WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:11.950 align:start position:0% [Music] 00:00:11.950 --> 00:00:11.960 align:start position:0% 00:00:11.960 --> 00:00:15.410 align:start position:0% the<00:00:12.960> workshop<00:00:13.259> that<00:00:13.500> we're<00:00:13.679> doing<00:00:13.860> is<00:00:14.639> using 00:00:15.410 --> 00:00:15.420 align:start position:0% the workshop that we're doing is using 00:00:15.420 --> 00:00:17.450 align:start position:0% the workshop that we're doing is using the<00:00:15.540> graph<00:00:15.780> in<00:00:16.080> Dune<00:00:16.500> to<00:00:16.740> power<00:00:16.920> on<00:00:17.220> chain 00:00:17.450 --> 00:00:17.460 align:start position:0% the graph in Dune to power on chain 00:00:17.460 --> 00:00:20.390 align:start position:0% the graph in Dune to power on chain actions<00:00:18.140> my<00:00:19.140> name<00:00:19.199> is<00:00:19.320> Christian<00:00:19.500> this<00:00:20.279> is 00:00:20.390 --> 00:00:20.400 align:start position:0% actions my name is Christian this is 00:00:20.400 --> 00:00:23.390 align:start position:0% actions my name is Christian this is Matthias<00:00:20.939> and<00:00:21.840> we're<00:00:22.140> from<00:00:22.380> component<00:00:22.980> you 00:00:23.390 --> 00:00:23.400 align:start position:0% Matthias and we're from component you 00:00:23.400 --> 00:00:26.689 align:start position:0% Matthias and we're from component you can<00:00:23.580> find<00:00:23.640> us<00:00:23.820> at<00:00:24.260> component.fi<00:00:25.580> and<00:00:26.580> we'll 00:00:26.689 --> 00:00:26.699 align:start position:0% can find us at component.fi and we'll 00:00:26.699 --> 00:00:30.109 align:start position:0% can find us at component.fi and we'll quickly<00:00:27.000> go<00:00:27.240> through<00:00:27.480> the<00:00:28.260> agenda<00:00:28.619> so 00:00:30.109 --> 00:00:30.119 align:start position:0% quickly go through the agenda so 00:00:30.119 --> 00:00:31.429 align:start position:0% quickly go through the agenda so you<00:00:30.539> can<00:00:30.660> get<00:00:30.720> an<00:00:30.840> idea<00:00:31.019> of<00:00:31.080> what<00:00:31.199> we're<00:00:31.320> doing 00:00:31.429 --> 00:00:31.439 align:start position:0% you can get an idea of what we're doing 00:00:31.439 --> 00:00:32.510 align:start position:0% you can get an idea of what we're doing here 00:00:32.510 --> 00:00:32.520 align:start position:0% here 00:00:32.520 --> 00:00:34.610 align:start position:0% here um<00:00:32.579> so<00:00:33.300> first<00:00:33.540> things<00:00:33.719> first<00:00:34.079> I<00:00:34.380> just<00:00:34.500> wanted 00:00:34.610 --> 00:00:34.620 align:start position:0% um so first things first I just wanted 00:00:34.620 --> 00:00:37.130 align:start position:0% um so first things first I just wanted to<00:00:34.800> mention<00:00:34.920> that<00:00:35.340> this<00:00:35.820> will<00:00:36.059> not<00:00:36.239> be<00:00:36.480> a<00:00:36.840> code 00:00:37.130 --> 00:00:37.140 align:start position:0% to mention that this will not be a code 00:00:37.140 --> 00:00:40.250 align:start position:0% to mention that this will not be a code along<00:00:37.399> we<00:00:38.399> wanted<00:00:38.520> it<00:00:38.760> to<00:00:38.880> be<00:00:39.000> but<00:00:39.420> some<00:00:40.020> of<00:00:40.140> the 00:00:40.250 --> 00:00:40.260 align:start position:0% along we wanted it to be but some of the 00:00:40.260 --> 00:00:43.549 align:start position:0% along we wanted it to be but some of the dependencies<00:00:40.739> required<00:00:41.480> uh<00:00:42.480> you<00:00:43.200> need<00:00:43.440> pretty 00:00:43.549 --> 00:00:43.559 align:start position:0% dependencies required uh you need pretty 00:00:43.559 --> 00:00:44.930 align:start position:0% dependencies required uh you need pretty good<00:00:43.739> Wi-Fi<00:00:44.040> to<00:00:44.280> download<00:00:44.399> them<00:00:44.640> so<00:00:44.820> you'd 00:00:44.930 --> 00:00:44.940 align:start position:0% good Wi-Fi to download them so you'd 00:00:44.940 --> 00:00:46.430 align:start position:0% good Wi-Fi to download them so you'd have<00:00:45.059> to<00:00:45.180> run<00:00:45.239> to<00:00:45.420> the<00:00:45.540> basement<00:00:45.660> come<00:00:46.079> back<00:00:46.200> up 00:00:46.430 --> 00:00:46.440 align:start position:0% have to run to the basement come back up 00:00:46.440 --> 00:00:49.369 align:start position:0% have to run to the basement come back up uh<00:00:47.219> we<00:00:47.399> don't<00:00:47.520> want<00:00:47.640> that<00:00:47.879> so<00:00:48.300> instead<00:00:49.200> we'll 00:00:49.369 --> 00:00:49.379 align:start position:0% uh we don't want that so instead we'll 00:00:49.379 --> 00:00:51.950 align:start position:0% uh we don't want that so instead we'll just<00:00:49.680> discuss<00:00:50.399> uh<00:00:51.239> some<00:00:51.420> of<00:00:51.539> the<00:00:51.600> things<00:00:51.780> that 00:00:51.950 --> 00:00:51.960 align:start position:0% just discuss uh some of the things that 00:00:51.960 --> 00:00:53.569 align:start position:0% just discuss uh some of the things that you<00:00:52.320> would<00:00:52.440> have<00:00:52.680> uh<00:00:53.100> that<00:00:53.340> you<00:00:53.399> would<00:00:53.520> have 00:00:53.569 --> 00:00:53.579 align:start position:0% you would have uh that you would have 00:00:53.579 --> 00:00:54.830 align:start position:0% you would have uh that you would have coded 00:00:54.830 --> 00:00:54.840 align:start position:0% coded 00:00:54.840 --> 00:00:56.330 align:start position:0% coded so<00:00:55.199> one<00:00:55.440> we<00:00:55.620> want<00:00:55.680> to<00:00:55.800> get<00:00:55.860> to<00:00:55.980> know<00:00:56.100> each<00:00:56.219> other 00:00:56.330 --> 00:00:56.340 align:start position:0% so one we want to get to know each other 00:00:56.340 --> 00:00:59.510 align:start position:0% so one we want to get to know each other I<00:00:57.059> think<00:00:57.420> that's<00:00:57.899> uh<00:00:58.440> you<00:00:58.620> know<00:00:58.739> why<00:00:59.039> a<00:00:59.399> lot<00:00:59.460> of 00:00:59.510 --> 00:00:59.520 align:start position:0% I think that's uh you know why a lot of 00:00:59.520 --> 00:01:01.610 align:start position:0% I think that's uh you know why a lot of us<00:00:59.640> come<00:00:59.820> here<00:01:00.000> is<00:01:00.300> to<00:01:00.539> find<00:01:00.780> like<00:01:00.960> like-minded 00:01:01.610 --> 00:01:01.620 align:start position:0% us come here is to find like like-minded 00:01:01.620 --> 00:01:04.670 align:start position:0% us come here is to find like like-minded individuals<00:01:02.180> uh<00:01:03.180> two<00:01:03.420> we're<00:01:03.960> gonna<00:01:04.140> do<00:01:04.440> an 00:01:04.670 --> 00:01:04.680 align:start position:0% individuals uh two we're gonna do an 00:01:04.680 --> 00:01:06.950 align:start position:0% individuals uh two we're gonna do an overview<00:01:04.979> of<00:01:05.159> the<00:01:05.339> web3<00:01:05.700> data<00:01:06.060> stack 00:01:06.950 --> 00:01:06.960 align:start position:0% overview of the web3 data stack 00:01:06.960 --> 00:01:08.030 align:start position:0% overview of the web3 data stack um<00:01:07.020> so<00:01:07.080> give<00:01:07.260> you<00:01:07.380> an<00:01:07.439> idea<00:01:07.680> of<00:01:07.740> like<00:01:07.860> the 00:01:08.030 --> 00:01:08.040 align:start position:0% um so give you an idea of like the 00:01:08.040 --> 00:01:09.950 align:start position:0% um so give you an idea of like the different<00:01:08.220> layers<00:01:08.640> of<00:01:08.939> the<00:01:09.060> web3<00:01:09.420> data<00:01:09.780> stack 00:01:09.950 --> 00:01:09.960 align:start position:0% different layers of the web3 data stack 00:01:09.960 --> 00:01:11.810 align:start position:0% different layers of the web3 data stack and<00:01:10.140> how<00:01:10.260> you<00:01:10.380> can<00:01:10.500> use<00:01:10.619> them 00:01:11.810 --> 00:01:11.820 align:start position:0% and how you can use them 00:01:11.820 --> 00:01:14.510 align:start position:0% and how you can use them three<00:01:12.659> um<00:01:12.720> we're<00:01:12.840> gonna<00:01:13.020> do<00:01:13.380> essentially<00:01:14.340> an 00:01:14.510 --> 00:01:14.520 align:start position:0% three um we're gonna do essentially an 00:01:14.520 --> 00:01:17.510 align:start position:0% three um we're gonna do essentially an example<00:01:14.960> that<00:01:15.960> goes<00:01:16.260> through<00:01:16.500> uh<00:01:17.159> that<00:01:17.400> you 00:01:17.510 --> 00:01:17.520 align:start position:0% example that goes through uh that you 00:01:17.520 --> 00:01:18.830 align:start position:0% example that goes through uh that you would<00:01:17.580> have<00:01:17.700> coded<00:01:18.000> along<00:01:18.119> but<00:01:18.420> instead<00:01:18.659> we'll 00:01:18.830 --> 00:01:18.840 align:start position:0% would have coded along but instead we'll 00:01:18.840 --> 00:01:20.929 align:start position:0% would have coded along but instead we'll just<00:01:18.960> kind<00:01:19.080> of<00:01:19.140> show<00:01:19.320> you<00:01:19.439> how<00:01:20.040> we<00:01:20.159> did<00:01:20.280> it<00:01:20.520> uh 00:01:20.929 --> 00:01:20.939 align:start position:0% just kind of show you how we did it uh 00:01:20.939 --> 00:01:22.670 align:start position:0% just kind of show you how we did it uh and<00:01:21.299> can<00:01:21.479> give<00:01:21.600> you<00:01:21.780> the<00:01:22.080> information<00:01:22.200> so<00:01:22.560> you 00:01:22.670 --> 00:01:22.680 align:start position:0% and can give you the information so you 00:01:22.680 --> 00:01:24.770 align:start position:0% and can give you the information so you can<00:01:22.799> do<00:01:22.920> it<00:01:23.040> yourself<00:01:23.100> later 00:01:24.770 --> 00:01:24.780 align:start position:0% can do it yourself later 00:01:24.780 --> 00:01:26.690 align:start position:0% can do it yourself later um<00:01:24.840> and<00:01:25.080> that'll<00:01:25.320> be<00:01:25.500> data<00:01:25.920> fetching<00:01:26.280> so<00:01:26.580> the 00:01:26.690 --> 00:01:26.700 align:start position:0% um and that'll be data fetching so the 00:01:26.700 --> 00:01:28.910 align:start position:0% um and that'll be data fetching so the data<00:01:26.939> fetching<00:01:27.299> process<00:01:27.600> data<00:01:28.500> processing 00:01:28.910 --> 00:01:28.920 align:start position:0% data fetching process data processing 00:01:28.920 --> 00:01:30.350 align:start position:0% data fetching process data processing and<00:01:29.040> modeling<00:01:29.400> so<00:01:29.640> what<00:01:29.820> you<00:01:29.939> do<00:01:30.060> with<00:01:30.240> that 00:01:30.350 --> 00:01:30.360 align:start position:0% and modeling so what you do with that 00:01:30.360 --> 00:01:32.210 align:start position:0% and modeling so what you do with that data<00:01:30.600> after<00:01:30.780> you<00:01:31.020> fetch<00:01:31.320> it<00:01:31.439> and<00:01:32.100> then 00:01:32.210 --> 00:01:32.220 align:start position:0% data after you fetch it and then 00:01:32.220 --> 00:01:34.030 align:start position:0% data after you fetch it and then transaction<00:01:32.759> execution 00:01:34.030 --> 00:01:34.040 align:start position:0% transaction execution 00:01:34.040 --> 00:01:37.550 align:start position:0% transaction execution so<00:01:35.040> essentially<00:01:35.579> a<00:01:36.119> way<00:01:36.299> to<00:01:36.780> grab<00:01:37.200> data 00:01:37.550 --> 00:01:37.560 align:start position:0% so essentially a way to grab data 00:01:37.560 --> 00:01:39.649 align:start position:0% so essentially a way to grab data process<00:01:37.920> it<00:01:38.100> model<00:01:38.340> it<00:01:38.579> and<00:01:39.119> then<00:01:39.240> have<00:01:39.479> that 00:01:39.649 --> 00:01:39.659 align:start position:0% process it model it and then have that 00:01:39.659 --> 00:01:42.469 align:start position:0% process it model it and then have that do<00:01:39.840> an<00:01:39.960> on-chain<00:01:40.439> action<00:01:40.860> a<00:01:41.820> transaction<00:01:42.180> for 00:01:42.469 --> 00:01:42.479 align:start position:0% do an on-chain action a transaction for 00:01:42.479 --> 00:01:43.490 align:start position:0% do an on-chain action a transaction for you 00:01:43.490 --> 00:01:43.500 align:start position:0% you 00:01:43.500 --> 00:01:45.950 align:start position:0% you and<00:01:43.979> then<00:01:44.100> at<00:01:44.220> the<00:01:44.400> end<00:01:44.520> we'll<00:01:44.880> do<00:01:45.119> breakout 00:01:45.950 --> 00:01:45.960 align:start position:0% and then at the end we'll do breakout 00:01:45.960 --> 00:01:47.870 align:start position:0% and then at the end we'll do breakout sessions<00:01:46.320> just<00:01:46.860> at<00:01:47.040> your<00:01:47.159> tables<00:01:47.460> or<00:01:47.700> whoever 00:01:47.870 --> 00:01:47.880 align:start position:0% sessions just at your tables or whoever 00:01:47.880 --> 00:01:49.670 align:start position:0% sessions just at your tables or whoever you're<00:01:48.000> standing<00:01:48.299> next<00:01:48.420> to 00:01:49.670 --> 00:01:49.680 align:start position:0% you're standing next to 00:01:49.680 --> 00:01:51.410 align:start position:0% you're standing next to um instead<00:01:50.159> of<00:01:50.280> the<00:01:50.460> instead<00:01:50.939> of<00:01:51.000> the<00:01:51.119> coding 00:01:51.410 --> 00:01:51.420 align:start position:0% um instead of the instead of the coding 00:01:51.420 --> 00:01:53.810 align:start position:0% um instead of the instead of the coding element<00:01:51.600> we'll<00:01:52.079> just<00:01:52.640> essentially<00:01:53.640> design 00:01:53.810 --> 00:01:53.820 align:start position:0% element we'll just essentially design 00:01:53.820 --> 00:01:55.490 align:start position:0% element we'll just essentially design your<00:01:54.180> own<00:01:54.299> automation<00:01:54.720> speaking<00:01:55.259> with<00:01:55.380> your 00:01:55.490 --> 00:01:55.500 align:start position:0% your own automation speaking with your 00:01:55.500 --> 00:01:56.810 align:start position:0% your own automation speaking with your table<00:01:55.680> but<00:01:56.040> we'll<00:01:56.280> walk<00:01:56.399> you<00:01:56.520> through<00:01:56.640> it 00:01:56.810 --> 00:01:56.820 align:start position:0% table but we'll walk you through it 00:01:56.820 --> 00:01:58.429 align:start position:0% table but we'll walk you through it we'll<00:01:57.119> do<00:01:57.360> some<00:01:57.600> engineering<00:01:57.960> instead<00:01:58.320> of 00:01:58.429 --> 00:01:58.439 align:start position:0% we'll do some engineering instead of 00:01:58.439 --> 00:02:02.330 align:start position:0% we'll do some engineering instead of coding 00:02:02.330 --> 00:02:02.340 align:start position:0% 00:02:02.340 --> 00:02:07.969 align:start position:0% cool<00:02:02.820> so<00:02:03.439> uh<00:02:04.439> this<00:02:04.860> is<00:02:05.100> actually<00:02:05.399> uh<00:02:06.360> my<00:02:06.719> email 00:02:07.969 --> 00:02:07.979 align:start position:0% cool so uh this is actually uh my email 00:02:07.979 --> 00:02:09.410 align:start position:0% cool so uh this is actually uh my email um<00:02:08.039> I<00:02:08.640> don't<00:02:08.759> know<00:02:08.819> if<00:02:08.880> you're<00:02:09.000> familiar<00:02:09.300> with 00:02:09.410 --> 00:02:09.420 align:start position:0% um I don't know if you're familiar with 00:02:09.420 --> 00:02:11.930 align:start position:0% um I don't know if you're familiar with Quest<00:02:09.599> trade<00:02:10.020> that's<00:02:10.200> a<00:02:10.440> Canadian<00:02:10.860> uh<00:02:11.580> company 00:02:11.930 --> 00:02:11.940 align:start position:0% Quest trade that's a Canadian uh company 00:02:11.940 --> 00:02:14.449 align:start position:0% Quest trade that's a Canadian uh company for<00:02:12.480> uh<00:02:13.020> for<00:02:13.440> trading<00:02:13.739> stocks<00:02:14.099> and<00:02:14.220> using 00:02:14.449 --> 00:02:14.459 align:start position:0% for uh for trading stocks and using 00:02:14.459 --> 00:02:16.910 align:start position:0% for uh for trading stocks and using derivatives<00:02:14.760> I<00:02:15.300> got<00:02:15.420> margin<00:02:15.780> called<00:02:15.959> a<00:02:16.260> lot<00:02:16.319> uh 00:02:16.910 --> 00:02:16.920 align:start position:0% derivatives I got margin called a lot uh 00:02:16.920 --> 00:02:18.890 align:start position:0% derivatives I got margin called a lot uh as<00:02:17.099> you<00:02:17.220> can<00:02:17.340> see 00:02:18.890 --> 00:02:18.900 align:start position:0% as you can see 00:02:18.900 --> 00:02:20.869 align:start position:0% as you can see um<00:02:19.379> it<00:02:19.860> wasn't<00:02:20.040> that<00:02:20.220> much<00:02:20.340> money<00:02:20.520> it's<00:02:20.700> okay 00:02:20.869 --> 00:02:20.879 align:start position:0% um it wasn't that much money it's okay 00:02:20.879 --> 00:02:24.530 align:start position:0% um it wasn't that much money it's okay but<00:02:22.080> um<00:02:22.140> I'm<00:02:22.440> not<00:02:22.620> a<00:02:22.739> good<00:02:22.800> Trader<00:02:23.220> basically 00:02:24.530 --> 00:02:24.540 align:start position:0% but um I'm not a good Trader basically 00:02:24.540 --> 00:02:27.110 align:start position:0% but um I'm not a good Trader basically um and<00:02:25.140> that's<00:02:25.560> kind<00:02:25.739> of<00:02:25.860> my<00:02:26.099> motivation<00:02:26.520> for 00:02:27.110 --> 00:02:27.120 align:start position:0% um and that's kind of my motivation for 00:02:27.120 --> 00:02:29.089 align:start position:0% um and that's kind of my motivation for for<00:02:27.420> what<00:02:27.660> we're<00:02:27.780> doing 00:02:29.089 --> 00:02:29.099 align:start position:0% for what we're doing 00:02:29.099 --> 00:02:31.130 align:start position:0% for what we're doing um<00:02:29.160> because<00:02:29.520> I<00:02:30.000> got<00:02:30.120> margin<00:02:30.360> called<00:02:30.540> so<00:02:30.840> much<00:02:30.959> I 00:02:31.130 --> 00:02:31.140 align:start position:0% um because I got margin called so much I 00:02:31.140 --> 00:02:32.270 align:start position:0% um because I got margin called so much I know<00:02:31.260> I'm<00:02:31.319> a<00:02:31.500> bad<00:02:31.560> Trader<00:02:31.920> you<00:02:32.040> know<00:02:32.160> maybe 00:02:32.270 --> 00:02:32.280 align:start position:0% know I'm a bad Trader you know maybe 00:02:32.280 --> 00:02:34.670 align:start position:0% know I'm a bad Trader you know maybe automating<00:02:32.940> things<00:02:33.239> and<00:02:33.540> having<00:02:33.780> uh<00:02:34.440> you<00:02:34.620> know 00:02:34.670 --> 00:02:34.680 align:start position:0% automating things and having uh you know 00:02:34.680 --> 00:02:36.589 align:start position:0% automating things and having uh you know logic<00:02:35.099> do<00:02:35.280> it<00:02:35.459> for<00:02:35.580> me<00:02:35.760> is<00:02:35.940> probably<00:02:36.239> a<00:02:36.480> better 00:02:36.589 --> 00:02:36.599 align:start position:0% logic do it for me is probably a better 00:02:36.599 --> 00:02:37.910 align:start position:0% logic do it for me is probably a better idea 00:02:37.910 --> 00:02:37.920 align:start position:0% idea 00:02:37.920 --> 00:02:39.890 align:start position:0% idea um<00:02:38.040> so<00:02:38.280> that's<00:02:38.459> specific<00:02:38.879> to<00:02:39.120> D5<00:02:39.480> but<00:02:39.720> of 00:02:39.890 --> 00:02:39.900 align:start position:0% um so that's specific to D5 but of 00:02:39.900 --> 00:02:41.869 align:start position:0% um so that's specific to D5 but of course<00:02:40.080> there's<00:02:40.800> many<00:02:40.980> other<00:02:41.160> ways<00:02:41.580> that<00:02:41.700> you 00:02:41.869 --> 00:02:41.879 align:start position:0% course there's many other ways that you 00:02:41.879 --> 00:02:43.490 align:start position:0% course there's many other ways that you can<00:02:42.000> uh<00:02:42.420> take<00:02:42.599> what<00:02:42.840> we're<00:02:42.959> going<00:02:43.140> to<00:02:43.200> show<00:02:43.319> you 00:02:43.490 --> 00:02:43.500 align:start position:0% can uh take what we're going to show you 00:02:43.500 --> 00:02:45.410 align:start position:0% can uh take what we're going to show you and<00:02:43.860> use<00:02:43.980> it<00:02:44.160> you<00:02:44.340> know<00:02:44.459> across<00:02:44.879> anything 00:02:45.410 --> 00:02:45.420 align:start position:0% and use it you know across anything 00:02:45.420 --> 00:02:48.970 align:start position:0% and use it you know across anything that's<00:02:45.660> built<00:02:45.959> on<00:02:46.019> the<00:02:46.140> blockchain 00:02:48.970 --> 00:02:48.980 align:start position:0% 00:02:48.980 --> 00:02:51.650 align:start position:0% okay<00:02:49.980> so<00:02:50.519> we<00:02:50.879> want<00:02:51.000> to<00:02:51.120> start<00:02:51.239> with<00:02:51.420> everyone 00:02:51.650 --> 00:02:51.660 align:start position:0% okay so we want to start with everyone 00:02:51.660 --> 00:02:52.910 align:start position:0% okay so we want to start with everyone just<00:02:51.959> kind<00:02:52.140> of<00:02:52.260> talking<00:02:52.319> to<00:02:52.560> each<00:02:52.680> other<00:02:52.739> at 00:02:52.910 --> 00:02:52.920 align:start position:0% just kind of talking to each other at 00:02:52.920 --> 00:02:54.050 align:start position:0% just kind of talking to each other at their<00:02:53.040> tables 00:02:54.050 --> 00:02:54.060 align:start position:0% their tables 00:02:54.060 --> 00:02:55.490 align:start position:0% their tables um<00:02:54.180> you<00:02:54.420> know<00:02:54.540> you<00:02:54.720> could<00:02:54.840> get<00:02:55.140> to<00:02:55.260> know<00:02:55.379> each 00:02:55.490 --> 00:02:55.500 align:start position:0% um you know you could get to know each 00:02:55.500 --> 00:02:56.930 align:start position:0% um you know you could get to know each other<00:02:55.560> maybe<00:02:55.739> introduce<00:02:56.160> each<00:02:56.340> other<00:02:56.459> but 00:02:56.930 --> 00:02:56.940 align:start position:0% other maybe introduce each other but 00:02:56.940 --> 00:02:59.509 align:start position:0% other maybe introduce each other but here's<00:02:57.239> a<00:02:57.360> prompt<00:02:57.660> based<00:02:58.440> on<00:02:58.680> what<00:02:59.220> I<00:02:59.400> just 00:02:59.509 --> 00:02:59.519 align:start position:0% here's a prompt based on what I just 00:02:59.519 --> 00:03:02.390 align:start position:0% here's a prompt based on what I just showed<00:02:59.819> you<00:02:59.940> uh<00:03:00.660> you<00:03:00.900> know<00:03:00.959> from<00:03:01.140> myself<00:03:01.400> uh 00:03:02.390 --> 00:03:02.400 align:start position:0% showed you uh you know from myself uh 00:03:02.400 --> 00:03:03.710 align:start position:0% showed you uh you know from myself uh and<00:03:02.580> that's<00:03:02.700> a<00:03:02.940> time<00:03:03.120> when<00:03:03.300> things<00:03:03.540> didn't 00:03:03.710 --> 00:03:03.720 align:start position:0% and that's a time when things didn't 00:03:03.720 --> 00:03:05.390 align:start position:0% and that's a time when things didn't really<00:03:03.900> go<00:03:04.140> your<00:03:04.260> way<00:03:04.440> in<00:03:04.560> web<00:03:04.739> 3<00:03:04.920> so<00:03:05.220> that 00:03:05.390 --> 00:03:05.400 align:start position:0% really go your way in web 3 so that 00:03:05.400 --> 00:03:07.309 align:start position:0% really go your way in web 3 so that could<00:03:05.519> be<00:03:05.700> you<00:03:06.180> know<00:03:06.300> you<00:03:06.420> lost<00:03:06.599> money<00:03:06.840> trading 00:03:07.309 --> 00:03:07.319 align:start position:0% could be you know you lost money trading 00:03:07.319 --> 00:03:09.890 align:start position:0% could be you know you lost money trading derivatives<00:03:07.739> uh<00:03:08.640> you<00:03:08.819> know<00:03:08.879> not<00:03:09.000> in<00:03:09.180> web<00:03:09.360> 3<00:03:09.540> you 00:03:09.890 --> 00:03:09.900 align:start position:0% derivatives uh you know not in web 3 you 00:03:09.900 --> 00:03:11.809 align:start position:0% derivatives uh you know not in web 3 you can<00:03:10.019> talk<00:03:10.140> about<00:03:10.200> that<00:03:10.440> too<00:03:10.620> a<00:03:11.459> time<00:03:11.640> when 00:03:11.809 --> 00:03:11.819 align:start position:0% can talk about that too a time when 00:03:11.819 --> 00:03:13.430 align:start position:0% can talk about that too a time when maybe<00:03:12.060> you<00:03:12.360> suffered<00:03:12.720> a<00:03:12.840> lot<00:03:12.900> of<00:03:12.959> impermanent 00:03:13.430 --> 00:03:13.440 align:start position:0% maybe you suffered a lot of impermanent 00:03:13.440 --> 00:03:15.110 align:start position:0% maybe you suffered a lot of impermanent loss<00:03:13.739> or<00:03:14.040> you<00:03:14.220> can<00:03:14.340> you<00:03:14.519> can<00:03:14.640> say<00:03:14.760> good<00:03:14.940> things 00:03:15.110 --> 00:03:15.120 align:start position:0% loss or you can you can say good things 00:03:15.120 --> 00:03:17.570 align:start position:0% loss or you can you can say good things too<00:03:15.300> I<00:03:15.720> mean<00:03:16.319> um<00:03:16.440> or<00:03:16.920> a<00:03:17.099> time<00:03:17.220> when<00:03:17.340> you<00:03:17.459> should 00:03:17.570 --> 00:03:17.580 align:start position:0% too I mean um or a time when you should 00:03:17.580 --> 00:03:18.949 align:start position:0% too I mean um or a time when you should have<00:03:17.700> sold<00:03:17.819> the<00:03:18.000> nft<00:03:18.180> at<00:03:18.480> the<00:03:18.540> top<00:03:18.659> you<00:03:18.840> know 00:03:18.949 --> 00:03:18.959 align:start position:0% have sold the nft at the top you know 00:03:18.959 --> 00:03:20.390 align:start position:0% have sold the nft at the top you know that<00:03:19.080> kind<00:03:19.260> of<00:03:19.379> thing 00:03:20.390 --> 00:03:20.400 align:start position:0% that kind of thing 00:03:20.400 --> 00:03:22.550 align:start position:0% that kind of thing um<00:03:20.459> so<00:03:21.120> yeah<00:03:21.300> take<00:03:21.480> five<00:03:21.659> minutes<00:03:21.840> and<00:03:22.140> chat 00:03:22.550 --> 00:03:22.560 align:start position:0% um so yeah take five minutes and chat 00:03:22.560 --> 00:03:25.270 align:start position:0% um so yeah take five minutes and chat with<00:03:22.860> uh<00:03:23.280> the<00:03:23.519> folks<00:03:23.760> around<00:03:23.879> you 00:03:25.270 --> 00:03:25.280 align:start position:0% with uh the folks around you 00:03:25.280 --> 00:03:27.649 align:start position:0% with uh the folks around you so<00:03:26.280> we're<00:03:26.459> gonna<00:03:26.580> give<00:03:26.700> a<00:03:26.819> little<00:03:26.940> overview<00:03:27.420> of 00:03:27.649 --> 00:03:27.659 align:start position:0% so we're gonna give a little overview of 00:03:27.659 --> 00:03:30.649 align:start position:0% so we're gonna give a little overview of the<00:03:27.840> web<00:03:27.959> 3<00:03:28.260> data<00:03:28.680> stack<00:03:28.920> uh<00:03:29.640> there's<00:03:30.000> a<00:03:30.480> lot 00:03:30.649 --> 00:03:30.659 align:start position:0% the web 3 data stack uh there's a lot 00:03:30.659 --> 00:03:32.809 align:start position:0% the web 3 data stack uh there's a lot here<00:03:31.080> and<00:03:31.620> uh<00:03:31.860> we're<00:03:32.159> not<00:03:32.340> going<00:03:32.580> to<00:03:32.700> have 00:03:32.809 --> 00:03:32.819 align:start position:0% here and uh we're not going to have 00:03:32.819 --> 00:03:33.949 align:start position:0% here and uh we're not going to have everything 00:03:33.949 --> 00:03:33.959 align:start position:0% everything 00:03:33.959 --> 00:03:36.649 align:start position:0% everything um<00:03:34.019> so<00:03:34.319> absolutely<00:03:35.280> if<00:03:35.819> you're<00:03:36.000> a<00:03:36.300> you<00:03:36.480> know<00:03:36.540> a 00:03:36.649 --> 00:03:36.659 align:start position:0% um so absolutely if you're a you know a 00:03:36.659 --> 00:03:38.509 align:start position:0% um so absolutely if you're a you know a data<00:03:36.900> protocol<00:03:37.140> please<00:03:37.560> reach<00:03:37.920> out<00:03:38.040> maybe<00:03:38.280> we 00:03:38.509 --> 00:03:38.519 align:start position:0% data protocol please reach out maybe we 00:03:38.519 --> 00:03:40.729 align:start position:0% data protocol please reach out maybe we can<00:03:38.640> add<00:03:38.760> it<00:03:38.879> to<00:03:39.060> our<00:03:39.180> slides 00:03:40.729 --> 00:03:40.739 align:start position:0% can add it to our slides 00:03:40.739 --> 00:03:43.430 align:start position:0% can add it to our slides um so<00:03:41.280> we'll<00:03:41.519> start<00:03:41.760> with<00:03:42.299> this<00:03:42.780> nice<00:03:43.260> little 00:03:43.430 --> 00:03:43.440 align:start position:0% um so we'll start with this nice little 00:03:43.440 --> 00:03:46.970 align:start position:0% um so we'll start with this nice little visual<00:03:43.860> from<00:03:44.760> Andrew<00:03:45.120> Hong<00:03:45.599> on<00:03:46.080> Twitter 00:03:46.970 --> 00:03:46.980 align:start position:0% visual from Andrew Hong on Twitter 00:03:46.980 --> 00:03:49.009 align:start position:0% visual from Andrew Hong on Twitter um<00:03:47.040> this<00:03:47.220> was<00:03:47.280> made<00:03:47.459> about<00:03:47.760> eight<00:03:47.940> months<00:03:48.239> ago 00:03:49.009 --> 00:03:49.019 align:start position:0% um this was made about eight months ago 00:03:49.019 --> 00:03:51.770 align:start position:0% um this was made about eight months ago uh<00:03:49.620> and<00:03:49.739> so<00:03:49.920> here's<00:03:50.519> a<00:03:50.640> breakdown<00:03:51.000> of<00:03:51.239> a<00:03:51.480> lot<00:03:51.599> of 00:03:51.770 --> 00:03:51.780 align:start position:0% uh and so here's a breakdown of a lot of 00:03:51.780 --> 00:03:54.410 align:start position:0% uh and so here's a breakdown of a lot of the<00:03:52.080> different<00:03:52.260> sort<00:03:52.739> of<00:03:52.799> layers<00:03:53.519> of<00:03:53.879> of<00:03:54.060> the 00:03:54.410 --> 00:03:54.420 align:start position:0% the different sort of layers of of the 00:03:54.420 --> 00:03:57.350 align:start position:0% the different sort of layers of of the web3<00:03:54.900> data<00:03:55.260> stack<00:03:55.500> you<00:03:55.860> know<00:03:55.980> mostly<00:03:56.700> mostly 00:03:57.350 --> 00:03:57.360 align:start position:0% web3 data stack you know mostly mostly 00:03:57.360 --> 00:04:00.350 align:start position:0% web3 data stack you know mostly mostly relating<00:03:57.720> to<00:03:58.019> to<00:03:58.260> ethereum<00:03:58.799> and<00:03:59.519> evm<00:03:59.940> chains 00:04:00.350 --> 00:04:00.360 align:start position:0% relating to to ethereum and evm chains 00:04:00.360 --> 00:04:02.630 align:start position:0% relating to to ethereum and evm chains so<00:04:00.900> obviously<00:04:01.200> you<00:04:01.379> have<00:04:01.620> your<00:04:01.980> your<00:04:02.220> sort<00:04:02.580> of 00:04:02.630 --> 00:04:02.640 align:start position:0% so obviously you have your your sort of 00:04:02.640 --> 00:04:04.729 align:start position:0% so obviously you have your your sort of base<00:04:02.819> layer<00:04:03.239> uh<00:04:04.080> where<00:04:04.319> you're<00:04:04.500> actually 00:04:04.729 --> 00:04:04.739 align:start position:0% base layer uh where you're actually 00:04:04.739 --> 00:04:08.149 align:start position:0% base layer uh where you're actually running<00:04:05.099> clients<00:04:05.760> uh<00:04:06.480> interacting<00:04:07.019> with<00:04:07.440> uh 00:04:08.149 --> 00:04:08.159 align:start position:0% running clients uh interacting with uh 00:04:08.159 --> 00:04:09.649 align:start position:0% running clients uh interacting with uh you<00:04:08.280> know<00:04:08.340> the<00:04:08.459> ethereum<00:04:08.879> blockchain<00:04:09.420> state 00:04:09.649 --> 00:04:09.659 align:start position:0% you know the ethereum blockchain state 00:04:09.659 --> 00:04:13.309 align:start position:0% you know the ethereum blockchain state directly<00:04:10.140> reading<00:04:10.920> logs<00:04:11.400> uh<00:04:12.180> call<00:04:12.420> data<00:04:13.140> Etc 00:04:13.309 --> 00:04:13.319 align:start position:0% directly reading logs uh call data Etc 00:04:13.319 --> 00:04:15.470 align:start position:0% directly reading logs uh call data Etc uh<00:04:14.159> you<00:04:14.280> have<00:04:14.400> nodes<00:04:14.580> as<00:04:14.760> a<00:04:14.879> service<00:04:15.060> you<00:04:15.360> don't 00:04:15.470 --> 00:04:15.480 align:start position:0% uh you have nodes as a service you don't 00:04:15.480 --> 00:04:16.729 align:start position:0% uh you have nodes as a service you don't do<00:04:15.720> that<00:04:15.780> yourself<00:04:16.019> but<00:04:16.380> you're<00:04:16.560> still 00:04:16.729 --> 00:04:16.739 align:start position:0% do that yourself but you're still 00:04:16.739 --> 00:04:19.670 align:start position:0% do that yourself but you're still operating<00:04:17.400> on<00:04:17.699> those<00:04:18.000> sort<00:04:18.540> of<00:04:18.660> raw<00:04:19.320> data 00:04:19.670 --> 00:04:19.680 align:start position:0% operating on those sort of raw data 00:04:19.680 --> 00:04:20.750 align:start position:0% operating on those sort of raw data streams 00:04:20.750 --> 00:04:20.760 align:start position:0% streams 00:04:20.760 --> 00:04:22.969 align:start position:0% streams and<00:04:21.239> you<00:04:21.419> have<00:04:21.600> a<00:04:21.840> layer<00:04:22.199> on<00:04:22.320> top<00:04:22.500> of<00:04:22.620> that<00:04:22.740> you 00:04:22.969 --> 00:04:22.979 align:start position:0% and you have a layer on top of that you 00:04:22.979 --> 00:04:24.290 align:start position:0% and you have a layer on top of that you can<00:04:23.100> think<00:04:23.220> of<00:04:23.340> that<00:04:23.460> as<00:04:23.580> you<00:04:23.759> know<00:04:23.880> the<00:04:24.000> query 00:04:24.290 --> 00:04:24.300 align:start position:0% can think of that as you know the query 00:04:24.300 --> 00:04:26.270 align:start position:0% can think of that as you know the query and<00:04:24.540> data<00:04:25.139> mapping<00:04:25.380> layer<00:04:25.680> there's<00:04:26.100> a<00:04:26.280> little 00:04:26.270 --> 00:04:26.280 align:start position:0% and data mapping layer there's a little 00:04:26.280 --> 00:04:28.189 align:start position:0% and data mapping layer there's a little more<00:04:26.460> structure<00:04:26.880> there<00:04:27.180> often<00:04:27.960> these<00:04:28.139> things 00:04:28.189 --> 00:04:28.199 align:start position:0% more structure there often these things 00:04:28.199 --> 00:04:29.749 align:start position:0% more structure there often these things are<00:04:28.380> indexed 00:04:29.749 --> 00:04:29.759 align:start position:0% are indexed 00:04:29.759 --> 00:04:31.310 align:start position:0% are indexed um<00:04:29.820> you<00:04:30.120> know<00:04:30.180> they're<00:04:30.479> they're<00:04:31.320> um 00:04:31.310 --> 00:04:31.320 align:start position:0% um you know they're they're um 00:04:31.320 --> 00:04:33.650 align:start position:0% um you know they're they're um potentially<00:04:32.160> you<00:04:32.580> know<00:04:32.639> doing<00:04:32.820> analytics 00:04:33.650 --> 00:04:33.660 align:start position:0% potentially you know doing analytics 00:04:33.660 --> 00:04:37.189 align:start position:0% potentially you know doing analytics takes<00:04:34.280> uh<00:04:35.280> it<00:04:35.460> takes<00:04:35.699> your<00:04:35.880> abis<00:04:36.479> and<00:04:36.960> does 00:04:37.189 --> 00:04:37.199 align:start position:0% takes uh it takes your abis and does 00:04:37.199 --> 00:04:38.570 align:start position:0% takes uh it takes your abis and does some<00:04:37.380> contract<00:04:37.740> decoding<00:04:38.220> so<00:04:38.340> you<00:04:38.460> can 00:04:38.570 --> 00:04:38.580 align:start position:0% some contract decoding so you can 00:04:38.580 --> 00:04:41.210 align:start position:0% some contract decoding so you can actually<00:04:38.699> read<00:04:39.120> the<00:04:39.419> the<00:04:40.139> parameters<00:04:40.800> and<00:04:41.100> the 00:04:41.210 --> 00:04:41.220 align:start position:0% actually read the the parameters and the 00:04:41.220 --> 00:04:42.950 align:start position:0% actually read the the parameters and the function<00:04:41.699> names<00:04:41.940> instead<00:04:42.360> of<00:04:42.479> looking<00:04:42.600> at<00:04:42.780> a 00:04:42.950 --> 00:04:42.960 align:start position:0% function names instead of looking at a 00:04:42.960 --> 00:04:45.350 align:start position:0% function names instead of looking at a bunch<00:04:43.080> of<00:04:43.199> hex<00:04:43.919> codes 00:04:45.350 --> 00:04:45.360 align:start position:0% bunch of hex codes 00:04:45.360 --> 00:04:46.969 align:start position:0% bunch of hex codes um<00:04:45.419> there's<00:04:45.600> flip<00:04:45.840> side<00:04:45.960> and<00:04:46.199> the<00:04:46.320> graph<00:04:46.560> and 00:04:46.969 --> 00:04:46.979 align:start position:0% um there's flip side and the graph and 00:04:46.979 --> 00:04:49.610 align:start position:0% um there's flip side and the graph and everybody<00:04:47.280> knows<00:04:47.759> those 00:04:49.610 --> 00:04:49.620 align:start position:0% everybody knows those 00:04:49.620 --> 00:04:51.409 align:start position:0% everybody knows those um<00:04:49.740> there's<00:04:50.340> uh<00:04:50.580> then<00:04:50.759> there's<00:04:51.000> sort<00:04:51.180> of<00:04:51.300> that 00:04:51.409 --> 00:04:51.419 align:start position:0% um there's uh then there's sort of that 00:04:51.419 --> 00:04:52.909 align:start position:0% um there's uh then there's sort of that layer<00:04:51.780> on<00:04:51.900> top<00:04:52.139> and<00:04:52.440> this<00:04:52.560> obviously 00:04:52.909 --> 00:04:52.919 align:start position:0% layer on top and this obviously 00:04:52.919 --> 00:04:54.590 align:start position:0% layer on top and this obviously encompasses<00:04:53.280> a<00:04:53.460> lot<00:04:53.580> of<00:04:53.639> things<00:04:53.759> but<00:04:54.180> they're 00:04:54.590 --> 00:04:54.600 align:start position:0% encompasses a lot of things but they're 00:04:54.600 --> 00:04:56.930 align:start position:0% encompasses a lot of things but they're higher<00:04:54.960> touch<00:04:55.080> more<00:04:55.620> much<00:04:55.919> more<00:04:56.220> customized 00:04:56.930 --> 00:04:56.940 align:start position:0% higher touch more much more customized 00:04:56.940 --> 00:04:58.430 align:start position:0% higher touch more much more customized apis 00:04:58.430 --> 00:04:58.440 align:start position:0% apis 00:04:58.440 --> 00:05:00.110 align:start position:0% apis um<00:04:58.500> the<00:04:58.860> the<00:04:59.100> data<00:04:59.460> might<00:04:59.699> be<00:04:59.820> a<00:04:59.940> lot<00:05:00.000> more 00:05:00.110 --> 00:05:00.120 align:start position:0% um the the data might be a lot more 00:05:00.120 --> 00:05:02.330 align:start position:0% um the the data might be a lot more contextualized<00:05:00.960> and<00:05:01.139> a<00:05:01.259> lot<00:05:01.380> more<00:05:01.560> useful<00:05:01.919> for 00:05:02.330 --> 00:05:02.340 align:start position:0% contextualized and a lot more useful for 00:05:02.340 --> 00:05:05.090 align:start position:0% contextualized and a lot more useful for specific<00:05:02.639> applications<00:05:03.380> but<00:05:04.380> potentially<00:05:04.979> a 00:05:05.090 --> 00:05:05.100 align:start position:0% specific applications but potentially a 00:05:05.100 --> 00:05:06.590 align:start position:0% specific applications but potentially a little<00:05:05.220> more<00:05:05.400> obtuse 00:05:06.590 --> 00:05:06.600 align:start position:0% little more obtuse 00:05:06.600 --> 00:05:08.810 align:start position:0% little more obtuse um<00:05:06.720> some<00:05:06.900> apis<00:05:07.380> you<00:05:07.680> know<00:05:07.800> are<00:05:07.979> that<00:05:08.520> data 00:05:08.810 --> 00:05:08.820 align:start position:0% um some apis you know are that data 00:05:08.820 --> 00:05:09.770 align:start position:0% um some apis you know are that data processing<00:05:09.180> is<00:05:09.360> happening<00:05:09.540> in<00:05:09.660> the 00:05:09.770 --> 00:05:09.780 align:start position:0% processing is happening in the 00:05:09.780 --> 00:05:11.090 align:start position:0% processing is happening in the background<00:05:10.020> and<00:05:10.380> you<00:05:10.500> don't<00:05:10.680> necessarily 00:05:11.090 --> 00:05:11.100 align:start position:0% background and you don't necessarily 00:05:11.100 --> 00:05:11.810 align:start position:0% background and you don't necessarily know 00:05:11.810 --> 00:05:11.820 align:start position:0% know 00:05:11.820 --> 00:05:13.310 align:start position:0% know um<00:05:11.880> so<00:05:12.000> things<00:05:12.180> those<00:05:12.360> are<00:05:12.540> things<00:05:12.720> like<00:05:12.960> you 00:05:13.310 --> 00:05:13.320 align:start position:0% um so things those are things like you 00:05:13.320 --> 00:05:15.710 align:start position:0% um so things those are things like you know<00:05:13.440> covalent<00:05:13.919> etherscan<00:05:14.580> some<00:05:15.419> you<00:05:15.660> know 00:05:15.710 --> 00:05:15.720 align:start position:0% know covalent etherscan some you know 00:05:15.720 --> 00:05:17.749 align:start position:0% know covalent etherscan some you know manual<00:05:16.139> tagging<00:05:16.740> systems<00:05:17.220> like<00:05:17.520> through 00:05:17.749 --> 00:05:17.759 align:start position:0% manual tagging systems like through 00:05:17.759 --> 00:05:19.070 align:start position:0% manual tagging systems like through nanson 00:05:19.070 --> 00:05:19.080 align:start position:0% nanson 00:05:19.080 --> 00:05:21.290 align:start position:0% nanson uh<00:05:19.620> and<00:05:19.800> then<00:05:19.919> we<00:05:20.160> have<00:05:20.280> a<00:05:20.520> few<00:05:20.639> that<00:05:20.880> we<00:05:21.120> use 00:05:21.290 --> 00:05:21.300 align:start position:0% uh and then we have a few that we use 00:05:21.300 --> 00:05:23.570 align:start position:0% uh and then we have a few that we use pretty<00:05:21.720> regularly<00:05:22.199> so<00:05:22.620> we<00:05:22.979> wanted<00:05:23.280> to<00:05:23.460> make 00:05:23.570 --> 00:05:23.580 align:start position:0% pretty regularly so we wanted to make 00:05:23.580 --> 00:05:25.370 align:start position:0% pretty regularly so we wanted to make sure<00:05:23.699> they<00:05:23.880> made<00:05:24.000> it<00:05:24.120> on<00:05:24.300> there 00:05:25.370 --> 00:05:25.380 align:start position:0% sure they made it on there 00:05:25.380 --> 00:05:27.290 align:start position:0% sure they made it on there um<00:05:25.440> so<00:05:25.860> and<00:05:26.220> a<00:05:26.400> lot<00:05:26.520> has<00:05:26.639> changed<00:05:26.940> in<00:05:27.060> the<00:05:27.180> last 00:05:27.290 --> 00:05:27.300 align:start position:0% um so and a lot has changed in the last 00:05:27.300 --> 00:05:29.270 align:start position:0% um so and a lot has changed in the last eight<00:05:27.479> months<00:05:27.660> eight<00:05:27.900> months<00:05:28.440> so<00:05:28.800> people<00:05:29.100> know 00:05:29.270 --> 00:05:29.280 align:start position:0% eight months eight months so people know 00:05:29.280 --> 00:05:32.150 align:start position:0% eight months eight months so people know crypto<00:05:29.699> Stacks<00:05:30.180> uh<00:05:30.539> David<00:05:30.720> mihai 00:05:32.150 --> 00:05:32.160 align:start position:0% crypto Stacks uh David mihai 00:05:32.160 --> 00:05:34.730 align:start position:0% crypto Stacks uh David mihai um<00:05:32.280> they<00:05:32.699> run<00:05:33.000> like<00:05:33.180> crypto<00:05:33.539> fees<00:05:33.840> and<00:05:34.020> L2<00:05:34.380> fees 00:05:34.730 --> 00:05:34.740 align:start position:0% um they run like crypto fees and L2 fees 00:05:34.740 --> 00:05:36.469 align:start position:0% um they run like crypto fees and L2 fees and<00:05:34.919> all<00:05:35.160> of<00:05:35.280> those<00:05:35.460> different<00:05:35.759> front<00:05:36.060> ends 00:05:36.469 --> 00:05:36.479 align:start position:0% and all of those different front ends 00:05:36.479 --> 00:05:38.450 align:start position:0% and all of those different front ends they<00:05:36.780> built<00:05:37.139> a<00:05:37.199> little<00:05:37.320> you<00:05:37.740> know<00:05:37.860> data 00:05:38.450 --> 00:05:38.460 align:start position:0% they built a little you know data 00:05:38.460 --> 00:05:39.650 align:start position:0% they built a little you know data processing 00:05:39.650 --> 00:05:39.660 align:start position:0% processing 00:05:39.660 --> 00:05:41.390 align:start position:0% processing um<00:05:39.720> stack<00:05:40.500> to<00:05:40.740> make<00:05:40.860> it<00:05:40.979> easier<00:05:41.160> to<00:05:41.280> build 00:05:41.390 --> 00:05:41.400 align:start position:0% um stack to make it easier to build 00:05:41.400 --> 00:05:43.850 align:start position:0% um stack to make it easier to build front<00:05:41.580> ends<00:05:41.940> with<00:05:42.180> uh<00:05:42.360> with<00:05:42.600> subgraph<00:05:42.960> data<00:05:43.380> uh 00:05:43.850 --> 00:05:43.860 align:start position:0% front ends with uh with subgraph data uh 00:05:43.860 --> 00:05:45.469 align:start position:0% front ends with uh with subgraph data uh the<00:05:43.979> Dune<00:05:44.220> is<00:05:44.340> releasing<00:05:44.639> their<00:05:44.820> API<00:05:45.240> we 00:05:45.469 --> 00:05:45.479 align:start position:0% the Dune is releasing their API we 00:05:45.479 --> 00:05:47.270 align:start position:0% the Dune is releasing their API we mentioned<00:05:45.720> the<00:05:45.840> Dune<00:05:46.139> but<00:05:46.320> API<00:05:46.919> changes 00:05:47.270 --> 00:05:47.280 align:start position:0% mentioned the Dune but API changes 00:05:47.280 --> 00:05:49.129 align:start position:0% mentioned the Dune but API changes things<00:05:47.460> pretty<00:05:47.759> significantly<00:05:48.300> uh<00:05:48.840> we<00:05:49.020> use 00:05:49.129 --> 00:05:49.139 align:start position:0% things pretty significantly uh we use 00:05:49.139 --> 00:05:52.969 align:start position:0% things pretty significantly uh we use the<00:05:49.380> massari<00:05:50.120> standardized<00:05:51.120> D5<00:05:51.840> subgraphs<00:05:52.620> uh 00:05:52.969 --> 00:05:52.979 align:start position:0% the massari standardized D5 subgraphs uh 00:05:52.979 --> 00:05:55.129 align:start position:0% the massari standardized D5 subgraphs uh pretty<00:05:53.100> much<00:05:53.220> on<00:05:53.460> a<00:05:53.580> daily<00:05:53.699> basis 00:05:55.129 --> 00:05:55.139 align:start position:0% pretty much on a daily basis 00:05:55.139 --> 00:05:56.270 align:start position:0% pretty much on a daily basis um<00:05:55.199> they've<00:05:55.500> created<00:05:55.680> you<00:05:55.860> know<00:05:55.979> an<00:05:56.100> open 00:05:56.270 --> 00:05:56.280 align:start position:0% um they've created you know an open 00:05:56.280 --> 00:05:59.689 align:start position:0% um they've created you know an open standard<00:05:56.820> for<00:05:57.120> different<00:05:57.479> kinds<00:05:58.020> of<00:05:58.380> uh<00:05:58.740> of<00:05:59.460> uh 00:05:59.689 --> 00:05:59.699 align:start position:0% standard for different kinds of uh of uh 00:05:59.699 --> 00:06:01.390 align:start position:0% standard for different kinds of uh of uh D5<00:06:00.120> Primitives 00:06:01.390 --> 00:06:01.400 align:start position:0% D5 Primitives 00:06:01.400 --> 00:06:04.070 align:start position:0% D5 Primitives across<00:06:02.400> chains<00:06:02.820> uh<00:06:03.419> if<00:06:03.600> you<00:06:03.660> want<00:06:03.840> a<00:06:03.960> little 00:06:04.070 --> 00:06:04.080 align:start position:0% across chains uh if you want a little 00:06:04.080 --> 00:06:06.469 align:start position:0% across chains uh if you want a little more<00:06:04.199> control<00:06:04.500> ethl<00:06:05.460> and<00:06:05.580> true<00:06:05.759> blocks<00:06:06.240> are 00:06:06.469 --> 00:06:06.479 align:start position:0% more control ethl and true blocks are 00:06:06.479 --> 00:06:08.689 align:start position:0% more control ethl and true blocks are are<00:06:06.660> pretty<00:06:06.840> great<00:06:07.020> they're<00:06:07.500> both<00:06:07.919> you<00:06:08.580> know 00:06:08.689 --> 00:06:08.699 align:start position:0% are pretty great they're both you know 00:06:08.699 --> 00:06:12.350 align:start position:0% are pretty great they're both you know open<00:06:08.880> tools<00:06:09.360> allowing<00:06:10.259> you<00:06:10.380> to<00:06:11.000> index<00:06:12.000> your 00:06:12.350 --> 00:06:12.360 align:start position:0% open tools allowing you to index your 00:06:12.360 --> 00:06:15.529 align:start position:0% open tools allowing you to index your own<00:06:12.539> index<00:06:13.259> from<00:06:13.440> your<00:06:13.560> own<00:06:13.680> node<00:06:14.240> and<00:06:15.240> even 00:06:15.529 --> 00:06:15.539 align:start position:0% own index from your own node and even 00:06:15.539 --> 00:06:19.010 align:start position:0% own index from your own node and even the<00:06:15.780> ectl<00:06:16.440> data<00:06:17.340> is<00:06:17.460> available<00:06:17.639> in 00:06:19.010 --> 00:06:19.020 align:start position:0% the ectl data is available in 00:06:19.020 --> 00:06:20.870 align:start position:0% the ectl data is available in uh<00:06:19.500> in<00:06:19.680> a<00:06:19.800> bigquery<00:06:20.160> database<00:06:20.460> you<00:06:20.759> don't 00:06:20.870 --> 00:06:20.880 align:start position:0% uh in a bigquery database you don't 00:06:20.880 --> 00:06:23.270 align:start position:0% uh in a bigquery database you don't actually<00:06:21.000> have<00:06:21.180> to<00:06:21.300> do<00:06:21.419> your<00:06:21.600> own<00:06:21.840> uh<00:06:22.620> your<00:06:23.160> own 00:06:23.270 --> 00:06:23.280 align:start position:0% actually have to do your own uh your own 00:06:23.280 --> 00:06:25.670 align:start position:0% actually have to do your own uh your own indexing<00:06:23.940> if<00:06:24.060> you<00:06:24.180> don't<00:06:24.300> want<00:06:24.419> to<00:06:24.539> uh<00:06:25.199> D5 00:06:25.670 --> 00:06:25.680 align:start position:0% indexing if you don't want to uh D5 00:06:25.680 --> 00:06:28.909 align:start position:0% indexing if you don't want to uh D5 llama<00:06:26.039> uh<00:06:26.880> you<00:06:27.060> know<00:06:27.180> they<00:06:27.300> pump<00:06:27.720> out<00:06:27.900> a<00:06:28.319> ton<00:06:28.500> of 00:06:28.909 --> 00:06:28.919 align:start position:0% llama uh you know they pump out a ton of 00:06:28.919 --> 00:06:32.510 align:start position:0% llama uh you know they pump out a ton of new<00:06:29.460> apis<00:06:29.940> and<00:06:30.539> new<00:06:30.900> protocols<00:06:31.440> uh<00:06:32.100> their 00:06:32.510 --> 00:06:32.520 align:start position:0% new apis and new protocols uh their 00:06:32.520 --> 00:06:34.850 align:start position:0% new apis and new protocols uh their adapters<00:06:33.120> are<00:06:33.360> a<00:06:33.479> pretty<00:06:33.600> cool<00:06:33.780> system<00:06:34.020> and 00:06:34.850 --> 00:06:34.860 align:start position:0% adapters are a pretty cool system and 00:06:34.860 --> 00:06:36.830 align:start position:0% adapters are a pretty cool system and then<00:06:34.979> we<00:06:35.340> have<00:06:35.460> another<00:06:35.580> one<00:06:35.759> spec 00:06:36.830 --> 00:06:36.840 align:start position:0% then we have another one spec 00:06:36.840 --> 00:06:40.730 align:start position:0% then we have another one spec um<00:06:36.960> they're<00:06:37.440> uh<00:06:37.759> they<00:06:38.759> do<00:06:39.139> allow<00:06:40.139> you<00:06:40.259> to<00:06:40.380> sync 00:06:40.730 --> 00:06:40.740 align:start position:0% um they're uh they do allow you to sync 00:06:40.740 --> 00:06:43.730 align:start position:0% um they're uh they do allow you to sync your<00:06:41.039> own<00:06:41.160> postgres<00:06:41.580> database<00:06:42.120> uh<00:06:42.840> with<00:06:43.199> uh 00:06:43.730 --> 00:06:43.740 align:start position:0% your own postgres database uh with uh 00:06:43.740 --> 00:06:45.950 align:start position:0% your own postgres database uh with uh you<00:06:43.860> know<00:06:43.979> typescript<00:06:44.759> Transformers<00:06:45.419> uh 00:06:45.950 --> 00:06:45.960 align:start position:0% you know typescript Transformers uh 00:06:45.960 --> 00:06:48.050 align:start position:0% you know typescript Transformers uh bringing<00:06:46.259> in<00:06:46.380> call<00:06:46.560> data<00:06:46.979> or<00:06:47.280> sorry<00:06:47.520> bringing 00:06:48.050 --> 00:06:48.060 align:start position:0% bringing in call data or sorry bringing 00:06:48.060 --> 00:06:49.370 align:start position:0% bringing in call data or sorry bringing in<00:06:48.600> um 00:06:49.370 --> 00:06:49.380 align:start position:0% in um 00:06:49.380 --> 00:06:52.129 align:start position:0% in um uh<00:06:50.100> you<00:06:50.280> know<00:06:50.340> transaction<00:06:50.699> data<00:06:51.240> uh<00:06:51.780> indexing 00:06:52.129 --> 00:06:52.139 align:start position:0% uh you know transaction data uh indexing 00:06:52.139 --> 00:06:53.330 align:start position:0% uh you know transaction data uh indexing it<00:06:52.259> and<00:06:52.440> then<00:06:52.500> bringing<00:06:52.800> it<00:06:52.860> into<00:06:52.979> your<00:06:53.220> own 00:06:53.330 --> 00:06:53.340 align:start position:0% it and then bringing it into your own 00:06:53.340 --> 00:06:55.550 align:start position:0% it and then bringing it into your own postgres<00:06:53.819> database<00:06:54.300> to<00:06:54.780> live<00:06:55.139> beside<00:06:55.440> your 00:06:55.550 --> 00:06:55.560 align:start position:0% postgres database to live beside your 00:06:55.560 --> 00:06:58.809 align:start position:0% postgres database to live beside your own<00:06:55.740> data 00:06:58.809 --> 00:06:58.819 align:start position:0% 00:06:58.819 --> 00:07:01.670 align:start position:0% cool<00:06:59.819> so<00:07:00.300> this<00:07:00.660> is<00:07:00.780> the<00:07:01.020> process<00:07:01.319> as<00:07:01.500> I 00:07:01.670 --> 00:07:01.680 align:start position:0% cool so this is the process as I 00:07:01.680 --> 00:07:02.450 align:start position:0% cool so this is the process as I mentioned<00:07:01.860> that<00:07:01.979> we're<00:07:02.100> going<00:07:02.220> to<00:07:02.280> be<00:07:02.340> going 00:07:02.450 --> 00:07:02.460 align:start position:0% mentioned that we're going to be going 00:07:02.460 --> 00:07:03.290 align:start position:0% mentioned that we're going to be going through 00:07:03.290 --> 00:07:03.300 align:start position:0% through 00:07:03.300 --> 00:07:04.969 align:start position:0% through um<00:07:03.360> so<00:07:03.660> first<00:07:04.259> thing<00:07:04.440> we're<00:07:04.620> going<00:07:04.740> to<00:07:04.800> do<00:07:04.919> is 00:07:04.969 --> 00:07:04.979 align:start position:0% um so first thing we're going to do is 00:07:04.979 --> 00:07:07.189 align:start position:0% um so first thing we're going to do is we're<00:07:05.160> going<00:07:05.220> to<00:07:05.280> do<00:07:05.400> data<00:07:05.759> fetching<00:07:06.120> and<00:07:06.900> for 00:07:07.189 --> 00:07:07.199 align:start position:0% we're going to do data fetching and for 00:07:07.199 --> 00:07:08.270 align:start position:0% we're going to do data fetching and for each<00:07:07.380> of<00:07:07.440> these<00:07:07.620> sections<00:07:07.919> we're<00:07:08.039> going<00:07:08.220> to 00:07:08.270 --> 00:07:08.280 align:start position:0% each of these sections we're going to 00:07:08.280 --> 00:07:10.189 align:start position:0% each of these sections we're going to talk<00:07:08.460> about 00:07:10.189 --> 00:07:10.199 align:start position:0% talk about 00:07:10.199 --> 00:07:11.990 align:start position:0% talk about um the<00:07:10.919> alternatives<00:07:11.280> to<00:07:11.520> what<00:07:11.699> we're<00:07:11.819> doing 00:07:11.990 --> 00:07:12.000 align:start position:0% um the alternatives to what we're doing 00:07:12.000 --> 00:07:13.249 align:start position:0% um the alternatives to what we're doing so<00:07:12.240> to<00:07:12.419> give<00:07:12.539> you<00:07:12.660> like<00:07:12.780> a<00:07:12.960> little<00:07:13.020> bit<00:07:13.139> of 00:07:13.249 --> 00:07:13.259 align:start position:0% so to give you like a little bit of 00:07:13.259 --> 00:07:14.749 align:start position:0% so to give you like a little bit of flavor<00:07:13.860> um<00:07:13.860> so<00:07:14.039> you're<00:07:14.160> not<00:07:14.280> stuck<00:07:14.460> with<00:07:14.639> with 00:07:14.749 --> 00:07:14.759 align:start position:0% flavor um so you're not stuck with with 00:07:14.759 --> 00:07:18.950 align:start position:0% flavor um so you're not stuck with with with<00:07:15.000> uh<00:07:15.900> one<00:07:16.139> thing<00:07:16.460> uh<00:07:17.460> and<00:07:18.060> uh<00:07:18.539> then<00:07:18.780> we'll 00:07:18.950 --> 00:07:18.960 align:start position:0% with uh one thing uh and uh then we'll 00:07:18.960 --> 00:07:20.570 align:start position:0% with uh one thing uh and uh then we'll give<00:07:19.139> we'll<00:07:19.620> run<00:07:19.740> through<00:07:19.919> the<00:07:20.099> example<00:07:20.340> that 00:07:20.570 --> 00:07:20.580 align:start position:0% give we'll run through the example that 00:07:20.580 --> 00:07:22.189 align:start position:0% give we'll run through the example that we<00:07:20.699> actually<00:07:20.759> did 00:07:22.189 --> 00:07:22.199 align:start position:0% we actually did 00:07:22.199 --> 00:07:23.390 align:start position:0% we actually did um but<00:07:22.319> yeah<00:07:22.440> just<00:07:22.620> an<00:07:22.740> overview<00:07:22.979> of<00:07:23.099> data 00:07:23.390 --> 00:07:23.400 align:start position:0% um but yeah just an overview of data 00:07:23.400 --> 00:07:25.070 align:start position:0% um but yeah just an overview of data fetching<00:07:23.759> processing<00:07:24.180> modeling<00:07:24.599> transaction 00:07:25.070 --> 00:07:25.080 align:start position:0% fetching processing modeling transaction 00:07:25.080 --> 00:07:26.990 align:start position:0% fetching processing modeling transaction execution 00:07:26.990 --> 00:07:27.000 align:start position:0% execution 00:07:27.000 --> 00:07:30.230 align:start position:0% execution so<00:07:27.660> our<00:07:27.900> example<00:07:28.380> is<00:07:29.160> using<00:07:29.460> python<00:07:29.940> to 00:07:30.230 --> 00:07:30.240 align:start position:0% so our example is using python to 00:07:30.240 --> 00:07:32.029 align:start position:0% so our example is using python to collect<00:07:30.539> data<00:07:30.960> and<00:07:31.560> write<00:07:31.740> a<00:07:31.860> simple 00:07:32.029 --> 00:07:32.039 align:start position:0% collect data and write a simple 00:07:32.039 --> 00:07:34.129 align:start position:0% collect data and write a simple prediction<00:07:32.400> model 00:07:34.129 --> 00:07:34.139 align:start position:0% prediction model 00:07:34.139 --> 00:07:36.830 align:start position:0% prediction model um<00:07:34.460> so<00:07:35.460> yeah<00:07:35.639> the<00:07:35.940> three<00:07:36.060> steps<00:07:36.419> are<00:07:36.539> pulling 00:07:36.830 --> 00:07:36.840 align:start position:0% um so yeah the three steps are pulling 00:07:36.840 --> 00:07:38.629 align:start position:0% um so yeah the three steps are pulling each<00:07:37.020> price<00:07:37.259> data<00:07:37.620> from<00:07:37.800> the<00:07:37.860> graph<00:07:38.039> in<00:07:38.280> Dune 00:07:38.629 --> 00:07:38.639 align:start position:0% each price data from the graph in Dune 00:07:38.639 --> 00:07:41.089 align:start position:0% each price data from the graph in Dune uh<00:07:39.240> just<00:07:39.419> to<00:07:39.539> have<00:07:39.720> kind<00:07:40.020> of<00:07:40.080> two<00:07:40.259> data<00:07:40.620> sets<00:07:40.860> to 00:07:41.089 --> 00:07:41.099 align:start position:0% uh just to have kind of two data sets to 00:07:41.099 --> 00:07:42.710 align:start position:0% uh just to have kind of two data sets to to<00:07:41.340> compare<00:07:41.699> and<00:07:41.880> to<00:07:42.000> show<00:07:42.120> you<00:07:42.240> you<00:07:42.419> know<00:07:42.539> two 00:07:42.710 --> 00:07:42.720 align:start position:0% to compare and to show you you know two 00:07:42.720 --> 00:07:44.510 align:start position:0% to compare and to show you you know two different<00:07:42.840> ways<00:07:43.139> that<00:07:43.199> you<00:07:43.319> can<00:07:43.380> do<00:07:43.560> it<00:07:43.680> and 00:07:44.510 --> 00:07:44.520 align:start position:0% different ways that you can do it and 00:07:44.520 --> 00:07:46.670 align:start position:0% different ways that you can do it and then<00:07:44.639> using<00:07:45.120> a<00:07:45.539> auto<00:07:45.840> regressive<00:07:46.380> moving 00:07:46.670 --> 00:07:46.680 align:start position:0% then using a auto regressive moving 00:07:46.680 --> 00:07:48.830 align:start position:0% then using a auto regressive moving average<00:07:46.919> uh<00:07:47.699> model<00:07:47.880> to<00:07:48.300> predict<00:07:48.599> price 00:07:48.830 --> 00:07:48.840 align:start position:0% average uh model to predict price 00:07:48.840 --> 00:07:50.210 align:start position:0% average uh model to predict price movement 00:07:50.210 --> 00:07:50.220 align:start position:0% movement 00:07:50.220 --> 00:07:51.290 align:start position:0% movement um 00:07:51.290 --> 00:07:51.300 align:start position:0% um 00:07:51.300 --> 00:07:54.050 align:start position:0% um I<00:07:51.780> wouldn't<00:07:51.900> use<00:07:52.259> that<00:07:52.680> uh<00:07:53.340> Approach<00:07:53.759> at<00:07:53.880> home 00:07:54.050 --> 00:07:54.060 align:start position:0% I wouldn't use that uh Approach at home 00:07:54.060 --> 00:07:56.150 align:start position:0% I wouldn't use that uh Approach at home uh<00:07:54.720> but<00:07:54.900> you<00:07:55.259> know<00:07:55.319> for<00:07:55.500> the<00:07:55.620> for<00:07:55.979> this 00:07:56.150 --> 00:07:56.160 align:start position:0% uh but you know for the for this 00:07:56.160 --> 00:07:57.950 align:start position:0% uh but you know for the for this presentation<00:07:56.520> it<00:07:56.759> works 00:07:57.950 --> 00:07:57.960 align:start position:0% presentation it works 00:07:57.960 --> 00:08:00.890 align:start position:0% presentation it works um<00:07:58.020> basically<00:07:58.680> if<00:07:58.860> price<00:07:59.099> go<00:07:59.400> up<00:07:59.580> uh<00:08:00.060> swap<00:08:00.360> usdc 00:08:00.890 --> 00:08:00.900 align:start position:0% um basically if price go up uh swap usdc 00:08:00.900 --> 00:08:02.870 align:start position:0% um basically if price go up uh swap usdc to<00:08:01.139> eth<00:08:01.440> on<00:08:01.620> unit<00:08:01.800> swap<00:08:02.220> that's<00:08:02.699> the 00:08:02.870 --> 00:08:02.880 align:start position:0% to eth on unit swap that's the 00:08:02.880 --> 00:08:04.850 align:start position:0% to eth on unit swap that's the transaction<00:08:03.300> that<00:08:03.660> will<00:08:03.860> automatically 00:08:04.850 --> 00:08:04.860 align:start position:0% transaction that will automatically 00:08:04.860 --> 00:08:06.710 align:start position:0% transaction that will automatically happen<00:08:05.099> obviously<00:08:06.000> this<00:08:06.180> was<00:08:06.360> built 00:08:06.710 --> 00:08:06.720 align:start position:0% happen obviously this was built 00:08:06.720 --> 00:08:08.689 align:start position:0% happen obviously this was built originally<00:08:07.440> as<00:08:07.620> a<00:08:07.740> code<00:08:07.860> along<00:08:08.039> so<00:08:08.400> we<00:08:08.520> tried 00:08:08.689 --> 00:08:08.699 align:start position:0% originally as a code along so we tried 00:08:08.699 --> 00:08:11.629 align:start position:0% originally as a code along so we tried to<00:08:08.759> keep<00:08:08.940> it<00:08:09.060> as<00:08:09.180> simple<00:08:09.360> as<00:08:09.539> possible<00:08:10.039> uh<00:08:11.039> a 00:08:11.629 --> 00:08:11.639 align:start position:0% to keep it as simple as possible uh a 00:08:11.639 --> 00:08:13.249 align:start position:0% to keep it as simple as possible uh a lot<00:08:11.699> of<00:08:11.819> this<00:08:11.940> can<00:08:12.180> be<00:08:12.300> expanded<00:08:12.780> on<00:08:12.960> pretty 00:08:13.249 --> 00:08:13.259 align:start position:0% lot of this can be expanded on pretty 00:08:13.259 --> 00:08:15.589 align:start position:0% lot of this can be expanded on pretty pretty<00:08:13.560> thoroughly 00:08:15.589 --> 00:08:15.599 align:start position:0% pretty thoroughly 00:08:15.599 --> 00:08:18.290 align:start position:0% pretty thoroughly definition 00:08:18.290 --> 00:08:18.300 align:start position:0% definition 00:08:18.300 --> 00:08:20.330 align:start position:0% definition so<00:08:18.960> obviously<00:08:19.379> we<00:08:19.500> went<00:08:19.680> over<00:08:19.860> that<00:08:20.039> data 00:08:20.330 --> 00:08:20.340 align:start position:0% so obviously we went over that data 00:08:20.340 --> 00:08:23.390 align:start position:0% so obviously we went over that data stack<00:08:20.580> and<00:08:20.819> there's<00:08:21.060> there's<00:08:21.599> so<00:08:22.139> much<00:08:22.319> there 00:08:23.390 --> 00:08:23.400 align:start position:0% stack and there's there's so much there 00:08:23.400 --> 00:08:24.890 align:start position:0% stack and there's there's so much there um<00:08:23.520> so<00:08:23.759> many<00:08:23.819> different<00:08:24.000> choices<00:08:24.419> to<00:08:24.660> be<00:08:24.780> made 00:08:24.890 --> 00:08:24.900 align:start position:0% um so many different choices to be made 00:08:24.900 --> 00:08:27.110 align:start position:0% um so many different choices to be made and<00:08:25.199> like<00:08:25.379> any<00:08:25.620> other<00:08:25.919> choice<00:08:26.280> you're<00:08:26.699> making 00:08:27.110 --> 00:08:27.120 align:start position:0% and like any other choice you're making 00:08:27.120 --> 00:08:28.730 align:start position:0% and like any other choice you're making when<00:08:27.360> building<00:08:27.539> a<00:08:27.780> product<00:08:27.900> it's<00:08:28.440> mostly 00:08:28.730 --> 00:08:28.740 align:start position:0% when building a product it's mostly 00:08:28.740 --> 00:08:31.070 align:start position:0% when building a product it's mostly about<00:08:28.919> trade-offs<00:08:29.580> uh<00:08:30.240> engineering<00:08:30.660> choices 00:08:31.070 --> 00:08:31.080 align:start position:0% about trade-offs uh engineering choices 00:08:31.080 --> 00:08:33.350 align:start position:0% about trade-offs uh engineering choices so<00:08:31.680> we<00:08:32.039> we<00:08:32.339> wanted<00:08:32.700> to<00:08:32.880> talk<00:08:33.000> about<00:08:33.120> some 00:08:33.350 --> 00:08:33.360 align:start position:0% so we we wanted to talk about some 00:08:33.360 --> 00:08:35.690 align:start position:0% so we we wanted to talk about some considerations<00:08:33.839> to<00:08:34.200> keep<00:08:34.440> in<00:08:34.560> mind<00:08:34.740> uh<00:08:35.459> there 00:08:35.690 --> 00:08:35.700 align:start position:0% considerations to keep in mind uh there 00:08:35.700 --> 00:08:38.209 align:start position:0% considerations to keep in mind uh there are<00:08:35.820> definitely<00:08:36.060> others<00:08:36.560> but<00:08:37.560> some<00:08:37.860> big<00:08:38.039> ones 00:08:38.209 --> 00:08:38.219 align:start position:0% are definitely others but some big ones 00:08:38.219 --> 00:08:39.589 align:start position:0% are definitely others but some big ones are<00:08:38.399> available<00:08:38.580> Fields<00:08:39.120> so<00:08:39.300> they<00:08:39.479> actually 00:08:39.589 --> 00:08:39.599 align:start position:0% are available Fields so they actually 00:08:39.599 --> 00:08:41.630 align:start position:0% are available Fields so they actually have<00:08:39.839> the<00:08:40.020> information<00:08:40.140> that<00:08:40.860> you<00:08:40.979> need<00:08:41.159> to 00:08:41.630 --> 00:08:41.640 align:start position:0% have the information that you need to 00:08:41.640 --> 00:08:44.149 align:start position:0% have the information that you need to use<00:08:41.880> uh<00:08:42.599> the<00:08:42.779> data<00:08:43.080> format<00:08:43.380> are<00:08:43.740> going<00:08:43.919> to<00:08:44.039> have 00:08:44.149 --> 00:08:44.159 align:start position:0% use uh the data format are going to have 00:08:44.159 --> 00:08:46.610 align:start position:0% use uh the data format are going to have to<00:08:44.279> Wrangle<00:08:44.700> all<00:08:44.820> this<00:08:45.000> data<00:08:45.360> to<00:08:46.020> to<00:08:46.260> get<00:08:46.500> it 00:08:46.610 --> 00:08:46.620 align:start position:0% to Wrangle all this data to to get it 00:08:46.620 --> 00:08:49.009 align:start position:0% to Wrangle all this data to to get it have<00:08:46.860> it<00:08:47.040> usable<00:08:47.519> in<00:08:47.700> your<00:08:47.880> automations 00:08:49.009 --> 00:08:49.019 align:start position:0% have it usable in your automations 00:08:49.019 --> 00:08:50.870 align:start position:0% have it usable in your automations um<00:08:49.080> scope<00:08:49.500> does<00:08:49.920> it<00:08:50.040> cover<00:08:50.220> the<00:08:50.459> chains<00:08:50.760> and 00:08:50.870 --> 00:08:50.880 align:start position:0% um scope does it cover the chains and 00:08:50.880 --> 00:08:53.150 align:start position:0% um scope does it cover the chains and protocols<00:08:51.360> that<00:08:51.480> you<00:08:51.600> want<00:08:51.720> to<00:08:51.899> use<00:08:52.080> are<00:08:53.040> you 00:08:53.150 --> 00:08:53.160 align:start position:0% protocols that you want to use are you 00:08:53.160 --> 00:08:55.190 align:start position:0% protocols that you want to use are you going<00:08:53.279> to<00:08:53.459> have<00:08:53.580> to<00:08:53.700> you<00:08:54.180> know<00:08:54.240> merge 00:08:55.190 --> 00:08:55.200 align:start position:0% going to have to you know merge 00:08:55.200 --> 00:08:56.810 align:start position:0% going to have to you know merge different<00:08:55.440> data<00:08:55.920> streams<00:08:56.160> in<00:08:56.339> order<00:08:56.459> to<00:08:56.640> get 00:08:56.810 --> 00:08:56.820 align:start position:0% different data streams in order to get 00:08:56.820 --> 00:08:59.329 align:start position:0% different data streams in order to get information<00:08:57.660> from<00:08:58.200> Cross<00:08:58.380> chain<00:08:58.680> cross<00:08:59.040> cross 00:08:59.329 --> 00:08:59.339 align:start position:0% information from Cross chain cross cross 00:08:59.339 --> 00:09:00.530 align:start position:0% information from Cross chain cross cross protocol 00:09:00.530 --> 00:09:00.540 align:start position:0% protocol 00:09:00.540 --> 00:09:03.410 align:start position:0% protocol um<00:09:00.600> is<00:09:00.779> it<00:09:00.899> event<00:09:01.019> driven<00:09:01.440> or<00:09:01.680> is<00:09:01.800> it<00:09:01.920> pulled<00:09:02.420> uh 00:09:03.410 --> 00:09:03.420 align:start position:0% um is it event driven or is it pulled uh 00:09:03.420 --> 00:09:05.210 align:start position:0% um is it event driven or is it pulled uh you<00:09:03.600> know<00:09:03.660> flexibility<00:09:04.200> can<00:09:04.560> you<00:09:04.680> extend<00:09:04.980> the 00:09:05.210 --> 00:09:05.220 align:start position:0% you know flexibility can you extend the 00:09:05.220 --> 00:09:07.730 align:start position:0% you know flexibility can you extend the model<00:09:05.420> uh<00:09:06.420> stability<00:09:06.839> are<00:09:07.320> they<00:09:07.440> going<00:09:07.560> to 00:09:07.730 --> 00:09:07.740 align:start position:0% model uh stability are they going to 00:09:07.740 --> 00:09:09.949 align:start position:0% model uh stability are they going to change<00:09:07.920> their<00:09:08.339> interface<00:09:08.820> on<00:09:09.060> you<00:09:09.240> while 00:09:09.949 --> 00:09:09.959 align:start position:0% change their interface on you while 00:09:09.959 --> 00:09:11.329 align:start position:0% change their interface on you while you're<00:09:10.200> running<00:09:10.320> your<00:09:10.560> automations<00:09:10.980> and 00:09:11.329 --> 00:09:11.339 align:start position:0% you're running your automations and 00:09:11.339 --> 00:09:13.790 align:start position:0% you're running your automations and break<00:09:11.519> everything<00:09:12.200> because<00:09:13.200> for<00:09:13.500> some<00:09:13.620> reason 00:09:13.790 --> 00:09:13.800 align:start position:0% break everything because for some reason 00:09:13.800 --> 00:09:16.970 align:start position:0% break everything because for some reason we<00:09:14.160> still<00:09:14.279> don't<00:09:14.459> Version<00:09:14.820> Control<00:09:15.300> apis<00:09:16.140> uh 00:09:16.970 --> 00:09:16.980 align:start position:0% we still don't Version Control apis uh 00:09:16.980 --> 00:09:18.970 align:start position:0% we still don't Version Control apis uh everywhere 00:09:18.970 --> 00:09:18.980 align:start position:0% everywhere 00:09:18.980 --> 00:09:21.829 align:start position:0% everywhere latency<00:09:20.000> if<00:09:21.000> your<00:09:21.240> your<00:09:21.420> application 00:09:21.829 --> 00:09:21.839 align:start position:0% latency if your your application 00:09:21.839 --> 00:09:23.449 align:start position:0% latency if your your application requires<00:09:22.260> is<00:09:22.440> real<00:09:22.680> time<00:09:22.920> you<00:09:23.160> can't<00:09:23.279> be 00:09:23.449 --> 00:09:23.459 align:start position:0% requires is real time you can't be 00:09:23.459 --> 00:09:26.410 align:start position:0% requires is real time you can't be operating<00:09:23.940> an<00:09:24.180> hour<00:09:24.360> behind<00:09:24.779> blocks<00:09:25.200> uh<00:09:25.860> trust 00:09:26.410 --> 00:09:26.420 align:start position:0% operating an hour behind blocks uh trust 00:09:26.420 --> 00:09:30.170 align:start position:0% operating an hour behind blocks uh trust reliability<00:09:27.420> and<00:09:27.839> redundancy<00:09:28.500> open<00:09:29.459> openness 00:09:30.170 --> 00:09:30.180 align:start position:0% reliability and redundancy open openness 00:09:30.180 --> 00:09:31.850 align:start position:0% reliability and redundancy open openness of<00:09:30.300> the<00:09:30.480> actual<00:09:30.660> transformation<00:09:31.140> functions 00:09:31.850 --> 00:09:31.860 align:start position:0% of the actual transformation functions 00:09:31.860 --> 00:09:34.070 align:start position:0% of the actual transformation functions so<00:09:32.160> you<00:09:32.459> know<00:09:32.580> understanding<00:09:33.120> how<00:09:33.480> that<00:09:33.720> data 00:09:34.070 --> 00:09:34.080 align:start position:0% so you know understanding how that data 00:09:34.080 --> 00:09:37.370 align:start position:0% so you know understanding how that data was<00:09:34.440> uh<00:09:35.040> was<00:09:35.459> transformed<00:09:36.180> from<00:09:36.600> you<00:09:37.019> know<00:09:37.080> raw 00:09:37.370 --> 00:09:37.380 align:start position:0% was uh was transformed from you know raw 00:09:37.380 --> 00:09:38.930 align:start position:0% was uh was transformed from you know raw inputs<00:09:37.800> to<00:09:38.040> the<00:09:38.220> data<00:09:38.459> you're<00:09:38.519> looking<00:09:38.700> at<00:09:38.820> now 00:09:38.930 --> 00:09:38.940 align:start position:0% inputs to the data you're looking at now 00:09:38.940 --> 00:09:41.030 align:start position:0% inputs to the data you're looking at now and<00:09:39.120> then<00:09:39.240> openness<00:09:39.600> of<00:09:39.720> the<00:09:39.839> data<00:09:40.080> itself<00:09:40.320> uh 00:09:41.030 --> 00:09:41.040 align:start position:0% and then openness of the data itself uh 00:09:41.040 --> 00:09:41.990 align:start position:0% and then openness of the data itself uh you<00:09:41.160> know<00:09:41.279> if<00:09:41.399> you<00:09:41.519> want<00:09:41.580> to<00:09:41.700> be<00:09:41.760> able<00:09:41.880> to 00:09:41.990 --> 00:09:42.000 align:start position:0% you know if you want to be able to 00:09:42.000 --> 00:09:44.030 align:start position:0% you know if you want to be able to inspect<00:09:42.360> the<00:09:42.779> internal<00:09:43.140> State<00:09:43.380> can<00:09:43.740> you<00:09:43.920> just 00:09:44.030 --> 00:09:44.040 align:start position:0% inspect the internal State can you just 00:09:44.040 --> 00:09:45.829 align:start position:0% inspect the internal State can you just get<00:09:44.220> a<00:09:44.339> dump<00:09:44.519> of<00:09:44.700> the<00:09:44.820> database<00:09:45.120> and<00:09:45.360> check<00:09:45.720> it 00:09:45.829 --> 00:09:45.839 align:start position:0% get a dump of the database and check it 00:09:45.839 --> 00:09:46.850 align:start position:0% get a dump of the database and check it out 00:09:46.850 --> 00:09:46.860 align:start position:0% out 00:09:46.860 --> 00:09:48.650 align:start position:0% out um those<00:09:47.339> are<00:09:47.519> all<00:09:47.580> some<00:09:47.880> pretty<00:09:48.240> important 00:09:48.650 --> 00:09:48.660 align:start position:0% um those are all some pretty important 00:09:48.660 --> 00:09:52.930 align:start position:0% um those are all some pretty important things 00:09:52.930 --> 00:09:52.940 align:start position:0% 00:09:52.940 --> 00:09:57.050 align:start position:0% so<00:09:53.940> we<00:09:54.660> are<00:09:54.839> in<00:09:55.200> our<00:09:55.500> example<00:09:55.860> we<00:09:56.339> are<00:09:56.580> just 00:09:57.050 --> 00:09:57.060 align:start position:0% so we are in our example we are just 00:09:57.060 --> 00:09:59.090 align:start position:0% so we are in our example we are just fetching<00:09:57.420> each<00:09:57.540> USD<00:09:58.080> price<00:09:58.320> data<00:09:58.740> from<00:09:58.980> both 00:09:59.090 --> 00:09:59.100 align:start position:0% fetching each USD price data from both 00:09:59.100 --> 00:10:01.130 align:start position:0% fetching each USD price data from both graph<00:09:59.519> and<00:09:59.760> the<00:09:59.880> and<00:10:00.120> dune 00:10:01.130 --> 00:10:01.140 align:start position:0% graph and the and dune 00:10:01.140 --> 00:10:02.829 align:start position:0% graph and the and dune um<00:10:01.260> of<00:10:01.440> course<00:10:01.560> this<00:10:01.800> could<00:10:01.920> be<00:10:02.040> done<00:10:02.220> through 00:10:02.829 --> 00:10:02.839 align:start position:0% um of course this could be done through 00:10:02.839 --> 00:10:06.170 align:start position:0% um of course this could be done through most<00:10:03.839> of<00:10:04.019> the<00:10:04.200> apis<00:10:04.620> that<00:10:04.860> we<00:10:04.980> mentioned 00:10:06.170 --> 00:10:06.180 align:start position:0% most of the apis that we mentioned 00:10:06.180 --> 00:10:07.790 align:start position:0% most of the apis that we mentioned um<00:10:06.300> what<00:10:06.540> we<00:10:06.660> like<00:10:06.839> working<00:10:07.019> with<00:10:07.200> both<00:10:07.380> tools 00:10:07.790 --> 00:10:07.800 align:start position:0% um what we like working with both tools 00:10:07.800 --> 00:10:09.710 align:start position:0% um what we like working with both tools and<00:10:08.100> so<00:10:08.399> this<00:10:08.580> was<00:10:08.760> just<00:10:08.940> a<00:10:09.180> nice<00:10:09.540> little 00:10:09.710 --> 00:10:09.720 align:start position:0% and so this was just a nice little 00:10:09.720 --> 00:10:18.190 align:start position:0% and so this was just a nice little example<00:10:10.200> of<00:10:10.560> using<00:10:11.220> those 00:10:18.190 --> 00:10:18.200 align:start position:0% 00:10:18.200 --> 00:10:20.690 align:start position:0% it'll<00:10:19.200> Doon<00:10:19.440> first<00:10:19.560> yeah<00:10:20.100> we'll<00:10:20.399> start<00:10:20.580> with 00:10:20.690 --> 00:10:20.700 align:start position:0% it'll Doon first yeah we'll start with 00:10:20.700 --> 00:10:23.750 align:start position:0% it'll Doon first yeah we'll start with Dune<00:10:21.120> so<00:10:21.420> very<00:10:22.080> simple<00:10:22.260> query<00:10:22.620> here 00:10:23.750 --> 00:10:23.760 align:start position:0% Dune so very simple query here 00:10:23.760 --> 00:10:26.990 align:start position:0% Dune so very simple query here um<00:10:23.820> we're<00:10:24.720> actually<00:10:24.959> just<00:10:25.200> using<00:10:25.680> a<00:10:26.279> dune 00:10:26.990 --> 00:10:27.000 align:start position:0% um we're actually just using a dune 00:10:27.000 --> 00:10:29.750 align:start position:0% um we're actually just using a dune created<00:10:27.240> or<00:10:27.480> user<00:10:27.779> created<00:10:28.080> table<00:10:28.760> which 00:10:29.750 --> 00:10:29.760 align:start position:0% created or user created table which 00:10:29.760 --> 00:10:32.750 align:start position:0% created or user created table which gives<00:10:30.120> you<00:10:30.240> prices<00:10:30.480> of<00:10:30.839> different<00:10:31.080> uh<00:10:31.800> erc20s 00:10:32.750 --> 00:10:32.760 align:start position:0% gives you prices of different uh erc20s 00:10:32.760 --> 00:10:35.509 align:start position:0% gives you prices of different uh erc20s on<00:10:33.300> layer<00:10:33.600> one<00:10:33.779> ethereum 00:10:35.509 --> 00:10:35.519 align:start position:0% on layer one ethereum 00:10:35.519 --> 00:10:37.490 align:start position:0% on layer one ethereum and<00:10:36.060> here<00:10:36.300> you<00:10:36.480> can<00:10:36.600> see<00:10:36.779> we're<00:10:37.200> basically 00:10:37.490 --> 00:10:37.500 align:start position:0% and here you can see we're basically 00:10:37.500 --> 00:10:38.870 align:start position:0% and here you can see we're basically just<00:10:37.620> pulling<00:10:37.980> in 00:10:38.870 --> 00:10:38.880 align:start position:0% just pulling in 00:10:38.880 --> 00:10:40.610 align:start position:0% just pulling in um the<00:10:39.360> the<00:10:39.600> time 00:10:40.610 --> 00:10:40.620 align:start position:0% um the the time 00:10:40.620 --> 00:10:42.470 align:start position:0% um the the time um<00:10:40.740> which<00:10:41.279> we're<00:10:41.519> changing<00:10:41.880> to<00:10:42.060> hour<00:10:42.180> because 00:10:42.470 --> 00:10:42.480 align:start position:0% um which we're changing to hour because 00:10:42.480 --> 00:10:44.930 align:start position:0% um which we're changing to hour because we<00:10:42.660> want<00:10:42.779> hourly<00:10:43.200> hourly<00:10:43.920> price<00:10:44.220> and<00:10:44.880> then 00:10:44.930 --> 00:10:44.940 align:start position:0% we want hourly hourly price and then 00:10:44.940 --> 00:10:46.910 align:start position:0% we want hourly hourly price and then we're<00:10:45.120> doing<00:10:45.300> the<00:10:45.600> average<00:10:45.839> of<00:10:46.260> the<00:10:46.440> price<00:10:46.620> of 00:10:46.910 --> 00:10:46.920 align:start position:0% we're doing the average of the price of 00:10:46.920 --> 00:10:49.790 align:start position:0% we're doing the average of the price of eth<00:10:48.240> um<00:10:48.300> over<00:10:48.540> that<00:10:48.720> hour<00:10:48.899> and<00:10:49.620> then<00:10:49.680> we're 00:10:49.790 --> 00:10:49.800 align:start position:0% eth um over that hour and then we're 00:10:49.800 --> 00:10:51.410 align:start position:0% eth um over that hour and then we're doing<00:10:49.920> the<00:10:50.100> max<00:10:50.220> price<00:10:50.579> and<00:10:50.940> the<00:10:51.060> Min<00:10:51.180> price 00:10:51.410 --> 00:10:51.420 align:start position:0% doing the max price and the Min price 00:10:51.420 --> 00:10:52.730 align:start position:0% doing the max price and the Min price during<00:10:51.660> that<00:10:51.839> hour 00:10:52.730 --> 00:10:52.740 align:start position:0% during that hour 00:10:52.740 --> 00:10:55.910 align:start position:0% during that hour uh<00:10:53.279> for<00:10:53.399> the<00:10:53.519> last<00:10:53.640> 30<00:10:53.880> days 00:10:55.910 --> 00:10:55.920 align:start position:0% uh for the last 30 days 00:10:55.920 --> 00:10:57.769 align:start position:0% uh for the last 30 days and<00:10:56.399> you'll<00:10:56.579> see<00:10:56.700> this<00:10:56.820> query<00:10:57.060> as<00:10:57.240> a<00:10:57.420> query<00:10:57.600> ID 00:10:57.769 --> 00:10:57.779 align:start position:0% and you'll see this query as a query ID 00:10:57.779 --> 00:10:59.690 align:start position:0% and you'll see this query as a query ID here<00:10:58.079> that's<00:10:58.740> going<00:10:58.920> to<00:10:58.980> be<00:10:59.100> relevant<00:10:59.399> in<00:10:59.579> a 00:10:59.690 --> 00:10:59.700 align:start position:0% here that's going to be relevant in a 00:10:59.700 --> 00:11:05.530 align:start position:0% here that's going to be relevant in a second 00:11:05.530 --> 00:11:05.540 align:start position:0% 00:11:05.540 --> 00:11:08.990 align:start position:0% cool<00:11:06.540> so<00:11:06.899> yeah<00:11:07.740> as<00:11:07.980> we<00:11:08.160> said<00:11:08.279> we<00:11:08.579> don't<00:11:08.700> have 00:11:08.990 --> 00:11:09.000 align:start position:0% cool so yeah as we said we don't have 00:11:09.000 --> 00:11:13.009 align:start position:0% cool so yeah as we said we don't have access<00:11:09.240> to<00:11:09.839> the<00:11:10.260> uh<00:11:10.740> Dune<00:11:11.160> API<00:11:11.519> right<00:11:11.820> now 00:11:13.009 --> 00:11:13.019 align:start position:0% access to the uh Dune API right now 00:11:13.019 --> 00:11:14.569 align:start position:0% access to the uh Dune API right now um<00:11:13.140> if<00:11:13.380> someone<00:11:13.500> from<00:11:13.740> Dune<00:11:14.040> is<00:11:14.160> here<00:11:14.279> please 00:11:14.569 --> 00:11:14.579 align:start position:0% um if someone from Dune is here please 00:11:14.579 --> 00:11:18.110 align:start position:0% um if someone from Dune is here please uh<00:11:15.480> let<00:11:15.839> us<00:11:15.959> know<00:11:16.079> we'd<00:11:16.620> love<00:11:16.740> to<00:11:16.860> use<00:11:17.040> it 00:11:18.110 --> 00:11:18.120 align:start position:0% uh let us know we'd love to use it 00:11:18.120 --> 00:11:20.569 align:start position:0% uh let us know we'd love to use it um<00:11:18.180> but<00:11:18.959> uh<00:11:19.320> so<00:11:19.560> instead<00:11:19.860> we're<00:11:19.980> using<00:11:20.279> this 00:11:20.569 --> 00:11:20.579 align:start position:0% um but uh so instead we're using this 00:11:20.579 --> 00:11:23.410 align:start position:0% um but uh so instead we're using this this<00:11:20.940> uh<00:11:21.360> open<00:11:21.540> source<00:11:21.899> SDK<00:11:22.320> that<00:11:22.560> grabs 00:11:23.410 --> 00:11:23.420 align:start position:0% this uh open source SDK that grabs 00:11:23.420 --> 00:11:26.329 align:start position:0% this uh open source SDK that grabs essentially<00:11:24.420> the<00:11:24.660> the<00:11:24.779> data<00:11:25.140> from<00:11:25.260> a<00:11:25.380> query<00:11:25.680> uh 00:11:26.329 --> 00:11:26.339 align:start position:0% essentially the the data from a query uh 00:11:26.339 --> 00:11:28.130 align:start position:0% essentially the the data from a query uh it's<00:11:26.519> limiting<00:11:26.880> in<00:11:27.060> the<00:11:27.180> sense<00:11:27.360> that<00:11:27.720> you 00:11:28.130 --> 00:11:28.140 align:start position:0% it's limiting in the sense that you 00:11:28.140 --> 00:11:29.870 align:start position:0% it's limiting in the sense that you can't<00:11:28.320> actually<00:11:28.500> run<00:11:28.800> the<00:11:29.040> query<00:11:29.339> using<00:11:29.760> this 00:11:29.870 --> 00:11:29.880 align:start position:0% can't actually run the query using this 00:11:29.880 --> 00:11:31.550 align:start position:0% can't actually run the query using this so<00:11:30.120> you<00:11:30.240> basically<00:11:30.540> you<00:11:31.079> know<00:11:31.140> every<00:11:31.260> time<00:11:31.440> you 00:11:31.550 --> 00:11:31.560 align:start position:0% so you basically you know every time you 00:11:31.560 --> 00:11:32.930 align:start position:0% so you basically you know every time you want<00:11:31.680> to<00:11:31.740> do<00:11:31.800> this<00:11:31.920> you'd<00:11:32.160> have<00:11:32.220> to<00:11:32.339> go<00:11:32.519> back<00:11:32.700> to 00:11:32.930 --> 00:11:32.940 align:start position:0% want to do this you'd have to go back to 00:11:32.940 --> 00:11:34.670 align:start position:0% want to do this you'd have to go back to do<00:11:33.120> and<00:11:33.240> run<00:11:33.420> the<00:11:33.600> query<00:11:33.839> and<00:11:34.260> then<00:11:34.320> come<00:11:34.500> back 00:11:34.670 --> 00:11:34.680 align:start position:0% do and run the query and then come back 00:11:34.680 --> 00:11:36.650 align:start position:0% do and run the query and then come back here<00:11:34.860> and<00:11:35.040> it'll<00:11:35.399> update<00:11:35.700> after<00:11:36.180> you<00:11:36.360> run<00:11:36.480> this 00:11:36.650 --> 00:11:36.660 align:start position:0% here and it'll update after you run this 00:11:36.660 --> 00:11:38.269 align:start position:0% here and it'll update after you run this function 00:11:38.269 --> 00:11:38.279 align:start position:0% function 00:11:38.279 --> 00:11:39.590 align:start position:0% function um but<00:11:38.459> yeah<00:11:38.640> basically<00:11:38.940> it's<00:11:39.060> just<00:11:39.240> grabbing 00:11:39.590 --> 00:11:39.600 align:start position:0% um but yeah basically it's just grabbing 00:11:39.600 --> 00:11:41.449 align:start position:0% um but yeah basically it's just grabbing kind<00:11:39.779> of<00:11:39.899> that<00:11:40.019> that<00:11:40.320> static<00:11:40.860> data<00:11:41.160> from<00:11:41.339> the 00:11:41.449 --> 00:11:41.459 align:start position:0% kind of that that static data from the 00:11:41.459 --> 00:11:45.769 align:start position:0% kind of that that static data from the query<00:11:41.640> the<00:11:41.880> last<00:11:42.060> time<00:11:42.180> it<00:11:42.300> was<00:11:42.420> run 00:11:45.769 --> 00:11:45.779 align:start position:0% 00:11:45.779 --> 00:11:48.050 align:start position:0% then<00:11:46.500> uh<00:11:47.040> yeah<00:11:47.220> if<00:11:47.399> you<00:11:47.519> just<00:11:47.579> scroll<00:11:47.760> up<00:11:47.940> a 00:11:48.050 --> 00:11:48.060 align:start position:0% then uh yeah if you just scroll up a 00:11:48.060 --> 00:11:49.850 align:start position:0% then uh yeah if you just scroll up a little<00:11:48.120> bit<00:11:48.240> to<00:11:48.420> data<00:11:48.899> data<00:11:49.380> one<00:11:49.500> two<00:11:49.680> three 00:11:49.850 --> 00:11:49.860 align:start position:0% little bit to data data one two three 00:11:49.860 --> 00:11:51.829 align:start position:0% little bit to data data one two three yeah<00:11:50.160> uh<00:11:50.760> just<00:11:51.000> quickly<00:11:51.240> mention<00:11:51.420> this<00:11:51.660> it's 00:11:51.829 --> 00:11:51.839 align:start position:0% yeah uh just quickly mention this it's 00:11:51.839 --> 00:11:53.630 align:start position:0% yeah uh just quickly mention this it's not<00:11:52.019> that<00:11:52.200> significant<00:11:52.680> but<00:11:52.980> we're<00:11:53.339> basically 00:11:53.630 --> 00:11:53.640 align:start position:0% not that significant but we're basically 00:11:53.640 --> 00:11:56.690 align:start position:0% not that significant but we're basically just<00:11:53.820> changing<00:11:54.360> the<00:11:54.899> uh<00:11:55.380> Json<00:11:55.740> format<00:11:56.279> that<00:11:56.519> we 00:11:56.690 --> 00:11:56.700 align:start position:0% just changing the uh Json format that we 00:11:56.700 --> 00:11:58.550 align:start position:0% just changing the uh Json format that we get<00:11:56.820> in<00:11:57.000> the<00:11:57.120> response<00:11:57.540> and<00:11:57.839> we're<00:11:58.079> turning<00:11:58.440> it 00:11:58.550 --> 00:11:58.560 align:start position:0% get in the response and we're turning it 00:11:58.560 --> 00:12:01.250 align:start position:0% get in the response and we're turning it into<00:11:58.680> a<00:11:58.860> panda's<00:11:59.279> data<00:11:59.579> frame<00:11:59.779> uh<00:12:00.779> are<00:12:00.959> people 00:12:01.250 --> 00:12:01.260 align:start position:0% into a panda's data frame uh are people 00:12:01.260 --> 00:12:04.370 align:start position:0% into a panda's data frame uh are people here<00:12:01.560> familiar<00:12:02.100> with<00:12:02.459> pandas<00:12:03.180> data<00:12:03.480> frame 00:12:04.370 --> 00:12:04.380 align:start position:0% here familiar with pandas data frame 00:12:04.380 --> 00:12:06.889 align:start position:0% here familiar with pandas data frame a<00:12:04.740> lot<00:12:04.920> of<00:12:05.040> nods<00:12:05.399> okay<00:12:05.700> cool 00:12:06.889 --> 00:12:06.899 align:start position:0% a lot of nods okay cool 00:12:06.899 --> 00:12:09.889 align:start position:0% a lot of nods okay cool rows<00:12:07.500> and<00:12:07.620> columns 00:12:09.889 --> 00:12:09.899 align:start position:0% rows and columns 00:12:09.899 --> 00:12:11.030 align:start position:0% rows and columns cool 00:12:11.030 --> 00:12:11.040 align:start position:0% cool 00:12:11.040 --> 00:12:12.290 align:start position:0% cool um<00:12:11.160> and<00:12:11.519> then 00:12:12.290 --> 00:12:12.300 align:start position:0% um and then 00:12:12.300 --> 00:12:14.930 align:start position:0% um and then yeah<00:12:13.160> yeah<00:12:14.160> there's<00:12:14.399> a<00:12:14.579> little<00:12:14.700> bit<00:12:14.820> of 00:12:14.930 --> 00:12:14.940 align:start position:0% yeah yeah there's a little bit of 00:12:14.940 --> 00:12:16.790 align:start position:0% yeah yeah there's a little bit of processing<00:12:15.480> here<00:12:15.660> to<00:12:15.839> get<00:12:16.019> you<00:12:16.320> know<00:12:16.440> the<00:12:16.500> data 00:12:16.790 --> 00:12:16.800 align:start position:0% processing here to get you know the data 00:12:16.800 --> 00:12:18.650 align:start position:0% processing here to get you know the data wrangled<00:12:17.100> so<00:12:17.459> it's<00:12:17.700> consistent<00:12:18.180> across<00:12:18.540> both 00:12:18.650 --> 00:12:18.660 align:start position:0% wrangled so it's consistent across both 00:12:18.660 --> 00:12:21.410 align:start position:0% wrangled so it's consistent across both Dune<00:12:19.079> and<00:12:19.140> the<00:12:19.320> graph<00:12:19.519> uh<00:12:20.519> this<00:12:20.820> one<00:12:20.940> is<00:12:21.180> you 00:12:21.410 --> 00:12:21.420 align:start position:0% Dune and the graph uh this one is you 00:12:21.420 --> 00:12:23.269 align:start position:0% Dune and the graph uh this one is you know<00:12:21.540> the<00:12:21.660> the<00:12:21.779> graph<00:12:22.079> data<00:12:22.440> pull 00:12:23.269 --> 00:12:23.279 align:start position:0% know the the graph data pull 00:12:23.279 --> 00:12:25.310 align:start position:0% know the the graph data pull um<00:12:23.339> so<00:12:23.519> we're<00:12:23.640> specifying<00:12:24.060> the<00:12:24.180> endpoint<00:12:24.540> uh 00:12:25.310 --> 00:12:25.320 align:start position:0% um so we're specifying the endpoint uh 00:12:25.320 --> 00:12:27.050 align:start position:0% um so we're specifying the endpoint uh we're<00:12:25.440> just<00:12:25.680> using<00:12:25.920> the<00:12:26.100> uh<00:12:26.459> chain<00:12:26.760> link 00:12:27.050 --> 00:12:27.060 align:start position:0% we're just using the uh chain link 00:12:27.060 --> 00:12:29.449 align:start position:0% we're just using the uh chain link prices<00:12:27.360> a<00:12:27.839> sub<00:12:28.079> graph<00:12:28.320> here 00:12:29.449 --> 00:12:29.459 align:start position:0% prices a sub graph here 00:12:29.459 --> 00:12:31.610 align:start position:0% prices a sub graph here um<00:12:29.519> in<00:12:29.820> fact<00:12:29.940> this<00:12:30.480> data<00:12:30.899> isn't<00:12:31.320> actually 00:12:31.610 --> 00:12:31.620 align:start position:0% um in fact this data isn't actually 00:12:31.620 --> 00:12:33.230 align:start position:0% um in fact this data isn't actually hourly<00:12:32.220> data 00:12:33.230 --> 00:12:33.240 align:start position:0% hourly data 00:12:33.240 --> 00:12:35.930 align:start position:0% hourly data um<00:12:33.360> so<00:12:33.660> we<00:12:34.079> first<00:12:34.620> you<00:12:34.980> know<00:12:35.040> we<00:12:35.220> were<00:12:35.519> using 00:12:35.930 --> 00:12:35.940 align:start position:0% um so we first you know we were using 00:12:35.940 --> 00:12:38.930 align:start position:0% um so we first you know we were using graphql<00:12:36.779> to<00:12:37.140> query<00:12:37.500> the<00:12:37.680> graph<00:12:37.980> uh<00:12:38.640> we're<00:12:38.820> just 00:12:38.930 --> 00:12:38.940 align:start position:0% graphql to query the graph uh we're just 00:12:38.940 --> 00:12:40.850 align:start position:0% graphql to query the graph uh we're just looking<00:12:39.060> for<00:12:39.240> the<00:12:39.420> eth<00:12:39.660> USD<00:12:40.140> asset<00:12:40.440> pair<00:12:40.620> we're 00:12:40.850 --> 00:12:40.860 align:start position:0% looking for the eth USD asset pair we're 00:12:40.860 --> 00:12:42.410 align:start position:0% looking for the eth USD asset pair we're ordering<00:12:41.100> by<00:12:41.279> Tam<00:12:41.459> timestamp<00:12:41.880> so<00:12:42.120> we<00:12:42.240> get<00:12:42.300> the 00:12:42.410 --> 00:12:42.420 align:start position:0% ordering by Tam timestamp so we get the 00:12:42.420 --> 00:12:45.110 align:start position:0% ordering by Tam timestamp so we get the newest<00:12:42.660> data<00:12:43.019> uh<00:12:43.740> we're<00:12:43.980> ordering<00:12:44.339> descending 00:12:45.110 --> 00:12:45.120 align:start position:0% newest data uh we're ordering descending 00:12:45.120 --> 00:12:46.610 align:start position:0% newest data uh we're ordering descending and<00:12:45.360> we're<00:12:45.480> grabbing<00:12:45.779> the<00:12:45.899> first<00:12:46.079> thousand 00:12:46.610 --> 00:12:46.620 align:start position:0% and we're grabbing the first thousand 00:12:46.620 --> 00:12:48.590 align:start position:0% and we're grabbing the first thousand prices<00:12:46.860> as<00:12:47.760> well<00:12:47.880> as<00:12:47.940> the<00:12:48.120> timestamps 00:12:48.590 --> 00:12:48.600 align:start position:0% prices as well as the timestamps 00:12:48.600 --> 00:12:50.750 align:start position:0% prices as well as the timestamps associated<00:12:48.899> with<00:12:49.139> that<00:12:49.260> uh<00:12:50.040> then<00:12:50.220> we<00:12:50.399> do<00:12:50.519> the 00:12:50.750 --> 00:12:50.760 align:start position:0% associated with that uh then we do the 00:12:50.760 --> 00:12:53.030 align:start position:0% associated with that uh then we do the exact<00:12:51.480> same<00:12:51.660> thing<00:12:51.899> here<00:12:52.139> except<00:12:52.500> we<00:12:52.740> do<00:12:52.860> one 00:12:53.030 --> 00:12:53.040 align:start position:0% exact same thing here except we do one 00:12:53.040 --> 00:12:54.650 align:start position:0% exact same thing here except we do one thing<00:12:53.220> which<00:12:53.399> is<00:12:53.519> resampling<00:12:54.120> so<00:12:54.360> that<00:12:54.540> we 00:12:54.650 --> 00:12:54.660 align:start position:0% thing which is resampling so that we 00:12:54.660 --> 00:12:56.750 align:start position:0% thing which is resampling so that we only<00:12:54.779> end<00:12:55.019> up<00:12:55.200> with<00:12:55.440> you<00:12:55.920> know<00:12:56.040> one<00:12:56.279> timestamp 00:12:56.750 --> 00:12:56.760 align:start position:0% only end up with you know one timestamp 00:12:56.760 --> 00:12:59.329 align:start position:0% only end up with you know one timestamp every<00:12:57.120> hour<00:12:57.440> or<00:12:58.440> one<00:12:58.680> price<00:12:58.920> every<00:12:59.160> hour 00:12:59.329 --> 00:12:59.339 align:start position:0% every hour or one price every hour 00:12:59.339 --> 00:13:01.670 align:start position:0% every hour or one price every hour instead<00:12:59.760> of<00:12:59.820> instead<00:13:00.180> of<00:13:00.240> multiple 00:13:01.670 --> 00:13:01.680 align:start position:0% instead of instead of multiple 00:13:01.680 --> 00:13:04.990 align:start position:0% instead of instead of multiple okay 00:13:04.990 --> 00:13:05.000 align:start position:0% 00:13:05.000 --> 00:13:07.850 align:start position:0% and<00:13:06.000> uh<00:13:06.300> here's<00:13:07.139> just<00:13:07.260> an<00:13:07.380> example<00:13:07.620> of<00:13:07.740> the 00:13:07.850 --> 00:13:07.860 align:start position:0% and uh here's just an example of the 00:13:07.860 --> 00:13:09.350 align:start position:0% and uh here's just an example of the outputs<00:13:08.279> you'll<00:13:08.579> notice<00:13:08.820> that<00:13:09.120> there's 00:13:09.350 --> 00:13:09.360 align:start position:0% outputs you'll notice that there's 00:13:09.360 --> 00:13:11.329 align:start position:0% outputs you'll notice that there's actually<00:13:09.540> inconsistency<00:13:10.260> between<00:13:10.680> price<00:13:11.100> and 00:13:11.329 --> 00:13:11.339 align:start position:0% actually inconsistency between price and 00:13:11.339 --> 00:13:12.590 align:start position:0% actually inconsistency between price and price<00:13:11.579> here 00:13:12.590 --> 00:13:12.600 align:start position:0% price here 00:13:12.600 --> 00:13:14.509 align:start position:0% price here um<00:13:12.660> that's<00:13:12.839> because<00:13:13.139> uh<00:13:13.860> the<00:13:14.100> Dune<00:13:14.399> table 00:13:14.509 --> 00:13:14.519 align:start position:0% um that's because uh the Dune table 00:13:14.519 --> 00:13:16.430 align:start position:0% um that's because uh the Dune table actually<00:13:15.300> does<00:13:15.480> this<00:13:15.660> in<00:13:15.779> decimal<00:13:16.139> format 00:13:16.430 --> 00:13:16.440 align:start position:0% actually does this in decimal format 00:13:16.440 --> 00:13:18.889 align:start position:0% actually does this in decimal format while<00:13:16.800> you<00:13:17.279> know<00:13:17.339> the<00:13:17.519> graph<00:13:17.820> uh<00:13:18.480> here<00:13:18.660> this 00:13:18.889 --> 00:13:18.899 align:start position:0% while you know the graph uh here this 00:13:18.899 --> 00:13:25.910 align:start position:0% while you know the graph uh here this subgraph<00:13:19.380> specifically<00:13:20.040> uh<00:13:20.940> looks<00:13:21.480> like 00:13:25.910 --> 00:13:25.920 align:start position:0% 00:13:25.920 --> 00:13:29.509 align:start position:0% uh<00:13:26.700> yeah<00:13:26.940> eight<00:13:27.420> decimal<00:13:28.079> points 00:13:29.509 --> 00:13:29.519 align:start position:0% uh yeah eight decimal points 00:13:29.519 --> 00:13:31.069 align:start position:0% uh yeah eight decimal points um<00:13:29.639> so<00:13:30.180> uh 00:13:31.069 --> 00:13:31.079 align:start position:0% um so uh 00:13:31.079 --> 00:13:33.410 align:start position:0% um so uh the<00:13:31.800> the<00:13:32.040> fact<00:13:32.519> is<00:13:32.700> we're<00:13:32.880> running<00:13:33.000> this<00:13:33.240> model 00:13:33.410 --> 00:13:33.420 align:start position:0% the the fact is we're running this model 00:13:33.420 --> 00:13:35.449 align:start position:0% the the fact is we're running this model separately<00:13:34.019> so<00:13:34.440> it<00:13:34.560> doesn't<00:13:34.920> really<00:13:35.220> matter 00:13:35.449 --> 00:13:35.459 align:start position:0% separately so it doesn't really matter 00:13:35.459 --> 00:13:37.850 align:start position:0% separately so it doesn't really matter for<00:13:36.180> this<00:13:36.300> example<00:13:36.660> but<00:13:37.260> it's<00:13:37.380> just<00:13:37.560> one<00:13:37.740> of 00:13:37.850 --> 00:13:37.860 align:start position:0% for this example but it's just one of 00:13:37.860 --> 00:13:39.350 align:start position:0% for this example but it's just one of those<00:13:38.100> things<00:13:38.639> to<00:13:38.820> pay<00:13:38.940> attention<00:13:39.240> to 00:13:39.350 --> 00:13:39.360 align:start position:0% those things to pay attention to 00:13:39.360 --> 00:13:40.490 align:start position:0% those things to pay attention to obviously<00:13:39.779> your<00:13:39.899> data<00:13:40.200> needs<00:13:40.380> to<00:13:40.380> be 00:13:40.490 --> 00:13:40.500 align:start position:0% obviously your data needs to be 00:13:40.500 --> 00:13:42.370 align:start position:0% obviously your data needs to be consistent 00:13:42.370 --> 00:13:42.380 align:start position:0% consistent 00:13:42.380 --> 00:13:44.810 align:start position:0% consistent yeah<00:13:43.380> and<00:13:43.500> one<00:13:43.620> thing<00:13:44.040> I'll<00:13:44.220> I'll<00:13:44.459> mention 00:13:44.810 --> 00:13:44.820 align:start position:0% yeah and one thing I'll I'll mention 00:13:44.820 --> 00:13:46.970 align:start position:0% yeah and one thing I'll I'll mention about<00:13:45.060> that<00:13:45.300> as<00:13:45.420> well<00:13:45.600> is 00:13:46.970 --> 00:13:46.980 align:start position:0% about that as well is 00:13:46.980 --> 00:13:49.250 align:start position:0% about that as well is um<00:13:47.399> it's<00:13:47.880> actually<00:13:48.060> great<00:13:48.420> to<00:13:48.720> use<00:13:48.959> more<00:13:49.139> than 00:13:49.250 --> 00:13:49.260 align:start position:0% um it's actually great to use more than 00:13:49.260 --> 00:13:50.690 align:start position:0% um it's actually great to use more than one<00:13:49.440> data<00:13:49.740> source 00:13:50.690 --> 00:13:50.700 align:start position:0% one data source 00:13:50.700 --> 00:13:52.190 align:start position:0% one data source um just<00:13:50.940> so<00:13:51.060> you<00:13:51.300> can<00:13:51.420> actually<00:13:51.600> check<00:13:51.839> these 00:13:52.190 --> 00:13:52.200 align:start position:0% um just so you can actually check these 00:13:52.200 --> 00:13:53.930 align:start position:0% um just so you can actually check these things<00:13:52.320> uh<00:13:53.040> you<00:13:53.160> know<00:13:53.279> it's<00:13:53.339> hard<00:13:53.579> to<00:13:53.760> know 00:13:53.930 --> 00:13:53.940 align:start position:0% things uh you know it's hard to know 00:13:53.940 --> 00:13:56.930 align:start position:0% things uh you know it's hard to know what<00:13:54.420> the<00:13:54.899> uh<00:13:55.320> the<00:13:55.980> source<00:13:56.160> of<00:13:56.220> Truth<00:13:56.459> is<00:13:56.639> so 00:13:56.930 --> 00:13:56.940 align:start position:0% what the uh the source of Truth is so 00:13:56.940 --> 00:13:58.490 align:start position:0% what the uh the source of Truth is so you<00:13:57.240> know<00:13:57.420> using<00:13:57.720> different<00:13:57.839> data<00:13:58.260> sources 00:13:58.490 --> 00:13:58.500 align:start position:0% you know using different data sources 00:13:58.500 --> 00:14:00.350 align:start position:0% you know using different data sources check<00:13:59.040> them<00:13:59.279> against<00:13:59.519> each<00:13:59.820> other<00:13:59.940> you<00:14:00.300> know 00:14:00.350 --> 00:14:00.360 align:start position:0% check them against each other you know 00:14:00.360 --> 00:14:02.329 align:start position:0% check them against each other you know maybe<00:14:00.480> before<00:14:00.720> you<00:14:00.959> run<00:14:01.139> something<00:14:01.380> is<00:14:02.220> always 00:14:02.329 --> 00:14:02.339 align:start position:0% maybe before you run something is always 00:14:02.339 --> 00:14:05.870 align:start position:0% maybe before you run something is always a<00:14:02.579> good<00:14:02.639> idea<00:14:02.940> and<00:14:03.660> another<00:14:04.260> thing<00:14:04.560> is<00:14:04.800> uh<00:14:05.339> we 00:14:05.870 --> 00:14:05.880 align:start position:0% a good idea and another thing is uh we 00:14:05.880 --> 00:14:07.730 align:start position:0% a good idea and another thing is uh we didn't<00:14:06.000> really<00:14:06.120> mention<00:14:06.420> this<00:14:06.660> but 00:14:07.730 --> 00:14:07.740 align:start position:0% didn't really mention this but 00:14:07.740 --> 00:14:09.710 align:start position:0% didn't really mention this but um<00:14:07.800> with<00:14:08.760> the<00:14:08.880> data<00:14:09.120> we're<00:14:09.180> pulling<00:14:09.480> you<00:14:09.600> know 00:14:09.710 --> 00:14:09.720 align:start position:0% um with the data we're pulling you know 00:14:09.720 --> 00:14:11.650 align:start position:0% um with the data we're pulling you know you<00:14:09.959> know<00:14:10.079> this<00:14:10.320> is<00:14:10.380> a<00:14:10.560> simple<00:14:10.680> example<00:14:11.100> but 00:14:11.650 --> 00:14:11.660 align:start position:0% you know this is a simple example but 00:14:11.660 --> 00:14:14.030 align:start position:0% you know this is a simple example but the<00:14:12.660> really<00:14:12.899> cool<00:14:13.139> thing<00:14:13.380> is<00:14:13.620> that<00:14:13.800> you<00:14:13.980> know 00:14:14.030 --> 00:14:14.040 align:start position:0% the really cool thing is that you know 00:14:14.040 --> 00:14:16.310 align:start position:0% the really cool thing is that you know anything<00:14:14.279> on<00:14:14.579> chain<00:14:14.820> is<00:14:15.120> fair<00:14:15.300> game<00:14:15.540> in<00:14:16.139> terms 00:14:16.310 --> 00:14:16.320 align:start position:0% anything on chain is fair game in terms 00:14:16.320 --> 00:14:18.470 align:start position:0% anything on chain is fair game in terms of<00:14:16.440> data<00:14:16.680> that<00:14:16.800> you<00:14:16.920> can<00:14:17.040> use<00:14:17.160> so<00:14:17.760> think<00:14:18.180> you 00:14:18.470 --> 00:14:18.480 align:start position:0% of data that you can use so think you 00:14:18.480 --> 00:14:22.129 align:start position:0% of data that you can use so think you know<00:14:18.620> lping<00:14:19.620> lending<00:14:20.339> protocols<00:14:21.060> uh<00:14:21.839> you<00:14:22.079> know 00:14:22.129 --> 00:14:22.139 align:start position:0% know lping lending protocols uh you know 00:14:22.139 --> 00:14:24.530 align:start position:0% know lping lending protocols uh you know on-chain<00:14:22.500> derivatives<00:14:22.860> protocols<00:14:23.339> nfts<00:14:24.120> you 00:14:24.530 --> 00:14:24.540 align:start position:0% on-chain derivatives protocols nfts you 00:14:24.540 --> 00:14:26.750 align:start position:0% on-chain derivatives protocols nfts you know<00:14:24.600> doesn't<00:14:24.720> have<00:14:24.899> to<00:14:25.019> be<00:14:25.200> defy<00:14:25.500> related 00:14:26.750 --> 00:14:26.760 align:start position:0% know doesn't have to be defy related 00:14:26.760 --> 00:14:27.949 align:start position:0% know doesn't have to be defy related um<00:14:26.820> you<00:14:27.180> know<00:14:27.240> you<00:14:27.300> can<00:14:27.480> do<00:14:27.600> some<00:14:27.779> pretty 00:14:27.949 --> 00:14:27.959 align:start position:0% um you know you can do some pretty 00:14:27.959 --> 00:14:30.470 align:start position:0% um you know you can do some pretty sophisticated<00:14:28.560> stuff<00:14:28.980> uh<00:14:29.820> with<00:14:30.360> different 00:14:30.470 --> 00:14:30.480 align:start position:0% sophisticated stuff uh with different 00:14:30.480 --> 00:14:32.090 align:start position:0% sophisticated stuff uh with different types<00:14:30.779> of<00:14:30.899> data 00:14:32.090 --> 00:14:32.100 align:start position:0% types of data 00:14:32.100 --> 00:14:34.430 align:start position:0% types of data so<00:14:32.760> yeah<00:14:33.060> moving<00:14:33.300> into<00:14:33.480> this<00:14:33.660> section<00:14:33.839> now<00:14:34.139> so 00:14:34.430 --> 00:14:34.440 align:start position:0% so yeah moving into this section now so 00:14:34.440 --> 00:14:36.470 align:start position:0% so yeah moving into this section now so data<00:14:34.920> processing<00:14:35.339> and<00:14:35.459> modeling 00:14:36.470 --> 00:14:36.480 align:start position:0% data processing and modeling 00:14:36.480 --> 00:14:37.730 align:start position:0% data processing and modeling um<00:14:36.540> you<00:14:36.779> know<00:14:36.839> now<00:14:37.079> we're<00:14:37.200> at<00:14:37.320> the<00:14:37.440> point<00:14:37.560> where 00:14:37.730 --> 00:14:37.740 align:start position:0% um you know now we're at the point where 00:14:37.740 --> 00:14:40.850 align:start position:0% um you know now we're at the point where we<00:14:37.920> have<00:14:38.180> uh<00:14:39.180> the<00:14:39.660> the<00:14:39.959> Dune<00:14:40.380> query<00:14:40.560> and<00:14:40.740> the 00:14:40.850 --> 00:14:40.860 align:start position:0% we have uh the the Dune query and the 00:14:40.860 --> 00:14:43.189 align:start position:0% we have uh the the Dune query and the graph<00:14:40.980> query<00:14:41.279> uh<00:14:41.639> pulled<00:14:41.940> in<00:14:42.060> uh<00:14:42.540> using<00:14:42.839> Python 00:14:43.189 --> 00:14:43.199 align:start position:0% graph query uh pulled in uh using Python 00:14:43.199 --> 00:14:45.410 align:start position:0% graph query uh pulled in uh using Python and<00:14:43.560> now<00:14:43.680> we<00:14:43.980> want<00:14:44.100> to<00:14:44.339> uh<00:14:45.000> model<00:14:45.240> it 00:14:45.410 --> 00:14:45.420 align:start position:0% and now we want to uh model it 00:14:45.420 --> 00:14:48.110 align:start position:0% and now we want to uh model it essentially 00:14:48.110 --> 00:14:48.120 align:start position:0% 00:14:48.120 --> 00:14:50.389 align:start position:0% so<00:14:48.540> before<00:14:48.779> we<00:14:49.079> jump<00:14:49.320> uh<00:14:49.680> in<00:14:49.800> back<00:14:50.040> into<00:14:50.160> the 00:14:50.389 --> 00:14:50.399 align:start position:0% so before we jump uh in back into the 00:14:50.399 --> 00:14:51.530 align:start position:0% so before we jump uh in back into the code 00:14:51.530 --> 00:14:51.540 align:start position:0% code 00:14:51.540 --> 00:14:54.110 align:start position:0% code um<00:14:51.660> there's<00:14:52.139> just<00:14:52.320> a<00:14:52.440> few<00:14:52.560> considerations<00:14:53.120> uh 00:14:54.110 --> 00:14:54.120 align:start position:0% um there's just a few considerations uh 00:14:54.120 --> 00:14:55.670 align:start position:0% um there's just a few considerations uh kind<00:14:54.420> of<00:14:54.540> like<00:14:54.660> just<00:14:54.839> what<00:14:55.019> I<00:14:55.139> said<00:14:55.260> with<00:14:55.440> like 00:14:55.670 --> 00:14:55.680 align:start position:0% kind of like just what I said with like 00:14:55.680 --> 00:14:57.470 align:start position:0% kind of like just what I said with like there's<00:14:56.100> so<00:14:56.399> much<00:14:56.519> composability<00:14:57.120> when<00:14:57.360> it 00:14:57.470 --> 00:14:57.480 align:start position:0% there's so much composability when it 00:14:57.480 --> 00:15:00.170 align:start position:0% there's so much composability when it comes<00:14:57.600> to<00:14:57.779> data<00:14:58.079> there's<00:14:58.800> also<00:14:59.180> infinite 00:15:00.170 --> 00:15:00.180 align:start position:0% comes to data there's also infinite 00:15:00.180 --> 00:15:02.870 align:start position:0% comes to data there's also infinite composability<00:15:01.079> when<00:15:01.320> it<00:15:01.440> comes<00:15:01.620> to<00:15:01.740> modeling 00:15:02.870 --> 00:15:02.880 align:start position:0% composability when it comes to modeling 00:15:02.880 --> 00:15:04.250 align:start position:0% composability when it comes to modeling um<00:15:02.940> you<00:15:03.000> know<00:15:03.120> you<00:15:03.300> could<00:15:03.420> use<00:15:03.540> instead<00:15:04.199> of 00:15:04.250 --> 00:15:04.260 align:start position:0% um you know you could use instead of 00:15:04.260 --> 00:15:06.530 align:start position:0% um you know you could use instead of using<00:15:04.980> a<00:15:05.339> Time<00:15:05.579> series<00:15:05.760> prediction<00:15:06.240> you<00:15:06.420> could 00:15:06.530 --> 00:15:06.540 align:start position:0% using a Time series prediction you could 00:15:06.540 --> 00:15:08.750 align:start position:0% using a Time series prediction you could do<00:15:06.660> conditional<00:15:07.139> logic<00:15:07.500> like 00:15:08.750 --> 00:15:08.760 align:start position:0% do conditional logic like 00:15:08.760 --> 00:15:10.250 align:start position:0% do conditional logic like um<00:15:08.820> you<00:15:09.480> know<00:15:09.540> maybe<00:15:09.660> there's<00:15:09.839> someone<00:15:10.019> you 00:15:10.250 --> 00:15:10.260 align:start position:0% um you know maybe there's someone you 00:15:10.260 --> 00:15:12.590 align:start position:0% um you know maybe there's someone you follow<00:15:10.500> that<00:15:11.100> trades<00:15:11.579> really<00:15:11.699> well<00:15:12.000> and 00:15:12.590 --> 00:15:12.600 align:start position:0% follow that trades really well and 00:15:12.600 --> 00:15:14.329 align:start position:0% follow that trades really well and anytime<00:15:13.139> that<00:15:13.260> they<00:15:13.380> make<00:15:13.740> a<00:15:13.860> trade<00:15:14.040> you<00:15:14.160> want 00:15:14.329 --> 00:15:14.339 align:start position:0% anytime that they make a trade you want 00:15:14.339 --> 00:15:16.009 align:start position:0% anytime that they make a trade you want to<00:15:14.399> mimic<00:15:14.639> it<00:15:14.760> uh<00:15:15.180> right<00:15:15.300> away<00:15:15.480> you<00:15:15.720> know<00:15:15.839> stuff 00:15:16.009 --> 00:15:16.019 align:start position:0% to mimic it uh right away you know stuff 00:15:16.019 --> 00:15:18.050 align:start position:0% to mimic it uh right away you know stuff like<00:15:16.199> that<00:15:16.380> or<00:15:17.160> if<00:15:17.279> you<00:15:17.399> know<00:15:17.519> someone<00:15:17.699> like<00:15:17.880> me 00:15:18.050 --> 00:15:18.060 align:start position:0% like that or if you know someone like me 00:15:18.060 --> 00:15:19.910 align:start position:0% like that or if you know someone like me is<00:15:18.240> not<00:15:18.420> a<00:15:18.600> good<00:15:18.660> Trader<00:15:19.079> you<00:15:19.380> can<00:15:19.440> take<00:15:19.740> the 00:15:19.910 --> 00:15:19.920 align:start position:0% is not a good Trader you can take the 00:15:19.920 --> 00:15:21.889 align:start position:0% is not a good Trader you can take the opposite<00:15:20.279> position 00:15:21.889 --> 00:15:21.899 align:start position:0% opposite position 00:15:21.899 --> 00:15:22.790 align:start position:0% opposite position um 00:15:22.790 --> 00:15:22.800 align:start position:0% um 00:15:22.800 --> 00:15:24.769 align:start position:0% um then<00:15:23.279> of<00:15:23.459> course<00:15:23.579> there's<00:15:23.880> there's<00:15:24.240> so<00:15:24.660> many 00:15:24.769 --> 00:15:24.779 align:start position:0% then of course there's there's so many 00:15:24.779 --> 00:15:26.150 align:start position:0% then of course there's there's so many types<00:15:25.139> of<00:15:25.199> machine<00:15:25.380> learning<00:15:25.800> algorithms 00:15:26.150 --> 00:15:26.160 align:start position:0% types of machine learning algorithms 00:15:26.160 --> 00:15:28.310 align:start position:0% types of machine learning algorithms time<00:15:26.399> series<00:15:26.579> predictions<00:15:27.180> uh<00:15:27.720> the<00:15:27.839> list<00:15:28.019> goes 00:15:28.310 --> 00:15:28.320 align:start position:0% time series predictions uh the list goes 00:15:28.320 --> 00:15:30.110 align:start position:0% time series predictions uh the list goes on<00:15:28.380> and<00:15:28.500> on<00:15:28.620> for<00:15:28.860> the<00:15:29.160> types<00:15:29.399> you<00:15:29.519> can<00:15:29.639> do<00:15:29.699> and 00:15:30.110 --> 00:15:30.120 align:start position:0% on and on for the types you can do and 00:15:30.120 --> 00:15:32.150 align:start position:0% on and on for the types you can do and again<00:15:30.240> I<00:15:30.480> know<00:15:30.600> we're<00:15:30.720> focused<00:15:31.139> on<00:15:31.260> on<00:15:31.440> D5<00:15:31.860> for 00:15:32.150 --> 00:15:32.160 align:start position:0% again I know we're focused on on D5 for 00:15:32.160 --> 00:15:33.470 align:start position:0% again I know we're focused on on D5 for that<00:15:32.279> presentation<00:15:32.699> this<00:15:33.120> presentation 00:15:33.470 --> 00:15:33.480 align:start position:0% that presentation this presentation 00:15:33.480 --> 00:15:34.910 align:start position:0% that presentation this presentation because<00:15:33.720> that's<00:15:33.959> mostly<00:15:34.260> what<00:15:34.440> we<00:15:34.620> interact 00:15:34.910 --> 00:15:34.920 align:start position:0% because that's mostly what we interact 00:15:34.920 --> 00:15:36.949 align:start position:0% because that's mostly what we interact with<00:15:35.100> but<00:15:35.639> you<00:15:36.120> know<00:15:36.180> if<00:15:36.360> you're<00:15:36.480> really<00:15:36.660> into 00:15:36.949 --> 00:15:36.959 align:start position:0% with but you know if you're really into 00:15:36.959 --> 00:15:39.590 align:start position:0% with but you know if you're really into stable<00:15:37.740> diffusion<00:15:38.459> and<00:15:39.120> you<00:15:39.240> want<00:15:39.360> to<00:15:39.480> see 00:15:39.590 --> 00:15:39.600 align:start position:0% stable diffusion and you want to see 00:15:39.600 --> 00:15:41.750 align:start position:0% stable diffusion and you want to see text<00:15:39.899> generated<00:15:40.380> images<00:15:40.620> uh<00:15:41.519> you<00:15:41.699> could 00:15:41.750 --> 00:15:41.760 align:start position:0% text generated images uh you could 00:15:41.760 --> 00:15:44.030 align:start position:0% text generated images uh you could always<00:15:41.880> grab<00:15:42.300> you<00:15:42.600> know<00:15:42.720> uh<00:15:43.440> text<00:15:43.620> from<00:15:43.860> your 00:15:44.030 --> 00:15:44.040 align:start position:0% always grab you know uh text from your 00:15:44.040 --> 00:15:46.790 align:start position:0% always grab you know uh text from your lens<00:15:44.279> protocol<00:15:44.760> interactions<00:15:45.720> and<00:15:46.139> generate 00:15:46.790 --> 00:15:46.800 align:start position:0% lens protocol interactions and generate 00:15:46.800 --> 00:15:48.829 align:start position:0% lens protocol interactions and generate an<00:15:46.980> image<00:15:47.279> based<00:15:47.639> on<00:15:47.699> it<00:15:47.820> and<00:15:48.000> mint<00:15:48.180> and<00:15:48.360> nft<00:15:48.600> on 00:15:48.829 --> 00:15:48.839 align:start position:0% an image based on it and mint and nft on 00:15:48.839 --> 00:15:50.329 align:start position:0% an image based on it and mint and nft on chain<00:15:49.079> if<00:15:49.320> you<00:15:49.440> wanted<00:15:49.500> to<00:15:49.740> something<00:15:50.100> like 00:15:50.329 --> 00:15:50.339 align:start position:0% chain if you wanted to something like 00:15:50.339 --> 00:15:52.069 align:start position:0% chain if you wanted to something like that<00:15:50.579> you<00:15:51.120> know<00:15:51.180> that's<00:15:51.360> really<00:15:51.600> up<00:15:51.839> to<00:15:51.899> you 00:15:52.069 --> 00:15:52.079 align:start position:0% that you know that's really up to you 00:15:52.079 --> 00:15:54.350 align:start position:0% that you know that's really up to you because<00:15:52.920> all<00:15:53.459> this<00:15:53.579> computation<00:15:53.940> is<00:15:54.120> done<00:15:54.240> off 00:15:54.350 --> 00:15:54.360 align:start position:0% because all this computation is done off 00:15:54.360 --> 00:15:58.069 align:start position:0% because all this computation is done off chain<00:15:54.600> the<00:15:55.260> uh<00:15:55.560> the<00:15:56.220> sky<00:15:56.459> is<00:15:56.639> the<00:15:56.820> limit 00:15:58.069 --> 00:15:58.079 align:start position:0% chain the uh the sky is the limit 00:15:58.079 --> 00:16:04.629 align:start position:0% chain the uh the sky is the limit foreign 00:16:04.629 --> 00:16:04.639 align:start position:0% 00:16:04.639 --> 00:16:08.449 align:start position:0% cool<00:16:05.639> so<00:16:06.060> uh<00:16:06.360> quickly<00:16:06.660> just<00:16:06.899> on<00:16:07.320> the<00:16:07.800> uh<00:16:08.339> I 00:16:08.449 --> 00:16:08.459 align:start position:0% cool so uh quickly just on the uh I 00:16:08.459 --> 00:16:09.710 align:start position:0% cool so uh quickly just on the uh I guess<00:16:08.579> the<00:16:08.699> modeling<00:16:09.060> uh<00:16:09.300> we<00:16:09.480> didn't<00:16:09.540> we 00:16:09.710 --> 00:16:09.720 align:start position:0% guess the modeling uh we didn't we 00:16:09.720 --> 00:16:10.910 align:start position:0% guess the modeling uh we didn't we already<00:16:09.839> did<00:16:10.019> the<00:16:10.199> processing<00:16:10.620> I<00:16:10.800> guess 00:16:10.910 --> 00:16:10.920 align:start position:0% already did the processing I guess 00:16:10.920 --> 00:16:13.670 align:start position:0% already did the processing I guess earlier<00:16:11.519> when<00:16:11.820> we<00:16:12.060> uh<00:16:12.899> just<00:16:13.079> reformatted 00:16:13.670 --> 00:16:13.680 align:start position:0% earlier when we uh just reformatted 00:16:13.680 --> 00:16:15.949 align:start position:0% earlier when we uh just reformatted stuff<00:16:13.920> into<00:16:14.100> into<00:16:14.399> a<00:16:14.579> panda's<00:16:15.000> data<00:16:15.180> frame 00:16:15.949 --> 00:16:15.959 align:start position:0% stuff into into a panda's data frame 00:16:15.959 --> 00:16:18.230 align:start position:0% stuff into into a panda's data frame um<00:16:16.079> so<00:16:16.500> here's<00:16:16.740> it's<00:16:16.980> it's<00:16:17.100> quite<00:16:17.399> simple 00:16:18.230 --> 00:16:18.240 align:start position:0% um so here's it's it's quite simple 00:16:18.240 --> 00:16:19.550 align:start position:0% um so here's it's it's quite simple um if<00:16:18.480> you're<00:16:18.600> familiar<00:16:18.959> with<00:16:19.139> like<00:16:19.320> a<00:16:19.440> little 00:16:19.550 --> 00:16:19.560 align:start position:0% um if you're familiar with like a little 00:16:19.560 --> 00:16:21.710 align:start position:0% um if you're familiar with like a little bit<00:16:19.740> of<00:16:20.040> data<00:16:20.399> science<00:16:20.519> I'm<00:16:21.120> not<00:16:21.240> a<00:16:21.420> data 00:16:21.710 --> 00:16:21.720 align:start position:0% bit of data science I'm not a data 00:16:21.720 --> 00:16:22.910 align:start position:0% bit of data science I'm not a data scientist<00:16:22.019> myself 00:16:22.910 --> 00:16:22.920 align:start position:0% scientist myself 00:16:22.920 --> 00:16:25.069 align:start position:0% scientist myself um<00:16:22.980> but<00:16:23.279> what<00:16:23.880> we<00:16:24.000> do<00:16:24.120> is<00:16:24.240> we<00:16:24.360> basically<00:16:24.660> split 00:16:25.069 --> 00:16:25.079 align:start position:0% um but what we do is we basically split 00:16:25.079 --> 00:16:26.870 align:start position:0% um but what we do is we basically split uh<00:16:25.500> the<00:16:25.680> data<00:16:26.100> that<00:16:26.160> we<00:16:26.279> pulled<00:16:26.459> in<00:16:26.579> so<00:16:26.760> the 00:16:26.870 --> 00:16:26.880 align:start position:0% uh the data that we pulled in so the 00:16:26.880 --> 00:16:28.970 align:start position:0% uh the data that we pulled in so the Dune<00:16:27.120> data<00:16:27.360> and<00:16:27.420> the<00:16:27.540> graph<00:16:27.660> data<00:16:28.019> and<00:16:28.740> we 00:16:28.970 --> 00:16:28.980 align:start position:0% Dune data and the graph data and we 00:16:28.980 --> 00:16:31.189 align:start position:0% Dune data and the graph data and we split<00:16:29.279> it<00:16:29.339> into<00:16:29.459> a<00:16:29.639> train<00:16:29.820> and<00:16:30.240> test<00:16:30.420> set 00:16:31.189 --> 00:16:31.199 align:start position:0% split it into a train and test set 00:16:31.199 --> 00:16:33.790 align:start position:0% split it into a train and test set um<00:16:31.320> just<00:16:31.560> basically<00:16:31.860> 80<00:16:32.040> trained<00:16:32.820> 20<00:16:33.000> tests 00:16:33.790 --> 00:16:33.800 align:start position:0% um just basically 80 trained 20 tests 00:16:33.800 --> 00:16:35.870 align:start position:0% um just basically 80 trained 20 tests not<00:16:34.800> that<00:16:34.920> sophisticated 00:16:35.870 --> 00:16:35.880 align:start position:0% not that sophisticated 00:16:35.880 --> 00:16:37.790 align:start position:0% not that sophisticated um<00:16:35.940> and<00:16:36.660> then<00:16:36.779> what<00:16:37.079> we<00:16:37.139> plot<00:16:37.440> it<00:16:37.560> and<00:16:37.680> we'll 00:16:37.790 --> 00:16:37.800 align:start position:0% um and then what we plot it and we'll 00:16:37.800 --> 00:16:39.290 align:start position:0% um and then what we plot it and we'll show<00:16:38.519> um<00:16:38.579> you<00:16:38.759> know<00:16:38.820> we'll<00:16:38.940> show<00:16:39.060> the<00:16:39.180> results 00:16:39.290 --> 00:16:39.300 align:start position:0% show um you know we'll show the results 00:16:39.300 --> 00:16:41.990 align:start position:0% show um you know we'll show the results after<00:16:39.600> and<00:16:40.199> then<00:16:40.380> we<00:16:40.500> run<00:16:40.680> it<00:16:40.860> through<00:16:41.100> a<00:16:41.519> Arma 00:16:41.990 --> 00:16:42.000 align:start position:0% after and then we run it through a Arma 00:16:42.000 --> 00:16:44.389 align:start position:0% after and then we run it through a Arma model<00:16:42.120> so<00:16:42.480> uh<00:16:42.959> Auto<00:16:43.380> regressive<00:16:43.980> moving 00:16:44.389 --> 00:16:44.399 align:start position:0% model so uh Auto regressive moving 00:16:44.399 --> 00:16:47.030 align:start position:0% model so uh Auto regressive moving average<00:16:44.519> model<00:16:44.880> to<00:16:45.420> essentially<00:16:45.779> predict 00:16:47.030 --> 00:16:47.040 align:start position:0% average model to essentially predict 00:16:47.040 --> 00:16:49.249 align:start position:0% average model to essentially predict um<00:16:47.100> so<00:16:47.699> we're<00:16:47.880> doing<00:16:48.000> this<00:16:48.120> by<00:16:48.240> hour<00:16:48.480> and<00:16:49.139> the 00:16:49.249 --> 00:16:49.259 align:start position:0% um so we're doing this by hour and the 00:16:49.259 --> 00:16:50.930 align:start position:0% um so we're doing this by hour and the goal<00:16:49.500> here<00:16:49.560> is<00:16:49.680> to<00:16:49.920> predict 00:16:50.930 --> 00:16:50.940 align:start position:0% goal here is to predict 00:16:50.940 --> 00:16:54.050 align:start position:0% goal here is to predict um<00:16:51.000> whether<00:16:51.480> the<00:16:52.019> uh<00:16:52.440> the<00:16:52.740> price<00:16:52.800> of<00:16:53.040> eth<00:16:53.399> in 00:16:54.050 --> 00:16:54.060 align:start position:0% um whether the uh the price of eth in 00:16:54.060 --> 00:16:56.470 align:start position:0% um whether the uh the price of eth in USD<00:16:54.480> is<00:16:54.600> going<00:16:54.720> to<00:16:54.839> go<00:16:54.959> up<00:16:55.199> in<00:16:55.740> the<00:16:55.800> next<00:16:55.920> hour 00:16:56.470 --> 00:16:56.480 align:start position:0% USD is going to go up in the next hour 00:16:56.480 --> 00:16:59.509 align:start position:0% USD is going to go up in the next hour and<00:16:57.480> so<00:16:58.079> the<00:16:58.259> logic<00:16:58.500> here<00:16:58.680> is<00:16:58.860> basically<00:16:59.160> just 00:16:59.509 --> 00:16:59.519 align:start position:0% and so the logic here is basically just 00:16:59.519 --> 00:17:02.030 align:start position:0% and so the logic here is basically just uh<00:17:00.300> if<00:17:00.600> the<00:17:00.779> next<00:17:00.899> hour<00:17:01.139> price<00:17:01.500> is<00:17:01.800> greater 00:17:02.030 --> 00:17:02.040 align:start position:0% uh if the next hour price is greater 00:17:02.040 --> 00:17:04.429 align:start position:0% uh if the next hour price is greater than<00:17:02.220> the<00:17:02.399> last<00:17:02.519> price<00:17:02.820> then<00:17:03.480> we<00:17:03.779> want<00:17:03.899> want<00:17:04.260> to 00:17:04.429 --> 00:17:04.439 align:start position:0% than the last price then we want want to 00:17:04.439 --> 00:17:06.829 align:start position:0% than the last price then we want want to buy<00:17:04.559> you<00:17:04.740> if<00:17:05.640> it's<00:17:05.760> less<00:17:06.000> then<00:17:06.299> we<00:17:06.540> want<00:17:06.720> to 00:17:06.829 --> 00:17:06.839 align:start position:0% buy you if it's less then we want to 00:17:06.839 --> 00:17:09.710 align:start position:0% buy you if it's less then we want to sell<00:17:07.140> or<00:17:07.799> short<00:17:08.040> or<00:17:08.459> what<00:17:08.699> have<00:17:08.880> you<00:17:09.059> it's<00:17:09.419> that 00:17:09.710 --> 00:17:09.720 align:start position:0% sell or short or what have you it's that 00:17:09.720 --> 00:17:13.850 align:start position:0% sell or short or what have you it's that easy<00:17:09.959> folks 00:17:13.850 --> 00:17:13.860 align:start position:0% 00:17:13.860 --> 00:17:16.850 align:start position:0% not<00:17:14.220> Financial<00:17:14.520> advice 00:17:16.850 --> 00:17:16.860 align:start position:0% not Financial advice 00:17:16.860 --> 00:17:18.650 align:start position:0% not Financial advice cool<00:17:17.459> yeah<00:17:17.640> these<00:17:17.880> are<00:17:18.000> the<00:17:18.059> results<00:17:18.179> so<00:17:18.419> as 00:17:18.650 --> 00:17:18.660 align:start position:0% cool yeah these are the results so as 00:17:18.660 --> 00:17:21.949 align:start position:0% cool yeah these are the results so as you<00:17:18.780> can<00:17:18.900> see<00:17:19.079> the<00:17:19.799> so<00:17:20.459> the<00:17:20.699> red<00:17:20.880> here<00:17:21.120> is<00:17:21.540> the 00:17:21.949 --> 00:17:21.959 align:start position:0% you can see the so the red here is the 00:17:21.959 --> 00:17:23.689 align:start position:0% you can see the so the red here is the test<00:17:22.380> set 00:17:23.689 --> 00:17:23.699 align:start position:0% test set 00:17:23.699 --> 00:17:26.510 align:start position:0% test set um<00:17:23.760> and<00:17:24.720> we<00:17:25.199> are<00:17:25.380> basically<00:17:25.740> you<00:17:26.220> know<00:17:26.339> the 00:17:26.510 --> 00:17:26.520 align:start position:0% um and we are basically you know the 00:17:26.520 --> 00:17:27.470 align:start position:0% um and we are basically you know the prediction<00:17:26.819> is<00:17:27.000> basically<00:17:27.240> saying<00:17:27.419> it's 00:17:27.470 --> 00:17:27.480 align:start position:0% prediction is basically saying it's 00:17:27.480 --> 00:17:29.330 align:start position:0% prediction is basically saying it's trading<00:17:27.839> sideways<00:17:28.380> uh<00:17:28.679> maybe<00:17:28.860> I<00:17:29.160> think<00:17:29.220> it 00:17:29.330 --> 00:17:29.340 align:start position:0% trading sideways uh maybe I think it 00:17:29.340 --> 00:17:31.130 align:start position:0% trading sideways uh maybe I think it probably<00:17:29.520> goes<00:17:29.820> down<00:17:29.880> about<00:17:30.059> 10<00:17:30.360> uh<00:17:30.840> ten 00:17:31.130 --> 00:17:31.140 align:start position:0% probably goes down about 10 uh ten 00:17:31.140 --> 00:17:34.370 align:start position:0% probably goes down about 10 uh ten dollars<00:17:31.440> roughly<00:17:32.000> uh<00:17:33.000> if<00:17:33.179> anyone<00:17:33.419> knows<00:17:33.840> uh 00:17:34.370 --> 00:17:34.380 align:start position:0% dollars roughly uh if anyone knows uh 00:17:34.380 --> 00:17:36.710 align:start position:0% dollars roughly uh if anyone knows uh the<00:17:34.620> crab<00:17:34.860> strategy<00:17:35.400> on<00:17:35.880> and<00:17:36.179> squeeze<00:17:36.600> this 00:17:36.710 --> 00:17:36.720 align:start position:0% the crab strategy on and squeeze this 00:17:36.720 --> 00:17:39.230 align:start position:0% the crab strategy on and squeeze this would<00:17:36.840> be<00:17:36.960> a<00:17:37.140> good<00:17:37.260> time<00:17:37.380> to<00:17:37.500> use<00:17:37.620> it<00:17:37.799> I<00:17:37.980> guess 00:17:39.230 --> 00:17:39.240 align:start position:0% would be a good time to use it I guess 00:17:39.240 --> 00:17:43.810 align:start position:0% would be a good time to use it I guess um yeah<00:17:39.600> these<00:17:39.900> are<00:17:39.960> just<00:17:40.080> the<00:17:40.260> results 00:17:43.810 --> 00:17:43.820 align:start position:0% 00:17:43.820 --> 00:17:47.390 align:start position:0% yeah<00:17:44.820> so<00:17:45.120> the<00:17:45.419> most<00:17:46.080> web<00:17:46.500> three<00:17:46.860> relevant 00:17:47.390 --> 00:17:47.400 align:start position:0% yeah so the most web three relevant 00:17:47.400 --> 00:17:49.789 align:start position:0% yeah so the most web three relevant probably<00:17:47.760> the<00:17:48.059> most<00:17:48.240> complicated 00:17:49.789 --> 00:17:49.799 align:start position:0% probably the most complicated 00:17:49.799 --> 00:17:52.909 align:start position:0% probably the most complicated um Step<00:17:50.580> uh<00:17:51.240> in<00:17:51.600> automation<00:17:52.080> here<00:17:52.500> is 00:17:52.909 --> 00:17:52.919 align:start position:0% um Step uh in automation here is 00:17:52.919 --> 00:17:55.070 align:start position:0% um Step uh in automation here is transaction<00:17:53.340> execution 00:17:55.070 --> 00:17:55.080 align:start position:0% transaction execution 00:17:55.080 --> 00:17:58.250 align:start position:0% transaction execution so<00:17:55.679> there's<00:17:56.100> a<00:17:56.880> number<00:17:57.240> of<00:17:57.419> ways<00:17:57.780> to<00:17:57.900> do<00:17:58.020> it<00:17:58.140> so 00:17:58.250 --> 00:17:58.260 align:start position:0% so there's a number of ways to do it so 00:17:58.260 --> 00:18:00.830 align:start position:0% so there's a number of ways to do it so bringing<00:17:58.620> these<00:17:58.860> insights<00:17:59.400> back<00:17:59.580> on<00:17:59.760> chain 00:18:00.830 --> 00:18:00.840 align:start position:0% bringing these insights back on chain 00:18:00.840 --> 00:18:02.570 align:start position:0% bringing these insights back on chain um<00:18:00.960> so<00:18:01.140> there's<00:18:01.380> there's<00:18:01.620> tons<00:18:02.160> of 00:18:02.570 --> 00:18:02.580 align:start position:0% um so there's there's tons of 00:18:02.580 --> 00:18:05.390 align:start position:0% um so there's there's tons of considerations<00:18:03.240> uh<00:18:03.960> to<00:18:04.140> think<00:18:04.260> about<00:18:04.440> uh 00:18:05.390 --> 00:18:05.400 align:start position:0% considerations uh to think about uh 00:18:05.400 --> 00:18:07.730 align:start position:0% considerations uh to think about uh which<00:18:05.640> chains<00:18:06.059> you're<00:18:06.179> operating<00:18:06.600> on<00:18:06.960> is<00:18:07.500> the 00:18:07.730 --> 00:18:07.740 align:start position:0% which chains you're operating on is the 00:18:07.740 --> 00:18:09.650 align:start position:0% which chains you're operating on is the environment<00:18:08.220> adversarial<00:18:08.940> so<00:18:09.179> are<00:18:09.360> you<00:18:09.480> you 00:18:09.650 --> 00:18:09.660 align:start position:0% environment adversarial so are you you 00:18:09.660 --> 00:18:11.750 align:start position:0% environment adversarial so are you you know<00:18:09.780> if<00:18:09.900> you're<00:18:10.020> working<00:18:10.140> in<00:18:10.380> D5<00:18:10.740> then<00:18:11.100> you're 00:18:11.750 --> 00:18:11.760 align:start position:0% know if you're working in D5 then you're 00:18:11.760 --> 00:18:14.029 align:start position:0% know if you're working in D5 then you're probably<00:18:12.000> looking<00:18:12.480> out<00:18:12.840> for<00:18:13.200> Mev<00:18:13.860> and 00:18:14.029 --> 00:18:14.039 align:start position:0% probably looking out for Mev and 00:18:14.039 --> 00:18:15.950 align:start position:0% probably looking out for Mev and sandwich<00:18:14.220> attacks<00:18:14.880> anybody<00:18:15.480> trying<00:18:15.780> to 00:18:15.950 --> 00:18:15.960 align:start position:0% sandwich attacks anybody trying to 00:18:15.960 --> 00:18:17.450 align:start position:0% sandwich attacks anybody trying to exploit<00:18:16.380> your<00:18:16.500> model 00:18:17.450 --> 00:18:17.460 align:start position:0% exploit your model 00:18:17.460 --> 00:18:20.090 align:start position:0% exploit your model um<00:18:17.520> if<00:18:17.760> you're<00:18:17.940> you<00:18:18.299> know<00:18:18.419> minting<00:18:19.200> nfts<00:18:19.860> for 00:18:20.090 --> 00:18:20.100 align:start position:0% um if you're you know minting nfts for 00:18:20.100 --> 00:18:22.310 align:start position:0% um if you're you know minting nfts for art<00:18:20.280> purposes<00:18:20.820> and<00:18:21.299> not<00:18:21.419> for<00:18:21.780> financial 00:18:22.310 --> 00:18:22.320 align:start position:0% art purposes and not for financial 00:18:22.320 --> 00:18:24.650 align:start position:0% art purposes and not for financial purposes<00:18:22.980> it's<00:18:23.640> probably<00:18:23.880> less<00:18:24.179> of<00:18:24.360> a<00:18:24.539> big 00:18:24.650 --> 00:18:24.660 align:start position:0% purposes it's probably less of a big 00:18:24.660 --> 00:18:27.169 align:start position:0% purposes it's probably less of a big deal<00:18:24.780> that<00:18:25.080> someone<00:18:25.200> front<00:18:25.440> runs<00:18:25.860> you<00:18:25.940> uh<00:18:26.940> what 00:18:27.169 --> 00:18:27.179 align:start position:0% deal that someone front runs you uh what 00:18:27.179 --> 00:18:28.669 align:start position:0% deal that someone front runs you uh what kind<00:18:27.240> of<00:18:27.360> timeline<00:18:27.660> are<00:18:27.900> you<00:18:28.020> operating<00:18:28.320> on 00:18:28.669 --> 00:18:28.679 align:start position:0% kind of timeline are you operating on 00:18:28.679 --> 00:18:30.110 align:start position:0% kind of timeline are you operating on and<00:18:29.160> you<00:18:29.340> know<00:18:29.400> some<00:18:29.580> things<00:18:29.700> have<00:18:29.880> much 00:18:30.110 --> 00:18:30.120 align:start position:0% and you know some things have much 00:18:30.120 --> 00:18:31.909 align:start position:0% and you know some things have much larger<00:18:30.419> delays<00:18:30.720> than<00:18:30.840> others<00:18:31.140> a<00:18:31.740> key 00:18:31.909 --> 00:18:31.919 align:start position:0% larger delays than others a key 00:18:31.919 --> 00:18:33.110 align:start position:0% larger delays than others a key management<00:18:32.160> do<00:18:32.460> you<00:18:32.580> want<00:18:32.640> to<00:18:32.760> manage<00:18:33.000> your 00:18:33.110 --> 00:18:33.120 align:start position:0% management do you want to manage your 00:18:33.120 --> 00:18:34.610 align:start position:0% management do you want to manage your own<00:18:33.240> Keys<00:18:33.539> what<00:18:33.720> kind<00:18:33.900> of<00:18:33.960> permissions<00:18:34.320> do 00:18:34.610 --> 00:18:34.620 align:start position:0% own Keys what kind of permissions do 00:18:34.620 --> 00:18:37.310 align:start position:0% own Keys what kind of permissions do those<00:18:34.860> keys<00:18:35.280> have<00:18:35.600> should<00:18:36.600> your<00:18:36.780> logic<00:18:37.140> be 00:18:37.310 --> 00:18:37.320 align:start position:0% those keys have should your logic be 00:18:37.320 --> 00:18:38.510 align:start position:0% those keys have should your logic be transparent<00:18:37.799> so<00:18:38.039> you<00:18:38.280> know<00:18:38.340> if<00:18:38.400> you're 00:18:38.510 --> 00:18:38.520 align:start position:0% transparent so you know if you're 00:18:38.520 --> 00:18:40.850 align:start position:0% transparent so you know if you're running<00:18:38.640> a<00:18:38.880> proprietary<00:18:39.360> training<00:18:39.840> algorithm 00:18:40.850 --> 00:18:40.860 align:start position:0% running a proprietary training algorithm 00:18:40.860 --> 00:18:42.650 align:start position:0% running a proprietary training algorithm um<00:18:40.980> you<00:18:41.160> probably<00:18:41.280> want<00:18:41.580> that<00:18:41.760> to<00:18:41.940> be<00:18:42.120> executed 00:18:42.650 --> 00:18:42.660 align:start position:0% um you probably want that to be executed 00:18:42.660 --> 00:18:43.850 align:start position:0% um you probably want that to be executed off<00:18:42.840> chain<00:18:43.020> and<00:18:43.200> just<00:18:43.380> have<00:18:43.500> the<00:18:43.679> results 00:18:43.850 --> 00:18:43.860 align:start position:0% off chain and just have the results 00:18:43.860 --> 00:18:46.490 align:start position:0% off chain and just have the results posted<00:18:44.400> to<00:18:44.520> the<00:18:44.640> chain<00:18:44.960> but<00:18:45.960> if<00:18:46.380> you're 00:18:46.490 --> 00:18:46.500 align:start position:0% posted to the chain but if you're 00:18:46.500 --> 00:18:47.810 align:start position:0% posted to the chain but if you're running<00:18:46.740> something<00:18:46.919> that<00:18:47.220> you<00:18:47.460> want<00:18:47.580> to<00:18:47.700> be 00:18:47.810 --> 00:18:47.820 align:start position:0% running something that you want to be 00:18:47.820 --> 00:18:50.330 align:start position:0% running something that you want to be transparent<00:18:48.419> uh<00:18:48.960> you<00:18:49.140> you<00:18:49.320> would<00:18:49.620> likely<00:18:49.980> want 00:18:50.330 --> 00:18:50.340 align:start position:0% transparent uh you you would likely want 00:18:50.340 --> 00:18:53.090 align:start position:0% transparent uh you you would likely want the<00:18:50.880> the<00:18:51.179> you<00:18:51.780> know<00:18:51.900> computation<00:18:52.799> to<00:18:52.980> be 00:18:53.090 --> 00:18:53.100 align:start position:0% the the you know computation to be 00:18:53.100 --> 00:18:54.890 align:start position:0% the the you know computation to be visible<00:18:53.340> on<00:18:53.580> chain<00:18:53.820> uh<00:18:54.600> you<00:18:54.720> know<00:18:54.840> what 00:18:54.890 --> 00:18:54.900 align:start position:0% visible on chain uh you know what 00:18:54.900 --> 00:18:57.169 align:start position:0% visible on chain uh you know what happened<00:18:55.020> of<00:18:55.500> a<00:18:55.679> transaction<00:18:55.980> fails<00:18:56.580> if<00:18:57.000> it's 00:18:57.169 --> 00:18:57.179 align:start position:0% happened of a transaction fails if it's 00:18:57.179 --> 00:18:59.690 align:start position:0% happened of a transaction fails if it's or<00:18:57.539> it's<00:18:57.720> congested<00:18:58.340> these<00:18:59.340> are<00:18:59.400> things<00:18:59.520> that 00:18:59.690 --> 00:18:59.700 align:start position:0% or it's congested these are things that 00:18:59.700 --> 00:19:02.210 align:start position:0% or it's congested these are things that are<00:18:59.820> annoying<00:19:00.179> for<00:19:00.539> manual<00:19:01.020> transactions<00:19:01.919> but 00:19:02.210 --> 00:19:02.220 align:start position:0% are annoying for manual transactions but 00:19:02.220 --> 00:19:03.770 align:start position:0% are annoying for manual transactions but if<00:19:02.700> you're<00:19:02.820> not<00:19:03.059> taking<00:19:03.240> them<00:19:03.419> in<00:19:03.600> account 00:19:03.770 --> 00:19:03.780 align:start position:0% if you're not taking them in account 00:19:03.780 --> 00:19:05.450 align:start position:0% if you're not taking them in account when<00:19:04.080> you're<00:19:04.200> automating<00:19:04.500> transactions<00:19:05.160> you 00:19:05.450 --> 00:19:05.460 align:start position:0% when you're automating transactions you 00:19:05.460 --> 00:19:06.890 align:start position:0% when you're automating transactions you can<00:19:05.580> get<00:19:05.700> something<00:19:05.880> stuck<00:19:06.120> in<00:19:06.299> the<00:19:06.480> mempool 00:19:06.890 --> 00:19:06.900 align:start position:0% can get something stuck in the mempool 00:19:06.900 --> 00:19:08.810 align:start position:0% can get something stuck in the mempool forever<00:19:07.260> you<00:19:07.799> can<00:19:07.919> potentially<00:19:08.220> end<00:19:08.460> up<00:19:08.580> not 00:19:08.810 --> 00:19:08.820 align:start position:0% forever you can potentially end up not 00:19:08.820 --> 00:19:10.669 align:start position:0% forever you can potentially end up not being<00:19:08.940> able<00:19:09.120> to<00:19:09.240> to<00:19:09.539> transact<00:19:10.020> if<00:19:10.380> you're<00:19:10.500> not 00:19:10.669 --> 00:19:10.679 align:start position:0% being able to to transact if you're not 00:19:10.679 --> 00:19:12.770 align:start position:0% being able to to transact if you're not you<00:19:11.160> know<00:19:11.220> replacing<00:19:11.700> that<00:19:11.940> transaction<00:19:12.419> and 00:19:12.770 --> 00:19:12.780 align:start position:0% you know replacing that transaction and 00:19:12.780 --> 00:19:14.510 align:start position:0% you know replacing that transaction and replacing<00:19:13.380> that<00:19:13.500> nonce 00:19:14.510 --> 00:19:14.520 align:start position:0% replacing that nonce 00:19:14.520 --> 00:19:16.190 align:start position:0% replacing that nonce um<00:19:14.580> so<00:19:14.700> there's<00:19:14.880> there's<00:19:15.179> a<00:19:15.299> bunch<00:19:15.419> of<00:19:15.480> options 00:19:16.190 --> 00:19:16.200 align:start position:0% um so there's there's a bunch of options 00:19:16.200 --> 00:19:19.490 align:start position:0% um so there's there's a bunch of options um<00:19:16.320> there<00:19:16.679> are<00:19:16.980> almost<00:19:17.640> certainly<00:19:18.380> others<00:19:19.380> as 00:19:19.490 --> 00:19:19.500 align:start position:0% um there are almost certainly others as 00:19:19.500 --> 00:19:21.409 align:start position:0% um there are almost certainly others as well<00:19:19.679> and<00:19:20.400> these<00:19:20.640> are<00:19:20.760> not<00:19:20.940> necessarily 00:19:21.409 --> 00:19:21.419 align:start position:0% well and these are not necessarily 00:19:21.419 --> 00:19:22.850 align:start position:0% well and these are not necessarily mutually<00:19:21.720> exclusive<00:19:22.200> they're<00:19:22.440> just<00:19:22.620> kind<00:19:22.799> of 00:19:22.850 --> 00:19:22.860 align:start position:0% mutually exclusive they're just kind of 00:19:22.860 --> 00:19:24.830 align:start position:0% mutually exclusive they're just kind of ideas<00:19:23.100> of<00:19:23.400> part<00:19:23.760> of<00:19:23.880> it<00:19:24.000> so<00:19:24.240> you<00:19:24.720> know 00:19:24.830 --> 00:19:24.840 align:start position:0% ideas of part of it so you know 00:19:24.840 --> 00:19:27.409 align:start position:0% ideas of part of it so you know libraries<00:19:25.679> that<00:19:25.860> wrap<00:19:26.039> on<00:19:26.340> top<00:19:26.520> of<00:19:26.760> uh<00:19:27.240> you 00:19:27.409 --> 00:19:27.419 align:start position:0% libraries that wrap on top of uh you 00:19:27.419 --> 00:19:29.590 align:start position:0% libraries that wrap on top of uh you know<00:19:27.480> the<00:19:27.780> wallet<00:19:28.380> apis 00:19:29.590 --> 00:19:29.600 align:start position:0% know the wallet apis 00:19:29.600 --> 00:19:33.310 align:start position:0% know the wallet apis that<00:19:30.600> translate<00:19:31.080> Json<00:19:31.919> RPC 00:19:33.310 --> 00:19:33.320 align:start position:0% that translate Json RPC 00:19:33.320 --> 00:19:36.590 align:start position:0% that translate Json RPC ethers<00:19:34.320> web3js<00:19:35.160> web3pi<00:19:36.000> which<00:19:36.179> we're<00:19:36.299> using 00:19:36.590 --> 00:19:36.600 align:start position:0% ethers web3js web3pi which we're using 00:19:36.600 --> 00:19:38.930 align:start position:0% ethers web3js web3pi which we're using in<00:19:36.900> this<00:19:37.080> example<00:19:37.440> uh<00:19:38.280> if<00:19:38.640> you're<00:19:38.700> running 00:19:38.930 --> 00:19:38.940 align:start position:0% in this example uh if you're running 00:19:38.940 --> 00:19:40.669 align:start position:0% in this example uh if you're running something<00:19:39.299> like<00:19:39.539> that<00:19:39.660> it's<00:19:39.960> probably<00:19:40.200> in 00:19:40.669 --> 00:19:40.679 align:start position:0% something like that it's probably in 00:19:40.679 --> 00:19:42.289 align:start position:0% something like that it's probably in some<00:19:40.919> sort<00:19:41.039> of<00:19:41.160> function<00:19:41.460> that<00:19:42.059> you<00:19:42.240> can 00:19:42.289 --> 00:19:42.299 align:start position:0% some sort of function that you can 00:19:42.299 --> 00:19:44.330 align:start position:0% some sort of function that you can either<00:19:42.419> be<00:19:42.660> running<00:19:42.840> you<00:19:43.320> know<00:19:43.380> locally<00:19:43.740> or<00:19:44.100> on 00:19:44.330 --> 00:19:44.340 align:start position:0% either be running you know locally or on 00:19:44.340 --> 00:19:45.830 align:start position:0% either be running you know locally or on a<00:19:44.460> cloud 00:19:45.830 --> 00:19:45.840 align:start position:0% a cloud 00:19:45.840 --> 00:19:47.690 align:start position:0% a cloud um<00:19:45.960> you<00:19:46.320> can<00:19:46.440> you<00:19:46.799> know<00:19:46.919> use<00:19:47.160> traditional 00:19:47.690 --> 00:19:47.700 align:start position:0% um you can you know use traditional 00:19:47.700 --> 00:19:49.789 align:start position:0% um you can you know use traditional cloud<00:19:48.000> service<00:19:48.240> providers<00:19:48.840> or<00:19:49.320> you<00:19:49.740> know 00:19:49.789 --> 00:19:49.799 align:start position:0% cloud service providers or you know 00:19:49.799 --> 00:19:51.950 align:start position:0% cloud service providers or you know tenderly<00:19:50.340> has<00:19:50.640> their<00:19:50.880> new<00:19:51.000> web<00:19:51.179> three<00:19:51.480> actions 00:19:51.950 --> 00:19:51.960 align:start position:0% tenderly has their new web three actions 00:19:51.960 --> 00:19:55.150 align:start position:0% tenderly has their new web three actions which<00:19:52.320> is<00:19:52.620> effectively<00:19:53.520> lambdas<00:19:54.120> for 00:19:55.150 --> 00:19:55.160 align:start position:0% which is effectively lambdas for 00:19:55.160 --> 00:19:58.310 align:start position:0% which is effectively lambdas for for<00:19:56.160> for<00:19:56.460> web<00:19:56.820> 3<00:19:57.120> interactions<00:19:57.900> to<00:19:58.140> be 00:19:58.310 --> 00:19:58.320 align:start position:0% for for web 3 interactions to be 00:19:58.320 --> 00:20:00.169 align:start position:0% for for web 3 interactions to be triggered<00:19:58.919> by<00:19:59.039> events 00:20:00.169 --> 00:20:00.179 align:start position:0% triggered by events 00:20:00.179 --> 00:20:03.230 align:start position:0% triggered by events um<00:20:00.299> keeper<00:20:00.900> networks<00:20:01.380> uh<00:20:01.799> so<00:20:02.039> you<00:20:02.820> can<00:20:02.940> some 00:20:03.230 --> 00:20:03.240 align:start position:0% um keeper networks uh so you can some 00:20:03.240 --> 00:20:04.909 align:start position:0% um keeper networks uh so you can some keep<00:20:03.480> your<00:20:03.600> networks<00:20:04.080> support<00:20:04.260> like<00:20:04.679> more 00:20:04.909 --> 00:20:04.919 align:start position:0% keep your networks support like more 00:20:04.919 --> 00:20:07.250 align:start position:0% keep your networks support like more complex<00:20:05.280> off-chain<00:20:05.880> logic<00:20:06.780> um<00:20:06.780> some<00:20:06.960> only 00:20:07.250 --> 00:20:07.260 align:start position:0% complex off-chain logic um some only 00:20:07.260 --> 00:20:09.590 align:start position:0% complex off-chain logic um some only support<00:20:07.620> uh<00:20:08.580> triggering<00:20:09.120> you<00:20:09.539> know 00:20:09.590 --> 00:20:09.600 align:start position:0% support uh triggering you know 00:20:09.600 --> 00:20:12.350 align:start position:0% support uh triggering you know transactions<00:20:10.320> with<00:20:10.500> a<00:20:10.620> function<00:20:10.860> signature 00:20:12.350 --> 00:20:12.360 align:start position:0% transactions with a function signature 00:20:12.360 --> 00:20:13.789 align:start position:0% transactions with a function signature um 00:20:13.789 --> 00:20:13.799 align:start position:0% um 00:20:13.799 --> 00:20:15.950 align:start position:0% um uh 00:20:15.950 --> 00:20:15.960 align:start position:0% uh 00:20:15.960 --> 00:20:19.250 align:start position:0% uh there<00:20:16.440> are<00:20:16.559> transaction<00:20:16.919> execution<00:20:17.520> Services 00:20:19.250 --> 00:20:19.260 align:start position:0% there are transaction execution Services 00:20:19.260 --> 00:20:22.370 align:start position:0% there are transaction execution Services um so<00:20:19.559> something<00:20:19.860> like<00:20:20.220> uh<00:20:20.940> open<00:20:21.179> Zeppelin<00:20:21.840> uh 00:20:22.370 --> 00:20:22.380 align:start position:0% um so something like uh open Zeppelin uh 00:20:22.380 --> 00:20:25.190 align:start position:0% um so something like uh open Zeppelin uh Defender<00:20:22.679> relay<00:20:23.240> and<00:20:24.240> uh<00:20:24.660> inferior 00:20:25.190 --> 00:20:25.200 align:start position:0% Defender relay and uh inferior 00:20:25.200 --> 00:20:28.070 align:start position:0% Defender relay and uh inferior transaction<00:20:25.620> Services<00:20:26.299> they<00:20:27.299> handle<00:20:27.660> a<00:20:27.960> lot 00:20:28.070 --> 00:20:28.080 align:start position:0% transaction Services they handle a lot 00:20:28.080 --> 00:20:30.169 align:start position:0% transaction Services they handle a lot of<00:20:28.200> these<00:20:28.500> questions<00:20:28.799> that<00:20:29.400> are<00:20:29.580> kind<00:20:30.059> of 00:20:30.169 --> 00:20:30.179 align:start position:0% of these questions that are kind of 00:20:30.179 --> 00:20:32.090 align:start position:0% of these questions that are kind of annoying<00:20:30.600> for<00:20:31.020> for<00:20:31.260> a<00:20:31.559> small<00:20:31.740> development 00:20:32.090 --> 00:20:32.100 align:start position:0% annoying for for a small development 00:20:32.100 --> 00:20:34.430 align:start position:0% annoying for for a small development team<00:20:32.280> to<00:20:32.580> deal<00:20:33.000> with<00:20:33.120> so<00:20:33.419> things<00:20:33.660> like<00:20:33.960> Key 00:20:34.430 --> 00:20:34.440 align:start position:0% team to deal with so things like Key 00:20:34.440 --> 00:20:36.409 align:start position:0% team to deal with so things like Key Management<00:20:34.740> they<00:20:35.460> allow<00:20:35.760> you<00:20:35.820> to<00:20:35.940> hook<00:20:36.059> into<00:20:36.240> a 00:20:36.409 --> 00:20:36.419 align:start position:0% Management they allow you to hook into a 00:20:36.419 --> 00:20:38.330 align:start position:0% Management they allow you to hook into a KMS<00:20:36.840> system 00:20:38.330 --> 00:20:38.340 align:start position:0% KMS system 00:20:38.340 --> 00:20:41.330 align:start position:0% KMS system um<00:20:38.400> they<00:20:38.880> also<00:20:39.240> handle<00:20:39.720> you<00:20:40.140> know<00:20:40.200> gas<00:20:40.740> uh 00:20:41.330 --> 00:20:41.340 align:start position:0% um they also handle you know gas uh 00:20:41.340 --> 00:20:43.370 align:start position:0% um they also handle you know gas uh figuring<00:20:41.760> out<00:20:41.880> gas<00:20:42.059> fees<00:20:42.480> so<00:20:42.780> if<00:20:43.200> a 00:20:43.370 --> 00:20:43.380 align:start position:0% figuring out gas fees so if a 00:20:43.380 --> 00:20:45.529 align:start position:0% figuring out gas fees so if a transaction<00:20:43.799> fails<00:20:44.280> and<00:20:44.460> the<00:20:44.640> first<00:20:44.760> or<00:20:45.120> a 00:20:45.529 --> 00:20:45.539 align:start position:0% transaction fails and the first or a 00:20:45.539 --> 00:20:48.350 align:start position:0% transaction fails and the first or a transaction<00:20:46.080> is<00:20:46.320> is<00:20:47.160> um<00:20:47.160> waiting<00:20:47.880> too<00:20:48.000> long<00:20:48.179> in 00:20:48.350 --> 00:20:48.360 align:start position:0% transaction is is um waiting too long in 00:20:48.360 --> 00:20:49.909 align:start position:0% transaction is is um waiting too long in the<00:20:48.480> mempool<00:20:48.780> because<00:20:49.020> it<00:20:49.320> doesn't<00:20:49.620> have<00:20:49.799> a 00:20:49.909 --> 00:20:49.919 align:start position:0% the mempool because it doesn't have a 00:20:49.919 --> 00:20:53.210 align:start position:0% the mempool because it doesn't have a high<00:20:50.039> enough<00:20:50.160> gas<00:20:50.520> price<00:20:51.480> assigned<00:20:52.020> then<00:20:52.679> uh 00:20:53.210 --> 00:20:53.220 align:start position:0% high enough gas price assigned then uh 00:20:53.220 --> 00:20:54.470 align:start position:0% high enough gas price assigned then uh it<00:20:53.400> will<00:20:53.520> actually<00:20:53.700> ramp<00:20:54.059> those<00:20:54.299> up 00:20:54.470 --> 00:20:54.480 align:start position:0% it will actually ramp those up 00:20:54.480 --> 00:20:56.330 align:start position:0% it will actually ramp those up aggressively<00:20:55.140> and<00:20:55.380> it<00:20:55.500> tries<00:20:55.679> to<00:20:55.860> figure<00:20:56.100> out 00:20:56.330 --> 00:20:56.340 align:start position:0% aggressively and it tries to figure out 00:20:56.340 --> 00:20:58.789 align:start position:0% aggressively and it tries to figure out you<00:20:57.000> know<00:20:57.059> uh<00:20:57.660> how<00:20:57.960> much<00:20:58.080> gas<00:20:58.260> do<00:20:58.500> we<00:20:58.620> need<00:20:58.740> to 00:20:58.789 --> 00:20:58.799 align:start position:0% you know uh how much gas do we need to 00:20:58.799 --> 00:21:01.970 align:start position:0% you know uh how much gas do we need to be<00:20:58.919> able<00:20:59.039> to<00:20:59.660> execute<00:21:00.660> this<00:21:00.840> transaction<00:21:01.260> in<00:21:01.740> a 00:21:01.970 --> 00:21:01.980 align:start position:0% be able to execute this transaction in a 00:21:01.980 --> 00:21:04.190 align:start position:0% be able to execute this transaction in a certain<00:21:02.100> amount<00:21:02.340> of<00:21:02.520> time<00:21:02.780> that<00:21:03.780> being<00:21:04.020> the 00:21:04.190 --> 00:21:04.200 align:start position:0% certain amount of time that being the 00:21:04.200 --> 00:21:08.570 align:start position:0% certain amount of time that being the variable<00:21:04.440> you<00:21:04.679> set<00:21:05.179> uh<00:21:06.179> you<00:21:06.960> can<00:21:07.220> you<00:21:08.220> need<00:21:08.520> to 00:21:08.570 --> 00:21:08.580 align:start position:0% variable you set uh you can you need to 00:21:08.580 --> 00:21:10.010 align:start position:0% variable you set uh you can you need to make<00:21:08.640> the<00:21:08.820> decision<00:21:09.059> you<00:21:09.360> know<00:21:09.419> if<00:21:09.660> you're<00:21:09.840> not 00:21:10.010 --> 00:21:10.020 align:start position:0% make the decision you know if you're not 00:21:10.020 --> 00:21:13.370 align:start position:0% make the decision you know if you're not actually<00:21:10.260> doing<00:21:10.760> uh<00:21:11.760> execution<00:21:12.360> and<00:21:13.200> you're 00:21:13.370 --> 00:21:13.380 align:start position:0% actually doing uh execution and you're 00:21:13.380 --> 00:21:15.110 align:start position:0% actually doing uh execution and you're just<00:21:13.559> posting<00:21:13.919> data<00:21:14.220> to<00:21:14.340> the<00:21:14.460> chain<00:21:14.640> then<00:21:14.880> you 00:21:15.110 --> 00:21:15.120 align:start position:0% just posting data to the chain then you 00:21:15.120 --> 00:21:16.549 align:start position:0% just posting data to the chain then you might<00:21:15.240> want<00:21:15.360> to<00:21:15.539> actually<00:21:15.840> more<00:21:16.320> like<00:21:16.500> an 00:21:16.549 --> 00:21:16.559 align:start position:0% might want to actually more like an 00:21:16.559 --> 00:21:19.850 align:start position:0% might want to actually more like an oracle<00:21:16.919> model<00:21:17.100> so<00:21:18.059> just<00:21:18.299> posting<00:21:18.660> data<00:21:19.080> you're 00:21:19.850 --> 00:21:19.860 align:start position:0% oracle model so just posting data you're 00:21:19.860 --> 00:21:21.770 align:start position:0% oracle model so just posting data you're not<00:21:20.039> necessarily<00:21:20.460> thinking<00:21:20.820> about<00:21:21.000> execution 00:21:21.770 --> 00:21:21.780 align:start position:0% not necessarily thinking about execution 00:21:21.780 --> 00:21:23.350 align:start position:0% not necessarily thinking about execution then<00:21:22.020> you're<00:21:22.260> more<00:21:22.440> thinking<00:21:22.740> about 00:21:23.350 --> 00:21:23.360 align:start position:0% then you're more thinking about 00:21:23.360 --> 00:21:25.430 align:start position:0% then you're more thinking about launching<00:21:24.360> execution<00:21:24.780> that<00:21:24.960> is<00:21:25.080> you're<00:21:25.260> more 00:21:25.430 --> 00:21:25.440 align:start position:0% launching execution that is you're more 00:21:25.440 --> 00:21:27.909 align:start position:0% launching execution that is you're more thinking<00:21:25.740> about<00:21:25.860> how<00:21:26.700> do<00:21:26.760> I<00:21:26.880> get<00:21:27.000> a<00:21:27.120> reliable 00:21:27.909 --> 00:21:27.919 align:start position:0% thinking about how do I get a reliable 00:21:27.919 --> 00:21:30.830 align:start position:0% thinking about how do I get a reliable uh<00:21:28.919> like<00:21:29.640> reliable<00:21:30.000> posting<00:21:30.360> of<00:21:30.480> results<00:21:30.659> to 00:21:30.830 --> 00:21:30.840 align:start position:0% uh like reliable posting of results to 00:21:30.840 --> 00:21:32.090 align:start position:0% uh like reliable posting of results to the<00:21:31.020> chain 00:21:32.090 --> 00:21:32.100 align:start position:0% the chain 00:21:32.100 --> 00:21:33.470 align:start position:0% the chain um you<00:21:32.280> can<00:21:32.400> go<00:21:32.520> through<00:21:32.640> a<00:21:32.760> multi-sig<00:21:33.179> if<00:21:33.419> you 00:21:33.470 --> 00:21:33.480 align:start position:0% um you can go through a multi-sig if you 00:21:33.480 --> 00:21:34.970 align:start position:0% um you can go through a multi-sig if you don't<00:21:33.600> trust<00:21:33.780> your<00:21:33.960> automation<00:21:34.380> you<00:21:34.860> could 00:21:34.970 --> 00:21:34.980 align:start position:0% don't trust your automation you could 00:21:34.980 --> 00:21:37.070 align:start position:0% don't trust your automation you could have<00:21:35.220> them<00:21:35.580> as<00:21:35.760> one<00:21:35.940> of<00:21:36.059> the<00:21:36.120> signers<00:21:36.539> of<00:21:36.720> a<00:21:36.900> you 00:21:37.070 --> 00:21:37.080 align:start position:0% have them as one of the signers of a you 00:21:37.080 --> 00:21:39.950 align:start position:0% have them as one of the signers of a you know<00:21:37.200> one<00:21:37.380> of<00:21:37.500> two<00:21:37.620> multisig<00:21:38.460> where<00:21:39.360> they<00:21:39.600> you 00:21:39.950 --> 00:21:39.960 align:start position:0% know one of two multisig where they you 00:21:39.960 --> 00:21:41.330 align:start position:0% know one of two multisig where they you know<00:21:40.020> basically<00:21:40.440> are<00:21:40.620> queuing<00:21:40.980> up<00:21:41.100> that 00:21:41.330 --> 00:21:41.340 align:start position:0% know basically are queuing up that 00:21:41.340 --> 00:21:43.430 align:start position:0% know basically are queuing up that transaction<00:21:41.880> send<00:21:42.480> yourself<00:21:42.659> a<00:21:42.960> notification 00:21:43.430 --> 00:21:43.440 align:start position:0% transaction send yourself a notification 00:21:43.440 --> 00:21:46.970 align:start position:0% transaction send yourself a notification and<00:21:43.799> then<00:21:43.980> accept<00:21:44.520> or<00:21:44.880> reject<00:21:45.559> that<00:21:46.559> might<00:21:46.740> be 00:21:46.970 --> 00:21:46.980 align:start position:0% and then accept or reject that might be 00:21:46.980 --> 00:21:48.890 align:start position:0% and then accept or reject that might be the<00:21:47.280> most<00:21:47.340> thing<00:21:47.640> that<00:21:47.880> most<00:21:48.240> people<00:21:48.480> are<00:21:48.720> more 00:21:48.890 --> 00:21:48.900 align:start position:0% the most thing that most people are more 00:21:48.900 --> 00:21:51.590 align:start position:0% the most thing that most people are more comfortable<00:21:49.200> with<00:21:49.880> you<00:21:50.880> could<00:21:51.059> potentially 00:21:51.590 --> 00:21:51.600 align:start position:0% comfortable with you could potentially 00:21:51.600 --> 00:21:54.710 align:start position:0% comfortable with you could potentially run<00:21:51.960> things<00:21:52.260> run<00:21:52.679> the<00:21:52.919> actual<00:21:53.280> uh<00:21:54.120> run<00:21:54.360> some<00:21:54.539> of 00:21:54.710 --> 00:21:54.720 align:start position:0% run things run the actual uh run some of 00:21:54.720 --> 00:21:56.870 align:start position:0% run things run the actual uh run some of this<00:21:54.780> Logic<00:21:55.080> on<00:21:55.320> an<00:21:55.500> L2 00:21:56.870 --> 00:21:56.880 align:start position:0% this Logic on an L2 00:21:56.880 --> 00:22:05.890 align:start position:0% this Logic on an L2 um<00:21:57.000> so<00:21:57.299> what's<00:21:57.600> the<00:21:57.840> name<00:21:57.960> of<00:21:58.080> the 00:22:05.890 --> 00:22:05.900 align:start position:0% 00:22:05.900 --> 00:22:08.990 align:start position:0% uh<00:22:06.900> yeah<00:22:07.080> uh<00:22:07.500> there's<00:22:07.679> a<00:22:07.799> company<00:22:07.980> called<00:22:08.460> uh 00:22:08.990 --> 00:22:09.000 align:start position:0% uh yeah uh there's a company called uh 00:22:09.000 --> 00:22:11.810 align:start position:0% uh yeah uh there's a company called uh modulus<00:22:09.480> Labs<00:22:10.159> uh<00:22:11.159> they're<00:22:11.520> doing<00:22:11.700> some 00:22:11.810 --> 00:22:11.820 align:start position:0% modulus Labs uh they're doing some 00:22:11.820 --> 00:22:13.310 align:start position:0% modulus Labs uh they're doing some pretty<00:22:12.000> cool<00:22:12.120> stuff<00:22:12.299> uh<00:22:12.539> so<00:22:12.840> they<00:22:12.960> created 00:22:13.310 --> 00:22:13.320 align:start position:0% pretty cool stuff uh so they created 00:22:13.320 --> 00:22:15.830 align:start position:0% pretty cool stuff uh so they created this<00:22:13.440> thing<00:22:13.559> called<00:22:13.740> Rocky<00:22:14.220> bot 00:22:15.830 --> 00:22:15.840 align:start position:0% this thing called Rocky bot 00:22:15.840 --> 00:22:17.930 align:start position:0% this thing called Rocky bot um<00:22:15.960> that<00:22:16.440> basically<00:22:16.679> does<00:22:16.980> what<00:22:17.280> Matthias<00:22:17.760> was 00:22:17.930 --> 00:22:17.940 align:start position:0% um that basically does what Matthias was 00:22:17.940 --> 00:22:21.289 align:start position:0% um that basically does what Matthias was saying<00:22:18.240> uh<00:22:19.140> where<00:22:19.440> uh<00:22:20.159> they're<00:22:20.460> running<00:22:20.700> uh 00:22:21.289 --> 00:22:21.299 align:start position:0% saying uh where uh they're running uh 00:22:21.299 --> 00:22:23.570 align:start position:0% saying uh where uh they're running uh it's<00:22:21.780> on<00:22:21.960> it's<00:22:22.200> on<00:22:22.380> start<00:22:22.559> net<00:22:22.799> uh<00:22:23.340> and<00:22:23.460> they're 00:22:23.570 --> 00:22:23.580 align:start position:0% it's on it's on start net uh and they're 00:22:23.580 --> 00:22:25.190 align:start position:0% it's on it's on start net uh and they're leveraging<00:22:23.940> that<00:22:24.059> and<00:22:24.240> just<00:22:24.419> basically<00:22:24.659> uh 00:22:25.190 --> 00:22:25.200 align:start position:0% leveraging that and just basically uh 00:22:25.200 --> 00:22:27.169 align:start position:0% leveraging that and just basically uh posting<00:22:25.559> the<00:22:25.679> result<00:22:25.799> to<00:22:26.039> the<00:22:26.159> chain<00:22:26.340> uh<00:22:27.059> so 00:22:27.169 --> 00:22:27.179 align:start position:0% posting the result to the chain uh so 00:22:27.179 --> 00:22:28.549 align:start position:0% posting the result to the chain uh so it's<00:22:27.299> like<00:22:27.419> a<00:22:27.539> neural<00:22:27.720> network<00:22:27.840> on<00:22:28.140> chain<00:22:28.380> it's 00:22:28.549 --> 00:22:28.559 align:start position:0% it's like a neural network on chain it's 00:22:28.559 --> 00:22:30.289 align:start position:0% it's like a neural network on chain it's it's<00:22:28.740> it's<00:22:28.860> it's<00:22:29.039> very<00:22:29.460> cool 00:22:30.289 --> 00:22:30.299 align:start position:0% it's it's it's very cool 00:22:30.299 --> 00:22:32.210 align:start position:0% it's it's it's very cool um definitely<00:22:30.600> check<00:22:30.840> it<00:22:30.960> out<00:22:31.380> yeah<00:22:31.919> and<00:22:32.100> then 00:22:32.210 --> 00:22:32.220 align:start position:0% um definitely check it out yeah and then 00:22:32.220 --> 00:22:34.669 align:start position:0% um definitely check it out yeah and then I'm<00:22:32.580> not<00:22:32.940> very<00:22:33.179> familiar<00:22:33.480> with<00:22:33.600> Mev<00:22:34.140> or<00:22:34.380> you 00:22:34.669 --> 00:22:34.679 align:start position:0% I'm not very familiar with Mev or you 00:22:34.679 --> 00:22:36.950 align:start position:0% I'm not very familiar with Mev or you know<00:22:34.740> like<00:22:34.919> uh<00:22:35.460> being<00:22:35.760> a<00:22:36.000> Searcher<00:22:36.360> so<00:22:36.659> I'm 00:22:36.950 --> 00:22:36.960 align:start position:0% know like uh being a Searcher so I'm 00:22:36.960 --> 00:22:38.330 align:start position:0% know like uh being a Searcher so I'm sure<00:22:37.140> there's<00:22:37.320> other<00:22:37.500> people<00:22:37.679> who<00:22:37.860> can<00:22:38.039> expand 00:22:38.330 --> 00:22:38.340 align:start position:0% sure there's other people who can expand 00:22:38.340 --> 00:22:40.130 align:start position:0% sure there's other people who can expand on<00:22:38.520> this<00:22:38.700> but<00:22:39.059> in<00:22:39.539> that<00:22:39.659> case<00:22:39.780> you're<00:22:39.960> probably 00:22:40.130 --> 00:22:40.140 align:start position:0% on this but in that case you're probably 00:22:40.140 --> 00:22:41.870 align:start position:0% on this but in that case you're probably using<00:22:40.500> something<00:22:40.620> more<00:22:40.860> dedicated<00:22:41.280> to<00:22:41.640> your 00:22:41.870 --> 00:22:41.880 align:start position:0% using something more dedicated to your 00:22:41.880 --> 00:22:43.730 align:start position:0% using something more dedicated to your building<00:22:42.360> bundles<00:22:42.780> using<00:22:43.140> the<00:22:43.260> the<00:22:43.380> Builder 00:22:43.730 --> 00:22:43.740 align:start position:0% building bundles using the the Builder 00:22:43.740 --> 00:22:49.070 align:start position:0% building bundles using the the Builder API<00:22:44.100> I<00:22:44.159> believe 00:22:49.070 --> 00:22:49.080 align:start position:0% 00:22:49.080 --> 00:22:50.990 align:start position:0% uh<00:22:49.620> and<00:22:49.799> for<00:22:49.980> this<00:22:50.100> example<00:22:50.340> we're<00:22:50.520> just<00:22:50.700> using 00:22:50.990 --> 00:22:51.000 align:start position:0% uh and for this example we're just using 00:22:51.000 --> 00:22:54.350 align:start position:0% uh and for this example we're just using uh<00:22:51.539> you<00:22:51.659> know<00:22:51.780> web3<00:22:52.380> dot<00:22:53.340> Pi 00:22:54.350 --> 00:22:54.360 align:start position:0% uh you know web3 dot Pi 00:22:54.360 --> 00:22:55.850 align:start position:0% uh you know web3 dot Pi um<00:22:54.419> this<00:22:55.020> is<00:22:55.140> probably<00:22:55.320> the<00:22:55.620> thing<00:22:55.740> that 00:22:55.850 --> 00:22:55.860 align:start position:0% um this is probably the thing that 00:22:55.860 --> 00:22:57.049 align:start position:0% um this is probably the thing that people<00:22:55.980> are<00:22:56.159> actually<00:22:56.340> the<00:22:56.520> most<00:22:56.700> familiar 00:22:57.049 --> 00:22:57.059 align:start position:0% people are actually the most familiar 00:22:57.059 --> 00:22:58.909 align:start position:0% people are actually the most familiar with<00:22:57.179> uh<00:22:57.720> were<00:22:57.960> fully<00:22:58.200> we're<00:22:58.380> just<00:22:58.620> you<00:22:58.860> know 00:22:58.909 --> 00:22:58.919 align:start position:0% with uh were fully we're just you know 00:22:58.919 --> 00:23:00.130 align:start position:0% with uh were fully we're just you know setting<00:22:59.280> some 00:23:00.130 --> 00:23:00.140 align:start position:0% setting some 00:23:00.140 --> 00:23:03.289 align:start position:0% setting some uh<00:23:01.140> some<00:23:01.799> variables<00:23:02.280> we're<00:23:02.580> selecting<00:23:03.179> our 00:23:03.289 --> 00:23:03.299 align:start position:0% uh some variables we're selecting our 00:23:03.299 --> 00:23:05.630 align:start position:0% uh some variables we're selecting our chain<00:23:03.539> being<00:23:03.840> girly<00:23:04.260> we're<00:23:04.559> grabbing<00:23:04.980> an<00:23:05.159> RPC 00:23:05.630 --> 00:23:05.640 align:start position:0% chain being girly we're grabbing an RPC 00:23:05.640 --> 00:23:07.490 align:start position:0% chain being girly we're grabbing an RPC provider<00:23:06.179> uh<00:23:06.900> there's<00:23:07.020> some<00:23:07.140> middleware 00:23:07.490 --> 00:23:07.500 align:start position:0% provider uh there's some middleware 00:23:07.500 --> 00:23:09.169 align:start position:0% provider uh there's some middleware that's<00:23:07.740> required<00:23:08.159> for<00:23:08.400> for<00:23:08.580> Gurley<00:23:08.940> here 00:23:09.169 --> 00:23:09.179 align:start position:0% that's required for for Gurley here 00:23:09.179 --> 00:23:10.730 align:start position:0% that's required for for Gurley here we're<00:23:09.600> grabbing<00:23:09.900> a<00:23:10.080> private<00:23:10.440> key<00:23:10.500> from 00:23:10.730 --> 00:23:10.740 align:start position:0% we're grabbing a private key from 00:23:10.740 --> 00:23:12.470 align:start position:0% we're grabbing a private key from environment<00:23:11.280> variables<00:23:11.820> which<00:23:12.179> of<00:23:12.360> course 00:23:12.470 --> 00:23:12.480 align:start position:0% environment variables which of course 00:23:12.480 --> 00:23:14.529 align:start position:0% environment variables which of course means<00:23:12.780> we<00:23:12.900> have<00:23:13.020> to<00:23:13.080> manage<00:23:13.380> that<00:23:13.559> ourselves 00:23:14.529 --> 00:23:14.539 align:start position:0% means we have to manage that ourselves 00:23:14.539 --> 00:23:17.690 align:start position:0% means we have to manage that ourselves and<00:23:15.539> then<00:23:16.140> we<00:23:16.559> are 00:23:17.690 --> 00:23:17.700 align:start position:0% and then we are 00:23:17.700 --> 00:23:19.909 align:start position:0% and then we are you<00:23:18.299> know<00:23:18.419> executing<00:23:18.840> transaction<00:23:19.200> in<00:23:19.799> this 00:23:19.909 --> 00:23:19.919 align:start position:0% you know executing transaction in this 00:23:19.919 --> 00:23:22.490 align:start position:0% you know executing transaction in this case<00:23:20.039> we<00:23:20.340> are<00:23:20.460> swapping<00:23:20.820> on<00:23:21.059> universal<00:23:21.500> v2's 00:23:22.490 --> 00:23:22.500 align:start position:0% case we are swapping on universal v2's 00:23:22.500 --> 00:23:23.510 align:start position:0% case we are swapping on universal v2's router 00:23:23.510 --> 00:23:23.520 align:start position:0% router 00:23:23.520 --> 00:23:25.549 align:start position:0% router um<00:23:23.580> so<00:23:23.880> we're 00:23:25.549 --> 00:23:25.559 align:start position:0% um so we're 00:23:25.559 --> 00:23:29.649 align:start position:0% um so we're grabbing<00:23:26.460> the<00:23:26.520> ABI<00:23:27.000> uh<00:23:27.960> using<00:23:28.320> that<00:23:28.500> to<00:23:28.740> to 00:23:29.649 --> 00:23:29.659 align:start position:0% grabbing the ABI uh using that to to 00:23:29.659 --> 00:23:34.730 align:start position:0% grabbing the ABI uh using that to to encode<00:23:30.659> our<00:23:31.039> function<00:23:32.039> signature<00:23:32.600> and<00:23:33.600> uh<00:23:34.260> you 00:23:34.730 --> 00:23:34.740 align:start position:0% encode our function signature and uh you 00:23:34.740 --> 00:23:36.289 align:start position:0% encode our function signature and uh you know<00:23:34.860> setting<00:23:35.159> some<00:23:35.340> parameters<00:23:35.880> and<00:23:36.120> and 00:23:36.289 --> 00:23:36.299 align:start position:0% know setting some parameters and and 00:23:36.299 --> 00:23:40.909 align:start position:0% know setting some parameters and and posting<00:23:36.780> that<00:23:36.900> to<00:23:37.080> the<00:23:37.200> chain 00:23:40.909 --> 00:23:40.919 align:start position:0% 00:23:40.919 --> 00:23:44.390 align:start position:0% cool<00:23:41.400> so<00:23:41.640> before<00:23:42.000> we<00:23:42.299> go<00:23:42.720> into<00:23:43.200> this 00:23:44.390 --> 00:23:44.400 align:start position:0% cool so before we go into this 00:23:44.400 --> 00:23:47.810 align:start position:0% cool so before we go into this um just<00:23:44.640> wanted<00:23:44.820> three<00:23:45.120> caps<00:23:45.480> so<00:23:45.740> we<00:23:46.740> used<00:23:47.220> a 00:23:47.810 --> 00:23:47.820 align:start position:0% um just wanted three caps so we used a 00:23:47.820 --> 00:23:49.549 align:start position:0% um just wanted three caps so we used a subgraph<00:23:48.419> to<00:23:48.659> pull 00:23:49.549 --> 00:23:49.559 align:start position:0% subgraph to pull 00:23:49.559 --> 00:23:52.190 align:start position:0% subgraph to pull um<00:23:49.679> typical<00:23:50.159> ethusd<00:23:51.000> price<00:23:51.179> data<00:23:51.480> we<00:23:51.600> use<00:23:51.780> Doom 00:23:52.190 --> 00:23:52.200 align:start position:0% um typical ethusd price data we use Doom 00:23:52.200 --> 00:23:55.610 align:start position:0% um typical ethusd price data we use Doom to<00:23:52.320> pull<00:23:52.500> eth<00:23:52.980> USD<00:23:53.580> price<00:23:53.760> data<00:23:54.240> and<00:23:55.080> we 00:23:55.610 --> 00:23:55.620 align:start position:0% to pull eth USD price data and we 00:23:55.620 --> 00:23:59.570 align:start position:0% to pull eth USD price data and we processed<00:23:56.220> it<00:23:56.360> we<00:23:57.360> using<00:23:57.960> python<00:23:58.320> pandas<00:23:58.799> and 00:23:59.570 --> 00:23:59.580 align:start position:0% processed it we using python pandas and 00:23:59.580 --> 00:24:03.350 align:start position:0% processed it we using python pandas and then<00:23:59.760> we<00:24:00.120> used<00:24:00.299> web3<00:24:01.220> dot<00:24:02.220> pi<00:24:02.760> to<00:24:03.179> actually 00:24:03.350 --> 00:24:03.360 align:start position:0% then we used web3 dot pi to actually 00:24:03.360 --> 00:24:05.570 align:start position:0% then we used web3 dot pi to actually send<00:24:03.659> the<00:24:03.840> transaction 00:24:05.570 --> 00:24:05.580 align:start position:0% send the transaction 00:24:05.580 --> 00:24:06.950 align:start position:0% send the transaction um<00:24:05.640> it's<00:24:06.240> actually<00:24:06.360> what<00:24:06.659> we<00:24:06.720> were<00:24:06.840> supposed 00:24:06.950 --> 00:24:06.960 align:start position:0% um it's actually what we were supposed 00:24:06.960 --> 00:24:09.070 align:start position:0% um it's actually what we were supposed to<00:24:07.080> show<00:24:07.200> just<00:24:07.440> put<00:24:07.980> putting<00:24:08.280> it<00:24:08.340> all<00:24:08.520> together 00:24:09.070 --> 00:24:09.080 align:start position:0% to show just put putting it all together 00:24:09.080 --> 00:24:12.830 align:start position:0% to show just put putting it all together yeah<00:24:10.080> it's<00:24:10.380> again<00:24:10.679> you<00:24:11.460> know<00:24:11.520> three<00:24:12.480> steps 00:24:12.830 --> 00:24:12.840 align:start position:0% yeah it's again you know three steps 00:24:12.840 --> 00:24:16.010 align:start position:0% yeah it's again you know three steps here<00:24:13.020> really<00:24:13.380> oh<00:24:14.039> grab<00:24:14.520> graph<00:24:14.940> and<00:24:15.120> dune<00:24:16.020> um 00:24:16.010 --> 00:24:16.020 align:start position:0% here really oh grab graph and dune um 00:24:16.020 --> 00:24:19.730 align:start position:0% here really oh grab graph and dune um you<00:24:16.320> know<00:24:16.380> formatted<00:24:16.919> data<00:24:17.419> uh<00:24:18.419> check<00:24:19.140> with 00:24:19.730 --> 00:24:19.740 align:start position:0% you know formatted data uh check with 00:24:19.740 --> 00:24:21.169 align:start position:0% you know formatted data uh check with the<00:24:19.860> model<00:24:19.980> whether<00:24:20.340> we<00:24:20.520> should<00:24:20.640> buy<00:24:20.820> graph 00:24:21.169 --> 00:24:21.179 align:start position:0% the model whether we should buy graph 00:24:21.179 --> 00:24:23.810 align:start position:0% the model whether we should buy graph buy<00:24:22.080> based<00:24:22.799> on<00:24:22.860> the<00:24:22.980> graph<00:24:23.100> model<00:24:23.280> whether<00:24:23.640> we 00:24:23.810 --> 00:24:23.820 align:start position:0% buy based on the graph model whether we 00:24:23.820 --> 00:24:26.390 align:start position:0% buy based on the graph model whether we should<00:24:23.940> buy<00:24:24.120> based<00:24:24.659> on<00:24:24.780> the<00:24:25.020> Dune<00:24:25.500> model<00:24:25.679> and 00:24:26.390 --> 00:24:26.400 align:start position:0% should buy based on the Dune model and 00:24:26.400 --> 00:24:29.090 align:start position:0% should buy based on the Dune model and you<00:24:26.580> know<00:24:26.700> if<00:24:26.880> both<00:24:27.059> are<00:24:27.240> true<00:24:27.480> uh<00:24:28.440> we<00:24:28.919> are 00:24:29.090 --> 00:24:29.100 align:start position:0% you know if both are true uh we are 00:24:29.100 --> 00:24:30.710 align:start position:0% you know if both are true uh we are buying 00:24:30.710 --> 00:24:30.720 align:start position:0% buying 00:24:30.720 --> 00:24:34.250 align:start position:0% buying yeah<00:24:31.200> and<00:24:31.440> one<00:24:31.740> more<00:24:32.039> thing<00:24:32.159> to<00:24:32.400> say<00:24:32.520> here<00:24:32.820> is 00:24:34.250 --> 00:24:34.260 align:start position:0% yeah and one more thing to say here is 00:24:34.260 --> 00:24:35.149 align:start position:0% yeah and one more thing to say here is um 00:24:35.149 --> 00:24:35.159 align:start position:0% um 00:24:35.159 --> 00:24:38.149 align:start position:0% um so<00:24:35.820> this<00:24:36.120> makes<00:24:36.600> it<00:24:36.780> look<00:24:36.960> easy 00:24:38.149 --> 00:24:38.159 align:start position:0% so this makes it look easy 00:24:38.159 --> 00:24:39.350 align:start position:0% so this makes it look easy um<00:24:38.220> and<00:24:38.580> that's<00:24:38.820> actually<00:24:39.000> what<00:24:39.240> we're 00:24:39.350 --> 00:24:39.360 align:start position:0% um and that's actually what we're 00:24:39.360 --> 00:24:41.510 align:start position:0% um and that's actually what we're working<00:24:39.600> on<00:24:39.840> at<00:24:40.320> component<00:24:40.799> so<00:24:41.159> working<00:24:41.340> on 00:24:41.510 --> 00:24:41.520 align:start position:0% working on at component so working on 00:24:41.520 --> 00:24:42.950 align:start position:0% working on at component so working on something<00:24:41.700> called<00:24:41.820> blueprint<00:24:42.240> that 00:24:42.950 --> 00:24:42.960 align:start position:0% something called blueprint that 00:24:42.960 --> 00:24:44.570 align:start position:0% something called blueprint that abstracts<00:24:43.500> away<00:24:43.620> all<00:24:43.860> the<00:24:44.039> stuff<00:24:44.159> we<00:24:44.340> just<00:24:44.460> had 00:24:44.570 --> 00:24:44.580 align:start position:0% abstracts away all the stuff we just had 00:24:44.580 --> 00:24:45.529 align:start position:0% abstracts away all the stuff we just had to<00:24:44.760> do 00:24:45.529 --> 00:24:45.539 align:start position:0% to do 00:24:45.539 --> 00:24:46.789 align:start position:0% to do um although<00:24:45.780> it's<00:24:45.900> really<00:24:46.080> fun<00:24:46.260> to<00:24:46.440> learn<00:24:46.500> how 00:24:46.789 --> 00:24:46.799 align:start position:0% um although it's really fun to learn how 00:24:46.799 --> 00:24:47.990 align:start position:0% um although it's really fun to learn how it's<00:24:46.919> done<00:24:47.100> and<00:24:47.280> you<00:24:47.400> can<00:24:47.520> definitely<00:24:47.700> do<00:24:47.820> it 00:24:47.990 --> 00:24:48.000 align:start position:0% it's done and you can definitely do it 00:24:48.000 --> 00:24:48.950 align:start position:0% it's done and you can definitely do it that<00:24:48.120> way 00:24:48.950 --> 00:24:48.960 align:start position:0% that way 00:24:48.960 --> 00:24:50.330 align:start position:0% that way um<00:24:49.080> and<00:24:49.440> you<00:24:49.740> know<00:24:49.799> to<00:24:49.860> see<00:24:49.980> how<00:24:50.100> it's<00:24:50.159> done 00:24:50.330 --> 00:24:50.340 align:start position:0% um and you know to see how it's done 00:24:50.340 --> 00:24:52.250 align:start position:0% um and you know to see how it's done under<00:24:50.460> the<00:24:50.640> hood<00:24:50.760> but<00:24:51.600> what<00:24:51.720> we<00:24:51.840> do<00:24:52.020> with<00:24:52.140> that 00:24:52.250 --> 00:24:52.260 align:start position:0% under the hood but what we do with that 00:24:52.260 --> 00:24:54.289 align:start position:0% under the hood but what we do with that product<00:24:52.500> is<00:24:52.860> essentially<00:24:53.280> uh<00:24:53.880> try<00:24:54.120> and<00:24:54.179> take 00:24:54.289 --> 00:24:54.299 align:start position:0% product is essentially uh try and take 00:24:54.299 --> 00:24:55.789 align:start position:0% product is essentially uh try and take you<00:24:54.419> to<00:24:54.539> this<00:24:54.720> step<00:24:54.900> without<00:24:55.260> having<00:24:55.559> to<00:24:55.679> do 00:24:55.789 --> 00:24:55.799 align:start position:0% you to this step without having to do 00:24:55.799 --> 00:25:02.350 align:start position:0% you to this step without having to do you<00:24:56.100> know<00:24:56.159> all<00:24:56.280> the<00:24:56.400> other<00:24:56.520> stuff 00:25:02.350 --> 00:25:02.360 align:start position:0% 00:25:02.360 --> 00:25:05.110 align:start position:0% okay<00:25:03.360> I<00:25:03.600> guess<00:25:03.840> it's<00:25:03.960> me 00:25:05.110 --> 00:25:05.120 align:start position:0% okay I guess it's me 00:25:05.120 --> 00:25:08.630 align:start position:0% okay I guess it's me so<00:25:06.120> uh<00:25:06.780> you<00:25:07.440> guys<00:25:07.559> saw<00:25:07.740> what<00:25:07.980> we<00:25:08.100> came<00:25:08.280> up<00:25:08.460> with 00:25:08.630 --> 00:25:08.640 align:start position:0% so uh you guys saw what we came up with 00:25:08.640 --> 00:25:11.029 align:start position:0% so uh you guys saw what we came up with uh<00:25:09.240> now<00:25:09.419> it's<00:25:09.659> your<00:25:09.900> turn 00:25:11.029 --> 00:25:11.039 align:start position:0% uh now it's your turn 00:25:11.039 --> 00:25:12.230 align:start position:0% uh now it's your turn um<00:25:11.100> this<00:25:11.340> might<00:25:11.520> be<00:25:11.580> a<00:25:11.700> little<00:25:11.760> long<00:25:11.940> with<00:25:12.120> the 00:25:12.230 --> 00:25:12.240 align:start position:0% um this might be a little long with the 00:25:12.240 --> 00:25:15.110 align:start position:0% um this might be a little long with the 10<00:25:12.360> minutes<00:25:12.539> but<00:25:13.500> um<00:25:13.559> I'm<00:25:14.340> sure<00:25:14.520> everyone<00:25:14.880> who 00:25:15.110 --> 00:25:15.120 align:start position:0% 10 minutes but um I'm sure everyone who 00:25:15.120 --> 00:25:17.149 align:start position:0% 10 minutes but um I'm sure everyone who came<00:25:15.299> here<00:25:15.480> has<00:25:15.900> something<00:25:16.320> in<00:25:16.620> webview<00:25:16.980> that 00:25:17.149 --> 00:25:17.159 align:start position:0% came here has something in webview that 00:25:17.159 --> 00:25:18.890 align:start position:0% came here has something in webview that they're<00:25:17.280> passionate<00:25:17.640> about<00:25:17.760> uh<00:25:18.480> that<00:25:18.720> thing 00:25:18.890 --> 00:25:18.900 align:start position:0% they're passionate about uh that thing 00:25:18.900 --> 00:25:20.390 align:start position:0% they're passionate about uh that thing probably<00:25:19.140> is<00:25:19.500> generating<00:25:19.860> quite<00:25:20.100> a<00:25:20.220> bit<00:25:20.280> of 00:25:20.390 --> 00:25:20.400 align:start position:0% probably is generating quite a bit of 00:25:20.400 --> 00:25:21.710 align:start position:0% probably is generating quite a bit of data 00:25:21.710 --> 00:25:21.720 align:start position:0% data 00:25:21.720 --> 00:25:23.630 align:start position:0% data um<00:25:21.840> and<00:25:22.320> that's<00:25:22.500> probably<00:25:22.740> available<00:25:23.039> through 00:25:23.630 --> 00:25:23.640 align:start position:0% um and that's probably available through 00:25:23.640 --> 00:25:26.990 align:start position:0% um and that's probably available through one<00:25:24.000> of<00:25:24.120> the<00:25:24.240> many<00:25:24.360> services<00:25:24.659> we<00:25:25.320> we<00:25:25.620> mentioned 00:25:26.990 --> 00:25:27.000 align:start position:0% one of the many services we we mentioned 00:25:27.000 --> 00:25:28.730 align:start position:0% one of the many services we we mentioned um<00:25:27.120> so<00:25:27.480> we'd<00:25:27.779> like<00:25:27.900> to<00:25:28.020> take<00:25:28.200> a<00:25:28.380> little<00:25:28.500> bit<00:25:28.620> of 00:25:28.730 --> 00:25:28.740 align:start position:0% um so we'd like to take a little bit of 00:25:28.740 --> 00:25:31.669 align:start position:0% um so we'd like to take a little bit of time<00:25:28.980> uh<00:25:29.760> you<00:25:29.880> know<00:25:29.940> explore<00:25:30.299> some<00:25:30.480> data<00:25:30.840> sets 00:25:31.669 --> 00:25:31.679 align:start position:0% time uh you know explore some data sets 00:25:31.679 --> 00:25:33.409 align:start position:0% time uh you know explore some data sets um<00:25:31.740> think<00:25:31.980> about<00:25:32.159> what<00:25:32.820> kind<00:25:33.000> of<00:25:33.059> automation 00:25:33.409 --> 00:25:33.419 align:start position:0% um think about what kind of automation 00:25:33.419 --> 00:25:35.330 align:start position:0% um think about what kind of automation you<00:25:33.659> could<00:25:33.779> build<00:25:33.960> using<00:25:34.500> those<00:25:34.679> as<00:25:34.919> you<00:25:35.220> know 00:25:35.330 --> 00:25:35.340 align:start position:0% you could build using those as you know 00:25:35.340 --> 00:25:36.789 align:start position:0% you could build using those as you know your<00:25:35.520> input 00:25:36.789 --> 00:25:36.799 align:start position:0% your input 00:25:36.799 --> 00:25:40.010 align:start position:0% your input you<00:25:37.799> can<00:25:37.860> work<00:25:38.220> as<00:25:38.520> individuals<00:25:39.059> or<00:25:39.539> as<00:25:39.840> a 00:25:40.010 --> 00:25:40.020 align:start position:0% you can work as individuals or as a 00:25:40.020 --> 00:25:43.130 align:start position:0% you can work as individuals or as a group<00:25:40.200> to<00:25:40.559> start<00:25:40.880> uh<00:25:41.880> after<00:25:42.419> that<00:25:42.720> we're<00:25:43.020> going 00:25:43.130 --> 00:25:43.140 align:start position:0% group to start uh after that we're going 00:25:43.140 --> 00:25:45.049 align:start position:0% group to start uh after that we're going to<00:25:43.320> sort<00:25:43.500> of<00:25:43.620> have<00:25:43.860> a<00:25:44.340> little<00:25:44.460> 30<00:25:44.760> second 00:25:45.049 --> 00:25:45.059 align:start position:0% to sort of have a little 30 second 00:25:45.059 --> 00:25:47.269 align:start position:0% to sort of have a little 30 second pitches<00:25:45.600> uh<00:25:46.020> to<00:25:46.200> everybody<00:25:46.380> else<00:25:46.620> in<00:25:46.919> your<00:25:47.039> on 00:25:47.269 --> 00:25:47.279 align:start position:0% pitches uh to everybody else in your on 00:25:47.279 --> 00:25:50.570 align:start position:0% pitches uh to everybody else in your on your<00:25:47.460> table<00:25:48.020> and<00:25:49.020> you'll<00:25:49.620> decide<00:25:49.860> on<00:25:50.039> one<00:25:50.340> to 00:25:50.570 --> 00:25:50.580 align:start position:0% your table and you'll decide on one to 00:25:50.580 --> 00:25:53.110 align:start position:0% your table and you'll decide on one to sort<00:25:50.880> of<00:25:51.000> design<00:25:51.299> as<00:25:51.600> a<00:25:51.720> group 00:25:53.110 --> 00:25:53.120 align:start position:0% sort of design as a group 00:25:53.120 --> 00:25:55.850 align:start position:0% sort of design as a group yeah<00:25:54.120> so<00:25:54.419> just<00:25:54.840> to<00:25:55.080> you<00:25:55.320> know<00:25:55.380> give<00:25:55.620> you<00:25:55.740> an 00:25:55.850 --> 00:25:55.860 align:start position:0% yeah so just to you know give you an 00:25:55.860 --> 00:25:57.470 align:start position:0% yeah so just to you know give you an idea<00:25:56.039> of<00:25:56.159> what<00:25:56.279> you<00:25:56.400> could<00:25:56.520> do<00:25:56.640> so<00:25:57.000> anything<00:25:57.240> in 00:25:57.470 --> 00:25:57.480 align:start position:0% idea of what you could do so anything in 00:25:57.480 --> 00:25:59.810 align:start position:0% idea of what you could do so anything in defy<00:25:58.380> um<00:25:58.440> where<00:25:58.799> you<00:25:59.159> know<00:25:59.279> you're<00:25:59.400> triggering 00:25:59.810 --> 00:25:59.820 align:start position:0% defy um where you know you're triggering 00:25:59.820 --> 00:26:01.490 align:start position:0% defy um where you know you're triggering you<00:26:00.120> know<00:26:00.240> based<00:26:00.480> on<00:26:00.539> a<00:26:00.659> prediction<00:26:00.900> model<00:26:01.140> or 00:26:01.490 --> 00:26:01.500 align:start position:0% you know based on a prediction model or 00:26:01.500 --> 00:26:03.529 align:start position:0% you know based on a prediction model or based<00:26:01.799> on<00:26:01.860> some<00:26:02.039> conditional<00:26:02.460> logic<00:26:02.820> it<00:26:03.299> could 00:26:03.529 --> 00:26:03.539 align:start position:0% based on some conditional logic it could 00:26:03.539 --> 00:26:05.810 align:start position:0% based on some conditional logic it could be<00:26:03.659> to<00:26:03.840> sweep<00:26:04.200> the<00:26:04.380> floor<00:26:04.559> of<00:26:05.220> an<00:26:05.520> nft 00:26:05.810 --> 00:26:05.820 align:start position:0% be to sweep the floor of an nft 00:26:05.820 --> 00:26:07.130 align:start position:0% be to sweep the floor of an nft collection 00:26:07.130 --> 00:26:07.140 align:start position:0% collection 00:26:07.140 --> 00:26:09.049 align:start position:0% collection um<00:26:07.200> you<00:26:07.380> know<00:26:07.440> the<00:26:07.860> really<00:26:08.279> anything<00:26:08.460> you<00:26:08.820> want 00:26:09.049 --> 00:26:09.059 align:start position:0% um you know the really anything you want 00:26:09.059 --> 00:26:11.630 align:start position:0% um you know the really anything you want and<00:26:09.480> any<00:26:09.779> data<00:26:10.140> that<00:26:10.320> comes<00:26:11.220> to<00:26:11.279> mind<00:26:11.400> that's 00:26:11.630 --> 00:26:11.640 align:start position:0% and any data that comes to mind that's 00:26:11.640 --> 00:26:16.430 align:start position:0% and any data that comes to mind that's particular<00:26:12.059> to<00:26:12.240> you<00:26:12.419> and<00:26:13.140> what<00:26:13.559> you're<00:26:13.679> doing 00:26:16.430 --> 00:26:16.440 align:start position:0% 00:26:16.440 --> 00:26:17.870 align:start position:0% thinking<00:26:16.799> about<00:26:16.919> those<00:26:17.159> three<00:26:17.340> steps<00:26:17.640> where 00:26:17.870 --> 00:26:17.880 align:start position:0% thinking about those three steps where 00:26:17.880 --> 00:26:19.250 align:start position:0% thinking about those three steps where I'm<00:26:18.000> getting<00:26:18.179> the<00:26:18.360> data<00:26:18.600> from<00:26:18.659> how<00:26:19.020> I'm<00:26:19.140> going 00:26:19.250 --> 00:26:19.260 align:start position:0% I'm getting the data from how I'm going 00:26:19.260 --> 00:26:21.230 align:start position:0% I'm getting the data from how I'm going to<00:26:19.320> process<00:26:19.620> it<00:26:19.860> and<00:26:20.100> then<00:26:20.279> how<00:26:20.700> I'm<00:26:20.820> going<00:26:21.059> to 00:26:21.230 --> 00:26:21.240 align:start position:0% to process it and then how I'm going to 00:26:21.240 --> 00:26:22.789 align:start position:0% to process it and then how I'm going to actually<00:26:21.480> generate<00:26:22.080> something<00:26:22.320> actionable 00:26:22.789 --> 00:26:22.799 align:start position:0% actually generate something actionable 00:26:22.799 --> 00:26:24.890 align:start position:0% actually generate something actionable from<00:26:23.039> it 00:26:24.890 --> 00:26:24.900 align:start position:0% from it 00:26:24.900 --> 00:26:30.710 align:start position:0% from it yeah<00:26:25.620> go<00:26:26.340> ahead 00:26:30.710 --> 00:26:30.720 align:start position:0% 00:26:30.720 --> 00:26:32.750 align:start position:0% all<00:26:31.140> right<00:26:31.320> folks 00:26:32.750 --> 00:26:32.760 align:start position:0% all right folks 00:26:32.760 --> 00:26:34.610 align:start position:0% all right folks uh 00:26:34.610 --> 00:26:34.620 align:start position:0% uh 00:26:34.620 --> 00:26:37.070 align:start position:0% uh we're<00:26:35.220> happy<00:26:35.460> if<00:26:36.000> a<00:26:36.240> few<00:26:36.419> people<00:26:36.600> came<00:26:36.840> up<00:26:36.960> with 00:26:37.070 --> 00:26:37.080 align:start position:0% we're happy if a few people came up with 00:26:37.080 --> 00:26:38.690 align:start position:0% we're happy if a few people came up with an<00:26:37.260> idea<00:26:37.500> and<00:26:37.679> like<00:26:37.980> thought<00:26:38.279> about<00:26:38.400> the 00:26:38.690 --> 00:26:38.700 align:start position:0% an idea and like thought about the 00:26:38.700 --> 00:26:41.210 align:start position:0% an idea and like thought about the process<00:26:39.000> and<00:26:39.900> I<00:26:40.080> think<00:26:40.140> if<00:26:40.320> you<00:26:40.500> did<00:26:40.860> anyone 00:26:41.210 --> 00:26:41.220 align:start position:0% process and I think if you did anyone 00:26:41.220 --> 00:26:43.310 align:start position:0% process and I think if you did anyone come<00:26:41.460> up<00:26:41.580> with<00:26:41.760> an<00:26:42.240> idea 00:26:43.310 --> 00:26:43.320 align:start position:0% come up with an idea 00:26:43.320 --> 00:26:47.990 align:start position:0% come up with an idea raise<00:26:43.620> your<00:26:43.860> hand<00:26:43.980> if<00:26:44.159> you<00:26:44.279> did 00:26:47.990 --> 00:26:48.000 align:start position:0% 00:26:48.000 --> 00:26:52.149 align:start position:0% you<00:26:48.059> wanna<00:26:48.480> you<00:26:48.720> wanna<00:26:48.900> talk<00:26:49.080> about<00:26:49.260> it 00:26:52.149 --> 00:26:52.159 align:start position:0% 00:26:52.159 --> 00:26:55.190 align:start position:0% so<00:26:53.520> um<00:26:53.640> we<00:26:53.820> think<00:26:54.059> that<00:26:54.299> kind<00:26:54.659> of<00:26:54.779> defy 00:26:55.190 --> 00:26:55.200 align:start position:0% so um we think that kind of defy 00:26:55.200 --> 00:26:57.190 align:start position:0% so um we think that kind of defy investing<00:26:55.500> has<00:26:55.679> been<00:26:55.799> quite<00:26:55.980> risky 00:26:57.190 --> 00:26:57.200 align:start position:0% investing has been quite risky 00:26:57.200 --> 00:27:00.649 align:start position:0% investing has been quite risky forever<00:26:58.400> and<00:26:59.400> so<00:26:59.520> the<00:26:59.700> idea<00:27:00.000> is<00:27:00.179> kind<00:27:00.419> of<00:27:00.480> a 00:27:00.649 --> 00:27:00.659 align:start position:0% forever and so the idea is kind of a 00:27:00.659 --> 00:27:03.470 align:start position:0% forever and so the idea is kind of a generalized<00:27:01.440> pressure<00:27:01.799> release<00:27:02.159> valve<00:27:02.700> so<00:27:03.299> if 00:27:03.470 --> 00:27:03.480 align:start position:0% generalized pressure release valve so if 00:27:03.480 --> 00:27:05.870 align:start position:0% generalized pressure release valve so if a<00:27:03.720> condition<00:27:04.020> is<00:27:04.320> met<00:27:04.559> whatever<00:27:05.340> investment 00:27:05.870 --> 00:27:05.880 align:start position:0% a condition is met whatever investment 00:27:05.880 --> 00:27:08.570 align:start position:0% a condition is met whatever investment you<00:27:06.360> have<00:27:06.539> if<00:27:07.380> it<00:27:07.679> crosses<00:27:08.159> over<00:27:08.340> that 00:27:08.570 --> 00:27:08.580 align:start position:0% you have if it crosses over that 00:27:08.580 --> 00:27:11.390 align:start position:0% you have if it crosses over that threshold<00:27:09.000> and<00:27:09.779> pull<00:27:10.020> pull<00:27:10.380> out<00:27:10.980> you<00:27:11.340> know 00:27:11.390 --> 00:27:11.400 align:start position:0% threshold and pull pull out you know 00:27:11.400 --> 00:27:13.430 align:start position:0% threshold and pull pull out you know pull<00:27:11.580> out<00:27:11.700> to<00:27:11.880> wallet<00:27:12.240> essentially<00:27:12.720> so<00:27:13.320> you 00:27:13.430 --> 00:27:13.440 align:start position:0% pull out to wallet essentially so you 00:27:13.440 --> 00:27:15.830 align:start position:0% pull out to wallet essentially so you can<00:27:13.559> think<00:27:13.679> of<00:27:13.799> a<00:27:13.980> liquidity<00:27:14.640> pool<00:27:14.880> you're 00:27:15.830 --> 00:27:15.840 align:start position:0% can think of a liquidity pool you're 00:27:15.840 --> 00:27:18.289 align:start position:0% can think of a liquidity pool you're invested<00:27:16.260> in<00:27:16.380> there<00:27:16.500> but<00:27:16.740> if<00:27:17.100> the<00:27:17.400> two<00:27:18.000> assets 00:27:18.289 --> 00:27:18.299 align:start position:0% invested in there but if the two assets 00:27:18.299 --> 00:27:20.029 align:start position:0% invested in there but if the two assets start<00:27:18.539> deviating<00:27:18.960> Beyond<00:27:19.380> a<00:27:19.559> certain<00:27:19.679> range 00:27:20.029 --> 00:27:20.039 align:start position:0% start deviating Beyond a certain range 00:27:20.039 --> 00:27:24.250 align:start position:0% start deviating Beyond a certain range and<00:27:20.760> you<00:27:20.940> you<00:27:21.059> exit<00:27:21.419> that<00:27:21.600> position 00:27:24.250 --> 00:27:24.260 align:start position:0% 00:27:24.260 --> 00:27:28.130 align:start position:0% thank<00:27:25.260> you<00:27:25.380> Greg<00:27:25.820> anyone<00:27:26.820> else 00:27:28.130 --> 00:27:28.140 align:start position:0% thank you Greg anyone else 00:27:28.140 --> 00:27:30.350 align:start position:0% thank you Greg anyone else you<00:27:28.620> look<00:27:28.799> like<00:27:28.919> you<00:27:29.039> have<00:27:29.159> an<00:27:29.279> idea 00:27:30.350 --> 00:27:30.360 align:start position:0% you look like you have an idea 00:27:30.360 --> 00:27:32.230 align:start position:0% you look like you have an idea okay 00:27:32.230 --> 00:27:32.240 align:start position:0% okay 00:27:32.240 --> 00:27:35.990 align:start position:0% okay Quick<00:27:33.240> Pitch<00:27:33.539> here<00:27:33.720> let's<00:27:34.080> hear<00:27:34.260> it 00:27:35.990 --> 00:27:36.000 align:start position:0% Quick Pitch here let's hear it 00:27:36.000 --> 00:27:38.450 align:start position:0% Quick Pitch here let's hear it um<00:27:36.120> I'll<00:27:36.360> try<00:27:36.659> to<00:27:36.779> make<00:27:37.140> it<00:27:37.320> very<00:27:37.559> quick<00:27:37.799> yeah 00:27:38.450 --> 00:27:38.460 align:start position:0% um I'll try to make it very quick yeah 00:27:38.460 --> 00:27:40.730 align:start position:0% um I'll try to make it very quick yeah what<00:27:38.700> I've<00:27:38.940> learned<00:27:39.240> throughout<00:27:39.779> a<00:27:39.840> lot<00:27:40.020> of<00:27:40.200> uh 00:27:40.730 --> 00:27:40.740 align:start position:0% what I've learned throughout a lot of uh 00:27:40.740 --> 00:27:44.149 align:start position:0% what I've learned throughout a lot of uh oh<00:27:41.340> worry<00:27:42.000> Parable<00:27:42.539> loss<00:27:43.080> experiences<00:27:43.679> is 00:27:44.149 --> 00:27:44.159 align:start position:0% oh worry Parable loss experiences is 00:27:44.159 --> 00:27:47.750 align:start position:0% oh worry Parable loss experiences is that<00:27:44.400> you<00:27:44.820> have<00:27:44.940> to<00:27:45.320> optimize<00:27:46.320> your<00:27:46.500> buys<00:27:46.980> uh 00:27:47.750 --> 00:27:47.760 align:start position:0% that you have to optimize your buys uh 00:27:47.760 --> 00:27:49.789 align:start position:0% that you have to optimize your buys uh that's<00:27:48.360> a<00:27:48.539> strategy<00:27:48.960> for<00:27:49.200> centralized 00:27:49.789 --> 00:27:49.799 align:start position:0% that's a strategy for centralized 00:27:49.799 --> 00:27:53.029 align:start position:0% that's a strategy for centralized Finance<00:27:50.580> I<00:27:50.820> mean<00:27:51.000> centralized<00:27:51.539> trading<00:27:52.080> but<00:27:52.740> I 00:27:53.029 --> 00:27:53.039 align:start position:0% Finance I mean centralized trading but I 00:27:53.039 --> 00:27:56.990 align:start position:0% Finance I mean centralized trading but I it<00:27:53.520> it<00:27:54.000> does<00:27:54.240> work<00:27:54.480> for<00:27:54.900> defy<00:27:55.440> and<00:27:55.740> helping<00:27:56.100> and 00:27:56.990 --> 00:27:57.000 align:start position:0% it it does work for defy and helping and 00:27:57.000 --> 00:28:00.409 align:start position:0% it it does work for defy and helping and it's<00:27:57.720> basically<00:27:58.279> spotting<00:27:59.279> when<00:27:59.940> the<00:28:00.240> price 00:28:00.409 --> 00:28:00.419 align:start position:0% it's basically spotting when the price 00:28:00.419 --> 00:28:03.230 align:start position:0% it's basically spotting when the price hits<00:28:01.260> it<00:28:01.500> hits<00:28:01.799> the<00:28:01.919> threshold<00:28:02.460> and<00:28:02.820> it<00:28:03.000> when 00:28:03.230 --> 00:28:03.240 align:start position:0% hits it hits the threshold and it when 00:28:03.240 --> 00:28:05.450 align:start position:0% hits it hits the threshold and it when when<00:28:03.480> it's<00:28:03.720> oversold<00:28:04.260> within<00:28:04.919> the<00:28:05.039> Bollinger 00:28:05.450 --> 00:28:05.460 align:start position:0% when it's oversold within the Bollinger 00:28:05.460 --> 00:28:08.630 align:start position:0% when it's oversold within the Bollinger Bands<00:28:05.940> like<00:28:06.120> I<00:28:06.360> mean<00:28:06.539> like<00:28:07.080> in<00:28:07.559> the<00:28:07.740> in<00:28:08.400> the 00:28:08.630 --> 00:28:08.640 align:start position:0% Bands like I mean like in the in the 00:28:08.640 --> 00:28:10.669 align:start position:0% Bands like I mean like in the in the lower<00:28:08.820> part<00:28:09.120> of<00:28:09.299> the<00:28:09.360> Bollinger<00:28:09.840> Bands<00:28:10.200> and 00:28:10.669 --> 00:28:10.679 align:start position:0% lower part of the Bollinger Bands and 00:28:10.679 --> 00:28:12.169 align:start position:0% lower part of the Bollinger Bands and you<00:28:10.799> you<00:28:11.100> want<00:28:11.340> to<00:28:11.460> do<00:28:11.580> that<00:28:11.700> you<00:28:11.940> want<00:28:12.059> to 00:28:12.169 --> 00:28:12.179 align:start position:0% you you want to do that you want to 00:28:12.179 --> 00:28:14.810 align:start position:0% you you want to do that you want to identify<00:28:12.600> that<00:28:12.900> buy<00:28:13.200> signal<00:28:13.620> throughout<00:28:14.279> uh 00:28:14.810 --> 00:28:14.820 align:start position:0% identify that buy signal throughout uh 00:28:14.820 --> 00:28:17.210 align:start position:0% identify that buy signal throughout uh different<00:28:15.179> uh<00:28:15.860> temporarily<00:28:16.860> these 00:28:17.210 --> 00:28:17.220 align:start position:0% different uh temporarily these 00:28:17.220 --> 00:28:19.430 align:start position:0% different uh temporarily these temporality 00:28:19.430 --> 00:28:19.440 align:start position:0% temporality 00:28:19.440 --> 00:28:21.950 align:start position:0% temporality um like<00:28:20.220> the<00:28:20.580> weekly<00:28:21.000> time<00:28:21.240> frame<00:28:21.480> the<00:28:21.779> daily 00:28:21.950 --> 00:28:21.960 align:start position:0% um like the weekly time frame the daily 00:28:21.960 --> 00:28:24.350 align:start position:0% um like the weekly time frame the daily time<00:28:22.260> frame<00:28:22.559> and<00:28:22.919> maybe<00:28:23.159> not<00:28:23.460> no<00:28:23.820> shorter<00:28:24.240> term 00:28:24.350 --> 00:28:24.360 align:start position:0% time frame and maybe not no shorter term 00:28:24.360 --> 00:28:26.450 align:start position:0% time frame and maybe not no shorter term like<00:28:24.720> the<00:28:24.960> time<00:28:25.260> frames<00:28:25.559> maybe<00:28:25.860> the<00:28:26.100> three<00:28:26.279> day 00:28:26.450 --> 00:28:26.460 align:start position:0% like the time frames maybe the three day 00:28:26.460 --> 00:28:29.210 align:start position:0% like the time frames maybe the three day time<00:28:26.700> frame<00:28:27.000> I<00:28:27.360> don't<00:28:27.480> know<00:28:27.600> but<00:28:28.260> they<00:28:29.039> are 00:28:29.210 --> 00:28:29.220 align:start position:0% time frame I don't know but they are 00:28:29.220 --> 00:28:31.610 align:start position:0% time frame I don't know but they are identifying<00:28:29.760> buy<00:28:30.659> signals<00:28:31.200> throughout 00:28:31.610 --> 00:28:31.620 align:start position:0% identifying buy signals throughout 00:28:31.620 --> 00:28:33.470 align:start position:0% identifying buy signals throughout different<00:28:32.220> temporalities<00:28:32.880> using<00:28:33.240> the<00:28:33.360> build 00:28:33.470 --> 00:28:33.480 align:start position:0% different temporalities using the build 00:28:33.480 --> 00:28:35.390 align:start position:0% different temporalities using the build mirror<00:28:33.960> pens<00:28:34.140> those<00:28:34.500> the<00:28:34.799> that's<00:28:35.159> that's 00:28:35.390 --> 00:28:35.400 align:start position:0% mirror pens those the that's that's 00:28:35.400 --> 00:28:39.649 align:start position:0% mirror pens those the that's that's basically 00:28:39.649 --> 00:28:39.659 align:start position:0% 00:28:39.659 --> 00:28:42.110 align:start position:0% oh<00:28:40.140> it's<00:28:40.380> working<00:28:40.620> yeah<00:28:40.980> you<00:28:41.700> look<00:28:41.820> like<00:28:41.940> you 00:28:42.110 --> 00:28:42.120 align:start position:0% oh it's working yeah you look like you 00:28:42.120 --> 00:28:43.190 align:start position:0% oh it's working yeah you look like you have<00:28:42.240> an<00:28:42.360> idea 00:28:43.190 --> 00:28:43.200 align:start position:0% have an idea 00:28:43.200 --> 00:28:44.990 align:start position:0% have an idea no<00:28:43.740> okay 00:28:44.990 --> 00:28:45.000 align:start position:0% no okay 00:28:45.000 --> 00:28:48.710 align:start position:0% no okay you<00:28:45.299> have<00:28:45.419> an<00:28:45.539> idea<00:28:45.720> okay 00:28:48.710 --> 00:28:48.720 align:start position:0% 00:28:48.720 --> 00:28:50.810 align:start position:0% um<00:28:48.779> so<00:28:49.020> we<00:28:49.140> discussed<00:28:49.440> an<00:28:49.679> idea<00:28:49.980> of<00:28:50.159> Auto 00:28:50.810 --> 00:28:50.820 align:start position:0% um so we discussed an idea of Auto 00:28:50.820 --> 00:28:53.570 align:start position:0% um so we discussed an idea of Auto rebalancing<00:28:51.480> crypto<00:28:51.900> index<00:28:52.260> so<00:28:53.159> let's<00:28:53.400> say 00:28:53.570 --> 00:28:53.580 align:start position:0% rebalancing crypto index so let's say 00:28:53.580 --> 00:28:55.610 align:start position:0% rebalancing crypto index so let's say you<00:28:53.820> want<00:28:54.059> to<00:28:54.179> build<00:28:54.299> a<00:28:54.539> simple<00:28:54.720> index<00:28:55.440> that's 00:28:55.610 --> 00:28:55.620 align:start position:0% you want to build a simple index that's 00:28:55.620 --> 00:28:59.390 align:start position:0% you want to build a simple index that's like<00:28:55.919> 50<00:28:56.179> wrapped<00:28:57.179> VTC<00:28:57.539> 50<00:28:57.779> wrapped<00:28:58.620> if 00:28:59.390 --> 00:28:59.400 align:start position:0% like 50 wrapped VTC 50 wrapped if 00:28:59.400 --> 00:29:02.870 align:start position:0% like 50 wrapped VTC 50 wrapped if over<00:28:59.700> time<00:29:00.059> that<00:29:00.539> balance<00:29:01.020> is<00:29:01.200> gonna<00:29:01.880> be 00:29:02.870 --> 00:29:02.880 align:start position:0% over time that balance is gonna be 00:29:02.880 --> 00:29:04.549 align:start position:0% over time that balance is gonna be different<00:29:03.000> 50<00:29:03.360> 50<00:29:03.600> if<00:29:03.900> the<00:29:04.020> price<00:29:04.140> of<00:29:04.320> Bitcoin 00:29:04.549 --> 00:29:04.559 align:start position:0% different 50 50 if the price of Bitcoin 00:29:04.559 --> 00:29:06.890 align:start position:0% different 50 50 if the price of Bitcoin increases<00:29:04.980> for<00:29:05.159> example<00:29:05.400> so<00:29:05.760> maybe<00:29:06.419> using 00:29:06.890 --> 00:29:06.900 align:start position:0% increases for example so maybe using 00:29:06.900 --> 00:29:10.990 align:start position:0% increases for example so maybe using some<00:29:07.620> some<00:29:07.799> kind<00:29:08.039> of<00:29:08.220> feed<00:29:08.580> like<00:29:08.880> that<00:29:09.059> to 00:29:10.990 --> 00:29:11.000 align:start position:0% some some kind of feed like that to 00:29:11.000 --> 00:29:13.250 align:start position:0% some some kind of feed like that to calculate<00:29:12.000> the<00:29:12.179> balance<00:29:12.539> of<00:29:12.659> your<00:29:12.779> portfolio 00:29:13.250 --> 00:29:13.260 align:start position:0% calculate the balance of your portfolio 00:29:13.260 --> 00:29:19.269 align:start position:0% calculate the balance of your portfolio and<00:29:14.220> rebalance<00:29:14.880> every<00:29:15.120> hour<00:29:15.980> week<00:29:16.980> whatever 00:29:19.269 --> 00:29:19.279 align:start position:0% and rebalance every hour week whatever 00:29:19.279 --> 00:29:23.090 align:start position:0% and rebalance every hour week whatever cool<00:29:20.279> yeah<00:29:20.640> rebalancing<00:29:21.480> I<00:29:21.600> think<00:29:21.779> is<00:29:21.960> a<00:29:22.260> is<00:29:22.860> a 00:29:23.090 --> 00:29:23.100 align:start position:0% cool yeah rebalancing I think is a is a 00:29:23.100 --> 00:29:25.070 align:start position:0% cool yeah rebalancing I think is a is a very<00:29:23.220> good<00:29:23.460> use<00:29:23.640> case<00:29:23.820> like<00:29:24.059> in<00:29:24.240> whether<00:29:24.899> it's 00:29:25.070 --> 00:29:25.080 align:start position:0% very good use case like in whether it's 00:29:25.080 --> 00:29:26.930 align:start position:0% very good use case like in whether it's you<00:29:25.440> know<00:29:25.500> just<00:29:25.860> a<00:29:26.039> simple<00:29:26.279> spot<00:29:26.520> trading 00:29:26.930 --> 00:29:26.940 align:start position:0% you know just a simple spot trading 00:29:26.940 --> 00:29:28.850 align:start position:0% you know just a simple spot trading portfolio<00:29:27.840> or<00:29:28.140> it's<00:29:28.320> you<00:29:28.500> know<00:29:28.620> something<00:29:28.679> a 00:29:28.850 --> 00:29:28.860 align:start position:0% portfolio or it's you know something a 00:29:28.860 --> 00:29:30.289 align:start position:0% portfolio or it's you know something a little<00:29:28.919> more<00:29:29.039> complicated<00:29:29.279> like<00:29:29.520> lping<00:29:30.059> or 00:29:30.289 --> 00:29:30.299 align:start position:0% little more complicated like lping or 00:29:30.299 --> 00:29:32.570 align:start position:0% little more complicated like lping or Landing<00:29:30.659> or<00:29:30.720> borrowing<00:29:31.020> that<00:29:31.200> kind<00:29:31.380> of<00:29:31.440> stuff 00:29:32.570 --> 00:29:32.580 align:start position:0% Landing or borrowing that kind of stuff 00:29:32.580 --> 00:29:35.210 align:start position:0% Landing or borrowing that kind of stuff um<00:29:32.640> do<00:29:32.940> we<00:29:33.059> have<00:29:33.120> time<00:29:33.240> for<00:29:33.360> one<00:29:33.480> more<00:29:33.659> maybe 00:29:35.210 --> 00:29:35.220 align:start position:0% um do we have time for one more maybe 00:29:35.220 --> 00:29:36.950 align:start position:0% um do we have time for one more maybe we<00:29:35.279> have<00:29:35.700> a<00:29:35.820> little<00:29:35.880> time<00:29:36.059> okay<00:29:36.480> it's<00:29:36.779> okay 00:29:36.950 --> 00:29:36.960 align:start position:0% we have a little time okay it's okay 00:29:36.960 --> 00:29:42.169 align:start position:0% we have a little time okay it's okay anyone<00:29:37.380> else<00:29:37.559> cool 00:29:42.169 --> 00:29:42.179 align:start position:0% 00:29:42.179 --> 00:29:43.190 align:start position:0% so 00:29:43.190 --> 00:29:43.200 align:start position:0% so 00:29:43.200 --> 00:29:45.889 align:start position:0% so um<00:29:43.520> like<00:29:44.640> um<00:29:44.640> none<00:29:44.880> of<00:29:45.000> us<00:29:45.059> were<00:29:45.600> actually<00:29:45.779> in 00:29:45.889 --> 00:29:45.899 align:start position:0% um like um none of us were actually in 00:29:45.899 --> 00:29:47.330 align:start position:0% um like um none of us were actually in device<00:29:46.080> space<00:29:46.380> but<00:29:46.559> we<00:29:46.799> actually<00:29:46.919> uh<00:29:47.100> thought 00:29:47.330 --> 00:29:47.340 align:start position:0% device space but we actually uh thought 00:29:47.340 --> 00:29:49.070 align:start position:0% device space but we actually uh thought about<00:29:47.460> some<00:29:47.700> other<00:29:47.880> use<00:29:48.299> cases 00:29:49.070 --> 00:29:49.080 align:start position:0% about some other use cases 00:29:49.080 --> 00:29:52.789 align:start position:0% about some other use cases um<00:29:49.200> so<00:29:50.340> um<00:29:50.399> I'm<00:29:50.640> working<00:29:50.940> on<00:29:51.779> um<00:29:51.840> a<00:29:52.020> reputation 00:29:52.789 --> 00:29:52.799 align:start position:0% um so um I'm working on um a reputation 00:29:52.799 --> 00:29:54.470 align:start position:0% um so um I'm working on um a reputation on<00:29:53.100> computation<00:29:53.520> protocol 00:29:54.470 --> 00:29:54.480 align:start position:0% on computation protocol 00:29:54.480 --> 00:29:55.850 align:start position:0% on computation protocol um<00:29:54.539> based<00:29:54.840> upon<00:29:55.020> Paradise<00:29:55.380> trust<00:29:55.620> like<00:29:55.740> a 00:29:55.850 --> 00:29:55.860 align:start position:0% um based upon Paradise trust like a 00:29:55.860 --> 00:29:57.710 align:start position:0% um based upon Paradise trust like a whole<00:29:55.980> trust<00:29:56.279> to<00:29:56.399> him<00:29:56.580> by<00:29:56.700> how<00:29:56.820> much<00:29:57.000> and<00:29:57.600> then 00:29:57.710 --> 00:29:57.720 align:start position:0% whole trust to him by how much and then 00:29:57.720 --> 00:29:59.510 align:start position:0% whole trust to him by how much and then I'm<00:29:57.960> like<00:29:58.260> in<00:29:58.500> my<00:29:58.620> output<00:29:58.860> would<00:29:59.279> be<00:29:59.399> a<00:29:59.460> bit 00:29:59.510 --> 00:29:59.520 align:start position:0% I'm like in my output would be a bit 00:29:59.520 --> 00:30:01.970 align:start position:0% I'm like in my output would be a bit basically<00:29:59.820> the<00:30:00.000> number<00:30:00.179> crunching<00:30:00.659> would<00:30:00.840> be 00:30:01.970 --> 00:30:01.980 align:start position:0% basically the number crunching would be 00:30:01.980 --> 00:30:04.250 align:start position:0% basically the number crunching would be um like<00:30:02.399> after<00:30:03.120> all<00:30:03.360> that<00:30:03.539> because<00:30:03.960> of<00:30:04.200> the 00:30:04.250 --> 00:30:04.260 align:start position:0% um like after all that because of the 00:30:04.260 --> 00:30:06.350 align:start position:0% um like after all that because of the calculation<00:30:04.559> like<00:30:05.100> um<00:30:05.100> each<00:30:05.580> peer<00:30:06.120> in<00:30:06.240> my 00:30:06.350 --> 00:30:06.360 align:start position:0% calculation like um each peer in my 00:30:06.360 --> 00:30:08.210 align:start position:0% calculation like um each peer in my network<00:30:06.539> is<00:30:07.140> um<00:30:07.140> assigned<00:30:07.559> a<00:30:07.679> trust<00:30:07.919> score 00:30:08.210 --> 00:30:08.220 align:start position:0% network is um assigned a trust score 00:30:08.220 --> 00:30:10.070 align:start position:0% network is um assigned a trust score right<00:30:08.580> and<00:30:09.059> like<00:30:09.179> he's<00:30:09.480> actually<00:30:09.720> from<00:30:09.960> the 00:30:10.070 --> 00:30:10.080 align:start position:0% right and like he's actually from the 00:30:10.080 --> 00:30:12.350 align:start position:0% right and like he's actually from the dial<00:30:10.620> space<00:30:10.919> and<00:30:11.220> we<00:30:11.640> talked<00:30:11.820> about<00:30:11.940> how<00:30:12.240> they 00:30:12.350 --> 00:30:12.360 align:start position:0% dial space and we talked about how they 00:30:12.360 --> 00:30:14.149 align:start position:0% dial space and we talked about how they can<00:30:12.539> actually<00:30:13.020> use<00:30:13.200> this<00:30:13.740> um<00:30:13.740> this<00:30:13.980> type<00:30:14.100> of 00:30:14.149 --> 00:30:14.159 align:start position:0% can actually use this um this type of 00:30:14.159 --> 00:30:16.730 align:start position:0% can actually use this um this type of algorithm<00:30:14.700> in<00:30:15.299> like<00:30:15.419> a<00:30:15.600> voting<00:30:16.080> uh<00:30:16.440> versus 00:30:16.730 --> 00:30:16.740 align:start position:0% algorithm in like a voting uh versus 00:30:16.740 --> 00:30:20.450 align:start position:0% algorithm in like a voting uh versus like<00:30:17.039> a<00:30:17.220> simple<00:30:17.399> prevention<00:30:18.240> typically<00:30:19.740> um<00:30:19.740> my 00:30:20.450 --> 00:30:20.460 align:start position:0% like a simple prevention typically um my 00:30:20.460 --> 00:30:21.950 align:start position:0% like a simple prevention typically um my algorithm<00:30:20.820> is<00:30:21.000> pretty<00:30:21.240> good<00:30:21.419> at<00:30:21.539> like<00:30:21.720> I'm 00:30:21.950 --> 00:30:21.960 align:start position:0% algorithm is pretty good at like I'm 00:30:21.960 --> 00:30:24.049 align:start position:0% algorithm is pretty good at like I'm identifying<00:30:22.679> the<00:30:22.860> Civil<00:30:23.340> clusters<00:30:23.700> who 00:30:24.049 --> 00:30:24.059 align:start position:0% identifying the Civil clusters who 00:30:24.059 --> 00:30:25.789 align:start position:0% identifying the Civil clusters who actually<00:30:24.240> trust<00:30:24.600> each<00:30:24.779> other<00:30:24.899> but<00:30:25.080> like<00:30:25.260> none 00:30:25.789 --> 00:30:25.799 align:start position:0% actually trust each other but like none 00:30:25.799 --> 00:30:27.470 align:start position:0% actually trust each other but like none of<00:30:25.860> the<00:30:25.980> other<00:30:26.100> real<00:30:26.340> people<00:30:26.520> actually<00:30:26.760> trust 00:30:27.470 --> 00:30:27.480 align:start position:0% of the other real people actually trust 00:30:27.480 --> 00:30:29.870 align:start position:0% of the other real people actually trust any<00:30:27.899> of<00:30:28.020> them<00:30:28.140> so<00:30:28.860> maybe<00:30:29.220> we<00:30:29.640> can<00:30:29.760> actually 00:30:29.870 --> 00:30:29.880 align:start position:0% any of them so maybe we can actually 00:30:29.880 --> 00:30:31.669 align:start position:0% any of them so maybe we can actually ingest<00:30:30.240> this<00:30:30.419> data<00:30:30.779> and<00:30:30.899> then<00:30:31.320> um<00:30:31.320> do<00:30:31.559> that 00:30:31.669 --> 00:30:31.679 align:start position:0% ingest this data and then um do that 00:30:31.679 --> 00:30:33.710 align:start position:0% ingest this data and then um do that number<00:30:31.980> crunching<00:30:32.520> identify<00:30:33.059> those<00:30:33.240> civil 00:30:33.710 --> 00:30:33.720 align:start position:0% number crunching identify those civil 00:30:33.720 --> 00:30:35.930 align:start position:0% number crunching identify those civil culture<00:30:33.960> and<00:30:34.200> then<00:30:34.740> um<00:30:34.740> his<00:30:35.039> Dao<00:30:35.460> could 00:30:35.930 --> 00:30:35.940 align:start position:0% culture and then um his Dao could 00:30:35.940 --> 00:30:37.549 align:start position:0% culture and then um his Dao could actually<00:30:36.419> um<00:30:36.539> emit<00:30:36.899> something<00:30:37.080> onto<00:30:37.440> the 00:30:37.549 --> 00:30:37.559 align:start position:0% actually um emit something onto the 00:30:37.559 --> 00:30:40.310 align:start position:0% actually um emit something onto the contract<00:30:37.919> so<00:30:38.279> I<00:30:38.460> sort<00:30:38.580> of<00:30:38.640> like<00:30:38.760> those<00:30:39.299> um 00:30:40.310 --> 00:30:40.320 align:start position:0% contract so I sort of like those um 00:30:40.320 --> 00:30:42.830 align:start position:0% contract so I sort of like those um um<00:30:40.440> accounts<00:30:41.039> as<00:30:41.220> potential<00:30:42.059> maybe<00:30:42.600> like 00:30:42.830 --> 00:30:42.840 align:start position:0% um accounts as potential maybe like 00:30:42.840 --> 00:30:47.029 align:start position:0% um accounts as potential maybe like avoid<00:30:43.200> them<00:30:43.440> you<00:30:43.679> know<00:30:43.740> things<00:30:43.980> like<00:30:44.159> that 00:30:47.029 --> 00:30:47.039 align:start position:0% 00:30:47.039 --> 00:30:50.029 align:start position:0% cool<00:30:47.580> thank<00:30:47.880> you<00:30:48.480> maybe<00:30:49.020> one<00:30:49.320> more<00:30:49.440> if<00:30:49.740> anyone 00:30:50.029 --> 00:30:50.039 align:start position:0% cool thank you maybe one more if anyone 00:30:50.039 --> 00:30:52.070 align:start position:0% cool thank you maybe one more if anyone has<00:30:50.159> one<00:30:50.340> if<00:30:50.640> not<00:30:50.820> it's<00:30:51.059> okay 00:30:52.070 --> 00:30:52.080 align:start position:0% has one if not it's okay 00:30:52.080 --> 00:30:55.370 align:start position:0% has one if not it's okay anyone<00:30:52.980> Keen<00:30:53.279> to<00:30:53.399> share 00:30:55.370 --> 00:30:55.380 align:start position:0% anyone Keen to share 00:30:55.380 --> 00:30:57.409 align:start position:0% anyone Keen to share Adrian<00:30:56.279> you<00:30:56.460> you<00:30:56.760> look<00:30:56.940> like<00:30:57.059> you<00:30:57.179> want<00:30:57.299> to 00:30:57.409 --> 00:30:57.419 align:start position:0% Adrian you you look like you want to 00:30:57.419 --> 00:30:58.269 align:start position:0% Adrian you you look like you want to share 00:30:58.269 --> 00:30:58.279 align:start position:0% share 00:30:58.279 --> 00:31:00.649 align:start position:0% share you're<00:30:59.279> writing<00:30:59.640> your<00:30:59.700> idea<00:31:00.000> right<00:31:00.179> on<00:31:00.539> your 00:31:00.649 --> 00:31:00.659 align:start position:0% you're writing your idea right on your 00:31:00.659 --> 00:31:01.389 align:start position:0% you're writing your idea right on your phone 00:31:01.389 --> 00:31:01.399 align:start position:0% phone 00:31:01.399 --> 00:31:03.889 align:start position:0% phone okay<00:31:02.399> later<00:31:02.760> okay 00:31:03.889 --> 00:31:03.899 align:start position:0% okay later okay 00:31:03.899 --> 00:31:06.590 align:start position:0% okay later okay um<00:31:03.960> cool<00:31:04.260> yeah<00:31:05.039> that's<00:31:05.399> it<00:31:05.820> um<00:31:05.820> so<00:31:06.120> we'll<00:31:06.299> just 00:31:06.590 --> 00:31:06.600 align:start position:0% um cool yeah that's it um so we'll just 00:31:06.600 --> 00:31:08.570 align:start position:0% um cool yeah that's it um so we'll just wrap<00:31:07.140> things<00:31:07.260> up<00:31:07.500> here<00:31:07.679> uh<00:31:08.039> yeah<00:31:08.279> we<00:31:08.460> don't 00:31:08.570 --> 00:31:08.580 align:start position:0% wrap things up here uh yeah we don't 00:31:08.580 --> 00:31:09.649 align:start position:0% wrap things up here uh yeah we don't have<00:31:08.700> time<00:31:08.760> for<00:31:08.940> that<00:31:09.059> I<00:31:09.179> don't<00:31:09.299> think<00:31:09.480> so 00:31:09.649 --> 00:31:09.659 align:start position:0% have time for that I don't think so 00:31:09.659 --> 00:31:11.930 align:start position:0% have time for that I don't think so we'll<00:31:10.020> just<00:31:10.440> go<00:31:10.620> to<00:31:10.679> the<00:31:10.799> last<00:31:10.980> last<00:31:11.279> slide<00:31:11.760> I 00:31:11.930 --> 00:31:11.940 align:start position:0% we'll just go to the last last slide I 00:31:11.940 --> 00:31:14.029 align:start position:0% we'll just go to the last last slide I guess<00:31:12.059> yeah<00:31:12.480> if<00:31:12.899> you<00:31:13.020> want<00:31:13.140> to<00:31:13.320> run<00:31:13.500> with<00:31:13.860> any 00:31:14.029 --> 00:31:14.039 align:start position:0% guess yeah if you want to run with any 00:31:14.039 --> 00:31:15.769 align:start position:0% guess yeah if you want to run with any of<00:31:14.220> these<00:31:14.399> just<00:31:14.640> remember<00:31:15.179> to<00:31:15.419> think<00:31:15.659> about 00:31:15.769 --> 00:31:15.779 align:start position:0% of these just remember to think about 00:31:15.779 --> 00:31:17.750 align:start position:0% of these just remember to think about like<00:31:16.200> we<00:31:16.380> have<00:31:16.559> the<00:31:16.740> basic<00:31:17.039> idea<00:31:17.399> right<00:31:17.640> now 00:31:17.750 --> 00:31:17.760 align:start position:0% like we have the basic idea right now 00:31:17.760 --> 00:31:19.669 align:start position:0% like we have the basic idea right now but<00:31:18.000> there's<00:31:18.120> a<00:31:18.299> lot<00:31:18.360> more<00:31:18.480> to<00:31:18.720> it<00:31:18.899> I<00:31:19.500> think 00:31:19.669 --> 00:31:19.679 align:start position:0% but there's a lot more to it I think 00:31:19.679 --> 00:31:21.950 align:start position:0% but there's a lot more to it I think adversarially<00:31:20.580> where<00:31:21.539> are<00:31:21.720> the<00:31:21.840> attack 00:31:21.950 --> 00:31:21.960 align:start position:0% adversarially where are the attack 00:31:21.960 --> 00:31:23.149 align:start position:0% adversarially where are the attack vectors 00:31:23.149 --> 00:31:23.159 align:start position:0% vectors 00:31:23.159 --> 00:31:25.190 align:start position:0% vectors um<00:31:23.220> how<00:31:23.460> could<00:31:23.580> your<00:31:23.820> strategy<00:31:24.240> be<00:31:24.539> be 00:31:25.190 --> 00:31:25.200 align:start position:0% um how could your strategy be be 00:31:25.200 --> 00:31:26.630 align:start position:0% um how could your strategy be be manipulated 00:31:26.630 --> 00:31:26.640 align:start position:0% manipulated 00:31:26.640 --> 00:31:27.970 align:start position:0% manipulated um<00:31:26.700> you<00:31:27.240> know 00:31:27.970 --> 00:31:27.980 align:start position:0% um you know 00:31:27.980 --> 00:31:32.210 align:start position:0% um you know uh<00:31:28.980> be<00:31:29.520> defensive 00:31:32.210 --> 00:31:32.220 align:start position:0% 00:31:32.220 --> 00:31:34.610 align:start position:0% yeah<00:31:32.520> and<00:31:32.880> then<00:31:33.000> just<00:31:33.179> to<00:31:33.360> close<00:31:33.539> things<00:31:33.779> out 00:31:34.610 --> 00:31:34.620 align:start position:0% yeah and then just to close things out 00:31:34.620 --> 00:31:35.210 align:start position:0% yeah and then just to close things out um 00:31:35.210 --> 00:31:35.220 align:start position:0% um 00:31:35.220 --> 00:31:37.310 align:start position:0% um to<00:31:35.640> mention<00:31:35.760> what<00:31:36.000> we're<00:31:36.120> doing<00:31:36.299> again<00:31:36.480> uh<00:31:37.140> so 00:31:37.310 --> 00:31:37.320 align:start position:0% to mention what we're doing again uh so 00:31:37.320 --> 00:31:38.570 align:start position:0% to mention what we're doing again uh so at<00:31:37.679> component<00:31:38.039> we're<00:31:38.220> building<00:31:38.340> something 00:31:38.570 --> 00:31:38.580 align:start position:0% at component we're building something 00:31:38.580 --> 00:31:40.970 align:start position:0% at component we're building something called<00:31:38.760> blueprint<00:31:39.179> and<00:31:39.840> all<00:31:40.500> of<00:31:40.620> your<00:31:40.799> ideas 00:31:40.970 --> 00:31:40.980 align:start position:0% called blueprint and all of your ideas 00:31:40.980 --> 00:31:42.710 align:start position:0% called blueprint and all of your ideas except<00:31:41.700> for<00:31:41.820> maybe<00:31:42.000> the<00:31:42.179> last<00:31:42.299> one<00:31:42.480> that 00:31:42.710 --> 00:31:42.720 align:start position:0% except for maybe the last one that 00:31:42.720 --> 00:31:44.330 align:start position:0% except for maybe the last one that sounded<00:31:43.140> really<00:31:43.320> cool<00:31:43.500> but<00:31:43.740> it<00:31:44.039> was<00:31:44.159> a<00:31:44.220> little 00:31:44.330 --> 00:31:44.340 align:start position:0% sounded really cool but it was a little 00:31:44.340 --> 00:31:47.149 align:start position:0% sounded really cool but it was a little over<00:31:44.520> my<00:31:44.760> head<00:31:45.299> um<00:31:45.360> but<00:31:45.539> very<00:31:45.720> very<00:31:45.960> cool 00:31:47.149 --> 00:31:47.159 align:start position:0% over my head um but very very cool 00:31:47.159 --> 00:31:49.130 align:start position:0% over my head um but very very cool um<00:31:47.220> but<00:31:47.580> for<00:31:48.000> the<00:31:48.059> defy<00:31:48.419> related<00:31:48.720> stuff<00:31:48.899> at 00:31:49.130 --> 00:31:49.140 align:start position:0% um but for the defy related stuff at 00:31:49.140 --> 00:31:50.810 align:start position:0% um but for the defy related stuff at least<00:31:49.260> and<00:31:49.980> would<00:31:50.220> love<00:31:50.399> to<00:31:50.520> talk<00:31:50.640> to<00:31:50.700> you 00:31:50.810 --> 00:31:50.820 align:start position:0% least and would love to talk to you 00:31:50.820 --> 00:31:52.010 align:start position:0% least and would love to talk to you about<00:31:50.880> what<00:31:51.120> you're<00:31:51.240> doing<00:31:51.360> to<00:31:51.539> see<00:31:51.659> if<00:31:51.720> we<00:31:51.899> can 00:31:52.010 --> 00:31:52.020 align:start position:0% about what you're doing to see if we can 00:31:52.020 --> 00:31:54.230 align:start position:0% about what you're doing to see if we can incorporate<00:31:52.559> that<00:31:52.799> in<00:31:53.159> the<00:31:53.340> stack<00:31:53.580> so<00:31:53.880> if<00:31:54.120> you 00:31:54.230 --> 00:31:54.240 align:start position:0% incorporate that in the stack so if you 00:31:54.240 --> 00:31:55.490 align:start position:0% incorporate that in the stack so if you have<00:31:54.360> any<00:31:54.480> ideas<00:31:54.720> that<00:31:54.960> you<00:31:55.140> actually<00:31:55.200> want<00:31:55.380> to 00:31:55.490 --> 00:31:55.500 align:start position:0% have any ideas that you actually want to 00:31:55.500 --> 00:31:57.169 align:start position:0% have any ideas that you actually want to execute<00:31:55.799> on<00:31:55.919> or<00:31:56.100> you<00:31:56.220> have<00:31:56.399> you<00:31:56.580> know<00:31:56.760> friends 00:31:57.169 --> 00:31:57.179 align:start position:0% execute on or you have you know friends 00:31:57.179 --> 00:31:58.789 align:start position:0% execute on or you have you know friends that<00:31:57.419> like<00:31:57.600> want<00:31:57.899> to<00:31:58.080> build<00:31:58.260> these<00:31:58.620> kind<00:31:58.740> of 00:31:58.789 --> 00:31:58.799 align:start position:0% that like want to build these kind of 00:31:58.799 --> 00:32:00.590 align:start position:0% that like want to build these kind of data<00:31:59.100> driven<00:31:59.340> strategies 00:32:00.590 --> 00:32:00.600 align:start position:0% data driven strategies 00:32:00.600 --> 00:32:03.110 align:start position:0% data driven strategies um<00:32:00.659> we're<00:32:00.960> building<00:32:01.200> tools<00:32:01.919> that<00:32:02.760> basically 00:32:03.110 --> 00:32:03.120 align:start position:0% um we're building tools that basically 00:32:03.120 --> 00:32:05.090 align:start position:0% um we're building tools that basically make<00:32:03.299> the<00:32:03.480> entire<00:32:03.720> process<00:32:04.080> easy<00:32:04.440> so<00:32:04.860> you<00:32:04.980> only 00:32:05.090 --> 00:32:05.100 align:start position:0% make the entire process easy so you only 00:32:05.100 --> 00:32:07.850 align:start position:0% make the entire process easy so you only have<00:32:05.279> to<00:32:05.460> worry<00:32:05.700> about<00:32:06.179> the<00:32:06.480> logic<00:32:06.899> of<00:32:07.679> what 00:32:07.850 --> 00:32:07.860 align:start position:0% have to worry about the logic of what 00:32:07.860 --> 00:32:09.169 align:start position:0% have to worry about the logic of what you're<00:32:07.980> building 00:32:09.169 --> 00:32:09.179 align:start position:0% you're building 00:32:09.179 --> 00:32:10.669 align:start position:0% you're building um<00:32:09.240> so<00:32:09.419> yeah<00:32:09.600> that<00:32:09.840> wraps<00:32:10.080> it<00:32:10.200> up<00:32:10.320> thank<00:32:10.559> you 00:32:10.669 --> 00:32:10.679 align:start position:0% um so yeah that wraps it up thank you 00:32:10.679 --> 00:32:11.870 align:start position:0% um so yeah that wraps it up thank you everyone 00:32:11.870 --> 00:32:11.880 align:start position:0% everyone 00:32:11.880 --> 00:32:20.049 align:start position:0% everyone foreign 00:32:20.049 --> 00:32:20.059 align:start position:0% 00:32:20.059 --> 00:32:22.190 align:start position:0% thanks<00:32:21.059> a<00:32:21.179> lot<00:32:21.240> I<00:32:21.539> know<00:32:21.840> it<00:32:21.960> was<00:32:22.080> an 00:32:22.190 --> 00:32:22.200 align:start position:0% thanks a lot I know it was an 00:32:22.200 --> 00:32:24.230 align:start position:0% thanks a lot I know it was an unconventional<00:32:22.679> Workshop<00:32:23.100> but<00:32:23.520> I<00:32:23.760> appreciate 00:32:24.230 --> 00:32:24.240 align:start position:0% unconventional Workshop but I appreciate 00:32:24.240 --> 00:32:25.970 align:start position:0% unconventional Workshop but I appreciate that<00:32:24.360> everybody<00:32:24.600> was<00:32:24.899> talkative<00:32:25.260> and<00:32:25.620> you 00:32:25.970 --> 00:32:25.980 align:start position:0% that everybody was talkative and you 00:32:25.980 --> 00:32:28.070 align:start position:0% that everybody was talkative and you know<00:32:26.039> engaging<00:32:26.700> instead<00:32:27.179> of<00:32:27.299> just<00:32:27.539> hanging 00:32:28.070 --> 00:32:28.080 align:start position:0% know engaging instead of just hanging 00:32:28.080 --> 00:32:29.510 align:start position:0% know engaging instead of just hanging out<00:32:28.140> on<00:32:28.320> their<00:32:28.500> phones<00:32:28.799> and<00:32:28.980> things<00:32:29.159> like<00:32:29.340> that 00:32:29.510 --> 00:32:29.520 align:start position:0% out on their phones and things like that 00:32:29.520 --> 00:32:32.600 align:start position:0% out on their phones and things like that so<00:32:29.880> it's<00:32:30.299> great