WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:01:05.399 align:start position:0% [Applause] 00:01:05.399 --> 00:01:05.409 align:start position:0% 00:01:05.409 --> 00:01:08.890 align:start position:0% so<00:01:06.409> this<00:01:07.220> is<00:01:07.400> more<00:01:07.940> or<00:01:07.970> less<00:01:08.120> a<00:01:08.420> continuation 00:01:08.890 --> 00:01:08.900 align:start position:0% so this is more or less a continuation 00:01:08.900 --> 00:01:12.690 align:start position:0% so this is more or less a continuation of<00:01:09.320> the<00:01:09.920> talk<00:01:10.310> I<00:01:10.460> gave<00:01:10.490> at<00:01:10.960> DEFCON<00:01:11.960> 4 00:01:12.690 --> 00:01:12.700 align:start position:0% of the talk I gave at DEFCON 4 00:01:12.700 --> 00:01:18.100 align:start position:0% of the talk I gave at DEFCON 4 let's<00:01:13.700> guess<00:01:15.190> community<00:01:16.190> it's<00:01:17.180> not<00:01:17.810> problem 00:01:18.100 --> 00:01:18.110 align:start position:0% let's guess community it's not problem 00:01:18.110 --> 00:01:19.899 align:start position:0% let's guess community it's not problem if<00:01:18.170> you<00:01:18.260> haven't<00:01:18.530> seen<00:01:18.650> that<00:01:18.680> talk<00:01:19.040> just 00:01:19.899 --> 00:01:19.909 align:start position:0% if you haven't seen that talk just 00:01:19.909 --> 00:01:26.170 align:start position:0% if you haven't seen that talk just context<00:01:20.810> not<00:01:21.440> talk<00:01:21.740> I<00:01:24.160> explained<00:01:25.160> how<00:01:25.340> we<00:01:25.759> want 00:01:26.170 --> 00:01:26.180 align:start position:0% context not talk I explained how we want 00:01:26.180 --> 00:01:29.499 align:start position:0% context not talk I explained how we want to<00:01:26.390> want<00:01:27.320> to<00:01:27.530> to<00:01:27.830> leverage<00:01:28.430> an<00:01:28.970> intermediate 00:01:29.499 --> 00:01:29.509 align:start position:0% to want to to leverage an intermediate 00:01:29.509 --> 00:01:42.930 align:start position:0% to want to to leverage an intermediate language<00:01:30.700> so<00:01:31.700> that<00:01:39.729> and<00:01:40.780> in<00:01:41.780> several<00:01:41.990> involve 00:01:42.930 --> 00:01:42.940 align:start position:0% language so that and in several involve 00:01:42.940 --> 00:01:47.980 align:start position:0% language so that and in several involve accessibility<00:01:43.940> it<00:01:44.000> was<00:01:44.390> which<00:01:44.660> back-end<00:01:46.990> you 00:01:47.980 --> 00:01:47.990 align:start position:0% accessibility it was which back-end you 00:01:47.990 --> 00:01:50.440 align:start position:0% accessibility it was which back-end you have<00:01:48.289> to<00:01:48.380> comply<00:01:48.680> to<00:01:48.890> IBM<00:01:49.399> to<00:01:49.700> be<00:01:49.850> Muslim<00:01:50.210> in 00:01:50.440 --> 00:01:50.450 align:start position:0% have to comply to IBM to be Muslim in 00:01:50.450 --> 00:01:54.389 align:start position:0% have to comply to IBM to be Muslim in one<00:01:50.750> run<00:01:50.899> five<00:01:51.080> or 00:01:54.389 --> 00:01:54.399 align:start position:0% 00:01:54.399 --> 00:01:57.819 align:start position:0% and<00:01:55.689> on<00:01:56.689> the<00:01:56.810> bottom<00:01:56.930> you<00:01:57.229> can<00:01:57.320> see<00:01:57.500> some 00:01:57.819 --> 00:01:57.829 align:start position:0% and on the bottom you can see some 00:01:57.829 --> 00:02:01.539 align:start position:0% and on the bottom you can see some example<00:01:58.220> new<00:01:58.399> code<00:01:58.670> is<00:01:59.500> in<00:02:00.500> allocation<00:02:01.159> or 00:02:01.539 --> 00:02:01.549 align:start position:0% example new code is in allocation or 00:02:01.549 --> 00:02:04.539 align:start position:0% example new code is in allocation or it's<00:02:01.640> a<00:02:01.700> standard<00:02:02.420> sylheti<00:02:03.100> alligator<00:02:04.100> memory 00:02:04.539 --> 00:02:04.549 align:start position:0% it's a standard sylheti alligator memory 00:02:04.549 --> 00:02:08.380 align:start position:0% it's a standard sylheti alligator memory allocator<00:02:04.960> and<00:02:05.960> i<00:02:06.049> think<00:02:06.409> is<00:02:06.820> obvious<00:02:07.820> what<00:02:08.239> it 00:02:08.380 --> 00:02:08.390 align:start position:0% allocator and i think is obvious what it 00:02:08.390 --> 00:02:19.930 align:start position:0% allocator and i think is obvious what it does 00:02:19.930 --> 00:02:19.940 align:start position:0% 00:02:19.940 --> 00:02:22.280 align:start position:0% okay<00:02:20.940> what<00:02:21.480> did<00:02:21.540> we<00:02:21.600> do<00:02:21.810> so<00:02:22.050> this<00:02:22.230> was 00:02:22.280 --> 00:02:22.290 align:start position:0% okay what did we do so this was 00:02:22.290 --> 00:02:24.470 align:start position:0% okay what did we do so this was basically<00:02:22.710> we<00:02:23.010> have<00:02:23.160> up<00:02:23.310> the<00:02:23.460> top<00:02:24.120> of<00:02:24.270> last 00:02:24.470 --> 00:02:24.480 align:start position:0% basically we have up the top of last 00:02:24.480 --> 00:02:26.810 align:start position:0% basically we have up the top of last year<00:02:24.690> and<00:02:24.840> what<00:02:25.020> happened<00:02:25.290> after<00:02:25.650> that<00:02:25.820> we 00:02:26.810 --> 00:02:26.820 align:start position:0% year and what happened after that we 00:02:26.820 --> 00:02:29.420 align:start position:0% year and what happened after that we started<00:02:27.240> the<00:02:28.200> rewrite<00:02:28.680> of<00:02:28.920> the<00:02:28.980> salinity 00:02:29.420 --> 00:02:29.430 align:start position:0% started the rewrite of the salinity 00:02:29.430 --> 00:02:35.690 align:start position:0% started the rewrite of the salinity generator<00:02:33.800> this<00:02:34.800> would<00:02:34.980> be<00:02:35.070> the<00:02:35.190> first<00:02:35.370> third 00:02:35.690 --> 00:02:35.700 align:start position:0% generator this would be the first third 00:02:35.700 --> 00:02:40.450 align:start position:0% generator this would be the first third of<00:02:35.880> the<00:02:35.940> talk<00:02:36.270> then<00:02:36.990> I<00:02:37.440> will<00:02:37.920> tell<00:02:38.100> you<00:02:38.280> how<00:02:39.320> he 00:02:40.450 --> 00:02:40.460 align:start position:0% of the talk then I will tell you how he 00:02:40.460 --> 00:02:44.180 align:start position:0% of the talk then I will tell you how he wasn't<00:02:41.460> called<00:02:41.670> from<00:02:42.000> solidity<00:02:42.360> and<00:02:42.950> the<00:02:43.950> last 00:02:44.180 --> 00:02:44.190 align:start position:0% wasn't called from solidity and the last 00:02:44.190 --> 00:02:51.640 align:start position:0% wasn't called from solidity and the last part<00:02:44.490> of<00:02:45.240> the<00:02:49.070> perpetrator<00:02:50.070> we<00:02:51.030> are<00:02:51.150> actually 00:02:51.640 --> 00:02:51.650 align:start position:0% part of the perpetrator we are actually 00:02:51.650 --> 00:02:54.200 align:start position:0% part of the perpetrator we are actually far<00:02:52.650> with<00:02:52.800> that<00:02:52.830> we<00:02:53.250> had<00:02:53.400> to<00:02:53.580> stop<00:02:53.910> at<00:02:54.060> some 00:02:54.200 --> 00:02:54.210 align:start position:0% far with that we had to stop at some 00:02:54.210 --> 00:02:56.300 align:start position:0% far with that we had to stop at some point<00:02:54.510> because<00:02:54.720> we<00:02:54.990> want<00:02:55.170> to<00:02:55.290> really<00:02:55.980> insulate 00:02:56.300 --> 00:02:56.310 align:start position:0% point because we want to really insulate 00:02:56.310 --> 00:03:03.320 align:start position:0% point because we want to really insulate you<00:02:56.610> zero<00:02:56.940> sixes 00:03:03.320 --> 00:03:03.330 align:start position:0% 00:03:03.330 --> 00:03:43.560 align:start position:0% we<00:03:04.330> are<00:03:21.990> the<00:03:41.730> reason<00:03:42.730> the<00:03:42.910> main<00:03:43.000> reason<00:03:43.060> why<00:03:43.450> we 00:03:43.560 --> 00:03:43.570 align:start position:0% we are the reason the main reason why we 00:03:43.570 --> 00:03:45.690 align:start position:0% we are the reason the main reason why we didn't<00:03:44.170> do<00:03:44.290> that<00:03:44.440> in<00:03:44.770> the<00:03:44.890> o2<00:03:45.190> villages 00:03:45.690 --> 00:03:45.700 align:start position:0% didn't do that in the o2 villages 00:03:45.700 --> 00:03:48.980 align:start position:0% didn't do that in the o2 villages because<00:03:46.090> it<00:03:47.610> yeah 00:03:48.980 --> 00:03:48.990 align:start position:0% because it yeah 00:03:48.990 --> 00:04:16.110 align:start position:0% because it yeah these<00:03:49.990> checks<00:03:50.620> will<00:03:51.220> have<00:03:51.430> promised<00:04:15.120> Ofsted 00:04:16.110 --> 00:04:16.120 align:start position:0% these checks will have promised Ofsted 00:04:16.120 --> 00:04:17.909 align:start position:0% these checks will have promised Ofsted you<00:04:16.720> know<00:04:16.810> he<00:04:16.930> has<00:04:17.019> those<00:04:17.229> variables<00:04:17.739> and 00:04:17.909 --> 00:04:17.919 align:start position:0% you know he has those variables and 00:04:17.919 --> 00:04:22.940 align:start position:0% you know he has those variables and these<00:04:18.790> are<00:04:19.320> rather<00:04:20.320> direct<00:04:20.890> translation<00:04:21.430> from 00:04:22.940 --> 00:04:22.950 align:start position:0% these are rather direct translation from 00:04:22.950 --> 00:04:26.610 align:start position:0% these are rather direct translation from variables<00:04:23.950> to<00:04:24.340> a<00:04:24.460> state<00:04:24.820> machine<00:04:25.410> but<00:04:26.410> in 00:04:26.610 --> 00:04:26.620 align:start position:0% variables to a state machine but in 00:04:26.620 --> 00:04:27.930 align:start position:0% variables to a state machine but in general<00:04:26.919> you<00:04:27.070> have<00:04:27.100> to<00:04:27.400> worry<00:04:27.760> about 00:04:27.930 --> 00:04:27.940 align:start position:0% general you have to worry about 00:04:27.940 --> 00:04:33.120 align:start position:0% general you have to worry about mystically<00:04:28.540> also<00:04:30.270> there<00:04:31.270> is<00:04:31.740> one<00:04:32.740> of<00:04:32.830> the<00:04:32.919> most 00:04:33.120 --> 00:04:33.130 align:start position:0% mystically also there is one of the most 00:04:33.130 --> 00:04:35.820 align:start position:0% mystically also there is one of the most complex<00:04:33.630> parts<00:04:34.630> in<00:04:34.870> the<00:04:35.200> celebrity<00:04:35.650> culture 00:04:35.820 --> 00:04:35.830 align:start position:0% complex parts in the celebrity culture 00:04:35.830 --> 00:04:39.060 align:start position:0% complex parts in the celebrity culture it<00:04:36.160> is<00:04:36.780> false<00:04:37.780> because<00:04:38.050> the<00:04:38.380> product<00:04:38.740> foot<00:04:38.890> has 00:04:39.060 --> 00:04:39.070 align:start position:0% it is false because the product foot has 00:04:39.070 --> 00:04:44.100 align:start position:0% it is false because the product foot has so<00:04:39.280> many<00:04:39.450> parameters<00:04:40.450> and<00:04:42.600> it<00:04:43.600> also<00:04:43.750> depends 00:04:44.100 --> 00:04:44.110 align:start position:0% so many parameters and it also depends 00:04:44.110 --> 00:04:46.140 align:start position:0% so many parameters and it also depends whether<00:04:44.290> one<00:04:44.530> whether<00:04:44.919> you<00:04:45.160> want<00:04:45.490> ivory<00:04:45.700> or<00:04:46.120> a 00:04:46.140 --> 00:04:46.150 align:start position:0% whether one whether you want ivory or a 00:04:46.150 --> 00:04:48.150 align:start position:0% whether one whether you want ivory or a regular<00:04:46.690> function<00:04:46.900> or<00:04:47.290> whether<00:04:47.590> you<00:04:47.740> specify 00:04:48.150 --> 00:04:48.160 align:start position:0% regular function or whether you specify 00:04:48.160 --> 00:04:50.159 align:start position:0% regular function or whether you specify the<00:04:48.220> gas<00:04:48.460> over<00:04:48.760> they<00:04:49.030> specify<00:04:49.570> the<00:04:49.630> value<00:04:49.990> and 00:04:50.159 --> 00:04:50.169 align:start position:0% the gas over they specify the value and 00:04:50.169 --> 00:04:56.909 align:start position:0% the gas over they specify the value and so<00:04:50.260> on<00:04:50.380> so<00:04:50.950> there<00:04:51.130> is<00:04:53.760> different<00:04:54.760> ways<00:04:54.820> to<00:04:55.919> use 00:04:56.909 --> 00:04:56.919 align:start position:0% so on so there is different ways to use 00:04:56.919 --> 00:04:59.070 align:start position:0% so on so there is different ways to use the<00:04:57.160> follow<00:04:57.400> up<00:04:57.490> code<00:04:57.760> and<00:04:58.000> all<00:04:58.630> the<00:04:58.750> time<00:04:58.930> you 00:04:59.070 --> 00:04:59.080 align:start position:0% the follow up code and all the time you 00:04:59.080 --> 00:05:01.290 align:start position:0% the follow up code and all the time you have<00:04:59.229> to<00:04:59.550> keep<00:05:00.550> track<00:05:00.760> of<00:05:00.820> where<00:05:01.270> everything 00:05:01.290 --> 00:05:01.300 align:start position:0% have to keep track of where everything 00:05:01.300 --> 00:05:03.030 align:start position:0% have to keep track of where everything is<00:05:01.840> on<00:05:02.050> the<00:05:02.200> stack<00:05:02.440> in<00:05:02.620> the<00:05:02.710> old<00:05:02.830> code 00:05:03.030 --> 00:05:03.040 align:start position:0% is on the stack in the old code 00:05:03.040 --> 00:05:05.030 align:start position:0% is on the stack in the old code generator<00:05:03.370> and<00:05:03.700> if<00:05:04.030> you<00:05:04.150> consider<00:05:04.570> it<00:05:04.690> just 00:05:05.030 --> 00:05:05.040 align:start position:0% generator and if you consider it just 00:05:05.040 --> 00:05:07.350 align:start position:0% generator and if you consider it just reference<00:05:06.040> stuff<00:05:06.310> by<00:05:06.610> their<00:05:06.910> names 00:05:07.350 --> 00:05:07.360 align:start position:0% reference stuff by their names 00:05:07.360 --> 00:05:14.970 align:start position:0% reference stuff by their names it's<00:05:08.050> just<00:05:08.349> yes<00:05:09.270> and 00:05:14.970 --> 00:05:14.980 align:start position:0% 00:05:14.980 --> 00:05:19.170 align:start position:0% another<00:05:15.670> thing<00:05:15.940> is<00:05:16.240> that<00:05:17.190> so<00:05:18.190> when<00:05:18.670> the<00:05:18.880> Opel 00:05:19.170 --> 00:05:19.180 align:start position:0% another thing is that so when the Opel 00:05:19.180 --> 00:05:22.140 align:start position:0% another thing is that so when the Opel generator<00:05:19.620> we<00:05:20.620> forgot<00:05:21.070> to<00:05:21.100> the<00:05:21.370> world<00:05:21.610> did<00:05:22.120> not 00:05:22.140 --> 00:05:22.150 align:start position:0% generator we forgot to the world did not 00:05:22.150 --> 00:05:24.990 align:start position:0% generator we forgot to the world did not yet<00:05:22.480> implement<00:05:22.960> a<00:05:23.170> certain<00:05:23.440> feature<00:05:23.710> but<00:05:24.520> by 00:05:24.990 --> 00:05:25.000 align:start position:0% yet implement a certain feature but by 00:05:25.000 --> 00:05:27.150 align:start position:0% yet implement a certain feature but by accident<00:05:25.210> the<00:05:25.840> stacked<00:05:26.080> layout<00:05:26.350> is<00:05:26.710> correct 00:05:27.150 --> 00:05:27.160 align:start position:0% accident the stacked layout is correct 00:05:27.160 --> 00:05:29.460 align:start position:0% accident the stacked layout is correct then<00:05:27.460> this<00:05:27.820> will<00:05:28.060> need<00:05:28.210> to<00:05:28.450> code<00:05:29.110> that<00:05:29.350> will 00:05:29.460 --> 00:05:29.470 align:start position:0% then this will need to code that will 00:05:29.470 --> 00:05:31.170 align:start position:0% then this will need to code that will actually<00:05:29.770> generate<00:05:29.860> it<00:05:30.250> and<00:05:30.430> will<00:05:30.910> of<00:05:31.030> course 00:05:31.170 --> 00:05:31.180 align:start position:0% actually generate it and will of course 00:05:31.180 --> 00:05:34.140 align:start position:0% actually generate it and will of course do<00:05:31.450> something<00:05:31.840> about<00:05:31.930> it<00:05:32.200> in<00:05:32.860> the<00:05:33.160> new<00:05:33.310> code 00:05:34.140 --> 00:05:34.150 align:start position:0% do something about it in the new code 00:05:34.150 --> 00:05:36.750 align:start position:0% do something about it in the new code generator<00:05:34.890> some<00:05:35.890> expressions<00:05:36.370> are<00:05:36.490> always 00:05:36.750 --> 00:05:36.760 align:start position:0% generator some expressions are always 00:05:36.760 --> 00:05:39.650 align:start position:0% generator some expressions are always referenced<00:05:37.240> by<00:05:37.510> their<00:05:37.750> identifier<00:05:38.290> and<00:05:38.560> a 00:05:39.650 --> 00:05:39.660 align:start position:0% referenced by their identifier and a 00:05:39.660 --> 00:05:42.390 align:start position:0% referenced by their identifier and a full<00:05:40.660> generation<00:05:41.080> of<00:05:41.350> that<00:05:41.560> sub<00:05:41.980> expressions 00:05:42.390 --> 00:05:42.400 align:start position:0% full generation of that sub expressions 00:05:42.400 --> 00:05:43.800 align:start position:0% full generation of that sub expressions are<00:05:42.490> implemented<00:05:43.000> then<00:05:43.150> the<00:05:43.330> identifier 00:05:43.800 --> 00:05:43.810 align:start position:0% are implemented then the identifier 00:05:43.810 --> 00:05:45.750 align:start position:0% are implemented then the identifier logistics<00:05:44.500> is<00:05:44.650> in<00:05:44.860> the<00:05:45.010> universe<00:05:45.460> an 00:05:45.750 --> 00:05:45.760 align:start position:0% logistics is in the universe an 00:05:45.760 --> 00:05:48.330 align:start position:0% logistics is in the universe an additional<00:05:46.720> level<00:05:47.620> of<00:05:47.680> checks<00:05:47.980> on<00:05:48.250> the 00:05:48.330 --> 00:05:48.340 align:start position:0% additional level of checks on the 00:05:48.340 --> 00:05:50.360 align:start position:0% additional level of checks on the intermediate<00:05:48.760> language<00:05:48.880> and<00:05:49.360> this<00:05:49.840> will<00:05:50.020> be 00:05:50.360 --> 00:05:50.370 align:start position:0% intermediate language and this will be 00:05:50.370 --> 00:05:57.740 align:start position:0% intermediate language and this will be detected<00:05:51.370> and<00:05:55.140> how<00:05:56.140> can<00:05:56.200> you<00:05:56.410> actually<00:05:56.590> use<00:05:56.800> it 00:05:57.740 --> 00:05:57.750 align:start position:0% detected and how can you actually use it 00:05:57.750 --> 00:06:00.030 align:start position:0% detected and how can you actually use it I'm<00:05:58.750> going<00:05:58.930> to<00:05:58.960> show<00:05:59.200> you<00:05:59.230> how<00:05:59.500> to<00:05:59.560> use<00:05:59.800> it<00:05:59.920> on 00:06:00.030 --> 00:06:00.040 align:start position:0% I'm going to show you how to use it on 00:06:00.040 --> 00:06:02.540 align:start position:0% I'm going to show you how to use it on the<00:06:00.130> command<00:06:00.430> line<00:06:00.490> the<00:06:00.880> standard<00:06:01.480> Chasen 00:06:02.540 --> 00:06:02.550 align:start position:0% the command line the standard Chasen 00:06:02.550 --> 00:06:05.790 align:start position:0% the command line the standard Chasen also<00:06:03.550> works 00:06:05.790 --> 00:06:05.800 align:start position:0% also works 00:06:05.800 --> 00:06:11.670 align:start position:0% so<00:06:07.440> -<00:06:08.440> my<00:06:08.620> art<00:06:08.860> will<00:06:09.789> generate<00:06:10.539> you<00:06:10.720> vote<00:06:11.080> from 00:06:11.670 --> 00:06:11.680 align:start position:0% so - my art will generate you vote from 00:06:11.680 --> 00:06:16.830 align:start position:0% so - my art will generate you vote from facility<00:06:12.310> code<00:06:12.520> and<00:06:14.340> for<00:06:15.340> safety<00:06:16.030> reason<00:06:16.479> we 00:06:16.830 --> 00:06:16.840 align:start position:0% facility code and for safety reason we 00:06:16.840 --> 00:06:19.369 align:start position:0% facility code and for safety reason we do<00:06:17.050> not<00:06:17.229> support<00:06:17.590> a<00:06:17.979> direct<00:06:18.460> translation<00:06:18.729> from 00:06:19.369 --> 00:06:19.379 align:start position:0% do not support a direct translation from 00:06:19.379 --> 00:06:22.710 align:start position:0% do not support a direct translation from civility<00:06:20.379> through<00:06:20.800> you'll<00:06:21.009> TBM<00:06:21.729> because<00:06:22.539> it's 00:06:22.710 --> 00:06:22.720 align:start position:0% civility through you'll TBM because it's 00:06:22.720 --> 00:06:26.520 align:start position:0% civility through you'll TBM because it's only<00:06:22.900> an<00:06:23.199> experimental<00:06:23.710> stage<00:06:25.199> so<00:06:26.199> you<00:06:26.259> have 00:06:26.520 --> 00:06:26.530 align:start position:0% only an experimental stage so you have 00:06:26.530 --> 00:06:30.270 align:start position:0% only an experimental stage so you have to<00:06:27.030> yeah<00:06:28.060> copy<00:06:28.870> the<00:06:29.139> ultimate<00:06:29.560> on<00:06:29.770> the<00:06:30.009> first 00:06:30.270 --> 00:06:30.280 align:start position:0% to yeah copy the ultimate on the first 00:06:30.280 --> 00:06:33.869 align:start position:0% to yeah copy the ultimate on the first stage<00:06:30.729> and<00:06:31.060> then<00:06:31.330> rerun<00:06:32.080> the<00:06:32.879> sudanese 00:06:33.869 --> 00:06:33.879 align:start position:0% stage and then rerun the sudanese 00:06:33.879 --> 00:06:35.909 align:start position:0% stage and then rerun the sudanese compiler<00:06:34.270> in<00:06:34.509> assembly<00:06:34.960> mode<00:06:35.139> and<00:06:35.440> then 00:06:35.909 --> 00:06:35.919 align:start position:0% compiler in assembly mode and then 00:06:35.919 --> 00:06:41.909 align:start position:0% compiler in assembly mode and then transform<00:06:36.909> the<00:06:37.120> video<00:06:37.389> recorder<00:06:37.900> -<00:06:40.919> yeah 00:06:41.909 --> 00:06:41.919 align:start position:0% transform the video recorder - yeah 00:06:41.919 --> 00:06:47.100 align:start position:0% transform the video recorder - yeah that's<00:06:42.099> a<00:06:42.190> gonna<00:06:42.370> get<00:06:42.610> how<00:06:43.419> that<00:06:45.990> looks<00:06:46.990> in 00:06:47.100 --> 00:06:47.110 align:start position:0% that's a gonna get how that looks in 00:06:47.110 --> 00:06:49.140 align:start position:0% that's a gonna get how that looks in practice<00:06:47.349> so<00:06:47.710> this<00:06:47.860> is<00:06:47.919> an<00:06:48.370> example<00:06:48.699> years<00:06:48.970> and 00:06:49.140 --> 00:06:49.150 align:start position:0% practice so this is an example years and 00:06:49.150 --> 00:06:52.649 align:start position:0% practice so this is an example years and 20<00:06:49.449> content<00:06:50.020> already<00:06:50.259> a<00:06:50.470> hard<00:06:51.099> early<00:06:51.539> years<00:06:52.539> in 00:06:52.649 --> 00:06:52.659 align:start position:0% 20 content already a hard early years in 00:06:52.659 --> 00:06:56.490 align:start position:0% 20 content already a hard early years in 20<00:06:52.930> contract<00:06:53.729> we<00:06:54.729> have<00:06:54.759> an<00:06:54.970> event<00:06:55.240> we<00:06:56.110> have<00:06:56.289> the 00:06:56.490 --> 00:06:56.500 align:start position:0% 20 contract we have an event we have the 00:06:56.500 --> 00:07:01.350 align:start position:0% 20 contract we have an event we have the mapping<00:06:56.800> of<00:06:56.889> the<00:06:56.949> balances<00:06:57.490> to<00:06:58.330> supply<00:06:59.460> a<00:07:00.460> mint 00:07:01.350 --> 00:07:01.360 align:start position:0% mapping of the balances to supply a mint 00:07:01.360 --> 00:07:03.510 align:start position:0% mapping of the balances to supply a mint function<00:07:01.840> that<00:07:01.990> generates<00:07:02.259> tokens<00:07:03.009> which<00:07:03.370> is 00:07:03.510 --> 00:07:03.520 align:start position:0% function that generates tokens which is 00:07:03.520 --> 00:07:04.920 align:start position:0% function that generates tokens which is conscious<00:07:03.909> which<00:07:04.300> is<00:07:04.449> called<00:07:04.690> in<00:07:04.840> the 00:07:04.920 --> 00:07:04.930 align:start position:0% conscious which is called in the 00:07:04.930 --> 00:07:08.809 align:start position:0% conscious which is called in the instructor<00:07:05.379> so<00:07:05.590> center<00:07:06.099> gets<00:07:06.849> 20<00:07:07.360> points<00:07:07.719> and 00:07:08.809 --> 00:07:08.819 align:start position:0% instructor so center gets 20 points and 00:07:08.819 --> 00:07:11.129 align:start position:0% instructor so center gets 20 points and the<00:07:09.819> mid<00:07:10.000> function 00:07:11.129 --> 00:07:11.139 align:start position:0% the mid function 00:07:11.139 --> 00:07:16.260 align:start position:0% the mid function this<00:07:11.580> required<00:07:12.580> also<00:07:14.490> Everest<00:07:15.490> mint<00:07:15.939> to 00:07:16.260 --> 00:07:16.270 align:start position:0% this required also Everest mint to 00:07:16.270 --> 00:07:19.020 align:start position:0% this required also Everest mint to cannot<00:07:16.960> be<00:07:17.080> the<00:07:17.199> similarities<00:07:17.770> and<00:07:18.310> then 00:07:19.020 --> 00:07:19.030 align:start position:0% cannot be the similarities and then 00:07:19.030 --> 00:07:23.149 align:start position:0% cannot be the similarities and then towards<00:07:19.360> my<00:07:19.599> analysis<00:07:20.050> is<00:07:20.259> modified<00:07:20.770> and<00:07:21.009> the 00:07:23.149 --> 00:07:23.159 align:start position:0% towards my analysis is modified and the 00:07:23.159 --> 00:07:30.119 align:start position:0% towards my analysis is modified and the transfer<00:07:24.330> event<00:07:26.819> now<00:07:27.819> we<00:07:28.779> compile<00:07:29.289> that<00:07:29.319> to 00:07:30.119 --> 00:07:30.129 align:start position:0% transfer event now we compile that to 00:07:30.129 --> 00:07:33.749 align:start position:0% transfer event now we compile that to unity<00:07:30.490> and<00:07:30.960> so<00:07:31.960> this<00:07:32.139> is<00:07:32.289> not<00:07:32.469> the<00:07:32.770> quote 00:07:33.749 --> 00:07:33.759 align:start position:0% unity and so this is not the quote 00:07:33.759 --> 00:07:35.790 align:start position:0% unity and so this is not the quote directly<00:07:34.689> generated<00:07:35.110> particle<00:07:35.529> generator 00:07:35.790 --> 00:07:35.800 align:start position:0% directly generated particle generator 00:07:35.800 --> 00:07:39.529 align:start position:0% directly generated particle generator but<00:07:35.949> this<00:07:36.069> is<00:07:36.189> the<00:07:36.340> code<00:07:36.520> after<00:07:36.999> optimization 00:07:39.529 --> 00:07:39.539 align:start position:0% 00:07:39.539 --> 00:07:41.850 align:start position:0% I<00:07:40.539> think<00:07:41.020> it's<00:07:41.110> really<00:07:41.199> nice<00:07:41.379> that<00:07:41.439> this<00:07:41.710> is 00:07:41.850 --> 00:07:41.860 align:start position:0% I think it's really nice that this is 00:07:41.860 --> 00:07:50.700 align:start position:0% I think it's really nice that this is still<00:07:43.020> nice<00:07:45.750> detail<00:07:46.750> and<00:07:47.710> you<00:07:47.800> will<00:07:47.919> see<00:07:49.710> but 00:07:50.700 --> 00:07:50.710 align:start position:0% still nice detail and you will see but 00:07:50.710 --> 00:07:53.820 align:start position:0% still nice detail and you will see but you<00:07:51.580> see<00:07:51.759> that<00:07:51.909> it<00:07:52.029> still<00:07:52.240> have<00:07:52.830> expressions 00:07:53.820 --> 00:07:53.830 align:start position:0% you see that it still have expressions 00:07:53.830 --> 00:07:59.999 align:start position:0% you see that it still have expressions and<00:07:57.000> yeah<00:07:58.000> it<00:07:58.240> so<00:07:58.539> you<00:07:59.199> would<00:07:59.379> even<00:07:59.650> see<00:07:59.830> the 00:07:59.999 --> 00:08:00.009 align:start position:0% and yeah it so you would even see the 00:08:00.009 --> 00:08:01.920 align:start position:0% and yeah it so you would even see the mid<00:08:00.219> function<00:08:00.490> call<00:08:00.939> here<00:08:00.969> and<00:08:01.569> he<00:08:01.779> was 00:08:01.920 --> 00:08:01.930 align:start position:0% mid function call here and he was 00:08:01.930 --> 00:08:05.429 align:start position:0% mid function call here and he was recognized<00:08:02.560> the<00:08:03.039> name<00:08:03.250> mint<00:08:03.610> the<00:08:04.330> the<00:08:05.289> issue 00:08:05.429 --> 00:08:05.439 align:start position:0% recognized the name mint the the issue 00:08:05.439 --> 00:08:09.629 align:start position:0% recognized the name mint the the issue here<00:08:05.740> is<00:08:05.830> just<00:08:06.069> that<00:08:06.189> the<00:08:07.050> mint<00:08:08.400> function<00:08:09.400> in 00:08:09.629 --> 00:08:09.639 align:start position:0% here is just that the mint function in 00:08:09.639 --> 00:08:12.420 align:start position:0% here is just that the mint function in the<00:08:09.939> init<00:08:10.419> context<00:08:11.050> is<00:08:11.199> only<00:08:11.499> called<00:08:11.889> once<00:08:12.129> and 00:08:12.420 --> 00:08:12.430 align:start position:0% the init context is only called once and 00:08:12.430 --> 00:08:14.820 align:start position:0% the init context is only called once and because<00:08:12.759> of<00:08:12.789> that<00:08:12.909> is<00:08:13.210> first<00:08:13.569> in<00:08:13.719> line<00:08:13.960> and<00:08:14.199> so 00:08:14.820 --> 00:08:14.830 align:start position:0% because of that is first in line and so 00:08:14.830 --> 00:08:18.659 align:start position:0% because of that is first in line and so the<00:08:14.949> function<00:08:15.279> eternal<00:08:15.779> but<00:08:16.779> we<00:08:17.409> so<00:08:17.800> it<00:08:18.310> starts 00:08:18.659 --> 00:08:18.669 align:start position:0% the function eternal but we so it starts 00:08:18.669 --> 00:08:21.300 align:start position:0% the function eternal but we so it starts with<00:08:19.349> initializing<00:08:20.349> the<00:08:20.500> memory<00:08:20.919> allocator 00:08:21.300 --> 00:08:21.310 align:start position:0% with initializing the memory allocator 00:08:21.310 --> 00:08:25.720 align:start position:0% with initializing the memory allocator then<00:08:22.270> we<00:08:22.810> have<00:08:22.930> the<00:08:23.050> core<00:08:23.229> value<00:08:23.529> checks 00:08:25.720 --> 00:08:25.730 align:start position:0% then we have the core value checks 00:08:25.730 --> 00:08:30.270 align:start position:0% then we have the core value checks people<00:08:26.590> and<00:08:27.590> then<00:08:27.740> the<00:08:28.310> second<00:08:28.610> thing<00:08:28.730> here<00:08:29.000> is 00:08:30.270 --> 00:08:30.280 align:start position:0% people and then the second thing here is 00:08:30.280 --> 00:08:32.980 align:start position:0% people and then the second thing here is required<00:08:31.280> that<00:08:31.430> the<00:08:31.610> and<00:08:32.210> as<00:08:32.540> we<00:08:32.660> meant<00:08:32.840> to 00:08:32.980 --> 00:08:32.990 align:start position:0% required that the and as we meant to 00:08:32.990 --> 00:08:38.230 align:start position:0% required that the and as we meant to it's<00:08:33.230> not<00:08:33.380> zero<00:08:35.350> you<00:08:36.350> actually<00:08:36.710> see<00:08:36.919> the<00:08:37.240> error 00:08:38.230 --> 00:08:38.240 align:start position:0% it's not zero you actually see the error 00:08:38.240 --> 00:08:43.600 align:start position:0% it's not zero you actually see the error string<00:08:38.660> here<00:08:41.590> here's<00:08:42.590> 20<00:08:43.040> in<00:08:43.160> minute<00:08:43.400> to<00:08:43.490> the 00:08:43.600 --> 00:08:43.610 align:start position:0% string here here's 20 in minute to the 00:08:43.610 --> 00:08:47.470 align:start position:0% string here here's 20 in minute to the zero<00:08:43.790> edges<00:08:44.470> so<00:08:45.470> this<00:08:45.650> this<00:08:46.580> block<00:08:46.850> here<00:08:47.210> is 00:08:47.470 --> 00:08:47.480 align:start position:0% zero edges so this this block here is 00:08:47.480 --> 00:08:51.130 align:start position:0% zero edges so this this block here is the<00:08:47.780> require<00:08:48.080> home<00:08:48.410> and<00:08:48.700> then<00:08:49.780> we<00:08:50.780> update<00:08:50.900> the 00:08:51.130 --> 00:08:51.140 align:start position:0% the require home and then we update the 00:08:51.140 --> 00:08:53.500 align:start position:0% the require home and then we update the tour<00:08:51.410> so<00:08:51.590> this<00:08:52.190> this<00:08:52.490> is<00:08:52.640> this<00:08:52.970> is<00:08:53.030> a<00:08:53.150> common<00:08:53.420> I 00:08:53.500 --> 00:08:53.510 align:start position:0% tour so this this is this is a common I 00:08:53.510 --> 00:08:59.080 align:start position:0% tour so this this is this is a common I am<00:08:53.630> menu<00:08:55.450> yeah<00:08:56.450> you<00:08:57.160> take<00:08:58.160> the<00:08:58.190> stuff<00:08:58.640> that<00:08:58.910> is 00:08:59.080 --> 00:08:59.090 align:start position:0% am menu yeah you take the stuff that is 00:08:59.090 --> 00:09:00.990 align:start position:0% am menu yeah you take the stuff that is take<00:08:59.510> the<00:08:59.600> day<00:08:59.720> that<00:08:59.900> is<00:09:00.020> currently<00:09:00.830> at 00:09:00.990 --> 00:09:01.000 align:start position:0% take the day that is currently at 00:09:01.000 --> 00:09:06.670 align:start position:0% take the day that is currently at storage<00:09:02.000> vacation<00:09:02.420> you<00:09:03.230> have<00:09:03.260> 29<00:09:04.010> useful<00:09:05.680> now 00:09:06.670 --> 00:09:06.680 align:start position:0% storage vacation you have 29 useful now 00:09:06.680 --> 00:09:11.170 align:start position:0% storage vacation you have 29 useful now it<00:09:07.640> it<00:09:08.360> calls<00:09:08.720> for<00:09:09.610> the<00:09:10.610> user-defined 00:09:11.170 --> 00:09:11.180 align:start position:0% it it calls for the user-defined 00:09:11.180 --> 00:09:13.150 align:start position:0% it it calls for the user-defined function<00:09:11.540> called<00:09:11.720> check<00:09:11.780> add<00:09:12.170> this<00:09:12.830> is<00:09:12.980> the 00:09:13.150 --> 00:09:13.160 align:start position:0% function called check add this is the 00:09:13.160 --> 00:09:14.500 align:start position:0% function called check add this is the the<00:09:13.460> overflow<00:09:13.790> check<00:09:14.000> I<00:09:14.030> was<00:09:14.180> talking<00:09:14.480> about 00:09:14.500 --> 00:09:14.510 align:start position:0% the overflow check I was talking about 00:09:14.510 --> 00:09:18.010 align:start position:0% the overflow check I was talking about earlier<00:09:14.780> and<00:09:16.180> that<00:09:17.180> is<00:09:17.330> one<00:09:17.600> of<00:09:17.630> the<00:09:17.840> two 00:09:18.010 --> 00:09:18.020 align:start position:0% earlier and that is one of the two 00:09:18.020 --> 00:09:20.260 align:start position:0% earlier and that is one of the two functions<00:09:18.500> that's<00:09:18.650> not<00:09:19.010> visible<00:09:19.460> on<00:09:19.880> the 00:09:20.260 --> 00:09:20.270 align:start position:0% functions that's not visible on the 00:09:20.270 --> 00:09:22.420 align:start position:0% functions that's not visible on the screen<00:09:20.450> here<00:09:20.930> and<00:09:21.140> the<00:09:21.500> rest<00:09:21.650> of<00:09:21.860> the<00:09:22.190> rest<00:09:22.370> of 00:09:22.420 --> 00:09:22.430 align:start position:0% screen here and the rest of the rest of 00:09:22.430 --> 00:09:24.760 align:start position:0% screen here and the rest of the rest of the<00:09:22.550> coast<00:09:22.760> all<00:09:22.970> the<00:09:23.080> all<00:09:24.080> there<00:09:24.350> is<00:09:24.530> to<00:09:24.680> the 00:09:24.760 --> 00:09:24.770 align:start position:0% the coast all the all there is to the 00:09:24.770 --> 00:09:27.880 align:start position:0% the coast all the all there is to the instructors<00:09:25.390> instructor<00:09:26.390> called<00:09:26.570> missing<00:09:27.320> to 00:09:27.880 --> 00:09:27.890 align:start position:0% instructors instructor called missing to 00:09:27.890 --> 00:09:30.850 align:start position:0% instructors instructor called missing to school<00:09:28.160> functions<00:09:28.570> and<00:09:29.570> now<00:09:29.840> we<00:09:30.470> update<00:09:30.740> the 00:09:30.850 --> 00:09:30.860 align:start position:0% school functions and now we update the 00:09:30.860 --> 00:09:33.310 align:start position:0% school functions and now we update the balances<00:09:31.310> this<00:09:32.270> is<00:09:32.390> the<00:09:32.540> kind<00:09:32.990> of<00:09:33.110> problem 00:09:33.310 --> 00:09:33.320 align:start position:0% balances this is the kind of problem 00:09:33.320 --> 00:09:35.369 align:start position:0% balances this is the kind of problem there<00:09:34.160> is<00:09:34.310> a<00:09:34.340> function 00:09:35.369 --> 00:09:35.379 align:start position:0% there is a function 00:09:35.379 --> 00:09:37.979 align:start position:0% there is a function access<00:09:35.889> team<00:09:36.129> mapping<00:09:36.549> and<00:09:36.789> so<00:09:37.359> on<00:09:37.419> it's<00:09:37.869> a 00:09:37.979 --> 00:09:37.989 align:start position:0% access team mapping and so on it's a 00:09:37.989 --> 00:09:41.400 align:start position:0% access team mapping and so on it's a little<00:09:38.319> bit<00:09:38.410> longer<00:09:38.619> so<00:09:40.019> the<00:09:41.019> reason<00:09:41.289> is<00:09:41.379> that 00:09:41.400 --> 00:09:41.410 align:start position:0% little bit longer so the reason is that 00:09:41.410 --> 00:09:43.859 align:start position:0% little bit longer so the reason is that so<00:09:41.799> this<00:09:41.919> is<00:09:41.979> the<00:09:42.160> the<00:09:42.639> in<00:09:42.759> x-axis<00:09:43.269> helper 00:09:43.859 --> 00:09:43.869 align:start position:0% so this is the the in x-axis helper 00:09:43.869 --> 00:09:46.469 align:start position:0% so this is the the in x-axis helper function<00:09:44.259> for<00:09:44.589> storage<00:09:45.099> mappings<00:09:45.489> and<00:09:45.669> the 00:09:46.469 --> 00:09:46.479 align:start position:0% function for storage mappings and the 00:09:46.479 --> 00:09:48.389 align:start position:0% function for storage mappings and the name<00:09:46.689> is<00:09:46.869> generated<00:09:47.319> from<00:09:47.470> the<00:09:47.679> type<00:09:47.889> and<00:09:48.160> I 00:09:48.389 --> 00:09:48.399 align:start position:0% name is generated from the type and I 00:09:48.399 --> 00:09:49.979 align:start position:0% name is generated from the type and I think<00:09:48.639> we<00:09:48.939> still<00:09:49.329> have<00:09:49.419> to<00:09:49.539> come<00:09:49.779> up<00:09:49.809> with<00:09:49.869> a 00:09:49.979 --> 00:09:49.989 align:start position:0% think we still have to come up with a 00:09:49.989 --> 00:09:54.239 align:start position:0% think we still have to come up with a way<00:09:50.109> to<00:09:50.139> shorten<00:09:50.529> it<00:09:50.649> so<00:09:50.769> it's<00:09:50.919> very<00:09:51.039> cool<00:09:53.249> yeah 00:09:54.239 --> 00:09:54.249 align:start position:0% way to shorten it so it's very cool yeah 00:09:54.249 --> 00:09:57.629 align:start position:0% way to shorten it so it's very cool yeah and<00:09:54.429> another<00:09:54.639> issue<00:09:54.909> here<00:09:55.389> is<00:09:56.279> you<00:09:57.279> see<00:09:57.489> that 00:09:57.629 --> 00:09:57.639 align:start position:0% and another issue here is you see that 00:09:57.639 --> 00:09:59.819 align:start position:0% and another issue here is you see that not<00:09:57.970> even<00:09:58.119> a<00:09:58.329> success<00:09:58.720> the<00:09:59.199> function<00:09:59.529> was<00:09:59.649> just 00:09:59.819 --> 00:09:59.829 align:start position:0% not even a success the function was just 00:09:59.829 --> 00:10:01.679 align:start position:0% not even a success the function was just talking<00:10:00.069> about<00:10:00.189> it's<00:10:00.729> called<00:10:00.789> here<00:10:01.209> and<00:10:01.419> it's 00:10:01.679 --> 00:10:01.689 align:start position:0% talking about it's called here and it's 00:10:01.689 --> 00:10:04.079 align:start position:0% talking about it's called here and it's also<00:10:01.869> called<00:10:02.259> here<00:10:02.649> again<00:10:03.099> with<00:10:03.699> the<00:10:03.849> same 00:10:04.079 --> 00:10:04.089 align:start position:0% also called here again with the same 00:10:04.089 --> 00:10:07.409 align:start position:0% also called here again with the same parameters<00:10:05.129> usually<00:10:06.129> the<00:10:06.339> optimizer<00:10:06.819> is<00:10:06.970> able 00:10:07.409 --> 00:10:07.419 align:start position:0% parameters usually the optimizer is able 00:10:07.419 --> 00:10:09.359 align:start position:0% parameters usually the optimizer is able to<00:10:07.539> combine<00:10:07.929> them<00:10:08.229> and<00:10:08.379> call<00:10:08.619> it<00:10:08.709> only<00:10:08.829> once 00:10:09.359 --> 00:10:09.369 align:start position:0% to combine them and call it only once 00:10:09.369 --> 00:10:13.319 align:start position:0% to combine them and call it only once the<00:10:09.789> problem<00:10:10.119> here<00:10:10.329> is<00:10:10.539> that<00:10:11.879> it<00:10:12.879> calls<00:10:13.149> the 00:10:13.319 --> 00:10:13.329 align:start position:0% the problem here is that it calls the 00:10:13.329 --> 00:10:16.109 align:start position:0% the problem here is that it calls the Kaptchuk<00:10:13.629> function<00:10:14.079> which<00:10:14.499> works<00:10:15.489> on<00:10:15.729> memory 00:10:16.109 --> 00:10:16.119 align:start position:0% Kaptchuk function which works on memory 00:10:16.119 --> 00:10:18.089 align:start position:0% Kaptchuk function which works on memory because<00:10:16.989> of<00:10:17.139> that<00:10:17.259> it<00:10:17.409> has<00:10:17.439> to<00:10:17.769> access<00:10:17.919> the 00:10:18.089 --> 00:10:18.099 align:start position:0% because of that it has to access the 00:10:18.099 --> 00:10:23.849 align:start position:0% because of that it has to access the memory<00:10:18.399> and<00:10:21.599> the<00:10:22.599> optimizer<00:10:23.019> cannot<00:10:23.589> yet 00:10:23.849 --> 00:10:23.859 align:start position:0% memory and the optimizer cannot yet 00:10:23.859 --> 00:10:28.379 align:start position:0% memory and the optimizer cannot yet recognize<00:10:24.519> that<00:10:25.769> writing<00:10:26.769> this<00:10:27.279> stuff<00:10:27.669> so 00:10:28.379 --> 00:10:28.389 align:start position:0% recognize that writing this stuff so 00:10:28.389 --> 00:10:30.299 align:start position:0% recognize that writing this stuff so that<00:10:28.419> the<00:10:29.349> stuff<00:10:29.589> that<00:10:29.769> is<00:10:29.859> written<00:10:30.039> in<00:10:30.220> the 00:10:30.299 --> 00:10:30.309 align:start position:0% that the stuff that is written in the 00:10:30.309 --> 00:10:31.829 align:start position:0% that the stuff that is written in the first<00:10:30.519> call<00:10:30.849> and<00:10:31.179> the<00:10:31.359> stuff<00:10:31.599> that<00:10:31.749> was 00:10:31.829 --> 00:10:31.839 align:start position:0% first call and the stuff that was 00:10:31.839 --> 00:10:33.389 align:start position:0% first call and the stuff that was written<00:10:31.929> said<00:10:32.319> Paul<00:10:32.619> did<00:10:32.829> no<00:10:32.979> conflict 00:10:33.389 --> 00:10:33.399 align:start position:0% written said Paul did no conflict 00:10:33.399 --> 00:10:35.399 align:start position:0% written said Paul did no conflict because<00:10:33.639> it<00:10:33.759> exactly<00:10:34.059> the<00:10:34.179> same<00:10:34.259> so<00:10:35.259> they 00:10:35.399 --> 00:10:35.409 align:start position:0% because it exactly the same so they 00:10:35.409 --> 00:10:36.179 align:start position:0% because it exactly the same so they write<00:10:35.529> to<00:10:35.589> the<00:10:35.769> same<00:10:35.799> memory<00:10:36.159> location 00:10:36.179 --> 00:10:36.189 align:start position:0% write to the same memory location 00:10:36.189 --> 00:10:39.719 align:start position:0% write to the same memory location because<00:10:36.849> of<00:10:36.939> that<00:10:37.089> it<00:10:37.359> can't<00:10:37.629> really<00:10:38.729> swap 00:10:39.719 --> 00:10:39.729 align:start position:0% because of that it can't really swap 00:10:39.729 --> 00:10:42.569 align:start position:0% because of that it can't really swap them<00:10:39.970> but<00:10:40.659> it<00:10:41.529> should<00:10:41.769> detect<00:10:42.069> that<00:10:42.339> it's 00:10:42.569 --> 00:10:42.579 align:start position:0% them but it should detect that it's 00:10:42.579 --> 00:10:49.979 align:start position:0% them but it should detect that it's actually<00:10:42.879> the<00:10:42.970> same<00:10:43.329> step<00:10:43.689> this<00:10:43.869> really<00:10:48.989> yeah 00:10:49.979 --> 00:10:49.989 align:start position:0% actually the same step this really yeah 00:10:49.989 --> 00:10:53.579 align:start position:0% actually the same step this really yeah talking<00:10:50.350> about<00:10:50.559> exercise<00:10:51.779> and<00:10:52.779> the<00:10:53.109> truth<00:10:53.379> you 00:10:53.579 --> 00:10:53.589 align:start position:0% talking about exercise and the truth you 00:10:53.589 --> 00:10:55.060 align:start position:0% talking about exercise and the truth you can 00:10:55.060 --> 00:10:55.070 align:start position:0% can 00:10:55.070 --> 00:11:02.590 align:start position:0% can this<00:10:55.790> is<00:10:59.650> 256-bit<00:11:00.650> EVM<00:11:01.460> code<00:11:01.730> and<00:11:02.000> I<00:11:02.390> think 00:11:02.590 --> 00:11:02.600 align:start position:0% this is 256-bit EVM code and I think 00:11:02.600 --> 00:11:05.560 align:start position:0% this is 256-bit EVM code and I think it's<00:11:02.720> also<00:11:02.930> a<00:11:03.110> lot<00:11:03.320> more<00:11:03.910> obviously<00:11:04.910> 20<00:11:05.330> then 00:11:05.560 --> 00:11:05.570 align:start position:0% it's also a lot more obviously 20 then 00:11:05.570 --> 00:11:09.010 align:start position:0% it's also a lot more obviously 20 then it<00:11:05.900> was<00:11:06.260> a<00:11:06.290> big<00:11:07.280> challenge<00:11:07.720> but<00:11:08.720> we<00:11:08.840> can 00:11:09.010 --> 00:11:09.020 align:start position:0% it was a big challenge but we can 00:11:09.020 --> 00:11:11.980 align:start position:0% it was a big challenge but we can prepare<00:11:09.350> the<00:11:10.090> compiler<00:11:11.090> that<00:11:11.270> goes<00:11:11.690> why<00:11:11.930> you 00:11:11.980 --> 00:11:11.990 align:start position:0% prepare the compiler that goes why you 00:11:11.990 --> 00:11:16.870 align:start position:0% prepare the compiler that goes why you will<00:11:12.350> and<00:11:12.500> does<00:11:13.130> not<00:11:13.490> kill<00:11:13.700> why<00:11:13.880> are<00:11:13.940> you<00:11:15.880> so 00:11:16.870 --> 00:11:16.880 align:start position:0% will and does not kill why are you so 00:11:16.880 --> 00:11:20.760 align:start position:0% will and does not kill why are you so there<00:11:17.500> the<00:11:18.500> particle<00:11:18.860> politics 00:11:20.760 --> 00:11:20.770 align:start position:0% there the particle politics 00:11:20.770 --> 00:11:25.330 align:start position:0% there the particle politics 1747<00:11:21.770> bytes<00:11:23.170> that's<00:11:24.170> been<00:11:24.440> unfair<00:11:24.800> because<00:11:25.010> it 00:11:25.330 --> 00:11:25.340 align:start position:0% 1747 bytes that's been unfair because it 00:11:25.340 --> 00:11:27.430 align:start position:0% 1747 bytes that's been unfair because it doesn't<00:11:25.730> alter<00:11:25.850> como<00:11:26.420> flow<00:11:26.600> checks<00:11:26.870> if<00:11:27.110> we<00:11:27.260> add 00:11:27.430 --> 00:11:27.440 align:start position:0% doesn't alter como flow checks if we add 00:11:27.440 --> 00:11:31.480 align:start position:0% doesn't alter como flow checks if we add the<00:11:27.590> objects<00:11:28.220> it's<00:11:28.460> fine<00:11:29.420> and<00:11:30.130> if<00:11:31.130> you<00:11:31.190> do<00:11:31.340> that 00:11:31.480 --> 00:11:31.490 align:start position:0% the objects it's fine and if you do that 00:11:31.490 --> 00:11:33.970 align:start position:0% the objects it's fine and if you do that why<00:11:31.640> it's<00:11:32.620> 2062 00:11:33.970 --> 00:11:33.980 align:start position:0% why it's 2062 00:11:33.980 --> 00:11:36.790 align:start position:0% why it's 2062 so<00:11:34.820> it<00:11:35.120> shows<00:11:35.330> that<00:11:35.360> are<00:11:35.660> still<00:11:35.990> some<00:11:36.590> work<00:11:36.740> to 00:11:36.790 --> 00:11:36.800 align:start position:0% so it shows that are still some work to 00:11:36.800 --> 00:11:39.370 align:start position:0% so it shows that are still some work to do<00:11:37.100> actually<00:11:37.760> I<00:11:37.850> did<00:11:38.480> not<00:11:38.690> you<00:11:38.810> find<00:11:39.050> the<00:11:39.230> time 00:11:39.370 --> 00:11:39.380 align:start position:0% do actually I did not you find the time 00:11:39.380 --> 00:11:42.730 align:start position:0% do actually I did not you find the time to<00:11:39.650> see<00:11:39.830> where<00:11:40.310> it<00:11:40.820> has<00:11:41.300> these<00:11:42.230> additional 00:11:42.730 --> 00:11:42.740 align:start position:0% to see where it has these additional 00:11:42.740 --> 00:11:49.450 align:start position:0% to see where it has these additional bytes<00:11:43.060> so<00:11:44.060> it<00:11:44.180> might<00:11:44.480> be<00:11:44.540> just<00:11:44.690> amenities<00:11:48.430> ok 00:11:49.450 --> 00:11:49.460 align:start position:0% bytes so it might be just amenities ok 00:11:49.460 --> 00:11:53.050 align:start position:0% bytes so it might be just amenities ok webassembly<00:11:51.250> similar<00:11:52.250> to<00:11:52.400> assault<00:11:52.730> see<00:11:52.880> my 00:11:53.050 --> 00:11:53.060 align:start position:0% webassembly similar to assault see my 00:11:53.060 --> 00:11:55.600 align:start position:0% webassembly similar to assault see my expense<00:11:53.390> I<00:11:53.540> already<00:11:54.020> knew<00:11:54.170> SSD<00:11:54.620> -<00:11:54.980> -<00:11:55.250> he<00:11:55.400> wasn't 00:11:55.600 --> 00:11:55.610 align:start position:0% expense I already knew SSD - - he wasn't 00:11:55.610 --> 00:12:00.610 align:start position:0% expense I already knew SSD - - he wasn't it<00:11:56.510> will<00:11:57.020> so<00:11:57.830> and<00:11:58.600> this<00:11:59.600> will<00:12:00.020> actually 00:12:00.610 --> 00:12:00.620 align:start position:0% it will so and this will actually 00:12:00.620 --> 00:12:03.730 align:start position:0% it will so and this will actually generate<00:12:01.720> he<00:12:02.720> wasn't<00:12:03.110> text<00:12:03.350> representation 00:12:03.730 --> 00:12:03.740 align:start position:0% generate he wasn't text representation 00:12:03.740 --> 00:12:09.640 align:start position:0% generate he wasn't text representation in<00:12:04.220> one<00:12:04.430> run<00:12:07.090> thing<00:12:08.090> is<00:12:08.240> it's<00:12:08.480> not<00:12:09.170> tested<00:12:09.560> at 00:12:09.640 --> 00:12:09.650 align:start position:0% in one run thing is it's not tested at 00:12:09.650 --> 00:12:15.310 align:start position:0% in one run thing is it's not tested at all<00:12:12.940> it's<00:12:13.940> not<00:12:14.060> tested<00:12:14.390> you<00:12:14.630> know<00:12:14.690> because<00:12:15.170> we 00:12:15.310 --> 00:12:15.320 align:start position:0% all it's not tested you know because we 00:12:15.320 --> 00:12:20.560 align:start position:0% all it's not tested you know because we couldn't<00:12:15.770> get<00:12:15.950> find<00:12:19.060> execution<00:12:20.060> environment 00:12:20.560 --> 00:12:20.570 align:start position:0% couldn't get find execution environment 00:12:20.570 --> 00:12:25.030 align:start position:0% couldn't get find execution environment we<00:12:20.750> can<00:12:23.080> Callaghan<00:12:24.080> took<00:12:24.200> my<00:12:24.320> contracts<00:12:24.890> and 00:12:25.030 --> 00:12:25.040 align:start position:0% we can Callaghan took my contracts and 00:12:25.040 --> 00:12:28.870 align:start position:0% we can Callaghan took my contracts and the<00:12:25.100> reason<00:12:25.370> for<00:12:25.400> that<00:12:25.550> is<00:12:25.880> that<00:12:26.150> we 00:12:28.870 --> 00:12:28.880 align:start position:0% 00:12:28.880 --> 00:12:30.860 align:start position:0% transform<00:12:29.970> web-centric<00:12:30.420> text 00:12:30.860 --> 00:12:30.870 align:start position:0% transform web-centric text 00:12:30.870 --> 00:12:32.600 align:start position:0% transform web-centric text representation<00:12:31.170> tumor<00:12:31.829> center<00:12:32.160> by<00:12:32.550> the 00:12:32.600 --> 00:12:32.610 align:start position:0% representation tumor center by the 00:12:32.610 --> 00:12:34.759 align:start position:0% representation tumor center by the representation<00:12:33.149> and<00:12:33.750> you<00:12:34.050> need<00:12:34.290> that<00:12:34.529> for 00:12:34.759 --> 00:12:34.769 align:start position:0% representation and you need that for 00:12:34.769 --> 00:12:36.829 align:start position:0% representation and you need that for deploying<00:12:35.640> the<00:12:35.820> fraction<00:12:36.269> deploying<00:12:36.660> the 00:12:36.829 --> 00:12:36.839 align:start position:0% deploying the fraction deploying the 00:12:36.839 --> 00:12:38.870 align:start position:0% deploying the fraction deploying the contract<00:12:37.260> smooth<00:12:37.649> because<00:12:38.430> it<00:12:38.610> means<00:12:38.760> the 00:12:38.870 --> 00:12:38.880 align:start position:0% contract smooth because it means the 00:12:38.880 --> 00:12:41.370 align:start position:0% contract smooth because it means the return<00:12:39.000> of<00:12:39.240> ivory 00:12:41.370 --> 00:12:41.380 align:start position:0% return of ivory 00:12:41.380 --> 00:12:49.530 align:start position:0% return of ivory I'm<00:12:43.380> representation<00:12:47.100> how<00:12:48.100> does<00:12:48.250> the<00:12:48.540> compiler 00:12:49.530 --> 00:12:49.540 align:start position:0% I'm representation how does the compiler 00:12:49.540 --> 00:12:56.370 align:start position:0% I'm representation how does the compiler -<00:12:50.140> II<00:12:50.170> wasn't<00:12:50.500> work<00:12:54.240> it<00:12:55.240> takes<00:12:55.510> the<00:12:55.840> regular 00:12:56.370 --> 00:12:56.380 align:start position:0% - II wasn't work it takes the regular 00:12:56.380 --> 00:12:58.410 align:start position:0% - II wasn't work it takes the regular IBM<00:12:56.860> you<00:12:56.980> know<00:12:57.040> so<00:12:57.430> it<00:12:57.520> starts<00:12:57.790> exactly<00:12:58.000> at<00:12:58.240> the 00:12:58.410 --> 00:12:58.420 align:start position:0% IBM you know so it starts exactly at the 00:12:58.420 --> 00:13:03.920 align:start position:0% IBM you know so it starts exactly at the point<00:12:58.990> where<00:12:59.230> the<00:13:00.300> civility<00:13:01.300> to<00:13:01.830> usually<00:13:02.830> be<00:13:02.950> a 00:13:03.920 --> 00:13:03.930 align:start position:0% point where the civility to usually be a 00:13:03.930 --> 00:13:11.430 align:start position:0% point where the civility to usually be a provider<00:13:07.050> went<00:13:08.050> and<00:13:09.690> so<00:13:10.690> you<00:13:10.750> have<00:13:10.990> to<00:13:11.140> you 00:13:11.430 --> 00:13:11.440 align:start position:0% provider went and so you have to you 00:13:11.440 --> 00:13:15.120 align:start position:0% provider went and so you have to you have<00:13:11.500> to<00:13:11.620> transform<00:13:12.120> 256<00:13:13.170> bit<00:13:14.170> code<00:13:14.410> to<00:13:14.590> 64-bit 00:13:15.120 --> 00:13:15.130 align:start position:0% have to transform 256 bit code to 64-bit 00:13:15.130 --> 00:13:17.370 align:start position:0% have to transform 256 bit code to 64-bit code<00:13:15.430> and<00:13:15.700> this<00:13:16.270> is<00:13:16.330> that<00:13:16.570> by<00:13:16.720> splitting<00:13:17.140> all 00:13:17.370 --> 00:13:17.380 align:start position:0% code and this is that by splitting all 00:13:17.380 --> 00:13:19.290 align:start position:0% code and this is that by splitting all the<00:13:17.530> you'll<00:13:17.680> variables<00:13:18.220> into<00:13:18.550> four<00:13:18.910> modules 00:13:19.290 --> 00:13:19.300 align:start position:0% the you'll variables into four modules 00:13:19.300 --> 00:13:26.490 align:start position:0% the you'll variables into four modules and<00:13:21.900> at<00:13:22.900> that<00:13:23.080> point<00:13:23.290> we<00:13:23.680> have<00:13:23.860> some<00:13:25.080> kind<00:13:26.080> of<00:13:26.170> a 00:13:26.490 --> 00:13:26.500 align:start position:0% and at that point we have some kind of a 00:13:26.500 --> 00:13:30.840 align:start position:0% and at that point we have some kind of a mix<00:13:27.100> of<00:13:27.510> web<00:13:28.510> assembly 00:13:30.840 --> 00:13:30.850 align:start position:0% mix of web assembly 00:13:30.850 --> 00:13:34.329 align:start position:0% mix of web assembly because<00:13:31.850> we<00:13:32.029> still<00:13:32.209> use<00:13:32.420> the<00:13:32.600> EBM<00:13:32.959> opcodes<00:13:33.709> but 00:13:34.329 --> 00:13:34.339 align:start position:0% because we still use the EBM opcodes but 00:13:34.339 --> 00:13:38.110 align:start position:0% because we still use the EBM opcodes but we<00:13:34.550> already<00:13:34.820> use<00:13:35.149> 64-bit<00:13:35.750> variables<00:13:36.350> and<00:13:37.120> then 00:13:38.110 --> 00:13:38.120 align:start position:0% we already use 64-bit variables and then 00:13:38.120 --> 00:13:43.540 align:start position:0% we already use 64-bit variables and then we<00:13:38.420> add<00:13:40.360> kind<00:13:41.360> of<00:13:41.420> a<00:13:41.540> library<00:13:42.080> code<00:13:42.800> that 00:13:43.540 --> 00:13:43.550 align:start position:0% we add kind of a library code that 00:13:43.550 --> 00:13:46.000 align:start position:0% we add kind of a library code that implements<00:13:44.000> all<00:13:44.360> EVM<00:13:45.320> opcodes 00:13:46.000 --> 00:13:46.010 align:start position:0% implements all EVM opcodes 00:13:46.010 --> 00:13:48.190 align:start position:0% implements all EVM opcodes has<00:13:46.130> used<00:13:46.700> different<00:13:46.880> functions<00:13:47.540> using<00:13:48.140> the 00:13:48.190 --> 00:13:48.200 align:start position:0% has used different functions using the 00:13:48.200 --> 00:13:49.530 align:start position:0% has used different functions using the EVM 00:13:49.530 --> 00:13:49.540 align:start position:0% EVM 00:13:49.540 --> 00:13:54.820 align:start position:0% EVM LED<00:13:50.540> wasn't<00:13:51.260> within<00:13:51.800> functions<00:13:52.270> and<00:13:53.680> at<00:13:54.680> that 00:13:54.820 --> 00:13:54.830 align:start position:0% LED wasn't within functions and at that 00:13:54.830 --> 00:14:00.970 align:start position:0% LED wasn't within functions and at that point<00:13:54.980> we<00:13:55.220> have<00:13:57.820> it<00:13:58.820> wasn't<00:13:59.209> favorable<00:13:59.839> and<00:14:00.020> we 00:14:00.970 --> 00:14:00.980 align:start position:0% point we have it wasn't favorable and we 00:14:00.980 --> 00:14:03.130 align:start position:0% point we have it wasn't favorable and we run<00:14:01.250> the<00:14:01.700> regular<00:14:02.089> optimizer<00:14:02.510> will<00:14:02.750> also<00:14:02.990> have 00:14:03.130 --> 00:14:03.140 align:start position:0% run the regular optimizer will also have 00:14:03.140 --> 00:14:05.320 align:start position:0% run the regular optimizer will also have an<00:14:03.260> EVM<00:14:03.680> you<00:14:03.830> with<00:14:04.190> slight<00:14:04.580> modifications 00:14:05.320 --> 00:14:05.330 align:start position:0% an EVM you with slight modifications 00:14:05.330 --> 00:14:08.519 align:start position:0% an EVM you with slight modifications because<00:14:06.170> we<00:14:06.410> have<00:14:06.529> different<00:14:06.620> approaches<00:14:07.279> and 00:14:08.519 --> 00:14:08.529 align:start position:0% because we have different approaches and 00:14:08.529 --> 00:14:11.290 align:start position:0% because we have different approaches and yeah<00:14:09.529> it<00:14:09.589> turns<00:14:09.800> out<00:14:09.950> that<00:14:10.100> we<00:14:10.279> are<00:14:10.610> able<00:14:11.180> to 00:14:11.290 --> 00:14:11.300 align:start position:0% yeah it turns out that we are able to 00:14:11.300 --> 00:14:13.780 align:start position:0% yeah it turns out that we are able to reuse<00:14:11.800> almost<00:14:12.800> all<00:14:13.010> of<00:14:13.040> the<00:14:13.190> proponents<00:14:13.670> of 00:14:13.780 --> 00:14:13.790 align:start position:0% reuse almost all of the proponents of 00:14:13.790 --> 00:14:20.079 align:start position:0% reuse almost all of the proponents of the<00:14:14.170> PM's<00:14:15.170> you<00:14:15.320> will<00:14:15.529> optimizer<00:14:18.760> yeah<00:14:19.760> in 00:14:20.079 --> 00:14:20.089 align:start position:0% the PM's you will optimizer yeah in 00:14:20.089 --> 00:14:22.410 align:start position:0% the PM's you will optimizer yeah in terrorist<00:14:20.420> academy<00:14:21.350> yeah<00:14:22.160> pretty 00:14:22.410 --> 00:14:22.420 align:start position:0% terrorist academy yeah pretty 00:14:22.420 --> 00:14:24.070 align:start position:0% terrorist academy yeah pretty straightforward<00:14:23.420> transformation 00:14:24.070 --> 00:14:24.080 align:start position:0% straightforward transformation 00:14:24.080 --> 00:14:25.920 align:start position:0% straightforward transformation everything 00:14:25.920 --> 00:14:25.930 align:start position:0% everything 00:14:25.930 --> 00:14:27.850 align:start position:0% everything yeah<00:14:26.930> that's<00:14:27.110> secretive<00:14:27.380> that<00:14:27.440> is<00:14:27.560> specific 00:14:27.850 --> 00:14:27.860 align:start position:0% yeah that's secretive that is specific 00:14:27.860 --> 00:14:32.230 align:start position:0% yeah that's secretive that is specific some<00:14:28.040> example<00:14:29.680> we<00:14:30.680> just<00:14:30.920> use<00:14:31.250> we<00:14:31.820> just<00:14:32.029> store 00:14:32.230 --> 00:14:32.240 align:start position:0% some example we just use we just store 00:14:32.240 --> 00:14:35.199 align:start position:0% some example we just use we just store the<00:14:32.570> current<00:14:33.080> block<00:14:33.800> element<00:14:34.370> at<00:14:34.550> position 00:14:35.199 --> 00:14:35.209 align:start position:0% the current block element at position 00:14:35.209 --> 00:14:39.970 align:start position:0% the current block element at position zero<00:14:35.660> in<00:14:35.750> memory<00:14:36.700> this<00:14:37.990> yeah<00:14:38.990> I<00:14:39.290> have<00:14:39.649> to<00:14:39.770> warn 00:14:39.970 --> 00:14:39.980 align:start position:0% zero in memory this yeah I have to warn 00:14:39.980 --> 00:14:42.970 align:start position:0% zero in memory this yeah I have to warn you<00:14:40.040> because<00:14:40.250> of<00:14:40.550> those<00:14:40.899> 256<00:14:41.899> bits<00:14:42.110> 64-bit 00:14:42.970 --> 00:14:42.980 align:start position:0% you because of those 256 bits 64-bit 00:14:42.980 --> 00:14:47.470 align:start position:0% you because of those 256 bits 64-bit thing<00:14:43.640> this<00:14:44.000> will<00:14:44.209> be<00:14:44.810> complicated<00:14:46.270> okay 00:14:47.470 --> 00:14:47.480 align:start position:0% thing this will be complicated okay 00:14:47.480 --> 00:14:50.319 align:start position:0% thing this will be complicated okay what<00:14:47.720> we<00:14:47.839> do<00:14:47.959> is<00:14:48.339> guesstimate<00:14:49.339> returns<00:14:49.700> a<00:14:49.820> 256 00:14:50.319 --> 00:14:50.329 align:start position:0% what we do is guesstimate returns a 256 00:14:50.329 --> 00:14:52.480 align:start position:0% what we do is guesstimate returns a 256 bit<00:14:50.420> value<00:14:51.230> so<00:14:51.770> we<00:14:51.860> have<00:14:51.950> to<00:14:52.010> split<00:14:52.160> that<00:14:52.279> into 00:14:52.480 --> 00:14:52.490 align:start position:0% bit value so we have to split that into 00:14:52.490 --> 00:14:55.300 align:start position:0% bit value so we have to split that into four<00:14:52.730> variables 00:14:55.300 --> 00:14:55.310 align:start position:0% 00:14:55.310 --> 00:14:57.070 align:start position:0% that's<00:14:55.760> what<00:14:56.510> is<00:14:56.600> done<00:14:56.780> here<00:14:56.810> in<00:14:57.020> the 00:14:57.070 --> 00:14:57.080 align:start position:0% that's what is done here in the 00:14:57.080 --> 00:14:58.810 align:start position:0% that's what is done here in the beginning<00:14:57.440> so<00:14:57.650> we<00:14:57.860> call<00:14:58.220> guesstimate<00:14:58.640> and 00:14:58.810 --> 00:14:58.820 align:start position:0% beginning so we call guesstimate and 00:14:58.820 --> 00:15:01.600 align:start position:0% beginning so we call guesstimate and selected<00:14:59.450> for<00:14:59.600> variables<00:15:00.290> and<00:15:00.500> then<00:15:01.100> we<00:15:01.130> for<00:15:01.430> M 00:15:01.600 --> 00:15:01.610 align:start position:0% selected for variables and then we for M 00:15:01.610 --> 00:15:04.530 align:start position:0% selected for variables and then we for M store<00:15:01.910> that<00:15:02.150> may<00:15:02.330> be<00:15:02.390> kind<00:15:02.930> of<00:15:03.020> sweet<00:15:03.650> new 00:15:04.530 --> 00:15:04.540 align:start position:0% store that may be kind of sweet new 00:15:04.540 --> 00:15:08.470 align:start position:0% store that may be kind of sweet new hybrid<00:15:05.540> EVM<00:15:05.990> it<00:15:06.230> was<00:15:06.440> new<00:15:07.450> function<00:15:08.450> that 00:15:08.470 --> 00:15:08.480 align:start position:0% hybrid EVM it was new function that 00:15:08.480 --> 00:15:10.450 align:start position:0% hybrid EVM it was new function that takes<00:15:08.840> eight<00:15:09.110> parameters<00:15:09.350> with<00:15:09.950> one<00:15:10.160> for<00:15:10.370> the 00:15:10.450 --> 00:15:10.460 align:start position:0% takes eight parameters with one for the 00:15:10.460 --> 00:15:14.110 align:start position:0% takes eight parameters with one for the address<00:15:11.450> and<00:15:11.630> proper<00:15:11.960> value<00:15:12.320> and<00:15:13.090> then<00:15:14.090> we 00:15:14.110 --> 00:15:14.120 align:start position:0% address and proper value and then we 00:15:14.120 --> 00:15:17.980 align:start position:0% address and proper value and then we have<00:15:14.690> the<00:15:16.150> implementations<00:15:17.150> of<00:15:17.360> the<00:15:17.600> idiom<00:15:17.900> of 00:15:17.980 --> 00:15:17.990 align:start position:0% have the implementations of the idiom of 00:15:17.990 --> 00:15:21.460 align:start position:0% have the implementations of the idiom of codes<00:15:18.260> in<00:15:19.210> some<00:15:20.210> built-ins<00:15:20.720> of<00:15:21.020> gasoline<00:15:21.350> for 00:15:21.460 --> 00:15:21.470 align:start position:0% codes in some built-ins of gasoline for 00:15:21.470 --> 00:15:24.250 align:start position:0% codes in some built-ins of gasoline for example<00:15:21.920> just<00:15:22.010> cause<00:15:22.280> you<00:15:23.030> don't<00:15:23.360> get<00:15:23.600> of 00:15:24.250 --> 00:15:24.260 align:start position:0% example just cause you don't get of 00:15:24.260 --> 00:15:28.060 align:start position:0% example just cause you don't get of Testament<00:15:24.940> and<00:15:25.940> an<00:15:26.090> M<00:15:26.270> store<00:15:26.570> our<00:15:27.440> wheat<00:15:27.620> for 00:15:28.060 --> 00:15:28.070 align:start position:0% Testament and an M store our wheat for 00:15:28.070 --> 00:15:31.690 align:start position:0% Testament and an M store our wheat for minion<00:15:28.460> swapping<00:15:28.910> because<00:15:30.190> what<00:15:31.190> assembly<00:15:31.580> is 00:15:31.690 --> 00:15:31.700 align:start position:0% minion swapping because what assembly is 00:15:31.700 --> 00:15:38.740 align:start position:0% minion swapping because what assembly is a<00:15:32.000> machine<00:15:35.260> is<00:15:36.260> not<00:15:36.410> very<00:15:36.620> complicated<00:15:36.890> but<00:15:37.750> if 00:15:38.740 --> 00:15:38.750 align:start position:0% a machine is not very complicated but if 00:15:38.750 --> 00:15:40.900 align:start position:0% a machine is not very complicated but if you<00:15:38.840> apply<00:15:39.080> the<00:15:39.140> optimizer<00:15:39.710> then<00:15:40.550> it<00:15:40.700> will<00:15:40.820> of 00:15:40.900 --> 00:15:40.910 align:start position:0% you apply the optimizer then it will of 00:15:40.910 --> 00:15:42.370 align:start position:0% you apply the optimizer then it will of course<00:15:40.940> in<00:15:41.390> line<00:15:41.570> the<00:15:41.780> guess<00:15:41.930> that<00:15:42.110> we<00:15:42.200> call 00:15:42.370 --> 00:15:42.380 align:start position:0% course in line the guess that we call 00:15:42.380 --> 00:15:45.580 align:start position:0% course in line the guess that we call here<00:15:42.680> and<00:15:43.690> also<00:15:44.690> remove<00:15:45.050> all<00:15:45.290> the<00:15:45.470> other 00:15:45.580 --> 00:15:45.590 align:start position:0% here and also remove all the other 00:15:45.590 --> 00:15:49.500 align:start position:0% here and also remove all the other varieties<00:15:46.370> we<00:15:46.460> don't<00:15:46.610> get<00:15:46.730> anymore 00:15:49.500 --> 00:15:49.510 align:start position:0% 00:15:49.510 --> 00:15:51.910 align:start position:0% also<00:15:50.510> the<00:15:50.630> M<00:15:50.750> store<00:15:51.080> it<00:15:51.320> has<00:15:51.470> all<00:15:51.770> the 00:15:51.910 --> 00:15:51.920 align:start position:0% also the M store it has all the 00:15:51.920 --> 00:15:54.070 align:start position:0% also the M store it has all the constants<00:15:52.460> here<00:15:52.640> so<00:15:52.970> it's<00:15:53.240> probably<00:15:53.960> make 00:15:54.070 --> 00:15:54.080 align:start position:0% constants here so it's probably make 00:15:54.080 --> 00:15:56.590 align:start position:0% constants here so it's probably make sense<00:15:54.260> and<00:15:54.740> then<00:15:55.070> and 00:15:56.590 --> 00:15:56.600 align:start position:0% sense and then and 00:15:56.600 --> 00:16:07.270 align:start position:0% sense and then and like<00:15:56.900> this<00:15:58.930> only<00:15:59.930> the<00:16:00.050> engines<00:16:00.380> watches 00:16:07.270 --> 00:16:07.280 align:start position:0% 00:16:07.280 --> 00:16:10.000 align:start position:0% okay<00:16:07.820> now<00:16:08.510> the<00:16:08.570> three<00:16:08.780> tarts<00:16:09.110> third<00:16:09.590> part<00:16:09.920> of 00:16:10.000 --> 00:16:10.010 align:start position:0% okay now the three tarts third part of 00:16:10.010 --> 00:16:16.780 align:start position:0% okay now the three tarts third part of the<00:16:10.130> talk<00:16:10.370> the<00:16:10.930> original<00:16:11.930> optimizer<00:16:14.710> all<00:16:15.790> all 00:16:16.780 --> 00:16:16.790 align:start position:0% the talk the original optimizer all all 00:16:16.790 --> 00:16:19.150 align:start position:0% the talk the original optimizer all all components<00:16:17.210> of<00:16:17.510> the<00:16:17.630> optimizer<00:16:18.050> take<00:16:18.980> your 00:16:19.150 --> 00:16:19.160 align:start position:0% components of the optimizer take your 00:16:19.160 --> 00:16:19.930 align:start position:0% components of the optimizer take your coat 00:16:19.930 --> 00:16:19.940 align:start position:0% coat 00:16:19.940 --> 00:16:22.090 align:start position:0% coat transform<00:16:20.750> it<00:16:20.840> and<00:16:20.990> I'll<00:16:21.080> put<00:16:21.290> you<00:16:21.380> in<00:16:21.410> yes<00:16:21.860> sir 00:16:22.090 --> 00:16:22.100 align:start position:0% transform it and I'll put you in yes sir 00:16:22.100 --> 00:16:33.100 align:start position:0% transform it and I'll put you in yes sir it's<00:16:27.790> so<00:16:28.790> all<00:16:29.450> the<00:16:30.140> motives<00:16:30.980> are<00:16:31.960> simple<00:16:32.960> that 00:16:33.100 --> 00:16:33.110 align:start position:0% it's so all the motives are simple that 00:16:33.110 --> 00:16:35.820 align:start position:0% it's so all the motives are simple that can<00:16:33.350> be<00:16:33.470> combined<00:16:33.920> in<00:16:34.070> an<00:16:34.160> arbitrary<00:16:34.550> rating 00:16:35.820 --> 00:16:35.830 align:start position:0% can be combined in an arbitrary rating 00:16:35.830 --> 00:16:39.580 align:start position:0% can be combined in an arbitrary rating if<00:16:36.830> all<00:16:37.100> the<00:16:37.340> modules<00:16:38.210> are<00:16:38.600> correct<00:16:38.900> and<00:16:39.230> the 00:16:39.580 --> 00:16:39.590 align:start position:0% if all the modules are correct and the 00:16:39.590 --> 00:16:43.960 align:start position:0% if all the modules are correct and the Veloster<00:16:41.830> it<00:16:42.830> turned<00:16:43.190> out<00:16:43.310> that<00:16:43.370> we<00:16:43.640> need<00:16:43.940> a 00:16:43.960 --> 00:16:43.970 align:start position:0% Veloster it turned out that we need a 00:16:43.970 --> 00:16:46.480 align:start position:0% Veloster it turned out that we need a little<00:16:44.180> bit<00:16:44.330> more<00:16:45.050> notice<00:16:46.010> that<00:16:46.190> we<00:16:46.310> initially 00:16:46.480 --> 00:16:46.490 align:start position:0% little bit more notice that we initially 00:16:46.490 --> 00:16:49.900 align:start position:0% little bit more notice that we initially thought<00:16:46.700> we<00:16:47.060> currently<00:16:47.210> have<00:16:47.450> roughly<00:16:47.960> 25<00:16:48.910> but 00:16:49.900 --> 00:16:49.910 align:start position:0% thought we currently have roughly 25 but 00:16:49.910 --> 00:16:53.970 align:start position:0% thought we currently have roughly 25 but most<00:16:50.240> of<00:16:50.420> the<00:16:50.540> motives<00:16:50.870> are<00:16:51.020> really<00:16:51.410> tiny<00:16:51.680> and 00:16:53.970 --> 00:16:53.980 align:start position:0% most of the motives are really tiny and 00:16:53.980 --> 00:16:57.040 align:start position:0% most of the motives are really tiny and there<00:16:54.980> are<00:16:55.190> only<00:16:55.430> two<00:16:55.820> to<00:16:56.000> three<00:16:56.050> components 00:16:57.040 --> 00:16:57.050 align:start position:0% there are only two to three components 00:16:57.050 --> 00:17:03.700 align:start position:0% there are only two to three components that<00:16:57.080> we<00:16:57.320> store<00:16:57.620> a<00:16:57.860> data<00:16:58.280> structure<00:16:58.700> so<00:17:02.530> so<00:17:03.530> for 00:17:03.700 --> 00:17:03.710 align:start position:0% that we store a data structure so so for 00:17:03.710 --> 00:17:09.910 align:start position:0% that we store a data structure so so for example<00:17:04.480> the<00:17:05.480> condition<00:17:06.439> of<00:17:06.530> 35<00:17:07.040> is<00:17:07.390> that<00:17:08.920> it 00:17:09.910 --> 00:17:09.920 align:start position:0% example the condition of 35 is that it 00:17:09.920 --> 00:17:12.939 align:start position:0% example the condition of 35 is that it takes<00:17:10.130> a<00:17:10.280> look<00:17:10.400> at<00:17:10.640> branches<00:17:11.480> so<00:17:12.350> for<00:17:12.560> some<00:17:12.740> you 00:17:12.939 --> 00:17:12.949 align:start position:0% takes a look at branches so for some you 00:17:12.949 --> 00:17:17.079 align:start position:0% takes a look at branches so for some you see<00:17:13.220> we<00:17:13.400> start<00:17:14.650> the<00:17:15.650> body<00:17:15.860> of<00:17:16.010> this<00:17:16.160> is<00:17:16.339> almost 00:17:17.079 --> 00:17:17.089 align:start position:0% see we start the body of this is almost 00:17:17.089 --> 00:17:19.630 align:start position:0% see we start the body of this is almost earnings<00:17:17.540> so<00:17:18.199> after<00:17:18.530> the<00:17:18.650> body<00:17:18.829> you<00:17:19.130> need<00:17:19.310> you 00:17:19.630 --> 00:17:19.640 align:start position:0% earnings so after the body you need you 00:17:19.640 --> 00:17:23.380 align:start position:0% earnings so after the body you need you know<00:17:20.120> that<00:17:20.420> C<00:17:20.900> is<00:17:21.020> false<00:17:21.290> or<00:17:21.560> so<00:17:21.980> so<00:17:22.790> the<00:17:23.240> only 00:17:23.380 --> 00:17:23.390 align:start position:0% know that C is false or so so the only 00:17:23.390 --> 00:17:25.030 align:start position:0% know that C is false or so so the only thing<00:17:23.600> that<00:17:23.630> this<00:17:23.990> asses<00:17:24.380> injects 00:17:25.030 --> 00:17:25.040 align:start position:0% thing that this asses injects 00:17:25.040 --> 00:17:27.600 align:start position:0% thing that this asses injects assignments<00:17:25.699> of<00:17:25.790> this<00:17:25.939> form<00:17:26.240> after 00:17:27.600 --> 00:17:27.610 align:start position:0% assignments of this form after 00:17:27.610 --> 00:17:33.040 align:start position:0% assignments of this form after terminating<00:17:28.610> branches<00:17:29.090> and<00:17:31.060> other<00:17:32.060> motifs<00:17:32.870> in 00:17:33.040 --> 00:17:33.050 align:start position:0% terminating branches and other motifs in 00:17:33.050 --> 00:17:35.230 align:start position:0% terminating branches and other motifs in the<00:17:33.140> optimizer<00:17:33.590> can<00:17:34.160> pick<00:17:34.340> that<00:17:34.490> up<00:17:34.550> and<00:17:34.820> use 00:17:35.230 --> 00:17:35.240 align:start position:0% the optimizer can pick that up and use 00:17:35.240 --> 00:17:37.480 align:start position:0% the optimizer can pick that up and use their<00:17:35.480> information<00:17:35.810> but<00:17:36.410> the<00:17:36.950> information<00:17:37.100> is 00:17:37.480 --> 00:17:37.490 align:start position:0% their information but the information is 00:17:37.490 --> 00:17:40.000 align:start position:0% their information but the information is visible<00:17:37.670> below<00:17:38.060> this<00:17:38.600> is<00:17:38.750> not<00:17:38.930> stored<00:17:39.260> in<00:17:39.470> some 00:17:40.000 --> 00:17:40.010 align:start position:0% visible below this is not stored in some 00:17:40.010 --> 00:17:52.620 align:start position:0% visible below this is not stored in some Hey 00:17:52.620 --> 00:17:52.630 align:start position:0% 00:17:52.630 --> 00:17:56.530 align:start position:0% talk<00:17:53.630> about<00:17:53.750> the<00:17:54.320> future<00:17:54.560> memory<00:17:55.460> times<00:17:55.700> we 00:17:56.530 --> 00:17:56.540 align:start position:0% talk about the future memory times we 00:17:56.540 --> 00:17:58.420 align:start position:0% talk about the future memory times we already<00:17:56.810> saw<00:17:56.960> that<00:17:56.990> we<00:17:57.950> have<00:17:58.100> some<00:17:58.280> problems 00:17:58.420 --> 00:17:58.430 align:start position:0% already saw that we have some problems 00:17:58.430 --> 00:18:00.580 align:start position:0% already saw that we have some problems with<00:17:58.790> memory<00:17:59.090> this<00:17:59.750> will<00:18:00.140> hopefully<00:18:00.290> be 00:18:00.580 --> 00:18:00.590 align:start position:0% with memory this will hopefully be 00:18:00.590 --> 00:18:04.360 align:start position:0% with memory this will hopefully be solved<00:18:00.890> by<00:18:01.070> adding<00:18:02.060> memory<00:18:02.840> chunks<00:18:03.680> as<00:18:03.860> a 00:18:04.360 --> 00:18:04.370 align:start position:0% solved by adding memory chunks as a 00:18:04.370 --> 00:18:08.260 align:start position:0% solved by adding memory chunks as a built-in<00:18:05.210> type<00:18:05.510> into<00:18:05.990> you<00:18:07.210> that<00:18:08.210> way 00:18:08.260 --> 00:18:08.270 align:start position:0% built-in type into you that way 00:18:08.270 --> 00:18:10.180 align:start position:0% built-in type into you that way different<00:18:08.960> memory<00:18:09.260> stores<00:18:09.560> two<00:18:09.770> different 00:18:10.180 --> 00:18:10.190 align:start position:0% different memory stores two different 00:18:10.190 --> 00:18:12.250 align:start position:0% different memory stores two different data<00:18:10.550> structure<00:18:11.000> are<00:18:11.330> fully<00:18:11.750> independent 00:18:12.250 --> 00:18:12.260 align:start position:0% data structure are fully independent 00:18:12.260 --> 00:18:14.230 align:start position:0% data structure are fully independent because<00:18:12.560> it<00:18:12.800> uses<00:18:13.160> kind<00:18:13.370> of<00:18:13.490> a<00:18:13.580> different<00:18:14.030> hand 00:18:14.230 --> 00:18:14.240 align:start position:0% because it uses kind of a different hand 00:18:14.240 --> 00:18:19.690 align:start position:0% because it uses kind of a different hand into<00:18:14.540> excess<00:18:14.870> memory<00:18:17.710> also<00:18:18.710> we're<00:18:19.430> thinking 00:18:19.690 --> 00:18:19.700 align:start position:0% into excess memory also we're thinking 00:18:19.700 --> 00:18:21.340 align:start position:0% into excess memory also we're thinking about<00:18:19.820> hanging<00:18:19.940> a<00:18:20.090> super<00:18:20.360> optimizer<00:18:20.780> so<00:18:20.960> in 00:18:21.340 --> 00:18:21.350 align:start position:0% about hanging a super optimizer so in 00:18:21.350 --> 00:18:23.500 align:start position:0% about hanging a super optimizer so in optimizer<00:18:21.890> that<00:18:22.040> takes<00:18:22.880> a<00:18:23.030> really<00:18:23.300> long<00:18:23.390> time 00:18:23.500 --> 00:18:23.510 align:start position:0% optimizer that takes a really long time 00:18:23.510 --> 00:18:26.200 align:start position:0% optimizer that takes a really long time and<00:18:23.750> tries<00:18:24.230> to<00:18:24.580> really<00:18:25.580> crunch<00:18:26.060> the<00:18:26.180> numbers 00:18:26.200 --> 00:18:26.210 align:start position:0% and tries to really crunch the numbers 00:18:26.210 --> 00:18:28.930 align:start position:0% and tries to really crunch the numbers and<00:18:26.660> find<00:18:26.900> a<00:18:27.050> good<00:18:27.530> way<00:18:27.710> to<00:18:27.770> optimize<00:18:28.520> the<00:18:28.790> code 00:18:28.930 --> 00:18:28.940 align:start position:0% and find a good way to optimize the code 00:18:28.940 --> 00:18:32.560 align:start position:0% and find a good way to optimize the code and<00:18:29.980> that<00:18:30.980> can<00:18:31.160> have<00:18:31.340> that<00:18:32.060> can<00:18:32.210> maybe<00:18:32.360> have 00:18:32.560 --> 00:18:32.570 align:start position:0% and that can have that can maybe have 00:18:32.570 --> 00:18:34.300 align:start position:0% and that can have that can maybe have shortcuts<00:18:33.050> if<00:18:33.290> you<00:18:33.380> want<00:18:33.560> to<00:18:33.620> recompile<00:18:34.010> stuff 00:18:34.300 --> 00:18:34.310 align:start position:0% shortcuts if you want to recompile stuff 00:18:34.310 --> 00:18:37.750 align:start position:0% shortcuts if you want to recompile stuff that<00:18:34.490> it's<00:18:34.610> it's<00:18:35.090> faster<00:18:35.420> and<00:18:36.550> when<00:18:37.550> thinking 00:18:37.750 --> 00:18:37.760 align:start position:0% that it's it's faster and when thinking 00:18:37.760 --> 00:18:39.880 align:start position:0% that it's it's faster and when thinking about<00:18:37.850> adding<00:18:38.210> a<00:18:38.330> genetic<00:18:39.320> I<00:18:39.410> really<00:18:39.710> need<00:18:39.860> to 00:18:39.880 --> 00:18:39.890 align:start position:0% about adding a genetic I really need to 00:18:39.890 --> 00:18:41.950 align:start position:0% about adding a genetic I really need to find<00:18:40.220> a<00:18:40.370> good<00:18:40.490> order<00:18:40.790> for<00:18:41.030> applying<00:18:41.450> steps<00:18:41.780> it 00:18:41.950 --> 00:18:41.960 align:start position:0% find a good order for applying steps it 00:18:41.960 --> 00:18:44.590 align:start position:0% find a good order for applying steps it has<00:18:42.050> already<00:18:42.290> said<00:18:42.580> each<00:18:43.580> step<00:18:43.910> individually 00:18:44.590 --> 00:18:44.600 align:start position:0% has already said each step individually 00:18:44.600 --> 00:18:48.310 align:start position:0% has already said each step individually should<00:18:45.290> be<00:18:45.440> correct<00:18:45.710> the<00:18:46.430> order<00:18:47.320> doesn't 00:18:48.310 --> 00:18:48.320 align:start position:0% should be correct the order doesn't 00:18:48.320 --> 00:18:49.750 align:start position:0% should be correct the order doesn't matter<00:18:48.440> for<00:18:48.710> correctness<00:18:49.070> but<00:18:49.430> it<00:18:49.580> matters 00:18:49.750 --> 00:18:49.760 align:start position:0% matter for correctness but it matters 00:18:49.760 --> 00:18:54.000 align:start position:0% matter for correctness but it matters for<00:18:49.940> efficiency<00:18:50.900> and<00:18:52.690> yes 00:18:54.000 --> 00:18:54.010 align:start position:0% for efficiency and yes 00:18:54.010 --> 00:18:56.290 align:start position:0% for efficiency and yes fortunately<00:18:55.010> come<00:18:55.190> up<00:18:55.310> with<00:18:55.490> a<00:18:55.610> good<00:18:55.970> order<00:18:56.120> to 00:18:56.290 --> 00:18:56.300 align:start position:0% fortunately come up with a good order to 00:18:56.300 --> 00:19:07.980 align:start position:0% fortunately come up with a good order to apply<00:18:56.480> them 00:19:07.980 --> 00:19:07.990 align:start position:0% 00:19:07.990 --> 00:19:14.960 align:start position:0% the<00:19:08.170> truth<00:19:08.380> was<00:19:08.470> that 00:19:14.960 --> 00:19:14.970 align:start position:0% 00:19:14.970 --> 00:19:21.310 align:start position:0% [Applause]