WEBVTT Kind: captions Language: en 00:00:00.180 --> 00:00:02.650 align:start position:0% [Applause] 00:00:02.650 --> 00:00:02.660 align:start position:0% [Applause] 00:00:02.660 --> 00:00:04.150 align:start position:0% [Applause] [Music] 00:00:04.150 --> 00:00:04.160 align:start position:0% [Music] 00:00:04.160 --> 00:00:07.610 align:start position:0% [Music] hello<00:00:05.160> everyone<00:00:05.670> shall<00:00:06.569> we<00:00:06.600> and<00:00:07.049> finder<00:00:07.500> and 00:00:07.610 --> 00:00:07.620 align:start position:0% hello everyone shall we and finder and 00:00:07.620 --> 00:00:11.570 align:start position:0% hello everyone shall we and finder and foundation<00:00:08.160> research<00:00:09.059> thing<00:00:09.590> so<00:00:10.590> in<00:00:11.130> research 00:00:11.570 --> 00:00:11.580 align:start position:0% foundation research thing so in research 00:00:11.580 --> 00:00:14.660 align:start position:0% foundation research thing so in research team<00:00:11.790> we<00:00:12.059> do<00:00:12.300> research<00:00:12.780> on<00:00:13.370> the<00:00:14.370> next 00:00:14.660 --> 00:00:14.670 align:start position:0% team we do research on the next 00:00:14.670 --> 00:00:17.840 align:start position:0% team we do research on the next generation<00:00:14.880> in<00:00:15.690> certain<00:00:16.109> protocols<00:00:16.560> and<00:00:17.369> we 00:00:17.840 --> 00:00:17.850 align:start position:0% generation in certain protocols and we 00:00:17.850 --> 00:00:20.210 align:start position:0% generation in certain protocols and we also<00:00:18.029> drew<00:00:18.449> some<00:00:18.480> proof<00:00:19.230> of<00:00:19.320> concept<00:00:19.800> to 00:00:20.210 --> 00:00:20.220 align:start position:0% also drew some proof of concept to 00:00:20.220 --> 00:00:24.349 align:start position:0% also drew some proof of concept to verify<00:00:21.180> our<00:00:21.210> ideas<00:00:21.900> so<00:00:22.710> today<00:00:23.670> this<00:00:23.850> is<00:00:24.300> a 00:00:24.349 --> 00:00:24.359 align:start position:0% verify our ideas so today this is a 00:00:24.359 --> 00:00:26.540 align:start position:0% verify our ideas so today this is a lightning<00:00:24.960> Hawk<00:00:25.170> and<00:00:25.500> it<00:00:25.769> will<00:00:25.980> be<00:00:26.189> more<00:00:26.430> about 00:00:26.540 --> 00:00:26.550 align:start position:0% lightning Hawk and it will be more about 00:00:26.550 --> 00:00:29.859 align:start position:0% lightning Hawk and it will be more about the<00:00:26.779> implementation<00:00:27.779> part 00:00:29.859 --> 00:00:29.869 align:start position:0% the implementation part 00:00:29.869 --> 00:00:34.120 align:start position:0% the implementation part so<00:00:30.869> first<00:00:31.349> let's<00:00:31.619> a<00:00:31.800> quick<00:00:32.219> recap<00:00:32.610> that<00:00:33.390> now 00:00:34.120 --> 00:00:34.130 align:start position:0% so first let's a quick recap that now 00:00:34.130 --> 00:00:36.979 align:start position:0% so first let's a quick recap that now may<00:00:35.130> already<00:00:35.430> know<00:00:35.730> that<00:00:35.850> from<00:00:36.300> Tally's<00:00:36.750> talk 00:00:36.979 --> 00:00:36.989 align:start position:0% may already know that from Tally's talk 00:00:36.989 --> 00:00:40.670 align:start position:0% may already know that from Tally's talk lab<00:00:38.059> Casper<00:00:39.059> shouting<00:00:39.510> and<00:00:39.870> pick<00:00:40.170> random<00:00:40.530> be 00:00:40.670 --> 00:00:40.680 align:start position:0% lab Casper shouting and pick random be 00:00:40.680 --> 00:00:41.990 align:start position:0% lab Casper shouting and pick random be concerned<00:00:41.070> they<00:00:41.190> are<00:00:41.219> all<00:00:41.430> together<00:00:41.610> right 00:00:41.990 --> 00:00:42.000 align:start position:0% concerned they are all together right 00:00:42.000 --> 00:00:47.080 align:start position:0% concerned they are all together right now<00:00:42.030> and<00:00:42.420> we<00:00:43.320> I<00:00:43.649> prefer<00:00:44.250> to<00:00:44.460> call<00:00:44.760> it<00:00:44.820> serenity 00:00:47.080 --> 00:00:47.090 align:start position:0% now and we I prefer to call it serenity 00:00:47.090 --> 00:00:51.470 align:start position:0% now and we I prefer to call it serenity and<00:00:48.350> know<00:00:49.350> these<00:00:49.770> circles<00:00:50.280> our<00:00:50.610> current<00:00:51.270> world 00:00:51.470 --> 00:00:51.480 align:start position:0% and know these circles our current world 00:00:51.480 --> 00:00:56.139 align:start position:0% and know these circles our current world is<00:00:51.870> server<00:00:52.350> 1.0<00:00:52.949> and<00:00:53.600> poof<00:00:54.600> up<00:00:54.719> work<00:00:54.930> chain<00:00:55.289> and 00:00:56.139 --> 00:00:56.149 align:start position:0% is server 1.0 and poof up work chain and 00:00:56.149 --> 00:01:00.560 align:start position:0% is server 1.0 and poof up work chain and the<00:00:57.149> serenity<00:00:57.780> is<00:00:57.989> quite<00:00:58.440> different<00:00:59.300> but<00:01:00.300> it's 00:01:00.560 --> 00:01:00.570 align:start position:0% the serenity is quite different but it's 00:01:00.570 --> 00:01:04.579 align:start position:0% the serenity is quite different but it's still<00:01:01.010> extension<00:01:02.010> of<00:01:02.219> the<00:01:02.489> external<00:01:02.789> 1.0<00:01:03.589> and 00:01:04.579 --> 00:01:04.589 align:start position:0% still extension of the external 1.0 and 00:01:04.589 --> 00:01:08.149 align:start position:0% still extension of the external 1.0 and we<00:01:04.799> will<00:01:04.979> have<00:01:05.280> those<00:01:05.510> fantastic<00:01:06.510> future<00:01:07.380> like 00:01:08.149 --> 00:01:08.159 align:start position:0% we will have those fantastic future like 00:01:08.159 --> 00:01:10.940 align:start position:0% we will have those fantastic future like the<00:01:08.400> four<00:01:08.700> pop-ups<00:01:09.090> take<00:01:09.390> a<00:01:09.750> good<00:01:10.380> random 00:01:10.940 --> 00:01:10.950 align:start position:0% the four pop-ups take a good random 00:01:10.950 --> 00:01:14.090 align:start position:0% the four pop-ups take a good random number<00:01:11.280> generator<00:01:11.760> and<00:01:12.360> the<00:01:13.260> blockchain<00:01:13.650> shot 00:01:14.090 --> 00:01:14.100 align:start position:0% number generator and the blockchain shot 00:01:14.100 --> 00:01:19.310 align:start position:0% number generator and the blockchain shot in<00:01:14.280> for<00:01:14.580> scalability<00:01:15.210> problem<00:01:16.280> and<00:01:18.170> we<00:01:19.170> will 00:01:19.310 --> 00:01:19.320 align:start position:0% in for scalability problem and we will 00:01:19.320 --> 00:01:22.429 align:start position:0% in for scalability problem and we will have<00:01:19.590> a<00:01:19.619> whole<00:01:20.130> new<00:01:20.340> brand<00:01:20.759> brand<00:01:21.750> new<00:01:21.900> beacon 00:01:22.429 --> 00:01:22.439 align:start position:0% have a whole new brand brand new beacon 00:01:22.439 --> 00:01:25.039 align:start position:0% have a whole new brand brand new beacon chain<00:01:22.710> and<00:01:22.920> many<00:01:23.610> xiaochun's<00:01:24.330> in<00:01:24.570> this 00:01:25.039 --> 00:01:25.049 align:start position:0% chain and many xiaochun's in this 00:01:25.049 --> 00:01:31.310 align:start position:0% chain and many xiaochun's in this ecosystem<00:01:25.700> to<00:01:26.700> realize<00:01:27.090> it<00:01:29.270> so<00:01:30.270> if<00:01:31.020> we 00:01:31.310 --> 00:01:31.320 align:start position:0% ecosystem to realize it so if we 00:01:31.320 --> 00:01:35.420 align:start position:0% ecosystem to realize it so if we abstract<00:01:32.280> the<00:01:32.759> different<00:01:33.689> chains<00:01:33.930> into<00:01:34.430> okay 00:01:35.420 --> 00:01:35.430 align:start position:0% abstract the different chains into okay 00:01:35.430 --> 00:01:39.620 align:start position:0% abstract the different chains into okay make<00:01:35.850> it<00:01:35.970> into<00:01:36.299> three<00:01:36.600> levels<00:01:37.520> so<00:01:38.520> the<00:01:39.060> if<00:01:39.420> I'm 00:01:39.620 --> 00:01:39.630 align:start position:0% make it into three levels so the if I'm 00:01:39.630 --> 00:01:43.789 align:start position:0% make it into three levels so the if I'm a<00:01:39.659> user<00:01:40.140> of<00:01:40.979> the<00:01:41.340> faux<00:01:42.060> fur<00:01:42.210> auction<00:01:42.390> I<00:01:42.990> can 00:01:43.789 --> 00:01:43.799 align:start position:0% a user of the faux fur auction I can 00:01:43.799 --> 00:01:48.020 align:start position:0% a user of the faux fur auction I can make<00:01:43.979> a<00:01:44.009> deposit<00:01:45.619> country<00:01:46.619> on<00:01:46.979> the<00:01:47.220> pure 00:01:48.020 --> 00:01:48.030 align:start position:0% make a deposit country on the pure 00:01:48.030 --> 00:01:50.870 align:start position:0% make a deposit country on the pure double<00:01:48.180> chain<00:01:48.600> I<00:01:48.840> mean<00:01:49.500> I<00:01:49.649> say<00:01:49.890> I<00:01:50.130> can<00:01:50.520> say<00:01:50.670> that 00:01:50.870 --> 00:01:50.880 align:start position:0% double chain I mean I say I can say that 00:01:50.880 --> 00:01:54.530 align:start position:0% double chain I mean I say I can say that hey<00:01:51.119> I<00:01:51.149> want<00:01:51.570> to<00:01:51.890> pass<00:01:52.890> it<00:01:53.100> at<00:01:53.280> my<00:01:53.430> 32<00:01:53.939> Easter 00:01:54.530 --> 00:01:54.540 align:start position:0% hey I want to pass it at my 32 Easter 00:01:54.540 --> 00:01:56.929 align:start position:0% hey I want to pass it at my 32 Easter and<00:01:54.780> I<00:01:55.439> want<00:01:55.619> to<00:01:55.710> be<00:01:55.890> for<00:01:56.369> one<00:01:56.549> of<00:01:56.700> the<00:01:56.880> other 00:01:56.929 --> 00:01:56.939 align:start position:0% and I want to be for one of the other 00:01:56.939 --> 00:02:01.670 align:start position:0% and I want to be for one of the other editors<00:01:57.479> and<00:01:58.399> the<00:01:59.399> validators<00:01:59.909> is<00:02:00.210> a<00:02:00.680> long 00:02:01.670 --> 00:02:01.680 align:start position:0% editors and the validators is a long 00:02:01.680 --> 00:02:05.630 align:start position:0% editors and the validators is a long list<00:02:02.070> of<00:02:02.399> the<00:02:03.180> visitors<00:02:03.689> and<00:02:03.979> those<00:02:04.979> letters 00:02:05.630 --> 00:02:05.640 align:start position:0% list of the visitors and those letters 00:02:05.640 --> 00:02:11.710 align:start position:0% list of the visitors and those letters will<00:02:06.090> be<00:02:06.380> sued<00:02:07.380> or<00:02:07.590> Rendell<00:02:08.069> a<00:02:08.360> travel<00:02:09.360> into 00:02:11.710 --> 00:02:11.720 align:start position:0% will be sued or Rendell a travel into 00:02:11.720 --> 00:02:13.690 align:start position:0% will be sued or Rendell a travel into many<00:02:12.720> groups 00:02:13.690 --> 00:02:13.700 align:start position:0% many groups 00:02:13.700 --> 00:02:17.550 align:start position:0% many groups we<00:02:14.030> call<00:02:14.300> that<00:02:14.599> this<00:02:14.990> process<00:02:15.590> the<00:02:16.130> community 00:02:17.550 --> 00:02:17.560 align:start position:0% we call that this process the community 00:02:17.560 --> 00:02:19.890 align:start position:0% we call that this process the community shoveling 00:02:19.890 --> 00:02:19.900 align:start position:0% shoveling 00:02:19.900 --> 00:02:24.460 align:start position:0% shoveling so<00:02:21.459> the<00:02:22.459> mention<00:02:23.270> is<00:02:23.450> still<00:02:23.690> here<00:02:23.959> the<00:02:24.230> pure 00:02:24.460 --> 00:02:24.470 align:start position:0% so the mention is still here the pure 00:02:24.470 --> 00:02:26.680 align:start position:0% so the mention is still here the pure documentary<00:02:25.069> is<00:02:25.190> still<00:02:25.370> here<00:02:25.700> and<00:02:25.880> the<00:02:26.480> blog 00:02:26.680 --> 00:02:26.690 align:start position:0% documentary is still here and the blog 00:02:26.690 --> 00:02:30.699 align:start position:0% documentary is still here and the blog is<00:02:26.720> proposed<00:02:27.790> but<00:02:28.790> when<00:02:29.360> we<00:02:29.540> do<00:02:29.840> the<00:02:30.170> big<00:02:30.440> hunch 00:02:30.699 --> 00:02:30.709 align:start position:0% is proposed but when we do the big hunch 00:02:30.709 --> 00:02:33.520 align:start position:0% is proposed but when we do the big hunch and<00:02:30.980> black<00:02:31.430> proposed<00:02:31.910> the<00:02:32.750> pecans<00:02:33.080> and<00:02:33.260> black 00:02:33.520 --> 00:02:33.530 align:start position:0% and black proposed the pecans and black 00:02:33.530 --> 00:02:38.290 align:start position:0% and black proposed the pecans and black will<00:02:34.040> point<00:02:34.850> to<00:02:35.390> a<00:02:37.060> reference<00:02:38.060> make<00:02:38.270> a 00:02:38.290 --> 00:02:38.300 align:start position:0% will point to a reference make a 00:02:38.300 --> 00:02:40.180 align:start position:0% will point to a reference make a reference<00:02:38.540> that<00:02:39.230> point<00:02:39.500> to<00:02:39.890> the 00:02:40.180 --> 00:02:40.190 align:start position:0% reference that point to the 00:02:40.190 --> 00:02:44.280 align:start position:0% reference that point to the proof-of-work<00:02:40.730> chain<00:02:41.150> and<00:02:42.550> there<00:02:43.550> will<00:02:43.760> be<00:02:44.030> a 00:02:44.280 --> 00:02:44.290 align:start position:0% proof-of-work chain and there will be a 00:02:44.290 --> 00:02:47.199 align:start position:0% proof-of-work chain and there will be a committee<00:02:45.290> lack<00:02:45.560> there<00:02:46.040> will<00:02:46.190> be<00:02:46.220> a<00:02:46.400> sight<00:02:46.819> and 00:02:47.199 --> 00:02:47.209 align:start position:0% committee lack there will be a sight and 00:02:47.209 --> 00:02:51.809 align:start position:0% committee lack there will be a sight and be<00:02:47.750> able<00:02:48.100> to<00:02:49.100> verify<00:02:49.519> and<00:02:50.209> attest<00:02:51.200> earth 00:02:51.809 --> 00:02:51.819 align:start position:0% be able to verify and attest earth 00:02:51.819 --> 00:02:53.380 align:start position:0% be able to verify and attest earth become<00:02:52.819> black 00:02:53.380 --> 00:02:53.390 align:start position:0% become black 00:02:53.390 --> 00:02:56.170 align:start position:0% become black so<00:02:54.170> this<00:02:54.410> committee<00:02:54.799> they<00:02:54.920> have<00:02:55.100> to<00:02:55.280> send 00:02:56.170 --> 00:02:56.180 align:start position:0% so this committee they have to send 00:02:56.180 --> 00:02:59.680 align:start position:0% so this committee they have to send their<00:02:56.299> vote<00:02:56.920> them<00:02:57.920> super<00:02:58.670> to<00:02:58.940> say<00:02:59.120> hey<00:02:59.330> yes 00:02:59.680 --> 00:02:59.690 align:start position:0% their vote them super to say hey yes 00:02:59.690 --> 00:03:03.430 align:start position:0% their vote them super to say hey yes this<00:02:59.989> blog<00:03:00.260> is<00:03:00.500> valid<00:03:00.950> and<00:03:01.630> then<00:03:02.630> we<00:03:03.019> call<00:03:03.260> this 00:03:03.430 --> 00:03:03.440 align:start position:0% this blog is valid and then we call this 00:03:03.440 --> 00:03:07.870 align:start position:0% this blog is valid and then we call this process<00:03:03.739> the<00:03:04.220> attestation<00:03:05.890> so<00:03:06.890> instruction 00:03:07.870 --> 00:03:07.880 align:start position:0% process the attestation so instruction 00:03:07.880 --> 00:03:12.330 align:start position:0% process the attestation so instruction is<00:03:08.330> similar<00:03:09.340> the<00:03:10.340> Charter<00:03:10.760> will<00:03:11.090> also<00:03:11.450> be<00:03:11.780> a 00:03:12.330 --> 00:03:12.340 align:start position:0% is similar the Charter will also be a 00:03:12.340 --> 00:03:15.280 align:start position:0% is similar the Charter will also be a committee<00:03:13.340> that<00:03:13.370> will<00:03:13.790> be<00:03:14.110> assigned<00:03:15.110> to 00:03:15.280 --> 00:03:15.290 align:start position:0% committee that will be assigned to 00:03:15.290 --> 00:03:18.460 align:start position:0% committee that will be assigned to validate<00:03:16.040> some<00:03:16.489> specific<00:03:17.030> shot<00:03:17.630> block<00:03:17.900> and 00:03:18.460 --> 00:03:18.470 align:start position:0% validate some specific shot block and 00:03:18.470 --> 00:03:21.340 align:start position:0% validate some specific shot block and the<00:03:19.070> shopvac<00:03:19.640> the<00:03:20.269> vehicle<00:03:20.720> we<00:03:20.840> have<00:03:21.049> to 00:03:21.340 --> 00:03:21.350 align:start position:0% the shopvac the vehicle we have to 00:03:21.350 --> 00:03:23.560 align:start position:0% the shopvac the vehicle we have to verify<00:03:22.100> this<00:03:22.370> blog<00:03:22.850> and<00:03:23.090> make<00:03:23.359> their 00:03:23.560 --> 00:03:23.570 align:start position:0% verify this blog and make their 00:03:23.570 --> 00:03:27.699 align:start position:0% verify this blog and make their attestations<00:03:25.030> so<00:03:26.030> um<00:03:26.359> the<00:03:26.870> following<00:03:27.530> process 00:03:27.699 --> 00:03:27.709 align:start position:0% attestations so um the following process 00:03:27.709 --> 00:03:31.390 align:start position:0% attestations so um the following process is<00:03:28.070> similar<00:03:28.340> just<00:03:29.440> propose<00:03:30.440> a<00:03:30.470> block<00:03:30.799> they 00:03:31.390 --> 00:03:31.400 align:start position:0% is similar just propose a block they 00:03:31.400 --> 00:03:34.599 align:start position:0% is similar just propose a block they refer<00:03:31.700> sit<00:03:31.970> and<00:03:32.380> notice<00:03:33.380> that<00:03:33.560> the<00:03:33.950> retention 00:03:34.599 --> 00:03:34.609 align:start position:0% refer sit and notice that the retention 00:03:34.609 --> 00:03:37.810 align:start position:0% refer sit and notice that the retention Park<00:03:35.060> and<00:03:35.299> shadow<00:03:35.540> can<00:03:35.870> be<00:03:36.280> fast<00:03:37.280> early<00:03:37.670> and 00:03:37.810 --> 00:03:37.820 align:start position:0% Park and shadow can be fast early and 00:03:37.820 --> 00:03:41.520 align:start position:0% Park and shadow can be fast early and the<00:03:38.000> proof<00:03:38.209> of<00:03:38.329> work<00:03:38.480> chip<00:03:39.430> so<00:03:40.430> that's<00:03:41.120> the 00:03:41.520 --> 00:03:41.530 align:start position:0% the proof of work chip so that's the 00:03:41.530 --> 00:03:44.310 align:start position:0% the proof of work chip so that's the simple<00:03:42.530> high-level<00:03:43.400> overview<00:03:43.579> of<00:03:43.940> this 00:03:44.310 --> 00:03:44.320 align:start position:0% simple high-level overview of this 00:03:44.320 --> 00:03:50.229 align:start position:0% simple high-level overview of this system<00:03:45.340> and<00:03:46.630> I<00:03:48.040> won't<00:03:49.040> know<00:03:49.340> when<00:03:49.579> focus<00:03:50.030> on 00:03:50.229 --> 00:03:50.239 align:start position:0% system and I won't know when focus on 00:03:50.239 --> 00:03:55.330 align:start position:0% system and I won't know when focus on long<00:03:51.579> talk<00:03:52.579> about<00:03:52.850> the<00:03:53.060> kind<00:03:53.329> side<00:03:53.920> so<00:03:54.920> I<00:03:54.950> think 00:03:55.330 --> 00:03:55.340 align:start position:0% long talk about the kind side so I think 00:03:55.340 --> 00:03:58.229 align:start position:0% long talk about the kind side so I think high<00:03:55.609> is<00:03:55.970> the<00:03:56.359> heart<00:03:56.750> of<00:03:56.930> Israel<00:03:57.140> right<00:03:57.650> now 00:03:58.229 --> 00:03:58.239 align:start position:0% high is the heart of Israel right now 00:03:58.239 --> 00:04:02.199 align:start position:0% high is the heart of Israel right now we<00:03:59.239> never<00:03:59.420> happy<00:04:00.319> to<00:04:00.709> have<00:04:00.950> many<00:04:01.250> deaths<00:04:01.970> and 00:04:02.199 --> 00:04:02.209 align:start position:0% we never happy to have many deaths and 00:04:02.209 --> 00:04:03.809 align:start position:0% we never happy to have many deaths and things<00:04:02.569> they<00:04:02.810> are<00:04:02.840> working<00:04:02.930> on<00:04:03.350> the<00:04:03.560> system 00:04:03.809 --> 00:04:03.819 align:start position:0% things they are working on the system 00:04:03.819 --> 00:04:07.890 align:start position:0% things they are working on the system and<00:04:04.819> we<00:04:05.420> want<00:04:05.690> to<00:04:05.989> shout<00:04:06.380> out<00:04:06.560> their<00:04:06.799> name<00:04:06.880> here 00:04:07.890 --> 00:04:07.900 align:start position:0% and we want to shout out their name here 00:04:07.900 --> 00:04:13.680 align:start position:0% and we want to shout out their name here we<00:04:08.900> have<00:04:09.609> harmony<00:04:11.019> lighthouse<00:04:12.069> lost<00:04:13.069> our 00:04:13.680 --> 00:04:13.690 align:start position:0% we have harmony lighthouse lost our 00:04:13.690 --> 00:04:19.029 align:start position:0% we have harmony lighthouse lost our numbers<00:04:15.039> Pantheon's<00:04:16.389> prison<00:04:17.389> and<00:04:18.039> parity 00:04:19.029 --> 00:04:19.039 align:start position:0% numbers Pantheon's prison and parity 00:04:19.039 --> 00:04:22.320 align:start position:0% numbers Pantheon's prison and parity substrate<00:04:19.609> Chester<00:04:20.150> and<00:04:20.389> Trinity<00:04:21.229> we<00:04:21.830> have<00:04:21.979> a 00:04:22.320 --> 00:04:22.330 align:start position:0% substrate Chester and Trinity we have a 00:04:22.330 --> 00:04:29.320 align:start position:0% substrate Chester and Trinity we have a active<00:04:23.590> highs<00:04:24.590> right<00:04:24.860> now 00:04:29.320 --> 00:04:29.330 align:start position:0% 00:04:29.330 --> 00:04:32.809 align:start position:0% and<00:04:30.330> now<00:04:30.690> research<00:04:31.620> team<00:04:31.889> and<00:04:32.099> always<00:04:32.460> find 00:04:32.809 --> 00:04:32.819 align:start position:0% and now research team and always find 00:04:32.819 --> 00:04:34.879 align:start position:0% and now research team and always find their<00:04:33.090> researchers<00:04:33.720> develops<00:04:34.229> we<00:04:34.770> are 00:04:34.879 --> 00:04:34.889 align:start position:0% their researchers develops we are 00:04:34.889 --> 00:04:39.140 align:start position:0% their researchers develops we are walking<00:04:35.099> on<00:04:35.610> the<00:04:36.710> open<00:04:37.710> source<00:04:37.919> you<00:04:38.610> have 00:04:39.140 --> 00:04:39.150 align:start position:0% walking on the open source you have 00:04:39.150 --> 00:04:42.559 align:start position:0% walking on the open source you have repository<00:04:40.080> and<00:04:40.580> it's<00:04:41.580> a<00:04:41.729> community<00:04:41.940> walk<00:04:42.330> and 00:04:42.559 --> 00:04:42.569 align:start position:0% repository and it's a community walk and 00:04:42.569 --> 00:04:46.339 align:start position:0% repository and it's a community walk and everyone<00:04:42.930> can<00:04:43.199> make<00:04:43.860> an<00:04:44.009> issue<00:04:44.190> and<00:04:45.110> get<00:04:46.110> some 00:04:46.339 --> 00:04:46.349 align:start position:0% everyone can make an issue and get some 00:04:46.349 --> 00:04:49.610 align:start position:0% everyone can make an issue and get some input<00:04:46.560> down<00:04:46.830> here<00:04:47.099> and<00:04:47.970> I<00:04:48.810> also<00:04:49.050> wanted<00:04:49.470> to 00:04:49.610 --> 00:04:49.620 align:start position:0% input down here and I also wanted to 00:04:49.620 --> 00:04:53.749 align:start position:0% input down here and I also wanted to shout<00:04:49.919> out<00:04:50.129> to<00:04:50.400> Danny<00:04:50.759> Ryan<00:04:51.030> and<00:04:51.690> he<00:04:52.759> he 00:04:53.749 --> 00:04:53.759 align:start position:0% shout out to Danny Ryan and he he 00:04:53.759 --> 00:04:56.240 align:start position:0% shout out to Danny Ryan and he he organized<00:04:54.120> by<00:04:54.539> weight<00:04:55.139> to<00:04:55.319> you<00:04:55.470> community 00:04:56.240 --> 00:04:56.250 align:start position:0% organized by weight to you community 00:04:56.250 --> 00:05:01.510 align:start position:0% organized by weight to you community call<00:04:56.490> and<00:04:56.819> so<00:04:57.720> are<00:04:58.409> some<00:04:59.219> ongoing<00:04:59.569> discussion 00:05:01.510 --> 00:05:01.520 align:start position:0% call and so are some ongoing discussion 00:05:01.520 --> 00:05:09.730 align:start position:0% call and so are some ongoing discussion with<00:05:02.520> Rico<00:05:03.030> Thank<00:05:03.960> You<00:05:04.110> Danny 00:05:09.730 --> 00:05:09.740 align:start position:0% 00:05:09.740 --> 00:05:14.180 align:start position:0% and<00:05:10.969> all<00:05:11.969> these<00:05:12.150> pies<00:05:12.810> they<00:05:13.379> are<00:05:13.530> all<00:05:13.770> open 00:05:14.180 --> 00:05:14.190 align:start position:0% and all these pies they are all open 00:05:14.190 --> 00:05:20.659 align:start position:0% and all these pies they are all open sourcing<00:05:14.759> up<00:05:14.879> I<00:05:15.180> think<00:05:15.389> yeah<00:05:17.960> um<00:05:19.159> with<00:05:20.159> this<00:05:20.400> um 00:05:20.659 --> 00:05:20.669 align:start position:0% sourcing up I think yeah um with this um 00:05:20.669 --> 00:05:24.350 align:start position:0% sourcing up I think yeah um with this um a<00:05:21.289> strong<00:05:22.289> community<00:05:22.770> we<00:05:23.129> can<00:05:23.340> have<00:05:23.940> a<00:05:23.969> chance 00:05:24.350 --> 00:05:24.360 align:start position:0% a strong community we can have a chance 00:05:24.360 --> 00:05:29.629 align:start position:0% a strong community we can have a chance to<00:05:24.629> read<00:05:24.810> aside<00:05:25.259> idea<00:05:26.039> black<00:05:26.340> transistor<00:05:28.639> so 00:05:29.629 --> 00:05:29.639 align:start position:0% to read aside idea black transistor so 00:05:29.639 --> 00:05:32.330 align:start position:0% to read aside idea black transistor so that's<00:05:30.419> some<00:05:30.690> example<00:05:31.409> that<00:05:31.650> list<00:05:31.919> are<00:05:32.099> some 00:05:32.330 --> 00:05:32.340 align:start position:0% that's some example that list are some 00:05:32.340 --> 00:05:34.480 align:start position:0% that's some example that list are some question<00:05:32.849> issues<00:05:33.210> that<00:05:33.419> we<00:05:33.569> are<00:05:33.599> working<00:05:33.750> on 00:05:34.480 --> 00:05:34.490 align:start position:0% question issues that we are working on 00:05:34.490 --> 00:05:39.140 align:start position:0% question issues that we are working on for<00:05:35.490> example<00:05:35.580> that<00:05:36.300> because<00:05:37.190> there<00:05:38.190> are<00:05:38.219> many 00:05:39.140 --> 00:05:39.150 align:start position:0% for example that because there are many 00:05:39.150 --> 00:05:42.920 align:start position:0% for example that because there are many roads<00:05:40.110> on<00:05:40.469> the<00:05:40.919> internet<00:05:41.340> for<00:05:41.729> the<00:05:42.060> proof<00:05:42.779> of 00:05:42.920 --> 00:05:42.930 align:start position:0% roads on the internet for the proof of 00:05:42.930 --> 00:05:45.529 align:start position:0% roads on the internet for the proof of stake<00:05:43.229> system<00:05:43.949> because<00:05:44.279> everybody<00:05:45.150> literally 00:05:45.529 --> 00:05:45.539 align:start position:0% stake system because everybody literally 00:05:45.539 --> 00:05:48.320 align:start position:0% stake system because everybody literally have<00:05:45.719> to<00:05:45.900> broadcast<00:05:46.380> their<00:05:46.560> individual<00:05:47.330> votes 00:05:48.320 --> 00:05:48.330 align:start position:0% have to broadcast their individual votes 00:05:48.330 --> 00:05:52.969 align:start position:0% have to broadcast their individual votes to<00:05:48.659> say<00:05:48.930> hey<00:05:49.110> this<00:05:49.319> block<00:05:49.620> is<00:05:49.860> valid<00:05:50.460> or<00:05:50.699> and<00:05:51.979> if 00:05:52.969 --> 00:05:52.979 align:start position:0% to say hey this block is valid or and if 00:05:52.979 --> 00:05:56.330 align:start position:0% to say hey this block is valid or and if we<00:05:53.250> want<00:05:53.669> to<00:05:53.759> have<00:05:54.240> them<00:05:54.419> like<00:05:55.409> thousands 00:05:56.330 --> 00:05:56.340 align:start position:0% we want to have them like thousands 00:05:56.340 --> 00:06:00.110 align:start position:0% we want to have them like thousands shots<00:05:56.789> in<00:05:57.120> this<00:05:57.330> system<00:05:57.620> the<00:05:58.620> trapeze<00:05:59.069> is<00:05:59.940> not 00:06:00.110 --> 00:06:00.120 align:start position:0% shots in this system the trapeze is not 00:06:00.120 --> 00:06:02.860 align:start position:0% shots in this system the trapeze is not good<00:06:00.330> for<00:06:00.360> network<00:06:00.900> traffic<00:06:01.110> so<00:06:02.069> how<00:06:02.340> to<00:06:02.400> make 00:06:02.860 --> 00:06:02.870 align:start position:0% good for network traffic so how to make 00:06:02.870 --> 00:06:07.070 align:start position:0% good for network traffic so how to make how<00:06:03.870> to<00:06:03.930> build<00:06:04.229> an<00:06:04.379> efficient<00:06:06.080> signature 00:06:07.070 --> 00:06:07.080 align:start position:0% how to build an efficient signature 00:06:07.080 --> 00:06:10.339 align:start position:0% how to build an efficient signature application<00:06:07.770> protocol<00:06:08.639> or<00:06:09.150> in<00:06:09.810> the 00:06:10.339 --> 00:06:10.349 align:start position:0% application protocol or in the 00:06:10.349 --> 00:06:14.209 align:start position:0% application protocol or in the cryptography<00:06:11.690> thinking<00:06:12.690> that's<00:06:13.680> a<00:06:13.830> problem 00:06:14.209 --> 00:06:14.219 align:start position:0% cryptography thinking that's a problem 00:06:14.219 --> 00:06:17.209 align:start position:0% cryptography thinking that's a problem and<00:06:14.400> also<00:06:15.330> we<00:06:15.599> have<00:06:15.779> a<00:06:15.810> chance<00:06:16.199> to<00:06:16.469> change<00:06:16.949> the 00:06:17.209 --> 00:06:17.219 align:start position:0% and also we have a chance to change the 00:06:17.219 --> 00:06:20.980 align:start position:0% and also we have a chance to change the IOP<00:06:18.180> data<00:06:18.389> serialization<00:06:19.219> into<00:06:20.219> something 00:06:20.980 --> 00:06:20.990 align:start position:0% IOP data serialization into something 00:06:20.990 --> 00:06:27.620 align:start position:0% IOP data serialization into something more<00:06:21.990> efficient<00:06:22.590> or<00:06:22.849> simpler 00:06:27.620 --> 00:06:27.630 align:start position:0% 00:06:27.630 --> 00:06:30.740 align:start position:0% and<00:06:27.720> for<00:06:28.500> the<00:06:28.770> name<00:06:28.920> walk<00:06:29.130> scilab<00:06:29.730> there's<00:06:30.660> a 00:06:30.740 --> 00:06:30.750 align:start position:0% and for the name walk scilab there's a 00:06:30.750 --> 00:06:35.650 align:start position:0% and for the name walk scilab there's a problem<00:06:31.380> is<00:06:31.740> that<00:06:31.980> because<00:06:32.930> for<00:06:33.930> I'm<00:06:34.620> the<00:06:35.040> I 00:06:35.650 --> 00:06:35.660 align:start position:0% problem is that because for I'm the I 00:06:35.660 --> 00:06:39.320 align:start position:0% problem is that because for I'm the I say<00:06:36.660> that<00:06:36.900> the<00:06:37.560> validator<00:06:37.920> will<00:06:38.280> be<00:06:39.090> rendered 00:06:39.320 --> 00:06:39.330 align:start position:0% say that the validator will be rendered 00:06:39.330 --> 00:06:43.730 align:start position:0% say that the validator will be rendered I<00:06:39.570> traveled<00:06:40.200> to<00:06:40.470> a<00:06:41.870> stylist<00:06:42.870> I<00:06:42.990> will<00:06:43.260> be<00:06:43.440> aside 00:06:43.730 --> 00:06:43.740 align:start position:0% I traveled to a stylist I will be aside 00:06:43.740 --> 00:06:47.690 align:start position:0% I traveled to a stylist I will be aside to<00:06:44.090> very<00:06:45.090> day<00:06:45.300> sounds<00:06:45.900> basic<00:06:46.350> shot<00:06:46.700> English 00:06:47.690 --> 00:06:47.700 align:start position:0% to very day sounds basic shot English 00:06:47.700 --> 00:06:51.980 align:start position:0% to very day sounds basic shot English basic<00:06:48.270> Thai<00:06:49.140> slots<00:06:49.490> which<00:06:50.490> means<00:06:50.760> that<00:06:51.030> when 00:06:51.980 --> 00:06:51.990 align:start position:0% basic Thai slots which means that when 00:06:51.990 --> 00:06:57.440 align:start position:0% basic Thai slots which means that when the<00:06:53.810> condition<00:06:54.810> by<00:06:55.230> later<00:06:55.850> they<00:06:56.850> will<00:06:57.030> they 00:06:57.440 --> 00:06:57.450 align:start position:0% the condition by later they will they 00:06:57.450 --> 00:07:00.230 align:start position:0% the condition by later they will they will<00:06:57.480> be<00:06:57.780> asked<00:06:58.140> to<00:06:58.170> hey<00:06:58.560> I<00:06:58.590> have<00:06:59.220> to<00:06:59.250> wear<00:07:00.090> it 00:07:00.230 --> 00:07:00.240 align:start position:0% will be asked to hey I have to wear it 00:07:00.240 --> 00:07:04.190 align:start position:0% will be asked to hey I have to wear it it<00:07:00.450> welded<00:07:01.110> shut<00:07:01.620> lock<00:07:02.400> like<00:07:02.820> in<00:07:03.120> ten<00:07:03.600> minutes 00:07:04.190 --> 00:07:04.200 align:start position:0% it welded shut lock like in ten minutes 00:07:04.200 --> 00:07:07.430 align:start position:0% it welded shut lock like in ten minutes for<00:07:04.440> example<00:07:04.800> then<00:07:05.550> they<00:07:05.760> it's<00:07:06.330> easy<00:07:07.050> in 00:07:07.430 --> 00:07:07.440 align:start position:0% for example then they it's easy in 00:07:07.440 --> 00:07:10.280 align:start position:0% for example then they it's easy in protocol<00:07:07.950> but<00:07:08.160> if<00:07:08.490> we<00:07:09.300> say<00:07:09.540> that<00:07:09.750> in<00:07:09.930> the 00:07:10.280 --> 00:07:10.290 align:start position:0% protocol but if we say that in the 00:07:10.290 --> 00:07:14.090 align:start position:0% protocol but if we say that in the network<00:07:10.530> layer<00:07:10.740> they<00:07:11.340> have<00:07:11.550> to<00:07:12.500> move<00:07:13.500> their 00:07:14.090 --> 00:07:14.100 align:start position:0% network layer they have to move their 00:07:14.100 --> 00:07:17.840 align:start position:0% network layer they have to move their peers<00:07:15.000> they<00:07:15.420> work<00:07:15.600> in<00:07:15.840> two<00:07:16.080> different<00:07:16.850> network 00:07:17.840 --> 00:07:17.850 align:start position:0% peers they work in two different network 00:07:17.850 --> 00:07:23.000 align:start position:0% peers they work in two different network so<00:07:18.480> it<00:07:18.780> will<00:07:19.310> cause<00:07:20.310> a<00:07:20.340> lot<00:07:21.710> carnation<00:07:22.710> tie<00:07:22.950> to 00:07:23.000 --> 00:07:23.010 align:start position:0% so it will cause a lot carnation tie to 00:07:23.010 --> 00:07:28.220 align:start position:0% so it will cause a lot carnation tie to the<00:07:23.910> peer<00:07:24.690> discovery<00:07:25.290> and<00:07:25.530> thinking<00:07:26.270> so<00:07:27.270> we 00:07:28.220 --> 00:07:28.230 align:start position:0% the peer discovery and thinking so we 00:07:28.230 --> 00:07:30.740 align:start position:0% the peer discovery and thinking so we need<00:07:28.440> to<00:07:28.680> redesign<00:07:29.010> a<00:07:29.250> new<00:07:29.580> technology<00:07:30.450> and 00:07:30.740 --> 00:07:30.750 align:start position:0% need to redesign a new technology and 00:07:30.750 --> 00:07:35.420 align:start position:0% need to redesign a new technology and new<00:07:31.620> pH<00:07:32.160> management<00:07:32.700> system<00:07:33.180> to<00:07:33.980> deal<00:07:34.980> with<00:07:35.220> it 00:07:35.420 --> 00:07:35.430 align:start position:0% new pH management system to deal with it 00:07:35.430 --> 00:07:40.400 align:start position:0% new pH management system to deal with it so<00:07:36.620> our<00:07:37.620> current<00:07:38.130> idea<00:07:38.460> is<00:07:39.060> that<00:07:39.480> we<00:07:39.990> can<00:07:40.020> use 00:07:40.400 --> 00:07:40.410 align:start position:0% so our current idea is that we can use 00:07:40.410 --> 00:07:45.370 align:start position:0% so our current idea is that we can use the<00:07:40.650> liquid<00:07:41.160> to<00:07:41.280> pick<00:07:41.490> a<00:07:41.700> zips<00:07:42.000> up<00:07:43.520> china's<00:07:44.520> to 00:07:45.370 --> 00:07:45.380 align:start position:0% the liquid to pick a zips up china's to 00:07:45.380 --> 00:07:50.660 align:start position:0% the liquid to pick a zips up china's to gossip<00:07:46.380> channels<00:07:46.860> to<00:07:47.690> like<00:07:48.690> a<00:07:48.990> sigh<00:07:49.500> of<00:07:49.670> shot 00:07:50.660 --> 00:07:50.670 align:start position:0% gossip channels to like a sigh of shot 00:07:50.670 --> 00:07:54.230 align:start position:0% gossip channels to like a sigh of shot for<00:07:51.030> sounds<00:07:51.570> basic<00:07:51.990> channels<00:07:52.640> in<00:07:53.640> that<00:07:53.850> way<00:07:54.030> we 00:07:54.230 --> 00:07:54.240 align:start position:0% for sounds basic channels in that way we 00:07:54.240 --> 00:08:01.190 align:start position:0% for sounds basic channels in that way we can<00:07:54.450> reduce<00:07:55.050> the<00:07:55.590> connection<00:07:56.430> overhead<00:07:59.150> and<00:08:00.200> I 00:08:01.190 --> 00:08:01.200 align:start position:0% can reduce the connection overhead and I 00:08:01.200 --> 00:08:03.050 align:start position:0% can reduce the connection overhead and I like<00:08:01.650> to<00:08:01.920> spend<00:08:02.220> some<00:08:02.310> time<00:08:02.430> for<00:08:02.910> the 00:08:03.050 --> 00:08:03.060 align:start position:0% like to spend some time for the 00:08:03.060 --> 00:08:08.390 align:start position:0% like to spend some time for the presentation<00:08:05.900> so<00:08:06.900> because<00:08:07.410> we<00:08:07.800> have<00:08:07.830> a<00:08:08.040> big 00:08:08.390 --> 00:08:08.400 align:start position:0% presentation so because we have a big 00:08:08.400 --> 00:08:12.110 align:start position:0% presentation so because we have a big concern<00:08:08.760> reference<00:08:09.420> that<00:08:10.400> and<00:08:11.400> in<00:08:11.700> a<00:08:11.820> flag 00:08:12.110 --> 00:08:12.120 align:start position:0% concern reference that and in a flag 00:08:12.120 --> 00:08:15.470 align:start position:0% concern reference that and in a flag effect<00:08:12.780> the<00:08:12.960> current<00:08:13.200> spec<00:08:13.620> but<00:08:14.490> now<00:08:15.180> we<00:08:15.240> also 00:08:15.470 --> 00:08:15.480 align:start position:0% effect the current spec but now we also 00:08:15.480 --> 00:08:19.100 align:start position:0% effect the current spec but now we also want<00:08:15.690> to<00:08:16.200> hold<00:08:17.100> it<00:08:17.400> in<00:08:17.730> to<00:08:18.450> the<00:08:18.720> production 00:08:19.100 --> 00:08:19.110 align:start position:0% want to hold it in to the production 00:08:19.110 --> 00:08:21.830 align:start position:0% want to hold it in to the production environment<00:08:19.680> because<00:08:20.520> I<00:08:20.820> want<00:08:21.480> to<00:08:21.630> make<00:08:21.810> a 00:08:21.830 --> 00:08:21.840 align:start position:0% environment because I want to make a 00:08:21.840 --> 00:08:28.040 align:start position:0% environment because I want to make a test<00:08:22.710> now<00:08:22.830> in<00:08:23.100> Python<00:08:23.520> yay 00:08:28.040 --> 00:08:28.050 align:start position:0% 00:08:28.050 --> 00:08:30.930 align:start position:0% and<00:08:29.050> Trinity<00:08:29.620> is<00:08:29.830> the<00:08:29.860> seventh<00:08:30.610> one<00:08:30.640> point 00:08:30.930 --> 00:08:30.940 align:start position:0% and Trinity is the seventh one point 00:08:30.940 --> 00:08:34.800 align:start position:0% and Trinity is the seventh one point okay<00:08:31.390> we've<00:08:32.169> built<00:08:32.979> with<00:08:33.130> Python<00:08:33.640> led<00:08:34.570> by 00:08:34.800 --> 00:08:34.810 align:start position:0% okay we've built with Python led by 00:08:34.810 --> 00:08:38.279 align:start position:0% okay we've built with Python led by Piper<00:08:35.349> Miriam<00:08:35.710> and<00:08:36.099> his<00:08:36.520> and<00:08:37.060> his<00:08:37.570> team<00:08:37.870> the 00:08:38.279 --> 00:08:38.289 align:start position:0% Piper Miriam and his and his team the 00:08:38.289 --> 00:08:42.899 align:start position:0% Piper Miriam and his and his team the snake<00:08:39.190> tremors<00:08:40.140> and<00:08:41.250> it's<00:08:42.250> open<00:08:42.550> source<00:08:42.580> now 00:08:42.899 --> 00:08:42.909 align:start position:0% snake tremors and it's open source now 00:08:42.909 --> 00:08:47.070 align:start position:0% snake tremors and it's open source now you<00:08:43.690> can<00:08:43.930> check<00:08:44.440> their<00:08:44.910> website<00:08:45.910> and<00:08:46.150> link<00:08:46.900> to 00:08:47.070 --> 00:08:47.080 align:start position:0% you can check their website and link to 00:08:47.080 --> 00:08:51.330 align:start position:0% you can check their website and link to the<00:08:47.260> repository<00:08:48.630> and<00:08:49.710> if<00:08:50.710> we<00:08:50.860> see<00:08:51.130> the 00:08:51.330 --> 00:08:51.340 align:start position:0% the repository and if we see the 00:08:51.340 --> 00:08:54.690 align:start position:0% the repository and if we see the architectural<00:08:52.090> layer<00:08:52.330> by<00:08:52.570> layer<00:08:53.520> there<00:08:54.520> will 00:08:54.690 --> 00:08:54.700 align:start position:0% architectural layer by layer there will 00:08:54.700 --> 00:08:58.020 align:start position:0% architectural layer by layer there will be<00:08:54.730> an<00:08:54.910> echo<00:08:55.090> layer<00:08:55.390> and<00:08:56.430> state<00:08:57.430> extrusion 00:08:58.020 --> 00:08:58.030 align:start position:0% be an echo layer and state extrusion 00:08:58.030 --> 00:08:59.820 align:start position:0% be an echo layer and state extrusion they're<00:08:58.210> like<00:08:58.600> beacon<00:08:58.990> chance<00:08:59.290> state 00:08:59.820 --> 00:08:59.830 align:start position:0% they're like beacon chance state 00:08:59.830 --> 00:09:02.910 align:start position:0% they're like beacon chance state machines<00:09:00.490> different<00:09:01.120> from<00:09:02.080> evn<00:09:02.590> it's<00:09:02.710> quite 00:09:02.910 --> 00:09:02.920 align:start position:0% machines different from evn it's quite 00:09:02.920 --> 00:09:05.850 align:start position:0% machines different from evn it's quite simple<00:09:03.310> and<00:09:03.730> for<00:09:04.240> a<00:09:04.300> shot<00:09:04.570> we<00:09:05.080> will<00:09:05.260> have<00:09:05.500> like 00:09:05.850 --> 00:09:05.860 align:start position:0% simple and for a shot we will have like 00:09:05.860 --> 00:09:08.910 align:start position:0% simple and for a shot we will have like it<00:09:06.070> wasn't<00:09:06.250> in<00:09:06.760> the<00:09:06.910> system<00:09:07.120> and<00:09:07.920> different 00:09:08.910 --> 00:09:08.920 align:start position:0% it wasn't in the system and different 00:09:08.920 --> 00:09:11.940 align:start position:0% it wasn't in the system and different chains<00:09:09.220> and<00:09:09.930> different<00:09:10.930> Kairos<00:09:11.380> because<00:09:11.800> we 00:09:11.940 --> 00:09:11.950 align:start position:0% chains and different Kairos because we 00:09:11.950 --> 00:09:13.890 align:start position:0% chains and different Kairos because we now<00:09:12.070> we<00:09:12.130> are<00:09:12.370> using<00:09:12.850> the<00:09:13.120> validator<00:09:13.480> or<00:09:13.750> not 00:09:13.890 --> 00:09:13.900 align:start position:0% now we are using the validator or not 00:09:13.900 --> 00:09:17.880 align:start position:0% now we are using the validator or not minor<00:09:14.380> and<00:09:15.480> the<00:09:16.480> last<00:09:16.720> I<00:09:16.930> want<00:09:17.440> to<00:09:17.590> encourage 00:09:17.880 --> 00:09:17.890 align:start position:0% minor and the last I want to encourage 00:09:17.890 --> 00:09:21.090 align:start position:0% minor and the last I want to encourage you<00:09:18.220> to<00:09:18.520> check<00:09:18.820> out<00:09:18.970> those<00:09:19.390> resource<00:09:19.960> if<00:09:20.950> you 00:09:21.090 --> 00:09:21.100 align:start position:0% you to check out those resource if you 00:09:21.100 --> 00:09:23.880 align:start position:0% you to check out those resource if you want<00:09:21.400> to<00:09:21.550> participate<00:09:21.730> more<00:09:22.240> and<00:09:22.750> I<00:09:23.560> think<00:09:23.620> we 00:09:23.880 --> 00:09:23.890 align:start position:0% want to participate more and I think we 00:09:23.890 --> 00:09:25.910 align:start position:0% want to participate more and I think we are<00:09:24.040> doing<00:09:24.190> something<00:09:24.520> really<00:09:24.760> cool<00:09:24.910> here<00:09:25.510> and 00:09:25.910 --> 00:09:25.920 align:start position:0% are doing something really cool here and 00:09:25.920 --> 00:09:29.160 align:start position:0% are doing something really cool here and thank<00:09:26.920> you<00:09:27.040> for<00:09:27.250> community<00:09:27.880> contribution<00:09:28.690> and 00:09:29.160 --> 00:09:29.170 align:start position:0% thank you for community contribution and 00:09:29.170 --> 00:09:36.510 align:start position:0% thank you for community contribution and thank<00:09:30.010> you<00:09:30.160> for<00:09:30.430> your<00:09:30.700> listening<00:09:30.790> and<00:09:35.520> next 00:09:36.510 --> 00:09:36.520 align:start position:0% thank you for your listening and next 00:09:36.520 --> 00:09:38.700 align:start position:0% thank you for your listening and next Ron<00:09:36.820> found<00:09:37.150> prismatic<00:09:37.690> left<00:09:37.960> he<00:09:38.440> will<00:09:38.560> give 00:09:38.700 --> 00:09:38.710 align:start position:0% Ron found prismatic left he will give 00:09:38.710 --> 00:09:45.880 align:start position:0% Ron found prismatic left he will give you<00:09:38.830> a<00:09:38.860> talk<00:09:39.160> about<00:09:40.080> their<00:09:41.080> golden<00:09:41.530> exultation 00:09:45.880 --> 00:09:45.890 align:start position:0% 00:09:45.890 --> 00:09:53.830 align:start position:0% [Music] 00:09:53.830 --> 00:09:53.840 align:start position:0% [Music] 00:09:53.840 --> 00:09:57.410 align:start position:0% [Music] all<00:09:54.840> right<00:09:55.280> well<00:09:56.280> so<00:09:56.520> thank<00:09:56.820> you<00:09:56.910> shall<00:09:57.090> we<00:09:57.210> for 00:09:57.410 --> 00:09:57.420 align:start position:0% all right well so thank you shall we for 00:09:57.420 --> 00:09:59.210 align:start position:0% all right well so thank you shall we for the<00:09:57.540> amazing<00:09:57.900> presentation<00:09:58.410> I<00:09:58.530> think<00:09:58.590> it's 00:09:59.210 --> 00:09:59.220 align:start position:0% the amazing presentation I think it's 00:09:59.220 --> 00:10:02.210 align:start position:0% the amazing presentation I think it's been<00:09:59.640> so<00:10:00.120> incredible<00:10:00.720> how<00:10:00.900> ever<00:10:01.500> since<00:10:01.920> kind 00:10:02.210 --> 00:10:02.220 align:start position:0% been so incredible how ever since kind 00:10:02.220 --> 00:10:05.120 align:start position:0% been so incredible how ever since kind of<00:10:02.400> the<00:10:03.000> etherium<00:10:03.450> charting<00:10:03.810> efforts<00:10:04.130> first 00:10:05.120 --> 00:10:05.130 align:start position:0% of the etherium charting efforts first 00:10:05.130 --> 00:10:08.300 align:start position:0% of the etherium charting efforts first spun<00:10:05.400> up<00:10:05.810> there<00:10:06.810> was<00:10:06.930> essentially<00:10:07.380> nobody 00:10:08.300 --> 00:10:08.310 align:start position:0% spun up there was essentially nobody 00:10:08.310 --> 00:10:09.980 align:start position:0% spun up there was essentially nobody working<00:10:08.700> on<00:10:08.850> this<00:10:09.060> there<00:10:09.600> were<00:10:09.690> a<00:10:09.720> few 00:10:09.980 --> 00:10:09.990 align:start position:0% working on this there were a few 00:10:09.990 --> 00:10:12.260 align:start position:0% working on this there were a few reference<00:10:10.470> implementation<00:10:11.220> a<00:10:11.250> few<00:10:11.880> reference 00:10:12.260 --> 00:10:12.270 align:start position:0% reference implementation a few reference 00:10:12.270 --> 00:10:15.290 align:start position:0% reference implementation a few reference specs<00:10:12.900> out<00:10:13.080> there<00:10:13.320> a<00:10:13.350> few<00:10:13.560> blog<00:10:13.740> posts<00:10:13.910> but<00:10:14.910> in 00:10:15.290 --> 00:10:15.300 align:start position:0% specs out there a few blog posts but in 00:10:15.300 --> 00:10:17.690 align:start position:0% specs out there a few blog posts but in the<00:10:15.390> span<00:10:15.630> of<00:10:15.660> less<00:10:15.990> than<00:10:16.290> a<00:10:16.470> year<00:10:16.800> there<00:10:17.610> have 00:10:17.690 --> 00:10:17.700 align:start position:0% the span of less than a year there have 00:10:17.700 --> 00:10:18.950 align:start position:0% the span of less than a year there have been<00:10:17.820> more<00:10:18.060> than<00:10:18.240> eight<00:10:18.390> teams<00:10:18.720> just 00:10:18.950 --> 00:10:18.960 align:start position:0% been more than eight teams just 00:10:18.960 --> 00:10:21.110 align:start position:0% been more than eight teams just aggregating<00:10:19.560> coming<00:10:19.920> together<00:10:20.160> and<00:10:20.460> putting 00:10:21.110 --> 00:10:21.120 align:start position:0% aggregating coming together and putting 00:10:21.120 --> 00:10:22.340 align:start position:0% aggregating coming together and putting together<00:10:21.300> something<00:10:21.780> that<00:10:21.990> will<00:10:22.110> work<00:10:22.200> in 00:10:22.340 --> 00:10:22.350 align:start position:0% together something that will work in 00:10:22.350 --> 00:10:24.260 align:start position:0% together something that will work in production<00:10:22.800> as<00:10:23.250> the<00:10:23.310> next<00:10:23.580> iteration<00:10:23.910> of<00:10:24.120> our 00:10:24.260 --> 00:10:24.270 align:start position:0% production as the next iteration of our 00:10:24.270 --> 00:10:26.900 align:start position:0% production as the next iteration of our platform<00:10:24.750> so<00:10:25.010> today<00:10:26.010> I<00:10:26.250> will<00:10:26.670> be<00:10:26.760> talking 00:10:26.900 --> 00:10:26.910 align:start position:0% platform so today I will be talking 00:10:26.910 --> 00:10:30.230 align:start position:0% platform so today I will be talking about<00:10:27.150> implementing<00:10:27.860> prism<00:10:28.860> which<00:10:29.340> is<00:10:29.490> our<00:10:29.700> go 00:10:30.230 --> 00:10:30.240 align:start position:0% about implementing prism which is our go 00:10:30.240 --> 00:10:32.990 align:start position:0% about implementing prism which is our go client<00:10:30.660> for<00:10:30.900> aetherium<00:10:31.200> 2.0<00:10:31.710> and<00:10:31.920> I<00:10:32.730> just<00:10:32.880> want 00:10:32.990 --> 00:10:33.000 align:start position:0% client for aetherium 2.0 and I just want 00:10:33.000 --> 00:10:33.890 align:start position:0% client for aetherium 2.0 and I just want to<00:10:33.060> give<00:10:33.180> a<00:10:33.210> little<00:10:33.330> bit<00:10:33.510> of<00:10:33.570> a<00:10:33.720> background 00:10:33.890 --> 00:10:33.900 align:start position:0% to give a little bit of a background 00:10:33.900 --> 00:10:36.200 align:start position:0% to give a little bit of a background kind<00:10:34.380> of<00:10:34.470> who<00:10:34.590> we<00:10:34.740> are<00:10:34.770> so<00:10:35.580> my<00:10:35.700> name<00:10:35.820> is<00:10:35.850> Raul 00:10:36.200 --> 00:10:36.210 align:start position:0% kind of who we are so my name is Raul 00:10:36.210 --> 00:10:37.790 align:start position:0% kind of who we are so my name is Raul and<00:10:36.390> I<00:10:36.840> am<00:10:37.020> the<00:10:37.140> co-founder<00:10:37.320> of<00:10:37.560> prismatic 00:10:37.790 --> 00:10:37.800 align:start position:0% and I am the co-founder of prismatic 00:10:37.800 --> 00:10:40.670 align:start position:0% and I am the co-founder of prismatic labs<00:10:38.300> so<00:10:39.300> we<00:10:39.600> are<00:10:39.840> an<00:10:39.960> independent<00:10:40.200> team<00:10:40.560> of 00:10:40.670 --> 00:10:40.680 align:start position:0% labs so we are an independent team of 00:10:40.680 --> 00:10:42.800 align:start position:0% labs so we are an independent team of developers<00:10:40.800> that<00:10:41.340> aggregated<00:10:41.940> to<00:10:42.510> build<00:10:42.690> an 00:10:42.800 --> 00:10:42.810 align:start position:0% developers that aggregated to build an 00:10:42.810 --> 00:10:44.660 align:start position:0% developers that aggregated to build an implementation<00:10:43.320> for<00:10:43.470> shardene<00:10:43.890> Kaspar<00:10:44.400> and<00:10:44.430> a 00:10:44.660 --> 00:10:44.670 align:start position:0% implementation for shardene Kaspar and a 00:10:44.670 --> 00:10:46.100 align:start position:0% implementation for shardene Kaspar and a general<00:10:44.940> upgrade<00:10:45.270> to<00:10:45.360> the<00:10:45.450> etherium<00:10:45.840> network 00:10:46.100 --> 00:10:46.110 align:start position:0% general upgrade to the etherium network 00:10:46.110 --> 00:10:49.700 align:start position:0% general upgrade to the etherium network there<00:10:47.070> is<00:10:47.100> no<00:10:47.520> token<00:10:47.970> there<00:10:48.690> is<00:10:48.810> no<00:10:49.020> there's<00:10:49.620> no 00:10:49.700 --> 00:10:49.710 align:start position:0% there is no token there is no there's no 00:10:49.710 --> 00:10:52.160 align:start position:0% there is no token there is no there's no presale<00:10:50.310> there's<00:10:50.730> nothing<00:10:51.030> of<00:10:51.120> that<00:10:51.180> sort<00:10:51.270> we 00:10:52.160 --> 00:10:52.170 align:start position:0% presale there's nothing of that sort we 00:10:52.170 --> 00:10:54.020 align:start position:0% presale there's nothing of that sort we just<00:10:52.410> want<00:10:52.590> to<00:10:52.800> create<00:10:53.130> a<00:10:53.220> public<00:10:53.400> good<00:10:53.760> we 00:10:54.020 --> 00:10:54.030 align:start position:0% just want to create a public good we 00:10:54.030 --> 00:10:55.610 align:start position:0% just want to create a public good we understand<00:10:54.540> how<00:10:54.750> powerful<00:10:55.170> this<00:10:55.260> would<00:10:55.470> be 00:10:55.610 --> 00:10:55.620 align:start position:0% understand how powerful this would be 00:10:55.620 --> 00:10:57.410 align:start position:0% understand how powerful this would be for<00:10:56.250> everyone<00:10:56.490> to<00:10:56.700> use<00:10:56.910> and<00:10:57.090> we<00:10:57.210> want<00:10:57.360> to 00:10:57.410 --> 00:10:57.420 align:start position:0% for everyone to use and we want to 00:10:57.420 --> 00:10:58.010 align:start position:0% for everyone to use and we want to create<00:10:57.570> something<00:10:57.780> that<00:10:57.900> is 00:10:58.010 --> 00:10:58.020 align:start position:0% create something that is 00:10:58.020 --> 00:11:00.350 align:start position:0% create something that is production-grade<00:10:58.500> using<00:10:59.430> the<00:10:59.520> best<00:10:59.700> software 00:11:00.350 --> 00:11:00.360 align:start position:0% production-grade using the best software 00:11:00.360 --> 00:11:02.270 align:start position:0% production-grade using the best software engineering<00:11:00.840> practices<00:11:01.350> to<00:11:01.530> build<00:11:01.710> a<00:11:01.860> client 00:11:02.270 --> 00:11:02.280 align:start position:0% engineering practices to build a client 00:11:02.280 --> 00:11:09.310 align:start position:0% engineering practices to build a client like<00:11:02.400> this<00:11:03.860> so 00:11:09.310 --> 00:11:09.320 align:start position:0% 00:11:09.320 --> 00:11:13.100 align:start position:0% so<00:11:10.320> why<00:11:10.950> exactly<00:11:11.430> did<00:11:12.240> we<00:11:12.360> start<00:11:12.660> and<00:11:12.840> how 00:11:13.100 --> 00:11:13.110 align:start position:0% so why exactly did we start and how 00:11:13.110 --> 00:11:14.450 align:start position:0% so why exactly did we start and how exactly<00:11:13.560> does<00:11:13.710> this<00:11:13.890> happen 00:11:14.450 --> 00:11:14.460 align:start position:0% exactly does this happen 00:11:14.460 --> 00:11:17.120 align:start position:0% exactly does this happen so<00:11:15.000> we<00:11:15.150> fast-forward<00:11:15.750> kind<00:11:16.020> of<00:11:16.170> we'll<00:11:16.290> go<00:11:16.950> back 00:11:17.120 --> 00:11:17.130 align:start position:0% so we fast-forward kind of we'll go back 00:11:17.130 --> 00:11:20.930 align:start position:0% so we fast-forward kind of we'll go back to<00:11:17.790> the<00:11:18.270> late<00:11:18.710> 2017<00:11:19.710> where<00:11:20.190> italic<00:11:20.760> had<00:11:20.910> a 00:11:20.930 --> 00:11:20.940 align:start position:0% to the late 2017 where italic had a 00:11:20.940 --> 00:11:23.090 align:start position:0% to the late 2017 where italic had a basic<00:11:21.360> charting<00:11:21.720> FAQ<00:11:22.140> explaining<00:11:23.010> the 00:11:23.090 --> 00:11:23.100 align:start position:0% basic charting FAQ explaining the 00:11:23.100 --> 00:11:25.100 align:start position:0% basic charting FAQ explaining the possibility<00:11:23.700> of<00:11:23.880> having<00:11:24.060> a<00:11:24.300> parallelizable 00:11:25.100 --> 00:11:25.110 align:start position:0% possibility of having a parallelizable 00:11:25.110 --> 00:11:27.620 align:start position:0% possibility of having a parallelizable world<00:11:25.470> computer<00:11:25.950> this<00:11:26.940> was<00:11:27.120> the<00:11:27.210> start<00:11:27.480> of 00:11:27.620 --> 00:11:27.630 align:start position:0% world computer this was the start of 00:11:27.630 --> 00:11:30.800 align:start position:0% world computer this was the start of kind<00:11:28.140> of<00:11:28.200> a<00:11:28.320> new<00:11:28.440> initiative<00:11:28.620> there<00:11:29.610> were<00:11:29.810> it 00:11:30.800 --> 00:11:30.810 align:start position:0% kind of a new initiative there were it 00:11:30.810 --> 00:11:32.510 align:start position:0% kind of a new initiative there were it was<00:11:30.960> very<00:11:31.200> very<00:11:31.500> high<00:11:31.680> level<00:11:32.040> in<00:11:32.190> the<00:11:32.220> sense 00:11:32.510 --> 00:11:32.520 align:start position:0% was very very high level in the sense 00:11:32.520 --> 00:11:34.010 align:start position:0% was very very high level in the sense that<00:11:32.670> it<00:11:32.910> didn't<00:11:33.240> really<00:11:33.480> go<00:11:33.630> into<00:11:33.810> much 00:11:34.010 --> 00:11:34.020 align:start position:0% that it didn't really go into much 00:11:34.020 --> 00:11:36.290 align:start position:0% that it didn't really go into much detail<00:11:34.050> of<00:11:34.590> how<00:11:35.070> this<00:11:35.250> would<00:11:35.400> work<00:11:35.430> you<00:11:36.210> know 00:11:36.290 --> 00:11:36.300 align:start position:0% detail of how this would work you know 00:11:36.300 --> 00:11:38.390 align:start position:0% detail of how this would work you know like<00:11:36.510> how<00:11:37.020> feasible<00:11:37.650> would<00:11:37.770> this<00:11:37.860> be<00:11:38.010> from<00:11:38.220> an 00:11:38.390 --> 00:11:38.400 align:start position:0% like how feasible would this be from an 00:11:38.400 --> 00:11:40.000 align:start position:0% like how feasible would this be from an implementation<00:11:38.580> perspective<00:11:39.000> and 00:11:40.000 --> 00:11:40.010 align:start position:0% implementation perspective and 00:11:40.010 --> 00:11:42.200 align:start position:0% implementation perspective and essentially<00:11:41.010> a<00:11:41.130> bunch<00:11:41.520> of<00:11:41.640> a<00:11:41.820> bunch<00:11:41.940> of 00:11:42.200 --> 00:11:42.210 align:start position:0% essentially a bunch of a bunch of 00:11:42.210 --> 00:11:43.550 align:start position:0% essentially a bunch of a bunch of blockchain<00:11:42.510> developers<00:11:42.960> like<00:11:43.170> me<00:11:43.320> and<00:11:43.470> my 00:11:43.550 --> 00:11:43.560 align:start position:0% blockchain developers like me and my 00:11:43.560 --> 00:11:46.070 align:start position:0% blockchain developers like me and my team<00:11:43.770> were<00:11:44.040> you<00:11:44.310> know<00:11:44.400> scouring<00:11:44.910> gaiter<00:11:45.150> going 00:11:46.070 --> 00:11:46.080 align:start position:0% team were you know scouring gaiter going 00:11:46.080 --> 00:11:47.300 align:start position:0% team were you know scouring gaiter going through<00:11:46.230> github<00:11:46.320> issues<00:11:46.830> trying<00:11:47.130> to<00:11:47.190> get<00:11:47.280> a 00:11:47.300 --> 00:11:47.310 align:start position:0% through github issues trying to get a 00:11:47.310 --> 00:11:49.610 align:start position:0% through github issues trying to get a grasp<00:11:47.550> if<00:11:47.850> like<00:11:48.030> this<00:11:48.180> is<00:11:48.300> viable<00:11:48.510> or<00:11:48.780> not<00:11:48.870> so 00:11:49.610 --> 00:11:49.620 align:start position:0% grasp if like this is viable or not so 00:11:49.620 --> 00:11:51.470 align:start position:0% grasp if like this is viable or not so we<00:11:49.710> started<00:11:49.980> asking<00:11:50.220> ourselves<00:11:50.310> who<00:11:51.240> is 00:11:51.470 --> 00:11:51.480 align:start position:0% we started asking ourselves who is 00:11:51.480 --> 00:11:53.870 align:start position:0% we started asking ourselves who is working<00:11:51.720> on<00:11:51.930> this<00:11:52.110> who<00:11:52.620> wants<00:11:52.860> to<00:11:53.100> work<00:11:53.700> on 00:11:53.870 --> 00:11:53.880 align:start position:0% working on this who wants to work on 00:11:53.880 --> 00:11:55.100 align:start position:0% working on this who wants to work on this<00:11:54.060> and<00:11:54.330> just<00:11:54.570> join<00:11:54.780> us<00:11:54.930> on<00:11:55.020> an 00:11:55.100 --> 00:11:55.110 align:start position:0% this and just join us on an 00:11:55.110 --> 00:11:56.810 align:start position:0% this and just join us on an implementation<00:11:55.620> effort<00:11:55.860> so<00:11:56.490> we<00:11:56.580> put<00:11:56.730> together 00:11:56.810 --> 00:11:56.820 align:start position:0% implementation effort so we put together 00:11:56.820 --> 00:11:59.120 align:start position:0% implementation effort so we put together a<00:11:57.060> call<00:11:57.300> on<00:11:57.510> reddit<00:11:57.810> and<00:11:58.410> our<00:11:58.800> whole<00:11:58.980> team 00:11:59.120 --> 00:11:59.130 align:start position:0% a call on reddit and our whole team 00:11:59.130 --> 00:12:00.290 align:start position:0% a call on reddit and our whole team assembled<00:11:59.580> organically<00:12:00.000> through<00:12:00.120> the 00:12:00.290 --> 00:12:00.300 align:start position:0% assembled organically through the 00:12:00.300 --> 00:12:02.900 align:start position:0% assembled organically through the internet<00:12:00.630> and<00:12:00.810> actually<00:12:01.440> this<00:12:01.740> Def<00:12:01.980> Con<00:12:02.190> marks 00:12:02.900 --> 00:12:02.910 align:start position:0% internet and actually this Def Con marks 00:12:02.910 --> 00:12:04.280 align:start position:0% internet and actually this Def Con marks the<00:12:03.030> first<00:12:03.180> time<00:12:03.330> all<00:12:03.600> of<00:12:03.630> us<00:12:03.810> actually<00:12:04.140> meet 00:12:04.280 --> 00:12:04.290 align:start position:0% the first time all of us actually meet 00:12:04.290 --> 00:12:06.320 align:start position:0% the first time all of us actually meet in<00:12:04.410> person<00:12:04.590> so<00:12:05.580> it's<00:12:05.910> been<00:12:06.030> an<00:12:06.120> amazing 00:12:06.320 --> 00:12:06.330 align:start position:0% in person so it's been an amazing 00:12:06.330 --> 00:12:13.550 align:start position:0% in person so it's been an amazing amazing<00:12:07.020> time<00:12:07.230> yeah<00:12:08.220> so<00:12:12.140> what<00:12:13.140> does<00:12:13.260> it<00:12:13.410> mean 00:12:13.550 --> 00:12:13.560 align:start position:0% amazing time yeah so what does it mean 00:12:13.560 --> 00:12:16.790 align:start position:0% amazing time yeah so what does it mean to<00:12:13.860> work<00:12:14.070> on<00:12:14.340> earth<00:12:14.550> 2.0<00:12:15.170> working<00:12:16.170> on<00:12:16.290> s<00:12:16.380> 2.0 00:12:16.790 --> 00:12:16.800 align:start position:0% to work on earth 2.0 working on s 2.0 00:12:16.800 --> 00:12:18.620 align:start position:0% to work on earth 2.0 working on s 2.0 means<00:12:17.070> at<00:12:17.430> a<00:12:17.460> very<00:12:17.700> high<00:12:17.790> level<00:12:17.970> operating 00:12:18.620 --> 00:12:18.630 align:start position:0% means at a very high level operating 00:12:18.630 --> 00:12:21.020 align:start position:0% means at a very high level operating under<00:12:18.900> constraints<00:12:19.440> and<00:12:19.790> we<00:12:20.790> have<00:12:20.910> to 00:12:21.020 --> 00:12:21.030 align:start position:0% under constraints and we have to 00:12:21.030 --> 00:12:22.460 align:start position:0% under constraints and we have to understand<00:12:21.540> that<00:12:21.690> we<00:12:21.810> have<00:12:21.840> a<00:12:21.990> currently 00:12:22.460 --> 00:12:22.470 align:start position:0% understand that we have a currently 00:12:22.470 --> 00:12:24.620 align:start position:0% understand that we have a currently functioning<00:12:22.710> you<00:12:23.430> know<00:12:23.580> maintained<00:12:24.180> client 00:12:24.620 --> 00:12:24.630 align:start position:0% functioning you know maintained client 00:12:24.630 --> 00:12:25.910 align:start position:0% functioning you know maintained client that<00:12:24.840> runs<00:12:25.050> a<00:12:25.170> proof-of-work<00:12:25.440> chain<00:12:25.770> right 00:12:25.910 --> 00:12:25.920 align:start position:0% that runs a proof-of-work chain right 00:12:25.920 --> 00:12:27.680 align:start position:0% that runs a proof-of-work chain right now<00:12:26.100> where<00:12:26.790> there<00:12:26.940> are<00:12:27.030> real<00:12:27.210> people<00:12:27.600> with 00:12:27.680 --> 00:12:27.690 align:start position:0% now where there are real people with 00:12:27.690 --> 00:12:30.590 align:start position:0% now where there are real people with invested<00:12:28.170> at<00:12:28.350> applications<00:12:29.120> bid<00:12:30.120> alerts<00:12:30.420> as 00:12:30.590 --> 00:12:30.600 align:start position:0% invested at applications bid alerts as 00:12:30.600 --> 00:12:33.410 align:start position:0% invested at applications bid alerts as we've<00:12:30.750> seen<00:12:31.040> and<00:12:32.040> a<00:12:32.430> lot<00:12:32.580> of<00:12:32.700> a<00:12:32.910> lot<00:12:33.270> of 00:12:33.410 --> 00:12:33.420 align:start position:0% we've seen and a lot of a lot of 00:12:33.420 --> 00:12:34.850 align:start position:0% we've seen and a lot of a lot of initiatives<00:12:33.960> to<00:12:34.020> kind<00:12:34.260> of<00:12:34.350> keep<00:12:34.470> this<00:12:34.620> going 00:12:34.850 --> 00:12:34.860 align:start position:0% initiatives to kind of keep this going 00:12:34.860 --> 00:12:37.490 align:start position:0% initiatives to kind of keep this going and<00:12:35.220> make<00:12:35.790> it<00:12:36.000> into<00:12:36.420> you<00:12:37.020> know<00:12:37.050> make<00:12:37.290> it<00:12:37.320> as 00:12:37.490 --> 00:12:37.500 align:start position:0% and make it into you know make it as 00:12:37.500 --> 00:12:39.080 align:start position:0% and make it into you know make it as robust<00:12:37.830> as<00:12:37.950> possible<00:12:38.040> so<00:12:38.550> we<00:12:38.640> can<00:12:38.760> get<00:12:38.880> to<00:12:39.060> our 00:12:39.080 --> 00:12:39.090 align:start position:0% robust as possible so we can get to our 00:12:39.090 --> 00:12:41.240 align:start position:0% robust as possible so we can get to our goal<00:12:39.390> of<00:12:39.420> achieving<00:12:39.630> a<00:12:39.930> world<00:12:40.110> computer<00:12:40.530> the 00:12:41.240 --> 00:12:41.250 align:start position:0% goal of achieving a world computer the 00:12:41.250 --> 00:12:43.940 align:start position:0% goal of achieving a world computer the problem<00:12:41.580> is<00:12:41.700> that<00:12:42.230> when<00:12:43.230> upgrading<00:12:43.560> the 00:12:43.940 --> 00:12:43.950 align:start position:0% problem is that when upgrading the 00:12:43.950 --> 00:12:46.100 align:start position:0% problem is that when upgrading the system<00:12:44.370> this<00:12:44.910> isn't<00:12:45.240> exactly<00:12:45.330> going<00:12:45.840> to<00:12:45.930> be<00:12:46.080> a 00:12:46.100 --> 00:12:46.110 align:start position:0% system this isn't exactly going to be a 00:12:46.110 --> 00:12:48.350 align:start position:0% system this isn't exactly going to be a hard<00:12:46.410> fork<00:12:46.710> so<00:12:47.610> what<00:12:47.700> this<00:12:47.790> means<00:12:47.850> is<00:12:48.210> that<00:12:48.240> a 00:12:48.350 --> 00:12:48.360 align:start position:0% hard fork so what this means is that a 00:12:48.360 --> 00:12:50.000 align:start position:0% hard fork so what this means is that a theorem<00:12:48.630> 2.0<00:12:48.990> shall<00:12:49.260> we<00:12:49.350> explain<00:12:49.650> it's<00:12:49.890> going 00:12:50.000 --> 00:12:50.010 align:start position:0% theorem 2.0 shall we explain it's going 00:12:50.010 --> 00:12:51.920 align:start position:0% theorem 2.0 shall we explain it's going to<00:12:50.070> be<00:12:50.190> a<00:12:50.220> side<00:12:50.520> chain<00:12:50.850> of<00:12:51.210> sorts<00:12:51.630> is<00:12:51.720> going<00:12:51.870> to 00:12:51.920 --> 00:12:51.930 align:start position:0% to be a side chain of sorts is going to 00:12:51.930 --> 00:12:54.140 align:start position:0% to be a side chain of sorts is going to be<00:12:52.020> basically<00:12:52.290> a<00:12:52.410> parallel<00:12:52.860> chain<00:12:53.100> that<00:12:54.030> is 00:12:54.140 --> 00:12:54.150 align:start position:0% be basically a parallel chain that is 00:12:54.150 --> 00:12:55.730 align:start position:0% be basically a parallel chain that is then<00:12:54.300> pegged<00:12:54.600> to<00:12:54.690> the<00:12:54.750> proof<00:12:55.020> work<00:12:55.260> chain<00:12:55.470> as<00:12:55.680> a 00:12:55.730 --> 00:12:55.740 align:start position:0% then pegged to the proof work chain as a 00:12:55.740 --> 00:12:58.370 align:start position:0% then pegged to the proof work chain as a way<00:12:56.010> to<00:12:56.070> create<00:12:56.520> a<00:12:56.610> full<00:12:56.910> Kaspar<00:12:57.450> FFG<00:12:57.930> enabled 00:12:58.370 --> 00:12:58.380 align:start position:0% way to create a full Kaspar FFG enabled 00:12:58.380 --> 00:13:01.460 align:start position:0% way to create a full Kaspar FFG enabled proof<00:12:58.950> stake<00:12:59.220> chain<00:12:59.490> and<00:13:00.210> what<00:13:00.900> this<00:13:01.050> means<00:13:01.230> is 00:13:01.460 --> 00:13:01.470 align:start position:0% proof stake chain and what this means is 00:13:01.470 --> 00:13:02.750 align:start position:0% proof stake chain and what this means is that<00:13:01.500> we<00:13:01.680> must<00:13:01.860> have<00:13:01.920> to<00:13:02.280> be<00:13:02.370> very<00:13:02.610> very 00:13:02.750 --> 00:13:02.760 align:start position:0% that we must have to be very very 00:13:02.760 --> 00:13:05.080 align:start position:0% that we must have to be very very careful<00:13:03.240> with<00:13:03.480> our<00:13:03.750> crypto<00:13:04.140> economic<00:13:04.560> design 00:13:05.080 --> 00:13:05.090 align:start position:0% careful with our crypto economic design 00:13:05.090 --> 00:13:07.970 align:start position:0% careful with our crypto economic design how<00:13:06.090> we<00:13:06.150> are<00:13:06.540> more<00:13:06.840> people<00:13:07.170> into<00:13:07.410> the<00:13:07.530> system 00:13:07.970 --> 00:13:07.980 align:start position:0% how we are more people into the system 00:13:07.980 --> 00:13:10.430 align:start position:0% how we are more people into the system and<00:13:08.270> how<00:13:09.270> we<00:13:09.300> can<00:13:09.510> get<00:13:09.720> the<00:13:09.870> same<00:13:10.050> level<00:13:10.380> of 00:13:10.430 --> 00:13:10.440 align:start position:0% and how we can get the same level of 00:13:10.440 --> 00:13:14.300 align:start position:0% and how we can get the same level of scale<00:13:10.770> of<00:13:11.610> usability<00:13:12.590> and<00:13:13.590> a<00:13:13.890> much<00:13:14.100> much 00:13:14.300 --> 00:13:14.310 align:start position:0% scale of usability and a much much 00:13:14.310 --> 00:13:18.260 align:start position:0% scale of usability and a much much larger<00:13:14.700> level<00:13:14.730> of<00:13:15.120> throughput<00:13:16.430> so<00:13:17.430> what<00:13:18.000> is 00:13:18.260 --> 00:13:18.270 align:start position:0% larger level of throughput so what is 00:13:18.270 --> 00:13:21.560 align:start position:0% larger level of throughput so what is the<00:13:18.600> road<00:13:18.840> so<00:13:19.200> far<00:13:19.520> ever<00:13:20.520> since<00:13:20.880> we<00:13:21.030> started<00:13:21.090> in 00:13:21.560 --> 00:13:21.570 align:start position:0% the road so far ever since we started in 00:13:21.570 --> 00:13:23.850 align:start position:0% the road so far ever since we started in around<00:13:21.810> January<00:13:22.200> of<00:13:22.320> 20 00:13:23.850 --> 00:13:23.860 align:start position:0% around January of 20 00:13:23.860 --> 00:13:25.139 align:start position:0% around January of 20 we<00:13:24.040> initially<00:13:24.399> started<00:13:24.639> doing<00:13:24.670> a<00:13:24.879> biweekly 00:13:25.139 --> 00:13:25.149 align:start position:0% we initially started doing a biweekly 00:13:25.149 --> 00:13:26.699 align:start position:0% we initially started doing a biweekly development<00:13:25.720> update<00:13:25.810> we<00:13:26.139> wanted<00:13:26.379> to<00:13:26.440> be<00:13:26.560> as 00:13:26.699 --> 00:13:26.709 align:start position:0% development update we wanted to be as 00:13:26.709 --> 00:13:28.139 align:start position:0% development update we wanted to be as transparent<00:13:26.949> as<00:13:27.339> possible<00:13:27.399> about<00:13:27.819> these 00:13:28.139 --> 00:13:28.149 align:start position:0% transparent as possible about these 00:13:28.149 --> 00:13:30.240 align:start position:0% transparent as possible about these efforts<00:13:28.329> we<00:13:28.930> understand<00:13:29.410> that<00:13:29.680> given<00:13:30.129> the 00:13:30.240 --> 00:13:30.250 align:start position:0% efforts we understand that given the 00:13:30.250 --> 00:13:33.030 align:start position:0% efforts we understand that given the spec<00:13:30.550> is<00:13:30.730> so<00:13:30.940> kind<00:13:31.389> of<00:13:31.509> young<00:13:31.750> we<00:13:32.649> need<00:13:32.800> as<00:13:32.920> much 00:13:33.030 --> 00:13:33.040 align:start position:0% spec is so kind of young we need as much 00:13:33.040 --> 00:13:34.650 align:start position:0% spec is so kind of young we need as much discussion<00:13:33.459> around<00:13:33.759> some<00:13:34.029> of<00:13:34.060> these<00:13:34.180> problems 00:13:34.650 --> 00:13:34.660 align:start position:0% discussion around some of these problems 00:13:34.660 --> 00:13:36.180 align:start position:0% discussion around some of these problems we<00:13:34.779> need<00:13:34.870> people<00:13:35.170> criticizing<00:13:35.649> many<00:13:35.949> people 00:13:36.180 --> 00:13:36.190 align:start position:0% we need people criticizing many people 00:13:36.190 --> 00:13:37.530 align:start position:0% we need people criticizing many people coming<00:13:36.490> in<00:13:36.610> and<00:13:36.730> being<00:13:36.879> like<00:13:37.060> you<00:13:37.209> guys<00:13:37.360> should 00:13:37.530 --> 00:13:37.540 align:start position:0% coming in and being like you guys should 00:13:37.540 --> 00:13:39.269 align:start position:0% coming in and being like you guys should not<00:13:37.660> do<00:13:37.839> it<00:13:37.959> this<00:13:38.079> way<00:13:38.290> you<00:13:38.350> should<00:13:38.440> try<00:13:39.220> this 00:13:39.269 --> 00:13:39.279 align:start position:0% not do it this way you should try this 00:13:39.279 --> 00:13:41.790 align:start position:0% not do it this way you should try this way<00:13:39.579> instead<00:13:40.110> aside<00:13:41.110> from<00:13:41.199> that<00:13:41.259> we've<00:13:41.649> been 00:13:41.790 --> 00:13:41.800 align:start position:0% way instead aside from that we've been 00:13:41.800 --> 00:13:43.800 align:start position:0% way instead aside from that we've been big<00:13:42.100> fans<00:13:42.399> of<00:13:42.579> having<00:13:42.910> extensive<00:13:43.240> onboarding 00:13:43.800 --> 00:13:43.810 align:start position:0% big fans of having extensive onboarding 00:13:43.810 --> 00:13:45.840 align:start position:0% big fans of having extensive onboarding documentation<00:13:44.529> so<00:13:45.279> we've<00:13:45.459> been<00:13:45.579> able<00:13:45.699> to 00:13:45.840 --> 00:13:45.850 align:start position:0% documentation so we've been able to 00:13:45.850 --> 00:13:47.699 align:start position:0% documentation so we've been able to onboard<00:13:46.329> a<00:13:46.389> lot<00:13:46.540> of<00:13:46.629> contributors<00:13:47.170> that<00:13:47.439> have 00:13:47.699 --> 00:13:47.709 align:start position:0% onboard a lot of contributors that have 00:13:47.709 --> 00:13:49.379 align:start position:0% onboard a lot of contributors that have not<00:13:47.889> been<00:13:48.100> as<00:13:48.279> familiar<00:13:48.610> with<00:13:48.639> aetherium<00:13:48.939> 2.0 00:13:49.379 --> 00:13:49.389 align:start position:0% not been as familiar with aetherium 2.0 00:13:49.389 --> 00:13:51.269 align:start position:0% not been as familiar with aetherium 2.0 to<00:13:49.629> be<00:13:49.689> able<00:13:49.839> to<00:13:49.899> come<00:13:50.050> in<00:13:50.199> and<00:13:50.350> just<00:13:50.560> build<00:13:51.129> out 00:13:51.269 --> 00:13:51.279 align:start position:0% to be able to come in and just build out 00:13:51.279 --> 00:13:53.309 align:start position:0% to be able to come in and just build out parts<00:13:51.879> of<00:13:51.939> our<00:13:52.029> implementation<00:13:52.540> we've<00:13:53.199> been 00:13:53.309 --> 00:13:53.319 align:start position:0% parts of our implementation we've been 00:13:53.319 --> 00:13:54.929 align:start position:0% parts of our implementation we've been leveraging<00:13:53.680> get<00:13:53.860> coined<00:13:54.069> extensively<00:13:54.610> so 00:13:54.929 --> 00:13:54.939 align:start position:0% leveraging get coined extensively so 00:13:54.939 --> 00:13:57.689 align:start position:0% leveraging get coined extensively so thank<00:13:55.209> you<00:13:55.329> very<00:13:55.360> amazing<00:13:56.199> tool<00:13:56.500> it's<00:13:57.250> a<00:13:57.370> it's 00:13:57.689 --> 00:13:57.699 align:start position:0% thank you very amazing tool it's a it's 00:13:57.699 --> 00:13:59.100 align:start position:0% thank you very amazing tool it's a it's an<00:13:57.790> incredible<00:13:58.180> tool<00:13:58.389> every<00:13:58.720> time<00:13:58.870> I<00:13:58.930> make<00:13:59.079> a 00:13:59.100 --> 00:13:59.110 align:start position:0% an incredible tool every time I make a 00:13:59.110 --> 00:14:01.319 align:start position:0% an incredible tool every time I make a bounty<00:13:59.470> we<00:14:00.040> get<00:14:00.189> tons<00:14:00.430> of<00:14:00.519> people<00:14:00.670> just<00:14:01.000> coming 00:14:01.319 --> 00:14:01.329 align:start position:0% bounty we get tons of people just coming 00:14:01.329 --> 00:14:03.660 align:start position:0% bounty we get tons of people just coming in<00:14:01.480> and<00:14:01.509> flocking<00:14:01.990> to<00:14:02.139> it<00:14:02.189> and<00:14:03.189> it's<00:14:03.370> just<00:14:03.430> been 00:14:03.660 --> 00:14:03.670 align:start position:0% in and flocking to it and it's just been 00:14:03.670 --> 00:14:05.040 align:start position:0% in and flocking to it and it's just been a<00:14:03.699> great<00:14:03.879> experience<00:14:04.060> just<00:14:04.629> onboarding 00:14:05.040 --> 00:14:05.050 align:start position:0% a great experience just onboarding 00:14:05.050 --> 00:14:06.480 align:start position:0% a great experience just onboarding people<00:14:05.350> into<00:14:05.560> the<00:14:05.649> community<00:14:05.769> I<00:14:06.129> think<00:14:06.339> that's 00:14:06.480 --> 00:14:06.490 align:start position:0% people into the community I think that's 00:14:06.490 --> 00:14:08.490 align:start position:0% people into the community I think that's that's<00:14:06.850> the<00:14:07.060> way<00:14:07.149> to<00:14:07.209> go<00:14:07.449> aside<00:14:08.319> from<00:14:08.439> that 00:14:08.490 --> 00:14:08.500 align:start position:0% that's the way to go aside from that 00:14:08.500 --> 00:14:09.900 align:start position:0% that's the way to go aside from that we've<00:14:08.889> also<00:14:09.069> been<00:14:09.279> doing<00:14:09.399> bi-weekly 00:14:09.900 --> 00:14:09.910 align:start position:0% we've also been doing bi-weekly 00:14:09.910 --> 00:14:11.340 align:start position:0% we've also been doing bi-weekly development<00:14:10.449> updates<00:14:10.720> so<00:14:11.050> we've<00:14:11.259> been 00:14:11.340 --> 00:14:11.350 align:start position:0% development updates so we've been 00:14:11.350 --> 00:14:13.079 align:start position:0% development updates so we've been frequently<00:14:11.800> posting<00:14:12.250> about<00:14:12.519> everything<00:14:13.000> we 00:14:13.079 --> 00:14:13.089 align:start position:0% frequently posting about everything we 00:14:13.089 --> 00:14:15.420 align:start position:0% frequently posting about everything we do<00:14:13.209> and<00:14:13.449> on<00:14:14.110> October<00:14:14.620> 3rd<00:14:14.829> we<00:14:14.980> released<00:14:15.279> our 00:14:15.420 --> 00:14:15.430 align:start position:0% do and on October 3rd we released our 00:14:15.430 --> 00:14:17.850 align:start position:0% do and on October 3rd we released our very<00:14:15.610> first<00:14:15.910> POC<00:14:16.660> of<00:14:16.870> the<00:14:17.290> current<00:14:17.589> beacon 00:14:17.850 --> 00:14:17.860 align:start position:0% very first POC of the current beacon 00:14:17.860 --> 00:14:27.749 align:start position:0% very first POC of the current beacon change<00:14:18.100> as<00:14:18.370> per<00:14:18.579> spec<00:14:19.290> and<00:14:20.290> yeah<00:14:26.130> so<00:14:27.130> what<00:14:27.639> does 00:14:27.749 --> 00:14:27.759 align:start position:0% change as per spec and yeah so what does 00:14:27.759 --> 00:14:29.819 align:start position:0% change as per spec and yeah so what does it<00:14:27.850> mean<00:14:28.000> to<00:14:28.269> create<00:14:28.480> an<00:14:29.019> entirely<00:14:29.319> new<00:14:29.470> system 00:14:29.819 --> 00:14:29.829 align:start position:0% it mean to create an entirely new system 00:14:29.829 --> 00:14:31.530 align:start position:0% it mean to create an entirely new system it<00:14:29.980> means<00:14:30.069> that<00:14:30.279> we<00:14:30.370> have<00:14:30.399> the<00:14:30.850> opportunity<00:14:31.449> to 00:14:31.530 --> 00:14:31.540 align:start position:0% it means that we have the opportunity to 00:14:31.540 --> 00:14:33.059 align:start position:0% it means that we have the opportunity to make<00:14:31.660> better<00:14:32.050> and<00:14:32.139> more<00:14:32.319> robust<00:14:32.740> design 00:14:33.059 --> 00:14:33.069 align:start position:0% make better and more robust design 00:14:33.069 --> 00:14:35.340 align:start position:0% make better and more robust design choices<00:14:33.310> so<00:14:34.269> in<00:14:34.420> that<00:14:34.509> sense<00:14:34.810> you<00:14:35.019> know<00:14:35.139> we've 00:14:35.340 --> 00:14:35.350 align:start position:0% choices so in that sense you know we've 00:14:35.350 --> 00:14:38.189 align:start position:0% choices so in that sense you know we've been<00:14:35.529> like<00:14:36.370> aetherium<00:14:36.850> as<00:14:37.089> kind<00:14:37.810> of<00:14:37.839> italic 00:14:38.189 --> 00:14:38.199 align:start position:0% been like aetherium as kind of italic 00:14:38.199 --> 00:14:40.290 align:start position:0% been like aetherium as kind of italic puts<00:14:38.380> it<00:14:38.529> was<00:14:38.680> kind<00:14:38.920> of<00:14:39.009> a<00:14:39.100> scrappy<00:14:39.459> attempt<00:14:39.880> to 00:14:40.290 --> 00:14:40.300 align:start position:0% puts it was kind of a scrappy attempt to 00:14:40.300 --> 00:14:42.090 align:start position:0% puts it was kind of a scrappy attempt to build<00:14:40.449> a<00:14:40.600> work<00:14:40.750> on<00:14:40.930> the<00:14:40.959> world<00:14:41.259> computer<00:14:41.560> and<00:14:41.889> f 00:14:42.090 --> 00:14:42.100 align:start position:0% build a work on the world computer and f 00:14:42.100 --> 00:14:44.069 align:start position:0% build a work on the world computer and f 2.0<00:14:42.550> will<00:14:42.730> actually<00:14:43.149> be<00:14:43.300> the<00:14:43.449> world<00:14:43.630> computer 00:14:44.069 --> 00:14:44.079 align:start position:0% 2.0 will actually be the world computer 00:14:44.079 --> 00:14:46.290 align:start position:0% 2.0 will actually be the world computer so<00:14:44.769> under<00:14:45.220> this<00:14:45.370> set<00:14:45.670> of<00:14:45.759> constraints<00:14:46.060> we<00:14:46.269> have 00:14:46.290 --> 00:14:46.300 align:start position:0% so under this set of constraints we have 00:14:46.300 --> 00:14:48.449 align:start position:0% so under this set of constraints we have to<00:14:46.449> consider<00:14:46.750> you<00:14:47.230> know<00:14:47.259> how<00:14:47.889> will<00:14:48.339> the 00:14:48.449 --> 00:14:48.459 align:start position:0% to consider you know how will the 00:14:48.459 --> 00:14:50.370 align:start position:0% to consider you know how will the underlying<00:14:48.970> tech<00:14:49.509> stack<00:14:49.720> improve<00:14:50.259> this 00:14:50.370 --> 00:14:50.380 align:start position:0% underlying tech stack improve this 00:14:50.380 --> 00:14:52.019 align:start position:0% underlying tech stack improve this efficiency<00:14:50.800> and<00:14:51.100> reduce<00:14:51.370> as<00:14:51.519> much<00:14:51.550> overhead 00:14:52.019 --> 00:14:52.029 align:start position:0% efficiency and reduce as much overhead 00:14:52.029 --> 00:14:54.240 align:start position:0% efficiency and reduce as much overhead as<00:14:52.269> possible<00:14:52.810> so<00:14:53.290> we<00:14:53.470> can<00:14:53.620> maximize<00:14:53.800> the 00:14:54.240 --> 00:14:54.250 align:start position:0% as possible so we can maximize the 00:14:54.250 --> 00:14:55.259 align:start position:0% as possible so we can maximize the throughput<00:14:54.399> that<00:14:54.639> we<00:14:54.730> get<00:14:54.850> from<00:14:54.970> the<00:14:55.089> system 00:14:55.259 --> 00:14:55.269 align:start position:0% throughput that we get from the system 00:14:55.269 --> 00:14:57.389 align:start position:0% throughput that we get from the system as<00:14:55.689> well<00:14:55.870> as<00:14:55.990> the<00:14:56.079> usability<00:14:56.410> so<00:14:57.250> one<00:14:57.370> of 00:14:57.389 --> 00:14:57.399 align:start position:0% as well as the usability so one of 00:14:57.399 --> 00:14:58.949 align:start position:0% as well as the usability so one of things<00:14:57.519> that<00:14:57.699> we've<00:14:57.790> been<00:14:57.880> using<00:14:58.120> is<00:14:58.480> there's 00:14:58.949 --> 00:14:58.959 align:start position:0% things that we've been using is there's 00:14:58.959 --> 00:15:00.569 align:start position:0% things that we've been using is there's a<00:14:59.019> lot<00:14:59.139> of<00:14:59.259> kind<00:14:59.649> of<00:14:59.800> a<00:14:59.920> lot<00:15:00.040> of<00:15:00.069> discussions 00:15:00.569 --> 00:15:00.579 align:start position:0% a lot of kind of a lot of discussions 00:15:00.579 --> 00:15:02.280 align:start position:0% a lot of kind of a lot of discussions around<00:15:00.730> all<00:15:00.939> the<00:15:01.060> ES<00:15:01.180> 2.0<00:15:01.600> teams<00:15:01.810> using<00:15:02.050> Lib 00:15:02.280 --> 00:15:02.290 align:start position:0% around all the ES 2.0 teams using Lib 00:15:02.290 --> 00:15:04.439 align:start position:0% around all the ES 2.0 teams using Lib PDP<00:15:02.740> which<00:15:03.339> is<00:15:03.459> a<00:15:03.490> very<00:15:03.730> popular<00:15:03.970> networking 00:15:04.439 --> 00:15:04.449 align:start position:0% PDP which is a very popular networking 00:15:04.449 --> 00:15:06.110 align:start position:0% PDP which is a very popular networking library<00:15:04.689> maintained<00:15:05.170> by<00:15:05.290> protocol<00:15:05.680> labs 00:15:06.110 --> 00:15:06.120 align:start position:0% library maintained by protocol labs 00:15:06.120 --> 00:15:08.069 align:start position:0% library maintained by protocol labs aside<00:15:07.120> from<00:15:07.209> that<00:15:07.300> we've<00:15:07.899> been<00:15:08.019> using 00:15:08.069 --> 00:15:08.079 align:start position:0% aside from that we've been using 00:15:08.079 --> 00:15:10.499 align:start position:0% aside from that we've been using Google's<00:15:08.680> popular<00:15:09.130> G<00:15:09.430> RPC<00:15:09.819> framework<00:15:10.209> for<00:15:10.480> a 00:15:10.499 --> 00:15:10.509 align:start position:0% Google's popular G RPC framework for a 00:15:10.509 --> 00:15:12.629 align:start position:0% Google's popular G RPC framework for a communication<00:15:10.930> between<00:15:11.230> processes<00:15:11.800> so<00:15:12.550> we 00:15:12.629 --> 00:15:12.639 align:start position:0% communication between processes so we 00:15:12.639 --> 00:15:14.309 align:start position:0% communication between processes so we want<00:15:12.790> the<00:15:12.880> friction<00:15:13.089> to<00:15:13.420> be<00:15:13.540> as<00:15:13.809> little<00:15:14.199> as 00:15:14.309 --> 00:15:14.319 align:start position:0% want the friction to be as little as 00:15:14.319 --> 00:15:16.379 align:start position:0% want the friction to be as little as possible<00:15:14.500> we<00:15:14.889> want<00:15:15.040> nodes<00:15:15.399> to<00:15:15.670> be<00:15:15.699> able<00:15:15.850> to 00:15:16.379 --> 00:15:16.389 align:start position:0% possible we want nodes to be able to 00:15:16.389 --> 00:15:18.269 align:start position:0% possible we want nodes to be able to just<00:15:16.569> work<00:15:16.779> you<00:15:17.170> can<00:15:17.319> spin<00:15:17.559> up<00:15:17.680> a<00:15:17.769> node<00:15:17.949> you<00:15:18.220> can 00:15:18.269 --> 00:15:18.279 align:start position:0% just work you can spin up a node you can 00:15:18.279 --> 00:15:19.679 align:start position:0% just work you can spin up a node you can communicate<00:15:18.819> you<00:15:18.910> can<00:15:19.059> run<00:15:19.180> a<00:15:19.209> validator 00:15:19.679 --> 00:15:19.689 align:start position:0% communicate you can run a validator 00:15:19.689 --> 00:15:21.299 align:start position:0% communicate you can run a validator client<00:15:20.079> you<00:15:20.410> don't<00:15:20.559> need<00:15:20.649> to<00:15:20.740> think<00:15:20.860> about<00:15:21.009> it 00:15:21.299 --> 00:15:21.309 align:start position:0% client you don't need to think about it 00:15:21.309 --> 00:15:23.759 align:start position:0% client you don't need to think about it and<00:15:21.459> in<00:15:22.389> our<00:15:22.540> eyes<00:15:22.809> what<00:15:23.410> we<00:15:23.529> see<00:15:23.740> a 00:15:23.759 --> 00:15:23.769 align:start position:0% and in our eyes what we see a 00:15:23.769 --> 00:15:25.920 align:start position:0% and in our eyes what we see a scalability<00:15:24.459> of<00:15:24.490> a<00:15:24.639> blockchain<00:15:24.850> is<00:15:25.240> truly 00:15:25.920 --> 00:15:25.930 align:start position:0% scalability of a blockchain is truly 00:15:25.930 --> 00:15:27.929 align:start position:0% scalability of a blockchain is truly having<00:15:26.230> a<00:15:26.350> base<00:15:26.559> layer<00:15:26.769> that<00:15:27.519> does<00:15:27.730> this<00:15:27.879> job 00:15:27.929 --> 00:15:27.939 align:start position:0% having a base layer that does this job 00:15:27.939 --> 00:15:29.819 align:start position:0% having a base layer that does this job good<00:15:28.389> enough<00:15:28.689> so<00:15:29.019> the<00:15:29.110> applications<00:15:29.649> don't 00:15:29.819 --> 00:15:29.829 align:start position:0% good enough so the applications don't 00:15:29.829 --> 00:15:33.840 align:start position:0% good enough so the applications don't even<00:15:30.069> need<00:15:30.129> to<00:15:30.279> consider<00:15:30.610> it<00:15:32.670> aside<00:15:33.670> from<00:15:33.790> that 00:15:33.840 --> 00:15:33.850 align:start position:0% even need to consider it aside from that 00:15:33.850 --> 00:15:36.269 align:start position:0% even need to consider it aside from that we<00:15:34.329> picked<00:15:34.600> go<00:15:34.809> as<00:15:35.079> our<00:15:35.319> tool 00:15:36.269 --> 00:15:36.279 align:start position:0% we picked go as our tool 00:15:36.279 --> 00:15:38.309 align:start position:0% we picked go as our tool go<00:15:36.490> is<00:15:36.639> an<00:15:36.759> incredible<00:15:37.300> language<00:15:38.050> for 00:15:38.309 --> 00:15:38.319 align:start position:0% go is an incredible language for 00:15:38.319 --> 00:15:39.749 align:start position:0% go is an incredible language for blockchains<00:15:38.800> in<00:15:38.949> particular<00:15:39.399> where<00:15:39.579> you<00:15:39.639> have 00:15:39.749 --> 00:15:39.759 align:start position:0% blockchains in particular where you have 00:15:39.759 --> 00:15:41.400 align:start position:0% blockchains in particular where you have so<00:15:39.970> many<00:15:40.060> concurrent<00:15:40.629> processes 00:15:41.400 --> 00:15:41.410 align:start position:0% so many concurrent processes 00:15:41.410 --> 00:15:44.189 align:start position:0% so many concurrent processes it's<00:15:41.949> very<00:15:42.279> concise<00:15:42.790> and<00:15:43.149> what's<00:15:44.050> really 00:15:44.189 --> 00:15:44.199 align:start position:0% it's very concise and what's really 00:15:44.199 --> 00:15:45.480 align:start position:0% it's very concise and what's really great<00:15:44.410> about<00:15:44.470> go<00:15:44.800> is<00:15:44.949> that<00:15:45.129> you<00:15:45.249> know<00:15:45.339> we're 00:15:45.480 --> 00:15:45.490 align:start position:0% great about go is that you know we're 00:15:45.490 --> 00:15:47.069 align:start position:0% great about go is that you know we're collaborating<00:15:45.939> as<00:15:46.060> a<00:15:46.089> team<00:15:46.360> it<00:15:46.629> feels<00:15:46.959> like 00:15:47.069 --> 00:15:47.079 align:start position:0% collaborating as a team it feels like 00:15:47.079 --> 00:15:49.079 align:start position:0% collaborating as a team it feels like almost<00:15:47.350> every<00:15:47.709> file<00:15:47.980> has<00:15:48.579> been<00:15:48.610> written<00:15:48.970> by 00:15:49.079 --> 00:15:49.089 align:start position:0% almost every file has been written by 00:15:49.089 --> 00:15:50.579 align:start position:0% almost every file has been written by the<00:15:49.240> same<00:15:49.509> person<00:15:49.810> or<00:15:50.079> the<00:15:50.170> same<00:15:50.319> group<00:15:50.529> of 00:15:50.579 --> 00:15:50.589 align:start position:0% the same person or the same group of 00:15:50.589 --> 00:15:52.110 align:start position:0% the same person or the same group of people<00:15:50.649> because<00:15:51.129> it's<00:15:51.279> so<00:15:51.339> strict<00:15:51.759> and<00:15:51.879> how<00:15:51.970> it 00:15:52.110 --> 00:15:52.120 align:start position:0% people because it's so strict and how it 00:15:52.120 --> 00:15:54.299 align:start position:0% people because it's so strict and how it does<00:15:52.300> things<00:15:52.769> aside<00:15:53.769> from<00:15:53.860> that<00:15:54.009> it's<00:15:54.129> very 00:15:54.299 --> 00:15:54.309 align:start position:0% does things aside from that it's very 00:15:54.309 --> 00:15:56.400 align:start position:0% does things aside from that it's very batteries<00:15:54.759> included<00:15:55.240> so<00:15:55.420> it<00:15:55.569> prefers 00:15:56.400 --> 00:15:56.410 align:start position:0% batteries included so it prefers 00:15:56.410 --> 00:15:58.290 align:start position:0% batteries included so it prefers simplicity<00:15:57.009> over<00:15:57.220> magic<00:15:57.639> we<00:15:57.910> have<00:15:58.059> a<00:15:58.089> lot<00:15:58.269> of 00:15:58.290 --> 00:15:58.300 align:start position:0% simplicity over magic we have a lot of 00:15:58.300 --> 00:16:00.989 align:start position:0% simplicity over magic we have a lot of other<00:15:58.509> languages<00:15:58.899> that<00:15:59.709> just<00:16:00.220> seem<00:16:00.430> you<00:16:00.879> know 00:16:00.989 --> 00:16:00.999 align:start position:0% other languages that just seem you know 00:16:00.999 --> 00:16:02.610 align:start position:0% other languages that just seem you know like<00:16:01.180> they're<00:16:01.329> written<00:16:01.509> they're<00:16:01.959> coming<00:16:02.529> from 00:16:02.610 --> 00:16:02.620 align:start position:0% like they're written they're coming from 00:16:02.620 --> 00:16:05.309 align:start position:0% like they're written they're coming from some<00:16:02.860> arcane<00:16:03.220> alien<00:16:03.639> knowledge<00:16:04.079> and<00:16:05.079> there's 00:16:05.309 --> 00:16:05.319 align:start position:0% some arcane alien knowledge and there's 00:16:05.319 --> 00:16:07.379 align:start position:0% some arcane alien knowledge and there's a<00:16:05.410> lot<00:16:05.529> of<00:16:05.649> crazy<00:16:06.279> kind<00:16:06.759> of<00:16:06.790> constructs<00:16:07.240> in 00:16:07.379 --> 00:16:07.389 align:start position:0% a lot of crazy kind of constructs in 00:16:07.389 --> 00:16:07.739 align:start position:0% a lot of crazy kind of constructs in there 00:16:07.739 --> 00:16:07.749 align:start position:0% there 00:16:07.749 --> 00:16:09.629 align:start position:0% there however<00:16:08.199> with<00:16:08.410> go<00:16:08.620> we<00:16:08.980> have<00:16:09.129> the<00:16:09.249> simplicity 00:16:09.629 --> 00:16:09.639 align:start position:0% however with go we have the simplicity 00:16:09.639 --> 00:16:11.100 align:start position:0% however with go we have the simplicity that<00:16:10.029> everyone<00:16:10.509> that<00:16:10.569> wants<00:16:10.749> to<00:16:10.809> contribute 00:16:11.100 --> 00:16:11.110 align:start position:0% that everyone that wants to contribute 00:16:11.110 --> 00:16:13.350 align:start position:0% that everyone that wants to contribute to<00:16:11.350> a<00:16:11.379> blockchain<00:16:11.620> project<00:16:12.189> they<00:16:13.120> basically 00:16:13.350 --> 00:16:13.360 align:start position:0% to a blockchain project they basically 00:16:13.360 --> 00:16:14.850 align:start position:0% to a blockchain project they basically can<00:16:13.569> just<00:16:13.779> come<00:16:13.959> in<00:16:14.110> they'll<00:16:14.410> understand 00:16:14.850 --> 00:16:14.860 align:start position:0% can just come in they'll understand 00:16:14.860 --> 00:16:16.650 align:start position:0% can just come in they'll understand what's<00:16:15.040> going<00:16:15.279> on<00:16:15.399> in<00:16:15.579> the<00:16:15.670> code<00:16:15.879> all<00:16:16.360> they 00:16:16.650 --> 00:16:16.660 align:start position:0% what's going on in the code all they 00:16:16.660 --> 00:16:17.999 align:start position:0% what's going on in the code all they need<00:16:16.809> to<00:16:16.839> understand<00:16:17.319> is<00:16:17.499> to<00:16:17.529> read<00:16:17.740> more<00:16:17.889> about 00:16:17.999 --> 00:16:18.009 align:start position:0% need to understand is to read more about 00:16:18.009 --> 00:16:20.009 align:start position:0% need to understand is to read more about the<00:16:18.189> context<00:16:18.730> read<00:16:18.970> our<00:16:19.089> documentation<00:16:19.600> and 00:16:20.009 --> 00:16:20.019 align:start position:0% the context read our documentation and 00:16:20.019 --> 00:16:23.429 align:start position:0% the context read our documentation and we'll<00:16:20.290> always<00:16:20.529> gladly<00:16:20.829> onboard<00:16:21.370> them<00:16:21.899> so<00:16:22.899> we 00:16:23.429 --> 00:16:23.439 align:start position:0% we'll always gladly onboard them so we 00:16:23.439 --> 00:16:25.679 align:start position:0% we'll always gladly onboard them so we we<00:16:23.920> believe<00:16:24.189> in<00:16:24.279> the<00:16:24.370> power<00:16:24.550> of<00:16:24.670> Geth<00:16:25.029> gas<00:16:25.540> has 00:16:25.679 --> 00:16:25.689 align:start position:0% we believe in the power of Geth gas has 00:16:25.689 --> 00:16:27.449 align:start position:0% we believe in the power of Geth gas has been<00:16:25.809> is<00:16:26.050> an<00:16:26.499> incredible<00:16:26.860> project<00:16:27.040> it's<00:16:27.370> been 00:16:27.449 --> 00:16:27.459 align:start position:0% been is an incredible project it's been 00:16:27.459 --> 00:16:29.489 align:start position:0% been is an incredible project it's been battle<00:16:27.850> tested<00:16:27.879> it's<00:16:28.839> gone<00:16:29.019> through<00:16:29.139> a<00:16:29.230> lot<00:16:29.350> of 00:16:29.489 --> 00:16:29.499 align:start position:0% battle tested it's gone through a lot of 00:16:29.499 --> 00:16:31.710 align:start position:0% battle tested it's gone through a lot of upgrades<00:16:29.889> and<00:16:30.160> even<00:16:30.639> then<00:16:30.850> like<00:16:31.089> it<00:16:31.269> maintains 00:16:31.710 --> 00:16:31.720 align:start position:0% upgrades and even then like it maintains 00:16:31.720 --> 00:16:33.929 align:start position:0% upgrades and even then like it maintains you<00:16:32.199> know<00:16:32.319> the<00:16:32.499> robustness<00:16:33.160> and<00:16:33.249> flexibility 00:16:33.929 --> 00:16:33.939 align:start position:0% you know the robustness and flexibility 00:16:33.939 --> 00:16:38.489 align:start position:0% you know the robustness and flexibility of<00:16:33.999> a<00:16:34.300> language<00:16:34.629> as<00:16:34.779> greatest<00:16:35.139> go<00:16:36.509> so<00:16:37.509> exactly 00:16:38.489 --> 00:16:38.499 align:start position:0% of a language as greatest go so exactly 00:16:38.499 --> 00:16:40.949 align:start position:0% of a language as greatest go so exactly what<00:16:38.860> does<00:16:39.069> prism<00:16:39.550> encompass<00:16:40.209> as<00:16:40.420> a<00:16:40.480> client 00:16:40.949 --> 00:16:40.959 align:start position:0% what does prism encompass as a client 00:16:40.959 --> 00:16:43.860 align:start position:0% what does prism encompass as a client for<00:16:41.470> you<00:16:41.559> guys<00:16:41.850> we<00:16:42.850> are<00:16:43.089> careful<00:16:43.449> to<00:16:43.480> design 00:16:43.860 --> 00:16:43.870 align:start position:0% for you guys we are careful to design 00:16:43.870 --> 00:16:46.199 align:start position:0% for you guys we are careful to design this<00:16:44.079> knowing<00:16:44.620> that<00:16:45.040> a<00:16:45.279> lot<00:16:45.819> of<00:16:45.850> people<00:16:46.120> in 00:16:46.199 --> 00:16:46.209 align:start position:0% this knowing that a lot of people in 00:16:46.209 --> 00:16:47.579 align:start position:0% this knowing that a lot of people in this<00:16:46.329> room<00:16:46.540> will<00:16:46.750> probably<00:16:46.809> be<00:16:47.170> using<00:16:47.379> this 00:16:47.579 --> 00:16:47.589 align:start position:0% this room will probably be using this 00:16:47.589 --> 00:16:49.530 align:start position:0% this room will probably be using this client<00:16:47.980> as<00:16:48.069> a<00:16:48.129> theorem<00:16:48.490> 2.0<00:16:48.850> launches<00:16:49.240> and<00:16:49.449> we 00:16:49.530 --> 00:16:49.540 align:start position:0% client as a theorem 2.0 launches and we 00:16:49.540 --> 00:16:51.210 align:start position:0% client as a theorem 2.0 launches and we want<00:16:49.720> to<00:16:49.809> be<00:16:49.899> sure<00:16:50.110> a<00:16:50.559> great<00:16:50.829> developer 00:16:51.210 --> 00:16:51.220 align:start position:0% want to be sure a great developer 00:16:51.220 --> 00:16:53.160 align:start position:0% want to be sure a great developer experience<00:16:51.250> as<00:16:51.699> well<00:16:51.819> as<00:16:51.879> user<00:16:52.569> facing<00:16:53.050> piece 00:16:53.160 --> 00:16:53.170 align:start position:0% experience as well as user facing piece 00:16:53.170 --> 00:16:56.490 align:start position:0% experience as well as user facing piece of<00:16:53.319> software<00:16:53.620> so<00:16:54.839> if<00:16:55.839> you<00:16:55.990> guys<00:16:56.110> check<00:16:56.319> out<00:16:56.410> our 00:16:56.490 --> 00:16:56.500 align:start position:0% of software so if you guys check out our 00:16:56.500 --> 00:16:58.980 align:start position:0% of software so if you guys check out our repo<00:16:56.829> you<00:16:57.519> know<00:16:57.610> fully<00:16:57.850> open<00:16:58.180> always<00:16:58.600> welcome 00:16:58.980 --> 00:16:58.990 align:start position:0% repo you know fully open always welcome 00:16:58.990 --> 00:17:02.160 align:start position:0% repo you know fully open always welcome so<00:16:59.350> it's<00:16:59.620> prismatic<00:17:00.009> labs<00:17:00.189> slash<00:17:00.730> prism<00:17:01.170> we've 00:17:02.160 --> 00:17:02.170 align:start position:0% so it's prismatic labs slash prism we've 00:17:02.170 --> 00:17:03.420 align:start position:0% so it's prismatic labs slash prism we've put<00:17:02.439> a<00:17:02.470> lot<00:17:02.649> of<00:17:02.800> work<00:17:02.980> together<00:17:03.129> on 00:17:03.420 --> 00:17:03.430 align:start position:0% put a lot of work together on 00:17:03.430 --> 00:17:05.250 align:start position:0% put a lot of work together on implementing<00:17:03.790> the<00:17:04.000> beacon<00:17:04.270> chain<00:17:04.480> making 00:17:05.250 --> 00:17:05.260 align:start position:0% implementing the beacon chain making 00:17:05.260 --> 00:17:07.409 align:start position:0% implementing the beacon chain making sure<00:17:05.470> we<00:17:05.589> have<00:17:05.770> up-to-date<00:17:06.299> documentation<00:17:07.299> on 00:17:07.409 --> 00:17:07.419 align:start position:0% sure we have up-to-date documentation on 00:17:07.419 --> 00:17:09.630 align:start position:0% sure we have up-to-date documentation on how<00:17:07.569> this<00:17:07.720> works<00:17:08.020> have<00:17:08.770> parity<00:17:09.130> with<00:17:09.159> the<00:17:09.370> spec 00:17:09.630 --> 00:17:09.640 align:start position:0% how this works have parity with the spec 00:17:09.640 --> 00:17:11.130 align:start position:0% how this works have parity with the spec one<00:17:10.179> of<00:17:10.270> the<00:17:10.329> biggest<00:17:10.630> things<00:17:10.809> is<00:17:10.899> that<00:17:11.020> were 00:17:11.130 --> 00:17:11.140 align:start position:0% one of the biggest things is that were 00:17:11.140 --> 00:17:12.929 align:start position:0% one of the biggest things is that were very<00:17:11.350> much<00:17:11.679> we<00:17:12.100> aim<00:17:12.189> to<00:17:12.220> be<00:17:12.429> very<00:17:12.610> much<00:17:12.760> on<00:17:12.880> the 00:17:12.929 --> 00:17:12.939 align:start position:0% very much we aim to be very much on the 00:17:12.939 --> 00:17:14.730 align:start position:0% very much we aim to be very much on the bleeding<00:17:13.149> edge<00:17:13.390> the<00:17:14.289> thing<00:17:14.470> about<00:17:14.620> the 00:17:14.730 --> 00:17:14.740 align:start position:0% bleeding edge the thing about the 00:17:14.740 --> 00:17:16.669 align:start position:0% bleeding edge the thing about the interim<00:17:14.980> 2.0<00:17:15.339> spec<00:17:15.610> is<00:17:15.789> that<00:17:16.000> it's<00:17:16.179> very<00:17:16.449> much 00:17:16.669 --> 00:17:16.679 align:start position:0% interim 2.0 spec is that it's very much 00:17:16.679 --> 00:17:19.260 align:start position:0% interim 2.0 spec is that it's very much still<00:17:17.679> in<00:17:17.799> the<00:17:17.919> works<00:17:18.159> so<00:17:18.850> there<00:17:19.000> are<00:17:19.059> a<00:17:19.120> lot<00:17:19.240> of 00:17:19.260 --> 00:17:19.270 align:start position:0% still in the works so there are a lot of 00:17:19.270 --> 00:17:20.850 align:start position:0% still in the works so there are a lot of core<00:17:19.539> functionality<00:17:20.140> and<00:17:20.230> logistics<00:17:20.740> about 00:17:20.850 --> 00:17:20.860 align:start position:0% core functionality and logistics about 00:17:20.860 --> 00:17:22.380 align:start position:0% core functionality and logistics about how<00:17:21.100> the<00:17:21.159> validators<00:17:21.610> will<00:17:21.789> work<00:17:21.970> that<00:17:22.299> are 00:17:22.380 --> 00:17:22.390 align:start position:0% how the validators will work that are 00:17:22.390 --> 00:17:24.029 align:start position:0% how the validators will work that are still<00:17:22.600> kind<00:17:22.899> of<00:17:22.959> being<00:17:23.140> designed<00:17:23.470> a<00:17:23.740> lot<00:17:23.919> of 00:17:24.029 --> 00:17:24.039 align:start position:0% still kind of being designed a lot of 00:17:24.039 --> 00:17:25.649 align:start position:0% still kind of being designed a lot of R&D<00:17:24.399> efforts<00:17:24.789> specifically<00:17:25.299> around<00:17:25.539> the 00:17:25.649 --> 00:17:25.659 align:start position:0% R&D efforts specifically around the 00:17:25.659 --> 00:17:28.740 align:start position:0% R&D efforts specifically around the cryptography<00:17:26.230> behind<00:17:26.620> this<00:17:26.770> and<00:17:27.600> we've<00:17:28.600> been 00:17:28.740 --> 00:17:28.750 align:start position:0% cryptography behind this and we've been 00:17:28.750 --> 00:17:31.529 align:start position:0% cryptography behind this and we've been taking<00:17:29.110> we've<00:17:29.320> been<00:17:29.440> a<00:17:29.470> little<00:17:29.710> bit<00:17:29.830> more<00:17:30.539> you 00:17:31.529 --> 00:17:31.539 align:start position:0% taking we've been a little bit more you 00:17:31.539 --> 00:17:32.490 align:start position:0% taking we've been a little bit more you know<00:17:31.570> we've<00:17:31.840> been<00:17:31.870> taking<00:17:32.169> a<00:17:32.200> little<00:17:32.260> more 00:17:32.490 --> 00:17:32.500 align:start position:0% know we've been taking a little more 00:17:32.500 --> 00:17:34.350 align:start position:0% know we've been taking a little more risks<00:17:32.919> and<00:17:33.159> implementing<00:17:33.789> something<00:17:34.030> further 00:17:34.350 --> 00:17:34.360 align:start position:0% risks and implementing something further 00:17:34.360 --> 00:17:36.539 align:start position:0% risks and implementing something further ahead<00:17:34.649> so<00:17:35.649> we've<00:17:35.770> been<00:17:35.860> careful<00:17:36.130> with<00:17:36.399> you 00:17:36.539 --> 00:17:36.549 align:start position:0% ahead so we've been careful with you 00:17:36.549 --> 00:17:37.889 align:start position:0% ahead so we've been careful with you know<00:17:36.669> kind<00:17:36.880> of<00:17:36.909> how<00:17:37.030> we<00:17:37.090> design<00:17:37.419> the<00:17:37.450> system 00:17:37.889 --> 00:17:37.899 align:start position:0% know kind of how we design the system 00:17:37.899 --> 00:17:40.020 align:start position:0% know kind of how we design the system what<00:17:38.080> architecture<00:17:38.559> we<00:17:38.649> pick<00:17:38.890> how<00:17:39.549> users<00:17:39.909> will 00:17:40.020 --> 00:17:40.030 align:start position:0% what architecture we pick how users will 00:17:40.030 --> 00:17:43.380 align:start position:0% what architecture we pick how users will interact<00:17:40.270> with<00:17:40.600> this<00:17:40.780> and<00:17:41.669> what<00:17:42.669> exactly<00:17:43.179> are 00:17:43.380 --> 00:17:43.390 align:start position:0% interact with this and what exactly are 00:17:43.390 --> 00:17:46.200 align:start position:0% interact with this and what exactly are the<00:17:43.539> roles<00:17:43.780> of<00:17:44.110> the<00:17:44.919> interact<00:17:45.580> the<00:17:45.940> people 00:17:46.200 --> 00:17:46.210 align:start position:0% the roles of the interact the people 00:17:46.210 --> 00:17:49.649 align:start position:0% the roles of the interact the people interacting<00:17:46.690> in<00:17:46.780> aetherium<00:17:47.020> 2.0<00:17:47.940> so<00:17:48.940> in<00:17:49.059> s<00:17:49.179> 2.0 00:17:49.649 --> 00:17:49.659 align:start position:0% interacting in aetherium 2.0 so in s 2.0 00:17:49.659 --> 00:17:50.250 align:start position:0% interacting in aetherium 2.0 so in s 2.0 we 00:17:50.250 --> 00:17:50.260 align:start position:0% we 00:17:50.260 --> 00:17:52.770 align:start position:0% we have<00:17:50.380> an<00:17:50.920> entity<00:17:51.250> called<00:17:51.400> a<00:17:51.550> beacon<00:17:51.850> node<00:17:52.060> and 00:17:52.770 --> 00:17:52.780 align:start position:0% have an entity called a beacon node and 00:17:52.780 --> 00:17:54.390 align:start position:0% have an entity called a beacon node and we<00:17:52.870> also<00:17:53.020> have<00:17:53.260> validator<00:17:53.710> clients 00:17:54.390 --> 00:17:54.400 align:start position:0% we also have validator clients 00:17:54.400 --> 00:17:57.450 align:start position:0% we also have validator clients so<00:17:54.880> why<00:17:55.180> establish<00:17:55.720> the<00:17:55.840> separation<00:17:56.470> right<00:17:56.680> so 00:17:57.450 --> 00:17:57.460 align:start position:0% so why establish the separation right so 00:17:57.460 --> 00:17:59.010 align:start position:0% so why establish the separation right so a<00:17:57.490> beacon<00:17:57.820> node<00:17:58.000> essentially<00:17:58.450> serves<00:17:58.690> as<00:17:58.870> like 00:17:59.010 --> 00:17:59.020 align:start position:0% a beacon node essentially serves as like 00:17:59.020 --> 00:18:01.110 align:start position:0% a beacon node essentially serves as like the<00:17:59.140> source<00:17:59.380> of<00:17:59.560> randomness<00:17:59.920> for<00:18:00.760> a<00:18:00.820> theorem 00:18:01.110 --> 00:18:01.120 align:start position:0% the source of randomness for a theorem 00:18:01.120 --> 00:18:03.690 align:start position:0% the source of randomness for a theorem 2.0<00:18:01.510> it<00:18:01.870> processes<00:18:02.830> kind<00:18:03.070> of<00:18:03.160> information 00:18:03.690 --> 00:18:03.700 align:start position:0% 2.0 it processes kind of information 00:18:03.700 --> 00:18:05.700 align:start position:0% 2.0 it processes kind of information that<00:18:03.790> is<00:18:03.910> aggregated<00:18:04.450> across<00:18:04.510> shards<00:18:05.140> it 00:18:05.700 --> 00:18:05.710 align:start position:0% that is aggregated across shards it 00:18:05.710 --> 00:18:07.710 align:start position:0% that is aggregated across shards it processes<00:18:06.310> the<00:18:06.460> votes<00:18:06.700> from<00:18:07.030> validators<00:18:07.570> on 00:18:07.710 --> 00:18:07.720 align:start position:0% processes the votes from validators on 00:18:07.720 --> 00:18:10.530 align:start position:0% processes the votes from validators on shards<00:18:08.110> and<00:18:08.230> it<00:18:08.710> also<00:18:08.860> determines<00:18:09.340> casper<00:18:10.090> FFG 00:18:10.530 --> 00:18:10.540 align:start position:0% shards and it also determines casper FFG 00:18:10.540 --> 00:18:12.030 align:start position:0% shards and it also determines casper FFG rewards<00:18:10.900> and<00:18:11.020> penalties<00:18:11.140> to<00:18:11.500> people<00:18:11.770> involved 00:18:12.030 --> 00:18:12.040 align:start position:0% rewards and penalties to people involved 00:18:12.040 --> 00:18:14.700 align:start position:0% rewards and penalties to people involved so<00:18:12.510> if<00:18:13.510> you<00:18:13.600> guys<00:18:13.750> imagine<00:18:13.990> running<00:18:14.290> a<00:18:14.500> current 00:18:14.700 --> 00:18:14.710 align:start position:0% so if you guys imagine running a current 00:18:14.710 --> 00:18:16.800 align:start position:0% so if you guys imagine running a current guest<00:18:15.250> node<00:18:15.430> or<00:18:15.580> a<00:18:15.610> parody<00:18:15.880> node<00:18:16.120> in<00:18:16.330> the 00:18:16.800 --> 00:18:16.810 align:start position:0% guest node or a parody node in the 00:18:16.810 --> 00:18:18.120 align:start position:0% guest node or a parody node in the future<00:18:17.080> that's<00:18:17.230> going<00:18:17.320> to<00:18:17.470> be<00:18:17.590> what<00:18:18.010> we<00:18:18.100> call 00:18:18.120 --> 00:18:18.130 align:start position:0% future that's going to be what we call 00:18:18.130 --> 00:18:21.210 align:start position:0% future that's going to be what we call running<00:18:18.520> a<00:18:18.700> beacon<00:18:19.000> node<00:18:19.470> aside<00:18:20.470> from<00:18:20.590> that<00:18:20.650> we 00:18:21.210 --> 00:18:21.220 align:start position:0% running a beacon node aside from that we 00:18:21.220 --> 00:18:22.590 align:start position:0% running a beacon node aside from that we have<00:18:21.340> an<00:18:21.430> abstraction<00:18:21.790> of<00:18:22.030> a<00:18:22.120> validator 00:18:22.590 --> 00:18:22.600 align:start position:0% have an abstraction of a validator 00:18:22.600 --> 00:18:24.570 align:start position:0% have an abstraction of a validator client<00:18:23.020> which<00:18:23.770> is<00:18:23.950> essentially<00:18:24.280> like<00:18:24.520> a 00:18:24.570 --> 00:18:24.580 align:start position:0% client which is essentially like a 00:18:24.580 --> 00:18:26.880 align:start position:0% client which is essentially like a wrapper<00:18:24.880> that<00:18:25.840> can<00:18:26.050> help<00:18:26.230> you<00:18:26.440> you<00:18:26.620> know<00:18:26.740> kind 00:18:26.880 --> 00:18:26.890 align:start position:0% wrapper that can help you you know kind 00:18:26.890 --> 00:18:28.260 align:start position:0% wrapper that can help you you know kind of<00:18:27.010> interact<00:18:27.460> with<00:18:27.640> your<00:18:27.730> private<00:18:28.090> keys 00:18:28.260 --> 00:18:28.270 align:start position:0% of interact with your private keys 00:18:28.270 --> 00:18:29.790 align:start position:0% of interact with your private keys however<00:18:28.810> you<00:18:28.960> can<00:18:29.080> store<00:18:29.260> your<00:18:29.290> private<00:18:29.680> keys 00:18:29.790 --> 00:18:29.800 align:start position:0% however you can store your private keys 00:18:29.800 --> 00:18:31.200 align:start position:0% however you can store your private keys elsewhere<00:18:30.220> such<00:18:30.370> as<00:18:30.460> in<00:18:30.580> a<00:18:30.640> hardware<00:18:30.940> wallet 00:18:31.200 --> 00:18:31.210 align:start position:0% elsewhere such as in a hardware wallet 00:18:31.210 --> 00:18:34.140 align:start position:0% elsewhere such as in a hardware wallet or<00:18:31.600> your<00:18:32.110> other<00:18:32.290> preferred<00:18:32.650> methods<00:18:33.150> this 00:18:34.140 --> 00:18:34.150 align:start position:0% or your other preferred methods this 00:18:34.150 --> 00:18:35.520 align:start position:0% or your other preferred methods this validator<00:18:34.600> client<00:18:34.990> will<00:18:35.080> actually<00:18:35.380> be 00:18:35.520 --> 00:18:35.530 align:start position:0% validator client will actually be 00:18:35.530 --> 00:18:37.620 align:start position:0% validator client will actually be shuffled<00:18:36.010> by<00:18:36.340> the<00:18:36.400> beacon<00:18:36.820> node<00:18:37.030> into<00:18:37.360> shards 00:18:37.620 --> 00:18:37.630 align:start position:0% shuffled by the beacon node into shards 00:18:37.630 --> 00:18:40.560 align:start position:0% shuffled by the beacon node into shards and<00:18:38.070> it's<00:18:39.070> gonna<00:18:39.220> be<00:18:39.430> your<00:18:39.640> main<00:18:39.820> interface<00:18:40.180> as 00:18:40.560 --> 00:18:40.570 align:start position:0% and it's gonna be your main interface as 00:18:40.570 --> 00:18:42.810 align:start position:0% and it's gonna be your main interface as a<00:18:40.630> user<00:18:40.930> into<00:18:41.560> you<00:18:41.950> know<00:18:42.070> participating<00:18:42.730> in 00:18:42.810 --> 00:18:42.820 align:start position:0% a user into you know participating in 00:18:42.820 --> 00:18:44.220 align:start position:0% a user into you know participating in securing<00:18:43.240> the<00:18:43.330> etherium<00:18:43.720> network<00:18:43.960> for<00:18:44.140> the 00:18:44.220 --> 00:18:44.230 align:start position:0% securing the etherium network for the 00:18:44.230 --> 00:18:47.430 align:start position:0% securing the etherium network for the future<00:18:44.530> right<00:18:45.160> and<00:18:45.780> specifically<00:18:46.780> everyone 00:18:47.430 --> 00:18:47.440 align:start position:0% future right and specifically everyone 00:18:47.440 --> 00:18:50.190 align:start position:0% future right and specifically everyone needs<00:18:47.650> 32<00:18:48.370> eath<00:18:48.520> to<00:18:48.700> participate<00:18:49.240> so<00:18:49.810> this<00:18:50.080> is 00:18:50.190 --> 00:18:50.200 align:start position:0% needs 32 eath to participate so this is 00:18:50.200 --> 00:18:52.650 align:start position:0% needs 32 eath to participate so this is a<00:18:50.230> number<00:18:50.590> you<00:18:50.710> can't<00:18:50.950> go<00:18:51.190> higher<00:18:51.520> or<00:18:51.550> lower<00:18:52.060> at 00:18:52.650 --> 00:18:52.660 align:start position:0% a number you can't go higher or lower at 00:18:52.660 --> 00:18:55.140 align:start position:0% a number you can't go higher or lower at the<00:18:52.840> moment<00:18:53.280> and<00:18:54.280> what<00:18:54.550> would<00:18:54.700> this<00:18:54.790> look<00:18:54.970> like 00:18:55.140 --> 00:18:55.150 align:start position:0% the moment and what would this look like 00:18:55.150 --> 00:18:55.950 align:start position:0% the moment and what would this look like kind<00:18:55.330> of<00:18:55.420> from<00:18:55.540> a<00:18:55.630> software<00:18:55.930> architecture 00:18:55.950 --> 00:18:55.960 align:start position:0% kind of from a software architecture 00:18:55.960 --> 00:18:59.850 align:start position:0% kind of from a software architecture perspective<00:18:57.150> so<00:18:58.150> we<00:18:58.450> have<00:18:59.230> a<00:18:59.260> beacon<00:18:59.650> node 00:18:59.850 --> 00:18:59.860 align:start position:0% perspective so we have a beacon node 00:18:59.860 --> 00:19:01.350 align:start position:0% perspective so we have a beacon node that<00:19:00.190> serves<00:19:00.400> as<00:19:00.490> a<00:19:00.520> single<00:19:00.850> source<00:19:00.970> of<00:19:01.150> truth 00:19:01.350 --> 00:19:01.360 align:start position:0% that serves as a single source of truth 00:19:01.360 --> 00:19:03.240 align:start position:0% that serves as a single source of truth for<00:19:01.390> kind<00:19:01.870> of<00:19:01.930> short<00:19:02.140> assignments<00:19:02.680> state 00:19:03.240 --> 00:19:03.250 align:start position:0% for kind of short assignments state 00:19:03.250 --> 00:19:04.620 align:start position:0% for kind of short assignments state transitions<00:19:03.760> and<00:19:04.000> everything<00:19:04.270> that<00:19:04.390> happens 00:19:04.620 --> 00:19:04.630 align:start position:0% transitions and everything that happens 00:19:04.630 --> 00:19:06.900 align:start position:0% transitions and everything that happens in<00:19:04.750> that<00:19:04.810> 2.0<00:19:05.310> aside<00:19:06.310> from<00:19:06.430> that<00:19:06.640> you<00:19:06.880> have 00:19:06.900 --> 00:19:06.910 align:start position:0% in that 2.0 aside from that you have 00:19:06.910 --> 00:19:08.880 align:start position:0% in that 2.0 aside from that you have your<00:19:07.180> little<00:19:07.300> validator<00:19:07.750> client<00:19:08.170> which<00:19:08.860> is 00:19:08.880 --> 00:19:08.890 align:start position:0% your little validator client which is 00:19:08.890 --> 00:19:10.890 align:start position:0% your little validator client which is your<00:19:09.160> user<00:19:09.370> user<00:19:09.850> facing<00:19:10.300> piece<00:19:10.450> of<00:19:10.600> software 00:19:10.890 --> 00:19:10.900 align:start position:0% your user user facing piece of software 00:19:10.900 --> 00:19:12.810 align:start position:0% your user user facing piece of software so<00:19:11.530> one<00:19:11.680> thing<00:19:11.860> we<00:19:11.950> can<00:19:12.070> imagine<00:19:12.520> is<00:19:12.640> that<00:19:12.790> a 00:19:12.810 --> 00:19:12.820 align:start position:0% so one thing we can imagine is that a 00:19:12.820 --> 00:19:14.250 align:start position:0% so one thing we can imagine is that a beacon<00:19:13.090> node<00:19:13.240> can<00:19:13.420> be<00:19:13.510> something<00:19:13.720> hosted<00:19:14.140> by<00:19:14.230> a 00:19:14.250 --> 00:19:14.260 align:start position:0% beacon node can be something hosted by a 00:19:14.260 --> 00:19:16.650 align:start position:0% beacon node can be something hosted by a provider<00:19:14.710> like<00:19:14.950> in<00:19:15.100> Fuhrer<00:19:15.370> you<00:19:15.640> can<00:19:16.390> run<00:19:16.540> your 00:19:16.650 --> 00:19:16.660 align:start position:0% provider like in Fuhrer you can run your 00:19:16.660 --> 00:19:19.440 align:start position:0% provider like in Fuhrer you can run your own<00:19:16.750> beacon<00:19:17.080> node<00:19:17.230> for<00:19:17.440> example<00:19:18.240> staking<00:19:19.240> pool 00:19:19.440 --> 00:19:19.450 align:start position:0% own beacon node for example staking pool 00:19:19.450 --> 00:19:21.030 align:start position:0% own beacon node for example staking pool providers<00:19:19.990> can<00:19:20.170> run<00:19:20.350> a<00:19:20.380> bunch<00:19:20.620> of<00:19:20.740> beacon 00:19:21.030 --> 00:19:21.040 align:start position:0% providers can run a bunch of beacon 00:19:21.040 --> 00:19:24.300 align:start position:0% providers can run a bunch of beacon nodes<00:19:21.280> so<00:19:21.730> ideally<00:19:22.540> you<00:19:23.140> know<00:19:23.290> these<00:19:24.010> these 00:19:24.300 --> 00:19:24.310 align:start position:0% nodes so ideally you know these these 00:19:24.310 --> 00:19:26.760 align:start position:0% nodes so ideally you know these these machines<00:19:24.790> are<00:19:25.060> not<00:19:25.720> going<00:19:25.990> to<00:19:26.080> be<00:19:26.200> as<00:19:26.380> resource 00:19:26.760 --> 00:19:26.770 align:start position:0% machines are not going to be as resource 00:19:26.770 --> 00:19:28.640 align:start position:0% machines are not going to be as resource intensive<00:19:27.250> as<00:19:27.400> the<00:19:27.610> ones<00:19:27.790> that<00:19:27.850> we<00:19:28.000> have<00:19:28.150> today 00:19:28.640 --> 00:19:28.650 align:start position:0% intensive as the ones that we have today 00:19:28.650 --> 00:19:31.380 align:start position:0% intensive as the ones that we have today however<00:19:29.650> like<00:19:29.980> as<00:19:30.190> a<00:19:30.250> user<00:19:30.670> we<00:19:31.030> want<00:19:31.150> to<00:19:31.270> make 00:19:31.380 --> 00:19:31.390 align:start position:0% however like as a user we want to make 00:19:31.390 --> 00:19:32.580 align:start position:0% however like as a user we want to make it<00:19:31.540> also<00:19:31.810> say<00:19:31.930> you<00:19:31.990> can<00:19:32.170> run<00:19:32.260> your<00:19:32.380> own<00:19:32.440> be 00:19:32.580 --> 00:19:32.590 align:start position:0% it also say you can run your own be 00:19:32.590 --> 00:19:34.950 align:start position:0% it also say you can run your own be conduct<00:19:32.950> validator<00:19:33.910> clients<00:19:34.420> can<00:19:34.690> be<00:19:34.810> run 00:19:34.950 --> 00:19:34.960 align:start position:0% conduct validator clients can be run 00:19:34.960 --> 00:19:37.140 align:start position:0% conduct validator clients can be run anywhere<00:19:35.080> and<00:19:35.590> these<00:19:36.460> are<00:19:36.610> very<00:19:36.850> lightweight 00:19:37.140 --> 00:19:37.150 align:start position:0% anywhere and these are very lightweight 00:19:37.150 --> 00:19:39.450 align:start position:0% anywhere and these are very lightweight pieces<00:19:37.540> of<00:19:37.810> software<00:19:38.170> ideally<00:19:39.160> we<00:19:39.280> might<00:19:39.430> even 00:19:39.450 --> 00:19:39.460 align:start position:0% pieces of software ideally we might even 00:19:39.460 --> 00:19:40.980 align:start position:0% pieces of software ideally we might even abstract<00:19:40.000> it<00:19:40.120> even<00:19:40.330> more<00:19:40.510> such<00:19:40.810> that 00:19:40.980 --> 00:19:40.990 align:start position:0% abstract it even more such that 00:19:40.990 --> 00:19:42.780 align:start position:0% abstract it even more such that validators<00:19:41.470> all<00:19:41.830> you<00:19:42.100> need<00:19:42.250> to<00:19:42.340> do<00:19:42.460> is<00:19:42.580> really 00:19:42.780 --> 00:19:42.790 align:start position:0% validators all you need to do is really 00:19:42.790 --> 00:19:45.030 align:start position:0% validators all you need to do is really manage<00:19:43.390> private<00:19:43.780> keys<00:19:43.990> and<00:19:44.290> that<00:19:44.860> could<00:19:44.980> be 00:19:45.030 --> 00:19:45.040 align:start position:0% manage private keys and that could be 00:19:45.040 --> 00:19:46.050 align:start position:0% manage private keys and that could be them<00:19:45.160> through<00:19:45.280> it<00:19:45.370> through<00:19:45.670> you<00:19:45.940> know<00:19:46.030> through 00:19:46.050 --> 00:19:46.060 align:start position:0% them through it through you know through 00:19:46.060 --> 00:19:47.400 align:start position:0% them through it through you know through your<00:19:46.270> hardware<00:19:46.510> wallet<00:19:46.810> and<00:19:46.960> have<00:19:47.140> a<00:19:47.170> little 00:19:47.400 --> 00:19:47.410 align:start position:0% your hardware wallet and have a little 00:19:47.410 --> 00:19:49.710 align:start position:0% your hardware wallet and have a little interface<00:19:47.770> for<00:19:47.980> you<00:19:48.040> to<00:19:48.160> do<00:19:48.250> that<00:19:48.630> aside<00:19:49.630> from 00:19:49.710 --> 00:19:49.720 align:start position:0% interface for you to do that aside from 00:19:49.720 --> 00:19:51.240 align:start position:0% interface for you to do that aside from that<00:19:49.810> in<00:19:50.080> the<00:19:50.170> system<00:19:50.320> we<00:19:50.590> also<00:19:50.740> contain<00:19:51.130> the 00:19:51.240 --> 00:19:51.250 align:start position:0% that in the system we also contain the 00:19:51.250 --> 00:19:54.630 align:start position:0% that in the system we also contain the idea<00:19:51.460> of<00:19:51.580> shards<00:19:51.940> and<00:19:53.040> one<00:19:54.040> question<00:19:54.370> we<00:19:54.460> get<00:19:54.580> a 00:19:54.630 --> 00:19:54.640 align:start position:0% idea of shards and one question we get a 00:19:54.640 --> 00:19:56.340 align:start position:0% idea of shards and one question we get a lot<00:19:54.700> is<00:19:55.000> I<00:19:55.120> want<00:19:55.300> to<00:19:55.390> run<00:19:55.480> multiple<00:19:55.600> validators 00:19:56.340 --> 00:19:56.350 align:start position:0% lot is I want to run multiple validators 00:19:56.350 --> 00:19:58.710 align:start position:0% lot is I want to run multiple validators how<00:19:56.710> can<00:19:56.890> I<00:19:56.950> do<00:19:57.010> that<00:19:57.100> say<00:19:57.970> you're<00:19:58.150> you're<00:19:58.660> a 00:19:58.710 --> 00:19:58.720 align:start position:0% how can I do that say you're you're a 00:19:58.720 --> 00:20:01.410 align:start position:0% how can I do that say you're you're a company<00:19:59.140> you<00:19:59.620> know<00:19:59.710> we<00:19:59.890> as<00:20:00.820> an<00:20:00.970> example<00:20:01.210> when<00:20:01.390> I 00:20:01.410 --> 00:20:01.420 align:start position:0% company you know we as an example when I 00:20:01.420 --> 00:20:02.550 align:start position:0% company you know we as an example when I give<00:20:01.570> a<00:20:01.600> shout<00:20:01.750> out<00:20:01.780> to<00:20:01.960> rocket<00:20:02.230> pool<00:20:02.440> these 00:20:02.550 --> 00:20:02.560 align:start position:0% give a shout out to rocket pool these 00:20:02.560 --> 00:20:03.870 align:start position:0% give a shout out to rocket pool these guys<00:20:02.740> are<00:20:02.890> awesome<00:20:02.980> they're<00:20:03.370> working 00:20:03.870 --> 00:20:03.880 align:start position:0% guys are awesome they're working 00:20:03.880 --> 00:20:06.150 align:start position:0% guys are awesome they're working kind<00:20:04.120> of<00:20:04.179> a<00:20:04.270> staking<00:20:04.600> architecture<00:20:05.169> for 00:20:06.150 --> 00:20:06.160 align:start position:0% kind of a staking architecture for 00:20:06.160 --> 00:20:07.890 align:start position:0% kind of a staking architecture for people<00:20:06.700> to<00:20:06.789> get<00:20:06.940> involved<00:20:07.150> even<00:20:07.450> if<00:20:07.630> you<00:20:07.750> don't 00:20:07.890 --> 00:20:07.900 align:start position:0% people to get involved even if you don't 00:20:07.900 --> 00:20:10.080 align:start position:0% people to get involved even if you don't have<00:20:08.020> the<00:20:08.110> 30<00:20:08.289> to<00:20:08.440> eath<00:20:08.620> so<00:20:09.490> what<00:20:09.880> would<00:20:10.059> that 00:20:10.080 --> 00:20:10.090 align:start position:0% have the 30 to eath so what would that 00:20:10.090 --> 00:20:12.060 align:start position:0% have the 30 to eath so what would that look<00:20:10.210> like<00:20:10.440> one<00:20:11.440> of<00:20:11.530> the<00:20:11.590> things<00:20:11.770> that<00:20:11.950> we 00:20:12.060 --> 00:20:12.070 align:start position:0% look like one of the things that we 00:20:12.070 --> 00:20:16.140 align:start position:0% look like one of the things that we don't<00:20:12.370> want<00:20:12.610> to<00:20:12.910> happen<00:20:13.090> is<00:20:13.470> this<00:20:14.470> right<00:20:15.220> so<00:20:16.000> we 00:20:16.140 --> 00:20:16.150 align:start position:0% don't want to happen is this right so we 00:20:16.150 --> 00:20:17.310 align:start position:0% don't want to happen is this right so we don't<00:20:16.210> want<00:20:16.450> you<00:20:16.510> to<00:20:16.570> have<00:20:16.690> to<00:20:16.780> spin<00:20:16.990> up<00:20:17.140> a 00:20:17.310 --> 00:20:17.320 align:start position:0% don't want you to have to spin up a 00:20:17.320 --> 00:20:20.070 align:start position:0% don't want you to have to spin up a single<00:20:17.830> client<00:20:18.070> every<00:20:18.580> single<00:20:18.880> time<00:20:19.120> you<00:20:19.660> you 00:20:20.070 --> 00:20:20.080 align:start position:0% single client every single time you you 00:20:20.080 --> 00:20:21.390 align:start position:0% single client every single time you you want<00:20:20.289> to<00:20:20.350> stake<00:20:20.590> 32<00:20:20.919> eath<00:20:21.070> you<00:20:21.190> want<00:20:21.340> to 00:20:21.390 --> 00:20:21.400 align:start position:0% want to stake 32 eath you want to 00:20:21.400 --> 00:20:23.730 align:start position:0% want to stake 32 eath you want to participate<00:20:21.789> in<00:20:21.880> the<00:20:21.940> network<00:20:22.179> so<00:20:22.559> one<00:20:23.559> of<00:20:23.590> the 00:20:23.730 --> 00:20:23.740 align:start position:0% participate in the network so one of the 00:20:23.740 --> 00:20:25.320 align:start position:0% participate in the network so one of the one<00:20:24.039> of<00:20:24.070> the<00:20:24.130> things<00:20:24.220> we've<00:20:24.460> gotten<00:20:24.730> around<00:20:24.910> is 00:20:25.320 --> 00:20:25.330 align:start position:0% one of the things we've gotten around is 00:20:25.330 --> 00:20:27.330 align:start position:0% one of the things we've gotten around is actually<00:20:26.260> creating<00:20:26.770> a<00:20:26.830> multi-tenant 00:20:27.330 --> 00:20:27.340 align:start position:0% actually creating a multi-tenant 00:20:27.340 --> 00:20:30.240 align:start position:0% actually creating a multi-tenant validator<00:20:28.270> client<00:20:28.600> architecture<00:20:29.010> so<00:20:30.010> in<00:20:30.160> the 00:20:30.240 --> 00:20:30.250 align:start position:0% validator client architecture so in the 00:20:30.250 --> 00:20:31.710 align:start position:0% validator client architecture so in the sense<00:20:30.460> that<00:20:30.580> like<00:20:30.669> validator<00:20:31.210> assignments 00:20:31.710 --> 00:20:31.720 align:start position:0% sense that like validator assignments 00:20:31.720 --> 00:20:34.799 align:start position:0% sense that like validator assignments are<00:20:32.350> live<00:20:32.650> streamed<00:20:33.010> for<00:20:33.520> a<00:20:33.549> subset<00:20:34.059> of<00:20:34.090> public 00:20:34.799 --> 00:20:34.809 align:start position:0% are live streamed for a subset of public 00:20:34.809 --> 00:20:36.840 align:start position:0% are live streamed for a subset of public keys<00:20:35.049> so<00:20:35.830> for<00:20:35.950> example<00:20:36.340> I'm<00:20:36.520> running<00:20:36.789> a 00:20:36.840 --> 00:20:36.850 align:start position:0% keys so for example I'm running a 00:20:36.850 --> 00:20:38.669 align:start position:0% keys so for example I'm running a validator<00:20:37.179> client<00:20:37.570> on<00:20:37.690> my<00:20:38.020> laptop<00:20:38.350> or<00:20:38.620> my 00:20:38.669 --> 00:20:38.679 align:start position:0% validator client on my laptop or my 00:20:38.679 --> 00:20:42.480 align:start position:0% validator client on my laptop or my computer<00:20:39.190> at<00:20:39.400> home<00:20:39.580> I<00:20:40.330> manage<00:20:41.080> 10<00:20:41.950> public<00:20:42.340> keys 00:20:42.480 --> 00:20:42.490 align:start position:0% computer at home I manage 10 public keys 00:20:42.490 --> 00:20:45.270 align:start position:0% computer at home I manage 10 public keys on<00:20:42.700> there<00:20:42.880> I<00:20:43.059> can<00:20:43.900> send<00:20:44.169> an<00:20:44.320> API<00:20:44.590> request<00:20:45.010> to<00:20:45.159> my 00:20:45.270 --> 00:20:45.280 align:start position:0% on there I can send an API request to my 00:20:45.280 --> 00:20:47.250 align:start position:0% on there I can send an API request to my beacon<00:20:45.580> node<00:20:45.820> for<00:20:46.510> the<00:20:46.720> assignments<00:20:47.200> for 00:20:47.250 --> 00:20:47.260 align:start position:0% beacon node for the assignments for 00:20:47.260 --> 00:20:49.080 align:start position:0% beacon node for the assignments for those<00:20:47.380> 10<00:20:47.590> public<00:20:47.919> keys<00:20:48.130> and<00:20:48.400> I<00:20:48.549> get<00:20:48.700> a<00:20:48.730> stream 00:20:49.080 --> 00:20:49.090 align:start position:0% those 10 public keys and I get a stream 00:20:49.090 --> 00:20:50.640 align:start position:0% those 10 public keys and I get a stream telling<00:20:49.510> me<00:20:49.600> exactly<00:20:49.929> what<00:20:50.140> I<00:20:50.169> need<00:20:50.320> to<00:20:50.409> do<00:20:50.500> my 00:20:50.640 --> 00:20:50.650 align:start position:0% telling me exactly what I need to do my 00:20:50.650 --> 00:20:52.590 align:start position:0% telling me exactly what I need to do my job<00:20:50.890> I<00:20:51.159> don't<00:20:51.549> need<00:20:51.730> to<00:20:51.820> do<00:20:51.909> anything<00:20:52.090> I<00:20:52.390> just 00:20:52.590 --> 00:20:52.600 align:start position:0% job I don't need to do anything I just 00:20:52.600 --> 00:20:55.500 align:start position:0% job I don't need to do anything I just have<00:20:52.720> one<00:20:52.840> machine<00:20:53.260> I<00:20:53.559> trust<00:20:54.010> it<00:20:54.240> and<00:20:55.240> things 00:20:55.500 --> 00:20:55.510 align:start position:0% have one machine I trust it and things 00:20:55.510 --> 00:20:58.470 align:start position:0% have one machine I trust it and things get<00:20:55.690> done<00:20:56.250> so<00:20:57.250> essentially<00:20:57.970> we<00:20:58.150> also<00:20:58.270> this 00:20:58.470 --> 00:20:58.480 align:start position:0% get done so essentially we also this 00:20:58.480 --> 00:21:00.180 align:start position:0% get done so essentially we also this also<00:20:58.630> allows<00:20:58.960> for<00:20:58.990> validator<00:20:59.530> as<00:20:59.679> a<00:20:59.710> service 00:21:00.180 --> 00:21:00.190 align:start position:0% also allows for validator as a service 00:21:00.190 --> 00:21:02.669 align:start position:0% also allows for validator as a service sort<00:21:00.640> of<00:21:00.700> opportunities<00:21:01.299> at<00:21:02.140> prism<00:21:02.559> we're 00:21:02.669 --> 00:21:02.679 align:start position:0% sort of opportunities at prism we're 00:21:02.679 --> 00:21:03.990 align:start position:0% sort of opportunities at prism we're going<00:21:02.860> to<00:21:02.950> be<00:21:03.010> shipping<00:21:03.370> our<00:21:03.490> own<00:21:03.610> in-house 00:21:03.990 --> 00:21:04.000 align:start position:0% going to be shipping our own in-house 00:21:04.000 --> 00:21:05.310 align:start position:0% going to be shipping our own in-house validator<00:21:04.450> client<00:21:04.809> that<00:21:04.870> you<00:21:04.960> guys<00:21:05.110> can<00:21:05.289> use 00:21:05.310 --> 00:21:05.320 align:start position:0% validator client that you guys can use 00:21:05.320 --> 00:21:07.320 align:start position:0% validator client that you guys can use but<00:21:06.070> it<00:21:06.159> should<00:21:06.309> be<00:21:06.340> a<00:21:06.429> very<00:21:06.520> simple<00:21:07.090> piece<00:21:07.299> of 00:21:07.320 --> 00:21:07.330 align:start position:0% but it should be a very simple piece of 00:21:07.330 --> 00:21:09.240 align:start position:0% but it should be a very simple piece of software<00:21:07.450> that<00:21:08.380> any<00:21:08.530> other<00:21:08.740> person<00:21:09.100> can 00:21:09.240 --> 00:21:09.250 align:start position:0% software that any other person can 00:21:09.250 --> 00:21:10.919 align:start position:0% software that any other person can create<00:21:09.370> as<00:21:09.610> well<00:21:09.820> as<00:21:10.000> long<00:21:10.240> as<00:21:10.270> it<00:21:10.480> conforms<00:21:10.870> to 00:21:10.919 --> 00:21:10.929 align:start position:0% create as well as long as it conforms to 00:21:10.929 --> 00:21:12.570 align:start position:0% create as well as long as it conforms to the<00:21:11.080> beacon<00:21:11.380> know<00:21:11.470> that<00:21:11.620> theorem<00:21:11.830> 2.0<00:21:12.250> API 00:21:12.570 --> 00:21:12.580 align:start position:0% the beacon know that theorem 2.0 API 00:21:12.580 --> 00:21:15.120 align:start position:0% the beacon know that theorem 2.0 API right<00:21:13.380> and<00:21:14.380> like<00:21:14.500> I<00:21:14.590> said<00:21:14.740> these<00:21:14.830> are<00:21:14.890> very 00:21:15.120 --> 00:21:15.130 align:start position:0% right and like I said these are very 00:21:15.130 --> 00:21:16.440 align:start position:0% right and like I said these are very lightweight<00:21:15.340> can<00:21:15.789> be<00:21:15.850> spun<00:21:16.000> all<00:21:16.179> types<00:21:16.360> of 00:21:16.440 --> 00:21:16.450 align:start position:0% lightweight can be spun all types of 00:21:16.450 --> 00:21:17.970 align:start position:0% lightweight can be spun all types of devices<00:21:16.570> so<00:21:17.020> I<00:21:17.049> can<00:21:17.260> even<00:21:17.440> imagine<00:21:17.620> having 00:21:17.970 --> 00:21:17.980 align:start position:0% devices so I can even imagine having 00:21:17.980 --> 00:21:20.370 align:start position:0% devices so I can even imagine having your<00:21:18.190> phone<00:21:18.429> as<00:21:18.700> as<00:21:19.630> the<00:21:19.780> entity<00:21:20.049> that<00:21:20.169> you 00:21:20.370 --> 00:21:20.380 align:start position:0% your phone as as the entity that you 00:21:20.380 --> 00:21:21.840 align:start position:0% your phone as as the entity that you know<00:21:20.500> stores<00:21:20.770> private<00:21:21.100> keys<00:21:21.250> and<00:21:21.549> can<00:21:21.700> help 00:21:21.840 --> 00:21:21.850 align:start position:0% know stores private keys and can help 00:21:21.850 --> 00:21:24.680 align:start position:0% know stores private keys and can help with<00:21:22.000> signing<00:21:22.390> the<00:21:22.720> transactions<00:21:23.260> required 00:21:24.680 --> 00:21:24.690 align:start position:0% with signing the transactions required 00:21:24.690 --> 00:21:27.690 align:start position:0% with signing the transactions required so<00:21:25.690> what<00:21:26.110> does<00:21:26.440> beacon<00:21:27.280> change<00:21:27.490> kind<00:21:27.610> of 00:21:27.690 --> 00:21:27.700 align:start position:0% so what does beacon change kind of 00:21:27.700 --> 00:21:30.360 align:start position:0% so what does beacon change kind of public<00:21:27.970> API<00:21:28.210> look<00:21:28.450> like<00:21:28.630> and<00:21:29.220> one<00:21:30.220> of<00:21:30.309> the 00:21:30.360 --> 00:21:30.370 align:start position:0% public API look like and one of the 00:21:30.370 --> 00:21:31.710 align:start position:0% public API look like and one of the things<00:21:30.490> that<00:21:30.669> we<00:21:30.730> want<00:21:30.880> to<00:21:30.909> do<00:21:31.059> is<00:21:31.299> we<00:21:31.480> want<00:21:31.659> to 00:21:31.710 --> 00:21:31.720 align:start position:0% things that we want to do is we want to 00:21:31.720 --> 00:21:33.299 align:start position:0% things that we want to do is we want to improve<00:21:32.049> upon<00:21:32.230> the<00:21:32.440> current<00:21:32.740> system<00:21:33.070> which 00:21:33.299 --> 00:21:33.309 align:start position:0% improve upon the current system which 00:21:33.309 --> 00:21:36.000 align:start position:0% improve upon the current system which currently<00:21:33.610> uses<00:21:33.940> JSON<00:21:34.150> RPC<00:21:34.570> I'm<00:21:35.470> sure<00:21:35.650> a<00:21:35.860> lot 00:21:36.000 --> 00:21:36.010 align:start position:0% currently uses JSON RPC I'm sure a lot 00:21:36.010 --> 00:21:37.230 align:start position:0% currently uses JSON RPC I'm sure a lot of<00:21:36.039> you<00:21:36.220> are<00:21:36.280> familiar<00:21:36.400> with<00:21:36.730> that<00:21:36.789> here 00:21:37.230 --> 00:21:37.240 align:start position:0% of you are familiar with that here 00:21:37.240 --> 00:21:39.690 align:start position:0% of you are familiar with that here includes<00:21:38.020> a<00:21:38.110> lot<00:21:38.230> of<00:21:38.350> a<00:21:38.620> lot<00:21:38.770> of<00:21:38.860> issues<00:21:39.010> a<00:21:39.250> lot 00:21:39.690 --> 00:21:39.700 align:start position:0% includes a lot of a lot of issues a lot 00:21:39.700 --> 00:21:41.640 align:start position:0% includes a lot of a lot of issues a lot of<00:21:39.760> issues<00:21:39.880> with<00:21:40.090> standardization<00:21:40.840> and<00:21:41.110> it's 00:21:41.640 --> 00:21:41.650 align:start position:0% of issues with standardization and it's 00:21:41.650 --> 00:21:43.710 align:start position:0% of issues with standardization and it's not<00:21:41.799> something<00:21:42.159> that<00:21:42.190> I<00:21:42.340> think<00:21:43.150> we<00:21:43.299> believe<00:21:43.600> is 00:21:43.710 --> 00:21:43.720 align:start position:0% not something that I think we believe is 00:21:43.720 --> 00:21:46.770 align:start position:0% not something that I think we believe is robust<00:21:44.110> enough<00:21:44.230> for<00:21:45.039> a<00:21:45.070> theorem<00:21:45.370> 2.0<00:21:45.780> so 00:21:46.770 --> 00:21:46.780 align:start position:0% robust enough for a theorem 2.0 so 00:21:46.780 --> 00:21:48.960 align:start position:0% robust enough for a theorem 2.0 so instead<00:21:47.169> we're<00:21:48.100> going<00:21:48.400> with<00:21:48.520> protocol 00:21:48.960 --> 00:21:48.970 align:start position:0% instead we're going with protocol 00:21:48.970 --> 00:21:51.240 align:start position:0% instead we're going with protocol buffers<00:21:49.360> and<00:21:49.620> protocol<00:21:50.620> buffers<00:21:50.919> give<00:21:51.130> you<00:21:51.190> a 00:21:51.240 --> 00:21:51.250 align:start position:0% buffers and protocol buffers give you a 00:21:51.250 --> 00:21:55.260 align:start position:0% buffers and protocol buffers give you a lot<00:21:51.429> of<00:21:51.460> benefits<00:21:51.970> so<00:21:52.150> as<00:21:53.140> an<00:21:53.380> example<00:21:54.150> say<00:21:55.150> we 00:21:55.260 --> 00:21:55.270 align:start position:0% lot of benefits so as an example say we 00:21:55.270 --> 00:21:56.580 align:start position:0% lot of benefits so as an example say we have<00:21:55.450> two<00:21:55.780> nodes<00:21:55.929> communicating<00:21:56.440> with<00:21:56.530> each 00:21:56.580 --> 00:21:56.590 align:start position:0% have two nodes communicating with each 00:21:56.590 --> 00:21:59.220 align:start position:0% have two nodes communicating with each other<00:21:56.710> right<00:21:57.659> protocol<00:21:58.659> buffers<00:21:58.929> provide 00:21:59.220 --> 00:21:59.230 align:start position:0% other right protocol buffers provide 00:21:59.230 --> 00:22:01.440 align:start position:0% other right protocol buffers provide this<00:21:59.350> by<00:21:59.500> directionality<00:22:00.039> of<00:22:00.450> essentially 00:22:01.440 --> 00:22:01.450 align:start position:0% this by directionality of essentially 00:22:01.450 --> 00:22:03.090 align:start position:0% this by directionality of essentially you<00:22:01.630> know<00:22:01.720> having<00:22:01.990> a<00:22:02.080> good<00:22:02.230> standard<00:22:02.710> for<00:22:03.070> a 00:22:03.090 --> 00:22:03.100 align:start position:0% you know having a good standard for a 00:22:03.100 --> 00:22:05.039 align:start position:0% you know having a good standard for a public<00:22:03.460> API<00:22:03.730> allowing<00:22:04.539> notes<00:22:04.840> to<00:22:04.960> know 00:22:05.039 --> 00:22:05.049 align:start position:0% public API allowing notes to know 00:22:05.049 --> 00:22:07.320 align:start position:0% public API allowing notes to know exactly<00:22:05.440> what<00:22:05.620> to<00:22:05.740> expect<00:22:06.159> and<00:22:06.340> allow<00:22:07.090> them<00:22:07.240> to 00:22:07.320 --> 00:22:07.330 align:start position:0% exactly what to expect and allow them to 00:22:07.330 --> 00:22:08.460 align:start position:0% exactly what to expect and allow them to interact<00:22:07.510> with<00:22:07.659> each<00:22:07.780> other<00:22:07.900> in<00:22:08.080> a<00:22:08.140> way<00:22:08.260> that 00:22:08.460 --> 00:22:08.470 align:start position:0% interact with each other in a way that 00:22:08.470 --> 00:22:10.590 align:start position:0% interact with each other in a way that we<00:22:08.620> know<00:22:08.770> will<00:22:09.010> work<00:22:09.220> even<00:22:09.730> cross<00:22:09.940> clients 00:22:10.590 --> 00:22:10.600 align:start position:0% we know will work even cross clients 00:22:10.600 --> 00:22:12.810 align:start position:0% we know will work even cross clients whereas<00:22:11.320> with<00:22:11.530> JSON<00:22:11.890> for<00:22:12.159> example<00:22:12.580> every 00:22:12.810 --> 00:22:12.820 align:start position:0% whereas with JSON for example every 00:22:12.820 --> 00:22:14.159 align:start position:0% whereas with JSON for example every client<00:22:13.120> needs<00:22:13.240> to<00:22:13.299> write<00:22:13.540> kind<00:22:13.780> of<00:22:13.900> their<00:22:14.049> own 00:22:14.159 --> 00:22:14.169 align:start position:0% client needs to write kind of their own 00:22:14.169 --> 00:22:15.930 align:start position:0% client needs to write kind of their own way<00:22:14.409> of<00:22:14.440> doing<00:22:14.590> things<00:22:15.040> you're<00:22:15.700> into<00:22:15.880> the 00:22:15.930 --> 00:22:15.940 align:start position:0% way of doing things you're into the 00:22:15.940 --> 00:22:17.220 align:start position:0% way of doing things you're into the situation<00:22:16.330> where<00:22:16.450> like<00:22:16.570> on<00:22:16.780> the 00:22:17.220 --> 00:22:17.230 align:start position:0% situation where like on the 00:22:17.230 --> 00:22:18.450 align:start position:0% situation where like on the sender<00:22:17.500> and<00:22:17.650> I'm<00:22:17.830> really<00:22:18.010> happy<00:22:18.190> with<00:22:18.340> what 00:22:18.450 --> 00:22:18.460 align:start position:0% sender and I'm really happy with what 00:22:18.460 --> 00:22:21.120 align:start position:0% sender and I'm really happy with what I'm<00:22:18.549> sending<00:22:18.940> the<00:22:19.570> recipe<00:22:19.870> has<00:22:19.990> no<00:22:20.140> idea<00:22:20.380> right 00:22:21.120 --> 00:22:21.130 align:start position:0% I'm sending the recipe has no idea right 00:22:21.130 --> 00:22:23.310 align:start position:0% I'm sending the recipe has no idea right as<00:22:21.700> of<00:22:21.910> today<00:22:22.120> a<00:22:22.510> lot<00:22:22.929> of<00:22:23.049> the<00:22:23.140> current 00:22:23.310 --> 00:22:23.320 align:start position:0% as of today a lot of the current 00:22:23.320 --> 00:22:24.570 align:start position:0% as of today a lot of the current aetherium<00:22:23.770> clients<00:22:24.160> they<00:22:24.309> don't<00:22:24.340> even 00:22:24.570 --> 00:22:24.580 align:start position:0% aetherium clients they don't even 00:22:24.580 --> 00:22:26.789 align:start position:0% aetherium clients they don't even implement<00:22:25.059> all<00:22:25.450> the<00:22:25.750> web<00:22:25.900> 3<00:22:26.110> endpoint<00:22:26.470> methods 00:22:26.789 --> 00:22:26.799 align:start position:0% implement all the web 3 endpoint methods 00:22:26.799 --> 00:22:28.380 align:start position:0% implement all the web 3 endpoint methods that<00:22:26.950> the<00:22:27.160> other<00:22:27.280> clients<00:22:27.730> do<00:22:27.880> that's 00:22:28.380 --> 00:22:28.390 align:start position:0% that the other clients do that's 00:22:28.390 --> 00:22:29.580 align:start position:0% that the other clients do that's something<00:22:28.510> we're<00:22:28.809> going<00:22:28.929> to<00:22:28.990> actively<00:22:29.410> try<00:22:29.559> to 00:22:29.580 --> 00:22:29.590 align:start position:0% something we're going to actively try to 00:22:29.590 --> 00:22:32.190 align:start position:0% something we're going to actively try to avoid<00:22:29.890> and<00:22:30.100> at<00:22:30.220> 2.0<00:22:30.870> so<00:22:31.870> just<00:22:31.990> to<00:22:32.049> give<00:22:32.169> you 00:22:32.190 --> 00:22:32.200 align:start position:0% avoid and at 2.0 so just to give you 00:22:32.200 --> 00:22:33.840 align:start position:0% avoid and at 2.0 so just to give you guys<00:22:32.350> an<00:22:32.470> example<00:22:32.500> of<00:22:32.919> gee<00:22:33.040> our<00:22:33.130> PC<00:22:33.490> connection 00:22:33.840 --> 00:22:33.850 align:start position:0% guys an example of gee our PC connection 00:22:33.850 --> 00:22:36.180 align:start position:0% guys an example of gee our PC connection metrics<00:22:34.299> so<00:22:35.200> G<00:22:35.350> RPC<00:22:35.679> is<00:22:35.770> kind<00:22:35.950> of<00:22:36.010> like<00:22:36.160> a 00:22:36.180 --> 00:22:36.190 align:start position:0% metrics so G RPC is kind of like a 00:22:36.190 --> 00:22:37.710 align:start position:0% metrics so G RPC is kind of like a framework<00:22:36.669> put<00:22:36.880> together<00:22:37.000> by<00:22:37.240> Google<00:22:37.570> for 00:22:37.710 --> 00:22:37.720 align:start position:0% framework put together by Google for 00:22:37.720 --> 00:22:40.740 align:start position:0% framework put together by Google for this<00:22:38.410> remote<00:22:38.950> procedure<00:22:39.070> call<00:22:39.750> service 00:22:40.740 --> 00:22:40.750 align:start position:0% this remote procedure call service 00:22:40.750 --> 00:22:43.560 align:start position:0% this remote procedure call service optimization<00:22:41.380> and<00:22:41.940> currently<00:22:42.940> you<00:22:43.120> know<00:22:43.150> when 00:22:43.560 --> 00:22:43.570 align:start position:0% optimization and currently you know when 00:22:43.570 --> 00:22:46.470 align:start position:0% optimization and currently you know when you<00:22:43.660> use<00:22:43.840> JSON<00:22:44.260> RPC<00:22:44.640> you<00:22:45.640> get<00:22:45.790> around<00:22:46.030> you<00:22:46.390> know 00:22:46.470 --> 00:22:46.480 align:start position:0% you use JSON RPC you get around you know 00:22:46.480 --> 00:22:48.780 align:start position:0% you use JSON RPC you get around you know almost<00:22:46.690> a<00:22:46.900> 10<00:22:47.110> order<00:22:47.470> which<00:22:48.250> in<00:22:48.340> reality<00:22:48.490> is 00:22:48.780 --> 00:22:48.790 align:start position:0% almost a 10 order which in reality is 00:22:48.790 --> 00:22:51.720 align:start position:0% almost a 10 order which in reality is about<00:22:49.030> like<00:22:49.179> a<00:22:49.210> 6<00:22:49.480> you<00:22:50.470> know<00:22:50.559> 6<00:22:51.250> times 00:22:51.720 --> 00:22:51.730 align:start position:0% about like a 6 you know 6 times 00:22:51.730 --> 00:22:53.880 align:start position:0% about like a 6 you know 6 times order<00:22:52.120> of<00:22:52.240> throughput<00:22:52.450> compared<00:22:53.440> to<00:22:53.500> JSON<00:22:53.799> RPC 00:22:53.880 --> 00:22:53.890 align:start position:0% order of throughput compared to JSON RPC 00:22:53.890 --> 00:22:57.480 align:start position:0% order of throughput compared to JSON RPC when<00:22:54.309> you<00:22:54.400> see<00:22:54.580> a<00:22:54.610> proto<00:22:55.360> bus<00:22:55.620> why<00:22:56.620> is<00:22:56.679> this<00:22:57.010> in 00:22:57.480 --> 00:22:57.490 align:start position:0% when you see a proto bus why is this in 00:22:57.490 --> 00:22:58.530 align:start position:0% when you see a proto bus why is this in particular<00:22:57.910> you<00:22:58.120> know<00:22:58.210> why<00:22:58.390> is<00:22:58.450> this 00:22:58.530 --> 00:22:58.540 align:start position:0% particular you know why is this 00:22:58.540 --> 00:23:00.120 align:start position:0% particular you know why is this important<00:22:58.990> well<00:22:59.200> we<00:22:59.290> want<00:22:59.470> to<00:22:59.530> make<00:22:59.620> sure<00:22:59.919> like 00:23:00.120 --> 00:23:00.130 align:start position:0% important well we want to make sure like 00:23:00.130 --> 00:23:01.560 align:start position:0% important well we want to make sure like I<00:23:00.220> said<00:23:00.429> want<00:23:00.610> to<00:23:00.700> reduce<00:23:00.850> the<00:23:01.059> mutt<00:23:01.240> as<00:23:01.360> much 00:23:01.560 --> 00:23:01.570 align:start position:0% I said want to reduce the mutt as much 00:23:01.570 --> 00:23:02.820 align:start position:0% I said want to reduce the mutt as much friction<00:23:01.809> as<00:23:01.990> possible<00:23:02.380> which<00:23:02.470> we<00:23:02.620> knows 00:23:02.820 --> 00:23:02.830 align:start position:0% friction as possible which we knows 00:23:02.830 --> 00:23:05.340 align:start position:0% friction as possible which we knows using<00:23:03.130> a<00:23:03.220> 2.0<00:23:03.669> to<00:23:04.390> make<00:23:04.570> it<00:23:04.720> so<00:23:04.840> that<00:23:04.870> you<00:23:05.169> don't 00:23:05.340 --> 00:23:05.350 align:start position:0% using a 2.0 to make it so that you don't 00:23:05.350 --> 00:23:07.320 align:start position:0% using a 2.0 to make it so that you don't need<00:23:05.410> to<00:23:05.470> worry<00:23:05.770> about<00:23:05.890> this<00:23:06.070> as<00:23:06.190> a<00:23:06.220> user<00:23:06.460> you 00:23:07.320 --> 00:23:07.330 align:start position:0% need to worry about this as a user you 00:23:07.330 --> 00:23:09.150 align:start position:0% need to worry about this as a user you don't<00:23:07.510> need<00:23:07.600> to<00:23:07.720> worry<00:23:07.929> about<00:23:08.290> like<00:23:08.500> the 00:23:09.150 --> 00:23:09.160 align:start position:0% don't need to worry about like the 00:23:09.160 --> 00:23:11.539 align:start position:0% don't need to worry about like the bottlenecks<00:23:09.610> that<00:23:09.669> you'll<00:23:09.850> obtain<00:23:10.030> from<00:23:10.299> this 00:23:11.539 --> 00:23:11.549 align:start position:0% bottlenecks that you'll obtain from this 00:23:11.549 --> 00:23:14.159 align:start position:0% bottlenecks that you'll obtain from this aside<00:23:12.549> from<00:23:12.669> that<00:23:12.880> here<00:23:13.450> are<00:23:13.510> some<00:23:13.630> utilities 00:23:14.159 --> 00:23:14.169 align:start position:0% aside from that here are some utilities 00:23:14.169 --> 00:23:15.570 align:start position:0% aside from that here are some utilities that<00:23:14.200> will<00:23:14.350> provide<00:23:14.650> our<00:23:14.890> client<00:23:15.280> for<00:23:15.490> you 00:23:15.570 --> 00:23:15.580 align:start position:0% that will provide our client for you 00:23:15.580 --> 00:23:17.250 align:start position:0% that will provide our client for you guys<00:23:15.730> to<00:23:15.880> use<00:23:15.910> and<00:23:16.360> that<00:23:16.900> are<00:23:16.990> gonna<00:23:17.049> be 00:23:17.250 --> 00:23:17.260 align:start position:0% guys to use and that are gonna be 00:23:17.260 --> 00:23:18.720 align:start position:0% guys to use and that are gonna be basically<00:23:17.620> like<00:23:17.799> you<00:23:17.950> know<00:23:18.010> public<00:23:18.220> packages 00:23:18.720 --> 00:23:18.730 align:start position:0% basically like you know public packages 00:23:18.730 --> 00:23:19.770 align:start position:0% basically like you know public packages that<00:23:18.820> can<00:23:18.910> be<00:23:19.030> imported<00:23:19.240> across<00:23:19.600> other 00:23:19.770 --> 00:23:19.780 align:start position:0% that can be imported across other 00:23:19.780 --> 00:23:22.409 align:start position:0% that can be imported across other projects<00:23:20.380> so<00:23:21.130> if<00:23:21.490> you<00:23:21.580> guys<00:23:21.730> went<00:23:22.000> to<00:23:22.059> Justin's 00:23:22.409 --> 00:23:22.419 align:start position:0% projects so if you guys went to Justin's 00:23:22.419 --> 00:23:24.360 align:start position:0% projects so if you guys went to Justin's Drake<00:23:22.660> I<00:23:22.840> just<00:23:23.049> in<00:23:23.169> Drake's<00:23:23.380> randomness<00:23:24.190> talk 00:23:24.360 --> 00:23:24.370 align:start position:0% Drake I just in Drake's randomness talk 00:23:24.370 --> 00:23:26.460 align:start position:0% Drake I just in Drake's randomness talk for<00:23:24.549> s<00:23:24.610> 2.0<00:23:25.090> we're<00:23:25.990> going<00:23:26.110> to<00:23:26.169> be<00:23:26.260> leveraging 00:23:26.460 --> 00:23:26.470 align:start position:0% for s 2.0 we're going to be leveraging 00:23:26.470 --> 00:23:30.000 align:start position:0% for s 2.0 we're going to be leveraging the<00:23:26.830> power<00:23:26.860> of<00:23:27.400> a<00:23:27.730> six<00:23:28.260> basic<00:23:29.260> rigs<00:23:29.500> to<00:23:29.740> create 00:23:30.000 --> 00:23:30.010 align:start position:0% the power of a six basic rigs to create 00:23:30.010 --> 00:23:31.770 align:start position:0% the power of a six basic rigs to create a<00:23:30.040> verifiable<00:23:30.790> delay<00:23:31.030> function<00:23:31.390> source<00:23:31.660> of 00:23:31.770 --> 00:23:31.780 align:start position:0% a verifiable delay function source of 00:23:31.780 --> 00:23:33.930 align:start position:0% a verifiable delay function source of randomness<00:23:31.900> for<00:23:32.320> a<00:23:32.380> tearoom<00:23:32.590> 2.0<00:23:32.980> so<00:23:33.790> it's 00:23:33.930 --> 00:23:33.940 align:start position:0% randomness for a tearoom 2.0 so it's 00:23:33.940 --> 00:23:35.280 align:start position:0% randomness for a tearoom 2.0 so it's really<00:23:34.120> cool<00:23:34.299> because<00:23:34.480> you<00:23:35.020> can<00:23:35.049> actually 00:23:35.280 --> 00:23:35.290 align:start position:0% really cool because you can actually 00:23:35.290 --> 00:23:36.980 align:start position:0% really cool because you can actually have<00:23:35.710> a<00:23:35.740> public<00:23:36.070> API<00:23:36.309> where<00:23:36.490> you<00:23:36.520> can<00:23:36.580> query 00:23:36.980 --> 00:23:36.990 align:start position:0% have a public API where you can query 00:23:36.990 --> 00:23:40.289 align:start position:0% have a public API where you can query the<00:23:37.990> randomness<00:23:38.590> like<00:23:39.130> unbiased<00:23:39.669> able<00:23:39.910> strong 00:23:40.289 --> 00:23:40.299 align:start position:0% the randomness like unbiased able strong 00:23:40.299 --> 00:23:42.570 align:start position:0% the randomness like unbiased able strong randomness<00:23:41.169> I'm<00:23:41.440> a<00:23:41.500> theorem<00:23:41.740> 2.0<00:23:42.100> nodes<00:23:42.340> that 00:23:42.570 --> 00:23:42.580 align:start position:0% randomness I'm a theorem 2.0 nodes that 00:23:42.580 --> 00:23:45.030 align:start position:0% randomness I'm a theorem 2.0 nodes that you<00:23:42.669> can<00:23:42.820> use<00:23:42.940> in<00:23:43.059> your<00:23:43.090> applications<00:23:44.040> we're 00:23:45.030 --> 00:23:45.040 align:start position:0% you can use in your applications we're 00:23:45.040 --> 00:23:46.650 align:start position:0% you can use in your applications we're gonna<00:23:45.160> have<00:23:45.340> a<00:23:45.370> very<00:23:45.520> robust<00:23:45.880> key<00:23:46.120> value<00:23:46.419> store 00:23:46.650 --> 00:23:46.660 align:start position:0% gonna have a very robust key value store 00:23:46.660 --> 00:23:48.690 align:start position:0% gonna have a very robust key value store using<00:23:46.960> both<00:23:47.140> DB<00:23:47.500> which<00:23:47.919> is<00:23:47.950> a<00:23:48.070> write<00:23:48.280> optimized 00:23:48.690 --> 00:23:48.700 align:start position:0% using both DB which is a write optimized 00:23:48.700 --> 00:23:50.970 align:start position:0% using both DB which is a write optimized database<00:23:49.120> specifically<00:23:49.900> you<00:23:50.140> know<00:23:50.230> very<00:23:50.740> well 00:23:50.970 --> 00:23:50.980 align:start position:0% database specifically you know very well 00:23:50.980 --> 00:23:52.710 align:start position:0% database specifically you know very well very<00:23:51.400> well<00:23:51.490> created<00:23:51.970> for<00:23:52.090> block<00:23:52.240> chains<00:23:52.480> as 00:23:52.710 --> 00:23:52.720 align:start position:0% very well created for block chains as 00:23:52.720 --> 00:23:54.539 align:start position:0% very well created for block chains as well<00:23:53.260> as<00:23:53.530> the<00:23:53.620> signature<00:23:53.919> aggregation 00:23:54.539 --> 00:23:54.549 align:start position:0% well as the signature aggregation 00:23:54.549 --> 00:23:56.669 align:start position:0% well as the signature aggregation library<00:23:54.880> using<00:23:55.150> VLS<00:23:55.540> so<00:23:56.169> the<00:23:56.290> cool<00:23:56.440> thing<00:23:56.650> is 00:23:56.669 --> 00:23:56.679 align:start position:0% library using VLS so the cool thing is 00:23:56.679 --> 00:23:58.799 align:start position:0% library using VLS so the cool thing is that<00:23:56.799> in<00:23:57.100> previous<00:23:57.280> iterations<00:23:57.549> of<00:23:58.150> kind<00:23:58.720> of 00:23:58.799 --> 00:23:58.809 align:start position:0% that in previous iterations of kind of 00:23:58.809 --> 00:24:01.400 align:start position:0% that in previous iterations of kind of the<00:23:58.870> etherium<00:23:59.260> 2.0<00:24:00.010> spec<00:24:00.309> there<00:24:01.000> are<00:24:01.120> a<00:24:01.150> lot<00:24:01.299> of 00:24:01.400 --> 00:24:01.410 align:start position:0% the etherium 2.0 spec there are a lot of 00:24:01.410 --> 00:24:03.690 align:start position:0% the etherium 2.0 spec there are a lot of questions<00:24:02.410> around<00:24:02.650> how<00:24:02.890> can<00:24:02.950> we<00:24:03.130> do<00:24:03.250> efficient 00:24:03.690 --> 00:24:03.700 align:start position:0% questions around how can we do efficient 00:24:03.700 --> 00:24:06.000 align:start position:0% questions around how can we do efficient signature<00:24:04.059> aggregation<00:24:04.660> we<00:24:05.620> have<00:24:05.740> a<00:24:05.770> lot<00:24:05.980> of 00:24:06.000 --> 00:24:06.010 align:start position:0% signature aggregation we have a lot of 00:24:06.010 --> 00:24:08.039 align:start position:0% signature aggregation we have a lot of validators<00:24:06.549> voting<00:24:06.910> on<00:24:07.030> blocks<00:24:07.299> how<00:24:07.720> can<00:24:07.900> we 00:24:08.039 --> 00:24:08.049 align:start position:0% validators voting on blocks how can we 00:24:08.049 --> 00:24:10.380 align:start position:0% validators voting on blocks how can we get<00:24:08.380> them<00:24:08.650> basically<00:24:09.490> doing<00:24:09.700> their<00:24:09.880> job<00:24:10.059> in<00:24:10.299> a 00:24:10.380 --> 00:24:10.390 align:start position:0% get them basically doing their job in a 00:24:10.390 --> 00:24:11.760 align:start position:0% get them basically doing their job in a way<00:24:10.510> that<00:24:10.660> we<00:24:11.260> don't<00:24:11.320> have<00:24:11.500> to<00:24:11.590> worry<00:24:11.740> about 00:24:11.760 --> 00:24:11.770 align:start position:0% way that we don't have to worry about 00:24:11.770 --> 00:24:13.650 align:start position:0% way that we don't have to worry about the<00:24:12.010> bottleneck<00:24:12.400> of<00:24:12.540> verification<00:24:13.540> I'll 00:24:13.650 --> 00:24:13.660 align:start position:0% the bottleneck of verification I'll 00:24:13.660 --> 00:24:15.810 align:start position:0% the bottleneck of verification I'll check<00:24:13.870> so<00:24:14.530> in<00:24:14.650> this<00:24:14.740> case<00:24:14.950> we<00:24:15.429> get<00:24:15.549> the 00:24:15.810 --> 00:24:15.820 align:start position:0% check so in this case we get the 00:24:15.820 --> 00:24:16.560 align:start position:0% check so in this case we get the wonderful 00:24:16.560 --> 00:24:16.570 align:start position:0% wonderful 00:24:16.570 --> 00:24:20.340 align:start position:0% wonderful BLS<00:24:16.929> signature<00:24:17.799> aggregation<00:24:18.730> tool<00:24:19.350> aside 00:24:20.340 --> 00:24:20.350 align:start position:0% BLS signature aggregation tool aside 00:24:20.350 --> 00:24:21.930 align:start position:0% BLS signature aggregation tool aside from<00:24:20.440> that<00:24:20.500> the<00:24:21.190> beacon<00:24:21.460> note<00:24:21.549> serves<00:24:21.790> as<00:24:21.910> a 00:24:21.930 --> 00:24:21.940 align:start position:0% from that the beacon note serves as a 00:24:21.940 --> 00:24:23.430 align:start position:0% from that the beacon note serves as a source<00:24:22.210> of<00:24:22.390> shards<00:24:22.720> shuffling<00:24:23.140> and<00:24:23.290> cross 00:24:23.430 --> 00:24:23.440 align:start position:0% source of shards shuffling and cross 00:24:23.440 --> 00:24:25.890 align:start position:0% source of shards shuffling and cross shard<00:24:23.710> communication<00:24:24.309> so<00:24:25.240> on<00:24:25.450> the<00:24:25.570> con<00:24:25.750> the 00:24:25.890 --> 00:24:25.900 align:start position:0% shard communication so on the con the 00:24:25.900 --> 00:24:27.720 align:start position:0% shard communication so on the con the beacon<00:24:26.169> chain<00:24:26.380> spec<00:24:26.980> right<00:24:27.220> now<00:24:27.340> that<00:24:27.520> shadow 00:24:27.720 --> 00:24:27.730 align:start position:0% beacon chain spec right now that shadow 00:24:27.730 --> 00:24:29.370 align:start position:0% beacon chain spec right now that shadow I<00:24:27.790> pointed<00:24:28.120> out<00:24:28.210> in<00:24:28.360> the<00:24:28.690> official<00:24:29.020> etherium 00:24:29.370 --> 00:24:29.380 align:start position:0% I pointed out in the official etherium 00:24:29.380 --> 00:24:30.450 align:start position:0% I pointed out in the official etherium repo 00:24:30.450 --> 00:24:30.460 align:start position:0% repo 00:24:30.460 --> 00:24:32.610 align:start position:0% repo there<00:24:31.060> is<00:24:31.180> essentially<00:24:31.660> not<00:24:31.990> enough<00:24:32.290> mention 00:24:32.610 --> 00:24:32.620 align:start position:0% there is essentially not enough mention 00:24:32.620 --> 00:24:34.170 align:start position:0% there is essentially not enough mention about<00:24:32.740> cross<00:24:32.980> communication<00:24:33.520> that<00:24:33.790> is<00:24:33.910> a<00:24:33.940> very 00:24:34.170 --> 00:24:34.180 align:start position:0% about cross communication that is a very 00:24:34.180 --> 00:24:36.330 align:start position:0% about cross communication that is a very active<00:24:34.480> area<00:24:34.600> of<00:24:34.780> research<00:24:34.920> but<00:24:35.920> the<00:24:36.040> beacon 00:24:36.330 --> 00:24:36.340 align:start position:0% active area of research but the beacon 00:24:36.340 --> 00:24:37.710 align:start position:0% active area of research but the beacon nodes<00:24:36.550> are<00:24:36.850> finality<00:24:37.330> and<00:24:37.450> the<00:24:37.570> way 00:24:37.710 --> 00:24:37.720 align:start position:0% nodes are finality and the way 00:24:37.720 --> 00:24:39.600 align:start position:0% nodes are finality and the way committees<00:24:38.440> are<00:24:38.590> handled<00:24:38.980> gives<00:24:39.160> us<00:24:39.280> a<00:24:39.310> strong 00:24:39.600 --> 00:24:39.610 align:start position:0% committees are handled gives us a strong 00:24:39.610 --> 00:24:41.580 align:start position:0% committees are handled gives us a strong way<00:24:39.850> to<00:24:39.880> kind<00:24:40.240> of<00:24:40.300> begin<00:24:40.450> on<00:24:41.140> an<00:24:41.320> approach 00:24:41.580 --> 00:24:41.590 align:start position:0% way to kind of begin on an approach 00:24:41.590 --> 00:24:44.610 align:start position:0% way to kind of begin on an approach towards<00:24:41.800> that<00:24:42.690> another<00:24:43.690> thing<00:24:43.930> is<00:24:44.110> we're 00:24:44.610 --> 00:24:44.620 align:start position:0% towards that another thing is we're 00:24:44.620 --> 00:24:46.110 align:start position:0% towards that another thing is we're going<00:24:44.650> to<00:24:44.800> be<00:24:44.890> building<00:24:45.190> a<00:24:45.310> common<00:24:45.670> client 00:24:46.110 --> 00:24:46.120 align:start position:0% going to be building a common client 00:24:46.120 --> 00:24:48.330 align:start position:0% going to be building a common client testing<00:24:47.080> framework<00:24:47.410> so<00:24:47.830> we<00:24:47.860> want<00:24:48.010> to<00:24:48.100> make<00:24:48.190> it 00:24:48.330 --> 00:24:48.340 align:start position:0% testing framework so we want to make it 00:24:48.340 --> 00:24:49.770 align:start position:0% testing framework so we want to make it so<00:24:48.460> we<00:24:48.610> have<00:24:48.700> a<00:24:48.730> very<00:24:48.910> simple<00:24:49.120> format<00:24:49.540> in<00:24:49.690> the 00:24:49.770 --> 00:24:49.780 align:start position:0% so we have a very simple format in the 00:24:49.780 --> 00:24:51.840 align:start position:0% so we have a very simple format in the ammo<00:24:49.930> where<00:24:50.590> you<00:24:50.650> can<00:24:50.800> specify<00:24:51.010> like<00:24:51.370> hey<00:24:51.550> you 00:24:51.840 --> 00:24:51.850 align:start position:0% ammo where you can specify like hey you 00:24:51.850 --> 00:24:54.030 align:start position:0% ammo where you can specify like hey you know<00:24:51.970> I<00:24:52.240> want<00:24:52.540> I<00:24:52.810> want<00:24:53.410> it<00:24:53.500> I<00:24:53.590> want<00:24:53.620> to<00:24:53.860> specify 00:24:54.030 --> 00:24:54.040 align:start position:0% know I want I want it I want to specify 00:24:54.040 --> 00:24:55.980 align:start position:0% know I want I want it I want to specify a<00:24:54.310> test<00:24:54.790> for<00:24:55.000> a<00:24:55.060> fork<00:24:55.270> choice<00:24:55.480> in<00:24:55.720> the<00:24:55.780> theorem 00:24:55.980 --> 00:24:55.990 align:start position:0% a test for a fork choice in the theorem 00:24:55.990 --> 00:24:58.110 align:start position:0% a test for a fork choice in the theorem 2.0<00:24:56.350> I<00:24:56.590> want<00:24:57.220> to<00:24:57.280> specify<00:24:57.610> what<00:24:57.760> happen<00:24:57.970> with<00:24:58.060> a 00:24:58.110 --> 00:24:58.120 align:start position:0% 2.0 I want to specify what happen with a 00:24:58.120 --> 00:24:59.940 align:start position:0% 2.0 I want to specify what happen with a signature<00:24:58.630> aggregation<00:24:59.260> I<00:24:59.560> want<00:24:59.800> to<00:24:59.860> know 00:24:59.940 --> 00:24:59.950 align:start position:0% signature aggregation I want to know 00:24:59.950 --> 00:25:02.190 align:start position:0% signature aggregation I want to know exactly<00:25:00.310> you<00:25:00.820> know<00:25:00.940> like<00:25:01.330> what<00:25:01.930> this<00:25:02.080> would 00:25:02.190 --> 00:25:02.200 align:start position:0% exactly you know like what this would 00:25:02.200 --> 00:25:03.570 align:start position:0% exactly you know like what this would look<00:25:02.230> like<00:25:02.320> what<00:25:02.530> the<00:25:02.590> result<00:25:02.860> would<00:25:02.980> be<00:25:03.010> and 00:25:03.570 --> 00:25:03.580 align:start position:0% look like what the result would be and 00:25:03.580 --> 00:25:05.850 align:start position:0% look like what the result would be and have<00:25:04.000> a<00:25:04.030> comprehensive<00:25:04.600> test<00:25:04.810> suite<00:25:04.990> so<00:25:05.620> that 00:25:05.850 --> 00:25:05.860 align:start position:0% have a comprehensive test suite so that 00:25:05.860 --> 00:25:07.830 align:start position:0% have a comprehensive test suite so that even<00:25:06.730> if<00:25:07.000> people<00:25:07.030> are<00:25:07.330> not<00:25:07.420> familiar<00:25:07.600> with 00:25:07.830 --> 00:25:07.840 align:start position:0% even if people are not familiar with 00:25:07.840 --> 00:25:09.900 align:start position:0% even if people are not familiar with their<00:25:07.990> client<00:25:08.350> and<00:25:09.160> are<00:25:09.430> coming<00:25:09.640> from<00:25:09.700> other 00:25:09.900 --> 00:25:09.910 align:start position:0% their client and are coming from other 00:25:09.910 --> 00:25:11.130 align:start position:0% their client and are coming from other client<00:25:10.300> teams<00:25:10.450> they<00:25:10.570> can<00:25:10.690> come<00:25:10.840> in<00:25:10.990> and 00:25:11.130 --> 00:25:11.140 align:start position:0% client teams they can come in and 00:25:11.140 --> 00:25:15.270 align:start position:0% client teams they can come in and testings<00:25:11.800> robustly<00:25:12.190> end-to-end<00:25:13.620> so<00:25:14.620> we<00:25:15.070> did<00:25:15.250> a 00:25:15.270 --> 00:25:15.280 align:start position:0% testings robustly end-to-end so we did a 00:25:15.280 --> 00:25:18.570 align:start position:0% testings robustly end-to-end so we did a POC<00:25:15.810> kind<00:25:16.810> of<00:25:16.960> early<00:25:17.560> October<00:25:18.010> in<00:25:18.160> which<00:25:18.400> we 00:25:18.570 --> 00:25:18.580 align:start position:0% POC kind of early October in which we 00:25:18.580 --> 00:25:20.640 align:start position:0% POC kind of early October in which we essentially<00:25:18.970> had<00:25:19.210> our<00:25:19.360> beacon<00:25:19.660> node<00:25:19.870> on<00:25:20.260> the 00:25:20.640 --> 00:25:20.650 align:start position:0% essentially had our beacon node on the 00:25:20.650 --> 00:25:21.960 align:start position:0% essentially had our beacon node on the left<00:25:20.860> and<00:25:21.130> on<00:25:21.190> the<00:25:21.220> right<00:25:21.430> hand<00:25:21.520> side<00:25:21.730> you<00:25:21.850> guys 00:25:21.960 --> 00:25:21.970 align:start position:0% left and on the right hand side you guys 00:25:21.970 --> 00:25:24.090 align:start position:0% left and on the right hand side you guys can<00:25:22.150> see<00:25:22.330> validator<00:25:22.810> clients<00:25:23.200> that<00:25:24.010> are 00:25:24.090 --> 00:25:24.100 align:start position:0% can see validator clients that are 00:25:24.100 --> 00:25:26.850 align:start position:0% can see validator clients that are connected<00:25:24.580> receiving<00:25:25.270> streams<00:25:25.600> of<00:25:25.870> ERP<00:25:26.620> see 00:25:26.850 --> 00:25:26.860 align:start position:0% connected receiving streams of ERP see 00:25:26.860 --> 00:25:28.770 align:start position:0% connected receiving streams of ERP see responses<00:25:27.250> getting<00:25:27.820> shuffled<00:25:28.060> into<00:25:28.480> shards 00:25:28.770 --> 00:25:28.780 align:start position:0% responses getting shuffled into shards 00:25:28.780 --> 00:25:30.660 align:start position:0% responses getting shuffled into shards and<00:25:29.110> performing<00:25:29.860> the<00:25:29.920> responsibility<00:25:30.640> of 00:25:30.660 --> 00:25:30.670 align:start position:0% and performing the responsibility of 00:25:30.670 --> 00:25:32.250 align:start position:0% and performing the responsibility of basically<00:25:31.180> a<00:25:31.240> testing<00:25:31.660> and<00:25:31.750> proposing<00:25:32.170> to 00:25:32.250 --> 00:25:32.260 align:start position:0% basically a testing and proposing to 00:25:32.260 --> 00:25:35.010 align:start position:0% basically a testing and proposing to shard<00:25:32.500> blocks<00:25:32.740> and<00:25:33.540> you<00:25:34.540> know<00:25:34.630> it<00:25:34.720> was<00:25:34.810> just 00:25:35.010 --> 00:25:35.020 align:start position:0% shard blocks and you know it was just 00:25:35.020 --> 00:25:37.380 align:start position:0% shard blocks and you know it was just really<00:25:35.260> interesting<00:25:35.620> to<00:25:35.650> see<00:25:35.740> how<00:25:36.390> this 00:25:37.380 --> 00:25:37.390 align:start position:0% really interesting to see how this 00:25:37.390 --> 00:25:38.820 align:start position:0% really interesting to see how this implementation<00:25:37.870> efforts<00:25:38.320> give<00:25:38.530> us<00:25:38.620> a<00:25:38.650> really 00:25:38.820 --> 00:25:38.830 align:start position:0% implementation efforts give us a really 00:25:38.830 --> 00:25:40.910 align:start position:0% implementation efforts give us a really good<00:25:39.010> idea<00:25:39.070> of<00:25:39.520> kind<00:25:39.730> of<00:25:39.820> where<00:25:39.910> the<00:25:40.060> spec<00:25:40.330> is<00:25:40.630> a 00:25:40.910 --> 00:25:40.920 align:start position:0% good idea of kind of where the spec is a 00:25:40.920 --> 00:25:43.260 align:start position:0% good idea of kind of where the spec is a lot<00:25:41.920> of<00:25:42.040> a<00:25:42.100> specification<00:25:42.490> right<00:25:42.910> now<00:25:43.060> is 00:25:43.260 --> 00:25:43.270 align:start position:0% lot of a specification right now is 00:25:43.270 --> 00:25:44.910 align:start position:0% lot of a specification right now is mostly<00:25:43.720> like<00:25:43.960> oh<00:25:44.170> we<00:25:44.470> should<00:25:44.650> do<00:25:44.710> block 00:25:44.910 --> 00:25:44.920 align:start position:0% mostly like oh we should do block 00:25:44.920 --> 00:25:47.340 align:start position:0% mostly like oh we should do block processing<00:25:45.430> we<00:25:45.550> should<00:25:45.730> be<00:25:45.790> for<00:25:46.000> chips<00:25:46.350> but 00:25:47.340 --> 00:25:47.350 align:start position:0% processing we should be for chips but 00:25:47.350 --> 00:25:49.200 align:start position:0% processing we should be for chips but nobody<00:25:47.770> really<00:25:48.010> tells<00:25:48.220> you<00:25:48.400> like<00:25:48.670> okay<00:25:48.970> where 00:25:49.200 --> 00:25:49.210 align:start position:0% nobody really tells you like okay where 00:25:49.210 --> 00:25:51.540 align:start position:0% nobody really tells you like okay where should<00:25:49.420> this<00:25:49.570> live<00:25:49.950> who<00:25:50.950> should<00:25:51.190> be<00:25:51.280> doing 00:25:51.540 --> 00:25:51.550 align:start position:0% should this live who should be doing 00:25:51.550 --> 00:25:53.460 align:start position:0% should this live who should be doing this<00:25:51.700> how<00:25:52.240> I<00:25:52.270> should<00:25:52.570> validate<00:25:52.840> or<00:25:53.140> clients 00:25:53.460 --> 00:25:53.470 align:start position:0% this how I should validate or clients 00:25:53.470 --> 00:25:55.620 align:start position:0% this how I should validate or clients interact<00:25:53.710> so<00:25:54.700> by<00:25:55.090> being<00:25:55.300> a<00:25:55.450> very 00:25:55.620 --> 00:25:55.630 align:start position:0% interact so by being a very 00:25:55.630 --> 00:25:57.660 align:start position:0% interact so by being a very bleeding-edge<00:25:56.230> focus<00:25:56.830> implementation<00:25:57.460> team 00:25:57.660 --> 00:25:57.670 align:start position:0% bleeding-edge focus implementation team 00:25:57.670 --> 00:25:59.130 align:start position:0% bleeding-edge focus implementation team we<00:25:58.360> get<00:25:58.480> to<00:25:58.600> answer<00:25:58.870> a<00:25:58.900> lot<00:25:58.960> of<00:25:59.050> these 00:25:59.130 --> 00:25:59.140 align:start position:0% we get to answer a lot of these 00:25:59.140 --> 00:26:01.260 align:start position:0% we get to answer a lot of these questions<00:25:59.500> ourselves<00:25:59.650> and<00:26:00.250> kind<00:26:00.730> of<00:26:00.910> come<00:26:01.150> up 00:26:01.260 --> 00:26:01.270 align:start position:0% questions ourselves and kind of come up 00:26:01.270 --> 00:26:02.970 align:start position:0% questions ourselves and kind of come up with<00:26:01.450> designs<00:26:02.080> that<00:26:02.230> would<00:26:02.410> make<00:26:02.560> sense<00:26:02.740> in 00:26:02.970 --> 00:26:02.980 align:start position:0% with designs that would make sense in 00:26:02.980 --> 00:26:05.700 align:start position:0% with designs that would make sense in light<00:26:03.100> of<00:26:03.130> the<00:26:03.280> spec<00:26:03.550> and<00:26:03.730> oftentimes<00:26:04.720> come<00:26:05.560> up 00:26:05.700 --> 00:26:05.710 align:start position:0% light of the spec and oftentimes come up 00:26:05.710 --> 00:26:07.110 align:start position:0% light of the spec and oftentimes come up and<00:26:05.860> be<00:26:05.980> like<00:26:06.130> hey<00:26:06.280> there<00:26:06.460> might<00:26:06.610> be<00:26:06.640> a<00:26:06.730> bug<00:26:06.970> in 00:26:07.110 --> 00:26:07.120 align:start position:0% and be like hey there might be a bug in 00:26:07.120 --> 00:26:09.750 align:start position:0% and be like hey there might be a bug in the<00:26:07.210> spec<00:26:07.500> and<00:26:08.500> that's<00:26:09.100> that's<00:26:09.460> I<00:26:09.550> think<00:26:09.610> been 00:26:09.750 --> 00:26:09.760 align:start position:0% the spec and that's that's I think been 00:26:09.760 --> 00:26:11.010 align:start position:0% the spec and that's that's I think been really<00:26:10.180> a<00:26:10.210> really<00:26:10.600> amazing<00:26:10.930> experience 00:26:11.010 --> 00:26:11.020 align:start position:0% really a really amazing experience 00:26:11.020 --> 00:26:12.600 align:start position:0% really a really amazing experience working<00:26:11.530> with<00:26:11.740> the<00:26:11.800> etherium<00:26:12.100> research<00:26:12.340> team 00:26:12.600 --> 00:26:12.610 align:start position:0% working with the etherium research team 00:26:12.610 --> 00:26:15.690 align:start position:0% working with the etherium research team on<00:26:12.790> this<00:26:13.320> so<00:26:14.320> what<00:26:14.560> are<00:26:14.680> the<00:26:14.740> next<00:26:14.890> steps<00:26:15.010> for 00:26:15.690 --> 00:26:15.700 align:start position:0% on this so what are the next steps for 00:26:15.700 --> 00:26:18.030 align:start position:0% on this so what are the next steps for us<00:26:15.960> prismatic<00:26:16.960> labs<00:26:17.140> there's<00:26:17.620> still<00:26:17.800> a<00:26:17.830> lot<00:26:18.010> of 00:26:18.030 --> 00:26:18.040 align:start position:0% us prismatic labs there's still a lot of 00:26:18.040 --> 00:26:20.370 align:start position:0% us prismatic labs there's still a lot of work<00:26:18.220> to<00:26:18.370> do<00:26:18.520> on<00:26:18.730> the<00:26:18.880> beacon<00:26:19.120> chain<00:26:19.330> spec<00:26:19.600> part 00:26:20.370 --> 00:26:20.380 align:start position:0% work to do on the beacon chain spec part 00:26:20.380 --> 00:26:22.320 align:start position:0% work to do on the beacon chain spec part of<00:26:20.470> it<00:26:20.590> is<00:26:20.710> due<00:26:20.830> to<00:26:20.860> research<00:26:21.250> but<00:26:22.030> one<00:26:22.150> of<00:26:22.210> the 00:26:22.320 --> 00:26:22.330 align:start position:0% of it is due to research but one of the 00:26:22.330 --> 00:26:23.490 align:start position:0% of it is due to research but one of the things<00:26:22.570> I<00:26:22.660> like<00:26:22.810> to<00:26:22.840> say<00:26:22.960> is<00:26:23.260> that<00:26:23.410> the 00:26:23.490 --> 00:26:23.500 align:start position:0% things I like to say is that the 00:26:23.500 --> 00:26:26.400 align:start position:0% things I like to say is that the research<00:26:23.860> at<00:26:24.010> this<00:26:24.130> point<00:26:24.370> is<00:26:24.630> is<00:26:25.630> most<00:26:26.140> of<00:26:26.320> the 00:26:26.400 --> 00:26:26.410 align:start position:0% research at this point is is most of the 00:26:26.410 --> 00:26:29.970 align:start position:0% research at this point is is most of the core<00:26:26.620> core<00:26:27.460> kind<00:26:28.000> of<00:26:28.410> items<00:26:29.410> will<00:26:29.620> remain<00:26:29.860> the 00:26:29.970 --> 00:26:29.980 align:start position:0% core core kind of items will remain the 00:26:29.980 --> 00:26:32.190 align:start position:0% core core kind of items will remain the same<00:26:30.030> what's<00:26:31.030> really<00:26:31.300> lacking<00:26:31.600> is<00:26:31.930> kind<00:26:32.140> of 00:26:32.190 --> 00:26:32.200 align:start position:0% same what's really lacking is kind of 00:26:32.200 --> 00:26:33.810 align:start position:0% same what's really lacking is kind of logistics<00:26:32.680> around<00:26:32.830> exactly<00:26:33.430> validator 00:26:33.810 --> 00:26:33.820 align:start position:0% logistics around exactly validator 00:26:33.820 --> 00:26:35.700 align:start position:0% logistics around exactly validator client<00:26:34.120> interactions<00:26:34.720> how<00:26:35.320> that's<00:26:35.470> going<00:26:35.620> to 00:26:35.700 --> 00:26:35.710 align:start position:0% client interactions how that's going to 00:26:35.710 --> 00:26:38.640 align:start position:0% client interactions how that's going to work<00:26:35.770> and<00:26:36.040> such<00:26:36.870> working<00:26:37.870> on<00:26:37.990> benchmarks<00:26:38.500> and 00:26:38.640 --> 00:26:38.650 align:start position:0% work and such working on benchmarks and 00:26:38.650 --> 00:26:40.590 align:start position:0% work and such working on benchmarks and metering<00:26:38.920> extensively<00:26:39.580> for<00:26:39.850> applications<00:26:40.420> so 00:26:40.590 --> 00:26:40.600 align:start position:0% metering extensively for applications so 00:26:40.600 --> 00:26:42.180 align:start position:0% metering extensively for applications so we<00:26:40.630> want<00:26:40.840> to<00:26:40.900> make<00:26:40.990> sure<00:26:41.020> we<00:26:41.290> understand<00:26:41.680> if 00:26:42.180 --> 00:26:42.190 align:start position:0% we want to make sure we understand if 00:26:42.190 --> 00:26:43.350 align:start position:0% we want to make sure we understand if our<00:26:42.340> signature<00:26:42.700> aggregation<00:26:43.120> is<00:26:43.210> done 00:26:43.350 --> 00:26:43.360 align:start position:0% our signature aggregation is done 00:26:43.360 --> 00:26:44.190 align:start position:0% our signature aggregation is done properly 00:26:44.190 --> 00:26:44.200 align:start position:0% properly 00:26:44.200 --> 00:26:46.350 align:start position:0% properly you<00:26:44.710> know<00:26:44.799> how<00:26:44.980> many<00:26:45.429> validated<00:26:45.940> clients<00:26:46.240> can 00:26:46.350 --> 00:26:46.360 align:start position:0% you know how many validated clients can 00:26:46.360 --> 00:26:48.720 align:start position:0% you know how many validated clients can we<00:26:46.450> realistically<00:26:46.690> have<00:26:47.250> attaches<00:26:48.250> G<00:26:48.370> RPC 00:26:48.720 --> 00:26:48.730 align:start position:0% we realistically have attaches G RPC 00:26:48.730 --> 00:26:52.139 align:start position:0% we realistically have attaches G RPC processes<00:26:49.299> as<00:26:50.080> well<00:26:50.950> as<00:26:51.130> work<00:26:51.309> on<00:26:51.429> sharp<00:26:51.730> p2p 00:26:52.139 --> 00:26:52.149 align:start position:0% processes as well as work on sharp p2p 00:26:52.149 --> 00:26:54.210 align:start position:0% processes as well as work on sharp p2p which<00:26:52.389> is<00:26:52.510> a<00:26:52.539> very<00:26:52.809> big<00:26:53.200> kind<00:26:53.710> of<00:26:53.889> umbrella 00:26:54.210 --> 00:26:54.220 align:start position:0% which is a very big kind of umbrella 00:26:54.220 --> 00:26:57.960 align:start position:0% which is a very big kind of umbrella term<00:26:54.610> all<00:26:55.120> right<00:26:55.409> so<00:26:56.409> our<00:26:56.769> next<00:26:56.970> major 00:26:57.960 --> 00:26:57.970 align:start position:0% term all right so our next major 00:26:57.970 --> 00:27:00.210 align:start position:0% term all right so our next major milestone<00:26:58.179> is<00:26:59.049> something<00:26:59.500> that<00:26:59.649> I'm<00:26:59.799> really 00:27:00.210 --> 00:27:00.220 align:start position:0% milestone is something that I'm really 00:27:00.220 --> 00:27:03.149 align:start position:0% milestone is something that I'm really happy<00:27:00.399> to<00:27:00.669> kind<00:27:00.850> of<00:27:00.880> announce<00:27:01.649> so<00:27:02.649> we<00:27:02.860> will<00:27:03.039> be 00:27:03.149 --> 00:27:03.159 align:start position:0% happy to kind of announce so we will be 00:27:03.159 --> 00:27:05.250 align:start position:0% happy to kind of announce so we will be doing<00:27:03.309> a<00:27:03.580> test<00:27:03.909> net<00:27:04.059> cluster<00:27:04.419> of<00:27:04.630> beacon<00:27:05.049> nodes 00:27:05.250 --> 00:27:05.260 align:start position:0% doing a test net cluster of beacon nodes 00:27:05.260 --> 00:27:07.409 align:start position:0% doing a test net cluster of beacon nodes and<00:27:05.470> validators<00:27:06.010> and<00:27:06.250> that's<00:27:07.059> something<00:27:07.269> that 00:27:07.409 --> 00:27:07.419 align:start position:0% and validators and that's something that 00:27:07.419 --> 00:27:09.330 align:start position:0% and validators and that's something that you<00:27:07.690> know<00:27:07.779> we<00:27:08.080> we<00:27:08.620> aim<00:27:08.769> to<00:27:08.799> deal<00:27:09.100> with<00:27:09.250> the 00:27:09.330 --> 00:27:09.340 align:start position:0% you know we we aim to deal with the 00:27:09.340 --> 00:27:10.769 align:start position:0% you know we we aim to deal with the other<00:27:09.370> client<00:27:09.820> implementation<00:27:10.389> teams<00:27:10.600> as 00:27:10.769 --> 00:27:10.779 align:start position:0% other client implementation teams as 00:27:10.779 --> 00:27:13.169 align:start position:0% other client implementation teams as well<00:27:11.100> but<00:27:12.100> we<00:27:12.190> want<00:27:12.279> to<00:27:12.399> make<00:27:12.519> it<00:27:12.700> so<00:27:12.880> we<00:27:13.029> have<00:27:13.149> a 00:27:13.169 --> 00:27:13.179 align:start position:0% well but we want to make it so we have a 00:27:13.179 --> 00:27:14.549 align:start position:0% well but we want to make it so we have a very<00:27:13.389> simple<00:27:13.720> system<00:27:13.899> where<00:27:14.169> you<00:27:14.289> guys<00:27:14.409> can 00:27:14.549 --> 00:27:14.559 align:start position:0% very simple system where you guys can 00:27:14.559 --> 00:27:17.460 align:start position:0% very simple system where you guys can obtain<00:27:14.860> faucet<00:27:15.190> eath<00:27:15.539> can<00:27:16.539> basically<00:27:16.750> deposit 00:27:17.460 --> 00:27:17.470 align:start position:0% obtain faucet eath can basically deposit 00:27:17.470 --> 00:27:19.440 align:start position:0% obtain faucet eath can basically deposit your<00:27:17.590> eath<00:27:17.769> to<00:27:17.950> become<00:27:18.220> validators<00:27:18.789> get<00:27:19.299> on 00:27:19.440 --> 00:27:19.450 align:start position:0% your eath to become validators get on 00:27:19.450 --> 00:27:21.000 align:start position:0% your eath to become validators get on board<00:27:19.690> at<00:27:19.840> as<00:27:19.929> validators<00:27:20.409> into<00:27:20.649> the<00:27:20.740> beacon 00:27:21.000 --> 00:27:21.010 align:start position:0% board at as validators into the beacon 00:27:21.010 --> 00:27:23.220 align:start position:0% board at as validators into the beacon chain<00:27:21.190> kind<00:27:21.460> of<00:27:21.610> 2.0<00:27:22.000> and<00:27:22.240> can<00:27:23.049> start 00:27:23.220 --> 00:27:23.230 align:start position:0% chain kind of 2.0 and can start 00:27:23.230 --> 00:27:25.039 align:start position:0% chain kind of 2.0 and can start performing<00:27:23.649> your<00:27:23.740> responsibilities<00:27:24.460> and 00:27:25.039 --> 00:27:25.049 align:start position:0% performing your responsibilities and 00:27:25.049 --> 00:27:27.629 align:start position:0% performing your responsibilities and that<00:27:26.049> it's<00:27:26.679> a<00:27:26.740> very<00:27:26.950> exciting<00:27:27.250> kind<00:27:27.519> of 00:27:27.629 --> 00:27:27.639 align:start position:0% that it's a very exciting kind of 00:27:27.639 --> 00:27:29.639 align:start position:0% that it's a very exciting kind of prospect<00:27:28.029> and<00:27:28.690> we<00:27:28.840> really<00:27:29.110> hope<00:27:29.289> that<00:27:29.380> you 00:27:29.639 --> 00:27:29.649 align:start position:0% prospect and we really hope that you 00:27:29.649 --> 00:27:30.960 align:start position:0% prospect and we really hope that you know<00:27:29.769> people<00:27:29.919> will<00:27:30.159> leverage<00:27:30.340> prism<00:27:30.789> to<00:27:30.880> the 00:27:30.960 --> 00:27:30.970 align:start position:0% know people will leverage prism to the 00:27:30.970 --> 00:27:32.940 align:start position:0% know people will leverage prism to the best<00:27:31.149> of<00:27:31.269> their<00:27:31.389> ability<00:27:31.750> and<00:27:31.899> understand<00:27:32.830> all 00:27:32.940 --> 00:27:32.950 align:start position:0% best of their ability and understand all 00:27:32.950 --> 00:27:34.950 align:start position:0% best of their ability and understand all the<00:27:33.010> tools<00:27:33.220> that<00:27:33.279> we<00:27:33.429> have<00:27:33.460> to<00:27:33.700> offer<00:27:33.820> and<00:27:34.630> of 00:27:34.950 --> 00:27:34.960 align:start position:0% the tools that we have to offer and of 00:27:34.960 --> 00:27:36.509 align:start position:0% the tools that we have to offer and of course<00:27:35.169> you<00:27:35.320> know<00:27:35.440> this<00:27:35.679> is<00:27:35.799> a<00:27:35.830> constant<00:27:36.340> you 00:27:36.509 --> 00:27:36.519 align:start position:0% course you know this is a constant you 00:27:36.519 --> 00:27:37.500 align:start position:0% course you know this is a constant you know<00:27:36.549> work<00:27:36.940> in<00:27:37.059> progress 00:27:37.500 --> 00:27:37.510 align:start position:0% know work in progress 00:27:37.510 --> 00:27:39.899 align:start position:0% know work in progress our<00:27:37.809> constantly<00:27:38.320> iterating<00:27:38.620> on<00:27:38.799> this<00:27:39.010> and 00:27:39.899 --> 00:27:39.909 align:start position:0% our constantly iterating on this and 00:27:39.909 --> 00:27:41.190 align:start position:0% our constantly iterating on this and we'll<00:27:40.059> have<00:27:40.179> a<00:27:40.210> lot<00:27:40.419> more<00:27:40.450> for<00:27:40.750> you<00:27:40.870> guys<00:27:41.019> in 00:27:41.190 --> 00:27:41.200 align:start position:0% we'll have a lot more for you guys in 00:27:41.200 --> 00:27:43.139 align:start position:0% we'll have a lot more for you guys in the<00:27:41.260> coming<00:27:41.559> months<00:27:41.769> so<00:27:41.950> staying<00:27:42.460> tuned<00:27:42.700> stay 00:27:43.139 --> 00:27:43.149 align:start position:0% the coming months so staying tuned stay 00:27:43.149 --> 00:27:48.820 align:start position:0% the coming months so staying tuned stay tuned<00:27:43.360> for<00:27:43.480> this 00:27:48.820 --> 00:27:48.830 align:start position:0% 00:27:48.830 --> 00:27:52.130 align:start position:0% yeah<00:27:50.040> so<00:27:50.190> some<00:27:50.460> learning<00:27:50.730> resources<00:27:51.140> there's 00:27:52.130 --> 00:27:52.140 align:start position:0% yeah so some learning resources there's 00:27:52.140 --> 00:27:53.450 align:start position:0% yeah so some learning resources there's a<00:27:52.230> lot<00:27:52.470> of<00:27:52.560> information<00:27:52.770> out<00:27:53.130> there<00:27:53.190> if<00:27:53.400> you 00:27:53.450 --> 00:27:53.460 align:start position:0% a lot of information out there if you 00:27:53.460 --> 00:27:55.630 align:start position:0% a lot of information out there if you guys<00:27:53.580> like<00:27:53.730> a<00:27:53.820> path<00:27:54.000> 2.0<00:27:54.450> now<00:27:54.630> called<00:27:55.020> serenity 00:27:55.630 --> 00:27:55.640 align:start position:0% guys like a path 2.0 now called serenity 00:27:55.640 --> 00:27:58.430 align:start position:0% guys like a path 2.0 now called serenity so<00:27:56.640> there's<00:27:57.000> an<00:27:57.150> F<00:27:57.270> 2.0<00:27:57.600> devs<00:27:57.840> handbook<00:27:58.230> if<00:27:58.350> you 00:27:58.430 --> 00:27:58.440 align:start position:0% so there's an F 2.0 devs handbook if you 00:27:58.440 --> 00:28:00.110 align:start position:0% so there's an F 2.0 devs handbook if you guys<00:27:58.530> don't<00:27:58.710> learn<00:27:58.800> more<00:27:58.980> about<00:27:59.070> this<00:27:59.370> we<00:28:00.000> have 00:28:00.110 --> 00:28:00.120 align:start position:0% guys don't learn more about this we have 00:28:00.120 --> 00:28:02.390 align:start position:0% guys don't learn more about this we have the<00:28:00.270> spec<00:28:00.600> we<00:28:00.870> have<00:28:01.170> a<00:28:01.200> repo<00:28:01.620> we<00:28:02.040> have<00:28:02.250> our 00:28:02.390 --> 00:28:02.400 align:start position:0% the spec we have a repo we have our 00:28:02.400 --> 00:28:04.340 align:start position:0% the spec we have a repo we have our bi-weekly<00:28:03.000> kind<00:28:03.240> of<00:28:03.330> implementer<00:28:03.810> calls<00:28:04.080> that 00:28:04.340 --> 00:28:04.350 align:start position:0% bi-weekly kind of implementer calls that 00:28:04.350 --> 00:28:05.690 align:start position:0% bi-weekly kind of implementer calls that are<00:28:04.470> kind<00:28:04.740> of<00:28:04.800> in<00:28:04.890> parallel<00:28:05.040> with<00:28:05.400> the<00:28:05.490> core 00:28:05.690 --> 00:28:05.700 align:start position:0% are kind of in parallel with the core 00:28:05.700 --> 00:28:08.990 align:start position:0% are kind of in parallel with the core devs<00:28:05.910> calls<00:28:06.620> and<00:28:07.620> overall<00:28:08.190> all<00:28:08.370> that<00:28:08.550> is<00:28:08.700> out 00:28:08.990 --> 00:28:09.000 align:start position:0% devs calls and overall all that is out 00:28:09.000 --> 00:28:09.230 align:start position:0% devs calls and overall all that is out there 00:28:09.230 --> 00:28:09.240 align:start position:0% there 00:28:09.240 --> 00:28:11.720 align:start position:0% there I<00:28:09.360> mean<00:28:09.690> earth<00:28:10.290> 2.0<00:28:11.250> went<00:28:11.430> from<00:28:11.580> being 00:28:11.720 --> 00:28:11.730 align:start position:0% I mean earth 2.0 went from being 00:28:11.730 --> 00:28:14.090 align:start position:0% I mean earth 2.0 went from being something<00:28:11.850> that<00:28:12.270> might<00:28:13.080> happen<00:28:13.260> maybe<00:28:13.860> it 00:28:14.090 --> 00:28:14.100 align:start position:0% something that might happen maybe it 00:28:14.100 --> 00:28:15.950 align:start position:0% something that might happen maybe it could<00:28:14.280> be<00:28:14.310> there<00:28:14.670> maybe<00:28:15.090> it's<00:28:15.330> feasible<00:28:15.780> to 00:28:15.950 --> 00:28:15.960 align:start position:0% could be there maybe it's feasible to 00:28:15.960 --> 00:28:18.110 align:start position:0% could be there maybe it's feasible to being<00:28:16.140> like<00:28:16.410> it's<00:28:16.740> gonna<00:28:16.950> happen<00:28:17.190> and<00:28:17.610> we're 00:28:18.110 --> 00:28:18.120 align:start position:0% being like it's gonna happen and we're 00:28:18.120 --> 00:28:21.170 align:start position:0% being like it's gonna happen and we're all<00:28:18.210> gonna<00:28:18.330> do<00:28:18.510> it<00:28:18.920> so<00:28:19.920> thank<00:28:20.760> you<00:28:20.880> everyone 00:28:21.170 --> 00:28:21.180 align:start position:0% all gonna do it so thank you everyone 00:28:21.180 --> 00:28:30.020 align:start position:0% all gonna do it so thank you everyone let's<00:28:21.510> do<00:28:21.600> some<00:28:21.720> questions<00:28:28.670> so<00:28:29.670> have<00:28:29.790> a<00:28:29.820> bit<00:28:29.940> of 00:28:30.020 --> 00:28:30.030 align:start position:0% let's do some questions so have a bit of 00:28:30.030 --> 00:28:58.870 align:start position:0% let's do some questions so have a bit of time<00:28:30.180> for<00:28:30.210> questions<00:28:30.620> yeah<00:28:37.520> yeah 00:28:58.870 --> 00:28:58.880 align:start position:0% 00:28:58.880 --> 00:29:01.420 align:start position:0% hi<00:28:59.270> my<00:28:59.960> name<00:29:00.080> is<00:29:00.140> Josh<00:29:00.380> I<00:29:00.770> got<00:29:01.220> a<00:29:01.250> quick 00:29:01.420 --> 00:29:01.430 align:start position:0% hi my name is Josh I got a quick 00:29:01.430 --> 00:29:04.780 align:start position:0% hi my name is Josh I got a quick question<00:29:01.490> yes<00:29:02.360> it<00:29:02.570> at<00:29:02.750> 2.0<00:29:03.470> and<00:29:03.740> charting<00:29:04.280> and 00:29:04.780 --> 00:29:04.790 align:start position:0% question yes it at 2.0 and charting and 00:29:04.790 --> 00:29:06.190 align:start position:0% question yes it at 2.0 and charting and beacon<00:29:05.240> chains<00:29:05.480> are<00:29:05.630> gonna<00:29:05.720> run<00:29:05.960> parallel 00:29:06.190 --> 00:29:06.200 align:start position:0% beacon chains are gonna run parallel 00:29:06.200 --> 00:29:09.250 align:start position:0% beacon chains are gonna run parallel with<00:29:06.440> proof-of-work<00:29:07.040> Shane<00:29:07.930> is<00:29:08.930> that<00:29:09.080> true 00:29:09.250 --> 00:29:09.260 align:start position:0% with proof-of-work Shane is that true 00:29:09.260 --> 00:29:11.530 align:start position:0% with proof-of-work Shane is that true yeah<00:29:09.920> so<00:29:10.160> essentially<00:29:10.520> 2.0<00:29:11.060> is<00:29:11.210> going<00:29:11.360> to<00:29:11.420> be<00:29:11.510> a 00:29:11.530 --> 00:29:11.540 align:start position:0% yeah so essentially 2.0 is going to be a 00:29:11.540 --> 00:29:13.240 align:start position:0% yeah so essentially 2.0 is going to be a new<00:29:11.720> chain<00:29:11.960> a<00:29:12.200> new<00:29:12.440> system<00:29:12.830> for<00:29:13.010> proof<00:29:13.190> of 00:29:13.240 --> 00:29:13.250 align:start position:0% new chain a new system for proof of 00:29:13.250 --> 00:29:15.940 align:start position:0% new chain a new system for proof of State<00:29:13.460> Caspar<00:29:13.880> f<00:29:13.940> of<00:29:14.060> G<00:29:14.240> where<00:29:15.140> you<00:29:15.680> have<00:29:15.830> the 00:29:15.940 --> 00:29:15.950 align:start position:0% State Caspar f of G where you have the 00:29:15.950 --> 00:29:18.280 align:start position:0% State Caspar f of G where you have the proof<00:29:16.880> work<00:29:17.060> chain<00:29:17.300> running<00:29:18.050> in<00:29:18.140> parallel 00:29:18.280 --> 00:29:18.290 align:start position:0% proof work chain running in parallel 00:29:18.290 --> 00:29:21.160 align:start position:0% proof work chain running in parallel with<00:29:18.800> it<00:29:18.940> the<00:29:19.940> reason<00:29:20.480> we<00:29:20.660> do<00:29:20.750> this<00:29:20.870> is<00:29:20.930> so<00:29:21.140> that 00:29:21.160 --> 00:29:21.170 align:start position:0% with it the reason we do this is so that 00:29:21.170 --> 00:29:22.510 align:start position:0% with it the reason we do this is so that we<00:29:21.380> make<00:29:21.530> it<00:29:21.650> easier<00:29:21.860> for<00:29:21.890> people<00:29:22.010> to<00:29:22.190> deposit 00:29:22.510 --> 00:29:22.520 align:start position:0% we make it easier for people to deposit 00:29:22.520 --> 00:29:25.300 align:start position:0% we make it easier for people to deposit eath<00:29:23.180> as<00:29:23.450> a<00:29:23.630> one-way<00:29:24.020> deposit<00:29:24.470> into<00:29:24.650> the<00:29:24.770> 2.0 00:29:25.300 --> 00:29:25.310 align:start position:0% eath as a one-way deposit into the 2.0 00:29:25.310 --> 00:29:27.280 align:start position:0% eath as a one-way deposit into the 2.0 chain<00:29:25.550> so<00:29:26.510> you<00:29:26.540> want<00:29:26.750> to<00:29:26.810> leverage<00:29:26.930> the<00:29:27.080> fact 00:29:27.280 --> 00:29:27.290 align:start position:0% chain so you want to leverage the fact 00:29:27.290 --> 00:29:28.720 align:start position:0% chain so you want to leverage the fact that<00:29:27.380> like<00:29:27.560> people<00:29:27.800> have<00:29:27.950> current<00:29:28.250> eath<00:29:28.400> they 00:29:28.720 --> 00:29:28.730 align:start position:0% that like people have current eath they 00:29:28.730 --> 00:29:29.860 align:start position:0% that like people have current eath they want<00:29:28.910> to<00:29:28.970> leverage<00:29:29.180> that<00:29:29.240> to<00:29:29.360> become<00:29:29.600> valid 00:29:29.860 --> 00:29:29.870 align:start position:0% want to leverage that to become valid 00:29:29.870 --> 00:29:31.270 align:start position:0% want to leverage that to become valid leaders<00:29:30.110> so<00:29:30.350> that's<00:29:30.500> kind<00:29:30.680> of<00:29:30.710> why<00:29:30.800> we're<00:29:30.980> kind 00:29:31.270 --> 00:29:31.280 align:start position:0% leaders so that's kind of why we're kind 00:29:31.280 --> 00:29:32.890 align:start position:0% leaders so that's kind of why we're kind of<00:29:31.400> synchronizing<00:29:31.940> the<00:29:32.120> two<00:29:32.300> at<00:29:32.600> the<00:29:32.690> moment 00:29:32.890 --> 00:29:32.900 align:start position:0% of synchronizing the two at the moment 00:29:32.900 --> 00:29:35.740 align:start position:0% of synchronizing the two at the moment okay<00:29:33.410> do<00:29:33.950> you<00:29:34.040> foresee<00:29:34.580> the<00:29:35.300> proof<00:29:35.480> of<00:29:35.600> work 00:29:35.740 --> 00:29:35.750 align:start position:0% okay do you foresee the proof of work 00:29:35.750 --> 00:29:39.160 align:start position:0% okay do you foresee the proof of work chain<00:29:36.080> being<00:29:36.410> deprecated<00:29:37.280> right<00:29:38.150> now<00:29:38.300> yes<00:29:38.840> I 00:29:39.160 --> 00:29:39.170 align:start position:0% chain being deprecated right now yes I 00:29:39.170 --> 00:29:40.450 align:start position:0% chain being deprecated right now yes I foresee<00:29:39.560> that<00:29:39.590> so<00:29:39.890> the<00:29:39.980> way<00:29:40.070> we're<00:29:40.160> gonna<00:29:40.220> do 00:29:40.450 --> 00:29:40.460 align:start position:0% foresee that so the way we're gonna do 00:29:40.460 --> 00:29:41.590 align:start position:0% foresee that so the way we're gonna do that<00:29:40.490> is<00:29:40.730> probably<00:29:40.850> going<00:29:41.150> to<00:29:41.210> migrate<00:29:41.360> the 00:29:41.590 --> 00:29:41.600 align:start position:0% that is probably going to migrate the 00:29:41.600 --> 00:29:44.260 align:start position:0% that is probably going to migrate the entire<00:29:41.870> state<00:29:42.250> of<00:29:43.250> the<00:29:43.550> current<00:29:43.700> Provo<00:29:44.090> chain 00:29:44.260 --> 00:29:44.270 align:start position:0% entire state of the current Provo chain 00:29:44.270 --> 00:29:46.390 align:start position:0% entire state of the current Provo chain into<00:29:44.510> a<00:29:44.540> contract<00:29:45.110> on<00:29:45.320> a<00:29:45.350> shard<00:29:45.620> in<00:29:45.920> the<00:29:46.070> future 00:29:46.390 --> 00:29:46.400 align:start position:0% into a contract on a shard in the future 00:29:46.400 --> 00:29:48.580 align:start position:0% into a contract on a shard in the future in<00:29:47.360> the<00:29:47.510> meantime<00:29:47.690> that<00:29:48.050> still<00:29:48.230> hasn't<00:29:48.500> really 00:29:48.580 --> 00:29:48.590 align:start position:0% in the meantime that still hasn't really 00:29:48.590 --> 00:29:50.320 align:start position:0% in the meantime that still hasn't really been<00:29:48.770> designed<00:29:48.920> but<00:29:49.730> yeah<00:29:49.850> we<00:29:50.000> would<00:29:50.120> still 00:29:50.320 --> 00:29:50.330 align:start position:0% been designed but yeah we would still 00:29:50.330 --> 00:29:51.670 align:start position:0% been designed but yeah we would still keep<00:29:50.480> the<00:29:50.630> same<00:29:50.810> state<00:29:51.110> but<00:29:51.140> in<00:29:51.440> the<00:29:51.500> future 00:29:51.670 --> 00:29:51.680 align:start position:0% keep the same state but in the future 00:29:51.680 --> 00:29:53.200 align:start position:0% keep the same state but in the future ideally<00:29:52.130> you<00:29:52.190> want<00:29:52.370> proof<00:29:52.730> of<00:29:52.820> work<00:29:52.940> to<00:29:53.090> be 00:29:53.200 --> 00:29:53.210 align:start position:0% ideally you want proof of work to be 00:29:53.210 --> 00:29:55.450 align:start position:0% ideally you want proof of work to be deprecated<00:29:53.630> over<00:29:54.050> time<00:29:54.260> yeah<00:29:54.590> great<00:29:55.250> thank 00:29:55.450 --> 00:29:55.460 align:start position:0% deprecated over time yeah great thank 00:29:55.460 --> 00:30:01.930 align:start position:0% deprecated over time yeah great thank you<00:29:55.610> yep<00:29:57.010> yeah<00:29:58.030> hey<00:29:59.350> two<00:30:00.350> questions<00:30:00.740> first<00:30:01.130> a 00:30:01.930 --> 00:30:01.940 align:start position:0% you yep yeah hey two questions first a 00:30:01.940 --> 00:30:05.830 align:start position:0% you yep yeah hey two questions first a Ewing<00:30:02.840> does<00:30:03.710> does<00:30:04.310> this<00:30:04.670> clan<00:30:05.000> prism<00:30:05.510> client 00:30:05.830 --> 00:30:05.840 align:start position:0% Ewing does does this clan prism client 00:30:05.840 --> 00:30:09.220 align:start position:0% Ewing does does this clan prism client intend<00:30:06.290> to<00:30:06.470> deprecate<00:30:06.830> get<00:30:07.430> always<00:30:08.300> something 00:30:09.220 --> 00:30:09.230 align:start position:0% intend to deprecate get always something 00:30:09.230 --> 00:30:10.870 align:start position:0% intend to deprecate get always something it's<00:30:09.530> a<00:30:09.590> good<00:30:09.710> question<00:30:09.860> I<00:30:10.250> think<00:30:10.640> the<00:30:10.790> gas 00:30:10.870 --> 00:30:10.880 align:start position:0% it's a good question I think the gas 00:30:10.880 --> 00:30:12.250 align:start position:0% it's a good question I think the gas team<00:30:11.060> has<00:30:11.180> been<00:30:11.270> really<00:30:11.480> busy<00:30:11.630> right<00:30:11.900> now<00:30:11.960> with 00:30:12.250 --> 00:30:12.260 align:start position:0% team has been really busy right now with 00:30:12.260 --> 00:30:14.740 align:start position:0% team has been really busy right now with all<00:30:12.440> the<00:30:12.620> hard<00:30:13.070> fork<00:30:13.280> situation<00:30:14.120> and<00:30:14.390> testing 00:30:14.740 --> 00:30:14.750 align:start position:0% all the hard fork situation and testing 00:30:14.750 --> 00:30:15.730 align:start position:0% all the hard fork situation and testing and<00:30:14.870> making<00:30:14.990> sure<00:30:15.140> everything<00:30:15.350> goes<00:30:15.440> up<00:30:15.650> to 00:30:15.730 --> 00:30:15.740 align:start position:0% and making sure everything goes up to 00:30:15.740 --> 00:30:17.920 align:start position:0% and making sure everything goes up to par<00:30:15.920> I'm<00:30:16.730> not<00:30:17.030> quite<00:30:17.240> sure<00:30:17.270> exactly<00:30:17.540> what 00:30:17.920 --> 00:30:17.930 align:start position:0% par I'm not quite sure exactly what 00:30:17.930 --> 00:30:20.410 align:start position:0% par I'm not quite sure exactly what their<00:30:18.050> plans<00:30:18.290> are<00:30:18.440> moving<00:30:18.740> forward<00:30:19.180> but<00:30:20.180> yeah 00:30:20.410 --> 00:30:20.420 align:start position:0% their plans are moving forward but yeah 00:30:20.420 --> 00:30:21.790 align:start position:0% their plans are moving forward but yeah I<00:30:20.450> mean<00:30:20.570> they<00:30:20.900> have<00:30:21.020> so<00:30:21.170> much<00:30:21.260> experience<00:30:21.320> and 00:30:21.790 --> 00:30:21.800 align:start position:0% I mean they have so much experience and 00:30:21.800 --> 00:30:24.070 align:start position:0% I mean they have so much experience and go<00:30:22.090> that<00:30:23.090> you<00:30:23.270> know<00:30:23.360> love<00:30:23.600> for<00:30:23.750> them<00:30:23.840> to<00:30:23.960> get 00:30:24.070 --> 00:30:24.080 align:start position:0% go that you know love for them to get 00:30:24.080 --> 00:30:27.430 align:start position:0% go that you know love for them to get involved<00:30:24.290> as<00:30:24.530> well<00:30:25.600> I'll<00:30:26.600> try<00:30:26.960> to<00:30:27.020> be<00:30:27.200> more 00:30:27.430 --> 00:30:27.440 align:start position:0% involved as well I'll try to be more 00:30:27.440 --> 00:30:28.000 align:start position:0% involved as well I'll try to be more specific 00:30:28.000 --> 00:30:28.010 align:start position:0% specific 00:30:28.010 --> 00:30:31.090 align:start position:0% specific we'll<00:30:28.220> get<00:30:28.550> B<00:30:29.150> off<00:30:29.690> of<00:30:29.990> work<00:30:30.200> like<00:30:30.590> a<00:30:30.770> theorem 00:30:31.090 --> 00:30:31.100 align:start position:0% we'll get B off of work like a theorem 00:30:31.100 --> 00:30:34.410 align:start position:0% we'll get B off of work like a theorem one<00:30:31.340> or<00:30:31.640> we'll<00:30:32.210> do<00:30:32.540> they<00:30:32.690> intend<00:30:33.020> to<00:30:33.170> implement 00:30:34.410 --> 00:30:34.420 align:start position:0% one or we'll do they intend to implement 00:30:34.420 --> 00:30:38.200 align:start position:0% one or we'll do they intend to implement 2.0<00:30:35.420> surrender<00:30:36.170> I<00:30:36.470> am<00:30:36.680> Not<00:30:36.860> sure<00:30:36.890> okay<00:30:37.640> sorry 00:30:38.200 --> 00:30:38.210 align:start position:0% 2.0 surrender I am Not sure okay sorry 00:30:38.210 --> 00:30:40.690 align:start position:0% 2.0 surrender I am Not sure okay sorry okay<00:30:38.570> and<00:30:38.750> the<00:30:39.050> second<00:30:39.410> question<00:30:39.500> sorry<00:30:39.920> is 00:30:40.690 --> 00:30:40.700 align:start position:0% okay and the second question sorry is 00:30:40.700 --> 00:30:45.900 align:start position:0% okay and the second question sorry is are<00:30:41.600> you<00:30:41.810> funded<00:30:42.650> by<00:30:43.180> consensus<00:30:44.180> that<00:30:44.300> you 00:30:45.900 --> 00:30:45.910 align:start position:0% are you funded by consensus that you 00:30:45.910 --> 00:30:48.280 align:start position:0% are you funded by consensus that you intervene<00:30:46.910> yeah<00:30:47.360> we<00:30:47.540> received<00:30:47.900> funding<00:30:48.080> from 00:30:48.280 --> 00:30:48.290 align:start position:0% intervene yeah we received funding from 00:30:48.290 --> 00:30:49.300 align:start position:0% intervene yeah we received funding from Aragon<00:30:48.890> nest 00:30:49.300 --> 00:30:49.310 align:start position:0% Aragon nest 00:30:49.310 --> 00:30:51.160 align:start position:0% Aragon nest we<00:30:49.400> received<00:30:49.790> a<00:30:50.210> major<00:30:50.510> grant<00:30:50.690> from<00:30:50.840> with<00:30:51.020> UN 00:30:51.160 --> 00:30:51.170 align:start position:0% we received a major grant from with UN 00:30:51.170 --> 00:30:53.710 align:start position:0% we received a major grant from with UN Foundation<00:30:51.590> a<00:30:51.680> $500,000<00:30:52.580> in<00:30:52.820> the<00:30:52.910> latest<00:30:53.180> wave 00:30:53.710 --> 00:30:53.720 align:start position:0% Foundation a $500,000 in the latest wave 00:30:53.720 --> 00:30:56.650 align:start position:0% Foundation a $500,000 in the latest wave so<00:30:54.380> I<00:30:54.410> was<00:30:54.590> super<00:30:54.860> nice<00:30:55.040> thank<00:30:55.370> you<00:30:55.460> if<00:30:55.660> we 00:30:56.650 --> 00:30:56.660 align:start position:0% so I was super nice thank you if we 00:30:56.660 --> 00:30:59.890 align:start position:0% so I was super nice thank you if we received<00:30:56.960> ECF<00:30:57.380> and<00:30:58.390> one<00:30:59.390> Shannon<00:30:59.600> blockchain 00:30:59.890 --> 00:30:59.900 align:start position:0% received ECF and one Shannon blockchain 00:30:59.900 --> 00:31:01.960 align:start position:0% received ECF and one Shannon blockchain labs<00:31:00.110> a<00:31:00.320> few<00:31:00.470> other<00:31:00.590> organizations<00:31:00.820> but<00:31:01.820> it's 00:31:01.960 --> 00:31:01.970 align:start position:0% labs a few other organizations but it's 00:31:01.970 --> 00:31:03.490 align:start position:0% labs a few other organizations but it's all<00:31:02.090> been<00:31:02.240> grants<00:31:02.600> we<00:31:02.870> haven't<00:31:03.140> taken<00:31:03.290> any 00:31:03.490 --> 00:31:03.500 align:start position:0% all been grants we haven't taken any 00:31:03.500 --> 00:31:06.340 align:start position:0% all been grants we haven't taken any equity<00:31:03.920> you<00:31:04.790> know<00:31:04.910> we're<00:31:05.060> not<00:31:05.180> we're<00:31:05.990> not<00:31:06.020> kind 00:31:06.340 --> 00:31:06.350 align:start position:0% equity you know we're not we're not kind 00:31:06.350 --> 00:31:07.900 align:start position:0% equity you know we're not we're not kind of<00:31:06.410> full<00:31:06.590> time<00:31:06.800> you're<00:31:07.190> walking<00:31:07.340> full<00:31:07.730> time 00:31:07.900 --> 00:31:07.910 align:start position:0% of full time you're walking full time 00:31:07.910 --> 00:31:10.240 align:start position:0% of full time you're walking full time the<00:31:08.060> team<00:31:08.240> yeah<00:31:08.480> on<00:31:08.630> this<00:31:08.810> okay<00:31:09.320> great<00:31:09.830> awesome 00:31:10.240 --> 00:31:10.250 align:start position:0% the team yeah on this okay great awesome 00:31:10.250 --> 00:31:12.580 align:start position:0% the team yeah on this okay great awesome thank<00:31:10.460> you<00:31:10.550> yeah<00:31:11.150> so<00:31:11.750> we<00:31:11.840> have<00:31:11.960> one<00:31:12.410> more 00:31:12.580 --> 00:31:12.590 align:start position:0% thank you yeah so we have one more 00:31:12.590 --> 00:31:13.270 align:start position:0% thank you yeah so we have one more question 00:31:13.270 --> 00:31:13.280 align:start position:0% question 00:31:13.280 --> 00:31:16.510 align:start position:0% question yeah<00:31:13.820> hey<00:31:14.570> can<00:31:15.350> you<00:31:15.470> talk<00:31:15.650> more<00:31:15.800> about<00:31:15.860> running 00:31:16.510 --> 00:31:16.520 align:start position:0% yeah hey can you talk more about running 00:31:16.520 --> 00:31:18.070 align:start position:0% yeah hey can you talk more about running a<00:31:16.610> validated<00:31:17.090> client<00:31:17.360> on<00:31:17.450> their<00:31:17.540> smartphone 00:31:18.070 --> 00:31:18.080 align:start position:0% a validated client on their smartphone 00:31:18.080 --> 00:31:20.080 align:start position:0% a validated client on their smartphone do<00:31:18.830> you<00:31:18.890> know<00:31:19.010> your<00:31:19.310> particular<00:31:19.610> wor<00:31:19.880> sure 00:31:20.080 --> 00:31:20.090 align:start position:0% do you know your particular wor sure 00:31:20.090 --> 00:31:22.060 align:start position:0% do you know your particular wor sure ideally<00:31:20.630> like<00:31:20.780> if<00:31:21.470> it's<00:31:21.680> gonna<00:31:21.740> run<00:31:21.950> on<00:31:22.040> a 00:31:22.060 --> 00:31:22.070 align:start position:0% ideally like if it's gonna run on a 00:31:22.070 --> 00:31:23.290 align:start position:0% ideally like if it's gonna run on a smartphone<00:31:22.280> a--probably<00:31:22.700> just<00:31:22.910> be<00:31:23.030> like<00:31:23.180> the 00:31:23.290 --> 00:31:23.300 align:start position:0% smartphone a--probably just be like the 00:31:23.300 --> 00:31:24.340 align:start position:0% smartphone a--probably just be like the private<00:31:23.600> key<00:31:23.720> kind<00:31:23.960> of<00:31:24.050> signing 00:31:24.340 --> 00:31:24.350 align:start position:0% private key kind of signing 00:31:24.350 --> 00:31:25.840 align:start position:0% private key kind of signing functionality<00:31:24.890> of<00:31:24.980> the<00:31:25.040> validator<00:31:25.400> client 00:31:25.840 --> 00:31:25.850 align:start position:0% functionality of the validator client 00:31:25.850 --> 00:31:27.550 align:start position:0% functionality of the validator client we<00:31:26.240> still<00:31:26.420> haven't<00:31:26.570> designed<00:31:26.900> exactly<00:31:27.080> like 00:31:27.550 --> 00:31:27.560 align:start position:0% we still haven't designed exactly like 00:31:27.560 --> 00:31:28.950 align:start position:0% we still haven't designed exactly like what<00:31:28.070> it<00:31:28.190> would<00:31:28.250> look<00:31:28.400> like<00:31:28.460> on<00:31:28.640> mobile 00:31:28.950 --> 00:31:28.960 align:start position:0% what it would look like on mobile 00:31:28.960 --> 00:31:30.760 align:start position:0% what it would look like on mobile because<00:31:29.960> there<00:31:30.140> are<00:31:30.200> still<00:31:30.380> things<00:31:30.560> to<00:31:30.620> be 00:31:30.760 --> 00:31:30.770 align:start position:0% because there are still things to be 00:31:30.770 --> 00:31:33.340 align:start position:0% because there are still things to be done<00:31:30.890> on<00:31:30.980> the<00:31:31.070> spec<00:31:31.310> but<00:31:32.060> ideally<00:31:32.300> like<00:31:32.840> yes 00:31:33.340 --> 00:31:33.350 align:start position:0% done on the spec but ideally like yes 00:31:33.350 --> 00:31:34.780 align:start position:0% done on the spec but ideally like yes like<00:31:33.620> we<00:31:33.890> want<00:31:34.100> to<00:31:34.190> make<00:31:34.310> it<00:31:34.460> as<00:31:34.550> lightweight 00:31:34.780 --> 00:31:34.790 align:start position:0% like we want to make it as lightweight 00:31:34.790 --> 00:31:36.190 align:start position:0% like we want to make it as lightweight as<00:31:34.940> possible<00:31:35.060> if<00:31:35.600> you're<00:31:35.720> running<00:31:35.840> on<00:31:36.050> your 00:31:36.190 --> 00:31:36.200 align:start position:0% as possible if you're running on your 00:31:36.200 --> 00:31:38.490 align:start position:0% as possible if you're running on your phone<00:31:36.410> and<00:31:37.130> obviously<00:31:37.490> phones<00:31:37.790> have<00:31:38.120> like 00:31:38.490 --> 00:31:38.500 align:start position:0% phone and obviously phones have like 00:31:38.500 --> 00:31:40.810 align:start position:0% phone and obviously phones have like availability<00:31:39.500> assumptions<00:31:40.160> like<00:31:40.400> you<00:31:40.520> know 00:31:40.810 --> 00:31:40.820 align:start position:0% availability assumptions like you know 00:31:40.820 --> 00:31:42.280 align:start position:0% availability assumptions like you know you<00:31:40.880> might<00:31:41.060> not<00:31:41.150> always<00:31:41.300> have<00:31:41.390> connection<00:31:41.990> we 00:31:42.280 --> 00:31:42.290 align:start position:0% you might not always have connection we 00:31:42.290 --> 00:31:43.300 align:start position:0% you might not always have connection we want<00:31:42.470> to<00:31:42.530> make<00:31:42.650> sure<00:31:42.770> that<00:31:42.950> you're<00:31:43.160> prepared 00:31:43.300 --> 00:31:43.310 align:start position:0% want to make sure that you're prepared 00:31:43.310 --> 00:31:44.770 align:start position:0% want to make sure that you're prepared for<00:31:43.520> that<00:31:43.730> and<00:31:44.030> have<00:31:44.180> some<00:31:44.210> way<00:31:44.420> to<00:31:44.480> protect 00:31:44.770 --> 00:31:44.780 align:start position:0% for that and have some way to protect 00:31:44.780 --> 00:31:46.930 align:start position:0% for that and have some way to protect you<00:31:45.020> against<00:31:45.320> those<00:31:45.440> things<00:31:45.650> so<00:31:46.610> there<00:31:46.850> are 00:31:46.930 --> 00:31:46.940 align:start position:0% you against those things so there are 00:31:46.940 --> 00:31:48.250 align:start position:0% you against those things so there are some<00:31:47.060> compromises<00:31:47.690> for<00:31:47.870> running<00:31:48.050> on<00:31:48.170> the 00:31:48.250 --> 00:31:48.260 align:start position:0% some compromises for running on the 00:31:48.260 --> 00:31:50.440 align:start position:0% some compromises for running on the phone<00:31:48.580> but<00:31:49.580> there<00:31:49.700> hasn't<00:31:49.850> been<00:31:49.970> designed<00:31:50.330> yet 00:31:50.440 --> 00:31:50.450 align:start position:0% phone but there hasn't been designed yet 00:31:50.450 --> 00:31:52.530 align:start position:0% phone but there hasn't been designed yet so<00:31:50.720> I<00:31:50.750> can't<00:31:51.050> give<00:31:51.200> a<00:31:51.230> strong<00:31:51.740> answer<00:31:52.040> to<00:31:52.160> that 00:31:52.530 --> 00:31:52.540 align:start position:0% so I can't give a strong answer to that 00:31:52.540 --> 00:31:55.330 align:start position:0% so I can't give a strong answer to that thank<00:31:53.540> you<00:31:53.660> right<00:31:54.200> so<00:31:54.440> thank<00:31:54.770> you<00:31:54.860> everyone 00:31:55.330 --> 00:31:55.340 align:start position:0% thank you right so thank you everyone 00:31:55.340 --> 00:31:56.190 align:start position:0% thank you right so thank you everyone appreciate<00:31:55.880> it 00:31:56.190 --> 00:31:56.200 align:start position:0% appreciate it 00:31:56.200 --> 00:32:08.810 align:start position:0% appreciate it [Applause] 00:32:08.810 --> 00:32:08.820 align:start position:0% 00:32:08.820 --> 00:32:10.880 align:start position:0% you