WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.230 align:start position:0% [Music] 00:00:09.230 --> 00:00:09.240 align:start position:0% [Music] 00:00:09.240 --> 00:00:11.230 align:start position:0% [Music] thank<00:00:09.440> you<00:00:09.599> so<00:00:09.760> much<00:00:09.920> for<00:00:10.120> sticking<00:00:10.599> through<00:00:11.120> I 00:00:11.230 --> 00:00:11.240 align:start position:0% thank you so much for sticking through I 00:00:11.240 --> 00:00:14.470 align:start position:0% thank you so much for sticking through I know<00:00:11.519> everyone's<00:00:12.200> hungry<00:00:12.559> for<00:00:12.759> lunch<00:00:13.120> so<00:00:13.320> am<00:00:13.559> I 00:00:14.470 --> 00:00:14.480 align:start position:0% know everyone's hungry for lunch so am I 00:00:14.480 --> 00:00:18.150 align:start position:0% know everyone's hungry for lunch so am I uh<00:00:14.679> hopefully<00:00:15.639> this<00:00:16.279> this<00:00:16.400> will<00:00:16.600> be<00:00:17.400> a<00:00:17.640> solid 00:00:18.150 --> 00:00:18.160 align:start position:0% uh hopefully this this will be a solid 00:00:18.160 --> 00:00:20.390 align:start position:0% uh hopefully this this will be a solid one<00:00:19.000> after<00:00:19.320> which<00:00:19.560> you<00:00:19.760> think<00:00:19.960> you<00:00:20.080> will<00:00:20.240> need 00:00:20.390 --> 00:00:20.400 align:start position:0% one after which you think you will need 00:00:20.400 --> 00:00:24.230 align:start position:0% one after which you think you will need a<00:00:20.680> break<00:00:21.680> um<00:00:22.400> super<00:00:22.760> glad<00:00:23.080> that<00:00:23.240> you<00:00:23.640> are<00:00:24.000> still 00:00:24.230 --> 00:00:24.240 align:start position:0% a break um super glad that you are still 00:00:24.240 --> 00:00:27.830 align:start position:0% a break um super glad that you are still like<00:00:24.439> up<00:00:24.640> and<00:00:25.000> Alive<00:00:26.000> um<00:00:27.000> sweet<00:00:27.400> guys<00:00:27.560> I<00:00:27.679> think 00:00:27.830 --> 00:00:27.840 align:start position:0% like up and Alive um sweet guys I think 00:00:27.840 --> 00:00:30.589 align:start position:0% like up and Alive um sweet guys I think to<00:00:28.240> get<00:00:28.439> into<00:00:28.720> it<00:00:29.720> um 00:00:30.589 --> 00:00:30.599 align:start position:0% to get into it um 00:00:30.599 --> 00:00:33.750 align:start position:0% to get into it um um<00:00:31.599> I<00:00:31.800> sort<00:00:32.040> of<00:00:32.200> like<00:00:32.320> wanted<00:00:32.559> to<00:00:32.719> talk<00:00:32.960> about 00:00:33.750 --> 00:00:33.760 align:start position:0% um I sort of like wanted to talk about 00:00:33.760 --> 00:00:36.470 align:start position:0% um I sort of like wanted to talk about this<00:00:34.040> upcoming<00:00:34.559> thing<00:00:34.840> called<00:00:35.360> intents<00:00:36.360> which 00:00:36.470 --> 00:00:36.480 align:start position:0% this upcoming thing called intents which 00:00:36.480 --> 00:00:38.270 align:start position:0% this upcoming thing called intents which is<00:00:36.640> supposed<00:00:36.920> to<00:00:37.000> sort<00:00:37.160> of<00:00:37.320> like<00:00:37.520> change<00:00:38.120> how 00:00:38.270 --> 00:00:38.280 align:start position:0% is supposed to sort of like change how 00:00:38.280 --> 00:00:41.069 align:start position:0% is supposed to sort of like change how we<00:00:38.480> interact<00:00:38.920> with<00:00:39.079> chains<00:00:39.520> going<00:00:40.079> forward 00:00:41.069 --> 00:00:41.079 align:start position:0% we interact with chains going forward 00:00:41.079 --> 00:00:42.869 align:start position:0% we interact with chains going forward and<00:00:41.480> a<00:00:41.600> bunch<00:00:41.840> of 00:00:42.869 --> 00:00:42.879 align:start position:0% and a bunch of 00:00:42.879 --> 00:00:46.189 align:start position:0% and a bunch of like<00:00:43.879> projects<00:00:44.480> are<00:00:44.760> starting<00:00:45.079> to<00:00:45.280> look<00:00:45.800> at<00:00:46.039> it 00:00:46.189 --> 00:00:46.199 align:start position:0% like projects are starting to look at it 00:00:46.199 --> 00:00:48.750 align:start position:0% like projects are starting to look at it in<00:00:46.320> a<00:00:46.760> pretty<00:00:47.039> deep<00:00:47.320> level<00:00:48.000> including<00:00:48.480> people 00:00:48.750 --> 00:00:48.760 align:start position:0% in a pretty deep level including people 00:00:48.760 --> 00:00:51.950 align:start position:0% in a pretty deep level including people at<00:00:49.199> Unis<00:00:49.760> swap<00:00:50.760> cow<00:00:51.160> Swap<00:00:51.399> and<00:00:51.480> a<00:00:51.600> bunch<00:00:51.760> of 00:00:51.950 --> 00:00:51.960 align:start position:0% at Unis swap cow Swap and a bunch of 00:00:51.960 --> 00:00:55.310 align:start position:0% at Unis swap cow Swap and a bunch of like<00:00:52.160> other<00:00:52.840> protocols<00:00:53.840> um<00:00:54.160> so<00:00:54.320> I<00:00:54.440> just<00:00:54.559> wanted 00:00:55.310 --> 00:00:55.320 align:start position:0% like other protocols um so I just wanted 00:00:55.320 --> 00:00:58.910 align:start position:0% like other protocols um so I just wanted to<00:00:56.320> chat<00:00:56.680> about<00:00:57.039> an<00:00:57.199> upcoming<00:00:57.680> proposal<00:00:58.199> there 00:00:58.910 --> 00:00:58.920 align:start position:0% to chat about an upcoming proposal there 00:00:58.920 --> 00:01:00.549 align:start position:0% to chat about an upcoming proposal there and<00:00:59.199> talk<00:00:59.440> through<00:00:59.680> some<00:01:00.039> of<00:01:00.160> the<00:01:00.239> design 00:01:00.549 --> 00:01:00.559 align:start position:0% and talk through some of the design 00:01:00.559 --> 00:01:03.869 align:start position:0% and talk through some of the design choices<00:01:01.480> that<00:01:01.640> have<00:01:01.760> been<00:01:02.000> made<00:01:02.800> and<00:01:03.120> why 00:01:03.869 --> 00:01:03.879 align:start position:0% choices that have been made and why 00:01:03.879 --> 00:01:05.830 align:start position:0% choices that have been made and why those<00:01:04.159> might<00:01:04.360> not<00:01:04.559> be<00:01:04.839> right<00:01:05.360> and<00:01:05.519> how<00:01:05.720> could 00:01:05.830 --> 00:01:05.840 align:start position:0% those might not be right and how could 00:01:05.840 --> 00:01:08.910 align:start position:0% those might not be right and how could we<00:01:06.000> potentially<00:01:06.479> fix<00:01:06.840> it<00:01:07.840> uh<00:01:08.200> this<00:01:08.320> is<00:01:08.520> not<00:01:08.720> a 00:01:08.910 --> 00:01:08.920 align:start position:0% we potentially fix it uh this is not a 00:01:08.920 --> 00:01:12.390 align:start position:0% we potentially fix it uh this is not a diss<00:01:09.200> track<00:01:09.799> this<00:01:10.759> like<00:01:10.920> I'm<00:01:11.080> using<00:01:11.600> the<00:01:11.799> EIP 00:01:12.390 --> 00:01:12.400 align:start position:0% diss track this like I'm using the EIP 00:01:12.400 --> 00:01:16.350 align:start position:0% diss track this like I'm using the EIP or<00:01:12.600> ERC<00:01:13.400> as<00:01:13.720> like<00:01:14.400> U<00:01:14.759> sort<00:01:14.960> of<00:01:15.200> like<00:01:15.759> a<00:01:16.000> channel 00:01:16.350 --> 00:01:16.360 align:start position:0% or ERC as like U sort of like a channel 00:01:16.360 --> 00:01:19.630 align:start position:0% or ERC as like U sort of like a channel to<00:01:16.520> talk<00:01:16.720> about<00:01:16.960> this<00:01:17.119> stuff<00:01:17.920> not<00:01:18.479> really<00:01:19.479> uh 00:01:19.630 --> 00:01:19.640 align:start position:0% to talk about this stuff not really uh 00:01:19.640 --> 00:01:22.990 align:start position:0% to talk about this stuff not really uh talking<00:01:20.240> about<00:01:21.240> this<00:01:21.640> specific<00:01:22.640> uh 00:01:22.990 --> 00:01:23.000 align:start position:0% talking about this specific uh 00:01:23.000 --> 00:01:25.830 align:start position:0% talking about this specific uh implementation<00:01:23.840> right<00:01:24.479> I<00:01:24.920> work<00:01:25.159> at<00:01:25.320> socket 00:01:25.830 --> 00:01:25.840 align:start position:0% implementation right I work at socket 00:01:25.840 --> 00:01:28.510 align:start position:0% implementation right I work at socket I'm<00:01:26.240> web<00:01:26.560> of<00:01:26.880> also<00:01:27.119> go<00:01:27.280> by<00:01:27.439> VC<00:01:27.960> you<00:01:28.079> can<00:01:28.280> you<00:01:28.360> can 00:01:28.510 --> 00:01:28.520 align:start position:0% I'm web of also go by VC you can you can 00:01:28.520 --> 00:01:30.910 align:start position:0% I'm web of also go by VC you can you can find<00:01:28.720> me<00:01:28.880> after<00:01:29.159> the<00:01:29.520> talk 00:01:30.910 --> 00:01:30.920 align:start position:0% find me after the talk 00:01:30.920 --> 00:01:33.590 align:start position:0% find me after the talk but<00:01:31.640> if<00:01:31.720> you<00:01:31.840> want<00:01:31.960> to<00:01:32.119> check<00:01:32.360> out<00:01:32.840> the<00:01:33.200> exact 00:01:33.590 --> 00:01:33.600 align:start position:0% but if you want to check out the exact 00:01:33.600 --> 00:01:35.190 align:start position:0% but if you want to check out the exact proposal<00:01:34.040> I'm<00:01:34.200> talking<00:01:34.479> about<00:01:34.759> here<00:01:35.040> there's 00:01:35.190 --> 00:01:35.200 align:start position:0% proposal I'm talking about here there's 00:01:35.200 --> 00:01:39.190 align:start position:0% proposal I'm talking about here there's a<00:01:35.560> quick<00:01:35.880> QR<00:01:36.360> code<00:01:37.360> uh<00:01:38.079> I<00:01:38.200> think<00:01:38.479> this<00:01:38.640> is<00:01:39.000> by 00:01:39.190 --> 00:01:39.200 align:start position:0% a quick QR code uh I think this is by 00:01:39.200 --> 00:01:42.270 align:start position:0% a quick QR code uh I think this is by Mark<00:01:39.560> T<00:01:40.000> from<00:01:40.520> Unis<00:01:40.920> Swap<00:01:41.680> and<00:01:41.840> this<00:01:41.960> is<00:01:42.119> what 00:01:42.270 --> 00:01:42.280 align:start position:0% Mark T from Unis Swap and this is what 00:01:42.280 --> 00:01:44.030 align:start position:0% Mark T from Unis Swap and this is what Unis<00:01:42.600> swap<00:01:42.799> is<00:01:42.880> going<00:01:43.040> to<00:01:43.119> be<00:01:43.240> using<00:01:43.600> for<00:01:43.799> the 00:01:44.030 --> 00:01:44.040 align:start position:0% Unis swap is going to be using for the 00:01:44.040 --> 00:01:47.990 align:start position:0% Unis swap is going to be using for the crossing<00:01:44.640> swap<00:01:45.280> stuff<00:01:46.079> generally<00:01:46.920> speaking 00:01:47.990 --> 00:01:48.000 align:start position:0% crossing swap stuff generally speaking 00:01:48.000 --> 00:01:51.590 align:start position:0% crossing swap stuff generally speaking um<00:01:49.000> I<00:01:49.079> think<00:01:49.520> we<00:01:49.799> always<00:01:50.119> begin<00:01:50.640> this<00:01:51.159> topic 00:01:51.590 --> 00:01:51.600 align:start position:0% um I think we always begin this topic 00:01:51.600 --> 00:01:56.230 align:start position:0% um I think we always begin this topic with<00:01:52.240> what<00:01:52.439> really<00:01:52.680> are<00:01:53.159> intents<00:01:54.360> right<00:01:55.360> um 00:01:56.230 --> 00:01:56.240 align:start position:0% with what really are intents right um 00:01:56.240 --> 00:01:58.389 align:start position:0% with what really are intents right um unfortunately<00:01:57.240> that<00:01:57.360> is<00:01:57.560> something<00:01:58.079> I<00:01:58.200> don't 00:01:58.389 --> 00:01:58.399 align:start position:0% unfortunately that is something I don't 00:01:58.399 --> 00:02:00.270 align:start position:0% unfortunately that is something I don't want<00:01:58.520> to<00:01:58.719> get<00:01:58.880> into<00:01:59.320> for<00:01:59.520> this<00:01:59.920> particular 00:02:00.270 --> 00:02:00.280 align:start position:0% want to get into for this particular 00:02:00.280 --> 00:02:02.429 align:start position:0% want to get into for this particular dock<00:02:00.880> right<00:02:01.240> it<00:02:01.399> always<00:02:01.680> sort<00:02:01.840> of<00:02:02.000> like<00:02:02.159> goes 00:02:02.429 --> 00:02:02.439 align:start position:0% dock right it always sort of like goes 00:02:02.439 --> 00:02:04.310 align:start position:0% dock right it always sort of like goes into<00:02:02.880> like<00:02:03.159> something<00:02:03.600> you<00:02:03.719> don't<00:02:03.920> want<00:02:04.039> to 00:02:04.310 --> 00:02:04.320 align:start position:0% into like something you don't want to 00:02:04.320 --> 00:02:06.310 align:start position:0% into like something you don't want to get<00:02:04.520> into<00:02:05.039> right<00:02:05.520> but<00:02:05.640> I<00:02:05.759> think<00:02:05.920> broadly 00:02:06.310 --> 00:02:06.320 align:start position:0% get into right but I think broadly 00:02:06.320 --> 00:02:07.870 align:start position:0% get into right but I think broadly speaking<00:02:06.719> you<00:02:06.920> want<00:02:07.079> to<00:02:07.240> do<00:02:07.399> something<00:02:07.640> on 00:02:07.870 --> 00:02:07.880 align:start position:0% speaking you want to do something on 00:02:07.880 --> 00:02:10.749 align:start position:0% speaking you want to do something on chain<00:02:08.679> you<00:02:08.879> specify<00:02:09.440> it<00:02:09.840> someone<00:02:10.160> else<00:02:10.440> takes 00:02:10.749 --> 00:02:10.759 align:start position:0% chain you specify it someone else takes 00:02:10.759 --> 00:02:12.910 align:start position:0% chain you specify it someone else takes care<00:02:10.959> of<00:02:11.080> it<00:02:11.680> that's<00:02:11.879> like<00:02:12.040> the<00:02:12.200> rough<00:02:12.520> mental 00:02:12.910 --> 00:02:12.920 align:start position:0% care of it that's like the rough mental 00:02:12.920 --> 00:02:14.869 align:start position:0% care of it that's like the rough mental model<00:02:13.200> you<00:02:13.319> can<00:02:13.480> have<00:02:13.640> in<00:02:13.800> mind<00:02:14.400> and<00:02:14.560> this<00:02:14.680> is 00:02:14.869 --> 00:02:14.879 align:start position:0% model you can have in mind and this is 00:02:14.879 --> 00:02:16.910 align:start position:0% model you can have in mind and this is different<00:02:15.200> than<00:02:15.519> transactions<00:02:16.519> because<00:02:16.720> in 00:02:16.910 --> 00:02:16.920 align:start position:0% different than transactions because in 00:02:16.920 --> 00:02:19.350 align:start position:0% different than transactions because in transactions<00:02:17.599> you<00:02:17.920> sort<00:02:18.120> of<00:02:18.319> like<00:02:18.879> send<00:02:19.200> a 00:02:19.350 --> 00:02:19.360 align:start position:0% transactions you sort of like send a 00:02:19.360 --> 00:02:21.190 align:start position:0% transactions you sort of like send a transaction<00:02:19.800> on<00:02:20.040> chain<00:02:20.319> saying<00:02:20.720> exactly<00:02:21.080> what 00:02:21.190 --> 00:02:21.200 align:start position:0% transaction on chain saying exactly what 00:02:21.200 --> 00:02:23.150 align:start position:0% transaction on chain saying exactly what you<00:02:21.319> want<00:02:21.400> to<00:02:21.560> do<00:02:22.120> but<00:02:22.319> here<00:02:22.560> you<00:02:22.720> just<00:02:22.920> talk 00:02:23.150 --> 00:02:23.160 align:start position:0% you want to do but here you just talk 00:02:23.160 --> 00:02:24.869 align:start position:0% you want to do but here you just talk about<00:02:23.440> the<00:02:23.560> end<00:02:24.000> goal<00:02:24.239> you<00:02:24.319> want<00:02:24.440> to<00:02:24.560> achieve 00:02:24.869 --> 00:02:24.879 align:start position:0% about the end goal you want to achieve 00:02:24.879 --> 00:02:26.470 align:start position:0% about the end goal you want to achieve and<00:02:25.040> someone<00:02:25.319> else<00:02:25.519> sort<00:02:25.720> of<00:02:25.879> like<00:02:26.040> takes<00:02:26.319> care 00:02:26.470 --> 00:02:26.480 align:start position:0% and someone else sort of like takes care 00:02:26.480 --> 00:02:27.350 align:start position:0% and someone else sort of like takes care of<00:02:26.640> the 00:02:27.350 --> 00:02:27.360 align:start position:0% of the 00:02:27.360 --> 00:02:29.350 align:start position:0% of the execution<00:02:28.360> that's<00:02:28.560> like<00:02:28.760> roughly<00:02:29.080> how<00:02:29.239> to 00:02:29.350 --> 00:02:29.360 align:start position:0% execution that's like roughly how to 00:02:29.360 --> 00:02:32.550 align:start position:0% execution that's like roughly how to think<00:02:29.519> about<00:02:29.680> it 00:02:32.550 --> 00:02:32.560 align:start position:0% 00:02:32.560 --> 00:02:34.630 align:start position:0% um<00:02:32.920> so<00:02:33.120> I'm<00:02:33.319> going<00:02:33.519> to<00:02:33.680> talk<00:02:33.959> about<00:02:34.360> like<00:02:34.480> a 00:02:34.630 --> 00:02:34.640 align:start position:0% um so I'm going to talk about like a 00:02:34.640 --> 00:02:36.470 align:start position:0% um so I'm going to talk about like a particular<00:02:35.120> sort<00:02:35.319> of<00:02:35.480> like<00:02:35.640> design<00:02:36.040> pattern 00:02:36.470 --> 00:02:36.480 align:start position:0% particular sort of like design pattern 00:02:36.480 --> 00:02:39.910 align:start position:0% particular sort of like design pattern here<00:02:37.480> um<00:02:38.000> goals<00:02:38.280> of<00:02:38.440> this<00:02:38.599> particular<00:02:39.000> ERC 00:02:39.910 --> 00:02:39.920 align:start position:0% here um goals of this particular ERC 00:02:39.920 --> 00:02:42.589 align:start position:0% here um goals of this particular ERC 7683<00:02:40.920> are<00:02:41.159> about<00:02:41.599> how<00:02:41.720> do<00:02:41.840> we<00:02:42.000> make<00:02:42.159> it<00:02:42.319> such 00:02:42.589 --> 00:02:42.599 align:start position:0% 7683 are about how do we make it such 00:02:42.599 --> 00:02:46.070 align:start position:0% 7683 are about how do we make it such that<00:02:43.599> uh<00:02:43.800> fillers<00:02:44.319> aren't<00:02:44.720> fragmented<00:02:45.720> this 00:02:46.070 --> 00:02:46.080 align:start position:0% that uh fillers aren't fragmented this 00:02:46.080 --> 00:02:47.830 align:start position:0% that uh fillers aren't fragmented this probably<00:02:46.400> doesn't<00:02:46.680> make<00:02:46.879> sense<00:02:47.239> right<00:02:47.400> away 00:02:47.830 --> 00:02:47.840 align:start position:0% probably doesn't make sense right away 00:02:47.840 --> 00:02:49.270 align:start position:0% probably doesn't make sense right away so<00:02:48.000> let<00:02:48.120> me<00:02:48.280> give<00:02:48.400> you<00:02:48.560> guys<00:02:48.680> a<00:02:48.840> quick<00:02:49.120> like 00:02:49.270 --> 00:02:49.280 align:start position:0% so let me give you guys a quick like 00:02:49.280 --> 00:02:50.869 align:start position:0% so let me give you guys a quick like walk<00:02:49.599> through<00:02:50.080> about<00:02:50.360> what<00:02:50.519> really<00:02:50.720> is 00:02:50.869 --> 00:02:50.879 align:start position:0% walk through about what really is 00:02:50.879 --> 00:02:53.550 align:start position:0% walk through about what really is happening<00:02:51.280> here<00:02:51.959> so<00:02:52.120> you<00:02:52.239> see<00:02:52.440> a<00:02:52.599> nice<00:02:52.840> farmer 00:02:53.550 --> 00:02:53.560 align:start position:0% happening here so you see a nice farmer 00:02:53.560 --> 00:02:55.670 align:start position:0% happening here so you see a nice farmer Emoji<00:02:54.040> there<00:02:54.640> that<00:02:54.760> is<00:02:54.959> the<00:02:55.319> that<00:02:55.400> is<00:02:55.519> our 00:02:55.670 --> 00:02:55.680 align:start position:0% Emoji there that is the that is our 00:02:55.680 --> 00:02:57.949 align:start position:0% Emoji there that is the that is our normal<00:02:56.040> blockchain<00:02:56.440> user<00:02:56.760> today<00:02:57.560> who<00:02:57.680> is<00:02:57.840> sort 00:02:57.949 --> 00:02:57.959 align:start position:0% normal blockchain user today who is sort 00:02:57.959 --> 00:03:00.030 align:start position:0% normal blockchain user today who is sort of<00:02:58.120> like<00:02:58.280> signing<00:02:58.879> something<00:02:59.519> that<00:02:59.840> looks 00:03:00.030 --> 00:03:00.040 align:start position:0% of like signing something that looks 00:03:00.040 --> 00:03:01.949 align:start position:0% of like signing something that looks like<00:03:00.200> a<00:03:00.319> struct<00:03:01.200> where<00:03:01.319> he's<00:03:01.519> sort<00:03:01.680> of<00:03:01.800> like 00:03:01.949 --> 00:03:01.959 align:start position:0% like a struct where he's sort of like 00:03:01.959 --> 00:03:03.990 align:start position:0% like a struct where he's sort of like talking<00:03:02.280> about<00:03:02.959> what<00:03:03.120> chains<00:03:03.440> he<00:03:03.560> want<00:03:03.680> to<00:03:03.799> go 00:03:03.990 --> 00:03:04.000 align:start position:0% talking about what chains he want to go 00:03:04.000 --> 00:03:06.149 align:start position:0% talking about what chains he want to go between<00:03:04.840> what's<00:03:05.040> the<00:03:05.200> input<00:03:05.560> asset<00:03:05.959> what's 00:03:06.149 --> 00:03:06.159 align:start position:0% between what's the input asset what's 00:03:06.159 --> 00:03:08.910 align:start position:0% between what's the input asset what's the<00:03:06.280> output<00:03:06.680> asset<00:03:07.400> things<00:03:07.599> like<00:03:07.840> that<00:03:08.400> right 00:03:08.910 --> 00:03:08.920 align:start position:0% the output asset things like that right 00:03:08.920 --> 00:03:11.070 align:start position:0% the output asset things like that right and<00:03:09.040> he<00:03:09.159> sort<00:03:09.319> of<00:03:09.440> like<00:03:09.560> Signs<00:03:09.920> this<00:03:10.120> stuff<00:03:10.840> and 00:03:11.070 --> 00:03:11.080 align:start position:0% and he sort of like Signs this stuff and 00:03:11.080 --> 00:03:12.630 align:start position:0% and he sort of like Signs this stuff and sends<00:03:11.400> it<00:03:11.519> onchain<00:03:12.000> to<00:03:12.159> a<00:03:12.280> particular 00:03:12.630 --> 00:03:12.640 align:start position:0% sends it onchain to a particular 00:03:12.640 --> 00:03:14.589 align:start position:0% sends it onchain to a particular settlement<00:03:13.080> contract<00:03:13.519> on<00:03:13.720> some<00:03:13.920> Source 00:03:14.589 --> 00:03:14.599 align:start position:0% settlement contract on some Source 00:03:14.599 --> 00:03:16.990 align:start position:0% settlement contract on some Source Network<00:03:15.599> where<00:03:15.920> a<00:03:16.040> bunch<00:03:16.200> of<00:03:16.400> like<00:03:16.599> these 00:03:16.990 --> 00:03:17.000 align:start position:0% Network where a bunch of like these 00:03:17.000 --> 00:03:19.990 align:start position:0% Network where a bunch of like these robots<00:03:17.920> these<00:03:18.120> Bots<00:03:18.440> sort<00:03:18.640> of<00:03:18.879> like<00:03:19.519> look<00:03:19.760> up 00:03:19.990 --> 00:03:20.000 align:start position:0% robots these Bots sort of like look up 00:03:20.000 --> 00:03:22.430 align:start position:0% robots these Bots sort of like look up to<00:03:20.239> this<00:03:20.400> Source<00:03:20.720> chain<00:03:21.000> contract<00:03:21.480> for<00:03:22.280> what 00:03:22.430 --> 00:03:22.440 align:start position:0% to this Source chain contract for what 00:03:22.440 --> 00:03:24.830 align:start position:0% to this Source chain contract for what are<00:03:23.319> pending<00:03:23.799> intents<00:03:24.239> that<00:03:24.400> need<00:03:24.560> to<00:03:24.640> be 00:03:24.830 --> 00:03:24.840 align:start position:0% are pending intents that need to be 00:03:24.840 --> 00:03:27.949 align:start position:0% are pending intents that need to be filled<00:03:25.840> right<00:03:26.519> and<00:03:27.000> then<00:03:27.280> they<00:03:27.440> sort<00:03:27.599> of<00:03:27.799> like 00:03:27.949 --> 00:03:27.959 align:start position:0% filled right and then they sort of like 00:03:27.959 --> 00:03:30.270 align:start position:0% filled right and then they sort of like fill<00:03:28.239> it<00:03:28.560> on<00:03:28.760> the<00:03:28.959> destination 00:03:30.270 --> 00:03:30.280 align:start position:0% fill it on the destination 00:03:30.280 --> 00:03:32.589 align:start position:0% fill it on the destination and<00:03:30.480> then<00:03:30.680> there's<00:03:30.920> a<00:03:31.560> Oracle<00:03:32.120> that<00:03:32.239> sort<00:03:32.400> of 00:03:32.589 --> 00:03:32.599 align:start position:0% and then there's a Oracle that sort of 00:03:32.599 --> 00:03:34.110 align:start position:0% and then there's a Oracle that sort of lets<00:03:32.840> the<00:03:32.959> settlement<00:03:33.360> contract<00:03:33.680> on<00:03:33.840> Source 00:03:34.110 --> 00:03:34.120 align:start position:0% lets the settlement contract on Source 00:03:34.120 --> 00:03:36.670 align:start position:0% lets the settlement contract on Source chain<00:03:34.400> know<00:03:34.640> that<00:03:34.920> hey<00:03:35.680> the<00:03:36.040> request<00:03:36.400> that<00:03:36.519> you 00:03:36.670 --> 00:03:36.680 align:start position:0% chain know that hey the request that you 00:03:36.680 --> 00:03:38.270 align:start position:0% chain know that hey the request that you had<00:03:36.920> has<00:03:37.040> been<00:03:37.239> fulfilled<00:03:37.760> by<00:03:38.040> this 00:03:38.270 --> 00:03:38.280 align:start position:0% had has been fulfilled by this 00:03:38.280 --> 00:03:41.149 align:start position:0% had has been fulfilled by this particular<00:03:38.760> bot<00:03:39.319> on<00:03:39.560> destination<00:03:40.560> right<00:03:40.879> so 00:03:41.149 --> 00:03:41.159 align:start position:0% particular bot on destination right so 00:03:41.159 --> 00:03:45.750 align:start position:0% particular bot on destination right so really<00:03:41.519> simple<00:03:42.519> um<00:03:43.360> user<00:03:44.239> sends<00:03:44.840> funds<00:03:45.200> on 00:03:45.750 --> 00:03:45.760 align:start position:0% really simple um user sends funds on 00:03:45.760 --> 00:03:48.589 align:start position:0% really simple um user sends funds on Source<00:03:46.760> the<00:03:46.920> Bots<00:03:47.319> fill<00:03:47.599> it<00:03:48.000> on<00:03:48.200> the 00:03:48.589 --> 00:03:48.599 align:start position:0% Source the Bots fill it on the 00:03:48.599 --> 00:03:51.630 align:start position:0% Source the Bots fill it on the destination<00:03:49.599> and<00:03:49.840> then<00:03:50.439> the<00:03:50.799> Oracle<00:03:51.280> sort<00:03:51.480> of 00:03:51.630 --> 00:03:51.640 align:start position:0% destination and then the Oracle sort of 00:03:51.640 --> 00:03:54.390 align:start position:0% destination and then the Oracle sort of like<00:03:51.879> conveys<00:03:52.879> the<00:03:53.280> message<00:03:53.760> that<00:03:53.920> you<00:03:54.040> know 00:03:54.390 --> 00:03:54.400 align:start position:0% like conveys the message that you know 00:03:54.400 --> 00:03:57.149 align:start position:0% like conveys the message that you know things<00:03:54.599> are<00:03:54.799> done 00:03:57.149 --> 00:03:57.159 align:start position:0% things are done 00:03:57.159 --> 00:03:59.789 align:start position:0% things are done really<00:03:58.159> I<00:03:58.280> think<00:03:58.640> filler<00:03:59.079> fragmentation 00:03:59.789 --> 00:03:59.799 align:start position:0% really I think filler fragmentation 00:03:59.799 --> 00:04:02.869 align:start position:0% really I think filler fragmentation starts<00:04:00.519> here<00:04:01.120> right<00:04:01.599> so<00:04:01.959> now<00:04:02.200> we<00:04:02.400> have<00:04:02.640> two 00:04:02.869 --> 00:04:02.879 align:start position:0% starts here right so now we have two 00:04:02.879 --> 00:04:05.190 align:start position:0% starts here right so now we have two structs<00:04:03.799> which<00:04:04.000> basically<00:04:04.360> means<00:04:04.840> like<00:04:05.040> now 00:04:05.190 --> 00:04:05.200 align:start position:0% structs which basically means like now 00:04:05.200 --> 00:04:07.589 align:start position:0% structs which basically means like now we<00:04:05.400> have<00:04:05.599> like<00:04:05.760> two<00:04:06.000> intent<00:04:06.480> protocols<00:04:07.480> the 00:04:07.589 --> 00:04:07.599 align:start position:0% we have like two intent protocols the 00:04:07.599 --> 00:04:09.350 align:start position:0% we have like two intent protocols the only<00:04:07.959> difference<00:04:08.280> between<00:04:08.599> the<00:04:08.760> first<00:04:09.040> one 00:04:09.350 --> 00:04:09.360 align:start position:0% only difference between the first one 00:04:09.360 --> 00:04:11.149 align:start position:0% only difference between the first one and<00:04:09.519> the<00:04:09.680> second<00:04:09.920> one<00:04:10.480> is<00:04:10.640> that<00:04:10.799> the<00:04:10.920> second 00:04:11.149 --> 00:04:11.159 align:start position:0% and the second one is that the second 00:04:11.159 --> 00:04:13.270 align:start position:0% and the second one is that the second one<00:04:11.439> has<00:04:11.599> an<00:04:11.799> extra<00:04:12.159> parameter<00:04:12.680> called<00:04:13.000> call 00:04:13.270 --> 00:04:13.280 align:start position:0% one has an extra parameter called call 00:04:13.280 --> 00:04:15.509 align:start position:0% one has an extra parameter called call data<00:04:14.120> let's<00:04:14.360> assume<00:04:14.840> everything<00:04:15.159> else<00:04:15.360> is 00:04:15.509 --> 00:04:15.519 align:start position:0% data let's assume everything else is 00:04:15.519 --> 00:04:18.310 align:start position:0% data let's assume everything else is same<00:04:16.160> this<00:04:16.280> is<00:04:16.400> the<00:04:16.560> only<00:04:16.880> difference<00:04:17.560> right 00:04:18.310 --> 00:04:18.320 align:start position:0% same this is the only difference right 00:04:18.320 --> 00:04:20.590 align:start position:0% same this is the only difference right um<00:04:18.560> due<00:04:18.799> to<00:04:19.000> which<00:04:19.239> now<00:04:19.440> we<00:04:19.639> have<00:04:19.919> these<00:04:20.120> two 00:04:20.590 --> 00:04:20.600 align:start position:0% um due to which now we have these two 00:04:20.600 --> 00:04:24.070 align:start position:0% um due to which now we have these two separate<00:04:21.240> contracts<00:04:22.240> and<00:04:23.080> earlier<00:04:23.600> while<00:04:23.880> we 00:04:24.070 --> 00:04:24.080 align:start position:0% separate contracts and earlier while we 00:04:24.080 --> 00:04:27.230 align:start position:0% separate contracts and earlier while we had<00:04:24.360> like<00:04:25.080> eight<00:04:25.400> fillers<00:04:26.400> solving<00:04:26.800> for<00:04:27.040> this 00:04:27.230 --> 00:04:27.240 align:start position:0% had like eight fillers solving for this 00:04:27.240 --> 00:04:29.390 align:start position:0% had like eight fillers solving for this particular<00:04:27.600> intent<00:04:27.960> protocol<00:04:28.759> as<00:04:28.880> soon<00:04:29.080> as<00:04:29.240> we 00:04:29.390 --> 00:04:29.400 align:start position:0% particular intent protocol as soon as we 00:04:29.400 --> 00:04:31.590 align:start position:0% particular intent protocol as soon as we have<00:04:29.840> two<00:04:30.000> intent<00:04:30.360> protocols<00:04:31.160> these<00:04:31.320> are<00:04:31.440> now 00:04:31.590 --> 00:04:31.600 align:start position:0% have two intent protocols these are now 00:04:31.600 --> 00:04:34.510 align:start position:0% have two intent protocols these are now split<00:04:31.919> in<00:04:32.360> two<00:04:33.360> right<00:04:33.880> as<00:04:34.039> more<00:04:34.240> and<00:04:34.360> more 00:04:34.510 --> 00:04:34.520 align:start position:0% split in two right as more and more 00:04:34.520 --> 00:04:36.749 align:start position:0% split in two right as more and more intent<00:04:34.840> protocols<00:04:35.240> go<00:04:35.479> live<00:04:36.320> sort<00:04:36.520> of<00:04:36.639> like 00:04:36.749 --> 00:04:36.759 align:start position:0% intent protocols go live sort of like 00:04:36.759 --> 00:04:38.550 align:start position:0% intent protocols go live sort of like fillers<00:04:37.240> get<00:04:37.400> fragmented<00:04:38.039> because<00:04:38.280> they<00:04:38.400> need 00:04:38.550 --> 00:04:38.560 align:start position:0% fillers get fragmented because they need 00:04:38.560 --> 00:04:40.029 align:start position:0% fillers get fragmented because they need to<00:04:38.680> do<00:04:38.880> more<00:04:39.080> work<00:04:39.360> they<00:04:39.479> need<00:04:39.600> to<00:04:39.720> do<00:04:39.840> more 00:04:40.029 --> 00:04:40.039 align:start position:0% to do more work they need to do more 00:04:40.039 --> 00:04:42.310 align:start position:0% to do more work they need to do more Integrations<00:04:40.800> and<00:04:41.120> stuff<00:04:41.360> like<00:04:41.520> that<00:04:41.880> right 00:04:42.310 --> 00:04:42.320 align:start position:0% Integrations and stuff like that right 00:04:42.320 --> 00:04:45.790 align:start position:0% Integrations and stuff like that right super<00:04:42.680> annoying<00:04:43.160> stuff<00:04:44.039> um<00:04:44.520> this<00:04:44.639> is<00:04:45.240> harmful 00:04:45.790 --> 00:04:45.800 align:start position:0% super annoying stuff um this is harmful 00:04:45.800 --> 00:04:48.550 align:start position:0% super annoying stuff um this is harmful for<00:04:46.240> everyone<00:04:47.240> not<00:04:47.520> not<00:04:47.720> exactly<00:04:48.080> harmful<00:04:48.440> but 00:04:48.550 --> 00:04:48.560 align:start position:0% for everyone not not exactly harmful but 00:04:48.560 --> 00:04:50.830 align:start position:0% for everyone not not exactly harmful but like<00:04:48.720> really<00:04:49.160> undesirable<00:04:50.160> specifically 00:04:50.830 --> 00:04:50.840 align:start position:0% like really undesirable specifically 00:04:50.840 --> 00:04:53.749 align:start position:0% like really undesirable specifically because<00:04:51.560> there<00:04:51.720> aren't<00:04:52.039> too<00:04:52.240> many<00:04:53.000> fillers 00:04:53.749 --> 00:04:53.759 align:start position:0% because there aren't too many fillers 00:04:53.759 --> 00:04:55.749 align:start position:0% because there aren't too many fillers anywhere<00:04:54.120> in<00:04:54.240> the<00:04:54.440> space<00:04:54.960> right<00:04:55.440> there<00:04:55.560> are 00:04:55.749 --> 00:04:55.759 align:start position:0% anywhere in the space right there are 00:04:55.759 --> 00:04:57.189 align:start position:0% anywhere in the space right there are there<00:04:55.840> are<00:04:56.000> probably<00:04:56.280> like<00:04:56.440> 15<00:04:56.759> to<00:04:56.919> 20 00:04:57.189 --> 00:04:57.199 align:start position:0% there are probably like 15 to 20 00:04:57.199 --> 00:04:59.189 align:start position:0% there are probably like 15 to 20 entities<00:04:58.039> that<00:04:58.199> are<00:04:58.360> sort<00:04:58.560> of<00:04:58.720> like<00:04:58.840> operating 00:04:59.189 --> 00:04:59.199 align:start position:0% entities that are sort of like operating 00:04:59.199 --> 00:05:01.629 align:start position:0% entities that are sort of like operating in<00:04:59.320> this<00:04:59.720> particular<00:05:00.080> role<00:05:01.080> and<00:05:01.280> if<00:05:01.360> you<00:05:01.479> sort 00:05:01.629 --> 00:05:01.639 align:start position:0% in this particular role and if you sort 00:05:01.639 --> 00:05:03.310 align:start position:0% in this particular role and if you sort of<00:05:01.800> like<00:05:01.919> start<00:05:02.199> fragmenting<00:05:02.800> those<00:05:03.000> we<00:05:03.120> don't 00:05:03.310 --> 00:05:03.320 align:start position:0% of like start fragmenting those we don't 00:05:03.320 --> 00:05:06.230 align:start position:0% of like start fragmenting those we don't know<00:05:03.479> where<00:05:03.639> we'll<00:05:03.840> end<00:05:04.039> up<00:05:04.479> right<00:05:05.000> so<00:05:05.479> we<00:05:05.680> want 00:05:06.230 --> 00:05:06.240 align:start position:0% know where we'll end up right so we want 00:05:06.240 --> 00:05:08.590 align:start position:0% know where we'll end up right so we want competition<00:05:06.840> over<00:05:07.080> here<00:05:07.680> so<00:05:07.840> we<00:05:07.960> want<00:05:08.280> as<00:05:08.400> many 00:05:08.590 --> 00:05:08.600 align:start position:0% competition over here so we want as many 00:05:08.600 --> 00:05:10.790 align:start position:0% competition over here so we want as many fillers<00:05:09.080> as<00:05:09.280> possible<00:05:09.840> so<00:05:10.039> fragmentation<00:05:10.639> is 00:05:10.790 --> 00:05:10.800 align:start position:0% fillers as possible so fragmentation is 00:05:10.800 --> 00:05:12.390 align:start position:0% fillers as possible so fragmentation is something<00:05:11.039> we<00:05:11.160> want<00:05:11.320> to<00:05:11.440> avoid<00:05:11.840> here 00:05:12.390 --> 00:05:12.400 align:start position:0% something we want to avoid here 00:05:12.400 --> 00:05:14.150 align:start position:0% something we want to avoid here fragmentation<00:05:13.000> is<00:05:13.160> bad<00:05:13.400> for<00:05:13.600> all<00:05:13.800> three<00:05:14.039> of 00:05:14.150 --> 00:05:14.160 align:start position:0% fragmentation is bad for all three of 00:05:14.160 --> 00:05:16.469 align:start position:0% fragmentation is bad for all three of these<00:05:14.360> parties<00:05:15.080> it's<00:05:15.280> bad<00:05:15.479> for<00:05:15.680> the<00:05:15.759> user 00:05:16.469 --> 00:05:16.479 align:start position:0% these parties it's bad for the user 00:05:16.479 --> 00:05:17.990 align:start position:0% these parties it's bad for the user because<00:05:16.720> if<00:05:16.840> people<00:05:17.080> aren't<00:05:17.400> competing 00:05:17.990 --> 00:05:18.000 align:start position:0% because if people aren't competing 00:05:18.000 --> 00:05:19.670 align:start position:0% because if people aren't competing you're<00:05:18.199> going<00:05:18.360> to<00:05:18.520> get<00:05:18.680> the<00:05:18.840> worst<00:05:19.280> possible 00:05:19.670 --> 00:05:19.680 align:start position:0% you're going to get the worst possible 00:05:19.680 --> 00:05:23.230 align:start position:0% you're going to get the worst possible price<00:05:20.639> right<00:05:21.160> it's<00:05:21.840> um<00:05:22.120> and<00:05:22.639> if<00:05:22.800> you<00:05:22.960> don't 00:05:23.230 --> 00:05:23.240 align:start position:0% price right it's um and if you don't 00:05:23.240 --> 00:05:25.029 align:start position:0% price right it's um and if you don't have<00:05:23.400> like<00:05:23.560> an<00:05:23.720> intent<00:05:24.120> standard<00:05:24.800> then<00:05:24.919> you 00:05:25.029 --> 00:05:25.039 align:start position:0% have like an intent standard then you 00:05:25.039 --> 00:05:26.909 align:start position:0% have like an intent standard then you don't<00:05:25.280> actually<00:05:25.880> understand<00:05:26.240> what<00:05:26.600> you<00:05:26.759> are 00:05:26.909 --> 00:05:26.919 align:start position:0% don't actually understand what you are 00:05:26.919 --> 00:05:28.870 align:start position:0% don't actually understand what you are signing<00:05:27.680> so<00:05:27.880> someday<00:05:28.240> you<00:05:28.360> might<00:05:28.560> sign 00:05:28.870 --> 00:05:28.880 align:start position:0% signing so someday you might sign 00:05:28.880 --> 00:05:31.230 align:start position:0% signing so someday you might sign something<00:05:29.360> that<00:05:30.120> give<00:05:30.360> someone<00:05:30.680> authority<00:05:31.080> to 00:05:31.230 --> 00:05:31.240 align:start position:0% something that give someone authority to 00:05:31.240 --> 00:05:33.390 align:start position:0% something that give someone authority to pull<00:05:31.479> all<00:05:31.639> of<00:05:31.759> your<00:05:31.880> funds<00:05:32.199> away<00:05:32.479> forever 00:05:33.390 --> 00:05:33.400 align:start position:0% pull all of your funds away forever 00:05:33.400 --> 00:05:34.950 align:start position:0% pull all of your funds away forever right<00:05:33.560> so<00:05:33.720> you<00:05:33.840> know<00:05:34.039> like<00:05:34.199> chances<00:05:34.520> of<00:05:34.680> rug 00:05:34.950 --> 00:05:34.960 align:start position:0% right so you know like chances of rug 00:05:34.960 --> 00:05:37.230 align:start position:0% right so you know like chances of rug pull<00:05:35.639> we<00:05:35.919> hear<00:05:36.160> about<00:05:36.360> fishing<00:05:36.759> attacks<00:05:37.080> with 00:05:37.230 --> 00:05:37.240 align:start position:0% pull we hear about fishing attacks with 00:05:37.240 --> 00:05:40.070 align:start position:0% pull we hear about fishing attacks with like<00:05:37.400> permit<00:05:37.720> to<00:05:38.520> Witnesses<00:05:39.440> all<00:05:39.600> the<00:05:39.759> time 00:05:40.070 --> 00:05:40.080 align:start position:0% like permit to Witnesses all the time 00:05:40.080 --> 00:05:42.390 align:start position:0% like permit to Witnesses all the time right<00:05:40.240> so<00:05:41.080> we<00:05:41.400> want<00:05:41.560> to<00:05:41.680> like<00:05:41.840> standardize<00:05:42.319> on 00:05:42.390 --> 00:05:42.400 align:start position:0% right so we want to like standardize on 00:05:42.400 --> 00:05:44.629 align:start position:0% right so we want to like standardize on this<00:05:42.520> layer<00:05:42.800> for<00:05:42.960> sure<00:05:43.840> it's<00:05:44.039> bad<00:05:44.199> for<00:05:44.319> intent 00:05:44.629 --> 00:05:44.639 align:start position:0% this layer for sure it's bad for intent 00:05:44.639 --> 00:05:48.029 align:start position:0% this layer for sure it's bad for intent protocols<00:05:45.160> because<00:05:46.039> we<00:05:46.199> had<00:05:46.400> eight<00:05:47.039> fillers 00:05:48.029 --> 00:05:48.039 align:start position:0% protocols because we had eight fillers 00:05:48.039 --> 00:05:50.150 align:start position:0% protocols because we had eight fillers you<00:05:48.199> launch<00:05:48.479> an<00:05:49.280> you<00:05:49.440> you<00:05:49.520> launch<00:05:49.759> an<00:05:49.840> intent 00:05:50.150 --> 00:05:50.160 align:start position:0% you launch an you you launch an intent 00:05:50.160 --> 00:05:52.150 align:start position:0% you launch an you you launch an intent protocol<00:05:50.560> and<00:05:50.680> you<00:05:50.759> have<00:05:50.880> to<00:05:51.080> like<00:05:51.199> sort<00:05:51.400> of 00:05:52.150 --> 00:05:52.160 align:start position:0% protocol and you have to like sort of 00:05:52.160 --> 00:05:54.550 align:start position:0% protocol and you have to like sort of bribe<00:05:53.000> four<00:05:53.280> of<00:05:53.479> them<00:05:53.720> to<00:05:53.840> sort<00:05:54.000> of<00:05:54.160> like<00:05:54.280> Port 00:05:54.550 --> 00:05:54.560 align:start position:0% bribe four of them to sort of like Port 00:05:54.560 --> 00:05:57.110 align:start position:0% bribe four of them to sort of like Port over<00:05:54.759> to<00:05:54.919> your<00:05:55.199> thing<00:05:55.960> and<00:05:56.120> then<00:05:56.600> as<00:05:56.759> more<00:05:56.960> and 00:05:57.110 --> 00:05:57.120 align:start position:0% over to your thing and then as more and 00:05:57.120 --> 00:05:58.990 align:start position:0% over to your thing and then as more and more<00:05:57.400> of<00:05:57.560> these<00:05:57.720> protocols<00:05:58.160> launch<00:05:58.840> it 00:05:58.990 --> 00:05:59.000 align:start position:0% more of these protocols launch it 00:05:59.000 --> 00:06:01.070 align:start position:0% more of these protocols launch it becomes<00:05:59.319> even<00:05:59.479> more<00:05:59.680> more<00:05:59.880> expensive<00:06:00.759> because 00:06:01.070 --> 00:06:01.080 align:start position:0% becomes even more more expensive because 00:06:01.080 --> 00:06:04.189 align:start position:0% becomes even more more expensive because these<00:06:01.400> fillers<00:06:02.400> aren't<00:06:02.960> commoditized<00:06:03.960> uh 00:06:04.189 --> 00:06:04.199 align:start position:0% these fillers aren't commoditized uh 00:06:04.199 --> 00:06:06.029 align:start position:0% these fillers aren't commoditized uh they<00:06:04.280> are<00:06:04.479> sort<00:06:04.680> of<00:06:04.840> like<00:06:05.039> specialized<00:06:05.919> and 00:06:06.029 --> 00:06:06.039 align:start position:0% they are sort of like specialized and 00:06:06.039 --> 00:06:08.189 align:start position:0% they are sort of like specialized and you<00:06:06.120> have<00:06:06.240> to<00:06:06.400> like<00:06:06.520> get<00:06:06.680> into<00:06:07.000> like<00:06:07.199> specific 00:06:08.189 --> 00:06:08.199 align:start position:0% you have to like get into like specific 00:06:08.199 --> 00:06:10.710 align:start position:0% you have to like get into like specific agreements<00:06:08.680> with<00:06:08.840> them<00:06:09.000> and<00:06:09.199> whatnot<00:06:09.720> so 00:06:10.710 --> 00:06:10.720 align:start position:0% agreements with them and whatnot so 00:06:10.720 --> 00:06:12.830 align:start position:0% agreements with them and whatnot so ideally<00:06:11.199> you<00:06:11.280> want<00:06:11.440> to<00:06:11.639> commoditize<00:06:12.360> and<00:06:12.599> have 00:06:12.830 --> 00:06:12.840 align:start position:0% ideally you want to commoditize and have 00:06:12.840 --> 00:06:15.070 align:start position:0% ideally you want to commoditize and have a<00:06:13.039> lot<00:06:13.240> of<00:06:13.400> fillers<00:06:14.280> so<00:06:14.440> you<00:06:14.599> have<00:06:14.840> high 00:06:15.070 --> 00:06:15.080 align:start position:0% a lot of fillers so you have high 00:06:15.080 --> 00:06:16.990 align:start position:0% a lot of fillers so you have high competition<00:06:15.840> if<00:06:15.919> you<00:06:16.039> launch<00:06:16.280> an<00:06:16.599> intent 00:06:16.990 --> 00:06:17.000 align:start position:0% competition if you launch an intent 00:06:17.000 --> 00:06:19.390 align:start position:0% competition if you launch an intent protocol<00:06:17.479> you<00:06:17.599> have<00:06:17.720> fillers<00:06:18.080> for<00:06:18.280> your<00:06:19.000> user 00:06:19.390 --> 00:06:19.400 align:start position:0% protocol you have fillers for your user 00:06:19.400 --> 00:06:22.390 align:start position:0% protocol you have fillers for your user requests<00:06:20.400> and<00:06:20.680> for<00:06:20.919> fillers<00:06:21.919> um<00:06:22.120> they<00:06:22.240> just 00:06:22.390 --> 00:06:22.400 align:start position:0% requests and for fillers um they just 00:06:22.400 --> 00:06:24.270 align:start position:0% requests and for fillers um they just want<00:06:22.680> access<00:06:22.960> to<00:06:23.240> more<00:06:23.599> autoflow<00:06:24.080> without 00:06:24.270 --> 00:06:24.280 align:start position:0% want access to more autoflow without 00:06:24.280 --> 00:06:27.390 align:start position:0% want access to more autoflow without doing<00:06:24.520> a<00:06:24.639> lot<00:06:24.800> of<00:06:25.000> work<00:06:25.720> so<00:06:26.120> as<00:06:26.240> a<00:06:26.720> like<00:06:27.000> just<00:06:27.199> as 00:06:27.390 --> 00:06:27.400 align:start position:0% doing a lot of work so as a like just as 00:06:27.400 --> 00:06:30.029 align:start position:0% doing a lot of work so as a like just as put<00:06:27.599> on<00:06:27.720> your<00:06:27.840> Market<00:06:28.160> maker<00:06:28.479> hat<00:06:29.840> what<00:06:29.960> you 00:06:30.029 --> 00:06:30.039 align:start position:0% put on your Market maker hat what you 00:06:30.039 --> 00:06:31.830 align:start position:0% put on your Market maker hat what you want<00:06:30.199> to<00:06:30.319> do<00:06:30.560> is<00:06:30.759> like<00:06:31.240> if<00:06:31.400> there's<00:06:31.639> an 00:06:31.830 --> 00:06:31.840 align:start position:0% want to do is like if there's an 00:06:31.840 --> 00:06:34.870 align:start position:0% want to do is like if there's an opportunity<00:06:32.360> out<00:06:32.599> there<00:06:33.240> I<00:06:33.400> have<00:06:33.720> capital<00:06:34.720> I 00:06:34.870 --> 00:06:34.880 align:start position:0% opportunity out there I have capital I 00:06:34.880 --> 00:06:37.189 align:start position:0% opportunity out there I have capital I want<00:06:35.360> access<00:06:35.639> to<00:06:35.840> that<00:06:36.039> opportunity<00:06:36.800> for<00:06:37.000> the 00:06:37.189 --> 00:06:37.199 align:start position:0% want access to that opportunity for the 00:06:37.199 --> 00:06:39.830 align:start position:0% want access to that opportunity for the least<00:06:37.560> amount<00:06:37.800> of<00:06:37.919> work<00:06:38.319> possible<00:06:39.319> so<00:06:39.479> I<00:06:39.599> think 00:06:39.830 --> 00:06:39.840 align:start position:0% least amount of work possible so I think 00:06:39.840 --> 00:06:42.510 align:start position:0% least amount of work possible so I think all<00:06:40.000> in<00:06:40.199> all<00:06:41.199> it<00:06:41.319> sounds<00:06:41.720> highly<00:06:42.000> beneficial 00:06:42.510 --> 00:06:42.520 align:start position:0% all in all it sounds highly beneficial 00:06:42.520 --> 00:06:43.870 align:start position:0% all in all it sounds highly beneficial that<00:06:42.639> we<00:06:42.759> should<00:06:42.960> like<00:06:43.120> standardize<00:06:43.720> this 00:06:43.870 --> 00:06:43.880 align:start position:0% that we should like standardize this 00:06:43.880 --> 00:06:46.710 align:start position:0% that we should like standardize this part<00:06:44.039> of<00:06:44.160> the<00:06:44.280> layer<00:06:45.039> for<00:06:45.360> all<00:06:45.639> three<00:06:45.800> of<00:06:45.960> these 00:06:46.710 --> 00:06:46.720 align:start position:0% part of the layer for all three of these 00:06:46.720 --> 00:06:48.909 align:start position:0% part of the layer for all three of these parties<00:06:47.720> and<00:06:47.919> that's<00:06:48.120> what<00:06:48.319> the<00:06:48.479> CIP<00:06:48.840> is 00:06:48.909 --> 00:06:48.919 align:start position:0% parties and that's what the CIP is 00:06:48.919 --> 00:06:51.390 align:start position:0% parties and that's what the CIP is trying<00:06:49.160> to<00:06:49.280> do<00:06:49.720> the<00:06:49.880> ideal<00:06:50.240> world<00:06:50.479> is<00:06:50.680> where<00:06:51.280> I 00:06:51.390 --> 00:06:51.400 align:start position:0% trying to do the ideal world is where I 00:06:51.400 --> 00:06:53.230 align:start position:0% trying to do the ideal world is where I launch<00:06:51.639> a<00:06:51.759> new<00:06:52.120> intent<00:06:52.440> protocol<00:06:52.919> and<00:06:53.039> all 00:06:53.230 --> 00:06:53.240 align:start position:0% launch a new intent protocol and all 00:06:53.240 --> 00:06:55.230 align:start position:0% launch a new intent protocol and all filler<00:06:53.639> start<00:06:53.919> filling<00:06:54.319> on<00:06:54.479> my<00:06:54.639> protocol<00:06:55.080> on 00:06:55.230 --> 00:06:55.240 align:start position:0% filler start filling on my protocol on 00:06:55.240 --> 00:06:57.629 align:start position:0% filler start filling on my protocol on day<00:06:55.440> one<00:06:56.080> with<00:06:56.280> like<00:06:56.599> close<00:06:56.840> to<00:06:56.960> zero<00:06:57.240> effort 00:06:57.629 --> 00:06:57.639 align:start position:0% day one with like close to zero effort 00:06:57.639 --> 00:06:59.629 align:start position:0% day one with like close to zero effort that's<00:06:57.800> the<00:06:57.919> idle<00:06:58.280> world<00:06:58.960> that's<00:06:59.120> the<00:06:59.240> world 00:06:59.629 --> 00:06:59.639 align:start position:0% that's the idle world that's the world 00:06:59.639 --> 00:07:02.110 align:start position:0% that's the idle world that's the world the<00:06:59.759> CIP<00:07:00.120> is<00:07:00.240> trying<00:07:00.440> to<00:07:00.599> take<00:07:00.759> us 00:07:02.110 --> 00:07:02.120 align:start position:0% the CIP is trying to take us 00:07:02.120 --> 00:07:05.990 align:start position:0% the CIP is trying to take us to<00:07:03.120> um<00:07:03.879> again<00:07:04.120> put<00:07:04.280> your<00:07:04.400> Market<00:07:04.720> maker<00:07:05.000> hat<00:07:05.199> on 00:07:05.990 --> 00:07:06.000 align:start position:0% to um again put your Market maker hat on 00:07:06.000 --> 00:07:07.550 align:start position:0% to um again put your Market maker hat on imagine<00:07:06.319> you<00:07:06.440> are<00:07:06.599> participating<00:07:07.120> in<00:07:07.240> one<00:07:07.360> of 00:07:07.550 --> 00:07:07.560 align:start position:0% imagine you are participating in one of 00:07:07.560 --> 00:07:10.070 align:start position:0% imagine you are participating in one of these<00:07:07.680> intent<00:07:08.000> based<00:07:08.599> protocols<00:07:09.599> how<00:07:09.759> does<00:07:09.919> a 00:07:10.070 --> 00:07:10.080 align:start position:0% these intent based protocols how does a 00:07:10.080 --> 00:07:12.589 align:start position:0% these intent based protocols how does a filler<00:07:10.520> decide<00:07:10.800> to<00:07:10.960> fill<00:07:11.680> like<00:07:11.960> what<00:07:12.160> is<00:07:12.360> the 00:07:12.589 --> 00:07:12.599 align:start position:0% filler decide to fill like what is the 00:07:12.599 --> 00:07:17.350 align:start position:0% filler decide to fill like what is the decision<00:07:13.000> Tree<00:07:13.759> on<00:07:14.000> their<00:07:14.240> end<00:07:15.319> right<00:07:16.319> um<00:07:17.080> you 00:07:17.350 --> 00:07:17.360 align:start position:0% decision Tree on their end right um you 00:07:17.360 --> 00:07:19.990 align:start position:0% decision Tree on their end right um you receive<00:07:17.720> an<00:07:18.080> intent<00:07:19.080> the<00:07:19.280> the<00:07:19.440> first<00:07:19.720> thought 00:07:19.990 --> 00:07:20.000 align:start position:0% receive an intent the the first thought 00:07:20.000 --> 00:07:22.749 align:start position:0% receive an intent the the first thought you<00:07:20.280> have<00:07:21.280> or<00:07:21.560> the<00:07:21.720> first<00:07:21.960> thing<00:07:22.120> your<00:07:22.360> program 00:07:22.749 --> 00:07:22.759 align:start position:0% you have or the first thing your program 00:07:22.759 --> 00:07:26.869 align:start position:0% you have or the first thing your program does<00:07:23.199> is<00:07:23.919> do<00:07:24.080> I<00:07:24.520> understand<00:07:24.800> this<00:07:25.280> aut<00:07:25.879> type 00:07:26.869 --> 00:07:26.879 align:start position:0% does is do I understand this aut type 00:07:26.879 --> 00:07:29.710 align:start position:0% does is do I understand this aut type and<00:07:27.160> like<00:07:27.360> how<00:07:27.520> do<00:07:27.680> I<00:07:27.919> interact<00:07:28.360> with<00:07:28.520> it<00:07:29.599> uh 00:07:29.710 --> 00:07:29.720 align:start position:0% and like how do I interact with it uh 00:07:29.720 --> 00:07:31.350 align:start position:0% and like how do I interact with it uh with<00:07:29.840> this<00:07:30.080> particular<00:07:30.400> onchain<00:07:30.840> contracts 00:07:31.350 --> 00:07:31.360 align:start position:0% with this particular onchain contracts 00:07:31.360 --> 00:07:32.909 align:start position:0% with this particular onchain contracts and<00:07:31.639> stuff<00:07:31.879> like<00:07:32.039> that<00:07:32.199> like<00:07:32.360> really<00:07:32.680> like 00:07:32.909 --> 00:07:32.919 align:start position:0% and stuff like that like really like 00:07:32.919 --> 00:07:34.749 align:start position:0% and stuff like that like really like generic 00:07:34.749 --> 00:07:34.759 align:start position:0% generic 00:07:34.759 --> 00:07:37.270 align:start position:0% generic interpretation<00:07:35.759> uh<00:07:35.960> second<00:07:36.319> is<00:07:36.560> like<00:07:36.720> do<00:07:36.879> I 00:07:37.270 --> 00:07:37.280 align:start position:0% interpretation uh second is like do I 00:07:37.280 --> 00:07:38.510 align:start position:0% interpretation uh second is like do I understand<00:07:37.680> how<00:07:37.840> does<00:07:38.039> this<00:07:38.199> particular 00:07:38.510 --> 00:07:38.520 align:start position:0% understand how does this particular 00:07:38.520 --> 00:07:40.830 align:start position:0% understand how does this particular protocol<00:07:38.919> work<00:07:39.440> can<00:07:39.560> I<00:07:39.680> fill<00:07:39.919> for<00:07:40.160> it<00:07:40.599> stuff 00:07:40.830 --> 00:07:40.840 align:start position:0% protocol work can I fill for it stuff 00:07:40.840 --> 00:07:43.950 align:start position:0% protocol work can I fill for it stuff like<00:07:41.000> that<00:07:41.560> so<00:07:42.280> users<00:07:42.720> and<00:07:42.919> fillers<00:07:43.639> are<00:07:43.800> sort 00:07:43.950 --> 00:07:43.960 align:start position:0% like that so users and fillers are sort 00:07:43.960 --> 00:07:46.710 align:start position:0% like that so users and fillers are sort of<00:07:44.120> like<00:07:44.240> entities<00:07:44.639> on<00:07:44.840> both<00:07:45.120> ends<00:07:46.120> and<00:07:46.599> we 00:07:46.710 --> 00:07:46.720 align:start position:0% of like entities on both ends and we 00:07:46.720 --> 00:07:48.430 align:start position:0% of like entities on both ends and we need<00:07:46.879> to<00:07:47.039> give<00:07:47.240> them<00:07:47.479> like<00:07:47.599> a<00:07:47.759> way<00:07:47.960> to<00:07:48.080> sort<00:07:48.280> of 00:07:48.430 --> 00:07:48.440 align:start position:0% need to give them like a way to sort of 00:07:48.440 --> 00:07:50.309 align:start position:0% need to give them like a way to sort of like<00:07:48.599> communicate<00:07:49.599> think<00:07:49.800> about<00:07:50.039> it<00:07:50.199> like 00:07:50.309 --> 00:07:50.319 align:start position:0% like communicate think about it like 00:07:50.319 --> 00:07:52.990 align:start position:0% like communicate think about it like sending<00:07:50.599> a<00:07:50.759> mors<00:07:51.080> code<00:07:51.879> right<00:07:52.120> like<00:07:52.599> you<00:07:52.759> are 00:07:52.990 --> 00:07:53.000 align:start position:0% sending a mors code right like you are 00:07:53.000 --> 00:07:54.629 align:start position:0% sending a mors code right like you are stuck<00:07:53.280> somewhere<00:07:54.039> and<00:07:54.159> you're<00:07:54.319> trying<00:07:54.520> to 00:07:54.629 --> 00:07:54.639 align:start position:0% stuck somewhere and you're trying to 00:07:54.639 --> 00:07:56.550 align:start position:0% stuck somewhere and you're trying to send<00:07:54.879> like<00:07:55.000> a<00:07:55.120> morse<00:07:55.479> code<00:07:55.759> through<00:07:56.360> to 00:07:56.550 --> 00:07:56.560 align:start position:0% send like a morse code through to 00:07:56.560 --> 00:07:58.350 align:start position:0% send like a morse code through to someone<00:07:57.039> so<00:07:57.240> that<00:07:57.400> they<00:07:57.520> can<00:07:57.680> come<00:07:57.800> and<00:07:57.960> rescue 00:07:58.350 --> 00:07:58.360 align:start position:0% someone so that they can come and rescue 00:07:58.360 --> 00:08:00.390 align:start position:0% someone so that they can come and rescue you<00:07:59.080> you<00:07:59.520> want<00:07:59.599> to<00:07:59.720> make<00:07:59.840> sure<00:08:00.039> they 00:08:00.390 --> 00:08:00.400 align:start position:0% you you want to make sure they 00:08:00.400 --> 00:08:01.950 align:start position:0% you you want to make sure they understand<00:08:00.520> your<00:08:00.680> Morse<00:08:01.039> code<00:08:01.599> otherwise 00:08:01.950 --> 00:08:01.960 align:start position:0% understand your Morse code otherwise 00:08:01.960 --> 00:08:04.149 align:start position:0% understand your Morse code otherwise you're<00:08:02.159> sending<00:08:02.560> signals<00:08:03.080> they<00:08:03.280> just<00:08:03.479> think 00:08:04.149 --> 00:08:04.159 align:start position:0% you're sending signals they just think 00:08:04.159 --> 00:08:05.869 align:start position:0% you're sending signals they just think it<00:08:04.319> is<00:08:04.479> like<00:08:04.639> a<00:08:04.720> faulty<00:08:05.120> bulb<00:08:05.479> or<00:08:05.599> something 00:08:05.869 --> 00:08:05.879 align:start position:0% it is like a faulty bulb or something 00:08:05.879 --> 00:08:08.390 align:start position:0% it is like a faulty bulb or something like<00:08:06.080> that<00:08:06.639> right<00:08:07.080> so<00:08:07.280> you<00:08:07.720> you<00:08:07.960> want<00:08:08.080> to<00:08:08.240> make 00:08:08.390 --> 00:08:08.400 align:start position:0% like that right so you you want to make 00:08:08.400 --> 00:08:11.469 align:start position:0% like that right so you you want to make sure<00:08:09.199> your<00:08:09.400> signal<00:08:10.319> can<00:08:10.479> be<00:08:10.680> understood<00:08:11.240> and 00:08:11.469 --> 00:08:11.479 align:start position:0% sure your signal can be understood and 00:08:11.479 --> 00:08:13.749 align:start position:0% sure your signal can be understood and interpreted<00:08:12.199> correctly<00:08:13.199> and<00:08:13.319> you<00:08:13.440> also<00:08:13.599> don't 00:08:13.749 --> 00:08:13.759 align:start position:0% interpreted correctly and you also don't 00:08:13.759 --> 00:08:15.070 align:start position:0% interpreted correctly and you also don't want<00:08:13.879> to<00:08:14.000> mean<00:08:14.319> situations<00:08:14.800> where<00:08:14.919> you're 00:08:15.070 --> 00:08:15.080 align:start position:0% want to mean situations where you're 00:08:15.080 --> 00:08:18.270 align:start position:0% want to mean situations where you're sending<00:08:15.479> something<00:08:15.800> like<00:08:16.360> hey<00:08:17.360> um<00:08:17.759> I<00:08:17.919> have<00:08:18.039> an 00:08:18.270 --> 00:08:18.280 align:start position:0% sending something like hey um I have an 00:08:18.280 --> 00:08:21.189 align:start position:0% sending something like hey um I have an apple<00:08:19.080> but<00:08:19.280> what<00:08:19.479> they<00:08:19.720> interpret<00:08:20.199> it<00:08:20.440> as<00:08:21.039> I 00:08:21.189 --> 00:08:21.199 align:start position:0% apple but what they interpret it as I 00:08:21.199 --> 00:08:24.070 align:start position:0% apple but what they interpret it as I have<00:08:21.319> a<00:08:21.479> bum<00:08:22.479> right<00:08:22.680> that's<00:08:22.960> that's<00:08:23.159> also<00:08:23.720> a<00:08:23.919> a 00:08:24.070 --> 00:08:24.080 align:start position:0% have a bum right that's that's also a a 00:08:24.080 --> 00:08:25.710 align:start position:0% have a bum right that's that's also a a bad<00:08:24.319> place<00:08:24.520> to<00:08:24.639> be<00:08:24.840> in<00:08:25.280> so<00:08:25.479> this 00:08:25.710 --> 00:08:25.720 align:start position:0% bad place to be in so this 00:08:25.720 --> 00:08:28.189 align:start position:0% bad place to be in so this interpretation<00:08:26.720> needs<00:08:26.960> to<00:08:27.080> be<00:08:27.280> on<00:08:27.520> point 00:08:28.189 --> 00:08:28.199 align:start position:0% interpretation needs to be on point 00:08:28.199 --> 00:08:29.830 align:start position:0% interpretation needs to be on point especially<00:08:28.680> in<00:08:28.879> this<00:08:29.039> context<00:08:29.520> because<00:08:29.720> we 00:08:29.830 --> 00:08:29.840 align:start position:0% especially in this context because we 00:08:29.840 --> 00:08:32.509 align:start position:0% especially in this context because we are<00:08:30.000> talking<00:08:30.319> about<00:08:30.599> financial<00:08:31.320> contracts<00:08:32.320> uh 00:08:32.509 --> 00:08:32.519 align:start position:0% are talking about financial contracts uh 00:08:32.519 --> 00:08:34.790 align:start position:0% are talking about financial contracts uh wrongful<00:08:33.399> interpretation<00:08:34.080> here<00:08:34.279> means<00:08:34.640> you 00:08:34.790 --> 00:08:34.800 align:start position:0% wrongful interpretation here means you 00:08:34.800 --> 00:08:35.670 align:start position:0% wrongful interpretation here means you lose 00:08:35.670 --> 00:08:35.680 align:start position:0% lose 00:08:35.680 --> 00:08:37.909 align:start position:0% lose money<00:08:36.680> so<00:08:36.880> this<00:08:37.000> is<00:08:37.120> the<00:08:37.240> first<00:08:37.560> thing<00:08:37.839> that 00:08:37.909 --> 00:08:37.919 align:start position:0% money so this is the first thing that 00:08:37.919 --> 00:08:39.790 align:start position:0% money so this is the first thing that you<00:08:38.080> think<00:08:38.279> about<00:08:38.479> as<00:08:38.599> a<00:08:38.680> filler<00:08:39.440> can<00:08:39.560> I 00:08:39.790 --> 00:08:39.800 align:start position:0% you think about as a filler can I 00:08:39.800 --> 00:08:44.230 align:start position:0% you think about as a filler can I interpret<00:08:40.360> this 00:08:44.230 --> 00:08:44.240 align:start position:0% 00:08:44.240 --> 00:08:46.550 align:start position:0% thing<00:08:45.240> okay<00:08:45.680> the<00:08:45.800> second<00:08:46.040> thing<00:08:46.160> you<00:08:46.320> think 00:08:46.550 --> 00:08:46.560 align:start position:0% thing okay the second thing you think 00:08:46.560 --> 00:08:49.430 align:start position:0% thing okay the second thing you think about<00:08:47.080> can<00:08:47.200> I<00:08:47.440> fulfill<00:08:48.440> meaning<00:08:48.839> if<00:08:48.959> the<00:08:49.120> user 00:08:49.430 --> 00:08:49.440 align:start position:0% about can I fulfill meaning if the user 00:08:49.440 --> 00:08:53.150 align:start position:0% about can I fulfill meaning if the user is<00:08:49.560> saying<00:08:50.040> hey<00:08:50.320> I<00:08:50.480> have<00:08:50.640> some<00:08:50.839> a<00:08:51.279> over<00:08:51.880> here<00:08:52.880> um 00:08:53.150 --> 00:08:53.160 align:start position:0% is saying hey I have some a over here um 00:08:53.160 --> 00:08:55.389 align:start position:0% is saying hey I have some a over here um if<00:08:53.279> the<00:08:53.399> user<00:08:53.680> is<00:08:53.800> saying<00:08:54.160> I<00:08:54.279> have<00:08:54.600> 100<00:08:54.839> a<00:08:55.200> over 00:08:55.389 --> 00:08:55.399 align:start position:0% if the user is saying I have 100 a over 00:08:55.399 --> 00:08:58.550 align:start position:0% if the user is saying I have 100 a over here<00:08:55.760> give<00:08:55.920> me<00:08:56.279> like<00:08:56.680> 200<00:08:56.920> a<00:08:57.279> on<00:08:57.440> this<00:08:57.600> chain 00:08:58.550 --> 00:08:58.560 align:start position:0% here give me like 200 a on this chain 00:08:58.560 --> 00:09:00.110 align:start position:0% here give me like 200 a on this chain this<00:08:58.680> is<00:08:58.839> something<00:08:59.160> that<00:08:59.279> is<00:08:59.519> simply<00:08:59.800> not 00:09:00.110 --> 00:09:00.120 align:start position:0% this is something that is simply not 00:09:00.120 --> 00:09:02.710 align:start position:0% this is something that is simply not possible<00:09:01.079> or<00:09:01.399> like<00:09:02.079> why<00:09:02.200> would<00:09:02.360> you<00:09:02.519> give 00:09:02.710 --> 00:09:02.720 align:start position:0% possible or like why would you give 00:09:02.720 --> 00:09:04.550 align:start position:0% possible or like why would you give anyone<00:09:03.040> free<00:09:03.240> money<00:09:03.880> unless<00:09:04.160> you're<00:09:04.360> getting 00:09:04.550 --> 00:09:04.560 align:start position:0% anyone free money unless you're getting 00:09:04.560 --> 00:09:07.389 align:start position:0% anyone free money unless you're getting more<00:09:04.760> free<00:09:04.959> money<00:09:05.839> down<00:09:06.000> the<00:09:06.160> lane<00:09:06.480> why<00:09:06.760> some 00:09:07.389 --> 00:09:07.399 align:start position:0% more free money down the lane why some 00:09:07.399 --> 00:09:10.269 align:start position:0% more free money down the lane why some airdrop<00:09:07.800> or<00:09:07.959> something<00:09:08.640> so<00:09:08.920> you<00:09:09.920> after<00:09:10.120> you 00:09:10.269 --> 00:09:10.279 align:start position:0% airdrop or something so you after you 00:09:10.279 --> 00:09:11.670 align:start position:0% airdrop or something so you after you interpret<00:09:10.760> you<00:09:10.880> just<00:09:11.000> make<00:09:11.160> sure<00:09:11.440> you<00:09:11.519> can 00:09:11.670 --> 00:09:11.680 align:start position:0% interpret you just make sure you can 00:09:11.680 --> 00:09:15.190 align:start position:0% interpret you just make sure you can fulfill<00:09:12.079> what<00:09:12.200> the<00:09:12.320> user<00:09:12.600> is<00:09:12.920> asking<00:09:13.440> for<00:09:14.440> um 00:09:15.190 --> 00:09:15.200 align:start position:0% fulfill what the user is asking for um 00:09:15.200 --> 00:09:17.269 align:start position:0% fulfill what the user is asking for um basically<00:09:15.600> sort<00:09:15.760> of<00:09:15.959> like<00:09:16.240> making<00:09:16.519> sure<00:09:16.880> you 00:09:17.269 --> 00:09:17.279 align:start position:0% basically sort of like making sure you 00:09:17.279 --> 00:09:18.750 align:start position:0% basically sort of like making sure you understand<00:09:17.399> the<00:09:17.519> terms<00:09:17.760> and<00:09:18.040> conditions<00:09:18.640> and 00:09:18.750 --> 00:09:18.760 align:start position:0% understand the terms and conditions and 00:09:18.760 --> 00:09:23.230 align:start position:0% understand the terms and conditions and you<00:09:18.880> are<00:09:19.160> like<00:09:19.760> opting<00:09:20.040> into 00:09:23.230 --> 00:09:23.240 align:start position:0% 00:09:23.240 --> 00:09:27.790 align:start position:0% it<00:09:24.240> all<00:09:24.640> right<00:09:25.640> so<00:09:25.920> once<00:09:26.240> you<00:09:26.480> interpret<00:09:27.399> you 00:09:27.790 --> 00:09:27.800 align:start position:0% it all right so once you interpret you 00:09:27.800 --> 00:09:29.389 align:start position:0% it all right so once you interpret you understand<00:09:27.920> the<00:09:28.040> terms<00:09:28.240> and<00:09:28.560> condition<00:09:29.160> now 00:09:29.389 --> 00:09:29.399 align:start position:0% understand the terms and condition now 00:09:29.399 --> 00:09:31.990 align:start position:0% understand the terms and condition now now<00:09:29.480> you<00:09:29.560> are<00:09:29.720> like<00:09:30.120> okay<00:09:31.120> uh<00:09:31.399> how<00:09:31.560> much<00:09:31.760> am<00:09:31.880> I 00:09:31.990 --> 00:09:32.000 align:start position:0% now you are like okay uh how much am I 00:09:32.000 --> 00:09:34.470 align:start position:0% now you are like okay uh how much am I going<00:09:32.160> to<00:09:32.320> make<00:09:33.079> on<00:09:33.320> this<00:09:33.480> thing<00:09:34.040> and<00:09:34.160> do<00:09:34.320> I 00:09:34.470 --> 00:09:34.480 align:start position:0% going to make on this thing and do I 00:09:34.480 --> 00:09:36.790 align:start position:0% going to make on this thing and do I participate<00:09:34.920> on<00:09:35.040> this<00:09:35.200> thing<00:09:35.360> or<00:09:35.519> not<00:09:36.079> so<00:09:36.640> now 00:09:36.790 --> 00:09:36.800 align:start position:0% participate on this thing or not so now 00:09:36.800 --> 00:09:39.150 align:start position:0% participate on this thing or not so now you<00:09:36.920> start<00:09:37.600> calculating<00:09:38.240> profit<00:09:38.680> loss<00:09:38.959> and 00:09:39.150 --> 00:09:39.160 align:start position:0% you start calculating profit loss and 00:09:39.160 --> 00:09:41.949 align:start position:0% you start calculating profit loss and all<00:09:39.320> of<00:09:39.480> those<00:09:39.680> things<00:09:40.279> so<00:09:40.519> this<00:09:40.600> is<00:09:40.839> like<00:09:41.079> how 00:09:41.949 --> 00:09:41.959 align:start position:0% all of those things so this is like how 00:09:41.959 --> 00:09:43.790 align:start position:0% all of those things so this is like how a<00:09:42.120> market<00:09:42.440> maker<00:09:42.760> or<00:09:42.880> a<00:09:42.959> filler<00:09:43.360> will<00:09:43.519> sort<00:09:43.640> of 00:09:43.790 --> 00:09:43.800 align:start position:0% a market maker or a filler will sort of 00:09:43.800 --> 00:09:45.550 align:start position:0% a market maker or a filler will sort of like<00:09:43.959> think<00:09:44.240> about<00:09:44.519> your<00:09:44.720> intent<00:09:45.200> as<00:09:45.399> they 00:09:45.550 --> 00:09:45.560 align:start position:0% like think about your intent as they 00:09:45.560 --> 00:09:47.190 align:start position:0% like think about your intent as they sort<00:09:45.720> of<00:09:45.839> like<00:09:45.959> flow<00:09:46.279> through<00:09:46.800> this<00:09:46.920> is<00:09:47.040> going 00:09:47.190 --> 00:09:47.200 align:start position:0% sort of like flow through this is going 00:09:47.200 --> 00:09:48.750 align:start position:0% sort of like flow through this is going to<00:09:47.320> be<00:09:47.480> like<00:09:47.640> super<00:09:47.920> important<00:09:48.279> as<00:09:48.399> we<00:09:48.560> go 00:09:48.750 --> 00:09:48.760 align:start position:0% to be like super important as we go 00:09:48.760 --> 00:09:51.949 align:start position:0% to be like super important as we go about<00:09:49.040> this<00:09:49.360> stuff 00:09:51.949 --> 00:09:51.959 align:start position:0% about this stuff 00:09:51.959 --> 00:09:55.150 align:start position:0% about this stuff so<00:09:52.959> I<00:09:53.079> think<00:09:53.640> um<00:09:54.040> if<00:09:54.160> you<00:09:54.480> if<00:09:54.560> you<00:09:54.680> think<00:09:54.920> about 00:09:55.150 --> 00:09:55.160 align:start position:0% so I think um if you if you think about 00:09:55.160 --> 00:09:57.110 align:start position:0% so I think um if you if you think about it<00:09:55.440> like<00:09:55.720> why<00:09:55.839> does<00:09:56.040> filler<00:09:56.399> fragmentation 00:09:57.110 --> 00:09:57.120 align:start position:0% it like why does filler fragmentation 00:09:57.120 --> 00:09:59.790 align:start position:0% it like why does filler fragmentation like<00:09:57.600> exist<00:09:57.920> on<00:09:58.040> a<00:09:58.200> on<00:09:58.320> a<00:09:58.480> on<00:09:58.560> a<00:09:58.680> deeper<00:09:59.000> level 00:09:59.790 --> 00:09:59.800 align:start position:0% like exist on a on a on a deeper level 00:09:59.800 --> 00:10:01.750 align:start position:0% like exist on a on a on a deeper level so<00:10:00.040> every<00:10:00.279> sort<00:10:00.440> of<00:10:00.600> like<00:10:00.720> order<00:10:01.079> or<00:10:01.240> intent<00:10:01.600> is 00:10:01.750 --> 00:10:01.760 align:start position:0% so every sort of like order or intent is 00:10:01.760 --> 00:10:03.269 align:start position:0% so every sort of like order or intent is basically<00:10:02.079> like<00:10:02.200> a<00:10:02.279> shared<00:10:02.680> language<00:10:03.040> between 00:10:03.269 --> 00:10:03.279 align:start position:0% basically like a shared language between 00:10:03.279 --> 00:10:05.829 align:start position:0% basically like a shared language between a<00:10:03.399> user<00:10:03.640> and<00:10:03.760> a<00:10:03.920> filler<00:10:04.920> how<00:10:05.040> many<00:10:05.279> languages 00:10:05.829 --> 00:10:05.839 align:start position:0% a user and a filler how many languages 00:10:05.839 --> 00:10:08.389 align:start position:0% a user and a filler how many languages do<00:10:06.079> people<00:10:06.279> in<00:10:06.440> this<00:10:06.560> room<00:10:06.839> know<00:10:07.839> I<00:10:07.920> think<00:10:08.279> I 00:10:08.389 --> 00:10:08.399 align:start position:0% do people in this room know I think I 00:10:08.399 --> 00:10:11.110 align:start position:0% do people in this room know I think I know<00:10:08.720> maybe<00:10:09.079> like<00:10:09.600> four<00:10:10.600> I<00:10:10.720> don't<00:10:10.959> think 00:10:11.110 --> 00:10:11.120 align:start position:0% know maybe like four I don't think 00:10:11.120 --> 00:10:15.030 align:start position:0% know maybe like four I don't think anyone<00:10:11.640> in<00:10:11.760> this<00:10:11.920> room<00:10:12.120> knows<00:10:12.760> above<00:10:13.440> 20<00:10:14.440> um<00:10:14.880> so 00:10:15.030 --> 00:10:15.040 align:start position:0% anyone in this room knows above 20 um so 00:10:15.040 --> 00:10:17.509 align:start position:0% anyone in this room knows above 20 um so I<00:10:15.120> think<00:10:15.240> it's<00:10:15.519> like<00:10:15.839> hard<00:10:16.160> for<00:10:16.360> us<00:10:16.480> to<00:10:16.720> like 00:10:17.509 --> 00:10:17.519 align:start position:0% I think it's like hard for us to like 00:10:17.519 --> 00:10:21.389 align:start position:0% I think it's like hard for us to like think<00:10:17.839> that<00:10:18.640> uh<00:10:18.760> fillers<00:10:19.160> will<00:10:19.360> know<00:10:20.000> 20<00:10:20.920> 25 00:10:21.389 --> 00:10:21.399 align:start position:0% think that uh fillers will know 20 25 00:10:21.399 --> 00:10:23.389 align:start position:0% think that uh fillers will know 20 25 different<00:10:21.800> like<00:10:22.120> intent<00:10:22.519> protocols<00:10:23.000> because 00:10:23.389 --> 00:10:23.399 align:start position:0% different like intent protocols because 00:10:23.399 --> 00:10:25.150 align:start position:0% different like intent protocols because those<00:10:23.560> are<00:10:23.720> also<00:10:23.920> sort<00:10:24.079> of<00:10:24.240> like<00:10:24.360> shared 00:10:25.150 --> 00:10:25.160 align:start position:0% those are also sort of like shared 00:10:25.160 --> 00:10:27.630 align:start position:0% those are also sort of like shared languages<00:10:26.160> um<00:10:26.399> and<00:10:26.640> as<00:10:26.760> I<00:10:26.959> mentioned<00:10:27.320> before 00:10:27.630 --> 00:10:27.640 align:start position:0% languages um and as I mentioned before 00:10:27.640 --> 00:10:29.630 align:start position:0% languages um and as I mentioned before right<00:10:27.760> these<00:10:27.880> are<00:10:28.120> like<00:10:28.279> Financial<00:10:28.800> contracts 00:10:29.630 --> 00:10:29.640 align:start position:0% right these are like Financial contracts 00:10:29.640 --> 00:10:31.750 align:start position:0% right these are like Financial contracts and<00:10:29.839> misunderstandings<00:10:30.839> have<00:10:31.040> a<00:10:31.240> financial 00:10:31.750 --> 00:10:31.760 align:start position:0% and misunderstandings have a financial 00:10:31.760 --> 00:10:34.470 align:start position:0% and misunderstandings have a financial cost<00:10:32.079> attached<00:10:32.440> to<00:10:32.560> it<00:10:33.120> if<00:10:33.279> you<00:10:33.880> sort<00:10:34.120> of<00:10:34.279> like 00:10:34.470 --> 00:10:34.480 align:start position:0% cost attached to it if you sort of like 00:10:34.480 --> 00:10:36.590 align:start position:0% cost attached to it if you sort of like assume<00:10:34.920> that<00:10:35.399> this<00:10:35.600> person<00:10:35.880> wanted<00:10:36.160> a<00:10:36.279> million 00:10:36.590 --> 00:10:36.600 align:start position:0% assume that this person wanted a million 00:10:36.600 --> 00:10:39.590 align:start position:0% assume that this person wanted a million dollars<00:10:37.440> but<00:10:37.560> you<00:10:37.680> send<00:10:38.200> $10<00:10:38.519> million<00:10:39.240> you<00:10:39.399> are 00:10:39.590 --> 00:10:39.600 align:start position:0% dollars but you send $10 million you are 00:10:39.600 --> 00:10:42.949 align:start position:0% dollars but you send $10 million you are now<00:10:39.800> down<00:10:40.160> $9<00:10:40.560> million<00:10:41.480> right<00:10:41.920> so<00:10:42.680> uh 00:10:42.949 --> 00:10:42.959 align:start position:0% now down $9 million right so uh 00:10:42.959 --> 00:10:44.590 align:start position:0% now down $9 million right so uh misunderstanding<00:10:43.600> here<00:10:43.800> has<00:10:43.920> a<00:10:44.040> financial 00:10:44.590 --> 00:10:44.600 align:start position:0% misunderstanding here has a financial 00:10:44.600 --> 00:10:46.509 align:start position:0% misunderstanding here has a financial cost<00:10:45.279> so<00:10:45.399> you<00:10:45.480> want<00:10:45.560> to<00:10:45.720> make<00:10:45.839> sure<00:10:46.120> you're 00:10:46.509 --> 00:10:46.519 align:start position:0% cost so you want to make sure you're 00:10:46.519 --> 00:10:48.710 align:start position:0% cost so you want to make sure you're interpreting<00:10:47.279> and<00:10:47.399> your<00:10:47.519> share<00:10:47.800> language<00:10:48.120> is 00:10:48.710 --> 00:10:48.720 align:start position:0% interpreting and your share language is 00:10:48.720 --> 00:10:52.710 align:start position:0% interpreting and your share language is tight<00:10:49.720> um<00:10:50.600> yeah<00:10:50.760> I<00:10:50.880> think<00:10:51.440> as<00:10:51.600> a<00:10:51.720> filler<00:10:52.560> in 00:10:52.710 --> 00:10:52.720 align:start position:0% tight um yeah I think as a filler in 00:10:52.720 --> 00:10:54.670 align:start position:0% tight um yeah I think as a filler in this<00:10:52.920> space<00:10:53.600> once<00:10:53.800> you<00:10:53.920> have<00:10:54.040> your<00:10:54.240> strategy 00:10:54.670 --> 00:10:54.680 align:start position:0% this space once you have your strategy 00:10:54.680 --> 00:10:56.389 align:start position:0% this space once you have your strategy once<00:10:54.839> you<00:10:54.959> have<00:10:55.120> your<00:10:55.320> Capital<00:10:55.880> you<00:10:56.040> spend 00:10:56.389 --> 00:10:56.399 align:start position:0% once you have your Capital you spend 00:10:56.399 --> 00:10:57.949 align:start position:0% once you have your Capital you spend most<00:10:56.680> amount<00:10:56.920> of<00:10:57.040> your<00:10:57.200> time<00:10:57.360> sort<00:10:57.560> of 00:10:57.949 --> 00:10:57.959 align:start position:0% most amount of your time sort of 00:10:57.959 --> 00:10:58.949 align:start position:0% most amount of your time sort of understanding<00:10:58.160> how<00:10:58.320> different<00:10:58.560> protocols 00:10:58.949 --> 00:10:58.959 align:start position:0% understanding how different protocols 00:10:58.959 --> 00:11:00.509 align:start position:0% understanding how different protocols work<00:10:59.279> and<00:10:59.360> how<00:10:59.480> you<00:10:59.600> integrate<00:10:59.959> with<00:11:00.120> them<00:11:00.320> and 00:11:00.509 --> 00:11:00.519 align:start position:0% work and how you integrate with them and 00:11:00.519 --> 00:11:01.670 align:start position:0% work and how you integrate with them and stuff<00:11:00.800> like 00:11:01.670 --> 00:11:01.680 align:start position:0% stuff like 00:11:01.680 --> 00:11:05.949 align:start position:0% stuff like that<00:11:02.680> um<00:11:03.519> now<00:11:03.760> we<00:11:03.880> are<00:11:04.040> finally<00:11:04.440> getting<00:11:04.959> to 00:11:05.949 --> 00:11:05.959 align:start position:0% that um now we are finally getting to 00:11:05.959 --> 00:11:08.670 align:start position:0% that um now we are finally getting to the<00:11:06.360> EIP<00:11:06.880> itself<00:11:07.560> right<00:11:08.040> if<00:11:08.120> you<00:11:08.279> think<00:11:08.480> about 00:11:08.670 --> 00:11:08.680 align:start position:0% the EIP itself right if you think about 00:11:08.680 --> 00:11:11.590 align:start position:0% the EIP itself right if you think about it<00:11:08.880> it<00:11:08.959> is<00:11:09.160> just<00:11:09.279> a<00:11:09.680> translator<00:11:10.680> everything<00:11:11.360> in 00:11:11.590 --> 00:11:11.600 align:start position:0% it it is just a translator everything in 00:11:11.600 --> 00:11:14.230 align:start position:0% it it is just a translator everything in sort<00:11:11.839> of<00:11:12.040> pink<00:11:12.360> is<00:11:12.519> standardized<00:11:13.079> by<00:11:13.200> the<00:11:13.320> EIP 00:11:14.230 --> 00:11:14.240 align:start position:0% sort of pink is standardized by the EIP 00:11:14.240 --> 00:11:16.110 align:start position:0% sort of pink is standardized by the EIP and<00:11:14.560> everything<00:11:14.880> in<00:11:15.040> green<00:11:15.399> is<00:11:15.519> sort<00:11:15.680> of<00:11:15.839> open 00:11:16.110 --> 00:11:16.120 align:start position:0% and everything in green is sort of open 00:11:16.120 --> 00:11:18.509 align:start position:0% and everything in green is sort of open for<00:11:16.440> developers<00:11:16.920> to<00:11:17.040> build<00:11:17.279> on<00:11:17.839> so<00:11:18.000> as<00:11:18.079> a<00:11:18.240> user 00:11:18.509 --> 00:11:18.519 align:start position:0% for developers to build on so as a user 00:11:18.519 --> 00:11:21.509 align:start position:0% for developers to build on so as a user you<00:11:18.639> send<00:11:18.880> a<00:11:19.040> cross<00:11:19.320> in<00:11:19.560> order<00:11:20.560> this<00:11:21.000> settler 00:11:21.509 --> 00:11:21.519 align:start position:0% you send a cross in order this settler 00:11:21.519 --> 00:11:23.990 align:start position:0% you send a cross in order this settler contract<00:11:21.959> it<00:11:22.079> sort<00:11:22.240> of<00:11:22.399> like<00:11:22.720> translates<00:11:23.720> it 00:11:23.990 --> 00:11:24.000 align:start position:0% contract it sort of like translates it 00:11:24.000 --> 00:11:26.389 align:start position:0% contract it sort of like translates it into<00:11:24.480> a<00:11:24.639> resolved<00:11:25.079> Crossing<00:11:25.519> order<00:11:26.079> which<00:11:26.200> is 00:11:26.389 --> 00:11:26.399 align:start position:0% into a resolved Crossing order which is 00:11:26.399 --> 00:11:28.389 align:start position:0% into a resolved Crossing order which is standardized<00:11:27.120> so<00:11:27.279> that<00:11:27.480> all<00:11:27.639> fillers<00:11:28.079> get<00:11:28.240> the 00:11:28.389 --> 00:11:28.399 align:start position:0% standardized so that all fillers get the 00:11:28.399 --> 00:11:30.590 align:start position:0% standardized so that all fillers get the same<00:11:28.639> resolved<00:11:29.000> cross<00:11:29.440> in<00:11:29.560> order<00:11:30.200> so<00:11:30.440> this 00:11:30.590 --> 00:11:30.600 align:start position:0% same resolved cross in order so this 00:11:30.600 --> 00:11:33.069 align:start position:0% same resolved cross in order so this thing<00:11:30.839> acts<00:11:31.120> like<00:11:31.240> a<00:11:31.440> translator<00:11:32.279> sort 00:11:33.069 --> 00:11:33.079 align:start position:0% thing acts like a translator sort 00:11:33.079 --> 00:11:36.190 align:start position:0% thing acts like a translator sort of<00:11:34.079> what's<00:11:34.320> inside<00:11:34.600> a<00:11:35.079> settlement<00:11:35.560> contract 00:11:36.190 --> 00:11:36.200 align:start position:0% of what's inside a settlement contract 00:11:36.200 --> 00:11:37.790 align:start position:0% of what's inside a settlement contract like<00:11:36.440> the<00:11:36.800> thing<00:11:36.959> in<00:11:37.040> the<00:11:37.160> middle<00:11:37.399> in<00:11:37.519> the<00:11:37.639> last 00:11:37.790 --> 00:11:37.800 align:start position:0% like the thing in the middle in the last 00:11:37.800 --> 00:11:41.590 align:start position:0% like the thing in the middle in the last slide<00:11:38.720> it<00:11:39.480> receives<00:11:39.639> a<00:11:39.760> cross<00:11:40.000> in<00:11:40.160> order<00:11:40.959> it<00:11:41.279> in 00:11:41.590 --> 00:11:41.600 align:start position:0% slide it receives a cross in order it in 00:11:41.600 --> 00:11:44.710 align:start position:0% slide it receives a cross in order it in it<00:11:42.000> sort<00:11:42.240> of<00:11:42.440> like<00:11:42.920> has<00:11:43.160> defined<00:11:44.079> interfaces 00:11:44.710 --> 00:11:44.720 align:start position:0% it sort of like has defined interfaces 00:11:44.720 --> 00:11:47.629 align:start position:0% it sort of like has defined interfaces to<00:11:45.440> receive<00:11:45.800> the<00:11:45.920> order<00:11:46.680> but<00:11:46.880> then<00:11:47.160> it's<00:11:47.399> open 00:11:47.629 --> 00:11:47.639 align:start position:0% to receive the order but then it's open 00:11:47.639 --> 00:11:49.509 align:start position:0% to receive the order but then it's open for<00:11:47.880> developers<00:11:48.360> to<00:11:48.519> interpret<00:11:48.920> it<00:11:49.320> however 00:11:49.509 --> 00:11:49.519 align:start position:0% for developers to interpret it however 00:11:49.519 --> 00:11:51.670 align:start position:0% for developers to interpret it however they<00:11:49.680> want<00:11:50.320> and<00:11:50.440> then<00:11:50.680> Dev<00:11:51.120> can<00:11:51.279> do<00:11:51.519> like 00:11:51.670 --> 00:11:51.680 align:start position:0% they want and then Dev can do like 00:11:51.680 --> 00:11:52.910 align:start position:0% they want and then Dev can do like whatever<00:11:52.000> they<00:11:52.120> want<00:11:52.320> in<00:11:52.399> the<00:11:52.519> settlement 00:11:52.910 --> 00:11:52.920 align:start position:0% whatever they want in the settlement 00:11:52.920 --> 00:11:55.870 align:start position:0% whatever they want in the settlement contract<00:11:53.760> and<00:11:53.920> then<00:11:54.120> they<00:11:54.240> sort<00:11:54.440> of<00:11:54.639> like<00:11:54.880> emit 00:11:55.870 --> 00:11:55.880 align:start position:0% contract and then they sort of like emit 00:11:55.880 --> 00:11:58.069 align:start position:0% contract and then they sort of like emit standardized<00:11:56.519> events<00:11:56.839> across<00:11:57.160> the<00:11:57.240> board 00:11:58.069 --> 00:11:58.079 align:start position:0% standardized events across the board 00:11:58.079 --> 00:12:00.430 align:start position:0% standardized events across the board right<00:11:58.839> uh<00:11:59.079> which<00:11:59.279> which<00:11:59.519> include<00:11:59.920> the<00:12:00.040> resolve 00:12:00.430 --> 00:12:00.440 align:start position:0% right uh which which include the resolve 00:12:00.440 --> 00:12:03.430 align:start position:0% right uh which which include the resolve cross<00:12:00.680> in<00:12:00.800> order<00:12:01.200> that<00:12:01.760> the<00:12:01.880> fillers<00:12:02.839> trust<00:12:03.240> as 00:12:03.430 --> 00:12:03.440 align:start position:0% cross in order that the fillers trust as 00:12:03.440 --> 00:12:05.670 align:start position:0% cross in order that the fillers trust as like<00:12:03.560> source<00:12:03.839> of<00:12:04.000> Truth 00:12:05.670 --> 00:12:05.680 align:start position:0% like source of Truth 00:12:05.680 --> 00:12:08.389 align:start position:0% like source of Truth almost<00:12:06.680> um<00:12:06.959> from<00:12:07.200> a<00:12:07.279> filler<00:12:07.800> point<00:12:08.000> of<00:12:08.120> view 00:12:08.389 --> 00:12:08.399 align:start position:0% almost um from a filler point of view 00:12:08.399 --> 00:12:10.829 align:start position:0% almost um from a filler point of view right<00:12:08.800> consider<00:12:09.200> this<00:12:09.360> intent<00:12:09.680> protocol<00:12:10.079> one 00:12:10.829 --> 00:12:10.839 align:start position:0% right consider this intent protocol one 00:12:10.839 --> 00:12:14.230 align:start position:0% right consider this intent protocol one that<00:12:11.000> is<00:12:11.680> 7<00:12:12.160> 7683<00:12:12.959> compatible<00:12:13.680> right<00:12:14.000> so<00:12:14.160> there 00:12:14.230 --> 00:12:14.240 align:start position:0% that is 7 7683 compatible right so there 00:12:14.240 --> 00:12:16.230 align:start position:0% that is 7 7683 compatible right so there is<00:12:14.360> a<00:12:14.519> crossan<00:12:14.839> order<00:12:15.079> that<00:12:15.279> goes<00:12:15.480> in<00:12:16.040> and<00:12:16.160> you 00:12:16.230 --> 00:12:16.240 align:start position:0% is a crossan order that goes in and you 00:12:16.240 --> 00:12:18.150 align:start position:0% is a crossan order that goes in and you can<00:12:16.360> see<00:12:16.519> a<00:12:16.639> result<00:12:16.959> cross<00:12:17.199> in<00:12:17.360> order<00:12:17.800> order<00:12:18.079> on 00:12:18.150 --> 00:12:18.160 align:start position:0% can see a result cross in order order on 00:12:18.160 --> 00:12:20.629 align:start position:0% can see a result cross in order order on the<00:12:18.279> other<00:12:18.519> side<00:12:18.800> that<00:12:19.120> exactly 00:12:20.629 --> 00:12:20.639 align:start position:0% the other side that exactly 00:12:20.639 --> 00:12:23.269 align:start position:0% the other side that exactly matches<00:12:21.639> now<00:12:22.000> I<00:12:22.160> built<00:12:22.519> another<00:12:22.880> intent 00:12:23.269 --> 00:12:23.279 align:start position:0% matches now I built another intent 00:12:23.279 --> 00:12:26.030 align:start position:0% matches now I built another intent protocol<00:12:23.720> that<00:12:23.839> is<00:12:23.920> also<00:12:24.160> 7683<00:12:25.040> compatible 00:12:26.030 --> 00:12:26.040 align:start position:0% protocol that is also 7683 compatible 00:12:26.040 --> 00:12:28.350 align:start position:0% protocol that is also 7683 compatible but<00:12:26.399> the<00:12:26.519> devs<00:12:26.920> did<00:12:27.120> something<00:12:27.399> on<00:12:27.600> this<00:12:27.760> one 00:12:28.350 --> 00:12:28.360 align:start position:0% but the devs did something on this one 00:12:28.360 --> 00:12:30.030 align:start position:0% but the devs did something on this one what<00:12:28.519> they<00:12:28.680> did<00:12:28.880> was 00:12:30.030 --> 00:12:30.040 align:start position:0% what they did was 00:12:30.040 --> 00:12:31.350 align:start position:0% what they did was now<00:12:30.240> if<00:12:30.320> you<00:12:30.440> look<00:12:30.560> at<00:12:30.680> the<00:12:30.800> cross<00:12:31.040> in<00:12:31.120> order 00:12:31.350 --> 00:12:31.360 align:start position:0% now if you look at the cross in order 00:12:31.360 --> 00:12:32.829 align:start position:0% now if you look at the cross in order and<00:12:31.480> the<00:12:31.560> result<00:12:31.880> cross<00:12:32.120> in<00:12:32.199> order<00:12:32.600> you<00:12:32.680> will 00:12:32.829 --> 00:12:32.839 align:start position:0% and the result cross in order you will 00:12:32.839 --> 00:12:35.069 align:start position:0% and the result cross in order you will notice<00:12:33.120> that<00:12:33.279> the<00:12:33.399> destination<00:12:33.839> chain<00:12:34.120> ID<00:12:34.959> has 00:12:35.069 --> 00:12:35.079 align:start position:0% notice that the destination chain ID has 00:12:35.079 --> 00:12:37.750 align:start position:0% notice that the destination chain ID has been<00:12:35.480> manipulated<00:12:36.480> so<00:12:37.199> in<00:12:37.320> the<00:12:37.399> crossing 00:12:37.750 --> 00:12:37.760 align:start position:0% been manipulated so in the crossing 00:12:37.760 --> 00:12:40.430 align:start position:0% been manipulated so in the crossing order<00:12:38.120> the<00:12:38.199> two<00:12:38.360> chain<00:12:38.600> ID<00:12:38.839> was<00:12:39.040> 137<00:12:40.040> versus<00:12:40.320> in 00:12:40.430 --> 00:12:40.440 align:start position:0% order the two chain ID was 137 versus in 00:12:40.440 --> 00:12:41.629 align:start position:0% order the two chain ID was 137 versus in the<00:12:40.560> result<00:12:40.880> Crossing<00:12:41.240> order<00:12:41.519> the 00:12:41.629 --> 00:12:41.639 align:start position:0% the result Crossing order the 00:12:41.639 --> 00:12:44.870 align:start position:0% the result Crossing order the destination<00:12:42.120> chain<00:12:42.519> is<00:12:43.120> 420<00:12:44.120> because<00:12:44.360> the<00:12:44.519> dev 00:12:44.870 --> 00:12:44.880 align:start position:0% destination chain is 420 because the dev 00:12:44.880 --> 00:12:46.310 align:start position:0% destination chain is 420 because the dev did<00:12:45.120> something<00:12:45.560> what<00:12:45.680> they<00:12:45.839> did<00:12:46.000> was<00:12:46.160> they 00:12:46.310 --> 00:12:46.320 align:start position:0% did something what they did was they 00:12:46.320 --> 00:12:49.470 align:start position:0% did something what they did was they interpreted<00:12:47.079> incorrectly<00:12:48.079> so<00:12:48.320> now<00:12:49.279> the 00:12:49.470 --> 00:12:49.480 align:start position:0% interpreted incorrectly so now the 00:12:49.480 --> 00:12:51.509 align:start position:0% interpreted incorrectly so now the filler<00:12:49.920> thinks<00:12:50.440> that<00:12:50.600> he's<00:12:50.800> supposed<00:12:51.120> to<00:12:51.240> fill 00:12:51.509 --> 00:12:51.519 align:start position:0% filler thinks that he's supposed to fill 00:12:51.519 --> 00:12:54.110 align:start position:0% filler thinks that he's supposed to fill on<00:12:51.680> chain<00:12:52.240> 420<00:12:53.240> but<00:12:53.480> actually<00:12:53.720> the<00:12:53.839> user 00:12:54.110 --> 00:12:54.120 align:start position:0% on chain 420 but actually the user 00:12:54.120 --> 00:12:57.629 align:start position:0% on chain 420 but actually the user wanted<00:12:54.399> funds<00:12:54.639> on<00:12:54.959> 137<00:12:55.959> so<00:12:56.199> now<00:12:57.079> the<00:12:57.160> filler<00:12:57.480> is 00:12:57.629 --> 00:12:57.639 align:start position:0% wanted funds on 137 so now the filler is 00:12:57.639 --> 00:13:00.030 align:start position:0% wanted funds on 137 so now the filler is in<00:12:58.079> in<00:12:58.199> a<00:12:58.360> in<00:12:58.440> a<00:12:58.600> tough<00:12:58.839> spot<00:12:59.440> even<00:12:59.680> if<00:12:59.800> he 00:13:00.030 --> 00:13:00.040 align:start position:0% in in a in a tough spot even if he 00:13:00.040 --> 00:13:01.629 align:start position:0% in in a in a tough spot even if he executes<00:13:00.519> the<00:13:00.680> intent<00:13:01.000> he<00:13:01.120> will<00:13:01.279> never<00:13:01.480> get 00:13:01.629 --> 00:13:01.639 align:start position:0% executes the intent he will never get 00:13:01.639 --> 00:13:04.430 align:start position:0% executes the intent he will never get fulfilled<00:13:02.279> or<00:13:02.560> never<00:13:02.760> get<00:13:02.920> his<00:13:03.079> money<00:13:03.360> back<00:13:04.279> uh 00:13:04.430 --> 00:13:04.440 align:start position:0% fulfilled or never get his money back uh 00:13:04.440 --> 00:13:07.350 align:start position:0% fulfilled or never get his money back uh this<00:13:04.560> is<00:13:04.880> basically<00:13:05.320> because<00:13:06.199> you<00:13:06.920> I<00:13:07.000> think 00:13:07.350 --> 00:13:07.360 align:start position:0% this is basically because you I think 00:13:07.360 --> 00:13:09.269 align:start position:0% this is basically because you I think the<00:13:07.639> the<00:13:07.760> protocol<00:13:08.120> is<00:13:08.279> like<00:13:08.399> too<00:13:08.600> generic<00:13:09.079> and 00:13:09.269 --> 00:13:09.279 align:start position:0% the the protocol is like too generic and 00:13:09.279 --> 00:13:11.590 align:start position:0% the the protocol is like too generic and gives<00:13:09.959> developers<00:13:10.639> or<00:13:10.839> like<00:13:11.000> this<00:13:11.160> settler 00:13:11.590 --> 00:13:11.600 align:start position:0% gives developers or like this settler 00:13:11.600 --> 00:13:13.990 align:start position:0% gives developers or like this settler contract<00:13:12.279> too<00:13:12.519> much<00:13:12.760> power<00:13:13.399> and<00:13:13.560> fillers 00:13:13.990 --> 00:13:14.000 align:start position:0% contract too much power and fillers 00:13:14.000 --> 00:13:16.550 align:start position:0% contract too much power and fillers don't<00:13:14.199> get<00:13:14.320> any<00:13:14.800> assurances<00:13:15.800> of<00:13:16.040> like<00:13:16.320> what 00:13:16.550 --> 00:13:16.560 align:start position:0% don't get any assurances of like what 00:13:16.560 --> 00:13:19.870 align:start position:0% don't get any assurances of like what exactly<00:13:16.959> can<00:13:17.240> happen<00:13:18.240> in<00:13:18.600> in<00:13:18.680> the<00:13:18.800> middle<00:13:19.120> over 00:13:19.870 --> 00:13:19.880 align:start position:0% exactly can happen in in the middle over 00:13:19.880 --> 00:13:23.069 align:start position:0% exactly can happen in in the middle over here<00:13:20.880> uh<00:13:21.000> so<00:13:21.880> yeah<00:13:22.160> the<00:13:22.320> the<00:13:22.440> core<00:13:22.639> issue<00:13:22.920> is 00:13:23.069 --> 00:13:23.079 align:start position:0% here uh so yeah the the core issue is 00:13:23.079 --> 00:13:24.949 align:start position:0% here uh so yeah the the core issue is fillers<00:13:23.440> can't<00:13:23.639> trust<00:13:23.959> data<00:13:24.279> from<00:13:24.519> like<00:13:24.720> these 00:13:24.949 --> 00:13:24.959 align:start position:0% fillers can't trust data from like these 00:13:24.959 --> 00:13:27.310 align:start position:0% fillers can't trust data from like these unauthenticated<00:13:25.839> contracts<00:13:26.839> they<00:13:27.000> have<00:13:27.120> to 00:13:27.310 --> 00:13:27.320 align:start position:0% unauthenticated contracts they have to 00:13:27.320 --> 00:13:29.150 align:start position:0% unauthenticated contracts they have to go<00:13:27.519> and<00:13:27.680> sort<00:13:27.880> of<00:13:28.000> like<00:13:28.120> audit<00:13:28.519> read<00:13:28.800> each<00:13:28.959> of 00:13:29.150 --> 00:13:29.160 align:start position:0% go and sort of like audit read each of 00:13:29.160 --> 00:13:31.350 align:start position:0% go and sort of like audit read each of of<00:13:29.240> these<00:13:29.399> settler<00:13:29.880> contracts<00:13:30.880> uh<00:13:31.040> these 00:13:31.350 --> 00:13:31.360 align:start position:0% of these settler contracts uh these 00:13:31.360 --> 00:13:33.150 align:start position:0% of these settler contracts uh these these<00:13:31.639> contracts<00:13:32.040> in<00:13:32.120> the<00:13:32.240> middle<00:13:32.839> these<00:13:32.959> are 00:13:33.150 --> 00:13:33.160 align:start position:0% these contracts in the middle these are 00:13:33.160 --> 00:13:35.470 align:start position:0% these contracts in the middle these are called<00:13:33.399> settler<00:13:33.800> contracts<00:13:34.199> in<00:13:34.320> the<00:13:34.480> ERC<00:13:35.360> they 00:13:35.470 --> 00:13:35.480 align:start position:0% called settler contracts in the ERC they 00:13:35.480 --> 00:13:36.990 align:start position:0% called settler contracts in the ERC they have<00:13:35.600> to<00:13:35.680> go<00:13:35.839> and<00:13:36.240> understand<00:13:36.440> each<00:13:36.639> of<00:13:36.800> them 00:13:36.990 --> 00:13:37.000 align:start position:0% have to go and understand each of them 00:13:37.000 --> 00:13:38.550 align:start position:0% have to go and understand each of them and<00:13:37.199> only<00:13:37.399> then<00:13:37.560> they<00:13:37.639> will<00:13:37.839> accept<00:13:38.120> data<00:13:38.360> from 00:13:38.550 --> 00:13:38.560 align:start position:0% and only then they will accept data from 00:13:38.560 --> 00:13:42.030 align:start position:0% and only then they will accept data from it<00:13:39.240> so<00:13:39.639> ideally<00:13:40.199> we<00:13:41.079> like<00:13:41.199> the<00:13:41.360> goal<00:13:41.600> was<00:13:41.800> to<00:13:41.920> be 00:13:42.030 --> 00:13:42.040 align:start position:0% it so ideally we like the goal was to be 00:13:42.040 --> 00:13:44.230 align:start position:0% it so ideally we like the goal was to be able<00:13:42.240> to<00:13:42.360> work<00:13:42.600> with<00:13:42.800> just<00:13:43.240> standardized 00:13:44.230 --> 00:13:44.240 align:start position:0% able to work with just standardized 00:13:44.240 --> 00:13:47.110 align:start position:0% able to work with just standardized resolved<00:13:44.720> orders<00:13:45.600> which<00:13:45.760> you<00:13:45.880> can<00:13:46.079> find<00:13:46.839> on 00:13:47.110 --> 00:13:47.120 align:start position:0% resolved orders which you can find on 00:13:47.120 --> 00:13:48.829 align:start position:0% resolved orders which you can find on that<00:13:47.360> bottom<00:13:47.800> there<00:13:48.000> resolved<00:13:48.440> cross<00:13:48.720> in 00:13:48.829 --> 00:13:48.839 align:start position:0% that bottom there resolved cross in 00:13:48.839 --> 00:13:50.910 align:start position:0% that bottom there resolved cross in order<00:13:49.440> idea<00:13:49.800> was<00:13:50.000> like<00:13:50.160> all<00:13:50.320> fillers<00:13:50.680> will<00:13:50.839> be 00:13:50.910 --> 00:13:50.920 align:start position:0% order idea was like all fillers will be 00:13:50.920 --> 00:13:53.749 align:start position:0% order idea was like all fillers will be able<00:13:51.079> to<00:13:51.199> work<00:13:51.440> with<00:13:51.600> this<00:13:52.480> but<00:13:52.880> not<00:13:53.199> really 00:13:53.749 --> 00:13:53.759 align:start position:0% able to work with this but not really 00:13:53.759 --> 00:13:55.590 align:start position:0% able to work with this but not really people<00:13:54.079> have<00:13:54.240> to<00:13:54.600> like<00:13:54.759> fillers<00:13:55.120> have<00:13:55.240> to 00:13:55.590 --> 00:13:55.600 align:start position:0% people have to like fillers have to 00:13:55.600 --> 00:13:57.550 align:start position:0% people have to like fillers have to understand<00:13:55.720> the<00:13:55.880> result<00:13:56.240> cross<00:13:56.519> in<00:13:56.639> order<00:13:57.440> as 00:13:57.550 --> 00:13:57.560 align:start position:0% understand the result cross in order as 00:13:57.560 --> 00:13:59.829 align:start position:0% understand the result cross in order as well<00:13:57.720> as<00:13:57.839> the<00:13:57.920> settler<00:13:58.360> contract<00:13:59.160> for<00:13:59.399> them<00:13:59.560> to 00:13:59.829 --> 00:13:59.839 align:start position:0% well as the settler contract for them to 00:13:59.839 --> 00:14:02.069 align:start position:0% well as the settler contract for them to actually<00:14:00.120> start<00:14:00.399> filling<00:14:00.800> this<00:14:01.000> stuff<00:14:01.880> right 00:14:02.069 --> 00:14:02.079 align:start position:0% actually start filling this stuff right 00:14:02.079 --> 00:14:04.710 align:start position:0% actually start filling this stuff right so<00:14:02.320> we<00:14:02.440> are<00:14:02.600> sort<00:14:02.800> of<00:14:02.959> like<00:14:03.240> again<00:14:03.920> in<00:14:04.120> our 00:14:04.710 --> 00:14:04.720 align:start position:0% so we are sort of like again in our 00:14:04.720 --> 00:14:06.470 align:start position:0% so we are sort of like again in our present<00:14:05.120> world<00:14:05.639> where<00:14:05.800> fillers<00:14:06.199> are 00:14:06.470 --> 00:14:06.480 align:start position:0% present world where fillers are 00:14:06.480 --> 00:14:08.910 align:start position:0% present world where fillers are fragmented<00:14:07.480> by<00:14:07.800> like<00:14:08.000> different<00:14:08.519> intent 00:14:08.910 --> 00:14:08.920 align:start position:0% fragmented by like different intent 00:14:08.920 --> 00:14:10.590 align:start position:0% fragmented by like different intent protocols<00:14:09.680> which<00:14:09.800> is<00:14:09.920> the<00:14:10.040> world<00:14:10.240> we<00:14:10.399> trying 00:14:10.590 --> 00:14:10.600 align:start position:0% protocols which is the world we trying 00:14:10.600 --> 00:14:11.310 align:start position:0% protocols which is the world we trying to 00:14:11.310 --> 00:14:11.320 align:start position:0% to 00:14:11.320 --> 00:14:13.710 align:start position:0% to avoid<00:14:12.320> so<00:14:12.480> I<00:14:12.560> think<00:14:12.800> like<00:14:13.240> uh<00:14:13.360> getting<00:14:13.560> to 00:14:13.710 --> 00:14:13.720 align:start position:0% avoid so I think like uh getting to 00:14:13.720 --> 00:14:15.470 align:start position:0% avoid so I think like uh getting to potential<00:14:14.079> Solutions<00:14:14.639> right<00:14:14.920> otherwise<00:14:15.320> I'm 00:14:15.470 --> 00:14:15.480 align:start position:0% potential Solutions right otherwise I'm 00:14:15.480 --> 00:14:16.910 align:start position:0% potential Solutions right otherwise I'm just<00:14:15.639> like<00:14:15.920> complaining<00:14:16.360> on<00:14:16.440> the<00:14:16.600> stage<00:14:16.800> for 00:14:16.910 --> 00:14:16.920 align:start position:0% just like complaining on the stage for 00:14:16.920 --> 00:14:19.189 align:start position:0% just like complaining on the stage for the<00:14:17.120> last<00:14:17.399> like<00:14:17.600> 15<00:14:17.959> minutes<00:14:18.800> uh<00:14:18.959> some 00:14:19.189 --> 00:14:19.199 align:start position:0% the last like 15 minutes uh some 00:14:19.199 --> 00:14:21.470 align:start position:0% the last like 15 minutes uh some potential<00:14:19.600> solutions<00:14:20.000> to<00:14:20.240> this<00:14:20.759> is<00:14:20.959> that<00:14:21.320> we 00:14:21.470 --> 00:14:21.480 align:start position:0% potential solutions to this is that we 00:14:21.480 --> 00:14:23.150 align:start position:0% potential solutions to this is that we sort<00:14:21.639> of<00:14:21.800> have<00:14:22.000> this<00:14:22.160> like<00:14:22.360> giant<00:14:22.680> black<00:14:22.920> boox 00:14:23.150 --> 00:14:23.160 align:start position:0% sort of have this like giant black boox 00:14:23.160 --> 00:14:25.030 align:start position:0% sort of have this like giant black boox in<00:14:23.240> the<00:14:23.360> middle<00:14:23.600> called<00:14:23.800> settler<00:14:24.240> contract<00:14:24.880> we 00:14:25.030 --> 00:14:25.040 align:start position:0% in the middle called settler contract we 00:14:25.040 --> 00:14:26.389 align:start position:0% in the middle called settler contract we sort<00:14:25.160> of<00:14:25.279> like<00:14:25.440> break<00:14:25.639> it<00:14:25.759> down<00:14:25.920> into<00:14:26.120> smaller 00:14:26.389 --> 00:14:26.399 align:start position:0% sort of like break it down into smaller 00:14:26.399 --> 00:14:29.550 align:start position:0% sort of like break it down into smaller modules<00:14:27.399> modules<00:14:27.839> that<00:14:28.040> provide<00:14:28.480> sort<00:14:28.680> of 00:14:29.550 --> 00:14:29.560 align:start position:0% modules modules that provide sort of 00:14:29.560 --> 00:14:33.389 align:start position:0% modules modules that provide sort of some<00:14:29.959> guarantees<00:14:30.440> to<00:14:30.680> fillers<00:14:32.079> on<00:14:33.079> whatever 00:14:33.389 --> 00:14:33.399 align:start position:0% some guarantees to fillers on whatever 00:14:33.399 --> 00:14:35.629 align:start position:0% some guarantees to fillers on whatever settlement<00:14:33.839> that<00:14:33.959> they<00:14:34.079> want<00:14:34.160> to<00:14:34.959> uh<00:14:35.199> operate 00:14:35.629 --> 00:14:35.639 align:start position:0% settlement that they want to uh operate 00:14:35.639 --> 00:14:37.509 align:start position:0% settlement that they want to uh operate with<00:14:36.040> right<00:14:36.360> so<00:14:36.480> we<00:14:36.600> sort<00:14:36.759> of<00:14:36.880> like<00:14:37.079> break<00:14:37.320> down 00:14:37.509 --> 00:14:37.519 align:start position:0% with right so we sort of like break down 00:14:37.519 --> 00:14:39.670 align:start position:0% with right so we sort of like break down this<00:14:37.720> like<00:14:38.000> big<00:14:38.279> giant<00:14:38.720> blackbox<00:14:39.360> that 00:14:39.670 --> 00:14:39.680 align:start position:0% this like big giant blackbox that 00:14:39.680 --> 00:14:42.069 align:start position:0% this like big giant blackbox that developers<00:14:40.360> can<00:14:40.519> do<00:14:40.759> anything<00:14:41.160> with<00:14:41.759> into 00:14:42.069 --> 00:14:42.079 align:start position:0% developers can do anything with into 00:14:42.079 --> 00:14:44.030 align:start position:0% developers can do anything with into smaller<00:14:42.560> standardized 00:14:44.030 --> 00:14:44.040 align:start position:0% smaller standardized 00:14:44.040 --> 00:14:47.110 align:start position:0% smaller standardized modules<00:14:45.040> um<00:14:45.920> one<00:14:46.120> such<00:14:46.399> module<00:14:46.759> could<00:14:46.920> be<00:14:47.000> a 00:14:47.110 --> 00:14:47.120 align:start position:0% modules um one such module could be a 00:14:47.120 --> 00:14:49.749 align:start position:0% modules um one such module could be a standard<00:14:47.440> escro<00:14:48.040> implementation<00:14:49.040> idea<00:14:49.399> is 00:14:49.749 --> 00:14:49.759 align:start position:0% standard escro implementation idea is 00:14:49.759 --> 00:14:51.389 align:start position:0% standard escro implementation idea is like<00:14:49.959> imagine<00:14:50.320> the<00:14:50.480> smart<00:14:50.759> contract<00:14:51.160> really 00:14:51.389 --> 00:14:51.399 align:start position:0% like imagine the smart contract really 00:14:51.399 --> 00:14:53.509 align:start position:0% like imagine the smart contract really really<00:14:51.600> simple<00:14:51.880> smart<00:14:52.199> contract<00:14:53.079> you<00:14:53.199> put<00:14:53.360> in 00:14:53.509 --> 00:14:53.519 align:start position:0% really simple smart contract you put in 00:14:53.519 --> 00:14:57.030 align:start position:0% really simple smart contract you put in funds<00:14:54.440> with<00:14:54.560> a<00:14:54.759> key<00:14:55.399> and<00:14:55.560> with<00:14:55.680> a<00:14:55.800> time<00:14:56.040> lock 00:14:57.030 --> 00:14:57.040 align:start position:0% funds with a key and with a time lock 00:14:57.040 --> 00:14:59.030 align:start position:0% funds with a key and with a time lock and<00:14:57.160> you<00:14:57.279> attach<00:14:57.519> an<00:14:57.680> oracle<00:14:58.079> with<00:14:58.199> it<00:14:58.720> now 00:14:59.030 --> 00:14:59.040 align:start position:0% and you attach an oracle with it now 00:14:59.040 --> 00:15:00.949 align:start position:0% and you attach an oracle with it now funds<00:14:59.279> can<00:14:59.399> leave<00:14:59.680> this<00:14:59.839> lockbox<00:15:00.600> either<00:15:00.839> when 00:15:00.949 --> 00:15:00.959 align:start position:0% funds can leave this lockbox either when 00:15:00.959 --> 00:15:03.350 align:start position:0% funds can leave this lockbox either when the<00:15:01.120> timeout<00:15:01.560> happens<00:15:02.240> or<00:15:02.440> when<00:15:02.600> the<00:15:02.720> Oracle 00:15:03.350 --> 00:15:03.360 align:start position:0% the timeout happens or when the Oracle 00:15:03.360 --> 00:15:06.430 align:start position:0% the timeout happens or when the Oracle asks<00:15:04.360> uh<00:15:04.600> to<00:15:04.800> sort<00:15:05.000> of<00:15:05.120> like<00:15:05.279> withdraw<00:15:06.120> so<00:15:06.279> your 00:15:06.430 --> 00:15:06.440 align:start position:0% asks uh to sort of like withdraw so your 00:15:06.440 --> 00:15:08.470 align:start position:0% asks uh to sort of like withdraw so your trust<00:15:06.680> model<00:15:07.040> as<00:15:07.160> a<00:15:07.279> user<00:15:07.519> is<00:15:07.680> like<00:15:07.920> very<00:15:08.120> well 00:15:08.470 --> 00:15:08.480 align:start position:0% trust model as a user is like very well 00:15:08.480 --> 00:15:12.030 align:start position:0% trust model as a user is like very well defined<00:15:09.480> and<00:15:10.040> as<00:15:10.160> a<00:15:10.560> filler<00:15:11.040> as<00:15:11.199> well<00:15:11.720> you<00:15:11.839> know 00:15:12.030 --> 00:15:12.040 align:start position:0% defined and as a filler as well you know 00:15:12.040 --> 00:15:14.030 align:start position:0% defined and as a filler as well you know if<00:15:12.160> the<00:15:12.240> funds<00:15:12.560> have<00:15:12.720> reached<00:15:13.040> the<00:15:13.160> lockbox 00:15:14.030 --> 00:15:14.040 align:start position:0% if the funds have reached the lockbox 00:15:14.040 --> 00:15:15.670 align:start position:0% if the funds have reached the lockbox they<00:15:14.160> are<00:15:14.279> going<00:15:14.440> to<00:15:14.519> be<00:15:14.639> unlocked<00:15:15.399> for<00:15:15.560> the 00:15:15.670 --> 00:15:15.680 align:start position:0% they are going to be unlocked for the 00:15:15.680 --> 00:15:17.790 align:start position:0% they are going to be unlocked for the user<00:15:15.920> in<00:15:16.079> 2<00:15:16.240> hours<00:15:16.720> but<00:15:16.880> you<00:15:16.959> can<00:15:17.160> unlock<00:15:17.560> them 00:15:17.790 --> 00:15:17.800 align:start position:0% user in 2 hours but you can unlock them 00:15:17.800 --> 00:15:20.670 align:start position:0% user in 2 hours but you can unlock them VI<00:15:18.040> the<00:15:18.120> Oracle<00:15:19.000> for<00:15:19.199> the<00:15:19.360> next<00:15:19.959> like<00:15:20.199> 2<00:15:20.399> hours 00:15:20.670 --> 00:15:20.680 align:start position:0% VI the Oracle for the next like 2 hours 00:15:20.680 --> 00:15:24.389 align:start position:0% VI the Oracle for the next like 2 hours or<00:15:20.920> like<00:15:21.160> whatever<00:15:21.440> the<00:15:21.639> time<00:15:22.399> uh<00:15:22.519> limit<00:15:23.000> is<00:15:24.000> um 00:15:24.389 --> 00:15:24.399 align:start position:0% or like whatever the time uh limit is um 00:15:24.399 --> 00:15:25.670 align:start position:0% or like whatever the time uh limit is um and<00:15:24.560> this<00:15:24.720> gives<00:15:24.880> you<00:15:25.040> like<00:15:25.199> really<00:15:25.480> strong 00:15:25.670 --> 00:15:25.680 align:start position:0% and this gives you like really strong 00:15:25.680 --> 00:15:27.749 align:start position:0% and this gives you like really strong guarantees<00:15:26.160> now<00:15:26.880> and<00:15:27.079> you<00:15:27.199> don't<00:15:27.440> have<00:15:27.560> to 00:15:27.749 --> 00:15:27.759 align:start position:0% guarantees now and you don't have to 00:15:27.759 --> 00:15:29.790 align:start position:0% guarantees now and you don't have to like<00:15:28.279> care<00:15:28.560> about<00:15:29.160> what<00:15:29.279> the<00:15:29.399> settlement 00:15:29.790 --> 00:15:29.800 align:start position:0% like care about what the settlement 00:15:29.800 --> 00:15:32.030 align:start position:0% like care about what the settlement contract<00:15:30.160> does<00:15:30.680> as<00:15:30.839> long<00:15:31.000> as<00:15:31.199> funds<00:15:31.600> reach<00:15:31.880> the 00:15:32.030 --> 00:15:32.040 align:start position:0% contract does as long as funds reach the 00:15:32.040 --> 00:15:33.790 align:start position:0% contract does as long as funds reach the lockbox<00:15:32.880> and<00:15:33.000> you<00:15:33.120> have<00:15:33.279> the<00:15:33.399> ability<00:15:33.680> to 00:15:33.790 --> 00:15:33.800 align:start position:0% lockbox and you have the ability to 00:15:33.800 --> 00:15:36.069 align:start position:0% lockbox and you have the ability to build<00:15:34.000> a<00:15:34.120> right<00:15:34.360> key<00:15:35.319> I'm<00:15:35.519> I'm<00:15:35.639> planning<00:15:35.920> to 00:15:36.069 --> 00:15:36.079 align:start position:0% build a right key I'm I'm planning to 00:15:36.079 --> 00:15:37.990 align:start position:0% build a right key I'm I'm planning to write<00:15:36.600> a<00:15:36.720> little<00:15:36.959> bit<00:15:37.160> more<00:15:37.319> about<00:15:37.560> this 00:15:37.990 --> 00:15:38.000 align:start position:0% write a little bit more about this 00:15:38.000 --> 00:15:40.150 align:start position:0% write a little bit more about this potentially<00:15:38.480> another<00:15:38.800> EIP<00:15:39.319> building<00:15:39.639> on<00:15:39.880> top 00:15:40.150 --> 00:15:40.160 align:start position:0% potentially another EIP building on top 00:15:40.160 --> 00:15:41.030 align:start position:0% potentially another EIP building on top top<00:15:40.319> of 00:15:41.030 --> 00:15:41.040 align:start position:0% top of 00:15:41.040 --> 00:15:43.829 align:start position:0% top of 7683<00:15:42.040> but<00:15:42.279> I<00:15:42.360> think<00:15:42.560> generally<00:15:43.440> what<00:15:43.560> I<00:15:43.639> wanted 00:15:43.829 --> 00:15:43.839 align:start position:0% 7683 but I think generally what I wanted 00:15:43.839 --> 00:15:46.189 align:start position:0% 7683 but I think generally what I wanted to<00:15:44.000> convey<00:15:44.360> with<00:15:44.519> this<00:15:45.360> entire<00:15:45.680> sort<00:15:45.839> of<00:15:46.000> like 00:15:46.189 --> 00:15:46.199 align:start position:0% to convey with this entire sort of like 00:15:46.199 --> 00:15:48.470 align:start position:0% to convey with this entire sort of like topic<00:15:46.560> was<00:15:47.440> uh<00:15:47.600> intents<00:15:47.959> are<00:15:48.079> going<00:15:48.240> to<00:15:48.319> be 00:15:48.470 --> 00:15:48.480 align:start position:0% topic was uh intents are going to be 00:15:48.480 --> 00:15:51.189 align:start position:0% topic was uh intents are going to be super<00:15:49.000> important<00:15:50.000> intents<00:15:50.639> are<00:15:50.800> going<00:15:50.959> to<00:15:51.079> be 00:15:51.189 --> 00:15:51.199 align:start position:0% super important intents are going to be 00:15:51.199 --> 00:15:53.670 align:start position:0% super important intents are going to be the<00:15:51.319> way<00:15:51.440> we<00:15:51.560> interact<00:15:51.920> on<00:15:52.199> chain<00:15:53.199> intents<00:15:53.560> are 00:15:53.670 --> 00:15:53.680 align:start position:0% the way we interact on chain intents are 00:15:53.680 --> 00:15:54.990 align:start position:0% the way we interact on chain intents are going<00:15:53.839> to<00:15:53.920> be<00:15:54.040> the<00:15:54.199> thing<00:15:54.399> that<00:15:54.519> you<00:15:54.600> see<00:15:54.880> on 00:15:54.990 --> 00:15:55.000 align:start position:0% going to be the thing that you see on 00:15:55.000 --> 00:15:57.110 align:start position:0% going to be the thing that you see on your<00:15:55.160> metam<00:15:55.480> mask<00:15:56.079> when<00:15:56.199> you<00:15:56.399> sort<00:15:56.560> of<00:15:56.759> like<00:15:56.959> go 00:15:57.110 --> 00:15:57.120 align:start position:0% your metam mask when you sort of like go 00:15:57.120 --> 00:15:58.990 align:start position:0% your metam mask when you sort of like go and<00:15:57.279> sign<00:15:57.600> something<00:15:58.319> so<00:15:58.440> it's<00:15:58.560> super 00:15:58.990 --> 00:15:59.000 align:start position:0% and sign something so it's super 00:15:59.000 --> 00:16:00.189 align:start position:0% and sign something so it's super important<00:15:59.319> for<00:15:59.440> us<00:15:59.560> to<00:15:59.680> sort<00:15:59.839> of<00:16:00.000> have<00:16:00.079> a 00:16:00.189 --> 00:16:00.199 align:start position:0% important for us to sort of have a 00:16:00.199 --> 00:16:02.309 align:start position:0% important for us to sort of have a shared<00:16:00.519> language<00:16:00.880> around<00:16:01.079> it<00:16:01.800> and<00:16:01.959> for<00:16:02.199> that 00:16:02.309 --> 00:16:02.319 align:start position:0% shared language around it and for that 00:16:02.319 --> 00:16:04.710 align:start position:0% shared language around it and for that shared<00:16:02.639> language<00:16:02.920> to<00:16:03.040> be<00:16:03.399> accurate<00:16:04.399> um<00:16:04.560> I'll 00:16:04.710 --> 00:16:04.720 align:start position:0% shared language to be accurate um I'll 00:16:04.720 --> 00:16:06.350 align:start position:0% shared language to be accurate um I'll be<00:16:04.880> collaborating<00:16:05.680> with<00:16:05.800> a<00:16:05.920> bunch<00:16:06.079> of<00:16:06.199> people 00:16:06.350 --> 00:16:06.360 align:start position:0% be collaborating with a bunch of people 00:16:06.360 --> 00:16:08.829 align:start position:0% be collaborating with a bunch of people in<00:16:06.480> the<00:16:06.639> space<00:16:07.120> find<00:16:07.360> me<00:16:07.519> elsewhere<00:16:08.319> and<00:16:08.600> super 00:16:08.829 --> 00:16:08.839 align:start position:0% in the space find me elsewhere and super 00:16:08.839 --> 00:16:10.590 align:start position:0% in the space find me elsewhere and super happy<00:16:09.000> to<00:16:09.120> chat<00:16:09.360> about<00:16:09.560> it<00:16:10.079> but<00:16:10.199> yeah<00:16:10.399> that's 00:16:10.590 --> 00:16:10.600 align:start position:0% happy to chat about it but yeah that's 00:16:10.600 --> 00:16:15.269 align:start position:0% happy to chat about it but yeah that's basically<00:16:11.399> uh<00:16:11.560> it<00:16:12.120> thank<00:16:12.279> you<00:16:12.399> so 00:16:15.269 --> 00:16:15.279 align:start position:0% 00:16:15.279 --> 00:16:18.710 align:start position:0% much<00:16:16.279> good<00:16:16.560> stuff<00:16:16.920> good<00:16:17.120> stuff<00:16:17.399> by<00:16:17.639> Bob<00:16:18.279> so<00:16:18.560> we 00:16:18.710 --> 00:16:18.720 align:start position:0% much good stuff good stuff by Bob so we 00:16:18.720 --> 00:16:20.350 align:start position:0% much good stuff good stuff by Bob so we got<00:16:18.839> a<00:16:18.920> few<00:16:19.160> questions<00:16:19.680> if<00:16:19.759> you<00:16:19.880> want<00:16:20.000> to<00:16:20.160> ask 00:16:20.350 --> 00:16:20.360 align:start position:0% got a few questions if you want to ask 00:16:20.360 --> 00:16:22.590 align:start position:0% got a few questions if you want to ask more<00:16:20.600> questions<00:16:20.959> you<00:16:21.079> can<00:16:21.199> scan<00:16:21.440> the<00:16:21.560> QR<00:16:22.360> send 00:16:22.590 --> 00:16:22.600 align:start position:0% more questions you can scan the QR send 00:16:22.600 --> 00:16:24.910 align:start position:0% more questions you can scan the QR send them<00:16:22.800> up<00:16:23.040> and<00:16:23.240> they<00:16:23.360> will<00:16:23.839> um<00:16:24.000> show<00:16:24.240> up 00:16:24.910 --> 00:16:24.920 align:start position:0% them up and they will um show up 00:16:24.920 --> 00:16:27.670 align:start position:0% them up and they will um show up automatically<00:16:25.920> um<00:16:26.120> but<00:16:26.240> the<00:16:26.399> first<00:16:26.680> question 00:16:27.670 --> 00:16:27.680 align:start position:0% automatically um but the first question 00:16:27.680 --> 00:16:29.949 align:start position:0% automatically um but the first question uh<00:16:27.800> that'll<00:16:28.079> come<00:16:28.240> up<00:16:28.399> slowly<00:16:29.199> uh<00:16:29.639> on<00:16:29.839> the 00:16:29.949 --> 00:16:29.959 align:start position:0% uh that'll come up slowly uh on the 00:16:29.959 --> 00:16:31.990 align:start position:0% uh that'll come up slowly uh on the screen<00:16:30.920> is<00:16:31.079> to<00:16:31.240> ask<00:16:31.399> is<00:16:31.600> that<00:16:31.759> should 00:16:31.990 --> 00:16:32.000 align:start position:0% screen is to ask is that should 00:16:32.000 --> 00:16:34.110 align:start position:0% screen is to ask is that should cross-chain<00:16:32.519> intents<00:16:33.240> more<00:16:33.519> explicitly 00:16:34.110 --> 00:16:34.120 align:start position:0% cross-chain intents more explicitly 00:16:34.120 --> 00:16:37.189 align:start position:0% cross-chain intents more explicitly include<00:16:34.600> execution<00:16:35.160> of<00:16:35.440> arbitrary<00:16:36.120> call<00:16:36.440> data 00:16:37.189 --> 00:16:37.199 align:start position:0% include execution of arbitrary call data 00:16:37.199 --> 00:16:38.870 align:start position:0% include execution of arbitrary call data on<00:16:37.360> the<00:16:37.680> receiving<00:16:37.880> chain<00:16:38.279> on<00:16:38.399> the<00:16:38.519> level<00:16:38.759> of 00:16:38.870 --> 00:16:38.880 align:start position:0% on the receiving chain on the level of 00:16:38.880 --> 00:16:42.269 align:start position:0% on the receiving chain on the level of the<00:16:39.000> ERC 00:16:42.269 --> 00:16:42.279 align:start position:0% 00:16:42.279 --> 00:16:46.030 align:start position:0% spec<00:16:43.279> I<00:16:43.399> think<00:16:43.720> like<00:16:44.079> highly<00:16:44.839> debatable<00:16:45.839> um 00:16:46.030 --> 00:16:46.040 align:start position:0% spec I think like highly debatable um 00:16:46.040 --> 00:16:47.870 align:start position:0% spec I think like highly debatable um and<00:16:46.199> we<00:16:46.319> should<00:16:46.800> sort<00:16:47.000> of<00:16:47.160> like<00:16:47.319> debate<00:16:47.680> about 00:16:47.870 --> 00:16:47.880 align:start position:0% and we should sort of like debate about 00:16:47.880 --> 00:16:50.870 align:start position:0% and we should sort of like debate about it<00:16:48.720> um<00:16:49.079> I<00:16:49.199> think<00:16:49.759> this<00:16:49.959> as<00:16:50.079> a<00:16:50.199> use<00:16:50.600> case 00:16:50.870 --> 00:16:50.880 align:start position:0% it um I think this as a use case 00:16:50.880 --> 00:16:54.910 align:start position:0% it um I think this as a use case generally<00:16:51.240> makes<00:16:51.759> sense<00:16:53.160> um<00:16:54.160> I<00:16:54.279> would<00:16:54.639> I<00:16:54.720> would 00:16:54.910 --> 00:16:54.920 align:start position:0% generally makes sense um I would I would 00:16:54.920 --> 00:16:57.030 align:start position:0% generally makes sense um I would I would be<00:16:55.040> in<00:16:55.240> favor<00:16:56.000> but<00:16:56.199> I<00:16:56.279> think<00:16:56.440> there<00:16:56.560> are 00:16:57.030 --> 00:16:57.040 align:start position:0% be in favor but I think there are 00:16:57.040 --> 00:16:59.590 align:start position:0% be in favor but I think there are Arguments<00:16:57.480> for<00:16:57.639> not<00:16:57.800> doing<00:16:58.040> it<00:16:58.240> as<00:16:58.440> well<00:16:58.959> so<00:16:59.480> I 00:16:59.590 --> 00:16:59.600 align:start position:0% Arguments for not doing it as well so I 00:16:59.600 --> 00:17:01.829 align:start position:0% Arguments for not doing it as well so I don't<00:16:59.800> have<00:16:59.920> a<00:17:00.120> super<00:17:00.519> strong 00:17:01.829 --> 00:17:01.839 align:start position:0% don't have a super strong 00:17:01.839 --> 00:17:05.309 align:start position:0% don't have a super strong opinion<00:17:02.839> okay<00:17:03.480> next<00:17:03.839> question<00:17:04.839> can<00:17:05.000> we<00:17:05.120> ever 00:17:05.309 --> 00:17:05.319 align:start position:0% opinion okay next question can we ever 00:17:05.319 --> 00:17:06.949 align:start position:0% opinion okay next question can we ever move<00:17:05.559> away<00:17:05.799> from<00:17:06.000> the<00:17:06.160> reputation<00:17:06.640> based 00:17:06.949 --> 00:17:06.959 align:start position:0% move away from the reputation based 00:17:06.959 --> 00:17:09.590 align:start position:0% move away from the reputation based system<00:17:07.240> for<00:17:07.400> solvers<00:17:07.880> fillers<00:17:08.799> do<00:17:09.000> a<00:17:09.199> cross 00:17:09.590 --> 00:17:09.600 align:start position:0% system for solvers fillers do a cross 00:17:09.600 --> 00:17:11.990 align:start position:0% system for solvers fillers do a cross socket<00:17:09.959> Etc<00:17:10.839> currently<00:17:11.319> actually<00:17:11.600> slash 00:17:11.990 --> 00:17:12.000 align:start position:0% socket Etc currently actually slash 00:17:12.000 --> 00:17:14.069 align:start position:0% socket Etc currently actually slash their<00:17:12.160> fillers<00:17:12.559> or<00:17:12.760> punish 00:17:14.069 --> 00:17:14.079 align:start position:0% their fillers or punish 00:17:14.079 --> 00:17:16.309 align:start position:0% their fillers or punish them<00:17:15.079> I<00:17:15.160> think<00:17:15.319> the<00:17:15.480> cool<00:17:15.679> thing<00:17:15.880> about<00:17:16.120> this 00:17:16.309 --> 00:17:16.319 align:start position:0% them I think the cool thing about this 00:17:16.319 --> 00:17:19.350 align:start position:0% them I think the cool thing about this stuff<00:17:16.959> is<00:17:17.240> that<00:17:17.439> it's<00:17:17.760> quite<00:17:18.280> different<00:17:18.760> from 00:17:19.350 --> 00:17:19.360 align:start position:0% stuff is that it's quite different from 00:17:19.360 --> 00:17:21.470 align:start position:0% stuff is that it's quite different from all<00:17:19.520> the<00:17:19.679> consensus<00:17:20.199> based<00:17:20.520> models<00:17:21.000> that<00:17:21.160> we 00:17:21.470 --> 00:17:21.480 align:start position:0% all the consensus based models that we 00:17:21.480 --> 00:17:24.350 align:start position:0% all the consensus based models that we have<00:17:21.640> seen<00:17:21.959> in<00:17:22.160> inter<00:17:23.039> before<00:17:23.600> how<00:17:23.760> INR<00:17:24.199> used 00:17:24.350 --> 00:17:24.360 align:start position:0% have seen in inter before how INR used 00:17:24.360 --> 00:17:27.630 align:start position:0% have seen in inter before how INR used to<00:17:24.480> work<00:17:24.720> before<00:17:25.160> was<00:17:25.799> you<00:17:25.959> would<00:17:26.319> send<00:17:27.280> money 00:17:27.630 --> 00:17:27.640 align:start position:0% to work before was you would send money 00:17:27.640 --> 00:17:29.750 align:start position:0% to work before was you would send money into<00:17:27.919> a<00:17:28.079> smart<00:17:28.360> contract<00:17:29.080> you<00:17:29.240> would<00:17:29.480> have<00:17:29.640> a 00:17:29.750 --> 00:17:29.760 align:start position:0% into a smart contract you would have a 00:17:29.760 --> 00:17:32.150 align:start position:0% into a smart contract you would have a bunch<00:17:29.960> of<00:17:30.320> validators<00:17:31.320> and<00:17:31.480> those<00:17:31.640> validators 00:17:32.150 --> 00:17:32.160 align:start position:0% bunch of validators and those validators 00:17:32.160 --> 00:17:35.070 align:start position:0% bunch of validators and those validators would<00:17:32.320> be<00:17:32.440> your<00:17:32.679> truth<00:17:33.080> Oracle<00:17:33.880> in<00:17:34.080> some<00:17:34.360> sense 00:17:35.070 --> 00:17:35.080 align:start position:0% would be your truth Oracle in some sense 00:17:35.080 --> 00:17:36.390 align:start position:0% would be your truth Oracle in some sense and<00:17:35.240> then<00:17:35.400> they<00:17:35.520> would<00:17:35.760> give<00:17:35.880> you<00:17:36.000> funds<00:17:36.280> on 00:17:36.390 --> 00:17:36.400 align:start position:0% and then they would give you funds on 00:17:36.400 --> 00:17:38.590 align:start position:0% and then they would give you funds on the<00:17:36.559> destination<00:17:37.200> so<00:17:37.360> you<00:17:37.440> would<00:17:37.679> trust<00:17:38.400> this 00:17:38.590 --> 00:17:38.600 align:start position:0% the destination so you would trust this 00:17:38.600 --> 00:17:41.310 align:start position:0% the destination so you would trust this consensus<00:17:39.320> or<00:17:39.640> the<00:17:39.840> this<00:17:39.960> like<00:17:40.160> Valor<00:17:40.640> set<00:17:41.120> to 00:17:41.310 --> 00:17:41.320 align:start position:0% consensus or the this like Valor set to 00:17:41.320 --> 00:17:43.870 align:start position:0% consensus or the this like Valor set to give<00:17:41.440> you<00:17:41.600> funds<00:17:41.880> on<00:17:42.240> destination<00:17:43.240> and<00:17:43.600> that's 00:17:43.870 --> 00:17:43.880 align:start position:0% give you funds on destination and that's 00:17:43.880 --> 00:17:45.710 align:start position:0% give you funds on destination and that's when<00:17:44.320> like<00:17:44.440> slashing<00:17:44.960> and<00:17:45.120> staking<00:17:45.480> all<00:17:45.600> of 00:17:45.710 --> 00:17:45.720 align:start position:0% when like slashing and staking all of 00:17:45.720 --> 00:17:47.430 align:start position:0% when like slashing and staking all of that<00:17:45.880> became<00:17:46.160> important<00:17:46.679> because<00:17:47.000> if<00:17:47.160> not 00:17:47.430 --> 00:17:47.440 align:start position:0% that became important because if not 00:17:47.440 --> 00:17:50.230 align:start position:0% that became important because if not they<00:17:47.559> would<00:17:47.760> run<00:17:48.039> away<00:17:48.240> with<00:17:48.360> your<00:17:48.600> funds<00:17:49.600> but 00:17:50.230 --> 00:17:50.240 align:start position:0% they would run away with your funds but 00:17:50.240 --> 00:17:52.029 align:start position:0% they would run away with your funds but why<00:17:50.440> this<00:17:50.559> thing<00:17:50.720> is<00:17:50.919> cool<00:17:51.320> why<00:17:51.520> in<00:17:51.919> why 00:17:52.029 --> 00:17:52.039 align:start position:0% why this thing is cool why in why 00:17:52.039 --> 00:17:53.310 align:start position:0% why this thing is cool why in why intents<00:17:52.360> are<00:17:52.520> cool<00:17:52.720> is<00:17:52.880> that<00:17:53.000> you<00:17:53.080> don't<00:17:53.240> have 00:17:53.310 --> 00:17:53.320 align:start position:0% intents are cool is that you don't have 00:17:53.320 --> 00:17:55.270 align:start position:0% intents are cool is that you don't have to<00:17:53.440> trust<00:17:53.640> the<00:17:53.720> validator<00:17:54.120> set<00:17:54.320> anymore<00:17:55.120> and 00:17:55.270 --> 00:17:55.280 align:start position:0% to trust the validator set anymore and 00:17:55.280 --> 00:17:57.950 align:start position:0% to trust the validator set anymore and there<00:17:55.400> is<00:17:55.559> no<00:17:55.760> need<00:17:56.039> for<00:17:56.360> like<00:17:56.880> uh<00:17:57.000> slashing<00:17:57.679> or 00:17:57.950 --> 00:17:57.960 align:start position:0% there is no need for like uh slashing or 00:17:57.960 --> 00:17:59.789 align:start position:0% there is no need for like uh slashing or anything<00:17:58.320> like<00:17:58.480> that<00:17:59.039> you<00:17:59.320> you<00:17:59.440> send<00:17:59.679> your 00:17:59.789 --> 00:17:59.799 align:start position:0% anything like that you you send your 00:17:59.799 --> 00:18:01.830 align:start position:0% anything like that you you send your funds<00:18:00.600> they<00:18:00.720> will<00:18:00.919> either<00:18:01.159> get<00:18:01.280> fulfilled<00:18:01.720> in 00:18:01.830 --> 00:18:01.840 align:start position:0% funds they will either get fulfilled in 00:18:01.840 --> 00:18:03.430 align:start position:0% funds they will either get fulfilled in the<00:18:01.919> next<00:18:02.120> two<00:18:02.280> hours<00:18:02.559> or<00:18:02.720> you'll<00:18:02.960> simply<00:18:03.320> get 00:18:03.430 --> 00:18:03.440 align:start position:0% the next two hours or you'll simply get 00:18:03.440 --> 00:18:05.430 align:start position:0% the next two hours or you'll simply get your<00:18:03.559> funds<00:18:03.919> back<00:18:04.400> and<00:18:04.559> this<00:18:04.679> is<00:18:04.919> assured<00:18:05.320> by 00:18:05.430 --> 00:18:05.440 align:start position:0% your funds back and this is assured by 00:18:05.440 --> 00:18:07.990 align:start position:0% your funds back and this is assured by smart<00:18:05.760> contracts<00:18:06.200> onchain<00:18:07.200> so<00:18:07.400> it's<00:18:07.679> pretty 00:18:07.990 --> 00:18:08.000 align:start position:0% smart contracts onchain so it's pretty 00:18:08.000 --> 00:18:10.190 align:start position:0% smart contracts onchain so it's pretty pretty<00:18:08.240> cool<00:18:08.440> in<00:18:08.600> that<00:18:08.760> General 00:18:10.190 --> 00:18:10.200 align:start position:0% pretty cool in that General 00:18:10.200 --> 00:18:13.190 align:start position:0% pretty cool in that General sense<00:18:11.200> okay<00:18:12.000> so<00:18:12.240> is<00:18:12.360> it<00:18:12.520> not<00:18:12.760> possible<00:18:13.039> to 00:18:13.190 --> 00:18:13.200 align:start position:0% sense okay so is it not possible to 00:18:13.200 --> 00:18:15.549 align:start position:0% sense okay so is it not possible to create<00:18:13.679> the<00:18:14.440> translation<00:18:15.080> code<00:18:15.320> for<00:18:15.440> the 00:18:15.549 --> 00:18:15.559 align:start position:0% create the translation code for the 00:18:15.559 --> 00:18:18.110 align:start position:0% create the translation code for the different<00:18:15.840> intent<00:18:16.200> protocol 00:18:18.110 --> 00:18:18.120 align:start position:0% different intent protocol 00:18:18.120 --> 00:18:22.350 align:start position:0% different intent protocol languages<00:18:19.120> I<00:18:19.200> am<00:18:19.760> I<00:18:19.840> am<00:18:20.000> bearish<00:18:20.360> on<00:18:20.679> it<00:18:21.679> um<00:18:22.280> I 00:18:22.350 --> 00:18:22.360 align:start position:0% languages I am I am bearish on it um I 00:18:22.360 --> 00:18:24.149 align:start position:0% languages I am I am bearish on it um I feel<00:18:22.640> like<00:18:22.919> standardization<00:18:23.679> in<00:18:23.840> this<00:18:24.039> like 00:18:24.149 --> 00:18:24.159 align:start position:0% feel like standardization in this like 00:18:24.159 --> 00:18:26.110 align:start position:0% feel like standardization in this like intent<00:18:24.600> world<00:18:24.840> needs<00:18:25.039> to<00:18:25.240> happen<00:18:25.559> like<00:18:25.799> bottom 00:18:26.110 --> 00:18:26.120 align:start position:0% intent world needs to happen like bottom 00:18:26.120 --> 00:18:28.110 align:start position:0% intent world needs to happen like bottom up<00:18:26.400> rather<00:18:26.640> than<00:18:26.799> top<00:18:27.120> down<00:18:27.720> because<00:18:27.919> the 00:18:28.110 --> 00:18:28.120 align:start position:0% up rather than top down because the 00:18:28.120 --> 00:18:30.310 align:start position:0% up rather than top down because the application<00:18:28.799> SP<00:18:28.960> is<00:18:29.200> like<00:18:29.520> as<00:18:29.760> wide<00:18:30.039> as 00:18:30.310 --> 00:18:30.320 align:start position:0% application SP is like as wide as 00:18:30.320 --> 00:18:33.230 align:start position:0% application SP is like as wide as basically<00:18:30.760> any<00:18:31.039> smart<00:18:31.400> contract<00:18:32.159> ever<00:18:32.400> built 00:18:33.230 --> 00:18:33.240 align:start position:0% basically any smart contract ever built 00:18:33.240 --> 00:18:35.070 align:start position:0% basically any smart contract ever built so<00:18:33.400> I<00:18:33.520> find<00:18:33.679> it<00:18:33.880> like<00:18:34.039> super<00:18:34.360> hard<00:18:34.600> to<00:18:34.760> sort<00:18:34.919> of 00:18:35.070 --> 00:18:35.080 align:start position:0% so I find it like super hard to sort of 00:18:35.080 --> 00:18:37.110 align:start position:0% so I find it like super hard to sort of go<00:18:35.400> top<00:18:35.760> down<00:18:36.159> when<00:18:36.320> standardizing<00:18:36.960> and 00:18:37.110 --> 00:18:37.120 align:start position:0% go top down when standardizing and 00:18:37.120 --> 00:18:39.470 align:start position:0% go top down when standardizing and talking<00:18:37.360> about<00:18:37.799> intents<00:18:38.799> um<00:18:39.039> I<00:18:39.159> think<00:18:39.320> my 00:18:39.470 --> 00:18:39.480 align:start position:0% talking about intents um I think my 00:18:39.480 --> 00:18:41.110 align:start position:0% talking about intents um I think my current<00:18:39.799> best<00:18:40.000> bet<00:18:40.240> would<00:18:40.400> be<00:18:40.679> having<00:18:40.960> some 00:18:41.110 --> 00:18:41.120 align:start position:0% current best bet would be having some 00:18:41.120 --> 00:18:45.990 align:start position:0% current best bet would be having some sort<00:18:41.320> of<00:18:41.520> like<00:18:41.799> intent<00:18:42.840> DSL<00:18:43.840> like<00:18:44.440> think<00:18:45.000> evm 00:18:45.990 --> 00:18:46.000 align:start position:0% sort of like intent DSL like think evm 00:18:46.000 --> 00:18:48.190 align:start position:0% sort of like intent DSL like think evm but<00:18:46.120> for<00:18:46.320> building<00:18:46.640> intents<00:18:47.640> something<00:18:48.000> like 00:18:48.190 --> 00:18:48.200 align:start position:0% but for building intents something like 00:18:48.200 --> 00:18:50.950 align:start position:0% but for building intents something like that<00:18:48.440> sise<00:18:49.280> at<00:18:49.559> that<00:18:49.880> generic<00:18:50.400> level<00:18:50.679> maybe 00:18:50.950 --> 00:18:50.960 align:start position:0% that sise at that generic level maybe 00:18:50.960 --> 00:18:53.310 align:start position:0% that sise at that generic level maybe that<00:18:51.080> makes<00:18:51.360> sense<00:18:52.240> but<00:18:52.559> I<00:18:52.760> would<00:18:52.960> I<00:18:53.039> would 00:18:53.310 --> 00:18:53.320 align:start position:0% that makes sense but I would I would 00:18:53.320 --> 00:18:55.470 align:start position:0% that makes sense but I would I would honestly<00:18:53.760> like<00:18:53.880> go<00:18:54.120> bottom<00:18:54.440> up<00:18:55.039> build<00:18:55.320> like 00:18:55.470 --> 00:18:55.480 align:start position:0% honestly like go bottom up build like 00:18:55.480 --> 00:18:57.029 align:start position:0% honestly like go bottom up build like standardized<00:18:56.000> escros<00:18:56.679> build<00:18:56.919> like 00:18:57.029 --> 00:18:57.039 align:start position:0% standardized escros build like 00:18:57.039 --> 00:18:58.870 align:start position:0% standardized escros build like standardized<00:18:57.559> proof<00:18:57.799> systems<00:18:58.240> and<00:18:58.400> sort<00:18:58.559> of 00:18:58.870 --> 00:18:58.880 align:start position:0% standardized proof systems and sort of 00:18:58.880 --> 00:19:01.390 align:start position:0% standardized proof systems and sort of have<00:18:59.120> these<00:18:59.360> Legos<00:19:00.120> available<00:19:01.080> for 00:19:01.390 --> 00:19:01.400 align:start position:0% have these Legos available for 00:19:01.400 --> 00:19:03.070 align:start position:0% have these Legos available for developers<00:19:01.919> to<00:19:02.120> combine<00:19:02.520> and<00:19:02.679> build<00:19:02.919> their 00:19:03.070 --> 00:19:03.080 align:start position:0% developers to combine and build their 00:19:03.080 --> 00:19:05.230 align:start position:0% developers to combine and build their intent<00:19:03.400> protocols<00:19:04.280> instead<00:19:04.559> of<00:19:04.799> having<00:19:05.120> like 00:19:05.230 --> 00:19:05.240 align:start position:0% intent protocols instead of having like 00:19:05.240 --> 00:19:07.110 align:start position:0% intent protocols instead of having like a<00:19:05.360> standardized<00:19:05.880> intent<00:19:06.520> and<00:19:06.760> everything 00:19:07.110 --> 00:19:07.120 align:start position:0% a standardized intent and everything 00:19:07.120 --> 00:19:10.190 align:start position:0% a standardized intent and everything else<00:19:07.960> below<00:19:08.280> that<00:19:08.400> is<00:19:08.520> a 00:19:10.190 --> 00:19:10.200 align:start position:0% else below that is a 00:19:10.200 --> 00:19:12.950 align:start position:0% else below that is a blackbox<00:19:11.200> all<00:19:11.440> right<00:19:12.240> one<00:19:12.400> more<00:19:12.679> question 00:19:12.950 --> 00:19:12.960 align:start position:0% blackbox all right one more question 00:19:12.960 --> 00:19:16.029 align:start position:0% blackbox all right one more question that<00:19:13.280> just<00:19:13.559> came<00:19:13.799> in<00:19:14.799> instead<00:19:15.080> of<00:19:15.159> the<00:19:15.280> lockbox 00:19:16.029 --> 00:19:16.039 align:start position:0% that just came in instead of the lockbox 00:19:16.039 --> 00:19:17.710 align:start position:0% that just came in instead of the lockbox couldn't<00:19:16.280> we<00:19:16.480> have<00:19:16.679> a<00:19:16.760> user<00:19:17.039> signature<00:19:17.440> on<00:19:17.600> the 00:19:17.710 --> 00:19:17.720 align:start position:0% couldn't we have a user signature on the 00:19:17.720 --> 00:19:19.830 align:start position:0% couldn't we have a user signature on the intent<00:19:18.360> and<00:19:18.520> an<00:19:18.640> offchain<00:19:19.120> mechanism<00:19:19.600> that 00:19:19.830 --> 00:19:19.840 align:start position:0% intent and an offchain mechanism that 00:19:19.840 --> 00:19:23.669 align:start position:0% intent and an offchain mechanism that verifies<00:19:20.799> that<00:19:21.000> the<00:19:21.200> intent<00:19:21.679> output<00:19:22.480> is<00:19:23.320> in 00:19:23.669 --> 00:19:23.679 align:start position:0% verifies that the intent output is in 00:19:23.679 --> 00:19:26.230 align:start position:0% verifies that the intent output is in intact<00:19:24.320> via<00:19:24.600> that 00:19:26.230 --> 00:19:26.240 align:start position:0% intact via that 00:19:26.240 --> 00:19:28.310 align:start position:0% intact via that signature<00:19:27.240> yeah<00:19:27.400> I<00:19:27.520> think<00:19:27.720> the<00:19:27.919> purpose<00:19:28.200> of 00:19:28.310 --> 00:19:28.320 align:start position:0% signature yeah I think the purpose of 00:19:28.320 --> 00:19:30.950 align:start position:0% signature yeah I think the purpose of logb<00:19:28.720> Bo<00:19:28.919> is<00:19:29.039> like<00:19:29.200> slightly<00:19:29.760> different<00:19:30.760> um 00:19:30.950 --> 00:19:30.960 align:start position:0% logb Bo is like slightly different um 00:19:30.960 --> 00:19:33.470 align:start position:0% logb Bo is like slightly different um purpose<00:19:31.240> of<00:19:31.360> logbox<00:19:32.240> isn't<00:19:32.600> to<00:19:32.880> sort<00:19:33.080> of<00:19:33.240> like 00:19:33.470 --> 00:19:33.480 align:start position:0% purpose of logbox isn't to sort of like 00:19:33.480 --> 00:19:36.830 align:start position:0% purpose of logbox isn't to sort of like prove<00:19:34.080> that<00:19:35.080> uh<00:19:35.280> you<00:19:35.440> got<00:19:35.760> exactly<00:19:36.240> what<00:19:36.400> you 00:19:36.830 --> 00:19:36.840 align:start position:0% prove that uh you got exactly what you 00:19:36.840 --> 00:19:38.710 align:start position:0% prove that uh you got exactly what you wanted<00:19:37.240> on<00:19:37.400> destination<00:19:38.120> that's<00:19:38.320> the<00:19:38.440> job<00:19:38.640> of 00:19:38.710 --> 00:19:38.720 align:start position:0% wanted on destination that's the job of 00:19:38.720 --> 00:19:41.149 align:start position:0% wanted on destination that's the job of the<00:19:38.840> Oracle<00:19:39.240> Oracle<00:19:39.640> is<00:19:39.760> your<00:19:40.039> Truth<00:19:41.039> uh 00:19:41.149 --> 00:19:41.159 align:start position:0% the Oracle Oracle is your Truth uh 00:19:41.159 --> 00:19:43.710 align:start position:0% the Oracle Oracle is your Truth uh finder<00:19:41.679> in<00:19:41.880> this<00:19:42.159> sort<00:19:42.360> of<00:19:42.520> scenario<00:19:43.520> uh<00:19:43.640> I 00:19:43.710 --> 00:19:43.720 align:start position:0% finder in this sort of scenario uh I 00:19:43.720 --> 00:19:45.590 align:start position:0% finder in this sort of scenario uh I think<00:19:43.880> Oracle<00:19:44.280> is<00:19:44.400> just<00:19:44.559> to<00:19:44.760> give<00:19:45.039> Assurance 00:19:45.590 --> 00:19:45.600 align:start position:0% think Oracle is just to give Assurance 00:19:45.600 --> 00:19:48.750 align:start position:0% think Oracle is just to give Assurance to<00:19:46.520> uh<00:19:46.640> fillers<00:19:47.080> and<00:19:47.240> users<00:19:47.799> that<00:19:48.240> if<00:19:48.360> funds 00:19:48.750 --> 00:19:48.760 align:start position:0% to uh fillers and users that if funds 00:19:48.760 --> 00:19:50.350 align:start position:0% to uh fillers and users that if funds enter<00:19:49.080> this<00:19:49.240> particular<00:19:49.640> contract<00:19:50.080> they<00:19:50.159> will 00:19:50.350 --> 00:19:50.360 align:start position:0% enter this particular contract they will 00:19:50.360 --> 00:19:52.669 align:start position:0% enter this particular contract they will exit<00:19:50.640> only<00:19:50.880> in<00:19:51.039> these<00:19:51.200> two<00:19:51.559> conditions<00:19:52.280> and 00:19:52.669 --> 00:19:52.679 align:start position:0% exit only in these two conditions and 00:19:52.679 --> 00:19:55.350 align:start position:0% exit only in these two conditions and based<00:19:52.919> on<00:19:53.159> that<00:19:53.640> you<00:19:53.799> can<00:19:54.080> sort<00:19:54.320> of<00:19:54.559> like<00:19:55.200> uh 00:19:55.350 --> 00:19:55.360 align:start position:0% based on that you can sort of like uh 00:19:55.360 --> 00:19:57.590 align:start position:0% based on that you can sort of like uh simulate<00:19:55.919> stuff<00:19:56.520> and<00:19:56.679> have<00:19:56.840> a<00:19:56.960> guarantee<00:19:57.400> that 00:19:57.590 --> 00:19:57.600 align:start position:0% simulate stuff and have a guarantee that 00:19:57.600 --> 00:19:59.830 align:start position:0% simulate stuff and have a guarantee that if<00:19:57.760> funds<00:19:57.960> are<00:19:58.280> entering<00:19:58.520> the<00:19:58.760> this<00:19:58.880> contract 00:19:59.830 --> 00:19:59.840 align:start position:0% if funds are entering the this contract 00:19:59.840 --> 00:20:02.190 align:start position:0% if funds are entering the this contract this<00:20:00.039> contract<00:20:00.400> is<00:20:00.559> not<00:20:00.919> poisonous<00:20:01.919> and<00:20:02.080> you 00:20:02.190 --> 00:20:02.200 align:start position:0% this contract is not poisonous and you 00:20:02.200 --> 00:20:03.669 align:start position:0% this contract is not poisonous and you can<00:20:02.360> interact<00:20:02.760> with<00:20:02.880> it<00:20:03.039> pretty<00:20:03.240> much<00:20:03.480> like 00:20:03.669 --> 00:20:03.679 align:start position:0% can interact with it pretty much like 00:20:03.679 --> 00:20:06.190 align:start position:0% can interact with it pretty much like how<00:20:03.799> you<00:20:03.880> do<00:20:04.039> with<00:20:04.200> erc20<00:20:04.720> is<00:20:04.880> today<00:20:05.840> uh<00:20:06.000> even 00:20:06.190 --> 00:20:06.200 align:start position:0% how you do with erc20 is today uh even 00:20:06.200 --> 00:20:08.110 align:start position:0% how you do with erc20 is today uh even with<00:20:06.360> erc20<00:20:06.960> is<00:20:07.080> you<00:20:07.159> can<00:20:07.360> have<00:20:07.600> like<00:20:07.760> weird 00:20:08.110 --> 00:20:08.120 align:start position:0% with erc20 is you can have like weird 00:20:08.120 --> 00:20:11.830 align:start position:0% with erc20 is you can have like weird poisonous<00:20:09.280> ec2s<00:20:10.280> um<00:20:10.679> rc20<00:20:11.240> is<00:20:11.360> that<00:20:11.520> charge 00:20:11.830 --> 00:20:11.840 align:start position:0% poisonous ec2s um rc20 is that charge 00:20:11.840 --> 00:20:14.110 align:start position:0% poisonous ec2s um rc20 is that charge fees<00:20:12.120> on<00:20:12.320> transfers<00:20:13.200> but<00:20:13.400> because<00:20:13.640> we<00:20:13.760> can<00:20:13.880> do 00:20:14.110 --> 00:20:14.120 align:start position:0% fees on transfers but because we can do 00:20:14.120 --> 00:20:17.430 align:start position:0% fees on transfers but because we can do simulations<00:20:14.760> on<00:20:14.919> it<00:20:15.480> you<00:20:15.720> know<00:20:16.520> that<00:20:17.039> you<00:20:17.159> know 00:20:17.430 --> 00:20:17.440 align:start position:0% simulations on it you know that you know 00:20:17.440 --> 00:20:20.230 align:start position:0% simulations on it you know that you know like<00:20:17.640> if<00:20:17.720> you<00:20:17.880> send<00:20:18.640> 100<00:20:19.120> usdc<00:20:19.799> your<00:20:20.000> balance 00:20:20.230 --> 00:20:20.240 align:start position:0% like if you send 100 usdc your balance 00:20:20.240 --> 00:20:22.029 align:start position:0% like if you send 100 usdc your balance is<00:20:20.400> decreasing<00:20:20.840> by<00:20:21.080> 100<00:20:21.320> and<00:20:21.480> someone<00:20:21.720> else's 00:20:22.029 --> 00:20:22.039 align:start position:0% is decreasing by 100 and someone else's 00:20:22.039 --> 00:20:24.110 align:start position:0% is decreasing by 100 and someone else's balance<00:20:22.280> is<00:20:22.400> increasing<00:20:22.919> by<00:20:23.120> 100<00:20:23.679> so<00:20:23.840> you<00:20:23.960> can 00:20:24.110 --> 00:20:24.120 align:start position:0% balance is increasing by 100 so you can 00:20:24.120 --> 00:20:26.270 align:start position:0% balance is increasing by 100 so you can see<00:20:24.400> like<00:20:24.559> there's<00:20:24.799> nothing<00:20:25.120> poisonous<00:20:25.720> there 00:20:26.270 --> 00:20:26.280 align:start position:0% see like there's nothing poisonous there 00:20:26.280 --> 00:20:27.510 align:start position:0% see like there's nothing poisonous there I<00:20:26.360> think<00:20:26.520> if<00:20:26.640> you<00:20:26.799> have<00:20:26.960> something<00:20:27.240> like<00:20:27.360> an 00:20:27.510 --> 00:20:27.520 align:start position:0% I think if you have something like an 00:20:27.520 --> 00:20:29.510 align:start position:0% I think if you have something like an escrow<00:20:27.960> there<00:20:28.080> you<00:20:28.159> can<00:20:28.320> Sim<00:20:28.919> and<00:20:29.039> see<00:20:29.320> that 00:20:29.510 --> 00:20:29.520 align:start position:0% escrow there you can Sim and see that 00:20:29.520 --> 00:20:31.750 align:start position:0% escrow there you can Sim and see that hey<00:20:29.640> funds<00:20:29.880> are<00:20:30.039> reaching<00:20:30.440> my<00:20:31.080> escrow<00:20:31.640> with 00:20:31.750 --> 00:20:31.760 align:start position:0% hey funds are reaching my escrow with 00:20:31.760 --> 00:20:33.789 align:start position:0% hey funds are reaching my escrow with the<00:20:31.960> right<00:20:32.200> key<00:20:32.760> so<00:20:32.960> no<00:20:33.120> matter<00:20:33.440> what<00:20:33.600> is 00:20:33.789 --> 00:20:33.799 align:start position:0% the right key so no matter what is 00:20:33.799 --> 00:20:35.510 align:start position:0% the right key so no matter what is happening<00:20:34.240> with<00:20:34.360> the<00:20:34.520> settlement<00:20:35.200> or<00:20:35.400> with 00:20:35.510 --> 00:20:35.520 align:start position:0% happening with the settlement or with 00:20:35.520 --> 00:20:36.909 align:start position:0% happening with the settlement or with the<00:20:35.679> with<00:20:35.760> the<00:20:35.880> settler<00:20:36.280> contract<00:20:36.679> I<00:20:36.799> don't 00:20:36.909 --> 00:20:36.919 align:start position:0% the with the settler contract I don't 00:20:36.919 --> 00:20:38.390 align:start position:0% the with the settler contract I don't have<00:20:37.039> to<00:20:37.159> be<00:20:37.280> worried<00:20:37.640> that<00:20:37.760> it's<00:20:37.960> poisonous 00:20:38.390 --> 00:20:38.400 align:start position:0% have to be worried that it's poisonous 00:20:38.400 --> 00:20:41.789 align:start position:0% have to be worried that it's poisonous or<00:20:38.559> something<00:20:38.840> like<00:20:39.400> that<00:20:40.400> okay<00:20:41.039> probably<00:20:41.520> the 00:20:41.789 --> 00:20:41.799 align:start position:0% or something like that okay probably the 00:20:41.799 --> 00:20:44.789 align:start position:0% or something like that okay probably the last<00:20:42.120> question<00:20:42.480> just<00:20:42.720> popped<00:20:43.200> up<00:20:44.200> if<00:20:44.320> solvers 00:20:44.789 --> 00:20:44.799 align:start position:0% last question just popped up if solvers 00:20:44.799 --> 00:20:46.990 align:start position:0% last question just popped up if solvers take<00:20:45.000> the<00:20:45.120> risk<00:20:45.360> of<00:20:45.480> finality<00:20:46.440> how<00:20:46.600> can<00:20:46.720> we<00:20:46.840> get 00:20:46.990 --> 00:20:47.000 align:start position:0% take the risk of finality how can we get 00:20:47.000 --> 00:20:49.870 align:start position:0% take the risk of finality how can we get high<00:20:47.240> security<00:20:47.840> in<00:20:48.240> insurances<00:20:48.960> with<00:20:49.520> cross 00:20:49.870 --> 00:20:49.880 align:start position:0% high security in insurances with cross 00:20:49.880 --> 00:20:52.789 align:start position:0% high security in insurances with cross chain<00:20:50.159> transfers<00:20:50.799> priced<00:20:51.400> at<00:20:51.520> a<00:20:51.640> few<00:20:51.840> cents<00:20:52.720> is 00:20:52.789 --> 00:20:52.799 align:start position:0% chain transfers priced at a few cents is 00:20:52.799 --> 00:20:53.909 align:start position:0% chain transfers priced at a few cents is it 00:20:53.909 --> 00:20:53.919 align:start position:0% it 00:20:53.919 --> 00:20:57.190 align:start position:0% it sustainable<00:20:54.919> super<00:20:55.559> solid<00:20:56.000> question<00:20:56.400> I<00:20:56.520> think 00:20:57.190 --> 00:20:57.200 align:start position:0% sustainable super solid question I think 00:20:57.200 --> 00:20:59.190 align:start position:0% sustainable super solid question I think it<00:20:57.360> is<00:20:57.880> not<00:20:58.159> sustainable<00:20:58.679> able<00:20:58.840> if<00:20:58.919> you<00:20:59.000> don't 00:20:59.190 --> 00:20:59.200 align:start position:0% it is not sustainable able if you don't 00:20:59.200 --> 00:21:00.830 align:start position:0% it is not sustainable able if you don't have<00:20:59.280> a<00:20:59.400> lot<00:20:59.520> of<00:20:59.640> fillers<00:21:00.240> that's<00:21:00.440> why<00:21:00.559> we<00:21:00.679> need 00:21:00.830 --> 00:21:00.840 align:start position:0% have a lot of fillers that's why we need 00:21:00.840 --> 00:21:02.870 align:start position:0% have a lot of fillers that's why we need a<00:21:01.200> ton<00:21:01.360> of<00:21:01.480> fillers<00:21:02.320> if<00:21:02.400> you<00:21:02.559> have<00:21:02.720> more 00:21:02.870 --> 00:21:02.880 align:start position:0% a ton of fillers if you have more 00:21:02.880 --> 00:21:05.669 align:start position:0% a ton of fillers if you have more fillers<00:21:03.280> we<00:21:03.400> have<00:21:03.559> more<00:21:04.000> competition<00:21:05.000> then<00:21:05.559> I 00:21:05.669 --> 00:21:05.679 align:start position:0% fillers we have more competition then I 00:21:05.679 --> 00:21:08.669 align:start position:0% fillers we have more competition then I am<00:21:05.919> quite<00:21:06.120> bullish<00:21:06.440> that<00:21:06.640> we'll<00:21:07.120> have<00:21:08.120> uh 00:21:08.669 --> 00:21:08.679 align:start position:0% am quite bullish that we'll have uh 00:21:08.679 --> 00:21:11.310 align:start position:0% am quite bullish that we'll have uh people<00:21:09.000> with<00:21:09.240> capital<00:21:10.039> fighting<00:21:10.360> for<00:21:10.600> pennies 00:21:11.310 --> 00:21:11.320 align:start position:0% people with capital fighting for pennies 00:21:11.320 --> 00:21:13.350 align:start position:0% people with capital fighting for pennies and<00:21:11.480> our<00:21:11.919> our<00:21:12.039> Crossing<00:21:12.480> transfers<00:21:13.039> can 00:21:13.350 --> 00:21:13.360 align:start position:0% and our our Crossing transfers can 00:21:13.360 --> 00:21:14.750 align:start position:0% and our our Crossing transfers can remain<00:21:13.640> like<00:21:13.840> fairly 00:21:14.750 --> 00:21:14.760 align:start position:0% remain like fairly 00:21:14.760 --> 00:21:17.919 align:start position:0% remain like fairly cheap<00:21:15.760> cool