WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.260 align:start position:0% [Applause] 00:00:12.260 --> 00:00:12.270 align:start position:0% 00:00:12.270 --> 00:00:14.760 align:start position:0% questions<00:00:13.270> they're<00:00:14.139> gonna<00:00:14.230> try<00:00:14.500> to<00:00:14.559> go 00:00:14.760 --> 00:00:14.770 align:start position:0% questions they're gonna try to go 00:00:14.770 --> 00:00:16.830 align:start position:0% questions they're gonna try to go through<00:00:15.010> but<00:00:15.730> if<00:00:15.850> any<00:00:16.000> of<00:00:16.090> you<00:00:16.330> have<00:00:16.570> a 00:00:16.830 --> 00:00:16.840 align:start position:0% through but if any of you have a 00:00:16.840 --> 00:00:19.019 align:start position:0% through but if any of you have a question<00:00:17.500> you<00:00:17.650> can<00:00:17.680> just<00:00:17.980> ask<00:00:18.160> it<00:00:18.369> or<00:00:18.610> a<00:00:18.640> CNN 00:00:19.019 --> 00:00:19.029 align:start position:0% question you can just ask it or a CNN 00:00:19.029 --> 00:00:20.970 align:start position:0% question you can just ask it or a CNN the<00:00:19.119> topic<00:00:19.540> you're<00:00:20.200> passionate<00:00:20.410> about<00:00:20.740> you 00:00:20.970 --> 00:00:20.980 align:start position:0% the topic you're passionate about you 00:00:20.980 --> 00:00:23.160 align:start position:0% the topic you're passionate about you can<00:00:21.099> also<00:00:21.250> just<00:00:21.520> move<00:00:21.700> up<00:00:21.880> here 00:00:23.160 --> 00:00:23.170 align:start position:0% can also just move up here 00:00:23.170 --> 00:00:27.470 align:start position:0% can also just move up here kick<00:00:23.890> me<00:00:24.040> out<00:00:24.189> sit<00:00:24.520> down<00:00:24.730> and<00:00:25.650> leave<00:00:26.650> the<00:00:26.740> topic 00:00:27.470 --> 00:00:27.480 align:start position:0% kick me out sit down and leave the topic 00:00:27.480 --> 00:00:50.220 align:start position:0% kick me out sit down and leave the topic but<00:00:28.480> if<00:00:28.600> you<00:00:28.690> don't<00:00:28.869> speak<00:00:29.439> up<00:00:49.110> even<00:00:50.110> though<00:00:50.200> I 00:00:50.220 --> 00:00:50.230 align:start position:0% but if you don't speak up even though I 00:00:50.230 --> 00:00:52.229 align:start position:0% but if you don't speak up even though I said<00:00:50.350> that<00:00:50.620> we<00:00:51.070> shouldn't<00:00:51.280> be<00:00:51.399> special<00:00:51.940> I 00:00:52.229 --> 00:00:52.239 align:start position:0% said that we shouldn't be special I 00:00:52.239 --> 00:00:53.729 align:start position:0% said that we shouldn't be special I think<00:00:52.780> you<00:00:52.870> guys<00:00:53.050> should<00:00:53.110> just<00:00:53.290> introduce 00:00:53.729 --> 00:00:53.739 align:start position:0% think you guys should just introduce 00:00:53.739 --> 00:00:56.369 align:start position:0% think you guys should just introduce yourself<00:00:54.250> like<00:00:54.430> in<00:00:54.579> a<00:00:54.610> one<00:00:55.300> sentence<00:00:55.780> and 00:00:56.369 --> 00:00:56.379 align:start position:0% yourself like in a one sentence and 00:00:56.379 --> 00:00:58.770 align:start position:0% yourself like in a one sentence and whoever<00:00:56.590> comes<00:00:56.800> scriptures<00:00:57.250> do<00:00:57.370> the<00:00:57.489> same<00:00:57.780> so 00:00:58.770 --> 00:00:58.780 align:start position:0% whoever comes scriptures do the same so 00:00:58.780 --> 00:01:01.619 align:start position:0% whoever comes scriptures do the same so then<00:00:58.960> if<00:00:59.410> you<00:00:59.500> want<00:00:59.649> to<00:00:59.710> start<00:00:59.969> everyone<00:01:00.969> my 00:01:01.619 --> 00:01:01.629 align:start position:0% then if you want to start everyone my 00:01:01.629 --> 00:01:05.229 align:start position:0% then if you want to start everyone my name<00:01:01.780> is<00:01:01.809> Leo<00:01:02.079> I<00:01:02.410> work<00:01:02.649> on 00:01:05.229 --> 00:01:05.239 align:start position:0% 00:01:05.239 --> 00:01:09.840 align:start position:0% [Music] 00:01:09.840 --> 00:01:09.850 align:start position:0% 00:01:09.850 --> 00:01:12.030 align:start position:0% it<00:01:10.180> could<00:01:10.689> help<00:01:10.900> them<00:01:11.200> now<00:01:11.350> they<00:01:11.590> need<00:01:11.740> to<00:01:11.770> be 00:01:12.030 --> 00:01:12.040 align:start position:0% it could help them now they need to be 00:01:12.040 --> 00:01:14.030 align:start position:0% it could help them now they need to be eating<00:01:12.310> their<00:01:12.909> juices 00:01:14.030 --> 00:01:14.040 align:start position:0% eating their juices 00:01:14.040 --> 00:01:22.770 align:start position:0% eating their juices hi<00:01:15.040> I'm<00:01:15.220> Chuck<00:01:19.830> hi<00:01:20.830> on<00:01:20.979> top<00:01:21.250> of<00:01:21.430> I<00:01:21.610> work<00:01:22.090> I 00:01:22.770 --> 00:01:22.780 align:start position:0% hi I'm Chuck hi on top of I work I 00:01:22.780 --> 00:01:26.609 align:start position:0% hi I'm Chuck hi on top of I work I mostly<00:01:23.259> do<00:01:23.680> EDM<00:01:24.930> and<00:01:25.930> my<00:01:26.080> mouth<00:01:26.259> except 00:01:26.609 --> 00:01:26.619 align:start position:0% mostly do EDM and my mouth except 00:01:26.619 --> 00:01:31.170 align:start position:0% mostly do EDM and my mouth except working<00:01:26.950> on<00:01:27.100> solidity<00:01:27.729> wasn't<00:01:29.789> the<00:01:30.789> case<00:01:30.940> here 00:01:31.170 --> 00:01:31.180 align:start position:0% working on solidity wasn't the case here 00:01:31.180 --> 00:01:35.550 align:start position:0% working on solidity wasn't the case here muscle<00:01:31.450> for<00:01:31.990> them<00:01:32.140> it<00:01:32.530> wasn't<00:01:34.259> alright<00:01:35.259> let's 00:01:35.550 --> 00:01:35.560 align:start position:0% muscle for them it wasn't alright let's 00:01:35.560 --> 00:01:40.139 align:start position:0% muscle for them it wasn't alright let's jump<00:01:36.009> in<00:01:36.310> to<00:01:36.670> some<00:01:37.240> of<00:01:37.270> these<00:01:37.450> questions<00:01:39.149> maybe 00:01:40.139 --> 00:01:40.149 align:start position:0% jump in to some of these questions maybe 00:01:40.149 --> 00:01:47.160 align:start position:0% jump in to some of these questions maybe start<00:01:40.479> with<00:01:40.630> a<00:01:40.810> big<00:01:41.409> one<00:01:42.330> which<00:01:43.330> is<00:01:45.210> no<00:01:46.210> pricing 00:01:47.160 --> 00:01:47.170 align:start position:0% start with a big one which is no pricing 00:01:47.170 --> 00:01:52.249 align:start position:0% start with a big one which is no pricing of<00:01:47.380> computational<00:01:48.100> and<00:01:48.520> arithmetic<00:01:48.789> octaves 00:01:52.249 --> 00:01:52.259 align:start position:0% 00:01:52.259 --> 00:01:54.899 align:start position:0% that<00:01:53.259> has<00:01:53.470> been<00:01:53.679> I<00:01:53.800> think<00:01:53.830> you<00:01:54.100> get<00:01:54.280> started<00:01:54.550> I 00:01:54.899 --> 00:01:54.909 align:start position:0% that has been I think you get started I 00:01:54.909 --> 00:01:56.430 align:start position:0% that has been I think you get started I will<00:01:55.090> today<00:01:55.330> the<00:01:55.509> discussion<00:01:55.750> will<00:01:56.140> give<00:01:56.289> him 00:01:56.430 --> 00:01:56.440 align:start position:0% will today the discussion will give him 00:01:56.440 --> 00:01:59.070 align:start position:0% will today the discussion will give him one<00:01:56.679> inoculations<00:01:57.610> not<00:01:58.390> sure<00:01:58.509> if<00:01:58.630> any<00:01:58.810> of<00:01:58.899> you 00:01:59.070 --> 00:01:59.080 align:start position:0% one inoculations not sure if any of you 00:01:59.080 --> 00:02:02.340 align:start position:0% one inoculations not sure if any of you guys<00:01:59.259> have<00:01:59.440> seen<00:01:59.500> that<00:01:59.740> talk<00:02:00.220> there<00:02:00.729> today<00:02:01.350> and 00:02:02.340 --> 00:02:02.350 align:start position:0% guys have seen that talk there today and 00:02:02.350 --> 00:02:06.749 align:start position:0% guys have seen that talk there today and but<00:02:03.340> there<00:02:03.490> was<00:02:03.640> also<00:02:04.000> a<00:02:04.240> paper<00:02:04.649> that<00:02:05.759> some 00:02:06.749 --> 00:02:06.759 align:start position:0% but there was also a paper that some 00:02:06.759 --> 00:02:09.809 align:start position:0% but there was also a paper that some instructions<00:02:07.270> may<00:02:07.420> be<00:02:07.479> mispriced<00:02:08.280> and<00:02:09.280> in 00:02:09.809 --> 00:02:09.819 align:start position:0% instructions may be mispriced and in 00:02:09.819 --> 00:02:12.630 align:start position:0% instructions may be mispriced and in Istanbul<00:02:10.600> heart<00:02:10.780> work<00:02:11.049> may<00:02:11.890> have<00:02:12.069> seen<00:02:12.310> the<00:02:12.489> IP 00:02:12.630 --> 00:02:12.640 align:start position:0% Istanbul heart work may have seen the IP 00:02:12.640 --> 00:02:15.539 align:start position:0% Istanbul heart work may have seen the IP one<00:02:13.090> eight<00:02:13.269> eight<00:02:13.480> four<00:02:14.070> which<00:02:15.070> also<00:02:15.280> suggests 00:02:15.539 --> 00:02:15.549 align:start position:0% one eight eight four which also suggests 00:02:15.549 --> 00:02:18.449 align:start position:0% one eight eight four which also suggests two<00:02:16.030> to<00:02:16.209> repress<00:02:16.570> a<00:02:16.600> couple<00:02:16.959> instructions<00:02:17.560> so 00:02:18.449 --> 00:02:18.459 align:start position:0% two to repress a couple instructions so 00:02:18.459 --> 00:02:19.550 align:start position:0% two to repress a couple instructions so what<00:02:18.790> do<00:02:18.850> you<00:02:18.910> guys<00:02:19.000> think<00:02:19.060> about 00:02:19.550 --> 00:02:19.560 align:start position:0% what do you guys think about 00:02:19.560 --> 00:02:22.650 align:start position:0% what do you guys think about instructional<00:02:20.560> pricing<00:02:21.180> is<00:02:22.180> everything 00:02:22.650 --> 00:02:22.660 align:start position:0% instructional pricing is everything 00:02:22.660 --> 00:02:29.250 align:start position:0% instructional pricing is everything correct<00:02:26.880> it's<00:02:27.880> it's<00:02:28.209> kind<00:02:28.420> of<00:02:28.450> impossible<00:02:28.720> for 00:02:29.250 --> 00:02:29.260 align:start position:0% correct it's it's kind of impossible for 00:02:29.260 --> 00:02:29.730 align:start position:0% correct it's it's kind of impossible for it 00:02:29.730 --> 00:02:29.740 align:start position:0% it 00:02:29.740 --> 00:02:31.140 align:start position:0% it right<00:02:29.920> across<00:02:30.190> all<00:02:30.430> the<00:02:30.490> machines<00:02:30.790> the<00:02:31.000> best 00:02:31.140 --> 00:02:31.150 align:start position:0% right across all the machines the best 00:02:31.150 --> 00:02:33.300 align:start position:0% right across all the machines the best we<00:02:31.270> can<00:02:31.330> do<00:02:31.510> is<00:02:31.630> try<00:02:31.810> entires<00:02:32.350> an<00:02:32.950> average 00:02:33.300 --> 00:02:33.310 align:start position:0% we can do is try entires an average 00:02:33.310 --> 00:02:35.100 align:start position:0% we can do is try entires an average machine<00:02:33.700> but<00:02:34.000> with<00:02:34.120> different<00:02:34.540> reasons<00:02:34.990> for 00:02:35.100 --> 00:02:35.110 align:start position:0% machine but with different reasons for 00:02:35.110 --> 00:02:36.630 align:start position:0% machine but with different reasons for transitive<00:02:35.560> difference<00:02:35.860> because<00:02:36.160> D<00:02:36.460> is 00:02:36.630 --> 00:02:36.640 align:start position:0% transitive difference because D is 00:02:36.640 --> 00:02:38.670 align:start position:0% transitive difference because D is different<00:02:36.820> parameter<00:02:37.450> teachers<00:02:37.900> and<00:02:38.080> so<00:02:38.200> on<00:02:38.350> I 00:02:38.670 --> 00:02:38.680 align:start position:0% different parameter teachers and so on I 00:02:38.680 --> 00:02:40.830 align:start position:0% different parameter teachers and so on I was<00:02:38.950> never<00:02:39.130> gonna<00:02:39.250> be<00:02:39.310> completely<00:02:39.730> correct<00:02:40.000> we 00:02:40.830 --> 00:02:40.840 align:start position:0% was never gonna be completely correct we 00:02:40.840 --> 00:02:41.740 align:start position:0% was never gonna be completely correct we just<00:02:41.050> have<00:02:41.140> to<00:02:41.230> try 00:02:41.740 --> 00:02:41.750 align:start position:0% just have to try 00:02:41.750 --> 00:02:43.780 align:start position:0% just have to try arrival<00:02:42.140> pricing<00:02:42.500> scheme<00:02:42.770> isn't<00:02:43.010> so<00:02:43.310> far<00:02:43.610> off 00:02:43.780 --> 00:02:43.790 align:start position:0% arrival pricing scheme isn't so far off 00:02:43.790 --> 00:02:45.760 align:start position:0% arrival pricing scheme isn't so far off base<00:02:44.030> that<00:02:44.360> it<00:02:44.480> converts<00:02:44.840> a<00:02:44.930> subject<00:02:45.290> dearest 00:02:45.760 --> 00:02:45.770 align:start position:0% base that it converts a subject dearest 00:02:45.770 --> 00:02:49.270 align:start position:0% base that it converts a subject dearest text<00:02:46.630> and<00:02:47.630> that's<00:02:48.080> why<00:02:48.440> we<00:02:48.680> had<00:02:48.830> to<00:02:48.860> do<00:02:49.070> things 00:02:49.270 --> 00:02:49.280 align:start position:0% text and that's why we had to do things 00:02:49.280 --> 00:02:50.680 align:start position:0% text and that's why we had to do things like<00:02:49.520> what<00:02:49.670> are<00:02:49.700> they<00:02:49.940> for 00:02:50.680 --> 00:02:50.690 align:start position:0% like what are they for 00:02:50.690 --> 00:02:52.480 align:start position:0% like what are they for in<00:02:51.020> order<00:02:51.290> to<00:02:51.320> or<00:02:51.470> whether<00:02:51.740> it's<00:02:52.070> like<00:02:52.280> the 00:02:52.480 --> 00:02:52.490 align:start position:0% in order to or whether it's like the 00:02:52.490 --> 00:02:55.450 align:start position:0% in order to or whether it's like the disruption<00:02:53.240> to<00:02:53.530> existing<00:02:54.530> stock<00:02:54.800> contracts<00:02:55.370> a 00:02:55.450 --> 00:02:55.460 align:start position:0% disruption to existing stock contracts a 00:02:55.460 --> 00:02:57.790 align:start position:0% disruption to existing stock contracts a problem<00:02:55.850> but<00:02:56.150> it's<00:02:56.810> not<00:02:56.900> avoidable<00:02:57.380> one<00:02:57.620> who 00:02:57.790 --> 00:02:57.800 align:start position:0% problem but it's not avoidable one who 00:02:57.800 --> 00:02:59.080 align:start position:0% problem but it's not avoidable one who is<00:02:57.860> the<00:02:57.980> alternative<00:02:58.430> is<00:02:58.580> that<00:02:58.610> we<00:02:58.910> just 00:02:59.080 --> 00:02:59.090 align:start position:0% is the alternative is that we just 00:02:59.090 --> 00:03:01.660 align:start position:0% is the alternative is that we just simply<00:02:59.240> what<00:02:59.810> we've<00:02:59.959> got<00:03:00.140> and<00:03:00.440> inside<00:03:00.860> we<00:03:01.010> have 00:03:01.660 --> 00:03:01.670 align:start position:0% simply what we've got and inside we have 00:03:01.670 --> 00:03:09.289 align:start position:0% simply what we've got and inside we have a<00:03:02.140> contract<00:03:03.140> that 00:03:09.289 --> 00:03:09.299 align:start position:0% 00:03:09.299 --> 00:03:14.670 align:start position:0% yes<00:03:10.299> just<00:03:11.140> to<00:03:11.230> add<00:03:11.349> to<00:03:11.379> it<00:03:11.739> I<00:03:11.920> think<00:03:13.170> just<00:03:14.170> as 00:03:14.670 --> 00:03:14.680 align:start position:0% yes just to add to it I think just as 00:03:14.680 --> 00:03:22.170 align:start position:0% yes just to add to it I think just as replacing<00:03:15.430> is<00:03:15.549> tough<00:03:18.810> I<00:03:20.340> think<00:03:21.340> it's<00:03:22.000> also 00:03:22.170 --> 00:03:22.180 align:start position:0% replacing is tough I think it's also 00:03:22.180 --> 00:03:29.509 align:start position:0% replacing is tough I think it's also kind<00:03:22.480> of<00:03:22.569> we<00:03:22.870> want<00:03:23.170> to<00:03:23.230> go<00:03:23.379> in<00:03:23.560> the<00:03:23.650> future<00:03:23.799> but 00:03:29.509 --> 00:03:29.519 align:start position:0% 00:03:29.519 --> 00:03:33.089 align:start position:0% also<00:03:30.519> in<00:03:31.000> a<00:03:31.060> high<00:03:31.180> life<00:03:31.390> it<00:03:31.569> is<00:03:31.689> we<00:03:32.560> often<00:03:32.709> say 00:03:33.089 --> 00:03:33.099 align:start position:0% also in a high life it is we often say 00:03:33.099 --> 00:03:38.490 align:start position:0% also in a high life it is we often say what<00:03:33.639> we<00:03:35.159> call<00:03:36.209> simple<00:03:37.209> make<00:03:37.480> love<00:03:37.719> change<00:03:38.019> so 00:03:38.490 --> 00:03:38.500 align:start position:0% what we call simple make love change so 00:03:38.500 --> 00:03:42.379 align:start position:0% what we call simple make love change so we<00:03:38.889> should<00:03:39.099> keep<00:03:39.400> that<00:03:39.579> in<00:03:39.639> mind<00:03:39.909> it's<00:03:40.840> not 00:03:42.379 --> 00:03:42.389 align:start position:0% we should keep that in mind it's not 00:03:42.389 --> 00:03:52.429 align:start position:0% we should keep that in mind it's not that's<00:03:43.389> why<00:03:43.540> we<00:03:43.659> will<00:03:43.810> have<00:03:46.650> we<00:03:47.650> want<00:03:47.829> to<00:03:47.919> do 00:03:52.429 --> 00:03:52.439 align:start position:0% 00:03:52.439 --> 00:03:56.759 align:start position:0% something<00:03:54.900> most<00:03:55.900> of<00:03:56.079> the<00:03:56.200> crisis<00:03:56.739> that 00:03:56.759 --> 00:03:56.769 align:start position:0% something most of the crisis that 00:03:56.769 --> 00:04:00.089 align:start position:0% something most of the crisis that happened<00:03:57.269> the<00:03:58.269> papers<00:03:58.689> are<00:03:58.870> welcome<00:03:59.379> this<00:04:00.040> is 00:04:00.089 --> 00:04:00.099 align:start position:0% happened the papers are welcome this is 00:04:00.099 --> 00:04:02.759 align:start position:0% happened the papers are welcome this is actually<00:04:00.639> about<00:04:00.900> accessing<00:04:01.900> exterminator 00:04:02.759 --> 00:04:02.769 align:start position:0% actually about accessing exterminator 00:04:02.769 --> 00:04:06.300 align:start position:0% actually about accessing exterminator PDF<00:04:03.400> and<00:04:04.030> like<00:04:04.840> this<00:04:05.169> is<00:04:05.319> actually<00:04:05.500> externally 00:04:06.300 --> 00:04:06.310 align:start position:0% PDF and like this is actually externally 00:04:06.310 --> 00:04:08.940 align:start position:0% PDF and like this is actually externally in<00:04:06.489> the<00:04:06.579> door<00:04:06.849> it's<00:04:07.419> just<00:04:07.510> a<00:04:07.959> way<00:04:08.109> to<00:04:08.169> do<00:04:08.919> it 00:04:08.940 --> 00:04:08.950 align:start position:0% in the door it's just a way to do it 00:04:08.950 --> 00:04:11.039 align:start position:0% in the door it's just a way to do it something<00:04:09.310> from<00:04:09.579> from<00:04:09.939> the<00:04:10.090> outside<00:04:10.510> let's 00:04:11.039 --> 00:04:11.049 align:start position:0% something from from the outside let's 00:04:11.049 --> 00:04:13.939 align:start position:0% something from from the outside let's say<00:04:11.199> this<00:04:11.409> for<00:04:11.739> something<00:04:12.099> like<00:04:12.340> memory<00:04:12.790> and 00:04:13.939 --> 00:04:13.949 align:start position:0% say this for something like memory and 00:04:13.949 --> 00:04:16.620 align:start position:0% say this for something like memory and and<00:04:14.949> I<00:04:15.400> think<00:04:15.609> this<00:04:15.849> is<00:04:16.000> what<00:04:16.150> we<00:04:16.299> mostly 00:04:16.620 --> 00:04:16.630 align:start position:0% and I think this is what we mostly 00:04:16.630 --> 00:04:19.680 align:start position:0% and I think this is what we mostly struggle<00:04:17.079> with<00:04:17.699> the<00:04:18.699> on<00:04:18.880> the<00:04:19.000> other<00:04:19.150> hand<00:04:19.479> the 00:04:19.680 --> 00:04:19.690 align:start position:0% struggle with the on the other hand the 00:04:19.690 --> 00:04:23.180 align:start position:0% struggle with the on the other hand the computation<00:04:20.349> of<00:04:20.440> the<00:04:20.560> kind<00:04:21.159> of<00:04:21.280> higher<00:04:21.789> price 00:04:23.180 --> 00:04:23.190 align:start position:0% computation of the kind of higher price 00:04:23.190 --> 00:04:26.730 align:start position:0% computation of the kind of higher price comparing<00:04:24.190> to<00:04:24.400> DHT<00:04:24.909> time<00:04:25.150> in<00:04:25.360> texting 00:04:26.730 --> 00:04:26.740 align:start position:0% comparing to DHT time in texting 00:04:26.740 --> 00:04:30.029 align:start position:0% comparing to DHT time in texting so<00:04:27.249> it's<00:04:27.400> up<00:04:27.520> like<00:04:27.550> big<00:04:27.969> safe<00:04:28.270> margin<00:04:28.599> here<00:04:29.039> and 00:04:30.029 --> 00:04:30.039 align:start position:0% so it's up like big safe margin here and 00:04:30.039 --> 00:04:32.369 align:start position:0% so it's up like big safe margin here and I<00:04:30.129> actually<00:04:30.280> have<00:04:31.150> a<00:04:31.180> claim<00:04:31.629> us<00:04:31.840> even<00:04:32.229> if<00:04:32.349> we 00:04:32.369 --> 00:04:32.379 align:start position:0% I actually have a claim us even if we 00:04:32.379 --> 00:04:34.679 align:start position:0% I actually have a claim us even if we prize<00:04:32.860> the<00:04:33.129> computation<00:04:33.969> of<00:04:34.090> course<00:04:34.389> by<00:04:34.629> the 00:04:34.679 --> 00:04:34.689 align:start position:0% prize the computation of course by the 00:04:34.689 --> 00:04:37.110 align:start position:0% prize the computation of course by the same<00:04:35.050> amount<00:04:35.379> of<00:04:35.680> them<00:04:36.039> it<00:04:36.520> wouldn't<00:04:36.909> matter 00:04:37.110 --> 00:04:37.120 align:start position:0% same amount of them it wouldn't matter 00:04:37.120 --> 00:04:39.809 align:start position:0% same amount of them it wouldn't matter because<00:04:37.509> it<00:04:38.259> still<00:04:38.650> so<00:04:38.860> by<00:04:39.099> comparing<00:04:39.699> it<00:04:39.789> to 00:04:39.809 --> 00:04:39.819 align:start position:0% because it still so by comparing it to 00:04:39.819 --> 00:04:40.769 align:start position:0% because it still so by comparing it to the<00:04:39.999> other<00:04:40.029> car 00:04:40.769 --> 00:04:40.779 align:start position:0% the other car 00:04:40.779 --> 00:04:51.689 align:start position:0% the other car that's<00:04:41.409> like<00:04:42.129> it's<00:04:42.249> not<00:04:42.490> exploitable<00:04:50.699> I 00:04:51.689 --> 00:04:51.699 align:start position:0% that's like it's not exploitable I 00:04:51.699 --> 00:04:55.379 align:start position:0% that's like it's not exploitable I kind<00:04:52.689> of<00:04:52.779> algorithm<00:04:53.499> instead<00:04:54.069> of<00:04:54.389> something 00:04:55.379 --> 00:04:55.389 align:start position:0% kind of algorithm instead of something 00:04:55.389 --> 00:05:01.339 align:start position:0% kind of algorithm instead of something something<00:04:56.110> more<00:04:56.939> so<00:04:57.939> the<00:04:58.090> worst<00:04:58.389> case<00:04:59.050> I<00:04:59.289> think 00:05:01.339 --> 00:05:01.349 align:start position:0% something more so the worst case I think 00:05:01.349 --> 00:05:04.709 align:start position:0% something more so the worst case I think what<00:05:02.349> I<00:05:02.529> think<00:05:02.560> of<00:05:02.919> code<00:05:03.159> that's<00:05:03.719> duplication 00:05:04.709 --> 00:05:04.719 align:start position:0% what I think of code that's duplication 00:05:04.719 --> 00:05:06.809 align:start position:0% what I think of code that's duplication and<00:05:04.840> division<00:05:05.349> but<00:05:06.099> still<00:05:06.430> I<00:05:06.460> think<00:05:06.639> the 00:05:06.809 --> 00:05:06.819 align:start position:0% and division but still I think the 00:05:06.819 --> 00:05:09.300 align:start position:0% and division but still I think the margin<00:05:07.210> is<00:05:07.330> big<00:05:07.599> enough<00:05:07.870> and<00:05:08.169> we<00:05:08.710> are<00:05:08.860> bounded 00:05:09.300 --> 00:05:09.310 align:start position:0% margin is big enough and we are bounded 00:05:09.310 --> 00:05:17.700 align:start position:0% margin is big enough and we are bounded by<00:05:14.400> but<00:05:15.400> I<00:05:15.639> think<00:05:15.939> they<00:05:16.090> could<00:05:16.300> be<00:05:16.469> smaller<00:05:17.469> if 00:05:17.700 --> 00:05:17.710 align:start position:0% by but I think they could be smaller if 00:05:17.710 --> 00:05:21.119 align:start position:0% by but I think they could be smaller if that<00:05:17.889> helps<00:05:18.569> for<00:05:19.569> exactly<00:05:20.020> to<00:05:20.139> be<00:05:20.169> to<00:05:20.710> go<00:05:20.889> more 00:05:21.119 --> 00:05:21.129 align:start position:0% that helps for exactly to be to go more 00:05:21.129 --> 00:05:25.379 align:start position:0% that helps for exactly to be to go more into<00:05:21.430> state<00:05:22.300> that<00:05:23.219> stateless<00:05:24.219> contract<00:05:24.759> so 00:05:25.379 --> 00:05:25.389 align:start position:0% into state that stateless contract so 00:05:25.389 --> 00:05:29.480 align:start position:0% into state that stateless contract so you<00:05:25.449> can<00:05:25.749> compute<00:05:26.319> more<00:05:26.589> instead<00:05:26.919> of<00:05:27.069> staying 00:05:29.480 --> 00:05:29.490 align:start position:0% 00:05:29.490 --> 00:05:33.540 align:start position:0% there<00:05:30.490> the<00:05:31.949> computational<00:05:32.949> ones<00:05:33.129> are<00:05:33.279> are 00:05:33.540 --> 00:05:33.550 align:start position:0% there the computational ones are are 00:05:33.550 --> 00:05:41.670 align:start position:0% there the computational ones are are highly<00:05:33.939> WordPress<00:05:34.389> today<00:05:40.169> but<00:05:41.169> now<00:05:41.319> you<00:05:41.379> say 00:05:41.670 --> 00:05:41.680 align:start position:0% highly WordPress today but now you say 00:05:41.680 --> 00:05:47.070 align:start position:0% highly WordPress today but now you say that<00:05:43.229> to<00:05:44.229> your<00:05:44.770> commutation<00:05:45.539> yeah<00:05:46.539> I 00:05:47.070 --> 00:05:47.080 align:start position:0% that to your commutation yeah I 00:05:47.080 --> 00:05:50.240 align:start position:0% that to your commutation yeah I personally<00:05:47.860> would<00:05:48.009> be<00:05:48.159> likely<00:05:48.819> to<00:05:49.029> lower<00:05:49.330> them 00:05:50.240 --> 00:05:50.250 align:start position:0% personally would be likely to lower them 00:05:50.250 --> 00:05:53.790 align:start position:0% personally would be likely to lower them but<00:05:51.250> well<00:05:52.060> we<00:05:52.509> cannot<00:05:52.779> try<00:05:53.080> them<00:05:53.349> accurately 00:05:53.790 --> 00:05:53.800 align:start position:0% but well we cannot try them accurately 00:05:53.800 --> 00:05:56.899 align:start position:0% but well we cannot try them accurately like<00:05:54.639> each<00:05:55.060> other<00:05:55.300> but<00:05:55.599> they're<00:05:56.110> not<00:05:56.289> like<00:05:56.529> oh 00:05:56.899 --> 00:05:56.909 align:start position:0% like each other but they're not like oh 00:05:56.909 --> 00:06:01.230 align:start position:0% like each other but they're not like oh this<00:05:57.909> other<00:05:58.659> things<00:05:58.990> they<00:05:59.319> not<00:05:59.789> in<00:06:00.789> terms<00:06:01.029> of 00:06:01.230 --> 00:06:01.240 align:start position:0% this other things they not in terms of 00:06:01.240 --> 00:06:04.230 align:start position:0% this other things they not in terms of time<00:06:01.629> they<00:06:02.379> eat<00:06:02.529> they<00:06:02.710> take<00:06:02.979> to<00:06:03.250> execute<00:06:03.520> and 00:06:04.230 --> 00:06:04.240 align:start position:0% time they eat they take to execute and 00:06:04.240 --> 00:06:06.990 align:start position:0% time they eat they take to execute and the<00:06:04.360> crisis<00:06:04.899> that's<00:06:05.680> not<00:06:05.889> also<00:06:06.279> a<00:06:06.460> queue<00:06:06.729> at 00:06:06.990 --> 00:06:07.000 align:start position:0% the crisis that's not also a queue at 00:06:07.000 --> 00:06:08.610 align:start position:0% the crisis that's not also a queue at the<00:06:07.120> moment<00:06:07.479> but<00:06:07.689> somehow<00:06:08.259> it's<00:06:08.589> not 00:06:08.610 --> 00:06:08.620 align:start position:0% the moment but somehow it's not 00:06:08.620 --> 00:06:11.550 align:start position:0% the moment but somehow it's not exploitable<00:06:09.629> from<00:06:10.629> the<00:06:10.779> security<00:06:11.259> point<00:06:11.439> of 00:06:11.550 --> 00:06:11.560 align:start position:0% exploitable from the security point of 00:06:11.560 --> 00:06:15.320 align:start position:0% exploitable from the security point of view<00:06:12.180> but<00:06:13.180> yeah<00:06:13.599> if<00:06:13.960> you<00:06:14.259> want<00:06:14.469> more<00:06:14.770> fair 00:06:15.320 --> 00:06:15.330 align:start position:0% view but yeah if you want more fair 00:06:15.330 --> 00:06:17.309 align:start position:0% view but yeah if you want more fair prices<00:06:16.330> I<00:06:16.419> think<00:06:16.659> they<00:06:16.960> should<00:06:17.169> be 00:06:17.309 --> 00:06:17.319 align:start position:0% prices I think they should be 00:06:17.319 --> 00:06:20.579 align:start position:0% prices I think they should be indefinitely<00:06:17.919> lowered<00:06:18.339> by<00:06:18.639> by<00:06:19.509> some<00:06:19.569> time<00:06:19.960> but 00:06:20.579 --> 00:06:20.589 align:start position:0% indefinitely lowered by by some time but 00:06:20.589 --> 00:06:22.769 align:start position:0% indefinitely lowered by by some time but bye<00:06:20.919> bye<00:06:21.430> geek<00:06:21.669> geek<00:06:22.060> Mountain 00:06:22.769 --> 00:06:22.779 align:start position:0% bye bye geek geek Mountain 00:06:22.779 --> 00:06:27.590 align:start position:0% bye bye geek geek Mountain I<00:06:22.810> mean<00:06:23.139> indecisive 00:06:27.590 --> 00:06:27.600 align:start position:0% 00:06:27.600 --> 00:06:31.379 align:start position:0% so<00:06:28.600> stank<00:06:28.900> blood<00:06:29.110> concerns<00:06:29.560> really<00:06:30.520> mostly 00:06:31.379 --> 00:06:31.389 align:start position:0% so stank blood concerns really mostly 00:06:31.389 --> 00:06:35.310 align:start position:0% so stank blood concerns really mostly like<00:06:31.630> unfortunately<00:06:32.110> the<00:06:33.009> store<00:06:34.139> so<00:06:35.139> I<00:06:35.199> think 00:06:35.310 --> 00:06:35.320 align:start position:0% like unfortunately the store so I think 00:06:35.320 --> 00:06:39.210 align:start position:0% like unfortunately the store so I think that<00:06:36.160> as<00:06:36.280> well<00:06:37.830> we're<00:06:38.830> talking<00:06:39.070> about 00:06:39.210 --> 00:06:39.220 align:start position:0% that as well we're talking about 00:06:39.220 --> 00:06:40.770 align:start position:0% that as well we're talking about reducing<00:06:39.340> the<00:06:39.699> cost<00:06:39.940> of<00:06:40.180> just<00:06:40.600> the 00:06:40.770 --> 00:06:40.780 align:start position:0% reducing the cost of just the 00:06:40.780 --> 00:06:43.529 align:start position:0% reducing the cost of just the computational<00:06:41.440> ones<00:06:41.650> right<00:06:41.860> now<00:06:42.419> that<00:06:43.419> are 00:06:43.529 --> 00:06:43.539 align:start position:0% computational ones right now that are 00:06:43.539 --> 00:06:55.860 align:start position:0% computational ones right now that are using<00:06:43.660> custom<00:06:53.880> topics<00:06:54.880> wouldn't<00:06:55.300> to<00:06:55.389> say<00:06:55.600> that 00:06:55.860 --> 00:06:55.870 align:start position:0% using custom topics wouldn't to say that 00:06:55.870 --> 00:06:57.960 align:start position:0% using custom topics wouldn't to say that if<00:06:56.740> you're<00:06:56.949> moving<00:06:57.070> towards<00:06:57.610> stateless 00:06:57.960 --> 00:06:57.970 align:start position:0% if you're moving towards stateless 00:06:57.970 --> 00:06:59.550 align:start position:0% if you're moving towards stateless contracts<00:06:58.449> that<00:06:58.630> you<00:06:58.690> would<00:06:58.840> actually<00:06:59.169> have 00:06:59.550 --> 00:06:59.560 align:start position:0% contracts that you would actually have 00:06:59.560 --> 00:07:02.250 align:start position:0% contracts that you would actually have to<00:07:00.330> decrease<00:07:01.330> the<00:07:01.479> price<00:07:01.660> up<00:07:01.870> to<00:07:02.020> come<00:07:02.139> to 00:07:02.250 --> 00:07:02.260 align:start position:0% to decrease the price up to come to 00:07:02.260 --> 00:07:05.159 align:start position:0% to decrease the price up to come to there's<00:07:02.380> always<00:07:02.520> to<00:07:03.520> make<00:07:03.639> reasonable<00:07:04.000> yeah 00:07:05.159 --> 00:07:05.169 align:start position:0% there's always to make reasonable yeah 00:07:05.169 --> 00:07:06.600 align:start position:0% there's always to make reasonable yeah otherwise<00:07:05.440> your<00:07:05.830> user<00:07:05.979> Richman's<00:07:06.400> have<00:07:06.520> been 00:07:06.600 --> 00:07:06.610 align:start position:0% otherwise your user Richman's have been 00:07:06.610 --> 00:07:09.290 align:start position:0% otherwise your user Richman's have been late<00:07:06.940> to<00:07:07.120> spend<00:07:07.680> yeah<00:07:08.680> actually<00:07:08.770> they 00:07:09.290 --> 00:07:09.300 align:start position:0% late to spend yeah actually they 00:07:09.300 --> 00:07:23.850 align:start position:0% late to spend yeah actually they expensive<00:07:19.440> very<00:07:20.440> different<00:07:22.410> lower<00:07:23.410> the<00:07:23.650> cost 00:07:23.850 --> 00:07:23.860 align:start position:0% expensive very different lower the cost 00:07:23.860 --> 00:07:33.310 align:start position:0% expensive very different lower the cost be<00:07:24.070> mindful 00:07:33.310 --> 00:07:33.320 align:start position:0% 00:07:33.320 --> 00:07:37.670 align:start position:0% yeah<00:07:35.420> yeah<00:07:36.420> the<00:07:36.630> maintenance<00:07:37.020> trane<00:07:37.230> this<00:07:37.410> is 00:07:37.670 --> 00:07:37.680 align:start position:0% yeah yeah the maintenance trane this is 00:07:37.680 --> 00:07:40.910 align:start position:0% yeah yeah the maintenance trane this is the<00:07:38.010> crisp<00:07:38.250> call<00:07:38.520> data<00:07:38.760> so<00:07:39.470> lovely<00:07:40.470> and<00:07:40.800> it's 00:07:40.910 --> 00:07:40.920 align:start position:0% the crisp call data so lovely and it's 00:07:40.920 --> 00:07:44.420 align:start position:0% the crisp call data so lovely and it's great<00:07:41.100> progress<00:07:41.310> that<00:07:42.440> the<00:07:43.440> VIP<00:07:43.920> were 00:07:44.420 --> 00:07:44.430 align:start position:0% great progress that the VIP were 00:07:44.430 --> 00:07:46.220 align:start position:0% great progress that the VIP were reducing<00:07:44.970> the<00:07:45.030> cost<00:07:45.240> of<00:07:45.330> call<00:07:45.510> data<00:07:45.750> is<00:07:45.930> going 00:07:46.220 --> 00:07:46.230 align:start position:0% reducing the cost of call data is going 00:07:46.230 --> 00:07:49.610 align:start position:0% reducing the cost of call data is going into<00:07:46.760> Istanbul<00:07:47.760> if<00:07:47.940> it<00:07:48.030> wasn't<00:07:48.270> for<00:07:48.360> that<00:07:48.620> I'll 00:07:49.610 --> 00:07:49.620 align:start position:0% into Istanbul if it wasn't for that I'll 00:07:49.620 --> 00:07:52.940 align:start position:0% into Istanbul if it wasn't for that I'll be<00:07:49.770> pretty<00:07:49.950> pessimistic<00:07:50.790> but<00:07:51.680> that<00:07:52.680> was<00:07:52.770> great 00:07:52.940 --> 00:07:52.950 align:start position:0% be pretty pessimistic but that was great 00:07:52.950 --> 00:07:55.580 align:start position:0% be pretty pessimistic but that was great progress<00:07:53.160> and<00:07:53.400> it's<00:07:53.940> like<00:07:54.120> about<00:07:54.720> halfway<00:07:55.050> to 00:07:55.580 --> 00:07:55.590 align:start position:0% progress and it's like about halfway to 00:07:55.590 --> 00:07:59.630 align:start position:0% progress and it's like about halfway to where<00:07:55.830> we<00:07:55.950> want<00:07:56.130> to<00:07:56.190> go<00:07:56.310> so<00:07:57.270> if<00:07:57.840> we<00:07:58.160> do<00:07:59.160> that 00:07:59.630 --> 00:07:59.640 align:start position:0% where we want to go so if we do that 00:07:59.640 --> 00:08:03.230 align:start position:0% where we want to go so if we do that again<00:08:00.030> the<00:08:00.270> next<00:08:00.450> work<00:08:00.720> once<00:08:01.080> the<00:08:02.240> price 00:08:03.230 --> 00:08:03.240 align:start position:0% again the next work once the price 00:08:03.240 --> 00:08:06.620 align:start position:0% again the next work once the price proposed<00:08:03.870> for<00:08:04.740> Istanbul<00:08:05.130> as<00:08:05.460> you<00:08:06.060> know<00:08:06.210> the 00:08:06.620 --> 00:08:06.630 align:start position:0% proposed for Istanbul as you know the 00:08:06.630 --> 00:08:09.620 align:start position:0% proposed for Istanbul as you know the network<00:08:06.780> is<00:08:07.050> still<00:08:07.170> stable<00:08:08.120> if<00:08:09.120> that's<00:08:09.510> the 00:08:09.620 --> 00:08:09.630 align:start position:0% network is still stable if that's the 00:08:09.630 --> 00:08:11.600 align:start position:0% network is still stable if that's the case<00:08:09.780> we<00:08:10.560> can<00:08:10.680> make<00:08:10.710> progress<00:08:10.980> and<00:08:11.190> reduce<00:08:11.460> it 00:08:11.600 --> 00:08:11.610 align:start position:0% case we can make progress and reduce it 00:08:11.610 --> 00:08:16.220 align:start position:0% case we can make progress and reduce it further<00:08:12.830> that<00:08:13.830> will<00:08:14.070> be<00:08:14.810> will<00:08:15.810> be<00:08:15.900> well<00:08:16.080> on<00:08:16.110> the 00:08:16.220 --> 00:08:16.230 align:start position:0% further that will be will be well on the 00:08:16.230 --> 00:08:19.820 align:start position:0% further that will be will be well on the way<00:08:16.320> and<00:08:16.710> but<00:08:17.400> I<00:08:17.460> think<00:08:17.490> the<00:08:17.880> other<00:08:18.830> difficult 00:08:19.820 --> 00:08:19.830 align:start position:0% way and but I think the other difficult 00:08:19.830 --> 00:08:27.250 align:start position:0% way and but I think the other difficult part<00:08:20.040> is<00:08:20.190> going<00:08:20.370> to<00:08:20.460> be<00:08:20.580> versioning<00:08:21.440> and 00:08:27.250 --> 00:08:27.260 align:start position:0% 00:08:27.260 --> 00:08:29.830 align:start position:0% versioning<00:08:28.260> will<00:08:28.440> be<00:08:28.530> necessary<00:08:28.710> to<00:08:29.040> prevent 00:08:29.830 --> 00:08:29.840 align:start position:0% versioning will be necessary to prevent 00:08:29.840 --> 00:08:35.960 align:start position:0% versioning will be necessary to prevent breaking<00:08:30.840> existing<00:08:31.590> contracts<00:08:32.060> so<00:08:33.890> but<00:08:34.890> if<00:08:35.729> we 00:08:35.960 --> 00:08:35.970 align:start position:0% breaking existing contracts so but if we 00:08:35.970 --> 00:08:38.600 align:start position:0% breaking existing contracts so but if we have<00:08:36.090> versioning<00:08:36.510> then<00:08:37.320> we<00:08:37.830> can<00:08:38.040> propose<00:08:38.340> new 00:08:38.600 --> 00:08:38.610 align:start position:0% have versioning then we can propose new 00:08:38.610 --> 00:08:40.580 align:start position:0% have versioning then we can propose new costs<00:08:39.120> and<00:08:39.300> it<00:08:39.450> will<00:08:39.630> incentive<00:08:40.260> these<00:08:40.410> new 00:08:40.580 --> 00:08:40.590 align:start position:0% costs and it will incentive these new 00:08:40.590 --> 00:08:42.590 align:start position:0% costs and it will incentive these new costs<00:08:41.040> plugs<00:08:41.370> will<00:08:41.520> be<00:08:41.610> cheaper<00:08:42.000> than<00:08:42.210> the<00:08:42.420> old 00:08:42.590 --> 00:08:42.600 align:start position:0% costs plugs will be cheaper than the old 00:08:42.600 --> 00:08:48.480 align:start position:0% costs plugs will be cheaper than the old costs<00:08:44.630> and 00:08:48.480 --> 00:08:48.490 align:start position:0% 00:08:48.490 --> 00:08:52.020 align:start position:0% the<00:08:49.090> and<00:08:49.860> existing<00:08:50.860> contracts<00:08:51.340> that<00:08:51.820> are 00:08:52.020 --> 00:08:52.030 align:start position:0% the and existing contracts that are 00:08:52.030 --> 00:08:53.850 align:start position:0% the and existing contracts that are blowing<00:08:52.570> the<00:08:52.750> state<00:08:52.990> will<00:08:53.260> eventually<00:08:53.680> be 00:08:53.850 --> 00:08:53.860 align:start position:0% blowing the state will eventually be 00:08:53.860 --> 00:08:55.740 align:start position:0% blowing the state will eventually be based<00:08:54.790> out<00:08:55.000> because<00:08:55.300> people<00:08:55.570> will<00:08:55.690> be 00:08:55.740 --> 00:08:55.750 align:start position:0% based out because people will be 00:08:55.750 --> 00:08:57.510 align:start position:0% based out because people will be incentivized<00:08:56.320> to<00:08:56.440> vote<00:08:56.650> today<00:08:56.860> cheaper<00:08:57.340> of 00:08:57.510 --> 00:08:57.520 align:start position:0% incentivized to vote today cheaper of 00:08:57.520 --> 00:08:58.940 align:start position:0% incentivized to vote today cheaper of stateless<00:08:57.910> pocket<00:08:58.210> house 00:08:58.940 --> 00:08:58.950 align:start position:0% stateless pocket house 00:08:58.950 --> 00:09:02.240 align:start position:0% stateless pocket house yeah<00:08:59.950> I<00:08:59.980> think<00:09:00.160> I<00:09:00.430> think<00:09:00.660> it's<00:09:01.660> a<00:09:01.750> great<00:09:01.840> idea 00:09:02.240 --> 00:09:02.250 align:start position:0% yeah I think I think it's a great idea 00:09:02.250 --> 00:09:04.350 align:start position:0% yeah I think I think it's a great idea also<00:09:03.250> because<00:09:03.520> it<00:09:03.670> kind<00:09:03.850> of<00:09:03.910> solves<00:09:04.150> that 00:09:04.350 --> 00:09:04.360 align:start position:0% also because it kind of solves that 00:09:04.360 --> 00:09:05.040 align:start position:0% also because it kind of solves that problem 00:09:05.040 --> 00:09:05.050 align:start position:0% problem 00:09:05.050 --> 00:09:08.040 align:start position:0% problem oh<00:09:05.080> I<00:09:05.620> have<00:09:06.070> this<00:09:06.250> contract<00:09:06.760> like<00:09:07.690> it's<00:09:07.840> my 00:09:08.040 --> 00:09:08.050 align:start position:0% oh I have this contract like it's my 00:09:08.050 --> 00:09:19.980 align:start position:0% oh I have this contract like it's my grave<00:09:08.320> do<00:09:09.190> this<00:09:09.450> I'm<00:09:17.880> a<00:09:18.880> good<00:09:19.060> stuff<00:09:19.300> so<00:09:19.780> is<00:09:19.900> it 00:09:19.980 --> 00:09:19.990 align:start position:0% grave do this I'm a good stuff so is it 00:09:19.990 --> 00:09:21.570 align:start position:0% grave do this I'm a good stuff so is it a<00:09:20.050> good<00:09:20.140> idea<00:09:20.260> various<00:09:20.680> countries<00:09:21.190> that's<00:09:21.370> the 00:09:21.570 --> 00:09:21.580 align:start position:0% a good idea various countries that's the 00:09:21.580 --> 00:09:25.350 align:start position:0% a good idea various countries that's the regime<00:09:22.510> you<00:09:22.600> wouldn't<00:09:22.900> also<00:09:23.560> sold<00:09:24.360> diseases 00:09:25.350 --> 00:09:25.360 align:start position:0% regime you wouldn't also sold diseases 00:09:25.360 --> 00:09:29.550 align:start position:0% regime you wouldn't also sold diseases free<00:09:25.630> with<00:09:26.440> the<00:09:27.000> sponsor<00:09:28.000> news<00:09:28.470> it's<00:09:29.470> an 00:09:29.550 --> 00:09:29.560 align:start position:0% free with the sponsor news it's an 00:09:29.560 --> 00:09:35.070 align:start position:0% free with the sponsor news it's an evening<00:09:29.740> for<00:09:30.010> me<00:09:32.280> are<00:09:33.280> you<00:09:33.430> guys<00:09:34.080> developers 00:09:35.070 --> 00:09:35.080 align:start position:0% evening for me are you guys developers 00:09:35.080 --> 00:09:40.020 align:start position:0% evening for me are you guys developers or<00:09:35.520> are<00:09:36.520> joining<00:09:36.760> deaf<00:09:37.000> developers<00:09:38.910> and<00:09:39.910> are 00:09:40.020 --> 00:09:40.030 align:start position:0% or are joining deaf developers and are 00:09:40.030 --> 00:09:43.860 align:start position:0% or are joining deaf developers and are you<00:09:40.120> guys<00:09:40.270> writing<00:09:40.480> contracts<00:09:42.570> are<00:09:43.570> you<00:09:43.690> happy 00:09:43.860 --> 00:09:43.870 align:start position:0% you guys writing contracts are you happy 00:09:43.870 --> 00:09:48.150 align:start position:0% you guys writing contracts are you happy with<00:09:44.020> the<00:09:44.140> prices<00:09:46.680> what<00:09:47.680> are<00:09:47.770> you<00:09:47.890> not<00:09:48.010> happy 00:09:48.150 --> 00:09:48.160 align:start position:0% with the prices what are you not happy 00:09:48.160 --> 00:09:53.760 align:start position:0% with the prices what are you not happy with<00:09:50.910> the<00:09:51.910> gas<00:09:52.120> price<00:09:52.510> as<00:09:52.840> a<00:09:52.900> misdemeanor<00:09:53.470> of 00:09:53.760 --> 00:09:53.770 align:start position:0% with the gas price as a misdemeanor of 00:09:53.770 --> 00:09:55.260 align:start position:0% with the gas price as a misdemeanor of actions<00:09:54.160> and<00:09:54.250> you<00:09:54.340> cry<00:09:54.520> too<00:09:54.580> much<00:09:54.730> for<00:09:55.000> them<00:09:55.090> or 00:09:55.260 --> 00:09:55.270 align:start position:0% actions and you cry too much for them or 00:09:55.270 --> 00:10:00.830 align:start position:0% actions and you cry too much for them or the<00:09:55.510> specific<00:09:56.200> if<00:09:57.160> you<00:09:57.340> have<00:09:57.490> to<00:09:57.670> like<00:09:57.850> wait 00:10:00.830 --> 00:10:00.840 align:start position:0% 00:10:00.840 --> 00:10:04.830 align:start position:0% yes<00:10:01.840> are<00:10:02.650> you<00:10:03.070> storing<00:10:03.670> enough<00:10:03.910> data<00:10:04.270> is<00:10:04.540> is 00:10:04.830 --> 00:10:04.840 align:start position:0% yes are you storing enough data is is 00:10:04.840 --> 00:10:07.170 align:start position:0% yes are you storing enough data is is that<00:10:05.080> the<00:10:05.230> main<00:10:05.350> challenge<00:10:05.620> but<00:10:06.580> just<00:10:06.880> try<00:10:07.150> to 00:10:07.170 --> 00:10:07.180 align:start position:0% that the main challenge but just try to 00:10:07.180 --> 00:10:12.090 align:start position:0% that the main challenge but just try to execute 00:10:12.090 --> 00:10:12.100 align:start position:0% 00:10:12.100 --> 00:10:15.389 align:start position:0% yes<00:10:13.089> I've<00:10:13.329> recently<00:10:13.810> deployed<00:10:14.319> contractor<00:10:15.220> to 00:10:15.389 --> 00:10:15.399 align:start position:0% yes I've recently deployed contractor to 00:10:15.399 --> 00:10:24.600 align:start position:0% yes I've recently deployed contractor to Nicole's<00:10:16.360> a<00:10:16.600> signature<00:10:22.920> for<00:10:23.920> deployment<00:10:24.220> wing 00:10:24.600 --> 00:10:24.610 align:start position:0% Nicole's a signature for deployment wing 00:10:24.610 --> 00:10:31.530 align:start position:0% Nicole's a signature for deployment wing yeah<00:10:27.720> people<00:10:28.720> so<00:10:28.990> the<00:10:29.199> gas<00:10:29.470> prices<00:10:29.889> on<00:10:30.190> 31 00:10:31.530 --> 00:10:31.540 align:start position:0% yeah people so the gas prices on 31 00:10:31.540 --> 00:10:35.970 align:start position:0% yeah people so the gas prices on 31 like<00:10:31.780> who<00:10:32.500> creates<00:10:32.980> bison 00:10:35.970 --> 00:10:35.980 align:start position:0% 00:10:35.980 --> 00:10:39.280 align:start position:0% beforehand<00:10:36.980> for<00:10:37.250> the<00:10:37.490> lifetime<00:10:38.080> right<00:10:39.080> it's 00:10:39.280 --> 00:10:39.290 align:start position:0% beforehand for the lifetime right it's 00:10:39.290 --> 00:10:53.549 align:start position:0% beforehand for the lifetime right it's not<00:10:39.440> that<00:10:39.500> because<00:10:39.950> the<00:10:40.250> cheap 00:10:53.549 --> 00:10:53.559 align:start position:0% 00:10:53.559 --> 00:11:27.549 align:start position:0% we<00:10:54.559> can<00:10:54.709> improve<00:10:54.829> the<00:10:55.160> efficiency<00:11:26.379> because<00:11:27.379> my 00:11:27.549 --> 00:11:27.559 align:start position:0% we can improve the efficiency because my 00:11:27.559 --> 00:11:29.860 align:start position:0% we can improve the efficiency because my name's<00:11:27.769> pollution<00:11:28.220> was<00:11:28.399> you<00:11:29.329> can't<00:11:29.600> really 00:11:29.860 --> 00:11:29.870 align:start position:0% name's pollution was you can't really 00:11:29.870 --> 00:11:31.480 align:start position:0% name's pollution was you can't really like<00:11:30.079> to<00:11:30.170> sell<00:11:30.410> a<00:11:30.470> future<00:11:30.920> and<00:11:31.100> they<00:11:31.220> would<00:11:31.370> be 00:11:31.480 --> 00:11:31.490 align:start position:0% like to sell a future and they would be 00:11:31.490 --> 00:11:41.420 align:start position:0% like to sell a future and they would be guaranteed 00:11:41.420 --> 00:11:41.430 align:start position:0% 00:11:41.430 --> 00:11:43.250 align:start position:0% works<00:11:41.850> for<00:11:42.180> there's<00:11:42.420> the<00:11:42.690> potentially 00:11:43.250 --> 00:11:43.260 align:start position:0% works for there's the potentially 00:11:43.260 --> 00:11:45.170 align:start position:0% works for there's the potentially effective<00:11:43.710> guest<00:11:44.340> token<00:11:44.700> works<00:11:44.910> by 00:11:45.170 --> 00:11:45.180 align:start position:0% effective guest token works by 00:11:45.180 --> 00:11:47.570 align:start position:0% effective guest token works by exploiting<00:11:45.510> data<00:11:45.900> and<00:11:46.890> issues<00:11:47.250> with<00:11:47.460> the 00:11:47.570 --> 00:11:47.580 align:start position:0% exploiting data and issues with the 00:11:47.580 --> 00:11:49.180 align:start position:0% exploiting data and issues with the refund<00:11:47.940> mechanics<00:11:48.540> where<00:11:48.720> you<00:11:48.810> can<00:11:48.960> basically 00:11:49.180 --> 00:11:49.190 align:start position:0% refund mechanics where you can basically 00:11:49.190 --> 00:11:51.590 align:start position:0% refund mechanics where you can basically most<00:11:50.190> of<00:11:50.310> the<00:11:50.370> miners<00:11:50.580> do<00:11:50.880> twice<00:11:51.090> as<00:11:51.300> much<00:11:51.330> work 00:11:51.590 --> 00:11:51.600 align:start position:0% most of the miners do twice as much work 00:11:51.600 --> 00:11:55.520 align:start position:0% most of the miners do twice as much work as<00:11:51.750> you<00:11:51.900> pay<00:11:53.060> but<00:11:54.060> it's<00:11:54.510> not<00:11:54.630> very<00:11:54.810> scalable<00:11:55.050> I 00:11:55.520 --> 00:11:55.530 align:start position:0% as you pay but it's not very scalable I 00:11:55.530 --> 00:11:57.350 align:start position:0% as you pay but it's not very scalable I mean<00:11:56.040> I<00:11:56.130> kind<00:11:56.370> of<00:11:56.400> wonder<00:11:56.700> if<00:11:56.790> we<00:11:56.940> shouldn't<00:11:57.210> if 00:11:57.350 --> 00:11:57.360 align:start position:0% mean I kind of wonder if we shouldn't if 00:11:57.360 --> 00:12:04.700 align:start position:0% mean I kind of wonder if we shouldn't if you<00:11:57.510> say<00:11:58.700> nothing<00:12:02.810> it<00:12:03.810> would<00:12:03.870> be<00:12:04.020> awful<00:12:04.440> but<00:12:04.620> at 00:12:04.700 --> 00:12:04.710 align:start position:0% you say nothing it would be awful but at 00:12:04.710 --> 00:12:06.550 align:start position:0% you say nothing it would be awful but at least<00:12:04.830> it<00:12:05.010> wouldn't<00:12:05.220> be<00:12:05.310> wasting<00:12:05.730> stories 00:12:06.550 --> 00:12:06.560 align:start position:0% least it wouldn't be wasting stories 00:12:06.560 --> 00:12:09.260 align:start position:0% least it wouldn't be wasting stories yeah<00:12:07.560> I<00:12:07.860> wish<00:12:08.070> I<00:12:08.160> was<00:12:08.280> wearing<00:12:08.490> my<00:12:08.520> I<00:12:08.880> was 00:12:09.260 --> 00:12:09.270 align:start position:0% yeah I wish I was wearing my I was 00:12:09.270 --> 00:12:11.830 align:start position:0% yeah I wish I was wearing my I was bringing<00:12:09.420> my<00:12:09.720> god<00:12:09.960> yes<00:12:10.260> token 00:12:11.830 --> 00:12:11.840 align:start position:0% bringing my god yes token 00:12:11.840 --> 00:12:15.020 align:start position:0% bringing my god yes token we're<00:12:12.840> in<00:12:13.020> today<00:12:13.140> but<00:12:13.370> it<00:12:14.370> was<00:12:14.520> the<00:12:14.850> funny 00:12:15.020 --> 00:12:15.030 align:start position:0% we're in today but it was the funny 00:12:15.030 --> 00:12:16.760 align:start position:0% we're in today but it was the funny thing<00:12:15.270> is<00:12:15.300> that<00:12:15.450> it<00:12:15.810> was<00:12:15.930> warned<00:12:16.170> about<00:12:16.290> in 00:12:16.760 --> 00:12:16.770 align:start position:0% thing is that it was warned about in 00:12:16.770 --> 00:12:20.390 align:start position:0% thing is that it was warned about in 2015<00:12:17.580> and<00:12:18.030> the<00:12:18.090> least<00:12:18.270> authority<00:12:19.280> you<00:12:20.280> know 00:12:20.390 --> 00:12:20.400 align:start position:0% 2015 and the least authority you know 00:12:20.400 --> 00:12:22.940 align:start position:0% 2015 and the least authority you know report<00:12:21.030> like<00:12:21.270> analysis<00:12:21.780> before<00:12:21.990> it's<00:12:22.740> very 00:12:22.940 --> 00:12:22.950 align:start position:0% report like analysis before it's very 00:12:22.950 --> 00:12:25.790 align:start position:0% report like analysis before it's very enlarged<00:12:23.400> and<00:12:24.290> but<00:12:25.290> well<00:12:25.440> the<00:12:25.530> way<00:12:25.650> they 00:12:25.790 --> 00:12:25.800 align:start position:0% enlarged and but well the way they 00:12:25.800 --> 00:12:27.560 align:start position:0% enlarged and but well the way they warned<00:12:26.040> about<00:12:26.130> it<00:12:26.340> was<00:12:26.460> minor<00:12:27.000> versus<00:12:27.360> minor 00:12:27.560 --> 00:12:27.570 align:start position:0% warned about it was minor versus minor 00:12:27.570 --> 00:12:31.760 align:start position:0% warned about it was minor versus minor storage<00:12:27.990> bombs<00:12:28.230> and<00:12:28.650> it's<00:12:29.640> not<00:12:29.790> exactly<00:12:30.770> what 00:12:31.760 --> 00:12:31.770 align:start position:0% storage bombs and it's not exactly what 00:12:31.770 --> 00:12:33.620 align:start position:0% storage bombs and it's not exactly what guess<00:12:31.980> token<00:12:32.340> has<00:12:32.460> what<00:12:32.790> did<00:12:33.060> has<00:12:33.330> the<00:12:33.450> same 00:12:33.620 --> 00:12:33.630 align:start position:0% guess token has what did has the same 00:12:33.630 --> 00:12:55.229 align:start position:0% guess token has what did has the same effect 00:12:55.229 --> 00:12:55.239 align:start position:0% 00:12:55.239 --> 00:13:14.289 align:start position:0% yeah<00:13:12.220> some<00:13:13.220> of<00:13:13.339> the<00:13:13.489> relate<00:13:13.819> such<00:13:14.059> as 00:13:14.289 --> 00:13:14.299 align:start position:0% yeah some of the relate such as 00:13:14.299 --> 00:13:17.079 align:start position:0% yeah some of the relate such as depression<00:13:14.629> is<00:13:15.049> like<00:13:15.399> we<00:13:16.399> say<00:13:16.639> that<00:13:16.939> you 00:13:17.079 --> 00:13:17.089 align:start position:0% depression is like we say that you 00:13:17.089 --> 00:13:19.479 align:start position:0% depression is like we say that you forgot<00:13:17.329> stateless<00:13:17.839> so<00:13:18.619> then<00:13:18.949> guess<00:13:19.220> if<00:13:19.399> you 00:13:19.479 --> 00:13:19.489 align:start position:0% forgot stateless so then guess if you 00:13:19.489 --> 00:13:21.609 align:start position:0% forgot stateless so then guess if you ever<00:13:19.609> stateless<00:13:20.029> mode<00:13:20.239> that<00:13:21.079> sure<00:13:21.319> on<00:13:21.499> that 00:13:21.609 --> 00:13:21.619 align:start position:0% ever stateless mode that sure on that 00:13:21.619 --> 00:13:24.129 align:start position:0% ever stateless mode that sure on that layer<00:13:22.039> we<00:13:22.369> can<00:13:22.639> maybe<00:13:22.939> price<00:13:23.659> that's 00:13:24.129 --> 00:13:24.139 align:start position:0% layer we can maybe price that's 00:13:24.139 --> 00:13:26.139 align:start position:0% layer we can maybe price that's different<00:13:24.499> but<00:13:24.799> guarantee<00:13:25.489> execution 00:13:26.139 --> 00:13:26.149 align:start position:0% different but guarantee execution 00:13:26.149 --> 00:13:27.849 align:start position:0% different but guarantee execution environments<00:13:26.629> could<00:13:26.749> have<00:13:26.899> the<00:13:27.019> same<00:13:27.229> sort<00:13:27.829> of 00:13:27.849 --> 00:13:27.859 align:start position:0% environments could have the same sort of 00:13:27.859 --> 00:13:41.639 align:start position:0% environments could have the same sort of thing<00:13:38.889> like<00:13:39.889> you<00:13:40.399> can<00:13:40.609> design<00:13:40.789> a 00:13:41.639 --> 00:13:41.649 align:start position:0% thing like you can design a 00:13:41.649 --> 00:13:51.219 align:start position:0% thing like you can design a controversial<00:13:46.029> I<00:13:49.869> just<00:13:50.869> stores<00:13:51.139> the 00:13:51.219 --> 00:13:51.229 align:start position:0% controversial I just stores the 00:13:51.229 --> 00:13:54.790 align:start position:0% controversial I just stores the compassion<00:13:51.919> for<00:13:52.039> each<00:13:52.069> child 00:13:54.790 --> 00:13:54.800 align:start position:0% compassion for each child 00:13:54.800 --> 00:13:58.960 align:start position:0% compassion for each child we<00:13:55.190> have<00:13:56.589> destructive<00:13:57.589> list<00:13:57.890> and<00:13:58.310> they<00:13:58.730> say 00:13:58.960 --> 00:13:58.970 align:start position:0% we have destructive list and they say 00:13:58.970 --> 00:14:03.430 align:start position:0% we have destructive list and they say the<00:13:59.209> great<00:13:59.420> deal<00:13:59.600> guess<00:13:59.839> that<00:14:00.820> mrs.<00:14:02.440> teevee 00:14:03.430 --> 00:14:03.440 align:start position:0% the great deal guess that mrs. teevee 00:14:03.440 --> 00:14:05.259 align:start position:0% the great deal guess that mrs. teevee similarly<00:14:04.160> does<00:14:04.370> the<00:14:04.490> same<00:14:04.670> thing<00:14:04.910> we<00:14:05.120> only 00:14:05.259 --> 00:14:05.269 align:start position:0% similarly does the same thing we only 00:14:05.269 --> 00:14:16.150 align:start position:0% similarly does the same thing we only store<00:14:05.540> -<00:14:09.130> and<00:14:10.130> I<00:14:10.279> think<00:14:13.269> yeah<00:14:14.709> one<00:14:15.709> of<00:14:15.740> the 00:14:16.150 --> 00:14:16.160 align:start position:0% store - and I think yeah one of the 00:14:16.160 --> 00:14:18.400 align:start position:0% store - and I think yeah one of the contractor<00:14:16.700> on<00:14:16.940> that<00:14:17.120> is<00:14:17.390> you<00:14:18.079> could<00:14:18.230> also 00:14:18.400 --> 00:14:18.410 align:start position:0% contractor on that is you could also 00:14:18.410 --> 00:14:20.319 align:start position:0% contractor on that is you could also like<00:14:18.769> using<00:14:18.980> sensors<00:14:19.550> to<00:14:19.850> do<00:14:20.089> any 00:14:20.319 --> 00:14:20.329 align:start position:0% like using sensors to do any 00:14:20.329 --> 00:14:23.290 align:start position:0% like using sensors to do any calculations<00:14:21.610> but<00:14:22.610> kind<00:14:22.880> of<00:14:23.000> if<00:14:23.120> you<00:14:23.209> have 00:14:23.290 --> 00:14:23.300 align:start position:0% calculations but kind of if you have 00:14:23.300 --> 00:14:24.730 align:start position:0% calculations but kind of if you have like<00:14:23.450> a<00:14:23.480> two-party<00:14:24.019> system<00:14:24.410> and<00:14:24.529> that's 00:14:24.730 --> 00:14:24.740 align:start position:0% like a two-party system and that's 00:14:24.740 --> 00:14:26.079 align:start position:0% like a two-party system and that's trading<00:14:25.010> or<00:14:25.220> something<00:14:25.550> and<00:14:25.730> you<00:14:25.910> have<00:14:26.060> a 00:14:26.079 --> 00:14:26.089 align:start position:0% trading or something and you have a 00:14:26.089 --> 00:14:29.040 align:start position:0% trading or something and you have a formula<00:14:26.450> that<00:14:26.630> derives<00:14:27.620> the<00:14:27.950> total<00:14:28.220> points 00:14:29.040 --> 00:14:29.050 align:start position:0% formula that derives the total points 00:14:29.050 --> 00:14:31.810 align:start position:0% formula that derives the total points both<00:14:30.050> parties<00:14:30.440> on<00:14:30.529> both<00:14:30.560> sides<00:14:31.010> actually<00:14:31.550> have 00:14:31.810 --> 00:14:31.820 align:start position:0% both parties on both sides actually have 00:14:31.820 --> 00:14:33.730 align:start position:0% both parties on both sides actually have incentives<00:14:32.329> to<00:14:32.390> calculate<00:14:33.200> the<00:14:33.320> closest 00:14:33.730 --> 00:14:33.740 align:start position:0% incentives to calculate the closest 00:14:33.740 --> 00:14:35.380 align:start position:0% incentives to calculate the closest value<00:14:33.920> and<00:14:34.490> you<00:14:34.730> could<00:14:34.880> actually<00:14:35.029> catch<00:14:35.360> the 00:14:35.380 --> 00:14:35.390 align:start position:0% value and you could actually catch the 00:14:35.390 --> 00:14:37.960 align:start position:0% value and you could actually catch the value<00:14:35.870> of<00:14:35.959> storage<00:14:36.380> and<00:14:36.680> then<00:14:36.860> make<00:14:37.700> them 00:14:37.960 --> 00:14:37.970 align:start position:0% value of storage and then make them 00:14:37.970 --> 00:14:39.910 align:start position:0% value of storage and then make them constantly<00:14:38.450> some<00:14:38.810> transactions<00:14:39.529> to<00:14:39.649> get<00:14:39.800> an 00:14:39.910 --> 00:14:39.920 align:start position:0% constantly some transactions to get an 00:14:39.920 --> 00:14:40.920 align:start position:0% constantly some transactions to get an actual<00:14:40.130> Maggie 00:14:40.920 --> 00:14:40.930 align:start position:0% actual Maggie 00:14:40.930 --> 00:14:47.319 align:start position:0% actual Maggie so<00:14:41.930> yeah<00:14:42.670> interesting<00:14:43.670> stateless<00:14:46.180> so<00:14:47.180> maybe 00:14:47.319 --> 00:14:47.329 align:start position:0% so yeah interesting stateless so maybe 00:14:47.329 --> 00:14:51.790 align:start position:0% so yeah interesting stateless so maybe the<00:14:47.600> unisex<00:14:48.550> you<00:14:49.550> said<00:14:49.790> that<00:14:50.560> and<00:14:51.560> you 00:14:51.790 --> 00:14:51.800 align:start position:0% the unisex you said that and you 00:14:51.800 --> 00:14:55.509 align:start position:0% the unisex you said that and you senators<00:14:52.790> who<00:14:52.970> just<00:14:54.070> arrived<00:14:55.070> at<00:14:55.250> the<00:14:55.339> hash 00:14:55.509 --> 00:14:55.519 align:start position:0% senators who just arrived at the hash 00:14:55.519 --> 00:14:57.100 align:start position:0% senators who just arrived at the hash how<00:14:56.390> do<00:14:56.450> I<00:14:56.480> get<00:14:56.600> the<00:14:56.690> date<00:14:56.839> that<00:14:56.959> you're 00:14:57.100 --> 00:14:57.110 align:start position:0% how do I get the date that you're 00:14:57.110 --> 00:15:00.220 align:start position:0% how do I get the date that you're sitting<00:14:57.350> on<00:14:58.220> the<00:14:58.579> order<00:14:58.880> of<00:14:58.910> at<00:14:59.839> least<00:14:59.990> the 00:15:00.220 --> 00:15:00.230 align:start position:0% sitting on the order of at least the 00:15:00.230 --> 00:15:03.040 align:start position:0% sitting on the order of at least the kilobyte<00:15:00.700> very<00:15:01.700> intrigued<00:15:02.029> basically<00:15:02.480> we 00:15:03.040 --> 00:15:03.050 align:start position:0% kilobyte very intrigued basically we 00:15:03.050 --> 00:15:04.630 align:start position:0% kilobyte very intrigued basically we think<00:15:03.170> that<00:15:03.440> saying<00:15:03.620> like<00:15:03.800> 500<00:15:04.220> bytes<00:15:04.430> of 00:15:04.630 --> 00:15:04.640 align:start position:0% think that saying like 500 bytes of 00:15:04.640 --> 00:15:08.680 align:start position:0% think that saying like 500 bytes of exercise<00:15:05.300> for<00:15:05.510> DNA<00:15:05.779> century<00:15:06.310> and<00:15:07.310> so<00:15:07.610> you<00:15:07.690> you 00:15:08.680 --> 00:15:08.690 align:start position:0% exercise for DNA century and so you you 00:15:08.690 --> 00:15:10.390 align:start position:0% exercise for DNA century and so you you know<00:15:08.810> use<00:15:08.990> the<00:15:09.020> Mercer<00:15:09.380> report 00:15:10.390 --> 00:15:10.400 align:start position:0% know use the Mercer report 00:15:10.400 --> 00:15:12.550 align:start position:0% know use the Mercer report things<00:15:10.550> of<00:15:10.790> how<00:15:11.210> the<00:15:11.270> beam<00:15:11.570> and<00:15:11.900> it<00:15:12.020> verifies 00:15:12.550 --> 00:15:12.560 align:start position:0% things of how the beam and it verifies 00:15:12.560 --> 00:15:14.559 align:start position:0% things of how the beam and it verifies thank<00:15:12.890> you 00:15:14.559 --> 00:15:14.569 align:start position:0% thank you 00:15:14.569 --> 00:15:16.819 align:start position:0% thank you stores<00:15:15.569> the<00:15:15.749> Hessian<00:15:16.019> that<00:15:16.199> definitely<00:15:16.589> hold 00:15:16.819 --> 00:15:16.829 align:start position:0% stores the Hessian that definitely hold 00:15:16.829 --> 00:15:18.319 align:start position:0% stores the Hessian that definitely hold some<00:15:17.009> of<00:15:17.069> the<00:15:17.189> links<00:15:17.429> one<00:15:17.639> assignment<00:15:18.269> that 00:15:18.319 --> 00:15:18.329 align:start position:0% some of the links one assignment that 00:15:18.329 --> 00:15:20.419 align:start position:0% some of the links one assignment that Kate<00:15:18.540> Hewson<00:15:18.779> back<00:15:19.259> and<00:15:19.949> used<00:15:20.220> to<00:15:20.309> the 00:15:20.419 --> 00:15:20.429 align:start position:0% Kate Hewson back and used to the 00:15:20.429 --> 00:15:22.879 align:start position:0% Kate Hewson back and used to the previous<00:15:20.850> record<00:15:21.299> verify<00:15:21.689> passionately<00:15:22.649> and 00:15:22.879 --> 00:15:22.889 align:start position:0% previous record verify passionately and 00:15:22.889 --> 00:15:27.019 align:start position:0% previous record verify passionately and so<00:15:23.040> on<00:15:23.189> see<00:15:23.819> some<00:15:23.999> changes<00:15:24.709> but<00:15:25.819> it's<00:15:26.819> not<00:15:26.999> a 00:15:27.019 --> 00:15:27.029 align:start position:0% so on see some changes but it's not a 00:15:27.029 --> 00:15:29.239 align:start position:0% so on see some changes but it's not a long<00:15:27.269> title<00:15:27.569> but<00:15:27.809> storage<00:15:28.649> is<00:15:28.739> very<00:15:28.769> expensive 00:15:29.239 --> 00:15:29.249 align:start position:0% long title but storage is very expensive 00:15:29.249 --> 00:15:32.210 align:start position:0% long title but storage is very expensive and<00:15:30.239> it's<00:15:30.779> been<00:15:30.929> watching<00:15:31.319> that<00:15:31.350> possibility 00:15:32.210 --> 00:15:32.220 align:start position:0% and it's been watching that possibility 00:15:32.220 --> 00:15:34.579 align:start position:0% and it's been watching that possibility twice<00:15:32.579> by<00:15:32.939> apologizing<00:15:33.689> as<00:15:33.899> it<00:15:33.989> is<00:15:34.079> one<00:15:34.319> cycle 00:15:34.579 --> 00:15:34.589 align:start position:0% twice by apologizing as it is one cycle 00:15:34.589 --> 00:15:39.079 align:start position:0% twice by apologizing as it is one cycle data<00:15:35.009> and<00:15:35.249> store<00:15:35.579> Freeland<00:15:37.609> independent<00:15:38.609> ever 00:15:39.079 --> 00:15:39.089 align:start position:0% data and store Freeland independent ever 00:15:39.089 --> 00:15:42.309 align:start position:0% data and store Freeland independent ever decides<00:15:39.509> that<00:15:40.069> if<00:15:41.069> you<00:15:41.309> do<00:15:41.459> have<00:15:41.669> a<00:15:41.879> lot<00:15:42.029> of 00:15:42.309 --> 00:15:42.319 align:start position:0% decides that if you do have a lot of 00:15:42.319 --> 00:15:45.590 align:start position:0% decides that if you do have a lot of data<00:15:43.319> you<00:15:43.829> need<00:15:44.160> to<00:15:44.249> pass<00:15:44.459> in<00:15:44.669> and<00:15:44.939> you<00:15:45.029> need<00:15:45.389> to 00:15:45.590 --> 00:15:45.600 align:start position:0% data you need to pass in and you need to 00:15:45.600 --> 00:15:48.499 align:start position:0% data you need to pass in and you need to do<00:15:45.899> certain<00:15:46.410> mental<00:15:46.759> computation<00:15:47.759> on<00:15:48.119> them<00:15:48.299> to 00:15:48.499 --> 00:15:48.509 align:start position:0% do certain mental computation on them to 00:15:48.509 --> 00:15:50.960 align:start position:0% do certain mental computation on them to derive<00:15:48.839> two<00:15:49.079> distinct<00:15:49.470> you<00:15:49.739> store<00:15:50.249> there's 00:15:50.960 --> 00:15:50.970 align:start position:0% derive two distinct you store there's 00:15:50.970 --> 00:15:53.179 align:start position:0% derive two distinct you store there's like<00:15:51.119> a<00:15:51.149> trio<00:15:51.389> Farragut<00:15:51.959> is<00:15:52.139> way<00:15:52.649> cheaper<00:15:52.679> to 00:15:53.179 --> 00:15:53.189 align:start position:0% like a trio Farragut is way cheaper to 00:15:53.189 --> 00:15:55.939 align:start position:0% like a trio Farragut is way cheaper to store<00:15:53.459> stuff<00:15:53.549> on<00:15:54.029> I<00:15:54.959> think<00:15:55.290> it<00:15:55.470> depends<00:15:55.739> on<00:15:55.889> the 00:15:55.939 --> 00:15:55.949 align:start position:0% store stuff on I think it depends on the 00:15:55.949 --> 00:15:58.519 align:start position:0% store stuff on I think it depends on the computation<00:15:56.279> so<00:15:56.970> in<00:15:57.029> this<00:15:57.149> case<00:15:57.419> I<00:15:57.749> think<00:15:57.809> it's 00:15:58.519 --> 00:15:58.529 align:start position:0% computation so in this case I think it's 00:15:58.529 --> 00:16:01.489 align:start position:0% computation so in this case I think it's obviously<00:15:59.009> in<00:15:59.579> this<00:15:59.699> case<00:16:00.379> when<00:16:01.379> you're 00:16:01.489 --> 00:16:01.499 align:start position:0% obviously in this case when you're 00:16:01.499 --> 00:16:02.989 align:start position:0% obviously in this case when you're passing<00:16:01.739> of<00:16:01.980> the<00:16:02.069> redundant<00:16:02.429> are<00:16:02.579> the<00:16:02.819> only 00:16:02.989 --> 00:16:02.999 align:start position:0% passing of the redundant are the only 00:16:02.999 --> 00:16:05.390 align:start position:0% passing of the redundant are the only computation 00:16:05.390 --> 00:16:05.400 align:start position:0% computation 00:16:05.400 --> 00:16:07.790 align:start position:0% computation some<00:16:05.640> codes<00:16:06.330> to<00:16:06.510> verify<00:16:06.870> that<00:16:06.930> the<00:16:07.290> cycnus<00:16:07.650> is 00:16:07.790 --> 00:16:07.800 align:start position:0% some codes to verify that the cycnus is 00:16:07.800 --> 00:16:10.490 align:start position:0% some codes to verify that the cycnus is passed<00:16:08.040> and<00:16:08.280> verified<00:16:09.240> last<00:16:09.480> time<00:16:09.720> so<00:16:10.470> we 00:16:10.490 --> 00:16:10.500 align:start position:0% passed and verified last time so we 00:16:10.500 --> 00:16:11.840 align:start position:0% passed and verified last time so we don't<00:16:10.710> repeating<00:16:11.280> a<00:16:11.370> lot<00:16:11.490> of<00:16:11.580> computation 00:16:11.840 --> 00:16:11.850 align:start position:0% don't repeating a lot of computation 00:16:11.850 --> 00:16:13.610 align:start position:0% don't repeating a lot of computation because<00:16:12.450> their<00:16:12.600> clarifications<00:16:13.350> only<00:16:13.500> two 00:16:13.610 --> 00:16:13.620 align:start position:0% because their clarifications only two 00:16:13.620 --> 00:16:16.210 align:start position:0% because their clarifications only two months 00:16:16.210 --> 00:16:16.220 align:start position:0% 00:16:16.220 --> 00:16:17.580 align:start position:0% actually 00:16:17.580 --> 00:16:17.590 align:start position:0% actually 00:16:17.590 --> 00:16:20.190 align:start position:0% actually I<00:16:17.640> guess<00:16:18.640> two<00:16:18.850> bets<00:16:19.029> for<00:16:19.180> our<00:16:19.330> panel<00:16:19.630> this<00:16:19.660> you 00:16:20.190 --> 00:16:20.200 align:start position:0% I guess two bets for our panel this you 00:16:20.200 --> 00:16:25.290 align:start position:0% I guess two bets for our panel this you want<00:16:20.350> use<00:16:20.470> his<00:16:20.680> works<00:16:20.920> Welland<00:16:23.970> the<00:16:24.970> issue<00:16:25.120> is 00:16:25.290 --> 00:16:25.300 align:start position:0% want use his works Welland the issue is 00:16:25.300 --> 00:16:27.150 align:start position:0% want use his works Welland the issue is when<00:16:25.450> there<00:16:25.660> when<00:16:26.020> every<00:16:26.590> part<00:16:26.800> is<00:16:26.860> Merkel 00:16:27.150 --> 00:16:27.160 align:start position:0% when there when every part is Merkel 00:16:27.160 --> 00:16:29.640 align:start position:0% when there when every part is Merkel cruises<00:16:27.700> and<00:16:27.850> all<00:16:28.060> that<00:16:28.240> Merkel<00:16:28.690> data<00:16:28.870> is<00:16:29.320> what 00:16:29.640 --> 00:16:29.650 align:start position:0% cruises and all that Merkel data is what 00:16:29.650 --> 00:16:33.240 align:start position:0% cruises and all that Merkel data is what makes<00:16:30.040> the<00:16:30.160> call<00:16:30.340> to<00:16:31.650> it's<00:16:32.650> interesting<00:16:32.800> you 00:16:33.240 --> 00:16:33.250 align:start position:0% makes the call to it's interesting you 00:16:33.250 --> 00:16:37.050 align:start position:0% makes the call to it's interesting you senators<00:16:34.290> currently<00:16:35.290> just<00:16:35.500> passing<00:16:35.950> it<00:16:36.100> you 00:16:37.050 --> 00:16:37.060 align:start position:0% senators currently just passing it you 00:16:37.060 --> 00:16:48.240 align:start position:0% senators currently just passing it you know<00:16:37.150> just<00:16:37.180> that<00:16:39.390> just<00:16:40.390> the<00:16:40.480> DNS<00:16:40.810> data<00:16:47.250> and 00:16:48.240 --> 00:16:48.250 align:start position:0% know just that just the DNS data and 00:16:48.250 --> 00:16:50.820 align:start position:0% know just that just the DNS data and then<00:16:48.940> that's<00:16:49.150> about<00:16:49.240> to<00:16:49.540> be<00:16:49.630> you<00:16:50.170> know<00:16:50.260> four 00:16:50.820 --> 00:16:50.830 align:start position:0% then that's about to be you know four 00:16:50.830 --> 00:17:03.620 align:start position:0% then that's about to be you know four times<00:16:50.980> cheaper<00:16:51.279> after<00:16:52.060> history<00:16:52.510> all<00:16:52.720> right<00:16:52.900> so 00:17:03.620 --> 00:17:03.630 align:start position:0% 00:17:03.630 --> 00:17:06.510 align:start position:0% we<00:17:04.630> still<00:17:04.930> need<00:17:04.959> he<00:17:05.290> receive<00:17:05.800> the<00:17:06.310> code 00:17:06.510 --> 00:17:06.520 align:start position:0% we still need he receive the code 00:17:06.520 --> 00:17:11.150 align:start position:0% we still need he receive the code deposit<00:17:07.089> limit<00:17:07.240> I<00:17:07.600> think<00:17:07.660> it's<00:17:08.110> your<00:17:08.319> see 00:17:11.150 --> 00:17:11.160 align:start position:0% 00:17:11.160 --> 00:17:16.199 align:start position:0% because<00:17:12.160> I<00:17:12.339> mean<00:17:13.150> the<00:17:13.439> contract<00:17:14.439> yeah<00:17:15.400> thank 00:17:16.199 --> 00:17:16.209 align:start position:0% because I mean the contract yeah thank 00:17:16.209 --> 00:17:18.960 align:start position:0% because I mean the contract yeah thank you<00:17:16.439> because<00:17:17.439> I<00:17:17.620> thought<00:17:18.189> some<00:17:18.430> discussion 00:17:18.960 --> 00:17:18.970 align:start position:0% you because I thought some discussion 00:17:18.970 --> 00:17:21.030 align:start position:0% you because I thought some discussion and<00:17:19.089> a<00:17:19.209> big<00:17:19.420> magician<00:17:19.780> forum<00:17:20.380> that<00:17:20.620> there<00:17:20.890> is 00:17:21.030 --> 00:17:21.040 align:start position:0% and a big magician forum that there is 00:17:21.040 --> 00:17:23.640 align:start position:0% and a big magician forum that there is some<00:17:21.310> debate<00:17:21.699> and<00:17:22.360> I<00:17:22.900> think<00:17:22.929> more<00:17:23.439> and<00:17:23.500> more 00:17:23.640 --> 00:17:23.650 align:start position:0% some debate and I think more and more 00:17:23.650 --> 00:17:26.460 align:start position:0% some debate and I think more and more demanding<00:17:24.280> into<00:17:24.579> this<00:17:24.699> limit<00:17:25.060> and<00:17:25.480> this<00:17:26.319> is 00:17:26.460 --> 00:17:26.470 align:start position:0% demanding into this limit and this is 00:17:26.470 --> 00:17:28.530 align:start position:0% demanding into this limit and this is really<00:17:26.770> needed<00:17:27.069> some<00:17:27.610> of<00:17:27.730> the<00:17:27.819> problem<00:17:28.420> is 00:17:28.530 --> 00:17:28.540 align:start position:0% really needed some of the problem is 00:17:28.540 --> 00:17:30.810 align:start position:0% really needed some of the problem is that<00:17:28.569> was<00:17:29.050> any<00:17:29.800> static<00:17:30.220> scheme<00:17:30.490> is<00:17:30.640> not 00:17:30.810 --> 00:17:30.820 align:start position:0% that was any static scheme is not 00:17:30.820 --> 00:17:32.409 align:start position:0% that was any static scheme is not contracted<00:17:31.480> alone 00:17:32.409 --> 00:17:32.419 align:start position:0% contracted alone 00:17:32.419 --> 00:17:34.570 align:start position:0% contracted alone say<00:17:32.570> not<00:17:32.749> disk<00:17:33.049> and<00:17:33.320> also<00:17:33.980> just<00:17:34.129> the<00:17:34.220> basic 00:17:34.570 --> 00:17:34.580 align:start position:0% say not disk and also just the basic 00:17:34.580 --> 00:17:36.159 align:start position:0% say not disk and also just the basic Java<00:17:34.789> test<00:17:34.970> analysis<00:17:35.570> for<00:17:35.720> the<00:17:35.809> whole<00:17:35.929> thing 00:17:36.159 --> 00:17:36.169 align:start position:0% Java test analysis for the whole thing 00:17:36.169 --> 00:17:38.259 align:start position:0% Java test analysis for the whole thing and<00:17:36.769> it's<00:17:36.950> the<00:17:37.039> size<00:17:37.279> that<00:17:37.309> is<00:17:37.700> I'm<00:17:37.850> down<00:17:38.059> to 00:17:38.259 --> 00:17:38.269 align:start position:0% and it's the size that is I'm down to 00:17:38.269 --> 00:17:39.759 align:start position:0% and it's the size that is I'm down to did<00:17:38.509> something<00:17:38.899> consumers<00:17:39.259> a<00:17:39.320> very<00:17:39.499> large 00:17:39.759 --> 00:17:39.769 align:start position:0% did something consumers a very large 00:17:39.769 --> 00:17:41.470 align:start position:0% did something consumers a very large contracts<00:17:40.309> that<00:17:40.549> only<00:17:40.700> execute<00:17:41.179> to<00:17:41.269> say<00:17:41.419> to 00:17:41.470 --> 00:17:41.480 align:start position:0% contracts that only execute to say to 00:17:41.480 --> 00:17:44.739 align:start position:0% contracts that only execute to say to all<00:17:41.779> codes<00:17:42.049> before<00:17:42.320> exiting<00:17:42.859> and<00:17:43.340> the<00:17:44.090> the<00:17:44.450> VM 00:17:44.739 --> 00:17:44.749 align:start position:0% all codes before exiting and the the VM 00:17:44.749 --> 00:17:46.180 align:start position:0% all codes before exiting and the the VM is<00:17:44.899> to<00:17:45.049> do<00:17:45.139> a<00:17:45.169> great<00:17:45.409> deal<00:17:45.559> of<00:17:45.590> work<00:17:45.799> for<00:17:46.009> very 00:17:46.180 --> 00:17:46.190 align:start position:0% is to do a great deal of work for very 00:17:46.190 --> 00:17:49.049 align:start position:0% is to do a great deal of work for very little<00:17:46.399> gas<00:17:46.549> so<00:17:47.269> that<00:17:47.299> the<00:17:48.019> OS<00:17:48.230> vector<00:17:48.649> so 00:17:49.049 --> 00:17:49.059 align:start position:0% little gas so that the OS vector so 00:17:49.059 --> 00:17:52.900 align:start position:0% little gas so that the OS vector so until<00:17:50.059> we<00:17:50.119> ever<00:17:50.330> be<00:17:50.539> a<00:17:50.570> solution 00:17:52.900 --> 00:17:52.910 align:start position:0% 00:17:52.910 --> 00:18:42.730 align:start position:0% I<00:18:39.730> kind<00:18:40.730> of<00:18:40.790> use<00:18:41.030> that<00:18:41.060> as<00:18:41.540> easy<00:18:42.170> any<00:18:42.380> plan 00:18:42.730 --> 00:18:42.740 align:start position:0% I kind of use that as easy any plan 00:18:42.740 --> 00:18:46.720 align:start position:0% I kind of use that as easy any plan implementer<00:18:43.960> because<00:18:44.960> yeah<00:18:45.460> they<00:18:46.460> said<00:18:46.700> it's 00:18:46.720 --> 00:18:46.730 align:start position:0% implementer because yeah they said it's 00:18:46.730 --> 00:18:49.780 align:start position:0% implementer because yeah they said it's like<00:18:47.030> I<00:18:47.360> know<00:18:47.860> when<00:18:48.860> I<00:18:48.890> actually<00:18:49.100> build<00:18:49.550> myself 00:18:49.780 --> 00:18:49.790 align:start position:0% like I know when I actually build myself 00:18:49.790 --> 00:18:52.150 align:start position:0% like I know when I actually build myself to<00:18:50.180> adapt<00:18:50.480> the<00:18:51.200> code<00:18:51.410> size<00:18:51.650> will<00:18:51.890> not<00:18:51.920> be 00:18:52.150 --> 00:18:52.160 align:start position:0% to adapt the code size will not be 00:18:52.160 --> 00:18:54.130 align:start position:0% to adapt the code size will not be graded<00:18:52.430> on<00:18:52.700> that<00:18:52.910> and<00:18:53.210> I<00:18:53.270> can<00:18:53.300> have<00:18:53.660> my<00:18:53.690> summer 00:18:54.130 --> 00:18:54.140 align:start position:0% graded on that and I can have my summer 00:18:54.140 --> 00:18:57.790 align:start position:0% graded on that and I can have my summer sample<00:18:54.590> some<00:18:54.710> new<00:18:54.830> notch<00:18:55.040> because<00:18:56.800> except 00:18:57.790 --> 00:18:57.800 align:start position:0% sample some new notch because except 00:18:57.800 --> 00:19:00.250 align:start position:0% sample some new notch because except that<00:18:58.010> something<00:18:58.370> like<00:18:58.780> analysis<00:18:59.780> you<00:18:59.900> have<00:19:00.080> to 00:19:00.250 --> 00:19:00.260 align:start position:0% that something like analysis you have to 00:19:00.260 --> 00:19:02.920 align:start position:0% that something like analysis you have to do<00:19:00.410> when<00:19:01.040> you<00:19:01.160> load<00:19:01.400> the<00:19:01.430> count<00:19:01.850> and<00:19:02.150> you<00:19:02.600> about 00:19:02.920 --> 00:19:02.930 align:start position:0% do when you load the count and you about 00:19:02.930 --> 00:19:06.640 align:start position:0% do when you load the count and you about execute<00:19:03.530> it<00:19:04.780> but<00:19:05.780> I<00:19:05.840> think<00:19:06.080> that<00:19:06.230> I<00:19:06.380> way<00:19:06.590> to 00:19:06.640 --> 00:19:06.650 align:start position:0% execute it but I think that I way to 00:19:06.650 --> 00:19:09.550 align:start position:0% execute it but I think that I way to kind<00:19:07.370> of<00:19:07.490> work<00:19:08.000> around<00:19:08.060> that<00:19:08.570> I<00:19:08.810> mean<00:19:09.020> some<00:19:09.530> of 00:19:09.550 --> 00:19:09.560 align:start position:0% kind of work around that I mean some of 00:19:09.560 --> 00:19:13.750 align:start position:0% kind of work around that I mean some of these<00:19:09.860> analysis<00:19:10.580> can<00:19:10.820> be<00:19:10.850> done<00:19:11.260> nicely<00:19:12.760> but 00:19:13.750 --> 00:19:13.760 align:start position:0% these analysis can be done nicely but 00:19:13.760 --> 00:19:16.360 align:start position:0% these analysis can be done nicely but it's<00:19:13.970> much<00:19:14.270> more<00:19:14.480> complicated<00:19:14.870> and<00:19:15.620> we<00:19:16.160> could 00:19:16.360 --> 00:19:16.370 align:start position:0% it's much more complicated and we could 00:19:16.370 --> 00:19:20.890 align:start position:0% it's much more complicated and we could do<00:19:16.520> now<00:19:16.850> I<00:19:17.150> just<00:19:17.510> come<00:19:18.080> to<00:19:18.110> code<00:19:18.470> once<00:19:19.100> and<00:19:19.900> also 00:19:20.890 --> 00:19:20.900 align:start position:0% do now I just come to code once and also 00:19:20.900 --> 00:19:23.950 align:start position:0% do now I just come to code once and also this<00:19:21.050> this<00:19:21.410> this<00:19:21.710> this<00:19:22.340> analysis<00:19:23.090> can<00:19:23.300> be<00:19:23.330> can 00:19:23.950 --> 00:19:23.960 align:start position:0% this this this this analysis can be can 00:19:23.960 --> 00:19:26.500 align:start position:0% this this this this analysis can be can be<00:19:24.110> cached<00:19:24.380> but<00:19:25.280> yeah<00:19:25.550> actually<00:19:26.180> hugely 00:19:26.500 --> 00:19:26.510 align:start position:0% be cached but yeah actually hugely 00:19:26.510 --> 00:19:29.590 align:start position:0% be cached but yeah actually hugely exploiting<00:19:27.260> that<00:19:27.370> doing<00:19:28.370> much<00:19:28.640> more<00:19:28.850> things 00:19:29.590 --> 00:19:29.600 align:start position:0% exploiting that doing much more things 00:19:29.600 --> 00:19:32.170 align:start position:0% exploiting that doing much more things doing<00:19:30.020> this<00:19:30.170> analysis<00:19:30.800> because<00:19:31.610> I<00:19:31.760> know<00:19:31.910> the 00:19:32.170 --> 00:19:32.180 align:start position:0% doing this analysis because I know the 00:19:32.180 --> 00:19:34.100 align:start position:0% doing this analysis because I know the the<00:19:32.480> curse<00:19:32.720> I<00:19:32.960> swap<00:19:33.260> meets 00:19:34.100 --> 00:19:34.110 align:start position:0% the curse I swap meets 00:19:34.110 --> 00:19:38.180 align:start position:0% the curse I swap meets super<00:19:34.500> huge<00:19:34.799> I<00:19:35.270> get<00:19:36.270> it<00:19:36.660> so<00:19:36.960> yeah<00:19:37.140> it's<00:19:37.799> limited 00:19:38.180 --> 00:19:38.190 align:start position:0% super huge I get it so yeah it's limited 00:19:38.190 --> 00:19:41.530 align:start position:0% super huge I get it so yeah it's limited by<00:19:38.370> the<00:19:39.120> gas<00:19:39.360> price<00:19:39.660> we<00:19:40.080> can<00:19:40.260> yeah<00:19:40.559> you<00:19:40.740> cannot 00:19:41.530 --> 00:19:41.540 align:start position:0% by the gas price we can yeah you cannot 00:19:41.540 --> 00:19:44.840 align:start position:0% by the gas price we can yeah you cannot deployed<00:19:42.860> super<00:19:43.860> big<00:19:44.070> contracts<00:19:44.610> because 00:19:44.840 --> 00:19:44.850 align:start position:0% deployed super big contracts because 00:19:44.850 --> 00:19:47.000 align:start position:0% deployed super big contracts because like<00:19:45.210> you<00:19:45.330> pay<00:19:45.540> for<00:19:45.600> them<00:19:45.929> to<00:19:46.080> bite<00:19:46.350> to<00:19:46.890> the 00:19:47.000 --> 00:19:47.010 align:start position:0% like you pay for them to bite to the 00:19:47.010 --> 00:19:47.870 align:start position:0% like you pay for them to bite to the blank<00:19:47.309> dad 00:19:47.870 --> 00:19:47.880 align:start position:0% blank dad 00:19:47.880 --> 00:19:50.060 align:start position:0% blank dad but<00:19:48.390> for<00:19:48.660> me<00:19:48.809> it's<00:19:49.020> it's<00:19:49.260> not<00:19:49.530> static<00:19:49.799> routing 00:19:50.060 --> 00:19:50.070 align:start position:0% but for me it's it's not static routing 00:19:50.070 --> 00:19:52.910 align:start position:0% but for me it's it's not static routing information<00:19:50.340> because<00:19:51.170> this<00:19:52.170> change<00:19:52.530> is<00:19:52.740> way 00:19:52.910 --> 00:19:52.920 align:start position:0% information because this change is way 00:19:52.920 --> 00:19:53.510 align:start position:0% information because this change is way too<00:19:52.980> wrong 00:19:53.510 --> 00:19:53.520 align:start position:0% too wrong 00:19:53.520 --> 00:19:55.520 align:start position:0% too wrong so<00:19:53.730> when<00:19:53.940> I<00:19:53.970> actually<00:19:54.299> like<00:19:54.900> make<00:19:55.140> design 00:19:55.520 --> 00:19:55.530 align:start position:0% so when I actually like make design 00:19:55.530 --> 00:20:00.049 align:start position:0% so when I actually like make design decisions<00:19:56.059> doing<00:19:57.260> yeah<00:19:58.290> implementing<00:19:59.220> EVM 00:20:00.049 --> 00:20:00.059 align:start position:0% decisions doing yeah implementing EVM 00:20:00.059 --> 00:20:03.020 align:start position:0% decisions doing yeah implementing EVM this<00:20:01.020> is<00:20:01.170> not<00:20:01.380> like<00:20:01.590> strict<00:20:01.980> grant<00:20:02.340> redux<00:20:02.880> I 00:20:03.020 --> 00:20:03.030 align:start position:0% this is not like strict grant redux I 00:20:03.030 --> 00:20:05.510 align:start position:0% this is not like strict grant redux I mean<00:20:03.840> I<00:20:03.990> cannot<00:20:04.290> guess<00:20:04.559> what<00:20:04.890> works<00:20:05.250> it's<00:20:05.429> like 00:20:05.510 --> 00:20:05.520 align:start position:0% mean I cannot guess what works it's like 00:20:05.520 --> 00:20:42.919 align:start position:0% mean I cannot guess what works it's like the<00:20:05.880> reasonable<00:20:06.450> size<00:20:12.049> for<00:20:13.049> you<00:20:13.200> I<00:20:13.230> mean<00:20:41.929> like 00:20:42.919 --> 00:20:42.929 align:start position:0% the reasonable size for you I mean like 00:20:42.929 --> 00:20:52.159 align:start position:0% the reasonable size for you I mean like I<00:20:43.290> know<00:20:43.350> that<00:20:44.299> for<00:20:45.299> example<00:20:47.299> for<00:20:50.630> example<00:20:51.630> if 00:20:52.159 --> 00:20:52.169 align:start position:0% I know that for example for example if 00:20:52.169 --> 00:20:57.590 align:start position:0% I know that for example for example if you<00:20:54.559> you<00:20:55.559> know<00:20:55.740> how<00:20:56.010> if<00:20:56.490> you're<00:20:56.700> like<00:20:56.970> let's 00:20:57.590 --> 00:20:57.600 align:start position:0% you you know how if you're like let's 00:20:57.600 --> 00:20:59.720 align:start position:0% you you know how if you're like let's say<00:20:57.809> you<00:20:57.870> sum<00:20:58.260> up<00:20:58.290> of<00:20:58.620> the<00:20:58.799> cost<00:20:59.070> of<00:20:59.340> all<00:20:59.580> the 00:20:59.720 --> 00:20:59.730 align:start position:0% say you sum up of the cost of all the 00:20:59.730 --> 00:21:02.419 align:start position:0% say you sum up of the cost of all the curve<00:20:59.970> I<00:21:00.299> know<00:21:00.870> it's<00:21:01.559> gonna<00:21:01.710> not<00:21:01.860> exceed<00:21:02.220> like 00:21:02.419 --> 00:21:02.429 align:start position:0% curve I know it's gonna not exceed like 00:21:02.429 --> 00:21:05.360 align:start position:0% curve I know it's gonna not exceed like it<00:21:02.730> to<00:21:02.970> this<00:21:03.179> value<00:21:03.929> because<00:21:04.530> it's<00:21:05.190> like 00:21:05.360 --> 00:21:05.370 align:start position:0% it to this value because it's like 00:21:05.370 --> 00:21:08.150 align:start position:0% it to this value because it's like the<00:21:06.210> maximum<00:21:06.570> code<00:21:07.080> of<00:21:07.679> codes 00:21:08.150 --> 00:21:08.160 align:start position:0% the maximum code of codes 00:21:08.160 --> 00:21:11.570 align:start position:0% the maximum code of codes constants<00:21:08.760> is<00:21:09.030> created<00:21:09.600> which<00:21:09.720> is<00:21:09.919> 42<00:21:10.919> K<00:21:11.250> and 00:21:11.570 --> 00:21:11.580 align:start position:0% constants is created which is 42 K and 00:21:11.580 --> 00:21:14.690 align:start position:0% constants is created which is 42 K and multiplied<00:21:12.390> by<00:21:12.419> the<00:21:12.690> Scout<00:21:13.140> size<00:21:13.410> it<00:21:13.919> still 00:21:14.690 --> 00:21:14.700 align:start position:0% multiplied by the Scout size it still 00:21:14.700 --> 00:21:17.750 align:start position:0% multiplied by the Scout size it still will<00:21:14.880> be<00:21:15.000> a<00:21:15.030> 32-bit<00:21:15.929> limit<00:21:16.290> so<00:21:17.010> things<00:21:17.580> like 00:21:17.750 --> 00:21:17.760 align:start position:0% will be a 32-bit limit so things like 00:21:17.760 --> 00:21:20.840 align:start position:0% will be a 32-bit limit so things like that<00:21:18.440> so<00:21:19.440> i<00:21:19.470> know<00:21:19.590> i<00:21:19.679> can<00:21:19.980> i<00:21:20.100> can<00:21:20.280> store<00:21:20.549> like 00:21:20.840 --> 00:21:20.850 align:start position:0% that so i know i can i can store like 00:21:20.850 --> 00:21:25.270 align:start position:0% that so i know i can i can store like this<00:21:21.059> information<00:21:22.040> within<00:21:23.040> a<00:21:23.120> 32-bit<00:21:24.120> limit 00:21:25.270 --> 00:21:25.280 align:start position:0% this information within a 32-bit limit 00:21:25.280 --> 00:21:29.090 align:start position:0% this information within a 32-bit limit that's<00:21:26.280> many<00:21:26.880> things<00:21:27.150> like<00:21:27.299> this<00:21:27.830> so<00:21:28.830> you<00:21:28.890> have 00:21:29.090 --> 00:21:29.100 align:start position:0% that's many things like this so you have 00:21:29.100 --> 00:21:33.350 align:start position:0% that's many things like this so you have at<00:21:29.190> least<00:21:30.890> I<00:21:31.890> also<00:21:32.190> can<00:21:32.520> actually<00:21:32.880> generate 00:21:33.350 --> 00:21:33.360 align:start position:0% at least I also can actually generate 00:21:33.360 --> 00:21:35.120 align:start position:0% at least I also can actually generate like<00:21:33.780> the<00:21:34.020> worst<00:21:34.260> cases 00:21:35.120 --> 00:21:35.130 align:start position:0% like the worst cases 00:21:35.130 --> 00:21:37.610 align:start position:0% like the worst cases businesses<00:21:35.820> in<00:21:36.059> Shekau<00:21:36.809> how<00:21:37.140> much<00:21:37.350> time 00:21:37.610 --> 00:21:37.620 align:start position:0% businesses in Shekau how much time 00:21:37.620 --> 00:21:39.799 align:start position:0% businesses in Shekau how much time elapsed<00:21:38.130> egg<00:21:38.370> so<00:21:38.700> like<00:21:38.880> this<00:21:39.120> is<00:21:39.299> some<00:21:39.480> kind<00:21:39.510> of 00:21:39.799 --> 00:21:39.809 align:start position:0% elapsed egg so like this is some kind of 00:21:39.809 --> 00:21:43.340 align:start position:0% elapsed egg so like this is some kind of security<00:21:40.679> precaution<00:21:41.520> like<00:21:42.270> yeah<00:21:42.960> in<00:21:43.260> the 00:21:43.340 --> 00:21:43.350 align:start position:0% security precaution like yeah in the 00:21:43.350 --> 00:21:47.380 align:start position:0% security precaution like yeah in the worst<00:21:43.620> case<00:21:43.980> and<00:21:44.610> it's<00:21:44.789> like<00:21:44.970> they're<00:21:45.210> the 00:21:47.380 --> 00:21:47.390 align:start position:0% worst case and it's like they're the 00:21:47.390 --> 00:23:13.880 align:start position:0% worst case and it's like they're the order<00:21:48.390> of<00:22:06.320> yeah<00:22:32.179> yeah<00:22:33.179> I<00:22:33.210> mean<00:23:12.200> I<00:23:13.200> mean<00:23:13.559> I<00:23:13.679> feel 00:23:13.880 --> 00:23:13.890 align:start position:0% order of yeah yeah I mean I mean I feel 00:23:13.890 --> 00:23:22.070 align:start position:0% order of yeah yeah I mean I mean I feel also<00:23:14.070> like<00:23:14.600> much<00:23:15.600> context<00:23:19.640> there's<00:23:20.640> no<00:23:21.080> saying 00:23:22.070 --> 00:23:22.080 align:start position:0% also like much context there's no saying 00:23:22.080 --> 00:23:26.630 align:start position:0% also like much context there's no saying no<00:23:22.320> use<00:23:22.740> contractors<00:23:23.490> lives<00:23:23.730> the<00:23:25.429> case<00:23:26.429> that 00:23:26.630 --> 00:23:26.640 align:start position:0% no use contractors lives the case that 00:23:26.640 --> 00:23:29.270 align:start position:0% no use contractors lives the case that represents<00:23:27.390> trying<00:23:28.350> to<00:23:28.500> make<00:23:28.650> contract<00:23:29.130> in 00:23:29.270 --> 00:23:29.280 align:start position:0% represents trying to make contract in 00:23:29.280 --> 00:23:33.400 align:start position:0% represents trying to make contract in too<00:23:29.400> much<00:23:29.640> or<00:23:30.000> that<00:23:30.270> you<00:23:30.390> should<00:23:30.570> be<00:23:30.600> motorized 00:23:33.400 --> 00:23:33.410 align:start position:0% 00:23:33.410 --> 00:23:36.190 align:start position:0% and<00:23:33.500> in<00:23:33.710> doing<00:23:33.890> place<00:23:34.840> so<00:23:35.840> it's<00:23:35.990> about 00:23:36.190 --> 00:23:36.200 align:start position:0% and in doing place so it's about 00:23:36.200 --> 00:23:38.890 align:start position:0% and in doing place so it's about complaint<00:23:36.710> or<00:23:36.890> resident<00:23:37.310> I<00:23:37.730> don't<00:23:38.600> think<00:23:38.780> it's 00:23:38.890 --> 00:23:38.900 align:start position:0% complaint or resident I don't think it's 00:23:38.900 --> 00:23:42.370 align:start position:0% complaint or resident I don't think it's I<00:23:39.500> think<00:23:39.530> it's<00:23:40.900> there<00:23:41.900> are<00:23:41.990> definitely 00:23:42.370 --> 00:23:42.380 align:start position:0% I think it's there are definitely 00:23:42.380 --> 00:23:45.630 align:start position:0% I think it's there are definitely contracts<00:23:42.890> that<00:23:43.040> product 00:23:45.630 --> 00:23:45.640 align:start position:0% 00:23:45.640 --> 00:23:47.070 align:start position:0% but<00:23:45.730> your<00:23:45.880> first<00:23:46.150> reaction<00:23:46.420> will<00:23:46.780> be<00:23:46.840> rather 00:23:47.070 --> 00:23:47.080 align:start position:0% but your first reaction will be rather 00:23:47.080 --> 00:23:50.100 align:start position:0% but your first reaction will be rather to<00:23:47.350> it<00:23:47.470> should<00:23:47.679> be<00:23:47.950> to<00:23:48.760> the<00:23:48.940> to<00:23:49.450> do<00:23:49.600> the<00:23:49.780> review 00:23:50.100 --> 00:23:50.110 align:start position:0% to it should be to the to do the review 00:23:50.110 --> 00:23:51.900 align:start position:0% to it should be to the to do the review of<00:23:50.140> your<00:23:50.320> college<00:23:50.679> and<00:23:50.830> say<00:23:51.040> how<00:23:51.250> am<00:23:51.549> i<00:23:51.640> try<00:23:51.850> the 00:23:51.900 --> 00:23:51.910 align:start position:0% of your college and say how am i try the 00:23:51.910 --> 00:23:53.700 align:start position:0% of your college and say how am i try the correct<00:23:52.179> way<00:23:52.330> too<00:23:52.390> much<00:23:52.630> stuff<00:23:52.870> as<00:23:53.110> maybe<00:23:53.350> or 00:23:53.700 --> 00:23:53.710 align:start position:0% correct way too much stuff as maybe or 00:23:53.710 --> 00:23:55.320 align:start position:0% correct way too much stuff as maybe or on<00:23:53.740> Changmin<00:23:54.340> is<00:23:54.429> it<00:23:54.610> something<00:23:54.820> to<00:23:55.000> take<00:23:55.179> off 00:23:55.320 --> 00:23:55.330 align:start position:0% on Changmin is it something to take off 00:23:55.330 --> 00:23:57.450 align:start position:0% on Changmin is it something to take off chains<00:23:55.660> and<00:23:55.960> stuff<00:23:56.049> I<00:23:56.260> didn't<00:23:56.500> walk<00:23:57.130> instead 00:23:57.450 --> 00:23:57.460 align:start position:0% chains and stuff I didn't walk instead 00:23:57.460 --> 00:23:59.640 align:start position:0% chains and stuff I didn't walk instead of<00:23:57.640> computing<00:23:58.120> and<00:23:58.270> storing<00:23:58.660> looks<00:23:59.320> like<00:23:59.470> that 00:23:59.640 --> 00:23:59.650 align:start position:0% of computing and storing looks like that 00:23:59.650 --> 00:24:01.830 align:start position:0% of computing and storing looks like that or<00:23:59.890> kind<00:24:00.580> of<00:24:00.640> modular<00:24:00.970> eyes<00:24:01.120> the<00:24:01.270> business<00:24:01.630> in 00:24:01.830 --> 00:24:01.840 align:start position:0% or kind of modular eyes the business in 00:24:01.840 --> 00:24:04.020 align:start position:0% or kind of modular eyes the business in case<00:24:02.110> the<00:24:02.320> TV<00:24:02.590> set<00:24:02.830> context<00:24:03.309> registers<00:24:03.790> was<00:24:04.000> a 00:24:04.020 --> 00:24:04.030 align:start position:0% case the TV set context registers was a 00:24:04.030 --> 00:24:05.669 align:start position:0% case the TV set context registers was a budget<00:24:04.360> ear<00:24:04.480> based<00:24:04.690> algorithm<00:24:05.260> is<00:24:05.380> an<00:24:05.530> ancient 00:24:05.669 --> 00:24:05.679 align:start position:0% budget ear based algorithm is an ancient 00:24:05.679 --> 00:24:07.380 align:start position:0% budget ear based algorithm is an ancient letters<00:24:05.980> of<00:24:06.190> the<00:24:06.280> civil<00:24:06.549> contract<00:24:07.030> without 00:24:07.380 --> 00:24:07.390 align:start position:0% letters of the civil contract without 00:24:07.390 --> 00:24:09.720 align:start position:0% letters of the civil contract without which<00:24:08.380> makes<00:24:08.650> it<00:24:08.770> more<00:24:08.860> flexible<00:24:08.980> and<00:24:09.429> also 00:24:09.720 --> 00:24:09.730 align:start position:0% which makes it more flexible and also 00:24:09.730 --> 00:24:19.530 align:start position:0% which makes it more flexible and also ensures 00:24:19.530 --> 00:24:19.540 align:start position:0% 00:24:19.540 --> 00:24:38.530 align:start position:0% [Music] 00:24:38.530 --> 00:24:38.540 align:start position:0% 00:24:38.540 --> 00:24:41.150 align:start position:0% but<00:24:39.540> I'm<00:24:39.690> talking<00:24:39.870> about<00:24:40.110> the<00:24:40.350> bucket<00:24:40.770> limit 00:24:41.150 --> 00:24:41.160 align:start position:0% but I'm talking about the bucket limit 00:24:41.160 --> 00:24:42.950 align:start position:0% but I'm talking about the bucket limit is<00:24:41.310> the<00:24:41.490> limiting<00:24:42.180> factor<00:24:42.570> for<00:24:42.600> the 00:24:42.950 --> 00:24:42.960 align:start position:0% is the limiting factor for the 00:24:42.960 --> 00:24:46.100 align:start position:0% is the limiting factor for the contrapositive<00:24:43.740> anyway<00:24:44.340> so<00:24:44.480> currently<00:24:45.480> when 00:24:46.100 --> 00:24:46.110 align:start position:0% contrapositive anyway so currently when 00:24:46.110 --> 00:24:48.880 align:start position:0% contrapositive anyway so currently when the<00:24:46.260> when<00:24:47.250> the<00:24:47.280> movie<00:24:47.640> was<00:24:47.700> in<00:24:48.030> host<00:24:48.240> and 00:24:48.880 --> 00:24:48.890 align:start position:0% the when the movie was in host and 00:24:48.890 --> 00:24:51.710 align:start position:0% the when the movie was in host and proximate<00:24:49.890> was<00:24:50.070> like<00:24:50.310> four<00:24:50.550> million<00:24:50.760> and<00:24:51.150> that 00:24:51.710 --> 00:24:51.720 align:start position:0% proximate was like four million and that 00:24:51.720 --> 00:24:54.080 align:start position:0% proximate was like four million and that was<00:24:51.780> the<00:24:52.200> mark<00:24:52.860> and<00:24:53.100> now<00:24:53.220> it's<00:24:53.400> at<00:24:53.610> 8<00:24:53.820> million 00:24:54.080 --> 00:24:54.090 align:start position:0% was the mark and now it's at 8 million 00:24:54.090 --> 00:24:57.880 align:start position:0% was the mark and now it's at 8 million 10<00:24:54.510> million<00:24:54.690> and<00:24:55.050> so<00:24:55.830> it<00:24:56.160> would<00:24:56.340> be<00:24:56.910> double<00:24:57.390> the 00:24:57.880 --> 00:24:57.890 align:start position:0% 10 million and so it would be double the 00:24:57.890 --> 00:25:00.530 align:start position:0% 10 million and so it would be double the Jebusites<00:24:58.890> that<00:24:59.400> they<00:24:59.610> in<00:25:00.060> have<00:25:00.210> to<00:25:00.330> guess 00:25:00.530 --> 00:25:00.540 align:start position:0% Jebusites that they in have to guess 00:25:00.540 --> 00:25:04.070 align:start position:0% Jebusites that they in have to guess from<00:25:01.910> the<00:25:02.910> contract<00:25:03.330> hasn't<00:25:03.480> changed 00:25:04.070 --> 00:25:04.080 align:start position:0% from the contract hasn't changed 00:25:04.080 --> 00:25:07.240 align:start position:0% from the contract hasn't changed so<00:25:04.440> they'd<00:25:05.340> still<00:25:05.610> be<00:25:05.640> trying<00:25:05.970> to<00:25:06.000> do 00:25:07.240 --> 00:25:07.250 align:start position:0% so they'd still be trying to do 00:25:07.250 --> 00:25:09.880 align:start position:0% so they'd still be trying to do yes<00:25:07.549> we<00:25:08.480> increased<00:25:08.870> against<00:25:09.200> one<00:25:09.590> that's 00:25:09.880 --> 00:25:09.890 align:start position:0% yes we increased against one that's 00:25:09.890 --> 00:25:15.399 align:start position:0% yes we increased against one that's right<00:25:10.090> increasing<00:25:13.510> as<00:25:14.510> much<00:25:14.720> of<00:25:14.929> arresting<00:25:15.289> it 00:25:15.399 --> 00:25:15.409 align:start position:0% right increasing as much of arresting it 00:25:15.409 --> 00:25:18.669 align:start position:0% right increasing as much of arresting it became<00:25:16.340> more<00:25:16.460> expensive<00:25:17.059> to<00:25:17.210> run<00:25:17.360> the<00:25:18.080> CPM<00:25:18.530> to 00:25:18.669 --> 00:25:18.679 align:start position:0% became more expensive to run the CPM to 00:25:18.679 --> 00:25:22.659 align:start position:0% became more expensive to run the CPM to inlining<00:25:19.429> the<00:25:20.030> back<00:25:20.210> end<00:25:20.830> part<00:25:21.830> of<00:25:21.919> the<00:25:22.039> cosmic 00:25:22.659 --> 00:25:22.669 align:start position:0% inlining the back end part of the cosmic 00:25:22.669 --> 00:25:25.659 align:start position:0% inlining the back end part of the cosmic separation<00:25:23.210> so<00:25:23.390> it<00:25:24.140> can<00:25:24.530> make<00:25:24.710> it<00:25:24.890> will<00:25:25.520> often 00:25:25.659 --> 00:25:25.669 align:start position:0% separation so it can make it will often 00:25:25.669 --> 00:25:27.950 align:start position:0% separation so it can make it will often make<00:25:25.940> it<00:25:26.120> worse<00:25:26.270> being<00:25:26.510> relatively 00:25:27.950 --> 00:25:27.960 align:start position:0% make it worse being relatively 00:25:27.960 --> 00:25:42.310 align:start position:0% make it worse being relatively [Music] 00:25:42.310 --> 00:25:42.320 align:start position:0% 00:25:42.320 --> 00:25:55.850 align:start position:0% this<00:25:43.320> kind<00:25:43.559> of<00:25:48.950> research<00:25:54.470> but<00:25:55.470> I<00:25:55.590> mean<00:25:55.740> very 00:25:55.850 --> 00:25:55.860 align:start position:0% this kind of research but I mean very 00:25:55.860 --> 00:25:57.560 align:start position:0% this kind of research but I mean very differently<00:25:56.279> about<00:25:56.340> just<00:25:56.880> having<00:25:57.029> some 00:25:57.560 --> 00:25:57.570 align:start position:0% differently about just having some 00:25:57.570 --> 00:26:21.350 align:start position:0% differently about just having some context<00:25:58.200> about<00:26:03.710> the<00:26:04.710> idea<00:26:05.460> that<00:26:20.179> safety<00:26:21.179> look 00:26:21.350 --> 00:26:21.360 align:start position:0% context about the idea that safety look 00:26:21.360 --> 00:26:34.970 align:start position:0% context about the idea that safety look at<00:26:21.480> the<00:26:28.490> so<00:26:29.490> so<00:26:30.179> I<00:26:30.659> still<00:26:31.169> like<00:26:31.320> that<00:26:31.350> idea<00:26:33.980> and 00:26:34.970 --> 00:26:34.980 align:start position:0% at the so so I still like that idea and 00:26:34.980 --> 00:26:38.600 align:start position:0% at the so so I still like that idea and I<00:26:35.730> think<00:26:36.389> what<00:26:36.870> I<00:26:37.169> bring<00:26:37.830> that<00:26:38.220> Nicholas<00:26:38.580> was 00:26:38.600 --> 00:26:38.610 align:start position:0% I think what I bring that Nicholas was 00:26:38.610 --> 00:26:40.820 align:start position:0% I think what I bring that Nicholas was actually<00:26:39.029> the<00:26:39.149> fact<00:26:39.360> that<00:26:39.480> they<00:26:40.200> business 00:26:40.820 --> 00:26:40.830 align:start position:0% actually the fact that they business 00:26:40.830 --> 00:26:43.759 align:start position:0% actually the fact that they business static<00:26:41.460> cost 00:26:43.759 --> 00:26:43.769 align:start position:0% static cost 00:26:43.769 --> 00:26:46.230 align:start position:0% static cost and<00:26:44.769> it's<00:26:44.980> like<00:26:45.190> same<00:26:45.429> amount<00:26:45.639> of<00:26:45.669> gas<00:26:45.880> this 00:26:46.230 --> 00:26:46.240 align:start position:0% and it's like same amount of gas this 00:26:46.240 --> 00:26:48.779 align:start position:0% and it's like same amount of gas this car<00:26:46.450> time<00:26:46.659> and<00:26:47.649> it<00:26:48.190> doesn't<00:26:48.460> really<00:26:48.580> reflect 00:26:48.779 --> 00:26:48.789 align:start position:0% car time and it doesn't really reflect 00:26:48.789 --> 00:26:52.200 align:start position:0% car time and it doesn't really reflect what<00:26:49.210> you<00:26:49.450> do<00:26:49.600> we<00:26:49.809> actually<00:26:50.080> running<00:26:50.409> and<00:26:51.279> so 00:26:52.200 --> 00:26:52.210 align:start position:0% what you do we actually running and so 00:26:52.210 --> 00:26:53.789 align:start position:0% what you do we actually running and so what<00:26:52.419> I<00:26:52.600> would<00:26:52.659> like<00:26:53.049> to<00:26:53.320> see<00:26:53.500> is<00:26:53.590> something 00:26:53.789 --> 00:26:53.799 align:start position:0% what I would like to see is something 00:26:53.799 --> 00:26:55.470 align:start position:0% what I would like to see is something more<00:26:54.070> like<00:26:54.279> what<00:26:54.309> the<00:26:54.580> operating<00:26:55.090> system<00:26:55.450> does 00:26:55.470 --> 00:26:55.480 align:start position:0% more like what the operating system does 00:26:55.480 --> 00:26:58.740 align:start position:0% more like what the operating system does it<00:26:56.169> does<00:26:56.350> the<00:26:56.500> computation<00:26:56.769> of<00:26:57.159> 30<00:26:57.429> your<00:26:58.269> I 00:26:58.740 --> 00:26:58.750 align:start position:0% it does the computation of 30 your I 00:26:58.750 --> 00:27:01.649 align:start position:0% it does the computation of 30 your I don't<00:26:59.409> know<00:26:59.500> your<00:26:59.740> your<00:27:00.340> index<00:27:00.850> library<00:27:01.330> from 00:27:01.649 --> 00:27:01.659 align:start position:0% don't know your your index library from 00:27:01.659 --> 00:27:03.930 align:start position:0% don't know your your index library from Thirsk<00:27:02.019> once<00:27:02.799> it's<00:27:02.950> a<00:27:03.039> memory<00:27:03.370> it<00:27:03.610> can<00:27:03.639> just 00:27:03.930 --> 00:27:03.940 align:start position:0% Thirsk once it's a memory it can just 00:27:03.940 --> 00:27:05.700 align:start position:0% Thirsk once it's a memory it can just recall<00:27:04.389> that<00:27:04.450> and<00:27:04.750> to<00:27:04.840> get<00:27:04.960> that<00:27:05.139> advantage<00:27:05.260> so 00:27:05.700 --> 00:27:05.710 align:start position:0% recall that and to get that advantage so 00:27:05.710 --> 00:27:08.250 align:start position:0% recall that and to get that advantage so like<00:27:05.919> and<00:27:06.399> water<00:27:06.639> in<00:27:07.389> the<00:27:07.600> transaction<00:27:08.139> the 00:27:08.250 --> 00:27:08.260 align:start position:0% like and water in the transaction the 00:27:08.260 --> 00:27:09.750 align:start position:0% like and water in the transaction the first<00:27:08.500> floor<00:27:08.710> was<00:27:08.830> priced<00:27:09.130> at<00:27:09.279> something<00:27:09.669> and 00:27:09.750 --> 00:27:09.760 align:start position:0% first floor was priced at something and 00:27:09.760 --> 00:27:11.250 align:start position:0% first floor was priced at something and it<00:27:09.880> may<00:27:09.970> be<00:27:10.029> to<00:27:10.330> somebody<00:27:10.539> else<00:27:10.840> pair<00:27:11.080> as 00:27:11.250 --> 00:27:11.260 align:start position:0% it may be to somebody else pair as 00:27:11.260 --> 00:27:18.720 align:start position:0% it may be to somebody else pair as European<00:27:15.690> philosophers<00:27:17.250> and<00:27:18.250> I<00:27:18.399> think<00:27:18.639> it 00:27:18.720 --> 00:27:18.730 align:start position:0% European philosophers and I think it 00:27:18.730 --> 00:27:21.029 align:start position:0% European philosophers and I think it makes<00:27:19.090> sense<00:27:19.330> for<00:27:19.570> the<00:27:19.779> same<00:27:19.990> reasons<00:27:20.409> the 00:27:21.029 --> 00:27:21.039 align:start position:0% makes sense for the same reasons the 00:27:21.039 --> 00:27:25.370 align:start position:0% makes sense for the same reasons the other<00:27:21.070> option<00:27:21.639> is<00:27:21.669> that<00:27:21.880> we<00:27:22.120> do<00:27:22.330> system<00:27:23.169> to 00:27:25.370 --> 00:27:25.380 align:start position:0% other option is that we do system to 00:27:25.380 --> 00:27:28.990 align:start position:0% other option is that we do system to propose<00:27:26.380> well<00:27:27.070> used<00:27:27.309> contractors 00:27:28.990 --> 00:27:29.000 align:start position:0% propose well used contractors 00:27:29.000 --> 00:27:32.150 align:start position:0% propose well used contractors Milton's<00:27:30.000> didn't<00:27:30.900> say<00:27:31.140> I<00:27:31.530> mean<00:27:31.890> my<00:27:32.040> own 00:27:32.150 --> 00:27:32.160 align:start position:0% Milton's didn't say I mean my own 00:27:32.160 --> 00:27:36.770 align:start position:0% Milton's didn't say I mean my own personal<00:27:33.920> Viennese<00:27:34.920> registry<00:27:35.550> yeah<00:27:35.880> is<00:27:36.570> now<00:27:36.750> a 00:27:36.770 --> 00:27:36.780 align:start position:0% personal Viennese registry yeah is now a 00:27:36.780 --> 00:27:38.540 align:start position:0% personal Viennese registry yeah is now a built-in<00:27:37.170> and<00:27:37.530> it<00:27:37.590> cause<00:27:37.800> it's<00:27:38.070> fifty<00:27:38.370> years 00:27:38.540 --> 00:27:38.550 align:start position:0% built-in and it cause it's fifty years 00:27:38.550 --> 00:27:39.740 align:start position:0% built-in and it cause it's fifty years to<00:27:38.700> go<00:27:38.820> let's<00:27:39.030> go<00:27:39.150> see<00:27:39.330> a<00:27:39.360> doctor 00:27:39.740 --> 00:27:39.750 align:start position:0% to go let's go see a doctor 00:27:39.750 --> 00:27:43.670 align:start position:0% to go let's go see a doctor because<00:27:40.050> you<00:27:40.140> expect<00:27:41.270> American<00:27:42.270> clients<00:27:42.720> to 00:27:43.670 --> 00:27:43.680 align:start position:0% because you expect American clients to 00:27:43.680 --> 00:27:48.500 align:start position:0% because you expect American clients to feel<00:27:44.220> safe<00:27:44.460> just<00:27:46.250> like<00:27:47.250> everybody<00:27:48.030> uses<00:27:48.360> this 00:27:48.500 --> 00:27:48.510 align:start position:0% feel safe just like everybody uses this 00:27:48.510 --> 00:27:50.450 align:start position:0% feel safe just like everybody uses this yeah<00:27:48.780> it<00:27:49.170> almost<00:27:49.440> cheap<00:27:49.710> enough<00:27:49.980> you<00:27:50.220> could 00:27:50.450 --> 00:27:50.460 align:start position:0% yeah it almost cheap enough you could 00:27:50.460 --> 00:27:59.750 align:start position:0% yeah it almost cheap enough you could get<00:27:51.060> up<00:27:51.770> recompile<00:27:52.770> it<00:27:58.310> suggested<00:27:59.310> some<00:27:59.520> kind 00:27:59.750 --> 00:27:59.760 align:start position:0% get up recompile it suggested some kind 00:27:59.760 --> 00:28:09.170 align:start position:0% get up recompile it suggested some kind of<00:28:01.490> advanced<00:28:02.490> caching<00:28:07.520> in<00:28:08.520> the<00:28:08.790> IPD 00:28:09.170 --> 00:28:09.180 align:start position:0% of advanced caching in the IPD 00:28:09.180 --> 00:28:11.840 align:start position:0% of advanced caching in the IPD grandmother's<00:28:09.840> though<00:28:10.080> this<00:28:11.040> contractor<00:28:11.700> was 00:28:11.840 --> 00:28:11.850 align:start position:0% grandmother's though this contractor was 00:28:11.850 --> 00:28:13.360 align:start position:0% grandmother's though this contractor was addresses<00:28:12.450> happens 00:28:13.360 --> 00:28:13.370 align:start position:0% addresses happens 00:28:13.370 --> 00:28:16.830 align:start position:0% addresses happens contract<00:28:13.940> especial<00:28:14.570> St<00:28:14.930> Trinian's 00:28:16.830 --> 00:28:16.840 align:start position:0% contract especial St Trinian's 00:28:16.840 --> 00:28:19.000 align:start position:0% contract especial St Trinian's individual<00:28:17.840> presentations<00:28:18.440> can<00:28:18.590> choose<00:28:18.830> to 00:28:19.000 --> 00:28:19.010 align:start position:0% individual presentations can choose to 00:28:19.010 --> 00:28:22.430 align:start position:0% individual presentations can choose to really<00:28:19.430> badly<00:28:19.809> or<00:28:20.809> advisor<00:28:21.110> complain 00:28:22.430 --> 00:28:22.440 align:start position:0% really badly or advisor complain 00:28:22.440 --> 00:28:25.020 align:start position:0% really badly or advisor complain Lotus<00:28:23.220> has<00:28:23.370> been<00:28:23.580> very<00:28:23.730> evident 00:28:25.020 --> 00:28:25.030 align:start position:0% Lotus has been very evident 00:28:25.030 --> 00:28:44.880 align:start position:0% Lotus has been very evident it's<00:28:26.030> kind<00:28:26.330> of<00:28:26.390> the<00:28:26.540> wasn't<00:28:27.020> a<00:28:37.990> frog<00:28:42.040> but 00:28:44.880 --> 00:28:44.890 align:start position:0% it's kind of the wasn't a frog but 00:28:44.890 --> 00:29:23.610 align:start position:0% it's kind of the wasn't a frog but that's<00:28:45.890> actually<00:29:21.280> Martin<00:29:22.280> Martin's<00:29:23.000> Wanda<00:29:23.330> I 00:29:23.610 --> 00:29:23.620 align:start position:0% that's actually Martin Martin's Wanda I 00:29:23.620 --> 00:29:28.990 align:start position:0% that's actually Martin Martin's Wanda I work<00:29:24.620> with<00:29:24.950> the<00:29:25.130> client<00:29:25.850> and<00:29:26.060> secured<00:29:28.000> their 00:29:28.990 --> 00:29:29.000 align:start position:0% work with the client and secured their 00:29:29.000 --> 00:29:32.140 align:start position:0% work with the client and secured their foundation<00:29:29.750> but<00:29:29.960> for<00:29:30.590> the<00:29:30.880> infrastructure<00:29:31.880> in 00:29:32.140 --> 00:29:32.150 align:start position:0% foundation but for the infrastructure in 00:29:32.150 --> 00:29:37.630 align:start position:0% foundation but for the infrastructure in the<00:29:32.180> EVM<00:29:32.770> and<00:29:33.770> I<00:29:33.860> was<00:29:33.980> up<00:29:34.130> another<00:29:34.400> and<00:29:34.880> also<00:29:36.640> we 00:29:37.630 --> 00:29:37.640 align:start position:0% the EVM and I was up another and also we 00:29:37.640 --> 00:29:42.040 align:start position:0% the EVM and I was up another and also we were<00:29:37.820> just<00:29:38.090> discussing<00:29:39.250> pricing<00:29:40.250> and<00:29:41.050> pricing 00:29:42.040 --> 00:29:42.050 align:start position:0% were just discussing pricing and pricing 00:29:42.050 --> 00:29:44.320 align:start position:0% were just discussing pricing and pricing in<00:29:42.320> general<00:29:42.620> and<00:29:43.160> what<00:29:43.430> we<00:29:43.550> ended<00:29:43.760> up<00:29:43.880> with<00:29:44.120> I 00:29:44.320 --> 00:29:44.330 align:start position:0% in general and what we ended up with I 00:29:44.330 --> 00:29:48.610 align:start position:0% in general and what we ended up with I think<00:29:44.720> Nick<00:29:45.230> proposing<00:29:45.890> that<00:29:46.480> so<00:29:47.620> regularly 00:29:48.610 --> 00:29:48.620 align:start position:0% think Nick proposing that so regularly 00:29:48.620 --> 00:29:54.400 align:start position:0% think Nick proposing that so regularly used<00:29:48.860> contracts<00:29:49.550> or<00:29:49.670> libraries<00:29:50.260> with 00:29:54.400 --> 00:29:54.410 align:start position:0% 00:29:54.410 --> 00:29:57.890 align:start position:0% right<00:29:55.410> so<00:29:56.130> how<00:29:56.370> would<00:29:56.430> you<00:29:56.670> so<00:29:57.420> I<00:29:57.660> have<00:29:57.870> a 00:29:57.890 --> 00:29:57.900 align:start position:0% right so how would you so I have a 00:29:57.900 --> 00:30:01.370 align:start position:0% right so how would you so I have a problem<00:29:58.350> with<00:29:59.540> there's<00:30:00.540> a<00:30:00.630> general<00:30:01.020> thinking 00:30:01.370 --> 00:30:01.380 align:start position:0% problem with there's a general thinking 00:30:01.380 --> 00:30:03.950 align:start position:0% problem with there's a general thinking sometimes<00:30:01.860> that<00:30:02.690> caching 00:30:03.950 --> 00:30:03.960 align:start position:0% sometimes that caching 00:30:03.960 --> 00:30:06.680 align:start position:0% sometimes that caching clients<00:30:04.950> have<00:30:05.100> caches<00:30:05.430> so<00:30:05.940> we<00:30:06.180> should<00:30:06.420> make 00:30:06.680 --> 00:30:06.690 align:start position:0% clients have caches so we should make 00:30:06.690 --> 00:30:09.490 align:start position:0% clients have caches so we should make the<00:30:07.110> things<00:30:07.440> memory<00:30:07.920> in<00:30:07.980> the<00:30:08.220> caches<00:30:08.730> cheaper 00:30:09.490 --> 00:30:09.500 align:start position:0% the things memory in the caches cheaper 00:30:09.500 --> 00:30:12.710 align:start position:0% the things memory in the caches cheaper and<00:30:10.500> my<00:30:10.710> problem<00:30:11.190> with<00:30:11.340> that<00:30:11.370> is<00:30:11.730> that<00:30:11.760> caches 00:30:12.710 --> 00:30:12.720 align:start position:0% and my problem with that is that caches 00:30:12.720 --> 00:30:16.040 align:start position:0% and my problem with that is that caches allow<00:30:13.170> the<00:30:13.590> level<00:30:13.980> of<00:30:14.100> freedom<00:30:14.600> to<00:30:15.600> have 00:30:16.040 --> 00:30:16.050 align:start position:0% allow the level of freedom to have 00:30:16.050 --> 00:30:18.140 align:start position:0% allow the level of freedom to have whatever<00:30:16.380> cash<00:30:16.830> eviction<00:30:17.340> policy<00:30:17.820> you<00:30:17.940> want 00:30:18.140 --> 00:30:18.150 align:start position:0% whatever cash eviction policy you want 00:30:18.150 --> 00:30:20.720 align:start position:0% whatever cash eviction policy you want it<00:30:18.540> can<00:30:18.690> be<00:30:18.840> least<00:30:19.440> frequently<00:30:20.010> used<00:30:20.280> lost 00:30:20.720 --> 00:30:20.730 align:start position:0% it can be least frequently used lost 00:30:20.730 --> 00:30:23.360 align:start position:0% it can be least frequently used lost recently<00:30:21.030> used<00:30:21.480> caches<00:30:22.110> and<00:30:22.320> if<00:30:22.980> you<00:30:23.130> have<00:30:23.340> a 00:30:23.360 --> 00:30:23.370 align:start position:0% recently used caches and if you have a 00:30:23.370 --> 00:30:25.400 align:start position:0% recently used caches and if you have a big<00:30:23.640> machine<00:30:23.820> you<00:30:24.180> have<00:30:24.420> a<00:30:24.450> large<00:30:24.750> cache<00:30:25.080> in<00:30:25.290> if 00:30:25.400 --> 00:30:25.410 align:start position:0% big machine you have a large cache in if 00:30:25.410 --> 00:30:26.810 align:start position:0% big machine you have a large cache in if you're<00:30:25.590> running<00:30:25.800> it<00:30:25.890> on<00:30:26.040> a<00:30:26.100> Raspberry<00:30:26.610> Pi<00:30:26.640> a 00:30:26.810 --> 00:30:26.820 align:start position:0% you're running it on a Raspberry Pi a 00:30:26.820 --> 00:30:30.320 align:start position:0% you're running it on a Raspberry Pi a very<00:30:27.240> small<00:30:27.540> cache<00:30:27.930> it<00:30:28.650> will<00:30:28.860> be<00:30:28.950> slower<00:30:29.330> but 00:30:30.320 --> 00:30:30.330 align:start position:0% very small cache it will be slower but 00:30:30.330 --> 00:30:34.550 align:start position:0% very small cache it will be slower but if<00:30:30.630> we<00:30:31.050> like<00:30:31.920> say<00:30:32.610> well<00:30:33.510> the<00:30:33.870> cache<00:30:34.110> should<00:30:34.380> be 00:30:34.550 --> 00:30:34.560 align:start position:0% if we like say well the cache should be 00:30:34.560 --> 00:30:37.130 align:start position:0% if we like say well the cache should be this<00:30:34.860> and<00:30:35.280> this<00:30:35.910> should<00:30:35.970> be<00:30:36.180> cheaper<00:30:36.690> than<00:30:36.720> we 00:30:37.130 --> 00:30:37.140 align:start position:0% this and this should be cheaper than we 00:30:37.140 --> 00:30:39.950 align:start position:0% this and this should be cheaper than we all<00:30:37.290> of<00:30:37.350> a<00:30:37.380> sudden<00:30:37.820> encode<00:30:38.820> in<00:30:39.240> cash 00:30:39.950 --> 00:30:39.960 align:start position:0% all of a sudden encode in cash 00:30:39.960 --> 00:30:42.470 align:start position:0% all of a sudden encode in cash eviction<00:30:40.470> policy<00:30:41.220> into<00:30:41.520> a<00:30:41.550> consensus<00:30:42.060> engine 00:30:42.470 --> 00:30:42.480 align:start position:0% eviction policy into a consensus engine 00:30:42.480 --> 00:30:44.690 align:start position:0% eviction policy into a consensus engine and<00:30:43.020> we<00:30:43.200> hope<00:30:43.500> fast<00:30:43.920> slice<00:30:44.280> into<00:30:44.610> the 00:30:44.690 --> 00:30:44.700 align:start position:0% and we hope fast slice into the 00:30:44.700 --> 00:30:47.120 align:start position:0% and we hope fast slice into the consensus<00:30:45.300> engine<00:30:45.630> and<00:30:46.140> we<00:30:46.230> need<00:30:46.380> to<00:30:46.680> make 00:30:47.120 --> 00:30:47.130 align:start position:0% consensus engine and we need to make 00:30:47.130 --> 00:30:50.810 align:start position:0% consensus engine and we need to make sure<00:30:47.460> that<00:30:48.020> if<00:30:49.020> something<00:30:49.770> is<00:30:49.980> put<00:30:50.340> into<00:30:50.670> this 00:30:50.810 --> 00:30:50.820 align:start position:0% sure that if something is put into this 00:30:50.820 --> 00:30:54.050 align:start position:0% sure that if something is put into this cache<00:30:51.510> and<00:30:52.080> it's<00:30:52.680> been<00:30:53.070> a<00:30:53.100> revert<00:30:53.580> that<00:30:53.850> we 00:30:54.050 --> 00:30:54.060 align:start position:0% cache and it's been a revert that we 00:30:54.060 --> 00:30:55.730 align:start position:0% cache and it's been a revert that we need<00:30:54.360> to<00:30:54.480> clean<00:30:54.720> it<00:30:54.750> up<00:30:55.020> from<00:30:55.320> this<00:30:55.500> cache 00:30:55.730 --> 00:30:55.740 align:start position:0% need to clean it up from this cache 00:30:55.740 --> 00:30:58.010 align:start position:0% need to clean it up from this cache again<00:30:56.130> so<00:30:56.400> it's<00:30:56.550> not<00:30:56.730> sitting<00:30:57.240> around<00:30:57.480> we<00:30:57.990> need 00:30:58.010 --> 00:30:58.020 align:start position:0% again so it's not sitting around we need 00:30:58.020 --> 00:31:00.530 align:start position:0% again so it's not sitting around we need to<00:30:58.290> have<00:30:58.860> a<00:30:58.890> journal<00:30:59.430> covering<00:30:59.940> this<00:31:00.120> cache 00:31:00.530 --> 00:31:00.540 align:start position:0% to have a journal covering this cache 00:31:00.540 --> 00:31:03.260 align:start position:0% to have a journal covering this cache and<00:31:01.290> basically<00:31:01.620> it's<00:31:01.920> no<00:31:02.130> longer<00:31:02.430> cached<00:31:02.940> but 00:31:03.260 --> 00:31:03.270 align:start position:0% and basically it's no longer cached but 00:31:03.270 --> 00:31:06.070 align:start position:0% and basically it's no longer cached but we've<00:31:03.450> added<00:31:03.720> the<00:31:03.990> new<00:31:04.170> consensus<00:31:04.860> structure 00:31:06.070 --> 00:31:06.080 align:start position:0% we've added the new consensus structure 00:31:06.080 --> 00:31:10.010 align:start position:0% we've added the new consensus structure with<00:31:07.080> very<00:31:07.820> strict<00:31:08.820> rules<00:31:09.120> on<00:31:09.420> what<00:31:09.720> needs<00:31:09.960> to 00:31:10.010 --> 00:31:10.020 align:start position:0% with very strict rules on what needs to 00:31:10.020 --> 00:31:13.840 align:start position:0% with very strict rules on what needs to be<00:31:10.200> in<00:31:10.260> the<00:31:10.380> must<00:31:10.560> means<00:31:10.980> not<00:31:11.370> being<00:31:11.670> there<00:31:11.880> and 00:31:13.840 --> 00:31:13.850 align:start position:0% be in the must means not being there and 00:31:13.850 --> 00:31:17.540 align:start position:0% be in the must means not being there and yeah<00:31:14.850> and<00:31:15.210> it's<00:31:15.420> room<00:31:15.630> so<00:31:16.290> the<00:31:16.590> the<00:31:16.890> old<00:31:17.160> cache 00:31:17.540 --> 00:31:17.550 align:start position:0% yeah and it's room so the the old cache 00:31:17.550 --> 00:31:20.090 align:start position:0% yeah and it's room so the the old cache has<00:31:17.880> become<00:31:18.390> just<00:31:19.290> another<00:31:19.530> consensus 00:31:20.090 --> 00:31:20.100 align:start position:0% has become just another consensus 00:31:20.100 --> 00:31:22.160 align:start position:0% has become just another consensus structure<00:31:20.550> which<00:31:20.850> doesn't<00:31:21.360> help 00:31:22.160 --> 00:31:22.170 align:start position:0% structure which doesn't help 00:31:22.170 --> 00:31:25.010 align:start position:0% structure which doesn't help make<00:31:22.380> it<00:31:22.500> more<00:31:22.650> complicated<00:31:23.420> so<00:31:24.420> the<00:31:24.690> question 00:31:25.010 --> 00:31:25.020 align:start position:0% make it more complicated so the question 00:31:25.020 --> 00:31:27.410 align:start position:0% make it more complicated so the question is<00:31:25.140> if<00:31:25.560> we<00:31:25.620> want<00:31:25.890> to<00:31:25.950> make<00:31:26.040> it<00:31:26.160> cheaper<00:31:26.580> I<00:31:26.790> don't 00:31:27.410 --> 00:31:27.420 align:start position:0% is if we want to make it cheaper I don't 00:31:27.420 --> 00:31:30.650 align:start position:0% is if we want to make it cheaper I don't think<00:31:27.720> we<00:31:27.900> should<00:31:27.930> have<00:31:28.170> like<00:31:29.660> anything 00:31:30.650 --> 00:31:30.660 align:start position:0% think we should have like anything 00:31:30.660 --> 00:31:32.840 align:start position:0% think we should have like anything except<00:31:31.050> in<00:31:31.170> the<00:31:31.290> last<00:31:31.410> town<00:31:31.740> solid<00:31:32.160> you<00:31:32.430> need 00:31:32.840 --> 00:31:32.850 align:start position:0% except in the last town solid you need 00:31:32.850 --> 00:31:35.120 align:start position:0% except in the last town solid you need to<00:31:32.910> be<00:31:33.000> very<00:31:33.210> clear<00:31:33.420> about<00:31:33.540> what<00:31:34.140> should<00:31:34.740> cheer 00:31:35.120 --> 00:31:35.130 align:start position:0% to be very clear about what should cheer 00:31:35.130 --> 00:31:37.700 align:start position:0% to be very clear about what should cheer and<00:31:35.430> why<00:31:35.640> and<00:31:36.270> what<00:31:36.870> kind<00:31:37.110> of<00:31:37.170> data<00:31:37.320> structure 00:31:37.700 --> 00:31:37.710 align:start position:0% and why and what kind of data structure 00:31:37.710 --> 00:31:42.710 align:start position:0% and why and what kind of data structure -<00:31:38.060> anything<00:31:39.060> -<00:31:39.420> I<00:31:40.550> agree<00:31:41.580> and<00:31:41.790> I'm<00:31:41.910> actually 00:31:42.710 --> 00:31:42.720 align:start position:0% - anything - I agree and I'm actually 00:31:42.720 --> 00:31:50.410 align:start position:0% - anything - I agree and I'm actually against<00:31:43.290> caches<00:31:47.000> very<00:31:48.000> easily<00:31:48.380> attacked<00:31:49.380> by 00:31:50.410 --> 00:31:50.420 align:start position:0% against caches very easily attacked by 00:31:50.420 --> 00:31:58.280 align:start position:0% against caches very easily attacked by the<00:31:52.160> eventually<00:31:53.160> we<00:31:54.090> saw<00:31:54.300> the<00:31:56.870> need<00:31:57.870> to<00:31:58.020> do<00:31:58.140> is 00:31:58.280 --> 00:31:58.290 align:start position:0% the eventually we saw the need to do is 00:31:58.290 --> 00:31:59.990 align:start position:0% the eventually we saw the need to do is make<00:31:58.470> sure<00:31:58.500> that<00:31:58.740> he<00:31:59.010> realizes<00:31:59.370> that 00:31:59.990 --> 00:32:00.000 align:start position:0% make sure that he realizes that 00:32:00.000 --> 00:32:01.850 align:start position:0% make sure that he realizes that application<00:32:00.720> so<00:32:00.810> they<00:32:00.960> think<00:32:01.020> would<00:32:01.530> when<00:32:01.770> you 00:32:01.850 --> 00:32:01.860 align:start position:0% application so they think would when you 00:32:01.860 --> 00:32:03.650 align:start position:0% application so they think would when you don't<00:32:02.040> really<00:32:02.340> need<00:32:02.640> them<00:32:02.880> and<00:32:03.090> they<00:32:03.240> fail 00:32:03.650 --> 00:32:03.660 align:start position:0% don't really need them and they fail 00:32:03.660 --> 00:32:05.720 align:start position:0% don't really need them and they fail when<00:32:03.990> you<00:32:04.020> need<00:32:04.230> it<00:32:04.440> most<00:32:04.470> and<00:32:04.980> you<00:32:05.550> always 00:32:05.720 --> 00:32:05.730 align:start position:0% when you need it most and you always 00:32:05.730 --> 00:32:07.340 align:start position:0% when you need it most and you always have<00:32:06.030> to<00:32:06.060> assume<00:32:06.360> the<00:32:06.540> worst<00:32:06.570> case<00:32:06.840> that 00:32:07.340 --> 00:32:07.350 align:start position:0% have to assume the worst case that 00:32:07.350 --> 00:32:09.350 align:start position:0% have to assume the worst case that everything<00:32:07.860> is<00:32:08.160> a<00:32:08.190> certification<00:32:08.580> therefore 00:32:09.350 --> 00:32:09.360 align:start position:0% everything is a certification therefore 00:32:09.360 --> 00:32:10.970 align:start position:0% everything is a certification therefore you<00:32:09.540> can't<00:32:09.810> actually<00:32:10.200> optimize<00:32:10.590> your<00:32:10.770> stuff 00:32:10.970 --> 00:32:10.980 align:start position:0% you can't actually optimize your stuff 00:32:10.980 --> 00:32:13.070 align:start position:0% you can't actually optimize your stuff further<00:32:11.250> at<00:32:11.610> least<00:32:11.790> you<00:32:11.940> can<00:32:12.090> do<00:32:12.240> this<00:32:12.450> when 00:32:13.070 --> 00:32:13.080 align:start position:0% further at least you can do this when 00:32:13.080 --> 00:32:14.450 align:start position:0% further at least you can do this when times<00:32:13.380> are<00:32:13.530> good<00:32:13.590> your<00:32:13.860> sink<00:32:14.100> is<00:32:14.220> slightly 00:32:14.450 --> 00:32:14.460 align:start position:0% times are good your sink is slightly 00:32:14.460 --> 00:32:15.920 align:start position:0% times are good your sink is slightly faster<00:32:14.760> still<00:32:15.000> if<00:32:15.120> you're<00:32:15.240> catching<00:32:15.390> out<00:32:15.690> or 00:32:15.920 --> 00:32:15.930 align:start position:0% faster still if you're catching out or 00:32:15.930 --> 00:32:19.250 align:start position:0% faster still if you're catching out or maybe<00:32:16.080> a<00:32:16.170> lot<00:32:16.320> faster<00:32:17.750> what<00:32:18.750> I<00:32:18.780> was<00:32:18.990> proposing 00:32:19.250 --> 00:32:19.260 align:start position:0% maybe a lot faster what I was proposing 00:32:19.260 --> 00:32:20.870 align:start position:0% maybe a lot faster what I was proposing is<00:32:19.590> is<00:32:19.710> one<00:32:19.920> of<00:32:20.010> two<00:32:20.130> things<00:32:20.400> one<00:32:20.670> is 00:32:20.870 --> 00:32:20.880 align:start position:0% is is one of two things one is 00:32:20.880 --> 00:32:23.190 align:start position:0% is is one of two things one is effectively<00:32:21.570> extinction<00:32:22.230> and<00:32:22.320> it<00:32:22.500> gets 00:32:23.190 --> 00:32:23.200 align:start position:0% effectively extinction and it gets 00:32:23.200 --> 00:32:32.730 align:start position:0% effectively extinction and it gets to<00:32:23.559> apply<00:32:23.830> to<00:32:24.600> corporations<00:32:31.620> the<00:32:32.620> other 00:32:32.730 --> 00:32:32.740 align:start position:0% to apply to corporations the other 00:32:32.740 --> 00:32:35.100 align:start position:0% to apply to corporations the other option<00:32:33.190> is<00:32:33.279> a<00:32:33.340> way<00:32:33.580> for<00:32:34.029> the<00:32:34.240> idea<00:32:34.570> is<00:32:34.630> to<00:32:34.899> say 00:32:35.100 --> 00:32:35.110 align:start position:0% option is a way for the idea is to say 00:32:35.110 --> 00:32:38.220 align:start position:0% option is a way for the idea is to say the<00:32:35.889> contractors<00:32:36.460> by<00:32:36.610> previous<00:32:37.029> address<00:32:37.960> why 00:32:38.220 --> 00:32:38.230 align:start position:0% the contractors by previous address why 00:32:38.230 --> 00:32:40.620 align:start position:0% the contractors by previous address why it<00:32:39.070> is<00:32:39.220> considered<00:32:39.399> a<00:32:39.789> public<00:32:39.970> road<00:32:40.330> in<00:32:40.480> this 00:32:40.620 --> 00:32:40.630 align:start position:0% it is considered a public road in this 00:32:40.630 --> 00:32:42.210 align:start position:0% it is considered a public road in this roost<00:32:40.870> regularly<00:32:41.350> because<00:32:41.529> of<00:32:41.830> the<00:32:41.889> science 00:32:42.210 --> 00:32:42.220 align:start position:0% roost regularly because of the science 00:32:42.220 --> 00:32:43.980 align:start position:0% roost regularly because of the science and<00:32:42.340> math<00:32:42.639> coding<00:32:42.970> or<00:32:43.090> something<00:32:43.480> and 00:32:43.980 --> 00:32:43.990 align:start position:0% and math coding or something and 00:32:43.990 --> 00:32:45.810 align:start position:0% and math coding or something and executing<00:32:44.649> the<00:32:44.980> cool<00:32:45.159> off<00:32:45.309> code<00:32:45.549> to<00:32:45.700> this 00:32:45.810 --> 00:32:45.820 align:start position:0% executing the cool off code to this 00:32:45.820 --> 00:32:47.730 align:start position:0% executing the cool off code to this world<00:32:46.120> across<00:32:46.299> 20<00:32:46.659> guests<00:32:46.990> because<00:32:47.289> we<00:32:47.320> expect 00:32:47.730 --> 00:32:47.740 align:start position:0% world across 20 guests because we expect 00:32:47.740 --> 00:32:49.350 align:start position:0% world across 20 guests because we expect every<00:32:47.980> client<00:32:48.340> emergent<00:32:48.820> to<00:32:48.880> the<00:32:49.000> American 00:32:49.350 --> 00:32:49.360 align:start position:0% every client emergent to the American 00:32:49.360 --> 00:32:51.629 align:start position:0% every client emergent to the American style<00:32:49.539> and<00:32:50.320> it'll<00:32:50.529> be<00:32:50.590> a<00:32:50.620> very<00:32:50.889> limited<00:32:51.159> Caesar 00:32:51.629 --> 00:32:51.639 align:start position:0% style and it'll be a very limited Caesar 00:32:51.639 --> 00:32:53.460 align:start position:0% style and it'll be a very limited Caesar small<00:32:51.940> contracts<00:32:52.450> that<00:32:52.779> work<00:32:53.019> the<00:32:53.169> CMAs 00:32:53.460 --> 00:32:53.470 align:start position:0% small contracts that work the CMAs 00:32:53.470 --> 00:32:57.570 align:start position:0% small contracts that work the CMAs basically<00:32:55.080> yeah<00:32:56.080> on<00:32:56.559> the<00:32:56.679> first<00:32:56.919> thing<00:32:57.190> yeah<00:32:57.340> I 00:32:57.570 --> 00:32:57.580 align:start position:0% basically yeah on the first thing yeah I 00:32:57.580 --> 00:33:01.529 align:start position:0% basically yeah on the first thing yeah I think<00:32:58.559> it<00:32:59.559> would<00:33:00.039> make<00:33:00.220> sense<00:33:00.490> but<00:33:00.880> probably 00:33:01.529 --> 00:33:01.539 align:start position:0% think it would make sense but probably 00:33:01.539 --> 00:33:05.129 align:start position:0% think it would make sense but probably be<00:33:01.750> a<00:33:01.779> maybe<00:33:02.409> a<00:33:02.529> limited<00:33:03.389> usability<00:33:04.389> and<00:33:04.990> on 00:33:05.129 --> 00:33:05.139 align:start position:0% be a maybe a limited usability and on 00:33:05.139 --> 00:33:06.539 align:start position:0% be a maybe a limited usability and on the<00:33:05.260> second<00:33:05.559> idea<00:33:05.799> I<00:33:05.889> think<00:33:06.039> that<00:33:06.279> would<00:33:06.429> be 00:33:06.539 --> 00:33:06.549 align:start position:0% the second idea I think that would be 00:33:06.549 --> 00:33:07.740 align:start position:0% the second idea I think that would be yeah<00:33:06.940> really 00:33:07.740 --> 00:33:07.750 align:start position:0% yeah really 00:33:07.750 --> 00:33:11.159 align:start position:0% yeah really that<00:33:08.080> look<00:33:08.230> okay<00:33:08.409> period<00:33:09.039> I<00:33:09.360> think<00:33:10.360> use<00:33:10.899> what 00:33:11.159 --> 00:33:11.169 align:start position:0% that look okay period I think use what 00:33:11.169 --> 00:33:13.860 align:start position:0% that look okay period I think use what my<00:33:12.070> team<00:33:12.309> will<00:33:12.490> use<00:33:12.519> music<00:33:13.269> because<00:33:13.570> it<00:33:13.659> was<00:33:13.779> an 00:33:13.860 --> 00:33:13.870 align:start position:0% my team will use music because it was an 00:33:13.870 --> 00:33:15.450 align:start position:0% my team will use music because it was an email<00:33:14.110> a<00:33:14.289> library<00:33:14.710> that<00:33:14.740> has<00:33:15.039> a<00:33:15.070> serious 00:33:15.450 --> 00:33:15.460 align:start position:0% email a library that has a serious 00:33:15.460 --> 00:33:17.910 align:start position:0% email a library that has a serious mentality<00:33:15.850> functions 00:33:17.910 --> 00:33:17.920 align:start position:0% mentality functions 00:33:17.920 --> 00:33:20.070 align:start position:0% mentality functions the<00:33:18.070> contracts<00:33:18.790> were<00:33:18.910> star<00:33:19.210> engage<00:33:19.480> cools<00:33:19.900> the 00:33:20.070 --> 00:33:20.080 align:start position:0% the contracts were star engage cools the 00:33:20.080 --> 00:33:23.430 align:start position:0% the contracts were star engage cools the defendant<00:33:21.010> gets<00:33:21.390> saved<00:33:22.390> in<00:33:22.630> deferral 00:33:23.430 --> 00:33:23.440 align:start position:0% defendant gets saved in deferral 00:33:23.440 --> 00:33:30.190 align:start position:0% defendant gets saved in deferral orientation<00:33:24.400> about<00:33:24.580> the<00:33:24.790> library 00:33:30.190 --> 00:33:30.200 align:start position:0% 00:33:30.200 --> 00:34:50.460 align:start position:0% [Music] 00:34:50.460 --> 00:34:50.470 align:start position:0% 00:34:50.470 --> 00:34:55.919 align:start position:0% tie<00:34:51.429> back<00:34:51.640> to<00:34:51.669> that<00:34:53.190> if<00:34:54.190> you<00:34:54.310> get<00:34:54.630> cheaper<00:34:55.630> call 00:34:55.919 --> 00:34:55.929 align:start position:0% tie back to that if you get cheaper call 00:34:55.929 --> 00:34:57.330 align:start position:0% tie back to that if you get cheaper call the<00:34:56.140> next<00:34:56.380> time<00:34:56.560> you<00:34:56.649> call<00:34:56.830> something<00:34:57.070> that 00:34:57.330 --> 00:34:57.340 align:start position:0% the next time you call something that 00:34:57.340 --> 00:34:59.370 align:start position:0% the next time you call something that you've<00:34:57.460> already<00:34:57.610> called<00:34:57.970> that's<00:34:58.720> like<00:34:59.020> the 00:34:59.370 --> 00:34:59.380 align:start position:0% you've already called that's like the 00:34:59.380 --> 00:35:05.100 align:start position:0% you've already called that's like the more<00:34:59.620> generic<00:34:59.910> version<00:35:00.910> of<00:35:02.100> Alex<00:35:03.100> or<00:35:04.110> typical 00:35:05.100 --> 00:35:05.110 align:start position:0% more generic version of Alex or typical 00:35:05.110 --> 00:35:09.240 align:start position:0% more generic version of Alex or typical self<00:35:05.470> and<00:35:06.420> I<00:35:07.420> took<00:35:07.840> that<00:35:08.200> Eve<00:35:08.440> and<00:35:08.770> I<00:35:08.830> did<00:35:09.070> an 00:35:09.240 --> 00:35:09.250 align:start position:0% self and I took that Eve and I did an 00:35:09.250 --> 00:35:13.260 align:start position:0% self and I took that Eve and I did an analysis<00:35:09.940> we<00:35:10.570> can<00:35:10.690> get<00:35:10.900> up<00:35:11.020> on<00:35:11.170> the<00:35:12.270> screen 00:35:13.260 --> 00:35:13.270 align:start position:0% analysis we can get up on the screen 00:35:13.270 --> 00:35:17.700 align:start position:0% analysis we can get up on the screen there<00:35:13.480> but<00:35:14.130> the<00:35:15.130> analysis<00:35:15.700> looked<00:35:16.210> at<00:35:16.480> if<00:35:17.170> you 00:35:17.700 --> 00:35:17.710 align:start position:0% there but the analysis looked at if you 00:35:17.710 --> 00:35:22.110 align:start position:0% there but the analysis looked at if you have<00:35:18.070> a<00:35:18.670> someone's<00:35:19.860> malicious<00:35:20.860> well<00:35:21.280> at<00:35:21.940> the 00:35:22.110 --> 00:35:22.120 align:start position:0% have a someone's malicious well at the 00:35:22.120 --> 00:35:25.580 align:start position:0% have a someone's malicious well at the contract<00:35:22.630> which<00:35:22.870> repeatedly<00:35:23.560> calls<00:35:23.860> itself 00:35:25.580 --> 00:35:25.590 align:start position:0% contract which repeatedly calls itself 00:35:25.590 --> 00:35:29.280 align:start position:0% contract which repeatedly calls itself as<00:35:26.590> many<00:35:26.860> clients<00:35:27.070> as<00:35:27.250> of<00:35:27.400> town<00:35:27.610> first<00:35:27.910> in<00:35:28.290> Java 00:35:29.280 --> 00:35:29.290 align:start position:0% as many clients as of town first in Java 00:35:29.290 --> 00:35:32.040 align:start position:0% as many clients as of town first in Java means<00:35:29.500> it<00:35:29.650> calls<00:35:29.920> itself<00:35:30.450> recursively<00:35:31.450> to 00:35:32.040 --> 00:35:32.050 align:start position:0% means it calls itself recursively to 00:35:32.050 --> 00:35:34.620 align:start position:0% means it calls itself recursively to limit<00:35:32.860> word<00:35:33.040> can't<00:35:33.310> do<00:35:33.430> that<00:35:33.550> any<00:35:33.820> longer<00:35:33.850> and 00:35:34.620 --> 00:35:34.630 align:start position:0% limit word can't do that any longer and 00:35:34.630 --> 00:35:38.280 align:start position:0% limit word can't do that any longer and when<00:35:35.020> it<00:35:35.310> runs<00:35:36.310> on<00:35:36.550> the<00:35:36.670> gas<00:35:36.850> there<00:35:37.150> it<00:35:37.480> will<00:35:37.870> do 00:35:38.280 --> 00:35:38.290 align:start position:0% when it runs on the gas there it will do 00:35:38.290 --> 00:35:38.670 align:start position:0% when it runs on the gas there it will do it<00:35:38.410> again 00:35:38.670 --> 00:35:38.680 align:start position:0% it again 00:35:38.680 --> 00:36:00.990 align:start position:0% it again so<00:35:38.980> it<00:35:39.070> could<00:35:39.190> be<00:35:39.220> like<00:35:40.320> down<00:35:41.320> down<00:35:59.670> go<00:36:00.670> even 00:36:00.990 --> 00:36:01.000 align:start position:0% so it could be like down down go even 00:36:01.000 --> 00:36:16.690 align:start position:0% so it could be like down down go even though 00:36:16.690 --> 00:36:16.700 align:start position:0% 00:36:16.700 --> 00:36:22.990 align:start position:0% [Music] 00:36:22.990 --> 00:36:23.000 align:start position:0% 00:36:23.000 --> 00:36:43.290 align:start position:0% [Music] 00:36:43.290 --> 00:36:43.300 align:start position:0% 00:36:43.300 --> 00:37:01.149 align:start position:0% [Music] 00:37:01.149 --> 00:37:01.159 align:start position:0% 00:37:01.159 --> 00:37:06.439 align:start position:0% the<00:37:02.159> first<00:37:02.400> contract<00:37:02.849> does<00:37:04.159> just<00:37:05.159> a<00:37:05.729> second 00:37:06.439 --> 00:37:06.449 align:start position:0% the first contract does just a second 00:37:06.449 --> 00:37:08.239 align:start position:0% the first contract does just a second time<00:37:06.900> and<00:37:07.259> what<00:37:07.380> the<00:37:07.469> second<00:37:07.769> one<00:37:07.799> does<00:37:08.009> is<00:37:08.159> it 00:37:08.239 --> 00:37:08.249 align:start position:0% time and what the second one does is it 00:37:08.249 --> 00:37:13.039 align:start position:0% time and what the second one does is it calls<00:37:08.459> itself<00:37:09.439> in<00:37:10.439> the<00:37:10.859> case<00:37:11.039> of<00:37:11.719> reduced<00:37:12.719> toss 00:37:13.039 --> 00:37:13.049 align:start position:0% calls itself in the case of reduced toss 00:37:13.049 --> 00:37:14.569 align:start position:0% calls itself in the case of reduced toss to<00:37:13.529> something<00:37:13.890> that's<00:37:14.009> already<00:37:14.219> been 00:37:14.569 --> 00:37:14.579 align:start position:0% to something that's already been 00:37:14.579 --> 00:37:17.799 align:start position:0% to something that's already been installed<00:37:14.999> this<00:37:15.630> would<00:37:15.839> fall<00:37:16.049> in<00:37:16.169> the<00:37:16.199> same 00:37:17.799 --> 00:37:17.809 align:start position:0% installed this would fall in the same 00:37:17.809 --> 00:37:23.809 align:start position:0% installed this would fall in the same general<00:37:18.809> framework<00:37:22.099> and<00:37:23.099> this<00:37:23.279> is<00:37:23.429> how<00:37:23.579> it 00:37:23.809 --> 00:37:23.819 align:start position:0% general framework and this is how it 00:37:23.819 --> 00:37:26.689 align:start position:0% general framework and this is how it basically<00:37:24.209> looks<00:37:24.859> so<00:37:25.859> first<00:37:26.339> you<00:37:26.519> have<00:37:26.669> a 00:37:26.689 --> 00:37:26.699 align:start position:0% basically looks so first you have a 00:37:26.699 --> 00:37:30.949 align:start position:0% basically looks so first you have a recursive<00:37:27.089> call<00:37:27.359> tree<00:37:28.849> going<00:37:29.849> to<00:37:30.599> a<00:37:30.630> certain 00:37:30.949 --> 00:37:30.959 align:start position:0% recursive call tree going to a certain 00:37:30.959 --> 00:37:34.970 align:start position:0% recursive call tree going to a certain depth<00:37:32.269> this 00:37:34.970 --> 00:37:34.980 align:start position:0% depth this 00:37:34.980 --> 00:37:40.080 align:start position:0% depth this Gasca<00:37:35.980> current<00:37:37.590> and<00:37:38.590> in<00:37:38.740> total<00:37:39.010> there<00:37:39.460> two<00:37:39.910> to 00:37:40.080 --> 00:37:40.090 align:start position:0% Gasca current and in total there two to 00:37:40.090 --> 00:37:43.109 align:start position:0% Gasca current and in total there two to six<00:37:40.330> decorations<00:37:41.080> where<00:37:42.010> it<00:37:42.130> goes<00:37:42.310> to<00:37:43.060> the 00:37:43.109 --> 00:37:43.119 align:start position:0% six decorations where it goes to the 00:37:43.119 --> 00:37:47.609 align:start position:0% six decorations where it goes to the depth<00:37:43.300> of<00:37:43.480> 344<00:37:44.470> and<00:37:45.210> total<00:37:46.380> 13,000<00:37:47.380> cause 00:37:47.609 --> 00:37:47.619 align:start position:0% depth of 344 and total 13,000 cause 00:37:47.619 --> 00:37:49.260 align:start position:0% depth of 344 and total 13,000 cause animate<00:37:48.130> 10<00:37:48.430> million<00:37:48.670> yes 00:37:49.260 --> 00:37:49.270 align:start position:0% animate 10 million yes 00:37:49.270 --> 00:37:55.350 align:start position:0% animate 10 million yes and<00:37:49.920> if<00:37:51.420> xyx<00:37:53.010> implements<00:37:54.010> the<00:37:54.160> where<00:37:55.030> the 00:37:55.350 --> 00:37:55.360 align:start position:0% and if xyx implements the where the 00:37:55.360 --> 00:37:59.010 align:start position:0% and if xyx implements the where the reduce<00:37:55.690> will<00:37:56.290> be<00:37:56.410> the<00:37:57.060> 1400<00:37:58.060> there<00:37:58.840> will<00:37:58.990> be 00:37:59.010 --> 00:37:59.020 align:start position:0% reduce will be the 1400 there will be 00:37:59.020 --> 00:38:01.140 align:start position:0% reduce will be the 1400 there will be welcome<00:37:59.950> is<00:38:00.070> the<00:38:00.100> more<00:38:00.369> important<00:38:00.820> to<00:38:00.940> five 00:38:01.140 --> 00:38:01.150 align:start position:0% welcome is the more important to five 00:38:01.150 --> 00:38:03.620 align:start position:0% welcome is the more important to five iterations<00:38:01.420> and<00:38:01.990> the<00:38:02.110> maximum<00:38:02.590> that<00:38:02.740> for<00:38:02.950> 503 00:38:03.620 --> 00:38:03.630 align:start position:0% iterations and the maximum that for 503 00:38:03.630 --> 00:38:07.050 align:start position:0% iterations and the maximum that for 503 and<00:38:04.630> what<00:38:05.619> you<00:38:05.770> can<00:38:05.920> see<00:38:06.100> what's<00:38:06.340> that<00:38:06.520> on<00:38:06.730> gift 00:38:07.050 --> 00:38:07.060 align:start position:0% and what you can see what's that on gift 00:38:07.060 --> 00:38:10.109 align:start position:0% and what you can see what's that on gift without<00:38:07.810> any<00:38:08.140> state<00:38:08.560> to<00:38:08.860> anything<00:38:09.250> and<00:38:09.550> i<00:38:09.910> only 00:38:10.109 --> 00:38:10.119 align:start position:0% without any state to anything and i only 00:38:10.119 --> 00:38:12.690 align:start position:0% without any state to anything and i only the<00:38:10.300> cure<00:38:10.570> gets<00:38:11.140> run<00:38:11.350> times<00:38:11.619> the<00:38:12.160> execution 00:38:12.690 --> 00:38:12.700 align:start position:0% the cure gets run times the execution 00:38:12.700 --> 00:38:17.359 align:start position:0% the cure gets run times the execution time<00:38:13.110> jumped<00:38:14.110> up<00:38:14.230> to<00:38:14.470> one<00:38:15.130> point<00:38:15.310> 18<00:38:15.850> seconds 00:38:17.359 --> 00:38:17.369 align:start position:0% time jumped up to one point 18 seconds 00:38:17.369 --> 00:38:24.380 align:start position:0% time jumped up to one point 18 seconds and<00:38:18.369> I'm<00:38:18.700> sure<00:38:18.940> the<00:38:19.180> must<00:38:19.360> be<00:38:19.510> the<00:38:19.630> floor 00:38:24.380 --> 00:38:24.390 align:start position:0% 00:38:24.390 --> 00:38:27.979 align:start position:0% yeah<00:38:24.839> and<00:38:25.079> then<00:38:25.349> became<00:38:26.630> 171,000<00:38:27.630> Coulson 00:38:27.979 --> 00:38:27.989 align:start position:0% yeah and then became 171,000 Coulson 00:38:27.989 --> 00:38:32.920 align:start position:0% yeah and then became 171,000 Coulson pump<00:38:28.200> oh<00:38:29.119> that's<00:38:30.119> pretty<00:38:30.329> steep<00:38:30.930> difference 00:38:32.920 --> 00:38:32.930 align:start position:0% pump oh that's pretty steep difference 00:38:32.930 --> 00:38:37.430 align:start position:0% pump oh that's pretty steep difference yeah<00:38:35.329> but<00:38:36.329> I<00:38:36.359> mean<00:38:36.539> you<00:38:36.630> could<00:38:36.779> adjust<00:38:36.900> the<00:38:37.230> gap 00:38:37.430 --> 00:38:37.440 align:start position:0% yeah but I mean you could adjust the gap 00:38:37.440 --> 00:38:41.089 align:start position:0% yeah but I mean you could adjust the gap priced<00:38:37.849> right<00:38:38.849> right<00:38:39.359> but<00:38:39.630> so<00:38:39.989> do<00:38:40.799> you<00:38:40.829> have<00:38:40.950> to 00:38:41.089 --> 00:38:41.099 align:start position:0% priced right right but so do you have to 00:38:41.099 --> 00:38:54.160 align:start position:0% priced right right but so do you have to decide<00:38:41.400> what<00:38:41.759> so<00:38:41.910> yeah<00:38:42.390> both<00:38:42.779> the<00:38:43.970> number<00:38:44.970> 14 00:38:54.160 --> 00:38:54.170 align:start position:0% 00:38:54.170 --> 00:39:00.900 align:start position:0% [Music] 00:39:00.900 --> 00:39:00.910 align:start position:0% 00:39:00.910 --> 00:39:03.730 align:start position:0% that's<00:39:01.910> what<00:39:02.180> spokes<00:39:02.569> third<00:39:02.900> person<00:39:03.470> from 00:39:03.730 --> 00:39:03.740 align:start position:0% that's what spokes third person from 00:39:03.740 --> 00:39:06.730 align:start position:0% that's what spokes third person from reaching<00:39:04.069> 1,000<00:39:04.819> foot<00:39:04.970> boards<00:39:05.470> but<00:39:06.470> when<00:39:06.619> that 00:39:06.730 --> 00:39:06.740 align:start position:0% reaching 1,000 foot boards but when that 00:39:06.740 --> 00:39:09.940 align:start position:0% reaching 1,000 foot boards but when that recursion<00:39:07.309> them<00:39:07.460> souls<00:39:07.910> all<00:39:08.420> those<00:39:08.720> 164<00:39:09.680> sorry 00:39:09.940 --> 00:39:09.950 align:start position:0% recursion them souls all those 164 sorry 00:39:09.950 --> 00:39:13.270 align:start position:0% recursion them souls all those 164 sorry turn<00:39:10.270> and<00:39:11.270> we<00:39:11.390> can<00:39:11.539> go<00:39:11.690> one<00:39:12.319> level<00:39:12.530> down<00:39:12.770> and<00:39:13.160> do 00:39:13.270 --> 00:39:13.280 align:start position:0% turn and we can go one level down and do 00:39:13.280 --> 00:39:15.599 align:start position:0% turn and we can go one level down and do the<00:39:13.430> depression<00:39:13.819> again<00:39:14.059> it'll<00:39:14.569> be<00:39:14.630> short 00:39:15.599 --> 00:39:15.609 align:start position:0% the depression again it'll be short 00:39:15.609 --> 00:39:20.680 align:start position:0% the depression again it'll be short because<00:39:16.750> started<00:39:18.789> so<00:39:19.789> there's<00:39:19.970> no<00:39:20.359> need<00:39:20.660> to 00:39:20.680 --> 00:39:20.690 align:start position:0% because started so there's no need to 00:39:20.690 --> 00:39:22.480 align:start position:0% because started so there's no need to use<00:39:20.960> an<00:39:21.140> explicit<00:39:21.680> call<00:39:21.799> that<00:39:22.010> plan<00:39:22.190> that<00:39:22.339> was 00:39:22.480 --> 00:39:22.490 align:start position:0% use an explicit call that plan that was 00:39:22.490 --> 00:39:26.589 align:start position:0% use an explicit call that plan that was do 00:39:26.589 --> 00:39:26.599 align:start position:0% 00:39:26.599 --> 00:39:30.799 align:start position:0% just<00:39:27.599> have<00:39:27.749> one<00:39:29.150> but<00:39:30.150> just<00:39:30.390> to<00:39:30.450> be<00:39:30.569> clear<00:39:30.599> that 00:39:30.799 --> 00:39:30.809 align:start position:0% just have one but just to be clear that 00:39:30.809 --> 00:39:33.170 align:start position:0% just have one but just to be clear that proposed<00:39:31.410> 14<00:39:32.099> or<00:39:32.279> whatever<00:39:32.549> it<00:39:32.730> was<00:39:32.849> to<00:39:32.910> the 00:39:33.170 --> 00:39:33.180 align:start position:0% proposed 14 or whatever it was to the 00:39:33.180 --> 00:39:35.930 align:start position:0% proposed 14 or whatever it was to the guestlist<00:39:33.569> it<00:39:33.839> was<00:39:33.990> just<00:39:34.339> starting<00:39:35.339> number 00:39:35.930 --> 00:39:35.940 align:start position:0% guestlist it was just starting number 00:39:35.940 --> 00:39:37.910 align:start position:0% guestlist it was just starting number which<00:39:36.420> means<00:39:36.749> do<00:39:36.900> the<00:39:37.109> benchmark<00:39:37.619> which<00:39:37.890> is 00:39:37.910 --> 00:39:37.920 align:start position:0% which means do the benchmark which is 00:39:37.920 --> 00:39:41.089 align:start position:0% which means do the benchmark which is right<00:39:38.869> where<00:39:39.869> this<00:39:40.019> is<00:39:40.230> always<00:39:40.499> good<00:39:40.769> to<00:39:40.920> happy 00:39:41.089 --> 00:39:41.099 align:start position:0% right where this is always good to happy 00:39:41.099 --> 00:39:43.930 align:start position:0% right where this is always good to happy with<00:39:41.339> it<00:39:41.549> yeah<00:39:41.789> say<00:39:42.119> to<00:39:42.180> you<00:39:42.359> you<00:39:42.779> have<00:39:43.109> this 00:39:43.930 --> 00:39:43.940 align:start position:0% with it yeah say to you you have this 00:39:43.940 --> 00:39:47.349 align:start position:0% with it yeah say to you you have this just<00:39:44.940> repricing<00:39:45.630> with<00:39:45.990> dynamic<00:39:46.470> repressing 00:39:47.349 --> 00:39:47.359 align:start position:0% just repricing with dynamic repressing 00:39:47.359 --> 00:39:53.870 align:start position:0% just repricing with dynamic repressing for<00:39:48.359> goal<00:39:48.599> that<00:39:48.869> you<00:39:49.019> more<00:39:49.470> often<00:39:52.759> there<00:39:53.759> is 00:39:53.870 --> 00:39:53.880 align:start position:0% for goal that you more often there is 00:39:53.880 --> 00:39:54.799 align:start position:0% for goal that you more often there is like<00:39:54.059> an<00:39:54.210> eternity 00:39:54.799 --> 00:39:54.809 align:start position:0% like an eternity 00:39:54.809 --> 00:39:56.839 align:start position:0% like an eternity I<00:39:54.839> mean<00:39:55.079> even<00:39:55.230> if<00:39:55.410> we<00:39:55.440> pull<00:39:55.859> call<00:39:56.430> something 00:39:56.839 --> 00:39:56.849 align:start position:0% I mean even if we pull call something 00:39:56.849 --> 00:39:58.789 align:start position:0% I mean even if we pull call something that's<00:39:57.150> working<00:39:57.569> close<00:39:57.869> there<00:39:58.440> is<00:39:58.470> an 00:39:58.789 --> 00:39:58.799 align:start position:0% that's working close there is an 00:39:58.799 --> 00:40:01.940 align:start position:0% that's working close there is an inherent<00:39:59.220> over<00:39:59.609> up<00:39:59.849> in<00:40:00.329> the<00:40:01.170> yes<00:40:01.410> they<00:40:01.589> can<00:40:01.650> do 00:40:01.940 --> 00:40:01.950 align:start position:0% inherent over up in the yes they can do 00:40:01.950 --> 00:40:04.039 align:start position:0% inherent over up in the yes they can do condemn<00:40:02.279> sweets<00:40:02.609> no<00:40:03.029> such<00:40:03.480> a<00:40:03.509> the<00:40:03.690> questions 00:40:04.039 --> 00:40:04.049 align:start position:0% condemn sweets no such a the questions 00:40:04.049 --> 00:40:09.270 align:start position:0% condemn sweets no such a the questions like<00:40:04.170> how<00:40:04.380> bad<00:40:04.619> is<00:40:04.980> this<00:40:07.249> fundamental 00:40:09.270 --> 00:40:09.280 align:start position:0% like how bad is this fundamental 00:40:09.280 --> 00:40:20.130 align:start position:0% like how bad is this fundamental [Music] 00:40:20.130 --> 00:40:20.140 align:start position:0% 00:40:20.140 --> 00:40:23.259 align:start position:0% right<00:40:21.170> this<00:40:21.680> probably<00:40:22.039> means<00:40:22.190> 700<00:40:22.880> is<00:40:23.000> pretty 00:40:23.259 --> 00:40:23.269 align:start position:0% right this probably means 700 is pretty 00:40:23.269 --> 00:40:26.470 align:start position:0% right this probably means 700 is pretty cheap<00:40:23.599> to<00:40:23.930> compare<00:40:24.349> it<00:40:24.500> to<00:40:24.680> an<00:40:24.829> extra<00:40:25.069> cash<00:40:25.490> but 00:40:26.470 --> 00:40:26.480 align:start position:0% cheap to compare it to an extra cash but 00:40:26.480 --> 00:40:30.519 align:start position:0% cheap to compare it to an extra cash but it's<00:40:26.630> super<00:40:27.140> expensive<00:40:28.089> and<00:40:29.089> then<00:40:29.900> you<00:40:30.319> get 00:40:30.519 --> 00:40:30.529 align:start position:0% it's super expensive and then you get 00:40:30.529 --> 00:40:33.430 align:start position:0% it's super expensive and then you get into<00:40:30.799> the<00:40:31.240> incentive<00:40:32.240> so<00:40:32.930> I<00:40:32.960> can<00:40:33.230> write 00:40:33.430 --> 00:40:33.440 align:start position:0% into the incentive so I can write 00:40:33.440 --> 00:40:35.769 align:start position:0% into the incentive so I can write modular<00:40:33.950> contracts<00:40:34.819> instead<00:40:34.970> of<00:40:35.240> fabula<00:40:35.660> a 00:40:35.769 --> 00:40:35.779 align:start position:0% modular contracts instead of fabula a 00:40:35.779 --> 00:40:40.150 align:start position:0% modular contracts instead of fabula a huge<00:40:36.279> we're<00:40:37.279> all<00:40:38.269> artists<00:40:38.599> just<00:40:38.920> so<00:40:39.920> because 00:40:40.150 --> 00:40:40.160 align:start position:0% huge we're all artists just so because 00:40:40.160 --> 00:40:44.319 align:start position:0% huge we're all artists just so because there<00:40:40.279> were<00:40:40.369> just<00:40:40.400> a<00:40:40.609> small<00:40:40.670> war<00:40:41.089> then<00:40:43.329> the 00:40:44.319 --> 00:40:44.329 align:start position:0% there were just a small war then the 00:40:44.329 --> 00:40:45.640 align:start position:0% there were just a small war then the repression<00:40:44.750> of<00:40:44.779> all<00:40:44.990> would<00:40:45.140> affect<00:40:45.410> that<00:40:45.470> so 00:40:45.640 --> 00:40:45.650 align:start position:0% repression of all would affect that so 00:40:45.650 --> 00:40:47.319 align:start position:0% repression of all would affect that so you<00:40:45.980> should<00:40:46.009> write<00:40:46.430> for<00:40:46.460> one<00:40:46.789> tool<00:40:46.910> a<00:40:46.940> contract 00:40:47.319 --> 00:40:47.329 align:start position:0% you should write for one tool a contract 00:40:47.329 --> 00:40:49.029 align:start position:0% you should write for one tool a contract which<00:40:47.480> are<00:40:47.660> easier<00:40:48.230> to<00:40:48.289> understand<00:40:48.710> lengths 00:40:49.029 --> 00:40:49.039 align:start position:0% which are easier to understand lengths 00:40:49.039 --> 00:40:51.099 align:start position:0% which are easier to understand lengths probably<00:40:49.460> safer<00:40:49.759> in<00:40:49.849> general<00:40:50.180> but<00:40:50.809> if<00:40:50.960> you're 00:40:51.099 --> 00:40:51.109 align:start position:0% probably safer in general but if you're 00:40:51.109 --> 00:40:53.440 align:start position:0% probably safer in general but if you're very<00:40:51.319> extremely<00:40:51.769> months<00:40:52.099> and<00:40:52.279> guests<00:40:52.759> they 00:40:53.440 --> 00:40:53.450 align:start position:0% very extremely months and guests they 00:40:53.450 --> 00:40:55.390 align:start position:0% very extremely months and guests they would<00:40:53.660> just<00:40:53.869> like<00:40:54.109> writing<00:40:54.680> which<00:40:54.980> in<00:40:55.130> huge 00:40:55.390 --> 00:40:55.400 align:start position:0% would just like writing which in huge 00:40:55.400 --> 00:40:57.549 align:start position:0% would just like writing which in huge contract<00:40:55.880> and<00:40:56.180> just<00:40:56.210> intro<00:40:56.960> calls<00:40:57.319> and 00:40:57.549 --> 00:40:57.559 align:start position:0% contract and just intro calls and 00:40:57.559 --> 00:40:59.529 align:start position:0% contract and just intro calls and functions<00:40:57.950> and<00:40:58.670> Anna<00:40:58.970> just<00:40:59.119> conjoined 00:40:59.529 --> 00:40:59.539 align:start position:0% functions and Anna just conjoined 00:40:59.539 --> 00:41:01.690 align:start position:0% functions and Anna just conjoined between<00:41:00.049> them<00:41:00.230> but<00:41:00.740> then<00:41:00.890> say<00:41:01.130> there's 00:41:01.690 --> 00:41:01.700 align:start position:0% between them but then say there's 00:41:01.700 --> 00:41:04.089 align:start position:0% between them but then say there's incentive<00:41:02.210> to<00:41:02.450> write<00:41:02.630> more<00:41:03.410> contracts 00:41:04.089 --> 00:41:04.099 align:start position:0% incentive to write more contracts 00:41:04.099 --> 00:41:07.470 align:start position:0% incentive to write more contracts against<00:41:04.460> similar<00:41:04.940> contract<00:41:05.650> but<00:41:06.650> that's 00:41:07.470 --> 00:41:07.480 align:start position:0% against similar contract but that's 00:41:07.480 --> 00:41:10.059 align:start position:0% against similar contract but that's inherent<00:41:08.480> that<00:41:08.630> means<00:41:08.779> jump<00:41:09.140> is<00:41:09.440> inherently 00:41:10.059 --> 00:41:10.069 align:start position:0% inherent that means jump is inherently 00:41:10.069 --> 00:41:11.349 align:start position:0% inherent that means jump is inherently cheaper<00:41:10.579> for<00:41:10.759> the<00:41:10.880> event 00:41:11.349 --> 00:41:11.359 align:start position:0% cheaper for the event 00:41:11.359 --> 00:41:13.839 align:start position:0% cheaper for the event correct<00:41:12.289> right<00:41:12.440> over<00:41:12.589> those<00:41:12.829> will<00:41:13.160> be<00:41:13.369> you 00:41:13.839 --> 00:41:13.849 align:start position:0% correct right over those will be you 00:41:13.849 --> 00:41:15.309 align:start position:0% correct right over those will be you know<00:41:13.970> you<00:41:14.029> take<00:41:14.359> care<00:41:14.569> all<00:41:14.720> the<00:41:14.839> sorts<00:41:15.200> of 00:41:15.309 --> 00:41:15.319 align:start position:0% know you take care all the sorts of 00:41:15.319 --> 00:41:18.069 align:start position:0% know you take care all the sorts of variables<00:41:15.890> and<00:41:16.160> of<00:41:16.339> veracity<00:41:17.059> call<00:41:17.720> is<00:41:17.900> like 00:41:18.069 --> 00:41:18.079 align:start position:0% variables and of veracity call is like 00:41:18.079 --> 00:41:20.289 align:start position:0% variables and of veracity call is like the<00:41:18.619> other<00:41:18.680> email<00:41:19.039> takes<00:41:19.250> care<00:41:19.519> although<00:41:19.730> yes 00:41:20.289 --> 00:41:20.299 align:start position:0% the other email takes care although yes 00:41:20.299 --> 00:41:22.839 align:start position:0% the other email takes care although yes personally<00:41:20.660> I'm<00:41:21.200> just<00:41:21.470> from<00:41:22.130> the<00:41:22.160> perspective 00:41:22.839 --> 00:41:22.849 align:start position:0% personally I'm just from the perspective 00:41:22.849 --> 00:41:27.519 align:start position:0% personally I'm just from the perspective of<00:41:23.329> the<00:41:23.660> incentive<00:41:24.220> for<00:41:25.220> coders<00:41:25.490> to<00:41:26.289> write<00:41:27.289> my 00:41:27.519 --> 00:41:27.529 align:start position:0% of the incentive for coders to write my 00:41:27.529 --> 00:41:31.059 align:start position:0% of the incentive for coders to write my comments<00:41:28.359> that's<00:41:29.359> the<00:41:29.509> perspective<00:41:30.039> can<00:41:31.039> be 00:41:31.059 --> 00:41:31.069 align:start position:0% comments that's the perspective can be 00:41:31.069 --> 00:41:33.490 align:start position:0% comments that's the perspective can be backtrack<00:41:31.519> a<00:41:31.549> tiny<00:41:31.849> bit<00:41:32.029> you<00:41:32.289> went<00:41:33.289> here<00:41:33.410> at 00:41:33.490 --> 00:41:33.500 align:start position:0% backtrack a tiny bit you went here at 00:41:33.500 --> 00:41:35.259 align:start position:0% backtrack a tiny bit you went here at the<00:41:33.559> beginning<00:41:33.680> and<00:41:33.920> I<00:41:34.609> know<00:41:34.940> that<00:41:35.119> some 00:41:35.259 --> 00:41:35.269 align:start position:0% the beginning and I know that some 00:41:35.269 --> 00:41:35.870 align:start position:0% the beginning and I know that some people 00:41:35.870 --> 00:41:35.880 align:start position:0% people 00:41:35.880 --> 00:41:39.470 align:start position:0% people questions<00:41:36.329> of<00:41:36.450> the<00:41:36.539> previous<00:41:38.269> cover<00:41:39.269> death 00:41:39.470 --> 00:41:39.480 align:start position:0% questions of the previous cover death 00:41:39.480 --> 00:41:41.359 align:start position:0% questions of the previous cover death but<00:41:39.839> we<00:41:39.930> started<00:41:40.319> off<00:41:40.470> with<00:41:40.619> one<00:41:41.039> single 00:41:41.359 --> 00:41:41.369 align:start position:0% but we started off with one single 00:41:41.369 --> 00:41:44.150 align:start position:0% but we started off with one single question<00:41:41.490> in<00:41:42.200> position<00:41:43.200> quite<00:41:43.349> a<00:41:43.410> bit<00:41:43.619> the 00:41:44.150 --> 00:41:44.160 align:start position:0% question in position quite a bit the 00:41:44.160 --> 00:41:46.819 align:start position:0% question in position quite a bit the single<00:41:44.460> question<00:41:44.849> was<00:41:45.059> why<00:41:45.960> is<00:41:45.990> the<00:41:46.410> code<00:41:46.619> says 00:41:46.819 --> 00:41:46.829 align:start position:0% single question was why is the code says 00:41:46.829 --> 00:41:51.049 align:start position:0% single question was why is the code says mechanic<00:41:47.430> or<00:41:47.640> TM<00:41:48.000> to<00:41:48.180> be<00:41:48.329> extended<00:41:48.839> and<00:41:49.910> it<00:41:50.910> is 00:41:51.049 --> 00:41:51.059 align:start position:0% mechanic or TM to be extended and it is 00:41:51.059 --> 00:41:53.779 align:start position:0% mechanic or TM to be extended and it is a<00:41:51.089> lot<00:41:51.269> of<00:41:51.359> different<00:41:51.750> topics<00:41:52.740> we<00:41:53.250> can<00:41:53.430> discuss 00:41:53.779 --> 00:41:53.789 align:start position:0% a lot of different topics we can discuss 00:41:53.789 --> 00:41:57.079 align:start position:0% a lot of different topics we can discuss in<00:41:53.970> with<00:41:54.119> it<00:41:54.240> whatever<00:41:54.809> you<00:41:55.079> think<00:41:55.910> one<00:41:56.910> we 00:41:57.079 --> 00:41:57.089 align:start position:0% in with it whatever you think one we 00:41:57.089 --> 00:41:58.670 align:start position:0% in with it whatever you think one we suggested<00:41:57.630> that<00:41:57.660> it<00:41:57.900> makes<00:41:58.079> sense<00:41:58.289> to<00:41:58.440> break 00:41:58.670 --> 00:41:58.680 align:start position:0% suggested that it makes sense to break 00:41:58.680 --> 00:42:00.490 align:start position:0% suggested that it makes sense to break up<00:41:58.859> contracts<00:41:59.460> to<00:41:59.549> make<00:41:59.640> them<00:41:59.789> more<00:41:59.940> matter 00:42:00.490 --> 00:42:00.500 align:start position:0% up contracts to make them more matter 00:42:00.500 --> 00:42:03.710 align:start position:0% up contracts to make them more matter but<00:42:01.500> that<00:42:01.650> has<00:42:01.859> the<00:42:02.009> issue<00:42:02.130> of<00:42:02.309> of<00:42:02.759> the<00:42:03.150> cost<00:42:03.569> of 00:42:03.710 --> 00:42:03.720 align:start position:0% but that has the issue of of the cost of 00:42:03.720 --> 00:42:08.390 align:start position:0% but that has the issue of of the cost of fall<00:42:03.990> and<00:42:04.319> you<00:42:04.890> know<00:42:05.009> these<00:42:05.250> overheads<00:42:06.440> and<00:42:07.440> we 00:42:08.390 --> 00:42:08.400 align:start position:0% fall and you know these overheads and we 00:42:08.400 --> 00:42:11.029 align:start position:0% fall and you know these overheads and we also<00:42:08.549> explained<00:42:09.089> that<00:42:09.329> the<00:42:10.259> code<00:42:10.470> size<00:42:10.680> limit 00:42:11.029 --> 00:42:11.039 align:start position:0% also explained that the code size limit 00:42:11.039 --> 00:42:13.700 align:start position:0% also explained that the code size limit is<00:42:11.250> there<00:42:11.579> because<00:42:11.849> of<00:42:12.359> an<00:42:12.539> issue<00:42:12.710> analysis 00:42:13.700 --> 00:42:13.710 align:start position:0% is there because of an issue analysis 00:42:13.710 --> 00:42:16.009 align:start position:0% is there because of an issue analysis cost<00:42:14.279> and<00:42:14.549> it's<00:42:14.670> it's<00:42:14.910> a<00:42:15.000> u.s.<00:42:15.329> record<00:42:15.509> and<00:42:15.900> I 00:42:16.009 --> 00:42:16.019 align:start position:0% cost and it's it's a u.s. record and I 00:42:16.019 --> 00:42:18.579 align:start position:0% cost and it's it's a u.s. record and I know<00:42:16.079> there<00:42:16.319> was<00:42:16.440> a<00:42:16.470> question<00:42:16.650> probably<00:42:17.130> there 00:42:18.579 --> 00:42:18.589 align:start position:0% know there was a question probably there 00:42:18.589 --> 00:42:20.569 align:start position:0% know there was a question probably there which<00:42:19.589> we<00:42:19.740> never<00:42:19.859> answered 00:42:20.569 --> 00:42:20.579 align:start position:0% which we never answered 00:42:20.579 --> 00:42:23.620 align:start position:0% which we never answered can<00:42:21.089> we<00:42:21.269> moved<00:42:21.509> to<00:42:21.750> the<00:42:21.990> analysis<00:42:22.200> earlier<00:42:22.980> a 00:42:23.620 --> 00:42:23.630 align:start position:0% can we moved to the analysis earlier a 00:42:23.630 --> 00:42:29.809 align:start position:0% can we moved to the analysis earlier a deployment<00:42:24.630> and<00:42:26.599> I<00:42:27.890> think<00:42:28.890> it's<00:42:29.640> certainly 00:42:29.809 --> 00:42:29.819 align:start position:0% deployment and I think it's certainly 00:42:29.819 --> 00:42:31.330 align:start position:0% deployment and I think it's certainly possible 00:42:31.330 --> 00:42:31.340 align:start position:0% possible 00:42:31.340 --> 00:42:34.600 align:start position:0% possible to<00:42:31.970> type<00:42:32.420> in<00:42:32.630> that<00:42:32.780> case<00:42:33.170> the<00:42:34.040> deployer<00:42:34.340> is 00:42:34.600 --> 00:42:34.610 align:start position:0% to type in that case the deployer is 00:42:34.610 --> 00:42:36.280 align:start position:0% to type in that case the deployer is already<00:42:34.940> paying<00:42:35.150> yes<00:42:35.450> proportional<00:42:36.140> to 00:42:36.280 --> 00:42:36.290 align:start position:0% already paying yes proportional to 00:42:36.290 --> 00:42:37.760 align:start position:0% already paying yes proportional to inside 00:42:37.760 --> 00:42:37.770 align:start position:0% inside 00:42:37.770 --> 00:42:40.550 align:start position:0% inside paid<00:42:38.430> for<00:42:38.730> at<00:42:39.030> least<00:42:39.120> there's<00:42:39.390> no<00:42:39.560> description 00:42:40.550 --> 00:42:40.560 align:start position:0% paid for at least there's no description 00:42:40.560 --> 00:42:44.540 align:start position:0% paid for at least there's no description seeing<00:42:40.920> because<00:42:41.160> there 00:42:44.540 --> 00:42:44.550 align:start position:0% 00:42:44.550 --> 00:42:46.160 align:start position:0% invisible<00:42:45.550> change 00:42:46.160 --> 00:42:46.170 align:start position:0% invisible change 00:42:46.170 --> 00:42:48.500 align:start position:0% invisible change the<00:42:46.380> contract<00:42:46.829> actually<00:42:47.510> BPM 00:42:48.500 --> 00:42:48.510 align:start position:0% the contract actually BPM 00:42:48.510 --> 00:42:50.329 align:start position:0% the contract actually BPM implementations<00:42:49.349> to<00:42:49.529> be<00:42:49.619> able<00:42:49.740> to<00:42:49.829> serialize 00:42:50.329 --> 00:42:50.339 align:start position:0% implementations to be able to serialize 00:42:50.339 --> 00:42:51.980 align:start position:0% implementations to be able to serialize that<00:42:50.640> and<00:42:50.760> they<00:42:50.819> also<00:42:51.000> said<00:42:51.359> that<00:42:51.480> efficiently 00:42:51.980 --> 00:42:51.990 align:start position:0% that and they also said that efficiently 00:42:51.990 --> 00:42:57.380 align:start position:0% that and they also said that efficiently loaded<00:42:52.380> up<00:42:52.500> again<00:42:53.299> execution 00:42:57.380 --> 00:42:57.390 align:start position:0% 00:42:57.390 --> 00:43:01.130 align:start position:0% if<00:42:57.989> even<00:42:58.499> if<00:42:58.589> they<00:42:58.769> do<00:42:59.039> that<00:42:59.269> we<00:43:00.269> would 00:43:01.130 --> 00:43:01.140 align:start position:0% if even if they do that we would 00:43:01.140 --> 00:43:02.569 align:start position:0% if even if they do that we would incentivize<00:43:01.499> people<00:43:01.799> to<00:43:01.980> create<00:43:02.369> bigger 00:43:02.569 --> 00:43:02.579 align:start position:0% incentivize people to create bigger 00:43:02.579 --> 00:43:08.870 align:start position:0% incentivize people to create bigger contracts<00:43:06.680> device<00:43:07.680> company<00:43:08.069> to<00:43:08.279> make<00:43:08.670> them 00:43:08.870 --> 00:43:08.880 align:start position:0% contracts device company to make them 00:43:08.880 --> 00:43:22.549 align:start position:0% contracts device company to make them practical<00:43:09.920> and<00:43:10.920> still<00:43:20.749> but<00:43:21.749> let's<00:43:22.019> assume<00:43:22.140> we 00:43:22.549 --> 00:43:22.559 align:start position:0% practical and still but let's assume we 00:43:22.559 --> 00:43:25.729 align:start position:0% practical and still but let's assume we would<00:43:23.089> we<00:43:24.089> would<00:43:24.119> make<00:43:24.390> this<00:43:24.599> easier<00:43:25.289> and<00:43:25.559> we 00:43:25.729 --> 00:43:25.739 align:start position:0% would we would make this easier and we 00:43:25.739 --> 00:43:27.289 align:start position:0% would we would make this easier and we would<00:43:25.920> mr.<00:43:26.369> Coates<00:43:26.549> estimate<00:43:26.999> that<00:43:27.210> we 00:43:27.289 --> 00:43:27.299 align:start position:0% would mr. Coates estimate that we 00:43:27.299 --> 00:43:29.200 align:start position:0% would mr. Coates estimate that we wouldn't<00:43:27.539> do<00:43:27.630> anything<00:43:27.869> on<00:43:28.319> the<00:43:28.619> call<00:43:28.829> cost 00:43:29.200 --> 00:43:29.210 align:start position:0% wouldn't do anything on the call cost 00:43:29.210 --> 00:43:32.839 align:start position:0% wouldn't do anything on the call cost then<00:43:30.440> then<00:43:31.440> we<00:43:31.589> would<00:43:31.769> be<00:43:31.920> just<00:43:32.220> expanding 00:43:32.839 --> 00:43:32.849 align:start position:0% then then we would be just expanding 00:43:32.849 --> 00:43:35.089 align:start position:0% then then we would be just expanding this<00:43:32.999> piece<00:43:33.299> to<00:43:34.140> make<00:43:34.529> more<00:43:34.799> monolithic 00:43:35.089 --> 00:43:35.099 align:start position:0% this piece to make more monolithic 00:43:35.099 --> 00:43:39.079 align:start position:0% this piece to make more monolithic contracts<00:43:35.759> and<00:43:37.160> the<00:43:38.160> the<00:43:38.430> alternative<00:43:38.970> to 00:43:39.079 --> 00:43:39.089 align:start position:0% contracts and the the alternative to 00:43:39.089 --> 00:43:42.440 align:start position:0% contracts and the the alternative to that<00:43:39.210> is<00:43:39.390> maybe<00:43:39.599> consider<00:43:40.849> making<00:43:41.849> multiple 00:43:42.440 --> 00:43:42.450 align:start position:0% that is maybe consider making multiple 00:43:42.450 --> 00:43:44.809 align:start position:0% that is maybe consider making multiple contracts<00:43:42.930> more<00:43:43.079> attractive<00:43:43.529> and<00:43:44.489> that's 00:43:44.809 --> 00:43:44.819 align:start position:0% contracts more attractive and that's 00:43:44.819 --> 00:43:53.580 align:start position:0% contracts more attractive and that's what<00:43:44.970> we<00:43:45.119> have<00:43:45.299> been<00:43:45.450> discussing 00:43:53.580 --> 00:43:53.590 align:start position:0% 00:43:53.590 --> 00:43:57.970 align:start position:0% but<00:43:56.650> scientists<00:43:57.650> soon 00:43:57.970 --> 00:43:57.980 align:start position:0% but scientists soon 00:43:57.980 --> 00:43:59.740 align:start position:0% but scientists soon let<00:43:58.310> me<00:43:58.430> put<00:43:58.580> it<00:43:58.700> in<00:43:58.850> fact<00:43:59.030> we<00:43:59.300> find<00:43:59.510> some 00:43:59.740 --> 00:43:59.750 align:start position:0% let me put it in fact we find some 00:43:59.750 --> 00:44:03.550 align:start position:0% let me put it in fact we find some material<00:44:00.410> and<00:44:01.750> we're<00:44:02.750> distant<00:44:02.930> projects 00:44:03.550 --> 00:44:03.560 align:start position:0% material and we're distant projects 00:44:03.560 --> 00:44:08.550 align:start position:0% material and we're distant projects every<00:44:03.890> time<00:44:04.580> you<00:44:04.760> recall<00:44:05.360> it 00:44:08.550 --> 00:44:08.560 align:start position:0% 00:44:08.560 --> 00:44:11.400 align:start position:0% would<00:44:08.830> be<00:44:08.920> possible<00:44:09.340> to<00:44:09.400> have<00:44:10.030> in<00:44:10.390> my<00:44:10.750> contract 00:44:11.400 --> 00:44:11.410 align:start position:0% would be possible to have in my contract 00:44:11.410 --> 00:44:13.740 align:start position:0% would be possible to have in my contract the<00:44:11.980> ability<00:44:12.490> to<00:44:12.520> indicate<00:44:13.270> that<00:44:13.330> a<00:44:13.480> club 00:44:13.740 --> 00:44:13.750 align:start position:0% the ability to indicate that a club 00:44:13.750 --> 00:44:16.440 align:start position:0% the ability to indicate that a club could<00:44:13.990> be<00:44:14.140> at<00:44:14.320> one<00:44:14.820> so<00:44:15.820> I<00:44:15.880> can<00:44:15.970> still<00:44:16.210> write<00:44:16.420> a 00:44:16.440 --> 00:44:16.450 align:start position:0% could be at one so I can still write a 00:44:16.450 --> 00:44:19.080 align:start position:0% could be at one so I can still write a modular<00:44:17.080> but<00:44:17.500> I'm<00:44:17.590> not<00:44:17.710> paying<00:44:18.040> the<00:44:18.760> price<00:44:19.060> of 00:44:19.080 --> 00:44:19.090 align:start position:0% modular but I'm not paying the price of 00:44:19.090 --> 00:44:21.720 align:start position:0% modular but I'm not paying the price of a<00:44:19.450> bull<00:44:19.750> call<00:44:20.110> because<00:44:20.620> of<00:44:21.010> load<00:44:21.310> times 00:44:21.720 --> 00:44:21.730 align:start position:0% a bull call because of load times 00:44:21.730 --> 00:44:24.930 align:start position:0% a bull call because of load times there's<00:44:22.570> some<00:44:22.870> hints<00:44:23.440> there<00:44:23.620> saying<00:44:24.010> you<00:44:24.850> know 00:44:24.930 --> 00:44:24.940 align:start position:0% there's some hints there saying you know 00:44:24.940 --> 00:44:26.160 align:start position:0% there's some hints there saying you know this<00:44:25.090> is<00:44:25.150> gonna<00:44:25.300> be<00:44:25.420> probably<00:44:25.570> eventually 00:44:26.160 --> 00:44:26.170 align:start position:0% this is gonna be probably eventually 00:44:26.170 --> 00:44:28.440 align:start position:0% this is gonna be probably eventually been<00:44:26.710> a<00:44:26.740> lot<00:44:26.950> of<00:44:26.980> sectoral<00:44:27.370> month<00:44:27.700> exactly 00:44:28.440 --> 00:44:28.450 align:start position:0% been a lot of sectoral month exactly 00:44:28.450 --> 00:44:30.840 align:start position:0% been a lot of sectoral month exactly like<00:44:28.600> I<00:44:28.720> want<00:44:29.200> to<00:44:29.320> write<00:44:29.650> a<00:44:29.680> module<00:44:30.010> early<00:44:30.580> but 00:44:30.840 --> 00:44:30.850 align:start position:0% like I want to write a module early but 00:44:30.850 --> 00:44:33.240 align:start position:0% like I want to write a module early but I<00:44:30.880> don't<00:44:31.090> want<00:44:31.210> to<00:44:31.240> pay<00:44:31.420> this<00:44:31.570> cost<00:44:31.840> so<00:44:32.170> in<00:44:32.680> - 00:44:33.240 --> 00:44:33.250 align:start position:0% I don't want to pay this cost so in - 00:44:33.250 --> 00:44:36.950 align:start position:0% I don't want to pay this cost so in - cause<00:44:33.810> it<00:44:34.810> seems<00:44:35.080> more<00:44:35.320> like<00:44:35.530> a<00:44:35.790> optimization 00:44:36.950 --> 00:44:36.960 align:start position:0% cause it seems more like a optimization 00:44:36.960 --> 00:44:40.230 align:start position:0% cause it seems more like a optimization the<00:44:37.960> the<00:44:38.350> difference<00:44:38.800> would<00:44:38.950> be<00:44:39.010> events<00:44:39.580> the 00:44:40.230 --> 00:44:40.240 align:start position:0% the the difference would be events the 00:44:40.240 --> 00:44:41.970 align:start position:0% the the difference would be events the summer<00:44:40.420> night<00:44:40.600> there's<00:44:40.900> no<00:44:40.930> in<00:44:41.110> my<00:44:41.260> contract 00:44:41.970 --> 00:44:41.980 align:start position:0% summer night there's no in my contract 00:44:41.980 --> 00:44:44.790 align:start position:0% summer night there's no in my contract okay<00:44:42.400> I'm<00:44:42.850> not<00:44:43.120> in<00:44:43.390> line<00:44:43.630> but<00:44:43.960> the<00:44:44.260> code<00:44:44.470> is<00:44:44.500> not 00:44:44.790 --> 00:44:44.800 align:start position:0% okay I'm not in line but the code is not 00:44:44.800 --> 00:44:46.560 align:start position:0% okay I'm not in line but the code is not in<00:44:45.010> line<00:44:45.190> in<00:44:45.490> the<00:44:45.760> contract<00:44:46.270> it's<00:44:46.450> an 00:44:46.560 --> 00:44:46.570 align:start position:0% in line in the contract it's an 00:44:46.570 --> 00:44:50.310 align:start position:0% in line in the contract it's an indication<00:44:46.990> to<00:44:47.170> the<00:44:47.410> end<00:44:47.940> time<00:44:49.200> so<00:44:50.200> I<00:44:50.230> don't 00:44:50.310 --> 00:44:50.320 align:start position:0% indication to the end time so I don't 00:44:50.320 --> 00:44:52.650 align:start position:0% indication to the end time so I don't pay<00:44:50.560> the<00:44:50.740> cost<00:44:51.010> of<00:44:51.310> this<00:44:51.430> bloated<00:44:51.850> contract 00:44:52.650 --> 00:44:52.660 align:start position:0% pay the cost of this bloated contract 00:44:52.660 --> 00:44:54.270 align:start position:0% pay the cost of this bloated contract but<00:44:52.810> then<00:44:52.990> the<00:44:53.170> others<00:44:53.470> has<00:44:53.650> to<00:44:53.770> be<00:44:53.890> studied 00:44:54.270 --> 00:44:54.280 align:start position:0% but then the others has to be studied 00:44:54.280 --> 00:44:56.610 align:start position:0% but then the others has to be studied for<00:44:54.430> it<00:44:54.550> yes<00:44:55.150> it<00:44:55.690> was<00:44:55.720> but<00:44:56.080> they<00:44:56.230> do<00:44:56.410> make 00:44:56.610 --> 00:44:56.620 align:start position:0% for it yes it was but they do make 00:44:56.620 --> 00:44:59.990 align:start position:0% for it yes it was but they do make medium<00:44:57.280> beta<00:44:57.580> cos<00:44:57.820> it's<00:44:58.090> a<00:44:58.150> widely<00:44:58.560> neglected 00:44:59.990 --> 00:45:00.000 align:start position:0% medium beta cos it's a widely neglected 00:45:00.000 --> 00:45:02.670 align:start position:0% medium beta cos it's a widely neglected I'm<00:45:01.000> paying<00:45:01.300> some<00:45:01.630> overhead<00:45:02.140> costs<00:45:02.560> to 00:45:02.670 --> 00:45:02.680 align:start position:0% I'm paying some overhead costs to 00:45:02.680 --> 00:45:04.770 align:start position:0% I'm paying some overhead costs to indicate<00:45:03.190> in<00:45:03.460> line<00:45:03.730> but<00:45:04.120> I'm<00:45:04.210> not<00:45:04.360> paying 00:45:04.770 --> 00:45:04.780 align:start position:0% indicate in line but I'm not paying 00:45:04.780 --> 00:45:07.050 align:start position:0% indicate in line but I'm not paying I<00:45:04.900> trust<00:45:05.200> everything<00:45:05.470> to<00:45:06.340> the<00:45:06.460> college<00:45:06.880> said 00:45:07.050 --> 00:45:07.060 align:start position:0% I trust everything to the college said 00:45:07.060 --> 00:45:12.910 align:start position:0% I trust everything to the college said it's<00:45:07.990> a<00:45:08.110> one-time<00:45:08.530> I<00:45:08.950> think 00:45:12.910 --> 00:45:12.920 align:start position:0% 00:45:12.920 --> 00:45:16.840 align:start position:0% this<00:45:13.640> may<00:45:14.030> change<00:45:14.860> if<00:45:15.860> I<00:45:15.980> can<00:45:16.190> get<00:45:16.520> not<00:45:16.730> too 00:45:16.840 --> 00:45:16.850 align:start position:0% this may change if I can get not too 00:45:16.850 --> 00:45:20.020 align:start position:0% this may change if I can get not too surprising<00:45:17.360> I'm<00:45:17.540> curious<00:45:17.900> you<00:45:18.440> should<00:45:19.430> times 00:45:20.020 --> 00:45:20.030 align:start position:0% surprising I'm curious you should times 00:45:20.030 --> 00:45:22.090 align:start position:0% surprising I'm curious you should times there<00:45:20.360> about<00:45:20.660> what<00:45:20.900> the<00:45:21.080> two<00:45:21.260> seconds<00:45:21.770> for<00:45:22.070> a 00:45:22.090 --> 00:45:22.100 align:start position:0% there about what the two seconds for a 00:45:22.100 --> 00:45:43.280 align:start position:0% there about what the two seconds for a block<00:45:22.430> full<00:45:22.700> of<00:45:22.850> these<00:45:23.270> we 00:45:43.280 --> 00:45:43.290 align:start position:0% 00:45:43.290 --> 00:46:34.470 align:start position:0% in<00:45:44.290> this<00:45:44.530> case<00:45:46.110> and<00:45:47.110> I<00:45:56.670> explained<00:46:33.300> then<00:46:34.300> we 00:46:34.470 --> 00:46:34.480 align:start position:0% in this case and I explained then we 00:46:34.480 --> 00:46:36.240 align:start position:0% in this case and I explained then we shouldn't<00:46:35.200> really<00:46:35.350> be<00:46:35.470> written<00:46:35.860> about<00:46:35.950> verse 00:46:36.240 --> 00:46:36.250 align:start position:0% shouldn't really be written about verse 00:46:36.250 --> 00:46:37.650 align:start position:0% shouldn't really be written about verse 1<00:46:36.490> because<00:46:36.790> they<00:46:37.090> could<00:46:37.300> just<00:46:37.420> write<00:46:37.540> the 00:46:37.650 --> 00:46:37.660 align:start position:0% 1 because they could just write the 00:46:37.660 --> 00:46:51.890 align:start position:0% 1 because they could just write the other<00:46:37.780> thing<00:46:38.050> which<00:46:38.200> would<00:46:38.320> be<00:46:38.410> worse<00:46:38.530> for<00:46:38.590> us 00:46:51.890 --> 00:46:51.900 align:start position:0% 00:46:51.900 --> 00:47:19.950 align:start position:0% I<00:46:57.150> actually<00:47:18.119> already<00:47:19.119> have<00:47:19.270> one<00:47:19.540> so<00:47:19.569> we<00:47:19.809> should 00:47:19.950 --> 00:47:19.960 align:start position:0% I actually already have one so we should 00:47:19.960 --> 00:47:21.870 align:start position:0% I actually already have one so we should be<00:47:19.990> getting<00:47:20.170> pretty<00:47:20.380> much<00:47:20.589> but<00:47:21.040> that<00:47:21.760> we 00:47:21.870 --> 00:47:21.880 align:start position:0% be getting pretty much but that we 00:47:21.880 --> 00:47:26.940 align:start position:0% be getting pretty much but that we wouldn't<00:47:22.089> be<00:47:22.150> making<00:47:22.210> things<00:47:22.660> worse<00:47:25.770> once<00:47:26.770> we 00:47:26.940 --> 00:47:26.950 align:start position:0% wouldn't be making things worse once we 00:47:26.950 --> 00:47:29.130 align:start position:0% wouldn't be making things worse once we get<00:47:27.069> rid<00:47:27.130> of<00:47:27.339> those<00:47:27.579> so<00:47:28.420> they<00:47:28.569> will<00:47:28.750> go<00:47:28.900> back<00:47:28.930> to 00:47:29.130 --> 00:47:29.140 align:start position:0% get rid of those so they will go back to 00:47:29.140 --> 00:47:32.490 align:start position:0% get rid of those so they will go back to that<00:47:29.319> one<00:47:30.099> so<00:47:30.250> I'm<00:47:30.400> asking<00:47:31.119> how<00:47:31.690> far<00:47:31.720> away<00:47:32.319> this 00:47:32.490 --> 00:47:32.500 align:start position:0% that one so I'm asking how far away this 00:47:32.500 --> 00:47:35.490 align:start position:0% that one so I'm asking how far away this is<00:47:32.559> from<00:47:33.010> a<00:47:33.099> reasonable<00:47:33.609> position<00:47:34.200> well<00:47:35.200> I 00:47:35.490 --> 00:47:35.500 align:start position:0% is from a reasonable position well I 00:47:35.500 --> 00:47:38.040 align:start position:0% is from a reasonable position well I mean<00:47:35.920> I<00:47:35.980> think<00:47:36.190> we<00:47:36.700> can<00:47:36.849> go<00:47:37.030> in<00:47:37.329> that<00:47:37.599> general 00:47:38.040 --> 00:47:38.050 align:start position:0% mean I think we can go in that general 00:47:38.050 --> 00:47:39.319 align:start position:0% mean I think we can go in that general direction 00:47:39.319 --> 00:47:39.329 align:start position:0% direction 00:47:39.329 --> 00:47:44.280 align:start position:0% direction but<00:47:40.829> we<00:47:41.829> kept<00:47:42.069> like<00:47:42.309> pretend<00:47:43.000> that<00:47:43.510> the<00:47:43.960> call 00:47:44.280 --> 00:47:44.290 align:start position:0% but we kept like pretend that the call 00:47:44.290 --> 00:47:47.900 align:start position:0% but we kept like pretend that the call is<00:47:44.760> equivalent<00:47:45.760> to<00:47:46.000> a<00:47:46.420> jump<00:47:46.720> because<00:47:47.410> it<00:47:47.680> is 00:47:47.900 --> 00:47:47.910 align:start position:0% is equivalent to a jump because it is 00:47:47.910 --> 00:47:50.880 align:start position:0% is equivalent to a jump because it is very<00:47:48.910> middle<00:47:49.329> but<00:47:49.660> I<00:47:50.109> don't<00:47:50.349> think<00:47:50.500> it's<00:47:50.710> ever 00:47:50.880 --> 00:47:50.890 align:start position:0% very middle but I don't think it's ever 00:47:50.890 --> 00:47:52.920 align:start position:0% very middle but I don't think it's ever I<00:47:51.400> don't<00:47:51.490> think<00:47:51.640> a<00:47:51.819> cool<00:47:51.970> to<00:47:52.180> Sophos<00:47:52.569> what's<00:47:52.780> a 00:47:52.920 --> 00:47:52.930 align:start position:0% I don't think a cool to Sophos what's a 00:47:52.930 --> 00:47:53.400 align:start position:0% I don't think a cool to Sophos what's a matter 00:47:53.400 --> 00:47:53.410 align:start position:0% matter 00:47:53.410 --> 00:47:55.680 align:start position:0% matter so<00:47:53.740> this<00:47:53.980> is<00:47:54.190> is<00:47:54.520> this<00:47:54.760> suggesting<00:47:55.329> that<00:47:55.540> it 00:47:55.680 --> 00:47:55.690 align:start position:0% so this is is this suggesting that it 00:47:55.690 --> 00:48:00.720 align:start position:0% so this is is this suggesting that it would<00:47:55.780> be<00:47:56.880> resisted<00:47:57.880> using<00:47:58.240> muscle<00:47:59.170> 14<00:47:59.730> yeah 00:48:00.720 --> 00:48:00.730 align:start position:0% would be resisted using muscle 14 yeah 00:48:00.730 --> 00:48:15.630 align:start position:0% would be resisted using muscle 14 yeah yeah<00:48:01.030> so<00:48:05.760> yeah 00:48:15.630 --> 00:48:15.640 align:start position:0% 00:48:15.640 --> 00:48:18.000 align:start position:0% [Music] 00:48:18.000 --> 00:48:18.010 align:start position:0% [Music] 00:48:18.010 --> 00:48:20.190 align:start position:0% [Music] but<00:48:18.310> anyway<00:48:18.850> this<00:48:19.000> is<00:48:19.150> only<00:48:19.240> for<00:48:19.480> call<00:48:19.720> to<00:48:19.900> self 00:48:20.190 --> 00:48:20.200 align:start position:0% but anyway this is only for call to self 00:48:20.200 --> 00:48:24.630 align:start position:0% but anyway this is only for call to self which<00:48:20.740> was<00:48:20.980> motivated<00:48:21.670> by<00:48:21.700> Viper<00:48:22.630> and<00:48:23.640> Viper 00:48:24.630 --> 00:48:24.640 align:start position:0% which was motivated by Viper and Viper 00:48:24.640 --> 00:48:29.640 align:start position:0% which was motivated by Viper and Viper initially<00:48:27.240> for<00:48:28.240> every<00:48:28.630> single<00:48:29.140> functional 00:48:29.640 --> 00:48:29.650 align:start position:0% initially for every single functional 00:48:29.650 --> 00:48:31.620 align:start position:0% initially for every single functional defining<00:48:30.130> writer<00:48:30.369> it<00:48:30.880> would<00:48:31.119> do<00:48:31.240> an<00:48:31.390> external 00:48:31.620 --> 00:48:31.630 align:start position:0% defining writer it would do an external 00:48:31.630 --> 00:48:34.020 align:start position:0% defining writer it would do an external call<00:48:31.990> so<00:48:32.740> that<00:48:32.770> to<00:48:33.010> make<00:48:33.190> those<00:48:33.580> functions 00:48:34.020 --> 00:48:34.030 align:start position:0% call so that to make those functions 00:48:34.030 --> 00:48:37.560 align:start position:0% call so that to make those functions fully<00:48:34.300> pure<00:48:35.310> and<00:48:36.310> this<00:48:36.520> has<00:48:36.730> changed<00:48:36.760> I 00:48:37.560 --> 00:48:37.570 align:start position:0% fully pure and this has changed I 00:48:37.570 --> 00:48:39.510 align:start position:0% fully pure and this has changed I believe<00:48:37.869> last<00:48:38.500> year<00:48:38.680> in<00:48:38.890> the<00:48:38.980> classroom<00:48:39.369> this 00:48:39.510 --> 00:48:39.520 align:start position:0% believe last year in the classroom this 00:48:39.520 --> 00:48:42.290 align:start position:0% believe last year in the classroom this year<00:48:39.760> and<00:48:40.359> the<00:48:40.720> writer<00:48:41.050> is<00:48:41.290> also<00:48:41.500> using<00:48:41.890> jumps 00:48:42.290 --> 00:48:42.300 align:start position:0% year and the writer is also using jumps 00:48:42.300 --> 00:48:45.960 align:start position:0% year and the writer is also using jumps for<00:48:43.300> internal<00:48:43.750> calls<00:48:43.990> because<00:48:44.410> obviously<00:48:44.970> we 00:48:45.960 --> 00:48:45.970 align:start position:0% for internal calls because obviously we 00:48:45.970 --> 00:48:50.550 align:start position:0% for internal calls because obviously we want<00:48:46.150> people<00:48:46.300> to<00:48:46.480> use<00:48:46.570> the<00:48:46.840> language<00:48:49.500> so<00:48:50.500> the 00:48:50.550 --> 00:48:50.560 align:start position:0% want people to use the language so the 00:48:50.560 --> 00:48:52.440 align:start position:0% want people to use the language so the motivation<00:48:50.830> of<00:48:51.010> this<00:48:51.250> proposal<00:48:51.850> was<00:48:52.119> to 00:48:52.440 --> 00:48:52.450 align:start position:0% motivation of this proposal was to 00:48:52.450 --> 00:48:55.260 align:start position:0% motivation of this proposal was to reduce<00:48:53.200> the<00:48:53.260> call<00:48:53.590> to<00:48:53.740> self<00:48:54.010> so<00:48:54.880> that<00:48:54.910> Viper 00:48:55.260 --> 00:48:55.270 align:start position:0% reduce the call to self so that Viper 00:48:55.270 --> 00:48:58.910 align:start position:0% reduce the call to self so that Viper could<00:48:56.200> could<00:48:56.619> keep<00:48:56.830> using<00:48:57.100> this<00:48:57.550> safer<00:48:58.330> method 00:48:58.910 --> 00:48:58.920 align:start position:0% could could keep using this safer method 00:48:58.920 --> 00:49:01.830 align:start position:0% could could keep using this safer method fewer<00:48:59.920> functions<00:49:00.400> and<00:49:00.609> also<00:49:01.240> suddenly<00:49:01.720> they 00:49:01.830 --> 00:49:01.840 align:start position:0% fewer functions and also suddenly they 00:49:01.840 --> 00:49:04.740 align:start position:0% fewer functions and also suddenly they could<00:49:01.990> start<00:49:02.200> using<00:49:02.350> them<00:49:02.650> exactly<00:49:03.340> I<00:49:04.119> mean 00:49:04.740 --> 00:49:04.750 align:start position:0% could start using them exactly I mean 00:49:04.750 --> 00:49:06.510 align:start position:0% could start using them exactly I mean I'm<00:49:04.990> not<00:49:05.109> a<00:49:05.170> big<00:49:05.440> fan<00:49:05.740> of<00:49:05.770> that<00:49:05.920> because<00:49:06.220> it 00:49:06.510 --> 00:49:06.520 align:start position:0% I'm not a big fan of that because it 00:49:06.520 --> 00:49:08.130 align:start position:0% I'm not a big fan of that because it requires<00:49:06.910> you<00:49:07.030> to<00:49:07.060> serialize<00:49:07.600> your<00:49:07.960> whole 00:49:08.130 --> 00:49:08.140 align:start position:0% requires you to serialize your whole 00:49:08.140 --> 00:49:10.109 align:start position:0% requires you to serialize your whole documents<00:49:08.680> retirement<00:49:09.250> in<00:49:09.340> AC<00:49:09.520> realize<00:49:09.910> that 00:49:10.109 --> 00:49:10.119 align:start position:0% documents retirement in AC realize that 00:49:10.119 --> 00:49:12.390 align:start position:0% documents retirement in AC realize that we<00:49:10.180> say<00:49:10.359> even<00:49:11.140> if<00:49:11.200> for<00:49:11.500> self<00:49:11.800> switching 00:49:12.390 --> 00:49:12.400 align:start position:0% we say even if for self switching 00:49:12.400 --> 00:49:13.160 align:start position:0% we say even if for self switching problems 00:49:13.160 --> 00:49:13.170 align:start position:0% problems 00:49:13.170 --> 00:49:16.870 align:start position:0% problems [Music] 00:49:16.870 --> 00:49:16.880 align:start position:0% 00:49:16.880 --> 00:49:20.390 align:start position:0% especially<00:49:17.880> say<00:49:18.059> this<00:49:18.239> conflict<00:49:19.249> buddy<00:49:20.249> I 00:49:20.390 --> 00:49:20.400 align:start position:0% especially say this conflict buddy I 00:49:20.400 --> 00:49:23.259 align:start position:0% especially say this conflict buddy I mean<00:49:20.609> you<00:49:20.910> would<00:49:21.089> have<00:49:21.119> to<00:49:21.420> navigate<00:49:22.259> the<00:49:22.529> home 00:49:23.259 --> 00:49:23.269 align:start position:0% mean you would have to navigate the home 00:49:23.269 --> 00:49:28.459 align:start position:0% mean you would have to navigate the home 63-64<00:49:24.269> throws<00:49:24.630> which<00:49:24.959> would<00:49:25.229> cause<00:49:25.859> issues<00:49:27.469> so 00:49:28.459 --> 00:49:28.469 align:start position:0% 63-64 throws which would cause issues so 00:49:28.469 --> 00:49:30.499 align:start position:0% 63-64 throws which would cause issues so every<00:49:29.160> time<00:49:29.309> you<00:49:29.400> make<00:49:29.549> a<00:49:29.579> call<00:49:29.880> you<00:49:30.209> can<00:49:30.390> only 00:49:30.499 --> 00:49:30.509 align:start position:0% every time you make a call you can only 00:49:30.509 --> 00:49:33.319 align:start position:0% every time you make a call you can only send<00:49:31.170> along<00:49:31.549> maximal<00:49:32.549> sixty<00:49:33.029> three<00:49:33.299> sixty 00:49:33.319 --> 00:49:33.329 align:start position:0% send along maximal sixty three sixty 00:49:33.329 --> 00:49:36.769 align:start position:0% send along maximal sixty three sixty fourths<00:49:34.140> of<00:49:34.259> the<00:49:34.380> gas<00:49:34.769> that<00:49:35.039> you<00:49:35.099> have<00:49:35.779> which 00:49:36.769 --> 00:49:36.779 align:start position:0% fourths of the gas that you have which 00:49:36.779 --> 00:49:40.219 align:start position:0% fourths of the gas that you have which makes<00:49:37.229> it<00:49:37.499> practically<00:49:38.660> impossible<00:49:39.660> to 00:49:40.219 --> 00:49:40.229 align:start position:0% makes it practically impossible to 00:49:40.229 --> 00:49:47.930 align:start position:0% makes it practically impossible to breathe<00:49:40.880> or<00:49:41.880> recursion<00:49:42.719> record<00:49:43.469> up<00:49:46.940> something 00:49:47.930 --> 00:49:47.940 align:start position:0% breathe or recursion record up something 00:49:47.940 --> 00:49:58.609 align:start position:0% breathe or recursion record up something like<00:49:52.130> yeah<00:49:55.880> and<00:49:56.880> that<00:49:57.059> so<00:49:57.539> the<00:49:57.900> conflict<00:49:58.410> which 00:49:58.609 --> 00:49:58.619 align:start position:0% like yeah and that so the conflict which 00:49:58.619 --> 00:50:01.849 align:start position:0% like yeah and that so the conflict which is<00:49:59.249> in<00:50:00.150> the<00:50:00.479> contract<00:50:01.019> world<00:50:01.349> where 00:50:01.849 --> 00:50:01.859 align:start position:0% is in the contract world where 00:50:01.859 --> 00:50:03.739 align:start position:0% is in the contract world where everything<00:50:02.309> is<00:50:02.339> based<00:50:02.849> on<00:50:03.059> causes<00:50:03.509> little 00:50:03.739 --> 00:50:03.749 align:start position:0% everything is based on causes little 00:50:03.749 --> 00:50:09.170 align:start position:0% everything is based on causes little jumps<00:50:04.160> that<00:50:05.160> can<00:50:05.400> be<00:50:05.519> problematic<00:50:08.059> on<00:50:09.059> the 00:50:09.170 --> 00:50:09.180 align:start position:0% jumps that can be problematic on the 00:50:09.180 --> 00:50:12.049 align:start position:0% jumps that can be problematic on the belt<00:50:09.329> of<00:50:09.450> series<00:50:09.809> ation<00:50:10.400> so<00:50:11.400> we<00:50:11.549> do<00:50:11.729> have<00:50:11.880> like 00:50:12.049 --> 00:50:12.059 align:start position:0% belt of series ation so we do have like 00:50:12.059 --> 00:50:15.529 align:start position:0% belt of series ation so we do have like the<00:50:12.180> EBI<00:50:12.450> including<00:50:13.940> across<00:50:14.940> different 00:50:15.529 --> 00:50:15.539 align:start position:0% the EBI including across different 00:50:15.539 --> 00:50:17.089 align:start position:0% the EBI including across different contracts<00:50:15.989> but<00:50:16.469> if<00:50:16.559> you're<00:50:16.709> calling<00:50:17.009> yourself 00:50:17.089 --> 00:50:17.099 align:start position:0% contracts but if you're calling yourself 00:50:17.099 --> 00:50:20.239 align:start position:0% contracts but if you're calling yourself you<00:50:17.969> may<00:50:18.119> not<00:50:18.329> not<00:50:18.930> be<00:50:19.079> to<00:50:19.259> use<00:50:19.380> it<00:50:19.559> you<00:50:19.859> can<00:50:19.890> use 00:50:20.239 --> 00:50:20.249 align:start position:0% you may not not be to use it you can use 00:50:20.249 --> 00:50:22.489 align:start position:0% you may not not be to use it you can use your<00:50:20.519> own<00:50:20.789> wizard<00:50:21.660> main<00:50:21.839> match<00:50:22.049> to<00:50:22.229> man<00:50:22.349> but 00:50:22.489 --> 00:50:22.499 align:start position:0% your own wizard main match to man but 00:50:22.499 --> 00:50:25.339 align:start position:0% your own wizard main match to man but you<00:50:22.619> do<00:50:22.829> still<00:50:22.890> need<00:50:23.420> things<00:50:24.420> much<00:50:24.779> like<00:50:25.170> if 00:50:25.339 --> 00:50:25.349 align:start position:0% you do still need things much like if 00:50:25.349 --> 00:50:30.970 align:start position:0% you do still need things much like if you've<00:50:25.469> got<00:50:25.680> a<00:50:25.709> data<00:50:25.949> structure<00:50:26.279> that 00:50:30.970 --> 00:50:30.980 align:start position:0% 00:50:30.980 --> 00:50:42.370 align:start position:0% yeah 00:50:42.370 --> 00:50:42.380 align:start position:0% 00:50:42.380 --> 00:50:49.090 align:start position:0% [Music] 00:50:49.090 --> 00:50:49.100 align:start position:0% 00:50:49.100 --> 00:51:17.090 align:start position:0% [Music] 00:51:17.090 --> 00:51:17.100 align:start position:0% 00:51:17.100 --> 00:51:40.860 align:start position:0% [Music] 00:51:40.860 --> 00:51:40.870 align:start position:0% 00:51:40.870 --> 00:51:50.770 align:start position:0% parents<00:51:47.590> okay<00:51:48.590> said<00:51:48.800> that<00:51:48.920> that's<00:51:49.600> just<00:51:50.600> what 00:51:50.770 --> 00:51:50.780 align:start position:0% parents okay said that that's just what 00:51:50.780 --> 00:51:53.260 align:start position:0% parents okay said that that's just what was<00:51:50.900> in<00:51:50.990> the<00:51:51.080> under<00:51:51.470> call<00:51:51.740> called<00:51:52.730> yourself<00:51:53.120> a 00:51:53.260 --> 00:51:53.270 align:start position:0% was in the under call called yourself a 00:51:53.270 --> 00:51:54.790 align:start position:0% was in the under call called yourself a new<00:51:53.390> free<00:51:53.570> starting<00:51:53.960> to<00:51:54.110> stand<00:51:54.290> up<00:51:54.440> good<00:51:54.620> for 00:51:54.790 --> 00:51:54.800 align:start position:0% new free starting to stand up good for 00:51:54.800 --> 00:51:56.620 align:start position:0% new free starting to stand up good for that<00:51:54.920> then<00:51:55.760> we<00:51:55.910> really<00:51:56.210> made<00:51:56.360> it<00:51:56.390> a<00:51:56.600> very 00:51:56.620 --> 00:51:56.630 align:start position:0% that then we really made it a very 00:51:56.630 --> 00:51:59.560 align:start position:0% that then we really made it a very specific<00:51:57.500> case<00:51:57.830> but<00:51:58.250> earlier<00:51:59.090> on<00:51:59.270> we<00:51:59.450> also 00:51:59.560 --> 00:51:59.570 align:start position:0% specific case but earlier on we also 00:51:59.570 --> 00:52:01.320 align:start position:0% specific case but earlier on we also said<00:51:59.900> that<00:52:00.050> this<00:52:00.200> between<00:52:00.620> more<00:52:00.770> generalized 00:52:01.320 --> 00:52:01.330 align:start position:0% said that this between more generalized 00:52:01.330 --> 00:52:06.280 align:start position:0% said that this between more generalized outside<00:52:02.330> of<00:52:02.540> all<00:52:02.750> to<00:52:02.870> sell<00:52:03.080> and<00:52:04.090> to<00:52:05.090> disk<00:52:06.020> and 00:52:06.280 --> 00:52:06.290 align:start position:0% outside of all to sell and to disk and 00:52:06.290 --> 00:52:08.080 align:start position:0% outside of all to sell and to disk and calls<00:52:06.710> to<00:52:06.980> contracts<00:52:07.520> which<00:52:07.640> were<00:52:07.790> already 00:52:08.080 --> 00:52:08.090 align:start position:0% calls to contracts which were already 00:52:08.090 --> 00:52:10.979 align:start position:0% calls to contracts which were already called<00:52:08.830> in 00:52:10.979 --> 00:52:10.989 align:start position:0% called in 00:52:10.989 --> 00:52:14.920 align:start position:0% called in execution<00:52:11.989> and<00:52:13.089> that's<00:52:14.089> that's<00:52:14.539> the<00:52:14.779> one 00:52:14.920 --> 00:52:14.930 align:start position:0% execution and that's that's the one 00:52:14.930 --> 00:52:16.179 align:start position:0% execution and that's that's the one which<00:52:15.079> would<00:52:15.229> be<00:52:15.349> useful<00:52:15.529> if<00:52:15.829> you<00:52:15.949> want<00:52:16.069> to 00:52:16.179 --> 00:52:16.189 align:start position:0% which would be useful if you want to 00:52:16.189 --> 00:52:17.890 align:start position:0% which would be useful if you want to have<00:52:16.309> more<00:52:16.489> model<00:52:16.849> contracts<00:52:17.539> to<00:52:17.809> your 00:52:17.890 --> 00:52:17.900 align:start position:0% have more model contracts to your 00:52:17.900 --> 00:52:19.440 align:start position:0% have more model contracts to your libraries 00:52:19.440 --> 00:52:19.450 align:start position:0% libraries 00:52:19.450 --> 00:52:28.540 align:start position:0% libraries [Music] 00:52:28.540 --> 00:52:28.550 align:start position:0% 00:52:28.550 --> 00:52:33.190 align:start position:0% [Music] 00:52:33.190 --> 00:52:33.200 align:start position:0% 00:52:33.200 --> 00:52:35.349 align:start position:0% so<00:52:33.770> you<00:52:34.220> guys<00:52:34.400> giving<00:52:34.760> any<00:52:34.970> issues 00:52:35.349 --> 00:52:35.359 align:start position:0% so you guys giving any issues 00:52:35.359 --> 00:52:40.030 align:start position:0% so you guys giving any issues considering<00:52:36.290> this<00:52:37.220> more<00:52:37.400> generative<00:52:37.760> case<00:52:39.040> is 00:52:40.030 --> 00:52:40.040 align:start position:0% considering this more generative case is 00:52:40.040 --> 00:52:41.589 align:start position:0% considering this more generative case is questioning<00:52:40.849> you<00:52:40.970> need<00:52:41.150> to<00:52:41.270> do<00:52:41.390> a<00:52:41.420> bit<00:52:41.569> of 00:52:41.589 --> 00:52:41.599 align:start position:0% questioning you need to do a bit of 00:52:41.599 --> 00:52:44.170 align:start position:0% questioning you need to do a bit of analysis<00:52:41.839> on<00:52:42.319> how<00:52:42.710> much<00:52:42.950> can<00:52:43.280> usually<00:52:43.490> be 00:52:44.170 --> 00:52:44.180 align:start position:0% analysis on how much can usually be 00:52:44.180 --> 00:52:46.690 align:start position:0% analysis on how much can usually be enough<00:52:44.390> attention<00:52:44.930> to<00:52:44.960> load<00:52:45.230> into<00:52:45.500> hurry<00:52:45.829> like 00:52:46.690 --> 00:52:46.700 align:start position:0% enough attention to load into hurry like 00:52:46.700 --> 00:52:49.089 align:start position:0% enough attention to load into hurry like tech<00:52:47.480> square<00:52:47.780> shows<00:52:48.170> the<00:52:48.290> number<00:52:48.530> of<00:52:48.589> was<00:52:48.890> your 00:52:49.089 --> 00:52:49.099 align:start position:0% tech square shows the number of was your 00:52:49.099 --> 00:52:57.170 align:start position:0% tech square shows the number of was your banking<00:52:49.460> everybody<00:52:50.240> contract<00:52:50.660> seventy<00:52:50.990> times 00:52:57.170 --> 00:52:57.180 align:start position:0% 00:52:57.180 --> 00:53:01.880 align:start position:0% because<00:52:57.980> BVM<00:52:58.980> intention<00:52:59.640> has<00:52:59.880> to<00:53:00.030> be 00:53:01.880 --> 00:53:01.890 align:start position:0% because BVM intention has to be 00:53:01.890 --> 00:53:04.760 align:start position:0% because BVM intention has to be I<00:53:02.240> occasionally<00:53:03.240> if<00:53:03.900> we<00:53:04.080> featured<00:53:04.440> a 00:53:04.760 --> 00:53:04.770 align:start position:0% I occasionally if we featured a 00:53:04.770 --> 00:53:08.660 align:start position:0% I occasionally if we featured a technologist<00:53:05.640> over<00:53:05.940> education 00:53:08.660 --> 00:53:08.670 align:start position:0% 00:53:08.670 --> 00:53:10.339 align:start position:0% choose<00:53:08.910> a<00:53:08.940> recipe<00:53:09.269> it<00:53:09.539> seems<00:53:09.779> like<00:53:09.990> if<00:53:10.140> that's 00:53:10.339 --> 00:53:10.349 align:start position:0% choose a recipe it seems like if that's 00:53:10.349 --> 00:53:14.070 align:start position:0% choose a recipe it seems like if that's a<00:53:10.500> nice<00:53:10.740> meal 00:53:14.070 --> 00:53:14.080 align:start position:0% 00:53:14.080 --> 00:53:17.130 align:start position:0% so<00:53:15.080> an<00:53:15.260> interesting<00:53:15.740> case<00:53:15.890> there<00:53:16.160> is<00:53:16.430> you<00:53:17.060> have 00:53:17.130 --> 00:53:17.140 align:start position:0% so an interesting case there is you have 00:53:17.140 --> 00:53:19.359 align:start position:0% so an interesting case there is you have given<00:53:18.140> contract<00:53:18.740> to<00:53:18.890> use<00:53:19.010> a<00:53:19.040> bunch<00:53:19.310> of 00:53:19.359 --> 00:53:19.369 align:start position:0% given contract to use a bunch of 00:53:19.369 --> 00:53:21.130 align:start position:0% given contract to use a bunch of librarians<00:53:19.790> to<00:53:19.970> keep<00:53:20.150> pulling<00:53:20.480> them<00:53:20.660> you 00:53:21.130 --> 00:53:21.140 align:start position:0% librarians to keep pulling them you 00:53:21.140 --> 00:53:23.290 align:start position:0% librarians to keep pulling them you catch<00:53:21.349> the<00:53:21.500> top<00:53:21.740> them<00:53:21.980> and<00:53:22.190> I<00:53:22.640> applied<00:53:23.060> to<00:53:23.270> a 00:53:23.290 --> 00:53:23.300 align:start position:0% catch the top them and I applied to a 00:53:23.300 --> 00:53:27.550 align:start position:0% catch the top them and I applied to a brand<00:53:23.570> new<00:53:23.660> contract<00:53:25.840> and<00:53:26.840> then<00:53:27.109> you<00:53:27.380> want 00:53:27.550 --> 00:53:27.560 align:start position:0% brand new contract and then you want 00:53:27.560 --> 00:53:29.470 align:start position:0% brand new contract and then you want also<00:53:27.800> catch<00:53:28.070> stuff<00:53:28.730> which<00:53:29.180> is<00:53:29.330> happening 00:53:29.470 --> 00:53:29.480 align:start position:0% also catch stuff which is happening 00:53:29.480 --> 00:53:30.099 align:start position:0% also catch stuff which is happening there 00:53:30.099 --> 00:53:30.109 align:start position:0% there 00:53:30.109 --> 00:53:47.920 align:start position:0% there I<00:53:32.230> knew<00:53:33.230> I<00:53:33.740> mean<00:53:45.940> should<00:53:46.940> that<00:53:47.180> be<00:53:47.330> the<00:53:47.359> case<00:53:47.660> or 00:53:47.920 --> 00:53:47.930 align:start position:0% I knew I mean should that be the case or 00:53:47.930 --> 00:53:56.880 align:start position:0% I knew I mean should that be the case or shouldn't<00:53:48.560> you<00:53:48.710> be<00:53:48.859> able<00:53:48.920> to<00:53:49.099> reuse<00:53:49.460> that 00:53:56.880 --> 00:53:56.890 align:start position:0% 00:53:56.890 --> 00:54:01.030 align:start position:0% system<00:53:57.890> I<00:53:58.900> mean<00:53:59.900> I<00:53:59.990> really<00:54:00.230> like<00:54:00.320> the<00:54:00.380> idea<00:54:00.530> but 00:54:01.030 --> 00:54:01.040 align:start position:0% system I mean I really like the idea but 00:54:01.040 --> 00:54:02.859 align:start position:0% system I mean I really like the idea but I'm<00:54:01.160> really<00:54:01.280> worried<00:54:02.090> that<00:54:02.119> it's<00:54:02.480> gonna<00:54:02.599> pull 00:54:02.859 --> 00:54:02.869 align:start position:0% I'm really worried that it's gonna pull 00:54:02.869 --> 00:54:04.240 align:start position:0% I'm really worried that it's gonna pull it<00:54:02.960> to<00:54:03.050> the<00:54:03.080> same<00:54:03.349> problem<00:54:03.710> system<00:54:04.099> s 00:54:04.240 --> 00:54:04.250 align:start position:0% it to the same problem system s 00:54:04.250 --> 00:54:05.800 align:start position:0% it to the same problem system s customers<00:54:04.640> that<00:54:04.849> gas<00:54:05.060> means<00:54:05.240> no<00:54:05.420> nominee 00:54:05.800 --> 00:54:05.810 align:start position:0% customers that gas means no nominee 00:54:05.810 --> 00:54:07.420 align:start position:0% customers that gas means no nominee repeat<00:54:06.200> old<00:54:06.380> specifically<00:54:07.040> that<00:54:07.220> the 00:54:07.420 --> 00:54:07.430 align:start position:0% repeat old specifically that the 00:54:07.430 --> 00:54:12.070 align:start position:0% repeat old specifically that the realization<00:54:10.390> history<00:54:11.390> imprints<00:54:11.810> the<00:54:11.900> issue 00:54:12.070 --> 00:54:12.080 align:start position:0% realization history imprints the issue 00:54:12.080 --> 00:54:16.720 align:start position:0% realization history imprints the issue but<00:54:14.530> apart<00:54:15.530> from<00:54:15.619> do<00:54:15.859> me<00:54:15.980> in<00:54:16.070> transient<00:54:16.580> was 00:54:16.720 --> 00:54:16.730 align:start position:0% but apart from do me in transient was 00:54:16.730 --> 00:54:18.520 align:start position:0% but apart from do me in transient was just<00:54:17.030> quite<00:54:17.390> complex<00:54:17.930> and<00:54:18.109> there<00:54:18.260> were<00:54:18.349> so 00:54:18.520 --> 00:54:18.530 align:start position:0% just quite complex and there were so 00:54:18.530 --> 00:54:22.270 align:start position:0% just quite complex and there were so many<00:54:18.589> versions<00:54:18.859> of<00:54:19.190> that<00:54:19.339> basket<00:54:19.810> and<00:54:21.280> it's 00:54:22.270 --> 00:54:22.280 align:start position:0% many versions of that basket and it's 00:54:22.280 --> 00:54:28.180 align:start position:0% many versions of that basket and it's forever<00:54:25.570> and<00:54:26.570> even<00:54:26.869> in<00:54:26.990> the<00:54:27.170> the<00:54:27.619> last<00:54:27.800> heart 00:54:28.180 --> 00:54:28.190 align:start position:0% forever and even in the the last heart 00:54:28.190 --> 00:54:31.410 align:start position:0% forever and even in the the last heart fork<00:54:28.550> on<00:54:29.300> coming<00:54:30.290> up<00:54:30.380> to<00:54:30.530> this<00:54:30.680> and<00:54:30.920> will 00:54:31.410 --> 00:54:31.420 align:start position:0% fork on coming up to this and will 00:54:31.420 --> 00:54:35.069 align:start position:0% fork on coming up to this and will guess<00:54:31.839> we<00:54:31.990> drink<00:54:32.910> it<00:54:33.910> seems<00:54:34.180> to<00:54:34.299> be<00:54:34.390> hard<00:54:34.660> to<00:54:34.809> to 00:54:35.069 --> 00:54:35.079 align:start position:0% guess we drink it seems to be hard to to 00:54:35.079 --> 00:54:36.539 align:start position:0% guess we drink it seems to be hard to to get<00:54:35.230> people<00:54:35.589> to<00:54:35.680> write<00:54:35.859> down<00:54:36.040> a<00:54:36.190> key<00:54:36.430> of 00:54:36.539 --> 00:54:36.549 align:start position:0% get people to write down a key of 00:54:36.549 --> 00:54:38.520 align:start position:0% get people to write down a key of specification<00:54:37.119> and<00:54:37.510> beer<00:54:37.780> tyskie<00:54:37.990> the<00:54:38.200> story 00:54:38.520 --> 00:54:38.530 align:start position:0% specification and beer tyskie the story 00:54:38.530 --> 00:54:40.530 align:start position:0% specification and beer tyskie the story and<00:54:39.010> I<00:54:39.099> mean<00:54:39.220> I<00:54:39.339> wrote<00:54:39.849> the<00:54:40.030> very<00:54:40.210> first 00:54:40.530 --> 00:54:40.540 align:start position:0% and I mean I wrote the very first 00:54:40.540 --> 00:54:42.569 align:start position:0% and I mean I wrote the very first petition<00:54:40.809> against<00:54:41.349> metering<00:54:41.799> and<00:54:42.010> with 00:54:42.569 --> 00:54:42.579 align:start position:0% petition against metering and with 00:54:42.579 --> 00:54:44.160 align:start position:0% petition against metering and with respect<00:54:42.940> I<00:54:43.030> wish<00:54:43.180> at<00:54:43.329> least<00:54:43.510> focused<00:54:43.990> on 00:54:44.160 --> 00:54:44.170 align:start position:0% respect I wish at least focused on 00:54:44.170 --> 00:54:46.380 align:start position:0% respect I wish at least focused on trying<00:54:44.380> to<00:54:44.470> get<00:54:44.619> me<00:54:44.890> think<00:54:45.220> it's<00:54:45.460> to<00:54:45.849> exactly 00:54:46.380 --> 00:54:46.390 align:start position:0% trying to get me think it's to exactly 00:54:46.390 --> 00:54:48.480 align:start position:0% trying to get me think it's to exactly reflect<00:54:46.839> what<00:54:47.170> the<00:54:47.440> airdrome<00:54:47.680> culture<00:54:48.160> and 00:54:48.480 --> 00:54:48.490 align:start position:0% reflect what the airdrome culture and 00:54:48.490 --> 00:54:51.170 align:start position:0% reflect what the airdrome culture and morale<00:54:49.119> just<00:54:49.329> Simone 00:54:51.170 --> 00:54:51.180 align:start position:0% morale just Simone 00:54:51.180 --> 00:54:53.029 align:start position:0% morale just Simone simple<00:54:51.780> protection<00:54:52.109> catches<00:54:52.799> some 00:54:53.029 --> 00:54:53.039 align:start position:0% simple protection catches some 00:54:53.039 --> 00:54:55.220 align:start position:0% simple protection catches some inefficiencies<00:54:53.280> rather<00:54:54.119> than<00:54:54.359> a<00:54:54.780> more 00:54:55.220 --> 00:54:55.230 align:start position:0% inefficiencies rather than a more 00:54:55.230 --> 00:54:58.210 align:start position:0% inefficiencies rather than a more complex<00:54:55.589> one<00:54:55.799> who<00:54:55.950> tries<00:54:56.190> to<00:54:56.339> reflect<00:54:56.520> a<00:54:56.730> mover 00:54:58.210 --> 00:54:58.220 align:start position:0% complex one who tries to reflect a mover 00:54:58.220 --> 00:55:01.099 align:start position:0% complex one who tries to reflect a mover so<00:54:59.220> maybe<00:54:59.400> that's<00:54:59.640> the<00:54:59.910> approach<00:55:00.299> we<00:55:00.420> take<00:55:00.960> on 00:55:01.099 --> 00:55:01.109 align:start position:0% so maybe that's the approach we take on 00:55:01.109 --> 00:55:02.329 align:start position:0% so maybe that's the approach we take on I'm<00:55:01.200> not<00:55:01.319> actually<00:55:01.500> up<00:55:01.740> to<00:55:01.859> date<00:55:02.010> on<00:55:02.250> the 00:55:02.329 --> 00:55:02.339 align:start position:0% I'm not actually up to date on the 00:55:02.339 --> 00:55:06.770 align:start position:0% I'm not actually up to date on the latest<00:55:02.369> variant<00:55:03.059> of<00:55:03.359> the<00:55:03.420> proposals<00:55:04.020> I<00:55:05.780> think 00:55:06.770 --> 00:55:06.780 align:start position:0% latest variant of the proposals I think 00:55:06.780 --> 00:55:10.279 align:start position:0% latest variant of the proposals I think they<00:55:06.869> leave<00:55:07.020> this<00:55:07.170> one<00:55:07.380> has<00:55:07.619> some<00:55:07.859> an<00:55:07.980> extra<00:55:09.289> an 00:55:10.279 --> 00:55:10.289 align:start position:0% they leave this one has some an extra an 00:55:10.289 --> 00:55:18.970 align:start position:0% they leave this one has some an extra an extra<00:55:10.650> rule<00:55:10.859> just<00:55:11.250> directly 00:55:18.970 --> 00:55:18.980 align:start position:0% 00:55:18.980 --> 00:55:23.500 align:start position:0% because<00:55:21.609> so<00:55:22.609> think<00:55:22.880> there<00:55:23.000> was<00:55:23.180> like<00:55:23.210> an 00:55:23.500 --> 00:55:23.510 align:start position:0% because so think there was like an 00:55:23.510 --> 00:55:25.480 align:start position:0% because so think there was like an article<00:55:23.780> or<00:55:24.020> a<00:55:24.050> paper<00:55:24.440> some<00:55:24.800> time<00:55:24.980> ago<00:55:25.190> is 00:55:25.480 --> 00:55:25.490 align:start position:0% article or a paper some time ago is 00:55:25.490 --> 00:55:28.300 align:start position:0% article or a paper some time ago is showing<00:55:25.880> that<00:55:26.030> like<00:55:26.390> we<00:55:27.320> were<00:55:27.440> presented<00:55:28.280> with 00:55:28.300 --> 00:55:28.310 align:start position:0% showing that like we were presented with 00:55:28.310 --> 00:55:30.099 align:start position:0% showing that like we were presented with like<00:55:28.579> it<00:55:28.670> was<00:55:28.790> really<00:55:29.000> a<00:55:29.119> high<00:55:29.300> percentage<00:55:29.839> of 00:55:30.099 --> 00:55:30.109 align:start position:0% like it was really a high percentage of 00:55:30.109 --> 00:55:31.740 align:start position:0% like it was really a high percentage of contracts<00:55:30.890> that<00:55:30.980> are<00:55:31.099> actually<00:55:31.400> the<00:55:31.460> same 00:55:31.740 --> 00:55:31.750 align:start position:0% contracts that are actually the same 00:55:31.750 --> 00:55:34.870 align:start position:0% contracts that are actually the same workplace<00:55:32.750> and<00:55:33.589> I<00:55:33.680> guess<00:55:33.829> most<00:55:34.190> difficult 00:55:34.870 --> 00:55:34.880 align:start position:0% workplace and I guess most difficult 00:55:34.880 --> 00:55:37.089 align:start position:0% workplace and I guess most difficult safe<00:55:35.030> math<00:55:35.270> and<00:55:35.570> similar<00:55:35.900> contracts<00:55:36.349> like 00:55:37.089 --> 00:55:37.099 align:start position:0% safe math and similar contracts like 00:55:37.099 --> 00:55:39.190 align:start position:0% safe math and similar contracts like what<00:55:37.460> so<00:55:38.030> this<00:55:38.570> whole<00:55:38.720> thing<00:55:38.750> that<00:55:38.990> we're 00:55:39.190 --> 00:55:39.200 align:start position:0% what so this whole thing that we're 00:55:39.200 --> 00:55:40.630 align:start position:0% what so this whole thing that we're talking<00:55:39.320> about<00:55:39.500> the<00:55:39.770> repricing<00:55:40.130> alcohol 00:55:40.630 --> 00:55:40.640 align:start position:0% talking about the repricing alcohol 00:55:40.640 --> 00:55:45.280 align:start position:0% talking about the repricing alcohol would<00:55:41.270> be<00:55:41.480> a<00:55:42.700> developer's<00:55:43.780> not<00:55:44.780> really<00:55:45.079> too 00:55:45.280 --> 00:55:45.290 align:start position:0% would be a developer's not really too 00:55:45.290 --> 00:55:51.280 align:start position:0% would be a developer's not really too many<00:55:45.589> these<00:55:45.829> are<00:55:45.890> for<00:55:48.670> what<00:55:49.750> what<00:55:50.750> would<00:55:51.109> be 00:55:51.280 --> 00:55:51.290 align:start position:0% many these are for what what would be 00:55:51.290 --> 00:55:54.270 align:start position:0% many these are for what what would be the<00:55:51.470> difference<00:55:51.859> for<00:55:51.950> declined 00:55:54.270 --> 00:55:54.280 align:start position:0% the difference for declined 00:55:54.280 --> 00:55:56.980 align:start position:0% the difference for declined okay<00:55:55.280> one<00:55:55.550> case<00:55:55.760> right<00:55:56.060> now<00:55:56.119> have<00:55:56.510> all<00:55:56.810> this 00:55:56.980 --> 00:55:56.990 align:start position:0% okay one case right now have all this 00:55:56.990 --> 00:56:00.010 align:start position:0% okay one case right now have all this contracts<00:55:57.730> being<00:55:58.730> the<00:55:58.880> same<00:55:59.089> of<00:55:59.599> course<00:55:59.660> I 00:56:00.010 --> 00:56:00.020 align:start position:0% contracts being the same of course I 00:56:00.020 --> 00:56:01.900 align:start position:0% contracts being the same of course I don't<00:56:00.079> assume<00:56:00.500> that<00:56:00.770> a<00:56:00.829> client<00:56:01.070> stores<00:56:01.490> all<00:56:01.849> of 00:56:01.900 --> 00:56:01.910 align:start position:0% don't assume that a client stores all of 00:56:01.910 --> 00:56:06.960 align:start position:0% don't assume that a client stores all of them<00:56:02.240> separately<00:56:04.839> but<00:56:05.839> then<00:56:06.050> if<00:56:06.500> you<00:56:06.680> have 00:56:06.960 --> 00:56:06.970 align:start position:0% them separately but then if you have 00:56:06.970 --> 00:56:09.069 align:start position:0% them separately but then if you have people<00:56:07.970> start<00:56:08.210> writing<00:56:08.420> more<00:56:08.720> modular 00:56:09.069 --> 00:56:09.079 align:start position:0% people start writing more modular 00:56:09.079 --> 00:56:11.829 align:start position:0% people start writing more modular contracts<00:56:09.589> and<00:56:09.770> just<00:56:10.250> delegating<00:56:10.730> poles<00:56:11.119> then 00:56:11.829 --> 00:56:11.839 align:start position:0% contracts and just delegating poles then 00:56:11.839 --> 00:56:13.480 align:start position:0% contracts and just delegating poles then you're<00:56:11.960> going<00:56:12.050> to<00:56:12.109> have<00:56:12.260> a<00:56:12.530> fear<00:56:13.099> of<00:56:13.130> them 00:56:13.480 --> 00:56:13.490 align:start position:0% you're going to have a fear of them 00:56:13.490 --> 00:56:17.890 align:start position:0% you're going to have a fear of them deployed<00:56:13.849> to<00:56:14.480> what<00:56:15.190> different 00:56:17.890 --> 00:56:17.900 align:start position:0% deployed to what different 00:56:17.900 --> 00:56:20.049 align:start position:0% deployed to what different or<00:56:18.440> would<00:56:18.739> would<00:56:19.489> have<00:56:19.579> been<00:56:19.700> basically<00:56:19.970> the 00:56:20.049 --> 00:56:20.059 align:start position:0% or would would have been basically the 00:56:20.059 --> 00:56:24.519 align:start position:0% or would would have been basically the same<00:56:20.829> I'll<00:56:21.829> say<00:56:22.099> it's<00:56:22.579> already<00:56:23.529> already 00:56:24.519 --> 00:56:24.529 align:start position:0% same I'll say it's already already 00:56:24.529 --> 00:56:35.589 align:start position:0% same I'll say it's already already hashed<00:56:24.829> by<00:56:25.279> 30<00:56:25.730> stores<00:56:26.180> Becky<00:56:26.690> Becky<00:56:26.869> stole<00:56:27.739> it 00:56:35.589 --> 00:56:35.599 align:start position:0% 00:56:35.599 --> 00:56:38.049 align:start position:0% it's<00:56:36.079> definitely<00:56:36.400> raised<00:56:37.400> to<00:56:37.609> little<00:56:37.819> such<00:56:37.940> as 00:56:38.049 --> 00:56:38.059 align:start position:0% it's definitely raised to little such as 00:56:38.059 --> 00:56:39.760 align:start position:0% it's definitely raised to little such as the<00:56:38.180> other<00:56:38.299> day<00:56:38.510> the<00:56:38.539> most<00:56:38.930> popular<00:56:39.349> contract 00:56:39.760 --> 00:56:39.770 align:start position:0% the other day the most popular contract 00:56:39.770 --> 00:57:21.130 align:start position:0% the other day the most popular contract or<00:56:39.890> theory<00:56:40.160> of<00:56:40.279> one<00:56:40.490> of<00:56:40.609> the<00:56:40.670> most 00:57:21.130 --> 00:57:21.140 align:start position:0% 00:57:21.140 --> 00:57:24.470 align:start position:0% so<00:57:22.140> the<00:57:22.350> clients<00:57:22.920> currently<00:57:23.790> store<00:57:24.300> the 00:57:24.470 --> 00:57:24.480 align:start position:0% so the clients currently store the 00:57:24.480 --> 00:57:26.690 align:start position:0% so the clients currently store the conference<00:57:24.960> on<00:57:25.110> at<00:57:25.260> once<00:57:25.500> but<00:57:26.130> that's<00:57:26.370> not 00:57:26.690 --> 00:57:26.700 align:start position:0% conference on at once but that's not 00:57:26.700 --> 00:57:29.500 align:start position:0% conference on at once but that's not something<00:57:26.970> we<00:57:27.450> should<00:57:27.690> and<00:57:28.260> trying<00:57:28.650> or<00:57:28.980> soon 00:57:29.500 --> 00:57:29.510 align:start position:0% something we should and trying or soon 00:57:29.510 --> 00:57:34.550 align:start position:0% something we should and trying or soon because<00:57:31.040> there<00:57:32.040> are<00:57:33.200> there<00:57:34.200> are 00:57:34.550 --> 00:57:34.560 align:start position:0% because there are there are 00:57:34.560 --> 00:57:37.550 align:start position:0% because there are there are it<00:57:35.130> might<00:57:35.430> change<00:57:35.460> over<00:57:36.390> time<00:57:36.630> and<00:57:37.260> that 00:57:37.550 --> 00:57:37.560 align:start position:0% it might change over time and that 00:57:37.560 --> 00:57:40.400 align:start position:0% it might change over time and that verdict<00:57:37.890> no<00:57:38.670> I<00:57:39.030> was<00:57:39.540> thinking<00:57:39.570> primarily 00:57:40.400 --> 00:57:40.410 align:start position:0% verdict no I was thinking primarily 00:57:40.410 --> 00:57:44.590 align:start position:0% verdict no I was thinking primarily because<00:57:41.370> if<00:57:42.090> they<00:57:42.870> are<00:57:43.050> store<00:57:43.500> if<00:57:43.710> they're<00:57:43.920> um 00:57:44.590 --> 00:57:44.600 align:start position:0% because if they are store if they're um 00:57:44.600 --> 00:57:46.700 align:start position:0% because if they are store if they're um right<00:57:45.600> now<00:57:45.720> that<00:57:45.900> they<00:57:46.080> duplicated 00:57:46.700 --> 00:57:46.710 align:start position:0% right now that they duplicated 00:57:46.710 --> 00:57:49.250 align:start position:0% right now that they duplicated and<00:57:46.920> if<00:57:47.310> they're<00:57:47.490> on<00:57:47.640> the<00:57:47.670> duplicated<00:57:48.420> that 00:57:49.250 --> 00:57:49.260 align:start position:0% and if they're on the duplicated that 00:57:49.260 --> 00:57:52.850 align:start position:0% and if they're on the duplicated that makes<00:57:49.650> it<00:57:49.950> possible<00:57:50.610> to<00:57:51.060> have<00:57:52.020> another 00:57:52.850 --> 00:57:52.860 align:start position:0% makes it possible to have another 00:57:52.860 --> 00:57:56.270 align:start position:0% makes it possible to have another representation<00:57:53.570> which<00:57:54.570> is<00:57:54.600> more<00:57:55.110> amenable<00:57:56.100> to 00:57:56.270 --> 00:57:56.280 align:start position:0% representation which is more amenable to 00:57:56.280 --> 00:58:44.470 align:start position:0% representation which is more amenable to things<00:57:56.940> like<00:58:00.980> lip-synching 00:58:44.470 --> 00:58:44.480 align:start position:0% 00:58:44.480 --> 00:58:51.570 align:start position:0% [Music] 00:58:51.570 --> 00:58:51.580 align:start position:0% 00:58:51.580 --> 00:58:56.130 align:start position:0% it's<00:58:52.450> actually<00:58:53.490> impossible<00:58:54.490> to<00:58:55.140> delete 00:58:56.130 --> 00:58:56.140 align:start position:0% it's actually impossible to delete 00:58:56.140 --> 00:59:10.280 align:start position:0% it's actually impossible to delete things<00:58:56.800> from<00:59:04.860> which 00:59:10.280 --> 00:59:10.290 align:start position:0% 00:59:10.290 --> 00:59:19.360 align:start position:0% how<00:59:10.710> does<00:59:10.890> creative 00:59:19.360 --> 00:59:19.370 align:start position:0% 00:59:19.370 --> 00:59:23.109 align:start position:0% billions<00:59:20.180> County 00:59:23.109 --> 00:59:23.119 align:start position:0% 00:59:23.119 --> 00:59:25.510 align:start position:0% most<00:59:24.119> party 00:59:25.510 --> 00:59:25.520 align:start position:0% most party 00:59:25.520 --> 00:59:27.790 align:start position:0% most party I<00:59:25.550> mean<00:59:26.210> I<00:59:26.300> invited<00:59:26.540> contract<00:59:27.410> storage 00:59:27.790 --> 00:59:27.800 align:start position:0% I mean I invited contract storage 00:59:27.800 --> 00:59:31.200 align:start position:0% I mean I invited contract storage solution<00:59:28.340> building<00:59:28.730> a<00:59:29.150> store<00:59:29.690> stewardship 00:59:31.200 --> 00:59:31.210 align:start position:0% solution building a store stewardship 00:59:31.210 --> 00:59:34.720 align:start position:0% solution building a store stewardship adjustment<00:59:32.210> to<00:59:32.810> store<00:59:33.430> frequently<00:59:34.430> changed 00:59:34.720 --> 00:59:34.730 align:start position:0% adjustment to store frequently changed 00:59:34.730 --> 00:59:37.510 align:start position:0% adjustment to store frequently changed author<00:59:34.940> at<00:59:35.210> the<00:59:35.390> end<00:59:35.770> but<00:59:36.770> if<00:59:36.920> people<00:59:37.070> start 00:59:37.510 --> 00:59:37.520 align:start position:0% author at the end but if people start 00:59:37.520 --> 00:59:40.330 align:start position:0% author at the end but if people start doing<00:59:37.670> that<00:59:38.260> we<00:59:39.260> are<00:59:39.320> gonna<00:59:39.560> run<00:59:39.770> to<00:59:39.980> issues<00:59:40.190> we 00:59:40.330 --> 00:59:40.340 align:start position:0% doing that we are gonna run to issues we 00:59:40.340 --> 00:59:43.710 align:start position:0% doing that we are gonna run to issues we need<00:59:40.520> to<00:59:40.670> start<00:59:40.910> college<00:59:41.119> committee<00:59:41.650> contract 00:59:43.710 --> 00:59:43.720 align:start position:0% need to start college committee contract 00:59:43.720 --> 00:59:49.630 align:start position:0% need to start college committee contract so<00:59:44.800> so<00:59:45.850> well<00:59:46.850> I<00:59:46.880> mean<00:59:47.950> the<00:59:48.950> garbage<00:59:49.220> collecting 00:59:49.630 --> 00:59:49.640 align:start position:0% so so well I mean the garbage collecting 00:59:49.640 --> 00:59:53.830 align:start position:0% so so well I mean the garbage collecting the<00:59:49.760> contracts<00:59:50.630> there<00:59:50.810> is<00:59:52.240> with<00:59:53.240> the<00:59:53.270> the 00:59:53.830 --> 00:59:53.840 align:start position:0% the contracts there is with the the 00:59:53.840 --> 00:59:57.160 align:start position:0% the contracts there is with the the repricing<00:59:54.470> coming<00:59:54.980> up<00:59:55.100> for<00:59:55.280> esto<00:59:56.170> there's 00:59:57.160 --> 00:59:57.170 align:start position:0% repricing coming up for esto there's 00:59:57.170 --> 01:00:00.670 align:start position:0% repricing coming up for esto there's this<00:59:57.530> other<00:59:58.510> discovery<00:59:59.510> that<00:59:59.720> it<01:00:00.260> is<01:00:00.410> cheaper 01:00:00.670 --> 01:00:00.680 align:start position:0% this other discovery that it is cheaper 01:00:00.680 --> 01:00:03.970 align:start position:0% this other discovery that it is cheaper if<01:00:01.010> you<01:00:01.040> have<01:00:01.520> a<01:00:01.550> lot<01:00:01.760> of<01:00:01.790> linear<01:00:02.720> data<01:00:02.960> it<01:00:03.920> is 01:00:03.970 --> 01:00:03.980 align:start position:0% if you have a lot of linear data it is 01:00:03.980 --> 01:00:07.120 align:start position:0% if you have a lot of linear data it is cheaper<01:00:04.550> to<01:00:04.580> store<01:00:05.330> this<01:00:05.510> in<01:00:05.660> context<01:00:06.110> and<01:00:06.410> use 01:00:07.120 --> 01:00:07.130 align:start position:0% cheaper to store this in context and use 01:00:07.130 --> 01:00:10.810 align:start position:0% cheaper to store this in context and use Xcode<01:00:07.670> copy<01:00:08.740> more<01:00:09.740> even<01:00:10.100> to<01:00:10.280> polish<01:00:10.670> and 01:00:10.810 --> 01:00:10.820 align:start position:0% Xcode copy more even to polish and 01:00:10.820 --> 01:00:12.850 align:start position:0% Xcode copy more even to polish and hostage<01:00:11.180> return<01:00:11.570> some<01:00:12.170> of<01:00:12.260> the<01:00:12.350> time<01:00:12.560> of<01:00:12.710> my 01:00:12.850 --> 01:00:12.860 align:start position:0% hostage return some of the time of my 01:00:12.860 --> 01:00:15.400 align:start position:0% hostage return some of the time of my code<01:00:13.190> yeah<01:00:13.670> it's<01:00:14.450> in<01:00:14.570> the<01:00:14.720> case<01:00:14.900> when<01:00:15.140> it's 01:00:15.400 --> 01:00:15.410 align:start position:0% code yeah it's in the case when it's 01:00:15.410 --> 01:00:17.350 align:start position:0% code yeah it's in the case when it's just<01:00:15.590> pure<01:00:15.860> data<01:00:16.070> and<01:00:16.369> you<01:00:16.490> X<01:00:16.700> goes<01:00:16.970> up<01:00:17.150> here 01:00:17.350 --> 01:00:17.360 align:start position:0% just pure data and you X goes up here 01:00:17.360 --> 01:00:20.070 align:start position:0% just pure data and you X goes up here then<01:00:18.290> a<01:00:18.340> difference<01:00:19.340> config 01:00:20.070 --> 01:00:20.080 align:start position:0% then a difference config 01:00:20.080 --> 01:00:26.330 align:start position:0% then a difference config [Music] 01:00:26.330 --> 01:00:26.340 align:start position:0% 01:00:26.340 --> 01:00:28.770 align:start position:0% my<01:00:27.340> test<01:00:27.610> ugh<01:00:27.820> but<01:00:27.970> I<01:00:28.060> don't<01:00:28.240> think<01:00:28.420> it's<01:00:28.630> a 01:00:28.770 --> 01:00:28.780 align:start position:0% my test ugh but I don't think it's a 01:00:28.780 --> 01:00:31.290 align:start position:0% my test ugh but I don't think it's a neat<01:00:29.020> bad<01:00:29.320> I<01:00:29.710> think<01:00:29.830> it's<01:00:30.130> just<01:00:30.310> it<01:00:30.550> reveals 01:00:31.290 --> 01:00:31.300 align:start position:0% neat bad I think it's just it reveals 01:00:31.300 --> 01:00:33.330 align:start position:0% neat bad I think it's just it reveals area<01:00:31.750> we<01:00:31.900> know<01:00:32.020> these<01:00:32.200> polytrauma<01:00:32.740> minds<01:00:33.100> this 01:00:33.330 --> 01:00:33.340 align:start position:0% area we know these polytrauma minds this 01:00:33.340 --> 01:00:35.400 align:start position:0% area we know these polytrauma minds this previously<01:00:33.790> hasn't<01:00:34.240> been<01:00:34.390> enough<01:00:34.810> initiative 01:00:35.400 --> 01:00:35.410 align:start position:0% previously hasn't been enough initiative 01:00:35.410 --> 01:00:39.210 align:start position:0% previously hasn't been enough initiative just<01:00:35.440> be<01:00:35.710> entitled<01:00:37.290> but<01:00:38.290> I<01:00:38.380> think<01:00:38.800> that<01:00:39.010> the 01:00:39.210 --> 01:00:39.220 align:start position:0% just be entitled but I think that the 01:00:39.220 --> 01:00:41.100 align:start position:0% just be entitled but I think that the costs<01:00:39.790> of<01:00:39.880> contract<01:00:40.360> storage<01:00:40.690> roughly 01:00:41.100 --> 01:00:41.110 align:start position:0% costs of contract storage roughly 01:00:41.110 --> 01:00:43.260 align:start position:0% costs of contract storage roughly relates<01:00:41.560> to<01:00:41.860> the<01:00:42.520> actual<01:00:42.670> costs<01:00:43.180> of 01:00:43.260 --> 01:00:43.270 align:start position:0% relates to the actual costs of 01:00:43.270 --> 01:00:46.670 align:start position:0% relates to the actual costs of individual<01:00:44.020> clients<01:00:44.620> it's<01:00:45.160> cheap<01:00:45.370> Livaudais 01:00:46.670 --> 01:00:46.680 align:start position:0% individual clients it's cheap Livaudais 01:00:46.680 --> 01:00:48.060 align:start position:0% individual clients it's cheap Livaudais reasons 01:00:48.060 --> 01:00:48.070 align:start position:0% reasons 01:00:48.070 --> 01:00:51.060 align:start position:0% reasons we<01:00:48.580> store<01:00:48.940> we've<01:00:49.240> got<01:00:49.540> was<01:00:49.720> mrs.<01:00:50.200> Patricia 01:00:51.060 --> 01:00:51.070 align:start position:0% we store we've got was mrs. Patricia 01:00:51.070 --> 01:00:55.350 align:start position:0% we store we've got was mrs. Patricia training<01:00:53.190> but<01:00:54.190> this<01:00:54.370> this<01:00:54.610> also<01:00:54.820> opens<01:00:55.000> up<01:00:55.300> the 01:00:55.350 --> 01:00:55.360 align:start position:0% training but this this also opens up the 01:00:55.360 --> 01:00:59.730 align:start position:0% training but this this also opens up the question<01:00:56.520> why<01:00:57.520> is<01:00:57.820> the<01:00:58.810> story<01:00:59.080> to<01:00:59.170> tell<01:00:59.440> you 01:00:59.730 --> 01:00:59.740 align:start position:0% question why is the story to tell you 01:00:59.740 --> 01:01:01.170 align:start position:0% question why is the story to tell you about<01:00:59.920> the<01:01:00.100> key<01:01:00.280> that<01:01:00.460> is<01:01:00.550> storage<01:01:00.820> venue 01:01:01.170 --> 01:01:01.180 align:start position:0% about the key that is storage venue 01:01:01.180 --> 01:01:02.900 align:start position:0% about the key that is storage venue limited<01:01:01.570> that's<01:01:01.810> where<01:01:01.990> the<01:01:02.080> two<01:01:02.200> bytes 01:01:02.900 --> 01:01:02.910 align:start position:0% limited that's where the two bytes 01:01:02.910 --> 01:01:05.040 align:start position:0% limited that's where the two bytes because<01:01:03.910> if<01:01:04.180> you<01:01:04.300> move<01:01:04.420> if<01:01:04.630> you<01:01:04.750> could<01:01:04.900> have 01:01:05.040 --> 01:01:05.050 align:start position:0% because if you move if you could have 01:01:05.050 --> 01:01:07.850 align:start position:0% because if you move if you could have more<01:01:05.350> in<01:01:06.040> their<01:01:06.160> names<01:01:06.370> of<01:01:06.520> interest<01:01:06.940> and<01:01:07.480> i 01:01:07.850 --> 01:01:07.860 align:start position:0% more in their names of interest and i 01:01:07.860 --> 01:01:10.170 align:start position:0% more in their names of interest and i storage<01:01:08.860> should<01:01:09.070> absolutely<01:01:09.340> get<01:01:09.670> me<01:01:09.850> a<01:01:10.000> page 01:01:10.170 --> 01:01:10.180 align:start position:0% storage should absolutely get me a page 01:01:10.180 --> 01:01:13.620 align:start position:0% storage should absolutely get me a page table<01:01:10.450> time<01:01:10.810> it's<01:01:11.020> it<01:01:11.230> up<01:01:11.380> with<01:01:12.070> large<01:01:13.060> pages 01:01:13.620 --> 01:01:13.630 align:start position:0% table time it's it up with large pages 01:01:13.630 --> 01:01:16.380 align:start position:0% table time it's it up with large pages so<01:01:14.020> it<01:01:14.260> cost<01:01:14.470> a<01:01:14.620> lot<01:01:14.770> but<01:01:15.000> perspective<01:01:16.000> page 01:01:16.380 --> 01:01:16.390 align:start position:0% so it cost a lot but perspective page 01:01:16.390 --> 01:01:18.840 align:start position:0% so it cost a lot but perspective page and<01:01:16.980> variable<01:01:17.980> quantities 01:01:18.840 --> 01:01:18.850 align:start position:0% and variable quantities 01:01:18.850 --> 01:01:22.430 align:start position:0% and variable quantities that's<01:01:19.210> how<01:01:19.480> just<01:01:20.110> a<01:01:20.200> story<01:01:20.530> a<01:01:20.620> lot<01:01:21.610> of<01:01:21.640> the 01:01:22.430 --> 01:01:22.440 align:start position:0% that's how just a story a lot of the 01:01:22.440 --> 01:01:24.700 align:start position:0% that's how just a story a lot of the machines 01:01:24.700 --> 01:01:24.710 align:start position:0% machines 01:01:24.710 --> 01:01:26.500 align:start position:0% machines okay<01:01:24.980> that's<01:01:25.730> when<01:01:25.940> there's<01:01:26.089> been<01:01:26.180> a<01:01:26.240> copy 01:01:26.500 --> 01:01:26.510 align:start position:0% okay that's when there's been a copy 01:01:26.510 --> 01:01:28.450 align:start position:0% okay that's when there's been a copy time<01:01:26.780> waiting<01:01:27.140> for<01:01:27.349> each<01:01:27.589> to<01:01:27.800> return<01:01:27.890> half<01:01:28.280> the 01:01:28.450 --> 01:01:28.460 align:start position:0% time waiting for each to return half the 01:01:28.460 --> 01:01:31.059 align:start position:0% time waiting for each to return half the time<01:01:28.640> receiving<01:01:29.030> the<01:01:29.089> data<01:01:29.440> and<01:01:30.440> maybe<01:01:30.619> much 01:01:31.059 --> 01:01:31.069 align:start position:0% time receiving the data and maybe much 01:01:31.069 --> 01:01:40.420 align:start position:0% time receiving the data and maybe much besides<01:01:38.170> straight<01:01:39.200> dick<01:01:39.470> you<01:01:39.589> know<01:01:39.619> I<01:01:39.950> even 01:01:40.420 --> 01:01:40.430 align:start position:0% besides straight dick you know I even 01:01:40.430 --> 01:01:42.069 align:start position:0% besides straight dick you know I even either<01:01:40.790> probably<01:01:41.119> do<01:01:41.270> it<01:01:41.420> without<01:01:41.599> changing 01:01:42.069 --> 01:01:42.079 align:start position:0% either probably do it without changing 01:01:42.079 --> 01:01:44.260 align:start position:0% either probably do it without changing table<01:01:42.470> covers<01:01:42.829> you<01:01:43.069> just<01:01:43.280> make<01:01:43.430> it<01:01:43.460> store<01:01:43.910> a 01:01:44.260 --> 01:01:44.270 align:start position:0% table covers you just make it store a 01:01:44.270 --> 01:01:49.440 align:start position:0% table covers you just make it store a lot<01:01:44.990> more<01:01:45.849> of<01:01:46.849> a<01:01:46.940> chance<01:01:47.270> but<01:01:48.140> we've<01:01:48.740> got 01:01:49.440 --> 01:01:49.450 align:start position:0% lot more of a chance but we've got 01:01:49.450 --> 01:01:51.339 align:start position:0% lot more of a chance but we've got thousands<01:01:50.450> hundreds<01:01:50.780> of<01:01:50.839> thousands<01:01:51.230> of 01:01:51.339 --> 01:01:51.349 align:start position:0% thousands hundreds of thousands of 01:01:51.349 --> 01:01:53.349 align:start position:0% thousands hundreds of thousands of contracts<01:01:51.800> deployed<01:01:52.160> that<01:01:52.490> rely<01:01:52.819> on<01:01:53.059> the 01:01:53.349 --> 01:01:53.359 align:start position:0% contracts deployed that rely on the 01:01:53.359 --> 01:01:55.870 align:start position:0% contracts deployed that rely on the ultimate<01:01:53.780> live<01:01:54.109> use<01:01:54.430> contract<01:01:55.430> storage<01:01:55.790> of 01:01:55.870 --> 01:01:55.880 align:start position:0% ultimate live use contract storage of 01:01:55.880 --> 01:02:08.079 align:start position:0% ultimate live use contract storage of the<01:01:55.940> massive<01:01:56.240> hash<01:01:56.420> table<01:01:57.790> over<01:01:58.790> 19<01:02:06.700> if<01:02:07.700> victim 01:02:08.079 --> 01:02:08.089 align:start position:0% the massive hash table over 19 if victim 01:02:08.089 --> 01:02:09.640 align:start position:0% the massive hash table over 19 if victim plea<01:02:08.210> is<01:02:08.300> instead<01:02:08.569> of<01:02:08.690> treating<01:02:09.200> contract 01:02:09.640 --> 01:02:09.650 align:start position:0% plea is instead of treating contract 01:02:09.650 --> 01:02:12.520 align:start position:0% plea is instead of treating contract storage<01:02:10.010> something<01:02:10.599> 286<01:02:11.599> that<01:02:11.839> played<01:02:12.380> 2 01:02:12.520 --> 01:02:12.530 align:start position:0% storage something 286 that played 2 01:02:12.530 --> 01:02:14.710 align:start position:0% storage something 286 that played 2 bytes<01:02:12.800> of<01:02:12.950> data<01:02:13.010> to<01:02:13.280> buy<01:02:13.430> that<01:02:13.700> you<01:02:14.540> would 01:02:14.710 --> 01:02:14.720 align:start position:0% bytes of data to buy that you would 01:02:14.720 --> 01:02:17.500 align:start position:0% bytes of data to buy that you would traces<01:02:15.109> the<01:02:15.200> series<01:02:15.470> of<01:02:15.589> pages<01:02:15.980> and<01:02:16.190> so<01:02:16.940> when 01:02:17.500 --> 01:02:17.510 align:start position:0% traces the series of pages and so when 01:02:17.510 --> 01:02:19.180 align:start position:0% traces the series of pages and so when you<01:02:17.630> do<01:02:17.780> a<01:02:18.109> you<01:02:18.410> basically<01:02:18.800> treat<01:02:19.069> the 01:02:19.180 --> 01:02:19.190 align:start position:0% you do a you basically treat the 01:02:19.190 --> 01:02:21.280 align:start position:0% you do a you basically treat the last<01:02:19.369> few<01:02:19.609> bits<01:02:19.790> of<01:02:20.000> the<01:02:20.180> position<01:02:21.109> of<01:02:21.200> the 01:02:21.280 --> 01:02:21.290 align:start position:0% last few bits of the position of the 01:02:21.290 --> 01:02:24.730 align:start position:0% last few bits of the position of the page<01:02:21.470> of<01:02:21.800> first<01:02:22.069> but<01:02:22.309> as<01:02:22.640> which<01:02:22.940> patients<01:02:23.740> and 01:02:24.730 --> 01:02:24.740 align:start position:0% page of first but as which patients and 01:02:24.740 --> 01:02:27.730 align:start position:0% page of first but as which patients and then<01:02:25.069> you<01:02:25.869> you<01:02:26.869> know<01:02:26.900> the<01:02:27.260> first<01:02:27.470> time<01:02:27.680> you 01:02:27.730 --> 01:02:27.740 align:start position:0% then you you know the first time you 01:02:27.740 --> 01:02:29.980 align:start position:0% then you you know the first time you defeat<01:02:28.250> genuine<01:02:28.670> page<01:02:28.849> you<01:02:29.150> charge<01:02:29.450> their<01:02:29.690> own 01:02:29.980 --> 01:02:29.990 align:start position:0% defeat genuine page you charge their own 01:02:29.990 --> 01:02:31.910 align:start position:0% defeat genuine page you charge their own gas<01:02:30.290> for<01:02:30.589> that<01:02:30.619> and 01:02:31.910 --> 01:02:31.920 align:start position:0% gas for that and 01:02:31.920 --> 01:02:33.950 align:start position:0% gas for that and like<01:02:32.279> maybe<01:02:32.490> two<01:02:32.789> or<01:02:32.940> three<01:02:32.970> five<01:02:33.359> times<01:02:33.720> well 01:02:33.950 --> 01:02:33.960 align:start position:0% like maybe two or three five times well 01:02:33.960 --> 01:02:36.140 align:start position:0% like maybe two or three five times well apparently<01:02:34.500> slope<01:02:34.829> costs<01:02:35.369> but<01:02:35.910> then<01:02:36.059> the 01:02:36.140 --> 01:02:36.150 align:start position:0% apparently slope costs but then the 01:02:36.150 --> 01:02:38.029 align:start position:0% apparently slope costs but then the several<01:02:36.599> times<01:02:36.900> with<01:02:37.170> a<01:02:37.260> page<01:02:37.529> sorry<01:02:37.859> of 01:02:38.029 --> 01:02:38.039 align:start position:0% several times with a page sorry of 01:02:38.039 --> 01:02:39.840 align:start position:0% several times with a page sorry of memory<01:02:38.339> you<01:02:38.519> charge<01:02:38.789> only 01:02:39.840 --> 01:02:39.850 align:start position:0% memory you charge only 01:02:39.850 --> 01:02:42.090 align:start position:0% memory you charge only comparable<01:02:40.510> to<01:02:40.720> get<01:02:40.870> luggage<01:02:41.230> costs<01:02:41.470> total 01:02:42.090 --> 01:02:42.100 align:start position:0% comparable to get luggage costs total 01:02:42.100 --> 01:02:44.100 align:start position:0% comparable to get luggage costs total load<01:02:42.430> of<01:02:42.640> cows<01:02:42.850> purchase<01:02:43.360> in<01:02:43.510> the<01:02:43.600> store<01:02:43.630> back 01:02:44.100 --> 01:02:44.110 align:start position:0% load of cows purchase in the store back 01:02:44.110 --> 01:02:47.460 align:start position:0% load of cows purchase in the store back potentially<01:02:45.210> and<01:02:46.210> city<01:02:46.600> of<01:02:46.810> codes<01:02:47.110> would<01:02:47.320> be 01:02:47.460 --> 01:02:47.470 align:start position:0% potentially and city of codes would be 01:02:47.470 --> 01:02:48.990 align:start position:0% potentially and city of codes would be the<01:02:47.590> sign<01:02:47.800> that<01:02:47.830> still<01:02:48.250> justice<01:02:48.580> lightly<01:02:48.970> a 01:02:48.990 --> 01:02:49.000 align:start position:0% the sign that still justice lightly a 01:02:49.000 --> 01:02:50.370 align:start position:0% the sign that still justice lightly a store<01:02:49.270> that's<01:02:49.600> just<01:02:49.900> treating<01:02:50.230> that 01:02:50.370 --> 01:02:50.380 align:start position:0% store that's just treating that 01:02:50.380 --> 01:02:52.080 align:start position:0% store that's just treating that semantically<01:02:51.070> that's<01:02:51.400> treating<01:02:51.790> the<01:02:51.910> belly 01:02:52.080 --> 01:02:52.090 align:start position:0% semantically that's treating the belly 01:02:52.090 --> 01:02:55.650 align:start position:0% semantically that's treating the belly differently<01:02:53.250> suits<01:02:54.250> their<01:02:54.430> lives<01:02:54.760> forty<01:02:55.240> two 01:02:55.650 --> 01:02:55.660 align:start position:0% differently suits their lives forty two 01:02:55.660 --> 01:02:57.600 align:start position:0% differently suits their lives forty two quite<01:02:56.260> so<01:02:56.440> that's<01:02:56.590> kinda<01:02:56.860> still<01:02:57.070> we<01:02:57.190> really<01:02:57.460> do 01:02:57.600 --> 01:02:57.610 align:start position:0% quite so that's kinda still we really do 01:02:57.610 --> 01:02:59.040 align:start position:0% quite so that's kinda still we really do contain<01:02:57.880> lots<01:02:58.210> of<01:02:58.390> they're<01:02:58.570> only<01:02:58.720> under 01:02:59.040 --> 01:02:59.050 align:start position:0% contain lots of they're only under 01:02:59.050 --> 01:03:00.690 align:start position:0% contain lots of they're only under twenty<01:02:59.290> eight<01:02:59.440> nightly<01:02:59.800> just<01:03:00.010> keep<01:03:00.160> infinity 01:03:00.690 --> 01:03:00.700 align:start position:0% twenty eight nightly just keep infinity 01:03:00.700 --> 01:03:02.730 align:start position:0% twenty eight nightly just keep infinity let<01:03:00.910> you<01:03:01.060> hospital<01:03:01.510> and<01:03:01.870> that's<01:03:02.020> longest<01:03:02.560> you 01:03:02.730 --> 01:03:02.740 align:start position:0% let you hospital and that's longest you 01:03:02.740 --> 01:03:05.280 align:start position:0% let you hospital and that's longest you you<01:03:02.980> go<01:03:03.130> within<01:03:03.340> the<01:03:03.400> same<01:03:03.640> page<01:03:03.940> only<01:03:04.750> charged 01:03:05.280 --> 01:03:05.290 align:start position:0% you go within the same page only charged 01:03:05.290 --> 01:03:07.050 align:start position:0% you go within the same page only charged much<01:03:05.560> of<01:03:05.740> it<01:03:05.830> at<01:03:05.920> their<01:03:06.070> scale<01:03:06.340> but<01:03:06.790> that<01:03:06.910> would 01:03:07.050 --> 01:03:07.060 align:start position:0% much of it at their scale but that would 01:03:07.060 --> 01:03:08.880 align:start position:0% much of it at their scale but that would radically<01:03:07.390> change<01:03:07.690> health<01:03:08.350> and<01:03:08.620> we<01:03:08.710> just 01:03:08.880 --> 01:03:08.890 align:start position:0% radically change health and we just 01:03:08.890 --> 01:03:10.700 align:start position:0% radically change health and we just needed<01:03:09.070> to<01:03:09.250> store<01:03:09.430> data<01:03:09.610> instead<01:03:10.150> of<01:03:10.270> using 01:03:10.700 --> 01:03:10.710 align:start position:0% needed to store data instead of using 01:03:10.710 --> 01:03:13.140 align:start position:0% needed to store data instead of using the<01:03:11.710> entire<01:03:12.010> storage<01:03:12.310> by<01:03:12.520> cash<01:03:12.730> table 01:03:13.140 --> 01:03:13.150 align:start position:0% the entire storage by cash table 01:03:13.150 --> 01:03:15.060 align:start position:0% the entire storage by cash table everything<01:03:13.390> to<01:03:13.660> start<01:03:13.900> using<01:03:14.200> things<01:03:14.950> like 01:03:15.060 --> 01:03:15.070 align:start position:0% everything to start using things like 01:03:15.070 --> 01:03:16.320 align:start position:0% everything to start using things like red<01:03:15.310> black<01:03:15.460> trees<01:03:15.790> and<01:03:16.000> so<01:03:16.180> on 01:03:16.320 --> 01:03:16.330 align:start position:0% red black trees and so on 01:03:16.330 --> 01:03:17.970 align:start position:0% red black trees and so on it<01:03:16.540> all<01:03:16.660> just<01:03:16.690> all<01:03:17.050> stuff<01:03:17.290> from<01:03:17.320> contiguous 01:03:17.970 --> 01:03:17.980 align:start position:0% it all just all stuff from contiguous 01:03:17.980 --> 01:03:21.050 align:start position:0% it all just all stuff from contiguous range<01:03:18.160> ISM<01:03:18.610> a<01:03:19.110> similar<01:03:20.110> idea<01:03:20.230> was<01:03:20.590> was 01:03:21.050 --> 01:03:21.060 align:start position:0% range ISM a similar idea was was 01:03:21.060 --> 01:03:23.280 align:start position:0% range ISM a similar idea was was explored<01:03:22.060> too<01:03:22.270> soon<01:03:22.540> I<01:03:22.810> guess<01:03:22.990> we<01:03:23.110> could 01:03:23.280 --> 01:03:23.290 align:start position:0% explored too soon I guess we could 01:03:23.290 --> 01:03:30.840 align:start position:0% explored too soon I guess we could extend<01:03:23.710> by<01:03:27.360> discussed<01:03:28.360> it<01:03:28.570> hmm<01:03:29.500> similar<01:03:30.430> but 01:03:30.840 --> 01:03:30.850 align:start position:0% extend by discussed it hmm similar but 01:03:30.850 --> 01:03:34.080 align:start position:0% extend by discussed it hmm similar but not<01:03:31.750> the<01:03:31.810> same<01:03:31.870> and<01:03:32.710> instead<01:03:33.130> of<01:03:33.190> using<01:03:33.490> s<01:03:33.820> load 01:03:34.080 --> 01:03:34.090 align:start position:0% not the same and instead of using s load 01:03:34.090 --> 01:03:36.240 align:start position:0% not the same and instead of using s load two<01:03:34.450> together<01:03:35.080> pages<01:03:35.560> it<01:03:35.710> would<01:03:35.830> be<01:03:35.950> memory 01:03:36.240 --> 01:03:36.250 align:start position:0% two together pages it would be memory 01:03:36.250 --> 01:03:41.430 align:start position:0% two together pages it would be memory mapping<01:03:36.750> the<01:03:37.750> entire<01:03:37.780> storage<01:03:40.020> some<01:03:41.020> are<01:03:41.170> pink 01:03:41.430 --> 01:03:41.440 align:start position:0% mapping the entire storage some are pink 01:03:41.440 --> 01:03:47.199 align:start position:0% mapping the entire storage some are pink tonight 01:03:47.199 --> 01:03:47.209 align:start position:0% 01:03:47.209 --> 01:03:50.849 align:start position:0% but<01:03:48.109> there's<01:03:48.319> one<01:03:48.529> trade<01:03:48.859> up<01:03:49.009> here<01:03:49.309> it<01:03:50.180> pushes 01:03:50.849 --> 01:03:50.859 align:start position:0% but there's one trade up here it pushes 01:03:50.859 --> 01:03:51.999 align:start position:0% but there's one trade up here it pushes hmm 01:03:51.999 --> 01:03:52.009 align:start position:0% hmm 01:03:52.009 --> 01:03:55.239 align:start position:0% hmm it<01:03:52.489> pushes<01:03:52.910> the<01:03:53.359> other<01:03:53.660> curve<01:03:54.109> to<01:03:54.319> do<01:03:54.499> hash 01:03:55.239 --> 01:03:55.249 align:start position:0% it pushes the other curve to do hash 01:03:55.249 --> 01:03:58.839 align:start position:0% it pushes the other curve to do hash tables<01:03:55.809> to<01:03:56.809> the<01:03:56.930> language<01:03:57.670> well<01:03:58.670> so 01:03:58.839 --> 01:03:58.849 align:start position:0% tables to the language well so 01:03:58.849 --> 01:04:00.309 align:start position:0% tables to the language well so differently<01:03:59.239> shouldn't<01:03:59.630> be<01:03:59.719> hash<01:03:59.869> tables 01:04:00.309 --> 01:04:00.319 align:start position:0% differently shouldn't be hash tables 01:04:00.319 --> 01:04:02.019 align:start position:0% differently shouldn't be hash tables because<01:04:00.799> hash<01:04:01.039> table<01:04:01.369> say<01:04:01.489> their<01:04:01.640> motorized 01:04:02.019 --> 01:04:02.029 align:start position:0% because hash table say their motorized 01:04:02.029 --> 01:04:04.329 align:start position:0% because hash table say their motorized on<01:04:02.299> one<01:04:02.569> and<01:04:02.930> every<01:04:03.499> time<01:04:03.680> you<01:04:03.739> need<01:04:03.890> to<01:04:03.979> expand 01:04:04.329 --> 01:04:04.339 align:start position:0% on one and every time you need to expand 01:04:04.339 --> 01:04:07.089 align:start position:0% on one and every time you need to expand the<01:04:04.459> edge<01:04:04.579> table<01:04:04.789> user<01:04:05.059> 208<01:04:05.569> word<01:04:05.829> which<01:04:06.829> means 01:04:07.089 --> 01:04:07.099 align:start position:0% the edge table user 208 word which means 01:04:07.099 --> 01:04:09.430 align:start position:0% the edge table user 208 word which means that<01:04:07.400> you<01:04:07.640> know<01:04:07.759> every<01:04:08.359> 10,000<01:04:08.959> or<01:04:09.049> agree<01:04:09.259> you 01:04:09.430 --> 01:04:09.440 align:start position:0% that you know every 10,000 or agree you 01:04:09.440 --> 01:04:11.109 align:start position:0% that you know every 10,000 or agree you know<01:04:09.559> two<01:04:09.949> thousand<01:04:10.279> transactions<01:04:10.819> and<01:04:11.059> it 01:04:11.109 --> 01:04:11.119 align:start position:0% know two thousand transactions and it 01:04:11.119 --> 01:04:16.299 align:start position:0% know two thousand transactions and it refers<01:04:11.390> what<01:04:11.599> needs<01:04:11.809> to<01:04:12.019> use<01:04:15.130> so<01:04:16.130> they're 01:04:16.299 --> 01:04:16.309 align:start position:0% refers what needs to use so they're 01:04:16.309 --> 01:04:20.829 align:start position:0% refers what needs to use so they're gonna<01:04:16.430> do<01:04:16.670> this<01:04:18.699> fixed<01:04:19.699> along<01:04:20.029> in<01:04:20.239> time<01:04:20.479> like<01:04:20.809> a 01:04:20.829 --> 01:04:20.839 align:start position:0% gonna do this fixed along in time like a 01:04:20.839 --> 01:04:23.380 align:start position:0% gonna do this fixed along in time like a red<01:04:21.049> black<01:04:21.079> tree<01:04:21.489> and<01:04:22.489> it<01:04:22.609> doesn<01:04:22.789> t<01:04:22.849> need<01:04:23.089> to<01:04:23.180> do 01:04:23.380 --> 01:04:23.390 align:start position:0% red black tree and it doesn t need to do 01:04:23.390 --> 01:04:28.130 align:start position:0% red black tree and it doesn t need to do that<01:04:23.599> in<01:04:24.489> part 01:04:28.130 --> 01:04:28.140 align:start position:0% 01:04:28.140 --> 01:04:39.980 align:start position:0% [Music] 01:04:39.980 --> 01:04:39.990 align:start position:0% 01:04:39.990 --> 01:04:43.319 align:start position:0% from<01:04:40.990> developer<01:04:41.740> experience<01:04:42.280> point<01:04:43.000> of<01:04:43.119> view 01:04:43.319 --> 01:04:43.329 align:start position:0% from developer experience point of view 01:04:43.329 --> 01:04:45.900 align:start position:0% from developer experience point of view a<01:04:43.630> lot<01:04:43.990> of<01:04:44.140> contracts<01:04:44.920> really<01:04:45.190> rely<01:04:45.609> on<01:04:45.640> a 01:04:45.900 --> 01:04:45.910 align:start position:0% a lot of contracts really rely on a 01:04:45.910 --> 01:04:46.950 align:start position:0% a lot of contracts really rely on a mapping<01:04:46.270> yes 01:04:46.950 --> 01:04:46.960 align:start position:0% mapping yes 01:04:46.960 --> 01:04:48.599 align:start position:0% mapping yes that's<01:04:47.200> like<01:04:47.410> the<01:04:47.530> core<01:04:47.829> data<01:04:47.980> structure<01:04:48.490> we 01:04:48.599 --> 01:04:48.609 align:start position:0% that's like the core data structure we 01:04:48.609 --> 01:04:50.819 align:start position:0% that's like the core data structure we use<01:04:48.640> I<01:04:49.000> think<01:04:49.119> it's<01:04:49.510> still<01:04:49.660> headset<01:04:50.109> it's<01:04:50.619> just 01:04:50.819 --> 01:04:50.829 align:start position:0% use I think it's still headset it's just 01:04:50.829 --> 01:04:53.720 align:start position:0% use I think it's still headset it's just what<01:04:50.950> the<01:04:51.039> language<01:04:51.190> was<01:04:51.369> different<01:04:52.270> seasons 01:04:53.720 --> 01:04:53.730 align:start position:0% what the language was different seasons 01:04:53.730 --> 01:04:55.859 align:start position:0% what the language was different seasons yeah<01:04:54.730> I<01:04:54.760> don't<01:04:55.150> think<01:04:55.329> it's<01:04:55.450> an<01:04:55.539> issue<01:04:55.569> that 01:04:55.859 --> 01:04:55.869 align:start position:0% yeah I don't think it's an issue that 01:04:55.869 --> 01:04:57.240 align:start position:0% yeah I don't think it's an issue that the<01:04:55.960> language<01:04:56.349> will<01:04:56.680> have<01:04:57.010> to<01:04:57.130> know 01:04:57.240 --> 01:04:57.250 align:start position:0% the language will have to know 01:04:57.250 --> 01:04:59.160 align:start position:0% the language will have to know everything<01:04:57.520> will<01:04:58.329> be<01:04:58.450> just<01:04:58.660> an<01:04:58.780> initial 01:04:59.160 --> 01:04:59.170 align:start position:0% everything will be just an initial 01:04:59.170 --> 01:05:01.529 align:start position:0% everything will be just an initial investment<01:04:59.819> all<01:05:00.819> these<01:05:00.970> languages<01:05:01.270> would 01:05:01.529 --> 01:05:01.539 align:start position:0% investment all these languages would 01:05:01.539 --> 01:05:02.910 align:start position:0% investment all these languages would have<01:05:01.750> to<01:05:01.900> do<01:05:01.990> quite<01:05:02.319> something 01:05:02.910 --> 01:05:02.920 align:start position:0% have to do quite something 01:05:02.920 --> 01:05:10.520 align:start position:0% have to do quite something and<01:05:03.220> then<01:05:04.030> perhaps<01:05:07.859> somebody<01:05:08.859> magical<01:05:09.420> but 01:05:10.520 --> 01:05:10.530 align:start position:0% and then perhaps somebody magical but 01:05:10.530 --> 01:05:13.980 align:start position:0% and then perhaps somebody magical but but<01:05:11.530> even<01:05:11.619> then<01:05:12.240> she<01:05:13.240> mentioned<01:05:13.390> either<01:05:13.809> it 01:05:13.980 --> 01:05:13.990 align:start position:0% but even then she mentioned either it 01:05:13.990 --> 01:05:15.660 align:start position:0% but even then she mentioned either it will<01:05:14.170> be<01:05:14.319> in<01:05:14.559> the<01:05:14.710> bytecode<01:05:14.920> invisible 01:05:15.660 --> 01:05:15.670 align:start position:0% will be in the bytecode invisible 01:05:15.670 --> 01:05:17.160 align:start position:0% will be in the bytecode invisible deployed<01:05:15.970> by<01:05:16.150> two<01:05:16.210> or<01:05:16.660> you<01:05:16.839> would<01:05:16.960> have<01:05:16.990> to 01:05:17.160 --> 01:05:17.170 align:start position:0% deployed by two or you would have to 01:05:17.170 --> 01:05:18.720 align:start position:0% deployed by two or you would have to generalize<01:05:17.530> it<01:05:17.829> out<01:05:18.010> into<01:05:18.250> some<01:05:18.490> kind<01:05:18.700> of 01:05:18.720 --> 01:05:18.730 align:start position:0% generalize it out into some kind of 01:05:18.730 --> 01:05:21.779 align:start position:0% generalize it out into some kind of library<01:05:19.349> or<01:05:20.349> by<01:05:20.799> the<01:05:20.980> end<01:05:21.130> of<01:05:21.339> it<01:05:21.490> the<01:05:21.579> same 01:05:21.779 --> 01:05:21.789 align:start position:0% library or by the end of it the same 01:05:21.789 --> 01:05:24.750 align:start position:0% library or by the end of it the same same<01:05:22.180> issues<01:05:22.630> as<01:05:23.319> we<01:05:23.500> discussed<01:05:23.859> before<01:05:24.010> so<01:05:24.700> it 01:05:24.750 --> 01:05:24.760 align:start position:0% same issues as we discussed before so it 01:05:24.760 --> 01:05:26.849 align:start position:0% same issues as we discussed before so it seems<01:05:25.030> to<01:05:25.150> be<01:05:25.299> all<01:05:25.450> of<01:05:25.539> these<01:05:25.750> you<01:05:26.619> want<01:05:26.799> to 01:05:26.849 --> 01:05:26.859 align:start position:0% seems to be all of these you want to 01:05:26.859 --> 01:05:28.470 align:start position:0% seems to be all of these you want to change<01:05:27.069> a<01:05:27.160> tiny<01:05:27.400> thing<01:05:27.640> and<01:05:27.670> you<01:05:27.940> you<01:05:28.270> have 01:05:28.470 --> 01:05:28.480 align:start position:0% change a tiny thing and you you have 01:05:28.480 --> 01:05:39.620 align:start position:0% change a tiny thing and you you have suddenly<01:05:28.809> a<01:05:29.079> bunch<01:05:29.559> of<01:05:29.650> every<01:05:30.270> primitive 01:05:39.620 --> 01:05:39.630 align:start position:0% 01:05:39.630 --> 01:05:43.289 align:start position:0% well<01:05:40.630> let's<01:05:41.289> just<01:05:41.440> say<01:05:41.589> that<01:05:41.619> I<01:05:41.920> mean<01:05:42.819> all<01:05:43.089> sort 01:05:43.289 --> 01:05:43.299 align:start position:0% well let's just say that I mean all sort 01:05:43.299 --> 01:05:45.059 align:start position:0% well let's just say that I mean all sort of<01:05:43.359> being<01:05:43.450> a<01:05:43.539> page<01:05:43.720> table<01:05:43.960> that's<01:05:44.319> the<01:05:44.440> reason 01:05:45.059 --> 01:05:45.069 align:start position:0% of being a page table that's the reason 01:05:45.069 --> 01:05:46.500 align:start position:0% of being a page table that's the reason the<01:05:45.250> punch<01:05:45.430> provision<01:05:46.000> we<01:05:46.119> get<01:05:46.240> under<01:05:46.390> the 01:05:46.500 --> 01:05:46.510 align:start position:0% the punch provision we get under the 01:05:46.510 --> 01:05:47.640 align:start position:0% the punch provision we get under the eyes<01:05:46.630> in<01:05:46.779> the<01:05:46.869> beginning<01:05:47.200> impact<01:05:47.559> of 01:05:47.640 --> 01:05:47.650 align:start position:0% eyes in the beginning impact of 01:05:47.650 --> 01:05:50.069 align:start position:0% eyes in the beginning impact of expandability<01:05:48.329> we<01:05:49.329> could<01:05:49.510> write<01:05:49.690> much<01:05:49.869> more 01:05:50.069 --> 01:05:50.079 align:start position:0% expandability we could write much more 01:05:50.079 --> 01:05:52.829 align:start position:0% expandability we could write much more natural<01:05:50.529> violence<01:05:51.400> if<01:05:51.640> we<01:05:51.910> could<01:05:52.089> everybody 01:05:52.829 --> 01:05:52.839 align:start position:0% natural violence if we could everybody 01:05:52.839 --> 01:05:54.289 align:start position:0% natural violence if we could everybody into<01:05:53.109> the<01:05:53.200> stack<01:05:53.440> of<01:05:53.470> the<01:05:53.619> other<01:05:53.829> and<01:05:54.069> so<01:05:54.220> on 01:05:54.289 --> 01:05:54.299 align:start position:0% into the stack of the other and so on 01:05:54.299 --> 01:05:58.349 align:start position:0% into the stack of the other and so on just<01:05:55.299> that<01:05:55.420> this<01:05:55.510> was<01:05:56.819> marriage<01:05:57.819> bubble<01:05:58.210> is 01:05:58.349 --> 01:05:58.359 align:start position:0% just that this was marriage bubble is 01:05:58.359 --> 01:05:59.789 align:start position:0% just that this was marriage bubble is here<01:05:58.510> now<01:05:58.660> because<01:05:58.990> Bethel<01:05:59.380> was<01:05:59.440> discussing 01:05:59.789 --> 01:05:59.799 align:start position:0% here now because Bethel was discussing 01:05:59.799 --> 01:06:05.069 align:start position:0% here now because Bethel was discussing it<01:06:00.130> with<01:06:01.260> 10<01:06:02.260> weeks<01:06:02.440> ago<01:06:02.740> venules<01:06:03.430> Lee<01:06:03.579> why<01:06:04.569> my 01:06:05.069 --> 01:06:05.079 align:start position:0% it with 10 weeks ago venules Lee why my 01:06:05.079 --> 01:06:08.010 align:start position:0% it with 10 weeks ago venules Lee why my is<01:06:05.109> advantageous<01:06:05.829> and<01:06:06.180> just<01:06:07.180> wondering<01:06:07.510> if 01:06:08.010 --> 01:06:08.020 align:start position:0% is advantageous and just wondering if 01:06:08.020 --> 01:06:13.799 align:start position:0% is advantageous and just wondering if this<01:06:08.109> was<01:06:08.260> discussed<01:06:08.619> before<01:06:12.450> to<01:06:13.450> give<01:06:13.599> some 01:06:13.799 --> 01:06:13.809 align:start position:0% this was discussed before to give some 01:06:13.809 --> 01:06:17.640 align:start position:0% this was discussed before to give some background<01:06:13.839> to<01:06:14.380> you<01:06:14.799> guys<01:06:15.690> this<01:06:16.690> this<01:06:17.440> was<01:06:17.619> a 01:06:17.640 --> 01:06:17.650 align:start position:0% background to you guys this this was a 01:06:17.650 --> 01:06:19.980 align:start position:0% background to you guys this this was a discussion<01:06:18.069> on<01:06:18.369> the<01:06:18.549> solidity<01:06:19.150> def<01:06:19.630> channel 01:06:19.980 --> 01:06:19.990 align:start position:0% discussion on the solidity def channel 01:06:19.990 --> 01:06:22.230 align:start position:0% discussion on the solidity def channel which<01:06:20.140> is<01:06:20.260> open<01:06:20.529> to<01:06:20.619> anyone<01:06:20.799> to<01:06:20.920> join<01:06:21.130> its<01:06:22.059> most 01:06:22.230 --> 01:06:22.240 align:start position:0% which is open to anyone to join its most 01:06:22.240 --> 01:06:23.670 align:start position:0% which is open to anyone to join its most people<01:06:22.420> to<01:06:22.480> compiler<01:06:22.839> but<01:06:23.079> this<01:06:23.200> has<01:06:23.410> some<01:06:23.440> of 01:06:23.670 --> 01:06:23.680 align:start position:0% people to compiler but this has some of 01:06:23.680 --> 01:06:25.549 align:start position:0% people to compiler but this has some of these<01:06:23.859> kind<01:06:24.250> of<01:06:24.279> interesting<01:06:24.910> questions<01:06:25.240> and 01:06:25.549 --> 01:06:25.559 align:start position:0% these kind of interesting questions and 01:06:25.559 --> 01:06:28.470 align:start position:0% these kind of interesting questions and it's<01:06:26.559> originated<01:06:27.130> from<01:06:27.309> memory<01:06:28.150> management 01:06:28.470 --> 01:06:28.480 align:start position:0% it's originated from memory management 01:06:28.480 --> 01:06:32.519 align:start position:0% it's originated from memory management anybody's<01:06:29.079> finished<01:06:29.380> the<01:06:29.650> compiler<01:06:30.809> I<01:06:31.809> mean 01:06:32.519 --> 01:06:32.529 align:start position:0% anybody's finished the compiler I mean 01:06:32.529 --> 01:06:34.529 align:start position:0% anybody's finished the compiler I mean in<01:06:32.740> the<01:06:32.829> context<01:06:33.279> but<01:06:33.430> it's<01:06:33.670> it's<01:06:33.910> prism<01:06:34.270> I<01:06:34.359> can 01:06:34.529 --> 01:06:34.539 align:start position:0% in the context but it's it's prism I can 01:06:34.539 --> 01:06:36.809 align:start position:0% in the context but it's it's prism I can color<01:06:34.720> and<01:06:35.020> you<01:06:35.920> can<01:06:36.069> only<01:06:36.190> expand<01:06:36.579> the<01:06:36.670> memory 01:06:36.809 --> 01:06:36.819 align:start position:0% color and you can only expand the memory 01:06:36.819 --> 01:06:41.370 align:start position:0% color and you can only expand the memory you<01:06:37.180> cannot<01:06:37.420> do<01:06:37.900> anything<01:06:38.109> else<01:06:38.460> and<01:06:39.480> in<01:06:40.480> any 01:06:41.370 --> 01:06:41.380 align:start position:0% you cannot do anything else and in any 01:06:41.380 --> 01:06:43.230 align:start position:0% you cannot do anything else and in any given<01:06:41.740> function<01:06:41.920> they<01:06:42.400> want<01:06:42.640> to<01:06:42.730> just<01:06:43.089> use 01:06:43.230 --> 01:06:43.240 align:start position:0% given function they want to just use 01:06:43.240 --> 01:06:48.120 align:start position:0% given function they want to just use temporary<01:06:43.750> memory<01:06:44.640> and<01:06:45.640> the<01:06:46.619> the<01:06:47.619> issue<01:06:47.829> was 01:06:48.120 --> 01:06:48.130 align:start position:0% temporary memory and the the issue was 01:06:48.130 --> 01:06:49.950 align:start position:0% temporary memory and the the issue was that<01:06:48.160> we<01:06:48.730> wanted<01:06:49.059> to<01:06:49.210> maybe<01:06:49.359> we<01:06:49.630> use<01:06:49.779> memory 01:06:49.950 --> 01:06:49.960 align:start position:0% that we wanted to maybe we use memory 01:06:49.960 --> 01:06:51.980 align:start position:0% that we wanted to maybe we use memory usage<01:06:50.410> because<01:06:50.680> memory<01:06:50.890> is<01:06:51.010> expensive<01:06:51.549> and 01:06:51.980 --> 01:06:51.990 align:start position:0% usage because memory is expensive and 01:06:51.990 --> 01:06:54.390 align:start position:0% usage because memory is expensive and you<01:06:52.990> want<01:06:53.140> to<01:06:53.200> await<01:06:53.589> their<01:06:53.770> temporary<01:06:54.220> memory 01:06:54.390 --> 01:06:54.400 align:start position:0% you want to await their temporary memory 01:06:54.400 --> 01:06:57.930 align:start position:0% you want to await their temporary memory but<01:06:55.210> it's<01:06:56.140> kind<01:06:56.500> of<01:06:56.650> a<01:06:56.950> challenge<01:06:57.309> if<01:06:57.670> you<01:06:57.700> want 01:06:57.930 --> 01:06:57.940 align:start position:0% but it's kind of a challenge if you want 01:06:57.940 --> 01:07:00.559 align:start position:0% but it's kind of a challenge if you want to<01:06:58.059> be<01:06:58.150> sitting<01:06:58.510> in<01:06:58.599> a<01:06:59.200> generic<01:06:59.500> way<01:06:59.710> because 01:07:00.559 --> 01:07:00.569 align:start position:0% to be sitting in a generic way because 01:07:00.569 --> 01:07:02.880 align:start position:0% to be sitting in a generic way because you<01:07:01.569> leaves<01:07:01.809> so<01:07:02.319> you<01:07:02.349> know<01:07:02.680> if<01:07:02.740> you're 01:07:02.880 --> 01:07:02.890 align:start position:0% you leaves so you know if you're 01:07:02.890 --> 01:07:05.940 align:start position:0% you leaves so you know if you're starting<01:07:03.220> memory<01:07:03.819> or<01:07:04.420> to<01:07:04.510> use<01:07:04.680> to<01:07:05.680> certain 01:07:05.940 --> 01:07:05.950 align:start position:0% starting memory or to use to certain 01:07:05.950 --> 01:07:07.890 align:start position:0% starting memory or to use to certain extent<01:07:06.250> you<01:07:06.460> get<01:07:06.940> me<01:07:07.059> to<01:07:07.180> follow<01:07:07.480> you<01:07:07.630> through 01:07:07.890 --> 01:07:07.900 align:start position:0% extent you get me to follow you through 01:07:07.900 --> 01:07:10.289 align:start position:0% extent you get me to follow you through you<01:07:08.020> want<01:07:08.140> to<01:07:08.260> interpret<01:07:08.710> memory<01:07:09.160> but<01:07:10.000> at<01:07:10.089> some 01:07:10.289 --> 01:07:10.299 align:start position:0% you want to interpret memory but at some 01:07:10.299 --> 01:07:12.720 align:start position:0% you want to interpret memory but at some point<01:07:10.329> you<01:07:10.690> may<01:07:10.839> also<01:07:11.049> want<01:07:11.260> to<01:07:11.349> store<01:07:11.730> data 01:07:12.720 --> 01:07:12.730 align:start position:0% point you may also want to store data 01:07:12.730 --> 01:07:15.480 align:start position:0% point you may also want to store data which<01:07:13.059> wouldn't<01:07:13.510> be<01:07:13.569> temporary<01:07:14.049> and<01:07:14.529> it 01:07:15.480 --> 01:07:15.490 align:start position:0% which wouldn't be temporary and it 01:07:15.490 --> 01:07:17.130 align:start position:0% which wouldn't be temporary and it becomes<01:07:15.789> a<01:07:15.880> challenge<01:07:16.089> but<01:07:16.299> if<01:07:16.420> you<01:07:16.630> have<01:07:16.839> page 01:07:17.130 --> 01:07:17.140 align:start position:0% becomes a challenge but if you have page 01:07:17.140 --> 01:07:19.569 align:start position:0% becomes a challenge but if you have page tables<01:07:17.589> then<01:07:17.890> that<01:07:18.819> you<01:07:18.970> can 01:07:19.569 --> 01:07:19.579 align:start position:0% tables then that you can 01:07:19.579 --> 01:07:21.949 align:start position:0% tables then that you can it<01:07:20.579> goes<01:07:20.789> to<01:07:20.999> me<01:07:21.089> for<01:07:21.239> some<01:07:21.390> reason<01:07:21.689> I<01:07:21.749> knew 01:07:21.949 --> 01:07:21.959 align:start position:0% it goes to me for some reason I knew 01:07:21.959 --> 01:07:23.390 align:start position:0% it goes to me for some reason I knew this<01:07:22.109> very<01:07:22.259> moment<01:07:22.559> that<01:07:22.799> we<01:07:22.979> could<01:07:23.189> actually 01:07:23.390 --> 01:07:23.400 align:start position:0% this very moment that we could actually 01:07:23.400 --> 01:07:26.420 align:start position:0% this very moment that we could actually change<01:07:24.089> that<01:07:24.559> without<01:07:25.559> big<01:07:25.920> impact<01:07:26.279> on 01:07:26.420 --> 01:07:26.430 align:start position:0% change that without big impact on 01:07:26.430 --> 01:07:28.729 align:start position:0% change that without big impact on existing<01:07:26.549> contracts<01:07:27.390> because<01:07:27.900> if<01:07:28.199> we<01:07:28.349> using 01:07:28.729 --> 01:07:28.739 align:start position:0% existing contracts because if we using 01:07:28.739 --> 01:07:30.499 align:start position:0% existing contracts because if we using page<01:07:28.920> tables<01:07:29.369> and<01:07:29.579> we<01:07:29.699> have<01:07:29.789> the<01:07:29.880> same<01:07:30.119> guest 01:07:30.499 --> 01:07:30.509 align:start position:0% page tables and we have the same guest 01:07:30.509 --> 01:07:32.150 align:start position:0% page tables and we have the same guest cost<01:07:30.809> of<01:07:30.989> letters<01:07:31.319> will<01:07:31.499> announce<01:07:31.680> memory<01:07:32.039> you 01:07:32.150 --> 01:07:32.160 align:start position:0% cost of letters will announce memory you 01:07:32.160 --> 01:07:34.249 align:start position:0% cost of letters will announce memory you use<01:07:32.339> it<01:07:32.519> throughout<01:07:32.759> look<01:07:33.089> the<01:07:33.539> first<01:07:33.689> invites 01:07:34.249 --> 01:07:34.259 align:start position:0% use it throughout look the first invites 01:07:34.259 --> 01:07:36.499 align:start position:0% use it throughout look the first invites the<01:07:35.069> existing<01:07:35.489> contracts<01:07:35.910> are<01:07:36.059> continue<01:07:36.420> to 01:07:36.499 --> 01:07:36.509 align:start position:0% the existing contracts are continue to 01:07:36.509 --> 01:07:37.819 align:start position:0% the existing contracts are continue to operate<01:07:36.660> the<01:07:36.900> way<01:07:36.930> they<01:07:37.019> are<01:07:37.289> but<01:07:37.529> new 01:07:37.819 --> 01:07:37.829 align:start position:0% operate the way they are but new 01:07:37.829 --> 01:07:39.469 align:start position:0% operate the way they are but new contracts<01:07:38.339> that<01:07:38.459> take<01:07:38.609> advantage<01:07:38.759> of<01:07:39.150> effect 01:07:39.469 --> 01:07:39.479 align:start position:0% contracts that take advantage of effect 01:07:39.479 --> 01:07:42.109 align:start position:0% contracts that take advantage of effect it<01:07:39.689> suddenly<01:07:39.959> think<01:07:40.229> of<01:07:40.289> right<01:07:40.529> to<01:07:40.880> take<01:07:41.880> off 01:07:42.109 --> 01:07:42.119 align:start position:0% it suddenly think of right to take off 01:07:42.119 --> 01:07:42.739 align:start position:0% it suddenly think of right to take off something 01:07:42.739 --> 01:07:42.749 align:start position:0% something 01:07:42.749 --> 01:07:46.309 align:start position:0% something Steve<01:07:43.380> proposal<01:07:44.069> Daniel<01:07:44.999> came<01:07:45.180> up<01:07:45.329> with<01:07:45.539> a 01:07:46.309 --> 01:07:46.319 align:start position:0% Steve proposal Daniel came up with a 01:07:46.319 --> 01:07:48.079 align:start position:0% Steve proposal Daniel came up with a special<01:07:46.380> so<01:07:46.979> we<01:07:47.099> took<01:07:47.249> the<01:07:47.489> memory<01:07:47.609> page<01:07:47.910> the 01:07:48.079 --> 01:07:48.089 align:start position:0% special so we took the memory page the 01:07:48.089 --> 01:07:51.890 align:start position:0% special so we took the memory page the most<01:07:48.269> that<01:07:48.930> you<01:07:48.959> know<01:07:50.299> the<01:07:51.299> proposal<01:07:51.719> was<01:07:51.839> to 01:07:51.890 --> 01:07:51.900 align:start position:0% most that you know the proposal was to 01:07:51.900 --> 01:07:54.739 align:start position:0% most that you know the proposal was to maybe<01:07:52.140> use<01:07:52.380> some<01:07:52.410> hybrids<01:07:52.979> of<01:07:53.160> the<01:07:53.239> the<01:07:54.239> offset 01:07:54.739 --> 01:07:54.749 align:start position:0% maybe use some hybrids of the the offset 01:07:54.749 --> 01:07:58.309 align:start position:0% maybe use some hybrids of the the offset the<01:07:55.709> page<01:07:56.130> table<01:07:56.930> so<01:07:57.930> what's<01:07:58.109> your<01:07:58.229> opinion 01:07:58.309 --> 01:07:58.319 align:start position:0% the page table so what's your opinion 01:07:58.319 --> 01:08:20.329 align:start position:0% the page table so what's your opinion don't<01:07:58.739> know<01:07:58.979> about<01:07:59.549> the<01:07:59.759> high<01:07:59.939> bid<01:08:00.209> well<01:08:19.339> you 01:08:20.329 --> 01:08:20.339 align:start position:0% don't know about the high bid well you 01:08:20.339 --> 01:08:23.180 align:start position:0% don't know about the high bid well you don't<01:08:20.639> I<01:08:20.759> think<01:08:20.790> like<01:08:21.119> do<01:08:21.329> we<01:08:21.540> like<01:08:21.900> but<01:08:22.559> a<01:08:22.829> lot 01:08:23.180 --> 01:08:23.190 align:start position:0% don't I think like do we like but a lot 01:08:23.190 --> 01:08:25.609 align:start position:0% don't I think like do we like but a lot of<01:08:23.219> nice<01:08:23.819> features<01:08:24.059> to<01:08:24.270> have<01:08:24.599> but<01:08:25.109> I<01:08:25.290> am<01:08:25.469> sure 01:08:25.609 --> 01:08:25.619 align:start position:0% of nice features to have but I am sure 01:08:25.619 --> 01:08:31.930 align:start position:0% of nice features to have but I am sure it's<01:08:25.829> practical<01:08:26.489> to<01:08:27.089> use<01:08:27.529> so<01:08:28.529> like 01:08:31.930 --> 01:08:31.940 align:start position:0% 01:08:31.940 --> 01:08:36.789 align:start position:0% do<01:08:32.029> it<01:08:33.279> in<01:08:34.279> the<01:08:34.430> way<01:08:34.549> it<01:08:34.580> up<01:08:34.989> between<01:08:35.989> or<01:08:36.410> affect 01:08:36.789 --> 01:08:36.799 align:start position:0% do it in the way it up between or affect 01:08:36.799 --> 01:08:47.200 align:start position:0% do it in the way it up between or affect existing<01:08:36.949> contracts<01:08:44.739> the<01:08:45.739> hybrids<01:08:46.370> are<01:08:46.609> kind 01:08:47.200 --> 01:08:47.210 align:start position:0% existing contracts the hybrids are kind 01:08:47.210 --> 01:08:50.729 align:start position:0% existing contracts the hybrids are kind of<01:08:47.299> I<01:08:47.569> don't<01:08:47.960> like<01:08:48.140> using<01:08:48.380> habits<01:08:49.009> within<01:08:49.580> the 01:08:50.729 --> 01:08:50.739 align:start position:0% of I don't like using habits within the 01:08:50.739 --> 01:08:59.229 align:start position:0% of I don't like using habits within the average<01:08:51.739> 56<01:08:52.489> values<01:08:57.400> when<01:08:58.400> you<01:08:58.430> implement 01:08:59.229 --> 01:08:59.239 align:start position:0% average 56 values when you implement 01:08:59.239 --> 01:09:01.450 align:start position:0% average 56 values when you implement stuff<01:08:59.750> you<01:08:59.960> actually<01:09:00.049> can<01:09:00.410> just<01:09:00.770> trim<01:09:01.100> it<01:09:01.250> to 01:09:01.450 --> 01:09:01.460 align:start position:0% stuff you actually can just trim it to 01:09:01.460 --> 01:09:04.870 align:start position:0% stuff you actually can just trim it to like<01:09:01.609> 32<01:09:02.150> bits<01:09:03.080> of<01:09:03.410> memory<01:09:03.469> access<01:09:04.310> and<01:09:04.580> then<01:09:04.850> I 01:09:04.870 --> 01:09:04.880 align:start position:0% like 32 bits of memory access and then I 01:09:04.880 --> 01:09:07.240 align:start position:0% like 32 bits of memory access and then I have<01:09:05.210> to<01:09:05.390> actually<01:09:05.540> consider<01:09:06.049> the<01:09:06.440> upper<01:09:06.589> of 01:09:07.240 --> 01:09:07.250 align:start position:0% have to actually consider the upper of 01:09:07.250 --> 01:09:11.650 align:start position:0% have to actually consider the upper of your<01:09:07.489> fixer-upper<01:09:07.989> like<01:09:09.219> part<01:09:10.219> of<01:09:10.430> the<01:09:10.660> value 01:09:11.650 --> 01:09:11.660 align:start position:0% your fixer-upper like part of the value 01:09:11.660 --> 01:09:14.499 align:start position:0% your fixer-upper like part of the value maybe<01:09:12.440> it's<01:09:12.650> also<01:09:12.830> big<01:09:13.160> deal<01:09:13.400> with<01:09:14.060> I<01:09:14.089> usually 01:09:14.499 --> 01:09:14.509 align:start position:0% maybe it's also big deal with I usually 01:09:14.509 --> 01:09:16.720 align:start position:0% maybe it's also big deal with I usually do<01:09:14.660> when<01:09:14.930> there<01:09:15.140> is<01:09:15.230> no<01:09:15.380> proposal<01:09:15.650> I<01:09:16.310> try<01:09:16.670> to 01:09:16.720 --> 01:09:16.730 align:start position:0% do when there is no proposal I try to 01:09:16.730 --> 01:09:19.150 align:start position:0% do when there is no proposal I try to make<01:09:17.089> a<01:09:17.299> prototype<01:09:17.569> implementation<01:09:18.109> and<01:09:18.859> then 01:09:19.150 --> 01:09:19.160 align:start position:0% make a prototype implementation and then 01:09:19.160 --> 01:09:26.229 align:start position:0% make a prototype implementation and then I<01:09:19.190> can<01:09:19.489> actually<01:09:19.640> comment<01:09:20.120> how<01:09:23.380> so<01:09:25.239> maybe 01:09:26.229 --> 01:09:26.239 align:start position:0% I can actually comment how so maybe 01:09:26.239 --> 01:09:30.670 align:start position:0% I can actually comment how so maybe there's<01:09:26.540> a<01:09:26.660> way<01:09:26.779> to<01:09:26.810> kind<01:09:27.230> of<01:09:27.380> come<01:09:28.190> up<01:09:29.500> but<01:09:30.500> I 01:09:30.670 --> 01:09:30.680 align:start position:0% there's a way to kind of come up but I 01:09:30.680 --> 01:09:33.459 align:start position:0% there's a way to kind of come up but I don't<01:09:30.830> like<01:09:31.130> my<01:09:32.029> first<01:09:32.480> choice<01:09:32.989> would<01:09:33.230> be<01:09:33.259> to 01:09:33.459 --> 01:09:33.469 align:start position:0% don't like my first choice would be to 01:09:33.469 --> 01:09:36.459 align:start position:0% don't like my first choice would be to use<01:09:33.770> the<01:09:34.759> even<01:09:35.180> if<01:09:35.330> you<01:09:35.480> have<01:09:35.690> some<01:09:35.930> like<01:09:36.199> bit 01:09:36.459 --> 01:09:36.469 align:start position:0% use the even if you have some like bit 01:09:36.469 --> 01:09:39.130 align:start position:0% use the even if you have some like bit mesquite<01:09:37.009> and<01:09:37.190> like<01:09:37.839> differentiate<01:09:38.839> like 01:09:39.130 --> 01:09:39.140 align:start position:0% mesquite and like differentiate like 01:09:39.140 --> 01:10:21.310 align:start position:0% mesquite and like differentiate like addresses 01:10:21.310 --> 01:10:21.320 align:start position:0% 01:10:21.320 --> 01:10:43.350 align:start position:0% [Music] 01:10:43.350 --> 01:10:43.360 align:start position:0% 01:10:43.360 --> 01:10:51.130 align:start position:0% first<01:10:43.990> one<01:10:44.200> that<01:10:44.380> was 01:10:51.130 --> 01:10:51.140 align:start position:0% 01:10:51.140 --> 01:10:54.220 align:start position:0% so<01:10:52.140> one<01:10:52.380> of<01:10:52.410> the<01:10:52.530> questions<01:10:52.650> we<01:10:53.430> have<01:10:53.580> here<01:10:53.850> is 01:10:54.220 --> 01:10:54.230 align:start position:0% so one of the questions we have here is 01:10:54.230 --> 01:10:56.540 align:start position:0% so one of the questions we have here is which<01:10:55.230> still<01:10:55.530> relates<01:10:55.860> to<01:10:56.010> the<01:10:56.160> earlier 01:10:56.540 --> 01:10:56.550 align:start position:0% which still relates to the earlier 01:10:56.550 --> 01:11:00.620 align:start position:0% which still relates to the earlier discussion<01:10:57.320> on<01:10:58.850> stateless<01:10:59.850> contracts 01:11:00.620 --> 01:11:00.630 align:start position:0% discussion on stateless contracts 01:11:00.630 --> 01:11:03.260 align:start position:0% discussion on stateless contracts why<01:11:01.260> are<01:11:01.470> zero<01:11:01.770> bytes<01:11:02.070> in<01:11:02.310> the<01:11:02.490> transaction<01:11:03.090> if 01:11:03.260 --> 01:11:03.270 align:start position:0% why are zero bytes in the transaction if 01:11:03.270 --> 01:11:11.740 align:start position:0% why are zero bytes in the transaction if cheaper<01:11:03.780> than<01:11:04.110> one<01:11:04.350> Z<01:11:04.500> of<01:11:04.620> X<01:11:04.800> there<01:11:05.460> are 01:11:11.740 --> 01:11:11.750 align:start position:0% 01:11:11.750 --> 01:11:16.430 align:start position:0% already<01:11:12.750> present<01:11:14.900> no<01:11:15.900> maybe<01:11:16.200> they<01:11:16.380> were 01:11:16.430 --> 01:11:16.440 align:start position:0% already present no maybe they were 01:11:16.440 --> 01:11:29.420 align:start position:0% already present no maybe they were thumbs<01:11:16.770> sixteen<01:11:17.340> from<01:11:17.610> sixty<01:11:18.000> but<01:11:18.690> only<01:11:28.430> yeah 01:11:29.420 --> 01:11:29.430 align:start position:0% thumbs sixteen from sixty but only yeah 01:11:29.430 --> 01:11:33.140 align:start position:0% thumbs sixteen from sixty but only yeah so<01:11:29.880> so<01:11:30.360> okay<01:11:30.690> so<01:11:31.100> context<01:11:32.100> around<01:11:32.220> this<01:11:32.460> and 01:11:33.140 --> 01:11:33.150 align:start position:0% so so okay so context around this and 01:11:33.150 --> 01:11:34.730 align:start position:0% so so okay so context around this and it's<01:11:33.300> in<01:11:33.390> a<01:11:33.420> transaction<01:11:33.840> it<01:11:34.560> has 01:11:34.730 --> 01:11:34.740 align:start position:0% it's in a transaction it has 01:11:34.740 --> 01:11:37.220 align:start position:0% it's in a transaction it has historically<01:11:35.280> been<01:11:35.340> the<01:11:35.490> case<01:11:35.760> that<01:11:36.270> the<01:11:36.750> data 01:11:37.220 --> 01:11:37.230 align:start position:0% historically been the case that the data 01:11:37.230 --> 01:11:39.860 align:start position:0% historically been the case that the data that<01:11:37.560> goes<01:11:37.950> into<01:11:38.220> transaction<01:11:38.910> I<01:11:39.090> think<01:11:39.660> that 01:11:39.860 --> 01:11:39.870 align:start position:0% that goes into transaction I think that 01:11:39.870 --> 01:11:43.090 align:start position:0% that goes into transaction I think that if<01:11:40.200> it's<01:11:40.500> the<01:11:41.250> bike<01:11:41.460> is<01:11:41.700> zero<01:11:42.030> it<01:11:42.390> was<01:11:42.600> before 01:11:43.090 --> 01:11:43.100 align:start position:0% if it's the bike is zero it was before 01:11:43.100 --> 01:11:48.380 align:start position:0% if it's the bike is zero it was before and<01:11:44.100> if<01:11:44.280> it's<01:11:44.490> nonzero<01:11:45.090> it<01:11:45.270> was<01:11:45.480> 68<01:11:46.260> gasps<01:11:47.390> now 01:11:48.380 --> 01:11:48.390 align:start position:0% and if it's nonzero it was 68 gasps now 01:11:48.390 --> 01:11:54.190 align:start position:0% and if it's nonzero it was 68 gasps now for<01:11:48.750> calls<01:11:49.320> that<01:11:49.740> happen<01:11:50.010> within<01:11:52.490> within<01:11:53.490> yeah 01:11:54.190 --> 01:11:54.200 align:start position:0% for calls that happen within within yeah 01:11:54.200 --> 01:11:56.450 align:start position:0% for calls that happen within within yeah with<01:11:55.200> it<01:11:55.350> from<01:11:55.560> a<01:11:55.620> contract<01:11:56.160> to<01:11:56.280> another 01:11:56.450 --> 01:11:56.460 align:start position:0% with it from a contract to another 01:11:56.460 --> 01:11:59.920 align:start position:0% with it from a contract to another contract<01:11:57.060> there<01:11:57.600> is<01:11:57.630> no<01:11:57.930> such<01:11:58.370> distinction 01:11:59.920 --> 01:11:59.930 align:start position:0% contract there is no such distinction 01:11:59.930 --> 01:12:06.380 align:start position:0% contract there is no such distinction what<01:12:00.930> you<01:12:01.290> pay<01:12:01.530> for<01:12:01.730> is<01:12:02.730> memory<01:12:03.450> expansion<01:12:05.390> if 01:12:06.380 --> 01:12:06.390 align:start position:0% what you pay for is memory expansion if 01:12:06.390 --> 01:12:12.410 align:start position:0% what you pay for is memory expansion if the<01:12:07.140> memory<01:12:07.560> expansion<01:12:07.890> address<01:12:11.180> sorry<01:12:12.180> I 01:12:12.410 --> 01:12:12.420 align:start position:0% the memory expansion address sorry I 01:12:12.420 --> 01:12:15.890 align:start position:0% the memory expansion address sorry I mean<01:12:12.660> you<01:12:12.750> can<01:12:12.900> send<01:12:13.290> a<01:12:13.620> long<01:12:14.870> megabyte<01:12:15.870> of 01:12:15.890 --> 01:12:15.900 align:start position:0% mean you can send a long megabyte of 01:12:15.900 --> 01:12:18.890 align:start position:0% mean you can send a long megabyte of data<01:12:16.140> but<01:12:16.800> not<01:12:16.980> actually<01:12:17.400> cost<01:12:18.120> anything<01:12:18.690> in 01:12:18.890 --> 01:12:18.900 align:start position:0% data but not actually cost anything in 01:12:18.900 --> 01:12:20.690 align:start position:0% data but not actually cost anything in the<01:12:19.140> gasps<01:12:19.380> if<01:12:19.710> you<01:12:19.860> have<01:12:19.950> already<01:12:20.430> expanded 01:12:20.690 --> 01:12:20.700 align:start position:0% the gasps if you have already expanded 01:12:20.700 --> 01:12:26.390 align:start position:0% the gasps if you have already expanded the<01:12:21.030> number<01:12:21.060> to<01:12:21.480> that<01:12:21.690> megabyte<01:12:24.770> yeah<01:12:25.800> so<01:12:26.130> with 01:12:26.390 --> 01:12:26.400 align:start position:0% the number to that megabyte yeah so with 01:12:26.400 --> 01:12:28.520 align:start position:0% the number to that megabyte yeah so with this<01:12:26.550> double<01:12:26.940> we're<01:12:27.270> lowering<01:12:27.510> with<01:12:28.140> this 01:12:28.520 --> 01:12:28.530 align:start position:0% this double we're lowering with this 01:12:28.530 --> 01:12:31.130 align:start position:0% this double we're lowering with this post<01:12:28.890> of<01:12:29.070> 68<01:12:29.610> which<01:12:30.150> those<01:12:30.480> are<01:12:30.660> some<01:12:30.900> of<01:12:31.050> the 01:12:31.130 --> 01:12:31.140 align:start position:0% post of 68 which those are some of the 01:12:31.140 --> 01:12:32.510 align:start position:0% post of 68 which those are some of the outermost 01:12:32.510 --> 01:12:32.520 align:start position:0% outermost 01:12:32.520 --> 01:12:38.240 align:start position:0% outermost it's<01:12:32.640> actually<01:12:33.000> lowering<01:12:33.480> it<01:12:33.600> to<01:12:33.630> 16<01:12:36.680> and<01:12:37.680> the 01:12:38.240 --> 01:12:38.250 align:start position:0% it's actually lowering it to 16 and the 01:12:38.250 --> 01:12:41.140 align:start position:0% it's actually lowering it to 16 and the initial<01:12:38.910> reasoning<01:12:39.390> to<01:12:39.600> have<01:12:39.750> a<01:12:39.780> different 01:12:41.140 --> 01:12:41.150 align:start position:0% initial reasoning to have a different 01:12:41.150 --> 01:13:29.840 align:start position:0% initial reasoning to have a different between<01:13:28.100> otherwise<01:13:29.100> there<01:13:29.460> would<01:13:29.580> have<01:13:29.670> to<01:13:29.760> be 01:13:29.840 --> 01:13:29.850 align:start position:0% between otherwise there would have to be 01:13:29.850 --> 01:13:32.060 align:start position:0% between otherwise there would have to be a<01:13:30.000> more<01:13:30.540> intricate<01:13:30.900> scheme<01:13:31.200> to<01:13:31.620> figure<01:13:31.950> out 01:13:32.060 --> 01:13:32.070 align:start position:0% a more intricate scheme to figure out 01:13:32.070 --> 01:13:35.470 align:start position:0% a more intricate scheme to figure out the<01:13:32.250> time<01:13:32.430> also<01:13:32.850> when<01:13:33.030> you<01:13:33.150> have<01:13:33.560> added<01:13:34.560> data 01:13:35.470 --> 01:13:35.480 align:start position:0% the time also when you have added data 01:13:35.480 --> 01:13:39.640 align:start position:0% the time also when you have added data suppose 01:13:39.640 --> 01:13:39.650 align:start position:0% 01:13:39.650 --> 01:13:51.740 align:start position:0% [Music] 01:13:51.740 --> 01:13:51.750 align:start position:0% 01:13:51.750 --> 01:13:59.270 align:start position:0% [Music] 01:13:59.270 --> 01:13:59.280 align:start position:0% 01:13:59.280 --> 01:14:02.240 align:start position:0% all<01:14:00.280> right<01:14:00.400> we<01:14:00.580> have<01:14:00.820> another<01:14:01.000> question 01:14:02.240 --> 01:14:02.250 align:start position:0% all right we have another question 01:14:02.250 --> 01:14:04.410 align:start position:0% all right we have another question stimulating<01:14:03.250> talk<01:14:03.369> about<01:14:03.610> pricing<01:14:04.090> and<01:14:04.179> we 01:14:04.410 --> 01:14:04.420 align:start position:0% stimulating talk about pricing and we 01:14:04.420 --> 01:14:06.689 align:start position:0% stimulating talk about pricing and we kind<01:14:04.690> of<01:14:04.980> explored<01:14:05.980> and<01:14:06.159> nothing<01:14:06.400> somebody 01:14:06.689 --> 01:14:06.699 align:start position:0% kind of explored and nothing somebody 01:14:06.699 --> 01:14:08.939 align:start position:0% kind of explored and nothing somebody wanted<01:14:07.000> to<01:14:07.060> ask<01:14:07.179> that<01:14:07.300> question<01:14:07.690> but<01:14:07.960> should 01:14:08.939 --> 01:14:08.949 align:start position:0% wanted to ask that question but should 01:14:08.949 --> 01:14:11.729 align:start position:0% wanted to ask that question but should be<01:14:09.190> should<01:14:10.060> occur<01:14:10.389> pricing<01:14:10.960> be<01:14:11.170> updated<01:14:11.619> every 01:14:11.729 --> 01:14:11.739 align:start position:0% be should occur pricing be updated every 01:14:11.739 --> 01:14:15.479 align:start position:0% be should occur pricing be updated every hard<01:14:12.310> work<01:14:13.020> using<01:14:14.020> some<01:14:14.230> benchmarks<01:14:14.800> so 01:14:15.479 --> 01:14:15.489 align:start position:0% hard work using some benchmarks so 01:14:15.489 --> 01:14:18.479 align:start position:0% hard work using some benchmarks so should<01:14:15.699> we<01:14:15.730> always<01:14:16.060> be<01:14:16.210> priced<01:14:16.770> things<01:14:17.770> to<01:14:18.310> do 01:14:18.479 --> 01:14:18.489 align:start position:0% should we always be priced things to do 01:14:18.489 --> 01:14:22.320 align:start position:0% should we always be priced things to do what<01:14:18.730> they<01:14:18.940> are<01:14:19.270> at<01:14:19.570> that<01:14:20.880> we<01:14:21.880> do<01:14:22.030> seem<01:14:22.179> to<01:14:22.210> have 01:14:22.320 --> 01:14:22.330 align:start position:0% what they are at that we do seem to have 01:14:22.330 --> 01:14:27.950 align:start position:0% what they are at that we do seem to have like<01:14:22.659> a<01:14:22.690> solid<01:14:23.530> benchmarks<01:14:24.070> it<01:14:24.159> always<01:14:24.340> gone 01:14:27.950 --> 01:14:27.960 align:start position:0% 01:14:27.960 --> 01:14:30.510 align:start position:0% there<01:14:28.960> so<01:14:29.080> like<01:14:29.199> always<01:14:29.440> adding<01:14:29.949> things<01:14:30.280> to<01:14:30.400> it 01:14:30.510 --> 01:14:30.520 align:start position:0% there so like always adding things to it 01:14:30.520 --> 01:14:32.459 align:start position:0% there so like always adding things to it as<01:14:30.730> well<01:14:30.940> would<01:14:31.630> that<01:14:31.690> mean<01:14:31.960> we<01:14:32.110> will<01:14:32.230> needs 01:14:32.459 --> 01:14:32.469 align:start position:0% as well would that mean we will needs 01:14:32.469 --> 01:14:36.260 align:start position:0% as well would that mean we will needs fixed<01:14:33.460> set<01:14:33.550> of<01:14:33.580> benchmarks<01:14:33.940> first<01:14:34.420> which<01:14:35.409> case 01:14:36.260 --> 01:14:36.270 align:start position:0% fixed set of benchmarks first which case 01:14:36.270 --> 01:14:38.609 align:start position:0% fixed set of benchmarks first which case so<01:14:37.270> what<01:14:37.389> I<01:14:37.420> think<01:14:37.659> still<01:14:37.929> like<01:14:38.110> we<01:14:38.320> have<01:14:38.500> to 01:14:38.609 --> 01:14:38.619 align:start position:0% so what I think still like we have to 01:14:38.619 --> 01:14:42.180 align:start position:0% so what I think still like we have to split<01:14:38.860> like<01:14:39.210> state<01:14:40.210> axes<01:14:40.719> of<01:14:41.020> curves<01:14:41.920> and 01:14:42.180 --> 01:14:42.190 align:start position:0% split like state axes of curves and 01:14:42.190 --> 01:14:44.640 align:start position:0% split like state axes of curves and computation<01:14:42.880> of<01:14:43.090> curves<01:14:43.360> I<01:14:43.570> think<01:14:43.810> that<01:14:44.110> they 01:14:44.640 --> 01:14:44.650 align:start position:0% computation of curves I think that they 01:14:44.650 --> 01:14:48.180 align:start position:0% computation of curves I think that they should<01:14:44.679> be<01:14:45.330> addressed<01:14:46.330> differently<01:14:47.190> actually 01:14:48.180 --> 01:14:48.190 align:start position:0% should be addressed differently actually 01:14:48.190 --> 01:14:51.090 align:start position:0% should be addressed differently actually has<01:14:48.369> something<01:14:48.790> like<01:14:49.320> remind<01:14:50.320> some<01:14:50.560> idea<01:14:50.860> how 01:14:51.090 --> 01:14:51.100 align:start position:0% has something like remind some idea how 01:14:51.100 --> 01:14:55.020 align:start position:0% has something like remind some idea how to<01:14:51.159> make<01:14:51.900> maybe<01:14:52.900> try<01:14:53.440> to<01:14:53.610> evaluate<01:14:54.610> a 01:14:55.020 --> 01:14:55.030 align:start position:0% to make maybe try to evaluate a 01:14:55.030 --> 01:14:57.629 align:start position:0% to make maybe try to evaluate a computation<01:14:55.840> of<01:14:55.960> course<01:14:56.290> a<01:14:56.409> more<01:14:56.650> systematic 01:14:57.629 --> 01:14:57.639 align:start position:0% computation of course a more systematic 01:14:57.639 --> 01:15:00.040 align:start position:0% computation of course a more systematic way<01:14:57.690> to<01:14:58.690> actually<01:14:58.810> have<01:14:58.989> some<01:14:59.409> kind<01:14:59.590> of 01:15:00.040 --> 01:15:00.050 align:start position:0% way to actually have some kind of 01:15:00.050 --> 01:15:05.170 align:start position:0% way to actually have some kind of a<01:15:00.080> bench<01:15:00.350> -<01:15:00.590> to<01:15:00.830> remind<01:15:03.730> these<01:15:04.730> will<01:15:04.940> tell 01:15:05.170 --> 01:15:05.180 align:start position:0% a bench - to remind these will tell 01:15:05.180 --> 01:15:07.000 align:start position:0% a bench - to remind these will tell something<01:15:05.480> like<01:15:05.780> a<01:15:05.810> script<01:15:06.290> to<01:15:06.530> reproduce 01:15:07.000 --> 01:15:07.010 align:start position:0% something like a script to reproduce 01:15:07.010 --> 01:15:10.270 align:start position:0% something like a script to reproduce Jenkins<01:15:08.000> yeah<01:15:08.870> I<01:15:09.050> mean<01:15:09.200> that's<01:15:09.920> what<01:15:10.040> the<01:15:10.100> hard 01:15:10.270 --> 01:15:10.280 align:start position:0% Jenkins yeah I mean that's what the hard 01:15:10.280 --> 01:15:13.420 align:start position:0% Jenkins yeah I mean that's what the hard part<01:15:10.490> right<01:15:10.670> our<01:15:11.240> part<01:15:11.540> is<01:15:11.630> designing<01:15:12.560> yeah 01:15:13.420 --> 01:15:13.430 align:start position:0% part right our part is designing yeah 01:15:13.430 --> 01:15:15.790 align:start position:0% part right our part is designing yeah benchmark<01:15:14.090> analysis<01:15:14.570> like<01:15:14.690> the<01:15:14.870> one<01:15:15.020> Martin 01:15:15.790 --> 01:15:15.800 align:start position:0% benchmark analysis like the one Martin 01:15:15.800 --> 01:15:19.900 align:start position:0% benchmark analysis like the one Martin did<01:15:15.980> or<01:15:17.650> against<01:15:18.650> among<01:15:18.980> to<01:15:19.160> determine<01:15:19.790> that 01:15:19.900 --> 01:15:19.910 align:start position:0% did or against among to determine that 01:15:19.910 --> 01:15:22.630 align:start position:0% did or against among to determine that estimate<01:15:20.300> was<01:15:20.570> commander<01:15:21.440> price<01:15:21.650> that<01:15:22.040> the 01:15:22.630 --> 01:15:22.640 align:start position:0% estimate was commander price that the 01:15:22.640 --> 01:15:25.930 align:start position:0% estimate was commander price that the one<01:15:22.760> that<01:15:22.940> these<01:15:23.210> guys<01:15:24.110> did<01:15:24.550> the<01:15:25.550> paper<01:15:25.760> they 01:15:25.930 --> 01:15:25.940 align:start position:0% one that these guys did the paper they 01:15:25.940 --> 01:15:30.520 align:start position:0% one that these guys did the paper they came<01:15:26.120> on<01:15:26.270> 72<01:15:27.110> second<01:15:27.440> walks<01:15:28.570> okay<01:15:29.570> so<01:15:30.350> you<01:15:30.440> know 01:15:30.520 --> 01:15:30.530 align:start position:0% came on 72 second walks okay so you know 01:15:30.530 --> 01:15:31.990 align:start position:0% came on 72 second walks okay so you know once<01:15:30.920> we<01:15:31.040> have<01:15:31.190> those<01:15:31.370> then<01:15:31.640> you<01:15:31.760> know<01:15:31.850> we<01:15:31.970> can 01:15:31.990 --> 01:15:32.000 align:start position:0% once we have those then you know we can 01:15:32.000 --> 01:15:33.760 align:start position:0% once we have those then you know we can start<01:15:32.300> repeating<01:15:33.050> and<01:15:33.230> systematically 01:15:33.760 --> 01:15:33.770 align:start position:0% start repeating and systematically 01:15:33.770 --> 01:15:35.770 align:start position:0% start repeating and systematically running<01:15:34.070> these<01:15:34.160> benchmarks<01:15:34.700> but<01:15:34.850> haven't 01:15:35.770 --> 01:15:35.780 align:start position:0% running these benchmarks but haven't 01:15:35.780 --> 01:15:41.920 align:start position:0% running these benchmarks but haven't really<01:15:35.960> had<01:15:36.250> these<01:15:37.690> you<01:15:38.690> know<01:15:39.490> analyses<01:15:40.930> until 01:15:41.920 --> 01:15:41.930 align:start position:0% really had these you know analyses until 01:15:41.930 --> 01:15:43.020 align:start position:0% really had these you know analyses until quite<01:15:42.530> recently 01:15:43.020 --> 01:15:43.030 align:start position:0% quite recently 01:15:43.030 --> 01:15:47.260 align:start position:0% quite recently yeah<01:15:44.230> my<01:15:45.230> ideal<01:15:45.590> situation<01:15:46.220> would<01:15:46.670> be<01:15:46.790> like 01:15:47.260 --> 01:15:47.270 align:start position:0% yeah my ideal situation would be like 01:15:47.270 --> 01:15:49.530 align:start position:0% yeah my ideal situation would be like with<01:15:47.480> help<01:15:47.720> us<01:15:47.900> like<01:15:48.350> some<01:15:48.650> planning<01:15:48.980> to<01:15:49.280> say 01:15:49.530 --> 01:15:49.540 align:start position:0% with help us like some planning to say 01:15:49.540 --> 01:15:53.080 align:start position:0% with help us like some planning to say algorithm<01:15:50.540> or<01:15:50.690> program<01:15:51.170> deflection<01:15:51.880> you<01:15:52.880> can 01:15:53.080 --> 01:15:53.090 align:start position:0% algorithm or program deflection you can 01:15:53.090 --> 01:15:55.510 align:start position:0% algorithm or program deflection you can rather<01:15:53.330> than<01:15:53.660> in<01:15:53.900> outputs<01:15:54.650> numbers<01:15:55.100> and<01:15:55.370> then 01:15:55.510 --> 01:15:55.520 align:start position:0% rather than in outputs numbers and then 01:15:55.520 --> 01:15:58.060 align:start position:0% rather than in outputs numbers and then we<01:15:55.550> can<01:15:55.760> discuss<01:15:56.120> about<01:15:56.180> their<01:15:56.660> the<01:15:57.470> algorithm 01:15:58.060 --> 01:15:58.070 align:start position:0% we can discuss about their the algorithm 01:15:58.070 --> 01:15:59.740 align:start position:0% we can discuss about their the algorithm and<01:15:58.190> the<01:15:58.250> program<01:15:58.730> not<01:15:58.910> negative<01:15:59.420> numbers 01:15:59.740 --> 01:15:59.750 align:start position:0% and the program not negative numbers 01:15:59.750 --> 01:16:02.620 align:start position:0% and the program not negative numbers themselves<01:16:00.340> so<01:16:01.340> like<01:16:01.490> maybe<01:16:01.730> done<01:16:02.030> we<01:16:02.240> need<01:16:02.420> to 01:16:02.620 --> 01:16:02.630 align:start position:0% themselves so like maybe done we need to 01:16:02.630 --> 01:16:06.010 align:start position:0% themselves so like maybe done we need to change<01:16:02.930> the<01:16:03.170> algorithm<01:16:03.440> and<01:16:03.830> so<01:16:04.480> we<01:16:05.480> mostly 01:16:06.010 --> 01:16:06.020 align:start position:0% change the algorithm and so we mostly 01:16:06.020 --> 01:16:08.410 align:start position:0% change the algorithm and so we mostly talk<01:16:06.350> about<01:16:06.380> the<01:16:06.770> script<01:16:07.130> of<01:16:07.310> that<01:16:07.610> produced 01:16:08.410 --> 01:16:08.420 align:start position:0% talk about the script of that produced 01:16:08.420 --> 01:16:11.860 align:start position:0% talk about the script of that produced the<01:16:08.540> numbers 01:16:11.860 --> 01:16:11.870 align:start position:0% 01:16:11.870 --> 01:16:15.770 align:start position:0% that<01:16:12.870> would<01:16:13.080> be<01:16:13.260> I<01:16:13.290> think<01:16:13.410> they<01:16:13.920> do<01:16:14.600> the<01:16:15.600> best 01:16:15.770 --> 01:16:15.780 align:start position:0% that would be I think they do the best 01:16:15.780 --> 01:16:20.980 align:start position:0% that would be I think they do the best we<01:16:15.900> can<01:16:15.930> have<01:16:19.190> but<01:16:20.190> they<01:16:20.340> should<01:16:20.520> stop 01:16:20.980 --> 01:16:20.990 align:start position:0% we can have but they should stop 01:16:20.990 --> 01:16:30.940 align:start position:0% we can have but they should stop whenever<01:16:21.990> it's<01:16:22.380> doable<01:16:22.740> I<01:16:23.070> think<01:16:25.220> what<01:16:26.220> is<01:16:29.120> I 01:16:30.940 --> 01:16:30.950 align:start position:0% whenever it's doable I think what is I 01:16:30.950 --> 01:16:33.980 align:start position:0% whenever it's doable I think what is I think<01:16:31.950> that<01:16:32.070> technically<01:16:33.000> it<01:16:33.360> would<01:16:33.540> be<01:16:33.750> ideal 01:16:33.980 --> 01:16:33.990 align:start position:0% think that technically it would be ideal 01:16:33.990 --> 01:16:37.250 align:start position:0% think that technically it would be ideal to<01:16:34.530> do<01:16:34.740> repricing<01:16:35.310> set<01:16:35.850> self<01:16:36.120> as<01:16:36.360> we<01:16:36.510> can<01:16:36.810> but 01:16:37.250 --> 01:16:37.260 align:start position:0% to do repricing set self as we can but 01:16:37.260 --> 01:16:40.580 align:start position:0% to do repricing set self as we can but then<01:16:37.440> there<01:16:37.650> is<01:16:37.890> like<01:16:38.240> social<01:16:39.240> aspect<01:16:39.720> that<01:16:40.170> we 01:16:40.580 --> 01:16:40.590 align:start position:0% then there is like social aspect that we 01:16:40.590 --> 01:16:43.820 align:start position:0% then there is like social aspect that we actually<01:16:40.740> do<01:16:41.160> screw<01:16:41.460> up<01:16:42.050> for<01:16:43.050> people<01:16:43.410> when<01:16:43.740> we 01:16:43.820 --> 01:16:43.830 align:start position:0% actually do screw up for people when we 01:16:43.830 --> 01:16:45.560 align:start position:0% actually do screw up for people when we do<01:16:43.950> it<01:16:44.070> needs<01:16:44.550> to<01:16:44.700> be<01:16:44.820> done<01:16:45.000> a<01:16:45.030> little<01:16:45.210> bit<01:16:45.510> oh 01:16:45.560 --> 01:16:45.570 align:start position:0% do it needs to be done a little bit oh 01:16:45.570 --> 01:16:49.010 align:start position:0% do it needs to be done a little bit oh oh<01:16:45.930> yeah<01:16:46.620> I<01:16:47.340> didn't<01:16:48.090> think<01:16:48.120> actually<01:16:48.420> like<01:16:48.750> we 01:16:49.010 --> 01:16:49.020 align:start position:0% oh yeah I didn't think actually like we 01:16:49.020 --> 01:16:51.200 align:start position:0% oh yeah I didn't think actually like we should<01:16:49.200> actually<01:16:49.650> use<01:16:50.160> that<01:16:50.190> to<01:16:50.610> advise<01:16:50.970> and 01:16:51.200 --> 01:16:51.210 align:start position:0% should actually use that to advise and 01:16:51.210 --> 01:16:54.230 align:start position:0% should actually use that to advise and hard<01:16:51.570> work<01:16:51.810> but<01:16:52.080> these<01:16:52.410> like<01:16:52.770> check<01:16:53.280> for<01:16:53.580> yeah 01:16:54.230 --> 01:16:54.240 align:start position:0% hard work but these like check for yeah 01:16:54.240 --> 01:16:57.800 align:start position:0% hard work but these like check for yeah the<01:16:55.170> question<01:16:55.620> yeah<01:16:56.010> yeah<01:16:57.000> I've<01:16:57.270> also<01:16:57.450> missed 01:16:57.800 --> 01:16:57.810 align:start position:0% the question yeah yeah I've also missed 01:16:57.810 --> 01:17:00.710 align:start position:0% the question yeah yeah I've also missed something<01:16:58.020> like<01:16:58.670> unless<01:16:59.670> we<01:16:59.910> need<01:17:00.060> it<01:17:00.240> I<01:17:00.480> think 01:17:00.710 --> 01:17:00.720 align:start position:0% something like unless we need it I think 01:17:00.720 --> 01:17:04.970 align:start position:0% something like unless we need it I think it's<01:17:00.870> not<01:17:01.080> worth<01:17:01.350> to<01:17:01.590> do<01:17:03.470> and<01:17:04.470> for 01:17:04.970 --> 01:17:04.980 align:start position:0% it's not worth to do and for 01:17:04.980 --> 01:17:14.300 align:start position:0% it's not worth to do and for computational<01:17:11.360> on<01:17:12.360> one<01:17:12.600> side<01:17:13.220> coming<01:17:14.220> up 01:17:14.300 --> 01:17:14.310 align:start position:0% computational on one side coming up 01:17:14.310 --> 01:17:17.480 align:start position:0% computational on one side coming up distant<01:17:14.730> wall<01:17:15.680> probably<01:17:16.680> mostly<01:17:17.010> triggered 01:17:17.480 --> 01:17:17.490 align:start position:0% distant wall probably mostly triggered 01:17:17.490 --> 01:17:20.770 align:start position:0% distant wall probably mostly triggered by<01:17:17.670> usually<01:17:18.000> an<01:17:18.150> appeal<01:17:18.480> realizing<01:17:19.230> as<01:17:19.380> though 01:17:20.770 --> 01:17:20.780 align:start position:0% by usually an appeal realizing as though 01:17:20.780 --> 01:17:23.680 align:start position:0% by usually an appeal realizing as though people<01:17:21.780> were<01:17:21.960> concerned<01:17:22.470> that<01:17:22.560> it's<01:17:22.920> gonna 01:17:23.680 --> 01:17:23.690 align:start position:0% people were concerned that it's gonna 01:17:23.690 --> 01:17:26.640 align:start position:0% people were concerned that it's gonna it's<01:17:24.690> gonna<01:17:24.780> break<01:17:25.230> the<01:17:25.380> contract<01:17:25.740> or<01:17:26.070> its 01:17:26.640 --> 01:17:26.650 align:start position:0% it's gonna break the contract or its 01:17:26.650 --> 01:17:28.890 align:start position:0% it's gonna break the contract or its expensive<01:17:27.280> Widow<01:17:27.850> Sudheer<01:17:28.360> seems<01:17:28.600> to<01:17:28.750> be<01:17:28.870> a 01:17:28.890 --> 01:17:28.900 align:start position:0% expensive Widow Sudheer seems to be a 01:17:28.900 --> 01:17:31.560 align:start position:0% expensive Widow Sudheer seems to be a really<01:17:29.350> big<01:17:29.469> big<01:17:29.920> clash<01:17:30.489> between<01:17:30.730> those 01:17:31.560 --> 01:17:31.570 align:start position:0% really big big clash between those 01:17:31.570 --> 01:17:33.419 align:start position:0% really big big clash between those people<01:17:31.840> who<01:17:32.020> ride<01:17:32.260> the<01:17:32.380> clients<01:17:32.860> and<01:17:33.219> try<01:17:33.370> to 01:17:33.419 --> 01:17:33.429 align:start position:0% people who ride the clients and try to 01:17:33.429 --> 01:17:36.510 align:start position:0% people who ride the clients and try to ensure<01:17:33.670> that<01:17:34.260> passes<01:17:35.260> are<01:17:35.409> so<01:17:36.400> much 01:17:36.510 --> 01:17:36.520 align:start position:0% ensure that passes are so much 01:17:36.520 --> 01:17:38.550 align:start position:0% ensure that passes are so much reflective<01:17:37.030> to<01:17:37.150> what<01:17:37.270> is<01:17:37.420> happening<01:17:37.560> compared 01:17:38.550 --> 01:17:38.560 align:start position:0% reflective to what is happening compared 01:17:38.560 --> 01:18:06.479 align:start position:0% reflective to what is happening compared to<01:17:38.650> the<01:17:38.739> people<01:17:39.040> who<01:17:39.219> use<01:17:39.960> I<01:18:04.590> mean<01:18:05.590> you<01:18:06.250> can't 01:18:06.479 --> 01:18:06.489 align:start position:0% to the people who use I mean you can't 01:18:06.489 --> 01:18:09.270 align:start position:0% to the people who use I mean you can't really<01:18:06.580> hope<01:18:06.969> in<01:18:07.390> to<01:18:08.290> like<01:18:08.530> yeah<01:18:08.800> I<01:18:08.830> want<01:18:09.190> to 01:18:09.270 --> 01:18:09.280 align:start position:0% really hope in to like yeah I want to 01:18:09.280 --> 01:18:21.120 align:start position:0% really hope in to like yeah I want to use<01:18:09.489> some<01:18:09.850> more<01:18:10.000> expensive<01:18:19.739> going<01:18:20.739> to<01:18:20.800> deploy 01:18:21.120 --> 01:18:21.130 align:start position:0% use some more expensive going to deploy 01:18:21.130 --> 01:18:25.080 align:start position:0% use some more expensive going to deploy after<01:18:21.670> the<01:18:21.790> new<01:18:21.909> rules<01:18:23.340> I<01:18:24.340> think<01:18:24.760> you<01:18:24.850> can 01:18:25.080 --> 01:18:25.090 align:start position:0% after the new rules I think you can 01:18:25.090 --> 01:18:26.700 align:start position:0% after the new rules I think you can blackberries<01:18:25.690> plus<01:18:25.870> no<01:18:26.080> I<01:18:26.380> mean<01:18:26.590> you're 01:18:26.700 --> 01:18:26.710 align:start position:0% blackberries plus no I mean you're 01:18:26.710 --> 01:18:27.890 align:start position:0% blackberries plus no I mean you're responsible<01:18:26.830> for<01:18:27.219> whatever 01:18:27.890 --> 01:18:27.900 align:start position:0% responsible for whatever 01:18:27.900 --> 01:18:29.930 align:start position:0% responsible for whatever but<01:18:28.590> they'd<01:18:28.680> like<01:18:28.710> to<01:18:28.860> change<01:18:29.070> something<01:18:29.490> that 01:18:29.930 --> 01:18:29.940 align:start position:0% but they'd like to change something that 01:18:29.940 --> 01:18:32.540 align:start position:0% but they'd like to change something that affects<01:18:30.420> ploy<01:18:31.290> lately<01:18:31.800> it<01:18:32.070> doesn't<01:18:32.310> it<01:18:32.370> come 01:18:32.540 --> 01:18:32.550 align:start position:0% affects ploy lately it doesn't it come 01:18:32.550 --> 01:18:34.520 align:start position:0% affects ploy lately it doesn't it come down<01:18:32.760> to<01:18:32.820> on<01:18:33.300> for<01:18:33.840> the<01:18:33.930> new<01:18:34.110> version<01:18:34.290> is 01:18:34.520 --> 01:18:34.530 align:start position:0% down to on for the new version is 01:18:34.530 --> 01:18:37.130 align:start position:0% down to on for the new version is calling<01:18:34.920> a<01:18:35.250> contract<01:18:35.820> that<01:18:36.000> you<01:18:36.450> know<01:18:36.540> support 01:18:37.130 --> 01:18:37.140 align:start position:0% calling a contract that you know support 01:18:37.140 --> 01:18:40.070 align:start position:0% calling a contract that you know support with<01:18:37.260> the<01:18:37.350> over<01:18:37.650> it<01:18:37.740> so<01:18:38.700> it's<01:18:39.210> running<01:18:39.660> as<01:18:39.930> he 01:18:40.070 --> 01:18:40.080 align:start position:0% with the over it so it's running as he 01:18:40.080 --> 01:18:45.470 align:start position:0% with the over it so it's running as he answered<01:18:42.920> yeah<01:18:43.950> and<01:18:44.370> it's<01:18:44.520> difficult<01:18:44.730> like<01:18:45.330> if 01:18:45.470 --> 01:18:45.480 align:start position:0% answered yeah and it's difficult like if 01:18:45.480 --> 01:18:47.860 align:start position:0% answered yeah and it's difficult like if you<01:18:45.630> have<01:18:45.810> it<01:18:46.020> if<01:18:46.500> you<01:18:46.650> deploy<01:18:46.920> an<01:18:47.100> old-style 01:18:47.860 --> 01:18:47.870 align:start position:0% you have it if you deploy an old-style 01:18:47.870 --> 01:18:51.680 align:start position:0% you have it if you deploy an old-style deployer<01:18:48.870> contract<01:18:49.860> deploy<01:18:50.820> any<01:18:51.060> contract<01:18:51.570> is 01:18:51.680 --> 01:18:51.690 align:start position:0% deployer contract deploy any contract is 01:18:51.690 --> 01:18:53.800 align:start position:0% deployer contract deploy any contract is throughout<01:18:51.930> it<01:18:52.200> and<01:18:52.350> then<01:18:52.590> in<01:18:52.770> the<01:18:52.890> new<01:18:53.040> world 01:18:53.800 --> 01:18:53.810 align:start position:0% throughout it and then in the new world 01:18:53.810 --> 01:18:59.600 align:start position:0% throughout it and then in the new world that<01:18:54.950> they<01:18:55.950> deployed<01:18:56.340> with<01:18:56.640> me<01:18:58.310> that's<01:18:59.310> a<01:18:59.460> good 01:18:59.600 --> 01:18:59.610 align:start position:0% that they deployed with me that's a good 01:18:59.610 --> 01:19:12.820 align:start position:0% that they deployed with me that's a good way<01:18:59.790> yeah<01:19:08.090> for<01:19:09.090> the<01:19:09.180> lower<01:19:09.360> gas<01:19:09.630> price<01:19:10.460> all<01:19:11.460> the 01:19:12.820 --> 01:19:12.830 align:start position:0% way yeah for the lower gas price all the 01:19:12.830 --> 01:19:16.790 align:start position:0% way yeah for the lower gas price all the really<01:19:13.830> cheap<01:19:15.170> competition<01:19:16.200> I<01:19:16.380> mean<01:19:16.710> you 01:19:16.790 --> 01:19:16.800 align:start position:0% really cheap competition I mean you 01:19:16.800 --> 01:19:20.780 align:start position:0% really cheap competition I mean you assume<01:19:17.160> that<01:19:17.190> say<01:19:18.590> the<01:19:19.590> new<01:19:19.800> version<01:19:20.250> which 01:19:20.780 --> 01:19:20.790 align:start position:0% assume that say the new version which 01:19:20.790 --> 01:19:22.760 align:start position:0% assume that say the new version which you<01:19:20.940> can<01:19:21.090> often<01:19:21.240> would<01:19:21.780> have<01:19:22.020> things<01:19:22.590> which 01:19:22.760 --> 01:19:22.770 align:start position:0% you can often would have things which 01:19:22.770 --> 01:19:24.380 align:start position:0% you can often would have things which are<01:19:22.920> cheaper<01:19:23.280> and<01:19:23.310> things<01:19:23.730> which<01:19:23.910> are<01:19:24.060> more 01:19:24.380 --> 01:19:24.390 align:start position:0% are cheaper and things which are more 01:19:24.390 --> 01:19:26.120 align:start position:0% are cheaper and things which are more expensive<01:19:24.510> and<01:19:25.110> they<01:19:25.530> will<01:19:25.800> often<01:19:25.950> be 01:19:26.120 --> 01:19:26.130 align:start position:0% expensive and they will often be 01:19:26.130 --> 01:19:28.850 align:start position:0% expensive and they will often be discount<01:19:26.670> somewhere<01:19:27.030> cheap<01:19:27.210> right<01:19:28.110> but<01:19:28.590> the 01:19:28.850 --> 01:19:28.860 align:start position:0% discount somewhere cheap right but the 01:19:28.860 --> 01:19:30.890 align:start position:0% discount somewhere cheap right but the things<01:19:29.370> that<01:19:29.430> are<01:19:29.610> cheaper<01:19:30.000> and<01:19:30.420> accomplish 01:19:30.890 --> 01:19:30.900 align:start position:0% things that are cheaper and accomplish 01:19:30.900 --> 01:19:32.340 align:start position:0% things that are cheaper and accomplish the<01:19:31.380> same<01:19:31.560> thing<01:19:31.830> as<01:19:31.980> the 01:19:32.340 --> 01:19:32.350 align:start position:0% the same thing as the 01:19:32.350 --> 01:19:33.420 align:start position:0% the same thing as the they're<01:19:32.530> more<01:19:32.740> expensive<01:19:32.800> in<01:19:33.250> the<01:19:33.280> all 01:19:33.420 --> 01:19:33.430 align:start position:0% they're more expensive in the all 01:19:33.430 --> 01:19:37.290 align:start position:0% they're more expensive in the all version<01:19:34.260> like<01:19:35.260> you<01:19:35.740> know<01:19:35.830> instead<01:19:36.250> of<01:19:36.400> reading 01:19:37.290 --> 01:19:37.300 align:start position:0% version like you know instead of reading 01:19:37.300 --> 01:19:38.910 align:start position:0% version like you know instead of reading data<01:19:37.510> for<01:19:37.780> peso<01:19:37.960> of<01:19:38.230> you<01:19:38.320> created<01:19:38.710> from 01:19:38.910 --> 01:19:38.920 align:start position:0% data for peso of you created from 01:19:38.920 --> 01:19:43.770 align:start position:0% data for peso of you created from default<01:19:39.250> data<01:19:40.650> you<01:19:41.650> know<01:19:41.770> it's<01:19:42.640> not<01:19:42.790> open<01:19:43.210> but 01:19:43.770 --> 01:19:43.780 align:start position:0% default data you know it's not open but 01:19:43.780 --> 01:19:45.390 align:start position:0% default data you know it's not open but it's<01:19:44.170> not<01:19:44.410> a<01:19:44.440> cure<01:19:44.620> but<01:19:44.830> it<01:19:44.890> doubled<01:19:45.190> up<01:19:45.250> guys 01:19:45.390 --> 01:19:45.400 align:start position:0% it's not a cure but it doubled up guys 01:19:45.400 --> 01:19:47.160 align:start position:0% it's not a cure but it doubled up guys can<01:19:45.640> you<01:19:45.730> mark<01:19:45.970> yeah 01:19:47.160 --> 01:19:47.170 align:start position:0% can you mark yeah 01:19:47.170 --> 01:19:49.230 align:start position:0% can you mark yeah so<01:19:47.920> there<01:19:48.100> were<01:19:48.250> a<01:19:48.280> couple<01:19:48.340> of<01:19:48.670> different 01:19:49.230 --> 01:19:49.240 align:start position:0% so there were a couple of different 01:19:49.240 --> 01:19:52.590 align:start position:0% so there were a couple of different possibilities<01:19:50.010> for<01:19:51.010> business<01:19:51.340> and<01:19:52.240> one<01:19:52.510> of 01:19:52.590 --> 01:19:52.600 align:start position:0% possibilities for business and one of 01:19:52.600 --> 01:19:53.490 align:start position:0% possibilities for business and one of them<01:19:52.750> would<01:19:52.930> say<01:19:52.960> that 01:19:53.490 --> 01:19:53.500 align:start position:0% them would say that 01:19:53.500 --> 01:19:55.470 align:start position:0% them would say that you<01:19:54.160> can<01:19:54.340> select<01:19:54.520> the<01:19:55.030> version<01:19:55.210> you're 01:19:55.470 --> 01:19:55.480 align:start position:0% you can select the version you're 01:19:55.480 --> 01:19:57.390 align:start position:0% you can select the version you're deploying<01:19:55.780> and<01:19:56.500> everyone<01:19:56.830> was<01:19:56.950> saying<01:19:57.100> that 01:19:57.390 --> 01:19:57.400 align:start position:0% deploying and everyone was saying that 01:19:57.400 --> 01:19:59.760 align:start position:0% deploying and everyone was saying that you<01:19:58.240> could<01:19:58.390> only<01:19:58.570> deploy<01:19:58.930> the<01:19:59.110> new<01:19:59.230> word<01:19:59.410> check 01:19:59.760 --> 01:19:59.770 align:start position:0% you could only deploy the new word check 01:19:59.770 --> 01:20:03.090 align:start position:0% you could only deploy the new word check you<01:20:00.280> can<01:20:00.460> deploy<01:20:01.320> the<01:20:02.320> other<01:20:02.440> complications 01:20:03.090 --> 01:20:03.100 align:start position:0% you can deploy the other complications 01:20:03.100 --> 01:20:06.660 align:start position:0% you can deploy the other complications for<01:20:03.990> when<01:20:04.990> you<01:20:05.200> within<01:20:05.620> the<01:20:05.710> contract<01:20:06.220> and 01:20:06.660 --> 01:20:06.670 align:start position:0% for when you within the contract and 01:20:06.670 --> 01:20:08.640 align:start position:0% for when you within the contract and already<01:20:06.940> deployed<01:20:07.420> contract<01:20:07.930> if<01:20:08.170> you<01:20:08.230> want<01:20:08.560> to 01:20:08.640 --> 01:20:08.650 align:start position:0% already deployed contract if you want to 01:20:08.650 --> 01:20:10.380 align:start position:0% already deployed contract if you want to create<01:20:08.860> another<01:20:09.100> contract<01:20:09.820> can<01:20:10.030> you<01:20:10.180> define 01:20:10.380 --> 01:20:10.390 align:start position:0% create another contract can you define 01:20:10.390 --> 01:20:11.460 align:start position:0% create another contract can you define the<01:20:10.720> words<01:20:10.900> from<01:20:11.050> there 01:20:11.460 --> 01:20:11.470 align:start position:0% the words from there 01:20:11.470 --> 01:20:14.040 align:start position:0% the words from there what<01:20:11.980> should<01:20:12.130> it<01:20:12.190> take<01:20:12.370> diversion<01:20:12.670> of<01:20:12.970> all<01:20:13.120> the 01:20:14.040 --> 01:20:14.050 align:start position:0% what should it take diversion of all the 01:20:14.050 --> 01:20:18.450 align:start position:0% what should it take diversion of all the contract<01:20:14.500> you<01:20:14.680> have<01:20:16.740> yeah<01:20:17.740> then<01:20:17.980> what<01:20:18.130> happens 01:20:18.450 --> 01:20:18.460 align:start position:0% contract you have yeah then what happens 01:20:18.460 --> 01:20:20.340 align:start position:0% contract you have yeah then what happens when<01:20:18.670> you<01:20:18.790> call<01:20:19.030> content<01:20:19.900> of<01:20:20.050> different 01:20:20.340 --> 01:20:20.350 align:start position:0% when you call content of different 01:20:20.350 --> 01:20:22.970 align:start position:0% when you call content of different versions<01:20:20.820> what<01:20:21.820> can<01:20:21.970> it<01:20:22.060> will<01:20:22.210> sell<01:20:22.420> out<01:20:22.570> there 01:20:22.970 --> 01:20:22.980 align:start position:0% versions what can it will sell out there 01:20:22.980 --> 01:20:27.920 align:start position:0% versions what can it will sell out there yeah<01:20:23.980> well<01:20:24.100> I<01:20:24.130> think<01:20:24.220> that<01:20:24.550> was<01:20:24.700> figure<01:20:25.000> out 01:20:27.920 --> 01:20:27.930 align:start position:0% 01:20:27.930 --> 01:20:33.900 align:start position:0% decided<01:20:28.930> not<01:20:29.110> to<01:20:29.170> actually<01:20:31.320> and<01:20:32.320> then<01:20:32.530> I<01:20:33.190> think 01:20:33.900 --> 01:20:33.910 align:start position:0% decided not to actually and then I think 01:20:33.910 --> 01:20:36.720 align:start position:0% decided not to actually and then I think man<01:20:34.870> think<01:20:35.110> it<01:20:35.260> was<01:20:35.350> fully<01:20:35.590> resolved<01:20:36.250> what<01:20:36.490> was 01:20:36.720 --> 01:20:36.730 align:start position:0% man think it was fully resolved what was 01:20:36.730 --> 01:20:41.090 align:start position:0% man think it was fully resolved what was probably<01:20:37.060> sold<01:20:37.630> is<01:20:37.990> the<01:20:39.330> current<01:20:40.330> set<01:20:40.780> of 01:20:41.090 --> 01:20:41.100 align:start position:0% probably sold is the current set of 01:20:41.100 --> 01:20:44.290 align:start position:0% probably sold is the current set of contracts<01:20:42.100> deployed<01:20:42.430> where<01:20:43.060> should<01:20:43.270> one 01:20:44.290 --> 01:20:44.300 align:start position:0% contracts deployed where should one 01:20:44.300 --> 01:20:46.149 align:start position:0% contracts deployed where should one we're<01:20:44.599> doing<01:20:44.780> two<01:20:44.960> and<01:20:45.199> if<01:20:45.469> you<01:20:45.590> like<01:20:45.739> boys<01:20:45.949> I 01:20:46.149 --> 01:20:46.159 align:start position:0% we're doing two and if you like boys I 01:20:46.159 --> 01:20:51.290 align:start position:0% we're doing two and if you like boys I think<01:20:46.400> that's<01:20:46.550> only 01:20:51.290 --> 01:20:51.300 align:start position:0% 01:20:51.300 --> 01:21:20.250 align:start position:0% yes<01:20:52.300> but<01:20:53.310> how<01:20:54.310> you<01:20:54.370> deal<01:20:54.730> with<01:21:19.110> versioning<01:21:20.110> you 01:21:20.250 --> 01:21:20.260 align:start position:0% yes but how you deal with versioning you 01:21:20.260 --> 01:21:22.320 align:start position:0% yes but how you deal with versioning you know<01:21:20.410> what<01:21:20.860> I<01:21:21.430> mean<01:21:21.670> what<01:21:21.850> scares<01:21:22.150> me<01:21:22.210> about 01:21:22.320 --> 01:21:22.330 align:start position:0% know what I mean what scares me about 01:21:22.330 --> 01:21:31.410 align:start position:0% know what I mean what scares me about version<01:21:22.870> is<01:21:28.470> more<01:21:29.470> like<01:21:29.740> I<01:21:30.060> mean<01:21:31.060> this<01:21:31.180> one 01:21:31.410 --> 01:21:31.420 align:start position:0% version is more like I mean this one 01:21:31.420 --> 01:21:36.600 align:start position:0% version is more like I mean this one kind<01:21:31.990> of<01:21:34.500> yeah<01:21:35.500> what<01:21:35.830> scares<01:21:36.100> me<01:21:36.160> as<01:21:36.430> if 01:21:36.600 --> 01:21:36.610 align:start position:0% kind of yeah what scares me as if 01:21:36.610 --> 01:21:38.190 align:start position:0% kind of yeah what scares me as if they're<01:21:36.820> you<01:21:37.210> know<01:21:37.240> would<01:21:37.480> be<01:21:37.510> a<01:21:37.630> new<01:21:37.900> version 01:21:38.190 --> 01:21:38.200 align:start position:0% they're you know would be a new version 01:21:38.200 --> 01:21:41.730 align:start position:0% they're you know would be a new version at<01:21:38.710> every<01:21:39.460> hard<01:21:40.390> work<01:21:40.690> and<01:21:40.990> then<01:21:41.080> also<01:21:41.260> we<01:21:41.590> have 01:21:41.730 --> 01:21:41.740 align:start position:0% at every hard work and then also we have 01:21:41.740 --> 01:21:44.280 align:start position:0% at every hard work and then also we have five<01:21:42.250> inversions<01:21:42.670> that<01:21:43.150> run<01:21:43.660> concurrently 01:21:44.280 --> 01:21:44.290 align:start position:0% five inversions that run concurrently 01:21:44.290 --> 01:21:46.500 align:start position:0% five inversions that run concurrently that's<01:21:44.800> just<01:21:45.010> way<01:21:45.100> too<01:21:45.160> complex<01:21:45.640> so<01:21:45.820> really 01:21:46.500 --> 01:21:46.510 align:start position:0% that's just way too complex so really 01:21:46.510 --> 01:21:50.670 align:start position:0% that's just way too complex so really the<01:21:47.500> one<01:21:47.680> had<01:21:47.860> one<01:21:48.220> new<01:21:48.760> version<01:21:49.210> and<01:21:49.680> that's 01:21:50.670 --> 01:21:50.680 align:start position:0% the one had one new version and that's 01:21:50.680 --> 01:21:52.920 align:start position:0% the one had one new version and that's one<01:21:50.950> where<01:21:51.130> we<01:21:51.250> continually<01:21:51.790> update<01:21:52.360> you<01:21:52.840> know 01:21:52.920 --> 01:21:52.930 align:start position:0% one where we continually update you know 01:21:52.930 --> 01:21:55.350 align:start position:0% one where we continually update you know how<01:21:53.170> guests<01:21:53.710> cost<01:21:54.010> of<01:21:54.370> anybody<01:21:54.760> assumes<01:21:55.150> it's 01:21:55.350 --> 01:21:55.360 align:start position:0% how guests cost of anybody assumes it's 01:21:55.360 --> 01:21:57.000 align:start position:0% how guests cost of anybody assumes it's constant<01:21:55.810> well<01:21:55.930> you<01:21:56.230> know<01:21:56.320> that<01:21:56.530> inversion 01:21:57.000 --> 01:21:57.010 align:start position:0% constant well you know that inversion 01:21:57.010 --> 01:22:29.260 align:start position:0% constant well you know that inversion it'll<01:21:57.640> break<01:21:57.820> you<01:21:58.570> know<01:21:58.660> get<01:21:59.170> rid<01:21:59.290> of<01:21:59.350> the<01:21:59.440> 20 01:22:29.260 --> 01:22:29.270 align:start position:0% 01:22:29.270 --> 01:22:30.649 align:start position:0% [Music] 01:22:30.649 --> 01:22:30.659 align:start position:0% [Music] 01:22:30.659 --> 01:22:36.030 align:start position:0% [Music] because<01:22:31.659> you<01:22:32.070> helped<01:22:33.070> the<01:22:33.510> enactments<01:22:34.920> to<01:22:35.920> the 01:22:36.030 --> 01:22:36.040 align:start position:0% because you helped the enactments to the 01:22:36.040 --> 01:22:38.810 align:start position:0% because you helped the enactments to the new<01:22:36.280> new<01:22:36.520> rules 01:22:38.810 --> 01:22:38.820 align:start position:0% new new rules 01:22:38.820 --> 01:22:47.000 align:start position:0% new new rules yeah<01:22:39.820> I<01:22:40.150> mean<01:22:40.360> this<01:22:40.840> recipe<01:22:41.739> is<01:22:41.829> ideal<01:22:42.639> with<01:22:42.849> me 01:22:47.000 --> 01:22:47.010 align:start position:0% 01:22:47.010 --> 01:22:55.210 align:start position:0% you<01:22:48.010> know 01:22:55.210 --> 01:22:55.220 align:start position:0% 01:22:55.220 --> 01:22:58.300 align:start position:0% there<01:22:56.220> was<01:22:56.370> this<01:22:56.520> other<01:22:56.700> aspect<01:22:57.330> to<01:22:57.390> it<01:22:57.510> that 01:22:58.300 --> 01:22:58.310 align:start position:0% there was this other aspect to it that 01:22:58.310 --> 01:23:00.950 align:start position:0% there was this other aspect to it that there<01:22:59.310> might<01:22:59.460> be<01:22:59.490> two<01:23:00.210> different<01:23:00.360> kinds<01:23:00.870> of 01:23:00.950 --> 01:23:00.960 align:start position:0% there might be two different kinds of 01:23:00.960 --> 01:23:04.580 align:start position:0% there might be two different kinds of gas<01:23:01.170> changes<01:23:01.880> there<01:23:02.880> one<01:23:03.840> set<01:23:04.110> of<01:23:04.200> gas<01:23:04.380> changes 01:23:04.580 --> 01:23:04.590 align:start position:0% gas changes there one set of gas changes 01:23:04.590 --> 01:23:07.160 align:start position:0% gas changes there one set of gas changes is<01:23:04.950> where<01:23:05.190> where<01:23:05.490> you<01:23:05.640> want<01:23:06.330> to<01:23:06.420> make<01:23:06.960> some 01:23:07.160 --> 01:23:07.170 align:start position:0% is where where you want to make some 01:23:07.170 --> 01:23:09.410 align:start position:0% is where where you want to make some features<01:23:07.500> better<01:23:07.770> and<01:23:08.370> compensate<01:23:09.060> against 01:23:09.410 --> 01:23:09.420 align:start position:0% features better and compensate against 01:23:09.420 --> 01:23:11.600 align:start position:0% features better and compensate against some<01:23:09.600> other<01:23:09.780> things<01:23:10.080> but<01:23:10.800> the<01:23:11.160> other<01:23:11.310> set<01:23:11.580> of 01:23:11.600 --> 01:23:11.610 align:start position:0% some other things but the other set of 01:23:11.610 --> 01:23:14.420 align:start position:0% some other things but the other set of changes<01:23:12.090> is<01:23:12.500> fixing<01:23:13.500> something<01:23:13.770> against<01:23:14.280> in 01:23:14.420 --> 01:23:14.430 align:start position:0% changes is fixing something against in 01:23:14.430 --> 01:23:17.180 align:start position:0% changes is fixing something against in the<01:23:14.550> u.s.<01:23:14.730> vectors<01:23:15.590> so<01:23:16.590> something<01:23:16.920> depressing 01:23:17.180 --> 01:23:17.190 align:start position:0% the u.s. vectors so something depressing 01:23:17.190 --> 01:23:19.700 align:start position:0% the u.s. vectors so something depressing issue<01:23:17.610> which<01:23:17.970> you<01:23:18.270> cannot<01:23:18.570> just<01:23:18.930> do<01:23:19.530> in 01:23:19.700 --> 01:23:19.710 align:start position:0% issue which you cannot just do in 01:23:19.710 --> 01:23:21.560 align:start position:0% issue which you cannot just do in version<01:23:20.310> two<01:23:20.520> on<01:23:20.700> the<01:23:20.790> new<01:23:20.910> version<01:23:21.330> of<01:23:21.390> one's 01:23:21.560 --> 01:23:21.570 align:start position:0% version two on the new version of one's 01:23:21.570 --> 01:23:24.050 align:start position:0% version two on the new version of one's own<01:23:21.950> because<01:23:22.950> you<01:23:23.190> can<01:23:23.340> already<01:23:23.430> exploit<01:23:23.940> the 01:23:24.050 --> 01:23:24.060 align:start position:0% own because you can already exploit the 01:23:24.060 --> 01:23:53.390 align:start position:0% own because you can already exploit the conversion<01:23:24.540> one<01:23:24.750> and<01:23:27.530> people<01:23:52.280> anticipate<01:23:53.280> as 01:23:53.390 --> 01:23:53.400 align:start position:0% conversion one and people anticipate as 01:23:53.400 --> 01:23:55.280 align:start position:0% conversion one and people anticipate as possible<01:23:53.910> that<01:23:54.120> there<01:23:54.420> are<01:23:54.450> various<01:23:54.810> outputs 01:23:55.280 --> 01:23:55.290 align:start position:0% possible that there are various outputs 01:23:55.290 --> 01:23:57.260 align:start position:0% possible that there are various outputs whose<01:23:55.560> gas<01:23:55.770> prices<01:23:56.250> could<01:23:56.520> change<01:23:56.760> by<01:23:57.030> like 01:23:57.260 --> 01:23:57.270 align:start position:0% whose gas prices could change by like 01:23:57.270 --> 01:23:59.600 align:start position:0% whose gas prices could change by like order<01:23:57.570> of<01:23:57.690> magnitudes<01:23:58.350> in<01:23:59.250> the<01:23:59.310> future 01:23:59.600 --> 01:23:59.610 align:start position:0% order of magnitudes in the future 01:23:59.610 --> 01:24:01.690 align:start position:0% order of magnitudes in the future because<01:23:59.910> in<01:24:00.030> my<01:24:00.150> opinion<01:24:00.360> in<01:24:00.900> regards<01:24:00.990> to<01:24:01.320> this 01:24:01.690 --> 01:24:01.700 align:start position:0% because in my opinion in regards to this 01:24:01.700 --> 01:24:04.250 align:start position:0% because in my opinion in regards to this proposal<01:24:02.700> where<01:24:03.000> a<01:24:03.660> smart<01:24:04.080> contract 01:24:04.250 --> 01:24:04.260 align:start position:0% proposal where a smart contract 01:24:04.260 --> 01:24:06.350 align:start position:0% proposal where a smart contract developer<01:24:04.770> could<01:24:04.890> opt<01:24:05.100> in<01:24:05.340> to<01:24:05.580> a<01:24:05.670> gas<01:24:05.910> system 01:24:06.350 --> 01:24:06.360 align:start position:0% developer could opt in to a gas system 01:24:06.360 --> 01:24:08.270 align:start position:0% developer could opt in to a gas system where<01:24:06.480> gas<01:24:06.600> prices<01:24:06.960> do<01:24:07.110> change<01:24:07.380> I<01:24:07.680> think<01:24:08.070> it 01:24:08.270 --> 01:24:08.280 align:start position:0% where gas prices do change I think it 01:24:08.280 --> 01:24:10.460 align:start position:0% where gas prices do change I think it would<01:24:08.430> be<01:24:08.580> like<01:24:08.910> a<01:24:08.970> code<01:24:09.210> smell<01:24:09.750> if<01:24:10.170> the<01:24:10.290> code 01:24:10.460 --> 01:24:10.470 align:start position:0% would be like a code smell if the code 01:24:10.470 --> 01:24:13.100 align:start position:0% would be like a code smell if the code you<01:24:10.650> write<01:24:10.770> today<01:24:10.950> is<01:24:11.280> already<01:24:11.490> close<01:24:12.060> to<01:24:12.110> you 01:24:13.100 --> 01:24:13.110 align:start position:0% you write today is already close to you 01:24:13.110 --> 01:24:14.420 align:start position:0% you write today is already close to you know<01:24:13.170> I<01:24:13.230> hitting<01:24:13.560> the<01:24:13.650> block<01:24:13.860> of<01:24:14.040> gas<01:24:14.160> limit 01:24:14.420 --> 01:24:14.430 align:start position:0% know I hitting the block of gas limit 01:24:14.430 --> 01:24:15.440 align:start position:0% know I hitting the block of gas limit and<01:24:14.760> sorry 01:24:15.440 --> 01:24:15.450 align:start position:0% and sorry 01:24:15.450 --> 01:24:18.860 align:start position:0% and sorry and<01:24:16.010> and<01:24:17.010> so<01:24:17.640> you<01:24:18.300> know<01:24:18.390> your<01:24:18.570> your 01:24:18.860 --> 01:24:18.870 align:start position:0% and and so you know your your 01:24:18.870 --> 01:24:20.390 align:start position:0% and and so you know your your transactions<01:24:19.500> should<01:24:19.740> be<01:24:19.830> much<01:24:19.980> smaller<01:24:20.190> than 01:24:20.390 --> 01:24:20.400 align:start position:0% transactions should be much smaller than 01:24:20.400 --> 01:24:22.550 align:start position:0% transactions should be much smaller than that<01:24:20.490> in<01:24:20.790> general<01:24:21.210> and<01:24:21.900> so<01:24:22.020> the<01:24:22.170> changes<01:24:22.440> are 01:24:22.550 --> 01:24:22.560 align:start position:0% that in general and so the changes are 01:24:22.560 --> 01:24:23.990 align:start position:0% that in general and so the changes are marginal<01:24:23.010> I<01:24:23.070> think<01:24:23.250> that<01:24:23.340> we<01:24:23.490> find<01:24:23.760> for<01:24:23.910> most 01:24:23.990 --> 01:24:24.000 align:start position:0% marginal I think that we find for most 01:24:24.000 --> 01:24:26.210 align:start position:0% marginal I think that we find for most developers<01:24:24.270> but<01:24:25.230> I<01:24:25.410> mean<01:24:25.560> is<01:24:25.740> it<01:24:25.860> possible 01:24:26.210 --> 01:24:26.220 align:start position:0% developers but I mean is it possible 01:24:26.220 --> 01:24:27.650 align:start position:0% developers but I mean is it possible that<01:24:26.280> certain<01:24:26.520> op<01:24:26.760> codes<01:24:27.120> could<01:24:27.270> have<01:24:27.480> their 01:24:27.650 --> 01:24:27.660 align:start position:0% that certain op codes could have their 01:24:27.660 --> 01:24:29.510 align:start position:0% that certain op codes could have their gas<01:24:27.810> prices<01:24:28.230> changed<01:24:28.590> by<01:24:28.710> worse<01:24:28.920> magnitude 01:24:29.510 --> 01:24:29.520 align:start position:0% gas prices changed by worse magnitude 01:24:29.520 --> 01:24:32.540 align:start position:0% gas prices changed by worse magnitude rather<01:24:29.700> up<01:24:29.850> or<01:24:30.060> down<01:24:30.240> I<01:24:30.960> think<01:24:31.470> it's<01:24:31.620> unlike<01:24:32.100> it 01:24:32.540 --> 01:24:32.550 align:start position:0% rather up or down I think it's unlike it 01:24:32.550 --> 01:24:35.840 align:start position:0% rather up or down I think it's unlike it happened<01:24:33.000> actually<01:24:33.210> I<01:24:34.200> think<01:24:34.440> esto<01:24:34.950> was<01:24:35.130> a<01:24:35.160> 15 01:24:35.840 --> 01:24:35.850 align:start position:0% happened actually I think esto was a 15 01:24:35.850 --> 01:24:38.750 align:start position:0% happened actually I think esto was a 15 and<01:24:36.120> raised<01:24:36.540> to<01:24:37.260> a<01:24:37.290> month<01:24:37.500> crisis<01:24:38.070> other<01:24:38.490> in 01:24:38.750 --> 01:24:38.760 align:start position:0% and raised to a month crisis other in 01:24:38.760 --> 01:24:44.810 align:start position:0% and raised to a month crisis other in order<01:24:38.940> of<01:24:39.120> magnitude<01:24:42.380> cortisone<01:24:43.550> and<01:24:44.550> as<01:24:44.790> I 01:24:44.810 --> 01:24:44.820 align:start position:0% order of magnitude cortisone and as I 01:24:44.820 --> 01:24:47.630 align:start position:0% order of magnitude cortisone and as I was<01:24:45.060> going<01:24:45.150> to<01:24:45.270> go<01:24:45.360> up<01:24:45.420> to<01:24:45.600> big<01:24:45.930> Rome<01:24:46.740> -<01:24:47.010> uh<01:24:47.040> yeah 01:24:47.630 --> 01:24:47.640 align:start position:0% was going to go up to big Rome - uh yeah 01:24:47.640 --> 01:24:49.310 align:start position:0% was going to go up to big Rome - uh yeah but<01:24:48.270> Estelle<01:24:48.660> that's<01:24:48.870> an<01:24:48.960> order<01:24:49.170> of<01:24:49.230> magnitude 01:24:49.310 --> 01:24:49.320 align:start position:0% but Estelle that's an order of magnitude 01:24:49.320 --> 01:24:52.220 align:start position:0% but Estelle that's an order of magnitude from<01:24:49.830> the<01:24:50.070> first<01:24:50.280> one<01:24:50.490> today<01:24:50.880> and<01:24:51.510> if<01:24:51.750> you<01:24:51.930> I 01:24:52.220 --> 01:24:52.230 align:start position:0% from the first one today and if you I 01:24:52.230 --> 01:24:56.330 align:start position:0% from the first one today and if you I mean<01:24:52.560> softballs<01:24:53.040> DBM<01:24:54.030> one<01:24:54.210> benchmarks<01:24:55.340> this 01:24:56.330 --> 01:24:56.340 align:start position:0% mean softballs DBM one benchmarks this 01:24:56.340 --> 01:24:59.300 align:start position:0% mean softballs DBM one benchmarks this morning<01:24:56.700> then<01:24:57.060> you<01:24:57.570> would<01:24:57.690> see<01:24:57.810> there's<01:24:58.310> room 01:24:59.300 --> 01:24:59.310 align:start position:0% morning then you would see there's room 01:24:59.310 --> 01:25:02.900 align:start position:0% morning then you would see there's room for<01:24:59.340> like<01:24:59.790> order<01:25:00.180> of<01:25:00.240> magnitude<01:25:01.910> price 01:25:02.900 --> 01:25:02.910 align:start position:0% for like order of magnitude price 01:25:02.910 --> 01:25:06.920 align:start position:0% for like order of magnitude price changes<01:25:04.430> yeah<01:25:05.430> I<01:25:05.640> just<01:25:05.820> did<01:25:05.970> some<01:25:06.180> research 01:25:06.920 --> 01:25:06.930 align:start position:0% changes yeah I just did some research 01:25:06.930 --> 01:25:09.740 align:start position:0% changes yeah I just did some research recently<01:25:07.430> just<01:25:08.430> looking<01:25:08.850> execution<01:25:09.540> times 01:25:09.740 --> 01:25:09.750 align:start position:0% recently just looking execution times 01:25:09.750 --> 01:25:13.040 align:start position:0% recently just looking execution times from<01:25:10.110> zero<01:25:10.350> negative<01:25:11.210> instructions<01:25:12.210> and<01:25:12.750> you 01:25:13.040 --> 01:25:13.050 align:start position:0% from zero negative instructions and you 01:25:13.050 --> 01:25:14.990 align:start position:0% from zero negative instructions and you can<01:25:13.170> say<01:25:13.320> like<01:25:13.500> well<01:25:13.710> the<01:25:13.860> size<01:25:14.400> dependent 01:25:14.990 --> 01:25:15.000 align:start position:0% can say like well the size dependent 01:25:15.000 --> 01:25:17.600 align:start position:0% can say like well the size dependent instructions<01:25:15.600> and<01:25:15.810> they're<01:25:15.900> being<01:25:16.050> crazy<01:25:16.610> so 01:25:17.600 --> 01:25:17.610 align:start position:0% instructions and they're being crazy so 01:25:17.610 --> 01:25:19.610 align:start position:0% instructions and they're being crazy so I<01:25:17.640> expect<01:25:18.210> that<01:25:18.360> that's<01:25:18.720> the<01:25:18.840> price<01:25:19.080> over<01:25:19.470> time 01:25:19.610 --> 01:25:19.620 align:start position:0% I expect that that's the price over time 01:25:19.620 --> 01:25:23.120 align:start position:0% I expect that that's the price over time will<01:25:19.980> erase<01:25:20.460> the<01:25:20.730> community 01:25:23.120 --> 01:25:23.130 align:start position:0% 01:25:23.130 --> 01:25:28.950 align:start position:0% yeah<01:25:24.130> me<01:25:24.520> too<01:25:26.670> but<01:25:27.670> we<01:25:27.880> could<01:25:28.060> go<01:25:28.210> down<01:25:28.480> I<01:25:28.780> mean 01:25:28.950 --> 01:25:28.960 align:start position:0% yeah me too but we could go down I mean 01:25:28.960 --> 01:25:32.450 align:start position:0% yeah me too but we could go down I mean it's<01:25:29.170> like<01:25:29.320> morning<01:25:30.040> because<01:25:30.520> because<01:25:31.450> goes 01:25:32.450 --> 01:25:32.460 align:start position:0% it's like morning because because goes 01:25:32.460 --> 01:25:35.880 align:start position:0% it's like morning because because goes so<01:25:33.460> I<01:25:33.490> choose<01:25:33.970> to<01:25:34.330> stay<01:25:34.750> for<01:25:35.050> a<01:25:35.080> minute<01:25:35.290> feels 01:25:35.880 --> 01:25:35.890 align:start position:0% so I choose to stay for a minute feels 01:25:35.890 --> 01:25:39.860 align:start position:0% so I choose to stay for a minute feels like<01:25:37.080> because<01:25:38.080> if<01:25:38.650> you<01:25:38.770> had<01:25:39.010> some<01:25:39.220> assumptions 01:25:39.860 --> 01:25:39.870 align:start position:0% like because if you had some assumptions 01:25:39.870 --> 01:25:42.720 align:start position:0% like because if you had some assumptions like<01:25:40.870> everything<01:25:41.380> else<01:25:41.620> that's<01:25:42.160> cheaper<01:25:42.700> than 01:25:42.720 --> 01:25:42.730 align:start position:0% like everything else that's cheaper than 01:25:42.730 --> 01:25:46.950 align:start position:0% like everything else that's cheaper than like<01:25:43.240> the<01:25:43.930> single<01:25:44.170> occupant<01:25:44.800> stays<01:25:45.660> it<01:25:46.660> might 01:25:46.950 --> 01:25:46.960 align:start position:0% like the single occupant stays it might 01:25:46.960 --> 01:25:51.270 align:start position:0% like the single occupant stays it might be<01:25:47.170> with<01:25:47.410> my<01:25:47.530> adventure<01:25:47.980> language<01:25:50.280> dictates 01:25:51.270 --> 01:25:51.280 align:start position:0% be with my adventure language dictates 01:25:51.280 --> 01:25:55.650 align:start position:0% be with my adventure language dictates everything<01:25:51.430> before<01:25:53.670> which<01:25:54.670> take<01:25:54.880> us<01:25:55.480> between 01:25:55.650 --> 01:25:55.660 align:start position:0% everything before which take us between 01:25:55.660 --> 01:25:57.530 align:start position:0% everything before which take us between it<01:25:56.020> is 01:25:57.530 --> 01:25:57.540 align:start position:0% it is 01:25:57.540 --> 01:26:05.160 align:start position:0% it is yeah<01:25:58.540> oh<01:25:58.690> yeah<01:26:03.090> and<01:26:04.090> that<01:26:04.480> transfer<01:26:04.870> to<01:26:04.900> this 01:26:05.160 --> 01:26:05.170 align:start position:0% yeah oh yeah and that transfer to this 01:26:05.170 --> 01:26:07.830 align:start position:0% yeah oh yeah and that transfer to this type<01:26:05.470> of<01:26:05.500> issue<01:26:06.240> freakin<01:26:07.240> parts<01:26:07.570> have<01:26:07.720> been 01:26:07.830 --> 01:26:07.840 align:start position:0% type of issue freakin parts have been 01:26:07.840 --> 01:26:10.980 align:start position:0% type of issue freakin parts have been that<01:26:08.080> cheaper<01:26:08.490> you<01:26:09.490> know<01:26:09.550> I<01:26:09.820> mostly<01:26:10.510> cook<01:26:10.780> like 01:26:10.980 --> 01:26:10.990 align:start position:0% that cheaper you know I mostly cook like 01:26:10.990 --> 01:26:16.680 align:start position:0% that cheaper you know I mostly cook like talking<01:26:11.530> about<01:26:11.770> like<01:26:12.240> not<01:26:13.240> state<01:26:13.570> taxes<01:26:15.690> if 01:26:16.680 --> 01:26:16.690 align:start position:0% talking about like not state taxes if 01:26:16.690 --> 01:26:18.360 align:start position:0% talking about like not state taxes if you<01:26:16.840> want<01:26:17.050> to<01:26:17.200> lower<01:26:17.410> the<01:26:17.620> confrontation<01:26:18.250> of 01:26:18.360 --> 01:26:18.370 align:start position:0% you want to lower the confrontation of 01:26:18.370 --> 01:26:23.700 align:start position:0% you want to lower the confrontation of goods<01:26:21.300> so<01:26:22.300> like<01:26:22.540> this<01:26:22.720> is<01:26:22.870> two<01:26:23.080> options<01:26:23.530> like 01:26:23.700 --> 01:26:23.710 align:start position:0% goods so like this is two options like 01:26:23.710 --> 01:26:26.130 align:start position:0% goods so like this is two options like rice<01:26:24.520> everything<01:26:24.880> cup<01:26:25.210> because<01:26:25.660> we<01:26:25.960> don't 01:26:26.130 --> 01:26:26.140 align:start position:0% rice everything cup because we don't 01:26:26.140 --> 01:26:27.410 align:start position:0% rice everything cup because we don't have<01:26:26.200> like<01:26:26.440> actually<01:26:26.740> lot<01:26:26.860> of<01:26:27.010> space<01:26:27.280> here 01:26:27.410 --> 01:26:27.420 align:start position:0% have like actually lot of space here 01:26:27.420 --> 01:26:38.570 align:start position:0% have like actually lot of space here because<01:26:30.330> this<01:26:31.330> is<01:26:35.310> my<01:26:36.310> tenth<01:26:36.610> of<01:26:36.850> them<01:26:37.090> like<01:26:37.510> I 01:26:38.570 --> 01:26:38.580 align:start position:0% because this is my tenth of them like I 01:26:38.580 --> 01:26:41.220 align:start position:0% because this is my tenth of them like I think<01:26:39.580> there<01:26:39.880> will<01:26:39.970> be<01:26:40.030> a<01:26:40.330> lot<01:26:40.480> of<01:26:40.510> issues<01:26:40.810> to 01:26:41.220 --> 01:26:41.230 align:start position:0% think there will be a lot of issues to 01:26:41.230 --> 01:26:43.320 align:start position:0% think there will be a lot of issues to the<01:26:41.710> existing<01:26:42.130> contract<01:26:42.520> to<01:26:42.820> tell<01:26:43.030> that 01:26:43.320 --> 01:26:43.330 align:start position:0% the existing contract to tell that 01:26:43.330 --> 01:26:45.960 align:start position:0% the existing contract to tell that because<01:26:44.290> all<01:26:44.710> of<01:26:44.740> these<01:26:44.980> like<01:26:45.190> cars<01:26:45.490> passing 01:26:45.960 --> 01:26:45.970 align:start position:0% because all of these like cars passing 01:26:45.970 --> 01:26:49.830 align:start position:0% because all of these like cars passing two<01:26:46.150> different<01:26:46.980> cones<01:26:47.980> and<01:26:48.460> so<01:26:48.670> on<01:26:48.850> so 01:26:49.830 --> 01:26:49.840 align:start position:0% two different cones and so on so 01:26:49.840 --> 01:26:52.080 align:start position:0% two different cones and so on so actually<01:26:50.200> you<01:26:50.260> can<01:26:50.320> like<01:26:50.890> lower<01:26:51.220> them<01:26:51.580> this 01:26:52.080 --> 01:26:52.090 align:start position:0% actually you can like lower them this 01:26:52.090 --> 01:27:07.910 align:start position:0% actually you can like lower them this makes<01:26:54.030> the<01:26:55.030> subject<01:26:55.270> of<01:26:55.660> this<01:26:57.990> fraction 01:27:07.910 --> 01:27:07.920 align:start position:0% 01:27:07.920 --> 01:27:12.010 align:start position:0% [Music] 01:27:12.010 --> 01:27:12.020 align:start position:0% 01:27:12.020 --> 01:28:37.640 align:start position:0% there<01:27:13.020> was<01:27:13.110> a<01:27:48.050> yeah<01:27:49.050> so<01:27:49.619> you<01:28:26.540> guys<01:28:35.869> I<01:28:36.869> have<01:28:37.619> a 01:28:37.640 --> 01:28:37.650 align:start position:0% there was a yeah so you guys I have a 01:28:37.650 --> 01:28:42.620 align:start position:0% there was a yeah so you guys I have a question<01:28:38.750> related<01:28:39.750> about<01:28:40.820> so<01:28:41.820> um<01:28:42.000> where<01:28:42.599> are 01:28:42.620 --> 01:28:42.630 align:start position:0% question related about so um where are 01:28:42.630 --> 01:28:44.450 align:start position:0% question related about so um where are you<01:28:42.840> talks<01:28:43.139> about<01:28:43.409> the<01:28:43.590> storage<01:28:43.889> layout 01:28:44.450 --> 01:28:44.460 align:start position:0% you talks about the storage layout 01:28:44.460 --> 01:28:46.760 align:start position:0% you talks about the storage layout because<01:28:44.699> what<01:28:45.510> I'm<01:28:45.630> trying<01:28:45.869> to<01:28:45.960> do<01:28:46.139> is<01:28:46.260> how<01:28:46.590> can 01:28:46.760 --> 01:28:46.770 align:start position:0% because what I'm trying to do is how can 01:28:46.770 --> 01:28:48.290 align:start position:0% because what I'm trying to do is how can I<01:28:46.860> get<01:28:47.099> X<01:28:47.309> product<01:28:47.520> of<01:28:47.790> a<01:28:47.940> culture<01:28:48.270> like 01:28:48.290 --> 01:28:48.300 align:start position:0% I get X product of a culture like 01:28:48.300 --> 01:28:51.410 align:start position:0% I get X product of a culture like inspect<01:28:49.050> this<01:28:49.199> product<01:28:49.650> very<01:28:49.800> easily<01:28:50.190> I<01:28:50.579> think 01:28:51.410 --> 01:28:51.420 align:start position:0% inspect this product very easily I think 01:28:51.420 --> 01:28:53.330 align:start position:0% inspect this product very easily I think right<01:28:51.540> now<01:28:51.570> you<01:28:51.750> need<01:28:51.989> to<01:28:52.050> go<01:28:52.380> to<01:28:52.440> the<01:28:52.800> initial 01:28:53.330 --> 01:28:53.340 align:start position:0% right now you need to go to the initial 01:28:53.340 --> 01:28:55.430 align:start position:0% right now you need to go to the initial deployment<01:28:53.520> look<01:28:54.239> for<01:28:54.449> all<01:28:54.630> the<01:28:54.750> transactions 01:28:55.430 --> 01:28:55.440 align:start position:0% deployment look for all the transactions 01:28:55.440 --> 01:28:57.799 align:start position:0% deployment look for all the transactions get<01:28:56.040> all<01:28:56.280> the<01:28:56.460> traces<01:28:56.849> of<01:28:57.000> the<01:28:57.179> contract<01:28:57.599> and 01:28:57.799 --> 01:28:57.809 align:start position:0% get all the traces of the contract and 01:28:57.809 --> 01:29:00.169 align:start position:0% get all the traces of the contract and then<01:28:58.139> you<01:28:58.320> can<01:28:58.500> do<01:28:58.650> any<01:28:58.829> computation<01:28:59.190> or<01:28:59.699> is 01:29:00.169 --> 01:29:00.179 align:start position:0% then you can do any computation or is 01:29:00.179 --> 01:29:09.709 align:start position:0% then you can do any computation or is there<01:29:00.389> any<01:29:00.630> war<01:29:04.369> there<01:29:05.369> is<01:29:06.179> actually<01:29:06.780> I<01:29:08.719> think 01:29:09.709 --> 01:29:09.719 align:start position:0% there any war there is actually I think 01:29:09.719 --> 01:29:11.240 align:start position:0% there any war there is actually I think it's<01:29:09.809> not<01:29:09.929> working<01:29:10.139> Phuket<01:29:10.710> that<01:29:10.889> there<01:29:11.070> have 01:29:11.240 --> 01:29:11.250 align:start position:0% it's not working Phuket that there have 01:29:11.250 --> 01:29:14.720 align:start position:0% it's not working Phuket that there have been<01:29:11.400> proposals<01:29:12.270> at<01:29:12.869> least<01:29:13.139> on<01:29:13.290> solidity<01:29:13.770> that 01:29:14.720 --> 01:29:14.730 align:start position:0% been proposals at least on solidity that 01:29:14.730 --> 01:29:18.200 align:start position:0% been proposals at least on solidity that the<01:29:15.659> compiler<01:29:16.199> would<01:29:16.469> ever<01:29:16.650> demand<01:29:17.159> off<01:29:17.969> the 01:29:18.200 --> 01:29:18.210 align:start position:0% the compiler would ever demand off the 01:29:18.210 --> 01:29:24.649 align:start position:0% the compiler would ever demand off the storage<01:29:18.570> and<01:29:19.170> you<01:29:19.800> would<01:29:19.920> use<01:29:20.099> that<01:29:23.449> there<01:29:24.449> has 01:29:24.649 --> 01:29:24.659 align:start position:0% storage and you would use that there has 01:29:24.659 --> 01:29:25.370 align:start position:0% storage and you would use that there has been<01:29:24.780> a<01:29:24.840> proposal 01:29:25.370 --> 01:29:25.380 align:start position:0% been a proposal 01:29:25.380 --> 01:29:27.109 align:start position:0% been a proposal nothing<01:29:25.829> has<01:29:25.949> been<01:29:26.070> implemented<01:29:26.579> yet<01:29:26.730> but 01:29:27.109 --> 01:29:27.119 align:start position:0% nothing has been implemented yet but 01:29:27.119 --> 01:29:30.040 align:start position:0% nothing has been implemented yet but this<01:29:27.780> might<01:29:27.989> happen<01:29:28.199> itself 01:29:30.040 --> 01:29:30.050 align:start position:0% this might happen itself 01:29:30.050 --> 01:29:33.680 align:start position:0% this might happen itself they're<01:29:31.050> often<01:29:31.340> Depot<01:29:32.340> methods<01:29:33.030> satellite 01:29:33.680 --> 01:29:33.690 align:start position:0% they're often Depot methods satellite 01:29:33.690 --> 01:29:37.129 align:start position:0% they're often Depot methods satellite dump<01:29:33.989> the<01:29:34.139> storage<01:29:34.500> of<01:29:34.679> a<01:29:34.800> contract<01:29:35.869> address<01:29:36.869> I 01:29:37.129 --> 01:29:37.139 align:start position:0% dump the storage of a contract address I 01:29:37.139 --> 01:29:41.390 align:start position:0% dump the storage of a contract address I don't<01:29:37.559> know<01:29:37.829> America<01:29:38.699> there's<01:29:38.909> RPC<01:29:40.040> yes<01:29:41.040> there 01:29:41.390 --> 01:29:41.400 align:start position:0% don't know America there's RPC yes there 01:29:41.400 --> 01:29:44.780 align:start position:0% don't know America there's RPC yes there is<01:29:41.750> so<01:29:42.750> and<01:29:43.440> it's<01:29:43.829> appropriate<01:29:44.250> only<01:29:44.610> on<01:29:44.699> the 01:29:44.780 --> 01:29:44.790 align:start position:0% is so and it's appropriate only on the 01:29:44.790 --> 01:29:47.350 align:start position:0% is so and it's appropriate only on the gathered<01:29:45.090> clients<01:29:45.570> I'm<01:29:45.750> not<01:29:45.989> sure 01:29:47.350 --> 01:29:47.360 align:start position:0% gathered clients I'm not sure 01:29:47.360 --> 01:29:51.290 align:start position:0% gathered clients I'm not sure rain<01:29:48.360> storage<01:29:48.929> range<01:29:49.409> at<01:29:49.860> direct<01:29:50.639> and<01:29:50.849> storage 01:29:51.290 --> 01:29:51.300 align:start position:0% rain storage range at direct and storage 01:29:51.300 --> 01:29:53.950 align:start position:0% rain storage range at direct and storage range<01:29:51.659> allows<01:29:52.559> you<01:29:52.860> to<01:29:53.190> in 01:29:53.950 --> 01:29:53.960 align:start position:0% range allows you to in 01:29:53.960 --> 01:29:57.810 align:start position:0% range allows you to in the<01:29:54.560> storage<01:29:54.830> of<01:29:55.040> a<01:29:55.160> contract<01:29:55.760> I<01:29:56.260> don't<01:29:57.260> I 01:29:57.810 --> 01:29:57.820 align:start position:0% the storage of a contract I don't I 01:29:57.820 --> 01:30:00.190 align:start position:0% the storage of a contract I don't I suspect<01:29:58.820> that<01:29:58.910> you<01:29:59.330> won't<01:29:59.510> get<01:29:59.810> it<01:29:59.930> from<01:30:00.080> my 01:30:00.190 --> 01:30:00.200 align:start position:0% suspect that you won't get it from my 01:30:00.200 --> 01:30:05.709 align:start position:0% suspect that you won't get it from my Fuhrer<01:30:00.560> but<01:30:02.200> no<01:30:03.200> no<01:30:03.260> -<01:30:03.820> probably<01:30:04.820> not<01:30:05.239> I<01:30:05.540> don't 01:30:05.709 --> 01:30:05.719 align:start position:0% Fuhrer but no no - probably not I don't 01:30:05.719 --> 01:30:07.959 align:start position:0% Fuhrer but no no - probably not I don't think<01:30:05.900> they<01:30:06.050> expose<01:30:06.380> me<01:30:06.710> you<01:30:07.460> can't<01:30:07.670> you<01:30:07.790> can 01:30:07.959 --> 01:30:07.969 align:start position:0% think they expose me you can't you can 01:30:07.969 --> 01:30:09.580 align:start position:0% think they expose me you can't you can have<01:30:08.090> their<01:30:08.239> try<01:30:08.390> sentiment 01:30:09.580 --> 01:30:09.590 align:start position:0% have their try sentiment 01:30:09.590 --> 01:30:12.100 align:start position:0% have their try sentiment no<01:30:09.860> it's<01:30:10.010> not<01:30:10.160> racist<01:30:10.370> it's<01:30:11.030> just<01:30:11.270> the<01:30:11.450> same 01:30:12.100 --> 01:30:12.110 align:start position:0% no it's not racist it's just the same 01:30:12.110 --> 01:30:19.290 align:start position:0% no it's not racist it's just the same courage<01:30:12.530> slug<01:30:13.840> but<01:30:14.840> it<01:30:14.960> can't<01:30:15.140> buy<01:30:15.350> a<01:30:15.730> rule 01:30:19.290 --> 01:30:19.300 align:start position:0% 01:30:19.300 --> 01:30:25.930 align:start position:0% which<01:30:20.300> you<01:30:20.330> seem<01:30:20.900> to<01:30:23.140> say<01:30:24.140> now<01:30:24.320> excuse<01:30:24.800> me 01:30:25.930 --> 01:30:25.940 align:start position:0% which you seem to say now excuse me 01:30:25.940 --> 01:30:28.390 align:start position:0% which you seem to say now excuse me yeah<01:30:26.719> it<01:30:26.870> was<01:30:26.989> it<01:30:27.230> was<01:30:27.350> implement<01:30:27.890> living<01:30:28.160> gift 01:30:28.390 --> 01:30:28.400 align:start position:0% yeah it was it was implement living gift 01:30:28.400 --> 01:30:44.560 align:start position:0% yeah it was it was implement living gift for<01:30:28.940> the<01:30:29.180> use<01:30:29.360> of<01:30:29.390> a<01:30:33.790> dress<01:30:35.200> and<01:30:37.360> I<01:30:42.820> mean<01:30:43.820> you 01:30:44.560 --> 01:30:44.570 align:start position:0% for the use of a dress and I mean you 01:30:44.570 --> 01:30:47.380 align:start position:0% for the use of a dress and I mean you want<01:30:44.750> to<01:30:44.810> know<01:30:45.620> yeah<01:30:46.070> I<01:30:46.100> want<01:30:46.700> to<01:30:46.850> know<01:30:47.180> that 01:30:47.380 --> 01:30:47.390 align:start position:0% want to know yeah I want to know that 01:30:47.390 --> 01:30:52.350 align:start position:0% want to know yeah I want to know that they<01:30:49.420> only<01:30:50.420> like<01:30:50.690> the<01:30:50.810> solidity 01:30:52.350 --> 01:30:52.360 align:start position:0% they only like the solidity 01:30:52.360 --> 01:30:57.400 align:start position:0% they only like the solidity to<01:30:53.360> visualize<01:30:53.870> it<01:30:54.610> so<01:30:55.610> it<01:30:55.850> has<01:30:55.969> to<01:30:56.150> be<01:30:56.300> I<01:30:57.170> need 01:30:57.400 --> 01:30:57.410 align:start position:0% to visualize it so it has to be I need 01:30:57.410 --> 01:31:00.250 align:start position:0% to visualize it so it has to be I need the<01:30:57.920> input<01:30:58.130> is<01:30:58.460> the<01:30:58.580> contact<01:30:58.910> address<01:30:59.120> and<01:31:00.110> I 01:31:00.250 --> 01:31:00.260 align:start position:0% the input is the contact address and I 01:31:00.260 --> 01:31:02.020 align:start position:0% the input is the contact address and I want<01:31:00.500> to<01:31:00.620> get<01:31:00.830> what<01:31:01.340> do<01:31:01.400> you<01:31:01.460> want<01:31:01.580> to<01:31:01.670> get<01:31:01.820> into 01:31:02.020 --> 01:31:02.030 align:start position:0% want to get what do you want to get into 01:31:02.030 --> 01:31:03.610 align:start position:0% want to get what do you want to get into trailers<01:31:02.210> that<01:31:02.390> are<01:31:02.510> there<01:31:02.870> at<01:31:03.200> the<01:31:03.380> moment 01:31:03.610 --> 01:31:03.620 align:start position:0% trailers that are there at the moment 01:31:03.620 --> 01:31:04.810 align:start position:0% trailers that are there at the moment yes 01:31:04.810 --> 01:31:04.820 align:start position:0% yes 01:31:04.820 --> 01:31:07.090 align:start position:0% yes what<01:31:05.360> do<01:31:05.450> you<01:31:05.540> see<01:31:05.600> in<01:31:05.719> the<01:31:05.810> contract<01:31:06.170> storage 01:31:07.090 --> 01:31:07.100 align:start position:0% what do you see in the contract storage 01:31:07.100 --> 01:31:18.280 align:start position:0% what do you see in the contract storage ranges<01:31:15.160> yes<01:31:16.160> they<01:31:16.280> went<01:31:16.520> like<01:31:16.760> that<01:31:17.290> balance 01:31:18.280 --> 01:31:18.290 align:start position:0% ranges yes they went like that balance 01:31:18.290 --> 01:31:22.479 align:start position:0% ranges yes they went like that balance mapping<01:31:18.710> that<01:31:19.430> we<01:31:20.030> need<01:31:20.210> to<01:31:20.360> know<01:31:21.340> so<01:31:22.340> they 01:31:22.479 --> 01:31:22.489 align:start position:0% mapping that we need to know so they 01:31:22.489 --> 01:31:23.339 align:start position:0% mapping that we need to know so they location 01:31:23.339 --> 01:31:23.349 align:start position:0% location 01:31:23.349 --> 01:31:26.879 align:start position:0% location the<01:31:24.040> map<01:31:24.250> ends<01:31:24.730> up<01:31:25.030> passing<01:31:25.270> -<01:31:25.659> yeah<01:31:26.530> you<01:31:26.770> need 01:31:26.879 --> 01:31:26.889 align:start position:0% the map ends up passing - yeah you need 01:31:26.889 --> 01:31:28.500 align:start position:0% the map ends up passing - yeah you need to<01:31:26.980> know<01:31:27.130> it<01:31:27.460> both<01:31:27.670> feeling<01:31:28.000> aesthetics 01:31:28.500 --> 01:31:28.510 align:start position:0% to know it both feeling aesthetics 01:31:28.510 --> 01:31:31.459 align:start position:0% to know it both feeling aesthetics partially<01:31:28.929> up<01:31:29.079> yeah<01:31:29.949> like<01:31:30.310> what<01:31:30.550> you<01:31:30.670> want<01:31:30.880> to 01:31:31.459 --> 01:31:31.469 align:start position:0% partially up yeah like what you want to 01:31:31.469 --> 01:31:34.500 align:start position:0% partially up yeah like what you want to remix<01:31:32.469> has<01:31:32.710> the<01:31:32.949> end<01:31:33.280> of<01:31:33.460> that<01:31:33.790> you<01:31:33.940> want<01:31:34.329> to 01:31:34.500 --> 01:31:34.510 align:start position:0% remix has the end of that you want to 01:31:34.510 --> 01:31:58.250 align:start position:0% remix has the end of that you want to see<01:31:34.719> what<01:31:34.989> exactly<01:31:35.409> this<01:31:39.900> what's<01:31:55.590> these 01:31:58.250 --> 01:31:58.260 align:start position:0% see what exactly this what's these 01:31:58.260 --> 01:32:01.500 align:start position:0% see what exactly this what's these nothing<01:31:59.260> that's<01:31:59.469> what<01:31:59.619> stores<01:32:00.159> rings<01:32:00.510> but 01:32:01.500 --> 01:32:01.510 align:start position:0% nothing that's what stores rings but 01:32:01.510 --> 01:32:02.819 align:start position:0% nothing that's what stores rings but your<01:32:01.659> conflict<01:32:02.139> versus<01:32:02.530> conservative 01:32:02.819 --> 01:32:02.829 align:start position:0% your conflict versus conservative 01:32:02.829 --> 01:32:06.149 align:start position:0% your conflict versus conservative original<01:32:03.579> key<01:32:03.730> right<01:32:04.560> because<01:32:05.560> your<01:32:05.710> hash<01:32:05.889> the 01:32:06.149 --> 01:32:06.159 align:start position:0% original key right because your hash the 01:32:06.159 --> 01:32:08.700 align:start position:0% original key right because your hash the key<01:32:06.190> overlapping<01:32:07.139> so<01:32:08.139> if<01:32:08.230> you<01:32:08.409> use<01:32:08.500> the 01:32:08.700 --> 01:32:08.710 align:start position:0% key overlapping so if you use the 01:32:08.710 --> 01:32:11.310 align:start position:0% key overlapping so if you use the there's<01:32:09.040> a<01:32:09.099> pre-image<01:32:09.579> tone<01:32:10.300> as<01:32:10.719> well<01:32:10.780> so<01:32:11.199> it 01:32:11.310 --> 01:32:11.320 align:start position:0% there's a pre-image tone as well so it 01:32:11.320 --> 01:32:13.589 align:start position:0% there's a pre-image tone as well so it saves<01:32:11.530> on<01:32:11.710> reimage<01:32:12.040> keys<01:32:12.280> and<01:32:12.849> I'm 01:32:13.589 --> 01:32:13.599 align:start position:0% saves on reimage keys and I'm 01:32:13.599 --> 01:32:15.510 align:start position:0% saves on reimage keys and I'm remembering<01:32:13.869> all<01:32:14.170> this<01:32:14.320> existed<01:32:14.980> that<01:32:15.429> was 01:32:15.510 --> 01:32:15.520 align:start position:0% remembering all this existed that was 01:32:15.520 --> 01:32:18.240 align:start position:0% remembering all this existed that was something<01:32:15.849> was<01:32:16.000> bugging<01:32:16.179> me<01:32:16.510> and<01:32:16.869> I<01:32:17.440> mean<01:32:18.099> now 01:32:18.240 --> 01:32:18.250 align:start position:0% something was bugging me and I mean now 01:32:18.250 --> 01:32:20.550 align:start position:0% something was bugging me and I mean now it's<01:32:18.280> a<01:32:18.429> feature<01:32:18.610> and<01:32:19.000> and<01:32:19.389> remixed<01:32:20.260> I<01:32:20.349> help 01:32:20.550 --> 01:32:20.560 align:start position:0% it's a feature and and remixed I help 01:32:20.560 --> 01:32:23.100 align:start position:0% it's a feature and and remixed I help them<01:32:20.739> with<01:32:20.949> the<01:32:21.099> picture<01:32:21.489> with<01:32:22.239> the<01:32:22.270> historic 01:32:23.100 --> 01:32:23.110 align:start position:0% them with the picture with the historic 01:32:23.110 --> 01:32:32.280 align:start position:0% them with the picture with the historic mapping<01:32:23.530> so<01:32:23.710> remix<01:32:24.010> has<01:32:24.190> this<01:32:24.369> lake<01:32:24.610> state<01:32:31.290> yet 01:32:32.280 --> 01:32:32.290 align:start position:0% mapping so remix has this lake state yet 01:32:32.290 --> 01:32:35.010 align:start position:0% mapping so remix has this lake state yet to<01:32:32.440> show<01:32:32.619> the<01:32:32.889> you<01:32:33.400> know<01:32:33.520> the<01:32:33.730> state<01:32:34.570> members 01:32:35.010 --> 01:32:35.020 align:start position:0% to show the you know the state members 01:32:35.020 --> 01:32:39.800 align:start position:0% to show the you know the state members of<01:32:35.199> mess<01:32:35.639> Distortion<01:32:36.670> keys<01:32:36.940> to<01:32:37.389> the<01:32:37.659> solidity 01:32:39.800 --> 01:32:39.810 align:start position:0% of mess Distortion keys to the solidity 01:32:39.810 --> 01:33:34.270 align:start position:0% of mess Distortion keys to the solidity variable<01:32:40.810> names 01:33:34.270 --> 01:33:34.280 align:start position:0% 01:33:34.280 --> 01:33:54.250 align:start position:0% yeah 01:33:54.250 --> 01:33:54.260 align:start position:0% 01:33:54.260 --> 01:34:11.820 align:start position:0% [Music] 01:34:11.820 --> 01:34:11.830 align:start position:0% 01:34:11.830 --> 01:34:15.090 align:start position:0% editor<01:34:12.670> question<01:34:13.170> I'm<01:34:14.170> using<01:34:14.410> an<01:34:14.920> di 01:34:15.090 --> 01:34:15.100 align:start position:0% editor question I'm using an di 01:34:15.100 --> 01:34:18.840 align:start position:0% editor question I'm using an di interview<01:34:15.820> -<01:34:16.060> for<01:34:16.450> my<01:34:16.570> contract<01:34:17.020> and<01:34:17.850> it's 01:34:18.840 --> 01:34:18.850 align:start position:0% interview - for my contract and it's 01:34:18.850 --> 01:34:33.390 align:start position:0% interview - for my contract and it's still<01:34:19.030> experimental<01:34:19.420> right<01:34:21.360> what<01:34:30.900> so<01:34:32.400> the 01:34:33.390 --> 01:34:33.400 align:start position:0% still experimental right what so the 01:34:33.400 --> 01:34:36.080 align:start position:0% still experimental right what so the main<01:34:33.610> reason<01:34:34.090> why<01:34:34.360> they<01:34:34.720> been<01:34:34.900> good<01:34:35.140> army<01:34:35.350> -<01:34:35.620> I 01:34:36.080 --> 01:34:36.090 align:start position:0% main reason why they been good army - I 01:34:36.090 --> 01:34:38.610 align:start position:0% main reason why they been good army - I hadn't<01:34:37.090> been<01:34:37.210> properly<01:34:37.810> really<01:34:38.110> easy<01:34:38.290> as 01:34:38.610 --> 01:34:38.620 align:start position:0% hadn't been properly really easy as 01:34:38.620 --> 01:34:40.680 align:start position:0% hadn't been properly really easy as non-experimental<01:34:39.100> is<01:34:40.030> that<01:34:40.300> we're<01:34:40.510> still 01:34:40.680 --> 01:34:40.690 align:start position:0% non-experimental is that we're still 01:34:40.690 --> 01:34:43.500 align:start position:0% non-experimental is that we're still fuzzing<01:34:41.080> it<01:34:41.200> a<01:34:41.410> lot<01:34:41.950> and<01:34:42.100> the<01:34:42.670> fuzzer<01:34:42.910> wasn't 01:34:43.500 --> 01:34:43.510 align:start position:0% fuzzing it a lot and the fuzzer wasn't 01:34:43.510 --> 01:34:46.140 align:start position:0% fuzzing it a lot and the fuzzer wasn't prepared<01:34:43.990> and<01:34:44.170> fully<01:34:44.460> to<01:34:45.460> fuzz<01:34:45.760> all<01:34:46.060> the 01:34:46.140 --> 01:34:46.150 align:start position:0% prepared and fully to fuzz all the 01:34:46.150 --> 01:34:48.180 align:start position:0% prepared and fully to fuzz all the complicated<01:34:46.570> cases<01:34:46.840> for<01:34:47.590> the<01:34:47.710> event<01:34:47.950> could<01:34:48.100> it 01:34:48.180 --> 01:34:48.190 align:start position:0% complicated cases for the event could it 01:34:48.190 --> 01:34:50.520 align:start position:0% complicated cases for the event could it be<01:34:48.280> -<01:34:48.960> because<01:34:49.960> there's<01:34:50.110> a<01:34:50.170> lot<01:34:50.320> of<01:34:50.410> erosion 01:34:50.520 --> 01:34:50.530 align:start position:0% be - because there's a lot of erosion 01:34:50.530 --> 01:34:52.800 align:start position:0% be - because there's a lot of erosion areas<01:34:51.040> so<01:34:51.970> that's<01:34:52.090> the<01:34:52.270> main<01:34:52.390> reason 01:34:52.800 --> 01:34:52.810 align:start position:0% areas so that's the main reason 01:34:52.810 --> 01:34:55.860 align:start position:0% areas so that's the main reason basically<01:34:53.230> and<01:34:53.650> but<01:34:54.100> for<01:34:54.370> the<01:34:54.520> next<01:34:54.870> breaking 01:34:55.860 --> 01:34:55.870 align:start position:0% basically and but for the next breaking 01:34:55.870 --> 01:34:58.050 align:start position:0% basically and but for the next breaking over<01:34:55.990> these<01:34:56.110> years<01:34:56.290> to<01:34:56.530> zero<01:34:56.770> it's<01:34:57.760> still<01:34:57.940> very 01:34:58.050 --> 01:34:58.060 align:start position:0% over these years to zero it's still very 01:34:58.060 --> 01:35:00.390 align:start position:0% over these years to zero it's still very experimental<01:34:58.480> but<01:34:59.380> at<01:34:59.500> least<01:34:59.710> I'm<01:35:00.100> gonna<01:35:00.220> need 01:35:00.390 --> 01:35:00.400 align:start position:0% experimental but at least I'm gonna need 01:35:00.400 --> 01:35:02.460 align:start position:0% experimental but at least I'm gonna need you<01:35:00.520> to<01:35:00.550> warning<01:35:01.000> anymore<01:35:01.390> but<01:35:01.720> it<01:35:01.810> shouldn't 01:35:02.460 --> 01:35:02.470 align:start position:0% you to warning anymore but it shouldn't 01:35:02.470 --> 01:35:07.610 align:start position:0% you to warning anymore but it shouldn't because<01:35:03.990> and<01:35:04.990> maybe<01:35:05.790> it's<01:35:06.790> something 01:35:07.610 --> 01:35:07.620 align:start position:0% because and maybe it's something 01:35:07.620 --> 01:35:12.570 align:start position:0% because and maybe it's something experimental<01:35:08.620> and<01:35:11.100> there<01:35:12.100> was<01:35:12.190> just<01:35:12.340> talk 01:35:12.570 --> 01:35:12.580 align:start position:0% experimental and there was just talk 01:35:12.580 --> 01:35:34.220 align:start position:0% experimental and there was just talk about<01:35:12.730> that<01:35:12.970> fuzzing<01:35:13.390> effort<01:35:13.690> right<01:35:14.170> yeah 01:35:34.220 --> 01:35:34.230 align:start position:0% 01:35:34.230 --> 01:35:57.639 align:start position:0% [Music] 01:35:57.639 --> 01:35:57.649 align:start position:0% 01:35:57.649 --> 01:36:03.319 align:start position:0% it's<01:35:58.649> a<01:35:58.739> good<01:35:58.889> idea<01:35:59.010> to<01:36:00.769> by<01:36:01.769> default<01:36:02.369> have 01:36:03.319 --> 01:36:03.329 align:start position:0% it's a good idea to by default have 01:36:03.329 --> 01:36:14.520 align:start position:0% it's a good idea to by default have contracts 01:36:14.520 --> 01:36:14.530 align:start position:0% 01:36:14.530 --> 01:36:18.100 align:start position:0% so<01:36:15.889> like<01:36:16.100> from<01:36:16.520> my<01:36:16.790> perspective<01:36:17.090> like<01:36:17.780> I 01:36:18.100 --> 01:36:18.110 align:start position:0% so like from my perspective like I 01:36:18.110 --> 01:36:22.419 align:start position:0% so like from my perspective like I truly<01:36:18.710> horribly<01:36:19.300> hate<01:36:20.300> this<01:36:20.540> one<01:36:20.780> because<01:36:21.469> all 01:36:22.419 --> 01:36:22.429 align:start position:0% truly horribly hate this one because all 01:36:22.429 --> 01:36:24.430 align:start position:0% truly horribly hate this one because all the<01:36:22.580> calls<01:36:22.850> because<01:36:23.330> whenever<01:36:23.750> I<01:36:23.929> implemented 01:36:24.430 --> 01:36:24.440 align:start position:0% the calls because whenever I implemented 01:36:24.440 --> 01:36:27.399 align:start position:0% the calls because whenever I implemented khasim<01:36:25.010> ABM<01:36:25.369> I<01:36:25.699> do<01:36:26.150> it<01:36:26.300> wrong<01:36:26.600> and<01:36:26.960> I<01:36:27.110> did<01:36:27.290> it 01:36:27.399 --> 01:36:27.409 align:start position:0% khasim ABM I do it wrong and I did it 01:36:27.409 --> 01:36:29.530 align:start position:0% khasim ABM I do it wrong and I did it like<01:36:27.590> like<01:36:27.920> 10<01:36:28.219> times<01:36:28.489> already<01:36:28.699> and<01:36:28.969> every 01:36:29.530 --> 01:36:29.540 align:start position:0% like like 10 times already and every 01:36:29.540 --> 01:36:33.300 align:start position:0% like like 10 times already and every time<01:36:29.750> I<01:36:29.780> do<01:36:30.020> it<01:36:30.050> it<01:36:30.280> because<01:36:31.280> like<01:36:31.520> all<01:36:31.730> the 01:36:33.300 --> 01:36:33.310 align:start position:0% time I do it it because like all the 01:36:33.310 --> 01:37:01.240 align:start position:0% time I do it it because like all the precise<01:36:34.630> order<01:36:59.590> it<01:37:00.590> doesn't<01:37:00.920> specify 01:37:01.240 --> 01:37:01.250 align:start position:0% precise order it doesn't specify 01:37:01.250 --> 01:37:03.580 align:start position:0% precise order it doesn't specify enjoying<01:37:02.179> page<01:37:02.420> it<01:37:02.630> when<01:37:02.810> stiffened<01:37:03.320> is<01:37:03.409> not 01:37:03.580 --> 01:37:03.590 align:start position:0% enjoying page it when stiffened is not 01:37:03.590 --> 01:37:05.560 align:start position:0% enjoying page it when stiffened is not it<01:37:03.739> like<01:37:03.889> when<01:37:04.550> you<01:37:04.699> actually<01:37:04.790> check<01:37:05.179> the<01:37:05.360> gas 01:37:05.560 --> 01:37:05.570 align:start position:0% it like when you actually check the gas 01:37:05.570 --> 01:37:09.370 align:start position:0% it like when you actually check the gas and<01:37:05.960> like<01:37:06.170> if<01:37:06.650> it's<01:37:08.020> there<01:37:09.020> are<01:37:09.110> a<01:37:09.170> lot<01:37:09.350> of 01:37:09.370 --> 01:37:09.380 align:start position:0% and like if it's there are a lot of 01:37:09.380 --> 01:37:13.479 align:start position:0% and like if it's there are a lot of conditions<01:37:09.679> in<01:37:10.130> the<01:37:10.250> call<01:37:10.600> yeah<01:37:11.600> and<01:37:12.110> I<01:37:12.590> think 01:37:13.479 --> 01:37:13.489 align:start position:0% conditions in the call yeah and I think 01:37:13.489 --> 01:37:15.550 align:start position:0% conditions in the call yeah and I think there<01:37:13.760> are<01:37:13.790> cases<01:37:14.090> where<01:37:14.360> you<01:37:14.690> could<01:37:14.869> do<01:37:15.050> them 01:37:15.550 --> 01:37:15.560 align:start position:0% there are cases where you could do them 01:37:15.560 --> 01:37:17.850 align:start position:0% there are cases where you could do them different<01:37:15.830> order<01:37:16.220> in<01:37:16.430> the<01:37:16.610> test<01:37:17.270> suite<01:37:17.360> was 01:37:17.850 --> 01:37:17.860 align:start position:0% different order in the test suite was 01:37:17.860 --> 01:37:24.150 align:start position:0% different order in the test suite was the<01:37:18.860> same<01:37:19.070> successfully<01:37:19.790> so<01:37:20.000> I<01:37:20.600> think<01:37:21.410> it's 01:37:24.150 --> 01:37:24.160 align:start position:0% 01:37:24.160 --> 01:37:35.680 align:start position:0% because<01:37:33.280> but<01:37:34.280> anyway<01:37:34.670> some<01:37:34.730> context<01:37:35.450> around 01:37:35.680 --> 01:37:35.690 align:start position:0% because but anyway some context around 01:37:35.690 --> 01:37:39.130 align:start position:0% because but anyway some context around this<01:37:36.140> so<01:37:36.940> there's<01:37:37.940> one<01:37:38.210> group<01:37:38.360> of<01:37:38.540> people<01:37:39.020> will 01:37:39.130 --> 01:37:39.140 align:start position:0% this so there's one group of people will 01:37:39.140 --> 01:37:41.310 align:start position:0% this so there's one group of people will think<01:37:39.170> that<01:37:39.560> there's<01:37:39.740> problems<01:37:40.400> that<01:37:40.760> I 01:37:41.310 --> 01:37:41.320 align:start position:0% think that there's problems that I 01:37:41.320 --> 01:37:45.330 align:start position:0% think that there's problems that I cannot<01:37:42.320> send<01:37:42.770> money<01:37:43.070> to<01:37:43.520> a<01:37:43.820> contract<01:37:44.600> and 01:37:45.330 --> 01:37:45.340 align:start position:0% cannot send money to a contract and 01:37:45.340 --> 01:37:48.550 align:start position:0% cannot send money to a contract and prevent<01:37:46.340> it<01:37:46.550> from<01:37:46.580> executing<01:37:47.360> code<01:37:47.510> I<01:37:47.840> cannot 01:37:48.550 --> 01:37:48.560 align:start position:0% prevent it from executing code I cannot 01:37:48.560 --> 01:37:52.180 align:start position:0% prevent it from executing code I cannot sell<01:37:48.860> it<01:37:48.890> zero<01:37:49.280> gasp<01:37:49.550> and<01:37:49.880> some<01:37:50.060> cash<01:37:50.330> and<01:37:51.260> then 01:37:52.180 --> 01:37:52.190 align:start position:0% sell it zero gasp and some cash and then 01:37:52.190 --> 01:37:53.680 align:start position:0% sell it zero gasp and some cash and then there<01:37:52.460> is<01:37:52.580> not<01:37:52.760> a<01:37:52.820> group<01:37:53.060> of<01:37:53.150> people<01:37:53.450> think 01:37:53.680 --> 01:37:53.690 align:start position:0% there is not a group of people think 01:37:53.690 --> 01:37:57.550 align:start position:0% there is not a group of people think that<01:37:53.930> any<01:37:55.120> time<01:37:56.120> you<01:37:56.360> receive<01:37:56.810> ether<01:37:57.320> it's 01:37:57.550 --> 01:37:57.560 align:start position:0% that any time you receive ether it's 01:37:57.560 --> 01:37:59.830 align:start position:0% that any time you receive ether it's Rita<01:37:58.100> awesome<01:37:58.610> that<01:37:58.760> you<01:37:58.880> can<01:37:59.060> execute<01:37:59.360> code 01:37:59.830 --> 01:37:59.840 align:start position:0% Rita awesome that you can execute code 01:37:59.840 --> 01:38:03.490 align:start position:0% Rita awesome that you can execute code and<01:38:00.260> it<01:38:00.890> should<01:38:01.250> always<01:38:01.520> be<01:38:01.730> given<01:38:02.270> full<01:38:03.140> gas 01:38:03.490 --> 01:38:03.500 align:start position:0% and it should always be given full gas 01:38:03.500 --> 01:38:08.830 align:start position:0% and it should always be given full gas to<01:38:04.250> do<01:38:04.370> whatever<01:38:04.610> it<01:38:04.910> wants<01:38:07.600> right<01:38:08.600> now<01:38:08.810> I 01:38:08.830 --> 01:38:08.840 align:start position:0% to do whatever it wants right now I 01:38:08.840 --> 01:38:11.800 align:start position:0% to do whatever it wants right now I think<01:38:09.080> even<01:38:09.350> for<01:38:09.410> 300<01:38:10.190> transfers<01:38:11.030> use<01:38:11.210> less 01:38:11.800 --> 01:38:11.810 align:start position:0% think even for 300 transfers use less 01:38:11.810 --> 01:38:14.730 align:start position:0% think even for 300 transfers use less time<01:38:12.020> a<01:38:12.170> middle<01:38:12.470> ground<01:38:12.710> where<01:38:13.250> people<01:38:13.580> say 01:38:14.730 --> 01:38:14.740 align:start position:0% time a middle ground where people say 01:38:14.740 --> 01:38:18.010 align:start position:0% time a middle ground where people say there<01:38:15.740> should<01:38:16.070> be<01:38:16.480> it<01:38:17.480> should<01:38:17.540> be<01:38:17.840> allowed 01:38:18.010 --> 01:38:18.020 align:start position:0% there should be it should be allowed 01:38:18.020 --> 01:38:20.770 align:start position:0% there should be it should be allowed execute<01:38:18.620> code<01:38:18.970> but<01:38:19.970> it<01:38:20.120> should<01:38:20.330> not<01:38:20.480> be<01:38:20.690> able 01:38:20.770 --> 01:38:20.780 align:start position:0% execute code but it should not be able 01:38:20.780 --> 01:38:24.370 align:start position:0% execute code but it should not be able to<01:38:20.930> do<01:38:21.260> state<01:38:21.980> multiplications<01:38:23.140> and<01:38:24.140> that's 01:38:24.370 --> 01:38:24.380 align:start position:0% to do state multiplications and that's 01:38:24.380 --> 01:38:28.570 align:start position:0% to do state multiplications and that's kind<01:38:24.860> of<01:38:25.010> where<01:38:25.280> this<01:38:26.410> 2300<01:38:27.410> comes<01:38:28.010> from<01:38:28.400> the 01:38:28.570 --> 01:38:28.580 align:start position:0% kind of where this 2300 comes from the 01:38:28.580 --> 01:38:31.470 align:start position:0% kind of where this 2300 comes from the current<01:38:28.880> gas<01:38:29.120> data<01:38:29.480> because<01:38:30.080> that<01:38:30.110> was 01:38:31.470 --> 01:38:31.480 align:start position:0% current gas data because that was 01:38:31.480 --> 01:38:34.630 align:start position:0% current gas data because that was sufficient<01:38:32.480> to<01:38:32.690> a<01:38:33.080> log<01:38:33.350> operation<01:38:33.530> or<01:38:34.460> two 01:38:34.630 --> 01:38:34.640 align:start position:0% sufficient to a log operation or two 01:38:34.640 --> 01:38:38.140 align:start position:0% sufficient to a log operation or two maybe<01:38:35.330> even<01:38:35.390> a<01:38:35.660> stove<01:38:36.220> but<01:38:37.220> not<01:38:37.490> actually<01:38:38.000> to 01:38:38.140 --> 01:38:38.150 align:start position:0% maybe even a stove but not actually to 01:38:38.150 --> 01:38:41.710 align:start position:0% maybe even a stove but not actually to the<01:38:38.690> state<01:38:38.980> multiplication<01:38:39.980> and<01:38:40.420> right<01:38:41.420> now 01:38:41.710 --> 01:38:41.720 align:start position:0% the state multiplication and right now 01:38:41.720 --> 01:38:47.160 align:start position:0% the state multiplication and right now is<01:38:42.550> 2,300<01:38:43.550> thing<01:38:43.850> is<01:38:44.240> kind<01:38:44.900> of<01:38:45.020> ugly 01:38:47.160 --> 01:38:47.170 align:start position:0% is 2,300 thing is kind of ugly 01:38:47.170 --> 01:38:53.350 align:start position:0% is 2,300 thing is kind of ugly catch-22<01:38:49.930> allow<01:38:50.930> a<01:38:50.960> bit<01:38:51.350> of<01:38:51.470> execution<01:38:52.190> no<01:38:52.880> too 01:38:53.350 --> 01:38:53.360 align:start position:0% catch-22 allow a bit of execution no too 01:38:53.360 --> 01:38:56.980 align:start position:0% catch-22 allow a bit of execution no too much<01:38:53.570> execution<01:38:54.910> not<01:38:55.910> allow<01:38:56.240> state<01:38:56.540> militia 01:38:56.980 --> 01:38:56.990 align:start position:0% much execution not allow state militia 01:38:56.990 --> 01:38:59.650 align:start position:0% much execution not allow state militia so<01:38:57.830> there<01:38:58.040> are<01:38:58.130> different<01:38:58.820> ways<01:38:58.880> that<01:38:59.390> this 01:38:59.650 --> 01:38:59.660 align:start position:0% so there are different ways that this 01:38:59.660 --> 01:39:03.490 align:start position:0% so there are different ways that this discussion<01:39:00.230> goes<01:39:00.460> like<01:39:01.460> one<01:39:01.940> one<01:39:02.930> group<01:39:03.170> maybe 01:39:03.490 --> 01:39:03.500 align:start position:0% discussion goes like one one group maybe 01:39:03.500 --> 01:39:05.950 align:start position:0% discussion goes like one one group maybe wants<01:39:03.830> to<01:39:03.950> do<01:39:04.100> have<01:39:04.460> a<01:39:04.490> special<01:39:05.060> call<01:39:05.300> on<01:39:05.660> some 01:39:05.950 --> 01:39:05.960 align:start position:0% wants to do have a special call on some 01:39:05.960 --> 01:39:07.570 align:start position:0% wants to do have a special call on some money<01:39:06.230> and<01:39:06.800> do<01:39:06.980> nothing 01:39:07.570 --> 01:39:07.580 align:start position:0% money and do nothing 01:39:07.580 --> 01:39:11.320 align:start position:0% money and do nothing transferring<01:39:09.010> the<01:39:10.010> group<01:39:10.490> you<01:39:10.790> might<01:39:11.030> not 01:39:11.320 --> 01:39:11.330 align:start position:0% transferring the group you might not 01:39:11.330 --> 01:39:13.870 align:start position:0% transferring the group you might not have<01:39:11.540> ecstatic<01:39:12.140> pokeman<01:39:12.590> value<01:39:13.010> and<01:39:13.190> logs<01:39:13.490> so 01:39:13.870 --> 01:39:13.880 align:start position:0% have ecstatic pokeman value and logs so 01:39:13.880 --> 01:39:16.390 align:start position:0% have ecstatic pokeman value and logs so the<01:39:14.000> receiver<01:39:14.300> can<01:39:14.810> do<01:39:14.990> that<01:39:15.770> can<01:39:15.950> consume 01:39:16.390 --> 01:39:16.400 align:start position:0% the receiver can do that can consume 01:39:16.400 --> 01:39:19.420 align:start position:0% the receiver can do that can consume infinite<01:39:16.910> number<01:39:17.390> into<01:39:17.900> the<01:39:17.990> gas<01:39:18.350> but<01:39:18.860> he<01:39:19.100> can 01:39:19.420 --> 01:39:19.430 align:start position:0% infinite number into the gas but he can 01:39:19.430 --> 01:39:21.430 align:start position:0% infinite number into the gas but he can really<01:39:19.760> only<01:39:20.000> do<01:39:20.210> like<01:39:20.480> aromatics<01:39:21.140> log 01:39:21.430 --> 01:39:21.440 align:start position:0% really only do like aromatics log 01:39:21.440 --> 01:39:30.640 align:start position:0% really only do like aromatics log operations<01:39:26.230> I<01:39:27.730> think<01:39:28.730> that<01:39:29.230> where<01:39:30.230> the<01:39:30.320> people 01:39:30.640 --> 01:39:30.650 align:start position:0% operations I think that where the people 01:39:30.650 --> 01:39:32.920 align:start position:0% operations I think that where the people are<01:39:30.710> different<01:39:30.950> we<01:39:31.160> want<01:39:31.340> this<01:39:31.700> discuss<01:39:32.330> which 01:39:32.920 --> 01:39:32.930 align:start position:0% are different we want this discuss which 01:39:32.930 --> 01:39:37.240 align:start position:0% are different we want this discuss which one<01:39:34.240> issues<01:39:35.240> good<01:39:35.750> what<01:39:36.740> is<01:39:36.860> the<01:39:36.980> reason 01:39:37.240 --> 01:39:37.250 align:start position:0% one issues good what is the reason 01:39:37.250 --> 01:39:39.070 align:start position:0% one issues good what is the reason people<01:39:37.430> want<01:39:37.730> to<01:39:37.940> have<01:39:38.150> good<01:39:38.360> executed<01:39:38.930> when 01:39:39.070 --> 01:39:39.080 align:start position:0% people want to have good executed when 01:39:39.080 --> 01:39:41.910 align:start position:0% people want to have good executed when they<01:39:39.200> receive<01:39:39.560> and<01:39:40.520> there's<01:39:40.790> some<01:39:41.060> reasons 01:39:41.910 --> 01:39:41.920 align:start position:0% they receive and there's some reasons 01:39:41.920 --> 01:39:46.150 align:start position:0% they receive and there's some reasons people<01:39:43.240> want<01:39:44.240> them<01:39:44.480> today<01:39:44.660> in<01:39:45.530> the<01:39:45.650> first<01:39:45.920> one 01:39:46.150 --> 01:39:46.160 align:start position:0% people want them today in the first one 01:39:46.160 --> 01:39:47.800 align:start position:0% people want them today in the first one I<01:39:46.430> believe<01:39:46.700> they<01:39:46.910> want<01:39:47.060> if<01:39:47.570> they<01:39:47.630> were 01:39:47.800 --> 01:39:47.810 align:start position:0% I believe they want if they were 01:39:47.810 --> 01:39:51.430 align:start position:0% I believe they want if they were guaranteed<01:39:48.500> to<01:39:48.950> be<01:39:49.480> yeah<01:39:50.510> to<01:39:51.080> have<01:39:51.200> the<01:39:51.290> code 01:39:51.430 --> 01:39:51.440 align:start position:0% guaranteed to be yeah to have the code 01:39:51.440 --> 01:39:53.380 align:start position:0% guaranteed to be yeah to have the code executed<01:39:52.010> and<01:39:52.160> the<01:39:52.250> one<01:39:52.580> of<01:39:52.670> the<01:39:52.760> main<01:39:52.910> reasons 01:39:53.380 --> 01:39:53.390 align:start position:0% executed and the one of the main reasons 01:39:53.390 --> 01:39:54.940 align:start position:0% executed and the one of the main reasons people<01:39:53.480> want<01:39:53.780> that<01:39:54.110> they<01:39:54.260> want<01:39:54.440> to<01:39:54.500> be<01:39:54.620> checked 01:39:54.940 --> 01:39:54.950 align:start position:0% people want that they want to be checked 01:39:54.950 --> 01:39:57.910 align:start position:0% people want that they want to be checked and<01:39:55.370> coming<01:39:55.670> transfers<01:39:56.240> if<01:39:57.230> the<01:39:57.440> contract<01:39:57.830> is 01:39:57.910 --> 01:39:57.920 align:start position:0% and coming transfers if the contract is 01:39:57.920 --> 01:40:00.760 align:start position:0% and coming transfers if the contract is not<01:39:58.100> supposed<01:39:58.520> to<01:39:58.610> score<01:39:58.910> money<01:39:59.380> because<01:40:00.380> if 01:40:00.760 --> 01:40:00.770 align:start position:0% not supposed to score money because if 01:40:00.770 --> 01:40:02.440 align:start position:0% not supposed to score money because if you<01:40:01.040> don't<01:40:01.220> do<01:40:01.400> that<01:40:01.580> and<01:40:01.790> it<01:40:01.940> stores<01:40:02.120> money 01:40:02.440 --> 01:40:02.450 align:start position:0% you don't do that and it stores money 01:40:02.450 --> 01:40:04.330 align:start position:0% you don't do that and it stores money and<01:40:02.750> you<01:40:03.140> don't<01:40:03.290> have<01:40:03.500> a<01:40:03.560> way<01:40:03.680> to<01:40:03.710> between<01:40:04.100> it 01:40:04.330 --> 01:40:04.340 align:start position:0% and you don't have a way to between it 01:40:04.340 --> 01:40:07.030 align:start position:0% and you don't have a way to between it then<01:40:04.550> it<01:40:04.640> just<01:40:04.850> lost<01:40:05.440> the<01:40:06.440> second<01:40:06.890> thing 01:40:07.030 --> 01:40:07.040 align:start position:0% then it just lost the second thing 01:40:07.040 --> 01:40:11.080 align:start position:0% then it just lost the second thing people<01:40:07.070> want<01:40:07.460> to<01:40:07.610> do<01:40:07.670> is<01:40:08.770> have<01:40:09.770> a<01:40:09.800> log<01:40:10.070> and<01:40:10.880> be 01:40:11.080 --> 01:40:11.090 align:start position:0% people want to do is have a log and be 01:40:11.090 --> 01:40:29.350 align:start position:0% people want to do is have a log and be able<01:40:11.240> to<01:40:11.360> catch<01:40:27.550> but<01:40:28.550> still<01:40:28.820> you<01:40:28.970> have<01:40:29.210> the 01:40:29.350 --> 01:40:29.360 align:start position:0% able to catch but still you have the 01:40:29.360 --> 01:40:30.910 align:start position:0% able to catch but still you have the option<01:40:29.720> of<01:40:29.840> doing<01:40:29.990> it<01:40:30.290> through<01:40:30.530> this<01:40:30.650> method 01:40:30.910 --> 01:40:30.920 align:start position:0% option of doing it through this method 01:40:30.920 --> 01:40:34.180 align:start position:0% option of doing it through this method then<01:40:31.910> you<01:40:32.480> know<01:40:33.320> it's<01:40:33.470> clearly<01:40:33.800> now 01:40:34.180 --> 01:40:34.190 align:start position:0% then you know it's clearly now 01:40:34.190 --> 01:40:36.490 align:start position:0% then you know it's clearly now absolutely<01:40:34.910> calling<01:40:35.240> contacts<01:40:35.810> to<01:40:36.260> choose 01:40:36.490 --> 01:40:36.500 align:start position:0% absolutely calling contacts to choose 01:40:36.500 --> 01:40:40.990 align:start position:0% absolutely calling contacts to choose whether<01:40:36.830> the<01:40:38.260> country<01:40:39.260> calling<01:40:39.620> in 01:40:40.990 --> 01:40:41.000 align:start position:0% whether the country calling in 01:40:41.000 --> 01:40:42.729 align:start position:0% whether the country calling in how<01:40:41.600> the<01:40:41.660> other<01:40:41.870> lien<01:40:42.110> takes<01:40:42.290> you<01:40:42.440> to<01:40:42.590> code 01:40:42.729 --> 01:40:42.739 align:start position:0% how the other lien takes you to code 01:40:42.739 --> 01:40:45.280 align:start position:0% how the other lien takes you to code enough<01:40:43.040> and<01:40:43.969> then<01:40:44.120> it<01:40:44.239> seems<01:40:44.420> like<01:40:44.600> this<01:40:44.780> yes 01:40:45.280 --> 01:40:45.290 align:start position:0% enough and then it seems like this yes 01:40:45.290 --> 01:40:48.820 align:start position:0% enough and then it seems like this yes Stefan<01:40:46.630> doesn't<01:40:47.630> still<01:40:48.260> serve<01:40:48.500> a<01:40:48.530> purpose 01:40:48.820 --> 01:40:48.830 align:start position:0% Stefan doesn't still serve a purpose 01:40:48.830 --> 01:40:52.690 align:start position:0% Stefan doesn't still serve a purpose because<01:40:49.280> it<01:40:49.370> doesn't<01:40:49.640> enforce<01:40:51.700> the 01:40:52.690 --> 01:40:52.700 align:start position:0% because it doesn't enforce the 01:40:52.700 --> 01:40:54.700 align:start position:0% because it doesn't enforce the invariants<01:40:53.330> that<01:40:53.690> the<01:40:54.200> convict<01:40:54.590> you're 01:40:54.700 --> 01:40:54.710 align:start position:0% invariants that the convict you're 01:40:54.710 --> 01:40:59.530 align:start position:0% invariants that the convict you're calling<01:40:55.040> into<01:40:56.380> can<01:40:57.380> always<01:40:57.620> execute<01:40:58.070> code<01:40:58.540> is 01:40:59.530 --> 01:40:59.540 align:start position:0% calling into can always execute code is 01:40:59.540 --> 01:41:00.930 align:start position:0% calling into can always execute code is this<01:40:59.780> case<01:40:59.960> read<01:41:00.200> count 01:41:00.930 --> 01:41:00.940 align:start position:0% this case read count 01:41:00.940 --> 01:41:09.150 align:start position:0% this case read count yeah<01:41:05.560> no<01:41:06.560> what<01:41:06.739> is<01:41:06.860> that<01:41:07.040> devious<01:41:07.520> consistent 01:41:09.150 --> 01:41:09.160 align:start position:0% yeah no what is that devious consistent 01:41:09.160 --> 01:41:13.060 align:start position:0% yeah no what is that devious consistent which<01:41:10.160> was<01:41:10.400> a<01:41:10.580> safety<01:41:10.940> feature<01:41:11.300> and<01:41:12.070> probably 01:41:13.060 --> 01:41:13.070 align:start position:0% which was a safety feature and probably 01:41:13.070 --> 01:41:15.820 align:start position:0% which was a safety feature and probably analyze<01:41:13.430> you<01:41:14.270> know<01:41:14.390> the<01:41:14.810> chain<01:41:15.320> has<01:41:15.500> treated 01:41:15.820 --> 01:41:15.830 align:start position:0% analyze you know the chain has treated 01:41:15.830 --> 01:41:19.209 align:start position:0% analyze you know the chain has treated see<01:41:16.100> how<01:41:17.060> many<01:41:17.239> times<01:41:17.480> that's<01:41:18.040> kept<01:41:19.040> people 01:41:19.209 --> 01:41:19.219 align:start position:0% see how many times that's kept people 01:41:19.219 --> 01:41:23.620 align:start position:0% see how many times that's kept people from<01:41:19.370> burning<01:41:21.130> into<01:41:22.130> a<01:41:22.190> condo<01:41:22.730> attempting<01:41:23.510> to 01:41:23.620 --> 01:41:23.630 align:start position:0% from burning into a condo attempting to 01:41:23.630 --> 01:41:25.570 align:start position:0% from burning into a condo attempting to set<01:41:23.810> it<01:41:23.900> to<01:41:23.980> contract<01:41:24.980> that<01:41:25.070> what<01:41:25.219> those<01:41:25.370> to 01:41:25.570 --> 01:41:25.580 align:start position:0% set it to contract that what those to 01:41:25.580 --> 01:41:28.900 align:start position:0% set it to contract that what those to receive<01:41:25.880> it<01:41:26.030> I<01:41:26.360> wonder<01:41:26.989> you<01:41:27.380> know<01:41:28.070> how<01:41:28.400> many<01:41:28.790> to 01:41:28.900 --> 01:41:28.910 align:start position:0% receive it I wonder you know how many to 01:41:28.910 --> 01:41:32.320 align:start position:0% receive it I wonder you know how many to people<01:41:29.210> how<01:41:29.480> much<01:41:29.540> easier<01:41:29.719> it<01:41:29.989> saved<01:41:31.210> throw<01:41:32.210> it 01:41:32.320 --> 01:41:32.330 align:start position:0% people how much easier it saved throw it 01:41:32.330 --> 01:41:36.940 align:start position:0% people how much easier it saved throw it with<01:41:32.450> quite<01:41:32.630> a<01:41:32.660> little<01:41:35.590> argue<01:41:36.590> that<01:41:36.739> this<01:41:36.890> is 01:41:36.940 --> 01:41:36.950 align:start position:0% with quite a little argue that this is 01:41:36.950 --> 01:41:37.560 align:start position:0% with quite a little argue that this is like<01:41:37.310> that 01:41:37.560 --> 01:41:37.570 align:start position:0% like that 01:41:37.570 --> 01:41:43.890 align:start position:0% like that [Music] 01:41:43.890 --> 01:41:43.900 align:start position:0% 01:41:43.900 --> 01:42:36.160 align:start position:0% yeah<01:42:33.820> my<01:42:34.820> turn<01:42:35.000> the<01:42:35.150> past<01:42:35.360> in<01:42:35.570> regards<01:42:35.900> to<01:42:35.960> that 01:42:36.160 --> 01:42:36.170 align:start position:0% yeah my turn the past in regards to that 01:42:36.170 --> 01:42:38.710 align:start position:0% yeah my turn the past in regards to that some<01:42:36.410> people<01:42:36.740> proposed<01:42:37.280> I<01:42:37.730> don't<01:42:38.480> think<01:42:38.660> this 01:42:38.710 --> 01:42:38.720 align:start position:0% some people proposed I don't think this 01:42:38.720 --> 01:42:40.030 align:start position:0% some people proposed I don't think this would<01:42:38.900> happen<01:42:39.050> at<01:42:39.260> this<01:42:39.320> point<01:42:39.440> I<01:42:39.740> proposed 01:42:40.030 --> 01:42:40.040 align:start position:0% would happen at this point I proposed 01:42:40.040 --> 01:42:43.890 align:start position:0% would happen at this point I proposed that<01:42:40.070> ether<01:42:41.410> native<01:42:42.410> ether 01:42:43.890 --> 01:42:43.900 align:start position:0% that ether native ether 01:42:43.900 --> 01:42:46.110 align:start position:0% that ether native ether as<01:42:44.440> in<01:42:44.590> the<01:42:44.680> ERC<01:42:44.860> 21<01:42:45.400> that<01:42:45.580> we<01:42:45.820> wouldn't<01:42:46.060> have 01:42:46.110 --> 01:42:46.120 align:start position:0% as in the ERC 21 that we wouldn't have 01:42:46.120 --> 01:42:48.300 align:start position:0% as in the ERC 21 that we wouldn't have this<01:42:46.360> like<01:42:46.570> penquin<01:42:46.930> asset<01:42:47.500> it's<01:42:47.740> a<01:42:47.890> special 01:42:48.300 --> 01:42:48.310 align:start position:0% this like penquin asset it's a special 01:42:48.310 --> 01:42:51.600 align:start position:0% this like penquin asset it's a special case<01:42:49.080> from<01:42:50.080> like<01:42:50.530> a<01:42:50.560> team<01:42:50.800> and<01:42:51.010> developers 01:42:51.600 --> 01:42:51.610 align:start position:0% case from like a team and developers 01:42:51.610 --> 01:42:53.700 align:start position:0% case from like a team and developers perspective<01:42:51.850> is<01:42:52.600> there<01:42:52.840> any<01:42:52.960> reason<01:42:53.470> that 01:42:53.700 --> 01:42:53.710 align:start position:0% perspective is there any reason that 01:42:53.710 --> 01:42:54.570 align:start position:0% perspective is there any reason that either 01:42:54.570 --> 01:42:54.580 align:start position:0% either 01:42:54.580 --> 01:42:56.730 align:start position:0% either that's<01:42:54.970> have<01:42:55.180> to<01:42:55.330> be<01:42:55.450> was<01:42:55.600> nominated<01:42:56.140> thing<01:42:56.590> or 01:42:56.730 --> 01:42:56.740 align:start position:0% that's have to be was nominated thing or 01:42:56.740 --> 01:42:58.260 align:start position:0% that's have to be was nominated thing or is<01:42:56.800> it<01:42:56.830> theoretically<01:42:57.190> possible<01:42:57.670> that<01:42:58.030> it 01:42:58.260 --> 01:42:58.270 align:start position:0% is it theoretically possible that it 01:42:58.270 --> 01:43:03.800 align:start position:0% is it theoretically possible that it could<01:42:58.810> be<01:42:58.870> an<01:42:59.530> ER<01:42:59.800> c<01:43:00.010> 20<01:43:00.360> contract<01:43:01.440> crazy 01:43:03.800 --> 01:43:03.810 align:start position:0% could be an ER c 20 contract crazy 01:43:03.810 --> 01:43:15.709 align:start position:0% could be an ER c 20 contract crazy [Music] 01:43:15.709 --> 01:43:15.719 align:start position:0% 01:43:15.719 --> 01:43:21.160 align:start position:0% I<01:43:16.310> think<01:43:17.310> yeah<01:43:18.180> wrapped<01:43:18.530> wrapped<01:43:19.530> Eva 01:43:21.160 --> 01:43:21.170 align:start position:0% I think yeah wrapped wrapped Eva 01:43:21.170 --> 01:43:23.330 align:start position:0% I think yeah wrapped wrapped Eva I<01:43:22.170> don't<01:43:22.380> think<01:43:22.590> there's<01:43:22.710> a<01:43:22.770> way<01:43:22.860> around<01:43:22.920> to 01:43:23.330 --> 01:43:23.340 align:start position:0% I don't think there's a way around to 01:43:23.340 --> 01:43:26.209 align:start position:0% I don't think there's a way around to first<01:43:23.640> not<01:43:24.480> look<01:43:24.780> but<01:43:25.199> for<01:43:25.410> what<01:43:25.560> the<01:43:25.710> original 01:43:26.209 --> 01:43:26.219 align:start position:0% first not look but for what the original 01:43:26.219 --> 01:43:29.300 align:start position:0% first not look but for what the original vision<01:43:26.340> was<01:43:26.520> for<01:43:26.699> reading<01:43:28.010> let's<01:43:29.010> say<01:43:29.130> they're 01:43:29.300 --> 01:43:29.310 align:start position:0% vision was for reading let's say they're 01:43:29.310 --> 01:43:33.950 align:start position:0% vision was for reading let's say they're like<01:43:29.460> two<01:43:31.160> endpoints<01:43:32.160> to<01:43:32.820> different<01:43:33.449> posts<01:43:33.719> to 01:43:33.950 --> 01:43:33.960 align:start position:0% like two endpoints to different posts to 01:43:33.960 --> 01:43:36.170 align:start position:0% like two endpoints to different posts to the<01:43:34.080> discussion<01:43:34.580> one<01:43:35.580> instead<01:43:35.790> of<01:43:35.850> the<01:43:36.000> ERC 01:43:36.170 --> 01:43:36.180 align:start position:0% the discussion one instead of the ERC 01:43:36.180 --> 01:43:40.520 align:start position:0% the discussion one instead of the ERC twenty<01:43:36.600> stuff<01:43:37.110> so<01:43:37.980> we've<01:43:38.160> done<01:43:39.260> what<01:43:40.260> people 01:43:40.520 --> 01:43:40.530 align:start position:0% twenty stuff so we've done what people 01:43:40.530 --> 01:43:42.650 align:start position:0% twenty stuff so we've done what people do<01:43:40.650> is<01:43:40.830> as<01:43:41.040> rep<01:43:41.310> Teeter<01:43:41.670> and<01:43:41.969> you<01:43:42.300> can<01:43:42.510> actually 01:43:42.650 --> 01:43:42.660 align:start position:0% do is as rep Teeter and you can actually 01:43:42.660 --> 01:43:44.270 align:start position:0% do is as rep Teeter and you can actually write<01:43:43.020> to<01:43:43.170> a<01:43:43.230> contract<01:43:43.650> in<01:43:43.770> the<01:43:43.830> way<01:43:43.949> you<01:43:44.130> only 01:43:44.270 --> 01:43:44.280 align:start position:0% write to a contract in the way you only 01:43:44.280 --> 01:43:46.280 align:start position:0% write to a contract in the way you only use<01:43:44.550> the<01:43:44.699> years<01:43:44.850> of<01:43:45.000> 20<01:43:45.239> interface<01:43:45.600> reject<01:43:46.080> all 01:43:46.280 --> 01:43:46.290 align:start position:0% use the years of 20 interface reject all 01:43:46.290 --> 01:43:49.580 align:start position:0% use the years of 20 interface reject all the<01:43:46.320> transfers<01:43:47.100> and<01:43:47.489> then<01:43:48.090> it's<01:43:48.810> it's<01:43:49.110> a<01:43:49.230> UX 01:43:49.580 --> 01:43:49.590 align:start position:0% the transfers and then it's it's a UX 01:43:49.590 --> 01:43:51.590 align:start position:0% the transfers and then it's it's a UX issue<01:43:49.830> that<01:43:50.130> you<01:43:50.250> require<01:43:50.610> users<01:43:51.210> to<01:43:51.239> use 01:43:51.590 --> 01:43:51.600 align:start position:0% issue that you require users to use 01:43:51.600 --> 01:43:54.350 align:start position:0% issue that you require users to use crafty<01:43:52.140> turkey<01:43:52.590> on<01:43:53.430> top<01:43:53.610> of<01:43:53.699> that<01:43:53.850> it<01:43:54.000> also<01:43:54.090> has 01:43:54.350 --> 01:43:54.360 align:start position:0% crafty turkey on top of that it also has 01:43:54.360 --> 01:43:55.850 align:start position:0% crafty turkey on top of that it also has an<01:43:54.510> extra<01:43:54.750> cost<01:43:54.989> and<01:43:55.290> whether<01:43:55.440> you<01:43:55.650> want<01:43:55.800> to 01:43:55.850 --> 01:43:55.860 align:start position:0% an extra cost and whether you want to 01:43:55.860 --> 01:44:01.130 align:start position:0% an extra cost and whether you want to pay<01:43:55.980> that<01:43:56.010> costed<01:43:59.330> so<01:44:00.330> for<01:44:00.660> that<01:44:00.750> there<01:44:00.989> were 01:44:01.130 --> 01:44:01.140 align:start position:0% pay that costed so for that there were 01:44:01.140 --> 01:44:04.580 align:start position:0% pay that costed so for that there were there<01:44:01.469> was<01:44:01.620> one<01:44:01.830> proposal<01:44:02.460> that<01:44:02.760> maybe<01:44:03.630> the 01:44:04.580 --> 01:44:04.590 align:start position:0% there was one proposal that maybe the 01:44:04.590 --> 01:44:06.530 align:start position:0% there was one proposal that maybe the red<01:44:04.830> eater<01:44:05.190> should<01:44:05.550> be<01:44:05.730> kind<01:44:06.000> of<01:44:06.060> versus 01:44:06.530 --> 01:44:06.540 align:start position:0% red eater should be kind of versus 01:44:06.540 --> 01:44:11.479 align:start position:0% red eater should be kind of versus standard<01:44:07.290> system<01:44:07.710> contract<01:44:08.160> with<01:44:08.370> people<01:44:10.489> and 01:44:11.479 --> 01:44:11.489 align:start position:0% standard system contract with people and 01:44:11.489 --> 01:44:13.280 align:start position:0% standard system contract with people and it<01:44:12.060> would<01:44:12.210> be<01:44:12.390> practically<01:44:12.810> feet<01:44:13.080> to<01:44:13.199> the 01:44:13.280 --> 01:44:13.290 align:start position:0% it would be practically feet to the 01:44:13.290 --> 01:44:15.229 align:start position:0% it would be practically feet to the other<01:44:13.320> death<01:44:13.680> and<01:44:13.949> users<01:44:14.520> wouldn't<01:44:14.790> need<01:44:15.030> to 01:44:15.229 --> 01:44:15.239 align:start position:0% other death and users wouldn't need to 01:44:15.239 --> 01:44:17.600 align:start position:0% other death and users wouldn't need to mentally<01:44:16.050> transfer<01:44:16.710> the<01:44:16.860> interest<01:44:17.250> in<01:44:17.460> to 01:44:17.600 --> 01:44:17.610 align:start position:0% mentally transfer the interest in to 01:44:17.610 --> 01:44:19.670 align:start position:0% mentally transfer the interest in to disrupt<01:44:17.969> your<01:44:18.180> contract<01:44:18.660> you<01:44:18.930> could<01:44:19.410> just 01:44:19.670 --> 01:44:19.680 align:start position:0% disrupt your contract you could just 01:44:19.680 --> 01:44:21.280 align:start position:0% disrupt your contract you could just through<01:44:19.949> this<01:44:20.040> extra<01:44:20.370> contract<01:44:20.910> you<01:44:21.030> could 01:44:21.280 --> 01:44:21.290 align:start position:0% through this extra contract you could 01:44:21.290 --> 01:44:25.040 align:start position:0% through this extra contract you could handle<01:44:22.290> your<01:44:23.219> ETA<01:44:23.610> as<01:44:23.850> if<01:44:24.090> it<01:44:24.270> were<01:44:24.390> your<01:44:24.600> C<01:44:24.750> 20 01:44:25.040 --> 01:44:25.050 align:start position:0% handle your ETA as if it were your C 20 01:44:25.050 --> 01:44:31.600 align:start position:0% handle your ETA as if it were your C 20 but<01:44:25.440> it<01:44:25.560> wouldn't<01:44:25.770> affect<01:44:25.920> everything<01:44:26.400> else 01:44:31.600 --> 01:44:31.610 align:start position:0% 01:44:31.610 --> 01:44:37.250 align:start position:0% is<01:44:32.610> the<01:44:33.620> beginning<01:44:34.620> of<01:44:34.739> your<01:44:34.860> question<01:44:36.199> why<01:44:37.199> is 01:44:37.250 --> 01:44:37.260 align:start position:0% is the beginning of your question why is 01:44:37.260 --> 01:44:39.860 align:start position:0% is the beginning of your question why is eater<01:44:37.830> dis<01:44:38.400> dis<01:44:38.640> native<01:44:39.000> thing<01:44:39.270> cannot<01:44:39.630> you 01:44:39.860 --> 01:44:39.870 align:start position:0% eater dis dis native thing cannot you 01:44:39.870 --> 01:44:41.510 align:start position:0% eater dis dis native thing cannot you just<01:44:40.140> make<01:44:40.440> it<01:44:40.530> more<01:44:40.650> flexible<01:44:40.830> and<01:44:41.310> these 01:44:41.510 --> 01:44:41.520 align:start position:0% just make it more flexible and these 01:44:41.520 --> 01:44:45.200 align:start position:0% just make it more flexible and these other<01:44:41.670> things<01:44:42.440> there<01:44:43.440> was<01:44:43.560> a<01:44:43.620> proposal<01:44:44.210> long 01:44:45.200 --> 01:44:45.210 align:start position:0% other things there was a proposal long 01:44:45.210 --> 01:44:48.350 align:start position:0% other things there was a proposal long way<01:44:45.390> to<01:44:45.449> go<01:44:45.660> for<01:44:45.900> it<01:44:46.170> can't<01:44:46.440> abstraction<01:44:47.160> to<01:44:47.360> it 01:44:48.350 --> 01:44:48.360 align:start position:0% way to go for it can't abstraction to it 01:44:48.360 --> 01:44:51.350 align:start position:0% way to go for it can't abstraction to it was<01:44:48.630> just<01:44:48.810> a<01:44:48.870> first<01:44:49.020> step<01:44:49.110> in<01:44:49.620> the<01:44:50.610> process<01:44:50.910> to 01:44:51.350 --> 01:44:51.360 align:start position:0% was just a first step in the process to 01:44:51.360 --> 01:44:53.020 align:start position:0% was just a first step in the process to getting<01:44:51.540> rid<01:44:51.840> of<01:44:52.080> each 01:44:53.020 --> 01:44:53.030 align:start position:0% getting rid of each 01:44:53.030 --> 01:44:55.690 align:start position:0% getting rid of each native<01:44:53.450> thing<01:44:53.830> with<01:44:54.830> in<01:44:55.040> theory<01:44:55.310> you<01:44:55.550> could 01:44:55.690 --> 01:44:55.700 align:start position:0% native thing with in theory you could 01:44:55.700 --> 01:44:57.900 align:start position:0% native thing with in theory you could use<01:44:55.910> other<01:44:56.150> things<01:44:56.270> to<01:44:56.630> pay<01:44:56.780> for<01:44:57.020> execution 01:44:57.900 --> 01:44:57.910 align:start position:0% use other things to pay for execution 01:44:57.910 --> 01:45:01.420 align:start position:0% use other things to pay for execution but<01:44:58.910> that<01:44:59.090> is<01:44:59.210> a<01:44:59.240> really<01:44:59.570> long<01:44:59.800> process<01:45:00.800> and<01:45:01.280> it 01:45:01.420 --> 01:45:01.430 align:start position:0% but that is a really long process and it 01:45:01.430 --> 01:45:07.679 align:start position:0% but that is a really long process and it stopped<01:45:01.760> at<01:45:02.150> the<01:45:02.240> first<01:45:02.480> step<01:45:02.690> it<01:45:02.900> never<01:45:03.440> got 01:45:07.679 --> 01:45:07.689 align:start position:0% 01:45:07.689 --> 01:45:17.040 align:start position:0% so<01:45:15.389> the<01:45:16.389> building 01:45:17.040 --> 01:45:17.050 align:start position:0% so the building 01:45:17.050 --> 01:45:20.969 align:start position:0% so the building it's<01:45:17.380> basically<01:45:17.769> the<01:45:17.949> base<01:45:18.099> layer<01:45:19.979> it's 01:45:20.969 --> 01:45:20.979 align:start position:0% it's basically the base layer it's 01:45:20.979 --> 01:45:22.500 align:start position:0% it's basically the base layer it's actually<01:45:21.280> what<01:45:21.429> we<01:45:21.550> you<01:45:21.639> exist<01:45:21.969> you<01:45:22.030> like<01:45:22.329> if 01:45:22.500 --> 01:45:22.510 align:start position:0% actually what we you exist you like if 01:45:22.510 --> 01:45:24.569 align:start position:0% actually what we you exist you like if you<01:45:22.659> don't<01:45:22.840> want<01:45:22.989> you<01:45:23.079> to<01:45:23.139> use<01:45:23.260> it<01:45:23.289> to<01:45:23.559> use<01:45:24.309> rap 01:45:24.569 --> 01:45:24.579 align:start position:0% you don't want you to use it to use rap 01:45:24.579 --> 01:45:26.580 align:start position:0% you don't want you to use it to use rap to<01:45:24.760> end<01:45:24.909> whatever<01:45:25.269> you<01:45:25.659> can't<01:45:25.900> fold<01:45:26.110> the<01:45:26.320> tools 01:45:26.580 --> 01:45:26.590 align:start position:0% to end whatever you can't fold the tools 01:45:26.590 --> 01:45:34.140 align:start position:0% to end whatever you can't fold the tools or<01:45:26.979> Robert<01:45:27.570> what<01:45:28.570> are<01:45:28.659> you<01:45:33.150> interactions 01:45:34.140 --> 01:45:34.150 align:start position:0% or Robert what are you interactions 01:45:34.150 --> 01:45:37.500 align:start position:0% or Robert what are you interactions Mississippi<01:45:34.959> you<01:45:35.709> can<01:45:35.739> get<01:45:36.039> quite<01:45:36.249> fall<01:45:36.519> the 01:45:37.500 --> 01:45:37.510 align:start position:0% Mississippi you can get quite fall the 01:45:37.510 --> 01:45:40.189 align:start position:0% Mississippi you can get quite fall the divers 01:45:40.189 --> 01:45:40.199 align:start position:0% 01:45:40.199 --> 01:45:42.479 align:start position:0% Martin<01:45:41.199> what<01:45:41.349> do<01:45:41.409> you<01:45:41.499> think<01:45:41.739> about<01:45:41.979> this<01:45:42.159> idea 01:45:42.479 --> 01:45:42.489 align:start position:0% Martin what do you think about this idea 01:45:42.489 --> 01:45:46.290 align:start position:0% Martin what do you think about this idea of<01:45:43.030> having<01:45:43.749> test<01:45:44.309> the<01:45:45.309> special<01:45:45.789> contract 01:45:46.290 --> 01:45:46.300 align:start position:0% of having test the special contract 01:45:46.300 --> 01:45:51.060 align:start position:0% of having test the special contract which<01:45:47.229> gives<01:45:47.499> in<01:45:47.650> the<01:45:47.739> air<01:45:47.800> see<01:45:48.010> too<01:45:48.130> many<01:45:50.070> but 01:45:51.060 --> 01:45:51.070 align:start position:0% which gives in the air see too many but 01:45:51.070 --> 01:45:53.370 align:start position:0% which gives in the air see too many but basically<01:45:52.059> you<01:45:52.510> wouldn't<01:45:52.689> need<01:45:52.840> to<01:45:52.900> transfer 01:45:53.370 --> 01:45:53.380 align:start position:0% basically you wouldn't need to transfer 01:45:53.380 --> 01:45:59.960 align:start position:0% basically you wouldn't need to transfer your<01:45:53.409> money<01:45:53.679> into<01:45:53.949> it<01:45:54.630> is<01:45:55.630> it<01:45:55.809> good 01:45:59.960 --> 01:45:59.970 align:start position:0% 01:45:59.970 --> 01:46:03.219 align:start position:0% [Music] 01:46:03.219 --> 01:46:03.229 align:start position:0% [Music] 01:46:03.229 --> 01:46:05.989 align:start position:0% [Music] something<01:46:04.229> that<01:46:04.379> I<01:46:04.590> need<01:46:04.979> to<01:46:05.159> think<01:46:05.609> about 01:46:05.989 --> 01:46:05.999 align:start position:0% something that I need to think about 01:46:05.999 --> 01:46:12.270 align:start position:0% something that I need to think about some<01:46:06.300> more 01:46:12.270 --> 01:46:12.280 align:start position:0% 01:46:12.280 --> 01:46:21.580 align:start position:0% [Music] 01:46:21.580 --> 01:46:21.590 align:start position:0% 01:46:21.590 --> 01:46:46.000 align:start position:0% [Music] 01:46:46.000 --> 01:46:46.010 align:start position:0% 01:46:46.010 --> 01:47:45.560 align:start position:0% like<01:47:42.350> something<01:47:43.350> why<01:47:43.710> is<01:47:43.739> it<01:47:44.100> that<01:47:44.570> like 01:47:45.560 --> 01:47:45.570 align:start position:0% like something why is it that like 01:47:45.570 --> 01:47:46.910 align:start position:0% like something why is it that like inside<01:47:45.960> the<01:47:46.110> EPI 01:47:46.910 --> 01:47:46.920 align:start position:0% inside the EPI 01:47:46.920 --> 01:47:50.200 align:start position:0% inside the EPI look<01:47:47.040> back<01:47:47.250> more<01:47:47.550> than<01:47:47.670> 256<01:47:48.360> blockages 01:47:50.200 --> 01:47:50.210 align:start position:0% look back more than 256 blockages 01:47:50.210 --> 01:47:52.430 align:start position:0% look back more than 256 blockages because<01:47:51.210> the<01:47:51.360> light<01:47:51.660> clients<01:47:52.080> wouldn't<01:47:52.260> be 01:47:52.430 --> 01:47:52.440 align:start position:0% because the light clients wouldn't be 01:47:52.440 --> 01:48:00.560 align:start position:0% because the light clients wouldn't be able<01:47:52.500> to<01:47:58.400> dougie<01:47:59.400> I<01:47:59.490> mean<01:47:59.730> it's<01:47:59.850> it's<01:48:00.300> a<01:48:00.420> pretty 01:48:00.560 --> 01:48:00.570 align:start position:0% able to dougie I mean it's it's a pretty 01:48:00.570 --> 01:48:05.090 align:start position:0% able to dougie I mean it's it's a pretty to<01:48:00.720> round<01:48:00.930> them<01:48:01.910> number<01:48:02.910> though<01:48:03.860> yes<01:48:04.860> I<01:48:05.040> don't 01:48:05.090 --> 01:48:05.100 align:start position:0% to round them number though yes I don't 01:48:05.100 --> 01:48:08.660 align:start position:0% to round them number though yes I don't know<01:48:05.310> pretty<01:48:05.460> big<01:48:07.130> but<01:48:08.130> it<01:48:08.250> had<01:48:08.400> to<01:48:08.520> use<01:48:08.640> a 01:48:08.660 --> 01:48:08.670 align:start position:0% know pretty big but it had to use a 01:48:08.670 --> 01:48:11.810 align:start position:0% know pretty big but it had to use a light<01:48:09.000> clients<01:48:09.780> as<01:48:10.020> far<01:48:10.260> as<01:48:10.410> I<01:48:10.500> know<01:48:10.820> download 01:48:11.810 --> 01:48:11.820 align:start position:0% light clients as far as I know download 01:48:11.820 --> 01:48:14.270 align:start position:0% light clients as far as I know download all<01:48:12.060> the<01:48:12.240> others<01:48:12.680> that<01:48:13.680> doesn't<01:48:14.070> verify 01:48:14.270 --> 01:48:14.280 align:start position:0% all the others that doesn't verify 01:48:14.280 --> 01:48:22.430 align:start position:0% all the others that doesn't verify everyone<01:48:15.030> maybe<01:48:15.270> like<01:48:15.570> every<01:48:21.110> just<01:48:22.110> random 01:48:22.430 --> 01:48:22.440 align:start position:0% everyone maybe like every just random 01:48:22.440 --> 01:48:24.650 align:start position:0% everyone maybe like every just random number<01:48:22.740> just<01:48:23.010> a<01:48:23.160> minute<01:48:23.970> it's<01:48:24.180> higher 01:48:24.650 --> 01:48:24.660 align:start position:0% number just a minute it's higher 01:48:24.660 --> 01:48:32.090 align:start position:0% number just a minute it's higher yes<01:48:24.870> it<01:48:26.180> was<01:48:27.180> it's<01:48:27.330> very<01:48:27.540> motivated<01:48:28.050> yeah<01:48:31.100> so 01:48:32.090 --> 01:48:32.100 align:start position:0% yes it was it's very motivated yeah so 01:48:32.100 --> 01:48:34.120 align:start position:0% yes it was it's very motivated yeah so your<01:48:32.250> professional<01:48:32.760> wine<01:48:32.940> up<01:48:33.090> up<01:48:33.270> codes<01:48:33.540> and 01:48:34.120 --> 01:48:34.130 align:start position:0% your professional wine up up codes and 01:48:34.130 --> 01:48:39.340 align:start position:0% your professional wine up up codes and I<01:48:36.910> think<01:48:37.910> even<01:48:38.090> the<01:48:38.390> the<01:48:38.690> initial<01:48:39.140> set<01:48:39.260> of 01:48:39.340 --> 01:48:39.350 align:start position:0% I think even the the initial set of 01:48:39.350 --> 01:48:40.929 align:start position:0% I think even the the initial set of freaking<01:48:39.650> christ-like 01:48:40.929 --> 01:48:40.939 align:start position:0% freaking christ-like 01:48:40.939 --> 01:48:44.859 align:start position:0% freaking christ-like the<01:48:41.110> sheriff<01:48:42.110> f6<01:48:42.559> rapidly<01:48:43.659> along<01:48:44.659> with 01:48:44.859 --> 01:48:44.869 align:start position:0% the sheriff f6 rapidly along with 01:48:44.869 --> 01:48:49.299 align:start position:0% the sheriff f6 rapidly along with catching<01:48:45.320> all<01:48:45.590> those<01:48:45.829> words<01:48:46.789> and<01:48:47.619> then<01:48:48.619> those 01:48:49.299 --> 01:48:49.309 align:start position:0% catching all those words and then those 01:48:49.309 --> 01:48:51.790 align:start position:0% catching all those words and then those accept<01:48:49.820> a<01:48:49.999> check<01:48:50.150> we<01:48:50.300> went<01:48:50.510> out<01:48:50.719> to<01:48:51.019> this<01:48:51.499> new 01:48:51.790 --> 01:48:51.800 align:start position:0% accept a check we went out to this new 01:48:51.800 --> 01:48:54.310 align:start position:0% accept a check we went out to this new concept<01:48:52.249> of<01:48:52.429> recompenses<01:48:53.179> kitchen<01:48:53.900> and<01:48:54.169> he 01:48:54.310 --> 01:48:54.320 align:start position:0% concept of recompenses kitchen and he 01:48:54.320 --> 01:49:07.989 align:start position:0% concept of recompenses kitchen and he was<01:48:54.349> left<01:48:54.739> to<01:48:54.829> kiss<01:48:55.099> it<01:48:55.729> would<01:48:55.909> be<01:48:56.030> more<01:49:06.999> like 01:49:07.989 --> 01:49:07.999 align:start position:0% was left to kiss it would be more like 01:49:07.999 --> 01:49:14.069 align:start position:0% was left to kiss it would be more like it<01:49:08.030> except<01:49:08.539> obviously<01:49:08.900> the<01:49:09.019> address 01:49:14.069 --> 01:49:14.079 align:start position:0% 01:49:14.079 --> 01:49:17.620 align:start position:0% basically<01:49:15.079> online<01:49:16.150> so<01:49:17.150> what<01:49:17.329> would<01:49:17.449> be<01:49:17.510> the 01:49:17.620 --> 01:49:17.630 align:start position:0% basically online so what would be the 01:49:17.630 --> 01:49:32.149 align:start position:0% basically online so what would be the benefit<01:49:18.079> having<01:49:18.260> them<01:49:18.499> as<01:49:21.039> well 01:49:32.149 --> 01:49:32.159 align:start position:0% 01:49:32.159 --> 01:49:36.529 align:start position:0% so<01:49:33.159> to<01:49:33.489> me<01:49:33.639> like<01:49:33.820> people<01:49:35.039> exhausting<01:49:36.039> the 01:49:36.529 --> 01:49:36.539 align:start position:0% so to me like people exhausting the 01:49:36.539 --> 01:49:54.359 align:start position:0% so to me like people exhausting the space<01:49:41.909> my<01:49:42.909> big<01:49:43.179> deal<01:49:45.269> it's<01:49:46.269> mine<01:49:52.979> ya<01:49:53.979> know<01:49:54.219> it's 01:49:54.359 --> 01:49:54.369 align:start position:0% space my big deal it's mine ya know it's 01:49:54.369 --> 01:50:04.979 align:start position:0% space my big deal it's mine ya know it's like<01:49:54.550> stuff<01:49:54.969> feels<01:49:55.329> like<01:49:55.709> problems<01:50:03.959> yeah<01:50:04.959> I 01:50:04.979 --> 01:50:04.989 align:start position:0% like stuff feels like problems yeah I 01:50:04.989 --> 01:50:08.100 align:start position:0% like stuff feels like problems yeah I don't<01:50:05.349> know<01:50:06.209> from<01:50:07.209> this<01:50:07.360> point<01:50:07.630> I<01:50:07.869> wanna 01:50:08.100 --> 01:50:08.110 align:start position:0% don't know from this point I wanna 01:50:08.110 --> 01:50:12.989 align:start position:0% don't know from this point I wanna contain<01:50:08.619> much<01:50:08.860> concern<01:50:10.260> but<01:50:11.260> I<01:50:11.499> I<01:50:11.530> so<01:50:12.189> 5°<01:50:12.789> like 01:50:12.989 --> 01:50:12.999 align:start position:0% contain much concern but I I so 5° like 01:50:12.999 --> 01:50:15.689 align:start position:0% contain much concern but I I so 5° like that's<01:50:13.780> not<01:50:13.989> the<01:50:14.050> issue<01:50:14.320> at<01:50:14.469> all<01:50:14.679> but<01:50:14.979> I<01:50:15.340> think 01:50:15.689 --> 01:50:15.699 align:start position:0% that's not the issue at all but I think 01:50:15.699 --> 01:50:19.379 align:start position:0% that's not the issue at all but I think I<01:50:15.909> was<01:50:16.539> corrected<01:50:17.260> in<01:50:17.289> fact<01:50:17.649> it<01:50:17.829> is<01:50:18.300> so<01:50:19.300> he 01:50:19.379 --> 01:50:19.389 align:start position:0% I was corrected in fact it is so he 01:50:19.389 --> 01:50:26.310 align:start position:0% I was corrected in fact it is so he still<01:50:19.630> has<01:50:19.659> next<01:50:23.849> but<01:50:24.869> well<01:50:25.869> there's<01:50:26.110> no<01:50:26.199> white 01:50:26.310 --> 01:50:26.320 align:start position:0% still has next but well there's no white 01:50:26.320 --> 01:50:39.550 align:start position:0% still has next but well there's no white water<01:50:26.619> on<01:50:26.860> it 01:50:39.550 --> 01:50:39.560 align:start position:0% 01:50:39.560 --> 01:50:52.620 align:start position:0% [Music] 01:50:52.620 --> 01:50:52.630 align:start position:0% 01:50:52.630 --> 01:51:10.250 align:start position:0% [Music] 01:51:10.250 --> 01:51:10.260 align:start position:0% 01:51:10.260 --> 01:51:41.800 align:start position:0% [Music] 01:51:41.800 --> 01:51:41.810 align:start position:0% 01:51:41.810 --> 01:51:49.490 align:start position:0% like<01:51:42.810> how<01:51:43.050> do<01:51:43.110> we<01:51:43.290> know<01:51:47.570> about<01:51:48.570> the<01:51:48.810> space 01:51:49.490 --> 01:51:49.500 align:start position:0% like how do we know about the space 01:51:49.500 --> 01:51:52.130 align:start position:0% like how do we know about the space there's<01:51:49.860> this<01:51:49.980> interesting<01:51:50.449> VIP<01:51:51.449> or<01:51:51.929> what 01:51:52.130 --> 01:51:52.140 align:start position:0% there's this interesting VIP or what 01:51:52.140 --> 01:51:56.810 align:start position:0% there's this interesting VIP or what Gavin<01:51:52.670> -<01:51:53.670> instead<01:51:54.420> of<01:51:54.480> having<01:51:54.690> like<01:51:55.650> oh<01:51:56.340> yeah 01:51:56.810 --> 01:51:56.820 align:start position:0% Gavin - instead of having like oh yeah 01:51:56.820 --> 01:51:59.630 align:start position:0% Gavin - instead of having like oh yeah exactly<01:51:57.150> instead<01:51:57.690> of<01:51:57.780> having<01:51:58.070> six<01:51:59.070> you<01:51:59.550> know 01:51:59.630 --> 01:51:59.640 align:start position:0% exactly instead of having six you know 01:51:59.640 --> 01:52:01.729 align:start position:0% exactly instead of having six you know sixteen<01:52:00.090> different<01:52:00.239> types<01:52:00.810> of<01:52:01.199> calls<01:52:01.409> you 01:52:01.729 --> 01:52:01.739 align:start position:0% sixteen different types of calls you 01:52:01.739 --> 01:52:03.730 align:start position:0% sixteen different types of calls you have<01:52:01.890> one<01:52:02.670> and<01:52:03.000> then 01:52:03.730 --> 01:52:03.740 align:start position:0% have one and then 01:52:03.740 --> 01:52:06.130 align:start position:0% have one and then it's<01:52:04.460> a<01:52:04.550> parameter<01:52:05.000> or<01:52:05.030> what<01:52:05.270> kind<01:52:05.690> of<01:52:05.750> quality 01:52:06.130 --> 01:52:06.140 align:start position:0% it's a parameter or what kind of quality 01:52:06.140 --> 01:52:19.740 align:start position:0% it's a parameter or what kind of quality one<01:52:06.350> going<01:52:06.920> to<01:52:06.950> do<01:52:07.240> seven<01:52:08.240> reduce<01:52:08.540> the<01:52:12.160> space 01:52:19.740 --> 01:52:19.750 align:start position:0% 01:52:19.750 --> 01:52:37.840 align:start position:0% yeah<01:52:35.830> so<01:52:36.830> while<01:52:37.010> you<01:52:37.100> also<01:52:37.250> get<01:52:37.490> to<01:52:37.580> levy<01:52:37.820> on 01:52:37.840 --> 01:52:37.850 align:start position:0% yeah so while you also get to levy on 01:52:37.850 --> 01:52:40.720 align:start position:0% yeah so while you also get to levy on one<01:52:38.150> there<01:52:38.360> was<01:52:38.450> a<01:52:38.480> question<01:52:39.010> whether<01:52:40.010> there 01:52:40.720 --> 01:52:40.730 align:start position:0% one there was a question whether there 01:52:40.730 --> 01:52:42.430 align:start position:0% one there was a question whether there any<01:52:40.880> other<01:52:41.060> optimization<01:52:41.660> student<01:52:42.050> apart 01:52:42.430 --> 01:52:42.440 align:start position:0% any other optimization student apart 01:52:42.440 --> 01:52:47.700 align:start position:0% any other optimization student apart from<01:52:42.560> what<01:52:42.710> to<01:52:42.830> expend<01:52:43.160> in<01:52:43.310> the<01:52:43.370> morning<01:52:46.180> yeah 01:52:47.700 --> 01:52:47.710 align:start position:0% from what to expend in the morning yeah 01:52:47.710 --> 01:52:51.370 align:start position:0% from what to expend in the morning yeah number<01:52:48.710> of<01:52:49.090> damn<01:52:50.090> but<01:52:50.480> they're<01:52:50.870> kind<01:52:51.230> of<01:52:51.320> like 01:52:51.370 --> 01:52:51.380 align:start position:0% number of damn but they're kind of like 01:52:51.380 --> 01:52:55.480 align:start position:0% number of damn but they're kind of like like<01:52:52.370> the<01:52:53.150> growth<01:52:53.420> engine<01:52:54.350> named<01:52:54.620> off<01:52:54.890> so<01:52:55.160> this 01:52:55.480 --> 01:52:55.490 align:start position:0% like the growth engine named off so this 01:52:55.490 --> 01:53:00.660 align:start position:0% like the growth engine named off so this like<01:52:56.120> I<01:52:56.500> don't<01:52:57.500> know<01:52:57.620> if<01:52:57.920> I<01:52:58.100> can<01:52:58.280> even<01:52:58.370> start 01:53:00.660 --> 01:53:00.670 align:start position:0% like I don't know if I can even start 01:53:00.670 --> 01:53:26.640 align:start position:0% like I don't know if I can even start but<01:53:01.670> yet<01:53:01.880> reallocate<01:53:02.540> stock 01:53:26.640 --> 01:53:26.650 align:start position:0% 01:53:26.650 --> 01:54:10.960 align:start position:0% yeah<01:54:06.490> yeah<01:54:08.950> yeah<01:54:09.950> we<01:54:10.250> can<01:54:10.400> simplify<01:54:10.730> that 01:54:10.960 --> 01:54:10.970 align:start position:0% yeah yeah yeah we can simplify that 01:54:10.970 --> 01:54:13.480 align:start position:0% yeah yeah yeah we can simplify that because<01:54:11.810> of<01:54:11.960> the<01:54:12.110> block<01:54:12.320> of<01:54:12.500> instructions 01:54:13.480 --> 01:54:13.490 align:start position:0% because of the block of instructions 01:54:13.490 --> 01:54:16.480 align:start position:0% because of the block of instructions yeah<01:54:13.730> but<01:54:14.210> you<01:54:14.300> can<01:54:14.450> also<01:54:15.190> calculate<01:54:16.190> the 01:54:16.480 --> 01:54:16.490 align:start position:0% yeah but you can also calculate the 01:54:16.490 --> 01:54:19.300 align:start position:0% yeah but you can also calculate the desire<01:54:17.000> you<01:54:17.300> are<01:54:17.480> yeah<01:54:18.080> and<01:54:18.440> there<01:54:18.980> were<01:54:19.160> the 01:54:19.300 --> 01:54:19.310 align:start position:0% desire you are yeah and there were the 01:54:19.310 --> 01:54:21.430 align:start position:0% desire you are yeah and there were the morons<01:54:19.580> in<01:54:19.730> the<01:54:19.820> work<01:54:20.030> so<01:54:20.390> I<01:54:20.420> thought<01:54:21.050> it's<01:54:21.230> the 01:54:21.430 --> 01:54:21.440 align:start position:0% morons in the work so I thought it's the 01:54:21.440 --> 01:54:23.350 align:start position:0% morons in the work so I thought it's the most<01:54:21.710> important<01:54:22.430> model<01:54:22.640> but<01:54:22.850> actually<01:54:23.210> it's 01:54:23.350 --> 01:54:23.360 align:start position:0% most important model but actually it's 01:54:23.360 --> 01:54:23.590 align:start position:0% most important model but actually it's not 01:54:23.590 --> 01:54:23.600 align:start position:0% not 01:54:23.600 --> 01:54:26.740 align:start position:0% not I<01:54:23.870> mean<01:54:24.140> so<01:54:24.740> I<01:54:25.130> think<01:54:25.520> good<01:54:25.850> news<01:54:26.090> like<01:54:26.390> the 01:54:26.740 --> 01:54:26.750 align:start position:0% I mean so I think good news like the 01:54:26.750 --> 01:54:29.890 align:start position:0% I mean so I think good news like the integer<01:54:27.170> implementation<01:54:27.980> I<01:54:28.370> think<01:54:29.060> we 01:54:29.890 --> 01:54:29.900 align:start position:0% integer implementation I think we 01:54:29.900 --> 01:54:31.030 align:start position:0% integer implementation I think we actually<01:54:30.230> change<01:54:30.470> the<01:54:30.590> integer 01:54:31.030 --> 01:54:31.040 align:start position:0% actually change the integer 01:54:31.040 --> 01:54:34.500 align:start position:0% actually change the integer implementation<01:54:31.760> we<01:54:31.880> hire<01:54:32.120> from<01:54:33.050> gusto<01:54:33.860> and 01:54:34.500 --> 01:54:34.510 align:start position:0% implementation we hire from gusto and 01:54:34.510 --> 01:54:38.279 align:start position:0% implementation we hire from gusto and index<01:54:35.510> and<01:54:36.020> it's<01:54:36.800> like<01:54:37.010> three<01:54:37.220> times 01:54:38.279 --> 01:54:38.289 align:start position:0% index and it's like three times 01:54:38.289 --> 01:54:50.160 align:start position:0% index and it's like three times so<01:54:39.309> things<01:54:42.340> change 01:54:50.160 --> 01:54:50.170 align:start position:0% 01:54:50.170 --> 01:54:54.609 align:start position:0% Mark<01:54:51.170> Martin<01:54:51.349> brain<01:54:52.539> insecurely<01:54:53.539> idea<01:54:54.050> yes 01:54:54.609 --> 01:54:54.619 align:start position:0% Mark Martin brain insecurely idea yes 01:54:54.619 --> 01:54:57.700 align:start position:0% Mark Martin brain insecurely idea yes this<01:54:55.550> is<01:54:55.849> definitely<01:54:56.269> faster<01:54:57.110> than<01:54:57.139> the<01:54:57.440> bigot 01:54:57.700 --> 01:54:57.710 align:start position:0% this is definitely faster than the bigot 01:54:57.710 --> 01:55:01.479 align:start position:0% this is definitely faster than the bigot library<01:54:58.159> but<01:54:58.519> in<01:54:59.449> practice<01:54:59.989> it<01:55:00.170> doesn't<01:55:00.489> make 01:55:01.479 --> 01:55:01.489 align:start position:0% library but in practice it doesn't make 01:55:01.489 --> 01:55:04.049 align:start position:0% library but in practice it doesn't make a<01:55:01.519> difference 01:55:04.049 --> 01:55:04.059 align:start position:0% 01:55:04.059 --> 01:55:09.939 align:start position:0% no<01:55:05.229> because<01:55:06.429> when<01:55:07.429> even<01:55:07.639> if<01:55:07.729> you<01:55:07.880> make<01:55:08.949> 10 01:55:09.939 --> 01:55:09.949 align:start position:0% no because when even if you make 10 01:55:09.949 --> 01:55:14.189 align:start position:0% no because when even if you make 10 times<01:55:10.130> faster<01:55:10.820> if<01:55:11.630> they<01:55:11.929> are<01:55:12.050> thematic<01:55:12.619> the 01:55:14.189 --> 01:55:14.199 align:start position:0% times faster if they are thematic the 01:55:14.199 --> 01:55:16.930 align:start position:0% times faster if they are thematic the contribution<01:55:15.199> of<01:55:15.289> their<01:55:15.440> automatic<01:55:15.800> offs<01:55:16.190> to 01:55:16.930 --> 01:55:16.940 align:start position:0% contribution of their automatic offs to 01:55:16.940 --> 01:55:19.540 align:start position:0% contribution of their automatic offs to the<01:55:17.210> actual<01:55:17.539> execution<01:55:18.050> time<01:55:18.650> is<01:55:18.920> only<01:55:19.280> this 01:55:19.540 --> 01:55:19.550 align:start position:0% the actual execution time is only this 01:55:19.550 --> 01:55:22.569 align:start position:0% the actual execution time is only this portion<01:55:19.849> it<01:55:20.210> doesn't<01:55:20.510> matter<01:55:20.630> this<01:55:21.489> so<01:55:22.489> you 01:55:22.569 --> 01:55:22.579 align:start position:0% portion it doesn't matter this so you 01:55:22.579 --> 01:55:24.160 align:start position:0% portion it doesn't matter this so you were<01:55:22.699> benchmarking<01:55:23.269> it<01:55:23.389> against<01:55:23.659> like<01:55:23.869> the 01:55:24.160 --> 01:55:24.170 align:start position:0% were benchmarking it against like the 01:55:24.170 --> 01:55:26.410 align:start position:0% were benchmarking it against like the full<01:55:24.380> Saint<01:55:24.679> yeah<01:55:24.889> right<01:55:25.639> that's<01:55:25.969> it 01:55:26.410 --> 01:55:26.420 align:start position:0% full Saint yeah right that's it 01:55:26.420 --> 01:55:29.830 align:start position:0% full Saint yeah right that's it but<01:55:26.809> if<01:55:26.900> you<01:55:27.019> run<01:55:27.530> a<01:55:27.940> numerical<01:55:28.940> benchmark 01:55:29.830 --> 01:55:29.840 align:start position:0% but if you run a numerical benchmark 01:55:29.840 --> 01:55:32.080 align:start position:0% but if you run a numerical benchmark just<01:55:30.139> a<01:55:30.280> traditional<01:55:31.280> opcodes<01:55:31.760> you<01:55:31.849> would<01:55:31.969> see 01:55:32.080 --> 01:55:32.090 align:start position:0% just a traditional opcodes you would see 01:55:32.090 --> 01:55:37.419 align:start position:0% just a traditional opcodes you would see a<01:55:32.119> big<01:55:32.179> speed<01:55:32.809> up<01:55:32.929> yes<01:55:35.800> so<01:55:36.800> if<01:55:36.949> you<01:55:37.130> would<01:55:37.309> have 01:55:37.419 --> 01:55:37.429 align:start position:0% a big speed up yes so if you would have 01:55:37.429 --> 01:55:40.930 align:start position:0% a big speed up yes so if you would have to<01:55:38.150> deploy<01:55:38.389> those<01:55:38.659> changes<01:55:39.280> and<01:55:40.280> habit 01:55:40.930 --> 01:55:40.940 align:start position:0% to deploy those changes and habit 01:55:40.940 --> 01:55:43.750 align:start position:0% to deploy those changes and habit actively<01:55:41.479> we<01:55:41.630> could<01:55:41.840> reprise<01:55:42.320> those<01:55:42.920> as<01:55:43.579> we 01:55:43.750 --> 01:55:43.760 align:start position:0% actively we could reprise those as we 01:55:43.760 --> 01:55:44.850 align:start position:0% actively we could reprise those as we discuss<01:55:44.090> it 01:55:44.850 --> 01:55:44.860 align:start position:0% discuss it 01:55:44.860 --> 01:55:47.520 align:start position:0% discuss it of<01:55:45.220> those<01:55:45.510> thing<01:55:46.510> could<01:55:46.720> be<01:55:46.870> get<01:55:47.080> rid<01:55:47.230> of<01:55:47.290> some 01:55:47.520 --> 01:55:47.530 align:start position:0% of those thing could be get rid of some 01:55:47.530 --> 01:56:20.390 align:start position:0% of those thing could be get rid of some difficult<01:55:56.940> levels<01:55:57.940> of<01:55:58.060> things<01:55:58.270> well 01:56:20.390 --> 01:56:20.400 align:start position:0% 01:56:20.400 --> 01:56:22.910 align:start position:0% ideally<01:56:21.240> you<01:56:21.450> want<01:56:22.110> people<01:56:22.380> to<01:56:22.530> be<01:56:22.710> able<01:56:22.770> to 01:56:22.910 --> 01:56:22.920 align:start position:0% ideally you want people to be able to 01:56:22.920 --> 01:56:26.630 align:start position:0% ideally you want people to be able to like<01:56:23.760> write<01:56:24.060> to<01:56:24.210> me<01:56:24.330> printf<01:56:24.720> function<01:56:25.100> to<01:56:26.100> rely 01:56:26.630 --> 01:56:26.640 align:start position:0% like write to me printf function to rely 01:56:26.640 --> 01:56:29.570 align:start position:0% like write to me printf function to rely on<01:56:26.670> the<01:56:27.060> the<01:56:27.960> client<01:56:28.290> is<01:56:28.440> to<01:56:28.680> tonight<01:56:29.010> oh<01:56:29.040> yeah 01:56:29.570 --> 01:56:29.580 align:start position:0% on the the client is to tonight oh yeah 01:56:29.580 --> 01:56:34.640 align:start position:0% on the the client is to tonight oh yeah there<01:56:30.540> gets<01:56:30.810> the<01:56:30.900> very<01:56:31.560> impossible<01:56:33.410> in<01:56:34.410> terms 01:56:34.640 --> 01:56:34.650 align:start position:0% there gets the very impossible in terms 01:56:34.650 --> 01:56:36.860 align:start position:0% there gets the very impossible in terms of<01:56:34.970> displacements<01:56:35.970> accompany<01:56:36.390> against<01:56:36.720> what 01:56:36.860 --> 01:56:36.870 align:start position:0% of displacements accompany against what 01:56:36.870 --> 01:56:44.600 align:start position:0% of displacements accompany against what treatment<01:56:37.410> miles<01:56:37.560> velocity<01:56:43.130> excess<01:56:44.130> are<01:56:44.340> over 01:56:44.600 --> 01:56:44.610 align:start position:0% treatment miles velocity excess are over 01:56:44.610 --> 01:56:47.630 align:start position:0% treatment miles velocity excess are over it's<01:56:44.880> a<01:56:44.940> fail<01:56:45.150> on<01:56:45.300> for<01:56:45.540> so<01:56:45.660> many<01:56:45.750> staff<01:56:46.640> yes 01:56:47.630 --> 01:56:47.640 align:start position:0% it's a fail on for so many staff yes 01:56:47.640 --> 01:56:52.540 align:start position:0% it's a fail on for so many staff yes it's<01:56:48.600> unfortunate<01:56:48.750> II<01:56:49.320> like<01:56:49.500> that<01:56:49.530> but<01:56:49.890> then 01:56:52.540 --> 01:56:52.550 align:start position:0% 01:56:52.550 --> 01:57:10.690 align:start position:0% [Music] 01:57:10.690 --> 01:57:10.700 align:start position:0% 01:57:10.700 --> 01:57:12.920 align:start position:0% one<01:57:11.700> of<01:57:11.730> the<01:57:11.880> problem<01:57:12.150> speaking<01:57:12.390> Francis 01:57:12.920 --> 01:57:12.930 align:start position:0% one of the problem speaking Francis 01:57:12.930 --> 01:57:14.570 align:start position:0% one of the problem speaking Francis people<01:57:13.320> just<01:57:13.560> want<01:57:13.950> to<01:57:14.010> get<01:57:14.190> these<01:57:14.340> features 01:57:14.570 --> 01:57:14.580 align:start position:0% people just want to get these features 01:57:14.580 --> 01:57:19.460 align:start position:0% people just want to get these features and<01:57:15.090> not<01:57:16.020> enough<01:57:16.350> to<01:57:16.530> to<01:57:17.280> wait<01:57:18.170> so<01:57:19.170> they<01:57:19.290> cannot 01:57:19.460 --> 01:57:19.470 align:start position:0% and not enough to to wait so they cannot 01:57:19.470 --> 01:57:21.080 align:start position:0% and not enough to to wait so they cannot do<01:57:19.860> many<01:57:20.100> of<01:57:20.190> these<01:57:20.310> things<01:57:20.370> on<01:57:20.760> the<01:57:20.790> again 01:57:21.080 --> 01:57:21.090 align:start position:0% do many of these things on the again 01:57:21.090 --> 01:57:23.300 align:start position:0% do many of these things on the again today<01:57:21.510> so<01:57:21.960> that's<01:57:22.110> banana<01:57:22.470> have<01:57:22.680> to<01:57:22.800> ask<01:57:23.010> for 01:57:23.300 --> 01:57:23.310 align:start position:0% today so that's banana have to ask for 01:57:23.310 --> 01:57:26.270 align:start position:0% today so that's banana have to ask for somebody<01:57:24.150> to<01:57:24.300> compose<01:57:24.660> it<01:57:24.870> and<01:57:25.170> be<01:57:25.800> lucky<01:57:26.010> to 01:57:26.270 --> 01:57:26.280 align:start position:0% somebody to compose it and be lucky to 01:57:26.280 --> 01:57:29.180 align:start position:0% somebody to compose it and be lucky to be<01:57:26.430> accepted<01:57:26.790> and<01:57:27.510> then<01:57:27.780> going<01:57:28.200> too<01:57:28.350> hard<01:57:28.890> for 01:57:29.180 --> 01:57:29.190 align:start position:0% be accepted and then going too hard for 01:57:29.190 --> 01:57:32.150 align:start position:0% be accepted and then going too hard for get<01:57:29.370> some<01:57:29.610> points<01:57:29.940> and<01:57:30.060> give<01:57:30.390> and<01:57:30.690> be<01:57:31.170> on<01:57:31.980> the 01:57:32.150 --> 01:57:32.160 align:start position:0% get some points and give and be on the 01:57:32.160 --> 01:57:33.590 align:start position:0% get some points and give and be on the sugar<01:57:32.400> veteran<01:57:32.790> goes<01:57:32.970> into<01:57:33.210> the<01:57:33.330> heart<01:57:33.480> from 01:57:33.590 --> 01:57:33.600 align:start position:0% sugar veteran goes into the heart from 01:57:33.600 --> 01:57:35.360 align:start position:0% sugar veteran goes into the heart from two<01:57:33.750> weeks<01:57:34.050> before<01:57:34.230> the<01:57:34.440> hard<01:57:34.620> work<01:57:34.800> Evans 01:57:35.360 --> 01:57:35.370 align:start position:0% two weeks before the hard work Evans 01:57:35.370 --> 01:57:39.459 align:start position:0% two weeks before the hard work Evans yeah<01:57:36.050> okay<01:57:37.050> so<01:57:37.110> you<01:57:37.320> made<01:57:37.500> some<01:57:37.530> benchmarks 01:57:39.459 --> 01:57:39.469 align:start position:0% yeah okay so you made some benchmarks 01:57:39.469 --> 01:57:40.899 align:start position:0% yeah okay so you made some benchmarks and<01:57:39.590> I<01:57:39.650> think<01:57:39.709> you<01:57:39.949> made<01:57:40.130> some<01:57:40.159> benchmarks<01:57:40.760> for 01:57:40.899 --> 01:57:40.909 align:start position:0% and I think you made some benchmarks for 01:57:40.909 --> 01:57:42.609 align:start position:0% and I think you made some benchmarks for some<01:57:41.209> existing<01:57:41.630> people<01:57:41.809> who<01:57:42.050> has<01:57:42.169> maybe<01:57:42.349> some 01:57:42.609 --> 01:57:42.619 align:start position:0% some existing people who has maybe some 01:57:42.619 --> 01:57:44.830 align:start position:0% some existing people who has maybe some proposed<01:57:42.949> ones<01:57:43.280> but<01:57:43.909> are<01:57:44.150> there<01:57:44.360> any<01:57:44.449> one 01:57:44.830 --> 01:57:44.840 align:start position:0% proposed ones but are there any one 01:57:44.840 --> 01:57:50.679 align:start position:0% proposed ones but are there any one switch<01:57:45.340> with<01:57:46.340> like<01:57:46.550> EVM<01:57:47.059> one<01:57:49.239> or<01:57:50.239> anyone's 01:57:50.679 --> 01:57:50.689 align:start position:0% switch with like EVM one or anyone's 01:57:50.689 --> 01:57:52.929 align:start position:0% switch with like EVM one or anyone's which<01:57:50.900> could<01:57:51.199> be<01:57:51.349> just<01:57:51.650> done<01:57:51.829> home<01:57:52.070> with<01:57:52.669> India 01:57:52.929 --> 01:57:52.939 align:start position:0% which could be just done home with India 01:57:52.939 --> 01:57:54.609 align:start position:0% which could be just done home with India moment<01:57:53.389> without<01:57:53.689> having<01:57:53.959> them<01:57:54.050> specialize 01:57:54.609 --> 01:57:54.619 align:start position:0% moment without having them specialize 01:57:54.619 --> 01:58:00.479 align:start position:0% moment without having them specialize whether<01:57:55.489> in<01:57:55.760> such<01:57:56.030> cases<01:57:56.300> we<01:57:57.019> have<01:57:57.169> only<01:57:57.320> to<01:57:57.619> me 01:58:00.479 --> 01:58:00.489 align:start position:0% 01:58:00.489 --> 01:58:04.839 align:start position:0% it<01:58:01.489> was<01:58:02.380> well<01:58:03.380> I<01:58:03.559> mean<01:58:03.709> the<01:58:04.130> thing<01:58:04.309> is<01:58:04.340> we<01:58:04.699> have 01:58:04.839 --> 01:58:04.849 align:start position:0% it was well I mean the thing is we have 01:58:04.849 --> 01:58:08.679 align:start position:0% it was well I mean the thing is we have to<01:58:05.409> be<01:58:06.409> careful<01:58:06.769> about<01:58:06.949> power<01:58:07.309> metering<01:58:07.849> you 01:58:08.679 --> 01:58:08.689 align:start position:0% to be careful about power metering you 01:58:08.689 --> 01:58:10.929 align:start position:0% to be careful about power metering you know<01:58:08.780> those<01:58:09.169> new<01:58:09.439> codes<01:58:10.309> and<01:58:10.459> so<01:58:10.579> we<01:58:10.729> don't 01:58:10.929 --> 01:58:10.939 align:start position:0% know those new codes and so we don't 01:58:10.939 --> 01:58:14.799 align:start position:0% know those new codes and so we don't have<01:58:11.360> the<01:58:11.860> studies<01:58:12.860> done<01:58:13.070> to<01:58:13.280> show<01:58:13.309> that<01:58:13.809> we 01:58:14.799 --> 01:58:14.809 align:start position:0% have the studies done to show that we 01:58:14.809 --> 01:58:18.669 align:start position:0% have the studies done to show that we can<01:58:14.989> safely<01:58:16.840> meter<01:58:17.840> them<01:58:18.079> and<01:58:18.260> get<01:58:18.349> the<01:58:18.499> full 01:58:18.669 --> 01:58:18.679 align:start position:0% can safely meter them and get the full 01:58:18.679 --> 01:58:23.339 align:start position:0% can safely meter them and get the full speed<01:58:18.949> up<01:58:19.099> so<01:58:19.369> that's<01:58:19.579> it's<01:58:19.849> going<01:58:19.999> to<01:58:20.119> be<01:58:20.209> done 01:58:23.339 --> 01:58:23.349 align:start position:0% 01:58:23.349 --> 01:58:26.830 align:start position:0% if<01:58:24.349> we're<01:58:24.590> optimistic<01:58:25.010> yeah<01:58:25.729> I<01:58:25.760> think<01:58:26.030> it's 01:58:26.830 --> 01:58:26.840 align:start position:0% if we're optimistic yeah I think it's 01:58:26.840 --> 01:58:29.859 align:start position:0% if we're optimistic yeah I think it's that's<01:58:27.679> when<01:58:27.860> show<01:58:28.099> would<01:58:28.249> be<01:58:28.659> sufficient<01:58:29.659> to 01:58:29.859 --> 01:58:29.869 align:start position:0% that's when show would be sufficient to 01:58:29.869 --> 01:58:38.489 align:start position:0% that's when show would be sufficient to replace<01:58:30.349> the<01:58:30.469> Green<01:58:30.650> Mile<01:58:32.469> but<01:58:37.090> cricket<01:58:38.090> they 01:58:38.489 --> 01:58:38.499 align:start position:0% replace the Green Mile but cricket they 01:58:38.499 --> 01:58:42.870 align:start position:0% replace the Green Mile but cricket they asked<01:58:39.499> was<01:58:39.769> did<01:58:40.669> you<01:58:40.729> in<01:58:41.360> a<01:58:41.599> way<01:58:41.900> did<01:58:42.320> you<01:58:42.439> check 01:58:42.870 --> 01:58:42.880 align:start position:0% asked was did you in a way did you check 01:58:42.880 --> 01:58:46.930 align:start position:0% asked was did you in a way did you check where<01:58:43.880> the<01:58:44.090> gas<01:58:44.269> went<01:58:44.659> in 01:58:46.930 --> 01:58:46.940 align:start position:0% where the gas went in 01:58:46.940 --> 01:58:51.550 align:start position:0% where the gas went in I<01:58:47.800> guess<01:58:48.850> when<01:58:49.850> to<01:58:50.300> computational<01:58:51.199> answer 01:58:51.550 --> 01:58:51.560 align:start position:0% I guess when to computational answer 01:58:51.560 --> 01:58:53.709 align:start position:0% I guess when to computational answer what<01:58:51.980> when<01:58:52.250> things<01:58:52.460> to<01:58:52.730> memory<01:58:53.060> sheltering<01:58:53.540> of 01:58:53.709 --> 01:58:53.719 align:start position:0% what when things to memory sheltering of 01:58:53.719 --> 01:58:55.650 align:start position:0% what when things to memory sheltering of theta<01:58:54.250> and 01:58:55.650 --> 01:58:55.660 align:start position:0% theta and 01:58:55.660 --> 01:58:57.160 align:start position:0% theta and [Music] 01:58:57.160 --> 01:58:57.170 align:start position:0% [Music] 01:58:57.170 --> 01:59:00.350 align:start position:0% [Music] No<01:58:58.200> so<01:58:58.560> we<01:58:58.680> haven't<01:58:58.920> done<01:58:59.010> any<01:58:59.250> gas<01:58:59.760> analysis 01:59:00.350 --> 01:59:00.360 align:start position:0% No so we haven't done any gas analysis 01:59:00.360 --> 01:59:04.160 align:start position:0% No so we haven't done any gas analysis we<01:59:00.540> just<01:59:00.750> did<01:59:01.290> the<01:59:02.330> you<01:59:03.330> know<01:59:03.420> runtime<01:59:03.960> fetch 01:59:04.160 --> 01:59:04.170 align:start position:0% we just did the you know runtime fetch 01:59:04.170 --> 01:59:06.260 align:start position:0% we just did the you know runtime fetch my<01:59:04.350> runtime<01:59:04.830> on<01:59:05.010> EVM<01:59:05.340> one<01:59:05.550> that<01:59:05.820> stable<01:59:06.090> okay 01:59:06.260 --> 01:59:06.270 align:start position:0% my runtime on EVM one that stable okay 01:59:06.270 --> 01:59:07.640 align:start position:0% my runtime on EVM one that stable okay well<01:59:06.420> this<01:59:06.540> is<01:59:06.660> way<01:59:06.840> less<01:59:07.020> than<01:59:07.080> the<01:59:07.320> Hartnell 01:59:07.640 --> 01:59:07.650 align:start position:0% well this is way less than the Hartnell 01:59:07.650 --> 01:59:10.100 align:start position:0% well this is way less than the Hartnell socket<01:59:08.040> so<01:59:08.250> then<01:59:08.520> it<01:59:08.969> should<01:59:09.150> cost<01:59:09.420> less<01:59:09.810> than 01:59:10.100 --> 01:59:10.110 align:start position:0% socket so then it should cost less than 01:59:10.110 --> 01:59:17.479 align:start position:0% socket so then it should cost less than you<01:59:10.680> know<01:59:13.969> but<01:59:14.969> that<01:59:15.330> assumes<01:59:16.140> weekend<01:59:16.710> you 01:59:17.479 --> 01:59:17.489 align:start position:0% you know but that assumes weekend you 01:59:17.489 --> 01:59:20.180 align:start position:0% you know but that assumes weekend you know<01:59:17.610> optimistically<01:59:18.510> price<01:59:19.170> up<01:59:19.560> codes<01:59:19.920> and 01:59:20.180 --> 01:59:20.190 align:start position:0% know optimistically price up codes and 01:59:20.190 --> 01:59:23.600 align:start position:0% know optimistically price up codes and that<01:59:20.280> there<01:59:20.489> are<01:59:20.719> worst<01:59:21.719> case<01:59:22.370> runtimes<01:59:23.370> and 01:59:23.600 --> 01:59:23.610 align:start position:0% that there are worst case runtimes and 01:59:23.610 --> 01:59:25.850 align:start position:0% that there are worst case runtimes and EVM<01:59:24.030> once<01:59:24.270> nowhere<01:59:24.660> where<01:59:25.440> we<01:59:25.560> have<01:59:25.680> to<01:59:25.770> be 01:59:25.850 --> 01:59:25.860 align:start position:0% EVM once nowhere where we have to be 01:59:25.860 --> 02:00:04.620 align:start position:0% EVM once nowhere where we have to be more<01:59:25.980> conservative<01:59:26.340> with<01:59:26.670> our<01:59:26.700> embraced<01:59:27.150> them 02:00:04.620 --> 02:00:04.630 align:start position:0% 02:00:04.630 --> 02:00:15.970 align:start position:0% [Music] 02:00:15.970 --> 02:00:15.980 align:start position:0% 02:00:15.980 --> 02:00:24.950 align:start position:0% there<02:00:16.980> is<02:00:17.100> the<02:00:17.220> way<02:00:17.340> to<02:00:19.190> actually<02:00:20.270> start<02:00:23.960> you 02:00:24.950 --> 02:00:24.960 align:start position:0% there is the way to actually start you 02:00:24.960 --> 02:00:28.370 align:start position:0% there is the way to actually start you can<02:00:25.110> also<02:00:25.290> see<02:00:25.770> the<02:00:25.830> some<02:00:26.070> calls<02:00:26.400> I<02:00:26.760> mean<02:00:27.540> this 02:00:28.370 --> 02:00:28.380 align:start position:0% can also see the some calls I mean this 02:00:28.380 --> 02:00:31.790 align:start position:0% can also see the some calls I mean this minimax<02:00:28.830> again<02:00:29.160> except<02:00:30.120> rates<02:00:30.360> some<02:00:30.800> calls 02:00:31.790 --> 02:00:31.800 align:start position:0% minimax again except rates some calls 02:00:31.800 --> 02:00:34.130 align:start position:0% minimax again except rates some calls and<02:00:32.160> our<02:00:32.790> our<02:00:32.910> process<02:00:33.360> on<02:00:33.570> in<02:00:33.720> this<02:00:33.870> course 02:00:34.130 --> 02:00:34.140 align:start position:0% and our our process on in this course 02:00:34.140 --> 02:00:37.880 align:start position:0% and our our process on in this course task<02:00:35.000> image<02:00:36.000> everything<02:00:36.660> other<02:00:36.960> tasks<02:00:37.350> travel 02:00:37.880 --> 02:00:37.890 align:start position:0% task image everything other tasks travel 02:00:37.890 --> 02:00:41.140 align:start position:0% task image everything other tasks travel costs<02:00:38.280> and<02:00:38.450> this<02:00:39.450> think<02:00:40.260> LLVM<02:00:40.920> and 02:00:41.140 --> 02:00:41.150 align:start position:0% costs and this think LLVM and 02:00:41.150 --> 02:00:44.630 align:start position:0% costs and this think LLVM and documentation<02:00:42.150> and<02:00:42.950> attached<02:00:43.950> documentation 02:00:44.630 --> 02:00:44.640 align:start position:0% documentation and attached documentation 02:00:44.640 --> 02:00:47.270 align:start position:0% documentation and attached documentation that<02:00:45.060> describes<02:00:45.900> many<02:00:46.230> of<02:00:46.410> these<02:00:46.560> tricks<02:00:46.860> you 02:00:47.270 --> 02:00:47.280 align:start position:0% that describes many of these tricks you 02:00:47.280 --> 02:00:49.640 align:start position:0% that describes many of these tricks you can<02:00:47.460> disable<02:00:47.780> to<02:00:48.780> go<02:00:48.990> through<02:00:49.470> for 02:00:49.640 --> 02:00:49.650 align:start position:0% can disable to go through for 02:00:49.650 --> 02:00:51.740 align:start position:0% can disable to go through for frequencies<02:00:50.190> so<02:00:50.610> twice<02:00:50.820> on<02:00:51.030> the<02:00:51.180> like<02:00:51.510> base 02:00:51.740 --> 02:00:51.750 align:start position:0% frequencies so twice on the like base 02:00:51.750 --> 02:00:53.810 align:start position:0% frequencies so twice on the like base map<02:00:52.020> which<02:00:52.650> formal<02:00:53.010> app<02:00:53.130> don't<02:00:53.340> make<02:00:53.550> it<02:00:53.670> like 02:00:53.810 --> 02:00:53.820 align:start position:0% map which formal app don't make it like 02:00:53.820 --> 02:01:00.800 align:start position:0% map which formal app don't make it like four<02:00:54.090> times<02:00:54.240> slower<02:00:56.810> like<02:00:57.810> yeah<02:00:58.640> like<02:00:59.810> we 02:01:00.800 --> 02:01:00.810 align:start position:0% four times slower like yeah like we 02:01:00.810 --> 02:01:04.700 align:start position:0% four times slower like yeah like we mostly<02:01:01.680> interested<02:01:01.920> in<02:01:02.220> in<02:01:02.880> my<02:01:03.560> difference<02:01:04.560> is 02:01:04.700 --> 02:01:04.710 align:start position:0% mostly interested in in my difference is 02:01:04.710 --> 02:01:11.480 align:start position:0% mostly interested in in my difference is writing<02:01:06.380> and<02:01:09.200> many<02:01:10.200> other<02:01:10.470> things<02:01:10.770> but<02:01:11.130> I<02:01:11.340> also 02:01:11.480 --> 02:01:11.490 align:start position:0% writing and many other things but I also 02:01:11.490 --> 02:01:13.820 align:start position:0% writing and many other things but I also got<02:01:11.760> checked<02:01:12.060> there<02:01:12.270> the<02:01:12.710> variation<02:01:13.710> of 02:01:13.820 --> 02:01:13.830 align:start position:0% got checked there the variation of 02:01:13.830 --> 02:01:17.370 align:start position:0% got checked there the variation of extender 02:01:17.370 --> 02:01:17.380 align:start position:0% 02:01:17.380 --> 02:01:25.870 align:start position:0% [Music] 02:01:25.870 --> 02:01:25.880 align:start position:0% 02:01:25.880 --> 02:02:20.780 align:start position:0% but<02:01:30.860> I<02:01:33.110> mean<02:02:18.860> that's<02:02:19.860> the<02:02:20.010> easy<02:02:20.130> case<02:02:20.370> the<02:02:20.640> hurt 02:02:20.780 --> 02:02:20.790 align:start position:0% but I mean that's the easy case the hurt 02:02:20.790 --> 02:02:22.850 align:start position:0% but I mean that's the easy case the hurt is<02:02:21.000> when<02:02:21.270> you<02:02:21.330> start<02:02:21.600> dealing<02:02:22.140> with<02:02:22.380> the<02:02:22.560> i/o 02:02:22.850 --> 02:02:22.860 align:start position:0% is when you start dealing with the i/o 02:02:22.860 --> 02:02:23.720 align:start position:0% is when you start dealing with the i/o operations 02:02:23.720 --> 02:02:23.730 align:start position:0% operations 02:02:23.730 --> 02:02:28.300 align:start position:0% operations yeah<02:02:24.600> that's<02:02:24.960> I'm<02:02:25.290> not<02:02:25.610> striking<02:02:26.610> at<02:02:26.730> all 02:02:28.300 --> 02:02:28.310 align:start position:0% yeah that's I'm not striking at all 02:02:28.310 --> 02:02:31.790 align:start position:0% yeah that's I'm not striking at all thank<02:02:29.310> you<02:02:29.400> for<02:02:29.870> discussion 02:02:31.790 --> 02:02:31.800 align:start position:0% thank you for discussion 02:02:31.800 --> 02:02:35.940 align:start position:0% thank you for discussion let's<02:02:32.010> finish<02:02:32.220> this 02:02:35.940 --> 02:02:35.950 align:start position:0% 02:02:35.950 --> 02:02:40.420 align:start position:0% [Applause]