WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:15.849 align:start position:0% [Music] 00:00:15.849 --> 00:00:15.859 align:start position:0% 00:00:15.859 --> 00:00:19.189 align:start position:0% Workshop<00:00:16.940> about<00:00:17.940> running<00:00:18.300> the<00:00:18.720> beaten<00:00:19.080> chain 00:00:19.189 --> 00:00:19.199 align:start position:0% Workshop about running the beaten chain 00:00:19.199 --> 00:00:22.130 align:start position:0% Workshop about running the beaten chain Explorer<00:00:19.619> on<00:00:19.920> your<00:00:20.039> own 00:00:22.130 --> 00:00:22.140 align:start position:0% Explorer on your own 00:00:22.140 --> 00:00:24.769 align:start position:0% Explorer on your own um<00:00:22.260> we<00:00:22.859> will<00:00:23.100> go<00:00:23.520> through 00:00:24.769 --> 00:00:24.779 align:start position:0% um we will go through 00:00:24.779 --> 00:00:27.589 align:start position:0% um we will go through how<00:00:25.439> we<00:00:25.619> came<00:00:25.920> to<00:00:26.100> the<00:00:26.279> idea<00:00:26.699> to<00:00:27.240> make<00:00:27.359> the 00:00:27.589 --> 00:00:27.599 align:start position:0% how we came to the idea to make the 00:00:27.599 --> 00:00:29.990 align:start position:0% how we came to the idea to make the beginning<00:00:27.800> chain<00:00:28.800> Explorer<00:00:29.340> and<00:00:29.760> then<00:00:29.880> we 00:00:29.990 --> 00:00:30.000 align:start position:0% beginning chain Explorer and then we 00:00:30.000 --> 00:00:32.030 align:start position:0% beginning chain Explorer and then we will<00:00:30.180> explain<00:00:30.359> how<00:00:30.840> we<00:00:31.019> how<00:00:31.500> you<00:00:31.740> can<00:00:31.859> actually 00:00:32.030 --> 00:00:32.040 align:start position:0% will explain how we how you can actually 00:00:32.040 --> 00:00:34.670 align:start position:0% will explain how we how you can actually run<00:00:32.340> the<00:00:32.640> beacon<00:00:33.000> chain<00:00:33.120> Explorer<00:00:33.600> we<00:00:34.260> this<00:00:34.559> is 00:00:34.670 --> 00:00:34.680 align:start position:0% run the beacon chain Explorer we this is 00:00:34.680 --> 00:00:35.690 align:start position:0% run the beacon chain Explorer we this is Stefan 00:00:35.690 --> 00:00:35.700 align:start position:0% Stefan 00:00:35.700 --> 00:00:38.630 align:start position:0% Stefan my<00:00:36.180> colleague<00:00:36.660> and<00:00:37.260> me<00:00:37.440> Patrick 00:00:38.630 --> 00:00:38.640 align:start position:0% my colleague and me Patrick 00:00:38.640 --> 00:00:41.330 align:start position:0% my colleague and me Patrick we<00:00:39.180> both<00:00:39.420> work<00:00:39.660> for<00:00:39.960> the<00:00:40.079> company<00:00:40.200> pit<00:00:40.620> plan 00:00:41.330 --> 00:00:41.340 align:start position:0% we both work for the company pit plan 00:00:41.340 --> 00:00:44.049 align:start position:0% we both work for the company pit plan so<00:00:41.760> yeah<00:00:41.940> first<00:00:42.360> we<00:00:42.660> are 00:00:44.049 --> 00:00:44.059 align:start position:0% so yeah first we are 00:00:44.059 --> 00:00:46.970 align:start position:0% so yeah first we are Stefan<00:00:45.059> will<00:00:45.180> introduce<00:00:45.719> you 00:00:46.970 --> 00:00:46.980 align:start position:0% Stefan will introduce you 00:00:46.980 --> 00:00:50.209 align:start position:0% Stefan will introduce you to<00:00:47.180> our<00:00:48.180> company<00:00:48.420> and<00:00:49.140> how<00:00:49.320> we<00:00:49.620> actually<00:00:49.920> came 00:00:50.209 --> 00:00:50.219 align:start position:0% to our company and how we actually came 00:00:50.219 --> 00:00:53.389 align:start position:0% to our company and how we actually came to<00:00:50.399> the<00:00:50.579> idea<00:00:50.879> to<00:00:51.300> make<00:00:51.600> and<00:00:52.440> explore<00:00:52.980> to<00:00:53.219> the 00:00:53.389 --> 00:00:53.399 align:start position:0% to the idea to make and explore to the 00:00:53.399 --> 00:00:56.209 align:start position:0% to the idea to make and explore to the for<00:00:53.879> the<00:00:54.120> next<00:00:54.960> stage<00:00:55.260> of<00:00:55.500> the<00:00:55.680> ethereum 00:00:56.209 --> 00:00:56.219 align:start position:0% for the next stage of the ethereum 00:00:56.219 --> 00:00:57.350 align:start position:0% for the next stage of the ethereum project 00:00:57.350 --> 00:00:57.360 align:start position:0% project 00:00:57.360 --> 00:00:59.930 align:start position:0% project then<00:00:57.840> we<00:00:58.079> go<00:00:58.440> briefly<00:00:58.920> into<00:00:59.100> the<00:00:59.399> through<00:00:59.760> the 00:00:59.930 --> 00:00:59.940 align:start position:0% then we go briefly into the through the 00:00:59.940 --> 00:01:03.110 align:start position:0% then we go briefly into the through the architecture<00:01:00.899> of<00:01:01.559> the<00:01:01.739> project<00:01:01.920> and<00:01:02.820> finally 00:01:03.110 --> 00:01:03.120 align:start position:0% architecture of the project and finally 00:01:03.120 --> 00:01:05.270 align:start position:0% architecture of the project and finally we<00:01:03.780> will<00:01:03.960> show<00:01:04.140> how<00:01:04.559> you<00:01:04.680> can<00:01:04.860> run<00:01:05.040> the 00:01:05.270 --> 00:01:05.280 align:start position:0% we will show how you can run the 00:01:05.280 --> 00:01:08.270 align:start position:0% we will show how you can run the Explorer<00:01:05.640> on<00:01:05.760> your<00:01:05.939> own 00:01:08.270 --> 00:01:08.280 align:start position:0% 00:01:08.280 --> 00:01:11.929 align:start position:0% but<00:01:09.119> before<00:01:09.360> we<00:01:10.140> start<00:01:10.320> with<00:01:10.619> anything 00:01:11.929 --> 00:01:11.939 align:start position:0% but before we start with anything 00:01:11.939 --> 00:01:13.969 align:start position:0% but before we start with anything everyone<00:01:12.540> who<00:01:13.140> everyone<00:01:13.439> who<00:01:13.680> wants<00:01:13.920> to 00:01:13.969 --> 00:01:13.979 align:start position:0% everyone who everyone who wants to 00:01:13.979 --> 00:01:17.390 align:start position:0% everyone who everyone who wants to participate<00:01:14.540> like<00:01:15.540> interactively<00:01:16.320> we<00:01:17.220> need 00:01:17.390 --> 00:01:17.400 align:start position:0% participate like interactively we need 00:01:17.400 --> 00:01:22.070 align:start position:0% participate like interactively we need you<00:01:17.780> sorry<00:01:18.780> I<00:01:19.740> was<00:01:19.920> on<00:01:19.979> the<00:01:20.159> wrong<00:01:20.280> laptop 00:01:22.070 --> 00:01:22.080 align:start position:0% you sorry I was on the wrong laptop 00:01:22.080 --> 00:01:24.289 align:start position:0% you sorry I was on the wrong laptop yeah 00:01:24.289 --> 00:01:24.299 align:start position:0% yeah 00:01:24.299 --> 00:01:27.410 align:start position:0% yeah we<00:01:24.659> will<00:01:24.840> go<00:01:25.020> first<00:01:25.259> to<00:01:25.680> how<00:01:26.340> we<00:01:26.520> came<00:01:26.880> to<00:01:27.119> the 00:01:27.410 --> 00:01:27.420 align:start position:0% we will go first to how we came to the 00:01:27.420 --> 00:01:30.770 align:start position:0% we will go first to how we came to the beginning<00:01:27.780> expert<00:01:28.740> and<00:01:29.299> what<00:01:30.299> what<00:01:30.540> the 00:01:30.770 --> 00:01:30.780 align:start position:0% beginning expert and what what the 00:01:30.780 --> 00:01:32.570 align:start position:0% beginning expert and what what the architecture<00:01:31.259> of<00:01:31.439> the<00:01:31.560> project<00:01:31.680> look<00:01:32.040> looks 00:01:32.570 --> 00:01:32.580 align:start position:0% architecture of the project look looks 00:01:32.580 --> 00:01:34.910 align:start position:0% architecture of the project look looks like<00:01:32.640> and<00:01:33.299> finally<00:01:33.659> we<00:01:34.380> will<00:01:34.500> show<00:01:34.619> you<00:01:34.740> how 00:01:34.910 --> 00:01:34.920 align:start position:0% like and finally we will show you how 00:01:34.920 --> 00:01:37.130 align:start position:0% like and finally we will show you how you<00:01:35.040> run<00:01:35.220> the<00:01:35.400> Explorer<00:01:35.820> but<00:01:36.240> before<00:01:36.360> we<00:01:36.659> go<00:01:36.900> to 00:01:37.130 --> 00:01:37.140 align:start position:0% you run the Explorer but before we go to 00:01:37.140 --> 00:01:40.010 align:start position:0% you run the Explorer but before we go to anything<00:01:37.439> we<00:01:38.340> need<00:01:38.520> you<00:01:38.820> anyone<00:01:39.479> who<00:01:39.659> wants<00:01:39.900> to 00:01:40.010 --> 00:01:40.020 align:start position:0% anything we need you anyone who wants to 00:01:40.020 --> 00:01:43.490 align:start position:0% anything we need you anyone who wants to participate<00:01:40.500> we<00:01:40.740> need<00:01:40.920> you<00:01:41.100> to<00:01:41.280> to<00:01:42.180> download<00:01:42.840> a 00:01:43.490 --> 00:01:43.500 align:start position:0% participate we need you to to download a 00:01:43.500 --> 00:01:44.390 align:start position:0% participate we need you to to download a few<00:01:43.619> things 00:01:44.390 --> 00:01:44.400 align:start position:0% few things 00:01:44.400 --> 00:01:45.649 align:start position:0% few things so 00:01:45.649 --> 00:01:45.659 align:start position:0% so 00:01:45.659 --> 00:01:48.170 align:start position:0% so are<00:01:46.259> there<00:01:46.439> any<00:01:46.680> anyone<00:01:47.159> who<00:01:47.460> wants<00:01:48.119> to 00:01:48.170 --> 00:01:48.180 align:start position:0% are there any anyone who wants to 00:01:48.180 --> 00:01:51.350 align:start position:0% are there any anyone who wants to participate<00:01:48.600> on<00:01:49.259> this<00:01:49.380> laptop 00:01:51.350 --> 00:01:51.360 align:start position:0% participate on this laptop 00:01:51.360 --> 00:01:53.749 align:start position:0% participate on this laptop um<00:01:51.479> do<00:01:51.659> we<00:01:51.840> have<00:01:51.960> install<00:01:52.380> Docker<00:01:53.100> in<00:01:53.399> Docker 00:01:53.749 --> 00:01:53.759 align:start position:0% um do we have install Docker in Docker 00:01:53.759 --> 00:01:57.350 align:start position:0% um do we have install Docker in Docker compose 00:01:57.350 --> 00:01:57.360 align:start position:0% 00:01:57.360 --> 00:01:59.929 align:start position:0% so<00:01:57.960> can<00:01:58.200> you<00:01:58.380> basically<00:01:58.920> try<00:01:59.159> and<00:01:59.340> see<00:01:59.520> if<00:01:59.759> you 00:01:59.929 --> 00:01:59.939 align:start position:0% so can you basically try and see if you 00:01:59.939 --> 00:02:02.030 align:start position:0% so can you basically try and see if you can<00:02:00.060> access<00:02:00.360> the<00:02:00.659> repository<00:02:01.200> if<00:02:01.619> we<00:02:01.740> made<00:02:01.920> it 00:02:02.030 --> 00:02:02.040 align:start position:0% can access the repository if we made it 00:02:02.040 --> 00:02:02.870 align:start position:0% can access the repository if we made it public 00:02:02.870 --> 00:02:02.880 align:start position:0% public 00:02:02.880 --> 00:02:04.310 align:start position:0% public or<00:02:03.240> not 00:02:04.310 --> 00:02:04.320 align:start position:0% or not 00:02:04.320 --> 00:02:05.569 align:start position:0% or not yeah<00:02:04.560> then 00:02:05.569 --> 00:02:05.579 align:start position:0% yeah then 00:02:05.579 --> 00:02:08.330 align:start position:0% yeah then I'll<00:02:06.060> quickly<00:02:06.540> we'll<00:02:06.899> jump<00:02:07.140> back<00:02:07.320> to<00:02:07.500> that 00:02:08.330 --> 00:02:08.340 align:start position:0% I'll quickly we'll jump back to that 00:02:08.340 --> 00:02:11.510 align:start position:0% I'll quickly we'll jump back to that and<00:02:08.880> I'll<00:02:09.060> quickly<00:02:09.479> introduce<00:02:10.220> kind<00:02:11.220> of<00:02:11.400> who 00:02:11.510 --> 00:02:11.520 align:start position:0% and I'll quickly introduce kind of who 00:02:11.520 --> 00:02:13.490 align:start position:0% and I'll quickly introduce kind of who we<00:02:11.700> are<00:02:11.879> a<00:02:12.180> bit<00:02:12.360> more<00:02:12.480> in<00:02:12.660> detail 00:02:13.490 --> 00:02:13.500 align:start position:0% we are a bit more in detail 00:02:13.500 --> 00:02:17.089 align:start position:0% we are a bit more in detail so<00:02:14.819> um<00:02:14.879> the<00:02:15.660> company<00:02:15.900> bitfly<00:02:16.440> was<00:02:16.739> founded 00:02:17.089 --> 00:02:17.099 align:start position:0% so um the company bitfly was founded 00:02:17.099 --> 00:02:20.990 align:start position:0% so um the company bitfly was founded 2017<00:02:17.819> and<00:02:18.660> we've<00:02:18.959> done<00:02:19.200> a<00:02:19.500> range<00:02:19.680> of<00:02:19.800> products 00:02:20.990 --> 00:02:21.000 align:start position:0% 2017 and we've done a range of products 00:02:21.000 --> 00:02:23.510 align:start position:0% 2017 and we've done a range of products um the<00:02:21.780> we've<00:02:22.379> been<00:02:22.440> basically<00:02:22.860> active<00:02:23.220> since 00:02:23.510 --> 00:02:23.520 align:start position:0% um the we've been basically active since 00:02:23.520 --> 00:02:25.190 align:start position:0% um the we've been basically active since the<00:02:23.700> beginning<00:02:23.819> of<00:02:24.120> ethereum<00:02:24.599> in<00:02:24.900> this<00:02:25.020> space 00:02:25.190 --> 00:02:25.200 align:start position:0% the beginning of ethereum in this space 00:02:25.200 --> 00:02:27.770 align:start position:0% the beginning of ethereum in this space we<00:02:26.040> actually<00:02:26.220> created<00:02:26.819> one<00:02:27.480> of<00:02:27.540> the<00:02:27.660> first 00:02:27.770 --> 00:02:27.780 align:start position:0% we actually created one of the first 00:02:27.780 --> 00:02:30.350 align:start position:0% we actually created one of the first block<00:02:28.140> explorers<00:02:28.800> but<00:02:29.459> kind<00:02:29.640> of<00:02:29.700> let<00:02:29.819> it<00:02:30.060> slack 00:02:30.350 --> 00:02:30.360 align:start position:0% block explorers but kind of let it slack 00:02:30.360 --> 00:02:32.630 align:start position:0% block explorers but kind of let it slack a<00:02:30.480> bit<00:02:30.599> so<00:02:31.080> that<00:02:31.260> was<00:02:31.459> etherchain.org<00:02:32.459> it's 00:02:32.630 --> 00:02:32.640 align:start position:0% a bit so that was etherchain.org it's 00:02:32.640 --> 00:02:34.850 align:start position:0% a bit so that was etherchain.org it's one<00:02:32.819> of<00:02:32.940> the<00:02:33.000> older<00:02:33.300> ones<00:02:33.599> and<00:02:34.319> then<00:02:34.379> later<00:02:34.620> on 00:02:34.850 --> 00:02:34.860 align:start position:0% one of the older ones and then later on 00:02:34.860 --> 00:02:36.830 align:start position:0% one of the older ones and then later on we<00:02:35.220> kind<00:02:35.400> of<00:02:35.520> regretted<00:02:36.060> not<00:02:36.360> putting<00:02:36.720> more 00:02:36.830 --> 00:02:36.840 align:start position:0% we kind of regretted not putting more 00:02:36.840 --> 00:02:39.110 align:start position:0% we kind of regretted not putting more effort<00:02:37.140> into<00:02:37.440> that<00:02:38.040> Explorer<00:02:38.580> and<00:02:38.700> then<00:02:38.879> we 00:02:39.110 --> 00:02:39.120 align:start position:0% effort into that Explorer and then we 00:02:39.120 --> 00:02:42.050 align:start position:0% effort into that Explorer and then we kind<00:02:39.900> of<00:02:40.020> decided<00:02:40.560> now<00:02:40.920> that<00:02:41.220> there's<00:02:41.580> uh 00:02:42.050 --> 00:02:42.060 align:start position:0% kind of decided now that there's uh 00:02:42.060 --> 00:02:44.750 align:start position:0% kind of decided now that there's uh gonna<00:02:42.300> be<00:02:42.480> ethereum<00:02:43.260> 2.0<00:02:43.800> or 00:02:44.750 --> 00:02:44.760 align:start position:0% gonna be ethereum 2.0 or 00:02:44.760 --> 00:02:47.089 align:start position:0% gonna be ethereum 2.0 or um<00:02:44.819> basically<00:02:45.599> the<00:02:45.840> merge<00:02:46.200> we<00:02:46.560> decided<00:02:46.980> to 00:02:47.089 --> 00:02:47.099 align:start position:0% um basically the merge we decided to 00:02:47.099 --> 00:02:49.070 align:start position:0% um basically the merge we decided to create<00:02:47.459> another<00:02:47.700> Explorer<00:02:48.300> specifically<00:02:48.840> for 00:02:49.070 --> 00:02:49.080 align:start position:0% create another Explorer specifically for 00:02:49.080 --> 00:02:52.729 align:start position:0% create another Explorer specifically for phase<00:02:49.379> zero<00:02:49.940> and<00:02:50.940> that<00:02:51.120> Explorer<00:02:51.680> kind<00:02:52.680> of 00:02:52.729 --> 00:02:52.739 align:start position:0% phase zero and that Explorer kind of 00:02:52.739 --> 00:02:54.710 align:start position:0% phase zero and that Explorer kind of ended<00:02:53.099> up<00:02:53.220> being<00:02:53.400> the<00:02:53.640> beacon<00:02:53.879> chain<00:02:54.060> Explorer 00:02:54.710 --> 00:02:54.720 align:start position:0% ended up being the beacon chain Explorer 00:02:54.720 --> 00:02:57.229 align:start position:0% ended up being the beacon chain Explorer and<00:02:54.900> it<00:02:55.019> started<00:02:55.319> out<00:02:55.440> where<00:02:56.099> everyone<00:02:56.400> could 00:02:57.229 --> 00:02:57.239 align:start position:0% and it started out where everyone could 00:02:57.239 --> 00:02:59.089 align:start position:0% and it started out where everyone could basically<00:02:57.599> see<00:02:57.900> all<00:02:58.080> the<00:02:58.200> information<00:02:58.379> about 00:02:59.089 --> 00:02:59.099 align:start position:0% basically see all the information about 00:02:59.099 --> 00:03:01.670 align:start position:0% basically see all the information about the<00:02:59.340> beacon<00:02:59.700> chain<00:02:59.879> uh<00:03:00.780> maybe<00:03:01.080> you<00:03:01.379> shall<00:03:01.560> of 00:03:01.670 --> 00:03:01.680 align:start position:0% the beacon chain uh maybe you shall of 00:03:01.680 --> 00:03:03.650 align:start position:0% the beacon chain uh maybe you shall of hands<00:03:01.980> who<00:03:02.220> has<00:03:02.400> used<00:03:02.580> the<00:03:02.879> Explorer<00:03:03.360> before 00:03:03.650 --> 00:03:03.660 align:start position:0% hands who has used the Explorer before 00:03:03.660 --> 00:03:06.430 align:start position:0% hands who has used the Explorer before maybe<00:03:04.620> just<00:03:04.980> to<00:03:05.160> kind<00:03:05.280> of<00:03:05.400> get<00:03:05.519> a<00:03:05.700> feel 00:03:06.430 --> 00:03:06.440 align:start position:0% maybe just to kind of get a feel 00:03:06.440 --> 00:03:09.110 align:start position:0% maybe just to kind of get a feel so<00:03:07.440> about<00:03:07.739> half<00:03:08.040> of<00:03:08.400> the<00:03:08.580> people<00:03:08.700> have<00:03:09.000> used 00:03:09.110 --> 00:03:09.120 align:start position:0% so about half of the people have used 00:03:09.120 --> 00:03:11.030 align:start position:0% so about half of the people have used the<00:03:09.300> Explorer<00:03:09.780> before 00:03:11.030 --> 00:03:11.040 align:start position:0% the Explorer before 00:03:11.040 --> 00:03:11.630 align:start position:0% the Explorer before um 00:03:11.630 --> 00:03:11.640 align:start position:0% um 00:03:11.640 --> 00:03:13.729 align:start position:0% um so<00:03:12.239> maybe<00:03:12.420> if<00:03:12.659> you<00:03:12.780> want<00:03:12.900> to<00:03:13.019> show<00:03:13.379> off<00:03:13.560> hand 00:03:13.729 --> 00:03:13.739 align:start position:0% so maybe if you want to show off hand 00:03:13.739 --> 00:03:16.729 align:start position:0% so maybe if you want to show off hand who's<00:03:14.040> running<00:03:14.400> a<00:03:14.640> validator 00:03:16.729 --> 00:03:16.739 align:start position:0% who's running a validator 00:03:16.739 --> 00:03:19.670 align:start position:0% who's running a validator okay<00:03:17.280> uh<00:03:18.239> quite<00:03:18.720> quite<00:03:19.019> a<00:03:19.140> few<00:03:19.200> of<00:03:19.379> the<00:03:19.500> people 00:03:19.670 --> 00:03:19.680 align:start position:0% okay uh quite quite a few of the people 00:03:19.680 --> 00:03:21.770 align:start position:0% okay uh quite quite a few of the people that<00:03:19.920> are<00:03:20.040> using<00:03:20.400> it 00:03:21.770 --> 00:03:21.780 align:start position:0% that are using it 00:03:21.780 --> 00:03:24.589 align:start position:0% that are using it um<00:03:21.840> so<00:03:22.319> basically<00:03:22.980> we<00:03:23.220> we<00:03:23.459> wanted<00:03:23.640> to<00:03:23.940> create<00:03:24.360> a 00:03:24.589 --> 00:03:24.599 align:start position:0% um so basically we we wanted to create a 00:03:24.599 --> 00:03:26.630 align:start position:0% um so basically we we wanted to create a nice<00:03:24.720> place<00:03:25.019> for<00:03:25.739> you<00:03:25.860> to<00:03:26.040> understand<00:03:26.220> what's 00:03:26.630 --> 00:03:26.640 align:start position:0% nice place for you to understand what's 00:03:26.640 --> 00:03:29.089 align:start position:0% nice place for you to understand what's actually<00:03:26.879> going<00:03:27.120> on<00:03:27.300> with<00:03:27.540> the<00:03:27.659> validator<00:03:28.099> uh 00:03:29.089 --> 00:03:29.099 align:start position:0% actually going on with the validator uh 00:03:29.099 --> 00:03:30.470 align:start position:0% actually going on with the validator uh to<00:03:29.459> see<00:03:29.580> the<00:03:29.760> different<00:03:29.879> states<00:03:30.120> of<00:03:30.360> the 00:03:30.470 --> 00:03:30.480 align:start position:0% to see the different states of the 00:03:30.480 --> 00:03:32.149 align:start position:0% to see the different states of the validator<00:03:30.900> to<00:03:31.260> kind<00:03:31.440> of<00:03:31.560> make<00:03:31.680> sure<00:03:31.800> you<00:03:31.980> don't 00:03:32.149 --> 00:03:32.159 align:start position:0% validator to kind of make sure you don't 00:03:32.159 --> 00:03:36.050 align:start position:0% validator to kind of make sure you don't get<00:03:32.340> slashed<00:03:32.959> and<00:03:33.959> we<00:03:34.379> also<00:03:34.620> operated<00:03:35.099> uh<00:03:35.819> one 00:03:36.050 --> 00:03:36.060 align:start position:0% get slashed and we also operated uh one 00:03:36.060 --> 00:03:37.449 align:start position:0% get slashed and we also operated uh one of<00:03:36.180> the<00:03:36.360> bigger<00:03:36.659> mining<00:03:36.959> pools<00:03:37.260> called 00:03:37.449 --> 00:03:37.459 align:start position:0% of the bigger mining pools called 00:03:37.459 --> 00:03:41.089 align:start position:0% of the bigger mining pools called ethermine.org<00:03:38.459> that<00:03:39.000> was<00:03:39.180> now<00:03:39.360> retired<00:03:40.099> since 00:03:41.089 --> 00:03:41.099 align:start position:0% ethermine.org that was now retired since 00:03:41.099 --> 00:03:43.430 align:start position:0% ethermine.org that was now retired since the<00:03:41.280> merge<00:03:41.700> and<00:03:42.060> we<00:03:42.420> kind<00:03:42.720> of<00:03:42.780> shifted<00:03:43.200> away 00:03:43.430 --> 00:03:43.440 align:start position:0% the merge and we kind of shifted away 00:03:43.440 --> 00:03:46.009 align:start position:0% the merge and we kind of shifted away from<00:03:43.980> mining<00:03:44.640> a<00:03:44.819> bit<00:03:44.940> and<00:03:45.299> focusing<00:03:45.720> we're 00:03:46.009 --> 00:03:46.019 align:start position:0% from mining a bit and focusing we're 00:03:46.019 --> 00:03:48.830 align:start position:0% from mining a bit and focusing we're focusing<00:03:46.379> a<00:03:46.560> bit<00:03:46.620> more<00:03:46.860> on<00:03:47.400> staking<00:03:47.760> so<00:03:48.180> kind 00:03:48.830 --> 00:03:48.840 align:start position:0% focusing a bit more on staking so kind 00:03:48.840 --> 00:03:51.170 align:start position:0% focusing a bit more on staking so kind of<00:03:48.959> to<00:03:49.379> chill<00:03:49.680> a<00:03:49.980> bit<00:03:50.099> our<00:03:50.340> other<00:03:50.459> products<00:03:50.940> we 00:03:51.170 --> 00:03:51.180 align:start position:0% of to chill a bit our other products we 00:03:51.180 --> 00:03:53.809 align:start position:0% of to chill a bit our other products we have<00:03:51.860> staking.ethermine.org<00:03:52.860> now<00:03:52.980> where<00:03:53.640> you 00:03:53.809 --> 00:03:53.819 align:start position:0% have staking.ethermine.org now where you 00:03:53.819 --> 00:03:56.330 align:start position:0% have staking.ethermine.org now where you can<00:03:53.879> stake<00:03:54.180> with<00:03:54.360> less<00:03:54.599> than<00:03:54.840> 32<00:03:55.799> each<00:03:55.980> and<00:03:56.220> we 00:03:56.330 --> 00:03:56.340 align:start position:0% can stake with less than 32 each and we 00:03:56.340 --> 00:03:58.430 align:start position:0% can stake with less than 32 each and we have<00:03:56.459> eat<00:03:56.640> pool<00:03:56.940> if<00:03:57.480> you're<00:03:57.599> too<00:03:57.780> lazy<00:03:58.080> to<00:03:58.319> run 00:03:58.430 --> 00:03:58.440 align:start position:0% have eat pool if you're too lazy to run 00:03:58.440 --> 00:04:00.410 align:start position:0% have eat pool if you're too lazy to run your<00:03:58.860> own<00:03:58.980> validator<00:03:59.580> you<00:03:59.879> can<00:04:00.000> just<00:04:00.120> upload 00:04:00.410 --> 00:04:00.420 align:start position:0% your own validator you can just upload 00:04:00.420 --> 00:04:02.270 align:start position:0% your own validator you can just upload your<00:04:00.599> validator<00:04:01.019> key<00:04:01.379> and<00:04:01.860> we'll<00:04:01.980> kind<00:04:02.220> of 00:04:02.270 --> 00:04:02.280 align:start position:0% your validator key and we'll kind of 00:04:02.280 --> 00:04:04.190 align:start position:0% your validator key and we'll kind of take<00:04:02.400> care<00:04:02.580> of<00:04:02.700> that<00:04:02.879> for<00:04:03.120> you 00:04:04.190 --> 00:04:04.200 align:start position:0% take care of that for you 00:04:04.200 --> 00:04:05.330 align:start position:0% take care of that for you um 00:04:05.330 --> 00:04:05.340 align:start position:0% um 00:04:05.340 --> 00:04:07.670 align:start position:0% um uh<00:04:06.060> and<00:04:06.299> then<00:04:06.360> a<00:04:06.599> brief<00:04:06.840> history<00:04:07.080> I<00:04:07.440> kind<00:04:07.620> of 00:04:07.670 --> 00:04:07.680 align:start position:0% uh and then a brief history I kind of 00:04:07.680 --> 00:04:10.309 align:start position:0% uh and then a brief history I kind of already<00:04:07.860> touched<00:04:08.280> on<00:04:08.400> that<00:04:08.640> so<00:04:09.840> um<00:04:09.840> it<00:04:10.019> started 00:04:10.309 --> 00:04:10.319 align:start position:0% already touched on that so um it started 00:04:10.319 --> 00:04:13.369 align:start position:0% already touched on that so um it started out<00:04:10.500> in<00:04:10.980> 2019<00:04:11.580> end<00:04:12.060> of<00:04:12.180> 2019<00:04:12.720> with<00:04:13.080> the<00:04:13.260> first 00:04:13.369 --> 00:04:13.379 align:start position:0% out in 2019 end of 2019 with the first 00:04:13.379 --> 00:04:16.129 align:start position:0% out in 2019 end of 2019 with the first test<00:04:13.620> networks<00:04:14.159> so<00:04:14.580> even<00:04:14.760> before 00:04:16.129 --> 00:04:16.139 align:start position:0% test networks so even before 00:04:16.139 --> 00:04:18.530 align:start position:0% test networks so even before um<00:04:16.199> the<00:04:16.500> Genesis<00:04:17.040> of<00:04:17.340> the<00:04:17.459> beacon<00:04:17.760> chain<00:04:17.940> here 00:04:18.530 --> 00:04:18.540 align:start position:0% um the Genesis of the beacon chain here 00:04:18.540 --> 00:04:20.270 align:start position:0% um the Genesis of the beacon chain here you<00:04:18.660> can<00:04:18.780> see<00:04:18.900> a<00:04:19.139> small<00:04:19.320> or<00:04:19.739> kind<00:04:20.040> of<00:04:20.100> nice 00:04:20.270 --> 00:04:20.280 align:start position:0% you can see a small or kind of nice 00:04:20.280 --> 00:04:23.270 align:start position:0% you can see a small or kind of nice picture<00:04:20.639> of<00:04:21.419> the<00:04:21.600> Genesis<00:04:22.019> event 00:04:23.270 --> 00:04:23.280 align:start position:0% picture of the Genesis event 00:04:23.280 --> 00:04:24.950 align:start position:0% picture of the Genesis event um<00:04:23.340> we<00:04:23.580> kind<00:04:23.759> of<00:04:23.880> created<00:04:24.180> like<00:04:24.360> a<00:04:24.540> slot<00:04:24.840> view 00:04:24.950 --> 00:04:24.960 align:start position:0% um we kind of created like a slot view 00:04:24.960 --> 00:04:28.070 align:start position:0% um we kind of created like a slot view so<00:04:25.440> each<00:04:26.400> one<00:04:26.580> of<00:04:26.699> those<00:04:26.820> rows<00:04:27.300> if<00:04:27.840> you<00:04:27.960> don't 00:04:28.070 --> 00:04:28.080 align:start position:0% so each one of those rows if you don't 00:04:28.080 --> 00:04:31.010 align:start position:0% so each one of those rows if you don't know<00:04:28.259> is<00:04:29.160> an<00:04:29.340> EPO<00:04:29.820> and<00:04:30.120> in<00:04:30.240> one<00:04:30.360> Epoch<00:04:30.900> there 00:04:31.010 --> 00:04:31.020 align:start position:0% know is an EPO and in one Epoch there 00:04:31.020 --> 00:04:32.749 align:start position:0% know is an EPO and in one Epoch there are<00:04:31.199> 32<00:04:31.560> slots<00:04:31.860> and<00:04:32.040> here<00:04:32.220> you<00:04:32.340> can<00:04:32.520> kind<00:04:32.639> of 00:04:32.749 --> 00:04:32.759 align:start position:0% are 32 slots and here you can kind of 00:04:32.759 --> 00:04:35.390 align:start position:0% are 32 slots and here you can kind of see<00:04:33.000> the<00:04:33.780> green<00:04:33.900> part<00:04:34.320> is<00:04:34.919> when<00:04:35.160> it<00:04:35.280> was 00:04:35.390 --> 00:04:35.400 align:start position:0% see the green part is when it was 00:04:35.400 --> 00:04:37.370 align:start position:0% see the green part is when it was proposed<00:04:35.880> the<00:04:36.000> red<00:04:36.180> one<00:04:36.360> is<00:04:36.600> when<00:04:36.780> it's<00:04:36.960> missed 00:04:37.370 --> 00:04:37.380 align:start position:0% proposed the red one is when it's missed 00:04:37.380 --> 00:04:40.550 align:start position:0% proposed the red one is when it's missed and<00:04:38.280> the<00:04:38.400> yellow<00:04:38.520> is<00:04:38.759> if<00:04:38.940> it's<00:04:39.060> orphaned<00:04:39.720> and 00:04:40.550 --> 00:04:40.560 align:start position:0% and the yellow is if it's orphaned and 00:04:40.560 --> 00:04:42.469 align:start position:0% and the yellow is if it's orphaned and that's<00:04:40.680> kind<00:04:40.979> of<00:04:41.040> a<00:04:41.280> nice<00:04:41.460> overview<00:04:42.000> of<00:04:42.300> the 00:04:42.469 --> 00:04:42.479 align:start position:0% that's kind of a nice overview of the 00:04:42.479 --> 00:04:44.749 align:start position:0% that's kind of a nice overview of the first<00:04:42.660> few<00:04:43.020> epochs<00:04:43.800> when<00:04:44.220> the<00:04:44.400> Genesis 00:04:44.749 --> 00:04:44.759 align:start position:0% first few epochs when the Genesis 00:04:44.759 --> 00:04:46.550 align:start position:0% first few epochs when the Genesis happened<00:04:45.060> and<00:04:45.720> we<00:04:45.900> also<00:04:46.080> have<00:04:46.199> like<00:04:46.380> a 00:04:46.550 --> 00:04:46.560 align:start position:0% happened and we also have like a 00:04:46.560 --> 00:04:49.490 align:start position:0% happened and we also have like a checklist<00:04:46.860> below<00:04:47.340> how<00:04:48.240> much<00:04:48.360> finalization<00:04:49.080> we 00:04:49.490 --> 00:04:49.500 align:start position:0% checklist below how much finalization we 00:04:49.500 --> 00:04:51.890 align:start position:0% checklist below how much finalization we have<00:04:49.680> uh<00:04:50.160> no<00:04:50.400> our<00:04:50.520> participation<00:04:51.000> we<00:04:51.300> have<00:04:51.479> and 00:04:51.890 --> 00:04:51.900 align:start position:0% have uh no our participation we have and 00:04:51.900 --> 00:04:53.930 align:start position:0% have uh no our participation we have and if<00:04:52.020> the<00:04:52.199> EPO<00:04:52.560> has<00:04:52.740> Justified<00:04:53.100> and<00:04:53.340> finalized 00:04:53.930 --> 00:04:53.940 align:start position:0% if the EPO has Justified and finalized 00:04:53.940 --> 00:04:56.629 align:start position:0% if the EPO has Justified and finalized and<00:04:54.900> a<00:04:55.080> nice<00:04:55.199> rocket<00:04:55.620> or<00:04:55.919> like<00:04:56.160> the<00:04:56.280> countdown 00:04:56.629 --> 00:04:56.639 align:start position:0% and a nice rocket or like the countdown 00:04:56.639 --> 00:04:59.930 align:start position:0% and a nice rocket or like the countdown when<00:04:57.300> Genesis<00:04:57.780> started<00:04:58.520> which<00:04:59.520> is<00:04:59.639> also 00:04:59.930 --> 00:04:59.940 align:start position:0% when Genesis started which is also 00:04:59.940 --> 00:05:03.710 align:start position:0% when Genesis started which is also pretty<00:05:00.120> pretty<00:05:00.419> nice<00:05:00.979> so<00:05:01.979> that's<00:05:02.220> kind<00:05:02.520> of<00:05:02.639> uh 00:05:03.710 --> 00:05:03.720 align:start position:0% pretty pretty nice so that's kind of uh 00:05:03.720 --> 00:05:06.950 align:start position:0% pretty pretty nice so that's kind of uh how<00:05:04.440> how<00:05:04.680> this<00:05:04.979> whole<00:05:05.160> project<00:05:05.460> began<00:05:06.000> and<00:05:06.720> it 00:05:06.950 --> 00:05:06.960 align:start position:0% how how this whole project began and it 00:05:06.960 --> 00:05:09.110 align:start position:0% how how this whole project began and it kind<00:05:07.139> of<00:05:07.259> exploded<00:05:07.979> a<00:05:08.220> bit<00:05:08.340> more<00:05:08.699> and<00:05:08.759> more<00:05:08.940> and 00:05:09.110 --> 00:05:09.120 align:start position:0% kind of exploded a bit more and more and 00:05:09.120 --> 00:05:12.530 align:start position:0% kind of exploded a bit more and more and with<00:05:09.360> the<00:05:09.540> merge<00:05:09.840> we<00:05:10.740> uh<00:05:11.220> tried<00:05:11.639> to<00:05:11.759> add<00:05:12.240> more 00:05:12.530 --> 00:05:12.540 align:start position:0% with the merge we uh tried to add more 00:05:12.540 --> 00:05:14.390 align:start position:0% with the merge we uh tried to add more information<00:05:12.780> not<00:05:13.380> just 00:05:14.390 --> 00:05:14.400 align:start position:0% information not just 00:05:14.400 --> 00:05:16.010 align:start position:0% information not just um the<00:05:14.639> phase<00:05:14.880> zero<00:05:15.240> information<00:05:15.419> and<00:05:15.840> it 00:05:16.010 --> 00:05:16.020 align:start position:0% um the phase zero information and it 00:05:16.020 --> 00:05:17.390 align:start position:0% um the phase zero information and it kind<00:05:16.139> of<00:05:16.199> grew<00:05:16.440> and<00:05:16.500> grew<00:05:16.860> and<00:05:17.220> this 00:05:17.390 --> 00:05:17.400 align:start position:0% kind of grew and grew and this 00:05:17.400 --> 00:05:19.010 align:start position:0% kind of grew and grew and this presentation<00:05:17.820> will<00:05:18.120> also<00:05:18.360> be<00:05:18.479> kind<00:05:18.720> of<00:05:18.840> about 00:05:19.010 --> 00:05:19.020 align:start position:0% presentation will also be kind of about 00:05:19.020 --> 00:05:21.650 align:start position:0% presentation will also be kind of about how<00:05:19.500> we<00:05:20.040> kind<00:05:20.160> of<00:05:20.280> handled<00:05:20.639> the<00:05:20.820> scale<00:05:21.120> and 00:05:21.650 --> 00:05:21.660 align:start position:0% how we kind of handled the scale and 00:05:21.660 --> 00:05:23.629 align:start position:0% how we kind of handled the scale and also<00:05:22.020> give<00:05:22.320> a<00:05:22.500> kind<00:05:22.680> of<00:05:22.800> a<00:05:22.860> workshop<00:05:23.220> where<00:05:23.460> you 00:05:23.629 --> 00:05:23.639 align:start position:0% also give a kind of a workshop where you 00:05:23.639 --> 00:05:25.790 align:start position:0% also give a kind of a workshop where you can<00:05:23.820> help<00:05:24.360> us<00:05:24.539> with<00:05:24.840> with<00:05:25.080> kind<00:05:25.380> of<00:05:25.500> finding 00:05:25.790 --> 00:05:25.800 align:start position:0% can help us with with kind of finding 00:05:25.800 --> 00:05:29.210 align:start position:0% can help us with with kind of finding ways<00:05:26.280> to<00:05:26.460> scale<00:05:26.639> better 00:05:29.210 --> 00:05:29.220 align:start position:0% 00:05:29.220 --> 00:05:32.210 align:start position:0% um<00:05:29.340> yeah<00:05:29.880> so<00:05:30.720> let's<00:05:31.020> go<00:05:31.259> a<00:05:31.560> bit<00:05:31.680> to<00:05:32.039> the 00:05:32.210 --> 00:05:32.220 align:start position:0% um yeah so let's go a bit to the 00:05:32.220 --> 00:05:34.909 align:start position:0% um yeah so let's go a bit to the architecture<00:05:32.820> so<00:05:33.780> in<00:05:34.020> the<00:05:34.139> beginning<00:05:34.259> this<00:05:34.740> is 00:05:34.909 --> 00:05:34.919 align:start position:0% architecture so in the beginning this is 00:05:34.919 --> 00:05:37.550 align:start position:0% architecture so in the beginning this is kind<00:05:35.160> of<00:05:35.280> a<00:05:35.759> very<00:05:36.120> simple<00:05:36.300> view<00:05:36.660> what<00:05:37.080> uh<00:05:37.440> the 00:05:37.550 --> 00:05:37.560 align:start position:0% kind of a very simple view what uh the 00:05:37.560 --> 00:05:39.650 align:start position:0% kind of a very simple view what uh the beacon<00:05:37.860> chain<00:05:37.979> Explorer<00:05:38.460> looked<00:05:38.699> like<00:05:38.820> I<00:05:39.419> also 00:05:39.650 --> 00:05:39.660 align:start position:0% beacon chain Explorer looked like I also 00:05:39.660 --> 00:05:43.010 align:start position:0% beacon chain Explorer looked like I also presented<00:05:40.139> this<00:05:40.440> a<00:05:40.800> similar<00:05:41.280> slide<00:05:41.900> I<00:05:42.900> think 00:05:43.010 --> 00:05:43.020 align:start position:0% presented this a similar slide I think 00:05:43.020 --> 00:05:47.090 align:start position:0% presented this a similar slide I think it<00:05:43.259> was<00:05:43.680> etcc<00:05:44.060> a<00:05:45.060> year<00:05:45.180> ago<00:05:45.500> where<00:05:46.500> we<00:05:46.680> had<00:05:46.860> just 00:05:47.090 --> 00:05:47.100 align:start position:0% it was etcc a year ago where we had just 00:05:47.100 --> 00:05:49.249 align:start position:0% it was etcc a year ago where we had just the<00:05:47.400> prism<00:05:47.639> node<00:05:48.000> we<00:05:48.240> had<00:05:48.360> infuro<00:05:48.900> node<00:05:49.080> and 00:05:49.249 --> 00:05:49.259 align:start position:0% the prism node we had infuro node and 00:05:49.259 --> 00:05:50.689 align:start position:0% the prism node we had infuro node and the<00:05:49.380> funeral<00:05:49.500> node<00:05:49.860> was<00:05:50.039> mainly<00:05:50.280> to<00:05:50.460> get<00:05:50.580> the 00:05:50.689 --> 00:05:50.699 align:start position:0% the funeral node was mainly to get the 00:05:50.699 --> 00:05:54.110 align:start position:0% the funeral node was mainly to get the deposit<00:05:51.120> data<00:05:51.539> from<00:05:52.020> East<00:05:52.320> one<00:05:52.639> and<00:05:53.639> then<00:05:53.759> we 00:05:54.110 --> 00:05:54.120 align:start position:0% deposit data from East one and then we 00:05:54.120 --> 00:05:55.430 align:start position:0% deposit data from East one and then we had<00:05:54.300> an<00:05:54.419> exporter<00:05:54.780> that<00:05:55.020> just<00:05:55.199> basically 00:05:55.430 --> 00:05:55.440 align:start position:0% had an exporter that just basically 00:05:55.440 --> 00:05:57.230 align:start position:0% had an exporter that just basically wrote<00:05:55.740> everything<00:05:55.919> into<00:05:56.220> postgres<00:05:56.820> database 00:05:57.230 --> 00:05:57.240 align:start position:0% wrote everything into postgres database 00:05:57.240 --> 00:05:58.850 align:start position:0% wrote everything into postgres database and<00:05:57.840> that<00:05:57.900> worked<00:05:58.259> really<00:05:58.380> well<00:05:58.560> in<00:05:58.740> the 00:05:58.850 --> 00:05:58.860 align:start position:0% and that worked really well in the 00:05:58.860 --> 00:06:01.189 align:start position:0% and that worked really well in the beginning<00:05:58.979> it<00:05:59.280> was<00:05:59.400> really<00:05:59.580> easy<00:05:59.840> to<00:06:00.840> work<00:06:00.960> on 00:06:01.189 --> 00:06:01.199 align:start position:0% beginning it was really easy to work on 00:06:01.199 --> 00:06:03.770 align:start position:0% beginning it was really easy to work on and<00:06:01.979> then<00:06:02.100> we<00:06:02.280> just<00:06:02.400> had<00:06:02.580> a<00:06:02.759> golang<00:06:03.360> front<00:06:03.600> end 00:06:03.770 --> 00:06:03.780 align:start position:0% and then we just had a golang front end 00:06:03.780 --> 00:06:05.570 align:start position:0% and then we just had a golang front end with<00:06:04.020> some<00:06:04.199> templates<00:06:04.560> that<00:06:04.919> kind<00:06:05.160> of<00:06:05.220> served 00:06:05.570 --> 00:06:05.580 align:start position:0% with some templates that kind of served 00:06:05.580 --> 00:06:08.930 align:start position:0% with some templates that kind of served everything<00:06:05.820> to<00:06:06.479> the<00:06:06.660> end<00:06:06.780> user<00:06:07.280> and<00:06:08.280> even<00:06:08.400> when 00:06:08.930 --> 00:06:08.940 align:start position:0% everything to the end user and even when 00:06:08.940 --> 00:06:10.909 align:start position:0% everything to the end user and even when I<00:06:09.120> presented<00:06:09.479> it<00:06:09.600> back<00:06:09.780> then<00:06:09.960> we<00:06:10.500> kind<00:06:10.620> of<00:06:10.740> can 00:06:10.909 --> 00:06:10.919 align:start position:0% I presented it back then we kind of can 00:06:10.919 --> 00:06:14.950 align:start position:0% I presented it back then we kind of can see<00:06:11.160> that<00:06:12.120> prism<00:06:12.840> already<00:06:13.139> needed<00:06:13.620> like<00:06:13.919> a 00:06:14.950 --> 00:06:14.960 align:start position:0% see that prism already needed like a 00:06:14.960 --> 00:06:19.129 align:start position:0% see that prism already needed like a 576<00:06:15.960> uh<00:06:16.620> 67<00:06:17.280> gigabytes<00:06:17.940> of<00:06:18.180> data<00:06:18.479> Erica<00:06:18.900> node 00:06:19.129 --> 00:06:19.139 align:start position:0% 576 uh 67 gigabytes of data Erica node 00:06:19.139 --> 00:06:21.650 align:start position:0% 576 uh 67 gigabytes of data Erica node already<00:06:19.320> 1.4<00:06:19.919> terabytes<00:06:20.460> and<00:06:21.000> cause<00:06:21.120> postgres 00:06:21.650 --> 00:06:21.660 align:start position:0% already 1.4 terabytes and cause postgres 00:06:21.660 --> 00:06:24.110 align:start position:0% already 1.4 terabytes and cause postgres already<00:06:21.960> two<00:06:22.500> terabytes<00:06:23.039> of<00:06:23.160> data<00:06:23.520> and<00:06:23.880> then<00:06:24.000> I 00:06:24.110 --> 00:06:24.120 align:start position:0% already two terabytes of data and then I 00:06:24.120 --> 00:06:25.909 align:start position:0% already two terabytes of data and then I looked<00:06:24.419> at<00:06:24.479> these<00:06:24.840> numbers<00:06:25.020> again<00:06:25.319> how<00:06:25.740> it's 00:06:25.909 --> 00:06:25.919 align:start position:0% looked at these numbers again how it's 00:06:25.919 --> 00:06:27.770 align:start position:0% looked at these numbers again how it's running<00:06:26.100> today<00:06:26.400> and<00:06:27.000> kind<00:06:27.180> of<00:06:27.300> the<00:06:27.360> reason<00:06:27.539> why 00:06:27.770 --> 00:06:27.780 align:start position:0% running today and kind of the reason why 00:06:27.780 --> 00:06:30.469 align:start position:0% running today and kind of the reason why we<00:06:27.960> had<00:06:28.080> to<00:06:28.139> scale<00:06:28.380> a<00:06:28.740> little<00:06:28.800> bit<00:06:28.979> more<00:06:29.300> so<00:06:30.300> the 00:06:30.469 --> 00:06:30.479 align:start position:0% we had to scale a little bit more so the 00:06:30.479 --> 00:06:32.090 align:start position:0% we had to scale a little bit more so the numbers<00:06:30.600> now<00:06:30.960> are<00:06:31.199> that<00:06:31.500> we<00:06:31.680> switched<00:06:31.979> to 00:06:32.090 --> 00:06:32.100 align:start position:0% numbers now are that we switched to 00:06:32.100 --> 00:06:35.210 align:start position:0% numbers now are that we switched to Lighthouse<00:06:32.539> and<00:06:33.539> we<00:06:33.720> have<00:06:33.840> a<00:06:34.020> 32<00:06:34.380> slot<00:06:34.740> sync<00:06:35.100> so 00:06:35.210 --> 00:06:35.220 align:start position:0% Lighthouse and we have a 32 slot sync so 00:06:35.220 --> 00:06:37.610 align:start position:0% Lighthouse and we have a 32 slot sync so there's<00:06:35.460> different<00:06:35.819> kind<00:06:36.539> of<00:06:36.660> sync<00:06:37.319> versions 00:06:37.610 --> 00:06:37.620 align:start position:0% there's different kind of sync versions 00:06:37.620 --> 00:06:39.110 align:start position:0% there's different kind of sync versions that<00:06:37.800> you<00:06:37.919> can<00:06:37.979> choose<00:06:38.280> and<00:06:38.580> depending<00:06:39.000> on 00:06:39.110 --> 00:06:39.120 align:start position:0% that you can choose and depending on 00:06:39.120 --> 00:06:41.809 align:start position:0% that you can choose and depending on what<00:06:39.680> amount<00:06:40.680> of<00:06:40.740> stats<00:06:41.100> you<00:06:41.220> choose<00:06:41.460> the<00:06:41.759> more 00:06:41.809 --> 00:06:41.819 align:start position:0% what amount of stats you choose the more 00:06:41.819 --> 00:06:43.309 align:start position:0% what amount of stats you choose the more information<00:06:42.060> is<00:06:42.419> stored<00:06:42.720> but<00:06:42.900> the<00:06:43.020> quicker 00:06:43.309 --> 00:06:43.319 align:start position:0% information is stored but the quicker 00:06:43.319 --> 00:06:45.350 align:start position:0% information is stored but the quicker you<00:06:43.500> can<00:06:43.620> retrieve<00:06:43.979> information<00:06:44.220> and<00:06:45.180> we 00:06:45.350 --> 00:06:45.360 align:start position:0% you can retrieve information and we 00:06:45.360 --> 00:06:47.930 align:start position:0% you can retrieve information and we basically<00:06:45.780> want<00:06:46.199> to<00:06:46.380> store<00:06:46.500> everything<00:06:46.940> and 00:06:47.930 --> 00:06:47.940 align:start position:0% basically want to store everything and 00:06:47.940 --> 00:06:51.170 align:start position:0% basically want to store everything and that's<00:06:48.360> already<00:06:48.600> a<00:06:48.840> five<00:06:49.080> terabyte<00:06:50.060> disk<00:06:51.060> that 00:06:51.170 --> 00:06:51.180 align:start position:0% that's already a five terabyte disk that 00:06:51.180 --> 00:06:53.330 align:start position:0% that's already a five terabyte disk that you<00:06:51.300> need<00:06:51.419> for<00:06:51.660> that<00:06:51.840> Lighthouse<00:06:52.199> then<00:06:52.800> Aragon 00:06:53.330 --> 00:06:53.340 align:start position:0% you need for that Lighthouse then Aragon 00:06:53.340 --> 00:06:57.110 align:start position:0% you need for that Lighthouse then Aragon is<00:06:53.580> 2.1<00:06:54.120> and<00:06:54.600> our<00:06:54.780> postgres<00:06:55.199> database<00:06:55.680> is<00:06:56.340> huge 00:06:57.110 --> 00:06:57.120 align:start position:0% is 2.1 and our postgres database is huge 00:06:57.120 --> 00:07:00.409 align:start position:0% is 2.1 and our postgres database is huge so<00:06:57.840> uh<00:06:58.380> kind<00:06:58.620> of<00:06:58.740> the<00:06:58.979> tables<00:06:59.580> and<00:06:59.880> the<00:07:00.000> indexes 00:07:00.409 --> 00:07:00.419 align:start position:0% so uh kind of the tables and the indexes 00:07:00.419 --> 00:07:01.850 align:start position:0% so uh kind of the tables and the indexes that<00:07:00.600> we<00:07:00.720> have<00:07:00.840> in<00:07:00.960> the<00:07:01.080> postgres<00:07:01.440> database 00:07:01.850 --> 00:07:01.860 align:start position:0% that we have in the postgres database 00:07:01.860 --> 00:07:04.309 align:start position:0% that we have in the postgres database they<00:07:02.340> just<00:07:02.520> don't<00:07:02.639> scale<00:07:03.000> that<00:07:03.180> well<00:07:03.419> so<00:07:04.139> it's 00:07:04.309 --> 00:07:04.319 align:start position:0% they just don't scale that well so it's 00:07:04.319 --> 00:07:06.950 align:start position:0% they just don't scale that well so it's already<00:07:04.500> 10<00:07:04.860> terabytes<00:07:05.460> big<00:07:05.699> and<00:07:06.120> we<00:07:06.600> don't 00:07:06.950 --> 00:07:06.960 align:start position:0% already 10 terabytes big and we don't 00:07:06.960 --> 00:07:09.110 align:start position:0% already 10 terabytes big and we don't only<00:07:07.199> run<00:07:07.560> the<00:07:07.800> mainnet<00:07:08.220> we<00:07:08.520> also<00:07:08.759> run<00:07:08.940> the 00:07:09.110 --> 00:07:09.120 align:start position:0% only run the mainnet we also run the 00:07:09.120 --> 00:07:12.050 align:start position:0% only run the mainnet we also run the test<00:07:09.240> net<00:07:09.479> and<00:07:10.380> the<00:07:10.500> test<00:07:10.620> net<00:07:10.860> is<00:07:11.400> just<00:07:11.759> that 00:07:12.050 --> 00:07:12.060 align:start position:0% test net and the test net is just that 00:07:12.060 --> 00:07:13.670 align:start position:0% test net and the test net is just that amount<00:07:12.300> and<00:07:12.539> even<00:07:12.840> a<00:07:12.960> bit<00:07:13.080> more<00:07:13.199> for<00:07:13.440> different 00:07:13.670 --> 00:07:13.680 align:start position:0% amount and even a bit more for different 00:07:13.680 --> 00:07:15.890 align:start position:0% amount and even a bit more for different test<00:07:13.919> Nets<00:07:14.400> so<00:07:14.759> it's<00:07:14.880> a<00:07:15.060> huge<00:07:15.240> amount<00:07:15.419> of<00:07:15.600> data 00:07:15.890 --> 00:07:15.900 align:start position:0% test Nets so it's a huge amount of data 00:07:15.900 --> 00:07:18.110 align:start position:0% test Nets so it's a huge amount of data and<00:07:16.740> it's<00:07:16.979> getting<00:07:17.280> a<00:07:17.460> bit<00:07:17.520> expensive<00:07:17.880> running 00:07:18.110 --> 00:07:18.120 align:start position:0% and it's getting a bit expensive running 00:07:18.120 --> 00:07:20.150 align:start position:0% and it's getting a bit expensive running that<00:07:18.360> in<00:07:18.479> the<00:07:18.660> cloud<00:07:18.780> so<00:07:19.199> we're<00:07:19.680> going<00:07:19.800> to<00:07:19.919> talk 00:07:20.150 --> 00:07:20.160 align:start position:0% that in the cloud so we're going to talk 00:07:20.160 --> 00:07:22.490 align:start position:0% that in the cloud so we're going to talk about<00:07:20.280> how<00:07:20.699> we<00:07:20.880> kind<00:07:21.419> of<00:07:21.479> started<00:07:22.020> migrating 00:07:22.490 --> 00:07:22.500 align:start position:0% about how we kind of started migrating 00:07:22.500 --> 00:07:25.490 align:start position:0% about how we kind of started migrating away<00:07:22.800> from<00:07:23.099> that 00:07:25.490 --> 00:07:25.500 align:start position:0% 00:07:25.500 --> 00:07:27.290 align:start position:0% um<00:07:25.560> and<00:07:25.919> basically<00:07:26.280> the<00:07:26.639> the<00:07:26.880> scaling 00:07:27.290 --> 00:07:27.300 align:start position:0% um and basically the the scaling 00:07:27.300 --> 00:07:29.809 align:start position:0% um and basically the the scaling challenges<00:07:27.780> uh<00:07:28.560> during<00:07:28.740> the<00:07:28.979> merge<00:07:29.340> so<00:07:29.580> this 00:07:29.809 --> 00:07:29.819 align:start position:0% challenges uh during the merge so this 00:07:29.819 --> 00:07:32.390 align:start position:0% challenges uh during the merge so this is<00:07:29.940> kind<00:07:30.180> of<00:07:30.300> a<00:07:30.599> analytics<00:07:31.560> view<00:07:31.800> that<00:07:32.099> we<00:07:32.280> had 00:07:32.390 --> 00:07:32.400 align:start position:0% is kind of a analytics view that we had 00:07:32.400 --> 00:07:33.710 align:start position:0% is kind of a analytics view that we had so<00:07:32.759> we<00:07:33.000> had 00:07:33.710 --> 00:07:33.720 align:start position:0% so we had 00:07:33.720 --> 00:07:37.730 align:start position:0% so we had um<00:07:33.860> concurrent<00:07:34.860> sessions<00:07:35.160> of<00:07:35.780> 2267<00:07:36.780> uh<00:07:37.500> people 00:07:37.730 --> 00:07:37.740 align:start position:0% um concurrent sessions of 2267 uh people 00:07:37.740 --> 00:07:39.110 align:start position:0% um concurrent sessions of 2267 uh people that<00:07:38.039> were<00:07:38.160> looking<00:07:38.340> during<00:07:38.639> the<00:07:38.819> merge 00:07:39.110 --> 00:07:39.120 align:start position:0% that were looking during the merge 00:07:39.120 --> 00:07:41.029 align:start position:0% that were looking during the merge because<00:07:39.300> we<00:07:39.479> had<00:07:39.599> like<00:07:39.840> this<00:07:40.080> nice<00:07:40.259> slot<00:07:40.860> view 00:07:41.029 --> 00:07:41.039 align:start position:0% because we had like this nice slot view 00:07:41.039 --> 00:07:42.830 align:start position:0% because we had like this nice slot view that<00:07:41.280> you<00:07:41.400> saw<00:07:41.580> before<00:07:41.819> where<00:07:42.419> people<00:07:42.599> could 00:07:42.830 --> 00:07:42.840 align:start position:0% that you saw before where people could 00:07:42.840 --> 00:07:45.529 align:start position:0% that you saw before where people could see<00:07:43.020> okay<00:07:43.259> during<00:07:43.979> the<00:07:44.280> transition 00:07:45.529 --> 00:07:45.539 align:start position:0% see okay during the transition 00:07:45.539 --> 00:07:47.570 align:start position:0% see okay during the transition um<00:07:45.599> what<00:07:45.840> was<00:07:46.020> happening<00:07:46.380> uh<00:07:46.919> it<00:07:47.099> was<00:07:47.160> it's<00:07:47.340> a 00:07:47.570 --> 00:07:47.580 align:start position:0% um what was happening uh it was it's a 00:07:47.580 --> 00:07:49.490 align:start position:0% um what was happening uh it was it's a nice<00:07:47.699> visual<00:07:48.120> way<00:07:48.479> of<00:07:48.660> kind<00:07:48.840> of<00:07:48.960> tracking<00:07:49.380> it 00:07:49.490 --> 00:07:49.500 align:start position:0% nice visual way of kind of tracking it 00:07:49.500 --> 00:07:51.469 align:start position:0% nice visual way of kind of tracking it and<00:07:50.099> we<00:07:50.160> had<00:07:50.280> a<00:07:50.400> lot<00:07:50.520> of<00:07:50.639> people 00:07:51.469 --> 00:07:51.479 align:start position:0% and we had a lot of people 00:07:51.479 --> 00:07:53.689 align:start position:0% and we had a lot of people um<00:07:51.539> we<00:07:52.139> kind<00:07:52.319> of<00:07:52.440> were<00:07:52.800> kind<00:07:53.039> of<00:07:53.160> prepared<00:07:53.460> so 00:07:53.689 --> 00:07:53.699 align:start position:0% um we kind of were kind of prepared so 00:07:53.699 --> 00:07:55.670 align:start position:0% um we kind of were kind of prepared so you<00:07:53.880> have<00:07:54.120> this<00:07:54.360> Super<00:07:54.599> Mario<00:07:54.780> mushroom<00:07:55.440> that 00:07:55.670 --> 00:07:55.680 align:start position:0% you have this Super Mario mushroom that 00:07:55.680 --> 00:07:57.469 align:start position:0% you have this Super Mario mushroom that should<00:07:55.800> power<00:07:56.039> you<00:07:56.280> up<00:07:56.460> but<00:07:57.000> that<00:07:57.180> mushroom 00:07:57.469 --> 00:07:57.479 align:start position:0% should power you up but that mushroom 00:07:57.479 --> 00:07:59.330 align:start position:0% should power you up but that mushroom was<00:07:57.720> kind<00:07:57.900> of<00:07:57.960> overpowered<00:07:58.680> by<00:07:58.919> the<00:07:59.160> people 00:07:59.330 --> 00:07:59.340 align:start position:0% was kind of overpowered by the people 00:07:59.340 --> 00:08:02.029 align:start position:0% was kind of overpowered by the people looking<00:07:59.940> at<00:08:00.240> it<00:08:00.360> because<00:08:00.599> uh<00:08:01.199> the<00:08:01.380> way<00:08:01.620> the 00:08:02.029 --> 00:08:02.039 align:start position:0% looking at it because uh the way the 00:08:02.039 --> 00:08:04.430 align:start position:0% looking at it because uh the way the architecture<00:08:02.639> was<00:08:03.120> designed<00:08:03.660> it<00:08:04.139> just<00:08:04.259> didn't 00:08:04.430 --> 00:08:04.440 align:start position:0% architecture was designed it just didn't 00:08:04.440 --> 00:08:06.230 align:start position:0% architecture was designed it just didn't scale<00:08:04.680> well<00:08:04.979> we<00:08:05.160> have<00:08:05.280> front-end<00:08:05.699> instances 00:08:06.230 --> 00:08:06.240 align:start position:0% scale well we have front-end instances 00:08:06.240 --> 00:08:08.150 align:start position:0% scale well we have front-end instances that<00:08:06.840> kind<00:08:07.020> of<00:08:07.139> have<00:08:07.259> to<00:08:07.440> query<00:08:07.680> the<00:08:07.979> same 00:08:08.150 --> 00:08:08.160 align:start position:0% that kind of have to query the same 00:08:08.160 --> 00:08:10.249 align:start position:0% that kind of have to query the same stuff<00:08:08.400> like<00:08:09.060> if<00:08:09.360> we<00:08:09.479> have<00:08:09.660> five<00:08:09.780> front-end 00:08:10.249 --> 00:08:10.259 align:start position:0% stuff like if we have five front-end 00:08:10.259 --> 00:08:12.230 align:start position:0% stuff like if we have five front-end instances<00:08:10.560> they<00:08:11.099> do<00:08:11.280> five<00:08:11.520> times<00:08:11.759> the<00:08:12.060> same 00:08:12.230 --> 00:08:12.240 align:start position:0% instances they do five times the same 00:08:12.240 --> 00:08:14.330 align:start position:0% instances they do five times the same queries<00:08:12.660> because<00:08:13.199> we<00:08:13.440> don't<00:08:13.620> just<00:08:13.800> have<00:08:14.039> like 00:08:14.330 --> 00:08:14.340 align:start position:0% queries because we don't just have like 00:08:14.340 --> 00:08:17.029 align:start position:0% queries because we don't just have like one<00:08:15.060> layer<00:08:15.419> that<00:08:15.780> updates<00:08:16.139> our<00:08:16.319> cache<00:08:16.680> we<00:08:16.860> just 00:08:17.029 --> 00:08:17.039 align:start position:0% one layer that updates our cache we just 00:08:17.039 --> 00:08:18.469 align:start position:0% one layer that updates our cache we just have<00:08:17.160> every<00:08:17.340> front<00:08:17.580> and<00:08:17.819> instance<00:08:18.120> that<00:08:18.300> has 00:08:18.469 --> 00:08:18.479 align:start position:0% have every front and instance that has 00:08:18.479 --> 00:08:20.570 align:start position:0% have every front and instance that has its<00:08:18.660> own<00:08:18.780> cache<00:08:19.199> so<00:08:19.680> these<00:08:20.039> are<00:08:20.160> things<00:08:20.340> we 00:08:20.570 --> 00:08:20.580 align:start position:0% its own cache so these are things we 00:08:20.580 --> 00:08:23.749 align:start position:0% its own cache so these are things we kind<00:08:20.699> of<00:08:20.819> try<00:08:21.060> to<00:08:21.300> try<00:08:21.960> to<00:08:22.199> improve<00:08:23.039> and<00:08:23.699> then 00:08:23.749 --> 00:08:23.759 align:start position:0% kind of try to try to improve and then 00:08:23.759 --> 00:08:26.390 align:start position:0% kind of try to try to improve and then again<00:08:23.879> we<00:08:24.120> have<00:08:24.419> very<00:08:25.020> expensive<00:08:25.560> indexing<00:08:26.220> as 00:08:26.390 --> 00:08:26.400 align:start position:0% again we have very expensive indexing as 00:08:26.400 --> 00:08:28.790 align:start position:0% again we have very expensive indexing as well<00:08:26.580> in<00:08:26.759> bigtable<00:08:27.300> and<00:08:27.539> big<00:08:27.720> I<00:08:28.139> know<00:08:28.259> a<00:08:28.440> big 00:08:28.790 --> 00:08:28.800 align:start position:0% well in bigtable and big I know a big 00:08:28.800 --> 00:08:30.950 align:start position:0% well in bigtable and big I know a big table<00:08:28.919> that's<00:08:29.580> going<00:08:29.940> to<00:08:30.060> get<00:08:30.120> to<00:08:30.240> later<00:08:30.479> in 00:08:30.950 --> 00:08:30.960 align:start position:0% table that's going to get to later in 00:08:30.960 --> 00:08:34.550 align:start position:0% table that's going to get to later in past<00:08:31.080> Chris<00:08:31.580> and<00:08:32.580> pascals<00:08:33.180> also<00:08:33.419> has<00:08:33.599> to<00:08:33.839> get<00:08:34.380> a 00:08:34.550 --> 00:08:34.560 align:start position:0% past Chris and pascals also has to get a 00:08:34.560 --> 00:08:36.529 align:start position:0% past Chris and pascals also has to get a lot<00:08:34.680> of<00:08:34.800> the<00:08:34.919> table<00:08:35.099> into<00:08:35.700> memory<00:08:36.060> to<00:08:36.300> be<00:08:36.419> able 00:08:36.529 --> 00:08:36.539 align:start position:0% lot of the table into memory to be able 00:08:36.539 --> 00:08:38.269 align:start position:0% lot of the table into memory to be able to<00:08:36.719> query<00:08:37.020> stuff 00:08:38.269 --> 00:08:38.279 align:start position:0% to query stuff 00:08:38.279 --> 00:08:40.790 align:start position:0% to query stuff um<00:08:38.820> which<00:08:39.240> is<00:08:39.419> a<00:08:39.659> lot<00:08:39.899> of<00:08:40.020> the<00:08:40.140> times<00:08:40.320> not<00:08:40.620> very 00:08:40.790 --> 00:08:40.800 align:start position:0% um which is a lot of the times not very 00:08:40.800 --> 00:08:42.350 align:start position:0% um which is a lot of the times not very efficient<00:08:41.219> especially<00:08:41.580> with<00:08:41.760> huge<00:08:42.060> amount<00:08:42.240> of 00:08:42.350 --> 00:08:42.360 align:start position:0% efficient especially with huge amount of 00:08:42.360 --> 00:08:43.990 align:start position:0% efficient especially with huge amount of data 00:08:43.990 --> 00:08:44.000 align:start position:0% data 00:08:44.000 --> 00:08:45.590 align:start position:0% data and 00:08:45.590 --> 00:08:45.600 align:start position:0% and 00:08:45.600 --> 00:08:46.730 align:start position:0% and um 00:08:46.730 --> 00:08:46.740 align:start position:0% um 00:08:46.740 --> 00:08:49.250 align:start position:0% um so<00:08:47.339> what<00:08:47.640> we<00:08:47.820> try<00:08:48.000> to<00:08:48.120> do<00:08:48.240> is<00:08:48.480> we<00:08:48.899> have<00:08:49.080> we 00:08:49.250 --> 00:08:49.260 align:start position:0% so what we try to do is we have we 00:08:49.260 --> 00:08:51.949 align:start position:0% so what we try to do is we have we started<00:08:49.560> out<00:08:49.680> with<00:08:49.920> one<00:08:50.220> big<00:08:50.399> binary<00:08:51.000> where 00:08:51.949 --> 00:08:51.959 align:start position:0% started out with one big binary where 00:08:51.959 --> 00:08:54.710 align:start position:0% started out with one big binary where everything<00:08:52.320> runs<00:08:52.860> and<00:08:53.339> we<00:08:53.459> try<00:08:53.700> to<00:08:54.000> strip<00:08:54.480> away 00:08:54.710 --> 00:08:54.720 align:start position:0% everything runs and we try to strip away 00:08:54.720 --> 00:08:56.690 align:start position:0% everything runs and we try to strip away things<00:08:55.140> from<00:08:55.380> that<00:08:55.560> big<00:08:55.740> binary<00:08:56.160> and<00:08:56.399> kind<00:08:56.580> of 00:08:56.690 --> 00:08:56.700 align:start position:0% things from that big binary and kind of 00:08:56.700 --> 00:08:59.810 align:start position:0% things from that big binary and kind of isolate<00:08:57.120> that<00:08:57.360> in<00:08:57.720> microservices<00:08:58.500> that<00:08:59.399> not 00:08:59.810 --> 00:08:59.820 align:start position:0% isolate that in microservices that not 00:08:59.820 --> 00:09:02.329 align:start position:0% isolate that in microservices that not every<00:09:00.060> binary<00:09:00.480> does<00:09:00.720> everything<00:09:01.019> and<00:09:01.860> if<00:09:02.160> we 00:09:02.329 --> 00:09:02.339 align:start position:0% every binary does everything and if we 00:09:02.339 --> 00:09:05.030 align:start position:0% every binary does everything and if we duplicate<00:09:03.000> one<00:09:03.240> binder<00:09:03.660> we<00:09:03.839> don't<00:09:04.019> do<00:09:04.440> uh 00:09:05.030 --> 00:09:05.040 align:start position:0% duplicate one binder we don't do uh 00:09:05.040 --> 00:09:07.370 align:start position:0% duplicate one binder we don't do uh unnecessary<00:09:05.700> work 00:09:07.370 --> 00:09:07.380 align:start position:0% unnecessary work 00:09:07.380 --> 00:09:09.590 align:start position:0% unnecessary work um<00:09:07.440> and<00:09:07.920> kind<00:09:08.220> of<00:09:08.339> the<00:09:08.760> migration<00:09:09.120> is<00:09:09.360> kind<00:09:09.540> of 00:09:09.590 --> 00:09:09.600 align:start position:0% um and kind of the migration is kind of 00:09:09.600 --> 00:09:11.449 align:start position:0% um and kind of the migration is kind of a<00:09:09.720> bit<00:09:09.839> challenging<00:09:10.260> for<00:09:10.440> us<00:09:10.560> because<00:09:10.740> then<00:09:11.040> we 00:09:11.449 --> 00:09:11.459 align:start position:0% a bit challenging for us because then we 00:09:11.459 --> 00:09:13.430 align:start position:0% a bit challenging for us because then we have<00:09:11.580> to<00:09:11.700> kind<00:09:11.880> of<00:09:11.940> make<00:09:12.180> sure<00:09:12.360> that<00:09:12.600> we<00:09:12.899> manage 00:09:13.430 --> 00:09:13.440 align:start position:0% have to kind of make sure that we manage 00:09:13.440 --> 00:09:15.889 align:start position:0% have to kind of make sure that we manage a<00:09:13.560> lot<00:09:13.680> of<00:09:13.800> the<00:09:13.920> technical<00:09:14.279> depth<00:09:14.880> that<00:09:15.180> we<00:09:15.420> uh 00:09:15.889 --> 00:09:15.899 align:start position:0% a lot of the technical depth that we uh 00:09:15.899 --> 00:09:18.350 align:start position:0% a lot of the technical depth that we uh kind<00:09:16.140> of<00:09:16.260> have<00:09:16.740> and<00:09:17.160> are<00:09:17.519> maybe<00:09:17.820> adding 00:09:18.350 --> 00:09:18.360 align:start position:0% kind of have and are maybe adding 00:09:18.360 --> 00:09:21.350 align:start position:0% kind of have and are maybe adding through<00:09:18.720> changing<00:09:19.380> Technologies 00:09:21.350 --> 00:09:21.360 align:start position:0% through changing Technologies 00:09:21.360 --> 00:09:22.970 align:start position:0% through changing Technologies could<00:09:21.720> someone<00:09:22.019> maybe<00:09:22.320> say<00:09:22.500> if<00:09:22.680> they<00:09:22.860> can 00:09:22.970 --> 00:09:22.980 align:start position:0% could someone maybe say if they can 00:09:22.980 --> 00:09:25.490 align:start position:0% could someone maybe say if they can access<00:09:23.160> the<00:09:23.519> repository<00:09:24.060> yeah<00:09:24.480> yeah<00:09:25.019> it 00:09:25.490 --> 00:09:25.500 align:start position:0% access the repository yeah yeah it 00:09:25.500 --> 00:09:27.230 align:start position:0% access the repository yeah yeah it didn't<00:09:26.160> there's<00:09:26.399> a<00:09:26.519> Docker<00:09:26.880> file<00:09:27.000> in<00:09:27.120> the 00:09:27.230 --> 00:09:27.240 align:start position:0% didn't there's a Docker file in the 00:09:27.240 --> 00:09:29.210 align:start position:0% didn't there's a Docker file in the docker<00:09:27.480> compost<00:09:27.720> file<00:09:28.019> in<00:09:28.140> it<00:09:28.320> and<00:09:28.860> if<00:09:29.100> you 00:09:29.210 --> 00:09:29.220 align:start position:0% docker compost file in it and if you 00:09:29.220 --> 00:09:34.269 align:start position:0% docker compost file in it and if you just<00:09:29.519> run<00:09:29.880> Docker<00:09:30.540> com<00:09:30.720> talk<00:09:31.260> compose<00:09:31.860> tool 00:09:34.269 --> 00:09:34.279 align:start position:0% just run Docker com talk compose tool 00:09:34.279 --> 00:09:36.889 align:start position:0% just run Docker com talk compose tool it<00:09:35.279> will<00:09:35.399> pull<00:09:35.580> all<00:09:35.880> the<00:09:36.000> images 00:09:36.889 --> 00:09:36.899 align:start position:0% it will pull all the images 00:09:36.899 --> 00:09:38.930 align:start position:0% it will pull all the images and<00:09:37.500> when<00:09:37.680> we<00:09:37.860> later<00:09:38.040> get<00:09:38.339> to<00:09:38.519> interactive 00:09:38.930 --> 00:09:38.940 align:start position:0% and when we later get to interactive 00:09:38.940 --> 00:09:40.190 align:start position:0% and when we later get to interactive part 00:09:40.190 --> 00:09:40.200 align:start position:0% part 00:09:40.200 --> 00:09:42.230 align:start position:0% part everything<00:09:40.800> will<00:09:41.100> be<00:09:41.279> done 00:09:42.230 --> 00:09:42.240 align:start position:0% everything will be done 00:09:42.240 --> 00:09:46.850 align:start position:0% everything will be done we<00:09:42.959> have<00:09:43.080> all<00:09:43.260> the<00:09:43.380> things<00:09:43.500> ready 00:09:46.850 --> 00:09:46.860 align:start position:0% 00:09:46.860 --> 00:09:49.070 align:start position:0% okay<00:09:47.339> great<00:09:47.640> I<00:09:48.060> hope<00:09:48.180> the<00:09:48.360> internet<00:09:48.480> is<00:09:48.839> good 00:09:49.070 --> 00:09:49.080 align:start position:0% okay great I hope the internet is good 00:09:49.080 --> 00:09:52.009 align:start position:0% okay great I hope the internet is good let's<00:09:49.860> pray<00:09:50.100> a<00:09:50.339> bit<00:09:50.459> because<00:09:50.940> when<00:09:51.600> we<00:09:51.720> tried 00:09:52.009 --> 00:09:52.019 align:start position:0% let's pray a bit because when we tried 00:09:52.019 --> 00:09:54.350 align:start position:0% let's pray a bit because when we tried it<00:09:52.140> or<00:09:52.320> tested<00:09:52.680> it<00:09:52.800> before<00:09:53.040> uh<00:09:53.880> it<00:09:54.060> took<00:09:54.240> a 00:09:54.350 --> 00:09:54.360 align:start position:0% it or tested it before uh it took a 00:09:54.360 --> 00:09:57.530 align:start position:0% it or tested it before uh it took a while<00:09:54.480> so<00:09:55.740> um<00:09:55.800> here<00:09:55.980> you<00:09:56.160> can<00:09:56.279> see<00:09:56.459> I<00:09:57.000> kind<00:09:57.420> of 00:09:57.530 --> 00:09:57.540 align:start position:0% while so um here you can see I kind of 00:09:57.540 --> 00:09:58.970 align:start position:0% while so um here you can see I kind of touched<00:09:58.080> on<00:09:58.200> that 00:09:58.970 --> 00:09:58.980 align:start position:0% touched on that 00:09:58.980 --> 00:10:01.670 align:start position:0% touched on that um<00:09:59.040> the<00:09:59.519> scaling<00:09:59.940> and<00:10:00.180> large<00:10:00.540> table<00:10:00.899> so<00:10:01.260> in 00:10:01.670 --> 00:10:01.680 align:start position:0% um the scaling and large table so in 00:10:01.680 --> 00:10:03.530 align:start position:0% um the scaling and large table so in postgres<00:10:02.160> in<00:10:02.760> the<00:10:02.820> beginning<00:10:02.940> we<00:10:03.240> didn't<00:10:03.360> have 00:10:03.530 --> 00:10:03.540 align:start position:0% postgres in the beginning we didn't have 00:10:03.540 --> 00:10:06.710 align:start position:0% postgres in the beginning we didn't have any<00:10:03.720> partitioning<00:10:04.320> at<00:10:05.040> all<00:10:05.160> so<00:10:05.700> later<00:10:05.940> on<00:10:06.180> when 00:10:06.710 --> 00:10:06.720 align:start position:0% any partitioning at all so later on when 00:10:06.720 --> 00:10:08.930 align:start position:0% any partitioning at all so later on when you<00:10:07.560> can<00:10:07.620> just<00:10:07.740> maybe<00:10:07.920> hold<00:10:08.220> out<00:10:08.459> I<00:10:08.760> can<00:10:08.820> hold 00:10:08.930 --> 00:10:08.940 align:start position:0% you can just maybe hold out I can hold 00:10:08.940 --> 00:10:10.670 align:start position:0% you can just maybe hold out I can hold it<00:10:09.120> up<00:10:09.240> and<00:10:09.480> you<00:10:09.720> can<00:10:09.899> maybe 00:10:10.670 --> 00:10:10.680 align:start position:0% it up and you can maybe 00:10:10.680 --> 00:10:12.769 align:start position:0% it up and you can maybe okay 00:10:12.769 --> 00:10:12.779 align:start position:0% okay 00:10:12.779 --> 00:10:14.690 align:start position:0% okay um<00:10:12.899> again<00:10:13.440> lots<00:10:13.860> of<00:10:13.920> assumptions<00:10:14.339> that<00:10:14.580> we 00:10:14.690 --> 00:10:14.700 align:start position:0% um again lots of assumptions that we 00:10:14.700 --> 00:10:16.310 align:start position:0% um again lots of assumptions that we made<00:10:14.820> without<00:10:15.180> knowing<00:10:15.839> too<00:10:15.959> much<00:10:16.080> of<00:10:16.200> the 00:10:16.310 --> 00:10:16.320 align:start position:0% made without knowing too much of the 00:10:16.320 --> 00:10:18.710 align:start position:0% made without knowing too much of the spec<00:10:16.440> or<00:10:16.680> or<00:10:16.920> your<00:10:17.279> uh<00:10:17.820> specific<00:10:18.300> use<00:10:18.540> case 00:10:18.710 --> 00:10:18.720 align:start position:0% spec or or your uh specific use case 00:10:18.720 --> 00:10:21.410 align:start position:0% spec or or your uh specific use case let's<00:10:19.019> go<00:10:19.200> so<00:10:19.980> Cloud<00:10:20.519> first<00:10:20.820> I<00:10:21.180> think<00:10:21.240> still 00:10:21.410 --> 00:10:21.420 align:start position:0% let's go so Cloud first I think still 00:10:21.420 --> 00:10:23.329 align:start position:0% let's go so Cloud first I think still makes<00:10:21.660> sense<00:10:21.779> especially<00:10:22.200> for<00:10:22.380> like<00:10:22.620> dos<00:10:23.220> or 00:10:23.329 --> 00:10:23.339 align:start position:0% makes sense especially for like dos or 00:10:23.339 --> 00:10:25.130 align:start position:0% makes sense especially for like dos or whatever<00:10:23.399> you<00:10:23.640> guys<00:10:23.700> might<00:10:23.880> need<00:10:24.120> that<00:10:24.360> for 00:10:25.130 --> 00:10:25.140 align:start position:0% whatever you guys might need that for 00:10:25.140 --> 00:10:26.870 align:start position:0% whatever you guys might need that for um<00:10:25.200> in<00:10:25.320> terms<00:10:25.500> of<00:10:25.560> front<00:10:25.860> end<00:10:26.040> I<00:10:26.640> don't<00:10:26.760> know<00:10:26.820> if 00:10:26.870 --> 00:10:26.880 align:start position:0% um in terms of front end I don't know if 00:10:26.880 --> 00:10:28.850 align:start position:0% um in terms of front end I don't know if this<00:10:27.000> is<00:10:27.120> a<00:10:27.300> bottleneck<00:10:27.839> but<00:10:27.959> we<00:10:28.080> mentioned<00:10:28.440> uh 00:10:28.850 --> 00:10:28.860 align:start position:0% this is a bottleneck but we mentioned uh 00:10:28.860 --> 00:10:30.290 align:start position:0% this is a bottleneck but we mentioned uh thought<00:10:29.040> about<00:10:29.220> clustering<00:10:29.760> or<00:10:29.880> some<00:10:30.120> Auto 00:10:30.290 --> 00:10:30.300 align:start position:0% thought about clustering or some Auto 00:10:30.300 --> 00:10:32.329 align:start position:0% thought about clustering or some Auto scale<00:10:30.720> for<00:10:30.899> this<00:10:31.080> or<00:10:31.500> even<00:10:31.620> if<00:10:31.800> we're<00:10:31.920> going<00:10:32.100> to 00:10:32.329 --> 00:10:32.339 align:start position:0% scale for this or even if we're going to 00:10:32.339 --> 00:10:35.090 align:start position:0% scale for this or even if we're going to the<00:10:32.459> web3<00:10:32.760> ethos<00:10:33.300> of<00:10:33.660> let's<00:10:33.899> put<00:10:34.140> this<00:10:34.260> on<00:10:34.440> ipfs 00:10:35.090 --> 00:10:35.100 align:start position:0% the web3 ethos of let's put this on ipfs 00:10:35.100 --> 00:10:37.490 align:start position:0% the web3 ethos of let's put this on ipfs or<00:10:35.580> like<00:10:35.760> distribute<00:10:36.240> it<00:10:36.360> somehow 00:10:37.490 --> 00:10:37.500 align:start position:0% or like distribute it somehow 00:10:37.500 --> 00:10:39.670 align:start position:0% or like distribute it somehow um<00:10:37.620> and<00:10:37.860> merely<00:10:38.160> make<00:10:38.399> it<00:10:38.580> un 00:10:39.670 --> 00:10:39.680 align:start position:0% um and merely make it un 00:10:39.680 --> 00:10:42.889 align:start position:0% um and merely make it un undeniable<00:10:40.680> Service<00:10:41.100> uh<00:10:41.940> scaling<00:10:42.600> that<00:10:42.779> way 00:10:42.889 --> 00:10:42.899 align:start position:0% undeniable Service uh scaling that way 00:10:42.899 --> 00:10:45.710 align:start position:0% undeniable Service uh scaling that way or<00:10:43.560> it<00:10:43.740> could<00:10:43.980> be<00:10:44.160> just<00:10:44.459> some<00:10:45.180> some<00:10:45.420> Auto 00:10:45.710 --> 00:10:45.720 align:start position:0% or it could be just some some Auto 00:10:45.720 --> 00:10:47.810 align:start position:0% or it could be just some some Auto scaling<00:10:46.140> surf<00:10:46.380> Some<00:10:46.620> Cloud<00:10:46.740> run<00:10:47.040> or<00:10:47.220> gcp<00:10:47.700> or 00:10:47.810 --> 00:10:47.820 align:start position:0% scaling surf Some Cloud run or gcp or 00:10:47.820 --> 00:10:49.610 align:start position:0% scaling surf Some Cloud run or gcp or whatever<00:10:48.000> I<00:10:48.480> use<00:10:48.600> for<00:10:48.779> that<00:10:48.839> so<00:10:49.079> I<00:10:49.440> don't<00:10:49.500> think 00:10:49.610 --> 00:10:49.620 align:start position:0% whatever I use for that so I don't think 00:10:49.620 --> 00:10:50.810 align:start position:0% whatever I use for that so I don't think this<00:10:49.740> would<00:10:49.860> be<00:10:49.920> the<00:10:50.040> bottleneck<00:10:50.399> anyways<00:10:50.700> the 00:10:50.810 --> 00:10:50.820 align:start position:0% this would be the bottleneck anyways the 00:10:50.820 --> 00:10:52.670 align:start position:0% this would be the bottleneck anyways the front<00:10:51.000> end<00:10:51.180> itself<00:10:51.540> I<00:10:51.779> think<00:10:51.899> that<00:10:52.019> and<00:10:52.500> if 00:10:52.670 --> 00:10:52.680 align:start position:0% front end itself I think that and if 00:10:52.680 --> 00:10:54.230 align:start position:0% front end itself I think that and if depending<00:10:53.279> on<00:10:53.339> what<00:10:53.579> you<00:10:53.760> have<00:10:53.880> here<00:10:54.060> this 00:10:54.230 --> 00:10:54.240 align:start position:0% depending on what you have here this 00:10:54.240 --> 00:10:55.550 align:start position:0% depending on what you have here this could<00:10:54.420> be<00:10:54.540> heavily 00:10:55.550 --> 00:10:55.560 align:start position:0% could be heavily 00:10:55.560 --> 00:10:57.050 align:start position:0% could be heavily um<00:10:55.620> statically<00:10:56.100> generated<00:10:56.459> so<00:10:56.700> it<00:10:56.820> might<00:10:56.940> be 00:10:57.050 --> 00:10:57.060 align:start position:0% um statically generated so it might be 00:10:57.060 --> 00:10:58.490 align:start position:0% um statically generated so it might be something<00:10:57.240> that<00:10:57.420> you<00:10:57.600> wouldn't<00:10:58.019> be<00:10:58.260> a<00:10:58.380> problem 00:10:58.490 --> 00:10:58.500 align:start position:0% something that you wouldn't be a problem 00:10:58.500 --> 00:11:00.769 align:start position:0% something that you wouldn't be a problem then<00:10:59.459> uh<00:10:59.940> second<00:11:00.120> layer<00:11:00.420> we're<00:11:00.540> talking<00:11:00.660> about 00:11:00.769 --> 00:11:00.779 align:start position:0% then uh second layer we're talking about 00:11:00.779 --> 00:11:02.870 align:start position:0% then uh second layer we're talking about cash<00:11:01.200> so<00:11:01.440> I<00:11:01.560> imagine<00:11:01.680> most<00:11:02.040> people<00:11:02.220> are<00:11:02.640> our 00:11:02.870 --> 00:11:02.880 align:start position:0% cash so I imagine most people are our 00:11:02.880 --> 00:11:04.250 align:start position:0% cash so I imagine most people are our team<00:11:03.060> imagines<00:11:03.480> that<00:11:03.660> most<00:11:03.899> people<00:11:04.079> are 00:11:04.250 --> 00:11:04.260 align:start position:0% team imagines that most people are 00:11:04.260 --> 00:11:06.410 align:start position:0% team imagines that most people are looking<00:11:04.500> at<00:11:04.800> past<00:11:05.040> data<00:11:05.519> so<00:11:05.700> you<00:11:06.300> probably 00:11:06.410 --> 00:11:06.420 align:start position:0% looking at past data so you probably 00:11:06.420 --> 00:11:08.389 align:start position:0% looking at past data so you probably don't<00:11:06.600> have<00:11:06.839> to<00:11:06.959> have<00:11:07.200> uh<00:11:07.620> direct<00:11:07.860> access<00:11:08.160> to 00:11:08.389 --> 00:11:08.399 align:start position:0% don't have to have uh direct access to 00:11:08.399 --> 00:11:09.710 align:start position:0% don't have to have uh direct access to the<00:11:08.519> database<00:11:08.880> you<00:11:09.180> don't<00:11:09.240> have<00:11:09.360> to<00:11:09.480> do<00:11:09.600> like 00:11:09.710 --> 00:11:09.720 align:start position:0% the database you don't have to do like 00:11:09.720 --> 00:11:11.509 align:start position:0% the database you don't have to do like real<00:11:09.899> queries<00:11:10.200> against<00:11:10.320> it<00:11:10.440> you<00:11:10.620> like<00:11:11.160> cash 00:11:11.509 --> 00:11:11.519 align:start position:0% real queries against it you like cash 00:11:11.519 --> 00:11:14.230 align:start position:0% real queries against it you like cash heavily<00:11:12.180> previous<00:11:13.019> data<00:11:13.800> that<00:11:13.920> was<00:11:14.040> already 00:11:14.230 --> 00:11:14.240 align:start position:0% heavily previous data that was already 00:11:14.240 --> 00:11:16.730 align:start position:0% heavily previous data that was already from<00:11:15.240> previous<00:11:15.480> blocks<00:11:16.200> that<00:11:16.320> will<00:11:16.500> never 00:11:16.730 --> 00:11:16.740 align:start position:0% from previous blocks that will never 00:11:16.740 --> 00:11:19.130 align:start position:0% from previous blocks that will never change<00:11:17.040> so<00:11:17.459> things<00:11:17.880> that<00:11:18.120> could<00:11:18.300> be<00:11:18.839> like 00:11:19.130 --> 00:11:19.140 align:start position:0% change so things that could be like 00:11:19.140 --> 00:11:21.230 align:start position:0% change so things that could be like pretty<00:11:19.320> much<00:11:19.680> Frozen<00:11:19.980> there<00:11:20.459> because<00:11:20.760> it's 00:11:21.230 --> 00:11:21.240 align:start position:0% pretty much Frozen there because it's 00:11:21.240 --> 00:11:23.290 align:start position:0% pretty much Frozen there because it's not<00:11:21.420> it's<00:11:21.720> really<00:11:22.079> static<00:11:22.560> and<00:11:22.740> and<00:11:22.920> and<00:11:23.160> and 00:11:23.290 --> 00:11:23.300 align:start position:0% not it's really static and and and and 00:11:23.300 --> 00:11:25.850 align:start position:0% not it's really static and and and and stale<00:11:24.300> deal<00:11:24.480> it's<00:11:24.660> called<00:11:24.779> like<00:11:24.959> that 00:11:25.850 --> 00:11:25.860 align:start position:0% stale deal it's called like that 00:11:25.860 --> 00:11:28.069 align:start position:0% stale deal it's called like that um so<00:11:26.040> this<00:11:26.279> depending<00:11:26.880> I<00:11:27.540> guess<00:11:27.899> there's 00:11:28.069 --> 00:11:28.079 align:start position:0% um so this depending I guess there's 00:11:28.079 --> 00:11:29.150 align:start position:0% um so this depending I guess there's probably<00:11:28.200> lots<00:11:28.560> of<00:11:28.560> ways<00:11:28.740> of<00:11:28.800> doing<00:11:28.980> this 00:11:29.150 --> 00:11:29.160 align:start position:0% probably lots of ways of doing this 00:11:29.160 --> 00:11:30.949 align:start position:0% probably lots of ways of doing this catch<00:11:29.399> layer<00:11:29.640> this<00:11:29.940> could<00:11:30.120> be<00:11:30.180> like<00:11:30.300> a<00:11:30.480> DB 00:11:30.949 --> 00:11:30.959 align:start position:0% catch layer this could be like a DB 00:11:30.959 --> 00:11:32.870 align:start position:0% catch layer this could be like a DB level<00:11:31.200> this<00:11:31.380> could<00:11:31.560> be<00:11:31.680> some<00:11:31.800> like<00:11:31.980> redis<00:11:32.519> cash 00:11:32.870 --> 00:11:32.880 align:start position:0% level this could be some like redis cash 00:11:32.880 --> 00:11:34.009 align:start position:0% level this could be some like redis cash flow<00:11:33.060> or<00:11:33.300> something<00:11:33.420> like<00:11:33.540> that<00:11:33.660> but<00:11:33.899> yeah 00:11:34.009 --> 00:11:34.019 align:start position:0% flow or something like that but yeah 00:11:34.019 --> 00:11:35.329 align:start position:0% flow or something like that but yeah really<00:11:34.200> really<00:11:34.380> something<00:11:34.620> before<00:11:34.860> the<00:11:35.040> data 00:11:35.329 --> 00:11:35.339 align:start position:0% really really something before the data 00:11:35.339 --> 00:11:37.850 align:start position:0% really really something before the data business<00:11:35.459> itself<00:11:35.880> then<00:11:36.420> on<00:11:36.660> database 00:11:37.850 --> 00:11:37.860 align:start position:0% business itself then on database 00:11:37.860 --> 00:11:40.490 align:start position:0% business itself then on database um<00:11:37.980> our<00:11:38.820> friend<00:11:39.060> I<00:11:39.480> forgot<00:11:39.779> his<00:11:39.959> name<00:11:40.140> but<00:11:40.380> our 00:11:40.490 --> 00:11:40.500 align:start position:0% um our friend I forgot his name but our 00:11:40.500 --> 00:11:41.990 align:start position:0% um our friend I forgot his name but our friend<00:11:40.680> there<00:11:40.860> give<00:11:41.100> idea<00:11:41.399> of<00:11:41.519> maybe<00:11:41.700> we<00:11:41.880> can 00:11:41.990 --> 00:11:42.000 align:start position:0% friend there give idea of maybe we can 00:11:42.000 --> 00:11:43.850 align:start position:0% friend there give idea of maybe we can start<00:11:42.120> sharding<00:11:42.540> this<00:11:42.660> maybe<00:11:43.200> some<00:11:43.440> sharding 00:11:43.850 --> 00:11:43.860 align:start position:0% start sharding this maybe some sharding 00:11:43.860 --> 00:11:45.769 align:start position:0% start sharding this maybe some sharding based<00:11:44.160> on<00:11:44.220> transaction<00:11:44.700> hash<00:11:45.240> or<00:11:45.600> something 00:11:45.769 --> 00:11:45.779 align:start position:0% based on transaction hash or something 00:11:45.779 --> 00:11:47.030 align:start position:0% based on transaction hash or something like<00:11:46.019> that<00:11:46.140> which 00:11:47.030 --> 00:11:47.040 align:start position:0% like that which 00:11:47.040 --> 00:11:49.190 align:start position:0% like that which um<00:11:47.100> same<00:11:47.399> thing<00:11:47.519> since<00:11:48.180> this<00:11:48.360> is<00:11:48.540> mostly<00:11:48.839> data 00:11:49.190 --> 00:11:49.200 align:start position:0% um same thing since this is mostly data 00:11:49.200 --> 00:11:50.870 align:start position:0% um same thing since this is mostly data that<00:11:49.320> will<00:11:49.500> live<00:11:49.800> forever<00:11:50.100> and<00:11:50.339> not<00:11:50.459> touch<00:11:50.700> it 00:11:50.870 --> 00:11:50.880 align:start position:0% that will live forever and not touch it 00:11:50.880 --> 00:11:52.190 align:start position:0% that will live forever and not touch it again<00:11:51.000> we<00:11:51.420> probably<00:11:51.600> have<00:11:51.839> a<00:11:51.959> part<00:11:52.079> that's 00:11:52.190 --> 00:11:52.200 align:start position:0% again we probably have a part that's 00:11:52.200 --> 00:11:55.190 align:start position:0% again we probably have a part that's only<00:11:52.380> read<00:11:52.560> only<00:11:52.800> so<00:11:53.100> it's<00:11:53.700> there<00:11:54.540> um<00:11:54.600> very 00:11:55.190 --> 00:11:55.200 align:start position:0% only read only so it's there um very 00:11:55.200 --> 00:11:57.530 align:start position:0% only read only so it's there um very high<00:11:55.560> output<00:11:56.040> for<00:11:56.220> reads<00:11:56.640> uh<00:11:57.060> not<00:11:57.240> that<00:11:57.360> much 00:11:57.530 --> 00:11:57.540 align:start position:0% high output for reads uh not that much 00:11:57.540 --> 00:11:59.870 align:start position:0% high output for reads uh not that much in<00:11:57.720> terms<00:11:57.899> of<00:11:58.019> Rights<00:11:58.740> and<00:11:59.100> a<00:11:59.279> part<00:11:59.519> which<00:11:59.700> will 00:11:59.870 --> 00:11:59.880 align:start position:0% in terms of Rights and a part which will 00:11:59.880 --> 00:12:01.370 align:start position:0% in terms of Rights and a part which will be<00:12:00.060> the<00:12:00.180> right<00:12:00.240> part<00:12:00.420> which<00:12:00.660> this<00:12:00.959> part<00:12:01.140> here 00:12:01.370 --> 00:12:01.380 align:start position:0% be the right part which this part here 00:12:01.380 --> 00:12:03.949 align:start position:0% be the right part which this part here would<00:12:01.920> have<00:12:02.160> more<00:12:02.760> direct<00:12:03.060> access<00:12:03.360> to<00:12:03.720> the 00:12:03.949 --> 00:12:03.959 align:start position:0% would have more direct access to the 00:12:03.959 --> 00:12:06.410 align:start position:0% would have more direct access to the actual<00:12:04.260> nodes<00:12:04.560> and<00:12:05.220> then<00:12:05.339> the<00:12:05.519> nodes 00:12:06.410 --> 00:12:06.420 align:start position:0% actual nodes and then the nodes 00:12:06.420 --> 00:12:08.509 align:start position:0% actual nodes and then the nodes um<00:12:06.540> probably<00:12:07.200> make<00:12:07.620> sense<00:12:07.800> have<00:12:08.040> multiple 00:12:08.509 --> 00:12:08.519 align:start position:0% um probably make sense have multiple 00:12:08.519 --> 00:12:10.910 align:start position:0% um probably make sense have multiple archive<00:12:08.880> nodes<00:12:09.180> if<00:12:09.540> if<00:12:09.720> the<00:12:09.899> RPC<00:12:10.260> calls<00:12:10.440> my<00:12:10.560> be 00:12:10.910 --> 00:12:10.920 align:start position:0% archive nodes if if the RPC calls my be 00:12:10.920 --> 00:12:11.990 align:start position:0% archive nodes if if the RPC calls my be a<00:12:11.100> problem<00:12:11.160> I<00:12:11.399> don't<00:12:11.519> know<00:12:11.519> if<00:12:11.579> it<00:12:11.700> makes<00:12:11.880> sense 00:12:11.990 --> 00:12:12.000 align:start position:0% a problem I don't know if it makes sense 00:12:12.000 --> 00:12:13.069 align:start position:0% a problem I don't know if it makes sense to<00:12:12.180> have<00:12:12.300> lots<00:12:12.660> of<00:12:12.720> different<00:12:12.839> machines 00:12:13.069 --> 00:12:13.079 align:start position:0% to have lots of different machines 00:12:13.079 --> 00:12:14.930 align:start position:0% to have lots of different machines running<00:12:13.260> those<00:12:13.620> instead<00:12:14.399> of<00:12:14.459> inferior 00:12:14.930 --> 00:12:14.940 align:start position:0% running those instead of inferior 00:12:14.940 --> 00:12:16.610 align:start position:0% running those instead of inferior inferior<00:12:15.600> for<00:12:15.720> us<00:12:15.839> in<00:12:16.019> our<00:12:16.140> company<00:12:16.260> is<00:12:16.440> always 00:12:16.610 --> 00:12:16.620 align:start position:0% inferior for us in our company is always 00:12:16.620 --> 00:12:18.949 align:start position:0% inferior for us in our company is always a<00:12:16.860> problem<00:12:16.980> and<00:12:17.160> turn<00:12:17.339> off<00:12:17.640> if<00:12:18.540> there's<00:12:18.660> anyone 00:12:18.949 --> 00:12:18.959 align:start position:0% a problem and turn off if there's anyone 00:12:18.959 --> 00:12:20.690 align:start position:0% a problem and turn off if there's anyone from<00:12:19.140> these<00:12:19.500> companies<00:12:19.800> talk<00:12:20.279> to<00:12:20.459> me<00:12:20.519> please 00:12:20.690 --> 00:12:20.700 align:start position:0% from these companies talk to me please 00:12:20.700 --> 00:12:22.850 align:start position:0% from these companies talk to me please but<00:12:21.839> um<00:12:21.839> yeah<00:12:22.019> maybe<00:12:22.140> just<00:12:22.320> run<00:12:22.500> your<00:12:22.740> own 00:12:22.850 --> 00:12:22.860 align:start position:0% but um yeah maybe just run your own 00:12:22.860 --> 00:12:24.889 align:start position:0% but um yeah maybe just run your own archive<00:12:23.220> notes<00:12:23.519> for<00:12:23.640> these<00:12:23.880> not<00:12:24.300> sure<00:12:24.480> also<00:12:24.779> if 00:12:24.889 --> 00:12:24.899 align:start position:0% archive notes for these not sure also if 00:12:24.899 --> 00:12:27.949 align:start position:0% archive notes for these not sure also if the<00:12:25.320> actual<00:12:25.680> RPC<00:12:26.100> calls<00:12:26.519> are<00:12:26.820> a<00:12:27.240> a<00:12:27.480> bottleneck 00:12:27.949 --> 00:12:27.959 align:start position:0% the actual RPC calls are a a bottleneck 00:12:27.959 --> 00:12:29.750 align:start position:0% the actual RPC calls are a a bottleneck for<00:12:28.140> you<00:12:28.260> guys<00:12:28.320> no<00:12:29.100> it's<00:12:29.279> good<00:12:29.459> to<00:12:29.519> have<00:12:29.640> a 00:12:29.750 --> 00:12:29.760 align:start position:0% for you guys no it's good to have a 00:12:29.760 --> 00:12:31.670 align:start position:0% for you guys no it's good to have a backup<00:12:30.000> okay<00:12:30.480> so<00:12:30.839> at<00:12:31.019> least<00:12:31.200> yeah<00:12:31.320> maybe<00:12:31.560> to 00:12:31.670 --> 00:12:31.680 align:start position:0% backup okay so at least yeah maybe to 00:12:31.680 --> 00:12:32.870 align:start position:0% backup okay so at least yeah maybe to like<00:12:31.860> archive<00:12:32.160> knows<00:12:32.459> you<00:12:32.519> guys<00:12:32.640> are<00:12:32.700> going<00:12:32.820> to 00:12:32.870 --> 00:12:32.880 align:start position:0% like archive knows you guys are going to 00:12:32.880 --> 00:12:34.370 align:start position:0% like archive knows you guys are going to run<00:12:33.000> for<00:12:33.180> that 00:12:34.370 --> 00:12:34.380 align:start position:0% run for that 00:12:34.380 --> 00:12:35.990 align:start position:0% run for that um and<00:12:34.680> then<00:12:34.800> this<00:12:35.160> part<00:12:35.339> here<00:12:35.519> would<00:12:35.700> just<00:12:35.880> be 00:12:35.990 --> 00:12:36.000 align:start position:0% um and then this part here would just be 00:12:36.000 --> 00:12:37.670 align:start position:0% um and then this part here would just be like<00:12:36.120> the<00:12:36.300> heavy<00:12:36.660> right<00:12:36.959> part<00:12:37.260> which 00:12:37.670 --> 00:12:37.680 align:start position:0% like the heavy right part which 00:12:37.680 --> 00:12:39.350 align:start position:0% like the heavy right part which everything<00:12:38.040> that<00:12:38.279> you<00:12:38.399> checked<00:12:38.640> as<00:12:38.820> a<00:12:39.000> new<00:12:39.060> you 00:12:39.350 --> 00:12:39.360 align:start position:0% everything that you checked as a new you 00:12:39.360 --> 00:12:41.030 align:start position:0% everything that you checked as a new you would<00:12:39.480> just<00:12:39.600> update<00:12:39.899> database<00:12:40.260> based<00:12:40.860> on<00:12:40.920> that 00:12:41.030 --> 00:12:41.040 align:start position:0% would just update database based on that 00:12:41.040 --> 00:12:43.190 align:start position:0% would just update database based on that thanks<00:12:41.519> so<00:12:41.700> much<00:12:41.820> okay<00:12:42.300> thanks<00:12:42.959> for 00:12:43.190 --> 00:12:43.200 align:start position:0% thanks so much okay thanks for 00:12:43.200 --> 00:12:44.870 align:start position:0% thanks so much okay thanks for participating 00:12:44.870 --> 00:12:44.880 align:start position:0% participating 00:12:44.880 --> 00:12:47.509 align:start position:0% participating [Applause] 00:12:47.509 --> 00:12:47.519 align:start position:0% [Applause] 00:12:47.519 --> 00:12:52.850 align:start position:0% [Applause] I'm<00:12:48.060> gonna<00:12:48.240> hang<00:12:48.420> that<00:12:48.600> up<00:12:48.839> okay 00:12:52.850 --> 00:12:52.860 align:start position:0% 00:12:52.860 --> 00:12:56.090 align:start position:0% so 00:12:56.090 --> 00:12:56.100 align:start position:0% 00:12:56.100 --> 00:12:58.810 align:start position:0% just<00:12:56.339> a<00:12:56.639> solution<00:12:56.880> we<00:12:57.120> came<00:12:57.300> up<00:12:57.480> with 00:12:58.810 --> 00:12:58.820 align:start position:0% just a solution we came up with 00:12:58.820 --> 00:13:01.790 align:start position:0% just a solution we came up with so<00:12:59.820> we<00:13:00.120> we<00:13:00.480> switched<00:13:00.899> kind<00:13:01.380> of<00:13:01.500> the<00:13:01.560> solution 00:13:01.790 --> 00:13:01.800 align:start position:0% so we we switched kind of the solution 00:13:01.800 --> 00:13:03.470 align:start position:0% so we we switched kind of the solution we<00:13:01.980> have<00:13:02.100> right<00:13:02.339> now<00:13:02.459> yeah<00:13:03.000> this<00:13:03.240> is<00:13:03.360> the 00:13:03.470 --> 00:13:03.480 align:start position:0% we have right now yeah this is the 00:13:03.480 --> 00:13:06.230 align:start position:0% we have right now yeah this is the solution<00:13:03.720> we<00:13:04.019> have<00:13:04.139> right<00:13:04.380> now 00:13:06.230 --> 00:13:06.240 align:start position:0% solution we have right now 00:13:06.240 --> 00:13:10.310 align:start position:0% solution we have right now uh<00:13:07.019> with<00:13:07.440> which<00:13:07.620> we<00:13:08.220> part<00:13:09.060> of<00:13:09.360> the<00:13:09.540> of<00:13:09.839> the<00:13:10.019> of 00:13:10.310 --> 00:13:10.320 align:start position:0% uh with which we part of the of the of 00:13:10.320 --> 00:13:12.050 align:start position:0% uh with which we part of the of the of the<00:13:10.440> of<00:13:10.800> the<00:13:10.980> data<00:13:11.220> set<00:13:11.279> we<00:13:11.519> now<00:13:11.700> store<00:13:11.940> and 00:13:12.050 --> 00:13:12.060 align:start position:0% the of the data set we now store and 00:13:12.060 --> 00:13:13.790 align:start position:0% the of the data set we now store and pick<00:13:12.240> table<00:13:12.420> instead<00:13:12.779> of<00:13:12.839> important<00:13:13.260> postgres 00:13:13.790 --> 00:13:13.800 align:start position:0% pick table instead of important postgres 00:13:13.800 --> 00:13:16.430 align:start position:0% pick table instead of important postgres so<00:13:14.519> we<00:13:15.180> thought<00:13:15.360> like<00:13:15.540> it's<00:13:15.899> not<00:13:16.139> really 00:13:16.430 --> 00:13:16.440 align:start position:0% so we thought like it's not really 00:13:16.440 --> 00:13:18.290 align:start position:0% so we thought like it's not really necessary<00:13:16.920> to<00:13:17.100> have<00:13:17.279> a<00:13:17.459> relational<00:13:17.700> database 00:13:18.290 --> 00:13:18.300 align:start position:0% necessary to have a relational database 00:13:18.300 --> 00:13:20.150 align:start position:0% necessary to have a relational database for<00:13:18.600> this<00:13:18.779> kind<00:13:18.899> of<00:13:19.019> data<00:13:19.380> set 00:13:20.150 --> 00:13:20.160 align:start position:0% for this kind of data set 00:13:20.160 --> 00:13:23.329 align:start position:0% for this kind of data set and<00:13:20.820> bigtable<00:13:21.240> scales<00:13:21.779> really<00:13:22.079> well<00:13:22.320> so<00:13:23.220> I 00:13:23.329 --> 00:13:23.339 align:start position:0% and bigtable scales really well so I 00:13:23.339 --> 00:13:25.730 align:start position:0% and bigtable scales really well so I think<00:13:23.459> that<00:13:23.639> we<00:13:23.880> we<00:13:24.240> were<00:13:24.480> able<00:13:24.779> to 00:13:25.730 --> 00:13:25.740 align:start position:0% think that we we were able to 00:13:25.740 --> 00:13:30.829 align:start position:0% think that we we were able to to<00:13:26.220> indexed<00:13:26.880> uh<00:13:27.180> all<00:13:27.720> of<00:13:28.079> the<00:13:28.200> current<00:13:29.000> uh<00:13:30.000> each 00:13:30.829 --> 00:13:30.839 align:start position:0% to indexed uh all of the current uh each 00:13:30.839 --> 00:13:32.509 align:start position:0% to indexed uh all of the current uh each one<00:13:31.019> transactions 00:13:32.509 --> 00:13:32.519 align:start position:0% one transactions 00:13:32.519 --> 00:13:35.569 align:start position:0% one transactions uh<00:13:33.240> in<00:13:33.480> five<00:13:33.720> hours<00:13:33.959> so<00:13:34.740> it's<00:13:34.920> like<00:13:35.160> really<00:13:35.339> it 00:13:35.569 --> 00:13:35.579 align:start position:0% uh in five hours so it's like really it 00:13:35.579 --> 00:13:37.430 align:start position:0% uh in five hours so it's like really it scales<00:13:36.000> really<00:13:36.240> well<00:13:36.360> depictable 00:13:37.430 --> 00:13:37.440 align:start position:0% scales really well depictable 00:13:37.440 --> 00:13:40.730 align:start position:0% scales really well depictable so<00:13:38.100> we<00:13:39.000> now<00:13:39.240> store 00:13:40.730 --> 00:13:40.740 align:start position:0% so we now store 00:13:40.740 --> 00:13:42.290 align:start position:0% so we now store the<00:13:41.160> blocks 00:13:42.290 --> 00:13:42.300 align:start position:0% the blocks 00:13:42.300 --> 00:13:44.750 align:start position:0% the blocks the<00:13:42.720> balances<00:13:43.139> of<00:13:43.320> the<00:13:43.440> validators<00:13:43.920> every 00:13:44.750 --> 00:13:44.760 align:start position:0% the balances of the validators every 00:13:44.760 --> 00:13:46.389 align:start position:0% the balances of the validators every transaction 00:13:46.389 --> 00:13:46.399 align:start position:0% transaction 00:13:46.399 --> 00:13:51.650 align:start position:0% transaction all<00:13:47.399> of<00:13:47.639> the<00:13:47.940> attestations<00:13:48.420> in<00:13:48.959> bigtable 00:13:51.650 --> 00:13:51.660 align:start position:0% 00:13:51.660 --> 00:13:52.970 align:start position:0% um 00:13:52.970 --> 00:13:52.980 align:start position:0% um 00:13:52.980 --> 00:13:56.750 align:start position:0% um and<00:13:53.760> this<00:13:54.120> resulted<00:13:54.720> in<00:13:54.959> a<00:13:55.200> really<00:13:55.500> much<00:13:56.459> more 00:13:56.750 --> 00:13:56.760 align:start position:0% and this resulted in a really much more 00:13:56.760 --> 00:13:59.150 align:start position:0% and this resulted in a really much more stable 00:13:59.150 --> 00:13:59.160 align:start position:0% stable 00:13:59.160 --> 00:14:03.650 align:start position:0% stable um<00:13:59.279> in<00:14:00.120> index<00:14:00.720> time<00:14:01.019> so<00:14:01.740> now<00:14:02.579> you<00:14:02.940> can<00:14:03.000> see<00:14:03.180> it 00:14:03.650 --> 00:14:03.660 align:start position:0% um in index time so now you can see it 00:14:03.660 --> 00:14:04.670 align:start position:0% um in index time so now you can see it takes<00:14:03.839> us 00:14:04.670 --> 00:14:04.680 align:start position:0% takes us 00:14:04.680 --> 00:14:07.310 align:start position:0% takes us like<00:14:05.220> really<00:14:05.399> Stables<00:14:05.820> 30<00:14:06.120> seconds<00:14:06.420> to<00:14:07.079> export 00:14:07.310 --> 00:14:07.320 align:start position:0% like really Stables 30 seconds to export 00:14:07.320 --> 00:14:13.910 align:start position:0% like really Stables 30 seconds to export all<00:14:07.560> the<00:14:07.680> data<00:14:07.920> of<00:14:08.040> one<00:14:08.220> epoch 00:14:13.910 --> 00:14:13.920 align:start position:0% 00:14:13.920 --> 00:14:16.009 align:start position:0% yeah<00:14:14.399> this<00:14:15.060> is<00:14:15.180> where<00:14:15.360> we<00:14:15.480> come<00:14:15.660> to<00:14:15.839> the 00:14:16.009 --> 00:14:16.019 align:start position:0% yeah this is where we come to the 00:14:16.019 --> 00:14:18.290 align:start position:0% yeah this is where we come to the interactive<00:14:16.620> part<00:14:17.100> of<00:14:17.339> this<00:14:17.639> of<00:14:18.000> this 00:14:18.290 --> 00:14:18.300 align:start position:0% interactive part of this of this 00:14:18.300 --> 00:14:19.670 align:start position:0% interactive part of this of this Workshop 00:14:19.670 --> 00:14:19.680 align:start position:0% Workshop 00:14:19.680 --> 00:14:24.769 align:start position:0% Workshop um<00:14:19.800> for<00:14:20.100> everyone<00:14:20.459> who<00:14:21.180> wants<00:14:21.899> to<00:14:21.899> participate 00:14:24.769 --> 00:14:24.779 align:start position:0% 00:14:24.779 --> 00:14:26.769 align:start position:0% do<00:14:25.440> you<00:14:25.620> think 00:14:26.769 --> 00:14:26.779 align:start position:0% do you think 00:14:26.779 --> 00:14:29.269 align:start position:0% do you think so<00:14:27.779> he's<00:14:28.019> just<00:14:28.200> resetting<00:14:28.740> everything<00:14:29.040> he's 00:14:29.269 --> 00:14:29.279 align:start position:0% so he's just resetting everything he's 00:14:29.279 --> 00:14:31.550 align:start position:0% so he's just resetting everything he's done<00:14:30.000> to<00:14:30.360> kind<00:14:30.600> of<00:14:30.660> start<00:14:30.839> fresh<00:14:31.139> with<00:14:31.380> you 00:14:31.550 --> 00:14:31.560 align:start position:0% done to kind of start fresh with you 00:14:31.560 --> 00:14:34.430 align:start position:0% done to kind of start fresh with you guys 00:14:34.430 --> 00:14:34.440 align:start position:0% 00:14:34.440 --> 00:14:37.850 align:start position:0% so<00:14:34.980> the<00:14:35.220> first<00:14:35.399> thing<00:14:35.579> we<00:14:35.880> we<00:14:36.360> want<00:14:37.019> to<00:14:37.139> do<00:14:37.260> is 00:14:37.850 --> 00:14:37.860 align:start position:0% so the first thing we we want to do is 00:14:37.860 --> 00:14:41.030 align:start position:0% so the first thing we we want to do is to<00:14:38.519> initialize<00:14:39.120> the<00:14:39.480> databases 00:14:41.030 --> 00:14:41.040 align:start position:0% to initialize the databases 00:14:41.040 --> 00:14:44.269 align:start position:0% to initialize the databases so 00:14:44.269 --> 00:14:44.279 align:start position:0% 00:14:44.279 --> 00:14:46.730 align:start position:0% we<00:14:44.699> turn<00:14:44.820> on<00:14:45.000> postgres<00:14:45.540> where<00:14:45.839> it<00:14:46.019> is<00:14:46.139> in<00:14:46.260> Peak 00:14:46.730 --> 00:14:46.740 align:start position:0% we turn on postgres where it is in Peak 00:14:46.740 --> 00:14:50.210 align:start position:0% we turn on postgres where it is in Peak table<00:14:46.860> and<00:14:47.339> initialize<00:14:48.000> the<00:14:48.380> the<00:14:49.380> postgres 00:14:50.210 --> 00:14:50.220 align:start position:0% table and initialize the the postgres 00:14:50.220 --> 00:14:54.530 align:start position:0% table and initialize the the postgres tables<00:14:50.699> and<00:14:50.940> picked<00:14:51.600> the<00:14:52.500> big<00:14:52.860> table<00:14:53.420> what<00:14:54.420> is 00:14:54.530 --> 00:14:54.540 align:start position:0% tables and picked the big table what is 00:14:54.540 --> 00:14:56.509 align:start position:0% tables and picked the big table what is called<00:14:54.720> tables 00:14:56.509 --> 00:14:56.519 align:start position:0% called tables 00:14:56.519 --> 00:15:02.090 align:start position:0% called tables uh<00:14:57.120> database 00:15:02.090 --> 00:15:02.100 align:start position:0% 00:15:02.100 --> 00:15:07.250 align:start position:0% so 00:15:07.250 --> 00:15:07.260 align:start position:0% 00:15:07.260 --> 00:15:09.889 align:start position:0% the<00:15:07.800> next<00:15:07.860> thing<00:15:08.040> we<00:15:08.220> want<00:15:08.339> to<00:15:08.459> do<00:15:08.579> is<00:15:09.060> to<00:15:09.600> start 00:15:09.889 --> 00:15:09.899 align:start position:0% the next thing we want to do is to start 00:15:09.899 --> 00:15:14.710 align:start position:0% the next thing we want to do is to start it<00:15:10.260> one<00:15:10.500> indexer<00:15:11.100> we<00:15:11.699> called<00:15:11.880> it<00:15:12.120> that<00:15:12.300> because 00:15:14.710 --> 00:15:14.720 align:start position:0% 00:15:14.720 --> 00:15:17.170 align:start position:0% we're<00:15:15.720> not<00:15:15.959> really<00:15:16.199> creative 00:15:17.170 --> 00:15:17.180 align:start position:0% we're not really creative 00:15:17.180 --> 00:15:22.189 align:start position:0% we're not really creative but<00:15:18.180> it<00:15:18.720> indexes<00:15:19.260> like<00:15:19.560> I<00:15:19.860> think<00:15:19.980> it<00:15:20.339> it<00:15:20.519> first 00:15:22.189 --> 00:15:22.199 align:start position:0% but it indexes like I think it it first 00:15:22.199 --> 00:15:22.850 align:start position:0% but it indexes like I think it it first um 00:15:22.850 --> 00:15:22.860 align:start position:0% um 00:15:22.860 --> 00:15:24.470 align:start position:0% um gets<00:15:23.399> the<00:15:23.459> blocks 00:15:24.470 --> 00:15:24.480 align:start position:0% gets the blocks 00:15:24.480 --> 00:15:28.310 align:start position:0% gets the blocks from<00:15:25.019> the<00:15:25.320> execution<00:15:26.160> glands 00:15:28.310 --> 00:15:28.320 align:start position:0% from the execution glands 00:15:28.320 --> 00:15:31.370 align:start position:0% from the execution glands um<00:15:28.380> and<00:15:29.160> encoded<00:15:29.940> in<00:15:30.120> protopath<00:15:30.839> and<00:15:31.199> still 00:15:31.370 --> 00:15:31.380 align:start position:0% um and encoded in protopath and still 00:15:31.380 --> 00:15:33.710 align:start position:0% um and encoded in protopath and still using<00:15:31.800> into<00:15:31.980> big<00:15:32.279> table<00:15:32.519> encoded<00:15:33.000> in<00:15:33.120> protobuf 00:15:33.710 --> 00:15:33.720 align:start position:0% using into big table encoded in protobuf 00:15:33.720 --> 00:15:35.389 align:start position:0% using into big table encoded in protobuf and<00:15:34.440> then 00:15:35.389 --> 00:15:35.399 align:start position:0% and then 00:15:35.399 --> 00:15:38.449 align:start position:0% and then we<00:15:35.880> index<00:15:36.300> as<00:15:36.720> after<00:15:37.079> that<00:15:37.380> we<00:15:37.740> index<00:15:38.100> the<00:15:38.279> the 00:15:38.449 --> 00:15:38.459 align:start position:0% we index as after that we index the the 00:15:38.459 --> 00:15:40.550 align:start position:0% we index as after that we index the the blocks<00:15:38.940> with<00:15:39.480> all<00:15:39.720> the<00:15:39.899> the<00:15:40.079> fields<00:15:40.440> and 00:15:40.550 --> 00:15:40.560 align:start position:0% blocks with all the the fields and 00:15:40.560 --> 00:15:41.629 align:start position:0% blocks with all the the fields and values 00:15:41.629 --> 00:15:41.639 align:start position:0% values 00:15:41.639 --> 00:15:48.129 align:start position:0% values and<00:15:42.000> then<00:15:42.120> transaction<00:15:42.540> as<00:15:42.779> well<00:15:43.440> so 00:15:48.129 --> 00:15:48.139 align:start position:0% 00:15:48.139 --> 00:15:49.970 align:start position:0% one 00:15:49.970 --> 00:15:49.980 align:start position:0% one 00:15:49.980 --> 00:15:52.550 align:start position:0% one one<00:15:50.339> big<00:15:50.639> thing<00:15:50.880> is<00:15:51.120> like<00:15:51.480> we're<00:15:52.139> actually<00:15:52.320> not 00:15:52.550 --> 00:15:52.560 align:start position:0% one big thing is like we're actually not 00:15:52.560 --> 00:15:55.610 align:start position:0% one big thing is like we're actually not using<00:15:52.980> bigtable<00:15:53.399> from<00:15:53.760> from<00:15:54.060> Google<00:15:54.360> chart<00:15:54.720> we 00:15:55.610 --> 00:15:55.620 align:start position:0% using bigtable from from Google chart we 00:15:55.620 --> 00:15:58.090 align:start position:0% using bigtable from from Google chart we are<00:15:55.800> using 00:15:58.090 --> 00:15:58.100 align:start position:0% are using 00:15:58.100 --> 00:16:01.550 align:start position:0% are using emulator<00:15:59.100> from<00:15:59.880> the<00:16:00.120> company<00:16:00.360> P<00:16:00.720> key 00:16:01.550 --> 00:16:01.560 align:start position:0% emulator from the company P key 00:16:01.560 --> 00:16:03.069 align:start position:0% emulator from the company P key what's<00:16:01.980> up 00:16:03.069 --> 00:16:03.079 align:start position:0% what's up 00:16:03.079 --> 00:16:06.710 align:start position:0% what's up it<00:16:04.079> just<00:16:04.380> emulates<00:16:04.860> the<00:16:05.220> the<00:16:05.519> peak<00:16:05.940> table<00:16:06.060> API 00:16:06.710 --> 00:16:06.720 align:start position:0% it just emulates the the peak table API 00:16:06.720 --> 00:16:09.350 align:start position:0% it just emulates the the peak table API and<00:16:06.959> stores<00:16:07.199> it<00:16:07.500> in<00:16:07.680> sqlite<00:16:08.339> database 00:16:09.350 --> 00:16:09.360 align:start position:0% and stores it in sqlite database 00:16:09.360 --> 00:16:12.829 align:start position:0% and stores it in sqlite database and<00:16:09.959> I<00:16:10.139> think<00:16:10.260> like<00:16:10.500> for 00:16:12.829 --> 00:16:12.839 align:start position:0% 00:16:12.839 --> 00:16:16.430 align:start position:0% for<00:16:13.560> just<00:16:14.459> storing<00:16:15.000> and<00:16:15.480> then<00:16:15.660> analyzing<00:16:16.260> the 00:16:16.430 --> 00:16:16.440 align:start position:0% for just storing and then analyzing the 00:16:16.440 --> 00:16:18.710 align:start position:0% for just storing and then analyzing the data<00:16:16.800> it<00:16:17.160> works<00:16:17.399> well<00:16:17.519> it's<00:16:17.940> not<00:16:18.060> like<00:16:18.300> it<00:16:18.600> will 00:16:18.710 --> 00:16:18.720 align:start position:0% data it works well it's not like it will 00:16:18.720 --> 00:16:20.689 align:start position:0% data it works well it's not like it will not<00:16:18.899> scale<00:16:19.260> for<00:16:19.740> uh 00:16:20.689 --> 00:16:20.699 align:start position:0% not scale for uh 00:16:20.699 --> 00:16:23.269 align:start position:0% not scale for uh for<00:16:21.240> a<00:16:21.360> thousand<00:16:21.660> requests<00:16:22.139> per<00:16:22.260> second<00:16:22.440> but 00:16:23.269 --> 00:16:23.279 align:start position:0% for a thousand requests per second but 00:16:23.279 --> 00:16:25.490 align:start position:0% for a thousand requests per second but for<00:16:23.699> analyzing<00:16:24.240> the<00:16:24.360> data<00:16:24.600> it's<00:16:24.959> a<00:16:25.139> like<00:16:25.380> a 00:16:25.490 --> 00:16:25.500 align:start position:0% for analyzing the data it's a like a 00:16:25.500 --> 00:16:26.930 align:start position:0% for analyzing the data it's a like a really<00:16:25.620> good<00:16:25.800> solution<00:16:26.100> solution<00:16:26.579> in<00:16:26.820> our 00:16:26.930 --> 00:16:26.940 align:start position:0% really good solution solution in our 00:16:26.940 --> 00:16:34.990 align:start position:0% really good solution solution in our opinion 00:16:34.990 --> 00:16:35.000 align:start position:0% 00:16:35.000 --> 00:16:38.090 align:start position:0% so<00:16:36.000> the<00:16:36.720> the<00:16:36.899> thing<00:16:37.139> here<00:16:37.320> is 00:16:38.090 --> 00:16:38.100 align:start position:0% so the the thing here is 00:16:38.100 --> 00:16:42.170 align:start position:0% so the the thing here is we<00:16:38.940> are<00:16:39.120> not<00:16:39.300> able<00:16:39.660> to 00:16:42.170 --> 00:16:42.180 align:start position:0% we are not able to 00:16:42.180 --> 00:16:46.129 align:start position:0% we are not able to to<00:16:42.660> reach<00:16:43.440> the<00:16:43.680> nodes<00:16:44.100> we<00:16:44.639> we<00:16:45.180> think<00:16:45.839> before 00:16:46.129 --> 00:16:46.139 align:start position:0% to reach the nodes we we think before 00:16:46.139 --> 00:16:50.449 align:start position:0% to reach the nodes we we think before the<00:16:46.680> the<00:16:46.980> workshop<00:16:47.459> in<00:16:48.180> the<00:16:48.300> cloud<00:16:48.860> somehow<00:16:49.860> we 00:16:50.449 --> 00:16:50.459 align:start position:0% the the workshop in the cloud somehow we 00:16:50.459 --> 00:16:52.790 align:start position:0% the the workshop in the cloud somehow we don't<00:16:50.639> get<00:16:50.940> access<00:16:51.540> we<00:16:52.019> have<00:16:52.259> this<00:16:52.380> wi-fi<00:16:52.680> fan 00:16:52.790 --> 00:16:52.800 align:start position:0% don't get access we have this wi-fi fan 00:16:52.800 --> 00:16:55.550 align:start position:0% don't get access we have this wi-fi fan so<00:16:53.459> we<00:16:53.759> are<00:16:53.940> now<00:16:54.120> running<00:16:54.360> the<00:16:54.660> nodes 00:16:55.550 --> 00:16:55.560 align:start position:0% so we are now running the nodes 00:16:55.560 --> 00:16:58.550 align:start position:0% so we are now running the nodes on<00:16:56.040> our<00:16:56.100> laptops<00:16:56.639> and<00:16:57.120> that<00:16:57.360> is<00:16:57.540> where<00:16:58.259> you<00:16:58.440> see 00:16:58.550 --> 00:16:58.560 align:start position:0% on our laptops and that is where you see 00:16:58.560 --> 00:17:01.129 align:start position:0% on our laptops and that is where you see some<00:16:58.860> errors<00:16:59.759> because<00:17:00.180> the<00:17:00.660> nodes<00:17:00.779> are<00:17:01.019> not 00:17:01.129 --> 00:17:01.139 align:start position:0% some errors because the nodes are not 00:17:01.139 --> 00:17:04.069 align:start position:0% some errors because the nodes are not synced<00:17:01.560> and<00:17:01.740> it<00:17:02.100> it's<00:17:02.759> not<00:17:02.940> like<00:17:03.180> doesn't<00:17:03.779> work 00:17:04.069 --> 00:17:04.079 align:start position:0% synced and it it's not like doesn't work 00:17:04.079 --> 00:17:05.990 align:start position:0% synced and it it's not like doesn't work well<00:17:04.319> but 00:17:05.990 --> 00:17:06.000 align:start position:0% well but 00:17:06.000 --> 00:17:15.640 align:start position:0% well but foreign 00:17:15.640 --> 00:17:15.650 align:start position:0% 00:17:15.650 --> 00:17:22.150 align:start position:0% [Music] 00:17:22.150 --> 00:17:22.160 align:start position:0% 00:17:22.160 --> 00:17:24.710 align:start position:0% index<00:17:23.160> around<00:17:23.400> me<00:17:23.640> the<00:17:24.120> next<00:17:24.240> thing<00:17:24.360> we<00:17:24.540> want 00:17:24.710 --> 00:17:24.720 align:start position:0% index around me the next thing we want 00:17:24.720 --> 00:17:29.330 align:start position:0% index around me the next thing we want to<00:17:24.839> run<00:17:25.199> is<00:17:25.559> the 00:17:29.330 --> 00:17:29.340 align:start position:0% 00:17:29.340 --> 00:17:31.730 align:start position:0% exporter 00:17:31.730 --> 00:17:31.740 align:start position:0% exporter 00:17:31.740 --> 00:17:33.530 align:start position:0% exporter the<00:17:32.100> exporter<00:17:32.520> is<00:17:32.700> like<00:17:32.820> truster<00:17:33.299> and<00:17:33.419> the 00:17:33.530 --> 00:17:33.540 align:start position:0% the exporter is like truster and the 00:17:33.540 --> 00:17:36.590 align:start position:0% the exporter is like truster and the export<00:17:33.780> we<00:17:34.080> had<00:17:34.260> before<00:17:34.559> the<00:17:35.340> merge 00:17:36.590 --> 00:17:36.600 align:start position:0% export we had before the merge 00:17:36.600 --> 00:17:40.430 align:start position:0% export we had before the merge but<00:17:37.140> now<00:17:37.380> it<00:17:37.799> will<00:17:38.059> index<00:17:39.059> the 00:17:40.430 --> 00:17:40.440 align:start position:0% but now it will index the 00:17:40.440 --> 00:17:43.130 align:start position:0% but now it will index the the<00:17:40.919> blocks<00:17:41.340> from<00:17:41.580> the 00:17:43.130 --> 00:17:43.140 align:start position:0% the blocks from the 00:17:43.140 --> 00:17:45.830 align:start position:0% the blocks from the from<00:17:43.740> the<00:17:44.039> from<00:17:44.520> the<00:17:44.700> big<00:17:44.820> table<00:17:45.000> that<00:17:45.360> we<00:17:45.539> just 00:17:45.830 --> 00:17:45.840 align:start position:0% from the from the big table that we just 00:17:45.840 --> 00:17:50.570 align:start position:0% from the from the big table that we just exported<00:17:46.559> in<00:17:46.799> the<00:17:46.919> in<00:17:47.100> the<00:17:47.340> 81<00:17:47.700> induction 00:17:50.570 --> 00:17:50.580 align:start position:0% 00:17:50.580 --> 00:17:52.490 align:start position:0% again<00:17:51.059> we<00:17:51.360> have<00:17:51.419> some<00:17:51.600> errors<00:17:52.020> because<00:17:52.260> the 00:17:52.490 --> 00:17:52.500 align:start position:0% again we have some errors because the 00:17:52.500 --> 00:17:54.470 align:start position:0% again we have some errors because the notes<00:17:52.740> are<00:17:52.799> not<00:17:52.919> synced 00:17:54.470 --> 00:17:54.480 align:start position:0% notes are not synced 00:17:54.480 --> 00:17:56.710 align:start position:0% notes are not synced the<00:17:55.020> next<00:17:55.140> thing<00:17:55.320> is<00:17:55.500> like<00:17:55.919> the<00:17:56.220> the 00:17:56.710 --> 00:17:56.720 align:start position:0% the next thing is like the the 00:17:56.720 --> 00:18:00.169 align:start position:0% the next thing is like the the statistics<00:17:57.720> module<00:17:58.140> module<00:17:58.620> and<00:17:59.580> this<00:18:00.059> is 00:18:00.169 --> 00:18:00.179 align:start position:0% statistics module module and this is 00:18:00.179 --> 00:18:02.990 align:start position:0% statistics module module and this is also<00:18:00.539> a<00:18:00.840> really<00:18:00.960> important<00:18:01.500> uh<00:18:02.220> and<00:18:02.460> integral 00:18:02.990 --> 00:18:03.000 align:start position:0% also a really important uh and integral 00:18:03.000 --> 00:18:06.770 align:start position:0% also a really important uh and integral part<00:18:03.660> of<00:18:03.840> the<00:18:04.020> whole<00:18:04.140> project<00:18:04.440> because 00:18:06.770 --> 00:18:06.780 align:start position:0% part of the whole project because 00:18:06.780 --> 00:18:09.650 align:start position:0% part of the whole project because the<00:18:07.200> indexer<00:18:07.620> will<00:18:07.799> aggregate<00:18:08.340> the<00:18:08.460> data 00:18:09.650 --> 00:18:09.660 align:start position:0% the indexer will aggregate the data 00:18:09.660 --> 00:18:11.570 align:start position:0% the indexer will aggregate the data one<00:18:10.260> day 00:18:11.570 --> 00:18:11.580 align:start position:0% one day 00:18:11.580 --> 00:18:14.270 align:start position:0% one day and<00:18:12.240> store<00:18:12.539> the<00:18:13.020> aggregated<00:18:13.440> data<00:18:13.799> of<00:18:13.919> the<00:18:14.100> one 00:18:14.270 --> 00:18:14.280 align:start position:0% and store the aggregated data of the one 00:18:14.280 --> 00:18:16.909 align:start position:0% and store the aggregated data of the one of<00:18:14.520> of<00:18:14.840> one<00:18:15.840> Beacon<00:18:16.200> chain<00:18:16.380> there<00:18:16.620> in<00:18:16.860> the 00:18:16.909 --> 00:18:16.919 align:start position:0% of of one Beacon chain there in the 00:18:16.919 --> 00:18:19.190 align:start position:0% of of one Beacon chain there in the database<00:18:17.280> and<00:18:17.640> so<00:18:17.760> it<00:18:18.120> all<00:18:18.660> the<00:18:18.840> queries 00:18:19.190 --> 00:18:19.200 align:start position:0% database and so it all the queries 00:18:19.200 --> 00:18:28.789 align:start position:0% database and so it all the queries become<00:18:19.440> much<00:18:19.679> faster 00:18:28.789 --> 00:18:28.799 align:start position:0% 00:18:28.799 --> 00:18:33.590 align:start position:0% the<00:18:29.520> last<00:18:29.700> thing<00:18:29.820> we<00:18:29.940> start<00:18:30.120> is<00:18:30.299> the<00:18:30.480> front<00:18:30.600> end 00:18:33.590 --> 00:18:33.600 align:start position:0% 00:18:33.600 --> 00:18:35.690 align:start position:0% and<00:18:33.780> we'll<00:18:34.020> get<00:18:34.260> started<00:18:34.559> with<00:18:34.740> the 00:18:35.690 --> 00:18:35.700 align:start position:0% and we'll get started with the 00:18:35.700 --> 00:18:38.210 align:start position:0% and we'll get started with the with<00:18:36.000> the<00:18:36.299> cache<00:18:36.600> up<00:18:36.720> data<00:18:37.200> and<00:18:37.679> then<00:18:37.919> the 00:18:38.210 --> 00:18:38.220 align:start position:0% with the cache up data and then the 00:18:38.220 --> 00:18:40.789 align:start position:0% with the cache up data and then the front-end<00:18:38.520> itself<00:18:38.760> which<00:18:39.120> is<00:18:39.299> a<00:18:39.600> golang<00:18:40.500> web 00:18:40.789 --> 00:18:40.799 align:start position:0% front-end itself which is a golang web 00:18:40.799 --> 00:18:43.010 align:start position:0% front-end itself which is a golang web server<00:18:41.160> which<00:18:41.820> just<00:18:42.120> queries<00:18:42.600> all<00:18:42.900> the 00:18:43.010 --> 00:18:43.020 align:start position:0% server which just queries all the 00:18:43.020 --> 00:18:46.310 align:start position:0% server which just queries all the databases<00:18:43.980> so<00:18:44.820> all<00:18:45.660> the<00:18:45.840> things<00:18:45.960> are<00:18:46.140> running 00:18:46.310 --> 00:18:46.320 align:start position:0% databases so all the things are running 00:18:46.320 --> 00:18:48.049 align:start position:0% databases so all the things are running now 00:18:48.049 --> 00:18:48.059 align:start position:0% now 00:18:48.059 --> 00:18:50.150 align:start position:0% now and<00:18:48.720> we<00:18:48.900> can<00:18:49.080> browse<00:18:49.559> the<00:18:49.740> pink<00:18:49.919> chain 00:18:50.150 --> 00:18:50.160 align:start position:0% and we can browse the pink chain 00:18:50.160 --> 00:18:51.590 align:start position:0% and we can browse the pink chain Explorer 00:18:51.590 --> 00:18:51.600 align:start position:0% Explorer 00:18:51.600 --> 00:18:55.130 align:start position:0% Explorer on<00:18:52.020> localhost<00:18:52.440> 8080<00:18:53.160> the<00:18:54.000> thing<00:18:54.179> is 00:18:55.130 --> 00:18:55.140 align:start position:0% on localhost 8080 the thing is 00:18:55.140 --> 00:18:58.549 align:start position:0% on localhost 8080 the thing is since<00:18:55.620> the<00:18:55.919> nodes<00:18:56.160> are<00:18:56.400> not<00:18:56.520> synced 00:18:58.549 --> 00:18:58.559 align:start position:0% since the nodes are not synced 00:18:58.559 --> 00:19:01.789 align:start position:0% since the nodes are not synced um<00:18:58.620> it<00:18:59.160> will<00:18:59.280> take<00:18:59.460> some<00:18:59.700> time<00:18:59.940> until<00:19:00.600> any<00:19:01.260> data 00:19:01.789 --> 00:19:01.799 align:start position:0% um it will take some time until any data 00:19:01.799 --> 00:19:04.549 align:start position:0% um it will take some time until any data will<00:19:02.039> show<00:19:02.220> up 00:19:04.549 --> 00:19:04.559 align:start position:0% 00:19:04.559 --> 00:19:07.070 align:start position:0% um 00:19:07.070 --> 00:19:07.080 align:start position:0% 00:19:07.080 --> 00:19:16.510 align:start position:0% this<00:19:07.740> one 00:19:16.510 --> 00:19:16.520 align:start position:0% 00:19:16.520 --> 00:19:22.990 align:start position:0% there's<00:19:17.520> some<00:19:17.760> extra<00:19:17.940> extra<00:19:18.919> scripts<00:19:19.919> we 00:19:22.990 --> 00:19:23.000 align:start position:0% 00:19:23.000 --> 00:19:26.930 align:start position:0% we<00:19:24.000> wrote<00:19:24.240> in<00:19:24.480> into<00:19:24.660> the<00:19:24.960> into<00:19:25.200> the<00:19:25.500> into<00:19:26.460> the 00:19:26.930 --> 00:19:26.940 align:start position:0% we wrote in into the into the into the 00:19:26.940 --> 00:19:29.990 align:start position:0% we wrote in into the into the into the another<00:19:27.179> main<00:19:27.539> script<00:19:28.320> um 00:19:29.990 --> 00:19:30.000 align:start position:0% another main script um 00:19:30.000 --> 00:19:32.810 align:start position:0% another main script um the<00:19:30.360> thing<00:19:30.419> is<00:19:30.600> like<00:19:30.780> we<00:19:31.440> we<00:19:31.799> understand<00:19:32.460> like 00:19:32.810 --> 00:19:32.820 align:start position:0% the thing is like we we understand like 00:19:32.820 --> 00:19:37.730 align:start position:0% the thing is like we we understand like this<00:19:33.000> repository<00:19:33.539> not<00:19:33.900> as<00:19:34.580> we<00:19:35.580> want<00:19:36.059> to<00:19:36.240> to<00:19:36.840> to 00:19:37.730 --> 00:19:37.740 align:start position:0% this repository not as we want to to to 00:19:37.740 --> 00:19:40.730 align:start position:0% this repository not as we want to to to make<00:19:38.039> it<00:19:38.220> the<00:19:38.700> big<00:19:39.059> change<00:19:39.299> for<00:19:39.660> available<00:19:40.200> for 00:19:40.730 --> 00:19:40.740 align:start position:0% make it the big change for available for 00:19:40.740 --> 00:19:43.070 align:start position:0% make it the big change for available for everyone<00:19:41.039> who<00:19:41.400> wants<00:19:41.700> to<00:19:41.820> to<00:19:42.240> explore<00:19:42.600> the<00:19:42.900> big 00:19:43.070 --> 00:19:43.080 align:start position:0% everyone who wants to to explore the big 00:19:43.080 --> 00:19:47.029 align:start position:0% everyone who wants to to explore the big engine<00:19:43.559> not 00:19:47.029 --> 00:19:47.039 align:start position:0% 00:19:47.039 --> 00:19:49.310 align:start position:0% so<00:19:47.520> you<00:19:47.760> don't<00:19:47.820> have<00:19:48.000> to<00:19:48.179> trust<00:19:48.360> us 00:19:49.310 --> 00:19:49.320 align:start position:0% so you don't have to trust us 00:19:49.320 --> 00:19:52.789 align:start position:0% so you don't have to trust us by<00:19:49.799> going<00:19:49.980> to<00:19:50.160> Beacon<00:19:50.520> chain<00:19:51.080> uh<00:19:52.080> we<00:19:52.260> can<00:19:52.500> begin 00:19:52.789 --> 00:19:52.799 align:start position:0% by going to Beacon chain uh we can begin 00:19:52.799 --> 00:19:59.690 align:start position:0% by going to Beacon chain uh we can begin chain<00:19:53.460> we<00:19:54.120> can<00:19:54.240> change<00:19:54.480> beacon.in 00:19:59.690 --> 00:19:59.700 align:start position:0% 00:19:59.700 --> 00:20:02.930 align:start position:0% you<00:20:00.360> can<00:20:00.539> run<00:20:00.660> it<00:20:00.900> yourself 00:20:02.930 --> 00:20:02.940 align:start position:0% you can run it yourself 00:20:02.940 --> 00:20:05.270 align:start position:0% you can run it yourself it<00:20:03.419> will<00:20:03.539> take<00:20:03.720> some<00:20:03.960> time<00:20:04.140> until<00:20:04.559> it's<00:20:04.980> like 00:20:05.270 --> 00:20:05.280 align:start position:0% it will take some time until it's like 00:20:05.280 --> 00:20:09.590 align:start position:0% it will take some time until it's like synced<00:20:05.700> and<00:20:06.059> we<00:20:06.240> will 00:20:09.590 --> 00:20:09.600 align:start position:0% 00:20:09.600 --> 00:20:11.870 align:start position:0% we<00:20:10.020> will<00:20:10.140> try<00:20:10.320> to<00:20:10.500> make<00:20:10.679> it<00:20:10.799> more<00:20:10.919> easy 00:20:11.870 --> 00:20:11.880 align:start position:0% we will try to make it more easy 00:20:11.880 --> 00:20:15.230 align:start position:0% we will try to make it more easy but<00:20:12.480> the<00:20:12.840> thing<00:20:13.020> is<00:20:13.200> we<00:20:14.160> really 00:20:15.230 --> 00:20:15.240 align:start position:0% but the thing is we really 00:20:15.240 --> 00:20:18.650 align:start position:0% but the thing is we really um<00:20:15.299> what<00:20:15.900> does<00:20:16.140> it<00:20:16.260> saying 00:20:18.650 --> 00:20:18.660 align:start position:0% 00:20:18.660 --> 00:20:20.750 align:start position:0% We<00:20:19.080> Stand<00:20:19.260> by<00:20:19.500> the<00:20:19.679> decision<00:20:20.039> to<00:20:20.340> make<00:20:20.520> the 00:20:20.750 --> 00:20:20.760 align:start position:0% We Stand by the decision to make the 00:20:20.760 --> 00:20:22.850 align:start position:0% We Stand by the decision to make the secure<00:20:21.179> open<00:20:21.419> source<00:20:21.900> so<00:20:22.080> it's<00:20:22.200> not<00:20:22.380> we<00:20:22.679> will 00:20:22.850 --> 00:20:22.860 align:start position:0% secure open source so it's not we will 00:20:22.860 --> 00:20:25.549 align:start position:0% secure open source so it's not we will we<00:20:23.160> will<00:20:23.340> try<00:20:23.580> to<00:20:23.760> to<00:20:24.120> make<00:20:24.780> it<00:20:24.960> available<00:20:25.140> for 00:20:25.549 --> 00:20:25.559 align:start position:0% we will try to to make it available for 00:20:25.559 --> 00:20:27.770 align:start position:0% we will try to to make it available for everyone<00:20:25.740> it's<00:20:26.220> not<00:20:26.400> like<00:20:26.640> we<00:20:27.419> made<00:20:27.660> the 00:20:27.770 --> 00:20:27.780 align:start position:0% everyone it's not like we made the 00:20:27.780 --> 00:20:30.230 align:start position:0% everyone it's not like we made the decision<00:20:28.080> to<00:20:28.320> go<00:20:28.440> into<00:20:28.740> bigtable<00:20:29.280> from<00:20:30.059> from 00:20:30.230 --> 00:20:30.240 align:start position:0% decision to go into bigtable from from 00:20:30.240 --> 00:20:35.210 align:start position:0% decision to go into bigtable from from Google<00:20:30.780> and<00:20:31.620> to<00:20:31.799> run<00:20:31.980> it<00:20:32.100> in<00:20:32.220> gcp<00:20:32.840> just<00:20:33.840> to 00:20:35.210 --> 00:20:35.220 align:start position:0% Google and to run it in gcp just to 00:20:35.220 --> 00:20:38.570 align:start position:0% Google and to run it in gcp just to to<00:20:35.640> make<00:20:35.880> the<00:20:36.059> scaling<00:20:36.419> issue<00:20:37.020> like<00:20:37.260> gone 00:20:38.570 --> 00:20:38.580 align:start position:0% to make the scaling issue like gone 00:20:38.580 --> 00:20:41.630 align:start position:0% to make the scaling issue like gone but<00:20:39.360> that<00:20:39.840> doesn't<00:20:39.960> mean<00:20:40.200> it's<00:20:40.679> it's<00:20:41.340> not 00:20:41.630 --> 00:20:41.640 align:start position:0% but that doesn't mean it's it's not 00:20:41.640 --> 00:20:44.930 align:start position:0% but that doesn't mean it's it's not available<00:20:41.820> for<00:20:42.299> everyone 00:20:44.930 --> 00:20:44.940 align:start position:0% 00:20:44.940 --> 00:20:47.029 align:start position:0% thanks<00:20:45.419> to<00:20:45.720> such<00:20:45.960> amazing<00:20:46.380> open<00:20:46.679> source 00:20:47.029 --> 00:20:47.039 align:start position:0% thanks to such amazing open source 00:20:47.039 --> 00:20:50.810 align:start position:0% thanks to such amazing open source projects<00:20:47.820> like<00:20:47.940> from<00:20:48.240> bitly<00:20:48.960> the<00:20:49.820> gcp 00:20:50.810 --> 00:20:50.820 align:start position:0% projects like from bitly the gcp 00:20:50.820 --> 00:20:52.669 align:start position:0% projects like from bitly the gcp emulator 00:20:52.669 --> 00:20:52.679 align:start position:0% emulator 00:20:52.679 --> 00:20:55.669 align:start position:0% emulator so<00:20:53.100> the<00:20:53.460> last<00:20:53.640> script<00:20:54.059> is 00:20:55.669 --> 00:20:55.679 align:start position:0% so the last script is 00:20:55.679 --> 00:20:59.090 align:start position:0% so the last script is now<00:20:56.340> you<00:20:56.760> have<00:20:56.880> like<00:20:57.120> a<00:20:57.299> postgres<00:20:57.660> database 00:20:59.090 --> 00:20:59.100 align:start position:0% now you have like a postgres database 00:20:59.100 --> 00:21:01.970 align:start position:0% now you have like a postgres database where<00:20:59.700> you<00:20:59.880> can<00:21:00.000> think<00:21:00.120> with<00:21:00.419> the<00:21:00.600> data 00:21:01.970 --> 00:21:01.980 align:start position:0% where you can think with the data 00:21:01.980 --> 00:21:05.390 align:start position:0% where you can think with the data we<00:21:02.520> made<00:21:02.760> just<00:21:03.059> some 00:21:05.390 --> 00:21:05.400 align:start position:0% we made just some 00:21:05.400 --> 00:21:10.870 align:start position:0% we made just some hmm 00:21:10.870 --> 00:21:10.880 align:start position:0% 00:21:10.880 --> 00:21:15.470 align:start position:0% the<00:21:11.880> script<00:21:12.000> is<00:21:12.179> not<00:21:12.360> uploaded 00:21:15.470 --> 00:21:15.480 align:start position:0% 00:21:15.480 --> 00:21:25.510 align:start position:0% no<00:21:15.960> it<00:21:16.260> is 00:21:25.510 --> 00:21:25.520 align:start position:0% 00:21:25.520 --> 00:21:36.470 align:start position:0% yeah<00:21:26.520> okay 00:21:36.470 --> 00:21:36.480 align:start position:0% 00:21:36.480 --> 00:21:39.549 align:start position:0% let's<00:21:36.960> restart<00:21:37.260> the<00:21:37.620> services 00:21:39.549 --> 00:21:39.559 align:start position:0% let's restart the services 00:21:39.559 --> 00:21:43.730 align:start position:0% let's restart the services I<00:21:40.559> don't<00:21:40.799> know<00:21:40.980> if<00:21:41.159> I<00:21:41.340> want<00:21:41.460> to<00:21:41.580> do<00:21:41.700> that 00:21:43.730 --> 00:21:43.740 align:start position:0% I don't know if I want to do that 00:21:43.740 --> 00:21:46.370 align:start position:0% I don't know if I want to do that has<00:21:44.400> anyone<00:21:44.700> followed<00:21:45.059> a<00:21:45.240> lot<00:21:45.360> is<00:21:46.080> anyone 00:21:46.370 --> 00:21:46.380 align:start position:0% has anyone followed a lot is anyone 00:21:46.380 --> 00:21:47.750 align:start position:0% has anyone followed a lot is anyone following<00:21:46.740> along 00:21:47.750 --> 00:21:47.760 align:start position:0% following along 00:21:47.760 --> 00:21:50.330 align:start position:0% following along is<00:21:48.240> it<00:21:48.360> working<00:21:48.539> well<00:21:48.919> okay<00:21:49.919> it's<00:21:50.159> working 00:21:50.330 --> 00:21:50.340 align:start position:0% is it working well okay it's working 00:21:50.340 --> 00:21:54.649 align:start position:0% is it working well okay it's working yeah 00:21:54.649 --> 00:21:54.659 align:start position:0% 00:21:54.659 --> 00:21:57.409 align:start position:0% yeah<00:21:54.720> okay<00:21:55.620> okay<00:21:55.799> okay<00:21:55.860> yeah 00:21:57.409 --> 00:21:57.419 align:start position:0% yeah okay okay okay yeah 00:21:57.419 --> 00:22:00.409 align:start position:0% yeah okay okay okay yeah so<00:21:57.900> so<00:21:57.900> the<00:21:58.320> thing<00:21:58.440> is<00:21:58.559> like<00:21:58.679> with<00:21:59.460> this<00:21:59.700> uh 00:22:00.409 --> 00:22:00.419 align:start position:0% so so the thing is like with this uh 00:22:00.419 --> 00:22:02.990 align:start position:0% so so the thing is like with this uh repository<00:22:01.080> we<00:22:01.919> show<00:22:02.159> really<00:22:02.460> how<00:22:02.760> you<00:22:02.880> can 00:22:02.990 --> 00:22:03.000 align:start position:0% repository we show really how you can 00:22:03.000 --> 00:22:06.289 align:start position:0% repository we show really how you can set<00:22:03.240> up<00:22:03.539> the<00:22:03.840> Explorer<00:22:04.620> and<00:22:04.980> we<00:22:05.220> we<00:22:05.700> know<00:22:05.940> it's 00:22:06.289 --> 00:22:06.299 align:start position:0% set up the Explorer and we we know it's 00:22:06.299 --> 00:22:08.270 align:start position:0% set up the Explorer and we we know it's not<00:22:06.480> like<00:22:06.720> there's<00:22:07.440> a<00:22:07.740> lot<00:22:07.860> of<00:22:07.980> technical 00:22:08.270 --> 00:22:08.280 align:start position:0% not like there's a lot of technical 00:22:08.280 --> 00:22:10.750 align:start position:0% not like there's a lot of technical technical<00:22:09.059> depth<00:22:09.539> that<00:22:09.840> is<00:22:09.960> like 00:22:10.750 --> 00:22:10.760 align:start position:0% technical depth that is like 00:22:10.760 --> 00:22:14.090 align:start position:0% technical depth that is like we<00:22:11.760> need<00:22:11.880> to<00:22:12.000> solve<00:22:12.299> it<00:22:12.419> but<00:22:13.080> it<00:22:13.559> it's<00:22:13.799> working 00:22:14.090 --> 00:22:14.100 align:start position:0% we need to solve it but it it's working 00:22:14.100 --> 00:22:16.850 align:start position:0% we need to solve it but it it's working for<00:22:15.000> everyone<00:22:15.179> not<00:22:15.659> just<00:22:15.840> for<00:22:16.260> those<00:22:16.440> who<00:22:16.620> have 00:22:16.850 --> 00:22:16.860 align:start position:0% for everyone not just for those who have 00:22:16.860 --> 00:22:20.149 align:start position:0% for everyone not just for those who have really<00:22:17.299> gcp<00:22:18.299> accounts<00:22:18.900> and<00:22:18.960> everything 00:22:20.149 --> 00:22:20.159 align:start position:0% really gcp accounts and everything 00:22:20.159 --> 00:22:21.350 align:start position:0% really gcp accounts and everything um 00:22:21.350 --> 00:22:21.360 align:start position:0% um 00:22:21.360 --> 00:22:45.289 align:start position:0% um I<00:22:21.900> think<00:22:22.020> we<00:22:22.380> can<00:22:22.500> go<00:22:22.679> to<00:22:22.799> the<00:22:22.919> next<00:22:23.039> slide 00:22:45.289 --> 00:22:45.299 align:start position:0% 00:22:45.299 --> 00:22:48.110 align:start position:0% yeah 00:22:48.110 --> 00:22:48.120 align:start position:0% 00:22:48.120 --> 00:22:51.110 align:start position:0% okay<00:22:48.900> so<00:22:49.320> for<00:22:49.620> anyone<00:22:49.919> using 00:22:51.110 --> 00:22:51.120 align:start position:0% okay so for anyone using 00:22:51.120 --> 00:22:53.810 align:start position:0% okay so for anyone using um<00:22:51.179> our<00:22:51.480> mobile<00:22:51.720> app<00:22:52.020> or<00:22:52.380> the<00:22:52.559> website<00:22:52.980> we've 00:22:53.810 --> 00:22:53.820 align:start position:0% um our mobile app or the website we've 00:22:53.820 --> 00:22:57.409 align:start position:0% um our mobile app or the website we've got<00:22:54.000> a<00:22:54.620> discount<00:22:55.620> code<00:22:56.039> Bogota<00:22:56.520> 50<00:22:56.940> if<00:22:57.299> you 00:22:57.409 --> 00:22:57.419 align:start position:0% got a discount code Bogota 50 if you 00:22:57.419 --> 00:23:00.409 align:start position:0% got a discount code Bogota 50 if you want<00:22:57.539> to<00:22:57.659> use<00:22:57.780> it<00:22:57.960> you<00:22:58.559> can<00:22:58.679> get<00:22:58.860> our<00:22:59.419> Premium 00:23:00.409 --> 00:23:00.419 align:start position:0% want to use it you can get our Premium 00:23:00.419 --> 00:23:01.270 align:start position:0% want to use it you can get our Premium app 00:23:01.270 --> 00:23:01.280 align:start position:0% app 00:23:01.280 --> 00:23:04.010 align:start position:0% app Services<00:23:02.299> uh<00:23:03.299> if<00:23:03.539> you<00:23:03.600> have<00:23:03.720> a<00:23:03.780> lot<00:23:03.900> of 00:23:04.010 --> 00:23:04.020 align:start position:0% Services uh if you have a lot of 00:23:04.020 --> 00:23:06.110 align:start position:0% Services uh if you have a lot of validators<00:23:04.440> it's<00:23:04.740> nice<00:23:04.980> uh<00:23:05.580> among<00:23:05.940> other 00:23:06.110 --> 00:23:06.120 align:start position:0% validators it's nice uh among other 00:23:06.120 --> 00:23:08.570 align:start position:0% validators it's nice uh among other things<00:23:06.360> or<00:23:07.200> if<00:23:07.440> you<00:23:07.559> want<00:23:07.679> to<00:23:07.799> use<00:23:07.980> our<00:23:08.159> API 00:23:08.570 --> 00:23:08.580 align:start position:0% things or if you want to use our API 00:23:08.580 --> 00:23:11.210 align:start position:0% things or if you want to use our API Services<00:23:09.380> you<00:23:10.380> can<00:23:10.440> use<00:23:10.559> the<00:23:10.740> code<00:23:10.860> over<00:23:11.039> the 00:23:11.210 --> 00:23:11.220 align:start position:0% Services you can use the code over the 00:23:11.220 --> 00:23:14.570 align:start position:0% Services you can use the code over the website<00:23:11.640> not<00:23:12.059> directly<00:23:12.419> over<00:23:12.600> the<00:23:12.840> mobile 00:23:14.570 --> 00:23:14.580 align:start position:0% website not directly over the mobile 00:23:14.580 --> 00:23:16.669 align:start position:0% website not directly over the mobile um<00:23:14.700> and<00:23:15.059> yeah<00:23:15.360> if<00:23:16.320> you're<00:23:16.380> running<00:23:16.500> a 00:23:16.669 --> 00:23:16.679 align:start position:0% um and yeah if you're running a 00:23:16.679 --> 00:23:18.230 align:start position:0% um and yeah if you're running a validator<00:23:17.100> the<00:23:17.460> mobile<00:23:17.580> and<00:23:17.880> you<00:23:18.000> don't<00:23:18.120> know 00:23:18.230 --> 00:23:18.240 align:start position:0% validator the mobile and you don't know 00:23:18.240 --> 00:23:20.930 align:start position:0% validator the mobile and you don't know about<00:23:18.419> the<00:23:18.600> mobile<00:23:18.720> app<00:23:19.020> it's<00:23:19.380> pretty<00:23:19.620> nice<00:23:19.940> it 00:23:20.930 --> 00:23:20.940 align:start position:0% about the mobile app it's pretty nice it 00:23:20.940 --> 00:23:23.270 align:start position:0% about the mobile app it's pretty nice it lets<00:23:21.240> you<00:23:21.299> look<00:23:22.080> at<00:23:22.200> your<00:23:22.380> validators<00:23:22.919> on<00:23:23.159> the 00:23:23.270 --> 00:23:23.280 align:start position:0% lets you look at your validators on the 00:23:23.280 --> 00:23:25.010 align:start position:0% lets you look at your validators on the go<00:23:23.400> it<00:23:23.760> lets<00:23:24.000> you<00:23:24.059> get<00:23:24.240> notifications<00:23:24.720> when 00:23:25.010 --> 00:23:25.020 align:start position:0% go it lets you get notifications when 00:23:25.020 --> 00:23:27.169 align:start position:0% go it lets you get notifications when you<00:23:25.140> propose<00:23:25.440> a<00:23:25.620> Blog 00:23:27.169 --> 00:23:27.179 align:start position:0% you propose a Blog 00:23:27.179 --> 00:23:29.810 align:start position:0% you propose a Blog um<00:23:27.240> and<00:23:27.480> kind<00:23:27.840> of<00:23:27.960> see<00:23:28.200> if<00:23:28.380> you've<00:23:28.919> gotten<00:23:29.400> uh 00:23:29.810 --> 00:23:29.820 align:start position:0% um and kind of see if you've gotten uh 00:23:29.820 --> 00:23:32.330 align:start position:0% um and kind of see if you've gotten uh those<00:23:30.179> 30<00:23:30.840> East<00:23:31.080> block<00:23:31.440> Rewards<00:23:31.919> or<00:23:32.220> something 00:23:32.330 --> 00:23:32.340 align:start position:0% those 30 East block Rewards or something 00:23:32.340 --> 00:23:34.130 align:start position:0% those 30 East block Rewards or something like<00:23:32.640> that 00:23:34.130 --> 00:23:34.140 align:start position:0% like that 00:23:34.140 --> 00:23:35.270 align:start position:0% like that um<00:23:34.200> yeah 00:23:35.270 --> 00:23:35.280 align:start position:0% um yeah 00:23:35.280 --> 00:23:37.549 align:start position:0% um yeah okay<00:23:35.820> then 00:23:37.549 --> 00:23:37.559 align:start position:0% okay then 00:23:37.559 --> 00:23:38.890 align:start position:0% okay then um 00:23:38.890 --> 00:23:38.900 align:start position:0% um 00:23:38.900 --> 00:23:42.830 align:start position:0% um yeah<00:23:40.340> if<00:23:41.340> you<00:23:41.400> want<00:23:41.520> to<00:23:41.640> contribute 00:23:42.830 --> 00:23:42.840 align:start position:0% yeah if you want to contribute 00:23:42.840 --> 00:23:45.169 align:start position:0% yeah if you want to contribute um<00:23:42.960> here's<00:23:43.320> kind<00:23:43.500> of<00:23:43.559> the<00:23:43.679> overview 00:23:45.169 --> 00:23:45.179 align:start position:0% um here's kind of the overview 00:23:45.179 --> 00:23:48.049 align:start position:0% um here's kind of the overview um<00:23:45.299> of<00:23:45.659> kind<00:23:45.960> of<00:23:46.080> the<00:23:46.140> resources<00:23:46.679> so 00:23:48.049 --> 00:23:48.059 align:start position:0% um of kind of the resources so 00:23:48.059 --> 00:23:49.789 align:start position:0% um of kind of the resources so um<00:23:48.120> we<00:23:48.419> have<00:23:48.539> a<00:23:48.600> good<00:23:48.720> coin<00:23:49.080> Grant<00:23:49.380> that's 00:23:49.789 --> 00:23:49.799 align:start position:0% um we have a good coin Grant that's 00:23:49.799 --> 00:23:52.430 align:start position:0% um we have a good coin Grant that's linked<00:23:50.159> below<00:23:50.520> uh<00:23:51.179> you<00:23:51.419> can<00:23:51.480> tweet<00:23:51.780> at<00:23:52.140> Peak 00:23:52.430 --> 00:23:52.440 align:start position:0% linked below uh you can tweet at Peak 00:23:52.440 --> 00:23:54.350 align:start position:0% linked below uh you can tweet at Peak and<00:23:52.620> chain<00:23:52.740> if<00:23:53.280> you<00:23:53.400> see<00:23:53.520> any<00:23:53.700> issues<00:23:54.120> or 00:23:54.350 --> 00:23:54.360 align:start position:0% and chain if you see any issues or 00:23:54.360 --> 00:23:57.529 align:start position:0% and chain if you see any issues or something<00:23:54.539> create<00:23:55.320> issues<00:23:55.919> uh<00:23:56.580> on<00:23:57.059> the<00:23:57.240> GitHub 00:23:57.529 --> 00:23:57.539 align:start position:0% something create issues uh on the GitHub 00:23:57.539 --> 00:24:00.470 align:start position:0% something create issues uh on the GitHub repository<00:23:58.080> that's<00:23:58.320> also<00:23:58.559> linked<00:23:58.919> there 00:24:00.470 --> 00:24:00.480 align:start position:0% repository that's also linked there 00:24:00.480 --> 00:24:01.909 align:start position:0% repository that's also linked there um and 00:24:01.909 --> 00:24:01.919 align:start position:0% um and 00:24:01.919 --> 00:24:03.890 align:start position:0% um and oh<00:24:02.400> did<00:24:02.700> anyone<00:24:02.940> still<00:24:03.120> want<00:24:03.299> to<00:24:03.480> take<00:24:03.780> a 00:24:03.890 --> 00:24:03.900 align:start position:0% oh did anyone still want to take a 00:24:03.900 --> 00:24:04.850 align:start position:0% oh did anyone still want to take a picture 00:24:04.850 --> 00:24:04.860 align:start position:0% picture 00:24:04.860 --> 00:24:07.549 align:start position:0% picture or<00:24:05.400> no<00:24:05.760> thanks<00:24:06.179> yeah<00:24:06.659> that's<00:24:07.080> basically<00:24:07.380> it 00:24:07.549 --> 00:24:07.559 align:start position:0% or no thanks yeah that's basically it 00:24:07.559 --> 00:24:10.010 align:start position:0% or no thanks yeah that's basically it from<00:24:07.799> us<00:24:07.980> thanks<00:24:08.880> so<00:24:09.000> much<00:24:09.179> for<00:24:09.539> participating 00:24:10.010 --> 00:24:10.020 align:start position:0% from us thanks so much for participating 00:24:10.020 --> 00:24:16.130 align:start position:0% from us thanks so much for participating and<00:24:10.320> listening 00:24:16.130 --> 00:24:16.140 align:start position:0% 00:24:16.140 --> 00:24:19.010 align:start position:0% if<00:24:16.620> you<00:24:16.740> have<00:24:16.860> any<00:24:17.039> questions 00:24:19.010 --> 00:24:19.020 align:start position:0% if you have any questions 00:24:19.020 --> 00:24:21.730 align:start position:0% if you have any questions um<00:24:19.140> yours<00:24:19.679> right<00:24:19.919> now<00:24:20.039> that<00:24:20.340> you<00:24:20.580> personally 00:24:21.730 --> 00:24:21.740 align:start position:0% um yours right now that you personally 00:24:21.740 --> 00:24:24.169 align:start position:0% um yours right now that you personally it's<00:24:22.740> called<00:24:22.919> so<00:24:23.159> it's<00:24:23.280> one<00:24:23.460> of<00:24:23.520> the<00:24:23.580> test<00:24:23.760> Nets 00:24:24.169 --> 00:24:24.179 align:start position:0% it's called so it's one of the test Nets 00:24:24.179 --> 00:24:26.029 align:start position:0% it's called so it's one of the test Nets it's<00:24:24.299> a<00:24:24.419> bit<00:24:24.539> smaller<00:24:24.900> so<00:24:25.559> it<00:24:25.679> should<00:24:25.799> be<00:24:25.919> able 00:24:26.029 --> 00:24:26.039 align:start position:0% it's a bit smaller so it should be able 00:24:26.039 --> 00:24:28.190 align:start position:0% it's a bit smaller so it should be able to<00:24:26.220> think<00:24:26.400> in<00:24:26.820> a<00:24:27.000> reasonable<00:24:27.659> amount<00:24:28.020> of 00:24:28.190 --> 00:24:28.200 align:start position:0% to think in a reasonable amount of 00:24:28.200 --> 00:24:29.390 align:start position:0% to think in a reasonable amount of amount<00:24:28.559> of<00:24:28.679> time 00:24:29.390 --> 00:24:29.400 align:start position:0% amount of time 00:24:29.400 --> 00:24:31.610 align:start position:0% amount of time um<00:24:29.460> the<00:24:29.700> Wi-Fi<00:24:29.880> isn't<00:24:30.179> the<00:24:30.299> best<00:24:30.480> here<00:24:30.780> so<00:24:31.380> here 00:24:31.610 --> 00:24:31.620 align:start position:0% um the Wi-Fi isn't the best here so here 00:24:31.620 --> 00:24:33.470 align:start position:0% um the Wi-Fi isn't the best here so here it<00:24:31.799> could<00:24:31.919> take<00:24:32.100> a<00:24:32.220> while 00:24:33.470 --> 00:24:33.480 align:start position:0% it could take a while 00:24:33.480 --> 00:24:36.470 align:start position:0% it could take a while um<00:24:33.600> but<00:24:33.840> it's<00:24:34.140> a<00:24:34.320> lot<00:24:34.440> smaller<00:24:34.860> than<00:24:35.400> Plata<00:24:36.120> or 00:24:36.470 --> 00:24:36.480 align:start position:0% um but it's a lot smaller than Plata or 00:24:36.480 --> 00:24:39.950 align:start position:0% um but it's a lot smaller than Plata or which<00:24:36.659> is<00:24:36.780> girly<00:24:37.200> or<00:24:37.620> mainnet<00:24:38.179> which<00:24:39.179> are 00:24:39.950 --> 00:24:39.960 align:start position:0% which is girly or mainnet which are 00:24:39.960 --> 00:24:42.169 align:start position:0% which is girly or mainnet which are pretty<00:24:40.440> huge<00:24:40.740> right<00:24:40.980> now 00:24:42.169 --> 00:24:42.179 align:start position:0% pretty huge right now 00:24:42.179 --> 00:24:46.669 align:start position:0% pretty huge right now okay<00:24:42.659> any<00:24:43.140> other<00:24:43.380> questions 00:24:46.669 --> 00:24:46.679 align:start position:0% 00:24:46.679 --> 00:24:47.510 align:start position:0% um 00:24:47.510 --> 00:24:47.520 align:start position:0% um 00:24:47.520 --> 00:24:50.510 align:start position:0% um not<00:24:48.360> sure<00:24:48.539> if<00:24:48.720> I<00:24:48.900> if<00:24:49.679> I<00:24:49.860> should<00:24:49.980> answer<00:24:50.159> that 00:24:50.510 --> 00:24:50.520 align:start position:0% not sure if I if I should answer that 00:24:50.520 --> 00:24:52.430 align:start position:0% not sure if I if I should answer that but 00:24:52.430 --> 00:24:52.440 align:start position:0% but 00:24:52.440 --> 00:24:54.649 align:start position:0% but um<00:24:52.500> it's<00:24:52.919> it's<00:24:53.159> quite<00:24:53.400> a<00:24:53.580> lot<00:24:53.700> it's<00:24:54.299> quite<00:24:54.539> a 00:24:54.649 --> 00:24:54.659 align:start position:0% um it's it's quite a lot it's quite a 00:24:54.659 --> 00:24:57.049 align:start position:0% um it's it's quite a lot it's quite a lot<00:24:54.860> so<00:24:55.860> it's 00:24:57.049 --> 00:24:57.059 align:start position:0% lot so it's 00:24:57.059 --> 00:24:58.850 align:start position:0% lot so it's um<00:24:57.120> what<00:24:57.539> is<00:24:57.780> it 00:24:58.850 --> 00:24:58.860 align:start position:0% um what is it 00:24:58.860 --> 00:25:04.070 align:start position:0% um what is it five<00:24:59.159> figures 00:25:04.070 --> 00:25:04.080 align:start position:0% 00:25:04.080 --> 00:25:09.370 align:start position:0% we<00:25:04.559> looked<00:25:05.159> especially 00:25:09.370 --> 00:25:09.380 align:start position:0% 00:25:09.380 --> 00:25:12.649 align:start position:0% especially<00:25:10.380> but<00:25:11.280> we<00:25:11.520> looked<00:25:11.820> also<00:25:12.120> at<00:25:12.299> other 00:25:12.649 --> 00:25:12.659 align:start position:0% especially but we looked also at other 00:25:12.659 --> 00:25:13.789 align:start position:0% especially but we looked also at other DPS 00:25:13.789 --> 00:25:13.799 align:start position:0% DPS 00:25:13.799 --> 00:25:16.490 align:start position:0% DPS but<00:25:14.460> in<00:25:14.700> the<00:25:14.820> end<00:25:14.940> we<00:25:15.360> took<00:25:15.600> something<00:25:15.840> that 00:25:16.490 --> 00:25:16.500 align:start position:0% but in the end we took something that 00:25:16.500 --> 00:25:19.970 align:start position:0% but in the end we took something that also<00:25:17.400> fits<00:25:17.820> in<00:25:18.720> our<00:25:18.900> team 00:25:19.970 --> 00:25:19.980 align:start position:0% also fits in our team 00:25:19.980 --> 00:25:22.430 align:start position:0% also fits in our team like<00:25:20.400> we<00:25:20.580> don't<00:25:20.760> have<00:25:20.880> so<00:25:21.120> much<00:25:21.240> resources<00:25:21.900> I 00:25:22.430 --> 00:25:22.440 align:start position:0% like we don't have so much resources I 00:25:22.440 --> 00:25:23.930 align:start position:0% like we don't have so much resources I was<00:25:22.679> like<00:25:22.799> so<00:25:23.159> much 00:25:23.930 --> 00:25:23.940 align:start position:0% was like so much 00:25:23.940 --> 00:25:27.110 align:start position:0% was like so much take<00:25:24.419> so<00:25:24.600> much<00:25:24.779> man<00:25:25.020> hours<00:25:25.380> to<00:25:26.100> get<00:25:26.580> into<00:25:26.760> a<00:25:27.000> new 00:25:27.110 --> 00:25:27.120 align:start position:0% take so much man hours to get into a new 00:25:27.120 --> 00:25:28.549 align:start position:0% take so much man hours to get into a new technology 00:25:28.549 --> 00:25:28.559 align:start position:0% technology 00:25:28.559 --> 00:25:29.870 align:start position:0% technology and 00:25:29.870 --> 00:25:29.880 align:start position:0% and 00:25:29.880 --> 00:25:32.630 align:start position:0% and for<00:25:30.299> us<00:25:30.480> this<00:25:30.779> looked<00:25:31.140> at<00:25:31.200> the<00:25:31.500> best<00:25:31.620> fit 00:25:32.630 --> 00:25:32.640 align:start position:0% for us this looked at the best fit 00:25:32.640 --> 00:25:34.490 align:start position:0% for us this looked at the best fit and<00:25:33.179> right<00:25:33.419> now<00:25:33.600> we<00:25:33.779> are<00:25:33.900> really<00:25:34.020> happy<00:25:34.200> with 00:25:34.490 --> 00:25:34.500 align:start position:0% and right now we are really happy with 00:25:34.500 --> 00:25:37.490 align:start position:0% and right now we are really happy with it<00:25:34.679> so 00:25:37.490 --> 00:25:37.500 align:start position:0% 00:25:37.500 --> 00:25:39.470 align:start position:0% yeah<00:25:37.679> we<00:25:38.039> basically<00:25:38.460> went<00:25:38.760> from<00:25:39.059> an<00:25:39.179> export 00:25:39.470 --> 00:25:39.480 align:start position:0% yeah we basically went from an export 00:25:39.480 --> 00:25:41.930 align:start position:0% yeah we basically went from an export time<00:25:39.779> of<00:25:40.080> 30<00:25:40.620> plus<00:25:40.919> seconds<00:25:41.159> for<00:25:41.460> attestation 00:25:41.930 --> 00:25:41.940 align:start position:0% time of 30 plus seconds for attestation 00:25:41.940 --> 00:25:43.730 align:start position:0% time of 30 plus seconds for attestation assignments<00:25:42.480> to<00:25:42.600> like<00:25:42.779> five<00:25:43.020> seconds<00:25:43.260> which 00:25:43.730 --> 00:25:43.740 align:start position:0% assignments to like five seconds which 00:25:43.740 --> 00:25:45.590 align:start position:0% assignments to like five seconds which is<00:25:43.860> a<00:25:43.980> lot<00:25:44.100> better<00:25:44.279> and<00:25:45.179> there<00:25:45.299> was<00:25:45.480> less 00:25:45.590 --> 00:25:45.600 align:start position:0% is a lot better and there was less 00:25:45.600 --> 00:25:48.830 align:start position:0% is a lot better and there was less contention<00:25:46.140> between<00:25:46.799> different<00:25:47.279> queries<00:25:47.880> uh 00:25:48.830 --> 00:25:48.840 align:start position:0% contention between different queries uh 00:25:48.840 --> 00:25:50.690 align:start position:0% contention between different queries uh on<00:25:49.020> bigtable<00:25:49.500> now<00:25:49.799> that<00:25:49.980> we<00:25:50.039> moved<00:25:50.279> but<00:25:50.460> that 00:25:50.690 --> 00:25:50.700 align:start position:0% on bigtable now that we moved but that 00:25:50.700 --> 00:25:52.130 align:start position:0% on bigtable now that we moved but that can<00:25:50.940> change<00:25:51.179> if<00:25:51.419> we<00:25:51.539> have<00:25:51.659> everything<00:25:51.900> on 00:25:52.130 --> 00:25:52.140 align:start position:0% can change if we have everything on 00:25:52.140 --> 00:25:54.409 align:start position:0% can change if we have everything on bigtable<00:25:52.559> we're<00:25:53.220> just<00:25:53.460> starting<00:25:53.760> to<00:25:54.059> migrate 00:25:54.409 --> 00:25:54.419 align:start position:0% bigtable we're just starting to migrate 00:25:54.419 --> 00:25:57.710 align:start position:0% bigtable we're just starting to migrate so<00:25:55.140> I<00:25:55.380> hope<00:25:55.500> it<00:25:55.679> stays<00:25:56.100> good 00:25:57.710 --> 00:25:57.720 align:start position:0% so I hope it stays good 00:25:57.720 --> 00:26:05.090 align:start position:0% so I hope it stays good yeah<00:25:58.440> and<00:25:58.679> Layer<00:25:59.100> Two<00:25:59.279> is<00:25:59.520> coming<00:25:59.760> yes<00:26:00.480> okay 00:26:05.090 --> 00:26:05.100 align:start position:0% 00:26:05.100 --> 00:26:06.950 align:start position:0% anything<00:26:05.880> else 00:26:06.950 --> 00:26:06.960 align:start position:0% anything else 00:26:06.960 --> 00:26:08.810 align:start position:0% anything else thank<00:26:07.440> you<00:26:07.559> very<00:26:07.679> much<00:26:07.860> for<00:26:08.100> listening<00:26:08.400> and 00:26:08.810 --> 00:26:08.820 align:start position:0% thank you very much for listening and 00:26:08.820 --> 00:26:11.810 align:start position:0% thank you very much for listening and for<00:26:09.360> participating<00:26:10.020> again<00:26:10.440> yes<00:26:11.400> thank<00:26:11.640> you<00:26:11.700> so 00:26:11.810 --> 00:26:11.820 align:start position:0% for participating again yes thank you so 00:26:11.820 --> 00:26:13.940 align:start position:0% for participating again yes thank you so much