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:26.790 align:start position:0% [Music] 00:00:26.790 --> 00:00:26.800 align:start position:0% 00:00:26.800 --> 00:00:30.790 align:start position:0% hello<00:00:27.800> hello<00:00:28.519> hello<00:00:28.920> everyone<00:00:29.759> uh<00:00:30.240> well<00:00:30.640> thank 00:00:30.790 --> 00:00:30.800 align:start position:0% hello hello hello everyone uh well thank 00:00:30.800 --> 00:00:33.950 align:start position:0% hello hello hello everyone uh well thank you<00:00:30.880> for<00:00:31.080> joining<00:00:31.480> us<00:00:32.480> um<00:00:32.719> we<00:00:32.880> are<00:00:33.160> here<00:00:33.520> to 00:00:33.950 --> 00:00:33.960 align:start position:0% you for joining us um we are here to 00:00:33.960 --> 00:00:37.350 align:start position:0% you for joining us um we are here to discuss<00:00:34.960> um<00:00:35.360> about<00:00:35.920> how<00:00:36.200> intents<00:00:36.960> or<00:00:37.120> or 00:00:37.350 --> 00:00:37.360 align:start position:0% discuss um about how intents or or 00:00:37.360 --> 00:00:39.590 align:start position:0% discuss um about how intents or or intents<00:00:38.200> are<00:00:38.440> reshaping<00:00:39.040> the<00:00:39.160> user 00:00:39.590 --> 00:00:39.600 align:start position:0% intents are reshaping the user 00:00:39.600 --> 00:00:43.630 align:start position:0% intents are reshaping the user experience<00:00:40.360> uh<00:00:40.480> in<00:00:41.039> Defi<00:00:42.120> and<00:00:43.120> from 00:00:43.630 --> 00:00:43.640 align:start position:0% experience uh in Defi and from 00:00:43.640 --> 00:00:45.750 align:start position:0% experience uh in Defi and from simplifying<00:00:44.640> complex<00:00:45.079> operations<00:00:45.520> or 00:00:45.750 --> 00:00:45.760 align:start position:0% simplifying complex operations or 00:00:45.760 --> 00:00:48.630 align:start position:0% simplifying complex operations or complex<00:00:46.239> transactions<00:00:46.920> in<00:00:47.199> in<00:00:47.520> blockchain<00:00:48.520> uh 00:00:48.630 --> 00:00:48.640 align:start position:0% complex transactions in in blockchain uh 00:00:48.640 --> 00:00:50.229 align:start position:0% complex transactions in in blockchain uh to<00:00:48.840> increasing 00:00:50.229 --> 00:00:50.239 align:start position:0% to increasing 00:00:50.239 --> 00:00:53.910 align:start position:0% to increasing security<00:00:51.239> and<00:00:51.640> oh<00:00:51.840> thank<00:00:52.000> you<00:00:52.520> and<00:00:52.800> improving 00:00:53.910 --> 00:00:53.920 align:start position:0% security and oh thank you and improving 00:00:53.920 --> 00:00:56.950 align:start position:0% security and oh thank you and improving decentralization<00:00:54.920> so<00:00:55.840> I'm<00:00:56.079> very<00:00:56.320> happy<00:00:56.559> to<00:00:56.719> be 00:00:56.950 --> 00:00:56.960 align:start position:0% decentralization so I'm very happy to be 00:00:56.960 --> 00:00:59.189 align:start position:0% decentralization so I'm very happy to be here<00:00:57.280> and<00:00:57.440> I'm<00:00:57.600> very<00:00:57.800> happy<00:00:58.039> to<00:00:58.120> be<00:00:58.280> joined<00:00:58.680> by 00:00:59.189 --> 00:00:59.199 align:start position:0% here and I'm very happy to be joined by 00:00:59.199 --> 00:01:03.029 align:start position:0% here and I'm very happy to be joined by this<00:00:59.399> group<00:00:59.600> of<00:01:00.039> experts<00:01:00.879> who<00:01:01.079> are<00:01:02.039> uh 00:01:03.029 --> 00:01:03.039 align:start position:0% this group of experts who are uh 00:01:03.039 --> 00:01:05.229 align:start position:0% this group of experts who are uh collaborating<00:01:03.840> with<00:01:04.040> leading<00:01:04.519> protocols<00:01:05.000> on 00:01:05.229 --> 00:01:05.239 align:start position:0% collaborating with leading protocols on 00:01:05.239 --> 00:01:07.710 align:start position:0% collaborating with leading protocols on this<00:01:05.439> matter<00:01:06.240> so<00:01:06.680> if<00:01:06.799> it's<00:01:07.040> okay<00:01:07.200> for<00:01:07.400> you<00:01:07.600> we 00:01:07.710 --> 00:01:07.720 align:start position:0% this matter so if it's okay for you we 00:01:07.720 --> 00:01:09.910 align:start position:0% this matter so if it's okay for you we can<00:01:07.960> start<00:01:08.320> with<00:01:08.720> uh<00:01:09.080> with<00:01:09.280> introductions 00:01:09.910 --> 00:01:09.920 align:start position:0% can start with uh with introductions 00:01:09.920 --> 00:01:12.190 align:start position:0% can start with uh with introductions brief<00:01:10.159> introductions<00:01:10.799> from<00:01:11.159> from<00:01:11.720> uh<00:01:11.880> all<00:01:12.040> of 00:01:12.190 --> 00:01:12.200 align:start position:0% brief introductions from from uh all of 00:01:12.200 --> 00:01:15.950 align:start position:0% brief introductions from from uh all of us<00:01:13.040> I<00:01:13.159> will<00:01:13.320> let<00:01:13.520> you<00:01:14.159> uh<00:01:14.560> start<00:01:15.000> probably<00:01:15.799> uh 00:01:15.950 --> 00:01:15.960 align:start position:0% us I will let you uh start probably uh 00:01:15.960 --> 00:01:18.070 align:start position:0% us I will let you uh start probably uh Sean<00:01:16.240> do<00:01:16.320> you<00:01:16.400> want<00:01:16.479> to 00:01:18.070 --> 00:01:18.080 align:start position:0% Sean do you want to 00:01:18.080 --> 00:01:21.910 align:start position:0% Sean do you want to start 00:01:21.910 --> 00:01:21.920 align:start position:0% 00:01:21.920 --> 00:01:25.670 align:start position:0% yeah<00:01:22.920> hey<00:01:23.520> okay<00:01:23.720> cool<00:01:24.280> um<00:01:24.479> hey<00:01:24.680> guys<00:01:24.840> I'm<00:01:24.960> Sean 00:01:25.670 --> 00:01:25.680 align:start position:0% yeah hey okay cool um hey guys I'm Sean 00:01:25.680 --> 00:01:28.749 align:start position:0% yeah hey okay cool um hey guys I'm Sean I<00:01:25.799> work<00:01:25.920> at<00:01:26.040> orbs<00:01:26.600> I've<00:01:26.920> been<00:01:27.920> um<00:01:28.040> in<00:01:28.200> the<00:01:28.400> space 00:01:28.749 --> 00:01:28.759 align:start position:0% I work at orbs I've been um in the space 00:01:28.759 --> 00:01:30.590 align:start position:0% I work at orbs I've been um in the space since<00:01:29.200> uh<00:01:29.320> 2018 00:01:30.590 --> 00:01:30.600 align:start position:0% since uh 2018 00:01:30.600 --> 00:01:32.590 align:start position:0% since uh 2018 uh<00:01:30.720> doing<00:01:31.079> a<00:01:31.320> bunch<00:01:31.479> of<00:01:31.640> stuff<00:01:31.880> I<00:01:31.960> have<00:01:32.119> no<00:01:32.399> web 00:01:32.590 --> 00:01:32.600 align:start position:0% uh doing a bunch of stuff I have no web 00:01:32.600 --> 00:01:34.870 align:start position:0% uh doing a bunch of stuff I have no web 2<00:01:32.880> experience<00:01:33.439> so<00:01:33.720> I've<00:01:33.840> been<00:01:34.000> doing<00:01:34.200> it<00:01:34.399> live 00:01:34.870 --> 00:01:34.880 align:start position:0% 2 experience so I've been doing it live 00:01:34.880 --> 00:01:37.030 align:start position:0% 2 experience so I've been doing it live since<00:01:35.880> um<00:01:36.079> since<00:01:36.399> then<00:01:36.600> and<00:01:36.720> just<00:01:36.840> kind<00:01:36.960> of 00:01:37.030 --> 00:01:37.040 align:start position:0% since um since then and just kind of 00:01:37.040 --> 00:01:39.830 align:start position:0% since um since then and just kind of learning<00:01:37.399> as<00:01:37.560> I<00:01:37.759> as<00:01:37.880> I<00:01:38.000> go<00:01:38.159> along<00:01:38.399> it's<00:01:38.600> been<00:01:39.600> um 00:01:39.830 --> 00:01:39.840 align:start position:0% learning as I as I go along it's been um 00:01:39.840 --> 00:01:42.230 align:start position:0% learning as I as I go along it's been um a<00:01:39.920> lot<00:01:40.079> of<00:01:40.320> fun<00:01:41.320> um<00:01:41.479> at<00:01:41.640> orbs<00:01:42.000> what<00:01:42.119> we're 00:01:42.230 --> 00:01:42.240 align:start position:0% a lot of fun um at orbs what we're 00:01:42.240 --> 00:01:44.950 align:start position:0% a lot of fun um at orbs what we're building<00:01:43.159> um<00:01:43.399> is<00:01:43.640> is<00:01:43.880> kind<00:01:44.000> of<00:01:44.479> we<00:01:44.600> kind<00:01:44.719> of 00:01:44.950 --> 00:01:44.960 align:start position:0% building um is is kind of we kind of 00:01:44.960 --> 00:01:48.630 align:start position:0% building um is is kind of we kind of call<00:01:45.159> ourselves<00:01:45.640> a<00:01:46.040> L3<00:01:46.520> for<00:01:46.719> onchain<00:01:47.640> trading 00:01:48.630 --> 00:01:48.640 align:start position:0% call ourselves a L3 for onchain trading 00:01:48.640 --> 00:01:50.550 align:start position:0% call ourselves a L3 for onchain trading um<00:01:48.840> what<00:01:48.960> that<00:01:49.159> actually<00:01:49.360> means<00:01:49.840> in<00:01:50.200> practice 00:01:50.550 --> 00:01:50.560 align:start position:0% um what that actually means in practice 00:01:50.560 --> 00:01:53.590 align:start position:0% um what that actually means in practice is<00:01:50.799> we<00:01:51.600> uh<00:01:51.719> build<00:01:52.000> protocols<00:01:52.439> for<00:01:52.719> D5<00:01:53.200> Pro<00:01:53.399> for 00:01:53.590 --> 00:01:53.600 align:start position:0% is we uh build protocols for D5 Pro for 00:01:53.600 --> 00:01:57.029 align:start position:0% is we uh build protocols for D5 Pro for for<00:01:54.159> D<00:01:55.159> um<00:01:55.280> so<00:01:55.399> we<00:01:55.479> have<00:01:55.600> advanced<00:01:55.920> order<00:01:56.240> types 00:01:57.029 --> 00:01:57.039 align:start position:0% for D um so we have advanced order types 00:01:57.039 --> 00:01:59.109 align:start position:0% for D um so we have advanced order types um<00:01:57.159> for<00:01:57.320> dexes<00:01:58.119> uh<00:01:58.240> so<00:01:58.399> two<00:01:58.640> op<00:01:58.799> and<00:01:58.920> limit 00:01:59.109 --> 00:01:59.119 align:start position:0% um for dexes uh so two op and limit 00:01:59.119 --> 00:02:01.590 align:start position:0% um for dexes uh so two op and limit orders<00:02:00.079> um<00:02:00.200> we<00:02:00.320> have<00:02:00.479> another<00:02:01.159> protocol 00:02:01.590 --> 00:02:01.600 align:start position:0% orders um we have another protocol 00:02:01.600 --> 00:02:05.029 align:start position:0% orders um we have another protocol called<00:02:01.799> liquidity<00:02:02.280> Hub<00:02:02.520> that<00:02:02.920> uses<00:02:03.920> um<00:02:04.439> that's 00:02:05.029 --> 00:02:05.039 align:start position:0% called liquidity Hub that uses um that's 00:02:05.039 --> 00:02:07.029 align:start position:0% called liquidity Hub that uses um that's intent<00:02:05.439> in<00:02:05.640> nature<00:02:06.000> in<00:02:06.119> terms<00:02:06.439> of<00:02:06.880> it 00:02:07.029 --> 00:02:07.039 align:start position:0% intent in nature in terms of it 00:02:07.039 --> 00:02:08.550 align:start position:0% intent in nature in terms of it Aggregates<00:02:07.479> all<00:02:07.640> the<00:02:07.719> liquidity<00:02:08.119> on<00:02:08.239> chain<00:02:08.440> we 00:02:08.550 --> 00:02:08.560 align:start position:0% Aggregates all the liquidity on chain we 00:02:08.560 --> 00:02:10.550 align:start position:0% Aggregates all the liquidity on chain we use<00:02:08.800> par<00:02:09.080> swap<00:02:09.360> as<00:02:09.440> a<00:02:09.879> good<00:02:10.039> friend<00:02:10.239> of<00:02:10.360> ours 00:02:10.550 --> 00:02:10.560 align:start position:0% use par swap as a good friend of ours 00:02:10.560 --> 00:02:13.670 align:start position:0% use par swap as a good friend of ours for<00:02:10.759> that<00:02:11.239> and<00:02:11.959> um<00:02:12.959> and<00:02:13.120> then<00:02:13.280> we're<00:02:13.520> we're 00:02:13.670 --> 00:02:13.680 align:start position:0% for that and um and then we're we're 00:02:13.680 --> 00:02:15.589 align:start position:0% for that and um and then we're we're doing<00:02:13.920> some<00:02:14.120> stuff<00:02:14.400> now<00:02:14.640> with<00:02:14.959> um<00:02:15.120> with<00:02:15.280> pers 00:02:15.589 --> 00:02:15.599 align:start position:0% doing some stuff now with um with pers 00:02:15.599 --> 00:02:17.430 align:start position:0% doing some stuff now with um with pers as<00:02:15.680> well<00:02:15.879> that's<00:02:16.000> also<00:02:16.239> intent<00:02:16.599> based<00:02:16.920> so<00:02:17.160> yeah 00:02:17.430 --> 00:02:17.440 align:start position:0% as well that's also intent based so yeah 00:02:17.440 --> 00:02:19.030 align:start position:0% as well that's also intent based so yeah really<00:02:17.640> excited<00:02:18.000> glad<00:02:18.160> to<00:02:18.239> be<00:02:18.360> up<00:02:18.480> here<00:02:18.720> guys 00:02:19.030 --> 00:02:19.040 align:start position:0% really excited glad to be up here guys 00:02:19.040 --> 00:02:22.589 align:start position:0% really excited glad to be up here guys um<00:02:19.400> thanks<00:02:19.560> for<00:02:19.720> inviting<00:02:20.160> me<00:02:21.160> thank<00:02:21.360> you<00:02:22.239> uh 00:02:22.589 --> 00:02:22.599 align:start position:0% um thanks for inviting me thank you uh 00:02:22.599 --> 00:02:24.550 align:start position:0% um thanks for inviting me thank you uh Julie<00:02:23.120> do<00:02:23.239> you<00:02:23.360> want<00:02:23.480> to<00:02:23.599> introduce<00:02:24.040> yourself 00:02:24.550 --> 00:02:24.560 align:start position:0% Julie do you want to introduce yourself 00:02:24.560 --> 00:02:27.350 align:start position:0% Julie do you want to introduce yourself yep<00:02:25.120> okay<00:02:25.760> uh<00:02:25.920> hi<00:02:26.120> everyone<00:02:26.760> nice<00:02:26.920> to<00:02:27.040> be<00:02:27.200> here 00:02:27.350 --> 00:02:27.360 align:start position:0% yep okay uh hi everyone nice to be here 00:02:27.360 --> 00:02:30.470 align:start position:0% yep okay uh hi everyone nice to be here too<00:02:27.720> thanks<00:02:27.920> for<00:02:28.080> the<00:02:28.200> invitation<00:02:28.599> I<00:02:29.400> um<00:02:30.319> I 00:02:30.470 --> 00:02:30.480 align:start position:0% too thanks for the invitation I um I 00:02:30.480 --> 00:02:33.150 align:start position:0% too thanks for the invitation I um I work<00:02:30.760> at<00:02:30.959> mimic<00:02:31.720> and<00:02:32.040> I'm<00:02:32.280> in<00:02:32.480> the<00:02:32.680> whole 00:02:33.150 --> 00:02:33.160 align:start position:0% work at mimic and I'm in the whole 00:02:33.160 --> 00:02:35.630 align:start position:0% work at mimic and I'm in the whole Partnerships<00:02:33.920> Communications<00:02:34.560> PR<00:02:35.280> part<00:02:35.440> of 00:02:35.630 --> 00:02:35.640 align:start position:0% Partnerships Communications PR part of 00:02:35.640 --> 00:02:38.990 align:start position:0% Partnerships Communications PR part of the<00:02:36.440> protocol<00:02:37.280> so<00:02:37.519> at<00:02:37.640> mimic<00:02:38.000> we're<00:02:38.200> a<00:02:38.560> defi 00:02:38.990 --> 00:02:39.000 align:start position:0% the protocol so at mimic we're a defi 00:02:39.000 --> 00:02:40.869 align:start position:0% the protocol so at mimic we're a defi automation<00:02:39.440> protocol<00:02:39.959> and<00:02:40.120> what<00:02:40.239> we<00:02:40.360> do<00:02:40.599> is<00:02:40.720> we 00:02:40.869 --> 00:02:40.879 align:start position:0% automation protocol and what we do is we 00:02:40.879 --> 00:02:43.630 align:start position:0% automation protocol and what we do is we simplify<00:02:41.560> day-to-day<00:02:42.080> operations<00:02:43.080> by 00:02:43.630 --> 00:02:43.640 align:start position:0% simplify day-to-day operations by 00:02:43.640 --> 00:02:46.110 align:start position:0% simplify day-to-day operations by automating<00:02:44.640> and<00:02:45.360> what<00:02:45.480> we're<00:02:45.599> doing<00:02:45.959> right 00:02:46.110 --> 00:02:46.120 align:start position:0% automating and what we're doing right 00:02:46.120 --> 00:02:48.630 align:start position:0% automating and what we're doing right now<00:02:46.360> is<00:02:46.560> we<00:02:46.720> are<00:02:47.280> launching<00:02:47.760> our<00:02:48.239> newest 00:02:48.630 --> 00:02:48.640 align:start position:0% now is we are launching our newest 00:02:48.640 --> 00:02:50.550 align:start position:0% now is we are launching our newest version<00:02:49.080> which<00:02:49.239> is<00:02:49.599> launching<00:02:49.920> our<00:02:50.080> protocol 00:02:50.550 --> 00:02:50.560 align:start position:0% version which is launching our protocol 00:02:50.560 --> 00:02:52.390 align:start position:0% version which is launching our protocol and<00:02:50.720> we<00:02:50.840> would<00:02:51.040> like<00:02:51.200> to<00:02:51.440> everyone<00:02:51.800> to<00:02:52.080> start 00:02:52.390 --> 00:02:52.400 align:start position:0% and we would like to everyone to start 00:02:52.400 --> 00:02:54.710 align:start position:0% and we would like to everyone to start trying<00:02:52.959> and<00:02:53.640> see<00:02:53.959> the<00:02:54.040> full<00:02:54.200> experience<00:02:54.560> of 00:02:54.710 --> 00:02:54.720 align:start position:0% trying and see the full experience of 00:02:54.720 --> 00:02:56.630 align:start position:0% trying and see the full experience of How<00:02:54.840> It's<00:02:55.040> like<00:02:55.200> to<00:02:55.319> automate<00:02:55.680> on<00:02:55.840> Defi<00:02:56.360> and 00:02:56.630 --> 00:02:56.640 align:start position:0% How It's like to automate on Defi and 00:02:56.640 --> 00:02:58.390 align:start position:0% How It's like to automate on Defi and make<00:02:56.800> it<00:02:57.000> easier<00:02:57.360> for<00:02:57.599> people<00:02:57.800> to<00:02:58.000> interact 00:02:58.390 --> 00:02:58.400 align:start position:0% make it easier for people to interact 00:02:58.400 --> 00:03:00.149 align:start position:0% make it easier for people to interact more<00:02:58.720> and<00:02:58.840> get<00:02:59.000> more<00:02:59.200> access<00:02:59.400> to<00:02:59.560> it<00:02:59.680> and<00:02:59.879> and 00:03:00.149 --> 00:03:00.159 align:start position:0% more and get more access to it and and 00:03:00.159 --> 00:03:01.910 align:start position:0% more and get more access to it and and instead<00:03:00.400> of<00:03:00.480> being<00:03:00.720> like<00:03:01.080> this<00:03:01.280> complex<00:03:01.640> idea 00:03:01.910 --> 00:03:01.920 align:start position:0% instead of being like this complex idea 00:03:01.920 --> 00:03:05.430 align:start position:0% instead of being like this complex idea that<00:03:02.080> we<00:03:02.239> have<00:03:02.920> and<00:03:03.360> make<00:03:03.519> it<00:03:03.720> more<00:03:04.599> like<00:03:05.280> uh 00:03:05.430 --> 00:03:05.440 align:start position:0% that we have and make it more like uh 00:03:05.440 --> 00:03:08.470 align:start position:0% that we have and make it more like uh day<00:03:05.640> to-day<00:03:06.120> and<00:03:06.840> basically<00:03:07.319> make<00:03:07.440> it<00:03:07.560> easier 00:03:08.470 --> 00:03:08.480 align:start position:0% day to-day and basically make it easier 00:03:08.480 --> 00:03:10.910 align:start position:0% day to-day and basically make it easier yeah<00:03:09.480> cool<00:03:10.000> thank<00:03:10.159> you<00:03:10.480> thank<00:03:10.640> you<00:03:10.720> for 00:03:10.910 --> 00:03:10.920 align:start position:0% yeah cool thank you thank you for 00:03:10.920 --> 00:03:14.589 align:start position:0% yeah cool thank you thank you for joining<00:03:11.920> Dom<00:03:12.920> uh<00:03:13.080> hey<00:03:13.239> everyone<00:03:13.720> I'm<00:03:13.959> Dominic 00:03:14.589 --> 00:03:14.599 align:start position:0% joining Dom uh hey everyone I'm Dominic 00:03:14.599 --> 00:03:17.910 align:start position:0% joining Dom uh hey everyone I'm Dominic um<00:03:14.760> I'm<00:03:14.879> the<00:03:15.000> head<00:03:15.120> of<00:03:15.200> ecosystem<00:03:15.840> at<00:03:16.319> lifi<00:03:17.319> um 00:03:17.910 --> 00:03:17.920 align:start position:0% um I'm the head of ecosystem at lifi um 00:03:17.920 --> 00:03:21.070 align:start position:0% um I'm the head of ecosystem at lifi um we<00:03:18.159> are<00:03:18.720> a<00:03:19.280> bridge<00:03:19.599> and<00:03:19.840> deex<00:03:20.080> aggregator<00:03:20.599> so 00:03:21.070 --> 00:03:21.080 align:start position:0% we are a bridge and deex aggregator so 00:03:21.080 --> 00:03:23.309 align:start position:0% we are a bridge and deex aggregator so generally<00:03:21.599> a<00:03:21.760> liquidity<00:03:22.440> aggregation 00:03:23.309 --> 00:03:23.319 align:start position:0% generally a liquidity aggregation 00:03:23.319 --> 00:03:28.309 align:start position:0% generally a liquidity aggregation protocol<00:03:24.480> um<00:03:25.480> our<00:03:26.239> main<00:03:26.799> usage 00:03:28.309 --> 00:03:28.319 align:start position:0% protocol um our main usage 00:03:28.319 --> 00:03:32.350 align:start position:0% protocol um our main usage is<00:03:29.319> having<00:03:29.760> any<00:03:29.920> to<00:03:30.080> any<00:03:30.400> swaps<00:03:31.280> um<00:03:31.680> across<00:03:32.159> all 00:03:32.350 --> 00:03:32.360 align:start position:0% is having any to any swaps um across all 00:03:32.360 --> 00:03:34.350 align:start position:0% is having any to any swaps um across all the<00:03:32.560> major<00:03:32.840> chains<00:03:33.239> and<00:03:33.439> ecosystems<00:03:34.200> we 00:03:34.350 --> 00:03:34.360 align:start position:0% the major chains and ecosystems we 00:03:34.360 --> 00:03:38.190 align:start position:0% the major chains and ecosystems we support<00:03:34.760> evm<00:03:35.760> Solana<00:03:36.640> and<00:03:37.000> Bitcoin<00:03:37.439> right<00:03:37.560> now 00:03:38.190 --> 00:03:38.200 align:start position:0% support evm Solana and Bitcoin right now 00:03:38.200 --> 00:03:40.710 align:start position:0% support evm Solana and Bitcoin right now um<00:03:38.439> expanding<00:03:39.159> further<00:03:39.560> into<00:03:39.799> other 00:03:40.710 --> 00:03:40.720 align:start position:0% um expanding further into other 00:03:40.720 --> 00:03:44.309 align:start position:0% um expanding further into other ecosystems<00:03:41.720> um<00:03:42.560> we<00:03:42.720> do<00:03:43.120> have<00:03:43.560> Lei<00:03:43.920> itself<00:03:44.159> is<00:03:44.200> a 00:03:44.309 --> 00:03:44.319 align:start position:0% ecosystems um we do have Lei itself is a 00:03:44.319 --> 00:03:47.110 align:start position:0% ecosystems um we do have Lei itself is a B2B<00:03:44.720> product<00:03:45.040> mostly<00:03:45.680> integrated<00:03:46.680> um<00:03:46.920> with 00:03:47.110 --> 00:03:47.120 align:start position:0% B2B product mostly integrated um with 00:03:47.120 --> 00:03:49.670 align:start position:0% B2B product mostly integrated um with big<00:03:47.280> wallets<00:03:47.599> and<00:03:48.040> applications<00:03:49.040> and<00:03:49.200> then<00:03:49.480> it 00:03:49.670 --> 00:03:49.680 align:start position:0% big wallets and applications and then it 00:03:49.680 --> 00:03:52.030 align:start position:0% big wallets and applications and then it also<00:03:50.000> Powers<00:03:50.400> jumper.<00:03:51.000> exchange<00:03:51.599> which<00:03:51.799> is 00:03:52.030 --> 00:03:52.040 align:start position:0% also Powers jumper. exchange which is 00:03:52.040 --> 00:03:55.229 align:start position:0% also Powers jumper. exchange which is our<00:03:52.280> own<00:03:52.640> front<00:03:52.920> end<00:03:53.480> interface<00:03:54.480> um<00:03:54.840> which<00:03:55.000> is 00:03:55.229 --> 00:03:55.239 align:start position:0% our own front end interface um which is 00:03:55.239 --> 00:03:57.229 align:start position:0% our own front end interface um which is catered<00:03:55.560> to<00:03:55.680> end 00:03:57.229 --> 00:03:57.239 align:start position:0% catered to end 00:03:57.239 --> 00:04:00.470 align:start position:0% catered to end users<00:03:58.239> great<00:03:58.760> thank<00:03:58.959> you<00:03:59.519> uh<00:03:59.840> thank<00:04:00.040> you<00:04:00.159> for 00:04:00.470 --> 00:04:00.480 align:start position:0% users great thank you uh thank you for 00:04:00.480 --> 00:04:03.309 align:start position:0% users great thank you uh thank you for for<00:04:00.680> your<00:04:00.920> introductions<00:04:01.519> for<00:04:01.760> joining<00:04:02.120> us<00:04:03.040> uh 00:04:03.309 --> 00:04:03.319 align:start position:0% for your introductions for joining us uh 00:04:03.319 --> 00:04:06.350 align:start position:0% for your introductions for joining us uh myself<00:04:04.000> I'm<00:04:04.599> uh<00:04:04.760> I'm<00:04:04.959> a<00:04:05.519> I'm<00:04:05.640> leading<00:04:06.120> the 00:04:06.350 --> 00:04:06.360 align:start position:0% myself I'm uh I'm a I'm leading the 00:04:06.360 --> 00:04:08.390 align:start position:0% myself I'm uh I'm a I'm leading the operations<00:04:06.840> and<00:04:07.000> the<00:04:07.120> partnership<00:04:07.560> teams<00:04:08.079> at 00:04:08.390 --> 00:04:08.400 align:start position:0% operations and the partnership teams at 00:04:08.400 --> 00:04:12.030 align:start position:0% operations and the partnership teams at Paras<00:04:08.720> swap<00:04:09.560> Paras<00:04:09.920> swap<00:04:10.120> it's<00:04:10.280> a<00:04:11.159> defi 00:04:12.030 --> 00:04:12.040 align:start position:0% Paras swap Paras swap it's a defi 00:04:12.040 --> 00:04:16.030 align:start position:0% Paras swap Paras swap it's a defi aggregator<00:04:13.040> and<00:04:13.720> we<00:04:14.720> not<00:04:14.959> so<00:04:15.239> recently<00:04:15.799> but 00:04:16.030 --> 00:04:16.040 align:start position:0% aggregator and we not so recently but 00:04:16.040 --> 00:04:18.390 align:start position:0% aggregator and we not so recently but it's<00:04:16.199> a<00:04:16.440> kind<00:04:16.600> of<00:04:16.759> new<00:04:17.000> released<00:04:17.479> our<00:04:17.880> intense 00:04:18.390 --> 00:04:18.400 align:start position:0% it's a kind of new released our intense 00:04:18.400 --> 00:04:22.030 align:start position:0% it's a kind of new released our intense trading<00:04:19.239> uh<00:04:19.680> solution<00:04:20.680> uh<00:04:20.880> that<00:04:21.040> it's<00:04:21.280> built 00:04:22.030 --> 00:04:22.040 align:start position:0% trading uh solution uh that it's built 00:04:22.040 --> 00:04:24.790 align:start position:0% trading uh solution uh that it's built uh<00:04:22.160> on<00:04:22.440> top<00:04:22.800> of<00:04:23.040> porticus<00:04:23.880> which<00:04:24.040> is<00:04:24.560> uh 00:04:24.790 --> 00:04:24.800 align:start position:0% uh on top of porticus which is uh 00:04:24.800 --> 00:04:26.870 align:start position:0% uh on top of porticus which is uh providing<00:04:25.280> the<00:04:25.440> intense<00:04:25.960> infrastructure<00:04:26.639> for 00:04:26.870 --> 00:04:26.880 align:start position:0% providing the intense infrastructure for 00:04:26.880 --> 00:04:30.189 align:start position:0% providing the intense infrastructure for this<00:04:27.600> and<00:04:27.840> why<00:04:28.000> is<00:04:28.199> this<00:04:28.600> important<00:04:29.600> uh<00:04:29.919> for 00:04:30.189 --> 00:04:30.199 align:start position:0% this and why is this important uh for 00:04:30.199 --> 00:04:32.070 align:start position:0% this and why is this important uh for Paras<00:04:30.520> swap<00:04:30.840> Paras<00:04:31.160> swap<00:04:31.360> is<00:04:31.479> leveraging 00:04:32.070 --> 00:04:32.080 align:start position:0% Paras swap Paras swap is leveraging 00:04:32.080 --> 00:04:34.870 align:start position:0% Paras swap Paras swap is leveraging Paras<00:04:32.400> swap<00:04:32.600> Delta<00:04:33.120> the<00:04:33.520> trading<00:04:34.360> the<00:04:34.479> intense 00:04:34.870 --> 00:04:34.880 align:start position:0% Paras swap Delta the trading the intense 00:04:34.880 --> 00:04:37.909 align:start position:0% Paras swap Delta the trading the intense trading<00:04:35.240> solution<00:04:36.160> and<00:04:36.320> this<00:04:36.560> enables<00:04:37.520> our 00:04:37.909 --> 00:04:37.919 align:start position:0% trading solution and this enables our 00:04:37.919 --> 00:04:41.270 align:start position:0% trading solution and this enables our users<00:04:38.400> to<00:04:39.320> uh<00:04:39.440> trade<00:04:39.840> gasless<00:04:40.600> and<00:04:40.759> trade<00:04:41.120> with 00:04:41.270 --> 00:04:41.280 align:start position:0% users to uh trade gasless and trade with 00:04:41.280 --> 00:04:43.950 align:start position:0% users to uh trade gasless and trade with me<00:04:41.759> protection<00:04:42.600> with<00:04:43.039> it<00:04:43.240> would<00:04:43.560> it<00:04:43.639> wouldn't 00:04:43.950 --> 00:04:43.960 align:start position:0% me protection with it would it wouldn't 00:04:43.960 --> 00:04:45.550 align:start position:0% me protection with it would it wouldn't be<00:04:44.199> possible<00:04:44.639> without 00:04:45.550 --> 00:04:45.560 align:start position:0% be possible without 00:04:45.560 --> 00:04:48.830 align:start position:0% be possible without intents<00:04:46.560> um<00:04:47.280> so<00:04:47.720> and<00:04:48.000> and<00:04:48.280> it's<00:04:48.479> not<00:04:48.680> a 00:04:48.830 --> 00:04:48.840 align:start position:0% intents um so and and it's not a 00:04:48.840 --> 00:04:50.749 align:start position:0% intents um so and and it's not a coincidence<00:04:49.400> that<00:04:49.560> we<00:04:49.680> are<00:04:49.840> all<00:04:50.000> sitting<00:04:50.440> here 00:04:50.749 --> 00:04:50.759 align:start position:0% coincidence that we are all sitting here 00:04:50.759 --> 00:04:52.749 align:start position:0% coincidence that we are all sitting here because<00:04:51.199> we<00:04:51.320> are<00:04:51.479> partnering<00:04:52.039> with<00:04:52.440> between 00:04:52.749 --> 00:04:52.759 align:start position:0% because we are partnering with between 00:04:52.759 --> 00:04:54.790 align:start position:0% because we are partnering with between all<00:04:52.880> of<00:04:53.120> all<00:04:53.240> of<00:04:53.360> our<00:04:53.680> protocols<00:04:54.560> uh<00:04:54.680> to 00:04:54.790 --> 00:04:54.800 align:start position:0% all of all of our protocols uh to 00:04:54.800 --> 00:04:57.550 align:start position:0% all of all of our protocols uh to leverage<00:04:55.400> intents<00:04:55.840> and<00:04:55.960> to<00:04:56.160> bring<00:04:56.960> uh<00:04:57.199> better 00:04:57.550 --> 00:04:57.560 align:start position:0% leverage intents and to bring uh better 00:04:57.560 --> 00:05:01.390 align:start position:0% leverage intents and to bring uh better user<00:04:58.199> experience<00:04:59.199> uh<00:04:59.440> in<00:04:59.800> different<00:05:00.199> use 00:05:01.390 --> 00:05:01.400 align:start position:0% user experience uh in different use 00:05:01.400 --> 00:05:04.670 align:start position:0% user experience uh in different use cases<00:05:02.400> so<00:05:03.280> having<00:05:03.560> done<00:05:03.880> this<00:05:04.280> uh<00:05:04.479> these 00:05:04.670 --> 00:05:04.680 align:start position:0% cases so having done this uh these 00:05:04.680 --> 00:05:06.749 align:start position:0% cases so having done this uh these introductions<00:05:05.479> what<00:05:05.840> uh<00:05:06.320> where<00:05:06.560> where 00:05:06.749 --> 00:05:06.759 align:start position:0% introductions what uh where where 00:05:06.759 --> 00:05:10.310 align:start position:0% introductions what uh where where probably<00:05:07.120> we<00:05:07.240> can<00:05:07.400> start<00:05:08.039> is<00:05:09.039> we<00:05:09.240> know<00:05:09.440> intents 00:05:10.310 --> 00:05:10.320 align:start position:0% probably we can start is we know intents 00:05:10.320 --> 00:05:14.350 align:start position:0% probably we can start is we know intents uh<00:05:10.479> will<00:05:10.960> be<00:05:11.960> uh<00:05:12.120> or<00:05:12.360> are<00:05:13.080> tackling<00:05:13.840> the<00:05:14.039> most 00:05:14.350 --> 00:05:14.360 align:start position:0% uh will be uh or are tackling the most 00:05:14.360 --> 00:05:16.230 align:start position:0% uh will be uh or are tackling the most important<00:05:14.880> or<00:05:15.080> one<00:05:15.199> of<00:05:15.320> the<00:05:15.440> most<00:05:15.720> important 00:05:16.230 --> 00:05:16.240 align:start position:0% important or one of the most important 00:05:16.240 --> 00:05:19.830 align:start position:0% important or one of the most important challenges<00:05:17.240> uh<00:05:17.320> in<00:05:17.520> defi<00:05:18.400> which<00:05:18.560> is<00:05:19.080> user 00:05:19.830 --> 00:05:19.840 align:start position:0% challenges uh in defi which is user 00:05:19.840 --> 00:05:21.629 align:start position:0% challenges uh in defi which is user experience 00:05:21.629 --> 00:05:21.639 align:start position:0% experience 00:05:21.639 --> 00:05:25.710 align:start position:0% experience so<00:05:22.639> besides<00:05:23.080> tackling<00:05:23.600> this<00:05:23.880> issue<00:05:24.520> and<00:05:25.039> when 00:05:25.710 --> 00:05:25.720 align:start position:0% so besides tackling this issue and when 00:05:25.720 --> 00:05:27.830 align:start position:0% so besides tackling this issue and when we<00:05:25.960> simplify<00:05:26.560> with<00:05:26.759> intense<00:05:27.360> complex 00:05:27.830 --> 00:05:27.840 align:start position:0% we simplify with intense complex 00:05:27.840 --> 00:05:29.950 align:start position:0% we simplify with intense complex transactions<00:05:28.479> or<00:05:28.720> complex<00:05:29.080> operations<00:05:29.840> we 00:05:29.950 --> 00:05:29.960 align:start position:0% transactions or complex operations we 00:05:29.960 --> 00:05:32.830 align:start position:0% transactions or complex operations we are<00:05:30.080> lowering<00:05:31.000> the<00:05:31.160> entry<00:05:31.520> barriers<00:05:32.160> for<00:05:32.520> new 00:05:32.830 --> 00:05:32.840 align:start position:0% are lowering the entry barriers for new 00:05:32.840 --> 00:05:36.270 align:start position:0% are lowering the entry barriers for new users<00:05:33.840> and<00:05:34.160> we<00:05:34.280> are<00:05:34.520> also<00:05:35.440> lowering<00:05:36.080> the 00:05:36.270 --> 00:05:36.280 align:start position:0% users and we are also lowering the 00:05:36.280 --> 00:05:38.990 align:start position:0% users and we are also lowering the existing<00:05:36.639> barriers<00:05:37.039> for<00:05:37.319> existing<00:05:37.759> users<00:05:38.240> so 00:05:38.990 --> 00:05:39.000 align:start position:0% existing barriers for existing users so 00:05:39.000 --> 00:05:41.550 align:start position:0% existing barriers for existing users so what<00:05:39.120> I<00:05:39.240> wanted<00:05:39.479> to<00:05:39.680> discuss<00:05:40.080> with<00:05:40.240> you<00:05:40.440> is<00:05:41.400> uh 00:05:41.550 --> 00:05:41.560 align:start position:0% what I wanted to discuss with you is uh 00:05:41.560 --> 00:05:44.189 align:start position:0% what I wanted to discuss with you is uh how<00:05:41.680> are<00:05:41.800> you<00:05:41.960> seeing<00:05:42.520> intents<00:05:43.280> improving<00:05:44.039> the 00:05:44.189 --> 00:05:44.199 align:start position:0% how are you seeing intents improving the 00:05:44.199 --> 00:05:47.309 align:start position:0% how are you seeing intents improving the user<00:05:44.600> experience<00:05:45.160> in<00:05:45.360> your<00:05:45.960> protocols<00:05:46.960> and 00:05:47.309 --> 00:05:47.319 align:start position:0% user experience in your protocols and 00:05:47.319 --> 00:05:49.309 align:start position:0% user experience in your protocols and from<00:05:47.520> your<00:05:47.800> perspective<00:05:48.720> which<00:05:48.960> kind<00:05:49.120> of 00:05:49.309 --> 00:05:49.319 align:start position:0% from your perspective which kind of 00:05:49.319 --> 00:05:56.230 align:start position:0% from your perspective which kind of barriers<00:05:49.880> are<00:05:50.120> we<00:05:50.479> lowering<00:05:51.440> for<00:05:51.800> new 00:05:56.230 --> 00:05:56.240 align:start position:0% 00:05:56.240 --> 00:05:59.950 align:start position:0% users<00:05:57.240> yeah<00:05:57.520> so<00:05:58.039> um<00:05:58.919> I<00:05:59.039> think<00:05:59.199> the<00:05:59.319> first<00:05:59.720> step 00:05:59.950 --> 00:05:59.960 align:start position:0% users yeah so um I think the first step 00:05:59.960 --> 00:06:02.670 align:start position:0% users yeah so um I think the first step is<00:06:00.080> starting<00:06:00.520> with<00:06:00.759> like<00:06:01.080> breaking<00:06:01.759> down<00:06:02.520> kind 00:06:02.670 --> 00:06:02.680 align:start position:0% is starting with like breaking down kind 00:06:02.680 --> 00:06:05.590 align:start position:0% is starting with like breaking down kind of<00:06:03.000> like<00:06:03.840> what<00:06:03.960> are<00:06:04.120> the<00:06:04.360> parts<00:06:04.800> of<00:06:05.080> this<00:06:05.400> like 00:06:05.590 --> 00:06:05.600 align:start position:0% of like what are the parts of this like 00:06:05.600 --> 00:06:07.870 align:start position:0% of like what are the parts of this like intent<00:06:06.080> based<00:06:06.520> user<00:06:06.840> flow<00:06:07.240> right<00:06:07.440> you<00:06:07.639> already 00:06:07.870 --> 00:06:07.880 align:start position:0% intent based user flow right you already 00:06:07.880 --> 00:06:10.830 align:start position:0% intent based user flow right you already said<00:06:08.039> it<00:06:08.720> um<00:06:08.960> for<00:06:09.160> the<00:06:09.319> most<00:06:09.720> part<00:06:10.599> um 00:06:10.830 --> 00:06:10.840 align:start position:0% said it um for the most part um 00:06:10.840 --> 00:06:13.870 align:start position:0% said it um for the most part um important<00:06:11.560> parts<00:06:11.800> of<00:06:11.960> it<00:06:12.240> is<00:06:12.720> a<00:06:13.240> gasless 00:06:13.870 --> 00:06:13.880 align:start position:0% important parts of it is a gasless 00:06:13.880 --> 00:06:17.230 align:start position:0% important parts of it is a gasless transaction<00:06:14.880> um<00:06:15.800> it<00:06:16.000> is<00:06:16.680> um<00:06:17.080> a 00:06:17.230 --> 00:06:17.240 align:start position:0% transaction um it is um a 00:06:17.240 --> 00:06:19.990 align:start position:0% transaction um it is um a signature-based<00:06:17.759> transaction<00:06:18.720> scheme<00:06:19.720> um 00:06:19.990 --> 00:06:20.000 align:start position:0% signature-based transaction scheme um 00:06:20.000 --> 00:06:22.749 align:start position:0% signature-based transaction scheme um and<00:06:20.160> then<00:06:20.319> on<00:06:20.479> the<00:06:20.639> other<00:06:20.960> hand<00:06:21.919> um<00:06:22.160> what<00:06:22.479> is 00:06:22.749 --> 00:06:22.759 align:start position:0% and then on the other hand um what is 00:06:22.759 --> 00:06:25.510 align:start position:0% and then on the other hand um what is almost<00:06:23.319> like<00:06:24.080> equally<00:06:24.520> used<00:06:24.919> with<00:06:25.120> the<00:06:25.280> word 00:06:25.510 --> 00:06:25.520 align:start position:0% almost like equally used with the word 00:06:25.520 --> 00:06:28.990 align:start position:0% almost like equally used with the word intense<00:06:26.319> is<00:06:27.240> um<00:06:27.360> the<00:06:27.479> term<00:06:27.800> solver<00:06:28.759> which 00:06:28.990 --> 00:06:29.000 align:start position:0% intense is um the term solver which 00:06:29.000 --> 00:06:32.270 align:start position:0% intense is um the term solver which basically<00:06:29.639> is<00:06:30.000> some<00:06:30.400> type<00:06:30.720> of<00:06:31.000> entity<00:06:31.960> call<00:06:32.160> it 00:06:32.270 --> 00:06:32.280 align:start position:0% basically is some type of entity call it 00:06:32.280 --> 00:06:34.430 align:start position:0% basically is some type of entity call it a<00:06:32.440> market<00:06:32.800> maker<00:06:33.319> routing<00:06:33.800> mechanism<00:06:34.280> or 00:06:34.430 --> 00:06:34.440 align:start position:0% a market maker routing mechanism or 00:06:34.440 --> 00:06:37.589 align:start position:0% a market maker routing mechanism or whatever<00:06:35.160> that<00:06:35.440> then<00:06:36.039> is<00:06:36.440> able<00:06:36.840> to<00:06:37.160> actually 00:06:37.589 --> 00:06:37.599 align:start position:0% whatever that then is able to actually 00:06:37.599 --> 00:06:39.909 align:start position:0% whatever that then is able to actually fulfill<00:06:38.120> these<00:06:38.400> complex<00:06:38.840> order<00:06:39.319> types<00:06:39.680> or 00:06:39.909 --> 00:06:39.919 align:start position:0% fulfill these complex order types or 00:06:39.919 --> 00:06:43.309 align:start position:0% fulfill these complex order types or sess<00:06:40.840> liquidity<00:06:41.840> um<00:06:42.639> that<00:06:42.800> we're<00:06:42.960> talking 00:06:43.309 --> 00:06:43.319 align:start position:0% sess liquidity um that we're talking 00:06:43.319 --> 00:06:46.629 align:start position:0% sess liquidity um that we're talking about<00:06:43.759> right<00:06:44.479> um<00:06:45.319> at<00:06:45.560> Lei<00:06:45.880> where<00:06:46.000> we're<00:06:46.120> mostly 00:06:46.629 --> 00:06:46.639 align:start position:0% about right um at Lei where we're mostly 00:06:46.639 --> 00:06:48.790 align:start position:0% about right um at Lei where we're mostly interacting<00:06:47.639> um<00:06:47.960> in<00:06:48.080> a<00:06:48.199> cross-chain 00:06:48.790 --> 00:06:48.800 align:start position:0% interacting um in a cross-chain 00:06:48.800 --> 00:06:51.270 align:start position:0% interacting um in a cross-chain environment<00:06:49.800> um<00:06:49.960> for<00:06:50.160> us<00:06:50.400> the<00:06:50.599> most<00:06:50.880> important 00:06:51.270 --> 00:06:51.280 align:start position:0% environment um for us the most important 00:06:51.280 --> 00:06:53.950 align:start position:0% environment um for us the most important Point<00:06:51.639> probably<00:06:52.319> is<00:06:52.919> um<00:06:53.120> that<00:06:53.360> gas 00:06:53.950 --> 00:06:53.960 align:start position:0% Point probably is um that gas 00:06:53.960 --> 00:06:56.270 align:start position:0% Point probably is um that gas abstraction<00:06:54.960> um<00:06:55.160> we're<00:06:55.440> actually<00:06:55.879> going<00:06:56.080> to 00:06:56.270 --> 00:06:56.280 align:start position:0% abstraction um we're actually going to 00:06:56.280 --> 00:06:58.150 align:start position:0% abstraction um we're actually going to launch<00:06:56.919> um<00:06:57.039> our<00:06:57.160> own<00:06:57.360> version<00:06:57.639> of<00:06:57.840> gas 00:06:58.150 --> 00:06:58.160 align:start position:0% launch um our own version of gas 00:06:58.160 --> 00:07:00.070 align:start position:0% launch um our own version of gas abstraction<00:06:59.160> in 00:07:00.070 --> 00:07:00.080 align:start position:0% abstraction in 00:07:00.080 --> 00:07:02.869 align:start position:0% abstraction in the<00:07:00.240> next<00:07:00.479> two<00:07:00.720> weeks<00:07:01.000> probably<00:07:02.000> um<00:07:02.280> and<00:07:02.479> also 00:07:02.869 --> 00:07:02.879 align:start position:0% the next two weeks probably um and also 00:07:02.879 --> 00:07:05.629 align:start position:0% the next two weeks probably um and also we<00:07:03.120> are<00:07:03.400> integrating<00:07:04.080> a<00:07:04.280> gas<00:07:04.560> zip<00:07:04.960> into<00:07:05.400> our 00:07:05.629 --> 00:07:05.639 align:start position:0% we are integrating a gas zip into our 00:07:05.639 --> 00:07:09.070 align:start position:0% we are integrating a gas zip into our routing<00:07:06.560> um<00:07:06.800> and<00:07:06.919> and<00:07:07.080> use<00:07:07.400> that<00:07:07.800> for<00:07:08.800> gas 00:07:09.070 --> 00:07:09.080 align:start position:0% routing um and and use that for gas 00:07:09.080 --> 00:07:12.469 align:start position:0% routing um and and use that for gas refueling<00:07:09.879> on<00:07:10.199> on<00:07:10.440> other<00:07:10.680> chains<00:07:11.400> um<00:07:12.120> which<00:07:12.360> if 00:07:12.469 --> 00:07:12.479 align:start position:0% refueling on on other chains um which if 00:07:12.479 --> 00:07:13.869 align:start position:0% refueling on on other chains um which if you're<00:07:12.759> interacting<00:07:13.199> in<00:07:13.319> a<00:07:13.440> cross<00:07:13.639> chain 00:07:13.869 --> 00:07:13.879 align:start position:0% you're interacting in a cross chain 00:07:13.879 --> 00:07:15.830 align:start position:0% you're interacting in a cross chain environment<00:07:14.280> is<00:07:14.479> very<00:07:14.680> important<00:07:15.199> because 00:07:15.830 --> 00:07:15.840 align:start position:0% environment is very important because 00:07:15.840 --> 00:07:17.869 align:start position:0% environment is very important because you<00:07:16.000> might<00:07:16.199> want<00:07:16.319> to<00:07:16.440> trade<00:07:16.680> on<00:07:16.800> a<00:07:16.960> chain<00:07:17.599> um 00:07:17.869 --> 00:07:17.879 align:start position:0% you might want to trade on a chain um 00:07:17.879 --> 00:07:20.070 align:start position:0% you might want to trade on a chain um that<00:07:18.000> you've<00:07:18.240> never<00:07:18.479> been<00:07:18.680> on<00:07:19.360> so<00:07:19.720> you<00:07:19.840> don't 00:07:20.070 --> 00:07:20.080 align:start position:0% that you've never been on so you don't 00:07:20.080 --> 00:07:22.869 align:start position:0% that you've never been on so you don't have<00:07:20.199> any<00:07:20.440> gas<00:07:20.639> in<00:07:20.759> your<00:07:20.960> account<00:07:21.360> there<00:07:22.160> um<00:07:22.560> so 00:07:22.869 --> 00:07:22.879 align:start position:0% have any gas in your account there um so 00:07:22.879 --> 00:07:24.550 align:start position:0% have any gas in your account there um so this<00:07:23.080> this<00:07:23.160> is<00:07:23.280> a<00:07:23.400> very<00:07:23.840> complex<00:07:24.160> and 00:07:24.550 --> 00:07:24.560 align:start position:0% this this is a very complex and 00:07:24.560 --> 00:07:26.469 align:start position:0% this this is a very complex and difficult<00:07:24.800> problem<00:07:25.520> or<00:07:25.720> it<00:07:25.840> used<00:07:26.039> to<00:07:26.160> be<00:07:26.319> a 00:07:26.469 --> 00:07:26.479 align:start position:0% difficult problem or it used to be a 00:07:26.479 --> 00:07:28.230 align:start position:0% difficult problem or it used to be a very<00:07:26.960> complex<00:07:27.240> and<00:07:27.560> difficult<00:07:27.720> problem<00:07:28.000> as 00:07:28.230 --> 00:07:28.240 align:start position:0% very complex and difficult problem as 00:07:28.240 --> 00:07:30.189 align:start position:0% very complex and difficult problem as many<00:07:28.440> of<00:07:28.599> you<00:07:28.759> probably<00:07:29.080> know 00:07:30.189 --> 00:07:30.199 align:start position:0% many of you probably know 00:07:30.199 --> 00:07:34.469 align:start position:0% many of you probably know um<00:07:31.199> so<00:07:31.919> for<00:07:32.080> me<00:07:32.400> those<00:07:32.639> are<00:07:33.120> kind<00:07:33.280> of<00:07:33.759> the<00:07:33.960> most 00:07:34.469 --> 00:07:34.479 align:start position:0% um so for me those are kind of the most 00:07:34.479 --> 00:07:37.710 align:start position:0% um so for me those are kind of the most important<00:07:35.479> issues<00:07:35.919> that<00:07:36.080> we<00:07:36.199> can<00:07:36.720> um<00:07:37.080> solve 00:07:37.710 --> 00:07:37.720 align:start position:0% important issues that we can um solve 00:07:37.720 --> 00:07:40.830 align:start position:0% important issues that we can um solve with<00:07:38.120> intents<00:07:39.120> um<00:07:39.520> and<00:07:39.720> then<00:07:40.440> there's 00:07:40.830 --> 00:07:40.840 align:start position:0% with intents um and then there's 00:07:40.840 --> 00:07:44.749 align:start position:0% with intents um and then there's probably<00:07:41.840> more<00:07:42.199> complex<00:07:42.680> use<00:07:43.440> cases<00:07:44.440> um<00:07:44.599> on 00:07:44.749 --> 00:07:44.759 align:start position:0% probably more complex use cases um on 00:07:44.759 --> 00:07:46.950 align:start position:0% probably more complex use cases um on top<00:07:44.960> of<00:07:45.120> that<00:07:45.520> that<00:07:45.840> these<00:07:46.000> two<00:07:46.199> teams<00:07:46.720> are 00:07:46.950 --> 00:07:46.960 align:start position:0% top of that that these two teams are 00:07:46.960 --> 00:07:49.469 align:start position:0% top of that that these two teams are tackling<00:07:47.599> which<00:07:48.080> yeah<00:07:48.280> they<00:07:48.400> can<00:07:48.520> talk 00:07:49.469 --> 00:07:49.479 align:start position:0% tackling which yeah they can talk 00:07:49.479 --> 00:07:51.710 align:start position:0% tackling which yeah they can talk about<00:07:50.479> yeah<00:07:50.599> well<00:07:50.759> I<00:07:50.840> can<00:07:51.000> continue<00:07:51.319> because<00:07:51.599> I 00:07:51.710 --> 00:07:51.720 align:start position:0% about yeah well I can continue because I 00:07:51.720 --> 00:07:53.869 align:start position:0% about yeah well I can continue because I can<00:07:52.000> take<00:07:52.199> your<00:07:52.440> point<00:07:52.680> and<00:07:53.240> reaching<00:07:53.720> more 00:07:53.869 --> 00:07:53.879 align:start position:0% can take your point and reaching more 00:07:53.879 --> 00:07:56.309 align:start position:0% can take your point and reaching more use<00:07:54.240> cases<00:07:54.599> which<00:07:54.759> is<00:07:55.520> basically<00:07:55.960> what<00:07:56.080> we're 00:07:56.309 --> 00:07:56.319 align:start position:0% use cases which is basically what we're 00:07:56.319 --> 00:07:59.230 align:start position:0% use cases which is basically what we're aiming<00:07:57.039> by<00:07:57.479> using<00:07:57.919> the<00:07:58.280> well<00:07:58.400> the<00:07:58.560> mimic<00:07:58.840> infra 00:07:59.230 --> 00:07:59.240 align:start position:0% aiming by using the well the mimic infra 00:07:59.240 --> 00:08:01.950 align:start position:0% aiming by using the well the mimic infra and<00:07:59.720> by<00:07:59.879> partnering<00:08:00.319> with<00:08:00.440> you<00:08:00.639> guys<00:08:01.319> is<00:08:01.680> the 00:08:01.950 --> 00:08:01.960 align:start position:0% and by partnering with you guys is the 00:08:01.960 --> 00:08:05.189 align:start position:0% and by partnering with you guys is the possibility<00:08:02.560> to<00:08:03.280> scale<00:08:03.759> on<00:08:04.039> that<00:08:04.840> and<00:08:05.039> the 00:08:05.189 --> 00:08:05.199 align:start position:0% possibility to scale on that and the 00:08:05.199 --> 00:08:06.790 align:start position:0% possibility to scale on that and the whole<00:08:05.440> that<00:08:05.639> decentralization<00:08:06.520> but<00:08:06.639> it's 00:08:06.790 --> 00:08:06.800 align:start position:0% whole that decentralization but it's 00:08:06.800 --> 00:08:08.230 align:start position:0% whole that decentralization but it's really<00:08:07.039> like<00:08:07.199> important<00:08:07.520> for<00:08:07.680> the<00:08:07.759> user<00:08:08.039> to 00:08:08.230 --> 00:08:08.240 align:start position:0% really like important for the user to 00:08:08.240 --> 00:08:11.550 align:start position:0% really like important for the user to know<00:08:09.240> what<00:08:09.440> it<00:08:09.680> what<00:08:09.800> it<00:08:10.080> needs<00:08:10.319> to<00:08:10.479> be<00:08:10.599> done<00:08:11.199> so 00:08:11.550 --> 00:08:11.560 align:start position:0% know what it what it needs to be done so 00:08:11.560 --> 00:08:13.749 align:start position:0% know what it what it needs to be done so if<00:08:11.680> you<00:08:11.840> know<00:08:12.319> what<00:08:12.639> action<00:08:13.080> you<00:08:13.199> want<00:08:13.319> to<00:08:13.479> take 00:08:13.749 --> 00:08:13.759 align:start position:0% if you know what action you want to take 00:08:13.759 --> 00:08:16.550 align:start position:0% if you know what action you want to take what<00:08:14.039> intent<00:08:15.039> then<00:08:15.720> all<00:08:15.919> the<00:08:16.039> rest<00:08:16.319> can<00:08:16.440> be 00:08:16.550 --> 00:08:16.560 align:start position:0% what intent then all the rest can be 00:08:16.560 --> 00:08:19.149 align:start position:0% what intent then all the rest can be taken<00:08:16.840> careed<00:08:17.440> of<00:08:18.159> and<00:08:18.400> that's<00:08:18.560> what<00:08:18.680> def<00:08:19.039> is 00:08:19.149 --> 00:08:19.159 align:start position:0% taken careed of and that's what def is 00:08:19.159 --> 00:08:21.670 align:start position:0% taken careed of and that's what def is about<00:08:19.560> and<00:08:19.960> that's<00:08:20.240> what<00:08:20.560> we're<00:08:21.039> aiming<00:08:21.479> with 00:08:21.670 --> 00:08:21.680 align:start position:0% about and that's what we're aiming with 00:08:21.680 --> 00:08:24.629 align:start position:0% about and that's what we're aiming with this<00:08:22.400> not<00:08:22.560> only<00:08:22.800> for<00:08:23.080> users<00:08:23.680> that<00:08:24.199> know<00:08:24.479> how 00:08:24.629 --> 00:08:24.639 align:start position:0% this not only for users that know how 00:08:24.639 --> 00:08:27.029 align:start position:0% this not only for users that know how dii<00:08:25.000> works<00:08:25.240> but<00:08:25.400> for<00:08:25.560> those<00:08:25.759> also<00:08:26.080> that<00:08:26.720> don't 00:08:27.029 --> 00:08:27.039 align:start position:0% dii works but for those also that don't 00:08:27.039 --> 00:08:29.710 align:start position:0% dii works but for those also that don't know<00:08:27.479> about<00:08:27.720> it<00:08:28.080> but<00:08:28.199> want<00:08:28.360> to<00:08:28.479> get<00:08:28.639> into<00:08:29.120> so<00:08:29.599> if 00:08:29.710 --> 00:08:29.720 align:start position:0% know about it but want to get into so if 00:08:29.720 --> 00:08:31.790 align:start position:0% know about it but want to get into so if you<00:08:29.840> know<00:08:30.280> what<00:08:30.759> slippage<00:08:31.240> you<00:08:31.319> want<00:08:31.400> to<00:08:31.520> set 00:08:31.790 --> 00:08:31.800 align:start position:0% you know what slippage you want to set 00:08:31.800 --> 00:08:34.269 align:start position:0% you know what slippage you want to set what<00:08:31.919> first<00:08:32.240> goal<00:08:32.440> you<00:08:32.519> want<00:08:32.599> to<00:08:32.719> set<00:08:33.240> and<00:08:34.120> that 00:08:34.269 --> 00:08:34.279 align:start position:0% what first goal you want to set and that 00:08:34.279 --> 00:08:39.670 align:start position:0% what first goal you want to set and that makes<00:08:34.440> it<00:08:34.680> much<00:08:34.919> easier<00:08:35.719> in<00:08:35.919> the<00:08:36.120> whole 00:08:39.670 --> 00:08:39.680 align:start position:0% 00:08:39.680 --> 00:08:43.149 align:start position:0% interaction<00:08:40.680> yeah<00:08:40.880> so<00:08:41.360> um<00:08:41.519> for<00:08:41.719> us<00:08:41.880> at<00:08:42.039> orbs<00:08:42.560> we 00:08:43.149 --> 00:08:43.159 align:start position:0% interaction yeah so um for us at orbs we 00:08:43.159 --> 00:08:45.150 align:start position:0% interaction yeah so um for us at orbs we have<00:08:43.919> um<00:08:44.120> I<00:08:44.200> mentioned<00:08:44.640> at<00:08:44.760> the<00:08:44.839> beginning 00:08:45.150 --> 00:08:45.160 align:start position:0% have um I mentioned at the beginning 00:08:45.160 --> 00:08:46.990 align:start position:0% have um I mentioned at the beginning that<00:08:45.279> we<00:08:45.480> have<00:08:45.680> an<00:08:45.839> onchain<00:08:46.640> sort<00:08:46.839> of 00:08:46.990 --> 00:08:47.000 align:start position:0% that we have an onchain sort of 00:08:47.000 --> 00:08:49.870 align:start position:0% that we have an onchain sort of aggregator<00:08:47.680> it's<00:08:47.800> for<00:08:48.120> spot<00:08:48.560> markets<00:08:49.560> um<00:08:49.720> and 00:08:49.870 --> 00:08:49.880 align:start position:0% aggregator it's for spot markets um and 00:08:49.880 --> 00:08:51.670 align:start position:0% aggregator it's for spot markets um and we<00:08:50.080> actually<00:08:50.320> integrate<00:08:50.839> that<00:08:51.040> directly<00:08:51.519> with 00:08:51.670 --> 00:08:51.680 align:start position:0% we actually integrate that directly with 00:08:51.680 --> 00:08:54.509 align:start position:0% we actually integrate that directly with Dex<00:08:52.320> uis<00:08:53.320> um<00:08:53.480> so<00:08:53.600> it's<00:08:53.680> called<00:08:53.839> liquidity<00:08:54.240> Hub 00:08:54.509 --> 00:08:54.519 align:start position:0% Dex uis um so it's called liquidity Hub 00:08:54.519 --> 00:08:58.030 align:start position:0% Dex uis um so it's called liquidity Hub it's<00:08:54.640> on<00:08:55.120> um<00:08:55.279> quick<00:08:55.519> swap<00:08:56.320> uh<00:08:57.120> uh<00:08:57.360> spooky<00:08:57.760> swap 00:08:58.030 --> 00:08:58.040 align:start position:0% it's on um quick swap uh uh spooky swap 00:08:58.040 --> 00:08:59.630 align:start position:0% it's on um quick swap uh uh spooky swap on<00:08:58.200> Phantom<00:08:58.640> if<00:08:58.959> you<00:08:59.040> guys<00:08:59.200> remember<00:08:59.560> that 00:08:59.630 --> 00:08:59.640 align:start position:0% on Phantom if you guys remember that 00:08:59.640 --> 00:09:00.870 align:start position:0% on Phantom if you guys remember that there's<00:08:59.760> a<00:08:59.839> phantom<00:09:00.120> chain<00:09:00.399> and<00:09:00.560> it's<00:09:00.720> not 00:09:00.870 --> 00:09:00.880 align:start position:0% there's a phantom chain and it's not 00:09:00.880 --> 00:09:04.110 align:start position:0% there's a phantom chain and it's not just<00:09:01.000> a<00:09:01.440> wallet<00:09:02.440> um<00:09:03.160> I<00:09:03.279> got<00:09:03.440> as<00:09:03.680> that<00:09:03.800> earlier 00:09:04.110 --> 00:09:04.120 align:start position:0% just a wallet um I got as that earlier 00:09:04.120 --> 00:09:07.069 align:start position:0% just a wallet um I got as that earlier that's<00:09:04.240> why<00:09:04.360> I'm<00:09:05.040> chuckling<00:09:05.440> about<00:09:05.600> it<00:09:06.560> um<00:09:06.920> as 00:09:07.069 --> 00:09:07.079 align:start position:0% that's why I'm chuckling about it um as 00:09:07.079 --> 00:09:10.509 align:start position:0% that's why I'm chuckling about it um as well<00:09:07.519> as<00:09:08.040> um<00:09:08.160> Thea<00:09:08.519> on<00:09:08.839> BMB<00:09:09.839> um<00:09:10.000> and<00:09:10.120> so<00:09:10.279> when 00:09:10.509 --> 00:09:10.519 align:start position:0% well as um Thea on BMB um and so when 00:09:10.519 --> 00:09:13.350 align:start position:0% well as um Thea on BMB um and so when users<00:09:10.880> come<00:09:11.000> to<00:09:11.160> swap<00:09:11.600> on<00:09:11.839> these<00:09:12.120> dexes<00:09:13.120> um<00:09:13.240> we 00:09:13.350 --> 00:09:13.360 align:start position:0% users come to swap on these dexes um we 00:09:13.360 --> 00:09:15.630 align:start position:0% users come to swap on these dexes um we do<00:09:13.519> an<00:09:13.640> RFQ<00:09:14.079> on<00:09:14.160> the<00:09:14.279> back<00:09:14.440> end<00:09:14.760> on<00:09:15.279> on<00:09:15.399> orbs 00:09:15.630 --> 00:09:15.640 align:start position:0% do an RFQ on the back end on on orbs 00:09:15.640 --> 00:09:17.670 align:start position:0% do an RFQ on the back end on on orbs layer<00:09:15.880> 3<00:09:16.120> rather<00:09:16.800> we<00:09:16.959> call<00:09:17.279> I<00:09:17.320> don't<00:09:17.440> know<00:09:17.560> we 00:09:17.670 --> 00:09:17.680 align:start position:0% layer 3 rather we call I don't know we 00:09:17.680 --> 00:09:20.870 align:start position:0% layer 3 rather we call I don't know we call<00:09:17.800> it<00:09:17.880> a<00:09:17.959> back<00:09:18.160> end<00:09:19.160> um<00:09:19.600> and<00:09:19.880> that<00:09:20.600> uh<00:09:20.800> kind 00:09:20.870 --> 00:09:20.880 align:start position:0% call it a back end um and that uh kind 00:09:20.880 --> 00:09:22.750 align:start position:0% call it a back end um and that uh kind of<00:09:21.040> abstracts<00:09:21.480> the<00:09:21.640> complexity<00:09:22.279> of<00:09:22.440> having 00:09:22.750 --> 00:09:22.760 align:start position:0% of abstracts the complexity of having 00:09:22.760 --> 00:09:26.190 align:start position:0% of abstracts the complexity of having users<00:09:23.600> need<00:09:23.760> to<00:09:24.000> go<00:09:24.200> to<00:09:24.600> an<00:09:24.880> aggregator<00:09:25.839> um<00:09:26.040> and 00:09:26.190 --> 00:09:26.200 align:start position:0% users need to go to an aggregator um and 00:09:26.200 --> 00:09:28.750 align:start position:0% users need to go to an aggregator um and and<00:09:26.320> search<00:09:26.600> for<00:09:26.760> the<00:09:26.880> best<00:09:27.079> price<00:09:27.760> themselves 00:09:28.750 --> 00:09:28.760 align:start position:0% and search for the best price themselves 00:09:28.760 --> 00:09:31.829 align:start position:0% and search for the best price themselves um<00:09:28.959> in<00:09:29.079> addition<00:09:29.519> to<00:09:29.760> this<00:09:30.680> um<00:09:31.320> we<00:09:31.480> also<00:09:31.640> have 00:09:31.829 --> 00:09:31.839 align:start position:0% um in addition to this um we also have 00:09:31.839 --> 00:09:33.310 align:start position:0% um in addition to this um we also have got<00:09:32.000> gasless<00:09:32.360> transactions<00:09:32.959> as<00:09:33.079> I<00:09:33.160> think 00:09:33.310 --> 00:09:33.320 align:start position:0% got gasless transactions as I think 00:09:33.320 --> 00:09:36.069 align:start position:0% got gasless transactions as I think everyone<00:09:33.600> else<00:09:34.240> up<00:09:34.600> up<00:09:34.760> here<00:09:34.959> has<00:09:35.120> mentioned 00:09:36.069 --> 00:09:36.079 align:start position:0% everyone else up up here has mentioned 00:09:36.079 --> 00:09:37.710 align:start position:0% everyone else up up here has mentioned um<00:09:36.200> and<00:09:36.320> I<00:09:36.399> think<00:09:36.600> these<00:09:36.760> two<00:09:36.959> things<00:09:37.279> are<00:09:37.519> are 00:09:37.710 --> 00:09:37.720 align:start position:0% um and I think these two things are are 00:09:37.720 --> 00:09:40.630 align:start position:0% um and I think these two things are are really<00:09:38.640> um<00:09:38.880> kind<00:09:39.000> of<00:09:39.160> the<00:09:39.320> core<00:09:40.200> the<00:09:40.560> the 00:09:40.630 --> 00:09:40.640 align:start position:0% really um kind of the core the the 00:09:40.640 --> 00:09:42.630 align:start position:0% really um kind of the core the the underscoring<00:09:41.240> of<00:09:41.440> of<00:09:41.560> what<00:09:41.680> we're 00:09:42.630 --> 00:09:42.640 align:start position:0% underscoring of of what we're 00:09:42.640 --> 00:09:46.829 align:start position:0% underscoring of of what we're doing<00:09:43.640> great<00:09:43.920> so<00:09:44.480> uh<00:09:45.360> it's<00:09:45.640> uh<00:09:46.399> it's<00:09:46.560> not<00:09:46.720> a 00:09:46.829 --> 00:09:46.839 align:start position:0% doing great so uh it's uh it's not a 00:09:46.839 --> 00:09:48.710 align:start position:0% doing great so uh it's uh it's not a coincidence<00:09:47.360> that<00:09:47.519> the<00:09:47.680> three<00:09:47.920> of<00:09:48.079> you 00:09:48.710 --> 00:09:48.720 align:start position:0% coincidence that the three of you 00:09:48.720 --> 00:09:51.750 align:start position:0% coincidence that the three of you mentioned<00:09:49.720> uh<00:09:50.040> abstracting<00:09:50.839> complexity<00:09:51.480> from 00:09:51.750 --> 00:09:51.760 align:start position:0% mentioned uh abstracting complexity from 00:09:51.760 --> 00:09:54.509 align:start position:0% mentioned uh abstracting complexity from users<00:09:52.640> uh<00:09:53.000> from<00:09:53.360> different<00:09:54.120> different 00:09:54.509 --> 00:09:54.519 align:start position:0% users uh from different different 00:09:54.519 --> 00:09:56.750 align:start position:0% users uh from different different different<00:09:54.920> in<00:09:55.079> different<00:09:55.440> ways<00:09:56.240> uh<00:09:56.360> in<00:09:56.440> order 00:09:56.750 --> 00:09:56.760 align:start position:0% different in different ways uh in order 00:09:56.760 --> 00:10:01.470 align:start position:0% different in different ways uh in order to<00:09:57.680> make<00:09:58.000> their<00:09:58.680> lives<00:09:59.079> EAS<00:09:59.399> easier<00:10:00.360> uh<00:10:00.680> and 00:10:01.470 --> 00:10:01.480 align:start position:0% to make their lives EAS easier uh and 00:10:01.480 --> 00:10:04.269 align:start position:0% to make their lives EAS easier uh and maybe<00:10:01.959> not<00:10:02.279> have<00:10:02.600> them<00:10:03.079> deciding<00:10:03.600> on<00:10:03.880> things 00:10:04.269 --> 00:10:04.279 align:start position:0% maybe not have them deciding on things 00:10:04.279 --> 00:10:06.430 align:start position:0% maybe not have them deciding on things that<00:10:04.839> they<00:10:04.959> don't<00:10:05.200> care<00:10:05.560> that<00:10:05.720> much<00:10:05.959> or<00:10:06.200> most 00:10:06.430 --> 00:10:06.440 align:start position:0% that they don't care that much or most 00:10:06.440 --> 00:10:09.550 align:start position:0% that they don't care that much or most users<00:10:06.839> don't<00:10:07.079> care<00:10:07.399> that<00:10:07.600> much<00:10:08.320> and<00:10:09.079> myself 00:10:09.550 --> 00:10:09.560 align:start position:0% users don't care that much and myself 00:10:09.560 --> 00:10:13.470 align:start position:0% users don't care that much and myself personally<00:10:10.120> I<00:10:10.240> have<00:10:10.440> found<00:10:10.800> myself<00:10:11.240> in<00:10:12.240> uh<00:10:13.240> not 00:10:13.470 --> 00:10:13.480 align:start position:0% personally I have found myself in uh not 00:10:13.480 --> 00:10:15.910 align:start position:0% personally I have found myself in uh not having<00:10:13.839> gas<00:10:14.240> on<00:10:14.440> the<00:10:14.680> destination<00:10:15.360> chain<00:10:15.680> when 00:10:15.910 --> 00:10:15.920 align:start position:0% having gas on the destination chain when 00:10:15.920 --> 00:10:18.590 align:start position:0% having gas on the destination chain when bridging<00:10:16.720> and<00:10:16.920> that<00:10:17.120> blocking<00:10:17.600> me<00:10:17.839> from<00:10:18.079> doing 00:10:18.590 --> 00:10:18.600 align:start position:0% bridging and that blocking me from doing 00:10:18.600 --> 00:10:20.949 align:start position:0% bridging and that blocking me from doing whatever<00:10:19.000> I<00:10:19.079> was<00:10:19.320> trying<00:10:19.600> to<00:10:19.800> do<00:10:20.519> having<00:10:20.760> to 00:10:20.949 --> 00:10:20.959 align:start position:0% whatever I was trying to do having to 00:10:20.959 --> 00:10:24.110 align:start position:0% whatever I was trying to do having to set<00:10:21.240> up<00:10:21.880> uh<00:10:22.040> lots<00:10:22.360> of<00:10:22.839> uh<00:10:23.240> uh<00:10:23.480> configurations 00:10:24.110 --> 00:10:24.120 align:start position:0% set up uh lots of uh uh configurations 00:10:24.120 --> 00:10:26.150 align:start position:0% set up uh lots of uh uh configurations that<00:10:24.320> probably<00:10:24.920> I<00:10:25.040> don't<00:10:25.240> care<00:10:25.480> or<00:10:25.640> I<00:10:25.800> prefer 00:10:26.150 --> 00:10:26.160 align:start position:0% that probably I don't care or I prefer 00:10:26.160 --> 00:10:30.030 align:start position:0% that probably I don't care or I prefer that<00:10:26.720> someone<00:10:27.040> else<00:10:27.320> decides<00:10:27.920> for<00:10:28.120> me<00:10:29.040> um<00:10:29.760> and 00:10:30.030 --> 00:10:30.040 align:start position:0% that someone else decides for me um and 00:10:30.040 --> 00:10:33.389 align:start position:0% that someone else decides for me um and when<00:10:30.360> using<00:10:30.800> different<00:10:31.399> dexes<00:10:32.399> uh<00:10:32.839> not<00:10:33.120> having 00:10:33.389 --> 00:10:33.399 align:start position:0% when using different dexes uh not having 00:10:33.399 --> 00:10:35.670 align:start position:0% when using different dexes uh not having to<00:10:33.640> maybe<00:10:33.959> go<00:10:34.160> to<00:10:34.360> a<00:10:34.519> meta<00:10:34.800> agregator<00:10:35.440> but 00:10:35.670 --> 00:10:35.680 align:start position:0% to maybe go to a meta agregator but 00:10:35.680 --> 00:10:38.389 align:start position:0% to maybe go to a meta agregator but rather<00:10:36.600> going<00:10:36.959> through<00:10:37.760> something<00:10:38.120> like<00:10:38.279> a 00:10:38.389 --> 00:10:38.399 align:start position:0% rather going through something like a 00:10:38.399 --> 00:10:41.190 align:start position:0% rather going through something like a liquidity<00:10:38.959> Hub<00:10:39.519> so<00:10:39.800> I<00:10:39.880> can<00:10:40.240> I<00:10:40.320> can<00:10:40.880> get<00:10:41.040> a 00:10:41.190 --> 00:10:41.200 align:start position:0% liquidity Hub so I can I can get a 00:10:41.200 --> 00:10:44.949 align:start position:0% liquidity Hub so I can I can get a better<00:10:41.600> a<00:10:41.720> better<00:10:42.040> quote<00:10:43.040> and<00:10:43.680> so<00:10:43.959> I<00:10:44.079> think<00:10:44.800> we 00:10:44.949 --> 00:10:44.959 align:start position:0% better a better quote and so I think we 00:10:44.959 --> 00:10:47.269 align:start position:0% better a better quote and so I think we are<00:10:45.120> on<00:10:45.320> the<00:10:45.560> path<00:10:46.000> with<00:10:46.200> intents<00:10:47.079> on 00:10:47.269 --> 00:10:47.279 align:start position:0% are on the path with intents on 00:10:47.279 --> 00:10:49.509 align:start position:0% are on the path with intents on different<00:10:47.639> protocols<00:10:48.079> in<00:10:48.240> different<00:10:48.600> ways<00:10:49.399> uh 00:10:49.509 --> 00:10:49.519 align:start position:0% different protocols in different ways uh 00:10:49.519 --> 00:10:52.269 align:start position:0% different protocols in different ways uh to<00:10:49.680> simplify<00:10:50.320> this<00:10:50.720> uh<00:10:51.000> this 00:10:52.269 --> 00:10:52.279 align:start position:0% to simplify this uh this 00:10:52.279 --> 00:10:56.629 align:start position:0% to simplify this uh this experience<00:10:53.279> what<00:10:54.200> um<00:10:55.200> what<00:10:55.360> I<00:10:55.480> see<00:10:56.040> from<00:10:56.480> from 00:10:56.629 --> 00:10:56.639 align:start position:0% experience what um what I see from from 00:10:56.639 --> 00:10:58.310 align:start position:0% experience what um what I see from from my<00:10:56.800> personal<00:10:57.200> view<00:10:57.440> is<00:10:57.560> I<00:10:57.680> see<00:10:57.880> lots<00:10:58.120> of 00:10:58.310 --> 00:10:58.320 align:start position:0% my personal view is I see lots of 00:10:58.320 --> 00:11:01.069 align:start position:0% my personal view is I see lots of protocols<00:10:58.760> that<00:10:58.920> are<00:10:59.440> uh<00:10:59.639> adopting<00:11:00.120> intents 00:11:01.069 --> 00:11:01.079 align:start position:0% protocols that are uh adopting intents 00:11:01.079 --> 00:11:04.829 align:start position:0% protocols that are uh adopting intents uh<00:11:01.240> and<00:11:01.440> this<00:11:01.600> is<00:11:01.920> kind<00:11:02.120> of<00:11:02.720> uh<00:11:03.360> it<00:11:03.600> has<00:11:03.839> come<00:11:04.600> a 00:11:04.829 --> 00:11:04.839 align:start position:0% uh and this is kind of uh it has come a 00:11:04.839 --> 00:11:08.509 align:start position:0% uh and this is kind of uh it has come a rise<00:11:05.200> it<00:11:05.360> has<00:11:05.519> become<00:11:05.839> a<00:11:06.000> race<00:11:06.480> of<00:11:07.200> uh<00:11:07.680> speed<00:11:08.040> of 00:11:08.509 --> 00:11:08.519 align:start position:0% rise it has become a race of uh speed of 00:11:08.519 --> 00:11:12.629 align:start position:0% rise it has become a race of uh speed of innovation<00:11:09.519> versus<00:11:10.399> scalability<00:11:11.639> so 00:11:12.629 --> 00:11:12.639 align:start position:0% innovation versus scalability so 00:11:12.639 --> 00:11:14.350 align:start position:0% innovation versus scalability so deploying<00:11:13.160> intents<00:11:13.639> or<00:11:13.839> implementing 00:11:14.350 --> 00:11:14.360 align:start position:0% deploying intents or implementing 00:11:14.360 --> 00:11:16.870 align:start position:0% deploying intents or implementing intents<00:11:15.040> uh<00:11:15.279> it's<00:11:15.480> not<00:11:15.839> easy<00:11:16.240> it's<00:11:16.399> not 00:11:16.870 --> 00:11:16.880 align:start position:0% intents uh it's not easy it's not 00:11:16.880 --> 00:11:18.430 align:start position:0% intents uh it's not easy it's not something<00:11:17.200> that<00:11:17.360> can<00:11:17.519> be<00:11:17.639> done<00:11:17.839> from<00:11:18.040> one<00:11:18.240> day 00:11:18.430 --> 00:11:18.440 align:start position:0% something that can be done from one day 00:11:18.440 --> 00:11:22.150 align:start position:0% something that can be done from one day to<00:11:18.600> the<00:11:18.720> other<00:11:19.680> so<00:11:20.639> what<00:11:20.800> I<00:11:20.920> wanted<00:11:21.200> to<00:11:21.600> to<00:11:21.920> ask 00:11:22.150 --> 00:11:22.160 align:start position:0% to the other so what I wanted to to ask 00:11:22.160 --> 00:11:24.310 align:start position:0% to the other so what I wanted to to ask you<00:11:22.360> is<00:11:22.519> about<00:11:22.800> your<00:11:23.000> point<00:11:23.279> of<00:11:23.440> you<00:11:23.720> regarding 00:11:24.310 --> 00:11:24.320 align:start position:0% you is about your point of you regarding 00:11:24.320 --> 00:11:26.750 align:start position:0% you is about your point of you regarding the<00:11:25.040> speed<00:11:25.360> of<00:11:25.560> deployment<00:11:26.120> the<00:11:26.240> speed<00:11:26.519> of 00:11:26.750 --> 00:11:26.760 align:start position:0% the speed of deployment the speed of 00:11:26.760 --> 00:11:31.230 align:start position:0% the speed of deployment the speed of innovation<00:11:27.760> versus<00:11:28.720> the<00:11:29.680> um<00:11:30.279> scalability<00:11:31.040> and 00:11:31.230 --> 00:11:31.240 align:start position:0% innovation versus the um scalability and 00:11:31.240 --> 00:11:33.750 align:start position:0% innovation versus the um scalability and how<00:11:31.399> to<00:11:31.680> design<00:11:32.519> uh<00:11:32.639> scalable<00:11:33.160> solutions<00:11:33.600> that 00:11:33.750 --> 00:11:33.760 align:start position:0% how to design uh scalable solutions that 00:11:33.760 --> 00:11:36.190 align:start position:0% how to design uh scalable solutions that can<00:11:33.920> leverage<00:11:34.399> intents<00:11:34.839> in<00:11:34.959> the<00:11:35.079> future<00:11:36.040> uh 00:11:36.190 --> 00:11:36.200 align:start position:0% can leverage intents in the future uh 00:11:36.200 --> 00:11:38.069 align:start position:0% can leverage intents in the future uh have<00:11:36.399> you<00:11:36.680> have<00:11:36.880> you 00:11:38.069 --> 00:11:38.079 align:start position:0% have you have you 00:11:38.079 --> 00:11:41.190 align:start position:0% have you have you found<00:11:39.079> um<00:11:40.000> how<00:11:40.200> you<00:11:40.360> find<00:11:40.760> trouble 00:11:41.190 --> 00:11:41.200 align:start position:0% found um how you find trouble 00:11:41.200 --> 00:11:42.790 align:start position:0% found um how you find trouble implementing<00:11:41.800> this<00:11:42.000> how<00:11:42.160> you<00:11:42.279> found<00:11:42.519> trouble 00:11:42.790 --> 00:11:42.800 align:start position:0% implementing this how you found trouble 00:11:42.800 --> 00:11:44.910 align:start position:0% implementing this how you found trouble in<00:11:43.079> finding<00:11:43.440> Scala<00:11:44.040> Solutions<00:11:44.399> and<00:11:44.639> how<00:11:44.800> did 00:11:44.910 --> 00:11:44.920 align:start position:0% in finding Scala Solutions and how did 00:11:44.920 --> 00:11:47.069 align:start position:0% in finding Scala Solutions and how did you<00:11:45.040> solve 00:11:47.069 --> 00:11:47.079 align:start position:0% you solve 00:11:47.079 --> 00:11:51.350 align:start position:0% you solve those<00:11:48.079> yeah<00:11:48.760> um<00:11:49.240> I<00:11:49.320> can<00:11:49.560> start<00:11:50.480> um<00:11:50.680> I<00:11:50.760> think<00:11:51.120> the 00:11:51.350 --> 00:11:51.360 align:start position:0% those yeah um I can start um I think the 00:11:51.360 --> 00:11:53.670 align:start position:0% those yeah um I can start um I think the the<00:11:51.480> way<00:11:51.639> that<00:11:51.839> we<00:11:52.040> look<00:11:52.240> at<00:11:52.440> that<00:11:53.200> um<00:11:53.480> is 00:11:53.670 --> 00:11:53.680 align:start position:0% the way that we look at that um is 00:11:53.680 --> 00:11:55.949 align:start position:0% the way that we look at that um is probably<00:11:54.000> the<00:11:54.120> one<00:11:54.560> where<00:11:55.320> there's<00:11:55.519> the<00:11:55.680> most 00:11:55.949 --> 00:11:55.959 align:start position:0% probably the one where there's the most 00:11:55.959 --> 00:11:58.150 align:start position:0% probably the one where there's the most problems<00:11:56.279> with<00:11:56.480> this<00:11:56.720> as<00:11:57.040> our<00:11:57.519> like<00:11:57.680> frame<00:11:57.959> of 00:11:58.150 --> 00:11:58.160 align:start position:0% problems with this as our like frame of 00:11:58.160 --> 00:12:00.269 align:start position:0% problems with this as our like frame of reference<00:11:58.680> is<00:11:58.880> kind<00:11:59.000> of<00:11:59.079> a<00:11:59.279> multi-chain 00:12:00.269 --> 00:12:00.279 align:start position:0% reference is kind of a multi-chain 00:12:00.279 --> 00:12:04.190 align:start position:0% reference is kind of a multi-chain environment<00:12:01.279> and<00:12:01.880> um<00:12:02.880> I<00:12:02.959> mean<00:12:03.279> it<00:12:03.480> starts<00:12:03.920> with 00:12:04.190 --> 00:12:04.200 align:start position:0% environment and um I mean it starts with 00:12:04.200 --> 00:12:06.310 align:start position:0% environment and um I mean it starts with just<00:12:04.440> like<00:12:05.240> it<00:12:05.360> starts<00:12:05.680> with<00:12:05.880> finding 00:12:06.310 --> 00:12:06.320 align:start position:0% just like it starts with finding 00:12:06.320 --> 00:12:10.069 align:start position:0% just like it starts with finding something<00:12:07.279> that<00:12:07.440> can<00:12:07.639> work<00:12:08.120> on<00:12:08.920> um<00:12:09.720> all<00:12:09.959> the 00:12:10.069 --> 00:12:10.079 align:start position:0% something that can work on um all the 00:12:10.079 --> 00:12:12.110 align:start position:0% something that can work on um all the chains<00:12:10.440> that<00:12:10.560> you<00:12:10.680> want<00:12:10.760> to<00:12:10.920> be<00:12:11.079> on<00:12:11.360> right<00:12:11.839> and 00:12:12.110 --> 00:12:12.120 align:start position:0% chains that you want to be on right and 00:12:12.120 --> 00:12:14.509 align:start position:0% chains that you want to be on right and let<00:12:12.279> let's<00:12:12.480> maybe<00:12:12.720> start<00:12:12.920> out<00:12:13.199> just<00:12:13.519> talking 00:12:14.509 --> 00:12:14.519 align:start position:0% let let's maybe start out just talking 00:12:14.519 --> 00:12:16.350 align:start position:0% let let's maybe start out just talking one<00:12:14.920> execution<00:12:15.480> environment<00:12:15.880> let's<00:12:16.040> say<00:12:16.240> we 00:12:16.350 --> 00:12:16.360 align:start position:0% one execution environment let's say we 00:12:16.360 --> 00:12:18.990 align:start position:0% one execution environment let's say we we<00:12:16.519> just<00:12:16.720> stay<00:12:17.000> within<00:12:17.240> the<00:12:17.480> evm<00:12:18.480> even<00:12:18.760> then 00:12:18.990 --> 00:12:19.000 align:start position:0% we just stay within the evm even then 00:12:19.000 --> 00:12:22.509 align:start position:0% we just stay within the evm even then that<00:12:19.120> means<00:12:19.760> if<00:12:19.959> if<00:12:20.120> something<00:12:20.519> like<00:12:20.800> Lei<00:12:21.800> is 00:12:22.509 --> 00:12:22.519 align:start position:0% that means if if something like Lei is 00:12:22.519 --> 00:12:24.269 align:start position:0% that means if if something like Lei is you<00:12:22.639> know<00:12:22.839> expanding<00:12:23.279> to<00:12:23.399> new<00:12:23.560> chains<00:12:24.000> and<00:12:24.120> we 00:12:24.269 --> 00:12:24.279 align:start position:0% you know expanding to new chains and we 00:12:24.279 --> 00:12:27.750 align:start position:0% you know expanding to new chains and we use<00:12:24.480> something<00:12:24.800> like<00:12:25.000> Gip<00:12:25.440> for<00:12:25.639> example<00:12:26.519> to<00:12:27.240> um 00:12:27.750 --> 00:12:27.760 align:start position:0% use something like Gip for example to um 00:12:27.760 --> 00:12:29.629 align:start position:0% use something like Gip for example to um have<00:12:27.959> this<00:12:28.160> kind<00:12:28.279> of<00:12:28.360> like<00:12:28.480> refuel<00:12:28.880> feature 00:12:29.629 --> 00:12:29.639 align:start position:0% have this kind of like refuel feature 00:12:29.639 --> 00:12:31.949 align:start position:0% have this kind of like refuel feature that<00:12:29.839> means<00:12:30.519> that 00:12:31.949 --> 00:12:31.959 align:start position:0% that means that 00:12:31.959 --> 00:12:35.750 align:start position:0% that means that um<00:12:32.959> Gip<00:12:33.399> needs<00:12:33.600> to<00:12:33.800> scale<00:12:34.480> with<00:12:34.680> our<00:12:34.920> own 00:12:35.750 --> 00:12:35.760 align:start position:0% um Gip needs to scale with our own 00:12:35.760 --> 00:12:39.550 align:start position:0% um Gip needs to scale with our own expansion<00:12:36.760> right<00:12:37.440> so<00:12:38.440> we<00:12:38.560> are<00:12:38.800> mostly<00:12:39.360> an 00:12:39.550 --> 00:12:39.560 align:start position:0% expansion right so we are mostly an 00:12:39.560 --> 00:12:42.710 align:start position:0% expansion right so we are mostly an aggregation<00:12:40.160> protocol<00:12:40.959> so<00:12:41.160> we<00:12:41.279> don't<00:12:41.920> build 00:12:42.710 --> 00:12:42.720 align:start position:0% aggregation protocol so we don't build 00:12:42.720 --> 00:12:45.590 align:start position:0% aggregation protocol so we don't build things<00:12:43.720> ourselves<00:12:44.440> necessarily<00:12:45.160> but<00:12:45.399> more 00:12:45.590 --> 00:12:45.600 align:start position:0% things ourselves necessarily but more 00:12:45.600 --> 00:12:48.389 align:start position:0% things ourselves necessarily but more and<00:12:45.760> more<00:12:45.920> so<00:12:46.160> we<00:12:46.320> found<00:12:46.560> ourselves<00:12:47.240> in<00:12:48.240> kind 00:12:48.389 --> 00:12:48.399 align:start position:0% and more so we found ourselves in kind 00:12:48.399 --> 00:12:50.470 align:start position:0% and more so we found ourselves in kind of<00:12:49.240> that<00:12:49.440> tough<00:12:49.639> spot<00:12:49.920> where<00:12:50.040> you<00:12:50.199> have<00:12:50.320> to 00:12:50.470 --> 00:12:50.480 align:start position:0% of that tough spot where you have to 00:12:50.480 --> 00:12:53.310 align:start position:0% of that tough spot where you have to start<00:12:50.720> building<00:12:51.079> things<00:12:51.480> yourself<00:12:52.480> or<00:12:53.120> you 00:12:53.310 --> 00:12:53.320 align:start position:0% start building things yourself or you 00:12:53.320 --> 00:12:55.590 align:start position:0% start building things yourself or you have<00:12:53.480> to<00:12:54.160> build<00:12:54.519> something<00:12:55.040> that's<00:12:55.279> more 00:12:55.590 --> 00:12:55.600 align:start position:0% have to build something that's more 00:12:55.600 --> 00:12:57.750 align:start position:0% have to build something that's more similar<00:12:56.079> to<00:12:56.440> a<00:12:56.600> Marketplace<00:12:57.360> which<00:12:57.480> is<00:12:57.639> kind 00:12:57.750 --> 00:12:57.760 align:start position:0% similar to a Marketplace which is kind 00:12:57.760 --> 00:12:59.790 align:start position:0% similar to a Marketplace which is kind of<00:12:57.959> like<00:12:58.120> what<00:12:58.279> Paras<00:12:58.760> is<00:12:58.839> building 00:12:59.790 --> 00:12:59.800 align:start position:0% of like what Paras is building 00:12:59.800 --> 00:13:04.550 align:start position:0% of like what Paras is building um<00:13:00.240> to<00:13:00.720> attract<00:13:01.720> solvers<00:13:02.560> to<00:13:02.760> attract<00:13:03.560> agents 00:13:04.550 --> 00:13:04.560 align:start position:0% um to attract solvers to attract agents 00:13:04.560 --> 00:13:06.790 align:start position:0% um to attract solvers to attract agents that<00:13:04.760> can<00:13:05.000> execute<00:13:05.560> these<00:13:05.800> transactions 00:13:06.790 --> 00:13:06.800 align:start position:0% that can execute these transactions 00:13:06.800 --> 00:13:09.949 align:start position:0% that can execute these transactions across<00:13:07.360> many<00:13:07.600> many<00:13:07.839> chains<00:13:08.680> so<00:13:09.399> when<00:13:09.560> we<00:13:09.680> start 00:13:09.949 --> 00:13:09.959 align:start position:0% across many many chains so when we start 00:13:09.959 --> 00:13:12.230 align:start position:0% across many many chains so when we start from<00:13:10.279> there 00:13:12.230 --> 00:13:12.240 align:start position:0% from there 00:13:12.240 --> 00:13:15.269 align:start position:0% from there um<00:13:13.240> obviously<00:13:13.839> we<00:13:14.040> have<00:13:14.320> certain<00:13:14.760> Pathways 00:13:15.269 --> 00:13:15.279 align:start position:0% um obviously we have certain Pathways 00:13:15.279 --> 00:13:17.670 align:start position:0% um obviously we have certain Pathways that<00:13:15.399> are<00:13:15.639> very<00:13:15.959> crowded<00:13:16.560> right<00:13:16.760> like<00:13:17.399> every 00:13:17.670 --> 00:13:17.680 align:start position:0% that are very crowded right like every 00:13:17.680 --> 00:13:19.670 align:start position:0% that are very crowded right like every solver<00:13:18.160> wants<00:13:18.399> to<00:13:18.519> solve<00:13:18.800> on<00:13:18.959> Bas<00:13:19.440> every 00:13:19.670 --> 00:13:19.680 align:start position:0% solver wants to solve on Bas every 00:13:19.680 --> 00:13:22.550 align:start position:0% solver wants to solve on Bas every solver<00:13:20.120> wants<00:13:20.320> to<00:13:20.480> solve<00:13:20.839> on<00:13:21.320> arbitrum<00:13:22.320> every 00:13:22.550 --> 00:13:22.560 align:start position:0% solver wants to solve on arbitrum every 00:13:22.560 --> 00:13:24.870 align:start position:0% solver wants to solve on arbitrum every solver<00:13:23.320> you<00:13:23.440> know<00:13:23.800> eventually<00:13:24.160> wants<00:13:24.360> to 00:13:24.870 --> 00:13:24.880 align:start position:0% solver you know eventually wants to 00:13:24.880 --> 00:13:26.430 align:start position:0% solver you know eventually wants to solve<00:13:25.160> on<00:13:25.279> like<00:13:25.440> bar<00:13:25.720> chain<00:13:25.920> or<00:13:26.040> Monet 00:13:26.430 --> 00:13:26.440 align:start position:0% solve on like bar chain or Monet 00:13:26.440 --> 00:13:29.110 align:start position:0% solve on like bar chain or Monet whenever<00:13:26.760> these<00:13:26.959> chains<00:13:27.160> are<00:13:27.519> launching<00:13:28.519> um 00:13:29.110 --> 00:13:29.120 align:start position:0% whenever these chains are launching um 00:13:29.120 --> 00:13:31.629 align:start position:0% whenever these chains are launching um for<00:13:29.240> the<00:13:29.320> more<00:13:29.519> long<00:13:29.839> tale<00:13:30.480> of 00:13:31.629 --> 00:13:31.639 align:start position:0% for the more long tale of 00:13:31.639 --> 00:13:34.750 align:start position:0% for the more long tale of chains<00:13:32.639> um<00:13:33.160> that's<00:13:33.360> probably<00:13:33.600> more<00:13:33.959> difficult 00:13:34.750 --> 00:13:34.760 align:start position:0% chains um that's probably more difficult 00:13:34.760 --> 00:13:36.590 align:start position:0% chains um that's probably more difficult um<00:13:34.959> there<00:13:35.040> might<00:13:35.199> have<00:13:35.320> to<00:13:35.440> be<00:13:36.240> different 00:13:36.590 --> 00:13:36.600 align:start position:0% um there might have to be different 00:13:36.600 --> 00:13:39.470 align:start position:0% um there might have to be different solutions<00:13:37.199> of<00:13:37.360> how<00:13:37.440> to<00:13:37.600> do<00:13:37.800> that<00:13:38.639> and<00:13:38.839> then<00:13:39.320> the 00:13:39.470 --> 00:13:39.480 align:start position:0% solutions of how to do that and then the 00:13:39.480 --> 00:13:41.629 align:start position:0% solutions of how to do that and then the other<00:13:39.720> issue<00:13:39.959> of<00:13:40.079> scalability<00:13:41.000> that<00:13:41.160> comes<00:13:41.440> to 00:13:41.629 --> 00:13:41.639 align:start position:0% other issue of scalability that comes to 00:13:41.639 --> 00:13:43.069 align:start position:0% other issue of scalability that comes to be<00:13:42.079> is 00:13:43.069 --> 00:13:43.079 align:start position:0% be is 00:13:43.079 --> 00:13:46.389 align:start position:0% be is like<00:13:44.079> how<00:13:44.240> do<00:13:44.360> you<00:13:44.560> do<00:13:44.880> that<00:13:45.560> cross<00:13:46.079> different 00:13:46.389 --> 00:13:46.399 align:start position:0% like how do you do that cross different 00:13:46.399 --> 00:13:49.110 align:start position:0% like how do you do that cross different virtual<00:13:46.959> machines<00:13:47.959> um<00:13:48.240> and<00:13:48.440> how<00:13:48.600> do<00:13:48.880> these 00:13:49.110 --> 00:13:49.120 align:start position:0% virtual machines um and how do these 00:13:49.120 --> 00:13:51.990 align:start position:0% virtual machines um and how do these agents<00:13:49.680> and<00:13:49.839> the<00:13:50.000> protocols<00:13:50.800> that<00:13:51.639> have<00:13:51.839> the 00:13:51.990 --> 00:13:52.000 align:start position:0% agents and the protocols that have the 00:13:52.000 --> 00:13:54.550 align:start position:0% agents and the protocols that have the marketplaces<00:13:52.720> start<00:13:53.079> talking<00:13:53.360> to<00:13:53.560> each<00:13:53.759> other 00:13:54.550 --> 00:13:54.560 align:start position:0% marketplaces start talking to each other 00:13:54.560 --> 00:13:56.550 align:start position:0% marketplaces start talking to each other across<00:13:55.000> these<00:13:55.519> environments<00:13:56.160> and<00:13:56.279> then<00:13:56.440> we 00:13:56.550 --> 00:13:56.560 align:start position:0% across these environments and then we 00:13:56.560 --> 00:13:58.069 align:start position:0% across these environments and then we have<00:13:56.680> to<00:13:56.800> go<00:13:56.920> into<00:13:57.160> something<00:13:57.480> like<00:13:57.639> message 00:13:58.069 --> 00:13:58.079 align:start position:0% have to go into something like message 00:13:58.079 --> 00:14:01.230 align:start position:0% have to go into something like message passing<00:13:59.279> um<00:13:59.680> we<00:13:59.839> have<00:13:59.920> to<00:14:00.040> go<00:14:00.199> into<00:14:00.480> something 00:14:01.230 --> 00:14:01.240 align:start position:0% passing um we have to go into something 00:14:01.240 --> 00:14:04.310 align:start position:0% passing um we have to go into something like<00:14:02.240> building<00:14:02.839> multiple<00:14:03.360> versions<00:14:03.920> of<00:14:04.120> these 00:14:04.310 --> 00:14:04.320 align:start position:0% like building multiple versions of these 00:14:04.320 --> 00:14:07.470 align:start position:0% like building multiple versions of these protocols<00:14:05.320> so<00:14:05.920> um<00:14:06.160> I<00:14:06.240> think<00:14:06.440> when<00:14:06.560> it<00:14:06.680> comes<00:14:06.920> to 00:14:07.470 --> 00:14:07.480 align:start position:0% protocols so um I think when it comes to 00:14:07.480 --> 00:14:09.189 align:start position:0% protocols so um I think when it comes to this<00:14:07.839> end<00:14:08.040> of<00:14:08.199> the<00:14:08.279> scalability<00:14:08.839> we're<00:14:09.000> still 00:14:09.189 --> 00:14:09.199 align:start position:0% this end of the scalability we're still 00:14:09.199 --> 00:14:11.470 align:start position:0% this end of the scalability we're still pretty<00:14:09.440> early<00:14:10.360> um<00:14:10.560> and<00:14:10.720> nobody<00:14:11.120> has<00:14:11.320> like 00:14:11.470 --> 00:14:11.480 align:start position:0% pretty early um and nobody has like 00:14:11.480 --> 00:14:14.310 align:start position:0% pretty early um and nobody has like really<00:14:11.759> figured<00:14:12.720> that<00:14:12.880> out<00:14:13.120> yet<00:14:13.440> but<00:14:13.880> um<00:14:14.240> if 00:14:14.310 --> 00:14:14.320 align:start position:0% really figured that out yet but um if 00:14:14.320 --> 00:14:16.269 align:start position:0% really figured that out yet but um if you<00:14:14.440> think<00:14:14.680> about<00:14:14.920> it<00:14:15.360> we<00:14:15.519> just<00:14:15.680> talked<00:14:15.959> about 00:14:16.269 --> 00:14:16.279 align:start position:0% you think about it we just talked about 00:14:16.279 --> 00:14:19.150 align:start position:0% you think about it we just talked about how<00:14:16.480> these<00:14:16.639> intent<00:14:17.079> types<00:14:17.839> basically<00:14:18.399> make 00:14:19.150 --> 00:14:19.160 align:start position:0% how these intent types basically make 00:14:19.160 --> 00:14:21.470 align:start position:0% how these intent types basically make the<00:14:19.320> ecosystem<00:14:20.320> much<00:14:20.519> more<00:14:20.800> much<00:14:20.959> easier<00:14:21.320> to 00:14:21.470 --> 00:14:21.480 align:start position:0% the ecosystem much more much easier to 00:14:21.480 --> 00:14:23.310 align:start position:0% the ecosystem much more much easier to use<00:14:21.920> where<00:14:22.360> ecosystems<00:14:22.880> where<00:14:23.000> you<00:14:23.160> don't 00:14:23.310 --> 00:14:23.320 align:start position:0% use where ecosystems where you don't 00:14:23.320 --> 00:14:25.590 align:start position:0% use where ecosystems where you don't have<00:14:23.480> all<00:14:23.639> these<00:14:23.800> things<00:14:24.079> yet<00:14:24.279> you<00:14:24.440> kind<00:14:24.600> of 00:14:25.590 --> 00:14:25.600 align:start position:0% have all these things yet you kind of 00:14:25.600 --> 00:14:26.910 align:start position:0% have all these things yet you kind of it's<00:14:25.759> It's<00:14:25.920> kind<00:14:26.040> of<00:14:26.160> the<00:14:26.279> similar<00:14:26.759> the 00:14:26.910 --> 00:14:26.920 align:start position:0% it's It's kind of the similar the 00:14:26.920 --> 00:14:28.030 align:start position:0% it's It's kind of the similar the difference<00:14:27.199> between<00:14:27.399> a<00:14:27.519> transaction<00:14:27.880> and 00:14:28.030 --> 00:14:28.040 align:start position:0% difference between a transaction and 00:14:28.040 --> 00:14:29.949 align:start position:0% difference between a transaction and intent<00:14:28.440> right<00:14:28.600> is<00:14:28.759> like<00:14:29.120> you<00:14:29.240> have<00:14:29.360> to<00:14:29.480> find<00:14:29.720> a 00:14:29.949 --> 00:14:29.959 align:start position:0% intent right is like you have to find a 00:14:29.959 --> 00:14:31.870 align:start position:0% intent right is like you have to find a pathway<00:14:30.360> yourself<00:14:30.800> still<00:14:31.399> which<00:14:31.560> makes<00:14:31.720> it 00:14:31.870 --> 00:14:31.880 align:start position:0% pathway yourself still which makes it 00:14:31.880 --> 00:14:34.749 align:start position:0% pathway yourself still which makes it like<00:14:32.040> much<00:14:32.199> harder<00:14:32.440> to<00:14:32.600> navigate<00:14:33.079> these<00:14:33.920> um<00:14:34.519> so 00:14:34.749 --> 00:14:34.759 align:start position:0% like much harder to navigate these um so 00:14:34.759 --> 00:14:36.509 align:start position:0% like much harder to navigate these um so yeah<00:14:34.959> I<00:14:35.040> think<00:14:35.279> it's<00:14:35.600> it's<00:14:35.759> in<00:14:35.880> some<00:14:36.079> ways<00:14:36.399> if 00:14:36.509 --> 00:14:36.519 align:start position:0% yeah I think it's it's in some ways if 00:14:36.519 --> 00:14:38.189 align:start position:0% yeah I think it's it's in some ways if somebody<00:14:36.800> can<00:14:37.079> build<00:14:37.360> something<00:14:37.839> that 00:14:38.189 --> 00:14:38.199 align:start position:0% somebody can build something that 00:14:38.199 --> 00:14:39.710 align:start position:0% somebody can build something that abstracts<00:14:38.639> all<00:14:38.759> of<00:14:38.880> that<00:14:39.079> way<00:14:39.320> across<00:14:39.600> all 00:14:39.710 --> 00:14:39.720 align:start position:0% abstracts all of that way across all 00:14:39.720 --> 00:14:40.870 align:start position:0% abstracts all of that way across all these<00:14:39.880> different<00:14:40.160> environments<00:14:40.680> that's 00:14:40.870 --> 00:14:40.880 align:start position:0% these different environments that's 00:14:40.880 --> 00:14:42.990 align:start position:0% these different environments that's probably<00:14:41.120> like<00:14:41.240> the<00:14:41.320> Holy<00:14:41.639> Grail<00:14:42.639> of<00:14:42.800> that 00:14:42.990 --> 00:14:43.000 align:start position:0% probably like the Holy Grail of that 00:14:43.000 --> 00:14:45.910 align:start position:0% probably like the Holy Grail of that entire<00:14:43.560> Market<00:14:44.000> of<00:14:44.320> like<00:14:44.920> liquidity<00:14:45.440> routing 00:14:45.910 --> 00:14:45.920 align:start position:0% entire Market of like liquidity routing 00:14:45.920 --> 00:14:47.310 align:start position:0% entire Market of like liquidity routing but<00:14:46.040> it's<00:14:46.160> a<00:14:46.320> really<00:14:46.560> really<00:14:46.759> tough<00:14:47.040> problem 00:14:47.310 --> 00:14:47.320 align:start position:0% but it's a really really tough problem 00:14:47.320 --> 00:14:48.790 align:start position:0% but it's a really really tough problem to 00:14:48.790 --> 00:14:48.800 align:start position:0% to 00:14:48.800 --> 00:14:51.509 align:start position:0% to solve<00:14:49.800> okay<00:14:49.959> so<00:14:50.240> you<00:14:50.399> are<00:14:50.639> focusing<00:14:51.120> on<00:14:51.279> the 00:14:51.509 --> 00:14:51.519 align:start position:0% solve okay so you are focusing on the 00:14:51.519 --> 00:14:53.829 align:start position:0% solve okay so you are focusing on the composability<00:14:52.079> of<00:14:52.720> that<00:14:53.040> uh<00:14:53.399> of<00:14:53.600> that 00:14:53.829 --> 00:14:53.839 align:start position:0% composability of that uh of that 00:14:53.839 --> 00:14:57.230 align:start position:0% composability of that uh of that ecosystem<00:14:54.800> besides<00:14:55.360> improving<00:14:56.360> the<00:14:56.720> external 00:14:57.230 --> 00:14:57.240 align:start position:0% ecosystem besides improving the external 00:14:57.240 --> 00:14:59.350 align:start position:0% ecosystem besides improving the external experience<00:14:57.680> for<00:14:57.839> user<00:14:58.199> you<00:14:58.320> are<00:14:58.480> also 00:14:59.350 --> 00:14:59.360 align:start position:0% experience for user you are also 00:14:59.360 --> 00:15:01.590 align:start position:0% experience for user you are also focusing<00:14:59.800> on<00:15:00.480> improving<00:15:00.920> this<00:15:01.160> composability 00:15:01.590 --> 00:15:01.600 align:start position:0% focusing on improving this composability 00:15:01.600 --> 00:15:03.509 align:start position:0% focusing on improving this composability for<00:15:02.160> the<00:15:02.360> protocols<00:15:02.759> that<00:15:02.880> need<00:15:03.040> to<00:15:03.199> connect 00:15:03.509 --> 00:15:03.519 align:start position:0% for the protocols that need to connect 00:15:03.519 --> 00:15:05.350 align:start position:0% for the protocols that need to connect to<00:15:03.839> to<00:15:04.160> to<00:15:04.560> yeah<00:15:04.680> like<00:15:04.839> just<00:15:04.959> think<00:15:05.160> about 00:15:05.350 --> 00:15:05.360 align:start position:0% to to to yeah like just think about 00:15:05.360 --> 00:15:07.030 align:start position:0% to to to yeah like just think about something<00:15:05.920> as<00:15:06.040> I<00:15:06.120> said<00:15:06.279> earlier<00:15:06.560> we<00:15:06.680> support 00:15:07.030 --> 00:15:07.040 align:start position:0% something as I said earlier we support 00:15:07.040 --> 00:15:09.550 align:start position:0% something as I said earlier we support Solana<00:15:07.639> evm<00:15:08.120> and<00:15:08.279> Bitcoin<00:15:08.880> but<00:15:09.040> that<00:15:09.279> also 00:15:09.550 --> 00:15:09.560 align:start position:0% Solana evm and Bitcoin but that also 00:15:09.560 --> 00:15:12.870 align:start position:0% Solana evm and Bitcoin but that also means<00:15:10.120> that<00:15:10.440> currently<00:15:10.959> the<00:15:11.079> user<00:15:11.440> has<00:15:11.639> to<00:15:12.639> um 00:15:12.870 --> 00:15:12.880 align:start position:0% means that currently the user has to um 00:15:12.880 --> 00:15:14.790 align:start position:0% means that currently the user has to um use<00:15:13.199> three<00:15:13.440> different<00:15:14.000> wallet<00:15:14.320> types<00:15:14.639> because 00:15:14.790 --> 00:15:14.800 align:start position:0% use three different wallet types because 00:15:14.800 --> 00:15:16.790 align:start position:0% use three different wallet types because you<00:15:14.920> need<00:15:15.079> a<00:15:15.360> phantom<00:15:16.000> wallet<00:15:16.320> whatever<00:15:16.639> on 00:15:16.790 --> 00:15:16.800 align:start position:0% you need a phantom wallet whatever on 00:15:16.800 --> 00:15:18.150 align:start position:0% you need a phantom wallet whatever on Solana<00:15:17.320> and<00:15:17.399> then<00:15:17.519> you<00:15:17.600> need<00:15:17.720> a<00:15:17.800> Bitcoin 00:15:18.150 --> 00:15:18.160 align:start position:0% Solana and then you need a Bitcoin 00:15:18.160 --> 00:15:20.629 align:start position:0% Solana and then you need a Bitcoin wallet<00:15:18.519> need<00:15:19.399> whatever<00:15:19.680> you're<00:15:19.800> using<00:15:20.120> on<00:15:20.279> the 00:15:20.629 --> 00:15:20.639 align:start position:0% wallet need whatever you're using on the 00:15:20.639 --> 00:15:24.310 align:start position:0% wallet need whatever you're using on the evm<00:15:21.639> um<00:15:22.639> the<00:15:22.759> end<00:15:23.079> game<00:15:23.240> of<00:15:23.399> this<00:15:23.720> is<00:15:23.920> to<00:15:24.120> have 00:15:24.310 --> 00:15:24.320 align:start position:0% evm um the end game of this is to have 00:15:24.320 --> 00:15:27.110 align:start position:0% evm um the end game of this is to have some<00:15:24.600> kind<00:15:24.759> of<00:15:25.240> signature<00:15:25.839> abstraction<00:15:26.440> game 00:15:27.110 --> 00:15:27.120 align:start position:0% some kind of signature abstraction game 00:15:27.120 --> 00:15:29.590 align:start position:0% some kind of signature abstraction game that<00:15:27.279> allows<00:15:27.720> you<00:15:28.000> to<00:15:28.600> basically<00:15:29.160> compos 00:15:29.590 --> 00:15:29.600 align:start position:0% that allows you to basically compos 00:15:29.600 --> 00:15:31.829 align:start position:0% that allows you to basically compos signatures<00:15:30.240> across<00:15:30.519> multiple<00:15:30.880> chains 00:15:31.829 --> 00:15:31.839 align:start position:0% signatures across multiple chains 00:15:31.839 --> 00:15:33.749 align:start position:0% signatures across multiple chains probably<00:15:32.240> with<00:15:32.440> something<00:15:32.720> like<00:15:32.880> ZK<00:15:33.319> proofs 00:15:33.749 --> 00:15:33.759 align:start position:0% probably with something like ZK proofs 00:15:33.759 --> 00:15:37.430 align:start position:0% probably with something like ZK proofs or<00:15:34.040> MPC<00:15:34.720> or<00:15:34.920> whatever<00:15:35.519> you<00:15:35.920> um<00:15:36.160> prefer 00:15:37.430 --> 00:15:37.440 align:start position:0% or MPC or whatever you um prefer 00:15:37.440 --> 00:15:40.470 align:start position:0% or MPC or whatever you um prefer cryptographically<00:15:38.480> um<00:15:39.480> and<00:15:39.959> that's<00:15:40.199> kind<00:15:40.319> of 00:15:40.470 --> 00:15:40.480 align:start position:0% cryptographically um and that's kind of 00:15:40.480 --> 00:15:43.430 align:start position:0% cryptographically um and that's kind of like<00:15:40.680> the<00:15:40.839> next<00:15:41.199> level<00:15:41.680> of<00:15:42.600> intense<00:15:43.040> in<00:15:43.160> a<00:15:43.279> way 00:15:43.430 --> 00:15:43.440 align:start position:0% like the next level of intense in a way 00:15:43.440 --> 00:15:44.430 align:start position:0% like the next level of intense in a way because<00:15:43.600> that's<00:15:43.759> kind<00:15:43.880> of<00:15:44.000> what<00:15:44.079> you<00:15:44.199> guys<00:15:44.319> are 00:15:44.430 --> 00:15:44.440 align:start position:0% because that's kind of what you guys are 00:15:44.440 --> 00:15:46.509 align:start position:0% because that's kind of what you guys are doing<00:15:44.720> right<00:15:44.880> you<00:15:45.079> abstracted<00:15:45.480> it<00:15:45.680> on<00:15:45.880> DVM<00:15:46.399> but 00:15:46.509 --> 00:15:46.519 align:start position:0% doing right you abstracted it on DVM but 00:15:46.519 --> 00:15:48.430 align:start position:0% doing right you abstracted it on DVM but the<00:15:46.639> next<00:15:46.839> level<00:15:47.079> is<00:15:47.639> how<00:15:47.759> do<00:15:47.839> you<00:15:47.959> make<00:15:48.079> it 00:15:48.430 --> 00:15:48.440 align:start position:0% the next level is how do you make it 00:15:48.440 --> 00:15:50.150 align:start position:0% the next level is how do you make it even<00:15:48.639> more<00:15:48.920> composable<00:15:49.560> across<00:15:49.959> these 00:15:50.150 --> 00:15:50.160 align:start position:0% even more composable across these 00:15:50.160 --> 00:15:54.309 align:start position:0% even more composable across these different<00:15:50.880> ecosystems<00:15:51.880> that's 00:15:54.309 --> 00:15:54.319 align:start position:0% 00:15:54.319 --> 00:15:57.829 align:start position:0% correct<00:15:55.319> okay<00:15:55.639> so<00:15:56.480> the<00:15:56.639> way<00:15:56.839> we<00:15:57.000> see<00:15:57.279> it<00:15:57.680> is 00:15:57.829 --> 00:15:57.839 align:start position:0% correct okay so the way we see it is 00:15:57.839 --> 00:15:59.629 align:start position:0% correct okay so the way we see it is more<00:15:58.079> about<00:15:58.360> if<00:15:58.440> you<00:15:58.560> want<00:15:58.639> to<00:15:59.040> like<00:15:59.279> lower 00:15:59.629 --> 00:15:59.639 align:start position:0% more about if you want to like lower 00:15:59.639 --> 00:16:01.949 align:start position:0% more about if you want to like lower that<00:15:59.800> barrier<00:16:00.240> entrance<00:16:01.240> maybe<00:16:01.480> you<00:16:01.720> need<00:16:01.839> to 00:16:01.949 --> 00:16:01.959 align:start position:0% that barrier entrance maybe you need to 00:16:01.959 --> 00:16:04.550 align:start position:0% that barrier entrance maybe you need to think<00:16:02.160> it<00:16:02.319> as<00:16:03.079> for<00:16:03.240> example<00:16:03.560> if<00:16:03.720> you're<00:16:04.199> in<00:16:04.360> a 00:16:04.550 --> 00:16:04.560 align:start position:0% think it as for example if you're in a 00:16:04.560 --> 00:16:06.670 align:start position:0% think it as for example if you're in a room<00:16:05.000> you<00:16:05.079> want<00:16:05.199> to<00:16:05.319> communicate<00:16:06.000> to<00:16:06.240> another 00:16:06.670 --> 00:16:06.680 align:start position:0% room you want to communicate to another 00:16:06.680 --> 00:16:10.629 align:start position:0% room you want to communicate to another room<00:16:07.680> if<00:16:07.880> you<00:16:08.880> feel<00:16:09.160> like<00:16:09.519> like<00:16:09.759> two<00:16:10.079> isolated 00:16:10.629 --> 00:16:10.639 align:start position:0% room if you feel like like two isolated 00:16:10.639 --> 00:16:13.110 align:start position:0% room if you feel like like two isolated things<00:16:11.000> right<00:16:11.519> if<00:16:11.600> you<00:16:11.759> find<00:16:11.959> the<00:16:12.160> way<00:16:12.839> how<00:16:12.959> to 00:16:13.110 --> 00:16:13.120 align:start position:0% things right if you find the way how to 00:16:13.120 --> 00:16:15.629 align:start position:0% things right if you find the way how to communicate<00:16:13.519> with<00:16:13.680> those<00:16:14.519> like<00:16:15.240> then<00:16:15.360> you<00:16:15.480> can 00:16:15.629 --> 00:16:15.639 align:start position:0% communicate with those like then you can 00:16:15.639 --> 00:16:17.269 align:start position:0% communicate with those like then you can communicate<00:16:16.000> to<00:16:16.160> others<00:16:16.360> too<00:16:16.680> right<00:16:17.079> and<00:16:17.199> you 00:16:17.269 --> 00:16:17.279 align:start position:0% communicate to others too right and you 00:16:17.279 --> 00:16:19.790 align:start position:0% communicate to others too right and you can<00:16:17.440> get<00:16:17.560> to<00:16:17.720> more<00:16:17.959> and<00:16:18.120> more<00:16:18.279> and<00:16:18.399> more<00:16:18.800> places 00:16:19.790 --> 00:16:19.800 align:start position:0% can get to more and more and more places 00:16:19.800 --> 00:16:23.269 align:start position:0% can get to more and more and more places so<00:16:20.279> it's<00:16:20.880> about<00:16:21.880> looking<00:16:22.160> at<00:16:22.360> that<00:16:22.519> connector 00:16:23.269 --> 00:16:23.279 align:start position:0% so it's about looking at that connector 00:16:23.279 --> 00:16:25.189 align:start position:0% so it's about looking at that connector and<00:16:23.720> it<00:16:23.839> may<00:16:24.120> happens<00:16:24.360> all<00:16:24.519> the<00:16:24.639> time<00:16:24.920> with<00:16:25.079> all 00:16:25.189 --> 00:16:25.199 align:start position:0% and it may happens all the time with all 00:16:25.199 --> 00:16:26.790 align:start position:0% and it may happens all the time with all of<00:16:25.319> our<00:16:25.480> times<00:16:25.759> we<00:16:25.880> have<00:16:26.000> and<00:16:26.160> all<00:16:26.279> the<00:16:26.600> people 00:16:26.790 --> 00:16:26.800 align:start position:0% of our times we have and all the people 00:16:26.800 --> 00:16:28.030 align:start position:0% of our times we have and all the people that<00:16:26.920> want<00:16:27.000> to<00:16:27.079> say<00:16:27.319> hey<00:16:27.440> I<00:16:27.480> want<00:16:27.600> to<00:16:27.680> automate 00:16:28.030 --> 00:16:28.040 align:start position:0% that want to say hey I want to automate 00:16:28.040 --> 00:16:30.269 align:start position:0% that want to say hey I want to automate I<00:16:28.120> want<00:16:28.199> to<00:16:28.319> do<00:16:28.480> this<00:16:28.560> and<00:16:28.720> that<00:16:29.360> we<00:16:29.519> act<00:16:29.720> as 00:16:30.269 --> 00:16:30.279 align:start position:0% I want to do this and that we act as 00:16:30.279 --> 00:16:33.230 align:start position:0% I want to do this and that we act as intermediaries<00:16:31.279> to<00:16:31.480> the<00:16:31.680> solution<00:16:32.360> so 00:16:33.230 --> 00:16:33.240 align:start position:0% intermediaries to the solution so 00:16:33.240 --> 00:16:36.030 align:start position:0% intermediaries to the solution so intents<00:16:33.600> for<00:16:33.839> us<00:16:34.120> are<00:16:34.399> that<00:16:35.079> that<00:16:35.440> looking<00:16:35.759> for 00:16:36.030 --> 00:16:36.040 align:start position:0% intents for us are that that looking for 00:16:36.040 --> 00:16:38.350 align:start position:0% intents for us are that that looking for that<00:16:36.360> path<00:16:37.120> that<00:16:37.440> execution<00:16:37.959> plan<00:16:38.199> that<00:16:38.279> you 00:16:38.350 --> 00:16:38.360 align:start position:0% that path that execution plan that you 00:16:38.360 --> 00:16:41.389 align:start position:0% that path that execution plan that you want<00:16:38.480> to<00:16:38.720> have<00:16:39.519> and<00:16:39.880> seek<00:16:40.199> the<00:16:40.360> best<00:16:40.560> way<00:16:40.720> to 00:16:41.389 --> 00:16:41.399 align:start position:0% want to have and seek the best way to 00:16:41.399 --> 00:16:43.269 align:start position:0% want to have and seek the best way to get<00:16:41.560> all<00:16:41.720> those<00:16:41.959> connections<00:16:42.600> and<00:16:42.800> get<00:16:43.079> to 00:16:43.269 --> 00:16:43.279 align:start position:0% get all those connections and get to 00:16:43.279 --> 00:16:45.990 align:start position:0% get all those connections and get to more<00:16:43.440> and<00:16:43.560> more<00:16:43.759> use<00:16:44.160> cases<00:16:44.639> scalability 00:16:45.990 --> 00:16:46.000 align:start position:0% more and more use cases scalability 00:16:46.000 --> 00:16:48.870 align:start position:0% more and more use cases scalability cation<00:16:47.000> so<00:16:47.240> kind<00:16:47.399> of<00:16:47.680> uh<00:16:47.880> standardizing<00:16:48.680> those 00:16:48.870 --> 00:16:48.880 align:start position:0% cation so kind of uh standardizing those 00:16:48.880 --> 00:16:50.910 align:start position:0% cation so kind of uh standardizing those connections<00:16:49.519> so<00:16:49.720> using<00:16:50.040> the<00:16:50.199> same<00:16:50.480> connection 00:16:50.910 --> 00:16:50.920 align:start position:0% connections so using the same connection 00:16:50.920 --> 00:16:52.990 align:start position:0% connections so using the same connection that<00:16:51.040> you<00:16:51.199> have<00:16:51.560> from<00:16:51.759> one<00:16:51.959> room<00:16:52.399> going<00:16:52.720> going 00:16:52.990 --> 00:16:53.000 align:start position:0% that you have from one room going going 00:16:53.000 --> 00:16:54.670 align:start position:0% that you have from one room going going to<00:16:53.120> the<00:16:53.279> example<00:16:53.759> from<00:16:53.920> one<00:16:54.120> room<00:16:54.360> to<00:16:54.519> the 00:16:54.670 --> 00:16:54.680 align:start position:0% to the example from one room to the 00:16:54.680 --> 00:16:56.829 align:start position:0% to the example from one room to the other<00:16:55.279> but<00:16:55.480> also<00:16:55.680> to<00:16:55.839> connect<00:16:56.240> other<00:16:56.600> other 00:16:56.829 --> 00:16:56.839 align:start position:0% other but also to connect other other 00:16:56.839 --> 00:16:58.590 align:start position:0% other but also to connect other other partners<00:16:57.199> for<00:16:57.399> you<00:16:57.639> for<00:16:57.800> example<00:16:58.399> yeah<00:16:58.519> it's 00:16:58.590 --> 00:16:58.600 align:start position:0% partners for you for example yeah it's 00:16:58.600 --> 00:17:01.350 align:start position:0% partners for you for example yeah it's going<00:16:59.079> like<00:16:59.240> like<00:16:59.360> KN<00:16:59.639> how<00:16:59.839> we<00:17:00.040> have<00:17:00.279> in<00:17:01.160> like 00:17:01.350 --> 00:17:01.360 align:start position:0% going like like KN how we have in like 00:17:01.360 --> 00:17:03.629 align:start position:0% going like like KN how we have in like it<00:17:01.480> happens<00:17:01.839> with<00:17:02.120> some<00:17:02.360> protocols<00:17:02.959> and<00:17:03.240> then 00:17:03.629 --> 00:17:03.639 align:start position:0% it happens with some protocols and then 00:17:03.639 --> 00:17:05.949 align:start position:0% it happens with some protocols and then we<00:17:03.839> can<00:17:04.480> like<00:17:05.120> have<00:17:05.280> the<00:17:05.400> experience<00:17:05.760> that<00:17:05.839> we 00:17:05.949 --> 00:17:05.959 align:start position:0% we can like have the experience that we 00:17:05.959 --> 00:17:07.590 align:start position:0% we can like have the experience that we have<00:17:06.079> with<00:17:06.199> one<00:17:06.480> and<00:17:06.640> then<00:17:06.880> standardize<00:17:07.360> it<00:17:07.520> in 00:17:07.590 --> 00:17:07.600 align:start position:0% have with one and then standardize it in 00:17:07.600 --> 00:17:10.710 align:start position:0% have with one and then standardize it in order<00:17:07.919> like<00:17:08.079> to<00:17:08.439> reach<00:17:08.760> more<00:17:09.600> and<00:17:10.280> access<00:17:10.559> like 00:17:10.710 --> 00:17:10.720 align:start position:0% order like to reach more and access like 00:17:10.720 --> 00:17:11.990 align:start position:0% order like to reach more and access like more<00:17:10.880> information<00:17:11.199> on 00:17:11.990 --> 00:17:12.000 align:start position:0% more information on 00:17:12.000 --> 00:17:16.350 align:start position:0% more information on that 00:17:16.350 --> 00:17:16.360 align:start position:0% 00:17:16.360 --> 00:17:19.870 align:start position:0% great<00:17:17.360> yeah<00:17:17.559> so<00:17:17.760> for<00:17:18.079> sorry<00:17:18.640> so<00:17:18.839> for<00:17:19.039> us<00:17:19.480> um<00:17:19.799> I 00:17:19.870 --> 00:17:19.880 align:start position:0% great yeah so for sorry so for us um I 00:17:19.880 --> 00:17:22.029 align:start position:0% great yeah so for sorry so for us um I think<00:17:20.079> the<00:17:20.199> biggest<00:17:20.439> thing<00:17:20.640> was<00:17:21.360> um<00:17:21.520> for<00:17:21.839> for 00:17:22.029 --> 00:17:22.039 align:start position:0% think the biggest thing was um for for 00:17:22.039 --> 00:17:25.590 align:start position:0% think the biggest thing was um for for liquidity<00:17:22.520> Hub<00:17:23.520> um<00:17:23.760> we'd<00:17:24.039> have<00:17:24.799> um<00:17:24.959> dexes<00:17:25.439> that 00:17:25.590 --> 00:17:25.600 align:start position:0% liquidity Hub um we'd have um dexes that 00:17:25.600 --> 00:17:29.150 align:start position:0% liquidity Hub um we'd have um dexes that really<00:17:25.799> really<00:17:25.959> want<00:17:26.120> to<00:17:26.520> integrate<00:17:27.520> um<00:17:28.079> the 00:17:29.150 --> 00:17:29.160 align:start position:0% really really want to integrate um the 00:17:29.160 --> 00:17:32.070 align:start position:0% really really want to integrate um the the<00:17:29.440> the<00:17:29.600> the<00:17:29.720> protocol<00:17:30.440> on<00:17:30.720> on<00:17:30.880> their<00:17:31.400> UI<00:17:31.880> but 00:17:32.070 --> 00:17:32.080 align:start position:0% the the the protocol on on their UI but 00:17:32.080 --> 00:17:33.590 align:start position:0% the the the protocol on on their UI but then<00:17:32.360> you<00:17:32.440> know<00:17:32.600> when<00:17:32.760> we<00:17:32.880> look<00:17:33.080> at<00:17:33.200> the<00:17:33.360> actual 00:17:33.590 --> 00:17:33.600 align:start position:0% then you know when we look at the actual 00:17:33.600 --> 00:17:36.230 align:start position:0% then you know when we look at the actual chain<00:17:33.919> itself<00:17:34.600> there's<00:17:34.799> maybe<00:17:35.280> only<00:17:35.559> one<00:17:35.799> or 00:17:36.230 --> 00:17:36.240 align:start position:0% chain itself there's maybe only one or 00:17:36.240 --> 00:17:39.150 align:start position:0% chain itself there's maybe only one or two<00:17:37.240> um<00:17:37.440> solvers<00:17:38.000> there<00:17:38.200> that<00:17:38.320> are<00:17:38.640> that<00:17:38.720> are 00:17:39.150 --> 00:17:39.160 align:start position:0% two um solvers there that are that are 00:17:39.160 --> 00:17:41.470 align:start position:0% two um solvers there that are that are facilitating<00:17:39.679> orders<00:17:40.200> on<00:17:40.840> on<00:17:41.039> the<00:17:41.240> on<00:17:41.360> the 00:17:41.470 --> 00:17:41.480 align:start position:0% facilitating orders on on the on the 00:17:41.480 --> 00:17:43.990 align:start position:0% facilitating orders on on the on the Chain<00:17:41.960> so<00:17:42.520> for<00:17:43.080> you<00:17:43.200> know<00:17:43.320> for<00:17:43.559> something<00:17:43.840> like 00:17:43.990 --> 00:17:44.000 align:start position:0% Chain so for you know for something like 00:17:44.000 --> 00:17:46.110 align:start position:0% Chain so for you know for something like polygon<00:17:44.559> where<00:17:45.559> um<00:17:45.720> you<00:17:45.799> know<00:17:45.919> we<00:17:46.039> have 00:17:46.110 --> 00:17:46.120 align:start position:0% polygon where um you know we have 00:17:46.120 --> 00:17:50.230 align:start position:0% polygon where um you know we have everyone<00:17:46.520> added<00:17:47.400> um<00:17:47.919> odos<00:17:48.480> open<00:17:49.240> uh<00:17:49.520> oos<00:17:50.039> open 00:17:50.230 --> 00:17:50.240 align:start position:0% everyone added um odos open uh oos open 00:17:50.240 --> 00:17:52.870 align:start position:0% everyone added um odos open uh oos open oer<00:17:50.720> Power<00:17:50.960> Swap<00:17:51.280> obviously<00:17:52.240> um<00:17:52.360> and<00:17:52.480> offchain 00:17:52.870 --> 00:17:52.880 align:start position:0% oer Power Swap obviously um and offchain 00:17:52.880 --> 00:17:55.870 align:start position:0% oer Power Swap obviously um and offchain liquidity<00:17:53.360> as<00:17:53.480> well<00:17:53.919> it's<00:17:54.039> like<00:17:54.240> very<00:17:54.520> easy<00:17:55.520> um 00:17:55.870 --> 00:17:55.880 align:start position:0% liquidity as well it's like very easy um 00:17:55.880 --> 00:17:57.549 align:start position:0% liquidity as well it's like very easy um but<00:17:56.039> like<00:17:56.159> what<00:17:56.320> D<00:17:56.559> is<00:17:56.640> saying<00:17:56.880> when<00:17:56.960> you<00:17:57.120> go<00:17:57.320> to 00:17:57.549 --> 00:17:57.559 align:start position:0% but like what D is saying when you go to 00:17:57.559 --> 00:17:59.390 align:start position:0% but like what D is saying when you go to these<00:17:57.799> like<00:17:58.000> further<00:17:58.280> and<00:17:58.400> further<00:17:59.039> chains 00:17:59.390 --> 00:17:59.400 align:start position:0% these like further and further chains 00:17:59.400 --> 00:18:00.789 align:start position:0% these like further and further chains where<00:17:59.559> there's<00:17:59.799> just<00:17:59.960> not<00:18:00.159> as<00:18:00.320> much<00:18:00.480> of<00:18:00.600> an 00:18:00.789 --> 00:18:00.799 align:start position:0% where there's just not as much of an 00:18:00.799 --> 00:18:03.990 align:start position:0% where there's just not as much of an ecosystem<00:18:01.400> buil<00:18:01.720> built<00:18:01.960> up<00:18:02.240> there<00:18:03.240> um<00:18:03.880> you 00:18:03.990 --> 00:18:04.000 align:start position:0% ecosystem buil built up there um you 00:18:04.000 --> 00:18:06.590 align:start position:0% ecosystem buil built up there um you know<00:18:04.760> there<00:18:04.919> there's<00:18:05.400> there's<00:18:05.520> only<00:18:05.720> so<00:18:05.960> much 00:18:06.590 --> 00:18:06.600 align:start position:0% know there there's there's only so much 00:18:06.600 --> 00:18:07.830 align:start position:0% know there there's there's only so much uh<00:18:06.720> there's<00:18:06.880> only<00:18:07.039> so<00:18:07.159> many<00:18:07.320> pools<00:18:07.600> that<00:18:07.720> you 00:18:07.830 --> 00:18:07.840 align:start position:0% uh there's only so many pools that you 00:18:07.840 --> 00:18:10.110 align:start position:0% uh there's only so many pools that you can<00:18:08.039> that<00:18:08.120> you<00:18:08.200> can<00:18:08.400> reach<00:18:09.280> um<00:18:09.440> and<00:18:09.640> you<00:18:09.760> know 00:18:10.110 --> 00:18:10.120 align:start position:0% can that you can reach um and you know 00:18:10.120 --> 00:18:12.390 align:start position:0% can that you can reach um and you know and<00:18:10.240> then<00:18:10.400> taking<00:18:10.640> that<00:18:10.760> one<00:18:10.960> step<00:18:11.280> further<00:18:12.280> um 00:18:12.390 --> 00:18:12.400 align:start position:0% and then taking that one step further um 00:18:12.400 --> 00:18:14.270 align:start position:0% and then taking that one step further um you<00:18:12.520> know<00:18:12.679> to<00:18:12.880> bring<00:18:13.400> offchain<00:18:13.840> liquidity 00:18:14.270 --> 00:18:14.280 align:start position:0% you know to bring offchain liquidity 00:18:14.280 --> 00:18:16.270 align:start position:0% you know to bring offchain liquidity into<00:18:14.559> these<00:18:14.799> pool<00:18:15.120> into<00:18:15.360> this<00:18:15.559> Marketplace<00:18:16.080> is 00:18:16.270 --> 00:18:16.280 align:start position:0% into these pool into this Marketplace is 00:18:16.280 --> 00:18:18.789 align:start position:0% into these pool into this Marketplace is even<00:18:16.840> like<00:18:17.000> another<00:18:17.320> crazy<00:18:17.640> step<00:18:18.320> um<00:18:18.520> and<00:18:18.640> and 00:18:18.789 --> 00:18:18.799 align:start position:0% even like another crazy step um and and 00:18:18.799 --> 00:18:21.190 align:start position:0% even like another crazy step um and and requires<00:18:19.159> a<00:18:19.280> lot<00:18:19.400> of<00:18:20.200> uh<00:18:20.320> development<00:18:20.799> effort 00:18:21.190 --> 00:18:21.200 align:start position:0% requires a lot of uh development effort 00:18:21.200 --> 00:18:24.230 align:start position:0% requires a lot of uh development effort and<00:18:21.480> and<00:18:21.760> and<00:18:22.039> OB<00:18:22.320> obviously<00:18:22.880> Capital<00:18:23.880> um<00:18:24.039> so 00:18:24.230 --> 00:18:24.240 align:start position:0% and and and OB obviously Capital um so 00:18:24.240 --> 00:18:26.230 align:start position:0% and and and OB obviously Capital um so from<00:18:24.440> our<00:18:24.799> perspective<00:18:25.520> um<00:18:25.679> that<00:18:25.880> that's<00:18:26.080> been 00:18:26.230 --> 00:18:26.240 align:start position:0% from our perspective um that that's been 00:18:26.240 --> 00:18:28.029 align:start position:0% from our perspective um that that's been the<00:18:26.360> biggest<00:18:26.799> the<00:18:26.919> biggest<00:18:27.360> and<00:18:27.640> and<00:18:27.880> most 00:18:28.029 --> 00:18:28.039 align:start position:0% the biggest the biggest and and most 00:18:28.039 --> 00:18:29.590 align:start position:0% the biggest the biggest and and most challenging<00:18:28.400> hurdle 00:18:29.590 --> 00:18:29.600 align:start position:0% challenging hurdle 00:18:29.600 --> 00:18:31.149 align:start position:0% challenging hurdle but<00:18:29.840> it<00:18:30.000> actually<00:18:30.480> I<00:18:30.559> think<00:18:30.720> it<00:18:30.880> actually 00:18:31.149 --> 00:18:31.159 align:start position:0% but it actually I think it actually 00:18:31.159 --> 00:18:33.630 align:start position:0% but it actually I think it actually makes<00:18:31.440> sense<00:18:31.720> that<00:18:31.880> you<00:18:32.039> start<00:18:32.400> with<00:18:32.640> the 00:18:33.630 --> 00:18:33.640 align:start position:0% makes sense that you start with the 00:18:33.640 --> 00:18:35.270 align:start position:0% makes sense that you start with the let's<00:18:33.840> call<00:18:33.960> it<00:18:34.080> the<00:18:34.200> lwh<00:18:34.520> hanging<00:18:34.840> fruit 00:18:35.270 --> 00:18:35.280 align:start position:0% let's call it the lwh hanging fruit 00:18:35.280 --> 00:18:37.270 align:start position:0% let's call it the lwh hanging fruit where<00:18:35.440> that<00:18:35.559> you<00:18:35.679> can<00:18:35.880> integrate<00:18:36.360> easily<00:18:36.960> and 00:18:37.270 --> 00:18:37.280 align:start position:0% where that you can integrate easily and 00:18:37.280 --> 00:18:40.110 align:start position:0% where that you can integrate easily and and<00:18:37.600> fast<00:18:38.360> and<00:18:38.480> then<00:18:38.640> you<00:18:38.799> move<00:18:39.080> into<00:18:39.600> the<00:18:39.760> more 00:18:40.110 --> 00:18:40.120 align:start position:0% and fast and then you move into the more 00:18:40.120 --> 00:18:42.909 align:start position:0% and fast and then you move into the more complex<00:18:40.640> but<00:18:41.240> probably<00:18:41.679> the<00:18:41.799> ones<00:18:42.120> that<00:18:42.280> will 00:18:42.909 --> 00:18:42.919 align:start position:0% complex but probably the ones that will 00:18:42.919 --> 00:18:44.950 align:start position:0% complex but probably the ones that will that<00:18:43.080> you<00:18:43.280> select<00:18:43.840> or<00:18:44.000> you<00:18:44.200> prioritize<00:18:44.840> the 00:18:44.950 --> 00:18:44.960 align:start position:0% that you select or you prioritize the 00:18:44.960 --> 00:18:47.190 align:start position:0% that you select or you prioritize the ones<00:18:45.159> that<00:18:45.280> will<00:18:45.400> be<00:18:45.559> adding<00:18:45.880> more<00:18:46.159> value<00:18:47.080> uh 00:18:47.190 --> 00:18:47.200 align:start position:0% ones that will be adding more value uh 00:18:47.200 --> 00:18:48.950 align:start position:0% ones that will be adding more value uh to<00:18:47.400> your<00:18:47.600> to<00:18:47.720> your<00:18:47.880> ecosystem<00:18:48.360> and<00:18:48.480> you<00:18:48.640> focus 00:18:48.950 --> 00:18:48.960 align:start position:0% to your to your ecosystem and you focus 00:18:48.960 --> 00:18:51.070 align:start position:0% to your to your ecosystem and you focus on<00:18:49.320> on<00:18:49.480> implementing<00:18:50.400> uh 00:18:51.070 --> 00:18:51.080 align:start position:0% on on implementing uh 00:18:51.080 --> 00:18:54.909 align:start position:0% on on implementing uh those<00:18:52.080> um<00:18:53.039> thank<00:18:53.200> you<00:18:53.799> uh<00:18:53.960> if<00:18:54.159> if<00:18:54.280> I<00:18:54.400> may<00:18:54.640> add 00:18:54.909 --> 00:18:54.919 align:start position:0% those um thank you uh if if I may add 00:18:54.919 --> 00:18:56.510 align:start position:0% those um thank you uh if if I may add here<00:18:55.240> something<00:18:55.840> that<00:18:56.000> I<00:18:56.120> think<00:18:56.320> it's 00:18:56.510 --> 00:18:56.520 align:start position:0% here something that I think it's 00:18:56.520 --> 00:18:58.310 align:start position:0% here something that I think it's important<00:18:56.880> for<00:18:57.080> scalability<00:18:57.799> and<00:18:58.039> it's<00:18:58.159> a 00:18:58.310 --> 00:18:58.320 align:start position:0% important for scalability and it's a 00:18:58.320 --> 00:19:00.710 align:start position:0% important for scalability and it's a concept<00:18:59.039> that<00:18:59.159> we<00:18:59.320> didn't<00:18:59.520> mention<00:19:00.440> uh<00:19:00.559> it's 00:19:00.710 --> 00:19:00.720 align:start position:0% concept that we didn't mention uh it's 00:19:00.720 --> 00:19:03.149 align:start position:0% concept that we didn't mention uh it's the<00:19:00.919> concept<00:19:01.240> of<00:19:01.640> modularity<00:19:02.640> so<00:19:02.919> I<00:19:03.000> think 00:19:03.149 --> 00:19:03.159 align:start position:0% the concept of modularity so I think 00:19:03.159 --> 00:19:05.110 align:start position:0% the concept of modularity so I think modularity<00:19:03.720> is<00:19:03.799> going<00:19:04.000> to<00:19:04.240> play<00:19:04.480> an<00:19:04.679> important 00:19:05.110 --> 00:19:05.120 align:start position:0% modularity is going to play an important 00:19:05.120 --> 00:19:08.390 align:start position:0% modularity is going to play an important role<00:19:05.640> in<00:19:06.159> in<00:19:06.559> the<00:19:06.840> intense<00:19:07.559> uh 00:19:08.390 --> 00:19:08.400 align:start position:0% role in in the intense uh 00:19:08.400 --> 00:19:11.549 align:start position:0% role in in the intense uh scaling<00:19:09.400> um<00:19:10.280> for<00:19:10.520> example<00:19:11.080> the<00:19:11.360> the 00:19:11.549 --> 00:19:11.559 align:start position:0% scaling um for example the the 00:19:11.559 --> 00:19:12.990 align:start position:0% scaling um for example the the infrastructure<00:19:12.240> that<00:19:12.440> Paras<00:19:12.720> swap<00:19:12.919> is 00:19:12.990 --> 00:19:13.000 align:start position:0% infrastructure that Paras swap is 00:19:13.000 --> 00:19:16.110 align:start position:0% infrastructure that Paras swap is leveraging<00:19:13.600> to<00:19:13.760> enable<00:19:14.600> uh<00:19:14.840> intents<00:19:15.840> uh<00:19:15.960> it's 00:19:16.110 --> 00:19:16.120 align:start position:0% leveraging to enable uh intents uh it's 00:19:16.120 --> 00:19:18.110 align:start position:0% leveraging to enable uh intents uh it's a<00:19:16.320> modular<00:19:16.799> infrastructure<00:19:17.559> what<00:19:17.720> does<00:19:17.919> this 00:19:18.110 --> 00:19:18.120 align:start position:0% a modular infrastructure what does this 00:19:18.120 --> 00:19:20.510 align:start position:0% a modular infrastructure what does this means<00:19:18.600> it's<00:19:18.960> uh<00:19:19.200> it<00:19:19.320> means<00:19:19.679> for<00:19:19.880> example<00:19:20.320> that 00:19:20.510 --> 00:19:20.520 align:start position:0% means it's uh it means for example that 00:19:20.520 --> 00:19:23.390 align:start position:0% means it's uh it means for example that the<00:19:21.039> swap<00:19:21.600> module<00:19:22.159> that<00:19:22.360> Paras<00:19:22.640> swap<00:19:23.000> it's 00:19:23.390 --> 00:19:23.400 align:start position:0% the swap module that Paras swap it's 00:19:23.400 --> 00:19:26.310 align:start position:0% the swap module that Paras swap it's leveraging<00:19:24.039> to<00:19:24.200> enable<00:19:24.600> intents<00:19:25.600> uh<00:19:25.919> it's<00:19:26.120> a 00:19:26.310 --> 00:19:26.320 align:start position:0% leveraging to enable intents uh it's a 00:19:26.320 --> 00:19:29.310 align:start position:0% leveraging to enable intents uh it's a module<00:19:26.760> that<00:19:26.919> was<00:19:27.159> built<00:19:27.919> exactly<00:19:28.440> with<00:19:29.120> this 00:19:29.310 --> 00:19:29.320 align:start position:0% module that was built exactly with this 00:19:29.320 --> 00:19:32.549 align:start position:0% module that was built exactly with this use<00:19:29.679> case<00:19:30.159> exactly<00:19:30.559> for<00:19:30.880> this<00:19:31.080> use<00:19:31.440> case<00:19:32.280> uh<00:19:32.440> if 00:19:32.549 --> 00:19:32.559 align:start position:0% use case exactly for this use case uh if 00:19:32.559 --> 00:19:35.669 align:start position:0% use case exactly for this use case uh if we<00:19:32.720> want<00:19:32.960> to<00:19:33.159> enable<00:19:33.799> other<00:19:34.559> uh<00:19:34.720> modules<00:19:35.520> then 00:19:35.669 --> 00:19:35.679 align:start position:0% we want to enable other uh modules then 00:19:35.679 --> 00:19:37.549 align:start position:0% we want to enable other uh modules then we<00:19:35.760> need<00:19:35.919> to<00:19:36.120> develop<00:19:36.559> that<00:19:36.760> module<00:19:37.240> and<00:19:37.360> it's 00:19:37.549 --> 00:19:37.559 align:start position:0% we need to develop that module and it's 00:19:37.559 --> 00:19:40.190 align:start position:0% we need to develop that module and it's probably<00:19:38.000> easier<00:19:38.400> to<00:19:38.600> escalate<00:19:39.559> things<00:19:39.960> by 00:19:40.190 --> 00:19:40.200 align:start position:0% probably easier to escalate things by 00:19:40.200 --> 00:19:42.230 align:start position:0% probably easier to escalate things by module<00:19:40.679> rather<00:19:40.880> than<00:19:41.120> just<00:19:41.360> escalating<00:19:42.039> all 00:19:42.230 --> 00:19:42.240 align:start position:0% module rather than just escalating all 00:19:42.240 --> 00:19:45.950 align:start position:0% module rather than just escalating all the<00:19:42.400> use<00:19:42.760> cases<00:19:43.360> uh<00:19:43.520> at<00:19:43.880> once<00:19:44.880> uh<00:19:45.080> so<00:19:45.320> I<00:19:45.440> think 00:19:45.950 --> 00:19:45.960 align:start position:0% the use cases uh at once uh so I think 00:19:45.960 --> 00:19:48.029 align:start position:0% the use cases uh at once uh so I think uh<00:19:46.320> modularity<00:19:47.000> will<00:19:47.240> play<00:19:47.400> an<00:19:47.600> important 00:19:48.029 --> 00:19:48.039 align:start position:0% uh modularity will play an important 00:19:48.039 --> 00:19:49.630 align:start position:0% uh modularity will play an important role<00:19:48.559> because<00:19:48.760> you<00:19:48.919> can<00:19:49.080> think<00:19:49.360> about 00:19:49.630 --> 00:19:49.640 align:start position:0% role because you can think about 00:19:49.640 --> 00:19:51.430 align:start position:0% role because you can think about modularity<00:19:50.320> then<00:19:50.440> you<00:19:50.559> can<00:19:50.720> start<00:19:51.000> connecting 00:19:51.430 --> 00:19:51.440 align:start position:0% modularity then you can start connecting 00:19:51.440 --> 00:19:53.430 align:start position:0% modularity then you can start connecting the<00:19:51.600> different<00:19:51.919> modules<00:19:52.360> and<00:19:52.480> I<00:19:52.679> go<00:19:52.880> to<00:19:53.080> the<00:19:53.320> to 00:19:53.430 --> 00:19:53.440 align:start position:0% the different modules and I go to the to 00:19:53.440 --> 00:19:54.950 align:start position:0% the different modules and I go to the to the<00:19:53.600> connecting<00:19:54.000> rooms<00:19:54.360> that<00:19:54.520> you<00:19:54.600> were 00:19:54.950 --> 00:19:54.960 align:start position:0% the connecting rooms that you were 00:19:54.960 --> 00:19:58.669 align:start position:0% the connecting rooms that you were saying<00:19:55.960> um<00:19:56.799> if<00:19:56.960> you<00:19:57.400> start<00:19:57.799> connecting<00:19:58.280> mod 00:19:58.669 --> 00:19:58.679 align:start position:0% saying um if you start connecting mod 00:19:58.679 --> 00:20:01.070 align:start position:0% saying um if you start connecting mod mod<00:19:59.000> and<00:19:59.159> each<00:19:59.360> module<00:19:59.760> enables<00:20:00.280> a<00:20:00.440> use<00:20:00.760> case 00:20:01.070 --> 00:20:01.080 align:start position:0% mod and each module enables a use case 00:20:01.080 --> 00:20:03.909 align:start position:0% mod and each module enables a use case let's<00:20:01.280> say<00:20:02.200> uh<00:20:02.360> swap<00:20:02.760> module<00:20:03.120> Bridge<00:20:03.480> module 00:20:03.909 --> 00:20:03.919 align:start position:0% let's say uh swap module Bridge module 00:20:03.919 --> 00:20:06.430 align:start position:0% let's say uh swap module Bridge module cross<00:20:04.240> chain<00:20:04.600> module<00:20:05.600> uh<00:20:05.880> you<00:20:06.000> can<00:20:06.200> start 00:20:06.430 --> 00:20:06.440 align:start position:0% cross chain module uh you can start 00:20:06.440 --> 00:20:08.430 align:start position:0% cross chain module uh you can start mixing<00:20:07.120> the<00:20:07.280> usage<00:20:07.640> of<00:20:07.840> this<00:20:07.960> module<00:20:08.280> to 00:20:08.430 --> 00:20:08.440 align:start position:0% mixing the usage of this module to 00:20:08.440 --> 00:20:10.750 align:start position:0% mixing the usage of this module to enable<00:20:08.840> different<00:20:09.200> features<00:20:10.200> uh<00:20:10.320> on<00:20:10.559> the 00:20:10.750 --> 00:20:10.760 align:start position:0% enable different features uh on the 00:20:10.760 --> 00:20:14.190 align:start position:0% enable different features uh on the different<00:20:11.080> protocols<00:20:11.559> UI<00:20:12.520> so<00:20:13.240> I<00:20:13.360> think<00:20:14.039> that 00:20:14.190 --> 00:20:14.200 align:start position:0% different protocols UI so I think that 00:20:14.200 --> 00:20:16.110 align:start position:0% different protocols UI so I think that would<00:20:14.360> be<00:20:14.520> an<00:20:14.720> important<00:20:15.200> concept<00:20:15.679> that<00:20:15.960> at 00:20:16.110 --> 00:20:16.120 align:start position:0% would be an important concept that at 00:20:16.120 --> 00:20:18.149 align:start position:0% would be an important concept that at some<00:20:16.360> point<00:20:16.640> it's<00:20:16.799> going<00:20:17.000> to<00:20:17.159> be<00:20:17.640> uh<00:20:17.799> more 00:20:18.149 --> 00:20:18.159 align:start position:0% some point it's going to be uh more 00:20:18.159 --> 00:20:22.549 align:start position:0% some point it's going to be uh more spreaded<00:20:19.039> uh<00:20:19.200> around<00:20:19.600> the<00:20:19.799> intense 00:20:22.549 --> 00:20:22.559 align:start position:0% 00:20:22.559 --> 00:20:26.310 align:start position:0% ecosystem<00:20:23.559> um<00:20:24.360> now<00:20:24.760> now<00:20:24.919> I<00:20:25.039> want<00:20:25.240> you<00:20:25.799> I<00:20:26.080> I<00:20:26.159> want 00:20:26.310 --> 00:20:26.320 align:start position:0% ecosystem um now now I want you I I want 00:20:26.320 --> 00:20:30.270 align:start position:0% ecosystem um now now I want you I I want to<00:20:26.480> take<00:20:26.640> you<00:20:26.799> out<00:20:27.039> of<00:20:27.240> your<00:20:27.640> protocols<00:20:28.919> uh 00:20:30.270 --> 00:20:30.280 align:start position:0% to take you out of your protocols uh 00:20:30.280 --> 00:20:32.750 align:start position:0% to take you out of your protocols uh and<00:20:31.280> make<00:20:31.600> a<00:20:31.919> question<00:20:32.240> that<00:20:32.360> it's<00:20:32.520> more 00:20:32.750 --> 00:20:32.760 align:start position:0% and make a question that it's more 00:20:32.760 --> 00:20:35.029 align:start position:0% and make a question that it's more related<00:20:33.120> to<00:20:33.520> more<00:20:33.720> related<00:20:34.039> to<00:20:34.159> the<00:20:34.360> general 00:20:35.029 --> 00:20:35.039 align:start position:0% related to more related to the general 00:20:35.039 --> 00:20:38.230 align:start position:0% related to more related to the general experience<00:20:35.640> through<00:20:35.880> intents<00:20:36.440> so<00:20:37.280> when<00:20:37.520> we 00:20:38.230 --> 00:20:38.240 align:start position:0% experience through intents so when we 00:20:38.240 --> 00:20:40.510 align:start position:0% experience through intents so when we when<00:20:38.400> we<00:20:38.600> talk<00:20:38.880> about<00:20:39.440> simplifying<00:20:40.039> user 00:20:40.510 --> 00:20:40.520 align:start position:0% when we talk about simplifying user 00:20:40.520 --> 00:20:43.669 align:start position:0% when we talk about simplifying user experience<00:20:41.520> uh<00:20:41.679> taking<00:20:42.240> the<00:20:42.600> specifics<00:20:43.480> out 00:20:43.669 --> 00:20:43.679 align:start position:0% experience uh taking the specifics out 00:20:43.679 --> 00:20:46.149 align:start position:0% experience uh taking the specifics out of<00:20:43.840> the<00:20:44.000> hands<00:20:44.240> of<00:20:44.360> the<00:20:44.480> users<00:20:44.960> and<00:20:45.679> leaving 00:20:46.149 --> 00:20:46.159 align:start position:0% of the hands of the users and leaving 00:20:46.159 --> 00:20:49.510 align:start position:0% of the hands of the users and leaving that<00:20:46.360> to<00:20:46.559> a<00:20:46.720> third<00:20:47.400> party<00:20:48.400> I<00:20:48.679> kind<00:20:48.880> of<00:20:49.080> feel 00:20:49.510 --> 00:20:49.520 align:start position:0% that to a third party I kind of feel 00:20:49.520 --> 00:20:53.270 align:start position:0% that to a third party I kind of feel related<00:20:50.159> to<00:20:50.640> a<00:20:50.840> web<00:20:51.080> to<00:20:51.679> experience<00:20:52.679> uh<00:20:52.919> where 00:20:53.270 --> 00:20:53.280 align:start position:0% related to a web to experience uh where 00:20:53.280 --> 00:20:55.789 align:start position:0% related to a web to experience uh where we<00:20:53.480> have<00:20:54.080> centralized<00:20:54.760> entities<00:20:55.240> centralized 00:20:55.789 --> 00:20:55.799 align:start position:0% we have centralized entities centralized 00:20:55.799 --> 00:20:58.350 align:start position:0% we have centralized entities centralized actors<00:20:56.280> that<00:20:56.520> decide<00:20:57.360> for<00:20:57.600> the<00:20:57.760> user<00:20:58.200> that 00:20:58.350 --> 00:20:58.360 align:start position:0% actors that decide for the user that 00:20:58.360 --> 00:21:00.549 align:start position:0% actors that decide for the user that take<00:20:58.720> complexity<00:20:59.240> out<00:20:59.400> of<00:20:59.559> users<00:20:59.960> but<00:21:00.159> decide 00:21:00.549 --> 00:21:00.559 align:start position:0% take complexity out of users but decide 00:21:00.559 --> 00:21:04.549 align:start position:0% take complexity out of users but decide for<00:21:01.039> users<00:21:02.320> so<00:21:03.320> at<00:21:03.480> some<00:21:03.720> points<00:21:04.120> I<00:21:04.280> found 00:21:04.549 --> 00:21:04.559 align:start position:0% for users so at some points I found 00:21:04.559 --> 00:21:07.270 align:start position:0% for users so at some points I found myself<00:21:04.960> talking<00:21:05.240> about<00:21:05.480> intents<00:21:06.280> and<00:21:06.919> remind 00:21:07.270 --> 00:21:07.280 align:start position:0% myself talking about intents and remind 00:21:07.280 --> 00:21:11.269 align:start position:0% myself talking about intents and remind me<00:21:07.480> of<00:21:07.640> the<00:21:07.840> experience<00:21:08.320> we<00:21:08.520> have<00:21:08.799> in<00:21:09.080> web<00:21:09.360> 2<00:21:10.360> so 00:21:11.269 --> 00:21:11.279 align:start position:0% me of the experience we have in web 2 so 00:21:11.279 --> 00:21:13.390 align:start position:0% me of the experience we have in web 2 so how<00:21:11.640> how<00:21:11.760> do<00:21:11.880> you<00:21:12.039> think<00:21:12.279> we<00:21:12.400> should<00:21:12.720> find<00:21:13.039> the 00:21:13.390 --> 00:21:13.400 align:start position:0% how how do you think we should find the 00:21:13.400 --> 00:21:17.390 align:start position:0% how how do you think we should find the balance<00:21:13.880> or<00:21:14.039> the<00:21:14.159> switch<00:21:14.640> spot<00:21:15.240> of<00:21:16.400> making 00:21:17.390 --> 00:21:17.400 align:start position:0% balance or the switch spot of making 00:21:17.400 --> 00:21:21.070 align:start position:0% balance or the switch spot of making users<00:21:17.919> experience<00:21:18.400> better<00:21:19.200> easier<00:21:20.200> but<00:21:20.679> not 00:21:21.070 --> 00:21:21.080 align:start position:0% users experience better easier but not 00:21:21.080 --> 00:21:24.310 align:start position:0% users experience better easier but not losing<00:21:21.799> or<00:21:22.080> not<00:21:22.919> uh<00:21:23.320> yeah<00:21:23.480> not<00:21:23.640> losing<00:21:24.080> the 00:21:24.310 --> 00:21:24.320 align:start position:0% losing or not uh yeah not losing the 00:21:24.320 --> 00:21:27.149 align:start position:0% losing or not uh yeah not losing the decentralization<00:21:25.320> that<00:21:25.520> Defi<00:21:26.039> and<00:21:26.200> ethereum 00:21:27.149 --> 00:21:27.159 align:start position:0% decentralization that Defi and ethereum 00:21:27.159 --> 00:21:29.190 align:start position:0% decentralization that Defi and ethereum have<00:21:27.400> already<00:21:28.240> uh 00:21:29.190 --> 00:21:29.200 align:start position:0% have already uh 00:21:29.200 --> 00:21:34.230 align:start position:0% have already uh establish<00:21:29.760> as<00:21:29.880> a<00:21:30.039> kind<00:21:30.200> of<00:21:30.320> a 00:21:34.230 --> 00:21:34.240 align:start position:0% 00:21:34.240 --> 00:21:37.110 align:start position:0% standard<00:21:35.240> yeah<00:21:35.559> I<00:21:35.640> mean<00:21:36.000> I<00:21:36.080> mean<00:21:36.279> first<00:21:36.600> of<00:21:36.760> all 00:21:37.110 --> 00:21:37.120 align:start position:0% standard yeah I mean I mean first of all 00:21:37.120 --> 00:21:39.269 align:start position:0% standard yeah I mean I mean first of all if<00:21:37.279> we<00:21:37.520> go<00:21:37.720> from<00:21:38.000> like<00:21:38.159> the<00:21:38.320> solver<00:21:38.760> based 00:21:39.269 --> 00:21:39.279 align:start position:0% if we go from like the solver based 00:21:39.279 --> 00:21:43.909 align:start position:0% if we go from like the solver based system<00:21:40.159> um<00:21:41.200> generally<00:21:42.200> it<00:21:42.480> takes<00:21:43.279> a<00:21:43.440> lot<00:21:43.600> of 00:21:43.909 --> 00:21:43.919 align:start position:0% system um generally it takes a lot of 00:21:43.919 --> 00:21:47.950 align:start position:0% system um generally it takes a lot of risk<00:21:44.640> out<00:21:44.840> of<00:21:45.360> um<00:21:46.240> or<00:21:46.440> away<00:21:46.679> from<00:21:46.880> the<00:21:47.000> user 00:21:47.950 --> 00:21:47.960 align:start position:0% risk out of um or away from the user 00:21:47.960 --> 00:21:49.510 align:start position:0% risk out of um or away from the user because 00:21:49.510 --> 00:21:49.520 align:start position:0% because 00:21:49.520 --> 00:21:53.590 align:start position:0% because um<00:21:50.520> the<00:21:50.720> way<00:21:51.039> that<00:21:51.360> these<00:21:52.360> um<00:21:52.720> systems<00:21:53.200> usually 00:21:53.590 --> 00:21:53.600 align:start position:0% um the way that these um systems usually 00:21:53.600 --> 00:21:57.830 align:start position:0% um the way that these um systems usually work<00:21:54.320> is<00:21:55.320> a<00:21:55.520> solver<00:21:56.080> basically<00:21:56.520> more<00:21:56.679> or<00:21:56.880> less 00:21:57.830 --> 00:21:57.840 align:start position:0% work is a solver basically more or less 00:21:57.840 --> 00:22:01.230 align:start position:0% work is a solver basically more or less instantly<00:21:58.600> fills<00:21:59.400> prefills<00:22:00.400> um<00:22:01.039> the 00:22:01.230 --> 00:22:01.240 align:start position:0% instantly fills prefills um the 00:22:01.240 --> 00:22:04.470 align:start position:0% instantly fills prefills um the transaction<00:22:01.840> that<00:22:02.000> the<00:22:02.120> user<00:22:02.919> requests<00:22:03.919> um<00:22:04.279> in 00:22:04.470 --> 00:22:04.480 align:start position:0% transaction that the user requests um in 00:22:04.480 --> 00:22:06.990 align:start position:0% transaction that the user requests um in kind<00:22:04.640> of<00:22:04.760> like<00:22:04.880> an<00:22:05.000> RFQ<00:22:05.520> system<00:22:05.919> as<00:22:06.039> you<00:22:06.159> said 00:22:06.990 --> 00:22:07.000 align:start position:0% kind of like an RFQ system as you said 00:22:07.000 --> 00:22:10.470 align:start position:0% kind of like an RFQ system as you said and<00:22:07.200> then<00:22:08.120> um<00:22:09.120> on<00:22:09.279> the<00:22:09.440> same<00:22:09.640> chain<00:22:10.039> obviously 00:22:10.470 --> 00:22:10.480 align:start position:0% and then um on the same chain obviously 00:22:10.480 --> 00:22:12.669 align:start position:0% and then um on the same chain obviously they're<00:22:10.760> usually<00:22:11.200> more<00:22:11.360> or<00:22:11.520> less<00:22:11.720> Atomic<00:22:12.320> so 00:22:12.669 --> 00:22:12.679 align:start position:0% they're usually more or less Atomic so 00:22:12.679 --> 00:22:15.310 align:start position:0% they're usually more or less Atomic so there<00:22:12.799> isn't<00:22:13.240> too<00:22:13.440> much<00:22:13.640> risk<00:22:14.039> there<00:22:14.919> um<00:22:15.080> once 00:22:15.310 --> 00:22:15.320 align:start position:0% there isn't too much risk there um once 00:22:15.320 --> 00:22:19.110 align:start position:0% there isn't too much risk there um once you<00:22:15.559> go<00:22:16.279> across<00:22:17.120> multiple<00:22:17.679> chains<00:22:18.679> um<00:22:19.000> there 00:22:19.110 --> 00:22:19.120 align:start position:0% you go across multiple chains um there 00:22:19.120 --> 00:22:21.590 align:start position:0% you go across multiple chains um there might<00:22:19.320> obviously<00:22:19.760> be<00:22:20.200> some<00:22:20.640> kind<00:22:20.799> of<00:22:20.960> finality 00:22:21.590 --> 00:22:21.600 align:start position:0% might obviously be some kind of finality 00:22:21.600 --> 00:22:24.230 align:start position:0% might obviously be some kind of finality problems<00:22:22.400> and<00:22:22.840> now<00:22:23.039> the<00:22:23.200> solver<00:22:23.679> takes<00:22:23.960> on 00:22:24.230 --> 00:22:24.240 align:start position:0% problems and now the solver takes on 00:22:24.240 --> 00:22:27.310 align:start position:0% problems and now the solver takes on these<00:22:24.400> finality<00:22:25.039> risks<00:22:25.520> that<00:22:25.679> the<00:22:25.960> user<00:22:26.960> um 00:22:27.310 --> 00:22:27.320 align:start position:0% these finality risks that the user um 00:22:27.320 --> 00:22:31.390 align:start position:0% these finality risks that the user um had<00:22:27.600> before<00:22:28.600> and<00:22:29.120> um<00:22:29.400> the<00:22:29.559> solver<00:22:30.240> as<00:22:30.600> a<00:22:30.840> more 00:22:31.390 --> 00:22:31.400 align:start position:0% had before and um the solver as a more 00:22:31.400 --> 00:22:34.190 align:start position:0% had before and um the solver as a more professional<00:22:32.000> Market<00:22:32.400> making<00:22:32.880> entity<00:22:33.880> should 00:22:34.190 --> 00:22:34.200 align:start position:0% professional Market making entity should 00:22:34.200 --> 00:22:36.269 align:start position:0% professional Market making entity should be<00:22:34.480> better<00:22:34.880> equipped<00:22:35.400> to 00:22:36.269 --> 00:22:36.279 align:start position:0% be better equipped to 00:22:36.279 --> 00:22:39.590 align:start position:0% be better equipped to basically<00:22:37.600> calculate<00:22:38.600> um<00:22:38.840> this<00:22:39.000> finality 00:22:39.590 --> 00:22:39.600 align:start position:0% basically calculate um this finality 00:22:39.600 --> 00:22:43.190 align:start position:0% basically calculate um this finality risk<00:22:40.480> um<00:22:40.760> and<00:22:40.880> then<00:22:41.159> settles<00:22:41.919> through<00:22:42.880> some 00:22:43.190 --> 00:22:43.200 align:start position:0% risk um and then settles through some 00:22:43.200 --> 00:22:45.950 align:start position:0% risk um and then settles through some type<00:22:43.520> of<00:22:44.039> you<00:22:44.200> know<00:22:44.559> intense<00:22:45.000> settlement 00:22:45.950 --> 00:22:45.960 align:start position:0% type of you know intense settlement 00:22:45.960 --> 00:22:50.710 align:start position:0% type of you know intense settlement layer<00:22:47.159> mechanism<00:22:48.159> um<00:22:48.960> so<00:22:49.960> I<00:22:50.039> think<00:22:50.240> from<00:22:50.520> that 00:22:50.710 --> 00:22:50.720 align:start position:0% layer mechanism um so I think from that 00:22:50.720 --> 00:22:54.750 align:start position:0% layer mechanism um so I think from that perspective<00:22:51.559> there<00:22:52.559> there<00:22:53.240> isn't<00:22:54.240> too<00:22:54.480> much 00:22:54.750 --> 00:22:54.760 align:start position:0% perspective there there isn't too much 00:22:54.760 --> 00:22:57.390 align:start position:0% perspective there there isn't too much risk<00:22:55.000> for<00:22:55.159> the<00:22:55.360> user<00:22:56.360> um<00:22:56.720> I<00:22:56.799> think<00:22:57.039> where<00:22:57.240> the 00:22:57.390 --> 00:22:57.400 align:start position:0% risk for the user um I think where the 00:22:57.400 --> 00:22:59.870 align:start position:0% risk for the user um I think where the risk<00:22:57.679> becomes 00:22:59.870 --> 00:22:59.880 align:start position:0% risk becomes 00:22:59.880 --> 00:23:03.510 align:start position:0% risk becomes more<00:23:00.360> prevalent<00:23:01.360> is<00:23:01.919> when<00:23:02.120> we<00:23:02.320> start<00:23:02.679> thinking 00:23:03.510 --> 00:23:03.520 align:start position:0% more prevalent is when we start thinking 00:23:03.520 --> 00:23:07.149 align:start position:0% more prevalent is when we start thinking about<00:23:04.520> competition<00:23:05.520> as<00:23:05.640> you<00:23:05.799> said<00:23:06.200> earlier<00:23:07.000> um 00:23:07.149 --> 00:23:07.159 align:start position:0% about competition as you said earlier um 00:23:07.159 --> 00:23:11.830 align:start position:0% about competition as you said earlier um on<00:23:08.080> a<00:23:08.240> chain<00:23:09.159> um<00:23:09.960> that<00:23:10.120> is<00:23:10.520> smaller<00:23:11.520> um<00:23:11.720> there 00:23:11.830 --> 00:23:11.840 align:start position:0% on a chain um that is smaller um there 00:23:11.840 --> 00:23:13.909 align:start position:0% on a chain um that is smaller um there might<00:23:12.039> only<00:23:12.240> be<00:23:12.480> like<00:23:12.720> one<00:23:12.880> or<00:23:13.039> two<00:23:13.200> solvers 00:23:13.909 --> 00:23:13.919 align:start position:0% might only be like one or two solvers 00:23:13.919 --> 00:23:15.990 align:start position:0% might only be like one or two solvers okay<00:23:14.480> one<00:23:14.720> solver<00:23:15.200> I<00:23:15.279> think<00:23:15.480> everybody<00:23:15.880> here 00:23:15.990 --> 00:23:16.000 align:start position:0% okay one solver I think everybody here 00:23:16.000 --> 00:23:17.590 align:start position:0% okay one solver I think everybody here can<00:23:16.159> see<00:23:16.360> the<00:23:16.520> problem<00:23:16.840> with<00:23:17.039> that<00:23:17.320> it's 00:23:17.590 --> 00:23:17.600 align:start position:0% can see the problem with that it's 00:23:17.600 --> 00:23:20.149 align:start position:0% can see the problem with that it's basically<00:23:18.600> a<00:23:18.760> monopoly<00:23:19.279> so<00:23:19.440> the<00:23:19.559> solver<00:23:19.919> can 00:23:20.149 --> 00:23:20.159 align:start position:0% basically a monopoly so the solver can 00:23:20.159 --> 00:23:23.430 align:start position:0% basically a monopoly so the solver can just<00:23:20.360> quote<00:23:20.760> you<00:23:21.640> and<00:23:22.000> obviously<00:23:22.919> he<00:23:23.080> has<00:23:23.240> an 00:23:23.430 --> 00:23:23.440 align:start position:0% just quote you and obviously he has an 00:23:23.440 --> 00:23:25.310 align:start position:0% just quote you and obviously he has an information<00:23:24.000> advantage<00:23:24.480> over<00:23:24.760> you<00:23:25.039> unless 00:23:25.310 --> 00:23:25.320 align:start position:0% information advantage over you unless 00:23:25.320 --> 00:23:27.190 align:start position:0% information advantage over you unless you're<00:23:25.559> very<00:23:25.840> sophisticated<00:23:26.840> you<00:23:26.960> don't 00:23:27.190 --> 00:23:27.200 align:start position:0% you're very sophisticated you don't 00:23:27.200 --> 00:23:28.830 align:start position:0% you're very sophisticated you don't really<00:23:27.440> know<00:23:27.720> if<00:23:27.919> that<00:23:28.120> price<00:23:28.559> you're<00:23:28.679> getting 00:23:28.830 --> 00:23:28.840 align:start position:0% really know if that price you're getting 00:23:28.840 --> 00:23:30.549 align:start position:0% really know if that price you're getting quoted<00:23:29.240> right<00:23:29.360> now<00:23:29.520> is<00:23:29.640> a<00:23:29.760> good<00:23:29.960> price<00:23:30.200> for<00:23:30.360> you 00:23:30.549 --> 00:23:30.559 align:start position:0% quoted right now is a good price for you 00:23:30.559 --> 00:23:33.870 align:start position:0% quoted right now is a good price for you or<00:23:30.720> not<00:23:31.080> unless<00:23:31.799> you<00:23:31.960> go<00:23:32.240> back<00:23:32.400> to<00:23:32.880> basically 00:23:33.870 --> 00:23:33.880 align:start position:0% or not unless you go back to basically 00:23:33.880 --> 00:23:35.549 align:start position:0% or not unless you go back to basically doing<00:23:34.200> all<00:23:34.360> the<00:23:34.559> research<00:23:35.120> that<00:23:35.279> you<00:23:35.360> would 00:23:35.549 --> 00:23:35.559 align:start position:0% doing all the research that you would 00:23:35.559 --> 00:23:39.070 align:start position:0% doing all the research that you would have<00:23:36.159> to<00:23:36.320> do<00:23:36.600> yourself<00:23:36.919> in<00:23:37.039> a<00:23:37.400> transaction<00:23:38.400> um 00:23:39.070 --> 00:23:39.080 align:start position:0% have to do yourself in a transaction um 00:23:39.080 --> 00:23:42.149 align:start position:0% have to do yourself in a transaction um based<00:23:40.080> um<00:23:40.480> system<00:23:41.159> but<00:23:41.400> even<00:23:41.720> let's<00:23:41.880> say<00:23:42.039> if 00:23:42.149 --> 00:23:42.159 align:start position:0% based um system but even let's say if 00:23:42.159 --> 00:23:46.029 align:start position:0% based um system but even let's say if there<00:23:42.279> are<00:23:42.440> two<00:23:42.600> or<00:23:42.760> three<00:23:43.200> solvers<00:23:44.200> um<00:23:45.159> the 00:23:46.029 --> 00:23:46.039 align:start position:0% there are two or three solvers um the 00:23:46.039 --> 00:23:48.789 align:start position:0% there are two or three solvers um the the<00:23:46.240> problem<00:23:46.520> of<00:23:47.279> collusion<00:23:48.279> could<00:23:48.440> still<00:23:48.640> be 00:23:48.789 --> 00:23:48.799 align:start position:0% the problem of collusion could still be 00:23:48.799 --> 00:23:50.830 align:start position:0% the problem of collusion could still be pretty<00:23:49.039> prevalent<00:23:49.559> where<00:23:49.760> the<00:23:49.919> solvers<00:23:50.440> just 00:23:50.830 --> 00:23:50.840 align:start position:0% pretty prevalent where the solvers just 00:23:50.840 --> 00:23:53.390 align:start position:0% pretty prevalent where the solvers just basically<00:23:51.840> talk<00:23:52.039> to<00:23:52.200> each<00:23:52.320> other<00:23:53.039> and<00:23:53.200> they're 00:23:53.390 --> 00:23:53.400 align:start position:0% basically talk to each other and they're 00:23:53.400 --> 00:23:55.510 align:start position:0% basically talk to each other and they're like<00:23:53.679> hey<00:23:53.840> look<00:23:54.200> let's<00:23:54.480> all<00:23:54.799> just<00:23:55.000> like<00:23:55.200> quote 00:23:55.510 --> 00:23:55.520 align:start position:0% like hey look let's all just like quote 00:23:55.520 --> 00:23:57.430 align:start position:0% like hey look let's all just like quote a<00:23:55.640> little<00:23:55.799> bit<00:23:56.000> higher<00:23:56.360> price<00:23:56.799> and<00:23:56.960> we<00:23:57.080> skim 00:23:57.430 --> 00:23:57.440 align:start position:0% a little bit higher price and we skim 00:23:57.440 --> 00:23:58.950 align:start position:0% a little bit higher price and we skim some<00:23:57.600> money<00:23:57.799> of<00:23:57.960> the<00:23:58.080> user 00:23:58.950 --> 00:23:58.960 align:start position:0% some money of the user 00:23:58.960 --> 00:24:02.149 align:start position:0% some money of the user and<00:23:59.080> then<00:23:59.240> we<00:23:59.360> share<00:23:59.640> that<00:23:59.799> in<00:23:59.919> the<00:24:00.039> end<00:24:00.960> so<00:24:01.960> for 00:24:02.149 --> 00:24:02.159 align:start position:0% and then we share that in the end so for 00:24:02.159 --> 00:24:05.070 align:start position:0% and then we share that in the end so for solver<00:24:02.600> systems<00:24:02.960> to<00:24:03.400> actually<00:24:04.400> um 00:24:05.070 --> 00:24:05.080 align:start position:0% solver systems to actually um 00:24:05.080 --> 00:24:07.990 align:start position:0% solver systems to actually um sufficiently<00:24:05.720> work<00:24:06.559> we<00:24:06.760> need<00:24:07.120> a<00:24:07.320> competitive 00:24:07.990 --> 00:24:08.000 align:start position:0% sufficiently work we need a competitive 00:24:08.000 --> 00:24:11.750 align:start position:0% sufficiently work we need a competitive market<00:24:09.000> and<00:24:09.480> creating<00:24:10.000> a<00:24:10.200> competitive<00:24:10.760> market 00:24:11.750 --> 00:24:11.760 align:start position:0% market and creating a competitive market 00:24:11.760 --> 00:24:17.029 align:start position:0% market and creating a competitive market is<00:24:12.720> um<00:24:13.159> a<00:24:13.400> question<00:24:14.400> of<00:24:15.400> you<00:24:15.520> know<00:24:16.400> demand<00:24:16.960> at 00:24:17.029 --> 00:24:17.039 align:start position:0% is um a question of you know demand at 00:24:17.039 --> 00:24:18.830 align:start position:0% is um a question of you know demand at the<00:24:17.159> end<00:24:17.320> of<00:24:17.440> the<00:24:17.559> day<00:24:18.000> if<00:24:18.159> there's<00:24:18.440> enough 00:24:18.830 --> 00:24:18.840 align:start position:0% the end of the day if there's enough 00:24:18.840 --> 00:24:23.070 align:start position:0% the end of the day if there's enough demand<00:24:19.799> then<00:24:20.279> enough<00:24:20.640> solvers<00:24:21.360> will<00:24:21.679> show<00:24:22.080> up 00:24:23.070 --> 00:24:23.080 align:start position:0% demand then enough solvers will show up 00:24:23.080 --> 00:24:25.750 align:start position:0% demand then enough solvers will show up um<00:24:23.720> but<00:24:24.200> also<00:24:24.559> on<00:24:24.840> their<00:24:25.080> end<00:24:25.320> it<00:24:25.440> becomes 00:24:25.750 --> 00:24:25.760 align:start position:0% um but also on their end it becomes 00:24:25.760 --> 00:24:27.750 align:start position:0% um but also on their end it becomes about<00:24:25.960> like<00:24:26.159> scalability<00:24:26.720> of<00:24:26.919> infrastructure 00:24:27.750 --> 00:24:27.760 align:start position:0% about like scalability of infrastructure 00:24:27.760 --> 00:24:31.070 align:start position:0% about like scalability of infrastructure again<00:24:28.520> where<00:24:29.200> you<00:24:29.360> know<00:24:29.720> demand<00:24:30.159> might<00:24:30.440> pop<00:24:30.720> up 00:24:31.070 --> 00:24:31.080 align:start position:0% again where you know demand might pop up 00:24:31.080 --> 00:24:34.149 align:start position:0% again where you know demand might pop up anywhere<00:24:32.080> at<00:24:32.279> any<00:24:32.480> point<00:24:32.679> in<00:24:32.880> time<00:24:33.600> and<00:24:33.919> a<00:24:34.000> lot 00:24:34.149 --> 00:24:34.159 align:start position:0% anywhere at any point in time and a lot 00:24:34.159 --> 00:24:36.190 align:start position:0% anywhere at any point in time and a lot of<00:24:34.279> that<00:24:34.480> is<00:24:34.600> like<00:24:34.760> uninformed<00:24:35.399> flow<00:24:35.919> in<00:24:36.039> a 00:24:36.190 --> 00:24:36.200 align:start position:0% of that is like uninformed flow in a 00:24:36.200 --> 00:24:40.389 align:start position:0% of that is like uninformed flow in a sense<00:24:37.039> so<00:24:37.320> I<00:24:37.480> think<00:24:37.960> Dux<00:24:38.880> can<00:24:39.159> look<00:24:39.520> good<00:24:40.240> but 00:24:40.389 --> 00:24:40.399 align:start position:0% sense so I think Dux can look good but 00:24:40.399 --> 00:24:42.149 align:start position:0% sense so I think Dux can look good but it's<00:24:40.600> kind<00:24:40.760> of<00:24:40.919> like<00:24:41.159> getting<00:24:41.440> scammed<00:24:41.880> in<00:24:42.000> a 00:24:42.149 --> 00:24:42.159 align:start position:0% it's kind of like getting scammed in a 00:24:42.159 --> 00:24:44.789 align:start position:0% it's kind of like getting scammed in a taxi<00:24:42.559> you<00:24:42.679> know<00:24:43.120> you<00:24:43.320> really<00:24:43.600> have<00:24:43.720> to<00:24:43.960> know 00:24:44.789 --> 00:24:44.799 align:start position:0% taxi you know you really have to know 00:24:44.799 --> 00:24:47.149 align:start position:0% taxi you know you really have to know the<00:24:44.960> environment<00:24:45.640> like<00:24:46.000> if<00:24:46.120> you<00:24:46.360> guys<00:24:46.760> grab<00:24:47.000> a 00:24:47.149 --> 00:24:47.159 align:start position:0% the environment like if you guys grab a 00:24:47.159 --> 00:24:49.430 align:start position:0% the environment like if you guys grab a taxi<00:24:47.520> here<00:24:47.640> in<00:24:47.760> Thailand<00:24:48.480> you're<00:24:48.679> not<00:24:48.799> a<00:24:48.960> local 00:24:49.430 --> 00:24:49.440 align:start position:0% taxi here in Thailand you're not a local 00:24:49.440 --> 00:24:51.549 align:start position:0% taxi here in Thailand you're not a local you<00:24:49.559> don't<00:24:49.760> know<00:24:49.960> the<00:24:50.159> prices<00:24:51.039> how<00:24:51.200> would<00:24:51.360> you 00:24:51.549 --> 00:24:51.559 align:start position:0% you don't know the prices how would you 00:24:51.559 --> 00:24:53.870 align:start position:0% you don't know the prices how would you know<00:24:52.399> if<00:24:52.520> you're<00:24:52.679> getting<00:24:52.880> scammed<00:24:53.360> right<00:24:53.520> now 00:24:53.870 --> 00:24:53.880 align:start position:0% know if you're getting scammed right now 00:24:53.880 --> 00:24:56.830 align:start position:0% know if you're getting scammed right now or 00:24:56.830 --> 00:24:56.840 align:start position:0% 00:24:56.840 --> 00:25:01.789 align:start position:0% not<00:24:57.840> so<00:24:58.799> uh<00:24:59.799> you<00:24:59.960> would<00:25:00.240> put<00:25:00.440> the<00:25:00.679> focus<00:25:01.240> in 00:25:01.789 --> 00:25:01.799 align:start position:0% not so uh you would put the focus in 00:25:01.799 --> 00:25:03.950 align:start position:0% not so uh you would put the focus in decentralizing<00:25:02.799> the<00:25:03.200> the<00:25:03.360> whole 00:25:03.950 --> 00:25:03.960 align:start position:0% decentralizing the the whole 00:25:03.960 --> 00:25:06.830 align:start position:0% decentralizing the the whole infrastructure<00:25:04.919> I<00:25:05.000> would<00:25:05.240> say<00:25:05.840> or<00:25:06.080> increasing 00:25:06.830 --> 00:25:06.840 align:start position:0% infrastructure I would say or increasing 00:25:06.840 --> 00:25:09.549 align:start position:0% infrastructure I would say or increasing the<00:25:07.799> the<00:25:08.000> competitiveness<00:25:08.919> of<00:25:09.159> the 00:25:09.549 --> 00:25:09.559 align:start position:0% the the competitiveness of the 00:25:09.559 --> 00:25:11.630 align:start position:0% the the competitiveness of the competition<00:25:10.080> increasing<00:25:11.080> I<00:25:11.200> think<00:25:11.480> yeah 00:25:11.630 --> 00:25:11.640 align:start position:0% competition increasing I think yeah 00:25:11.640 --> 00:25:15.070 align:start position:0% competition increasing I think yeah competition<00:25:12.200> is<00:25:12.440> more<00:25:12.960> important<00:25:13.960> than 00:25:15.070 --> 00:25:15.080 align:start position:0% competition is more important than 00:25:15.080 --> 00:25:18.669 align:start position:0% competition is more important than decentralization<00:25:16.080> from<00:25:16.279> a<00:25:16.520> perspective<00:25:17.679> of 00:25:18.669 --> 00:25:18.679 align:start position:0% decentralization from a perspective of 00:25:18.679 --> 00:25:21.230 align:start position:0% decentralization from a perspective of you<00:25:18.799> know<00:25:19.240> like<00:25:20.240> competition<00:25:20.679> could<00:25:20.840> also<00:25:21.039> be 00:25:21.230 --> 00:25:21.240 align:start position:0% you know like competition could also be 00:25:21.240 --> 00:25:23.310 align:start position:0% you know like competition could also be great<00:25:21.520> between<00:25:21.840> tree<00:25:22.120> solver<00:25:22.679> if<00:25:22.880> the<00:25:23.039> system 00:25:23.310 --> 00:25:23.320 align:start position:0% great between tree solver if the system 00:25:23.320 --> 00:25:26.190 align:start position:0% great between tree solver if the system is<00:25:23.520> designed<00:25:23.960> well<00:25:24.200> enough<00:25:25.159> that<00:25:25.640> they<00:25:25.840> cannot 00:25:26.190 --> 00:25:26.200 align:start position:0% is designed well enough that they cannot 00:25:26.200 --> 00:25:28.590 align:start position:0% is designed well enough that they cannot collude<00:25:26.520> with<00:25:26.640> each<00:25:26.760> other<00:25:27.360> so<00:25:28.080> yeah 00:25:28.590 --> 00:25:28.600 align:start position:0% collude with each other so yeah 00:25:28.600 --> 00:25:30.549 align:start position:0% collude with each other so yeah designing<00:25:29.000> the<00:25:29.159> system<00:25:29.399> in<00:25:29.520> a<00:25:29.679> way<00:25:29.960> that<00:25:30.159> keeps 00:25:30.549 --> 00:25:30.559 align:start position:0% designing the system in a way that keeps 00:25:30.559 --> 00:25:32.269 align:start position:0% designing the system in a way that keeps everybody<00:25:31.120> competitive<00:25:31.600> with<00:25:31.799> each<00:25:31.919> other<00:25:32.120> is 00:25:32.269 --> 00:25:32.279 align:start position:0% everybody competitive with each other is 00:25:32.279 --> 00:25:33.070 align:start position:0% everybody competitive with each other is very 00:25:33.070 --> 00:25:33.080 align:start position:0% very 00:25:33.080 --> 00:25:36.029 align:start position:0% very important<00:25:34.080> makes<00:25:34.399> sense<00:25:34.960> thank 00:25:36.029 --> 00:25:36.039 align:start position:0% important makes sense thank 00:25:36.039 --> 00:25:40.430 align:start position:0% important makes sense thank you<00:25:37.039> um<00:25:37.520> the<00:25:37.679> way<00:25:38.640> I<00:25:38.799> think<00:25:39.120> about<00:25:39.360> it<00:25:39.760> and 00:25:40.430 --> 00:25:40.440 align:start position:0% you um the way I think about it and 00:25:40.440 --> 00:25:43.350 align:start position:0% you um the way I think about it and short<00:25:40.799> experience<00:25:41.159> I<00:25:41.320> have<00:25:41.640> like<00:25:42.120> um<00:25:42.760> well 00:25:43.350 --> 00:25:43.360 align:start position:0% short experience I have like um well 00:25:43.360 --> 00:25:45.070 align:start position:0% short experience I have like um well recent<00:25:43.679> experience<00:25:43.960> in<00:25:44.080> web<00:25:44.279> 2<00:25:44.520> and<00:25:44.640> now<00:25:44.880> web 00:25:45.070 --> 00:25:45.080 align:start position:0% recent experience in web 2 and now web 00:25:45.080 --> 00:25:48.110 align:start position:0% recent experience in web 2 and now web free<00:25:45.760> is<00:25:45.960> that<00:25:46.399> user<00:25:46.760> experience<00:25:47.760> is<00:25:47.919> really 00:25:48.110 --> 00:25:48.120 align:start position:0% free is that user experience is really 00:25:48.120 --> 00:25:51.710 align:start position:0% free is that user experience is really important<00:25:48.360> in<00:25:48.480> web<00:25:48.640> 2<00:25:49.320> but<00:25:49.559> for<00:25:49.919> web<00:25:50.159> free<00:25:50.919> it's 00:25:51.710 --> 00:25:51.720 align:start position:0% important in web 2 but for web free it's 00:25:51.720 --> 00:25:54.230 align:start position:0% important in web 2 but for web free it's getting<00:25:52.120> there<00:25:52.679> it's<00:25:52.919> improving<00:25:53.360> a<00:25:53.520> lot<00:25:53.880> but 00:25:54.230 --> 00:25:54.240 align:start position:0% getting there it's improving a lot but 00:25:54.240 --> 00:25:57.230 align:start position:0% getting there it's improving a lot but if<00:25:54.360> you<00:25:54.559> need<00:25:54.840> to<00:25:55.200> risk<00:25:56.000> something<00:25:56.840> will<00:25:57.000> be 00:25:57.230 --> 00:25:57.240 align:start position:0% if you need to risk something will be 00:25:57.240 --> 00:26:00.230 align:start position:0% if you need to risk something will be that<00:25:57.840> and<00:25:58.399> main<00:25:58.600> focus<00:25:58.880> should<00:25:59.200> stay<00:25:59.440> on 00:26:00.230 --> 00:26:00.240 align:start position:0% that and main focus should stay on 00:26:00.240 --> 00:26:02.510 align:start position:0% that and main focus should stay on transparency<00:26:01.240> and<00:26:01.720> that's<00:26:02.039> thing<00:26:02.240> with 00:26:02.510 --> 00:26:02.520 align:start position:0% transparency and that's thing with 00:26:02.520 --> 00:26:04.630 align:start position:0% transparency and that's thing with centralization<00:26:03.240> and<00:26:03.399> everything<00:26:03.880> but<00:26:04.480> it's 00:26:04.630 --> 00:26:04.640 align:start position:0% centralization and everything but it's 00:26:04.640 --> 00:26:06.549 align:start position:0% centralization and everything but it's really<00:26:04.840> important<00:26:05.120> to<00:26:05.520> be<00:26:05.720> transparent<00:26:06.399> and 00:26:06.549 --> 00:26:06.559 align:start position:0% really important to be transparent and 00:26:06.559 --> 00:26:08.269 align:start position:0% really important to be transparent and if<00:26:06.679> there's<00:26:06.960> competition<00:26:07.760> and<00:26:07.960> everything 00:26:08.269 --> 00:26:08.279 align:start position:0% if there's competition and everything 00:26:08.279 --> 00:26:09.909 align:start position:0% if there's competition and everything and<00:26:08.440> everything<00:26:08.840> like<00:26:09.159> keeps<00:26:09.440> going<00:26:09.640> forward 00:26:09.909 --> 00:26:09.919 align:start position:0% and everything like keeps going forward 00:26:09.919 --> 00:26:12.269 align:start position:0% and everything like keeps going forward and<00:26:10.120> we<00:26:10.279> improve<00:26:10.640> and<00:26:10.840> we<00:26:10.960> get<00:26:11.120> better<00:26:11.600> in 00:26:12.269 --> 00:26:12.279 align:start position:0% and we improve and we get better in 00:26:12.279 --> 00:26:14.029 align:start position:0% and we improve and we get better in models<00:26:12.640> and<00:26:12.799> everything<00:26:13.480> I<00:26:13.559> think<00:26:13.840> that 00:26:14.029 --> 00:26:14.039 align:start position:0% models and everything I think that 00:26:14.039 --> 00:26:15.269 align:start position:0% models and everything I think that that's<00:26:14.320> like<00:26:14.480> the<00:26:14.600> most<00:26:14.760> important<00:26:15.080> thing 00:26:15.269 --> 00:26:15.279 align:start position:0% that's like the most important thing 00:26:15.279 --> 00:26:18.350 align:start position:0% that's like the most important thing that<00:26:15.360> we<00:26:15.480> should<00:26:15.679> focus<00:26:16.640> and<00:26:17.240> especially<00:26:18.080> when 00:26:18.350 --> 00:26:18.360 align:start position:0% that we should focus and especially when 00:26:18.360 --> 00:26:20.389 align:start position:0% that we should focus and especially when we're<00:26:19.360> doing<00:26:19.640> this<00:26:19.799> kind<00:26:19.919> of<00:26:20.000> things<00:26:20.279> right 00:26:20.389 --> 00:26:20.399 align:start position:0% we're doing this kind of things right 00:26:20.399 --> 00:26:22.350 align:start position:0% we're doing this kind of things right and<00:26:20.559> it's<00:26:20.799> like<00:26:21.080> money<00:26:21.360> from<00:26:21.559> others<00:26:22.000> and<00:26:22.159> you 00:26:22.350 --> 00:26:22.360 align:start position:0% and it's like money from others and you 00:26:22.360 --> 00:26:25.350 align:start position:0% and it's like money from others and you keep<00:26:22.520> put<00:26:22.760> the<00:26:23.240> Uber<00:26:23.520> taxi<00:26:24.200> example<00:26:25.039> and<00:26:25.200> the 00:26:25.350 --> 00:26:25.360 align:start position:0% keep put the Uber taxi example and the 00:26:25.360 --> 00:26:26.710 align:start position:0% keep put the Uber taxi example and the taxi<00:26:25.679> where<00:26:25.799> you<00:26:25.880> know<00:26:26.000> it<00:26:26.159> really<00:26:26.360> well<00:26:26.640> the 00:26:26.710 --> 00:26:26.720 align:start position:0% taxi where you know it really well the 00:26:26.720 --> 00:26:28.870 align:start position:0% taxi where you know it really well the Uber<00:26:27.000> not<00:26:27.200> so<00:26:27.360> much<00:26:27.640> so<00:26:27.799> it's<00:26:27.880> like<00:26:28.279> but<00:26:28.399> if<00:26:28.640> we 00:26:28.870 --> 00:26:28.880 align:start position:0% Uber not so much so it's like but if we 00:26:28.880 --> 00:26:30.430 align:start position:0% Uber not so much so it's like but if we don't<00:26:29.039> know<00:26:29.240> it<00:26:29.360> so<00:26:29.559> well<00:26:29.799> so<00:26:30.000> if<00:26:30.120> we<00:26:30.240> keep 00:26:30.430 --> 00:26:30.440 align:start position:0% don't know it so well so if we keep 00:26:30.440 --> 00:26:32.789 align:start position:0% don't know it so well so if we keep transparent<00:26:31.159> and<00:26:31.760> it's<00:26:31.960> better<00:26:32.360> and<00:26:32.559> it<00:26:32.640> will 00:26:32.789 --> 00:26:32.799 align:start position:0% transparent and it's better and it will 00:26:32.799 --> 00:26:35.029 align:start position:0% transparent and it's better and it will get<00:26:32.960> you<00:26:33.080> more<00:26:33.240> users<00:26:33.760> eventually<00:26:34.679> one<00:26:34.880> one 00:26:35.029 --> 00:26:35.039 align:start position:0% get you more users eventually one one 00:26:35.039 --> 00:26:36.269 align:start position:0% get you more users eventually one one maybe<00:26:35.279> one<00:26:35.399> more<00:26:35.600> point<00:26:35.799> that<00:26:35.919> I<00:26:36.039> just 00:26:36.269 --> 00:26:36.279 align:start position:0% maybe one more point that I just 00:26:36.279 --> 00:26:39.750 align:start position:0% maybe one more point that I just realized<00:26:36.960> um<00:26:37.440> adding<00:26:37.720> onto<00:26:38.080> this<00:26:38.799> is<00:26:39.600> the 00:26:39.750 --> 00:26:39.760 align:start position:0% realized um adding onto this is the 00:26:39.760 --> 00:26:41.870 align:start position:0% realized um adding onto this is the advantage<00:26:40.159> that<00:26:40.360> blockchains<00:26:40.799> don't<00:26:41.080> have<00:26:41.399> is 00:26:41.870 --> 00:26:41.880 align:start position:0% advantage that blockchains don't have is 00:26:41.880 --> 00:26:43.909 align:start position:0% advantage that blockchains don't have is once<00:26:42.080> the<00:26:42.279> transaction<00:26:42.880> is<00:26:43.039> settled<00:26:43.760> and 00:26:43.909 --> 00:26:43.919 align:start position:0% once the transaction is settled and 00:26:43.919 --> 00:26:46.389 align:start position:0% once the transaction is settled and inscribed<00:26:44.320> in<00:26:44.399> the<00:26:44.559> blockchain<00:26:45.559> it's<00:26:45.960> there 00:26:46.389 --> 00:26:46.399 align:start position:0% inscribed in the blockchain it's there 00:26:46.399 --> 00:26:49.190 align:start position:0% inscribed in the blockchain it's there so<00:26:46.960> that<00:26:47.200> data<00:26:47.520> will<00:26:47.720> be<00:26:47.919> available<00:26:48.360> forever 00:26:49.190 --> 00:26:49.200 align:start position:0% so that data will be available forever 00:26:49.200 --> 00:26:51.630 align:start position:0% so that data will be available forever so<00:26:49.440> unlike<00:26:49.799> web<00:26:50.000> 2<00:26:50.320> where<00:26:50.480> maybe<00:26:50.799> we<00:26:51.000> have<00:26:51.360> that 00:26:51.630 --> 00:26:51.640 align:start position:0% so unlike web 2 where maybe we have that 00:26:51.640 --> 00:26:53.110 align:start position:0% so unlike web 2 where maybe we have that kind<00:26:51.799> of<00:26:51.960> obscured<00:26:52.480> and<00:26:52.600> we<00:26:52.720> don't<00:26:52.919> really 00:26:53.110 --> 00:26:53.120 align:start position:0% kind of obscured and we don't really 00:26:53.120 --> 00:26:56.070 align:start position:0% kind of obscured and we don't really know<00:26:53.880> somebody<00:26:54.320> could<00:26:54.559> actually<00:26:54.919> go<00:26:55.120> in<00:26:55.840> and 00:26:56.070 --> 00:26:56.080 align:start position:0% know somebody could actually go in and 00:26:56.080 --> 00:26:59.389 align:start position:0% know somebody could actually go in and kind<00:26:56.200> of<00:26:56.399> prove<00:26:56.679> to<00:26:57.240> you<00:26:58.240> later<00:26:58.520> on<00:26:59.200> that<00:26:59.320> you 00:26:59.389 --> 00:26:59.399 align:start position:0% kind of prove to you later on that you 00:26:59.399 --> 00:27:01.350 align:start position:0% kind of prove to you later on that you were<00:26:59.600> getting<00:26:59.799> scammed<00:27:00.600> and<00:27:00.720> this<00:27:00.840> is<00:27:00.960> a<00:27:01.080> huge 00:27:01.350 --> 00:27:01.360 align:start position:0% were getting scammed and this is a huge 00:27:01.360 --> 00:27:03.389 align:start position:0% were getting scammed and this is a huge Advantage<00:27:01.840> obviously<00:27:02.200> that<00:27:02.399> blockchains 00:27:03.389 --> 00:27:03.399 align:start position:0% Advantage obviously that blockchains 00:27:03.399 --> 00:27:06.350 align:start position:0% Advantage obviously that blockchains have<00:27:04.080> over<00:27:05.000> like<00:27:05.120> as<00:27:05.240> an<00:27:05.399> open<00:27:05.640> system<00:27:06.039> over 00:27:06.350 --> 00:27:06.360 align:start position:0% have over like as an open system over 00:27:06.360 --> 00:27:09.190 align:start position:0% have over like as an open system over maybe<00:27:06.600> the<00:27:06.720> more<00:27:06.880> closed<00:27:07.279> systems<00:27:07.600> and<00:27:07.760> web 00:27:09.190 --> 00:27:09.200 align:start position:0% maybe the more closed systems and web 00:27:09.200 --> 00:27:12.630 align:start position:0% maybe the more closed systems and web tool<00:27:10.200> if<00:27:10.480> if<00:27:10.640> I<00:27:10.840> may<00:27:11.159> if<00:27:11.279> I<00:27:11.399> may<00:27:11.679> complement<00:27:12.399> uh 00:27:12.630 --> 00:27:12.640 align:start position:0% tool if if I may if I may complement uh 00:27:12.640 --> 00:27:16.190 align:start position:0% tool if if I may if I may complement uh what<00:27:12.880> what<00:27:13.000> you<00:27:13.080> are<00:27:13.279> saying<00:27:14.120> um<00:27:14.880> it<00:27:15.120> feels<00:27:16.120> it 00:27:16.190 --> 00:27:16.200 align:start position:0% what what you are saying um it feels it 00:27:16.200 --> 00:27:19.190 align:start position:0% what what you are saying um it feels it feels<00:27:16.480> a<00:27:16.640> bit<00:27:16.960> like<00:27:17.799> uh<00:27:17.919> we<00:27:18.080> are<00:27:18.559> simplifying 00:27:19.190 --> 00:27:19.200 align:start position:0% feels a bit like uh we are simplifying 00:27:19.200 --> 00:27:21.669 align:start position:0% feels a bit like uh we are simplifying and<00:27:19.399> taking<00:27:19.760> complexity<00:27:20.520> out<00:27:20.720> of<00:27:20.919> users<00:27:21.480> but 00:27:21.669 --> 00:27:21.679 align:start position:0% and taking complexity out of users but 00:27:21.679 --> 00:27:22.909 align:start position:0% and taking complexity out of users but at<00:27:21.799> the<00:27:21.919> same<00:27:22.120> time<00:27:22.360> we<00:27:22.480> need<00:27:22.600> to<00:27:22.720> be 00:27:22.909 --> 00:27:22.919 align:start position:0% at the same time we need to be 00:27:22.919 --> 00:27:24.750 align:start position:0% at the same time we need to be transparent<00:27:23.559> about<00:27:23.880> how<00:27:24.000> we<00:27:24.120> are<00:27:24.279> building 00:27:24.750 --> 00:27:24.760 align:start position:0% transparent about how we are building 00:27:24.760 --> 00:27:27.470 align:start position:0% transparent about how we are building the<00:27:24.960> protocols<00:27:25.720> which<00:27:25.919> can<00:27:26.120> be<00:27:26.960> which<00:27:27.120> can<00:27:27.320> end 00:27:27.470 --> 00:27:27.480 align:start position:0% the protocols which can be which can end 00:27:27.480 --> 00:27:29.750 align:start position:0% the protocols which can be which can end up<00:27:27.679> being<00:27:27.880> more<00:27:28.320> complex<00:27:28.679> for<00:27:28.840> the<00:27:28.960> user<00:27:29.279> to 00:27:29.750 --> 00:27:29.760 align:start position:0% up being more complex for the user to 00:27:29.760 --> 00:27:31.990 align:start position:0% up being more complex for the user to understand<00:27:30.600> that<00:27:30.799> the<00:27:30.960> initial<00:27:31.640> let's<00:27:31.840> say 00:27:31.990 --> 00:27:32.000 align:start position:0% understand that the initial let's say 00:27:32.000 --> 00:27:37.269 align:start position:0% understand that the initial let's say slipage<00:27:32.559> or<00:27:32.919> gas<00:27:33.559> gas<00:27:33.799> setup<00:27:34.799> so<00:27:35.440> I<00:27:35.559> think<00:27:36.279> the 00:27:37.269 --> 00:27:37.279 align:start position:0% slipage or gas gas setup so I think the 00:27:37.279 --> 00:27:41.630 align:start position:0% slipage or gas gas setup so I think the the<00:27:37.880> the<00:27:38.880> the<00:27:39.080> point<00:27:39.399> here<00:27:39.679> is<00:27:40.320> that<00:27:41.320> we<00:27:41.440> need 00:27:41.630 --> 00:27:41.640 align:start position:0% the the the point here is that we need 00:27:41.640 --> 00:27:45.310 align:start position:0% the the the point here is that we need to<00:27:41.880> make<00:27:42.120> sure<00:27:42.559> that<00:27:43.039> the<00:27:43.960> infrastructure<00:27:44.960> or 00:27:45.310 --> 00:27:45.320 align:start position:0% to make sure that the infrastructure or 00:27:45.320 --> 00:27:48.470 align:start position:0% to make sure that the infrastructure or the<00:27:45.960> uh<00:27:46.399> or<00:27:46.640> the<00:27:46.799> ecosystem<00:27:47.399> is<00:27:47.640> decentralized 00:27:48.470 --> 00:27:48.480 align:start position:0% the uh or the ecosystem is decentralized 00:27:48.480 --> 00:27:51.389 align:start position:0% the uh or the ecosystem is decentralized or<00:27:48.760> it<00:27:48.960> has<00:27:49.200> enough<00:27:50.159> competitors<00:27:50.960> so<00:27:51.240> they 00:27:51.389 --> 00:27:51.399 align:start position:0% or it has enough competitors so they 00:27:51.399 --> 00:27:53.710 align:start position:0% or it has enough competitors so they canot<00:27:51.840> collude<00:27:52.240> or<00:27:52.399> they<00:27:52.519> cannot<00:27:52.799> screw<00:27:53.120> the 00:27:53.710 --> 00:27:53.720 align:start position:0% canot collude or they cannot screw the 00:27:53.720 --> 00:27:57.470 align:start position:0% canot collude or they cannot screw the users<00:27:54.720> but<00:27:55.559> uh<00:27:55.760> it's<00:27:56.000> more<00:27:56.279> for<00:27:56.880> making<00:27:57.200> sure 00:27:57.470 --> 00:27:57.480 align:start position:0% users but uh it's more for making sure 00:27:57.480 --> 00:27:59.070 align:start position:0% users but uh it's more for making sure that<00:27:57.600> the<00:27:57.720> user<00:27:58.159> experience<00:27:58.480> is<00:27:58.600> going<00:27:58.760> to<00:27:58.880> be 00:27:59.070 --> 00:27:59.080 align:start position:0% that the user experience is going to be 00:27:59.080 --> 00:28:01.269 align:start position:0% that the user experience is going to be good<00:27:59.399> rather<00:27:59.679> than<00:27:59.840> to<00:28:00.080> explaining<00:28:00.679> that<00:28:01.000> to 00:28:01.269 --> 00:28:01.279 align:start position:0% good rather than to explaining that to 00:28:01.279 --> 00:28:04.789 align:start position:0% good rather than to explaining that to everyone<00:28:02.000> or<00:28:02.200> to<00:28:02.360> the<00:28:02.519> users<00:28:03.120> because<00:28:04.120> uh<00:28:04.720> I 00:28:04.789 --> 00:28:04.799 align:start position:0% everyone or to the users because uh I 00:28:04.799 --> 00:28:06.830 align:start position:0% everyone or to the users because uh I don't<00:28:05.039> know<00:28:05.440> how 00:28:06.830 --> 00:28:06.840 align:start position:0% don't know how 00:28:06.840 --> 00:28:10.470 align:start position:0% don't know how how<00:28:07.840> how<00:28:08.320> we<00:28:08.440> would<00:28:08.799> explain<00:28:09.480> how<00:28:09.720> a<00:28:09.960> complex 00:28:10.470 --> 00:28:10.480 align:start position:0% how how we would explain how a complex 00:28:10.480 --> 00:28:13.350 align:start position:0% how how we would explain how a complex system<00:28:10.919> like<00:28:11.080> an<00:28:11.279> intent<00:28:11.799> system<00:28:12.200> worked<00:28:12.840> to<00:28:13.080> a 00:28:13.350 --> 00:28:13.360 align:start position:0% system like an intent system worked to a 00:28:13.360 --> 00:28:15.430 align:start position:0% system like an intent system worked to a retail<00:28:13.760> user<00:28:14.200> for<00:28:14.360> example<00:28:14.880> I<00:28:15.039> I<00:28:15.120> don't<00:28:15.360> I 00:28:15.430 --> 00:28:15.440 align:start position:0% retail user for example I I don't I 00:28:15.440 --> 00:28:19.630 align:start position:0% retail user for example I I don't I don't<00:28:15.600> know<00:28:16.200> how<00:28:16.440> we<00:28:16.559> would<00:28:16.799> find<00:28:17.039> the 00:28:19.630 --> 00:28:19.640 align:start position:0% 00:28:19.640 --> 00:28:23.310 align:start position:0% way<00:28:20.640> I<00:28:20.760> think<00:28:21.320> um<00:28:22.320> I<00:28:22.399> think<00:28:22.559> ux<00:28:22.880> is<00:28:23.080> super 00:28:23.310 --> 00:28:23.320 align:start position:0% way I think um I think ux is super 00:28:23.320 --> 00:28:25.269 align:start position:0% way I think um I think ux is super important<00:28:23.960> and<00:28:24.159> like<00:28:24.360> I<00:28:24.480> don't<00:28:24.720> I<00:28:24.799> don't<00:28:25.000> think 00:28:25.269 --> 00:28:25.279 align:start position:0% important and like I don't I don't think 00:28:25.279 --> 00:28:28.110 align:start position:0% important and like I don't I don't think anything<00:28:25.760> that<00:28:26.519> I<00:28:26.720> I<00:28:26.799> don't<00:28:27.000> think<00:28:27.799> NE 00:28:28.110 --> 00:28:28.120 align:start position:0% anything that I I don't think NE 00:28:28.120 --> 00:28:29.549 align:start position:0% anything that I I don't think NE necessarily<00:28:28.559> that<00:28:28.720> you<00:28:28.840> know<00:28:28.960> you<00:28:29.240> you<00:28:29.360> never 00:28:29.549 --> 00:28:29.559 align:start position:0% necessarily that you know you you never 00:28:29.559 --> 00:28:31.149 align:start position:0% necessarily that you know you you never want<00:28:29.640> to<00:28:30.039> at<00:28:30.120> least<00:28:30.279> with<00:28:30.640> intense<00:28:30.960> you<00:28:31.039> don't 00:28:31.149 --> 00:28:31.159 align:start position:0% want to at least with intense you don't 00:28:31.159 --> 00:28:32.509 align:start position:0% want to at least with intense you don't want<00:28:31.240> to<00:28:31.320> ever<00:28:31.519> compromise<00:28:31.919> that<00:28:32.080> ux<00:28:32.360> that 00:28:32.509 --> 00:28:32.519 align:start position:0% want to ever compromise that ux that 00:28:32.519 --> 00:28:35.789 align:start position:0% want to ever compromise that ux that users<00:28:33.279> have<00:28:33.720> now<00:28:34.440> at<00:28:34.559> least<00:28:35.399> um<00:28:35.519> you<00:28:35.600> know<00:28:35.720> you 00:28:35.789 --> 00:28:35.799 align:start position:0% users have now at least um you know you 00:28:35.799 --> 00:28:37.190 align:start position:0% users have now at least um you know you have<00:28:35.919> a<00:28:36.080> better<00:28:36.279> price<00:28:36.519> so<00:28:36.720> you<00:28:36.799> want<00:28:36.919> to<00:28:37.039> keep 00:28:37.190 --> 00:28:37.200 align:start position:0% have a better price so you want to keep 00:28:37.200 --> 00:28:38.190 align:start position:0% have a better price so you want to keep the<00:28:37.320> better<00:28:37.519> price<00:28:37.720> and<00:28:37.880> you<00:28:37.960> have<00:28:38.080> this 00:28:38.190 --> 00:28:38.200 align:start position:0% the better price and you have this 00:28:38.200 --> 00:28:39.549 align:start position:0% the better price and you have this better<00:28:38.399> user<00:28:38.679> experience<00:28:39.080> it's<00:28:39.200> better<00:28:39.399> than 00:28:39.549 --> 00:28:39.559 align:start position:0% better user experience it's better than 00:28:39.559 --> 00:28:41.669 align:start position:0% better user experience it's better than having<00:28:39.760> to<00:28:40.159> to<00:28:40.320> search<00:28:40.559> for<00:28:40.760> it<00:28:40.919> yourself<00:28:41.440> it's 00:28:41.669 --> 00:28:41.679 align:start position:0% having to to search for it yourself it's 00:28:41.679 --> 00:28:44.269 align:start position:0% having to to search for it yourself it's it's<00:28:41.840> much<00:28:42.039> easier<00:28:42.399> for<00:28:42.760> for<00:28:43.000> for<00:28:43.200> everyone<00:28:44.200> I 00:28:44.269 --> 00:28:44.279 align:start position:0% it's much easier for for for everyone I 00:28:44.279 --> 00:28:45.669 align:start position:0% it's much easier for for for everyone I would<00:28:44.519> say<00:28:44.880> just<00:28:45.000> to<00:28:45.159> add<00:28:45.320> on<00:28:45.440> to<00:28:45.559> what 00:28:45.669 --> 00:28:45.679 align:start position:0% would say just to add on to what 00:28:45.679 --> 00:28:47.909 align:start position:0% would say just to add on to what everyone<00:28:45.919> else<00:28:46.080> has<00:28:46.240> already<00:28:46.600> kind<00:28:46.720> of<00:28:47.399> echoed 00:28:47.909 --> 00:28:47.919 align:start position:0% everyone else has already kind of echoed 00:28:47.919 --> 00:28:50.029 align:start position:0% everyone else has already kind of echoed but<00:28:48.760> um<00:28:49.080> just<00:28:49.320> just<00:28:49.519> the<00:28:49.640> way<00:28:49.760> that<00:28:49.919> these 00:28:50.029 --> 00:28:50.039 align:start position:0% but um just just the way that these 00:28:50.039 --> 00:28:51.870 align:start position:0% but um just just the way that these Protocols<00:28:50.440> are<00:28:50.600> designed<00:28:51.039> to<00:28:51.200> make<00:28:51.360> sure<00:28:51.640> that 00:28:51.870 --> 00:28:51.880 align:start position:0% Protocols are designed to make sure that 00:28:51.880 --> 00:28:54.389 align:start position:0% Protocols are designed to make sure that they<00:28:52.279> they're<00:28:52.600> open<00:28:53.600> um<00:28:53.720> that<00:28:53.840> there's<00:28:54.000> clear 00:28:54.389 --> 00:28:54.399 align:start position:0% they they're open um that there's clear 00:28:54.399 --> 00:28:56.430 align:start position:0% they they're open um that there's clear documentation<00:28:55.240> so<00:28:55.799> that<00:28:55.919> there's<00:28:56.120> not<00:28:56.320> it's 00:28:56.430 --> 00:28:56.440 align:start position:0% documentation so that there's not it's 00:28:56.440 --> 00:28:57.710 align:start position:0% documentation so that there's not it's not<00:28:56.559> like<00:28:56.640> an<00:28:56.760> airline<00:28:57.159> industry<00:28:57.519> where<00:28:57.640> the 00:28:57.710 --> 00:28:57.720 align:start position:0% not like an airline industry where the 00:28:57.720 --> 00:29:00.190 align:start position:0% not like an airline industry where the barrier<00:28:58.200> to<00:28:58.320> entry<00:28:58.679> is<00:28:58.960> like<00:28:59.320> you<00:28:59.440> know<00:29:00.039> it's 00:29:00.190 --> 00:29:00.200 align:start position:0% barrier to entry is like you know it's 00:29:00.200 --> 00:29:02.230 align:start position:0% barrier to entry is like you know it's not<00:29:00.480> possible<00:29:01.480> um<00:29:01.640> so<00:29:01.760> you<00:29:01.840> know<00:29:01.960> if<00:29:02.039> someone 00:29:02.230 --> 00:29:02.240 align:start position:0% not possible um so you know if someone 00:29:02.240 --> 00:29:03.630 align:start position:0% not possible um so you know if someone wants<00:29:02.399> to<00:29:02.480> be<00:29:02.559> a<00:29:02.679> solver<00:29:03.080> if<00:29:03.159> someone<00:29:03.399> wants 00:29:03.630 --> 00:29:03.640 align:start position:0% wants to be a solver if someone wants 00:29:03.640 --> 00:29:05.789 align:start position:0% wants to be a solver if someone wants them<00:29:04.039> um<00:29:04.159> route<00:29:04.440> liquidity<00:29:05.240> if<00:29:05.360> someone<00:29:05.600> wants 00:29:05.789 --> 00:29:05.799 align:start position:0% them um route liquidity if someone wants 00:29:05.799 --> 00:29:08.389 align:start position:0% them um route liquidity if someone wants them<00:29:06.120> if<00:29:06.200> a<00:29:06.320> market<00:29:06.559> maker<00:29:06.919> wants<00:29:07.159> to<00:29:07.320> earn<00:29:08.279> uh 00:29:08.389 --> 00:29:08.399 align:start position:0% them if a market maker wants to earn uh 00:29:08.399 --> 00:29:09.950 align:start position:0% them if a market maker wants to earn uh money<00:29:08.760> this<00:29:08.919> way<00:29:09.240> that<00:29:09.480> that<00:29:09.640> that<00:29:09.760> there's 00:29:09.950 --> 00:29:09.960 align:start position:0% money this way that that that there's 00:29:09.960 --> 00:29:10.870 align:start position:0% money this way that that that there's clear 00:29:10.870 --> 00:29:10.880 align:start position:0% clear 00:29:10.880 --> 00:29:13.230 align:start position:0% clear documentation<00:29:11.880> um<00:29:12.120> and<00:29:12.240> that<00:29:12.440> Protocols<00:29:13.039> are 00:29:13.230 --> 00:29:13.240 align:start position:0% documentation um and that Protocols are 00:29:13.240 --> 00:29:16.430 align:start position:0% documentation um and that Protocols are set<00:29:13.480> up<00:29:13.720> to<00:29:14.559> um<00:29:14.720> be<00:29:14.960> open<00:29:15.679> you<00:29:15.799> know<00:29:16.080> and<00:29:16.240> and 00:29:16.430 --> 00:29:16.440 align:start position:0% set up to um be open you know and and 00:29:16.440 --> 00:29:17.870 align:start position:0% set up to um be open you know and and have<00:29:16.640> these<00:29:16.919> these<00:29:17.080> ethos<00:29:17.480> that<00:29:17.559> we're<00:29:17.799> that 00:29:17.870 --> 00:29:17.880 align:start position:0% have these these ethos that we're that 00:29:17.880 --> 00:29:19.630 align:start position:0% have these these ethos that we're that we're<00:29:18.039> kind<00:29:18.120> of<00:29:18.279> discussing<00:29:18.720> and 00:29:19.630 --> 00:29:19.640 align:start position:0% we're kind of discussing and 00:29:19.640 --> 00:29:21.310 align:start position:0% we're kind of discussing and decentralization<00:29:20.640> um<00:29:20.799> so<00:29:20.919> that<00:29:21.039> they<00:29:21.159> can 00:29:21.310 --> 00:29:21.320 align:start position:0% decentralization um so that they can 00:29:21.320 --> 00:29:24.950 align:start position:0% decentralization um so that they can easily<00:29:21.840> easily<00:29:22.200> do<00:29:22.440> so<00:29:23.440> but<00:29:24.159> I<00:29:24.240> think<00:29:24.600> like<00:29:24.760> a 00:29:24.950 --> 00:29:24.960 align:start position:0% easily easily do so but I think like a 00:29:24.960 --> 00:29:27.710 align:start position:0% easily easily do so but I think like a pattern<00:29:25.279> that<00:29:25.440> emerges<00:29:25.960> here<00:29:26.200> is<00:29:26.600> like<00:29:27.600> you 00:29:27.710 --> 00:29:27.720 align:start position:0% pattern that emerges here is like you 00:29:27.720 --> 00:29:29.590 align:start position:0% pattern that emerges here is like you just<00:29:27.840> said<00:29:28.159> we're<00:29:28.279> taking<00:29:28.600> complexity<00:29:29.360> away 00:29:29.590 --> 00:29:29.600 align:start position:0% just said we're taking complexity away 00:29:29.600 --> 00:29:31.950 align:start position:0% just said we're taking complexity away from<00:29:29.799> the<00:29:30.159> user<00:29:31.159> we're<00:29:31.399> giving<00:29:31.760> the 00:29:31.950 --> 00:29:31.960 align:start position:0% from the user we're giving the 00:29:31.960 --> 00:29:34.750 align:start position:0% from the user we're giving the complexity<00:29:32.559> to<00:29:32.760> the<00:29:32.919> system<00:29:33.840> so<00:29:34.360> you<00:29:34.480> know 00:29:34.750 --> 00:29:34.760 align:start position:0% complexity to the system so you know 00:29:34.760 --> 00:29:39.350 align:start position:0% complexity to the system so you know there's<00:29:35.120> no<00:29:36.559> um<00:29:37.559> in<00:29:37.919> you<00:29:38.039> know<00:29:38.720> in<00:29:38.880> alchemy 00:29:39.350 --> 00:29:39.360 align:start position:0% there's no um in you know in alchemy 00:29:39.360 --> 00:29:40.710 align:start position:0% there's no um in you know in alchemy there's<00:29:39.679> like<00:29:39.840> the<00:29:40.000> the<00:29:40.120> concept<00:29:40.440> of<00:29:40.559> an 00:29:40.710 --> 00:29:40.720 align:start position:0% there's like the the concept of an 00:29:40.720 --> 00:29:42.669 align:start position:0% there's like the the concept of an equivalent<00:29:41.200> exchange<00:29:41.679> you<00:29:41.799> know<00:29:41.919> you<00:29:42.120> can't 00:29:42.669 --> 00:29:42.679 align:start position:0% equivalent exchange you know you can't 00:29:42.679 --> 00:29:44.230 align:start position:0% equivalent exchange you know you can't you<00:29:42.840> can't<00:29:43.039> just<00:29:43.200> like<00:29:43.399> gain<00:29:43.720> something 00:29:44.230 --> 00:29:44.240 align:start position:0% you can't just like gain something 00:29:44.240 --> 00:29:46.190 align:start position:0% you can't just like gain something without<00:29:44.519> losing<00:29:45.000> something<00:29:45.360> else<00:29:45.919> so<00:29:46.080> you 00:29:46.190 --> 00:29:46.200 align:start position:0% without losing something else so you 00:29:46.200 --> 00:29:49.750 align:start position:0% without losing something else so you can't<00:29:46.440> just<00:29:46.640> make<00:29:46.919> you<00:29:47.159> act<00:29:47.559> like<00:29:48.279> super<00:29:49.279> good 00:29:49.750 --> 00:29:49.760 align:start position:0% can't just make you act like super good 00:29:49.760 --> 00:29:52.430 align:start position:0% can't just make you act like super good without<00:29:50.640> with<00:29:51.000> without<00:29:51.320> increasing<00:29:52.080> the 00:29:52.430 --> 00:29:52.440 align:start position:0% without with without increasing the 00:29:52.440 --> 00:29:55.149 align:start position:0% without with without increasing the complexity<00:29:53.440> somewhere<00:29:53.840> else<00:29:54.240> right<00:29:54.760> but<00:29:55.000> what 00:29:55.149 --> 00:29:55.159 align:start position:0% complexity somewhere else right but what 00:29:55.159 --> 00:29:56.750 align:start position:0% complexity somewhere else right but what we're<00:29:55.360> basically<00:29:55.760> doing<00:29:56.120> here<00:29:56.399> is<00:29:56.559> we're 00:29:56.750 --> 00:29:56.760 align:start position:0% we're basically doing here is we're 00:29:56.760 --> 00:29:59.590 align:start position:0% we're basically doing here is we're taking<00:29:57.080> that<00:29:57.200> complexity<00:29:57.679> into<00:29:57.799> the<00:29:58.080> back<00:29:58.200> end 00:29:59.590 --> 00:29:59.600 align:start position:0% taking that complexity into the back end 00:29:59.600 --> 00:30:02.149 align:start position:0% taking that complexity into the back end and<00:30:00.600> as<00:30:00.679> you<00:30:00.799> said<00:30:01.080> for<00:30:01.279> for<00:30:01.440> example<00:30:01.799> like<00:30:02.039> you 00:30:02.149 --> 00:30:02.159 align:start position:0% and as you said for for example like you 00:30:02.159 --> 00:30:04.350 align:start position:0% and as you said for for example like you want<00:30:02.279> to<00:30:02.440> keep<00:30:02.640> that<00:30:02.760> system<00:30:03.120> open<00:30:03.720> okay<00:30:04.200> that 00:30:04.350 --> 00:30:04.360 align:start position:0% want to keep that system open okay that 00:30:04.360 --> 00:30:06.470 align:start position:0% want to keep that system open okay that sounds<00:30:04.840> great<00:30:05.279> like<00:30:05.480> right<00:30:05.640> we<00:30:05.760> all<00:30:06.000> want<00:30:06.200> open 00:30:06.470 --> 00:30:06.480 align:start position:0% sounds great like right we all want open 00:30:06.480 --> 00:30:10.350 align:start position:0% sounds great like right we all want open systems<00:30:07.279> but<00:30:07.519> now<00:30:07.960> let's<00:30:08.880> what<00:30:09.159> happens<00:30:10.159> for 00:30:10.350 --> 00:30:10.360 align:start position:0% systems but now let's what happens for 00:30:10.360 --> 00:30:12.630 align:start position:0% systems but now let's what happens for example<00:30:10.720> if<00:30:10.840> you<00:30:10.960> keep<00:30:11.120> the<00:30:11.279> system<00:30:11.640> open<00:30:12.480> a 00:30:12.630 --> 00:30:12.640 align:start position:0% example if you keep the system open a 00:30:12.640 --> 00:30:15.350 align:start position:0% example if you keep the system open a solver<00:30:13.159> says<00:30:13.519> I'm<00:30:13.640> going<00:30:13.760> to<00:30:13.880> fill<00:30:14.200> this<00:30:14.360> order 00:30:15.350 --> 00:30:15.360 align:start position:0% solver says I'm going to fill this order 00:30:15.360 --> 00:30:18.789 align:start position:0% solver says I'm going to fill this order and<00:30:15.559> then<00:30:16.200> doesn't<00:30:16.519> fill<00:30:16.760> it<00:30:17.480> right<00:30:18.000> so<00:30:18.320> like 00:30:18.789 --> 00:30:18.799 align:start position:0% and then doesn't fill it right so like 00:30:18.799 --> 00:30:20.430 align:start position:0% and then doesn't fill it right so like that<00:30:18.919> means<00:30:19.320> now<00:30:19.480> if<00:30:19.600> you<00:30:19.720> keep<00:30:19.880> the<00:30:20.039> system 00:30:20.430 --> 00:30:20.440 align:start position:0% that means now if you keep the system 00:30:20.440 --> 00:30:23.190 align:start position:0% that means now if you keep the system open<00:30:21.360> that<00:30:21.480> means<00:30:21.720> you<00:30:21.840> need<00:30:22.039> to<00:30:22.679> implement 00:30:23.190 --> 00:30:23.200 align:start position:0% open that means you need to implement 00:30:23.200 --> 00:30:25.789 align:start position:0% open that means you need to implement something<00:30:23.679> like<00:30:24.120> slashing<00:30:25.080> and<00:30:25.240> then<00:30:25.559> it 00:30:25.789 --> 00:30:25.799 align:start position:0% something like slashing and then it 00:30:25.799 --> 00:30:28.430 align:start position:0% something like slashing and then it becomes<00:30:26.240> kind<00:30:26.399> of<00:30:26.960> a<00:30:27.279> a<00:30:27.399> game<00:30:27.600> of<00:30:28.000> consensus 00:30:28.430 --> 00:30:28.440 align:start position:0% becomes kind of a a game of consensus 00:30:28.440 --> 00:30:30.110 align:start position:0% becomes kind of a a game of consensus where<00:30:28.559> you're<00:30:28.760> almost 00:30:30.110 --> 00:30:30.120 align:start position:0% where you're almost 00:30:30.120 --> 00:30:32.070 align:start position:0% where you're almost basically<00:30:31.120> you're<00:30:31.279> kind<00:30:31.399> of<00:30:31.559> building<00:30:31.919> a 00:30:32.070 --> 00:30:32.080 align:start position:0% basically you're kind of building a 00:30:32.080 --> 00:30:33.470 align:start position:0% basically you're kind of building a blockchain<00:30:32.640> at<00:30:32.760> the<00:30:32.840> end<00:30:32.960> of<00:30:33.080> the<00:30:33.200> day<00:30:33.320> you 00:30:33.470 --> 00:30:33.480 align:start position:0% blockchain at the end of the day you 00:30:33.480 --> 00:30:35.470 align:start position:0% blockchain at the end of the day you build<00:30:33.679> you<00:30:33.840> rebuilding<00:30:34.360> consensus<00:30:34.960> into<00:30:35.240> that 00:30:35.470 --> 00:30:35.480 align:start position:0% build you rebuilding consensus into that 00:30:35.480 --> 00:30:38.789 align:start position:0% build you rebuilding consensus into that in<00:30:35.600> some<00:30:35.799> way<00:30:36.640> because<00:30:37.320> you<00:30:37.519> have<00:30:37.919> agents<00:30:38.679> that 00:30:38.789 --> 00:30:38.799 align:start position:0% in some way because you have agents that 00:30:38.799 --> 00:30:40.990 align:start position:0% in some way because you have agents that are<00:30:39.000> kind<00:30:39.120> of<00:30:39.279> like<00:30:39.440> validators<00:30:40.039> in<00:30:40.159> a<00:30:40.320> sense 00:30:40.990 --> 00:30:41.000 align:start position:0% are kind of like validators in a sense 00:30:41.000 --> 00:30:43.470 align:start position:0% are kind of like validators in a sense and<00:30:41.240> they<00:30:41.640> do<00:30:41.960> certain<00:30:42.320> tasks<00:30:43.080> and<00:30:43.200> you<00:30:43.360> have 00:30:43.470 --> 00:30:43.480 align:start position:0% and they do certain tasks and you have 00:30:43.480 --> 00:30:48.750 align:start position:0% and they do certain tasks and you have to<00:30:43.640> make<00:30:44.120> sure<00:30:45.440> um<00:30:46.679> that<00:30:47.679> they<00:30:47.880> can<00:30:48.080> be<00:30:48.440> like 00:30:48.750 --> 00:30:48.760 align:start position:0% to make sure um that they can be like 00:30:48.760 --> 00:30:50.950 align:start position:0% to make sure um that they can be like properly<00:30:49.320> incentivized<00:30:50.200> and<00:30:50.360> then<00:30:50.600> also 00:30:50.950 --> 00:30:50.960 align:start position:0% properly incentivized and then also 00:30:50.960 --> 00:30:54.789 align:start position:0% properly incentivized and then also properly<00:30:51.880> um<00:30:52.279> you<00:30:52.480> know<00:30:53.480> slashed<00:30:54.000> or<00:30:54.200> whatever 00:30:54.789 --> 00:30:54.799 align:start position:0% properly um you know slashed or whatever 00:30:54.799 --> 00:30:58.310 align:start position:0% properly um you know slashed or whatever if<00:30:55.000> they<00:30:55.360> misbehave<00:30:56.360> which<00:30:56.600> I<00:30:56.679> mean<00:30:58.039> in<00:30:58.200> in 00:30:58.310 --> 00:30:58.320 align:start position:0% if they misbehave which I mean in in 00:30:58.320 --> 00:30:59.789 align:start position:0% if they misbehave which I mean in in some<00:30:58.519> ways<00:30:58.679> it's<00:30:58.840> great<00:30:59.240> because<00:30:59.519> you<00:30:59.679> it 00:30:59.789 --> 00:30:59.799 align:start position:0% some ways it's great because you it 00:30:59.799 --> 00:31:01.470 align:start position:0% some ways it's great because you it means<00:30:59.960> you<00:31:00.080> can<00:31:00.200> add<00:31:00.360> a<00:31:00.480> token<00:31:00.760> onto<00:31:01.000> the<00:31:01.200> stuff 00:31:01.470 --> 00:31:01.480 align:start position:0% means you can add a token onto the stuff 00:31:01.480 --> 00:31:03.710 align:start position:0% means you can add a token onto the stuff at<00:31:01.600> some<00:31:01.799> point<00:31:02.039> you<00:31:02.159> know<00:31:02.960> but<00:31:03.159> but<00:31:03.279> you<00:31:03.440> went 00:31:03.710 --> 00:31:03.720 align:start position:0% at some point you know but but you went 00:31:03.720 --> 00:31:06.750 align:start position:0% at some point you know but but you went from<00:31:04.159> from<00:31:04.480> infrastructure<00:31:05.320> to<00:31:05.880> uh<00:31:06.320> kind<00:31:06.519> of 00:31:06.750 --> 00:31:06.760 align:start position:0% from from infrastructure to uh kind of 00:31:06.760 --> 00:31:09.669 align:start position:0% from from infrastructure to uh kind of Economics<00:31:07.360> of<00:31:07.600> the<00:31:07.919> of<00:31:08.120> the<00:31:08.679> of<00:31:08.799> the<00:31:08.960> protocol 00:31:09.669 --> 00:31:09.679 align:start position:0% Economics of the of the of the protocol 00:31:09.679 --> 00:31:13.430 align:start position:0% Economics of the of the of the protocol yeah<00:31:10.240> that's<00:31:10.600> that's<00:31:10.760> what<00:31:10.880> I<00:31:11.000> do 00:31:13.430 --> 00:31:13.440 align:start position:0% 00:31:13.440 --> 00:31:17.149 align:start position:0% sometimes<00:31:14.440> um<00:31:15.120> okay<00:31:15.559> uh<00:31:15.720> we<00:31:15.880> have<00:31:16.639> uh<00:31:16.840> we<00:31:16.960> have 00:31:17.149 --> 00:31:17.159 align:start position:0% sometimes um okay uh we have uh we have 00:31:17.159 --> 00:31:19.029 align:start position:0% sometimes um okay uh we have uh we have few<00:31:17.320> minutes<00:31:17.720> left<00:31:17.960> and<00:31:18.120> I<00:31:18.200> want<00:31:18.399> to<00:31:18.519> leave 00:31:19.029 --> 00:31:19.039 align:start position:0% few minutes left and I want to leave 00:31:19.039 --> 00:31:21.950 align:start position:0% few minutes left and I want to leave some<00:31:19.320> time<00:31:19.519> for<00:31:19.960> for<00:31:20.240> questions<00:31:21.080> so<00:31:21.480> my<00:31:21.679> last 00:31:21.950 --> 00:31:21.960 align:start position:0% some time for for questions so my last 00:31:21.960 --> 00:31:23.830 align:start position:0% some time for for questions so my last question<00:31:22.279> would 00:31:23.830 --> 00:31:23.840 align:start position:0% question would 00:31:23.840 --> 00:31:26.549 align:start position:0% question would be<00:31:24.840> I<00:31:24.960> believe<00:31:25.279> that<00:31:25.440> the<00:31:25.559> intense<00:31:26.000> ecosystem 00:31:26.549 --> 00:31:26.559 align:start position:0% be I believe that the intense ecosystem 00:31:26.559 --> 00:31:28.549 align:start position:0% be I believe that the intense ecosystem it's<00:31:26.880> uh<00:31:27.159> just<00:31:27.399> starting<00:31:27.960> so<00:31:28.080> we're<00:31:28.279> probably 00:31:28.549 --> 00:31:28.559 align:start position:0% it's uh just starting so we're probably 00:31:28.559 --> 00:31:30.190 align:start position:0% it's uh just starting so we're probably going<00:31:28.720> to<00:31:28.840> see<00:31:29.000> a<00:31:29.120> lot<00:31:29.240> of<00:31:29.399> innovation<00:31:29.919> in<00:31:30.039> the 00:31:30.190 --> 00:31:30.200 align:start position:0% going to see a lot of innovation in the 00:31:30.200 --> 00:31:33.509 align:start position:0% going to see a lot of innovation in the future<00:31:31.200> so<00:31:32.159> uh<00:31:32.519> where<00:31:32.720> do<00:31:32.840> you<00:31:32.960> see<00:31:33.360> this 00:31:33.509 --> 00:31:33.519 align:start position:0% future so uh where do you see this 00:31:33.519 --> 00:31:37.350 align:start position:0% future so uh where do you see this Innovation<00:31:34.159> happening<00:31:34.760> in<00:31:34.960> the<00:31:35.880> short<00:31:36.360> to 00:31:37.350 --> 00:31:37.360 align:start position:0% Innovation happening in the short to 00:31:37.360 --> 00:31:40.190 align:start position:0% Innovation happening in the short to midterm<00:31:38.360> uh<00:31:38.799> and<00:31:39.000> also<00:31:39.279> how<00:31:39.399> do<00:31:39.519> you<00:31:39.720> balance 00:31:40.190 --> 00:31:40.200 align:start position:0% midterm uh and also how do you balance 00:31:40.200 --> 00:31:42.909 align:start position:0% midterm uh and also how do you balance this<00:31:40.679> uh<00:31:41.080> with<00:31:41.519> security<00:31:42.039> risks<00:31:42.519> that<00:31:42.679> may 00:31:42.909 --> 00:31:42.919 align:start position:0% this uh with security risks that may 00:31:42.919 --> 00:31:46.870 align:start position:0% this uh with security risks that may come<00:31:43.799> uh<00:31:44.200> with<00:31:44.840> new<00:31:45.080> features<00:31:45.760> new<00:31:46.039> products 00:31:46.870 --> 00:31:46.880 align:start position:0% come uh with new features new products 00:31:46.880 --> 00:31:49.470 align:start position:0% come uh with new features new products um<00:31:47.240> or<00:31:47.480> new<00:31:48.080> uh<00:31:48.240> improvements<00:31:48.880> that<00:31:49.039> intents 00:31:49.470 --> 00:31:49.480 align:start position:0% um or new uh improvements that intents 00:31:49.480 --> 00:31:53.310 align:start position:0% um or new uh improvements that intents can 00:31:53.310 --> 00:31:53.320 align:start position:0% 00:31:53.320 --> 00:31:57.070 align:start position:0% bring<00:31:54.320> uh<00:31:54.720> sorry<00:31:55.440> so<00:31:55.720> I<00:31:55.799> think<00:31:56.080> I<00:31:56.159> think<00:31:56.720> um<00:31:56.880> so 00:31:57.070 --> 00:31:57.080 align:start position:0% bring uh sorry so I think I think um so 00:31:57.080 --> 00:31:58.990 align:start position:0% bring uh sorry so I think I think um so looking<00:31:57.360> ahead<00:31:57.600> I<00:31:57.679> think 00:31:58.990 --> 00:31:59.000 align:start position:0% looking ahead I think 00:31:59.000 --> 00:32:01.350 align:start position:0% looking ahead I think um<00:31:59.559> we're<00:31:59.880> now<00:32:00.080> kind<00:32:00.240> of<00:32:00.360> building<00:32:00.919> at<00:32:01.039> orbs 00:32:01.350 --> 00:32:01.360 align:start position:0% um we're now kind of building at orbs 00:32:01.360 --> 00:32:03.710 align:start position:0% um we're now kind of building at orbs anyways<00:32:01.720> we're<00:32:01.880> we're<00:32:02.080> we're<00:32:02.760> we<00:32:02.960> think<00:32:03.240> that 00:32:03.710 --> 00:32:03.720 align:start position:0% anyways we're we're we're we think that 00:32:03.720 --> 00:32:06.549 align:start position:0% anyways we're we're we're we think that the<00:32:03.840> next<00:32:04.039> thing<00:32:04.279> is<00:32:04.440> onchain<00:32:05.399> perpetuals<00:32:06.399> um 00:32:06.549 --> 00:32:06.559 align:start position:0% the next thing is onchain perpetuals um 00:32:06.559 --> 00:32:09.269 align:start position:0% the next thing is onchain perpetuals um so<00:32:07.039> like<00:32:07.200> if<00:32:07.279> you<00:32:07.399> look<00:32:07.519> at<00:32:07.799> like<00:32:08.440> spot<00:32:08.960> spot 00:32:09.269 --> 00:32:09.279 align:start position:0% so like if you look at like spot spot 00:32:09.279 --> 00:32:11.430 align:start position:0% so like if you look at like spot spot Market<00:32:09.559> to<00:32:09.799> sex<00:32:10.080> volumes<00:32:10.519> it's<00:32:10.760> like<00:32:11.159> I<00:32:11.240> think 00:32:11.430 --> 00:32:11.440 align:start position:0% Market to sex volumes it's like I think 00:32:11.440 --> 00:32:13.430 align:start position:0% Market to sex volumes it's like I think about<00:32:11.720> like<00:32:12.600> I<00:32:12.679> don't<00:32:12.840> remember<00:32:13.080> off<00:32:13.200> the<00:32:13.320> top 00:32:13.430 --> 00:32:13.440 align:start position:0% about like I don't remember off the top 00:32:13.440 --> 00:32:14.990 align:start position:0% about like I don't remember off the top of<00:32:13.480> my<00:32:13.600> head<00:32:13.720> but<00:32:13.840> it's<00:32:14.200> it's<00:32:14.399> significantly 00:32:14.990 --> 00:32:15.000 align:start position:0% of my head but it's it's significantly 00:32:15.000 --> 00:32:17.029 align:start position:0% of my head but it's it's significantly more<00:32:15.480> than<00:32:15.880> it's<00:32:16.039> huge<00:32:16.399> yeah<00:32:16.480> it's<00:32:16.639> huge<00:32:16.880> it's 00:32:17.029 --> 00:32:17.039 align:start position:0% more than it's huge yeah it's huge it's 00:32:17.039 --> 00:32:19.509 align:start position:0% more than it's huge yeah it's huge it's huge<00:32:17.559> on<00:32:17.679> dexes<00:32:18.120> it's<00:32:18.559> it's<00:32:18.720> much<00:32:18.919> larger<00:32:19.279> than 00:32:19.509 --> 00:32:19.519 align:start position:0% huge on dexes it's it's much larger than 00:32:19.519 --> 00:32:22.389 align:start position:0% huge on dexes it's it's much larger than the<00:32:19.760> than<00:32:19.880> the<00:32:20.039> percentage<00:32:20.559> of<00:32:21.559> um<00:32:21.919> Perpetual 00:32:22.389 --> 00:32:22.399 align:start position:0% the than the percentage of um Perpetual 00:32:22.399 --> 00:32:24.870 align:start position:0% the than the percentage of um Perpetual trading<00:32:22.840> happening<00:32:23.200> on<00:32:23.480> dex's<00:32:24.480> um<00:32:24.600> which<00:32:24.720> is 00:32:24.870 --> 00:32:24.880 align:start position:0% trading happening on dex's um which is 00:32:24.880 --> 00:32:28.430 align:start position:0% trading happening on dex's um which is about<00:32:25.120> like<00:32:25.240> 1%<00:32:26.159> and<00:32:26.279> the<00:32:26.399> other<00:32:26.559> 99.9%<00:32:28.000> is<00:32:28.120> on 00:32:28.430 --> 00:32:28.440 align:start position:0% about like 1% and the other 99.9% is on 00:32:28.440 --> 00:32:31.029 align:start position:0% about like 1% and the other 99.9% is on is<00:32:28.559> on<00:32:28.799> is<00:32:28.880> on<00:32:29.039> centralized<00:32:29.760> exchanges<00:32:30.760> um<00:32:30.880> so 00:32:31.029 --> 00:32:31.039 align:start position:0% is on is on centralized exchanges um so 00:32:31.039 --> 00:32:32.470 align:start position:0% is on is on centralized exchanges um so we<00:32:31.159> think<00:32:31.360> that<00:32:31.519> there's<00:32:31.880> like<00:32:32.039> one<00:32:32.200> there's<00:32:32.360> a 00:32:32.470 --> 00:32:32.480 align:start position:0% we think that there's like one there's a 00:32:32.480 --> 00:32:34.909 align:start position:0% we think that there's like one there's a huge<00:32:32.880> Market<00:32:33.240> opportunity<00:32:33.799> here<00:32:34.600> uh<00:32:34.720> people 00:32:34.909 --> 00:32:34.919 align:start position:0% huge Market opportunity here uh people 00:32:34.919 --> 00:32:37.990 align:start position:0% huge Market opportunity here uh people want<00:32:35.039> to<00:32:35.200> trade<00:32:35.840> um<00:32:36.840> uh<00:32:36.960> per<00:32:37.279> on<00:32:37.399> chain<00:32:37.760> because 00:32:37.990 --> 00:32:38.000 align:start position:0% want to trade um uh per on chain because 00:32:38.000 --> 00:32:39.110 align:start position:0% want to trade um uh per on chain because you<00:32:38.080> know<00:32:38.200> there's<00:32:38.360> a<00:32:38.440> lot<00:32:38.559> of<00:32:38.639> counterparty 00:32:39.110 --> 00:32:39.120 align:start position:0% you know there's a lot of counterparty 00:32:39.120 --> 00:32:41.509 align:start position:0% you know there's a lot of counterparty risk<00:32:39.360> that<00:32:39.519> you<00:32:39.679> have<00:32:39.960> with<00:32:40.159> Sexes<00:32:40.720> as<00:32:41.279> yeah<00:32:41.399> I 00:32:41.509 --> 00:32:41.519 align:start position:0% risk that you have with Sexes as yeah I 00:32:41.519 --> 00:32:43.149 align:start position:0% risk that you have with Sexes as yeah I don't<00:32:41.880> I<00:32:41.960> don't<00:32:42.120> think<00:32:42.240> we<00:32:42.320> need<00:32:42.440> to<00:32:42.600> go<00:32:42.960> down 00:32:43.149 --> 00:32:43.159 align:start position:0% don't I don't think we need to go down 00:32:43.159 --> 00:32:45.549 align:start position:0% don't I don't think we need to go down the<00:32:43.279> memory<00:32:43.559> lane<00:32:44.240> um<00:32:44.720> so<00:32:44.960> we<00:32:45.080> can<00:32:45.200> skip<00:32:45.440> over 00:32:45.549 --> 00:32:45.559 align:start position:0% the memory lane um so we can skip over 00:32:45.559 --> 00:32:47.389 align:start position:0% the memory lane um so we can skip over that<00:32:45.679> for<00:32:45.799> now<00:32:46.039> but<00:32:46.279> yeah<00:32:46.519> yeah<00:32:46.679> so<00:32:47.000> I<00:32:47.120> think 00:32:47.389 --> 00:32:47.399 align:start position:0% that for now but yeah yeah so I think 00:32:47.399 --> 00:32:49.750 align:start position:0% that for now but yeah yeah so I think that<00:32:47.760> for<00:32:48.039> us<00:32:48.279> this<00:32:48.399> is<00:32:48.559> kind<00:32:48.679> of<00:32:48.880> where<00:32:49.480> we're 00:32:49.750 --> 00:32:49.760 align:start position:0% that for us this is kind of where we're 00:32:49.760 --> 00:32:51.230 align:start position:0% that for us this is kind of where we're headed<00:32:50.039> in<00:32:50.240> in<00:32:50.399> this 00:32:51.230 --> 00:32:51.240 align:start position:0% headed in in this 00:32:51.240 --> 00:32:54.509 align:start position:0% headed in in this direction<00:32:52.240> um<00:32:53.039> and<00:32:53.159> yeah<00:32:53.279> in<00:32:53.360> terms<00:32:53.600> of<00:32:54.320> uh 00:32:54.509 --> 00:32:54.519 align:start position:0% direction um and yeah in terms of uh 00:32:54.519 --> 00:32:56.990 align:start position:0% direction um and yeah in terms of uh security<00:32:54.919> risks<00:32:55.919> it<00:32:56.080> really<00:32:56.320> just<00:32:56.600> depends<00:32:56.880> on 00:32:56.990 --> 00:32:57.000 align:start position:0% security risks it really just depends on 00:32:57.000 --> 00:32:59.389 align:start position:0% security risks it really just depends on the<00:32:57.080> protocol<00:32:57.480> at<00:32:57.559> the<00:32:57.639> end<00:32:57.720> of<00:32:57.960> the<00:32:58.080> day<00:32:58.279> so 00:32:59.389 --> 00:32:59.399 align:start position:0% the protocol at the end of the day so 00:32:59.399 --> 00:33:02.470 align:start position:0% the protocol at the end of the day so yeah<00:33:00.399> is<00:33:00.559> that<00:33:01.000> uh<00:33:01.159> kind<00:33:01.320> of<00:33:01.440> an<00:33:01.600> alpha<00:33:02.360> that 00:33:02.470 --> 00:33:02.480 align:start position:0% yeah is that uh kind of an alpha that 00:33:02.480 --> 00:33:05.389 align:start position:0% yeah is that uh kind of an alpha that you're<00:33:02.919> giving<00:33:03.919> I<00:33:04.000> mean<00:33:04.880> you<00:33:05.000> could<00:33:05.120> take<00:33:05.279> it 00:33:05.389 --> 00:33:05.399 align:start position:0% you're giving I mean you could take it 00:33:05.399 --> 00:33:08.350 align:start position:0% you're giving I mean you could take it as<00:33:05.799> that<00:33:06.799> it<00:33:06.960> depends<00:33:07.279> on<00:33:07.760> on<00:33:07.960> how<00:33:08.039> you<00:33:08.120> want<00:33:08.240> to 00:33:08.350 --> 00:33:08.360 align:start position:0% as that it depends on on how you want to 00:33:08.360 --> 00:33:10.830 align:start position:0% as that it depends on on how you want to look<00:33:08.480> at<00:33:08.600> it<00:33:09.120> um<00:33:09.960> yeah<00:33:10.200> I<00:33:10.279> saw<00:33:10.480> something<00:33:10.720> on 00:33:10.830 --> 00:33:10.840 align:start position:0% look at it um yeah I saw something on 00:33:10.840 --> 00:33:11.830 align:start position:0% look at it um yeah I saw something on Twitter<00:33:11.120> that<00:33:11.200> was<00:33:11.320> like<00:33:11.519> I<00:33:11.600> think<00:33:11.679> it<00:33:11.760> was 00:33:11.830 --> 00:33:11.840 align:start position:0% Twitter that was like I think it was 00:33:11.840 --> 00:33:14.230 align:start position:0% Twitter that was like I think it was like<00:33:11.960> the<00:33:12.039> GMX<00:33:12.399> model<00:33:12.639> is<00:33:12.880> like<00:33:13.320> um<00:33:13.799> like<00:33:14.039> like 00:33:14.230 --> 00:33:14.240 align:start position:0% like the GMX model is like um like like 00:33:14.240 --> 00:33:15.389 align:start position:0% like the GMX model is like um like like some<00:33:14.399> of<00:33:14.519> the<00:33:14.600> pools<00:33:14.840> are<00:33:15.000> getting<00:33:15.240> like 00:33:15.389 --> 00:33:15.399 align:start position:0% some of the pools are getting like 00:33:15.399 --> 00:33:17.070 align:start position:0% some of the pools are getting like locked<00:33:15.720> or<00:33:15.880> something<00:33:16.240> as<00:33:16.440> we're<00:33:16.639> in<00:33:16.799> like<00:33:16.880> an 00:33:17.070 --> 00:33:17.080 align:start position:0% locked or something as we're in like an 00:33:17.080 --> 00:33:20.909 align:start position:0% locked or something as we're in like an up<00:33:17.559> only<00:33:18.279> Market<00:33:19.279> um<00:33:19.760> so<00:33:20.200> you<00:33:20.320> know<00:33:20.480> and<00:33:20.639> Tents 00:33:20.909 --> 00:33:20.919 align:start position:0% up only Market um so you know and Tents 00:33:20.919 --> 00:33:23.750 align:start position:0% up only Market um so you know and Tents are<00:33:21.240> potentially<00:33:22.360> potentially<00:33:23.360> the<00:33:23.480> way<00:33:23.639> the 00:33:23.750 --> 00:33:23.760 align:start position:0% are potentially potentially the way the 00:33:23.760 --> 00:33:25.230 align:start position:0% are potentially potentially the way the way<00:33:23.960> that<00:33:24.159> that<00:33:24.320> that<00:33:24.399> it's<00:33:24.519> going<00:33:24.600> to<00:33:24.679> be<00:33:24.960> yeah 00:33:25.230 --> 00:33:25.240 align:start position:0% way that that that it's going to be yeah 00:33:25.240 --> 00:33:26.350 align:start position:0% way that that that it's going to be yeah I<00:33:25.320> mean<00:33:25.440> there's<00:33:25.600> a<00:33:25.639> lot<00:33:25.760> of<00:33:25.840> Builders<00:33:26.159> around 00:33:26.350 --> 00:33:26.360 align:start position:0% I mean there's a lot of Builders around 00:33:26.360 --> 00:33:28.750 align:start position:0% I mean there's a lot of Builders around it<00:33:26.519> still<00:33:26.799> so<00:33:27.080> so<00:33:27.279> yeah 00:33:28.750 --> 00:33:28.760 align:start position:0% it still so so yeah 00:33:28.760 --> 00:33:29.950 align:start position:0% it still so so yeah thank 00:33:29.950 --> 00:33:29.960 align:start position:0% thank 00:33:29.960 --> 00:33:32.470 align:start position:0% thank you<00:33:30.960> okay<00:33:31.279> I'm<00:33:31.440> going<00:33:31.559> to<00:33:31.720> bring<00:33:31.919> a<00:33:32.080> concept 00:33:32.470 --> 00:33:32.480 align:start position:0% you okay I'm going to bring a concept 00:33:32.480 --> 00:33:34.549 align:start position:0% you okay I'm going to bring a concept that<00:33:32.919> eventually<00:33:33.320> was<00:33:33.480> going<00:33:33.559> to<00:33:33.720> be<00:33:34.240> in<00:33:34.360> our 00:33:34.549 --> 00:33:34.559 align:start position:0% that eventually was going to be in our 00:33:34.559 --> 00:33:36.310 align:start position:0% that eventually was going to be in our conversation<00:33:35.080> it's<00:33:35.240> going<00:33:35.320> to<00:33:35.440> be 00:33:36.310 --> 00:33:36.320 align:start position:0% conversation it's going to be 00:33:36.320 --> 00:33:39.190 align:start position:0% conversation it's going to be Ai<00:33:37.320> and<00:33:38.240> with<00:33:38.399> nimic<00:33:38.799> right<00:33:38.919> now<00:33:39.039> we're 00:33:39.190 --> 00:33:39.200 align:start position:0% Ai and with nimic right now we're 00:33:39.200 --> 00:33:42.029 align:start position:0% Ai and with nimic right now we're building<00:33:39.519> a<00:33:39.720> free<00:33:40.080> layer<00:33:40.679> protocol<00:33:41.679> with 00:33:42.029 --> 00:33:42.039 align:start position:0% building a free layer protocol with 00:33:42.039 --> 00:33:45.909 align:start position:0% building a free layer protocol with intents<00:33:42.720> in<00:33:42.919> Ai<00:33:43.679> and<00:33:44.320> the<00:33:44.480> idea<00:33:45.159> is<00:33:45.360> to<00:33:45.639> create 00:33:45.909 --> 00:33:45.919 align:start position:0% intents in Ai and the idea is to create 00:33:45.919 --> 00:33:48.029 align:start position:0% intents in Ai and the idea is to create the<00:33:46.039> best<00:33:46.240> execution<00:33:46.679> plan<00:33:47.399> in<00:33:47.519> order<00:33:47.760> for<00:33:47.880> the 00:33:48.029 --> 00:33:48.039 align:start position:0% the best execution plan in order for the 00:33:48.039 --> 00:33:51.470 align:start position:0% the best execution plan in order for the user<00:33:48.679> to<00:33:49.000> later<00:33:49.360> have<00:33:49.519> the<00:33:49.639> control<00:33:50.480> and<00:33:51.279> like 00:33:51.470 --> 00:33:51.480 align:start position:0% user to later have the control and like 00:33:51.480 --> 00:33:53.310 align:start position:0% user to later have the control and like delegate<00:33:52.120> what<00:33:52.440> you<00:33:52.600> want<00:33:52.720> to<00:33:52.919> do<00:33:53.120> and 00:33:53.310 --> 00:33:53.320 align:start position:0% delegate what you want to do and 00:33:53.320 --> 00:33:55.909 align:start position:0% delegate what you want to do and everything<00:33:54.200> but<00:33:54.440> then<00:33:55.120> you<00:33:55.279> have<00:33:55.440> the<00:33:55.559> control 00:33:55.909 --> 00:33:55.919 align:start position:0% everything but then you have the control 00:33:55.919 --> 00:33:59.789 align:start position:0% everything but then you have the control to<00:33:56.480> sign<00:33:57.279> and<00:33:57.440> then<00:33:57.880> executed<00:33:58.840> so<00:33:59.279> that's<00:33:59.639> the 00:33:59.789 --> 00:33:59.799 align:start position:0% to sign and then executed so that's the 00:33:59.799 --> 00:34:03.350 align:start position:0% to sign and then executed so that's the main<00:34:00.080> role<00:34:00.320> in<00:34:00.519> security<00:34:01.360> that<00:34:01.840> we<00:34:02.039> have<00:34:02.360> and 00:34:03.350 --> 00:34:03.360 align:start position:0% main role in security that we have and 00:34:03.360 --> 00:34:06.190 align:start position:0% main role in security that we have and super<00:34:03.639> important<00:34:04.200> because<00:34:05.080> we<00:34:05.840> want<00:34:05.960> to<00:34:06.080> give 00:34:06.190 --> 00:34:06.200 align:start position:0% super important because we want to give 00:34:06.200 --> 00:34:08.629 align:start position:0% super important because we want to give the<00:34:06.320> US<00:34:06.440> for<00:34:06.559> that<00:34:06.760> control<00:34:07.600> but<00:34:07.799> we<00:34:07.960> also<00:34:08.399> have 00:34:08.629 --> 00:34:08.639 align:start position:0% the US for that control but we also have 00:34:08.639 --> 00:34:10.230 align:start position:0% the US for that control but we also have all<00:34:08.800> the<00:34:08.960> track<00:34:09.200> record<00:34:09.560> from<00:34:09.720> before<00:34:10.079> we've 00:34:10.230 --> 00:34:10.240 align:start position:0% all the track record from before we've 00:34:10.240 --> 00:34:12.030 align:start position:0% all the track record from before we've been<00:34:10.359> in<00:34:10.480> the<00:34:10.639> market<00:34:10.960> for<00:34:11.119> three<00:34:11.480> years<00:34:11.919> we 00:34:12.030 --> 00:34:12.040 align:start position:0% been in the market for three years we 00:34:12.040 --> 00:34:16.190 align:start position:0% been in the market for three years we know<00:34:12.359> how<00:34:12.679> stuff<00:34:12.919> is<00:34:13.119> done<00:34:14.079> and<00:34:14.800> we<00:34:15.000> know<00:34:15.800> how's 00:34:16.190 --> 00:34:16.200 align:start position:0% know how stuff is done and we know how's 00:34:16.200 --> 00:34:18.790 align:start position:0% know how stuff is done and we know how's the<00:34:16.399> best<00:34:16.679> way<00:34:17.119> to<00:34:17.720> with<00:34:18.000> the<00:34:18.200> mimic 00:34:18.790 --> 00:34:18.800 align:start position:0% the best way to with the mimic 00:34:18.800 --> 00:34:22.270 align:start position:0% the best way to with the mimic safeguards<00:34:19.800> to<00:34:20.480> have<00:34:20.599> it<00:34:20.720> all<00:34:20.960> like<00:34:21.159> back<00:34:21.480> up 00:34:22.270 --> 00:34:22.280 align:start position:0% safeguards to have it all like back up 00:34:22.280 --> 00:34:24.790 align:start position:0% safeguards to have it all like back up and<00:34:22.599> making<00:34:22.839> sure<00:34:23.159> the<00:34:23.280> user<00:34:24.200> doesn't<00:34:24.440> need<00:34:24.599> to 00:34:24.790 --> 00:34:24.800 align:start position:0% and making sure the user doesn't need to 00:34:24.800 --> 00:34:26.669 align:start position:0% and making sure the user doesn't need to worry<00:34:25.240> about<00:34:25.560> that<00:34:26.079> because<00:34:26.280> of<00:34:26.399> course<00:34:26.560> it's 00:34:26.669 --> 00:34:26.679 align:start position:0% worry about that because of course it's 00:34:26.679 --> 00:34:28.109 align:start position:0% worry about that because of course it's like<00:34:26.879> a<00:34:27.040> concern<00:34:27.320> and<00:34:27.440> everything<00:34:27.839> but<00:34:27.960> it's 00:34:28.109 --> 00:34:28.119 align:start position:0% like a concern and everything but it's 00:34:28.119 --> 00:34:29.589 align:start position:0% like a concern and everything but it's like<00:34:28.520> you<00:34:28.639> want<00:34:28.760> to<00:34:28.919> have<00:34:29.040> someone<00:34:29.399> that 00:34:29.589 --> 00:34:29.599 align:start position:0% like you want to have someone that 00:34:29.599 --> 00:34:32.230 align:start position:0% like you want to have someone that that's<00:34:29.800> got<00:34:29.960> your<00:34:30.119> back<00:34:30.879> so<00:34:31.639> that's<00:34:31.839> like<00:34:32.040> the 00:34:32.230 --> 00:34:32.240 align:start position:0% that's got your back so that's like the 00:34:32.240 --> 00:34:33.470 align:start position:0% that's got your back so that's like the the<00:34:32.359> main<00:34:32.560> thing<00:34:32.760> for<00:34:32.879> us<00:34:33.040> and<00:34:33.159> that's<00:34:33.320> what 00:34:33.470 --> 00:34:33.480 align:start position:0% the main thing for us and that's what 00:34:33.480 --> 00:34:34.750 align:start position:0% the main thing for us and that's what we're<00:34:33.599> building<00:34:34.000> right<00:34:34.119> now<00:34:34.399> and<00:34:34.599> we're 00:34:34.750 --> 00:34:34.760 align:start position:0% we're building right now and we're 00:34:34.760 --> 00:34:36.629 align:start position:0% we're building right now and we're launching<00:34:35.119> the<00:34:35.280> protocol<00:34:36.119> because<00:34:36.359> we're<00:34:36.520> a 00:34:36.629 --> 00:34:36.639 align:start position:0% launching the protocol because we're a 00:34:36.639 --> 00:34:38.109 align:start position:0% launching the protocol because we're a business<00:34:36.879> to<00:34:37.040> business<00:34:37.280> model<00:34:37.760> and<00:34:37.960> we've 00:34:38.109 --> 00:34:38.119 align:start position:0% business to business model and we've 00:34:38.119 --> 00:34:39.629 align:start position:0% business to business model and we've been<00:34:38.879> with<00:34:39.040> that<00:34:39.159> and<00:34:39.280> we're<00:34:39.399> going<00:34:39.480> to 00:34:39.629 --> 00:34:39.639 align:start position:0% been with that and we're going to 00:34:39.639 --> 00:34:42.109 align:start position:0% been with that and we're going to continue<00:34:40.040> with<00:34:40.200> it<00:34:40.760> but<00:34:40.919> we<00:34:41.000> want<00:34:41.119> to<00:34:41.599> give<00:34:41.760> the 00:34:42.109 --> 00:34:42.119 align:start position:0% continue with it but we want to give the 00:34:42.119 --> 00:34:43.990 align:start position:0% continue with it but we want to give the opportunity<00:34:42.560> to<00:34:42.800> more<00:34:43.040> users<00:34:43.440> to<00:34:43.679> build<00:34:43.879> on 00:34:43.990 --> 00:34:44.000 align:start position:0% opportunity to more users to build on 00:34:44.000 --> 00:34:47.230 align:start position:0% opportunity to more users to build on top<00:34:44.159> of<00:34:44.240> the<00:34:44.520> protocol<00:34:45.520> and<00:34:46.520> connect<00:34:46.879> and<00:34:47.079> be 00:34:47.230 --> 00:34:47.240 align:start position:0% top of the protocol and connect and be 00:34:47.240 --> 00:34:51.030 align:start position:0% top of the protocol and connect and be able<00:34:47.480> to<00:34:48.480> to<00:34:48.639> do<00:34:48.960> this<00:34:49.280> stuff<00:34:50.280> do<00:34:50.440> we<00:34:50.679> have<00:34:50.839> a 00:34:51.030 --> 00:34:51.040 align:start position:0% able to to do this stuff do we have a 00:34:51.040 --> 00:34:53.030 align:start position:0% able to to do this stuff do we have a date<00:34:51.320> for<00:34:51.480> the<00:34:51.679> launch<00:34:51.960> of<00:34:52.119> their<00:34:52.399> protocol 00:34:53.030 --> 00:34:53.040 align:start position:0% date for the launch of their protocol 00:34:53.040 --> 00:34:57.190 align:start position:0% date for the launch of their protocol it's<00:34:53.159> going<00:34:53.280> to<00:34:53.440> be<00:34:54.440> next<00:34:54.720> year<00:34:55.520> okay<00:34:56.359> you<00:34:56.480> can 00:34:57.190 --> 00:34:57.200 align:start position:0% it's going to be next year okay you can 00:34:57.200 --> 00:34:59.310 align:start position:0% it's going to be next year okay you can like<00:34:57.400> check<00:34:57.839> our<00:34:58.040> socials<00:34:58.560> and<00:34:59.040> we're<00:34:59.200> going 00:34:59.310 --> 00:34:59.320 align:start position:0% like check our socials and we're going 00:34:59.320 --> 00:35:01.069 align:start position:0% like check our socials and we're going to<00:34:59.400> be<00:34:59.480> sharing<00:34:59.760> more<00:34:59.920> information<00:35:00.560> sorry<00:35:00.920> I'm 00:35:01.069 --> 00:35:01.079 align:start position:0% to be sharing more information sorry I'm 00:35:01.079 --> 00:35:02.790 align:start position:0% to be sharing more information sorry I'm from<00:35:01.280> com<00:35:01.599> so<00:35:01.839> of<00:35:01.960> course<00:35:02.119> I'm<00:35:02.240> going<00:35:02.320> to<00:35:02.520> say 00:35:02.790 --> 00:35:02.800 align:start position:0% from com so of course I'm going to say 00:35:02.800 --> 00:35:05.710 align:start position:0% from com so of course I'm going to say that<00:35:03.800> but<00:35:04.200> okay<00:35:04.480> thank<00:35:04.640> you<00:35:05.000> but<00:35:05.200> yeah<00:35:05.560> it's 00:35:05.710 --> 00:35:05.720 align:start position:0% that but okay thank you but yeah it's 00:35:05.720 --> 00:35:07.670 align:start position:0% that but okay thank you but yeah it's coming<00:35:05.960> soon<00:35:06.520> and<00:35:06.760> it's<00:35:06.920> going<00:35:07.040> to<00:35:07.119> be<00:35:07.240> good 00:35:07.670 --> 00:35:07.680 align:start position:0% coming soon and it's going to be good 00:35:07.680 --> 00:35:09.910 align:start position:0% coming soon and it's going to be good cool<00:35:08.280> you<00:35:08.560> you<00:35:08.800> the<00:35:08.920> last<00:35:09.119> one<00:35:09.280> to<00:35:09.599> give<00:35:09.800> us 00:35:09.910 --> 00:35:09.920 align:start position:0% cool you you the last one to give us 00:35:09.920 --> 00:35:13.790 align:start position:0% cool you you the last one to give us some<00:35:10.200> Alpha<00:35:11.200> okay<00:35:11.800> um<00:35:12.640> yeah<00:35:12.800> I<00:35:12.880> mean<00:35:13.160> I<00:35:13.280> think 00:35:13.790 --> 00:35:13.800 align:start position:0% some Alpha okay um yeah I mean I think 00:35:13.800 --> 00:35:16.349 align:start position:0% some Alpha okay um yeah I mean I think the<00:35:13.960> alpha<00:35:14.320> for<00:35:14.599> any<00:35:15.040> type<00:35:15.400> of<00:35:15.640> protocol<00:35:16.200> that 00:35:16.349 --> 00:35:16.359 align:start position:0% the alpha for any type of protocol that 00:35:16.359 --> 00:35:19.710 align:start position:0% the alpha for any type of protocol that is<00:35:16.599> within<00:35:16.880> the<00:35:17.000> interoperability<00:35:17.920> space<00:35:18.920> um 00:35:19.710 --> 00:35:19.720 align:start position:0% is within the interoperability space um 00:35:19.720 --> 00:35:22.630 align:start position:0% is within the interoperability space um is<00:35:20.720> pretty<00:35:20.960> much<00:35:21.160> the<00:35:21.320> same<00:35:21.839> um<00:35:22.280> I<00:35:22.320> feel<00:35:22.480> like 00:35:22.630 --> 00:35:22.640 align:start position:0% is pretty much the same um I feel like 00:35:22.640 --> 00:35:25.109 align:start position:0% is pretty much the same um I feel like every<00:35:22.880> protocol<00:35:23.280> is<00:35:23.440> working<00:35:23.800> on<00:35:24.079> like<00:35:24.839> some 00:35:25.109 --> 00:35:25.119 align:start position:0% every protocol is working on like some 00:35:25.119 --> 00:35:28.589 align:start position:0% every protocol is working on like some level<00:35:25.480> of<00:35:26.160> First<00:35:26.839> Chain<00:35:27.160> abstraction 00:35:28.589 --> 00:35:28.599 align:start position:0% level of First Chain abstraction 00:35:28.599 --> 00:35:29.750 align:start position:0% level of First Chain abstraction um<00:35:28.839> I<00:35:28.920> mean<00:35:29.119> that's<00:35:29.280> something<00:35:29.520> that<00:35:29.599> we're 00:35:29.750 --> 00:35:29.760 align:start position:0% um I mean that's something that we're 00:35:29.760 --> 00:35:32.230 align:start position:0% um I mean that's something that we're looking<00:35:30.079> into<00:35:30.920> I<00:35:31.160> I<00:35:31.359> do<00:35:31.520> not<00:35:31.760> really<00:35:31.960> like<00:35:32.119> the 00:35:32.230 --> 00:35:32.240 align:start position:0% looking into I I do not really like the 00:35:32.240 --> 00:35:34.510 align:start position:0% looking into I I do not really like the term<00:35:32.520> chain<00:35:32.760> abstraction<00:35:33.400> itself<00:35:34.200> I<00:35:34.320> think 00:35:34.510 --> 00:35:34.520 align:start position:0% term chain abstraction itself I think 00:35:34.520 --> 00:35:37.349 align:start position:0% term chain abstraction itself I think it's<00:35:34.680> more<00:35:34.920> like<00:35:35.119> chain<00:35:36.040> agnosticism<00:35:37.040> um 00:35:37.349 --> 00:35:37.359 align:start position:0% it's more like chain agnosticism um 00:35:37.359 --> 00:35:39.270 align:start position:0% it's more like chain agnosticism um because<00:35:37.720> like<00:35:38.240> chain<00:35:38.560> abstraction<00:35:39.000> means 00:35:39.270 --> 00:35:39.280 align:start position:0% because like chain abstraction means 00:35:39.280 --> 00:35:40.910 align:start position:0% because like chain abstraction means that<00:35:39.440> the<00:35:39.520> end<00:35:39.720> user<00:35:39.960> doesn't<00:35:40.320> care<00:35:40.599> about<00:35:40.800> the 00:35:40.910 --> 00:35:40.920 align:start position:0% that the end user doesn't care about the 00:35:40.920 --> 00:35:43.829 align:start position:0% that the end user doesn't care about the chain<00:35:41.240> at<00:35:41.359> all<00:35:42.119> but<00:35:42.480> like<00:35:43.200> with<00:35:43.359> the<00:35:43.520> current 00:35:43.829 --> 00:35:43.839 align:start position:0% chain at all but like with the current 00:35:43.839 --> 00:35:45.630 align:start position:0% chain at all but like with the current state<00:35:44.000> of<00:35:44.119> crypto<00:35:44.480> that's<00:35:44.680> not<00:35:44.880> really<00:35:45.119> true 00:35:45.630 --> 00:35:45.640 align:start position:0% state of crypto that's not really true 00:35:45.640 --> 00:35:47.870 align:start position:0% state of crypto that's not really true users<00:35:46.160> do<00:35:46.599> usually<00:35:46.920> still<00:35:47.240> care<00:35:47.480> what<00:35:47.640> chain 00:35:47.870 --> 00:35:47.880 align:start position:0% users do usually still care what chain 00:35:47.880 --> 00:35:51.470 align:start position:0% users do usually still care what chain they're<00:35:48.040> on<00:35:48.760> for<00:35:49.319> either<00:35:50.079> tribal<00:35:50.720> reasons<00:35:51.280> for 00:35:51.470 --> 00:35:51.480 align:start position:0% they're on for either tribal reasons for 00:35:51.480 --> 00:35:53.910 align:start position:0% they're on for either tribal reasons for reasons<00:35:51.920> of<00:35:52.160> like<00:35:52.960> wanting<00:35:53.240> to<00:35:53.400> farm 00:35:53.910 --> 00:35:53.920 align:start position:0% reasons of like wanting to farm 00:35:53.920 --> 00:35:58.390 align:start position:0% reasons of like wanting to farm something<00:35:54.880> uh<00:35:55.359> for<00:35:55.680> security<00:35:56.119> reasons<00:35:57.079> um<00:35:57.280> so 00:35:58.390 --> 00:35:58.400 align:start position:0% something uh for security reasons um so 00:35:58.400 --> 00:36:02.470 align:start position:0% something uh for security reasons um so um<00:35:58.880> I<00:35:59.000> think<00:35:59.400> we<00:35:59.560> want<00:35:59.680> to<00:36:00.240> at<00:36:00.359> least<00:36:00.800> give<00:36:01.800> um 00:36:02.470 --> 00:36:02.480 align:start position:0% um I think we want to at least give um 00:36:02.480 --> 00:36:04.790 align:start position:0% um I think we want to at least give um users<00:36:02.960> and<00:36:03.119> that<00:36:03.280> also<00:36:03.480> means<00:36:04.119> companies<00:36:04.640> that 00:36:04.790 --> 00:36:04.800 align:start position:0% users and that also means companies that 00:36:04.800 --> 00:36:07.150 align:start position:0% users and that also means companies that work<00:36:05.040> with<00:36:05.200> us<00:36:05.760> the<00:36:05.920> ability<00:36:06.480> to<00:36:06.920> be 00:36:07.150 --> 00:36:07.160 align:start position:0% work with us the ability to be 00:36:07.160 --> 00:36:08.910 align:start position:0% work with us the ability to be opinionated<00:36:07.839> about<00:36:08.160> like<00:36:08.440> completely 00:36:08.910 --> 00:36:08.920 align:start position:0% opinionated about like completely 00:36:08.920 --> 00:36:10.630 align:start position:0% opinionated about like completely abstracting<00:36:09.440> this<00:36:09.599> away<00:36:09.839> or<00:36:10.000> just<00:36:10.200> partially 00:36:10.630 --> 00:36:10.640 align:start position:0% abstracting this away or just partially 00:36:10.640 --> 00:36:13.190 align:start position:0% abstracting this away or just partially abstracting<00:36:11.079> this<00:36:11.319> away<00:36:12.319> and<00:36:12.480> then<00:36:12.760> the<00:36:12.880> other 00:36:13.190 --> 00:36:13.200 align:start position:0% abstracting this away and then the other 00:36:13.200 --> 00:36:14.870 align:start position:0% abstracting this away and then the other thing<00:36:13.599> that<00:36:13.720> I<00:36:13.880> talked<00:36:14.160> about<00:36:14.359> earlier<00:36:14.760> a 00:36:14.870 --> 00:36:14.880 align:start position:0% thing that I talked about earlier a 00:36:14.880 --> 00:36:17.470 align:start position:0% thing that I talked about earlier a little<00:36:15.040> bit<00:36:15.280> was<00:36:15.480> like<00:36:16.240> going<00:36:16.560> into<00:36:17.079> virtual 00:36:17.470 --> 00:36:17.480 align:start position:0% little bit was like going into virtual 00:36:17.480 --> 00:36:19.630 align:start position:0% little bit was like going into virtual machine<00:36:17.920> abstraction<00:36:18.640> like<00:36:18.920> and<00:36:19.240> that<00:36:19.359> to<00:36:19.480> me 00:36:19.630 --> 00:36:19.640 align:start position:0% machine abstraction like and that to me 00:36:19.640 --> 00:36:22.589 align:start position:0% machine abstraction like and that to me is<00:36:19.800> like<00:36:19.920> the<00:36:20.040> end<00:36:20.319> game<00:36:20.599> actually<00:36:21.520> um<00:36:22.240> having 00:36:22.589 --> 00:36:22.599 align:start position:0% is like the end game actually um having 00:36:22.599 --> 00:36:26.750 align:start position:0% is like the end game actually um having a<00:36:22.839> unified<00:36:23.640> experience<00:36:24.640> of<00:36:25.119> accessing<00:36:26.119> all<00:36:26.480> of 00:36:26.750 --> 00:36:26.760 align:start position:0% a unified experience of accessing all of 00:36:26.760 --> 00:36:30.109 align:start position:0% a unified experience of accessing all of like<00:36:26.960> the<00:36:27.119> crypto<00:36:27.400> world<00:36:27.599> World<00:36:28.400> um<00:36:28.880> and<00:36:29.640> yeah 00:36:30.109 --> 00:36:30.119 align:start position:0% like the crypto world World um and yeah 00:36:30.119 --> 00:36:33.550 align:start position:0% like the crypto world World um and yeah as<00:36:30.280> stated<00:36:31.319> probably<00:36:32.319> some<00:36:32.640> kind<00:36:32.760> of<00:36:33.000> proving 00:36:33.550 --> 00:36:33.560 align:start position:0% as stated probably some kind of proving 00:36:33.560 --> 00:36:36.230 align:start position:0% as stated probably some kind of proving schemes<00:36:34.560> um<00:36:34.800> hopefully<00:36:35.160> ZK<00:36:35.560> proofs<00:36:35.880> becoming 00:36:36.230 --> 00:36:36.240 align:start position:0% schemes um hopefully ZK proofs becoming 00:36:36.240 --> 00:36:39.829 align:start position:0% schemes um hopefully ZK proofs becoming cheaper<00:36:37.000> is<00:36:37.200> going<00:36:37.319> to<00:36:37.560> play<00:36:37.920> a<00:36:38.079> huge<00:36:38.560> role<00:36:39.560> in 00:36:39.829 --> 00:36:39.839 align:start position:0% cheaper is going to play a huge role in 00:36:39.839 --> 00:36:42.950 align:start position:0% cheaper is going to play a huge role in this<00:36:40.720> and<00:36:41.200> I<00:36:41.319> think<00:36:41.640> in<00:36:41.880> like<00:36:42.079> the 00:36:42.950 --> 00:36:42.960 align:start position:0% this and I think in like the 00:36:42.960 --> 00:36:45.710 align:start position:0% this and I think in like the next<00:36:43.960> let's<00:36:44.119> say<00:36:44.280> 18<00:36:44.680> months<00:36:45.280> we're<00:36:45.440> going<00:36:45.560> to 00:36:45.710 --> 00:36:45.720 align:start position:0% next let's say 18 months we're going to 00:36:45.720 --> 00:36:48.190 align:start position:0% next let's say 18 months we're going to see<00:36:46.079> like<00:36:46.240> the<00:36:46.440> first<00:36:46.880> truly<00:36:47.440> unified 00:36:48.190 --> 00:36:48.200 align:start position:0% see like the first truly unified 00:36:48.200 --> 00:36:50.790 align:start position:0% see like the first truly unified accounts<00:36:49.200> like<00:36:49.440> you<00:36:49.560> know<00:36:49.839> people<00:36:50.400> use<00:36:50.680> the 00:36:50.790 --> 00:36:50.800 align:start position:0% accounts like you know people use the 00:36:50.800 --> 00:36:52.349 align:start position:0% accounts like you know people use the word<00:36:51.000> unified<00:36:51.400> account<00:36:51.800> right<00:36:51.920> now<00:36:52.119> but<00:36:52.240> it's 00:36:52.349 --> 00:36:52.359 align:start position:0% word unified account right now but it's 00:36:52.359 --> 00:36:55.430 align:start position:0% word unified account right now but it's really<00:36:52.560> just<00:36:52.720> an<00:36:52.839> evbm<00:36:53.319> balance<00:36:54.319> um<00:36:54.800> but<00:36:55.079> like 00:36:55.430 --> 00:36:55.440 align:start position:0% really just an evbm balance um but like 00:36:55.440 --> 00:36:59.030 align:start position:0% really just an evbm balance um but like unified<00:36:56.000> account<00:36:56.480> across<00:36:57.079> all<00:36:58.000> um<00:36:58.640> virtual 00:36:59.030 --> 00:36:59.040 align:start position:0% unified account across all um virtual 00:36:59.040 --> 00:37:00.349 align:start position:0% unified account across all um virtual machine 00:37:00.349 --> 00:37:00.359 align:start position:0% machine 00:37:00.359 --> 00:37:03.829 align:start position:0% machine environments<00:37:01.359> great<00:37:01.920> thank<00:37:02.160> you<00:37:03.119> I<00:37:03.240> think<00:37:03.480> I'm 00:37:03.829 --> 00:37:03.839 align:start position:0% environments great thank you I think I'm 00:37:03.839 --> 00:37:05.390 align:start position:0% environments great thank you I think I'm I'm<00:37:04.000> the<00:37:04.119> only<00:37:04.280> one<00:37:04.480> missing<00:37:04.760> to<00:37:05.079> give<00:37:05.240> some 00:37:05.390 --> 00:37:05.400 align:start position:0% I'm the only one missing to give some 00:37:05.400 --> 00:37:10.109 align:start position:0% I'm the only one missing to give some Alpa<00:37:06.119> uh<00:37:06.280> but<00:37:06.680> as<00:37:06.960> is<00:37:07.560> also<00:37:07.839> related<00:37:08.240> to<00:37:08.480> AI<00:37:09.359> so 00:37:10.109 --> 00:37:10.119 align:start position:0% Alpa uh but as is also related to AI so 00:37:10.119 --> 00:37:13.390 align:start position:0% Alpa uh but as is also related to AI so uh<00:37:10.400> AI<00:37:10.800> agents<00:37:11.240> are<00:37:11.599> plan<00:37:11.920> of<00:37:12.520> are<00:37:12.720> part<00:37:12.920> of<00:37:13.079> our 00:37:13.390 --> 00:37:13.400 align:start position:0% uh AI agents are plan of are part of our 00:37:13.400 --> 00:37:16.349 align:start position:0% uh AI agents are plan of are part of our of<00:37:13.560> our<00:37:13.760> road<00:37:14.079> map<00:37:14.800> uh<00:37:14.960> think<00:37:15.160> of<00:37:15.319> an<00:37:15.520> AI<00:37:15.920> agent 00:37:16.349 --> 00:37:16.359 align:start position:0% of our road map uh think of an AI agent 00:37:16.359 --> 00:37:19.710 align:start position:0% of our road map uh think of an AI agent as<00:37:17.040> uh<00:37:17.200> an<00:37:17.400> entity<00:37:17.839> that<00:37:17.960> can<00:37:18.200> execute<00:37:18.760> complex 00:37:19.710 --> 00:37:19.720 align:start position:0% as uh an entity that can execute complex 00:37:19.720 --> 00:37:23.430 align:start position:0% as uh an entity that can execute complex uh<00:37:19.960> strategies<00:37:20.960> uh<00:37:21.160> in<00:37:21.599> in<00:37:22.079> favor<00:37:22.480> of<00:37:22.640> the<00:37:22.800> user 00:37:23.430 --> 00:37:23.440 align:start position:0% uh strategies uh in in favor of the user 00:37:23.440 --> 00:37:27.069 align:start position:0% uh strategies uh in in favor of the user so<00:37:23.720> imagine<00:37:24.720> uh<00:37:24.880> DCA<00:37:25.760> on<00:37:26.040> on<00:37:26.240> a<00:37:26.440> on<00:37:26.560> a<00:37:26.720> certain 00:37:27.069 --> 00:37:27.079 align:start position:0% so imagine uh DCA on on a on a certain 00:37:27.079 --> 00:37:30.190 align:start position:0% so imagine uh DCA on on a on a certain tokens<00:37:27.520> so<00:37:27.680> be<00:37:27.880> able<00:37:28.119> to<00:37:28.839> buy<00:37:29.119> in<00:37:29.560> at<00:37:29.800> certain 00:37:30.190 --> 00:37:30.200 align:start position:0% tokens so be able to buy in at certain 00:37:30.200 --> 00:37:32.870 align:start position:0% tokens so be able to buy in at certain points<00:37:30.520> of<00:37:30.760> time<00:37:31.359> and<00:37:31.560> doing<00:37:31.920> this<00:37:32.119> leveraging 00:37:32.870 --> 00:37:32.880 align:start position:0% points of time and doing this leveraging 00:37:32.880 --> 00:37:34.950 align:start position:0% points of time and doing this leveraging the<00:37:33.079> security<00:37:33.560> and<00:37:33.680> the<00:37:33.800> decentralization<00:37:34.520> of 00:37:34.950 --> 00:37:34.960 align:start position:0% the security and the decentralization of 00:37:34.960 --> 00:37:38.470 align:start position:0% the security and the decentralization of intents<00:37:35.960> um<00:37:36.560> so<00:37:36.760> we<00:37:36.880> are<00:37:37.040> also<00:37:37.440> going<00:37:37.760> into<00:37:38.119> a 00:37:38.470 --> 00:37:38.480 align:start position:0% intents um so we are also going into a 00:37:38.480 --> 00:37:41.589 align:start position:0% intents um so we are also going into a AI<00:37:39.200> through<00:37:39.599> through 00:37:41.589 --> 00:37:41.599 align:start position:0% AI through through 00:37:41.599 --> 00:37:45.150 align:start position:0% AI through through intents<00:37:42.599> so<00:37:43.599> I<00:37:43.680> think<00:37:43.800> we<00:37:43.960> have<00:37:44.079> a<00:37:44.400> little<00:37:44.720> gift 00:37:45.150 --> 00:37:45.160 align:start position:0% intents so I think we have a little gift 00:37:45.160 --> 00:37:48.630 align:start position:0% intents so I think we have a little gift for<00:37:45.359> you<00:37:46.160> uh<00:37:46.359> we<00:37:46.560> prepared<00:37:47.160> the<00:37:47.720> poop<00:37:48.200> for<00:37:48.440> the 00:37:48.630 --> 00:37:48.640 align:start position:0% for you uh we prepared the poop for the 00:37:48.640 --> 00:37:50.950 align:start position:0% for you uh we prepared the poop for the talk<00:37:49.319> uh<00:37:49.440> I<00:37:49.599> hope<00:37:49.920> there<00:37:50.040> are<00:37:50.240> some<00:37:50.599> poop 00:37:50.950 --> 00:37:50.960 align:start position:0% talk uh I hope there are some poop 00:37:50.960 --> 00:37:52.030 align:start position:0% talk uh I hope there are some poop lovers 00:37:52.030 --> 00:37:52.040 align:start position:0% lovers 00:37:52.040 --> 00:37:53.550 align:start position:0% lovers here 00:37:53.550 --> 00:37:53.560 align:start position:0% here 00:37:53.560 --> 00:37:58.030 align:start position:0% here so<00:37:54.839> uh<00:37:55.839> you<00:37:56.000> should<00:37:56.560> you<00:37:56.839> if<00:37:56.960> you<00:37:57.079> have<00:37:57.280> the<00:37:57.680> po 00:37:58.030 --> 00:37:58.040 align:start position:0% so uh you should you if you have the po 00:37:58.040 --> 00:38:01.230 align:start position:0% so uh you should you if you have the po app<00:37:58.240> I<00:37:58.319> think<00:37:58.520> you<00:37:58.800> can<00:37:59.079> scan<00:37:59.640> this<00:37:59.960> QR<00:38:00.960> uh<00:38:01.079> to 00:38:01.230 --> 00:38:01.240 align:start position:0% app I think you can scan this QR uh to 00:38:01.240 --> 00:38:04.150 align:start position:0% app I think you can scan this QR uh to get<00:38:01.400> a<00:38:01.680> memory<00:38:02.280> of<00:38:02.720> uh<00:38:03.079> this<00:38:03.480> panel<00:38:03.839> that<00:38:03.960> you 00:38:04.150 --> 00:38:04.160 align:start position:0% get a memory of uh this panel that you 00:38:04.160 --> 00:38:07.950 align:start position:0% get a memory of uh this panel that you just<00:38:04.400> attended<00:38:05.319> so<00:38:06.319> uh<00:38:06.520> besides<00:38:07.160> thanking<00:38:07.560> you 00:38:07.950 --> 00:38:07.960 align:start position:0% just attended so uh besides thanking you 00:38:07.960 --> 00:38:10.109 align:start position:0% just attended so uh besides thanking you for<00:38:08.400> attending<00:38:08.920> this<00:38:09.280> uh<00:38:09.400> panel<00:38:09.720> I<00:38:09.800> want<00:38:09.960> to 00:38:10.109 --> 00:38:10.119 align:start position:0% for attending this uh panel I want to 00:38:10.119 --> 00:38:12.349 align:start position:0% for attending this uh panel I want to also<00:38:10.599> thank<00:38:10.839> you<00:38:11.599> uh<00:38:11.720> the<00:38:11.880> three<00:38:12.040> of<00:38:12.160> you 00:38:12.349 --> 00:38:12.359 align:start position:0% also thank you uh the three of you 00:38:12.359 --> 00:38:15.309 align:start position:0% also thank you uh the three of you because<00:38:12.560> it<00:38:12.720> was<00:38:12.920> a<00:38:13.160> a<00:38:13.319> very<00:38:13.680> very<00:38:14.000> good<00:38:14.319> talk 00:38:15.309 --> 00:38:15.319 align:start position:0% because it was a a very very good talk 00:38:15.319 --> 00:38:17.309 align:start position:0% because it was a a very very good talk uh<00:38:15.480> and<00:38:15.680> now<00:38:16.119> maybe<00:38:16.400> we<00:38:16.520> can<00:38:16.760> have<00:38:17.040> some 00:38:17.309 --> 00:38:17.319 align:start position:0% uh and now maybe we can have some 00:38:17.319 --> 00:38:44.710 align:start position:0% uh and now maybe we can have some questions<00:38:17.760> if<00:38:17.960> there<00:38:18.040> are<00:38:18.280> some 00:38:44.710 --> 00:38:44.720 align:start position:0% 00:38:44.720 --> 00:38:48.550 align:start position:0% hello<00:38:45.640> yeah<00:38:46.240> uh<00:38:46.760> my<00:38:46.920> name<00:38:47.079> is<00:38:47.280> Jason<00:38:47.800> and<00:38:48.200> uh 00:38:48.550 --> 00:38:48.560 align:start position:0% hello yeah uh my name is Jason and uh 00:38:48.560 --> 00:38:51.510 align:start position:0% hello yeah uh my name is Jason and uh and<00:38:48.760> the<00:38:48.960> topic<00:38:49.280> about<00:38:49.480> the<00:38:49.680> int<00:38:50.680> Trad<00:38:51.079> is<00:38:51.240> very 00:38:51.510 --> 00:38:51.520 align:start position:0% and the topic about the int Trad is very 00:38:51.520 --> 00:38:55.710 align:start position:0% and the topic about the int Trad is very interesting<00:38:52.440> uh<00:38:53.440> uh<00:38:53.720> so<00:38:54.280> uh<00:38:54.720> I'm<00:38:55.079> I'm<00:38:55.240> very<00:38:55.440> new 00:38:55.710 --> 00:38:55.720 align:start position:0% interesting uh uh so uh I'm I'm very new 00:38:55.720 --> 00:38:57.550 align:start position:0% interesting uh uh so uh I'm I'm very new here<00:38:55.960> and<00:38:56.160> I<00:38:56.359> just<00:38:56.560> have<00:38:56.760> one<00:38:56.960> question<00:38:57.240> is<00:38:57.440> is 00:38:57.550 --> 00:38:57.560 align:start position:0% here and I just have one question is is 00:38:57.560 --> 00:39:01.309 align:start position:0% here and I just have one question is is that<00:38:58.160> uh<00:38:59.160> uh<00:38:59.480> why<00:38:59.760> you<00:39:00.319> uh<00:39:00.520> when<00:39:00.680> you<00:39:00.839> do<00:39:01.160> kind 00:39:01.309 --> 00:39:01.319 align:start position:0% that uh uh why you uh when you do kind 00:39:01.319 --> 00:39:04.109 align:start position:0% that uh uh why you uh when you do kind of<00:39:01.599> uh<00:39:01.720> intend<00:39:02.280> trading<00:39:03.280> uh<00:39:03.480> does<00:39:03.680> it<00:39:03.839> mean 00:39:04.109 --> 00:39:04.119 align:start position:0% of uh intend trading uh does it mean 00:39:04.119 --> 00:39:10.270 align:start position:0% of uh intend trading uh does it mean that<00:39:04.319> you<00:39:04.599> shift<00:39:05.319> the<00:39:06.319> uh<00:39:06.440> you<00:39:06.560> know<00:39:07.800> um<00:39:08.800> on<00:39:09.280> the 00:39:10.270 --> 00:39:10.280 align:start position:0% that you shift the uh you know um on the 00:39:10.280 --> 00:39:15.030 align:start position:0% that you shift the uh you know um on the uh<00:39:10.680> on<00:39:11.000> the<00:39:11.359> kind<00:39:11.560> of<00:39:11.920> uh<00:39:12.079> risk<00:39:12.400> of<00:39:13.400> uh<00:39:14.400> uh 00:39:15.030 --> 00:39:15.040 align:start position:0% uh on the kind of uh risk of uh uh 00:39:15.040 --> 00:39:18.309 align:start position:0% uh on the kind of uh risk of uh uh centralization<00:39:15.960> to<00:39:16.160> the<00:39:16.319> backend<00:39:16.839> system<00:39:17.839> and 00:39:18.309 --> 00:39:18.319 align:start position:0% centralization to the backend system and 00:39:18.319 --> 00:39:21.190 align:start position:0% centralization to the backend system and uh<00:39:18.599> and<00:39:18.839> as<00:39:19.359> as<00:39:19.480> I<00:39:19.599> know<00:39:20.079> uh<00:39:20.200> using<00:39:20.520> backend<00:39:21.000> is 00:39:21.190 --> 00:39:21.200 align:start position:0% uh and as as I know uh using backend is 00:39:21.200 --> 00:39:25.630 align:start position:0% uh and as as I know uh using backend is quite<00:39:21.760> uh<00:39:22.359> you<00:39:22.520> know<00:39:23.119> very<00:39:23.640> um<00:39:24.560> uh<00:39:24.839> using<00:39:25.240> backp 00:39:25.630 --> 00:39:25.640 align:start position:0% quite uh you know very um uh using backp 00:39:25.640 --> 00:39:27.990 align:start position:0% quite uh you know very um uh using backp and<00:39:25.800> in<00:39:25.920> the<00:39:26.040> system<00:39:27.000> would<00:39:27.200> bring<00:39:27.520> the<00:39:27.640> best 00:39:27.990 --> 00:39:28.000 align:start position:0% and in the system would bring the best 00:39:28.000 --> 00:39:31.430 align:start position:0% and in the system would bring the best uh<00:39:28.119> user<00:39:28.760> experience<00:39:29.760> uh<00:39:29.880> in<00:39:30.040> trading<00:39:31.040> but<00:39:31.280> it 00:39:31.430 --> 00:39:31.440 align:start position:0% uh user experience uh in trading but it 00:39:31.440 --> 00:39:34.069 align:start position:0% uh user experience uh in trading but it will<00:39:32.319> bring<00:39:32.599> some<00:39:32.839> downside<00:39:33.480> and<00:39:33.599> I<00:39:33.760> just<00:39:33.880> want 00:39:34.069 --> 00:39:34.079 align:start position:0% will bring some downside and I just want 00:39:34.079 --> 00:39:36.309 align:start position:0% will bring some downside and I just want to<00:39:34.240> hear<00:39:34.440> more<00:39:34.599> about<00:39:34.760> it<00:39:34.960> because<00:39:35.480> uh<00:39:36.079> it's 00:39:36.309 --> 00:39:36.319 align:start position:0% to hear more about it because uh it's 00:39:36.319 --> 00:39:41.030 align:start position:0% to hear more about it because uh it's very<00:39:36.560> important<00:39:36.960> to<00:39:37.200> us<00:39:37.359> to<00:39:37.560> improve<00:39:37.920> our<00:39:38.359> user 00:39:41.030 --> 00:39:41.040 align:start position:0% 00:39:41.040 --> 00:39:50.430 align:start position:0% experience<00:39:42.040> you<00:39:42.680> do<00:39:42.800> you<00:39:42.960> get<00:39:43.119> my 00:39:50.430 --> 00:39:50.440 align:start position:0% 00:39:50.440 --> 00:39:53.950 align:start position:0% question<00:39:51.440> um<00:39:52.240> if<00:39:52.359> I<00:39:52.520> got<00:39:52.720> it<00:39:52.920> correctly<00:39:53.520> it's 00:39:53.950 --> 00:39:53.960 align:start position:0% question um if I got it correctly it's 00:39:53.960 --> 00:39:57.910 align:start position:0% question um if I got it correctly it's uh<00:39:54.480> it's<00:39:54.720> about<00:39:55.560> you're<00:39:55.800> asking<00:39:56.119> if<00:39:56.280> we<00:39:56.400> are<00:39:57.160> uh 00:39:57.910 --> 00:39:57.920 align:start position:0% uh it's about you're asking if we are uh 00:39:57.920 --> 00:39:59.829 align:start position:0% uh it's about you're asking if we are uh leaving<00:39:58.359> the<00:39:58.560> centralization<00:39:59.319> for<00:39:59.520> the<00:39:59.680> back 00:39:59.829 --> 00:39:59.839 align:start position:0% leaving the centralization for the back 00:39:59.839 --> 00:40:02.430 align:start position:0% leaving the centralization for the back end<00:40:00.800> is<00:40:00.960> that<00:40:01.240> is<00:40:01.400> that<00:40:01.680> the<00:40:02.000> is<00:40:02.119> that<00:40:02.319> the 00:40:02.430 --> 00:40:02.440 align:start position:0% end is that is that the is that the 00:40:02.440 --> 00:40:05.710 align:start position:0% end is that is that the is that the question<00:40:03.040> yeah<00:40:03.160> that's<00:40:03.359> my<00:40:03.520> question<00:40:04.720> okay 00:40:05.710 --> 00:40:05.720 align:start position:0% question yeah that's my question okay 00:40:05.720 --> 00:40:06.990 align:start position:0% question yeah that's my question okay yeah<00:40:05.839> I<00:40:05.920> think<00:40:06.040> it<00:40:06.200> depends<00:40:06.560> what<00:40:06.680> you<00:40:06.760> mean 00:40:06.990 --> 00:40:07.000 align:start position:0% yeah I think it depends what you mean 00:40:07.000 --> 00:40:09.829 align:start position:0% yeah I think it depends what you mean here<00:40:07.240> I<00:40:07.319> think<00:40:07.560> like<00:40:07.800> obviously<00:40:08.440> like<00:40:08.880> every 00:40:09.829 --> 00:40:09.839 align:start position:0% here I think like obviously like every 00:40:09.839 --> 00:40:11.550 align:start position:0% here I think like obviously like every every<00:40:10.079> intense<00:40:10.560> system<00:40:10.960> is<00:40:11.160> at<00:40:11.240> the<00:40:11.319> end<00:40:11.480> of 00:40:11.550 --> 00:40:11.560 align:start position:0% every intense system is at the end of 00:40:11.560 --> 00:40:13.150 align:start position:0% every intense system is at the end of the<00:40:11.680> day<00:40:11.800> an<00:40:11.920> aggregation<00:40:12.520> system<00:40:12.839> and<00:40:13.000> every 00:40:13.150 --> 00:40:13.160 align:start position:0% the day an aggregation system and every 00:40:13.160 --> 00:40:15.309 align:start position:0% the day an aggregation system and every aggregation<00:40:13.760> system<00:40:14.119> obviously<00:40:14.520> strives<00:40:15.079> to 00:40:15.309 --> 00:40:15.319 align:start position:0% aggregation system obviously strives to 00:40:15.319 --> 00:40:19.790 align:start position:0% aggregation system obviously strives to be<00:40:16.079> the<00:40:16.319> sole<00:40:16.800> owner<00:40:17.520> of<00:40:18.119> orderflow<00:40:19.119> um<00:40:19.440> so 00:40:19.790 --> 00:40:19.800 align:start position:0% be the sole owner of orderflow um so 00:40:19.800 --> 00:40:22.550 align:start position:0% be the sole owner of orderflow um so like<00:40:20.800> if<00:40:20.960> you<00:40:21.280> imagine<00:40:21.720> there<00:40:21.839> to<00:40:22.040> be<00:40:22.240> one<00:40:22.400> of 00:40:22.550 --> 00:40:22.560 align:start position:0% like if you imagine there to be one of 00:40:22.560 --> 00:40:24.950 align:start position:0% like if you imagine there to be one of those<00:40:22.760> systems<00:40:23.240> that<00:40:23.440> would<00:40:23.720> be<00:40:24.480> better<00:40:24.800> than 00:40:24.950 --> 00:40:24.960 align:start position:0% those systems that would be better than 00:40:24.960 --> 00:40:27.069 align:start position:0% those systems that would be better than all<00:40:25.119> the<00:40:25.240> other<00:40:25.440> ones<00:40:25.680> and<00:40:25.800> obviously<00:40:26.800> if<00:40:26.920> you 00:40:27.069 --> 00:40:27.079 align:start position:0% all the other ones and obviously if you 00:40:27.079 --> 00:40:28.630 align:start position:0% all the other ones and obviously if you talk<00:40:27.319> talking<00:40:27.480> from<00:40:27.599> a<00:40:27.680> solver<00:40:28.040> perspective 00:40:28.630 --> 00:40:28.640 align:start position:0% talk talking from a solver perspective 00:40:28.640 --> 00:40:30.150 align:start position:0% talk talking from a solver perspective some<00:40:28.800> of<00:40:28.920> these<00:40:29.079> systems<00:40:29.440> are<00:40:29.560> going<00:40:29.680> to<00:40:29.880> have 00:40:30.150 --> 00:40:30.160 align:start position:0% some of these systems are going to have 00:40:30.160 --> 00:40:34.309 align:start position:0% some of these systems are going to have more<00:40:30.400> Network<00:40:30.880> effects<00:40:31.240> than<00:40:31.480> others<00:40:32.480> um<00:40:33.359> then 00:40:34.309 --> 00:40:34.319 align:start position:0% more Network effects than others um then 00:40:34.319 --> 00:40:37.470 align:start position:0% more Network effects than others um then yes<00:40:34.760> there<00:40:34.960> is<00:40:35.800> definitely<00:40:36.800> like<00:40:37.040> some<00:40:37.319> kind 00:40:37.470 --> 00:40:37.480 align:start position:0% yes there is definitely like some kind 00:40:37.480 --> 00:40:40.589 align:start position:0% yes there is definitely like some kind of<00:40:38.160> centralization<00:40:39.079> risk<00:40:39.560> that<00:40:39.839> like<00:40:40.480> a 00:40:40.589 --> 00:40:40.599 align:start position:0% of centralization risk that like a 00:40:40.599 --> 00:40:43.870 align:start position:0% of centralization risk that like a winner<00:40:41.119> might<00:40:41.400> take<00:40:42.319> this<00:40:42.520> entire<00:40:42.920> Market<00:40:43.720> but 00:40:43.870 --> 00:40:43.880 align:start position:0% winner might take this entire Market but 00:40:43.880 --> 00:40:45.950 align:start position:0% winner might take this entire Market but the<00:40:44.040> thing<00:40:44.240> is<00:40:44.480> like<00:40:44.760> as<00:40:44.920> we<00:40:45.040> said<00:40:45.640> this<00:40:45.800> back 00:40:45.950 --> 00:40:45.960 align:start position:0% the thing is like as we said this back 00:40:45.960 --> 00:40:48.430 align:start position:0% the thing is like as we said this back end<00:40:46.240> will<00:40:46.480> probably<00:40:47.040> be<00:40:47.280> some<00:40:47.520> type<00:40:47.680> of<00:40:47.880> chain 00:40:48.430 --> 00:40:48.440 align:start position:0% end will probably be some type of chain 00:40:48.440 --> 00:40:51.790 align:start position:0% end will probably be some type of chain with<00:40:48.680> some<00:40:48.920> type<00:40:49.079> of<00:40:49.280> consensus<00:40:49.960> mechanism<00:40:50.960> um 00:40:51.790 --> 00:40:51.800 align:start position:0% with some type of consensus mechanism um 00:40:51.800 --> 00:40:54.109 align:start position:0% with some type of consensus mechanism um so<00:40:52.599> if<00:40:52.720> you<00:40:53.000> look<00:40:53.160> at<00:40:53.280> it<00:40:53.400> from<00:40:53.640> that 00:40:54.109 --> 00:40:54.119 align:start position:0% so if you look at it from that 00:40:54.119 --> 00:40:57.750 align:start position:0% so if you look at it from that perspective<00:40:55.119> um<00:40:55.480> it's<00:40:55.640> more<00:40:55.920> of<00:40:56.160> an<00:40:56.800> uh 00:40:57.750 --> 00:40:57.760 align:start position:0% perspective um it's more of an uh 00:40:57.760 --> 00:41:00.670 align:start position:0% perspective um it's more of an uh it's<00:40:57.920> more<00:40:58.119> of<00:40:58.880> it's<00:40:59.040> more<00:40:59.200> of<00:40:59.440> a<00:41:00.040> a 00:41:00.670 --> 00:41:00.680 align:start position:0% it's more of it's more of a a 00:41:00.680 --> 00:41:03.630 align:start position:0% it's more of it's more of a a competitive<00:41:01.680> system<00:41:02.480> but<00:41:02.720> yes<00:41:03.200> in<00:41:03.280> terms<00:41:03.520> of 00:41:03.630 --> 00:41:03.640 align:start position:0% competitive system but yes in terms of 00:41:03.640 --> 00:41:05.829 align:start position:0% competitive system but yes in terms of an<00:41:03.839> API<00:41:04.480> you<00:41:04.560> would<00:41:04.839> access<00:41:05.359> probably<00:41:05.680> a 00:41:05.829 --> 00:41:05.839 align:start position:0% an API you would access probably a 00:41:05.839 --> 00:41:09.470 align:start position:0% an API you would access probably a simple<00:41:06.640> a<00:41:06.760> single<00:41:07.160> API<00:41:07.720> to<00:41:08.720> um<00:41:08.920> get<00:41:09.160> quotes 00:41:09.470 --> 00:41:09.480 align:start position:0% simple a single API to um get quotes 00:41:09.480 --> 00:41:11.430 align:start position:0% simple a single API to um get quotes from<00:41:09.680> the 00:41:11.430 --> 00:41:11.440 align:start position:0% from the 00:41:11.440 --> 00:41:14.829 align:start position:0% from the system<00:41:12.440> uh<00:41:12.920> if<00:41:13.040> I<00:41:13.280> may<00:41:13.520> add<00:41:13.880> there<00:41:14.240> I<00:41:14.400> think 00:41:14.829 --> 00:41:14.839 align:start position:0% system uh if I may add there I think 00:41:14.839 --> 00:41:16.670 align:start position:0% system uh if I may add there I think that 00:41:16.670 --> 00:41:16.680 align:start position:0% that 00:41:16.680 --> 00:41:19.710 align:start position:0% that uh<00:41:17.680> there<00:41:17.920> will<00:41:18.200> be<00:41:18.720> improvements<00:41:19.359> on<00:41:19.560> the 00:41:19.710 --> 00:41:19.720 align:start position:0% uh there will be improvements on the 00:41:19.720 --> 00:41:22.309 align:start position:0% uh there will be improvements on the decentralization<00:41:20.599> of<00:41:20.760> the<00:41:20.920> intents<00:41:21.520> existing 00:41:22.309 --> 00:41:22.319 align:start position:0% decentralization of the intents existing 00:41:22.319 --> 00:41:26.030 align:start position:0% decentralization of the intents existing systems<00:41:23.319> uh<00:41:23.800> I<00:41:23.920> think<00:41:24.200> that<00:41:24.520> today<00:41:25.520> uh<00:41:25.640> it's 00:41:26.030 --> 00:41:26.040 align:start position:0% systems uh I think that today uh it's 00:41:26.040 --> 00:41:27.829 align:start position:0% systems uh I think that today uh it's difficult<00:41:26.200> to<00:41:26.359> fully<00:41:26.720> decentralize 00:41:27.829 --> 00:41:27.839 align:start position:0% difficult to fully decentralize 00:41:27.839 --> 00:41:29.630 align:start position:0% difficult to fully decentralize an<00:41:28.040> intense<00:41:28.440> system<00:41:28.800> mainly<00:41:29.160> because<00:41:29.400> of<00:41:29.520> the 00:41:29.630 --> 00:41:29.640 align:start position:0% an intense system mainly because of the 00:41:29.640 --> 00:41:32.309 align:start position:0% an intense system mainly because of the risk<00:41:29.920> that<00:41:30.079> we<00:41:30.240> describ<00:41:31.000> here<00:41:31.319> that<00:41:32.040> uh<00:41:32.160> you 00:41:32.309 --> 00:41:32.319 align:start position:0% risk that we describ here that uh you 00:41:32.319 --> 00:41:34.710 align:start position:0% risk that we describ here that uh you cannot<00:41:32.680> ensure<00:41:33.200> that<00:41:33.400> suddenly<00:41:34.160> from<00:41:34.359> one<00:41:34.599> day 00:41:34.710 --> 00:41:34.720 align:start position:0% cannot ensure that suddenly from one day 00:41:34.720 --> 00:41:36.790 align:start position:0% cannot ensure that suddenly from one day to<00:41:34.880> the<00:41:35.000> other<00:41:35.280> you<00:41:35.440> have<00:41:35.560> a<00:41:35.720> thousand<00:41:36.040> solvers 00:41:36.790 --> 00:41:36.800 align:start position:0% to the other you have a thousand solvers 00:41:36.800 --> 00:41:38.870 align:start position:0% to the other you have a thousand solvers doing<00:41:37.160> whatever<00:41:37.480> they<00:41:37.640> want<00:41:37.920> on<00:41:38.079> the<00:41:38.359> on<00:41:38.520> the 00:41:38.870 --> 00:41:38.880 align:start position:0% doing whatever they want on the on the 00:41:38.880 --> 00:41:41.309 align:start position:0% doing whatever they want on the on the system<00:41:39.880> um<00:41:40.280> but<00:41:40.400> I<00:41:40.480> think<00:41:40.640> it's<00:41:40.800> going<00:41:41.000> to<00:41:41.119> be 00:41:41.309 --> 00:41:41.319 align:start position:0% system um but I think it's going to be 00:41:41.319 --> 00:41:43.990 align:start position:0% system um but I think it's going to be Progressive<00:41:42.119> So<00:41:42.440> today<00:41:42.760> we're<00:41:43.000> here<00:41:43.280> on<00:41:43.400> the 00:41:43.990 --> 00:41:44.000 align:start position:0% Progressive So today we're here on the 00:41:44.000 --> 00:41:46.470 align:start position:0% Progressive So today we're here on the decentralization<00:41:45.000> uh<00:41:45.400> the<00:41:45.920> the<00:41:46.079> intent 00:41:46.470 --> 00:41:46.480 align:start position:0% decentralization uh the the intent 00:41:46.480 --> 00:41:49.990 align:start position:0% decentralization uh the the intent system<00:41:46.800> are<00:41:47.160> going<00:41:47.400> to<00:41:47.960> slowly<00:41:48.599> start<00:41:49.599> uh<00:41:49.800> to 00:41:49.990 --> 00:41:50.000 align:start position:0% system are going to slowly start uh to 00:41:50.000 --> 00:41:51.829 align:start position:0% system are going to slowly start uh to decentralize<00:41:50.680> the<00:41:50.800> different<00:41:51.119> parts<00:41:51.440> of<00:41:51.640> the 00:41:51.829 --> 00:41:51.839 align:start position:0% decentralize the different parts of the 00:41:51.839 --> 00:41:53.990 align:start position:0% decentralize the different parts of the of<00:41:51.960> the<00:41:52.079> back<00:41:52.240> end<00:41:52.839> until<00:41:53.119> we<00:41:53.319> have<00:41:53.599> until<00:41:53.839> we 00:41:53.990 --> 00:41:54.000 align:start position:0% of the back end until we have until we 00:41:54.000 --> 00:41:56.150 align:start position:0% of the back end until we have until we find<00:41:54.200> a<00:41:54.400> solution<00:41:54.760> that<00:41:54.880> it's<00:41:55.079> a<00:41:55.560> completely 00:41:56.150 --> 00:41:56.160 align:start position:0% find a solution that it's a completely 00:41:56.160 --> 00:41:58.430 align:start position:0% find a solution that it's a completely or<00:41:56.440> almost<00:41:56.839> completely<00:41:57.240> Ely<00:41:57.480> decentralized<00:41:58.319> I 00:41:58.430 --> 00:41:58.440 align:start position:0% or almost completely Ely decentralized I 00:41:58.440 --> 00:41:59.710 align:start position:0% or almost completely Ely decentralized I highly<00:41:58.760> doubt<00:41:59.000> that<00:41:59.119> at<00:41:59.240> some<00:41:59.400> point<00:41:59.599> you 00:41:59.710 --> 00:41:59.720 align:start position:0% highly doubt that at some point you 00:41:59.720 --> 00:42:01.910 align:start position:0% highly doubt that at some point you won't<00:42:00.000> have<00:42:00.200> any<00:42:00.640> API<00:42:01.119> to<00:42:01.319> access<00:42:01.599> that<00:42:01.760> it's 00:42:01.910 --> 00:42:01.920 align:start position:0% won't have any API to access that it's 00:42:01.920 --> 00:42:04.510 align:start position:0% won't have any API to access that it's not<00:42:02.160> centralized<00:42:02.760> but<00:42:03.640> I<00:42:03.720> don't<00:42:03.839> know<00:42:04.079> maybe 00:42:04.510 --> 00:42:04.520 align:start position:0% not centralized but I don't know maybe 00:42:04.520 --> 00:42:07.829 align:start position:0% not centralized but I don't know maybe maybe<00:42:05.240> uh<00:42:05.400> I'm<00:42:06.079> wrong<00:42:07.079> thank<00:42:07.240> you<00:42:07.400> for<00:42:07.599> the 00:42:07.829 --> 00:42:07.839 align:start position:0% maybe uh I'm wrong thank you for the 00:42:07.839 --> 00:42:10.390 align:start position:0% maybe uh I'm wrong thank you for the question<00:42:08.839> so<00:42:09.359> we<00:42:09.480> have<00:42:09.640> two<00:42:09.800> more<00:42:10.000> questions 00:42:10.390 --> 00:42:10.400 align:start position:0% question so we have two more questions 00:42:10.400 --> 00:42:12.510 align:start position:0% question so we have two more questions here<00:42:10.599> so<00:42:10.920> the<00:42:11.160> next<00:42:11.400> question<00:42:11.599> is<00:42:11.720> are<00:42:11.960> intents 00:42:12.510 --> 00:42:12.520 align:start position:0% here so the next question is are intents 00:42:12.520 --> 00:42:14.630 align:start position:0% here so the next question is are intents the<00:42:12.880> future<00:42:13.319> of<00:42:13.440> all<00:42:13.640> of<00:42:13.760> defi<00:42:14.160> or<00:42:14.319> are<00:42:14.480> there 00:42:14.630 --> 00:42:14.640 align:start position:0% the future of all of defi or are there 00:42:14.640 --> 00:42:16.550 align:start position:0% the future of all of defi or are there use<00:42:14.920> cases<00:42:15.240> where<00:42:15.680> smart<00:42:16.000> contracts<00:42:16.400> are 00:42:16.550 --> 00:42:16.560 align:start position:0% use cases where smart contracts are 00:42:16.560 --> 00:42:18.190 align:start position:0% use cases where smart contracts are still 00:42:18.190 --> 00:42:18.200 align:start position:0% still 00:42:18.200 --> 00:42:25.470 align:start position:0% still useful<00:42:19.200> any<00:42:19.359> of<00:42:19.480> you<00:42:19.640> can<00:42:19.800> take 00:42:25.470 --> 00:42:25.480 align:start position:0% 00:42:25.480 --> 00:42:29.829 align:start position:0% it<00:42:26.480> uh<00:42:26.680> I<00:42:26.760> think<00:42:27.200> I<00:42:27.319> think<00:42:28.240> both<00:42:28.559> can<00:42:28.839> coexist 00:42:29.829 --> 00:42:29.839 align:start position:0% it uh I think I think both can coexist 00:42:29.839 --> 00:42:33.270 align:start position:0% it uh I think I think both can coexist uh<00:42:30.079> both<00:42:30.319> use<00:42:30.640> cases<00:42:31.280> might<00:42:31.520> be<00:42:32.119> uh<00:42:32.280> able<00:42:32.559> to 00:42:33.270 --> 00:42:33.280 align:start position:0% uh both use cases might be uh able to 00:42:33.280 --> 00:42:36.870 align:start position:0% uh both use cases might be uh able to coexist<00:42:34.280> um<00:42:34.599> there<00:42:34.800> are<00:42:35.000> today<00:42:35.520> some<00:42:36.200> use 00:42:36.870 --> 00:42:36.880 align:start position:0% coexist um there are today some use 00:42:36.880 --> 00:42:40.349 align:start position:0% coexist um there are today some use cases<00:42:37.880> um<00:42:38.280> I<00:42:38.359> don't<00:42:38.520> know<00:42:39.319> flash<00:42:39.720> loans<00:42:40.160> for 00:42:40.349 --> 00:42:40.359 align:start position:0% cases um I don't know flash loans for 00:42:40.359 --> 00:42:43.750 align:start position:0% cases um I don't know flash loans for example<00:42:40.839> that<00:42:41.040> might<00:42:41.319> not<00:42:41.680> be<00:42:42.160> might<00:42:42.319> not<00:42:42.520> be<00:42:42.760> a 00:42:43.750 --> 00:42:43.760 align:start position:0% example that might not be might not be a 00:42:43.760 --> 00:42:46.910 align:start position:0% example that might not be might not be a good<00:42:44.400> fit<00:42:44.760> for<00:42:45.040> intents<00:42:45.559> or<00:42:45.800> how<00:42:46.000> the<00:42:46.160> intents 00:42:46.910 --> 00:42:46.920 align:start position:0% good fit for intents or how the intents 00:42:46.920 --> 00:42:49.309 align:start position:0% good fit for intents or how the intents uh<00:42:47.160> systems<00:42:47.520> are<00:42:47.720> working<00:42:48.079> today<00:42:48.839> but<00:42:49.000> I<00:42:49.079> think 00:42:49.309 --> 00:42:49.319 align:start position:0% uh systems are working today but I think 00:42:49.319 --> 00:42:51.910 align:start position:0% uh systems are working today but I think it's<00:42:49.720> uh<00:42:50.200> at<00:42:50.359> some<00:42:50.599> point<00:42:51.200> there<00:42:51.359> is<00:42:51.559> going<00:42:51.760> to 00:42:51.910 --> 00:42:51.920 align:start position:0% it's uh at some point there is going to 00:42:51.920 --> 00:42:55.510 align:start position:0% it's uh at some point there is going to be<00:42:52.839> interest<00:42:53.559> or<00:42:54.200> prioritization<00:42:55.079> of<00:42:55.280> these 00:42:55.510 --> 00:42:55.520 align:start position:0% be interest or prioritization of these 00:42:55.520 --> 00:42:57.829 align:start position:0% be interest or prioritization of these kind<00:42:55.680> of<00:42:55.880> different<00:42:56.240> use<00:42:56.559> cases<00:42:57.400> uh<00:42:57.559> but<00:42:57.680> it's 00:42:57.829 --> 00:42:57.839 align:start position:0% kind of different use cases uh but it's 00:42:57.839 --> 00:43:00.829 align:start position:0% kind of different use cases uh but it's going<00:42:58.000> to<00:42:58.160> be<00:42:58.440> one<00:42:58.720> by<00:42:59.000> one<00:43:00.000> um<00:43:00.160> so<00:43:00.400> I<00:43:00.480> think 00:43:00.829 --> 00:43:00.839 align:start position:0% going to be one by one um so I think 00:43:00.839 --> 00:43:03.430 align:start position:0% going to be one by one um so I think they<00:43:01.079> might<00:43:01.559> they<00:43:01.720> might<00:43:02.000> coexist<00:43:03.000> uh<00:43:03.119> in<00:43:03.280> a 00:43:03.430 --> 00:43:03.440 align:start position:0% they might they might coexist uh in a 00:43:03.440 --> 00:43:06.630 align:start position:0% they might they might coexist uh in a world<00:43:03.880> where<00:43:04.680> um<00:43:05.400> where<00:43:05.599> both<00:43:05.800> use<00:43:06.040> cases<00:43:06.400> can 00:43:06.630 --> 00:43:06.640 align:start position:0% world where um where both use cases can 00:43:06.640 --> 00:43:09.109 align:start position:0% world where um where both use cases can can<00:43:06.839> still<00:43:07.559> uh<00:43:07.880> have<00:43:08.440> I<00:43:08.559> actually<00:43:08.720> think<00:43:08.920> they 00:43:09.109 --> 00:43:09.119 align:start position:0% can still uh have I actually think they 00:43:09.119 --> 00:43:11.710 align:start position:0% can still uh have I actually think they have<00:43:09.240> to<00:43:09.480> exist<00:43:09.920> right<00:43:10.160> like<00:43:10.400> because 00:43:11.710 --> 00:43:11.720 align:start position:0% have to exist right like because 00:43:11.720 --> 00:43:13.670 align:start position:0% have to exist right like because liquidity<00:43:12.720> is<00:43:12.800> still<00:43:12.960> going<00:43:13.079> to<00:43:13.200> be<00:43:13.319> in<00:43:13.440> like 00:43:13.670 --> 00:43:13.680 align:start position:0% liquidity is still going to be in like 00:43:13.680 --> 00:43:15.750 align:start position:0% liquidity is still going to be in like Unis<00:43:14.079> swap<00:43:14.480> unless<00:43:14.720> it's<00:43:14.880> like<00:43:15.040> an<00:43:15.160> offchain 00:43:15.750 --> 00:43:15.760 align:start position:0% Unis swap unless it's like an offchain 00:43:15.760 --> 00:43:17.510 align:start position:0% Unis swap unless it's like an offchain unless<00:43:16.040> everything<00:43:16.319> becomes<00:43:16.559> an<00:43:16.680> offchain<00:43:17.040> fq 00:43:17.510 --> 00:43:17.520 align:start position:0% unless everything becomes an offchain fq 00:43:17.520 --> 00:43:19.589 align:start position:0% unless everything becomes an offchain fq system<00:43:18.160> which<00:43:18.319> might<00:43:18.559> happen<00:43:18.839> but<00:43:19.000> like<00:43:19.359> even 00:43:19.589 --> 00:43:19.599 align:start position:0% system which might happen but like even 00:43:19.599 --> 00:43:20.790 align:start position:0% system which might happen but like even then<00:43:19.800> let's<00:43:19.960> say<00:43:20.079> you<00:43:20.160> want<00:43:20.240> to<00:43:20.359> borrow<00:43:20.640> some 00:43:20.790 --> 00:43:20.800 align:start position:0% then let's say you want to borrow some 00:43:20.800 --> 00:43:22.349 align:start position:0% then let's say you want to borrow some money<00:43:21.079> then<00:43:21.240> you<00:43:21.319> have<00:43:21.400> to<00:43:21.520> go<00:43:21.599> to<00:43:21.800> AA<00:43:22.160> you<00:43:22.240> want 00:43:22.349 --> 00:43:22.359 align:start position:0% money then you have to go to AA you want 00:43:22.359 --> 00:43:25.309 align:start position:0% money then you have to go to AA you want to<00:43:23.040> do<00:43:23.240> some<00:43:23.440> kind<00:43:23.559> of<00:43:24.119> YN<00:43:24.599> type<00:43:24.760> of<00:43:24.920> Vault 00:43:25.309 --> 00:43:25.319 align:start position:0% to do some kind of YN type of Vault 00:43:25.319 --> 00:43:28.349 align:start position:0% to do some kind of YN type of Vault stuff<00:43:25.760> that<00:43:25.960> you<00:43:26.480> like<00:43:27.240> basically<00:43:27.839> intense 00:43:28.349 --> 00:43:28.359 align:start position:0% stuff that you like basically intense 00:43:28.359 --> 00:43:30.309 align:start position:0% stuff that you like basically intense and<00:43:28.520> smart<00:43:28.839> contracts<00:43:29.240> are<00:43:29.400> just<00:43:29.839> they're<00:43:30.000> not 00:43:30.309 --> 00:43:30.319 align:start position:0% and smart contracts are just they're not 00:43:30.319 --> 00:43:32.750 align:start position:0% and smart contracts are just they're not really<00:43:30.720> con<00:43:31.079> connected<00:43:31.599> in<00:43:31.760> that<00:43:31.960> sense<00:43:32.359> right 00:43:32.750 --> 00:43:32.760 align:start position:0% really con connected in that sense right 00:43:32.760 --> 00:43:35.630 align:start position:0% really con connected in that sense right smart<00:43:33.119> contracts<00:43:33.559> are<00:43:34.079> protocols<00:43:35.079> or 00:43:35.630 --> 00:43:35.640 align:start position:0% smart contracts are protocols or 00:43:35.640 --> 00:43:37.829 align:start position:0% smart contracts are protocols or nowadays<00:43:36.200> also<00:43:36.520> accounts<00:43:37.119> if<00:43:37.240> we<00:43:37.440> talk<00:43:37.599> about 00:43:37.829 --> 00:43:37.839 align:start position:0% nowadays also accounts if we talk about 00:43:37.839 --> 00:43:39.150 align:start position:0% nowadays also accounts if we talk about account<00:43:38.119> abstraction<00:43:38.640> and<00:43:38.760> something<00:43:39.000> like 00:43:39.150 --> 00:43:39.160 align:start position:0% account abstraction and something like 00:43:39.160 --> 00:43:42.510 align:start position:0% account abstraction and something like that<00:43:39.720> the<00:43:39.880> intent<00:43:40.319> really<00:43:40.640> is<00:43:40.920> just<00:43:41.599> the<00:43:41.880> way 00:43:42.510 --> 00:43:42.520 align:start position:0% that the intent really is just the way 00:43:42.520 --> 00:43:45.230 align:start position:0% that the intent really is just the way how<00:43:42.680> you<00:43:43.079> express<00:43:43.640> your<00:43:44.079> preferences<00:43:45.079> that 00:43:45.230 --> 00:43:45.240 align:start position:0% how you express your preferences that 00:43:45.240 --> 00:43:47.069 align:start position:0% how you express your preferences that that<00:43:45.319> is<00:43:45.440> what<00:43:45.559> an<00:43:45.720> intent<00:43:46.119> is<00:43:46.440> but<00:43:46.640> that<00:43:46.880> that 00:43:47.069 --> 00:43:47.079 align:start position:0% that is what an intent is but that that 00:43:47.079 --> 00:43:49.190 align:start position:0% that is what an intent is but that that isn't<00:43:47.440> necessarily<00:43:48.000> connected<00:43:48.680> to<00:43:48.880> Smart 00:43:49.190 --> 00:43:49.200 align:start position:0% isn't necessarily connected to Smart 00:43:49.200 --> 00:43:51.430 align:start position:0% isn't necessarily connected to Smart contracts<00:43:49.559> in<00:43:49.680> anyway<00:43:50.040> smart<00:43:50.359> contracts<00:43:50.800> are 00:43:51.430 --> 00:43:51.440 align:start position:0% contracts in anyway smart contracts are 00:43:51.440 --> 00:43:54.030 align:start position:0% contracts in anyway smart contracts are how<00:43:51.640> we<00:43:52.359> build 00:43:54.030 --> 00:43:54.040 align:start position:0% how we build 00:43:54.040 --> 00:43:58.470 align:start position:0% how we build um<00:43:55.040> expression<00:43:56.040> of<00:43:56.559> something<00:43:57.520> on<00:43:57.760> chain<00:43:58.280> it's 00:43:58.470 --> 00:43:58.480 align:start position:0% um expression of something on chain it's 00:43:58.480 --> 00:44:00.829 align:start position:0% um expression of something on chain it's just<00:43:58.680> like<00:43:58.800> a<00:43:58.960> programming<00:43:59.640> language<00:44:00.400> thing 00:44:00.829 --> 00:44:00.839 align:start position:0% just like a programming language thing 00:44:00.839 --> 00:44:02.670 align:start position:0% just like a programming language thing at<00:44:00.960> the<00:44:01.040> end<00:44:01.200> of<00:44:01.319> the<00:44:01.480> day<00:44:02.040> which<00:44:02.319> the<00:44:02.440> other 00:44:02.670 --> 00:44:02.680 align:start position:0% at the end of the day which the other 00:44:02.680 --> 00:44:05.030 align:start position:0% at the end of the day which the other thing<00:44:02.880> is<00:44:03.119> like<00:44:03.559> what<00:44:03.720> do<00:44:03.839> I<00:44:04.000> want<00:44:04.280> is<00:44:04.400> a 00:44:05.030 --> 00:44:05.040 align:start position:0% thing is like what do I want is a 00:44:05.040 --> 00:44:08.270 align:start position:0% thing is like what do I want is a preference<00:44:06.040> um 00:44:08.270 --> 00:44:08.280 align:start position:0% preference um 00:44:08.280 --> 00:44:10.549 align:start position:0% preference um expression<00:44:09.280> okay<00:44:09.520> so<00:44:09.839> we<00:44:09.960> have<00:44:10.160> one<00:44:10.280> more 00:44:10.549 --> 00:44:10.559 align:start position:0% expression okay so we have one more 00:44:10.559 --> 00:44:12.790 align:start position:0% expression okay so we have one more question<00:44:11.079> are<00:44:11.440> Merkle<00:44:11.880> trees<00:44:12.200> the<00:44:12.359> answer<00:44:12.599> for 00:44:12.790 --> 00:44:12.800 align:start position:0% question are Merkle trees the answer for 00:44:12.800 --> 00:44:15.549 align:start position:0% question are Merkle trees the answer for cross 00:44:15.549 --> 00:44:15.559 align:start position:0% 00:44:15.559 --> 00:44:19.430 align:start position:0% intentions<00:44:16.559> again<00:44:16.800> anybody<00:44:17.200> can<00:44:17.880> take<00:44:18.880> I 00:44:19.430 --> 00:44:19.440 align:start position:0% intentions again anybody can take I 00:44:19.440 --> 00:44:21.710 align:start position:0% intentions again anybody can take I honestly<00:44:20.119> I<00:44:20.319> I<00:44:20.400> don't<00:44:20.640> have<00:44:20.839> a<00:44:21.079> an<00:44:21.280> opinion 00:44:21.710 --> 00:44:21.720 align:start position:0% honestly I I don't have a an opinion 00:44:21.720 --> 00:44:24.190 align:start position:0% honestly I I don't have a an opinion about<00:44:22.280> the<00:44:22.640> how<00:44:22.760> to<00:44:22.920> solve<00:44:23.240> the<00:44:23.640> cross<00:44:23.920> chain 00:44:24.190 --> 00:44:24.200 align:start position:0% about the how to solve the cross chain 00:44:24.200 --> 00:44:26.430 align:start position:0% about the how to solve the cross chain intentions<00:44:25.200> uh<00:44:25.599> I<00:44:25.680> mean<00:44:25.800> merries<00:44:26.319> are 00:44:26.430 --> 00:44:26.440 align:start position:0% intentions uh I mean merries are 00:44:26.440 --> 00:44:28.790 align:start position:0% intentions uh I mean merries are probably<00:44:26.640> going<00:44:26.720> to<00:44:26.800> be<00:44:27.119> out<00:44:27.280> of<00:44:27.400> it<00:44:27.800> um<00:44:28.079> in 00:44:28.790 --> 00:44:28.800 align:start position:0% probably going to be out of it um in 00:44:28.800 --> 00:44:30.630 align:start position:0% probably going to be out of it um in expressing<00:44:29.280> certain<00:44:29.599> things<00:44:30.280> as<00:44:30.359> I<00:44:30.480> said 00:44:30.630 --> 00:44:30.640 align:start position:0% expressing certain things as I said 00:44:30.640 --> 00:44:32.670 align:start position:0% expressing certain things as I said earlier<00:44:31.240> I<00:44:31.359> think<00:44:31.680> the<00:44:31.880> answer<00:44:32.240> for<00:44:32.440> cross 00:44:32.670 --> 00:44:32.680 align:start position:0% earlier I think the answer for cross 00:44:32.680 --> 00:44:35.589 align:start position:0% earlier I think the answer for cross chain<00:44:33.000> intentions<00:44:33.559> are<00:44:33.760> probably<00:44:34.079> ZK 00:44:35.589 --> 00:44:35.599 align:start position:0% chain intentions are probably ZK 00:44:35.599 --> 00:44:38.870 align:start position:0% chain intentions are probably ZK proofs<00:44:36.599> okay<00:44:37.400> yeah<00:44:37.559> that<00:44:37.720> makes<00:44:37.960> sense<00:44:38.440> uh<00:44:38.559> so 00:44:38.870 --> 00:44:38.880 align:start position:0% proofs okay yeah that makes sense uh so 00:44:38.880 --> 00:44:40.829 align:start position:0% proofs okay yeah that makes sense uh so we<00:44:39.000> have<00:44:39.119> a<00:44:39.240> question<00:44:39.480> from<00:44:39.760> there<00:44:40.280> yeah<00:44:40.520> just 00:44:40.829 --> 00:44:40.839 align:start position:0% we have a question from there yeah just 00:44:40.839 --> 00:44:42.990 align:start position:0% we have a question from there yeah just just<00:44:40.960> a<00:44:41.160> question<00:44:41.559> like<00:44:41.720> do<00:44:41.880> you<00:44:42.040> see<00:44:42.480> intense 00:44:42.990 --> 00:44:43.000 align:start position:0% just a question like do you see intense 00:44:43.000 --> 00:44:46.150 align:start position:0% just a question like do you see intense in<00:44:43.240> anything<00:44:43.599> beyond<00:44:44.280> defi<00:44:45.280> other<00:44:45.520> than<00:44:45.680> def 00:44:46.150 --> 00:44:46.160 align:start position:0% in anything beyond defi other than def 00:44:46.160 --> 00:44:48.630 align:start position:0% in anything beyond defi other than def have<00:44:46.240> you<00:44:46.359> seen<00:44:46.839> anything<00:44:47.839> any<00:44:48.040> intents<00:44:48.440> being 00:44:48.630 --> 00:44:48.640 align:start position:0% have you seen anything any intents being 00:44:48.640 --> 00:44:53.670 align:start position:0% have you seen anything any intents being used<00:44:49.319> Beyond 00:44:53.670 --> 00:44:53.680 align:start position:0% 00:44:53.680 --> 00:44:58.309 align:start position:0% D<00:44:54.680> I<00:44:54.839> have<00:44:55.119> heard<00:44:55.480> about<00:44:55.800> some<00:44:56.079> use<00:44:56.480> cases 00:44:58.309 --> 00:44:58.319 align:start position:0% D I have heard about some use cases 00:44:58.319 --> 00:45:02.230 align:start position:0% D I have heard about some use cases but<00:44:58.520> all<00:44:58.839> theorical<00:44:59.680> I<00:44:59.760> mean<00:45:00.480> I<00:45:01.480> I<00:45:01.599> never<00:45:01.880> saw 00:45:02.230 --> 00:45:02.240 align:start position:0% but all theorical I mean I I never saw 00:45:02.240 --> 00:45:07.430 align:start position:0% but all theorical I mean I I never saw them<00:45:03.079> uh<00:45:03.839> really<00:45:04.720> implemented<00:45:05.720> but<00:45:06.040> I<00:45:06.440> heard 00:45:07.430 --> 00:45:07.440 align:start position:0% them uh really implemented but I heard 00:45:07.440 --> 00:45:10.309 align:start position:0% them uh really implemented but I heard uh<00:45:07.720> and<00:45:07.880> I've<00:45:08.040> been<00:45:08.240> pitched<00:45:08.720> about<00:45:09.119> some<00:45:10.079> uh 00:45:10.309 --> 00:45:10.319 align:start position:0% uh and I've been pitched about some uh 00:45:10.319 --> 00:45:13.150 align:start position:0% uh and I've been pitched about some uh like<00:45:10.520> real<00:45:10.880> world<00:45:11.280> use<00:45:11.640> cases<00:45:12.119> where<00:45:12.319> you<00:45:12.520> can 00:45:13.150 --> 00:45:13.160 align:start position:0% like real world use cases where you can 00:45:13.160 --> 00:45:14.990 align:start position:0% like real world use cases where you can I<00:45:13.240> don't<00:45:13.400> know<00:45:13.720> rent<00:45:14.200> for<00:45:14.400> example<00:45:14.800> an 00:45:14.990 --> 00:45:15.000 align:start position:0% I don't know rent for example an 00:45:15.000 --> 00:45:18.030 align:start position:0% I don't know rent for example an apartment<00:45:15.599> with<00:45:15.920> uh<00:45:16.559> uh<00:45:17.119> with<00:45:17.280> through 00:45:18.030 --> 00:45:18.040 align:start position:0% apartment with uh uh with through 00:45:18.040 --> 00:45:21.109 align:start position:0% apartment with uh uh with through intents<00:45:19.040> um<00:45:19.760> but<00:45:19.920> I<00:45:20.000> think<00:45:20.160> we<00:45:20.280> are<00:45:20.440> not<00:45:20.680> there 00:45:21.109 --> 00:45:21.119 align:start position:0% intents um but I think we are not there 00:45:21.119 --> 00:45:24.549 align:start position:0% intents um but I think we are not there yet<00:45:21.880> uh<00:45:22.280> I<00:45:22.680> think<00:45:23.680> I'm<00:45:23.800> sure<00:45:24.079> that<00:45:24.200> we<00:45:24.319> are<00:45:24.400> not 00:45:24.549 --> 00:45:24.559 align:start position:0% yet uh I think I'm sure that we are not 00:45:24.559 --> 00:45:26.150 align:start position:0% yet uh I think I'm sure that we are not there<00:45:24.800> yet<00:45:24.960> because<00:45:25.160> we<00:45:25.280> are<00:45:25.400> not<00:45:25.520> seeing<00:45:25.839> them 00:45:26.150 --> 00:45:26.160 align:start position:0% there yet because we are not seeing them 00:45:26.160 --> 00:45:29.309 align:start position:0% there yet because we are not seeing them being<00:45:27.200> uh<00:45:27.440> implemented<00:45:27.960> in<00:45:28.160> that<00:45:28.359> way<00:45:29.079> but<00:45:29.240> I 00:45:29.309 --> 00:45:29.319 align:start position:0% being uh implemented in that way but I 00:45:29.319 --> 00:45:32.430 align:start position:0% being uh implemented in that way but I think<00:45:29.520> it<00:45:29.680> can<00:45:29.920> it<00:45:30.079> can<00:45:30.319> be<00:45:30.920> uh<00:45:31.160> work<00:45:32.119> it<00:45:32.240> can 00:45:32.430 --> 00:45:32.440 align:start position:0% think it can it can be uh work it can 00:45:32.440 --> 00:45:36.190 align:start position:0% think it can it can be uh work it can work<00:45:32.680> for<00:45:33.000> other<00:45:33.359> stuff<00:45:33.800> besides<00:45:34.240> D5<00:45:35.200> besides 00:45:36.190 --> 00:45:36.200 align:start position:0% work for other stuff besides D5 besides 00:45:36.200 --> 00:45:38.750 align:start position:0% work for other stuff besides D5 besides uh<00:45:36.760> I<00:45:36.839> don't<00:45:36.960> know<00:45:37.800> lending<00:45:38.240> borrowing 00:45:38.750 --> 00:45:38.760 align:start position:0% uh I don't know lending borrowing 00:45:38.760 --> 00:45:40.549 align:start position:0% uh I don't know lending borrowing besides<00:45:39.160> those<00:45:39.359> use<00:45:39.680> cases<00:45:40.040> I<00:45:40.160> think<00:45:40.400> they 00:45:40.549 --> 00:45:40.559 align:start position:0% besides those use cases I think they 00:45:40.559 --> 00:45:42.430 align:start position:0% besides those use cases I think they might<00:45:40.760> work<00:45:41.000> at<00:45:41.160> some<00:45:41.359> point<00:45:42.040> I<00:45:42.119> think<00:45:42.280> the 00:45:42.430 --> 00:45:42.440 align:start position:0% might work at some point I think the 00:45:42.440 --> 00:45:46.190 align:start position:0% might work at some point I think the technology<00:45:43.079> has<00:45:43.440> to<00:45:44.440> uh<00:45:44.960> has<00:45:45.079> to<00:45:45.319> evolve<00:45:46.040> in 00:45:46.190 --> 00:45:46.200 align:start position:0% technology has to uh has to evolve in 00:45:46.200 --> 00:45:48.230 align:start position:0% technology has to uh has to evolve in order<00:45:46.440> to<00:45:46.599> take<00:45:46.760> it<00:45:46.880> to<00:45:47.119> other<00:45:47.720> to<00:45:47.960> other 00:45:48.230 --> 00:45:48.240 align:start position:0% order to take it to other to other 00:45:48.240 --> 00:45:50.390 align:start position:0% order to take it to other to other places<00:45:49.160> I<00:45:49.240> mean<00:45:49.400> if<00:45:49.520> you<00:45:49.640> think<00:45:49.839> about<00:45:50.040> it<00:45:50.200> like 00:45:50.390 --> 00:45:50.400 align:start position:0% places I mean if you think about it like 00:45:50.400 --> 00:45:52.109 align:start position:0% places I mean if you think about it like Skys<00:45:50.760> scanner<00:45:51.160> is<00:45:51.240> an<00:45:51.400> intent-based 00:45:52.109 --> 00:45:52.119 align:start position:0% Skys scanner is an intent-based 00:45:52.119 --> 00:45:54.109 align:start position:0% Skys scanner is an intent-based application<00:45:53.119> you<00:45:53.280> go<00:45:53.480> in<00:45:53.640> there<00:45:53.800> you<00:45:53.920> put<00:45:54.040> a 00:45:54.109 --> 00:45:54.119 align:start position:0% application you go in there you put a 00:45:54.119 --> 00:45:56.109 align:start position:0% application you go in there you put a flight<00:45:54.440> in<00:45:54.640> and<00:45:54.800> it<00:45:54.960> says<00:45:55.280> you<00:45:55.480> it<00:45:55.599> gives<00:45:55.760> you<00:45:56.079> I 00:45:56.109 --> 00:45:56.119 align:start position:0% flight in and it says you it gives you I 00:45:56.119 --> 00:45:57.829 align:start position:0% flight in and it says you it gives you I mean<00:45:56.319> the<00:45:56.440> difference<00:45:56.720> between<00:45:57.040> intent<00:45:57.559> in<00:45:57.720> in 00:45:57.829 --> 00:45:57.839 align:start position:0% mean the difference between intent in in 00:45:57.839 --> 00:45:59.670 align:start position:0% mean the difference between intent in in some<00:45:58.040> ways<00:45:58.240> would<00:45:58.440> be<00:45:59.000> the<00:45:59.160> way<00:45:59.280> we<00:45:59.440> see 00:45:59.670 --> 00:45:59.680 align:start position:0% some ways would be the way we see 00:45:59.680 --> 00:46:01.870 align:start position:0% some ways would be the way we see intents<00:46:00.280> is<00:46:00.559> like<00:46:00.960> the<00:46:01.119> solver<00:46:01.480> just<00:46:01.599> fills 00:46:01.870 --> 00:46:01.880 align:start position:0% intents is like the solver just fills 00:46:01.880 --> 00:46:04.430 align:start position:0% intents is like the solver just fills you<00:46:02.079> the<00:46:02.280> best<00:46:02.559> one<00:46:03.000> and<00:46:03.680> like<00:46:03.920> in<00:46:04.119> Skys 00:46:04.430 --> 00:46:04.440 align:start position:0% you the best one and like in Skys 00:46:04.440 --> 00:46:05.990 align:start position:0% you the best one and like in Skys scanner<00:46:04.720> you<00:46:04.839> get<00:46:05.000> a<00:46:05.119> couple<00:46:05.319> of<00:46:05.480> options<00:46:05.800> of 00:46:05.990 --> 00:46:06.000 align:start position:0% scanner you get a couple of options of 00:46:06.000 --> 00:46:08.309 align:start position:0% scanner you get a couple of options of flights<00:46:06.640> but<00:46:06.760> in<00:46:06.880> similar<00:46:07.240> ways<00:46:07.520> how<00:46:07.720> lei<00:46:08.160> for 00:46:08.309 --> 00:46:08.319 align:start position:0% flights but in similar ways how lei for 00:46:08.319 --> 00:46:10.670 align:start position:0% flights but in similar ways how lei for example<00:46:08.599> works<00:46:08.920> today<00:46:09.720> is<00:46:10.000> you<00:46:10.160> go<00:46:10.319> in<00:46:10.480> and<00:46:10.559> you 00:46:10.670 --> 00:46:10.680 align:start position:0% example works today is you go in and you 00:46:10.680 --> 00:46:12.549 align:start position:0% example works today is you go in and you say<00:46:10.800> I<00:46:10.880> want<00:46:10.960> to<00:46:11.079> go<00:46:11.200> from<00:46:11.520> asset<00:46:11.839> a<00:46:12.000> on<00:46:12.160> chain<00:46:12.400> a 00:46:12.549 --> 00:46:12.559 align:start position:0% say I want to go from asset a on chain a 00:46:12.559 --> 00:46:15.030 align:start position:0% say I want to go from asset a on chain a to<00:46:12.720> asset<00:46:13.079> chain<00:46:13.559> B<00:46:13.720> on<00:46:13.839> chain<00:46:14.079> B<00:46:14.559> and<00:46:14.680> we<00:46:14.800> still 00:46:15.030 --> 00:46:15.040 align:start position:0% to asset chain B on chain B and we still 00:46:15.040 --> 00:46:17.390 align:start position:0% to asset chain B on chain B and we still give<00:46:15.200> you<00:46:15.400> options<00:46:15.800> we<00:46:15.920> just<00:46:16.119> don't<00:46:16.480> pick<00:46:17.200> like 00:46:17.390 --> 00:46:17.400 align:start position:0% give you options we just don't pick like 00:46:17.400 --> 00:46:19.390 align:start position:0% give you options we just don't pick like basically<00:46:18.079> we<00:46:18.280> we're<00:46:18.440> not<00:46:18.559> an<00:46:18.720> opinionated 00:46:19.390 --> 00:46:19.400 align:start position:0% basically we we're not an opinionated 00:46:19.400 --> 00:46:21.710 align:start position:0% basically we we're not an opinionated solver<00:46:20.200> as<00:46:20.400> to<00:46:20.640> we<00:46:20.760> don't<00:46:21.040> give<00:46:21.160> you<00:46:21.400> one 00:46:21.710 --> 00:46:21.720 align:start position:0% solver as to we don't give you one 00:46:21.720 --> 00:46:23.990 align:start position:0% solver as to we don't give you one option<00:46:22.400> we<00:46:22.559> give<00:46:22.720> you<00:46:22.880> multiple<00:46:23.359> options<00:46:23.880> that 00:46:23.990 --> 00:46:24.000 align:start position:0% option we give you multiple options that 00:46:24.000 --> 00:46:26.630 align:start position:0% option we give you multiple options that you<00:46:24.160> can<00:46:24.599> pick<00:46:24.839> from<00:46:25.520> but<00:46:25.720> that's<00:46:26.000> still<00:46:26.440> you 00:46:26.630 --> 00:46:26.640 align:start position:0% you can pick from but that's still you 00:46:26.640 --> 00:46:28.829 align:start position:0% you can pick from but that's still you still<00:46:27.119> give<00:46:27.280> us<00:46:27.440> an<00:46:27.599> intent<00:46:28.079> and<00:46:28.240> we<00:46:28.440> process 00:46:28.829 --> 00:46:28.839 align:start position:0% still give us an intent and we process 00:46:28.839 --> 00:46:30.710 align:start position:0% still give us an intent and we process that<00:46:29.000> intent<00:46:29.680> and<00:46:29.839> like<00:46:30.079> every<00:46:30.359> type<00:46:30.559> of 00:46:30.710 --> 00:46:30.720 align:start position:0% that intent and like every type of 00:46:30.720 --> 00:46:33.510 align:start position:0% that intent and like every type of aggregation<00:46:31.319> protocol<00:46:31.760> in<00:46:31.920> web<00:46:32.119> 2<00:46:33.040> more<00:46:33.240> or 00:46:33.510 --> 00:46:33.520 align:start position:0% aggregation protocol in web 2 more or 00:46:33.520 --> 00:46:35.990 align:start position:0% aggregation protocol in web 2 more or less<00:46:34.280> works<00:46:34.640> in<00:46:34.800> the<00:46:35.000> same<00:46:35.240> way<00:46:35.559> like<00:46:35.839> I<00:46:35.920> want 00:46:35.990 --> 00:46:36.000 align:start position:0% less works in the same way like I want 00:46:36.000 --> 00:46:37.910 align:start position:0% less works in the same way like I want to<00:46:36.119> buy<00:46:36.280> an<00:46:36.400> insurance<00:46:37.040> and<00:46:37.160> then<00:46:37.400> Insurance 00:46:37.910 --> 00:46:37.920 align:start position:0% to buy an insurance and then Insurance 00:46:37.920 --> 00:46:40.190 align:start position:0% to buy an insurance and then Insurance aggregator<00:46:38.520> gives<00:46:38.760> you<00:46:39.480> you<00:46:39.640> know<00:46:39.839> a<00:46:39.960> couple 00:46:40.190 --> 00:46:40.200 align:start position:0% aggregator gives you you know a couple 00:46:40.200 --> 00:46:42.870 align:start position:0% aggregator gives you you know a couple of<00:46:40.400> options<00:46:41.160> so<00:46:41.520> like<00:46:41.680> intents<00:46:42.079> are<00:46:42.280> not<00:46:42.640> in 00:46:42.870 --> 00:46:42.880 align:start position:0% of options so like intents are not in 00:46:42.880 --> 00:46:44.829 align:start position:0% of options so like intents are not in anyway<00:46:43.400> web<00:46:43.640> tree<00:46:43.960> specific<00:46:44.400> they're<00:46:44.599> just 00:46:44.829 --> 00:46:44.839 align:start position:0% anyway web tree specific they're just 00:46:44.839 --> 00:46:49.870 align:start position:0% anyway web tree specific they're just like<00:46:45.040> a<00:46:45.240> way<00:46:45.599> of<00:46:46.680> solving<00:46:47.680> um<00:46:48.440> user 00:46:49.870 --> 00:46:49.880 align:start position:0% like a way of solving um user 00:46:49.880 --> 00:46:53.349 align:start position:0% like a way of solving um user experience<00:46:50.880> I<00:46:51.000> think<00:46:51.440> uh<00:46:52.440> doubling<00:46:52.920> down<00:46:53.119> on 00:46:53.349 --> 00:46:53.359 align:start position:0% experience I think uh doubling down on 00:46:53.359 --> 00:46:56.230 align:start position:0% experience I think uh doubling down on your<00:46:54.079> example<00:46:54.440> of<00:46:54.559> Skys<00:46:54.880> scanner<00:46:55.839> something 00:46:56.230 --> 00:46:56.240 align:start position:0% your example of Skys scanner something 00:46:56.240 --> 00:46:59.150 align:start position:0% your example of Skys scanner something that<00:46:56.400> in<00:46:56.960> might<00:46:57.160> soul<00:46:57.440> for<00:46:57.599> example<00:46:58.040> is<00:46:58.839> I<00:46:58.960> want 00:46:59.150 --> 00:46:59.160 align:start position:0% that in might soul for example is I want 00:46:59.160 --> 00:47:01.829 align:start position:0% that in might soul for example is I want to<00:46:59.800> travel<00:47:00.160> to<00:47:00.400> this<00:47:00.559> destination<00:47:01.319> for<00:47:01.640> this 00:47:01.829 --> 00:47:01.839 align:start position:0% to travel to this destination for this 00:47:01.839 --> 00:47:03.470 align:start position:0% to travel to this destination for this amount<00:47:02.079> of<00:47:02.280> time<00:47:02.599> and<00:47:02.720> I<00:47:02.839> want<00:47:02.960> to<00:47:03.119> stay<00:47:03.319> in 00:47:03.470 --> 00:47:03.480 align:start position:0% amount of time and I want to stay in 00:47:03.480 --> 00:47:05.870 align:start position:0% amount of time and I want to stay in these<00:47:03.720> places<00:47:04.520> and<00:47:04.720> have<00:47:04.960> the<00:47:05.079> whole<00:47:05.440> solution 00:47:05.870 --> 00:47:05.880 align:start position:0% these places and have the whole solution 00:47:05.880 --> 00:47:09.030 align:start position:0% these places and have the whole solution built<00:47:06.160> for<00:47:06.359> you<00:47:06.839> like<00:47:07.359> book<00:47:07.640> your<00:47:08.040> book<00:47:08.319> your 00:47:09.030 --> 00:47:09.040 align:start position:0% built for you like book your book your 00:47:09.040 --> 00:47:12.549 align:start position:0% built for you like book your book your uh<00:47:09.200> airplane<00:47:09.720> tickets<00:47:10.440> book<00:47:10.720> your<00:47:11.160> hotel<00:47:12.160> uh 00:47:12.549 --> 00:47:12.559 align:start position:0% uh airplane tickets book your hotel uh 00:47:12.559 --> 00:47:14.710 align:start position:0% uh airplane tickets book your hotel uh book<00:47:12.880> the<00:47:13.119> stuff<00:47:13.400> that<00:47:13.520> you<00:47:13.640> want<00:47:13.800> to<00:47:13.960> do<00:47:14.520> and 00:47:14.710 --> 00:47:14.720 align:start position:0% book the stuff that you want to do and 00:47:14.720 --> 00:47:18.470 align:start position:0% book the stuff that you want to do and reserve<00:47:15.240> your<00:47:16.040> uh<00:47:16.359> your<00:47:16.960> dinners<00:47:17.440> or<00:47:17.640> lunch<00:47:17.960> in 00:47:18.470 --> 00:47:18.480 align:start position:0% reserve your uh your dinners or lunch in 00:47:18.480 --> 00:47:21.309 align:start position:0% reserve your uh your dinners or lunch in restaurants<00:47:19.480> that<00:47:19.599> would<00:47:19.800> be<00:47:20.000> like<00:47:20.240> the<00:47:20.839> uh 00:47:21.309 --> 00:47:21.319 align:start position:0% restaurants that would be like the uh 00:47:21.319 --> 00:47:25.589 align:start position:0% restaurants that would be like the uh the<00:47:21.480> the<00:47:21.680> ideal<00:47:22.119> world<00:47:22.400> of<00:47:22.559> an<00:47:23.040> intense<00:47:24.520> um<00:47:25.520> I 00:47:25.589 --> 00:47:25.599 align:start position:0% the the ideal world of an intense um I 00:47:25.599 --> 00:47:27.190 align:start position:0% the the ideal world of an intense um I think<00:47:25.800> it<00:47:25.960> might<00:47:26.200> it<00:47:26.359> might<00:47:26.520> happen<00:47:26.920> at<00:47:27.040> some 00:47:27.190 --> 00:47:27.200 align:start position:0% think it might it might happen at some 00:47:27.200 --> 00:47:29.910 align:start position:0% think it might it might happen at some point<00:47:27.400> but<00:47:27.559> I<00:47:27.640> don't<00:47:27.760> know<00:47:28.119> when<00:47:28.400> or 00:47:29.910 --> 00:47:29.920 align:start position:0% point but I don't know when or 00:47:29.920 --> 00:47:32.190 align:start position:0% point but I don't know when or how<00:47:30.920> yeah<00:47:31.280> maybe<00:47:31.480> you<00:47:31.559> can<00:47:31.720> say<00:47:31.880> something 00:47:32.190 --> 00:47:32.200 align:start position:0% how yeah maybe you can say something 00:47:32.200 --> 00:47:33.710 align:start position:0% how yeah maybe you can say something because<00:47:32.480> that's<00:47:32.599> kind<00:47:32.720> of<00:47:32.800> the<00:47:33.000> AI<00:47:33.280> use<00:47:33.520> case 00:47:33.710 --> 00:47:33.720 align:start position:0% because that's kind of the AI use case 00:47:33.720 --> 00:47:36.589 align:start position:0% because that's kind of the AI use case at<00:47:33.800> the<00:47:33.920> end<00:47:34.040> of<00:47:34.160> the<00:47:34.760> day<00:47:35.760> The<00:47:35.920> Skys<00:47:36.200> scanner 00:47:36.589 --> 00:47:36.599 align:start position:0% at the end of the day The Skys scanner 00:47:36.599 --> 00:47:37.790 align:start position:0% at the end of the day The Skys scanner thing 00:47:37.790 --> 00:47:37.800 align:start position:0% thing 00:47:37.800 --> 00:47:40.470 align:start position:0% thing was<00:47:38.800> I<00:47:38.920> used<00:47:39.040> to<00:47:39.160> use<00:47:39.319> it<00:47:39.480> like<00:47:39.640> all<00:47:39.760> the<00:47:39.960> time 00:47:40.470 --> 00:47:40.480 align:start position:0% was I used to use it like all the time 00:47:40.480 --> 00:47:41.990 align:start position:0% was I used to use it like all the time but<00:47:40.640> yeah<00:47:40.720> I<00:47:40.800> mean<00:47:41.000> intend<00:47:41.280> is<00:47:41.359> an<00:47:41.480> intention<00:47:41.960> I 00:47:41.990 --> 00:47:42.000 align:start position:0% but yeah I mean intend is an intention I 00:47:42.000 --> 00:47:45.430 align:start position:0% but yeah I mean intend is an intention I mean<00:47:42.359> it<00:47:42.480> depends<00:47:42.960> on<00:47:43.960> what<00:47:44.160> context<00:47:44.559> it<00:47:44.680> is 00:47:45.430 --> 00:47:45.440 align:start position:0% mean it depends on what context it is 00:47:45.440 --> 00:47:49.710 align:start position:0% mean it depends on what context it is but<00:47:46.359> defi<00:47:47.359> abroad<00:47:48.240> other<00:47:48.599> like<00:47:48.839> cases<00:47:49.559> yeah 00:47:49.710 --> 00:47:49.720 align:start position:0% but defi abroad other like cases yeah 00:47:49.720 --> 00:47:52.829 align:start position:0% but defi abroad other like cases yeah we're<00:47:49.920> not<00:47:50.119> there<00:47:50.319> yet<00:47:50.559> I<00:47:50.680> think<00:47:51.480> we'll<00:47:51.839> see 00:47:52.829 --> 00:47:52.839 align:start position:0% we're not there yet I think we'll see 00:47:52.839 --> 00:47:55.790 align:start position:0% we're not there yet I think we'll see but<00:47:53.559> you<00:47:53.680> want<00:47:53.760> to<00:47:53.880> say<00:47:54.119> something<00:47:55.119> I<00:47:55.559> I<00:47:55.640> think 00:47:55.790 --> 00:47:55.800 align:start position:0% but you want to say something I I think 00:47:55.800 --> 00:47:57.430 align:start position:0% but you want to say something I I think we're<00:47:56.000> yeah<00:47:56.280> I<00:47:56.359> think<00:47:56.480> we're<00:47:56.599> good 00:47:57.430 --> 00:47:57.440 align:start position:0% we're yeah I think we're good 00:47:57.440 --> 00:47:59.349 align:start position:0% we're yeah I think we're good we<00:47:57.640> agree<00:47:58.000> we 00:47:59.349 --> 00:47:59.359 align:start position:0% we agree we 00:47:59.359 --> 00:48:04.349 align:start position:0% we agree we agree<00:48:00.359> say<00:48:00.680> goodbye<00:48:01.760> yeah<00:48:02.760> so<00:48:03.079> any<00:48:03.240> more 00:48:04.349 --> 00:48:04.359 align:start position:0% agree say goodbye yeah so any more 00:48:04.359 --> 00:48:08.309 align:start position:0% agree say goodbye yeah so any more questions<00:48:05.359> we<00:48:05.520> have<00:48:05.720> one<00:48:05.880> more<00:48:06.079> minute 00:48:08.309 --> 00:48:08.319 align:start position:0% questions we have one more minute 00:48:08.319 --> 00:48:11.069 align:start position:0% questions we have one more minute here<00:48:09.319> if<00:48:09.520> not<00:48:10.000> we<00:48:10.119> can<00:48:10.319> thank<00:48:10.520> the<00:48:10.640> speakers 00:48:11.069 --> 00:48:11.079 align:start position:0% here if not we can thank the speakers 00:48:11.079 --> 00:48:12.230 align:start position:0% here if not we can thank the speakers again<00:48:11.359> thank<00:48:11.520> you<00:48:11.640> so<00:48:11.760> much<00:48:11.920> for<00:48:12.040> the 00:48:12.230 --> 00:48:12.240 align:start position:0% again thank you so much for the 00:48:12.240 --> 00:48:17.200 align:start position:0% again thank you so much for the wonderful<00:48:12.640> talk<00:48:13.000> and<00:48:14.000> thank<00:48:14.200> you