WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.880 align:start position:0% [Applause] 00:00:10.880 --> 00:00:10.890 align:start position:0% 00:00:10.890 --> 00:00:13.560 align:start position:0% there's<00:00:11.890> some<00:00:12.100> time<00:00:12.340> steps<00:00:12.730> so<00:00:12.970> if<00:00:13.090> you<00:00:13.300> do 00:00:13.560 --> 00:00:13.570 align:start position:0% there's some time steps so if you do 00:00:13.570 --> 00:00:14.940 align:start position:0% there's some time steps so if you do have<00:00:13.750> to<00:00:13.870> leave<00:00:13.990> for<00:00:14.200> something<00:00:14.620> you<00:00:14.799> can 00:00:14.940 --> 00:00:14.950 align:start position:0% have to leave for something you can 00:00:14.950 --> 00:00:16.859 align:start position:0% have to leave for something you can still<00:00:15.130> come<00:00:15.340> back<00:00:15.460> and<00:00:15.670> know<00:00:15.820> what<00:00:16.540> time<00:00:16.720> you 00:00:16.859 --> 00:00:16.869 align:start position:0% still come back and know what time you 00:00:16.869 --> 00:00:19.170 align:start position:0% still come back and know what time you should<00:00:17.050> come<00:00:17.260> back<00:00:17.470> but<00:00:18.220> please<00:00:18.369> like<00:00:18.820> look<00:00:19.060> at 00:00:19.170 --> 00:00:19.180 align:start position:0% should come back but please like look at 00:00:19.180 --> 00:00:21.060 align:start position:0% should come back but please like look at those<00:00:19.360> times<00:00:19.720> you<00:00:19.930> know<00:00:20.080> somewhat<00:00:20.590> flexibly 00:00:21.060 --> 00:00:21.070 align:start position:0% those times you know somewhat flexibly 00:00:21.070 --> 00:00:23.670 align:start position:0% those times you know somewhat flexibly maybe<00:00:21.400> come<00:00:21.640> five<00:00:21.880> minutes<00:00:22.180> early<00:00:22.680> compared 00:00:23.670 --> 00:00:23.680 align:start position:0% maybe come five minutes early compared 00:00:23.680 --> 00:00:26.939 align:start position:0% maybe come five minutes early compared to<00:00:23.770> those<00:00:23.890> times<00:00:24.160> just<00:00:24.490> to<00:00:24.670> be<00:00:24.759> sure<00:00:25.710> so<00:00:26.710> first 00:00:26.939 --> 00:00:26.949 align:start position:0% to those times just to be sure so first 00:00:26.949 --> 00:00:29.820 align:start position:0% to those times just to be sure so first we're<00:00:27.400> gonna<00:00:27.550> have<00:00:27.850> a<00:00:28.180> lengthy<00:00:28.660> intro<00:00:29.050> on<00:00:29.320> what 00:00:29.820 --> 00:00:29.830 align:start position:0% we're gonna have a lengthy intro on what 00:00:29.830 --> 00:00:34.890 align:start position:0% we're gonna have a lengthy intro on what execution<00:00:30.699> and<00:00:31.000> a<00:00:31.150> 2.0<00:00:31.570> is<00:00:32.730> and<00:00:33.730> then<00:00:34.420> we<00:00:34.629> we 00:00:34.890 --> 00:00:34.900 align:start position:0% execution and a 2.0 is and then we we 00:00:34.900 --> 00:00:36.660 align:start position:0% execution and a 2.0 is and then we we have<00:00:35.140> some<00:00:35.350> explanation<00:00:35.559> on<00:00:35.890> the<00:00:36.040> toolkit<00:00:36.519> we 00:00:36.660 --> 00:00:36.670 align:start position:0% have some explanation on the toolkit we 00:00:36.670 --> 00:00:39.960 align:start position:0% have some explanation on the toolkit we have<00:00:36.850> which<00:00:37.150> is<00:00:37.330> called<00:00:37.540> scared<00:00:38.790> you<00:00:39.790> should 00:00:39.960 --> 00:00:39.970 align:start position:0% have which is called scared you should 00:00:39.970 --> 00:00:41.880 align:start position:0% have which is called scared you should be<00:00:40.120> really<00:00:40.480> safe<00:00:40.780> for<00:00:41.050> this<00:00:41.170> first<00:00:41.500> two<00:00:41.680> talks 00:00:41.880 --> 00:00:41.890 align:start position:0% be really safe for this first two talks 00:00:41.890 --> 00:00:43.799 align:start position:0% be really safe for this first two talks for<00:00:42.820> sure<00:00:43.030> because<00:00:43.239> that<00:00:43.510> gives<00:00:43.660> you<00:00:43.780> the 00:00:43.799 --> 00:00:43.809 align:start position:0% for sure because that gives you the 00:00:43.809 --> 00:00:45.690 align:start position:0% for sure because that gives you the background<00:00:44.260> what<00:00:44.469> this<00:00:44.620> is<00:00:44.800> and<00:00:45.430> Scott 00:00:45.690 --> 00:00:45.700 align:start position:0% background what this is and Scott 00:00:45.700 --> 00:00:48.360 align:start position:0% background what this is and Scott explains<00:00:46.149> to<00:00:46.270> you<00:00:46.360> how<00:00:46.390> you<00:00:46.600> can<00:00:47.020> write<00:00:47.350> any<00:00:48.219> of 00:00:48.360 --> 00:00:48.370 align:start position:0% explains to you how you can write any of 00:00:48.370 --> 00:00:49.590 align:start position:0% explains to you how you can write any of these<00:00:48.489> environments<00:00:49.059> how<00:00:49.180> you<00:00:49.239> can<00:00:49.420> test 00:00:49.590 --> 00:00:49.600 align:start position:0% these environments how you can test 00:00:49.600 --> 00:00:52.380 align:start position:0% these environments how you can test those<00:00:49.809> out<00:00:50.280> so<00:00:51.280> if<00:00:51.370> you<00:00:51.460> guys<00:00:51.610> are<00:00:51.670> developing 00:00:52.380 --> 00:00:52.390 align:start position:0% those out so if you guys are developing 00:00:52.390 --> 00:00:54.389 align:start position:0% those out so if you guys are developing or<00:00:52.600> want<00:00:52.930> to<00:00:53.050> develop<00:00:53.379> anything<00:00:53.559> on<00:00:53.829> e<00:00:53.980> 2.0 00:00:54.389 --> 00:00:54.399 align:start position:0% or want to develop anything on e 2.0 00:00:54.399 --> 00:00:56.340 align:start position:0% or want to develop anything on e 2.0 these<00:00:54.879> are<00:00:55.059> the<00:00:55.239> bare<00:00:55.690> minimum<00:00:56.140> you<00:00:56.320> should 00:00:56.340 --> 00:00:56.350 align:start position:0% these are the bare minimum you should 00:00:56.350 --> 00:00:59.010 align:start position:0% these are the bare minimum you should really<00:00:56.680> have<00:00:57.100> a<00:00:57.460> look<00:00:57.640> at<00:00:57.789> and<00:00:58.719> then<00:00:58.840> we're 00:00:59.010 --> 00:00:59.020 align:start position:0% really have a look at and then we're 00:00:59.020 --> 00:01:01.049 align:start position:0% really have a look at and then we're gonna<00:00:59.110> go<00:00:59.590> very<00:00:59.770> deep<00:01:00.039> into<00:01:00.250> a<00:01:00.730> lot<00:01:00.850> of<00:01:00.969> the 00:01:01.049 --> 00:01:01.059 align:start position:0% gonna go very deep into a lot of the 00:01:01.059 --> 00:01:02.790 align:start position:0% gonna go very deep into a lot of the research<00:01:01.420> we<00:01:01.690> have<00:01:01.719> done<00:01:01.899> on<00:01:02.289> execution 00:01:02.790 --> 00:01:02.800 align:start position:0% research we have done on execution 00:01:02.800 --> 00:01:05.580 align:start position:0% research we have done on execution environments<00:01:03.309> now<00:01:04.059> a<00:01:04.539> big<00:01:04.989> challenge<00:01:05.320> of 00:01:05.580 --> 00:01:05.590 align:start position:0% environments now a big challenge of 00:01:05.590 --> 00:01:07.859 align:start position:0% environments now a big challenge of execution<00:01:06.039> environments<00:01:06.490> is<00:01:06.670> which<00:01:07.360> TC<00:01:07.630> can 00:01:07.859 --> 00:01:07.869 align:start position:0% execution environments is which TC can 00:01:07.869 --> 00:01:10.160 align:start position:0% execution environments is which TC can explain<00:01:08.259> is<00:01:08.530> that<00:01:08.800> they<00:01:09.220> are<00:01:09.280> stateless<00:01:09.580> and 00:01:10.160 --> 00:01:10.170 align:start position:0% explain is that they are stateless and 00:01:10.170 --> 00:01:12.270 align:start position:0% explain is that they are stateless and therefore<00:01:11.170> we<00:01:11.289> need<00:01:11.410> to<00:01:11.560> transmit<00:01:11.920> all<00:01:12.160> the 00:01:12.270 --> 00:01:12.280 align:start position:0% therefore we need to transmit all the 00:01:12.280 --> 00:01:15.000 align:start position:0% therefore we need to transmit all the data<00:01:12.899> to<00:01:13.899> the<00:01:13.990> execution<00:01:14.380> environments<00:01:14.890> we 00:01:15.000 --> 00:01:15.010 align:start position:0% data to the execution environments we 00:01:15.010 --> 00:01:17.370 align:start position:0% data to the execution environments we need<00:01:15.189> to<00:01:15.670> perform<00:01:16.060> an<00:01:16.240> end<00:01:16.450> of<00:01:16.540> operation<00:01:17.020> and 00:01:17.370 --> 00:01:17.380 align:start position:0% need to perform an end of operation and 00:01:17.380 --> 00:01:20.310 align:start position:0% need to perform an end of operation and a<00:01:17.920> big<00:01:18.070> challenge<00:01:18.250> there<00:01:18.909> is<00:01:19.260> how<00:01:20.260> to 00:01:20.310 --> 00:01:20.320 align:start position:0% a big challenge there is how to 00:01:20.320 --> 00:01:22.590 align:start position:0% a big challenge there is how to efficiently<00:01:20.650> include<00:01:21.250> the<00:01:21.369> data<00:01:21.610> and<00:01:22.180> we<00:01:22.570> have 00:01:22.590 --> 00:01:22.600 align:start position:0% efficiently include the data and we have 00:01:22.600 --> 00:01:25.109 align:start position:0% efficiently include the data and we have a<00:01:22.720> couple<00:01:22.990> of<00:01:23.049> different<00:01:23.470> ways<00:01:24.280> to<00:01:24.520> do<00:01:24.610> that<00:01:24.820> so 00:01:25.109 --> 00:01:25.119 align:start position:0% a couple of different ways to do that so 00:01:25.119 --> 00:01:27.990 align:start position:0% a couple of different ways to do that so for<00:01:25.840> example<00:01:26.229> the<00:01:26.380> the<00:01:26.650> tufa<00:01:26.979> proof<00:01:27.250> is<00:01:27.460> one 00:01:27.990 --> 00:01:28.000 align:start position:0% for example the the tufa proof is one 00:01:28.000 --> 00:01:30.899 align:start position:0% for example the the tufa proof is one way<00:01:28.210> SSD<00:01:29.200> is<00:01:29.350> another<00:01:29.619> SS<00:01:30.009> is<00:01:30.159> another<00:01:30.460> way<00:01:30.670> and 00:01:30.899 --> 00:01:30.909 align:start position:0% way SSD is another SS is another way and 00:01:30.909 --> 00:01:33.210 align:start position:0% way SSD is another SS is another way and jungle<00:01:31.479> token<00:01:31.780> is<00:01:31.869> is<00:01:32.049> a<00:01:32.080> third<00:01:32.380> way<00:01:32.650> so<00:01:33.070> these 00:01:33.210 --> 00:01:33.220 align:start position:0% jungle token is is a third way so these 00:01:33.220 --> 00:01:35.160 align:start position:0% jungle token is is a third way so these tweets<00:01:33.610> hogs<00:01:33.880> can<00:01:34.240> explain<00:01:34.630> these<00:01:34.810> different 00:01:35.160 --> 00:01:35.170 align:start position:0% tweets hogs can explain these different 00:01:35.170 --> 00:01:36.810 align:start position:0% tweets hogs can explain these different ways<00:01:35.380> and<00:01:35.619> compare<00:01:36.070> them<00:01:36.220> against<00:01:36.549> each<00:01:36.640> other 00:01:36.810 --> 00:01:36.820 align:start position:0% ways and compare them against each other 00:01:36.820 --> 00:01:39.840 align:start position:0% ways and compare them against each other and<00:01:37.470> begin<00:01:38.470> at<00:01:38.770> the<00:01:38.890> end<00:01:39.040> concludes<00:01:39.610> me<00:01:39.790> the 00:01:39.840 --> 00:01:39.850 align:start position:0% and begin at the end concludes me the 00:01:39.850 --> 00:01:42.450 align:start position:0% and begin at the end concludes me the test<00:01:40.119> map<00:01:40.360> demo<00:01:40.570> which<00:01:41.439> I<00:01:41.770> have<00:01:42.130> something 00:01:42.450 --> 00:01:42.460 align:start position:0% test map demo which I have something 00:01:42.460 --> 00:01:45.450 align:start position:0% test map demo which I have something very<00:01:42.820> interesting<00:01:43.799> so<00:01:44.799> Casey<00:01:45.009> if<00:01:45.159> you<00:01:45.280> will 00:01:45.450 --> 00:01:45.460 align:start position:0% very interesting so Casey if you will 00:01:45.460 --> 00:01:48.420 align:start position:0% very interesting so Casey if you will start<00:01:46.270> up<00:01:46.420> it's<00:01:46.630> your<00:01:46.860> your<00:01:47.860> time<00:01:48.100> to<00:01:48.220> do<00:01:48.340> the 00:01:48.420 --> 00:01:48.430 align:start position:0% start up it's your your time to do the 00:01:48.430 --> 00:01:58.499 align:start position:0% start up it's your your time to do the first<00:01:48.579> talk<00:01:49.170> please<00:01:50.170> welcome<00:01:50.380> /<00:01:50.619> kc 00:01:58.499 --> 00:01:58.509 align:start position:0% 00:01:58.509 --> 00:02:06.280 align:start position:0% get<00:01:59.509> the<00:01:59.659> slides<00:01:59.899> please 00:02:06.280 --> 00:02:06.290 align:start position:0% 00:02:06.290 --> 00:02:09.190 align:start position:0% what<00:02:06.860> begin<00:02:07.160> to<00:02:07.280> sites<00:02:07.600> we<00:02:08.600> want<00:02:08.780> to<00:02:08.960> have<00:02:09.080> my 00:02:09.190 --> 00:02:09.200 align:start position:0% what begin to sites we want to have my 00:02:09.200 --> 00:02:13.030 align:start position:0% what begin to sites we want to have my just<00:02:09.470> specific<00:02:10.280> to<00:02:10.550> any<00:02:11.380> slots<00:02:12.380> probably 00:02:13.030 --> 00:02:13.040 align:start position:0% just specific to any slots probably 00:02:13.040 --> 00:02:14.710 align:start position:0% just specific to any slots probably gonna<00:02:13.190> have<00:02:13.400> some<00:02:13.430> to<00:02:13.880> anytime<00:02:14.330> at<00:02:14.540> three 00:02:14.710 --> 00:02:14.720 align:start position:0% gonna have some to anytime at three 00:02:14.720 --> 00:02:16.540 align:start position:0% gonna have some to anytime at three stuff<00:02:15.050> so<00:02:15.470> if<00:02:15.530> these<00:02:15.650> you<00:02:16.100> know<00:02:16.190> ask<00:02:16.370> your 00:02:16.540 --> 00:02:16.550 align:start position:0% stuff so if these you know ask your 00:02:16.550 --> 00:02:23.920 align:start position:0% stuff so if these you know ask your question 00:02:23.920 --> 00:02:23.930 align:start position:0% 00:02:23.930 --> 00:02:29.290 align:start position:0% so<00:02:24.860> when<00:02:25.220> trendy<00:02:25.820> I<00:02:26.950> mean<00:02:27.950> if<00:02:28.100> the<00:02:28.670> uncertainty 00:02:29.290 --> 00:02:29.300 align:start position:0% so when trendy I mean if the uncertainty 00:02:29.300 --> 00:02:31.480 align:start position:0% so when trendy I mean if the uncertainty around<00:02:29.510> the<00:02:29.900> timeline<00:02:30.650> in<00:02:30.800> the<00:02:30.890> architecture 00:02:31.480 --> 00:02:31.490 align:start position:0% around the timeline in the architecture 00:02:31.490 --> 00:02:33.670 align:start position:0% around the timeline in the architecture of<00:02:31.760> e<00:02:32.300> to<00:02:32.540> is<00:02:32.750> driving<00:02:33.170> you<00:02:33.260> a<00:02:33.290> little<00:02:33.560> bit 00:02:33.670 --> 00:02:33.680 align:start position:0% of e to is driving you a little bit 00:02:33.680 --> 00:02:37.980 align:start position:0% of e to is driving you a little bit crazy<00:02:34.900> try<00:02:35.900> being<00:02:36.140> a<00:02:36.380> poor<00:02:36.740> defense 00:02:37.980 --> 00:02:37.990 align:start position:0% crazy try being a poor defense 00:02:37.990 --> 00:02:43.780 align:start position:0% crazy try being a poor defense I'd<00:02:38.990> like<00:02:39.200> the<00:02:40.840> something<00:02:42.040> shoved<00:02:43.040> along<00:02:43.310> said 00:02:43.780 --> 00:02:43.790 align:start position:0% I'd like the something shoved along said 00:02:43.790 --> 00:02:47.800 align:start position:0% I'd like the something shoved along said he<00:02:44.000> organized<00:02:44.480> the<00:02:44.780> recent<00:02:45.230> era<00:02:45.380> and<00:02:46.810> the 00:02:47.800 --> 00:02:47.810 align:start position:0% he organized the recent era and the 00:02:47.810 --> 00:02:50.490 align:start position:0% he organized the recent era and the other<00:02:47.930> day<00:02:48.110> on<00:02:48.290> the<00:02:48.850> accession<00:02:49.850> he<00:02:50.150> said 00:02:50.490 --> 00:02:50.500 align:start position:0% other day on the accession he said 00:02:50.500 --> 00:02:52.570 align:start position:0% other day on the accession he said basically<00:02:51.500> we<00:02:51.740> could<00:02:51.950> come<00:02:52.130> to<00:02:52.220> the<00:02:52.310> interview 00:02:52.570 --> 00:02:52.580 align:start position:0% basically we could come to the interview 00:02:52.580 --> 00:02:57.580 align:start position:0% basically we could come to the interview join<00:02:53.510> the<00:02:53.630> cult<00:02:54.580> well<00:02:55.990> and<00:02:56.990> we<00:02:57.080> have<00:02:57.230> a<00:02:57.260> cult 00:02:57.580 --> 00:02:57.590 align:start position:0% join the cult well and we have a cult 00:02:57.590 --> 00:03:02.560 align:start position:0% join the cult well and we have a cult maybe<00:02:57.770> this<00:02:57.980> would<00:02:58.130> be<00:02:58.160> the<00:02:58.310> prayer<00:03:00.220> and<00:03:01.570> we're 00:03:02.560 --> 00:03:02.570 align:start position:0% maybe this would be the prayer and we're 00:03:02.570 --> 00:03:07.420 align:start position:0% maybe this would be the prayer and we're spraying<00:03:03.190> every<00:03:04.190> day<00:03:04.340> that<00:03:05.020> this<00:03:06.020> chaos<00:03:06.430> you 00:03:07.420 --> 00:03:07.430 align:start position:0% spraying every day that this chaos you 00:03:07.430 --> 00:03:10.150 align:start position:0% spraying every day that this chaos you know<00:03:07.550> well<00:03:07.940> spring<00:03:08.590> will<00:03:09.590> spring<00:03:09.830> forward 00:03:10.150 --> 00:03:10.160 align:start position:0% know well spring will spring forward 00:03:10.160 --> 00:03:18.160 align:start position:0% know well spring will spring forward some<00:03:10.370> sanity<00:03:10.850> and<00:03:11.920> some<00:03:12.920> serenity<00:03:14.800> so<00:03:17.020> when<00:03:18.020> is 00:03:18.160 --> 00:03:18.170 align:start position:0% some sanity and some serenity so when is 00:03:18.170 --> 00:03:20.440 align:start position:0% some sanity and some serenity so when is there<00:03:18.410> any<00:03:18.500> I<00:03:18.740> mean<00:03:18.770> coming<00:03:19.130> soon<00:03:19.520> the 00:03:20.440 --> 00:03:20.450 align:start position:0% there any I mean coming soon the 00:03:20.450 --> 00:03:29.410 align:start position:0% there any I mean coming soon the starting<00:03:20.810> is<00:03:20.930> coming<00:03:21.730> soon<00:03:22.730> since<00:03:23.120> 2015 00:03:29.410 --> 00:03:29.420 align:start position:0% 00:03:29.420 --> 00:03:32.110 align:start position:0% I<00:03:29.450> mean<00:03:30.260> there's<00:03:30.440> detailed<00:03:30.860> blog<00:03:31.070> post<00:03:31.370> since 00:03:32.110 --> 00:03:32.120 align:start position:0% I mean there's detailed blog post since 00:03:32.120 --> 00:03:35.140 align:start position:0% I mean there's detailed blog post since 2015<00:03:32.780> about<00:03:33.710> Casper<00:03:34.520> and<00:03:34.550> serenity<00:03:34.850> and<00:03:35.000> how 00:03:35.140 --> 00:03:35.150 align:start position:0% 2015 about Casper and serenity and how 00:03:35.150 --> 00:03:38.770 align:start position:0% 2015 about Casper and serenity and how it<00:03:35.210> work<00:03:36.430> and<00:03:37.430> actually<00:03:38.090> have<00:03:38.180> to<00:03:38.270> go<00:03:38.450> back<00:03:38.660> to 00:03:38.770 --> 00:03:38.780 align:start position:0% it work and actually have to go back to 00:03:38.780 --> 00:03:43.720 align:start position:0% it work and actually have to go back to this<00:03:38.900> bar<00:03:40.870> understand<00:03:41.870> you<00:03:42.590> know<00:03:42.710> where<00:03:43.130> the 00:03:43.720 --> 00:03:43.730 align:start position:0% this bar understand you know where the 00:03:43.730 --> 00:03:47.670 align:start position:0% this bar understand you know where the architecture<00:03:44.300> here<00:03:45.190> these<00:03:46.190> two<00:03:46.400> comes<00:03:46.670> from 00:03:47.670 --> 00:03:47.680 align:start position:0% architecture here these two comes from 00:03:47.680 --> 00:03:53.380 align:start position:0% architecture here these two comes from and<00:03:48.680> I<00:03:49.670> think<00:03:49.700> the<00:03:49.910> main<00:03:50.060> point<00:03:50.390> is<00:03:52.300> there<00:03:53.300> were 00:03:53.380 --> 00:03:53.390 align:start position:0% and I think the main point is there were 00:03:53.390 --> 00:03:57.010 align:start position:0% and I think the main point is there were two<00:03:53.420> betting<00:03:53.840> cycles<00:03:55.450> black<00:03:56.450> -<00:03:56.630> betting<00:03:56.960> the 00:03:57.010 --> 00:03:57.020 align:start position:0% two betting cycles black - betting the 00:03:57.020 --> 00:03:59.230 align:start position:0% two betting cycles black - betting the state<00:03:57.230> route<00:03:57.410> betting<00:03:57.740> this<00:03:58.460> is<00:03:58.640> when<00:03:58.790> you<00:03:59.180> get 00:03:59.230 --> 00:03:59.240 align:start position:0% state route betting this is when you get 00:03:59.240 --> 00:04:01.270 align:start position:0% state route betting this is when you get consensus<00:03:59.810> by<00:03:59.930> bet<00:04:00.230> was<00:04:00.560> one<00:04:00.890> of<00:04:00.980> those<00:04:01.100> call 00:04:01.270 --> 00:04:01.280 align:start position:0% consensus by bet was one of those call 00:04:01.280 --> 00:04:03.010 align:start position:0% consensus by bet was one of those call that<00:04:01.550> was<00:04:01.640> game<00:04:01.820> theory<00:04:02.090> then<00:04:02.540> turned<00:04:02.870> out 00:04:03.010 --> 00:04:03.020 align:start position:0% that was game theory then turned out 00:04:03.020 --> 00:04:06.130 align:start position:0% that was game theory then turned out well<00:04:03.580> traditional<00:04:04.580> computer<00:04:04.880> science<00:04:05.210> is 00:04:06.130 --> 00:04:06.140 align:start position:0% well traditional computer science is 00:04:06.140 --> 00:04:07.420 align:start position:0% well traditional computer science is more<00:04:06.350> secure<00:04:06.709> and<00:04:06.800> it's<00:04:06.920> worth<00:04:07.070> this<00:04:07.220> out 00:04:07.420 --> 00:04:07.430 align:start position:0% more secure and it's worth this out 00:04:07.430 --> 00:04:09.910 align:start position:0% more secure and it's worth this out better<00:04:07.670> so<00:04:07.910> maybe<00:04:08.090> just<00:04:08.480> do<00:04:08.959> something<00:04:09.200> PBMCs 00:04:09.910 --> 00:04:09.920 align:start position:0% better so maybe just do something PBMCs 00:04:09.920 --> 00:04:14.770 align:start position:0% better so maybe just do something PBMCs fire<00:04:10.250> that<00:04:10.550> became<00:04:10.790> Casper<00:04:11.209> FFG<00:04:13.450> but<00:04:14.450> the<00:04:14.630> main 00:04:14.770 --> 00:04:14.780 align:start position:0% fire that became Casper FFG but the main 00:04:14.780 --> 00:04:17.979 align:start position:0% fire that became Casper FFG but the main point<00:04:15.050> is<00:04:15.260> that<00:04:15.730> these<00:04:16.730> two<00:04:16.940> game<00:04:17.180> these<00:04:17.720> two 00:04:17.979 --> 00:04:17.989 align:start position:0% point is that these two game these two 00:04:17.989 --> 00:04:20.199 align:start position:0% point is that these two game these two processes<00:04:18.920> are<00:04:19.130> wonderful<00:04:19.670> different<00:04:20.030> types 00:04:20.199 --> 00:04:20.209 align:start position:0% processes are wonderful different types 00:04:20.209 --> 00:04:20.830 align:start position:0% processes are wonderful different types of<00:04:20.390> games 00:04:20.830 --> 00:04:20.840 align:start position:0% of games 00:04:20.840 --> 00:04:23.590 align:start position:0% of games once<00:04:21.739> the<00:04:21.890> consensus<00:04:22.370> game<00:04:22.580> the<00:04:23.180> other<00:04:23.330> one<00:04:23.480> is 00:04:23.590 --> 00:04:23.600 align:start position:0% once the consensus game the other one is 00:04:23.600 --> 00:04:25.990 align:start position:0% once the consensus game the other one is an<00:04:23.720> interactive<00:04:24.050> verification<00:04:24.830> game<00:04:25.000> they're 00:04:25.990 --> 00:04:26.000 align:start position:0% an interactive verification game they're 00:04:26.000 --> 00:04:27.160 align:start position:0% an interactive verification game they're fundamentally<00:04:26.450> different<00:04:26.810> because<00:04:26.840> the 00:04:27.160 --> 00:04:27.170 align:start position:0% fundamentally different because the 00:04:27.170 --> 00:04:28.930 align:start position:0% fundamentally different because the consensus<00:04:27.620> gave<00:04:27.770> is<00:04:27.950> not<00:04:28.100> deterministic 00:04:28.930 --> 00:04:28.940 align:start position:0% consensus gave is not deterministic 00:04:28.940 --> 00:04:30.790 align:start position:0% consensus gave is not deterministic and<00:04:29.030> the<00:04:29.180> internet<00:04:29.500> verification<00:04:30.500> game<00:04:30.620> is 00:04:30.790 --> 00:04:30.800 align:start position:0% and the internet verification game is 00:04:30.800 --> 00:04:36.820 align:start position:0% and the internet verification game is deterministic<00:04:33.490> this<00:04:34.490> realization<00:04:35.830> inspired 00:04:36.820 --> 00:04:36.830 align:start position:0% deterministic this realization inspired 00:04:36.830 --> 00:04:40.710 align:start position:0% deterministic this realization inspired the<00:04:38.110> architecture<00:04:39.110> the<00:04:39.530> phase<00:04:39.890> 1<00:04:40.190> phase<00:04:40.550> 2 00:04:40.710 --> 00:04:40.720 align:start position:0% the architecture the phase 1 phase 2 00:04:40.720 --> 00:04:46.300 align:start position:0% the architecture the phase 1 phase 2 architecture<00:04:44.410> phase<00:04:45.410> 1<00:04:45.620> is<00:04:45.770> the<00:04:45.860> consensus 00:04:46.300 --> 00:04:46.310 align:start position:0% architecture phase 1 is the consensus 00:04:46.310 --> 00:04:48.010 align:start position:0% architecture phase 1 is the consensus game<00:04:46.520> and<00:04:46.790> phase<00:04:47.060> 2<00:04:47.270> is<00:04:47.360> the<00:04:47.480> verification 00:04:48.010 --> 00:04:48.020 align:start position:0% game and phase 2 is the verification 00:04:48.020 --> 00:04:49.930 align:start position:0% game and phase 2 is the verification game<00:04:48.530> and<00:04:48.740> ideally<00:04:49.160> the<00:04:49.490> two<00:04:49.669> would<00:04:49.820> be 00:04:49.930 --> 00:04:49.940 align:start position:0% game and ideally the two would be 00:04:49.940 --> 00:04:56.939 align:start position:0% game and ideally the two would be decoupled 00:04:56.939 --> 00:04:56.949 align:start position:0% 00:04:56.949 --> 00:05:02.439 align:start position:0% and<00:04:57.949> as<00:04:58.070> all<00:04:58.190> this<00:04:58.310> was<00:04:58.370> happening<00:05:01.330> the<00:05:02.330> way 00:05:02.439 --> 00:05:02.449 align:start position:0% and as all this was happening the way 00:05:02.449 --> 00:05:07.000 align:start position:0% and as all this was happening the way the<00:05:02.660> the<00:05:03.290> roadmap<00:05:05.020> evolved<00:05:06.020> is<00:05:06.350> kind<00:05:06.620> of<00:05:06.710> messy 00:05:07.000 --> 00:05:07.010 align:start position:0% the the roadmap evolved is kind of messy 00:05:07.010 --> 00:05:11.850 align:start position:0% the the roadmap evolved is kind of messy but<00:05:07.449> it<00:05:08.449> was<00:05:08.570> really<00:05:08.780> in<00:05:08.960> this<00:05:09.050> link<00:05:09.260> this<00:05:10.600> June 00:05:11.850 --> 00:05:11.860 align:start position:0% but it was really in this link this June 00:05:11.860 --> 00:05:17.050 align:start position:0% but it was really in this link this June 2018<00:05:12.860> pivot<00:05:14.050> was<00:05:15.050> really<00:05:16.010> a<00:05:16.040> hero<00:05:16.280> Hail<00:05:16.760> Mary 00:05:17.050 --> 00:05:17.060 align:start position:0% 2018 pivot was really a hero Hail Mary 00:05:17.060 --> 00:05:19.150 align:start position:0% 2018 pivot was really a hero Hail Mary so<00:05:17.750> again<00:05:18.020> we're<00:05:18.199> just<00:05:18.229> praying<00:05:18.770> that<00:05:18.919> this 00:05:19.150 --> 00:05:19.160 align:start position:0% so again we're just praying that this 00:05:19.160 --> 00:05:24.270 align:start position:0% so again we're just praying that this thing<00:05:19.340> is<00:05:19.460> gonna<00:05:19.580> is<00:05:20.000> gonna<00:05:20.210> work<00:05:20.300> out<00:05:21.970> as<00:05:22.970> a 00:05:24.270 --> 00:05:24.280 align:start position:0% thing is gonna is gonna work out as a 00:05:24.280 --> 00:05:28.180 align:start position:0% thing is gonna is gonna work out as a Def<00:05:25.280> Con<00:05:25.610> last<00:05:25.910> year<00:05:26.270> this<00:05:26.600> was<00:05:26.900> the<00:05:27.290> late 00:05:28.180 --> 00:05:28.190 align:start position:0% Def Con last year this was the late 00:05:28.190 --> 00:05:33.040 align:start position:0% Def Con last year this was the late launch<00:05:28.940> plan<00:05:29.240> in<00:05:29.870> phase<00:05:30.260> one<00:05:31.090> we<00:05:32.090> would<00:05:32.360> launch 00:05:33.040 --> 00:05:33.050 align:start position:0% launch plan in phase one we would launch 00:05:33.050 --> 00:05:35.020 align:start position:0% launch plan in phase one we would launch phase<00:05:33.350> one<00:05:33.590> there<00:05:33.860> would<00:05:33.950> be<00:05:34.010> 1,000<00:05:34.700> charts 00:05:35.020 --> 00:05:35.030 align:start position:0% phase one there would be 1,000 charts 00:05:35.030 --> 00:05:36.340 align:start position:0% phase one there would be 1,000 charts that<00:05:35.210> Rashard<00:05:35.570> would<00:05:35.750> collect<00:05:35.990> lots<00:05:36.169> of<00:05:36.290> data 00:05:36.340 --> 00:05:36.350 align:start position:0% that Rashard would collect lots of data 00:05:36.350 --> 00:05:39.790 align:start position:0% that Rashard would collect lots of data blobs<00:05:36.880> and<00:05:38.200> probably<00:05:39.200> the<00:05:39.290> data<00:05:39.440> blocks<00:05:39.680> would 00:05:39.790 --> 00:05:39.800 align:start position:0% blobs and probably the data blocks would 00:05:39.800 --> 00:05:42.879 align:start position:0% blobs and probably the data blocks would be<00:05:39.950> filled<00:05:40.190> with<00:05:40.280> zero<00:05:40.520> bytes<00:05:41.590> so<00:05:42.590> that's 00:05:42.879 --> 00:05:42.889 align:start position:0% be filled with zero bytes so that's 00:05:42.889 --> 00:05:45.280 align:start position:0% be filled with zero bytes so that's phase<00:05:43.370> one<00:05:43.400> we<00:05:43.760> collect<00:05:44.030> data<00:05:44.600> blobs<00:05:44.870> and 00:05:45.280 --> 00:05:45.290 align:start position:0% phase one we collect data blobs and 00:05:45.290 --> 00:05:51.100 align:start position:0% phase one we collect data blobs and Phase<00:05:45.620> two<00:05:45.650> we<00:05:46.360> really<00:05:47.360> didn't<00:05:47.570> know<00:05:50.110> early 00:05:51.100 --> 00:05:51.110 align:start position:0% Phase two we really didn't know early 00:05:51.110 --> 00:05:53.500 align:start position:0% Phase two we really didn't know early 2019<00:05:51.410> is<00:05:51.830> crushed<00:05:52.130> did<00:05:52.550> all<00:05:52.669> these<00:05:52.820> like<00:05:53.090> basis 00:05:53.500 --> 00:05:53.510 align:start position:0% 2019 is crushed did all these like basis 00:05:53.510 --> 00:05:54.730 align:start position:0% 2019 is crushed did all these like basis depression<00:05:53.840> about-face<00:05:54.229> you<00:05:54.410> were<00:05:54.530> still 00:05:54.730 --> 00:05:54.740 align:start position:0% depression about-face you were still 00:05:54.740 --> 00:05:57.270 align:start position:0% depression about-face you were still open 00:05:57.270 --> 00:05:57.280 align:start position:0% 00:05:57.280 --> 00:06:04.900 align:start position:0% how<00:05:58.280> will<00:05:58.550> state<00:05:58.760> rad<00:05:58.970> work<00:06:02.860> will<00:06:03.860> there<00:06:04.520> will 00:06:04.900 --> 00:06:04.910 align:start position:0% how will state rad work will there will 00:06:04.910 --> 00:06:08.020 align:start position:0% how will state rad work will there will excuse<00:06:05.300> me<00:06:05.479> to<00:06:05.570> meet<00:06:05.750> or<00:06:06.020> Glade<00:06:06.320> will<00:06:07.010> there<00:06:07.700> be 00:06:08.020 --> 00:06:08.030 align:start position:0% excuse me to meet or Glade will there be 00:06:08.030 --> 00:06:10.659 align:start position:0% excuse me to meet or Glade will there be well<00:06:08.990> all<00:06:09.229> volunteers<00:06:09.740> are<00:06:09.889> scooped<00:06:10.100> lots<00:06:10.340> or 00:06:10.659 --> 00:06:10.669 align:start position:0% well all volunteers are scooped lots or 00:06:10.669 --> 00:06:12.420 align:start position:0% well all volunteers are scooped lots or will<00:06:10.789> they<00:06:10.880> just<00:06:11.090> you<00:06:11.570> know<00:06:11.599> provide 00:06:12.420 --> 00:06:12.430 align:start position:0% will they just you know provide 00:06:12.430 --> 00:06:14.860 align:start position:0% will they just you know provide consensus<00:06:13.430> on<00:06:13.580> the<00:06:13.669> data<00:06:13.880> availability<00:06:14.630> of 00:06:14.860 --> 00:06:14.870 align:start position:0% consensus on the data availability of 00:06:14.870 --> 00:06:17.350 align:start position:0% consensus on the data availability of the<00:06:14.930> blocks<00:06:15.340> pi<00:06:16.340> will<00:06:16.460> crush<00:06:16.639> our<00:06:16.789> calls<00:06:17.210> or 00:06:17.350 --> 00:06:17.360 align:start position:0% the blocks pi will crush our calls or 00:06:17.360 --> 00:06:19.300 align:start position:0% the blocks pi will crush our calls or these<00:06:17.630> we<00:06:18.560> didn't<00:06:18.710> have<00:06:18.800> answers<00:06:18.979> to<00:06:19.190> these 00:06:19.300 --> 00:06:19.310 align:start position:0% these we didn't have answers to these 00:06:19.310 --> 00:06:24.580 align:start position:0% these we didn't have answers to these questions<00:06:21.250> if<00:06:22.250> you<00:06:22.400> hear<00:06:22.610> the<00:06:23.200> phrase<00:06:24.200> phase 00:06:24.580 --> 00:06:24.590 align:start position:0% questions if you hear the phrase phase 00:06:24.590 --> 00:06:26.409 align:start position:0% questions if you hear the phrase phase one<00:06:24.830> and<00:06:24.919> done<00:06:25.130> what<00:06:25.789> it<00:06:25.910> refers<00:06:26.180> to<00:06:26.210> is 00:06:26.409 --> 00:06:26.419 align:start position:0% one and done what it refers to is 00:06:26.419 --> 00:06:32.409 align:start position:0% one and done what it refers to is beneath<00:06:27.260> research<00:06:27.650> posts<00:06:30.280> it's<00:06:31.280> not<00:06:31.490> really<00:06:32.150> a 00:06:32.409 --> 00:06:32.419 align:start position:0% beneath research posts it's not really a 00:06:32.419 --> 00:06:34.540 align:start position:0% beneath research posts it's not really a proposal<00:06:33.169> and<00:06:33.410> all<00:06:33.470> it<00:06:33.830> was<00:06:33.950> just<00:06:34.160> like<00:06:34.340> some 00:06:34.540 --> 00:06:34.550 align:start position:0% proposal and all it was just like some 00:06:34.550 --> 00:06:39.310 align:start position:0% proposal and all it was just like some ramblings<00:06:35.000> that<00:06:35.120> I<00:06:35.419> wrote<00:06:35.960> and<00:06:36.169> posted<00:06:36.590> and<00:06:38.320> it 00:06:39.310 --> 00:06:39.320 align:start position:0% ramblings that I wrote and posted and it 00:06:39.320 --> 00:06:42.490 align:start position:0% ramblings that I wrote and posted and it you<00:06:40.250> probably<00:06:40.400> never<00:06:40.760> even<00:06:41.229> when<00:06:42.229> I've<00:06:42.349> heard 00:06:42.490 --> 00:06:42.500 align:start position:0% you probably never even when I've heard 00:06:42.500 --> 00:06:44.560 align:start position:0% you probably never even when I've heard about<00:06:42.590> it<00:06:42.860> unless<00:06:43.220> you<00:06:43.400> are<00:06:43.669> a<00:06:44.120> religious 00:06:44.560 --> 00:06:44.570 align:start position:0% about it unless you are a religious 00:06:44.570 --> 00:06:49.000 align:start position:0% about it unless you are a religious scholar<00:06:44.720> he's<00:06:45.349> research<00:06:46.660> but<00:06:48.010> metallic 00:06:49.000 --> 00:06:49.010 align:start position:0% scholar he's research but metallic 00:06:49.010 --> 00:06:51.580 align:start position:0% scholar he's research but metallic responded<00:06:49.490> to<00:06:49.610> it<00:06:49.789> sixteen<00:06:50.570> days<00:06:50.660> later<00:06:50.930> so 00:06:51.580 --> 00:06:51.590 align:start position:0% responded to it sixteen days later so 00:06:51.590 --> 00:06:53.680 align:start position:0% responded to it sixteen days later so thanks<00:06:52.190> for<00:06:52.280> talking<00:06:52.400> I<00:06:52.610> think<00:06:52.669> that's<00:06:52.940> why<00:06:53.090> it 00:06:53.680 --> 00:06:53.690 align:start position:0% thanks for talking I think that's why it 00:06:53.690 --> 00:06:58.550 align:start position:0% thanks for talking I think that's why it started<00:06:54.020> getting<00:06:54.229> correction<00:06:54.620> as<00:06:54.710> a<00:06:54.740> mean 00:06:58.550 --> 00:06:58.560 align:start position:0% 00:06:58.560 --> 00:07:01.320 align:start position:0% the<00:06:59.560> philosophy<00:07:00.100> and<00:07:00.130> approach<00:07:00.250> of<00:07:00.490> phase<00:07:01.090> one 00:07:01.320 --> 00:07:01.330 align:start position:0% the philosophy and approach of phase one 00:07:01.330 --> 00:07:04.890 align:start position:0% the philosophy and approach of phase one and<00:07:01.420> done<00:07:01.600> is<00:07:01.930> basically<00:07:02.680> we<00:07:03.520> start<00:07:03.820> did<00:07:04.810> we 00:07:04.890 --> 00:07:04.900 align:start position:0% and done is basically we start did we 00:07:04.900 --> 00:07:05.820 align:start position:0% and done is basically we start did we just<00:07:05.020> start<00:07:05.170> answering<00:07:05.350> some<00:07:05.590> of<00:07:05.710> these 00:07:05.820 --> 00:07:05.830 align:start position:0% just start answering some of these 00:07:05.830 --> 00:07:08.490 align:start position:0% just start answering some of these questions<00:07:05.890> so<00:07:06.370> how<00:07:06.760> will<00:07:07.180> stare<00:07:07.390> at<00:07:07.540> work<00:07:07.690> it 00:07:08.490 --> 00:07:08.500 align:start position:0% questions so how will stare at work it 00:07:08.500 --> 00:07:10.650 align:start position:0% questions so how will stare at work it won't<00:07:08.770> because<00:07:09.370> their<00:07:09.940> own<00:07:10.090> beanie<00:07:10.300> States 00:07:10.650 --> 00:07:10.660 align:start position:0% won't because their own beanie States 00:07:10.660 --> 00:07:12.840 align:start position:0% won't because their own beanie States gonna<00:07:10.870> be<00:07:11.050> stateless<00:07:11.320> it's<00:07:12.070> like<00:07:12.220> way<00:07:12.460> simpler 00:07:12.840 --> 00:07:12.850 align:start position:0% gonna be stateless it's like way simpler 00:07:12.850 --> 00:07:15.750 align:start position:0% gonna be stateless it's like way simpler you<00:07:13.810> know<00:07:13.840> I<00:07:13.930> think<00:07:14.050> that's<00:07:14.320> a<00:07:14.760> commonly 00:07:15.750 --> 00:07:15.760 align:start position:0% you know I think that's a commonly 00:07:15.760 --> 00:07:18.630 align:start position:0% you know I think that's a commonly accepted<00:07:15.850> now<00:07:16.740> it's<00:07:17.740> going<00:07:17.980> to<00:07:18.040> be<00:07:18.160> a<00:07:18.400> meeting 00:07:18.630 --> 00:07:18.640 align:start position:0% accepted now it's going to be a meeting 00:07:18.640 --> 00:07:22.250 align:start position:0% accepted now it's going to be a meeting execution<00:07:19.210> just<00:07:19.240> like<00:07:19.750> eath<00:07:19.900> one<00:07:20.460> simpler 00:07:22.250 --> 00:07:22.260 align:start position:0% execution just like eath one simpler 00:07:22.260 --> 00:07:24.510 align:start position:0% execution just like eath one simpler Valhalla<00:07:23.260> volunteers<00:07:23.740> be<00:07:23.860> able<00:07:24.040> to<00:07:24.100> keep<00:07:24.250> the 00:07:24.510 --> 00:07:24.520 align:start position:0% Valhalla volunteers be able to keep the 00:07:24.520 --> 00:07:28.680 align:start position:0% Valhalla volunteers be able to keep the executors<00:07:25.210> yes<00:07:25.510> and<00:07:27.060> how<00:07:28.060> will<00:07:28.210> cross<00:07:28.420> shard 00:07:28.680 --> 00:07:28.690 align:start position:0% executors yes and how will cross shard 00:07:28.690 --> 00:07:31.680 align:start position:0% executors yes and how will cross shard the<00:07:29.260> calls<00:07:29.500> work<00:07:29.830> they're<00:07:30.760> gonna<00:07:30.850> work<00:07:31.120> great 00:07:31.680 --> 00:07:31.690 align:start position:0% the calls work they're gonna work great 00:07:31.690 --> 00:07:37.830 align:start position:0% the calls work they're gonna work great ok<00:07:32.050> don't<00:07:32.200> worry 00:07:37.830 --> 00:07:37.840 align:start position:0% 00:07:37.840 --> 00:07:42.010 align:start position:0% and<00:07:38.840> the<00:07:39.020> philosophy<00:07:39.170> is<00:07:39.560> really<00:07:40.600> just<00:07:41.600> like 00:07:42.010 --> 00:07:42.020 align:start position:0% and the philosophy is really just like 00:07:42.020 --> 00:07:45.010 align:start position:0% and the philosophy is really just like start<00:07:42.470> simple<00:07:42.890> keep<00:07:43.280> execution<00:07:43.820> minimum<00:07:44.180> you 00:07:45.010 --> 00:07:45.020 align:start position:0% start simple keep execution minimum you 00:07:45.020 --> 00:07:46.680 align:start position:0% start simple keep execution minimum you know<00:07:45.140> don't<00:07:45.500> try<00:07:45.590> to<00:07:45.650> answer<00:07:45.860> every<00:07:46.100> question 00:07:46.680 --> 00:07:46.690 align:start position:0% know don't try to answer every question 00:07:46.690 --> 00:07:49.810 align:start position:0% know don't try to answer every question just<00:07:47.690> get<00:07:48.110> something<00:07:48.350> basic<00:07:48.890> like<00:07:49.040> working 00:07:49.810 --> 00:07:49.820 align:start position:0% just get something basic like working 00:07:49.820 --> 00:07:52.000 align:start position:0% just get something basic like working you<00:07:50.450> know<00:07:50.540> a<00:07:50.570> basic<00:07:50.960> prototype<00:07:51.170> so<00:07:51.680> we 00:07:52.000 --> 00:07:52.010 align:start position:0% you know a basic prototype so we 00:07:52.010 --> 00:07:53.230 align:start position:0% you know a basic prototype so we piggyback<00:07:52.490> on<00:07:52.700> the<00:07:52.730> existing<00:07:53.210> data 00:07:53.230 --> 00:07:53.240 align:start position:0% piggyback on the existing data 00:07:53.240 --> 00:07:56.320 align:start position:0% piggyback on the existing data structures<00:07:53.870> the<00:07:54.110> beacon<00:07:54.410> state<00:07:55.060> data<00:07:56.060> code 00:07:56.320 --> 00:07:56.330 align:start position:0% structures the beacon state data code 00:07:56.330 --> 00:07:58.300 align:start position:0% structures the beacon state data code fields<00:07:56.690> in<00:07:56.810> the<00:07:56.870> validator<00:07:57.260> accounts<00:07:57.650> okay 00:07:58.300 --> 00:07:58.310 align:start position:0% fields in the validator accounts okay 00:07:58.310 --> 00:08:01.330 align:start position:0% fields in the validator accounts okay that's<00:07:58.580> what<00:07:58.730> keys<00:07:59.090> are<00:08:00.130> and<00:08:01.130> then<00:08:01.280> you 00:08:01.330 --> 00:08:01.340 align:start position:0% that's what keys are and then you 00:08:01.340 --> 00:08:02.880 align:start position:0% that's what keys are and then you execute<00:08:01.760> the<00:08:01.880> code<00:08:02.030> and<00:08:02.180> the<00:08:02.270> shared<00:08:02.480> blocks 00:08:02.880 --> 00:08:02.890 align:start position:0% execute the code and the shared blocks 00:08:02.890 --> 00:08:05.260 align:start position:0% execute the code and the shared blocks when<00:08:03.890> you<00:08:03.950> turn<00:08:04.130> the<00:08:04.220> state<00:08:04.430> root<00:08:04.640> keeps 00:08:05.260 --> 00:08:05.270 align:start position:0% when you turn the state root keeps 00:08:05.270 --> 00:08:09.700 align:start position:0% when you turn the state root keeps everything<00:08:05.540> stateless<00:08:06.970> and<00:08:08.260> so<00:08:09.260> basically<00:08:09.530> in 00:08:09.700 --> 00:08:09.710 align:start position:0% everything stateless and so basically in 00:08:09.710 --> 00:08:12.220 align:start position:0% everything stateless and so basically in the<00:08:09.770> post<00:08:09.980> I<00:08:10.100> argue<00:08:10.430> that<00:08:10.510> when<00:08:11.510> you<00:08:11.840> have 00:08:12.220 --> 00:08:12.230 align:start position:0% the post I argue that when you have 00:08:12.230 --> 00:08:15.220 align:start position:0% the post I argue that when you have minimal<00:08:12.620> execution<00:08:13.340> you<00:08:14.030> know<00:08:14.150> coupled<00:08:14.990> to 00:08:15.220 --> 00:08:15.230 align:start position:0% minimal execution you know coupled to 00:08:15.230 --> 00:08:20.260 align:start position:0% minimal execution you know coupled to these<00:08:15.590> phase<00:08:16.010> one<00:08:17.530> shard<00:08:18.530> blocks<00:08:18.770> it's<00:08:19.130> a<00:08:19.340> 10x 00:08:20.260 --> 00:08:20.270 align:start position:0% these phase one shard blocks it's a 10x 00:08:20.270 --> 00:08:24.970 align:start position:0% these phase one shard blocks it's a 10x improvement<00:08:20.420> over<00:08:22.270> or<00:08:23.270> if<00:08:23.660> you<00:08:23.780> just<00:08:24.020> have<00:08:24.290> you 00:08:24.970 --> 00:08:24.980 align:start position:0% improvement over or if you just have you 00:08:24.980 --> 00:08:26.860 align:start position:0% improvement over or if you just have you know<00:08:25.010> phase<00:08:25.670> one<00:08:25.940> as<00:08:26.120> the<00:08:26.210> data<00:08:26.420> availability 00:08:26.860 --> 00:08:26.870 align:start position:0% know phase one as the data availability 00:08:26.870 --> 00:08:32.620 align:start position:0% know phase one as the data availability engine<00:08:27.290> without<00:08:27.470> execution<00:08:30.880> so<00:08:31.880> again<00:08:32.180> you 00:08:32.620 --> 00:08:32.630 align:start position:0% engine without execution so again you 00:08:32.630 --> 00:08:35.440 align:start position:0% engine without execution so again you start<00:08:32.900> simple<00:08:33.200> and<00:08:33.320> easy<00:08:33.500> I<00:08:34.150> like<00:08:35.150> the<00:08:35.240> term 00:08:35.440 --> 00:08:35.450 align:start position:0% start simple and easy I like the term 00:08:35.450 --> 00:08:36.940 align:start position:0% start simple and easy I like the term phase<00:08:35.660> when<00:08:35.840> I'm<00:08:35.930> done<00:08:36.020> because<00:08:36.229> it's<00:08:36.710> like 00:08:36.940 --> 00:08:36.950 align:start position:0% phase when I'm done because it's like 00:08:36.950 --> 00:08:39.730 align:start position:0% phase when I'm done because it's like the<00:08:37.640> execution<00:08:38.180> is<00:08:38.450> coupled<00:08:38.930> to<00:08:38.960> consensus<00:08:39.590> so 00:08:39.730 --> 00:08:39.740 align:start position:0% the execution is coupled to consensus so 00:08:39.740 --> 00:08:42.700 align:start position:0% the execution is coupled to consensus so the<00:08:39.860> old<00:08:40.010> architecture<00:08:40.419> with<00:08:41.419> phase<00:08:41.990> two<00:08:42.290> and 00:08:42.700 --> 00:08:42.710 align:start position:0% the old architecture with phase two and 00:08:42.710 --> 00:08:47.200 align:start position:0% the old architecture with phase two and phase<00:08:43.120> one<00:08:44.120> decoupled<00:08:44.960> I<00:08:45.340> mean<00:08:46.340> if<00:08:47.060> the 00:08:47.200 --> 00:08:47.210 align:start position:0% phase one decoupled I mean if the 00:08:47.210 --> 00:08:50.170 align:start position:0% phase one decoupled I mean if the execution<00:08:47.630> is<00:08:47.840> in<00:08:48.020> phase<00:08:48.290> one<00:08:48.590> then<00:08:49.100> just<00:08:49.760> you 00:08:50.170 --> 00:08:50.180 align:start position:0% execution is in phase one then just you 00:08:50.180 --> 00:08:53.080 align:start position:0% execution is in phase one then just you know<00:08:50.270> just<00:08:50.600> say<00:08:50.750> that<00:08:50.960> I<00:08:51.140> don't<00:08:52.000> anyway<00:08:53.000> and 00:08:53.080 --> 00:08:53.090 align:start position:0% know just say that I don't anyway and 00:08:53.090 --> 00:08:54.850 align:start position:0% know just say that I don't anyway and you<00:08:53.150> punt<00:08:53.660> the<00:08:53.750> hard<00:08:53.900> question<00:08:54.290> so<00:08:54.470> we<00:08:54.560> put<00:08:54.770> the 00:08:54.850 --> 00:08:54.860 align:start position:0% you punt the hard question so we put the 00:08:54.860 --> 00:08:57.970 align:start position:0% you punt the hard question so we put the hard<00:08:55.010> questions<00:08:55.400> about<00:08:56.290> crosshair<00:08:57.290> calls<00:08:57.560> and 00:08:57.970 --> 00:08:57.980 align:start position:0% hard questions about crosshair calls and 00:08:57.980 --> 00:09:00.640 align:start position:0% hard questions about crosshair calls and you<00:08:58.310> know<00:08:58.370> so<00:08:58.670> forth<00:08:59.260> help<00:09:00.260> to<00:09:00.470> the 00:09:00.640 --> 00:09:00.650 align:start position:0% you know so forth help to the 00:09:00.650 --> 00:09:02.320 align:start position:0% you know so forth help to the application<00:09:01.250> layer<00:09:01.280> because<00:09:01.820> now<00:09:02.030> you're 00:09:02.320 --> 00:09:02.330 align:start position:0% application layer because now you're 00:09:02.330 --> 00:09:05.800 align:start position:0% application layer because now you're implementing<00:09:02.750> this<00:09:02.960> logic<00:09:03.940> in<00:09:04.940> wasum<00:09:05.510> you 00:09:05.800 --> 00:09:05.810 align:start position:0% implementing this logic in wasum you 00:09:05.810 --> 00:09:07.510 align:start position:0% implementing this logic in wasum you know<00:09:05.900> it's<00:09:06.110> not<00:09:06.260> really<00:09:06.470> in<00:09:06.710> the<00:09:06.950> core 00:09:07.510 --> 00:09:07.520 align:start position:0% know it's not really in the core 00:09:07.520 --> 00:09:10.480 align:start position:0% know it's not really in the core protocol<00:09:08.000> is<00:09:08.210> it<00:09:08.420> I<00:09:08.630> mean<00:09:08.960> it's<00:09:09.200> like<00:09:09.350> possible 00:09:10.480 --> 00:09:10.490 align:start position:0% protocol is it I mean it's like possible 00:09:10.490 --> 00:09:12.280 align:start position:0% protocol is it I mean it's like possible and<00:09:10.580> do<00:09:10.670> any<00:09:10.790> ease<00:09:11.150> whatever<00:09:11.570> you<00:09:11.780> can<00:09:12.140> do 00:09:12.280 --> 00:09:12.290 align:start position:0% and do any ease whatever you can do 00:09:12.290 --> 00:09:14.260 align:start position:0% and do any ease whatever you can do whatever<00:09:12.920> you<00:09:13.130> can<00:09:13.190> implement<00:09:13.430> relate 00:09:14.260 --> 00:09:14.270 align:start position:0% whatever you can implement relate 00:09:14.270 --> 00:09:20.770 align:start position:0% whatever you can implement relate contracts<00:09:14.750> unease<00:09:15.440> one<00:09:15.730> so<00:09:19.240> so<00:09:20.240> yeah<00:09:20.480> I<00:09:20.510> mean 00:09:20.770 --> 00:09:20.780 align:start position:0% contracts unease one so so yeah I mean 00:09:20.780 --> 00:09:22.690 align:start position:0% contracts unease one so so yeah I mean so<00:09:20.990> you<00:09:21.050> put<00:09:21.260> those<00:09:21.350> hard<00:09:21.590> questions<00:09:21.740> where 00:09:22.690 --> 00:09:22.700 align:start position:0% so you put those hard questions where 00:09:22.700 --> 00:09:24.490 align:start position:0% so you put those hard questions where researchers<00:09:23.360> can<00:09:23.420> keep<00:09:23.750> circling<00:09:24.140> and 00:09:24.490 --> 00:09:24.500 align:start position:0% researchers can keep circling and 00:09:24.500 --> 00:09:29.020 align:start position:0% researchers can keep circling and whiteboarding<00:09:24.950> and<00:09:26.560> you<00:09:27.560> know<00:09:27.680> in<00:09:28.310> the 00:09:29.020 --> 00:09:29.030 align:start position:0% whiteboarding and you know in the 00:09:29.030 --> 00:09:30.460 align:start position:0% whiteboarding and you know in the meantime<00:09:29.210> we<00:09:29.540> decided<00:09:29.930> to<00:09:30.050> building<00:09:30.380> and 00:09:30.460 --> 00:09:30.470 align:start position:0% meantime we decided to building and 00:09:30.470 --> 00:09:32.710 align:start position:0% meantime we decided to building and prototyping<00:09:30.980> with<00:09:31.220> like<00:09:31.490> you<00:09:32.150> know<00:09:32.270> we<00:09:32.510> can<00:09:32.630> we 00:09:32.710 --> 00:09:32.720 align:start position:0% prototyping with like you know we can we 00:09:32.720 --> 00:09:37.080 align:start position:0% prototyping with like you know we can we have<00:09:32.750> something<00:09:33.170> concrete<00:09:33.440> to<00:09:33.740> work<00:09:33.920> with 00:09:37.080 --> 00:09:37.090 align:start position:0% 00:09:37.090 --> 00:09:39.310 align:start position:0% recently<00:09:38.090> I<00:09:38.180> don't<00:09:38.330> know<00:09:38.420> this<00:09:38.810> is<00:09:39.110> where 00:09:39.310 --> 00:09:39.320 align:start position:0% recently I don't know this is where 00:09:39.320 --> 00:09:46.360 align:start position:0% recently I don't know this is where composability<00:09:40.240> what<00:09:41.240> composability<00:09:45.370> it 00:09:46.360 --> 00:09:46.370 align:start position:0% composability what composability it 00:09:46.370 --> 00:09:49.360 align:start position:0% composability what composability it sounds<00:09:46.910> like<00:09:47.120> composability<00:09:48.050> it's<00:09:49.040> like 00:09:49.360 --> 00:09:49.370 align:start position:0% sounds like composability it's like 00:09:49.370 --> 00:09:51.340 align:start position:0% sounds like composability it's like charting<00:09:49.730> is<00:09:49.790> gonna<00:09:49.940> break<00:09:50.210> impose<00:09:50.840> ability 00:09:51.340 --> 00:09:51.350 align:start position:0% charting is gonna break impose ability 00:09:51.350 --> 00:09:55.570 align:start position:0% charting is gonna break impose ability this<00:09:52.340> sounds<00:09:52.730> like<00:09:52.790> news<00:09:53.210> from<00:09:54.140> 2015<00:09:54.950> if<00:09:55.400> you 00:09:55.570 --> 00:09:55.580 align:start position:0% this sounds like news from 2015 if you 00:09:55.580 --> 00:09:57.250 align:start position:0% this sounds like news from 2015 if you were<00:09:55.700> paying<00:09:55.880> attention<00:09:56.000> this<00:09:56.450> this<00:09:57.050> is<00:09:57.230> a 00:09:57.250 --> 00:09:57.260 align:start position:0% were paying attention this this is a 00:09:57.260 --> 00:10:00.670 align:start position:0% were paying attention this this is a metallic<00:09:58.010> stock<00:09:58.400> from<00:09:58.940> 2015<00:09:59.600> a<00:09:59.630> DEFCON<00:09:59.990> one 00:10:00.670 --> 00:10:00.680 align:start position:0% metallic stock from 2015 a DEFCON one 00:10:00.680 --> 00:10:03.550 align:start position:0% metallic stock from 2015 a DEFCON one I<00:10:00.710> just<00:10:01.340> think<00:10:01.550> in<00:10:01.640> the<00:10:01.760> text<00:10:02.390> that<00:10:02.420> was<00:10:03.140> on<00:10:03.320> his 00:10:03.550 --> 00:10:03.560 align:start position:0% I just think in the text that was on his 00:10:03.560 --> 00:10:05.230 align:start position:0% I just think in the text that was on his slide<00:10:03.800> and<00:10:04.220> put<00:10:04.400> it<00:10:04.460> up<00:10:04.550> here<00:10:04.730> so<00:10:04.820> you<00:10:04.880> can<00:10:05.060> read 00:10:05.230 --> 00:10:05.240 align:start position:0% slide and put it up here so you can read 00:10:05.240 --> 00:10:07.140 align:start position:0% slide and put it up here so you can read it<00:10:05.410> okay 00:10:07.140 --> 00:10:07.150 align:start position:0% it okay 00:10:07.150 --> 00:10:10.180 align:start position:0% it okay ugly<00:10:08.150> call<00:10:09.140> that<00:10:09.320> code<00:10:09.560> per<00:10:09.740> second<00:10:10.040> this<00:10:10.130> is 00:10:10.180 --> 00:10:10.190 align:start position:0% ugly call that code per second this is 00:10:10.190 --> 00:10:12.300 align:start position:0% ugly call that code per second this is like<00:10:10.400> referring<00:10:10.790> to<00:10:11.030> a<00:10:11.060> synchronous<00:10:11.600> charts 00:10:12.300 --> 00:10:12.310 align:start position:0% like referring to a synchronous charts 00:10:12.310 --> 00:10:14.680 align:start position:0% like referring to a synchronous charts that's<00:10:13.310> what<00:10:13.670> people<00:10:13.790> mean<00:10:14.000> by<00:10:14.060> freaking 00:10:14.680 --> 00:10:14.690 align:start position:0% that's what people mean by freaking 00:10:14.690 --> 00:10:17.470 align:start position:0% that's what people mean by freaking composability<00:10:15.320> right<00:10:15.680> that<00:10:16.210> cross<00:10:17.210> chart 00:10:17.470 --> 00:10:17.480 align:start position:0% composability right that cross chart 00:10:17.480 --> 00:10:21.970 align:start position:0% composability right that cross chart calls<00:10:17.930> are<00:10:18.140> gonna<00:10:18.230> be<00:10:18.380> asynchronous<00:10:20.860> so<00:10:21.860> he 00:10:21.970 --> 00:10:21.980 align:start position:0% calls are gonna be asynchronous so he 00:10:21.980 --> 00:10:24.250 align:start position:0% calls are gonna be asynchronous so he went<00:10:22.220> he<00:10:22.490> walked<00:10:22.970> through<00:10:23.330> how<00:10:23.930> this<00:10:24.050> might 00:10:24.250 --> 00:10:24.260 align:start position:0% went he walked through how this might 00:10:24.260 --> 00:10:26.740 align:start position:0% went he walked through how this might work<00:10:24.290> was<00:10:24.830> an<00:10:24.950> async<00:10:25.340> call<00:10:25.550> an<00:10:25.850> async<00:10:26.210> blog<00:10:26.450> and 00:10:26.740 --> 00:10:26.750 align:start position:0% work was an async call an async blog and 00:10:26.750 --> 00:10:31.930 align:start position:0% work was an async call an async blog and in<00:10:26.810> sync<00:10:27.050> callback<00:10:27.470> and<00:10:29.830> but<00:10:30.830> then<00:10:31.040> you<00:10:31.850> know 00:10:31.930 --> 00:10:31.940 align:start position:0% in sync callback and but then you know 00:10:31.940 --> 00:10:34.360 align:start position:0% in sync callback and but then you know the<00:10:32.030> 2015<00:10:32.570> 2018<00:10:33.440> he<00:10:33.650> has<00:10:33.740> this<00:10:33.860> other<00:10:34.070> post 00:10:34.360 --> 00:10:34.370 align:start position:0% the 2015 2018 he has this other post 00:10:34.370 --> 00:10:36.510 align:start position:0% the 2015 2018 he has this other post about<00:10:34.880> how<00:10:35.090> you<00:10:35.150> could<00:10:35.390> do<00:10:35.510> it<00:10:35.660> synchronous 00:10:36.510 --> 00:10:36.520 align:start position:0% about how you could do it synchronous 00:10:36.520 --> 00:10:40.320 align:start position:0% about how you could do it synchronous crusher<00:10:37.520> called<00:10:37.790> so<00:10:38.090> this<00:10:38.870> is<00:10:39.200> to<00:10:39.440> gonna<00:10:39.890> break 00:10:40.320 --> 00:10:40.330 align:start position:0% crusher called so this is to gonna break 00:10:40.330 --> 00:10:43.480 align:start position:0% crusher called so this is to gonna break composability<00:10:41.330> I<00:10:41.950> mean<00:10:42.950> sounds<00:10:43.220> like<00:10:43.340> it 00:10:43.480 --> 00:10:43.490 align:start position:0% composability I mean sounds like it 00:10:43.490 --> 00:10:45.820 align:start position:0% composability I mean sounds like it won't<00:10:43.670> if<00:10:43.970> we<00:10:44.150> have<00:10:44.270> synchronous<00:10:44.830> trust 00:10:45.820 --> 00:10:45.830 align:start position:0% won't if we have synchronous trust 00:10:45.830 --> 00:10:48.970 align:start position:0% won't if we have synchronous trust sharing<00:10:46.100> close 00:10:48.970 --> 00:10:48.980 align:start position:0% 00:10:48.980 --> 00:10:50.560 align:start position:0% oh<00:10:49.040> by<00:10:49.610> the<00:10:49.640> way<00:10:49.790> if<00:10:50.000> you<00:10:50.120> heard<00:10:50.270> there's<00:10:50.450> gonna 00:10:50.560 --> 00:10:50.570 align:start position:0% oh by the way if you heard there's gonna 00:10:50.570 --> 00:10:53.410 align:start position:0% oh by the way if you heard there's gonna be<00:10:50.690> one<00:10:50.900> thousand<00:10:51.320> charms<00:10:51.820> actually<00:10:52.820> it<00:10:53.240> might 00:10:53.410 --> 00:10:53.420 align:start position:0% be one thousand charms actually it might 00:10:53.420 --> 00:10:57.700 align:start position:0% be one thousand charms actually it might be<00:10:53.600> 64<00:10:54.260> charts<00:10:54.770> instead 00:10:57.700 --> 00:10:57.710 align:start position:0% 00:10:57.710 --> 00:11:02.740 align:start position:0% so<00:11:00.370> open<00:11:01.370> question<00:11:01.730> is<00:11:01.820> how<00:11:01.940> will<00:11:02.000> across 00:11:02.740 --> 00:11:02.750 align:start position:0% so open question is how will across 00:11:02.750 --> 00:11:04.690 align:start position:0% so open question is how will across chard<00:11:03.170> calls<00:11:03.470> work<00:11:03.770> I<00:11:03.980> don't<00:11:04.250> why<00:11:04.310> people<00:11:04.610> are 00:11:04.690 --> 00:11:04.700 align:start position:0% chard calls work I don't why people are 00:11:04.700 --> 00:11:08.700 align:start position:0% chard calls work I don't why people are afraid<00:11:04.880> to<00:11:05.000> say<00:11:05.779> that<00:11:06.050> we<00:11:06.680> don't<00:11:06.770> know<00:11:07.180> okay 00:11:08.700 --> 00:11:08.710 align:start position:0% afraid to say that we don't know okay 00:11:08.710 --> 00:11:10.840 align:start position:0% afraid to say that we don't know okay you<00:11:09.710> know<00:11:09.740> you're<00:11:10.279> gonna<00:11:10.370> ask<00:11:10.520> for<00:11:10.730> direction 00:11:10.840 --> 00:11:10.850 align:start position:0% you know you're gonna ask for direction 00:11:10.850 --> 00:11:12.910 align:start position:0% you know you're gonna ask for direction sometimes<00:11:11.480> we<00:11:11.779> don't<00:11:11.870> know<00:11:12.110> I<00:11:12.410> mean<00:11:12.710> long 00:11:12.910 --> 00:11:12.920 align:start position:0% sometimes we don't know I mean long 00:11:12.920 --> 00:11:15.220 align:start position:0% sometimes we don't know I mean long answer<00:11:13.250> we<00:11:14.180> have<00:11:14.300> a<00:11:14.330> prototype<00:11:14.720> and<00:11:14.899> figured 00:11:15.220 --> 00:11:15.230 align:start position:0% answer we have a prototype and figured 00:11:15.230 --> 00:11:19.900 align:start position:0% answer we have a prototype and figured out<00:11:17.440> how<00:11:18.440> will<00:11:18.620> the<00:11:18.770> eath<00:11:19.070> one<00:11:19.339> switchover 00:11:19.900 --> 00:11:19.910 align:start position:0% out how will the eath one switchover 00:11:19.910 --> 00:11:21.940 align:start position:0% out how will the eath one switchover works<00:11:20.089> I<00:11:20.270> just<00:11:20.540> learned<00:11:20.779> like<00:11:21.110> a<00:11:21.320> few<00:11:21.740> hours 00:11:21.940 --> 00:11:21.950 align:start position:0% works I just learned like a few hours 00:11:21.950 --> 00:11:23.940 align:start position:0% works I just learned like a few hours ago 00:11:23.940 --> 00:11:23.950 align:start position:0% ago 00:11:23.950 --> 00:11:28.269 align:start position:0% ago vitaly<00:11:24.950> posted<00:11:25.670> a<00:11:25.790> new<00:11:25.970> post<00:11:26.209> on<00:11:26.450> e3<00:11:27.050> search<00:11:27.560> he 00:11:28.269 --> 00:11:28.279 align:start position:0% vitaly posted a new post on e3 search he 00:11:28.279 --> 00:11:30.160 align:start position:0% vitaly posted a new post on e3 search he doesn't<00:11:28.520> call<00:11:28.640> to<00:11:28.790> switch<00:11:29.000> over<00:11:29.149> hoping<00:11:29.930> the 00:11:30.160 --> 00:11:30.170 align:start position:0% doesn't call to switch over hoping the 00:11:30.170 --> 00:11:33.760 align:start position:0% doesn't call to switch over hoping the switch<00:11:30.380> over<00:11:30.560> with<00:11:31.510> interruptions<00:11:32.510> I<00:11:33.170> propose 00:11:33.760 --> 00:11:33.770 align:start position:0% switch over with interruptions I propose 00:11:33.770 --> 00:11:35.590 align:start position:0% switch over with interruptions I propose calling<00:11:34.100> it<00:11:34.160> the<00:11:34.250> switch<00:11:34.459> over<00:11:34.730> but<00:11:35.420> he's 00:11:35.590 --> 00:11:35.600 align:start position:0% calling it the switch over but he's 00:11:35.600 --> 00:11:38.079 align:start position:0% calling it the switch over but he's calling<00:11:35.899> it<00:11:35.959> the<00:11:36.050> transition<00:11:37.000> maybe<00:11:38.000> we 00:11:38.079 --> 00:11:38.089 align:start position:0% calling it the transition maybe we 00:11:38.089 --> 00:11:45.010 align:start position:0% calling it the transition maybe we should<00:11:38.240> call<00:11:38.330> the<00:11:38.480> rapture<00:11:43.270> but<00:11:44.270> I<00:11:44.540> mean<00:11:44.959> it 00:11:45.010 --> 00:11:45.020 align:start position:0% should call the rapture but I mean it 00:11:45.020 --> 00:11:47.940 align:start position:0% should call the rapture but I mean it may<00:11:45.140> never<00:11:45.260> happen<00:11:45.490> okay<00:11:46.520> I<00:11:46.700> mean<00:11:46.940> did<00:11:47.240> like 00:11:47.940 --> 00:11:47.950 align:start position:0% may never happen okay I mean did like 00:11:47.950 --> 00:11:51.610 align:start position:0% may never happen okay I mean did like months<00:11:48.950> ago<00:11:49.160> it<00:11:49.760> was<00:11:50.110> really<00:11:51.110> neat<00:11:51.290> there's 00:11:51.610 --> 00:11:51.620 align:start position:0% months ago it was really neat there's 00:11:51.620 --> 00:11:53.560 align:start position:0% months ago it was really neat there's skepticism<00:11:51.860> that<00:11:52.550> maybe<00:11:52.730> the<00:11:52.940> eats<00:11:53.089> one<00:11:53.300> chain 00:11:53.560 --> 00:11:53.570 align:start position:0% skepticism that maybe the eats one chain 00:11:53.570 --> 00:11:56.260 align:start position:0% skepticism that maybe the eats one chain is<00:11:54.020> gonna<00:11:54.200> have<00:11:54.380> to<00:11:54.410> continue<00:11:55.310> on<00:11:55.610> forever<00:11:55.730> and 00:11:56.260 --> 00:11:56.270 align:start position:0% is gonna have to continue on forever and 00:11:56.270 --> 00:11:57.790 align:start position:0% is gonna have to continue on forever and everyone<00:11:56.540> will<00:11:56.630> have<00:11:56.660> to<00:11:56.779> redeploy<00:11:57.440> to 00:11:57.790 --> 00:11:57.800 align:start position:0% everyone will have to redeploy to 00:11:57.800 --> 00:12:00.960 align:start position:0% everyone will have to redeploy to rewrite<00:11:58.130> all<00:11:58.310> their<00:11:58.490> deaths<00:11:59.350> we<00:12:00.350> don't<00:12:00.529> know 00:12:00.960 --> 00:12:00.970 align:start position:0% rewrite all their deaths we don't know 00:12:00.970 --> 00:12:04.990 align:start position:0% rewrite all their deaths we don't know houston<00:12:01.970> worthless<00:12:02.410> prototype<00:12:03.410> it<00:12:03.589> and<00:12:04.000> you 00:12:04.990 --> 00:12:05.000 align:start position:0% houston worthless prototype it and you 00:12:05.000 --> 00:12:08.680 align:start position:0% houston worthless prototype it and you know<00:12:05.120> see<00:12:05.720> if<00:12:05.839> we<00:12:05.959> can<00:12:06.080> make<00:12:06.200> it<00:12:06.290> work 00:12:08.680 --> 00:12:08.690 align:start position:0% 00:12:08.690 --> 00:12:11.350 align:start position:0% lastly<00:12:09.440> winter<00:12:09.740> any<00:12:09.920> a<00:12:10.220> January<00:12:10.850> 3rd<00:12:11.089> Navy 00:12:11.350 --> 00:12:11.360 align:start position:0% lastly winter any a January 3rd Navy 00:12:11.360 --> 00:12:14.920 align:start position:0% lastly winter any a January 3rd Navy right<00:12:12.020> also<00:12:12.890> likely<00:12:13.610> we<00:12:14.300> don't<00:12:14.480> know<00:12:14.570> what<00:12:14.839> the 00:12:14.920 --> 00:12:14.930 align:start position:0% right also likely we don't know what the 00:12:14.930 --> 00:12:16.840 align:start position:0% right also likely we don't know what the price<00:12:15.080> of<00:12:15.110> ether<00:12:15.470> is<00:12:15.529> gonna<00:12:15.709> be<00:12:15.920> you<00:12:16.640> know<00:12:16.670> in 00:12:16.840 --> 00:12:16.850 align:start position:0% price of ether is gonna be you know in 00:12:16.850 --> 00:12:19.120 align:start position:0% price of ether is gonna be you know in our<00:12:17.000> suite<00:12:17.209> to<00:12:17.420> be<00:12:17.540> surprised<00:12:17.870> so<00:12:18.130> commonly 00:12:19.120 --> 00:12:19.130 align:start position:0% our suite to be surprised so commonly 00:12:19.130 --> 00:12:40.360 align:start position:0% our suite to be surprised so commonly people<00:12:19.279> ask<00:12:19.550> oh<00:12:21.310> and<00:12:22.310> yeah<00:12:22.880> that's<00:12:23.120> it<00:12:23.209> for<00:12:23.270> me 00:12:40.360 --> 00:12:40.370 align:start position:0% 00:12:40.370 --> 00:12:46.790 align:start position:0% I'm<00:12:41.149> gonna<00:12:41.269> teach<00:12:41.480> you 00:12:46.790 --> 00:12:46.800 align:start position:0% 00:12:46.800 --> 00:12:53.180 align:start position:0% hey<00:12:47.800> let's<00:12:47.980> do<00:12:48.070> some<00:12:48.220> Q&A 00:12:53.180 --> 00:12:53.190 align:start position:0% 00:12:53.190 --> 00:13:02.640 align:start position:0% what<00:12:54.190> do<00:12:54.370> we<00:12:54.520> know<00:12:59.430> what<00:13:00.430> do<00:13:00.730> we<00:13:00.880> know<00:13:01.030> well<00:13:01.840> we 00:13:02.640 --> 00:13:02.650 align:start position:0% what do we know what do we know well we 00:13:02.650 --> 00:13:06.120 align:start position:0% what do we know what do we know well we know<00:13:02.740> what's<00:13:02.890> going<00:13:02.980> to<00:13:03.040> use<00:13:03.190> awasum<00:13:05.130> anybody 00:13:06.120 --> 00:13:06.130 align:start position:0% know what's going to use awasum anybody 00:13:06.130 --> 00:13:29.640 align:start position:0% know what's going to use awasum anybody want<00:13:06.280> to<00:13:06.310> expand<00:13:12.600> any<00:13:13.600> other<00:13:13.720> questions<00:13:28.650> so 00:13:29.640 --> 00:13:29.650 align:start position:0% want to expand any other questions so 00:13:29.650 --> 00:13:31.500 align:start position:0% want to expand any other questions so it's<00:13:30.370> really<00:13:30.550> good<00:13:30.790> you<00:13:30.880> put<00:13:31.090> down<00:13:31.210> in<00:13:31.420> the 00:13:31.500 --> 00:13:31.510 align:start position:0% it's really good you put down in the 00:13:31.510 --> 00:13:34.680 align:start position:0% it's really good you put down in the slides<00:13:31.750> there<00:13:31.990> but<00:13:32.730> for<00:13:33.730> people<00:13:33.970> who<00:13:34.180> want<00:13:34.630> to 00:13:34.680 --> 00:13:34.690 align:start position:0% slides there but for people who want to 00:13:34.690 --> 00:13:36.750 align:start position:0% slides there but for people who want to help<00:13:34.840> there's<00:13:35.620> some<00:13:35.920> a<00:13:36.190> lot<00:13:36.400> of<00:13:36.490> help<00:13:36.610> that's 00:13:36.750 --> 00:13:36.760 align:start position:0% help there's some a lot of help that's 00:13:36.760 --> 00:13:39.410 align:start position:0% help there's some a lot of help that's needed<00:13:36.940> so<00:13:37.840> the<00:13:37.930> main<00:13:38.080> help<00:13:38.380> that's<00:13:38.530> needed<00:13:38.650> to 00:13:39.410 --> 00:13:39.420 align:start position:0% needed so the main help that's needed to 00:13:39.420 --> 00:13:42.330 align:start position:0% needed so the main help that's needed to basically<00:13:40.420> just<00:13:40.900> say<00:13:40.990> is<00:13:41.200> how<00:13:41.500> would<00:13:41.740> cost<00:13:42.100> our 00:13:42.330 --> 00:13:42.340 align:start position:0% basically just say is how would cost our 00:13:42.340 --> 00:13:55.050 align:start position:0% basically just say is how would cost our calls<00:13:42.670> work<00:13:42.910> I<00:13:43.150> mean<00:13:43.900> help<00:13:44.260> us<00:13:44.410> keep<00:13:44.620> it<00:13:44.770> down<00:13:54.060> I 00:13:55.050 --> 00:13:55.060 align:start position:0% calls work I mean help us keep it down I 00:13:55.060 --> 00:13:56.220 align:start position:0% calls work I mean help us keep it down I think<00:13:55.270> every<00:13:55.540> we're<00:13:55.690> just<00:13:55.900> getting<00:13:56.110> more 00:13:56.220 --> 00:13:56.230 align:start position:0% think every we're just getting more 00:13:56.230 --> 00:13:57.780 align:start position:0% think every we're just getting more people<00:13:56.350> involved<00:13:56.680> more<00:13:57.130> people<00:13:57.430> building 00:13:57.780 --> 00:13:57.790 align:start position:0% people involved more people building 00:13:57.790 --> 00:14:01.590 align:start position:0% people involved more people building IEDs<00:13:58.330> so<00:13:58.930> in<00:13:59.530> attention<00:13:59.920> to<00:14:00.070> the<00:14:00.600> presentation 00:14:01.590 --> 00:14:01.600 align:start position:0% IEDs so in attention to the presentation 00:14:01.600 --> 00:14:05.340 align:start position:0% IEDs so in attention to the presentation today<00:14:03.330> there's<00:14:04.330> there's<00:14:04.690> a<00:14:04.780> lot<00:14:04.810> of<00:14:05.050> proposals 00:14:05.340 --> 00:14:05.350 align:start position:0% today there's there's a lot of proposals 00:14:05.350 --> 00:14:09.030 align:start position:0% today there's there's a lot of proposals for<00:14:05.680> the<00:14:05.800> crushed<00:14:06.070> red<00:14:06.250> cars<00:14:06.490> right<00:14:06.870> and<00:14:07.870> so<00:14:08.440> we 00:14:09.030 --> 00:14:09.040 align:start position:0% for the crushed red cars right and so we 00:14:09.040 --> 00:14:10.810 align:start position:0% for the crushed red cars right and so we just<00:14:09.190> have<00:14:09.460> to<00:14:09.490> build<00:14:09.970> the<00:14:10.090> different<00:14:10.240> ones 00:14:10.810 --> 00:14:10.820 align:start position:0% just have to build the different ones 00:14:10.820 --> 00:14:14.530 align:start position:0% just have to build the different ones in<00:14:11.000> different<00:14:11.450> keys<00:14:11.930> try<00:14:13.360> getting<00:14:14.360> more 00:14:14.530 --> 00:14:14.540 align:start position:0% in different keys try getting more 00:14:14.540 --> 00:14:16.360 align:start position:0% in different keys try getting more developers<00:14:14.990> involved<00:14:15.410> in<00:14:15.500> this<00:14:15.620> I<00:14:15.800> think<00:14:16.010> you 00:14:16.360 --> 00:14:16.370 align:start position:0% developers involved in this I think you 00:14:16.370 --> 00:14:18.700 align:start position:0% developers involved in this I think you know<00:14:16.490> this<00:14:16.700> is<00:14:17.690> gonna<00:14:17.840> be<00:14:18.020> really<00:14:18.140> helpful<00:14:18.380> I 00:14:18.700 --> 00:14:18.710 align:start position:0% know this is gonna be really helpful I 00:14:18.710 --> 00:14:21.670 align:start position:0% know this is gonna be really helpful I think<00:14:18.740> that's<00:14:19.040> that's<00:14:19.430> what<00:14:19.670> I've<00:14:20.560> made<00:14:21.560> one 00:14:21.670 --> 00:14:21.680 align:start position:0% think that's that's what I've made one 00:14:21.680 --> 00:14:26.850 align:start position:0% think that's that's what I've made one of<00:14:21.770> the<00:14:21.830> goals 00:14:26.850 --> 00:14:26.860 align:start position:0% 00:14:26.860 --> 00:14:29.070 align:start position:0% anybody<00:14:27.700> knows<00:14:27.910> what<00:14:28.150> what<00:14:28.690> any<00:14:28.840> of<00:14:28.930> these 00:14:29.070 --> 00:14:29.080 align:start position:0% anybody knows what what any of these 00:14:29.080 --> 00:14:32.910 align:start position:0% anybody knows what what any of these face<00:14:29.350> two<00:14:29.680> proposals<00:14:30.190> are<00:14:31.740> anybody<00:14:32.740> knows 00:14:32.910 --> 00:14:32.920 align:start position:0% face two proposals are anybody knows 00:14:32.920 --> 00:14:35.450 align:start position:0% face two proposals are anybody knows what<00:14:33.100> the<00:14:33.250> architecture<00:14:33.730> proposed<00:14:34.360> this 00:14:35.450 --> 00:14:35.460 align:start position:0% what the architecture proposed this 00:14:35.460 --> 00:14:38.340 align:start position:0% what the architecture proposed this nobody<00:14:36.460> so<00:14:37.240> I<00:14:37.300> guess<00:14:37.450> it<00:14:37.630> kind<00:14:38.020> of<00:14:38.050> will<00:14:38.200> be 00:14:38.340 --> 00:14:38.350 align:start position:0% nobody so I guess it kind of will be 00:14:38.350 --> 00:14:43.440 align:start position:0% nobody so I guess it kind of will be hard<00:14:38.560> to<00:14:38.740> continue<00:14:39.640> from<00:14:39.910> there<00:14:40.090> but<00:14:42.210> we<00:14:43.210> were 00:14:43.440 --> 00:14:43.450 align:start position:0% hard to continue from there but we were 00:14:43.450 --> 00:14:44.910 align:start position:0% hard to continue from there but we were supposed<00:14:43.690> to<00:14:43.870> have<00:14:43.990> some<00:14:44.170> slides<00:14:44.440> showing 00:14:44.910 --> 00:14:44.920 align:start position:0% supposed to have some slides showing 00:14:44.920 --> 00:14:46.940 align:start position:0% supposed to have some slides showing darka<00:14:45.340> textured<00:14:45.520> it<00:14:45.790> was<00:14:45.910> kind<00:14:46.120> of<00:14:46.210> a<00:14:46.270> short 00:14:46.940 --> 00:14:46.950 align:start position:0% darka textured it was kind of a short 00:14:46.950 --> 00:14:49.410 align:start position:0% darka textured it was kind of a short time<00:14:47.950> frame<00:14:48.280> to<00:14:48.550> explain<00:14:48.850> all<00:14:49.030> that<00:14:49.060> it's 00:14:49.410 --> 00:14:49.420 align:start position:0% time frame to explain all that it's 00:14:49.420 --> 00:14:50.400 align:start position:0% time frame to explain all that it's kinda<00:14:49.660> hard<00:14:49.810> to<00:14:49.870> you<00:14:50.050> know<00:14:50.110> to<00:14:50.260> go<00:14:50.380> to 00:14:50.400 --> 00:14:50.410 align:start position:0% kinda hard to you know to go to 00:14:50.410 --> 00:14:53.370 align:start position:0% kinda hard to you know to go to everything<00:14:51.480> but<00:14:52.480> we<00:14:52.630> all<00:14:52.720> need<00:14:52.840> to<00:14:52.990> work<00:14:53.140> we 00:14:53.370 --> 00:14:53.380 align:start position:0% everything but we all need to work we 00:14:53.380 --> 00:14:54.270 align:start position:0% everything but we all need to work we need<00:14:53.530> help 00:14:54.270 --> 00:14:54.280 align:start position:0% need help 00:14:54.280 --> 00:14:56.700 align:start position:0% need help okay<00:14:54.760> see<00:14:54.820> you<00:14:55.060> mentioned<00:14:55.480> that<00:14:55.660> there<00:14:56.620> were 00:14:56.700 --> 00:14:56.710 align:start position:0% okay see you mentioned that there were 00:14:56.710 --> 00:15:01.860 align:start position:0% okay see you mentioned that there were some<00:14:56.740> of<00:14:57.130> these<00:14:57.280> questions<00:15:00.480> which<00:15:01.480> there<00:15:01.720> were 00:15:01.860 --> 00:15:01.870 align:start position:0% some of these questions which there were 00:15:01.870 --> 00:15:03.420 align:start position:0% some of these questions which there were answers<00:15:02.110> we've<00:15:02.410> met<00:15:02.590> for<00:15:02.620> many<00:15:02.830> of<00:15:03.040> them<00:15:03.220> there 00:15:03.420 --> 00:15:03.430 align:start position:0% answers we've met for many of them there 00:15:03.430 --> 00:15:06.210 align:start position:0% answers we've met for many of them there weren't<00:15:03.700> any<00:15:03.910> answers<00:15:04.210> and<00:15:04.840> the<00:15:05.740> same<00:15:05.950> still 00:15:06.210 --> 00:15:06.220 align:start position:0% weren't any answers and the same still 00:15:06.220 --> 00:15:11.250 align:start position:0% weren't any answers and the same still applies<00:15:06.550> on<00:15:07.150> Phase<00:15:08.140> two<00:15:08.170> the<00:15:08.800> only<00:15:09.460> thing<00:15:10.260> the 00:15:11.250 --> 00:15:11.260 align:start position:0% applies on Phase two the only thing the 00:15:11.260 --> 00:15:14.190 align:start position:0% applies on Phase two the only thing the only<00:15:11.320> things<00:15:11.650> we<00:15:11.830> know<00:15:12.550> right<00:15:13.150> now<00:15:13.390> is<00:15:13.750> just 00:15:14.190 --> 00:15:14.200 align:start position:0% only things we know right now is just 00:15:14.200 --> 00:15:18.450 align:start position:0% only things we know right now is just how<00:15:15.040> to<00:15:15.100> execute<00:15:15.460> stuff<00:15:16.680> but<00:15:17.680> some<00:15:18.340> other 00:15:18.450 --> 00:15:18.460 align:start position:0% how to execute stuff but some other 00:15:18.460 --> 00:15:19.830 align:start position:0% how to execute stuff but some other things<00:15:18.700> are<00:15:18.820> still<00:15:19.000> decoupled<00:15:19.540> from<00:15:19.570> the 00:15:19.830 --> 00:15:19.840 align:start position:0% things are still decoupled from the 00:15:19.840 --> 00:15:23.820 align:start position:0% things are still decoupled from the system<00:15:21.570> the<00:15:22.570> exact<00:15:23.050> thing<00:15:23.230> I'm<00:15:23.470> not<00:15:23.650> sure<00:15:23.740> if 00:15:23.820 --> 00:15:23.830 align:start position:0% system the exact thing I'm not sure if 00:15:23.830 --> 00:15:25.290 align:start position:0% system the exact thing I'm not sure if you<00:15:23.950> wanna<00:15:24.100> go<00:15:24.220> back<00:15:24.340> to<00:15:24.460> the<00:15:24.550> slide<00:15:24.760> but<00:15:24.940> exit 00:15:25.290 --> 00:15:25.300 align:start position:0% you wanna go back to the slide but exit 00:15:25.300 --> 00:15:27.570 align:start position:0% you wanna go back to the slide but exit thing<00:15:25.510> is<00:15:25.750> you<00:15:26.290> can<00:15:26.440> us<00:15:26.530> keep<00:15:26.860> the<00:15:27.040> statements 00:15:27.570 --> 00:15:27.580 align:start position:0% thing is you can us keep the statements 00:15:27.580 --> 00:15:29.880 align:start position:0% thing is you can us keep the statements you're<00:15:27.670> gonna<00:15:27.790> provide<00:15:28.060> a<00:15:28.120> state<00:15:28.740> and<00:15:29.740> that 00:15:29.880 --> 00:15:29.890 align:start position:0% you're gonna provide a state and that 00:15:29.890 --> 00:15:32.100 align:start position:0% you're gonna provide a state and that big<00:15:30.250> topic<00:15:30.940> is<00:15:31.090> is<00:15:31.330> called<00:15:31.600> the<00:15:31.720> relayer 00:15:32.100 --> 00:15:32.110 align:start position:0% big topic is is called the relayer 00:15:32.110 --> 00:15:34.110 align:start position:0% big topic is is called the relayer Markinson<00:15:32.770> that's<00:15:33.370> one<00:15:33.550> of<00:15:33.640> the<00:15:33.730> big<00:15:33.880> topics 00:15:34.110 --> 00:15:34.120 align:start position:0% Markinson that's one of the big topics 00:15:34.120 --> 00:15:37.470 align:start position:0% Markinson that's one of the big topics be<00:15:34.480> definitely<00:15:35.200> more<00:15:35.440> eyes<00:15:35.980> on<00:15:36.210> and<00:15:37.210> another 00:15:37.470 --> 00:15:37.480 align:start position:0% be definitely more eyes on and another 00:15:37.480 --> 00:15:40.440 align:start position:0% be definitely more eyes on and another big<00:15:37.690> topic<00:15:37.870> then<00:15:38.260> is<00:15:38.670> called<00:15:39.670> the<00:15:39.850> fee<00:15:40.000> markets 00:15:40.440 --> 00:15:40.450 align:start position:0% big topic then is called the fee markets 00:15:40.450 --> 00:15:43.110 align:start position:0% big topic then is called the fee markets but<00:15:40.840> what<00:15:41.410> all<00:15:41.590> of<00:15:41.620> these<00:15:41.830> means<00:15:42.130> is<00:15:42.430> how<00:15:42.940> do<00:15:43.000> we 00:15:43.110 --> 00:15:43.120 align:start position:0% but what all of these means is how do we 00:15:43.120 --> 00:15:46.170 align:start position:0% but what all of these means is how do we get<00:15:43.330> the<00:15:43.450> data<00:15:43.920> the<00:15:44.920> stateless<00:15:45.340> contracting 00:15:46.170 --> 00:15:46.180 align:start position:0% get the data the stateless contracting 00:15:46.180 --> 00:15:49.370 align:start position:0% get the data the stateless contracting and<00:15:46.420> had<00:15:47.380> to<00:15:47.500> be<00:15:47.590> paid<00:15:47.890> each<00:15:48.520> of<00:15:48.700> the<00:15:48.760> parties 00:15:49.370 --> 00:15:49.380 align:start position:0% and had to be paid each of the parties 00:15:49.380 --> 00:15:54.330 align:start position:0% and had to be paid each of the parties involved<00:15:50.380> and<00:15:51.750> two<00:15:52.750> we<00:15:53.290> have<00:15:53.680> basically<00:15:54.010> four 00:15:54.330 --> 00:15:54.340 align:start position:0% involved and two we have basically four 00:15:54.340 --> 00:15:56.580 align:start position:0% involved and two we have basically four parties<00:15:54.820> here<00:15:55.150> at<00:15:55.360> least<00:15:55.600> they<00:15:56.350> have<00:15:56.500> the 00:15:56.580 --> 00:15:56.590 align:start position:0% parties here at least they have the 00:15:56.590 --> 00:15:59.010 align:start position:0% parties here at least they have the users<00:15:56.950> who<00:15:57.310> want<00:15:57.490> to<00:15:57.610> do<00:15:57.840> transactions<00:15:58.840> don't 00:15:59.010 --> 00:15:59.020 align:start position:0% users who want to do transactions don't 00:15:59.020 --> 00:16:01.460 align:start position:0% users who want to do transactions don't you<00:15:59.170> want<00:15:59.350> to<00:15:59.530> use<00:15:59.680> the<00:15:59.830> system<00:15:59.980> and<00:16:00.400> we<00:16:01.390> have 00:16:01.460 --> 00:16:01.470 align:start position:0% you want to use the system and we have 00:16:01.470 --> 00:16:03.870 align:start position:0% you want to use the system and we have another<00:16:02.470> party<00:16:02.920> which<00:16:03.070> recovery<00:16:03.580> layers 00:16:03.870 --> 00:16:03.880 align:start position:0% another party which recovery layers 00:16:03.880 --> 00:16:06.660 align:start position:0% another party which recovery layers right<00:16:04.150> now<00:16:04.360> who<00:16:05.260> are<00:16:06.190> basically<00:16:06.430> the 00:16:06.660 --> 00:16:06.670 align:start position:0% right now who are basically the 00:16:06.670 --> 00:16:08.460 align:start position:0% right now who are basically the providers<00:16:07.300> who<00:16:07.510> store<00:16:07.780> all<00:16:08.020> of<00:16:08.110> the<00:16:08.230> states 00:16:08.460 --> 00:16:08.470 align:start position:0% providers who store all of the states 00:16:08.470 --> 00:16:11.130 align:start position:0% providers who store all of the states for<00:16:08.680> you<00:16:08.830> and<00:16:09.160> they're<00:16:09.610> able<00:16:09.820> to<00:16:10.000> package<00:16:10.840> up 00:16:11.130 --> 00:16:11.140 align:start position:0% for you and they're able to package up 00:16:11.140 --> 00:16:12.060 align:start position:0% for you and they're able to package up whatever 00:16:12.060 --> 00:16:12.070 align:start position:0% whatever 00:16:12.070 --> 00:16:14.880 align:start position:0% whatever transaction<00:16:12.910> use<00:16:13.030> them<00:16:13.410> into<00:16:14.410> something<00:16:14.650> the 00:16:14.880 --> 00:16:14.890 align:start position:0% transaction use them into something the 00:16:14.890 --> 00:16:19.290 align:start position:0% transaction use them into something the system<00:16:15.220> can<00:16:15.370> actually<00:16:15.490> use<00:16:17.040> and<00:16:18.040> then<00:16:18.300> these 00:16:19.290 --> 00:16:19.300 align:start position:0% system can actually use and then these 00:16:19.300 --> 00:16:23.600 align:start position:0% system can actually use and then these really<00:16:19.360> are<00:16:19.780> send<00:16:20.310> these<00:16:21.310> package<00:16:22.030> things<00:16:22.330> to 00:16:23.600 --> 00:16:23.610 align:start position:0% really are send these package things to 00:16:23.610 --> 00:16:25.920 align:start position:0% really are send these package things to the<00:16:24.610> blog<00:16:24.820> producers<00:16:25.330> who<00:16:25.540> are<00:16:25.660> the<00:16:25.750> ones 00:16:25.920 --> 00:16:25.930 align:start position:0% the blog producers who are the ones 00:16:25.930 --> 00:16:30.240 align:start position:0% the blog producers who are the ones actually<00:16:26.140> running<00:16:27.130> it<00:16:27.370> on<00:16:27.640> e<00:16:27.850> 2.0<00:16:28.860> and<00:16:29.860> each<00:16:30.100> of 00:16:30.240 --> 00:16:30.250 align:start position:0% actually running it on e 2.0 and each of 00:16:30.250 --> 00:16:33.930 align:start position:0% actually running it on e 2.0 and each of these<00:16:30.370> steps<00:16:31.200> people<00:16:32.200> have<00:16:32.440> to<00:16:32.560> be<00:16:32.650> paid<00:16:32.940> so 00:16:33.930 --> 00:16:33.940 align:start position:0% these steps people have to be paid so 00:16:33.940 --> 00:16:35.150 align:start position:0% these steps people have to be paid so these<00:16:34.300> are<00:16:34.510> kind<00:16:34.720> of<00:16:34.810> big 00:16:35.150 --> 00:16:35.160 align:start position:0% these are kind of big 00:16:35.160 --> 00:16:37.160 align:start position:0% these are kind of big they're<00:16:35.699> many<00:16:35.850> ways<00:16:36.060> to<00:16:36.209> do<00:16:36.300> it<00:16:36.329> and<00:16:36.990> you<00:16:37.079> were 00:16:37.160 --> 00:16:37.170 align:start position:0% they're many ways to do it and you were 00:16:37.170 --> 00:16:39.769 align:start position:0% they're many ways to do it and you were experimenting<00:16:37.829> with<00:16:37.949> different<00:16:38.040> ways<00:16:38.779> but 00:16:39.769 --> 00:16:39.779 align:start position:0% experimenting with different ways but 00:16:39.779 --> 00:16:41.300 align:start position:0% experimenting with different ways but before<00:16:40.230> we<00:16:40.350> get<00:16:40.470> into<00:16:40.529> cross<00:16:41.009> shark 00:16:41.300 --> 00:16:41.310 align:start position:0% before we get into cross shark 00:16:41.310 --> 00:16:43.519 align:start position:0% before we get into cross shark convocation<00:16:41.850> I<00:16:42.149> would<00:16:42.870> suggest<00:16:43.019> maybe<00:16:43.350> these 00:16:43.519 --> 00:16:43.529 align:start position:0% convocation I would suggest maybe these 00:16:43.529 --> 00:16:49.990 align:start position:0% convocation I would suggest maybe these are<00:16:43.709> the<00:16:43.740> things<00:16:44.009> to<00:16:44.069> be<00:16:44.160> able<00:16:44.310> to<00:16:44.370> Soulforce<00:16:44.759> a 00:16:49.990 --> 00:16:50.000 align:start position:0% 00:16:50.000 --> 00:16:55.600 align:start position:0% little<00:16:51.000> bit<00:16:52.610> so<00:16:53.610> we<00:16:54.540> thought<00:16:54.810> we<00:16:54.959> knew<00:16:55.139> that 00:16:55.600 --> 00:16:55.610 align:start position:0% little bit so we thought we knew that 00:16:55.610 --> 00:16:58.910 align:start position:0% little bit so we thought we knew that wasn't<00:16:56.610> code<00:16:57.329> would<00:16:57.660> be<00:16:57.720> run<00:16:58.079> in<00:16:58.439> the<00:16:58.709> shark 00:16:58.910 --> 00:16:58.920 align:start position:0% wasn't code would be run in the shark 00:16:58.920 --> 00:17:02.809 align:start position:0% wasn't code would be run in the shark box<00:16:59.189> and<00:16:59.550> not<00:16:59.850> in<00:17:00.089> the<00:17:00.990> beacon<00:17:01.230> box<00:17:01.560> and<00:17:01.920> then 00:17:02.809 --> 00:17:02.819 align:start position:0% box and not in the beacon box and then 00:17:02.819 --> 00:17:05.779 align:start position:0% box and not in the beacon box and then you<00:17:03.509> know<00:17:03.629> about<00:17:03.930> a<00:17:03.990> month<00:17:04.289> ago 00:17:05.779 --> 00:17:05.789 align:start position:0% you know about a month ago 00:17:05.789 --> 00:17:08.779 align:start position:0% you know about a month ago metallic<00:17:06.780> manual<00:17:07.230> proposal<00:17:07.709> that<00:17:08.069> was<00:17:08.429> that 00:17:08.779 --> 00:17:08.789 align:start position:0% metallic manual proposal that was that 00:17:08.789 --> 00:17:11.149 align:start position:0% metallic manual proposal that was that was<00:17:08.939> like<00:17:09.000> the<00:17:09.209> spec<00:17:09.449> as<00:17:09.689> a<00:17:09.799> phase<00:17:10.799> two 00:17:11.149 --> 00:17:11.159 align:start position:0% was like the spec as a phase two 00:17:11.159 --> 00:17:17.179 align:start position:0% was like the spec as a phase two proposal<00:17:11.699> -<00:17:14.750> yeah<00:17:15.750> yeah<00:17:16.620> and<00:17:16.860> this<00:17:16.919> one<00:17:17.069> they 00:17:17.179 --> 00:17:17.189 align:start position:0% proposal - yeah yeah and this one they 00:17:17.189 --> 00:17:19.069 align:start position:0% proposal - yeah yeah and this one they added<00:17:17.520> functionality<00:17:17.909> was<00:17:18.329> oh<00:17:18.539> yeah<00:17:18.900> we<00:17:19.049> also 00:17:19.069 --> 00:17:19.079 align:start position:0% added functionality was oh yeah we also 00:17:19.079 --> 00:17:22.909 align:start position:0% added functionality was oh yeah we also run<00:17:19.530> awesome<00:17:20.010> code<00:17:20.370> and<00:17:21.350> beacon<00:17:22.350> blocks<00:17:22.559> and 00:17:22.909 --> 00:17:22.919 align:start position:0% run awesome code and beacon blocks and 00:17:22.919 --> 00:17:26.329 align:start position:0% run awesome code and beacon blocks and so<00:17:23.039> that<00:17:23.189> was<00:17:23.339> like<00:17:23.490> eight<00:17:24.199> proposal<00:17:25.339> three 00:17:26.329 --> 00:17:26.339 align:start position:0% so that was like eight proposal three 00:17:26.339 --> 00:17:29.600 align:start position:0% so that was like eight proposal three and<00:17:26.939> then<00:17:27.809> the<00:17:28.289> proposal<00:17:28.799> to<00:17:28.950> reduce<00:17:29.370> the 00:17:29.600 --> 00:17:29.610 align:start position:0% and then the proposal to reduce the 00:17:29.610 --> 00:17:32.990 align:start position:0% and then the proposal to reduce the number<00:17:29.880> of<00:17:30.000> sharks<00:17:30.450> from<00:17:30.690> 1,000<00:17:31.440> to<00:17:31.640> 64<00:17:32.640> which 00:17:32.990 --> 00:17:33.000 align:start position:0% number of sharks from 1,000 to 64 which 00:17:33.000 --> 00:17:37.549 align:start position:0% number of sharks from 1,000 to 64 which I<00:17:33.470> already<00:17:34.470> mentioned<00:17:34.860> in<00:17:35.100> the<00:17:36.110> East<00:17:37.110> magician 00:17:37.549 --> 00:17:37.559 align:start position:0% I already mentioned in the East magician 00:17:37.559 --> 00:17:39.500 align:start position:0% I already mentioned in the East magician session<00:17:37.980> you<00:17:38.490> know<00:17:38.580> a<00:17:38.610> couple<00:17:38.820> days<00:17:39.000> ago<00:17:39.150> and 00:17:39.500 --> 00:17:39.510 align:start position:0% session you know a couple days ago and 00:17:39.510 --> 00:17:42.820 align:start position:0% session you know a couple days ago and said<00:17:40.320> there<00:17:40.830> will<00:17:40.980> be<00:17:41.010> you<00:17:41.429> know<00:17:41.520> more 00:17:42.820 --> 00:17:42.830 align:start position:0% said there will be you know more 00:17:42.830 --> 00:17:47.210 align:start position:0% said there will be you know more published<00:17:43.830> on<00:17:43.980> this<00:17:44.159> very<00:17:44.429> soon<00:17:45.980> and<00:17:46.980> that's 00:17:47.210 --> 00:17:47.220 align:start position:0% published on this very soon and that's 00:17:47.220 --> 00:17:51.180 align:start position:0% published on this very soon and that's like<00:17:47.340> the<00:17:47.809> radical<00:17:48.809> new<00:17:49.080> new<00:17:49.380> proposal 00:17:51.180 --> 00:17:51.190 align:start position:0% like the radical new new proposal 00:17:51.190 --> 00:17:53.230 align:start position:0% like the radical new new proposal [Music] 00:17:53.230 --> 00:17:53.240 align:start position:0% [Music] 00:17:53.240 --> 00:17:55.430 align:start position:0% [Music] federal<00:17:54.240> I<00:17:54.299> mean<00:17:54.419> this<00:17:54.570> kind<00:17:54.809> of<00:17:54.900> like<00:17:55.110> would 00:17:55.430 --> 00:17:55.440 align:start position:0% federal I mean this kind of like would 00:17:55.440 --> 00:17:57.890 align:start position:0% federal I mean this kind of like would what<00:17:55.980> we<00:17:56.070> know<00:17:56.220> is<00:17:56.490> just<00:17:56.610> as<00:17:57.090> these<00:17:57.510> proposals 00:17:57.890 --> 00:17:57.900 align:start position:0% what we know is just as these proposals 00:17:57.900 --> 00:18:00.799 align:start position:0% what we know is just as these proposals are<00:17:58.260> rolling<00:17:59.100> out<00:17:59.330> we<00:18:00.330> know<00:18:00.480> a<00:18:00.510> little<00:18:00.720> bit 00:18:00.799 --> 00:18:00.809 align:start position:0% are rolling out we know a little bit 00:18:00.809 --> 00:18:03.289 align:start position:0% are rolling out we know a little bit more<00:18:00.870> every<00:18:01.289> time<00:18:01.320> there's<00:18:02.130> a<00:18:02.190> new<00:18:02.309> one<00:18:02.520> what 00:18:03.289 --> 00:18:03.299 align:start position:0% more every time there's a new one what 00:18:03.299 --> 00:18:05.840 align:start position:0% more every time there's a new one what so<00:18:03.419> what's<00:18:03.600> the<00:18:03.659> reason<00:18:03.960> both<00:18:04.620> over<00:18:04.799> that<00:18:04.950> yeah 00:18:05.840 --> 00:18:05.850 align:start position:0% so what's the reason both over that yeah 00:18:05.850 --> 00:18:08.539 align:start position:0% so what's the reason both over that yeah so<00:18:06.090> I<00:18:06.120> mean<00:18:06.390> each<00:18:07.230> of<00:18:07.409> them<00:18:07.530> kind<00:18:07.860> of<00:18:07.950> give 00:18:08.539 --> 00:18:08.549 align:start position:0% so I mean each of them kind of give 00:18:08.549 --> 00:18:10.070 align:start position:0% so I mean each of them kind of give their<00:18:08.700> own<00:18:08.820> strengths<00:18:09.330> and<00:18:09.390> weaknesses<00:18:09.570> so 00:18:10.070 --> 00:18:10.080 align:start position:0% their own strengths and weaknesses so 00:18:10.080 --> 00:18:12.210 align:start position:0% their own strengths and weaknesses so like<00:18:10.559> the<00:18:10.740> proposal<00:18:11.429> with<00:18:11.789> what 00:18:12.210 --> 00:18:12.220 align:start position:0% like the proposal with what 00:18:12.220 --> 00:18:15.350 align:start position:0% like the proposal with what called<00:18:12.429> two<00:18:12.610> and<00:18:12.700> a<00:18:12.730> half<00:18:12.880> three<00:18:13.470> three 00:18:15.350 --> 00:18:15.360 align:start position:0% called two and a half three three 00:18:15.360 --> 00:18:19.220 align:start position:0% called two and a half three three provided<00:18:16.830> some<00:18:17.830> level<00:18:18.130> of<00:18:18.250> load<00:18:18.700> balancing 00:18:19.220 --> 00:18:19.230 align:start position:0% provided some level of load balancing 00:18:19.230 --> 00:18:22.200 align:start position:0% provided some level of load balancing and<00:18:20.230> some<00:18:20.409> level<00:18:20.559> of<00:18:20.710> scheduling<00:18:21.220> across<00:18:22.059> the 00:18:22.200 --> 00:18:22.210 align:start position:0% and some level of scheduling across the 00:18:22.210 --> 00:18:24.210 align:start position:0% and some level of scheduling across the charts<00:18:22.570> and<00:18:22.870> and<00:18:23.230> you<00:18:23.409> kind<00:18:23.710> of<00:18:23.770> treat<00:18:23.980> each<00:18:24.100> of 00:18:24.210 --> 00:18:24.220 align:start position:0% charts and and you kind of treat each of 00:18:24.220 --> 00:18:27.680 align:start position:0% charts and and you kind of treat each of the<00:18:24.280> shards<00:18:24.610> this<00:18:24.789> you're<00:18:25.419> competing<00:18:25.720> layer 00:18:27.680 --> 00:18:27.690 align:start position:0% the shards this you're competing layer 00:18:27.690 --> 00:18:30.029 align:start position:0% the shards this you're competing layer one<00:18:28.690> that<00:18:28.840> kind<00:18:29.049> of<00:18:29.080> you<00:18:29.320> know<00:18:29.380> came<00:18:29.710> after 00:18:30.029 --> 00:18:30.039 align:start position:0% one that kind of you know came after 00:18:30.039 --> 00:18:33.870 align:start position:0% one that kind of you know came after that<00:18:30.780> was<00:18:31.780> more<00:18:32.220> has<00:18:33.220> been<00:18:33.250> more<00:18:33.580> geared 00:18:33.870 --> 00:18:33.880 align:start position:0% that was more has been more geared 00:18:33.880 --> 00:18:35.510 align:start position:0% that was more has been more geared towards<00:18:34.210> making<00:18:34.360> crash<00:18:34.750> that<00:18:34.960> calls 00:18:35.510 --> 00:18:35.520 align:start position:0% towards making crash that calls 00:18:35.520 --> 00:18:38.340 align:start position:0% towards making crash that calls significantly<00:18:36.520> quicker<00:18:36.730> so<00:18:37.299> you<00:18:38.080> can<00:18:38.200> make<00:18:38.320> a 00:18:38.340 --> 00:18:38.350 align:start position:0% significantly quicker so you can make a 00:18:38.350 --> 00:18:42.510 align:start position:0% significantly quicker so you can make a crash<00:18:38.620> call<00:18:39.100> what<00:18:39.970> one<00:18:40.419> block<00:18:41.190> so<00:18:42.190> if<00:18:42.340> you're 00:18:42.510 --> 00:18:42.520 align:start position:0% crash call what one block so if you're 00:18:42.520 --> 00:18:45.299 align:start position:0% crash call what one block so if you're calling<00:18:43.510> a<00:18:43.750> contract<00:18:44.380> on<00:18:44.530> another<00:18:44.770> block<00:18:45.010> on 00:18:45.299 --> 00:18:45.309 align:start position:0% calling a contract on another block on 00:18:45.309 --> 00:18:48.539 align:start position:0% calling a contract on another block on another<00:18:46.150> shard<00:18:46.390> you<00:18:46.659> can<00:18:46.809> do<00:18:46.900> that<00:18:47.049> block<00:18:47.890> so<00:18:48.340> I 00:18:48.539 --> 00:18:48.549 align:start position:0% another shard you can do that block so I 00:18:48.549 --> 00:18:50.610 align:start position:0% another shard you can do that block so I think<00:18:49.000> each<00:18:49.299> proposal<00:18:49.870> has<00:18:50.020> its<00:18:50.200> trade-offs 00:18:50.610 --> 00:18:50.620 align:start position:0% think each proposal has its trade-offs 00:18:50.620 --> 00:18:52.950 align:start position:0% think each proposal has its trade-offs and<00:18:50.950> so<00:18:51.250> I<00:18:51.549> think<00:18:51.970> what<00:18:52.450> you'll<00:18:52.570> realize 00:18:52.950 --> 00:18:52.960 align:start position:0% and so I think what you'll realize 00:18:52.960 --> 00:18:54.750 align:start position:0% and so I think what you'll realize through<00:18:53.440> kind<00:18:54.070> of<00:18:54.100> what<00:18:54.220> we're<00:18:54.340> talking<00:18:54.520> about 00:18:54.750 --> 00:18:54.760 align:start position:0% through kind of what we're talking about 00:18:54.760 --> 00:18:57.870 align:start position:0% through kind of what we're talking about today<00:18:55.030> when<00:18:55.419> one<00:18:55.780> of<00:18:55.870> our<00:18:55.990> goals<00:18:56.610> has<00:18:57.610> been<00:18:57.640> to 00:18:57.870 --> 00:18:57.880 align:start position:0% today when one of our goals has been to 00:18:57.880 --> 00:19:01.409 align:start position:0% today when one of our goals has been to you<00:18:58.750> know<00:18:58.840> kind<00:18:59.590> of<00:18:59.650> test<00:19:00.549> ground<00:19:00.940> each<00:19:01.240> of 00:19:01.409 --> 00:19:01.419 align:start position:0% you know kind of test ground each of 00:19:01.419 --> 00:19:04.950 align:start position:0% you know kind of test ground each of these<00:19:01.950> and<00:19:03.120> prototype<00:19:04.120> each<00:19:04.360> of<00:19:04.539> these<00:19:04.690> and 00:19:04.950 --> 00:19:04.960 align:start position:0% these and prototype each of these and 00:19:04.960 --> 00:19:07.799 align:start position:0% these and prototype each of these and you<00:19:05.440> know<00:19:05.530> really<00:19:05.860> understand<00:19:06.809> the 00:19:07.799 --> 00:19:07.809 align:start position:0% you know really understand the 00:19:07.809 --> 00:19:12.810 align:start position:0% you know really understand the trade-offs<00:19:08.169> the<00:19:08.470> gains<00:19:10.470> on<00:19:11.470> everything<00:19:11.980> and 00:19:12.810 --> 00:19:12.820 align:start position:0% trade-offs the gains on everything and 00:19:12.820 --> 00:19:15.240 align:start position:0% trade-offs the gains on everything and yeah<00:19:13.240> as<00:19:13.450> Alex<00:19:13.929> said<00:19:14.080> I<00:19:14.590> think<00:19:14.890> the<00:19:15.010> biggest 00:19:15.240 --> 00:19:15.250 align:start position:0% yeah as Alex said I think the biggest 00:19:15.250 --> 00:19:19.980 align:start position:0% yeah as Alex said I think the biggest still<00:19:16.120> today<00:19:16.539> the<00:19:16.690> biggest<00:19:16.960> question<00:19:17.440> is<00:19:18.990> who 00:19:19.980 --> 00:19:19.990 align:start position:0% still today the biggest question is who 00:19:19.990 --> 00:19:22.380 align:start position:0% still today the biggest question is who who's<00:19:20.409> providing<00:19:21.309> state<00:19:21.580> how<00:19:21.850> how<00:19:22.179> are<00:19:22.270> they 00:19:22.380 --> 00:19:22.390 align:start position:0% who's providing state how how are they 00:19:22.390 --> 00:19:28.200 align:start position:0% who's providing state how how are they paid<00:19:22.570> to<00:19:22.780> do<00:19:22.900> that<00:19:23.080> and<00:19:23.409> so<00:19:23.940> we<00:19:25.230> are<00:19:26.940> we<00:19:27.940> kind<00:19:28.150> of 00:19:28.200 --> 00:19:28.210 align:start position:0% paid to do that and so we are we kind of 00:19:28.210 --> 00:19:29.549 align:start position:0% paid to do that and so we are we kind of needed<00:19:28.419> to<00:19:28.539> validate<00:19:29.020> some<00:19:29.169> other<00:19:29.320> things 00:19:29.549 --> 00:19:29.559 align:start position:0% needed to validate some other things 00:19:29.559 --> 00:19:32.789 align:start position:0% needed to validate some other things first<00:19:29.740> like<00:19:30.570> the<00:19:31.570> stateless<00:19:32.200> Iggy's<00:19:32.620> good 00:19:32.789 --> 00:19:32.799 align:start position:0% first like the stateless Iggy's good 00:19:32.799 --> 00:19:34.560 align:start position:0% first like the stateless Iggy's good working<00:19:33.130> time<00:19:33.280> and<00:19:33.640> that's<00:19:33.820> generally<00:19:34.419> been 00:19:34.560 --> 00:19:34.570 align:start position:0% working time and that's generally been 00:19:34.570 --> 00:19:39.450 align:start position:0% working time and that's generally been validated<00:19:34.929> now<00:19:35.200> and<00:19:36.179> so<00:19:37.179> the<00:19:37.690> next<00:19:38.340> you<00:19:39.340> know 00:19:39.450 --> 00:19:39.460 align:start position:0% validated now and so the next you know 00:19:39.460 --> 00:19:41.370 align:start position:0% validated now and so the next you know the<00:19:39.490> next<00:19:39.610> step<00:19:39.850> is<00:19:40.150> really<00:19:40.330> beginning<00:19:41.140> to 00:19:41.370 --> 00:19:41.380 align:start position:0% the next step is really beginning to 00:19:41.380 --> 00:19:45.120 align:start position:0% the next step is really beginning to validate<00:19:41.830> that<00:19:42.220> question<00:19:43.169> regarding<00:19:44.169> the 00:19:45.120 --> 00:19:45.130 align:start position:0% validate that question regarding the 00:19:45.130 --> 00:19:47.010 align:start position:0% validate that question regarding the state<00:19:45.370> of<00:19:45.490> free<00:19:45.640> market<00:19:46.030> and<00:19:46.539> then<00:19:46.690> after<00:19:46.900> that 00:19:47.010 --> 00:19:47.020 align:start position:0% state of free market and then after that 00:19:47.020 --> 00:19:50.340 align:start position:0% state of free market and then after that is<00:19:47.289> is<00:19:47.799> really<00:19:48.190> expanding<00:19:48.760> a<00:19:49.030> lot<00:19:49.210> of<00:19:49.990> the 00:19:50.340 --> 00:19:50.350 align:start position:0% is is really expanding a lot of the 00:19:50.350 --> 00:19:52.690 align:start position:0% is is really expanding a lot of the things<00:19:50.559> around<00:19:50.679> cross<00:19:51.039> our<00:19:51.250> transactions 00:19:52.690 --> 00:19:52.700 align:start position:0% things around cross our transactions 00:19:52.700 --> 00:19:56.620 align:start position:0% things around cross our transactions but<00:19:53.690> I<00:19:54.020> from<00:19:54.980> an<00:19:55.070> optimistic<00:19:55.630> perspective 00:19:56.620 --> 00:19:56.630 align:start position:0% but I from an optimistic perspective 00:19:56.630 --> 00:19:59.650 align:start position:0% but I from an optimistic perspective there<00:19:57.080> are<00:19:57.400> there<00:19:58.400> is<00:19:58.429> a<00:19:58.549> lot<00:19:58.820> of<00:19:58.970> content<00:19:59.419> and 00:19:59.650 --> 00:19:59.660 align:start position:0% there are there is a lot of content and 00:19:59.660 --> 00:20:02.260 align:start position:0% there are there is a lot of content and a<00:19:59.929> lot<00:20:00.140> of<00:20:00.260> proposals<00:20:00.590> in<00:20:00.799> a<00:20:00.919> lot<00:20:01.100> of<00:20:01.270> really 00:20:02.260 --> 00:20:02.270 align:start position:0% a lot of proposals in a lot of really 00:20:02.270 --> 00:20:06.720 align:start position:0% a lot of proposals in a lot of really promising<00:20:02.720> directions<00:20:03.230> for<00:20:03.679> all<00:20:03.710> of<00:20:03.950> these<00:20:05.470> so 00:20:06.720 --> 00:20:06.730 align:start position:0% promising directions for all of these so 00:20:06.730 --> 00:20:12.380 align:start position:0% promising directions for all of these so yeah 00:20:12.380 --> 00:20:12.390 align:start position:0% 00:20:12.390 --> 00:20:14.780 align:start position:0% it<00:20:12.960> smells<00:20:13.230> I<00:20:13.380> think<00:20:13.590> it's<00:20:13.980> a<00:20:14.070> good<00:20:14.250> segue 00:20:14.780 --> 00:20:14.790 align:start position:0% it smells I think it's a good segue 00:20:14.790 --> 00:20:18.500 align:start position:0% it smells I think it's a good segue actually<00:20:15.179> to<00:20:15.720> tonight's<00:20:16.650> talk<00:20:16.890> I<00:20:17.270> just<00:20:18.270> want 00:20:18.500 --> 00:20:18.510 align:start position:0% actually to tonight's talk I just want 00:20:18.510 --> 00:20:20.090 align:start position:0% actually to tonight's talk I just want to<00:20:18.690> reiterate<00:20:18.840> the<00:20:19.170> type<00:20:19.380> is<00:20:19.530> what<00:20:19.679> you<00:20:19.799> said 00:20:20.090 --> 00:20:20.100 align:start position:0% to reiterate the type is what you said 00:20:20.100 --> 00:20:21.280 align:start position:0% to reiterate the type is what you said today 00:20:21.280 --> 00:20:21.290 align:start position:0% today 00:20:21.290 --> 00:20:23.480 align:start position:0% today what<00:20:22.290> were<00:20:22.410> the<00:20:22.470> kick<00:20:22.650> started<00:20:22.980> all<00:20:23.070> this<00:20:23.250> work 00:20:23.480 --> 00:20:23.490 align:start position:0% what were the kick started all this work 00:20:23.490 --> 00:20:26.320 align:start position:0% what were the kick started all this work was<00:20:23.790> proposal<00:20:24.450> 2<00:20:24.600> which<00:20:24.900> was<00:20:25.140> an<00:20:25.410> actual<00:20:25.710> real 00:20:26.320 --> 00:20:26.330 align:start position:0% was proposal 2 which was an actual real 00:20:26.330 --> 00:20:29.180 align:start position:0% was proposal 2 which was an actual real thing<00:20:27.330> written<00:20:27.540> down<00:20:27.840> so<00:20:28.140> we<00:20:28.290> could<00:20:28.500> take<00:20:29.130> a 00:20:29.180 --> 00:20:29.190 align:start position:0% thing written down so we could take a 00:20:29.190 --> 00:20:31.070 align:start position:0% thing written down so we could take a look<00:20:29.309> at<00:20:29.429> they<00:20:29.549> don't<00:20:29.670> do<00:20:29.790> something<00:20:30.000> but<00:20:30.870> up 00:20:31.070 --> 00:20:31.080 align:start position:0% look at they don't do something but up 00:20:31.080 --> 00:20:32.600 align:start position:0% look at they don't do something but up to<00:20:31.230> that<00:20:31.350> point<00:20:31.559> everything<00:20:31.920> happened<00:20:32.429> just 00:20:32.600 --> 00:20:32.610 align:start position:0% to that point everything happened just 00:20:32.610 --> 00:20:34.100 align:start position:0% to that point everything happened just on<00:20:32.850> each<00:20:33.030> researching<00:20:33.720> different 00:20:34.100 --> 00:20:34.110 align:start position:0% on each researching different 00:20:34.110 --> 00:20:37.340 align:start position:0% on each researching different discussions<00:20:35.090> it's<00:20:36.090> easy<00:20:36.570> to<00:20:36.750> discuss<00:20:37.110> stuff 00:20:37.340 --> 00:20:37.350 align:start position:0% discussions it's easy to discuss stuff 00:20:37.350 --> 00:20:40.520 align:start position:0% discussions it's easy to discuss stuff twist<00:20:37.830> on<00:20:38.040> different<00:20:38.549> texts<00:20:39.480> but<00:20:40.200> it's<00:20:40.380> also 00:20:40.520 --> 00:20:40.530 align:start position:0% twist on different texts but it's also 00:20:40.530 --> 00:20:42.110 align:start position:0% twist on different texts but it's also kind<00:20:40.799> of<00:20:40.890> hard<00:20:41.100> to<00:20:41.160> know<00:20:41.610> which<00:20:41.850> direction 00:20:42.110 --> 00:20:42.120 align:start position:0% kind of hard to know which direction 00:20:42.120 --> 00:20:45.230 align:start position:0% kind of hard to know which direction actually<00:20:42.480> make<00:20:42.840> sense<00:20:43.049> in<00:20:43.350> practice<00:20:44.090> so<00:20:45.090> this 00:20:45.230 --> 00:20:45.240 align:start position:0% actually make sense in practice so this 00:20:45.240 --> 00:20:46.789 align:start position:0% actually make sense in practice so this was<00:20:45.419> a<00:20:45.450> big<00:20:45.660> banquet<00:20:46.020> with<00:20:46.290> that<00:20:46.440> kind<00:20:46.740> of 00:20:46.789 --> 00:20:46.799 align:start position:0% was a big banquet with that kind of 00:20:46.799 --> 00:20:49.730 align:start position:0% was a big banquet with that kind of mindset<00:20:47.160> we<00:20:47.910> started<00:20:48.360> to<00:20:48.720> teach<00:20:49.049> a<00:20:49.230> proposal 00:20:49.730 --> 00:20:49.740 align:start position:0% mindset we started to teach a proposal 00:20:49.740 --> 00:20:52.340 align:start position:0% mindset we started to teach a proposal to<00:20:50.010> as<00:20:50.190> it<00:20:50.340> is<00:20:50.480> violently<00:20:51.480> implemented<00:20:51.780> it<00:20:52.140> and 00:20:52.340 --> 00:20:52.350 align:start position:0% to as it is violently implemented it and 00:20:52.350 --> 00:20:55.460 align:start position:0% to as it is violently implemented it and tried<00:20:53.340> to<00:20:53.370> validate<00:20:53.820> certain<00:20:54.179> aspects<00:20:54.960> and 00:20:55.460 --> 00:20:55.470 align:start position:0% tried to validate certain aspects and 00:20:55.470 --> 00:20:57.740 align:start position:0% tried to validate certain aspects and that<00:20:55.799> implementation<00:20:56.280> is<00:20:56.580> is<00:20:57.179> what<00:20:57.419> it<00:20:57.510> said 00:20:57.740 --> 00:20:57.750 align:start position:0% that implementation is is what it said 00:20:57.750 --> 00:21:00.770 align:start position:0% that implementation is is what it said so<00:20:58.049> basically<00:20:58.770> we<00:20:58.919> took<00:20:59.419> this<00:21:00.419> proposal 00:21:00.770 --> 00:21:00.780 align:start position:0% so basically we took this proposal 00:21:00.780 --> 00:21:03.830 align:start position:0% so basically we took this proposal implemented<00:21:01.710> it<00:21:01.830> and<00:21:02.250> we<00:21:03.150> started<00:21:03.510> out<00:21:03.660> with 00:21:03.830 --> 00:21:03.840 align:start position:0% implemented it and we started out with 00:21:03.840 --> 00:21:06.710 align:start position:0% implemented it and we started out with just<00:21:03.929> the<00:21:04.860> goal<00:21:05.130> of<00:21:05.370> validating<00:21:06.000> those<00:21:06.360> basic 00:21:06.710 --> 00:21:06.720 align:start position:0% just the goal of validating those basic 00:21:06.720 --> 00:21:08.539 align:start position:0% just the goal of validating those basic assumptions<00:21:07.320> and<00:21:07.530> the<00:21:07.590> basic<00:21:07.860> assumption<00:21:08.400> we 00:21:08.539 --> 00:21:08.549 align:start position:0% assumptions and the basic assumption we 00:21:08.549 --> 00:21:11.030 align:start position:0% assumptions and the basic assumption we had<00:21:08.760> is<00:21:09.330> here<00:21:09.570> the<00:21:09.720> limits<00:21:10.080> of<00:21:10.230> time<00:21:10.620> you<00:21:10.830> can 00:21:11.030 --> 00:21:11.040 align:start position:0% had is here the limits of time you can 00:21:11.040 --> 00:21:13.850 align:start position:0% had is here the limits of time you can spend<00:21:11.370> and<00:21:11.970> at<00:21:12.090> every<00:21:12.900> sharp<00:21:13.380> block<00:21:13.650> on 00:21:13.850 --> 00:21:13.860 align:start position:0% spend and at every sharp block on 00:21:13.860 --> 00:21:17.030 align:start position:0% spend and at every sharp block on processing<00:21:14.669> and<00:21:15.090> we<00:21:16.080> all<00:21:16.169> set<00:21:16.350> limits<00:21:16.679> of<00:21:16.860> how 00:21:17.030 --> 00:21:17.040 align:start position:0% processing and we all set limits of how 00:21:17.040 --> 00:21:19.190 align:start position:0% processing and we all set limits of how much<00:21:17.160> data<00:21:17.429> we<00:21:17.580> can<00:21:17.760> supply<00:21:18.120> to<00:21:18.419> these 00:21:19.190 --> 00:21:19.200 align:start position:0% much data we can supply to these 00:21:19.200 --> 00:21:22.370 align:start position:0% much data we can supply to these execution<00:21:19.710> environments<00:21:20.220> and<00:21:21.260> basically<00:21:22.260> we 00:21:22.370 --> 00:21:22.380 align:start position:0% execution environments and basically we 00:21:22.380 --> 00:21:27.590 align:start position:0% execution environments and basically we had<00:21:22.650> to<00:21:22.860> write<00:21:23.370> some<00:21:23.549> code<00:21:25.010> in<00:21:26.010> Watson<00:21:26.700> which 00:21:27.590 --> 00:21:27.600 align:start position:0% had to write some code in Watson which 00:21:27.600 --> 00:21:30.049 align:start position:0% had to write some code in Watson which takes<00:21:27.900> this<00:21:28.080> data<00:21:28.320> tries<00:21:29.160> to<00:21:29.309> do<00:21:29.400> transactions 00:21:30.049 --> 00:21:30.059 align:start position:0% takes this data tries to do transactions 00:21:30.059 --> 00:21:33.260 align:start position:0% takes this data tries to do transactions and<00:21:30.270> fit<00:21:31.140> into<00:21:31.440> the<00:21:31.679> time<00:21:31.950> limit<00:21:32.220> so<00:21:32.790> this<00:21:33.090> is 00:21:33.260 --> 00:21:33.270 align:start position:0% and fit into the time limit so this is 00:21:33.270 --> 00:21:36.110 align:start position:0% and fit into the time limit so this is what<00:21:33.390> we<00:21:33.510> have<00:21:33.660> done<00:21:34.250> and<00:21:35.250> once<00:21:35.549> we<00:21:35.760> got<00:21:35.910> like 00:21:36.110 --> 00:21:36.120 align:start position:0% what we have done and once we got like 00:21:36.120 --> 00:21:37.340 align:start position:0% what we have done and once we got like two<00:21:36.270> really<00:21:36.419> good<00:21:36.540> numbers<00:21:36.870> and<00:21:37.169> then<00:21:37.320> we 00:21:37.340 --> 00:21:37.350 align:start position:0% two really good numbers and then we 00:21:37.350 --> 00:21:38.870 align:start position:0% two really good numbers and then we solved<00:21:37.799> all<00:21:37.919> these<00:21:38.070> different<00:21:38.340> problems<00:21:38.700> so<00:21:38.850> a 00:21:38.870 --> 00:21:38.880 align:start position:0% solved all these different problems so a 00:21:38.880 --> 00:21:41.360 align:start position:0% solved all these different problems so a couple<00:21:39.120> months<00:21:39.419> of<00:21:39.690> time<00:21:39.900> then<00:21:40.890> we<00:21:40.980> started<00:21:41.280> to 00:21:41.360 --> 00:21:41.370 align:start position:0% couple months of time then we started to 00:21:41.370 --> 00:21:43.909 align:start position:0% couple months of time then we started to look<00:21:41.400> at<00:21:41.669> the<00:21:42.419> prettier<00:21:42.720> stuff<00:21:43.110> how<00:21:43.590> do<00:21:43.650> these 00:21:43.909 --> 00:21:43.919 align:start position:0% look at the prettier stuff how do these 00:21:43.919 --> 00:21:46.789 align:start position:0% look at the prettier stuff how do these things<00:21:44.190> actually<00:21:44.340> get<00:21:44.790> the<00:21:45.030> data<00:21:45.270> and<00:21:45.620> the<00:21:46.620> fee 00:21:46.789 --> 00:21:46.799 align:start position:0% things actually get the data and the fee 00:21:46.799 --> 00:21:49.789 align:start position:0% things actually get the data and the fee stuff<00:21:47.419> in<00:21:48.419> a<00:21:48.570> long<00:21:48.720> session<00:21:48.960> discussing<00:21:49.440> this 00:21:49.789 --> 00:21:49.799 align:start position:0% stuff in a long session discussing this 00:21:49.799 --> 00:21:53.090 align:start position:0% stuff in a long session discussing this on<00:21:50.460> a<00:21:50.610> whiteboard<00:21:51.350> and<00:21:52.350> kind<00:21:52.530> of<00:21:52.590> realize<00:21:52.860> that 00:21:53.090 --> 00:21:53.100 align:start position:0% on a whiteboard and kind of realize that 00:21:53.100 --> 00:21:56.240 align:start position:0% on a whiteboard and kind of realize that it's<00:21:53.220> insanely<00:21:54.090> complex<00:21:54.740> and<00:21:55.740> I<00:21:55.950> think<00:21:55.980> that's 00:21:56.240 --> 00:21:56.250 align:start position:0% it's insanely complex and I think that's 00:21:56.250 --> 00:21:58.220 align:start position:0% it's insanely complex and I think that's that's<00:21:56.549> one<00:21:56.669> of<00:21:56.760> the<00:21:56.850> reasons<00:21:57.210> we<00:21:58.080> can 00:21:58.220 --> 00:21:58.230 align:start position:0% that's one of the reasons we can 00:21:58.230 --> 00:21:59.480 align:start position:0% that's one of the reasons we can actually<00:21:58.470> just<00:21:58.620> look<00:21:58.740> in<00:21:58.890> isolation<00:21:59.220> with 00:21:59.480 --> 00:21:59.490 align:start position:0% actually just look in isolation with 00:21:59.490 --> 00:22:01.070 align:start position:0% actually just look in isolation with these<00:21:59.640> things<00:21:59.880> we<00:22:00.030> have<00:22:00.120> to<00:22:00.150> do<00:22:00.360> we<00:22:00.900> have<00:22:00.929> to 00:22:01.070 --> 00:22:01.080 align:start position:0% these things we have to do we have to 00:22:01.080 --> 00:22:04.220 align:start position:0% these things we have to do we have to look<00:22:01.200> at<00:22:01.350> them<00:22:01.530> more<00:22:02.120> integrated<00:22:03.120> way<00:22:03.240> and<00:22:03.450> I 00:22:04.220 --> 00:22:04.230 align:start position:0% look at them more integrated way and I 00:22:04.230 --> 00:22:05.690 align:start position:0% look at them more integrated way and I think<00:22:04.290> probably<00:22:04.740> was<00:22:05.010> one<00:22:05.160> of<00:22:05.250> the<00:22:05.370> reason 00:22:05.690 --> 00:22:05.700 align:start position:0% think probably was one of the reason 00:22:05.700 --> 00:22:08.510 align:start position:0% think probably was one of the reason that<00:22:06.330> these<00:22:06.510> new<00:22:06.690> proposals<00:22:07.260> were<00:22:07.520> inspired 00:22:08.510 --> 00:22:08.520 align:start position:0% that these new proposals were inspired 00:22:08.520 --> 00:22:10.669 align:start position:0% that these new proposals were inspired by<00:22:08.669> so<00:22:09.390> I<00:22:09.450> expect<00:22:09.809> that<00:22:10.080> they're<00:22:10.260> gonna<00:22:10.410> be<00:22:10.590> as 00:22:10.669 --> 00:22:10.679 align:start position:0% by so I expect that they're gonna be as 00:22:10.679 --> 00:22:11.840 align:start position:0% by so I expect that they're gonna be as we<00:22:10.860> look<00:22:11.040> at<00:22:11.130> more<00:22:11.250> of<00:22:11.400> these<00:22:11.490> different 00:22:11.840 --> 00:22:11.850 align:start position:0% we look at more of these different 00:22:11.850 --> 00:22:14.150 align:start position:0% we look at more of these different problems<00:22:12.270> and<00:22:13.169> not<00:22:13.290> just<00:22:13.350> you<00:22:13.740> know<00:22:13.799> one 00:22:14.150 --> 00:22:14.160 align:start position:0% problems and not just you know one 00:22:14.160 --> 00:22:15.919 align:start position:0% problems and not just you know one problem<00:22:14.490> at<00:22:14.580> a<00:22:14.669> time<00:22:14.700> they're<00:22:15.540> gonna<00:22:15.660> be<00:22:15.809> more 00:22:15.919 --> 00:22:15.929 align:start position:0% problem at a time they're gonna be more 00:22:15.929 --> 00:22:16.700 align:start position:0% problem at a time they're gonna be more and<00:22:16.049> more<00:22:16.110> proposed 00:22:16.700 --> 00:22:16.710 align:start position:0% and more proposed 00:22:16.710 --> 00:22:18.049 align:start position:0% and more proposed and<00:22:16.799> we're<00:22:16.950> gonna<00:22:17.039> get<00:22:17.429> closer<00:22:17.730> to<00:22:17.970> the 00:22:18.049 --> 00:22:18.059 align:start position:0% and we're gonna get closer to the 00:22:18.059 --> 00:22:26.649 align:start position:0% and we're gonna get closer to the solution<00:22:20.870> so<00:22:21.870> scant<00:22:22.529> itself<00:22:23.600> listening<00:22:24.600> Tom 00:22:26.649 --> 00:22:26.659 align:start position:0% solution so scant itself listening Tom 00:22:26.659 --> 00:22:31.010 align:start position:0% solution so scant itself listening Tom okay<00:22:28.010> so<00:22:29.010> as<00:22:29.130> I<00:22:29.279> said<00:22:29.490> it's<00:22:29.760> this<00:22:30.059> actual 00:22:31.010 --> 00:22:31.020 align:start position:0% okay so as I said it's this actual 00:22:31.020 --> 00:22:33.919 align:start position:0% okay so as I said it's this actual tangible<00:22:31.200> tangible<00:22:32.029> piece<00:22:33.029> of<00:22:33.210> code<00:22:33.539> you<00:22:33.779> can 00:22:33.919 --> 00:22:33.929 align:start position:0% tangible tangible piece of code you can 00:22:33.929 --> 00:22:36.980 align:start position:0% tangible tangible piece of code you can interact<00:22:34.230> with<00:22:34.470> it's<00:22:35.100> not<00:22:35.279> just<00:22:35.580> the<00:22:35.700> text<00:22:36.059> so 00:22:36.980 --> 00:22:36.990 align:start position:0% interact with it's not just the text so 00:22:36.990 --> 00:22:39.680 align:start position:0% interact with it's not just the text so if<00:22:37.080> influence<00:22:37.740> that<00:22:37.919> proposal<00:22:38.460> -<00:22:38.640> we<00:22:39.330> do<00:22:39.480> plan 00:22:39.680 --> 00:22:39.690 align:start position:0% if influence that proposal - we do plan 00:22:39.690 --> 00:22:41.899 align:start position:0% if influence that proposal - we do plan to<00:22:39.870> take<00:22:40.049> in<00:22:40.230> the<00:22:40.409> the<00:22:40.649> changes<00:22:41.159> from 00:22:41.899 --> 00:22:41.909 align:start position:0% to take in the the changes from 00:22:41.909 --> 00:22:43.370 align:start position:0% to take in the the changes from different<00:22:42.179> proposals<00:22:42.630> and<00:22:42.809> we<00:22:42.960> also<00:22:43.080> want<00:22:43.320> to 00:22:43.370 --> 00:22:43.380 align:start position:0% different proposals and we also want to 00:22:43.380 --> 00:22:45.440 align:start position:0% different proposals and we also want to come<00:22:43.500> up<00:22:43.590> with<00:22:43.710> our<00:22:43.860> own<00:22:44.070> proposals<00:22:44.610> but<00:22:45.299> we 00:22:45.440 --> 00:22:45.450 align:start position:0% come up with our own proposals but we 00:22:45.450 --> 00:22:46.700 align:start position:0% come up with our own proposals but we haven't<00:22:45.570> done<00:22:45.809> that<00:22:45.870> yet<00:22:46.049> we<00:22:46.409> were<00:22:46.500> really 00:22:46.700 --> 00:22:46.710 align:start position:0% haven't done that yet we were really 00:22:46.710 --> 00:22:49.279 align:start position:0% haven't done that yet we were really focusing<00:22:47.130> on<00:22:47.279> getting<00:22:47.909> those<00:22:48.059> core<00:22:48.510> basic 00:22:49.279 --> 00:22:49.289 align:start position:0% focusing on getting those core basic 00:22:49.289 --> 00:22:52.669 align:start position:0% focusing on getting those core basic things<00:22:49.500> as<00:22:49.710> for<00:22:49.980> regarding<00:22:50.610> speed<00:22:51.679> it 00:22:52.669 --> 00:22:52.679 align:start position:0% things as for regarding speed it 00:22:52.679 --> 00:22:54.940 align:start position:0% things as for regarding speed it actually<00:22:52.799> black<00:22:53.279> does<00:22:53.760> it<00:22:53.880> in<00:22:53.970> a<00:22:54.000> pointer 00:22:54.940 --> 00:22:54.950 align:start position:0% actually black does it in a pointer 00:22:54.950 --> 00:22:57.860 align:start position:0% actually black does it in a pointer doesn't<00:22:55.950> work<00:22:56.130> so<00:22:56.909> it's<00:22:57.029> black<00:22:57.149> box<00:22:57.450> is<00:22:57.600> most 00:22:57.860 --> 00:22:57.870 align:start position:0% doesn't work so it's black box is most 00:22:57.870 --> 00:23:00.200 align:start position:0% doesn't work so it's black box is most of<00:22:58.049> the<00:22:58.230> stuff<00:22:58.830> you<00:22:58.860> don't<00:22:59.130> care<00:22:59.309> about<00:22:59.370> and 00:23:00.200 --> 00:23:00.210 align:start position:0% of the stuff you don't care about and 00:23:00.210 --> 00:23:01.669 align:start position:0% of the stuff you don't care about and just<00:23:00.539> stuff<00:23:00.690> you<00:23:00.809> don't<00:23:00.929> care<00:23:01.169> about<00:23:01.260> at<00:23:01.500> least 00:23:01.669 --> 00:23:01.679 align:start position:0% just stuff you don't care about at least 00:23:01.679 --> 00:23:04.159 align:start position:0% just stuff you don't care about at least that<00:23:02.190> that<00:23:02.610> point<00:23:02.850> of<00:23:03.000> time<00:23:03.029> is<00:23:03.539> whatever<00:23:03.870> is 00:23:04.159 --> 00:23:04.169 align:start position:0% that that point of time is whatever is 00:23:04.169 --> 00:23:06.529 align:start position:0% that that point of time is whatever is happening<00:23:04.500> on<00:23:04.620> the<00:23:04.679> video<00:23:04.919> channel<00:23:05.309> I<00:23:05.539> never 00:23:06.529 --> 00:23:06.539 align:start position:0% happening on the video channel I never 00:23:06.539 --> 00:23:10.220 align:start position:0% happening on the video channel I never do<00:23:07.140> expect<00:23:07.740> that<00:23:07.860> with<00:23:08.130> time<00:23:08.490> as<00:23:08.700> we<00:23:08.880> get<00:23:09.299> more 00:23:10.220 --> 00:23:10.230 align:start position:0% do expect that with time as we get more 00:23:10.230 --> 00:23:12.470 align:start position:0% do expect that with time as we get more closer<00:23:10.590> to<00:23:10.799> figuring<00:23:11.010> things<00:23:11.490> out<00:23:11.760> and<00:23:12.149> in<00:23:12.419> a 00:23:12.470 --> 00:23:12.480 align:start position:0% closer to figuring things out and in a 00:23:12.480 --> 00:23:14.149 align:start position:0% closer to figuring things out and in a drawer<00:23:12.690> did<00:23:12.899> more<00:23:13.049> complex<00:23:13.500> because<00:23:13.860> it<00:23:14.010> has 00:23:14.149 --> 00:23:14.159 align:start position:0% drawer did more complex because it has 00:23:14.159 --> 00:23:16.430 align:start position:0% drawer did more complex because it has to<00:23:14.309> take<00:23:14.520> in<00:23:14.700> more<00:23:15.270> things<00:23:15.510> from<00:23:15.929> from<00:23:16.260> the 00:23:16.430 --> 00:23:16.440 align:start position:0% to take in more things from from the 00:23:16.440 --> 00:23:19.070 align:start position:0% to take in more things from from the different<00:23:16.740> phases<00:23:17.450> but<00:23:18.450> right<00:23:18.659> now<00:23:18.870> it's 00:23:19.070 --> 00:23:19.080 align:start position:0% different phases but right now it's 00:23:19.080 --> 00:23:21.889 align:start position:0% different phases but right now it's pretty<00:23:19.260> simple<00:23:20.090> that<00:23:21.090> still<00:23:21.390> there<00:23:21.659> were<00:23:21.720> job 00:23:21.889 --> 00:23:21.899 align:start position:0% pretty simple that still there were job 00:23:21.899 --> 00:23:24.310 align:start position:0% pretty simple that still there were job announcement<00:23:22.529> URL<00:23:22.919> you<00:23:23.070> can<00:23:23.250> feed<00:23:23.640> a<00:23:23.669> bit<00:23:23.880> more 00:23:24.310 --> 00:23:24.320 align:start position:0% announcement URL you can feed a bit more 00:23:24.320 --> 00:23:27.620 align:start position:0% announcement URL you can feed a bit more reasoning<00:23:25.320> and<00:23:25.710> you<00:23:26.190> know<00:23:26.279> how<00:23:26.370> does<00:23:26.520> it<00:23:26.549> work 00:23:27.620 --> 00:23:27.630 align:start position:0% reasoning and you know how does it work 00:23:27.630 --> 00:23:30.590 align:start position:0% reasoning and you know how does it work but<00:23:28.409> the<00:23:28.830> URL<00:23:29.250> that<00:23:29.549> the<00:23:29.640> github<00:23:29.789> URL<00:23:30.059> is<00:23:30.390> where 00:23:30.590 --> 00:23:30.600 align:start position:0% but the URL that the github URL is where 00:23:30.600 --> 00:23:34.310 align:start position:0% but the URL that the github URL is where all<00:23:30.809> the<00:23:30.990> dakotas<00:23:32.570> just<00:23:33.570> kind<00:23:33.840> of<00:23:33.899> itself 00:23:34.310 --> 00:23:34.320 align:start position:0% all the dakotas just kind of itself 00:23:34.320 --> 00:23:35.480 align:start position:0% all the dakotas just kind of itself there's<00:23:34.559> a<00:23:34.649> couple<00:23:34.860> of<00:23:34.980> different<00:23:35.250> ads 00:23:35.480 --> 00:23:35.490 align:start position:0% there's a couple of different ads 00:23:35.490 --> 00:23:37.159 align:start position:0% there's a couple of different ads actually<00:23:35.940> are<00:23:36.029> going<00:23:36.149> to<00:23:36.210> go<00:23:36.330> into<00:23:36.539> this<00:23:36.630> but 00:23:37.159 --> 00:23:37.169 align:start position:0% actually are going to go into this but 00:23:37.169 --> 00:23:44.330 align:start position:0% actually are going to go into this but the<00:23:37.559> thing<00:23:37.799> we<00:23:37.950> call<00:23:38.610> scared<00:23:39.210> is<00:23:39.679> this 00:23:44.330 --> 00:23:44.340 align:start position:0% 00:23:44.340 --> 00:23:46.610 align:start position:0% so<00:23:44.640> basically<00:23:44.940> scans<00:23:45.360> does<00:23:46.020> a<00:23:46.289> couple<00:23:46.500> of 00:23:46.610 --> 00:23:46.620 align:start position:0% so basically scans does a couple of 00:23:46.620 --> 00:23:49.399 align:start position:0% so basically scans does a couple of different<00:23:46.710> things<00:23:47.870> under<00:23:48.870> the<00:23:48.990> same<00:23:49.200> name<00:23:49.230> so 00:23:49.399 --> 00:23:49.409 align:start position:0% different things under the same name so 00:23:49.409 --> 00:23:51.710 align:start position:0% different things under the same name so it<00:23:49.679> has<00:23:49.860> it<00:23:50.100> is<00:23:50.250> this<00:23:50.399> tool<00:23:50.700> but<00:23:51.390> it<00:23:51.510> also 00:23:51.710 --> 00:23:51.720 align:start position:0% it has it is this tool but it also 00:23:51.720 --> 00:23:53.799 align:start position:0% it has it is this tool but it also defines<00:23:52.169> the<00:23:52.590> API<00:23:52.919> is<00:23:53.010> based<00:23:53.250> on<00:23:53.370> the<00:23:53.460> proposal 00:23:53.799 --> 00:23:53.809 align:start position:0% defines the API is based on the proposal 00:23:53.809 --> 00:23:58.100 align:start position:0% defines the API is based on the proposal it<00:23:54.809> has<00:23:55.020> a<00:23:55.049> testing<00:23:55.529> format<00:23:56.659> and<00:23:57.659> it<00:23:57.899> has<00:23:58.080> a 00:23:58.100 --> 00:23:58.110 align:start position:0% it has a testing format and it has a 00:23:58.110 --> 00:24:00.110 align:start position:0% it has a testing format and it has a couple<00:23:58.320> of<00:23:58.500> example<00:23:58.919> e's<00:23:59.279> me<00:23:59.490> we<00:23:59.760> cannot<00:23:59.940> go 00:24:00.110 --> 00:24:00.120 align:start position:0% couple of example e's me we cannot go 00:24:00.120 --> 00:24:04.250 align:start position:0% couple of example e's me we cannot go into<00:24:00.149> that<00:24:00.510> in<00:24:01.049> a<00:24:01.289> second<00:24:01.620> so<00:24:02.840> the<00:24:03.840> ordinary 00:24:04.250 --> 00:24:04.260 align:start position:0% into that in a second so the ordinary 00:24:04.260 --> 00:24:06.860 align:start position:0% into that in a second so the ordinary original<00:24:05.010> scared<00:24:05.340> I<00:24:05.640> must<00:24:06.390> be<00:24:06.480> talking<00:24:06.600> about 00:24:06.860 --> 00:24:06.870 align:start position:0% original scared I must be talking about 00:24:06.870 --> 00:24:11.060 align:start position:0% original scared I must be talking about is<00:24:07.200> written<00:24:07.529> in<00:24:07.649> rust<00:24:08.240> and<00:24:09.260> it's<00:24:10.260> it's<00:24:10.559> really 00:24:11.060 --> 00:24:11.070 align:start position:0% is written in rust and it's it's really 00:24:11.070 --> 00:24:12.740 align:start position:0% is written in rust and it's it's really small<00:24:11.279> it's<00:24:11.520> a<00:24:11.640> tener<00:24:11.880> that's<00:24:12.090> like<00:24:12.240> 300<00:24:12.450> lines 00:24:12.740 --> 00:24:12.750 align:start position:0% small it's a tener that's like 300 lines 00:24:12.750 --> 00:24:14.690 align:start position:0% small it's a tener that's like 300 lines of<00:24:12.929> code<00:24:13.140> that's<00:24:13.529> that's<00:24:14.100> all<00:24:14.340> what<00:24:14.549> was 00:24:14.690 --> 00:24:14.700 align:start position:0% of code that's that's all what was 00:24:14.700 --> 00:24:18.500 align:start position:0% of code that's that's all what was needed<00:24:14.850> to<00:24:15.659> implement<00:24:16.220> proposal<00:24:17.220> to<00:24:17.450> in<00:24:18.450> a 00:24:18.500 --> 00:24:18.510 align:start position:0% needed to implement proposal to in a 00:24:18.510 --> 00:24:20.690 align:start position:0% needed to implement proposal to in a black<00:24:18.690> woods<00:24:18.899> manner<00:24:19.110> it<00:24:19.710> uses<00:24:20.070> waz<00:24:20.279> me<00:24:20.490> which 00:24:20.690 --> 00:24:20.700 align:start position:0% black woods manner it uses waz me which 00:24:20.700 --> 00:24:22.400 align:start position:0% black woods manner it uses waz me which is<00:24:20.820> was<00:24:21.000> an<00:24:21.120> interpreter<00:24:21.539> and 00:24:22.400 --> 00:24:22.410 align:start position:0% is was an interpreter and 00:24:22.410 --> 00:24:23.660 align:start position:0% is was an interpreter and the<00:24:22.470> compiler<00:24:22.770> engine<00:24:23.160> it's<00:24:23.280> it's<00:24:23.550> an 00:24:23.660 --> 00:24:23.670 align:start position:0% the compiler engine it's it's an 00:24:23.670 --> 00:24:26.630 align:start position:0% the compiler engine it's it's an interpreter<00:24:24.210> it's<00:24:24.540> written<00:24:24.720> in<00:24:24.960> rust<00:24:25.610> but<00:24:26.610> a 00:24:26.630 --> 00:24:26.640 align:start position:0% interpreter it's written in rust but a 00:24:26.640 --> 00:24:28.070 align:start position:0% interpreter it's written in rust but a waste<00:24:26.850> game<00:24:27.030> is<00:24:27.150> written<00:24:27.420> you<00:24:27.540> can<00:24:27.720> you<00:24:27.930> can 00:24:28.070 --> 00:24:28.080 align:start position:0% waste game is written you can you can 00:24:28.080 --> 00:24:30.440 align:start position:0% waste game is written you can you can survive<00:24:28.380> two<00:24:28.650> different<00:24:29.280> engines<00:24:29.670> this 00:24:30.440 --> 00:24:30.450 align:start position:0% survive two different engines this 00:24:30.450 --> 00:24:34.880 align:start position:0% survive two different engines this engines<00:24:30.840> that<00:24:30.990> will<00:24:31.140> be<00:24:31.290> important<00:24:31.800> later<00:24:33.890> and 00:24:34.880 --> 00:24:34.890 align:start position:0% engines that will be important later and 00:24:34.890 --> 00:24:37.160 align:start position:0% engines that will be important later and the<00:24:35.610> user<00:24:35.910> wasn't<00:24:36.270> my<00:24:36.360> tools<00:24:36.600> recovered<00:24:37.020> it<00:24:37.140> a 00:24:37.160 --> 00:24:37.170 align:start position:0% the user wasn't my tools recovered it a 00:24:37.170 --> 00:24:39.890 align:start position:0% the user wasn't my tools recovered it a couple<00:24:37.380> of<00:24:37.470> times<00:24:37.740> already<00:24:37.980> but<00:24:38.810> there's<00:24:39.810> this 00:24:39.890 --> 00:24:39.900 align:start position:0% couple of times already but there's this 00:24:39.900 --> 00:24:42.920 align:start position:0% couple of times already but there's this other<00:24:40.050> schedule<00:24:40.560> today<00:24:41.190> scattered<00:24:42.120> TS<00:24:42.570> switch 00:24:42.920 --> 00:24:42.930 align:start position:0% other schedule today scattered TS switch 00:24:42.930 --> 00:24:44.750 align:start position:0% other schedule today scattered TS switch if<00:24:43.260> one<00:24:43.410> has<00:24:43.500> the<00:24:43.590> same<00:24:43.740> API<00:24:44.100> mode<00:24:44.310> is<00:24:44.430> written 00:24:44.750 --> 00:24:44.760 align:start position:0% if one has the same API mode is written 00:24:44.760 --> 00:24:49.280 align:start position:0% if one has the same API mode is written in<00:24:44.880> typescript<00:24:45.890> and<00:24:47.450> that<00:24:48.450> uses<00:24:48.870> of<00:24:48.990> course 00:24:49.280 --> 00:24:49.290 align:start position:0% in typescript and that uses of course 00:24:49.290 --> 00:24:52.030 align:start position:0% in typescript and that uses of course notes<00:24:49.740> who<00:24:50.040> uses<00:24:50.250> a<00:24:50.430> fast<00:24:50.760> compiler<00:24:51.300> engine 00:24:52.030 --> 00:24:52.040 align:start position:0% notes who uses a fast compiler engine 00:24:52.040 --> 00:24:54.280 align:start position:0% notes who uses a fast compiler engine therefore<00:24:53.040> you<00:24:53.100> can<00:24:53.250> do<00:24:53.340> more<00:24:53.490> stuff<00:24:53.550> in<00:24:54.030> time 00:24:54.280 --> 00:24:54.290 align:start position:0% therefore you can do more stuff in time 00:24:54.290 --> 00:24:57.830 align:start position:0% therefore you can do more stuff in time but<00:24:55.290> a<00:24:55.650> quick<00:24:56.520> question<00:24:56.700> did<00:24:56.970> anybody<00:24:57.450> of<00:24:57.600> you 00:24:57.830 --> 00:24:57.840 align:start position:0% but a quick question did anybody of you 00:24:57.840 --> 00:25:00.980 align:start position:0% but a quick question did anybody of you seen<00:24:58.350> yesterday<00:24:59.040> it<00:24:59.880> wasn't<00:25:00.120> 1.0<00:25:00.600> session 00:25:00.980 --> 00:25:00.990 align:start position:0% seen yesterday it wasn't 1.0 session 00:25:00.990 --> 00:25:04.970 align:start position:0% seen yesterday it wasn't 1.0 session with<00:25:01.140> benchmarking<00:25:03.080> yet<00:25:04.080> so<00:25:04.260> you<00:25:04.320> know<00:25:04.590> from 00:25:04.970 --> 00:25:04.980 align:start position:0% with benchmarking yet so you know from 00:25:04.980 --> 00:25:08.680 align:start position:0% with benchmarking yet so you know from that<00:25:05.090> that<00:25:06.090> we<00:25:06.510> won't<00:25:06.720> use<00:25:07.020> fast<00:25:07.890> interpreters 00:25:08.680 --> 00:25:08.690 align:start position:0% that that we won't use fast interpreters 00:25:08.690 --> 00:25:13.760 align:start position:0% that that we won't use fast interpreters so<00:25:09.690> v8<00:25:10.080> is<00:25:10.290> not<00:25:10.440> something<00:25:10.860> you<00:25:11.010> would<00:25:11.130> use<00:25:12.770> at 00:25:13.760 --> 00:25:13.770 align:start position:0% so v8 is not something you would use at 00:25:13.770 --> 00:25:15.410 align:start position:0% so v8 is not something you would use at least<00:25:14.010> soon<00:25:14.370> it's<00:25:14.700> not<00:25:14.850> something<00:25:15.180> you<00:25:15.300> would 00:25:15.410 --> 00:25:15.420 align:start position:0% least soon it's not something you would 00:25:15.420 --> 00:25:18.050 align:start position:0% least soon it's not something you would use<00:25:15.480> so<00:25:15.780> if<00:25:15.900> you<00:25:16.080> use<00:25:16.380> scabbit<00:25:17.370> TS<00:25:17.670> to 00:25:18.050 --> 00:25:18.060 align:start position:0% use so if you use scabbit TS to 00:25:18.060 --> 00:25:20.950 align:start position:0% use so if you use scabbit TS to benchmark<00:25:18.480> your<00:25:18.750> EE<00:25:19.260> if<00:25:20.160> you<00:25:20.370> happen<00:25:20.670> to 00:25:20.950 --> 00:25:20.960 align:start position:0% benchmark your EE if you happen to 00:25:20.960 --> 00:25:23.570 align:start position:0% benchmark your EE if you happen to prototyping<00:25:21.960> some<00:25:22.260> ease<00:25:22.380> so<00:25:23.040> the<00:25:23.160> numbers<00:25:23.460> you 00:25:23.570 --> 00:25:23.580 align:start position:0% prototyping some ease so the numbers you 00:25:23.580 --> 00:25:26.270 align:start position:0% prototyping some ease so the numbers you get<00:25:23.760> there<00:25:24.090> is<00:25:24.500> it's<00:25:25.500> probably<00:25:25.680> something<00:25:26.070> you 00:25:26.270 --> 00:25:26.280 align:start position:0% get there is it's probably something you 00:25:26.280 --> 00:25:29.180 align:start position:0% get there is it's probably something you shouldn't<00:25:26.580> take<00:25:26.730> seriously<00:25:27.680> you<00:25:28.680> have<00:25:28.890> to<00:25:28.920> use 00:25:29.180 --> 00:25:29.190 align:start position:0% shouldn't take seriously you have to use 00:25:29.190 --> 00:25:31.310 align:start position:0% shouldn't take seriously you have to use interpreters<00:25:29.520> to<00:25:29.970> to<00:25:30.330> get<00:25:30.510> the<00:25:30.750> actual 00:25:31.310 --> 00:25:31.320 align:start position:0% interpreters to to get the actual 00:25:31.320 --> 00:25:34.550 align:start position:0% interpreters to to get the actual numbers<00:25:32.330> schedules<00:25:33.330> can<00:25:33.480> be<00:25:33.510> found<00:25:33.780> there<00:25:33.990> one 00:25:34.550 --> 00:25:34.560 align:start position:0% numbers schedules can be found there one 00:25:34.560 --> 00:25:37.610 align:start position:0% numbers schedules can be found there one other<00:25:34.890> interesting<00:25:35.250> point<00:25:35.700> is<00:25:36.060> that<00:25:36.330> with<00:25:37.170> the 00:25:37.610 --> 00:25:37.620 align:start position:0% other interesting point is that with the 00:25:37.620 --> 00:25:41.030 align:start position:0% other interesting point is that with the rice<00:25:37.800> rust<00:25:38.310> version<00:25:39.380> scant<00:25:40.380> itself<00:25:40.770> is<00:25:40.920> the 00:25:41.030 --> 00:25:41.040 align:start position:0% rice rust version scant itself is the 00:25:41.040 --> 00:25:43.370 align:start position:0% rice rust version scant itself is the thing<00:25:41.220> you<00:25:41.310> can<00:25:41.520> execute<00:25:41.940> EES<00:25:42.540> but<00:25:42.900> there's 00:25:43.370 --> 00:25:43.380 align:start position:0% thing you can execute EES but there's 00:25:43.380 --> 00:25:47.180 align:start position:0% thing you can execute EES but there's also<00:25:43.620> a<00:25:44.190> library<00:25:45.060> to<00:25:45.300> write<00:25:45.480> e's<00:25:45.960> in<00:25:46.230> rust<00:25:46.560> and 00:25:47.180 --> 00:25:47.190 align:start position:0% also a library to write e's in rust and 00:25:47.190 --> 00:25:48.740 align:start position:0% also a library to write e's in rust and you<00:25:47.280> can<00:25:47.430> compile<00:25:47.760> the<00:25:47.880> transcript<00:25:48.300> to<00:25:48.390> aasman 00:25:48.740 --> 00:25:48.750 align:start position:0% you can compile the transcript to aasman 00:25:48.750 --> 00:25:51.470 align:start position:0% you can compile the transcript to aasman and<00:25:49.710> then<00:25:49.890> the<00:25:50.010> typescript<00:25:50.400> there's<00:25:51.120> a<00:25:51.210> second 00:25:51.470 --> 00:25:51.480 align:start position:0% and then the typescript there's a second 00:25:51.480 --> 00:25:54.170 align:start position:0% and then the typescript there's a second language<00:25:51.630> called<00:25:52.050> assembly<00:25:52.350> script<00:25:53.180> which 00:25:54.170 --> 00:25:54.180 align:start position:0% language called assembly script which 00:25:54.180 --> 00:25:55.880 align:start position:0% language called assembly script which looks<00:25:54.480> like<00:25:54.660> time<00:25:54.900> strip<00:25:55.230> but<00:25:55.410> complies<00:25:55.860> to 00:25:55.880 --> 00:25:55.890 align:start position:0% looks like time strip but complies to 00:25:55.890 --> 00:25:59.420 align:start position:0% looks like time strip but complies to wasn't<00:25:56.760> so<00:25:57.690> in<00:25:58.050> the<00:25:58.170> scalp<00:25:58.410> TS<00:25:58.740> repo<00:25:59.070> we<00:25:59.250> have<00:25:59.400> a 00:25:59.420 --> 00:25:59.430 align:start position:0% wasn't so in the scalp TS repo we have a 00:25:59.430 --> 00:26:01.660 align:start position:0% wasn't so in the scalp TS repo we have a hello<00:25:59.670> word<00:25:59.970> greater<00:26:00.540> than<00:26:00.750> assemblers<00:26:01.170> will 00:26:01.660 --> 00:26:01.670 align:start position:0% hello word greater than assemblers will 00:26:01.670 --> 00:26:03.710 align:start position:0% hello word greater than assemblers will just<00:26:02.670> highlight<00:26:02.850> exists<00:26:03.300> that<00:26:03.480> you<00:26:03.600> can 00:26:03.710 --> 00:26:03.720 align:start position:0% just highlight exists that you can 00:26:03.720 --> 00:26:05.830 align:start position:0% just highlight exists that you can actually<00:26:03.840> write<00:26:04.230> contracts<00:26:04.920> for<00:26:05.130> right<00:26:05.400> ease 00:26:05.830 --> 00:26:05.840 align:start position:0% actually write contracts for right ease 00:26:05.840 --> 00:26:08.630 align:start position:0% actually write contracts for right ease cargo<00:26:06.840> so<00:26:07.170> right<00:26:07.530> he<00:26:07.740> is<00:26:07.980> in<00:26:08.220> different 00:26:08.630 --> 00:26:08.640 align:start position:0% cargo so right he is in different 00:26:08.640 --> 00:26:10.520 align:start position:0% cargo so right he is in different languages 00:26:10.520 --> 00:26:10.530 align:start position:0% languages 00:26:10.530 --> 00:26:12.830 align:start position:0% languages and<00:26:10.620> there's<00:26:11.340> another<00:26:11.580> staff<00:26:11.880> as<00:26:12.060> well<00:26:12.240> but 00:26:12.830 --> 00:26:12.840 align:start position:0% and there's another staff as well but 00:26:12.840 --> 00:26:15.350 align:start position:0% and there's another staff as well but Scott<00:26:13.140> one<00:26:13.410> which<00:26:13.620> is<00:26:13.770> between<00:26:13.950> C++<00:26:14.670> and 00:26:15.350 --> 00:26:15.360 align:start position:0% Scott one which is between C++ and 00:26:15.360 --> 00:26:18.470 align:start position:0% Scott one which is between C++ and that's<00:26:15.540> gonna<00:26:15.720> use<00:26:16.220> webbot<00:26:17.220> the<00:26:18.030> optimized 00:26:18.470 --> 00:26:18.480 align:start position:0% that's gonna use webbot the optimized 00:26:18.480 --> 00:26:21.560 align:start position:0% that's gonna use webbot the optimized interpreter<00:26:19.080> behave<00:26:20.040> so<00:26:20.520> this<00:26:20.790> is<00:26:21.060> the<00:26:21.330> the 00:26:21.560 --> 00:26:21.570 align:start position:0% interpreter behave so this is the the 00:26:21.570 --> 00:26:23.840 align:start position:0% interpreter behave so this is the the scheduler<00:26:22.200> ssin<00:26:22.470> eventually<00:26:23.340> you<00:26:23.490> want<00:26:23.670> to 00:26:23.840 --> 00:26:23.850 align:start position:0% scheduler ssin eventually you want to 00:26:23.850 --> 00:26:25.550 align:start position:0% scheduler ssin eventually you want to use<00:26:24.000> to<00:26:24.210> get<00:26:24.300> the<00:26:24.450> final<00:26:24.840> numbers<00:26:25.110> which<00:26:25.380> would 00:26:25.550 --> 00:26:25.560 align:start position:0% use to get the final numbers which would 00:26:25.560 --> 00:26:29.020 align:start position:0% use to get the final numbers which would reflect<00:26:25.740> what's<00:26:26.490> going<00:26:26.790> on<00:26:26.940> on<00:26:27.360> the<00:26:27.510> network 00:26:29.020 --> 00:26:29.030 align:start position:0% reflect what's going on on the network 00:26:29.030 --> 00:26:33.110 align:start position:0% reflect what's going on on the network okay<00:26:30.030> so<00:26:30.120> what<00:26:30.360> are<00:26:30.390> easy<00:26:31.010> quick<00:26:32.010> recap<00:26:32.430> they 00:26:33.110 --> 00:26:33.120 align:start position:0% okay so what are easy quick recap they 00:26:33.120 --> 00:26:35.290 align:start position:0% okay so what are easy quick recap they are<00:26:33.210> basically<00:26:33.480> the<00:26:33.600> contracts<00:26:34.200> in<00:26:34.290> the<00:26:34.320> chart 00:26:35.290 --> 00:26:35.300 align:start position:0% are basically the contracts in the chart 00:26:35.300 --> 00:26:38.000 align:start position:0% are basically the contracts in the chart and<00:26:36.300> they<00:26:36.450> only<00:26:36.600> have<00:26:36.840> a<00:26:36.870> limited<00:26:36.930> access<00:26:37.380> they 00:26:38.000 --> 00:26:38.010 align:start position:0% and they only have a limited access they 00:26:38.010 --> 00:26:40.190 align:start position:0% and they only have a limited access they think<00:26:38.280> are<00:26:38.370> pure<00:26:38.700> functions<00:26:39.270> that<00:26:39.420> all<00:26:39.660> they 00:26:40.190 --> 00:26:40.200 align:start position:0% think are pure functions that all they 00:26:40.200 --> 00:26:43.550 align:start position:0% think are pure functions that all they do<00:26:40.380> they<00:26:41.010> get<00:26:41.220> on<00:26:42.150> the<00:26:42.360> input<00:26:42.570> side<00:26:42.780> they<00:26:43.110> get 00:26:43.550 --> 00:26:43.560 align:start position:0% do they get on the input side they get 00:26:43.560 --> 00:26:46.310 align:start position:0% do they get on the input side they get this<00:26:43.770> data<00:26:44.010> log<00:26:44.310> which<00:26:44.580> is<00:26:44.900> which<00:26:45.900> contains 00:26:46.310 --> 00:26:46.320 align:start position:0% this data log which is which contains 00:26:46.320 --> 00:26:50.360 align:start position:0% this data log which is which contains the<00:26:46.470> proof<00:26:46.910> of<00:26:48.140> the<00:26:49.140> previous<00:26:49.440> state<00:26:49.650> so<00:26:50.310> you 00:26:50.360 --> 00:26:50.370 align:start position:0% the proof of the previous state so you 00:26:50.370 --> 00:26:52.310 align:start position:0% the proof of the previous state so you take<00:26:50.670> that<00:26:50.850> that<00:26:51.210> proof<00:26:51.480> and<00:26:51.690> you<00:26:51.780> construct 00:26:52.310 --> 00:26:52.320 align:start position:0% take that that proof and you construct 00:26:52.320 --> 00:26:54.140 align:start position:0% take that that proof and you construct the<00:26:52.950> previous<00:26:53.220> day<00:26:53.370> to<00:26:53.430> end<00:26:53.670> up<00:26:53.790> at<00:26:53.910> the<00:26:53.940> same 00:26:54.140 --> 00:26:54.150 align:start position:0% the previous day to end up at the same 00:26:54.150 --> 00:26:56.750 align:start position:0% the previous day to end up at the same state<00:26:54.450> road<00:26:54.690> and<00:26:55.340> that's<00:26:56.340> the<00:26:56.550> other<00:26:56.640> thing 00:26:56.750 --> 00:26:56.760 align:start position:0% state road and that's the other thing 00:26:56.760 --> 00:26:58.460 align:start position:0% state road and that's the other thing you<00:26:56.970> get<00:26:57.210> as<00:26:57.330> an<00:26:57.450> input<00:26:57.690> text<00:26:58.020> your<00:26:58.260> state 00:26:58.460 --> 00:26:58.470 align:start position:0% you get as an input text your state 00:26:58.470 --> 00:27:03.080 align:start position:0% you get as an input text your state route<00:26:58.680> which<00:26:58.890> is<00:26:58.920> stored<00:26:59.520> on<00:26:59.820> the<00:27:00.360> shark<00:27:02.090> well 00:27:03.080 --> 00:27:03.090 align:start position:0% route which is stored on the shark well 00:27:03.090 --> 00:27:05.000 align:start position:0% route which is stored on the shark well as<00:27:03.270> a<00:27:03.300> proposal<00:27:03.690> to<00:27:03.900> anyway<00:27:04.200> because<00:27:04.380> that 00:27:05.000 --> 00:27:05.010 align:start position:0% as a proposal to anyway because that 00:27:05.010 --> 00:27:07.820 align:start position:0% as a proposal to anyway because that might<00:27:05.190> change<00:27:05.840> but<00:27:06.840> you<00:27:07.020> get<00:27:07.200> the<00:27:07.350> state<00:27:07.590> route 00:27:07.820 --> 00:27:07.830 align:start position:0% might change but you get the state route 00:27:07.830 --> 00:27:10.280 align:start position:0% might change but you get the state route from<00:27:08.010> the<00:27:08.160> chart<00:27:08.430> and<00:27:08.670> then<00:27:09.090> you<00:27:09.270> supply<00:27:09.660> all 00:27:10.280 --> 00:27:10.290 align:start position:0% from the chart and then you supply all 00:27:10.290 --> 00:27:13.400 align:start position:0% from the chart and then you supply all the<00:27:10.620> proofs<00:27:10.890> to<00:27:11.660> recalculate<00:27:12.660> the<00:27:12.990> same<00:27:13.170> state 00:27:13.400 --> 00:27:13.410 align:start position:0% the proofs to recalculate the same state 00:27:13.410 --> 00:27:14.780 align:start position:0% the proofs to recalculate the same state route<00:27:13.620> then<00:27:13.770> you<00:27:13.890> have<00:27:14.070> to<00:27:14.190> validate<00:27:14.340> that<00:27:14.640> it 00:27:14.780 --> 00:27:14.790 align:start position:0% route then you have to validate that it 00:27:14.790 --> 00:27:16.760 align:start position:0% route then you have to validate that it matches<00:27:15.000> and<00:27:15.750> that<00:27:15.870> means<00:27:16.080> you<00:27:16.350> you<00:27:16.560> have<00:27:16.740> a 00:27:16.760 --> 00:27:16.770 align:start position:0% matches and that means you you have a 00:27:16.770 --> 00:27:18.470 align:start position:0% matches and that means you you have a good<00:27:16.920> starting<00:27:17.250> point<00:27:17.430> and<00:27:17.700> then<00:27:18.150> you<00:27:18.300> also 00:27:18.470 --> 00:27:18.480 align:start position:0% good starting point and then you also 00:27:18.480 --> 00:27:20.870 align:start position:0% good starting point and then you also receive<00:27:19.050> in<00:27:19.440> the<00:27:19.560> same<00:27:19.740> data<00:27:19.950> blob<00:27:20.190> all<00:27:20.580> the 00:27:20.870 --> 00:27:20.880 align:start position:0% receive in the same data blob all the 00:27:20.880 --> 00:27:22.310 align:start position:0% receive in the same data blob all the transactions<00:27:21.450> all<00:27:21.660> the<00:27:21.720> things<00:27:21.930> you<00:27:22.140> want<00:27:22.290> to 00:27:22.310 --> 00:27:22.320 align:start position:0% transactions all the things you want to 00:27:22.320 --> 00:27:24.560 align:start position:0% transactions all the things you want to do<00:27:22.500> so<00:27:23.220> you<00:27:23.280> apply<00:27:23.610> those<00:27:23.820> changes<00:27:24.330> you 00:27:24.560 --> 00:27:24.570 align:start position:0% do so you apply those changes you 00:27:24.570 --> 00:27:26.840 align:start position:0% do so you apply those changes you calculate<00:27:25.530> the<00:27:25.770> the<00:27:26.010> final<00:27:26.460> stage<00:27:26.670> through 00:27:26.840 --> 00:27:26.850 align:start position:0% calculate the the final stage through 00:27:26.850 --> 00:27:28.910 align:start position:0% calculate the the final stage through the<00:27:27.000> positive<00:27:27.210> hood<00:27:27.720> and<00:27:27.960> that's<00:27:28.620> what<00:27:28.800> you 00:27:28.910 --> 00:27:28.920 align:start position:0% the positive hood and that's what you 00:27:28.920 --> 00:27:30.380 align:start position:0% the positive hood and that's what you work<00:27:29.040> with<00:27:29.250> and<00:27:29.400> that's<00:27:29.460> what's<00:27:29.730> stored<00:27:29.940> so 00:27:30.380 --> 00:27:30.390 align:start position:0% work with and that's what's stored so 00:27:30.390 --> 00:27:34.850 align:start position:0% work with and that's what's stored so that<00:27:30.570> that's<00:27:31.050> all<00:27:31.320> at<00:27:31.590> ease<00:27:31.920> can<00:27:32.250> do<00:27:33.710> so<00:27:34.710> this 00:27:34.850 --> 00:27:34.860 align:start position:0% that that's all at ease can do so this 00:27:34.860 --> 00:27:38.070 align:start position:0% that that's all at ease can do so this is<00:27:34.920> the<00:27:35.130> API 00:27:38.070 --> 00:27:38.080 align:start position:0% 00:27:38.080 --> 00:27:41.370 align:start position:0% the<00:27:39.010> APR<00:27:39.340> in<00:27:39.610> Ind<00:27:39.970> s<00:27:40.180> wasn't<00:27:40.720> close<00:27:41.170> function 00:27:41.370 --> 00:27:41.380 align:start position:0% the APR in Ind s wasn't close function 00:27:41.380 --> 00:27:44.730 align:start position:0% the APR in Ind s wasn't close function so<00:27:41.920> the<00:27:42.640> just<00:27:43.090> to<00:27:43.180> explain<00:27:43.450> it<00:27:43.600> better<00:27:43.780> so<00:27:44.620> this 00:27:44.730 --> 00:27:44.740 align:start position:0% so the just to explain it better so this 00:27:44.740 --> 00:27:46.710 align:start position:0% so the just to explain it better so this e<00:27:44.920> to<00:27:45.130> stuff<00:27:45.430> here<00:27:45.640> is<00:27:45.730> a<00:27:45.760> namespace<00:27:46.150> and<00:27:46.570> this 00:27:46.710 --> 00:27:46.720 align:start position:0% e to stuff here is a namespace and this 00:27:46.720 --> 00:27:48.120 align:start position:0% e to stuff here is a namespace and this is<00:27:46.840> a<00:27:46.900> function<00:27:47.260> name<00:27:47.440> and<00:27:47.470> these<00:27:47.830> are<00:27:47.980> the 00:27:48.120 --> 00:27:48.130 align:start position:0% is a function name and these are the 00:27:48.130 --> 00:27:51.750 align:start position:0% is a function name and these are the parameters<00:27:49.200> so<00:27:50.200> what<00:27:50.650> I<00:27:50.680> just<00:27:51.130> explained<00:27:51.580> you 00:27:51.750 --> 00:27:51.760 align:start position:0% parameters so what I just explained you 00:27:51.760 --> 00:27:53.700 align:start position:0% parameters so what I just explained you have<00:27:52.000> a<00:27:52.030> way<00:27:52.360> to<00:27:52.390> get<00:27:52.660> the<00:27:52.780> data<00:27:52.990> you<00:27:53.500> have<00:27:53.620> a 00:27:53.700 --> 00:27:53.710 align:start position:0% have a way to get the data you have a 00:27:53.710 --> 00:27:56.220 align:start position:0% have a way to get the data you have a way<00:27:53.830> to<00:27:53.890> get<00:27:54.130> the<00:27:54.310> P<00:27:54.610> and<00:27:55.030> up<00:27:55.510> and<00:27:55.750> set<00:27:56.110> the 00:27:56.220 --> 00:27:56.230 align:start position:0% way to get the P and up and set the 00:27:56.230 --> 00:27:58.560 align:start position:0% way to get the P and up and set the positive<00:27:56.680> trip<00:27:56.830> the<00:27:57.730> deposit<00:27:58.180> stuff<00:27:58.420> I 00:27:58.560 --> 00:27:58.570 align:start position:0% positive trip the deposit stuff I 00:27:58.570 --> 00:28:00.510 align:start position:0% positive trip the deposit stuff I wouldn't<00:27:58.870> be<00:27:59.050> paid<00:27:59.710> too<00:27:59.800> much<00:27:59.830> attention<00:27:59.980> to 00:28:00.510 --> 00:28:00.520 align:start position:0% wouldn't be paid too much attention to 00:28:00.520 --> 00:28:02.670 align:start position:0% wouldn't be paid too much attention to right<00:28:00.670> now<00:28:00.730> because<00:28:01.180> that<00:28:02.140> might<00:28:02.440> change 00:28:02.670 --> 00:28:02.680 align:start position:0% right now because that might change 00:28:02.680 --> 00:28:06.180 align:start position:0% right now because that might change whatever<00:28:04.230> but<00:28:05.230> we<00:28:05.320> also<00:28:05.500> haven't<00:28:05.770> abandoned 00:28:06.180 --> 00:28:06.190 align:start position:0% whatever but we also haven't abandoned 00:28:06.190 --> 00:28:08.940 align:start position:0% whatever but we also haven't abandoned API<00:28:06.460> because<00:28:07.020> why<00:28:08.020> don't<00:28:08.260> you<00:28:08.380> want<00:28:08.560> to<00:28:08.590> debug 00:28:08.940 --> 00:28:08.950 align:start position:0% API because why don't you want to debug 00:28:08.950 --> 00:28:11.070 align:start position:0% API because why don't you want to debug it<00:28:09.220> yeah<00:28:09.460> it's<00:28:10.300> an<00:28:10.420> easy<00:28:10.570> way<00:28:10.720> to<00:28:10.930> get 00:28:11.070 --> 00:28:11.080 align:start position:0% it yeah it's an easy way to get 00:28:11.080 --> 00:28:13.350 align:start position:0% it yeah it's an easy way to get something<00:28:11.440> is<00:28:11.650> end<00:28:11.920> of<00:28:12.160> the<00:28:12.760> e<00:28:12.790> during 00:28:13.350 --> 00:28:13.360 align:start position:0% something is end of the e during 00:28:13.360 --> 00:28:15.900 align:start position:0% something is end of the e during execution<00:28:13.720> so<00:28:14.380> you<00:28:14.440> can<00:28:14.590> print<00:28:14.770> numbers<00:28:15.160> you 00:28:15.900 --> 00:28:15.910 align:start position:0% execution so you can print numbers you 00:28:15.910 --> 00:28:18.330 align:start position:0% execution so you can print numbers you can<00:28:16.060> pin<00:28:16.270> memory<00:28:16.650> you<00:28:17.650> can<00:28:17.770> feed<00:28:17.920> number<00:28:18.130> in<00:28:18.220> a 00:28:18.330 --> 00:28:18.340 align:start position:0% can pin memory you can feed number in a 00:28:18.340 --> 00:28:20.640 align:start position:0% can pin memory you can feed number in a in<00:28:18.550> a<00:28:18.610> hexadecimal<00:28:19.240> form<00:28:19.480> but<00:28:20.230> this<00:28:20.410> one 00:28:20.640 --> 00:28:20.650 align:start position:0% in a hexadecimal form but this one 00:28:20.650 --> 00:28:23.160 align:start position:0% in a hexadecimal form but this one prints<00:28:21.340> man<00:28:21.490> only<00:28:21.850> prints<00:28:22.210> memory<00:28:22.540> only<00:28:22.960> the 00:28:23.160 --> 00:28:23.170 align:start position:0% prints man only prints memory only the 00:28:23.170 --> 00:28:25.560 align:start position:0% prints man only prints memory only the printable<00:28:23.500> characters<00:28:24.130> so<00:28:24.640> essentially<00:28:25.240> it's 00:28:25.560 --> 00:28:25.570 align:start position:0% printable characters so essentially it's 00:28:25.570 --> 00:28:29.970 align:start position:0% printable characters so essentially it's usable<00:28:26.110> for<00:28:26.710> printing<00:28:27.070> strings<00:28:28.530> and<00:28:29.530> giving 00:28:29.970 --> 00:28:29.980 align:start position:0% usable for printing strings and giving 00:28:29.980 --> 00:28:33.960 align:start position:0% usable for printing strings and giving them<00:28:30.130> a<00:28:30.250> big<00:28:30.610> nom<00:28:30.790> API<00:28:32.100> so<00:28:33.100> that's<00:28:33.340> that<00:28:33.790> was 00:28:33.960 --> 00:28:33.970 align:start position:0% them a big nom API so that's that was 00:28:33.970 --> 00:28:35.100 align:start position:0% them a big nom API so that's that was mentioned<00:28:34.360> yesterday<00:28:34.390> during<00:28:34.840> the 00:28:35.100 --> 00:28:35.110 align:start position:0% mentioned yesterday during the 00:28:35.110 --> 00:28:38.520 align:start position:0% mentioned yesterday during the benchmarking<00:28:35.770> and<00:28:36.390> it's<00:28:37.390> not<00:28:37.540> fixed<00:28:37.900> at<00:28:38.320> all 00:28:38.520 --> 00:28:38.530 align:start position:0% benchmarking and it's not fixed at all 00:28:38.530 --> 00:28:41.520 align:start position:0% benchmarking and it's not fixed at all but<00:28:39.190> that<00:28:39.340> is<00:28:39.460> the<00:28:39.580> discussion<00:28:39.910> URL<00:28:40.530> to 00:28:41.520 --> 00:28:41.530 align:start position:0% but that is the discussion URL to 00:28:41.530 --> 00:28:43.080 align:start position:0% but that is the discussion URL to discuss<00:28:41.890> what<00:28:42.070> the<00:28:42.160> big<00:28:42.310> media<00:28:42.520> should<00:28:42.940> look 00:28:43.080 --> 00:28:43.090 align:start position:0% discuss what the big media should look 00:28:43.090 --> 00:28:45.120 align:start position:0% discuss what the big media should look like<00:28:43.120> this<00:28:44.110> is<00:28:44.290> one<00:28:44.440> of<00:28:44.470> the<00:28:44.710> recurrent 00:28:45.120 --> 00:28:45.130 align:start position:0% like this is one of the recurrent 00:28:45.130 --> 00:28:47.670 align:start position:0% like this is one of the recurrent proposals<00:28:45.610> it<00:28:45.820> matches<00:28:46.390> what<00:28:46.630> is<00:28:46.690> implemented 00:28:47.670 --> 00:28:47.680 align:start position:0% proposals it matches what is implemented 00:28:47.680 --> 00:28:49.740 align:start position:0% proposals it matches what is implemented in<00:28:47.890> the<00:28:48.370> typescript<00:28:48.730> in<00:28:49.060> the<00:28:49.150> past<00:28:49.330> version 00:28:49.740 --> 00:28:49.750 align:start position:0% in the typescript in the past version 00:28:49.750 --> 00:28:55.800 align:start position:0% in the typescript in the past version but<00:28:50.560> it<00:28:51.010> may<00:28:51.280> change<00:28:51.940> in<00:28:52.150> the<00:28:52.180> future<00:28:54.810> so 00:28:55.800 --> 00:28:55.810 align:start position:0% but it may change in the future so 00:28:55.810 --> 00:28:58.910 align:start position:0% but it may change in the future so regarding<00:28:56.200> the<00:28:56.230> ease<00:28:56.470> we<00:28:56.890> have<00:28:56.920> in<00:28:57.840> in 00:28:58.910 --> 00:28:58.920 align:start position:0% regarding the ease we have in in 00:28:58.920 --> 00:29:01.110 align:start position:0% regarding the ease we have in in scalloped<00:28:59.920> itself<00:29:00.400> we<00:29:00.550> have<00:29:00.670> two<00:29:00.850> examples 00:29:01.110 --> 00:29:01.120 align:start position:0% scalloped itself we have two examples 00:29:01.120 --> 00:29:04.230 align:start position:0% scalloped itself we have two examples the<00:29:01.450> hell<00:29:01.570> over<00:29:01.660> to<00:29:01.870> the<00:29:01.960> bizarre<00:29:02.290> I<00:29:03.210> can<00:29:04.210> I 00:29:04.230 --> 00:29:04.240 align:start position:0% the hell over to the bizarre I can I 00:29:04.240 --> 00:29:07.050 align:start position:0% the hell over to the bizarre I can I have<00:29:04.360> some<00:29:04.540> screenshots<00:29:04.870> afterwards<00:29:05.880> and<00:29:06.880> we 00:29:07.050 --> 00:29:07.060 align:start position:0% have some screenshots afterwards and we 00:29:07.060 --> 00:29:09.030 align:start position:0% have some screenshots afterwards and we have<00:29:07.300> a<00:29:07.330> bunch<00:29:07.600> of<00:29:07.750> other<00:29:08.020> examples<00:29:08.470> but<00:29:08.890> they 00:29:09.030 --> 00:29:09.040 align:start position:0% have a bunch of other examples but they 00:29:09.040 --> 00:29:11.790 align:start position:0% have a bunch of other examples but they love<00:29:09.190> necessarily<00:29:09.760> in<00:29:09.820> the<00:29:09.910> same<00:29:09.940> place<00:29:10.800> and 00:29:11.790 --> 00:29:11.800 align:start position:0% love necessarily in the same place and 00:29:11.800 --> 00:29:13.650 align:start position:0% love necessarily in the same place and these<00:29:12.040> all<00:29:12.460> these<00:29:12.850> example<00:29:13.330> is<00:29:13.420> going<00:29:13.510> to<00:29:13.600> be 00:29:13.650 --> 00:29:13.660 align:start position:0% these all these example is going to be 00:29:13.660 --> 00:29:15.270 align:start position:0% these all these example is going to be all<00:29:13.900> these<00:29:14.080> extinction<00:29:14.800> round<00:29:14.950> it's<00:29:15.070> going<00:29:15.220> to 00:29:15.270 --> 00:29:15.280 align:start position:0% all these extinction round it's going to 00:29:15.280 --> 00:29:17.670 align:start position:0% all these extinction round it's going to be<00:29:15.340> covered<00:29:15.640> today<00:29:16.140> so<00:29:17.140> here<00:29:17.260> is<00:29:17.350> an<00:29:17.440> example 00:29:17.670 --> 00:29:17.680 align:start position:0% be covered today so here is an example 00:29:17.680 --> 00:29:19.050 align:start position:0% be covered today so here is an example in<00:29:17.860> rust<00:29:18.130> if<00:29:18.340> anybody<00:29:18.640> is<00:29:18.730> familiar<00:29:18.790> with 00:29:19.050 --> 00:29:19.060 align:start position:0% in rust if anybody is familiar with 00:29:19.060 --> 00:29:23.810 align:start position:0% in rust if anybody is familiar with truss<00:29:20.610> as<00:29:21.610> I<00:29:21.760> said<00:29:21.970> you'll<00:29:22.210> note<00:29:22.680> here 00:29:23.810 --> 00:29:23.820 align:start position:0% truss as I said you'll note here 00:29:23.820 --> 00:29:26.700 align:start position:0% truss as I said you'll note here basically<00:29:24.900> what<00:29:25.900> this<00:29:25.990> hello<00:29:26.170> world<00:29:26.350> is<00:29:26.470> doing 00:29:26.700 --> 00:29:26.710 align:start position:0% basically what this hello world is doing 00:29:26.710 --> 00:29:28.950 align:start position:0% basically what this hello world is doing you<00:29:27.280> expect<00:29:27.640> that<00:29:27.760> there<00:29:27.910> is<00:29:27.970> no<00:29:28.240> change<00:29:28.600> no 00:29:28.950 --> 00:29:28.960 align:start position:0% you expect that there is no change no 00:29:28.960 --> 00:29:31.890 align:start position:0% you expect that there is no change no inputs<00:29:29.410> so<00:29:30.010> obviously<00:29:30.550> the<00:29:31.240> piano<00:29:31.540> phosphate 00:29:31.890 --> 00:29:31.900 align:start position:0% inputs so obviously the piano phosphate 00:29:31.900 --> 00:29:34.560 align:start position:0% inputs so obviously the piano phosphate with<00:29:32.080> good<00:29:32.320> French<00:29:33.120> but<00:29:34.120> it's<00:29:34.270> just<00:29:34.420> an 00:29:34.560 --> 00:29:34.570 align:start position:0% with good French but it's just an 00:29:34.570 --> 00:29:36.530 align:start position:0% with good French but it's just an example<00:29:34.690> to<00:29:34.930> see<00:29:35.050> how<00:29:35.590> to<00:29:35.650> use<00:29:35.800> the<00:29:36.010> API<00:29:36.100> so 00:29:36.530 --> 00:29:36.540 align:start position:0% example to see how to use the API so 00:29:36.540 --> 00:29:40.620 align:start position:0% example to see how to use the API so let's<00:29:37.540> the<00:29:37.630> same<00:29:37.780> assembly<00:29:38.080> script<00:29:38.500> and<00:29:39.630> I 00:29:40.620 --> 00:29:40.630 align:start position:0% let's the same assembly script and I 00:29:40.630 --> 00:29:42.900 align:start position:0% let's the same assembly script and I read<00:29:40.750> earlier<00:29:40.780> in<00:29:41.200> which<00:29:41.350> both<00:29:41.530> lists<00:29:41.910> which 00:29:42.900 --> 00:29:42.910 align:start position:0% read earlier in which both lists which 00:29:42.910 --> 00:29:46.009 align:start position:0% read earlier in which both lists which also<00:29:43.120> comprise<00:29:43.540> to<00:29:43.660> us 00:29:46.009 --> 00:29:46.019 align:start position:0% 00:29:46.019 --> 00:29:50.070 align:start position:0% this<00:29:47.019> is<00:29:47.169> a<00:29:47.200> longer<00:29:47.409> example<00:29:48.570> this<00:29:49.570> instead 00:29:50.070 --> 00:29:50.080 align:start position:0% this is a longer example this instead 00:29:50.080 --> 00:29:52.740 align:start position:0% this is a longer example this instead that<00:29:50.320> the<00:29:50.529> baseline<00:29:50.769> to<00:29:51.429> do<00:29:52.120> all<00:29:52.299> of<00:29:52.330> the<00:29:52.600> work 00:29:52.740 --> 00:29:52.750 align:start position:0% that the baseline to do all of the work 00:29:52.750 --> 00:29:55.919 align:start position:0% that the baseline to do all of the work we<00:29:53.110> have<00:29:53.559> done<00:29:53.590> because<00:29:53.950> basically<00:29:54.929> this 00:29:55.919 --> 00:29:55.929 align:start position:0% we have done because basically this 00:29:55.929 --> 00:29:58.470 align:start position:0% we have done because basically this doesn't<00:29:56.440> do<00:29:56.559> any<00:29:56.740> kind<00:29:57.039> of<00:29:57.159> impression<00:29:58.090> or<00:29:58.210> any 00:29:58.470 --> 00:29:58.480 align:start position:0% doesn't do any kind of impression or any 00:29:58.480 --> 00:30:01.230 align:start position:0% doesn't do any kind of impression or any sparse<00:29:59.139> market<00:29:59.529> fees<00:29:59.710> and<00:30:00.070> just<00:30:00.820> takes<00:30:01.000> in<00:30:01.149> the 00:30:01.230 --> 00:30:01.240 align:start position:0% sparse market fees and just takes in the 00:30:01.240 --> 00:30:03.480 align:start position:0% sparse market fees and just takes in the nail<00:30:01.419> of<00:30:01.570> fascism<00:30:01.960> and<00:30:02.289> that's<00:30:02.769> it<00:30:02.980> so 00:30:03.480 --> 00:30:03.490 align:start position:0% nail of fascism and that's it so 00:30:03.490 --> 00:30:06.990 align:start position:0% nail of fascism and that's it so basically<00:30:05.070> this<00:30:06.070> is<00:30:06.250> the<00:30:06.340> state<00:30:06.580> which<00:30:06.820> is<00:30:06.970> a 00:30:06.990 --> 00:30:07.000 align:start position:0% basically this is the state which is a 00:30:07.000 --> 00:30:09.450 align:start position:0% basically this is the state which is a list<00:30:07.539> of<00:30:07.690> messages<00:30:07.899> message<00:30:08.740> contains<00:30:09.159> self 00:30:09.450 --> 00:30:09.460 align:start position:0% list of messages message contains self 00:30:09.460 --> 00:30:11.549 align:start position:0% list of messages message contains self just<00:30:09.909> the<00:30:10.000> message<00:30:10.240> of<00:30:10.389> The<00:30:10.480> Times<00:30:10.659> them<00:30:10.929> at 00:30:11.549 --> 00:30:11.559 align:start position:0% just the message of The Times them at 00:30:11.559 --> 00:30:13.980 align:start position:0% just the message of The Times them at the<00:30:11.710> input<00:30:11.980> blog<00:30:12.190> has<00:30:12.429> to<00:30:12.639> supply<00:30:12.990> every 00:30:13.980 --> 00:30:13.990 align:start position:0% the input blog has to supply every 00:30:13.990 --> 00:30:17.159 align:start position:0% the input blog has to supply every single<00:30:14.320> time<00:30:14.700> DD<00:30:15.700> state<00:30:15.970> because<00:30:16.870> what<00:30:17.049> you 00:30:17.159 --> 00:30:17.169 align:start position:0% single time DD state because what you 00:30:17.169 --> 00:30:19.950 align:start position:0% single time DD state because what you store<00:30:17.549> is<00:30:18.549> the<00:30:18.789> hash<00:30:19.029> of<00:30:19.389> all<00:30:19.600> the<00:30:19.659> messages 00:30:19.950 --> 00:30:19.960 align:start position:0% store is the hash of all the messages 00:30:19.960 --> 00:30:22.769 align:start position:0% store is the hash of all the messages obviously<00:30:20.710> you<00:30:20.860> need<00:30:21.309> all<00:30:21.580> of<00:30:21.789> them<00:30:22.000> at<00:30:22.659> the 00:30:22.769 --> 00:30:22.779 align:start position:0% obviously you need all of them at the 00:30:22.779 --> 00:30:25.049 align:start position:0% obviously you need all of them at the input<00:30:22.990> side<00:30:23.139> of<00:30:23.320> it<00:30:23.529> so<00:30:23.679> this<00:30:24.460> is<00:30:24.700> not<00:30:24.909> very 00:30:25.049 --> 00:30:25.059 align:start position:0% input side of it so this is not very 00:30:25.059 --> 00:30:26.909 align:start position:0% input side of it so this is not very useful<00:30:25.149> it's<00:30:25.570> useful<00:30:25.870> as<00:30:25.929> an<00:30:26.049> example<00:30:26.350> but<00:30:26.649> in 00:30:26.909 --> 00:30:26.919 align:start position:0% useful it's useful as an example but in 00:30:26.919 --> 00:30:29.700 align:start position:0% useful it's useful as an example but in order<00:30:27.159> to<00:30:27.190> descale<00:30:27.990> so<00:30:28.990> that's<00:30:29.139> why<00:30:29.320> you<00:30:29.559> have 00:30:29.700 --> 00:30:29.710 align:start position:0% order to descale so that's why you have 00:30:29.710 --> 00:30:33.509 align:start position:0% order to descale so that's why you have all<00:30:29.740> these<00:30:29.950> discussions<00:30:30.669> afterwards<00:30:32.370> and<00:30:33.370> i 00:30:33.509 --> 00:30:33.519 align:start position:0% all these discussions afterwards and i 00:30:33.519 --> 00:30:35.129 align:start position:0% all these discussions afterwards and i mentioned<00:30:33.909> that<00:30:34.029> you<00:30:34.179> can<00:30:34.299> interact<00:30:34.750> with<00:30:34.929> sky 00:30:35.129 --> 00:30:35.139 align:start position:0% mentioned that you can interact with sky 00:30:35.139 --> 00:30:37.379 align:start position:0% mentioned that you can interact with sky through<00:30:35.440> a<00:30:35.470> yellow<00:30:35.769> file<00:30:36.190> such<00:30:36.669> as<00:30:36.820> an<00:30:36.940> example 00:30:37.379 --> 00:30:37.389 align:start position:0% through a yellow file such as an example 00:30:37.389 --> 00:30:40.110 align:start position:0% through a yellow file such as an example of<00:30:37.509> the<00:30:37.690> demo<00:30:38.019> file<00:30:38.259> you<00:30:39.100> specify<00:30:39.610> what<00:30:39.820> is<00:30:39.970> the 00:30:40.110 --> 00:30:40.120 align:start position:0% of the demo file you specify what is the 00:30:40.120 --> 00:30:41.940 align:start position:0% of the demo file you specify what is the code<00:30:40.299> you<00:30:40.450> wanna<00:30:40.629> run<00:30:40.809> the<00:30:41.470> priest<00:30:41.710> a<00:30:41.889> the 00:30:41.940 --> 00:30:41.950 align:start position:0% code you wanna run the priest a the 00:30:41.950 --> 00:30:45.419 align:start position:0% code you wanna run the priest a the prostate<00:30:42.519> and<00:30:42.789> the<00:30:43.269> data<00:30:43.919> and<00:30:44.919> you<00:30:45.039> can<00:30:45.070> also 00:30:45.419 --> 00:30:45.429 align:start position:0% prostate and the data and you can also 00:30:45.429 --> 00:30:47.549 align:start position:0% prostate and the data and you can also run<00:30:45.789> multiple<00:30:46.000> scripts<00:30:46.870> in<00:30:47.049> the<00:30:47.080> same<00:30:47.289> llamo 00:30:47.549 --> 00:30:47.559 align:start position:0% run multiple scripts in the same llamo 00:30:47.559 --> 00:30:48.930 align:start position:0% run multiple scripts in the same llamo file<00:30:47.769> it<00:30:47.950> doesn't<00:30:48.220> have<00:30:48.340> to<00:30:48.490> be<00:30:48.639> a<00:30:48.669> super 00:30:48.930 --> 00:30:48.940 align:start position:0% file it doesn't have to be a super 00:30:48.940 --> 00:30:51.299 align:start position:0% file it doesn't have to be a super single<00:30:49.330> one<00:30:49.500> you<00:30:50.500> never<00:30:50.679> see<00:30:50.860> these<00:30:50.980> sample 00:30:51.299 --> 00:30:51.309 align:start position:0% single one you never see these sample 00:30:51.309 --> 00:30:53.490 align:start position:0% single one you never see these sample files<00:30:51.519> in<00:30:51.669> the<00:30:51.789> repos<00:30:52.149> for<00:30:52.570> every<00:30:53.139> single<00:30:53.320> to 00:30:53.490 --> 00:30:53.500 align:start position:0% files in the repos for every single to 00:30:53.500 --> 00:30:57.690 align:start position:0% files in the repos for every single to you<00:30:54.929> so<00:30:55.929> the<00:30:56.019> next<00:30:56.049> steps<00:30:56.500> I<00:30:56.860> haven't 00:30:57.690 --> 00:30:57.700 align:start position:0% you so the next steps I haven't 00:30:57.700 --> 00:31:00.029 align:start position:0% you so the next steps I haven't mentioned<00:30:57.820> but<00:30:58.259> the<00:30:59.259> emergent<00:30:59.620> equal<00:30:59.860> team 00:31:00.029 --> 00:31:00.039 align:start position:0% mentioned but the emergent equal team 00:31:00.039 --> 00:31:02.549 align:start position:0% mentioned but the emergent equal team and<00:31:00.429> they<00:31:00.820> have<00:31:00.909> taken<00:31:01.029> scared<00:31:01.629> to<00:31:02.409> be 00:31:02.549 --> 00:31:02.559 align:start position:0% and they have taken scared to be 00:31:02.559 --> 00:31:05.220 align:start position:0% and they have taken scared to be integrated<00:31:03.370> into<00:31:03.519> lighthouse<00:31:04.029> to<00:31:04.840> do<00:31:04.990> some 00:31:05.220 --> 00:31:05.230 align:start position:0% integrated into lighthouse to do some 00:31:05.230 --> 00:31:08.909 align:start position:0% integrated into lighthouse to do some kind<00:31:05.470> of<00:31:05.529> testing<00:31:06.399> or<00:31:06.850> simulation<00:31:07.679> and<00:31:08.679> what 00:31:08.909 --> 00:31:08.919 align:start position:0% kind of testing or simulation and what 00:31:08.919 --> 00:31:11.100 align:start position:0% kind of testing or simulation and what we<00:31:09.009> actually<00:31:09.159> are<00:31:09.549> thinking<00:31:09.879> about<00:31:09.970> to<00:31:10.330> to 00:31:11.100 --> 00:31:11.110 align:start position:0% we actually are thinking about to to 00:31:11.110 --> 00:31:12.899 align:start position:0% we actually are thinking about to to move<00:31:11.230> all<00:31:11.409> of<00:31:11.710> that<00:31:11.860> comes<00:31:12.039> back<00:31:12.100> and<00:31:12.549> just 00:31:12.899 --> 00:31:12.909 align:start position:0% move all of that comes back and just 00:31:12.909 --> 00:31:14.009 align:start position:0% move all of that comes back and just have<00:31:13.090> it<00:31:13.120> in<00:31:13.299> scared<00:31:13.570> and<00:31:13.779> have<00:31:13.929> an 00:31:14.009 --> 00:31:14.019 align:start position:0% have it in scared and have an 00:31:14.019 --> 00:31:15.840 align:start position:0% have it in scared and have an independent<00:31:14.259> tool<00:31:14.740> to<00:31:15.370> do<00:31:15.460> rapid<00:31:15.820> prototyping 00:31:15.840 --> 00:31:15.850 align:start position:0% independent tool to do rapid prototyping 00:31:15.850 --> 00:31:19.980 align:start position:0% independent tool to do rapid prototyping now<00:31:17.159> but<00:31:18.159> we<00:31:18.279> do<00:31:18.639> want<00:31:19.000> to<00:31:19.149> add<00:31:19.389> a<00:31:19.450> few<00:31:19.929> things 00:31:19.980 --> 00:31:19.990 align:start position:0% now but we do want to add a few things 00:31:19.990 --> 00:31:22.350 align:start position:0% now but we do want to add a few things there<00:31:20.440> may<00:31:20.860> be<00:31:20.889> multiple<00:31:21.100> engines<00:31:21.700> and<00:31:22.240> a 00:31:22.350 --> 00:31:22.360 align:start position:0% there may be multiple engines and a 00:31:22.360 --> 00:31:25.049 align:start position:0% there may be multiple engines and a scalpel<00:31:22.659> of<00:31:22.899> course<00:31:23.200> and<00:31:23.440> me<00:31:24.190> just<00:31:24.549> the<00:31:24.789> the 00:31:25.049 --> 00:31:25.059 align:start position:0% scalpel of course and me just the the 00:31:25.059 --> 00:31:27.360 align:start position:0% scalpel of course and me just the the developer<00:31:25.779> experience<00:31:25.899> better<00:31:26.440> have<00:31:27.159> better 00:31:27.360 --> 00:31:27.370 align:start position:0% developer experience better have better 00:31:27.370 --> 00:31:30.419 align:start position:0% developer experience better have better tools<00:31:27.549> friend<00:31:28.799> that's<00:31:29.799> what<00:31:30.070> we<00:31:30.250> are<00:31:30.279> one 00:31:30.419 --> 00:31:30.429 align:start position:0% tools friend that's what we are one 00:31:30.429 --> 00:31:35.490 align:start position:0% tools friend that's what we are one scared<00:31:31.110> you<00:31:32.110> guys<00:31:32.259> have<00:31:32.940> army<00:31:33.940> on<00:31:34.029> time<00:31:34.240> yeah 00:31:35.490 --> 00:31:35.500 align:start position:0% scared you guys have army on time yeah 00:31:35.500 --> 00:31:38.480 align:start position:0% scared you guys have army on time yeah right<00:31:35.850> so<00:31:36.850> maybe<00:31:36.970> one<00:31:37.270> one<00:31:37.480> or<00:31:37.570> two<00:31:37.690> questions 00:31:38.480 --> 00:31:38.490 align:start position:0% right so maybe one one or two questions 00:31:38.490 --> 00:31:49.110 align:start position:0% right so maybe one one or two questions okay<00:31:39.490> go<00:31:40.210> ahead<00:31:40.350> yeah<00:31:41.350> -<00:31:41.890> you<00:31:47.400> look<00:31:48.400> more<00:31:48.850> about 00:31:49.110 --> 00:31:49.120 align:start position:0% okay go ahead yeah - you look more about 00:31:49.120 --> 00:31:52.050 align:start position:0% okay go ahead yeah - you look more about the<00:31:49.360> east<00:31:50.040> crease<00:31:51.040> Ted<00:31:51.250> Cruz<00:31:51.460> and<00:31:51.670> posted 00:31:52.050 --> 00:31:52.060 align:start position:0% the east crease Ted Cruz and posted 00:31:52.060 --> 00:31:55.130 align:start position:0% the east crease Ted Cruz and posted moves<00:31:52.860> south<00:31:53.860> like<00:31:54.190> they<00:31:54.370> are<00:31:54.430> soon<00:31:54.820> to<00:31:54.850> be 00:31:55.130 --> 00:31:55.140 align:start position:0% moves south like they are soon to be 00:31:55.140 --> 00:31:58.860 align:start position:0% moves south like they are soon to be hostage<00:31:56.140> groups<00:31:56.410> but<00:31:56.950> is<00:31:57.550> it<00:31:57.700> up<00:31:57.820> to<00:31:57.850> the<00:31:58.120> EE<00:31:58.300> to 00:31:58.860 --> 00:31:58.870 align:start position:0% hostage groups but is it up to the EE to 00:31:58.870 --> 00:32:01.730 align:start position:0% hostage groups but is it up to the EE to use<00:31:58.990> those<00:31:59.530> to<00:32:00.160> buy<00:32:00.370> celebrity<00:32:01.030> wishes 00:32:01.730 --> 00:32:01.740 align:start position:0% use those to buy celebrity wishes 00:32:01.740 --> 00:32:03.750 align:start position:0% use those to buy celebrity wishes yesterday<00:32:02.740> question<00:32:03.070> was<00:32:03.220> that<00:32:03.250> it<00:32:03.430> assumes 00:32:03.750 --> 00:32:03.760 align:start position:0% yesterday question was that it assumes 00:32:03.760 --> 00:32:07.800 align:start position:0% yesterday question was that it assumes it's<00:32:04.650> it<00:32:05.650> just<00:32:05.710> hatches<00:32:06.250> and<00:32:06.610> that<00:32:07.330> both<00:32:07.540> the 00:32:07.800 --> 00:32:07.810 align:start position:0% it's it just hatches and that both the 00:32:07.810 --> 00:32:09.960 align:start position:0% it's it just hatches and that both the stage<00:32:08.020> with<00:32:08.170> is<00:32:08.320> just<00:32:08.470> ahead<00:32:08.620> and<00:32:09.040> it's<00:32:09.760> not 00:32:09.960 --> 00:32:09.970 align:start position:0% stage with is just ahead and it's not 00:32:09.970 --> 00:32:13.530 align:start position:0% stage with is just ahead and it's not actually<00:32:10.150> limited<00:32:10.870> to<00:32:10.990> 32<00:32:11.260> bytes<00:32:11.700> which<00:32:12.700> this 00:32:13.530 --> 00:32:13.540 align:start position:0% actually limited to 32 bytes which this 00:32:13.540 --> 00:32:15.270 align:start position:0% actually limited to 32 bytes which this purpose<00:32:13.870> of<00:32:13.990> -<00:32:14.170> to<00:32:14.350> make<00:32:14.500> it<00:32:14.650> longer 00:32:15.270 --> 00:32:15.280 align:start position:0% purpose of - to make it longer 00:32:15.280 --> 00:32:17.430 align:start position:0% purpose of - to make it longer I<00:32:15.310> think<00:32:15.610> 96<00:32:15.940> bytes<00:32:16.330> or<00:32:16.510> something<00:32:16.900> but<00:32:17.410> anyway 00:32:17.430 --> 00:32:17.440 align:start position:0% I think 96 bytes or something but anyway 00:32:17.440 --> 00:32:20.460 align:start position:0% I think 96 bytes or something but anyway it's<00:32:18.010> it's<00:32:18.850> a<00:32:19.060> bit<00:32:19.240> please<00:32:19.480> that's<00:32:19.990> Department 00:32:20.460 --> 00:32:20.470 align:start position:0% it's it's a bit please that's Department 00:32:20.470 --> 00:32:23.370 align:start position:0% it's it's a bit please that's Department 56<00:32:20.950> fights<00:32:21.420> what<00:32:22.420> the<00:32:22.570> state<00:32:22.810> rule<00:32:22.990> is<00:32:23.140> and 00:32:23.370 --> 00:32:23.380 align:start position:0% 56 fights what the state rule is and 00:32:23.380 --> 00:32:34.020 align:start position:0% 56 fights what the state rule is and it's<00:32:23.740> up<00:32:23.860> to<00:32:23.890> the<00:32:24.070> EU<00:32:24.250> to<00:32:24.550> do<00:32:24.640> whatever<00:32:24.850> it<00:32:33.030> you 00:32:34.020 --> 00:32:34.030 align:start position:0% it's up to the EU to do whatever it you 00:32:34.030 --> 00:32:36.330 align:start position:0% it's up to the EU to do whatever it you mean<00:32:34.210> so<00:32:34.690> is<00:32:34.840> there<00:32:35.020> capi<00:32:35.440> prescribe<00:32:35.860> 50<00:32:36.220> you 00:32:36.330 --> 00:32:36.340 align:start position:0% mean so is there capi prescribe 50 you 00:32:36.340 --> 00:32:44.700 align:start position:0% mean so is there capi prescribe 50 you mean<00:32:36.520> writing<00:32:37.440> decency<00:32:38.440> or<00:32:38.740> the<00:32:39.190> law<00:32:40.620> from<00:32:43.710> yes 00:32:44.700 --> 00:32:44.710 align:start position:0% mean writing decency or the law from yes 00:32:44.710 --> 00:32:48.570 align:start position:0% mean writing decency or the law from yes so<00:32:44.950> scanty<00:32:45.880> one<00:32:46.060> would<00:32:46.810> be<00:32:46.980> is<00:32:47.980> written<00:32:48.370> in<00:32:48.460> C++ 00:32:48.570 --> 00:32:48.580 align:start position:0% so scanty one would be is written in C++ 00:32:48.580 --> 00:32:50.490 align:start position:0% so scanty one would be is written in C++ so<00:32:49.120> that<00:32:49.270> would<00:32:49.450> be<00:32:49.540> the<00:32:49.630> best<00:32:49.840> one<00:32:50.020> to<00:32:50.050> use<00:32:50.230> in 00:32:50.490 --> 00:32:50.500 align:start position:0% so that would be the best one to use in 00:32:50.500 --> 00:32:54.260 align:start position:0% so that would be the best one to use in in<00:32:50.680> C<00:32:50.920> and<00:32:51.510> you<00:32:52.510> know<00:32:52.630> calling<00:32:52.930> it<00:32:53.050> from<00:32:53.200> C<00:32:53.380> and 00:32:54.260 --> 00:32:54.270 align:start position:0% in C and you know calling it from C and 00:32:54.270 --> 00:32:56.630 align:start position:0% in C and you know calling it from C and there<00:32:55.270> was<00:32:55.390> one<00:32:55.540> more<00:32:55.660> question 00:32:56.630 --> 00:32:56.640 align:start position:0% there was one more question 00:32:56.640 --> 00:33:00.080 align:start position:0% there was one more question distantly<00:32:57.150> plummet<00:32:57.600> the<00:32:58.429> mine<00:32:59.429> activity<00:33:00.030> is 00:33:00.080 --> 00:33:00.090 align:start position:0% distantly plummet the mine activity is 00:33:00.090 --> 00:33:01.160 align:start position:0% distantly plummet the mine activity is going<00:33:00.270> to<00:33:00.360> be<00:33:00.480> the<00:33:00.720> reservists 00:33:01.160 --> 00:33:01.170 align:start position:0% going to be the reservists 00:33:01.170 --> 00:33:04.610 align:start position:0% going to be the reservists implementation<00:33:02.010> of<00:33:02.790> scouts<00:33:03.179> invasion<00:33:03.870> as<00:33:04.470> you 00:33:04.610 --> 00:33:04.620 align:start position:0% implementation of scouts invasion as you 00:33:04.620 --> 00:33:06.140 align:start position:0% implementation of scouts invasion as you mentioned<00:33:05.010> the<00:33:05.070> secret<00:33:05.490> last<00:33:05.760> one<00:33:05.970> which 00:33:06.140 --> 00:33:06.150 align:start position:0% mentioned the secret last one which 00:33:06.150 --> 00:33:07.940 align:start position:0% mentioned the secret last one which sounds<00:33:06.600> like<00:33:06.809> it's<00:33:07.020> more<00:33:07.110> for<00:33:07.559> benchmarking 00:33:07.940 --> 00:33:07.950 align:start position:0% sounds like it's more for benchmarking 00:33:07.950 --> 00:33:10.030 align:start position:0% sounds like it's more for benchmarking getting<00:33:08.670> the<00:33:08.760> most<00:33:08.910> lecture<00:33:09.270> announces<00:33:09.690> that 00:33:10.030 --> 00:33:10.040 align:start position:0% getting the most lecture announces that 00:33:10.040 --> 00:33:13.820 align:start position:0% getting the most lecture announces that the<00:33:11.040> assembly<00:33:12.030> strings<00:33:12.360> one<00:33:12.960> I<00:33:13.290> guess<00:33:13.620> exactly 00:33:13.820 --> 00:33:13.830 align:start position:0% the assembly strings one I guess exactly 00:33:13.830 --> 00:33:15.650 align:start position:0% the assembly strings one I guess exactly if<00:33:14.520> you<00:33:14.640> want<00:33:14.820> to<00:33:14.880> work<00:33:15.000> with<00:33:15.030> assembly 00:33:15.650 --> 00:33:15.660 align:start position:0% if you want to work with assembly 00:33:15.660 --> 00:33:18.110 align:start position:0% if you want to work with assembly sprints<00:33:16.110> and<00:33:16.260> presumably<00:33:16.670> the<00:33:17.670> actual<00:33:17.940> rust 00:33:18.110 --> 00:33:18.120 align:start position:0% sprints and presumably the actual rust 00:33:18.120 --> 00:33:20.390 align:start position:0% sprints and presumably the actual rust ones<00:33:18.420> where<00:33:18.750> is<00:33:19.230> innocent<00:33:20.070> leave<00:33:20.220> the 00:33:20.390 --> 00:33:20.400 align:start position:0% ones where is innocent leave the 00:33:20.400 --> 00:33:22.460 align:start position:0% ones where is innocent leave the pleistocene<00:33:21.000> register<00:33:21.360> via<00:33:21.420> record<00:33:21.840> it's<00:33:22.350> not 00:33:22.460 --> 00:33:22.470 align:start position:0% pleistocene register via record it's not 00:33:22.470 --> 00:33:24.440 align:start position:0% pleistocene register via record it's not fair<00:33:22.650> to<00:33:22.799> say<00:33:22.980> so<00:33:23.549> the<00:33:23.670> center<00:33:23.940> question<00:33:24.240> was 00:33:24.440 --> 00:33:24.450 align:start position:0% fair to say so the center question was 00:33:24.450 --> 00:33:26.570 align:start position:0% fair to say so the center question was what<00:33:24.900> is<00:33:24.990> the<00:33:25.170> motivation<00:33:25.890> for<00:33:26.070> each<00:33:26.280> of<00:33:26.429> these 00:33:26.570 --> 00:33:26.580 align:start position:0% what is the motivation for each of these 00:33:26.580 --> 00:33:31.370 align:start position:0% what is the motivation for each of these different<00:33:26.910> versions<00:33:27.750> of<00:33:28.080> scale<00:33:28.429> and<00:33:30.350> so<00:33:31.350> a 00:33:31.370 --> 00:33:31.380 align:start position:0% different versions of scale and so a 00:33:31.380 --> 00:33:33.500 align:start position:0% different versions of scale and so a distinction<00:33:31.830> just<00:33:32.280> did<00:33:32.460> the<00:33:32.730> languages<00:33:33.210> used 00:33:33.500 --> 00:33:33.510 align:start position:0% distinction just did the languages used 00:33:33.510 --> 00:33:35.659 align:start position:0% distinction just did the languages used to<00:33:33.690> write<00:33:34.020> the<00:33:34.470> contracts<00:33:34.919> in<00:33:35.040> verses<00:33:35.429> what's 00:33:35.659 --> 00:33:35.669 align:start position:0% to write the contracts in verses what's 00:33:35.669 --> 00:33:37.310 align:start position:0% to write the contracts in verses what's kept<00:33:35.970> is<00:33:36.090> written<00:33:36.390> in<00:33:36.480> as<00:33:36.840> you<00:33:36.960> mentioned<00:33:37.260> this 00:33:37.310 --> 00:33:37.320 align:start position:0% kept is written in as you mentioned this 00:33:37.320 --> 00:33:41.090 align:start position:0% kept is written in as you mentioned this in<00:33:37.470> the<00:33:37.590> script<00:33:38.900> so<00:33:39.900> regarding<00:33:40.290> just<00:33:40.530> kept<00:33:40.830> it 00:33:41.090 --> 00:33:41.100 align:start position:0% in the script so regarding just kept it 00:33:41.100 --> 00:33:44.900 align:start position:0% in the script so regarding just kept it the<00:33:41.280> way<00:33:41.429> you<00:33:41.490> run<00:33:41.820> these<00:33:42.030> contracts<00:33:42.570> and<00:33:43.910> it 00:33:44.900 --> 00:33:44.910 align:start position:0% the way you run these contracts and it 00:33:44.910 --> 00:33:46.340 align:start position:0% the way you run these contracts and it depends<00:33:45.299> on<00:33:45.360> personal<00:33:45.690> preference<00:33:45.960> between 00:33:46.340 --> 00:33:46.350 align:start position:0% depends on personal preference between 00:33:46.350 --> 00:33:48.470 align:start position:0% depends on personal preference between the<00:33:46.679> thrust<00:33:47.040> in<00:33:47.340> this<00:33:47.520> the<00:33:48.090> typescript 00:33:48.470 --> 00:33:48.480 align:start position:0% the thrust in this the typescript 00:33:48.480 --> 00:33:50.289 align:start position:0% the thrust in this the typescript version<00:33:48.929> which<00:33:49.110> ones<00:33:49.410> would<00:33:49.559> you<00:33:49.650> like<00:33:49.890> more 00:33:50.289 --> 00:33:50.299 align:start position:0% version which ones would you like more 00:33:50.299 --> 00:33:53.870 align:start position:0% version which ones would you like more but<00:33:51.299> on<00:33:51.590> more<00:33:52.590> on<00:33:52.770> a<00:33:52.830> production<00:33:53.309> system<00:33:53.520> the 00:33:53.870 --> 00:33:53.880 align:start position:0% but on more on a production system the 00:33:53.880 --> 00:33:56.390 align:start position:0% but on more on a production system the expected<00:33:54.360> scale<00:33:54.630> on<00:33:54.870> the<00:33:54.960> C++<00:33:55.500> version<00:33:55.740> is<00:33:56.160> the 00:33:56.390 --> 00:33:56.400 align:start position:0% expected scale on the C++ version is the 00:33:56.400 --> 00:33:58.940 align:start position:0% expected scale on the C++ version is the one<00:33:56.549> which<00:33:56.760> going<00:33:57.000> to<00:33:57.150> be<00:33:57.299> used<00:33:57.590> the<00:33:58.590> other<00:33:58.710> two 00:33:58.940 --> 00:33:58.950 align:start position:0% one which going to be used the other two 00:33:58.950 --> 00:34:01.669 align:start position:0% one which going to be used the other two are<00:33:59.100> more<00:33:59.250> for<00:33:59.460> prototyping<00:34:00.000> reasons<00:34:00.679> one 00:34:01.669 --> 00:34:01.679 align:start position:0% are more for prototyping reasons one 00:34:01.679 --> 00:34:04.520 align:start position:0% are more for prototyping reasons one interesting<00:34:02.540> fact<00:34:03.540> with<00:34:03.780> the<00:34:04.020> typescript 00:34:04.520 --> 00:34:04.530 align:start position:0% interesting fact with the typescript 00:34:04.530 --> 00:34:06.020 align:start position:0% interesting fact with the typescript version<00:34:05.010> is<00:34:05.100> that<00:34:05.250> you<00:34:05.309> could<00:34:05.549> use<00:34:05.580> it<00:34:05.850> in<00:34:05.970> a 00:34:06.020 --> 00:34:06.030 align:start position:0% version is that you could use it in a 00:34:06.030 --> 00:34:08.330 align:start position:0% version is that you could use it in a browser<00:34:06.210> you<00:34:07.020> wouldn't<00:34:07.260> even<00:34:07.350> need<00:34:07.620> an 00:34:08.330 --> 00:34:08.340 align:start position:0% browser you wouldn't even need an 00:34:08.340 --> 00:34:10.700 align:start position:0% browser you wouldn't even need an environment<00:34:08.780> but<00:34:09.780> I<00:34:10.020> think<00:34:10.379> they're<00:34:10.470> really 00:34:10.700 --> 00:34:10.710 align:start position:0% environment but I think they're really 00:34:10.710 --> 00:34:12.230 align:start position:0% environment but I think they're really just<00:34:10.859> personal<00:34:11.399> preference<00:34:11.609> which<00:34:11.940> one<00:34:12.119> you 00:34:12.230 --> 00:34:12.240 align:start position:0% just personal preference which one you 00:34:12.240 --> 00:34:14.119 align:start position:0% just personal preference which one you want<00:34:12.389> to<00:34:12.480> use<00:34:12.510> or<00:34:12.990> for<00:34:13.129> day-to-day 00:34:14.119 --> 00:34:14.129 align:start position:0% want to use or for day-to-day 00:34:14.129 --> 00:34:17.270 align:start position:0% want to use or for day-to-day prototyping<00:34:14.820> the<00:34:15.540> scans<00:34:15.869> one<00:34:16.109> would<00:34:16.379> be<00:34:16.530> what 00:34:17.270 --> 00:34:17.280 align:start position:0% prototyping the scans one would be what 00:34:17.280 --> 00:34:19.609 align:start position:0% prototyping the scans one would be what you<00:34:17.490> should<00:34:17.730> use<00:34:18.000> to<00:34:18.600> validate<00:34:18.869> that<00:34:19.409> your 00:34:19.609 --> 00:34:19.619 align:start position:0% you should use to validate that your 00:34:19.619 --> 00:34:21.919 align:start position:0% you should use to validate that your stuff<00:34:19.889> actually<00:34:20.280> gonna<00:34:20.639> work<00:34:20.850> and<00:34:21.690> then<00:34:21.780> we 00:34:21.919 --> 00:34:21.929 align:start position:0% stuff actually gonna work and then we 00:34:21.929 --> 00:34:24.080 align:start position:0% stuff actually gonna work and then we got<00:34:22.050> into<00:34:22.200> contract<00:34:22.619> languages<00:34:23.070> the<00:34:23.700> assembly 00:34:24.080 --> 00:34:24.090 align:start position:0% got into contract languages the assembly 00:34:24.090 --> 00:34:25.639 align:start position:0% got into contract languages the assembly script<00:34:24.359> versus<00:34:24.690> writing<00:34:25.050> contracts<00:34:25.470> with 00:34:25.639 --> 00:34:25.649 align:start position:0% script versus writing contracts with 00:34:25.649 --> 00:34:29.659 align:start position:0% script versus writing contracts with contracts<00:34:26.129> in<00:34:26.220> rust<00:34:26.460> or<00:34:26.669> ease<00:34:26.909> or<00:34:27.570> in<00:34:27.690> C<00:34:28.669> it's 00:34:29.659 --> 00:34:29.669 align:start position:0% contracts in rust or ease or in C it's 00:34:29.669 --> 00:34:31.869 align:start position:0% contracts in rust or ease or in C it's again<00:34:29.970> down<00:34:30.210> to<00:34:30.389> personal<00:34:30.629> preference<00:34:31.020> but 00:34:31.869 --> 00:34:31.879 align:start position:0% again down to personal preference but 00:34:31.879 --> 00:34:33.919 align:start position:0% again down to personal preference but each<00:34:32.879> of<00:34:32.940> them<00:34:33.240> we<00:34:33.359> have<00:34:33.480> different<00:34:33.780> ways<00:34:33.869> to 00:34:33.919 --> 00:34:33.929 align:start position:0% each of them we have different ways to 00:34:33.929 --> 00:34:36.470 align:start position:0% each of them we have different ways to optimize<00:34:34.280> the<00:34:35.280> code<00:34:35.490> to<00:34:35.700> be<00:34:35.790> efficiently<00:34:36.300> more 00:34:36.470 --> 00:34:36.480 align:start position:0% optimize the code to be efficiently more 00:34:36.480 --> 00:34:38.359 align:start position:0% optimize the code to be efficiently more had<00:34:37.080> better<00:34:37.260> experience<00:34:37.740> which<00:34:37.889> one<00:34:38.070> or<00:34:38.220> that 00:34:38.359 --> 00:34:38.369 align:start position:0% had better experience which one or that 00:34:38.369 --> 00:34:41.359 align:start position:0% had better experience which one or that are<00:34:38.550> depending<00:34:39.000> on<00:34:39.090> the<00:34:39.210> use<00:34:39.330> case<00:34:39.710> and<00:34:40.710> that's 00:34:41.359 --> 00:34:41.369 align:start position:0% are depending on the use case and that's 00:34:41.369 --> 00:34:43.010 align:start position:0% are depending on the use case and that's that's<00:34:41.760> actually<00:34:41.970> one<00:34:42.389> of<00:34:42.419> the<00:34:42.629> the<00:34:42.810> biggest 00:34:43.010 --> 00:34:43.020 align:start position:0% that's actually one of the the biggest 00:34:43.020 --> 00:34:45.470 align:start position:0% that's actually one of the the biggest challenges<00:34:43.740> to<00:34:43.800> to<00:34:44.609> figure<00:34:44.850> out<00:34:44.970> what<00:34:45.179> is<00:34:45.270> the 00:34:45.470 --> 00:34:45.480 align:start position:0% challenges to to figure out what is the 00:34:45.480 --> 00:34:48.710 align:start position:0% challenges to to figure out what is the the<00:34:45.720> best<00:34:45.960> way<00:34:46.320> to<00:34:46.350> optimize<00:34:47.040> these<00:34:47.720> high 00:34:48.710 --> 00:34:48.720 align:start position:0% the best way to optimize these high 00:34:48.720 --> 00:34:52.520 align:start position:0% the best way to optimize these high level<00:34:48.960> languages<00:34:49.350> for<00:34:49.889> was<00:34:51.530> necessarily 00:34:52.520 --> 00:34:52.530 align:start position:0% level languages for was necessarily 00:34:52.530 --> 00:34:53.710 align:start position:0% level languages for was necessarily encouraging<00:34:53.010> papers 00:34:53.710 --> 00:34:53.720 align:start position:0% encouraging papers 00:34:53.720 --> 00:34:56.409 align:start position:0% encouraging papers some<00:34:54.020> specific<00:34:54.409> one<00:34:54.980> massage<00:34:55.520> is<00:34:55.790> for<00:34:56.030> every 00:34:56.409 --> 00:34:56.419 align:start position:0% some specific one massage is for every 00:34:56.419 --> 00:34:58.480 align:start position:0% some specific one massage is for every what<00:34:56.659> we<00:34:56.810> want<00:34:57.290> to<00:34:57.410> work<00:34:57.589> with<00:34:57.829> right<00:34:58.010> now 00:34:58.480 --> 00:34:58.490 align:start position:0% what we want to work with right now 00:34:58.490 --> 00:35:03.940 align:start position:0% what we want to work with right now yeah<00:34:59.119> yeah<00:34:59.510> I<00:34:59.540> would<00:34:59.810> say<00:35:00.490> thanks<00:35:01.490> beer<00:35:02.950> we 00:35:03.940 --> 00:35:03.950 align:start position:0% yeah yeah I would say thanks beer we 00:35:03.950 --> 00:35:14.270 align:start position:0% yeah yeah I would say thanks beer we should<00:35:04.130> be<00:35:04.250> moving<00:35:04.369> on<00:35:04.609> a<00:35:04.670> time<00:35:04.940> right 00:35:14.270 --> 00:35:14.280 align:start position:0% 00:35:14.280 --> 00:35:16.860 align:start position:0% Cecina<00:35:15.280> and<00:35:15.640> came<00:35:15.910> from<00:35:16.090> the<00:35:16.180> he<00:35:16.360> wasn't<00:35:16.660> team 00:35:16.860 --> 00:35:16.870 align:start position:0% Cecina and came from the he wasn't team 00:35:16.870 --> 00:35:19.320 align:start position:0% Cecina and came from the he wasn't team are<00:35:17.020> talking<00:35:17.440> about<00:35:17.500> to<00:35:18.250> become<00:35:18.640> a<00:35:18.880> to<00:35:19.180> bow 00:35:19.320 --> 00:35:19.330 align:start position:0% are talking about to become a to bow 00:35:19.330 --> 00:35:21.240 align:start position:0% are talking about to become a to bow token<00:35:19.720> I'm<00:35:20.650> sure<00:35:20.830> it<00:35:20.950> will<00:35:21.040> be<00:35:21.160> very 00:35:21.240 --> 00:35:21.250 align:start position:0% token I'm sure it will be very 00:35:21.250 --> 00:35:30.120 align:start position:0% token I'm sure it will be very interesting<00:35:24.990> thanks<00:35:25.990> for<00:35:26.140> products<00:35:29.130> party 00:35:30.120 --> 00:35:30.130 align:start position:0% interesting thanks for products party 00:35:30.130 --> 00:35:32.160 align:start position:0% interesting thanks for products party disclaimers<00:35:30.910> have<00:35:31.120> our<00:35:31.240> time<00:35:31.510> I'm<00:35:31.690> just<00:35:31.990> going 00:35:32.160 --> 00:35:32.170 align:start position:0% disclaimers have our time I'm just going 00:35:32.170 --> 00:35:38.550 align:start position:0% disclaimers have our time I'm just going to<00:35:32.200> trade<00:35:32.440> on<00:35:35.220> all<00:35:36.220> right<00:35:36.340> so<00:35:37.240> now<00:35:37.750> that<00:35:37.780> we've 00:35:38.550 --> 00:35:38.560 align:start position:0% to trade on all right so now that we've 00:35:38.560 --> 00:35:41.340 align:start position:0% to trade on all right so now that we've seen<00:35:38.800> what<00:35:39.220> these<00:35:39.700> are<00:35:40.120> and<00:35:40.150> how<00:35:40.510> we<00:35:40.570> can<00:35:40.720> test 00:35:41.340 --> 00:35:41.350 align:start position:0% seen what these are and how we can test 00:35:41.350 --> 00:35:42.680 align:start position:0% seen what these are and how we can test them<00:35:41.590> and<00:35:41.890> protect<00:35:42.430> them 00:35:42.680 --> 00:35:42.690 align:start position:0% them and protect them 00:35:42.690 --> 00:35:48.330 align:start position:0% them and protect them we're<00:35:43.690> going<00:35:43.900> to<00:35:44.080> go<00:35:44.440> into<00:35:45.000> a<00:35:46.000> sample<00:35:47.160> token<00:35:48.160> EE 00:35:48.330 --> 00:35:48.340 align:start position:0% we're going to go into a sample token EE 00:35:48.340 --> 00:35:51.750 align:start position:0% we're going to go into a sample token EE and<00:35:49.020> our<00:35:50.020> constraint<00:35:50.650> here<00:35:50.980> is<00:35:51.220> that<00:35:51.460> we<00:35:51.640> want 00:35:51.750 --> 00:35:51.760 align:start position:0% and our constraint here is that we want 00:35:51.760 --> 00:35:53.850 align:start position:0% and our constraint here is that we want to<00:35:51.910> have<00:35:52.150> a<00:35:52.390> token<00:35:52.810> EE<00:35:52.930> that<00:35:53.260> is<00:35:53.470> compatible 00:35:53.850 --> 00:35:53.860 align:start position:0% to have a token EE that is compatible 00:35:53.860 --> 00:35:56.970 align:start position:0% to have a token EE that is compatible with<00:35:54.100> one<00:35:54.910> to<00:35:55.300> eath<00:35:55.450> one<00:35:55.720> chain<00:35:55.960> that<00:35:56.260> we<00:35:56.830> know 00:35:56.970 --> 00:35:56.980 align:start position:0% with one to eath one chain that we know 00:35:56.980 --> 00:36:01.140 align:start position:0% with one to eath one chain that we know and<00:35:57.220> love<00:35:59.070> the<00:36:00.070> all<00:36:00.340> kind<00:36:00.610> of<00:36:00.730> just<00:36:00.940> thought 00:36:01.140 --> 00:36:01.150 align:start position:0% and love the all kind of just thought 00:36:01.150 --> 00:36:04.230 align:start position:0% and love the all kind of just thought would<00:36:01.450> be<00:36:01.660> as<00:36:02.620> follows<00:36:03.010> first<00:36:03.520> people<00:36:03.880> going 00:36:04.230 --> 00:36:04.240 align:start position:0% would be as follows first people going 00:36:04.240 --> 00:36:06.960 align:start position:0% would be as follows first people going to<00:36:04.450> SMPT<00:36:05.200> which<00:36:05.410> is<00:36:05.560> which<00:36:06.250> was<00:36:06.460> our<00:36:06.670> initial 00:36:06.960 --> 00:36:06.970 align:start position:0% to SMPT which is which was our initial 00:36:06.970 --> 00:36:13.550 align:start position:0% to SMPT which is which was our initial prototype<00:36:08.310> offer<00:36:09.420> stateless<00:36:10.420> token<00:36:10.870> it<00:36:11.620> was 00:36:13.550 --> 00:36:13.560 align:start position:0% prototype offer stateless token it was 00:36:13.560 --> 00:36:17.670 align:start position:0% prototype offer stateless token it was implemented<00:36:14.560> in<00:36:14.680> Rossum<00:36:15.160> as<00:36:15.310> well<00:36:15.550> see<00:36:16.680> then 00:36:17.670 --> 00:36:17.680 align:start position:0% implemented in Rossum as well see then 00:36:17.680 --> 00:36:20.160 align:start position:0% implemented in Rossum as well see then we'll<00:36:17.950> go<00:36:18.160> into<00:36:18.550> a<00:36:18.850> multi<00:36:19.300> proof<00:36:19.510> scheme<00:36:19.900> for 00:36:20.160 --> 00:36:20.170 align:start position:0% we'll go into a multi proof scheme for 00:36:20.170 --> 00:36:23.700 align:start position:0% we'll go into a multi proof scheme for the<00:36:20.320> work<00:36:20.500> of<00:36:20.710> Patricia<00:36:21.460> free<00:36:22.080> which<00:36:23.080> team 00:36:23.700 --> 00:36:23.710 align:start position:0% the work of Patricia free which team 00:36:23.710 --> 00:36:26.940 align:start position:0% the work of Patricia free which team will<00:36:23.950> explain<00:36:24.430> and<00:36:24.880> then<00:36:25.450> we'll<00:36:26.350> see<00:36:26.590> two<00:36:26.770> more 00:36:26.940 --> 00:36:26.950 align:start position:0% will explain and then we'll see two more 00:36:26.950 --> 00:36:30.270 align:start position:0% will explain and then we'll see two more token<00:36:27.310> which<00:36:27.970> is<00:36:28.120> a<00:36:28.150> lot<00:36:28.360> of<00:36:28.480> e<00:36:28.630> similar<00:36:29.440> to<00:36:29.650> SPT 00:36:30.270 --> 00:36:30.280 align:start position:0% token which is a lot of e similar to SPT 00:36:30.280 --> 00:36:33.360 align:start position:0% token which is a lot of e similar to SPT by<00:36:30.640> Jesus<00:36:31.150> the<00:36:31.330> butiful<00:36:31.870> scheme<00:36:32.350> and<00:36:32.920> comes<00:36:33.190> of 00:36:33.360 --> 00:36:33.370 align:start position:0% by Jesus the butiful scheme and comes of 00:36:33.370 --> 00:36:37.730 align:start position:0% by Jesus the butiful scheme and comes of comes<00:36:34.060> with<00:36:34.600> a<00:36:34.630> lot<00:36:34.900> of<00:36:35.400> optimizations<00:36:36.400> so 00:36:37.730 --> 00:36:37.740 align:start position:0% comes with a lot of optimizations so 00:36:37.740 --> 00:36:40.850 align:start position:0% comes with a lot of optimizations so yeah<00:36:38.740> SME<00:36:39.370> is<00:36:39.640> a<00:36:39.670> stateless<00:36:40.120> o-chem 00:36:40.850 --> 00:36:40.860 align:start position:0% yeah SME is a stateless o-chem 00:36:40.860 --> 00:36:43.980 align:start position:0% yeah SME is a stateless o-chem compatible<00:36:41.860> with<00:36:42.100> this<00:36:42.310> one<00:36:42.610> and<00:36:42.910> what<00:36:43.630> I<00:36:43.660> mean 00:36:43.980 --> 00:36:43.990 align:start position:0% compatible with this one and what I mean 00:36:43.990 --> 00:36:47.550 align:start position:0% compatible with this one and what I mean with<00:36:44.440> that<00:36:44.800> is<00:36:45.090> given<00:36:46.090> the<00:36:46.210> same<00:36:46.390> accounts<00:36:46.930> it 00:36:47.550 --> 00:36:47.560 align:start position:0% with that is given the same accounts it 00:36:47.560 --> 00:36:49.650 align:start position:0% with that is given the same accounts it will<00:36:47.830> have<00:36:48.070> to<00:36:48.250> produce<00:36:48.460> the<00:36:48.850> same<00:36:49.090> state 00:36:49.650 --> 00:36:49.660 align:start position:0% will have to produce the same state 00:36:49.660 --> 00:36:52.230 align:start position:0% will have to produce the same state route<00:36:49.900> and<00:36:50.170> we<00:36:51.070> also<00:36:51.220> want<00:36:51.550> to<00:36:51.700> enable<00:36:51.880> users 00:36:52.230 --> 00:36:52.240 align:start position:0% route and we also want to enable users 00:36:52.240 --> 00:36:54.990 align:start position:0% route and we also want to enable users to<00:36:52.510> you<00:36:53.020> know<00:36:53.230> to<00:36:53.500> sign<00:36:53.800> transactions<00:36:54.430> with 00:36:54.990 --> 00:36:55.000 align:start position:0% to you know to sign transactions with 00:36:55.000 --> 00:36:59.250 align:start position:0% to you know to sign transactions with their<00:36:55.210> f1<00:36:55.590> private<00:36:56.590> keys<00:36:57.810> this<00:36:58.810> initial 00:36:59.250 --> 00:36:59.260 align:start position:0% their f1 private keys this initial 00:36:59.260 --> 00:37:02.340 align:start position:0% their f1 private keys this initial prototype<00:36:59.770> was<00:37:00.070> in<00:37:00.940> brass<00:37:01.270> and<00:37:01.510> its<00:37:01.900> users 00:37:02.340 --> 00:37:02.350 align:start position:0% prototype was in brass and its users 00:37:02.350 --> 00:37:06.600 align:start position:0% prototype was in brass and its users parity<00:37:03.220> libraries<00:37:04.950> in<00:37:05.950> order<00:37:06.130> to<00:37:06.460> maintain 00:37:06.600 --> 00:37:06.610 align:start position:0% parity libraries in order to maintain 00:37:06.610 --> 00:37:11.580 align:start position:0% parity libraries in order to maintain user<00:37:07.590> balances<00:37:08.730> we<00:37:09.730> stored<00:37:10.210> the<00:37:10.450> key<00:37:10.780> to 00:37:11.580 --> 00:37:11.590 align:start position:0% user balances we stored the key to 00:37:11.590 --> 00:37:13.890 align:start position:0% user balances we stored the key to accounts<00:37:12.250> in<00:37:12.430> the<00:37:13.060> leaves<00:37:13.300> of 00:37:13.890 --> 00:37:13.900 align:start position:0% accounts in the leaves of 00:37:13.900 --> 00:37:15.840 align:start position:0% accounts in the leaves of Patricia<00:37:14.440> tree<00:37:14.710> that<00:37:15.220> you<00:37:15.310> can<00:37:15.490> see<00:37:15.640> in<00:37:15.700> this 00:37:15.840 --> 00:37:15.850 align:start position:0% Patricia tree that you can see in this 00:37:15.850 --> 00:37:19.050 align:start position:0% Patricia tree that you can see in this diagram<00:37:16.170> so<00:37:17.170> the<00:37:17.620> accounts<00:37:18.040> are<00:37:18.220> very<00:37:18.610> similar 00:37:19.050 --> 00:37:19.060 align:start position:0% diagram so the accounts are very similar 00:37:19.060 --> 00:37:22.830 align:start position:0% diagram so the accounts are very similar to<00:37:19.330> each<00:37:19.630> one<00:37:20.020> accounts<00:37:20.410> the<00:37:21.070> same<00:37:21.570> here<00:37:22.570> are 00:37:22.830 --> 00:37:22.840 align:start position:0% to each one accounts the same here are 00:37:22.840 --> 00:37:25.350 align:start position:0% to each one accounts the same here are the<00:37:23.170> leaves<00:37:23.440> you<00:37:23.890> can<00:37:24.640> see<00:37:24.880> branch<00:37:25.150> no 00:37:25.350 --> 00:37:25.360 align:start position:0% the leaves you can see branch no 00:37:25.360 --> 00:37:29.880 align:start position:0% the leaves you can see branch no extension<00:37:26.050> notes<00:37:26.370> and<00:37:27.370> so<00:37:27.670> on<00:37:28.620> but<00:37:29.620> note<00:37:29.860> that 00:37:29.880 --> 00:37:29.890 align:start position:0% extension notes and so on but note that 00:37:29.890 --> 00:37:33.170 align:start position:0% extension notes and so on but note that as<00:37:30.730> we<00:37:30.940> all<00:37:31.030> know<00:37:31.240> this<00:37:31.630> is<00:37:31.780> stateless<00:37:32.200> so<00:37:32.470> this 00:37:33.170 --> 00:37:33.180 align:start position:0% as we all know this is stateless so this 00:37:33.180 --> 00:37:36.360 align:start position:0% as we all know this is stateless so this state<00:37:34.180> is<00:37:34.210> not<00:37:34.660> stored<00:37:35.050> unchanged<00:37:35.590> but<00:37:36.160> we 00:37:36.360 --> 00:37:36.370 align:start position:0% state is not stored unchanged but we 00:37:36.370 --> 00:37:38.610 align:start position:0% state is not stored unchanged but we rely<00:37:36.760> on<00:37:37.180> third<00:37:37.630> party<00:37:37.960> entities<00:37:38.380> called 00:37:38.610 --> 00:37:38.620 align:start position:0% rely on third party entities called 00:37:38.620 --> 00:37:41.160 align:start position:0% rely on third party entities called three<00:37:38.980> layers<00:37:39.280> to<00:37:39.610> store<00:37:40.450> this<00:37:40.600> state<00:37:40.900> and 00:37:41.160 --> 00:37:41.170 align:start position:0% three layers to store this state and 00:37:41.170 --> 00:37:45.930 align:start position:0% three layers to store this state and provide<00:37:41.800> the<00:37:42.550> service<00:37:43.000> to<00:37:43.030> users<00:37:44.490> so<00:37:45.490> users 00:37:45.930 --> 00:37:45.940 align:start position:0% provide the service to users so users 00:37:45.940 --> 00:37:47.970 align:start position:0% provide the service to users so users when<00:37:46.300> they<00:37:46.390> want<00:37:46.570> to<00:37:46.750> send<00:37:47.530> this<00:37:47.620> transaction 00:37:47.970 --> 00:37:47.980 align:start position:0% when they want to send this transaction 00:37:47.980 --> 00:37:50.400 align:start position:0% when they want to send this transaction they<00:37:48.790> sign<00:37:49.090> the<00:37:49.210> transaction<00:37:49.750> send<00:37:50.020> it<00:37:50.170> to<00:37:50.260> the 00:37:50.400 --> 00:37:50.410 align:start position:0% they sign the transaction send it to the 00:37:50.410 --> 00:37:53.820 align:start position:0% they sign the transaction send it to the layer<00:37:50.740> which<00:37:51.490> then<00:37:51.790> attaches<00:37:52.830> necessary 00:37:53.820 --> 00:37:53.830 align:start position:0% layer which then attaches necessary 00:37:53.830 --> 00:37:56.340 align:start position:0% layer which then attaches necessary myrtle<00:37:54.250> proofs<00:37:54.550> for<00:37:55.270> a<00:37:55.330> sender<00:37:55.840> and<00:37:55.870> recipient 00:37:56.340 --> 00:37:56.350 align:start position:0% myrtle proofs for a sender and recipient 00:37:56.350 --> 00:37:59.280 align:start position:0% myrtle proofs for a sender and recipient to<00:37:57.070> the<00:37:57.220> transaction<00:37:57.790> packages<00:37:58.660> multiple<00:37:59.170> of 00:37:59.280 --> 00:37:59.290 align:start position:0% to the transaction packages multiple of 00:37:59.290 --> 00:38:02.370 align:start position:0% to the transaction packages multiple of these<00:37:59.530> into<00:38:00.250> a<00:38:00.280> block<00:38:00.640> and<00:38:01.020> publishes<00:38:02.020> it<00:38:02.050> to 00:38:02.370 --> 00:38:02.380 align:start position:0% these into a block and publishes it to 00:38:02.380 --> 00:38:08.700 align:start position:0% these into a block and publishes it to the<00:38:02.470> network<00:38:05.640> looking<00:38:06.640> from<00:38:06.880> outside<00:38:07.470> the<00:38:08.470> he 00:38:08.700 --> 00:38:08.710 align:start position:0% the network looking from outside the he 00:38:08.710 --> 00:38:11.310 align:start position:0% the network looking from outside the he would<00:38:09.220> take<00:38:09.430> this<00:38:09.700> block<00:38:09.970> data<00:38:10.240> as<00:38:10.690> well<00:38:11.200> as 00:38:11.310 --> 00:38:11.320 align:start position:0% would take this block data as well as 00:38:11.320 --> 00:38:13.350 align:start position:0% would take this block data as well as the<00:38:11.500> priest<00:38:11.800> a<00:38:11.950> truth<00:38:12.190> which<00:38:12.550> is<00:38:12.730> in<00:38:12.910> the<00:38:13.060> short 00:38:13.350 --> 00:38:13.360 align:start position:0% the priest a truth which is in the short 00:38:13.360 --> 00:38:17.640 align:start position:0% the priest a truth which is in the short state<00:38:14.220> and<00:38:15.220> it<00:38:15.700> will<00:38:16.150> have<00:38:16.360> to<00:38:16.390> produce<00:38:16.810> a<00:38:17.230> post 00:38:17.640 --> 00:38:17.650 align:start position:0% state and it will have to produce a post 00:38:17.650 --> 00:38:23.220 align:start position:0% state and it will have to produce a post a<00:38:17.860> true<00:38:18.870> and<00:38:19.870> now<00:38:20.020> going<00:38:20.410> inside<00:38:21.990> of<00:38:22.990> course 00:38:23.220 --> 00:38:23.230 align:start position:0% a true and now going inside of course 00:38:23.230 --> 00:38:26.370 align:start position:0% a true and now going inside of course the<00:38:23.560> EE<00:38:23.980> will<00:38:24.400> first<00:38:24.730> have<00:38:25.030> to<00:38:25.090> be<00:38:25.630> counterpart 00:38:26.370 --> 00:38:26.380 align:start position:0% the EE will first have to be counterpart 00:38:26.380 --> 00:38:28.770 align:start position:0% the EE will first have to be counterpart a<00:38:26.530> town<00:38:26.770> and<00:38:27.010> this<00:38:27.400> voltage<00:38:27.820> is<00:38:28.000> comprised<00:38:28.540> of 00:38:28.770 --> 00:38:28.780 align:start position:0% a town and this voltage is comprised of 00:38:28.780 --> 00:38:32.400 align:start position:0% a town and this voltage is comprised of a<00:38:28.930> list<00:38:29.110> of<00:38:29.290> transactions<00:38:30.750> it's<00:38:31.750> very<00:38:32.110> similar 00:38:32.400 --> 00:38:32.410 align:start position:0% a list of transactions it's very similar 00:38:32.410 --> 00:38:34.740 align:start position:0% a list of transactions it's very similar to<00:38:32.800> this<00:38:33.280> one<00:38:33.340> so<00:38:33.730> we<00:38:33.850> have<00:38:34.030> the<00:38:34.210> to<00:38:34.360> address 00:38:34.740 --> 00:38:34.750 align:start position:0% to this one so we have the to address 00:38:34.750 --> 00:38:37.380 align:start position:0% to this one so we have the to address value<00:38:34.990> non<00:38:35.260> signature<00:38:36.000> additionally<00:38:37.000> we<00:38:37.180> have 00:38:37.380 --> 00:38:37.390 align:start position:0% value non signature additionally we have 00:38:37.390 --> 00:38:41.520 align:start position:0% value non signature additionally we have the<00:38:38.670> food<00:38:39.670> for<00:38:39.940> the<00:38:40.060> sender's<00:38:40.480> account<00:38:40.870> and<00:38:41.140> as 00:38:41.520 --> 00:38:41.530 align:start position:0% the food for the sender's account and as 00:38:41.530 --> 00:38:45.560 align:start position:0% the food for the sender's account and as well<00:38:41.680> as<00:38:41.800> the<00:38:41.920> recipients<00:38:42.400> account<00:38:44.100> and<00:38:45.100> now 00:38:45.560 --> 00:38:45.570 align:start position:0% well as the recipients account and now 00:38:45.570 --> 00:38:49.440 align:start position:0% well as the recipients account and now for<00:38:46.570> each<00:38:46.750> of<00:38:46.780> the<00:38:47.050> transactions<00:38:47.790> the<00:38:48.790> verify 00:38:49.440 --> 00:38:49.450 align:start position:0% for each of the transactions the verify 00:38:49.450 --> 00:38:52.790 align:start position:0% for each of the transactions the verify the<00:38:49.510> signature<00:38:50.110> be<00:38:50.770> verified<00:38:51.250> demarco<00:38:52.090> crews 00:38:52.790 --> 00:38:52.800 align:start position:0% the signature be verified demarco crews 00:38:52.800 --> 00:38:55.950 align:start position:0% the signature be verified demarco crews checked<00:38:53.800> for<00:38:54.100> lumps<00:38:54.340> and<00:38:54.610> balances<00:38:55.180> and<00:38:55.420> then 00:38:55.950 --> 00:38:55.960 align:start position:0% checked for lumps and balances and then 00:38:55.960 --> 00:38:59.250 align:start position:0% checked for lumps and balances and then update<00:38:56.920> the<00:38:57.310> leaves<00:38:57.880> of<00:38:58.210> the<00:38:58.390> tree<00:38:58.630> for<00:38:59.110> those 00:38:59.250 --> 00:38:59.260 align:start position:0% update the leaves of the tree for those 00:38:59.260 --> 00:39:02.220 align:start position:0% update the leaves of the tree for those accounts<00:39:00.330> after<00:39:01.330> every<00:39:01.570> transaction<00:39:01.930> has 00:39:02.220 --> 00:39:02.230 align:start position:0% accounts after every transaction has 00:39:02.230 --> 00:39:04.010 align:start position:0% accounts after every transaction has been<00:39:02.260> processed 00:39:04.010 --> 00:39:04.020 align:start position:0% been processed 00:39:04.020 --> 00:39:10.110 align:start position:0% been processed we<00:39:05.020> can<00:39:05.320> finally<00:39:05.860> compute<00:39:06.490> the<00:39:06.670> postage<00:39:07.180> rules 00:39:10.110 --> 00:39:10.120 align:start position:0% 00:39:10.120 --> 00:39:13.850 align:start position:0% to<00:39:10.450> evaluate<00:39:10.840> this<00:39:11.380> prototype<00:39:11.770> we<00:39:12.640> simulated 00:39:13.850 --> 00:39:13.860 align:start position:0% to evaluate this prototype we simulated 00:39:13.860 --> 00:39:17.760 align:start position:0% to evaluate this prototype we simulated 5,000<00:39:14.860> accounts<00:39:15.280> in<00:39:15.400> the<00:39:15.490> state<00:39:15.760> and<00:39:16.770> 70 00:39:17.760 --> 00:39:17.770 align:start position:0% 5,000 accounts in the state and 70 00:39:17.770 --> 00:39:22.530 align:start position:0% 5,000 accounts in the state and 70 transactions<00:39:19.200> and<00:39:20.200> run<00:39:21.100> it<00:39:21.250> through<00:39:21.540> scout 00:39:22.530 --> 00:39:22.540 align:start position:0% transactions and run it through scout 00:39:22.540 --> 00:39:26.310 align:start position:0% transactions and run it through scout with<00:39:23.140> there<00:39:23.770> was<00:39:23.920> we<00:39:24.190> interpreter<00:39:25.060> and<00:39:25.420> these 00:39:26.310 --> 00:39:26.320 align:start position:0% with there was we interpreter and these 00:39:26.320 --> 00:39:29.250 align:start position:0% with there was we interpreter and these are<00:39:26.470> the<00:39:26.590> results<00:39:26.950> we<00:39:27.070> got<00:39:27.250> so<00:39:28.020> blood<00:39:29.020> size 00:39:29.250 --> 00:39:29.260 align:start position:0% are the results we got so blood size 00:39:29.260 --> 00:39:33.810 align:start position:0% are the results we got so blood size here<00:39:29.650> is<00:39:30.300> 235<00:39:31.300> kilobytes<00:39:31.840> for<00:39:32.370> the<00:39:33.370> 70 00:39:33.810 --> 00:39:33.820 align:start position:0% here is 235 kilobytes for the 70 00:39:33.820 --> 00:39:38.520 align:start position:0% here is 235 kilobytes for the 70 transaction<00:39:34.420> and<00:39:35.070> speed<00:39:36.070> is<00:39:36.370> 5<00:39:37.360> seconds<00:39:37.870> out 00:39:38.520 --> 00:39:38.530 align:start position:0% transaction and speed is 5 seconds out 00:39:38.530 --> 00:39:42.300 align:start position:0% transaction and speed is 5 seconds out of<00:39:38.590> reach<00:39:39.160> 4<00:39:40.150> seconds<00:39:40.660> is<00:39:40.840> for<00:39:41.470> signature 00:39:42.300 --> 00:39:42.310 align:start position:0% of reach 4 seconds is for signature 00:39:42.310 --> 00:39:45.990 align:start position:0% of reach 4 seconds is for signature verification<00:39:43.830> but<00:39:44.830> don't<00:39:45.070> panic<00:39:45.220> just<00:39:45.490> yet 00:39:45.990 --> 00:39:46.000 align:start position:0% verification but don't panic just yet 00:39:46.000 --> 00:39:48.540 align:start position:0% verification but don't panic just yet we'll<00:39:46.240> get<00:39:46.570> much<00:39:47.050> better<00:39:47.260> results<00:39:47.740> very<00:39:48.460> soon 00:39:48.540 --> 00:39:48.550 align:start position:0% we'll get much better results very soon 00:39:48.550 --> 00:39:53.400 align:start position:0% we'll get much better results very soon might<00:39:49.420> end<00:39:49.600> of<00:39:49.750> this<00:39:49.870> talk<00:39:51.300> now<00:39:52.300> let's<00:39:53.140> go<00:39:53.260> back 00:39:53.400 --> 00:39:53.410 align:start position:0% might end of this talk now let's go back 00:39:53.410 --> 00:39:56.370 align:start position:0% might end of this talk now let's go back to<00:39:53.440> the<00:39:53.680> same<00:39:54.490> diagram<00:39:55.000> let's<00:39:55.900> say<00:39:56.020> we<00:39:56.200> have<00:39:56.350> a 00:39:56.370 --> 00:39:56.380 align:start position:0% to the same diagram let's say we have a 00:39:56.380 --> 00:40:00.090 align:start position:0% to the same diagram let's say we have a transaction<00:39:57.100> that<00:39:57.370> wants<00:39:57.910> to<00:39:58.120> prove<00:39:59.100> these 00:40:00.090 --> 00:40:00.100 align:start position:0% transaction that wants to prove these 00:40:00.100 --> 00:40:03.690 align:start position:0% transaction that wants to prove these two<00:40:00.520> accounts<00:40:00.940> and<00:40:01.360> as<00:40:02.140> you<00:40:02.440> will<00:40:02.620> notice<00:40:02.830> the 00:40:03.690 --> 00:40:03.700 align:start position:0% two accounts and as you will notice the 00:40:03.700 --> 00:40:06.420 align:start position:0% two accounts and as you will notice the note<00:40:03.910> that<00:40:04.120> I've<00:40:04.270> highlighted<00:40:04.540> in<00:40:05.050> red<00:40:05.430> will 00:40:06.420 --> 00:40:06.430 align:start position:0% note that I've highlighted in red will 00:40:06.430 --> 00:40:09.050 align:start position:0% note that I've highlighted in red will be<00:40:06.460> duplicated<00:40:07.360> in<00:40:07.600> both<00:40:07.930> of<00:40:08.200> the<00:40:08.380> proofs 00:40:09.050 --> 00:40:09.060 align:start position:0% be duplicated in both of the proofs 00:40:09.060 --> 00:40:12.870 align:start position:0% be duplicated in both of the proofs which<00:40:10.060> is<00:40:10.270> inefficient<00:40:10.690> so<00:40:11.440> if<00:40:12.310> we<00:40:12.550> could<00:40:12.700> have 00:40:12.870 --> 00:40:12.880 align:start position:0% which is inefficient so if we could have 00:40:12.880 --> 00:40:15.840 align:start position:0% which is inefficient so if we could have a<00:40:12.910> multi<00:40:13.360> proof<00:40:13.570> scheme<00:40:13.960> that<00:40:14.440> includes<00:40:15.130> all 00:40:15.840 --> 00:40:15.850 align:start position:0% a multi proof scheme that includes all 00:40:15.850 --> 00:40:19.110 align:start position:0% a multi proof scheme that includes all the<00:40:16.150> necessary<00:40:16.180> notes<00:40:16.870> but<00:40:17.170> only<00:40:17.470> ones<00:40:18.120> we 00:40:19.110 --> 00:40:19.120 align:start position:0% the necessary notes but only ones we 00:40:19.120 --> 00:40:22.410 align:start position:0% the necessary notes but only ones we would<00:40:19.330> reduce<00:40:19.630> the<00:40:19.840> block<00:40:20.050> size<00:40:20.290> and<00:40:21.390> with<00:40:22.390> a 00:40:22.410 --> 00:40:22.420 align:start position:0% would reduce the block size and with a 00:40:22.420 --> 00:40:24.720 align:start position:0% would reduce the block size and with a good<00:40:22.720> algorithm<00:40:23.050> we<00:40:23.410> could<00:40:23.560> also<00:40:23.770> gain 00:40:24.720 --> 00:40:24.730 align:start position:0% good algorithm we could also gain 00:40:24.730 --> 00:40:26.970 align:start position:0% good algorithm we could also gain efficiency<00:40:25.390> in<00:40:25.540> the<00:40:25.660> run<00:40:25.840> time<00:40:26.110> by<00:40:26.560> matching 00:40:26.970 --> 00:40:26.980 align:start position:0% efficiency in the run time by matching 00:40:26.980 --> 00:40:29.940 align:start position:0% efficiency in the run time by matching the<00:40:27.310> verification<00:40:27.970> and<00:40:28.440> Guillaume<00:40:29.440> will<00:40:29.770> now 00:40:29.940 --> 00:40:29.950 align:start position:0% the verification and Guillaume will now 00:40:29.950 --> 00:40:36.870 align:start position:0% the verification and Guillaume will now talk<00:40:30.010> about<00:40:30.550> such<00:40:31.060> as 00:40:36.870 --> 00:40:36.880 align:start position:0% 00:40:36.880 --> 00:40:39.130 align:start position:0% well<00:40:37.880> thanks<00:40:38.119> for<00:40:38.270> Cena<00:40:38.570> but<00:40:38.720> he's<00:40:38.839> coming 00:40:39.130 --> 00:40:39.140 align:start position:0% well thanks for Cena but he's coming 00:40:39.140 --> 00:40:44.290 align:start position:0% well thanks for Cena but he's coming back<00:40:39.320> so<00:40:39.530> just<00:40:42.670> yeah<00:40:43.670> so<00:40:43.880> I<00:40:43.910> would<00:40:44.060> like<00:40:44.150> to 00:40:44.290 --> 00:40:44.300 align:start position:0% back so just yeah so I would like to 00:40:44.300 --> 00:40:46.030 align:start position:0% back so just yeah so I would like to talk<00:40:44.450> about<00:40:44.510> turbo<00:40:45.020> proof<00:40:45.230> that<00:40:45.410> so<00:40:45.680> that<00:40:45.859> used 00:40:46.030 --> 00:40:46.040 align:start position:0% talk about turbo proof that so that used 00:40:46.040 --> 00:40:47.579 align:start position:0% talk about turbo proof that so that used to<00:40:46.099> be<00:40:46.250> called<00:40:46.400> multi<00:40:46.760> proof<00:40:47.000> but<00:40:47.210> apparently 00:40:47.579 --> 00:40:47.589 align:start position:0% to be called multi proof but apparently 00:40:47.589 --> 00:40:49.930 align:start position:0% to be called multi proof but apparently everybody<00:40:48.589> started<00:40:49.070> calling<00:40:49.520> their<00:40:49.820> own 00:40:49.930 --> 00:40:49.940 align:start position:0% everybody started calling their own 00:40:49.940 --> 00:40:52.450 align:start position:0% everybody started calling their own skeeball<00:40:50.330> T<00:40:50.510> proof<00:40:50.720> so<00:40:50.869> I<00:40:50.930> had<00:40:51.349> actually<00:40:52.099> seen 00:40:52.450 --> 00:40:52.460 align:start position:0% skeeball T proof so I had actually seen 00:40:52.460 --> 00:40:55.270 align:start position:0% skeeball T proof so I had actually seen I<00:40:52.580> came<00:40:52.760> up<00:40:52.910> with<00:40:52.940> a<00:40:53.089> new<00:40:53.270> scheme<00:40:53.540> name<00:40:54.099> so<00:40:55.099> it 00:40:55.270 --> 00:40:55.280 align:start position:0% I came up with a new scheme name so it 00:40:55.280 --> 00:40:58.720 align:start position:0% I came up with a new scheme name so it has<00:40:55.460> been<00:40:55.640> invented<00:40:55.910> by<00:40:56.270> Alex<00:40:57.020> I<00:40:57.430> had<00:40:58.430> exact 00:40:58.720 --> 00:40:58.730 align:start position:0% has been invented by Alex I had exact 00:40:58.730 --> 00:41:03.450 align:start position:0% has been invented by Alex I had exact analysis<00:40:59.240> who<00:41:00.220> was<00:41:01.220> using<00:41:02.000> it<00:41:02.240> for<00:41:02.270> for<00:41:03.170> a 00:41:03.450 --> 00:41:03.460 align:start position:0% analysis who was using it for for a 00:41:03.460 --> 00:41:06.280 align:start position:0% analysis who was using it for for a night<00:41:04.460> clients<00:41:04.970> proposed<00:41:05.690> so<00:41:05.869> it's<00:41:06.020> really 00:41:06.280 --> 00:41:06.290 align:start position:0% night clients proposed so it's really 00:41:06.290 --> 00:41:09.070 align:start position:0% night clients proposed so it's really designed<00:41:06.440> to<00:41:06.800> to<00:41:07.490> make<00:41:07.990> rebuilding<00:41:08.990> the 00:41:09.070 --> 00:41:09.080 align:start position:0% designed to to make rebuilding the 00:41:09.080 --> 00:41:12.160 align:start position:0% designed to to make rebuilding the schrieffer<00:41:09.560> fast<00:41:10.040> and<00:41:10.450> we<00:41:11.450> want<00:41:11.720> to<00:41:11.839> use<00:41:11.990> it 00:41:12.160 --> 00:41:12.170 align:start position:0% schrieffer fast and we want to use it 00:41:12.170 --> 00:41:14.200 align:start position:0% schrieffer fast and we want to use it because<00:41:12.349> while<00:41:12.890> we're<00:41:13.040> interest<00:41:13.760> but<00:41:13.970> there 00:41:14.200 --> 00:41:14.210 align:start position:0% because while we're interest but there 00:41:14.210 --> 00:41:15.579 align:start position:0% because while we're interest but there are<00:41:14.300> several<00:41:14.480> reasons<00:41:14.630> why<00:41:15.020> we<00:41:15.200> want<00:41:15.349> to<00:41:15.440> use 00:41:15.579 --> 00:41:15.589 align:start position:0% are several reasons why we want to use 00:41:15.589 --> 00:41:17.890 align:start position:0% are several reasons why we want to use it<00:41:15.740> is<00:41:15.890> really<00:41:16.070> pal<00:41:16.369> to<00:41:17.089> the<00:41:17.330> eighth<00:41:17.540> one 00:41:17.890 --> 00:41:17.900 align:start position:0% it is really pal to the eighth one 00:41:17.900 --> 00:41:22.570 align:start position:0% it is really pal to the eighth one miracle<00:41:18.770> but<00:41:19.099> Patricia<00:41:19.640> tree<00:41:20.109> and<00:41:21.109> also<00:41:21.580> we 00:41:22.570 --> 00:41:22.580 align:start position:0% miracle but Patricia tree and also we 00:41:22.580 --> 00:41:24.930 align:start position:0% miracle but Patricia tree and also we since<00:41:23.030> there's<00:41:23.240> going<00:41:23.420> to<00:41:23.510> be<00:41:23.630> an<00:41:23.930> S<00:41:24.170> one<00:41:24.410> he 00:41:24.930 --> 00:41:24.940 align:start position:0% since there's going to be an S one he 00:41:24.940 --> 00:41:29.079 align:start position:0% since there's going to be an S one he integrated<00:41:25.940> and<00:41:26.330> in<00:41:27.109> eighth<00:41:27.440> tube<00:41:27.770> we<00:41:28.700> we 00:41:29.079 --> 00:41:29.089 align:start position:0% integrated and in eighth tube we we 00:41:29.089 --> 00:41:31.359 align:start position:0% integrated and in eighth tube we we figured<00:41:29.420> it<00:41:29.780> would<00:41:29.960> make<00:41:30.140> sense<00:41:30.320> to<00:41:30.440> to<00:41:30.890> study 00:41:31.359 --> 00:41:31.369 align:start position:0% figured it would make sense to to study 00:41:31.369 --> 00:41:32.829 align:start position:0% figured it would make sense to to study that<00:41:31.550> so<00:41:31.730> there<00:41:31.849> are<00:41:31.910> three<00:41:32.089> implementations 00:41:32.829 --> 00:41:32.839 align:start position:0% that so there are three implementations 00:41:32.839 --> 00:41:35.140 align:start position:0% that so there are three implementations the<00:41:32.990> first<00:41:33.230> one<00:41:33.440> is<00:41:33.650> described<00:41:34.490> by<00:41:34.670> Alexei 00:41:35.140 --> 00:41:35.150 align:start position:0% the first one is described by Alexei 00:41:35.150 --> 00:41:38.980 align:start position:0% the first one is described by Alexei himself<00:41:36.190> the<00:41:37.190> other<00:41:37.310> two<00:41:37.580> are<00:41:38.060> the<00:41:38.119> ones<00:41:38.300> seen 00:41:38.980 --> 00:41:38.990 align:start position:0% himself the other two are the ones seen 00:41:38.990 --> 00:41:41.980 align:start position:0% himself the other two are the ones seen and<00:41:39.230> I<00:41:39.320> wrote<00:41:39.619> in<00:41:39.890> typescript<00:41:40.490> and<00:41:40.880> rust<00:41:41.240> and 00:41:41.980 --> 00:41:41.990 align:start position:0% and I wrote in typescript and rust and 00:41:41.990 --> 00:41:44.200 align:start position:0% and I wrote in typescript and rust and yeah<00:41:42.770> I'm<00:41:42.830> going<00:41:43.010> to<00:41:43.160> explain<00:41:43.490> how<00:41:43.550> the<00:41:43.730> later 00:41:44.200 --> 00:41:44.210 align:start position:0% yeah I'm going to explain how the later 00:41:44.210 --> 00:41:46.870 align:start position:0% yeah I'm going to explain how the later latter<00:41:44.690> to<00:41:44.990> work<00:41:45.640> yes 00:41:46.870 --> 00:41:46.880 align:start position:0% latter to work yes 00:41:46.880 --> 00:41:49.390 align:start position:0% latter to work yes so<00:41:47.300> we<00:41:47.660> start<00:41:48.080> with<00:41:48.680> the<00:41:48.800> tree<00:41:49.040> sources 00:41:49.390 --> 00:41:49.400 align:start position:0% so we start with the tree sources 00:41:49.400 --> 00:41:54.490 align:start position:0% so we start with the tree sources century<00:41:49.900> and<00:41:51.369> we<00:41:52.369> want<00:41:52.820> imagine<00:41:53.420> you<00:41:54.050> want<00:41:54.290> to 00:41:54.490 --> 00:41:54.500 align:start position:0% century and we want imagine you want to 00:41:54.500 --> 00:41:57.190 align:start position:0% century and we want imagine you want to make<00:41:55.040> the<00:41:55.160> proof<00:41:55.430> that<00:41:55.820> you<00:41:56.270> know<00:41:56.480> the<00:41:56.839> values 00:41:57.190 --> 00:41:57.200 align:start position:0% make the proof that you know the values 00:41:57.200 --> 00:41:59.620 align:start position:0% make the proof that you know the values of<00:41:57.410> those<00:41:57.560> two<00:41:57.800> those<00:41:58.099> two<00:41:58.130> leaves<00:41:58.599> so<00:41:59.599> you 00:41:59.620 --> 00:41:59.630 align:start position:0% of those two those two leaves so you 00:41:59.630 --> 00:42:02.920 align:start position:0% of those two those two leaves so you start<00:41:59.960> by<00:42:00.890> selecting<00:42:01.130> the<00:42:01.520> notes<00:42:01.880> so<00:42:02.480> you<00:42:02.540> if 00:42:02.920 --> 00:42:02.930 align:start position:0% start by selecting the notes so you if 00:42:02.930 --> 00:42:05.079 align:start position:0% start by selecting the notes so you if you<00:42:03.109> want<00:42:03.290> those<00:42:03.440> to<00:42:03.619> know<00:42:03.770> those<00:42:04.369> two<00:42:04.550> leaves 00:42:05.079 --> 00:42:05.089 align:start position:0% you want those to know those two leaves 00:42:05.089 --> 00:42:07.300 align:start position:0% you want those to know those two leaves you<00:42:05.359> this<00:42:05.750> is<00:42:05.960> in<00:42:06.320> write<00:42:06.560> the<00:42:06.710> path<00:42:06.950> that<00:42:07.190> you 00:42:07.300 --> 00:42:07.310 align:start position:0% you this is in write the path that you 00:42:07.310 --> 00:42:09.099 align:start position:0% you this is in write the path that you will<00:42:07.460> have<00:42:07.580> to<00:42:07.730> travel<00:42:08.000> which<00:42:08.599> means<00:42:08.900> that 00:42:09.099 --> 00:42:09.109 align:start position:0% will have to travel which means that 00:42:09.109 --> 00:42:10.960 align:start position:0% will have to travel which means that everything<00:42:09.410> that<00:42:09.560> is<00:42:09.710> left<00:42:10.010> will<00:42:10.640> be<00:42:10.670> hashed 00:42:10.960 --> 00:42:10.970 align:start position:0% everything that is left will be hashed 00:42:10.970 --> 00:42:14.349 align:start position:0% everything that is left will be hashed so<00:42:11.869> this<00:42:12.050> is<00:42:12.260> roughly<00:42:12.800> the<00:42:13.040> the<00:42:13.880> tree<00:42:14.150> that 00:42:14.349 --> 00:42:14.359 align:start position:0% so this is roughly the the tree that 00:42:14.359 --> 00:42:16.839 align:start position:0% so this is roughly the the tree that you're<00:42:14.510> going<00:42:14.750> to<00:42:14.960> send<00:42:15.470> over<00:42:15.589> and<00:42:15.920> then<00:42:16.520> you 00:42:16.839 --> 00:42:16.849 align:start position:0% you're going to send over and then you 00:42:16.849 --> 00:42:19.660 align:start position:0% you're going to send over and then you just<00:42:17.150> get<00:42:17.390> all<00:42:17.690> the<00:42:17.839> notes<00:42:18.020> and<00:42:18.320> you<00:42:18.520> put<00:42:19.520> them 00:42:19.660 --> 00:42:19.670 align:start position:0% just get all the notes and you put them 00:42:19.670 --> 00:42:22.609 align:start position:0% just get all the notes and you put them in<00:42:19.880> your<00:42:19.970> desk<00:42:20.270> first 00:42:22.609 --> 00:42:22.619 align:start position:0% 00:42:22.619 --> 00:42:26.099 align:start position:0% order<00:42:23.619> so<00:42:24.100> you<00:42:25.000> don't<00:42:25.210> actually<00:42:25.359> need<00:42:25.780> to 00:42:26.099 --> 00:42:26.109 align:start position:0% order so you don't actually need to 00:42:26.109 --> 00:42:28.710 align:start position:0% order so you don't actually need to store<00:42:26.680> the<00:42:26.980> two<00:42:27.220> full<00:42:27.640> notes<00:42:27.880> here<00:42:28.210> but 00:42:28.710 --> 00:42:28.720 align:start position:0% store the two full notes here but 00:42:28.720 --> 00:42:30.810 align:start position:0% store the two full notes here but they're<00:42:28.930> they're<00:42:29.200> here<00:42:29.440> to<00:42:29.619> help<00:42:29.820> understand 00:42:30.810 --> 00:42:30.820 align:start position:0% they're they're here to help understand 00:42:30.820 --> 00:42:36.140 align:start position:0% they're they're here to help understand the<00:42:31.810> the<00:42:32.050> representation<00:42:33.660> then<00:42:34.660> Alex<00:42:35.440> started 00:42:36.140 --> 00:42:36.150 align:start position:0% the the representation then Alex started 00:42:36.150 --> 00:42:39.359 align:start position:0% the the representation then Alex started using<00:42:37.150> wanted<00:42:38.140> to<00:42:38.260> use<00:42:38.440> a<00:42:38.470> some<00:42:39.100> kind<00:42:39.310> of 00:42:39.359 --> 00:42:39.369 align:start position:0% using wanted to use a some kind of 00:42:39.369 --> 00:42:41.700 align:start position:0% using wanted to use a some kind of virtual<00:42:39.880> machine<00:42:40.270> to<00:42:40.869> start<00:42:41.109> reconstructing 00:42:41.700 --> 00:42:41.710 align:start position:0% virtual machine to start reconstructing 00:42:41.710 --> 00:42:43.380 align:start position:0% virtual machine to start reconstructing the<00:42:41.800> proof<00:42:42.010> so<00:42:42.220> basically<00:42:42.850> the<00:42:43.030> preferred 00:42:43.380 --> 00:42:43.390 align:start position:0% the proof so basically the preferred 00:42:43.390 --> 00:42:45.900 align:start position:0% the proof so basically the preferred construction<00:42:44.020> like<00:42:44.230> how<00:42:44.470> the<00:42:45.310> instruction<00:42:45.790> on 00:42:45.900 --> 00:42:45.910 align:start position:0% construction like how the instruction on 00:42:45.910 --> 00:42:48.810 align:start position:0% construction like how the instruction on how<00:42:45.970> to<00:42:46.180> rebuild<00:42:46.510> a<00:42:46.660> tree<00:42:46.900> is<00:42:47.380> used<00:42:47.800> it<00:42:48.640> is 00:42:48.810 --> 00:42:48.820 align:start position:0% how to rebuild a tree is used it is 00:42:48.820 --> 00:42:51.780 align:start position:0% how to rebuild a tree is used it is encoded<00:42:49.570> as<00:42:49.660> a<00:42:49.720> program<00:42:50.230> so<00:42:50.830> relief<00:42:51.160> means<00:42:51.580> you 00:42:51.780 --> 00:42:51.790 align:start position:0% encoded as a program so relief means you 00:42:51.790 --> 00:42:54.270 align:start position:0% encoded as a program so relief means you have<00:42:52.000> a<00:42:52.030> list<00:42:52.300> of<00:42:52.480> leaves<00:42:52.720> you<00:42:53.200> pick<00:42:53.500> the<00:42:53.770> the 00:42:54.270 --> 00:42:54.280 align:start position:0% have a list of leaves you pick the the 00:42:54.280 --> 00:42:56.849 align:start position:0% have a list of leaves you pick the the leaf<00:42:54.490> at<00:42:54.790> the<00:42:54.940> top<00:42:55.180> of<00:42:55.330> that<00:42:55.480> list<00:42:55.859> extension 00:42:56.849 --> 00:42:56.859 align:start position:0% leaf at the top of that list extension 00:42:56.859 --> 00:42:58.680 align:start position:0% leaf at the top of that list extension it<00:42:57.040> just<00:42:57.369> means<00:42:57.550> you<00:42:57.730> take<00:42:57.940> whatever's<00:42:58.359> on<00:42:58.540> the 00:42:58.680 --> 00:42:58.690 align:start position:0% it just means you take whatever's on the 00:42:58.690 --> 00:43:01.710 align:start position:0% it just means you take whatever's on the stack<00:42:58.990> and<00:42:59.320> you<00:43:00.220> add<00:43:00.490> it<00:43:00.609> as<00:43:00.760> a<00:43:00.790> node<00:43:01.119> as<00:43:01.450> you 00:43:01.710 --> 00:43:01.720 align:start position:0% stack and you add it as a node as you 00:43:01.720 --> 00:43:05.580 align:start position:0% stack and you add it as a node as you saw<00:43:01.930> of<00:43:02.830> that<00:43:02.890> extension<00:43:03.430> branch<00:43:04.240> and<00:43:04.600> add<00:43:04.780> do 00:43:05.580 --> 00:43:05.590 align:start position:0% saw of that extension branch and add do 00:43:05.590 --> 00:43:07.260 align:start position:0% saw of that extension branch and add do the<00:43:05.710> same<00:43:05.920> thing<00:43:06.160> the<00:43:06.340> bridge<00:43:06.580> actually 00:43:07.260 --> 00:43:07.270 align:start position:0% the same thing the bridge actually 00:43:07.270 --> 00:43:10.080 align:start position:0% the same thing the bridge actually creates<00:43:07.960> the<00:43:08.140> wrench<00:43:08.380> node<00:43:08.619> and<00:43:08.920> add<00:43:09.490> just 00:43:10.080 --> 00:43:10.090 align:start position:0% creates the wrench node and add just 00:43:10.090 --> 00:43:12.930 align:start position:0% creates the wrench node and add just says<00:43:10.740> you<00:43:11.740> have<00:43:11.920> a<00:43:11.950> rational<00:43:12.280> on<00:43:12.550> the<00:43:12.700> stack 00:43:12.930 --> 00:43:12.940 align:start position:0% says you have a rational on the stack 00:43:12.940 --> 00:43:16.080 align:start position:0% says you have a rational on the stack you<00:43:12.970> have<00:43:13.180> a<00:43:14.280> another<00:43:15.280> node<00:43:15.550> on<00:43:15.700> the<00:43:15.730> stack<00:43:16.060> so 00:43:16.080 --> 00:43:16.090 align:start position:0% you have a another node on the stack so 00:43:16.090 --> 00:43:17.460 align:start position:0% you have a another node on the stack so you<00:43:16.240> have<00:43:16.390> at<00:43:16.480> least<00:43:16.600> two<00:43:16.780> nodes<00:43:16.990> on<00:43:17.109> the<00:43:17.230> stack 00:43:17.460 --> 00:43:17.470 align:start position:0% you have at least two nodes on the stack 00:43:17.470 --> 00:43:19.920 align:start position:0% you have at least two nodes on the stack and<00:43:17.740> you<00:43:18.100> make<00:43:18.340> the<00:43:18.580> the<00:43:18.910> child<00:43:19.270> node<00:43:19.510> the 00:43:19.920 --> 00:43:19.930 align:start position:0% and you make the the child node the 00:43:19.930 --> 00:43:23.940 align:start position:0% and you make the the child node the parent<00:43:20.320> of<00:43:20.640> the<00:43:21.640> child<00:43:21.670> of<00:43:22.359> this<00:43:22.720> of<00:43:23.440> this 00:43:23.940 --> 00:43:23.950 align:start position:0% parent of the child of this of this 00:43:23.950 --> 00:43:26.490 align:start position:0% parent of the child of this of this previous<00:43:24.580> branch<00:43:24.850> node<00:43:25.090> and<00:43:26.080> finding<00:43:26.410> your 00:43:26.490 --> 00:43:26.500 align:start position:0% previous branch node and finding your 00:43:26.500 --> 00:43:29.010 align:start position:0% previous branch node and finding your hash<00:43:26.740> there's<00:43:27.340> also<00:43:27.490> a<00:43:27.640> list<00:43:27.850> of<00:43:28.060> hashes<00:43:28.240> so 00:43:29.010 --> 00:43:29.020 align:start position:0% hash there's also a list of hashes so 00:43:29.020 --> 00:43:30.540 align:start position:0% hash there's also a list of hashes so you<00:43:29.080> grab<00:43:29.440> it<00:43:29.619> says<00:43:29.830> you<00:43:29.950> brought<00:43:30.130> the<00:43:30.310> first 00:43:30.540 --> 00:43:30.550 align:start position:0% you grab it says you brought the first 00:43:30.550 --> 00:43:32.609 align:start position:0% you grab it says you brought the first hash<00:43:30.730> in<00:43:30.940> that<00:43:31.090> list<00:43:31.270> available<00:43:32.230> in<00:43:32.290> that<00:43:32.410> list 00:43:32.609 --> 00:43:32.619 align:start position:0% hash in that list available in that list 00:43:32.619 --> 00:43:35.880 align:start position:0% hash in that list available in that list and<00:43:32.800> you<00:43:33.160> put<00:43:33.340> it<00:43:33.430> on<00:43:33.550> the<00:43:33.670> stack<00:43:34.560> so<00:43:35.560> I'm<00:43:35.680> going 00:43:35.880 --> 00:43:35.890 align:start position:0% and you put it on the stack so I'm going 00:43:35.890 --> 00:43:38.940 align:start position:0% and you put it on the stack so I'm going to<00:43:35.950> run<00:43:36.369> through<00:43:36.609> a<00:43:36.730> program<00:43:37.480> so<00:43:37.720> this<00:43:38.170> is<00:43:38.380> the 00:43:38.940 --> 00:43:38.950 align:start position:0% to run through a program so this is the 00:43:38.950 --> 00:43:42.680 align:start position:0% to run through a program so this is the program<00:43:39.160> that<00:43:39.550> includes<00:43:40.000> the<00:43:41.070> double 00:43:42.680 --> 00:43:42.690 align:start position:0% program that includes the double 00:43:42.690 --> 00:43:45.930 align:start position:0% program that includes the double structure<00:43:43.690> information<00:43:43.960> so<00:43:44.859> you<00:43:44.920> start<00:43:45.340> here 00:43:45.930 --> 00:43:45.940 align:start position:0% structure information so you start here 00:43:45.940 --> 00:43:47.400 align:start position:0% structure information so you start here you<00:43:45.970> have<00:43:46.180> this<00:43:46.300> type<00:43:46.570> right<00:43:46.900> now<00:43:47.020> it's<00:43:47.170> empty 00:43:47.400 --> 00:43:47.410 align:start position:0% you have this type right now it's empty 00:43:47.410 --> 00:43:49.500 align:start position:0% you have this type right now it's empty you<00:43:47.500> have<00:43:47.619> the<00:43:47.830> list<00:43:48.040> of<00:43:48.160> hashes<00:43:48.340> and<00:43:48.760> you<00:43:49.300> have 00:43:49.500 --> 00:43:49.510 align:start position:0% you have the list of hashes and you have 00:43:49.510 --> 00:43:52.590 align:start position:0% you have the list of hashes and you have the<00:43:49.990> list<00:43:50.170> of<00:43:50.290> nodes<00:43:50.530> and<00:43:50.820> so<00:43:51.820> what<00:43:52.000> you<00:43:52.150> do<00:43:52.359> is 00:43:52.590 --> 00:43:52.600 align:start position:0% the list of nodes and so what you do is 00:43:52.600 --> 00:43:54.090 align:start position:0% the list of nodes and so what you do is you<00:43:52.990> start<00:43:53.230> with<00:43:53.440> the<00:43:53.560> first<00:43:53.710> instruction 00:43:54.090 --> 00:43:54.100 align:start position:0% you start with the first instruction 00:43:54.100 --> 00:43:57.500 align:start position:0% you start with the first instruction it's<00:43:54.490> a<00:43:54.609> leaf<00:43:54.820> you<00:43:55.240> put<00:43:55.840> it<00:43:55.930> on<00:43:56.050> the<00:43:56.200> stack 00:43:57.500 --> 00:43:57.510 align:start position:0% it's a leaf you put it on the stack 00:43:57.510 --> 00:43:59.820 align:start position:0% it's a leaf you put it on the stack another<00:43:58.510> leaf<00:43:58.780> so<00:43:59.140> now<00:43:59.260> you<00:43:59.320> have<00:43:59.500> two<00:43:59.650> leaves 00:43:59.820 --> 00:43:59.830 align:start position:0% another leaf so now you have two leaves 00:43:59.830 --> 00:44:01.109 align:start position:0% another leaf so now you have two leaves on<00:43:59.980> the<00:44:00.070> stack<00:44:00.310> or<00:44:00.520> by<00:44:00.670> the<00:44:00.730> way<00:44:00.880> I<00:44:00.910> should<00:44:01.000> have 00:44:01.109 --> 00:44:01.119 align:start position:0% on the stack or by the way I should have 00:44:01.119 --> 00:44:02.910 align:start position:0% on the stack or by the way I should have specified<00:44:01.420> to<00:44:01.930> the<00:44:02.020> stack<00:44:02.290> grows<00:44:02.320> in<00:44:02.740> that 00:44:02.910 --> 00:44:02.920 align:start position:0% specified to the stack grows in that 00:44:02.920 --> 00:44:05.330 align:start position:0% specified to the stack grows in that direction 00:44:05.330 --> 00:44:05.340 align:start position:0% 00:44:05.340 --> 00:44:08.210 align:start position:0% then<00:44:05.820> the<00:44:05.940> next<00:44:06.320> instruction<00:44:07.320> is<00:44:07.380> a<00:44:07.440> branch<00:44:07.530> to 00:44:08.210 --> 00:44:08.220 align:start position:0% then the next instruction is a branch to 00:44:08.220 --> 00:44:11.120 align:start position:0% then the next instruction is a branch to grab<00:44:08.750> the<00:44:09.750> branch<00:44:09.990> node<00:44:10.320> and<00:44:10.620> you<00:44:10.650> take<00:44:10.980> the 00:44:11.120 --> 00:44:11.130 align:start position:0% grab the branch node and you take the 00:44:11.130 --> 00:44:13.940 align:start position:0% grab the branch node and you take the leaf<00:44:11.700> there<00:44:11.910> was<00:44:12.030> first<00:44:12.330> on<00:44:12.480> the<00:44:12.600> stack<00:44:12.950> and 00:44:13.940 --> 00:44:13.950 align:start position:0% leaf there was first on the stack and 00:44:13.950 --> 00:44:17.870 align:start position:0% leaf there was first on the stack and you<00:44:13.980> may<00:44:14.220> make<00:44:14.580> it<00:44:14.730> a<00:44:15.060> child<00:44:15.740> and<00:44:16.740> then<00:44:17.460> after 00:44:17.870 --> 00:44:17.880 align:start position:0% you may make it a child and then after 00:44:17.880 --> 00:44:19.910 align:start position:0% you may make it a child and then after that<00:44:18.030> there's<00:44:18.270> an<00:44:18.360> added<00:44:18.810> so<00:44:19.080> the<00:44:19.350> Hat<00:44:19.560> takes 00:44:19.910 --> 00:44:19.920 align:start position:0% that there's an added so the Hat takes 00:44:19.920 --> 00:44:23.690 align:start position:0% that there's an added so the Hat takes the<00:44:20.220> the<00:44:21.030> branch<00:44:21.330> plus<00:44:21.630> child<00:44:21.990> and<00:44:22.700> another 00:44:23.690 --> 00:44:23.700 align:start position:0% the the branch plus child and another 00:44:23.700 --> 00:44:25.550 align:start position:0% the the branch plus child and another node<00:44:23.970> is<00:44:24.420> going<00:44:24.570> to<00:44:24.780> make<00:44:24.930> that<00:44:25.050> note<00:44:25.320> the 00:44:25.550 --> 00:44:25.560 align:start position:0% node is going to make that note the 00:44:25.560 --> 00:44:28.280 align:start position:0% node is going to make that note the child<00:44:26.130> of<00:44:26.340> of<00:44:26.970> the<00:44:27.150> top<00:44:27.330> node<00:44:27.600> so<00:44:27.960> that's<00:44:28.140> what 00:44:28.280 --> 00:44:28.290 align:start position:0% child of of the top node so that's what 00:44:28.290 --> 00:44:29.630 align:start position:0% child of of the top node so that's what you<00:44:28.410> get 00:44:29.630 --> 00:44:29.640 align:start position:0% you get 00:44:29.640 --> 00:44:30.890 align:start position:0% you get yeah<00:44:29.970> there's<00:44:30.180> a<00:44:30.240> beautiful<00:44:30.450> squiggle<00:44:30.870> here 00:44:30.890 --> 00:44:30.900 align:start position:0% yeah there's a beautiful squiggle here 00:44:30.900 --> 00:44:35.150 align:start position:0% yeah there's a beautiful squiggle here but<00:44:31.290> yeah<00:44:31.860> that's<00:44:32.090> generated<00:44:33.590> then<00:44:34.590> there's 00:44:35.150 --> 00:44:35.160 align:start position:0% but yeah that's generated then there's 00:44:35.160 --> 00:44:36.860 align:start position:0% but yeah that's generated then there's an<00:44:35.280> extension<00:44:35.610> note<00:44:35.940> here<00:44:36.240> and<00:44:36.420> an<00:44:36.510> extension 00:44:36.860 --> 00:44:36.870 align:start position:0% an extension note here and an extension 00:44:36.870 --> 00:44:40.720 align:start position:0% an extension note here and an extension instruction<00:44:37.650> so<00:44:38.160> this<00:44:38.340> is<00:44:38.520> what<00:44:39.120> happens<00:44:39.510> and 00:44:40.720 --> 00:44:40.730 align:start position:0% instruction so this is what happens and 00:44:40.730 --> 00:44:43.700 align:start position:0% instruction so this is what happens and finally<00:44:41.730> well<00:44:42.030> finding<00:44:42.390> there's<00:44:42.630> a<00:44:42.720> branch<00:44:42.990> so 00:44:43.700 --> 00:44:43.710 align:start position:0% finally well finding there's a branch so 00:44:43.710 --> 00:44:45.950 align:start position:0% finally well finding there's a branch so you<00:44:43.800> create<00:44:44.190> the<00:44:44.760> branch<00:44:44.970> like<00:44:45.150> this<00:44:45.330> and<00:44:45.600> at 00:44:45.950 --> 00:44:45.960 align:start position:0% you create the branch like this and at 00:44:45.960 --> 00:44:47.720 align:start position:0% you create the branch like this and at this<00:44:46.110> point<00:44:46.350> you<00:44:46.560> the<00:44:46.950> next<00:44:47.130> instruction<00:44:47.640> is 00:44:47.720 --> 00:44:47.730 align:start position:0% this point you the next instruction is 00:44:47.730 --> 00:44:50.120 align:start position:0% this point you the next instruction is hash<00:44:48.000> so<00:44:48.540> you're<00:44:48.690> going<00:44:48.900> to<00:44:48.930> take<00:44:49.230> the<00:44:49.890> hash 00:44:50.120 --> 00:44:50.130 align:start position:0% hash so you're going to take the hash 00:44:50.130 --> 00:44:53.240 align:start position:0% hash so you're going to take the hash from<00:44:50.370> the<00:44:50.550> list<00:44:50.730> of<00:44:50.820> hashes<00:44:51.030> and<00:44:52.010> put<00:44:53.010> it<00:44:53.130> on 00:44:53.240 --> 00:44:53.250 align:start position:0% from the list of hashes and put it on 00:44:53.250 --> 00:44:55.250 align:start position:0% from the list of hashes and put it on the<00:44:53.370> stand<00:44:53.610> so<00:44:53.760> it's<00:44:53.970> in<00:44:54.150> the<00:44:54.270> planet<00:44:54.570> at<00:44:55.110> the 00:44:55.250 --> 00:44:55.260 align:start position:0% the stand so it's in the planet at the 00:44:55.260 --> 00:44:58.400 align:start position:0% the stand so it's in the planet at the moment<00:44:55.290> and<00:44:55.830> then<00:44:56.670> finally<00:44:57.270> you<00:44:57.600> perform<00:44:58.260> the 00:44:58.400 --> 00:44:58.410 align:start position:0% moment and then finally you perform the 00:44:58.410 --> 00:45:00.860 align:start position:0% moment and then finally you perform the last<00:44:58.770> instruction<00:44:59.370> which<00:44:59.520> is<00:44:59.670> the<00:44:59.820> add<00:44:59.970> and<00:45:00.720> it 00:45:00.860 --> 00:45:00.870 align:start position:0% last instruction which is the add and it 00:45:00.870 --> 00:45:03.800 align:start position:0% last instruction which is the add and it adds<00:45:01.050> the<00:45:01.980> hash<00:45:02.190> to<00:45:02.430> -<00:45:02.820> and<00:45:03.510> by<00:45:03.660> the<00:45:03.690> way 00:45:03.800 --> 00:45:03.810 align:start position:0% adds the hash to - and by the way 00:45:03.810 --> 00:45:05.330 align:start position:0% adds the hash to - and by the way there's<00:45:04.080> another<00:45:04.170> mistake<00:45:04.740> here<00:45:04.980> it<00:45:05.160> should 00:45:05.330 --> 00:45:05.340 align:start position:0% there's another mistake here it should 00:45:05.340 --> 00:45:09.290 align:start position:0% there's another mistake here it should be<00:45:05.400> Dino<00:45:05.760> see<00:45:06.180> that<00:45:06.600> the<00:45:06.750> hashes<00:45:07.110> come<00:45:07.260> from 00:45:09.290 --> 00:45:09.300 align:start position:0% be Dino see that the hashes come from 00:45:09.300 --> 00:45:13.370 align:start position:0% be Dino see that the hashes come from yes<00:45:09.810> so<00:45:10.080> it's<00:45:11.330> pretty<00:45:12.330> simple<00:45:12.630> relatively 00:45:13.370 --> 00:45:13.380 align:start position:0% yes so it's pretty simple relatively 00:45:13.380 --> 00:45:16.790 align:start position:0% yes so it's pretty simple relatively simple<00:45:14.090> it<00:45:15.090> has<00:45:15.240> a<00:45:15.270> lot<00:45:15.480> of<00:45:15.510> inefficiency<00:45:16.440> that 00:45:16.790 --> 00:45:16.800 align:start position:0% simple it has a lot of inefficiency that 00:45:16.800 --> 00:45:20.030 align:start position:0% simple it has a lot of inefficiency that you<00:45:17.040> get<00:45:17.460> inherited<00:45:17.990> from<00:45:18.990> from<00:45:19.590> the<00:45:19.740> vertical 00:45:20.030 --> 00:45:20.040 align:start position:0% you get inherited from from the vertical 00:45:20.040 --> 00:45:20.510 align:start position:0% you get inherited from from the vertical position 00:45:20.510 --> 00:45:20.520 align:start position:0% position 00:45:20.520 --> 00:45:23.570 align:start position:0% position petruchio<00:45:21.000> tree<00:45:21.240> it<00:45:21.720> chooses<00:45:22.080> our<00:45:22.320> LP<00:45:22.710> it's 00:45:23.570 --> 00:45:23.580 align:start position:0% petruchio tree it chooses our LP it's 00:45:23.580 --> 00:45:25.910 align:start position:0% petruchio tree it chooses our LP it's nipple<00:45:24.060> base<00:45:24.270> so<00:45:24.690> that<00:45:24.720> makes<00:45:25.290> a<00:45:25.500> lot<00:45:25.740> of 00:45:25.910 --> 00:45:25.920 align:start position:0% nipple base so that makes a lot of 00:45:25.920 --> 00:45:27.990 align:start position:0% nipple base so that makes a lot of unnecessary<00:45:26.250> copies<00:45:27.060> of<00:45:27.270> other<00:45:27.390> than<00:45:27.630> this 00:45:27.990 --> 00:45:28.000 align:start position:0% unnecessary copies of other than this 00:45:28.000 --> 00:45:31.410 align:start position:0% unnecessary copies of other than this very<00:45:28.800> braixen<00:45:29.800> in<00:45:30.040> Turkey<00:45:30.400> there's<00:45:31.360> a 00:45:31.410 --> 00:45:31.420 align:start position:0% very braixen in Turkey there's a 00:45:31.420 --> 00:45:34.440 align:start position:0% very braixen in Turkey there's a write-up<00:45:31.810> that<00:45:32.440> is<00:45:32.680> really<00:45:33.040> that<00:45:34.030> is<00:45:34.150> almost 00:45:34.440 --> 00:45:34.450 align:start position:0% write-up that is really that is almost 00:45:34.450 --> 00:45:37.020 align:start position:0% write-up that is really that is almost ready<00:45:34.750> and<00:45:35.080> it's<00:45:35.340> collecting<00:45:36.340> feedback<00:45:36.550> that 00:45:37.020 --> 00:45:37.030 align:start position:0% ready and it's collecting feedback that 00:45:37.030 --> 00:45:40.560 align:start position:0% ready and it's collecting feedback that we<00:45:37.180> need<00:45:37.270> to<00:45:37.360> publish<00:45:37.690> soon<00:45:38.020> and<00:45:38.700> yes<00:45:39.700> so<00:45:40.330> far 00:45:40.560 --> 00:45:40.570 align:start position:0% we need to publish soon and yes so far 00:45:40.570 --> 00:45:45.330 align:start position:0% we need to publish soon and yes so far to<00:45:40.780> serialize<00:45:41.620> the<00:45:41.800> proof<00:45:42.300> we<00:45:43.300> use<00:45:43.450> our<00:45:43.690> LP<00:45:44.340> as 00:45:45.330 --> 00:45:45.340 align:start position:0% to serialize the proof we use our LP as 00:45:45.340 --> 00:45:48.450 align:start position:0% to serialize the proof we use our LP as proto<00:45:46.060> mentor<00:45:46.450> who's<00:45:46.860> working<00:45:47.860> on<00:45:47.950> the<00:45:48.100> better 00:45:48.450 --> 00:45:48.460 align:start position:0% proto mentor who's working on the better 00:45:48.460 --> 00:45:51.180 align:start position:0% proto mentor who's working on the better way<00:45:48.730> to<00:45:48.790> encode<00:45:49.360> the<00:45:49.870> same<00:45:50.080> tree<00:45:50.350> without<00:45:51.040> the 00:45:51.180 --> 00:45:51.190 align:start position:0% way to encode the same tree without the 00:45:51.190 --> 00:45:52.680 align:start position:0% way to encode the same tree without the structural<00:45:51.550> information<00:45:51.850> so<00:45:52.300> there's<00:45:52.510> some 00:45:52.680 --> 00:45:52.690 align:start position:0% structural information so there's some 00:45:52.690 --> 00:45:54.060 align:start position:0% structural information so there's some work<00:45:52.900> here<00:45:53.170> in<00:45:53.320> that<00:45:53.440> direction<00:45:53.590> that's 00:45:54.060 --> 00:45:54.070 align:start position:0% work here in that direction that's 00:45:54.070 --> 00:45:55.890 align:start position:0% work here in that direction that's really<00:45:54.340> twisting<00:45:54.820> and<00:45:55.030> that<00:45:55.240> encourage<00:45:55.720> you 00:45:55.890 --> 00:45:55.900 align:start position:0% really twisting and that encourage you 00:45:55.900 --> 00:45:57.960 align:start position:0% really twisting and that encourage you to<00:45:56.110> to<00:45:56.770> look<00:45:56.890> at<00:45:57.100> when<00:45:57.370> it's<00:45:57.550> when<00:45:57.940> it's 00:45:57.960 --> 00:45:57.970 align:start position:0% to to look at when it's when it's 00:45:57.970 --> 00:46:01.590 align:start position:0% to to look at when it's when it's published<00:45:58.620> and<00:45:59.620> was<00:45:59.920> this<00:46:00.330> seniors<00:46:01.330> gonna 00:46:01.590 --> 00:46:01.600 align:start position:0% published and was this seniors gonna 00:46:01.600 --> 00:46:03.720 align:start position:0% published and was this seniors gonna tell<00:46:01.840> us<00:46:01.960> what<00:46:02.350> to<00:46:02.590> do<00:46:02.770> with<00:46:03.220> this 00:46:03.720 --> 00:46:03.730 align:start position:0% tell us what to do with this 00:46:03.730 --> 00:46:15.390 align:start position:0% tell us what to do with this turbo<00:46:04.060> proof<00:46:11.700> so<00:46:13.740> now<00:46:14.740> that<00:46:14.800> we've<00:46:15.100> seen<00:46:15.340> how 00:46:15.390 --> 00:46:15.400 align:start position:0% turbo proof so now that we've seen how 00:46:15.400 --> 00:46:19.350 align:start position:0% turbo proof so now that we've seen how to<00:46:15.760> improve<00:46:16.240> words<00:46:16.660> we<00:46:16.870> can<00:46:17.280> go<00:46:18.280> to<00:46:18.340> our<00:46:18.520> latest 00:46:19.350 --> 00:46:19.360 align:start position:0% to improve words we can go to our latest 00:46:19.360 --> 00:46:24.120 align:start position:0% to improve words we can go to our latest prototype<00:46:20.610> which<00:46:21.610> was<00:46:22.680> the<00:46:23.680> majority<00:46:23.920> of 00:46:24.120 --> 00:46:24.130 align:start position:0% prototype which was the majority of 00:46:24.130 --> 00:46:26.370 align:start position:0% prototype which was the majority of which<00:46:24.340> was<00:46:24.550> implemented<00:46:25.150> by<00:46:25.180> virginity<00:46:26.080> in 00:46:26.370 --> 00:46:26.380 align:start position:0% which was implemented by virginity in 00:46:26.380 --> 00:46:30.060 align:start position:0% which was implemented by virginity in assembly<00:46:26.920> script<00:46:28.050> this<00:46:29.050> is<00:46:29.230> the<00:46:29.440> language 00:46:30.060 --> 00:46:30.070 align:start position:0% assembly script this is the language 00:46:30.070 --> 00:46:32.430 align:start position:0% assembly script this is the language that<00:46:30.310> looks<00:46:30.670> like<00:46:30.880> typescript<00:46:31.450> but<00:46:31.750> it's 00:46:32.430 --> 00:46:32.440 align:start position:0% that looks like typescript but it's 00:46:32.440 --> 00:46:34.280 align:start position:0% that looks like typescript but it's solely<00:46:32.680> different<00:46:33.160> and<00:46:33.340> it<00:46:33.400> complies<00:46:33.760> to 00:46:34.280 --> 00:46:34.290 align:start position:0% solely different and it complies to 00:46:34.290 --> 00:46:38.760 align:start position:0% solely different and it complies to working<00:46:35.370> so<00:46:36.370> children<00:46:37.360> has<00:46:37.570> a<00:46:38.170> bunch<00:46:38.590> of 00:46:38.760 --> 00:46:38.770 align:start position:0% working so children has a bunch of 00:46:38.770 --> 00:46:41.280 align:start position:0% working so children has a bunch of differences<00:46:39.340> to<00:46:39.490> SMPTE<00:46:40.090> I<00:46:40.360> won't<00:46:40.660> go<00:46:40.810> into<00:46:41.110> all 00:46:41.280 --> 00:46:41.290 align:start position:0% differences to SMPTE I won't go into all 00:46:41.290 --> 00:46:45.720 align:start position:0% differences to SMPTE I won't go into all of<00:46:41.500> them<00:46:41.650> but<00:46:42.810> one<00:46:43.810> of<00:46:43.840> the<00:46:44.190> bigger<00:46:45.190> changes<00:46:45.370> is 00:46:45.720 --> 00:46:45.730 align:start position:0% of them but one of the bigger changes is 00:46:45.730 --> 00:46:48.780 align:start position:0% of them but one of the bigger changes is that<00:46:46.210> the<00:46:46.600> blog<00:46:46.840> title<00:46:47.260> is<00:46:47.380> different<00:46:48.250> it's 00:46:48.780 --> 00:46:48.790 align:start position:0% that the blog title is different it's 00:46:48.790 --> 00:46:50.790 align:start position:0% that the blog title is different it's not<00:46:48.910> only<00:46:49.210> a<00:46:49.600> list<00:46:49.780> of<00:46:49.900> transactions<00:46:50.440> anymore 00:46:50.790 --> 00:46:50.800 align:start position:0% not only a list of transactions anymore 00:46:50.800 --> 00:46:52.040 align:start position:0% not only a list of transactions anymore we<00:46:51.250> also<00:46:51.400> include<00:46:51.790> some<00:46:51.970> additional 00:46:52.040 --> 00:46:52.050 align:start position:0% we also include some additional 00:46:52.050 --> 00:46:55.560 align:start position:0% we also include some additional information<00:46:53.050> for<00:46:53.290> the<00:46:53.410> EE<00:46:53.620> and<00:46:54.100> we<00:46:55.090> sort<00:46:55.390> them 00:46:55.560 --> 00:46:55.570 align:start position:0% information for the EE and we sort them 00:46:55.570 --> 00:47:00.000 align:start position:0% information for the EE and we sort them in<00:46:55.780> a<00:46:55.930> way<00:46:56.310> so<00:46:57.310> that<00:46:57.340> the<00:46:57.640> EE<00:46:57.820> could<00:46:59.010> without 00:47:00.000 --> 00:47:00.010 align:start position:0% in a way so that the EE could without 00:47:00.010 --> 00:47:03.200 align:start position:0% in a way so that the EE could without many<00:47:00.520> memory<00:47:01.060> copy<00:47:01.360> without<00:47:01.960> many<00:47:02.350> lookups 00:47:03.200 --> 00:47:03.210 align:start position:0% many memory copy without many lookups 00:47:03.210 --> 00:47:06.900 align:start position:0% many memory copy without many lookups process<00:47:04.210> the<00:47:04.360> transactions<00:47:05.050> and<00:47:05.980> I<00:47:06.490> won't<00:47:06.760> go 00:47:06.900 --> 00:47:06.910 align:start position:0% process the transactions and I won't go 00:47:06.910 --> 00:47:10.950 align:start position:0% process the transactions and I won't go into<00:47:07.090> details<00:47:07.630> here<00:47:07.780> but<00:47:08.010> you<00:47:09.010> can<00:47:09.220> see<00:47:09.960> how 00:47:10.950 --> 00:47:10.960 align:start position:0% into details here but you can see how 00:47:10.960 --> 00:47:11.910 align:start position:0% into details here but you can see how the<00:47:11.020> party 00:47:11.910 --> 00:47:11.920 align:start position:0% the party 00:47:11.920 --> 00:47:15.690 align:start position:0% the party looks<00:47:12.400> like<00:47:13.349> so<00:47:14.349> to<00:47:15.099> process<00:47:15.309> each 00:47:15.690 --> 00:47:15.700 align:start position:0% looks like so to process each 00:47:15.700 --> 00:47:19.200 align:start position:0% looks like so to process each transaction<00:47:16.240> we<00:47:17.079> recover<00:47:17.819> the<00:47:18.819> sender's 00:47:19.200 --> 00:47:19.210 align:start position:0% transaction we recover the sender's 00:47:19.210 --> 00:47:22.680 align:start position:0% transaction we recover the sender's address<00:47:19.480> from<00:47:20.140> the<00:47:20.319> signature<00:47:21.000> we<00:47:22.000> get<00:47:22.329> the 00:47:22.680 --> 00:47:22.690 align:start position:0% address from the signature we get the 00:47:22.690 --> 00:47:23.940 align:start position:0% address from the signature we get the accounts<00:47:23.170> for<00:47:23.289> the<00:47:23.410> sender<00:47:23.710> and<00:47:23.890> the 00:47:23.940 --> 00:47:23.950 align:start position:0% accounts for the sender and the 00:47:23.950 --> 00:47:27.150 align:start position:0% accounts for the sender and the recipient<00:47:24.660> with<00:47:25.660> just<00:47:25.960> a<00:47:26.079> simple<00:47:26.319> index<00:47:26.829> based 00:47:27.150 --> 00:47:27.160 align:start position:0% recipient with just a simple index based 00:47:27.160 --> 00:47:33.720 align:start position:0% recipient with just a simple index based look<00:47:27.579> up<00:47:27.789> from<00:47:28.089> an<00:47:28.210> array<00:47:31.559> technologies<00:47:32.730> and 00:47:33.720 --> 00:47:33.730 align:start position:0% look up from an array technologies and 00:47:33.730 --> 00:47:36.329 align:start position:0% look up from an array technologies and then<00:47:33.910> we<00:47:34.119> update<00:47:34.420> the<00:47:34.750> account<00:47:35.130> the<00:47:36.130> account 00:47:36.329 --> 00:47:36.339 align:start position:0% then we update the account the account 00:47:36.339 --> 00:47:38.579 align:start position:0% then we update the account the account objects<00:47:36.940> not<00:47:37.150> in<00:47:37.329> the<00:47:37.450> tree<00:47:37.690> but<00:47:38.049> just<00:47:38.380> the 00:47:38.579 --> 00:47:38.589 align:start position:0% objects not in the tree but just the 00:47:38.589 --> 00:47:40.980 align:start position:0% objects not in the tree but just the account<00:47:38.920> object<00:47:39.430> itself<00:47:40.000> and<00:47:40.240> then<00:47:40.630> partly 00:47:40.980 --> 00:47:40.990 align:start position:0% account object itself and then partly 00:47:40.990 --> 00:47:43.460 align:start position:0% account object itself and then partly encoded<00:47:41.589> and<00:47:42.279> then<00:47:42.579> you<00:47:42.700> might<00:47:42.910> notice<00:47:43.299> that 00:47:43.460 --> 00:47:43.470 align:start position:0% encoded and then you might notice that 00:47:43.470 --> 00:47:46.049 align:start position:0% encoded and then you might notice that one<00:47:44.470> of<00:47:44.589> the<00:47:44.680> differences<00:47:44.859> here<00:47:45.400> is<00:47:45.579> that<00:47:45.760> we 00:47:46.049 --> 00:47:46.059 align:start position:0% one of the differences here is that we 00:47:46.059 --> 00:47:48.329 align:start position:0% one of the differences here is that we are<00:47:46.180> not<00:47:46.390> doing<00:47:47.109> the<00:47:47.410> proof<00:47:47.680> verification 00:47:48.329 --> 00:47:48.339 align:start position:0% are not doing the proof verification 00:47:48.339 --> 00:47:51.359 align:start position:0% are not doing the proof verification here<00:47:48.539> that<00:47:49.539> we<00:47:49.750> are<00:47:49.839> doing<00:47:49.960> afterwards<00:47:50.920> so 00:47:51.359 --> 00:47:51.369 align:start position:0% here that we are doing afterwards so 00:47:51.369 --> 00:47:52.769 align:start position:0% here that we are doing afterwards so after<00:47:51.730> every<00:47:52.000> transaction<00:47:52.329> has<00:47:52.599> been 00:47:52.769 --> 00:47:52.779 align:start position:0% after every transaction has been 00:47:52.779 --> 00:47:58.200 align:start position:0% after every transaction has been processed<00:47:53.910> we<00:47:54.910> hash<00:47:55.539> of<00:47:55.869> the<00:47:56.670> addresses<00:47:57.670> to 00:47:58.200 --> 00:47:58.210 align:start position:0% processed we hash of the addresses to 00:47:58.210 --> 00:48:03.480 align:start position:0% processed we hash of the addresses to get<00:47:58.539> the<00:47:59.079> list<00:47:59.319> of<00:47:59.880> three<00:48:00.880> keys<00:48:01.619> and<00:48:02.619> then<00:48:02.829> in<00:48:03.279> a 00:48:03.480 --> 00:48:03.490 align:start position:0% get the list of three keys and then in a 00:48:03.490 --> 00:48:08.549 align:start position:0% get the list of three keys and then in a single<00:48:03.849> pass<00:48:05.220> we<00:48:06.220> do<00:48:06.369> a<00:48:06.400> couple<00:48:06.819> of<00:48:06.880> things<00:48:07.559> as 00:48:08.549 --> 00:48:08.559 align:start position:0% single pass we do a couple of things as 00:48:08.559 --> 00:48:11.130 align:start position:0% single pass we do a couple of things as we<00:48:09.339> are<00:48:09.369> rebuilding<00:48:09.970> the<00:48:10.240> tree<00:48:10.480> similar<00:48:10.930> to 00:48:11.130 --> 00:48:11.140 align:start position:0% we are rebuilding the tree similar to 00:48:11.140 --> 00:48:16.220 align:start position:0% we are rebuilding the tree similar to how<00:48:11.319> how<00:48:11.650> to<00:48:11.710> you<00:48:11.950> explained<00:48:12.720> we<00:48:14.279> hash<00:48:15.279> the 00:48:16.220 --> 00:48:16.230 align:start position:0% how how to you explained we hash the 00:48:16.230 --> 00:48:20.009 align:start position:0% how how to you explained we hash the existing<00:48:17.230> leaves<00:48:17.910> to<00:48:18.910> compute<00:48:19.420> the<00:48:19.569> pre<00:48:19.779> state 00:48:20.009 --> 00:48:20.019 align:start position:0% existing leaves to compute the pre state 00:48:20.019 --> 00:48:22.559 align:start position:0% existing leaves to compute the pre state route<00:48:20.259> at<00:48:20.500> the<00:48:21.160> same<00:48:21.400> time<00:48:21.730> in<00:48:22.269> a<00:48:22.420> different 00:48:22.559 --> 00:48:22.569 align:start position:0% route at the same time in a different 00:48:22.569 --> 00:48:26.700 align:start position:0% route at the same time in a different sack<00:48:23.079> we<00:48:23.789> hashed<00:48:24.869> updated<00:48:25.869> accounts<00:48:26.380> to<00:48:26.559> get 00:48:26.700 --> 00:48:26.710 align:start position:0% sack we hashed updated accounts to get 00:48:26.710 --> 00:48:30.720 align:start position:0% sack we hashed updated accounts to get the<00:48:26.920> co-state<00:48:27.519> route<00:48:28.049> and<00:48:29.549> additionally<00:48:30.549> we 00:48:30.720 --> 00:48:30.730 align:start position:0% the co-state route and additionally we 00:48:30.730 --> 00:48:33.990 align:start position:0% the co-state route and additionally we also<00:48:31.140> reconstruct<00:48:32.140> the<00:48:32.410> paths<00:48:32.769> of<00:48:33.069> each<00:48:33.789> of 00:48:33.990 --> 00:48:34.000 align:start position:0% also reconstruct the paths of each of 00:48:34.000 --> 00:48:40.049 align:start position:0% also reconstruct the paths of each of these<00:48:34.180> leaves<00:48:35.309> to<00:48:36.309> get<00:48:36.539> to<00:48:37.539> get<00:48:37.890> the<00:48:38.890> keys<00:48:39.519> for 00:48:40.049 --> 00:48:40.059 align:start position:0% these leaves to get to get the keys for 00:48:40.059 --> 00:48:42.569 align:start position:0% these leaves to get to get the keys for those<00:48:40.240> leaves<00:48:40.589> we<00:48:41.589> want<00:48:41.799> to<00:48:41.920> do<00:48:42.099> this<00:48:42.250> because 00:48:42.569 --> 00:48:42.579 align:start position:0% those leaves we want to do this because 00:48:42.579 --> 00:48:45.870 align:start position:0% those leaves we want to do this because otherwise<00:48:43.029> I<00:48:44.009> could<00:48:45.009> send<00:48:45.220> a<00:48:45.279> transaction 00:48:45.870 --> 00:48:45.880 align:start position:0% otherwise I could send a transaction 00:48:45.880 --> 00:48:48.059 align:start position:0% otherwise I could send a transaction with<00:48:46.059> my<00:48:46.210> own<00:48:46.420> address<00:48:46.960> but<00:48:47.650> then<00:48:47.799> in<00:48:47.980> the 00:48:48.059 --> 00:48:48.069 align:start position:0% with my own address but then in the 00:48:48.069 --> 00:48:50.670 align:start position:0% with my own address but then in the motive<00:48:48.460> proof<00:48:48.759> include<00:48:49.630> with<00:48:50.019> Alex<00:48:50.319> account 00:48:50.670 --> 00:48:50.680 align:start position:0% motive proof include with Alex account 00:48:50.680 --> 00:48:52.710 align:start position:0% motive proof include with Alex account which<00:48:50.890> has<00:48:50.920> much<00:48:51.220> more<00:48:51.400> teeth<00:48:51.549> than<00:48:51.579> me<00:48:51.910> so 00:48:52.710 --> 00:48:52.720 align:start position:0% which has much more teeth than me so 00:48:52.720 --> 00:48:56.220 align:start position:0% which has much more teeth than me so this<00:48:53.529> is<00:48:53.680> crucial<00:48:53.890> and<00:48:54.700> notice<00:48:55.660> yet<00:48:55.930> again 00:48:56.220 --> 00:48:56.230 align:start position:0% this is crucial and notice yet again 00:48:56.230 --> 00:48:58.470 align:start position:0% this is crucial and notice yet again this<00:48:56.589> is<00:48:56.740> done<00:48:57.009> in<00:48:57.190> a<00:48:57.250> single<00:48:57.579> pass<00:48:57.759> and<00:48:58.000> this 00:48:58.470 --> 00:48:58.480 align:start position:0% this is done in a single pass and this 00:48:58.480 --> 00:49:02.609 align:start position:0% this is done in a single pass and this wasn't<00:48:58.690> hired<00:48:59.019> by<00:48:59.289> Paul<00:48:59.619> Anka<00:48:59.950> so<00:49:00.250> from<00:49:01.619> then 00:49:02.609 --> 00:49:02.619 align:start position:0% wasn't hired by Paul Anka so from then 00:49:02.619 --> 00:49:06.569 align:start position:0% wasn't hired by Paul Anka so from then as<00:49:02.920> you<00:49:03.670> saw<00:49:04.380> signature<00:49:05.380> verification<00:49:05.549> was<00:49:06.549> a 00:49:06.569 --> 00:49:06.579 align:start position:0% as you saw signature verification was a 00:49:06.579 --> 00:49:09.029 align:start position:0% as you saw signature verification was a major<00:49:07.029> bottleneck<00:49:07.329> in<00:49:07.839> SMPT<00:49:08.470> which<00:49:08.859> was 00:49:09.029 --> 00:49:09.039 align:start position:0% major bottleneck in SMPT which was 00:49:09.039 --> 00:49:12.029 align:start position:0% major bottleneck in SMPT which was taking<00:49:09.430> four<00:49:09.730> out<00:49:09.940> of<00:49:09.970> five<00:49:10.509> seconds<00:49:11.049> so<00:49:11.980> to 00:49:12.029 --> 00:49:12.039 align:start position:0% taking four out of five seconds so to 00:49:12.039 --> 00:49:19.049 align:start position:0% taking four out of five seconds so to remedy<00:49:12.609> that<00:49:13.680> Casey<00:49:14.680> took<00:49:16.859> beps<00:49:17.859> mark<00:49:18.220> which 00:49:19.049 --> 00:49:19.059 align:start position:0% remedy that Casey took beps mark which 00:49:19.059 --> 00:49:22.950 align:start position:0% remedy that Casey took beps mark which is<00:49:19.470> a<00:49:20.470> library<00:49:21.130> of<00:49:21.160> optimized<00:49:22.089> wasn't<00:49:22.660> code 00:49:22.950 --> 00:49:22.960 align:start position:0% is a library of optimized wasn't code 00:49:22.960 --> 00:49:26.279 align:start position:0% is a library of optimized wasn't code for<00:49:23.609> elliptic<00:49:24.609> curve<00:49:25.000> and<00:49:25.329> snark<00:49:25.779> primitives 00:49:26.279 --> 00:49:26.289 align:start position:0% for elliptic curve and snark primitives 00:49:26.289 --> 00:49:31.650 align:start position:0% for elliptic curve and snark primitives he<00:49:27.039> adapted<00:49:27.519> it<00:49:27.670> to<00:49:27.700> the<00:49:28.660> SEC<00:49:28.930> P<00:49:29.230> 256<00:49:29.950> K<00:49:30.519> 1<00:49:30.759> curve 00:49:31.650 --> 00:49:31.660 align:start position:0% he adapted it to the SEC P 256 K 1 curve 00:49:31.660 --> 00:49:35.390 align:start position:0% he adapted it to the SEC P 256 K 1 curve which<00:49:32.259> is<00:49:32.500> what<00:49:32.769> users<00:49:33.359> he<00:49:34.359> also<00:49:34.630> replaced<00:49:35.049> the 00:49:35.390 --> 00:49:35.400 align:start position:0% which is what users he also replaced the 00:49:35.400 --> 00:49:38.579 align:start position:0% which is what users he also replaced the the<00:49:36.400> big<00:49:37.059> number<00:49:37.390> thematics<00:49:37.900> with<00:49:38.109> the<00:49:38.230> bignum 00:49:38.579 --> 00:49:38.589 align:start position:0% the big number thematics with the bignum 00:49:38.589 --> 00:49:43.829 align:start position:0% the big number thematics with the bignum api<00:49:38.920> and<00:49:40.559> this<00:49:41.559> all<00:49:41.890> resulted<00:49:42.490> in<00:49:42.700> a<00:49:42.819> major 00:49:43.829 --> 00:49:43.839 align:start position:0% api and this all resulted in a major 00:49:43.839 --> 00:49:47.579 align:start position:0% api and this all resulted in a major runtime<00:49:44.670> improvement<00:49:46.170> another<00:49:47.170> thing<00:49:47.410> that 00:49:47.579 --> 00:49:47.589 align:start position:0% runtime improvement another thing that 00:49:47.589 --> 00:49:50.940 align:start position:0% runtime improvement another thing that we<00:49:47.710> do<00:49:47.859> is<00:49:48.190> optimize<00:49:49.000> all<00:49:49.839> P<00:49:50.259> encoding<00:49:50.769> and 00:49:50.940 --> 00:49:50.950 align:start position:0% we do is optimize all P encoding and 00:49:50.950 --> 00:49:55.410 align:start position:0% we do is optimize all P encoding and decoding<00:49:51.900> and<00:49:52.900> so<00:49:53.680> we<00:49:53.940> instead<00:49:54.940> of<00:49:55.059> having<00:49:55.210> a 00:49:55.410 --> 00:49:55.420 align:start position:0% decoding and so we instead of having a 00:49:55.420 --> 00:49:59.900 align:start position:0% decoding and so we instead of having a generic<00:49:56.640> encode<00:49:57.640> and<00:49:57.910> decode<00:49:58.619> we<00:49:59.619> have 00:49:59.900 --> 00:49:59.910 align:start position:0% generic encode and decode we have 00:49:59.910 --> 00:50:02.460 align:start position:0% generic encode and decode we have specific<00:50:00.910> encoders<00:50:01.390> and<00:50:01.450> decoders<00:50:01.630> for<00:50:02.140> every 00:50:02.460 --> 00:50:02.470 align:start position:0% specific encoders and decoders for every 00:50:02.470 --> 00:50:04.829 align:start position:0% specific encoders and decoders for every data<00:50:02.710> structure<00:50:03.220> this<00:50:04.000> is<00:50:04.180> because<00:50:04.539> for 00:50:04.829 --> 00:50:04.839 align:start position:0% data structure this is because for 00:50:04.839 --> 00:50:06.990 align:start position:0% data structure this is because for example<00:50:05.529> for<00:50:05.710> a<00:50:05.740> branch<00:50:06.009> node<00:50:06.220> we<00:50:06.490> know<00:50:06.700> how 00:50:06.990 --> 00:50:07.000 align:start position:0% example for a branch node we know how 00:50:07.000 --> 00:50:08.460 align:start position:0% example for a branch node we know how it's<00:50:07.180> going<00:50:07.359> to<00:50:07.480> look<00:50:07.630> like<00:50:07.839> we<00:50:08.319> have<00:50:08.440> much 00:50:08.460 --> 00:50:08.470 align:start position:0% it's going to look like we have much 00:50:08.470 --> 00:50:11.430 align:start position:0% it's going to look like we have much more<00:50:08.859> information<00:50:09.059> so<00:50:10.059> we<00:50:10.299> can<00:50:10.509> encode<00:50:11.259> or 00:50:11.430 --> 00:50:11.440 align:start position:0% more information so we can encode or 00:50:11.440 --> 00:50:14.730 align:start position:0% more information so we can encode or decode<00:50:11.470> with<00:50:12.430> a<00:50:12.460> lot<00:50:12.700> less<00:50:13.140> memory<00:50:14.140> copies<00:50:14.559> or 00:50:14.730 --> 00:50:14.740 align:start position:0% decode with a lot less memory copies or 00:50:14.740 --> 00:50:20.130 align:start position:0% decode with a lot less memory copies or overheads<00:50:16.200> and<00:50:17.490> to<00:50:18.490> evaluate<00:50:19.210> we<00:50:19.750> took<00:50:19.930> the 00:50:20.130 --> 00:50:20.140 align:start position:0% overheads and to evaluate we took the 00:50:20.140 --> 00:50:24.240 align:start position:0% overheads and to evaluate we took the same<00:50:20.470> test<00:50:21.039> case<00:50:21.369> so<00:50:21.970> 5000<00:50:22.690> accounts<00:50:23.250> 70 00:50:24.240 --> 00:50:24.250 align:start position:0% same test case so 5000 accounts 70 00:50:24.250 --> 00:50:27.269 align:start position:0% same test case so 5000 accounts 70 transactions<00:50:24.910> and<00:50:25.210> here<00:50:26.079> are<00:50:26.410> the<00:50:26.650> results<00:50:27.160> we 00:50:27.269 --> 00:50:27.279 align:start position:0% transactions and here are the results we 00:50:27.279 --> 00:50:30.420 align:start position:0% transactions and here are the results we got<00:50:27.460> so<00:50:27.880> in<00:50:28.150> SPT<00:50:28.750> as<00:50:28.960> you<00:50:29.140> remember<00:50:29.559> that<00:50:30.250> the 00:50:30.420 --> 00:50:30.430 align:start position:0% got so in SPT as you remember that the 00:50:30.430 --> 00:50:34.680 align:start position:0% got so in SPT as you remember that the block<00:50:30.670> size<00:50:30.940> was<00:50:31.680> 235<00:50:32.680> kilobytes<00:50:33.369> and<00:50:33.690> in 00:50:34.680 --> 00:50:34.690 align:start position:0% block size was 235 kilobytes and in 00:50:34.690 --> 00:50:38.190 align:start position:0% block size was 235 kilobytes and in turbo<00:50:34.990> token<00:50:35.349> that's<00:50:35.559> 50<00:50:36.099> kilobytes<00:50:36.430> and<00:50:37.200> for 00:50:38.190 --> 00:50:38.200 align:start position:0% turbo token that's 50 kilobytes and for 00:50:38.200 --> 00:50:43.349 align:start position:0% turbo token that's 50 kilobytes and for runtime<00:50:38.430> in<00:50:39.430> was<00:50:39.789> B<00:50:40.059> we<00:50:40.329> had<00:50:40.569> 5<00:50:41.440> seconds<00:50:42.359> for 00:50:43.349 --> 00:50:43.359 align:start position:0% runtime in was B we had 5 seconds for 00:50:43.359 --> 00:50:47.099 align:start position:0% runtime in was B we had 5 seconds for for<00:50:43.630> 2<00:50:43.779> more<00:50:43.960> token<00:50:44.289> we<00:50:44.559> ran<00:50:45.069> the<00:50:46.109> optimized 00:50:47.099 --> 00:50:47.109 align:start position:0% for 2 more token we ran the optimized 00:50:47.109 --> 00:50:52.620 align:start position:0% for 2 more token we ran the optimized rabbit<00:50:47.740> and<00:50:49.380> it<00:50:50.380> took<00:50:50.710> a<00:50:51.430> hundred<00:50:51.759> 40 00:50:52.620 --> 00:50:52.630 align:start position:0% rabbit and it took a hundred 40 00:50:52.630 --> 00:50:55.980 align:start position:0% rabbit and it took a hundred 40 milliseconds<00:50:53.230> out<00:50:54.009> of<00:50:54.250> which<00:50:54.750> 105<00:50:55.750> minutes 00:50:55.980 --> 00:50:55.990 align:start position:0% milliseconds out of which 105 minutes 00:50:55.990 --> 00:50:58.559 align:start position:0% milliseconds out of which 105 minutes seconds<00:50:56.440> is<00:50:56.589> for<00:50:56.829> signature<00:50:57.339> verification<00:50:57.569> of 00:50:58.559 --> 00:50:58.569 align:start position:0% seconds is for signature verification of 00:50:58.569 --> 00:51:04.549 align:start position:0% seconds is for signature verification of KC<00:50:58.869> things<00:50:59.410> that<00:50:59.680> that<00:50:59.980> so<00:51:00.039> can<00:51:00.490> go<00:51:00.730> down<00:51:01.500> 3 00:51:04.549 --> 00:51:04.559 align:start position:0% 00:51:04.559 --> 00:51:06.829 align:start position:0% please<00:51:04.920> also<00:51:05.130> note<00:51:05.249> that<00:51:05.400> this<00:51:05.789> this<00:51:06.660> is<00:51:06.779> a 00:51:06.829 --> 00:51:06.839 align:start position:0% please also note that this this is a 00:51:06.839 --> 00:51:09.859 align:start position:0% please also note that this this is a lower<00:51:07.140> bound<00:51:07.400> because<00:51:08.400> currently<00:51:08.910> turbo 00:51:09.859 --> 00:51:09.869 align:start position:0% lower bound because currently turbo 00:51:09.869 --> 00:51:11.900 align:start position:0% lower bound because currently turbo token<00:51:10.170> is<00:51:10.319> only<00:51:10.619> limited<00:51:10.890> to<00:51:11.190> updating 00:51:11.900 --> 00:51:11.910 align:start position:0% token is only limited to updating 00:51:11.910 --> 00:51:15.049 align:start position:0% token is only limited to updating existing<00:51:12.630> leaves<00:51:13.259> it<00:51:13.589> doesn't<00:51:13.980> add<00:51:14.759> new 00:51:15.049 --> 00:51:15.059 align:start position:0% existing leaves it doesn't add new 00:51:15.059 --> 00:51:19.400 align:start position:0% existing leaves it doesn't add new accounts<00:51:15.569> to<00:51:15.660> try<00:51:16.049> or<00:51:17.359> remove<00:51:18.359> them<00:51:18.599> and<00:51:18.779> in 00:51:19.400 --> 00:51:19.410 align:start position:0% accounts to try or remove them and in 00:51:19.410 --> 00:51:22.430 align:start position:0% accounts to try or remove them and in order<00:51:19.499> to<00:51:19.710> do<00:51:19.920> that<00:51:20.069> the<00:51:20.339> marketing<00:51:21.440> adjust 00:51:22.430 --> 00:51:22.440 align:start position:0% order to do that the marketing adjust 00:51:22.440 --> 00:51:24.259 align:start position:0% order to do that the marketing adjust the<00:51:22.589> algorithm<00:51:23.130> which<00:51:23.309> will<00:51:23.460> incur<00:51:23.970> some 00:51:24.259 --> 00:51:24.269 align:start position:0% the algorithm which will incur some 00:51:24.269 --> 00:51:33.380 align:start position:0% the algorithm which will incur some overhead<00:51:26.240> so<00:51:27.240> so<00:51:27.930> what<00:51:28.109> we<00:51:28.259> saw<00:51:28.440> so<00:51:28.470> far 00:51:33.380 --> 00:51:33.390 align:start position:0% 00:51:33.390 --> 00:51:35.390 align:start position:0% all<00:51:34.109> right<00:51:34.259> so<00:51:34.529> I<00:51:34.559> guess<00:51:34.859> we<00:51:35.099> can<00:51:35.249> take 00:51:35.390 --> 00:51:35.400 align:start position:0% all right so I guess we can take 00:51:35.400 --> 00:51:40.910 align:start position:0% all right so I guess we can take questions<00:51:37.190> yes<00:51:38.599> so<00:51:39.599> he<00:51:39.720> looked<00:51:39.930> example<00:51:40.650> try 00:51:40.910 --> 00:51:40.920 align:start position:0% questions yes so he looked example try 00:51:40.920 --> 00:51:43.700 align:start position:0% questions yes so he looked example try it<00:51:41.220> was<00:51:41.400> a<00:51:41.690> trying<00:51:42.690> it<00:51:42.809> but<00:51:42.900> I'm<00:51:43.019> here<00:51:43.349> is<00:51:43.470> about 00:51:43.700 --> 00:51:43.710 align:start position:0% it was a trying it but I'm here is about 00:51:43.710 --> 00:51:46.970 align:start position:0% it was a trying it but I'm here is about being<00:51:44.009> back<00:51:45.140> was<00:51:46.140> that<00:51:46.349> the<00:51:46.470> line<00:51:46.650> on<00:51:46.859> the 00:51:46.970 --> 00:51:46.980 align:start position:0% being back was that the line on the 00:51:46.980 --> 00:51:49.460 align:start position:0% being back was that the line on the lines<00:51:47.190> of<00:51:47.279> the<00:51:47.339> large<00:51:47.609> try<00:51:48.359> or<00:51:49.140> didn't<00:51:49.380> know 00:51:49.460 --> 00:51:49.470 align:start position:0% lines of the large try or didn't know 00:51:49.470 --> 00:51:51.739 align:start position:0% lines of the large try or didn't know what<00:51:49.650> was<00:51:49.890> with<00:51:50.369> five<00:51:51.059> thousand<00:51:51.480> that<00:51:51.539> comes 00:51:51.739 --> 00:51:51.749 align:start position:0% what was with five thousand that comes 00:51:51.749 --> 00:51:54.499 align:start position:0% what was with five thousand that comes in<00:51:51.900> mistake<00:51:52.230> like<00:51:52.410> that<00:51:52.759> yeah<00:51:53.759> so<00:51:53.970> so<00:51:54.329> this<00:51:54.450> is 00:51:54.499 --> 00:51:54.509 align:start position:0% in mistake like that yeah so so this is 00:51:54.509 --> 00:51:59.029 align:start position:0% in mistake like that yeah so so this is yeah<00:51:54.960> this<00:51:54.990> is<00:51:55.589> a<00:51:56.539> pathological<00:51:57.539> as<00:51:58.349> Alexa 00:51:59.029 --> 00:51:59.039 align:start position:0% yeah this is a pathological as Alexa 00:51:59.039 --> 00:52:02.569 align:start position:0% yeah this is a pathological as Alexa called<00:51:59.630> example<00:52:00.630> it<00:52:01.559> doesn't<00:52:01.890> represent<00:52:02.009> a 00:52:02.569 --> 00:52:02.579 align:start position:0% called example it doesn't represent a 00:52:02.579 --> 00:52:05.239 align:start position:0% called example it doesn't represent a real<00:52:02.940> workload<00:52:03.569> that's<00:52:03.829> one<00:52:04.829> of<00:52:04.920> the<00:52:05.039> things 00:52:05.239 --> 00:52:05.249 align:start position:0% real workload that's one of the things 00:52:05.249 --> 00:52:09.019 align:start position:0% real workload that's one of the things that<00:52:05.369> we<00:52:05.490> want<00:52:05.640> to<00:52:05.670> do<00:52:05.880> as<00:52:06.269> a<00:52:06.329> next<00:52:06.509> step<00:52:06.779> but<00:52:08.029> it 00:52:09.019 --> 00:52:09.029 align:start position:0% that we want to do as a next step but it 00:52:09.029 --> 00:52:11.599 align:start position:0% that we want to do as a next step but it was<00:52:09.210> also<00:52:09.420> like<00:52:09.630> one<00:52:10.230> of<00:52:10.349> the<00:52:11.130> reasons<00:52:11.460> we 00:52:11.599 --> 00:52:11.609 align:start position:0% was also like one of the reasons we 00:52:11.609 --> 00:52:14.200 align:start position:0% was also like one of the reasons we chose<00:52:11.640> this<00:52:12.150> test<00:52:12.839> case<00:52:13.019> because<00:52:13.650> of<00:52:13.859> the 00:52:14.200 --> 00:52:14.210 align:start position:0% chose this test case because of the 00:52:14.210 --> 00:52:16.729 align:start position:0% chose this test case because of the constraints<00:52:15.210> that<00:52:15.269> we<00:52:15.420> have<00:52:15.779> or<00:52:15.989> we<00:52:16.380> think<00:52:16.559> we 00:52:16.729 --> 00:52:16.739 align:start position:0% constraints that we have or we think we 00:52:16.739 --> 00:52:20.210 align:start position:0% constraints that we have or we think we have<00:52:16.920> we<00:52:17.130> will<00:52:17.249> have<00:52:17.279> for<00:52:18.089> the<00:52:18.269> EE<00:52:18.480> is<00:52:19.220> around 00:52:20.210 --> 00:52:20.220 align:start position:0% have we will have for the EE is around 00:52:20.220 --> 00:52:22.759 align:start position:0% have we will have for the EE is around 50<00:52:20.670> kilobytes<00:52:21.059> of<00:52:21.450> data<00:52:21.779> in<00:52:22.170> the<00:52:22.319> block<00:52:22.529> size 00:52:22.759 --> 00:52:22.769 align:start position:0% 50 kilobytes of data in the block size 00:52:22.769 --> 00:52:25.789 align:start position:0% 50 kilobytes of data in the block size so<00:52:23.339> we<00:52:23.489> set<00:52:23.789> everything<00:52:23.999> up<00:52:24.509> so<00:52:24.569> that<00:52:24.900> the<00:52:25.619> data 00:52:25.789 --> 00:52:25.799 align:start position:0% so we set everything up so that the data 00:52:25.799 --> 00:52:29.829 align:start position:0% so we set everything up so that the data would<00:52:26.099> roughly<00:52:26.579> fit<00:52:26.940> in<00:52:27.569> 50<00:52:28.349> kilobytes<00:52:28.680> and 00:52:29.829 --> 00:52:29.839 align:start position:0% would roughly fit in 50 kilobytes and 00:52:29.839 --> 00:52:33.289 align:start position:0% would roughly fit in 50 kilobytes and and<00:52:30.839> for<00:52:31.559> run<00:52:31.710> time<00:52:31.950> it's<00:52:32.160> likely<00:52:32.940> going<00:52:32.970> to<00:52:33.210> be 00:52:33.289 --> 00:52:33.299 align:start position:0% and for run time it's likely going to be 00:52:33.299 --> 00:52:38.890 align:start position:0% and for run time it's likely going to be around<00:52:33.599> 100<00:52:34.049> milliseconds 00:52:38.890 --> 00:52:38.900 align:start position:0% 00:52:38.900 --> 00:52:41.500 align:start position:0% have<00:52:39.290> you<00:52:39.410> considered<00:52:39.770> or<00:52:40.180> recently<00:52:41.180> chance 00:52:41.500 --> 00:52:41.510 align:start position:0% have you considered or recently chance 00:52:41.510 --> 00:52:43.690 align:start position:0% have you considered or recently chance that<00:52:42.320> the<00:52:42.530> statement<00:52:42.980> said<00:52:43.130> of<00:52:43.280> being<00:52:43.460> in<00:52:43.580> a 00:52:43.690 --> 00:52:43.700 align:start position:0% that the statement said of being in a 00:52:43.700 --> 00:52:46.600 align:start position:0% that the statement said of being in a but<00:52:43.910> recently<00:52:44.360> we<00:52:44.630> sponsor<00:52:45.470> a<00:52:45.590> country 00:52:46.600 --> 00:52:46.610 align:start position:0% but recently we sponsor a country 00:52:46.610 --> 00:52:49.390 align:start position:0% but recently we sponsor a country yes<00:52:47.060> and<00:52:47.390> in<00:52:47.660> fact<00:52:47.870> we<00:52:48.020> will<00:52:48.350> see<00:52:48.590> that<00:52:48.740> very 00:52:49.390 --> 00:52:49.400 align:start position:0% yes and in fact we will see that very 00:52:49.400 --> 00:52:52.930 align:start position:0% yes and in fact we will see that very soon<00:52:50.000> in<00:52:50.240> the<00:52:50.360> next<00:52:50.660> talks<00:52:51.230> this<00:52:51.770> is<00:52:51.980> as<00:52:52.190> I<00:52:52.700> said 00:52:52.930 --> 00:52:52.940 align:start position:0% soon in the next talks this is as I said 00:52:52.940 --> 00:52:54.400 align:start position:0% soon in the next talks this is as I said like<00:52:53.150> one<00:52:53.390> of<00:52:53.480> the<00:52:53.600> major<00:52:53.750> constraints<00:52:54.380> that 00:52:54.400 --> 00:52:54.410 align:start position:0% like one of the major constraints that 00:52:54.410 --> 00:52:56.440 align:start position:0% like one of the major constraints that we<00:52:54.620> had<00:52:54.770> for<00:52:54.980> this<00:52:55.070> prototyping<00:52:55.790> is<00:52:56.180> that<00:52:56.330> we 00:52:56.440 --> 00:52:56.450 align:start position:0% we had for this prototyping is that we 00:52:56.450 --> 00:52:58.480 align:start position:0% we had for this prototyping is that we wanted<00:52:56.750> to<00:52:56.930> remain<00:52:57.350> compatible<00:52:57.860> with<00:52:58.280> this 00:52:58.480 --> 00:52:58.490 align:start position:0% wanted to remain compatible with this 00:52:58.490 --> 00:53:05.740 align:start position:0% wanted to remain compatible with this one<00:53:02.440> okay<00:53:03.440> if<00:53:03.740> there's<00:53:04.010> no<00:53:04.190> more<00:53:04.340> questions<00:53:04.750> so 00:53:05.740 --> 00:53:05.750 align:start position:0% one okay if there's no more questions so 00:53:05.750 --> 00:53:08.320 align:start position:0% one okay if there's no more questions so far<00:53:05.960> what<00:53:06.140> we<00:53:06.260> saw<00:53:06.500> was<00:53:06.770> just<00:53:07.520> this<00:53:08.090> one 00:53:08.320 --> 00:53:08.330 align:start position:0% far what we saw was just this one 00:53:08.330 --> 00:53:11.380 align:start position:0% far what we saw was just this one compatible<00:53:08.900> token<00:53:09.680> EE<00:53:09.890> but<00:53:10.790> of<00:53:11.000> course<00:53:11.210> we 00:53:11.380 --> 00:53:11.390 align:start position:0% compatible token EE but of course we 00:53:11.390 --> 00:53:14.730 align:start position:0% compatible token EE but of course we would<00:53:11.510> want<00:53:11.750> a<00:53:11.990> fully<00:53:12.500> fledged<00:53:12.890> eath<00:53:13.340> 1e<00:53:13.880> and 00:53:14.730 --> 00:53:14.740 align:start position:0% would want a fully fledged eath 1e and 00:53:14.740 --> 00:53:17.710 align:start position:0% would want a fully fledged eath 1e and for<00:53:15.740> that<00:53:15.830> purpose<00:53:16.130> among<00:53:16.970> other<00:53:17.210> things<00:53:17.300> we 00:53:17.710 --> 00:53:17.720 align:start position:0% for that purpose among other things we 00:53:17.720 --> 00:53:21.810 align:start position:0% for that purpose among other things we will<00:53:17.840> need<00:53:18.050> an<00:53:18.260> EVM<00:53:19.250> interpreter<00:53:19.970> in<00:53:20.510> yes<00:53:21.500> you 00:53:21.810 --> 00:53:21.820 align:start position:0% will need an EVM interpreter in yes you 00:53:21.820 --> 00:53:24.850 align:start position:0% will need an EVM interpreter in yes you have<00:53:22.820> like<00:53:23.150> can<00:53:23.780> happen<00:53:24.050> and<00:53:24.170> where<00:53:24.440> we<00:53:24.710> can 00:53:24.850 --> 00:53:24.860 align:start position:0% have like can happen and where we can 00:53:24.860 --> 00:53:28.000 align:start position:0% have like can happen and where we can find<00:53:25.100> us<00:53:26.500> yeah 00:53:28.000 --> 00:53:28.010 align:start position:0% find us yeah 00:53:28.010 --> 00:53:39.390 align:start position:0% find us yeah yeah<00:53:28.730> all<00:53:28.910> right<00:53:29.950> yeah<00:53:30.950> I<00:53:31.550> think<00:53:32.060> there<00:53:32.480> is 00:53:39.390 --> 00:53:39.400 align:start position:0% 00:53:39.400 --> 00:53:43.690 align:start position:0% yeah<00:53:40.450> so<00:53:41.450> this<00:53:41.960> is<00:53:42.170> too<00:53:42.350> much<00:53:42.470> okay<00:53:42.800> this<00:53:43.550> is 00:53:43.690 --> 00:53:43.700 align:start position:0% yeah so this is too much okay this is 00:53:43.700 --> 00:53:54.880 align:start position:0% yeah so this is too much okay this is the<00:53:43.910> wrost<00:53:44.600> implementation<00:53:45.350> of<00:53:52.660> okay<00:53:53.660> so<00:53:54.080> for 00:53:54.880 --> 00:53:54.890 align:start position:0% the wrost implementation of okay so for 00:53:54.890 --> 00:53:58.090 align:start position:0% the wrost implementation of okay so for for<00:53:55.340> for<00:53:55.850> the<00:53:55.940> EVM<00:53:56.300> interpreter<00:53:56.750> in<00:53:57.080> in<00:53:57.380> bottom 00:53:58.090 --> 00:53:58.100 align:start position:0% for for the EVM interpreter in in bottom 00:53:58.100 --> 00:54:25.430 align:start position:0% for for the EVM interpreter in in bottom I<00:53:58.820> invite<00:53:59.360> you 00:54:25.430 --> 00:54:25.440 align:start position:0% 00:54:25.440 --> 00:54:28.349 align:start position:0% I'm<00:54:26.440> going<00:54:26.650> to<00:54:26.739> talk<00:54:26.920> about<00:54:27.220> these<00:54:27.489> EBM 00:54:28.349 --> 00:54:28.359 align:start position:0% I'm going to talk about these EBM 00:54:28.359 --> 00:54:30.930 align:start position:0% I'm going to talk about these EBM interpreter<00:54:28.960> there<00:54:29.230> is<00:54:29.499> an<00:54:29.589> environment<00:54:29.940> it 00:54:30.930 --> 00:54:30.940 align:start position:0% interpreter there is an environment it 00:54:30.940 --> 00:54:39.089 align:start position:0% interpreter there is an environment it was<00:54:32.130> for<00:54:33.130> example<00:54:34.529> be<00:54:35.529> done<00:54:36.930> this<00:54:38.099> execution 00:54:39.089 --> 00:54:39.099 align:start position:0% was for example be done this execution 00:54:39.099 --> 00:54:40.589 align:start position:0% was for example be done this execution environment<00:54:39.609> is<00:54:39.759> written<00:54:40.029> in<00:54:40.210> us<00:54:40.329> on<00:54:40.509> the 00:54:40.589 --> 00:54:40.599 align:start position:0% environment is written in us on the 00:54:40.599 --> 00:54:44.759 align:start position:0% environment is written in us on the script<00:54:40.869> and<00:54:41.319> it<00:54:41.680> runs<00:54:41.950> on<00:54:42.279> the<00:54:43.769> transformer 00:54:44.759 --> 00:54:44.769 align:start position:0% script and it runs on the transformer 00:54:44.769 --> 00:54:48.299 align:start position:0% script and it runs on the transformer for<00:54:45.069> cover<00:54:45.339> of<00:54:45.940> scout<00:54:46.390> where<00:54:47.049> I<00:54:47.289> gathered<00:54:47.739> some 00:54:48.299 --> 00:54:48.309 align:start position:0% for cover of scout where I gathered some 00:54:48.309 --> 00:54:52.859 align:start position:0% for cover of scout where I gathered some more<00:54:49.119> cost<00:54:49.630> functions<00:54:50.170> in<00:54:50.410> order<00:54:50.559> to<00:54:51.869> process 00:54:52.859 --> 00:54:52.869 align:start position:0% more cost functions in order to process 00:54:52.869 --> 00:54:57.509 align:start position:0% more cost functions in order to process some<00:54:53.140> of<00:54:53.259> the<00:54:53.410> opcodes<00:54:55.230> the<00:54:56.230> way<00:54:56.410> it<00:54:56.470> works<00:54:56.799> it 00:54:57.509 --> 00:54:57.519 align:start position:0% some of the opcodes the way it works it 00:54:57.519 --> 00:55:01.680 align:start position:0% some of the opcodes the way it works it defines<00:54:57.940> an<00:54:58.269> IBM<00:54:58.660> stock<00:55:00.059> in<00:55:01.059> the<00:55:01.299> wasn't 00:55:01.680 --> 00:55:01.690 align:start position:0% defines an IBM stock in the wasn't 00:55:01.690 --> 00:55:04.559 align:start position:0% defines an IBM stock in the wasn't memory<00:55:02.009> where<00:55:03.009> each<00:55:03.339> element<00:55:03.759> in<00:55:04.210> the<00:55:04.239> spike 00:55:04.559 --> 00:55:04.569 align:start position:0% memory where each element in the spike 00:55:04.569 --> 00:55:10.410 align:start position:0% memory where each element in the spike is<00:55:04.720> a<00:55:05.220> 256-bit<00:55:07.980> element<00:55:08.980> so<00:55:09.249> it<00:55:10.089> is<00:55:10.210> basically 00:55:10.410 --> 00:55:10.420 align:start position:0% is a 256-bit element so it is basically 00:55:10.420 --> 00:55:11.099 align:start position:0% is a 256-bit element so it is basically the<00:55:10.660> same 00:55:11.099 --> 00:55:11.109 align:start position:0% the same 00:55:11.109 --> 00:55:16.220 align:start position:0% the same IBM<00:55:11.650> one<00:55:11.920> also<00:55:12.910> defines<00:55:13.450> an<00:55:13.809> IBM<00:55:14.319> memory<00:55:14.650> and 00:55:16.220 --> 00:55:16.230 align:start position:0% IBM one also defines an IBM memory and 00:55:16.230 --> 00:55:20.819 align:start position:0% IBM one also defines an IBM memory and later<00:55:17.230> it<00:55:17.680> calls<00:55:18.009> these<00:55:18.430> two<00:55:19.259> cost<00:55:20.259> functions 00:55:20.819 --> 00:55:20.829 align:start position:0% later it calls these two cost functions 00:55:20.829 --> 00:55:24.059 align:start position:0% later it calls these two cost functions to<00:55:21.489> tell<00:55:21.700> the<00:55:21.880> Scout<00:55:22.150> in<00:55:22.900> which<00:55:23.200> part<00:55:23.559> of<00:55:23.829> the 00:55:24.059 --> 00:55:24.069 align:start position:0% to tell the Scout in which part of the 00:55:24.069 --> 00:55:28.559 align:start position:0% to tell the Scout in which part of the wasum<00:55:24.670> memory<00:55:25.230> this<00:55:26.230> tag<00:55:26.789> DVM<00:55:27.789> star<00:55:28.089> candy<00:55:28.390> via 00:55:28.559 --> 00:55:28.569 align:start position:0% wasum memory this tag DVM star candy via 00:55:28.569 --> 00:55:34.950 align:start position:0% wasum memory this tag DVM star candy via memory<00:55:29.289> exists<00:55:32.069> then<00:55:33.069> it<00:55:33.309> gets<00:55:33.670> the<00:55:33.940> IBM<00:55:34.569> 5 00:55:34.950 --> 00:55:34.960 align:start position:0% memory exists then it gets the IBM 5 00:55:34.960 --> 00:55:37.499 align:start position:0% memory exists then it gets the IBM 5 code<00:55:35.230> and<00:55:35.589> the<00:55:36.009> input<00:55:36.400> data<00:55:36.609> directly<00:55:37.420> from 00:55:37.499 --> 00:55:37.509 align:start position:0% code and the input data directly from 00:55:37.509 --> 00:55:45.660 align:start position:0% code and the input data directly from the<00:55:37.989> from<00:55:38.920> the<00:55:39.130> raw<00:55:39.910> data<00:55:43.380> and<00:55:44.380> once<00:55:45.279> we<00:55:45.489> have 00:55:45.660 --> 00:55:45.670 align:start position:0% the from the raw data and once we have 00:55:45.670 --> 00:55:48.660 align:start position:0% the from the raw data and once we have the<00:55:45.819> IBM<00:55:46.359> bytecode<00:55:46.839> interests<00:55:47.680> interests<00:55:48.460> the 00:55:48.660 --> 00:55:48.670 align:start position:0% the IBM bytecode interests interests the 00:55:48.670 --> 00:55:52.319 align:start position:0% the IBM bytecode interests interests the byte<00:55:48.849> code<00:55:48.880> and<00:55:49.450> execute<00:55:50.880> interpret<00:55:51.880> each<00:55:52.059> one 00:55:52.319 --> 00:55:52.329 align:start position:0% byte code and execute interpret each one 00:55:52.329 --> 00:55:57.450 align:start position:0% byte code and execute interpret each one of<00:55:52.599> the<00:55:52.809> of<00:55:53.200> the<00:55:53.319> opcodes<00:55:55.980> the<00:55:56.980> majority<00:55:57.430> of 00:55:57.450 --> 00:55:57.460 align:start position:0% of the of the opcodes the majority of 00:55:57.460 --> 00:55:59.999 align:start position:0% of the of the opcodes the majority of the<00:55:57.670> opcodes<00:55:58.059> are<00:55:58.239> implemented<00:55:59.079> directly<00:55:59.529> in 00:55:59.999 --> 00:56:00.009 align:start position:0% the opcodes are implemented directly in 00:56:00.009 --> 00:56:02.519 align:start position:0% the opcodes are implemented directly in a<00:56:00.160> some<00:56:00.339> script<00:56:00.700> but<00:56:01.539> there<00:56:01.930> are<00:56:02.019> some<00:56:02.259> other 00:56:02.519 --> 00:56:02.529 align:start position:0% a some script but there are some other 00:56:02.529 --> 00:56:06.029 align:start position:0% a some script but there are some other code<00:56:03.099> for<00:56:03.940> example<00:56:03.999> this<00:56:04.420> one<00:56:04.720> that<00:56:05.039> instead 00:56:06.029 --> 00:56:06.039 align:start position:0% code for example this one that instead 00:56:06.039 --> 00:56:08.099 align:start position:0% code for example this one that instead of<00:56:06.099> being<00:56:06.519> implemented<00:56:07.059> directly<00:56:07.450> in<00:56:07.749> a<00:56:07.839> semi 00:56:08.099 --> 00:56:08.109 align:start position:0% of being implemented directly in a semi 00:56:08.109 --> 00:56:10.880 align:start position:0% of being implemented directly in a semi scale<00:56:08.319> because<00:56:09.069> our<00:56:09.369> cost<00:56:09.579> function 00:56:10.880 --> 00:56:10.890 align:start position:0% scale because our cost function 00:56:10.890 --> 00:56:14.190 align:start position:0% scale because our cost function basically<00:56:11.890> are<00:56:12.400> they<00:56:12.880> the<00:56:13.390> of<00:56:13.509> course<00:56:13.779> that 00:56:14.190 --> 00:56:14.200 align:start position:0% basically are they the of course that 00:56:14.200 --> 00:56:20.039 align:start position:0% basically are they the of course that deals<00:56:14.470> with<00:56:14.759> bignum<00:56:15.789> operations<00:56:18.119> and<00:56:19.119> these 00:56:20.039 --> 00:56:20.049 align:start position:0% deals with bignum operations and these 00:56:20.049 --> 00:56:22.440 align:start position:0% deals with bignum operations and these are<00:56:20.289> a<00:56:20.319> couple<00:56:20.589> of<00:56:20.710> examples 00:56:22.440 --> 00:56:22.450 align:start position:0% are a couple of examples 00:56:22.450 --> 00:56:25.380 align:start position:0% are a couple of examples this<00:56:22.870> is<00:56:22.990> a<00:56:23.080> very<00:56:23.260> simple<00:56:23.620> EP<00:56:23.980> my<00:56:24.280> thought<00:56:24.550> with 00:56:25.380 --> 00:56:25.390 align:start position:0% this is a very simple EP my thought with 00:56:25.390 --> 00:56:29.100 align:start position:0% this is a very simple EP my thought with just<00:56:25.840> our<00:56:26.490> first<00:56:27.490> put<00:56:27.940> the<00:56:28.240> number<00:56:28.510> one<00:56:28.540> to<00:56:28.990> the 00:56:29.100 --> 00:56:29.110 align:start position:0% just our first put the number one to the 00:56:29.110 --> 00:56:31.680 align:start position:0% just our first put the number one to the to<00:56:29.470> the<00:56:29.590> VM<00:56:29.830> spark<00:56:30.220> then<00:56:30.970> push<00:56:31.330> our<00:56:31.510> gained 00:56:31.680 --> 00:56:31.690 align:start position:0% to the VM spark then push our gained 00:56:31.690 --> 00:56:34.530 align:start position:0% to the VM spark then push our gained another<00:56:31.960> number<00:56:32.260> one<00:56:32.560> to<00:56:32.770> the<00:56:32.890> IBM<00:56:33.310> stock<00:56:33.670> and 00:56:34.530 --> 00:56:34.540 align:start position:0% another number one to the IBM stock and 00:56:34.540 --> 00:56:37.800 align:start position:0% another number one to the IBM stock and then<00:56:34.780> run<00:56:35.200> execute<00:56:35.770> the<00:56:36.060> opcode<00:56:37.060> so<00:56:37.390> we<00:56:37.600> have 00:56:37.800 --> 00:56:37.810 align:start position:0% then run execute the opcode so we have 00:56:37.810 --> 00:56:40.710 align:start position:0% then run execute the opcode so we have the<00:56:38.050> number<00:56:38.320> two<00:56:38.560> in<00:56:38.740> the<00:56:38.860> stack<00:56:39.100> and<00:56:39.760> then<00:56:40.510> we 00:56:40.710 --> 00:56:40.720 align:start position:0% the number two in the stack and then we 00:56:40.720 --> 00:56:43.830 align:start position:0% the number two in the stack and then we store<00:56:41.050> these<00:56:41.680> are<00:56:42.040> this<00:56:42.760> number<00:56:43.090> two<00:56:43.360> from<00:56:43.660> the 00:56:43.830 --> 00:56:43.840 align:start position:0% store these are this number two from the 00:56:43.840 --> 00:56:47.040 align:start position:0% store these are this number two from the start<00:56:44.110> to<00:56:44.260> the<00:56:44.290> to<00:56:45.010> the<00:56:45.160> vm<00:56:45.520> memory<00:56:45.700> and<00:56:46.600> at<00:56:46.900> the 00:56:47.040 --> 00:56:47.050 align:start position:0% start to the to the vm memory and at the 00:56:47.050 --> 00:56:50.070 align:start position:0% start to the to the vm memory and at the end<00:56:47.230> we<00:56:47.440> return<00:56:47.470> this<00:56:48.750> result<00:56:49.750> which<00:56:49.960> is 00:56:50.070 --> 00:56:50.080 align:start position:0% end we return this result which is 00:56:50.080 --> 00:56:53.070 align:start position:0% end we return this result which is number<00:56:50.230> two<00:56:50.590> and<00:56:50.860> we<00:56:51.430> write<00:56:51.700> this<00:56:51.850> on<00:56:52.120> the<00:56:52.270> on 00:56:53.070 --> 00:56:53.080 align:start position:0% number two and we write this on the on 00:56:53.080 --> 00:56:55.380 align:start position:0% number two and we write this on the on the<00:56:53.200> post<00:56:53.470> at<00:56:53.710> some<00:56:54.340> someone<00:56:54.670> asked<00:56:54.850> before<00:56:55.030> if 00:56:55.380 --> 00:56:55.390 align:start position:0% the post at some someone asked before if 00:56:55.390 --> 00:56:58.260 align:start position:0% the post at some someone asked before if we<00:56:55.600> can<00:56:55.810> do<00:56:55.960> whatever<00:56:56.170> we<00:56:56.350> want<00:56:56.560> to<00:56:57.270> know 00:56:58.260 --> 00:56:58.270 align:start position:0% we can do whatever we want to know 00:56:58.270 --> 00:57:03.150 align:start position:0% we can do whatever we want to know please<00:56:58.300> they<00:56:58.690> post<00:56:58.960> data<00:57:01.440> so<00:57:02.440> we<00:57:02.800> can<00:57:02.950> take 00:57:03.150 --> 00:57:03.160 align:start position:0% please they post data so we can take 00:57:03.160 --> 00:57:07.170 align:start position:0% please they post data so we can take this<00:57:03.400> IBM<00:57:04.300> white<00:57:04.600> coat<00:57:04.870> and<00:57:05.220> put<00:57:06.220> it<00:57:06.340> in<00:57:06.550> a<00:57:06.700> in<00:57:07.120> a 00:57:07.170 --> 00:57:07.180 align:start position:0% this IBM white coat and put it in a in a 00:57:07.180 --> 00:57:11.900 align:start position:0% this IBM white coat and put it in a in a stout<00:57:08.730> test<00:57:09.730> case<00:57:09.940> where<00:57:10.870> we<00:57:11.170> put<00:57:11.620> the 00:57:11.900 --> 00:57:11.910 align:start position:0% stout test case where we put the 00:57:11.910 --> 00:57:15.500 align:start position:0% stout test case where we put the bytecode<00:57:12.910> and<00:57:13.300> the<00:57:13.570> expected<00:57:14.080> result<00:57:14.440> here 00:57:15.500 --> 00:57:15.510 align:start position:0% bytecode and the expected result here 00:57:15.510 --> 00:57:19.230 align:start position:0% bytecode and the expected result here and<00:57:16.510> if<00:57:16.840> we<00:57:17.080> execute<00:57:17.440> this<00:57:17.740> test<00:57:18.220> case<00:57:18.400> we<00:57:19.030> get 00:57:19.230 --> 00:57:19.240 align:start position:0% and if we execute this test case we get 00:57:19.240 --> 00:57:21.540 align:start position:0% and if we execute this test case we get this<00:57:19.720> result<00:57:20.140> which<00:57:20.680> basically<00:57:21.130> says<00:57:21.520> that 00:57:21.540 --> 00:57:21.550 align:start position:0% this result which basically says that 00:57:21.550 --> 00:57:24.690 align:start position:0% this result which basically says that conference<00:57:22.510> that<00:57:22.720> we<00:57:23.440> expected<00:57:24.160> what<00:57:24.550> we 00:57:24.690 --> 00:57:24.700 align:start position:0% conference that we expected what we 00:57:24.700 --> 00:57:29.130 align:start position:0% conference that we expected what we expected<00:57:25.180> is<00:57:26.070> actually<00:57:27.070> we<00:57:27.250> get<00:57:28.080> for<00:57:29.080> example 00:57:29.130 --> 00:57:29.140 align:start position:0% expected is actually we get for example 00:57:29.140 --> 00:57:31.440 align:start position:0% expected is actually we get for example if<00:57:29.500> for<00:57:29.710> some<00:57:29.740> reason<00:57:30.340> I<00:57:30.550> change<00:57:30.820> this<00:57:31.090> sum 00:57:31.440 --> 00:57:31.450 align:start position:0% if for some reason I change this sum 00:57:31.450 --> 00:57:35.040 align:start position:0% if for some reason I change this sum this<00:57:32.290> test<00:57:33.040> case<00:57:33.250> and<00:57:33.310> I<00:57:33.640> say<00:57:33.940> that<00:57:34.240> one<00:57:34.840> plus 00:57:35.040 --> 00:57:35.050 align:start position:0% this test case and I say that one plus 00:57:35.050 --> 00:57:37.530 align:start position:0% this test case and I say that one plus one<00:57:35.080> equals<00:57:35.830> three<00:57:35.920> the<00:57:36.820> skull<00:57:37.060> will<00:57:37.300> show 00:57:37.530 --> 00:57:37.540 align:start position:0% one equals three the skull will show 00:57:37.540 --> 00:57:39.000 align:start position:0% one equals three the skull will show something<00:57:37.930> like<00:57:38.080> this<00:57:38.230> it<00:57:38.500> will<00:57:38.590> show<00:57:38.650> that 00:57:39.000 --> 00:57:39.010 align:start position:0% something like this it will show that 00:57:39.010 --> 00:57:40.890 align:start position:0% something like this it will show that these<00:57:39.520> are<00:57:39.730> difference<00:57:40.150> between<00:57:40.780> the 00:57:40.890 --> 00:57:40.900 align:start position:0% these are difference between the 00:57:40.900 --> 00:57:44.180 align:start position:0% these are difference between the execution<00:57:41.470> and<00:57:41.650> what<00:57:42.610> we<00:57:42.790> expected 00:57:44.180 --> 00:57:44.190 align:start position:0% execution and what we expected 00:57:44.190 --> 00:57:49.110 align:start position:0% execution and what we expected and<00:57:45.190> this<00:57:46.000> is<00:57:46.120> another<00:57:46.390> example<00:57:47.730> in<00:57:48.730> this<00:57:48.910> case 00:57:49.110 --> 00:57:49.120 align:start position:0% and this is another example in this case 00:57:49.120 --> 00:57:53.040 align:start position:0% and this is another example in this case the<00:57:49.390> EB<00:57:49.750> my<00:57:50.050> code<00:57:50.320> is<00:57:51.390> generated<00:57:52.390> by<00:57:52.990> the 00:57:53.040 --> 00:57:53.050 align:start position:0% the EB my code is generated by the 00:57:53.050 --> 00:58:00.120 align:start position:0% the EB my code is generated by the Sevilla<00:57:53.680> compiled<00:57:54.100> salinity<00:57:54.730> compiler<00:57:56.880> so<00:57:59.130> we 00:58:00.120 --> 00:58:00.130 align:start position:0% Sevilla compiled salinity compiler so we 00:58:00.130 --> 00:58:02.610 align:start position:0% Sevilla compiled salinity compiler so we are<00:58:00.280> we<00:58:00.730> are<00:58:00.760> sending<00:58:01.060> this<00:58:01.330> evn<00:58:01.930> by<00:58:02.140> code<00:58:02.380> as 00:58:02.610 --> 00:58:02.620 align:start position:0% are we are sending this evn by code as 00:58:02.620 --> 00:58:09.380 align:start position:0% are we are sending this evn by code as well<00:58:02.800> as<00:58:02.860> the<00:58:03.130> input<00:58:03.610> data<00:58:05.640> and<00:58:06.640> again<00:58:07.320> for<00:58:08.320> for 00:58:09.380 --> 00:58:09.390 align:start position:0% well as the input data and again for for 00:58:09.390 --> 00:58:12.150 align:start position:0% well as the input data and again for for forgetting<00:58:10.390> the<00:58:10.720> result<00:58:11.080> of<00:58:11.230> the<00:58:11.440> sound<00:58:11.830> of 00:58:12.150 --> 00:58:12.160 align:start position:0% forgetting the result of the sound of 00:58:12.160 --> 00:58:16.320 align:start position:0% forgetting the result of the sound of this<00:58:12.820> contract<00:58:13.360> I<00:58:13.600> also<00:58:13.810> run<00:58:14.320> it<00:58:14.500> in<00:58:15.220> in<00:58:15.790> the 00:58:16.320 --> 00:58:16.330 align:start position:0% this contract I also run it in in the 00:58:16.330 --> 00:58:21.130 align:start position:0% this contract I also run it in in the MDS<00:58:16.480> VM<00:58:17.050> in<00:58:17.970> the<00:58:18.970> same<00:58:19.240> result<00:58:20.080> that<00:58:20.260> we 00:58:21.130 --> 00:58:21.140 align:start position:0% MDS VM in the same result that we 00:58:21.140 --> 00:58:24.430 align:start position:0% MDS VM in the same result that we the<00:58:21.340> SVM<00:58:22.340> I'm<00:58:22.660> expecting<00:58:23.660> to<00:58:23.810> be<00:58:23.930> the<00:58:24.080> result 00:58:24.430 --> 00:58:24.440 align:start position:0% the SVM I'm expecting to be the result 00:58:24.440 --> 00:58:29.470 align:start position:0% the SVM I'm expecting to be the result in<00:58:24.680> the<00:58:25.180> execution<00:58:26.180> of<00:58:26.330> the<00:58:26.540> of<00:58:27.290> the<00:58:28.480> execution 00:58:29.470 --> 00:58:29.480 align:start position:0% in the execution of the of the execution 00:58:29.480 --> 00:58:33.190 align:start position:0% in the execution of the of the execution environment<00:58:30.490> so<00:58:31.490> we<00:58:31.670> run<00:58:31.850> this<00:58:32.000> sound<00:58:32.360> test 00:58:33.190 --> 00:58:33.200 align:start position:0% environment so we run this sound test 00:58:33.200 --> 00:58:36.550 align:start position:0% environment so we run this sound test case<00:58:33.410> and<00:58:33.760> Scout<00:58:34.760> confirms<00:58:35.390> that<00:58:35.630> we<00:58:35.900> but<00:58:36.410> we 00:58:36.550 --> 00:58:36.560 align:start position:0% case and Scout confirms that we but we 00:58:36.560 --> 00:58:41.110 align:start position:0% case and Scout confirms that we but we expected<00:58:37.070> is<00:58:37.220> what<00:58:37.520> we<00:58:38.150> are<00:58:38.300> getting<00:58:39.550> so<00:58:40.550> one 00:58:41.110 --> 00:58:41.120 align:start position:0% expected is what we are getting so one 00:58:41.120 --> 00:58:43.030 align:start position:0% expected is what we are getting so one of<00:58:41.150> the<00:58:41.330> next<00:58:41.600> steps<00:58:41.750> what<00:58:42.110> still<00:58:42.650> needs<00:58:42.680> to<00:58:42.950> be 00:58:43.030 --> 00:58:43.040 align:start position:0% of the next steps what still needs to be 00:58:43.040 --> 00:58:47.530 align:start position:0% of the next steps what still needs to be done<00:58:45.130> the<00:58:46.130> first<00:58:46.430> thing<00:58:46.730> that<00:58:46.760> it<00:58:47.090> to<00:58:47.240> be<00:58:47.390> done 00:58:47.530 --> 00:58:47.540 align:start position:0% done the first thing that it to be done 00:58:47.540 --> 00:58:49.170 align:start position:0% done the first thing that it to be done is<00:58:47.780> to<00:58:47.810> actually<00:58:48.170> use<00:58:48.440> the<00:58:48.770> discount 00:58:49.170 --> 00:58:49.180 align:start position:0% is to actually use the discount 00:58:49.180 --> 00:58:52.240 align:start position:0% is to actually use the discount establish<00:58:50.180> capabilities<00:58:50.810> which<00:58:51.620> means<00:58:51.890> that 00:58:52.240 --> 00:58:52.250 align:start position:0% establish capabilities which means that 00:58:52.250 --> 00:58:56.200 align:start position:0% establish capabilities which means that we<00:58:53.180> need<00:58:53.330> at<00:58:53.870> first<00:58:54.170> we<00:58:55.010> need<00:58:55.040> to<00:58:55.250> have<00:58:55.430> mr. 00:58:56.200 --> 00:58:56.210 align:start position:0% we need at first we need to have mr. 00:58:56.210 --> 00:59:00.340 align:start position:0% we need at first we need to have mr. hood<00:58:56.480> and<00:58:57.020> instead<00:58:58.010> of<00:58:58.180> adding<00:58:59.180> the<00:58:59.570> IBM<00:59:00.110> byte 00:59:00.340 --> 00:59:00.350 align:start position:0% hood and instead of adding the IBM byte 00:59:00.350 --> 00:59:03.220 align:start position:0% hood and instead of adding the IBM byte code<00:59:00.620> directly<00:59:01.490> in<00:59:01.730> the<00:59:01.850> block<00:59:02.030> data<00:59:02.240> we<00:59:03.050> need 00:59:03.220 --> 00:59:03.230 align:start position:0% code directly in the block data we need 00:59:03.230 --> 00:59:09.670 align:start position:0% code directly in the block data we need to<00:59:04.300> instead<00:59:05.620> a<00:59:06.620> list<00:59:07.160> of<00:59:07.340> transactions<00:59:08.090> a<00:59:08.680> list 00:59:09.670 --> 00:59:09.680 align:start position:0% to instead a list of transactions a list 00:59:09.680 --> 00:59:12.940 align:start position:0% to instead a list of transactions a list of<00:59:09.890> proof<00:59:10.190> nodes<00:59:11.620> corresponding<00:59:12.620> to<00:59:12.830> the 00:59:12.940 --> 00:59:12.950 align:start position:0% of proof nodes corresponding to the 00:59:12.950 --> 00:59:15.310 align:start position:0% of proof nodes corresponding to the accounts<00:59:13.550> and<00:59:13.670> the<00:59:13.790> contracts<00:59:14.300> affected<00:59:14.930> by 00:59:15.310 --> 00:59:15.320 align:start position:0% accounts and the contracts affected by 00:59:15.320 --> 00:59:19.270 align:start position:0% accounts and the contracts affected by those<00:59:15.710> transactions<00:59:16.510> and<00:59:17.510> we<00:59:18.080> also<00:59:18.950> need<00:59:19.250> to 00:59:19.270 --> 00:59:19.280 align:start position:0% those transactions and we also need to 00:59:19.280 --> 00:59:25.480 align:start position:0% those transactions and we also need to do<00:59:20.120> other<00:59:20.890> posture<00:59:21.890> hood<00:59:22.130> where<00:59:24.490> this 00:59:25.480 --> 00:59:25.490 align:start position:0% do other posture hood where this 00:59:25.490 --> 00:59:28.420 align:start position:0% do other posture hood where this reflects<00:59:26.240> the<00:59:26.660> result<00:59:27.200> of<00:59:27.470> the<00:59:27.770> only<00:59:28.010> changes 00:59:28.420 --> 00:59:28.430 align:start position:0% reflects the result of the only changes 00:59:28.430 --> 00:59:31.720 align:start position:0% reflects the result of the only changes made<00:59:28.640> in<00:59:28.820> those<00:59:29.060> transactions<00:59:30.490> another<00:59:31.490> thing 00:59:31.720 --> 00:59:31.730 align:start position:0% made in those transactions another thing 00:59:31.730 --> 00:59:33.850 align:start position:0% made in those transactions another thing another<00:59:32.300> thing<00:59:32.660> that<00:59:32.870> needs<00:59:33.050> to<00:59:33.140> be<00:59:33.230> done<00:59:33.500> is<00:59:33.800> a 00:59:33.850 --> 00:59:33.860 align:start position:0% another thing that needs to be done is a 00:59:33.860 --> 00:59:38.830 align:start position:0% another thing that needs to be done is a test<00:59:34.400> with<00:59:34.640> more<00:59:35.470> more<00:59:36.470> contracts<00:59:37.480> it<00:59:38.480> will<00:59:38.690> be 00:59:38.830 --> 00:59:38.840 align:start position:0% test with more more contracts it will be 00:59:38.840 --> 00:59:42.610 align:start position:0% test with more more contracts it will be testing<00:59:39.770> with<00:59:39.920> the<00:59:40.510> with<00:59:41.510> the<00:59:41.690> contracts<00:59:42.440> in 00:59:42.610 --> 00:59:42.620 align:start position:0% testing with the with the contracts in 00:59:42.620 --> 00:59:50.080 align:start position:0% testing with the with the contracts in the<00:59:42.650> team<00:59:43.460> tests<00:59:45.700> in<00:59:46.700> the<00:59:47.360> main<00:59:48.170> team<00:59:48.470> test<00:59:49.090> and 00:59:50.080 --> 00:59:50.090 align:start position:0% the team tests in the main team test and 00:59:50.090 --> 00:59:52.870 align:start position:0% the team tests in the main team test and finally<00:59:50.780> the<00:59:51.130> one<00:59:52.130> important<00:59:52.550> thing<00:59:52.580> that 00:59:52.870 --> 00:59:52.880 align:start position:0% finally the one important thing that 00:59:52.880 --> 00:59:56.940 align:start position:0% finally the one important thing that needs<00:59:53.660> to<00:59:53.720> be<00:59:53.810> done<00:59:54.080> is<00:59:55.090> benchmarking<00:59:56.090> and 00:59:56.940 --> 00:59:56.950 align:start position:0% needs to be done is benchmarking and 00:59:56.950 --> 01:00:38.440 align:start position:0% needs to be done is benchmarking and that 01:00:38.440 --> 01:00:38.450 align:start position:0% 01:00:38.450 --> 01:00:51.850 align:start position:0% not<01:00:39.450> yet<01:00:39.660> and<01:00:39.960> we<01:00:40.170> need<01:00:40.320> to<01:00:40.470> keep<01:00:40.859> testing 01:00:51.850 --> 01:00:51.860 align:start position:0% 01:00:51.860 --> 01:00:55.180 align:start position:0% synthesis<01:00:52.790> business<01:00:53.720> part<01:00:53.960> of<01:00:54.050> the<01:00:54.110> EVM<01:00:54.770> once 01:00:55.180 --> 01:00:55.190 align:start position:0% synthesis business part of the EVM once 01:00:55.190 --> 01:01:00.790 align:start position:0% synthesis business part of the EVM once the<01:00:55.610> equals<01:00:56.060> speech<01:00:56.660> award<01:00:56.990> idea<01:00:57.380> and<01:00:59.800> about 01:01:00.790 --> 01:01:00.800 align:start position:0% the equals speech award idea and about 01:01:00.800 --> 01:01:02.920 align:start position:0% the equals speech award idea and about the<01:01:00.980> defense's<01:01:01.670> to<01:01:01.940> to<01:01:02.240> probably<01:01:02.540> integrate 01:01:02.920 --> 01:01:02.930 align:start position:0% the defense's to to probably integrate 01:01:02.930 --> 01:01:05.710 align:start position:0% the defense's to to probably integrate this<01:01:03.050> into<01:01:03.230> two<01:01:03.470> remote<01:01:03.680> token<01:01:04.010> and<01:01:04.640> at<01:01:05.300> that 01:01:05.710 --> 01:01:05.720 align:start position:0% this into two remote token and at that 01:01:05.720 --> 01:01:08.260 align:start position:0% this into two remote token and at that point<01:01:05.990> you<01:01:06.830> would<01:01:06.950> want<01:01:07.220> to<01:01:07.340> have<01:01:07.520> some<01:01:08.030> kind 01:01:08.260 --> 01:01:08.270 align:start position:0% point you would want to have some kind 01:01:08.270 --> 01:01:11.080 align:start position:0% point you would want to have some kind of<01:01:08.360> a<01:01:08.570> best<01:01:09.110> form<01:01:09.440> of<01:01:09.560> the<01:01:10.340> entire<01:01:10.610> need<01:01:10.850> one 01:01:11.080 --> 01:01:11.090 align:start position:0% of a best form of the entire need one 01:01:11.090 --> 01:01:14.440 align:start position:0% of a best form of the entire need one blocks<01:01:11.710> to<01:01:12.710> be<01:01:12.800> transmitted<01:01:13.310> but<01:01:14.000> of<01:01:14.270> course 01:01:14.440 --> 01:01:14.450 align:start position:0% blocks to be transmitted but of course 01:01:14.450 --> 01:01:17.560 align:start position:0% blocks to be transmitted but of course you<01:01:14.600> need<01:01:14.720> two<01:01:15.050> cups<01:01:15.230> as<01:01:15.410> well<01:01:15.730> but<01:01:16.730> the<01:01:17.150> buck 01:01:17.560 --> 01:01:17.570 align:start position:0% you need two cups as well but the buck 01:01:17.570 --> 01:01:39.160 align:start position:0% you need two cups as well but the buck they<01:01:17.720> did 01:01:39.160 --> 01:01:39.170 align:start position:0% 01:01:39.170 --> 01:01:42.380 align:start position:0% hi<01:01:40.170> guys<01:01:40.410> my<01:01:40.710> name<01:01:40.920> is<01:01:40.950> Matt<01:01:41.250> I<01:01:41.580> am<01:01:41.730> with<01:01:42.180> the 01:01:42.380 --> 01:01:42.390 align:start position:0% hi guys my name is Matt I am with the 01:01:42.390 --> 01:01:51.050 align:start position:0% hi guys my name is Matt I am with the police<01:01:48.380> so<01:01:49.380> the<01:01:49.560> name<01:01:49.710> sheath<01:01:50.040> comes<01:01:50.400> from<01:01:50.760> the 01:01:51.050 --> 01:01:51.060 align:start position:0% police so the name sheath comes from the 01:01:51.060 --> 01:01:53.470 align:start position:0% police so the name sheath comes from the shard<01:01:51.360> he's<01:01:51.600> her<01:01:51.750> manager<01:01:52.020> it's<01:01:52.800> a<01:01:53.100> token 01:01:53.470 --> 01:01:53.480 align:start position:0% shard he's her manager it's a token 01:01:53.480 --> 01:01:55.850 align:start position:0% shard he's her manager it's a token transfer<01:01:54.480> execution<01:01:55.020> apartment<01:01:55.500> just<01:01:55.620> like 01:01:55.850 --> 01:01:55.860 align:start position:0% transfer execution apartment just like 01:01:55.860 --> 01:01:57.650 align:start position:0% transfer execution apartment just like you<01:01:55.980> saw<01:01:56.190> with<01:01:56.220> Sina<01:01:56.730> and<01:01:56.760> Guillaume<01:01:57.180> and<01:01:57.360> just 01:01:57.650 --> 01:01:57.660 align:start position:0% you saw with Sina and Guillaume and just 01:01:57.660 --> 01:02:02.090 align:start position:0% you saw with Sina and Guillaume and just like<01:01:57.780> you<01:01:57.930> see<01:01:58.140> with<01:01:58.230> all<01:01:58.500> after<01:02:00.890> it's<01:02:01.890> written 01:02:02.090 --> 01:02:02.100 align:start position:0% like you see with all after it's written 01:02:02.100 --> 01:02:04.430 align:start position:0% like you see with all after it's written rust<01:02:02.490> and<01:02:02.820> it<01:02:03.300> provides<01:02:03.630> a<01:02:03.780> few<01:02:03.960> things<01:02:04.200> for 01:02:04.430 --> 01:02:04.440 align:start position:0% rust and it provides a few things for 01:02:04.440 --> 01:02:06.170 align:start position:0% rust and it provides a few things for you<01:02:04.500> provides<01:02:04.980> an<01:02:05.190> execution<01:02:05.730> environment 01:02:06.170 --> 01:02:06.180 align:start position:0% you provides an execution environment 01:02:06.180 --> 01:02:08.060 align:start position:0% you provides an execution environment which<01:02:06.420> is<01:02:06.630> like<01:02:06.870> a<01:02:06.900> web<01:02:07.050> assembly<01:02:07.440> binary<01:02:07.950> that 01:02:08.060 --> 01:02:08.070 align:start position:0% which is like a web assembly binary that 01:02:08.070 --> 01:02:10.310 align:start position:0% which is like a web assembly binary that you<01:02:08.190> give<01:02:08.430> to<01:02:08.730> the<01:02:09.120> beacon<01:02:09.480> and<01:02:09.780> it's<01:02:09.900> execute 01:02:10.310 --> 01:02:10.320 align:start position:0% you give to the beacon and it's execute 01:02:10.320 --> 01:02:13.010 align:start position:0% you give to the beacon and it's execute on<01:02:10.440> the<01:02:10.500> shards<01:02:10.920> it<01:02:11.460> gives<01:02:11.880> a<01:02:12.060> CLI<01:02:12.510> tool<01:02:12.780> to 01:02:13.010 --> 01:02:13.020 align:start position:0% on the shards it gives a CLI tool to 01:02:13.020 --> 01:02:15.860 align:start position:0% on the shards it gives a CLI tool to build<01:02:13.400> random<01:02:14.400> transaction<01:02:15.090> packages<01:02:15.600> and 01:02:15.860 --> 01:02:15.870 align:start position:0% build random transaction packages and 01:02:15.870 --> 01:02:17.450 align:start position:0% build random transaction packages and the<01:02:16.350> proofs<01:02:16.680> that<01:02:16.860> go<01:02:16.980> along<01:02:17.250> with<01:02:17.280> that 01:02:17.450 --> 01:02:17.460 align:start position:0% the proofs that go along with that 01:02:17.460 --> 01:02:18.980 align:start position:0% the proofs that go along with that transaction<01:02:17.940> package<01:02:18.540> so<01:02:18.720> it<01:02:18.780> can<01:02:18.870> be 01:02:18.980 --> 01:02:18.990 align:start position:0% transaction package so it can be 01:02:18.990 --> 01:02:21.470 align:start position:0% transaction package so it can be executed<01:02:19.350> stateless<01:02:20.010> ligament<01:02:20.490> and<01:02:20.670> it<01:02:21.300> gives 01:02:21.470 --> 01:02:21.480 align:start position:0% executed stateless ligament and it gives 01:02:21.480 --> 01:02:23.630 align:start position:0% executed stateless ligament and it gives some<01:02:21.690> testing<01:02:22.200> and<01:02:22.350> debugging<01:02:22.470> tools<01:02:23.130> because 01:02:23.630 --> 01:02:23.640 align:start position:0% some testing and debugging tools because 01:02:23.640 --> 01:02:27.770 align:start position:0% some testing and debugging tools because compiling<01:02:24.180> tool<01:02:24.480> of<01:02:24.600> assembly<01:02:25.050> arrests<01:02:26.780> and 01:02:27.770 --> 01:02:27.780 align:start position:0% compiling tool of assembly arrests and 01:02:27.780 --> 01:02:30.890 align:start position:0% compiling tool of assembly arrests and it<01:02:28.770> helps<01:02:29.160> kind<01:02:29.400> of<01:02:29.550> streamline<01:02:30.240> on<01:02:30.420> process 01:02:30.890 --> 01:02:30.900 align:start position:0% it helps kind of streamline on process 01:02:30.900 --> 01:02:32.540 align:start position:0% it helps kind of streamline on process and<01:02:31.230> streamline<01:02:31.740> the<01:02:31.860> process<01:02:32.220> of<01:02:32.340> writing 01:02:32.540 --> 01:02:32.550 align:start position:0% and streamline the process of writing 01:02:32.550 --> 01:02:34.280 align:start position:0% and streamline the process of writing your<01:02:33.120> execution<01:02:33.690> environment<01:02:34.170> their 01:02:34.280 --> 01:02:34.290 align:start position:0% your execution environment their 01:02:34.290 --> 01:02:37.370 align:start position:0% your execution environment their skeleton<01:02:35.600> so<01:02:36.600> when<01:02:36.720> I<01:02:36.750> started<01:02:37.080> out<01:02:37.260> with 01:02:37.370 --> 01:02:37.380 align:start position:0% skeleton so when I started out with 01:02:37.380 --> 01:02:39.500 align:start position:0% skeleton so when I started out with building<01:02:37.860> sheath<01:02:38.100> the<01:02:38.340> design<01:02:38.640> goals<01:02:38.940> fishies 01:02:39.500 --> 01:02:39.510 align:start position:0% building sheath the design goals fishies 01:02:39.510 --> 01:02:41.720 align:start position:0% building sheath the design goals fishies were<01:02:39.810> we're<01:02:40.260> trying<01:02:40.530> to<01:02:40.590> make<01:02:40.770> took<01:02:41.640> a 01:02:41.720 --> 01:02:41.730 align:start position:0% were we're trying to make took a 01:02:41.730 --> 01:02:43.040 align:start position:0% were we're trying to make took a transfer<01:02:42.090> environment<01:02:42.600> that<01:02:42.720> they're<01:02:42.840> really 01:02:43.040 --> 01:02:43.050 align:start position:0% transfer environment that they're really 01:02:43.050 --> 01:02:45.530 align:start position:0% transfer environment that they're really small<01:02:43.290> of<01:02:43.530> assembly<01:02:43.950> binary<01:02:44.400> we<01:02:45.090> wanted<01:02:45.390> to 01:02:45.530 --> 01:02:45.540 align:start position:0% small of assembly binary we wanted to 01:02:45.540 --> 01:02:48.800 align:start position:0% small of assembly binary we wanted to have<01:02:45.810> a<01:02:46.170> small<01:02:46.500> crew<01:02:46.770> sizes<01:02:47.310> to<01:02:47.700> execute<01:02:48.540> on<01:02:48.660> I 01:02:48.800 --> 01:02:48.810 align:start position:0% have a small crew sizes to execute on I 01:02:48.810 --> 01:02:50.120 align:start position:0% have a small crew sizes to execute on I thought<01:02:49.050> we<01:02:49.110> wanted<01:02:49.410> to<01:02:49.500> that<01:02:49.680> are<01:02:49.740> going<01:02:49.770> fast 01:02:50.120 --> 01:02:50.130 align:start position:0% thought we wanted to that are going fast 01:02:50.130 --> 01:02:53.450 align:start position:0% thought we wanted to that are going fast and<01:02:51.590> it<01:02:52.590> turns<01:02:52.770> out<01:02:52.890> that<01:02:53.010> we're<01:02:53.280> still 01:02:53.450 --> 01:02:53.460 align:start position:0% and it turns out that we're still 01:02:53.460 --> 01:02:55.160 align:start position:0% and it turns out that we're still working<01:02:53.490> on<01:02:53.820> those<01:02:53.940> things<01:02:54.180> because<01:02:54.750> they're 01:02:55.160 --> 01:02:55.170 align:start position:0% working on those things because they're 01:02:55.170 --> 01:02:58.289 align:start position:0% working on those things because they're not<01:02:55.290> as<01:02:55.500> easy<01:02:55.710> is 01:02:58.289 --> 01:02:58.299 align:start position:0% 01:02:58.299 --> 01:03:01.289 align:start position:0% and<01:02:58.410> so<01:02:59.410> right<01:03:00.400> now<01:03:00.579> I'm<01:03:00.730> trying<01:03:01.000> to<01:03:01.089> get<01:03:01.210> it 01:03:01.289 --> 01:03:01.299 align:start position:0% and so right now I'm trying to get it 01:03:01.299 --> 01:03:02.579 align:start position:0% and so right now I'm trying to get it really<01:03:01.599> hot<01:03:01.690> or<01:03:01.960> something<01:03:02.049> and<01:03:02.349> what<01:03:02.440> do<01:03:02.530> I 01:03:02.579 --> 01:03:02.589 align:start position:0% really hot or something and what do I 01:03:02.589 --> 01:03:04.230 align:start position:0% really hot or something and what do I mean<01:03:02.619> by<01:03:02.770> hospital<01:03:03.280> I<01:03:03.309> mean<01:03:03.520> it's<01:03:03.910> something 01:03:04.230 --> 01:03:04.240 align:start position:0% mean by hospital I mean it's something 01:03:04.240 --> 01:03:05.940 align:start position:0% mean by hospital I mean it's something like<01:03:04.299> you<01:03:04.359> at<01:03:04.780> a<01:03:04.809> hackathon<01:03:05.020> you<01:03:05.500> go<01:03:05.650> in<01:03:05.829> and 01:03:05.940 --> 01:03:05.950 align:start position:0% like you at a hackathon you go in and 01:03:05.950 --> 01:03:07.950 align:start position:0% like you at a hackathon you go in and fork<01:03:06.190> and<01:03:06.490> start<01:03:06.910> swapping<01:03:07.150> out<01:03:07.390> components 01:03:07.950 --> 01:03:07.960 align:start position:0% fork and start swapping out components 01:03:07.960 --> 01:03:09.390 align:start position:0% fork and start swapping out components and<01:03:08.109> start<01:03:08.290> experimenting<01:03:08.770> with<01:03:09.010> what<01:03:09.309> an 01:03:09.390 --> 01:03:09.400 align:start position:0% and start experimenting with what an 01:03:09.400 --> 01:03:12.569 align:start position:0% and start experimenting with what an execution<01:03:09.940> environment<01:03:10.480> is<01:03:10.630> and<01:03:10.930> does<01:03:11.579> you 01:03:12.569 --> 01:03:12.579 align:start position:0% execution environment is and does you 01:03:12.579 --> 01:03:14.099 align:start position:0% execution environment is and does you can<01:03:12.700> put<01:03:12.849> your<01:03:13.000> own<01:03:13.030> logic<01:03:13.480> in<01:03:13.599> it<01:03:13.630> it's 01:03:14.099 --> 01:03:14.109 align:start position:0% can put your own logic in it it's 01:03:14.109 --> 01:03:15.660 align:start position:0% can put your own logic in it it's hopefully<01:03:14.680> a<01:03:14.740> really<01:03:14.920> readable<01:03:15.309> via<01:03:15.490> there 01:03:15.660 --> 01:03:15.670 align:start position:0% hopefully a really readable via there 01:03:15.670 --> 01:03:17.280 align:start position:0% hopefully a really readable via there should<01:03:15.819> be<01:03:15.910> the<01:03:16.030> apparently<01:03:16.390> idiomatic<01:03:16.869> rust 01:03:17.280 --> 01:03:17.290 align:start position:0% should be the apparently idiomatic rust 01:03:17.290 --> 01:03:20.160 align:start position:0% should be the apparently idiomatic rust where<01:03:17.589> us<01:03:18.250> is<01:03:18.760> not<01:03:19.000> incredibly<01:03:19.630> compromised 01:03:20.160 --> 01:03:20.170 align:start position:0% where us is not incredibly compromised 01:03:20.170 --> 01:03:22.109 align:start position:0% where us is not incredibly compromised so<01:03:20.500> there's<01:03:21.160> one<01:03:21.339> thing<01:03:21.490> to<01:03:21.579> take<01:03:21.730> from<01:03:21.790> this 01:03:22.109 --> 01:03:22.119 align:start position:0% so there's one thing to take from this 01:03:22.119 --> 01:03:25.410 align:start position:0% so there's one thing to take from this is<01:03:22.180> to<01:03:22.780> try<01:03:23.140> it<01:03:23.200> for<01:03:23.500> CSUN<01:03:24.130> and<01:03:24.339> get<01:03:24.970> a<01:03:25.000> go<01:03:25.210> at<01:03:25.390> it 01:03:25.410 --> 01:03:25.420 align:start position:0% is to try it for CSUN and get a go at it 01:03:25.420 --> 01:03:27.690 align:start position:0% is to try it for CSUN and get a go at it so<01:03:25.750> the<01:03:26.440> general<01:03:26.740> architecture<01:03:26.890> was 01:03:27.690 --> 01:03:27.700 align:start position:0% so the general architecture was 01:03:27.700 --> 01:03:29.849 align:start position:0% so the general architecture was happening<01:03:28.150> is<01:03:28.329> kind<01:03:29.079> of<01:03:29.140> laid<01:03:29.319> out<01:03:29.349> here<01:03:29.740> and 01:03:29.849 --> 01:03:29.859 align:start position:0% happening is kind of laid out here and 01:03:29.859 --> 01:03:32.039 align:start position:0% happening is kind of laid out here and like<01:03:29.950> this<01:03:30.430> base<01:03:30.700> layer<01:03:31.059> is<01:03:31.119> sheath<01:03:31.809> and 01:03:32.039 --> 01:03:32.049 align:start position:0% like this base layer is sheath and 01:03:32.049 --> 01:03:33.780 align:start position:0% like this base layer is sheath and that's<01:03:32.170> kind<01:03:32.410> of<01:03:32.440> just<01:03:32.859> provide<01:03:33.190> some<01:03:33.220> like 01:03:33.780 --> 01:03:33.790 align:start position:0% that's kind of just provide some like 01:03:33.790 --> 01:03:35.670 align:start position:0% that's kind of just provide some like rails<01:03:34.059> for<01:03:34.420> you<01:03:34.540> to<01:03:34.660> build<01:03:34.809> an<01:03:35.109> execution<01:03:35.589> of 01:03:35.670 --> 01:03:35.680 align:start position:0% rails for you to build an execution of 01:03:35.680 --> 01:03:38.039 align:start position:0% rails for you to build an execution of iron<01:03:35.859> on<01:03:36.040> top<01:03:36.220> of<01:03:36.460> and<01:03:36.670> so<01:03:37.210> each<01:03:37.540> of<01:03:37.660> these<01:03:37.839> like 01:03:38.039 --> 01:03:38.049 align:start position:0% iron on top of and so each of these like 01:03:38.049 --> 01:03:39.870 align:start position:0% iron on top of and so each of these like kind<01:03:38.170> of<01:03:38.290> components<01:03:38.890> are<01:03:39.369> things<01:03:39.640> that<01:03:39.790> you 01:03:39.870 --> 01:03:39.880 align:start position:0% kind of components are things that you 01:03:39.880 --> 01:03:42.059 align:start position:0% kind of components are things that you can<01:03:40.089> you<01:03:40.750> can<01:03:40.869> swap<01:03:41.200> out<01:03:41.349> and<01:03:41.619> put<01:03:41.740> whatever 01:03:42.059 --> 01:03:42.069 align:start position:0% can you can swap out and put whatever 01:03:42.069 --> 01:03:44.490 align:start position:0% can you can swap out and put whatever you<01:03:42.220> want<01:03:42.280> here<01:03:42.670> and<01:03:42.760> so<01:03:42.960> the<01:03:43.960> base<01:03:44.140> layer<01:03:44.410> is 01:03:44.490 --> 01:03:44.500 align:start position:0% you want here and so the base layer is 01:03:44.500 --> 01:03:46.200 align:start position:0% you want here and so the base layer is kind<01:03:44.799> of<01:03:44.859> the<01:03:44.950> database<01:03:45.400> that<01:03:45.579> you<01:03:45.730> operate<01:03:46.089> on 01:03:46.200 --> 01:03:46.210 align:start position:0% kind of the database that you operate on 01:03:46.210 --> 01:03:48.450 align:start position:0% kind of the database that you operate on your<01:03:46.690> like<01:03:46.990> multi<01:03:47.470> proof<01:03:47.770> that<01:03:48.040> Siena<01:03:48.430> and 01:03:48.450 --> 01:03:48.460 align:start position:0% your like multi proof that Siena and 01:03:48.460 --> 01:03:50.460 align:start position:0% your like multi proof that Siena and Yale<01:03:48.730> talked<01:03:49.059> about<01:03:49.329> and<01:03:49.630> so<01:03:50.260> my 01:03:50.460 --> 01:03:50.470 align:start position:0% Yale talked about and so my 01:03:50.470 --> 01:03:52.349 align:start position:0% Yale talked about and so my implementation<01:03:50.710> is<01:03:51.400> like<01:03:51.609> a<01:03:51.700> sparse<01:03:51.940> Merkel 01:03:52.349 --> 01:03:52.359 align:start position:0% implementation is like a sparse Merkel 01:03:52.359 --> 01:03:54.930 align:start position:0% implementation is like a sparse Merkel Sharia<01:03:52.630> I'm<01:03:53.530> calling<01:03:54.069> it<01:03:54.160> in<01:03:54.339> because<01:03:54.730> it's<01:03:54.849> an 01:03:54.930 --> 01:03:54.940 align:start position:0% Sharia I'm calling it in because it's an 01:03:54.940 --> 01:03:56.940 align:start position:0% Sharia I'm calling it in because it's an in-place<01:03:55.329> multi<01:03:55.720> proof<01:03:55.960> but<01:03:56.500> you<01:03:56.530> can<01:03:56.740> swap 01:03:56.940 --> 01:03:56.950 align:start position:0% in-place multi proof but you can swap 01:03:56.950 --> 01:03:59.430 align:start position:0% in-place multi proof but you can swap that<01:03:56.980> out<01:03:57.130> for<01:03:57.990> nutritional<01:03:58.990> vertical<01:03:59.290> tree 01:03:59.430 --> 01:03:59.440 align:start position:0% that out for nutritional vertical tree 01:03:59.440 --> 01:04:00.839 align:start position:0% that out for nutritional vertical tree or<01:03:59.559> any<01:03:59.710> other<01:03:59.859> kind<01:04:00.069> of<01:04:00.130> fruit<01:04:00.339> format<01:04:00.760> that 01:04:00.839 --> 01:04:00.849 align:start position:0% or any other kind of fruit format that 01:04:00.849 --> 01:04:03.329 align:start position:0% or any other kind of fruit format that you<01:04:00.970> like<01:04:01.290> all<01:04:02.290> of<01:04:02.440> it<01:04:02.530> has<01:04:02.740> seduced<01:04:03.010> has<01:04:03.220> to 01:04:03.329 --> 01:04:03.339 align:start position:0% you like all of it has seduced has to 01:04:03.339 --> 01:04:05.190 align:start position:0% you like all of it has seduced has to implement<01:04:03.849> a<01:04:04.030> trait<01:04:04.299> that<01:04:04.329> has<01:04:04.569> kind<01:04:04.960> of<01:04:05.020> these 01:04:05.190 --> 01:04:05.200 align:start position:0% implement a trait that has kind of these 01:04:05.200 --> 01:04:07.079 align:start position:0% implement a trait that has kind of these functions<01:04:05.950> so<01:04:06.490> you<01:04:06.579> need<01:04:06.670> to<01:04:06.760> be<01:04:06.880> able<01:04:06.940> to 01:04:07.079 --> 01:04:07.089 align:start position:0% functions so you need to be able to 01:04:07.089 --> 01:04:08.640 align:start position:0% functions so you need to be able to figure<01:04:07.240> out<01:04:07.390> what<01:04:07.480> the<01:04:07.599> value<01:04:07.960> and<01:04:08.109> account<01:04:08.440> is 01:04:08.640 --> 01:04:08.650 align:start position:0% figure out what the value and account is 01:04:08.650 --> 01:04:10.740 align:start position:0% figure out what the value and account is what<01:04:08.950> that<01:04:09.099> it<01:04:09.190> comes<01:04:09.369> to<01:04:09.460> dances<01:04:09.880> and<01:04:10.450> he<01:04:10.599> to 01:04:10.740 --> 01:04:10.750 align:start position:0% what that it comes to dances and he to 01:04:10.750 --> 01:04:12.680 align:start position:0% what that it comes to dances and he to be<01:04:10.839> able<01:04:10.900> to<01:04:11.079> add<01:04:11.260> and<01:04:11.530> subtract<01:04:11.859> values 01:04:12.680 --> 01:04:12.690 align:start position:0% be able to add and subtract values 01:04:12.690 --> 01:04:15.539 align:start position:0% be able to add and subtract values increase<01:04:13.690> the<01:04:13.839> nonspecific<01:04:14.200> Council<01:04:14.770> and 01:04:15.539 --> 01:04:15.549 align:start position:0% increase the nonspecific Council and 01:04:15.549 --> 01:04:17.250 align:start position:0% increase the nonspecific Council and then<01:04:15.700> there's<01:04:16.180> a<01:04:16.240> few<01:04:16.420> types<01:04:16.780> of<01:04:16.869> types<01:04:17.109> of 01:04:17.250 --> 01:04:17.260 align:start position:0% then there's a few types of types of 01:04:17.260 --> 01:04:19.920 align:start position:0% then there's a few types of types of transfers<01:04:17.710> for<01:04:17.890> execution<01:04:18.430> of<01:04:18.460> artisan<01:04:18.940> 2.0 01:04:19.920 --> 01:04:19.930 align:start position:0% transfers for execution of artisan 2.0 01:04:19.930 --> 01:04:22.170 align:start position:0% transfers for execution of artisan 2.0 so<01:04:20.380> the<01:04:20.619> transferred<01:04:21.130> applies<01:04:21.549> in<01:04:21.730> withdraw 01:04:22.170 --> 01:04:22.180 align:start position:0% so the transferred applies in withdraw 01:04:22.180 --> 01:04:24.240 align:start position:0% so the transferred applies in withdraw the<01:04:22.809> deposit<01:04:23.200> of<01:04:23.230> the<01:04:23.349> drawer<01:04:23.589> like<01:04:23.740> beacon 01:04:24.240 --> 01:04:24.250 align:start position:0% the deposit of the drawer like beacon 01:04:24.250 --> 01:04:25.740 align:start position:0% the deposit of the drawer like beacon chain<01:04:24.490> related<01:04:24.849> functions<01:04:25.299> it's<01:04:25.569> how<01:04:25.690> you 01:04:25.740 --> 01:04:25.750 align:start position:0% chain related functions it's how you 01:04:25.750 --> 01:04:28.339 align:start position:0% chain related functions it's how you move<01:04:26.339> ether<01:04:27.339> in<01:04:27.400> the<01:04:27.490> one<01:04:27.670> shard<01:04:27.940> to<01:04:28.059> the<01:04:28.150> other 01:04:28.339 --> 01:04:28.349 align:start position:0% move ether in the one shard to the other 01:04:28.349 --> 01:04:31.140 align:start position:0% move ether in the one shard to the other transfer<01:04:29.349> is<01:04:29.500> how<01:04:29.650> you<01:04:30.609> transfer<01:04:31.000> between 01:04:31.140 --> 01:04:31.150 align:start position:0% transfer is how you transfer between 01:04:31.150 --> 01:04:33.140 align:start position:0% transfer is how you transfer between accounts<01:04:31.720> but<01:04:32.559> if<01:04:32.650> you 01:04:33.140 --> 01:04:33.150 align:start position:0% accounts but if you 01:04:33.150 --> 01:04:35.000 align:start position:0% accounts but if you you<01:04:33.240> morphism<01:04:33.900> pack<01:04:34.230> out<01:04:34.440> your<01:04:34.619> own<01:04:34.770> things 01:04:35.000 --> 01:04:35.010 align:start position:0% you morphism pack out your own things 01:04:35.010 --> 01:04:37.130 align:start position:0% you morphism pack out your own things this<01:04:35.430> is<01:04:35.579> where<01:04:35.730> you<01:04:35.880> can<01:04:36.000> add<01:04:36.180> and<01:04:36.450> swap<01:04:36.930> out 01:04:37.130 --> 01:04:37.140 align:start position:0% this is where you can add and swap out 01:04:37.140 --> 01:04:38.299 align:start position:0% this is where you can add and swap out and<01:04:37.349> put<01:04:37.500> whatever<01:04:37.619> kind<01:04:37.770> of<01:04:37.950> trends 01:04:38.299 --> 01:04:38.309 align:start position:0% and put whatever kind of trends 01:04:38.309 --> 01:04:39.980 align:start position:0% and put whatever kind of trends transactions<01:04:39.119> you<01:04:39.210> want<01:04:39.420> as<01:04:39.510> long<01:04:39.660> as<01:04:39.779> you 01:04:39.980 --> 01:04:39.990 align:start position:0% transactions you want as long as you 01:04:39.990 --> 01:04:44.269 align:start position:0% transactions you want as long as you update<01:04:40.710> them<01:04:40.890> and<01:04:41.130> the<01:04:41.460> TX<01:04:41.970> interpreter<01:04:43.279> so 01:04:44.269 --> 01:04:44.279 align:start position:0% update them and the TX interpreter so 01:04:44.279 --> 01:04:47.150 align:start position:0% update them and the TX interpreter so what<01:04:44.549> is<01:04:44.700> M<01:04:44.940> well<01:04:45.450> it's<01:04:45.750> it's<01:04:46.319> a<01:04:46.410> place<01:04:46.740> to<01:04:46.859> work 01:04:47.150 --> 01:04:47.160 align:start position:0% what is M well it's it's a place to work 01:04:47.160 --> 01:04:49.250 align:start position:0% what is M well it's it's a place to work multi<01:04:47.520> Merkle<01:04:47.849> proof<01:04:48.089> and<01:04:48.480> it's<01:04:48.809> kind<01:04:48.990> of<01:04:49.020> born 01:04:49.250 --> 01:04:49.260 align:start position:0% multi Merkle proof and it's kind of born 01:04:49.260 --> 01:04:51.230 align:start position:0% multi Merkle proof and it's kind of born from<01:04:49.589> the<01:04:50.010> simple<01:04:50.549> serialized 01:04:51.230 --> 01:04:51.240 align:start position:0% from the simple serialized 01:04:51.240 --> 01:04:53.000 align:start position:0% from the simple serialized algorithm<01:04:51.750> for<01:04:51.930> Merkel<01:04:52.289> Ising<01:04:52.559> very<01:04:52.770> large 01:04:53.000 --> 01:04:53.010 align:start position:0% algorithm for Merkel Ising very large 01:04:53.010 --> 01:04:56.059 align:start position:0% algorithm for Merkel Ising very large lists<01:04:53.460> it's<01:04:54.240> it<01:04:54.809> uses<01:04:55.140> a<01:04:55.200> sparse<01:04:55.470> Merkle<01:04:55.859> tree 01:04:56.059 --> 01:04:56.069 align:start position:0% lists it's it uses a sparse Merkle tree 01:04:56.069 --> 01:04:57.980 align:start position:0% lists it's it uses a sparse Merkle tree and<01:04:56.220> it's<01:04:56.390> verbalizes<01:04:57.390> things<01:04:57.599> in<01:04:57.720> the<01:04:57.809> same 01:04:57.980 --> 01:04:57.990 align:start position:0% and it's verbalizes things in the same 01:04:57.990 --> 01:04:59.960 align:start position:0% and it's verbalizes things in the same way<01:04:58.049> that<01:04:58.410> this<01:04:58.650> is<01:04:58.829> suspect<01:04:59.430> appliance<01:04:59.880> like 01:04:59.960 --> 01:04:59.970 align:start position:0% way that this is suspect appliance like 01:04:59.970 --> 01:05:02.150 align:start position:0% way that this is suspect appliance like Merkel's<01:05:00.359> Asia<01:05:00.510> to<01:05:00.660> happen<01:05:01.020> and<01:05:02.010> it's 01:05:02.150 --> 01:05:02.160 align:start position:0% Merkel's Asia to happen and it's 01:05:02.160 --> 01:05:04.130 align:start position:0% Merkel's Asia to happen and it's optimized<01:05:02.910> to<01:05:03.089> perform<01:05:03.450> read<01:05:03.690> rights<01:05:03.930> of 01:05:04.130 --> 01:05:04.140 align:start position:0% optimized to perform read rights of 01:05:04.140 --> 01:05:06.019 align:start position:0% optimized to perform read rights of reading<01:05:04.380> in<01:05:04.500> place<01:05:04.799> because<01:05:05.490> the<01:05:05.789> original 01:05:06.019 --> 01:05:06.029 align:start position:0% reading in place because the original 01:05:06.029 --> 01:05:07.970 align:start position:0% reading in place because the original iteration<01:05:06.359> of<01:05:06.750> this<01:05:06.869> execution<01:05:07.380> environment 01:05:07.970 --> 01:05:07.980 align:start position:0% iteration of this execution environment 01:05:07.980 --> 01:05:11.450 align:start position:0% iteration of this execution environment I<01:05:08.099> just<01:05:08.339> use<01:05:08.490> the<01:05:08.609> hash<01:05:08.789> table<01:05:09.089> to<01:05:10.069> back<01:05:11.069> all<01:05:11.400> of 01:05:11.450 --> 01:05:11.460 align:start position:0% I just use the hash table to back all of 01:05:11.460 --> 01:05:14.450 align:start position:0% I just use the hash table to back all of my<01:05:11.849> notes<01:05:12.630> my<01:05:12.960> murder<01:05:13.200> weapon<01:05:13.650> I<01:05:13.859> found<01:05:14.309> that 01:05:14.450 --> 01:05:14.460 align:start position:0% my notes my murder weapon I found that 01:05:14.460 --> 01:05:16.880 align:start position:0% my notes my murder weapon I found that the<01:05:14.579> execution<01:05:14.849> environment<01:05:15.599> was<01:05:16.380> dominated 01:05:16.880 --> 01:05:16.890 align:start position:0% the execution environment was dominated 01:05:16.890 --> 01:05:19.010 align:start position:0% the execution environment was dominated by<01:05:16.920> mental<01:05:17.279> coffees<01:05:17.579> and<01:05:17.789> so<01:05:17.940> that's<01:05:18.660> not<01:05:18.809> what 01:05:19.010 --> 01:05:19.020 align:start position:0% by mental coffees and so that's not what 01:05:19.020 --> 01:05:20.900 align:start position:0% by mental coffees and so that's not what we<01:05:19.109> want<01:05:19.380> we<01:05:19.470> want<01:05:19.529> to<01:05:19.829> kind<01:05:20.490> of<01:05:20.520> choose<01:05:20.700> like 01:05:20.900 --> 01:05:20.910 align:start position:0% we want we want to kind of choose like 01:05:20.910 --> 01:05:22.099 align:start position:0% we want we want to kind of choose like in<01:05:21.000> admitted<01:05:21.329> environments<01:05:21.839> and<01:05:21.930> take 01:05:22.099 --> 01:05:22.109 align:start position:0% in admitted environments and take 01:05:22.109 --> 01:05:23.630 align:start position:0% in admitted environments and take advantage<01:05:22.319> of<01:05:22.529> every<01:05:22.740> cyclist<01:05:23.220> I'm<01:05:23.369> doing<01:05:23.579> in 01:05:23.630 --> 01:05:23.640 align:start position:0% advantage of every cyclist I'm doing in 01:05:23.640 --> 01:05:25.490 align:start position:0% advantage of every cyclist I'm doing in a<01:05:23.700> place<01:05:23.819> there<01:05:24.569> that's<01:05:24.779> even<01:05:24.990> more<01:05:25.020> efficient 01:05:25.490 --> 01:05:25.500 align:start position:0% a place there that's even more efficient 01:05:25.500 --> 01:05:28.460 align:start position:0% a place there that's even more efficient and<01:05:25.559> so<01:05:26.130> the<01:05:26.660> the<01:05:27.660> citation<01:05:28.140> here<01:05:28.260> is<01:05:28.319> for 01:05:28.460 --> 01:05:28.470 align:start position:0% and so the the citation here is for 01:05:28.470 --> 01:05:29.839 align:start position:0% and so the the citation here is for proto<01:05:28.650> MZ<01:05:29.069> kind<01:05:29.279> of<01:05:29.339> came<01:05:29.520> up<01:05:29.609> with<01:05:29.760> this 01:05:29.839 --> 01:05:29.849 align:start position:0% proto MZ kind of came up with this 01:05:29.849 --> 01:05:31.579 align:start position:0% proto MZ kind of came up with this method<01:05:30.029> so<01:05:30.390> this<01:05:30.569> is<01:05:30.690> like<01:05:30.809> a<01:05:30.839> github<01:05:31.200> link<01:05:31.230> to 01:05:31.579 --> 01:05:31.589 align:start position:0% method so this is like a github link to 01:05:31.589 --> 01:05:34.039 align:start position:0% method so this is like a github link to his<01:05:32.150> repo<01:05:33.150> Arif<01:05:33.420> like<01:05:33.599> first<01:05:33.839> kind<01:05:34.020> of 01:05:34.039 --> 01:05:34.049 align:start position:0% his repo Arif like first kind of 01:05:34.049 --> 01:05:36.620 align:start position:0% his repo Arif like first kind of describes<01:05:34.410> it<01:05:34.619> and<01:05:35.520> we<01:05:36.000> kind<01:05:36.119> of<01:05:36.210> come<01:05:36.359> back<01:05:36.390> to 01:05:36.620 --> 01:05:36.630 align:start position:0% describes it and we kind of come back to 01:05:36.630 --> 01:05:40.069 align:start position:0% describes it and we kind of come back to this<01:05:36.750> but<01:05:36.960> let's<01:05:37.170> do<01:05:37.430> an<01:05:38.430> SSD<01:05:38.760> review<01:05:39.270> as 01:05:40.069 --> 01:05:40.079 align:start position:0% this but let's do an SSD review as 01:05:40.079 --> 01:05:42.329 align:start position:0% this but let's do an SSD review as everyone 01:05:42.329 --> 01:05:42.339 align:start position:0% everyone 01:05:42.339 --> 01:05:47.559 align:start position:0% everyone good<01:05:43.930> good<01:05:45.670> ok<01:05:46.670> so<01:05:46.700> I'm<01:05:47.119> just<01:05:47.150> going<01:05:47.359> to<01:05:47.420> kind 01:05:47.559 --> 01:05:47.569 align:start position:0% good good ok so I'm just going to kind 01:05:47.569 --> 01:05:48.819 align:start position:0% good good ok so I'm just going to kind of<01:05:47.599> go<01:05:47.690> over<01:05:47.749> like<01:05:47.930> how<01:05:48.049> containers<01:05:48.529> working 01:05:48.819 --> 01:05:48.829 align:start position:0% of go over like how containers working 01:05:48.829 --> 01:05:50.890 align:start position:0% of go over like how containers working as<01:05:48.950> a<01:05:48.979> Z<01:05:49.219> because<01:05:49.489> that's<01:05:49.700> what<01:05:49.999> I<01:05:50.239> really<01:05:50.569> how 01:05:50.890 --> 01:05:50.900 align:start position:0% as a Z because that's what I really how 01:05:50.900 --> 01:05:52.299 align:start position:0% as a Z because that's what I really how this<01:05:51.440> works<01:05:51.650> that's<01:05:51.769> what<01:05:51.890> I<01:05:51.920> really<01:05:52.130> care 01:05:52.299 --> 01:05:52.309 align:start position:0% this works that's what I really care 01:05:52.309 --> 01:05:55.660 align:start position:0% this works that's what I really care about<01:05:52.339> so<01:05:53.180> for<01:05:53.690> a<01:05:54.619> website<01:05:55.279> that's<01:05:55.519> kind<01:05:55.579> of 01:05:55.660 --> 01:05:55.670 align:start position:0% about so for a website that's kind of 01:05:55.670 --> 01:05:57.370 align:start position:0% about so for a website that's kind of like<01:05:55.759> the<01:05:55.969> object<01:05:56.599> that<01:05:56.959> we're<01:05:57.109> going<01:05:57.200> to<01:05:57.259> talk 01:05:57.370 --> 01:05:57.380 align:start position:0% like the object that we're going to talk 01:05:57.380 --> 01:05:59.289 align:start position:0% like the object that we're going to talk about<01:05:57.650> on<01:05:57.739> the<01:05:57.829> right<01:05:58.009> side<01:05:58.249> is<01:05:58.519> the<01:05:58.549> tree<01:05:59.119> that 01:05:59.289 --> 01:05:59.299 align:start position:0% about on the right side is the tree that 01:05:59.299 --> 01:06:01.209 align:start position:0% about on the right side is the tree that it<01:05:59.450> represents<01:05:59.930> so<01:06:00.109> an<01:06:00.289> SSD<01:06:00.619> if<01:06:00.890> I<01:06:01.009> want<01:06:01.160> to 01:06:01.209 --> 01:06:01.219 align:start position:0% it represents so an SSD if I want to 01:06:01.219 --> 01:06:04.569 align:start position:0% it represents so an SSD if I want to verbalize<01:06:01.670> an<01:06:01.969> object<01:06:02.450> it<01:06:02.509> has<01:06:02.630> one<01:06:02.869> value<01:06:03.579> 532 01:06:04.569 --> 01:06:04.579 align:start position:0% verbalize an object it has one value 532 01:06:04.579 --> 01:06:07.329 align:start position:0% verbalize an object it has one value 532 then<01:06:05.180> it's<01:06:05.599> the<01:06:06.170> roots<01:06:06.440> of<01:06:06.619> that<01:06:06.739> the<01:06:07.039> mirco 01:06:07.329 --> 01:06:07.339 align:start position:0% then it's the roots of that the mirco 01:06:07.339 --> 01:06:09.400 align:start position:0% then it's the roots of that the mirco root<01:06:07.579> of<01:06:07.700> that<01:06:07.839> container<01:06:08.839> is<01:06:09.079> actually 01:06:09.400 --> 01:06:09.410 align:start position:0% root of that container is actually 01:06:09.410 --> 01:06:11.559 align:start position:0% root of that container is actually exactly<01:06:09.680> the<01:06:09.950> value<01:06:10.459> because<01:06:10.700> it's<01:06:10.789> only<01:06:10.910> 32 01:06:11.559 --> 01:06:11.569 align:start position:0% exactly the value because it's only 32 01:06:11.569 --> 01:06:13.449 align:start position:0% exactly the value because it's only 32 bytes<01:06:11.839> in<01:06:12.109> each<01:06:12.200> node<01:06:12.499> and<01:06:12.559> the<01:06:12.859> vertical<01:06:13.069> tree 01:06:13.449 --> 01:06:13.459 align:start position:0% bytes in each node and the vertical tree 01:06:13.459 --> 01:06:16.839 align:start position:0% bytes in each node and the vertical tree for<01:06:13.759> SSE<01:06:14.180> is<01:06:14.269> 32<01:06:14.630> bytes<01:06:15.549> if<01:06:16.549> we<01:06:16.700> have<01:06:16.819> a 01:06:16.839 --> 01:06:16.849 align:start position:0% for SSE is 32 bytes if we have a 01:06:16.849 --> 01:06:18.279 align:start position:0% for SSE is 32 bytes if we have a container<01:06:17.119> with<01:06:17.239> two<01:06:17.269> elements<01:06:17.569> and<01:06:18.109> these 01:06:18.279 --> 01:06:18.289 align:start position:0% container with two elements and these 01:06:18.289 --> 01:06:20.079 align:start position:0% container with two elements and these are<01:06:18.440> you<01:06:18.650> one<01:06:18.859> two<01:06:18.979> weeks<01:06:19.249> that's<01:06:19.430> only<01:06:19.670> 16 01:06:20.079 --> 01:06:20.089 align:start position:0% are you one two weeks that's only 16 01:06:20.089 --> 01:06:23.469 align:start position:0% are you one two weeks that's only 16 bytes<01:06:20.329> we<01:06:21.200> verbalize<01:06:21.650> it<01:06:21.709> where<01:06:22.369> it's<01:06:23.209> got<01:06:23.450> a 01:06:23.469 --> 01:06:23.479 align:start position:0% bytes we verbalize it where it's got a 01:06:23.479 --> 01:06:26.859 align:start position:0% bytes we verbalize it where it's got a tree<01:06:24.019> of<01:06:24.369> one<01:06:25.369> depth<01:06:25.640> and<01:06:25.910> two<01:06:26.089> children<01:06:26.359> so 01:06:26.859 --> 01:06:26.869 align:start position:0% tree of one depth and two children so 01:06:26.869 --> 01:06:28.630 align:start position:0% tree of one depth and two children so because<01:06:27.440> there<01:06:27.559> are<01:06:27.650> 16<01:06:27.979> bytes<01:06:28.160> of<01:06:28.279> a<01:06:28.309> theory 01:06:28.630 --> 01:06:28.640 align:start position:0% because there are 16 bytes of a theory 01:06:28.640 --> 01:06:30.249 align:start position:0% because there are 16 bytes of a theory that<01:06:28.849> could<01:06:29.029> put<01:06:29.359> them<01:06:29.479> together<01:06:29.630> into<01:06:30.079> one 01:06:30.249 --> 01:06:30.259 align:start position:0% that could put them together into one 01:06:30.259 --> 01:06:33.729 align:start position:0% that could put them together into one node<01:06:30.469> like<01:06:30.769> we<01:06:31.339> had<01:06:31.579> here<01:06:32.410> but<01:06:33.410> for<01:06:33.619> like 01:06:33.729 --> 01:06:33.739 align:start position:0% node like we had here but for like 01:06:33.739 --> 01:06:35.319 align:start position:0% node like we had here but for like accessories<01:06:34.190> and<01:06:34.430> improving<01:06:34.789> reasons<01:06:35.150> it's 01:06:35.319 --> 01:06:35.329 align:start position:0% accessories and improving reasons it's 01:06:35.329 --> 01:06:37.029 align:start position:0% accessories and improving reasons it's better<01:06:35.509> to<01:06:35.749> split<01:06:35.930> it<01:06:36.079> out<01:06:36.229> split<01:06:36.890> the 01:06:37.029 --> 01:06:37.039 align:start position:0% better to split it out split the 01:06:37.039 --> 01:06:39.430 align:start position:0% better to split it out split the containers<01:06:37.459> out<01:06:37.579> based<01:06:37.849> on<01:06:38.109> each<01:06:39.109> of<01:06:39.170> the 01:06:39.430 --> 01:06:39.440 align:start position:0% containers out based on each of the 01:06:39.440 --> 01:06:42.729 align:start position:0% containers out based on each of the members<01:06:39.769> of<01:06:39.799> the<01:06:40.339> container<01:06:41.349> so<01:06:42.349> for<01:06:42.559> lists 01:06:42.729 --> 01:06:42.739 align:start position:0% members of the container so for lists 01:06:42.739 --> 01:06:43.930 align:start position:0% members of the container so for lists you<01:06:42.979> can<01:06:43.039> see<01:06:43.279> that<01:06:43.430> it<01:06:43.519> has<01:06:43.549> the<01:06:43.729> same 01:06:43.930 --> 01:06:43.940 align:start position:0% you can see that it has the same 01:06:43.940 --> 01:06:45.789 align:start position:0% you can see that it has the same structure<01:06:44.329> even<01:06:44.809> though<01:06:45.019> now<01:06:45.229> it<01:06:45.410> has<01:06:45.529> three 01:06:45.789 --> 01:06:45.799 align:start position:0% structure even though now it has three 01:06:45.799 --> 01:06:47.199 align:start position:0% structure even though now it has three elements<01:06:45.829> so<01:06:46.339> on<01:06:46.430> the<01:06:46.519> right<01:06:46.699> side<01:06:46.729> that<01:06:46.940> set 01:06:47.199 --> 01:06:47.209 align:start position:0% elements so on the right side that set 01:06:47.209 --> 01:06:48.519 align:start position:0% elements so on the right side that set at<01:06:47.359> maximum<01:06:47.749> elements<01:06:48.079> you<01:06:48.140> can<01:06:48.259> have<01:06:48.380> in<01:06:48.469> this 01:06:48.519 --> 01:06:48.529 align:start position:0% at maximum elements you can have in this 01:06:48.529 --> 01:06:50.739 align:start position:0% at maximum elements you can have in this list<01:06:48.829> and<01:06:49.099> here<01:06:49.880> it's<01:06:49.999> the<01:06:50.089> same<01:06:50.239> structure<01:06:50.719> as 01:06:50.739 --> 01:06:50.749 align:start position:0% list and here it's the same structure as 01:06:50.749 --> 01:06:52.359 align:start position:0% list and here it's the same structure as the<01:06:50.869> container<01:06:51.289> and<01:06:51.469> developments<01:06:52.130> of<01:06:52.279> the 01:06:52.359 --> 01:06:52.369 align:start position:0% the container and developments of the 01:06:52.369 --> 01:06:54.069 align:start position:0% the container and developments of the same<01:06:52.579> size<01:06:52.849> and<01:06:53.390> the<01:06:53.509> reason<01:06:53.779> is<01:06:53.900> is<01:06:54.049> because 01:06:54.069 --> 01:06:54.079 align:start position:0% same size and the reason is is because 01:06:54.079 --> 01:06:56.799 align:start position:0% same size and the reason is is because here<01:06:54.559> in<01:06:54.619> that<01:06:54.709> left<01:06:54.949> node<01:06:55.130> we're<01:06:55.309> packing<01:06:55.809> all 01:06:56.799 --> 01:06:56.809 align:start position:0% here in that left node we're packing all 01:06:56.809 --> 01:06:59.019 align:start position:0% here in that left node we're packing all two<01:06:57.410> values<01:06:57.769> in<01:06:57.890> them<01:06:58.009> because<01:06:58.219> they<01:06:58.309> 32<01:06:58.819> bytes 01:06:59.019 --> 01:06:59.029 align:start position:0% two values in them because they 32 bytes 01:06:59.029 --> 01:07:00.699 align:start position:0% two values in them because they 32 bytes in<01:06:59.180> total<01:06:59.539> and<01:06:59.779> on<01:07:00.079> the<01:07:00.170> right<01:07:00.319> we<01:07:00.469> only<01:07:00.499> have 01:07:00.699 --> 01:07:00.709 align:start position:0% in total and on the right we only have 01:07:00.709 --> 01:07:06.069 align:start position:0% in total and on the right we only have one<01:07:00.949> value<01:07:01.400> and<01:07:01.670> 16<01:07:02.059> bytes<01:07:02.299> of<01:07:02.449> padding<01:07:04.900> so<01:07:05.900> now 01:07:06.069 --> 01:07:06.079 align:start position:0% one value and 16 bytes of padding so now 01:07:06.079 --> 01:07:07.749 align:start position:0% one value and 16 bytes of padding so now as<01:07:06.349> we<01:07:06.469> grow<01:07:06.619> to<01:07:06.680> another<01:07:07.099> container<01:07:07.400> that's<01:07:07.729> a 01:07:07.749 --> 01:07:07.759 align:start position:0% as we grow to another container that's a 01:07:07.759 --> 01:07:08.920 align:start position:0% as we grow to another container that's a little<01:07:07.880> bit<01:07:07.999> bigger<01:07:08.180> you<01:07:08.269> can<01:07:08.479> kind<01:07:08.660> of<01:07:08.690> see 01:07:08.920 --> 01:07:08.930 align:start position:0% little bit bigger you can kind of see 01:07:08.930 --> 01:07:11.439 align:start position:0% little bit bigger you can kind of see that<01:07:09.170> the<01:07:09.739> number<01:07:10.249> of<01:07:10.339> leaves<01:07:10.549> is<01:07:10.880> equal<01:07:11.209> to 01:07:11.439 --> 01:07:11.449 align:start position:0% that the number of leaves is equal to 01:07:11.449 --> 01:07:13.930 align:start position:0% that the number of leaves is equal to the<01:07:12.289> next<01:07:12.650> power<01:07:12.829> of<01:07:13.069> two<01:07:13.249> of<01:07:13.519> the<01:07:13.609> number<01:07:13.910> of 01:07:13.930 --> 01:07:13.940 align:start position:0% the next power of two of the number of 01:07:13.940 --> 01:07:15.960 align:start position:0% the next power of two of the number of elements<01:07:14.390> you<01:07:14.539> have<01:07:14.599> in<01:07:14.959> your<01:07:15.049> container<01:07:15.380> so 01:07:15.960 --> 01:07:15.970 align:start position:0% elements you have in your container so 01:07:15.970 --> 01:07:18.180 align:start position:0% elements you have in your container so three<01:07:16.390> elements<01:07:16.510> the<01:07:16.900> next<01:07:17.109> part<01:07:17.290> is<01:07:17.560> four<01:07:17.950> and 01:07:18.180 --> 01:07:18.190 align:start position:0% three elements the next part is four and 01:07:18.190 --> 01:07:21.960 align:start position:0% three elements the next part is four and we<01:07:19.000> have<01:07:19.150> each<01:07:19.359> a<01:07:19.480> note<01:07:19.690> being<01:07:20.280> the<01:07:21.280> values<01:07:21.670> in 01:07:21.960 --> 01:07:21.970 align:start position:0% we have each a note being the values in 01:07:21.970 --> 01:07:23.849 align:start position:0% we have each a note being the values in the<01:07:22.090> container<01:07:22.450> padded<01:07:23.109> to<01:07:23.230> sixteen<01:07:23.590> bytes 01:07:23.849 --> 01:07:23.859 align:start position:0% the container padded to sixteen bytes 01:07:23.859 --> 01:07:27.150 align:start position:0% the container padded to sixteen bytes since<01:07:24.250> there<01:07:24.940> you<01:07:25.119> want<01:07:25.359> you<01:07:25.900> 128<01:07:26.470> and<01:07:26.890> then 01:07:27.150 --> 01:07:27.160 align:start position:0% since there you want you 128 and then 01:07:27.160 --> 01:07:29.130 align:start position:0% since there you want you 128 and then the<01:07:27.310> last<01:07:27.490> note<01:07:27.730> here<01:07:27.760> is<01:07:28.060> just<01:07:28.240> a<01:07:28.330> zero<01:07:28.750> padded 01:07:29.130 --> 01:07:29.140 align:start position:0% the last note here is just a zero padded 01:07:29.140 --> 01:07:30.320 align:start position:0% the last note here is just a zero padded note 01:07:30.320 --> 01:07:30.330 align:start position:0% note 01:07:30.330 --> 01:07:33.359 align:start position:0% note so<01:07:31.330> when<01:07:31.450> she's<01:07:31.720> there's<01:07:32.020> the<01:07:32.890> concept<01:07:33.310> of 01:07:33.359 --> 01:07:33.369 align:start position:0% so when she's there's the concept of 01:07:33.369 --> 01:07:35.190 align:start position:0% so when she's there's the concept of accounts<01:07:33.910> and<01:07:34.119> this<01:07:34.420> is<01:07:34.599> what<01:07:34.750> the<01:07:34.900> account 01:07:35.190 --> 01:07:35.200 align:start position:0% accounts and this is what the account 01:07:35.200 --> 01:07:37.680 align:start position:0% accounts and this is what the account reishi<01:07:35.619> looks<01:07:35.890> like<01:07:36.099> so<01:07:36.640> every<01:07:37.030> leaf<01:07:37.240> of<01:07:37.510> my 01:07:37.680 --> 01:07:37.690 align:start position:0% reishi looks like so every leaf of my 01:07:37.690 --> 01:07:39.810 align:start position:0% reishi looks like so every leaf of my sparse<01:07:38.050> marquetry<01:07:38.590> is<01:07:38.980> that<01:07:39.250> roots<01:07:39.490> where 01:07:39.810 --> 01:07:39.820 align:start position:0% sparse marquetry is that roots where 01:07:39.820 --> 01:07:41.820 align:start position:0% sparse marquetry is that roots where they<01:07:39.910> count<01:07:40.150> and<01:07:40.450> it<01:07:41.050> has<01:07:41.230> this<01:07:41.560> kind<01:07:41.619> of 01:07:41.820 --> 01:07:41.830 align:start position:0% they count and it has this kind of 01:07:41.830 --> 01:07:45.060 align:start position:0% they count and it has this kind of structure<01:07:42.160> so<01:07:42.520> the<01:07:43.150> bottom<01:07:44.109> left<01:07:44.380> to<01:07:44.470> note<01:07:44.800> is 01:07:45.060 --> 01:07:45.070 align:start position:0% structure so the bottom left to note is 01:07:45.070 --> 01:07:47.210 align:start position:0% structure so the bottom left to note is the<01:07:45.160> whites<01:07:45.369> 48<01:07:45.760> that's<01:07:45.910> the<01:07:46.090> VLS<01:07:46.510> public<01:07:46.869> key 01:07:47.210 --> 01:07:47.220 align:start position:0% the whites 48 that's the VLS public key 01:07:47.220 --> 01:07:49.500 align:start position:0% the whites 48 that's the VLS public key then<01:07:48.220> we've<01:07:48.340> got<01:07:48.460> the<01:07:48.580> knowledge<01:07:48.760> that<01:07:48.910> value 01:07:49.500 --> 01:07:49.510 align:start position:0% then we've got the knowledge that value 01:07:49.510 --> 01:07:51.599 align:start position:0% then we've got the knowledge that value and<01:07:49.810> then<01:07:49.930> the<01:07:50.380> way<01:07:50.500> that<01:07:50.530> SNC<01:07:50.950> Merck<01:07:51.190> Eliza's 01:07:51.599 --> 01:07:51.609 align:start position:0% and then the way that SNC Merck Eliza's 01:07:51.609 --> 01:07:53.280 align:start position:0% and then the way that SNC Merck Eliza's things<01:07:51.849> like<01:07:52.090> we<01:07:52.210> saw<01:07:52.359> on<01:07:52.390> a<01:07:52.570> last<01:07:52.780> slide<01:07:53.020> is 01:07:53.280 --> 01:07:53.290 align:start position:0% things like we saw on a last slide is 01:07:53.290 --> 01:07:55.650 align:start position:0% things like we saw on a last slide is we've<01:07:53.890> got<01:07:54.040> the<01:07:54.130> padding<01:07:54.520> here<01:07:54.790> for<01:07:55.599> the 01:07:55.650 --> 01:07:55.660 align:start position:0% we've got the padding here for the 01:07:55.660 --> 01:08:00.150 align:start position:0% we've got the padding here for the fourth<01:07:56.650> wave<01:07:58.020> so<01:07:59.020> if<01:07:59.080> I<01:07:59.170> want<01:07:59.320> to<01:07:59.349> prove<01:07:59.950> an 01:08:00.150 --> 01:08:00.160 align:start position:0% fourth wave so if I want to prove an 01:08:00.160 --> 01:08:02.640 align:start position:0% fourth wave so if I want to prove an account<01:08:00.460> value<01:08:00.700> then<01:08:01.330> all<01:08:01.960> I<01:08:02.020> need<01:08:02.140> is<01:08:02.470> I<01:08:02.590> just 01:08:02.640 --> 01:08:02.650 align:start position:0% account value then all I need is I just 01:08:02.650 --> 01:08:04.560 align:start position:0% account value then all I need is I just need<01:08:02.920> these<01:08:03.099> three<01:08:03.369> notes<01:08:03.580> I<01:08:03.880> mean<01:08:04.030> that's<01:08:04.510> a 01:08:04.560 --> 01:08:04.570 align:start position:0% need these three notes I mean that's a 01:08:04.570 --> 01:08:06.720 align:start position:0% need these three notes I mean that's a lot<01:08:04.750> left<01:08:05.020> note<01:08:05.290> and<01:08:05.619> I<01:08:05.920> need<01:08:06.099> the<01:08:06.250> value<01:08:06.550> note 01:08:06.720 --> 01:08:06.730 align:start position:0% lot left note and I need the value note 01:08:06.730 --> 01:08:08.280 align:start position:0% lot left note and I need the value note and<01:08:06.940> then<01:08:07.030> the<01:08:07.570> padding<01:08:07.750> note<01:08:08.080> and 01:08:08.280 --> 01:08:08.290 align:start position:0% and then the padding note and 01:08:08.290 --> 01:08:10.080 align:start position:0% and then the padding note and theoretically<01:08:09.070> we<01:08:09.369> don't<01:08:09.550> really<01:08:09.790> need<01:08:09.970> the 01:08:10.080 --> 01:08:10.090 align:start position:0% theoretically we don't really need the 01:08:10.090 --> 01:08:13.950 align:start position:0% theoretically we don't really need the padding<01:08:10.420> notice<01:08:10.780> is<01:08:10.900> just<01:08:11.080> zeros<01:08:12.660> so<01:08:13.660> what 01:08:13.950 --> 01:08:13.960 align:start position:0% padding notice is just zeros so what 01:08:13.960 --> 01:08:16.559 align:start position:0% padding notice is just zeros so what does<01:08:14.140> the<01:08:14.440> like<01:08:14.650> steets<01:08:15.099> tree<01:08:15.640> for<01:08:16.000> sheep<01:08:16.330> look 01:08:16.559 --> 01:08:16.569 align:start position:0% does the like steets tree for sheep look 01:08:16.569 --> 01:08:18.990 align:start position:0% does the like steets tree for sheep look like<01:08:16.779> or<01:08:17.290> like<01:08:17.799> just<01:08:17.830> a<01:08:18.190> general<01:08:18.520> execution 01:08:18.990 --> 01:08:19.000 align:start position:0% like or like just a general execution 01:08:19.000 --> 01:08:21.209 align:start position:0% like or like just a general execution apartment<01:08:19.420> well<01:08:19.600> the<01:08:20.380> way<01:08:20.739> that<01:08:20.950> I've<01:08:21.009> gone 01:08:21.209 --> 01:08:21.219 align:start position:0% apartment well the way that I've gone 01:08:21.219 --> 01:08:22.559 align:start position:0% apartment well the way that I've gone through<01:08:21.430> out<01:08:21.700> my<01:08:21.730> phone<01:08:22.000> down<01:08:22.210> is<01:08:22.330> that<01:08:22.420> it's 01:08:22.559 --> 01:08:22.569 align:start position:0% through out my phone down is that it's 01:08:22.569 --> 01:08:24.180 align:start position:0% through out my phone down is that it's going<01:08:22.839> to<01:08:22.930> be<01:08:23.049> as<01:08:23.140> far<01:08:23.319> as<01:08:23.380> Merkle<01:08:23.710> tree<01:08:23.920> and<01:08:24.069> so 01:08:24.180 --> 01:08:24.190 align:start position:0% going to be as far as Merkle tree and so 01:08:24.190 --> 01:08:25.620 align:start position:0% going to be as far as Merkle tree and so I<01:08:24.489> don't<01:08:24.730> know<01:08:24.819> if<01:08:24.910> you<01:08:24.969> can<01:08:25.089> read<01:08:25.270> this<01:08:25.390> but<01:08:25.509> it 01:08:25.620 --> 01:08:25.630 align:start position:0% I don't know if you can read this but it 01:08:25.630 --> 01:08:28.440 align:start position:0% I don't know if you can read this but it says<01:08:25.810> the<01:08:25.989> list<01:08:26.200> of<01:08:26.469> accounts<01:08:27.430> which<01:08:27.880> was<01:08:28.120> this 01:08:28.440 --> 01:08:28.450 align:start position:0% says the list of accounts which was this 01:08:28.450 --> 01:08:30.570 align:start position:0% says the list of accounts which was this structure<01:08:28.870> and<01:08:29.230> there's<01:08:29.890> two<01:08:30.069> to<01:08:30.130> the<01:08:30.310> tune<01:08:30.520> of 01:08:30.570 --> 01:08:30.580 align:start position:0% structure and there's two to the tune of 01:08:30.580 --> 01:08:33.510 align:start position:0% structure and there's two to the tune of 56<01:08:31.089> of<01:08:31.239> those<01:08:31.359> accounts<01:08:32.040> and<01:08:33.040> so<01:08:33.219> like<01:08:33.370> what 01:08:33.510 --> 01:08:33.520 align:start position:0% 56 of those accounts and so like what 01:08:33.520 --> 01:08:34.530 align:start position:0% 56 of those accounts and so like what does<01:08:33.609> that<01:08:33.670> look<01:08:33.910> like 01:08:34.530 --> 01:08:34.540 align:start position:0% does that look like 01:08:34.540 --> 01:08:36.840 align:start position:0% does that look like it's<01:08:35.109> too<01:08:35.410> big<01:08:35.589> filling<01:08:35.920> slide<01:08:36.130> so<01:08:36.430> just<01:08:36.700> like 01:08:36.840 --> 01:08:36.850 align:start position:0% it's too big filling slide so just like 01:08:36.850 --> 01:08:38.849 align:start position:0% it's too big filling slide so just like I<01:08:37.060> don't<01:08:37.540> believe<01:08:37.690> it<01:08:37.779> occur<01:08:38.259> I<01:08:38.440> don't<01:08:38.770> think 01:08:38.849 --> 01:08:38.859 align:start position:0% I don't believe it occur I don't think 01:08:38.859 --> 01:08:40.740 align:start position:0% I don't believe it occur I don't think thought<01:08:39.160> in<01:08:39.310> your<01:08:39.400> head<01:08:39.460> but<01:08:40.239> if<01:08:40.420> we<01:08:40.540> were<01:08:40.690> to 01:08:40.740 --> 01:08:40.750 align:start position:0% thought in your head but if we were to 01:08:40.750 --> 01:08:41.910 align:start position:0% thought in your head but if we were to kind<01:08:40.989> of<01:08:41.109> do<01:08:41.259> it<01:08:41.380> it<01:08:41.469> might<01:08:41.589> look<01:08:41.859> something 01:08:41.910 --> 01:08:41.920 align:start position:0% kind of do it it might look something 01:08:41.920 --> 01:08:44.519 align:start position:0% kind of do it it might look something like<01:08:42.310> this<01:08:42.670> where<01:08:43.330> at<01:08:43.509> the<01:08:43.630> very<01:08:43.660> top<01:08:44.140> of<01:08:44.200> a 01:08:44.519 --> 01:08:44.529 align:start position:0% like this where at the very top of a 01:08:44.529 --> 01:08:47.400 align:start position:0% like this where at the very top of a tree<01:08:44.710> that<01:08:44.739> has<01:08:44.920> 256<01:08:45.790> steps<01:08:46.210> you've<01:08:47.140> got<01:08:47.380> a 01:08:47.400 --> 01:08:47.410 align:start position:0% tree that has 256 steps you've got a 01:08:47.410 --> 01:08:48.710 align:start position:0% tree that has 256 steps you've got a roots<01:08:47.799> and<01:08:48.069> then<01:08:48.190> like 01:08:48.710 --> 01:08:48.720 align:start position:0% roots and then like 01:08:48.720 --> 01:08:50.360 align:start position:0% roots and then like if<01:08:48.900> you<01:08:49.020> take<01:08:49.200> last<01:08:49.470> ten<01:08:49.650> or<01:08:49.710> fifty<01:08:49.950> six<01:08:50.160> times 01:08:50.360 --> 01:08:50.370 align:start position:0% if you take last ten or fifty six times 01:08:50.370 --> 01:08:51.980 align:start position:0% if you take last ten or fifty six times you'll<01:08:50.640> get<01:08:50.790> to<01:08:50.970> account<01:08:51.330> with<01:08:51.450> address<01:08:51.720> zero 01:08:51.980 --> 01:08:51.990 align:start position:0% you'll get to account with address zero 01:08:51.990 --> 01:08:55.400 align:start position:0% you'll get to account with address zero if<01:08:52.950> you<01:08:53.100> go<01:08:53.220> right<01:08:53.490> 256<01:08:54.330> times<01:08:54.540> you<01:08:54.750> get<01:08:54.870> to<01:08:55.020> an 01:08:55.400 --> 01:08:55.410 align:start position:0% if you go right 256 times you get to an 01:08:55.410 --> 01:08:58.520 align:start position:0% if you go right 256 times you get to an account<01:08:55.790> root<01:08:56.790> node<01:08:56.970> with<01:08:57.210> address<01:08:57.840> up<01:08:58.230> to<01:08:58.380> to 01:08:58.520 --> 01:08:58.530 align:start position:0% account root node with address up to to 01:08:58.530 --> 01:09:02.960 align:start position:0% account root node with address up to to the<01:08:58.620> 256<01:08:59.280> minus<01:09:00.180> one<01:09:01.310> so<01:09:02.310> back<01:09:02.550> to<01:09:02.580> the<01:09:02.880> in 01:09:02.960 --> 01:09:02.970 align:start position:0% the 256 minus one so back to the in 01:09:02.970 --> 01:09:06.200 align:start position:0% the 256 minus one so back to the in format<01:09:03.710> in<01:09:04.710> format<01:09:05.160> that<01:09:05.280> lets<01:09:05.550> us<01:09:05.730> do<01:09:06.000> in 01:09:06.200 --> 01:09:06.210 align:start position:0% format in format that lets us do in 01:09:06.210 --> 01:09:09.280 align:start position:0% format in format that lets us do in place<01:09:06.510> marbleization<01:09:07.260> merkel<01:09:07.740> operations 01:09:09.280 --> 01:09:09.290 align:start position:0% place marbleization merkel operations 01:09:09.290 --> 01:09:12.290 align:start position:0% place marbleization merkel operations it's<01:09:10.290> kind<01:09:10.530> of<01:09:10.620> built<01:09:10.770> into<01:09:10.920> two<01:09:11.220> two<01:09:12.120> main 01:09:12.290 --> 01:09:12.300 align:start position:0% it's kind of built into two two main 01:09:12.300 --> 01:09:14.960 align:start position:0% it's kind of built into two two main portions<01:09:12.840> this<01:09:13.080> left<01:09:13.470> portion<01:09:13.740> here<01:09:14.190> is<01:09:14.340> the 01:09:14.960 --> 01:09:14.970 align:start position:0% portions this left portion here is the 01:09:14.970 --> 01:09:16.880 align:start position:0% portions this left portion here is the offsets<01:09:15.420> and<01:09:15.690> so<01:09:15.840> the<01:09:15.930> offsets<01:09:16.320> is<01:09:16.470> what<01:09:16.650> let's 01:09:16.880 --> 01:09:16.890 align:start position:0% offsets and so the offsets is what let's 01:09:16.890 --> 01:09:19.700 align:start position:0% offsets and so the offsets is what let's just<01:09:16.980> reverse<01:09:17.460> this<01:09:18.060> passion<01:09:18.960> is<01:09:19.080> object<01:09:19.560> and 01:09:19.700 --> 01:09:19.710 align:start position:0% just reverse this passion is object and 01:09:19.710 --> 01:09:21.140 align:start position:0% just reverse this passion is object and you<01:09:19.770> can<01:09:19.890> kind<01:09:20.040> of<01:09:20.070> think<01:09:20.250> of<01:09:20.370> this<01:09:20.760> hashes 01:09:21.140 --> 01:09:21.150 align:start position:0% you can kind of think of this hashes 01:09:21.150 --> 01:09:23.630 align:start position:0% you can kind of think of this hashes object<01:09:21.600> is<01:09:21.750> like<01:09:21.930> a<01:09:21.960> continuous<01:09:22.590> array<01:09:22.980> of<01:09:23.220> 32 01:09:23.630 --> 01:09:23.640 align:start position:0% object is like a continuous array of 32 01:09:23.640 --> 01:09:26.300 align:start position:0% object is like a continuous array of 32 byte<01:09:23.940> values<01:09:24.660> and<01:09:24.960> some<01:09:25.560> of<01:09:25.650> those<01:09:25.740> values<01:09:26.130> are 01:09:26.300 --> 01:09:26.310 align:start position:0% byte values and some of those values are 01:09:26.310 --> 01:09:27.710 align:start position:0% byte values and some of those values are like<01:09:26.400> internal<01:09:26.910> nodes<01:09:27.150> of<01:09:27.330> your<01:09:27.420> vertical 01:09:27.710 --> 01:09:27.720 align:start position:0% like internal nodes of your vertical 01:09:27.720 --> 01:09:29.840 align:start position:0% like internal nodes of your vertical tree<01:09:27.900> and<01:09:28.020> some<01:09:28.170> of<01:09:28.320> our<01:09:28.590> like<01:09:28.770> in<01:09:29.100> nodes<01:09:29.550> that 01:09:29.840 --> 01:09:29.850 align:start position:0% tree and some of our like in nodes that 01:09:29.850 --> 01:09:31.760 align:start position:0% tree and some of our like in nodes that are<01:09:29.910> the<01:09:30.150> actual<01:09:30.450> values<01:09:30.600> we<01:09:31.170> care<01:09:31.410> about<01:09:31.500> like 01:09:31.760 --> 01:09:31.770 align:start position:0% are the actual values we care about like 01:09:31.770 --> 01:09:34.160 align:start position:0% are the actual values we care about like the<01:09:31.950> account<01:09:32.610> balance<01:09:33.150> the<01:09:33.330> non-set<01:09:33.780> cetera 01:09:34.160 --> 01:09:34.170 align:start position:0% the account balance the non-set cetera 01:09:34.170 --> 01:09:36.470 align:start position:0% the account balance the non-set cetera and<01:09:34.350> so<01:09:34.410> we<01:09:34.980> use<01:09:35.130> the<01:09:35.250> offsets<01:09:35.730> to<01:09:35.880> traverse 01:09:36.470 --> 01:09:36.480 align:start position:0% and so we use the offsets to traverse 01:09:36.480 --> 01:09:42.200 align:start position:0% and so we use the offsets to traverse these<01:09:36.780> hashes<01:09:37.020> I<01:09:40.850> can<01:09:41.850> run<01:09:42.000> through<01:09:42.150> this 01:09:42.200 --> 01:09:42.210 align:start position:0% these hashes I can run through this 01:09:42.210 --> 01:09:44.000 align:start position:0% these hashes I can run through this algorithm<01:09:42.540> if<01:09:42.870> people<01:09:43.320> have<01:09:43.410> questions<01:09:43.620> on 01:09:44.000 --> 01:09:44.010 align:start position:0% algorithm if people have questions on 01:09:44.010 --> 01:09:45.650 align:start position:0% algorithm if people have questions on execution<01:09:44.610> environments<01:09:45.150> and<01:09:45.240> rather<01:09:45.480> than 01:09:45.650 --> 01:09:45.660 align:start position:0% execution environments and rather than 01:09:45.660 --> 01:09:47.720 align:start position:0% execution environments and rather than see<01:09:45.780> some<01:09:45.960> questions<01:09:46.170> I<01:09:46.680> can<01:09:47.430> do<01:09:47.490> that<01:09:47.610> instead 01:09:47.720 --> 01:09:47.730 align:start position:0% see some questions I can do that instead 01:09:47.730 --> 01:09:52.970 align:start position:0% see some questions I can do that instead say<01:09:48.720> I<01:09:48.750> have<01:09:48.900> a<01:09:48.960> preference<01:09:51.680> okay<01:09:52.680> let's<01:09:52.890> run 01:09:52.970 --> 01:09:52.980 align:start position:0% say I have a preference okay let's run 01:09:52.980 --> 01:09:55.010 align:start position:0% say I have a preference okay let's run through<01:09:53.160> it<01:09:53.220> quickly<01:09:53.460> and<01:09:53.670> then<01:09:53.790> questions<01:09:54.600> so 01:09:55.010 --> 01:09:55.020 align:start position:0% through it quickly and then questions so 01:09:55.020 --> 01:09:57.800 align:start position:0% through it quickly and then questions so let's<01:09:55.530> generate<01:09:55.950> the<01:09:56.160> offsets<01:09:56.670> so<01:09:57.390> right<01:09:57.630> here 01:09:57.800 --> 01:09:57.810 align:start position:0% let's generate the offsets so right here 01:09:57.810 --> 01:09:59.180 align:start position:0% let's generate the offsets so right here I<01:09:57.840> say<01:09:58.080> we've<01:09:58.260> got<01:09:58.410> offsets<01:09:58.800> very<01:09:58.950> no<01:09:59.100> the 01:09:59.180 --> 01:09:59.190 align:start position:0% I say we've got offsets very no the 01:09:59.190 --> 01:10:00.620 align:start position:0% I say we've got offsets very no the hashes<01:09:59.550> because<01:09:59.820> we've<01:09:59.940> got<01:10:00.060> the<01:10:00.180> Merkle<01:10:00.480> tree 01:10:00.620 --> 01:10:00.630 align:start position:0% hashes because we've got the Merkle tree 01:10:00.630 --> 01:10:02.210 align:start position:0% hashes because we've got the Merkle tree I'm<01:10:01.020> going<01:10:01.170> to<01:10:01.230> figure<01:10:01.320> out<01:10:01.470> the<01:10:01.560> offsets<01:10:02.010> so 01:10:02.210 --> 01:10:02.220 align:start position:0% I'm going to figure out the offsets so 01:10:02.220 --> 01:10:04.970 align:start position:0% I'm going to figure out the offsets so that<01:10:02.400> we<01:10:02.490> can<01:10:02.670> later<01:10:03.330> traverse<01:10:03.750> it<01:10:03.960> so<01:10:04.530> we<01:10:04.830> can 01:10:04.970 --> 01:10:04.980 align:start position:0% that we can later traverse it so we can 01:10:04.980 --> 01:10:08.600 align:start position:0% that we can later traverse it so we can think<01:10:05.190> of<01:10:05.310> a<01:10:05.550> Mirko<01:10:05.850> tree<01:10:06.120> of<01:10:06.480> depth<01:10:07.340> 3<01:10:08.340> here 01:10:08.600 --> 01:10:08.610 align:start position:0% think of a Mirko tree of depth 3 here 01:10:08.610 --> 01:10:11.000 align:start position:0% think of a Mirko tree of depth 3 here and<01:10:08.910> we<01:10:09.540> can<01:10:09.660> think<01:10:09.780> of<01:10:09.930> these<01:10:10.290> numbers<01:10:10.860> is 01:10:11.000 --> 01:10:11.010 align:start position:0% and we can think of these numbers is 01:10:11.010 --> 01:10:12.470 align:start position:0% and we can think of these numbers is like<01:10:11.130> kind<01:10:11.310> of<01:10:11.340> like<01:10:11.430> the<01:10:11.490> general<01:10:11.910> index<01:10:12.270> this 01:10:12.470 --> 01:10:12.480 align:start position:0% like kind of like the general index this 01:10:12.480 --> 01:10:14.420 align:start position:0% like kind of like the general index this is<01:10:12.600> like<01:10:12.720> defining<01:10:13.320> which<01:10:14.070> node<01:10:14.280> we're 01:10:14.420 --> 01:10:14.430 align:start position:0% is like defining which node we're 01:10:14.430 --> 01:10:15.740 align:start position:0% is like defining which node we're talking<01:10:14.790> about<01:10:14.880> it<01:10:15.120> you<01:10:15.180> can<01:10:15.300> start<01:10:15.480> with<01:10:15.660> the 01:10:15.740 --> 01:10:15.750 align:start position:0% talking about it you can start with the 01:10:15.750 --> 01:10:17.480 align:start position:0% talking about it you can start with the top<01:10:15.960> node<01:10:16.230> and<01:10:16.380> that's<01:10:16.440> one<01:10:16.770> and<01:10:17.040> then<01:10:17.340> you<01:10:17.460> can 01:10:17.480 --> 01:10:17.490 align:start position:0% top node and that's one and then you can 01:10:17.490 --> 01:10:18.030 align:start position:0% top node and that's one and then you can say<01:10:17.730> two 01:10:18.030 --> 01:10:18.040 align:start position:0% say two 01:10:18.040 --> 01:10:19.260 align:start position:0% say two three<01:10:18.340> just<01:10:18.550> like<01:10:18.670> kind<01:10:18.850> of<01:10:18.880> in<01:10:19.000> order<01:10:19.120> to 01:10:19.260 --> 01:10:19.270 align:start position:0% three just like kind of in order to 01:10:19.270 --> 01:10:21.960 align:start position:0% three just like kind of in order to reverse<01:10:19.600> all<01:10:19.840> the<01:10:19.930> way<01:10:20.020> down<01:10:20.170> the<01:10:20.290> tree<01:10:20.530> so<01:10:21.130> say 01:10:21.960 --> 01:10:21.970 align:start position:0% reverse all the way down the tree so say 01:10:21.970 --> 01:10:23.520 align:start position:0% reverse all the way down the tree so say that<01:10:22.090> we've<01:10:22.210> got<01:10:22.360> this<01:10:22.510> proof<01:10:22.840> right<01:10:23.080> here<01:10:23.140> we 01:10:23.520 --> 01:10:23.530 align:start position:0% that we've got this proof right here we 01:10:23.530 --> 01:10:25.620 align:start position:0% that we've got this proof right here we want<01:10:23.740> to<01:10:23.830> say<01:10:24.370> we're<01:10:24.490> trying<01:10:24.580> to<01:10:24.730> prove<01:10:24.850> 12<01:10:25.150> and 01:10:25.620 --> 01:10:25.630 align:start position:0% want to say we're trying to prove 12 and 01:10:25.630 --> 01:10:28.110 align:start position:0% want to say we're trying to prove 12 and the<01:10:26.290> nodes<01:10:26.530> we<01:10:26.740> want<01:10:26.980> we<01:10:27.220> need<01:10:27.430> to<01:10:27.670> provide 01:10:28.110 --> 01:10:28.120 align:start position:0% the nodes we want we need to provide 01:10:28.120 --> 01:10:29.850 align:start position:0% the nodes we want we need to provide this<01:10:28.630> like<01:10:28.840> in<01:10:28.990> the<01:10:29.080> stainless<01:10:29.320> multi<01:10:29.680> proof 01:10:29.850 --> 01:10:29.860 align:start position:0% this like in the stainless multi proof 01:10:29.860 --> 01:10:34.530 align:start position:0% this like in the stainless multi proof to<01:10:30.010> prove<01:10:30.220> 12<01:10:30.550> is<01:10:30.700> to<01:10:31.240> 12<01:10:31.630> 13<01:10:32.140> 7<01:10:33.120> so<01:10:34.120> what<01:10:34.270> we<01:10:34.360> do 01:10:34.530 --> 01:10:34.540 align:start position:0% to prove 12 is to 12 13 7 so what we do 01:10:34.540 --> 01:10:36.660 align:start position:0% to prove 12 is to 12 13 7 so what we do is<01:10:34.660> we<01:10:34.750> kind<01:10:34.870> of<01:10:34.990> like<01:10:35.110> bring<01:10:35.740> those<01:10:35.980> down<01:10:36.280> and 01:10:36.660 --> 01:10:36.670 align:start position:0% is we kind of like bring those down and 01:10:36.670 --> 01:10:38.340 align:start position:0% is we kind of like bring those down and these<01:10:37.360> this<01:10:37.570> is<01:10:37.630> kind<01:10:37.780> of<01:10:37.810> like<01:10:37.930> the<01:10:37.990> order 01:10:38.340 --> 01:10:38.350 align:start position:0% these this is kind of like the order 01:10:38.350 --> 01:10:41.160 align:start position:0% these this is kind of like the order that<01:10:38.620> these<01:10:38.830> hatches<01:10:39.430> will<01:10:39.610> be<01:10:39.730> stored<01:10:40.000> in<01:10:40.480> our 01:10:41.160 --> 01:10:41.170 align:start position:0% that these hatches will be stored in our 01:10:41.170 --> 01:10:42.900 align:start position:0% that these hatches will be stored in our like<01:10:41.380> contiguous<01:10:41.860> array<01:10:42.010> of<01:10:42.280> hashes<01:10:42.700> or 01:10:42.900 --> 01:10:42.910 align:start position:0% like contiguous array of hashes or 01:10:42.910 --> 01:10:45.570 align:start position:0% like contiguous array of hashes or everything<01:10:43.860> so<01:10:44.860> now<01:10:44.980> let's<01:10:45.190> generate<01:10:45.430> those 01:10:45.570 --> 01:10:45.580 align:start position:0% everything so now let's generate those 01:10:45.580 --> 01:10:47.550 align:start position:0% everything so now let's generate those those<01:10:45.940> offsets<01:10:46.270> so<01:10:46.780> the<01:10:46.870> first<01:10:47.080> thing<01:10:47.320> to<01:10:47.350> do 01:10:47.550 --> 01:10:47.560 align:start position:0% those offsets so the first thing to do 01:10:47.560 --> 01:10:49.050 align:start position:0% those offsets so the first thing to do is<01:10:47.710> we<01:10:47.830> started<01:10:48.130> like<01:10:48.220> at<01:10:48.310> the<01:10:48.400> very<01:10:48.580> top<01:10:48.790> and 01:10:49.050 --> 01:10:49.060 align:start position:0% is we started like at the very top and 01:10:49.060 --> 01:10:50.400 align:start position:0% is we started like at the very top and it's<01:10:49.150> kinda<01:10:49.330> like<01:10:49.390> this<01:10:49.540> recursive<01:10:50.050> thing<01:10:50.230> we 01:10:50.400 --> 01:10:50.410 align:start position:0% it's kinda like this recursive thing we 01:10:50.410 --> 01:10:53.160 align:start position:0% it's kinda like this recursive thing we say<01:10:50.620> how<01:10:51.130> many<01:10:51.480> nodes<01:10:52.480> is<01:10:52.750> in<01:10:52.840> the<01:10:52.930> left 01:10:53.160 --> 01:10:53.170 align:start position:0% say how many nodes is in the left 01:10:53.170 --> 01:10:55.200 align:start position:0% say how many nodes is in the left subtree<01:10:53.410> of<01:10:53.740> this<01:10:54.280> leg<01:10:54.460> entire<01:10:54.760> so<01:10:54.940> this 01:10:55.200 --> 01:10:55.210 align:start position:0% subtree of this leg entire so this 01:10:55.210 --> 01:10:56.430 align:start position:0% subtree of this leg entire so this entire<01:10:55.480> tree<01:10:55.750> that<01:10:55.870> we're<01:10:55.960> looking<01:10:56.020> at<01:10:56.230> and 01:10:56.430 --> 01:10:56.440 align:start position:0% entire tree that we're looking at and 01:10:56.440 --> 01:10:58.710 align:start position:0% entire tree that we're looking at and well<01:10:56.860> like<01:10:57.040> in<01:10:57.370> that<01:10:57.490> case<01:10:57.550> it's<01:10:57.850> 4<01:10:58.120> because<01:10:58.540> we 01:10:58.710 --> 01:10:58.720 align:start position:0% well like in that case it's 4 because we 01:10:58.720 --> 01:11:00.090 align:start position:0% well like in that case it's 4 because we can<01:10:58.840> just<01:10:58.990> like<01:10:59.110> count<01:10:59.500> the<01:10:59.650> number<01:10:59.860> of<01:10:59.920> nodes 01:11:00.090 --> 01:11:00.100 align:start position:0% can just like count the number of nodes 01:11:00.100 --> 01:11:02.520 align:start position:0% can just like count the number of nodes that<01:11:00.280> we're<01:11:00.430> providing<01:11:01.000> as<01:11:01.450> proof<01:11:01.720> on<01:11:01.990> 2<01:11:02.140> 3<01:11:02.320> 4 01:11:02.520 --> 01:11:02.530 align:start position:0% that we're providing as proof on 2 3 4 01:11:02.530 --> 01:11:05.180 align:start position:0% that we're providing as proof on 2 3 4 and<01:11:02.860> so<01:11:03.310> that's<01:11:03.520> like<01:11:03.610> the<01:11:03.730> first<01:11:03.880> number<01:11:04.360> of 01:11:05.180 --> 01:11:05.190 align:start position:0% and so that's like the first number of 01:11:05.190 --> 01:11:08.610 align:start position:0% and so that's like the first number of offsets<01:11:06.190> and<01:11:06.430> so<01:11:07.330> we<01:11:07.480> started<01:11:07.750> continuing<01:11:08.530> to 01:11:08.610 --> 01:11:08.620 align:start position:0% offsets and so we started continuing to 01:11:08.620 --> 01:11:11.340 align:start position:0% offsets and so we started continuing to traverse<01:11:08.980> down<01:11:09.210> to<01:11:10.210> the<01:11:10.300> left<01:11:10.510> and<01:11:10.840> now<01:11:11.200> that 01:11:11.340 --> 01:11:11.350 align:start position:0% traverse down to the left and now that 01:11:11.350 --> 01:11:13.350 align:start position:0% traverse down to the left and now that were<01:11:11.410> wanting<01:11:11.770> to<01:11:11.800> say<01:11:11.980> ok<01:11:12.190> how<01:11:12.640> many<01:11:12.700> nodes<01:11:13.120> is 01:11:13.350 --> 01:11:13.360 align:start position:0% were wanting to say ok how many nodes is 01:11:13.360 --> 01:11:15.780 align:start position:0% were wanting to say ok how many nodes is in<01:11:13.480> the<01:11:13.570> left<01:11:13.720> subtree<01:11:13.960> from<01:11:14.410> 1<01:11:14.650> it's<01:11:15.520> just<01:11:15.580> a 01:11:15.780 --> 01:11:15.790 align:start position:0% in the left subtree from 1 it's just a 01:11:15.790 --> 01:11:16.980 align:start position:0% in the left subtree from 1 it's just a to<01:11:16.000> note<01:11:16.240> there<01:11:16.480> because<01:11:16.780> we're<01:11:16.900> not 01:11:16.980 --> 01:11:16.990 align:start position:0% to note there because we're not 01:11:16.990 --> 01:11:18.510 align:start position:0% to note there because we're not providing<01:11:17.560> anything<01:11:17.740> below<01:11:18.190> we're<01:11:18.460> only 01:11:18.510 --> 01:11:18.520 align:start position:0% providing anything below we're only 01:11:18.520 --> 01:11:20.400 align:start position:0% providing anything below we're only everybody<01:11:19.090> that<01:11:19.360> once<01:11:19.570> that's<01:11:19.810> the<01:11:20.260> only 01:11:20.400 --> 01:11:20.410 align:start position:0% everybody that once that's the only 01:11:20.410 --> 01:11:23.190 align:start position:0% everybody that once that's the only thing<01:11:20.560> we<01:11:20.620> need<01:11:20.710> to<01:11:20.890> prove<01:11:21.550> 12<01:11:21.940> and<01:11:22.240> so<01:11:22.870> in<01:11:23.110> that 01:11:23.190 --> 01:11:23.200 align:start position:0% thing we need to prove 12 and so in that 01:11:23.200 --> 01:11:25.830 align:start position:0% thing we need to prove 12 and so in that case<01:11:23.380> it's<01:11:23.560> a<01:11:23.620> 1<01:11:23.830> so<01:11:24.550> we<01:11:24.640> come<01:11:24.790> down<01:11:25.030> to<01:11:25.240> 2<01:11:25.540> now 01:11:25.830 --> 01:11:25.840 align:start position:0% case it's a 1 so we come down to 2 now 01:11:25.840 --> 01:11:27.960 align:start position:0% case it's a 1 so we come down to 2 now we're<01:11:26.050> still<01:11:26.230> traversing<01:11:26.830> left<01:11:27.070> first<01:11:27.610> and 01:11:27.960 --> 01:11:27.970 align:start position:0% we're still traversing left first and 01:11:27.970 --> 01:11:29.640 align:start position:0% we're still traversing left first and there's<01:11:28.360> no<01:11:28.570> nodes<01:11:28.900> and<01:11:29.080> that<01:11:29.140> left<01:11:29.380> subtree 01:11:29.640 --> 01:11:29.650 align:start position:0% there's no nodes and that left subtree 01:11:29.650 --> 01:11:33.300 align:start position:0% there's no nodes and that left subtree of<01:11:29.980> 2<01:11:30.190> so<01:11:30.790> we<01:11:30.910> can<01:11:30.940> skip<01:11:31.420> over<01:11:31.600> to<01:11:31.810> 3<01:11:32.190> and<01:11:33.190> we 01:11:33.300 --> 01:11:33.310 align:start position:0% of 2 so we can skip over to 3 and we 01:11:33.310 --> 01:11:35.100 align:start position:0% of 2 so we can skip over to 3 and we asked<01:11:33.550> how<01:11:33.670> many<01:11:33.730> nodes<01:11:34.030> is<01:11:34.210> in<01:11:34.330> the<01:11:34.390> 3<01:11:34.600> subtree 01:11:35.100 --> 01:11:35.110 align:start position:0% asked how many nodes is in the 3 subtree 01:11:35.110 --> 01:11:37.680 align:start position:0% asked how many nodes is in the 3 subtree it's<01:11:35.410> just<01:11:35.710> folded<01:11:36.070> 13<01:11:36.490> so<01:11:36.760> we<01:11:36.850> can<01:11:36.970> put<01:11:37.150> two<01:11:37.330> in 01:11:37.680 --> 01:11:37.690 align:start position:0% it's just folded 13 so we can put two in 01:11:37.690 --> 01:11:40.590 align:start position:0% it's just folded 13 so we can put two in our<01:11:37.780> offsets<01:11:38.370> we<01:11:39.370> come<01:11:39.550> down<01:11:39.670> to<01:11:39.730> 6<01:11:40.030> same 01:11:40.590 --> 01:11:40.600 align:start position:0% our offsets we come down to 6 same 01:11:40.600 --> 01:11:42.000 align:start position:0% our offsets we come down to 6 same question<01:11:41.140> how<01:11:41.230> many<01:11:41.290> nodes<01:11:41.500> to<01:11:41.710> the<01:11:41.770> left 01:11:42.000 --> 01:11:42.010 align:start position:0% question how many nodes to the left 01:11:42.010 --> 01:11:44.940 align:start position:0% question how many nodes to the left subtree<01:11:42.220> one<01:11:42.690> go<01:11:43.690> down<01:11:43.810> to<01:11:43.930> 12<01:11:44.200> well<01:11:44.740> there's 01:11:44.940 --> 01:11:44.950 align:start position:0% subtree one go down to 12 well there's 01:11:44.950 --> 01:11:47.250 align:start position:0% subtree one go down to 12 well there's no<01:11:45.340> no<01:11:45.910> knows<01:11:46.090> where<01:11:46.300> to<01:11:46.360> leave<01:11:46.510> and<01:11:47.080> how<01:11:47.170> we 01:11:47.250 --> 01:11:47.260 align:start position:0% no no knows where to leave and how we 01:11:47.260 --> 01:11:49.500 align:start position:0% no no knows where to leave and how we come<01:11:47.410> to<01:11:47.500> 7<01:11:47.920> and<01:11:48.070> we<01:11:48.460> do<01:11:48.790> include<01:11:49.090> 7<01:11:49.360> in<01:11:49.450> the 01:11:49.500 --> 01:11:49.510 align:start position:0% come to 7 and we do include 7 in the 01:11:49.510 --> 01:11:52.170 align:start position:0% come to 7 and we do include 7 in the proof<01:11:49.780> but<01:11:50.050> it<01:11:50.200> has<01:11:50.350> no<01:11:50.500> children<01:11:50.800> so<01:11:51.220> I<01:11:51.550> kind 01:11:52.170 --> 01:11:52.180 align:start position:0% proof but it has no children so I kind 01:11:52.180 --> 01:11:53.580 align:start position:0% proof but it has no children so I kind of<01:11:52.240> meandered<01:11:52.660> just<01:11:52.990> for<01:11:53.080> the<01:11:53.140> office<01:11:53.470> that 01:11:53.580 --> 01:11:53.590 align:start position:0% of meandered just for the office that 01:11:53.590 --> 01:11:56.580 align:start position:0% of meandered just for the office that we've<01:11:53.710> already<01:11:53.830> come<01:11:54.070> up<01:11:54.100> with<01:11:54.270> so<01:11:55.410> this<01:11:56.410> is 01:11:56.580 --> 01:11:56.590 align:start position:0% we've already come up with so this is 01:11:56.590 --> 01:11:58.239 align:start position:0% we've already come up with so this is this<01:11:56.890> is<01:11:56.980> what<01:11:57.130> I<01:11:57.370> kind<01:11:57.610> of<01:11:57.760> improve 01:11:58.239 --> 01:11:58.249 align:start position:0% this is what I kind of improve 01:11:58.249 --> 01:11:59.560 align:start position:0% this is what I kind of improve is<01:11:58.369> we've<01:11:58.670> got<01:11:58.820> these<01:11:58.940> offsets<01:11:59.329> that<01:11:59.420> we 01:11:59.560 --> 01:11:59.570 align:start position:0% is we've got these offsets that we 01:11:59.570 --> 01:12:03.279 align:start position:0% is we've got these offsets that we generated<01:11:59.989> like<01:12:00.289> 4<01:12:00.679> to<01:12:00.920> 4<01:12:01.400> 1<01:12:01.429> to<01:12:01.849> 1<01:12:02.119> and<01:12:02.360> the 01:12:03.279 --> 01:12:03.289 align:start position:0% generated like 4 to 4 1 to 1 and the 01:12:03.289 --> 01:12:05.489 align:start position:0% generated like 4 to 4 1 to 1 and the branch<01:12:03.590> they'll<01:12:03.920> need<01:12:04.099> to<01:12:04.130> provide<01:12:04.519> to<01:12:04.909> prove 01:12:05.489 --> 01:12:05.499 align:start position:0% branch they'll need to provide to prove 01:12:05.499 --> 01:12:09.069 align:start position:0% branch they'll need to provide to prove this<01:12:06.499> general<01:12:06.860> that's<01:12:07.010> note<01:12:07.309> at<01:12:07.489> index<01:12:08.150> 12<01:12:08.539> the 01:12:09.069 --> 01:12:09.079 align:start position:0% this general that's note at index 12 the 01:12:09.079 --> 01:12:11.290 align:start position:0% this general that's note at index 12 the branch<01:12:09.349> is<01:12:09.559> not<01:12:09.710> actually<01:12:10.219> the<01:12:10.489> branch 01:12:11.290 --> 01:12:11.300 align:start position:0% branch is not actually the branch 01:12:11.300 --> 01:12:13.509 align:start position:0% branch is not actually the branch indices<01:12:11.749> it's<01:12:11.960> actually<01:12:12.260> is<01:12:12.320> 1/2<01:12:12.530> 32<01:12:13.309> bytes 01:12:13.509 --> 01:12:13.519 align:start position:0% indices it's actually is 1/2 32 bytes 01:12:13.519 --> 01:12:15.879 align:start position:0% indices it's actually is 1/2 32 bytes it's<01:12:14.449> just<01:12:14.630> easier<01:12:14.900> to<01:12:14.989> like<01:12:15.409> reason<01:12:15.679> about<01:12:15.829> it 01:12:15.879 --> 01:12:15.889 align:start position:0% it's just easier to like reason about it 01:12:15.889 --> 01:12:27.489 align:start position:0% it's just easier to like reason about it might<01:12:16.249> just<01:12:16.519> show<01:12:16.849> the<01:12:16.969> branch<01:12:17.150> indices<01:12:26.499> so 01:12:27.489 --> 01:12:27.499 align:start position:0% might just show the branch indices so 01:12:27.499 --> 01:12:30.669 align:start position:0% might just show the branch indices so right<01:12:28.249> now<01:12:28.400> this<01:12:28.519> is<01:12:28.639> like<01:12:28.699> the<01:12:28.880> size<01:12:29.119> of<01:12:29.679> so 01:12:30.669 --> 01:12:30.679 align:start position:0% right now this is like the size of so 01:12:30.679 --> 01:12:32.680 align:start position:0% right now this is like the size of so I've<01:12:30.800> told<01:12:31.039> you<01:12:31.219> there's<01:12:31.489> a<01:12:31.579> tool<01:12:32.059> to<01:12:32.300> generate 01:12:32.680 --> 01:12:32.690 align:start position:0% I've told you there's a tool to generate 01:12:32.690 --> 01:12:34.629 align:start position:0% I've told you there's a tool to generate these<01:12:32.900> funky<01:12:33.349> proofs<01:12:33.679> and<01:12:33.800> this<01:12:34.099> the<01:12:34.219> size<01:12:34.400> I'm 01:12:34.629 --> 01:12:34.639 align:start position:0% these funky proofs and this the size I'm 01:12:34.639 --> 01:12:37.390 align:start position:0% these funky proofs and this the size I'm getting<01:12:34.880> right<01:12:34.999> now<01:12:35.829> and<01:12:36.829> you<01:12:36.920> can<01:12:37.039> read<01:12:37.249> them 01:12:37.390 --> 01:12:37.400 align:start position:0% getting right now and you can read them 01:12:37.400 --> 01:12:38.799 align:start position:0% getting right now and you can read them down<01:12:37.639> that's<01:12:37.729> it<01:12:37.909> these<01:12:38.090> numbers<01:12:38.420> like<01:12:38.599> aren't 01:12:38.799 --> 01:12:38.809 align:start position:0% down that's it these numbers like aren't 01:12:38.809 --> 01:12:40.419 align:start position:0% down that's it these numbers like aren't super<01:12:39.499> accurate<01:12:39.650> until<01:12:40.099> we<01:12:40.190> do<01:12:40.340> these 01:12:40.419 --> 01:12:40.429 align:start position:0% super accurate until we do these 01:12:40.429 --> 01:12:42.009 align:start position:0% super accurate until we do these optimization<01:12:41.210> so<01:12:41.389> the<01:12:41.510> first<01:12:41.690> optimization 01:12:42.009 --> 01:12:42.019 align:start position:0% optimization so the first optimization 01:12:42.019 --> 01:12:43.930 align:start position:0% optimization so the first optimization is<01:12:42.469> the<01:12:42.829> offsets<01:12:43.159> are<01:12:43.280> going<01:12:43.400> to<01:12:43.519> resent<01:12:43.760> firm 01:12:43.930 --> 01:12:43.940 align:start position:0% is the offsets are going to resent firm 01:12:43.940 --> 01:12:46.479 align:start position:0% is the offsets are going to resent firm is<01:12:44.030> ended<01:12:44.239> by<01:12:44.300> you<01:12:44.510> 64<01:12:45.079> 's<01:12:45.110> and<01:12:45.380> I'm<01:12:46.340> never 01:12:46.479 --> 01:12:46.489 align:start position:0% is ended by you 64 's and I'm never 01:12:46.489 --> 01:12:49.149 align:start position:0% is ended by you 64 's and I'm never gonna<01:12:46.670> provide<01:12:46.999> enough<01:12:47.510> hashes<01:12:48.320> to<01:12:48.349> be<01:12:48.679> all 01:12:49.149 --> 01:12:49.159 align:start position:0% gonna provide enough hashes to be all 01:12:49.159 --> 01:12:51.790 align:start position:0% gonna provide enough hashes to be all those<01:12:50.119> bits<01:12:50.300> of<01:12:50.570> significance<01:12:51.289> so<01:12:51.590> I<01:12:51.650> could 01:12:51.790 --> 01:12:51.800 align:start position:0% those bits of significance so I could 01:12:51.800 --> 01:12:53.500 align:start position:0% those bits of significance so I could probably<01:12:51.889> get<01:12:52.130> away<01:12:52.219> with<01:12:52.519> like<01:12:52.699> you<01:12:52.999> 16<01:12:53.389> or 01:12:53.500 --> 01:12:53.510 align:start position:0% probably get away with like you 16 or 01:12:53.510 --> 01:12:55.359 align:start position:0% probably get away with like you 16 or something<01:12:53.630> but<01:12:54.530> the<01:12:54.619> more<01:12:54.829> important<01:12:55.190> one<01:12:55.280> is 01:12:55.359 --> 01:12:55.369 align:start position:0% something but the more important one is 01:12:55.369 --> 01:12:57.339 align:start position:0% something but the more important one is that<01:12:55.489> right<01:12:55.610> now<01:12:55.760> including<01:12:56.420> 0<01:12:56.630> hashes<01:12:57.110> and<01:12:57.139> if 01:12:57.339 --> 01:12:57.349 align:start position:0% that right now including 0 hashes and if 01:12:57.349 --> 01:12:58.689 align:start position:0% that right now including 0 hashes and if you're<01:12:57.499> familiar<01:12:57.679> with<01:12:57.979> the<01:12:58.159> structure<01:12:58.550> of<01:12:58.639> a 01:12:58.689 --> 01:12:58.699 align:start position:0% you're familiar with the structure of a 01:12:58.699 --> 01:13:00.969 align:start position:0% you're familiar with the structure of a sparse<01:12:58.909> Merkle<01:12:59.239> tree<01:12:59.389> there's<01:12:59.989> a<01:13:00.349> lot<01:13:00.590> of<01:13:00.710> to<01:13:00.769> 0 01:13:00.969 --> 01:13:00.979 align:start position:0% sparse Merkle tree there's a lot of to 0 01:13:00.979 --> 01:13:03.310 align:start position:0% sparse Merkle tree there's a lot of to 0 hashes<01:13:01.489> especially<01:13:02.449> the<01:13:02.630> lower<01:13:02.809> levels<01:13:03.199> of 01:13:03.310 --> 01:13:03.320 align:start position:0% hashes especially the lower levels of 01:13:03.320 --> 01:13:05.410 align:start position:0% hashes especially the lower levels of your<01:13:03.499> tree<01:13:03.679> and<01:13:03.860> so<01:13:04.119> until<01:13:05.119> these 01:13:05.410 --> 01:13:05.420 align:start position:0% your tree and so until these 01:13:05.420 --> 01:13:06.879 align:start position:0% your tree and so until these optimizations<01:13:05.960> start<01:13:06.139> down<01:13:06.320> these<01:13:06.499> numbers 01:13:06.879 --> 01:13:06.889 align:start position:0% optimizations start down these numbers 01:13:06.889 --> 01:13:08.469 align:start position:0% optimizations start down these numbers are<01:13:07.190> kind<01:13:07.489> of<01:13:07.610> just<01:13:07.820> like 01:13:08.469 --> 01:13:08.479 align:start position:0% are kind of just like 01:13:08.479 --> 01:13:12.040 align:start position:0% are kind of just like waiting<01:13:08.929> around<01:13:09.019> in<01:13:09.289> the<01:13:09.320> air<01:13:10.179> so<01:13:11.179> I<01:13:11.209> told<01:13:11.840> you 01:13:12.040 --> 01:13:12.050 align:start position:0% waiting around in the air so I told you 01:13:12.050 --> 01:13:14.529 align:start position:0% waiting around in the air so I told you about<01:13:12.369> how<01:13:13.369> to<01:13:13.429> create<01:13:13.849> the<01:13:13.940> offsets<01:13:14.329> because 01:13:14.529 --> 01:13:14.539 align:start position:0% about how to create the offsets because 01:13:14.539 --> 01:13:16.209 align:start position:0% about how to create the offsets because these<01:13:14.869> algorithms<01:13:15.139> that<01:13:15.409> you<01:13:15.499> need<01:13:15.650> to<01:13:15.739> do<01:13:15.860> to 01:13:16.209 --> 01:13:16.219 align:start position:0% these algorithms that you need to do to 01:13:16.219 --> 01:13:19.359 align:start position:0% these algorithms that you need to do to look<01:13:16.760> up<01:13:16.909> values<01:13:17.329> and<01:13:17.889> do<01:13:18.889> the<01:13:19.039> virtualization 01:13:19.359 --> 01:13:19.369 align:start position:0% look up values and do the virtualization 01:13:19.369 --> 01:13:22.000 align:start position:0% look up values and do the virtualization so<01:13:20.059> if<01:13:20.389> you're<01:13:20.599> interested<01:13:20.809> in<01:13:21.079> like<01:13:21.229> like 01:13:22.000 --> 01:13:22.010 align:start position:0% so if you're interested in like like 01:13:22.010 --> 01:13:23.589 align:start position:0% so if you're interested in like like understanding<01:13:22.429> those<01:13:22.550> algorithms<01:13:23.059> you<01:13:23.570> can 01:13:23.589 --> 01:13:23.599 align:start position:0% understanding those algorithms you can 01:13:23.599 --> 01:13:26.949 align:start position:0% understanding those algorithms you can read<01:13:23.869> proto<01:13:24.170> lambdas<01:13:25.420> kind<01:13:26.420> of<01:13:26.479> paper<01:13:26.659> that<01:13:26.809> he 01:13:26.949 --> 01:13:26.959 align:start position:0% read proto lambdas kind of paper that he 01:13:26.959 --> 01:13:28.660 align:start position:0% read proto lambdas kind of paper that he published<01:13:26.989> on<01:13:27.409> get<01:13:27.559> up<01:13:27.709> and<01:13:27.949> I've<01:13:28.340> got<01:13:28.369> two 01:13:28.660 --> 01:13:28.670 align:start position:0% published on get up and I've got two 01:13:28.670 --> 01:13:30.640 align:start position:0% published on get up and I've got two implementations<01:13:28.940> I<01:13:29.599> did<01:13:29.869> one<01:13:30.079> in<01:13:30.110> Rus<01:13:30.409> and 01:13:30.640 --> 01:13:30.650 align:start position:0% implementations I did one in Rus and 01:13:30.650 --> 01:13:32.949 align:start position:0% implementations I did one in Rus and then<01:13:30.769> I<01:13:30.829> did<01:13:31.010> want<01:13:31.219> to<01:13:31.309> Python<01:13:31.729> this<01:13:32.599> Python 01:13:32.949 --> 01:13:32.959 align:start position:0% then I did want to Python this Python 01:13:32.959 --> 01:13:34.390 align:start position:0% then I did want to Python this Python one<01:13:33.079> is<01:13:33.139> way<01:13:33.229> more<01:13:33.380> readable<01:13:33.650> to<01:13:33.829> the<01:13:33.949> rest<01:13:34.130> one 01:13:34.390 --> 01:13:34.400 align:start position:0% one is way more readable to the rest one 01:13:34.400 --> 01:13:35.049 align:start position:0% one is way more readable to the rest one I<01:13:34.639> suppose 01:13:35.049 --> 01:13:35.059 align:start position:0% I suppose 01:13:35.059 --> 01:13:39.100 align:start position:0% I suppose Python<01:13:35.449> things<01:13:35.659> they<01:13:36.289> are<01:13:37.809> if<01:13:38.809> you<01:13:38.929> want<01:13:39.050> to 01:13:39.100 --> 01:13:39.110 align:start position:0% Python things they are if you want to 01:13:39.110 --> 01:13:40.870 align:start position:0% Python things they are if you want to learn<01:13:39.199> more<01:13:39.349> about<01:13:39.409> sheath<01:13:39.860> if<01:13:40.550> you<01:13:40.639> want<01:13:40.820> to 01:13:40.870 --> 01:13:40.880 align:start position:0% learn more about sheath if you want to 01:13:40.880 --> 01:13:42.189 align:start position:0% learn more about sheath if you want to work<01:13:41.059> in<01:13:41.239> and<01:13:41.360> trying<01:13:41.539> to<01:13:41.599> act<01:13:41.719> at<01:13:41.900> the<01:13:41.989> next 01:13:42.189 --> 01:13:42.199 align:start position:0% work in and trying to act at the next 01:13:42.199 --> 01:13:44.290 align:start position:0% work in and trying to act at the next target<01:13:42.320> or<01:13:42.590> whatever<01:13:42.949> the<01:13:43.459> repository<01:13:44.150> is 01:13:44.290 --> 01:13:44.300 align:start position:0% target or whatever the repository is 01:13:44.300 --> 01:13:46.540 align:start position:0% target or whatever the repository is github.com<01:13:44.690> slash<01:13:45.499> like<01:13:45.920> client<01:13:46.309> slash 01:13:46.540 --> 01:13:46.550 align:start position:0% github.com slash like client slash 01:13:46.550 --> 01:13:49.509 align:start position:0% github.com slash like client slash cheese<01:13:46.880> and<01:13:47.260> check<01:13:48.260> out<01:13:48.380> the<01:13:48.530> hacking<01:13:48.709> DMD 01:13:49.509 --> 01:13:49.519 align:start position:0% cheese and check out the hacking DMD 01:13:49.519 --> 01:13:51.040 align:start position:0% cheese and check out the hacking DMD file<01:13:49.849> it's<01:13:50.119> a<01:13:50.179> pretty<01:13:50.420> good<01:13:50.539> guide<01:13:50.719> I'm<01:13:50.900> like 01:13:51.040 --> 01:13:51.050 align:start position:0% file it's a pretty good guide I'm like 01:13:51.050 --> 01:13:52.899 align:start position:0% file it's a pretty good guide I'm like recording<01:13:51.530> is<01:13:51.650> started<01:13:51.679> if<01:13:52.249> you<01:13:52.429> want<01:13:52.610> to<01:13:52.699> like 01:13:52.899 --> 01:13:52.909 align:start position:0% recording is started if you want to like 01:13:52.909 --> 01:13:54.939 align:start position:0% recording is started if you want to like play<01:13:53.239> around<01:13:53.449> with<01:13:53.599> cheese<01:13:53.929> feel<01:13:54.769> free<01:13:54.920> to 01:13:54.939 --> 01:13:54.949 align:start position:0% play around with cheese feel free to 01:13:54.949 --> 01:13:57.250 align:start position:0% play around with cheese feel free to ping<01:13:55.219> me<01:13:55.249> on<01:13:55.369> twitter<01:13:55.729> my<01:13:56.239> handle<01:13:56.510> is<01:13:56.929> about<01:13:57.110> it 01:13:57.250 --> 01:13:57.260 align:start position:0% ping me on twitter my handle is about it 01:13:57.260 --> 01:14:02.620 align:start position:0% ping me on twitter my handle is about it matters<01:13:57.949> for<01:13:58.030> Garnett<01:13:59.030> and<01:14:00.489> or<01:14:01.489> you<01:14:01.610> saw<01:14:01.820> me<01:14:01.999> at 01:14:02.620 --> 01:14:02.630 align:start position:0% matters for Garnett and or you saw me at 01:14:02.630 --> 01:14:03.879 align:start position:0% matters for Garnett and or you saw me at the<01:14:02.749> conference<01:14:03.139> I<01:14:03.229> hope<01:14:03.440> you<01:14:03.530> like<01:14:03.650> talk<01:14:03.860> to 01:14:03.879 --> 01:14:03.889 align:start position:0% the conference I hope you like talk to 01:14:03.889 --> 01:14:05.669 align:start position:0% the conference I hope you like talk to you<01:14:04.039> more<01:14:04.550> about<01:14:04.610> shoes 01:14:05.669 --> 01:14:05.679 align:start position:0% you more about shoes 01:14:05.679 --> 01:14:08.680 align:start position:0% you more about shoes so<01:14:06.679> thank<01:14:07.190> you<01:14:07.400> does<01:14:08.119> anybody<01:14:08.360> have<01:14:08.510> any 01:14:08.680 --> 01:14:08.690 align:start position:0% so thank you does anybody have any 01:14:08.690 --> 01:14:15.719 align:start position:0% so thank you does anybody have any questions<01:14:09.079> or<01:14:09.729> questions<01:14:10.780> ok<01:14:11.780> any<01:14:12.409> questions 01:14:15.719 --> 01:14:15.729 align:start position:0% 01:14:15.729 --> 01:14:22.709 align:start position:0% yes 01:14:22.709 --> 01:14:22.719 align:start position:0% 01:14:22.719 --> 01:14:24.810 align:start position:0% to<01:14:23.530> do<01:14:23.679> from<01:14:24.070> here<01:14:24.219> to<01:14:24.369> do<01:14:24.460> more<01:14:24.639> than 01:14:24.810 --> 01:14:24.820 align:start position:0% to do from here to do more than 01:14:24.820 --> 01:14:29.850 align:start position:0% to do from here to do more than transfers<01:14:25.980> people<01:14:27.659> I<01:14:28.659> feel<01:14:29.440> like<01:14:29.500> a<01:14:29.650> lot<01:14:29.800> of 01:14:29.850 --> 01:14:29.860 align:start position:0% transfers people I feel like a lot of 01:14:29.860 --> 01:14:32.640 align:start position:0% transfers people I feel like a lot of the<01:14:30.099> the<01:14:30.610> framework<01:14:31.090> is<01:14:31.300> there<01:14:31.510> and<01:14:31.869> I<01:14:32.110> just 01:14:32.640 --> 01:14:32.650 align:start position:0% the the framework is there and I just 01:14:32.650 --> 01:14:34.500 align:start position:0% the the framework is there and I just like<01:14:32.860> I<01:14:33.039> personally<01:14:33.520> don't<01:14:33.940> have<01:14:33.969> time<01:14:34.239> to 01:14:34.500 --> 01:14:34.510 align:start position:0% like I personally don't have time to 01:14:34.510 --> 01:14:36.720 align:start position:0% like I personally don't have time to build<01:14:34.719> like<01:14:34.989> more<01:14:35.530> exciting<01:14:36.039> ones<01:14:36.190> but<01:14:36.460> I've 01:14:36.720 --> 01:14:36.730 align:start position:0% build like more exciting ones but I've 01:14:36.730 --> 01:14:38.430 align:start position:0% build like more exciting ones but I've been<01:14:36.909> the<01:14:37.059> bond<01:14:37.420> it's<01:14:37.630> like<01:14:37.750> really<01:14:37.960> you<01:14:38.349> just 01:14:38.430 --> 01:14:38.440 align:start position:0% been the bond it's like really you just 01:14:38.440 --> 01:14:39.750 align:start position:0% been the bond it's like really you just have<01:14:38.559> to<01:14:38.710> like<01:14:38.829> go<01:14:38.949> back<01:14:39.099> to<01:14:39.280> like<01:14:39.400> the<01:14:39.520> very 01:14:39.750 --> 01:14:39.760 align:start position:0% have to like go back to like the very 01:14:39.760 --> 01:14:41.729 align:start position:0% have to like go back to like the very beginning<01:14:40.090> this<01:14:40.480> like<01:14:40.690> slide<01:14:40.989> on<01:14:41.440> if<01:14:41.530> I<01:14:41.619> get 01:14:41.729 --> 01:14:41.739 align:start position:0% beginning this like slide on if I get 01:14:41.739 --> 01:14:45.990 align:start position:0% beginning this like slide on if I get there<01:14:41.889> fast<01:14:42.070> up<01:14:43.889> but<01:14:44.889> it's<01:14:45.460> really<01:14:45.639> just<01:14:45.760> like 01:14:45.990 --> 01:14:46.000 align:start position:0% there fast up but it's really just like 01:14:46.000 --> 01:14:48.600 align:start position:0% there fast up but it's really just like replacing<01:14:46.570> these<01:14:46.780> kind<01:14:47.050> of<01:14:47.400> like<01:14:48.400> these 01:14:48.600 --> 01:14:48.610 align:start position:0% replacing these kind of like these 01:14:48.610 --> 01:14:50.220 align:start position:0% replacing these kind of like these concepts<01:14:49.119> transferred<01:14:49.539> to<01:14:49.630> positive<01:14:49.960> Charlie 01:14:50.220 --> 01:14:50.230 align:start position:0% concepts transferred to positive Charlie 01:14:50.230 --> 01:14:52.620 align:start position:0% concepts transferred to positive Charlie I'm<01:14:50.440> gonna<01:14:50.530> do<01:14:50.739> like<01:14:50.829> a<01:14:50.889> bounties<01:14:51.579> contract<01:14:52.119> II 01:14:52.620 --> 01:14:52.630 align:start position:0% I'm gonna do like a bounties contract II 01:14:52.630 --> 01:14:54.600 align:start position:0% I'm gonna do like a bounties contract II it<01:14:53.559> would<01:14:53.679> just<01:14:53.829> feel<01:14:53.889> like<01:14:54.039> instead<01:14:54.550> of 01:14:54.600 --> 01:14:54.610 align:start position:0% it would just feel like instead of 01:14:54.610 --> 01:14:56.339 align:start position:0% it would just feel like instead of trance<01:14:54.820> would<01:14:54.969> be<01:14:55.090> create<01:14:55.329> Dominique<01:14:55.750> and<01:14:55.989> an 01:14:56.339 --> 01:14:56.349 align:start position:0% trance would be create Dominique and an 01:14:56.349 --> 01:14:58.049 align:start position:0% trance would be create Dominique and an interpreter<01:14:56.770> interprets<01:14:57.010> some<01:14:57.550> way<01:14:57.699> and<01:14:57.940> then 01:14:58.049 --> 01:14:58.059 align:start position:0% interpreter interprets some way and then 01:14:58.059 --> 01:14:59.520 align:start position:0% interpreter interprets some way and then I<01:14:58.090> would<01:14:58.270> change<01:14:58.480> kind<01:14:58.780> of<01:14:58.840> these<01:14:59.230> are<01:14:59.349> like 01:14:59.520 --> 01:14:59.530 align:start position:0% I would change kind of these are like 01:14:59.530 --> 01:15:02.220 align:start position:0% I would change kind of these are like the<01:15:00.000> variables<01:15:01.000> in<01:15:01.179> yours<01:15:01.329> Olivia<01:15:01.690> contract 01:15:02.220 --> 01:15:02.230 align:start position:0% the variables in yours Olivia contract 01:15:02.230 --> 01:15:04.010 align:start position:0% the variables in yours Olivia contract that's<01:15:02.860> kind<01:15:03.070> of<01:15:03.130> like<01:15:03.219> the<01:15:03.309> same<01:15:03.489> like 01:15:04.010 --> 01:15:04.020 align:start position:0% that's kind of like the same like 01:15:04.020 --> 01:15:06.959 align:start position:0% that's kind of like the same like similarity<01:15:05.020> and<01:15:05.139> so<01:15:05.320> it's<01:15:06.010> possible<01:15:06.309> to<01:15:06.670> do<01:15:06.789> it 01:15:06.959 --> 01:15:06.969 align:start position:0% similarity and so it's possible to do it 01:15:06.969 --> 01:15:08.370 align:start position:0% similarity and so it's possible to do it you<01:15:07.150> can<01:15:07.270> fork<01:15:07.480> it<01:15:07.599> from<01:15:07.719> here<01:15:07.869> and<01:15:07.960> do<01:15:08.079> it<01:15:08.230> it's 01:15:08.370 --> 01:15:08.380 align:start position:0% you can fork it from here and do it it's 01:15:08.380 --> 01:15:10.049 align:start position:0% you can fork it from here and do it it's just<01:15:08.440> you<01:15:09.099> need<01:15:09.250> to<01:15:09.400> spend<01:15:09.610> some<01:15:09.760> time<01:15:09.969> to 01:15:10.049 --> 01:15:10.059 align:start position:0% just you need to spend some time to 01:15:10.059 --> 01:15:19.020 align:start position:0% just you need to spend some time to think<01:15:10.179> about<01:15:10.300> it<01:15:16.469> the<01:15:17.469> hashes<01:15:18.039> can't<01:15:18.400> be<01:15:18.610> some 01:15:19.020 --> 01:15:19.030 align:start position:0% think about it the hashes can't be some 01:15:19.030 --> 01:15:25.169 align:start position:0% think about it the hashes can't be some compromise<01:15:19.510> now<01:15:20.280> it's<01:15:21.280> a<01:15:21.900> so<01:15:23.520> is<01:15:24.520> any<01:15:24.699> expected 01:15:25.169 --> 01:15:25.179 align:start position:0% compromise now it's a so is any expected 01:15:25.179 --> 01:15:30.270 align:start position:0% compromise now it's a so is any expected savings<01:15:25.889> any<01:15:26.889> early<01:15:27.250> numbers<01:15:28.530> not<01:15:29.530> really<01:15:29.920> but 01:15:30.270 --> 01:15:30.280 align:start position:0% savings any early numbers not really but 01:15:30.280 --> 01:15:33.750 align:start position:0% savings any early numbers not really but I<01:15:30.880> have<01:15:31.260> come<01:15:32.260> up<01:15:32.440> with<01:15:32.469> like<01:15:32.829> kind<01:15:33.159> so<01:15:33.369> similar 01:15:33.750 --> 01:15:33.760 align:start position:0% I have come up with like kind so similar 01:15:33.760 --> 01:15:35.609 align:start position:0% I have come up with like kind so similar to<01:15:34.000> the<01:15:34.150> way<01:15:34.270> the<01:15:34.300> tours<01:15:34.960> are<01:15:35.050> done<01:15:35.260> was<01:15:35.469> the 01:15:35.609 --> 01:15:35.619 align:start position:0% to the way the tours are done was the 01:15:35.619 --> 01:15:37.680 align:start position:0% to the way the tours are done was the opcodes<01:15:36.039> I've<01:15:36.550> kind<01:15:36.789> of<01:15:36.820> come<01:15:36.969> up<01:15:37.059> with<01:15:37.119> way<01:15:37.389> of 01:15:37.680 --> 01:15:37.690 align:start position:0% opcodes I've kind of come up with way of 01:15:37.690 --> 01:15:40.620 align:start position:0% opcodes I've kind of come up with way of compressing<01:15:38.409> like<01:15:38.829> the<01:15:38.949> offset<01:15:39.369> concept<01:15:40.059> here 01:15:40.620 --> 01:15:40.630 align:start position:0% compressing like the offset concept here 01:15:40.630 --> 01:15:42.540 align:start position:0% compressing like the offset concept here and<01:15:40.750> I<01:15:40.809> think<01:15:41.050> that<01:15:41.170> that<01:15:41.380> can<01:15:41.590> provide<01:15:41.949> a<01:15:42.010> good 01:15:42.540 --> 01:15:42.550 align:start position:0% and I think that that can provide a good 01:15:42.550 --> 01:15:45.060 align:start position:0% and I think that that can provide a good way<01:15:42.699> of<01:15:42.820> removing<01:15:43.090> the<01:15:43.449> zero<01:15:43.719> hashes<01:15:44.170> and 01:15:45.060 --> 01:15:45.070 align:start position:0% way of removing the zero hashes and 01:15:45.070 --> 01:15:46.529 align:start position:0% way of removing the zero hashes and basically<01:15:45.699> is<01:15:45.909> like<01:15:46.059> if<01:15:46.300> you're<01:15:46.510> not 01:15:46.529 --> 01:15:46.539 align:start position:0% basically is like if you're not 01:15:46.539 --> 01:15:48.839 align:start position:0% basically is like if you're not traversing<01:15:47.320> those<01:15:47.500> offsets<01:15:47.920> any<01:15:48.130> boosters 01:15:48.839 --> 01:15:48.849 align:start position:0% traversing those offsets any boosters 01:15:48.849 --> 01:15:50.220 align:start position:0% traversing those offsets any boosters for<01:15:48.969> persons<01:15:49.300> with<01:15:49.360> future<01:15:49.960> bursts<01:15:50.139> like 01:15:50.220 --> 01:15:50.230 align:start position:0% for persons with future bursts like 01:15:50.230 --> 01:15:52.830 align:start position:0% for persons with future bursts like through<01:15:50.440> the<01:15:50.530> same<01:15:50.880> team<01:15:51.880> direction<01:15:52.360> for<01:15:52.719> like 01:15:52.830 --> 01:15:52.840 align:start position:0% through the same team direction for like 01:15:52.840 --> 01:15:54.180 align:start position:0% through the same team direction for like many<01:15:53.050> different<01:15:53.349> levels<01:15:53.619> and<01:15:53.980> you<01:15:54.039> should 01:15:54.180 --> 01:15:54.190 align:start position:0% many different levels and you should 01:15:54.190 --> 01:15:55.890 align:start position:0% many different levels and you should just<01:15:54.280> go<01:15:54.429> to<01:15:54.460> compress<01:15:54.909> that<01:15:54.940> and<01:15:55.659> by 01:15:55.890 --> 01:15:55.900 align:start position:0% just go to compress that and by 01:15:55.900 --> 01:16:00.390 align:start position:0% just go to compress that and by compressing<01:15:56.289> that<01:15:56.409> you<01:15:56.590> would<01:15:56.710> know 01:16:00.390 --> 01:16:00.400 align:start position:0% 01:16:00.400 --> 01:16:06.400 align:start position:0% so<01:16:01.400> how<01:16:01.610> many<01:16:01.760> numbers<01:16:04.510> so<01:16:05.510> next<01:16:05.660> up<01:16:05.780> is<01:16:05.930> all<01:16:06.260> of 01:16:06.400 --> 01:16:06.410 align:start position:0% so how many numbers so next up is all of 01:16:06.410 --> 01:16:08.380 align:start position:0% so how many numbers so next up is all of these<01:16:06.500> ants<01:16:06.800> eats<01:16:07.010> gonna<01:16:07.250> talk<01:16:07.460> about<01:16:07.610> this 01:16:08.380 --> 01:16:08.390 align:start position:0% these ants eats gonna talk about this 01:16:08.390 --> 01:16:20.940 align:start position:0% these ants eats gonna talk about this stateless<01:16:08.990> Virgo<01:16:09.320> treats<01:16:09.590> okay<01:16:19.300> lots<01:16:20.300> of<01:16:20.420> work 01:16:20.940 --> 01:16:20.950 align:start position:0% stateless Virgo treats okay lots of work 01:16:20.950 --> 01:16:23.760 align:start position:0% stateless Virgo treats okay lots of work right 01:16:23.760 --> 01:16:23.770 align:start position:0% right 01:16:23.770 --> 01:16:26.410 align:start position:0% right it's<01:16:24.770> a<01:16:24.830> one<01:16:25.010> slide<01:16:25.310> presentation<01:16:26.000> by<01:16:26.180> the<01:16:26.210> way 01:16:26.410 --> 01:16:26.420 align:start position:0% it's a one slide presentation by the way 01:16:26.420 --> 01:16:31.180 align:start position:0% it's a one slide presentation by the way for<01:16:26.660> me<01:16:27.700> lots<01:16:28.700> of<01:16:28.820> work<01:16:29.060> to<01:16:29.780> write<01:16:30.470> a<01:16:30.530> tease<01:16:30.830> but 01:16:31.180 --> 01:16:31.190 align:start position:0% for me lots of work to write a tease but 01:16:31.190 --> 01:16:33.460 align:start position:0% for me lots of work to write a tease but I<01:16:31.880> think<01:16:32.090> the<01:16:32.720> question<01:16:32.990> is<01:16:33.050> how<01:16:33.200> to<01:16:33.230> make<01:16:33.440> it 01:16:33.460 --> 01:16:33.470 align:start position:0% I think the question is how to make it 01:16:33.470 --> 01:16:35.050 align:start position:0% I think the question is how to make it usable<01:16:33.830> I<01:16:33.980> think<01:16:34.190> that<01:16:34.340> this<01:16:34.460> is<01:16:34.610> the<01:16:34.730> base 01:16:35.050 --> 01:16:35.060 align:start position:0% usable I think that this is the base 01:16:35.060 --> 01:16:39.370 align:start position:0% usable I think that this is the base because<01:16:35.330> it's<01:16:35.510> a<01:16:35.780> stateless<01:16:37.450> model<01:16:38.450> and<01:16:38.660> I'll 01:16:39.370 --> 01:16:39.380 align:start position:0% because it's a stateless model and I'll 01:16:39.380 --> 01:16:42.460 align:start position:0% because it's a stateless model and I'll explain<01:16:39.650> this<01:16:39.830> in<01:16:39.890> a<01:16:40.100> moment<01:16:41.140> so<01:16:42.140> everything 01:16:42.460 --> 01:16:42.470 align:start position:0% explain this in a moment so everything 01:16:42.470 --> 01:16:44.410 align:start position:0% explain this in a moment so everything is<01:16:42.590> stateless<01:16:42.920> and<01:16:43.070> that's<01:16:43.520> -<01:16:43.730> so<01:16:43.760> how<01:16:44.360> many 01:16:44.410 --> 01:16:44.420 align:start position:0% is stateless and that's - so how many 01:16:44.420 --> 01:16:46.420 align:start position:0% is stateless and that's - so how many DAP<01:16:44.660> developers<01:16:45.200> doing<01:16:45.590> that<01:16:45.800> never<01:16:46.070> complain 01:16:46.420 --> 01:16:46.430 align:start position:0% DAP developers doing that never complain 01:16:46.430 --> 01:16:49.360 align:start position:0% DAP developers doing that never complain fairness<01:16:47.410> so<01:16:48.410> a<01:16:48.470> few<01:16:48.680> so<01:16:48.860> this<01:16:49.010> is<01:16:49.130> sort<01:16:49.340> of 01:16:49.360 --> 01:16:49.370 align:start position:0% fairness so a few so this is sort of 01:16:49.370 --> 01:16:51.580 align:start position:0% fairness so a few so this is sort of what<01:16:49.910> the<01:16:50.030> who<01:16:50.450> this<01:16:50.540> talk<01:16:50.780> is<01:16:50.900> targeted<01:16:51.320> at 01:16:51.580 --> 01:16:51.590 align:start position:0% what the who this talk is targeted at 01:16:51.590 --> 01:16:53.710 align:start position:0% what the who this talk is targeted at but<01:16:51.920> there's<01:16:52.100> less<01:16:52.880> than<01:16:53.090> I<01:16:53.150> expect<01:16:53.480> it<01:16:53.600> to<01:16:53.630> be 01:16:53.710 --> 01:16:53.720 align:start position:0% but there's less than I expect it to be 01:16:53.720 --> 01:16:57.460 align:start position:0% but there's less than I expect it to be here<01:16:54.250> but<01:16:55.250> for<01:16:55.790> the<01:16:55.850> maybe<01:16:56.420> everyone<01:16:57.380> is 01:16:57.460 --> 01:16:57.470 align:start position:0% here but for the maybe everyone is 01:16:57.470 --> 01:16:59.410 align:start position:0% here but for the maybe everyone is interested<01:16:57.890> how<01:16:58.040> are<01:16:58.160> we<01:16:58.250> gonna<01:16:58.370> do<01:16:58.610> stateless 01:16:59.410 --> 01:16:59.420 align:start position:0% interested how are we gonna do stateless 01:16:59.420 --> 01:17:03.340 align:start position:0% interested how are we gonna do stateless what's<01:17:00.290> the<01:17:00.470> throughput<01:17:01.690> but<01:17:02.690> you<01:17:02.900> know<01:17:02.990> how 01:17:03.340 --> 01:17:03.350 align:start position:0% what's the throughput but you know how 01:17:03.350 --> 01:17:06.010 align:start position:0% what's the throughput but you know how does<01:17:03.560> the<01:17:03.620> policy<01:17:04.040> they're<01:17:04.160> gonna<01:17:04.280> work<01:17:05.020> you 01:17:06.010 --> 01:17:06.020 align:start position:0% does the policy they're gonna work you 01:17:06.020 --> 01:17:07.600 align:start position:0% does the policy they're gonna work you know<01:17:06.170> if<01:17:06.380> we<01:17:06.500> have<01:17:06.590> stateless<01:17:07.010> we're<01:17:07.160> passing 01:17:07.600 --> 01:17:07.610 align:start position:0% know if we have stateless we're passing 01:17:07.610 --> 01:17:09.160 align:start position:0% know if we have stateless we're passing so<01:17:07.760> many<01:17:07.910> hashes<01:17:08.300> and<01:17:08.510> with<01:17:08.660> the<01:17:08.750> call<01:17:08.960> data 01:17:09.160 --> 01:17:09.170 align:start position:0% so many hashes and with the call data 01:17:09.170 --> 01:17:10.870 align:start position:0% so many hashes and with the call data this<01:17:09.500> dominates<01:17:09.920> the<01:17:10.100> called<01:17:10.340> a<01:17:10.490> ton<01:17:10.700> crop 01:17:10.870 --> 01:17:10.880 align:start position:0% this dominates the called a ton crop 01:17:10.880 --> 01:17:11.890 align:start position:0% this dominates the called a ton crop what<01:17:11.180> is<01:17:11.300> it<01:17:11.390> going<01:17:11.480> to<01:17:11.540> be<01:17:11.630> like<01:17:11.750> one 01:17:11.890 --> 01:17:11.900 align:start position:0% what is it going to be like one 01:17:11.900 --> 01:17:13.990 align:start position:0% what is it going to be like one transaction<01:17:12.470> per<01:17:12.620> selecting<01:17:12.980> -<01:17:13.160> I<01:17:13.400> mean<01:17:13.850> is<01:17:13.970> it 01:17:13.990 --> 01:17:14.000 align:start position:0% transaction per selecting - I mean is it 01:17:14.000 --> 01:17:15.370 align:start position:0% transaction per selecting - I mean is it was<01:17:14.270> this<01:17:14.360> he<01:17:14.480> could<01:17:14.600> make<01:17:14.750> sense<01:17:14.960> to<01:17:15.110> begin 01:17:15.370 --> 01:17:15.380 align:start position:0% was this he could make sense to begin 01:17:15.380 --> 01:17:17.830 align:start position:0% was this he could make sense to begin with<01:17:15.610> and<01:17:16.610> that's<01:17:16.700> what<01:17:16.880> I<01:17:16.910> thought<01:17:17.180> about<01:17:17.600> an 01:17:17.830 --> 01:17:17.840 align:start position:0% with and that's what I thought about an 01:17:17.840 --> 01:17:20.020 align:start position:0% with and that's what I thought about an else<01:17:18.020> I<01:17:18.460> didn't<01:17:19.460> think<01:17:19.550> it<01:17:19.700> was<01:17:19.790> gonna<01:17:19.940> work 01:17:20.020 --> 01:17:20.030 align:start position:0% else I didn't think it was gonna work 01:17:20.030 --> 01:17:23.770 align:start position:0% else I didn't think it was gonna work and<01:17:20.360> I<01:17:20.690> have<01:17:21.110> a<01:17:21.140> little<01:17:21.410> bit<01:17:21.530> more<01:17:21.680> hope<01:17:21.860> now<01:17:22.780> it 01:17:23.770 --> 01:17:23.780 align:start position:0% and I have a little bit more hope now it 01:17:23.780 --> 01:17:26.170 align:start position:0% and I have a little bit more hope now it might<01:17:23.960> work<01:17:24.640> but<01:17:25.640> we<01:17:25.790> have<01:17:25.880> to<01:17:25.970> be<01:17:26.060> very 01:17:26.170 --> 01:17:26.180 align:start position:0% might work but we have to be very 01:17:26.180 --> 01:17:28.300 align:start position:0% might work but we have to be very careful<01:17:26.690> in<01:17:26.750> this<01:17:27.080> this<01:17:27.500> for<01:17:28.100> the<01:17:28.160> deaf 01:17:28.300 --> 01:17:28.310 align:start position:0% careful in this this for the deaf 01:17:28.310 --> 01:17:30.550 align:start position:0% careful in this this for the deaf developers<01:17:28.850> in<01:17:29.030> the<01:17:29.090> room<01:17:29.200> this<01:17:30.200> is<01:17:30.260> sort<01:17:30.530> of 01:17:30.550 --> 01:17:30.560 align:start position:0% developers in the room this is sort of 01:17:30.560 --> 01:17:36.070 align:start position:0% developers in the room this is sort of the<01:17:30.710> basis<01:17:31.570> these<01:17:32.570> Merkle<01:17:34.630> having<01:17:35.630> states<01:17:35.930> so 01:17:36.070 --> 01:17:36.080 align:start position:0% the basis these Merkle having states so 01:17:36.080 --> 01:17:38.200 align:start position:0% the basis these Merkle having states so you<01:17:36.170> want<01:17:36.350> to<01:17:36.580> persist<01:17:37.580> 8<01:17:37.790> but<01:17:37.940> you<01:17:38.000> have<01:17:38.090> to 01:17:38.200 --> 01:17:38.210 align:start position:0% you want to persist 8 but you have to 01:17:38.210 --> 01:17:40.630 align:start position:0% you want to persist 8 but you have to you<01:17:38.390> know<01:17:38.480> hash<01:17:38.660> it<01:17:38.840> up<01:17:38.960> somehow<01:17:39.740> we<01:17:40.280> know<01:17:40.400> that 01:17:40.630 --> 01:17:40.640 align:start position:0% you know hash it up somehow we know that 01:17:40.640 --> 01:17:41.980 align:start position:0% you know hash it up somehow we know that there<01:17:40.760> are<01:17:40.790> other<01:17:41.000> accumulators<01:17:41.630> there's<01:17:41.840> art 01:17:41.980 --> 01:17:41.990 align:start position:0% there are other accumulators there's art 01:17:41.990 --> 01:17:43.450 align:start position:0% there are other accumulators there's art there<01:17:42.200> RSA<01:17:42.650> maybe<01:17:42.920> some<01:17:43.070> zero-knowledge 01:17:43.450 --> 01:17:43.460 align:start position:0% there RSA maybe some zero-knowledge 01:17:43.460 --> 01:17:46.300 align:start position:0% there RSA maybe some zero-knowledge stuff<01:17:43.790> i<01:17:44.120> think<01:17:44.690> those<01:17:44.960> have<01:17:45.110> big<01:17:45.590> use<01:17:46.070> cases 01:17:46.300 --> 01:17:46.310 align:start position:0% stuff i think those have big use cases 01:17:46.310 --> 01:17:48.640 align:start position:0% stuff i think those have big use cases but<01:17:46.460> I<01:17:46.550> think<01:17:46.760> that<01:17:46.850> the<01:17:46.940> Merkle<01:17:47.410> trees<01:17:48.410> also 01:17:48.640 --> 01:17:48.650 align:start position:0% but I think that the Merkle trees also 01:17:48.650 --> 01:17:50.110 align:start position:0% but I think that the Merkle trees also have<01:17:48.800> big<01:17:48.980> use<01:17:49.130> cases<01:17:49.370> but<01:17:49.580> we<01:17:49.730> need<01:17:49.880> trees 01:17:50.110 --> 01:17:50.120 align:start position:0% have big use cases but we need trees 01:17:50.120 --> 01:17:52.000 align:start position:0% have big use cases but we need trees that<01:17:50.390> have<01:17:50.570> like<01:17:50.720> deaf<01:17:50.930> Millions 01:17:52.000 --> 01:17:52.010 align:start position:0% that have like deaf Millions 01:17:52.010 --> 01:17:55.360 align:start position:0% that have like deaf Millions like<01:17:52.190> you<01:17:52.310> know<01:17:52.510> thousand<01:17:53.510> three<01:17:53.660> millions<01:17:54.370> of 01:17:55.360 --> 01:17:55.370 align:start position:0% like you know thousand three millions of 01:17:55.370 --> 01:17:58.270 align:start position:0% like you know thousand three millions of in<01:17:55.820> depth<01:17:56.530> so<01:17:57.530> that's<01:17:57.710> the<01:17:57.890> big<01:17:58.040> problem 01:17:58.270 --> 01:17:58.280 align:start position:0% in depth so that's the big problem 01:17:58.280 --> 01:17:59.730 align:start position:0% in depth so that's the big problem that's<01:17:58.580> the<01:17:58.730> big<01:17:58.880> challenge<01:17:59.060> we<01:17:59.360> need 01:17:59.730 --> 01:17:59.740 align:start position:0% that's the big challenge we need 01:17:59.740 --> 01:18:02.200 align:start position:0% that's the big challenge we need breakthroughs<01:18:00.740> and<01:18:00.890> we<01:18:01.010> need<01:18:01.160> you<01:18:02.090> know 01:18:02.200 --> 01:18:02.210 align:start position:0% breakthroughs and we need you know 01:18:02.210 --> 01:18:04.990 align:start position:0% breakthroughs and we need you know efficient<01:18:02.810> Merkle<01:18:03.350> trees<01:18:03.710> for<01:18:04.130> to<01:18:04.250> make<01:18:04.370> EF<01:18:04.760> to 01:18:04.990 --> 01:18:05.000 align:start position:0% efficient Merkle trees for to make EF to 01:18:05.000 --> 01:18:06.490 align:start position:0% efficient Merkle trees for to make EF to the<01:18:05.240> stateless<01:18:05.510> idea<01:18:05.810> that<01:18:05.930> even<01:18:06.140> worked<01:18:06.320> for 01:18:06.490 --> 01:18:06.500 align:start position:0% the stateless idea that even worked for 01:18:06.500 --> 01:18:09.220 align:start position:0% the stateless idea that even worked for 30<01:18:06.680> goods<01:18:07.010> so<01:18:07.190> so<01:18:08.120> now<01:18:08.240> is<01:18:08.300> Mike<01:18:08.510> you<01:18:09.110> know<01:18:09.200> I 01:18:09.220 --> 01:18:09.230 align:start position:0% 30 goods so so now is Mike you know I 01:18:09.230 --> 01:18:12.880 align:start position:0% 30 goods so so now is Mike you know I thought<01:18:09.470> about<01:18:09.530> this<01:18:09.860> for<01:18:10.100> a<01:18:10.310> long<01:18:10.460> time<01:18:11.890> so 01:18:12.880 --> 01:18:12.890 align:start position:0% thought about this for a long time so 01:18:12.890 --> 01:18:14.410 align:start position:0% thought about this for a long time so the<01:18:13.010> two<01:18:13.160> big<01:18:13.310> things<01:18:13.370> are<01:18:13.730> called<01:18:13.970> data<01:18:14.120> size 01:18:14.410 --> 01:18:14.420 align:start position:0% the two big things are called data size 01:18:14.420 --> 01:18:16.360 align:start position:0% the two big things are called data size and<01:18:14.630> run<01:18:14.780> time<01:18:15.080> and<01:18:15.380> there<01:18:16.010> are<01:18:16.040> trade-offs 01:18:16.360 --> 01:18:16.370 align:start position:0% and run time and there are trade-offs 01:18:16.370 --> 01:18:17.770 align:start position:0% and run time and there are trade-offs between<01:18:16.580> them<01:18:16.910> of<01:18:17.000> course<01:18:17.210> there<01:18:17.420> are<01:18:17.450> speeds 01:18:17.770 --> 01:18:17.780 align:start position:0% between them of course there are speeds 01:18:17.780 --> 01:18:21.940 align:start position:0% between them of course there are speeds size<01:18:18.500> be<01:18:18.740> trade-offs<01:18:20.440> but<01:18:21.440> so<01:18:21.710> I'm<01:18:21.770> gonna 01:18:21.940 --> 01:18:21.950 align:start position:0% size be trade-offs but so I'm gonna 01:18:21.950 --> 01:18:27.070 align:start position:0% size be trade-offs but so I'm gonna explain<01:18:22.250> I<01:18:25.060> wrote<01:18:26.060> everything<01:18:26.270> in<01:18:26.450> C<01:18:26.660> violate 01:18:27.070 --> 01:18:27.080 align:start position:0% explain I wrote everything in C violate 01:18:27.080 --> 01:18:28.110 align:start position:0% explain I wrote everything in C violate chopin's 01:18:28.110 --> 01:18:28.120 align:start position:0% chopin's 01:18:28.120 --> 01:18:31.780 align:start position:0% chopin's C<01:18:29.120> fence<01:18:29.360> C<01:18:30.350> programming<01:18:30.740> Winston<01:18:31.130> okay<01:18:31.400> great 01:18:31.780 --> 01:18:31.790 align:start position:0% C fence C programming Winston okay great 01:18:31.790 --> 01:18:33.670 align:start position:0% C fence C programming Winston okay great so<01:18:32.210> there<01:18:32.330> are<01:18:32.450> people<01:18:32.630> maybe<01:18:33.230> they're<01:18:33.590> not 01:18:33.670 --> 01:18:33.680 align:start position:0% so there are people maybe they're not 01:18:33.680 --> 01:18:35.110 align:start position:0% so there are people maybe they're not interested<01:18:34.040> in<01:18:34.130> writing<01:18:34.250> the<01:18:34.400> absence<01:18:34.820> T<01:18:34.940> but 01:18:35.110 --> 01:18:35.120 align:start position:0% interested in writing the absence T but 01:18:35.120 --> 01:18:37.560 align:start position:0% interested in writing the absence T but I<01:18:35.360> think<01:18:35.930> C<01:18:36.080> is<01:18:36.140> a<01:18:36.200> reasonable<01:18:36.620> language<01:18:36.980> I 01:18:37.560 --> 01:18:37.570 align:start position:0% I think C is a reasonable language I 01:18:37.570 --> 01:18:40.750 align:start position:0% I think C is a reasonable language I think<01:18:38.570> we<01:18:38.840> have<01:18:38.960> to<01:18:39.050> be<01:18:39.140> efficient<01:18:39.560> also<01:18:39.760> when 01:18:40.750 --> 01:18:40.760 align:start position:0% think we have to be efficient also when 01:18:40.760 --> 01:18:42.130 align:start position:0% think we have to be efficient also when were<01:18:40.850> writing<01:18:41.000> EES<01:18:41.390> everything<01:18:41.810> has<01:18:41.930> to<01:18:42.050> be 01:18:42.130 --> 01:18:42.140 align:start position:0% were writing EES everything has to be 01:18:42.140 --> 01:18:43.840 align:start position:0% were writing EES everything has to be you<01:18:42.320> know<01:18:42.410> micromanage<01:18:43.190> we'd<01:18:43.430> like<01:18:43.670> you<01:18:43.790> know 01:18:43.840 --> 01:18:43.850 align:start position:0% you know micromanage we'd like you know 01:18:43.850 --> 01:18:46.780 align:start position:0% you know micromanage we'd like you know embedded<01:18:44.210> systems<01:18:45.010> we<01:18:46.010> have<01:18:46.100> limited<01:18:46.520> you 01:18:46.780 --> 01:18:46.790 align:start position:0% embedded systems we have limited you 01:18:46.790 --> 01:18:50.140 align:start position:0% embedded systems we have limited you know<01:18:46.820> memory<01:18:47.240> limited<01:18:48.100> cycles<01:18:49.100> CPU<01:18:49.580> cycles<01:18:50.000> so 01:18:50.140 --> 01:18:50.150 align:start position:0% know memory limited cycles CPU cycles so 01:18:50.150 --> 01:18:52.270 align:start position:0% know memory limited cycles CPU cycles so we<01:18:50.240> have<01:18:50.360> to<01:18:50.450> do<01:18:50.570> everything<01:18:50.810> we<01:18:51.710> have<01:18:52.130> to 01:18:52.270 --> 01:18:52.280 align:start position:0% we have to do everything we have to 01:18:52.280 --> 01:18:54.160 align:start position:0% we have to do everything we have to listen<01:18:53.060> to<01:18:53.090> them<01:18:53.300> invited<01:18:53.570> systems<01:18:53.930> people 01:18:54.160 --> 01:18:54.170 align:start position:0% listen to them invited systems people 01:18:54.170 --> 01:18:55.300 align:start position:0% listen to them invited systems people and<01:18:54.260> do<01:18:54.320> everything<01:18:54.650> as<01:18:54.770> efficiently<01:18:55.160> as 01:18:55.300 --> 01:18:55.310 align:start position:0% and do everything as efficiently as 01:18:55.310 --> 01:18:58.870 align:start position:0% and do everything as efficiently as possible<01:18:56.740> and<01:18:57.740> there<01:18:57.890> are<01:18:57.980> you<01:18:58.190> know<01:18:58.220> many 01:18:58.870 --> 01:18:58.880 align:start position:0% possible and there are you know many 01:18:58.880 --> 01:19:00.430 align:start position:0% possible and there are you know many years<01:18:59.120> of<01:18:59.300> accumulated<01:18:59.780> knowledge<01:19:00.020> in<01:19:00.320> this 01:19:00.430 --> 01:19:00.440 align:start position:0% years of accumulated knowledge in this 01:19:00.440 --> 01:19:03.040 align:start position:0% years of accumulated knowledge in this kind<01:19:00.650> of<01:19:00.710> area<01:19:00.980> so<01:19:01.610> called<01:19:01.910> data<01:19:02.090> size<01:19:02.330> so<01:19:02.510> -<01:19:02.690> so 01:19:03.040 --> 01:19:03.050 align:start position:0% kind of area so called data size so - so 01:19:03.050 --> 01:19:07.540 align:start position:0% kind of area so called data size so - so millions<01:19:03.650> four<01:19:03.920> million<01:19:04.210> -<01:19:05.210> to<01:19:05.330> the<01:19:05.560> 22<01:19:06.560> it 01:19:07.540 --> 01:19:07.550 align:start position:0% millions four million - to the 22 it 01:19:07.550 --> 01:19:09.550 align:start position:0% millions four million - to the 22 it comes<01:19:08.060> in<01:19:08.210> the<01:19:08.300> states<01:19:08.570> 40<01:19:09.110> accounts<01:19:09.320> in<01:19:09.500> the 01:19:09.550 --> 01:19:09.560 align:start position:0% comes in the states 40 accounts in the 01:19:09.560 --> 01:19:12.160 align:start position:0% comes in the states 40 accounts in the witness<01:19:09.920> what's<01:19:10.520> the<01:19:10.700> best<01:19:10.880> we<01:19:11.690> can<01:19:11.780> possibly 01:19:12.160 --> 01:19:12.170 align:start position:0% witness what's the best we can possibly 01:19:12.170 --> 01:19:14.470 align:start position:0% witness what's the best we can possibly want<01:19:12.380> to<01:19:12.500> be<01:19:12.560> dominated<01:19:13.160> by<01:19:13.310> hashes<01:19:14.240> and 01:19:14.470 --> 01:19:14.480 align:start position:0% want to be dominated by hashes and 01:19:14.480 --> 01:19:19.030 align:start position:0% want to be dominated by hashes and signatures<01:19:15.820> or<01:19:16.820> whatever<01:19:17.350> for<01:19:18.350> signatures 01:19:19.030 --> 01:19:19.040 align:start position:0% signatures or whatever for signatures 01:19:19.040 --> 01:19:20.650 align:start position:0% signatures or whatever for signatures for<01:19:19.160> the<01:19:19.220> transactions<01:19:19.850> I'm<01:19:19.970> sorry<01:19:20.180> if<01:19:20.360> you 01:19:20.650 --> 01:19:20.660 align:start position:0% for the transactions I'm sorry if you 01:19:20.660 --> 01:19:22.540 align:start position:0% for the transactions I'm sorry if you are<01:19:20.810> if<01:19:21.020> your<01:19:21.140> dad<01:19:21.350> is<01:19:21.380> using<01:19:21.710> but<01:19:22.280> that's<01:19:22.430> the 01:19:22.540 --> 01:19:22.550 align:start position:0% are if your dad is using but that's the 01:19:22.550 --> 01:19:24.400 align:start position:0% are if your dad is using but that's the goal<01:19:22.700> is<01:19:22.850> to<01:19:22.880> be<01:19:23.360> dominated<01:19:23.780> by<01:19:23.810> hashes<01:19:24.230> and 01:19:24.400 --> 01:19:24.410 align:start position:0% goal is to be dominated by hashes and 01:19:24.410 --> 01:19:27.340 align:start position:0% goal is to be dominated by hashes and then<01:19:24.530> the<01:19:25.070> tree<01:19:25.280> structure<01:19:26.110> you<01:19:27.110> know<01:19:27.200> the 01:19:27.340 --> 01:19:27.350 align:start position:0% then the tree structure you know the 01:19:27.350 --> 01:19:29.080 align:start position:0% then the tree structure you know the theoretical<01:19:27.860> limit<01:19:27.980> is<01:19:28.220> zero<01:19:28.430> percent<01:19:28.610> of 01:19:29.080 --> 01:19:29.090 align:start position:0% theoretical limit is zero percent of 01:19:29.090 --> 01:19:30.520 align:start position:0% theoretical limit is zero percent of your<01:19:29.270> call<01:19:29.510> data<01:19:29.690> is<01:19:29.840> for<01:19:30.020> the<01:19:30.080> tree<01:19:30.260> structure 01:19:30.520 --> 01:19:30.530 align:start position:0% your call data is for the tree structure 01:19:30.530 --> 01:19:33.100 align:start position:0% your call data is for the tree structure but<01:19:30.800> I<01:19:30.860> I<01:19:31.280> can<01:19:31.880> get<01:19:32.000> it<01:19:32.090> less<01:19:32.300> less<01:19:32.780> than<01:19:32.810> one 01:19:33.100 --> 01:19:33.110 align:start position:0% but I I can get it less less than one 01:19:33.110 --> 01:19:35.320 align:start position:0% but I I can get it less less than one percent<01:19:33.470> that's<01:19:34.100> sort<01:19:34.490> of<01:19:34.520> a<01:19:34.640> great<01:19:35.090> thing 01:19:35.320 --> 01:19:35.330 align:start position:0% percent that's sort of a great thing 01:19:35.330 --> 01:19:39.370 align:start position:0% percent that's sort of a great thing there's<01:19:36.260> hope<01:19:36.640> so<01:19:37.960> you<01:19:38.960> know<01:19:39.050> this<01:19:39.200> is<01:19:39.290> the 01:19:39.370 --> 01:19:39.380 align:start position:0% there's hope so you know this is the 01:19:39.380 --> 01:19:40.660 align:start position:0% there's hope so you know this is the best<01:19:39.530> we<01:19:39.680> can<01:19:39.710> possibly<01:19:39.980> do<01:19:40.340> is<01:19:40.370> just 01:19:40.660 --> 01:19:40.670 align:start position:0% best we can possibly do is just 01:19:40.670 --> 01:19:43.930 align:start position:0% best we can possibly do is just dominated<01:19:41.570> by<01:19:41.630> hashes<01:19:42.020> and<01:19:42.430> this<01:19:43.430> is<01:19:43.550> 425 01:19:43.930 --> 01:19:43.940 align:start position:0% dominated by hashes and this is 425 01:19:43.940 --> 01:19:45.790 align:start position:0% dominated by hashes and this is 425 kilobytes<01:19:44.570> so<01:19:44.660> it's<01:19:44.840> close<01:19:45.020> to<01:19:45.050> etholon<01:19:45.560> stuff 01:19:45.790 --> 01:19:45.800 align:start position:0% kilobytes so it's close to etholon stuff 01:19:45.800 --> 01:19:47.470 align:start position:0% kilobytes so it's close to etholon stuff but<01:19:45.980> you<01:19:46.070> can<01:19:46.220> double<01:19:46.550> and<01:19:47.030> so<01:19:47.210> you 01:19:47.470 --> 01:19:47.480 align:start position:0% but you can double and so you 01:19:47.480 --> 01:19:49.110 align:start position:0% but you can double and so you say<01:19:47.570> 80<01:19:47.780> but<01:19:48.200> it's<01:19:48.320> a<01:19:48.380> little<01:19:48.500> better<01:19:48.710> because 01:19:49.110 --> 01:19:49.120 align:start position:0% say 80 but it's a little better because 01:19:49.120 --> 01:19:51.970 align:start position:0% say 80 but it's a little better because there<01:19:50.120> are<01:19:50.210> two<01:19:50.330> things<01:19:50.360> the<01:19:51.260> two<01:19:51.560> first<01:19:51.860> two 01:19:51.970 --> 01:19:51.980 align:start position:0% there are two things the two first two 01:19:51.980 --> 01:19:54.280 align:start position:0% there are two things the two first two trips<01:19:52.340> and<01:19:52.640> then<01:19:52.820> two<01:19:53.330> more<01:19:53.840> tricks<01:19:54.080> that<01:19:54.200> are 01:19:54.280 --> 01:19:54.290 align:start position:0% trips and then two more tricks that are 01:19:54.290 --> 01:19:55.990 align:start position:0% trips and then two more tricks that are being<01:19:54.440> worked<01:19:54.890> and<01:19:55.130> then<01:19:55.220> another<01:19:55.430> sort<01:19:55.940> of 01:19:55.990 --> 01:19:56.000 align:start position:0% being worked and then another sort of 01:19:56.000 --> 01:19:58.330 align:start position:0% being worked and then another sort of few<01:19:56.180> things<01:19:56.390> we<01:19:56.810> need<01:19:56.840> like<01:19:56.989> two<01:19:57.620> orders<01:19:58.310> of 01:19:58.330 --> 01:19:58.340 align:start position:0% few things we need like two orders of 01:19:58.340 --> 01:19:59.890 align:start position:0% few things we need like two orders of magnitude<01:19:58.460> increase<01:19:59.180> in<01:19:59.330> another<01:19:59.600> one<01:19:59.780> in 01:19:59.890 --> 01:19:59.900 align:start position:0% magnitude increase in another one in 01:19:59.900 --> 01:20:01.270 align:start position:0% magnitude increase in another one in another<01:19:59.989> big<01:20:00.320> trip<01:20:00.560> in<01:20:00.650> another<01:20:00.860> victory<01:20:01.130> we 01:20:01.270 --> 01:20:01.280 align:start position:0% another big trip in another victory we 01:20:01.280 --> 01:20:03.100 align:start position:0% another big trip in another victory we need<01:20:01.400> a<01:20:01.430> bunch<01:20:01.640> of<01:20:01.730> those<01:20:01.850> two<01:20:02.120> exes<01:20:02.390> increases 01:20:03.100 --> 01:20:03.110 align:start position:0% need a bunch of those two exes increases 01:20:03.110 --> 01:20:04.420 align:start position:0% need a bunch of those two exes increases to<01:20:03.200> make<01:20:03.320> this<01:20:03.410> even<01:20:03.650> feasible<01:20:04.010> but<01:20:04.130> I<01:20:04.220> think 01:20:04.420 --> 01:20:04.430 align:start position:0% to make this even feasible but I think 01:20:04.430 --> 01:20:09.250 align:start position:0% to make this even feasible but I think it<01:20:05.360> might<01:20:05.840> be<01:20:05.870> possible<01:20:07.600> so<01:20:08.600> binary<01:20:08.840> tree<01:20:09.200> is 01:20:09.250 --> 01:20:09.260 align:start position:0% it might be possible so binary tree is 01:20:09.260 --> 01:20:12.940 align:start position:0% it might be possible so binary tree is the<01:20:09.380> first<01:20:09.620> thing<01:20:10.390> why<01:20:11.390> is<01:20:11.450> binary<01:20:12.320> tree<01:20:12.680> more 01:20:12.940 --> 01:20:12.950 align:start position:0% the first thing why is binary tree more 01:20:12.950 --> 01:20:15.610 align:start position:0% the first thing why is binary tree more efficient<01:20:13.810> than<01:20:14.810> the<01:20:14.930> hex<01:20:15.140> there<01:20:15.290> you<01:20:15.440> saw 01:20:15.610 --> 01:20:15.620 align:start position:0% efficient than the hex there you saw 01:20:15.620 --> 01:20:18.100 align:start position:0% efficient than the hex there you saw that<01:20:15.739> the<01:20:15.980> tree<01:20:16.190> with<01:20:16.370> the<01:20:16.480> sixteen<01:20:17.480> leaves 01:20:18.100 --> 01:20:18.110 align:start position:0% that the tree with the sixteen leaves 01:20:18.110 --> 01:20:20.260 align:start position:0% that the tree with the sixteen leaves and<01:20:18.500> then<01:20:18.680> these<01:20:18.830> trees<01:20:19.280> have<01:20:19.520> sort<01:20:19.760> of<01:20:19.790> two 01:20:20.260 --> 01:20:20.270 align:start position:0% and then these trees have sort of two 01:20:20.270 --> 01:20:25.510 align:start position:0% and then these trees have sort of two leaves<01:20:20.540> II<01:20:20.690> okay<01:20:21.230> why<01:20:22.630> why<01:20:23.630> is<01:20:23.690> binary<01:20:24.520> pack 01:20:25.510 --> 01:20:25.520 align:start position:0% leaves II okay why why is binary pack 01:20:25.520 --> 01:20:28.900 align:start position:0% leaves II okay why why is binary pack Surrey<01:20:25.730> is<01:20:26.570> then<01:20:27.070> the<01:20:28.070> other<01:20:28.220> is<01:20:28.580> nothing<01:20:28.880> that 01:20:28.900 --> 01:20:28.910 align:start position:0% Surrey is then the other is nothing that 01:20:28.910 --> 01:20:31.510 align:start position:0% Surrey is then the other is nothing that little<01:20:29.360> bit<01:20:29.480> of<01:20:29.600> the<01:20:29.690> Hat<01:20:29.920> yes<01:20:30.920> so<01:20:31.220> there<01:20:31.370> so 01:20:31.510 --> 01:20:31.520 align:start position:0% little bit of the Hat yes so there so 01:20:31.520 --> 01:20:33.670 align:start position:0% little bit of the Hat yes so there so for<01:20:31.670> for<01:20:31.910> purpose<01:20:32.780> I'm<01:20:33.080> sorry<01:20:33.260> interrupting 01:20:33.670 --> 01:20:33.680 align:start position:0% for for purpose I'm sorry interrupting 01:20:33.680 --> 01:20:35.920 align:start position:0% for for purpose I'm sorry interrupting for<01:20:33.830> four<01:20:34.100> four<01:20:34.310> levels<01:20:34.760> here<01:20:35.480> you<01:20:35.600> need<01:20:35.720> one<01:20:35.900> - 01:20:35.920 --> 01:20:35.930 align:start position:0% for four four levels here you need one - 01:20:35.930 --> 01:20:38.380 align:start position:0% for four four levels here you need one - two<01:20:36.380> -<01:20:36.410> three<01:20:36.620> -<01:20:36.830> four<01:20:36.980> hashes<01:20:37.670> for<01:20:38.120> the<01:20:38.210> hex 01:20:38.380 --> 01:20:38.390 align:start position:0% two - three - four hashes for the hex 01:20:38.390 --> 01:20:41.500 align:start position:0% two - three - four hashes for the hex there<01:20:38.540> you<01:20:38.660> need<01:20:38.810> 15<01:20:39.350> hashes<01:20:39.739> so<01:20:40.180> four<01:20:41.180> versus 01:20:41.500 --> 01:20:41.510 align:start position:0% there you need 15 hashes so four versus 01:20:41.510 --> 01:20:43.260 align:start position:0% there you need 15 hashes so four versus 15<01:20:41.900> you<01:20:42.020> have<01:20:42.050> a<01:20:42.140> 4x 01:20:43.260 --> 01:20:43.270 align:start position:0% 15 you have a 4x 01:20:43.270 --> 01:20:45.040 align:start position:0% 15 you have a 4x improvement<01:20:44.270> in<01:20:44.360> the<01:20:44.450> call<01:20:44.630> data<01:20:44.810> size 01:20:45.040 --> 01:20:45.050 align:start position:0% improvement in the call data size 01:20:45.050 --> 01:20:47.050 align:start position:0% improvement in the call data size freezing<01:20:45.800> binary<01:20:46.130> so<01:20:46.250> I<01:20:46.310> think<01:20:46.370> binary<01:20:46.820> tree 01:20:47.050 --> 01:20:47.060 align:start position:0% freezing binary so I think binary tree 01:20:47.060 --> 01:20:50.320 align:start position:0% freezing binary so I think binary tree are<01:20:47.150> a<01:20:47.480> good<01:20:47.660> option<01:20:48.190> I<01:20:49.190> think<01:20:49.820> that's<01:20:50.239> the 01:20:50.320 --> 01:20:50.330 align:start position:0% are a good option I think that's the 01:20:50.330 --> 01:20:52.210 align:start position:0% are a good option I think that's the best<01:20:50.510> we<01:20:50.660> can<01:20:50.690> do<01:20:50.960> okay<01:20:51.560> so<01:20:51.710> what<01:20:51.950> does<01:20:52.070> the 01:20:52.210 --> 01:20:52.220 align:start position:0% best we can do okay so what does the 01:20:52.220 --> 01:20:57.090 align:start position:0% best we can do okay so what does the tree<01:20:52.460> look<01:20:52.640> like<01:20:55.000> so<01:20:56.000> there's<01:20:56.480> a<01:20:56.540> paper<01:20:56.720> in 01:20:57.090 --> 01:20:57.100 align:start position:0% tree look like so there's a paper in 01:20:57.100 --> 01:20:58.780 align:start position:0% tree look like so there's a paper in 1990 01:20:58.780 --> 01:20:58.790 align:start position:0% 1990 01:20:58.790 --> 01:21:01.300 align:start position:0% 1990 captain<01:20:59.480> Jana<01:20:59.720> and<01:20:59.870> mech<01:21:00.200> and<01:21:00.380> then<01:21:00.470> they 01:21:01.300 --> 01:21:01.310 align:start position:0% captain Jana and mech and then they 01:21:01.310 --> 01:21:03.580 align:start position:0% captain Jana and mech and then they defined<01:21:01.640> two<01:21:01.730> children<01:21:02.120> pattern<01:21:02.450> sequence<01:21:02.810> so 01:21:03.580 --> 01:21:03.590 align:start position:0% defined two children pattern sequence so 01:21:03.590 --> 01:21:07.750 align:start position:0% defined two children pattern sequence so on<01:21:03.920> each<01:21:04.330> note<01:21:05.330> there's<01:21:05.780> a<01:21:05.840> label<01:21:06.230> 1<01:21:07.220> 1<01:21:07.460> means 01:21:07.750 --> 01:21:07.760 align:start position:0% on each note there's a label 1 1 means 01:21:07.760 --> 01:21:10.210 align:start position:0% on each note there's a label 1 1 means it<01:21:07.910> has<01:21:08.090> left<01:21:08.360> and<01:21:08.540> right<01:21:08.630> child<01:21:08.930> 1<01:21:09.560> 0<01:21:09.830> means<01:21:10.100> it 01:21:10.210 --> 01:21:10.220 align:start position:0% it has left and right child 1 0 means it 01:21:10.220 --> 01:21:11.890 align:start position:0% it has left and right child 1 0 means it only<01:21:10.280> has<01:21:10.580> a<01:21:10.610> left<01:21:10.850> child<01:21:11.120> and<01:21:11.390> there's<01:21:11.720> no 01:21:11.890 --> 01:21:11.900 align:start position:0% only has a left child and there's no 01:21:11.900 --> 01:21:13.510 align:start position:0% only has a left child and there's no right<01:21:12.080> child<01:21:12.110> I<01:21:12.500> interpreted<01:21:12.950> that<01:21:13.010> as<01:21:13.160> no 01:21:13.510 --> 01:21:13.520 align:start position:0% right child I interpreted that as no 01:21:13.520 --> 01:21:15.490 align:start position:0% right child I interpreted that as no right<01:21:13.700> child<01:21:13.730> as<01:21:14.060> being<01:21:14.090> being<01:21:14.690> a<01:21:14.750> hash<01:21:14.960> so 01:21:15.490 --> 01:21:15.500 align:start position:0% right child as being being a hash so 01:21:15.500 --> 01:21:16.810 align:start position:0% right child as being being a hash so there's<01:21:15.650> a<01:21:15.680> whole<01:21:15.860> you<01:21:16.100> know<01:21:16.160> sub<01:21:16.460> tree<01:21:16.670> each 01:21:16.810 --> 01:21:16.820 align:start position:0% there's a whole you know sub tree each 01:21:16.820 --> 01:21:18.310 align:start position:0% there's a whole you know sub tree each one<01:21:17.000> of<01:21:17.090> these<01:21:17.150> hashes<01:21:17.390> is<01:21:17.630> just<01:21:17.840> a<01:21:17.930> whole<01:21:18.170> big 01:21:18.310 --> 01:21:18.320 align:start position:0% one of these hashes is just a whole big 01:21:18.320 --> 01:21:23.320 align:start position:0% one of these hashes is just a whole big subtree<01:21:18.800> down<01:21:19.280> to<01:21:19.489> it<01:21:19.550> you<01:21:19.700> know<01:21:21.430> depth<01:21:22.430> 22<01:21:23.060> or 01:21:23.320 --> 01:21:23.330 align:start position:0% subtree down to it you know depth 22 or 01:21:23.330 --> 01:21:26.620 align:start position:0% subtree down to it you know depth 22 or 30<01:21:23.720> or<01:21:23.930> whatever<01:21:24.670> so<01:21:25.670> that's<01:21:25.790> we<01:21:26.360> don't<01:21:26.450> need 01:21:26.620 --> 01:21:26.630 align:start position:0% 30 or whatever so that's we don't need 01:21:26.630 --> 01:21:27.760 align:start position:0% 30 or whatever so that's we don't need that<01:21:26.750> in<01:21:26.870> the<01:21:26.960> witness<01:21:27.230> this<01:21:27.380> is<01:21:27.500> what<01:21:27.650> the 01:21:27.760 --> 01:21:27.770 align:start position:0% that in the witness this is what the 01:21:27.770 --> 01:21:32.380 align:start position:0% that in the witness this is what the witness<01:21:28.040> looks<01:21:28.280> like<01:21:28.489> and<01:21:30.220> so<01:21:31.220> the<01:21:31.430> 0<01:21:31.700> 1<01:21:32.000> means 01:21:32.380 --> 01:21:32.390 align:start position:0% witness looks like and so the 0 1 means 01:21:32.390 --> 01:21:36.010 align:start position:0% witness looks like and so the 0 1 means that<01:21:32.570> there's<01:21:32.750> a<01:21:33.530> hash<01:21:34.010> no<01:21:34.430> empty<01:21:35.030> left<01:21:35.480> child 01:21:36.010 --> 01:21:36.020 align:start position:0% that there's a hash no empty left child 01:21:36.020 --> 01:21:38.110 align:start position:0% that there's a hash no empty left child so<01:21:36.230> there's<01:21:36.350> a<01:21:36.470> hash<01:21:36.650> and<01:21:36.980> there<01:21:37.280> is<01:21:37.400> a<01:21:37.430> right 01:21:38.110 --> 01:21:38.120 align:start position:0% so there's a hash and there is a right 01:21:38.120 --> 01:21:41.140 align:start position:0% so there's a hash and there is a right child<01:21:38.300> so<01:21:38.720> 0<01:21:39.020> &<01:21:39.350> 1<01:21:39.550> you<01:21:40.550> know<01:21:40.700> the<01:21:40.820> first<01:21:41.000> thing 01:21:41.140 --> 01:21:41.150 align:start position:0% child so 0 & 1 you know the first thing 01:21:41.150 --> 01:21:43.960 align:start position:0% child so 0 & 1 you know the first thing is<01:21:41.270> a<01:21:41.300> 0<01:21:41.570> if<01:21:41.750> it's<01:21:41.900> a<01:21:41.960> hash<01:21:42.140> or<01:21:42.860> 1<01:21:43.430> if<01:21:43.640> it's<01:21:43.760> not<01:21:43.940> a 01:21:43.960 --> 01:21:43.970 align:start position:0% is a 0 if it's a hash or 1 if it's not a 01:21:43.970 --> 01:21:46.780 align:start position:0% is a 0 if it's a hash or 1 if it's not a catch<01:21:44.210> the<01:21:44.780> right<01:21:44.930> part<01:21:45.200> is<01:21:45.380> a<01:21:45.620> 1<01:21:45.800> if<01:21:45.980> it's<01:21:46.130> if 01:21:46.780 --> 01:21:46.790 align:start position:0% catch the right part is a 1 if it's if 01:21:46.790 --> 01:21:48.439 align:start position:0% catch the right part is a 1 if it's if it's<01:21:47.030> not<01:21:47.570> a<01:21:47.600> hash<01:21:47.810> at<01:21:47.989> 0 01:21:48.439 --> 01:21:48.449 align:start position:0% it's not a hash at 0 01:21:48.449 --> 01:21:49.910 align:start position:0% it's not a hash at 0 so<01:21:48.719> this<01:21:48.840> one<01:21:48.989> has<01:21:49.139> two<01:21:49.349> but<01:21:49.530> left<01:21:49.650> the<01:21:49.769> right 01:21:49.910 --> 01:21:49.920 align:start position:0% so this one has two but left the right 01:21:49.920 --> 01:21:51.410 align:start position:0% so this one has two but left the right shot<01:21:50.099> so<01:21:50.190> it's<01:21:50.340> one<01:21:50.489> one<01:21:50.670> so<01:21:50.880> it<01:21:50.999> sort<01:21:51.179> of<01:21:51.209> makes 01:21:51.410 --> 01:21:51.420 align:start position:0% shot so it's one one so it sort of makes 01:21:51.420 --> 01:21:52.430 align:start position:0% shot so it's one one so it sort of makes sense<01:21:51.539> the<01:21:51.719> one<01:21:51.869> means<01:21:52.079> that<01:21:52.260> there's 01:21:52.430 --> 01:21:52.440 align:start position:0% sense the one means that there's 01:21:52.440 --> 01:21:53.930 align:start position:0% sense the one means that there's something<01:21:52.619> there<01:21:52.829> and<01:21:53.130> the<01:21:53.429> zero<01:21:53.639> means<01:21:53.880> that 01:21:53.930 --> 01:21:53.940 align:start position:0% something there and the zero means that 01:21:53.940 --> 01:21:57.169 align:start position:0% something there and the zero means that there's<01:21:54.179> a<01:21:54.239> hash<01:21:54.389> thing<01:21:55.820> so<01:21:56.820> that's<01:21:56.999> the 01:21:57.169 --> 01:21:57.179 align:start position:0% there's a hash thing so that's the 01:21:57.179 --> 01:21:59.359 align:start position:0% there's a hash thing so that's the that's<01:21:57.510> the<01:21:57.630> note<01:21:58.289> labels<01:21:58.709> are<01:21:58.979> the<01:21:59.130> tree 01:21:59.359 --> 01:21:59.369 align:start position:0% that's the note labels are the tree 01:21:59.369 --> 01:22:00.709 align:start position:0% that's the note labels are the tree structure<01:21:59.670> that<01:21:59.909> enclose<01:22:00.179> it<01:22:00.329> and<01:22:00.449> that's<01:22:00.570> so 01:22:00.709 --> 01:22:00.719 align:start position:0% structure that enclose it and that's so 01:22:00.719 --> 01:22:04.699 align:start position:0% structure that enclose it and that's so small<01:22:01.050> it's<01:22:01.260> like<01:22:01.320> it's<01:22:01.679> less<01:22:02.039> than<01:22:02.190> 1%<01:22:03.709> then 01:22:04.699 --> 01:22:04.709 align:start position:0% small it's like it's less than 1% then 01:22:04.709 --> 01:22:06.350 align:start position:0% small it's like it's less than 1% then we<01:22:04.829> we<01:22:05.369> don't<01:22:05.489> need<01:22:05.639> these<01:22:05.789> agile<01:22:06.119> labels 01:22:06.350 --> 01:22:06.360 align:start position:0% we we don't need these agile labels 01:22:06.360 --> 01:22:07.580 align:start position:0% we we don't need these agile labels because<01:22:06.630> they're<01:22:06.780> already<01:22:06.900> given<01:22:07.229> to<01:22:07.260> us<01:22:07.380> and 01:22:07.580 --> 01:22:07.590 align:start position:0% because they're already given to us and 01:22:07.590 --> 01:22:08.779 align:start position:0% because they're already given to us and this<01:22:07.679> is<01:22:07.800> sort<01:22:07.949> of<01:22:08.039> building<01:22:08.340> down<01:22:08.519> to<01:22:08.670> this 01:22:08.779 --> 01:22:08.789 align:start position:0% this is sort of building down to this 01:22:08.789 --> 01:22:10.850 align:start position:0% this is sort of building down to this address<01:22:09.059> which<01:22:09.389> is<01:22:09.539> the<01:22:09.749> dress<01:22:09.929> of<01:22:10.079> care<01:22:10.559> of 01:22:10.850 --> 01:22:10.860 align:start position:0% address which is the dress of care of 01:22:10.860 --> 01:22:13.279 align:start position:0% address which is the dress of care of this<01:22:10.979> accounts<01:22:11.489> and<01:22:11.670> the<01:22:11.849> leaf<01:22:12.170> comes<01:22:13.170> where 01:22:13.279 --> 01:22:13.289 align:start position:0% this accounts and the leaf comes where 01:22:13.289 --> 01:22:15.799 align:start position:0% this accounts and the leaf comes where these<01:22:13.380> is<01:22:13.590> zero<01:22:14.099> zero<01:22:14.400> one<01:22:14.579> zero<01:22:14.610> zero<01:22:14.969> dot<01:22:15.780> dot 01:22:15.799 --> 01:22:15.809 align:start position:0% these is zero zero one zero zero dot dot 01:22:15.809 --> 01:22:19.279 align:start position:0% these is zero zero one zero zero dot dot one<01:22:15.989> and<01:22:16.920> then<01:22:17.130> we<01:22:17.309> have<01:22:17.340> an<01:22:17.579> edge<01:22:18.510> label<01:22:19.019> here 01:22:19.279 --> 01:22:19.289 align:start position:0% one and then we have an edge label here 01:22:19.289 --> 01:22:21.109 align:start position:0% one and then we have an edge label here with<01:22:19.709> the<01:22:19.829> rest<01:22:20.010> of<01:22:20.130> the<01:22:20.280> address<01:22:20.699> and<01:22:20.999> there's 01:22:21.109 --> 01:22:21.119 align:start position:0% with the rest of the address and there's 01:22:21.119 --> 01:22:23.089 align:start position:0% with the rest of the address and there's an<01:22:21.239> ellipses<01:22:21.599> that<01:22:21.659> didn't<01:22:22.079> render<01:22:22.260> it<01:22:22.440> here 01:22:23.089 --> 01:22:23.099 align:start position:0% an ellipses that didn't render it here 01:22:23.099 --> 01:22:25.339 align:start position:0% an ellipses that didn't render it here so<01:22:23.489> we<01:22:23.579> have<01:22:23.729> to<01:22:23.880> pass<01:22:24.510> call<01:22:24.749> data<01:22:24.929> with<01:22:25.170> no 01:22:25.339 --> 01:22:25.349 align:start position:0% so we have to pass call data with no 01:22:25.349 --> 01:22:26.839 align:start position:0% so we have to pass call data with no labels<01:22:25.769> which<01:22:25.860> is<01:22:26.010> so<01:22:26.190> tiny 01:22:26.839 --> 01:22:26.849 align:start position:0% labels which is so tiny 01:22:26.849 --> 01:22:28.459 align:start position:0% labels which is so tiny agile<01:22:27.329> Able's<01:22:27.659> which<01:22:27.809> is<01:22:27.929> still<01:22:28.139> small 01:22:28.459 --> 01:22:28.469 align:start position:0% agile Able's which is still small 01:22:28.469 --> 01:22:30.410 align:start position:0% agile Able's which is still small account<01:22:29.099> data<01:22:29.340> which<01:22:29.519> can<01:22:29.670> be<01:22:29.820> arbitrary<01:22:30.300> you 01:22:30.410 --> 01:22:30.420 align:start position:0% account data which can be arbitrary you 01:22:30.420 --> 01:22:32.810 align:start position:0% account data which can be arbitrary you can<01:22:30.570> have<01:22:30.719> balance<01:22:31.499> announce<01:22:31.800> whatever<01:22:32.280> no 01:22:32.810 --> 01:22:32.820 align:start position:0% can have balance announce whatever no 01:22:32.820 --> 01:22:36.799 align:start position:0% can have balance announce whatever no kidding<01:22:33.150> you<01:22:33.209> own<01:22:33.360> whatever<01:22:34.130> and<01:22:35.130> then<01:22:36.119> hashes 01:22:36.799 --> 01:22:36.809 align:start position:0% kidding you own whatever and then hashes 01:22:36.809 --> 01:22:40.009 align:start position:0% kidding you own whatever and then hashes and<01:22:36.840> these<01:22:37.079> hashes<01:22:37.320> are<01:22:37.590> h1<01:22:38.039> h2<01:22:38.780> all<01:22:39.780> these 01:22:40.009 --> 01:22:40.019 align:start position:0% and these hashes are h1 h2 all these 01:22:40.019 --> 01:22:41.239 align:start position:0% and these hashes are h1 h2 all these caches<01:22:40.289> these<01:22:40.440> dominate<01:22:40.829> these<01:22:40.979> aren't<01:22:41.130> like 01:22:41.239 --> 01:22:41.249 align:start position:0% caches these dominate these aren't like 01:22:41.249 --> 01:22:43.160 align:start position:0% caches these dominate these aren't like 80%<01:22:41.909> and<01:22:42.119> then<01:22:42.389> if<01:22:42.510> you<01:22:42.599> do<01:22:42.719> happen<01:22:42.929> to<01:22:43.079> have 01:22:43.160 --> 01:22:43.170 align:start position:0% 80% and then if you do happen to have 01:22:43.170 --> 01:22:45.620 align:start position:0% 80% and then if you do happen to have signatures<01:22:43.709> or<01:22:44.300> transactions<01:22:45.300> then<01:22:45.449> that's 01:22:45.620 --> 01:22:45.630 align:start position:0% signatures or transactions then that's 01:22:45.630 --> 01:22:48.620 align:start position:0% signatures or transactions then that's kind<01:22:45.989> of<01:22:46.139> big<01:22:46.289> to<01:22:46.530> the<01:22:47.400> count<01:22:47.670> data<01:22:47.909> you<01:22:48.539> know 01:22:48.620 --> 01:22:48.630 align:start position:0% kind of big to the count data you know 01:22:48.630 --> 01:22:50.020 align:start position:0% kind of big to the count data you know when<01:22:48.809> you<01:22:48.959> might<01:22:49.079> need<01:22:49.139> balance<01:22:49.559> of<01:22:49.650> nan<01:22:49.769> says 01:22:50.020 --> 01:22:50.030 align:start position:0% when you might need balance of nan says 01:22:50.030 --> 01:22:52.520 align:start position:0% when you might need balance of nan says well<01:22:51.030> the<01:22:51.090> trees<01:22:51.300> the<01:22:51.599> good<01:22:51.959> news<01:22:52.110> of<01:22:52.260> the<01:22:52.289> tree 01:22:52.520 --> 01:22:52.530 align:start position:0% well the trees the good news of the tree 01:22:52.530 --> 01:22:56.060 align:start position:0% well the trees the good news of the tree structure<01:22:52.769> we<01:22:52.979> can<01:22:53.099> get<01:22:53.249> less<01:22:53.909> than<01:22:54.059> 1%<01:22:55.070> and 01:22:56.060 --> 01:22:56.070 align:start position:0% structure we can get less than 1% and 01:22:56.070 --> 01:22:57.919 align:start position:0% structure we can get less than 1% and there's<01:22:56.519> there's<01:22:57.150> interactions<01:22:57.749> between 01:22:57.919 --> 01:22:57.929 align:start position:0% there's there's interactions between 01:22:57.929 --> 01:22:59.750 align:start position:0% there's there's interactions between these<01:22:58.170> and<01:22:58.650> another<01:22:59.249> thing<01:22:59.429> is<01:22:59.519> that<01:22:59.550> these 01:22:59.750 --> 01:22:59.760 align:start position:0% these and another thing is that these 01:22:59.760 --> 01:23:01.459 align:start position:0% these and another thing is that these duplication<01:23:00.420> so<01:23:00.659> the<01:23:00.749> binary<01:23:00.929> is<01:23:01.199> the<01:23:01.260> big 01:23:01.459 --> 01:23:01.469 align:start position:0% duplication so the binary is the big 01:23:01.469 --> 01:23:04.819 align:start position:0% duplication so the binary is the big thing<01:23:01.739> the<01:23:02.340> deduplication<01:23:02.909> I<01:23:03.090> found<01:23:03.329> that<01:23:03.829> 20% 01:23:04.819 --> 01:23:04.829 align:start position:0% thing the deduplication I found that 20% 01:23:04.829 --> 01:23:07.069 align:start position:0% thing the deduplication I found that 20% least<01:23:05.699> savings<01:23:06.179> so<01:23:06.329> we<01:23:06.360> don't<01:23:06.570> have<01:23:06.690> to<01:23:06.840> you 01:23:07.069 --> 01:23:07.079 align:start position:0% least savings so we don't have to you 01:23:07.079 --> 01:23:09.350 align:start position:0% least savings so we don't have to you know<01:23:07.110> certain<01:23:07.769> caches<01:23:08.130> if<01:23:08.880> we<01:23:09.030> just<01:23:09.179> had<01:23:09.329> one 01:23:09.350 --> 01:23:09.360 align:start position:0% know certain caches if we just had one 01:23:09.360 --> 01:23:11.089 align:start position:0% know certain caches if we just had one account<01:23:09.749> you<01:23:09.929> have<01:23:09.989> to<01:23:10.170> pass<01:23:10.409> all<01:23:10.590> the<01:23:10.709> hashes 01:23:11.089 --> 01:23:11.099 align:start position:0% account you have to pass all the hashes 01:23:11.099 --> 01:23:14.509 align:start position:0% account you have to pass all the hashes down<01:23:11.789> but<01:23:12.479> we<01:23:12.690> can<01:23:12.840> recompute<01:23:13.409> hashes<01:23:13.829> so<01:23:14.099> so 01:23:14.509 --> 01:23:14.519 align:start position:0% down but we can recompute hashes so so 01:23:14.519 --> 01:23:16.879 align:start position:0% down but we can recompute hashes so so we<01:23:14.610> can<01:23:14.760> compute<01:23:15.420> this<01:23:15.510> hash<01:23:15.719> or<01:23:16.019> in<01:23:16.499> this<01:23:16.679> hash 01:23:16.879 --> 01:23:16.889 align:start position:0% we can compute this hash or in this hash 01:23:16.889 --> 01:23:19.699 align:start position:0% we can compute this hash or in this hash so<01:23:17.159> we<01:23:17.280> don't<01:23:17.429> have<01:23:17.579> to<01:23:17.699> search<01:23:18.059> we<01:23:18.659> save<01:23:19.050> with 01:23:19.699 --> 01:23:19.709 align:start position:0% so we don't have to search we save with 01:23:19.709 --> 01:23:22.399 align:start position:0% so we don't have to search we save with deduplication<01:23:20.340> we<01:23:21.239> save<01:23:21.449> about<01:23:21.479> 20%<01:23:22.260> for 01:23:22.399 --> 01:23:22.409 align:start position:0% deduplication we save about 20% for 01:23:22.409 --> 01:23:23.839 align:start position:0% deduplication we save about 20% for significant<01:23:23.010> size<01:23:23.159> of<01:23:23.309> that<01:23:23.400> so<01:23:23.579> that's<01:23:23.670> what 01:23:23.839 --> 01:23:23.849 align:start position:0% significant size of that so that's what 01:23:23.849 --> 01:23:25.850 align:start position:0% significant size of that so that's what I<01:23:23.880> found<01:23:24.059> with<01:23:24.239> my<01:23:24.300> with<01:23:24.659> my<01:23:24.690> batch<01:23:24.959> works<01:23:25.199> so 01:23:25.850 --> 01:23:25.860 align:start position:0% I found with my with my batch works so 01:23:25.860 --> 01:23:27.410 align:start position:0% I found with my with my batch works so this<01:23:25.979> is<01:23:26.099> a<01:23:26.130> big<01:23:26.340> improvement<01:23:26.610> the<01:23:26.940> binary<01:23:27.300> is 01:23:27.410 --> 01:23:27.420 align:start position:0% this is a big improvement the binary is 01:23:27.420 --> 01:23:32.299 align:start position:0% this is a big improvement the binary is a<01:23:27.449> big<01:23:27.659> improvement<01:23:29.150> so<01:23:30.150> the<01:23:30.989> run<01:23:31.139> time<01:23:31.409> it 01:23:32.299 --> 01:23:32.309 align:start position:0% a big improvement so the run time it 01:23:32.309 --> 01:23:34.189 align:start position:0% a big improvement so the run time it will<01:23:32.429> sneak<01:23:32.639> about<01:23:32.849> now 01:23:34.189 --> 01:23:34.199 align:start position:0% will sneak about now 01:23:34.199 --> 01:23:37.370 align:start position:0% will sneak about now same<01:23:34.739> thing<01:23:35.010> for<01:23:35.579> million<01:23:36.420> accounts<01:23:36.959> 40 01:23:37.370 --> 01:23:37.380 align:start position:0% same thing for million accounts 40 01:23:37.380 --> 01:23:41.449 align:start position:0% same thing for million accounts 40 accounts<01:23:37.769> and<01:23:37.889> witness<01:23:39.380> 20<01:23:40.380> milliseconds<01:23:41.039> to 01:23:41.449 --> 01:23:41.459 align:start position:0% accounts and witness 20 milliseconds to 01:23:41.459 --> 01:23:43.879 align:start position:0% accounts and witness 20 milliseconds to so<01:23:41.699> do<01:23:41.849> it<01:23:41.880> but<01:23:42.510> it's<01:23:42.599> mostly<01:23:42.840> happy<01:23:43.110> and<01:23:43.439> we 01:23:43.879 --> 01:23:43.889 align:start position:0% so do it but it's mostly happy and we 01:23:43.889 --> 01:23:45.410 align:start position:0% so do it but it's mostly happy and we can<01:23:44.010> improve<01:23:44.130> hashing<01:23:44.670> as<01:23:44.789> well<01:23:44.969> so<01:23:45.150> I<01:23:45.179> think 01:23:45.410 --> 01:23:45.420 align:start position:0% can improve hashing as well so I think 01:23:45.420 --> 01:23:47.449 align:start position:0% can improve hashing as well so I think we<01:23:45.510> can<01:23:45.630> improve<01:23:45.900> this<01:23:46.079> run<01:23:46.289> time<01:23:46.499> so<01:23:47.070> we're 01:23:47.449 --> 01:23:47.459 align:start position:0% we can improve this run time so we're 01:23:47.459 --> 01:23:48.859 align:start position:0% we can improve this run time so we're going<01:23:47.579> to<01:23:47.639> be<01:23:47.699> dominated<01:23:48.269> this<01:23:48.449> is<01:23:48.570> just<01:23:48.719> other 01:23:48.859 --> 01:23:48.869 align:start position:0% going to be dominated this is just other 01:23:48.869 --> 01:23:50.179 align:start position:0% going to be dominated this is just other vertical<01:23:49.139> ization<01:23:49.349> not<01:23:49.769> to<01:23:49.860> speak<01:23:50.070> of 01:23:50.179 --> 01:23:50.189 align:start position:0% vertical ization not to speak of 01:23:50.189 --> 01:23:53.149 align:start position:0% vertical ization not to speak of signature<01:23:50.909> verification<01:23:51.269> and<01:23:52.070> that's<01:23:53.070> the 01:23:53.149 --> 01:23:53.159 align:start position:0% signature verification and that's the 01:23:53.159 --> 01:23:54.620 align:start position:0% signature verification and that's the other<01:23:53.249> bottom<01:23:53.550> like<01:23:53.639> we<01:23:53.670> can<01:23:53.939> improve<01:23:54.449> that 01:23:54.620 --> 01:23:54.630 align:start position:0% other bottom like we can improve that 01:23:54.630 --> 01:23:56.629 align:start position:0% other bottom like we can improve that too<01:23:54.959> so<01:23:55.499> I<01:23:55.530> guess<01:23:55.619> the<01:23:55.860> ball<01:23:56.010> might<01:23:56.159> be<01:23:56.189> 800 01:23:56.629 --> 01:23:56.639 align:start position:0% too so I guess the ball might be 800 01:23:56.639 --> 01:23:58.609 align:start position:0% too so I guess the ball might be 800 milliseconds<01:23:57.179> for<01:23:57.360> her<01:23:57.630> have<01:23:57.749> to<01:23:57.929> so<01:23:58.349> the<01:23:58.469> DAP 01:23:58.609 --> 01:23:58.619 align:start position:0% milliseconds for her have to so the DAP 01:23:58.619 --> 01:24:03.919 align:start position:0% milliseconds for her have to so the DAP developers<01:23:59.189> have<01:24:00.059> hope<01:24:00.800> here<01:24:01.800> that<01:24:02.729> that<01:24:03.479> this 01:24:03.919 --> 01:24:03.929 align:start position:0% developers have hope here that that this 01:24:03.929 --> 01:24:06.040 align:start position:0% developers have hope here that that this sort<01:24:04.170> of<01:24:04.199> tree<01:24:04.739> stuff<01:24:05.010> is<01:24:05.280> going<01:24:05.429> to<01:24:05.489> be 01:24:06.040 --> 01:24:06.050 align:start position:0% sort of tree stuff is going to be 01:24:06.050 --> 01:24:09.679 align:start position:0% sort of tree stuff is going to be marginal<01:24:07.050> trivial<01:24:07.530> almost<01:24:07.949> like<01:24:08.130> 1%<01:24:08.459> 1%<01:24:08.880> we're 01:24:09.679 --> 01:24:09.689 align:start position:0% marginal trivial almost like 1% 1% we're 01:24:09.689 --> 01:24:11.330 align:start position:0% marginal trivial almost like 1% 1% we're approaching<01:24:09.869> 0<01:24:10.289> that's<01:24:10.679> the<01:24:10.829> important<01:24:11.189> thing 01:24:11.330 --> 01:24:11.340 align:start position:0% approaching 0 that's the important thing 01:24:11.340 --> 01:24:14.149 align:start position:0% approaching 0 that's the important thing this<01:24:12.119> were<01:24:12.900> dominated<01:24:13.469> by<01:24:13.499> things<01:24:13.800> that<01:24:13.979> can 01:24:14.149 --> 01:24:14.159 align:start position:0% this were dominated by things that can 01:24:14.159 --> 01:24:16.009 align:start position:0% this were dominated by things that can be<01:24:14.309> improved<01:24:14.400> so<01:24:14.909> work<01:24:15.539> is<01:24:15.659> being<01:24:15.809> done<01:24:15.900> to 01:24:16.009 --> 01:24:16.019 align:start position:0% be improved so work is being done to 01:24:16.019 --> 01:24:18.669 align:start position:0% be improved so work is being done to improve<01:24:16.289> that<01:24:16.619> hashing<01:24:17.039> speed<01:24:17.309> group<01:24:17.579> the 01:24:18.669 --> 01:24:18.679 align:start position:0% improve that hashing speed group the 01:24:18.679 --> 01:24:21.319 align:start position:0% improve that hashing speed group the transaction<01:24:19.679> you<01:24:19.949> know<01:24:20.159> either<01:24:20.820> the<01:24:20.939> EC 01:24:21.319 --> 01:24:21.329 align:start position:0% transaction you know either the EC 01:24:21.329 --> 01:24:21.799 align:start position:0% transaction you know either the EC recover 01:24:21.799 --> 01:24:21.809 align:start position:0% recover 01:24:21.809 --> 01:24:25.459 align:start position:0% recover you<01:24:22.170> know<01:24:22.260> the<01:24:22.380> sake<01:24:22.889> curve<01:24:23.309> or<01:24:23.670> a<01:24:24.209> 2<01:24:24.900> 5<01:24:25.079> 5<01:24:25.229> 1<01:24:25.439> 9 01:24:25.459 --> 01:24:25.469 align:start position:0% you know the sake curve or a 2 5 5 1 9 01:24:25.469 --> 01:24:38.319 align:start position:0% you know the sake curve or a 2 5 5 1 9 is<01:24:25.709> another<01:24:25.920> option<01:24:26.219> which<01:24:26.340> has<01:24:26.369> some<01:24:26.939> more 01:24:38.319 --> 01:24:38.329 align:start position:0% 01:24:38.329 --> 01:24:43.370 align:start position:0% targets<01:24:40.130> so<01:24:41.420> what<01:24:42.420> was<01:24:42.510> written<01:24:42.630> here<01:24:42.959> is<01:24:43.110> that 01:24:43.370 --> 01:24:43.380 align:start position:0% targets so what was written here is that 01:24:43.380 --> 01:24:46.250 align:start position:0% targets so what was written here is that I<01:24:43.439> do<01:24:44.010> the<01:24:44.539> primary<01:24:45.539> wooden<01:24:45.780> post<01:24:46.050> group 01:24:46.250 --> 01:24:46.260 align:start position:0% I do the primary wooden post group 01:24:46.260 --> 01:24:48.500 align:start position:0% I do the primary wooden post group together<01:24:46.769> so<01:24:47.429> in<01:24:47.579> one<01:24:47.729> pass<01:24:47.969> so<01:24:48.179> I<01:24:48.239> sort<01:24:48.449> of 01:24:48.500 --> 01:24:48.510 align:start position:0% together so in one pass so I sort of 01:24:48.510 --> 01:24:50.989 align:start position:0% together so in one pass so I sort of merged<01:24:48.780> the<01:24:49.110> reversal<01:24:50.039> and<01:24:50.219> it's<01:24:50.610> and<01:24:50.880> it's 01:24:50.989 --> 01:24:50.999 align:start position:0% merged the reversal and it's and it's 01:24:50.999 --> 01:24:53.810 align:start position:0% merged the reversal and it's and it's made<01:24:51.239> like<01:24:51.449> that<01:24:51.599> you<01:24:51.749> saw<01:24:51.959> because<01:24:52.650> they<01:24:53.519> call 01:24:53.810 --> 01:24:53.820 align:start position:0% made like that you saw because they call 01:24:53.820 --> 01:24:56.330 align:start position:0% made like that you saw because they call the<01:24:53.909> ADA's<01:24:54.059> past<01:24:54.269> like<01:24:54.420> that<01:24:54.599> in<01:24:54.979> that<01:24:55.979> first 01:24:56.330 --> 01:24:56.340 align:start position:0% the ADA's past like that in that first 01:24:56.340 --> 01:24:58.129 align:start position:0% the ADA's past like that in that first pre<01:24:56.909> order<01:24:57.179> because<01:24:57.360> that's<01:24:57.539> how<01:24:57.659> we<01:24:57.719> traverse 01:24:58.129 --> 01:24:58.139 align:start position:0% pre order because that's how we traverse 01:24:58.139 --> 01:25:00.469 align:start position:0% pre order because that's how we traverse the<01:24:58.320> tree<01:24:58.409> so<01:24:58.590> the<01:24:58.709> the<01:24:59.159> the<01:24:59.189> way<01:24:59.639> past<01:24:59.969> the 01:25:00.469 --> 01:25:00.479 align:start position:0% the tree so the the the way past the 01:25:00.479 --> 01:25:01.969 align:start position:0% the tree so the the the way past the reason<01:25:00.630> it's<01:25:00.840> so<01:25:00.989> fast<01:25:01.229> at<01:25:01.409> run<01:25:01.590> time<01:25:01.619> their 01:25:01.969 --> 01:25:01.979 align:start position:0% reason it's so fast at run time their 01:25:01.979 --> 01:25:03.979 align:start position:0% reason it's so fast at run time their interaction<01:25:02.400> with<01:25:02.429> puzzle<01:25:02.909> all<01:25:03.090> run<01:25:03.840> today 01:25:03.979 --> 01:25:03.989 align:start position:0% interaction with puzzle all run today 01:25:03.989 --> 01:25:06.439 align:start position:0% interaction with puzzle all run today but<01:25:04.199> they're<01:25:04.409> both<01:25:04.559> sort<01:25:04.800> of<01:25:04.920> we<01:25:05.909> sort<01:25:06.119> of<01:25:06.209> read 01:25:06.439 --> 01:25:06.449 align:start position:0% but they're both sort of we sort of read 01:25:06.449 --> 01:25:07.879 align:start position:0% but they're both sort of we sort of read some<01:25:06.689> sort<01:25:06.869> of<01:25:06.900> optimal<01:25:07.289> point<01:25:07.590> where<01:25:07.769> you 01:25:07.879 --> 01:25:07.889 align:start position:0% some sort of optimal point where you 01:25:07.889 --> 01:25:10.580 align:start position:0% some sort of optimal point where you know<01:25:08.039> we<01:25:09.030> it's<01:25:09.269> perfect<01:25:09.630> for<01:25:09.659> both<01:25:09.900> this<01:25:10.409> is<01:25:10.469> a 01:25:10.580 --> 01:25:10.590 align:start position:0% know we it's perfect for both this is a 01:25:10.590 --> 01:25:14.410 align:start position:0% know we it's perfect for both this is a great<01:25:10.800> configuration<01:25:11.070> for<01:25:11.519> both<01:25:11.840> that 01:25:14.410 --> 01:25:14.420 align:start position:0% great configuration for both that 01:25:14.420 --> 01:25:17.540 align:start position:0% great configuration for both that trevor's<01:25:15.449> you<01:25:15.719> know<01:25:15.920> it's<01:25:16.920> like<01:25:17.039> outcodes 01:25:17.540 --> 01:25:17.550 align:start position:0% trevor's you know it's like outcodes 01:25:17.550 --> 01:25:18.709 align:start position:0% trevor's you know it's like outcodes it's<01:25:17.639> like<01:25:17.760> that<01:25:17.909> it's<01:25:18.209> similar<01:25:18.420> to<01:25:18.570> that 01:25:18.709 --> 01:25:18.719 align:start position:0% it's like that it's similar to that 01:25:18.719 --> 01:25:21.140 align:start position:0% it's like that it's similar to that model<01:25:19.320> but<01:25:19.439> I<01:25:19.499> call<01:25:20.070> them<01:25:20.249> no<01:25:20.369> labels<01:25:20.849> and<01:25:21.030> that 01:25:21.140 --> 01:25:21.150 align:start position:0% model but I call them no labels and that 01:25:21.150 --> 01:25:22.910 align:start position:0% model but I call them no labels and that app<01:25:21.389> codes<01:25:21.689> and<01:25:21.840> then<01:25:21.929> the<01:25:22.170> traversal<01:25:22.499> is<01:25:22.769> just 01:25:22.910 --> 01:25:22.920 align:start position:0% app codes and then the traversal is just 01:25:22.920 --> 01:25:24.859 align:start position:0% app codes and then the traversal is just a<01:25:23.010> recursive<01:25:23.429> call<01:25:23.459> here<01:25:23.939> and<01:25:24.150> then<01:25:24.570> later<01:25:24.809> on 01:25:24.859 --> 01:25:24.869 align:start position:0% a recursive call here and then later on 01:25:24.869 --> 01:25:26.959 align:start position:0% a recursive call here and then later on once<01:25:25.199> we<01:25:25.349> return<01:25:25.769> the<01:25:25.889> hash<01:25:26.070> to<01:25:26.219> here<01:25:26.459> we<01:25:26.820> do<01:25:26.939> a 01:25:26.959 --> 01:25:26.969 align:start position:0% once we return the hash to here we do a 01:25:26.969 --> 01:25:28.310 align:start position:0% once we return the hash to here we do a recursive<01:25:27.449> call<01:25:27.479> here<01:25:27.780> or<01:25:27.900> if<01:25:27.989> this<01:25:28.110> was<01:25:28.170> a 01:25:28.310 --> 01:25:28.320 align:start position:0% recursive call here or if this was a 01:25:28.320 --> 01:25:30.199 align:start position:0% recursive call here or if this was a happy<01:25:28.469> to<01:25:28.679> just<01:25:28.829> grab<01:25:29.039> the<01:25:29.219> cash<01:25:29.369> and<01:25:29.639> we<01:25:30.090> know 01:25:30.199 --> 01:25:30.209 align:start position:0% happy to just grab the cash and we know 01:25:30.209 --> 01:25:31.819 align:start position:0% happy to just grab the cash and we know what<01:25:30.389> to<01:25:30.479> do<01:25:30.719> here<01:25:31.079> because<01:25:31.199> we<01:25:31.469> have<01:25:31.559> the<01:25:31.590> one 01:25:31.819 --> 01:25:31.829 align:start position:0% what to do here because we have the one 01:25:31.829 --> 01:25:34.279 align:start position:0% what to do here because we have the one one<01:25:32.039> so<01:25:32.849> we<01:25:32.939> know<01:25:33.059> two<01:25:33.269> recursive<01:25:33.510> recursive 01:25:34.279 --> 01:25:34.289 align:start position:0% one so we know two recursive recursive 01:25:34.289 --> 01:25:36.229 align:start position:0% one so we know two recursive recursive left<01:25:34.530> and<01:25:34.709> right<01:25:34.829> but<01:25:35.070> if<01:25:35.159> those<01:25:35.249> a<01:25:35.519> 1-0<01:25:36.059> lead 01:25:36.229 --> 01:25:36.239 align:start position:0% left and right but if those a 1-0 lead 01:25:36.239 --> 01:25:37.699 align:start position:0% left and right but if those a 1-0 lead recurse<01:25:36.630> left<01:25:36.900> and<01:25:37.079> then<01:25:37.170> when<01:25:37.289> that<01:25:37.409> returns 01:25:37.699 --> 01:25:37.709 align:start position:0% recurse left and then when that returns 01:25:37.709 --> 01:25:39.020 align:start position:0% recurse left and then when that returns we<01:25:37.889> just<01:25:38.070> grab<01:25:38.309> the<01:25:38.429> hashing<01:25:38.729> than<01:25:38.820> we<01:25:38.909> catch 01:25:39.020 --> 01:25:39.030 align:start position:0% we just grab the hashing than we catch 01:25:39.030 --> 01:25:41.120 align:start position:0% we just grab the hashing than we catch up<01:25:39.260> there's<01:25:40.260> a<01:25:40.349> bunch<01:25:40.530> of<01:25:40.590> other<01:25:40.739> options<01:25:40.800> I'm 01:25:41.120 --> 01:25:41.130 align:start position:0% up there's a bunch of other options I'm 01:25:41.130 --> 01:25:42.439 align:start position:0% up there's a bunch of other options I'm using<01:25:41.280> C<01:25:41.550> so<01:25:41.699> I'm<01:25:41.760> using<01:25:41.999> pointers<01:25:42.360> I'm 01:25:42.439 --> 01:25:42.449 align:start position:0% using C so I'm using pointers I'm 01:25:42.449 --> 01:25:44.810 align:start position:0% using C so I'm using pointers I'm creating<01:25:42.809> a<01:25:42.869> stack<01:25:43.139> as<01:25:43.949> I<01:25:44.159> Trevor<01:25:44.400> so<01:25:44.729> I'm 01:25:44.810 --> 01:25:44.820 align:start position:0% creating a stack as I Trevor so I'm 01:25:44.820 --> 01:25:45.570 align:start position:0% creating a stack as I Trevor so I'm putting<01:25:45.209> that 01:25:45.570 --> 01:25:45.580 align:start position:0% putting that 01:25:45.580 --> 01:25:46.830 align:start position:0% putting that the<01:25:45.700> roots<01:25:45.850> of<01:25:45.970> the<01:25:46.060> hash<01:25:46.210> that<01:25:46.420> I<01:25:46.450> returned 01:25:46.830 --> 01:25:46.840 align:start position:0% the roots of the hash that I returned 01:25:46.840 --> 01:25:48.600 align:start position:0% the roots of the hash that I returned here<01:25:47.200> exactly<01:25:47.860> where<01:25:48.100> I'm<01:25:48.190> going<01:25:48.370> to<01:25:48.430> hash 01:25:48.600 --> 01:25:48.610 align:start position:0% here exactly where I'm going to hash 01:25:48.610 --> 01:25:50.040 align:start position:0% here exactly where I'm going to hash here<01:25:48.880> and<01:25:49.090> then<01:25:49.180> the<01:25:49.270> hash<01:25:49.390> I<01:25:49.540> returned<01:25:49.810> here 01:25:50.040 --> 01:25:50.050 align:start position:0% here and then the hash I returned here 01:25:50.050 --> 01:25:51.900 align:start position:0% here and then the hash I returned here exactly<01:25:50.620> where<01:25:50.920> I<01:25:50.980> needed<01:25:51.220> to<01:25:51.340> hash<01:25:51.550> here<01:25:51.760> so 01:25:51.900 --> 01:25:51.910 align:start position:0% exactly where I needed to hash here so 01:25:51.910 --> 01:25:53.400 align:start position:0% exactly where I needed to hash here so there's<01:25:52.090> minimize<01:25:52.510> amount<01:25:52.780> of<01:25:52.840> copies<01:25:53.110> all 01:25:53.400 --> 01:25:53.410 align:start position:0% there's minimize amount of copies all 01:25:53.410 --> 01:25:54.180 align:start position:0% there's minimize amount of copies all these<01:25:53.590> little<01:25:53.770> things<01:25:54.070> these 01:25:54.180 --> 01:25:54.190 align:start position:0% these little things these 01:25:54.190 --> 01:25:56.400 align:start position:0% these little things these microcontroller<01:25:54.970> people<01:25:55.300> is<01:25:55.570> about<01:25:56.050> it<01:25:56.140> some 01:25:56.400 --> 01:25:56.410 align:start position:0% microcontroller people is about it some 01:25:56.410 --> 01:25:57.900 align:start position:0% microcontroller people is about it some people<01:25:56.440> know<01:25:56.800> these<01:25:56.980> stuff<01:25:57.190> these<01:25:57.640> sort<01:25:57.850> of 01:25:57.900 --> 01:25:57.910 align:start position:0% people know these stuff these sort of 01:25:57.910 --> 01:26:00.600 align:start position:0% people know these stuff these sort of tricks<01:25:58.180> where<01:25:58.360> you<01:25:58.450> sort<01:25:58.690> of<01:25:59.370> minimize<01:26:00.370> mem 01:26:00.600 --> 01:26:00.610 align:start position:0% tricks where you sort of minimize mem 01:26:00.610 --> 01:26:02.130 align:start position:0% tricks where you sort of minimize mem copy<01:26:00.820> all<01:26:01.030> these<01:26:01.180> things<01:26:01.420> are<01:26:01.540> important<01:26:01.990> know 01:26:02.130 --> 01:26:02.140 align:start position:0% copy all these things are important know 01:26:02.140 --> 01:26:04.770 align:start position:0% copy all these things are important know without<01:26:02.920> -<01:26:03.130> because<01:26:03.460> speed<01:26:03.940> they<01:26:04.480> weren't 01:26:04.770 --> 01:26:04.780 align:start position:0% without - because speed they weren't 01:26:04.780 --> 01:26:06.630 align:start position:0% without - because speed they weren't desperate<01:26:05.050> for<01:26:05.530> you<01:26:05.770> know<01:26:05.890> run<01:26:06.160> time<01:26:06.370> and 01:26:06.630 --> 01:26:06.640 align:start position:0% desperate for you know run time and 01:26:06.640 --> 01:26:07.920 align:start position:0% desperate for you know run time and we're<01:26:06.760> desperate<01:26:06.910> for<01:26:07.120> call<01:26:07.480> data<01:26:07.720> so 01:26:07.920 --> 01:26:07.930 align:start position:0% we're desperate for call data so 01:26:07.930 --> 01:26:10.110 align:start position:0% we're desperate for call data so everything<01:26:08.260> has<01:26:08.410> to<01:26:08.440> be<01:26:08.590> perfect<01:26:08.980> for<01:26:09.880> the<01:26:09.970> dab 01:26:10.110 --> 01:26:10.120 align:start position:0% everything has to be perfect for the dab 01:26:10.120 --> 01:26:13.140 align:start position:0% everything has to be perfect for the dab developers<01:26:11.310> so<01:26:12.310> I<01:26:12.340> pretty<01:26:12.610> much<01:26:12.790> called<01:26:13.090> a 01:26:13.140 --> 01:26:13.150 align:start position:0% developers so I pretty much called a 01:26:13.150 --> 01:26:15.210 align:start position:0% developers so I pretty much called a traversal<01:26:13.840> order<01:26:14.110> merkel<01:26:14.470> ice-free<01:26:14.800> wood<01:26:15.010> in 01:26:15.210 --> 01:26:15.220 align:start position:0% traversal order merkel ice-free wood in 01:26:15.220 --> 01:26:17.550 align:start position:0% traversal order merkel ice-free wood in the<01:26:15.280> same<01:26:15.520> way<01:26:15.850> mem<01:26:16.120> copy<01:26:16.360> so<01:26:17.080> I<01:26:17.110> mentioned 01:26:17.550 --> 01:26:17.560 align:start position:0% the same way mem copy so I mentioned 01:26:17.560 --> 01:26:18.900 align:start position:0% the same way mem copy so I mentioned that<01:26:17.740> stack<01:26:18.070> there<01:26:18.280> are<01:26:18.370> a<01:26:18.400> few<01:26:18.490> other<01:26:18.640> things 01:26:18.900 --> 01:26:18.910 align:start position:0% that stack there are a few other things 01:26:18.910 --> 01:26:20.430 align:start position:0% that stack there are a few other things I'm<01:26:19.030> not<01:26:19.120> I'm<01:26:19.540> just<01:26:19.720> giving<01:26:19.900> you<01:26:19.930> a<01:26:20.050> high-level 01:26:20.430 --> 01:26:20.440 align:start position:0% I'm not I'm just giving you a high-level 01:26:20.440 --> 01:26:22.410 align:start position:0% I'm not I'm just giving you a high-level overview<01:26:20.800> there<01:26:21.280> are<01:26:21.310> details<01:26:21.820> that<01:26:21.910> well 01:26:22.410 --> 01:26:22.420 align:start position:0% overview there are details that well 01:26:22.420 --> 01:26:25.110 align:start position:0% overview there are details that well this<01:26:22.990> is<01:26:23.140> like<01:26:23.320> look<01:26:23.620> easy<01:26:23.860> part<01:26:24.220> but<01:26:24.250> there 01:26:25.110 --> 01:26:25.120 align:start position:0% this is like look easy part but there 01:26:25.120 --> 01:26:27.030 align:start position:0% this is like look easy part but there are<01:26:25.180> some<01:26:25.330> details<01:26:25.690> that<01:26:25.990> I<01:26:26.230> spent<01:26:26.800> a<01:26:26.860> lot<01:26:26.980> of 01:26:27.030 --> 01:26:27.040 align:start position:0% are some details that I spent a lot of 01:26:27.040 --> 01:26:30.660 align:start position:0% are some details that I spent a lot of time<01:26:27.250> on<01:26:27.840> so<01:26:28.840> I<01:26:29.140> already<01:26:29.500> have<01:26:29.800> it<01:26:30.040> says<01:26:30.340> next 01:26:30.660 --> 01:26:30.670 align:start position:0% time on so I already have it says next 01:26:30.670 --> 01:26:33.270 align:start position:0% time on so I already have it says next here<01:26:31.120> adaptive<01:26:31.570> hatchling<01:26:32.050> so<01:26:32.140> why<01:26:32.290> 256-bit 01:26:33.270 --> 01:26:33.280 align:start position:0% here adaptive hatchling so why 256-bit 01:26:33.280 --> 01:26:36.540 align:start position:0% here adaptive hatchling so why 256-bit is<01:26:33.580> is<01:26:34.480> that<01:26:34.720> a<01:26:34.930> requirement<01:26:35.740> for<01:26:35.890> everybody 01:26:36.540 --> 01:26:36.550 align:start position:0% is is that a requirement for everybody 01:26:36.550 --> 01:26:38.250 align:start position:0% is is that a requirement for everybody nobody's<01:26:37.090> broken<01:26:37.450> hundreds<01:26:37.960> a<01:26:38.050> lot<01:26:38.200> of 01:26:38.250 --> 01:26:38.260 align:start position:0% nobody's broken hundreds a lot of 01:26:38.260 --> 01:26:39.240 align:start position:0% nobody's broken hundreds a lot of hundred<01:26:38.500> six<01:26:38.680> I<01:26:38.770> don't<01:26:38.890> think<01:26:39.010> that<01:26:39.100> I<01:26:39.190> need 01:26:39.240 --> 01:26:39.250 align:start position:0% hundred six I don't think that I need 01:26:39.250 --> 01:26:41.250 align:start position:0% hundred six I don't think that I need significant<01:26:40.030> you<01:26:40.210> know<01:26:40.330> good<01:26:40.720> hundred<01:26:40.930> sixty 01:26:41.250 --> 01:26:41.260 align:start position:0% significant you know good hundred sixty 01:26:41.260 --> 01:26:42.990 align:start position:0% significant you know good hundred sixty bit<01:26:41.410> caches<01:26:42.160> with<01:26:42.280> a<01:26:42.310> broken<01:26:42.610> and<01:26:42.730> let's<01:26:42.850> say 01:26:42.990 --> 01:26:43.000 align:start position:0% bit caches with a broken and let's say 01:26:43.000 --> 01:26:43.770 align:start position:0% bit caches with a broken and let's say it<01:26:43.090> is<01:26:43.210> broken 01:26:43.770 --> 01:26:43.780 align:start position:0% it is broken 01:26:43.780 --> 01:26:46.170 align:start position:0% it is broken I'll<01:26:43.990> save<01:26:44.230> link<01:26:44.440> to<01:26:44.620> these<01:26:44.800> 160-bit<01:26:45.700> hash<01:26:45.790> is 01:26:46.170 --> 01:26:46.180 align:start position:0% I'll save link to these 160-bit hash is 01:26:46.180 --> 01:26:48.420 align:start position:0% I'll save link to these 160-bit hash is broken<01:26:46.540> but<01:26:47.170> if<01:26:47.290> we<01:26:47.410> have<01:26:47.530> adapted<01:26:47.740> but<01:26:48.280> that 01:26:48.420 --> 01:26:48.430 align:start position:0% broken but if we have adapted but that 01:26:48.430 --> 01:26:50.160 align:start position:0% broken but if we have adapted but that detached<01:26:48.790> is<01:26:48.940> where<01:26:49.090> we<01:26:49.210> remark<01:26:49.630> lies<01:26:49.870> with 01:26:50.160 --> 01:26:50.170 align:start position:0% detached is where we remark lies with 01:26:50.170 --> 01:26:52.590 align:start position:0% detached is where we remark lies with you<01:26:50.500> know<01:26:50.620> hundred<01:26:50.950> seventy<01:26:51.280> six<01:26:51.460> bit<01:26:51.760> you 01:26:52.590 --> 01:26:52.600 align:start position:0% you know hundred seventy six bit you 01:26:52.600 --> 01:26:54.870 align:start position:0% you know hundred seventy six bit you know<01:26:52.720> if<01:26:52.900> you<01:26:53.020> submit<01:26:53.320> a<01:26:53.350> proof<01:26:53.620> of<01:26:53.880> collision 01:26:54.870 --> 01:26:54.880 align:start position:0% know if you submit a proof of collision 01:26:54.880 --> 01:26:56.700 align:start position:0% know if you submit a proof of collision then<01:26:55.210> we<01:26:55.360> can<01:26:55.540> you<01:26:55.780> know<01:26:55.870> reverb<01:26:56.200> lies<01:26:56.440> on 01:26:56.700 --> 01:26:56.710 align:start position:0% then we can you know reverb lies on 01:26:56.710 --> 01:26:58.740 align:start position:0% then we can you know reverb lies on chain<01:26:57.010> and<01:26:57.850> then<01:26:57.940> we<01:26:58.090> can<01:26:58.210> bill<01:26:58.360> for<01:26:58.390> another 01:26:58.740 --> 01:26:58.750 align:start position:0% chain and then we can bill for another 01:26:58.750 --> 01:27:01.050 align:start position:0% chain and then we can bill for another ten<01:26:58.990> years<01:26:59.310> so<01:27:00.310> that<01:27:00.460> only<01:27:00.550> proof<01:27:00.850> things 01:27:01.050 --> 01:27:01.060 align:start position:0% ten years so that only proof things 01:27:01.060 --> 01:27:03.540 align:start position:0% ten years so that only proof things alive<01:27:01.870> by<01:27:02.050> thirty<01:27:02.500> you<01:27:02.590> know<01:27:02.620> 32<01:27:03.040> bytes<01:27:03.250> versus 01:27:03.540 --> 01:27:03.550 align:start position:0% alive by thirty you know 32 bytes versus 01:27:03.550 --> 01:27:05.160 align:start position:0% alive by thirty you know 32 bytes versus twenty<01:27:03.790> bytes<01:27:03.970> that's<01:27:04.090> like<01:27:04.300> that<01:27:04.420> what<01:27:04.720> like 01:27:05.160 --> 01:27:05.170 align:start position:0% twenty bytes that's like that what like 01:27:05.170 --> 01:27:06.270 align:start position:0% twenty bytes that's like that what like you<01:27:05.560> know<01:27:05.680> thirty<01:27:05.980> three<01:27:06.160> percent 01:27:06.270 --> 01:27:06.280 align:start position:0% you know thirty three percent 01:27:06.280 --> 01:27:08.250 align:start position:0% you know thirty three percent improvement<01:27:07.000> in<01:27:07.330> the<01:27:07.390> call<01:27:07.600> data<01:27:07.780> so<01:27:08.170> all 01:27:08.250 --> 01:27:08.260 align:start position:0% improvement in the call data so all 01:27:08.260 --> 01:27:09.360 align:start position:0% improvement in the call data so all these<01:27:08.380> things<01:27:08.590> you<01:27:08.860> know<01:27:08.950> this<01:27:09.100> thirty 01:27:09.360 --> 01:27:09.370 align:start position:0% these things you know this thirty 01:27:09.370 --> 01:27:10.590 align:start position:0% these things you know this thirty percent<01:27:09.700> that's<01:27:09.880> twenty<01:27:10.150> percent<01:27:10.480> of<01:27:10.570> all 01:27:10.590 --> 01:27:10.600 align:start position:0% percent that's twenty percent of all 01:27:10.600 --> 01:27:12.510 align:start position:0% percent that's twenty percent of all this<01:27:10.780> stuff<01:27:11.020> adds<01:27:11.260> up<01:27:11.470> another<01:27:12.310> one<01:27:12.460> is 01:27:12.510 --> 01:27:12.520 align:start position:0% this stuff adds up another one is 01:27:12.520 --> 01:27:14.640 align:start position:0% this stuff adds up another one is caching<01:27:13.000> breast<01:27:13.570> who<01:27:13.690> there's<01:27:13.870> a<01:27:13.930> proposal<01:27:14.290> to 01:27:14.640 --> 01:27:14.650 align:start position:0% caching breast who there's a proposal to 01:27:14.650 --> 01:27:17.130 align:start position:0% caching breast who there's a proposal to store<01:27:15.580> it<01:27:15.700> alexey<01:27:16.240> taught<01:27:16.510> us<01:27:16.660> he<01:27:16.840> had<01:27:16.930> some 01:27:17.130 --> 01:27:17.140 align:start position:0% store it alexey taught us he had some 01:27:17.140 --> 01:27:18.780 align:start position:0% store it alexey taught us he had some blog<01:27:17.350> post<01:27:17.620> that<01:27:17.710> if<01:27:17.890> you<01:27:17.980> passed<01:27:18.250> the<01:27:18.430> recent 01:27:18.780 --> 01:27:18.790 align:start position:0% blog post that if you passed the recent 01:27:18.790 --> 01:27:22.080 align:start position:0% blog post that if you passed the recent you<01:27:19.600> cache<01:27:19.870> so<01:27:20.800> you<01:27:20.920> maintain<01:27:21.430> the<01:27:21.760> recent 01:27:22.080 --> 01:27:22.090 align:start position:0% you cache so you maintain the recent 01:27:22.090 --> 01:27:24.630 align:start position:0% you cache so you maintain the recent hashes<01:27:22.480> that<01:27:22.630> were<01:27:22.720> used<01:27:23.130> and<01:27:24.130> you<01:27:24.310> can<01:27:24.460> sort 01:27:24.630 --> 01:27:24.640 align:start position:0% hashes that were used and you can sort 01:27:24.640 --> 01:27:27.270 align:start position:0% hashes that were used and you can sort of<01:27:24.700> reuse<01:27:25.570> those<01:27:25.840> and<01:27:26.200> you<01:27:26.530> know<01:27:26.650> it'll<01:27:27.040> save 01:27:27.270 --> 01:27:27.280 align:start position:0% of reuse those and you know it'll save 01:27:27.280 --> 01:27:29.070 align:start position:0% of reuse those and you know it'll save as<01:27:27.670> well<01:27:27.880> as<01:27:28.000> little<01:27:28.210> it'll<01:27:28.540> increase<01:27:28.810> you 01:27:29.070 --> 01:27:29.080 align:start position:0% as well as little it'll increase you 01:27:29.080 --> 01:27:30.000 align:start position:0% as well as little it'll increase you know<01:27:29.170> there'll<01:27:29.410> be<01:27:29.470> a<01:27:29.560> worst<01:27:29.770> case<01:27:29.860> scenario 01:27:30.000 --> 01:27:30.010 align:start position:0% know there'll be a worst case scenario 01:27:30.010 --> 01:27:31.009 align:start position:0% know there'll be a worst case scenario but<01:27:30.520> if 01:27:31.009 --> 01:27:31.019 align:start position:0% but if 01:27:31.019 --> 01:27:33.649 align:start position:0% but if if<01:27:31.709> the<01:27:31.859> cash<01:27:32.069> has<01:27:32.699> a<01:27:32.760> lot<01:27:32.939> of<01:27:32.969> fascism<01:27:33.359> they 01:27:33.649 --> 01:27:33.659 align:start position:0% if the cash has a lot of fascism they 01:27:33.659 --> 01:27:36.349 align:start position:0% if the cash has a lot of fascism they were<01:27:33.719> used<01:27:33.929> a<01:27:34.079> lot<01:27:34.229> then<01:27:34.669> we'll<01:27:35.669> have<01:27:35.879> you<01:27:36.269> know 01:27:36.349 --> 01:27:36.359 align:start position:0% were used a lot then we'll have you know 01:27:36.359 --> 01:27:37.819 align:start position:0% were used a lot then we'll have you know this<01:27:36.569> will<01:27:36.719> change<01:27:36.899> there'll<01:27:37.229> be<01:27:37.260> a<01:27:37.379> lot<01:27:37.799> more 01:27:37.819 --> 01:27:37.829 align:start position:0% this will change there'll be a lot more 01:27:37.829 --> 01:27:40.219 align:start position:0% this will change there'll be a lot more cities<01:27:38.219> remaining<01:27:38.519> transactions<01:27:39.059> and<01:27:40.049> what 01:27:40.219 --> 01:27:40.229 align:start position:0% cities remaining transactions and what 01:27:40.229 --> 01:27:41.689 align:start position:0% cities remaining transactions and what else<01:27:40.349> did<01:27:40.469> I<01:27:40.559> want<01:27:40.769> to<01:27:40.799> say<01:27:40.859> they<01:27:41.189> inserted<01:27:41.489> two 01:27:41.689 --> 01:27:41.699 align:start position:0% else did I want to say they inserted two 01:27:41.699 --> 01:27:43.219 align:start position:0% else did I want to say they inserted two leaders<01:27:41.939> written<01:27:42.179> it's<01:27:42.419> writing<01:27:42.629> the<01:27:42.839> test 01:27:43.219 --> 01:27:43.229 align:start position:0% leaders written it's writing the test 01:27:43.229 --> 01:27:44.479 align:start position:0% leaders written it's writing the test generation<01:27:43.589> isn't<01:27:43.949> ready<01:27:44.099> yet 01:27:44.479 --> 01:27:44.489 align:start position:0% generation isn't ready yet 01:27:44.489 --> 01:27:48.079 align:start position:0% generation isn't ready yet so<01:27:44.760> how<01:27:45.359> does<01:27:45.419> insert<01:27:45.809> and<01:27:46.289> remove<01:27:47.099> happen 01:27:48.079 --> 01:27:48.089 align:start position:0% so how does insert and remove happen 01:27:48.089 --> 01:27:50.509 align:start position:0% so how does insert and remove happen what<01:27:48.479> we<01:27:48.599> we<01:27:49.349> find<01:27:49.559> the<01:27:49.709> neighbors<01:27:50.069> we<01:27:50.309> find 01:27:50.509 --> 01:27:50.519 align:start position:0% what we we find the neighbors we find 01:27:50.519 --> 01:27:52.039 align:start position:0% what we we find the neighbors we find this<01:27:50.729> let's<01:27:51.179> say<01:27:51.329> I<01:27:51.389> want<01:27:51.569> to<01:27:51.599> insert<01:27:51.869> a 01:27:52.039 --> 01:27:52.049 align:start position:0% this let's say I want to insert a 01:27:52.049 --> 01:27:53.989 align:start position:0% this let's say I want to insert a neighbor<01:27:52.229> to<01:27:52.499> this<01:27:52.619> one<01:27:53.069> which<01:27:53.309> whose<01:27:53.819> address 01:27:53.989 --> 01:27:53.999 align:start position:0% neighbor to this one which whose address 01:27:53.999 --> 01:27:55.579 align:start position:0% neighbor to this one which whose address is<01:27:54.089> zero<01:27:54.329> zero<01:27:54.539> one<01:27:54.719> zero<01:27:54.749> zero<01:27:55.049> Levitt<01:27:55.439> that 01:27:55.579 --> 01:27:55.589 align:start position:0% is zero zero one zero zero Levitt that 01:27:55.589 --> 01:27:57.889 align:start position:0% is zero zero one zero zero Levitt that one<01:27:55.799> one<01:27:56.339> zero<01:27:56.789> one<01:27:56.909> one<01:27:57.179> zero<01:27:57.239> definite<01:27:57.749> that 01:27:57.889 --> 01:27:57.899 align:start position:0% one one zero one one zero definite that 01:27:57.899 --> 01:28:01.549 align:start position:0% one one zero one one zero definite that one<01:27:58.049> zero<01:27:58.319> that's<01:27:58.919> this<01:28:00.019> this<01:28:01.019> sort<01:28:01.260> of<01:28:01.319> cut 01:28:01.549 --> 01:28:01.559 align:start position:0% one zero that's this this sort of cut 01:28:01.559 --> 01:28:07.099 align:start position:0% one zero that's this this sort of cut soft<01:28:04.939> place<01:28:05.939> is<01:28:06.089> growing<01:28:06.299> so<01:28:06.599> it's<01:28:06.749> the<01:28:06.929> full 01:28:07.099 --> 01:28:07.109 align:start position:0% soft place is growing so it's the full 01:28:07.109 --> 01:28:09.319 align:start position:0% soft place is growing so it's the full thing<01:28:07.260> yeah<01:28:08.039> that's<01:28:08.309> the<01:28:08.399> whole<01:28:08.549> thing 01:28:09.319 --> 01:28:09.329 align:start position:0% thing yeah that's the whole thing 01:28:09.329 --> 01:28:13.459 align:start position:0% thing yeah that's the whole thing so<01:28:10.049> we<01:28:10.489> instantiate<01:28:11.489> a<01:28:11.789> tree<01:28:12.119> as<01:28:12.959> you<01:28:13.379> know 01:28:13.459 --> 01:28:13.469 align:start position:0% so we instantiate a tree as you know 01:28:13.469 --> 01:28:15.829 align:start position:0% so we instantiate a tree as you know pointers<01:28:14.339> to<01:28:14.579> the<01:28:14.699> children<01:28:15.089> but<01:28:15.239> we<01:28:15.389> know<01:28:15.569> we 01:28:15.829 --> 01:28:15.839 align:start position:0% pointers to the children but we know we 01:28:15.839 --> 01:28:17.059 align:start position:0% pointers to the children but we know we pass<01:28:16.019> this<01:28:16.139> call<01:28:16.349> data<01:28:16.499> to<01:28:16.679> solve<01:28:16.859> done 01:28:17.059 --> 01:28:17.069 align:start position:0% pass this call data to solve done 01:28:17.069 --> 01:28:18.469 align:start position:0% pass this call data to solve done already<01:28:17.279> I<01:28:17.399> just<01:28:17.459> beat<01:28:17.729> us<01:28:17.879> Confederation 01:28:18.469 --> 01:28:18.479 align:start position:0% already I just beat us Confederation 01:28:18.479 --> 01:28:22.669 align:start position:0% already I just beat us Confederation that<01:28:19.669> we<01:28:20.669> instantiate<01:28:20.999> them<01:28:21.419> note<01:28:21.629> here<01:28:21.959> and 01:28:22.669 --> 01:28:22.679 align:start position:0% that we instantiate them note here and 01:28:22.679 --> 01:28:24.019 align:start position:0% that we instantiate them note here and then<01:28:22.829> we<01:28:22.919> have<01:28:23.039> left<01:28:23.279> pointer<01:28:23.669> to<01:28:23.789> the<01:28:23.879> hash 01:28:24.019 --> 01:28:24.029 align:start position:0% then we have left pointer to the hash 01:28:24.029 --> 01:28:26.389 align:start position:0% then we have left pointer to the hash white<01:28:24.389> pointer<01:28:24.779> to<01:28:24.929> this<01:28:25.049> and<01:28:25.409> then<01:28:25.649> we<01:28:26.069> insert 01:28:26.389 --> 01:28:26.399 align:start position:0% white pointer to this and then we insert 01:28:26.399 --> 01:28:28.429 align:start position:0% white pointer to this and then we insert by<01:28:26.609> you<01:28:26.669> know<01:28:26.909> taking<01:28:27.119> the<01:28:27.449> right<01:28:27.989> pointers<01:28:28.319> we 01:28:28.429 --> 01:28:28.439 align:start position:0% by you know taking the right pointers we 01:28:28.439 --> 01:28:30.079 align:start position:0% by you know taking the right pointers we you<01:28:28.829> know<01:28:28.919> this<01:28:29.039> this<01:28:29.399> tree<01:28:29.549> structure<01:28:29.849> we 01:28:30.079 --> 01:28:30.089 align:start position:0% you know this this tree structure we 01:28:30.089 --> 01:28:32.239 align:start position:0% you know this this tree structure we have<01:28:30.239> pointers<01:28:30.569> about<01:28:30.839> the<01:28:31.079> right<01:28:31.229> mouth<01:28:31.439> we 01:28:32.239 --> 01:28:32.249 align:start position:0% have pointers about the right mouth we 01:28:32.249 --> 01:28:35.839 align:start position:0% have pointers about the right mouth we we<01:28:32.549> do<01:28:32.699> some<01:28:32.879> bit<01:28:33.689> twiddling<01:28:33.899> to<01:28:34.729> change<01:28:35.729> the 01:28:35.839 --> 01:28:35.849 align:start position:0% we do some bit twiddling to change the 01:28:35.849 --> 01:28:41.899 align:start position:0% we do some bit twiddling to change the snow<01:28:36.029> label<01:28:36.419> or<01:28:36.479> whatever<01:28:39.199> and<01:28:40.429> we<01:28:41.429> insert<01:28:41.789> the 01:28:41.899 --> 01:28:41.909 align:start position:0% snow label or whatever and we insert the 01:28:41.909 --> 01:28:43.489 align:start position:0% snow label or whatever and we insert the node<01:28:42.059> so<01:28:42.329> it's<01:28:42.479> and<01:28:42.689> then<01:28:42.809> when<01:28:43.079> we<01:28:43.169> merkel 01:28:43.489 --> 01:28:43.499 align:start position:0% node so it's and then when we merkel 01:28:43.499 --> 01:28:45.109 align:start position:0% node so it's and then when we merkel eyes<01:28:43.559> we<01:28:43.769> do<01:28:43.889> we<01:28:44.129> sort<01:28:44.369> of<01:28:44.459> merkel<01:28:44.819> eyes<01:28:44.939> this 01:28:45.109 --> 01:28:45.119 align:start position:0% eyes we do we sort of merkel eyes this 01:28:45.119 --> 01:28:46.459 align:start position:0% eyes we do we sort of merkel eyes this subtree<01:28:45.659> that's<01:28:45.899> actually<01:28:46.169> instantiated 01:28:46.459 --> 01:28:46.469 align:start position:0% subtree that's actually instantiated 01:28:46.469 --> 01:28:48.289 align:start position:0% subtree that's actually instantiated where<01:28:46.889> we<01:28:47.010> you<01:28:47.249> know<01:28:47.279> the<01:28:47.519> sachet<01:28:47.969> children 01:28:48.289 --> 01:28:48.299 align:start position:0% where we you know the sachet children 01:28:48.299 --> 01:28:50.899 align:start position:0% where we you know the sachet children pointers<01:28:48.629> of<01:28:48.749> children<01:28:49.519> but<01:28:50.519> that's<01:28:50.699> going<01:28:50.849> to 01:28:50.899 --> 01:28:50.909 align:start position:0% pointers of children but that's going to 01:28:50.909 --> 01:28:54.349 align:start position:0% pointers of children but that's going to be<01:28:50.999> I<01:28:51.629> think<01:28:52.169> it's<01:28:52.439> gonna<01:28:52.499> be<01:28:52.709> on<01:28:52.829> like<01:28:53.239> you<01:28:54.239> can 01:28:54.349 --> 01:28:54.359 align:start position:0% be I think it's gonna be on like you can 01:28:54.359 --> 01:28:57.139 align:start position:0% be I think it's gonna be on like you can insert<01:28:54.599> a<01:28:54.659> few<01:28:54.869> notes<01:28:55.109> or<01:28:55.319> like<01:28:55.439> a<01:28:55.649> I<01:28:56.429> think<01:28:56.639> for 01:28:57.139 --> 01:28:57.149 align:start position:0% insert a few notes or like a I think for 01:28:57.149 --> 01:28:58.579 align:start position:0% insert a few notes or like a I think for a<01:28:57.179> theorem<01:28:57.479> it's<01:28:57.629> an<01:28:57.779> average<01:28:58.229> they've 01:28:58.579 --> 01:28:58.589 align:start position:0% a theorem it's an average they've 01:28:58.589 --> 01:28:59.119 align:start position:0% a theorem it's an average they've inserted 01:28:59.119 --> 01:28:59.129 align:start position:0% inserted 01:28:59.129 --> 01:29:02.779 align:start position:0% inserted per<01:29:00.119> block<01:29:00.359> eight<01:29:00.629> accounts<01:29:01.499> an<01:29:01.709> average<01:29:02.399> but 01:29:02.779 --> 01:29:02.789 align:start position:0% per block eight accounts an average but 01:29:02.789 --> 01:29:05.299 align:start position:0% per block eight accounts an average but maybe<01:29:02.969> sometimes<01:29:03.569> more<01:29:03.629> sometimes<01:29:03.899> less<01:29:04.279> so<01:29:05.279> I 01:29:05.299 --> 01:29:05.309 align:start position:0% maybe sometimes more sometimes less so I 01:29:05.309 --> 01:29:06.559 align:start position:0% maybe sometimes more sometimes less so I think<01:29:05.399> it's<01:29:05.609> gonna<01:29:05.699> be<01:29:05.849> trivial 01:29:06.559 --> 01:29:06.569 align:start position:0% think it's gonna be trivial 01:29:06.569 --> 01:29:08.750 align:start position:0% think it's gonna be trivial just<01:29:07.169> just<01:29:07.589> because<01:29:07.829> we're<01:29:08.010> doing<01:29:08.429> a<01:29:08.609> little 01:29:08.750 --> 01:29:08.760 align:start position:0% just just because we're doing a little 01:29:08.760 --> 01:29:10.609 align:start position:0% just just because we're doing a little bit<01:29:08.939> of<01:29:09.059> you<01:29:09.179> know<01:29:09.299> of<01:29:09.629> the<01:29:09.929> parent<01:29:10.349> of<01:29:10.469> the 01:29:10.609 --> 01:29:10.619 align:start position:0% bit of you know of the parent of the 01:29:10.619 --> 01:29:12.349 align:start position:0% bit of you know of the parent of the glass<01:29:10.799> child<01:29:11.039> update<01:29:11.369> you<01:29:11.789> know<01:29:11.879> insert<01:29:12.209> new 01:29:12.349 --> 01:29:12.359 align:start position:0% glass child update you know insert new 01:29:12.359 --> 01:29:14.839 align:start position:0% glass child update you know insert new internal<01:29:12.779> know<01:29:12.989> things<01:29:13.229> like<01:29:13.349> this<01:29:13.729> but<01:29:14.729> it 01:29:14.839 --> 01:29:14.849 align:start position:0% internal know things like this but it 01:29:14.849 --> 01:29:15.919 align:start position:0% internal know things like this but it soon<01:29:14.999> it's<01:29:15.239> just<01:29:15.359> going<01:29:15.449> to<01:29:15.539> be<01:29:15.599> you<01:29:15.809> know<01:29:15.899> very 01:29:15.919 --> 01:29:15.929 align:start position:0% soon it's just going to be you know very 01:29:15.929 --> 01:29:18.589 align:start position:0% soon it's just going to be you know very close<01:29:16.549> it's<01:29:17.549> just<01:29:17.849> gonna<01:29:18.059> be<01:29:18.209> like<01:29:18.239> a<01:29:18.359> few 01:29:18.589 --> 01:29:18.599 align:start position:0% close it's just gonna be like a few 01:29:18.599 --> 01:29:20.509 align:start position:0% close it's just gonna be like a few things<01:29:18.809> we<01:29:19.649> call<01:29:19.769> this<01:29:19.919> sort<01:29:20.069> of<01:29:20.159> business 01:29:20.509 --> 01:29:20.519 align:start position:0% things we call this sort of business 01:29:20.519 --> 01:29:22.519 align:start position:0% things we call this sort of business logic<01:29:20.639> this<01:29:20.909> sort<01:29:21.119> of<01:29:21.149> fast<01:29:21.689> stuff<01:29:22.019> but<01:29:22.260> it's 01:29:22.519 --> 01:29:22.529 align:start position:0% logic this sort of fast stuff but it's 01:29:22.529 --> 01:29:23.929 align:start position:0% logic this sort of fast stuff but it's still<01:29:22.679> gonna<01:29:22.829> be<01:29:22.919> dominated<01:29:23.429> by<01:29:23.459> hashing<01:29:23.879> I 01:29:23.929 --> 01:29:23.939 align:start position:0% still gonna be dominated by hashing I 01:29:23.939 --> 01:29:26.659 align:start position:0% still gonna be dominated by hashing I believe<01:29:24.209> and<01:29:24.419> then<01:29:24.869> the<01:29:25.319> speed-up<01:29:26.249> hashing 01:29:26.659 --> 01:29:26.669 align:start position:0% believe and then the speed-up hashing 01:29:26.669 --> 01:29:28.279 align:start position:0% believe and then the speed-up hashing bottleneck<01:29:27.119> and<01:29:27.299> then<01:29:27.419> speed<01:29:27.659> up<01:29:27.749> transaction 01:29:28.279 --> 01:29:28.289 align:start position:0% bottleneck and then speed up transaction 01:29:28.289 --> 01:29:30.199 align:start position:0% bottleneck and then speed up transaction so<01:29:28.619> I<01:29:28.649> think<01:29:28.859> there's<01:29:29.010> hope<01:29:29.039> that's<01:29:29.639> what<01:29:30.179> I 01:29:30.199 --> 01:29:30.209 align:start position:0% so I think there's hope that's what I 01:29:30.209 --> 01:29:30.490 align:start position:0% so I think there's hope that's what I want 01:29:30.490 --> 01:29:30.500 align:start position:0% want 01:29:30.500 --> 01:29:32.320 align:start position:0% want say<01:29:30.620> that<01:29:30.830> there's<01:29:31.040> hope<01:29:31.220> for<01:29:31.250> this<01:29:31.520> model<01:29:31.910> the 01:29:32.320 --> 01:29:32.330 align:start position:0% say that there's hope for this model the 01:29:32.330 --> 01:29:34.240 align:start position:0% say that there's hope for this model the other<01:29:32.450> big<01:29:32.690> thing<01:29:32.870> about<01:29:32.990> huge<01:29:33.410> thing<01:29:33.680> is<01:29:33.890> this 01:29:34.240 --> 01:29:34.250 align:start position:0% other big thing about huge thing is this 01:29:34.250 --> 01:29:35.980 align:start position:0% other big thing about huge thing is this 25<01:29:34.730> kilobytes<01:29:35.330> they're<01:29:35.570> gonna<01:29:35.660> they're 01:29:35.980 --> 01:29:35.990 align:start position:0% 25 kilobytes they're gonna they're 01:29:35.990 --> 01:29:37.720 align:start position:0% 25 kilobytes they're gonna they're talking<01:29:36.290> about<01:29:36.410> way<01:29:36.650> more<01:29:36.890> this<01:29:37.070> you<01:29:37.220> proposal 01:29:37.720 --> 01:29:37.730 align:start position:0% talking about way more this you proposal 01:29:37.730 --> 01:29:41.110 align:start position:0% talking about way more this you proposal I<01:29:37.820> saw<01:29:38.530> for<01:29:39.530> 64<01:29:40.040> shards<01:29:40.610> they're<01:29:40.790> talking 01:29:41.110 --> 01:29:41.120 align:start position:0% I saw for 64 shards they're talking 01:29:41.120 --> 01:29:42.910 align:start position:0% I saw for 64 shards they're talking about<01:29:41.300> increasing<01:29:41.990> called<01:29:42.200> data<01:29:42.380> by<01:29:42.650> a<01:29:42.680> lot 01:29:42.910 --> 01:29:42.920 align:start position:0% about increasing called data by a lot 01:29:42.920 --> 01:29:46.420 align:start position:0% about increasing called data by a lot I'm<01:29:43.370> like<01:29:43.820> you<01:29:43.940> know<01:29:44.060> 128<01:29:44.720> or<01:29:44.960> even<01:29:45.530> there's 01:29:46.420 --> 01:29:46.430 align:start position:0% I'm like you know 128 or even there's 01:29:46.430 --> 01:29:52.180 align:start position:0% I'm like you know 128 or even there's some<01:29:46.990> 512<01:29:48.340> 512<01:29:49.340> you<01:29:50.060> know<01:29:50.180> half<01:29:50.570> a<01:29:50.770> megabyte<01:29:51.770> so 01:29:52.180 --> 01:29:52.190 align:start position:0% some 512 512 you know half a megabyte so 01:29:52.190 --> 01:29:54.010 align:start position:0% some 512 512 you know half a megabyte so this<01:29:52.310> is<01:29:52.430> huge<01:29:52.760> and<01:29:52.940> then<01:29:53.240> this<01:29:53.390> this<01:29:53.780> sort<01:29:53.960> of 01:29:54.010 --> 01:29:54.020 align:start position:0% this is huge and then this this sort of 01:29:54.020 --> 01:29:55.660 align:start position:0% this is huge and then this this sort of deduplication<01:29:54.590> is<01:29:54.830> going<01:29:54.950> to<01:29:55.010> be<01:29:55.130> weight<01:29:55.310> is 01:29:55.660 --> 01:29:55.670 align:start position:0% deduplication is going to be weight is 01:29:55.670 --> 01:29:56.890 align:start position:0% deduplication is going to be weight is going<01:29:55.850> to<01:29:55.910> help<01:29:56.090> us<01:29:56.150> by<01:29:56.330> it's<01:29:56.480> not<01:29:56.510> going<01:29:56.750> to<01:29:56.810> be 01:29:56.890 --> 01:29:56.900 align:start position:0% going to help us by it's not going to be 01:29:56.900 --> 01:29:58.270 align:start position:0% going to help us by it's not going to be only<01:29:57.140> 20%<01:29:57.410> because<01:29:57.650> there's<01:29:57.890> gonna<01:29:58.040> be<01:29:58.130> so 01:29:58.270 --> 01:29:58.280 align:start position:0% only 20% because there's gonna be so 01:29:58.280 --> 01:30:00.700 align:start position:0% only 20% because there's gonna be so many<01:29:58.340> more<01:29:58.520> accounts<01:29:58.850> so<01:29:58.940> this<01:29:59.060> is<01:29:59.500> gonna<01:30:00.500> help 01:30:00.700 --> 01:30:00.710 align:start position:0% many more accounts so this is gonna help 01:30:00.710 --> 01:30:03.400 align:start position:0% many more accounts so this is gonna help sup<01:30:00.950> you<01:30:01.280> know<01:30:01.400> every<01:30:01.670> cycle<01:30:02.510> is<01:30:02.870> important 01:30:03.400 --> 01:30:03.410 align:start position:0% sup you know every cycle is important 01:30:03.410 --> 01:30:05.740 align:start position:0% sup you know every cycle is important that<01:30:03.620> were<01:30:03.770> you<01:30:03.860> you<01:30:04.430> know<01:30:04.550> bite<01:30:05.000> of<01:30:05.300> call<01:30:05.540> data 01:30:05.740 --> 01:30:05.750 align:start position:0% that were you you know bite of call data 01:30:05.750 --> 01:30:07.660 align:start position:0% that were you you know bite of call data is<01:30:05.870> important<01:30:06.320> that's<01:30:06.410> like<01:30:06.710> and<01:30:06.920> then<01:30:07.220> you 01:30:07.660 --> 01:30:07.670 align:start position:0% is important that's like and then you 01:30:07.670 --> 01:30:09.760 align:start position:0% is important that's like and then you know<01:30:07.790> see<01:30:08.030> the<01:30:08.120> programmers<01:30:08.750> hi<01:30:08.900> I'm<01:30:09.200> writing 01:30:09.760 --> 01:30:09.770 align:start position:0% know see the programmers hi I'm writing 01:30:09.770 --> 01:30:11.710 align:start position:0% know see the programmers hi I'm writing emails<01:30:10.550> and<01:30:10.670> contracts<01:30:10.970> and<01:30:11.060> see<01:30:11.270> so<01:30:11.600> that's 01:30:11.710 --> 01:30:11.720 align:start position:0% emails and contracts and see so that's 01:30:11.720 --> 01:30:17.890 align:start position:0% emails and contracts and see so that's it 01:30:17.890 --> 01:30:17.900 align:start position:0% 01:30:17.900 --> 01:30:20.210 align:start position:0% time<01:30:18.900> for<01:30:19.080> questions<01:30:19.440> are<01:30:19.620> introduced<01:30:20.010> in<01:30:20.130> the 01:30:20.210 --> 01:30:20.220 align:start position:0% time for questions are introduced in the 01:30:20.220 --> 01:30:21.490 align:start position:0% time for questions are introduced in the US 01:30:21.490 --> 01:30:21.500 align:start position:0% US 01:30:21.500 --> 01:30:25.310 align:start position:0% US yes<01:30:22.500> sir<01:30:22.620> I<01:30:23.280> was<01:30:23.820> a<01:30:23.880> little<01:30:24.150> confused<01:30:24.720> with 01:30:25.310 --> 01:30:25.320 align:start position:0% yes sir I was a little confused with 01:30:25.320 --> 01:30:28.220 align:start position:0% yes sir I was a little confused with what<01:30:25.620> you're<01:30:25.830> beginning<01:30:26.730> exactly<01:30:27.360> yes 01:30:28.220 --> 01:30:28.230 align:start position:0% what you're beginning exactly yes 01:30:28.230 --> 01:30:32.570 align:start position:0% what you're beginning exactly yes so<01:30:28.950> if<01:30:29.220> you<01:30:29.400> have<01:30:29.580> one<01:30:30.230> child<01:30:31.230> you<01:30:32.160> can<01:30:32.310> you 01:30:32.570 --> 01:30:32.580 align:start position:0% so if you have one child you can you 01:30:32.580 --> 01:30:34.100 align:start position:0% so if you have one child you can you have<01:30:32.730> to<01:30:32.850> pass<01:30:33.000> all<01:30:33.180> the<01:30:33.330> witness<01:30:33.630> all<01:30:33.900> the 01:30:34.100 --> 01:30:34.110 align:start position:0% have to pass all the witness all the 01:30:34.110 --> 01:30:35.690 align:start position:0% have to pass all the witness all the hashes<01:30:34.440> of<01:30:34.650> a<01:30:34.770> you<01:30:35.010> know<01:30:35.100> neighbors<01:30:35.430> neighbor 01:30:35.690 --> 01:30:35.700 align:start position:0% hashes of a you know neighbors neighbor 01:30:35.700 --> 01:30:36.650 align:start position:0% hashes of a you know neighbors neighbor neighbor<01:30:35.850> neighbor<01:30:36.090> neighbor<01:30:36.300> all<01:30:36.510> the<01:30:36.570> way 01:30:36.650 --> 01:30:36.660 align:start position:0% neighbor neighbor neighbor all the way 01:30:36.660 --> 01:30:39.140 align:start position:0% neighbor neighbor neighbor all the way done<01:30:36.840> but<01:30:37.740> you<01:30:38.520> don't<01:30:38.670> have<01:30:38.760> to<01:30:38.880> do<01:30:39.000> that 01:30:39.140 --> 01:30:39.150 align:start position:0% done but you don't have to do that 01:30:39.150 --> 01:30:41.540 align:start position:0% done but you don't have to do that because<01:30:39.330> you<01:30:39.600> recompute<01:30:40.170> sometimes<01:30:40.680> you 01:30:41.540 --> 01:30:41.550 align:start position:0% because you recompute sometimes you 01:30:41.550 --> 01:30:43.310 align:start position:0% because you recompute sometimes you could<01:30:41.700> you<01:30:41.790> can<01:30:41.910> recompute<01:30:42.450> the<01:30:42.540> so<01:30:43.080> you<01:30:43.170> don't 01:30:43.310 --> 01:30:43.320 align:start position:0% could you can recompute the so you don't 01:30:43.320 --> 01:30:46.220 align:start position:0% could you can recompute the so you don't have<01:30:43.410> to<01:30:43.530> pass<01:30:44.300> it'll<01:30:45.300> be<01:30:45.480> recomputed<01:30:45.810> on<01:30:46.050> chin 01:30:46.220 --> 01:30:46.230 align:start position:0% have to pass it'll be recomputed on chin 01:30:46.230 --> 01:30:47.540 align:start position:0% have to pass it'll be recomputed on chin anyways<01:30:46.620> so<01:30:46.770> you<01:30:46.830> have<01:30:46.950> to<01:30:47.130> you<01:30:47.400> have<01:30:47.430> to 01:30:47.540 --> 01:30:47.550 align:start position:0% anyways so you have to you have to 01:30:47.550 --> 01:30:49.610 align:start position:0% anyways so you have to you have to recompute<01:30:48.000> enough<01:30:48.300> this<01:30:48.690> this<01:30:49.080> site<01:30:49.290> anyway 01:30:49.610 --> 01:30:49.620 align:start position:0% recompute enough this this site anyway 01:30:49.620 --> 01:30:52.370 align:start position:0% recompute enough this this site anyway so<01:30:49.680> then<01:30:50.040> you<01:30:51.030> don't<01:30:51.120> pass<01:30:51.390> certain<01:30:51.870> hashes<01:30:52.230> at 01:30:52.370 --> 01:30:52.380 align:start position:0% so then you don't pass certain hashes at 01:30:52.380 --> 01:30:54.290 align:start position:0% so then you don't pass certain hashes at the<01:30:52.470> very<01:30:52.650> very<01:30:52.920> close<01:30:53.130> to<01:30:53.250> the<01:30:53.370> root<01:30:53.550> you<01:30:53.850> you 01:30:54.290 --> 01:30:54.300 align:start position:0% the very very close to the root you you 01:30:54.300 --> 01:30:55.640 align:start position:0% the very very close to the root you you don't<01:30:54.540> have<01:30:54.720> stashes<01:30:55.170> because<01:30:55.410> they're<01:30:55.530> gonna 01:30:55.640 --> 01:30:55.650 align:start position:0% don't have stashes because they're gonna 01:30:55.650 --> 01:30:58.390 align:start position:0% don't have stashes because they're gonna be<01:30:55.740> computed<01:30:56.190> anyway<01:30:56.600> you<01:30:57.600> mean<01:30:57.780> essentially 01:30:58.390 --> 01:30:58.400 align:start position:0% be computed anyway you mean essentially 01:30:58.400 --> 01:30:59.660 align:start position:0% be computed anyway you mean essentially before 01:30:59.660 --> 01:30:59.670 align:start position:0% before 01:30:59.670 --> 01:31:01.490 align:start position:0% before yes<01:31:00.030> it's<01:31:00.180> yes<01:31:00.600> I<01:31:00.810> should<01:31:00.960> have<01:31:00.990> just<01:31:01.200> used<01:31:01.350> the 01:31:01.490 --> 01:31:01.500 align:start position:0% yes it's yes I should have just used the 01:31:01.500 --> 01:31:03.230 align:start position:0% yes it's yes I should have just used the word<01:31:01.590> multi-purpose<01:31:02.250> but<01:31:02.850> maybe<01:31:02.970> some<01:31:03.210> people 01:31:03.230 --> 01:31:03.240 align:start position:0% word multi-purpose but maybe some people 01:31:03.240 --> 01:31:08.270 align:start position:0% word multi-purpose but maybe some people don't<01:31:03.540> like<01:31:03.720> that<01:31:03.870> word<01:31:07.130> since<01:31:08.130> you're 01:31:08.270 --> 01:31:08.280 align:start position:0% don't like that word since you're 01:31:08.280 --> 01:31:12.320 align:start position:0% don't like that word since you're calling<01:31:08.700> it<01:31:10.160> called<01:31:11.160> it<01:31:11.340> sighs<01:31:12.000> you're 01:31:12.320 --> 01:31:12.330 align:start position:0% calling it called it sighs you're 01:31:12.330 --> 01:31:14.510 align:start position:0% calling it called it sighs you're imagining<01:31:12.720> that<01:31:12.930> these<01:31:13.710> come<01:31:14.040> equipped<01:31:14.190> with 01:31:14.510 --> 01:31:14.520 align:start position:0% imagining that these come equipped with 01:31:14.520 --> 01:31:17.240 align:start position:0% imagining that these come equipped with every<01:31:14.820> transaction<01:31:15.180> and<01:31:15.630> then<01:31:16.100> when<01:31:17.100> they 01:31:17.240 --> 01:31:17.250 align:start position:0% every transaction and then when they 01:31:17.250 --> 01:31:20.360 align:start position:0% every transaction and then when they gets<01:31:17.520> bunched<01:31:18.270> together<01:31:18.450> in<01:31:18.780> a<01:31:18.870> block<01:31:19.080> you<01:31:19.410> do 01:31:20.360 --> 01:31:20.370 align:start position:0% gets bunched together in a block you do 01:31:20.370 --> 01:31:22.640 align:start position:0% gets bunched together in a block you do this<01:31:20.550> do<01:31:20.760> occasional<01:31:21.420> construction<01:31:22.380> up<01:31:22.500> but 01:31:22.640 --> 01:31:22.650 align:start position:0% this do occasional construction up but 01:31:22.650 --> 01:31:26.450 align:start position:0% this do occasional construction up but then<01:31:23.390> you<01:31:24.390> get<01:31:24.510> the<01:31:24.570> final<01:31:24.980> great<01:31:25.980> question 01:31:26.450 --> 01:31:26.460 align:start position:0% then you get the final great question 01:31:26.460 --> 01:31:28.880 align:start position:0% then you get the final great question cool<01:31:26.670> does<01:31:26.910> this<01:31:27.150> you<01:31:27.570> know<01:31:27.660> it's<01:31:28.350> merging<01:31:28.770> of 01:31:28.880 --> 01:31:28.890 align:start position:0% cool does this you know it's merging of 01:31:28.890 --> 01:31:31.250 align:start position:0% cool does this you know it's merging of these<01:31:29.040> multi<01:31:29.400> proofs<01:31:29.640> in<01:31:29.790> there<01:31:29.940> into<01:31:30.750> one<01:31:30.900> yes 01:31:31.250 --> 01:31:31.260 align:start position:0% these multi proofs in there into one yes 01:31:31.260 --> 01:31:34.940 align:start position:0% these multi proofs in there into one yes it<01:31:31.740> could<01:31:31.920> be<01:31:32.010> done<01:31:32.420> we<01:31:33.420> need<01:31:33.450> a<01:31:33.660> key<01:31:33.900> role<01:31:33.960> that 01:31:34.940 --> 01:31:34.950 align:start position:0% it could be done we need a key role that 01:31:34.950 --> 01:31:36.860 align:start position:0% it could be done we need a key role that writer<01:31:35.280> who<01:31:35.580> will<01:31:35.700> write<01:31:35.940> this<01:31:36.180> merging<01:31:36.660> and 01:31:36.860 --> 01:31:36.870 align:start position:0% writer who will write this merging and 01:31:36.870 --> 01:31:39.080 align:start position:0% writer who will write this merging and this<01:31:36.990> best<01:31:37.350> practices<01:31:38.340> maybe<01:31:38.550> not<01:31:38.790> maybe 01:31:39.080 --> 01:31:39.090 align:start position:0% this best practices maybe not maybe 01:31:39.090 --> 01:31:40.400 align:start position:0% this best practices maybe not maybe it'll<01:31:39.300> be<01:31:39.390> similar<01:31:39.600> to<01:31:39.810> this<01:31:39.900> maybe<01:31:40.080> it<01:31:40.290> won't 01:31:40.400 --> 01:31:40.410 align:start position:0% it'll be similar to this maybe it won't 01:31:40.410 --> 01:31:41.600 align:start position:0% it'll be similar to this maybe it won't be<01:31:40.530> somewhere<01:31:40.860> but<01:31:41.100> I<01:31:41.190> don't<01:31:41.310> know<01:31:41.370> how<01:31:41.490> much 01:31:41.600 --> 01:31:41.610 align:start position:0% be somewhere but I don't know how much 01:31:41.610 --> 01:31:42.620 align:start position:0% be somewhere but I don't know how much better<01:31:41.790> you're<01:31:41.940> going<01:31:42.030> to<01:31:42.090> get<01:31:42.240> with<01:31:42.390> me<01:31:42.510> if 01:31:42.620 --> 01:31:42.630 align:start position:0% better you're going to get with me if 01:31:42.630 --> 01:31:43.880 align:start position:0% better you're going to get with me if we're<01:31:42.780> down<01:31:42.900> needed<01:31:43.170> by<01:31:43.230> actions<01:31:43.620> that<01:31:43.680> maybe 01:31:43.880 --> 01:31:43.890 align:start position:0% we're down needed by actions that maybe 01:31:43.890 --> 01:31:45.440 align:start position:0% we're down needed by actions that maybe might<01:31:44.010> have<01:31:44.040> just<01:31:44.280> but<01:31:44.490> hopefully<01:31:45.210> there<01:31:45.390> will 01:31:45.440 --> 01:31:45.450 align:start position:0% might have just but hopefully there will 01:31:45.450 --> 01:31:49.190 align:start position:0% might have just but hopefully there will be<01:31:45.510> some<01:31:45.720> hero<01:31:45.930> that<01:31:46.140> invents<01:31:46.910> an<01:31:47.910> EE<01:31:48.180> and<01:31:49.020> with 01:31:49.190 --> 01:31:49.200 align:start position:0% be some hero that invents an EE and with 01:31:49.200 --> 01:31:50.990 align:start position:0% be some hero that invents an EE and with all<01:31:49.440> this<01:31:49.830> you<01:31:49.980> know<01:31:50.010> merging<01:31:50.760> and<01:31:50.910> the 01:31:50.990 --> 01:31:51.000 align:start position:0% all this you know merging and the 01:31:51.000 --> 01:31:52.430 align:start position:0% all this you know merging and the perfect<01:31:51.210> tree<01:31:51.630> and<01:31:51.780> the<01:31:51.840> perfect<01:31:52.170> everything 01:31:52.430 --> 01:31:52.440 align:start position:0% perfect tree and the perfect everything 01:31:52.440 --> 01:31:56.390 align:start position:0% perfect tree and the perfect everything so<01:31:52.890> yes<01:31:53.580> I<01:31:53.880> don't<01:31:54.510> know<01:31:55.100> but<01:31:56.100> I<01:31:56.130> mean<01:31:56.310> an 01:31:56.390 --> 01:31:56.400 align:start position:0% so yes I don't know but I mean an 01:31:56.400 --> 01:32:00.850 align:start position:0% so yes I don't know but I mean an alternative<01:31:57.180> is<01:31:57.300> that<01:31:57.330> you<01:31:58.070> let<01:31:59.070> the<01:31:59.600> business 01:32:00.850 --> 01:32:00.860 align:start position:0% alternative is that you let the business 01:32:00.860 --> 01:32:03.860 align:start position:0% alternative is that you let the business yes<01:32:01.860> we<01:32:02.040> don't<01:32:02.580> have<01:32:02.670> a<01:32:02.730> by<01:32:03.510> that<01:32:03.630> I<01:32:03.690> mean 01:32:03.860 --> 01:32:03.870 align:start position:0% yes we don't have a by that I mean 01:32:03.870 --> 01:32:05.540 align:start position:0% yes we don't have a by that I mean though<01:32:04.110> there<01:32:04.470> will<01:32:04.530> be<01:32:04.590> some<01:32:04.890> black<01:32:05.070> producer 01:32:05.540 --> 01:32:05.550 align:start position:0% though there will be some black producer 01:32:05.550 --> 01:32:07.190 align:start position:0% though there will be some black producer some<01:32:05.820> relay<01:32:06.090> or<01:32:06.210> infrastructure<01:32:06.750> or<01:32:06.870> whatever 01:32:07.190 --> 01:32:07.200 align:start position:0% some relay or infrastructure or whatever 01:32:07.200 --> 01:32:08.660 align:start position:0% some relay or infrastructure or whatever some<01:32:07.500> V<01:32:07.650> market<01:32:07.950> infrastructure<01:32:08.370> to<01:32:08.550> handle 01:32:08.660 --> 01:32:08.670 align:start position:0% some V market infrastructure to handle 01:32:08.670 --> 01:32:11.180 align:start position:0% some V market infrastructure to handle all<01:32:08.970> this<01:32:09.120> stuff<01:32:09.390> I<01:32:09.570> it's<01:32:10.440> a<01:32:10.530> big<01:32:10.710> question<01:32:10.830> but 01:32:11.180 --> 01:32:11.190 align:start position:0% all this stuff I it's a big question but 01:32:11.190 --> 01:32:13.010 align:start position:0% all this stuff I it's a big question but it's<01:32:11.400> unobtainium<01:32:12.060> but<01:32:12.270> the<01:32:12.450> great<01:32:12.870> thing 01:32:13.010 --> 01:32:13.020 align:start position:0% it's unobtainium but the great thing 01:32:13.020 --> 01:32:16.400 align:start position:0% it's unobtainium but the great thing about<01:32:13.080> f2<01:32:13.560> is<01:32:13.770> that<01:32:14.490> you<01:32:14.910> know<01:32:15.080> crypto<01:32:16.080> kitties 01:32:16.400 --> 01:32:16.410 align:start position:0% about f2 is that you know crypto kitties 01:32:16.410 --> 01:32:18.350 align:start position:0% about f2 is that you know crypto kitties or<01:32:16.590> whoever<01:32:16.860> can<01:32:16.980> launch<01:32:17.730> and<01:32:17.970> some<01:32:18.240> there 01:32:18.350 --> 01:32:18.360 align:start position:0% or whoever can launch and some there 01:32:18.360 --> 01:32:19.980 align:start position:0% or whoever can launch and some there will<01:32:18.450> be<01:32:18.480> some<01:32:18.780> hero<01:32:19.020> that<01:32:19.200> will<01:32:19.380> invent 01:32:19.980 --> 01:32:19.990 align:start position:0% will be some hero that will invent 01:32:19.990 --> 01:32:21.810 align:start position:0% will be some hero that will invent relayer<01:32:20.470> than<01:32:20.860> you<01:32:20.980> and<01:32:21.280> it's<01:32:21.490> not<01:32:21.610> going<01:32:21.760> to 01:32:21.810 --> 01:32:21.820 align:start position:0% relayer than you and it's not going to 01:32:21.820 --> 01:32:23.460 align:start position:0% relayer than you and it's not going to be<01:32:21.910> you<01:32:22.090> know<01:32:22.120> you<01:32:22.720> have<01:32:22.840> to<01:32:22.930> do<01:32:23.020> it<01:32:23.110> this<01:32:23.260> way 01:32:23.460 --> 01:32:23.470 align:start position:0% be you know you have to do it this way 01:32:23.470 --> 01:32:25.200 align:start position:0% be you know you have to do it this way because<01:32:23.620> the<01:32:24.100> theory<01:32:24.250> and<01:32:24.430> foundation<01:32:24.790> set<01:32:25.000> so 01:32:25.200 --> 01:32:25.210 align:start position:0% because the theory and foundation set so 01:32:25.210 --> 01:32:26.880 align:start position:0% because the theory and foundation set so it's<01:32:25.750> going<01:32:25.900> to<01:32:25.960> be<01:32:26.080> you<01:32:26.290> know<01:32:26.320> you<01:32:26.590> know<01:32:26.680> do<01:32:26.860> it 01:32:26.880 --> 01:32:26.890 align:start position:0% it's going to be you know you know do it 01:32:26.890 --> 01:32:27.870 align:start position:0% it's going to be you know you know do it however<01:32:27.400> you<01:32:27.610> want 01:32:27.870 --> 01:32:27.880 align:start position:0% however you want 01:32:27.880 --> 01:32:36.930 align:start position:0% however you want please<01:32:28.150> teach<01:32:28.570> us<01:32:28.630> because<01:32:29.170> I<01:32:29.410> think<01:32:29.560> that<01:32:35.940> it 01:32:36.930 --> 01:32:36.940 align:start position:0% please teach us because I think that it 01:32:36.940 --> 01:32:43.980 align:start position:0% please teach us because I think that it was<01:32:41.760> basically<01:32:42.760> that<01:32:42.970> they<01:32:43.180> have<01:32:43.390> that<01:32:43.570> use 01:32:43.980 --> 01:32:43.990 align:start position:0% was basically that they have that use 01:32:43.990 --> 01:32:52.830 align:start position:0% was basically that they have that use some<01:32:44.650> trusses<01:32:45.250> approved<01:32:51.270> yes<01:32:52.270> the<01:32:52.510> cold<01:32:52.720> air 01:32:52.830 --> 01:32:52.840 align:start position:0% some trusses approved yes the cold air 01:32:52.840 --> 01:32:55.260 align:start position:0% some trusses approved yes the cold air is<01:32:52.990> enough<01:32:53.200> wanting<01:32:53.590> right<01:32:53.950> now<01:32:54.160> which<01:32:54.910> you 01:32:55.260 --> 01:32:55.270 align:start position:0% is enough wanting right now which you 01:32:55.270 --> 01:32:57.360 align:start position:0% is enough wanting right now which you sang<01:32:55.540> some<01:32:55.930> string<01:32:56.320> of<01:32:56.440> bytes<01:32:56.800> that<01:32:57.130> you<01:32:57.250> have 01:32:57.360 --> 01:32:57.370 align:start position:0% sang some string of bytes that you have 01:32:57.370 --> 01:32:59.880 align:start position:0% sang some string of bytes that you have passed<01:32:57.670> and<01:32:58.030> then<01:32:58.270> to<01:32:59.170> play<01:32:59.380> the<01:32:59.440> very<01:32:59.620> bigger 01:32:59.880 --> 01:32:59.890 align:start position:0% passed and then to play the very bigger 01:32:59.890 --> 01:33:05.580 align:start position:0% passed and then to play the very bigger to<01:33:00.190> learn<01:33:00.520> by<01:33:00.760> the<01:33:02.430> state<01:33:03.430> oh<01:33:03.580> yes<01:33:04.320> yes<01:33:05.320> so 01:33:05.580 --> 01:33:05.590 align:start position:0% to learn by the state oh yes yes so 01:33:05.590 --> 01:33:07.110 align:start position:0% to learn by the state oh yes yes so currently<01:33:06.190> the<01:33:06.280> call<01:33:06.430> data<01:33:06.580> doesn't<01:33:06.940> need 01:33:07.110 --> 01:33:07.120 align:start position:0% currently the call data doesn't need 01:33:07.120 --> 01:33:08.730 align:start position:0% currently the call data doesn't need this<01:33:07.300> proof<01:33:07.570> the<01:33:07.960> call<01:33:08.140> data<01:33:08.290> is<01:33:08.440> just<01:33:08.650> I<01:33:08.710> want 01:33:08.730 --> 01:33:08.740 align:start position:0% this proof the call data is just I want 01:33:08.740 --> 01:33:10.050 align:start position:0% this proof the call data is just I want to<01:33:08.920> send<01:33:09.130> it<01:33:09.280> I<01:33:09.460> want<01:33:09.670> to<01:33:09.700> send<01:33:09.880> them<01:33:09.940> my 01:33:10.050 --> 01:33:10.060 align:start position:0% to send it I want to send them my 01:33:10.060 --> 01:33:11.850 align:start position:0% to send it I want to send them my transaction<01:33:10.510> to<01:33:10.600> this<01:33:10.690> or<01:33:10.930> -<01:33:11.350> uh<01:33:11.440> Micra<01:33:11.710> took 01:33:11.850 --> 01:33:11.860 align:start position:0% transaction to this or - uh Micra took 01:33:11.860 --> 01:33:15.810 align:start position:0% transaction to this or - uh Micra took Katie<01:33:12.040> to<01:33:12.190> this<01:33:12.310> person<01:33:12.780> but<01:33:13.780> with<01:33:14.400> with<01:33:15.400> f2 01:33:15.810 --> 01:33:15.820 align:start position:0% Katie to this person but with with f2 01:33:15.820 --> 01:33:18.120 align:start position:0% Katie to this person but with with f2 with<01:33:16.090> statelessness<01:33:16.510> they<01:33:17.470> have<01:33:17.620> to<01:33:17.770> also<01:33:17.920> in 01:33:18.120 --> 01:33:18.130 align:start position:0% with statelessness they have to also in 01:33:18.130 --> 01:33:19.590 align:start position:0% with statelessness they have to also in their<01:33:18.250> call<01:33:18.430> data<01:33:18.610> past<01:33:18.910> this<01:33:19.090> whole<01:33:19.270> tree 01:33:19.590 --> 01:33:19.600 align:start position:0% their call data past this whole tree 01:33:19.600 --> 01:33:21.030 align:start position:0% their call data past this whole tree structure<01:33:20.110> these<01:33:20.350> edge<01:33:20.530> labels<01:33:20.950> these 01:33:21.030 --> 01:33:21.040 align:start position:0% structure these edge labels these 01:33:21.040 --> 01:33:23.760 align:start position:0% structure these edge labels these accounts<01:33:21.580> these<01:33:21.730> hashes<01:33:21.970> so<01:33:22.440> the<01:33:23.440> call<01:33:23.590> data 01:33:23.760 --> 01:33:23.770 align:start position:0% accounts these hashes so the call data 01:33:23.770 --> 01:33:27.450 align:start position:0% accounts these hashes so the call data is<01:33:23.890> going<01:33:23.980> to<01:33:24.040> be<01:33:24.100> much<01:33:24.280> much<01:33:24.760> huger<01:33:26.100> so<01:33:27.100> in<01:33:27.340> an 01:33:27.450 --> 01:33:27.460 align:start position:0% is going to be much much huger so in an 01:33:27.460 --> 01:33:30.430 align:start position:0% is going to be much much huger so in an alternative<01:33:28.060> environment 01:33:30.430 --> 01:33:30.440 align:start position:0% alternative environment 01:33:30.440 --> 01:33:36.030 align:start position:0% alternative environment the<01:33:31.440> beta<01:33:31.650> matrix<01:33:31.950> ever<01:33:32.340> called 01:33:36.030 --> 01:33:36.040 align:start position:0% 01:33:36.040 --> 01:33:41.190 align:start position:0% yes<01:33:38.430> yes<01:33:39.430> but<01:33:39.670> the<01:33:39.940> E's<01:33:40.480> will<01:33:40.750> already<01:33:40.900> have 01:33:41.190 --> 01:33:41.200 align:start position:0% yes yes but the E's will already have 01:33:41.200 --> 01:33:43.230 align:start position:0% yes yes but the E's will already have the<01:33:41.620> smart<01:33:42.100> contracts<01:33:42.490> will<01:33:42.670> already<01:33:42.940> exist 01:33:43.230 --> 01:33:43.240 align:start position:0% the smart contracts will already exist 01:33:43.240 --> 01:33:44.610 align:start position:0% the smart contracts will already exist unchanged<01:33:43.720> but<01:33:43.870> let's<01:33:44.080> say<01:33:44.200> you<01:33:44.260> want<01:33:44.350> to<01:33:44.500> have 01:33:44.610 --> 01:33:44.620 align:start position:0% unchanged but let's say you want to have 01:33:44.620 --> 01:33:47.490 align:start position:0% unchanged but let's say you want to have some<01:33:44.860> extra<01:33:45.570> bytecode<01:33:46.570> for<01:33:46.600> some<01:33:46.960> custom 01:33:47.490 --> 01:33:47.500 align:start position:0% some extra bytecode for some custom 01:33:47.500 --> 01:33:49.680 align:start position:0% some extra bytecode for some custom thing<01:33:48.190> to<01:33:48.520> send<01:33:48.730> your<01:33:48.910> crypto<01:33:49.210> Kitty<01:33:49.420> that 01:33:49.680 --> 01:33:49.690 align:start position:0% thing to send your crypto Kitty that 01:33:49.690 --> 01:33:50.940 align:start position:0% thing to send your crypto Kitty that it'll<01:33:49.930> you<01:33:50.470> know<01:33:50.500> you'll<01:33:50.740> have<01:33:50.830> an 01:33:50.940 --> 01:33:50.950 align:start position:0% it'll you know you'll have an 01:33:50.950 --> 01:33:52.320 align:start position:0% it'll you know you'll have an interpreter<01:33:51.460> on<01:33:51.490> chain<01:33:51.850> or<01:33:51.970> something<01:33:52.120> that 01:33:52.320 --> 01:33:52.330 align:start position:0% interpreter on chain or something that 01:33:52.330 --> 01:33:53.850 align:start position:0% interpreter on chain or something that yesterday<01:33:52.660> passed<01:33:52.900> whatever<01:33:53.230> you<01:33:53.350> want<01:33:53.500> it's 01:33:53.850 --> 01:33:53.860 align:start position:0% yesterday passed whatever you want it's 01:33:53.860 --> 01:33:55.290 align:start position:0% yesterday passed whatever you want it's you<01:33:54.070> do<01:33:54.190> whatever<01:33:54.340> you<01:33:54.610> want<01:33:54.640> like<01:33:54.850> all<01:33:55.060> data 01:33:55.290 --> 01:33:55.300 align:start position:0% you do whatever you want like all data 01:33:55.300 --> 01:33:57.290 align:start position:0% you do whatever you want like all data you<01:33:55.450> just<01:33:55.480> pass<01:33:55.780> them<01:33:56.020> and<01:33:56.110> invent<01:33:56.830> something 01:33:57.290 --> 01:33:57.300 align:start position:0% you just pass them and invent something 01:33:57.300 --> 01:34:00.120 align:start position:0% you just pass them and invent something amazing<01:33:58.300> like<01:33:58.690> some<01:33:58.870> crypto<01:33:59.170> de<01:33:59.380> 2.0<01:33:59.980> or 01:34:00.120 --> 01:34:00.130 align:start position:0% amazing like some crypto de 2.0 or 01:34:00.130 --> 01:34:03.150 align:start position:0% amazing like some crypto de 2.0 or something<01:34:01.470> and<01:34:02.470> then<01:34:02.590> I've<01:34:02.680> got<01:34:02.830> a<01:34:02.860> little<01:34:02.920> get 01:34:03.150 --> 01:34:03.160 align:start position:0% something and then I've got a little get 01:34:03.160 --> 01:34:04.560 align:start position:0% something and then I've got a little get there<01:34:03.580> will<01:34:03.670> be<01:34:03.700> another<01:34:03.940> bubble<01:34:04.360> I'm<01:34:04.420> never 01:34:04.560 --> 01:34:04.570 align:start position:0% there will be another bubble I'm never 01:34:04.570 --> 01:34:11.490 align:start position:0% there will be another bubble I'm never gonna<01:34:04.690> get<01:34:04.930> rich<01:34:05.110> I'll<01:34:06.010> retire<01:34:10.200> we<01:34:11.200> have<01:34:11.290> time 01:34:11.490 --> 01:34:11.500 align:start position:0% gonna get rich I'll retire we have time 01:34:11.500 --> 01:34:14.270 align:start position:0% gonna get rich I'll retire we have time for<01:34:11.530> another 01:34:14.270 --> 01:34:14.280 align:start position:0% 01:34:14.280 --> 01:34:17.219 align:start position:0% also<01:34:15.280> an<01:34:15.459> important<01:34:16.179> opportunity<01:34:16.539> the<01:34:17.199> last 01:34:17.219 --> 01:34:17.229 align:start position:0% also an important opportunity the last 01:34:17.229 --> 01:34:19.319 align:start position:0% also an important opportunity the last box<01:34:17.769> if<01:34:18.130> it's<01:34:18.309> specific<01:34:18.459> to<01:34:18.729> this<01:34:18.909> talk<01:34:19.150> very 01:34:19.319 --> 01:34:19.329 align:start position:0% box if it's specific to this talk very 01:34:19.329 --> 01:34:24.449 align:start position:0% box if it's specific to this talk very do<01:34:22.559> if<01:34:23.559> you'll<01:34:23.829> have<01:34:23.949> another<01:34:24.130> like<01:34:24.340> 10 01:34:24.449 --> 01:34:24.459 align:start position:0% do if you'll have another like 10 01:34:24.459 --> 01:34:43.069 align:start position:0% do if you'll have another like 10 minutes<01:34:24.670> at<01:34:24.820> 300<01:34:25.030> K<01:34:25.979> will<01:34:27.090> speak<01:34:28.090> now<01:34:29.429> oh<01:34:36.300> okay 01:34:43.069 --> 01:34:43.079 align:start position:0% 01:34:43.079 --> 01:34:51.580 align:start position:0% you<01:34:44.079> have<01:34:44.260> to<01:34:44.380> link<01:34:44.499> to<01:34:44.679> right 01:34:51.580 --> 01:34:51.590 align:start position:0% 01:34:51.590 --> 01:34:56.890 align:start position:0% okay<01:34:52.670> hello<01:34:53.670> my<01:34:54.480> name<01:34:54.599> is<01:34:54.659> Jared<01:34:54.989> washing<01:34:55.769> her 01:34:56.890 --> 01:34:56.900 align:start position:0% okay hello my name is Jared washing her 01:34:56.900 --> 01:35:00.229 align:start position:0% okay hello my name is Jared washing her i'll<01:34:57.900> just<01:34:58.230> preface<01:34:58.559> this<01:34:58.739> that<01:34:59.099> I<01:34:59.340> am<01:34:59.369> NOT<01:34:59.969> an 01:35:00.229 --> 01:35:00.239 align:start position:0% i'll just preface this that I am NOT an 01:35:00.239 --> 01:35:02.120 align:start position:0% i'll just preface this that I am NOT an expert<01:35:00.389> on<01:35:00.869> zero<01:35:01.170> knowledge<01:35:01.380> proof<01:35:01.559> or 01:35:02.120 --> 01:35:02.130 align:start position:0% expert on zero knowledge proof or 01:35:02.130 --> 01:35:04.479 align:start position:0% expert on zero knowledge proof or roll-up<01:35:02.460> so<01:35:02.789> if<01:35:03.059> I<01:35:03.179> say<01:35:03.420> anything<01:35:03.749> that<01:35:03.900> is 01:35:04.479 --> 01:35:04.489 align:start position:0% roll-up so if I say anything that is 01:35:04.489 --> 01:35:07.040 align:start position:0% roll-up so if I say anything that is extremely<01:35:05.489> inaccurate<01:35:05.730> don't<01:35:06.539> feel<01:35:06.749> free 01:35:07.040 --> 01:35:07.050 align:start position:0% extremely inaccurate don't feel free 01:35:07.050 --> 01:35:10.729 align:start position:0% extremely inaccurate don't feel free feel<01:35:07.559> free<01:35:07.889> to<01:35:08.269> correctly 01:35:10.729 --> 01:35:10.739 align:start position:0% feel free to correctly 01:35:10.739 --> 01:35:14.810 align:start position:0% feel free to correctly that<01:35:11.039> being<01:35:11.280> said<01:35:13.099> sir<01:35:14.130> yes<01:35:14.519> there's<01:35:14.760> a 01:35:14.810 --> 01:35:14.820 align:start position:0% that being said sir yes there's a 01:35:14.820 --> 01:35:26.299 align:start position:0% that being said sir yes there's a clicker<01:35:15.030> oh<01:35:21.800> cool<01:35:22.800> so<01:35:23.630> what<01:35:24.630> is<01:35:24.749> roll-up<01:35:25.309> it 01:35:26.299 --> 01:35:26.309 align:start position:0% clicker oh cool so what is roll-up it 01:35:26.309 --> 01:35:28.970 align:start position:0% clicker oh cool so what is roll-up it leverages<01:35:26.849> CPS<01:35:27.840> night<01:35:28.019> crews<01:35:28.349> to<01:35:28.710> batch 01:35:28.970 --> 01:35:28.980 align:start position:0% leverages CPS night crews to batch 01:35:28.980 --> 01:35:31.850 align:start position:0% leverages CPS night crews to batch transactions<01:35:29.940> off<01:35:30.119> chain<01:35:30.599> and<01:35:30.929> provide 01:35:31.850 --> 01:35:31.860 align:start position:0% transactions off chain and provide 01:35:31.860 --> 01:35:36.439 align:start position:0% transactions off chain and provide succinct<01:35:32.460> ruse<01:35:32.639> on<01:35:32.880> chain<01:35:34.519> like<01:35:35.519> many<01:35:35.820> quote 01:35:36.439 --> 01:35:36.449 align:start position:0% succinct ruse on chain like many quote 01:35:36.449 --> 01:35:39.680 align:start position:0% succinct ruse on chain like many quote unquote<01:35:36.539> LT<01:35:37.050> solutions<01:35:37.619> there<01:35:38.579> are<01:35:38.690> operators 01:35:39.680 --> 01:35:39.690 align:start position:0% unquote LT solutions there are operators 01:35:39.690 --> 01:35:41.540 align:start position:0% unquote LT solutions there are operators and<01:35:40.139> verifiers<01:35:40.679> operators<01:35:41.400> take 01:35:41.540 --> 01:35:41.550 align:start position:0% and verifiers operators take 01:35:41.550 --> 01:35:44.930 align:start position:0% and verifiers operators take transactions<01:35:42.239> off<01:35:42.420> chain<01:35:43.039> and<01:35:44.039> bash<01:35:44.670> them 01:35:44.930 --> 01:35:44.940 align:start position:0% transactions off chain and bash them 01:35:44.940 --> 01:35:46.819 align:start position:0% transactions off chain and bash them into<01:35:45.150> proofs<01:35:45.420> which<01:35:45.690> are<01:35:45.929> then<01:35:46.110> submitted<01:35:46.619> on 01:35:46.819 --> 01:35:46.829 align:start position:0% into proofs which are then submitted on 01:35:46.829 --> 01:35:50.330 align:start position:0% into proofs which are then submitted on chain<01:35:47.130> and<01:35:47.369> verified<01:35:48.050> so<01:35:49.159> zero<01:35:50.159> knowledge 01:35:50.330 --> 01:35:50.340 align:start position:0% chain and verified so zero knowledge 01:35:50.340 --> 01:35:54.169 align:start position:0% chain and verified so zero knowledge proof<01:35:50.780> our<01:35:51.780> constant<01:35:52.559> sized<01:35:53.090> verified<01:35:54.090> in 01:35:54.169 --> 01:35:54.179 align:start position:0% proof our constant sized verified in 01:35:54.179 --> 01:35:58.700 align:start position:0% proof our constant sized verified in constant<01:35:54.659> time<01:35:54.920> assuming<01:35:56.300> the<01:35:57.300> yes<01:35:58.260> verifying 01:35:58.700 --> 01:35:58.710 align:start position:0% constant time assuming the yes verifying 01:35:58.710 --> 01:36:00.890 align:start position:0% constant time assuming the yes verifying constant<01:35:59.159> time<01:35:59.309> for<01:35:59.340> a<01:35:59.579> given<01:35:59.820> circuit<01:36:00.239> and 01:36:00.890 --> 01:36:00.900 align:start position:0% constant time for a given circuit and 01:36:00.900 --> 01:36:04.069 align:start position:0% constant time for a given circuit and for<01:36:01.590> roll-up<01:36:02.099> this<01:36:02.489> means<01:36:03.059> that<01:36:03.449> groups<01:36:03.869> can 01:36:04.069 --> 01:36:04.079 align:start position:0% for roll-up this means that groups can 01:36:04.079 --> 01:36:05.870 align:start position:0% for roll-up this means that groups can be<01:36:04.110> verified<01:36:04.380> regardless<01:36:05.340> of<01:36:05.489> the<01:36:05.579> number<01:36:05.820> of 01:36:05.870 --> 01:36:05.880 align:start position:0% be verified regardless of the number of 01:36:05.880 --> 01:36:11.029 align:start position:0% be verified regardless of the number of transactions<01:36:06.510> that<01:36:07.469> are<01:36:07.530> matched<01:36:09.769> right<01:36:10.769> and 01:36:11.029 --> 01:36:11.039 align:start position:0% transactions that are matched right and 01:36:11.039 --> 01:36:14.959 align:start position:0% transactions that are matched right and so<01:36:11.219> scalability<01:36:11.940> is<01:36:12.869> mainly<01:36:13.650> constrained<01:36:14.639> by 01:36:14.959 --> 01:36:14.969 align:start position:0% so scalability is mainly constrained by 01:36:14.969 --> 01:36:21.560 align:start position:0% so scalability is mainly constrained by the<01:36:15.079> on<01:36:16.079> the<01:36:16.230> proving<01:36:16.559> side<01:36:17.929> and<01:36:20.150> yeah<01:36:21.150> so<01:36:21.389> I 01:36:21.560 --> 01:36:21.570 align:start position:0% the on the proving side and yeah so I 01:36:21.570 --> 01:36:24.560 align:start position:0% the on the proving side and yeah so I think<01:36:21.630> we've<01:36:21.869> had<01:36:21.989> a<01:36:22.050> few<01:36:22.769> existing<01:36:23.570> roll-up 01:36:24.560 --> 01:36:24.570 align:start position:0% think we've had a few existing roll-up 01:36:24.570 --> 01:36:27.350 align:start position:0% think we've had a few existing roll-up systems<01:36:25.019> that<01:36:25.650> have<01:36:25.889> been<01:36:25.920> advertised<01:36:26.519> to 01:36:27.350 --> 01:36:27.360 align:start position:0% systems that have been advertised to 01:36:27.360 --> 01:36:29.089 align:start position:0% systems that have been advertised to provide<01:36:27.659> like<01:36:28.079> somewhat<01:36:28.590> in<01:36:28.710> the<01:36:28.800> order<01:36:29.070> of 01:36:29.089 --> 01:36:29.099 align:start position:0% provide like somewhat in the order of 01:36:29.099 --> 01:36:32.239 align:start position:0% provide like somewhat in the order of one<01:36:29.460> to<01:36:29.730> two<01:36:30.090> magnitudes<01:36:30.570> of<01:36:31.249> transaction 01:36:32.239 --> 01:36:32.249 align:start position:0% one to two magnitudes of transaction 01:36:32.249 --> 01:36:41.259 align:start position:0% one to two magnitudes of transaction through<01:36:32.460> put<01:36:32.719> on<01:36:33.719> the<01:36:33.929> EVM<01:36:34.260> today<01:36:38.150> right<01:36:39.440> so 01:36:41.259 --> 01:36:41.269 align:start position:0% through put on the EVM today right so 01:36:41.269 --> 01:36:43.819 align:start position:0% through put on the EVM today right so why<01:36:42.269> this<01:36:43.110> role<01:36:43.380> of<01:36:43.469> an<01:36:43.590> interesting 01:36:43.819 --> 01:36:43.829 align:start position:0% why this role of an interesting 01:36:43.829 --> 01:36:46.310 align:start position:0% why this role of an interesting application<01:36:44.340> for<01:36:44.969> you<01:36:45.059> two 01:36:46.310 --> 01:36:46.320 align:start position:0% application for you two 01:36:46.320 --> 01:36:49.640 align:start position:0% application for you two well<01:36:47.659> the<01:36:48.659> data<01:36:48.840> availability<01:36:49.320> requirements 01:36:49.640 --> 01:36:49.650 align:start position:0% well the data availability requirements 01:36:49.650 --> 01:36:56.239 align:start position:0% well the data availability requirements are<01:36:51.889> somewhat<01:36:52.889> lower<01:36:53.130> than<01:36:53.550> say<01:36:54.239> the<01:36:54.780> other<01:36:55.650> on 01:36:56.239 --> 01:36:56.249 align:start position:0% are somewhat lower than say the other on 01:36:56.249 --> 01:36:57.180 align:start position:0% are somewhat lower than say the other on chain 01:36:57.180 --> 01:36:57.190 align:start position:0% chain 01:36:57.190 --> 01:36:59.370 align:start position:0% chain like<01:36:57.760> if<01:36:58.030> we're<01:36:58.570> talking<01:36:58.780> about<01:36:58.870> verifying 01:36:59.370 --> 01:36:59.380 align:start position:0% like if we're talking about verifying 01:36:59.380 --> 01:37:01.490 align:start position:0% like if we're talking about verifying multi<01:36:59.710> proof<01:36:59.920> some<01:37:00.130> change<01:37:00.430> well<01:37:00.670> this<01:37:00.850> is<01:37:01.000> a 01:37:01.490 --> 01:37:01.500 align:start position:0% multi proof some change well this is a 01:37:01.500 --> 01:37:04.830 align:start position:0% multi proof some change well this is a this<01:37:02.500> is<01:37:02.640> similar<01:37:03.640> to<01:37:04.060> what<01:37:04.720> is<01:37:04.810> happening 01:37:04.830 --> 01:37:04.840 align:start position:0% this is similar to what is happening 01:37:04.840 --> 01:37:07.500 align:start position:0% this is similar to what is happening with<01:37:05.590> rola<01:37:05.860> but<01:37:06.250> the<01:37:06.400> data<01:37:06.610> ability<01:37:07.060> veil 01:37:07.500 --> 01:37:07.510 align:start position:0% with rola but the data ability veil 01:37:07.510 --> 01:37:09.170 align:start position:0% with rola but the data ability veil ability<01:37:07.900> requirement<01:37:08.380> starting<01:37:08.680> to<01:37:08.740> be<01:37:08.830> lower 01:37:09.170 --> 01:37:09.180 align:start position:0% ability requirement starting to be lower 01:37:09.180 --> 01:37:14.550 align:start position:0% ability requirement starting to be lower with<01:37:10.180> rollers<01:37:12.420> there<01:37:13.420> are<01:37:13.510> no<01:37:13.630> exit<01:37:14.350> games 01:37:14.550 --> 01:37:14.560 align:start position:0% with rollers there are no exit games 01:37:14.560 --> 01:37:19.440 align:start position:0% with rollers there are no exit games lock-up<01:37:15.160> periods<01:37:16.650> basically<01:37:17.940> your<01:37:18.940> funds<01:37:19.270> can 01:37:19.440 --> 01:37:19.450 align:start position:0% lock-up periods basically your funds can 01:37:19.450 --> 01:37:22.530 align:start position:0% lock-up periods basically your funds can only<01:37:19.570> be<01:37:19.750> spent<01:37:20.050> if<01:37:20.260> you<01:37:20.530> if<01:37:21.160> that<01:37:22.150> operator 01:37:22.530 --> 01:37:22.540 align:start position:0% only be spent if you if that operator 01:37:22.540 --> 01:37:23.940 align:start position:0% only be spent if you if that operator can<01:37:22.720> only<01:37:22.840> spend<01:37:23.110> your<01:37:23.230> funds<01:37:23.440> if<01:37:23.680> they<01:37:23.800> have 01:37:23.940 --> 01:37:23.950 align:start position:0% can only spend your funds if they have 01:37:23.950 --> 01:37:28.230 align:start position:0% can only spend your funds if they have your<01:37:24.070> private<01:37:24.400> keys<01:37:25.920> so<01:37:26.920> we've<01:37:27.700> been<01:37:27.850> using<01:37:28.060> a 01:37:28.230 --> 01:37:28.240 align:start position:0% your private keys so we've been using a 01:37:28.240 --> 01:37:31.230 align:start position:0% your private keys so we've been using a web<01:37:28.690> snark<01:37:29.020> which<01:37:29.290> uh<01:37:29.320> I<01:37:29.860> think<01:37:30.280> jority<01:37:30.910> this 01:37:31.230 --> 01:37:31.240 align:start position:0% web snark which uh I think jority this 01:37:31.240 --> 01:37:35.100 align:start position:0% web snark which uh I think jority this is<01:37:31.360> your<01:37:31.510> tool<01:37:31.690> thank<01:37:31.990> you<01:37:33.360> so<01:37:34.360> written 01:37:35.100 --> 01:37:35.110 align:start position:0% is your tool thank you so written 01:37:35.110 --> 01:37:40.190 align:start position:0% is your tool thank you so written written<01:37:35.500> in<01:37:36.610> and<01:37:37.600> we've<01:37:38.020> been<01:37:38.170> able<01:37:38.350> to 01:37:40.190 --> 01:37:40.200 align:start position:0% written in and we've been able to 01:37:40.200 --> 01:37:42.480 align:start position:0% written in and we've been able to generate<01:37:41.200> it<01:37:41.560> wasn't<01:37:41.890> generated<01:37:42.340> from 01:37:42.480 --> 01:37:42.490 align:start position:0% generate it wasn't generated from 01:37:42.490 --> 01:37:47.910 align:start position:0% generate it wasn't generated from handwritten<01:37:43.420> text<01:37:43.690> format<01:37:44.110> but<01:37:45.390> right<01:37:46.530> so<01:37:47.530> if 01:37:47.910 --> 01:37:47.920 align:start position:0% handwritten text format but right so if 01:37:47.920 --> 01:37:53.580 align:start position:0% handwritten text format but right so if we<01:37:48.160> look<01:37:48.310> up<01:37:48.460> look<01:37:49.000> at<01:37:49.200> some<01:37:50.940> benchmarks<01:37:52.590> we 01:37:53.580 --> 01:37:53.590 align:start position:0% we look up look at some benchmarks we 01:37:53.590 --> 01:37:55.950 align:start position:0% we look up look at some benchmarks we can<01:37:53.740> actually<01:37:53.860> see<01:37:54.190> that<01:37:54.450> if<01:37:55.450> you<01:37:55.600> look<01:37:55.660> on<01:37:55.870> the 01:37:55.950 --> 01:37:55.960 align:start position:0% can actually see that if you look on the 01:37:55.960 --> 01:37:58.860 align:start position:0% can actually see that if you look on the Left<01:37:56.200> Russ<01:37:57.010> native<01:37:57.430> and<01:37:57.700> this<01:37:57.820> is<01:37:57.940> for<01:37:58.210> a<01:37:58.510> two 01:37:58.860 --> 01:37:58.870 align:start position:0% Left Russ native and this is for a two 01:37:58.870 --> 01:38:03.330 align:start position:0% Left Russ native and this is for a two point<01:37:59.110> peri<01:37:59.350> check<01:38:00.030> Russ<01:38:01.030> native<01:38:01.450> is<01:38:02.340> actually 01:38:03.330 --> 01:38:03.340 align:start position:0% point peri check Russ native is actually 01:38:03.340 --> 01:38:05.670 align:start position:0% point peri check Russ native is actually very<01:38:03.490> comparable<01:38:03.910> to<01:38:04.330> an<01:38:04.690> interpreter 01:38:05.670 --> 01:38:05.680 align:start position:0% very comparable to an interpreter 01:38:05.680 --> 01:38:08.550 align:start position:0% very comparable to an interpreter assuming<01:38:06.370> that<01:38:06.400> we<01:38:06.550> shim<01:38:07.000> in<01:38:07.270> debating<01:38:07.870> on<01:38:08.050> big 01:38:08.550 --> 01:38:08.560 align:start position:0% assuming that we shim in debating on big 01:38:08.560 --> 01:38:12.380 align:start position:0% assuming that we shim in debating on big number<01:38:08.860> of<01:38:08.920> operations<01:38:09.460> as<01:38:10.920> natively 01:38:12.380 --> 01:38:12.390 align:start position:0% number of operations as natively 01:38:12.390 --> 01:38:21.390 align:start position:0% number of operations as natively as<01:38:13.390> host<01:38:13.750> functions<01:38:14.580> and<01:38:19.350> okay<01:38:20.350> so<01:38:20.890> I'll<01:38:21.220> just 01:38:21.390 --> 01:38:21.400 align:start position:0% as host functions and okay so I'll just 01:38:21.400 --> 01:38:24.510 align:start position:0% as host functions and okay so I'll just go<01:38:21.520> from<01:38:21.730> left<01:38:21.940> to<01:38:22.030> right<01:38:22.380> Russ<01:38:23.380> native<01:38:23.800> four 01:38:24.510 --> 01:38:24.520 align:start position:0% go from left to right Russ native four 01:38:24.520 --> 01:38:28.470 align:start position:0% go from left to right Russ native four point<01:38:24.700> two<01:38:24.820> milliseconds<01:38:26.340> Bobbitt 01:38:28.470 --> 01:38:28.480 align:start position:0% point two milliseconds Bobbitt 01:38:28.480 --> 01:38:31.200 align:start position:0% point two milliseconds Bobbitt five<01:38:29.110> point<01:38:29.350> seven<01:38:29.500> milliseconds<01:38:30.190> v8<01:38:30.790> turbo 01:38:31.200 --> 01:38:31.210 align:start position:0% five point seven milliseconds v8 turbo 01:38:31.210 --> 01:38:33.540 align:start position:0% five point seven milliseconds v8 turbo fan<01:38:31.450> seven<01:38:32.140> point<01:38:32.320> five<01:38:32.470> milliseconds<01:38:33.220> v8 01:38:33.540 --> 01:38:33.550 align:start position:0% fan seven point five milliseconds v8 01:38:33.550 --> 01:38:38.130 align:start position:0% fan seven point five milliseconds v8 lift<01:38:33.760> up<01:38:34.000> and<01:38:34.210> these<01:38:34.270> are<01:38:35.670> compilers<01:38:36.670> here<01:38:37.140> he 01:38:38.130 --> 01:38:38.140 align:start position:0% lift up and these are compilers here he 01:38:38.140 --> 01:38:41.370 align:start position:0% lift up and these are compilers here he is<01:38:38.500> is<01:38:39.310> going<01:38:39.520> to<01:38:39.580> be<01:38:39.670> 12<01:38:39.910> milliseconds<01:38:40.570> and 01:38:41.370 --> 01:38:41.380 align:start position:0% is is going to be 12 milliseconds and 01:38:41.380 --> 01:38:44.130 align:start position:0% is is going to be 12 milliseconds and then<01:38:41.590> if<01:38:41.680> we<01:38:41.800> look<01:38:41.980> at<01:38:42.190> eater<01:38:42.670> pra's<01:38:43.140> vomit 01:38:44.130 --> 01:38:44.140 align:start position:0% then if we look at eater pra's vomit 01:38:44.140 --> 01:38:45.990 align:start position:0% then if we look at eater pra's vomit shoots<01:38:44.890> up<01:38:45.070> to<01:38:45.190> two<01:38:45.340> hundred<01:38:45.640> thirty<01:38:45.820> six 01:38:45.990 --> 01:38:46.000 align:start position:0% shoots up to two hundred thirty six 01:38:46.000 --> 01:38:54.480 align:start position:0% shoots up to two hundred thirty six milliseconds<01:38:46.720> and<01:38:47.020> v8<01:38:47.680> is<01:38:47.980> at<01:38:49.200> 733<01:38:52.920> right<01:38:53.920> so<01:38:54.280> I 01:38:54.480 --> 01:38:54.490 align:start position:0% milliseconds and v8 is at 733 right so I 01:38:54.490 --> 01:38:57.270 align:start position:0% milliseconds and v8 is at 733 right so I mean<01:38:54.640> kind<01:38:55.570> of<01:38:55.690> the<01:38:55.930> point<01:38:56.560> of<01:38:56.770> this<01:38:56.860> talk<01:38:57.100> and 01:38:57.270 --> 01:38:57.280 align:start position:0% mean kind of the point of this talk and 01:38:57.280 --> 01:39:00.030 align:start position:0% mean kind of the point of this talk and I<01:38:57.340> don't<01:38:57.370> have<01:38:58.330> numbers<01:38:58.750> currently 01:39:00.030 --> 01:39:00.040 align:start position:0% I don't have numbers currently 01:39:00.040 --> 01:39:01.950 align:start position:0% I don't have numbers currently we're<01:39:00.340> able<01:39:00.670> to<01:39:00.880> generate<01:39:01.180> the<01:39:01.300> charts<01:39:01.690> in 01:39:01.950 --> 01:39:01.960 align:start position:0% we're able to generate the charts in 01:39:01.960 --> 01:39:06.330 align:start position:0% we're able to generate the charts in time<01:39:02.950> but<01:39:03.420> I<01:39:04.420> can<01:39:04.930> I'll<01:39:05.170> just<01:39:05.410> have<01:39:05.980> you<01:39:06.010> take 01:39:06.330 --> 01:39:06.340 align:start position:0% time but I can I'll just have you take 01:39:06.340 --> 01:39:08.700 align:start position:0% time but I can I'll just have you take my<01:39:06.490> word<01:39:06.700> that<01:39:06.730> Russ<01:39:07.690> compiled<01:39:08.140> laws<01:39:08.470> in 01:39:08.700 --> 01:39:08.710 align:start position:0% my word that Russ compiled laws in 01:39:08.710 --> 01:39:12.680 align:start position:0% my word that Russ compiled laws in general<01:39:09.010> is<01:39:09.550> a<01:39:09.940> lot<01:39:10.420> slower<01:39:10.750> than<01:39:11.490> these 01:39:12.680 --> 01:39:12.690 align:start position:0% general is a lot slower than these 01:39:12.690 --> 01:39:15.920 align:start position:0% general is a lot slower than these optimized<01:39:13.690> handwritten 01:39:15.920 --> 01:39:15.930 align:start position:0% optimized handwritten 01:39:15.930 --> 01:39:19.590 align:start position:0% optimized handwritten wazzle<01:39:16.930> binaries<01:39:17.490> and<01:39:18.490> so<01:39:19.240> it<01:39:19.360> kind<01:39:19.570> of 01:39:19.590 --> 01:39:19.600 align:start position:0% wazzle binaries and so it kind of 01:39:19.600 --> 01:39:22.680 align:start position:0% wazzle binaries and so it kind of illustrates<01:39:20.020> a<01:39:20.440> point<01:39:20.620> that<01:39:21.300> perhaps<01:39:22.300> e 01:39:22.680 --> 01:39:22.690 align:start position:0% illustrates a point that perhaps e 01:39:22.690 --> 01:39:26.550 align:start position:0% illustrates a point that perhaps e development<01:39:23.500> is<01:39:23.650> going<01:39:23.890> to<01:39:23.980> need<01:39:25.560> specialized 01:39:26.550 --> 01:39:26.560 align:start position:0% development is going to need specialized 01:39:26.560 --> 01:39:30.090 align:start position:0% development is going to need specialized in<01:39:26.800> the<01:39:26.860> sense<01:39:27.100> that<01:39:27.190> DAP<01:39:27.790> developers<01:39:28.530> the<01:39:29.530> set 01:39:30.090 --> 01:39:30.100 align:start position:0% in the sense that DAP developers the set 01:39:30.100 --> 01:39:33.150 align:start position:0% in the sense that DAP developers the set of<01:39:30.220> tool<01:39:30.430> sets<01:39:30.730> for<01:39:31.510> the<01:39:32.020> the<01:39:32.680> set<01:39:32.860> of<01:39:32.950> skill 01:39:33.150 --> 01:39:33.160 align:start position:0% of tool sets for the the set of skill 01:39:33.160 --> 01:39:35.070 align:start position:0% of tool sets for the the set of skill sets<01:39:33.430> for<01:39:33.640> GAF<01:39:33.850> developers<01:39:34.450> versus<01:39:34.870> EE 01:39:35.070 --> 01:39:35.080 align:start position:0% sets for GAF developers versus EE 01:39:35.080 --> 01:39:38.420 align:start position:0% sets for GAF developers versus EE developers<01:39:35.350> is<01:39:35.890> going<01:39:36.010> to<01:39:36.070> be<01:39:36.160> akin<01:39:36.490> to 01:39:38.420 --> 01:39:38.430 align:start position:0% developers is going to be akin to 01:39:38.430 --> 01:39:40.800 align:start position:0% developers is going to be akin to protocol<01:39:39.430> developers<01:39:39.850> versus<01:39:40.180> not<01:39:40.360> protocol 01:39:40.800 --> 01:39:40.810 align:start position:0% protocol developers versus not protocol 01:39:40.810 --> 01:39:41.910 align:start position:0% protocol developers versus not protocol developers<01:39:41.260> and<01:39:41.500> it's<01:39:41.590> gonna<01:39:41.680> require 01:39:41.910 --> 01:39:41.920 align:start position:0% developers and it's gonna require 01:39:41.920 --> 01:39:45.420 align:start position:0% developers and it's gonna require perhaps<01:39:42.790> a<01:39:43.260> specialized<01:39:44.260> skill<01:39:44.560> set<01:39:44.890> in<01:39:45.160> both 01:39:45.420 --> 01:39:45.430 align:start position:0% perhaps a specialized skill set in both 01:39:45.430 --> 01:39:49.200 align:start position:0% perhaps a specialized skill set in both maybe<01:39:45.940> cryptography<01:39:46.690> and<01:39:48.180> understanding<01:39:49.180> of 01:39:49.200 --> 01:39:49.210 align:start position:0% maybe cryptography and understanding of 01:39:49.210 --> 01:39:52.470 align:start position:0% maybe cryptography and understanding of what<01:39:49.300> assembly<01:39:49.870> but<01:39:50.500> to<01:39:50.680> really<01:39:51.240> squeeze<01:39:52.240> as 01:39:52.470 --> 01:39:52.480 align:start position:0% what assembly but to really squeeze as 01:39:52.480 --> 01:39:55.380 align:start position:0% what assembly but to really squeeze as much<01:39:52.600> juice<01:39:52.960> out<01:39:53.350> of<01:39:53.410> these<01:39:54.390> execution 01:39:55.380 --> 01:39:55.390 align:start position:0% much juice out of these execution 01:39:55.390 --> 01:39:57.210 align:start position:0% much juice out of these execution environment<01:39:55.870> execution<01:39:56.680> engines<01:39:57.040> as 01:39:57.210 --> 01:39:57.220 align:start position:0% environment execution engines as 01:39:57.220 --> 01:40:02.610 align:start position:0% environment execution engines as possible<01:39:57.760> to<01:39:58.600> get<01:40:00.060> the<01:40:01.060> performance<01:40:01.390> that<01:40:01.870> we 01:40:02.610 --> 01:40:02.620 align:start position:0% possible to get the performance that we 01:40:02.620 --> 01:40:06.000 align:start position:0% possible to get the performance that we want<01:40:02.860> that<01:40:02.950> we<01:40:03.100> want<01:40:03.220> a<01:40:03.490> need<01:40:03.670> for<01:40:03.970> e<01:40:04.150> to<01:40:04.800> so<01:40:05.800> we 01:40:06.000 --> 01:40:06.010 align:start position:0% want that we want a need for e to so we 01:40:06.010 --> 01:40:11.550 align:start position:0% want that we want a need for e to so we got<01:40:06.160> that<01:40:06.340> um<01:40:07.380> that's<01:40:08.380> my<01:40:08.620> talk<01:40:10.410> thanks<01:40:11.410> for 01:40:11.550 --> 01:40:11.560 align:start position:0% got that um that's my talk thanks for 01:40:11.560 --> 01:40:12.920 align:start position:0% got that um that's my talk thanks for coming 01:40:12.920 --> 01:40:12.930 align:start position:0% coming 01:40:12.930 --> 01:40:14.760 align:start position:0% coming and<01:40:13.930> I<01:40:13.990> think<01:40:14.170> I'm<01:40:14.260> gonna<01:40:14.350> hand<01:40:14.560> it<01:40:14.650> off<01:40:14.710> to 01:40:14.760 --> 01:40:14.770 align:start position:0% and I think I'm gonna hand it off to 01:40:14.770 --> 01:40:21.350 align:start position:0% and I think I'm gonna hand it off to will 01:40:21.350 --> 01:40:21.360 align:start position:0% 01:40:21.360 --> 01:40:23.990 align:start position:0% and<01:40:22.360> while<01:40:22.540> I'm<01:40:22.659> studying<01:40:22.869> I'm<01:40:23.050> talking<01:40:23.380> about 01:40:23.990 --> 01:40:24.000 align:start position:0% and while I'm studying I'm talking about 01:40:24.000 --> 01:40:29.549 align:start position:0% and while I'm studying I'm talking about the<01:40:25.000> session<01:40:26.429> tomorrow<01:40:27.630> and<01:40:28.630> I'll<01:40:29.079> dive<01:40:29.530> into 01:40:29.549 --> 01:40:29.559 align:start position:0% the session tomorrow and I'll dive into 01:40:29.559 --> 01:40:33.870 align:start position:0% the session tomorrow and I'll dive into a<01:40:30.340> quick<01:40:31.710> 10<01:40:32.710> minute<01:40:32.739> demo<01:40:33.070> and<01:40:33.309> explain<01:40:33.670> what 01:40:33.870 --> 01:40:33.880 align:start position:0% a quick 10 minute demo and explain what 01:40:33.880 --> 01:40:36.299 align:start position:0% a quick 10 minute demo and explain what we're<01:40:34.119> trying<01:40:34.630> to<01:40:34.750> do<01:40:34.929> by<01:40:35.469> simulating<01:40:35.980> crush 01:40:36.299 --> 01:40:36.309 align:start position:0% we're trying to do by simulating crush 01:40:36.309 --> 01:40:39.870 align:start position:0% we're trying to do by simulating crush our<01:40:36.520> behaviors<01:40:36.969> already<01:40:38.309> which<01:40:39.309> we<01:40:39.579> kind<01:40:39.760> of 01:40:39.870 --> 01:40:39.880 align:start position:0% our behaviors already which we kind of 01:40:39.880 --> 01:40:41.870 align:start position:0% our behaviors already which we kind of circle<01:40:40.540> back<01:40:40.690> around<01:40:40.929> the<01:40:41.139> nature<01:40:41.380> attack 01:40:41.870 --> 01:40:41.880 align:start position:0% circle back around the nature attack 01:40:41.880 --> 01:40:47.189 align:start position:0% circle back around the nature attack real<01:40:42.880> quick<01:40:43.119> I<01:40:45.630> just<01:40:46.630> wanted<01:40:47.020> to<01:40:47.110> mention 01:40:47.189 --> 01:40:47.199 align:start position:0% real quick I just wanted to mention 01:40:47.199 --> 01:40:49.140 align:start position:0% real quick I just wanted to mention these<01:40:47.530> two<01:40:47.590> sessions<01:40:48.550> tomorrow 01:40:49.140 --> 01:40:49.150 align:start position:0% these two sessions tomorrow 01:40:49.150 --> 01:40:53.939 align:start position:0% these two sessions tomorrow the<01:40:49.659> kiss<01:40:49.869> you<01:40:49.989> guys<01:40:50.579> expertise<01:40:52.770> so<01:40:53.770> in<01:40:53.889> the 01:40:53.939 --> 01:40:53.949 align:start position:0% the kiss you guys expertise so in the 01:40:53.949 --> 01:40:57.240 align:start position:0% the kiss you guys expertise so in the morning<01:40:54.280> at<01:40:54.699> 9:10<01:40:55.270> mp8<01:40:55.840> justice<01:40:56.679> two<01:40:56.949> hours 01:40:57.240 --> 01:40:57.250 align:start position:0% morning at 9:10 mp8 justice two hours 01:40:57.250 --> 01:40:59.640 align:start position:0% morning at 9:10 mp8 justice two hours long<01:40:57.520> tinted<01:40:58.360> window<01:40:58.570> fix<01:40:58.809> one<01:40:59.020> and<01:40:59.320> two<01:40:59.500> the 01:40:59.640 --> 01:40:59.650 align:start position:0% long tinted window fix one and two the 01:40:59.650 --> 01:41:02.459 align:start position:0% long tinted window fix one and two the developer<01:41:00.070> experience<01:41:00.270> I<01:41:01.270> think<01:41:02.230> it's<01:41:02.349> gonna 01:41:02.459 --> 01:41:02.469 align:start position:0% developer experience I think it's gonna 01:41:02.469 --> 01:41:03.990 align:start position:0% developer experience I think it's gonna be<01:41:02.619> a<01:41:02.650> real<01:41:02.770> good<01:41:02.800> session<01:41:03.219> so<01:41:03.489> if<01:41:03.639> you<01:41:03.790> are 01:41:03.990 --> 01:41:04.000 align:start position:0% be a real good session so if you are 01:41:04.000 --> 01:41:06.270 align:start position:0% be a real good session so if you are interested<01:41:04.389> in<01:41:04.719> ease<01:41:04.960> and<01:41:05.260> how<01:41:06.070> does<01:41:06.219> the 01:41:06.270 --> 01:41:06.280 align:start position:0% interested in ease and how does the 01:41:06.280 --> 01:41:07.979 align:start position:0% interested in ease and how does the network<01:41:06.520> you<01:41:06.639> should<01:41:06.670> show<01:41:06.940> up<01:41:07.059> there's<01:41:07.869> an 01:41:07.979 --> 01:41:07.989 align:start position:0% network you should show up there's an 01:41:07.989 --> 01:41:10.530 align:start position:0% network you should show up there's an every<01:41:08.170> woman<01:41:08.409> as<01:41:08.619> 12<01:41:09.239> v8 01:41:10.530 --> 01:41:10.540 align:start position:0% every woman as 12 v8 01:41:10.540 --> 01:41:13.770 align:start position:0% every woman as 12 v8 so<01:41:10.960> it's<01:41:11.170> just<01:41:11.440> forests<01:41:11.829> felt<01:41:12.239> even<01:41:13.239> hour-long 01:41:13.770 --> 01:41:13.780 align:start position:0% so it's just forests felt even hour-long 01:41:13.780 --> 01:41:15.629 align:start position:0% so it's just forests felt even hour-long medieval<01:41:14.650> execution<01:41:15.130> anyway<01:41:15.369> so<01:41:15.429> basically 01:41:15.629 --> 01:41:15.639 align:start position:0% medieval execution anyway so basically 01:41:15.639 --> 01:41:18.439 align:start position:0% medieval execution anyway so basically it's<01:41:16.150> gonna<01:41:16.270> be<01:41:16.449> kind<01:41:17.050> of<01:41:17.110> a<01:41:17.290> flexible<01:41:17.829> panel 01:41:18.439 --> 01:41:18.449 align:start position:0% it's gonna be kind of a flexible panel 01:41:18.449 --> 01:41:21.030 align:start position:0% it's gonna be kind of a flexible panel about<01:41:19.449> the<01:41:19.540> work<01:41:19.750> which<01:41:19.989> was<01:41:20.290> showcase<01:41:20.710> here 01:41:21.030 --> 01:41:21.040 align:start position:0% about the work which was showcase here 01:41:21.040 --> 01:41:25.560 align:start position:0% about the work which was showcase here and<01:41:21.929> it's<01:41:22.929> but<01:41:23.110> also<01:41:23.290> consist<01:41:23.739> of<01:41:24.239> each<01:41:25.239> other 01:41:25.560 --> 01:41:25.570 align:start position:0% and it's but also consist of each other 01:41:25.570 --> 01:41:27.390 align:start position:0% and it's but also consist of each other find<01:41:26.380> the<01:41:26.500> other<01:41:26.650> person<01:41:27.040> and<01:41:27.190> some 01:41:27.390 --> 01:41:27.400 align:start position:0% find the other person and some 01:41:27.400 --> 01:41:30.089 align:start position:0% find the other person and some researchers<01:41:28.059> so<01:41:28.780> it's<01:41:28.900> gonna<01:41:29.230> be<01:41:29.380> a<01:41:29.409> place<01:41:29.920> to 01:41:30.089 --> 01:41:30.099 align:start position:0% researchers so it's gonna be a place to 01:41:30.099 --> 01:41:32.069 align:start position:0% researchers so it's gonna be a place to ask<01:41:30.250> questions<01:41:30.340> and<01:41:30.909> discuss<01:41:31.480> this<01:41:31.659> more<01:41:32.050> in 01:41:32.069 --> 01:41:32.079 align:start position:0% ask questions and discuss this more in 01:41:32.079 --> 01:41:37.879 align:start position:0% ask questions and discuss this more in depth<01:41:32.489> so<01:41:33.489> will<01:41:33.670> please<01:41:33.969> go<01:41:34.420> ahead<01:41:35.790> cool<01:41:36.820> also 01:41:37.879 --> 01:41:37.889 align:start position:0% depth so will please go ahead cool also 01:41:37.889 --> 01:41:42.680 align:start position:0% depth so will please go ahead cool also yeah<01:41:39.300> I'll<01:41:40.300> be<01:41:40.449> giving<01:41:40.750> a<01:41:40.980> quick<01:41:41.980> 10<01:41:42.520> minute 01:41:42.680 --> 01:41:42.690 align:start position:0% yeah I'll be giving a quick 10 minute 01:41:42.690 --> 01:41:44.969 align:start position:0% yeah I'll be giving a quick 10 minute overview<01:41:43.690> ovaries 01:41:44.969 --> 01:41:44.979 align:start position:0% overview ovaries 01:41:44.979 --> 01:41:53.640 align:start position:0% overview ovaries well<01:41:46.050> okay<01:41:47.050> so<01:41:50.550> um<01:41:51.840> so<01:41:52.840> I<01:41:52.869> think<01:41:52.929> like<01:41:53.260> just<01:41:53.499> to 01:41:53.640 --> 01:41:53.650 align:start position:0% well okay so um so I think like just to 01:41:53.650 --> 01:41:57.629 align:start position:0% well okay so um so I think like just to summarize<01:41:54.010> everything<01:41:55.170> we've<01:41:56.170> seen<01:41:56.380> it<01:41:56.639> tied 01:41:57.629 --> 01:41:57.639 align:start position:0% summarize everything we've seen it tied 01:41:57.639 --> 01:42:01.709 align:start position:0% summarize everything we've seen it tied into<01:41:57.849> this<01:41:59.099> I<01:42:00.119> mean<01:42:01.119> what<01:42:01.269> we're<01:42:01.389> seeing<01:42:01.599> from 01:42:01.709 --> 01:42:01.719 align:start position:0% into this I mean what we're seeing from 01:42:01.719 --> 01:42:04.830 align:start position:0% into this I mean what we're seeing from early<01:42:02.110> perspective<01:42:02.709> is<01:42:02.920> that<01:42:03.570> you<01:42:04.570> know<01:42:04.659> we 01:42:04.830 --> 01:42:04.840 align:start position:0% early perspective is that you know we 01:42:04.840 --> 01:42:09.540 align:start position:0% early perspective is that you know we can<01:42:05.289> build<01:42:06.209> these<01:42:07.209> V's<01:42:07.690> in<01:42:08.079> a<01:42:08.920> stateless<01:42:09.340> way 01:42:09.540 --> 01:42:09.550 align:start position:0% can build these V's in a stateless way 01:42:09.550 --> 01:42:13.379 align:start position:0% can build these V's in a stateless way that's<01:42:09.820> performing<01:42:10.360> enough<01:42:12.150> 3/2<01:42:13.150> that's 01:42:13.379 --> 01:42:13.389 align:start position:0% that's performing enough 3/2 that's 01:42:13.389 --> 01:42:15.959 align:start position:0% that's performing enough 3/2 that's that's<01:42:13.840> pretty<01:42:14.050> cool<01:42:14.289> and<01:42:14.679> so<01:42:15.249> what<01:42:15.639> we<01:42:15.760> talked 01:42:15.959 --> 01:42:15.969 align:start position:0% that's pretty cool and so what we talked 01:42:15.969 --> 01:42:19.469 align:start position:0% that's pretty cool and so what we talked about<01:42:16.030> earlier<01:42:16.269> is<01:42:16.749> as<01:42:17.579> you<01:42:18.579> know<01:42:18.610> now<01:42:18.999> now 01:42:19.469 --> 01:42:19.479 align:start position:0% about earlier is as you know now now 01:42:19.479 --> 01:42:21.750 align:start position:0% about earlier is as you know now now that<01:42:19.719> we<01:42:19.869> have<01:42:20.170> begun<01:42:20.559> to<01:42:20.739> fill<01:42:21.429> it<01:42:21.550> off'<01:42:21.639> i 01:42:21.750 --> 01:42:21.760 align:start position:0% that we have begun to fill it off' i 01:42:21.760 --> 01:42:25.080 align:start position:0% that we have begun to fill it off' i that<01:42:22.079> we've<01:42:23.079> new<01:42:23.260> things<01:42:23.499> to<01:42:23.829> to<01:42:24.429> validate<01:42:24.789> and 01:42:25.080 --> 01:42:25.090 align:start position:0% that we've new things to to validate and 01:42:25.090 --> 01:42:28.620 align:start position:0% that we've new things to to validate and so<01:42:26.130> that<01:42:27.130> would<01:42:27.280> be<01:42:27.489> different<01:42:28.150> models<01:42:28.420> around 01:42:28.620 --> 01:42:28.630 align:start position:0% so that would be different models around 01:42:28.630 --> 01:42:31.439 align:start position:0% so that would be different models around crushed<01:42:29.440> our<01:42:29.650> transactions<01:42:30.329> and<01:42:31.329> also 01:42:31.439 --> 01:42:31.449 align:start position:0% crushed our transactions and also 01:42:31.449 --> 01:42:32.969 align:start position:0% crushed our transactions and also different<01:42:31.869> models<01:42:32.079> around<01:42:32.260> the<01:42:32.349> fee<01:42:32.559> market 01:42:32.969 --> 01:42:32.979 align:start position:0% different models around the fee market 01:42:32.979 --> 01:42:35.759 align:start position:0% different models around the fee market and<01:42:33.280> the<01:42:33.999> real<01:42:34.510> a<01:42:34.659> market<01:42:35.079> you<01:42:35.289> know<01:42:35.349> someone 01:42:35.759 --> 01:42:35.769 align:start position:0% and the real a market you know someone 01:42:35.769 --> 01:42:38.310 align:start position:0% and the real a market you know someone has<01:42:35.979> to<01:42:36.219> be<01:42:36.369> responsible<01:42:36.969> for<01:42:37.199> setting<01:42:38.199> up 01:42:38.310 --> 01:42:38.320 align:start position:0% has to be responsible for setting up 01:42:38.320 --> 01:42:41.339 align:start position:0% has to be responsible for setting up these<01:42:38.440> multi<01:42:38.800> proofs<01:42:39.929> refreshing<01:42:40.929> the<01:42:41.050> multi 01:42:41.339 --> 01:42:41.349 align:start position:0% these multi proofs refreshing the multi 01:42:41.349 --> 01:42:44.729 align:start position:0% these multi proofs refreshing the multi proves<01:42:41.590> every<01:42:41.920> block<01:42:42.159> as<01:42:42.369> well<01:42:42.400> and<01:42:43.619> you<01:42:44.619> know 01:42:44.729 --> 01:42:44.739 align:start position:0% proves every block as well and you know 01:42:44.739 --> 01:42:46.439 align:start position:0% proves every block as well and you know so<01:42:45.099> we<01:42:45.489> want<01:42:45.670> to<01:42:45.760> be<01:42:45.849> able<01:42:45.909> to<01:42:45.999> make<01:42:46.179> tests 01:42:46.439 --> 01:42:46.449 align:start position:0% so we want to be able to make tests 01:42:46.449 --> 01:42:49.890 align:start position:0% so we want to be able to make tests grounds<01:42:46.949> by<01:42:47.949> which<01:42:48.130> we<01:42:48.340> can<01:42:48.630> you<01:42:49.630> know<01:42:49.719> we<01:42:49.869> can 01:42:49.890 --> 01:42:49.900 align:start position:0% grounds by which we can you know we can 01:42:49.900 --> 01:42:52.169 align:start position:0% grounds by which we can you know we can show<01:42:50.170> all<01:42:50.409> of<01:42:50.440> that<01:42:50.709> so<01:42:51.039> that's<01:42:51.459> the<01:42:51.670> goal<01:42:51.849> of 01:42:52.169 --> 01:42:52.179 align:start position:0% show all of that so that's the goal of 01:42:52.179 --> 01:42:57.629 align:start position:0% show all of that so that's the goal of work<01:42:52.659> behind<01:42:52.959> this<01:42:53.999> so<01:42:55.260> in<01:42:56.260> general<01:42:56.639> the 01:42:57.629 --> 01:42:57.639 align:start position:0% work behind this so in general the 01:42:57.639 --> 01:42:59.790 align:start position:0% work behind this so in general the purpose<01:42:58.030> is<01:42:58.360> want<01:42:59.170> to<01:42:59.229> be<01:42:59.320> able<01:42:59.380> to<01:42:59.499> simulate 01:42:59.790 --> 01:42:59.800 align:start position:0% purpose is want to be able to simulate 01:42:59.800 --> 01:43:02.310 align:start position:0% purpose is want to be able to simulate the<01:43:00.070> system<01:43:00.249> at<01:43:00.579> the<01:43:00.699> end<01:43:00.849> on<01:43:01.179> begin<01:43:02.019> building 01:43:02.310 --> 01:43:02.320 align:start position:0% the system at the end on begin building 01:43:02.320 --> 01:43:06.299 align:start position:0% the system at the end on begin building simulations<01:43:03.249> around<01:43:03.699> the<01:43:04.530> the<01:43:05.530> fee<01:43:05.920> market 01:43:06.299 --> 01:43:06.309 align:start position:0% simulations around the the fee market 01:43:06.309 --> 01:43:09.870 align:start position:0% simulations around the the fee market and<01:43:07.150> relay<01:43:07.780> network<01:43:08.079> as<01:43:08.229> well<01:43:08.550> and<01:43:09.550> we<01:43:09.639> want<01:43:09.760> to 01:43:09.870 --> 01:43:09.880 align:start position:0% and relay network as well and we want to 01:43:09.880 --> 01:43:13.199 align:start position:0% and relay network as well and we want to have<01:43:10.030> you<01:43:10.570> know<01:43:10.929> you<01:43:11.320> can<01:43:11.349> reckon<01:43:11.769> and<01:43:12.249> you<01:43:12.999> can 01:43:13.199 --> 01:43:13.209 align:start position:0% have you know you can reckon and you can 01:43:13.209 --> 01:43:16.069 align:start position:0% have you know you can reckon and you can you<01:43:13.599> know<01:43:13.690> communicate<01:43:14.289> across<01:43:14.499> jars<01:43:14.829> now<01:43:15.010> so 01:43:16.069 --> 01:43:16.079 align:start position:0% you know communicate across jars now so 01:43:16.079 --> 01:43:18.330 align:start position:0% you know communicate across jars now so that's<01:43:17.079> the<01:43:17.260> goal<01:43:17.380> here 01:43:18.330 --> 01:43:18.340 align:start position:0% that's the goal here 01:43:18.340 --> 01:43:21.540 align:start position:0% that's the goal here and<01:43:18.670> you<01:43:19.090> know<01:43:19.209> the<01:43:19.989> system<01:43:20.650> you<01:43:21.219> know<01:43:21.340> should 01:43:21.540 --> 01:43:21.550 align:start position:0% and you know the system you know should 01:43:21.550 --> 01:43:26.170 align:start position:0% and you know the system you know should also<01:43:21.840> have<01:43:23.159> core<01:43:24.159> tenants 01:43:26.170 --> 01:43:26.180 align:start position:0% also have core tenants 01:43:26.180 --> 01:43:27.700 align:start position:0% also have core tenants you<01:43:26.480> know<01:43:26.570> this<01:43:26.720> chart<01:43:26.930> should<01:43:27.170> be<01:43:27.290> for<01:43:27.530> King 01:43:27.700 --> 01:43:27.710 align:start position:0% you know this chart should be for King 01:43:27.710 --> 01:43:29.620 align:start position:0% you know this chart should be for King house<01:43:28.280> ability<01:43:28.760> that<01:43:29.360> should<01:43:29.540> be 01:43:29.620 --> 01:43:29.630 align:start position:0% house ability that should be 01:43:29.630 --> 01:43:31.690 align:start position:0% house ability that should be configurable<01:43:30.260> so<01:43:30.500> you<01:43:31.100> can<01:43:31.220> also<01:43:31.340> deal<01:43:31.580> with 01:43:31.690 --> 01:43:31.700 align:start position:0% configurable so you can also deal with 01:43:31.700 --> 01:43:34.510 align:start position:0% configurable so you can also deal with real<01:43:31.910> Ericsson<01:43:32.560> you<01:43:33.560> know<01:43:33.680> respond 01:43:34.510 --> 01:43:34.520 align:start position:0% real Ericsson you know respond 01:43:34.520 --> 01:43:36.190 align:start position:0% real Ericsson you know respond accordingly 01:43:36.190 --> 01:43:36.200 align:start position:0% accordingly 01:43:36.200 --> 01:43:38.770 align:start position:0% accordingly so<01:43:36.650> in<01:43:37.070> this<01:43:37.250> the<01:43:37.550> validators<01:43:38.090> are<01:43:38.210> simulated 01:43:38.770 --> 01:43:38.780 align:start position:0% so in this the validators are simulated 01:43:38.780 --> 01:43:41.560 align:start position:0% so in this the validators are simulated using<01:43:39.350> local<01:43:39.620> keys<01:43:40.060> so<01:43:41.060> it's<01:43:41.240> not<01:43:41.390> like 01:43:41.560 --> 01:43:41.570 align:start position:0% using local keys so it's not like 01:43:41.570 --> 01:43:43.240 align:start position:0% using local keys so it's not like there's<01:43:41.750> an<01:43:41.870> entry<01:43:42.230> into<01:43:42.350> the<01:43:42.500> test<01:43:42.710> mess<01:43:42.950> it's 01:43:43.240 --> 01:43:43.250 align:start position:0% there's an entry into the test mess it's 01:43:43.250 --> 01:43:45.210 align:start position:0% there's an entry into the test mess it's not<01:43:43.400> like<01:43:43.580> you're<01:43:43.910> gonna<01:43:44.180> run<01:43:44.450> here<01:43:44.690> don't 01:43:45.210 --> 01:43:45.220 align:start position:0% not like you're gonna run here don't 01:43:45.220 --> 01:43:47.680 align:start position:0% not like you're gonna run here don't know<01:43:46.220> that<01:43:46.490> can<01:43:46.670> enter<01:43:46.970> into<01:43:47.300> it<01:43:47.510> this<01:43:47.630> is 01:43:47.680 --> 01:43:47.690 align:start position:0% know that can enter into it this is 01:43:47.690 --> 01:43:53.140 align:start position:0% know that can enter into it this is again<01:43:48.020> more<01:43:48.350> of<01:43:48.380> a<01:43:50.500> testament<01:43:51.500> that<01:43:52.280> is<01:43:52.520> set<01:43:53.030> up 01:43:53.140 --> 01:43:53.150 align:start position:0% again more of a testament that is set up 01:43:53.150 --> 01:43:55.390 align:start position:0% again more of a testament that is set up and<01:43:53.450> optimized<01:43:54.170> for<01:43:54.470> YouTube<01:43:54.770> right<01:43:55.010> and 01:43:55.390 --> 01:43:55.400 align:start position:0% and optimized for YouTube right and 01:43:55.400 --> 01:43:58.690 align:start position:0% and optimized for YouTube right and around<01:43:56.260> that<01:43:57.260> makes<01:43:57.800> multiple<01:43:58.010> shards<01:43:58.430> and 01:43:58.690 --> 01:43:58.700 align:start position:0% around that makes multiple shards and 01:43:58.700 --> 01:44:00.250 align:start position:0% around that makes multiple shards and shows<01:43:58.910> beacon<01:43:59.300> chain<01:43:59.510> that's<01:43:59.690> running<01:43:59.930> and 01:44:00.250 --> 01:44:00.260 align:start position:0% shows beacon chain that's running and 01:44:00.260 --> 01:44:02.260 align:start position:0% shows beacon chain that's running and that<01:44:00.440> is<01:44:00.740> interacting<01:44:01.730> with<01:44:01.760> these<01:44:02.000> chart 01:44:02.260 --> 01:44:02.270 align:start position:0% that is interacting with these chart 01:44:02.270 --> 01:44:05.620 align:start position:0% that is interacting with these chart changes<01:44:02.740> also<01:44:03.910> what<01:44:04.910> will<01:44:05.090> be<01:44:05.210> really<01:44:05.450> cool 01:44:05.620 --> 01:44:05.630 align:start position:0% changes also what will be really cool 01:44:05.630 --> 01:44:07.480 align:start position:0% changes also what will be really cool and<01:44:05.840> what<01:44:06.050> I'd<01:44:06.200> like<01:44:06.350> to<01:44:06.470> have<01:44:06.620> by<01:44:06.770> January<01:44:07.250> is 01:44:07.480 --> 01:44:07.490 align:start position:0% and what I'd like to have by January is 01:44:07.490 --> 01:44:10.540 align:start position:0% and what I'd like to have by January is real-time<01:44:08.180> deployments<01:44:08.930> of<01:44:09.110> these<01:44:09.230> so<01:44:10.160> having 01:44:10.540 --> 01:44:10.550 align:start position:0% real-time deployments of these so having 01:44:10.550 --> 01:44:13.870 align:start position:0% real-time deployments of these so having having<01:44:10.970> this<01:44:11.210> running<01:44:11.870> and<01:44:12.020> you<01:44:12.380> know<01:44:12.470> you<01:44:12.880> as 01:44:13.870 --> 01:44:13.880 align:start position:0% having this running and you know you as 01:44:13.880 --> 01:44:15.610 align:start position:0% having this running and you know you as a<01:44:13.910> developer<01:44:14.120> you<01:44:14.570> being<01:44:14.780> able<01:44:14.870> to<01:44:14.990> write<01:44:15.380> Nene 01:44:15.610 --> 01:44:15.620 align:start position:0% a developer you being able to write Nene 01:44:15.620 --> 01:44:19.030 align:start position:0% a developer you being able to write Nene and<01:44:16.120> deploy<01:44:17.120> that<01:44:17.150> with<01:44:17.570> the<01:44:17.720> click<01:44:18.080> then 01:44:19.030 --> 01:44:19.040 align:start position:0% and deploy that with the click then 01:44:19.040 --> 01:44:21.250 align:start position:0% and deploy that with the click then being<01:44:19.760> able<01:44:19.850> to<01:44:20.000> see<01:44:20.210> how<01:44:20.450> you<01:44:20.870> know<01:44:20.900> how<01:44:21.200> you 01:44:21.250 --> 01:44:21.260 align:start position:0% being able to see how you know how you 01:44:21.260 --> 01:44:23.350 align:start position:0% being able to see how you know how you can<01:44:21.530> interact<01:44:21.920> with<01:44:22.250> that<01:44:22.400> in<01:44:22.550> and<01:44:23.150> the 01:44:23.350 --> 01:44:23.360 align:start position:0% can interact with that in and the 01:44:23.360 --> 01:44:27.760 align:start position:0% can interact with that in and the simulation<01:44:23.870> was<01:44:23.960> a<01:44:24.050> whole<01:44:25.480> so<01:44:26.480> what<01:44:26.870> is<01:44:27.140> it<01:44:27.320> so 01:44:27.760 --> 01:44:27.770 align:start position:0% simulation was a whole so what is it so 01:44:27.770 --> 01:44:29.650 align:start position:0% simulation was a whole so what is it so we're<01:44:28.100> not<01:44:28.370> dealing<01:44:28.700> with<01:44:28.880> networking<01:44:29.480> so 01:44:29.650 --> 01:44:29.660 align:start position:0% we're not dealing with networking so 01:44:29.660 --> 01:44:31.150 align:start position:0% we're not dealing with networking so we're<01:44:29.960> not<01:44:30.050> trying<01:44:30.350> to<01:44:30.380> benchmark<01:44:30.680> any<01:44:31.010> other 01:44:31.150 --> 01:44:31.160 align:start position:0% we're not trying to benchmark any other 01:44:31.160 --> 01:44:34.480 align:start position:0% we're not trying to benchmark any other networking<01:44:31.610> side<01:44:31.970> of<01:44:32.090> things<01:44:32.650> you<01:44:33.650> know<01:44:34.370> it's 01:44:34.480 --> 01:44:34.490 align:start position:0% networking side of things you know it's 01:44:34.490 --> 01:44:37.180 align:start position:0% networking side of things you know it's all<01:44:34.670> simulated<01:44:35.210> so<01:44:35.870> you<01:44:36.500> can't<01:44:36.770> you<01:44:37.070> know 01:44:37.180 --> 01:44:37.190 align:start position:0% all simulated so you can't you know 01:44:37.190 --> 01:44:39.400 align:start position:0% all simulated so you can't you know start<01:44:37.850> it<01:44:37.940> out<01:44:38.060> and<01:44:38.300> connect<01:44:38.690> to<01:44:38.750> this<01:44:38.930> this 01:44:39.400 --> 01:44:39.410 align:start position:0% start it out and connect to this this 01:44:39.410 --> 01:44:42.070 align:start position:0% start it out and connect to this this network<01:44:39.850> we're<01:44:40.850> not<01:44:40.940> trying<01:44:41.180> to<01:44:41.210> go<01:44:41.360> any<01:44:41.750> type 01:44:42.070 --> 01:44:42.080 align:start position:0% network we're not trying to go any type 01:44:42.080 --> 01:44:44.980 align:start position:0% network we're not trying to go any type of<01:44:42.200> production<01:44:42.470> client<01:44:43.220> that's<01:44:44.060> not<01:44:44.750> our<01:44:44.900> goal 01:44:44.980 --> 01:44:44.990 align:start position:0% of production client that's not our goal 01:44:44.990 --> 01:44:47.380 align:start position:0% of production client that's not our goal at<01:44:45.110> all<01:44:45.200> so<01:44:45.470> again<01:44:45.920> we<01:44:46.100> just<01:44:46.280> start<01:44:46.610> trying<01:44:47.240> to 01:44:47.380 --> 01:44:47.390 align:start position:0% at all so again we just start trying to 01:44:47.390 --> 01:44:48.820 align:start position:0% at all so again we just start trying to validate<01:44:47.750> all<01:44:47.930> these<01:44:48.080> things<01:44:48.350> and<01:44:48.530> let<01:44:48.650> people 01:44:48.820 --> 01:44:48.830 align:start position:0% validate all these things and let people 01:44:48.830 --> 01:44:51.730 align:start position:0% validate all these things and let people have<01:44:49.070> an<01:44:49.190> early<01:44:49.600> early<01:44:50.600> foray<01:44:51.080> into<01:44:51.560> this 01:44:51.730 --> 01:44:51.740 align:start position:0% have an early early foray into this 01:44:51.740 --> 01:44:56.860 align:start position:0% have an early early foray into this world<01:44:53.170> so<01:44:54.190> you<01:44:55.190> know<01:44:55.310> the<01:44:56.210> system<01:44:56.690> should<01:44:56.810> be 01:44:56.860 --> 01:44:56.870 align:start position:0% world so you know the system should be 01:44:56.870 --> 01:44:58.330 align:start position:0% world so you know the system should be configurable<01:44:57.590> we<01:44:57.770> should<01:44:57.950> say<01:44:58.130> how<01:44:58.280> many 01:44:58.330 --> 01:44:58.340 align:start position:0% configurable we should say how many 01:44:58.340 --> 01:45:00.970 align:start position:0% configurable we should say how many shards<01:44:58.730> are<01:44:58.940> running<01:44:59.590> you<01:45:00.590> know<01:45:00.710> you<01:45:00.800> should 01:45:00.970 --> 01:45:00.980 align:start position:0% shards are running you know you should 01:45:00.980 --> 01:45:04.420 align:start position:0% shards are running you know you should set<01:45:01.220> the<01:45:01.400> fourth<01:45:01.640> ability<01:45:02.000> parameters<01:45:03.430> you 01:45:04.420 --> 01:45:04.430 align:start position:0% set the fourth ability parameters you 01:45:04.430 --> 01:45:05.830 align:start position:0% set the fourth ability parameters you know<01:45:04.550> one<01:45:04.700> of<01:45:04.730> the<01:45:04.850> thing<01:45:05.060> the<01:45:05.300> taller<01:45:05.540> you 01:45:05.830 --> 01:45:05.840 align:start position:0% know one of the thing the taller you 01:45:05.840 --> 01:45:08.200 align:start position:0% know one of the thing the taller you know<01:45:05.960> has<01:45:06.110> given<01:45:06.550> three<01:45:07.550> different<01:45:07.640> you<01:45:08.120> know 01:45:08.200 --> 01:45:08.210 align:start position:0% know has given three different you know 01:45:08.210 --> 01:45:11.620 align:start position:0% know has given three different you know proposals<01:45:08.780> over<01:45:09.140> the<01:45:09.260> last<01:45:09.410> over<01:45:10.480> the<01:45:11.480> last 01:45:11.620 --> 01:45:11.630 align:start position:0% proposals over the last over the last 01:45:11.630 --> 01:45:14.980 align:start position:0% proposals over the last over the last couple<01:45:11.840> months<01:45:12.140> and<01:45:12.550> I<01:45:13.550> think<01:45:14.180> you<01:45:14.600> know<01:45:14.720> some 01:45:14.980 --> 01:45:14.990 align:start position:0% couple months and I think you know some 01:45:14.990 --> 01:45:16.510 align:start position:0% couple months and I think you know some of<01:45:15.020> these<01:45:15.200> new<01:45:15.410> proposals<01:45:15.890> are<01:45:15.980> really 01:45:16.510 --> 01:45:16.520 align:start position:0% of these new proposals are really 01:45:16.520 --> 01:45:17.950 align:start position:0% of these new proposals are really awesome<01:45:16.910> like<01:45:17.030> they<01:45:17.210> all<01:45:17.360> have<01:45:17.540> trade-offs 01:45:17.950 --> 01:45:17.960 align:start position:0% awesome like they all have trade-offs 01:45:17.960 --> 01:45:19.210 align:start position:0% awesome like they all have trade-offs and<01:45:18.200> there's<01:45:18.380> there's<01:45:18.740> some<01:45:18.860> really<01:45:18.980> cool 01:45:19.210 --> 01:45:19.220 align:start position:0% and there's there's some really cool 01:45:19.220 --> 01:45:21.940 align:start position:0% and there's there's some really cool things<01:45:19.460> and<01:45:19.850> so<01:45:20.090> if<01:45:21.020> we're<01:45:21.200> able<01:45:21.320> to<01:45:21.500> just<01:45:21.710> test 01:45:21.940 --> 01:45:21.950 align:start position:0% things and so if we're able to just test 01:45:21.950 --> 01:45:22.540 align:start position:0% things and so if we're able to just test this 01:45:22.540 --> 01:45:22.550 align:start position:0% this 01:45:22.550 --> 01:45:25.150 align:start position:0% this pretty<01:45:23.150> quickly<01:45:23.390> to<01:45:23.600> make<01:45:23.780> changes<01:45:24.230> that<01:45:24.290> that 01:45:25.150 --> 01:45:25.160 align:start position:0% pretty quickly to make changes that that 01:45:25.160 --> 01:45:27.729 align:start position:0% pretty quickly to make changes that that becomes<01:45:25.489> that<01:45:25.940> becomes<01:45:26.090> really<01:45:26.450> viable<01:45:26.739> so 01:45:27.729 --> 01:45:27.739 align:start position:0% becomes that becomes really viable so 01:45:27.739 --> 01:45:30.340 align:start position:0% becomes that becomes really viable so that's<01:45:27.920> that's<01:45:28.190> kind<01:45:28.370> of<01:45:28.520> the<01:45:28.640> goal<01:45:28.790> of<01:45:29.510> this 01:45:30.340 --> 01:45:30.350 align:start position:0% that's that's kind of the goal of this 01:45:30.350 --> 01:45:32.500 align:start position:0% that's that's kind of the goal of this and<01:45:30.739> what<01:45:31.280> we're<01:45:31.400> building<01:45:31.550> and<01:45:31.940> we<01:45:32.300> have<01:45:32.480> a 01:45:32.500 --> 01:45:32.510 align:start position:0% and what we're building and we have a 01:45:32.510 --> 01:45:34.680 align:start position:0% and what we're building and we have a basic<01:45:33.080> functioning<01:45:33.620> system<01:45:34.040> right<01:45:34.130> now<01:45:34.190> and 01:45:34.680 --> 01:45:34.690 align:start position:0% basic functioning system right now and 01:45:34.690 --> 01:45:37.270 align:start position:0% basic functioning system right now and so<01:45:35.690> I'll<01:45:35.810> talk<01:45:35.960> about<01:45:36.020> that<01:45:36.230> to<01:45:36.590> show<01:45:36.770> you<01:45:36.830> real 01:45:37.270 --> 01:45:37.280 align:start position:0% so I'll talk about that to show you real 01:45:37.280 --> 01:45:39.040 align:start position:0% so I'll talk about that to show you real quick<01:45:37.520> and<01:45:37.550> then<01:45:37.850> talk<01:45:38.150> about<01:45:38.330> the<01:45:38.870> vision 01:45:39.040 --> 01:45:39.050 align:start position:0% quick and then talk about the vision 01:45:39.050 --> 01:45:42.490 align:start position:0% quick and then talk about the vision behind<01:45:39.290> that<01:45:40.150> again<01:45:41.150> it<01:45:41.270> provides<01:45:41.630> endpoints 01:45:42.490 --> 01:45:42.500 align:start position:0% behind that again it provides endpoints 01:45:42.500 --> 01:45:44.530 align:start position:0% behind that again it provides endpoints interactive<01:45:43.010> block<01:45:43.310> producer<01:45:43.880> you<01:45:44.239> could<01:45:44.360> get 01:45:44.530 --> 01:45:44.540 align:start position:0% interactive block producer you could get 01:45:44.540 --> 01:45:46.420 align:start position:0% interactive block producer you could get the<01:45:44.750> historical<01:45:45.560> data<01:45:45.770> and<01:45:45.950> say<01:45:46.100> these<01:45:46.280> would 01:45:46.420 --> 01:45:46.430 align:start position:0% the historical data and say these would 01:45:46.430 --> 01:45:48.040 align:start position:0% the historical data and say these would be<01:45:46.580> like<01:45:46.610> what<01:45:47.270> you<01:45:47.330> would<01:45:47.450> have<01:45:47.570> this<01:45:47.719> normal 01:45:48.040 --> 01:45:48.050 align:start position:0% be like what you would have this normal 01:45:48.050 --> 01:45:51.670 align:start position:0% be like what you would have this normal RPC<01:45:48.410> endpoints<01:45:49.960> one<01:45:50.960> of<01:45:51.050> the<01:45:51.110> things<01:45:51.320> is<01:45:51.500> this 01:45:51.670 --> 01:45:51.680 align:start position:0% RPC endpoints one of the things is this 01:45:51.680 --> 01:45:56.700 align:start position:0% RPC endpoints one of the things is this is<01:45:51.830> right<01:45:52.130> now<01:45:52.280> if<01:45:52.430> orchid<01:45:52.880> lighthouse<01:45:54.580> and 01:45:56.700 --> 01:45:56.710 align:start position:0% is right now if orchid lighthouse and 01:45:56.710 --> 01:45:59.200 align:start position:0% is right now if orchid lighthouse and what<01:45:57.710> we<01:45:57.830> did<01:45:57.980> is<01:45:58.130> we<01:45:58.160> use<01:45:58.550> the<01:45:58.760> beacon<01:45:59.030> chain 01:45:59.200 --> 01:45:59.210 align:start position:0% what we did is we use the beacon chain 01:45:59.210 --> 01:46:02.110 align:start position:0% what we did is we use the beacon chain that<01:45:59.360> lighthouse<01:45:59.510> has<01:45:59.930> and<01:46:00.350> I<01:46:00.530> broke<01:46:01.250> a<01:46:01.700> char 01:46:02.110 --> 01:46:02.120 align:start position:0% that lighthouse has and I broke a char 01:46:02.120 --> 01:46:05.470 align:start position:0% that lighthouse has and I broke a char chain<01:46:02.739> and<01:46:03.739> then<01:46:03.890> the<01:46:03.980> char<01:46:04.160> chain<01:46:04.480> interacts 01:46:05.470 --> 01:46:05.480 align:start position:0% chain and then the char chain interacts 01:46:05.480 --> 01:46:11.530 align:start position:0% chain and then the char chain interacts with<01:46:05.660> weakened<01:46:05.989> chain<01:46:07.239> and<01:46:09.910> it's<01:46:10.910> right<01:46:11.390> now 01:46:11.530 --> 01:46:11.540 align:start position:0% with weakened chain and it's right now 01:46:11.540 --> 01:46:14.380 align:start position:0% with weakened chain and it's right now it's<01:46:11.780> running<01:46:12.080> one<01:46:12.440> star<01:46:12.710> shape<01:46:12.980> it's<01:46:13.250> I<01:46:13.940> think 01:46:14.380 --> 01:46:14.390 align:start position:0% it's running one star shape it's I think 01:46:14.390 --> 01:46:16.300 align:start position:0% it's running one star shape it's I think after<01:46:14.600> DEFCON<01:46:15.140> I'm<01:46:15.350> gonna<01:46:15.710> expand<01:46:16.160> it<01:46:16.280> to 01:46:16.300 --> 01:46:16.310 align:start position:0% after DEFCON I'm gonna expand it to 01:46:16.310 --> 01:46:19.720 align:start position:0% after DEFCON I'm gonna expand it to build<01:46:17.180> a<01:46:17.300> run<01:46:17.450> you<01:46:17.840> know<01:46:17.960> four<01:46:18.469> or<01:46:18.500> five<01:46:18.800> and 01:46:19.720 --> 01:46:19.730 align:start position:0% build a run you know four or five and 01:46:19.730 --> 01:46:20.500 align:start position:0% build a run you know four or five and it's<01:46:19.850> fairly<01:46:20.030> trivial 01:46:20.500 --> 01:46:20.510 align:start position:0% it's fairly trivial 01:46:20.510 --> 01:46:22.240 align:start position:0% it's fairly trivial I<01:46:20.660> just<01:46:20.960> didn't<01:46:21.290> you<01:46:21.469> know<01:46:21.500> want<01:46:21.770> to<01:46:21.890> break<01:46:22.219> a 01:46:22.240 --> 01:46:22.250 align:start position:0% I just didn't you know want to break a 01:46:22.250 --> 01:46:24.130 align:start position:0% I just didn't you know want to break a bunch<01:46:22.430> of<01:46:22.580> stuff<01:46:22.760> before<01:46:23.090> coming<01:46:23.330> here<01:46:23.480> so 01:46:24.130 --> 01:46:24.140 align:start position:0% bunch of stuff before coming here so 01:46:24.140 --> 01:46:26.470 align:start position:0% bunch of stuff before coming here so that<01:46:24.530> that<01:46:24.980> will<01:46:25.100> be<01:46:25.270> working<01:46:26.270> and<01:46:26.420> that's 01:46:26.470 --> 01:46:26.480 align:start position:0% that that will be working and that's 01:46:26.480 --> 01:46:30.310 align:start position:0% that that will be working and that's that's<01:46:26.870> pretty<01:46:26.989> cool<01:46:28.120> so<01:46:29.120> I'll<01:46:29.780> just<01:46:29.930> kind<01:46:30.290> of 01:46:30.310 --> 01:46:30.320 align:start position:0% that's pretty cool so I'll just kind of 01:46:30.320 --> 01:46:32.170 align:start position:0% that's pretty cool so I'll just kind of show<01:46:30.380> you<01:46:30.530> I<01:46:30.710> showed<01:46:31.130> this<01:46:31.250> demo<01:46:31.610> briefly<01:46:32.000> in 01:46:32.170 --> 01:46:32.180 align:start position:0% show you I showed this demo briefly in 01:46:32.180 --> 01:46:37.479 align:start position:0% show you I showed this demo briefly in my<01:46:32.300> talk<01:46:32.510> on<01:46:32.540> the<01:46:32.750> first<01:46:32.989> day<01:46:34.719> but<01:46:35.980> in<01:46:36.980> this 01:46:37.479 --> 01:46:37.489 align:start position:0% my talk on the first day but in this 01:46:37.489 --> 01:46:43.060 align:start position:0% my talk on the first day but in this case<01:46:38.380> what<01:46:39.380> I<01:46:39.560> will<01:46:39.800> first<01:46:40.100> do<01:46:41.469> just<01:46:42.469> clear<01:46:42.890> the 01:46:43.060 --> 01:46:43.070 align:start position:0% case what I will first do just clear the 01:46:43.070 --> 01:46:47.390 align:start position:0% case what I will first do just clear the screen<01:46:43.310> here 01:46:47.390 --> 01:46:47.400 align:start position:0% 01:46:47.400 --> 01:46:50.390 align:start position:0% I'm<01:46:47.850> gonna<01:46:47.970> start<01:46:48.470> the<01:46:49.470> demo<01:46:49.650> so<01:46:50.130> the<01:46:50.220> first 01:46:50.390 --> 01:46:50.400 align:start position:0% I'm gonna start the demo so the first 01:46:50.400 --> 01:46:51.080 align:start position:0% I'm gonna start the demo so the first thing<01:46:50.520> that<01:46:50.610> we're<01:46:50.730> doing<01:46:50.760> is<01:46:51.000> were 01:46:51.080 --> 01:46:51.090 align:start position:0% thing that we're doing is were 01:46:51.090 --> 01:46:54.400 align:start position:0% thing that we're doing is were fast-forwarding<01:46:51.480> the<01:46:52.080> beacon<01:46:52.730> Deacon<01:46:53.730> shape 01:46:54.400 --> 01:46:54.410 align:start position:0% fast-forwarding the beacon Deacon shape 01:46:54.410 --> 01:46:57.890 align:start position:0% fast-forwarding the beacon Deacon shape and<01:46:55.410> we're<01:46:56.280> bringing<01:46:56.490> it<01:46:56.730> to<01:46:57.090> the<01:46:57.450> phase<01:46:57.660> one 01:46:57.890 --> 01:46:57.900 align:start position:0% and we're bringing it to the phase one 01:46:57.900 --> 01:46:59.960 align:start position:0% and we're bringing it to the phase one fork<01:46:58.170> epics<01:46:58.530> the<01:46:58.740> phase<01:46:58.920> one<01:46:59.100> fork<01:46:59.340> epoch<01:46:59.700> is 01:46:59.960 --> 01:46:59.970 align:start position:0% fork epics the phase one fork epoch is 01:46:59.970 --> 01:47:02.690 align:start position:0% fork epics the phase one fork epoch is basically<01:47:01.010> the<01:47:02.010> beacon<01:47:02.250> change<01:47:02.430> would<01:47:02.580> be 01:47:02.690 --> 01:47:02.700 align:start position:0% basically the beacon change would be 01:47:02.700 --> 01:47:05.810 align:start position:0% basically the beacon change would be running<01:47:03.500> alone<01:47:04.500> without<01:47:04.830> the<01:47:04.980> charts<01:47:05.370> once 01:47:05.810 --> 01:47:05.820 align:start position:0% running alone without the charts once 01:47:05.820 --> 01:47:07.790 align:start position:0% running alone without the charts once you<01:47:05.970> rigid<01:47:06.210> or<01:47:06.420> fork<01:47:06.960> epic<01:47:07.260> than<01:47:07.470> the<01:47:07.500> starts 01:47:07.790 --> 01:47:07.800 align:start position:0% you rigid or fork epic than the starts 01:47:07.800 --> 01:47:09.890 align:start position:0% you rigid or fork epic than the starts are<01:47:07.890> gonna<01:47:08.010> start<01:47:08.310> so<01:47:08.520> now<01:47:09.390> we<01:47:09.450> see<01:47:09.660> that<01:47:09.810> the 01:47:09.890 --> 01:47:09.900 align:start position:0% are gonna start so now we see that the 01:47:09.900 --> 01:47:12.560 align:start position:0% are gonna start so now we see that the shards<01:47:10.260> are<01:47:10.830> ready<01:47:11.070> and<01:47:11.430> we're<01:47:12.210> simulating 01:47:12.560 --> 01:47:12.570 align:start position:0% shards are ready and we're simulating 01:47:12.570 --> 01:47:14.930 align:start position:0% shards are ready and we're simulating three<01:47:13.110> second<01:47:13.410> chart<01:47:13.620> blocks<01:47:13.890> and<01:47:14.220> six<01:47:14.640> second 01:47:14.930 --> 01:47:14.940 align:start position:0% three second chart blocks and six second 01:47:14.940 --> 01:47:17.090 align:start position:0% three second chart blocks and six second beacon<01:47:15.330> blocks<01:47:15.570> and<01:47:15.810> so<01:47:15.960> in<01:47:16.530> a<01:47:16.650> second<01:47:16.980> you're 01:47:17.090 --> 01:47:17.100 align:start position:0% beacon blocks and so in a second you're 01:47:17.100 --> 01:47:18.620 align:start position:0% beacon blocks and so in a second you're going<01:47:17.190> to<01:47:17.280> see<01:47:17.430> that<01:47:17.670> there<01:47:17.970> will<01:47:18.180> be<01:47:18.240> a<01:47:18.360> cross 01:47:18.620 --> 01:47:18.630 align:start position:0% going to see that there will be a cross 01:47:18.630 --> 01:47:20.600 align:start position:0% going to see that there will be a cross link<01:47:18.990> cross<01:47:19.800> links<01:47:20.040> that<01:47:20.130> are<01:47:20.250> sent<01:47:20.460> over<01:47:20.490> to 01:47:20.600 --> 01:47:20.610 align:start position:0% link cross links that are sent over to 01:47:20.610 --> 01:47:23.300 align:start position:0% link cross links that are sent over to the<01:47:20.760> beacon<01:47:21.030> chain<01:47:21.380> finality<01:47:22.380> is<01:47:22.650> established 01:47:23.300 --> 01:47:23.310 align:start position:0% the beacon chain finality is established 01:47:23.310 --> 01:47:26.390 align:start position:0% the beacon chain finality is established and<01:47:23.690> ultimately<01:47:24.690> that<01:47:25.650> proves<01:47:26.010> the<01:47:26.190> poor 01:47:26.390 --> 01:47:26.400 align:start position:0% and ultimately that proves the poor 01:47:26.400 --> 01:47:28.900 align:start position:0% and ultimately that proves the poor choice<01:47:26.640> rule<01:47:26.970> for<01:47:27.660> the<01:47:27.720> shire<01:47:27.900> chain<01:47:28.140> as<01:47:28.260> well 01:47:28.900 --> 01:47:28.910 align:start position:0% choice rule for the shire chain as well 01:47:28.910 --> 01:47:31.880 align:start position:0% choice rule for the shire chain as well on<01:47:29.910> this<01:47:30.090> end<01:47:30.330> I'm<01:47:30.510> about<01:47:30.720> to<01:47:30.930> start<01:47:31.350> a<01:47:31.470> client 01:47:31.880 --> 01:47:31.890 align:start position:0% on this end I'm about to start a client 01:47:31.890 --> 01:47:34.820 align:start position:0% on this end I'm about to start a client called<01:47:32.220> wool<01:47:32.940> it's<01:47:33.120> part<01:47:33.660> of<01:47:33.720> what<01:47:33.960> Matt<01:47:34.800> was 01:47:34.820 --> 01:47:34.830 align:start position:0% called wool it's part of what Matt was 01:47:34.830 --> 01:47:38.150 align:start position:0% called wool it's part of what Matt was talking<01:47:35.190> about<01:47:35.370> this<01:47:35.640> she<01:47:36.300> shard<01:47:36.750> ether<01:47:37.160> and 01:47:38.150 --> 01:47:38.160 align:start position:0% talking about this she shard ether and 01:47:38.160 --> 01:47:41.930 align:start position:0% talking about this she shard ether and this<01:47:38.280> is<01:47:38.430> not<01:47:38.880> only<01:47:38.910> an<01:47:39.390> eat<01:47:39.630> but<01:47:39.810> it<01:47:39.900> also<01:47:40.940> is 01:47:41.930 --> 01:47:41.940 align:start position:0% this is not only an eat but it also is 01:47:41.940 --> 01:47:46.610 align:start position:0% this is not only an eat but it also is the<01:47:42.240> binary<01:47:43.110> that<01:47:43.440> lets<01:47:43.740> you<01:47:45.380> basically<01:47:46.380> go<01:47:46.590> to 01:47:46.610 --> 01:47:46.620 align:start position:0% the binary that lets you basically go to 01:47:46.620 --> 01:47:48.170 align:start position:0% the binary that lets you basically go to the<01:47:46.860> proofs<01:47:47.130> that<01:47:47.250> were<01:47:47.520> talking<01:47:47.790> about<01:47:48.000> so 01:47:48.170 --> 01:47:48.180 align:start position:0% the proofs that were talking about so 01:47:48.180 --> 01:47:49.130 align:start position:0% the proofs that were talking about so this<01:47:48.270> could<01:47:48.420> be<01:47:48.510> considered<01:47:48.900> an<01:47:48.990> early 01:47:49.130 --> 01:47:49.140 align:start position:0% this could be considered an early 01:47:49.140 --> 01:47:52.910 align:start position:0% this could be considered an early relayer<01:47:49.850> or<01:47:50.850> an<01:47:50.970> early<01:47:51.270> state<01:47:51.600> provider<01:47:51.960> so 01:47:52.910 --> 01:47:52.920 align:start position:0% relayer or an early state provider so 01:47:52.920 --> 01:47:55.360 align:start position:0% relayer or an early state provider so T's<01:47:53.190> its<01:47:53.370> own<01:47:53.550> vision<01:47:53.940> of<01:47:54.000> state<01:47:54.300> locally<01:47:54.750> and 01:47:55.360 --> 01:47:55.370 align:start position:0% T's its own vision of state locally and 01:47:55.370 --> 01:47:59.540 align:start position:0% T's its own vision of state locally and it<01:47:57.230> generates<01:47:58.230> the<01:47:58.470> multiple<01:47:59.100> centers<01:47:59.370> or 01:47:59.540 --> 01:47:59.550 align:start position:0% it generates the multiple centers or 01:47:59.550 --> 01:48:02.710 align:start position:0% it generates the multiple centers or transactions<01:48:00.510> to<01:48:00.780> establish<01:48:01.430> transfers<01:48:02.430> and 01:48:02.710 --> 01:48:02.720 align:start position:0% transactions to establish transfers and 01:48:02.720 --> 01:48:16.010 align:start position:0% transactions to establish transfers and imbalances<01:48:03.720> so<01:48:04.520> here<01:48:05.520> we<01:48:05.640> go 01:48:16.010 --> 01:48:16.020 align:start position:0% 01:48:16.020 --> 01:48:23.280 align:start position:0% okay 01:48:23.280 --> 01:48:23.290 align:start position:0% 01:48:23.290 --> 01:48:29.430 align:start position:0% because<01:48:23.980> I<01:48:24.550> just<01:48:24.880> do<01:48:25.440> please<01:48:26.440> transfer<01:48:28.440> this 01:48:29.430 --> 01:48:29.440 align:start position:0% because I just do please transfer this 01:48:29.440 --> 01:48:33.510 align:start position:0% because I just do please transfer this is<01:48:29.590> actually<01:48:30.040> creating<01:48:30.790> a<01:48:31.380> new<01:48:32.520> basically 01:48:33.510 --> 01:48:33.520 align:start position:0% is actually creating a new basically 01:48:33.520 --> 01:48:34.860 align:start position:0% is actually creating a new basically wanted<01:48:33.850> proof<01:48:33.970> of<01:48:34.150> this<01:48:34.210> transaction<01:48:34.660> has 01:48:34.860 --> 01:48:34.870 align:start position:0% wanted proof of this transaction has 01:48:34.870 --> 01:48:38.370 align:start position:0% wanted proof of this transaction has been<01:48:34.990> submitted<01:48:35.800> to<01:48:36.210> the<01:48:37.210> block<01:48:37.540> producer<01:48:38.080> I'm 01:48:38.370 --> 01:48:38.380 align:start position:0% been submitted to the block producer I'm 01:48:38.380 --> 01:48:46.080 align:start position:0% been submitted to the block producer I'm a<01:48:38.440> star<01:48:38.770> chain<01:48:39.040> right<01:48:39.220> now<01:48:42.750> so<01:48:45.090> transfer 01:48:46.080 --> 01:48:46.090 align:start position:0% a star chain right now so transfer 01:48:46.090 --> 01:48:52.390 align:start position:0% a star chain right now so transfer happened 01:48:52.390 --> 01:48:52.400 align:start position:0% 01:48:52.400 --> 01:48:54.880 align:start position:0% and<01:48:53.180> so<01:48:53.270> you'll<01:48:53.420> see<01:48:53.570> that<01:48:53.690> a<01:48:53.750> new<01:48:54.050> state<01:48:54.680> group 01:48:54.880 --> 01:48:54.890 align:start position:0% and so you'll see that a new state group 01:48:54.890 --> 01:48:57.520 align:start position:0% and so you'll see that a new state group is<01:48:55.130> now<01:48:55.870> available<01:48:56.870> for<01:48:57.020> that<01:48:57.080> execution 01:48:57.520 --> 01:48:57.530 align:start position:0% is now available for that execution 01:48:57.530 --> 01:48:59.170 align:start position:0% is now available for that execution environments<01:48:58.100> that<01:48:58.250> operated<01:48:58.880> there<01:48:59.000> and<01:48:59.120> I'm 01:48:59.170 --> 01:48:59.180 align:start position:0% environments that operated there and I'm 01:48:59.180 --> 01:49:00.400 align:start position:0% environments that operated there and I'm going<01:48:59.330> to<01:48:59.390> show<01:48:59.570> just<01:48:59.750> a<01:48:59.870> little<01:48:59.930> bit<01:49:00.140> of<01:49:00.230> code 01:49:00.400 --> 01:49:00.410 align:start position:0% going to show just a little bit of code 01:49:00.410 --> 01:49:01.470 align:start position:0% going to show just a little bit of code in<01:49:00.560> a<01:49:00.620> moment 01:49:01.470 --> 01:49:01.480 align:start position:0% in a moment 01:49:01.480 --> 01:49:04.420 align:start position:0% in a moment and<01:49:02.480> we<01:49:02.930> can<01:49:03.080> you<01:49:03.320> know<01:49:03.440> look<01:49:03.560> at<01:49:03.680> the<01:49:03.830> balance 01:49:04.420 --> 01:49:04.430 align:start position:0% and we can you know look at the balance 01:49:04.430 --> 01:49:08.410 align:start position:0% and we can you know look at the balance now<01:49:05.150> as<01:49:05.360> well<01:49:05.570> see<01:49:06.140> that<01:49:06.410> that's<01:49:07.000> was<01:49:08.000> updated 01:49:08.410 --> 01:49:08.420 align:start position:0% now as well see that that's was updated 01:49:08.420 --> 01:49:11.110 align:start position:0% now as well see that that's was updated so<01:49:08.840> that's<01:49:08.960> really<01:49:09.080> cool<01:49:09.320> so<01:49:09.790> the<01:49:10.790> goal<01:49:11.000> is 01:49:11.110 --> 01:49:11.120 align:start position:0% so that's really cool so the goal is 01:49:11.120 --> 01:49:13.300 align:start position:0% so that's really cool so the goal is really<01:49:11.360> now<01:49:11.510> you<01:49:12.110> know<01:49:12.230> all<01:49:12.260> these<01:49:12.800> E's<01:49:13.130> that 01:49:13.300 --> 01:49:13.310 align:start position:0% really now you know all these E's that 01:49:13.310 --> 01:49:14.440 align:start position:0% really now you know all these E's that are<01:49:13.400> being<01:49:13.550> build<01:49:13.790> we<01:49:13.910> can<01:49:14.030> start<01:49:14.270> plugging 01:49:14.440 --> 01:49:14.450 align:start position:0% are being build we can start plugging 01:49:14.450 --> 01:49:18.370 align:start position:0% are being build we can start plugging into<01:49:14.780> this<01:49:14.990> and<01:49:16.150> we<01:49:17.150> want<01:49:17.600> to<01:49:17.690> kind<01:49:18.110> of<01:49:18.140> change 01:49:18.370 --> 01:49:18.380 align:start position:0% into this and we want to kind of change 01:49:18.380 --> 01:49:20.170 align:start position:0% into this and we want to kind of change this<01:49:18.590> to<01:49:19.100> where<01:49:19.310> it's<01:49:19.460> no<01:49:19.640> longer<01:49:19.670> just<01:49:19.970> a 01:49:20.170 --> 01:49:20.180 align:start position:0% this to where it's no longer just a 01:49:20.180 --> 01:49:22.540 align:start position:0% this to where it's no longer just a forked<01:49:20.510> plate<01:49:20.690> house<01:49:20.870> but<01:49:21.860> we<01:49:22.250> want<01:49:22.460> to 01:49:22.540 --> 01:49:22.550 align:start position:0% forked plate house but we want to 01:49:22.550 --> 01:49:25.420 align:start position:0% forked plate house but we want to actually<01:49:22.880> just<01:49:23.060> pull<01:49:23.450> them<01:49:23.690> to<01:49:24.500> scalp<01:49:25.130> and 01:49:25.420 --> 01:49:25.430 align:start position:0% actually just pull them to scalp and 01:49:25.430 --> 01:49:28.000 align:start position:0% actually just pull them to scalp and have<01:49:25.880> this<01:49:26.120> be<01:49:26.540> just<01:49:26.930> an<01:49:27.080> additional<01:49:27.530> tool<01:49:27.710> set 01:49:28.000 --> 01:49:28.010 align:start position:0% have this be just an additional tool set 01:49:28.010 --> 01:49:28.990 align:start position:0% have this be just an additional tool set scalp<01:49:28.520> lever 01:49:28.990 --> 01:49:29.000 align:start position:0% scalp lever 01:49:29.000 --> 01:49:31.290 align:start position:0% scalp lever let's<01:49:29.570> you<01:49:29.750> mimic<01:49:30.050> this<01:49:30.260> whole<01:49:30.470> system<01:49:30.920> and 01:49:31.290 --> 01:49:31.300 align:start position:0% let's you mimic this whole system and 01:49:31.300 --> 01:49:33.400 align:start position:0% let's you mimic this whole system and you<01:49:32.300> know<01:49:32.420> we<01:49:32.570> don't<01:49:32.690> we<01:49:33.050> don't<01:49:33.140> need<01:49:33.290> the 01:49:33.400 --> 01:49:33.410 align:start position:0% you know we don't we don't need the 01:49:33.410 --> 01:49:35.050 align:start position:0% you know we don't we don't need the networking<01:49:33.740> side<01:49:33.860> of<01:49:34.160> things<01:49:34.400> we<01:49:34.640> can<01:49:34.820> you 01:49:35.050 --> 01:49:35.060 align:start position:0% networking side of things we can you 01:49:35.060 --> 01:49:48.970 align:start position:0% networking side of things we can you know<01:49:35.180> fairly<01:49:35.840> simplify<01:49:36.680> a<01:49:37.330> decent<01:49:38.330> amount<01:49:38.980> so 01:49:48.970 --> 01:49:48.980 align:start position:0% 01:49:48.980 --> 01:49:54.010 align:start position:0% all<01:49:49.980> right<01:49:50.190> here<01:49:51.090> you'll<01:49:51.330> see<01:49:51.420> this<01:49:51.690> is<01:49:52.620> the 01:49:54.010 --> 01:49:54.020 align:start position:0% all right here you'll see this is the 01:49:54.020 --> 01:49:57.140 align:start position:0% all right here you'll see this is the code<01:49:55.020> so<01:49:55.710> there's<01:49:55.860> a<01:49:56.159> lot<01:49:56.460> of<01:49:56.489> work<01:49:56.730> lots<01:49:57.030> of 01:49:57.140 --> 01:49:57.150 align:start position:0% code so there's a lot of work lots of 01:49:57.150 --> 01:49:59.209 align:start position:0% code so there's a lot of work lots of cleanup<01:49:57.389> needed<01:49:57.840> lots<01:49:58.530> of<01:49:58.620> things<01:49:58.830> that<01:49:59.070> need 01:49:59.209 --> 01:49:59.219 align:start position:0% cleanup needed lots of things that need 01:49:59.219 --> 01:50:03.649 align:start position:0% cleanup needed lots of things that need to<01:49:59.250> be<01:49:59.840> added<01:50:01.520> but<01:50:02.520> again<01:50:02.790> the<01:50:02.969> system<01:50:03.360> is 01:50:03.649 --> 01:50:03.659 align:start position:0% to be added but again the system is 01:50:03.659 --> 01:50:05.209 align:start position:0% to be added but again the system is working<01:50:03.960> end<01:50:04.290> to<01:50:04.409> end<01:50:04.590> and<01:50:04.739> what's<01:50:04.920> what's 01:50:05.209 --> 01:50:05.219 align:start position:0% working end to end and what's what's 01:50:05.219 --> 01:50:11.600 align:start position:0% working end to end and what's what's cool<01:50:05.429> is<01:50:05.460> that<01:50:05.730> the<01:50:07.340> the<01:50:10.070> hardest<01:50:11.070> thing<01:50:11.340> is 01:50:11.600 --> 01:50:11.610 align:start position:0% cool is that the the hardest thing is 01:50:11.610 --> 01:50:13.820 align:start position:0% cool is that the the hardest thing is not<01:50:11.969> writing<01:50:12.330> state-transition<01:50:12.830> wasn't 01:50:13.820 --> 01:50:13.830 align:start position:0% not writing state-transition wasn't 01:50:13.830 --> 01:50:15.950 align:start position:0% not writing state-transition wasn't actually<01:50:14.310> including<01:50:15.179> the<01:50:15.449> including 01:50:15.950 --> 01:50:15.960 align:start position:0% actually including the including 01:50:15.960 --> 01:50:18.200 align:start position:0% actually including the including skeleton<01:50:16.679> runtime<01:50:17.130> the<01:50:17.370> hardest<01:50:17.730> part<01:50:17.969> of<01:50:18.090> all 01:50:18.200 --> 01:50:18.210 align:start position:0% skeleton runtime the hardest part of all 01:50:18.210 --> 01:50:21.649 align:start position:0% skeleton runtime the hardest part of all is<01:50:19.250> excuse<01:50:20.250> me<01:50:20.280> the<01:50:20.400> hardest<01:50:21.179> part<01:50:21.270> of<01:50:21.540> all 01:50:21.649 --> 01:50:21.659 align:start position:0% is excuse me the hardest part of all 01:50:21.659 --> 01:50:24.860 align:start position:0% is excuse me the hardest part of all this<01:50:21.900> was<01:50:22.699> just<01:50:23.699> getting<01:50:23.969> everything<01:50:24.300> before 01:50:24.860 --> 01:50:24.870 align:start position:0% this was just getting everything before 01:50:24.870 --> 01:50:28.280 align:start position:0% this was just getting everything before choice<01:50:25.080> all<01:50:25.500> of<01:50:25.739> the<01:50:25.920> the<01:50:26.810> vs<01:50:27.810> and<01:50:27.989> store 01:50:28.280 --> 01:50:28.290 align:start position:0% choice all of the the vs and store 01:50:28.290 --> 01:50:30.520 align:start position:0% choice all of the the vs and store everything<01:50:28.679> like<01:50:28.920> that<01:50:28.949> to<01:50:29.790> all<01:50:29.969> all 01:50:30.520 --> 01:50:30.530 align:start position:0% everything like that to all all 01:50:30.530 --> 01:50:34.189 align:start position:0% everything like that to all all proximate<01:50:31.530> ended<01:50:31.860> and<01:50:32.010> so<01:50:32.659> anyways<01:50:33.659> this<01:50:33.900> this 01:50:34.189 --> 01:50:34.199 align:start position:0% proximate ended and so anyways this this 01:50:34.199 --> 01:50:35.990 align:start position:0% proximate ended and so anyways this this should<01:50:34.440> ultimately<01:50:34.980> have<01:50:35.219> to<01:50:35.370> clean<01:50:35.610> up<01:50:35.639> to<01:50:35.850> be 01:50:35.990 --> 01:50:36.000 align:start position:0% should ultimately have to clean up to be 01:50:36.000 --> 01:50:39.890 align:start position:0% should ultimately have to clean up to be pulled<01:50:36.510> into<01:50:36.900> a<01:50:37.830> discount<01:50:38.489> or<01:50:38.900> initially 01:50:39.890 --> 01:50:39.900 align:start position:0% pulled into a discount or initially 01:50:39.900 --> 01:50:42.229 align:start position:0% pulled into a discount or initially maybe<01:50:40.080> into<01:50:40.350> the<01:50:40.440> lighthouse<01:50:40.770> areevo 01:50:42.229 --> 01:50:42.239 align:start position:0% maybe into the lighthouse areevo 01:50:42.239 --> 01:50:46.879 align:start position:0% maybe into the lighthouse areevo the<01:50:43.429> actually<01:50:44.429> plugging<01:50:45.000> in<01:50:45.620> scalp<01:50:46.620> and<01:50:46.830> a 01:50:46.879 --> 01:50:46.889 align:start position:0% the actually plugging in scalp and a 01:50:46.889 --> 01:50:49.240 align:start position:0% the actually plugging in scalp and a runtime<01:50:47.280> into<01:50:47.610> the<01:50:47.699> node<01:50:47.909> was<01:50:48.780> actually 01:50:49.240 --> 01:50:49.250 align:start position:0% runtime into the node was actually 01:50:49.250 --> 01:50:52.910 align:start position:0% runtime into the node was actually surprisingly<01:50:50.250> simple<01:50:51.409> and<01:50:52.409> that's<01:50:52.590> that's 01:50:52.910 --> 01:50:52.920 align:start position:0% surprisingly simple and that's that's 01:50:52.920 --> 01:50:54.950 align:start position:0% surprisingly simple and that's that's really<01:50:53.070> cool<01:50:53.400> and<01:50:53.670> so<01:50:53.909> this<01:50:54.270> is<01:50:54.449> really<01:50:54.480> good 01:50:54.950 --> 01:50:54.960 align:start position:0% really cool and so this is really good 01:50:54.960 --> 01:50:59.560 align:start position:0% really cool and so this is really good for<01:50:55.170> that<01:50:56.130> client<01:50:56.489> developers<01:50:57.409> in<01:50:58.409> this<01:50:58.650> case 01:50:59.560 --> 01:50:59.570 align:start position:0% for that client developers in this case 01:50:59.570 --> 01:51:03.260 align:start position:0% for that client developers in this case oh<01:51:00.620> we<01:51:01.620> really<01:51:02.010> have<01:51:02.400> is<01:51:02.639> in<01:51:02.790> the<01:51:02.969> state 01:51:03.260 --> 01:51:03.270 align:start position:0% oh we really have is in the state 01:51:03.270 --> 01:51:04.820 align:start position:0% oh we really have is in the state transition<01:51:03.750> for<01:51:03.900> a<01:51:03.960> process<01:51:04.199> shark<01:51:04.560> walk 01:51:04.820 --> 01:51:04.830 align:start position:0% transition for a process shark walk 01:51:04.830 --> 01:51:07.280 align:start position:0% transition for a process shark walk bunny<01:51:05.270> wickedest<01:51:06.270> instantiate<01:51:06.810> a<01:51:06.840> runtime 01:51:07.280 --> 01:51:07.290 align:start position:0% bunny wickedest instantiate a runtime 01:51:07.290 --> 01:51:08.750 align:start position:0% bunny wickedest instantiate a runtime right<01:51:07.590> now<01:51:07.739> we're<01:51:07.889> passing<01:51:08.040> the<01:51:08.280> block<01:51:08.489> body 01:51:08.750 --> 01:51:08.760 align:start position:0% right now we're passing the block body 01:51:08.760 --> 01:51:11.810 align:start position:0% right now we're passing the block body again<01:51:09.510> this<01:51:09.630> is<01:51:09.840> an<01:51:10.110> early<01:51:10.469> prototype<01:51:10.860> this 01:51:11.810 --> 01:51:11.820 align:start position:0% again this is an early prototype this 01:51:11.820 --> 01:51:13.910 align:start position:0% again this is an early prototype this who<01:51:11.969> really<01:51:12.239> just<01:51:12.389> accessed<01:51:12.929> the<01:51:13.139> beacon 01:51:13.910 --> 01:51:13.920 align:start position:0% who really just accessed the beacon 01:51:13.920 --> 01:51:16.610 align:start position:0% who really just accessed the beacon state<01:51:14.130> and<01:51:14.340> a<01:51:14.370> shard<01:51:14.610> state<01:51:14.900> and<01:51:15.900> then<01:51:16.230> you 01:51:16.610 --> 01:51:16.620 align:start position:0% state and a shard state and then you 01:51:16.620 --> 01:51:18.420 align:start position:0% state and a shard state and then you have<01:51:17.070> functions<01:51:17.280> other<01:51:17.760> than<01:51:17.850> Eric 01:51:18.420 --> 01:51:18.430 align:start position:0% have functions other than Eric 01:51:18.430 --> 01:51:20.910 align:start position:0% have functions other than Eric that<01:51:18.750> that<01:51:19.750> can<01:51:19.900> interact<01:51:20.110> at<01:51:20.380> that<01:51:20.560> so<01:51:20.770> this 01:51:20.910 --> 01:51:20.920 align:start position:0% that that can interact at that so this 01:51:20.920 --> 01:51:24.390 align:start position:0% that that can interact at that so this is<01:51:21.100> a<01:51:21.130> fairly<01:51:21.850> simple<01:51:22.120> again<01:51:22.900> this<01:51:23.260> will<01:51:23.980> need 01:51:24.390 --> 01:51:24.400 align:start position:0% is a fairly simple again this will need 01:51:24.400 --> 01:51:26.220 align:start position:0% is a fairly simple again this will need to<01:51:24.460> be<01:51:24.580> expanded<01:51:25.450> to<01:51:25.630> where<01:51:25.810> you<01:51:25.930> can<01:51:26.050> do 01:51:26.220 --> 01:51:26.230 align:start position:0% to be expanded to where you can do 01:51:26.230 --> 01:51:29.730 align:start position:0% to be expanded to where you can do interactive<01:51:26.860> deployments<01:51:27.730> of<01:51:27.850> annuities<01:51:28.740> and 01:51:29.730 --> 01:51:29.740 align:start position:0% interactive deployments of annuities and 01:51:29.740 --> 01:52:09.200 align:start position:0% interactive deployments of annuities and some<01:51:30.010> of<01:51:30.130> the<01:51:30.250> logic 01:52:09.200 --> 01:52:09.210 align:start position:0% 01:52:09.210 --> 01:52:12.150 align:start position:0% gotcha<01:52:10.210> yes<01:52:10.510> that's<01:52:10.930> that's<01:52:11.290> something<01:52:11.650> that 01:52:12.150 --> 01:52:12.160 align:start position:0% gotcha yes that's that's something that 01:52:12.160 --> 01:52:15.930 align:start position:0% gotcha yes that's that's something that I'm<01:52:12.400> gonna<01:52:12.700> start<01:52:13.060> doing<01:52:14.580> after<01:52:15.580> the<01:52:15.640> DEF<01:52:15.760> CON 01:52:15.930 --> 01:52:15.940 align:start position:0% I'm gonna start doing after the DEF CON 01:52:15.940 --> 01:52:19.410 align:start position:0% I'm gonna start doing after the DEF CON actually<01:52:16.600> so<01:52:16.900> I<01:52:16.930> want<01:52:17.140> to<01:52:17.200> start<01:52:17.730> so<01:52:18.730> quote<01:52:19.150> has 01:52:19.410 --> 01:52:19.420 align:start position:0% actually so I want to start so quote has 01:52:19.420 --> 01:52:22.230 align:start position:0% actually so I want to start so quote has grown<01:52:20.050> we<01:52:20.680> have<01:52:20.830> a<01:52:20.860> really<01:52:21.220> awesome<01:52:21.670> team<01:52:22.030> of 01:52:22.230 --> 01:52:22.240 align:start position:0% grown we have a really awesome team of 01:52:22.240 --> 01:52:26.720 align:start position:0% grown we have a really awesome team of really<01:52:22.450> awesome<01:52:23.040> and<01:52:24.040> engineers<01:52:24.670> and<01:52:25.330> so<01:52:25.630> I<01:52:25.960> am 01:52:26.720 --> 01:52:26.730 align:start position:0% really awesome and engineers and so I am 01:52:26.730 --> 01:52:29.250 align:start position:0% really awesome and engineers and so I am going<01:52:27.730> to<01:52:27.880> probably<01:52:28.060> start<01:52:28.540> migrating<01:52:28.750> to 01:52:29.250 --> 01:52:29.260 align:start position:0% going to probably start migrating to 01:52:29.260 --> 01:52:30.900 align:start position:0% going to probably start migrating to myself<01:52:29.440> I'll<01:52:29.770> start<01:52:30.010> working<01:52:30.250> on<01:52:30.490> building 01:52:30.900 --> 01:52:30.910 align:start position:0% myself I'll start working on building 01:52:30.910 --> 01:52:32.640 align:start position:0% myself I'll start working on building simulations<01:52:31.870> that<01:52:31.900> will<01:52:32.080> plug<01:52:32.260> into<01:52:32.440> this 01:52:32.640 --> 01:52:32.650 align:start position:0% simulations that will plug into this 01:52:32.650 --> 01:52:35.160 align:start position:0% simulations that will plug into this from<01:52:33.160> the<01:52:33.310> state<01:52:33.550> provide<01:52:33.820> the<01:52:33.940> network<01:52:34.170> and 01:52:35.160 --> 01:52:35.170 align:start position:0% from the state provide the network and 01:52:35.170 --> 01:52:36.420 align:start position:0% from the state provide the network and the<01:52:35.230> relay<01:52:35.470> network<01:52:35.770> so<01:52:35.980> I'm<01:52:36.070> gonna<01:52:36.160> start 01:52:36.420 --> 01:52:36.430 align:start position:0% the relay network so I'm gonna start 01:52:36.430 --> 01:52:38.640 align:start position:0% the relay network so I'm gonna start doing<01:52:36.640> some<01:52:36.820> early<01:52:37.240> research<01:52:37.720> on<01:52:38.080> that<01:52:38.200> since 01:52:38.640 --> 01:52:38.650 align:start position:0% doing some early research on that since 01:52:38.650 --> 01:52:42.090 align:start position:0% doing some early research on that since we<01:52:38.800> really<01:52:39.310> need<01:52:39.430> to<01:52:39.520> validate<01:52:39.850> that<01:52:40.890> as<01:52:41.890> far 01:52:42.090 --> 01:52:42.100 align:start position:0% we really need to validate that as far 01:52:42.100 --> 01:52:43.110 align:start position:0% we really need to validate that as far as<01:52:42.130> what<01:52:42.280> you<01:52:42.370> were<01:52:42.460> saying<01:52:42.700> the<01:52:42.790> token 01:52:43.110 --> 01:52:43.120 align:start position:0% as what you were saying the token 01:52:43.120 --> 01:52:46.770 align:start position:0% as what you were saying the token economy<01:52:43.600> and<01:52:43.810> pain<01:52:44.230> a<01:52:44.260> block<01:52:44.620> producer<01:52:45.780> so 01:52:46.770 --> 01:52:46.780 align:start position:0% economy and pain a block producer so 01:52:46.780 --> 01:52:48.900 align:start position:0% economy and pain a block producer so again<01:52:47.140> it<01:52:47.260> depends<01:52:47.590> on<01:52:47.680> which<01:52:47.860> proposal<01:52:48.640> we<01:52:48.730> go 01:52:48.900 --> 01:52:48.910 align:start position:0% again it depends on which proposal we go 01:52:48.910 --> 01:52:50.730 align:start position:0% again it depends on which proposal we go with<01:52:49.090> so<01:52:49.360> the<01:52:49.480> tall<01:52:49.660> cuz<01:52:49.900> if<01:52:50.020> you<01:52:50.050> want<01:52:50.320> that 01:52:50.730 --> 01:52:50.740 align:start position:0% with so the tall cuz if you want that 01:52:50.740 --> 01:52:54.980 align:start position:0% with so the tall cuz if you want that kind<01:52:50.890> of<01:52:50.980> enshrines<01:52:52.440> into<01:52:53.440> the<01:52:53.530> charts 01:52:54.980 --> 01:52:54.990 align:start position:0% kind of enshrines into the charts 01:52:54.990 --> 01:52:58.740 align:start position:0% kind of enshrines into the charts if<01:52:55.990> we<01:52:56.500> go<01:52:56.680> in<01:52:56.800> that<01:52:56.830> direction<01:52:56.980> this<01:52:57.490> makes<01:52:57.790> my 01:52:58.740 --> 01:52:58.750 align:start position:0% if we go in that direction this makes my 01:52:58.750 --> 01:53:01.260 align:start position:0% if we go in that direction this makes my work<01:52:59.290> a<01:52:59.560> lot<01:52:59.920> easier<01:53:00.160> and<01:53:00.700> I'm<01:53:01.060> actually 01:53:01.260 --> 01:53:01.270 align:start position:0% work a lot easier and I'm actually 01:53:01.270 --> 01:53:03.120 align:start position:0% work a lot easier and I'm actually fairly<01:53:01.540> excited<01:53:02.080> about<01:53:02.260> that<01:53:02.470> one<01:53:02.590> but<01:53:02.860> again 01:53:03.120 --> 01:53:03.130 align:start position:0% fairly excited about that one but again 01:53:03.130 --> 01:53:05.970 align:start position:0% fairly excited about that one but again each<01:53:03.490> proposal<01:53:04.450> has<01:53:04.810> pros<01:53:05.290> a<01:53:05.320> trade<01:53:05.800> off<01:53:05.950> so 01:53:05.970 --> 01:53:05.980 align:start position:0% each proposal has pros a trade off so 01:53:05.980 --> 01:53:06.850 align:start position:0% each proposal has pros a trade off so it's<01:53:06.400> also 01:53:06.850 --> 01:53:06.860 align:start position:0% it's also 01:53:06.860 --> 01:53:10.090 align:start position:0% it's also like<01:53:07.449> what<01:53:08.449> do<01:53:08.630> developers<01:53:09.290> you<01:53:09.770> know<01:53:09.800> in<01:53:10.010> this 01:53:10.090 --> 01:53:10.100 align:start position:0% like what do developers you know in this 01:53:10.100 --> 01:53:12.340 align:start position:0% like what do developers you know in this ecosystem<01:53:10.369> want<01:53:10.909> and<01:53:11.119> I<01:53:11.179> think<01:53:11.449> we'll 01:53:12.340 --> 01:53:12.350 align:start position:0% ecosystem want and I think we'll 01:53:12.350 --> 01:53:14.439 align:start position:0% ecosystem want and I think we'll probably<01:53:12.500> dive<01:53:12.889> into<01:53:13.100> the<01:53:13.250> people<01:53:13.610> into<01:53:14.270> some 01:53:14.439 --> 01:53:14.449 align:start position:0% probably dive into the people into some 01:53:14.449 --> 01:53:15.850 align:start position:0% probably dive into the people into some of<01:53:14.510> the<01:53:14.570> meter<01:53:14.780> that<01:53:14.900> tomorrow<01:53:15.469> in<01:53:15.710> these 01:53:15.850 --> 01:53:15.860 align:start position:0% of the meter that tomorrow in these 01:53:15.860 --> 01:53:18.790 align:start position:0% of the meter that tomorrow in these sessions<01:53:16.070> as<01:53:16.699> well<01:53:17.080> I<01:53:18.080> don't<01:53:18.500> know<01:53:18.590> if<01:53:18.650> that 01:53:18.790 --> 01:53:18.800 align:start position:0% sessions as well I don't know if that 01:53:18.800 --> 01:53:21.160 align:start position:0% sessions as well I don't know if that that<01:53:19.130> like<01:53:19.400> answered<01:53:20.150> your<01:53:20.270> question<01:53:20.630> but<01:53:20.840> in 01:53:21.160 --> 01:53:21.170 align:start position:0% that like answered your question but in 01:53:21.170 --> 01:53:24.129 align:start position:0% that like answered your question but in in<01:53:21.650> in<01:53:22.130> this<01:53:22.369> system<01:53:22.760> where<01:53:22.940> sharp<01:53:23.270> either<01:53:23.869> as 01:53:24.129 --> 01:53:24.139 align:start position:0% in in this system where sharp either as 01:53:24.139 --> 01:53:27.250 align:start position:0% in in this system where sharp either as march<01:53:24.380> right<01:53:25.060> it<01:53:26.060> becomes<01:53:26.420> more<01:53:26.750> of<01:53:26.810> a<01:53:26.960> system 01:53:27.250 --> 01:53:27.260 align:start position:0% march right it becomes more of a system 01:53:27.260 --> 01:53:29.169 align:start position:0% march right it becomes more of a system of<01:53:27.350> just<01:53:27.530> stay<01:53:27.739> providers<01:53:28.250> how<01:53:28.610> do<01:53:28.670> you<01:53:28.820> pay 01:53:29.169 --> 01:53:29.179 align:start position:0% of just stay providers how do you pay 01:53:29.179 --> 01:53:32.740 align:start position:0% of just stay providers how do you pay some<01:53:29.449> ones<01:53:29.630> that<01:53:29.690> provide<01:53:30.080> state<01:53:30.790> if<01:53:31.790> ether<01:53:32.570> is 01:53:32.740 --> 01:53:32.750 align:start position:0% some ones that provide state if ether is 01:53:32.750 --> 01:53:36.430 align:start position:0% some ones that provide state if ether is less<01:53:33.080> enshrined<01:53:34.600> if<01:53:35.600> you<01:53:35.780> need<01:53:35.989> a<01:53:36.020> whole 01:53:36.430 --> 01:53:36.440 align:start position:0% less enshrined if you need a whole 01:53:36.440 --> 01:53:38.620 align:start position:0% less enshrined if you need a whole system<01:53:37.010> it<01:53:37.400> becomes<01:53:38.030> a<01:53:38.210> little<01:53:38.389> bit<01:53:38.510> more 01:53:38.620 --> 01:53:38.630 align:start position:0% system it becomes a little bit more 01:53:38.630 --> 01:53:43.270 align:start position:0% system it becomes a little bit more complex<01:53:39.699> because<01:53:40.699> the<01:53:40.880> block<01:53:41.090> producers<01:53:42.280> need 01:53:43.270 --> 01:53:43.280 align:start position:0% complex because the block producers need 01:53:43.280 --> 01:53:49.090 align:start position:0% complex because the block producers need to<01:53:44.679> basically<01:53:46.270> need<01:53:47.270> to<01:53:47.300> have<01:53:47.750> some<01:53:48.619> level<01:53:49.070> of 01:53:49.090 --> 01:53:49.100 align:start position:0% to basically need to have some level of 01:53:49.100 --> 01:53:50.770 align:start position:0% to basically need to have some level of trust<01:53:49.340> with<01:53:49.489> the<01:53:49.639> real<01:53:49.790> layers<01:53:49.969> and<01:53:50.239> and 01:53:50.770 --> 01:53:50.780 align:start position:0% trust with the real layers and and 01:53:50.780 --> 01:53:52.180 align:start position:0% trust with the real layers and and there's<01:53:50.929> some<01:53:51.080> complexity<01:53:51.530> there<01:53:51.860> where<01:53:52.100> is 01:53:52.180 --> 01:53:52.190 align:start position:0% there's some complexity there where is 01:53:52.190 --> 01:53:54.430 align:start position:0% there's some complexity there where is it<01:53:52.310> in<01:53:52.610> this<01:53:53.090> new<01:53:53.360> model<01:53:53.540> that<01:53:53.780> he's<01:53:54.110> proposed 01:53:54.430 --> 01:53:54.440 align:start position:0% it in this new model that he's proposed 01:53:54.440 --> 01:53:57.850 align:start position:0% it in this new model that he's proposed they<01:53:54.619> don't<01:53:54.830> they<01:53:55.130> don't<01:53:55.159> and<01:53:55.670> and<01:53:56.239> so<01:53:57.020> yeah 01:53:57.850 --> 01:53:57.860 align:start position:0% they don't they don't and and so yeah 01:53:57.860 --> 01:53:59.890 align:start position:0% they don't they don't and and so yeah it's<01:53:58.550> a<01:53:58.699> higher<01:53:59.000> level<01:53:59.030> overview<01:53:59.540> without 01:53:59.890 --> 01:53:59.900 align:start position:0% it's a higher level overview without 01:53:59.900 --> 01:54:01.419 align:start position:0% it's a higher level overview without studying<01:54:00.170> ten<01:54:00.679> minutes<01:54:00.920> talking<01:54:01.040> about<01:54:01.250> it 01:54:01.419 --> 01:54:01.429 align:start position:0% studying ten minutes talking about it 01:54:01.429 --> 01:54:03.910 align:start position:0% studying ten minutes talking about it yeah<01:54:02.000> because<01:54:02.150> it's<01:54:02.420> like<01:54:02.480> but<01:54:03.230> flooring 01:54:03.910 --> 01:54:03.920 align:start position:0% yeah because it's like but flooring 01:54:03.920 --> 01:54:05.979 align:start position:0% yeah because it's like but flooring questions<01:54:04.460> though<01:54:04.670> because<01:54:04.969> this<01:54:05.420> talking<01:54:05.780> is 01:54:05.979 --> 01:54:05.989 align:start position:0% questions though because this talking is 01:54:05.989 --> 01:54:09.189 align:start position:0% questions though because this talking is incentive<01:54:07.090> also<01:54:08.090> have<01:54:08.239> changes<01:54:08.719> a<01:54:08.960> lot<01:54:09.110> of 01:54:09.189 --> 01:54:09.199 align:start position:0% incentive also have changes a lot of 01:54:09.199 --> 01:54:12.560 align:start position:0% incentive also have changes a lot of behaviors<01:54:09.770> of<01:54:10.010> like<01:54:10.310> state<01:54:10.850> fighters<01:54:11.179> and 01:54:12.560 --> 01:54:12.570 align:start position:0% behaviors of like state fighters and 01:54:12.570 --> 01:54:15.550 align:start position:0% behaviors of like state fighters and but<01:54:13.110> a<01:54:13.140> bit<01:54:13.350> Ursuline<01:54:14.040> and<01:54:14.370> in<01:54:14.460> such<01:54:14.670> case 01:54:15.550 --> 01:54:15.560 align:start position:0% but a bit Ursuline and in such case 01:54:15.560 --> 01:54:18.380 align:start position:0% but a bit Ursuline and in such case maybe<01:54:16.560> the<01:54:16.739> sooner<01:54:16.950> they<01:54:17.100> forget<01:54:17.430> how<01:54:17.670> to<01:54:18.090> we 01:54:18.380 --> 01:54:18.390 align:start position:0% maybe the sooner they forget how to we 01:54:18.390 --> 01:54:21.459 align:start position:0% maybe the sooner they forget how to we can<01:54:18.570> explain<01:54:18.930> those<01:54:19.170> they<01:54:19.920> call<01:54:20.130> me<01:54:20.219> their 01:54:21.459 --> 01:54:21.469 align:start position:0% can explain those they call me their 01:54:21.469 --> 01:54:22.670 align:start position:0% can explain those they call me their solutions 01:54:22.670 --> 01:54:22.680 align:start position:0% solutions 01:54:22.680 --> 01:54:24.290 align:start position:0% solutions yeah<01:54:22.950> that's<01:54:23.160> the<01:54:23.280> goal<01:54:23.400> and<01:54:23.730> then<01:54:23.880> have<01:54:24.270> it 01:54:24.290 --> 01:54:24.300 align:start position:0% yeah that's the goal and then have it 01:54:24.300 --> 01:54:27.950 align:start position:0% yeah that's the goal and then have it have<01:54:24.690> it<01:54:24.719> be<01:54:25.550> have<01:54:26.550> some<01:54:26.580> actual<01:54:27.090> does<01:54:27.719> not 01:54:27.950 --> 01:54:27.960 align:start position:0% have it be have some actual does not 01:54:27.960 --> 01:54:29.600 align:start position:0% have it be have some actual does not well-defined<01:54:28.170> right<01:54:28.680> it's<01:54:29.160> not<01:54:29.370> well-defined 01:54:29.600 --> 01:54:29.610 align:start position:0% well-defined right it's not well-defined 01:54:29.610 --> 01:54:30.470 align:start position:0% well-defined right it's not well-defined yeah<01:54:30.030> yeah 01:54:30.470 --> 01:54:30.480 align:start position:0% yeah yeah 01:54:30.480 --> 01:54:34.580 align:start position:0% yeah yeah and<01:54:30.570> so<01:54:30.750> I<01:54:30.780> think<01:54:31.080> we<01:54:31.380> need<01:54:32.270> we<01:54:33.270> need<01:54:33.300> just<01:54:33.690> you 01:54:34.580 --> 01:54:34.590 align:start position:0% and so I think we need we need just you 01:54:34.590 --> 01:54:36.050 align:start position:0% and so I think we need we need just you know<01:54:34.710> a<01:54:34.860> little<01:54:35.100> time<01:54:35.340> first<01:54:35.610> to<01:54:35.730> figure<01:54:35.880> out 01:54:36.050 --> 01:54:36.060 align:start position:0% know a little time first to figure out 01:54:36.060 --> 01:54:38.720 align:start position:0% know a little time first to figure out what<01:54:36.239> people<01:54:36.690> so<01:54:36.840> we're<01:54:37.080> gonna<01:54:37.170> go<01:54:37.350> with<01:54:37.730> and 01:54:38.720 --> 01:54:38.730 align:start position:0% what people so we're gonna go with and 01:54:38.730 --> 01:54:42.979 align:start position:0% what people so we're gonna go with and maybe<01:54:39.090> some<01:54:39.630> of<01:54:39.810> the<01:54:40.969> some<01:54:41.969> of<01:54:42.000> the<01:54:42.360> direction 01:54:42.979 --> 01:54:42.989 align:start position:0% maybe some of the some of the direction 01:54:42.989 --> 01:54:45.080 align:start position:0% maybe some of the some of the direction of<01:54:43.080> the<01:54:43.230> research<01:54:43.530> that<01:54:43.560> you<01:54:44.340> know<01:54:44.430> or<01:54:44.850> dive 01:54:45.080 --> 01:54:45.090 align:start position:0% of the research that you know or dive 01:54:45.090 --> 01:54:47.240 align:start position:0% of the research that you know or dive into<01:54:45.120> it<01:54:45.630> and<01:54:45.750> also<01:54:45.930> John<01:54:46.230> Adler<01:54:46.469> is<01:54:46.890> going<01:54:47.160> to 01:54:47.240 --> 01:54:47.250 align:start position:0% into it and also John Adler is going to 01:54:47.250 --> 01:54:48.709 align:start position:0% into it and also John Adler is going to be<01:54:47.520> diving<01:54:47.700> into<01:54:48.060> as<01:54:48.180> well 01:54:48.709 --> 01:54:48.719 align:start position:0% be diving into as well 01:54:48.719 --> 01:54:52.190 align:start position:0% be diving into as well John<01:54:49.440> raise<01:54:49.860> their<01:54:50.010> hands<01:54:50.310> yeah<01:54:51.200> regarding 01:54:52.190 --> 01:54:52.200 align:start position:0% John raise their hands yeah regarding 01:54:52.200 --> 01:54:54.380 align:start position:0% John raise their hands yeah regarding this<01:54:52.320> thing<01:54:52.620> you<01:54:53.160> know<01:54:53.280> can<01:54:53.489> also<01:54:53.610> help<01:54:53.940> fuel 01:54:54.380 --> 01:54:54.390 align:start position:0% this thing you know can also help fuel 01:54:54.390 --> 01:54:55.840 align:start position:0% this thing you know can also help fuel that<01:54:54.780> direction 01:54:55.840 --> 01:54:55.850 align:start position:0% that direction 01:54:55.850 --> 01:55:01.010 align:start position:0% that direction yeah<01:54:58.790> is<01:54:59.790> anyone<01:55:00.120> interested<01:55:00.330> in<01:55:00.719> giving 01:55:01.010 --> 01:55:01.020 align:start position:0% yeah is anyone interested in giving 01:55:01.020 --> 01:55:03.650 align:start position:0% yeah is anyone interested in giving markets<01:55:01.770> new<01:55:02.280> markets<01:55:02.670> like<01:55:03.390> getting 01:55:03.650 --> 01:55:03.660 align:start position:0% markets new markets like getting 01:55:03.660 --> 01:55:05.570 align:start position:0% markets new markets like getting involved<01:55:04.020> in<01:55:04.140> that<01:55:04.230> area<01:55:04.440> if<01:55:04.650> you<01:55:04.830> are<01:55:04.890> like<01:55:05.340> to 01:55:05.570 --> 01:55:05.580 align:start position:0% involved in that area if you are like to 01:55:05.580 --> 01:55:09.140 align:start position:0% involved in that area if you are like to free<01:55:05.790> today<01:55:05.969> take<01:55:06.930> your<01:55:07.020> hand<01:55:07.230> up<01:55:07.670> yeah<01:55:08.670> okay 01:55:09.140 --> 01:55:09.150 align:start position:0% free today take your hand up yeah okay 01:55:09.150 --> 01:55:09.650 align:start position:0% free today take your hand up yeah okay awesome 01:55:09.650 --> 01:55:09.660 align:start position:0% awesome 01:55:09.660 --> 01:55:13.430 align:start position:0% awesome cool<01:55:09.900> let's<01:55:10.530> talk<01:55:10.770> yeah<01:55:11.190> let's<01:55:11.610> see<01:55:12.290> any<01:55:13.290> other 01:55:13.430 --> 01:55:13.440 align:start position:0% cool let's talk yeah let's see any other 01:55:13.440 --> 01:55:19.690 align:start position:0% cool let's talk yeah let's see any other questions<01:55:14.450> yes<01:55:17.150> something<01:55:18.150> allowed<01:55:18.450> here<01:55:18.750> but 01:55:19.690 --> 01:55:19.700 align:start position:0% questions yes something allowed here but 01:55:19.700 --> 01:55:23.690 align:start position:0% questions yes something allowed here but is<01:55:20.700> it<01:55:20.880> feasible<01:55:21.239> in<01:55:21.989> a<01:55:22.230> way<01:55:22.440> that<01:55:22.800> like<01:55:23.130> say<01:55:23.460> we 01:55:23.690 --> 01:55:23.700 align:start position:0% is it feasible in a way that like say we 01:55:23.700 --> 01:55:26.450 align:start position:0% is it feasible in a way that like say we can<01:55:23.880> open<01:55:24.660> up<01:55:24.840> an<01:55:25.050> area<01:55:25.320> in<01:55:25.530> the<01:55:25.560> memory<01:55:26.100> say 01:55:26.450 --> 01:55:26.460 align:start position:0% can open up an area in the memory say 01:55:26.460 --> 01:55:30.470 align:start position:0% can open up an area in the memory say this<01:55:26.760> area<01:55:27.750> is<01:55:28.320> gonna<01:55:28.650> be<01:55:28.920> there<01:55:29.219> for<01:55:30.180> the<01:55:30.270> sake 01:55:30.470 --> 01:55:30.480 align:start position:0% this area is gonna be there for the sake 01:55:30.480 --> 01:55:32.900 align:start position:0% this area is gonna be there for the sake of<01:55:30.690> this<01:55:31.080> entire<01:55:31.620> block<01:55:32.040> of<01:55:32.070> transactions 01:55:32.900 --> 01:55:32.910 align:start position:0% of this entire block of transactions 01:55:32.910 --> 01:55:35.870 align:start position:0% of this entire block of transactions execution<01:55:33.630> so<01:55:33.900> that<01:55:34.080> let's<01:55:34.320> say<01:55:34.640> when<01:55:35.640> you<01:55:35.730> do 01:55:35.870 --> 01:55:35.880 align:start position:0% execution so that let's say when you do 01:55:35.880 --> 01:55:40.300 align:start position:0% execution so that let's say when you do like<01:55:36.030> stainless<01:55:36.390> things<01:55:38.480> like<01:55:39.480> maybe<01:55:39.900> they're 01:55:40.300 --> 01:55:40.310 align:start position:0% like stainless things like maybe they're 01:55:40.310 --> 01:55:43.190 align:start position:0% like stainless things like maybe they're public<01:55:41.310> in<01:55:41.430> sections<01:55:41.820> technic<01:55:42.750> stopping<01:55:43.110> the 01:55:43.190 --> 01:55:43.200 align:start position:0% public in sections technic stopping the 01:55:43.200 --> 01:55:45.500 align:start position:0% public in sections technic stopping the same<01:55:43.380> uni<01:55:43.739> and<01:55:44.040> then<01:55:44.670> they<01:55:44.910> are<01:55:45.120> tied<01:55:45.420> to 01:55:45.500 --> 01:55:45.510 align:start position:0% same uni and then they are tied to 01:55:45.510 --> 01:55:47.150 align:start position:0% same uni and then they are tied to construct<01:55:45.900> a<01:55:46.020> tree<01:55:46.200> but<01:55:46.560> then<01:55:46.710> the<01:55:46.830> previous 01:55:47.150 --> 01:55:47.160 align:start position:0% construct a tree but then the previous 01:55:47.160 --> 01:55:48.650 align:start position:0% construct a tree but then the previous transaction<01:55:47.550> has<01:55:47.880> already<01:55:48.150> constructed<01:55:48.450> a 01:55:48.650 --> 01:55:48.660 align:start position:0% transaction has already constructed a 01:55:48.660 --> 01:55:50.900 align:start position:0% transaction has already constructed a part<01:55:48.900> of<01:55:49.020> the<01:55:49.140> tree<01:55:49.350> and<01:55:49.620> then<01:55:50.160> the<01:55:50.460> said<01:55:50.670> the 01:55:50.900 --> 01:55:50.910 align:start position:0% part of the tree and then the said the 01:55:50.910 --> 01:55:52.100 align:start position:0% part of the tree and then the said the following<01:55:51.239> one<01:55:51.390> is<01:55:51.420> constructed<01:55:51.960> another 01:55:52.100 --> 01:55:52.110 align:start position:0% following one is constructed another 01:55:52.110 --> 01:55:53.860 align:start position:0% following one is constructed another part<01:55:52.410> of<01:55:52.469> the<01:55:52.590> tree<01:55:52.770> and<01:55:53.040> those<01:55:53.520> up<01:55:53.700> because 01:55:53.860 --> 01:55:53.870 align:start position:0% part of the tree and those up because 01:55:53.870 --> 01:55:56.900 align:start position:0% part of the tree and those up because you<01:55:54.870> know<01:55:54.989> and<01:55:55.260> there's<01:55:55.739> apples<01:55:56.310> are<01:55:56.489> out<01:55:56.850> of 01:55:56.900 --> 01:55:56.910 align:start position:0% you know and there's apples are out of 01:55:56.910 --> 01:55:59.240 align:start position:0% you know and there's apples are out of date<01:55:57.330> in<01:55:57.570> the<01:55:57.719> same<01:55:57.900> tree<01:55:58.230> right<01:55:58.620> then<01:55:58.920> like 01:55:59.240 --> 01:55:59.250 align:start position:0% date in the same tree right then like 01:55:59.250 --> 01:56:01.459 align:start position:0% date in the same tree right then like then<01:55:59.550> conflicting<01:56:00.450> transactions<01:56:01.080> in<01:56:01.350> the 01:56:01.459 --> 01:56:01.469 align:start position:0% then conflicting transactions in the 01:56:01.469 --> 01:56:03.650 align:start position:0% then conflicting transactions in the same<01:56:01.650> block<01:56:01.920> can<01:56:02.160> go<01:56:02.280> together<01:56:02.460> because<01:56:03.090> you 01:56:03.650 --> 01:56:03.660 align:start position:0% same block can go together because you 01:56:03.660 --> 01:56:06.080 align:start position:0% same block can go together because you know<01:56:03.780> the<01:56:03.930> following<01:56:04.110> one<01:56:04.380> sees<01:56:04.800> oh<01:56:05.130> it's 01:56:06.080 --> 01:56:06.090 align:start position:0% know the following one sees oh it's 01:56:06.090 --> 01:56:07.280 align:start position:0% know the following one sees oh it's ready<01:56:06.270> to<01:56:06.300> update<01:56:06.630> the<01:56:06.750> someone<01:56:07.050> constructed 01:56:07.280 --> 01:56:07.290 align:start position:0% ready to update the someone constructed 01:56:07.290 --> 01:56:08.720 align:start position:0% ready to update the someone constructed I'm<01:56:07.680> just<01:56:07.890> gonna<01:56:08.010> use<01:56:08.219> it<01:56:08.400> instead<01:56:08.670> of 01:56:08.720 --> 01:56:08.730 align:start position:0% I'm just gonna use it instead of 01:56:08.730 --> 01:56:13.380 align:start position:0% I'm just gonna use it instead of reconstruct<01:56:09.450> approved<01:56:09.840> kind<01:56:10.050> of<01:56:10.140> thing 01:56:13.380 --> 01:56:13.390 align:start position:0% 01:56:13.390 --> 01:56:16.690 align:start position:0% what's<01:56:14.390> that<01:56:14.920> like<01:56:16.280> my<01:56:16.370> deal<01:56:16.550> with 01:56:16.690 --> 01:56:16.700 align:start position:0% what's that like my deal with 01:56:16.700 --> 01:56:19.350 align:start position:0% what's that like my deal with hustle<01:56:17.090> state<01:56:17.360> or<01:56:17.510> cash<01:56:17.750> flow<01:56:17.900> State<01:56:18.280> yeah 01:56:19.350 --> 01:56:19.360 align:start position:0% hustle state or cash flow State yeah 01:56:19.360 --> 01:56:23.490 align:start position:0% hustle state or cash flow State yeah that's<01:56:20.360> yeah<01:56:20.540> did<01:56:21.110> you<01:56:21.140> say<01:56:21.490> epic<01:56:22.490> caching<01:56:22.910> API 01:56:23.490 --> 01:56:23.500 align:start position:0% that's yeah did you say epic caching API 01:56:23.500 --> 01:56:27.010 align:start position:0% that's yeah did you say epic caching API under<01:56:24.500> consideration<01:56:25.420> you<01:56:26.420> guys<01:56:26.630> did<01:56:26.810> some 01:56:27.010 --> 01:56:27.020 align:start position:0% under consideration you guys did some 01:56:27.020 --> 01:56:30.220 align:start position:0% under consideration you guys did some tests<01:56:27.320> with<01:56:27.440> it<01:56:28.450> yeah<01:56:29.450> but<01:56:29.600> can<01:56:29.840> she<01:56:29.870> gave<01:56:30.110> me 01:56:30.220 --> 01:56:30.230 align:start position:0% tests with it yeah but can she gave me 01:56:30.230 --> 01:56:33.220 align:start position:0% tests with it yeah but can she gave me out<01:56:30.760> and<01:56:31.760> I<01:56:31.850> think<01:56:32.060> we<01:56:32.300> we<01:56:32.720> had<01:56:32.840> some<01:56:33.020> tests 01:56:33.220 --> 01:56:33.230 align:start position:0% out and I think we we had some tests 01:56:33.230 --> 01:56:41.139 align:start position:0% out and I think we we had some tests with<01:56:33.380> it<01:56:33.500> but<01:56:33.710> such<01:56:34.400> conclusive<01:56:34.910> yet 01:56:41.139 --> 01:56:41.149 align:start position:0% 01:56:41.149 --> 01:56:47.520 align:start position:0% any<01:56:41.689> other<01:56:41.809> pending<01:56:42.349> questions<01:56:45.070> questions<01:56:46.070> I 01:56:47.520 --> 01:56:47.530 align:start position:0% any other pending questions questions I 01:56:47.530 --> 01:56:53.430 align:start position:0% any other pending questions questions I think<01:56:48.530> so 01:56:53.430 --> 01:56:53.440 align:start position:0% 01:56:53.440 --> 01:57:02.550 align:start position:0% [Applause] 01:57:02.550 --> 01:57:02.560 align:start position:0% 01:57:02.560 --> 01:57:04.620 align:start position:0% you