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:14.470 align:start position:0% [Music] 00:00:14.470 --> 00:00:14.480 align:start position:0% 00:00:14.480 --> 00:00:17.810 align:start position:0% ER<00:00:15.480> I'm<00:00:15.900> CTO<00:00:16.199> at<00:00:16.440> streaming<00:00:16.800> fast<00:00:16.980> and<00:00:17.520> I'm 00:00:17.810 --> 00:00:17.820 align:start position:0% ER I'm CTO at streaming fast and I'm 00:00:17.820 --> 00:00:20.510 align:start position:0% ER I'm CTO at streaming fast and I'm also<00:00:18.119> a<00:00:18.300> Pianist<00:00:18.720> a<00:00:19.199> data<00:00:19.560> scientist<00:00:19.980> whatever 00:00:20.510 --> 00:00:20.520 align:start position:0% also a Pianist a data scientist whatever 00:00:20.520 --> 00:00:22.429 align:start position:0% also a Pianist a data scientist whatever that<00:00:20.820> means<00:00:21.119> I'm<00:00:21.600> a<00:00:21.779> father<00:00:21.960> of<00:00:22.260> eight 00:00:22.429 --> 00:00:22.439 align:start position:0% that means I'm a father of eight 00:00:22.439 --> 00:00:24.230 align:start position:0% that means I'm a father of eight beautiful<00:00:22.800> children<00:00:23.160> two<00:00:23.460> of<00:00:23.580> whom<00:00:23.699> which<00:00:23.880> are 00:00:24.230 --> 00:00:24.240 align:start position:0% beautiful children two of whom which are 00:00:24.240 --> 00:00:26.750 align:start position:0% beautiful children two of whom which are there<00:00:24.539> I<00:00:25.140> love<00:00:25.380> designing<00:00:26.100> and<00:00:26.279> crafting 00:00:26.750 --> 00:00:26.760 align:start position:0% there I love designing and crafting 00:00:26.760 --> 00:00:28.490 align:start position:0% there I love designing and crafting software<00:00:27.240> which<00:00:27.539> I've<00:00:27.660> done<00:00:27.840> since<00:00:27.960> I<00:00:28.199> was<00:00:28.320> 12 00:00:28.490 --> 00:00:28.500 align:start position:0% software which I've done since I was 12 00:00:28.500 --> 00:00:31.250 align:start position:0% software which I've done since I was 12 and<00:00:29.220> I'm<00:00:29.400> here<00:00:29.640> today<00:00:29.820> because<00:00:30.480> one<00:00:30.900> day<00:00:31.080> in 00:00:31.250 --> 00:00:31.260 align:start position:0% and I'm here today because one day in 00:00:31.260 --> 00:00:34.670 align:start position:0% and I'm here today because one day in 2013<00:00:32.120> I<00:00:33.120> read<00:00:33.360> the<00:00:33.600> Bitcoin<00:00:33.960> white<00:00:34.140> paper<00:00:34.380> and 00:00:34.670 --> 00:00:34.680 align:start position:0% 2013 I read the Bitcoin white paper and 00:00:34.680 --> 00:00:36.350 align:start position:0% 2013 I read the Bitcoin white paper and that<00:00:34.920> changed<00:00:35.399> the<00:00:35.460> trajectory<00:00:35.880> of<00:00:36.120> my<00:00:36.180> life 00:00:36.350 --> 00:00:36.360 align:start position:0% that changed the trajectory of my life 00:00:36.360 --> 00:00:38.450 align:start position:0% that changed the trajectory of my life and<00:00:36.960> fast<00:00:37.200> forward<00:00:37.380> to<00:00:37.620> today 00:00:38.450 --> 00:00:38.460 align:start position:0% and fast forward to today 00:00:38.460 --> 00:00:40.010 align:start position:0% and fast forward to today streaming<00:00:39.120> fast<00:00:39.239> a<00:00:39.480> company<00:00:39.600> based<00:00:39.960> in 00:00:40.010 --> 00:00:40.020 align:start position:0% streaming fast a company based in 00:00:40.020 --> 00:00:42.110 align:start position:0% streaming fast a company based in Montreal<00:00:40.440> Canada<00:00:40.739> is<00:00:41.399> now<00:00:41.579> one<00:00:41.700> of<00:00:41.879> the<00:00:41.940> core 00:00:42.110 --> 00:00:42.120 align:start position:0% Montreal Canada is now one of the core 00:00:42.120 --> 00:00:45.229 align:start position:0% Montreal Canada is now one of the core developers<00:00:42.660> of<00:00:43.980> the<00:00:44.460> graph 00:00:45.229 --> 00:00:45.239 align:start position:0% developers of the graph 00:00:45.239 --> 00:00:47.209 align:start position:0% developers of the graph and<00:00:45.719> we<00:00:45.899> joined<00:00:46.200> the<00:00:46.320> graph<00:00:46.620> a<00:00:46.860> bit<00:00:46.980> more<00:00:47.100> than 00:00:47.209 --> 00:00:47.219 align:start position:0% and we joined the graph a bit more than 00:00:47.219 --> 00:00:49.069 align:start position:0% and we joined the graph a bit more than a<00:00:47.280> year<00:00:47.399> ago<00:00:47.579> and<00:00:47.820> it<00:00:47.940> kind<00:00:48.180> of<00:00:48.300> bizarre<00:00:48.719> m<00:00:48.899> a 00:00:49.069 --> 00:00:49.079 align:start position:0% a year ago and it kind of bizarre m a 00:00:49.079 --> 00:00:51.529 align:start position:0% a year ago and it kind of bizarre m a 2.0<00:00:49.739> fashion<00:00:50.340> or<00:00:50.820> lawyers<00:00:51.180> they<00:00:51.360> don't 00:00:51.529 --> 00:00:51.539 align:start position:0% 2.0 fashion or lawyers they don't 00:00:51.539 --> 00:00:53.029 align:start position:0% 2.0 fashion or lawyers they don't understand<00:00:51.660> what<00:00:51.960> happened<00:00:52.140> but<00:00:52.559> anyway<00:00:52.739> we 00:00:53.029 --> 00:00:53.039 align:start position:0% understand what happened but anyway we 00:00:53.039 --> 00:00:55.490 align:start position:0% understand what happened but anyway we said<00:00:53.280> thanks<00:00:53.640> and<00:00:54.000> goodbye<00:00:54.360> to<00:00:54.480> our<00:00:54.660> VCS<00:00:55.199> and 00:00:55.490 --> 00:00:55.500 align:start position:0% said thanks and goodbye to our VCS and 00:00:55.500 --> 00:00:57.529 align:start position:0% said thanks and goodbye to our VCS and shifted<00:00:55.920> our<00:00:56.100> Focus<00:00:56.280> to<00:00:56.520> make<00:00:56.579> the<00:00:56.879> graph<00:00:57.120> the 00:00:57.529 --> 00:00:57.539 align:start position:0% shifted our Focus to make the graph the 00:00:57.539 --> 00:00:59.750 align:start position:0% shifted our Focus to make the graph the greatest<00:00:57.719> data<00:00:58.500> platform<00:00:58.739> on<00:00:58.980> Earth 00:00:59.750 --> 00:00:59.760 align:start position:0% greatest data platform on Earth 00:00:59.760 --> 00:01:01.430 align:start position:0% greatest data platform on Earth so<00:01:00.180> today<00:01:00.360> I'm<00:01:00.600> here<00:01:00.840> to<00:01:01.020> introduce 00:01:01.430 --> 00:01:01.440 align:start position:0% so today I'm here to introduce 00:01:01.440 --> 00:01:04.130 align:start position:0% so today I'm here to introduce substreams<00:01:02.340> which<00:01:02.520> is<00:01:02.699> a<00:01:03.059> powerful<00:01:03.480> new 00:01:04.130 --> 00:01:04.140 align:start position:0% substreams which is a powerful new 00:01:04.140 --> 00:01:06.590 align:start position:0% substreams which is a powerful new paralyzed<00:01:04.860> engine<00:01:05.159> to<00:01:05.580> process<00:01:05.939> blockchain 00:01:06.590 --> 00:01:06.600 align:start position:0% paralyzed engine to process blockchain 00:01:06.600 --> 00:01:08.870 align:start position:0% paralyzed engine to process blockchain data<00:01:07.200> and<00:01:07.799> before<00:01:08.040> I<00:01:08.220> can<00:01:08.340> do<00:01:08.460> that<00:01:08.520> I<00:01:08.760> just 00:01:08.870 --> 00:01:08.880 align:start position:0% data and before I can do that I just 00:01:08.880 --> 00:01:10.609 align:start position:0% data and before I can do that I just want<00:01:09.000> to<00:01:09.119> set<00:01:09.299> a<00:01:09.479> bit<00:01:09.540> of<00:01:09.659> context<00:01:10.080> perhaps<00:01:10.439> you 00:01:10.609 --> 00:01:10.619 align:start position:0% want to set a bit of context perhaps you 00:01:10.619 --> 00:01:12.350 align:start position:0% want to set a bit of context perhaps you can<00:01:10.740> raise<00:01:10.920> your<00:01:11.100> hand<00:01:11.280> if<00:01:11.760> you<00:01:11.820> know<00:01:11.939> what<00:01:12.119> sub 00:01:12.350 --> 00:01:12.360 align:start position:0% can raise your hand if you know what sub 00:01:12.360 --> 00:01:14.810 align:start position:0% can raise your hand if you know what sub graphs<00:01:12.840> are<00:01:13.020> raise<00:01:13.260> your<00:01:13.439> hand<00:01:13.619> if<00:01:13.740> you<00:01:13.860> know 00:01:14.810 --> 00:01:14.820 align:start position:0% graphs are raise your hand if you know 00:01:14.820 --> 00:01:18.350 align:start position:0% graphs are raise your hand if you know you're<00:01:15.600> good<00:01:15.840> okay<00:01:16.799> so<00:01:17.580> slip<00:01:17.820> graphs<00:01:18.180> can<00:01:18.240> be 00:01:18.350 --> 00:01:18.360 align:start position:0% you're good okay so slip graphs can be 00:01:18.360 --> 00:01:21.530 align:start position:0% you're good okay so slip graphs can be thought<00:01:18.540> of<00:01:18.720> an<00:01:19.500> ETL<00:01:19.799> process<00:01:20.280> right<00:01:20.700> extract 00:01:21.530 --> 00:01:21.540 align:start position:0% thought of an ETL process right extract 00:01:21.540 --> 00:01:23.510 align:start position:0% thought of an ETL process right extract transform<00:01:21.960> and<00:01:22.140> load<00:01:22.500> and<00:01:22.740> subgraphs<00:01:23.400> add 00:01:23.510 --> 00:01:23.520 align:start position:0% transform and load and subgraphs add 00:01:23.520 --> 00:01:25.490 align:start position:0% transform and load and subgraphs add that<00:01:23.700> little<00:01:23.880> Q<00:01:24.119> there<00:01:24.420> that<00:01:24.659> graphql<00:01:25.200> layer 00:01:25.490 --> 00:01:25.500 align:start position:0% that little Q there that graphql layer 00:01:25.500 --> 00:01:27.890 align:start position:0% that little Q there that graphql layer to<00:01:25.680> it<00:01:25.799> and<00:01:26.520> some<00:01:26.880> grass<00:01:27.240> today<00:01:27.299> provide<00:01:27.720> that 00:01:27.890 --> 00:01:27.900 align:start position:0% to it and some grass today provide that 00:01:27.900 --> 00:01:30.530 align:start position:0% to it and some grass today provide that sort<00:01:28.140> of<00:01:28.320> simple<00:01:28.560> approachable<00:01:29.540> end-to-end 00:01:30.530 --> 00:01:30.540 align:start position:0% sort of simple approachable end-to-end 00:01:30.540 --> 00:01:32.810 align:start position:0% sort of simple approachable end-to-end solution<00:01:31.140> to<00:01:31.320> blockchain<00:01:31.740> indexing<00:01:32.280> and<00:01:32.640> the 00:01:32.810 --> 00:01:32.820 align:start position:0% solution to blockchain indexing and the 00:01:32.820 --> 00:01:34.550 align:start position:0% solution to blockchain indexing and the graph<00:01:33.000> node<00:01:33.299> is<00:01:33.360> responsible<00:01:33.900> for<00:01:34.259> all<00:01:34.439> of 00:01:34.550 --> 00:01:34.560 align:start position:0% graph node is responsible for all of 00:01:34.560 --> 00:01:36.950 align:start position:0% graph node is responsible for all of these<00:01:34.860> components<00:01:35.700> right<00:01:35.939> the<00:01:36.420> extraction<00:01:36.780> is 00:01:36.950 --> 00:01:36.960 align:start position:0% these components right the extraction is 00:01:36.960 --> 00:01:39.289 align:start position:0% these components right the extraction is done<00:01:37.140> through<00:01:37.320> hitting<00:01:38.040> Json<00:01:38.340> RPC<00:01:38.820> nodes<00:01:39.119> and 00:01:39.289 --> 00:01:39.299 align:start position:0% done through hitting Json RPC nodes and 00:01:39.299 --> 00:01:40.969 align:start position:0% done through hitting Json RPC nodes and then<00:01:39.360> transformation<00:01:39.780> you<00:01:40.500> provide<00:01:40.799> some 00:01:40.969 --> 00:01:40.979 align:start position:0% then transformation you provide some 00:01:40.979 --> 00:01:42.230 align:start position:0% then transformation you provide some assembly<00:01:41.340> script<00:01:41.520> you<00:01:41.759> guys<00:01:41.880> know<00:01:42.000> that 00:01:42.230 --> 00:01:42.240 align:start position:0% assembly script you guys know that 00:01:42.240 --> 00:01:44.030 align:start position:0% assembly script you guys know that composite<00:01:42.659> wasm<00:01:43.079> running<00:01:43.320> in<00:01:43.560> a<00:01:43.680> distributed 00:01:44.030 --> 00:01:44.040 align:start position:0% composite wasm running in a distributed 00:01:44.040 --> 00:01:45.950 align:start position:0% composite wasm running in a distributed environment<00:01:44.400> and<00:01:45.000> then<00:01:45.060> you<00:01:45.240> have<00:01:45.420> the<00:01:45.659> load 00:01:45.950 --> 00:01:45.960 align:start position:0% environment and then you have the load 00:01:45.960 --> 00:01:47.630 align:start position:0% environment and then you have the load aspect<00:01:46.200> which<00:01:46.380> the<00:01:46.560> graph<00:01:46.680> node<00:01:47.040> does<00:01:47.159> puts 00:01:47.630 --> 00:01:47.640 align:start position:0% aspect which the graph node does puts 00:01:47.640 --> 00:01:49.789 align:start position:0% aspect which the graph node does puts that<00:01:47.700> into<00:01:47.880> postgres<00:01:48.360> and<00:01:48.659> offers<00:01:48.960> you<00:01:49.200> a<00:01:49.680> rich 00:01:49.789 --> 00:01:49.799 align:start position:0% that into postgres and offers you a rich 00:01:49.799 --> 00:01:51.710 align:start position:0% that into postgres and offers you a rich you<00:01:50.040> know<00:01:50.100> and<00:01:50.280> beautiful<00:01:50.460> graphql<00:01:51.299> interface 00:01:51.710 --> 00:01:51.720 align:start position:0% you know and beautiful graphql interface 00:01:51.720 --> 00:01:53.510 align:start position:0% you know and beautiful graphql interface on<00:01:51.960> top<00:01:52.140> and<00:01:52.799> one<00:01:52.920> of<00:01:53.040> the<00:01:53.040> reason<00:01:53.100> one<00:01:53.399> of<00:01:53.460> the 00:01:53.510 --> 00:01:53.520 align:start position:0% on top and one of the reason one of the 00:01:53.520 --> 00:01:55.550 align:start position:0% on top and one of the reason one of the reasons<00:01:53.700> we<00:01:53.880> were<00:01:54.000> brought<00:01:54.240> in<00:01:54.420> was<00:01:54.960> that<00:01:55.140> so 00:01:55.550 --> 00:01:55.560 align:start position:0% reasons we were brought in was that so 00:01:55.560 --> 00:01:58.429 align:start position:0% reasons we were brought in was that so we<00:01:55.740> could<00:01:55.860> push<00:01:56.159> the<00:01:56.460> graph<00:01:56.759> to<00:01:57.240> New<00:01:57.479> Height<00:01:57.720> in 00:01:58.429 --> 00:01:58.439 align:start position:0% we could push the graph to New Height in 00:01:58.439 --> 00:02:01.609 align:start position:0% we could push the graph to New Height in terms<00:01:58.619> of<00:01:58.740> performances<00:01:59.460> so<00:02:00.060> to<00:02:00.299> do<00:02:00.540> that<00:02:00.720> we 00:02:01.609 --> 00:02:01.619 align:start position:0% terms of performances so to do that we 00:02:01.619 --> 00:02:03.649 align:start position:0% terms of performances so to do that we brought<00:02:02.040> first<00:02:02.579> thing<00:02:02.820> the<00:02:03.119> fire<00:02:03.420> hose 00:02:03.649 --> 00:02:03.659 align:start position:0% brought first thing the fire hose 00:02:03.659 --> 00:02:07.010 align:start position:0% brought first thing the fire hose something<00:02:04.140> at<00:02:04.560> the<00:02:04.979> extraction<00:02:05.460> layer<00:02:06.000> to<00:02:06.719> our 00:02:07.010 --> 00:02:07.020 align:start position:0% something at the extraction layer to our 00:02:07.020 --> 00:02:09.949 align:start position:0% something at the extraction layer to our take<00:02:07.259> to<00:02:07.500> boosting<00:02:07.920> performance<00:02:08.459> by<00:02:08.880> one<00:02:09.660> two 00:02:09.949 --> 00:02:09.959 align:start position:0% take to boosting performance by one two 00:02:09.959 --> 00:02:12.229 align:start position:0% take to boosting performance by one two three<00:02:10.380> orders<00:02:10.800> of<00:02:10.979> magnitude<00:02:11.520> the<00:02:12.060> first 00:02:12.229 --> 00:02:12.239 align:start position:0% three orders of magnitude the first 00:02:12.239 --> 00:02:14.449 align:start position:0% three orders of magnitude the first layer<00:02:12.540> extraction<00:02:12.959> it's<00:02:13.200> the<00:02:13.440> method<00:02:13.800> of 00:02:14.449 --> 00:02:14.459 align:start position:0% layer extraction it's the method of 00:02:14.459 --> 00:02:16.430 align:start position:0% layer extraction it's the method of extract<00:02:14.760> attracting<00:02:15.480> data<00:02:15.840> from<00:02:16.020> blockchain 00:02:16.430 --> 00:02:16.440 align:start position:0% extract attracting data from blockchain 00:02:16.440 --> 00:02:18.830 align:start position:0% extract attracting data from blockchain nodes<00:02:16.800> imagine<00:02:17.160> prying<00:02:17.819> an<00:02:17.940> egg<00:02:18.120> open<00:02:18.300> where 00:02:18.830 --> 00:02:18.840 align:start position:0% nodes imagine prying an egg open where 00:02:18.840 --> 00:02:20.630 align:start position:0% nodes imagine prying an egg open where the<00:02:19.020> data<00:02:19.260> is<00:02:19.379> exfiltrated<00:02:19.920> as<00:02:20.280> fast<00:02:20.459> as 00:02:20.630 --> 00:02:20.640 align:start position:0% the data is exfiltrated as fast as 00:02:20.640 --> 00:02:23.150 align:start position:0% the data is exfiltrated as fast as possible<00:02:20.940> and<00:02:21.180> all<00:02:21.420> the<00:02:21.599> juicy<00:02:21.959> data<00:02:22.319> gets 00:02:23.150 --> 00:02:23.160 align:start position:0% possible and all the juicy data gets 00:02:23.160 --> 00:02:26.809 align:start position:0% possible and all the juicy data gets then<00:02:23.280> thrown<00:02:23.819> in<00:02:24.360> a<00:02:24.620> grpc<00:02:25.620> stream<00:02:25.920> as<00:02:26.520> well<00:02:26.640> as 00:02:26.809 --> 00:02:26.819 align:start position:0% then thrown in a grpc stream as well as 00:02:26.819 --> 00:02:29.210 align:start position:0% then thrown in a grpc stream as well as into<00:02:27.120> flat<00:02:27.660> files<00:02:28.080> and<00:02:28.739> you<00:02:28.860> can<00:02:28.980> think<00:02:29.099> of 00:02:29.210 --> 00:02:29.220 align:start position:0% into flat files and you can think of 00:02:29.220 --> 00:02:30.949 align:start position:0% into flat files and you can think of that<00:02:29.400> as<00:02:29.580> sort<00:02:29.760> of<00:02:29.879> a<00:02:30.060> the<00:02:30.480> bin<00:02:30.780> log 00:02:30.949 --> 00:02:30.959 align:start position:0% that as sort of a the bin log 00:02:30.959 --> 00:02:33.830 align:start position:0% that as sort of a the bin log replication<00:02:31.680> stream<00:02:32.220> for<00:02:32.580> blockchains<00:02:33.420> where 00:02:33.830 --> 00:02:33.840 align:start position:0% replication stream for blockchains where 00:02:33.840 --> 00:02:35.270 align:start position:0% replication stream for blockchains where you'd<00:02:34.020> find<00:02:34.200> in<00:02:34.319> a<00:02:34.440> Master<00:02:34.560> Slave<00:02:34.860> replication 00:02:35.270 --> 00:02:35.280 align:start position:0% you'd find in a Master Slave replication 00:02:35.280 --> 00:02:37.309 align:start position:0% you'd find in a Master Slave replication engine<00:02:35.459> like<00:02:35.700> in<00:02:35.940> databases<00:02:36.599> so<00:02:37.020> we'll<00:02:37.140> get 00:02:37.309 --> 00:02:37.319 align:start position:0% engine like in databases so we'll get 00:02:37.319 --> 00:02:39.290 align:start position:0% engine like in databases so we'll get back<00:02:37.440> to<00:02:37.560> fire<00:02:37.739> hose<00:02:37.980> in<00:02:38.099> a<00:02:38.220> minute<00:02:38.280> then<00:02:39.060> sub 00:02:39.290 --> 00:02:39.300 align:start position:0% back to fire hose in a minute then sub 00:02:39.300 --> 00:02:41.509 align:start position:0% back to fire hose in a minute then sub streams<00:02:39.780> is<00:02:40.440> sort<00:02:40.739> of<00:02:40.860> a<00:02:40.920> reasoning<00:02:41.340> of<00:02:41.400> this 00:02:41.509 --> 00:02:41.519 align:start position:0% streams is sort of a reasoning of this 00:02:41.519 --> 00:02:43.850 align:start position:0% streams is sort of a reasoning of this rethinking<00:02:42.120> of<00:02:42.360> the<00:02:42.540> second<00:02:42.720> box<00:02:43.080> the 00:02:43.850 --> 00:02:43.860 align:start position:0% rethinking of the second box the 00:02:43.860 --> 00:02:47.089 align:start position:0% rethinking of the second box the transformation<00:02:44.519> layer<00:02:45.239> here<00:02:45.959> instead<00:02:46.860> of<00:02:46.920> the 00:02:47.089 --> 00:02:47.099 align:start position:0% transformation layer here instead of the 00:02:47.099 --> 00:02:48.890 align:start position:0% transformation layer here instead of the traditional<00:02:47.519> sub<00:02:47.879> graph<00:02:48.180> handlers<00:02:48.720> and 00:02:48.890 --> 00:02:48.900 align:start position:0% traditional sub graph handlers and 00:02:48.900 --> 00:02:50.690 align:start position:0% traditional sub graph handlers and assembly<00:02:49.319> script<00:02:49.620> you<00:02:50.340> will<00:02:50.519> write 00:02:50.690 --> 00:02:50.700 align:start position:0% assembly script you will write 00:02:50.700 --> 00:02:53.330 align:start position:0% assembly script you will write substreams<00:02:51.420> modules<00:02:51.840> in<00:02:52.200> Rust<00:02:52.500> and<00:02:52.920> those<00:02:53.099> can 00:02:53.330 --> 00:02:53.340 align:start position:0% substreams modules in Rust and those can 00:02:53.340 --> 00:02:56.270 align:start position:0% substreams modules in Rust and those can be<00:02:53.519> executed<00:02:54.120> in<00:02:54.300> real<00:02:54.540> time<00:02:54.780> as<00:02:55.739> well<00:02:55.920> as<00:02:56.040> in 00:02:56.270 --> 00:02:56.280 align:start position:0% be executed in real time as well as in 00:02:56.280 --> 00:02:59.150 align:start position:0% be executed in real time as well as in parallel<00:02:56.760> with<00:02:57.060> unprecedented<00:02:57.780> performance 00:02:59.150 --> 00:02:59.160 align:start position:0% parallel with unprecedented performance 00:02:59.160 --> 00:03:01.369 align:start position:0% parallel with unprecedented performance so<00:02:59.640> let<00:02:59.819> me<00:03:00.000> give<00:03:00.120> you<00:03:00.300> first<00:03:00.599> a<00:03:00.840> primer<00:03:01.200> on 00:03:01.369 --> 00:03:01.379 align:start position:0% so let me give you first a primer on 00:03:01.379 --> 00:03:02.809 align:start position:0% so let me give you first a primer on fire<00:03:01.560> hose<00:03:01.800> because<00:03:02.040> there's<00:03:02.340> a<00:03:02.519> lot<00:03:02.700> of 00:03:02.809 --> 00:03:02.819 align:start position:0% fire hose because there's a lot of 00:03:02.819 --> 00:03:05.150 align:start position:0% fire hose because there's a lot of benefits<00:03:03.360> of<00:03:03.959> substreams<00:03:04.620> that<00:03:04.980> come 00:03:05.150 --> 00:03:05.160 align:start position:0% benefits of substreams that come 00:03:05.160 --> 00:03:08.210 align:start position:0% benefits of substreams that come directly<00:03:05.640> from<00:03:06.060> the<00:03:06.480> fire<00:03:06.660> hose<00:03:07.019> so<00:03:07.739> a 00:03:08.210 --> 00:03:08.220 align:start position:0% directly from the fire hose so a 00:03:08.220 --> 00:03:09.650 align:start position:0% directly from the fire hose so a streaming<00:03:08.580> fast<00:03:08.700> for<00:03:09.000> many<00:03:09.120> years<00:03:09.300> we've<00:03:09.540> been 00:03:09.650 --> 00:03:09.660 align:start position:0% streaming fast for many years we've been 00:03:09.660 --> 00:03:11.270 align:start position:0% streaming fast for many years we've been thinking<00:03:09.959> hard<00:03:10.140> about<00:03:10.319> all<00:03:10.560> these<00:03:10.739> indexing 00:03:11.270 --> 00:03:11.280 align:start position:0% thinking hard about all these indexing 00:03:11.280 --> 00:03:13.790 align:start position:0% thinking hard about all these indexing problems<00:03:11.819> from<00:03:12.360> first<00:03:12.599> principles<00:03:13.140> and<00:03:13.680> we 00:03:13.790 --> 00:03:13.800 align:start position:0% problems from first principles and we 00:03:13.800 --> 00:03:16.309 align:start position:0% problems from first principles and we needed<00:03:14.099> a<00:03:14.220> first<00:03:14.459> a<00:03:14.760> robust<00:03:15.180> extraction<00:03:15.780> layer 00:03:16.309 --> 00:03:16.319 align:start position:0% needed a first a robust extraction layer 00:03:16.319 --> 00:03:18.470 align:start position:0% needed a first a robust extraction layer we<00:03:16.860> wanted<00:03:17.040> something<00:03:17.280> that<00:03:17.580> is<00:03:17.700> creamy<00:03:18.120> but 00:03:18.470 --> 00:03:18.480 align:start position:0% we wanted something that is creamy but 00:03:18.480 --> 00:03:20.630 align:start position:0% we wanted something that is creamy but that<00:03:18.720> was<00:03:18.780> extremely<00:03:19.200> low<00:03:19.440> latency<00:03:19.980> so<00:03:20.459> I'm 00:03:20.630 --> 00:03:20.640 align:start position:0% that was extremely low latency so I'm 00:03:20.640 --> 00:03:22.490 align:start position:0% that was extremely low latency so I'm thinking<00:03:20.819> that<00:03:21.000> would<00:03:21.239> push<00:03:21.599> data<00:03:21.959> out<00:03:22.140> the 00:03:22.490 --> 00:03:22.500 align:start position:0% thinking that would push data out the 00:03:22.500 --> 00:03:24.649 align:start position:0% thinking that would push data out the moment<00:03:22.800> the<00:03:23.519> transaction<00:03:23.940> was<00:03:24.239> executed 00:03:24.649 --> 00:03:24.659 align:start position:0% moment the transaction was executed 00:03:24.659 --> 00:03:26.930 align:start position:0% moment the transaction was executed within<00:03:25.019> a<00:03:25.140> block<00:03:25.260> within<00:03:25.739> a<00:03:25.860> blockchain<00:03:26.459> node 00:03:26.930 --> 00:03:26.940 align:start position:0% within a block within a blockchain node 00:03:26.940 --> 00:03:29.869 align:start position:0% within a block within a blockchain node Json<00:03:27.659> RPC<00:03:28.140> was<00:03:28.379> not<00:03:28.500> going<00:03:28.680> to<00:03:28.800> cut<00:03:28.980> it<00:03:29.220> and<00:03:29.760> we 00:03:29.869 --> 00:03:29.879 align:start position:0% Json RPC was not going to cut it and we 00:03:29.879 --> 00:03:31.729 align:start position:0% Json RPC was not going to cut it and we didn't<00:03:30.000> want<00:03:30.239> to<00:03:30.360> have<00:03:30.540> to<00:03:30.720> deal<00:03:30.900> with<00:03:31.200> those 00:03:31.729 --> 00:03:31.739 align:start position:0% didn't want to have to deal with those 00:03:31.739 --> 00:03:34.369 align:start position:0% didn't want to have to deal with those large<00:03:32.280> bulky<00:03:32.879> nodes<00:03:33.180> right<00:03:33.420> hang<00:03:33.599> on<00:03:33.840> a<00:03:34.080> thread 00:03:34.369 --> 00:03:34.379 align:start position:0% large bulky nodes right hang on a thread 00:03:34.379 --> 00:03:38.149 align:start position:0% large bulky nodes right hang on a thread occupied<00:03:35.340> due<00:03:35.940> to<00:03:36.060> with<00:03:37.019> uh<00:03:37.260> managing<00:03:37.739> high 00:03:38.149 --> 00:03:38.159 align:start position:0% occupied due to with uh managing high 00:03:38.159 --> 00:03:40.910 align:start position:0% occupied due to with uh managing high right<00:03:38.519> throughput<00:03:39.060> I<00:03:39.780> kept<00:03:40.319> everything<00:03:40.440> in<00:03:40.739> a 00:03:40.910 --> 00:03:40.920 align:start position:0% right throughput I kept everything in a 00:03:40.920 --> 00:03:43.369 align:start position:0% right throughput I kept everything in a key<00:03:41.040> Value<00:03:41.280> Store<00:03:41.640> behind<00:03:42.239> a<00:03:42.420> you<00:03:42.959> know<00:03:43.019> a<00:03:43.140> Json 00:03:43.369 --> 00:03:43.379 align:start position:0% key Value Store behind a you know a Json 00:03:43.379 --> 00:03:46.369 align:start position:0% key Value Store behind a you know a Json RPC<00:03:43.860> requests<00:03:44.340> and<00:03:45.180> it<00:03:45.360> was<00:03:45.540> really<00:03:45.780> heavy<00:03:46.140> in 00:03:46.369 --> 00:03:46.379 align:start position:0% RPC requests and it was really heavy in 00:03:46.379 --> 00:03:48.229 align:start position:0% RPC requests and it was really heavy in Ram<00:03:46.680> and<00:03:46.980> CPU<00:03:47.459> and<00:03:47.640> you<00:03:47.760> needed<00:03:48.000> super 00:03:48.229 --> 00:03:48.239 align:start position:0% Ram and CPU and you needed super 00:03:48.239 --> 00:03:50.630 align:start position:0% Ram and CPU and you needed super optimize<00:03:48.780> ssds<00:03:49.500> this<00:03:49.860> is<00:03:50.040> really<00:03:50.159> annoying 00:03:50.630 --> 00:03:50.640 align:start position:0% optimize ssds this is really annoying 00:03:50.640 --> 00:03:52.490 align:start position:0% optimize ssds this is really annoying and<00:03:50.940> all<00:03:51.060> these<00:03:51.239> things<00:03:51.360> are<00:03:51.659> much<00:03:51.959> costlier 00:03:52.490 --> 00:03:52.500 align:start position:0% and all these things are much costlier 00:03:52.500 --> 00:03:54.350 align:start position:0% and all these things are much costlier than<00:03:52.739> what's<00:03:52.980> needed<00:03:53.280> when<00:03:53.760> our<00:03:53.879> goal<00:03:54.120> was<00:03:54.180> to 00:03:54.350 --> 00:03:54.360 align:start position:0% than what's needed when our goal was to 00:03:54.360 --> 00:03:56.869 align:start position:0% than what's needed when our goal was to get<00:03:54.480> to<00:03:54.659> the<00:03:54.780> data<00:03:55.140> inside<00:03:55.319> so<00:03:56.220> we<00:03:56.340> also<00:03:56.700> wanted 00:03:56.869 --> 00:03:56.879 align:start position:0% get to the data inside so we also wanted 00:03:56.879 --> 00:04:00.410 align:start position:0% get to the data inside so we also wanted proper<00:03:57.720> decoupling<00:03:58.379> between<00:03:59.099> the<00:03:59.760> processes 00:04:00.410 --> 00:04:00.420 align:start position:0% proper decoupling between the processes 00:04:00.420 --> 00:04:02.210 align:start position:0% proper decoupling between the processes producing<00:04:01.200> the<00:04:01.319> data<00:04:01.560> so<00:04:01.680> the<00:04:01.920> blockchain 00:04:02.210 --> 00:04:02.220 align:start position:0% producing the data so the blockchain 00:04:02.220 --> 00:04:03.830 align:start position:0% producing the data so the blockchain knows<00:04:02.459> and<00:04:02.580> its<00:04:02.760> intricacies<00:04:03.180> and<00:04:03.480> it's<00:04:03.599> it's 00:04:03.830 --> 00:04:03.840 align:start position:0% knows and its intricacies and it's it's 00:04:03.840 --> 00:04:05.509 align:start position:0% knows and its intricacies and it's it's request<00:04:04.260> response<00:04:04.799> bottle<00:04:04.980> and<00:04:05.220> they're<00:04:05.340> all 00:04:05.509 --> 00:04:05.519 align:start position:0% request response bottle and they're all 00:04:05.519 --> 00:04:08.270 align:start position:0% request response bottle and they're all different<00:04:05.900> and<00:04:06.900> the<00:04:07.140> data<00:04:07.560> itself<00:04:07.799> we<00:04:08.099> wanted 00:04:08.270 --> 00:04:08.280 align:start position:0% different and the data itself we wanted 00:04:08.280 --> 00:04:11.390 align:start position:0% different and the data itself we wanted the<00:04:09.000> data<00:04:09.420> to<00:04:09.659> be<00:04:09.780> the<00:04:09.959> interface<00:04:10.500> and<00:04:11.220> we 00:04:11.390 --> 00:04:11.400 align:start position:0% the data to be the interface and we 00:04:11.400 --> 00:04:13.550 align:start position:0% the data to be the interface and we wanted<00:04:11.519> something<00:04:11.879> also<00:04:12.360> extremely<00:04:12.959> reliable 00:04:13.550 --> 00:04:13.560 align:start position:0% wanted something also extremely reliable 00:04:13.560 --> 00:04:16.310 align:start position:0% wanted something also extremely reliable in<00:04:14.400> the<00:04:14.640> sense<00:04:14.760> that<00:04:14.939> we<00:04:15.420> could<00:04:15.540> avoid<00:04:15.900> hitting 00:04:16.310 --> 00:04:16.320 align:start position:0% in the sense that we could avoid hitting 00:04:16.320 --> 00:04:19.069 align:start position:0% in the sense that we could avoid hitting load<00:04:16.739> balanced<00:04:17.220> nodes<00:04:17.639> that<00:04:17.880> had<00:04:18.180> all<00:04:18.540> sorts 00:04:19.069 --> 00:04:19.079 align:start position:0% load balanced nodes that had all sorts 00:04:19.079 --> 00:04:20.689 align:start position:0% load balanced nodes that had all sorts of<00:04:19.139> different<00:04:19.380> views<00:04:19.799> of<00:04:19.979> the<00:04:20.100> world<00:04:20.280> and<00:04:20.579> that 00:04:20.689 --> 00:04:20.699 align:start position:0% of different views of the world and that 00:04:20.699 --> 00:04:23.210 align:start position:0% of different views of the world and that we<00:04:20.880> need<00:04:21.000> to<00:04:21.120> have<00:04:21.239> like<00:04:21.540> client<00:04:22.139> code<00:04:22.380> to<00:04:22.680> like 00:04:23.210 --> 00:04:23.220 align:start position:0% we need to have like client code to like 00:04:23.220 --> 00:04:25.909 align:start position:0% we need to have like client code to like latency<00:04:23.940> inducing<00:04:24.540> code<00:04:24.780> to<00:04:24.960> to<00:04:25.320> resolve 00:04:25.909 --> 00:04:25.919 align:start position:0% latency inducing code to to resolve 00:04:25.919 --> 00:04:26.930 align:start position:0% latency inducing code to to resolve what's<00:04:26.100> happening<00:04:26.400> there<00:04:26.580> if<00:04:26.820> there's 00:04:26.930 --> 00:04:26.940 align:start position:0% what's happening there if there's 00:04:26.940 --> 00:04:29.090 align:start position:0% what's happening there if there's another<00:04:27.180> fourth<00:04:27.600> you<00:04:27.720> need<00:04:27.840> to<00:04:27.960> query<00:04:28.380> nodes 00:04:29.090 --> 00:04:29.100 align:start position:0% another fourth you need to query nodes 00:04:29.100 --> 00:04:31.370 align:start position:0% another fourth you need to query nodes again<00:04:29.340> and<00:04:30.120> and<00:04:30.540> you<00:04:30.840> know<00:04:30.960> for 00:04:31.370 --> 00:04:31.380 align:start position:0% again and and you know for 00:04:31.380 --> 00:04:33.170 align:start position:0% again and and you know for reorganization<00:04:32.040> heuristics<00:04:32.699> for<00:04:32.940> example 00:04:33.170 --> 00:04:33.180 align:start position:0% reorganization heuristics for example 00:04:33.180 --> 00:04:34.730 align:start position:0% reorganization heuristics for example but<00:04:33.660> also<00:04:33.900> you<00:04:34.139> know<00:04:34.199> we<00:04:34.320> wanted<00:04:34.500> something 00:04:34.730 --> 00:04:34.740 align:start position:0% but also you know we wanted something 00:04:34.740 --> 00:04:36.950 align:start position:0% but also you know we wanted something better<00:04:35.040> than<00:04:35.280> even<00:04:35.460> the<00:04:35.759> websocket<00:04:36.360> streams 00:04:36.950 --> 00:04:36.960 align:start position:0% better than even the websocket streams 00:04:36.960 --> 00:04:38.810 align:start position:0% better than even the websocket streams that<00:04:37.620> pretend<00:04:37.919> to<00:04:38.040> be<00:04:38.220> sort<00:04:38.400> of<00:04:38.520> you<00:04:38.699> know 00:04:38.810 --> 00:04:38.820 align:start position:0% that pretend to be sort of you know 00:04:38.820 --> 00:04:41.090 align:start position:0% that pretend to be sort of you know linear<00:04:39.180> uh<00:04:40.020> that<00:04:40.440> the<00:04:40.680> nodes<00:04:40.860> have 00:04:41.090 --> 00:04:41.100 align:start position:0% linear uh that the nodes have 00:04:41.100 --> 00:04:43.430 align:start position:0% linear uh that the nodes have implemented<00:04:41.580> because<00:04:41.880> when<00:04:42.840> they<00:04:43.020> would<00:04:43.199> send 00:04:43.430 --> 00:04:43.440 align:start position:0% implemented because when they would send 00:04:43.440 --> 00:04:45.770 align:start position:0% implemented because when they would send you<00:04:43.560> a<00:04:43.740> signal<00:04:44.100> that<00:04:44.699> would<00:04:45.060> say<00:04:45.240> this<00:04:45.600> block 00:04:45.770 --> 00:04:45.780 align:start position:0% you a signal that would say this block 00:04:45.780 --> 00:04:48.830 align:start position:0% you a signal that would say this block was<00:04:46.020> removed<00:04:46.500> it<00:04:47.280> can<00:04:47.460> leave<00:04:47.880> you<00:04:48.060> hang<00:04:48.300> if<00:04:48.660> if 00:04:48.830 --> 00:04:48.840 align:start position:0% was removed it can leave you hang if if 00:04:48.840 --> 00:04:50.749 align:start position:0% was removed it can leave you hang if if you<00:04:49.020> happen<00:04:49.440> to<00:04:49.620> be<00:04:49.800> disconnected<00:04:50.400> for<00:04:50.520> just 00:04:50.749 --> 00:04:50.759 align:start position:0% you happen to be disconnected for just 00:04:50.759 --> 00:04:53.150 align:start position:0% you happen to be disconnected for just half<00:04:50.940> a<00:04:51.120> second<00:04:51.300> you'd<00:04:52.020> reconnect<00:04:52.380> you'd<00:04:52.979> miss 00:04:53.150 --> 00:04:53.160 align:start position:0% half a second you'd reconnect you'd miss 00:04:53.160 --> 00:04:55.550 align:start position:0% half a second you'd reconnect you'd miss the<00:04:53.340> signal<00:04:53.639> so<00:04:54.000> the<00:04:54.360> reliability<00:04:54.900> was<00:04:55.320> not 00:04:55.550 --> 00:04:55.560 align:start position:0% the signal so the reliability was not 00:04:55.560 --> 00:04:56.930 align:start position:0% the signal so the reliability was not built<00:04:55.919> in<00:04:55.979> so<00:04:56.160> we<00:04:56.340> wanted<00:04:56.460> something<00:04:56.699> to 00:04:56.930 --> 00:04:56.940 align:start position:0% built in so we wanted something to 00:04:56.940 --> 00:04:58.730 align:start position:0% built in so we wanted something to address<00:04:57.000> that<00:04:57.300> and<00:04:57.780> above<00:04:58.139> all<00:04:58.320> we<00:04:58.620> wanted 00:04:58.730 --> 00:04:58.740 align:start position:0% address that and above all we wanted 00:04:58.740 --> 00:05:01.030 align:start position:0% address that and above all we wanted something<00:04:59.040> thing<00:04:59.520> that<00:04:59.699> is<00:04:59.880> able<00:05:00.120> to<00:05:00.240> process 00:05:01.030 --> 00:05:01.040 align:start position:0% something thing that is able to process 00:05:01.040 --> 00:05:04.670 align:start position:0% something thing that is able to process networks<00:05:02.040> in<00:05:02.580> 20<00:05:02.820> minutes<00:05:03.120> well<00:05:03.600> okay<00:05:03.900> an<00:05:04.500> hour 00:05:04.670 --> 00:05:04.680 align:start position:0% networks in 20 minutes well okay an hour 00:05:04.680 --> 00:05:07.189 align:start position:0% networks in 20 minutes well okay an hour or<00:05:04.919> two<00:05:05.100> but<00:05:05.340> you<00:05:05.639> know<00:05:05.759> never<00:05:06.240> three<00:05:06.660> weeks<00:05:07.020> or 00:05:07.189 --> 00:05:07.199 align:start position:0% or two but you know never three weeks or 00:05:07.199 --> 00:05:09.590 align:start position:0% or two but you know never three weeks or things<00:05:07.380> where<00:05:07.620> we're<00:05:07.860> waiting<00:05:08.220> linearly<00:05:08.639> and 00:05:09.590 --> 00:05:09.600 align:start position:0% things where we're waiting linearly and 00:05:09.600 --> 00:05:11.990 align:start position:0% things where we're waiting linearly and that's<00:05:09.960> still<00:05:10.199> our<00:05:10.380> goal<00:05:10.680> today<00:05:10.800> and<00:05:11.639> when<00:05:11.820> we 00:05:11.990 --> 00:05:12.000 align:start position:0% that's still our goal today and when we 00:05:12.000 --> 00:05:14.150 align:start position:0% that's still our goal today and when we say<00:05:12.180> Network<00:05:12.419> history<00:05:12.720> I<00:05:13.139> mean<00:05:13.259> executing 00:05:14.150 --> 00:05:14.160 align:start position:0% say Network history I mean executing 00:05:14.160 --> 00:05:17.030 align:start position:0% say Network history I mean executing guests<00:05:14.759> and<00:05:15.000> extracting<00:05:15.600> data<00:05:16.020> executed<00:05:16.620> into 00:05:17.030 --> 00:05:17.040 align:start position:0% guests and extracting data executed into 00:05:17.040 --> 00:05:18.830 align:start position:0% guests and extracting data executed into flat<00:05:17.460> files<00:05:17.759> that's<00:05:17.880> the<00:05:18.060> extraction<00:05:18.360> layer 00:05:18.830 --> 00:05:18.840 align:start position:0% flat files that's the extraction layer 00:05:18.840 --> 00:05:21.710 align:start position:0% flat files that's the extraction layer but<00:05:19.380> also<00:05:19.860> any<00:05:20.520> sort<00:05:20.699> of<00:05:20.820> indexing<00:05:21.240> after<00:05:21.479> the 00:05:21.710 --> 00:05:21.720 align:start position:0% but also any sort of indexing after the 00:05:21.720 --> 00:05:23.510 align:start position:0% but also any sort of indexing after the facts<00:05:22.020> we<00:05:22.199> wanted<00:05:22.380> to<00:05:22.620> be<00:05:22.800> able<00:05:22.979> to<00:05:23.220> have 00:05:23.510 --> 00:05:23.520 align:start position:0% facts we wanted to be able to have 00:05:23.520 --> 00:05:26.270 align:start position:0% facts we wanted to be able to have massive<00:05:24.360> parallelization<00:05:25.139> like<00:05:25.919> there<00:05:26.160> was 00:05:26.270 --> 00:05:26.280 align:start position:0% massive parallelization like there was 00:05:26.280 --> 00:05:28.850 align:start position:0% massive parallelization like there was no<00:05:26.460> other<00:05:26.580> way<00:05:26.820> to<00:05:27.120> have<00:05:27.300> reliable<00:05:27.960> and 00:05:28.850 --> 00:05:28.860 align:start position:0% no other way to have reliable and 00:05:28.860 --> 00:05:30.529 align:start position:0% no other way to have reliable and durable<00:05:29.460> in<00:05:29.820> performance<00:05:30.180> without 00:05:30.529 --> 00:05:30.539 align:start position:0% durable in performance without 00:05:30.539 --> 00:05:33.529 align:start position:0% durable in performance without parallelization<00:05:31.380> so<00:05:31.979> our<00:05:32.220> solution<00:05:32.520> was<00:05:32.940> the 00:05:33.529 --> 00:05:33.539 align:start position:0% parallelization so our solution was the 00:05:33.539 --> 00:05:35.629 align:start position:0% parallelization so our solution was the fire<00:05:33.780> hose<00:05:34.020> and<00:05:34.199> the<00:05:34.320> fire<00:05:34.440> host<00:05:34.740> of<00:05:34.979> all<00:05:35.400> of 00:05:35.629 --> 00:05:35.639 align:start position:0% fire hose and the fire host of all of 00:05:35.639 --> 00:05:38.930 align:start position:0% fire hose and the fire host of all of these<00:05:36.120> issues<00:05:36.479> in<00:05:37.139> a<00:05:37.259> radical<00:05:37.560> way<00:05:37.979> we<00:05:38.580> took<00:05:38.820> a 00:05:38.930 --> 00:05:38.940 align:start position:0% these issues in a radical way we took a 00:05:38.940 --> 00:05:40.249 align:start position:0% these issues in a radical way we took a radical<00:05:39.180> approach<00:05:39.479> because<00:05:39.660> we<00:05:39.900> wanted<00:05:40.080> to 00:05:40.249 --> 00:05:40.259 align:start position:0% radical approach because we wanted to 00:05:40.259 --> 00:05:43.430 align:start position:0% radical approach because we wanted to solve<00:05:40.560> those<00:05:40.680> problems<00:05:41.660> definitively<00:05:42.660> like 00:05:43.430 --> 00:05:43.440 align:start position:0% solve those problems definitively like 00:05:43.440 --> 00:05:45.350 align:start position:0% solve those problems definitively like meaning<00:05:43.860> that<00:05:44.100> there<00:05:44.280> would<00:05:44.400> be<00:05:44.580> no<00:05:44.940> further 00:05:45.350 --> 00:05:45.360 align:start position:0% meaning that there would be no further 00:05:45.360 --> 00:05:47.930 align:start position:0% meaning that there would be no further optimization<00:05:46.020> possible<00:05:46.680> except<00:05:47.460> attempting 00:05:47.930 --> 00:05:47.940 align:start position:0% optimization possible except attempting 00:05:47.940 --> 00:05:50.090 align:start position:0% optimization possible except attempting to<00:05:48.180> bend<00:05:48.419> sort<00:05:48.660> of<00:05:48.780> space-time<00:05:49.440> Continuum 00:05:50.090 --> 00:05:50.100 align:start position:0% to bend sort of space-time Continuum 00:05:50.100 --> 00:05:53.689 align:start position:0% to bend sort of space-time Continuum itself<00:05:51.000> right<00:05:51.240> so<00:05:51.720> with<00:05:51.960> streaming<00:05:52.500> we<00:05:53.340> with 00:05:53.689 --> 00:05:53.699 align:start position:0% itself right so with streaming we with 00:05:53.699 --> 00:05:56.210 align:start position:0% itself right so with streaming we with even<00:05:54.060> multiple<00:05:54.600> nodes<00:05:54.960> pushing<00:05:55.560> out<00:05:55.740> data 00:05:56.210 --> 00:05:56.220 align:start position:0% even multiple nodes pushing out data 00:05:56.220 --> 00:05:58.490 align:start position:0% even multiple nodes pushing out data multiple<00:05:56.940> nodes<00:05:57.240> are<00:05:57.419> actually<00:05:57.600> racing<00:05:58.380> to 00:05:58.490 --> 00:05:58.500 align:start position:0% multiple nodes are actually racing to 00:05:58.500 --> 00:06:00.409 align:start position:0% multiple nodes are actually racing to push<00:05:58.680> the<00:05:58.800> data<00:05:58.979> the<00:05:59.460> first<00:05:59.820> through<00:06:00.180> a 00:06:00.409 --> 00:06:00.419 align:start position:0% push the data the first through a 00:06:00.419 --> 00:06:02.029 align:start position:0% push the data the first through a consuming<00:06:00.720> process<00:06:01.020> gets<00:06:01.440> the<00:06:01.560> first<00:06:01.680> to<00:06:01.860> get 00:06:02.029 --> 00:06:02.039 align:start position:0% consuming process gets the first to get 00:06:02.039 --> 00:06:04.550 align:start position:0% consuming process gets the first to get out<00:06:02.220> like<00:06:02.699> you<00:06:03.000> can't<00:06:03.240> really<00:06:03.539> add<00:06:04.080> remove 00:06:04.550 --> 00:06:04.560 align:start position:0% out like you can't really add remove 00:06:04.560 --> 00:06:07.550 align:start position:0% out like you can't really add remove more<00:06:04.860> latency<00:06:05.220> there<00:06:05.580> and<00:06:06.720> um<00:06:06.720> there<00:06:07.320> can<00:06:07.440> be 00:06:07.550 --> 00:06:07.560 align:start position:0% more latency there and um there can be 00:06:07.560 --> 00:06:10.249 align:start position:0% more latency there and um there can be nothing<00:06:07.740> faster<00:06:08.280> than<00:06:08.520> immediately<00:06:09.080> when<00:06:10.080> the 00:06:10.249 --> 00:06:10.259 align:start position:0% nothing faster than immediately when the 00:06:10.259 --> 00:06:12.050 align:start position:0% nothing faster than immediately when the transaction<00:06:10.560> has<00:06:10.979> just<00:06:11.220> executed<00:06:11.759> from<00:06:11.940> your 00:06:12.050 --> 00:06:12.060 align:start position:0% transaction has just executed from your 00:06:12.060 --> 00:06:14.930 align:start position:0% transaction has just executed from your node<00:06:12.360> and<00:06:12.900> then<00:06:13.080> like<00:06:13.440> regarding<00:06:13.860> the<00:06:14.100> staple 00:06:14.930 --> 00:06:14.940 align:start position:0% node and then like regarding the staple 00:06:14.940 --> 00:06:16.969 align:start position:0% node and then like regarding the staple processes<00:06:15.360> and<00:06:15.600> cost<00:06:15.840> flat<00:06:16.320> files<00:06:16.620> flat<00:06:16.860> fast 00:06:16.969 --> 00:06:16.979 align:start position:0% processes and cost flat files flat fast 00:06:16.979 --> 00:06:18.469 align:start position:0% processes and cost flat files flat fast for<00:06:17.220> the<00:06:17.340> wind<00:06:17.460> we<00:06:17.639> have<00:06:17.759> a<00:06:17.820> hashtag<00:06:18.180> for<00:06:18.360> that 00:06:18.469 --> 00:06:18.479 align:start position:0% for the wind we have a hashtag for that 00:06:18.479 --> 00:06:20.930 align:start position:0% for the wind we have a hashtag for that right<00:06:18.660> flat<00:06:19.500> files<00:06:19.740> are<00:06:19.860> the<00:06:20.039> cheapest<00:06:20.400> much 00:06:20.930 --> 00:06:20.940 align:start position:0% right flat files are the cheapest much 00:06:20.940 --> 00:06:23.150 align:start position:0% right flat files are the cheapest much cheaper<00:06:21.300> than<00:06:21.479> processes<00:06:22.080> they're<00:06:22.620> easier<00:06:22.919> to 00:06:23.150 --> 00:06:23.160 align:start position:0% cheaper than processes they're easier to 00:06:23.160 --> 00:06:25.249 align:start position:0% cheaper than processes they're easier to work<00:06:23.280> with<00:06:23.460> there's<00:06:24.180> nothing<00:06:24.360> simpler<00:06:24.960> nor 00:06:25.249 --> 00:06:25.259 align:start position:0% work with there's nothing simpler nor 00:06:25.259 --> 00:06:26.809 align:start position:0% work with there's nothing simpler nor cheaper<00:06:25.620> in<00:06:25.740> terms<00:06:25.860> of<00:06:25.979> computing<00:06:26.340> resources 00:06:26.809 --> 00:06:26.819 align:start position:0% cheaper in terms of computing resources 00:06:26.819 --> 00:06:28.670 align:start position:0% cheaper in terms of computing resources these<00:06:27.240> storage<00:06:27.720> facilities<00:06:28.319> have<00:06:28.560> been 00:06:28.670 --> 00:06:28.680 align:start position:0% these storage facilities have been 00:06:28.680 --> 00:06:31.010 align:start position:0% these storage facilities have been optimized<00:06:29.100> like<00:06:29.280> crazy<00:06:29.580> and<00:06:30.360> it's<00:06:30.600> also<00:06:30.840> where 00:06:31.010 --> 00:06:31.020 align:start position:0% optimized like crazy and it's also where 00:06:31.020 --> 00:06:33.110 align:start position:0% optimized like crazy and it's also where data<00:06:31.380> science<00:06:31.440> is<00:06:31.680> headed<00:06:31.979> these<00:06:32.220> days<00:06:32.340> and 00:06:33.110 --> 00:06:33.120 align:start position:0% data science is headed these days and 00:06:33.120 --> 00:06:35.510 align:start position:0% data science is headed these days and there's<00:06:33.360> one<00:06:33.780> common<00:06:34.020> thing<00:06:34.440> to<00:06:35.280> every 00:06:35.510 --> 00:06:35.520 align:start position:0% there's one common thing to every 00:06:35.520 --> 00:06:37.189 align:start position:0% there's one common thing to every blockchain<00:06:35.940> protocol<00:06:36.360> and<00:06:36.720> that<00:06:36.960> it 00:06:37.189 --> 00:06:37.199 align:start position:0% blockchain protocol and that it 00:06:37.199 --> 00:06:40.730 align:start position:0% blockchain protocol and that it processes<00:06:37.940> data<00:06:38.960> data<00:06:39.960> is<00:06:40.080> also<00:06:40.319> the<00:06:40.560> right 00:06:40.730 --> 00:06:40.740 align:start position:0% processes data data is also the right 00:06:40.740 --> 00:06:43.010 align:start position:0% processes data data is also the right abstraction<00:06:41.340> for<00:06:41.639> this<00:06:41.880> technology<00:06:42.300> not<00:06:42.840> an 00:06:43.010 --> 00:06:43.020 align:start position:0% abstraction for this technology not an 00:06:43.020 --> 00:06:45.650 align:start position:0% abstraction for this technology not an API<00:06:43.380> that's<00:06:43.620> common<00:06:43.800> to<00:06:44.039> all<00:06:44.160> chain<00:06:44.419> data<00:06:45.419> so 00:06:45.650 --> 00:06:45.660 align:start position:0% API that's common to all chain data so 00:06:45.660 --> 00:06:47.529 align:start position:0% API that's common to all chain data so fire<00:06:46.020> hose<00:06:46.319> clearly<00:06:46.860> delineates 00:06:47.529 --> 00:06:47.539 align:start position:0% fire hose clearly delineates 00:06:47.539 --> 00:06:50.090 align:start position:0% fire hose clearly delineates responsibilities<00:06:48.539> and<00:06:49.500> and<00:06:49.680> the<00:06:49.860> contract 00:06:50.090 --> 00:06:50.100 align:start position:0% responsibilities and and the contract 00:06:50.100 --> 00:06:51.350 align:start position:0% responsibilities and and the contract between<00:06:50.340> the<00:06:50.639> extraction<00:06:51.060> and 00:06:51.350 --> 00:06:51.360 align:start position:0% between the extraction and 00:06:51.360 --> 00:06:53.930 align:start position:0% between the extraction and transformation<00:06:51.720> layers<00:06:52.319> is<00:06:52.979> again<00:06:53.160> the<00:06:53.520> data 00:06:53.930 --> 00:06:53.940 align:start position:0% transformation layers is again the data 00:06:53.940 --> 00:06:56.870 align:start position:0% transformation layers is again the data model<00:06:54.060> fire<00:06:54.660> hose<00:06:54.960> creates<00:06:55.860> and<00:06:56.340> for<00:06:56.759> every 00:06:56.870 --> 00:06:56.880 align:start position:0% model fire hose creates and for every 00:06:56.880 --> 00:07:00.230 align:start position:0% model fire hose creates and for every chain<00:06:57.060> you<00:06:57.300> can<00:06:57.419> imagine<00:06:57.720> the<00:06:58.919> best<00:06:59.699> data 00:07:00.230 --> 00:07:00.240 align:start position:0% chain you can imagine the best data 00:07:00.240 --> 00:07:02.150 align:start position:0% chain you can imagine the best data model<00:07:00.360> the<00:07:00.960> most<00:07:01.080> complete<00:07:01.560> and<00:07:01.919> that's<00:07:02.039> what 00:07:02.150 --> 00:07:02.160 align:start position:0% model the most complete and that's what 00:07:02.160 --> 00:07:04.370 align:start position:0% model the most complete and that's what he<00:07:02.340> done<00:07:02.520> for<00:07:02.699> fire<00:07:02.819> for<00:07:03.479> for<00:07:03.660> ethereum<00:07:04.139> for 00:07:04.370 --> 00:07:04.380 align:start position:0% he done for fire for for ethereum for 00:07:04.380 --> 00:07:06.950 align:start position:0% he done for fire for for ethereum for example<00:07:04.620> that<00:07:05.580> both<00:07:05.759> the<00:07:06.120> the<00:07:06.240> data<00:07:06.600> model<00:07:06.660> for 00:07:06.950 --> 00:07:06.960 align:start position:0% example that both the the data model for 00:07:06.960 --> 00:07:09.230 align:start position:0% example that both the the data model for ethereum<00:07:07.440> within<00:07:07.919> fire<00:07:08.100> hose<00:07:08.400> is<00:07:08.819> the<00:07:09.000> richest 00:07:09.230 --> 00:07:09.240 align:start position:0% ethereum within fire hose is the richest 00:07:09.240 --> 00:07:11.390 align:start position:0% ethereum within fire hose is the richest there<00:07:09.479> is<00:07:09.660> like<00:07:10.199> you<00:07:10.380> have<00:07:10.560> in<00:07:10.680> there<00:07:10.860> the<00:07:11.100> full 00:07:11.390 --> 00:07:11.400 align:start position:0% there is like you have in there the full 00:07:11.400 --> 00:07:13.909 align:start position:0% there is like you have in there the full call<00:07:11.759> tree<00:07:12.180> internal<00:07:12.960> transactions<00:07:13.560> you<00:07:13.740> have 00:07:13.909 --> 00:07:13.919 align:start position:0% call tree internal transactions you have 00:07:13.919 --> 00:07:16.129 align:start position:0% call tree internal transactions you have the<00:07:14.039> inputs<00:07:14.400> and<00:07:14.460> outputs<00:07:14.940> as<00:07:15.060> raw<00:07:15.360> bytes<00:07:15.780> you 00:07:16.129 --> 00:07:16.139 align:start position:0% the inputs and outputs as raw bytes you 00:07:16.139 --> 00:07:17.809 align:start position:0% the inputs and outputs as raw bytes you have<00:07:16.319> the<00:07:16.500> logs<00:07:16.800> obviously<00:07:17.220> you<00:07:17.400> have<00:07:17.580> the 00:07:17.809 --> 00:07:17.819 align:start position:0% have the logs obviously you have the 00:07:17.819 --> 00:07:20.089 align:start position:0% have the logs obviously you have the state<00:07:18.060> changes<00:07:18.600> like<00:07:19.139> you<00:07:19.259> see<00:07:19.380> on<00:07:19.500> etherscan 00:07:20.089 --> 00:07:20.099 align:start position:0% state changes like you see on etherscan 00:07:20.099 --> 00:07:23.150 align:start position:0% state changes like you see on etherscan down<00:07:20.639> to<00:07:20.819> the<00:07:21.440> internal<00:07:22.440> transaction<00:07:22.919> level 00:07:23.150 --> 00:07:23.160 align:start position:0% down to the internal transaction level 00:07:23.160 --> 00:07:25.070 align:start position:0% down to the internal transaction level you<00:07:23.460> have<00:07:23.639> balance<00:07:24.120> changes<00:07:24.539> the<00:07:24.780> same<00:07:24.900> way 00:07:25.070 --> 00:07:25.080 align:start position:0% you have balance changes the same way 00:07:25.080 --> 00:07:27.350 align:start position:0% you have balance changes the same way with<00:07:25.560> the<00:07:25.800> prior<00:07:26.099> value<00:07:26.400> and<00:07:26.759> the<00:07:26.940> next<00:07:27.120> value 00:07:27.350 --> 00:07:27.360 align:start position:0% with the prior value and the next value 00:07:27.360 --> 00:07:29.390 align:start position:0% with the prior value and the next value so<00:07:27.840> when<00:07:28.020> you're<00:07:28.139> doing<00:07:28.380> like<00:07:28.860> navigation 00:07:29.390 --> 00:07:29.400 align:start position:0% so when you're doing like navigation 00:07:29.400 --> 00:07:31.550 align:start position:0% so when you're doing like navigation backwards<00:07:29.940> or<00:07:30.060> forward<00:07:30.240> you<00:07:30.900> get<00:07:31.080> you<00:07:31.380> have 00:07:31.550 --> 00:07:31.560 align:start position:0% backwards or forward you get you have 00:07:31.560 --> 00:07:33.650 align:start position:0% backwards or forward you get you have the<00:07:31.740> data<00:07:32.039> you<00:07:32.160> need<00:07:32.340> you<00:07:32.940> have<00:07:33.060> also<00:07:33.360> gas 00:07:33.650 --> 00:07:33.660 align:start position:0% the data you need you have also gas 00:07:33.660 --> 00:07:35.450 align:start position:0% the data you need you have also gas costs<00:07:34.080> at<00:07:34.259> different<00:07:34.380> places<00:07:34.680> and<00:07:35.280> there's 00:07:35.450 --> 00:07:35.460 align:start position:0% costs at different places and there's 00:07:35.460 --> 00:07:37.670 align:start position:0% costs at different places and there's that<00:07:35.639> important<00:07:36.000> notion<00:07:36.360> of<00:07:36.599> total<00:07:37.199> ordering 00:07:37.670 --> 00:07:37.680 align:start position:0% that important notion of total ordering 00:07:37.680 --> 00:07:39.469 align:start position:0% that important notion of total ordering between<00:07:37.919> things<00:07:38.280> happening<00:07:38.580> within<00:07:38.940> the<00:07:39.120> logs 00:07:39.469 --> 00:07:39.479 align:start position:0% between things happening within the logs 00:07:39.479 --> 00:07:41.990 align:start position:0% between things happening within the logs State<00:07:39.780> changes<00:07:40.259> and<00:07:40.440> calls<00:07:40.800> all<00:07:41.639> of<00:07:41.759> these 00:07:41.990 --> 00:07:42.000 align:start position:0% State changes and calls all of these 00:07:42.000 --> 00:07:43.670 align:start position:0% State changes and calls all of these things<00:07:42.120> happening<00:07:42.539> during<00:07:42.840> execution<00:07:43.380> are 00:07:43.670 --> 00:07:43.680 align:start position:0% things happening during execution are 00:07:43.680 --> 00:07:45.469 align:start position:0% things happening during execution are totally<00:07:44.160> ordered<00:07:44.520> so<00:07:44.880> you<00:07:45.000> get<00:07:45.120> in<00:07:45.240> there 00:07:45.469 --> 00:07:45.479 align:start position:0% totally ordered so you get in there 00:07:45.479 --> 00:07:47.510 align:start position:0% totally ordered so you get in there everything<00:07:46.020> parity<00:07:46.560> traces<00:07:47.039> would<00:07:47.220> give<00:07:47.400> you 00:07:47.510 --> 00:07:47.520 align:start position:0% everything parity traces would give you 00:07:47.520 --> 00:07:49.850 align:start position:0% everything parity traces would give you and<00:07:48.120> more<00:07:48.360> and<00:07:48.960> everything<00:07:49.199> you<00:07:49.440> would<00:07:49.620> need 00:07:49.850 --> 00:07:49.860 align:start position:0% and more and everything you would need 00:07:49.860 --> 00:07:52.969 align:start position:0% and more and everything you would need to<00:07:50.220> rebuild<00:07:50.699> a<00:07:51.419> full<00:07:51.539> archive<00:07:51.960> node<00:07:52.319> from<00:07:52.620> Flat 00:07:52.969 --> 00:07:52.979 align:start position:0% to rebuild a full archive node from Flat 00:07:52.979 --> 00:07:55.189 align:start position:0% to rebuild a full archive node from Flat files<00:07:53.400> and<00:07:53.880> everything<00:07:54.060> there<00:07:54.360> is<00:07:54.660> goes<00:07:55.080> to 00:07:55.189 --> 00:07:55.199 align:start position:0% files and everything there is goes to 00:07:55.199 --> 00:07:58.070 align:start position:0% files and everything there is goes to the<00:07:55.440> transaction<00:07:55.860> level<00:07:56.280> not<00:07:57.240> rounded<00:07:57.780> at<00:07:57.960> the 00:07:58.070 --> 00:07:58.080 align:start position:0% the transaction level not rounded at the 00:07:58.080 --> 00:07:59.990 align:start position:0% the transaction level not rounded at the Block<00:07:58.199> Level<00:07:58.500> which<00:07:58.919> is<00:07:59.099> crucial<00:07:59.520> if<00:07:59.759> you<00:07:59.880> want 00:07:59.990 --> 00:08:00.000 align:start position:0% Block Level which is crucial if you want 00:08:00.000 --> 00:08:02.330 align:start position:0% Block Level which is crucial if you want to<00:08:00.120> index<00:08:00.360> with<00:08:00.539> Precision<00:08:01.080> right<00:08:01.680> it<00:08:02.160> doesn't 00:08:02.330 --> 00:08:02.340 align:start position:0% to index with Precision right it doesn't 00:08:02.340 --> 00:08:04.670 align:start position:0% to index with Precision right it doesn't rounding<00:08:03.120> of<00:08:03.240> blockchain<00:08:03.720> information<00:08:04.199> at 00:08:04.670 --> 00:08:04.680 align:start position:0% rounding of blockchain information at 00:08:04.680 --> 00:08:08.029 align:start position:0% rounding of blockchain information at the<00:08:04.860> Block<00:08:04.979> Level<00:08:05.280> is<00:08:06.060> sort<00:08:06.240> of<00:08:06.360> a<00:08:06.479> was<00:08:07.039> meant 00:08:08.029 --> 00:08:08.039 align:start position:0% the Block Level is sort of a was meant 00:08:08.039 --> 00:08:10.249 align:start position:0% the Block Level is sort of a was meant for<00:08:08.160> helping<00:08:08.759> in<00:08:08.880> consensus<00:08:09.539> right<00:08:10.020> but<00:08:10.139> it 00:08:10.249 --> 00:08:10.259 align:start position:0% for helping in consensus right but it 00:08:10.259 --> 00:08:11.809 align:start position:0% for helping in consensus right but it doesn't<00:08:10.380> mean<00:08:10.560> that<00:08:10.740> what<00:08:11.099> happens<00:08:11.220> mid<00:08:11.580> block 00:08:11.809 --> 00:08:11.819 align:start position:0% doesn't mean that what happens mid block 00:08:11.819 --> 00:08:13.550 align:start position:0% doesn't mean that what happens mid block is<00:08:12.060> of<00:08:12.180> less<00:08:12.419> value<00:08:12.660> than<00:08:12.960> what<00:08:13.139> happens<00:08:13.259> at 00:08:13.550 --> 00:08:13.560 align:start position:0% is of less value than what happens at 00:08:13.560 --> 00:08:16.730 align:start position:0% is of less value than what happens at the<00:08:13.740> boundaries<00:08:14.220> so<00:08:15.120> okay<00:08:15.840> so<00:08:16.380> that's<00:08:16.560> very 00:08:16.730 --> 00:08:16.740 align:start position:0% the boundaries so okay so that's very 00:08:16.740 --> 00:08:17.870 align:start position:0% the boundaries so okay so that's very interesting<00:08:17.099> and<00:08:17.220> now<00:08:17.400> regarding 00:08:17.870 --> 00:08:17.880 align:start position:0% interesting and now regarding 00:08:17.880 --> 00:08:20.270 align:start position:0% interesting and now regarding reliability<00:08:18.479> whoops<00:08:19.259> no<00:08:19.620> not<00:08:19.860> too<00:08:20.039> fast 00:08:20.270 --> 00:08:20.280 align:start position:0% reliability whoops no not too fast 00:08:20.280 --> 00:08:23.570 align:start position:0% reliability whoops no not too fast regarding<00:08:21.240> reliability<00:08:21.780> the<00:08:22.620> fire<00:08:22.740> hose<00:08:23.039> erpc 00:08:23.570 --> 00:08:23.580 align:start position:0% regarding reliability the fire hose erpc 00:08:23.580 --> 00:08:27.110 align:start position:0% regarding reliability the fire hose erpc stream<00:08:23.759> provides<00:08:24.620> reorg<00:08:25.620> messages<00:08:25.860> like<00:08:26.639> new 00:08:27.110 --> 00:08:27.120 align:start position:0% stream provides reorg messages like new 00:08:27.120 --> 00:08:29.330 align:start position:0% stream provides reorg messages like new block<00:08:27.360> or<00:08:27.780> undo<00:08:28.199> this<00:08:28.440> block<00:08:28.620> or<00:08:28.919> this<00:08:29.160> block 00:08:29.330 --> 00:08:29.340 align:start position:0% block or undo this block or this block 00:08:29.340 --> 00:08:32.510 align:start position:0% block or undo this block or this block is<00:08:29.580> now<00:08:29.759> final<00:08:30.500> accompanied<00:08:31.500> by<00:08:31.800> a<00:08:32.159> precious 00:08:32.510 --> 00:08:32.520 align:start position:0% is now final accompanied by a precious 00:08:32.520 --> 00:08:34.850 align:start position:0% is now final accompanied by a precious cursor<00:08:33.300> I<00:08:33.659> think<00:08:33.839> that's<00:08:34.020> really<00:08:34.380> key<00:08:34.680> here 00:08:34.850 --> 00:08:34.860 align:start position:0% cursor I think that's really key here 00:08:34.860 --> 00:08:37.370 align:start position:0% cursor I think that's really key here with<00:08:35.700> each<00:08:35.940> message<00:08:36.240> so<00:08:36.839> if<00:08:37.080> you<00:08:37.200> get 00:08:37.370 --> 00:08:37.380 align:start position:0% with each message so if you get 00:08:37.380 --> 00:08:39.709 align:start position:0% with each message so if you get disconnected<00:08:38.099> and<00:08:38.700> upon<00:08:39.120> reconnection<00:08:39.539> you 00:08:39.709 --> 00:08:39.719 align:start position:0% disconnected and upon reconnection you 00:08:39.719 --> 00:08:41.690 align:start position:0% disconnected and upon reconnection you give<00:08:39.899> back<00:08:40.140> that<00:08:40.380> cursor<00:08:40.860> you'll<00:08:41.520> continue 00:08:41.690 --> 00:08:41.700 align:start position:0% give back that cursor you'll continue 00:08:41.700 --> 00:08:43.790 align:start position:0% give back that cursor you'll continue exactly<00:08:42.419> where<00:08:42.599> you<00:08:42.779> left<00:08:42.959> off<00:08:43.200> and 00:08:43.790 --> 00:08:43.800 align:start position:0% exactly where you left off and 00:08:43.800 --> 00:08:45.410 align:start position:0% exactly where you left off and potentially<00:08:44.279> receiving<00:08:44.640> that<00:08:44.880> undo<00:08:45.240> say 00:08:45.410 --> 00:08:45.420 align:start position:0% potentially receiving that undo say 00:08:45.420 --> 00:08:47.990 align:start position:0% potentially receiving that undo say signal<00:08:45.959> that<00:08:46.320> you<00:08:46.680> would<00:08:46.860> not<00:08:47.100> have<00:08:47.399> seen<00:08:47.640> were 00:08:47.990 --> 00:08:48.000 align:start position:0% signal that you would not have seen were 00:08:48.000 --> 00:08:49.910 align:start position:0% signal that you would not have seen were you<00:08:48.180> disconnected<00:08:48.360> right<00:08:48.899> so<00:08:49.380> you<00:08:49.560> will<00:08:49.740> get 00:08:49.910 --> 00:08:49.920 align:start position:0% you disconnected right so you will get 00:08:49.920 --> 00:08:51.949 align:start position:0% you disconnected right so you will get it<00:08:50.040> so<00:08:50.279> with<00:08:50.459> the<00:08:50.640> guarantees<00:08:51.120> or<00:08:51.300> linearity 00:08:51.949 --> 00:08:51.959 align:start position:0% it so with the guarantees or linearity 00:08:51.959 --> 00:08:54.949 align:start position:0% it so with the guarantees or linearity of<00:08:52.860> the<00:08:53.040> stream<00:08:53.220> so<00:08:54.120> no<00:08:54.300> websocket 00:08:54.949 --> 00:08:54.959 align:start position:0% of the stream so no websocket 00:08:54.959 --> 00:08:56.509 align:start position:0% of the stream so no websocket implementation<00:08:55.380> would<00:08:55.920> do<00:08:56.100> that<00:08:56.160> because<00:08:56.339> it 00:08:56.509 --> 00:08:56.519 align:start position:0% implementation would do that because it 00:08:56.519 --> 00:08:58.610 align:start position:0% implementation would do that because it doesn't<00:08:56.940> make<00:08:57.180> sense<00:08:57.300> for<00:08:57.540> a<00:08:57.779> single<00:08:58.080> node<00:08:58.380> to 00:08:58.610 --> 00:08:58.620 align:start position:0% doesn't make sense for a single node to 00:08:58.620 --> 00:09:00.470 align:start position:0% doesn't make sense for a single node to track<00:08:58.920> all<00:08:59.220> the<00:08:59.399> force<00:08:59.700> possible<00:09:00.000> even<00:09:00.180> two 00:09:00.470 --> 00:09:00.480 align:start position:0% track all the force possible even two 00:09:00.480 --> 00:09:02.990 align:start position:0% track all the force possible even two days<00:09:00.660> after<00:09:00.959> the<00:09:01.260> fact<00:09:01.459> and<00:09:02.459> undue<00:09:02.820> messages 00:09:02.990 --> 00:09:03.000 align:start position:0% days after the fact and undue messages 00:09:03.000 --> 00:09:05.990 align:start position:0% days after the fact and undue messages come<00:09:03.540> with<00:09:03.839> full<00:09:04.260> payloads<00:09:05.040> so<00:09:05.519> you<00:09:05.700> get<00:09:05.820> all 00:09:05.990 --> 00:09:06.000 align:start position:0% come with full payloads so you get all 00:09:06.000 --> 00:09:07.610 align:start position:0% come with full payloads so you get all the<00:09:06.180> Delta<00:09:06.540> so<00:09:06.779> you<00:09:06.899> can<00:09:06.959> just<00:09:07.080> turn<00:09:07.260> around<00:09:07.380> to 00:09:07.610 --> 00:09:07.620 align:start position:0% the Delta so you can just turn around to 00:09:07.620 --> 00:09:09.650 align:start position:0% the Delta so you can just turn around to your<00:09:07.680> database<00:09:07.980> and<00:09:08.160> apply<00:09:08.459> the<00:09:08.580> reverse<00:09:09.000> or 00:09:09.650 --> 00:09:09.660 align:start position:0% your database and apply the reverse or 00:09:09.660 --> 00:09:12.410 align:start position:0% your database and apply the reverse or you<00:09:09.779> know<00:09:09.959> pluck<00:09:10.800> again<00:09:11.160> in<00:09:11.580> the<00:09:11.700> the<00:09:11.940> full 00:09:12.410 --> 00:09:12.420 align:start position:0% you know pluck again in the the full 00:09:12.420 --> 00:09:13.730 align:start position:0% you know pluck again in the the full payload<00:09:12.899> of<00:09:13.019> what<00:09:13.140> happened<00:09:13.260> in<00:09:13.500> the<00:09:13.620> block 00:09:13.730 --> 00:09:13.740 align:start position:0% payload of what happened in the block 00:09:13.740 --> 00:09:16.130 align:start position:0% payload of what happened in the block and<00:09:14.519> just<00:09:14.640> like<00:09:14.880> what<00:09:15.060> you<00:09:15.120> do<00:09:15.240> is<00:09:15.420> so<00:09:15.959> it 00:09:16.130 --> 00:09:16.140 align:start position:0% and just like what you do is so it 00:09:16.140 --> 00:09:18.110 align:start position:0% and just like what you do is so it doesn't<00:09:16.260> pose<00:09:16.560> on<00:09:16.680> the<00:09:16.860> reader<00:09:17.160> to<00:09:17.519> store<00:09:17.820> what 00:09:18.110 --> 00:09:18.120 align:start position:0% doesn't pose on the reader to store what 00:09:18.120 --> 00:09:20.150 align:start position:0% doesn't pose on the reader to store what happened<00:09:18.360> like<00:09:19.080> at<00:09:19.320> that<00:09:19.500> previous<00:09:19.620> block<00:09:19.920> if 00:09:20.150 --> 00:09:20.160 align:start position:0% happened like at that previous block if 00:09:20.160 --> 00:09:22.310 align:start position:0% happened like at that previous block if the<00:09:20.339> signal<00:09:20.640> was<00:09:20.820> just<00:09:21.000> remove<00:09:21.240> block<00:09:21.600> 7000 00:09:22.310 --> 00:09:22.320 align:start position:0% the signal was just remove block 7000 00:09:22.320 --> 00:09:24.590 align:start position:0% the signal was just remove block 7000 right<00:09:22.560> okay<00:09:23.220> and<00:09:23.760> when<00:09:23.940> you<00:09:24.060> commit<00:09:24.360> that 00:09:24.590 --> 00:09:24.600 align:start position:0% right okay and when you commit that 00:09:24.600 --> 00:09:26.690 align:start position:0% right okay and when you commit that cursor<00:09:24.959> to<00:09:25.200> your<00:09:25.380> transfer<00:09:25.800> database<00:09:26.279> well 00:09:26.690 --> 00:09:26.700 align:start position:0% cursor to your transfer database well 00:09:26.700 --> 00:09:28.970 align:start position:0% cursor to your transfer database well you<00:09:26.880> get<00:09:27.060> through<00:09:27.240> that<00:09:27.480> you<00:09:28.260> know<00:09:28.500> finally 00:09:28.970 --> 00:09:28.980 align:start position:0% you get through that you know finally 00:09:28.980 --> 00:09:32.509 align:start position:0% you get through that you know finally some<00:09:29.339> consistency<00:09:29.940> guarantees<00:09:30.839> within<00:09:31.740> your 00:09:32.509 --> 00:09:32.519 align:start position:0% some consistency guarantees within your 00:09:32.519 --> 00:09:34.790 align:start position:0% some consistency guarantees within your you<00:09:32.820> know<00:09:32.940> your<00:09:33.240> your<00:09:33.540> back<00:09:33.779> end<00:09:33.899> so<00:09:34.440> some<00:09:34.680> of 00:09:34.790 --> 00:09:34.800 align:start position:0% you know your your back end so some of 00:09:34.800 --> 00:09:37.130 align:start position:0% you know your your back end so some of our<00:09:34.860> users<00:09:35.160> told<00:09:35.459> us<00:09:35.640> they<00:09:36.000> could<00:09:36.180> cut<00:09:36.480> ninety 00:09:37.130 --> 00:09:37.140 align:start position:0% our users told us they could cut ninety 00:09:37.140 --> 00:09:39.590 align:start position:0% our users told us they could cut ninety percent<00:09:37.260> nine<00:09:37.800> zero<00:09:38.100> of<00:09:38.519> their<00:09:38.700> code<00:09:38.940> reading 00:09:39.590 --> 00:09:39.600 align:start position:0% percent nine zero of their code reading 00:09:39.600 --> 00:09:41.630 align:start position:0% percent nine zero of their code reading the<00:09:39.779> chain<00:09:39.959> because<00:09:40.680> they<00:09:40.980> were<00:09:41.100> relying<00:09:41.459> on 00:09:41.630 --> 00:09:41.640 align:start position:0% the chain because they were relying on 00:09:41.640 --> 00:09:44.810 align:start position:0% the chain because they were relying on some<00:09:42.060> that<00:09:42.720> reliable<00:09:43.140> stream<00:09:43.920> and<00:09:44.339> okay<00:09:44.519> and 00:09:44.810 --> 00:09:44.820 align:start position:0% some that reliable stream and okay and 00:09:44.820 --> 00:09:47.090 align:start position:0% some that reliable stream and okay and it<00:09:44.940> also<00:09:45.240> lays<00:09:45.600> lies<00:09:46.380> down<00:09:46.500> the<00:09:46.740> foundation 00:09:47.090 --> 00:09:47.100 align:start position:0% it also lays lies down the foundation 00:09:47.100 --> 00:09:49.910 align:start position:0% it also lays lies down the foundation for<00:09:47.459> massively<00:09:47.940> paralyzed<00:09:48.480> operation<00:09:48.920> files 00:09:49.910 --> 00:09:49.920 align:start position:0% for massively paralyzed operation files 00:09:49.920 --> 00:09:52.430 align:start position:0% for massively paralyzed operation files plus<00:09:50.160> the<00:09:50.459> stream<00:09:50.700> and<00:09:51.660> so<00:09:51.959> this<00:09:52.140> is<00:09:52.260> the 00:09:52.430 --> 00:09:52.440 align:start position:0% plus the stream and so this is the 00:09:52.440 --> 00:09:55.009 align:start position:0% plus the stream and so this is the future<00:09:52.760> of<00:09:53.760> the<00:09:53.940> graph<00:09:54.300> unbeatable 00:09:55.009 --> 00:09:55.019 align:start position:0% future of the graph unbeatable 00:09:55.019 --> 00:09:57.110 align:start position:0% future of the graph unbeatable performance<00:09:55.620> and<00:09:56.339> it's<00:09:56.459> core<00:09:56.700> to<00:09:56.940> our 00:09:57.110 --> 00:09:57.120 align:start position:0% performance and it's core to our 00:09:57.120 --> 00:09:59.449 align:start position:0% performance and it's core to our multi-chain<00:09:57.720> strategy<00:09:58.200> because<00:09:58.500> you<00:09:59.339> know 00:09:59.449 --> 00:09:59.459 align:start position:0% multi-chain strategy because you know 00:09:59.459 --> 00:10:03.769 align:start position:0% multi-chain strategy because you know any<00:10:00.120> blockchain<00:10:00.660> can<00:10:01.380> have<00:10:01.620> that<00:10:01.980> data<00:10:02.519> model 00:10:03.769 --> 00:10:03.779 align:start position:0% any blockchain can have that data model 00:10:03.779 --> 00:10:06.110 align:start position:0% any blockchain can have that data model uh<00:10:04.320> now<00:10:04.500> let's<00:10:04.680> dig<00:10:04.860> into<00:10:04.980> sub<00:10:05.279> streams 00:10:06.110 --> 00:10:06.120 align:start position:0% uh now let's dig into sub streams 00:10:06.120 --> 00:10:08.750 align:start position:0% uh now let's dig into sub streams substreams<00:10:07.019> is<00:10:07.200> a<00:10:07.500> powerful<00:10:07.920> clustered 00:10:08.750 --> 00:10:08.760 align:start position:0% substreams is a powerful clustered 00:10:08.760 --> 00:10:11.449 align:start position:0% substreams is a powerful clustered engine<00:10:09.000> to<00:10:09.660> process<00:10:09.959> blockchain<00:10:10.500> data<00:10:10.980> it's<00:10:11.339> a 00:10:11.449 --> 00:10:11.459 align:start position:0% engine to process blockchain data it's a 00:10:11.459 --> 00:10:12.889 align:start position:0% engine to process blockchain data it's a streaming<00:10:11.760> first<00:10:11.940> engine<00:10:12.120> and<00:10:12.420> it's<00:10:12.600> powered 00:10:12.889 --> 00:10:12.899 align:start position:0% streaming first engine and it's powered 00:10:12.899 --> 00:10:14.990 align:start position:0% streaming first engine and it's powered by<00:10:13.019> the<00:10:13.140> fire<00:10:13.260> hose<00:10:13.500> underneath<00:10:13.800> and<00:10:14.339> its<00:10:14.700> data 00:10:14.990 --> 00:10:15.000 align:start position:0% by the fire hose underneath and its data 00:10:15.000 --> 00:10:17.269 align:start position:0% by the fire hose underneath and its data models<00:10:15.300> of<00:10:15.480> the<00:10:15.660> chain<00:10:15.779> so<00:10:16.080> let's<00:10:16.200> dig<00:10:16.380> in 00:10:17.269 --> 00:10:17.279 align:start position:0% models of the chain so let's dig in 00:10:17.279 --> 00:10:19.790 align:start position:0% models of the chain so let's dig in here<00:10:17.760> are<00:10:17.940> a<00:10:17.940> few<00:10:18.060> quick<00:10:18.240> facts<00:10:18.660> it's<00:10:19.320> invoked 00:10:19.790 --> 00:10:19.800 align:start position:0% here are a few quick facts it's invoked 00:10:19.800 --> 00:10:23.389 align:start position:0% here are a few quick facts it's invoked as<00:10:19.980> a<00:10:20.160> single<00:10:20.519> Jace<00:10:21.000> grpc<00:10:21.899> call<00:10:22.260> and<00:10:22.920> within 00:10:23.389 --> 00:10:23.399 align:start position:0% as a single Jace grpc call and within 00:10:23.399 --> 00:10:24.829 align:start position:0% as a single Jace grpc call and within the<00:10:23.519> request<00:10:23.760> we<00:10:23.940> provide<00:10:24.240> all<00:10:24.660> the 00:10:24.829 --> 00:10:24.839 align:start position:0% the request we provide all the 00:10:24.839 --> 00:10:26.810 align:start position:0% the request we provide all the transformation<00:10:25.200> code<00:10:25.740> like<00:10:26.160> you'll<00:10:26.459> have<00:10:26.640> in 00:10:26.810 --> 00:10:26.820 align:start position:0% transformation code like you'll have in 00:10:26.820 --> 00:10:28.610 align:start position:0% transformation code like you'll have in there<00:10:26.940> oh<00:10:27.180> it's<00:10:27.420> too<00:10:27.600> low<00:10:27.720> you'll<00:10:28.380> have<00:10:28.500> in 00:10:28.610 --> 00:10:28.620 align:start position:0% there oh it's too low you'll have in 00:10:28.620 --> 00:10:30.730 align:start position:0% there oh it's too low you'll have in there<00:10:28.740> the<00:10:29.100> code<00:10:29.339> from<00:10:29.580> some<00:10:29.820> wasm<00:10:30.300> modules 00:10:30.730 --> 00:10:30.740 align:start position:0% there the code from some wasm modules 00:10:30.740 --> 00:10:33.350 align:start position:0% there the code from some wasm modules relationships<00:10:31.740> within<00:10:32.040> the<00:10:32.160> modules<00:10:32.519> and<00:10:33.180> uh 00:10:33.350 --> 00:10:33.360 align:start position:0% relationships within the modules and uh 00:10:33.360 --> 00:10:34.910 align:start position:0% relationships within the modules and uh you<00:10:33.540> know<00:10:33.660> all<00:10:33.839> the<00:10:34.019> transaction<00:10:34.380> the 00:10:34.910 --> 00:10:34.920 align:start position:0% you know all the transaction the 00:10:34.920 --> 00:10:37.009 align:start position:0% you know all the transaction the Transformations<00:10:35.580> within<00:10:36.180> the<00:10:36.300> request<00:10:36.540> it's 00:10:37.009 --> 00:10:37.019 align:start position:0% Transformations within the request it's 00:10:37.019 --> 00:10:38.810 align:start position:0% Transformations within the request it's not<00:10:37.320> a<00:10:37.500> long<00:10:37.620> running<00:10:37.800> process<00:10:38.220> except<00:10:38.519> if<00:10:38.640> you 00:10:38.810 --> 00:10:38.820 align:start position:0% not a long running process except if you 00:10:38.820 --> 00:10:40.670 align:start position:0% not a long running process except if you run<00:10:39.000> it<00:10:39.120> for<00:10:39.180> long<00:10:39.360> it's<00:10:39.540> not<00:10:39.779> a<00:10:39.959> service<00:10:40.320> you 00:10:40.670 --> 00:10:40.680 align:start position:0% run it for long it's not a service you 00:10:40.680 --> 00:10:43.310 align:start position:0% run it for long it's not a service you you<00:10:40.860> spin<00:10:41.160> up<00:10:41.339> right<00:10:41.760> and<00:10:42.480> the<00:10:42.779> backing<00:10:43.080> nodes 00:10:43.310 --> 00:10:43.320 align:start position:0% you spin up right and the backing nodes 00:10:43.320 --> 00:10:44.930 align:start position:0% you spin up right and the backing nodes are<00:10:43.500> stateless<00:10:43.920> which<00:10:44.279> provide<00:10:44.579> nice 00:10:44.930 --> 00:10:44.940 align:start position:0% are stateless which provide nice 00:10:44.940 --> 00:10:47.690 align:start position:0% are stateless which provide nice scalability<00:10:45.600> properties<00:10:46.279> modules<00:10:47.279> for 00:10:47.690 --> 00:10:47.700 align:start position:0% scalability properties modules for 00:10:47.700 --> 00:10:49.610 align:start position:0% scalability properties modules for Transformations<00:10:48.120> are<00:10:48.420> written<00:10:48.779> in<00:10:48.899> Rust<00:10:49.200> they 00:10:49.610 --> 00:10:49.620 align:start position:0% Transformations are written in Rust they 00:10:49.620 --> 00:10:51.170 align:start position:0% Transformations are written in Rust they compile<00:10:49.860> to<00:10:50.100> wasm<00:10:50.459> and<00:10:50.640> they're<00:10:50.700> running<00:10:50.880> a 00:10:51.170 --> 00:10:51.180 align:start position:0% compile to wasm and they're running a 00:10:51.180 --> 00:10:53.449 align:start position:0% compile to wasm and they're running a secure<00:10:51.420> sandbox<00:10:52.019> on<00:10:52.620> on<00:10:52.800> the<00:10:52.980> infrastructure 00:10:53.449 --> 00:10:53.459 align:start position:0% secure sandbox on on the infrastructure 00:10:53.459 --> 00:10:55.069 align:start position:0% secure sandbox on on the infrastructure they're<00:10:53.579> similar<00:10:53.940> to<00:10:54.000> the<00:10:54.120> sub<00:10:54.240> graphs<00:10:54.660> and 00:10:55.069 --> 00:10:55.079 align:start position:0% they're similar to the sub graphs and 00:10:55.079 --> 00:10:56.630 align:start position:0% they're similar to the sub graphs and the<00:10:55.260> ultimate<00:10:55.560> data<00:10:55.860> source<00:10:56.160> being<00:10:56.339> the 00:10:56.630 --> 00:10:56.640 align:start position:0% the ultimate data source being the 00:10:56.640 --> 00:10:59.810 align:start position:0% the ultimate data source being the blockchain<00:10:57.120> data<00:10:57.660> being<00:10:58.079> deterministic<00:10:58.980> all 00:10:59.810 --> 00:10:59.820 align:start position:0% blockchain data being deterministic all 00:10:59.820 --> 00:11:01.790 align:start position:0% blockchain data being deterministic all the<00:11:00.000> transformation<00:11:00.420> outputs<00:11:01.200> are<00:11:01.380> also 00:11:01.790 --> 00:11:01.800 align:start position:0% the transformation outputs are also 00:11:01.800 --> 00:11:04.550 align:start position:0% the transformation outputs are also deterministic<00:11:02.700> and<00:11:03.600> the<00:11:03.720> request<00:11:04.079> if<00:11:04.380> the 00:11:04.550 --> 00:11:04.560 align:start position:0% deterministic and the request if the 00:11:04.560 --> 00:11:07.130 align:start position:0% deterministic and the request if the request<00:11:04.860> you<00:11:05.040> send<00:11:05.220> involves<00:11:05.760> process<00:11:06.300> prior 00:11:07.130 --> 00:11:07.140 align:start position:0% request you send involves process prior 00:11:07.140 --> 00:11:09.290 align:start position:0% request you send involves process prior history<00:11:07.440> even<00:11:07.980> if<00:11:08.220> it's<00:11:08.339> 15<00:11:08.579> million<00:11:09.000> blocks 00:11:09.290 --> 00:11:09.300 align:start position:0% history even if it's 15 million blocks 00:11:09.300 --> 00:11:10.850 align:start position:0% history even if it's 15 million blocks well<00:11:09.480> the<00:11:09.720> substream's<00:11:10.200> runtime<00:11:10.500> will<00:11:10.740> then 00:11:10.850 --> 00:11:10.860 align:start position:0% well the substream's runtime will then 00:11:10.860 --> 00:11:13.130 align:start position:0% well the substream's runtime will then turn<00:11:11.100> around<00:11:11.300> and<00:11:12.300> orchestrate<00:11:12.899> the 00:11:13.130 --> 00:11:13.140 align:start position:0% turn around and orchestrate the 00:11:13.140 --> 00:11:15.290 align:start position:0% turn around and orchestrate the execution<00:11:13.620> of<00:11:13.920> a<00:11:14.100> multitude<00:11:14.579> of<00:11:14.700> smaller<00:11:15.120> jobs 00:11:15.290 --> 00:11:15.300 align:start position:0% execution of a multitude of smaller jobs 00:11:15.300 --> 00:11:18.290 align:start position:0% execution of a multitude of smaller jobs in<00:11:16.140> parallel<00:11:16.560> fuse<00:11:17.040> the<00:11:17.220> is<00:11:17.640> lost<00:11:17.820> on<00:11:18.060> the<00:11:18.240> Fly 00:11:18.290 --> 00:11:18.300 align:start position:0% in parallel fuse the is lost on the Fly 00:11:18.300 --> 00:11:20.810 align:start position:0% in parallel fuse the is lost on the Fly for<00:11:18.600> you<00:11:18.720> and<00:11:18.959> aggregate<00:11:19.500> the<00:11:20.100> results<00:11:20.220> to 00:11:20.810 --> 00:11:20.820 align:start position:0% for you and aggregate the results to 00:11:20.820 --> 00:11:22.790 align:start position:0% for you and aggregate the results to simulate<00:11:21.240> a<00:11:21.480> linear<00:11:21.779> execution<00:11:22.320> so<00:11:22.500> you<00:11:22.680> would 00:11:22.790 --> 00:11:22.800 align:start position:0% simulate a linear execution so you would 00:11:22.800 --> 00:11:24.710 align:start position:0% simulate a linear execution so you would see<00:11:22.980> a<00:11:23.100> dime<00:11:23.279> in<00:11:23.519> the<00:11:23.700> difference<00:11:23.880> and<00:11:24.420> all<00:11:24.600> the 00:11:24.710 --> 00:11:24.720 align:start position:0% see a dime in the difference and all the 00:11:24.720 --> 00:11:26.449 align:start position:0% see a dime in the difference and all the results<00:11:24.899> are<00:11:25.200> streamed<00:11:25.680> back<00:11:25.800> to<00:11:25.980> you<00:11:26.100> as<00:11:26.279> fast 00:11:26.449 --> 00:11:26.459 align:start position:0% results are streamed back to you as fast 00:11:26.459 --> 00:11:28.009 align:start position:0% results are streamed back to you as fast as<00:11:26.700> possible<00:11:27.000> with<00:11:27.240> same<00:11:27.540> guarantees 00:11:28.009 --> 00:11:28.019 align:start position:0% as possible with same guarantees 00:11:28.019 --> 00:11:29.990 align:start position:0% as possible with same guarantees provided<00:11:28.380> by<00:11:28.560> the<00:11:28.680> fire<00:11:28.860> hose<00:11:29.160> with<00:11:29.700> a<00:11:29.880> block 00:11:29.990 --> 00:11:30.000 align:start position:0% provided by the fire hose with a block 00:11:30.000 --> 00:11:32.810 align:start position:0% provided by the fire hose with a block per<00:11:30.240> block<00:11:30.480> cursor<00:11:31.019> and<00:11:31.860> a<00:11:32.220> transparent 00:11:32.810 --> 00:11:32.820 align:start position:0% per block cursor and a transparent 00:11:32.820 --> 00:11:35.150 align:start position:0% per block cursor and a transparent handoff<00:11:33.300> from<00:11:33.600> batching<00:11:34.200> into<00:11:34.500> a<00:11:34.800> historical 00:11:35.150 --> 00:11:35.160 align:start position:0% handoff from batching into a historical 00:11:35.160 --> 00:11:37.670 align:start position:0% handoff from batching into a historical processing<00:11:35.760> to<00:11:36.360> the<00:11:36.540> real-time<00:11:36.959> low<00:11:37.260> latency 00:11:37.670 --> 00:11:37.680 align:start position:0% processing to the real-time low latency 00:11:37.680 --> 00:11:40.850 align:start position:0% processing to the real-time low latency rewards<00:11:38.279> aware<00:11:38.940> stream<00:11:39.779> of<00:11:40.140> the<00:11:40.320> head<00:11:40.500> of<00:11:40.680> the 00:11:40.850 --> 00:11:40.860 align:start position:0% rewards aware stream of the head of the 00:11:40.860 --> 00:11:43.190 align:start position:0% rewards aware stream of the head of the chain<00:11:41.040> so<00:11:41.820> let<00:11:42.060> me<00:11:42.180> show<00:11:42.360> you<00:11:42.779> if<00:11:43.019> you're 00:11:43.190 --> 00:11:43.200 align:start position:0% chain so let me show you if you're 00:11:43.200 --> 00:11:45.110 align:start position:0% chain so let me show you if you're interested<00:11:43.560> how<00:11:44.220> we<00:11:44.399> create<00:11:44.579> one<00:11:44.820> of<00:11:44.940> these 00:11:45.110 --> 00:11:45.120 align:start position:0% interested how we create one of these 00:11:45.120 --> 00:11:46.490 align:start position:0% interested how we create one of these things<00:11:45.240> raise<00:11:45.540> your<00:11:45.720> hand<00:11:45.839> if<00:11:46.019> you're<00:11:46.140> curious 00:11:46.490 --> 00:11:46.500 align:start position:0% things raise your hand if you're curious 00:11:46.500 --> 00:11:49.490 align:start position:0% things raise your hand if you're curious okay<00:11:47.279> you're<00:11:47.640> good<00:11:47.820> okay<00:11:48.480> so<00:11:48.899> let's<00:11:49.079> start<00:11:49.320> we 00:11:49.490 --> 00:11:49.500 align:start position:0% okay you're good okay so let's start we 00:11:49.500 --> 00:11:51.470 align:start position:0% okay you're good okay so let's start we start<00:11:49.680> with<00:11:49.860> a<00:11:50.100> manifest<00:11:50.579> like<00:11:51.000> that<00:11:51.180> do<00:11:51.360> you 00:11:51.470 --> 00:11:51.480 align:start position:0% start with a manifest like that do you 00:11:51.480 --> 00:11:53.750 align:start position:0% start with a manifest like that do you see<00:11:51.600> that<00:11:51.779> down<00:11:52.019> here<00:11:52.320> can<00:11:52.980> move<00:11:53.220> the<00:11:53.279> podium<00:11:53.519> I 00:11:53.750 --> 00:11:53.760 align:start position:0% see that down here can move the podium I 00:11:53.760 --> 00:11:56.389 align:start position:0% see that down here can move the podium I can't<00:11:53.959> so<00:11:54.959> there's<00:11:55.140> package<00:11:55.620> information<00:11:55.860> you 00:11:56.389 --> 00:11:56.399 align:start position:0% can't so there's package information you 00:11:56.399 --> 00:11:58.069 align:start position:0% can't so there's package information you know<00:11:56.519> some<00:11:56.820> metadata<00:11:57.300> there<00:11:57.480> you<00:11:57.899> have 00:11:58.069 --> 00:11:58.079 align:start position:0% know some metadata there you have 00:11:58.079 --> 00:12:00.050 align:start position:0% know some metadata there you have pointers<00:11:58.500> to<00:11:58.740> the<00:11:58.920> Proto<00:11:59.279> buff<00:11:59.519> that<00:11:59.880> you'll 00:12:00.050 --> 00:12:00.060 align:start position:0% pointers to the Proto buff that you'll 00:12:00.060 --> 00:12:02.449 align:start position:0% pointers to the Proto buff that you'll use<00:12:00.240> again<00:12:00.839> contracts<00:12:01.680> between<00:12:01.860> modules<00:12:02.279> are 00:12:02.449 --> 00:12:02.459 align:start position:0% use again contracts between modules are 00:12:02.459 --> 00:12:04.430 align:start position:0% use again contracts between modules are about<00:12:02.640> data<00:12:03.120> so<00:12:03.240> there<00:12:03.480> are<00:12:03.600> protobuf<00:12:04.079> models 00:12:04.430 --> 00:12:04.440 align:start position:0% about data so there are protobuf models 00:12:04.440 --> 00:12:06.290 align:start position:0% about data so there are protobuf models similar<00:12:04.920> to<00:12:05.040> the<00:12:05.160> protobuf<00:12:05.700> models<00:12:05.940> of<00:12:06.120> the 00:12:06.290 --> 00:12:06.300 align:start position:0% similar to the protobuf models of the 00:12:06.300 --> 00:12:08.090 align:start position:0% similar to the protobuf models of the root<00:12:06.540> chain<00:12:06.720> of<00:12:06.959> the<00:12:07.079> chains<00:12:07.380> the<00:12:07.560> layer<00:12:07.860> ones 00:12:08.090 --> 00:12:08.100 align:start position:0% root chain of the chains the layer ones 00:12:08.100 --> 00:12:10.069 align:start position:0% root chain of the chains the layer ones and<00:12:08.399> you<00:12:08.579> have<00:12:08.700> pointers<00:12:09.060> to<00:12:09.240> the<00:12:09.360> binary<00:12:09.720> that 00:12:10.069 --> 00:12:10.079 align:start position:0% and you have pointers to the binary that 00:12:10.079 --> 00:12:11.210 align:start position:0% and you have pointers to the binary that you're<00:12:10.200> working<00:12:10.380> on<00:12:10.560> your<00:12:10.680> drive<00:12:10.800> and<00:12:11.040> all 00:12:11.210 --> 00:12:11.220 align:start position:0% you're working on your drive and all 00:12:11.220 --> 00:12:13.069 align:start position:0% you're working on your drive and all that<00:12:11.339> and<00:12:11.640> you<00:12:11.760> have<00:12:11.940> Imports<00:12:12.480> and<00:12:12.600> imports 00:12:13.069 --> 00:12:13.079 align:start position:0% that and you have Imports and imports 00:12:13.079 --> 00:12:14.269 align:start position:0% that and you have Imports and imports are<00:12:13.200> actually<00:12:13.560> very<00:12:13.800> interesting<00:12:14.160> because 00:12:14.269 --> 00:12:14.279 align:start position:0% are actually very interesting because 00:12:14.279 --> 00:12:17.150 align:start position:0% are actually very interesting because you<00:12:14.640> can<00:12:14.700> import<00:12:15.260> third-party<00:12:16.260> substreams 00:12:17.150 --> 00:12:17.160 align:start position:0% you can import third-party substreams 00:12:17.160 --> 00:12:20.630 align:start position:0% you can import third-party substreams packages<00:12:18.000> and<00:12:18.600> these<00:12:18.839> yamo<00:12:19.800> can<00:12:19.980> be<00:12:20.100> packaged 00:12:20.630 --> 00:12:20.640 align:start position:0% packages and these yamo can be packaged 00:12:20.640 --> 00:12:22.310 align:start position:0% packages and these yamo can be packaged and<00:12:21.180> so<00:12:21.360> you<00:12:21.540> can<00:12:21.600> import<00:12:21.779> from<00:12:22.140> someone 00:12:22.310 --> 00:12:22.320 align:start position:0% and so you can import from someone 00:12:22.320 --> 00:12:24.230 align:start position:0% and so you can import from someone else's<00:12:22.680> package<00:12:23.040> you<00:12:23.160> can<00:12:23.279> write<00:12:23.459> your<00:12:23.640> own<00:12:23.820> or 00:12:24.230 --> 00:12:24.240 align:start position:0% else's package you can write your own or 00:12:24.240 --> 00:12:26.810 align:start position:0% else's package you can write your own or combine<00:12:24.660> both<00:12:25.019> that<00:12:25.800> means<00:12:26.100> substreams 00:12:26.810 --> 00:12:26.820 align:start position:0% combine both that means substreams 00:12:26.820 --> 00:12:30.170 align:start position:0% combine both that means substreams enables<00:12:27.860> composition<00:12:28.860> at<00:12:29.700> transformation 00:12:30.170 --> 00:12:30.180 align:start position:0% enables composition at transformation 00:12:30.180 --> 00:12:32.690 align:start position:0% enables composition at transformation time<00:12:30.779> which<00:12:31.380> I<00:12:31.500> think<00:12:31.620> is<00:12:31.800> pretty<00:12:31.980> unique<00:12:32.220> in<00:12:32.459> a 00:12:32.690 --> 00:12:32.700 align:start position:0% time which I think is pretty unique in a 00:12:32.700 --> 00:12:35.389 align:start position:0% time which I think is pretty unique in a pretty<00:12:32.880> Game<00:12:33.240> Changer<00:12:33.779> and<00:12:34.440> then<00:12:34.620> follow<00:12:35.220> up 00:12:35.389 --> 00:12:35.399 align:start position:0% pretty Game Changer and then follow up 00:12:35.399 --> 00:12:37.250 align:start position:0% pretty Game Changer and then follow up and<00:12:35.820> there<00:12:36.000> you<00:12:36.180> have<00:12:36.300> the<00:12:36.480> module<00:12:36.839> sections 00:12:37.250 --> 00:12:37.260 align:start position:0% and there you have the module sections 00:12:37.260 --> 00:12:39.829 align:start position:0% and there you have the module sections which<00:12:37.500> defines<00:12:38.100> the<00:12:38.640> relation<00:12:39.120> between<00:12:39.540> the 00:12:39.829 --> 00:12:39.839 align:start position:0% which defines the relation between the 00:12:39.839 --> 00:12:42.410 align:start position:0% which defines the relation between the different<00:12:39.959> modules<00:12:40.700> and<00:12:41.700> you<00:12:41.820> see<00:12:42.000> it<00:12:42.120> defines 00:12:42.410 --> 00:12:42.420 align:start position:0% different modules and you see it defines 00:12:42.420 --> 00:12:45.009 align:start position:0% different modules and you see it defines it<00:12:42.540> directed<00:12:43.200> a<00:12:43.380> cyclic<00:12:43.620> graph<00:12:44.040> you<00:12:44.459> have 00:12:45.009 --> 00:12:45.019 align:start position:0% it directed a cyclic graph you have 00:12:45.019 --> 00:12:48.710 align:start position:0% it directed a cyclic graph you have modules<00:12:46.019> that<00:12:46.260> slowly<00:12:46.620> refine<00:12:47.339> the<00:12:47.639> data<00:12:48.060> and 00:12:48.710 --> 00:12:48.720 align:start position:0% modules that slowly refine the data and 00:12:48.720 --> 00:12:51.110 align:start position:0% modules that slowly refine the data and so<00:12:48.839> there's<00:12:49.079> two<00:12:49.380> types<00:12:49.620> of<00:12:49.740> modules<00:12:50.220> one<00:12:50.820> the 00:12:51.110 --> 00:12:51.120 align:start position:0% so there's two types of modules one the 00:12:51.120 --> 00:12:53.509 align:start position:0% so there's two types of modules one the mapper<00:12:51.420> the<00:12:51.660> first<00:12:51.779> up<00:12:52.019> there<00:12:52.200> map<00:12:52.500> pools<00:12:53.040> and 00:12:53.509 --> 00:12:53.519 align:start position:0% mapper the first up there map pools and 00:12:53.519 --> 00:12:55.490 align:start position:0% mapper the first up there map pools and this<00:12:53.760> one<00:12:53.940> takes<00:12:54.720> inputs<00:12:55.200> does 00:12:55.490 --> 00:12:55.500 align:start position:0% this one takes inputs does 00:12:55.500 --> 00:12:57.650 align:start position:0% this one takes inputs does transformation<00:12:55.920> and<00:12:56.279> outputs<00:12:57.060> it's 00:12:57.650 --> 00:12:57.660 align:start position:0% transformation and outputs it's 00:12:57.660 --> 00:12:59.810 align:start position:0% transformation and outputs it's parallelizable<00:12:58.440> down<00:12:58.800> to<00:12:58.980> its<00:12:59.279> core<00:12:59.399> block 00:12:59.810 --> 00:12:59.820 align:start position:0% parallelizable down to its core block 00:12:59.820 --> 00:13:01.670 align:start position:0% parallelizable down to its core block wise<00:13:00.240> though<00:13:00.480> massively<00:13:00.899> paralyzable<00:13:01.380> and 00:13:01.670 --> 00:13:01.680 align:start position:0% wise though massively paralyzable and 00:13:01.680 --> 00:13:03.410 align:start position:0% wise though massively paralyzable and then<00:13:01.860> there's<00:13:02.040> the<00:13:02.279> store<00:13:02.639> input<00:13:03.060> I<00:13:03.300> think 00:13:03.410 --> 00:13:03.420 align:start position:0% then there's the store input I think 00:13:03.420 --> 00:13:06.710 align:start position:0% then there's the store input I think it's<00:13:03.540> awesome<00:13:04.040> this<00:13:05.040> one<00:13:05.220> takes<00:13:05.880> any<00:13:06.120> inputs 00:13:06.710 --> 00:13:06.720 align:start position:0% it's awesome this one takes any inputs 00:13:06.720 --> 00:13:10.610 align:start position:0% it's awesome this one takes any inputs and<00:13:07.200> outputs<00:13:07.800> a<00:13:08.220> key<00:13:08.459> value<00:13:08.760> store<00:13:09.320> that<00:13:10.320> or 00:13:10.610 --> 00:13:10.620 align:start position:0% and outputs a key value store that or 00:13:10.620 --> 00:13:12.530 align:start position:0% and outputs a key value store that or something<00:13:10.800> accumulated<00:13:11.399> in<00:13:11.639> a<00:13:11.820> stateful<00:13:12.240> way 00:13:12.530 --> 00:13:12.540 align:start position:0% something accumulated in a stateful way 00:13:12.540 --> 00:13:15.350 align:start position:0% something accumulated in a stateful way and<00:13:13.440> stores<00:13:13.740> can<00:13:14.220> then<00:13:14.399> be<00:13:14.639> queried<00:13:15.000> by 00:13:15.350 --> 00:13:15.360 align:start position:0% and stores can then be queried by 00:13:15.360 --> 00:13:18.410 align:start position:0% and stores can then be queried by Downstream<00:13:15.959> modules<00:13:16.459> and<00:13:17.459> uh<00:13:17.639> okay<00:13:17.940> so<00:13:18.180> we'll 00:13:18.410 --> 00:13:18.420 align:start position:0% Downstream modules and uh okay so we'll 00:13:18.420 --> 00:13:19.910 align:start position:0% Downstream modules and uh okay so we'll see<00:13:18.540> a<00:13:18.720> bit<00:13:18.899> more<00:13:19.019> after<00:13:19.139> then<00:13:19.500> the<00:13:19.800> name 00:13:19.910 --> 00:13:19.920 align:start position:0% see a bit more after then the name 00:13:19.920 --> 00:13:21.650 align:start position:0% see a bit more after then the name corresponds<00:13:20.459> to<00:13:20.519> the<00:13:20.700> function<00:13:20.940> in<00:13:21.120> the<00:13:21.300> wasm 00:13:21.650 --> 00:13:21.660 align:start position:0% corresponds to the function in the wasm 00:13:21.660 --> 00:13:24.530 align:start position:0% corresponds to the function in the wasm code<00:13:21.899> and<00:13:22.680> the<00:13:22.860> inputs<00:13:23.279> can<00:13:23.459> be<00:13:23.639> of<00:13:24.120> a<00:13:24.420> few 00:13:24.530 --> 00:13:24.540 align:start position:0% code and the inputs can be of a few 00:13:24.540 --> 00:13:27.050 align:start position:0% code and the inputs can be of a few things<00:13:24.720> either<00:13:25.079> the<00:13:25.440> raw<00:13:25.740> fire<00:13:25.980> hose<00:13:26.279> feed<00:13:26.519> so 00:13:27.050 --> 00:13:27.060 align:start position:0% things either the raw fire hose feed so 00:13:27.060 --> 00:13:28.910 align:start position:0% things either the raw fire hose feed so for<00:13:27.300> example<00:13:27.540> The<00:13:27.839> Source<00:13:28.200> here<00:13:28.320> that<00:13:28.560> means 00:13:28.910 --> 00:13:28.920 align:start position:0% for example The Source here that means 00:13:28.920 --> 00:13:31.850 align:start position:0% for example The Source here that means the<00:13:29.519> block<00:13:29.820> with<00:13:30.360> all<00:13:30.540> transactions<00:13:31.260> you<00:13:31.740> know 00:13:31.850 --> 00:13:31.860 align:start position:0% the block with all transactions you know 00:13:31.860 --> 00:13:34.009 align:start position:0% the block with all transactions you know for<00:13:32.040> for<00:13:32.220> that<00:13:32.399> particular<00:13:32.700> block<00:13:32.940> and<00:13:33.779> it<00:13:33.959> can 00:13:34.009 --> 00:13:34.019 align:start position:0% for for that particular block and it can 00:13:34.019 --> 00:13:35.509 align:start position:0% for for that particular block and it can be<00:13:34.139> the<00:13:34.260> output<00:13:34.500> of<00:13:34.680> another<00:13:34.800> module<00:13:35.220> like<00:13:35.399> you 00:13:35.509 --> 00:13:35.519 align:start position:0% be the output of another module like you 00:13:35.519 --> 00:13:37.550 align:start position:0% be the output of another module like you see<00:13:35.700> down<00:13:35.880> here<00:13:36.000> the<00:13:36.180> input<00:13:36.420> of<00:13:36.600> map<00:13:36.779> map<00:13:37.079> pools 00:13:37.550 --> 00:13:37.560 align:start position:0% see down here the input of map map pools 00:13:37.560 --> 00:13:40.370 align:start position:0% see down here the input of map map pools so<00:13:38.100> you'll<00:13:38.399> get<00:13:38.579> the<00:13:38.880> data<00:13:39.180> as<00:13:39.420> bytes<00:13:39.839> and<00:13:40.260> it 00:13:40.370 --> 00:13:40.380 align:start position:0% so you'll get the data as bytes and it 00:13:40.380 --> 00:13:42.530 align:start position:0% so you'll get the data as bytes and it also<00:13:40.680> be<00:13:40.920> a<00:13:41.639> store<00:13:41.820> which<00:13:42.180> would<00:13:42.300> be<00:13:42.420> a 00:13:42.530 --> 00:13:42.540 align:start position:0% also be a store which would be a 00:13:42.540 --> 00:13:43.850 align:start position:0% also be a store which would be a reference<00:13:42.779> we'll<00:13:43.019> see<00:13:43.200> in<00:13:43.260> the<00:13:43.380> next<00:13:43.500> slide 00:13:43.850 --> 00:13:43.860 align:start position:0% reference we'll see in the next slide 00:13:43.860 --> 00:13:45.829 align:start position:0% reference we'll see in the next slide there<00:13:43.980> and<00:13:44.639> on<00:13:44.760> the<00:13:44.940> store<00:13:45.060> pools<00:13:45.540> here<00:13:45.660> you 00:13:45.829 --> 00:13:45.839 align:start position:0% there and on the store pools here you 00:13:45.839 --> 00:13:49.430 align:start position:0% there and on the store pools here you see<00:13:46.019> there's<00:13:46.200> an<00:13:46.500> update<00:13:47.220> policy<00:13:48.000> which<00:13:48.899> sets 00:13:49.430 --> 00:13:49.440 align:start position:0% see there's an update policy which sets 00:13:49.440 --> 00:13:50.990 align:start position:0% see there's an update policy which sets constraints<00:13:49.860> on<00:13:50.100> what<00:13:50.279> you<00:13:50.399> can<00:13:50.459> do<00:13:50.639> with<00:13:50.820> the 00:13:50.990 --> 00:13:51.000 align:start position:0% constraints on what you can do with the 00:13:51.000 --> 00:13:53.569 align:start position:0% constraints on what you can do with the store<00:13:51.240> and<00:13:51.959> it<00:13:52.079> defines<00:13:52.440> a<00:13:52.680> merged<00:13:53.040> strategy 00:13:53.569 --> 00:13:53.579 align:start position:0% store and it defines a merged strategy 00:13:53.579 --> 00:13:55.250 align:start position:0% store and it defines a merged strategy for<00:13:53.880> when<00:13:54.060> you're<00:13:54.240> running<00:13:54.480> paralyzed 00:13:55.250 --> 00:13:55.260 align:start position:0% for when you're running paralyzed 00:13:55.260 --> 00:13:56.150 align:start position:0% for when you're running paralyzed operation 00:13:56.150 --> 00:13:56.160 align:start position:0% operation 00:13:56.160 --> 00:13:57.590 align:start position:0% operation okay<00:13:56.519> I'll<00:13:56.760> get<00:13:56.880> to<00:13:57.000> that<00:13:57.060> also<00:13:57.360> a<00:13:57.540> little 00:13:57.590 --> 00:13:57.600 align:start position:0% okay I'll get to that also a little 00:13:57.600 --> 00:13:59.870 align:start position:0% okay I'll get to that also a little later<00:13:57.779> and<00:13:58.200> the<00:13:58.320> value<00:13:58.500> type<00:13:58.860> field<00:13:59.160> will<00:13:59.700> help 00:13:59.870 --> 00:13:59.880 align:start position:0% later and the value type field will help 00:13:59.880 --> 00:14:02.150 align:start position:0% later and the value type field will help anyone<00:14:00.240> decoding<00:14:00.839> understand<00:14:01.260> what<00:14:01.740> bytes 00:14:02.150 --> 00:14:02.160 align:start position:0% anyone decoding understand what bytes 00:14:02.160 --> 00:14:03.829 align:start position:0% anyone decoding understand what bytes there<00:14:02.279> is<00:14:02.459> in<00:14:02.700> that<00:14:02.880> store<00:14:03.120> so<00:14:03.480> you're<00:14:03.720> going 00:14:03.829 --> 00:14:03.839 align:start position:0% there is in that store so you're going 00:14:03.839 --> 00:14:05.750 align:start position:0% there is in that store so you're going to<00:14:03.899> UI<00:14:04.139> you<00:14:04.320> can<00:14:04.440> jsonify<00:14:05.040> them<00:14:05.220> and<00:14:05.399> your<00:14:05.579> code 00:14:05.750 --> 00:14:05.760 align:start position:0% to UI you can jsonify them and your code 00:14:05.760 --> 00:14:07.490 align:start position:0% to UI you can jsonify them and your code consuming<00:14:06.420> can<00:14:06.660> automatically<00:14:07.079> you<00:14:07.380> know 00:14:07.490 --> 00:14:07.500 align:start position:0% consuming can automatically you know 00:14:07.500 --> 00:14:09.470 align:start position:0% consuming can automatically you know decode<00:14:07.860> them<00:14:08.040> with<00:14:08.220> protobuf<00:14:08.880> all<00:14:09.120> languages 00:14:09.470 --> 00:14:09.480 align:start position:0% decode them with protobuf all languages 00:14:09.480 --> 00:14:11.629 align:start position:0% decode them with protobuf all languages supported<00:14:09.959> otherwise<00:14:10.740> the<00:14:11.160> key<00:14:11.279> value<00:14:11.459> is 00:14:11.629 --> 00:14:11.639 align:start position:0% supported otherwise the key value is 00:14:11.639 --> 00:14:14.509 align:start position:0% supported otherwise the key value is just<00:14:11.820> Keys<00:14:12.420> as<00:14:12.540> strings<00:14:12.899> bytes<00:14:13.680> values<00:14:14.100> very 00:14:14.509 --> 00:14:14.519 align:start position:0% just Keys as strings bytes values very 00:14:14.519 --> 00:14:16.370 align:start position:0% just Keys as strings bytes values very simple<00:14:14.760> and<00:14:15.420> one<00:14:15.600> thing<00:14:15.720> to<00:14:15.899> note<00:14:16.019> here<00:14:16.260> is 00:14:16.370 --> 00:14:16.380 align:start position:0% simple and one thing to note here is 00:14:16.380 --> 00:14:18.470 align:start position:0% simple and one thing to note here is that<00:14:16.560> because<00:14:16.860> it<00:14:17.279> has<00:14:17.399> deterministic<00:14:18.120> input 00:14:18.470 --> 00:14:18.480 align:start position:0% that because it has deterministic input 00:14:18.480 --> 00:14:22.129 align:start position:0% that because it has deterministic input it's<00:14:19.380> possible<00:14:19.800> to<00:14:20.220> Hash<00:14:20.880> a<00:14:21.120> module<00:14:21.540> like<00:14:21.959> the 00:14:22.129 --> 00:14:22.139 align:start position:0% it's possible to Hash a module like the 00:14:22.139 --> 00:14:24.650 align:start position:0% it's possible to Hash a module like the kind<00:14:22.380> and<00:14:22.980> all<00:14:23.100> of<00:14:23.220> its<00:14:23.519> inputs<00:14:24.000> and<00:14:24.480> the 00:14:24.650 --> 00:14:24.660 align:start position:0% kind and all of its inputs and the 00:14:24.660 --> 00:14:26.449 align:start position:0% kind and all of its inputs and the pointers<00:14:25.019> to<00:14:25.200> its<00:14:25.500> parents<00:14:25.860> and<00:14:26.100> including 00:14:26.449 --> 00:14:26.459 align:start position:0% pointers to its parents and including 00:14:26.459 --> 00:14:29.030 align:start position:0% pointers to its parents and including the<00:14:26.579> initial<00:14:26.880> block<00:14:27.120> so<00:14:27.839> you<00:14:28.019> have<00:14:28.260> a<00:14:28.620> fully 00:14:29.030 --> 00:14:29.040 align:start position:0% the initial block so you have a fully 00:14:29.040 --> 00:14:31.850 align:start position:0% the initial block so you have a fully determined<00:14:29.760> and<00:14:30.000> hashable<00:14:30.660> let's<00:14:31.019> say<00:14:31.260> cache 00:14:31.850 --> 00:14:31.860 align:start position:0% determined and hashable let's say cache 00:14:31.860 --> 00:14:34.190 align:start position:0% determined and hashable let's say cache location<00:14:32.120> for<00:14:33.120> all<00:14:33.360> of<00:14:33.480> the<00:14:33.600> history<00:14:33.720> similar 00:14:34.190 --> 00:14:34.200 align:start position:0% location for all of the history similar 00:14:34.200 --> 00:14:36.050 align:start position:0% location for all of the history similar to<00:14:34.320> git<00:14:34.560> right<00:14:34.740> all<00:14:35.040> the<00:14:35.279> history<00:14:35.459> of<00:14:35.700> data 00:14:36.050 --> 00:14:36.060 align:start position:0% to git right all the history of data 00:14:36.060 --> 00:14:38.449 align:start position:0% to git right all the history of data produced<00:14:36.480> by<00:14:37.079> by<00:14:37.380> and<00:14:37.740> you'd<00:14:37.920> hash<00:14:38.100> also<00:14:38.279> the 00:14:38.449 --> 00:14:38.459 align:start position:0% produced by by and you'd hash also the 00:14:38.459 --> 00:14:41.689 align:start position:0% produced by by and you'd hash also the wasm<00:14:38.880> code<00:14:39.120> right<00:14:39.380> so<00:14:40.380> it<00:14:40.920> makes<00:14:41.040> it<00:14:41.279> for<00:14:41.459> an 00:14:41.689 --> 00:14:41.699 align:start position:0% wasm code right so it makes it for an 00:14:41.699 --> 00:14:44.389 align:start position:0% wasm code right so it makes it for an extremely<00:14:42.120> cachable<00:14:42.779> system<00:14:43.139> and<00:14:44.040> highly 00:14:44.389 --> 00:14:44.399 align:start position:0% extremely cachable system and highly 00:14:44.399 --> 00:14:47.569 align:start position:0% extremely cachable system and highly shareable<00:14:45.000> and<00:14:45.779> cross<00:14:46.079> verifiable<00:14:46.860> output<00:14:47.399> of 00:14:47.569 --> 00:14:47.579 align:start position:0% shareable and cross verifiable output of 00:14:47.579 --> 00:14:49.250 align:start position:0% shareable and cross verifiable output of modules<00:14:48.000> which<00:14:48.300> opens<00:14:48.660> really<00:14:48.839> interesting 00:14:49.250 --> 00:14:49.260 align:start position:0% modules which opens really interesting 00:14:49.260 --> 00:14:51.410 align:start position:0% modules which opens really interesting possibilities<00:14:49.860> you<00:14:50.699> know<00:14:50.820> for<00:14:51.180> uh 00:14:51.410 --> 00:14:51.420 align:start position:0% possibilities you know for uh 00:14:51.420 --> 00:14:53.150 align:start position:0% possibilities you know for uh collaboration<00:14:51.959> within<00:14:52.440> the<00:14:52.560> graph<00:14:52.740> ecosystem 00:14:53.150 --> 00:14:53.160 align:start position:0% collaboration within the graph ecosystem 00:14:53.160 --> 00:14:55.790 align:start position:0% collaboration within the graph ecosystem and<00:14:54.060> imagine<00:14:54.240> one<00:14:54.839> has<00:14:55.079> large<00:14:55.320> disks<00:14:55.740> and 00:14:55.790 --> 00:14:55.800 align:start position:0% and imagine one has large disks and 00:14:55.800 --> 00:14:57.470 align:start position:0% and imagine one has large disks and everyone<00:14:55.920> has<00:14:56.100> large<00:14:56.519> CPUs<00:14:57.000> or<00:14:57.240> you<00:14:57.360> know 00:14:57.470 --> 00:14:57.480 align:start position:0% everyone has large CPUs or you know 00:14:57.480 --> 00:14:59.629 align:start position:0% everyone has large CPUs or you know sleeping<00:14:57.720> CPUs<00:14:58.139> they<00:14:58.680> could<00:14:58.800> pull<00:14:59.040> resources 00:14:59.629 --> 00:14:59.639 align:start position:0% sleeping CPUs they could pull resources 00:14:59.639 --> 00:15:01.009 align:start position:0% sleeping CPUs they could pull resources together<00:14:59.880> to<00:15:00.180> build<00:15:00.300> something<00:15:00.540> bigger<00:15:00.899> than 00:15:01.009 --> 00:15:01.019 align:start position:0% together to build something bigger than 00:15:01.019 --> 00:15:02.389 align:start position:0% together to build something bigger than themselves 00:15:02.389 --> 00:15:02.399 align:start position:0% themselves 00:15:02.399 --> 00:15:04.250 align:start position:0% themselves okay<00:15:02.820> you<00:15:03.000> see<00:15:03.180> the<00:15:03.300> relation<00:15:03.420> there<00:15:03.779> so<00:15:04.019> this 00:15:04.250 --> 00:15:04.260 align:start position:0% okay you see the relation there so this 00:15:04.260 --> 00:15:06.350 align:start position:0% okay you see the relation there so this gets<00:15:04.560> piped<00:15:04.800> to<00:15:04.920> that<00:15:05.100> and<00:15:05.519> if<00:15:05.699> we<00:15:05.820> add<00:15:06.000> another 00:15:06.350 --> 00:15:06.360 align:start position:0% gets piped to that and if we add another 00:15:06.360 --> 00:15:08.329 align:start position:0% gets piped to that and if we add another module<00:15:06.899> here<00:15:07.139> you<00:15:07.320> see<00:15:07.440> how<00:15:07.620> the<00:15:07.740> graph<00:15:07.980> comes 00:15:08.329 --> 00:15:08.339 align:start position:0% module here you see how the graph comes 00:15:08.339 --> 00:15:10.610 align:start position:0% module here you see how the graph comes together<00:15:08.519> this<00:15:09.300> one<00:15:09.480> computes<00:15:10.139> the<00:15:10.380> price 00:15:10.610 --> 00:15:10.620 align:start position:0% together this one computes the price 00:15:10.620 --> 00:15:13.430 align:start position:0% together this one computes the price this<00:15:10.920> is<00:15:11.040> unit<00:15:11.220> swap<00:15:11.579> V3<00:15:11.940> thing<00:15:12.180> it<00:15:13.079> computes 00:15:13.430 --> 00:15:13.440 align:start position:0% this is unit swap V3 thing it computes 00:15:13.440 --> 00:15:15.050 align:start position:0% this is unit swap V3 thing it computes the<00:15:13.500> price<00:15:13.740> but<00:15:13.980> it<00:15:14.160> you<00:15:14.519> want<00:15:14.639> to<00:15:14.760> get<00:15:14.880> them 00:15:15.050 --> 00:15:15.060 align:start position:0% the price but it you want to get them 00:15:15.060 --> 00:15:16.430 align:start position:0% the price but it you want to get them for<00:15:15.300> certain<00:15:15.480> pools<00:15:15.899> because<00:15:16.019> maybe<00:15:16.199> you<00:15:16.380> want 00:15:16.430 --> 00:15:16.440 align:start position:0% for certain pools because maybe you want 00:15:16.440 --> 00:15:17.990 align:start position:0% for certain pools because maybe you want to<00:15:16.560> use<00:15:16.620> the<00:15:16.860> decimal<00:15:17.279> placements<00:15:17.760> in<00:15:17.880> the 00:15:17.990 --> 00:15:18.000 align:start position:0% to use the decimal placements in the 00:15:18.000 --> 00:15:19.910 align:start position:0% to use the decimal placements in the pool<00:15:18.060> we'll<00:15:18.300> see<00:15:18.480> a<00:15:18.720> little<00:15:18.839> bit<00:15:18.959> more<00:15:19.079> there 00:15:19.910 --> 00:15:19.920 align:start position:0% pool we'll see a little bit more there 00:15:19.920 --> 00:15:21.650 align:start position:0% pool we'll see a little bit more there and<00:15:20.519> when<00:15:20.820> you're<00:15:20.940> running<00:15:21.120> let's<00:15:21.360> say<00:15:21.480> you're 00:15:21.650 --> 00:15:21.660 align:start position:0% and when you're running let's say you're 00:15:21.660 --> 00:15:24.470 align:start position:0% and when you're running let's say you're running<00:15:21.839> that<00:15:22.019> at<00:15:22.320> block<00:15:22.620> 15<00:15:23.040> million 00:15:24.470 --> 00:15:24.480 align:start position:0% running that at block 15 million 00:15:24.480 --> 00:15:27.650 align:start position:0% running that at block 15 million well<00:15:25.680> you're<00:15:26.339> guaranteed<00:15:26.880> the<00:15:27.240> runtime 00:15:27.650 --> 00:15:27.660 align:start position:0% well you're guaranteed the runtime 00:15:27.660 --> 00:15:31.129 align:start position:0% well you're guaranteed the runtime guarantees<00:15:28.320> that<00:15:28.680> the<00:15:29.519> store<00:15:29.880> you'll<00:15:30.660> have<00:15:30.899> to 00:15:31.129 --> 00:15:31.139 align:start position:0% guarantees that the store you'll have to 00:15:31.139 --> 00:15:33.170 align:start position:0% guarantees that the store you'll have to execute<00:15:31.500> code<00:15:31.680> at<00:15:31.860> block<00:15:32.040> 50<00:15:32.279> million<00:15:32.579> will 00:15:33.170 --> 00:15:33.180 align:start position:0% execute code at block 50 million will 00:15:33.180 --> 00:15:34.689 align:start position:0% execute code at block 50 million will have<00:15:33.420> been<00:15:33.660> synced 00:15:34.689 --> 00:15:34.699 align:start position:0% have been synced 00:15:34.699 --> 00:15:37.189 align:start position:0% have been synced linearly<00:15:35.699> or<00:15:36.180> in<00:15:36.420> parallel<00:15:36.779> but<00:15:36.959> you<00:15:37.139> wouldn't 00:15:37.189 --> 00:15:37.199 align:start position:0% linearly or in parallel but you wouldn't 00:15:37.199 --> 00:15:39.230 align:start position:0% linearly or in parallel but you wouldn't know<00:15:37.440> but<00:15:37.620> it'll<00:15:37.800> give<00:15:38.040> you<00:15:38.160> a<00:15:38.459> full<00:15:38.579> in-memory 00:15:39.230 --> 00:15:39.240 align:start position:0% know but it'll give you a full in-memory 00:15:39.240 --> 00:15:40.850 align:start position:0% know but it'll give you a full in-memory store<00:15:39.480> eventually<00:15:40.019> backed<00:15:40.320> by<00:15:40.380> some<00:15:40.500> disk<00:15:40.800> but 00:15:40.850 --> 00:15:40.860 align:start position:0% store eventually backed by some disk but 00:15:40.860 --> 00:15:43.129 align:start position:0% store eventually backed by some disk but whatever<00:15:41.040> and<00:15:41.820> you<00:15:42.000> can<00:15:42.120> query<00:15:42.480> the<00:15:42.779> key<00:15:42.959> value 00:15:43.129 --> 00:15:43.139 align:start position:0% whatever and you can query the key value 00:15:43.139 --> 00:15:45.290 align:start position:0% whatever and you can query the key value store<00:15:43.560> at<00:15:44.100> each<00:15:44.279> block<00:15:44.519> it's<00:15:44.760> guaranteed<00:15:45.180> to 00:15:45.290 --> 00:15:45.300 align:start position:0% store at each block it's guaranteed to 00:15:45.300 --> 00:15:47.329 align:start position:0% store at each block it's guaranteed to be<00:15:45.420> synced<00:15:45.839> for<00:15:45.959> you<00:15:46.139> that's<00:15:46.560> exciting<00:15:46.980> no 00:15:47.329 --> 00:15:47.339 align:start position:0% be synced for you that's exciting no 00:15:47.339 --> 00:15:50.090 align:start position:0% be synced for you that's exciting no okay<00:15:47.699> uh<00:15:48.480> so<00:15:48.720> you<00:15:48.899> see<00:15:49.019> the<00:15:49.260> dags<00:15:49.680> fully<00:15:49.920> being 00:15:50.090 --> 00:15:50.100 align:start position:0% okay uh so you see the dags fully being 00:15:50.100 --> 00:15:52.910 align:start position:0% okay uh so you see the dags fully being built<00:15:50.519> huh<00:15:50.940> right<00:15:51.240> so<00:15:51.480> the<00:15:51.720> dependency<00:15:52.079> so<00:15:52.740> now 00:15:52.910 --> 00:15:52.920 align:start position:0% built huh right so the dependency so now 00:15:52.920 --> 00:15:54.470 align:start position:0% built huh right so the dependency so now let's<00:15:53.220> let's 00:15:54.470 --> 00:15:54.480 align:start position:0% let's let's 00:15:54.480 --> 00:15:57.590 align:start position:0% let's let's this<00:15:55.019> leads<00:15:55.320> us<00:15:55.440> to<00:15:55.740> composability<00:15:56.579> see<00:15:57.360> each 00:15:57.590 --> 00:15:57.600 align:start position:0% this leads us to composability see each 00:15:57.600 --> 00:16:00.110 align:start position:0% this leads us to composability see each color<00:15:57.779> here<00:15:58.019> means<00:15:58.380> a<00:15:58.500> different<00:15:58.620> author<00:15:59.339> and 00:16:00.110 --> 00:16:00.120 align:start position:0% color here means a different author and 00:16:00.120 --> 00:16:01.810 align:start position:0% color here means a different author and modules<00:16:00.540> written<00:16:00.839> by<00:16:00.959> different<00:16:01.199> people 00:16:01.810 --> 00:16:01.820 align:start position:0% modules written by different people 00:16:01.820 --> 00:16:04.430 align:start position:0% modules written by different people ideally<00:16:02.820> the<00:16:03.060> most<00:16:03.240> competent<00:16:03.839> for<00:16:04.139> each 00:16:04.430 --> 00:16:04.440 align:start position:0% ideally the most competent for each 00:16:04.440 --> 00:16:07.129 align:start position:0% ideally the most competent for each right<00:16:04.620> like<00:16:04.800> we<00:16:05.040> would<00:16:05.279> hope<00:16:05.600> they<00:16:06.600> would<00:16:06.779> crop 00:16:07.129 --> 00:16:07.139 align:start position:0% right like we would hope they would crop 00:16:07.139 --> 00:16:08.930 align:start position:0% right like we would hope they would crop you<00:16:07.380> know<00:16:07.500> analyze<00:16:07.920> what's<00:16:08.100> on<00:16:08.279> chain<00:16:08.519> and 00:16:08.930 --> 00:16:08.940 align:start position:0% you know analyze what's on chain and 00:16:08.940 --> 00:16:12.050 align:start position:0% you know analyze what's on chain and refine<00:16:09.600> the<00:16:09.899> data<00:16:10.320> and<00:16:10.860> Abstract<00:16:11.339> it<00:16:11.579> to<00:16:11.820> new 00:16:12.050 --> 00:16:12.060 align:start position:0% refine the data and Abstract it to new 00:16:12.060 --> 00:16:13.009 align:start position:0% refine the data and Abstract it to new heights 00:16:13.009 --> 00:16:13.019 align:start position:0% heights 00:16:13.019 --> 00:16:15.350 align:start position:0% heights and<00:16:13.620> the<00:16:13.920> contract<00:16:14.220> between<00:16:14.459> the<00:16:14.699> handoffs<00:16:15.180> is 00:16:15.350 --> 00:16:15.360 align:start position:0% and the contract between the handoffs is 00:16:15.360 --> 00:16:18.290 align:start position:0% and the contract between the handoffs is always<00:16:15.600> data<00:16:16.500> it's<00:16:17.100> the<00:16:17.339> model<00:16:17.519> of<00:16:17.820> data<00:16:18.120> so 00:16:18.290 --> 00:16:18.300 align:start position:0% always data it's the model of data so 00:16:18.300 --> 00:16:20.750 align:start position:0% always data it's the model of data so you<00:16:18.480> take<00:16:18.660> a<00:16:18.779> modulus<00:16:19.199> bytes<00:16:19.680> in<00:16:19.800> bytes<00:16:20.639> out 00:16:20.750 --> 00:16:20.760 align:start position:0% you take a modulus bytes in bytes out 00:16:20.760 --> 00:16:22.670 align:start position:0% you take a modulus bytes in bytes out and<00:16:21.540> so<00:16:21.720> you<00:16:21.839> see<00:16:21.959> here<00:16:22.139> we<00:16:22.260> can<00:16:22.380> get<00:16:22.500> the 00:16:22.670 --> 00:16:22.680 align:start position:0% and so you see here we can get the 00:16:22.680 --> 00:16:25.009 align:start position:0% and so you see here we can get the prices<00:16:22.860> from<00:16:23.160> using<00:16:23.459> V2<00:16:23.940> and<00:16:24.660> price<00:16:24.839> this 00:16:25.009 --> 00:16:25.019 align:start position:0% prices from using V2 and price this 00:16:25.019 --> 00:16:26.810 align:start position:0% prices from using V2 and price this version<00:16:25.260> of<00:16:25.620> B3<00:16:25.860> and<00:16:26.040> Sushi<00:16:26.399> and<00:16:26.519> chain<00:16:26.639> link 00:16:26.810 --> 00:16:26.820 align:start position:0% version of B3 and Sushi and chain link 00:16:26.820 --> 00:16:29.090 align:start position:0% version of B3 and Sushi and chain link and<00:16:27.060> whatever<00:16:27.300> and<00:16:27.839> have<00:16:28.139> someone<00:16:28.380> reality<00:16:28.920> a 00:16:29.090 --> 00:16:29.100 align:start position:0% and whatever and have someone reality a 00:16:29.100 --> 00:16:30.470 align:start position:0% and whatever and have someone reality a module<00:16:29.339> that<00:16:29.459> takes<00:16:29.699> these<00:16:29.940> input<00:16:30.240> at 00:16:30.470 --> 00:16:30.480 align:start position:0% module that takes these input at 00:16:30.480 --> 00:16:31.850 align:start position:0% module that takes these input at transformation<00:16:30.839> time 00:16:31.850 --> 00:16:31.860 align:start position:0% transformation time 00:16:31.860 --> 00:16:34.069 align:start position:0% transformation time and<00:16:32.339> then<00:16:32.459> averages<00:16:33.000> them<00:16:33.300> out<00:16:33.480> and<00:16:33.660> whatnot 00:16:34.069 --> 00:16:34.079 align:start position:0% and then averages them out and whatnot 00:16:34.079 --> 00:16:35.810 align:start position:0% and then averages them out and whatnot right<00:16:34.500> and<00:16:34.740> then<00:16:34.860> that<00:16:35.040> you'd<00:16:35.279> have<00:16:35.399> like<00:16:35.579> sort 00:16:35.810 --> 00:16:35.820 align:start position:0% right and then that you'd have like sort 00:16:35.820 --> 00:16:38.210 align:start position:0% right and then that you'd have like sort of<00:16:35.940> one<00:16:36.180> beautiful<00:16:36.360> Universal<00:16:37.199> price<00:16:37.620> module 00:16:38.210 --> 00:16:38.220 align:start position:0% of one beautiful Universal price module 00:16:38.220 --> 00:16:41.030 align:start position:0% of one beautiful Universal price module that<00:16:38.940> you<00:16:39.180> can<00:16:39.300> then<00:16:39.600> hook<00:16:39.899> on<00:16:40.620> top<00:16:40.680> and<00:16:40.920> and 00:16:41.030 --> 00:16:41.040 align:start position:0% that you can then hook on top and and 00:16:41.040 --> 00:16:42.710 align:start position:0% that you can then hook on top and and feed<00:16:41.399> to<00:16:41.579> some<00:16:41.699> who<00:16:41.940> knows<00:16:42.120> maybe<00:16:42.300> if<00:16:42.480> someone 00:16:42.710 --> 00:16:42.720 align:start position:0% feed to some who knows maybe if someone 00:16:42.720 --> 00:16:44.509 align:start position:0% feed to some who knows maybe if someone feeds<00:16:43.139> that<00:16:43.259> back<00:16:43.500> onto<00:16:43.800> the<00:16:43.980> chain<00:16:44.100> for<00:16:44.399> some 00:16:44.509 --> 00:16:44.519 align:start position:0% feeds that back onto the chain for some 00:16:44.519 --> 00:16:47.629 align:start position:0% feeds that back onto the chain for some reason<00:16:44.699> and<00:16:45.660> then<00:16:45.839> soon<00:16:46.199> enough<00:16:46.380> you<00:16:46.800> know<00:16:46.860> all 00:16:47.629 --> 00:16:47.639 align:start position:0% reason and then soon enough you know all 00:16:47.639 --> 00:16:49.670 align:start position:0% reason and then soon enough you know all of<00:16:47.820> that<00:16:48.060> while<00:16:48.600> someone<00:16:48.839> wants<00:16:49.199> to<00:16:49.259> build<00:16:49.440> on 00:16:49.670 --> 00:16:49.680 align:start position:0% of that while someone wants to build on 00:16:49.680 --> 00:16:52.129 align:start position:0% of that while someone wants to build on top<00:16:49.860> of<00:16:50.040> it<00:16:50.699> ah<00:16:51.360> something<00:16:51.600> like<00:16:51.839> that<00:16:51.959> if 00:16:52.129 --> 00:16:52.139 align:start position:0% top of it ah something like that if 00:16:52.139 --> 00:16:54.350 align:start position:0% top of it ah something like that if someone<00:16:52.380> wants<00:16:52.800> to<00:16:52.860> compute<00:16:53.459> you<00:16:53.940> know<00:16:54.060> the 00:16:54.350 --> 00:16:54.360 align:start position:0% someone wants to compute you know the 00:16:54.360 --> 00:16:57.290 align:start position:0% someone wants to compute you know the USD<00:16:55.139> denominated<00:16:55.860> volumes<00:16:56.519> aggregation<00:16:57.060> of 00:16:57.290 --> 00:16:57.300 align:start position:0% USD denominated volumes aggregation of 00:16:57.300 --> 00:16:59.689 align:start position:0% USD denominated volumes aggregation of nft<00:16:57.600> sales<00:16:57.959> on<00:16:58.199> openc<00:16:58.620> you<00:16:58.860> know<00:16:58.980> you'll<00:16:59.519> take 00:16:59.689 --> 00:16:59.699 align:start position:0% nft sales on openc you know you'll take 00:16:59.699 --> 00:17:01.670 align:start position:0% nft sales on openc you know you'll take some<00:17:00.060> sales<00:17:00.360> you<00:17:00.779> merge<00:17:01.139> it<00:17:01.199> with<00:17:01.320> the<00:17:01.440> price 00:17:01.670 --> 00:17:01.680 align:start position:0% some sales you merge it with the price 00:17:01.680 --> 00:17:04.309 align:start position:0% some sales you merge it with the price and<00:17:02.279> we<00:17:02.519> see<00:17:02.639> here<00:17:02.820> that<00:17:03.060> little<00:17:03.240> Trader<00:17:03.899> Inc 00:17:04.309 --> 00:17:04.319 align:start position:0% and we see here that little Trader Inc 00:17:04.319 --> 00:17:07.250 align:start position:0% and we see here that little Trader Inc he<00:17:05.100> seems<00:17:05.400> he<00:17:05.520> maybe<00:17:05.699> he<00:17:06.000> wants<00:17:06.299> to<00:17:06.360> feed<00:17:07.020> that 00:17:07.250 --> 00:17:07.260 align:start position:0% he seems he maybe he wants to feed that 00:17:07.260 --> 00:17:09.530 align:start position:0% he seems he maybe he wants to feed that into<00:17:07.439> his<00:17:07.740> trading<00:17:08.280> bot<00:17:08.640> because<00:17:09.120> it's<00:17:09.360> a 00:17:09.530 --> 00:17:09.540 align:start position:0% into his trading bot because it's a 00:17:09.540 --> 00:17:10.730 align:start position:0% into his trading bot because it's a streaming<00:17:09.900> engine<00:17:10.020> we're<00:17:10.199> not<00:17:10.380> storing<00:17:10.620> that 00:17:10.730 --> 00:17:10.740 align:start position:0% streaming engine we're not storing that 00:17:10.740 --> 00:17:12.890 align:start position:0% streaming engine we're not storing that in<00:17:10.799> the<00:17:10.919> database<00:17:11.220> yet<00:17:11.459> right<00:17:11.699> but<00:17:12.419> this<00:17:12.540> begs 00:17:12.890 --> 00:17:12.900 align:start position:0% in the database yet right but this begs 00:17:12.900 --> 00:17:14.270 align:start position:0% in the database yet right but this begs the<00:17:13.020> question<00:17:13.140> where<00:17:13.620> is<00:17:13.799> that<00:17:13.919> all<00:17:14.040> that 00:17:14.270 --> 00:17:14.280 align:start position:0% the question where is that all that 00:17:14.280 --> 00:17:16.010 align:start position:0% the question where is that all that beautiful<00:17:14.459> data<00:17:14.939> at<00:17:15.120> land<00:17:15.419> where<00:17:15.660> does<00:17:15.780> it<00:17:15.900> get 00:17:16.010 --> 00:17:16.020 align:start position:0% beautiful data at land where does it get 00:17:16.020 --> 00:17:18.530 align:start position:0% beautiful data at land where does it get piped<00:17:16.439> that's<00:17:16.980> where<00:17:17.280> it<00:17:17.520> thinks<00:17:18.059> head<00:17:18.360> up 00:17:18.530 --> 00:17:18.540 align:start position:0% piped that's where it thinks head up 00:17:18.540 --> 00:17:21.890 align:start position:0% piped that's where it thinks head up like<00:17:19.760> substreams<00:17:20.760> being<00:17:21.000> limited<00:17:21.480> to<00:17:21.720> the 00:17:21.890 --> 00:17:21.900 align:start position:0% like substreams being limited to the 00:17:21.900 --> 00:17:23.929 align:start position:0% like substreams being limited to the transformation<00:17:22.319> stage<00:17:22.799> of<00:17:22.980> the<00:17:23.280> ETL<00:17:23.520> analogy 00:17:23.929 --> 00:17:23.939 align:start position:0% transformation stage of the ETL analogy 00:17:23.939 --> 00:17:25.850 align:start position:0% transformation stage of the ETL analogy remember<00:17:24.120> it<00:17:24.959> doesn't<00:17:25.079> really<00:17:25.319> care<00:17:25.559> where 00:17:25.850 --> 00:17:25.860 align:start position:0% remember it doesn't really care where 00:17:25.860 --> 00:17:27.829 align:start position:0% remember it doesn't really care where you<00:17:25.980> load<00:17:26.339> it<00:17:26.459> and<00:17:26.819> that<00:17:27.000> could<00:17:27.179> be<00:17:27.360> anywhere 00:17:27.829 --> 00:17:27.839 align:start position:0% you load it and that could be anywhere 00:17:27.839 --> 00:17:29.870 align:start position:0% you load it and that could be anywhere these<00:17:28.679> are<00:17:28.740> just<00:17:28.860> a<00:17:28.980> few<00:17:29.100> examples<00:17:29.460> you<00:17:29.700> can 00:17:29.870 --> 00:17:29.880 align:start position:0% these are just a few examples you can 00:17:29.880 --> 00:17:31.549 align:start position:0% these are just a few examples you can load<00:17:30.120> that<00:17:30.240> in<00:17:30.360> databases<00:17:30.780> we<00:17:31.140> already<00:17:31.260> have<00:17:31.440> a 00:17:31.549 --> 00:17:31.559 align:start position:0% load that in databases we already have a 00:17:31.559 --> 00:17:33.590 align:start position:0% load that in databases we already have a sync<00:17:31.860> for<00:17:31.980> postgres<00:17:32.580> and<00:17:33.120> you<00:17:33.240> hook<00:17:33.419> to 00:17:33.590 --> 00:17:33.600 align:start position:0% sync for postgres and you hook to 00:17:33.600 --> 00:17:35.450 align:start position:0% sync for postgres and you hook to sub<00:17:33.720> streams<00:17:34.080> and<00:17:34.200> it<00:17:34.380> just<00:17:34.559> loads<00:17:35.220> it<00:17:35.340> into 00:17:35.450 --> 00:17:35.460 align:start position:0% sub streams and it just loads it into 00:17:35.460 --> 00:17:37.490 align:start position:0% sub streams and it just loads it into postgres<00:17:36.000> with<00:17:36.600> a<00:17:36.780> data<00:17:37.080> model<00:17:37.140> that<00:17:37.380> we've 00:17:37.490 --> 00:17:37.500 align:start position:0% postgres with a data model that we've 00:17:37.500 --> 00:17:39.230 align:start position:0% postgres with a data model that we've agreed<00:17:37.799> upon<00:17:38.039> right<00:17:38.280> if<00:17:38.640> you<00:17:38.760> write<00:17:38.880> it<00:17:39.000> in<00:17:39.120> a 00:17:39.230 --> 00:17:39.240 align:start position:0% agreed upon right if you write it in a 00:17:39.240 --> 00:17:40.789 align:start position:0% agreed upon right if you write it in a certain<00:17:39.360> way<00:17:39.539> it<00:17:39.960> just<00:17:40.140> thinks<00:17:40.440> over<00:17:40.559> there 00:17:40.789 --> 00:17:40.799 align:start position:0% certain way it just thinks over there 00:17:40.799 --> 00:17:43.370 align:start position:0% certain way it just thinks over there and<00:17:41.400> or<00:17:41.640> message<00:17:41.940> cues<00:17:42.419> or<00:17:42.600> whatever<00:17:42.840> you<00:17:43.260> know 00:17:43.370 --> 00:17:43.380 align:start position:0% and or message cues or whatever you know 00:17:43.380 --> 00:17:45.950 align:start position:0% and or message cues or whatever you know data<00:17:44.160> lakes<00:17:44.400> or<00:17:44.700> some<00:17:44.940> Bots<00:17:45.240> or<00:17:45.480> some<00:17:45.660> trading 00:17:45.950 --> 00:17:45.960 align:start position:0% data lakes or some Bots or some trading 00:17:45.960 --> 00:17:47.330 align:start position:0% data lakes or some Bots or some trading already<00:17:46.140> you<00:17:46.440> know<00:17:46.559> so<00:17:46.740> I<00:17:46.980> don't<00:17:47.100> know<00:17:47.160> some 00:17:47.330 --> 00:17:47.340 align:start position:0% already you know so I don't know some 00:17:47.340 --> 00:17:49.549 align:start position:0% already you know so I don't know some whale<00:17:47.700> detector<00:17:48.240> you<00:17:48.480> want<00:17:48.660> to<00:17:48.840> hook<00:17:49.080> directly 00:17:49.549 --> 00:17:49.559 align:start position:0% whale detector you want to hook directly 00:17:49.559 --> 00:17:51.890 align:start position:0% whale detector you want to hook directly on<00:17:49.679> the<00:17:49.799> stream<00:17:49.980> or<00:17:50.400> also<00:17:50.640> so<00:17:51.000> something<00:17:51.360> I 00:17:51.890 --> 00:17:51.900 align:start position:0% on the stream or also so something I 00:17:51.900 --> 00:17:54.529 align:start position:0% on the stream or also so something I think<00:17:52.020> big<00:17:52.260> for<00:17:53.039> doing<00:17:53.400> some<00:17:53.640> ad<00:17:53.880> hoc<00:17:54.120> data 00:17:54.529 --> 00:17:54.539 align:start position:0% think big for doing some ad hoc data 00:17:54.539 --> 00:17:55.789 align:start position:0% think big for doing some ad hoc data science<00:17:54.660> because<00:17:54.960> you<00:17:55.140> know<00:17:55.200> you<00:17:55.440> have<00:17:55.559> a 00:17:55.789 --> 00:17:55.799 align:start position:0% science because you know you have a 00:17:55.799 --> 00:17:57.710 align:start position:0% science because you know you have a really<00:17:55.860> fast<00:17:56.160> engine<00:17:56.460> allows<00:17:57.240> you<00:17:57.299> to<00:17:57.480> process 00:17:57.710 --> 00:17:57.720 align:start position:0% really fast engine allows you to process 00:17:57.720 --> 00:18:00.110 align:start position:0% really fast engine allows you to process the<00:17:57.960> whole<00:17:58.140> history<00:17:58.320> in<00:17:59.100> like<00:17:59.400> it<00:17:59.700> can<00:17:59.820> take<00:17:59.940> a 00:18:00.110 --> 00:18:00.120 align:start position:0% the whole history in like it can take a 00:18:00.120 --> 00:18:01.909 align:start position:0% the whole history in like it can take a few<00:18:00.299> minutes<00:18:00.480> to<00:18:01.080> process<00:18:01.440> the<00:18:01.620> whole<00:18:01.679> of<00:18:01.799> it 00:18:01.909 --> 00:18:01.919 align:start position:0% few minutes to process the whole of it 00:18:01.919 --> 00:18:03.350 align:start position:0% few minutes to process the whole of it here<00:18:02.039> image<00:18:02.220> to<00:18:02.460> go<00:18:02.580> and<00:18:02.700> pluck<00:18:02.940> some<00:18:03.120> new 00:18:03.350 --> 00:18:03.360 align:start position:0% here image to go and pluck some new 00:18:03.360 --> 00:18:05.690 align:start position:0% here image to go and pluck some new insights<00:18:03.780> so<00:18:04.080> you<00:18:04.200> can<00:18:04.320> write<00:18:04.559> your<00:18:04.860> code<00:18:05.039> send 00:18:05.690 --> 00:18:05.700 align:start position:0% insights so you can write your code send 00:18:05.700 --> 00:18:07.250 align:start position:0% insights so you can write your code send it<00:18:05.820> to<00:18:05.940> the<00:18:06.000> network<00:18:06.179> and<00:18:06.539> then<00:18:06.720> you<00:18:07.200> know 00:18:07.250 --> 00:18:07.260 align:start position:0% it to the network and then you know 00:18:07.260 --> 00:18:09.289 align:start position:0% it to the network and then you know stream<00:18:07.559> out<00:18:07.799> the<00:18:07.980> results<00:18:08.100> similar<00:18:08.580> to<00:18:08.700> for 00:18:09.289 --> 00:18:09.299 align:start position:0% stream out the results similar to for 00:18:09.299 --> 00:18:11.270 align:start position:0% stream out the results similar to for those<00:18:09.419> who<00:18:09.600> know<00:18:09.780> big<00:18:10.080> query<00:18:10.620> you<00:18:11.039> know<00:18:11.160> the 00:18:11.270 --> 00:18:11.280 align:start position:0% those who know big query you know the 00:18:11.280 --> 00:18:13.370 align:start position:0% those who know big query you know the cluster<00:18:11.640> the<00:18:11.880> big<00:18:12.299> cluster<00:18:12.660> the<00:18:12.780> service<00:18:13.080> by 00:18:13.370 --> 00:18:13.380 align:start position:0% cluster the big cluster the service by 00:18:13.380 --> 00:18:15.230 align:start position:0% cluster the big cluster the service by Google<00:18:13.620> that's<00:18:14.280> what<00:18:14.520> they<00:18:14.640> do<00:18:14.760> you<00:18:14.940> send<00:18:15.059> the 00:18:15.230 --> 00:18:15.240 align:start position:0% Google that's what they do you send the 00:18:15.240 --> 00:18:16.730 align:start position:0% Google that's what they do you send the request<00:18:15.480> they<00:18:15.780> just<00:18:15.960> shot<00:18:16.440> at<00:18:16.620> everything 00:18:16.730 --> 00:18:16.740 align:start position:0% request they just shot at everything 00:18:16.740 --> 00:18:18.590 align:start position:0% request they just shot at everything they<00:18:17.039> send<00:18:17.220> you<00:18:17.340> back<00:18:17.460> the<00:18:17.640> request<00:18:17.880> well<00:18:18.360> all 00:18:18.590 --> 00:18:18.600 align:start position:0% they send you back the request well all 00:18:18.600 --> 00:18:20.390 align:start position:0% they send you back the request well all of<00:18:18.720> a<00:18:18.720> sudden<00:18:18.840> substream's<00:18:19.559> engine<00:18:19.679> can<00:18:20.100> allow 00:18:20.390 --> 00:18:20.400 align:start position:0% of a sudden substream's engine can allow 00:18:20.400 --> 00:18:22.190 align:start position:0% of a sudden substream's engine can allow you<00:18:20.460> to<00:18:20.580> do<00:18:20.760> some<00:18:21.000> things<00:18:21.240> like<00:18:21.480> that<00:18:21.660> ad<00:18:22.020> hoc 00:18:22.190 --> 00:18:22.200 align:start position:0% you to do some things like that ad hoc 00:18:22.200 --> 00:18:25.490 align:start position:0% you to do some things like that ad hoc and<00:18:22.799> it<00:18:23.160> you<00:18:23.580> can<00:18:23.700> write<00:18:23.820> any<00:18:24.059> program<00:18:24.299> uh<00:18:25.260> that 00:18:25.490 --> 00:18:25.500 align:start position:0% and it you can write any program uh that 00:18:25.500 --> 00:18:27.710 align:start position:0% and it you can write any program uh that that<00:18:25.679> supports<00:18:26.160> grpc<00:18:26.760> in<00:18:26.880> protobuf<00:18:27.480> which<00:18:27.600> are 00:18:27.710 --> 00:18:27.720 align:start position:0% that supports grpc in protobuf which are 00:18:27.720 --> 00:18:29.750 align:start position:0% that supports grpc in protobuf which are many<00:18:27.900> and<00:18:28.559> the<00:18:28.740> last<00:18:28.860> one<00:18:28.980> here<00:18:29.220> not<00:18:29.400> the<00:18:29.640> least 00:18:29.750 --> 00:18:29.760 align:start position:0% many and the last one here not the least 00:18:29.760 --> 00:18:33.110 align:start position:0% many and the last one here not the least subgras<00:18:30.419> through<00:18:30.660> graph<00:18:31.020> node<00:18:31.440> well<00:18:32.340> so<00:18:33.000> we're 00:18:33.110 --> 00:18:33.120 align:start position:0% subgras through graph node well so we're 00:18:33.120 --> 00:18:35.270 align:start position:0% subgras through graph node well so we're working<00:18:33.360> to<00:18:33.660> make<00:18:33.840> substreams<00:18:34.440> feed<00:18:34.740> directly 00:18:35.270 --> 00:18:35.280 align:start position:0% working to make substreams feed directly 00:18:35.280 --> 00:18:38.150 align:start position:0% working to make substreams feed directly into<00:18:35.520> into<00:18:36.059> graph<00:18:36.419> node<00:18:36.780> to<00:18:37.440> then<00:18:37.620> provide<00:18:37.980> the 00:18:38.150 --> 00:18:38.160 align:start position:0% into into graph node to then provide the 00:18:38.160 --> 00:18:39.590 align:start position:0% into into graph node to then provide the same<00:18:38.340> loading<00:18:38.760> experience<00:18:39.120> and<00:18:39.480> then 00:18:39.590 --> 00:18:39.600 align:start position:0% same loading experience and then 00:18:39.600 --> 00:18:41.210 align:start position:0% same loading experience and then querying<00:18:40.140> experience<00:18:40.500> that<00:18:40.679> you've<00:18:40.919> come<00:18:41.100> to 00:18:41.210 --> 00:18:41.220 align:start position:0% querying experience that you've come to 00:18:41.220 --> 00:18:43.190 align:start position:0% querying experience that you've come to know<00:18:41.460> and<00:18:42.179> love<00:18:42.360> and<00:18:42.600> you'll<00:18:42.840> be<00:18:42.960> able<00:18:43.080> to 00:18:43.190 --> 00:18:43.200 align:start position:0% know and love and you'll be able to 00:18:43.200 --> 00:18:45.169 align:start position:0% know and love and you'll be able to deploy<00:18:43.679> a<00:18:44.220> sub<00:18:44.340> grasp<00:18:44.760> this<00:18:44.940> time<00:18:45.000> not 00:18:45.169 --> 00:18:45.179 align:start position:0% deploy a sub grasp this time not 00:18:45.179 --> 00:18:47.090 align:start position:0% deploy a sub grasp this time not containing<00:18:45.600> assembly<00:18:46.020> script<00:18:46.320> but<00:18:46.679> a<00:18:46.860> stud 00:18:47.090 --> 00:18:47.100 align:start position:0% containing assembly script but a stud 00:18:47.100 --> 00:18:50.029 align:start position:0% containing assembly script but a stud streams<00:18:47.520> package<00:18:47.880> with<00:18:48.059> an<00:18:48.179> entry<00:18:48.480> point<00:18:49.039> and 00:18:50.029 --> 00:18:50.039 align:start position:0% streams package with an entry point and 00:18:50.039 --> 00:18:52.130 align:start position:0% streams package with an entry point and would<00:18:50.580> process<00:18:51.059> the<00:18:51.299> history<00:18:51.419> in<00:18:51.660> parallel 00:18:52.130 --> 00:18:52.140 align:start position:0% would process the history in parallel 00:18:52.140 --> 00:18:53.870 align:start position:0% would process the history in parallel and<00:18:52.679> load<00:18:52.919> that<00:18:53.039> in<00:18:53.160> your<00:18:53.280> database<00:18:53.580> in<00:18:53.700> Crazy 00:18:53.870 --> 00:18:53.880 align:start position:0% and load that in your database in Crazy 00:18:53.880 --> 00:18:56.690 align:start position:0% and load that in your database in Crazy speeds<00:18:54.419> so<00:18:54.960> stay<00:18:55.200> tuned<00:18:55.380> for<00:18:55.500> that<00:18:55.679> that's<00:18:56.520> not 00:18:56.690 --> 00:18:56.700 align:start position:0% speeds so stay tuned for that that's not 00:18:56.700 --> 00:18:59.150 align:start position:0% speeds so stay tuned for that that's not out<00:18:56.880> yet<00:18:57.000> but<00:18:57.299> you<00:18:57.480> know<00:18:57.660> soon<00:18:57.960> okay<00:18:58.559> and<00:18:58.980> so 00:18:59.150 --> 00:18:59.160 align:start position:0% out yet but you know soon okay and so 00:18:59.160 --> 00:19:01.789 align:start position:0% out yet but you know soon okay and so this<00:18:59.400> is<00:18:59.580> a<00:18:59.700> simple<00:19:00.059> example<00:19:00.539> in<00:19:00.720> Python 00:19:01.789 --> 00:19:01.799 align:start position:0% this is a simple example in Python 00:19:01.799 --> 00:19:03.529 align:start position:0% this is a simple example in Python it's<00:19:02.340> not<00:19:02.520> really<00:19:02.700> longer<00:19:03.059> than<00:19:03.179> that<00:19:03.360> you 00:19:03.529 --> 00:19:03.539 align:start position:0% it's not really longer than that you 00:19:03.539 --> 00:19:04.970 align:start position:0% it's not really longer than that you have<00:19:03.720> two<00:19:03.900> one<00:19:04.080> or<00:19:04.200> two<00:19:04.320> dependencies<00:19:04.740> like 00:19:04.970 --> 00:19:04.980 align:start position:0% have two one or two dependencies like 00:19:04.980 --> 00:19:07.070 align:start position:0% have two one or two dependencies like grpc<00:19:05.640> so<00:19:06.059> that<00:19:06.179> you<00:19:06.299> can<00:19:06.419> use<00:19:06.539> the<00:19:06.660> query<00:19:06.900> so 00:19:07.070 --> 00:19:07.080 align:start position:0% grpc so that you can use the query so 00:19:07.080 --> 00:19:10.010 align:start position:0% grpc so that you can use the query so we're<00:19:07.200> leveraging<00:19:07.559> a<00:19:07.799> lot<00:19:07.980> there<00:19:08.700> and<00:19:09.059> you<00:19:09.840> can 00:19:10.010 --> 00:19:10.020 align:start position:0% we're leveraging a lot there and you can 00:19:10.020 --> 00:19:13.010 align:start position:0% we're leveraging a lot there and you can uh<00:19:10.380> you<00:19:10.620> know<00:19:10.679> see<00:19:11.100> that<00:19:11.280> spkg<00:19:12.059> there<00:19:12.360> we<00:19:12.900> can 00:19:13.010 --> 00:19:13.020 align:start position:0% uh you know see that spkg there we can 00:19:13.020 --> 00:19:15.650 align:start position:0% uh you know see that spkg there we can use<00:19:13.260> that<00:19:13.620> to<00:19:13.919> code<00:19:14.160> gen<00:19:14.460> python<00:19:15.059> classes<00:19:15.480> and 00:19:15.650 --> 00:19:15.660 align:start position:0% use that to code gen python classes and 00:19:15.660 --> 00:19:17.930 align:start position:0% use that to code gen python classes and helpers<00:19:16.020> and<00:19:16.140> all<00:19:16.260> of<00:19:16.440> that<00:19:16.559> because<00:19:17.220> it<00:19:17.460> turns 00:19:17.930 --> 00:19:17.940 align:start position:0% helpers and all of that because it turns 00:19:17.940 --> 00:19:20.750 align:start position:0% helpers and all of that because it turns out<00:19:18.000> that<00:19:18.240> the<00:19:18.660> Manifest<00:19:19.080> through<00:19:19.980> the<00:19:20.160> spkg 00:19:20.750 --> 00:19:20.760 align:start position:0% out that the Manifest through the spkg 00:19:20.760 --> 00:19:22.909 align:start position:0% out that the Manifest through the spkg there<00:19:21.059> is<00:19:21.660> for<00:19:21.840> those<00:19:21.960> who<00:19:22.080> know<00:19:22.260> protobuf<00:19:22.799> is 00:19:22.909 --> 00:19:22.919 align:start position:0% there is for those who know protobuf is 00:19:22.919 --> 00:19:26.330 align:start position:0% there is for those who know protobuf is they<00:19:23.160> file<00:19:23.460> descriptor<00:19:24.179> set<00:19:24.360> it<00:19:24.960> contains<00:19:25.559> all 00:19:26.330 --> 00:19:26.340 align:start position:0% they file descriptor set it contains all 00:19:26.340 --> 00:19:28.310 align:start position:0% they file descriptor set it contains all of<00:19:26.460> the<00:19:26.820> things<00:19:27.000> all<00:19:27.660> the<00:19:27.840> protobuf 00:19:28.310 --> 00:19:28.320 align:start position:0% of the things all the protobuf 00:19:28.320 --> 00:19:30.650 align:start position:0% of the things all the protobuf definitions<00:19:28.799> so<00:19:29.280> the<00:19:29.460> spkg<00:19:30.059> also<00:19:30.360> contains 00:19:30.650 --> 00:19:30.660 align:start position:0% definitions so the spkg also contains 00:19:30.660 --> 00:19:33.169 align:start position:0% definitions so the spkg also contains all<00:19:30.840> the<00:19:31.020> wasm<00:19:31.559> code<00:19:31.799> the<00:19:32.460> module<00:19:32.760> graph 00:19:33.169 --> 00:19:33.179 align:start position:0% all the wasm code the module graph 00:19:33.179 --> 00:19:34.430 align:start position:0% all the wasm code the module graph information<00:19:33.360> you<00:19:33.780> know<00:19:33.900> the<00:19:34.080> dependencies 00:19:34.430 --> 00:19:34.440 align:start position:0% information you know the dependencies 00:19:34.440 --> 00:19:36.289 align:start position:0% information you know the dependencies the<00:19:34.679> inputs<00:19:35.039> and<00:19:35.100> all<00:19:35.280> that<00:19:35.400> and<00:19:35.940> even<00:19:36.000> some 00:19:36.289 --> 00:19:36.299 align:start position:0% the inputs and all that and even some 00:19:36.299 --> 00:19:38.510 align:start position:0% the inputs and all that and even some documentation<00:19:36.780> everything<00:19:37.200> is<00:19:37.380> needed<00:19:37.740> is<00:19:38.280> in 00:19:38.510 --> 00:19:38.520 align:start position:0% documentation everything is needed is in 00:19:38.520 --> 00:19:41.150 align:start position:0% documentation everything is needed is in there<00:19:38.700> so<00:19:39.059> you<00:19:39.539> can<00:19:39.660> pass<00:19:39.960> it<00:19:40.200> down<00:19:40.440> to<00:19:40.679> the<00:19:40.860> you 00:19:41.150 --> 00:19:41.160 align:start position:0% there so you can pass it down to the you 00:19:41.160 --> 00:19:43.010 align:start position:0% there so you can pass it down to the you know<00:19:41.340> modules<00:19:41.820> you<00:19:42.000> take<00:19:42.179> it<00:19:42.299> from<00:19:42.480> from<00:19:42.780> the 00:19:43.010 --> 00:19:43.020 align:start position:0% know modules you take it from from the 00:19:43.020 --> 00:19:45.110 align:start position:0% know modules you take it from from the disk<00:19:43.320> and<00:19:43.500> boom<00:19:44.280> you<00:19:44.460> send<00:19:44.580> the<00:19:44.700> request<00:19:44.940> to 00:19:45.110 --> 00:19:45.120 align:start position:0% disk and boom you send the request to 00:19:45.120 --> 00:19:47.029 align:start position:0% disk and boom you send the request to the<00:19:45.240> server<00:19:45.480> and<00:19:45.600> it's<00:19:45.720> running<00:19:45.960> so<00:19:46.559> you<00:19:46.919> can 00:19:47.029 --> 00:19:47.039 align:start position:0% the server and it's running so you can 00:19:47.039 --> 00:19:48.950 align:start position:0% the server and it's running so you can deploy<00:19:47.520> packages<00:19:48.120> also<00:19:48.419> very<00:19:48.600> easily<00:19:48.840> and 00:19:48.950 --> 00:19:48.960 align:start position:0% deploy packages also very easily and 00:19:48.960 --> 00:19:50.990 align:start position:0% deploy packages also very easily and consume<00:19:49.380> them<00:19:49.500> very<00:19:50.340> simply<00:19:50.640> this<00:19:50.880> way 00:19:50.990 --> 00:19:51.000 align:start position:0% consume them very simply this way 00:19:51.000 --> 00:19:52.549 align:start position:0% consume them very simply this way there's<00:19:51.299> a<00:19:51.480> few<00:19:51.600> Imports<00:19:52.020> we've<00:19:52.260> omitted 00:19:52.549 --> 00:19:52.559 align:start position:0% there's a few Imports we've omitted 00:19:52.559 --> 00:19:53.450 align:start position:0% there's a few Imports we've omitted there<00:19:52.679> but 00:19:53.450 --> 00:19:53.460 align:start position:0% there but 00:19:53.460 --> 00:19:56.690 align:start position:0% there but it's<00:19:54.059> simple<00:19:54.299> this<00:19:54.539> is<00:19:54.660> the<00:19:54.780> show<00:19:54.960> okay<00:19:55.799> and 00:19:56.690 --> 00:19:56.700 align:start position:0% it's simple this is the show okay and 00:19:56.700 --> 00:19:58.190 align:start position:0% it's simple this is the show okay and let's<00:19:56.940> look<00:19:57.120> at<00:19:57.299> a<00:19:57.419> simplified<00:19:57.780> data<00:19:58.140> model 00:19:58.190 --> 00:19:58.200 align:start position:0% let's look at a simplified data model 00:19:58.200 --> 00:20:00.289 align:start position:0% let's look at a simplified data model for<00:19:58.380> unionist<00:19:58.679> swap<00:19:58.919> V3<00:19:59.280> and<00:19:59.700> I'll<00:19:59.940> show<00:20:00.059> some 00:20:00.289 --> 00:20:00.299 align:start position:0% for unionist swap V3 and I'll show some 00:20:00.299 --> 00:20:02.330 align:start position:0% for unionist swap V3 and I'll show some code<00:20:00.419> making<00:20:00.600> use<00:20:00.780> of<00:20:00.960> it<00:20:01.080> okay<00:20:01.260> so<00:20:01.740> this<00:20:02.160> here 00:20:02.330 --> 00:20:02.340 align:start position:0% code making use of it okay so this here 00:20:02.340 --> 00:20:04.130 align:start position:0% code making use of it okay so this here the<00:20:02.580> pool<00:20:02.700> is<00:20:02.880> a<00:20:03.059> list<00:20:03.240> of<00:20:03.419> pool<00:20:03.600> this<00:20:04.020> is 00:20:04.130 --> 00:20:04.140 align:start position:0% the pool is a list of pool this is 00:20:04.140 --> 00:20:06.169 align:start position:0% the pool is a list of pool this is actually<00:20:04.260> what<00:20:04.500> gets<00:20:04.919> handed<00:20:05.400> off<00:20:05.520> from<00:20:05.760> you 00:20:06.169 --> 00:20:06.179 align:start position:0% actually what gets handed off from you 00:20:06.179 --> 00:20:08.390 align:start position:0% actually what gets handed off from you know<00:20:06.299> our<00:20:06.840> mapper<00:20:07.320> which<00:20:07.679> finds<00:20:08.100> the<00:20:08.280> pool 00:20:08.390 --> 00:20:08.400 align:start position:0% know our mapper which finds the pool 00:20:08.400 --> 00:20:10.970 align:start position:0% know our mapper which finds the pool that<00:20:08.640> were<00:20:08.820> created<00:20:09.179> down<00:20:09.840> to<00:20:10.080> the<00:20:10.320> store<00:20:10.679> pool 00:20:10.970 --> 00:20:10.980 align:start position:0% that were created down to the store pool 00:20:10.980 --> 00:20:13.190 align:start position:0% that were created down to the store pool which<00:20:11.280> we're<00:20:11.400> going<00:20:11.580> to<00:20:11.640> look<00:20:11.760> also<00:20:12.120> and<00:20:12.840> so<00:20:13.080> it 00:20:13.190 --> 00:20:13.200 align:start position:0% which we're going to look also and so it 00:20:13.200 --> 00:20:14.570 align:start position:0% which we're going to look also and so it has<00:20:13.440> a<00:20:13.559> list<00:20:13.679> of<00:20:13.799> tools<00:20:14.039> and<00:20:14.160> the<00:20:14.280> tools<00:20:14.460> you 00:20:14.570 --> 00:20:14.580 align:start position:0% has a list of tools and the tools you 00:20:14.580 --> 00:20:16.430 align:start position:0% has a list of tools and the tools you can<00:20:14.640> imagine<00:20:14.760> an<00:20:15.600> address<00:20:15.780> and<00:20:16.140> the<00:20:16.320> two 00:20:16.430 --> 00:20:16.440 align:start position:0% can imagine an address and the two 00:20:16.440 --> 00:20:17.750 align:start position:0% can imagine an address and the two tokens<00:20:16.740> that<00:20:16.919> are<00:20:17.039> concerned<00:20:17.340> here<00:20:17.460> and<00:20:17.640> we 00:20:17.750 --> 00:20:17.760 align:start position:0% tokens that are concerned here and we 00:20:17.760 --> 00:20:19.549 align:start position:0% tokens that are concerned here and we have<00:20:17.820> a<00:20:17.940> reference<00:20:18.179> to<00:20:18.360> the<00:20:18.480> Token<00:20:18.780> also<00:20:19.080> which 00:20:19.549 --> 00:20:19.559 align:start position:0% have a reference to the Token also which 00:20:19.559 --> 00:20:21.350 align:start position:0% have a reference to the Token also which is<00:20:19.799> going<00:20:20.039> to<00:20:20.100> be<00:20:20.220> very<00:20:20.280> useful<00:20:20.640> to<00:20:20.820> enrich<00:20:21.179> the 00:20:21.350 --> 00:20:21.360 align:start position:0% is going to be very useful to enrich the 00:20:21.360 --> 00:20:22.850 align:start position:0% is going to be very useful to enrich the data<00:20:21.539> down<00:20:21.660> so<00:20:21.780> we<00:20:21.960> will<00:20:22.020> have<00:20:22.140> the<00:20:22.260> decimals 00:20:22.850 --> 00:20:22.860 align:start position:0% data down so we will have the decimals 00:20:22.860 --> 00:20:24.770 align:start position:0% data down so we will have the decimals right<00:20:23.280> at<00:20:23.520> hand<00:20:23.700> like<00:20:24.000> we<00:20:24.240> won't<00:20:24.360> need<00:20:24.539> to<00:20:24.660> do 00:20:24.770 --> 00:20:24.780 align:start position:0% right at hand like we won't need to do 00:20:24.780 --> 00:20:26.270 align:start position:0% right at hand like we won't need to do much<00:20:24.900> loading<00:20:25.260> it's<00:20:25.380> going<00:20:25.620> to<00:20:25.740> be<00:20:25.860> very<00:20:26.100> very 00:20:26.270 --> 00:20:26.280 align:start position:0% much loading it's going to be very very 00:20:26.280 --> 00:20:28.789 align:start position:0% much loading it's going to be very very close<00:20:26.580> so<00:20:26.820> we<00:20:27.000> can<00:20:27.120> enrich<00:20:27.480> all<00:20:27.900> these<00:20:28.140> U<00:20:28.320> ins 00:20:28.789 --> 00:20:28.799 align:start position:0% close so we can enrich all these U ins 00:20:28.799 --> 00:20:32.210 align:start position:0% close so we can enrich all these U ins 250<00:20:29.160> 79<00:20:30.299> 000<00:20:30.419> and<00:20:31.140> you<00:20:31.559> know<00:20:31.679> put<00:20:31.860> the<00:20:32.039> the 00:20:32.210 --> 00:20:32.220 align:start position:0% 250 79 000 and you know put the the 00:20:32.220 --> 00:20:34.490 align:start position:0% 250 79 000 and you know put the the comma<00:20:32.520> where<00:20:32.640> it<00:20:32.760> belongs 00:20:34.490 --> 00:20:34.500 align:start position:0% comma where it belongs 00:20:34.500 --> 00:20:36.289 align:start position:0% comma where it belongs um so<00:20:35.039> let's<00:20:35.280> see<00:20:35.520> what<00:20:35.700> happens<00:20:35.880> in<00:20:36.179> the 00:20:36.289 --> 00:20:36.299 align:start position:0% um so let's see what happens in the 00:20:36.299 --> 00:20:38.330 align:start position:0% um so let's see what happens in the mappers<00:20:36.600> so<00:20:36.840> this<00:20:37.140> is<00:20:37.260> a<00:20:37.500> sample<00:20:37.799> rust<00:20:38.100> code 00:20:38.330 --> 00:20:38.340 align:start position:0% mappers so this is a sample rust code 00:20:38.340 --> 00:20:40.450 align:start position:0% mappers so this is a sample rust code raise<00:20:38.580> your<00:20:38.760> hand<00:20:38.880> if<00:20:39.000> you<00:20:39.120> love<00:20:39.240> rust 00:20:40.450 --> 00:20:40.460 align:start position:0% raise your hand if you love rust 00:20:40.460 --> 00:20:43.310 align:start position:0% raise your hand if you love rust where's<00:20:41.460> your<00:20:41.700> hand<00:20:41.820> if<00:20:42.059> you<00:20:42.179> no<00:20:42.480> rust<00:20:42.840> okay 00:20:43.310 --> 00:20:43.320 align:start position:0% where's your hand if you no rust okay 00:20:43.320 --> 00:20:44.510 align:start position:0% where's your hand if you no rust okay it's<00:20:43.679> very<00:20:43.799> simple<00:20:43.919> here<00:20:44.160> I'm<00:20:44.280> gonna<00:20:44.400> go 00:20:44.510 --> 00:20:44.520 align:start position:0% it's very simple here I'm gonna go 00:20:44.520 --> 00:20:46.010 align:start position:0% it's very simple here I'm gonna go through<00:20:44.700> you<00:20:45.059> have<00:20:45.179> the<00:20:45.299> map<00:20:45.480> pools<00:20:45.840> function 00:20:46.010 --> 00:20:46.020 align:start position:0% through you have the map pools function 00:20:46.020 --> 00:20:48.049 align:start position:0% through you have the map pools function corresponding<00:20:46.620> to<00:20:46.740> the<00:20:46.860> Manifest<00:20:47.340> there<00:20:47.580> has 00:20:48.049 --> 00:20:48.059 align:start position:0% corresponding to the Manifest there has 00:20:48.059 --> 00:20:50.510 align:start position:0% corresponding to the Manifest there has one<00:20:48.419> input<00:20:48.840> the<00:20:49.080> block<00:20:49.320> this<00:20:49.740> is<00:20:49.919> the<00:20:50.400> fire 00:20:50.510 --> 00:20:50.520 align:start position:0% one input the block this is the fire 00:20:50.520 --> 00:20:53.029 align:start position:0% one input the block this is the fire hose<00:20:50.820> block<00:20:51.059> with<00:20:51.299> all<00:20:51.600> transactions<00:20:52.380> all 00:20:53.029 --> 00:20:53.039 align:start position:0% hose block with all transactions all 00:20:53.039 --> 00:20:54.890 align:start position:0% hose block with all transactions all logs<00:20:53.460> All<00:20:53.580> State<00:20:53.760> chains<00:20:54.179> you<00:20:54.299> can<00:20:54.419> craft<00:20:54.600> your 00:20:54.890 --> 00:20:54.900 align:start position:0% logs All State chains you can craft your 00:20:54.900 --> 00:20:56.930 align:start position:0% logs All State chains you can craft your own<00:20:55.020> triggers<00:20:55.440> in<00:20:55.679> there<00:20:55.860> as<00:20:56.280> you<00:20:56.400> wish<00:20:56.580> but<00:20:56.760> we 00:20:56.930 --> 00:20:56.940 align:start position:0% own triggers in there as you wish but we 00:20:56.940 --> 00:20:58.850 align:start position:0% own triggers in there as you wish but we have<00:20:57.059> a<00:20:57.240> simple<00:20:57.539> Voyager<00:20:58.080> and<00:20:58.200> see<00:20:58.320> that<00:20:58.500> that 00:20:58.850 --> 00:20:58.860 align:start position:0% have a simple Voyager and see that that 00:20:58.860 --> 00:21:01.490 align:start position:0% have a simple Voyager and see that that line<00:20:59.100> there<00:20:59.340> blocks<00:20:59.940> events<00:21:00.299> you<00:21:00.960> have<00:21:01.140> a 00:21:01.490 --> 00:21:01.500 align:start position:0% line there blocks events you have a 00:21:01.500 --> 00:21:03.770 align:start position:0% line there blocks events you have a thing<00:21:01.679> that<00:21:01.860> goes<00:21:02.280> through<00:21:02.460> transactions<00:21:03.240> and 00:21:03.770 --> 00:21:03.780 align:start position:0% thing that goes through transactions and 00:21:03.780 --> 00:21:05.570 align:start position:0% thing that goes through transactions and it's<00:21:03.960> going<00:21:04.140> to<00:21:04.260> trig<00:21:04.440> on<00:21:04.620> pool<00:21:04.980> created<00:21:05.340> and 00:21:05.570 --> 00:21:05.580 align:start position:0% it's going to trig on pool created and 00:21:05.580 --> 00:21:07.190 align:start position:0% it's going to trig on pool created and that<00:21:05.700> pool<00:21:05.880> created<00:21:06.240> object<00:21:06.480> in<00:21:06.660> Rust<00:21:06.960> was 00:21:07.190 --> 00:21:07.200 align:start position:0% that pool created object in Rust was 00:21:07.200 --> 00:21:10.490 align:start position:0% that pool created object in Rust was actually<00:21:07.440> code<00:21:07.860> gen<00:21:08.100> from<00:21:08.640> the<00:21:08.820> Json<00:21:09.059> API<00:21:09.720> so 00:21:10.490 --> 00:21:10.500 align:start position:0% actually code gen from the Json API so 00:21:10.500 --> 00:21:11.990 align:start position:0% actually code gen from the Json API so you<00:21:10.799> can<00:21:10.919> just<00:21:11.039> give<00:21:11.220> the<00:21:11.340> instruction<00:21:11.520> and 00:21:11.990 --> 00:21:12.000 align:start position:0% you can just give the instruction and 00:21:12.000 --> 00:21:13.610 align:start position:0% you can just give the instruction and we're<00:21:12.120> going<00:21:12.240> to<00:21:12.299> filter<00:21:12.480> it<00:21:12.780> for<00:21:12.960> only<00:21:13.080> the<00:21:13.260> V3 00:21:13.610 --> 00:21:13.620 align:start position:0% we're going to filter it for only the V3 00:21:13.620 --> 00:21:15.350 align:start position:0% we're going to filter it for only the V3 swap<00:21:14.160> Factory<00:21:14.340> and<00:21:14.880> then<00:21:15.000> that<00:21:15.120> beautiful 00:21:15.350 --> 00:21:15.360 align:start position:0% swap Factory and then that beautiful 00:21:15.360 --> 00:21:18.710 align:start position:0% swap Factory and then that beautiful filter<00:21:15.660> map<00:21:15.900> will<00:21:16.140> give<00:21:16.320> us<00:21:16.500> the<00:21:16.980> log<00:21:17.160> okay<00:21:18.120> and 00:21:18.710 --> 00:21:18.720 align:start position:0% filter map will give us the log okay and 00:21:18.720 --> 00:21:20.510 align:start position:0% filter map will give us the log okay and then<00:21:18.840> we'll<00:21:19.020> we'll<00:21:19.260> output<00:21:19.679> we're<00:21:20.220> going<00:21:20.400> to 00:21:20.510 --> 00:21:20.520 align:start position:0% then we'll we'll output we're going to 00:21:20.520 --> 00:21:22.789 align:start position:0% then we'll we'll output we're going to collect<00:21:21.000> some<00:21:21.539> of<00:21:21.660> these<00:21:21.840> things<00:21:22.020> into<00:21:22.440> one 00:21:22.789 --> 00:21:22.799 align:start position:0% collect some of these things into one 00:21:22.799 --> 00:21:24.470 align:start position:0% collect some of these things into one list<00:21:23.039> of<00:21:23.340> pools<00:21:23.700> and<00:21:23.820> it's<00:21:24.000> assigned<00:21:24.299> to<00:21:24.360> the 00:21:24.470 --> 00:21:24.480 align:start position:0% list of pools and it's assigned to the 00:21:24.480 --> 00:21:26.870 align:start position:0% list of pools and it's assigned to the pools<00:21:24.840> object<00:21:25.140> there<00:21:25.380> and<00:21:26.220> and<00:21:26.400> notice<00:21:26.760> that 00:21:26.870 --> 00:21:26.880 align:start position:0% pools object there and and notice that 00:21:26.880 --> 00:21:29.149 align:start position:0% pools object there and and notice that little<00:21:27.000> thing<00:21:27.240> here<00:21:27.419> this<00:21:28.200> is<00:21:28.320> the<00:21:28.380> RPC<00:21:28.919> create 00:21:29.149 --> 00:21:29.159 align:start position:0% little thing here this is the RPC create 00:21:29.159 --> 00:21:31.190 align:start position:0% little thing here this is the RPC create unit<00:21:29.400> Swap<00:21:29.700> tokensing<00:21:30.179> this<00:21:30.659> actually<00:21:30.840> hits 00:21:31.190 --> 00:21:31.200 align:start position:0% unit Swap tokensing this actually hits 00:21:31.200 --> 00:21:33.649 align:start position:0% unit Swap tokensing this actually hits you<00:21:31.799> know<00:21:31.980> an<00:21:32.159> e-call<00:21:32.640> on<00:21:32.880> a<00:21:33.059> node<00:21:33.240> behind 00:21:33.649 --> 00:21:33.659 align:start position:0% you know an e-call on a node behind 00:21:33.659 --> 00:21:36.230 align:start position:0% you know an e-call on a node behind similar<00:21:34.200> to<00:21:34.320> what<00:21:34.440> we<00:21:34.559> have<00:21:34.679> in<00:21:34.740> sub<00:21:34.919> graphs 00:21:36.230 --> 00:21:36.240 align:start position:0% similar to what we have in sub graphs 00:21:36.240 --> 00:21:38.330 align:start position:0% similar to what we have in sub graphs that's<00:21:36.600> actually<00:21:36.780> very<00:21:37.080> important<00:21:37.380> it<00:21:37.980> means 00:21:38.330 --> 00:21:38.340 align:start position:0% that's actually very important it means 00:21:38.340 --> 00:21:41.149 align:start position:0% that's actually very important it means that<00:21:38.520> once<00:21:38.940> we've<00:21:39.179> processed<00:21:39.840> this<00:21:40.740> layer 00:21:41.149 --> 00:21:41.159 align:start position:0% that once we've processed this layer 00:21:41.159 --> 00:21:43.210 align:start position:0% that once we've processed this layer once<00:21:42.059> and<00:21:42.240> we've<00:21:42.480> done<00:21:42.600> it<00:21:42.720> for<00:21:42.840> the<00:21:43.020> history 00:21:43.210 --> 00:21:43.220 align:start position:0% once and we've done it for the history 00:21:43.220 --> 00:21:46.549 align:start position:0% once and we've done it for the history it<00:21:44.220> can<00:21:44.340> be<00:21:44.520> cached<00:21:45.000> very<00:21:45.360> efficiently<00:21:46.020> so 00:21:46.549 --> 00:21:46.559 align:start position:0% it can be cached very efficiently so 00:21:46.559 --> 00:21:48.950 align:start position:0% it can be cached very efficiently so anyone<00:21:46.980> relying<00:21:47.520> on<00:21:47.700> that<00:21:47.940> thing<00:21:48.120> will<00:21:48.720> never 00:21:48.950 --> 00:21:48.960 align:start position:0% anyone relying on that thing will never 00:21:48.960 --> 00:21:51.649 align:start position:0% anyone relying on that thing will never need<00:21:49.320> to<00:21:49.500> reprocess<00:21:50.039> it<00:21:50.340> again<00:21:50.580> you<00:21:51.360> can<00:21:51.480> give 00:21:51.649 --> 00:21:51.659 align:start position:0% need to reprocess it again you can give 00:21:51.659 --> 00:21:53.870 align:start position:0% need to reprocess it again you can give the<00:21:51.900> package<00:21:52.500> to<00:21:52.679> someone<00:21:52.919> and<00:21:53.580> they<00:21:53.760> can 00:21:53.870 --> 00:21:53.880 align:start position:0% the package to someone and they can 00:21:53.880 --> 00:21:55.909 align:start position:0% the package to someone and they can access<00:21:54.120> the<00:21:54.539> stores<00:21:54.720> that's<00:21:55.200> been<00:21:55.380> cached<00:21:55.799> by 00:21:55.909 --> 00:21:55.919 align:start position:0% access the stores that's been cached by 00:21:55.919 --> 00:21:58.070 align:start position:0% access the stores that's been cached by other<00:21:56.039> people<00:21:56.360> immediately<00:21:57.360> so<00:21:57.659> you<00:21:57.900> could<00:21:57.960> go 00:21:58.070 --> 00:21:58.080 align:start position:0% other people immediately so you could go 00:21:58.080 --> 00:22:00.890 align:start position:0% other people immediately so you could go to<00:21:58.140> block<00:21:58.320> 50<00:21:58.620> million<00:21:59.100> and<00:21:59.580> you'll<00:22:00.000> have<00:22:00.360> the 00:22:00.890 --> 00:22:00.900 align:start position:0% to block 50 million and you'll have the 00:22:00.900 --> 00:22:03.049 align:start position:0% to block 50 million and you'll have the list<00:22:01.080> of<00:22:01.320> all<00:22:01.620> pool<00:22:01.860> created<00:22:02.340> that<00:22:02.820> you<00:22:02.940> can 00:22:03.049 --> 00:22:03.059 align:start position:0% list of all pool created that you can 00:22:03.059 --> 00:22:05.029 align:start position:0% list of all pool created that you can query<00:22:03.360> super<00:22:03.659> fast<00:22:03.900> you<00:22:04.320> can<00:22:04.440> depend<00:22:04.740> on<00:22:04.919> it 00:22:05.029 --> 00:22:05.039 align:start position:0% query super fast you can depend on it 00:22:05.039 --> 00:22:08.330 align:start position:0% query super fast you can depend on it also<00:22:05.340> so<00:22:05.820> I<00:22:05.940> think<00:22:06.120> that's<00:22:06.780> pretty<00:22:07.440> cool 00:22:08.330 --> 00:22:08.340 align:start position:0% also so I think that's pretty cool 00:22:08.340 --> 00:22:11.270 align:start position:0% also so I think that's pretty cool and<00:22:09.120> here<00:22:09.299> that's<00:22:09.480> the<00:22:09.720> store<00:22:09.840> modules<00:22:10.799> the 00:22:11.270 --> 00:22:11.280 align:start position:0% and here that's the store modules the 00:22:11.280 --> 00:22:12.770 align:start position:0% and here that's the store modules the store<00:22:11.400> module<00:22:11.760> is<00:22:11.940> pretty<00:22:12.120> simple<00:22:12.299> here<00:22:12.600> it 00:22:12.770 --> 00:22:12.780 align:start position:0% store module is pretty simple here it 00:22:12.780 --> 00:22:15.169 align:start position:0% store module is pretty simple here it receives<00:22:13.140> C<00:22:13.380> the<00:22:13.860> pools<00:22:14.280> from<00:22:14.460> the<00:22:14.640> output<00:22:14.940> of 00:22:15.169 --> 00:22:15.179 align:start position:0% receives C the pools from the output of 00:22:15.179 --> 00:22:17.690 align:start position:0% receives C the pools from the output of the<00:22:15.360> prior<00:22:15.600> module<00:22:16.080> and<00:22:16.740> it<00:22:16.860> does<00:22:17.100> it<00:22:17.400> Loops 00:22:17.690 --> 00:22:17.700 align:start position:0% the prior module and it does it Loops 00:22:17.700 --> 00:22:19.610 align:start position:0% the prior module and it does it Loops through<00:22:17.820> the<00:22:17.940> little<00:22:18.059> pools<00:22:18.480> there<00:22:18.720> and<00:22:18.960> calls 00:22:19.610 --> 00:22:19.620 align:start position:0% through the little pools there and calls 00:22:19.620 --> 00:22:21.770 align:start position:0% through the little pools there and calls output<00:22:19.919> set<00:22:20.280> and<00:22:20.760> see<00:22:20.940> the<00:22:21.120> key<00:22:21.240> there<00:22:21.419> is<00:22:21.600> pool 00:22:21.770 --> 00:22:21.780 align:start position:0% output set and see the key there is pool 00:22:21.780 --> 00:22:24.710 align:start position:0% output set and see the key there is pool colon<00:22:22.320> the<00:22:23.100> address<00:22:23.280> is<00:22:24.000> going<00:22:24.240> to<00:22:24.299> store<00:22:24.419> the 00:22:24.710 --> 00:22:24.720 align:start position:0% colon the address is going to store the 00:22:24.720 --> 00:22:26.950 align:start position:0% colon the address is going to store the Proto<00:22:25.140> buff<00:22:25.320> encoded<00:22:25.799> stuff<00:22:26.220> of<00:22:26.460> the<00:22:26.580> pool 00:22:26.950 --> 00:22:26.960 align:start position:0% Proto buff encoded stuff of the pool 00:22:26.960 --> 00:22:29.930 align:start position:0% Proto buff encoded stuff of the pool with<00:22:27.960> the<00:22:28.440> token<00:22:28.799> decimals<00:22:29.340> for<00:22:29.460> both<00:22:29.640> right 00:22:29.930 --> 00:22:29.940 align:start position:0% with the token decimals for both right 00:22:29.940 --> 00:22:32.450 align:start position:0% with the token decimals for both right did<00:22:30.659> I<00:22:30.840> say<00:22:30.960> that<00:22:31.200> to<00:22:31.559> be<00:22:31.740> constrained<00:22:32.159> so<00:22:32.280> the 00:22:32.450 --> 00:22:32.460 align:start position:0% did I say that to be constrained so the 00:22:32.460 --> 00:22:35.510 align:start position:0% did I say that to be constrained so the store<00:22:32.640> here<00:22:32.880> is<00:22:33.059> constrained<00:22:33.659> in<00:22:34.500> two<00:22:34.679> ways<00:22:35.100> in 00:22:35.510 --> 00:22:35.520 align:start position:0% store here is constrained in two ways in 00:22:35.520 --> 00:22:37.970 align:start position:0% store here is constrained in two ways in order<00:22:35.640> to<00:22:35.940> preserve<00:22:36.620> parallelized<00:22:37.620> ability 00:22:37.970 --> 00:22:37.980 align:start position:0% order to preserve parallelized ability 00:22:37.980 --> 00:22:41.149 align:start position:0% order to preserve parallelized ability the<00:22:38.880> stores<00:22:39.179> are<00:22:39.539> right<00:22:40.020> only<00:22:40.320> you<00:22:40.860> cannot 00:22:41.149 --> 00:22:41.159 align:start position:0% the stores are right only you cannot 00:22:41.159 --> 00:22:42.649 align:start position:0% the stores are right only you cannot read<00:22:41.400> your<00:22:41.640> rights<00:22:42.000> otherwise<00:22:42.360> that<00:22:42.480> would 00:22:42.649 --> 00:22:42.659 align:start position:0% read your rights otherwise that would 00:22:42.659 --> 00:22:44.930 align:start position:0% read your rights otherwise that would make<00:22:42.840> some<00:22:43.020> potentially<00:22:43.440> cyclic<00:22:43.860> and<00:22:44.700> they 00:22:44.930 --> 00:22:44.940 align:start position:0% make some potentially cyclic and they 00:22:44.940 --> 00:22:47.330 align:start position:0% make some potentially cyclic and they expose<00:22:45.240> only<00:22:45.419> the<00:22:45.659> function<00:22:46.020> defined<00:22:46.919> by<00:22:47.159> the 00:22:47.330 --> 00:22:47.340 align:start position:0% expose only the function defined by the 00:22:47.340 --> 00:22:49.909 align:start position:0% expose only the function defined by the update<00:22:47.640> policy<00:22:48.059> in<00:22:48.179> this<00:22:48.299> case<00:22:48.419> it's<00:22:48.659> set<00:22:49.380> so 00:22:49.909 --> 00:22:49.919 align:start position:0% update policy in this case it's set so 00:22:49.919 --> 00:22:51.230 align:start position:0% update policy in this case it's set so let's<00:22:50.159> see<00:22:50.340> what<00:22:50.460> happens 00:22:51.230 --> 00:22:51.240 align:start position:0% let's see what happens 00:22:51.240 --> 00:22:53.810 align:start position:0% let's see what happens if<00:22:51.720> we<00:22:51.840> run<00:22:52.020> things<00:22:52.380> in<00:22:52.799> parallel 00:22:53.810 --> 00:22:53.820 align:start position:0% if we run things in parallel 00:22:53.820 --> 00:22:56.090 align:start position:0% if we run things in parallel so<00:22:54.179> here<00:22:54.360> we<00:22:54.480> have<00:22:54.600> two<00:22:54.840> jobs<00:22:55.020> covering<00:22:55.620> two 00:22:56.090 --> 00:22:56.100 align:start position:0% so here we have two jobs covering two 00:22:56.100 --> 00:22:57.409 align:start position:0% so here we have two jobs covering two segments<00:22:56.580> of<00:22:56.700> the<00:22:56.820> chain<00:22:56.940> you<00:22:57.120> know<00:22:57.179> one 00:22:57.409 --> 00:22:57.419 align:start position:0% segments of the chain you know one 00:22:57.419 --> 00:23:00.350 align:start position:0% segments of the chain you know one million<00:22:57.780> block<00:22:57.960> each<00:22:58.320> and<00:22:59.220> to<00:22:59.580> see<00:22:59.820> those<00:23:00.240> ugly 00:23:00.350 --> 00:23:00.360 align:start position:0% million block each and to see those ugly 00:23:00.360 --> 00:23:02.029 align:start position:0% million block each and to see those ugly arrows<00:23:00.720> there<00:23:00.900> they<00:23:01.260> correspond<00:23:01.559> to<00:23:01.679> a<00:23:01.919> pool 00:23:02.029 --> 00:23:02.039 align:start position:0% arrows there they correspond to a pool 00:23:02.039 --> 00:23:03.470 align:start position:0% arrows there they correspond to a pool created<00:23:02.520> event 00:23:03.470 --> 00:23:03.480 align:start position:0% created event 00:23:03.480 --> 00:23:05.029 align:start position:0% created event and<00:23:03.840> so<00:23:03.900> in<00:23:04.080> our<00:23:04.200> code<00:23:04.380> you've<00:23:04.559> seen<00:23:04.740> we<00:23:04.919> would 00:23:05.029 --> 00:23:05.039 align:start position:0% and so in our code you've seen we would 00:23:05.039 --> 00:23:08.450 align:start position:0% and so in our code you've seen we would write<00:23:05.340> a<00:23:05.640> key<00:23:05.820> for<00:23:06.299> each<00:23:06.539> of<00:23:06.720> them<00:23:06.960> and<00:23:07.860> uh<00:23:08.100> so 00:23:08.450 --> 00:23:08.460 align:start position:0% write a key for each of them and uh so 00:23:08.460 --> 00:23:10.549 align:start position:0% write a key for each of them and uh so in<00:23:08.700> the<00:23:08.940> first<00:23:09.120> partial<00:23:09.780> run<00:23:09.960> we'd<00:23:10.260> have<00:23:10.440> a 00:23:10.549 --> 00:23:10.559 align:start position:0% in the first partial run we'd have a 00:23:10.559 --> 00:23:12.350 align:start position:0% in the first partial run we'd have a what<00:23:10.679> we<00:23:10.799> call<00:23:10.919> a<00:23:11.100> partial<00:23:11.400> store<00:23:11.700> with<00:23:12.179> four 00:23:12.350 --> 00:23:12.360 align:start position:0% what we call a partial store with four 00:23:12.360 --> 00:23:14.510 align:start position:0% what we call a partial store with four keys<00:23:12.720> and<00:23:12.840> the<00:23:12.960> next<00:23:13.020> one<00:23:13.140> we<00:23:13.320> have<00:23:13.500> two<00:23:13.679> keys 00:23:14.510 --> 00:23:14.520 align:start position:0% keys and the next one we have two keys 00:23:14.520 --> 00:23:17.350 align:start position:0% keys and the next one we have two keys and<00:23:15.480> so<00:23:15.780> when<00:23:15.900> we<00:23:16.080> run<00:23:16.260> the<00:23:16.500> merge<00:23:16.860> operation 00:23:17.350 --> 00:23:17.360 align:start position:0% and so when we run the merge operation 00:23:17.360 --> 00:23:20.510 align:start position:0% and so when we run the merge operation we<00:23:18.360> would<00:23:18.480> apply<00:23:18.960> the<00:23:19.260> set<00:23:19.740> merge<00:23:20.159> policy 00:23:20.510 --> 00:23:20.520 align:start position:0% we would apply the set merge policy 00:23:20.520 --> 00:23:21.950 align:start position:0% we would apply the set merge policy which<00:23:20.820> says<00:23:21.179> basically<00:23:21.480> if<00:23:21.539> you<00:23:21.659> take<00:23:21.780> one 00:23:21.950 --> 00:23:21.960 align:start position:0% which says basically if you take one 00:23:21.960 --> 00:23:24.350 align:start position:0% which says basically if you take one store<00:23:22.140> take<00:23:22.440> the<00:23:22.559> other<00:23:22.679> store<00:23:23.120> cycle<00:23:24.120> through 00:23:24.350 --> 00:23:24.360 align:start position:0% store take the other store cycle through 00:23:24.360 --> 00:23:26.570 align:start position:0% store take the other store cycle through keys<00:23:24.720> and<00:23:24.840> the<00:23:25.020> last<00:23:25.080> key<00:23:25.260> wins<00:23:25.740> if<00:23:26.340> you<00:23:26.400> do 00:23:26.570 --> 00:23:26.580 align:start position:0% keys and the last key wins if you do 00:23:26.580 --> 00:23:29.029 align:start position:0% keys and the last key wins if you do that<00:23:26.700> you<00:23:26.940> can<00:23:27.059> paralyze<00:23:27.659> endlessly<00:23:28.559> so<00:23:28.799> we'd 00:23:29.029 --> 00:23:29.039 align:start position:0% that you can paralyze endlessly so we'd 00:23:29.039 --> 00:23:31.549 align:start position:0% that you can paralyze endlessly so we'd have<00:23:29.280> here<00:23:29.700> a<00:23:30.299> complete<00:23:30.600> store<00:23:30.780> with<00:23:31.020> six<00:23:31.200> keys 00:23:31.549 --> 00:23:31.559 align:start position:0% have here a complete store with six keys 00:23:31.559 --> 00:23:33.770 align:start position:0% have here a complete store with six keys and<00:23:32.039> now<00:23:32.220> at<00:23:32.460> that<00:23:32.640> place<00:23:32.760> we<00:23:33.059> have<00:23:33.179> a<00:23:33.360> snapshot 00:23:33.770 --> 00:23:33.780 align:start position:0% and now at that place we have a snapshot 00:23:33.780 --> 00:23:36.350 align:start position:0% and now at that place we have a snapshot we<00:23:34.380> can<00:23:34.500> have<00:23:34.620> periodic<00:23:35.220> snapshots<00:23:35.760> and<00:23:36.059> so<00:23:36.179> if 00:23:36.350 --> 00:23:36.360 align:start position:0% we can have periodic snapshots and so if 00:23:36.360 --> 00:23:38.210 align:start position:0% we can have periodic snapshots and so if you<00:23:36.480> want<00:23:36.600> to<00:23:36.720> go<00:23:36.900> and<00:23:37.020> explore<00:23:37.500> the<00:23:37.740> chain<00:23:37.919> at 00:23:38.210 --> 00:23:38.220 align:start position:0% you want to go and explore the chain at 00:23:38.220 --> 00:23:39.950 align:start position:0% you want to go and explore the chain at any<00:23:38.340> point<00:23:38.520> in<00:23:38.700> time<00:23:38.880> you<00:23:39.360> have<00:23:39.539> a<00:23:39.659> snapshot 00:23:39.950 --> 00:23:39.960 align:start position:0% any point in time you have a snapshot 00:23:39.960 --> 00:23:42.350 align:start position:0% any point in time you have a snapshot plus<00:23:40.260> a<00:23:40.440> little<00:23:40.559> partial<00:23:40.980> you<00:23:41.760> can<00:23:41.880> have<00:23:42.120> the 00:23:42.350 --> 00:23:42.360 align:start position:0% plus a little partial you can have the 00:23:42.360 --> 00:23:44.930 align:start position:0% plus a little partial you can have the state<00:23:42.600> synced<00:23:43.200> at<00:23:43.620> any<00:23:43.740> block<00:23:43.980> height 00:23:44.930 --> 00:23:44.940 align:start position:0% state synced at any block height 00:23:44.940 --> 00:23:48.890 align:start position:0% state synced at any block height so<00:23:45.960> so<00:23:46.020> this<00:23:46.679> one<00:23:46.860> you<00:23:47.520> know<00:23:47.640> has<00:23:48.179> the<00:23:48.480> last<00:23:48.659> key 00:23:48.890 --> 00:23:48.900 align:start position:0% so so this one you know has the last key 00:23:48.900 --> 00:23:50.270 align:start position:0% so so this one you know has the last key win<00:23:49.140> policy<00:23:49.500> but<00:23:49.620> you<00:23:49.740> have<00:23:49.860> a<00:23:49.919> few<00:23:50.039> others 00:23:50.270 --> 00:23:50.280 align:start position:0% win policy but you have a few others 00:23:50.280 --> 00:23:53.090 align:start position:0% win policy but you have a few others like<00:23:50.400> min<00:23:50.760> max<00:23:51.120> ad<00:23:51.960> and<00:23:52.500> another<00:23:52.679> one<00:23:52.919> like 00:23:53.090 --> 00:23:53.100 align:start position:0% like min max ad and another one like 00:23:53.100 --> 00:23:55.190 align:start position:0% like min max ad and another one like first<00:23:53.340> key<00:23:53.580> wins<00:23:53.940> so<00:23:54.059> if<00:23:54.120> you<00:23:54.240> merge<00:23:54.480> them<00:23:54.659> you 00:23:55.190 --> 00:23:55.200 align:start position:0% first key wins so if you merge them you 00:23:55.200 --> 00:23:57.649 align:start position:0% first key wins so if you merge them you have<00:23:55.440> set<00:23:55.679> if<00:23:55.919> not<00:23:56.159> exist<00:23:56.580> and<00:23:56.820> then<00:23:57.000> that<00:23:57.299> that 00:23:57.649 --> 00:23:57.659 align:start position:0% have set if not exist and then that that 00:23:57.659 --> 00:23:59.149 align:start position:0% have set if not exist and then that that allows<00:23:58.380> us<00:23:58.500> to<00:23:58.679> build<00:23:58.860> different 00:23:59.149 --> 00:23:59.159 align:start position:0% allows us to build different 00:23:59.159 --> 00:24:01.310 align:start position:0% allows us to build different aggregations<00:23:59.820> right<00:24:00.299> you'd<00:24:01.020> like<00:24:01.140> to<00:24:01.260> see 00:24:01.310 --> 00:24:01.320 align:start position:0% aggregations right you'd like to see 00:24:01.320 --> 00:24:02.690 align:start position:0% aggregations right you'd like to see that<00:24:01.500> running<00:24:01.620> live 00:24:02.690 --> 00:24:02.700 align:start position:0% that running live 00:24:02.700 --> 00:24:04.130 align:start position:0% that running live every<00:24:03.000> few<00:24:03.240> minutes<00:24:03.360> now<00:24:03.600> I<00:24:03.780> need<00:24:03.900> to<00:24:04.020> bring 00:24:04.130 --> 00:24:04.140 align:start position:0% every few minutes now I need to bring 00:24:04.140 --> 00:24:07.130 align:start position:0% every few minutes now I need to bring that<00:24:04.380> other<00:24:04.559> window<00:24:04.799> up<00:24:05.220> so<00:24:06.120> you<00:24:06.659> see<00:24:06.900> that 00:24:07.130 --> 00:24:07.140 align:start position:0% that other window up so you see that 00:24:07.140 --> 00:24:10.070 align:start position:0% that other window up so you see that okay<00:24:07.860> that's<00:24:08.100> good<00:24:08.280> enough<00:24:08.460> huh<00:24:08.940> okay<00:24:09.299> so 00:24:10.070 --> 00:24:10.080 align:start position:0% okay that's good enough huh okay so 00:24:10.080 --> 00:24:12.890 align:start position:0% okay that's good enough huh okay so let's<00:24:10.679> imagine<00:24:11.039> we<00:24:11.520> want<00:24:11.700> to 00:24:12.890 --> 00:24:12.900 align:start position:0% let's imagine we want to 00:24:12.900 --> 00:24:15.830 align:start position:0% let's imagine we want to see<00:24:13.440> that<00:24:13.679> pool<00:24:14.159> pools<00:24:14.820> created<00:24:15.120> thing<00:24:15.480> okay 00:24:15.830 --> 00:24:15.840 align:start position:0% see that pool pools created thing okay 00:24:15.840 --> 00:24:19.250 align:start position:0% see that pool pools created thing okay do<00:24:16.080> you<00:24:16.200> see<00:24:16.320> that<00:24:16.440> I<00:24:17.039> want<00:24:17.220> to<00:24:17.340> see<00:24:17.580> the<00:24:18.240> output 00:24:19.250 --> 00:24:19.260 align:start position:0% do you see that I want to see the output 00:24:19.260 --> 00:24:20.990 align:start position:0% do you see that I want to see the output I'm<00:24:19.679> going<00:24:19.860> to<00:24:19.919> run<00:24:20.039> that<00:24:20.280> I<00:24:20.580> hope<00:24:20.760> everything 00:24:20.990 --> 00:24:21.000 align:start position:0% I'm going to run that I hope everything 00:24:21.000 --> 00:24:23.149 align:start position:0% I'm going to run that I hope everything is<00:24:21.240> good<00:24:21.900> you<00:24:22.320> know<00:24:22.380> the<00:24:22.500> demo<00:24:22.740> of<00:24:22.799> gods<00:24:23.100> are 00:24:23.149 --> 00:24:23.159 align:start position:0% is good you know the demo of gods are 00:24:23.159 --> 00:24:24.409 align:start position:0% is good you know the demo of gods are connecting 00:24:24.409 --> 00:24:24.419 align:start position:0% connecting 00:24:24.419 --> 00:24:26.690 align:start position:0% connecting okay<00:24:24.960> okay<00:24:25.200> whoa<00:24:25.620> not<00:24:25.799> too<00:24:25.980> fast 00:24:26.690 --> 00:24:26.700 align:start position:0% okay okay whoa not too fast 00:24:26.700 --> 00:24:29.450 align:start position:0% okay okay whoa not too fast so<00:24:27.240> this<00:24:27.419> is<00:24:27.659> going<00:24:28.080> through<00:24:28.380> uh<00:24:29.039> starting<00:24:29.220> at 00:24:29.450 --> 00:24:29.460 align:start position:0% so this is going through uh starting at 00:24:29.460 --> 00:24:32.029 align:start position:0% so this is going through uh starting at the<00:24:29.580> beginning<00:24:29.700> and<00:24:30.419> we<00:24:30.659> have<00:24:30.900> there<00:24:31.260> a<00:24:31.860> pool 00:24:32.029 --> 00:24:32.039 align:start position:0% the beginning and we have there a pool 00:24:32.039 --> 00:24:33.950 align:start position:0% the beginning and we have there a pool credit<00:24:32.280> event<00:24:32.580> and<00:24:33.000> see<00:24:33.179> that<00:24:33.360> we<00:24:33.840> have 00:24:33.950 --> 00:24:33.960 align:start position:0% credit event and see that we have 00:24:33.960 --> 00:24:35.270 align:start position:0% credit event and see that we have everything<00:24:34.140> decoded<00:24:34.740> because<00:24:34.860> it's<00:24:35.100> the 00:24:35.270 --> 00:24:35.280 align:start position:0% everything decoded because it's the 00:24:35.280 --> 00:24:36.590 align:start position:0% everything decoded because it's the protobuf<00:24:35.880> thing<00:24:35.940> we<00:24:36.120> have<00:24:36.179> the<00:24:36.360> thing<00:24:36.480> to 00:24:36.590 --> 00:24:36.600 align:start position:0% protobuf thing we have the thing to 00:24:36.600 --> 00:24:38.450 align:start position:0% protobuf thing we have the thing to decode<00:24:36.900> it<00:24:37.080> we<00:24:37.200> could<00:24:37.320> feed<00:24:37.500> that<00:24:37.679> it<00:24:38.039> arrives 00:24:38.450 --> 00:24:38.460 align:start position:0% decode it we could feed that it arrives 00:24:38.460 --> 00:24:39.890 align:start position:0% decode it we could feed that it arrives on<00:24:38.580> the<00:24:38.700> wire<00:24:38.820> as<00:24:39.000> bytes<00:24:39.419> and<00:24:39.539> it<00:24:39.659> properly 00:24:39.890 --> 00:24:39.900 align:start position:0% on the wire as bytes and it properly 00:24:39.900 --> 00:24:41.630 align:start position:0% on the wire as bytes and it properly serialized<00:24:40.320> bytes<00:24:40.620> and<00:24:41.039> then<00:24:41.100> we<00:24:41.280> see<00:24:41.460> that 00:24:41.630 --> 00:24:41.640 align:start position:0% serialized bytes and then we see that 00:24:41.640 --> 00:24:43.430 align:start position:0% serialized bytes and then we see that the<00:24:41.820> token<00:24:42.120> address<00:24:42.240> is<00:24:42.600> there<00:24:42.960> we<00:24:43.140> have<00:24:43.260> a 00:24:43.430 --> 00:24:43.440 align:start position:0% the token address is there we have a 00:24:43.440 --> 00:24:45.409 align:start position:0% the token address is there we have a decimal<00:24:43.799> we<00:24:44.039> have<00:24:44.159> the<00:24:44.400> address 00:24:45.409 --> 00:24:45.419 align:start position:0% decimal we have the address 00:24:45.419 --> 00:24:47.630 align:start position:0% decimal we have the address and<00:24:46.080> so<00:24:46.380> what<00:24:46.679> that<00:24:46.860> means<00:24:47.100> is<00:24:47.220> pretty<00:24:47.460> crazy 00:24:47.630 --> 00:24:47.640 align:start position:0% and so what that means is pretty crazy 00:24:47.640 --> 00:24:50.270 align:start position:0% and so what that means is pretty crazy already<00:24:48.000> oh<00:24:48.419> do<00:24:48.720> I<00:24:48.840> see<00:24:49.020> that<00:24:49.200> okay<00:24:49.919> what<00:24:50.100> that 00:24:50.270 --> 00:24:50.280 align:start position:0% already oh do I see that okay what that 00:24:50.280 --> 00:24:52.789 align:start position:0% already oh do I see that okay what that means<00:24:50.520> is<00:24:50.580> that<00:24:50.820> you<00:24:51.659> can<00:24:51.780> inspect<00:24:52.260> the<00:24:52.620> chain 00:24:52.789 --> 00:24:52.799 align:start position:0% means is that you can inspect the chain 00:24:52.799 --> 00:24:54.890 align:start position:0% means is that you can inspect the chain with<00:24:53.100> your<00:24:53.280> code<00:24:53.520> at<00:24:54.059> any<00:24:54.179> place<00:24:54.360> in<00:24:54.600> time<00:24:54.720> for 00:24:54.890 --> 00:24:54.900 align:start position:0% with your code at any place in time for 00:24:54.900 --> 00:24:56.810 align:start position:0% with your code at any place in time for a<00:24:55.080> mapper<00:24:55.320> especially<00:24:55.740> you<00:24:56.100> can<00:24:56.280> go<00:24:56.460> there<00:24:56.640> and 00:24:56.810 --> 00:24:56.820 align:start position:0% a mapper especially you can go there and 00:24:56.820 --> 00:24:59.930 align:start position:0% a mapper especially you can go there and I<00:24:56.940> could<00:24:57.000> run<00:24:57.179> it<00:24:57.299> again<00:24:57.480> here<00:24:57.840> and<00:24:58.380> say<00:24:58.940> and 00:24:59.930 --> 00:24:59.940 align:start position:0% I could run it again here and say and 00:24:59.940 --> 00:25:01.669 align:start position:0% I could run it again here and say and say<00:25:00.120> I<00:25:00.299> want<00:25:00.419> to<00:25:00.539> run<00:25:00.659> the<00:25:00.840> mapper<00:25:01.200> let's<00:25:01.380> say<00:25:01.500> a 00:25:01.669 --> 00:25:01.679 align:start position:0% say I want to run the mapper let's say a 00:25:01.679 --> 00:25:03.770 align:start position:0% say I want to run the mapper let's say a block<00:25:01.860> I<00:25:02.220> don't<00:25:02.280> know<00:25:02.400> uh 00:25:03.770 --> 00:25:03.780 align:start position:0% block I don't know uh 00:25:03.780 --> 00:25:05.450 align:start position:0% block I don't know uh something<00:25:04.320> more<00:25:04.559> recent<00:25:04.799> give<00:25:04.980> me<00:25:05.100> a<00:25:05.220> recent 00:25:05.450 --> 00:25:05.460 align:start position:0% something more recent give me a recent 00:25:05.460 --> 00:25:08.750 align:start position:0% something more recent give me a recent block<00:25:05.700> what's<00:25:06.299> the<00:25:06.539> block<00:25:06.659> yesterday 00:25:08.750 --> 00:25:08.760 align:start position:0% block what's the block yesterday 00:25:08.760 --> 00:25:10.310 align:start position:0% block what's the block yesterday fifteen<00:25:09.480> seven<00:25:09.600> million<00:25:09.960> I<00:25:10.080> know<00:25:10.200> something 00:25:10.310 --> 00:25:10.320 align:start position:0% fifteen seven million I know something 00:25:10.320 --> 00:25:12.830 align:start position:0% fifteen seven million I know something like<00:25:10.500> that<00:25:10.620> okay<00:25:10.799> and<00:25:11.580> see<00:25:11.880> is<00:25:12.659> there<00:25:12.720> anything 00:25:12.830 --> 00:25:12.840 align:start position:0% like that okay and see is there anything 00:25:12.840 --> 00:25:15.529 align:start position:0% like that okay and see is there anything recent<00:25:13.320> so<00:25:13.559> there's<00:25:13.799> some<00:25:13.980> stuff<00:25:14.280> right<00:25:14.640> some 00:25:15.529 --> 00:25:15.539 align:start position:0% recent so there's some stuff right some 00:25:15.539 --> 00:25:18.169 align:start position:0% recent so there's some stuff right some things<00:25:15.780> are<00:25:16.020> recent<00:25:16.440> can<00:25:16.980> I<00:25:17.159> see<00:25:17.280> that<00:25:17.460> someone 00:25:18.169 --> 00:25:18.179 align:start position:0% things are recent can I see that someone 00:25:18.179 --> 00:25:20.450 align:start position:0% things are recent can I see that someone still<00:25:18.600> created<00:25:18.900> a<00:25:19.140> new<00:25:19.260> pool 00:25:20.450 --> 00:25:20.460 align:start position:0% still created a new pool 00:25:20.460 --> 00:25:22.310 align:start position:0% still created a new pool and<00:25:20.880> I<00:25:21.120> can<00:25:21.179> inspect<00:25:21.539> my<00:25:21.720> code<00:25:21.900> to<00:25:22.080> make<00:25:22.200> sure 00:25:22.310 --> 00:25:22.320 align:start position:0% and I can inspect my code to make sure 00:25:22.320 --> 00:25:24.049 align:start position:0% and I can inspect my code to make sure it<00:25:22.440> works<00:25:22.679> where<00:25:22.860> is<00:25:23.039> that 00:25:24.049 --> 00:25:24.059 align:start position:0% it works where is that 00:25:24.059 --> 00:25:26.630 align:start position:0% it works where is that come<00:25:24.539> on<00:25:24.720> right<00:25:25.080> this<00:25:25.380> one<00:25:25.559> was<00:25:25.679> rap<00:25:25.980> ether<00:25:26.400> and 00:25:26.630 --> 00:25:26.640 align:start position:0% come on right this one was rap ether and 00:25:26.640 --> 00:25:28.070 align:start position:0% come on right this one was rap ether and infinity<00:25:26.760> they<00:25:27.179> were<00:25:27.419> just<00:25:27.539> created<00:25:27.840> that 00:25:28.070 --> 00:25:28.080 align:start position:0% infinity they were just created that 00:25:28.080 --> 00:25:30.049 align:start position:0% infinity they were just created that address<00:25:28.260> as<00:25:28.559> a<00:25:28.740> new<00:25:28.799> pool<00:25:28.980> so<00:25:29.520> you<00:25:29.760> can<00:25:29.820> go<00:25:29.940> and 00:25:30.049 --> 00:25:30.059 align:start position:0% address as a new pool so you can go and 00:25:30.059 --> 00:25:31.789 align:start position:0% address as a new pool so you can go and test<00:25:30.240> your<00:25:30.419> code<00:25:30.539> everywhere<00:25:30.900> what's<00:25:31.320> that's 00:25:31.789 --> 00:25:31.799 align:start position:0% test your code everywhere what's that's 00:25:31.799 --> 00:25:33.529 align:start position:0% test your code everywhere what's that's done<00:25:32.100> well<00:25:32.400> you're<00:25:32.580> set<00:25:32.820> right<00:25:33.059> you<00:25:33.240> can<00:25:33.360> go 00:25:33.529 --> 00:25:33.539 align:start position:0% done well you're set right you can go 00:25:33.539 --> 00:25:36.590 align:start position:0% done well you're set right you can go then<00:25:33.720> to<00:25:34.200> the<00:25:34.380> next<00:25:34.559> data<00:25:35.159> dependency<00:25:35.640> so<00:25:36.419> this 00:25:36.590 --> 00:25:36.600 align:start position:0% then to the next data dependency so this 00:25:36.600 --> 00:25:38.090 align:start position:0% then to the next data dependency so this really<00:25:36.840> changes<00:25:37.140> Dynamics<00:25:37.620> for<00:25:37.740> debugging 00:25:38.090 --> 00:25:38.100 align:start position:0% really changes Dynamics for debugging 00:25:38.100 --> 00:25:40.310 align:start position:0% really changes Dynamics for debugging and<00:25:38.220> this<00:25:38.460> can<00:25:38.580> also<00:25:38.880> work<00:25:39.059> for<00:25:39.720> stores<00:25:40.020> they 00:25:40.310 --> 00:25:40.320 align:start position:0% and this can also work for stores they 00:25:40.320 --> 00:25:42.110 align:start position:0% and this can also work for stores they can<00:25:40.440> you<00:25:40.620> can<00:25:40.740> ask<00:25:40.860> for<00:25:41.100> a<00:25:41.279> store<00:25:41.460> and<00:25:41.940> it's 00:25:42.110 --> 00:25:42.120 align:start position:0% can you can ask for a store and it's 00:25:42.120 --> 00:25:43.549 align:start position:0% can you can ask for a store and it's going<00:25:42.179> to<00:25:42.240> process<00:25:42.600> it<00:25:42.840> in<00:25:42.960> parallel<00:25:43.320> and<00:25:43.440> then 00:25:43.549 --> 00:25:43.559 align:start position:0% going to process it in parallel and then 00:25:43.559 --> 00:25:45.110 align:start position:0% going to process it in parallel and then you<00:25:43.679> can<00:25:43.799> inspect<00:25:44.100> all<00:25:44.340> the<00:25:44.460> keys<00:25:44.760> that<00:25:44.880> exist 00:25:45.110 --> 00:25:45.120 align:start position:0% you can inspect all the keys that exist 00:25:45.120 --> 00:25:47.149 align:start position:0% you can inspect all the keys that exist there<00:25:45.299> or<00:25:45.720> see<00:25:45.960> the<00:25:46.200> Deltas<00:25:46.559> coming<00:25:46.919> through 00:25:47.149 --> 00:25:47.159 align:start position:0% there or see the Deltas coming through 00:25:47.159 --> 00:25:49.370 align:start position:0% there or see the Deltas coming through okay<00:25:47.880> and<00:25:48.539> let<00:25:48.900> me<00:25:48.960> show<00:25:49.080> you<00:25:49.200> something 00:25:49.370 --> 00:25:49.380 align:start position:0% okay and let me show you something 00:25:49.380 --> 00:25:51.110 align:start position:0% okay and let me show you something running<00:25:49.620> in<00:25:49.919> parallel 00:25:51.110 --> 00:25:51.120 align:start position:0% running in parallel 00:25:51.120 --> 00:25:54.409 align:start position:0% running in parallel uh-huh<00:25:52.020> graph<00:25:52.440> out<00:25:52.620> now<00:25:53.159> this<00:25:53.460> is<00:25:53.700> very 00:25:54.409 --> 00:25:54.419 align:start position:0% uh-huh graph out now this is very 00:25:54.419 --> 00:25:56.690 align:start position:0% uh-huh graph out now this is very interesting<00:25:54.779> because<00:25:55.080> oh<00:25:56.039> no<00:25:56.220> let's<00:25:56.400> start<00:25:56.580> it 00:25:56.690 --> 00:25:56.700 align:start position:0% interesting because oh no let's start it 00:25:56.700 --> 00:25:58.610 align:start position:0% interesting because oh no let's start it at<00:25:56.820> 15<00:25:57.059> million<00:25:57.539> let's<00:25:57.779> say<00:25:57.960> I<00:25:58.080> want<00:25:58.200> graph<00:25:58.500> out 00:25:58.610 --> 00:25:58.620 align:start position:0% at 15 million let's say I want graph out 00:25:58.620 --> 00:26:01.010 align:start position:0% at 15 million let's say I want graph out at<00:25:58.860> 15<00:25:59.100> million<00:25:59.640> I<00:26:00.299> didn't<00:26:00.419> run<00:26:00.720> it<00:26:00.900> again 00:26:01.010 --> 00:26:01.020 align:start position:0% at 15 million I didn't run it again 00:26:01.020 --> 00:26:04.669 align:start position:0% at 15 million I didn't run it again before<00:26:01.380> and<00:26:02.220> I<00:26:02.460> want<00:26:02.700> so<00:26:03.419> let's<00:26:03.720> write<00:26:03.900> it 00:26:04.669 --> 00:26:04.679 align:start position:0% before and I want so let's write it 00:26:04.679 --> 00:26:07.789 align:start position:0% before and I want so let's write it so<00:26:05.100> this<00:26:05.220> starts<00:26:05.640> a<00:26:05.880> whole<00:26:06.120> bunch<00:26:06.419> of<00:26:06.960> parallel 00:26:07.789 --> 00:26:07.799 align:start position:0% so this starts a whole bunch of parallel 00:26:07.799 --> 00:26:09.890 align:start position:0% so this starts a whole bunch of parallel processes<00:26:08.400> and<00:26:09.000> you<00:26:09.120> see<00:26:09.299> up<00:26:09.480> there<00:26:09.659> the 00:26:09.890 --> 00:26:09.900 align:start position:0% processes and you see up there the 00:26:09.900 --> 00:26:11.810 align:start position:0% processes and you see up there the number<00:26:10.020> of<00:26:10.140> blocks<00:26:10.500> per<00:26:10.620> second<00:26:10.799> yesterday<00:26:11.520> I 00:26:11.810 --> 00:26:11.820 align:start position:0% number of blocks per second yesterday I 00:26:11.820 --> 00:26:14.210 align:start position:0% number of blocks per second yesterday I had<00:26:12.000> about<00:26:12.120> 8<00:26:12.659> 000<00:26:12.720> on<00:26:13.200> Solana<00:26:13.620> blocks<00:26:13.919> I<00:26:14.100> had 00:26:14.210 --> 00:26:14.220 align:start position:0% had about 8 000 on Solana blocks I had 00:26:14.220 --> 00:26:15.830 align:start position:0% had about 8 000 on Solana blocks I had 16<00:26:14.760> 000<00:26:14.820> depends<00:26:15.179> on<00:26:15.240> the<00:26:15.360> power<00:26:15.480> you<00:26:15.720> put 00:26:15.830 --> 00:26:15.840 align:start position:0% 16 000 depends on the power you put 00:26:15.840 --> 00:26:18.710 align:start position:0% 16 000 depends on the power you put behind<00:26:16.140> there<00:26:16.320> but<00:26:17.159> this<00:26:17.640> all<00:26:17.820> like<00:26:18.299> you<00:26:18.539> said 00:26:18.710 --> 00:26:18.720 align:start position:0% behind there but this all like you said 00:26:18.720 --> 00:26:20.990 align:start position:0% behind there but this all like you said the<00:26:18.960> pool<00:26:19.140> counts<00:26:19.679> as<00:26:19.740> a<00:26:19.919> dependency<00:26:20.400> on<00:26:20.820> the 00:26:20.990 --> 00:26:21.000 align:start position:0% the pool counts as a dependency on the 00:26:21.000 --> 00:26:22.549 align:start position:0% the pool counts as a dependency on the pools<00:26:21.299> the<00:26:21.480> pools<00:26:21.720> is<00:26:21.840> further<00:26:22.080> down<00:26:22.200> so<00:26:22.380> we're 00:26:22.549 --> 00:26:22.559 align:start position:0% pools the pools is further down so we're 00:26:22.559 --> 00:26:24.529 align:start position:0% pools the pools is further down so we're able<00:26:22.740> to<00:26:22.799> schedule<00:26:23.039> things<00:26:23.400> and<00:26:24.240> all<00:26:24.360> that 00:26:24.529 --> 00:26:24.539 align:start position:0% able to schedule things and all that 00:26:24.539 --> 00:26:26.450 align:start position:0% able to schedule things and all that just<00:26:24.900> massively<00:26:25.620> parallel<00:26:25.980> and<00:26:26.100> once<00:26:26.340> that's 00:26:26.450 --> 00:26:26.460 align:start position:0% just massively parallel and once that's 00:26:26.460 --> 00:26:28.010 align:start position:0% just massively parallel and once that's ready<00:26:26.640> let's<00:26:26.880> say<00:26:27.059> everything<00:26:27.299> was<00:26:27.480> done<00:26:27.659> I 00:26:28.010 --> 00:26:28.020 align:start position:0% ready let's say everything was done I 00:26:28.020 --> 00:26:29.570 align:start position:0% ready let's say everything was done I would<00:26:28.260> start<00:26:28.440> streaming<00:26:28.860> and<00:26:28.980> get<00:26:29.220> all<00:26:29.400> the 00:26:29.570 --> 00:26:29.580 align:start position:0% would start streaming and get all the 00:26:29.580 --> 00:26:31.970 align:start position:0% would start streaming and get all the content<00:26:30.000> and<00:26:30.659> so<00:26:30.779> let<00:26:30.960> me<00:26:31.140> show<00:26:31.200> you<00:26:31.380> the<00:26:31.799> graph 00:26:31.970 --> 00:26:31.980 align:start position:0% content and so let me show you the graph 00:26:31.980 --> 00:26:34.430 align:start position:0% content and so let me show you the graph out<00:26:32.159> it's<00:26:32.400> very<00:26:32.580> interesting<00:26:32.940> because 00:26:34.430 --> 00:26:34.440 align:start position:0% out it's very interesting because 00:26:34.440 --> 00:26:38.210 align:start position:0% out it's very interesting because because<00:26:35.100> graph<00:26:35.700> out 00:26:38.210 --> 00:26:38.220 align:start position:0% 00:26:38.220 --> 00:26:39.769 align:start position:0% graph<00:26:38.940> out 00:26:39.769 --> 00:26:39.779 align:start position:0% graph out 00:26:39.779 --> 00:26:43.730 align:start position:0% graph out has<00:26:40.620> refined<00:26:41.340> the<00:26:41.460> data<00:26:41.820> up<00:26:42.120> to<00:26:42.360> entities<00:26:42.900> now 00:26:43.730 --> 00:26:43.740 align:start position:0% has refined the data up to entities now 00:26:43.740 --> 00:26:46.010 align:start position:0% has refined the data up to entities now we're<00:26:43.980> talking<00:26:44.159> about<00:26:44.400> database<00:26:45.240> tables<00:26:45.840> and 00:26:46.010 --> 00:26:46.020 align:start position:0% we're talking about database tables and 00:26:46.020 --> 00:26:48.710 align:start position:0% we're talking about database tables and Fields<00:26:46.380> and<00:26:46.919> you<00:26:47.100> get<00:26:47.340> and<00:26:48.120> you<00:26:48.240> get<00:26:48.419> out<00:26:48.600> of 00:26:48.710 --> 00:26:48.720 align:start position:0% Fields and you get and you get out of 00:26:48.720 --> 00:26:49.669 align:start position:0% Fields and you get and you get out of that 00:26:49.669 --> 00:26:49.679 align:start position:0% that 00:26:49.679 --> 00:26:52.190 align:start position:0% that do<00:26:50.039> you<00:26:50.159> not<00:26:50.279> see<00:26:50.520> it<00:26:50.700> okay<00:26:50.880> that<00:26:51.240> wait<00:26:51.960> a 00:26:52.190 --> 00:26:52.200 align:start position:0% do you not see it okay that wait a 00:26:52.200 --> 00:26:54.430 align:start position:0% do you not see it okay that wait a second<00:26:52.320> here<00:26:52.559> so<00:26:52.919> let's<00:26:53.460> imagine<00:26:53.640> see<00:26:54.000> we<00:26:54.240> have 00:26:54.430 --> 00:26:54.440 align:start position:0% second here so let's imagine see we have 00:26:54.440 --> 00:26:57.590 align:start position:0% second here so let's imagine see we have token<00:26:55.440> and<00:26:55.980> an<00:26:56.159> update<00:26:56.520> and<00:26:56.880> you<00:26:57.059> have<00:26:57.240> the 00:26:57.590 --> 00:26:57.600 align:start position:0% token and an update and you have the 00:26:57.600 --> 00:26:59.690 align:start position:0% token and an update and you have the field<00:26:57.779> derived<00:26:58.320> if<00:26:58.440> and<00:26:58.799> you<00:26:58.980> have<00:26:59.159> the<00:26:59.460> old 00:26:59.690 --> 00:26:59.700 align:start position:0% field derived if and you have the old 00:26:59.700 --> 00:27:01.430 align:start position:0% field derived if and you have the old value<00:26:59.940> and<00:27:00.360> the<00:27:00.539> new<00:27:00.720> value<00:27:00.900> I<00:27:01.140> don't<00:27:01.260> know<00:27:01.320> if 00:27:01.430 --> 00:27:01.440 align:start position:0% value and the new value I don't know if 00:27:01.440 --> 00:27:03.110 align:start position:0% value and the new value I don't know if you've<00:27:01.620> seen<00:27:01.799> this<00:27:02.039> thing<00:27:02.220> in<00:27:02.700> the<00:27:02.820> data 00:27:03.110 --> 00:27:03.120 align:start position:0% you've seen this thing in the data 00:27:03.120 --> 00:27:04.850 align:start position:0% you've seen this thing in the data Science<00:27:03.179> World<00:27:03.480> this<00:27:03.779> looks<00:27:04.140> very<00:27:04.380> much<00:27:04.500> like 00:27:04.850 --> 00:27:04.860 align:start position:0% Science World this looks very much like 00:27:04.860 --> 00:27:08.330 align:start position:0% Science World this looks very much like change<00:27:05.760> change<00:27:06.179> data<00:27:06.720> capture<00:27:07.020> cdcs<00:27:07.740> that<00:27:08.159> can 00:27:08.330 --> 00:27:08.340 align:start position:0% change change data capture cdcs that can 00:27:08.340 --> 00:27:11.450 align:start position:0% change change data capture cdcs that can power<00:27:08.580> a<00:27:08.940> lot<00:27:09.120> of<00:27:09.299> large-scale<00:27:09.960> systems<00:27:10.559> and 00:27:11.450 --> 00:27:11.460 align:start position:0% power a lot of large-scale systems and 00:27:11.460 --> 00:27:14.090 align:start position:0% power a lot of large-scale systems and uh<00:27:11.760> and<00:27:12.179> you<00:27:12.419> have<00:27:12.539> the<00:27:12.720> prior<00:27:12.960> after<00:27:13.260> so<00:27:13.620> you 00:27:14.090 --> 00:27:14.100 align:start position:0% uh and you have the prior after so you 00:27:14.100 --> 00:27:16.070 align:start position:0% uh and you have the prior after so you can<00:27:14.159> feed<00:27:14.400> that<00:27:14.640> to<00:27:14.880> your<00:27:15.059> let's<00:27:15.360> say<00:27:15.600> postgres 00:27:16.070 --> 00:27:16.080 align:start position:0% can feed that to your let's say postgres 00:27:16.080 --> 00:27:18.649 align:start position:0% can feed that to your let's say postgres apply<00:27:16.980> the<00:27:17.220> changes<00:27:17.640> and<00:27:18.000> when<00:27:18.179> you<00:27:18.299> have<00:27:18.419> an 00:27:18.649 --> 00:27:18.659 align:start position:0% apply the changes and when you have an 00:27:18.659 --> 00:27:20.750 align:start position:0% apply the changes and when you have an undo<00:27:19.020> signal<00:27:19.440> it<00:27:20.039> gives<00:27:20.220> you<00:27:20.400> back<00:27:20.580> that 00:27:20.750 --> 00:27:20.760 align:start position:0% undo signal it gives you back that 00:27:20.760 --> 00:27:22.310 align:start position:0% undo signal it gives you back that payload<00:27:21.240> you<00:27:21.360> then<00:27:21.539> just<00:27:21.720> flip<00:27:22.080> everything 00:27:22.310 --> 00:27:22.320 align:start position:0% payload you then just flip everything 00:27:22.320 --> 00:27:25.010 align:start position:0% payload you then just flip everything and<00:27:22.980> you<00:27:23.159> have<00:27:23.400> guaranteed<00:27:24.120> linearities<00:27:24.659> to 00:27:25.010 --> 00:27:25.020 align:start position:0% and you have guaranteed linearities to 00:27:25.020 --> 00:27:27.169 align:start position:0% and you have guaranteed linearities to your<00:27:25.200> store<00:27:25.500> with<00:27:25.679> a<00:27:25.860> cursor<00:27:26.220> and<00:27:26.880> it<00:27:27.059> is 00:27:27.169 --> 00:27:27.179 align:start position:0% your store with a cursor and it is 00:27:27.179 --> 00:27:29.210 align:start position:0% your store with a cursor and it is Flawless<00:27:27.720> it's<00:27:27.960> just<00:27:28.200> extremely<00:27:28.679> simple<00:27:28.980> to 00:27:29.210 --> 00:27:29.220 align:start position:0% Flawless it's just extremely simple to 00:27:29.220 --> 00:27:31.070 align:start position:0% Flawless it's just extremely simple to keep<00:27:29.340> your<00:27:29.520> things<00:27:29.700> in<00:27:29.880> sync<00:27:30.240> you<00:27:30.779> also<00:27:30.960> want 00:27:31.070 --> 00:27:31.080 align:start position:0% keep your things in sync you also want 00:27:31.080 --> 00:27:32.810 align:start position:0% keep your things in sync you also want to<00:27:31.200> have<00:27:31.260> a<00:27:31.440> slack<00:27:31.679> body<00:27:31.860> can<00:27:32.100> have<00:27:32.220> it<00:27:32.340> undo 00:27:32.810 --> 00:27:32.820 align:start position:0% to have a slack body can have it undo 00:27:32.820 --> 00:27:34.730 align:start position:0% to have a slack body can have it undo message<00:27:33.000> remove<00:27:33.360> the<00:27:33.659> message<00:27:33.900> if<00:27:34.200> you<00:27:34.380> have<00:27:34.500> a 00:27:34.730 --> 00:27:34.740 align:start position:0% message remove the message if you have a 00:27:34.740 --> 00:27:36.169 align:start position:0% message remove the message if you have a thing<00:27:34.919> coming<00:27:35.100> through<00:27:35.340> right 00:27:36.169 --> 00:27:36.179 align:start position:0% thing coming through right 00:27:36.179 --> 00:27:37.430 align:start position:0% thing coming through right so 00:27:37.430 --> 00:27:37.440 align:start position:0% so 00:27:37.440 --> 00:27:39.289 align:start position:0% so I<00:27:37.980> think<00:27:38.039> that's<00:27:38.220> pretty<00:27:38.460> cool<00:27:38.640> what<00:27:39.120> do<00:27:39.240> you 00:27:39.289 --> 00:27:39.299 align:start position:0% I think that's pretty cool what do you 00:27:39.299 --> 00:27:40.330 align:start position:0% I think that's pretty cool what do you think 00:27:40.330 --> 00:27:40.340 align:start position:0% think 00:27:40.340 --> 00:27:42.289 align:start position:0% think okay 00:27:42.289 --> 00:27:42.299 align:start position:0% okay 00:27:42.299 --> 00:27:44.390 align:start position:0% okay okay<00:27:42.659> that's<00:27:42.960> cool<00:27:43.200> can<00:27:43.679> I<00:27:43.799> shut<00:27:44.039> that<00:27:44.220> down 00:27:44.390 --> 00:27:44.400 align:start position:0% okay that's cool can I shut that down 00:27:44.400 --> 00:27:46.730 align:start position:0% okay that's cool can I shut that down here<00:27:44.580> do<00:27:44.820> I<00:27:44.940> have<00:27:45.000> another<00:27:45.120> window 00:27:46.730 --> 00:27:46.740 align:start position:0% here do I have another window 00:27:46.740 --> 00:27:48.590 align:start position:0% here do I have another window uh<00:27:47.279> I'm<00:27:47.460> close<00:27:47.640> to<00:27:47.820> them<00:27:48.000> prepare<00:27:48.480> your 00:27:48.590 --> 00:27:48.600 align:start position:0% uh I'm close to them prepare your 00:27:48.600 --> 00:27:50.570 align:start position:0% uh I'm close to them prepare your question<00:27:48.779> please<00:27:49.140> ask<00:27:49.440> ask<00:27:49.740> them<00:27:50.039> succinctly 00:27:50.570 --> 00:27:50.580 align:start position:0% question please ask ask them succinctly 00:27:50.580 --> 00:27:52.909 align:start position:0% question please ask ask them succinctly we<00:27:50.880> have<00:27:51.059> a<00:27:51.840> half<00:27:52.020> a<00:27:52.200> minute<00:27:52.320> I<00:27:52.500> just<00:27:52.620> wanted<00:27:52.740> to 00:27:52.909 --> 00:27:52.919 align:start position:0% we have a half a minute I just wanted to 00:27:52.919 --> 00:27:55.430 align:start position:0% we have a half a minute I just wanted to have<00:27:53.100> a<00:27:53.279> final<00:27:53.460> final<00:27:53.820> note<00:27:54.179> there 00:27:55.430 --> 00:27:55.440 align:start position:0% have a final final note there 00:27:55.440 --> 00:27:57.649 align:start position:0% have a final final note there so<00:27:55.860> as<00:27:56.100> a<00:27:56.340> final<00:27:56.520> note 00:27:57.649 --> 00:27:57.659 align:start position:0% so as a final note 00:27:57.659 --> 00:27:59.930 align:start position:0% so as a final note I<00:27:58.020> want<00:27:58.140> to<00:27:58.200> share<00:27:58.440> with<00:27:58.620> you<00:27:58.740> a<00:27:58.919> little<00:27:59.039> bit<00:27:59.220> of 00:27:59.930 --> 00:27:59.940 align:start position:0% I want to share with you a little bit of 00:27:59.940 --> 00:28:01.850 align:start position:0% I want to share with you a little bit of my<00:28:00.179> vision<00:28:00.360> for<00:28:00.720> the<00:28:00.840> graph 00:28:01.850 --> 00:28:01.860 align:start position:0% my vision for the graph 00:28:01.860 --> 00:28:03.769 align:start position:0% my vision for the graph okay<00:28:02.340> I<00:28:02.640> don't<00:28:02.700> know<00:28:02.820> where<00:28:02.880> the<00:28:03.000> window<00:28:03.120> is<00:28:03.360> so 00:28:03.769 --> 00:28:03.779 align:start position:0% okay I don't know where the window is so 00:28:03.779 --> 00:28:06.950 align:start position:0% okay I don't know where the window is so whatever<00:28:03.960> it<00:28:04.320> just<00:28:04.440> says<00:28:04.740> fine<00:28:04.919> it's<00:28:05.220> fine<00:28:05.460> uh 00:28:06.950 --> 00:28:06.960 align:start position:0% whatever it just says fine it's fine uh 00:28:06.960 --> 00:28:09.830 align:start position:0% whatever it just says fine it's fine uh I'm<00:28:07.440> imagining<00:28:07.919> the<00:28:08.100> graph<00:28:08.400> becoming<00:28:09.059> that 00:28:09.830 --> 00:28:09.840 align:start position:0% I'm imagining the graph becoming that 00:28:09.840 --> 00:28:12.950 align:start position:0% I'm imagining the graph becoming that sort<00:28:10.080> of<00:28:10.320> huge<00:28:11.039> worldwide<00:28:11.820> cluster<00:28:12.360> of 00:28:12.950 --> 00:28:12.960 align:start position:0% sort of huge worldwide cluster of 00:28:12.960 --> 00:28:15.470 align:start position:0% sort of huge worldwide cluster of processing<00:28:13.559> and<00:28:13.799> storage<00:28:13.980> capabilities<00:28:14.580> and 00:28:15.470 --> 00:28:15.480 align:start position:0% processing and storage capabilities and 00:28:15.480 --> 00:28:17.269 align:start position:0% processing and storage capabilities and something<00:28:15.779> like<00:28:16.020> Google's<00:28:16.500> bigquery<00:28:16.980> but 00:28:17.269 --> 00:28:17.279 align:start position:0% something like Google's bigquery but 00:28:17.279 --> 00:28:19.190 align:start position:0% something like Google's bigquery but where<00:28:17.580> people<00:28:17.820> join<00:28:18.179> because<00:28:18.360> it's<00:28:18.779> better 00:28:19.190 --> 00:28:19.200 align:start position:0% where people join because it's better 00:28:19.200 --> 00:28:21.230 align:start position:0% where people join because it's better together<00:28:19.559> right<00:28:20.220> instead<00:28:20.820> of<00:28:20.880> running<00:28:21.000> it 00:28:21.230 --> 00:28:21.240 align:start position:0% together right instead of running it 00:28:21.240 --> 00:28:22.850 align:start position:0% together right instead of running it alone<00:28:21.360> we<00:28:21.600> need<00:28:21.779> to<00:28:21.900> have<00:28:22.080> all<00:28:22.380> the<00:28:22.440> resources 00:28:22.850 --> 00:28:22.860 align:start position:0% alone we need to have all the resources 00:28:22.860 --> 00:28:24.950 align:start position:0% alone we need to have all the resources alone<00:28:23.039> and<00:28:23.760> I<00:28:23.880> see<00:28:24.059> also<00:28:24.360> a<00:28:24.480> new<00:28:24.600> era<00:28:24.840> of 00:28:24.950 --> 00:28:24.960 align:start position:0% alone and I see also a new era of 00:28:24.960 --> 00:28:26.630 align:start position:0% alone and I see also a new era of composability<00:28:25.620> which<00:28:26.100> means<00:28:26.340> more 00:28:26.630 --> 00:28:26.640 align:start position:0% composability which means more 00:28:26.640 --> 00:28:29.149 align:start position:0% composability which means more collaboration<00:28:27.299> and<00:28:28.140> in<00:28:28.320> a<00:28:28.500> tighter<00:28:28.919> Community 00:28:29.149 --> 00:28:29.159 align:start position:0% collaboration and in a tighter Community 00:28:29.159 --> 00:28:31.250 align:start position:0% collaboration and in a tighter Community working<00:28:29.520> together<00:28:29.880> more<00:28:30.840> intimately<00:28:31.080> in 00:28:31.250 --> 00:28:31.260 align:start position:0% working together more intimately in 00:28:31.260 --> 00:28:33.289 align:start position:0% working together more intimately in those<00:28:31.440> in<00:28:31.679> those<00:28:31.980> uh<00:28:32.220> you<00:28:32.760> know<00:28:32.820> with<00:28:33.059> those 00:28:33.289 --> 00:28:33.299 align:start position:0% those in those uh you know with those 00:28:33.299 --> 00:28:36.649 align:start position:0% those in those uh you know with those data<00:28:33.720> contracts<00:28:34.200> and<00:28:34.679> I<00:28:34.799> see<00:28:35.039> also<00:28:35.460> a<00:28:36.299> new<00:28:36.419> mix 00:28:36.649 --> 00:28:36.659 align:start position:0% data contracts and I see also a new mix 00:28:36.659 --> 00:28:39.710 align:start position:0% data contracts and I see also a new mix of<00:28:36.960> collaboration<00:28:37.559> between<00:28:38.100> indexers<00:28:38.940> like 00:28:39.710 --> 00:28:39.720 align:start position:0% of collaboration between indexers like 00:28:39.720 --> 00:28:42.409 align:start position:0% of collaboration between indexers like exchanging<00:28:40.440> data<00:28:40.980> or<00:28:41.279> sharing<00:28:41.700> resources<00:28:42.240> in 00:28:42.409 --> 00:28:42.419 align:start position:0% exchanging data or sharing resources in 00:28:42.419 --> 00:28:43.850 align:start position:0% exchanging data or sharing resources in terms<00:28:42.600> of<00:28:42.720> compute<00:28:43.020> and<00:28:43.080> stores<00:28:43.320> and<00:28:43.559> whatnot 00:28:43.850 --> 00:28:43.860 align:start position:0% terms of compute and stores and whatnot 00:28:43.860 --> 00:28:45.950 align:start position:0% terms of compute and stores and whatnot therefore<00:28:44.520> introducing<00:28:45.000> new<00:28:45.240> value<00:28:45.419> flows 00:28:45.950 --> 00:28:45.960 align:start position:0% therefore introducing new value flows 00:28:45.960 --> 00:28:48.110 align:start position:0% therefore introducing new value flows and<00:28:46.440> also<00:28:46.679> I'm<00:28:46.860> seeing<00:28:47.220> new<00:28:47.460> products<00:28:47.940> new 00:28:48.110 --> 00:28:48.120 align:start position:0% and also I'm seeing new products new 00:28:48.120 --> 00:28:49.669 align:start position:0% and also I'm seeing new products new Services<00:28:48.360> being<00:28:48.779> offered<00:28:49.080> directly<00:28:49.380> on<00:28:49.559> the 00:28:49.669 --> 00:28:49.679 align:start position:0% Services being offered directly on the 00:28:49.679 --> 00:28:51.890 align:start position:0% Services being offered directly on the network<00:28:49.860> you<00:28:50.700> know<00:28:50.820> to<00:28:51.000> satisfy<00:28:51.360> some<00:28:51.539> needs 00:28:51.890 --> 00:28:51.900 align:start position:0% network you know to satisfy some needs 00:28:51.900 --> 00:28:53.810 align:start position:0% network you know to satisfy some needs that<00:28:51.960> perhaps<00:28:52.320> couldn't<00:28:53.220> be<00:28:53.460> addressed 00:28:53.810 --> 00:28:53.820 align:start position:0% that perhaps couldn't be addressed 00:28:53.820 --> 00:28:56.149 align:start position:0% that perhaps couldn't be addressed before<00:28:54.140> and<00:28:55.140> I<00:28:55.320> mean<00:28:55.440> there's<00:28:55.559> a<00:28:55.799> place<00:28:55.980> for 00:28:56.149 --> 00:28:56.159 align:start position:0% before and I mean there's a place for 00:28:56.159 --> 00:28:58.010 align:start position:0% before and I mean there's a place for you<00:28:56.279> in<00:28:56.460> there<00:28:56.580> as<00:28:56.760> a<00:28:56.880> developer<00:28:57.299> as<00:28:57.779> an 00:28:58.010 --> 00:28:58.020 align:start position:0% you in there as a developer as an 00:28:58.020 --> 00:29:00.289 align:start position:0% you in there as a developer as an indexer<00:28:58.440> as<00:28:58.620> someone<00:28:58.799> who<00:28:59.039> realizes<00:28:59.820> the 00:29:00.289 --> 00:29:00.299 align:start position:0% indexer as someone who realizes the 00:29:00.299 --> 00:29:02.570 align:start position:0% indexer as someone who realizes the radical<00:29:01.020> benefits<00:29:01.559> of<00:29:01.740> such<00:29:01.919> a<00:29:02.100> platform<00:29:02.340> and 00:29:02.570 --> 00:29:02.580 align:start position:0% radical benefits of such a platform and 00:29:02.580 --> 00:29:04.970 align:start position:0% radical benefits of such a platform and who<00:29:02.820> who<00:29:03.000> builds<00:29:03.419> on<00:29:03.539> it<00:29:03.659> and<00:29:03.779> promotes<00:29:04.380> it<00:29:04.500> so 00:29:04.970 --> 00:29:04.980 align:start position:0% who who builds on it and promotes it so 00:29:04.980 --> 00:29:08.269 align:start position:0% who who builds on it and promotes it so my<00:29:05.220> ask<00:29:05.400> to<00:29:05.640> you<00:29:05.820> is<00:29:06.059> you<00:29:06.600> go<00:29:06.720> to<00:29:06.900> you<00:29:07.500> go<00:29:08.039> try 00:29:08.269 --> 00:29:08.279 align:start position:0% my ask to you is you go to you go try 00:29:08.279 --> 00:29:10.310 align:start position:0% my ask to you is you go to you go try substreams<00:29:09.059> put<00:29:09.419> pressure<00:29:09.720> on<00:29:09.960> your<00:29:10.140> favorite 00:29:10.310 --> 00:29:10.320 align:start position:0% substreams put pressure on your favorite 00:29:10.320 --> 00:29:12.230 align:start position:0% substreams put pressure on your favorite layer<00:29:10.740> ones<00:29:11.039> so<00:29:11.159> that<00:29:11.279> they<00:29:11.460> do<00:29:11.580> integrate<00:29:12.000> the 00:29:12.230 --> 00:29:12.240 align:start position:0% layer ones so that they do integrate the 00:29:12.240 --> 00:29:14.210 align:start position:0% layer ones so that they do integrate the fire<00:29:12.419> hose<00:29:12.720> natively<00:29:13.200> that's<00:29:13.559> pristine's 00:29:14.210 --> 00:29:14.220 align:start position:0% fire hose natively that's pristine's 00:29:14.220 --> 00:29:16.010 align:start position:0% fire hose natively that's pristine's Aptos<00:29:14.700> has<00:29:14.940> done<00:29:15.059> that<00:29:15.179> recently<00:29:15.480> some<00:29:15.720> others 00:29:16.010 --> 00:29:16.020 align:start position:0% Aptos has done that recently some others 00:29:16.020 --> 00:29:17.990 align:start position:0% Aptos has done that recently some others start<00:29:16.140> wear<00:29:16.320> I<00:29:16.559> think<00:29:16.679> so<00:29:17.159> that<00:29:17.460> makes<00:29:17.700> it 00:29:17.990 --> 00:29:18.000 align:start position:0% start wear I think so that makes it 00:29:18.000 --> 00:29:19.549 align:start position:0% start wear I think so that makes it everything<00:29:18.480> we've<00:29:18.840> seen<00:29:18.960> today<00:29:19.140> becomes 00:29:19.549 --> 00:29:19.559 align:start position:0% everything we've seen today becomes 00:29:19.559 --> 00:29:21.289 align:start position:0% everything we've seen today becomes immediately<00:29:19.919> available<00:29:20.159> to<00:29:20.520> them<00:29:20.640> sell<00:29:21.179> them 00:29:21.289 --> 00:29:21.299 align:start position:0% immediately available to them sell them 00:29:21.299 --> 00:29:23.690 align:start position:0% immediately available to them sell them on<00:29:21.480> the<00:29:21.600> goodies<00:29:21.840> so<00:29:22.320> also<00:29:22.620> join<00:29:22.919> a<00:29:23.039> Discord<00:29:23.340> I 00:29:23.690 --> 00:29:23.700 align:start position:0% on the goodies so also join a Discord I 00:29:23.700 --> 00:29:25.610 align:start position:0% on the goodies so also join a Discord I love<00:29:23.940> follow-up<00:29:24.360> follow-up<00:29:24.659> questions<00:29:24.960> and 00:29:25.610 --> 00:29:25.620 align:start position:0% love follow-up follow-up questions and 00:29:25.620 --> 00:29:27.289 align:start position:0% love follow-up follow-up questions and come<00:29:25.799> see<00:29:25.980> me<00:29:26.100> afterwards<00:29:26.460> I<00:29:26.640> love<00:29:26.880> feedbacks 00:29:27.289 --> 00:29:27.299 align:start position:0% come see me afterwards I love feedbacks 00:29:27.299 --> 00:29:28.850 align:start position:0% come see me afterwards I love feedbacks on<00:29:27.360> these<00:29:27.539> sort<00:29:27.659> of<00:29:27.720> things<00:29:27.840> all<00:29:28.500> of<00:29:28.679> this<00:29:28.740> is 00:29:28.850 --> 00:29:28.860 align:start position:0% on these sort of things all of this is 00:29:28.860 --> 00:29:31.130 align:start position:0% on these sort of things all of this is open<00:29:29.039> source<00:29:29.520> so<00:29:29.700> let's<00:29:29.940> dig<00:29:30.179> and<00:29:30.659> build 00:29:31.130 --> 00:29:31.140 align:start position:0% open source so let's dig and build 00:29:31.140 --> 00:29:32.870 align:start position:0% open source so let's dig and build something<00:29:31.380> of<00:29:31.740> the<00:29:31.919> like<00:29:32.279> together<00:29:32.520> the 00:29:32.870 --> 00:29:32.880 align:start position:0% something of the like together the 00:29:32.880 --> 00:29:34.310 align:start position:0% something of the like together the biggest<00:29:33.000> blockchain<00:29:33.539> platform<00:29:33.960> on<00:29:34.140> Earth 00:29:34.310 --> 00:29:34.320 align:start position:0% biggest blockchain platform on Earth 00:29:34.320 --> 00:29:40.970 align:start position:0% biggest blockchain platform on Earth thank<00:29:35.039> you<00:29:35.159> for<00:29:35.399> your<00:29:35.460> time<00:29:35.640> today 00:29:40.970 --> 00:29:40.980 align:start position:0% 00:29:40.980 --> 00:29:42.950 align:start position:0% do<00:29:41.399> we<00:29:41.460> have<00:29:41.700> time<00:29:41.880> for<00:29:42.179> two<00:29:42.480> three<00:29:42.779> questions 00:29:42.950 --> 00:29:42.960 align:start position:0% do we have time for two three questions 00:29:42.960 --> 00:29:44.389 align:start position:0% do we have time for two three questions we're<00:29:43.260> the<00:29:43.440> last<00:29:43.559> one<00:29:43.740> so<00:29:43.919> if<00:29:44.100> you<00:29:44.159> have<00:29:44.279> a 00:29:44.389 --> 00:29:44.399 align:start position:0% we're the last one so if you have a 00:29:44.399 --> 00:29:45.289 align:start position:0% we're the last one so if you have a question 00:29:45.289 --> 00:29:45.299 align:start position:0% question 00:29:45.299 --> 00:29:48.889 align:start position:0% question hey<00:29:45.899> uh<00:29:46.260> so<00:29:46.440> one<00:29:46.740> question<00:29:46.919> uh<00:29:47.820> modularity<00:29:48.600> and 00:29:48.889 --> 00:29:48.899 align:start position:0% hey uh so one question uh modularity and 00:29:48.899 --> 00:29:50.510 align:start position:0% hey uh so one question uh modularity and composability<00:29:49.440> of<00:29:49.679> these<00:29:49.919> substreams<00:29:50.399> is 00:29:50.510 --> 00:29:50.520 align:start position:0% composability of these substreams is 00:29:50.520 --> 00:29:53.029 align:start position:0% composability of these substreams is super<00:29:50.700> super<00:29:50.940> powerful<00:29:51.419> but<00:29:52.260> still<00:29:52.440> if<00:29:52.799> I<00:29:52.919> look 00:29:53.029 --> 00:29:53.039 align:start position:0% super super powerful but still if I look 00:29:53.039 --> 00:29:55.070 align:start position:0% super super powerful but still if I look at<00:29:53.159> this<00:29:53.340> compared<00:29:53.880> to<00:29:53.880> SQL<00:29:54.360> and<00:29:54.539> like<00:29:54.659> DVT 00:29:55.070 --> 00:29:55.080 align:start position:0% at this compared to SQL and like DVT 00:29:55.080 --> 00:29:57.590 align:start position:0% at this compared to SQL and like DVT models<00:29:55.500> right<00:29:55.860> it's<00:29:56.100> a<00:29:56.279> lot<00:29:56.399> more<00:29:56.520> complex<00:29:56.940> so 00:29:57.590 --> 00:29:57.600 align:start position:0% models right it's a lot more complex so 00:29:57.600 --> 00:29:59.990 align:start position:0% models right it's a lot more complex so how<00:29:57.899> can<00:29:58.080> we<00:29:58.320> enable<00:29:58.919> people<00:29:59.220> to<00:29:59.580> really<00:29:59.700> kind 00:29:59.990 --> 00:30:00.000 align:start position:0% how can we enable people to really kind 00:30:00.000 --> 00:30:02.330 align:start position:0% how can we enable people to really kind of<00:30:00.120> learn<00:30:00.360> this<00:30:00.659> and<00:30:01.020> like<00:30:01.200> build<00:30:01.559> these<00:30:02.220> kind 00:30:02.330 --> 00:30:02.340 align:start position:0% of learn this and like build these kind 00:30:02.340 --> 00:30:09.169 align:start position:0% of learn this and like build these kind of<00:30:02.460> hyper<00:30:03.059> modular<00:30:03.480> data<00:30:04.440> streams<00:30:04.799> so 00:30:09.169 --> 00:30:09.179 align:start position:0% 00:30:09.179 --> 00:30:12.110 align:start position:0% SQL<00:30:09.720> layer<00:30:10.020> like<00:30:10.440> this<00:30:10.919> is<00:30:11.159> powering<00:30:11.880> going 00:30:12.110 --> 00:30:12.120 align:start position:0% SQL layer like this is powering going 00:30:12.120 --> 00:30:14.330 align:start position:0% SQL layer like this is powering going through<00:30:12.360> history<00:30:12.600> it's<00:30:13.320> an<00:30:13.559> adult<00:30:13.740> transform 00:30:14.330 --> 00:30:14.340 align:start position:0% through history it's an adult transform 00:30:14.340 --> 00:30:16.250 align:start position:0% through history it's an adult transform with<00:30:14.760> stateful<00:30:15.179> storage<00:30:15.480> but<00:30:15.960> you<00:30:16.140> would 00:30:16.250 --> 00:30:16.260 align:start position:0% with stateful storage but you would 00:30:16.260 --> 00:30:18.049 align:start position:0% with stateful storage but you would pipelive<00:30:16.740> into<00:30:16.860> SQL<00:30:17.220> store<00:30:17.399> to<00:30:17.640> do<00:30:17.820> other 00:30:18.049 --> 00:30:18.059 align:start position:0% pipelive into SQL store to do other 00:30:18.059 --> 00:30:19.909 align:start position:0% pipelive into SQL store to do other things<00:30:18.360> right<00:30:19.020> you<00:30:19.200> would<00:30:19.380> have<00:30:19.440> refinement 00:30:19.909 --> 00:30:19.919 align:start position:0% things right you would have refinement 00:30:19.919 --> 00:30:21.769 align:start position:0% things right you would have refinement you<00:30:20.039> have<00:30:20.220> Knowledge<00:30:20.580> from<00:30:20.760> the<00:30:21.000> community<00:30:21.179> as 00:30:21.769 --> 00:30:21.779 align:start position:0% you have Knowledge from the community as 00:30:21.779 --> 00:30:23.630 align:start position:0% you have Knowledge from the community as to<00:30:22.020> how<00:30:22.140> to<00:30:22.320> analyze<00:30:22.799> this<00:30:22.980> and<00:30:23.159> that<00:30:23.340> protocol 00:30:23.630 --> 00:30:23.640 align:start position:0% to how to analyze this and that protocol 00:30:23.640 --> 00:30:25.490 align:start position:0% to how to analyze this and that protocol ever<00:30:24.360> ever<00:30:24.659> you<00:30:25.020> know<00:30:25.140> increasing 00:30:25.490 --> 00:30:25.500 align:start position:0% ever ever you know increasing 00:30:25.500 --> 00:30:27.110 align:start position:0% ever ever you know increasing refinements<00:30:26.220> but<00:30:26.399> then<00:30:26.580> you<00:30:26.700> might<00:30:26.880> store 00:30:27.110 --> 00:30:27.120 align:start position:0% refinements but then you might store 00:30:27.120 --> 00:30:29.210 align:start position:0% refinements but then you might store that<00:30:27.360> in<00:30:27.539> your<00:30:27.720> store<00:30:28.080> with<00:30:28.320> off-chain<00:30:28.860> data 00:30:29.210 --> 00:30:29.220 align:start position:0% that in your store with off-chain data 00:30:29.220 --> 00:30:31.070 align:start position:0% that in your store with off-chain data and<00:30:29.520> maybe<00:30:29.700> that's<00:30:29.940> best<00:30:30.179> fit<00:30:30.480> for<00:30:30.600> you<00:30:30.779> maybe 00:30:31.070 --> 00:30:31.080 align:start position:0% and maybe that's best fit for you maybe 00:30:31.080 --> 00:30:32.630 align:start position:0% and maybe that's best fit for you maybe you<00:30:31.320> feed<00:30:31.440> it<00:30:31.620> into<00:30:31.740> a<00:30:31.919> subgraph<00:30:32.220> that's<00:30:32.460> what 00:30:32.630 --> 00:30:32.640 align:start position:0% you feed it into a subgraph that's what 00:30:32.640 --> 00:30:34.190 align:start position:0% you feed it into a subgraph that's what you<00:30:32.820> need<00:30:33.000> you<00:30:33.240> had<00:30:33.360> a<00:30:33.539> total<00:30:33.720> decentralized 00:30:34.190 --> 00:30:34.200 align:start position:0% you need you had a total decentralized 00:30:34.200 --> 00:30:35.870 align:start position:0% you need you had a total decentralized solution<00:30:34.860> and<00:30:35.159> you<00:30:35.279> don't<00:30:35.399> need<00:30:35.520> to<00:30:35.640> host 00:30:35.870 --> 00:30:35.880 align:start position:0% solution and you don't need to host 00:30:35.880 --> 00:30:38.990 align:start position:0% solution and you don't need to host anything<00:30:36.120> so<00:30:36.960> this<00:30:37.320> is<00:30:37.440> enabler<00:30:37.919> at<00:30:38.399> a<00:30:38.640> lower 00:30:38.990 --> 00:30:39.000 align:start position:0% anything so this is enabler at a lower 00:30:39.000 --> 00:30:40.970 align:start position:0% anything so this is enabler at a lower level<00:30:39.419> it's<00:30:39.720> not<00:30:39.960> a<00:30:40.140> it<00:30:40.380> doesn't<00:30:40.500> seek<00:30:40.860> to 00:30:40.970 --> 00:30:40.980 align:start position:0% level it's not a it doesn't seek to 00:30:40.980 --> 00:30:43.310 align:start position:0% level it's not a it doesn't seek to replace<00:30:41.100> SQL<00:30:41.820> but<00:30:42.299> it<00:30:42.419> puts<00:30:42.720> itself<00:30:42.899> at<00:30:43.200> a 00:30:43.310 --> 00:30:43.320 align:start position:0% replace SQL but it puts itself at a 00:30:43.320 --> 00:30:45.710 align:start position:0% replace SQL but it puts itself at a place<00:30:43.440> where<00:30:43.740> we<00:30:44.220> can<00:30:44.399> feed<00:30:44.700> all<00:30:45.179> the<00:30:45.360> systems 00:30:45.710 --> 00:30:45.720 align:start position:0% place where we can feed all the systems 00:30:45.720 --> 00:30:48.049 align:start position:0% place where we can feed all the systems on<00:30:45.899> Earth<00:30:46.020> with<00:30:46.679> enriched<00:30:47.399> data<00:30:47.640> which<00:30:47.880> you 00:30:48.049 --> 00:30:48.059 align:start position:0% on Earth with enriched data which you 00:30:48.059 --> 00:30:50.269 align:start position:0% on Earth with enriched data which you would<00:30:48.179> need<00:30:48.299> to<00:30:48.419> do<00:30:48.539> in<00:30:48.659> SQL<00:30:49.200> and<00:30:49.320> it's<00:30:49.919> it's 00:30:50.269 --> 00:30:50.279 align:start position:0% would need to do in SQL and it's it's 00:30:50.279 --> 00:30:52.789 align:start position:0% would need to do in SQL and it's it's really<00:30:50.640> not<00:30:50.880> fun<00:30:51.240> so<00:30:51.960> you<00:30:52.080> leave<00:30:52.320> that<00:30:52.500> to<00:30:52.620> the 00:30:52.789 --> 00:30:52.799 align:start position:0% really not fun so you leave that to the 00:30:52.799 --> 00:30:55.549 align:start position:0% really not fun so you leave that to the community<00:30:52.919> right<00:30:53.279> gotcha<00:30:54.059> thank<00:30:54.360> you<00:30:54.480> we<00:30:55.440> have 00:30:55.549 --> 00:30:55.559 align:start position:0% community right gotcha thank you we have 00:30:55.559 --> 00:30:57.409 align:start position:0% community right gotcha thank you we have our<00:30:55.799> old<00:30:55.919> subgraph<00:30:56.520> which<00:30:56.760> is<00:30:56.880> pretty<00:30:57.120> slow 00:30:57.409 --> 00:30:57.419 align:start position:0% our old subgraph which is pretty slow 00:30:57.419 --> 00:31:00.289 align:start position:0% our old subgraph which is pretty slow and<00:30:57.779> we<00:30:57.960> would<00:30:58.140> like<00:30:58.260> to<00:30:58.559> transform<00:30:59.159> it<00:30:59.520> to<00:30:59.700> the 00:31:00.289 --> 00:31:00.299 align:start position:0% and we would like to transform it to the 00:31:00.299 --> 00:31:02.510 align:start position:0% and we would like to transform it to the new<00:31:00.480> type<00:31:00.659> of<00:31:00.779> subcraft<00:31:01.200> Yes<00:31:01.559> Should<00:31:01.860> I<00:31:02.340> only 00:31:02.510 --> 00:31:02.520 align:start position:0% new type of subcraft Yes Should I only 00:31:02.520 --> 00:31:05.330 align:start position:0% new type of subcraft Yes Should I only read<00:31:03.000> some<00:31:03.240> code<00:31:03.539> on<00:31:03.840> Rust<00:31:04.380> and<00:31:04.620> that's<00:31:04.860> it<00:31:05.100> or 00:31:05.330 --> 00:31:05.340 align:start position:0% read some code on Rust and that's it or 00:31:05.340 --> 00:31:07.789 align:start position:0% read some code on Rust and that's it or something<00:31:05.820> else<00:31:06.120> so<00:31:06.960> it<00:31:07.200> is<00:31:07.320> not<00:31:07.500> the<00:31:07.679> same 00:31:07.789 --> 00:31:07.799 align:start position:0% something else so it is not the same 00:31:07.799 --> 00:31:09.169 align:start position:0% something else so it is not the same Paradigm<00:31:08.340> to<00:31:08.460> enable<00:31:08.640> parallelization 00:31:09.169 --> 00:31:09.179 align:start position:0% Paradigm to enable parallelization 00:31:09.179 --> 00:31:11.930 align:start position:0% Paradigm to enable parallelization Nation<00:31:09.600> you<00:31:10.380> need<00:31:10.500> to<00:31:10.740> distinguish<00:31:11.220> the<00:31:11.640> data 00:31:11.930 --> 00:31:11.940 align:start position:0% Nation you need to distinguish the data 00:31:11.940 --> 00:31:13.490 align:start position:0% Nation you need to distinguish the data dependencies<00:31:12.480> and<00:31:12.779> that<00:31:12.840> infers<00:31:13.140> the<00:31:13.320> number 00:31:13.490 --> 00:31:13.500 align:start position:0% dependencies and that infers the number 00:31:13.500 --> 00:31:15.110 align:start position:0% dependencies and that infers the number of<00:31:13.679> stage<00:31:13.980> of<00:31:14.159> parallelization<00:31:14.760> that<00:31:15.000> is 00:31:15.110 --> 00:31:15.120 align:start position:0% of stage of parallelization that is 00:31:15.120 --> 00:31:17.149 align:start position:0% of stage of parallelization that is needed<00:31:15.419> it's<00:31:16.020> not<00:31:16.260> easy<00:31:16.500> at<00:31:16.799> all<00:31:16.919> actually 00:31:17.149 --> 00:31:17.159 align:start position:0% needed it's not easy at all actually 00:31:17.159 --> 00:31:20.269 align:start position:0% needed it's not easy at all actually it's<00:31:17.580> pretty<00:31:18.299> crazy<00:31:18.899> to<00:31:19.380> try<00:31:19.559> to<00:31:19.740> parallelize 00:31:20.269 --> 00:31:20.279 align:start position:0% it's pretty crazy to try to parallelize 00:31:20.279 --> 00:31:22.190 align:start position:0% it's pretty crazy to try to parallelize the<00:31:20.520> subgraphs<00:31:21.000> we<00:31:21.120> try<00:31:21.299> that<00:31:21.480> that's<00:31:21.899> what 00:31:22.190 --> 00:31:22.200 align:start position:0% the subgraphs we try that that's what 00:31:22.200 --> 00:31:24.830 align:start position:0% the subgraphs we try that that's what yield<00:31:22.440> us<00:31:22.679> to<00:31:22.919> design<00:31:23.100> substreams<00:31:24.000> by<00:31:24.360> cutting 00:31:24.830 --> 00:31:24.840 align:start position:0% yield us to design substreams by cutting 00:31:24.840 --> 00:31:28.130 align:start position:0% yield us to design substreams by cutting you<00:31:25.320> know<00:31:25.380> uni<00:31:25.980> swap<00:31:26.279> stuff<00:31:26.580> so<00:31:27.240> you<00:31:27.659> will<00:31:27.779> want 00:31:28.130 --> 00:31:28.140 align:start position:0% you know uni swap stuff so you will want 00:31:28.140 --> 00:31:31.190 align:start position:0% you know uni swap stuff so you will want to<00:31:28.919> go<00:31:29.520> and<00:31:29.760> write<00:31:29.880> in<00:31:30.059> Rust<00:31:30.360> modules<00:31:30.840> and<00:31:31.080> it's 00:31:31.190 --> 00:31:31.200 align:start position:0% to go and write in Rust modules and it's 00:31:31.200 --> 00:31:32.990 align:start position:0% to go and write in Rust modules and it's a<00:31:31.440> different<00:31:31.559> Paradigm<00:31:32.220> so<00:31:32.399> it's<00:31:32.520> not<00:31:32.700> just<00:31:32.880> an 00:31:32.990 --> 00:31:33.000 align:start position:0% a different Paradigm so it's not just an 00:31:33.000 --> 00:31:35.810 align:start position:0% a different Paradigm so it's not just an easy<00:31:33.120> switch<00:31:33.419> I<00:31:33.899> admit<00:31:34.320> but<00:31:34.799> it<00:31:35.100> brings<00:31:35.399> us<00:31:35.520> to 00:31:35.810 --> 00:31:35.820 align:start position:0% easy switch I admit but it brings us to 00:31:35.820 --> 00:31:38.149 align:start position:0% easy switch I admit but it brings us to the<00:31:35.940> next<00:31:36.179> stage<00:31:36.720> an<00:31:37.020> evolution<00:31:37.380> you<00:31:37.740> know<00:31:37.860> of 00:31:38.149 --> 00:31:38.159 align:start position:0% the next stage an evolution you know of 00:31:38.159 --> 00:31:40.909 align:start position:0% the next stage an evolution you know of blockchain<00:31:38.700> index<00:31:39.179> thing<00:31:39.720> yeah<00:31:40.200> I<00:31:40.380> see<00:31:40.559> thanks 00:31:40.909 --> 00:31:40.919 align:start position:0% blockchain index thing yeah I see thanks 00:31:40.919 --> 00:31:44.210 align:start position:0% blockchain index thing yeah I see thanks uh<00:31:41.820> thank<00:31:42.120> you<00:31:42.240> so<00:31:42.539> much<00:31:42.659> Alexander 00:31:44.210 --> 00:31:44.220 align:start position:0% uh thank you so much Alexander 00:31:44.220 --> 00:31:47.120 align:start position:0% uh thank you so much Alexander my<00:31:44.820> pleasure