WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:15.609 align:start position:0% [Applause] 00:00:15.609 --> 00:00:15.619 align:start position:0% 00:00:15.619 --> 00:00:18.109 align:start position:0% trying<00:00:16.619> to<00:00:16.770> show<00:00:16.890> ops<00:00:17.130> or<00:00:17.400> what<00:00:17.609> happens<00:00:18.060> if 00:00:18.109 --> 00:00:18.119 align:start position:0% trying to show ops or what happens if 00:00:18.119 --> 00:00:20.779 align:start position:0% trying to show ops or what happens if this<00:00:18.300> runs<00:00:18.509> successfully<00:00:18.990> for<00:00:19.560> you<00:00:19.710> but<00:00:20.699> if 00:00:20.779 --> 00:00:20.789 align:start position:0% this runs successfully for you but if 00:00:20.789 --> 00:00:21.950 align:start position:0% this runs successfully for you but if you're<00:00:20.939> able<00:00:21.360> to<00:00:21.390> connect<00:00:21.660> to<00:00:21.689> the<00:00:21.840> internet 00:00:21.950 --> 00:00:21.960 align:start position:0% you're able to connect to the internet 00:00:21.960 --> 00:00:25.040 align:start position:0% you're able to connect to the internet and<00:00:22.380> interested<00:00:22.980> in<00:00:23.340> the<00:00:24.090> workshop<00:00:24.599> or<00:00:24.779> style 00:00:25.040 --> 00:00:25.050 align:start position:0% and interested in the workshop or style 00:00:25.050 --> 00:00:29.119 align:start position:0% and interested in the workshop or style component<00:00:25.680> we<00:00:26.399> recommend<00:00:27.649> is<00:00:28.649> because 00:00:29.119 --> 00:00:29.129 align:start position:0% component we recommend is because 00:00:29.129 --> 00:00:31.459 align:start position:0% component we recommend is because pulling<00:00:29.489> down<00:00:29.669> vulcanize<00:00:30.259> checking<00:00:31.259> out<00:00:31.379> the 00:00:31.459 --> 00:00:31.469 align:start position:0% pulling down vulcanize checking out the 00:00:31.469 --> 00:00:33.680 align:start position:0% pulling down vulcanize checking out the branch<00:00:31.710> you've<00:00:31.950> got<00:00:32.129> set<00:00:32.399> up<00:00:32.430> for<00:00:32.850> this 00:00:33.680 --> 00:00:33.690 align:start position:0% branch you've got set up for this 00:00:33.690 --> 00:00:54.050 align:start position:0% branch you've got set up for this process<00:00:34.289> and<00:00:51.680> so<00:00:52.680> yeah<00:00:52.920> you're<00:00:53.670> talking<00:00:53.880> about 00:00:54.050 --> 00:00:54.060 align:start position:0% process and so yeah you're talking about 00:00:54.060 --> 00:00:55.190 align:start position:0% process and so yeah you're talking about multi<00:00:54.540> TV 00:00:55.190 --> 00:00:55.200 align:start position:0% multi TV 00:00:55.200 --> 00:00:57.319 align:start position:0% multi TV my<00:00:55.739> name's<00:00:55.980> Rob<00:00:56.250> Mahone<00:00:56.610> I'm<00:00:56.880> Pete<00:00:57.300> Nelson 00:00:57.319 --> 00:00:57.329 align:start position:0% my name's Rob Mahone I'm Pete Nelson 00:00:57.329 --> 00:01:00.470 align:start position:0% my name's Rob Mahone I'm Pete Nelson would<00:00:57.870> organize<00:00:58.380> multiple<00:00:59.070> software<00:00:59.880> crafter 00:01:00.470 --> 00:01:00.480 align:start position:0% would organize multiple software crafter 00:01:00.480 --> 00:01:02.660 align:start position:0% would organize multiple software crafter at<00:01:00.630> a<00:01:00.780> blend<00:01:01.050> of<00:01:01.110> Chicago<00:01:01.649> and<00:01:02.250> I'm<00:01:02.370> a<00:01:02.460> customer 00:01:02.660 --> 00:01:02.670 align:start position:0% at a blend of Chicago and I'm a customer 00:01:02.670 --> 00:01:03.290 align:start position:0% at a blend of Chicago and I'm a customer here 00:01:03.290 --> 00:01:03.300 align:start position:0% here 00:01:03.300 --> 00:01:09.420 align:start position:0% here I<00:01:03.570> had<00:01:04.530> three<00:01:04.979> likes 00:01:09.420 --> 00:01:09.430 align:start position:0% 00:01:09.430 --> 00:01:13.660 align:start position:0% bring<00:01:10.430> my<00:01:10.579> phone<00:01:10.789> up<00:01:10.939> cool<00:01:11.530> so<00:01:12.530> to<00:01:13.460> get<00:01:13.549> started 00:01:13.660 --> 00:01:13.670 align:start position:0% bring my phone up cool so to get started 00:01:13.670 --> 00:01:15.850 align:start position:0% bring my phone up cool so to get started talking<00:01:14.030> about<00:01:14.420> sort<00:01:14.840> of<00:01:14.899> the<00:01:14.960> motivation<00:01:15.140> for 00:01:15.850 --> 00:01:15.860 align:start position:0% talking about sort of the motivation for 00:01:15.860 --> 00:01:18.880 align:start position:0% talking about sort of the motivation for vulcanized<00:01:16.399> edu<00:01:16.970> I<00:01:17.210> wanted<00:01:18.140> to<00:01:18.229> start<00:01:18.470> talking 00:01:18.880 --> 00:01:18.890 align:start position:0% vulcanized edu I wanted to start talking 00:01:18.890 --> 00:01:21.429 align:start position:0% vulcanized edu I wanted to start talking about<00:01:19.070> sort<00:01:20.000> of<00:01:20.060> where<00:01:20.270> are<00:01:20.450> we<00:01:20.659> now<00:01:20.840> with 00:01:21.429 --> 00:01:21.439 align:start position:0% about sort of where are we now with 00:01:21.439 --> 00:01:24.480 align:start position:0% about sort of where are we now with accessing<00:01:22.310> data<00:01:22.549> in<00:01:23.060> the<00:01:23.299> imperial<00:01:23.810> system 00:01:24.480 --> 00:01:24.490 align:start position:0% accessing data in the imperial system 00:01:24.490 --> 00:01:27.760 align:start position:0% accessing data in the imperial system and<00:01:25.490> from<00:01:25.880> my<00:01:26.060> perspective<00:01:26.390> there's<00:01:27.200> a<00:01:27.409> few 00:01:27.760 --> 00:01:27.770 align:start position:0% and from my perspective there's a few 00:01:27.770 --> 00:01:30.249 align:start position:0% and from my perspective there's a few things<00:01:28.009> to<00:01:28.250> notice<00:01:28.789> one<00:01:29.149> is<00:01:29.299> that<00:01:29.509> can<00:01:30.079> got 00:01:30.249 --> 00:01:30.259 align:start position:0% things to notice one is that can got 00:01:30.259 --> 00:01:32.410 align:start position:0% things to notice one is that can got these<00:01:30.409> decentralized<00:01:31.250> applications<00:01:31.520> but 00:01:32.410 --> 00:01:32.420 align:start position:0% these decentralized applications but 00:01:32.420 --> 00:01:34.870 align:start position:0% these decentralized applications but largely<00:01:33.229> in<00:01:33.710> order<00:01:34.009> for<00:01:34.189> these<00:01:34.250> decentralized 00:01:34.870 --> 00:01:34.880 align:start position:0% largely in order for these decentralized 00:01:34.880 --> 00:01:36.850 align:start position:0% largely in order for these decentralized applications<00:01:35.119> to<00:01:35.780> work<00:01:36.020> we're<00:01:36.439> relying<00:01:36.679> on 00:01:36.850 --> 00:01:36.860 align:start position:0% applications to work we're relying on 00:01:36.860 --> 00:01:39.429 align:start position:0% applications to work we're relying on centralized<00:01:37.460> data<00:01:37.789> right<00:01:38.270> so<00:01:38.509> here<00:01:38.929> I'm 00:01:39.429 --> 00:01:39.439 align:start position:0% centralized data right so here I'm 00:01:39.439 --> 00:01:42.760 align:start position:0% centralized data right so here I'm visited<00:01:39.979> Bulaq<00:01:40.399> now<00:01:40.640> calm<00:01:41.240> and<00:01:41.929> we've<00:01:42.319> got<00:01:42.530> a 00:01:42.760 --> 00:01:42.770 align:start position:0% visited Bulaq now calm and we've got a 00:01:42.770 --> 00:01:44.350 align:start position:0% visited Bulaq now calm and we've got a bunch<00:01:42.920> of<00:01:43.069> network<00:01:43.399> requests<00:01:43.789> going<00:01:44.119> to<00:01:44.240> in 00:01:44.350 --> 00:01:44.360 align:start position:0% bunch of network requests going to in 00:01:44.360 --> 00:01:47.679 align:start position:0% bunch of network requests going to in Fura<00:01:44.720> do<00:01:45.110> you<00:01:45.259> access<00:01:45.740> the<00:01:46.729> latest<00:01:47.060> state<00:01:47.330> of 00:01:47.679 --> 00:01:47.689 align:start position:0% Fura do you access the latest state of 00:01:47.689 --> 00:01:50.649 align:start position:0% Fura do you access the latest state of the<00:01:48.590> bhulok<00:01:49.099> contracts<00:01:49.819> and<00:01:50.060> that's<00:01:50.360> pretty 00:01:50.649 --> 00:01:50.659 align:start position:0% the bhulok contracts and that's pretty 00:01:50.659 --> 00:01:52.809 align:start position:0% the bhulok contracts and that's pretty cool<00:01:50.869> like<00:01:51.289> it<00:01:51.439> works<00:01:51.709> and<00:01:52.069> it's<00:01:52.429> awesome 00:01:52.809 --> 00:01:52.819 align:start position:0% cool like it works and it's awesome 00:01:52.819 --> 00:01:55.179 align:start position:0% cool like it works and it's awesome doesent<00:01:53.119> here<00:01:53.299> provides<00:01:53.720> the<00:01:53.929> service<00:01:54.319> but 00:01:55.179 --> 00:01:55.189 align:start position:0% doesent here provides the service but 00:01:55.189 --> 00:01:57.669 align:start position:0% doesent here provides the service but ideally<00:01:55.670> you<00:01:56.330> know<00:01:56.420> we<00:01:56.569> might<00:01:56.750> have<00:01:56.780> solutions 00:01:57.669 --> 00:01:57.679 align:start position:0% ideally you know we might have solutions 00:01:57.679 --> 00:02:00.669 align:start position:0% ideally you know we might have solutions that<00:01:57.890> didn't<00:01:58.610> depend<00:01:58.759> on<00:01:59.149> one<00:01:59.420> third<00:02:00.110> party<00:02:00.560> to 00:02:00.669 --> 00:02:00.679 align:start position:0% that didn't depend on one third party to 00:02:00.679 --> 00:02:05.620 align:start position:0% that didn't depend on one third party to service<00:02:01.069> that<00:02:01.280> data<00:02:03.159> so<00:02:04.159> in<00:02:04.459> addition<00:02:04.640> to<00:02:05.090> sort 00:02:05.620 --> 00:02:05.630 align:start position:0% service that data so in addition to sort 00:02:05.630 --> 00:02:08.490 align:start position:0% service that data so in addition to sort of<00:02:05.750> centralization<00:02:06.349> around<00:02:07.250> access<00:02:07.759> to<00:02:07.939> data 00:02:08.490 --> 00:02:08.500 align:start position:0% of centralization around access to data 00:02:08.500 --> 00:02:10.749 align:start position:0% of centralization around access to data another<00:02:09.500> thing<00:02:09.709> we've<00:02:09.890> got<00:02:10.099> is<00:02:10.340> that<00:02:10.399> we've 00:02:10.749 --> 00:02:10.759 align:start position:0% another thing we've got is that we've 00:02:10.759 --> 00:02:13.150 align:start position:0% another thing we've got is that we've got<00:02:10.970> a<00:02:11.209> lot<00:02:11.420> of<00:02:11.450> duplicated<00:02:12.170> effort<00:02:12.530> right<00:02:12.859> so 00:02:13.150 --> 00:02:13.160 align:start position:0% got a lot of duplicated effort right so 00:02:13.160 --> 00:02:14.979 align:start position:0% got a lot of duplicated effort right so when<00:02:13.640> I<00:02:13.670> have<00:02:13.819> spoken<00:02:14.180> with<00:02:14.450> people<00:02:14.660> about 00:02:14.979 --> 00:02:14.989 align:start position:0% when I have spoken with people about 00:02:14.989 --> 00:02:16.990 align:start position:0% when I have spoken with people about what<00:02:15.049> can<00:02:15.380> I<00:02:15.470> teach<00:02:15.709> in<00:02:15.950> the<00:02:16.069> hallway<00:02:16.430> I<00:02:16.670> think 00:02:16.990 --> 00:02:17.000 align:start position:0% what can I teach in the hallway I think 00:02:17.000 --> 00:02:18.970 align:start position:0% what can I teach in the hallway I think one<00:02:17.150> of<00:02:17.239> the<00:02:17.299> like<00:02:17.450> most<00:02:17.720> common<00:02:18.350> comments<00:02:18.890> I 00:02:18.970 --> 00:02:18.980 align:start position:0% one of the like most common comments I 00:02:18.980 --> 00:02:20.949 align:start position:0% one of the like most common comments I get<00:02:19.160> is<00:02:19.310> like<00:02:19.489> oh<00:02:19.730> that<00:02:20.209> sounds<00:02:20.569> really<00:02:20.750> great 00:02:20.949 --> 00:02:20.959 align:start position:0% get is like oh that sounds really great 00:02:20.959 --> 00:02:22.390 align:start position:0% get is like oh that sounds really great like<00:02:21.140> we<00:02:21.290> had<00:02:21.380> to<00:02:21.500> build<00:02:21.620> something<00:02:21.920> like<00:02:22.100> that 00:02:22.390 --> 00:02:22.400 align:start position:0% like we had to build something like that 00:02:22.400 --> 00:02:23.710 align:start position:0% like we had to build something like that in<00:02:22.609> house<00:02:22.850> to<00:02:23.180> support<00:02:23.540> our<00:02:23.690> own 00:02:23.710 --> 00:02:23.720 align:start position:0% in house to support our own 00:02:23.720 --> 00:02:27.129 align:start position:0% in house to support our own infrastructure<00:02:24.380> right<00:02:25.160> so<00:02:25.690> it's<00:02:26.690> amazing<00:02:26.900> to 00:02:27.129 --> 00:02:27.139 align:start position:0% infrastructure right so it's amazing to 00:02:27.139 --> 00:02:28.720 align:start position:0% infrastructure right so it's amazing to me<00:02:27.380> how<00:02:27.410> many<00:02:27.650> teams<00:02:28.069> have<00:02:28.340> sort<00:02:28.549> of<00:02:28.609> gone 00:02:28.720 --> 00:02:28.730 align:start position:0% me how many teams have sort of gone 00:02:28.730 --> 00:02:30.460 align:start position:0% me how many teams have sort of gone through<00:02:28.790> this<00:02:29.180> work<00:02:29.420> of<00:02:29.690> figuring<00:02:30.109> out<00:02:30.230> how<00:02:30.410> to 00:02:30.460 --> 00:02:30.470 align:start position:0% through this work of figuring out how to 00:02:30.470 --> 00:02:32.289 align:start position:0% through this work of figuring out how to like<00:02:30.650> extract<00:02:31.100> data<00:02:31.310> from<00:02:31.519> an<00:02:31.730> a3<00:02:32.030> of<00:02:32.120> node 00:02:32.289 --> 00:02:32.299 align:start position:0% like extract data from an a3 of node 00:02:32.299 --> 00:02:33.440 align:start position:0% like extract data from an a3 of node decoded 00:02:33.440 --> 00:02:33.450 align:start position:0% decoded 00:02:33.450 --> 00:02:35.930 align:start position:0% decoded those<00:02:33.569> rest<00:02:33.840> database<00:02:34.200> but<00:02:34.950> the<00:02:35.400> fact<00:02:35.640> that<00:02:35.730> so 00:02:35.930 --> 00:02:35.940 align:start position:0% those rest database but the fact that so 00:02:35.940 --> 00:02:37.850 align:start position:0% those rest database but the fact that so many<00:02:36.060> people<00:02:36.180> are<00:02:36.480> doing<00:02:36.660> it<00:02:36.930> sort<00:02:37.500> of<00:02:37.530> raises 00:02:37.850 --> 00:02:37.860 align:start position:0% many people are doing it sort of raises 00:02:37.860 --> 00:02:39.800 align:start position:0% many people are doing it sort of raises the<00:02:37.950> obvious<00:02:38.069> question<00:02:38.670> of<00:02:38.849> like<00:02:39.030> why<00:02:39.569> don't 00:02:39.800 --> 00:02:39.810 align:start position:0% the obvious question of like why don't 00:02:39.810 --> 00:02:43.970 align:start position:0% the obvious question of like why don't we<00:02:39.959> have<00:02:40.110> a<00:02:40.140> shared<00:02:40.410> tool<00:02:40.650> set<00:02:40.860> for<00:02:40.890> that<00:02:42.200> I<00:02:43.200> did 00:02:43.970 --> 00:02:43.980 align:start position:0% we have a shared tool set for that I did 00:02:43.980 --> 00:02:45.979 align:start position:0% we have a shared tool set for that I did want<00:02:44.130> to<00:02:44.250> mention<00:02:44.400> that<00:02:44.910> there's<00:02:45.300> a<00:02:45.450> lot<00:02:45.840> of 00:02:45.979 --> 00:02:45.989 align:start position:0% want to mention that there's a lot of 00:02:45.989 --> 00:02:48.229 align:start position:0% want to mention that there's a lot of teams<00:02:46.290> doing<00:02:46.620> great<00:02:46.950> work<00:02:47.190> to<00:02:47.489> address<00:02:47.910> these 00:02:48.229 --> 00:02:48.239 align:start position:0% teams doing great work to address these 00:02:48.239 --> 00:02:50.030 align:start position:0% teams doing great work to address these two<00:02:48.540> issues<00:02:48.660> right<00:02:49.080> so<00:02:49.290> that<00:02:49.530> the<00:02:49.680> question<00:02:49.980> of 00:02:50.030 --> 00:02:50.040 align:start position:0% two issues right so that the question of 00:02:50.040 --> 00:02:52.160 align:start position:0% two issues right so that the question of centralization<00:02:50.700> of<00:02:50.760> duplicate<00:02:51.180> endeavour<00:02:51.450> we 00:02:52.160 --> 00:02:52.170 align:start position:0% centralization of duplicate endeavour we 00:02:52.170 --> 00:02:54.170 align:start position:0% centralization of duplicate endeavour we see<00:02:52.319> a<00:02:52.890> ton<00:02:53.190> of<00:02:53.250> teams<00:02:53.520> out<00:02:53.700> there<00:02:53.910> making 00:02:54.170 --> 00:02:54.180 align:start position:0% see a ton of teams out there making 00:02:54.180 --> 00:02:56.330 align:start position:0% see a ton of teams out there making progress<00:02:54.540> to<00:02:55.200> try<00:02:55.830> and<00:02:56.010> improve<00:02:56.280> the 00:02:56.330 --> 00:02:56.340 align:start position:0% progress to try and improve the 00:02:56.340 --> 00:02:59.930 align:start position:0% progress to try and improve the situation<00:02:57.200> and<00:02:58.400> you<00:02:59.400> know<00:02:59.489> I<00:02:59.550> think<00:02:59.610> that's 00:02:59.930 --> 00:02:59.940 align:start position:0% situation and you know I think that's 00:02:59.940 --> 00:03:01.550 align:start position:0% situation and you know I think that's super<00:03:00.090> awesome<00:03:00.300> I<00:03:00.780> really<00:03:01.019> have<00:03:01.200> to<00:03:01.290> be<00:03:01.500> able 00:03:01.550 --> 00:03:01.560 align:start position:0% super awesome I really have to be able 00:03:01.560 --> 00:03:04.490 align:start position:0% super awesome I really have to be able to<00:03:01.819> you<00:03:02.819> know<00:03:02.880> here<00:03:03.150> at<00:03:03.239> DEFCON<00:03:03.660> like<00:03:03.900> see<00:03:04.140> what 00:03:04.490 --> 00:03:04.500 align:start position:0% to you know here at DEFCON like see what 00:03:04.500 --> 00:03:06.199 align:start position:0% to you know here at DEFCON like see what other<00:03:04.620> people<00:03:04.980> are<00:03:05.040> feeling<00:03:05.099> and<00:03:05.580> from<00:03:06.060> that 00:03:06.199 --> 00:03:06.209 align:start position:0% other people are feeling and from that 00:03:06.209 --> 00:03:07.520 align:start position:0% other people are feeling and from that something<00:03:06.720> you<00:03:06.810> can<00:03:06.900> all<00:03:07.050> learn<00:03:07.200> from<00:03:07.260> each 00:03:07.520 --> 00:03:07.530 align:start position:0% something you can all learn from each 00:03:07.530 --> 00:03:08.000 align:start position:0% something you can all learn from each other 00:03:08.000 --> 00:03:08.010 align:start position:0% other 00:03:08.010 --> 00:03:09.680 align:start position:0% other but<00:03:08.489> I<00:03:08.640> think<00:03:08.850> the<00:03:09.000> fact<00:03:09.300> that<00:03:09.450> you've<00:03:09.660> got 00:03:09.680 --> 00:03:09.690 align:start position:0% but I think the fact that you've got 00:03:09.690 --> 00:03:13.160 align:start position:0% but I think the fact that you've got this<00:03:10.200> many<00:03:10.890> organizations<00:03:11.819> all<00:03:12.150> working<00:03:12.750> on 00:03:13.160 --> 00:03:13.170 align:start position:0% this many organizations all working on 00:03:13.170 --> 00:03:15.229 align:start position:0% this many organizations all working on like<00:03:13.350> this<00:03:13.560> shared<00:03:14.130> problem<00:03:14.760> sort<00:03:15.180> of 00:03:15.229 --> 00:03:15.239 align:start position:0% like this shared problem sort of 00:03:15.239 --> 00:03:17.180 align:start position:0% like this shared problem sort of indicates<00:03:15.720> the<00:03:15.959> the<00:03:16.230> magnitude<00:03:16.799> of<00:03:16.920> the<00:03:17.069> issue 00:03:17.180 --> 00:03:17.190 align:start position:0% indicates the the magnitude of the issue 00:03:17.190 --> 00:03:20.690 align:start position:0% indicates the the magnitude of the issue and<00:03:17.730> the<00:03:18.239> rationale<00:03:18.690> for<00:03:19.019> having<00:03:19.700> improved 00:03:20.690 --> 00:03:20.700 align:start position:0% and the rationale for having improved 00:03:20.700 --> 00:03:25.250 align:start position:0% and the rationale for having improved toolset<00:03:21.860> and<00:03:22.860> so<00:03:23.750> with<00:03:24.750> that<00:03:24.900> sort<00:03:25.140> of 00:03:25.250 --> 00:03:25.260 align:start position:0% toolset and so with that sort of 00:03:25.260 --> 00:03:27.710 align:start position:0% toolset and so with that sort of motivation<00:03:25.620> in<00:03:26.190> mind<00:03:26.519> the<00:03:27.239> question<00:03:27.569> I<00:03:27.600> want 00:03:27.710 --> 00:03:27.720 align:start position:0% motivation in mind the question I want 00:03:27.720 --> 00:03:28.910 align:start position:0% motivation in mind the question I want to<00:03:27.780> propose<00:03:28.049> is<00:03:28.290> so<00:03:28.440> like<00:03:28.590> where<00:03:28.769> are<00:03:28.830> we 00:03:28.910 --> 00:03:28.920 align:start position:0% to propose is so like where are we 00:03:28.920 --> 00:03:32.420 align:start position:0% to propose is so like where are we headed<00:03:29.250> and<00:03:29.459> with<00:03:30.239> vulcanize<00:03:30.690> DB<00:03:31.140> I<00:03:31.440> would<00:03:32.250> say 00:03:32.420 --> 00:03:32.430 align:start position:0% headed and with vulcanize DB I would say 00:03:32.430 --> 00:03:34.930 align:start position:0% headed and with vulcanize DB I would say that<00:03:32.730> our<00:03:32.970> mission<00:03:33.209> is<00:03:33.630> to<00:03:33.870> replace 00:03:34.930 --> 00:03:34.940 align:start position:0% that our mission is to replace 00:03:34.940 --> 00:03:37.309 align:start position:0% that our mission is to replace decentralized<00:03:35.940> and<00:03:36.239> misspoke<00:03:36.660> solutions 00:03:37.309 --> 00:03:37.319 align:start position:0% decentralized and misspoke solutions 00:03:37.319 --> 00:03:40.300 align:start position:0% decentralized and misspoke solutions with<00:03:37.560> shared<00:03:37.890> tooling<00:03:38.370> that<00:03:38.640> anyone<00:03:39.299> can<00:03:39.540> run 00:03:40.300 --> 00:03:40.310 align:start position:0% with shared tooling that anyone can run 00:03:40.310 --> 00:03:44.960 align:start position:0% with shared tooling that anyone can run and<00:03:41.310> so<00:03:42.150> if<00:03:42.720> we<00:03:42.900> look<00:03:43.079> at<00:03:43.170> the<00:03:43.350> toolbox<00:03:44.250> of<00:03:44.549> sort 00:03:44.960 --> 00:03:44.970 align:start position:0% and so if we look at the toolbox of sort 00:03:44.970 --> 00:03:47.349 align:start position:0% and so if we look at the toolbox of sort of<00:03:45.060> what<00:03:45.299> we<00:03:45.480> started<00:03:46.230> been<00:03:46.410> developing<00:03:46.920> to 00:03:47.349 --> 00:03:47.359 align:start position:0% of what we started been developing to 00:03:47.359 --> 00:03:50.060 align:start position:0% of what we started been developing to make<00:03:48.359> this<00:03:48.540> happen<00:03:48.810> I<00:03:49.170> wanted<00:03:49.799> to<00:03:49.890> walk 00:03:50.060 --> 00:03:50.070 align:start position:0% make this happen I wanted to walk 00:03:50.070 --> 00:03:51.830 align:start position:0% make this happen I wanted to walk through<00:03:50.370> a<00:03:50.790> few<00:03:51.120> different<00:03:51.480> things<00:03:51.570> in<00:03:51.720> our 00:03:51.830 --> 00:03:51.840 align:start position:0% through a few different things in our 00:03:51.840 --> 00:03:53.690 align:start position:0% through a few different things in our tool<00:03:52.109> chain<00:03:52.140> that<00:03:52.530> you<00:03:52.590> can<00:03:52.859> use<00:03:53.070> like<00:03:53.519> right 00:03:53.690 --> 00:03:53.700 align:start position:0% tool chain that you can use like right 00:03:53.700 --> 00:03:57.020 align:start position:0% tool chain that you can use like right now<00:03:53.880> to<00:03:54.859> start<00:03:55.859> spending<00:03:56.280> on<00:03:56.370> curtains<00:03:56.730> it's<00:03:56.940> a 00:03:57.020 --> 00:03:57.030 align:start position:0% now to start spending on curtains it's a 00:03:57.030 --> 00:04:00.710 align:start position:0% now to start spending on curtains it's a vulcanized<00:03:57.359> Evie<00:03:57.810> and<00:03:59.000> owning<00:04:00.000> your<00:04:00.120> own<00:04:00.180> your 00:04:00.710 --> 00:04:00.720 align:start position:0% vulcanized Evie and owning your own your 00:04:00.720 --> 00:04:02.390 align:start position:0% vulcanized Evie and owning your own your own<00:04:00.750> data<00:04:01.140> do<00:04:01.500> you<00:04:01.590> able<00:04:01.829> to<00:04:01.859> serve<00:04:02.100> it<00:04:02.220> for 00:04:02.390 --> 00:04:02.400 align:start position:0% own data do you able to serve it for 00:04:02.400 --> 00:04:05.180 align:start position:0% own data do you able to serve it for yourself<00:04:02.760> so<00:04:03.000> I'll<00:04:03.780> walk<00:04:03.959> through<00:04:04.019> each<00:04:04.829> of 00:04:05.180 --> 00:04:05.190 align:start position:0% yourself so I'll walk through each of 00:04:05.190 --> 00:04:09.830 align:start position:0% yourself so I'll walk through each of these<00:04:05.430> in<00:04:05.790> more<00:04:06.000> detail<00:04:07.400> so<00:04:08.400> the<00:04:08.840> foundation 00:04:09.830 --> 00:04:09.840 align:start position:0% these in more detail so the foundation 00:04:09.840 --> 00:04:12.319 align:start position:0% these in more detail so the foundation of<00:04:10.260> the<00:04:10.530> process<00:04:11.040> for<00:04:11.430> setting<00:04:11.880> up<00:04:12.090> of<00:04:12.209> all 00:04:12.319 --> 00:04:12.329 align:start position:0% of the process for setting up of all 00:04:12.329 --> 00:04:14.509 align:start position:0% of the process for setting up of all kinds<00:04:12.359> deviant<00:04:13.019> DB<00:04:13.410> instance<00:04:13.590> we've<00:04:14.070> got<00:04:14.280> this 00:04:14.509 --> 00:04:14.519 align:start position:0% kinds deviant DB instance we've got this 00:04:14.519 --> 00:04:16.729 align:start position:0% kinds deviant DB instance we've got this hetero<00:04:14.880> snake<00:04:15.150> process<00:04:15.660> and<00:04:15.900> what<00:04:16.470> the 00:04:16.729 --> 00:04:16.739 align:start position:0% hetero snake process and what the 00:04:16.739 --> 00:04:18.650 align:start position:0% hetero snake process and what the henderson<00:04:17.160> process<00:04:17.640> does<00:04:17.880> we're<00:04:18.239> basically 00:04:18.650 --> 00:04:18.660 align:start position:0% henderson process does we're basically 00:04:18.660 --> 00:04:21.879 align:start position:0% henderson process does we're basically taking<00:04:19.289> clock<00:04:19.919> headers<00:04:20.340> out<00:04:20.609> of<00:04:20.820> your<00:04:20.940> node 00:04:21.879 --> 00:04:21.889 align:start position:0% taking clock headers out of your node 00:04:21.889 --> 00:04:24.580 align:start position:0% taking clock headers out of your node Postgres<00:04:22.580> you<00:04:23.389> can<00:04:23.569> configure<00:04:23.900> a<00:04:24.050> starting 00:04:24.580 --> 00:04:24.590 align:start position:0% Postgres you can configure a starting 00:04:24.590 --> 00:04:26.529 align:start position:0% Postgres you can configure a starting block<00:04:24.680> so<00:04:25.159> if<00:04:25.490> you<00:04:25.699> only<00:04:25.999> care<00:04:26.330> about<00:04:26.360> a 00:04:26.529 --> 00:04:26.539 align:start position:0% block so if you only care about a 00:04:26.539 --> 00:04:28.809 align:start position:0% block so if you only care about a contract<00:04:27.080> that<00:04:27.199> was<00:04:27.289> deployed<00:04:27.680> a<00:04:28.039> block<00:04:28.610> you 00:04:28.809 --> 00:04:28.819 align:start position:0% contract that was deployed a block you 00:04:28.819 --> 00:04:30.700 align:start position:0% contract that was deployed a block you know<00:04:28.909> seven<00:04:29.240> and<00:04:29.330> a<00:04:29.360> half<00:04:29.419> million<00:04:29.780> then<00:04:30.469> you 00:04:30.700 --> 00:04:30.710 align:start position:0% know seven and a half million then you 00:04:30.710 --> 00:04:32.439 align:start position:0% know seven and a half million then you can<00:04:30.889> start<00:04:31.129> syncing<00:04:31.580> headers<00:04:31.879> into<00:04:32.210> your 00:04:32.439 --> 00:04:32.449 align:start position:0% can start syncing headers into your 00:04:32.449 --> 00:04:34.749 align:start position:0% can start syncing headers into your instance<00:04:32.840> from<00:04:33.289> that<00:04:33.499> individual<00:04:34.370> starting 00:04:34.749 --> 00:04:34.759 align:start position:0% instance from that individual starting 00:04:34.759 --> 00:04:37.209 align:start position:0% instance from that individual starting block<00:04:34.969> and<00:04:35.240> what<00:04:35.840> this<00:04:35.990> process<00:04:36.439> will<00:04:36.710> do<00:04:36.919> is 00:04:37.209 --> 00:04:37.219 align:start position:0% block and what this process will do is 00:04:37.219 --> 00:04:41.589 align:start position:0% block and what this process will do is it<00:04:37.879> will<00:04:37.909> able<00:04:38.330> you<00:04:38.509> to<00:04:39.969> continually<00:04:40.969> verify 00:04:41.589 --> 00:04:41.599 align:start position:0% it will able you to continually verify 00:04:41.599 --> 00:04:44.409 align:start position:0% it will able you to continually verify those<00:04:42.409> headers<00:04:42.770> at<00:04:43.129> a<00:04:43.159> configurable<00:04:43.759> depth<00:04:44.120> so 00:04:44.409 --> 00:04:44.419 align:start position:0% those headers at a configurable depth so 00:04:44.419 --> 00:04:46.809 align:start position:0% those headers at a configurable depth so depending<00:04:44.840> on<00:04:44.990> what<00:04:45.710> your<00:04:45.919> concern<00:04:46.400> is<00:04:46.430> about 00:04:46.809 --> 00:04:46.819 align:start position:0% depending on what your concern is about 00:04:46.819 --> 00:04:48.640 align:start position:0% depending on what your concern is about reorg<00:04:47.270> and<00:04:47.569> so<00:04:47.689> forth<00:04:47.990> you<00:04:48.199> can<00:04:48.349> have<00:04:48.499> this 00:04:48.640 --> 00:04:48.650 align:start position:0% reorg and so forth you can have this 00:04:48.650 --> 00:04:50.890 align:start position:0% reorg and so forth you can have this foundation<00:04:49.279> of<00:04:49.370> data<00:04:49.580> that's<00:04:50.240> continually 00:04:50.890 --> 00:04:50.900 align:start position:0% foundation of data that's continually 00:04:50.900 --> 00:04:54.939 align:start position:0% foundation of data that's continually being<00:04:51.080> validated<00:04:51.999> and<00:04:52.999> where<00:04:53.569> data<00:04:54.409> that's<00:04:54.710> no 00:04:54.939 --> 00:04:54.949 align:start position:0% being validated and where data that's no 00:04:54.949 --> 00:04:57.159 align:start position:0% being validated and where data that's no longer<00:04:55.400> on<00:04:55.789> the<00:04:56.000> chain<00:04:56.210> if<00:04:56.419> there<00:04:56.599> was<00:04:56.689> a<00:04:56.779> reorg 00:04:57.159 --> 00:04:57.169 align:start position:0% longer on the chain if there was a reorg 00:04:57.169 --> 00:04:58.809 align:start position:0% longer on the chain if there was a reorg or<00:04:57.289> something<00:04:57.590> like<00:04:57.710> that<00:04:57.770> is<00:04:58.430> going<00:04:58.639> to<00:04:58.729> be 00:04:58.809 --> 00:04:58.819 align:start position:0% or something like that is going to be 00:04:58.819 --> 00:05:01.059 align:start position:0% or something like that is going to be automatically<00:04:59.389> pruned<00:04:59.779> for<00:05:00.080> you<00:05:00.229> so<00:05:00.830> you<00:05:00.889> know 00:05:01.059 --> 00:05:01.069 align:start position:0% automatically pruned for you so you know 00:05:01.069 --> 00:05:02.709 align:start position:0% automatically pruned for you so you know you<00:05:01.129> have<00:05:01.460> a<00:05:01.490> consistent<00:05:02.120> record<00:05:02.240> of<00:05:02.539> just 00:05:02.709 --> 00:05:02.719 align:start position:0% you have a consistent record of just 00:05:02.719 --> 00:05:04.029 align:start position:0% you have a consistent record of just like<00:05:02.840> what<00:05:03.050> are<00:05:03.080> the<00:05:03.349> headers<00:05:03.590> that<00:05:03.800> were<00:05:03.919> on 00:05:04.029 --> 00:05:04.039 align:start position:0% like what are the headers that were on 00:05:04.039 --> 00:05:06.490 align:start position:0% like what are the headers that were on the<00:05:04.189> chain<00:05:04.400> and<00:05:04.840> importantly<00:05:05.840> for<00:05:06.169> some<00:05:06.409> of 00:05:06.490 --> 00:05:06.500 align:start position:0% the chain and importantly for some of 00:05:06.500 --> 00:05:08.589 align:start position:0% the chain and importantly for some of that<00:05:06.620> additional<00:05:07.159> tools<00:05:07.400> I'll<00:05:07.580> discuss<00:05:07.939> you 00:05:08.589 --> 00:05:08.599 align:start position:0% that additional tools I'll discuss you 00:05:08.599 --> 00:05:10.600 align:start position:0% that additional tools I'll discuss you know<00:05:08.689> we<00:05:08.840> have<00:05:09.020> form<00:05:09.529> D<00:05:09.770> relationship<00:05:10.340> between 00:05:10.600 --> 00:05:10.610 align:start position:0% know we have form D relationship between 00:05:10.610 --> 00:05:12.700 align:start position:0% know we have form D relationship between this<00:05:10.909> block<00:05:11.180> header<00:05:11.449> and<00:05:11.840> all<00:05:12.139> the<00:05:12.349> nested 00:05:12.700 --> 00:05:12.710 align:start position:0% this block header and all the nested 00:05:12.710 --> 00:05:15.100 align:start position:0% this block header and all the nested data<00:05:12.860> such<00:05:13.639> that<00:05:13.879> you<00:05:14.089> can<00:05:14.240> sort<00:05:14.449> of<00:05:14.569> cascade 00:05:15.100 --> 00:05:15.110 align:start position:0% data such that you can sort of cascade 00:05:15.110 --> 00:05:17.679 align:start position:0% data such that you can sort of cascade remove<00:05:15.560> any<00:05:15.939> any<00:05:16.939> game<00:05:17.150> that<00:05:17.180> you<00:05:17.389> have<00:05:17.419> in 00:05:17.679 --> 00:05:17.689 align:start position:0% remove any any game that you have in 00:05:17.689 --> 00:05:19.809 align:start position:0% remove any any game that you have in your<00:05:17.810> system<00:05:18.020> there's<00:05:18.800> a<00:05:18.919> product<00:05:19.219> of<00:05:19.610> a 00:05:19.809 --> 00:05:19.819 align:start position:0% your system there's a product of a 00:05:19.819 --> 00:05:25.689 align:start position:0% your system there's a product of a header<00:05:20.749> that<00:05:20.839> was<00:05:21.050> removed<00:05:23.110> so<00:05:24.430> the<00:05:25.430> thing<00:05:25.610> I 00:05:25.689 --> 00:05:25.699 align:start position:0% header that was removed so the thing I 00:05:25.699 --> 00:05:27.490 align:start position:0% header that was removed so the thing I wanted<00:05:25.939> to<00:05:26.000> talk<00:05:26.180> about<00:05:26.479> today<00:05:26.810> and<00:05:27.020> the<00:05:27.349> thing 00:05:27.490 --> 00:05:27.500 align:start position:0% wanted to talk about today and the thing 00:05:27.500 --> 00:05:29.110 align:start position:0% wanted to talk about today and the thing that<00:05:27.529> the<00:05:27.740> exercise<00:05:28.219> will<00:05:28.430> let<00:05:28.550> you<00:05:28.639> to<00:05:28.729> run<00:05:28.909> is 00:05:29.110 --> 00:05:29.120 align:start position:0% that the exercise will let you to run is 00:05:29.120 --> 00:05:33.010 align:start position:0% that the exercise will let you to run is then<00:05:29.330> contract<00:05:30.289> watcher<00:05:30.710> process<00:05:31.219> and<00:05:31.490> so<00:05:32.020> we 00:05:33.010 --> 00:05:33.020 align:start position:0% then contract watcher process and so we 00:05:33.020 --> 00:05:34.629 align:start position:0% then contract watcher process and so we think<00:05:33.169> the<00:05:33.289> contract<00:05:33.710> Watchers<00:05:34.129> pretty<00:05:34.400> neat 00:05:34.629 --> 00:05:34.639 align:start position:0% think the contract Watchers pretty neat 00:05:34.639 --> 00:05:37.899 align:start position:0% think the contract Watchers pretty neat what<00:05:35.629> it<00:05:35.750> does<00:05:35.960> is<00:05:36.349> basically<00:05:36.710> you<00:05:37.279> give<00:05:37.460> us<00:05:37.639> a 00:05:37.899 --> 00:05:37.909 align:start position:0% what it does is basically you give us a 00:05:37.909 --> 00:05:41.920 align:start position:0% what it does is basically you give us a address<00:05:38.599> for<00:05:39.409> a<00:05:39.680> contract<00:05:40.129> and<00:05:40.569> you<00:05:41.569> tell<00:05:41.779> us 00:05:41.920 --> 00:05:41.930 align:start position:0% address for a contract and you tell us 00:05:41.930 --> 00:05:43.809 align:start position:0% address for a contract and you tell us the<00:05:42.080> deployment<00:05:42.560> block<00:05:42.710> of<00:05:42.919> that<00:05:43.310> contract 00:05:43.809 --> 00:05:43.819 align:start position:0% the deployment block of that contract 00:05:43.819 --> 00:05:47.079 align:start position:0% the deployment block of that contract and<00:05:44.300> then<00:05:44.750> we<00:05:45.080> will<00:05:45.259> automatically<00:05:46.129> figure 00:05:47.079 --> 00:05:47.089 align:start position:0% and then we will automatically figure 00:05:47.089 --> 00:05:48.909 align:start position:0% and then we will automatically figure out<00:05:47.210> what<00:05:47.569> are<00:05:47.689> the<00:05:47.779> events<00:05:47.990> on<00:05:48.229> this<00:05:48.379> contract 00:05:48.909 --> 00:05:48.919 align:start position:0% out what are the events on this contract 00:05:48.919 --> 00:05:50.619 align:start position:0% out what are the events on this contract start<00:05:49.339> getting<00:05:49.939> them<00:05:50.060> off<00:05:50.180> the<00:05:50.360> chain<00:05:50.599> and 00:05:50.619 --> 00:05:50.629 align:start position:0% start getting them off the chain and 00:05:50.629 --> 00:05:53.529 align:start position:0% start getting them off the chain and decoding<00:05:51.469> them<00:05:51.620> for<00:05:51.889> you<00:05:52.069> you<00:05:52.729> can<00:05:53.270> run<00:05:53.449> the 00:05:53.529 --> 00:05:53.539 align:start position:0% decoding them for you you can run the 00:05:53.539 --> 00:05:55.689 align:start position:0% decoding them for you you can run the contract<00:05:53.990> watcher<00:05:54.319> with<00:05:54.560> multiple<00:05:55.099> contracts 00:05:55.689 --> 00:05:55.699 align:start position:0% contract watcher with multiple contracts 00:05:55.699 --> 00:05:57.760 align:start position:0% contract watcher with multiple contracts role<00:05:56.240> we'll<00:05:56.419> create<00:05:56.629> a<00:05:56.719> schema<00:05:57.199> for<00:05:57.229> each<00:05:57.500> one 00:05:57.760 --> 00:05:57.770 align:start position:0% role we'll create a schema for each one 00:05:57.770 --> 00:06:00.459 align:start position:0% role we'll create a schema for each one and<00:05:58.099> a<00:05:58.490> table<00:05:58.849> for<00:05:59.060> each<00:05:59.120> event<00:05:59.270> those<00:06:00.139> event 00:06:00.459 --> 00:06:00.469 align:start position:0% and a table for each event those event 00:06:00.469 --> 00:06:02.580 align:start position:0% and a table for each event those event and<00:06:00.770> end<00:06:00.979> up<00:06:01.189> in<00:06:01.399> Postgres<00:06:01.729> will<00:06:02.149> be 00:06:02.580 --> 00:06:02.590 align:start position:0% and end up in Postgres will be 00:06:02.590 --> 00:06:04.020 align:start position:0% and end up in Postgres will be with<00:06:02.980> the<00:06:03.070> headers<00:06:03.340> such<00:06:03.580> that<00:06:03.820> that 00:06:04.020 --> 00:06:04.030 align:start position:0% with the headers such that that 00:06:04.030 --> 00:06:05.550 align:start position:0% with the headers such that that interesting<00:06:04.480> process<00:06:04.930> is<00:06:05.139> going<00:06:05.260> to<00:06:05.320> remove 00:06:05.550 --> 00:06:05.560 align:start position:0% interesting process is going to remove 00:06:05.560 --> 00:06:09.720 align:start position:0% interesting process is going to remove so<00:06:05.889> that's<00:06:06.610> no<00:06:06.850> longer<00:06:07.210> valid<00:06:07.889> and<00:06:08.889> this<00:06:09.490> works 00:06:09.720 --> 00:06:09.730 align:start position:0% so that's no longer valid and this works 00:06:09.730 --> 00:06:13.500 align:start position:0% so that's no longer valid and this works pretty<00:06:10.300> great<00:06:10.600> for<00:06:11.730> things<00:06:12.730> that<00:06:13.030> are<00:06:13.180> like 00:06:13.500 --> 00:06:13.510 align:start position:0% pretty great for things that are like 00:06:13.510 --> 00:06:15.420 align:start position:0% pretty great for things that are like events<00:06:13.900> that<00:06:14.020> are<00:06:14.110> defined<00:06:14.470> in<00:06:14.650> a<00:06:14.830> contracts 00:06:15.420 --> 00:06:15.430 align:start position:0% events that are defined in a contracts 00:06:15.430 --> 00:06:18.990 align:start position:0% events that are defined in a contracts API<00:06:15.790> and<00:06:16.750> again<00:06:16.960> so<00:06:17.370> if<00:06:18.370> if<00:06:18.760> you're<00:06:18.910> able 00:06:18.990 --> 00:06:19.000 align:start position:0% API and again so if if you're able 00:06:19.000 --> 00:06:20.640 align:start position:0% API and again so if if you're able access<00:06:19.510> the<00:06:19.630> Internet<00:06:19.930> want<00:06:20.230> to<00:06:20.290> set<00:06:20.440> up<00:06:20.470> here 00:06:20.640 --> 00:06:20.650 align:start position:0% access the Internet want to set up here 00:06:20.650 --> 00:06:22.680 align:start position:0% access the Internet want to set up here on<00:06:20.770> instance<00:06:21.130> this<00:06:21.490> this<00:06:22.030> will<00:06:22.210> do<00:06:22.300> that<00:06:22.450> for 00:06:22.680 --> 00:06:22.690 align:start position:0% on instance this this will do that for 00:06:22.690 --> 00:06:24.060 align:start position:0% on instance this this will do that for you<00:06:22.840> this<00:06:22.990> will<00:06:23.169> kick<00:06:23.350> off<00:06:23.470> the<00:06:23.680> interesting 00:06:24.060 --> 00:06:24.070 align:start position:0% you this will kick off the interesting 00:06:24.070 --> 00:06:26.490 align:start position:0% you this will kick off the interesting process<00:06:24.520> contract<00:06:25.090> watcher<00:06:25.510> focusing<00:06:26.380> on 00:06:26.490 --> 00:06:26.500 align:start position:0% process contract watcher focusing on 00:06:26.500 --> 00:06:28.830 align:start position:0% process contract watcher focusing on three<00:06:26.710> contracts<00:06:27.370> from<00:06:27.460> Moloch<00:06:27.820> down<00:06:28.090> and<00:06:28.450> it 00:06:28.830 --> 00:06:28.840 align:start position:0% three contracts from Moloch down and it 00:06:28.840 --> 00:06:31.230 align:start position:0% three contracts from Moloch down and it will<00:06:28.930> spin<00:06:29.139> up<00:06:29.370> instance<00:06:30.370> of<00:06:30.550> PO<00:06:30.760> scrap<00:06:31.030> pile 00:06:31.230 --> 00:06:31.240 align:start position:0% will spin up instance of PO scrap pile 00:06:31.240 --> 00:06:32.790 align:start position:0% will spin up instance of PO scrap pile which<00:06:31.630> I'll<00:06:31.780> get<00:06:31.930> to<00:06:32.110> that<00:06:32.139> will<00:06:32.380> enable<00:06:32.530> you 00:06:32.790 --> 00:06:32.800 align:start position:0% which I'll get to that will enable you 00:06:32.800 --> 00:06:36.300 align:start position:0% which I'll get to that will enable you to<00:06:32.830> see<00:06:33.280> that<00:06:33.790> data<00:06:34.000> on<00:06:34.510> localhost<00:06:35.290> 5,000<00:06:35.979> in 00:06:36.300 --> 00:06:36.310 align:start position:0% to see that data on localhost 5,000 in 00:06:36.310 --> 00:06:41.159 align:start position:0% to see that data on localhost 5,000 in your<00:06:36.460> graduate<00:06:39.300> compose<00:06:40.300> an<00:06:40.450> excuse<00:06:40.840> is<00:06:41.139> a 00:06:41.159 --> 00:06:41.169 align:start position:0% your graduate compose an excuse is a 00:06:41.169 --> 00:06:42.810 align:start position:0% your graduate compose an excuse is a command<00:06:41.680> that<00:06:41.740> I<00:06:41.860> want<00:06:42.040> to<00:06:42.100> talk<00:06:42.250> about<00:06:42.400> so 00:06:42.810 --> 00:06:42.820 align:start position:0% command that I want to talk about so 00:06:42.820 --> 00:06:45.750 align:start position:0% command that I want to talk about so this<00:06:43.450> is<00:06:43.660> still<00:06:44.260> very<00:06:44.710> much<00:06:44.860> in<00:06:45.250> the<00:06:45.340> work<00:06:45.520> for 00:06:45.750 --> 00:06:45.760 align:start position:0% this is still very much in the work for 00:06:45.760 --> 00:06:48.390 align:start position:0% this is still very much in the work for us<00:06:45.880> but<00:06:46.270> what<00:06:47.229> the<00:06:47.320> contract<00:06:47.740> watcher<00:06:48.070> gives<00:06:48.280> e 00:06:48.390 --> 00:06:48.400 align:start position:0% us but what the contract watcher gives e 00:06:48.400 --> 00:06:50.460 align:start position:0% us but what the contract watcher gives e right<00:06:48.610> is<00:06:48.880> the<00:06:49.030> ability<00:06:49.300> to<00:06:49.510> automatically 00:06:50.460 --> 00:06:50.470 align:start position:0% right is the ability to automatically 00:06:50.470 --> 00:06:52.800 align:start position:0% right is the ability to automatically look<00:06:50.770> at<00:06:50.889> events<00:06:51.250> that<00:06:51.460> are<00:06:51.639> defined<00:06:52.540> in<00:06:52.690> the 00:06:52.800 --> 00:06:52.810 align:start position:0% look at events that are defined in the 00:06:52.810 --> 00:06:57.420 align:start position:0% look at events that are defined in the API<00:06:53.169> but<00:06:53.919> what<00:06:54.220> we<00:06:54.340> found<00:06:54.580> is<00:06:54.970> that<00:06:55.470> in<00:06:56.470> more 00:06:57.420 --> 00:06:57.430 align:start position:0% API but what we found is that in more 00:06:57.430 --> 00:06:59.370 align:start position:0% API but what we found is that in more complex<00:06:57.850> systems<00:06:58.360> of<00:06:58.450> smart<00:06:58.750> contracts<00:06:59.200> we 00:06:59.370 --> 00:06:59.380 align:start position:0% complex systems of smart contracts we 00:06:59.380 --> 00:07:00.510 align:start position:0% complex systems of smart contracts we also<00:06:59.500> got<00:06:59.770> to<00:06:59.800> worry<00:07:00.010> about<00:07:00.190> things<00:07:00.370> like 00:07:00.510 --> 00:07:00.520 align:start position:0% also got to worry about things like 00:07:00.520 --> 00:07:03.360 align:start position:0% also got to worry about things like anonymous<00:07:00.850> events<00:07:01.479> right<00:07:01.750> or<00:07:02.050> custom<00:07:03.010> events 00:07:03.360 --> 00:07:03.370 align:start position:0% anonymous events right or custom events 00:07:03.370 --> 00:07:05.879 align:start position:0% anonymous events right or custom events where<00:07:03.639> the<00:07:04.450> payload<00:07:04.840> doesn't<00:07:05.260> necessarily 00:07:05.879 --> 00:07:05.889 align:start position:0% where the payload doesn't necessarily 00:07:05.889 --> 00:07:07.380 align:start position:0% where the payload doesn't necessarily like<00:07:06.040> the<00:07:06.160> types<00:07:06.400> that<00:07:06.669> you<00:07:06.789> want<00:07:06.820> to<00:07:07.030> decode 00:07:07.380 --> 00:07:07.390 align:start position:0% like the types that you want to decode 00:07:07.390 --> 00:07:09.540 align:start position:0% like the types that you want to decode the<00:07:07.630> payload<00:07:08.020> into<00:07:08.470> and<00:07:08.710> Postgres<00:07:09.220> don't 00:07:09.540 --> 00:07:09.550 align:start position:0% the payload into and Postgres don't 00:07:09.550 --> 00:07:11.580 align:start position:0% the payload into and Postgres don't necessarily<00:07:10.210> match<00:07:10.360> what<00:07:11.020> might<00:07:11.169> be<00:07:11.289> defined 00:07:11.580 --> 00:07:11.590 align:start position:0% necessarily match what might be defined 00:07:11.590 --> 00:07:14.700 align:start position:0% necessarily match what might be defined on<00:07:11.710> the<00:07:11.800> API<00:07:12.160> or<00:07:12.789> the<00:07:12.910> topic<00:07:13.150> 0<00:07:13.330> on<00:07:14.169> a<00:07:14.229> given<00:07:14.530> log 00:07:14.700 --> 00:07:14.710 align:start position:0% on the API or the topic 0 on a given log 00:07:14.710 --> 00:07:16.200 align:start position:0% on the API or the topic 0 on a given log event<00:07:15.039> a<00:07:15.280> little<00:07:15.490> bit<00:07:15.700> different<00:07:16.030> than<00:07:16.150> what 00:07:16.200 --> 00:07:16.210 align:start position:0% event a little bit different than what 00:07:16.210 --> 00:07:19.440 align:start position:0% event a little bit different than what you<00:07:16.360> might<00:07:16.479> expect<00:07:16.810> and<00:07:17.110> so<00:07:17.650> our<00:07:18.310> answer<00:07:18.970> for 00:07:19.440 --> 00:07:19.450 align:start position:0% you might expect and so our answer for 00:07:19.450 --> 00:07:20.730 align:start position:0% you might expect and so our answer for dealing<00:07:19.630> with<00:07:19.870> that<00:07:20.020> sort<00:07:20.260> of<00:07:20.289> thing<00:07:20.500> have 00:07:20.730 --> 00:07:20.740 align:start position:0% dealing with that sort of thing have 00:07:20.740 --> 00:07:22.320 align:start position:0% dealing with that sort of thing have basically<00:07:21.010> been<00:07:21.130> to<00:07:21.340> say<00:07:21.520> hey<00:07:21.820> you<00:07:21.880> can<00:07:22.150> write 00:07:22.320 --> 00:07:22.330 align:start position:0% basically been to say hey you can write 00:07:22.330 --> 00:07:24.659 align:start position:0% basically been to say hey you can write your<00:07:22.479> own<00:07:22.539> plugins<00:07:22.900> and<00:07:23.289> these<00:07:23.979> plugins<00:07:24.250> can 00:07:24.659 --> 00:07:24.669 align:start position:0% your own plugins and these plugins can 00:07:24.669 --> 00:07:27.260 align:start position:0% your own plugins and these plugins can be<00:07:24.820> used<00:07:25.090> to<00:07:25.450> you<00:07:26.320> know<00:07:26.440> take<00:07:26.680> care<00:07:26.950> of<00:07:27.010> that 00:07:27.260 --> 00:07:27.270 align:start position:0% be used to you know take care of that 00:07:27.270 --> 00:07:29.610 align:start position:0% be used to you know take care of that another<00:07:28.270> thing<00:07:28.539> that<00:07:28.570> compose<00:07:29.050> and<00:07:29.229> execute 00:07:29.610 --> 00:07:29.620 align:start position:0% another thing that compose and execute 00:07:29.620 --> 00:07:31.230 align:start position:0% another thing that compose and execute plug-ins<00:07:29.830> enable<00:07:30.340> you<00:07:30.430> to<00:07:30.490> do<00:07:30.669> is<00:07:30.880> to<00:07:31.090> look 00:07:31.230 --> 00:07:31.240 align:start position:0% plug-ins enable you to do is to look 00:07:31.240 --> 00:07:34.440 align:start position:0% plug-ins enable you to do is to look directly<00:07:31.510> in<00:07:31.810> storage<00:07:32.289> tree<00:07:32.590> notes<00:07:33.150> so<00:07:34.150> when 00:07:34.440 --> 00:07:34.450 align:start position:0% directly in storage tree notes so when 00:07:34.450 --> 00:07:36.000 align:start position:0% directly in storage tree notes so when I'll<00:07:34.630> be<00:07:34.660> continuing<00:07:35.200> to<00:07:35.380> talk<00:07:35.590> about<00:07:35.740> this 00:07:36.000 --> 00:07:36.010 align:start position:0% I'll be continuing to talk about this 00:07:36.010 --> 00:07:37.980 align:start position:0% I'll be continuing to talk about this during<00:07:36.310> this<00:07:36.430> talk<00:07:36.700> but<00:07:37.000> I<00:07:37.210> think<00:07:37.720> one<00:07:37.960> thing 00:07:37.980 --> 00:07:37.990 align:start position:0% during this talk but I think one thing 00:07:37.990 --> 00:07:40.140 align:start position:0% during this talk but I think one thing that<00:07:38.289> is<00:07:38.919> really<00:07:39.220> interesting<00:07:39.550> that<00:07:39.880> the 00:07:40.140 --> 00:07:40.150 align:start position:0% that is really interesting that the 00:07:40.150 --> 00:07:42.000 align:start position:0% that is really interesting that the community's<00:07:40.570> sort<00:07:41.229> of<00:07:41.289> needs<00:07:41.440> to<00:07:41.560> like<00:07:41.710> reckon 00:07:42.000 --> 00:07:42.010 align:start position:0% community's sort of needs to like reckon 00:07:42.010 --> 00:07:42.709 align:start position:0% community's sort of needs to like reckon with<00:07:42.190> is<00:07:42.430> that 00:07:42.709 --> 00:07:42.719 align:start position:0% with is that 00:07:42.719 --> 00:07:46.609 align:start position:0% with is that right<00:07:44.059> in<00:07:45.059> order<00:07:45.269> to<00:07:45.360> access<00:07:45.509> a<00:07:45.959> traditional 00:07:46.609 --> 00:07:46.619 align:start position:0% right in order to access a traditional 00:07:46.619 --> 00:07:48.079 align:start position:0% right in order to access a traditional need<00:07:46.739> to<00:07:46.889> run<00:07:47.039> like<00:07:47.219> the<00:07:47.309> archive<00:07:47.669> note<00:07:47.909> right 00:07:48.079 --> 00:07:48.089 align:start position:0% need to run like the archive note right 00:07:48.089 --> 00:07:49.549 align:start position:0% need to run like the archive note right if<00:07:48.179> you<00:07:48.239> want<00:07:48.389> to<00:07:48.449> have<00:07:48.539> historical<00:07:49.080> state<00:07:49.319> and 00:07:49.549 --> 00:07:49.559 align:start position:0% if you want to have historical state and 00:07:49.559 --> 00:07:52.219 align:start position:0% if you want to have historical state and so<00:07:50.059> my<00:07:51.059> folks<00:07:51.329> don't<00:07:51.509> want<00:07:51.689> to<00:07:51.749> do<00:07:51.839> that<00:07:52.019> don't 00:07:52.219 --> 00:07:52.229 align:start position:0% so my folks don't want to do that don't 00:07:52.229 --> 00:07:53.569 align:start position:0% so my folks don't want to do that don't be<00:07:52.349> able<00:07:52.499> to<00:07:52.619> access<00:07:52.769> their<00:07:53.189> data<00:07:53.279> running 00:07:53.569 --> 00:07:53.579 align:start position:0% be able to access their data running 00:07:53.579 --> 00:07:56.239 align:start position:0% be able to access their data running this<00:07:53.759> the<00:07:53.879> full<00:07:54.119> note<00:07:54.360> and<00:07:54.829> the<00:07:55.829> way<00:07:55.949> you<00:07:56.009> can 00:07:56.239 --> 00:07:56.249 align:start position:0% this the full note and the way you can 00:07:56.249 --> 00:07:58.009 align:start position:0% this the full note and the way you can do<00:07:56.429> that<00:07:56.610> is<00:07:56.939> you<00:07:56.969> can<00:07:57.299> sort<00:07:57.509> of<00:07:57.569> stuff<00:07:57.809> your 00:07:58.009 --> 00:07:58.019 align:start position:0% do that is you can sort of stuff your 00:07:58.019 --> 00:08:00.559 align:start position:0% do that is you can sort of stuff your state<00:07:58.319> into<00:07:58.769> events<00:07:59.189> which<00:07:59.549> is<00:07:59.729> cool<00:07:59.939> except 00:08:00.559 --> 00:08:00.569 align:start position:0% state into events which is cool except 00:08:00.569 --> 00:08:02.029 align:start position:0% state into events which is cool except it<00:08:00.689> means<00:08:00.809> that<00:08:01.139> we've<00:08:01.289> just<00:08:01.529> sort<00:08:01.679> of<00:08:01.769> moved 00:08:02.029 --> 00:08:02.039 align:start position:0% it means that we've just sort of moved 00:08:02.039 --> 00:08:03.739 align:start position:0% it means that we've just sort of moved the<00:08:02.219> problem<00:08:02.669> over<00:08:02.789> where<00:08:03.179> instead<00:08:03.449> of<00:08:03.509> like 00:08:03.739 --> 00:08:03.749 align:start position:0% the problem over where instead of like 00:08:03.749 --> 00:08:05.929 align:start position:0% the problem over where instead of like state<00:08:04.139> float<00:08:04.409> or<00:08:04.769> you<00:08:05.279> have<00:08:05.489> the<00:08:05.579> state<00:08:05.759> look 00:08:05.929 --> 00:08:05.939 align:start position:0% state float or you have the state look 00:08:05.939 --> 00:08:07.339 align:start position:0% state float or you have the state look but<00:08:06.089> you<00:08:06.149> also<00:08:06.299> can<00:08:06.509> have<00:08:06.539> like<00:08:06.809> event<00:08:07.139> load 00:08:07.339 --> 00:08:07.349 align:start position:0% but you also can have like event load 00:08:07.349 --> 00:08:08.989 align:start position:0% but you also can have like event load right<00:08:07.919> so<00:08:08.099> there<00:08:08.219> have<00:08:08.309> been<00:08:08.459> proposals 00:08:08.989 --> 00:08:08.999 align:start position:0% right so there have been proposals 00:08:08.999 --> 00:08:11.569 align:start position:0% right so there have been proposals already<00:08:09.929> floated<00:08:10.349> in<00:08:10.529> the<00:08:10.709> ecosystem<00:08:11.369> to 00:08:11.569 --> 00:08:11.579 align:start position:0% already floated in the ecosystem to 00:08:11.579 --> 00:08:14.539 align:start position:0% already floated in the ecosystem to start<00:08:12.149> pruning<00:08:12.799> historical<00:08:13.799> events<00:08:14.189> out<00:08:14.519> of 00:08:14.539 --> 00:08:14.549 align:start position:0% start pruning historical events out of 00:08:14.549 --> 00:08:17.689 align:start position:0% start pruning historical events out of full<00:08:14.879> notes<00:08:15.179> as<00:08:15.329> well<00:08:15.949> and<00:08:16.949> the<00:08:17.279> state<00:08:17.519> that 00:08:17.689 --> 00:08:17.699 align:start position:0% full notes as well and the state that 00:08:17.699 --> 00:08:20.119 align:start position:0% full notes as well and the state that you<00:08:17.879> get<00:08:18.089> from<00:08:18.360> an<00:08:18.449> event<00:08:18.629> isn't<00:08:19.499> necessarily 00:08:20.119 --> 00:08:20.129 align:start position:0% you get from an event isn't necessarily 00:08:20.129 --> 00:08:22.519 align:start position:0% you get from an event isn't necessarily the<00:08:20.759> state<00:08:20.999> that's<00:08:21.239> actually<00:08:21.839> you<00:08:22.439> know 00:08:22.519 --> 00:08:22.529 align:start position:0% the state that's actually you know 00:08:22.529 --> 00:08:24.649 align:start position:0% the state that's actually you know what's<00:08:22.800> happening<00:08:23.219> on<00:08:23.399> a<00:08:23.429> given<00:08:23.909> contract<00:08:24.419> and 00:08:24.649 --> 00:08:24.659 align:start position:0% what's happening on a given contract and 00:08:24.659 --> 00:08:26.839 align:start position:0% what's happening on a given contract and so<00:08:24.899> one<00:08:25.739> thing<00:08:25.769> that<00:08:26.129> we've<00:08:26.249> been<00:08:26.399> working<00:08:26.729> on 00:08:26.839 --> 00:08:26.849 align:start position:0% so one thing that we've been working on 00:08:26.849 --> 00:08:28.309 align:start position:0% so one thing that we've been working on a<00:08:26.879> lot<00:08:27.089> with<00:08:27.419> the<00:08:27.539> plugins<00:08:27.989> that<00:08:28.110> we're 00:08:28.309 --> 00:08:28.319 align:start position:0% a lot with the plugins that we're 00:08:28.319 --> 00:08:31.759 align:start position:0% a lot with the plugins that we're developing<00:08:29.039> is<00:08:29.639> to<00:08:30.029> look<00:08:30.989> directly<00:08:31.259> at 00:08:31.759 --> 00:08:31.769 align:start position:0% developing is to look directly at 00:08:31.769 --> 00:08:36.319 align:start position:0% developing is to look directly at storage<00:08:32.519> on<00:08:32.819> a<00:08:32.849> contract<00:08:33.709> now<00:08:35.329> traditionally 00:08:36.319 --> 00:08:36.329 align:start position:0% storage on a contract now traditionally 00:08:36.329 --> 00:08:37.369 align:start position:0% storage on a contract now traditionally you're<00:08:36.419> gonna<00:08:36.539> have<00:08:36.719> to<00:08:36.839> do<00:08:36.930> this<00:08:37.050> with<00:08:37.259> an 00:08:37.369 --> 00:08:37.379 align:start position:0% you're gonna have to do this with an 00:08:37.379 --> 00:08:38.839 align:start position:0% you're gonna have to do this with an archive<00:08:37.649> node<00:08:37.919> but<00:08:38.159> we've<00:08:38.279> got<00:08:38.459> some<00:08:38.699> ideas 00:08:38.839 --> 00:08:38.849 align:start position:0% archive node but we've got some ideas 00:08:38.849 --> 00:08:39.829 align:start position:0% archive node but we've got some ideas there<00:08:39.120> as<00:08:39.360> well 00:08:39.829 --> 00:08:39.839 align:start position:0% there as well 00:08:39.839 --> 00:08:41.360 align:start position:0% there as well anyway<00:08:40.289> the<00:08:40.439> plugins<00:08:40.800> let<00:08:40.979> you<00:08:41.099> look<00:08:41.189> at 00:08:41.360 --> 00:08:41.370 align:start position:0% anyway the plugins let you look at 00:08:41.370 --> 00:08:42.920 align:start position:0% anyway the plugins let you look at storage<00:08:41.610> tree<00:08:41.879> nodes<00:08:42.089> you<00:08:42.300> can<00:08:42.449> automatically 00:08:42.920 --> 00:08:42.930 align:start position:0% storage tree nodes you can automatically 00:08:42.930 --> 00:08:44.869 align:start position:0% storage tree nodes you can automatically decode<00:08:43.409> like<00:08:43.620> one<00:08:43.829> of<00:08:43.919> the<00:08:44.039> true<00:08:44.219> that<00:08:44.519> value 00:08:44.869 --> 00:08:44.879 align:start position:0% decode like one of the true that value 00:08:44.879 --> 00:08:48.679 align:start position:0% decode like one of the true that value of<00:08:45.060> a<00:08:45.089> variable<00:08:45.269> on<00:08:46.170> a<00:08:46.230> contract<00:08:47.180> and<00:08:48.180> plugins 00:08:48.679 --> 00:08:48.689 align:start position:0% of a variable on a contract and plugins 00:08:48.689 --> 00:08:51.170 align:start position:0% of a variable on a contract and plugins also<00:08:48.870> need<00:08:49.139> to<00:08:49.439> make<00:08:49.620> more<00:08:50.250> complex<00:08:50.670> queries 00:08:51.170 --> 00:08:51.180 align:start position:0% also need to make more complex queries 00:08:51.180 --> 00:08:54.259 align:start position:0% also need to make more complex queries right<00:08:51.569> so<00:08:51.959> in<00:08:52.829> order<00:08:52.920> to<00:08:53.160> sort<00:08:53.490> of<00:08:53.639> crystallize 00:08:54.259 --> 00:08:54.269 align:start position:0% right so in order to sort of crystallize 00:08:54.269 --> 00:08:56.240 align:start position:0% right so in order to sort of crystallize what<00:08:54.300> those<00:08:54.660> complex<00:08:55.139> queries<00:08:55.529> look<00:08:55.740> like<00:08:55.949> I'm 00:08:56.240 --> 00:08:56.250 align:start position:0% what those complex queries look like I'm 00:08:56.250 --> 00:08:59.389 align:start position:0% what those complex queries look like I'm going<00:08:56.459> to<00:08:56.519> bump<00:08:56.639> ahead<00:08:56.939> to<00:08:57.209> post<00:08:57.629> grandpa<00:08:58.399> so 00:08:59.389 --> 00:08:59.399 align:start position:0% going to bump ahead to post grandpa so 00:08:59.399 --> 00:09:01.220 align:start position:0% going to bump ahead to post grandpa so post-grad<00:09:00.000> file<00:09:00.209> is<00:09:00.360> not<00:09:00.540> something<00:09:00.959> we<00:09:01.079> built 00:09:01.220 --> 00:09:01.230 align:start position:0% post-grad file is not something we built 00:09:01.230 --> 00:09:04.009 align:start position:0% post-grad file is not something we built the<00:09:01.920> post<00:09:02.220> gram<00:09:02.459> file<00:09:02.699> is<00:09:02.970> a<00:09:03.240> super<00:09:03.839> awesome 00:09:04.009 --> 00:09:04.019 align:start position:0% the post gram file is a super awesome 00:09:04.019 --> 00:09:06.889 align:start position:0% the post gram file is a super awesome tool<00:09:04.500> and<00:09:04.769> we<00:09:05.490> support<00:09:05.879> that<00:09:05.910> job<00:09:06.240> patreon<00:09:06.689> I 00:09:06.889 --> 00:09:06.899 align:start position:0% tool and we support that job patreon I 00:09:06.899 --> 00:09:07.980 align:start position:0% tool and we support that job patreon I recommend<00:09:07.439> everyone 00:09:07.980 --> 00:09:07.990 align:start position:0% recommend everyone 00:09:07.990 --> 00:09:10.590 align:start position:0% recommend everyone as<00:09:08.110> well<00:09:08.470> but<00:09:09.310> most<00:09:09.580> gravel<00:09:10.000> enables<00:09:10.510> you<00:09:10.570> to 00:09:10.590 --> 00:09:10.600 align:start position:0% as well but most gravel enables you to 00:09:10.600 --> 00:09:12.990 align:start position:0% as well but most gravel enables you to do<00:09:10.870> is<00:09:10.900> you<00:09:11.410> just<00:09:11.680> literally<00:09:12.160> like<00:09:12.490> post 00:09:12.990 --> 00:09:13.000 align:start position:0% do is you just literally like post 00:09:13.000 --> 00:09:14.700 align:start position:0% do is you just literally like post gravel<00:09:13.450> from<00:09:13.600> the<00:09:13.720> command<00:09:14.080> line<00:09:14.140> and<00:09:14.530> it<00:09:14.590> will 00:09:14.700 --> 00:09:14.710 align:start position:0% gravel from the command line and it will 00:09:14.710 --> 00:09:17.100 align:start position:0% gravel from the command line and it will inspect<00:09:15.070> your<00:09:15.250> Postgres<00:09:15.730> database<00:09:16.110> identify 00:09:17.100 --> 00:09:17.110 align:start position:0% inspect your Postgres database identify 00:09:17.110 --> 00:09:19.170 align:start position:0% inspect your Postgres database identify the<00:09:17.170> schema<00:09:17.680> and<00:09:18.160> like<00:09:18.310> automatically<00:09:18.970> make 00:09:19.170 --> 00:09:19.180 align:start position:0% the schema and like automatically make 00:09:19.180 --> 00:09:20.610 align:start position:0% the schema and like automatically make that<00:09:19.330> about<00:09:19.570> available<00:09:20.140> to<00:09:20.290> you<00:09:20.410> in<00:09:20.530> the 00:09:20.610 --> 00:09:20.620 align:start position:0% that about available to you in the 00:09:20.620 --> 00:09:23.430 align:start position:0% that about available to you in the browser<00:09:20.860> which<00:09:21.610> is<00:09:21.820> just<00:09:22.360> like<00:09:22.570> super-sick 00:09:23.430 --> 00:09:23.440 align:start position:0% browser which is just like super-sick 00:09:23.440 --> 00:09:25.410 align:start position:0% browser which is just like super-sick comments<00:09:23.860> so<00:09:24.070> thank<00:09:24.730> you<00:09:24.790> so<00:09:24.940> much<00:09:25.120> too<00:09:25.270> many 00:09:25.410 --> 00:09:25.420 align:start position:0% comments so thank you so much too many 00:09:25.420 --> 00:09:28.980 align:start position:0% comments so thank you so much too many he's<00:09:25.690> also<00:09:25.870> super<00:09:26.290> responsive<00:09:26.770> on<00:09:26.860> discord<00:09:27.990> we 00:09:28.980 --> 00:09:28.990 align:start position:0% he's also super responsive on discord we 00:09:28.990 --> 00:09:30.960 align:start position:0% he's also super responsive on discord we found<00:09:29.290> it<00:09:29.440> to<00:09:29.560> be<00:09:29.590> a<00:09:29.710> really<00:09:29.950> easy<00:09:29.980> solution<00:09:30.490> to 00:09:30.960 --> 00:09:30.970 align:start position:0% found it to be a really easy solution to 00:09:30.970 --> 00:09:33.960 align:start position:0% found it to be a really easy solution to sort<00:09:31.300> of<00:09:31.390> a<00:09:31.480> proposed<00:09:32.310> fixing<00:09:33.310> with<00:09:33.430> an<00:09:33.520> API<00:09:33.730> in 00:09:33.960 --> 00:09:33.970 align:start position:0% sort of a proposed fixing with an API in 00:09:33.970 --> 00:09:35.490 align:start position:0% sort of a proposed fixing with an API in the<00:09:34.000> browser<00:09:34.090> but<00:09:34.630> the<00:09:34.750> data<00:09:34.930> that<00:09:35.170> we<00:09:35.320> have 00:09:35.490 --> 00:09:35.500 align:start position:0% the browser but the data that we have 00:09:35.500 --> 00:09:37.410 align:start position:0% the browser but the data that we have and<00:09:35.530> both<00:09:35.860> graphs<00:09:36.190> of<00:09:36.820> course<00:09:37.090> if<00:09:37.300> you're 00:09:37.410 --> 00:09:37.420 align:start position:0% and both graphs of course if you're 00:09:37.420 --> 00:09:38.940 align:start position:0% and both graphs of course if you're interested<00:09:37.540> you<00:09:37.960> can<00:09:38.050> always<00:09:38.230> you<00:09:38.560> know<00:09:38.590> just 00:09:38.940 --> 00:09:38.950 align:start position:0% interested you can always you know just 00:09:38.950 --> 00:09:40.290 align:start position:0% interested you can always you know just make<00:09:39.130> queries<00:09:39.340> directly<00:09:39.610> against<00:09:40.120> that 00:09:40.290 --> 00:09:40.300 align:start position:0% make queries directly against that 00:09:40.300 --> 00:09:43.830 align:start position:0% make queries directly against that Postgres<00:09:40.720> data<00:09:41.040> but<00:09:42.040> for<00:09:42.540> browser<00:09:43.540> access 00:09:43.830 --> 00:09:43.840 align:start position:0% Postgres data but for browser access 00:09:43.840 --> 00:09:44.790 align:start position:0% Postgres data but for browser access close<00:09:44.290> grab<00:09:44.500> files 00:09:44.790 --> 00:09:44.800 align:start position:0% close grab files 00:09:44.800 --> 00:09:47.490 align:start position:0% close grab files angry<00:09:45.270> so<00:09:46.270> some<00:09:46.570> things<00:09:46.600> to<00:09:46.960> know<00:09:47.080> about<00:09:47.110> those 00:09:47.490 --> 00:09:47.500 align:start position:0% angry so some things to know about those 00:09:47.500 --> 00:09:49.260 align:start position:0% angry so some things to know about those grab<00:09:47.740> files<00:09:47.980> that<00:09:48.310> like<00:09:48.490> it'll<00:09:48.730> automatically 00:09:49.260 --> 00:09:49.270 align:start position:0% grab files that like it'll automatically 00:09:49.270 --> 00:09:50.970 align:start position:0% grab files that like it'll automatically discover<00:09:49.720> relations<00:09:50.260> between<00:09:50.500> your<00:09:50.770> data 00:09:50.970 --> 00:09:50.980 align:start position:0% discover relations between your data 00:09:50.980 --> 00:09:54.150 align:start position:0% discover relations between your data right<00:09:51.430> so<00:09:51.760> for<00:09:52.510> example<00:09:52.900> I<00:09:53.170> mentioned<00:09:53.980> that 00:09:54.150 --> 00:09:54.160 align:start position:0% right so for example I mentioned that 00:09:54.160 --> 00:09:56.070 align:start position:0% right so for example I mentioned that events<00:09:54.760> we<00:09:54.910> decode<00:09:55.300> or<00:09:55.540> as<00:09:55.630> soon<00:09:55.750> as<00:09:55.840> stated 00:09:56.070 --> 00:09:56.080 align:start position:0% events we decode or as soon as stated 00:09:56.080 --> 00:09:57.480 align:start position:0% events we decode or as soon as stated with<00:09:56.200> a<00:09:56.410> block<00:09:56.620> better<00:09:56.890> than<00:09:57.100> existing 00:09:57.480 --> 00:09:57.490 align:start position:0% with a block better than existing 00:09:57.490 --> 00:09:58.650 align:start position:0% with a block better than existing database<00:09:57.880> that<00:09:57.910> you<00:09:58.120> can<00:09:58.360> just<00:09:58.510> like 00:09:58.650 --> 00:09:58.660 align:start position:0% database that you can just like 00:09:58.660 --> 00:10:00.960 align:start position:0% database that you can just like automatically<00:09:59.290> get<00:09:59.530> better<00:09:59.770> by<00:10:00.010> an<00:10:00.130> e<00:10:00.310> with 00:10:00.960 --> 00:10:00.970 align:start position:0% automatically get better by an e with 00:10:00.970 --> 00:10:04.080 align:start position:0% automatically get better by an e with the<00:10:01.000> event<00:10:01.690> that<00:10:01.900> you're<00:10:02.020> looking<00:10:02.350> up<00:10:02.500> and<00:10:03.090> see 00:10:04.080 --> 00:10:04.090 align:start position:0% the event that you're looking up and see 00:10:04.090 --> 00:10:05.850 align:start position:0% the event that you're looking up and see you<00:10:04.540> know<00:10:04.630> metadata<00:10:05.080> about<00:10:05.440> that<00:10:05.650> block 00:10:05.850 --> 00:10:05.860 align:start position:0% you know metadata about that block 00:10:05.860 --> 00:10:07.320 align:start position:0% you know metadata about that block header<00:10:06.160> if<00:10:06.310> you<00:10:06.430> want<00:10:06.580> to<00:10:06.670> see<00:10:06.820> you<00:10:07.090> know<00:10:07.180> what 00:10:07.320 --> 00:10:07.330 align:start position:0% header if you want to see you know what 00:10:07.330 --> 00:10:10.230 align:start position:0% header if you want to see you know what block<00:10:07.510> number<00:10:07.870> was<00:10:08.020> it<00:10:08.170> or<00:10:08.350> whatever<00:10:09.240> post 00:10:10.230 --> 00:10:10.240 align:start position:0% block number was it or whatever post 00:10:10.240 --> 00:10:12.630 align:start position:0% block number was it or whatever post grant<00:10:10.480> file<00:10:10.720> also<00:10:10.930> exposes<00:10:11.650> built-in<00:10:12.160> filters 00:10:12.630 --> 00:10:12.640 align:start position:0% grant file also exposes built-in filters 00:10:12.640 --> 00:10:14.640 align:start position:0% grant file also exposes built-in filters and<00:10:12.880> conditions<00:10:13.300> and<00:10:13.510> so<00:10:13.660> forth<00:10:13.960> which<00:10:14.380> means 00:10:14.640 --> 00:10:14.650 align:start position:0% and conditions and so forth which means 00:10:14.650 --> 00:10:19.140 align:start position:0% and conditions and so forth which means that<00:10:15.010> you<00:10:16.200> can<00:10:17.200> Mike<00:10:17.550> is<00:10:18.550> gonna<00:10:18.700> find<00:10:19.000> this 00:10:19.140 --> 00:10:19.150 align:start position:0% that you can Mike is gonna find this 00:10:19.150 --> 00:10:20.460 align:start position:0% that you can Mike is gonna find this exact<00:10:19.510> tool<00:10:19.720> to<00:10:19.870> your<00:10:19.930> Postgres<00:10:20.320> database 00:10:20.460 --> 00:10:20.470 align:start position:0% exact tool to your Postgres database 00:10:20.470 --> 00:10:21.360 align:start position:0% exact tool to your Postgres database feed<00:10:20.950> here 00:10:21.360 --> 00:10:21.370 align:start position:0% feed here 00:10:21.370 --> 00:10:24.450 align:start position:0% feed here Camela<00:10:21.940> query<00:10:22.560> support<00:10:23.560> subscriptions<00:10:24.190> and 00:10:24.450 --> 00:10:24.460 align:start position:0% Camela query support subscriptions and 00:10:24.460 --> 00:10:26.310 align:start position:0% Camela query support subscriptions and notifications<00:10:25.390> and<00:10:25.540> our<00:10:25.660> view<00:10:25.840> data<00:10:25.990> hitting 00:10:26.310 --> 00:10:26.320 align:start position:0% notifications and our view data hitting 00:10:26.320 --> 00:10:28.770 align:start position:0% notifications and our view data hitting the<00:10:26.410> database<00:10:26.800> there<00:10:27.490> are<00:10:27.700> computed<00:10:28.300> columns 00:10:28.770 --> 00:10:28.780 align:start position:0% the database there are computed columns 00:10:28.780 --> 00:10:31.590 align:start position:0% the database there are computed columns which<00:10:28.960> enable<00:10:29.380> you<00:10:29.500> to<00:10:29.530> like<00:10:29.860> amend<00:10:30.520> data<00:10:31.300> and 00:10:31.590 --> 00:10:31.600 align:start position:0% which enable you to like amend data and 00:10:31.600 --> 00:10:34.110 align:start position:0% which enable you to like amend data and custom<00:10:32.500> queries<00:10:32.980> which<00:10:33.550> is<00:10:33.730> what<00:10:33.910> I<00:10:33.940> was 00:10:34.110 --> 00:10:34.120 align:start position:0% custom queries which is what I was 00:10:34.120 --> 00:10:36.120 align:start position:0% custom queries which is what I was mentioning<00:10:34.630> with<00:10:35.050> the<00:10:35.170> more<00:10:35.350> complex<00:10:35.770> queries 00:10:36.120 --> 00:10:36.130 align:start position:0% mentioning with the more complex queries 00:10:36.130 --> 00:10:38.520 align:start position:0% mentioning with the more complex queries on<00:10:36.250> the<00:10:36.280> last<00:10:36.520> slide<00:10:36.670> right<00:10:37.150> so<00:10:37.390> you<00:10:37.930> can<00:10:38.140> in<00:10:38.470> a 00:10:38.520 --> 00:10:38.530 align:start position:0% on the last slide right so you can in a 00:10:38.530 --> 00:10:40.110 align:start position:0% on the last slide right so you can in a migration<00:10:38.980> like<00:10:39.340> create<00:10:39.670> a<00:10:39.700> query<00:10:39.970> that 00:10:40.110 --> 00:10:40.120 align:start position:0% migration like create a query that 00:10:40.120 --> 00:10:42.060 align:start position:0% migration like create a query that aggregates<00:10:40.840> either<00:10:41.260> from<00:10:41.470> say<00:10:41.620> multiple 00:10:42.060 --> 00:10:42.070 align:start position:0% aggregates either from say multiple 00:10:42.070 --> 00:10:45.240 align:start position:0% aggregates either from say multiple events<00:10:42.490> or<00:10:42.640> tables<00:10:43.090> and<00:10:43.770> those<00:10:44.770> will<00:10:44.950> show<00:10:45.070> up 00:10:45.240 --> 00:10:45.250 align:start position:0% events or tables and those will show up 00:10:45.250 --> 00:10:50.480 align:start position:0% events or tables and those will show up automatically<00:10:46.000> in<00:10:46.300> post<00:10:46.990> growl<00:10:47.200> help<00:10:48.540> cool<00:10:49.540> so 00:10:50.480 --> 00:10:50.490 align:start position:0% automatically in post growl help cool so 00:10:50.490 --> 00:10:53.280 align:start position:0% automatically in post growl help cool so that's<00:10:51.490> the<00:10:51.730> toolbox<00:10:52.150> sort<00:10:52.630> of<00:10:52.720> like<00:10:52.870> as<00:10:53.110> it 00:10:53.280 --> 00:10:53.290 align:start position:0% that's the toolbox sort of like as it 00:10:53.290 --> 00:10:55.260 align:start position:0% that's the toolbox sort of like as it stands<00:10:53.590> right<00:10:53.830> now<00:10:54.040> again<00:10:54.610> you<00:10:54.880> can<00:10:55.000> try<00:10:55.150> it 00:10:55.260 --> 00:10:55.270 align:start position:0% stands right now again you can try it 00:10:55.270 --> 00:10:59.430 align:start position:0% stands right now again you can try it out<00:10:55.390> repos<00:10:56.110> took<00:10:56.320> the<00:10:56.410> open<00:10:56.680> source<00:10:56.860> and<00:10:58.440> the 00:10:59.430 --> 00:10:59.440 align:start position:0% out repos took the open source and the 00:10:59.440 --> 00:11:00.810 align:start position:0% out repos took the open source and the thing<00:10:59.620> I<00:10:59.710> wanted<00:10:59.920> to<00:10:59.980> talk<00:11:00.160> about<00:11:00.190> next<00:11:00.730> is 00:11:00.810 --> 00:11:00.820 align:start position:0% thing I wanted to talk about next is 00:11:00.820 --> 00:11:03.270 align:start position:0% thing I wanted to talk about next is sort<00:11:01.090> of<00:11:01.150> like<00:11:01.300> what<00:11:01.570> are<00:11:01.600> we<00:11:01.750> driving<00:11:02.680> toward 00:11:03.270 --> 00:11:03.280 align:start position:0% sort of like what are we driving toward 00:11:03.280 --> 00:11:04.220 align:start position:0% sort of like what are we driving toward with<00:11:03.700> our 00:11:04.220 --> 00:11:04.230 align:start position:0% with our 00:11:04.230 --> 00:11:06.710 align:start position:0% with our coming<00:11:04.470> work<00:11:04.680> and<00:11:04.920> so<00:11:05.250> the<00:11:05.970> first<00:11:06.120> thing<00:11:06.420> is 00:11:06.710 --> 00:11:06.720 align:start position:0% coming work and so the first thing is 00:11:06.720 --> 00:11:09.050 align:start position:0% coming work and so the first thing is simplifying<00:11:07.500> our<00:11:07.680> interfaces<00:11:08.310> for<00:11:08.550> plugins 00:11:09.050 --> 00:11:09.060 align:start position:0% simplifying our interfaces for plugins 00:11:09.060 --> 00:11:10.490 align:start position:0% simplifying our interfaces for plugins right<00:11:09.390> so<00:11:09.540> I<00:11:09.570> mentioned<00:11:09.810> you<00:11:10.080> can<00:11:10.290> write 00:11:10.490 --> 00:11:10.500 align:start position:0% right so I mentioned you can write 00:11:10.500 --> 00:11:12.530 align:start position:0% right so I mentioned you can write plugins<00:11:10.740> and<00:11:10.980> they<00:11:11.070> do<00:11:11.220> super<00:11:11.520> cool<00:11:11.700> stuff<00:11:11.970> but 00:11:12.530 --> 00:11:12.540 align:start position:0% plugins and they do super cool stuff but 00:11:12.540 --> 00:11:14.720 align:start position:0% plugins and they do super cool stuff but our<00:11:13.080> mission<00:11:13.350> there<00:11:13.680> is<00:11:13.710> to<00:11:14.070> make<00:11:14.220> sure<00:11:14.250> that 00:11:14.720 --> 00:11:14.730 align:start position:0% our mission there is to make sure that 00:11:14.730 --> 00:11:16.760 align:start position:0% our mission there is to make sure that in<00:11:15.120> order<00:11:15.450> to<00:11:15.480> write<00:11:15.720> a<00:11:15.780> plug-in<00:11:16.290> that<00:11:16.320> people 00:11:16.760 --> 00:11:16.770 align:start position:0% in order to write a plug-in that people 00:11:16.770 --> 00:11:18.260 align:start position:0% in order to write a plug-in that people need<00:11:16.890> to<00:11:16.980> get<00:11:17.100> things<00:11:17.400> like<00:11:17.670> storage<00:11:18.030> tree 00:11:18.260 --> 00:11:18.270 align:start position:0% need to get things like storage tree 00:11:18.270 --> 00:11:21.770 align:start position:0% need to get things like storage tree nodes<00:11:18.480> or<00:11:19.340> anonymous<00:11:20.340> events<00:11:20.790> that<00:11:21.150> you<00:11:21.750> have 00:11:21.770 --> 00:11:21.780 align:start position:0% nodes or anonymous events that you have 00:11:21.780 --> 00:11:23.780 align:start position:0% nodes or anonymous events that you have to<00:11:22.110> write<00:11:22.260> like<00:11:22.290> the<00:11:22.590> minimal<00:11:22.980> amount<00:11:23.340> of<00:11:23.520> this 00:11:23.780 --> 00:11:23.790 align:start position:0% to write like the minimal amount of this 00:11:23.790 --> 00:11:26.600 align:start position:0% to write like the minimal amount of this book<00:11:24.000> could<00:11:24.210> possible<00:11:24.810> for<00:11:25.340> given<00:11:26.340> smart 00:11:26.600 --> 00:11:26.610 align:start position:0% book could possible for given smart 00:11:26.610 --> 00:11:29.840 align:start position:0% book could possible for given smart contracts<00:11:28.190> another<00:11:29.190> thing<00:11:29.340> we're<00:11:29.460> working<00:11:29.640> on 00:11:29.840 --> 00:11:29.850 align:start position:0% contracts another thing we're working on 00:11:29.850 --> 00:11:33.050 align:start position:0% contracts another thing we're working on is<00:11:29.910> client<00:11:30.330> patches<00:11:30.870> to<00:11:31.170> omit<00:11:31.740> these<00:11:32.730> storage 00:11:33.050 --> 00:11:33.060 align:start position:0% is client patches to omit these storage 00:11:33.060 --> 00:11:36.740 align:start position:0% is client patches to omit these storage Tiff's<00:11:33.420> during<00:11:33.960> a<00:11:34.110> sync<00:11:34.380> so<00:11:35.060> I<00:11:36.060> mentioned<00:11:36.510> that 00:11:36.740 --> 00:11:36.750 align:start position:0% Tiff's during a sync so I mentioned that 00:11:36.750 --> 00:11:38.810 align:start position:0% Tiff's during a sync so I mentioned that like<00:11:36.930> traditionally<00:11:37.440> archived<00:11:38.100> new<00:11:38.370> to 00:11:38.810 --> 00:11:38.820 align:start position:0% like traditionally archived new to 00:11:38.820 --> 00:11:40.880 align:start position:0% like traditionally archived new to access<00:11:39.450> historical<00:11:40.080> state<00:11:40.320> and<00:11:40.500> that's<00:11:40.650> kind 00:11:40.880 --> 00:11:40.890 align:start position:0% access historical state and that's kind 00:11:40.890 --> 00:11:42.830 align:start position:0% access historical state and that's kind of<00:11:40.920> a<00:11:41.010> bummer<00:11:41.160> but<00:11:41.850> like<00:11:42.030> one<00:11:42.300> option<00:11:42.690> that's 00:11:42.830 --> 00:11:42.840 align:start position:0% of a bummer but like one option that's 00:11:42.840 --> 00:11:44.450 align:start position:0% of a bummer but like one option that's definitely<00:11:43.230> on<00:11:43.320> the<00:11:43.410> table<00:11:43.770> would<00:11:43.950> be<00:11:44.070> been 00:11:44.450 --> 00:11:44.460 align:start position:0% definitely on the table would be been 00:11:44.460 --> 00:11:46.460 align:start position:0% definitely on the table would be been able<00:11:44.640> to<00:11:44.760> subscription<00:11:45.390> over<00:11:45.690> the<00:11:45.900> JSON<00:11:46.320> RPC 00:11:46.460 --> 00:11:46.470 align:start position:0% able to subscription over the JSON RPC 00:11:46.470 --> 00:11:48.140 align:start position:0% able to subscription over the JSON RPC interface<00:11:46.890> that<00:11:47.370> would<00:11:47.460> just<00:11:47.670> like<00:11:47.850> spit<00:11:48.090> out 00:11:48.140 --> 00:11:48.150 align:start position:0% interface that would just like spit out 00:11:48.150 --> 00:11:49.610 align:start position:0% interface that would just like spit out those<00:11:48.450> bits<00:11:48.690> that<00:11:48.900> they're<00:11:49.050> happening<00:11:49.350> and 00:11:49.610 --> 00:11:49.620 align:start position:0% those bits that they're happening and 00:11:49.620 --> 00:11:51.680 align:start position:0% those bits that they're happening and you<00:11:50.040> can<00:11:50.220> even<00:11:50.370> say<00:11:50.700> like<00:11:50.940> specifically<00:11:51.480> and 00:11:51.680 --> 00:11:51.690 align:start position:0% you can even say like specifically and 00:11:51.690 --> 00:11:53.150 align:start position:0% you can even say like specifically and we<00:11:51.840> want<00:11:52.020> you<00:11:52.080> to<00:11:52.110> publish<00:11:52.440> just<00:11:52.710> me<00:11:52.920> if<00:11:53.040> they 00:11:53.150 --> 00:11:53.160 align:start position:0% we want you to publish just me if they 00:11:53.160 --> 00:11:55.130 align:start position:0% we want you to publish just me if they come<00:11:53.340> from<00:11:53.460> a<00:11:53.550> given<00:11:53.790> smart<00:11:54.060> contract<00:11:54.540> right 00:11:55.130 --> 00:11:55.140 align:start position:0% come from a given smart contract right 00:11:55.140 --> 00:11:57.650 align:start position:0% come from a given smart contract right so<00:11:55.410> part<00:11:56.160> of<00:11:56.250> our<00:11:56.370> sort<00:11:56.610> of<00:11:56.700> open<00:11:57.090> source<00:11:57.330> work 00:11:57.650 --> 00:11:57.660 align:start position:0% so part of our sort of open source work 00:11:57.660 --> 00:11:59.660 align:start position:0% so part of our sort of open source work is<00:11:57.960> to<00:11:58.320> figure<00:11:58.560> out<00:11:58.680> a<00:11:58.800> way<00:11:58.950> to<00:11:59.010> get<00:11:59.220> this<00:11:59.400> done 00:11:59.660 --> 00:11:59.670 align:start position:0% is to figure out a way to get this done 00:11:59.670 --> 00:12:02.540 align:start position:0% is to figure out a way to get this done and<00:12:00.000> get<00:12:00.120> that<00:12:00.300> upstream<00:12:00.870> into<00:12:01.280> gap<00:12:02.280> and 00:12:02.540 --> 00:12:02.550 align:start position:0% and get that upstream into gap and 00:12:02.550 --> 00:12:04.820 align:start position:0% and get that upstream into gap and parity<00:12:02.940> and<00:12:03.030> so<00:12:03.240> forth<00:12:03.570> so<00:12:03.780> that<00:12:03.810> you<00:12:04.500> can<00:12:04.650> sort 00:12:04.820 --> 00:12:04.830 align:start position:0% parity and so forth so that you can sort 00:12:04.830 --> 00:12:06.560 align:start position:0% parity and so forth so that you can sort of<00:12:04.890> plug<00:12:05.190> in<00:12:05.340> that<00:12:05.460> subscription<00:12:05.880> directly<00:12:06.480> to 00:12:06.560 --> 00:12:06.570 align:start position:0% of plug in that subscription directly to 00:12:06.570 --> 00:12:09.080 align:start position:0% of plug in that subscription directly to vault<00:12:06.750> as<00:12:06.990> DP<00:12:07.430> have<00:12:08.430> a<00:12:08.460> plug-in<00:12:08.790> that's 00:12:09.080 --> 00:12:09.090 align:start position:0% vault as DP have a plug-in that's 00:12:09.090 --> 00:12:11.200 align:start position:0% vault as DP have a plug-in that's parsing<00:12:09.540> that<00:12:09.660> end<00:12:09.900> up<00:12:10.020> on<00:12:10.140> the<00:12:10.260> fly<00:12:10.470> and<00:12:10.860> you 00:12:11.200 --> 00:12:11.210 align:start position:0% parsing that end up on the fly and you 00:12:11.210 --> 00:12:14.120 align:start position:0% parsing that end up on the fly and you can<00:12:12.210> be<00:12:12.360> accessing<00:12:12.780> state<00:12:13.140> data<00:12:13.380> with<00:12:14.100> a 00:12:14.120 --> 00:12:14.130 align:start position:0% can be accessing state data with a 00:12:14.130 --> 00:12:16.160 align:start position:0% can be accessing state data with a plugin<00:12:14.550> that<00:12:14.580> took<00:12:15.000> ideally<00:12:15.510> and<00:12:15.780> minimal 00:12:16.160 --> 00:12:16.170 align:start position:0% plugin that took ideally and minimal 00:12:16.170 --> 00:12:19.010 align:start position:0% plugin that took ideally and minimal amount<00:12:16.380> of<00:12:16.470> code<00:12:17.420> another<00:12:18.420> thing<00:12:18.720> that<00:12:18.900> we've 00:12:19.010 --> 00:12:19.020 align:start position:0% amount of code another thing that we've 00:12:19.020 --> 00:12:20.720 align:start position:0% amount of code another thing that we've got<00:12:19.200> coming<00:12:19.500> down<00:12:19.680> the<00:12:19.800> pipeline<00:12:20.010> is<00:12:20.430> what<00:12:20.610> we 00:12:20.720 --> 00:12:20.730 align:start position:0% got coming down the pipeline is what we 00:12:20.730 --> 00:12:23.090 align:start position:0% got coming down the pipeline is what we call<00:12:20.940> the<00:12:21.090> super<00:12:21.420> node<00:12:21.570> so<00:12:22.020> the<00:12:22.230> idea<00:12:22.740> for<00:12:22.860> the 00:12:23.090 --> 00:12:23.100 align:start position:0% call the super node so the idea for the 00:12:23.100 --> 00:12:24.470 align:start position:0% call the super node so the idea for the super<00:12:23.430> node<00:12:23.580> is<00:12:23.850> that<00:12:24.060> we<00:12:24.270> will<00:12:24.450> be 00:12:24.470 --> 00:12:24.480 align:start position:0% super node is that we will be 00:12:24.480 --> 00:12:28.220 align:start position:0% super node is that we will be automatically<00:12:25.410> digesting<00:12:26.250> all<00:12:26.960> those<00:12:27.960> states 00:12:28.220 --> 00:12:28.230 align:start position:0% automatically digesting all those states 00:12:28.230 --> 00:12:30.110 align:start position:0% automatically digesting all those states and<00:12:28.320> storage<00:12:28.680> tips<00:12:28.920> but<00:12:29.100> also<00:12:29.280> blocks<00:12:29.760> and 00:12:30.110 --> 00:12:30.120 align:start position:0% and storage tips but also blocks and 00:12:30.120 --> 00:12:32.840 align:start position:0% and storage tips but also blocks and also<00:12:30.480> proofs<00:12:31.110> for<00:12:31.800> the<00:12:31.860> deaths<00:12:32.520> that<00:12:32.670> are 00:12:32.840 --> 00:12:32.850 align:start position:0% also proofs for the deaths that are 00:12:32.850 --> 00:12:36.110 align:start position:0% also proofs for the deaths that are coming<00:12:33.150> out<00:12:33.270> of<00:12:33.450> a<00:12:33.540> node<00:12:33.860> and<00:12:34.860> our<00:12:35.550> goal<00:12:35.760> is<00:12:36.060> to 00:12:36.110 --> 00:12:36.120 align:start position:0% coming out of a node and our goal is to 00:12:36.120 --> 00:12:39.440 align:start position:0% coming out of a node and our goal is to publish<00:12:36.960> all<00:12:37.440> of<00:12:37.680> that<00:12:37.860> data<00:12:38.100> to<00:12:38.430> ipfs<00:12:39.150> and 00:12:39.440 --> 00:12:39.450 align:start position:0% publish all of that data to ipfs and 00:12:39.450 --> 00:12:42.260 align:start position:0% publish all of that data to ipfs and have<00:12:39.600> vulcanize<00:12:40.110> DB<00:12:40.590> serve<00:12:41.370> as<00:12:41.730> sort<00:12:42.120> of<00:12:42.150> a 00:12:42.260 --> 00:12:42.270 align:start position:0% have vulcanize DB serve as sort of a 00:12:42.270 --> 00:12:45.290 align:start position:0% have vulcanize DB serve as sort of a filtering<00:12:42.780> layer<00:12:43.020> where<00:12:43.740> you<00:12:43.770> can<00:12:44.010> say<00:12:44.250> I<00:12:44.640> want 00:12:45.290 --> 00:12:45.300 align:start position:0% filtering layer where you can say I want 00:12:45.300 --> 00:12:48.020 align:start position:0% filtering layer where you can say I want to<00:12:45.450> get<00:12:45.600> all<00:12:45.900> of<00:12:46.080> the<00:12:46.200> dips<00:12:46.440> from<00:12:46.890> X<00:12:47.340> contract 00:12:48.020 --> 00:12:48.030 align:start position:0% to get all of the dips from X contract 00:12:48.030 --> 00:12:49.790 align:start position:0% to get all of the dips from X contract and<00:12:48.330> we<00:12:48.480> will<00:12:48.600> give<00:12:48.750> you<00:12:48.780> a<00:12:48.930> list<00:12:49.110> of<00:12:49.260> contact 00:12:49.790 --> 00:12:49.800 align:start position:0% and we will give you a list of contact 00:12:49.800 --> 00:12:52.730 align:start position:0% and we will give you a list of contact addresses<00:12:50.070> back<00:12:50.670> on<00:12:50.940> content<00:12:51.720> of<00:12:51.810> justice<00:12:52.170> C 00:12:52.730 --> 00:12:52.740 align:start position:0% addresses back on content of justice C 00:12:52.740 --> 00:12:55.940 align:start position:0% addresses back on content of justice C IDs<00:12:53.070> and<00:12:53.390> you<00:12:54.390> can<00:12:54.570> then<00:12:54.690> query<00:12:54.960> ipfs<00:12:55.620> for<00:12:55.860> that 00:12:55.940 --> 00:12:55.950 align:start position:0% IDs and you can then query ipfs for that 00:12:55.950 --> 00:12:57.720 align:start position:0% IDs and you can then query ipfs for that data<00:12:56.190> and<00:12:56.520> you<00:12:57.120> can<00:12:57.150> get 00:12:57.720 --> 00:12:57.730 align:start position:0% data and you can get 00:12:57.730 --> 00:13:00.090 align:start position:0% data and you can get groups<00:12:57.880> with<00:12:58.089> it<00:12:58.269> right<00:12:58.570> so<00:12:58.930> you<00:12:59.740> don't<00:12:59.860> have 00:13:00.090 --> 00:13:00.100 align:start position:0% groups with it right so you don't have 00:13:00.100 --> 00:13:02.129 align:start position:0% groups with it right so you don't have to<00:13:00.279> trust<00:13:00.670> that<00:13:01.000> we're<00:13:01.300> giving<00:13:01.660> you<00:13:01.690> like<00:13:01.990> the 00:13:02.129 --> 00:13:02.139 align:start position:0% to trust that we're giving you like the 00:13:02.139 --> 00:13:03.810 align:start position:0% to trust that we're giving you like the correct<00:13:02.440> data<00:13:02.649> then<00:13:02.949> that<00:13:02.980> data<00:13:03.310> is<00:13:03.490> valid 00:13:03.810 --> 00:13:03.820 align:start position:0% correct data then that data is valid 00:13:03.820 --> 00:13:05.310 align:start position:0% correct data then that data is valid because<00:13:03.910> you<00:13:04.209> can<00:13:04.360> submit<00:13:04.600> that<00:13:04.839> proof<00:13:05.139> to 00:13:05.310 --> 00:13:05.320 align:start position:0% because you can submit that proof to 00:13:05.320 --> 00:13:07.949 align:start position:0% because you can submit that proof to your<00:13:05.410> new<00:13:05.589> one<00:13:06.130> in<00:13:06.760> order<00:13:06.970> to<00:13:07.089> verify<00:13:07.480> that 00:13:07.949 --> 00:13:07.959 align:start position:0% your new one in order to verify that 00:13:07.959 --> 00:13:10.319 align:start position:0% your new one in order to verify that that<00:13:08.079> ADA<00:13:08.380> isn't<00:13:09.160> back<00:13:09.339> to<00:13:09.610> what<00:13:09.850> we<00:13:09.970> say<00:13:10.120> it<00:13:10.240> is 00:13:10.319 --> 00:13:10.329 align:start position:0% that ADA isn't back to what we say it is 00:13:10.329 --> 00:13:13.980 align:start position:0% that ADA isn't back to what we say it is and<00:13:10.600> so<00:13:11.910> again<00:13:12.910> we<00:13:13.089> think<00:13:13.120> this<00:13:13.360> is<00:13:13.420> like<00:13:13.660> super 00:13:13.980 --> 00:13:13.990 align:start position:0% and so again we think this is like super 00:13:13.990 --> 00:13:16.939 align:start position:0% and so again we think this is like super cool<00:13:14.139> work<00:13:14.380> hopefully<00:13:15.279> you<00:13:15.610> can<00:13:15.910> like<00:13:16.120> share 00:13:16.939 --> 00:13:16.949 align:start position:0% cool work hopefully you can like share 00:13:16.949 --> 00:13:19.500 align:start position:0% cool work hopefully you can like share dr.<00:13:17.949> Campos<00:13:18.339> style<00:13:18.730> demo<00:13:19.000> the<00:13:19.180> Colette's<00:13:19.389> you 00:13:19.500 --> 00:13:19.510 align:start position:0% dr. Campos style demo the Colette's you 00:13:19.510 --> 00:13:22.280 align:start position:0% dr. Campos style demo the Colette's you do<00:13:19.660> this<00:13:19.810> next<00:13:20.560> year<00:13:20.680> maybe<00:13:20.949> your<00:13:21.160> even<00:13:21.399> sooner 00:13:22.280 --> 00:13:22.290 align:start position:0% do this next year maybe your even sooner 00:13:22.290 --> 00:13:25.410 align:start position:0% do this next year maybe your even sooner but<00:13:23.290> that's<00:13:23.709> that's<00:13:24.070> some<00:13:24.430> huge<00:13:24.970> primary 00:13:25.410 --> 00:13:25.420 align:start position:0% but that's that's some huge primary 00:13:25.420 --> 00:13:27.889 align:start position:0% but that's that's some huge primary stress<00:13:25.779> and<00:13:26.050> you<00:13:26.649> know<00:13:26.769> we<00:13:27.010> always<00:13:27.279> welcome 00:13:27.889 --> 00:13:27.899 align:start position:0% stress and you know we always welcome 00:13:27.899 --> 00:13:30.210 align:start position:0% stress and you know we always welcome issues<00:13:28.899> pull<00:13:29.199> requests<00:13:29.649> that<00:13:29.709> people<00:13:29.769> think 00:13:30.210 --> 00:13:30.220 align:start position:0% issues pull requests that people think 00:13:30.220 --> 00:13:31.620 align:start position:0% issues pull requests that people think that<00:13:30.430> other<00:13:30.610> priorities<00:13:31.120> are<00:13:31.240> worth<00:13:31.360> tracking 00:13:31.620 --> 00:13:31.630 align:start position:0% that other priorities are worth tracking 00:13:31.630 --> 00:13:36.930 align:start position:0% that other priorities are worth tracking down<00:13:31.810> as<00:13:32.019> well<00:13:33.480> so<00:13:35.040> this<00:13:36.040> is<00:13:36.220> the<00:13:36.339> part<00:13:36.579> of<00:13:36.730> the 00:13:36.930 --> 00:13:36.940 align:start position:0% down as well so this is the part of the 00:13:36.940 --> 00:13:38.639 align:start position:0% down as well so this is the part of the workshop<00:13:37.360> where<00:13:37.630> I<00:13:37.660> would<00:13:38.019> be<00:13:38.110> staying<00:13:38.320> like 00:13:38.639 --> 00:13:38.649 align:start position:0% workshop where I would be staying like 00:13:38.649 --> 00:13:40.920 align:start position:0% workshop where I would be staying like let's<00:13:39.040> go<00:13:39.160> ahead<00:13:39.399> and<00:13:39.550> try<00:13:39.699> this<00:13:39.760> out<00:13:40.149> everyone 00:13:40.920 --> 00:13:40.930 align:start position:0% let's go ahead and try this out everyone 00:13:40.930 --> 00:13:43.319 align:start position:0% let's go ahead and try this out everyone run<00:13:41.440> your<00:13:41.649> own<00:13:41.800> instance<00:13:42.279> of<00:13:42.370> vulcanize<00:13:42.820> DB<00:13:43.209> on 00:13:43.319 --> 00:13:43.329 align:start position:0% run your own instance of vulcanize DB on 00:13:43.329 --> 00:13:45.480 align:start position:0% run your own instance of vulcanize DB on their<00:13:43.510> machine<00:13:43.779> if<00:13:44.320> you<00:13:44.470> have<00:13:44.620> internet<00:13:45.040> we 00:13:45.480 --> 00:13:45.490 align:start position:0% their machine if you have internet we 00:13:45.490 --> 00:13:48.240 align:start position:0% their machine if you have internet we even<00:13:45.610> like<00:13:45.820> performance<00:13:46.389> tested<00:13:46.870> a<00:13:47.380> node<00:13:48.010> back 00:13:48.240 --> 00:13:48.250 align:start position:0% even like performance tested a node back 00:13:48.250 --> 00:13:49.889 align:start position:0% even like performance tested a node back home<00:13:48.490> that<00:13:48.639> you<00:13:48.699> can<00:13:48.850> connect<00:13:49.149> to<00:13:49.240> but<00:13:49.570> I<00:13:49.660> don't 00:13:49.889 --> 00:13:49.899 align:start position:0% home that you can connect to but I don't 00:13:49.899 --> 00:13:51.210 align:start position:0% home that you can connect to but I don't think<00:13:50.079> performance<00:13:50.709> is<00:13:50.829> going<00:13:51.010> to<00:13:51.070> be<00:13:51.190> a 00:13:51.210 --> 00:13:51.220 align:start position:0% think performance is going to be a 00:13:51.220 --> 00:13:56.480 align:start position:0% think performance is going to be a problem<00:13:52.230> with<00:13:53.230> an<00:13:53.350> internet<00:13:53.829> issue<00:13:54.070> here<00:13:55.050> so 00:13:56.480 --> 00:13:56.490 align:start position:0% problem with an internet issue here so 00:13:56.490 --> 00:14:00.060 align:start position:0% problem with an internet issue here so to<00:13:57.490> walk<00:13:57.670> into<00:13:58.180> our<00:13:58.389> stack<00:13:58.720> you<00:13:59.019> know<00:13:59.110> both<00:13:59.860> men 00:14:00.060 --> 00:14:00.070 align:start position:0% to walk into our stack you know both men 00:14:00.070 --> 00:14:01.920 align:start position:0% to walk into our stack you know both men TVs<00:14:00.430> written<00:14:00.760> and<00:14:00.880> go<00:14:01.029> it<00:14:01.480> was<00:14:01.600> pretty<00:14:01.750> nice 00:14:01.920 --> 00:14:01.930 align:start position:0% TVs written and go it was pretty nice 00:14:01.930 --> 00:14:03.360 align:start position:0% TVs written and go it was pretty nice because<00:14:02.139> it<00:14:02.380> enabled<00:14:02.680> us<00:14:02.769> to<00:14:02.829> like<00:14:03.160> really 00:14:03.360 --> 00:14:03.370 align:start position:0% because it enabled us to like really 00:14:03.370 --> 00:14:05.189 align:start position:0% because it enabled us to like really easily<00:14:03.699> integrate<00:14:04.120> with<00:14:04.300> going<00:14:04.540> theory<00:14:04.720> like 00:14:05.189 --> 00:14:05.199 align:start position:0% easily integrate with going theory like 00:14:05.199 --> 00:14:07.680 align:start position:0% easily integrate with going theory like unpacking<00:14:05.709> logs<00:14:05.920> and<00:14:06.190> so<00:14:06.310> forth<00:14:06.690> Postgres 00:14:07.680 --> 00:14:07.690 align:start position:0% unpacking logs and so forth Postgres 00:14:07.690 --> 00:14:10.879 align:start position:0% unpacking logs and so forth Postgres obviously<00:14:08.319> talked<00:14:08.500> about<00:14:08.529> after<00:14:09.069> graph<00:14:09.250> QL 00:14:10.879 --> 00:14:10.889 align:start position:0% obviously talked about after graph QL 00:14:10.889 --> 00:14:14.189 align:start position:0% obviously talked about after graph QL this<00:14:11.889> set<00:14:12.160> up<00:14:12.310> on<00:14:12.519> this<00:14:12.910> slide<00:14:13.060> is<00:14:13.600> exactly 00:14:14.189 --> 00:14:14.199 align:start position:0% this set up on this slide is exactly 00:14:14.199 --> 00:14:16.980 align:start position:0% this set up on this slide is exactly what<00:14:14.709> it<00:14:14.800> says<00:14:15.010> on<00:14:15.220> the<00:14:15.279> morning<00:14:15.750> but<00:14:16.750> you<00:14:16.899> know 00:14:16.980 --> 00:14:16.990 align:start position:0% what it says on the morning but you know 00:14:16.990 --> 00:14:18.389 align:start position:0% what it says on the morning but you know try<00:14:17.260> it<00:14:17.319> out<00:14:17.470> when<00:14:17.560> you're<00:14:17.709> at<00:14:17.769> the<00:14:17.860> hotel<00:14:18.010> or 00:14:18.389 --> 00:14:18.399 align:start position:0% try it out when you're at the hotel or 00:14:18.399 --> 00:14:21.360 align:start position:0% try it out when you're at the hotel or home<00:14:18.579> or<00:14:18.819> whatever<00:14:19.089> like<00:14:19.420> definitely<00:14:20.050> did<00:14:20.470> get 00:14:21.360 --> 00:14:21.370 align:start position:0% home or whatever like definitely did get 00:14:21.370 --> 00:14:25.319 align:start position:0% home or whatever like definitely did get feedback<00:14:21.730> on<00:14:21.940> this<00:14:23.160> so<00:14:24.160> what<00:14:24.850> I<00:14:24.880> wanted<00:14:25.209> to 00:14:25.319 --> 00:14:25.329 align:start position:0% feedback on this so what I wanted to 00:14:25.329 --> 00:14:27.600 align:start position:0% feedback on this so what I wanted to point<00:14:25.540> out<00:14:25.720> about<00:14:25.990> the<00:14:26.649> setup<00:14:27.069> that<00:14:27.250> we're 00:14:27.600 --> 00:14:27.610 align:start position:0% point out about the setup that we're 00:14:27.610 --> 00:14:30.600 align:start position:0% point out about the setup that we're showing<00:14:27.850> is<00:14:28.360> our<00:14:28.630> config<00:14:29.079> file<00:14:29.319> this<00:14:30.130> config 00:14:30.600 --> 00:14:30.610 align:start position:0% showing is our config file this config 00:14:30.610 --> 00:14:33.389 align:start position:0% showing is our config file this config file<00:14:30.850> is<00:14:31.180> 20<00:14:31.600> lines<00:14:31.810> this<00:14:32.470> config<00:14:32.860> file<00:14:33.040> also 00:14:33.389 --> 00:14:33.399 align:start position:0% file is 20 lines this config file also 00:14:33.399 --> 00:14:37.230 align:start position:0% file is 20 lines this config file also yields<00:14:34.000> parsed<00:14:34.690> events<00:14:35.139> from<00:14:35.920> all<00:14:36.399> three 00:14:37.230 --> 00:14:37.240 align:start position:0% yields parsed events from all three 00:14:37.240 --> 00:14:39.509 align:start position:0% yields parsed events from all three Moammar<00:14:37.990> contracts<00:14:38.529> the<00:14:38.740> Bhullar<00:14:39.040> contract 00:14:39.509 --> 00:14:39.519 align:start position:0% Moammar contracts the Bhullar contract 00:14:39.519 --> 00:14:41.309 align:start position:0% Moammar contracts the Bhullar contract you'll<00:14:39.790> make<00:14:40.029> contract<00:14:40.540> in<00:14:40.720> the<00:14:40.779> black<00:14:41.110> pool 00:14:41.309 --> 00:14:41.319 align:start position:0% you'll make contract in the black pool 00:14:41.319 --> 00:14:43.710 align:start position:0% you'll make contract in the black pool contract<00:14:41.829> and<00:14:42.160> to<00:14:42.550> be<00:14:42.639> honest<00:14:43.000> some<00:14:43.569> of<00:14:43.630> that 00:14:43.710 --> 00:14:43.720 align:start position:0% contract and to be honest some of that 00:14:43.720 --> 00:14:45.570 align:start position:0% contract and to be honest some of that data<00:14:43.930> at<00:14:44.110> the<00:14:44.230> top<00:14:44.410> I'm<00:14:44.620> gonna<00:14:44.829> put<00:14:45.040> in 00:14:45.570 --> 00:14:45.580 align:start position:0% data at the top I'm gonna put in 00:14:45.580 --> 00:14:47.220 align:start position:0% data at the top I'm gonna put in variables<00:14:46.120> to<00:14:46.330> slim<00:14:46.540> this<00:14:46.720> down<00:14:46.930> even<00:14:46.960> more 00:14:47.220 --> 00:14:47.230 align:start position:0% variables to slim this down even more 00:14:47.230 --> 00:14:48.840 align:start position:0% variables to slim this down even more but<00:14:47.950> I<00:14:48.040> just<00:14:48.130> wanted<00:14:48.310> to<00:14:48.370> show<00:14:48.550> you<00:14:48.610> like 00:14:48.840 --> 00:14:48.850 align:start position:0% but I just wanted to show you like 00:14:48.850 --> 00:14:51.360 align:start position:0% but I just wanted to show you like everything<00:14:49.210> you<00:14:49.480> need<00:14:49.660> to<00:14:50.080> do<00:14:50.350> to<00:14:51.100> do<00:14:51.220> this 00:14:51.360 --> 00:14:51.370 align:start position:0% everything you need to do to do this 00:14:51.370 --> 00:14:55.920 align:start position:0% everything you need to do to do this work<00:14:52.320> so<00:14:53.320> what's<00:14:53.880> happening<00:14:54.880> under<00:14:55.630> the<00:14:55.720> hood 00:14:55.920 --> 00:14:55.930 align:start position:0% work so what's happening under the hood 00:14:55.930 --> 00:14:58.380 align:start position:0% work so what's happening under the hood you've<00:14:56.770> got<00:14:56.950> this<00:14:57.130> configuration<00:14:57.820> file<00:14:58.060> and 00:14:58.380 --> 00:14:58.390 align:start position:0% you've got this configuration file and 00:14:58.390 --> 00:15:00.960 align:start position:0% you've got this configuration file and then<00:14:58.900> you're<00:14:59.740> running<00:14:59.890> three<00:15:00.790> of<00:15:00.880> the 00:15:00.960 --> 00:15:00.970 align:start position:0% then you're running three of the 00:15:00.970 --> 00:15:03.000 align:start position:0% then you're running three of the processes<00:15:01.540> that<00:15:01.570> I<00:15:01.810> mentioned<00:15:02.170> right<00:15:02.800> so 00:15:03.000 --> 00:15:03.010 align:start position:0% processes that I mentioned right so 00:15:03.010 --> 00:15:04.800 align:start position:0% processes that I mentioned right so you're<00:15:03.160> saying<00:15:03.400> I<00:15:03.670> had<00:15:04.450> an<00:15:04.600> interesting 00:15:04.800 --> 00:15:04.810 align:start position:0% you're saying I had an interesting 00:15:04.810 --> 00:15:06.810 align:start position:0% you're saying I had an interesting process<00:15:05.320> pointed<00:15:06.010> that<00:15:06.160> config<00:15:06.610> file 00:15:06.810 --> 00:15:06.820 align:start position:0% process pointed that config file 00:15:06.820 --> 00:15:09.240 align:start position:0% process pointed that config file starting<00:15:07.570> at<00:15:07.690> the<00:15:07.780> deployment<00:15:08.290> block<00:15:08.470> or 00:15:09.240 --> 00:15:09.250 align:start position:0% starting at the deployment block or 00:15:09.250 --> 00:15:12.000 align:start position:0% starting at the deployment block or bowler<00:15:09.610> I<00:15:09.910> want<00:15:10.600> to<00:15:10.810> run<00:15:11.080> a<00:15:11.110> contract<00:15:11.650> watcher 00:15:12.000 --> 00:15:12.010 align:start position:0% bowler I want to run a contract watcher 00:15:12.010 --> 00:15:14.100 align:start position:0% bowler I want to run a contract watcher process<00:15:12.460> with<00:15:12.640> that<00:15:12.670> config<00:15:13.150> file<00:15:13.360> and<00:15:13.750> the 00:15:14.100 --> 00:15:14.110 align:start position:0% process with that config file and the 00:15:14.110 --> 00:15:17.070 align:start position:0% process with that config file and the most<00:15:14.290> cumbersome<00:15:15.570> command<00:15:16.570> at<00:15:16.720> this<00:15:16.810> post 00:15:17.070 --> 00:15:17.080 align:start position:0% most cumbersome command at this post 00:15:17.080 --> 00:15:18.690 align:start position:0% most cumbersome command at this post route<00:15:17.290> but<00:15:17.680> that's<00:15:17.830> our<00:15:17.980> fault<00:15:18.220> because<00:15:18.400> the 00:15:18.690 --> 00:15:18.700 align:start position:0% route but that's our fault because the 00:15:18.700 --> 00:15:20.910 align:start position:0% route but that's our fault because the way<00:15:18.790> that<00:15:18.940> we<00:15:19.090> set<00:15:19.690> up<00:15:19.870> these<00:15:20.050> schemas<00:15:20.500> for<00:15:20.560> the 00:15:20.910 --> 00:15:20.920 align:start position:0% way that we set up these schemas for the 00:15:20.920 --> 00:15:23.610 align:start position:0% way that we set up these schemas for the contracts<00:15:21.400> is<00:15:21.670> Petter<00:15:22.480> they<00:15:22.900> said<00:15:23.320> this<00:15:23.470> is 00:15:23.610 --> 00:15:23.620 align:start position:0% contracts is Petter they said this is 00:15:23.620 --> 00:15:25.440 align:start position:0% contracts is Petter they said this is the<00:15:23.650> header<00:15:23.920> sync<00:15:24.220> process<00:15:24.700> and<00:15:24.970> the<00:15:25.030> contract 00:15:25.440 --> 00:15:25.450 align:start position:0% the header sync process and the contract 00:15:25.450 --> 00:15:27.360 align:start position:0% the header sync process and the contract watcher<00:15:25.840> the<00:15:25.930> training<00:15:26.320> this<00:15:26.440> data<00:15:26.680> and<00:15:27.010> then 00:15:27.360 --> 00:15:27.370 align:start position:0% watcher the training this data and then 00:15:27.370 --> 00:15:29.070 align:start position:0% watcher the training this data and then into<00:15:27.580> the<00:15:27.640> contract<00:15:28.060> address<00:15:28.360> right<00:15:28.810> so 00:15:29.070 --> 00:15:29.080 align:start position:0% into the contract address right so 00:15:29.080 --> 00:15:30.960 align:start position:0% into the contract address right so fairly<00:15:29.920> straightforward<00:15:30.070> they've<00:15:30.760> populated 00:15:30.960 --> 00:15:30.970 align:start position:0% fairly straightforward they've populated 00:15:30.970 --> 00:15:33.600 align:start position:0% fairly straightforward they've populated this<00:15:31.330> data<00:15:31.570> with<00:15:31.870> any<00:15:32.080> arbitrary<00:15:32.740> adjust<00:15:33.430> you 00:15:33.600 --> 00:15:33.610 align:start position:0% this data with any arbitrary adjust you 00:15:33.610 --> 00:15:35.370 align:start position:0% this data with any arbitrary adjust you wanted<00:15:33.940> you<00:15:34.150> know<00:15:34.240> you<00:15:34.300> can<00:15:34.540> point<00:15:34.720> this<00:15:34.960> email 00:15:35.370 --> 00:15:35.380 align:start position:0% wanted you know you can point this email 00:15:35.380 --> 00:15:37.890 align:start position:0% wanted you know you can point this email it'll<00:15:35.830> be<00:15:36.100> there<00:15:36.310> there's<00:15:36.910> a<00:15:37.000> little<00:15:37.180> W<00:15:37.630> flag 00:15:37.890 --> 00:15:37.900 align:start position:0% it'll be there there's a little W flag 00:15:37.900 --> 00:15:39.660 align:start position:0% it'll be there there's a little W flag there<00:15:38.200> which<00:15:38.410> is<00:15:38.560> important<00:15:39.100> right<00:15:39.280> like<00:15:39.490> you 00:15:39.660 --> 00:15:39.670 align:start position:0% there which is important right like you 00:15:39.670 --> 00:15:41.730 align:start position:0% there which is important right like you can<00:15:39.820> kick<00:15:40.030> off<00:15:40.210> this<00:15:40.510> post<00:15:40.750> graph<00:15:41.050> out<00:15:41.230> process 00:15:41.730 --> 00:15:41.740 align:start position:0% can kick off this post graph out process 00:15:41.740 --> 00:15:43.530 align:start position:0% can kick off this post graph out process as<00:15:42.010> soon<00:15:42.250> as<00:15:42.550> you<00:15:42.670> kick<00:15:42.850> off<00:15:43.000> the<00:15:43.180> contract 00:15:43.530 --> 00:15:43.540 align:start position:0% as soon as you kick off the contract 00:15:43.540 --> 00:15:46.650 align:start position:0% as soon as you kick off the contract watcher<00:15:44.050> and<00:15:44.520> with<00:15:45.520> the<00:15:45.610> W<00:15:45.940> flag<00:15:46.210> it'll<00:15:46.570> be 00:15:46.650 --> 00:15:46.660 align:start position:0% watcher and with the W flag it'll be 00:15:46.660 --> 00:15:49.320 align:start position:0% watcher and with the W flag it'll be watching<00:15:47.050> the<00:15:47.200> schema<00:15:47.610> so<00:15:48.610> you'll<00:15:48.790> see<00:15:48.970> a 00:15:49.320 --> 00:15:49.330 align:start position:0% watching the schema so you'll see a 00:15:49.330 --> 00:15:52.530 align:start position:0% watching the schema so you'll see a warning<00:15:50.140> perhaps<00:15:50.440> it'll<00:15:50.950> say<00:15:51.160> like<00:15:51.430> hey<00:15:52.360> we 00:15:52.530 --> 00:15:52.540 align:start position:0% warning perhaps it'll say like hey we 00:15:52.540 --> 00:15:53.910 align:start position:0% warning perhaps it'll say like hey we don't<00:15:52.630> have<00:15:52.810> anything<00:15:53.050> in<00:15:53.200> the<00:15:53.380> schema<00:15:53.740> right 00:15:53.910 --> 00:15:53.920 align:start position:0% don't have anything in the schema right 00:15:53.920 --> 00:15:56.250 align:start position:0% don't have anything in the schema right now<00:15:54.100> and<00:15:54.460> then<00:15:55.180> that<00:15:55.450> the<00:15:55.600> contract<00:15:56.020> water 00:15:56.250 --> 00:15:56.260 align:start position:0% now and then that the contract water 00:15:56.260 --> 00:15:58.500 align:start position:0% now and then that the contract water starts<00:15:56.710> to<00:15:56.770> populate<00:15:57.280> that<00:15:57.310> data<00:15:57.670> ok<00:15:58.360> the 00:15:58.500 --> 00:15:58.510 align:start position:0% starts to populate that data ok the 00:15:58.510 --> 00:16:00.510 align:start position:0% starts to populate that data ok the schemas<00:15:58.870> here<00:15:59.140> you<00:15:59.470> can<00:15:59.620> load<00:15:59.740> it<00:15:59.890> in<00:16:00.130> when<00:16:00.430> you 00:16:00.510 --> 00:16:00.520 align:start position:0% schemas here you can load it in when you 00:16:00.520 --> 00:16:01.650 align:start position:0% schemas here you can load it in when you refresh<00:16:00.880> your<00:16:00.910> browser<00:16:01.180> you're<00:16:01.480> going<00:16:01.600> to 00:16:01.650 --> 00:16:01.660 align:start position:0% refresh your browser you're going to 00:16:01.660 --> 00:16:04.380 align:start position:0% refresh your browser you're going to have<00:16:01.840> that<00:16:02.410> data<00:16:02.830> expose<00:16:03.370> in<00:16:03.700> what's<00:16:04.180> going 00:16:04.380 --> 00:16:04.390 align:start position:0% have that data expose in what's going 00:16:04.390 --> 00:16:11.610 align:start position:0% have that data expose in what's going well<00:16:05.190> so<00:16:06.190> in<00:16:07.290> a<00:16:08.490> workshop<00:16:09.990> well<00:16:11.020> ability<00:16:11.590> to 00:16:11.610 --> 00:16:11.620 align:start position:0% well so in a workshop well ability to 00:16:11.620 --> 00:16:16.410 align:start position:0% well so in a workshop well ability to run<00:16:11.950> this<00:16:12.190> stuff<00:16:13.920> we've<00:16:14.920> got<00:16:15.160> I've<00:16:16.000> got<00:16:16.210> sort 00:16:16.410 --> 00:16:16.420 align:start position:0% run this stuff we've got I've got sort 00:16:16.420 --> 00:16:21.630 align:start position:0% run this stuff we've got I've got sort of<00:16:16.480> the<00:16:16.570> demo<00:16:16.810> here<00:16:17.730> so<00:16:18.750> this<00:16:19.750> is<00:16:20.430> this<00:16:21.430> is<00:16:21.490> a 00:16:21.630 --> 00:16:21.640 align:start position:0% of the demo here so this is this is a 00:16:21.640 --> 00:16:23.910 align:start position:0% of the demo here so this is this is a set<00:16:21.910> up<00:16:22.030> instance<00:16:22.480> so<00:16:22.690> I<00:16:22.900> added<00:16:23.410> this<00:16:23.710> whole 00:16:23.910 --> 00:16:23.920 align:start position:0% set up instance so I added this whole 00:16:23.920 --> 00:16:26.010 align:start position:0% set up instance so I added this whole thing<00:16:24.130> these<00:16:24.940> steps<00:16:25.180> that<00:16:25.390> I'm<00:16:25.480> asking 00:16:26.010 --> 00:16:26.020 align:start position:0% thing these steps that I'm asking 00:16:26.020 --> 00:16:26.550 align:start position:0% thing these steps that I'm asking everyone 00:16:26.550 --> 00:16:26.560 align:start position:0% everyone 00:16:26.560 --> 00:16:30.929 align:start position:0% everyone to<00:16:26.649> do<00:16:26.769> and<00:16:28.649> this<00:16:29.649> is<00:16:29.889> the<00:16:30.129> this<00:16:30.759> is<00:16:30.819> the 00:16:30.929 --> 00:16:30.939 align:start position:0% to do and this is the this is the 00:16:30.939 --> 00:16:33.079 align:start position:0% to do and this is the this is the photograph<00:16:31.240> file<00:16:31.720> interface<00:16:31.990> that<00:16:32.410> we<00:16:32.560> have 00:16:33.079 --> 00:16:33.089 align:start position:0% photograph file interface that we have 00:16:33.089 --> 00:16:36.540 align:start position:0% photograph file interface that we have so<00:16:34.259> enhanced<00:16:35.259> graph<00:16:35.439> iql<00:16:36.069> which<00:16:36.339> was<00:16:36.519> a 00:16:36.540 --> 00:16:36.550 align:start position:0% so enhanced graph iql which was a 00:16:36.550 --> 00:16:38.429 align:start position:0% so enhanced graph iql which was a command<00:16:36.879> we<00:16:36.939> passed<00:16:37.240> to<00:16:37.509> who<00:16:37.720> post<00:16:37.959> a<00:16:38.170> file 00:16:38.429 --> 00:16:38.439 align:start position:0% command we passed to who post a file 00:16:38.439 --> 00:16:40.019 align:start position:0% command we passed to who post a file that<00:16:38.680> means<00:16:38.829> the<00:16:39.009> begin<00:16:39.249> a<00:16:39.279> list<00:16:39.519> of<00:16:39.699> like<00:16:39.819> all 00:16:40.019 --> 00:16:40.029 align:start position:0% that means the begin a list of like all 00:16:40.029 --> 00:16:41.519 align:start position:0% that means the begin a list of like all the<00:16:40.149> available<00:16:40.360> queries<00:16:40.870> on<00:16:41.050> the<00:16:41.139> left-hand 00:16:41.519 --> 00:16:41.529 align:start position:0% the available queries on the left-hand 00:16:41.529 --> 00:16:45.299 align:start position:0% the available queries on the left-hand side<00:16:41.649> and<00:16:42.160> then<00:16:43.769> what<00:16:44.769> we've<00:16:44.889> got<00:16:45.069> in<00:16:45.220> the 00:16:45.299 --> 00:16:45.309 align:start position:0% side and then what we've got in the 00:16:45.309 --> 00:16:47.280 align:start position:0% side and then what we've got in the center<00:16:45.610> is<00:16:45.879> you<00:16:46.329> know<00:16:46.420> graphical<00:16:46.959> interface 00:16:47.280 --> 00:16:47.290 align:start position:0% center is you know graphical interface 00:16:47.290 --> 00:16:49.470 align:start position:0% center is you know graphical interface with<00:16:47.589> these<00:16:47.800> queries<00:16:48.309> so<00:16:48.550> I've<00:16:49.209> selected 00:16:49.470 --> 00:16:49.480 align:start position:0% with these queries so I've selected 00:16:49.480 --> 00:16:51.809 align:start position:0% with these queries so I've selected these<00:16:49.990> two<00:16:50.290> ownership<00:16:50.829> transfers<00:16:51.279> events<00:16:51.610> and 00:16:51.809 --> 00:16:51.819 align:start position:0% these two ownership transfers events and 00:16:51.819 --> 00:16:54.569 align:start position:0% these two ownership transfers events and withdrawal<00:16:52.180> events<00:16:53.100> because<00:16:54.100> you<00:16:54.279> can<00:16:54.430> see 00:16:54.569 --> 00:16:54.579 align:start position:0% withdrawal events because you can see 00:16:54.579 --> 00:16:56.549 align:start position:0% withdrawal events because you can see that<00:16:54.850> if<00:16:54.999> I<00:16:55.089> ask<00:16:55.240> for<00:16:55.389> that<00:16:55.509> again<00:16:55.809> you<00:16:55.990> know<00:16:56.110> 23 00:16:56.549 --> 00:16:56.559 align:start position:0% that if I ask for that again you know 23 00:16:56.559 --> 00:16:59.369 align:start position:0% that if I ask for that again you know 23 events<00:16:56.860> and<00:16:57.040> if<00:16:57.730> we<00:16:57.819> pop<00:16:57.999> over<00:16:58.209> to<00:16:58.420> you<00:16:59.290> know 00:16:59.369 --> 00:16:59.379 align:start position:0% events and if we pop over to you know 00:16:59.379 --> 00:17:01.439 align:start position:0% events and if we pop over to you know the<00:16:59.559> main<00:16:59.740> source<00:17:00.009> of<00:17:00.189> truth<00:17:00.399> either<00:17:00.699> scan<00:17:01.029> you 00:17:01.439 --> 00:17:01.449 align:start position:0% the main source of truth either scan you 00:17:01.449 --> 00:17:06.779 align:start position:0% the main source of truth either scan you see<00:17:01.600> the<00:17:03.539> 23<00:17:04.539> events<00:17:04.959> on<00:17:05.169> the<00:17:05.890> full<00:17:06.459> contract 00:17:06.779 --> 00:17:06.789 align:start position:0% see the 23 events on the full contract 00:17:06.789 --> 00:17:10.460 align:start position:0% see the 23 events on the full contract so<00:17:07.390> that's<00:17:08.199> cool<00:17:08.409> that<00:17:08.650> lines<00:17:09.010> up<00:17:09.220> checks<00:17:09.610> out 00:17:10.460 --> 00:17:10.470 align:start position:0% so that's cool that lines up checks out 00:17:10.470 --> 00:17:13.860 align:start position:0% so that's cool that lines up checks out when<00:17:11.470> in<00:17:11.799> these<00:17:12.520> queries<00:17:13.059> we<00:17:13.329> can<00:17:13.539> do<00:17:13.689> some 00:17:13.860 --> 00:17:13.870 align:start position:0% when in these queries we can do some 00:17:13.870 --> 00:17:15.870 align:start position:0% when in these queries we can do some cool<00:17:14.020> stuff<00:17:14.079> so<00:17:14.409> we<00:17:14.679> can<00:17:14.709> say<00:17:14.980> like<00:17:15.220> I<00:17:15.490> want<00:17:15.520> to 00:17:15.870 --> 00:17:15.880 align:start position:0% cool stuff so we can say like I want to 00:17:15.880 --> 00:17:18.240 align:start position:0% cool stuff so we can say like I want to see<00:17:16.059> the<00:17:17.020> nodes<00:17:17.260> and<00:17:17.620> I<00:17:17.679> want<00:17:17.860> to<00:17:17.949> see<00:17:18.069> the 00:17:18.240 --> 00:17:18.250 align:start position:0% see the nodes and I want to see the 00:17:18.250 --> 00:17:20.069 align:start position:0% see the nodes and I want to see the parts<00:17:18.549> like<00:17:18.760> new<00:17:18.939> owner<00:17:19.270> and<00:17:19.390> previous<00:17:19.780> owner 00:17:20.069 --> 00:17:20.079 align:start position:0% parts like new owner and previous owner 00:17:20.079 --> 00:17:22.169 align:start position:0% parts like new owner and previous owner data<00:17:20.319> and<00:17:20.740> then<00:17:21.010> I<00:17:21.039> fire<00:17:21.280> that<00:17:21.520> query<00:17:21.789> and<00:17:22.000> like 00:17:22.169 --> 00:17:22.179 align:start position:0% data and then I fire that query and like 00:17:22.179 --> 00:17:23.669 align:start position:0% data and then I fire that query and like narratives<00:17:22.569> ok<00:17:22.870> ownership<00:17:23.319> was<00:17:23.500> transferred 00:17:23.669 --> 00:17:23.679 align:start position:0% narratives ok ownership was transferred 00:17:23.679 --> 00:17:26.880 align:start position:0% narratives ok ownership was transferred from<00:17:23.919> dress<00:17:25.079> and<00:17:26.079> I<00:17:26.169> can<00:17:26.319> do<00:17:26.409> the<00:17:26.470> same<00:17:26.620> thing 00:17:26.880 --> 00:17:26.890 align:start position:0% from dress and I can do the same thing 00:17:26.890 --> 00:17:30.750 align:start position:0% from dress and I can do the same thing with<00:17:27.520> withdrawal<00:17:28.150> events<00:17:28.710> I<00:17:29.710> want<00:17:30.370> to<00:17:30.490> see<00:17:30.610> the 00:17:30.750 --> 00:17:30.760 align:start position:0% with withdrawal events I want to see the 00:17:30.760 --> 00:17:33.990 align:start position:0% with withdrawal events I want to see the American<00:17:31.270> policy<00:17:31.390> receiver<00:17:32.140> and<00:17:32.730> cool<00:17:33.730> you 00:17:33.990 --> 00:17:34.000 align:start position:0% American policy receiver and cool you 00:17:34.000 --> 00:17:35.039 align:start position:0% American policy receiver and cool you know<00:17:34.120> these<00:17:34.299> are<00:17:34.419> mounts<00:17:34.630> are<00:17:34.750> weird<00:17:34.929> because 00:17:35.039 --> 00:17:35.049 align:start position:0% know these are mounts are weird because 00:17:35.049 --> 00:17:37.260 align:start position:0% know these are mounts are weird because it's<00:17:35.350> like<00:17:35.409> the<00:17:35.649> p.m.<00:17:35.980> but<00:17:36.220> there's<00:17:36.490> a<00:17:36.549> fixed 00:17:37.260 --> 00:17:37.270 align:start position:0% it's like the p.m. but there's a fixed 00:17:37.270 --> 00:17:39.680 align:start position:0% it's like the p.m. but there's a fixed value<00:17:37.390> and<00:17:37.870> divide<00:17:38.470> that<00:17:38.649> by<00:17:38.710> to<00:17:39.220> get 00:17:39.680 --> 00:17:39.690 align:start position:0% value and divide that by to get 00:17:39.690 --> 00:17:42.779 align:start position:0% value and divide that by to get something<00:17:40.690> that's<00:17:40.870> a<00:17:41.110> little<00:17:41.230> bit<00:17:41.350> more<00:17:41.789> easy 00:17:42.779 --> 00:17:42.789 align:start position:0% something that's a little bit more easy 00:17:42.789 --> 00:17:45.990 align:start position:0% something that's a little bit more easy to<00:17:42.970> parse<00:17:43.210> an<00:17:44.200> easier<00:17:44.770> event<00:17:45.039> to<00:17:45.190> look<00:17:45.340> at<00:17:45.549> for 00:17:45.990 --> 00:17:46.000 align:start position:0% to parse an easier event to look at for 00:17:46.000 --> 00:17:47.760 align:start position:0% to parse an easier event to look at for understanding<00:17:46.780> this<00:17:46.899> would<00:17:47.110> be<00:17:47.230> the<00:17:47.350> ragequit 00:17:47.760 --> 00:17:47.770 align:start position:0% understanding this would be the ragequit 00:17:47.770 --> 00:17:49.110 align:start position:0% understanding this would be the ragequit event<00:17:48.010> because<00:17:48.340> they're<00:17:48.490> dealing<00:17:48.610> with<00:17:48.789> share 00:17:49.110 --> 00:17:49.120 align:start position:0% event because they're dealing with share 00:17:49.120 --> 00:17:51.930 align:start position:0% event because they're dealing with share spreads<00:17:49.630> opposed<00:17:49.899> to<00:17:50.200> a<00:17:50.340> monetary<00:17:51.340> value<00:17:51.460> and 00:17:51.930 --> 00:17:51.940 align:start position:0% spreads opposed to a monetary value and 00:17:51.940 --> 00:17:52.240 align:start position:0% spreads opposed to a monetary value and so 00:17:52.240 --> 00:17:52.250 align:start position:0% so 00:17:52.250 --> 00:17:54.610 align:start position:0% so want<00:17:52.460> to<00:17:52.550> see<00:17:52.750> shares<00:17:53.750> to<00:17:54.020> learn<00:17:54.200> and<00:17:54.560> the 00:17:54.610 --> 00:17:54.620 align:start position:0% want to see shares to learn and the 00:17:54.620 --> 00:17:56.410 align:start position:0% want to see shares to learn and the member<00:17:54.890> address<00:17:55.190> for<00:17:55.460> the<00:17:55.580> rage<00:17:55.760> quit<00:17:56.030> events 00:17:56.410 --> 00:17:56.420 align:start position:0% member address for the rage quit events 00:17:56.420 --> 00:17:57.940 align:start position:0% member address for the rage quit events on<00:17:56.540> the<00:17:56.630> block<00:17:56.960> contract<00:17:57.530> that<00:17:57.710> at<00:17:57.800> Lake 00:17:57.940 --> 00:17:57.950 align:start position:0% on the block contract that at Lake 00:17:57.950 --> 00:18:01.840 align:start position:0% on the block contract that at Lake occasions<00:17:58.460> are<00:17:58.550> pretty<00:17:58.700> nice<00:17:58.820> numbers<00:17:59.240> and<00:18:00.850> we 00:18:01.840 --> 00:18:01.850 align:start position:0% occasions are pretty nice numbers and we 00:18:01.850 --> 00:18:04.120 align:start position:0% occasions are pretty nice numbers and we can<00:18:01.880> see<00:18:02.210> here<00:18:02.570> we've<00:18:03.170> got<00:18:03.380> like<00:18:03.680> ninety<00:18:03.980> nine 00:18:04.120 --> 00:18:04.130 align:start position:0% can see here we've got like ninety nine 00:18:04.130 --> 00:18:06.940 align:start position:0% can see here we've got like ninety nine chairs<00:18:04.490> break<00:18:04.930> we<00:18:05.930> pop<00:18:06.140> over<00:18:06.380> the<00:18:06.590> Mohawk 00:18:06.940 --> 00:18:06.950 align:start position:0% chairs break we pop over the Mohawk 00:18:06.950 --> 00:18:09.850 align:start position:0% chairs break we pop over the Mohawk contract<00:18:07.580> on<00:18:07.850> ether<00:18:08.750> stand<00:18:09.050> is<00:18:09.320> he<00:18:09.470> like<00:18:09.650> not 00:18:09.850 --> 00:18:09.860 align:start position:0% contract on ether stand is he like not 00:18:09.860 --> 00:18:12.670 align:start position:0% contract on ether stand is he like not interesting<00:18:10.340> here's<00:18:10.880> that<00:18:11.060> same<00:18:11.360> address<00:18:11.680> in 00:18:12.670 --> 00:18:12.680 align:start position:0% interesting here's that same address in 00:18:12.680 --> 00:18:15.730 align:start position:0% interesting here's that same address in topic<00:18:13.160> 1<00:18:13.190> you<00:18:13.700> know<00:18:13.820> it's<00:18:13.970> a<00:18:14.060> habit<00:18:14.960> hex<00:18:15.320> value 00:18:15.730 --> 00:18:15.740 align:start position:0% topic 1 you know it's a habit hex value 00:18:15.740 --> 00:18:18.370 align:start position:0% topic 1 you know it's a habit hex value and<00:18:16.520> we<00:18:16.730> do<00:18:16.880> put<00:18:17.030> this<00:18:17.270> number<00:18:17.570> it's<00:18:17.870> like<00:18:18.020> 99 00:18:18.370 --> 00:18:18.380 align:start position:0% and we do put this number it's like 99 00:18:18.380 --> 00:18:22.690 align:start position:0% and we do put this number it's like 99 this<00:18:19.190> event<00:18:19.490> was<00:18:19.730> dead<00:18:19.880> empty<00:18:20.530> so<00:18:21.530> okay<00:18:22.340> you 00:18:22.690 --> 00:18:22.700 align:start position:0% this event was dead empty so okay you 00:18:22.700 --> 00:18:24.460 align:start position:0% this event was dead empty so okay you know<00:18:22.820> you're<00:18:22.940> just<00:18:23.000> getting<00:18:23.470> like 00:18:24.460 --> 00:18:24.470 align:start position:0% know you're just getting like 00:18:24.470 --> 00:18:27.610 align:start position:0% know you're just getting like automatically<00:18:25.190> decoded<00:18:25.640> events<00:18:26.000> I<00:18:26.570> had<00:18:27.320> you 00:18:27.610 --> 00:18:27.620 align:start position:0% automatically decoded events I had you 00:18:27.620 --> 00:18:30.100 align:start position:0% automatically decoded events I had you know<00:18:27.710> I<00:18:27.740> can<00:18:28.130> walk<00:18:28.310> through<00:18:28.550> all<00:18:29.150> the<00:18:29.570> queries 00:18:30.100 --> 00:18:30.110 align:start position:0% know I can walk through all the queries 00:18:30.110 --> 00:18:33.700 align:start position:0% know I can walk through all the queries but<00:18:30.380> I<00:18:30.680> think<00:18:31.250> folks<00:18:31.520> get<00:18:31.850> an<00:18:32.750> idea<00:18:33.110> of<00:18:33.410> what 00:18:33.700 --> 00:18:33.710 align:start position:0% but I think folks get an idea of what 00:18:33.710 --> 00:18:35.560 align:start position:0% but I think folks get an idea of what we're<00:18:33.860> doing<00:18:33.950> right<00:18:34.340> here<00:18:34.790> are<00:18:35.090> automatically 00:18:35.560 --> 00:18:35.570 align:start position:0% we're doing right here are automatically 00:18:35.570 --> 00:18:38.290 align:start position:0% we're doing right here are automatically getting<00:18:35.870> all<00:18:36.560> these<00:18:36.770> events<00:18:37.010> parts<00:18:37.730> into 00:18:38.290 --> 00:18:38.300 align:start position:0% getting all these events parts into 00:18:38.300 --> 00:18:53.230 align:start position:0% getting all these events parts into Postgres<00:18:38.780> with<00:18:39.560> recant<00:18:50.650> so<00:18:51.650> you<00:18:52.580> know<00:18:52.670> the 00:18:53.230 --> 00:18:53.240 align:start position:0% Postgres with recant so you know the 00:18:53.240 --> 00:18:55.540 align:start position:0% Postgres with recant so you know the workshop<00:18:53.600> was<00:18:53.780> like<00:18:53.990> first<00:18:54.410> you<00:18:54.800> can<00:18:54.980> run<00:18:55.220> this 00:18:55.540 --> 00:18:55.550 align:start position:0% workshop was like first you can run this 00:18:55.550 --> 00:18:58.120 align:start position:0% workshop was like first you can run this doctor<00:18:56.360> compose<00:18:56.780> that<00:18:57.320> will<00:18:57.530> enable<00:18:57.740> you<00:18:58.070> to 00:18:58.120 --> 00:18:58.130 align:start position:0% doctor compose that will enable you to 00:18:58.130 --> 00:19:00.430 align:start position:0% doctor compose that will enable you to like<00:18:58.430> reproduce<00:18:59.030> exactly<00:18:59.360> what<00:18:59.930> I<00:18:59.960> just<00:19:00.020> demo 00:19:00.430 --> 00:19:00.440 align:start position:0% like reproduce exactly what I just demo 00:19:00.440 --> 00:19:03.970 align:start position:0% like reproduce exactly what I just demo I<00:19:00.980> did<00:19:01.280> want<00:19:01.850> to<00:19:01.880> mention<00:19:02.000> that<00:19:02.270> that<00:19:03.080> they 00:19:03.970 --> 00:19:03.980 align:start position:0% I did want to mention that that they 00:19:03.980 --> 00:19:06.640 align:start position:0% I did want to mention that that they would<00:19:04.160> I<00:19:04.250> demoed<00:19:04.460> that<00:19:04.960> database<00:19:05.960> ends<00:19:06.530> up 00:19:06.640 --> 00:19:06.650 align:start position:0% would I demoed that database ends up 00:19:06.650 --> 00:19:09.370 align:start position:0% would I demoed that database ends up being<00:19:06.860> about<00:19:07.130> three<00:19:07.550> gigs<00:19:07.880> that<00:19:08.270> also<00:19:08.810> took<00:19:08.990> me 00:19:09.370 --> 00:19:09.380 align:start position:0% being about three gigs that also took me 00:19:09.380 --> 00:19:11.710 align:start position:0% being about three gigs that also took me about<00:19:09.620> 30<00:19:09.980> hours<00:19:10.070> to<00:19:10.460> sync<00:19:10.820> on<00:19:10.970> my<00:19:11.120> own<00:19:11.300> Wi-Fi 00:19:11.710 --> 00:19:11.720 align:start position:0% about 30 hours to sync on my own Wi-Fi 00:19:11.720 --> 00:19:14.890 align:start position:0% about 30 hours to sync on my own Wi-Fi so<00:19:12.310> continue<00:19:13.310> to<00:19:13.370> work<00:19:13.550> on<00:19:13.730> performance<00:19:14.090> that 00:19:14.890 --> 00:19:14.900 align:start position:0% so continue to work on performance that 00:19:14.900 --> 00:19:17.020 align:start position:0% so continue to work on performance that cost<00:19:15.140> is<00:19:15.350> amortized<00:19:15.980> over<00:19:16.310> the<00:19:16.460> life<00:19:16.550> of<00:19:16.850> your 00:19:17.020 --> 00:19:17.030 align:start position:0% cost is amortized over the life of your 00:19:17.030 --> 00:19:18.640 align:start position:0% cost is amortized over the life of your system<00:19:17.420> right<00:19:17.840> so<00:19:18.020> you<00:19:18.110> might<00:19:18.170> have<00:19:18.440> like<00:19:18.620> a 00:19:18.640 --> 00:19:18.650 align:start position:0% system right so you might have like a 00:19:18.650 --> 00:19:21.190 align:start position:0% system right so you might have like a high<00:19:18.860> upfront<00:19:19.040> costs<00:19:19.670> to<00:19:19.820> get<00:19:19.940> totally<00:19:20.900> sync 00:19:21.190 --> 00:19:21.200 align:start position:0% high upfront costs to get totally sync 00:19:21.200 --> 00:19:22.300 align:start position:0% high upfront costs to get totally sync with<00:19:21.440> all<00:19:21.650> the<00:19:21.800> events<00:19:22.070> that<00:19:22.190> have<00:19:22.280> happened 00:19:22.300 --> 00:19:22.310 align:start position:0% with all the events that have happened 00:19:22.310 --> 00:19:24.280 align:start position:0% with all the events that have happened throughout<00:19:22.790> history<00:19:23.120> but<00:19:23.540> then<00:19:23.990> you're<00:19:24.140> going 00:19:24.280 --> 00:19:24.290 align:start position:0% throughout history but then you're going 00:19:24.290 --> 00:19:26.200 align:start position:0% throughout history but then you're going to<00:19:24.350> stay<00:19:24.710> in<00:19:25.100> sync<00:19:25.340> it's<00:19:25.580> running<00:19:25.940> the<00:19:26.000> process 00:19:26.200 --> 00:19:26.210 align:start position:0% to stay in sync it's running the process 00:19:26.210 --> 00:19:28.950 align:start position:0% to stay in sync it's running the process continually<00:19:26.960> not<00:19:27.470> going<00:19:27.620> to<00:19:27.680> fall<00:19:27.830> behind<00:19:27.950> and 00:19:28.950 --> 00:19:28.960 align:start position:0% continually not going to fall behind and 00:19:28.960 --> 00:19:31.930 align:start position:0% continually not going to fall behind and and<00:19:29.960> yet<00:19:30.650> that<00:19:30.770> costed<00:19:31.130> amortize<00:19:31.550> which<00:19:31.790> is 00:19:31.930 --> 00:19:31.940 align:start position:0% and yet that costed amortize which is 00:19:31.940 --> 00:19:36.280 align:start position:0% and yet that costed amortize which is built<00:19:32.350> but<00:19:34.450> what<00:19:35.450> that<00:19:35.630> means<00:19:35.780> is<00:19:36.050> that<00:19:36.080> you 00:19:36.280 --> 00:19:36.290 align:start position:0% built but what that means is that you 00:19:36.290 --> 00:19:37.990 align:start position:0% built but what that means is that you know<00:19:36.380> you<00:19:36.440> start<00:19:36.830> seeing<00:19:37.070> events<00:19:37.520> immediately 00:19:37.990 --> 00:19:38.000 align:start position:0% know you start seeing events immediately 00:19:38.000 --> 00:19:40.270 align:start position:0% know you start seeing events immediately for<00:19:38.750> things<00:19:38.990> that<00:19:39.140> happened<00:19:39.500> early<00:19:39.830> on<00:19:39.860> and 00:19:40.270 --> 00:19:40.280 align:start position:0% for things that happened early on and 00:19:40.280 --> 00:19:40.810 align:start position:0% for things that happened early on and the<00:19:40.340> history 00:19:40.810 --> 00:19:40.820 align:start position:0% the history 00:19:40.820 --> 00:19:42.700 align:start position:0% the history contracts<00:19:41.419> but<00:19:41.659> you<00:19:41.720> wouldn't<00:19:42.019> a<00:19:42.080> latest<00:19:42.559> one 00:19:42.700 --> 00:19:42.710 align:start position:0% contracts but you wouldn't a latest one 00:19:42.710 --> 00:19:44.759 align:start position:0% contracts but you wouldn't a latest one can<00:19:42.889> sell<00:19:43.009> your<00:19:43.100> system<00:19:43.399> and<00:19:43.519> finish<00:19:43.700> thinking 00:19:44.759 --> 00:19:44.769 align:start position:0% can sell your system and finish thinking 00:19:44.769 --> 00:19:47.889 align:start position:0% can sell your system and finish thinking but<00:19:45.769> if<00:19:46.039> you<00:19:46.340> wanted<00:19:46.639> to<00:19:46.700> check<00:19:47.509> out<00:19:47.690> some 00:19:47.889 --> 00:19:47.899 align:start position:0% but if you wanted to check out some 00:19:47.899 --> 00:19:49.990 align:start position:0% but if you wanted to check out some other<00:19:47.960> stuff<00:19:48.320> you<00:19:48.769> could<00:19:49.009> write<00:19:49.759> your<00:19:49.940> own 00:19:49.990 --> 00:19:50.000 align:start position:0% other stuff you could write your own 00:19:50.000 --> 00:19:52.419 align:start position:0% other stuff you could write your own config<00:19:50.450> file<00:19:50.659> right<00:19:51.110> so<00:19:51.380> that<00:19:51.649> was<00:19:51.799> 20<00:19:52.220> lines 00:19:52.419 --> 00:19:52.429 align:start position:0% config file right so that was 20 lines 00:19:52.429 --> 00:19:54.159 align:start position:0% config file right so that was 20 lines to<00:19:52.669> get<00:19:52.880> three<00:19:53.090> contracts<00:19:53.539> you<00:19:53.840> could<00:19:53.960> look<00:19:54.049> at 00:19:54.159 --> 00:19:54.169 align:start position:0% to get three contracts you could look at 00:19:54.169 --> 00:19:57.490 align:start position:0% to get three contracts you could look at 17<00:19:54.590> contracts<00:19:55.009> for<00:19:55.399> lines<00:19:55.639> that's<00:19:56.299> up<00:19:56.450> to<00:19:56.570> you 00:19:57.490 --> 00:19:57.500 align:start position:0% 17 contracts for lines that's up to you 00:19:57.500 --> 00:19:59.620 align:start position:0% 17 contracts for lines that's up to you you<00:19:58.130> could<00:19:58.309> you<00:19:58.820> could<00:19:58.850> run<00:19:59.179> it<00:19:59.299> with<00:19:59.480> an 00:19:59.620 --> 00:19:59.630 align:start position:0% you could you could run it with an 00:19:59.630 --> 00:20:01.570 align:start position:0% you could you could run it with an address<00:19:59.870> where<00:20:00.230> the<00:20:00.320> API<00:20:00.620> is<00:20:00.740> not<00:20:01.130> published 00:20:01.570 --> 00:20:01.580 align:start position:0% address where the API is not published 00:20:01.580 --> 00:20:03.669 align:start position:0% address where the API is not published on<00:20:01.759> ether<00:20:02.090> scan<00:20:02.330> right<00:20:02.720> -<00:20:02.929> there's<00:20:03.110> an<00:20:03.230> option 00:20:03.669 --> 00:20:03.679 align:start position:0% on ether scan right - there's an option 00:20:03.679 --> 00:20:06.669 align:start position:0% on ether scan right - there's an option to<00:20:03.919> supply<00:20:04.759> the<00:20:04.820> API<00:20:05.450> and<00:20:05.840> that<00:20:06.019> config<00:20:06.470> file 00:20:06.669 --> 00:20:06.679 align:start position:0% to supply the API and that config file 00:20:06.679 --> 00:20:08.169 align:start position:0% to supply the API and that config file for<00:20:06.950> the<00:20:07.009> contract<00:20:07.460> if<00:20:07.610> you're<00:20:07.759> not<00:20:07.909> dealing 00:20:08.169 --> 00:20:08.179 align:start position:0% for the contract if you're not dealing 00:20:08.179 --> 00:20:11.139 align:start position:0% for the contract if you're not dealing with<00:20:08.330> you<00:20:09.049> know<00:20:09.080> verified<00:20:09.559> source<00:20:09.889> code<00:20:10.159> so 00:20:11.139 --> 00:20:11.149 align:start position:0% with you know verified source code so 00:20:11.149 --> 00:20:12.759 align:start position:0% with you know verified source code so it's<00:20:11.450> not<00:20:11.570> a<00:20:11.630> constraint<00:20:12.169> for<00:20:12.350> the<00:20:12.440> system 00:20:12.759 --> 00:20:12.769 align:start position:0% it's not a constraint for the system 00:20:12.769 --> 00:20:14.590 align:start position:0% it's not a constraint for the system that<00:20:12.919> the<00:20:13.009> API<00:20:13.279> have<00:20:13.490> to<00:20:13.669> exist<00:20:13.940> on<00:20:14.029> understand 00:20:14.590 --> 00:20:14.600 align:start position:0% that the API have to exist on understand 00:20:14.600 --> 00:20:16.690 align:start position:0% that the API have to exist on understand but<00:20:14.840> that<00:20:15.129> minimizes<00:20:16.129> the<00:20:16.250> amount<00:20:16.309> you<00:20:16.549> have 00:20:16.690 --> 00:20:16.700 align:start position:0% but that minimizes the amount you have 00:20:16.700 --> 00:20:19.389 align:start position:0% but that minimizes the amount you have to<00:20:16.850> including<00:20:17.269> to<00:20:17.419> think<00:20:17.919> and<00:20:18.919> if<00:20:19.039> you<00:20:19.159> wanted 00:20:19.389 --> 00:20:19.399 align:start position:0% to including to think and if you wanted 00:20:19.399 --> 00:20:21.039 align:start position:0% to including to think and if you wanted to<00:20:19.460> run<00:20:19.669> it<00:20:19.789> locally<00:20:19.909> like<00:20:20.360> not<00:20:20.570> in<00:20:20.809> docker 00:20:21.039 --> 00:20:21.049 align:start position:0% to run it locally like not in docker 00:20:21.049 --> 00:20:22.869 align:start position:0% to run it locally like not in docker then<00:20:21.409> you<00:20:21.529> can<00:20:21.710> you<00:20:22.100> know<00:20:22.129> do<00:20:22.549> a<00:20:22.580> few<00:20:22.850> things 00:20:22.869 --> 00:20:22.879 align:start position:0% then you can you know do a few things 00:20:22.879 --> 00:20:24.940 align:start position:0% then you can you know do a few things that<00:20:23.330> we<00:20:23.450> have<00:20:23.690> hidden<00:20:24.110> for<00:20:24.500> you<00:20:24.649> in<00:20:24.860> our 00:20:24.940 --> 00:20:24.950 align:start position:0% that we have hidden for you in our 00:20:24.950 --> 00:20:26.560 align:start position:0% that we have hidden for you in our compose<00:20:25.340> script<00:20:25.730> right<00:20:25.970> so<00:20:26.090> you<00:20:26.210> have<00:20:26.299> to<00:20:26.450> like 00:20:26.560 --> 00:20:26.570 align:start position:0% compose script right so you have to like 00:20:26.570 --> 00:20:28.090 align:start position:0% compose script right so you have to like create<00:20:26.840> a<00:20:26.870> database<00:20:27.200> of<00:20:27.500> all<00:20:27.620> guys<00:20:27.860> can 00:20:28.090 --> 00:20:28.100 align:start position:0% create a database of all guys can 00:20:28.100 --> 00:20:30.820 align:start position:0% create a database of all guys can connect<00:20:28.370> to<00:20:28.570> we<00:20:29.570> use<00:20:29.720> go<00:20:29.899> modules<00:20:30.440> so<00:20:30.590> you<00:20:30.649> have 00:20:30.820 --> 00:20:30.830 align:start position:0% connect to we use go modules so you have 00:20:30.830 --> 00:20:32.860 align:start position:0% connect to we use go modules so you have to<00:20:30.950> turn<00:20:31.100> that<00:20:31.340> on<00:20:31.549> to<00:20:32.179> enable<00:20:32.480> it<00:20:32.570> to<00:20:32.600> bill 00:20:32.860 --> 00:20:32.870 align:start position:0% to turn that on to enable it to bill 00:20:32.870 --> 00:20:34.299 align:start position:0% to turn that on to enable it to bill your<00:20:33.080> bill<00:20:33.320> to<00:20:33.470> end<00:20:33.649> up<00:20:33.799> with<00:20:33.889> your<00:20:34.039> vulcanize 00:20:34.299 --> 00:20:34.309 align:start position:0% your bill to end up with your vulcanize 00:20:34.309 --> 00:20:37.299 align:start position:0% your bill to end up with your vulcanize DB<00:20:34.850> binary<00:20:35.330> and<00:20:35.809> you<00:20:36.259> should<00:20:36.470> be<00:20:36.590> able<00:20:36.679> to<00:20:36.860> run 00:20:37.299 --> 00:20:37.309 align:start position:0% DB binary and you should be able to run 00:20:37.309 --> 00:20:41.080 align:start position:0% DB binary and you should be able to run these<00:20:37.490> things<00:20:37.700> locally<00:20:38.289> and<00:20:39.289> then<00:20:39.700> if<00:20:40.700> folks 00:20:41.080 --> 00:20:41.090 align:start position:0% these things locally and then if folks 00:20:41.090 --> 00:20:43.360 align:start position:0% these things locally and then if folks were<00:20:41.360> able<00:20:41.419> to<00:20:41.750> you<00:20:42.470> know<00:20:42.590> be<00:20:42.620> like<00:20:42.860> okay<00:20:43.159> I<00:20:43.190> did 00:20:43.360 --> 00:20:43.370 align:start position:0% were able to you know be like okay I did 00:20:43.370 --> 00:20:45.549 align:start position:0% were able to you know be like okay I did this<00:20:43.399> award<00:20:44.059> and<00:20:44.389> I<00:20:44.450> like<00:20:44.629> made<00:20:44.840> my<00:20:44.990> own<00:20:45.019> config 00:20:45.549 --> 00:20:45.559 align:start position:0% this award and I like made my own config 00:20:45.559 --> 00:20:47.680 align:start position:0% this award and I like made my own config look<00:20:45.769> with<00:20:46.159> contracts<00:20:46.580> board<00:20:46.940> again<00:20:47.179> I'm 00:20:47.680 --> 00:20:47.690 align:start position:0% look with contracts board again I'm 00:20:47.690 --> 00:20:48.879 align:start position:0% look with contracts board again I'm running<00:20:47.929> it<00:20:48.019> locally<00:20:48.110> on<00:20:48.320> my<00:20:48.409> machine<00:20:48.500> you 00:20:48.879 --> 00:20:48.889 align:start position:0% running it locally on my machine you 00:20:48.889 --> 00:20:51.460 align:start position:0% running it locally on my machine you know<00:20:48.980> I'm<00:20:49.039> still<00:20:49.279> bored<00:20:49.490> then<00:20:50.059> like<00:20:50.779> option<00:20:51.230> 3 00:20:51.460 --> 00:20:51.470 align:start position:0% know I'm still bored then like option 3 00:20:51.470 --> 00:20:52.779 align:start position:0% know I'm still bored then like option 3 that<00:20:51.889> I<00:20:51.919> thought<00:20:52.100> would<00:20:52.190> really<00:20:52.279> take<00:20:52.639> up 00:20:52.779 --> 00:20:52.789 align:start position:0% that I thought would really take up 00:20:52.789 --> 00:20:55.180 align:start position:0% that I thought would really take up everyone's<00:20:53.149> time<00:20:53.360> would<00:20:53.990> be<00:20:54.110> okay<00:20:54.500> let's 00:20:55.180 --> 00:20:55.190 align:start position:0% everyone's time would be okay let's 00:20:55.190 --> 00:20:56.919 align:start position:0% everyone's time would be okay let's start<00:20:55.370> building<00:20:55.490> around<00:20:55.789> plugins<00:20:56.299> right<00:20:56.629> so 00:20:56.919 --> 00:20:56.929 align:start position:0% start building around plugins right so 00:20:56.929 --> 00:21:00.310 align:start position:0% start building around plugins right so all<00:20:57.289> the<00:20:57.769> plug-in<00:20:58.009> architecture<00:20:58.539> is<00:20:59.539> in<00:20:59.779> the 00:21:00.310 --> 00:21:00.320 align:start position:0% all the plug-in architecture is in the 00:21:00.320 --> 00:21:02.950 align:start position:0% all the plug-in architecture is in the libraries<00:21:00.889> shared<00:21:01.220> folder<00:21:01.700> baulkham<00:21:02.600> as<00:21:02.720> d-v 00:21:02.950 --> 00:21:02.960 align:start position:0% libraries shared folder baulkham as d-v 00:21:02.960 --> 00:21:05.019 align:start position:0% libraries shared folder baulkham as d-v and<00:21:03.379> specifically<00:21:04.100> in<00:21:04.309> the<00:21:04.460> factories 00:21:05.019 --> 00:21:05.029 align:start position:0% and specifically in the factories 00:21:05.029 --> 00:21:08.460 align:start position:0% and specifically in the factories directory<00:21:05.539> you<00:21:06.259> can<00:21:06.289> see<00:21:06.879> we've<00:21:07.879> abstracted 00:21:08.460 --> 00:21:08.470 align:start position:0% directory you can see we've abstracted 00:21:08.470 --> 00:21:11.799 align:start position:0% directory you can see we've abstracted code<00:21:09.470> that'll<00:21:10.039> handle<00:21:10.250> like<00:21:10.669> the<00:21:10.909> overarching 00:21:11.799 --> 00:21:11.809 align:start position:0% code that'll handle like the overarching 00:21:11.809 --> 00:21:14.289 align:start position:0% code that'll handle like the overarching process<00:21:12.289> of<00:21:12.860> syncing<00:21:13.370> anonymous<00:21:13.789> aventure 00:21:14.289 --> 00:21:14.299 align:start position:0% process of syncing anonymous aventure 00:21:14.299 --> 00:21:16.029 align:start position:0% process of syncing anonymous aventure sickening<00:21:14.690> storage<00:21:15.019> tips<00:21:15.259> that<00:21:15.470> you<00:21:15.590> have<00:21:15.620> to 00:21:16.029 --> 00:21:16.039 align:start position:0% sickening storage tips that you have to 00:21:16.039 --> 00:21:17.950 align:start position:0% sickening storage tips that you have to write<00:21:16.220> like<00:21:16.429> a<00:21:16.490> few<00:21:16.879> small<00:21:17.090> dependencies 00:21:17.950 --> 00:21:17.960 align:start position:0% write like a few small dependencies 00:21:17.960 --> 00:21:20.049 align:start position:0% write like a few small dependencies basically<00:21:18.200> tell<00:21:18.499> us<00:21:18.649> like<00:21:18.860> okay<00:21:19.639> you've<00:21:19.820> given 00:21:20.049 --> 00:21:20.059 align:start position:0% basically tell us like okay you've given 00:21:20.059 --> 00:21:22.269 align:start position:0% basically tell us like okay you've given me<00:21:20.119> an<00:21:20.210> ominous<00:21:20.480> event<00:21:20.809> like<00:21:21.320> how<00:21:22.009> does<00:21:22.190> it 00:21:22.269 --> 00:21:22.279 align:start position:0% me an ominous event like how does it 00:21:22.279 --> 00:21:24.249 align:start position:0% me an ominous event like how does it become<00:21:22.850> why<00:21:23.059> like<00:21:23.600> something<00:21:23.899> that<00:21:23.929> you<00:21:24.110> put 00:21:24.249 --> 00:21:24.259 align:start position:0% become why like something that you put 00:21:24.259 --> 00:21:28.389 align:start position:0% become why like something that you put the<00:21:24.409> database<00:21:25.600> but<00:21:26.600> yeah<00:21:27.409> and<00:21:27.590> you<00:21:28.159> know<00:21:28.249> how 00:21:28.389 --> 00:21:28.399 align:start position:0% the database but yeah and you know how 00:21:28.399 --> 00:21:30.489 align:start position:0% the database but yeah and you know how I'll<00:21:28.970> stick<00:21:29.269> around<00:21:29.419> after<00:21:29.929> this<00:21:30.049> time<00:21:30.289> I 00:21:30.489 --> 00:21:30.499 align:start position:0% I'll stick around after this time I 00:21:30.499 --> 00:21:33.100 align:start position:0% I'll stick around after this time I would<00:21:30.649> love<00:21:31.039> for<00:21:31.100> people<00:21:31.399> to<00:21:31.789> to<00:21:32.539> give<00:21:32.720> this<00:21:32.899> go 00:21:33.100 --> 00:21:33.110 align:start position:0% would love for people to to give this go 00:21:33.110 --> 00:21:37.389 align:start position:0% would love for people to to give this go we<00:21:33.320> can<00:21:33.999> but<00:21:35.440> there<00:21:36.440> we<00:21:36.590> are 00:21:37.389 --> 00:21:37.399 align:start position:0% we can but there we are 00:21:37.399 --> 00:21:40.720 align:start position:0% we can but there we are so<00:21:37.970> I<00:21:38.210> want<00:21:38.809> to<00:21:38.840> say<00:21:39.049> thank<00:21:39.350> you<00:21:39.409> I<00:21:39.769> definitely 00:21:40.720 --> 00:21:40.730 align:start position:0% so I want to say thank you I definitely 00:21:40.730 --> 00:21:42.369 align:start position:0% so I want to say thank you I definitely have<00:21:40.909> not<00:21:41.059> done<00:21:41.269> this<00:21:41.389> by<00:21:41.570> myself<00:21:41.749> thank<00:21:42.230> you 00:21:42.369 --> 00:21:42.379 align:start position:0% have not done this by myself thank you 00:21:42.379 --> 00:21:44.859 align:start position:0% have not done this by myself thank you know<00:21:42.649> how<00:21:42.799> to<00:21:42.860> uh<00:21:43.269> privilege<00:21:44.269> to<00:21:44.480> speak<00:21:44.690> up 00:21:44.859 --> 00:21:44.869 align:start position:0% know how to uh privilege to speak up 00:21:44.869 --> 00:21:48.159 align:start position:0% know how to uh privilege to speak up here<00:21:45.110> but<00:21:45.529> Rick<00:21:46.159> Dudley<00:21:46.610> Elizabeth<00:21:47.360> Andy<00:21:47.869> gave 00:21:48.159 --> 00:21:48.169 align:start position:0% here but Rick Dudley Elizabeth Andy gave 00:21:48.169 --> 00:21:50.499 align:start position:0% here but Rick Dudley Elizabeth Andy gave Edwardian<00:21:49.100> Connor<00:21:49.460> Gustav<00:21:50.029> have<00:21:50.210> all<00:21:50.330> been 00:21:50.499 --> 00:21:50.509 align:start position:0% Edwardian Connor Gustav have all been 00:21:50.509 --> 00:21:53.139 align:start position:0% Edwardian Connor Gustav have all been super<00:21:50.929> instrumental<00:21:51.409> to<00:21:51.799> getting<00:21:52.399> this 00:21:53.139 --> 00:21:53.149 align:start position:0% super instrumental to getting this 00:21:53.149 --> 00:21:54.570 align:start position:0% super instrumental to getting this project<00:21:53.389> to<00:21:53.779> where<00:21:53.899> it<00:21:53.990> is<00:21:54.049> today 00:21:54.570 --> 00:21:54.580 align:start position:0% project to where it is today 00:21:54.580 --> 00:21:58.269 align:start position:0% project to where it is today we<00:21:55.580> support<00:21:56.389> Pina<00:21:56.629> Pina<00:21:56.869> foundation<00:21:57.590> for<00:21:57.919> kids 00:21:58.269 --> 00:21:58.279 align:start position:0% we support Pina Pina foundation for kids 00:21:58.279 --> 00:22:00.460 align:start position:0% we support Pina Pina foundation for kids were<00:21:58.519> tremendously<00:21:58.999> grateful<00:21:59.299> and<00:22:00.110> also<00:22:00.379> go 00:22:00.460 --> 00:22:00.470 align:start position:0% were tremendously grateful and also go 00:22:00.470 --> 00:22:03.220 align:start position:0% were tremendously grateful and also go for<00:22:00.649> maker<00:22:00.860> down<00:22:01.100> so<00:22:01.490> thank<00:22:02.450> you<00:22:02.570> so<00:22:02.600> much<00:22:02.779> to 00:22:03.220 --> 00:22:03.230 align:start position:0% for maker down so thank you so much to 00:22:03.230 --> 00:22:05.350 align:start position:0% for maker down so thank you so much to those<00:22:03.470> folks<00:22:03.830> we're<00:22:04.519> supporting<00:22:04.759> our<00:22:04.999> effort 00:22:05.350 --> 00:22:05.360 align:start position:0% those folks we're supporting our effort 00:22:05.360 --> 00:22:08.289 align:start position:0% those folks we're supporting our effort we're<00:22:05.659> really<00:22:05.869> excited<00:22:06.200> about<00:22:06.879> hopefully<00:22:07.879> a 00:22:08.289 --> 00:22:08.299 align:start position:0% we're really excited about hopefully a 00:22:08.299 --> 00:22:09.999 align:start position:0% we're really excited about hopefully a lot<00:22:08.809> of<00:22:08.869> value<00:22:09.200> can<00:22:09.409> be<00:22:09.440> delivered<00:22:09.860> to<00:22:09.919> the 00:22:09.999 --> 00:22:10.009 align:start position:0% lot of value can be delivered to the 00:22:10.009 --> 00:22:12.279 align:start position:0% lot of value can be delivered to the community<00:22:10.429> with<00:22:10.639> shared<00:22:11.299> tools<00:22:11.629> that<00:22:11.869> for 00:22:12.279 --> 00:22:12.289 align:start position:0% community with shared tools that for 00:22:12.289 --> 00:22:16.899 align:start position:0% community with shared tools that for Casa<00:22:13.220> of<00:22:13.519> historical<00:22:14.029> data<00:22:14.179> and<00:22:15.580> that<00:22:16.580> is 00:22:16.899 --> 00:22:16.909 align:start position:0% Casa of historical data and that is 00:22:16.909 --> 00:22:28.410 align:start position:0% Casa of historical data and that is pretty<00:22:17.659> much 00:22:28.410 --> 00:22:28.420 align:start position:0% 00:22:28.420 --> 00:22:30.810 align:start position:0% definitely<00:22:29.420> have<00:22:29.570> the<00:22:29.690> answer<00:22:29.930> any<00:22:30.020> questions 00:22:30.810 --> 00:22:30.820 align:start position:0% definitely have the answer any questions 00:22:30.820 --> 00:22:33.610 align:start position:0% definitely have the answer any questions yep<00:22:31.820> there's<00:22:32.270> one<00:22:32.450> subscriptions<00:22:33.170> on<00:22:33.380> the 00:22:33.610 --> 00:22:33.620 align:start position:0% yep there's one subscriptions on the 00:22:33.620 --> 00:22:36.790 align:start position:0% yep there's one subscriptions on the Rettig<00:22:34.100> oh<00:22:34.190> yeah<00:22:35.090> yeah<00:22:35.450> it's<00:22:36.140> post<00:22:36.350> grab<00:22:36.560> out 00:22:36.790 --> 00:22:36.800 align:start position:0% Rettig oh yeah yeah it's post grab out 00:22:36.800 --> 00:22:39.190 align:start position:0% Rettig oh yeah yeah it's post grab out is<00:22:37.100> again<00:22:37.940> just<00:22:38.270> like<00:22:38.450> the<00:22:38.570> most<00:22:38.690> awesome<00:22:39.110> the 00:22:39.190 --> 00:22:39.200 align:start position:0% is again just like the most awesome the 00:22:39.200 --> 00:22:41.650 align:start position:0% is again just like the most awesome the Bossip<00:22:39.530> open-source<00:22:39.980> projects<00:22:40.540> it's<00:22:41.540> of 00:22:41.650 --> 00:22:41.660 align:start position:0% Bossip open-source projects it's of 00:22:41.660 --> 00:22:43.120 align:start position:0% Bossip open-source projects it's of course<00:22:41.810> subscriptions<00:22:42.350> out<00:22:42.470> of<00:22:42.590> barks<00:22:42.920> oh 00:22:43.120 --> 00:22:43.130 align:start position:0% course subscriptions out of barks oh 00:22:43.130 --> 00:22:46.660 align:start position:0% course subscriptions out of barks oh yeah<00:22:43.840> oh<00:22:44.840> it<00:22:45.530> just<00:22:45.560> curious 00:22:46.660 --> 00:22:46.670 align:start position:0% yeah oh it just curious 00:22:46.670 --> 00:22:50.320 align:start position:0% yeah oh it just curious intercom<00:22:47.210> file<00:22:47.660> they<00:22:48.170> showed<00:22:48.410> us<00:22:49.210> it's<00:22:50.210> quite 00:22:50.320 --> 00:22:50.330 align:start position:0% intercom file they showed us it's quite 00:22:50.330 --> 00:22:52.960 align:start position:0% intercom file they showed us it's quite another<00:22:50.570> dress<00:22:50.870> right<00:22:51.380> so<00:22:52.130> how<00:22:52.580> do<00:22:52.640> you<00:22:52.730> deal 00:22:52.960 --> 00:22:52.970 align:start position:0% another dress right so how do you deal 00:22:52.970 --> 00:22:58.270 align:start position:0% another dress right so how do you deal with<00:22:55.720> all<00:22:56.720> the<00:22:57.080> contracts<00:22:57.920> for<00:22:58.010> each 00:22:58.270 --> 00:22:58.280 align:start position:0% with all the contracts for each 00:22:58.280 --> 00:23:00.250 align:start position:0% with all the contracts for each individual<00:22:58.790> user<00:22:58.850> with<00:22:59.750> the<00:22:59.780> same<00:23:00.050> bytecodes 00:23:00.250 --> 00:23:00.260 align:start position:0% individual user with the same bytecodes 00:23:00.260 --> 00:23:02.280 align:start position:0% individual user with the same bytecodes and<00:23:00.920> some<00:23:01.340> you<00:23:01.490> know<00:23:01.610> the<00:23:01.790> induction 00:23:02.280 --> 00:23:02.290 align:start position:0% and some you know the induction 00:23:02.290 --> 00:23:03.850 align:start position:0% and some you know the induction hypothesis<00:23:03.290> my<00:23:03.440> choices 00:23:03.850 --> 00:23:03.860 align:start position:0% hypothesis my choices 00:23:03.860 --> 00:23:05.590 align:start position:0% hypothesis my choices yeah<00:23:04.550> so<00:23:04.790> you<00:23:04.910> definitely<00:23:05.060> want<00:23:05.450> to<00:23:05.510> like 00:23:05.590 --> 00:23:05.600 align:start position:0% yeah so you definitely want to like 00:23:05.600 --> 00:23:07.480 align:start position:0% yeah so you definitely want to like write<00:23:05.810> a<00:23:05.840> plug-in<00:23:06.140> to<00:23:06.440> deal<00:23:06.620> with<00:23:06.830> that<00:23:07.040> right 00:23:07.480 --> 00:23:07.490 align:start position:0% write a plug-in to deal with that right 00:23:07.490 --> 00:23:10.240 align:start position:0% write a plug-in to deal with that right because<00:23:07.910> um<00:23:08.420> what<00:23:09.230> the<00:23:09.350> contract<00:23:09.800> watcher<00:23:10.160> is 00:23:10.240 --> 00:23:10.250 align:start position:0% because um what the contract watcher is 00:23:10.250 --> 00:23:12.370 align:start position:0% because um what the contract watcher is giving<00:23:10.580> you<00:23:10.700> is<00:23:10.850> it's<00:23:11.000> giving<00:23:11.330> you<00:23:11.480> uh<00:23:11.510> upfront 00:23:12.370 --> 00:23:12.380 align:start position:0% giving you is it's giving you uh upfront 00:23:12.380 --> 00:23:14.890 align:start position:0% giving you is it's giving you uh upfront facility<00:23:12.980> to<00:23:13.130> say<00:23:13.340> like<00:23:13.640> give<00:23:14.300> it<00:23:14.360> a<00:23:14.450> contract 00:23:14.890 --> 00:23:14.900 align:start position:0% facility to say like give it a contract 00:23:14.900 --> 00:23:16.810 align:start position:0% facility to say like give it a contract address<00:23:15.260> I<00:23:15.470> want<00:23:15.710> to<00:23:15.830> see<00:23:15.950> all<00:23:16.130> of<00:23:16.160> its<00:23:16.370> events 00:23:16.810 --> 00:23:16.820 align:start position:0% address I want to see all of its events 00:23:16.820 --> 00:23:19.960 align:start position:0% address I want to see all of its events like<00:23:17.000> decoded<00:23:17.570> which<00:23:18.350> you<00:23:19.160> know<00:23:19.280> I<00:23:19.460> think<00:23:19.490> has 00:23:19.960 --> 00:23:19.970 align:start position:0% like decoded which you know I think has 00:23:19.970 --> 00:23:21.760 align:start position:0% like decoded which you know I think has some<00:23:20.180> value<00:23:20.510> on<00:23:20.540> its<00:23:20.780> own<00:23:20.930> but<00:23:21.200> we're<00:23:21.620> not 00:23:21.760 --> 00:23:21.770 align:start position:0% some value on its own but we're not 00:23:21.770 --> 00:23:23.920 align:start position:0% some value on its own but we're not trying<00:23:21.950> to<00:23:22.130> be<00:23:22.310> like<00:23:22.340> super<00:23:23.240> aggressive<00:23:23.690> on 00:23:23.920 --> 00:23:23.930 align:start position:0% trying to be like super aggressive on 00:23:23.930 --> 00:23:25.810 align:start position:0% trying to be like super aggressive on that<00:23:24.170> with<00:23:24.410> the<00:23:24.620> contract<00:23:25.040> watcher<00:23:25.430> itself 00:23:25.810 --> 00:23:25.820 align:start position:0% that with the contract watcher itself 00:23:25.820 --> 00:23:29.290 align:start position:0% that with the contract watcher itself but<00:23:26.810> with<00:23:26.960> plugins<00:23:27.410> what<00:23:27.590> you<00:23:27.680> can<00:23:27.860> do<00:23:28.100> is<00:23:28.430> you 00:23:29.290 --> 00:23:29.300 align:start position:0% but with plugins what you can do is you 00:23:29.300 --> 00:23:30.020 align:start position:0% but with plugins what you can do is you can<00:23:29.450> say 00:23:30.020 --> 00:23:30.030 align:start position:0% can say 00:23:30.030 --> 00:23:32.210 align:start position:0% can say okay<00:23:30.300> like<00:23:30.600> given<00:23:31.260> that<00:23:31.380> I<00:23:31.470> see<00:23:31.680> this<00:23:31.890> event 00:23:32.210 --> 00:23:32.220 align:start position:0% okay like given that I see this event 00:23:32.220 --> 00:23:34.610 align:start position:0% okay like given that I see this event that<00:23:32.430> I<00:23:32.460> want<00:23:32.700> to<00:23:32.820> spit<00:23:33.060> up<00:23:33.240> Big<00:23:33.930> Canoe<00:23:34.080> and<00:23:34.560> so 00:23:34.610 --> 00:23:34.620 align:start position:0% that I want to spit up Big Canoe and so 00:23:34.620 --> 00:23:36.200 align:start position:0% that I want to spit up Big Canoe and so the<00:23:34.770> contract<00:23:35.190> watch<00:23:35.400> her<00:23:35.580> appointment<00:23:36.120> to 00:23:36.200 --> 00:23:36.210 align:start position:0% the contract watch her appointment to 00:23:36.210 --> 00:23:38.150 align:start position:0% the contract watch her appointment to have<00:23:36.240> a<00:23:36.600> field<00:23:36.960> on<00:23:37.140> that<00:23:37.290> event<00:23:37.470> that<00:23:37.740> is<00:23:37.950> an 00:23:38.150 --> 00:23:38.160 align:start position:0% have a field on that event that is an 00:23:38.160 --> 00:23:40.340 align:start position:0% have a field on that event that is an address<00:23:38.430> that<00:23:38.460> I<00:23:38.700> care<00:23:38.910> about<00:23:38.940> or<00:23:39.660> you<00:23:40.230> know 00:23:40.340 --> 00:23:40.350 align:start position:0% address that I care about or you know 00:23:40.350 --> 00:23:41.690 align:start position:0% address that I care about or you know any<00:23:40.620> number<00:23:40.980> of<00:23:41.070> ways<00:23:41.190> you<00:23:41.370> can<00:23:41.490> implement 00:23:41.690 --> 00:23:41.700 align:start position:0% any number of ways you can implement 00:23:41.700 --> 00:23:44.300 align:start position:0% any number of ways you can implement that<00:23:41.910> to<00:23:42.360> to<00:23:43.140> run<00:23:43.260> the<00:23:43.350> process<00:23:43.530> and<00:23:44.100> we<00:23:44.280> have 00:23:44.300 --> 00:23:44.310 align:start position:0% that to to run the process and we have 00:23:44.310 --> 00:23:47.900 align:start position:0% that to to run the process and we have code<00:23:44.880> that<00:23:45.060> does<00:23:45.240> that<00:23:45.860> some<00:23:46.860> ian's<00:23:47.250> code<00:23:47.490> yes 00:23:47.900 --> 00:23:47.910 align:start position:0% code that does that some ian's code yes 00:23:47.910 --> 00:23:49.730 align:start position:0% code that does that some ian's code yes there's<00:23:48.840> a<00:23:48.930> couple<00:23:49.200> different<00:23:49.290> teams<00:23:49.650> that 00:23:49.730 --> 00:23:49.740 align:start position:0% there's a couple different teams that 00:23:49.740 --> 00:23:51.350 align:start position:0% there's a couple different teams that working<00:23:50.040> both<00:23:50.190> nice<00:23:50.400> TV<00:23:50.580> so<00:23:50.880> there's<00:23:51.150> another 00:23:51.350 --> 00:23:51.360 align:start position:0% working both nice TV so there's another 00:23:51.360 --> 00:23:54.110 align:start position:0% working both nice TV so there's another code<00:23:51.600> base<00:23:51.840> that<00:23:52.200> actually<00:23:52.920> does<00:23:53.310> that<00:23:53.340> it 00:23:54.110 --> 00:23:54.120 align:start position:0% code base that actually does that it 00:23:54.120 --> 00:23:57.260 align:start position:0% code base that actually does that it takes<00:23:54.440> it<00:23:55.440> will<00:23:55.620> read<00:23:55.890> a<00:23:55.920> contract<00:23:56.220> to<00:23:57.030> get<00:23:57.180> a 00:23:57.260 --> 00:23:57.270 align:start position:0% takes it will read a contract to get a 00:23:57.270 --> 00:23:59.330 align:start position:0% takes it will read a contract to get a contract<00:23:57.750> address<00:23:58.110> and<00:23:58.410> then<00:23:58.620> write<00:23:58.800> the<00:23:58.980> code 00:23:59.330 --> 00:23:59.340 align:start position:0% contract address and then write the code 00:23:59.340 --> 00:24:06.040 align:start position:0% contract address and then write the code without<00:23:59.670> a<00:23:59.820> dress<00:24:03.200> like<00:24:04.220> anyone<00:24:05.220> just<00:24:05.460> to 00:24:06.040 --> 00:24:06.050 align:start position:0% without a dress like anyone just to 00:24:06.050 --> 00:24:15.050 align:start position:0% without a dress like anyone just to simple<00:24:07.050> API<00:24:11.360> to<00:24:12.360> keep<00:24:12.510> track<00:24:13.220> into<00:24:14.220> Academy 00:24:15.050 --> 00:24:15.060 align:start position:0% simple API to keep track into Academy 00:24:15.060 --> 00:24:16.730 align:start position:0% simple API to keep track into Academy yes<00:24:15.690> that's<00:24:15.960> actually<00:24:16.260> what<00:24:16.410> I<00:24:16.590> was<00:24:16.710> just 00:24:16.730 --> 00:24:16.740 align:start position:0% yes that's actually what I was just 00:24:16.740 --> 00:24:19.490 align:start position:0% yes that's actually what I was just talking<00:24:16.950> about<00:24:17.190> it<00:24:17.640> was<00:24:18.240> an<00:24:18.360> ER<00:24:18.540> c20<00:24:19.050> watcher 00:24:19.490 --> 00:24:19.500 align:start position:0% talking about it was an ER c20 watcher 00:24:19.500 --> 00:24:21.950 align:start position:0% talking about it was an ER c20 watcher and<00:24:19.770> we<00:24:20.430> just<00:24:20.640> didn't<00:24:20.790> year<00:24:20.910> c20<00:24:21.330> watcher<00:24:21.690> but 00:24:21.950 --> 00:24:21.960 align:start position:0% and we just didn't year c20 watcher but 00:24:21.960 --> 00:24:23.180 align:start position:0% and we just didn't year c20 watcher but obviously<00:24:22.410> you<00:24:22.500> could<00:24:22.650> change<00:24:22.830> it<00:24:22.980> to<00:24:23.010> make<00:24:23.160> it 00:24:23.180 --> 00:24:23.190 align:start position:0% obviously you could change it to make it 00:24:23.190 --> 00:24:25.550 align:start position:0% obviously you could change it to make it in<00:24:23.370> ear<00:24:23.460> gear<00:24:24.030> see<00:24:24.240> seven<00:24:24.570> to<00:24:24.870> one<00:24:25.020> washer<00:24:25.440> as 00:24:25.550 --> 00:24:25.560 align:start position:0% in ear gear see seven to one washer as 00:24:25.560 --> 00:24:28.730 align:start position:0% in ear gear see seven to one washer as well<00:24:26.420> yeah<00:24:27.420> I<00:24:27.450> mean<00:24:27.690> one<00:24:28.200> thing<00:24:28.410> just<00:24:28.620> to 00:24:28.730 --> 00:24:28.740 align:start position:0% well yeah I mean one thing just to 00:24:28.740 --> 00:24:30.890 align:start position:0% well yeah I mean one thing just to expand<00:24:29.400> on<00:24:29.550> that<00:24:29.700> point<00:24:29.940> too 00:24:30.890 --> 00:24:30.900 align:start position:0% expand on that point too 00:24:30.900 --> 00:24:33.830 align:start position:0% expand on that point too you<00:24:31.590> know<00:24:31.710> we<00:24:32.070> sort<00:24:32.670> of<00:24:32.790> tinkered<00:24:33.300> with<00:24:33.330> a 00:24:33.830 --> 00:24:33.840 align:start position:0% you know we sort of tinkered with a 00:24:33.840 --> 00:24:36.410 align:start position:0% you know we sort of tinkered with a variety<00:24:34.140> of<00:24:34.590> different<00:24:35.100> amounts<00:24:35.940> of<00:24:36.120> like 00:24:36.410 --> 00:24:36.420 align:start position:0% variety of different amounts of like 00:24:36.420 --> 00:24:39.680 align:start position:0% variety of different amounts of like face<00:24:36.690> data<00:24:37.110> that<00:24:37.470> you<00:24:37.620> can<00:24:37.800> scan<00:24:38.700> for<00:24:39.150> when 00:24:39.680 --> 00:24:39.690 align:start position:0% face data that you can scan for when 00:24:39.690 --> 00:24:42.050 align:start position:0% face data that you can scan for when you're<00:24:39.870> running<00:24:40.110> vulcanize<00:24:40.680> TV<00:24:41.070> and<00:24:41.310> so<00:24:41.880> we 00:24:42.050 --> 00:24:42.060 align:start position:0% you're running vulcanize TV and so we 00:24:42.060 --> 00:24:44.270 align:start position:0% you're running vulcanize TV and so we started<00:24:42.360> off<00:24:42.480> in<00:24:42.750> like<00:24:42.960> listed<00:24:43.620> just<00:24:43.800> like 00:24:44.270 --> 00:24:44.280 align:start position:0% started off in like listed just like 00:24:44.280 --> 00:24:46.190 align:start position:0% started off in like listed just like digest<00:24:44.790> everything<00:24:45.150> and<00:24:45.600> anyone<00:24:45.870> can<00:24:46.020> run 00:24:46.190 --> 00:24:46.200 align:start position:0% digest everything and anyone can run 00:24:46.200 --> 00:24:47.840 align:start position:0% digest everything and anyone can run this<00:24:46.350> and<00:24:46.560> digest<00:24:46.860> everything<00:24:47.130> but<00:24:47.460> like<00:24:47.580> I 00:24:47.840 --> 00:24:47.850 align:start position:0% this and digest everything but like I 00:24:47.850 --> 00:24:50.870 align:start position:0% this and digest everything but like I think<00:24:48.450> reality<00:24:49.110> is<00:24:49.590> that<00:24:49.830> a<00:24:50.070> lot<00:24:50.370> of<00:24:50.610> people 00:24:50.870 --> 00:24:50.880 align:start position:0% think reality is that a lot of people 00:24:50.880 --> 00:24:53.420 align:start position:0% think reality is that a lot of people who<00:24:51.090> might<00:24:51.210> get<00:24:51.390> value<00:24:51.750> from<00:24:51.900> vocalize<00:24:52.380> DB<00:24:52.770> are 00:24:53.420 --> 00:24:53.430 align:start position:0% who might get value from vocalize DB are 00:24:53.430 --> 00:24:56.810 align:start position:0% who might get value from vocalize DB are not<00:24:54.360> necessarily<00:24:55.200> super<00:24:55.410> stoked<00:24:55.920> to<00:24:56.160> like<00:24:56.460> pay 00:24:56.810 --> 00:24:56.820 align:start position:0% not necessarily super stoked to like pay 00:24:56.820 --> 00:24:59.060 align:start position:0% not necessarily super stoked to like pay the<00:24:57.090> performance<00:24:57.840> cost<00:24:58.080> that<00:24:58.350> it<00:24:58.470> takes<00:24:58.500> to 00:24:59.060 --> 00:24:59.070 align:start position:0% the performance cost that it takes to 00:24:59.070 --> 00:25:01.700 align:start position:0% the performance cost that it takes to digest<00:24:59.880> all<00:25:00.030> of<00:25:00.270> that<00:25:00.450> extra<00:25:01.050> information 00:25:01.700 --> 00:25:01.710 align:start position:0% digest all of that extra information 00:25:01.710 --> 00:25:04.220 align:start position:0% digest all of that extra information if<00:25:01.980> they<00:25:02.160> don't<00:25:02.280> eat<00:25:02.520> it<00:25:02.550> right<00:25:03.210> so<00:25:03.540> a<00:25:03.810> lot<00:25:04.200> of 00:25:04.220 --> 00:25:04.230 align:start position:0% if they don't eat it right so a lot of 00:25:04.230 --> 00:25:05.450 align:start position:0% if they don't eat it right so a lot of what<00:25:04.380> I've<00:25:04.470> been<00:25:04.500> demoing<00:25:04.770> here<00:25:05.160> is<00:25:05.250> like<00:25:05.430> a 00:25:05.450 --> 00:25:05.460 align:start position:0% what I've been demoing here is like a 00:25:05.460 --> 00:25:07.400 align:start position:0% what I've been demoing here is like a pretty<00:25:05.700> lightweight<00:25:06.000> process<00:25:06.720> of<00:25:06.990> sinking 00:25:07.400 --> 00:25:07.410 align:start position:0% pretty lightweight process of sinking 00:25:07.410 --> 00:25:09.710 align:start position:0% pretty lightweight process of sinking headers<00:25:07.830> and<00:25:08.100> syncing<00:25:08.760> events<00:25:09.150> from<00:25:09.270> specific 00:25:09.710 --> 00:25:09.720 align:start position:0% headers and syncing events from specific 00:25:09.720 --> 00:25:12.080 align:start position:0% headers and syncing events from specific targeted<00:25:10.080> contracts<00:25:10.650> there<00:25:11.220> are<00:25:11.460> over<00:25:11.790> tools 00:25:12.080 --> 00:25:12.090 align:start position:0% targeted contracts there are over tools 00:25:12.090 --> 00:25:14.780 align:start position:0% targeted contracts there are over tools in<00:25:12.330> the<00:25:12.420> box<00:25:12.690> that<00:25:12.990> enable<00:25:13.350> you<00:25:13.500> to<00:25:13.550> do<00:25:14.550> more 00:25:14.780 --> 00:25:14.790 align:start position:0% in the box that enable you to do more 00:25:14.790 --> 00:25:16.310 align:start position:0% in the box that enable you to do more heavyweight<00:25:15.060> stuff<00:25:15.510> if<00:25:15.780> you've<00:25:15.990> got<00:25:16.170> the 00:25:16.310 --> 00:25:16.320 align:start position:0% heavyweight stuff if you've got the 00:25:16.320 --> 00:25:19.040 align:start position:0% heavyweight stuff if you've got the infrared<00:25:16.710> the<00:25:16.800> motivation<00:25:17.280> to<00:25:17.460> do<00:25:17.610> that<00:25:18.050> and 00:25:19.040 --> 00:25:19.050 align:start position:0% infrared the motivation to do that and 00:25:19.050 --> 00:25:20.570 align:start position:0% infrared the motivation to do that and we're<00:25:19.350> hoping<00:25:19.530> the<00:25:19.650> supernova<00:25:20.130> can<00:25:20.280> help<00:25:20.430> out 00:25:20.570 --> 00:25:20.580 align:start position:0% we're hoping the supernova can help out 00:25:20.580 --> 00:25:26.320 align:start position:0% we're hoping the supernova can help out with<00:25:20.670> that<00:25:20.790> lot<00:25:21.000> too<00:25:23.060> well<00:25:24.920> another<00:25:25.920> question 00:25:26.320 --> 00:25:26.330 align:start position:0% with that lot too well another question 00:25:26.330 --> 00:25:30.410 align:start position:0% with that lot too well another question okay<00:25:27.650> is<00:25:28.650> there<00:25:28.800> a<00:25:28.860> reason<00:25:29.670> for<00:25:29.700> not<00:25:29.910> sinking 00:25:30.410 --> 00:25:30.420 align:start position:0% okay is there a reason for not sinking 00:25:30.420 --> 00:25:34.310 align:start position:0% okay is there a reason for not sinking backwards<00:25:31.880> because<00:25:32.880> to<00:25:33.240> maintenance<00:25:33.660> that 00:25:34.310 --> 00:25:34.320 align:start position:0% backwards because to maintenance that 00:25:34.320 --> 00:25:36.500 align:start position:0% backwards because to maintenance that I've<00:25:34.860> seen<00:25:35.040> from<00:25:35.280> the<00:25:35.430> starting<00:25:35.760> book<00:25:35.910> which 00:25:36.500 --> 00:25:36.510 align:start position:0% I've seen from the starting book which 00:25:36.510 --> 00:25:38.710 align:start position:0% I've seen from the starting book which means<00:25:36.750> it<00:25:36.840> takes<00:25:37.080> you<00:25:37.320> 30<00:25:37.560> hours<00:25:38.010> to<00:25:38.160> get<00:25:38.280> to 00:25:38.710 --> 00:25:38.720 align:start position:0% means it takes you 30 hours to get to 00:25:38.720 --> 00:25:40.880 align:start position:0% means it takes you 30 hours to get to defense<00:25:39.720> you<00:25:39.840> probably<00:25:40.140> care<00:25:40.320> of<00:25:40.470> us 00:25:40.880 --> 00:25:40.890 align:start position:0% defense you probably care of us 00:25:40.890 --> 00:25:44.240 align:start position:0% defense you probably care of us yeah<00:25:41.840> so<00:25:42.840> I<00:25:43.230> mean<00:25:43.380> that<00:25:43.530> the<00:25:43.680> main<00:25:43.830> thing<00:25:44.100> is 00:25:44.240 --> 00:25:44.250 align:start position:0% yeah so I mean that the main thing is 00:25:44.250 --> 00:25:47.600 align:start position:0% yeah so I mean that the main thing is just<00:25:44.280> like<00:25:44.670> I<00:25:44.940> guess<00:25:45.510> that<00:25:46.050> the<00:25:46.680> latest<00:25:47.280> blocks 00:25:47.600 --> 00:25:47.610 align:start position:0% just like I guess that the latest blocks 00:25:47.610 --> 00:25:49.280 align:start position:0% just like I guess that the latest blocks are<00:25:47.880> more<00:25:48.030> likely<00:25:48.240> to<00:25:48.450> be<00:25:48.600> removed<00:25:48.930> by<00:25:49.230> the 00:25:49.280 --> 00:25:49.290 align:start position:0% are more likely to be removed by the 00:25:49.290 --> 00:25:52.120 align:start position:0% are more likely to be removed by the henderson<00:25:49.800> process<00:25:50.310> right<00:25:50.640> so<00:25:50.940> you'd<00:25:51.690> be 00:25:52.120 --> 00:25:52.130 align:start position:0% henderson process right so you'd be 00:25:52.130 --> 00:25:54.230 align:start position:0% henderson process right so you'd be potentially<00:25:53.130> doing<00:25:53.400> a<00:25:53.430> lot<00:25:53.550> more<00:25:53.580> redundant 00:25:54.230 --> 00:25:54.240 align:start position:0% potentially doing a lot more redundant 00:25:54.240 --> 00:25:56.810 align:start position:0% potentially doing a lot more redundant work<00:25:54.440> you<00:25:55.440> can<00:25:55.590> totally<00:25:55.980> get<00:25:56.100> around<00:25:56.370> that<00:25:56.610> if 00:25:56.810 --> 00:25:56.820 align:start position:0% work you can totally get around that if 00:25:56.820 --> 00:25:59.060 align:start position:0% work you can totally get around that if you're<00:25:56.940> interested<00:25:57.480> by<00:25:57.780> starting<00:25:58.740> the<00:25:58.890> header 00:25:59.060 --> 00:25:59.070 align:start position:0% you're interested by starting the header 00:25:59.070 --> 00:26:01.340 align:start position:0% you're interested by starting the header sync<00:25:59.370> process<00:25:59.580> with<00:26:00.210> a<00:26:00.240> more<00:26:00.630> recent<00:26:00.780> starting 00:26:01.340 --> 00:26:01.350 align:start position:0% sync process with a more recent starting 00:26:01.350 --> 00:26:04.160 align:start position:0% sync process with a more recent starting block<00:26:01.560> number<00:26:01.950> right<00:26:02.490> so<00:26:02.760> I<00:26:03.090> was<00:26:03.540> demoing<00:26:03.900> with 00:26:04.160 --> 00:26:04.170 align:start position:0% block number right so I was demoing with 00:26:04.170 --> 00:26:06.110 align:start position:0% block number right so I was demoing with like<00:26:04.440> the<00:26:04.620> deployment<00:26:05.250> block<00:26:05.430> as<00:26:05.730> a<00:26:05.760> starting 00:26:06.110 --> 00:26:06.120 align:start position:0% like the deployment block as a starting 00:26:06.120 --> 00:26:07.370 align:start position:0% like the deployment block as a starting block<00:26:06.240> number<00:26:06.690> so<00:26:06.840> that<00:26:07.020> you<00:26:07.080> know<00:26:07.200> you're 00:26:07.370 --> 00:26:07.380 align:start position:0% block number so that you know you're 00:26:07.380 --> 00:26:08.870 align:start position:0% block number so that you know you're going<00:26:07.530> to<00:26:07.560> get<00:26:07.650> like<00:26:07.860> all<00:26:08.040> of<00:26:08.250> the<00:26:08.400> events<00:26:08.730> but 00:26:08.870 --> 00:26:08.880 align:start position:0% going to get like all of the events but 00:26:08.880 --> 00:26:10.610 align:start position:0% going to get like all of the events but if<00:26:09.000> you<00:26:09.120> really<00:26:09.300> wanted<00:26:09.630> to<00:26:09.690> say<00:26:09.870> like<00:26:10.080> I've 00:26:10.610 --> 00:26:10.620 align:start position:0% if you really wanted to say like I've 00:26:10.620 --> 00:26:11.930 align:start position:0% if you really wanted to say like I've always<00:26:10.830> been<00:26:10.920> up<00:26:11.160> an<00:26:11.250> instance<00:26:11.550> to<00:26:11.670> give<00:26:11.820> me 00:26:11.930 --> 00:26:11.940 align:start position:0% always been up an instance to give me 00:26:11.940 --> 00:26:13.370 align:start position:0% always been up an instance to give me like<00:26:12.120> what<00:26:12.300> happened<00:26:12.630> the<00:26:12.690> last<00:26:12.720> five<00:26:13.140> days 00:26:13.370 --> 00:26:13.380 align:start position:0% like what happened the last five days 00:26:13.380 --> 00:26:15.530 align:start position:0% like what happened the last five days then<00:26:14.100> you<00:26:14.250> can<00:26:14.430> pop<00:26:14.670> that<00:26:14.880> in<00:26:15.090> at<00:26:15.330> the 00:26:15.530 --> 00:26:15.540 align:start position:0% then you can pop that in at the 00:26:15.540 --> 00:26:18.680 align:start position:0% then you can pop that in at the Perimeter<00:26:16.080> to<00:26:16.260> the<00:26:16.350> command<00:26:16.710> a<00:26:17.400> block<00:26:18.300> number 00:26:18.680 --> 00:26:18.690 align:start position:0% Perimeter to the command a block number 00:26:18.690 --> 00:26:20.690 align:start position:0% Perimeter to the command a block number where<00:26:18.900> you<00:26:19.080> start<00:26:19.710> caring<00:26:20.040> about<00:26:20.100> stuff<00:26:20.490> and 00:26:20.690 --> 00:26:20.700 align:start position:0% where you start caring about stuff and 00:26:20.700 --> 00:26:22.370 align:start position:0% where you start caring about stuff and then<00:26:20.820> that's<00:26:20.970> where<00:26:21.240> this<00:26:21.900> thing<00:26:21.960> will<00:26:22.290> happen 00:26:22.370 --> 00:26:22.380 align:start position:0% then that's where this thing will happen 00:26:22.380 --> 00:26:25.310 align:start position:0% then that's where this thing will happen from<00:26:22.680> no<00:26:23.430> but<00:26:23.580> I<00:26:23.610> mean<00:26:23.790> you<00:26:24.720> would<00:26:24.990> you<00:26:25.080> care 00:26:25.310 --> 00:26:25.320 align:start position:0% from no but I mean you would you care 00:26:25.320 --> 00:26:26.270 align:start position:0% from no but I mean you would you care about<00:26:25.530> everything 00:26:26.270 --> 00:26:26.280 align:start position:0% about everything 00:26:26.280 --> 00:26:30.800 align:start position:0% about everything it's<00:26:26.940> just<00:26:27.240> that's<00:26:27.420> I<00:26:28.640> in<00:26:29.640> that<00:26:29.790> 30<00:26:30.000> 30<00:26:30.480> hours 00:26:30.800 --> 00:26:30.810 align:start position:0% it's just that's I in that 30 30 hours 00:26:30.810 --> 00:26:34.030 align:start position:0% it's just that's I in that 30 30 hours you<00:26:30.870> want<00:26:30.990> to<00:26:31.080> do<00:26:31.230> something<00:26:31.560> as<00:26:31.680> well<00:26:31.860> yeah<00:26:32.490> so 00:26:34.030 --> 00:26:34.040 align:start position:0% you want to do something as well yeah so 00:26:34.040 --> 00:26:34.990 align:start position:0% you want to do something as well yeah so and<00:26:34.130> you<00:26:34.220> have<00:26:34.340> a<00:26:34.370> book<00:26:34.580> watch<00:26:34.820> you're 00:26:34.990 --> 00:26:35.000 align:start position:0% and you have a book watch you're 00:26:35.000 --> 00:26:37.000 align:start position:0% and you have a book watch you're watching<00:26:35.330> for<00:26:35.510> new<00:26:35.660> blows<00:26:35.930> so<00:26:36.380> your<00:26:36.770> real 00:26:37.000 --> 00:26:37.010 align:start position:0% watching for new blows so your real 00:26:37.010 --> 00:26:38.800 align:start position:0% watching for new blows so your real rooster<00:26:37.310> just<00:26:37.520> managed<00:26:38.180> to<00:26:38.330> just<00:26:38.510> the<00:26:38.630> same 00:26:38.800 --> 00:26:38.810 align:start position:0% rooster just managed to just the same 00:26:38.810 --> 00:26:40.570 align:start position:0% rooster just managed to just the same way<00:26:38.960> as<00:26:38.990> they<00:26:39.170> are<00:26:39.290> right<00:26:39.530> now<00:26:39.590> yep<00:26:40.190> it's<00:26:40.490> just 00:26:40.570 --> 00:26:40.580 align:start position:0% way as they are right now yep it's just 00:26:40.580 --> 00:26:42.460 align:start position:0% way as they are right now yep it's just it's<00:26:40.820> not<00:26:40.910> starting<00:26:41.420> at<00:26:41.510> 7:00<00:26:41.870> visit<00:26:42.170> whatever 00:26:42.460 --> 00:26:42.470 align:start position:0% it's not starting at 7:00 visit whatever 00:26:42.470 --> 00:26:45.100 align:start position:0% it's not starting at 7:00 visit whatever you<00:26:43.160> walk<00:26:43.580> backwards<00:26:44.090> from<00:26:44.330> the<00:26:44.630> moment<00:26:44.990> you 00:26:45.100 --> 00:26:45.110 align:start position:0% you walk backwards from the moment you 00:26:45.110 --> 00:26:46.900 align:start position:0% you walk backwards from the moment you start<00:26:45.290> at<00:26:45.440> the<00:26:45.500> book<00:26:45.680> watch<00:26:45.860> yeah<00:26:46.520> but<00:26:46.730> before 00:26:46.900 --> 00:26:46.910 align:start position:0% start at the book watch yeah but before 00:26:46.910 --> 00:26:49.990 align:start position:0% start at the book watch yeah but before but<00:26:47.270> before<00:26:47.540> what<00:26:47.720> before<00:26:48.340> yeah<00:26:49.340> so<00:26:49.700> the<00:26:49.790> short 00:26:49.990 --> 00:26:50.000 align:start position:0% but before what before yeah so the short 00:26:50.000 --> 00:26:51.610 align:start position:0% but before what before yeah so the short answer<00:26:50.090> is<00:26:50.300> it<00:26:50.450> is<00:26:50.660> technically<00:26:51.050> harder<00:26:51.410> to<00:26:51.500> do 00:26:51.610 --> 00:26:51.620 align:start position:0% answer is it is technically harder to do 00:26:51.620 --> 00:26:55.870 align:start position:0% answer is it is technically harder to do that<00:26:51.820> just<00:26:52.820> generally<00:26:53.680> gap<00:26:54.680> doesn't<00:26:55.220> like 00:26:55.870 --> 00:26:55.880 align:start position:0% that just generally gap doesn't like 00:26:55.880 --> 00:27:00.310 align:start position:0% that just generally gap doesn't like it's<00:26:56.090> a<00:26:56.150> goal<00:26:56.330> in<00:26:56.600> Reverse<00:26:57.910> so<00:26:58.910> I<00:26:58.940> mean<00:26:59.480> that's 00:27:00.310 --> 00:27:00.320 align:start position:0% it's a goal in Reverse so I mean that's 00:27:00.320 --> 00:27:01.780 align:start position:0% it's a goal in Reverse so I mean that's kind<00:27:00.560> of<00:27:00.710> weak<00:27:00.980> and<00:27:01.130> if<00:27:01.340> you<00:27:01.430> have<00:27:01.550> really 00:27:01.780 --> 00:27:01.790 align:start position:0% kind of weak and if you have really 00:27:01.790 --> 00:27:03.490 align:start position:0% kind of weak and if you have really curious<00:27:02.300> about<00:27:02.450> it<00:27:02.690> we<00:27:02.810> can<00:27:02.960> really<00:27:03.260> talk 00:27:03.490 --> 00:27:03.500 align:start position:0% curious about it we can really talk 00:27:03.500 --> 00:27:04.780 align:start position:0% curious about it we can really talk about<00:27:03.800> it<00:27:03.890> but<00:27:03.950> the<00:27:04.040> short<00:27:04.250> answer<00:27:04.490> is<00:27:04.520> got 00:27:04.780 --> 00:27:04.790 align:start position:0% about it but the short answer is got 00:27:04.790 --> 00:27:06.940 align:start position:0% about it but the short answer is got doesn't<00:27:05.120> want<00:27:05.240> to<00:27:05.300> go<00:27:05.390> in<00:27:05.510> reverse<00:27:05.660> well<00:27:06.650> I 00:27:06.940 --> 00:27:06.950 align:start position:0% doesn't want to go in reverse well I 00:27:06.950 --> 00:27:08.680 align:start position:0% doesn't want to go in reverse well I mean<00:27:07.220> that's<00:27:07.460> specifically<00:27:07.910> true<00:27:08.180> also<00:27:08.510> with 00:27:08.680 --> 00:27:08.690 align:start position:0% mean that's specifically true also with 00:27:08.690 --> 00:27:10.720 align:start position:0% mean that's specifically true also with like<00:27:08.870> subscription<00:27:09.560> that's<00:27:09.680> right<00:27:09.950> so<00:27:10.190> part 00:27:10.720 --> 00:27:10.730 align:start position:0% like subscription that's right so part 00:27:10.730 --> 00:27:12.310 align:start position:0% like subscription that's right so part of<00:27:10.820> the<00:27:10.910> idea<00:27:10.940> here<00:27:11.480> is<00:27:11.570> that<00:27:11.600> you<00:27:11.840> can<00:27:12.050> easily 00:27:12.310 --> 00:27:12.320 align:start position:0% of the idea here is that you can easily 00:27:12.320 --> 00:27:14.470 align:start position:0% of the idea here is that you can easily have<00:27:12.830> like<00:27:13.010> a<00:27:13.040> subscription<00:27:13.760> to<00:27:13.940> events<00:27:14.300> but 00:27:14.470 --> 00:27:14.480 align:start position:0% have like a subscription to events but 00:27:14.480 --> 00:27:16.720 align:start position:0% have like a subscription to events but then<00:27:14.660> those<00:27:15.320> are<00:27:15.500> going<00:27:15.590> to<00:27:15.650> be<00:27:15.800> fired<00:27:16.040> as<00:27:16.400> your 00:27:16.720 --> 00:27:16.730 align:start position:0% then those are going to be fired as your 00:27:16.730 --> 00:27:18.640 align:start position:0% then those are going to be fired as your nose<00:27:16.910> like<00:27:17.330> processing<00:27:18.020> the<00:27:18.140> blocks<00:27:18.380> that 00:27:18.640 --> 00:27:18.650 align:start position:0% nose like processing the blocks that 00:27:18.650 --> 00:27:21.850 align:start position:0% nose like processing the blocks that it's<00:27:18.770> going<00:27:19.010> over<00:27:19.630> so<00:27:20.630> part<00:27:21.260> of<00:27:21.440> the<00:27:21.590> ratchet 00:27:21.850 --> 00:27:21.860 align:start position:0% it's going over so part of the ratchet 00:27:21.860 --> 00:27:23.650 align:start position:0% it's going over so part of the ratchet count<00:27:22.160> for<00:27:22.280> the<00:27:22.340> set<00:27:22.490> up<00:27:22.610> is<00:27:22.760> like<00:27:23.000> you<00:27:23.540> could 00:27:23.650 --> 00:27:23.660 align:start position:0% count for the set up is like you could 00:27:23.660 --> 00:27:25.750 align:start position:0% count for the set up is like you could use<00:27:23.720> either<00:27:24.230> subscriptions<00:27:24.980> or<00:27:25.280> get<00:27:25.490> blogs 00:27:25.750 --> 00:27:25.760 align:start position:0% use either subscriptions or get blogs 00:27:25.760 --> 00:27:28.270 align:start position:0% use either subscriptions or get blogs furies<00:27:26.300> to<00:27:26.780> progress<00:27:27.110> forward<00:27:27.440> but<00:27:28.070> I<00:27:28.100> didn't 00:27:28.270 --> 00:27:28.280 align:start position:0% furies to progress forward but I didn't 00:27:28.280 --> 00:27:29.920 align:start position:0% furies to progress forward but I didn't think<00:27:28.340> that's<00:27:28.490> a<00:27:28.610> really<00:27:28.790> cool<00:27:28.970> idea<00:27:29.120> and 00:27:29.920 --> 00:27:29.930 align:start position:0% think that's a really cool idea and 00:27:29.930 --> 00:27:33.070 align:start position:0% think that's a really cool idea and something<00:27:30.650> we<00:27:30.890> could<00:27:31.040> totally<00:27:32.030> dig<00:27:32.210> into<00:27:32.420> so 00:27:33.070 --> 00:27:33.080 align:start position:0% something we could totally dig into so 00:27:33.080 --> 00:27:38.530 align:start position:0% something we could totally dig into so appreciate<00:27:33.800> it<00:27:36.190> yeah<00:27:37.190> last<00:27:37.940> time<00:27:38.150> I<00:27:38.240> checked 00:27:38.530 --> 00:27:38.540 align:start position:0% appreciate it yeah last time I checked 00:27:38.540 --> 00:27:42.799 align:start position:0% appreciate it yeah last time I checked you<00:27:38.630> have<00:27:38.840> no<00:27:39.020> upper<00:27:39.500> body 00:27:42.799 --> 00:27:42.809 align:start position:0% 00:27:42.809 --> 00:27:48.990 align:start position:0% they're<00:27:43.809> reasonable<00:27:47.520> it's<00:27:48.520> kind<00:27:48.730> of<00:27:48.790> a<00:27:48.880> work 00:27:48.990 --> 00:27:49.000 align:start position:0% they're reasonable it's kind of a work 00:27:49.000 --> 00:27:51.600 align:start position:0% they're reasonable it's kind of a work in<00:27:49.030> progress<00:27:49.330> I<00:27:49.540> mean<00:27:49.690> we<00:27:49.809> have<00:27:50.020> I<00:27:50.490> think<00:27:51.490> we 00:27:51.600 --> 00:27:51.610 align:start position:0% in progress I mean we have I think we 00:27:51.610 --> 00:27:53.820 align:start position:0% in progress I mean we have I think we had<00:27:51.760> like<00:27:51.790> a<00:27:51.940> doctor<00:27:52.360> file<00:27:52.570> a<00:27:52.960> long<00:27:53.290> time<00:27:53.559> ago 00:27:53.820 --> 00:27:53.830 align:start position:0% had like a doctor file a long time ago 00:27:53.830 --> 00:27:55.590 align:start position:0% had like a doctor file a long time ago and<00:27:54.190> it<00:27:54.280> was<00:27:54.309> like<00:27:54.549> wanted<00:27:54.790> to<00:27:54.970> bring<00:27:55.150> TP<00:27:55.420> and 00:27:55.590 --> 00:27:55.600 align:start position:0% and it was like wanted to bring TP and 00:27:55.600 --> 00:27:57.150 align:start position:0% and it was like wanted to bring TP and we<00:27:55.750> found<00:27:55.900> it<00:27:56.140> to<00:27:56.170> be<00:27:56.320> like<00:27:56.559> not<00:27:56.770> super<00:27:57.130> useful 00:27:57.150 --> 00:27:57.160 align:start position:0% we found it to be like not super useful 00:27:57.160 --> 00:27:59.190 align:start position:0% we found it to be like not super useful over<00:27:57.700> our<00:27:57.820> day<00:27:57.970> to<00:27:58.030> day<00:27:58.120> development<00:27:58.390> so 00:27:59.190 --> 00:27:59.200 align:start position:0% over our day to day development so 00:27:59.200 --> 00:28:01.799 align:start position:0% over our day to day development so lately<00:28:00.190> there's<00:28:00.610> been<00:28:00.700> a<00:28:00.880> lot<00:28:01.270> more<00:28:01.299> work<00:28:01.450> on 00:28:01.799 --> 00:28:01.809 align:start position:0% lately there's been a lot more work on 00:28:01.809 --> 00:28:03.840 align:start position:0% lately there's been a lot more work on that<00:28:02.020> and<00:28:02.200> we<00:28:02.320> have<00:28:02.350> a<00:28:02.470> lot<00:28:02.679> of<00:28:02.710> progress<00:28:02.980> on<00:28:03.490> an 00:28:03.840 --> 00:28:03.850 align:start position:0% that and we have a lot of progress on an 00:28:03.850 --> 00:28:05.850 align:start position:0% that and we have a lot of progress on an open<00:28:04.120> PRS<00:28:04.660> I<00:28:04.870> think<00:28:05.080> it's<00:28:05.170> called<00:28:05.320> like<00:28:05.410> dr. 00:28:05.850 --> 00:28:05.860 align:start position:0% open PRS I think it's called like dr. 00:28:05.860 --> 00:28:09.210 align:start position:0% open PRS I think it's called like dr. updates<00:28:06.960> but<00:28:07.960> yes<00:28:08.140> it's<00:28:08.350> not<00:28:08.500> on<00:28:08.650> master<00:28:09.010> yet 00:28:09.210 --> 00:28:09.220 align:start position:0% updates but yes it's not on master yet 00:28:09.220 --> 00:28:11.340 align:start position:0% updates but yes it's not on master yet and<00:28:09.880> the<00:28:10.150> reason<00:28:10.480> but<00:28:10.780> the<00:28:10.840> reason<00:28:11.080> that<00:28:11.110> this 00:28:11.340 --> 00:28:11.350 align:start position:0% and the reason but the reason that this 00:28:11.350 --> 00:28:13.020 align:start position:0% and the reason but the reason that this one<00:28:11.559> is<00:28:11.710> on<00:28:11.830> its<00:28:11.950> own<00:28:12.100> branch<00:28:12.370> is<00:28:12.549> because<00:28:12.820> like 00:28:13.020 --> 00:28:13.030 align:start position:0% one is on its own branch is because like 00:28:13.030 --> 00:28:14.880 align:start position:0% one is on its own branch is because like this<00:28:13.120> is<00:28:13.179> pointed<00:28:13.630> at<00:28:13.720> no<00:28:13.840> luck<00:28:14.080> but<00:28:14.440> maybe<00:28:14.679> it 00:28:14.880 --> 00:28:14.890 align:start position:0% this is pointed at no luck but maybe it 00:28:14.890 --> 00:28:16.350 align:start position:0% this is pointed at no luck but maybe it makes<00:28:15.040> sense<00:28:15.190> at<00:28:15.490> some<00:28:15.669> point<00:28:15.880> to<00:28:16.030> have<00:28:16.059> like 00:28:16.350 --> 00:28:16.360 align:start position:0% makes sense at some point to have like 00:28:16.360 --> 00:28:19.230 align:start position:0% makes sense at some point to have like an<00:28:16.510> animal<00:28:16.840> doctor<00:28:16.990> files<00:28:17.410> but<00:28:18.309> we<00:28:18.970> didn't 00:28:19.230 --> 00:28:19.240 align:start position:0% an animal doctor files but we didn't 00:28:19.240 --> 00:28:20.909 align:start position:0% an animal doctor files but we didn't want<00:28:19.360> to<00:28:19.419> be<00:28:19.510> like<00:28:19.660> the<00:28:20.410> purpose<00:28:20.770> of 00:28:20.909 --> 00:28:20.919 align:start position:0% want to be like the purpose of 00:28:20.919 --> 00:28:22.799 align:start position:0% want to be like the purpose of vulcanized<00:28:21.340> EP<00:28:21.760> is<00:28:21.940> watching<00:28:22.299> the<00:28:22.390> Moloch 00:28:22.799 --> 00:28:22.809 align:start position:0% vulcanized EP is watching the Moloch 00:28:22.809 --> 00:28:29.820 align:start position:0% vulcanized EP is watching the Moloch contracts<00:28:23.380> you<00:28:23.650> know<00:28:26.580> yep<00:28:27.610> so<00:28:28.290> I'm<00:28:29.290> curious 00:28:29.820 --> 00:28:29.830 align:start position:0% contracts you know yep so I'm curious 00:28:29.830 --> 00:28:32.130 align:start position:0% contracts you know yep so I'm curious about<00:28:30.100> the<00:28:30.460> limitations<00:28:31.059> of<00:28:31.240> the<00:28:31.390> packing<00:28:31.780> API 00:28:32.130 --> 00:28:32.140 align:start position:0% about the limitations of the packing API 00:28:32.140 --> 00:28:34.470 align:start position:0% about the limitations of the packing API so<00:28:32.830> currently<00:28:33.429> from<00:28:33.790> what<00:28:33.910> I<00:28:34.030> understood 00:28:34.470 --> 00:28:34.480 align:start position:0% so currently from what I understood 00:28:34.480 --> 00:28:37.710 align:start position:0% so currently from what I understood begins<00:28:34.990> as<00:28:35.860> a<00:28:35.890> mouth<00:28:36.460> that's<00:28:36.730> a<00:28:37.059> so<00:28:37.299> big<00:28:37.510> mouth 00:28:37.710 --> 00:28:37.720 align:start position:0% begins as a mouth that's a so big mouth 00:28:37.720 --> 00:28:40.409 align:start position:0% begins as a mouth that's a so big mouth event<00:28:38.440> or<00:28:38.679> whatever<00:28:38.799> to<00:28:39.160> another<00:28:39.400> events<00:28:40.120> or 00:28:40.409 --> 00:28:40.419 align:start position:0% event or whatever to another events or 00:28:40.419 --> 00:28:43.200 align:start position:0% event or whatever to another events or whatever<00:28:40.510> can<00:28:41.320> they<00:28:41.470> act<00:28:41.650> as<00:28:41.890> they<00:28:42.040> reduce<00:28:42.429> so 00:28:43.200 --> 00:28:43.210 align:start position:0% whatever can they act as they reduce so 00:28:43.210 --> 00:28:46.110 align:start position:0% whatever can they act as they reduce so for<00:28:43.419> example<00:28:43.809> red<00:28:43.960> juice<00:28:44.200> I<00:28:44.460> know<00:28:45.460> the<00:28:45.970> thing 00:28:46.110 --> 00:28:46.120 align:start position:0% for example red juice I know the thing 00:28:46.120 --> 00:28:49.380 align:start position:0% for example red juice I know the thing that<00:28:46.270> makes<00:28:46.450> a<00:28:46.540> level<00:28:46.990> I<00:28:47.230> can<00:28:47.500> sum<00:28:48.160> up<00:28:48.390> transfer 00:28:49.380 --> 00:28:49.390 align:start position:0% that makes a level I can sum up transfer 00:28:49.390 --> 00:28:51.900 align:start position:0% that makes a level I can sum up transfer balance<00:28:50.049> whatever<00:28:50.530> and<00:28:51.010> how<00:28:51.490> does<00:28:51.549> it<00:28:51.760> work 00:28:51.900 --> 00:28:51.910 align:start position:0% balance whatever and how does it work 00:28:51.910 --> 00:28:54.030 align:start position:0% balance whatever and how does it work with<00:28:52.210> three<00:28:52.540> arcs<00:28:52.809> yeah<00:28:53.559> I<00:28:53.590> think<00:28:53.770> I'm<00:28:53.950> gonna 00:28:54.030 --> 00:28:54.040 align:start position:0% with three arcs yeah I think I'm gonna 00:28:54.040 --> 00:28:56.700 align:start position:0% with three arcs yeah I think I'm gonna go<00:28:54.160> straight<00:28:54.460> to<00:28:54.640> rec<00:28:54.820> on<00:28:55.000> this<00:28:55.179> one<00:28:55.390> oh<00:28:55.600> okay<00:28:56.470> I 00:28:56.700 --> 00:28:56.710 align:start position:0% go straight to rec on this one oh okay I 00:28:56.710 --> 00:28:59.250 align:start position:0% go straight to rec on this one oh okay I mean<00:28:57.070> yeah<00:28:57.370> we<00:28:57.580> could<00:28:57.790> be<00:28:57.910> running<00:28:58.090> reduce<00:28:58.570> but 00:28:59.250 --> 00:28:59.260 align:start position:0% mean yeah we could be running reduce but 00:28:59.260 --> 00:29:01.260 align:start position:0% mean yeah we could be running reduce but then<00:28:59.380> as<00:28:59.470> you<00:28:59.559> pointed<00:28:59.830> out<00:28:59.980> at<00:29:00.640> the<00:29:00.880> area 00:29:01.260 --> 00:29:01.270 align:start position:0% then as you pointed out at the area 00:29:01.270 --> 00:29:02.940 align:start position:0% then as you pointed out at the area there<00:29:01.809> we<00:29:01.960> are<00:29:01.990> so<00:29:02.260> what<00:29:02.470> you<00:29:02.620> would<00:29:02.799> be<00:29:02.919> doing 00:29:02.940 --> 00:29:02.950 align:start position:0% there we are so what you would be doing 00:29:02.950 --> 00:29:06.270 align:start position:0% there we are so what you would be doing is<00:29:03.370> you<00:29:03.520> we<00:29:04.030> would<00:29:04.210> have<00:29:04.240> a<00:29:04.390> table<00:29:05.380> like<00:29:06.250> we 00:29:06.270 --> 00:29:06.280 align:start position:0% is you we would have a table like we 00:29:06.280 --> 00:29:08.909 align:start position:0% is you we would have a table like we have<00:29:06.580> now<00:29:06.820> and<00:29:07.120> then<00:29:07.540> we<00:29:07.990> would<00:29:08.200> just<00:29:08.260> again 00:29:08.909 --> 00:29:08.919 align:start position:0% have now and then we would just again 00:29:08.919 --> 00:29:10.770 align:start position:0% have now and then we would just again how<00:29:09.400> in<00:29:09.520> that<00:29:09.730> bed<00:29:09.910> from<00:29:10.059> that<00:29:10.210> table<00:29:10.600> and 00:29:10.770 --> 00:29:10.780 align:start position:0% how in that bed from that table and 00:29:10.780 --> 00:29:14.100 align:start position:0% how in that bed from that table and wrote<00:29:10.960> a<00:29:11.230> new<00:29:11.380> table<00:29:11.620> and<00:29:11.980> then<00:29:12.669> it<00:29:13.660> would<00:29:13.870> know 00:29:14.100 --> 00:29:14.110 align:start position:0% wrote a new table and then it would know 00:29:14.110 --> 00:29:16.710 align:start position:0% wrote a new table and then it would know to<00:29:14.169> compute<00:29:14.770> the<00:29:14.890> new<00:29:15.040> table<00:29:15.490> so<00:29:16.270> the<00:29:16.480> the 00:29:16.710 --> 00:29:16.720 align:start position:0% to compute the new table so the the 00:29:16.720 --> 00:29:18.240 align:start position:0% to compute the new table so the the first<00:29:16.750> table<00:29:17.140> that<00:29:17.470> I<00:29:17.500> described<00:29:17.980> would<00:29:18.100> have 00:29:18.240 --> 00:29:18.250 align:start position:0% first table that I described would have 00:29:18.250 --> 00:29:20.640 align:start position:0% first table that I described would have all<00:29:18.490> of<00:29:18.700> the<00:29:18.850> things<00:29:19.030> back<00:29:19.780> to<00:29:19.900> get<00:29:20.049> viewer<00:29:20.350> and 00:29:20.640 --> 00:29:20.650 align:start position:0% all of the things back to get viewer and 00:29:20.650 --> 00:29:22.140 align:start position:0% all of the things back to get viewer and then<00:29:20.799> the<00:29:21.040> secondary<00:29:21.669> table<00:29:21.850> get 00:29:22.140 --> 00:29:22.150 align:start position:0% then the secondary table get 00:29:22.150 --> 00:29:24.090 align:start position:0% then the secondary table get communicated<00:29:22.600> so<00:29:23.200> you<00:29:23.470> can<00:29:23.620> write<00:29:23.860> off<00:29:24.070> your 00:29:24.090 --> 00:29:24.100 align:start position:0% communicated so you can write off your 00:29:24.100 --> 00:29:26.040 align:start position:0% communicated so you can write off your thing<00:29:24.340> that<00:29:24.429> I<00:29:24.460> just<00:29:24.640> described<00:29:25.030> and<00:29:25.270> login 00:29:26.040 --> 00:29:26.050 align:start position:0% thing that I just described and login 00:29:26.050 --> 00:29:28.500 align:start position:0% thing that I just described and login do<00:29:26.410> all<00:29:26.620> these<00:29:26.770> things<00:29:26.830> in<00:29:27.160> plugins<00:29:27.550> and 00:29:28.500 --> 00:29:28.510 align:start position:0% do all these things in plugins and 00:29:28.510 --> 00:29:29.790 align:start position:0% do all these things in plugins and that's<00:29:28.750> sort<00:29:28.960> of<00:29:29.080> I<00:29:29.290> mean<00:29:29.410> that's<00:29:29.650> how<00:29:29.740> we 00:29:29.790 --> 00:29:29.800 align:start position:0% that's sort of I mean that's how we 00:29:29.800 --> 00:29:31.650 align:start position:0% that's sort of I mean that's how we would<00:29:30.040> have<00:29:30.160> to<00:29:30.310> trust<00:29:30.520> that<00:29:30.670> but<00:29:31.390> yeah<00:29:31.540> I<00:29:31.570> mean 00:29:31.650 --> 00:29:31.660 align:start position:0% would have to trust that but yeah I mean 00:29:31.660 --> 00:29:33.750 align:start position:0% would have to trust that but yeah I mean when<00:29:32.410> I<00:29:32.440> designed<00:29:32.950> the<00:29:33.040> system<00:29:33.160> originally<00:29:33.610> I 00:29:33.750 --> 00:29:33.760 align:start position:0% when I designed the system originally I 00:29:33.760 --> 00:29:35.670 align:start position:0% when I designed the system originally I thought<00:29:33.970> most<00:29:34.270> of<00:29:34.480> the<00:29:34.600> utility<00:29:35.080> would<00:29:35.260> be<00:29:35.410> in 00:29:35.670 --> 00:29:35.680 align:start position:0% thought most of the utility would be in 00:29:35.680 --> 00:29:39.210 align:start position:0% thought most of the utility would be in reduce<00:29:37.230> that's<00:29:38.230> just<00:29:38.410> not<00:29:38.590> the<00:29:39.040> way<00:29:39.190> that 00:29:39.210 --> 00:29:39.220 align:start position:0% reduce that's just not the way that 00:29:39.220 --> 00:29:43.830 align:start position:0% reduce that's just not the way that development<00:29:39.790> happened<00:29:40.270> to<00:29:40.360> go<00:29:41.550> yeah<00:29:42.550> that<00:29:42.880> I 00:29:43.830 --> 00:29:43.840 align:start position:0% development happened to go yeah that I 00:29:43.840 --> 00:29:45.650 align:start position:0% development happened to go yeah that I knew<00:29:43.990> was<00:29:44.170> the<00:29:44.200> nation<00:29:44.530> of<00:29:44.650> if<00:29:44.770> you<00:29:44.920> go<00:29:45.250> to 00:29:45.650 --> 00:29:45.660 align:start position:0% knew was the nation of if you go to 00:29:45.660 --> 00:29:52.320 align:start position:0% knew was the nation of if you go to coastal<00:29:46.660> state<00:29:46.870> changes<00:29:50.670> yes<00:29:51.670> so<00:29:51.880> I<00:29:51.970> mean<00:29:52.150> that 00:29:52.320 --> 00:29:52.330 align:start position:0% coastal state changes yes so I mean that 00:29:52.330 --> 00:29:54.270 align:start position:0% coastal state changes yes so I mean that that's<00:29:52.660> work<00:29:52.870> that<00:29:52.900> happens<00:29:53.500> in<00:29:53.770> plugins 00:29:54.270 --> 00:29:54.280 align:start position:0% that's work that happens in plugins 00:29:54.280 --> 00:29:57.000 align:start position:0% that's work that happens in plugins because<00:29:54.520> we're<00:29:54.850> actively<00:29:55.410> trying<00:29:56.410> to<00:29:56.560> sort<00:29:56.950> of 00:29:57.000 --> 00:29:57.010 align:start position:0% because we're actively trying to sort of 00:29:57.010 --> 00:29:58.410 align:start position:0% because we're actively trying to sort of figure<00:29:57.160> out<00:29:57.370> like<00:29:57.610> how<00:29:57.790> can<00:29:58.000> either<00:29:58.240> leave 00:29:58.410 --> 00:29:58.420 align:start position:0% figure out like how can either leave 00:29:58.420 --> 00:30:00.270 align:start position:0% figure out like how can either leave this<00:29:58.540> automatically<00:29:59.140> or<00:29:59.350> ask<00:29:59.830> you<00:30:00.070> to<00:30:00.130> write 00:30:00.270 --> 00:30:00.280 align:start position:0% this automatically or ask you to write 00:30:00.280 --> 00:30:02.010 align:start position:0% this automatically or ask you to write like<00:30:00.460> the<00:30:00.640> fair<00:30:00.970> minimum<00:30:01.420> of<00:30:01.540> code<00:30:01.720> do<00:30:01.900> you 00:30:02.010 --> 00:30:02.020 align:start position:0% like the fair minimum of code do you 00:30:02.020 --> 00:30:04.770 align:start position:0% like the fair minimum of code do you need<00:30:02.170> to<00:30:02.460> to<00:30:03.460> make<00:30:03.490> that<00:30:03.760> happen 00:30:04.770 --> 00:30:04.780 align:start position:0% need to to make that happen 00:30:04.780 --> 00:30:07.020 align:start position:0% need to to make that happen but<00:30:05.200> in<00:30:05.440> a<00:30:05.500> nutshell<00:30:05.950> the<00:30:06.340> way<00:30:06.430> it<00:30:06.490> works<00:30:06.730> is 00:30:07.020 --> 00:30:07.030 align:start position:0% but in a nutshell the way it works is 00:30:07.030 --> 00:30:10.410 align:start position:0% but in a nutshell the way it works is that<00:30:07.060> you<00:30:07.450> have<00:30:08.140> a<00:30:08.170> mapping<00:30:08.500> of<00:30:09.060> given<00:30:10.060> storage 00:30:10.410 --> 00:30:10.420 align:start position:0% that you have a mapping of given storage 00:30:10.420 --> 00:30:13.920 align:start position:0% that you have a mapping of given storage keys<00:30:10.900> to<00:30:11.560> given<00:30:12.070> contract<00:30:12.550> values<00:30:13.000> Frank<00:30:13.690> so 00:30:13.920 --> 00:30:13.930 align:start position:0% keys to given contract values Frank so 00:30:13.930 --> 00:30:16.920 align:start position:0% keys to given contract values Frank so that's<00:30:14.290> pretty<00:30:14.860> straightforward<00:30:15.340> for<00:30:16.300> static 00:30:16.920 --> 00:30:16.930 align:start position:0% that's pretty straightforward for static 00:30:16.930 --> 00:30:18.780 align:start position:0% that's pretty straightforward for static values<00:30:17.380> on<00:30:17.530> contracts<00:30:18.220> like<00:30:18.340> it's<00:30:18.520> literally 00:30:18.780 --> 00:30:18.790 align:start position:0% values on contracts like it's literally 00:30:18.790 --> 00:30:20.220 align:start position:0% values on contracts like it's literally just<00:30:19.000> like<00:30:19.150> the<00:30:19.300> index<00:30:19.630> the<00:30:19.780> value<00:30:20.020> on<00:30:20.140> the 00:30:20.220 --> 00:30:20.230 align:start position:0% just like the index the value on the 00:30:20.230 --> 00:30:21.660 align:start position:0% just like the index the value on the contracts<00:30:20.650> you<00:30:20.830> can<00:30:20.980> have<00:30:21.070> a<00:30:21.100> mapping<00:30:21.310> looks 00:30:21.660 --> 00:30:21.670 align:start position:0% contracts you can have a mapping looks 00:30:21.670 --> 00:30:25.050 align:start position:0% contracts you can have a mapping looks like<00:30:21.850> index<00:30:22.630> one<00:30:22.900> is<00:30:23.260> you<00:30:23.650> know<00:30:23.770> the<00:30:24.700> total 00:30:25.050 --> 00:30:25.060 align:start position:0% like index one is you know the total 00:30:25.060 --> 00:30:28.320 align:start position:0% like index one is you know the total supply<00:30:25.180> or<00:30:25.540> whatever<00:30:26.430> but<00:30:27.430> it<00:30:27.700> gets<00:30:27.910> a<00:30:28.150> little 00:30:28.320 --> 00:30:28.330 align:start position:0% supply or whatever but it gets a little 00:30:28.330 --> 00:30:29.850 align:start position:0% supply or whatever but it gets a little bit<00:30:28.600> more<00:30:28.810> interesting<00:30:29.320> when<00:30:29.530> you<00:30:29.620> start 00:30:29.850 --> 00:30:29.860 align:start position:0% bit more interesting when you start 00:30:29.860 --> 00:30:31.770 align:start position:0% bit more interesting when you start dealing<00:30:30.130> with<00:30:30.280> like<00:30:30.610> mappings<00:30:31.120> and<00:30:31.360> dynamic 00:30:31.770 --> 00:30:31.780 align:start position:0% dealing with like mappings and dynamic 00:30:31.780 --> 00:30:33.960 align:start position:0% dealing with like mappings and dynamic arrays<00:30:32.080> because<00:30:32.470> generating<00:30:33.340> storage<00:30:33.700> keys 00:30:33.960 --> 00:30:33.970 align:start position:0% arrays because generating storage keys 00:30:33.970 --> 00:30:35.580 align:start position:0% arrays because generating storage keys for<00:30:34.240> that<00:30:34.270> generally<00:30:34.870> dependence<00:30:35.380> on 00:30:35.580 --> 00:30:35.590 align:start position:0% for that generally dependence on 00:30:35.590 --> 00:30:38.190 align:start position:0% for that generally dependence on secondary<00:30:36.190> data<00:30:36.490> as<00:30:36.640> to<00:30:36.820> like<00:30:37.000> an<00:30:37.120> address<00:30:37.390> to 00:30:38.190 --> 00:30:38.200 align:start position:0% secondary data as to like an address to 00:30:38.200 --> 00:30:41.760 align:start position:0% secondary data as to like an address to map<00:30:38.410> to<00:30:38.620> balances<00:30:39.190> or<00:30:39.310> whatever<00:30:39.550> and<00:30:39.910> so<00:30:40.770> the 00:30:41.760 --> 00:30:41.770 align:start position:0% map to balances or whatever and so the 00:30:41.770 --> 00:30:44.250 align:start position:0% map to balances or whatever and so the way<00:30:41.950> that<00:30:41.980> we're<00:30:42.520> looking<00:30:42.730> at<00:30:43.180> doing<00:30:43.630> that<00:30:43.930> is 00:30:44.250 --> 00:30:44.260 align:start position:0% way that we're looking at doing that is 00:30:44.260 --> 00:30:46.650 align:start position:0% way that we're looking at doing that is basically<00:30:44.710> you<00:30:45.100> flag<00:30:45.430> some<00:30:45.790> events<00:30:46.210> as<00:30:46.390> like 00:30:46.650 --> 00:30:46.660 align:start position:0% basically you flag some events as like 00:30:46.660 --> 00:30:48.480 align:start position:0% basically you flag some events as like these<00:30:46.930> have<00:30:47.230> addresses<00:30:47.650> that<00:30:48.010> I<00:30:48.040> know<00:30:48.160> for 00:30:48.480 --> 00:30:48.490 align:start position:0% these have addresses that I know for 00:30:48.490 --> 00:30:50.640 align:start position:0% these have addresses that I know for sure<00:30:48.550> are<00:30:49.360> going<00:30:49.480> to<00:30:49.540> be<00:30:49.660> in<00:30:49.750> this<00:30:49.900> mapping<00:30:50.380> and 00:30:50.640 --> 00:30:50.650 align:start position:0% sure are going to be in this mapping and 00:30:50.650 --> 00:30:52.650 align:start position:0% sure are going to be in this mapping and then<00:30:51.070> will<00:30:51.310> like<00:30:51.460> automatically<00:30:52.150> based<00:30:52.420> on 00:30:52.650 --> 00:30:52.660 align:start position:0% then will like automatically based on 00:30:52.660 --> 00:30:54.450 align:start position:0% then will like automatically based on the<00:30:52.780> index<00:30:53.140> of<00:30:53.350> the<00:30:53.440> mapping<00:30:53.800> generate<00:30:54.280> the 00:30:54.450 --> 00:30:54.460 align:start position:0% the index of the mapping generate the 00:30:54.460 --> 00:30:54.960 align:start position:0% the index of the mapping generate the keys 00:30:54.960 --> 00:30:54.970 align:start position:0% keys 00:30:54.970 --> 00:30:56.550 align:start position:0% keys based<00:30:55.150> on<00:30:55.330> hashing<00:30:55.720> that<00:30:55.870> address<00:30:56.170> with<00:30:56.440> the 00:30:56.550 --> 00:30:56.560 align:start position:0% based on hashing that address with the 00:30:56.560 --> 00:30:59.100 align:start position:0% based on hashing that address with the index<00:30:56.940> such<00:30:57.940> that<00:30:58.210> you<00:30:58.330> can<00:30:58.480> recognize<00:30:58.780> like 00:30:59.100 --> 00:30:59.110 align:start position:0% index such that you can recognize like 00:30:59.110 --> 00:31:01.710 align:start position:0% index such that you can recognize like all<00:30:59.380> of<00:30:59.590> the<00:30:59.770> storage<00:31:00.070> dips<00:31:00.460> that<00:31:00.730> are<00:31:01.360> coming 00:31:01.710 --> 00:31:01.720 align:start position:0% all of the storage dips that are coming 00:31:01.720 --> 00:31:05.670 align:start position:0% all of the storage dips that are coming off<00:31:01.870> of<00:31:01.930> a<00:31:02.200> contract<00:31:02.740> after<00:31:03.390> a<00:31:04.390> given<00:31:05.290> event 00:31:05.670 --> 00:31:05.680 align:start position:0% off of a contract after a given event 00:31:05.680 --> 00:31:08.070 align:start position:0% off of a contract after a given event has<00:31:06.040> been<00:31:06.190> sync<00:31:06.490> and<00:31:06.670> then<00:31:07.060> you<00:31:07.270> know<00:31:07.390> after 00:31:08.070 --> 00:31:08.080 align:start position:0% has been sync and then you know after 00:31:08.080 --> 00:31:09.840 align:start position:0% has been sync and then you know after you<00:31:08.170> know<00:31:08.320> like<00:31:08.560> what<00:31:08.800> it<00:31:08.920> maps<00:31:09.160> to<00:31:09.310> it's<00:31:09.670> a 00:31:09.840 --> 00:31:09.850 align:start position:0% you know like what it maps to it's a 00:31:09.850 --> 00:31:11.529 align:start position:0% you know like what it maps to it's a pretty<00:31:10.630> trivial 00:31:11.529 --> 00:31:11.539 align:start position:0% pretty trivial 00:31:11.539 --> 00:31:13.930 align:start position:0% pretty trivial just<00:31:11.840> like<00:31:11.989> decoding<00:31:12.590> though<00:31:12.799> the<00:31:13.519> value 00:31:13.930 --> 00:31:13.940 align:start position:0% just like decoding though the value 00:31:13.940 --> 00:31:15.789 align:start position:0% just like decoding though the value associated<00:31:14.210> with<00:31:14.479> that<00:31:14.690> storage<00:31:14.960> key<00:31:15.259> into 00:31:15.789 --> 00:31:15.799 align:start position:0% associated with that storage key into 00:31:15.799 --> 00:31:24.820 align:start position:0% associated with that storage key into the<00:31:16.009> perfect<00:31:16.639> type<00:31:21.190> cool<00:31:23.679> alrighty<00:31:24.679> well 00:31:24.820 --> 00:31:24.830 align:start position:0% the perfect type cool alrighty well 00:31:24.830 --> 00:31:26.229 align:start position:0% the perfect type cool alrighty well thank<00:31:25.039> you<00:31:25.129> so<00:31:25.279> much<00:31:25.340> for<00:31:25.609> coming<00:31:25.970> out<00:31:26.059> to 00:31:26.229 --> 00:31:26.239 align:start position:0% thank you so much for coming out to 00:31:26.239 --> 00:31:27.940 align:start position:0% thank you so much for coming out to listen<00:31:26.509> to<00:31:26.570> me<00:31:26.659> topic<00:31:27.080> and<00:31:27.229> we're<00:31:27.799> really 00:31:27.940 --> 00:31:27.950 align:start position:0% listen to me topic and we're really 00:31:27.950 --> 00:31:29.409 align:start position:0% listen to me topic and we're really excited<00:31:28.100> about<00:31:28.399> this<00:31:28.669> work<00:31:28.879> and<00:31:29.059> hope<00:31:29.239> that<00:31:29.389> I 00:31:29.409 --> 00:31:29.419 align:start position:0% excited about this work and hope that I 00:31:29.419 --> 00:31:30.549 align:start position:0% excited about this work and hope that I can<00:31:29.629> provide<00:31:29.779> a<00:31:29.899> lot<00:31:30.019> of<00:31:30.080> value<00:31:30.200> for<00:31:30.409> the 00:31:30.549 --> 00:31:30.559 align:start position:0% can provide a lot of value for the 00:31:30.559 --> 00:31:35.150 align:start position:0% can provide a lot of value for the community<00:31:30.710> and<00:31:31.279> totally<00:31:31.700> open<00:31:31.909> source 00:31:35.150 --> 00:31:35.160 align:start position:0% 00:31:35.160 --> 00:31:42.420 align:start position:0% [Applause]