WEBVTT Kind: captions Language: en 00:00:05.470 --> 00:00:09.120 align:start position:0% so<00:00:06.630> so<00:00:07.630> my<00:00:07.750> talk<00:00:07.900> is<00:00:07.960> about<00:00:08.260> building<00:00:08.740> the 00:00:09.120 --> 00:00:09.130 align:start position:0% so so my talk is about building the 00:00:09.130 --> 00:00:12.560 align:start position:0% so so my talk is about building the serum<00:00:09.790> to<00:00:09.910> pan<00:00:10.090> around<00:00:10.120> sharp<00:00:10.660> subject<00:00:11.139> so 00:00:12.560 --> 00:00:12.570 align:start position:0% serum to pan around sharp subject so 00:00:12.570 --> 00:00:14.850 align:start position:0% serum to pan around sharp subject so before<00:00:13.570> I<00:00:13.600> go<00:00:13.870> into<00:00:14.020> the<00:00:14.139> talk--i<00:00:14.469> Short 00:00:14.850 --> 00:00:14.860 align:start position:0% before I go into the talk--i Short 00:00:14.860 --> 00:00:17.220 align:start position:0% before I go into the talk--i Short Introduction<00:00:15.490> open<00:00:16.000> e<00:00:16.090> I'm<00:00:16.360> Rita<00:00:16.930> I'm<00:00:17.200> a 00:00:17.220 --> 00:00:17.230 align:start position:0% Introduction open e I'm Rita I'm a 00:00:17.230 --> 00:00:19.620 align:start position:0% Introduction open e I'm Rita I'm a Caldwell<00:00:17.950> for<00:00:18.160> I<00:00:18.220> party<00:00:18.580> technology<00:00:18.760> and<00:00:19.480> I 00:00:19.620 --> 00:00:19.630 align:start position:0% Caldwell for I party technology and I 00:00:19.630 --> 00:00:23.070 align:start position:0% Caldwell for I party technology and I work<00:00:19.900> on<00:00:20.850> assume<00:00:21.850> and<00:00:22.150> assume<00:00:22.450> two<00:00:22.870> one<00:00:23.050> zero 00:00:23.070 --> 00:00:23.080 align:start position:0% work on assume and assume two one zero 00:00:23.080 --> 00:00:26.100 align:start position:0% work on assume and assume two one zero so<00:00:23.760> we<00:00:24.760> really<00:00:25.000> want<00:00:25.180> to<00:00:25.240> lean<00:00:25.480> this<00:00:25.630> talk<00:00:25.870> talk 00:00:26.100 --> 00:00:26.110 align:start position:0% so we really want to lean this talk talk 00:00:26.110 --> 00:00:28.620 align:start position:0% so we really want to lean this talk talk about<00:00:26.380> how<00:00:27.310> we<00:00:27.370> got<00:00:27.640> involved<00:00:28.120> in<00:00:28.420> to<00:00:28.540> improve 00:00:28.620 --> 00:00:28.630 align:start position:0% about how we got involved in to improve 00:00:28.630 --> 00:00:32.549 align:start position:0% about how we got involved in to improve on<00:00:29.230> zero<00:00:29.470> and<00:00:29.620> some<00:00:30.750> quite<00:00:31.750> hard<00:00:31.930> license<00:00:32.379> we 00:00:32.549 --> 00:00:32.559 align:start position:0% on zero and some quite hard license we 00:00:32.559 --> 00:00:38.400 align:start position:0% on zero and some quite hard license we learned<00:00:32.800> in<00:00:33.340> the<00:00:33.460> process<00:00:35.700> so<00:00:36.810> so<00:00:37.810> like<00:00:38.079> our 00:00:38.400 --> 00:00:38.410 align:start position:0% learned in the process so so like our 00:00:38.410 --> 00:00:41.370 align:start position:0% learned in the process so so like our journey<00:00:38.800> for<00:00:39.250> eastern<00:00:40.180> 2.0<00:00:40.750> is<00:00:40.930> really<00:00:41.200> about 00:00:41.370 --> 00:00:41.380 align:start position:0% journey for eastern 2.0 is really about 00:00:41.380 --> 00:00:44.460 align:start position:0% journey for eastern 2.0 is really about building<00:00:41.740> a<00:00:41.910> generic<00:00:43.020> blockchain<00:00:44.020> framework 00:00:44.460 --> 00:00:44.470 align:start position:0% building a generic blockchain framework 00:00:44.470 --> 00:00:47.490 align:start position:0% building a generic blockchain framework because<00:00:45.040> we<00:00:45.760> i<00:00:46.090> party<00:00:46.810> revealed<00:00:47.110> a<00:00:47.230> lot<00:00:47.380> of 00:00:47.490 --> 00:00:47.500 align:start position:0% because we i party revealed a lot of 00:00:47.500 --> 00:00:50.760 align:start position:0% because we i party revealed a lot of blog<00:00:47.739> chance<00:00:48.040> and<00:00:48.280> we<00:00:48.970> really<00:00:49.239> want<00:00:49.420> to<00:00:49.770> make 00:00:50.760 --> 00:00:50.770 align:start position:0% blog chance and we really want to make 00:00:50.770 --> 00:00:52.800 align:start position:0% blog chance and we really want to make sure<00:00:50.950> we<00:00:51.190> don't<00:00:51.340> write<00:00:51.820> too<00:00:52.060> many<00:00:52.180> duplicate 00:00:52.800 --> 00:00:52.810 align:start position:0% sure we don't write too many duplicate 00:00:52.810 --> 00:00:55.710 align:start position:0% sure we don't write too many duplicate code<00:00:52.960> so<00:00:53.410> the<00:00:53.680> first<00:00:53.920> thing<00:00:54.130> I<00:00:54.370> remember<00:00:55.090> for 00:00:55.710 --> 00:00:55.720 align:start position:0% code so the first thing I remember for 00:00:55.720 --> 00:00:59.160 align:start position:0% code so the first thing I remember for the<00:00:55.950> ich10r<00:00:56.950> was<00:00:57.070> a<00:00:57.100> hybrid<00:00:57.340> Casper<00:00:58.000> I<00:00:58.180> tell 00:00:59.160 --> 00:00:59.170 align:start position:0% the ich10r was a hybrid Casper I tell 00:00:59.170 --> 00:01:02.389 align:start position:0% the ich10r was a hybrid Casper I tell him<00:00:59.380> we<00:00:59.530> were<00:00:59.940> experimenting<00:01:00.940> with<00:01:01.180> building 00:01:02.389 --> 00:01:02.399 align:start position:0% him we were experimenting with building 00:01:02.399 --> 00:01:05.399 align:start position:0% him we were experimenting with building having<00:01:03.399> a<00:01:03.610> generic<00:01:04.089> engine<00:01:04.420> design<00:01:04.809> in<00:01:05.049> our 00:01:05.399 --> 00:01:05.409 align:start position:0% having a generic engine design in our 00:01:05.409 --> 00:01:08.219 align:start position:0% having a generic engine design in our party<00:01:06.250> serum<00:01:06.549> plant<00:01:06.759> so<00:01:07.149> we<00:01:07.390> have<00:01:07.600> support<00:01:08.170> for 00:01:08.219 --> 00:01:08.229 align:start position:0% party serum plant so we have support for 00:01:08.229 --> 00:01:11.039 align:start position:0% party serum plant so we have support for finality<00:01:08.799> and<00:01:09.010> a<00:01:09.549> real<00:01:10.180> size<00:01:10.420> support<00:01:10.840> for 00:01:11.039 --> 00:01:11.049 align:start position:0% finality and a real size support for 00:01:11.049 --> 00:01:13.560 align:start position:0% finality and a real size support for custom<00:01:11.409> fortress<00:01:11.860> rules<00:01:12.250> so<00:01:13.150> in<00:01:13.270> that<00:01:13.390> case 00:01:13.560 --> 00:01:13.570 align:start position:0% custom fortress rules so in that case 00:01:13.570 --> 00:01:16.289 align:start position:0% custom fortress rules so in that case adding<00:01:14.140> the<00:01:14.380> hybrid<00:01:14.950> Casper<00:01:15.340> FFG<00:01:15.850> turns<00:01:16.060> out 00:01:16.289 --> 00:01:16.299 align:start position:0% adding the hybrid Casper FFG turns out 00:01:16.299 --> 00:01:20.609 align:start position:0% adding the hybrid Casper FFG turns out to<00:01:16.479> be<00:01:16.920> quite<00:01:18.180> relatively<00:01:19.180> easy<00:01:19.720> task<00:01:20.049> so<00:01:20.470> we 00:01:20.609 --> 00:01:20.619 align:start position:0% to be quite relatively easy task so we 00:01:20.619 --> 00:01:23.430 align:start position:0% to be quite relatively easy task so we had<00:01:20.830> a<00:01:21.330> working<00:01:22.330> hybrid<00:01:23.080> class<00:01:23.229> for 00:01:23.430 --> 00:01:23.440 align:start position:0% had a working hybrid class for 00:01:23.440 --> 00:01:25.980 align:start position:0% had a working hybrid class for implementation<00:01:23.890> quite<00:01:24.369> early<00:01:24.810> and<00:01:25.810> it 00:01:25.980 --> 00:01:25.990 align:start position:0% implementation quite early and it 00:01:25.990 --> 00:01:30.450 align:start position:0% implementation quite early and it actually<00:01:26.380> works<00:01:26.560> so<00:01:27.750> but<00:01:28.750> later<00:01:28.930> it<00:01:29.920> comes<00:01:30.340> to 00:01:30.450 --> 00:01:30.460 align:start position:0% actually works so but later it comes to 00:01:30.460 --> 00:01:34.440 align:start position:0% actually works so but later it comes to the<00:01:30.610> second<00:01:31.000> freeze<00:01:31.240> which<00:01:31.510> is<00:01:32.189> we<00:01:33.189> decided<00:01:33.670> to 00:01:34.440 --> 00:01:34.450 align:start position:0% the second freeze which is we decided to 00:01:34.450 --> 00:01:37.710 align:start position:0% the second freeze which is we decided to build<00:01:34.659> a<00:01:35.040> separate<00:01:36.040> block<00:01:36.250> chain<00:01:36.479> for<00:01:37.479> assume 00:01:37.710 --> 00:01:37.720 align:start position:0% build a separate block chain for assume 00:01:37.720 --> 00:01:38.370 align:start position:0% build a separate block chain for assume two<00:01:37.900> one<00:01:38.080> zero 00:01:38.370 --> 00:01:38.380 align:start position:0% two one zero 00:01:38.380 --> 00:01:43.890 align:start position:0% two one zero so<00:01:38.939> for<00:01:39.939> us<00:01:39.970> we<00:01:40.960> move<00:01:41.619> to<00:01:42.010> the<00:01:42.479> beacon<00:01:43.479> subtree 00:01:43.890 --> 00:01:43.900 align:start position:0% so for us we move to the beacon subtree 00:01:43.900 --> 00:01:48.929 align:start position:0% so for us we move to the beacon subtree runtime<00:01:46.140> so<00:01:47.140> for<00:01:47.590> the<00:01:47.799> epic<00:01:48.220> has<00:01:48.430> furthers 00:01:48.929 --> 00:01:48.939 align:start position:0% runtime so for the epic has furthers 00:01:48.939 --> 00:01:51.179 align:start position:0% runtime so for the epic has furthers really<00:01:49.299> some<00:01:49.600> performance<00:01:50.229> issues<00:01:50.350> and<00:01:50.650> we 00:01:51.179 --> 00:01:51.189 align:start position:0% really some performance issues and we 00:01:51.189 --> 00:01:53.789 align:start position:0% really some performance issues and we had<00:01:51.430> to<00:01:51.549> abandon<00:01:51.820> that<00:01:52.350> so<00:01:53.350> to<00:01:53.409> create<00:01:53.650> a 00:01:53.789 --> 00:01:53.799 align:start position:0% had to abandon that so to create a 00:01:53.799 --> 00:01:56.120 align:start position:0% had to abandon that so to create a separate<00:01:54.189> block<00:01:54.369> transfer<00:01:54.820> into<00:01:55.270> one<00:01:55.450> zero 00:01:56.120 --> 00:01:56.130 align:start position:0% separate block transfer into one zero 00:01:56.130 --> 00:02:01.140 align:start position:0% separate block transfer into one zero and<00:01:58.020> what<00:01:59.020> I<00:01:59.049> mean<00:01:59.320> by<00:01:59.579> beacon<00:02:00.579> substituent 00:02:01.140 --> 00:02:01.150 align:start position:0% and what I mean by beacon substituent 00:02:01.150 --> 00:02:07.050 align:start position:0% and what I mean by beacon substituent runtime<00:02:01.600> is<00:02:02.430> basically<00:02:03.720> P<00:02:04.720> Kanchan<00:02:05.909> Isis<00:02:06.909> up 00:02:07.050 --> 00:02:07.060 align:start position:0% runtime is basically P Kanchan Isis up 00:02:07.060 --> 00:02:10.820 align:start position:0% runtime is basically P Kanchan Isis up six<00:02:07.329> runtime 00:02:10.820 --> 00:02:10.830 align:start position:0% 00:02:10.830 --> 00:02:13.070 align:start position:0% so<00:02:11.250> I<00:02:11.280> really<00:02:11.640> want<00:02:11.790> to<00:02:11.849> go<00:02:12.060> into<00:02:12.300> the<00:02:12.599> like 00:02:13.070 --> 00:02:13.080 align:start position:0% so I really want to go into the like 00:02:13.080 --> 00:02:18.619 align:start position:0% so I really want to go into the like some<00:02:13.379> of<00:02:13.530> the<00:02:13.860> details<00:02:14.819> of<00:02:15.060> how<00:02:15.750> we<00:02:16.879> think<00:02:17.879> the 00:02:18.619 --> 00:02:18.629 align:start position:0% some of the details of how we think the 00:02:18.629 --> 00:02:20.509 align:start position:0% some of the details of how we think the pic<00:02:19.200> and<00:02:19.349> Chang<00:02:19.500> can<00:02:19.650> work<00:02:19.860> on<00:02:20.010> subsequent 00:02:20.509 --> 00:02:20.519 align:start position:0% pic and Chang can work on subsequent 00:02:20.519 --> 00:02:22.750 align:start position:0% pic and Chang can work on subsequent time<00:02:20.640> but<00:02:20.819> before<00:02:21.000> that<00:02:21.330> probably<00:02:22.110> a<00:02:22.200> really 00:02:22.750 --> 00:02:22.760 align:start position:0% time but before that probably a really 00:02:22.760 --> 00:02:25.699 align:start position:0% time but before that probably a really short<00:02:23.760> introduction<00:02:24.390> about<00:02:24.510> the<00:02:25.140> selfie 00:02:25.699 --> 00:02:25.709 align:start position:0% short introduction about the selfie 00:02:25.709 --> 00:02:28.670 align:start position:0% short introduction about the selfie runtime<00:02:26.390> so<00:02:27.390> subtree<00:02:27.900> diesel<00:02:28.290> engine<00:02:28.650> to 00:02:28.670 --> 00:02:28.680 align:start position:0% runtime so subtree diesel engine to 00:02:28.680 --> 00:02:31.160 align:start position:0% runtime so subtree diesel engine to build<00:02:28.920> locations<00:02:29.459> and<00:02:29.730> we<00:02:30.599> figure<00:02:30.900> out<00:02:30.930> that 00:02:31.160 --> 00:02:31.170 align:start position:0% build locations and we figure out that 00:02:31.170 --> 00:02:32.750 align:start position:0% build locations and we figure out that there<00:02:31.470> are<00:02:31.500> two<00:02:31.590> magazines<00:02:31.890> that<00:02:32.370> every 00:02:32.750 --> 00:02:32.760 align:start position:0% there are two magazines that every 00:02:32.760 --> 00:02:35.869 align:start position:0% there are two magazines that every blockchain<00:02:33.150> need<00:02:33.330> it's<00:02:33.900> basically<00:02:34.879> consensus 00:02:35.869 --> 00:02:35.879 align:start position:0% blockchain need it's basically consensus 00:02:35.879 --> 00:02:38.990 align:start position:0% blockchain need it's basically consensus and<00:02:36.030> stata<00:02:37.019> execution<00:02:37.680> it's<00:02:38.519> really<00:02:38.760> hard<00:02:38.910> to 00:02:38.990 --> 00:02:39.000 align:start position:0% and stata execution it's really hard to 00:02:39.000 --> 00:02:41.119 align:start position:0% and stata execution it's really hard to generate<00:02:39.420> the<00:02:40.019> consciousness<00:02:40.560> part<00:02:40.829> because 00:02:41.119 --> 00:02:41.129 align:start position:0% generate the consciousness part because 00:02:41.129 --> 00:02:42.740 align:start position:0% generate the consciousness part because different<00:02:41.670> consciousness<00:02:41.849> can<00:02:42.420> require 00:02:42.740 --> 00:02:42.750 align:start position:0% different consciousness can require 00:02:42.750 --> 00:02:45.729 align:start position:0% different consciousness can require different<00:02:43.230> like<00:02:43.920> entirely<00:02:44.700> different 00:02:45.729 --> 00:02:45.739 align:start position:0% different like entirely different 00:02:45.739 --> 00:02:48.470 align:start position:0% different like entirely different structures<00:02:46.739> like<00:02:47.010> some<00:02:47.250> consensus<00:02:47.879> need 00:02:48.470 --> 00:02:48.480 align:start position:0% structures like some consensus need 00:02:48.480 --> 00:02:50.270 align:start position:0% structures like some consensus need finality<00:02:48.900> some<00:02:49.319> candidates<00:02:49.859> don't<00:02:50.069> need 00:02:50.270 --> 00:02:50.280 align:start position:0% finality some candidates don't need 00:02:50.280 --> 00:02:52.670 align:start position:0% finality some candidates don't need finality<00:02:50.760> some<00:02:51.000> concerns<00:02:51.390> need<00:02:51.629> to<00:02:51.810> just 00:02:52.670 --> 00:02:52.680 align:start position:0% finality some concerns need to just 00:02:52.680 --> 00:02:54.920 align:start position:0% finality some concerns need to just needs<00:02:52.920> a<00:02:53.129> pass<00:02:53.400> plural<00:02:54.000> Sun<00:02:54.239> and<00:02:54.480> other 00:02:54.920 --> 00:02:54.930 align:start position:0% needs a pass plural Sun and other 00:02:54.930 --> 00:02:58.940 align:start position:0% needs a pass plural Sun and other probably<00:02:55.500> need<00:02:55.680> to<00:02:56.359> like<00:02:57.359> to<00:02:58.140> refer<00:02:58.560> back<00:02:58.590> to<00:02:58.799> a 00:02:58.940 --> 00:02:58.950 align:start position:0% probably need to like to refer back to a 00:02:58.950 --> 00:03:01.309 align:start position:0% probably need to like to refer back to a lot<00:02:59.190> of<00:02:59.340> previous<00:03:00.030> block<00:03:00.450> I<00:03:00.660> know<00:03:00.720> so<00:03:01.049> some 00:03:01.309 --> 00:03:01.319 align:start position:0% lot of previous block I know so some 00:03:01.319 --> 00:03:04.089 align:start position:0% lot of previous block I know so some consensus<00:03:01.920> need<00:03:02.220> to<00:03:02.599> have<00:03:03.599> a<00:03:03.629> lot<00:03:03.870> of 00:03:04.089 --> 00:03:04.099 align:start position:0% consensus need to have a lot of 00:03:04.099 --> 00:03:06.770 align:start position:0% consensus need to have a lot of accelerated<00:03:05.099> data<00:03:05.430> some<00:03:06.030> doesn't<00:03:06.599> really 00:03:06.770 --> 00:03:06.780 align:start position:0% accelerated data some doesn't really 00:03:06.780 --> 00:03:09.830 align:start position:0% accelerated data some doesn't really need<00:03:06.959> that<00:03:07.170> and<00:03:07.829> also<00:03:08.430> we<00:03:08.700> have<00:03:08.879> those<00:03:09.299> vast 00:03:09.830 --> 00:03:09.840 align:start position:0% need that and also we have those vast 00:03:09.840 --> 00:03:11.839 align:start position:0% need that and also we have those vast majority<00:03:10.829> of<00:03:10.859> different<00:03:11.340> focused<00:03:11.700> on<00:03:11.790> Ice 00:03:11.839 --> 00:03:11.849 align:start position:0% majority of different focused on Ice 00:03:11.849 --> 00:03:14.180 align:start position:0% majority of different focused on Ice Road<00:03:11.879> just<00:03:12.660> really<00:03:13.230> hard<00:03:13.379> to<00:03:13.470> generalize<00:03:13.769> but 00:03:14.180 --> 00:03:14.190 align:start position:0% Road just really hard to generalize but 00:03:14.190 --> 00:03:16.819 align:start position:0% Road just really hard to generalize but we<00:03:14.609> have<00:03:14.819> some<00:03:15.030> helpers<00:03:15.450> and<00:03:15.930> the<00:03:16.260> second<00:03:16.590> part 00:03:16.819 --> 00:03:16.829 align:start position:0% we have some helpers and the second part 00:03:16.829 --> 00:03:20.420 align:start position:0% we have some helpers and the second part is<00:03:16.919> still<00:03:17.760> execution<00:03:18.739> so<00:03:19.739> we<00:03:19.829> figure<00:03:20.099> out<00:03:20.160> we 00:03:20.420 --> 00:03:20.430 align:start position:0% is still execution so we figure out we 00:03:20.430 --> 00:03:21.710 align:start position:0% is still execution so we figure out we probably<00:03:20.609> can<00:03:20.940> generate<00:03:21.209> the<00:03:21.450> scale 00:03:21.710 --> 00:03:21.720 align:start position:0% probably can generate the scale 00:03:21.720 --> 00:03:25.280 align:start position:0% probably can generate the scale execution<00:03:22.349> part<00:03:22.530> and<00:03:22.799> we<00:03:23.549> just<00:03:23.760> call<00:03:23.970> it<00:03:24.290> run 00:03:25.280 --> 00:03:25.290 align:start position:0% execution part and we just call it run 00:03:25.290 --> 00:03:31.640 align:start position:0% execution part and we just call it run time<00:03:25.669> so<00:03:28.970> we<00:03:29.970> have<00:03:30.150> a<00:03:30.180> current<00:03:30.540> our<00:03:30.989> current 00:03:31.640 --> 00:03:31.650 align:start position:0% time so we have a current our current 00:03:31.650 --> 00:03:35.210 align:start position:0% time so we have a current our current set<00:03:32.340> to<00:03:32.430> run<00:03:32.609> time<00:03:32.790> Pisa<00:03:33.000> has<00:03:33.380> has<00:03:34.380> some<00:03:34.650> fixed 00:03:35.210 --> 00:03:35.220 align:start position:0% set to run time Pisa has has some fixed 00:03:35.220 --> 00:03:37.940 align:start position:0% set to run time Pisa has has some fixed seems<00:03:35.400> like<00:03:35.760> we<00:03:35.940> have<00:03:36.180> a<00:03:36.209> definition<00:03:36.870> of<00:03:37.079> block 00:03:37.940 --> 00:03:37.950 align:start position:0% seems like we have a definition of block 00:03:37.950 --> 00:03:40.339 align:start position:0% seems like we have a definition of block we<00:03:38.940> have<00:03:39.090> something<00:03:39.540> like<00:03:39.720> an<00:03:39.870> extrinsic 00:03:40.339 --> 00:03:40.349 align:start position:0% we have something like an extrinsic 00:03:40.349 --> 00:03:44.390 align:start position:0% we have something like an extrinsic which<00:03:41.870> includes<00:03:42.870> what<00:03:43.260> we<00:03:43.290> all<00:03:43.560> know<00:03:43.739> called 00:03:44.390 --> 00:03:44.400 align:start position:0% which includes what we all know called 00:03:44.400 --> 00:03:46.839 align:start position:0% which includes what we all know called transactions<00:03:45.030> or<00:03:45.569> and<00:03:45.989> other<00:03:46.260> parties 00:03:46.839 --> 00:03:46.849 align:start position:0% transactions or and other parties 00:03:46.849 --> 00:03:49.250 align:start position:0% transactions or and other parties information<00:03:47.849> six<00:03:48.120> which<00:03:48.359> includes<00:03:49.079> things 00:03:49.250 --> 00:03:49.260 align:start position:0% information six which includes things 00:03:49.260 --> 00:03:52.759 align:start position:0% information six which includes things like<00:03:49.910> timestamp<00:03:50.910> service<00:03:51.840> guide<00:03:52.049> and<00:03:52.349> we<00:03:52.650> also 00:03:52.759 --> 00:03:52.769 align:start position:0% like timestamp service guide and we also 00:03:52.769 --> 00:03:55.750 align:start position:0% like timestamp service guide and we also have<00:03:53.099> this<00:03:53.220> item<00:03:53.760> which<00:03:54.000> is<00:03:54.169> similar<00:03:55.169> to<00:03:55.349> logs 00:03:55.750 --> 00:03:55.760 align:start position:0% have this item which is similar to logs 00:03:55.760 --> 00:03:59.330 align:start position:0% have this item which is similar to logs in<00:03:56.760> Sturm<00:03:57.000> and<00:03:57.989> we<00:03:58.500> have<00:03:58.650> a<00:03:58.680> definition<00:03:59.160> of 00:03:59.330 --> 00:03:59.340 align:start position:0% in Sturm and we have a definition of 00:03:59.340 --> 00:04:01.520 align:start position:0% in Sturm and we have a definition of runtime<00:03:59.609> external<00:04:00.419> T's<00:04:00.540> basically<00:04:01.290> how<00:04:01.470> the 00:04:01.520 --> 00:04:01.530 align:start position:0% runtime external T's basically how the 00:04:01.530 --> 00:04:05.780 align:start position:0% runtime external T's basically how the runtime<00:04:02.040> talk<00:04:02.310> reached<00:04:02.900> outside<00:04:03.900> world<00:04:04.669> so<00:04:05.669> we 00:04:05.780 --> 00:04:05.790 align:start position:0% runtime talk reached outside world so we 00:04:05.790 --> 00:04:07.640 align:start position:0% runtime talk reached outside world so we have<00:04:05.819> all<00:04:06.180> these<00:04:06.359> things<00:04:06.569> and<00:04:06.900> they<00:04:07.139> have<00:04:07.379> some 00:04:07.640 --> 00:04:07.650 align:start position:0% have all these things and they have some 00:04:07.650 --> 00:04:11.509 align:start position:0% have all these things and they have some defense<00:04:08.069> structures<00:04:08.660> and<00:04:09.660> once<00:04:10.560> in<00:04:10.739> brief 00:04:11.509 --> 00:04:11.519 align:start position:0% defense structures and once in brief 00:04:11.519 --> 00:04:15.710 align:start position:0% defense structures and once in brief ones<00:04:11.849> who<00:04:12.150> figure<00:04:12.419> out<00:04:12.569> is<00:04:12.750> how<00:04:14.480> how<00:04:15.480> we<00:04:15.540> can 00:04:15.710 --> 00:04:15.720 align:start position:0% ones who figure out is how how we can 00:04:15.720 --> 00:04:17.599 align:start position:0% ones who figure out is how how we can reuse<00:04:16.229> those<00:04:16.410> structures<00:04:16.889> and<00:04:17.220> make<00:04:17.459> it 00:04:17.599 --> 00:04:17.609 align:start position:0% reuse those structures and make it 00:04:17.609 --> 00:04:20.719 align:start position:0% reuse those structures and make it working<00:04:18.120> for<00:04:18.930> building<00:04:19.409> our<00:04:19.530> assumed<00:04:20.099> 2.0 00:04:20.719 --> 00:04:20.729 align:start position:0% working for building our assumed 2.0 00:04:20.729 --> 00:04:23.029 align:start position:0% working for building our assumed 2.0 client<00:04:21.060> because<00:04:21.450> if<00:04:22.140> we<00:04:22.289> can<00:04:22.440> do<00:04:22.590> that<00:04:22.770> then<00:04:23.010> we 00:04:23.029 --> 00:04:23.039 align:start position:0% client because if we can do that then we 00:04:23.039 --> 00:04:23.900 align:start position:0% client because if we can do that then we kind 00:04:23.900 --> 00:04:23.910 align:start position:0% kind 00:04:23.910 --> 00:04:26.570 align:start position:0% kind a<00:04:23.940> lot<00:04:24.480> of<00:04:24.510> the<00:04:24.960> sub-tree<00:04:25.320> contract<00:04:25.800> and<00:04:26.010> guide 00:04:26.570 --> 00:04:26.580 align:start position:0% a lot of the sub-tree contract and guide 00:04:26.580 --> 00:04:29.030 align:start position:0% a lot of the sub-tree contract and guide something<00:04:27.570> for<00:04:27.750> free<00:04:27.930> like<00:04:28.170> so<00:04:28.590> networking 00:04:29.030 --> 00:04:29.040 align:start position:0% something for free like so networking 00:04:29.040 --> 00:04:31.970 align:start position:0% something for free like so networking world's<00:04:29.520> the<00:04:30.180> subject<00:04:30.690> light<00:04:31.530> client 00:04:31.970 --> 00:04:31.980 align:start position:0% world's the subject light client 00:04:31.980 --> 00:04:36.670 align:start position:0% world's the subject light client particle<00:04:32.660> so<00:04:33.680> what<00:04:34.680> we<00:04:34.830> end<00:04:34.980> up<00:04:35.100> doing<00:04:35.160> is<00:04:35.730> we 00:04:36.670 --> 00:04:36.680 align:start position:0% particle so what we end up doing is we 00:04:36.680 --> 00:04:40.210 align:start position:0% particle so what we end up doing is we create<00:04:37.680> a<00:04:37.710> wafer<00:04:38.040> block<00:04:38.360> this<00:04:39.360> is<00:04:39.510> basically 00:04:40.210 --> 00:04:40.220 align:start position:0% create a wafer block this is basically 00:04:40.220 --> 00:04:43.790 align:start position:0% create a wafer block this is basically says<00:04:41.220> that<00:04:41.670> we<00:04:42.000> create<00:04:42.510> a<00:04:42.540> separate<00:04:43.020> block 00:04:43.790 --> 00:04:43.800 align:start position:0% says that we create a separate block 00:04:43.800 --> 00:04:46.970 align:start position:0% says that we create a separate block definition<00:04:44.180> this<00:04:45.180> block<00:04:45.420> definition<00:04:45.570> we<00:04:46.560> call 00:04:46.970 --> 00:04:46.980 align:start position:0% definition this block definition we call 00:04:46.980 --> 00:04:48.560 align:start position:0% definition this block definition we call it<00:04:47.070> viper<00:04:47.280> block<00:04:47.580> follows 00:04:48.560 --> 00:04:48.570 align:start position:0% it viper block follows 00:04:48.570 --> 00:04:51.080 align:start position:0% it viper block follows selphie<00:04:48.990> definition<00:04:49.590> of<00:04:49.800> what<00:04:50.490> a<00:04:50.670> block<00:04:50.910> is 00:04:51.080 --> 00:04:51.090 align:start position:0% selphie definition of what a block is 00:04:51.090 --> 00:04:53.530 align:start position:0% selphie definition of what a block is basically<00:04:52.080> easier<00:04:52.380> set<00:04:52.590> the<00:04:52.740> fund<00:04:52.950> structure 00:04:53.530 --> 00:04:53.540 align:start position:0% basically easier set the fund structure 00:04:53.540 --> 00:04:57.890 align:start position:0% basically easier set the fund structure and<00:04:54.540> we<00:04:55.380> also<00:04:55.530> have<00:04:55.830> to<00:04:56.010> like<00:04:56.900> unmodified 00:04:57.890 --> 00:04:57.900 align:start position:0% and we also have to like unmodified 00:04:57.900 --> 00:05:01.010 align:start position:0% and we also have to like unmodified beacon<00:04:58.500> block<00:04:58.710> and<00:04:58.950> for<00:04:59.430> each<00:05:00.420> beacon<00:05:00.810> block 00:05:01.010 --> 00:05:01.020 align:start position:0% beacon block and for each beacon block 00:05:01.020 --> 00:05:03.170 align:start position:0% beacon block and for each beacon block we<00:05:01.440> make<00:05:01.620> sure<00:05:01.860> that<00:05:02.160> there<00:05:02.610> is<00:05:02.700> a<00:05:02.730> unique 00:05:03.170 --> 00:05:03.180 align:start position:0% we make sure that there is a unique 00:05:03.180 --> 00:05:05.210 align:start position:0% we make sure that there is a unique corresponding<00:05:04.020> Weaver<00:05:04.260> block<00:05:04.470> so<00:05:04.920> in<00:05:05.100> that 00:05:05.210 --> 00:05:05.220 align:start position:0% corresponding Weaver block so in that 00:05:05.220 --> 00:05:08.060 align:start position:0% corresponding Weaver block so in that case<00:05:05.780> even<00:05:06.780> become<00:05:07.230> blog<00:05:07.470> you<00:05:07.650> can<00:05:07.800> always 00:05:08.060 --> 00:05:08.070 align:start position:0% case even become blog you can always 00:05:08.070 --> 00:05:12.740 align:start position:0% case even become blog you can always generate<00:05:10.070> generate<00:05:11.070> a<00:05:11.310> waiver<00:05:11.700> block<00:05:11.910> but<00:05:12.390> you 00:05:12.740 --> 00:05:12.750 align:start position:0% generate generate a waiver block but you 00:05:12.750 --> 00:05:15.770 align:start position:0% generate generate a waiver block but you might<00:05:12.960> need<00:05:13.200> some<00:05:13.530> passed<00:05:14.330> flock<00:05:15.330> that<00:05:15.570> hang 00:05:15.770 --> 00:05:15.780 align:start position:0% might need some passed flock that hang 00:05:15.780 --> 00:05:18.710 align:start position:0% might need some passed flock that hang it<00:05:16.200> may<00:05:16.770> not<00:05:16.950> be<00:05:17.190> so<00:05:17.430> trivial<00:05:17.640> but<00:05:17.880> but<00:05:18.270> it 00:05:18.710 --> 00:05:18.720 align:start position:0% it may not be so trivial but but it 00:05:18.720 --> 00:05:20.840 align:start position:0% it may not be so trivial but but it should<00:05:19.050> be<00:05:19.170> in<00:05:19.350> Siri<00:05:19.590> possible<00:05:19.980> to<00:05:20.070> generate<00:05:20.460> a 00:05:20.840 --> 00:05:20.850 align:start position:0% should be in Siri possible to generate a 00:05:20.850 --> 00:05:25.100 align:start position:0% should be in Siri possible to generate a wafer<00:05:21.450> block<00:05:22.880> we<00:05:23.880> also<00:05:24.060> have<00:05:24.390> a<00:05:24.420> Reaper<00:05:24.840> state 00:05:25.100 --> 00:05:25.110 align:start position:0% wafer block we also have a Reaper state 00:05:25.110 --> 00:05:28.070 align:start position:0% wafer block we also have a Reaper state which<00:05:25.830> also<00:05:26.190> is<00:05:26.550> a<00:05:26.580> Viper<00:05:27.300> structure<00:05:27.810> on<00:05:28.050> top 00:05:28.070 --> 00:05:28.080 align:start position:0% which also is a Viper structure on top 00:05:28.080 --> 00:05:31.160 align:start position:0% which also is a Viper structure on top of<00:05:28.440> the<00:05:28.800> beacon<00:05:29.070> state<00:05:29.340> and<00:05:29.870> this<00:05:30.870> for<00:05:31.050> per 00:05:31.160 --> 00:05:31.170 align:start position:0% of the beacon state and this for per 00:05:31.170 --> 00:05:34.190 align:start position:0% of the beacon state and this for per wafer<00:05:31.470> state<00:05:32.210> follows<00:05:33.210> substrate<00:05:33.630> definition 00:05:34.190 --> 00:05:34.200 align:start position:0% wafer state follows substrate definition 00:05:34.200 --> 00:05:40.540 align:start position:0% wafer state follows substrate definition and<00:05:36.440> this<00:05:37.440> is<00:05:38.100> basically<00:05:38.340> a<00:05:38.670> marquetry<00:05:39.180> and 00:05:40.540 --> 00:05:40.550 align:start position:0% and this is basically a marquetry and 00:05:40.550 --> 00:05:43.220 align:start position:0% and this is basically a marquetry and this<00:05:41.550> particle<00:05:41.820> tree<00:05:42.060> also<00:05:42.270> has<00:05:42.390> a<00:05:42.570> definition 00:05:43.220 --> 00:05:43.230 align:start position:0% this particle tree also has a definition 00:05:43.230 --> 00:05:46.909 align:start position:0% this particle tree also has a definition in<00:05:43.380> subject<00:05:43.860> and<00:05:44.070> what<00:05:44.550> we<00:05:44.700> do<00:05:44.880> and<00:05:45.600> that<00:05:46.560> marco 00:05:46.909 --> 00:05:46.919 align:start position:0% in subject and what we do and that marco 00:05:46.919 --> 00:05:49.100 align:start position:0% in subject and what we do and that marco tree<00:05:47.130> make<00:05:47.340> is<00:05:47.640> it's<00:05:48.330> different<00:05:48.750> it's 00:05:49.100 --> 00:05:49.110 align:start position:0% tree make is it's different it's 00:05:49.110 --> 00:05:52.690 align:start position:0% tree make is it's different it's currently<00:05:49.440> different<00:05:49.820> than<00:05:50.820> what<00:05:51.060> is<00:05:51.540> defined 00:05:52.690 --> 00:05:52.700 align:start position:0% currently different than what is defined 00:05:52.700 --> 00:05:55.040 align:start position:0% currently different than what is defined assumed<00:05:53.700> to<00:05:53.880> burn<00:05:54.030> 0<00:05:54.210> so<00:05:54.480> what<00:05:54.660> we<00:05:54.780> do<00:05:54.900> we 00:05:55.040 --> 00:05:55.050 align:start position:0% assumed to burn 0 so what we do we 00:05:55.050 --> 00:05:59.450 align:start position:0% assumed to burn 0 so what we do we define<00:05:55.350> our<00:05:55.790> child<00:05:56.790> tree<00:05:57.330> and<00:05:58.400> this<00:05:59.400> tree 00:05:59.450 --> 00:05:59.460 align:start position:0% define our child tree and this tree 00:05:59.460 --> 00:06:01.520 align:start position:0% define our child tree and this tree structure<00:05:59.940> is<00:06:00.210> exactly<00:06:00.540> the<00:06:00.930> same<00:06:01.140> as<00:06:01.320> the 00:06:01.520 --> 00:06:01.530 align:start position:0% structure is exactly the same as the 00:06:01.530 --> 00:06:05.420 align:start position:0% structure is exactly the same as the pecan<00:06:01.860> tree<00:06:02.790> structure<00:06:03.150> this<00:06:04.020> is<00:06:04.400> like<00:06:05.400> a 00:06:05.420 --> 00:06:05.430 align:start position:0% pecan tree structure this is like a 00:06:05.430 --> 00:06:08.900 align:start position:0% pecan tree structure this is like a working<00:06:06.440> library<00:06:07.440> can<00:06:07.620> use<00:06:07.740> on<00:06:07.950> subject<00:06:08.340> so<00:06:08.880> we 00:06:08.900 --> 00:06:08.910 align:start position:0% working library can use on subject so we 00:06:08.910 --> 00:06:13.010 align:start position:0% working library can use on subject so we define<00:06:09.300> child<00:06:09.570> tree<00:06:09.840> and<00:06:11.330> in<00:06:12.330> this<00:06:12.570> country 00:06:13.010 --> 00:06:13.020 align:start position:0% define child tree and in this country 00:06:13.020 --> 00:06:14.810 align:start position:0% define child tree and in this country will<00:06:13.200> follow<00:06:13.380> exactly<00:06:13.650> what<00:06:14.280> the<00:06:14.430> beacon 00:06:14.810 --> 00:06:14.820 align:start position:0% will follow exactly what the beacon 00:06:14.820 --> 00:06:21.650 align:start position:0% will follow exactly what the beacon block<00:06:15.450> is<00:06:16.520> and<00:06:17.570> we<00:06:18.570> store<00:06:19.880> the<00:06:20.880> actual<00:06:21.150> beacon 00:06:21.650 --> 00:06:21.660 align:start position:0% block is and we store the actual beacon 00:06:21.660 --> 00:06:24.050 align:start position:0% block is and we store the actual beacon state<00:06:21.900> in<00:06:22.350> the<00:06:22.530> weber<00:06:22.740> state<00:06:22.860> so<00:06:23.370> there's 00:06:24.050 --> 00:06:24.060 align:start position:0% state in the weber state so there's 00:06:24.060 --> 00:06:26.000 align:start position:0% state in the weber state so there's there's<00:06:24.630> always<00:06:24.810> a<00:06:24.960> child<00:06:25.230> tree<00:06:25.470> which<00:06:25.680> has 00:06:26.000 --> 00:06:26.010 align:start position:0% there's always a child tree which has 00:06:26.010 --> 00:06:29.060 align:start position:0% there's always a child tree which has the<00:06:26.220> exact<00:06:26.610> same<00:06:26.880> route<00:06:27.419> of<00:06:27.660> the<00:06:27.900> beacon<00:06:28.800> state 00:06:29.060 --> 00:06:29.070 align:start position:0% the exact same route of the beacon state 00:06:29.070 --> 00:06:31.640 align:start position:0% the exact same route of the beacon state and<00:06:29.310> we<00:06:29.550> wet<00:06:29.820> it<00:06:29.850> with<00:06:30.510> some<00:06:30.810> other<00:06:30.990> states 00:06:31.640 --> 00:06:31.650 align:start position:0% and we wet it with some other states 00:06:31.650 --> 00:06:34.219 align:start position:0% and we wet it with some other states probably<00:06:31.950> some<00:06:32.250> cash<00:06:32.520> or<00:06:32.789> other<00:06:33.229> information 00:06:34.219 --> 00:06:34.229 align:start position:0% probably some cash or other information 00:06:34.229 --> 00:06:37.490 align:start position:0% probably some cash or other information that<00:06:34.260> we<00:06:34.800> need 00:06:37.490 --> 00:06:37.500 align:start position:0% 00:06:37.500 --> 00:06:41.420 align:start position:0% so<00:06:37.980> to<00:06:38.040> look<00:06:38.400> into<00:06:38.940> the<00:06:39.210> actual<00:06:39.800> thing<00:06:40.800> it<00:06:41.160> will 00:06:41.420 --> 00:06:41.430 align:start position:0% so to look into the actual thing it will 00:06:41.430 --> 00:06:43.880 align:start position:0% so to look into the actual thing it will be<00:06:41.550> like<00:06:41.760> this<00:06:41.940> exist<00:06:42.390> is<00:06:42.510> a<00:06:42.620> sandra<00:06:43.620> beacon 00:06:43.880 --> 00:06:43.890 align:start position:0% be like this exist is a sandra beacon 00:06:43.890 --> 00:06:48.050 align:start position:0% be like this exist is a sandra beacon block<00:06:45.200> we<00:06:46.200> have<00:06:46.230> the<00:06:46.980> slow<00:06:47.220> definition<00:06:47.790> block 00:06:48.050 --> 00:06:48.060 align:start position:0% block we have the slow definition block 00:06:48.060 --> 00:06:50.120 align:start position:0% block we have the slow definition block root<00:06:48.270> state<00:06:48.570> route<00:06:48.750> block<00:06:49.440> body<00:06:49.650> and<00:06:49.920> the 00:06:50.120 --> 00:06:50.130 align:start position:0% root state route block body and the 00:06:50.130 --> 00:06:54.740 align:start position:0% root state route block body and the signature<00:06:50.900> seems<00:06:51.900> like<00:06:52.080> that<00:06:52.290> and<00:06:53.390> for<00:06:54.390> the 00:06:54.740 --> 00:06:54.750 align:start position:0% signature seems like that and for the 00:06:54.750 --> 00:06:58.400 align:start position:0% signature seems like that and for the subtree<00:06:55.200> block<00:06:56.030> we<00:06:57.030> basically<00:06:57.360> make<00:06:57.750> it<00:06:57.930> like 00:06:58.400 --> 00:06:58.410 align:start position:0% subtree block we basically make it like 00:06:58.410 --> 00:07:02.330 align:start position:0% subtree block we basically make it like this<00:06:58.590> so<00:06:59.220> you<00:06:59.700> can<00:07:00.390> say<00:07:00.690> some<00:07:01.050> of<00:07:01.080> some<00:07:01.830> of<00:07:01.890> the 00:07:02.330 --> 00:07:02.340 align:start position:0% this so you can say some of some of the 00:07:02.340 --> 00:07:05.750 align:start position:0% this so you can say some of some of the items<00:07:03.060> are<00:07:03.570> exactly<00:07:04.050> the<00:07:04.200> same<00:07:04.230> as<00:07:04.760> ice 00:07:05.750 --> 00:07:05.760 align:start position:0% items are exactly the same as ice 00:07:05.760 --> 00:07:08.510 align:start position:0% items are exactly the same as ice Wally's<00:07:06.240> found<00:07:06.630> a<00:07:06.930> beacon<00:07:07.830> block<00:07:08.160> so<00:07:08.460> you 00:07:08.510 --> 00:07:08.520 align:start position:0% Wally's found a beacon block so you 00:07:08.520 --> 00:07:11.050 align:start position:0% Wally's found a beacon block so you should<00:07:08.820> you're<00:07:09.270> so<00:07:09.420> unique<00:07:09.810> corresponding 00:07:11.050 --> 00:07:11.060 align:start position:0% should you're so unique corresponding 00:07:11.060 --> 00:07:15.920 align:start position:0% should you're so unique corresponding and<00:07:12.560> for<00:07:13.560> stuff<00:07:14.310> that<00:07:14.690> doesn't<00:07:15.690> have<00:07:15.900> a 00:07:15.920 --> 00:07:15.930 align:start position:0% and for stuff that doesn't have a 00:07:15.930 --> 00:07:18.740 align:start position:0% and for stuff that doesn't have a definition<00:07:16.680> that<00:07:17.520> these<00:07:17.700> constants<00:07:18.150> is<00:07:18.300> sub 00:07:18.740 --> 00:07:18.750 align:start position:0% definition that these constants is sub 00:07:18.750 --> 00:07:22.760 align:start position:0% definition that these constants is sub sick<00:07:18.960> for<00:07:19.500> example<00:07:19.980> the<00:07:20.190> slot<00:07:20.780> and<00:07:21.780> the 00:07:22.760 --> 00:07:22.770 align:start position:0% sick for example the slot and the 00:07:22.770 --> 00:07:26.240 align:start position:0% sick for example the slot and the signature<00:07:23.280> which<00:07:23.700> is<00:07:23.850> food<00:07:24.120> identities<00:07:25.250> which 00:07:26.240 --> 00:07:26.250 align:start position:0% signature which is food identities which 00:07:26.250 --> 00:07:28.340 align:start position:0% signature which is food identities which because<00:07:27.120> is<00:07:27.330> in<00:07:27.480> the<00:07:27.570> header<00:07:27.780> is<00:07:27.960> obviously 00:07:28.340 --> 00:07:28.350 align:start position:0% because is in the header is obviously 00:07:28.350 --> 00:07:30.440 align:start position:0% because is in the header is obviously ball<00:07:28.740> no<00:07:28.980> matter<00:07:29.190> your<00:07:29.460> fluke<00:07:29.790> and<00:07:30.000> or<00:07:30.240> light 00:07:30.440 --> 00:07:30.450 align:start position:0% ball no matter your fluke and or light 00:07:30.450 --> 00:07:33.560 align:start position:0% ball no matter your fluke and or light clad<00:07:31.040> and<00:07:32.040> the<00:07:32.430> last<00:07:32.670> thing<00:07:32.940> we<00:07:33.060> need<00:07:33.090> to<00:07:33.240> care 00:07:33.560 --> 00:07:33.570 align:start position:0% clad and the last thing we need to care 00:07:33.570 --> 00:07:39.320 align:start position:0% clad and the last thing we need to care about<00:07:33.600> is<00:07:34.020> this<00:07:35.010> state<00:07:35.670> route<00:07:35.880> because<00:07:36.920> I<00:07:38.330> mean 00:07:39.320 --> 00:07:39.330 align:start position:0% about is this state route because I mean 00:07:39.330 --> 00:07:42.380 align:start position:0% about is this state route because I mean in<00:07:39.810> the<00:07:40.020> end<00:07:40.200> we<00:07:40.500> need<00:07:40.650> to<00:07:40.710> verify<00:07:41.060> this<00:07:42.060> this 00:07:42.380 --> 00:07:42.390 align:start position:0% in the end we need to verify this this 00:07:42.390 --> 00:07:47.090 align:start position:0% in the end we need to verify this this block<00:07:42.630> structure<00:07:43.080> the<00:07:43.950> issue<00:07:44.130> is<00:07:44.550> in<00:07:45.980> even<00:07:46.980> if 00:07:47.090 --> 00:07:47.100 align:start position:0% block structure the issue is in even if 00:07:47.100 --> 00:07:49.640 align:start position:0% block structure the issue is in even if there's<00:07:47.340> a<00:07:47.430> unique<00:07:48.090> correspondence<00:07:48.780> the 00:07:49.640 --> 00:07:49.650 align:start position:0% there's a unique correspondence the 00:07:49.650 --> 00:07:52.460 align:start position:0% there's a unique correspondence the signature<00:07:50.160> is<00:07:50.220> to<00:07:50.460> a<00:07:50.490> beacon<00:07:51.260> beacon<00:07:52.260> block 00:07:52.460 --> 00:07:52.470 align:start position:0% signature is to a beacon beacon block 00:07:52.470 --> 00:07:57.200 align:start position:0% signature is to a beacon beacon block signature<00:07:52.920> so<00:07:54.620> it<00:07:55.620> doesn't<00:07:56.190> verify<00:07:56.640> this 00:07:57.200 --> 00:07:57.210 align:start position:0% signature so it doesn't verify this 00:07:57.210 --> 00:07:58.940 align:start position:0% signature so it doesn't verify this state<00:07:57.480> route<00:07:57.690> but<00:07:57.930> instead<00:07:58.260> it<00:07:58.470> verifies<00:07:58.920> a 00:07:58.940 --> 00:07:58.950 align:start position:0% state route but instead it verifies a 00:07:58.950 --> 00:08:01.880 align:start position:0% state route but instead it verifies a beacon<00:07:59.400> block<00:07:59.610> state<00:07:59.910> route<00:08:00.260> so<00:08:01.260> in<00:08:01.440> that<00:08:01.590> case 00:08:01.880 --> 00:08:01.890 align:start position:0% beacon block state route so in that case 00:08:01.890 --> 00:08:05.380 align:start position:0% beacon block state route so in that case we<00:08:02.580> need<00:08:02.610> to<00:08:02.820> find<00:08:03.060> a<00:08:03.180> way<00:08:03.360> to<00:08:03.660> make<00:08:03.870> sure<00:08:04.080> that 00:08:05.380 --> 00:08:05.390 align:start position:0% we need to find a way to make sure that 00:08:05.390 --> 00:08:08.360 align:start position:0% we need to find a way to make sure that we<00:08:06.390> have<00:08:06.540> also<00:08:06.720> our<00:08:06.840> fallacy<00:08:07.470> so<00:08:07.830> how<00:08:08.010> do<00:08:08.070> we<00:08:08.190> do 00:08:08.360 --> 00:08:08.370 align:start position:0% we have also our fallacy so how do we do 00:08:08.370 --> 00:08:11.180 align:start position:0% we have also our fallacy so how do we do that<00:08:08.610> but<00:08:08.760> basically<00:08:09.770> it's<00:08:10.770> stuff<00:08:10.980> showing 00:08:11.180 --> 00:08:11.190 align:start position:0% that but basically it's stuff showing 00:08:11.190 --> 00:08:13.460 align:start position:0% that but basically it's stuff showing here<00:08:11.490> but<00:08:11.610> we<00:08:11.940> basically<00:08:12.300> create<00:08:12.720> a<00:08:12.750> second<00:08:13.170> TD 00:08:13.460 --> 00:08:13.470 align:start position:0% here but we basically create a second TD 00:08:13.470 --> 00:08:17.390 align:start position:0% here but we basically create a second TD structure<00:08:13.980> that<00:08:14.880> creates<00:08:15.330> the<00:08:15.510> proof<00:08:15.750> so<00:08:16.400> an 00:08:17.390 --> 00:08:17.400 align:start position:0% structure that creates the proof so an 00:08:17.400 --> 00:08:21.380 align:start position:0% structure that creates the proof so an additional<00:08:18.590> the<00:08:19.590> state<00:08:19.860> proof<00:08:20.130> that<00:08:20.550> goes 00:08:21.380 --> 00:08:21.390 align:start position:0% additional the state proof that goes 00:08:21.390 --> 00:08:25.760 align:start position:0% additional the state proof that goes from<00:08:21.690> the<00:08:22.380> beacon<00:08:23.070> salute<00:08:23.570> into<00:08:24.570> the<00:08:25.020> subject 00:08:25.760 --> 00:08:25.770 align:start position:0% from the beacon salute into the subject 00:08:25.770 --> 00:08:27.140 align:start position:0% from the beacon salute into the subject state<00:08:25.950> routes<00:08:26.130> the<00:08:26.310> wafer<00:08:26.580> blocks<00:08:26.760> a<00:08:26.940> route 00:08:27.140 --> 00:08:27.150 align:start position:0% state routes the wafer blocks a route 00:08:27.150 --> 00:08:32.870 align:start position:0% state routes the wafer blocks a route that<00:08:27.450> we<00:08:27.600> need<00:08:28.730> and<00:08:30.860> we're<00:08:31.860> doing<00:08:32.310> this<00:08:32.460> so 00:08:32.870 --> 00:08:32.880 align:start position:0% that we need and we're doing this so 00:08:32.880 --> 00:08:37.130 align:start position:0% that we need and we're doing this so this<00:08:33.630> is<00:08:33.810> or<00:08:34.110> about<00:08:34.350> reusability<00:08:35.390> so<00:08:36.390> let<00:08:37.050> me 00:08:37.130 --> 00:08:37.140 align:start position:0% this is or about reusability so let me 00:08:37.140 --> 00:08:40.370 align:start position:0% this is or about reusability so let me create<00:08:37.290> this<00:08:37.500> waiver<00:08:37.800> block<00:08:38.100> and<00:08:39.050> we<00:08:40.050> create<00:08:40.350> a 00:08:40.370 --> 00:08:40.380 align:start position:0% create this waiver block and we create a 00:08:40.380 --> 00:08:43.550 align:start position:0% create this waiver block and we create a consensus<00:08:40.950> engine<00:08:41.430> in<00:08:42.240> subject<00:08:42.630> returns<00:08:43.410> and 00:08:43.550 --> 00:08:43.560 align:start position:0% consensus engine in subject returns and 00:08:43.560 --> 00:08:45.560 align:start position:0% consensus engine in subject returns and just<00:08:43.740> directly<00:08:44.100> practice<00:08:44.610> plug<00:08:44.970> it<00:08:45.150> into 00:08:45.560 --> 00:08:45.570 align:start position:0% just directly practice plug it into 00:08:45.570 --> 00:08:48.820 align:start position:0% just directly practice plug it into subject<00:08:46.350> and<00:08:46.590> evil<00:08:47.220> work<00:08:47.430> with<00:08:47.610> the<00:08:47.790> rights<00:08:48.000> of 00:08:48.820 --> 00:08:48.830 align:start position:0% subject and evil work with the rights of 00:08:48.830 --> 00:08:50.330 align:start position:0% subject and evil work with the rights of the 00:08:50.330 --> 00:08:50.340 align:start position:0% the 00:08:50.340 --> 00:08:53.330 align:start position:0% the political<00:08:50.700> base<00:08:50.880> so<00:08:51.150> we<00:08:51.300> can<00:08:51.510> get<00:08:51.980> like<00:08:52.980> a 00:08:53.330 --> 00:08:53.340 align:start position:0% political base so we can get like a 00:08:53.340 --> 00:08:56.150 align:start position:0% political base so we can get like a separate<00:08:54.060> networking<00:08:54.870> and<00:08:55.170> also<00:08:55.440> the<00:08:55.740> subject 00:08:56.150 --> 00:08:56.160 align:start position:0% separate networking and also the subject 00:08:56.160 --> 00:08:59.000 align:start position:0% separate networking and also the subject like<00:08:56.490> land<00:08:57.170> component<00:08:58.170> for<00:08:58.560> free<00:08:58.740> and<00:08:58.980> that 00:08:59.000 --> 00:08:59.010 align:start position:0% like land component for free and that 00:08:59.010 --> 00:09:04.400 align:start position:0% like land component for free and that will<00:08:59.460> be<00:08:59.580> working<00:08:59.970> on<00:09:00.210> a<00:09:00.450> sort<00:09:00.660> of<00:09:00.870> a<00:09:00.960> zero<00:09:03.410> so 00:09:04.400 --> 00:09:04.410 align:start position:0% will be working on a sort of a zero so 00:09:04.410 --> 00:09:10.520 align:start position:0% will be working on a sort of a zero so we<00:09:04.920> unit<00:09:05.310> has<00:09:05.490> some<00:09:05.790> obstacles<00:09:06.660> that's<00:09:07.560> why<00:09:09.530> so 00:09:10.520 --> 00:09:10.530 align:start position:0% we unit has some obstacles that's why so 00:09:10.530 --> 00:09:13.880 align:start position:0% we unit has some obstacles that's why so the<00:09:11.250> issue<00:09:11.640> is<00:09:11.760> we<00:09:12.000> try<00:09:12.180> to<00:09:12.240> do<00:09:12.510> too<00:09:13.440> early<00:09:13.710> of 00:09:13.880 --> 00:09:13.890 align:start position:0% the issue is we try to do too early of 00:09:13.890 --> 00:09:16.850 align:start position:0% the issue is we try to do too early of this<00:09:14.730> thing<00:09:14.970> in<00:09:15.840> the<00:09:16.020> specification<00:09:16.680> process 00:09:16.850 --> 00:09:16.860 align:start position:0% this thing in the specification process 00:09:16.860 --> 00:09:19.940 align:start position:0% this thing in the specification process issue<00:09:17.520> is<00:09:17.820> either<00:09:18.750> time<00:09:19.140> the<00:09:19.290> specification 00:09:19.940 --> 00:09:19.950 align:start position:0% issue is either time the specification 00:09:19.950 --> 00:09:21.770 align:start position:0% issue is either time the specification is<00:09:20.040> still<00:09:20.340> trending<00:09:20.580> a<00:09:20.790> lot<00:09:20.970> and<00:09:21.180> that<00:09:21.420> creates 00:09:21.770 --> 00:09:21.780 align:start position:0% is still trending a lot and that creates 00:09:21.780 --> 00:09:24.800 align:start position:0% is still trending a lot and that creates a<00:09:21.960> little<00:09:22.380> problem<00:09:23.250> for<00:09:23.430> us<00:09:23.520> because<00:09:23.550> for<00:09:24.180> each 00:09:24.800 --> 00:09:24.810 align:start position:0% a little problem for us because for each 00:09:24.810 --> 00:09:27.020 align:start position:0% a little problem for us because for each new<00:09:25.140> release<00:09:25.470> we<00:09:25.920> are<00:09:25.950> basically<00:09:26.430> rewriting 00:09:27.020 --> 00:09:27.030 align:start position:0% new release we are basically rewriting 00:09:27.030 --> 00:09:31.700 align:start position:0% new release we are basically rewriting everything<00:09:27.360> and<00:09:29.180> that<00:09:30.180> kind<00:09:30.450> of<00:09:30.630> slow<00:09:31.500> down 00:09:31.700 --> 00:09:31.710 align:start position:0% everything and that kind of slow down 00:09:31.710 --> 00:09:34.610 align:start position:0% everything and that kind of slow down the<00:09:31.860> process<00:09:32.070> quite<00:09:32.730> a<00:09:32.790> little<00:09:32.970> bit<00:09:33.350> we<00:09:34.350> still 00:09:34.610 --> 00:09:34.620 align:start position:0% the process quite a little bit we still 00:09:34.620 --> 00:09:38.090 align:start position:0% the process quite a little bit we still lack<00:09:34.860> a<00:09:35.220> little<00:09:35.700> bit<00:09:35.850> primitives<00:09:36.740> we<00:09:37.740> have<00:09:37.950> the 00:09:38.090 --> 00:09:38.100 align:start position:0% lack a little bit primitives we have the 00:09:38.100 --> 00:09:40.130 align:start position:0% lack a little bit primitives we have the child<00:09:38.820> mark<00:09:39.090> of<00:09:39.180> tree<00:09:39.330> structure<00:09:39.600> but<00:09:39.930> we 00:09:40.130 --> 00:09:40.140 align:start position:0% child mark of tree structure but we 00:09:40.140 --> 00:09:41.980 align:start position:0% child mark of tree structure but we currently<00:09:40.380> don't<00:09:40.590> have<00:09:40.740> a<00:09:40.860> binary<00:09:41.250> marquetry 00:09:41.980 --> 00:09:41.990 align:start position:0% currently don't have a binary marquetry 00:09:41.990 --> 00:09:46.280 align:start position:0% currently don't have a binary marquetry child<00:09:42.990> tree<00:09:43.350> setup<00:09:44.010> so<00:09:44.370> assessing<00:09:45.150> that<00:09:45.420> is<00:09:45.840> we 00:09:46.280 --> 00:09:46.290 align:start position:0% child tree setup so assessing that is we 00:09:46.290 --> 00:09:51.980 align:start position:0% child tree setup so assessing that is we are<00:09:46.320> adding<00:09:47.750> the<00:09:48.750> POS<00:09:49.230> works<00:09:49.770> on<00:09:50.070> on<00:09:50.810> the<00:09:51.810> run 00:09:51.980 --> 00:09:51.990 align:start position:0% are adding the POS works on on the run 00:09:51.990 --> 00:09:55.040 align:start position:0% are adding the POS works on on the run time<00:09:52.230> like<00:09:53.130> by<00:09:53.460> itself<00:09:53.490> but<00:09:54.180> the<00:09:54.330> issue<00:09:54.510> is<00:09:54.780> if 00:09:55.040 --> 00:09:55.050 align:start position:0% time like by itself but the issue is if 00:09:55.050 --> 00:09:57.500 align:start position:0% time like by itself but the issue is if we<00:09:55.230> don't<00:09:55.410> get<00:09:55.650> it<00:09:55.860> at<00:09:56.160> new<00:09:56.370> primitives<00:09:56.880> OPRS 00:09:57.500 --> 00:09:57.510 align:start position:0% we don't get it at new primitives OPRS 00:09:57.510 --> 00:10:00.590 align:start position:0% we don't get it at new primitives OPRS will<00:09:57.750> be<00:09:57.900> too<00:09:58.080> slow<00:09:58.290> for<00:09:59.150> production<00:10:00.150> use<00:10:00.300> so 00:10:00.590 --> 00:10:00.600 align:start position:0% will be too slow for production use so 00:10:00.600 --> 00:10:02.870 align:start position:0% will be too slow for production use so that's<00:10:00.960> also<00:10:01.590> some<00:10:01.920> primitives<00:10:02.370> we<00:10:02.550> need<00:10:02.760> to 00:10:02.870 --> 00:10:02.880 align:start position:0% that's also some primitives we need to 00:10:02.880 --> 00:10:08.170 align:start position:0% that's also some primitives we need to add<00:10:03.030> and<00:10:04.880> because<00:10:05.880> we<00:10:06.180> are<00:10:06.330> kind<00:10:06.720> of<00:10:06.810> not<00:10:07.560> too 00:10:08.170 --> 00:10:08.180 align:start position:0% add and because we are kind of not too 00:10:08.180 --> 00:10:11.900 align:start position:0% add and because we are kind of not too fast<00:10:09.180> on<00:10:09.510> that<00:10:09.800> the<00:10:10.800> current<00:10:11.070> plans<00:10:11.280> is<00:10:11.640> we 00:10:11.900 --> 00:10:11.910 align:start position:0% fast on that the current plans is we 00:10:11.910 --> 00:10:18.680 align:start position:0% fast on that the current plans is we build<00:10:12.150> a<00:10:12.320> way<00:10:13.320> to<00:10:13.380> to<00:10:16.610> like<00:10:17.610> to<00:10:17.850> plant<00:10:18.120> setup<00:10:18.480> so 00:10:18.680 --> 00:10:18.690 align:start position:0% build a way to to like to plant setup so 00:10:18.690 --> 00:10:22.010 align:start position:0% build a way to to like to plant setup so basically<00:10:19.080> we<00:10:19.470> have<00:10:19.740> the<00:10:20.390> suffix<00:10:21.390> runtime 00:10:22.010 --> 00:10:22.020 align:start position:0% basically we have the suffix runtime 00:10:22.020 --> 00:10:24.590 align:start position:0% basically we have the suffix runtime plant<00:10:22.350> during<00:10:22.770> place<00:10:23.100> but<00:10:23.520> we<00:10:24.180> still<00:10:24.360> want<00:10:24.540> to 00:10:24.590 --> 00:10:24.600 align:start position:0% plant during place but we still want to 00:10:24.600 --> 00:10:26.390 align:start position:0% plant during place but we still want to catch<00:10:24.810> up<00:10:24.870> with<00:10:25.080> the<00:10:25.350> rest<00:10:25.560> of<00:10:25.680> the<00:10:25.830> team<00:10:26.070> so 00:10:26.390 --> 00:10:26.400 align:start position:0% catch up with the rest of the team so 00:10:26.400 --> 00:10:28.790 align:start position:0% catch up with the rest of the team so what<00:10:27.060> we<00:10:27.180> plan<00:10:27.390> to<00:10:27.420> do<00:10:27.660> is<00:10:27.840> we<00:10:28.140> want<00:10:28.350> to<00:10:28.470> build<00:10:28.620> a 00:10:28.790 --> 00:10:28.800 align:start position:0% what we plan to do is we want to build a 00:10:28.800 --> 00:10:31.580 align:start position:0% what we plan to do is we want to build a beacon<00:10:29.070> court<00:10:29.310> and<00:10:29.570> we<00:10:30.570> want<00:10:30.780> to<00:10:30.960> plug<00:10:31.410> their 00:10:31.580 --> 00:10:31.590 align:start position:0% beacon court and we want to plug their 00:10:31.590 --> 00:10:33.590 align:start position:0% beacon court and we want to plug their beacon<00:10:31.830> Kong<00:10:32.040> in<00:10:32.730> the<00:10:32.790> future<00:10:33.150> we<00:10:33.330> want<00:10:33.450> to 00:10:33.590 --> 00:10:33.600 align:start position:0% beacon Kong in the future we want to 00:10:33.600 --> 00:10:34.910 align:start position:0% beacon Kong in the future we want to plug<00:10:33.780> this<00:10:33.930> we<00:10:34.110> can<00:10:34.260> come<00:10:34.410> into<00:10:34.770> the 00:10:34.910 --> 00:10:34.920 align:start position:0% plug this we can come into the 00:10:34.920 --> 00:10:37.520 align:start position:0% plug this we can come into the Southfield<00:10:35.220> runtime<00:10:35.960> but<00:10:36.960> currently<00:10:37.260> we<00:10:37.440> are 00:10:37.520 --> 00:10:37.530 align:start position:0% Southfield runtime but currently we are 00:10:37.530 --> 00:10:40.850 align:start position:0% Southfield runtime but currently we are also<00:10:37.710> building<00:10:38.510> users<00:10:39.510> we<00:10:39.660> can<00:10:39.840> call<00:10:40.020> to<00:10:40.260> build 00:10:40.850 --> 00:10:40.860 align:start position:0% also building users we can call to build 00:10:40.860 --> 00:10:43.130 align:start position:0% also building users we can call to build a<00:10:41.040> subject<00:10:41.490> to<00:10:41.910> build<00:10:42.150> a<00:10:42.270> easy<00:10:42.720> improvement 00:10:43.130 --> 00:10:43.140 align:start position:0% a subject to build a easy improvement 00:10:43.140 --> 00:10:46.250 align:start position:0% a subject to build a easy improvement zero<00:10:43.290> current<00:10:43.650> without<00:10:44.040> sub<00:10:44.400> to<00:10:44.520> runtime<00:10:45.260> but 00:10:46.250 --> 00:10:46.260 align:start position:0% zero current without sub to runtime but 00:10:46.260 --> 00:10:47.960 align:start position:0% zero current without sub to runtime but we<00:10:46.380> are<00:10:46.470> still<00:10:46.620> trying<00:10:46.800> to<00:10:46.920> use<00:10:46.980> a<00:10:47.430> limited<00:10:47.790> set 00:10:47.960 --> 00:10:47.970 align:start position:0% we are still trying to use a limited set 00:10:47.970 --> 00:10:51.470 align:start position:0% we are still trying to use a limited set of<00:10:48.000> sub<00:10:48.420> components<00:10:49.140> so<00:10:49.290> that<00:10:49.560> we<00:10:50.490> can<00:10:50.700> reuse 00:10:51.470 --> 00:10:51.480 align:start position:0% of sub components so that we can reuse 00:10:51.480 --> 00:10:56.230 align:start position:0% of sub components so that we can reuse things<00:10:51.690> and<00:10:51.990> not<00:10:52.710> read<00:10:52.920> too<00:10:53.100> much<00:10:53.960> and<00:10:54.960> later 00:10:56.230 --> 00:10:56.240 align:start position:0% things and not read too much and later 00:10:56.240 --> 00:10:58.990 align:start position:0% things and not read too much and later still<00:10:57.240> use<00:10:57.420> it<00:10:57.600> it's<00:10:57.750> pecan<00:10:58.050> come<00:10:58.230> we<00:10:58.530> want<00:10:58.740> to 00:10:58.990 --> 00:10:59.000 align:start position:0% still use it it's pecan come we want to 00:10:59.000 --> 00:11:01.880 align:start position:0% still use it it's pecan come we want to appeal<00:11:00.000> the<00:11:00.180> footprint<00:11:00.930> amount<00:11:01.320> of<00:11:01.440> on<00:11:01.680> top 00:11:01.880 --> 00:11:01.890 align:start position:0% appeal the footprint amount of on top 00:11:01.890 --> 00:11:04.670 align:start position:0% appeal the footprint amount of on top weight<00:11:02.100> so<00:11:02.370> these<00:11:02.760> two<00:11:02.970> two 00:11:04.670 --> 00:11:04.680 align:start position:0% weight so these two two 00:11:04.680 --> 00:11:08.689 align:start position:0% weight so these two two to<00:11:05.339> plan<00:11:05.550> setup<00:11:05.699> is<00:11:06.060> basically<00:11:06.920> one<00:11:07.920> way<00:11:08.190> south 00:11:08.689 --> 00:11:08.699 align:start position:0% to plan setup is basically one way south 00:11:08.699 --> 00:11:13.819 align:start position:0% to plan setup is basically one way south to<00:11:08.850> run<00:11:09.029> time<00:11:09.240> and<00:11:09.480> another<00:11:09.990> is<00:11:10.259> not<00:11:10.519> and<00:11:12.829> we 00:11:13.819 --> 00:11:13.829 align:start position:0% to run time and another is not and we 00:11:13.829 --> 00:11:17.470 align:start position:0% to run time and another is not and we didn't<00:11:14.370> ruin<00:11:14.880> the<00:11:15.029> interrobang<00:11:15.660> site<00:11:16.019> but<00:11:16.259> I 00:11:17.470 --> 00:11:17.480 align:start position:0% didn't ruin the interrobang site but I 00:11:17.480 --> 00:11:21.410 align:start position:0% didn't ruin the interrobang site but I try<00:11:18.480> to<00:11:18.680> hack<00:11:19.680> hack<00:11:20.190> it<00:11:20.370> at<00:11:20.639> home<00:11:20.940> and<00:11:21.180> it's 00:11:21.410 --> 00:11:21.420 align:start position:0% try to hack hack it at home and it's 00:11:21.420 --> 00:11:28.819 align:start position:0% try to hack hack it at home and it's mostly<00:11:22.019> works<00:11:22.730> last<00:11:23.730> mass<00:11:24.920> so<00:11:27.649> so<00:11:28.649> basically 00:11:28.819 --> 00:11:28.829 align:start position:0% mostly works last mass so so basically 00:11:28.829 --> 00:11:33.350 align:start position:0% mostly works last mass so so basically we<00:11:29.339> are<00:11:29.399> talking<00:11:29.759> about<00:11:31.880> writing<00:11:32.880> generic 00:11:33.350 --> 00:11:33.360 align:start position:0% we are talking about writing generic 00:11:33.360 --> 00:11:37.340 align:start position:0% we are talking about writing generic clans<00:11:33.600> and<00:11:33.930> for<00:11:34.620> a<00:11:34.920> museum<00:11:35.370> to<00:11:35.610> one<00:11:35.759> zero<00:11:36.019> so<00:11:37.019> in 00:11:37.340 --> 00:11:37.350 align:start position:0% clans and for a museum to one zero so in 00:11:37.350 --> 00:11:39.970 align:start position:0% clans and for a museum to one zero so in the<00:11:37.500> beginning<00:11:37.649> we<00:11:37.949> have<00:11:38.160> fabric<00:11:38.730> as<00:11:38.910> per 00:11:39.970 --> 00:11:39.980 align:start position:0% the beginning we have fabric as per 00:11:39.980 --> 00:11:42.199 align:start position:0% the beginning we have fabric as per which<00:11:40.980> I'm<00:11:41.160> fortunate<00:11:41.370> we<00:11:41.699> need<00:11:41.880> to<00:11:41.970> abandon 00:11:42.199 --> 00:11:42.209 align:start position:0% which I'm fortunate we need to abandon 00:11:42.209 --> 00:11:46.670 align:start position:0% which I'm fortunate we need to abandon because<00:11:42.750> of<00:11:42.930> performance<00:11:43.110> issues<00:11:43.829> and<00:11:45.680> later 00:11:46.670 --> 00:11:46.680 align:start position:0% because of performance issues and later 00:11:46.680 --> 00:11:49.430 align:start position:0% because of performance issues and later we<00:11:47.069> decided<00:11:47.430> to<00:11:47.850> build<00:11:48.600> beacon<00:11:48.990> Chen<00:11:49.199> I'm 00:11:49.430 --> 00:11:49.440 align:start position:0% we decided to build beacon Chen I'm 00:11:49.440 --> 00:11:53.840 align:start position:0% we decided to build beacon Chen I'm subject<00:11:50.899> runtime<00:11:51.980> using<00:11:52.980> what<00:11:53.430> is<00:11:53.459> called<00:11:53.610> a 00:11:53.840 --> 00:11:53.850 align:start position:0% subject runtime using what is called a 00:11:53.850 --> 00:11:56.990 align:start position:0% subject runtime using what is called a wiper<00:11:54.060> block<00:11:54.800> in<00:11:55.800> this<00:11:55.980> way<00:11:56.190> we<00:11:56.339> can<00:11:56.550> reuse<00:11:56.819> all 00:11:56.990 --> 00:11:57.000 align:start position:0% wiper block in this way we can reuse all 00:11:57.000 --> 00:12:00.379 align:start position:0% wiper block in this way we can reuse all of<00:11:57.120> a<00:11:57.420> lot<00:11:58.019> of<00:11:58.139> the<00:11:58.319> sub<00:11:58.620> tree<00:11:58.649> components<00:11:59.389> and 00:12:00.379 --> 00:12:00.389 align:start position:0% of a lot of the sub tree components and 00:12:00.389 --> 00:12:02.629 align:start position:0% of a lot of the sub tree components and our<00:12:00.899> current<00:12:01.560> plan<00:12:01.800> is<00:12:02.009> to<00:12:02.190> build<00:12:02.370> a<00:12:02.579> bo 00:12:02.629 --> 00:12:02.639 align:start position:0% our current plan is to build a bo 00:12:02.639 --> 00:12:04.819 align:start position:0% our current plan is to build a bo clients<00:12:03.029> basically<00:12:03.300> the<00:12:03.930> first<00:12:04.170> client<00:12:04.589> is 00:12:04.819 --> 00:12:04.829 align:start position:0% clients basically the first client is 00:12:04.829 --> 00:12:07.550 align:start position:0% clients basically the first client is for<00:12:05.519> without<00:12:06.420> sub<00:12:06.660> to<00:12:06.779> run<00:12:06.959> time<00:12:07.139> to<00:12:07.290> catch<00:12:07.529> up 00:12:07.550 --> 00:12:07.560 align:start position:0% for without sub to run time to catch up 00:12:07.560 --> 00:12:10.579 align:start position:0% for without sub to run time to catch up with<00:12:07.939> the<00:12:08.939> magnetic<00:12:09.300> Elise<00:12:09.630> and<00:12:09.899> the<00:12:10.199> rest<00:12:10.439> of 00:12:10.579 --> 00:12:10.589 align:start position:0% with the magnetic Elise and the rest of 00:12:10.589 --> 00:12:13.460 align:start position:0% with the magnetic Elise and the rest of team<00:12:10.769> schedule<00:12:11.160> and<00:12:11.930> another<00:12:12.930> receptor 00:12:13.460 --> 00:12:13.470 align:start position:0% team schedule and another receptor 00:12:13.470 --> 00:12:15.670 align:start position:0% team schedule and another receptor runtime<00:12:13.980> so<00:12:14.189> we<00:12:14.310> can<00:12:14.490> continue<00:12:14.790> to<00:12:14.939> explore 00:12:15.670 --> 00:12:15.680 align:start position:0% runtime so we can continue to explore 00:12:15.680 --> 00:12:18.769 align:start position:0% runtime so we can continue to explore building<00:12:16.680> our<00:12:16.800> very<00:12:17.250> generic<00:12:17.730> block<00:12:18.540> chain 00:12:18.769 --> 00:12:18.779 align:start position:0% building our very generic block chain 00:12:18.779 --> 00:12:23.780 align:start position:0% building our very generic block chain framework<00:12:19.970> for<00:12:21.050> magazine<00:12:22.050> so<00:12:22.670> that's<00:12:23.670> all 00:12:23.780 --> 00:12:23.790 align:start position:0% framework for magazine so that's all 00:12:23.790 --> 00:12:25.210 align:start position:0% framework for magazine so that's all thank<00:12:24.480> you 00:12:25.210 --> 00:12:25.220 align:start position:0% thank you 00:12:25.220 --> 00:12:37.449 align:start position:0% thank you [Applause] 00:12:37.449 --> 00:12:37.459 align:start position:0% 00:12:37.459 --> 00:12:39.519 align:start position:0% you