WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:16.230 align:start position:0% [Applause] 00:00:16.230 --> 00:00:16.240 align:start position:0% 00:00:16.240 --> 00:00:20.140 align:start position:0% welcome<00:00:17.240> everyone<00:00:17.510> my<00:00:17.810> name<00:00:18.439> is<00:00:18.529> Isaac<00:00:18.890> I<00:00:19.640> work 00:00:20.140 --> 00:00:20.150 align:start position:0% welcome everyone my name is Isaac I work 00:00:20.150 --> 00:00:24.010 align:start position:0% welcome everyone my name is Isaac I work at<00:00:20.330> status<00:00:20.750> at<00:00:21.020> the<00:00:21.140> research<00:00:21.470> they're<00:00:23.020> the 00:00:24.010 --> 00:00:24.020 align:start position:0% at status at the research they're the 00:00:24.020 --> 00:00:25.600 align:start position:0% at status at the research they're the dominant<00:00:24.200> key<00:00:24.619> right<00:00:24.770> now<00:00:24.950> one<00:00:25.189> of<00:00:25.220> the<00:00:25.400> bigger 00:00:25.600 --> 00:00:25.610 align:start position:0% dominant key right now one of the bigger 00:00:25.610 --> 00:00:27.720 align:start position:0% dominant key right now one of the bigger projects<00:00:25.970> were<00:00:26.150> working<00:00:26.180> on<00:00:26.630> is<00:00:26.810> they're 00:00:27.720 --> 00:00:27.730 align:start position:0% projects were working on is they're 00:00:27.730 --> 00:00:32.530 align:start position:0% projects were working on is they're interesting<00:00:28.989> everybody<00:00:31.000> try<00:00:32.000> to<00:00:32.060> see<00:00:32.390> you 00:00:32.530 --> 00:00:32.540 align:start position:0% interesting everybody try to see you 00:00:32.540 --> 00:00:36.850 align:start position:0% interesting everybody try to see you messages<00:00:35.200> there's<00:00:36.200> one<00:00:36.380> thing<00:00:36.559> you<00:00:36.680> wouldn't 00:00:36.850 --> 00:00:36.860 align:start position:0% messages there's one thing you wouldn't 00:00:36.860 --> 00:00:45.930 align:start position:0% messages there's one thing you wouldn't remember<00:00:37.130> about<00:00:37.460> you<00:00:37.730> is<00:00:38.030> that<00:00:38.809> I<00:00:38.870> changed<00:00:40.690> I 00:00:45.930 --> 00:00:45.940 align:start position:0% 00:00:45.940 --> 00:00:48.669 align:start position:0% would<00:00:46.940> actually<00:00:47.359> go<00:00:47.480> into<00:00:47.629> the<00:00:47.809> reason<00:00:48.140> why 00:00:48.669 --> 00:00:48.679 align:start position:0% would actually go into the reason why 00:00:48.679 --> 00:00:54.189 align:start position:0% would actually go into the reason why the<00:00:48.739> girl<00:00:49.100> I<00:00:52.449> mentioned<00:00:53.449> that<00:00:53.539> they're<00:00:53.780> gonna 00:00:54.189 --> 00:00:54.199 align:start position:0% the girl I mentioned that they're gonna 00:00:54.199 --> 00:00:57.700 align:start position:0% the girl I mentioned that they're gonna follow<00:00:54.469> along<00:00:55.629> looking<00:00:56.629> at<00:00:56.749> is<00:00:56.899> on<00:00:57.019> lines<00:00:57.260> in 00:00:57.700 --> 00:00:57.710 align:start position:0% follow along looking at is on lines in 00:00:57.710 --> 00:01:03.780 align:start position:0% follow along looking at is on lines in notes<00:00:58.010> are<00:00:58.329> rid<00:00:59.329> of<00:00:59.449> the<00:00:59.539> spicy<00:00:59.809> so<00:01:00.379> many 00:01:03.780 --> 00:01:03.790 align:start position:0% 00:01:03.790 --> 00:01:05.980 align:start position:0% there's<00:01:04.790> a<00:01:04.879> couple<00:01:05.059> of<00:01:05.239> people<00:01:05.420> I<00:01:05.630> wanted<00:01:05.870> to 00:01:05.980 --> 00:01:05.990 align:start position:0% there's a couple of people I wanted to 00:01:05.990 --> 00:01:11.040 align:start position:0% there's a couple of people I wanted to mention<00:01:06.820> like<00:01:08.530> where<00:01:09.530> this<00:01:09.620> is<00:01:10.340> coming<00:01:10.520> from 00:01:11.040 --> 00:01:11.050 align:start position:0% mention like where this is coming from 00:01:11.050 --> 00:01:14.560 align:start position:0% mention like where this is coming from we<00:01:12.050> were<00:01:12.200> sort<00:01:12.470> of<00:01:13.030> sitting<00:01:14.030> around<00:01:14.240> and 00:01:14.560 --> 00:01:14.570 align:start position:0% we were sort of sitting around and 00:01:14.570 --> 00:01:15.880 align:start position:0% we were sort of sitting around and thinking<00:01:14.659> whether<00:01:15.110> we<00:01:15.259> should<00:01:15.409> start<00:01:15.649> just 00:01:15.880 --> 00:01:15.890 align:start position:0% thinking whether we should start just 00:01:15.890 --> 00:01:20.410 align:start position:0% thinking whether we should start just like<00:01:15.950> you<00:01:16.220> punk<00:01:16.850> project<00:01:17.270> in<00:01:17.420> name<00:01:17.740> and<00:01:19.420> you 00:01:20.410 --> 00:01:20.420 align:start position:0% like you punk project in name and you 00:01:20.420 --> 00:01:22.090 align:start position:0% like you punk project in name and you know<00:01:20.540> as<00:01:20.689> everybody<00:01:20.810> every<00:01:21.470> programmer<00:01:21.860> know 00:01:22.090 --> 00:01:22.100 align:start position:0% know as everybody every programmer know 00:01:22.100 --> 00:01:23.469 align:start position:0% know as everybody every programmer know that<00:01:22.369> the<00:01:22.520> very<00:01:22.729> first<00:01:22.790> thing<00:01:23.270> that<00:01:23.299> you 00:01:23.469 --> 00:01:23.479 align:start position:0% that the very first thing that you 00:01:23.479 --> 00:01:24.750 align:start position:0% that the very first thing that you should<00:01:23.810> do<00:01:23.990> in<00:01:24.140> your 00:01:24.750 --> 00:01:24.760 align:start position:0% should do in your 00:01:24.760 --> 00:01:26.710 align:start position:0% should do in your so<00:01:25.760> that's<00:01:25.910> sitting<00:01:26.210> down<00:01:26.390> and<00:01:26.600> like 00:01:26.710 --> 00:01:26.720 align:start position:0% so that's sitting down and like 00:01:26.720 --> 00:01:30.790 align:start position:0% so that's sitting down and like optimizing<00:01:27.380> the<00:01:27.620> out<00:01:27.770> of<00:01:27.800> it<00:01:29.770> those<00:01:30.770> of 00:01:30.790 --> 00:01:30.800 align:start position:0% optimizing the out of it those of 00:01:30.800 --> 00:01:32.440 align:start position:0% optimizing the out of it those of you<00:01:31.070> that<00:01:31.220> have<00:01:31.400> a<00:01:31.430> manager<00:01:31.970> you<00:01:32.090> call<00:01:32.270> this<00:01:32.390> a 00:01:32.440 --> 00:01:32.450 align:start position:0% you that have a manager you call this a 00:01:32.450 --> 00:01:35.680 align:start position:0% you that have a manager you call this a feasibility<00:01:33.230> study<00:01:33.470> I<00:01:34.390> know<00:01:35.390> it<00:01:35.540> isn't 00:01:35.680 --> 00:01:35.690 align:start position:0% feasibility study I know it isn't 00:01:35.690 --> 00:01:38.380 align:start position:0% feasibility study I know it isn't working<00:01:36.080> it<00:01:36.260> like<00:01:36.640> we<00:01:37.640> can<00:01:37.850> basically<00:01:38.060> and 00:01:38.380 --> 00:01:38.390 align:start position:0% working it like we can basically and 00:01:38.390 --> 00:01:39.940 align:start position:0% working it like we can basically and that's<00:01:38.479> the<00:01:38.870> basis<00:01:39.410> of<00:01:39.500> what<00:01:39.680> we'll<00:01:39.860> be 00:01:39.940 --> 00:01:39.950 align:start position:0% that's the basis of what we'll be 00:01:39.950 --> 00:01:41.219 align:start position:0% that's the basis of what we'll be talking<00:01:40.100> about<00:01:40.370> today 00:01:41.219 --> 00:01:41.229 align:start position:0% talking about today 00:01:41.229 --> 00:01:45.400 align:start position:0% talking about today Yuri<00:01:43.000> friend<00:01:44.000> of<00:01:44.060> mine<00:01:44.210> on<00:01:44.240> the<00:01:44.570> minim<00:01:45.170> team 00:01:45.400 --> 00:01:45.410 align:start position:0% Yuri friend of mine on the minim team 00:01:45.410 --> 00:01:47.980 align:start position:0% Yuri friend of mine on the minim team sort<00:01:46.340> of<00:01:46.460> started<00:01:46.790> this<00:01:46.880> idea<00:01:47.060> to<00:01:47.360> do<00:01:47.840> video 00:01:47.980 --> 00:01:47.990 align:start position:0% sort of started this idea to do video 00:01:47.990 --> 00:01:50.080 align:start position:0% sort of started this idea to do video tracks<00:01:48.350> in<00:01:48.590> this<00:01:48.920> brand-new<00:01:49.369> language<00:01:49.670> for 00:01:50.080 --> 00:01:50.090 align:start position:0% tracks in this brand-new language for 00:01:50.090 --> 00:01:52.990 align:start position:0% tracks in this brand-new language for men<00:01:50.650> sort<00:01:51.650> of<00:01:51.740> experimenting<00:01:52.430> with<00:01:52.580> expense 00:01:52.990 --> 00:01:53.000 align:start position:0% men sort of experimenting with expense 00:01:53.000 --> 00:01:56.040 align:start position:0% men sort of experimenting with expense to<00:01:53.540> nice<00:01:53.690> little<00:01:54.020> language<00:01:54.350> it<00:01:54.470> has<00:01:54.619> very<00:01:54.860> good 00:01:56.040 --> 00:01:56.050 align:start position:0% to nice little language it has very good 00:01:56.050 --> 00:02:00.120 align:start position:0% to nice little language it has very good programming<00:01:57.050> tricks<00:01:57.440> they<00:01:58.040> have<00:01:58.220> a<00:01:58.550> very<00:01:58.820> nice 00:02:00.120 --> 00:02:00.130 align:start position:0% programming tricks they have a very nice 00:02:00.130 --> 00:02:03.280 align:start position:0% programming tricks they have a very nice environment<00:02:01.130> for<00:02:01.759> a<00:02:01.820> programmer<00:02:02.240> and<00:02:02.540> at 00:02:03.280 --> 00:02:03.290 align:start position:0% environment for a programmer and at 00:02:03.290 --> 00:02:05.139 align:start position:0% environment for a programmer and at compile<00:02:03.740> time<00:02:03.770> translate<00:02:04.580> a<00:02:04.610> lot<00:02:04.850> of<00:02:04.940> things 00:02:05.139 --> 00:02:05.149 align:start position:0% compile time translate a lot of things 00:02:05.149 --> 00:02:08.410 align:start position:0% compile time translate a lot of things very<00:02:05.479> efficient<00:02:05.840> constructs<00:02:07.330> for<00:02:08.330> the 00:02:08.410 --> 00:02:08.420 align:start position:0% very efficient constructs for the 00:02:08.420 --> 00:02:12.970 align:start position:0% very efficient constructs for the computer<00:02:08.810> to<00:02:08.899> execute<00:02:09.640> right<00:02:11.830> the<00:02:12.830> other 00:02:12.970 --> 00:02:12.980 align:start position:0% computer to execute right the other 00:02:12.980 --> 00:02:14.860 align:start position:0% computer to execute right the other person<00:02:13.400> I<00:02:13.459> wanted<00:02:13.670> to<00:02:13.820> mention<00:02:13.970> is<00:02:14.209> all<00:02:14.570> the 00:02:14.860 --> 00:02:14.870 align:start position:0% person I wanted to mention is all the 00:02:14.870 --> 00:02:20.740 align:start position:0% person I wanted to mention is all the younger<00:02:15.290> it<00:02:15.500> wasn't<00:02:15.830> he<00:02:17.650> so<00:02:18.790> we<00:02:19.790> post<00:02:20.060> like<00:02:20.570> we 00:02:20.740 --> 00:02:20.750 align:start position:0% younger it wasn't he so we post like we 00:02:20.750 --> 00:02:22.120 align:start position:0% younger it wasn't he so we post like we posted<00:02:21.110> is<00:02:21.230> the<00:02:21.380> elevator<00:02:21.739> and<00:02:21.890> then<00:02:22.040> he 00:02:22.120 --> 00:02:22.130 align:start position:0% posted is the elevator and then he 00:02:22.130 --> 00:02:24.580 align:start position:0% posted is the elevator and then he started<00:02:22.430> like<00:02:22.610> if<00:02:23.470> communicating<00:02:24.470> in<00:02:24.560> the 00:02:24.580 --> 00:02:24.590 align:start position:0% started like if communicating in the 00:02:24.590 --> 00:02:26.350 align:start position:0% started like if communicating in the back<00:02:24.890> and<00:02:25.070> for<00:02:25.280> things<00:02:25.489> that<00:02:25.670> is<00:02:25.790> farther<00:02:26.150> than 00:02:26.350 --> 00:02:26.360 align:start position:0% back and for things that is farther than 00:02:26.360 --> 00:02:31.600 align:start position:0% back and for things that is farther than he<00:02:26.690> had<00:02:26.930> oh<00:02:29.260> like<00:02:30.260> that<00:02:30.530> so<00:02:30.890> together<00:02:31.280> we<00:02:31.430> get 00:02:31.600 --> 00:02:31.610 align:start position:0% he had oh like that so together we get 00:02:31.610 --> 00:02:36.070 align:start position:0% he had oh like that so together we get to<00:02:33.670> where<00:02:34.670> we<00:02:34.940> will<00:02:35.120> be<00:02:35.239> going<00:02:35.269> to<00:02:35.540> make<00:02:35.780> this 00:02:36.070 --> 00:02:36.080 align:start position:0% to where we will be going to make this 00:02:36.080 --> 00:02:43.740 align:start position:0% to where we will be going to make this thing<00:02:38.019> finally<00:02:39.019> we<00:02:39.440> have<00:02:40.090> the<00:02:41.090> project 00:02:43.740 --> 00:02:43.750 align:start position:0% 00:02:43.750 --> 00:02:45.880 align:start position:0% actually<00:02:44.750> - 00:02:45.880 --> 00:02:45.890 align:start position:0% actually - 00:02:45.890 --> 00:02:49.090 align:start position:0% actually - a<00:02:46.090> smart<00:02:47.090> contract<00:02:47.300> environment<00:02:48.110> we're 00:02:49.090 --> 00:02:49.100 align:start position:0% a smart contract environment we're 00:02:49.100 --> 00:02:50.650 align:start position:0% a smart contract environment we're experimenting<00:02:49.400> with<00:02:49.880> it<00:02:50.000> to<00:02:50.150> see<00:02:50.330> what<00:02:50.569> it 00:02:50.650 --> 00:02:50.660 align:start position:0% experimenting with it to see what it 00:02:50.660 --> 00:02:52.600 align:start position:0% experimenting with it to see what it would<00:02:50.810> look<00:02:50.870> like<00:02:51.020> parent<00:02:51.830> smart<00:02:52.100> contracts 00:02:52.600 --> 00:02:52.610 align:start position:0% would look like parent smart contracts 00:02:52.610 --> 00:02:56.170 align:start position:0% would look like parent smart contracts becoming<00:02:52.940> a<00:02:53.240> template<00:02:53.630> for<00:02:53.840> not<00:02:55.180> something 00:02:56.170 --> 00:02:56.180 align:start position:0% becoming a template for not something 00:02:56.180 --> 00:02:58.860 align:start position:0% becoming a template for not something you<00:02:56.240> should<00:02:56.270> totally<00:02:56.540> check<00:02:56.720> out<00:02:57.020> online<00:02:57.370> or 00:02:58.860 --> 00:02:58.870 align:start position:0% you should totally check out online or 00:02:58.870 --> 00:03:03.130 align:start position:0% you should totally check out online or there's<00:02:59.870> a<00:02:59.959> presentation<00:03:00.560> going<00:03:00.830> on<00:03:02.080> or<00:03:03.080> a 00:03:03.130 --> 00:03:03.140 align:start position:0% there's a presentation going on or a 00:03:03.140 --> 00:03:05.590 align:start position:0% there's a presentation going on or a workshop<00:03:03.620> with<00:03:03.890> Denmark's<00:03:04.340> team<00:03:05.060> from<00:03:05.360> all 00:03:05.590 --> 00:03:05.600 align:start position:0% workshop with Denmark's team from all 00:03:05.600 --> 00:03:07.420 align:start position:0% workshop with Denmark's team from all circumstance<00:03:06.200> they're<00:03:06.709> sort<00:03:06.890> of<00:03:06.980> presenting 00:03:07.420 --> 00:03:07.430 align:start position:0% circumstance they're sort of presenting 00:03:07.430 --> 00:03:08.680 align:start position:0% circumstance they're sort of presenting a<00:03:07.459> little<00:03:07.670> bit<00:03:07.760> about<00:03:07.940> how<00:03:08.150> you<00:03:08.209> can<00:03:08.450> deploy 00:03:08.680 --> 00:03:08.690 align:start position:0% a little bit about how you can deploy 00:03:08.690 --> 00:03:10.949 align:start position:0% a little bit about how you can deploy your<00:03:08.930> contract<00:03:09.470> some<00:03:09.620> Universal<00:03:10.100> mysterious 00:03:10.949 --> 00:03:10.959 align:start position:0% your contract some Universal mysterious 00:03:10.959 --> 00:03:16.630 align:start position:0% your contract some Universal mysterious mystical<00:03:11.959> stuff<00:03:14.830> all<00:03:15.830> right<00:03:15.860> so<00:03:16.130> where<00:03:16.310> are<00:03:16.340> we 00:03:16.630 --> 00:03:16.640 align:start position:0% mystical stuff all right so where are we 00:03:16.640 --> 00:03:18.360 align:start position:0% mystical stuff all right so where are we we're<00:03:16.790> talking<00:03:17.120> what<00:03:17.239> he<00:03:17.420> wasn't<00:03:17.630> here 00:03:18.360 --> 00:03:18.370 align:start position:0% we're talking what he wasn't here 00:03:18.370 --> 00:03:22.060 align:start position:0% we're talking what he wasn't here he<00:03:19.370> wasn't<00:03:19.580> one<00:03:19.790> developed<00:03:20.239> but<00:03:21.080> as<00:03:21.830> an 00:03:22.060 --> 00:03:22.070 align:start position:0% he wasn't one developed but as an 00:03:22.070 --> 00:03:24.640 align:start position:0% he wasn't one developed but as an alternative<00:03:22.640> for<00:03:22.940> it<00:03:23.030> there<00:03:23.209> one<00:03:23.650> execution 00:03:24.640 --> 00:03:24.650 align:start position:0% alternative for it there one execution 00:03:24.650 --> 00:03:27.280 align:start position:0% alternative for it there one execution and<00:03:24.980> may<00:03:25.100> get<00:03:25.310> there<00:03:25.550> into<00:03:25.760> execution<00:03:26.390> and<00:03:26.540> you 00:03:27.280 --> 00:03:27.290 align:start position:0% and may get there into execution and you 00:03:27.290 --> 00:03:28.570 align:start position:0% and may get there into execution and you know<00:03:27.410> that<00:03:27.590> goes<00:03:27.769> a<00:03:27.800> little<00:03:27.950> bit<00:03:28.190> back<00:03:28.400> and 00:03:28.570 --> 00:03:28.580 align:start position:0% know that goes a little bit back and 00:03:28.580 --> 00:03:31.920 align:start position:0% know that goes a little bit back and forth<00:03:28.640> whether<00:03:29.150> that<00:03:29.420> would<00:03:29.630> be<00:03:29.720> used<00:03:29.900> or<00:03:30.050> not 00:03:31.920 --> 00:03:31.930 align:start position:0% forth whether that would be used or not 00:03:31.930 --> 00:03:33.940 align:start position:0% forth whether that would be used or not for<00:03:32.930> the<00:03:33.050> purpose<00:03:33.440> of<00:03:33.560> this<00:03:33.709> presentation 00:03:33.940 --> 00:03:33.950 align:start position:0% for the purpose of this presentation 00:03:33.950 --> 00:03:38.229 align:start position:0% for the purpose of this presentation we'll<00:03:34.760> be<00:03:34.910> using<00:03:35.030> a<00:03:35.570> very<00:03:36.110> old<00:03:36.410> version<00:03:36.650> of<00:03:37.239> us 00:03:38.229 --> 00:03:38.239 align:start position:0% we'll be using a very old version of us 00:03:38.239 --> 00:03:41.100 align:start position:0% we'll be using a very old version of us and<00:03:38.480> one<00:03:38.720> that's<00:03:38.959> targeting<00:03:39.500> is<00:03:39.620> there<00:03:39.890> in<00:03:39.980> one 00:03:41.100 --> 00:03:41.110 align:start position:0% and one that's targeting is there in one 00:03:41.110 --> 00:03:43.570 align:start position:0% and one that's targeting is there in one any<00:03:42.110> end<00:03:42.350> of<00:03:42.440> the<00:03:42.530> minds<00:03:42.800> like<00:03:43.190> you<00:03:43.340> know<00:03:43.459> how 00:03:43.570 --> 00:03:43.580 align:start position:0% any end of the minds like you know how 00:03:43.580 --> 00:03:46.090 align:start position:0% any end of the minds like you know how to<00:03:43.640> be<00:03:43.850> in<00:03:43.880> supporting<00:03:44.600> what<00:03:45.170> contract<00:03:45.620> should 00:03:46.090 --> 00:03:46.100 align:start position:0% to be in supporting what contract should 00:03:46.100 --> 00:03:49.690 align:start position:0% to be in supporting what contract should be<00:03:46.160> able<00:03:46.340> to<00:03:46.550> do<00:03:47.200> how<00:03:48.200> to<00:03:48.230> access<00:03:48.530> the<00:03:49.010> air<00:03:49.610> in 00:03:49.690 --> 00:03:49.700 align:start position:0% be able to do how to access the air in 00:03:49.700 --> 00:03:53.180 align:start position:0% be able to do how to access the air in one<00:03:49.880> state<00:03:50.500> a<00:03:51.500> publicist 00:03:53.180 --> 00:03:53.190 align:start position:0% one state a publicist 00:03:53.190 --> 00:03:56.670 align:start position:0% one state a publicist and<00:03:54.190> what<00:03:54.490> sort<00:03:54.760> of<00:03:54.819> thought<00:03:55.120> of<00:03:55.240> as<00:03:55.390> a<00:03:55.680> gateway 00:03:56.670 --> 00:03:56.680 align:start position:0% and what sort of thought of as a gateway 00:03:56.680 --> 00:04:00.000 align:start position:0% and what sort of thought of as a gateway to<00:03:57.209> tutoring<00:03:58.209> water<00:03:58.510> and<00:03:58.780> so<00:03:59.020> what<00:03:59.770> of<00:03:59.890> the 00:04:00.000 --> 00:04:00.010 align:start position:0% to tutoring water and so what of the 00:04:00.010 --> 00:04:01.949 align:start position:0% to tutoring water and so what of the stuff<00:04:00.220> you'll<00:04:00.580> see<00:04:00.819> here<00:04:01.090> if<00:04:01.569> you're<00:04:01.780> familiar 00:04:01.949 --> 00:04:01.959 align:start position:0% stuff you'll see here if you're familiar 00:04:01.959 --> 00:04:04.050 align:start position:0% stuff you'll see here if you're familiar with<00:04:02.230> it<00:04:02.500> Sarah<00:04:02.709> one<00:04:02.950> you<00:04:03.100> probably<00:04:03.459> recognize 00:04:04.050 --> 00:04:04.060 align:start position:0% with it Sarah one you probably recognize 00:04:04.060 --> 00:04:09.210 align:start position:0% with it Sarah one you probably recognize like<00:04:04.330> the<00:04:04.650> commands<00:04:05.650> of<00:04:05.800> the<00:04:05.890> functions<00:04:08.220> how 00:04:09.210 --> 00:04:09.220 align:start position:0% like the commands of the functions how 00:04:09.220 --> 00:04:12.240 align:start position:0% like the commands of the functions how it<00:04:09.400> sort<00:04:09.580> of<00:04:09.670> looks<00:04:09.940> at<00:04:10.620> its<00:04:11.620> enormous<00:04:12.010> data 00:04:12.240 --> 00:04:12.250 align:start position:0% it sort of looks at its enormous data 00:04:12.250 --> 00:04:16.170 align:start position:0% it sort of looks at its enormous data and<00:04:12.430> so<00:04:12.580> on<00:04:13.500> it's<00:04:14.500> not<00:04:14.680> a<00:04:14.740> very<00:04:15.250> difficult<00:04:15.520> area 00:04:16.170 --> 00:04:16.180 align:start position:0% and so on it's not a very difficult area 00:04:16.180 --> 00:04:17.940 align:start position:0% and so on it's not a very difficult area to<00:04:16.480> written<00:04:16.989> that<00:04:17.140> there<00:04:17.320> are<00:04:17.410> tumors<00:04:17.769> to 00:04:17.940 --> 00:04:17.950 align:start position:0% to written that there are tumors to 00:04:17.950 --> 00:04:19.949 align:start position:0% to written that there are tumors to right<00:04:18.250> now<00:04:18.430> especially<00:04:18.730> exports<00:04:19.600> that<00:04:19.780> cause 00:04:19.949 --> 00:04:19.959 align:start position:0% right now especially exports that cause 00:04:19.959 --> 00:04:22.409 align:start position:0% right now especially exports that cause problems<00:04:20.320> and<00:04:20.500> then<00:04:20.680> maybe<00:04:21.489> something<00:04:22.060> like 00:04:22.409 --> 00:04:22.419 align:start position:0% problems and then maybe something like 00:04:22.419 --> 00:04:26.430 align:start position:0% problems and then maybe something like this<00:04:22.630> will<00:04:23.620> be<00:04:23.800> available<00:04:24.250> under<00:04:24.400> theory<00:04:25.440> in 00:04:26.430 --> 00:04:26.440 align:start position:0% this will be available under theory in 00:04:26.440 --> 00:04:28.490 align:start position:0% this will be available under theory in the<00:04:26.590> form<00:04:26.800> of<00:04:26.890> an<00:04:27.040> execution<00:04:27.430> environment 00:04:28.490 --> 00:04:28.500 align:start position:0% the form of an execution environment 00:04:28.500 --> 00:04:33.210 align:start position:0% the form of an execution environment like<00:04:29.500> that<00:04:29.710> to<00:04:30.460> be<00:04:30.610> in<00:04:30.669> the<00:04:30.760> same<00:04:32.130> but<00:04:33.130> it 00:04:33.210 --> 00:04:33.220 align:start position:0% like that to be in the same but it 00:04:33.220 --> 00:04:35.550 align:start position:0% like that to be in the same but it doesn't<00:04:33.520> really<00:04:33.610> matter<00:04:33.850> like<00:04:33.970> wasn't<00:04:34.540> one<00:04:35.470> of 00:04:35.550 --> 00:04:35.560 align:start position:0% doesn't really matter like wasn't one of 00:04:35.560 --> 00:04:37.050 align:start position:0% doesn't really matter like wasn't one of the<00:04:35.680> reasons<00:04:35.980> why<00:04:36.100> it<00:04:36.160> wasn't<00:04:36.370> as<00:04:36.580> interesting 00:04:37.050 --> 00:04:37.060 align:start position:0% the reasons why it wasn't as interesting 00:04:37.060 --> 00:04:40.940 align:start position:0% the reasons why it wasn't as interesting is<00:04:37.150> because<00:04:37.270> it's<00:04:37.570> this<00:04:37.750> type<00:04:39.090> generic<00:04:40.090> VM 00:04:40.940 --> 00:04:40.950 align:start position:0% is because it's this type generic VM 00:04:40.950 --> 00:04:43.140 align:start position:0% is because it's this type generic VM that's<00:04:41.950> being<00:04:42.190> explored<00:04:42.520> for<00:04:42.820> a<00:04:42.910> lot<00:04:43.030> of 00:04:43.140 --> 00:04:43.150 align:start position:0% that's being explored for a lot of 00:04:43.150 --> 00:04:45.659 align:start position:0% that's being explored for a lot of different<00:04:44.040> blockchain<00:04:45.040> so<00:04:45.280> whatever 00:04:45.659 --> 00:04:45.669 align:start position:0% different blockchain so whatever 00:04:45.669 --> 00:04:47.070 align:start position:0% different blockchain so whatever blockchain<00:04:46.090> you<00:04:46.180> happen<00:04:46.419> to<00:04:46.450> be<00:04:46.630> using<00:04:46.780> that 00:04:47.070 --> 00:04:47.080 align:start position:0% blockchain you happen to be using that 00:04:47.080 --> 00:04:49.890 align:start position:0% blockchain you happen to be using that is<00:04:47.169> targeting<00:04:47.680> was<00:04:48.490> in<00:04:48.730> this<00:04:48.970> discussion<00:04:49.510> that 00:04:49.890 --> 00:04:49.900 align:start position:0% is targeting was in this discussion that 00:04:49.900 --> 00:04:52.800 align:start position:0% is targeting was in this discussion that you're<00:04:50.830> optimizing<00:04:51.010> will<00:04:51.700> be<00:04:51.820> more<00:04:52.540> or<00:04:52.660> less 00:04:52.800 --> 00:04:52.810 align:start position:0% you're optimizing will be more or less 00:04:52.810 --> 00:05:00.240 align:start position:0% you're optimizing will be more or less the<00:04:52.960> same<00:04:54.210> and<00:04:55.770> I<00:04:57.690> mean<00:04:58.800> why<00:04:59.800> would<00:05:00.100> you<00:05:00.130> even 00:05:00.240 --> 00:05:00.250 align:start position:0% the same and I mean why would you even 00:05:00.250 --> 00:05:06.990 align:start position:0% the same and I mean why would you even go<00:05:00.970> here<00:05:02.430> well<00:05:04.500> on<00:05:05.500> the<00:05:05.890> theory<00:05:06.220> on<00:05:06.550> on<00:05:06.880> an 00:05:06.990 --> 00:05:07.000 align:start position:0% go here well on the theory on on an 00:05:07.000 --> 00:05:10.469 align:start position:0% go here well on the theory on on an abduction<00:05:07.300> right<00:05:07.690> storage<00:05:08.110> is<00:05:08.350> at<00:05:08.500> previous 00:05:10.469 --> 00:05:10.479 align:start position:0% abduction right storage is at previous 00:05:10.479 --> 00:05:13.140 align:start position:0% abduction right storage is at previous so<00:05:11.470> if<00:05:11.590> you<00:05:11.710> deploy<00:05:12.039> like<00:05:12.310> the<00:05:12.460> large<00:05:12.669> contract 00:05:13.140 --> 00:05:13.150 align:start position:0% so if you deploy like the large contract 00:05:13.150 --> 00:05:14.700 align:start position:0% so if you deploy like the large contract that's<00:05:13.300> bad<00:05:13.509> for<00:05:13.780> everybody<00:05:14.169> it's<00:05:14.289> bad<00:05:14.470> for 00:05:14.700 --> 00:05:14.710 align:start position:0% that's bad for everybody it's bad for 00:05:14.710 --> 00:05:16.740 align:start position:0% that's bad for everybody it's bad for your<00:05:14.830> own<00:05:14.889> base<00:05:15.250> plane<00:05:15.520> in<00:05:15.699> terms<00:05:15.910> of<00:05:16.120> cost<00:05:16.300> but 00:05:16.740 --> 00:05:16.750 align:start position:0% your own base plane in terms of cost but 00:05:16.750 --> 00:05:21.120 align:start position:0% your own base plane in terms of cost but for<00:05:16.990> users<00:05:17.410> to<00:05:17.590> cos<00:05:17.789> like<00:05:19.710> they'll<00:05:20.710> be<00:05:20.919> paying 00:05:21.120 --> 00:05:21.130 align:start position:0% for users to cos like they'll be paying 00:05:21.130 --> 00:05:23.070 align:start position:0% for users to cos like they'll be paying lots<00:05:21.310> of<00:05:21.460> gas<00:05:21.669> for<00:05:21.970> the<00:05:22.389> execution<00:05:22.930> was 00:05:23.070 --> 00:05:23.080 align:start position:0% lots of gas for the execution was 00:05:23.080 --> 00:05:32.460 align:start position:0% lots of gas for the execution was obviously<00:05:23.440> better<00:05:23.710> system<00:05:24.550> is<00:05:25.740> just<00:05:31.350> par<00:05:32.350> as 00:05:32.460 --> 00:05:32.470 align:start position:0% obviously better system is just par as 00:05:32.470 --> 00:05:33.300 align:start position:0% obviously better system is just par as he<00:05:32.590> hasn't<00:05:32.800> worked 00:05:33.300 --> 00:05:33.310 align:start position:0% he hasn't worked 00:05:33.310 --> 00:05:37.879 align:start position:0% he hasn't worked well<00:05:33.430> how<00:05:34.030> does<00:05:34.090> Weizen<00:05:34.539> work<00:05:35.620> first<00:05:36.490> of<00:05:36.669> all 00:05:37.879 --> 00:05:37.889 align:start position:0% well how does Weizen work first of all 00:05:37.889 --> 00:05:40.529 align:start position:0% well how does Weizen work first of all you<00:05:38.889> have<00:05:39.039> an<00:05:39.130> environment<00:05:39.430> in<00:05:40.180> which<00:05:40.330> your 00:05:40.529 --> 00:05:40.539 align:start position:0% you have an environment in which your 00:05:40.539 --> 00:05:44.249 align:start position:0% you have an environment in which your code<00:05:40.720> is<00:05:40.840> executing<00:05:41.440> them<00:05:41.590> in<00:05:41.800> sandbox<00:05:43.259> then 00:05:44.249 --> 00:05:44.259 align:start position:0% code is executing them in sandbox then 00:05:44.259 --> 00:05:46.529 align:start position:0% code is executing them in sandbox then you<00:05:44.410> have<00:05:44.590> your<00:05:44.800> contact<00:05:45.250> code<00:05:45.520> on<00:05:45.940> the<00:05:46.389> one 00:05:46.529 --> 00:05:46.539 align:start position:0% you have your contact code on the one 00:05:46.539 --> 00:05:48.689 align:start position:0% you have your contact code on the one silence<00:05:47.020> when<00:05:47.229> you<00:05:47.349> start<00:05:47.590> if<00:05:47.710> you<00:05:47.830> write<00:05:48.039> and 00:05:48.689 --> 00:05:48.699 align:start position:0% silence when you start if you write and 00:05:48.699 --> 00:05:49.999 align:start position:0% silence when you start if you write and then<00:05:48.910> the<00:05:49.030> environment<00:05:49.300> provides 00:05:49.999 --> 00:05:50.009 align:start position:0% then the environment provides 00:05:50.009 --> 00:05:52.439 align:start position:0% then the environment provides functionality<00:05:51.009> from<00:05:51.699> the<00:05:51.880> outside<00:05:52.210> world 00:05:52.439 --> 00:05:52.449 align:start position:0% functionality from the outside world 00:05:52.449 --> 00:05:53.040 align:start position:0% functionality from the outside world right 00:05:53.040 --> 00:05:53.050 align:start position:0% right 00:05:53.050 --> 00:05:54.900 align:start position:0% right that<00:05:53.229> might<00:05:53.410> be<00:05:53.620> if<00:05:54.370> you're<00:05:54.490> running<00:05:54.669> this 00:05:54.900 --> 00:05:54.910 align:start position:0% that might be if you're running this 00:05:54.910 --> 00:05:56.159 align:start position:0% that might be if you're running this that<00:05:55.150> if<00:05:55.360> you're<00:05:55.479> running<00:05:55.569> wasn't<00:05:56.050> in<00:05:56.110> the 00:05:56.159 --> 00:05:56.169 align:start position:0% that if you're running wasn't in the 00:05:56.169 --> 00:05:58.230 align:start position:0% that if you're running wasn't in the browser<00:05:56.379> for<00:05:56.530> example<00:05:56.819> that's<00:05:57.819> gonna<00:05:58.000> be 00:05:58.230 --> 00:05:58.240 align:start position:0% browser for example that's gonna be 00:05:58.240 --> 00:06:00.119 align:start position:0% browser for example that's gonna be access<00:05:58.930> to<00:05:59.110> the<00:05:59.169> JavaScript<00:05:59.710> world<00:05:59.830> on 00:06:00.119 --> 00:06:00.129 align:start position:0% access to the JavaScript world on 00:06:00.129 --> 00:06:03.960 align:start position:0% access to the JavaScript world on whatever<00:06:02.159> the<00:06:03.159> JavaScript<00:06:03.759> code 00:06:03.960 --> 00:06:03.970 align:start position:0% whatever the JavaScript code 00:06:03.970 --> 00:06:06.450 align:start position:0% whatever the JavaScript code instantiating<00:06:04.720> there<00:06:05.020> wasn't<00:06:05.379> it<00:06:05.590> has<00:06:05.860> given 00:06:06.450 --> 00:06:06.460 align:start position:0% instantiating there wasn't it has given 00:06:06.460 --> 00:06:07.860 align:start position:0% instantiating there wasn't it has given you<00:06:06.550> to<00:06:06.580> play<00:06:06.909> with<00:06:07.090> that<00:06:07.240> might<00:06:07.449> give<00:06:07.599> the<00:06:07.690> Dom 00:06:07.860 --> 00:06:07.870 align:start position:0% you to play with that might give the Dom 00:06:07.870 --> 00:06:12.710 align:start position:0% you to play with that might give the Dom that<00:06:07.900> make<00:06:08.349> you<00:06:08.470> like<00:06:09.240> UI<00:06:10.240> campus<00:06:10.690> like<00:06:11.680> this 00:06:12.710 --> 00:06:12.720 align:start position:0% that make you like UI campus like this 00:06:12.720 --> 00:06:16.230 align:start position:0% that make you like UI campus like this if<00:06:13.720> you're<00:06:13.900> doing<00:06:14.460> many<00:06:15.460> more<00:06:15.669> modern<00:06:16.000> stuff 00:06:16.230 --> 00:06:16.240 align:start position:0% if you're doing many more modern stuff 00:06:16.240 --> 00:06:19.740 align:start position:0% if you're doing many more modern stuff to<00:06:16.539> standard<00:06:17.470> in<00:06:17.590> Facebook<00:06:18.190> buzzing<00:06:18.750> which 00:06:19.740 --> 00:06:19.750 align:start position:0% to standard in Facebook buzzing which 00:06:19.750 --> 00:06:21.719 align:start position:0% to standard in Facebook buzzing which gives<00:06:19.960> you<00:06:20.080> access<00:06:20.259> to<00:06:20.409> files<00:06:20.740> it's<00:06:21.400> basically 00:06:21.719 --> 00:06:21.729 align:start position:0% gives you access to files it's basically 00:06:21.729 --> 00:06:23.189 align:start position:0% gives you access to files it's basically the<00:06:21.940> interface<00:06:22.300> it's<00:06:22.479> a<00:06:22.539> little<00:06:22.900> bit<00:06:23.050> like 00:06:23.189 --> 00:06:23.199 align:start position:0% the interface it's a little bit like 00:06:23.199 --> 00:06:24.570 align:start position:0% the interface it's a little bit like what<00:06:23.440> what<00:06:23.800> you<00:06:23.919> would<00:06:24.039> expect<00:06:24.400> on<00:06:24.520> your 00:06:24.570 --> 00:06:24.580 align:start position:0% what what you would expect on your 00:06:24.580 --> 00:06:26.129 align:start position:0% what what you would expect on your current<00:06:25.030> library<00:06:25.210> or<00:06:25.479> your<00:06:25.599> sub<00:06:25.780> library 00:06:26.129 --> 00:06:26.139 align:start position:0% current library or your sub library 00:06:26.139 --> 00:06:28.680 align:start position:0% current library or your sub library right<00:06:26.349> that's<00:06:27.069> the<00:06:27.220> interface<00:06:27.490> around<00:06:28.419> there 00:06:28.680 --> 00:06:28.690 align:start position:0% right that's the interface around there 00:06:28.690 --> 00:06:32.189 align:start position:0% right that's the interface around there so<00:06:28.930> you<00:06:29.560> as<00:06:29.710> my<00:06:29.949> particular<00:06:30.960> defines<00:06:31.960> these 00:06:32.189 --> 00:06:32.199 align:start position:0% so you as my particular defines these 00:06:32.199 --> 00:06:35.969 align:start position:0% so you as my particular defines these functions<00:06:33.159> which<00:06:33.759> are<00:06:33.940> basically<00:06:34.979> for 00:06:35.969 --> 00:06:35.979 align:start position:0% functions which are basically for 00:06:35.979 --> 00:06:38.370 align:start position:0% functions which are basically for example<00:06:36.389> comes<00:06:37.389> straight<00:06:37.780> from<00:06:37.840> the<00:06:38.050> via 00:06:38.370 --> 00:06:38.380 align:start position:0% example comes straight from the via 00:06:38.380 --> 00:06:41.339 align:start position:0% example comes straight from the via right<00:06:38.650> storage<00:06:39.340> they<00:06:40.180> asked<00:06:40.419> for<00:06:40.449> Islamic 00:06:41.339 --> 00:06:41.349 align:start position:0% right storage they asked for Islamic 00:06:41.349 --> 00:06:44.159 align:start position:0% right storage they asked for Islamic install<00:06:41.970> so<00:06:42.970> it<00:06:43.090> has<00:06:43.240> like<00:06:43.389> the<00:06:43.539> function<00:06:43.960> for 00:06:44.159 --> 00:06:44.169 align:start position:0% install so it has like the function for 00:06:44.169 --> 00:06:47.600 align:start position:0% install so it has like the function for everything<00:06:44.699> in<00:06:45.699> EVM<00:06:46.270> that<00:06:46.539> is<00:06:46.630> not<00:06:46.810> present<00:06:47.110> in 00:06:47.600 --> 00:06:47.610 align:start position:0% everything in EVM that is not present in 00:06:47.610 --> 00:06:51.330 align:start position:0% everything in EVM that is not present in wasn't<00:06:48.610> native<00:06:49.620> and<00:06:50.620> you<00:06:50.710> could<00:06:50.860> access<00:06:51.159> to 00:06:51.330 --> 00:06:51.340 align:start position:0% wasn't native and you could access to 00:06:51.340 --> 00:06:53.670 align:start position:0% wasn't native and you could access to this<00:06:51.460> from<00:06:51.900> from<00:06:52.900> inside<00:06:53.259> here<00:06:53.440> within 00:06:53.670 --> 00:06:53.680 align:start position:0% this from from inside here within 00:06:53.680 --> 00:06:56.200 align:start position:0% this from from inside here within sandbox<00:06:54.190> or<00:06:54.370> conduits 00:06:56.200 --> 00:06:56.210 align:start position:0% sandbox or conduits 00:06:56.210 --> 00:06:58.370 align:start position:0% sandbox or conduits [Music] 00:06:58.370 --> 00:06:58.380 align:start position:0% [Music] 00:06:58.380 --> 00:07:01.290 align:start position:0% [Music] the<00:06:59.380> contract<00:07:00.099> will<00:07:00.340> be<00:07:00.370> optimizing<00:07:00.880> today's 00:07:01.290 --> 00:07:01.300 align:start position:0% the contract will be optimizing today's 00:07:01.300 --> 00:07:04.430 align:start position:0% the contract will be optimizing today's like<00:07:01.900> this<00:07:02.110> very<00:07:02.469> small<00:07:02.880> and<00:07:03.880> simple 00:07:04.430 --> 00:07:04.440 align:start position:0% like this very small and simple 00:07:04.440 --> 00:07:07.320 align:start position:0% like this very small and simple WRC<00:07:05.440> 20<00:07:05.949> was<00:07:06.159> a<00:07:06.190> challenge<00:07:06.639> that 00:07:07.320 --> 00:07:07.330 align:start position:0% WRC 20 was a challenge that 00:07:07.330 --> 00:07:09.990 align:start position:0% WRC 20 was a challenge that the<00:07:07.509> poster<00:07:07.960> a<00:07:07.990> year<00:07:08.229> ago<00:07:08.409> it's<00:07:09.400> very<00:07:09.639> like<00:07:09.849> the 00:07:09.990 --> 00:07:10.000 align:start position:0% the poster a year ago it's very like the 00:07:10.000 --> 00:07:13.649 align:start position:0% the poster a year ago it's very like the token<00:07:10.960> contracted<00:07:11.680> transfer<00:07:12.580> object<00:07:13.389> you<00:07:13.479> can 00:07:13.649 --> 00:07:13.659 align:start position:0% token contracted transfer object you can 00:07:13.659 --> 00:07:16.980 align:start position:0% token contracted transfer object you can see<00:07:14.500> that<00:07:14.680> their<00:07:14.860> balance<00:07:15.129> function<00:07:15.460> and<00:07:16.270> your 00:07:16.980 --> 00:07:16.990 align:start position:0% see that their balance function and your 00:07:16.990 --> 00:07:20.820 align:start position:0% see that their balance function and your transfer<00:07:17.469> function<00:07:17.830> right<00:07:19.710> this<00:07:20.710> is 00:07:20.820 --> 00:07:20.830 align:start position:0% transfer function right this is 00:07:20.830 --> 00:07:22.529 align:start position:0% transfer function right this is basically<00:07:21.159> an<00:07:21.340> example<00:07:21.460> of<00:07:21.909> this<00:07:22.060> new<00:07:22.300> play 00:07:22.529 --> 00:07:22.539 align:start position:0% basically an example of this new play 00:07:22.539 --> 00:07:24.149 align:start position:0% basically an example of this new play contract<00:07:22.960> environment<00:07:23.469> that<00:07:23.590> we're<00:07:23.800> talking 00:07:24.149 --> 00:07:24.159 align:start position:0% contract environment that we're talking 00:07:24.159 --> 00:07:26.279 align:start position:0% contract environment that we're talking about<00:07:24.430> but<00:07:24.729> this<00:07:24.879> is<00:07:25.030> a<00:07:25.060> pretty<00:07:25.569> alpha<00:07:26.110> 3 00:07:26.279 --> 00:07:26.289 align:start position:0% about but this is a pretty alpha 3 00:07:26.289 --> 00:07:28.890 align:start position:0% about but this is a pretty alpha 3 degree<00:07:26.740> version<00:07:27.360> there's<00:07:28.360> no<00:07:28.479> experimental 00:07:28.890 --> 00:07:28.900 align:start position:0% degree version there's no experimental 00:07:28.900 --> 00:07:31.200 align:start position:0% degree version there's no experimental witness<00:07:29.469> and<00:07:29.650> that's<00:07:29.830> not<00:07:30.069> with<00:07:30.250> it<00:07:30.370> if<00:07:31.060> you 00:07:31.200 --> 00:07:31.210 align:start position:0% witness and that's not with it if you 00:07:31.210 --> 00:07:33.350 align:start position:0% witness and that's not with it if you look<00:07:31.419> at<00:07:31.750> viper<00:07:32.020> it's<00:07:32.710> a<00:07:32.800> little<00:07:32.979> bit<00:07:33.069> similar 00:07:33.350 --> 00:07:33.360 align:start position:0% look at viper it's a little bit similar 00:07:33.360 --> 00:07:38.520 align:start position:0% look at viper it's a little bit similar so<00:07:34.360> you<00:07:34.449> have<00:07:34.659> like<00:07:36.060> functions<00:07:37.060> then<00:07:37.530> Lazarus 00:07:38.520 --> 00:07:38.530 align:start position:0% so you have like functions then Lazarus 00:07:38.530 --> 00:07:45.409 align:start position:0% so you have like functions then Lazarus and<00:07:38.770> eternal<00:07:39.219> you<00:07:39.340> like<00:07:40.229> violence<00:07:43.229> you<00:07:44.229> can<00:07:44.289> do 00:07:45.409 --> 00:07:45.419 align:start position:0% and eternal you like violence you can do 00:07:45.419 --> 00:07:58.589 align:start position:0% and eternal you like violence you can do comparisons<00:07:46.419> and<00:07:46.750> chance<00:07:56.400> but<00:07:57.400> when<00:07:58.270> we<00:07:58.419> give 00:07:58.589 --> 00:07:58.599 align:start position:0% comparisons and chance but when we give 00:07:58.599 --> 00:08:00.360 align:start position:0% comparisons and chance but when we give it<00:07:58.629> to<00:07:58.779> the<00:07:58.960> compiler<00:07:59.319> and<00:08:00.039> we'll<00:08:00.219> go<00:08:00.340> through 00:08:00.360 --> 00:08:00.370 align:start position:0% it to the compiler and we'll go through 00:08:00.370 --> 00:08:04.760 align:start position:0% it to the compiler and we'll go through this<00:08:00.699> pipeline<00:08:01.090> in<00:08:01.419> multiple<00:08:01.900> stages<00:08:02.139> right 00:08:04.760 --> 00:08:04.770 align:start position:0% 00:08:04.770 --> 00:08:12.089 align:start position:0% so<00:08:06.569> we<00:08:07.569> start<00:08:07.779> with<00:08:07.990> your<00:08:10.770> parson<00:08:11.770> pointing 00:08:12.089 --> 00:08:12.099 align:start position:0% so we start with your parson pointing 00:08:12.099 --> 00:08:14.570 align:start position:0% so we start with your parson pointing right<00:08:12.250> the<00:08:12.940> first<00:08:13.150> thing<00:08:13.330> that<00:08:13.360> happens 00:08:14.570 --> 00:08:14.580 align:start position:0% right the first thing that happens 00:08:14.580 --> 00:08:17.000 align:start position:0% right the first thing that happens and<00:08:14.670> then<00:08:14.880> ladder<00:08:15.500> and<00:08:16.500> the<00:08:16.710> GNU<00:08:16.860> Compiler 00:08:17.000 --> 00:08:17.010 align:start position:0% and then ladder and the GNU Compiler 00:08:17.010 --> 00:08:20.800 align:start position:0% and then ladder and the GNU Compiler expensive<00:08:17.910> in<00:08:18.030> that<00:08:18.330> peashooter<00:08:19.140> very<00:08:19.710> music 00:08:20.800 --> 00:08:20.810 align:start position:0% expensive in that peashooter very music 00:08:20.810 --> 00:08:23.390 align:start position:0% expensive in that peashooter very music macros<00:08:21.810> are<00:08:21.990> their<00:08:22.230> basic<00:08:22.380> it<00:08:22.710> compiled<00:08:23.100> and 00:08:23.390 --> 00:08:23.400 align:start position:0% macros are their basic it compiled and 00:08:23.400 --> 00:08:25.400 align:start position:0% macros are their basic it compiled and there's<00:08:24.240> a<00:08:24.270> bunch<00:08:24.420> of<00:08:24.600> code<00:08:24.780> executes<00:08:25.380> that 00:08:25.400 --> 00:08:25.410 align:start position:0% there's a bunch of code executes that 00:08:25.410 --> 00:08:27.440 align:start position:0% there's a bunch of code executes that explains<00:08:25.830> it<00:08:26.100> in<00:08:26.220> different<00:08:26.370> slightly<00:08:27.150> more 00:08:27.440 --> 00:08:27.450 align:start position:0% explains it in different slightly more 00:08:27.450 --> 00:08:30.440 align:start position:0% explains it in different slightly more primitive<00:08:28.670> constructs<00:08:29.670> in<00:08:29.880> the<00:08:29.970> language 00:08:30.440 --> 00:08:30.450 align:start position:0% primitive constructs in the language 00:08:30.450 --> 00:08:33.860 align:start position:0% primitive constructs in the language right<00:08:31.670> and<00:08:32.670> you<00:08:32.820> access<00:08:33.180> this<00:08:33.300> library<00:08:33.570> that 00:08:33.860 --> 00:08:33.870 align:start position:0% right and you access this library that 00:08:33.870 --> 00:08:35.630 align:start position:0% right and you access this library that we<00:08:34.020> were<00:08:34.080> talking<00:08:34.290> about<00:08:34.470> the<00:08:34.830> caldera<00:08:35.400> coffee 00:08:35.630 --> 00:08:35.640 align:start position:0% we were talking about the caldera coffee 00:08:35.640 --> 00:08:41.000 align:start position:0% we were talking about the caldera coffee and<00:08:35.880> so<00:08:36.090> on<00:08:38.660> then<00:08:39.660> it<00:08:39.990> goes<00:08:40.200> into<00:08:40.380> the<00:08:40.530> compiler 00:08:41.000 --> 00:08:41.010 align:start position:0% and so on then it goes into the compiler 00:08:41.010 --> 00:08:45.490 align:start position:0% and so on then it goes into the compiler ast<00:08:41.490> like<00:08:42.240> that's<00:08:42.830> my<00:08:43.830> Heartland<00:08:44.430> right 00:08:45.490 --> 00:08:45.500 align:start position:0% ast like that's my Heartland right 00:08:45.500 --> 00:08:48.050 align:start position:0% ast like that's my Heartland right the<00:08:46.500> language<00:08:46.950> will<00:08:47.220> do<00:08:47.640> a<00:08:47.670> little<00:08:47.910> bit<00:08:48.030> of 00:08:48.050 --> 00:08:48.060 align:start position:0% the language will do a little bit of 00:08:48.060 --> 00:08:51.890 align:start position:0% the language will do a little bit of processing<00:08:48.720> tried<00:08:49.290> to<00:08:49.410> fight<00:08:49.620> her<00:08:50.630> cases<00:08:51.630> for 00:08:51.890 --> 00:08:51.900 align:start position:0% processing tried to fight her cases for 00:08:51.900 --> 00:08:53.540 align:start position:0% processing tried to fight her cases for optimization<00:08:52.380> of<00:08:52.590> a<00:08:52.710> message<00:08:53.070> that<00:08:53.100> would<00:08:53.400> be 00:08:53.540 --> 00:08:53.550 align:start position:0% optimization of a message that would be 00:08:53.550 --> 00:08:56.240 align:start position:0% optimization of a message that would be a<00:08:53.580> and<00:08:54.390> a<00:08:54.810> little<00:08:54.930> B<00:08:55.080> and<00:08:55.260> in<00:08:55.470> turn<00:08:55.680> has<00:08:55.920> its<00:08:56.070> own 00:08:56.240 --> 00:08:56.250 align:start position:0% a and a little B and in turn has its own 00:08:56.250 --> 00:08:58.040 align:start position:0% a and a little B and in turn has its own intermediate<00:08:57.150> representation<00:08:57.900> and 00:08:58.040 --> 00:08:58.050 align:start position:0% intermediate representation and 00:08:58.050 --> 00:09:03.260 align:start position:0% intermediate representation and optimizations<00:09:00.830> wasn't<00:09:01.830> that<00:09:02.640> wasn't<00:09:02.880> as<00:09:03.150> this 00:09:03.260 --> 00:09:03.270 align:start position:0% optimizations wasn't that wasn't as this 00:09:03.270 --> 00:09:08.990 align:start position:0% optimizations wasn't that wasn't as this instruction<00:09:03.840> set<00:09:04.050> that<00:09:05.840> is<00:09:07.760> executed<00:09:08.760> by<00:09:08.940> the 00:09:08.990 --> 00:09:09.000 align:start position:0% instruction set that is executed by the 00:09:09.000 --> 00:09:11.720 align:start position:0% instruction set that is executed by the Basel<00:09:09.660> environment<00:09:10.350> later<00:09:10.500> on<00:09:10.710> and<00:09:11.130> there 00:09:11.720 --> 00:09:11.730 align:start position:0% Basel environment later on and there 00:09:11.730 --> 00:09:14.270 align:start position:0% Basel environment later on and there will<00:09:11.940> be<00:09:11.970> one<00:09:12.630> more<00:09:12.770> translation<00:09:13.770> into<00:09:14.190> the 00:09:14.270 --> 00:09:14.280 align:start position:0% will be one more translation into the 00:09:14.280 --> 00:09:26.250 align:start position:0% will be one more translation into the native<00:09:14.490> instruction<00:09:15.120> set<00:09:15.300> of<00:09:15.420> your<00:09:20.870> father 00:09:26.250 --> 00:09:26.260 align:start position:0% 00:09:26.260 --> 00:09:29.020 align:start position:0% and<00:09:27.260> every<00:09:27.680> single<00:09:27.890> stage<00:09:28.280> with<00:09:28.550> when<00:09:28.880> you're 00:09:29.020 --> 00:09:29.030 align:start position:0% and every single stage with when you're 00:09:29.030 --> 00:09:31.270 align:start position:0% and every single stage with when you're optimizing<00:09:29.230> something<00:09:30.230> there<00:09:31.070> is<00:09:31.160> like 00:09:31.270 --> 00:09:31.280 align:start position:0% optimizing something there is like 00:09:31.280 --> 00:09:35.230 align:start position:0% optimizing something there is like opportunity<00:09:32.150> to<00:09:33.140> save<00:09:34.010> either<00:09:34.310> time<00:09:34.700> or<00:09:34.730> space 00:09:35.230 --> 00:09:35.240 align:start position:0% opportunity to save either time or space 00:09:35.240 --> 00:09:38.700 align:start position:0% opportunity to save either time or space or<00:09:35.600> whatever<00:09:35.780> it<00:09:36.050> is<00:09:36.080> you're<00:09:36.350> optimizing<00:09:36.710> for 00:09:38.700 --> 00:09:38.710 align:start position:0% or whatever it is you're optimizing for 00:09:38.710 --> 00:09:41.560 align:start position:0% or whatever it is you're optimizing for today<00:09:39.710> we'll<00:09:39.980> be<00:09:40.130> talking<00:09:40.300> mostly<00:09:41.300> about 00:09:41.560 --> 00:09:41.570 align:start position:0% today we'll be talking mostly about 00:09:41.570 --> 00:09:43.180 align:start position:0% today we'll be talking mostly about space<00:09:41.990> this<00:09:42.290> is<00:09:42.410> just<00:09:42.650> because<00:09:42.890> I<00:09:42.980> want<00:09:43.130> to 00:09:43.180 --> 00:09:43.190 align:start position:0% space this is just because I want to 00:09:43.190 --> 00:09:44.950 align:start position:0% space this is just because I want to scope<00:09:44.030> this<00:09:44.270> presentation 00:09:44.950 --> 00:09:44.960 align:start position:0% scope this presentation 00:09:44.960 --> 00:09:47.170 align:start position:0% scope this presentation yeah<00:09:45.140> and<00:09:45.800> you<00:09:45.890> usually<00:09:46.100> like<00:09:46.370> it<00:09:46.520> wasn't<00:09:46.730> in 00:09:47.170 --> 00:09:47.180 align:start position:0% yeah and you usually like it wasn't in 00:09:47.180 --> 00:09:49.240 align:start position:0% yeah and you usually like it wasn't in the<00:09:47.420> last<00:09:48.080> books<00:09:48.380> like<00:09:48.620> Dean<00:09:49.100> thought 00:09:49.240 --> 00:09:49.250 align:start position:0% the last books like Dean thought 00:09:49.250 --> 00:09:51.250 align:start position:0% the last books like Dean thought generally<00:09:49.790> we'll<00:09:49.940> see<00:09:50.030> wasn't<00:09:50.450> or<00:09:50.630> I<00:09:50.990> mean 00:09:51.250 --> 00:09:51.260 align:start position:0% generally we'll see wasn't or I mean 00:09:51.260 --> 00:09:53.890 align:start position:0% generally we'll see wasn't or I mean uses<00:09:51.860> WRC<00:09:52.730> when<00:09:52.970> it<00:09:53.120> going<00:09:53.300> to<00:09:53.450> be<00:09:53.540> like<00:09:53.750> II 00:09:53.890 --> 00:09:53.900 align:start position:0% uses WRC when it going to be like II 00:09:53.900 --> 00:09:56.500 align:start position:0% uses WRC when it going to be like II wasn't<00:09:54.080> corporately<00:09:54.910> yeah<00:09:55.940> so<00:09:56.210> you<00:09:56.330> go<00:09:56.480> right 00:09:56.500 --> 00:09:56.510 align:start position:0% wasn't corporately yeah so you go right 00:09:56.510 --> 00:09:58.900 align:start position:0% wasn't corporately yeah so you go right there<00:09:56.660> one<00:09:57.020> thing<00:09:57.350> I<00:09:57.650> think<00:09:58.310> you<00:09:58.400> can<00:09:58.640> execute 00:09:58.900 --> 00:09:58.910 align:start position:0% there one thing I think you can execute 00:09:58.910 --> 00:10:00.640 align:start position:0% there one thing I think you can execute discovered<00:09:59.480> in<00:09:59.570> the<00:09:59.660> browser<00:09:59.870> or<00:10:00.410> you<00:10:00.500> can 00:10:00.640 --> 00:10:00.650 align:start position:0% discovered in the browser or you can 00:10:00.650 --> 00:10:02.950 align:start position:0% discovered in the browser or you can execute<00:10:01.150> like<00:10:02.150> you<00:10:02.300> could<00:10:02.480> write<00:10:02.630> this<00:10:02.780> by 00:10:02.950 --> 00:10:02.960 align:start position:0% execute like you could write this by 00:10:02.960 --> 00:10:08.350 align:start position:0% execute like you could write this by hand<00:10:03.200> side<00:10:03.650> yeah 00:10:08.350 --> 00:10:08.360 align:start position:0% 00:10:08.360 --> 00:10:17.110 align:start position:0% like<00:10:08.750> he<00:10:08.930> wasn't<00:10:09.670> what's<00:10:10.670> no<00:10:10.850> he<00:10:11.000> was<00:10:15.910> yes<00:10:16.910> he 00:10:17.110 --> 00:10:17.120 align:start position:0% like he wasn't what's no he was yes he 00:10:17.120 --> 00:10:18.940 align:start position:0% like he wasn't what's no he was yes he wasn't<00:10:17.480> defined<00:10:17.720> the<00:10:17.930> visit<00:10:18.590> to<00:10:18.710> the<00:10:18.770> library 00:10:18.940 --> 00:10:18.950 align:start position:0% wasn't defined the visit to the library 00:10:18.950 --> 00:10:26.560 align:start position:0% wasn't defined the visit to the library and<00:10:19.460> you<00:10:19.580> know<00:10:19.910> semantics<00:10:20.390> outside<00:10:20.840> wasn't<00:10:25.570> so 00:10:26.560 --> 00:10:26.570 align:start position:0% and you know semantics outside wasn't so 00:10:26.570 --> 00:10:28.390 align:start position:0% and you know semantics outside wasn't so just<00:10:27.050> to<00:10:27.140> give<00:10:27.350> you<00:10:27.440> an<00:10:27.500> idea<00:10:27.830> of<00:10:27.890> what<00:10:28.070> it<00:10:28.160> what 00:10:28.390 --> 00:10:28.400 align:start position:0% just to give you an idea of what it what 00:10:28.400 --> 00:10:32.260 align:start position:0% just to give you an idea of what it what this<00:10:28.550> looks<00:10:28.790> like<00:10:28.880> right<00:10:30.580> the<00:10:31.580> first<00:10:31.790> stage<00:10:32.090> of 00:10:32.260 --> 00:10:32.270 align:start position:0% this looks like right the first stage of 00:10:32.270 --> 00:10:35.890 align:start position:0% this looks like right the first stage of the<00:10:32.540> pipeline<00:10:33.370> we<00:10:34.370> take<00:10:34.550> your<00:10:34.730> coat<00:10:34.970> and<00:10:35.330> we 00:10:35.890 --> 00:10:35.900 align:start position:0% the pipeline we take your coat and we 00:10:35.900 --> 00:10:37.600 align:start position:0% the pipeline we take your coat and we sort<00:10:36.110> of<00:10:36.140> covered<00:10:36.350> these<00:10:36.830> low-level<00:10:37.220> calls 00:10:37.600 --> 00:10:37.610 align:start position:0% sort of covered these low-level calls 00:10:37.610 --> 00:10:41.380 align:start position:0% sort of covered these low-level calls right<00:10:38.240> and<00:10:39.130> why<00:10:40.130> would<00:10:40.370> you<00:10:40.400> use<00:10:40.490> the<00:10:41.210> higher 00:10:41.380 --> 00:10:41.390 align:start position:0% right and why would you use the higher 00:10:41.390 --> 00:10:42.489 align:start position:0% right and why would you use the higher level<00:10:41.750> thing 00:10:42.489 --> 00:10:42.499 align:start position:0% level thing 00:10:42.499 --> 00:10:46.869 align:start position:0% level thing Odin<00:10:43.699> they're<00:10:44.239> like<00:10:44.389> the<00:10:44.569> experience<00:10:45.609> that<00:10:46.609> we 00:10:46.869 --> 00:10:46.879 align:start position:0% Odin they're like the experience that we 00:10:46.879 --> 00:10:51.999 align:start position:0% Odin they're like the experience that we as<00:10:47.119> the<00:10:49.119> maintain<00:10:50.119> their<00:10:50.919> environments<00:10:51.919> that 00:10:51.999 --> 00:10:52.009 align:start position:0% as the maintain their environments that 00:10:52.009 --> 00:10:53.679 align:start position:0% as the maintain their environments that we<00:10:52.129> take<00:10:52.339> all<00:10:52.519> these<00:10:52.639> organizations<00:10:53.389> that<00:10:53.509> we 00:10:53.679 --> 00:10:53.689 align:start position:0% we take all these organizations that we 00:10:53.689 --> 00:10:55.479 align:start position:0% we take all these organizations that we figure<00:10:53.989> out<00:10:54.049> on<00:10:54.229> the<00:10:54.319> story<00:10:54.589> tragically<00:10:55.099> to 00:10:55.479 --> 00:10:55.489 align:start position:0% figure out on the story tragically to 00:10:55.489 --> 00:10:56.979 align:start position:0% figure out on the story tragically to this<00:10:55.639> conservation<00:10:56.059> rights<00:10:56.479> but<00:10:56.659> they<00:10:56.809> don't 00:10:56.979 --> 00:10:56.989 align:start position:0% this conservation rights but they don't 00:10:56.989 --> 00:10:59.769 align:start position:0% this conservation rights but they don't want<00:10:57.139> to<00:10:57.229> bother<00:10:57.379> this<00:10:58.279> is<00:10:58.459> the<00:10:58.639> premise<00:10:59.539> of 00:10:59.769 --> 00:10:59.779 align:start position:0% want to bother this is the premise of 00:10:59.779 --> 00:11:01.359 align:start position:0% want to bother this is the premise of why<00:10:59.959> you're<00:11:00.169> using<00:11:00.409> a<00:11:00.619> high-level<00:11:00.919> language 00:11:01.359 --> 00:11:01.369 align:start position:0% why you're using a high-level language 00:11:01.369 --> 00:11:06.129 align:start position:0% why you're using a high-level language instead<00:11:01.819> of<00:11:03.609> stuff<00:11:04.609> so<00:11:04.729> you<00:11:04.819> can<00:11:04.879> see<00:11:05.119> here<00:11:05.299> the 00:11:06.129 --> 00:11:06.139 align:start position:0% instead of stuff so you can see here the 00:11:06.139 --> 00:11:08.859 align:start position:0% instead of stuff so you can see here the transfer<00:11:06.769> function<00:11:07.509> previous<00:11:08.509> think<00:11:08.719> was 00:11:08.859 --> 00:11:08.869 align:start position:0% transfer function previous think was 00:11:08.869 --> 00:11:10.899 align:start position:0% transfer function previous think was just<00:11:09.079> like<00:11:09.229> one<00:11:09.439> line<00:11:09.649> carry<00:11:10.009> its<00:11:10.309> expanded 00:11:10.899 --> 00:11:10.909 align:start position:0% just like one line carry its expanded 00:11:10.909 --> 00:11:12.699 align:start position:0% just like one line carry its expanded into<00:11:11.179> a<00:11:11.299> alright<00:11:11.989> we're<00:11:12.139> going<00:11:12.259> to<00:11:12.319> check<00:11:12.499> if 00:11:12.699 --> 00:11:12.709 align:start position:0% into a alright we're going to check if 00:11:12.709 --> 00:11:15.339 align:start position:0% into a alright we're going to check if we<00:11:12.889> have<00:11:13.009> enough<00:11:13.279> Paul<00:11:13.939> later<00:11:14.179> we're<00:11:15.169> gonna 00:11:15.339 --> 00:11:15.349 align:start position:0% we have enough Paul later we're gonna 00:11:15.349 --> 00:11:16.809 align:start position:0% we have enough Paul later we're gonna get<00:11:15.499> the<00:11:15.649> color<00:11:15.919> we're<00:11:16.399> going<00:11:16.549> to<00:11:16.639> get<00:11:16.699> the 00:11:16.809 --> 00:11:16.819 align:start position:0% get the color we're going to get the 00:11:16.819 --> 00:11:19.899 align:start position:0% get the color we're going to get the recipient<00:11:18.099> now<00:11:19.099> we're<00:11:19.249> going<00:11:19.429> to<00:11:19.489> copy<00:11:19.669> back 00:11:19.899 --> 00:11:19.909 align:start position:0% recipient now we're going to copy back 00:11:19.909 --> 00:11:22.989 align:start position:0% recipient now we're going to copy back to<00:11:20.089> values<00:11:21.159> the<00:11:22.159> Depression<00:11:22.579> positive 00:11:22.989 --> 00:11:22.999 align:start position:0% to values the Depression positive 00:11:22.999 --> 00:11:29.889 align:start position:0% to values the Depression positive alright<00:11:27.309> the<00:11:28.309> nymph<00:11:28.549> compiler<00:11:28.969> then<00:11:29.239> combines 00:11:29.889 --> 00:11:29.899 align:start position:0% alright the nymph compiler then combines 00:11:29.899 --> 00:11:31.719 align:start position:0% alright the nymph compiler then combines to<00:11:30.139> say<00:11:30.289> hello<00:11:30.499> we<00:11:30.679> have<00:11:30.829> another<00:11:31.099> businesses 00:11:31.719 --> 00:11:31.729 align:start position:0% to say hello we have another businesses 00:11:31.729 --> 00:11:36.539 align:start position:0% to say hello we have another businesses kind<00:11:31.969> of<00:11:32.059> generic<00:11:32.629> ir<00:11:33.229> for<00:11:33.559> lots<00:11:33.769> of<00:11:33.889> languages 00:11:36.539 --> 00:11:36.549 align:start position:0% 00:11:36.549 --> 00:11:39.249 align:start position:0% the<00:11:37.549> reason<00:11:37.879> why<00:11:37.999> um<00:11:38.479> does<00:11:38.689> this<00:11:38.959> waves 00:11:39.249 --> 00:11:39.259 align:start position:0% the reason why um does this waves 00:11:39.259 --> 00:11:41.769 align:start position:0% the reason why um does this waves because<00:11:39.709> they<00:11:39.889> can<00:11:40.159> then<00:11:40.189> generic<00:11:41.179> optimize 00:11:41.769 --> 00:11:41.779 align:start position:0% because they can then generic optimize 00:11:41.779 --> 00:11:44.949 align:start position:0% because they can then generic optimize and<00:11:42.409> there's<00:11:42.709> like<00:11:42.919> medium<00:11:43.929> level<00:11:44.929> of 00:11:44.949 --> 00:11:44.959 align:start position:0% and there's like medium level of 00:11:44.959 --> 00:11:48.219 align:start position:0% and there's like medium level of abstraction<00:11:45.589> and<00:11:46.629> it's<00:11:47.629> looking<00:11:47.899> even<00:11:48.199> worse 00:11:48.219 --> 00:11:48.229 align:start position:0% abstraction and it's looking even worse 00:11:48.229 --> 00:11:52.509 align:start position:0% abstraction and it's looking even worse right<00:11:48.679> here<00:11:48.919> it's<00:11:49.039> but<00:11:51.339> there's<00:11:52.339> not<00:11:52.459> even 00:11:52.509 --> 00:11:52.519 align:start position:0% right here it's but there's not even 00:11:52.519 --> 00:11:55.949 align:start position:0% right here it's but there's not even really<00:11:52.970> having<00:11:53.449> rights<00:11:53.629> yeah<00:11:54.529> big<00:11:54.859> memory 00:11:55.949 --> 00:11:55.959 align:start position:0% really having rights yeah big memory 00:11:55.959 --> 00:11:58.569 align:start position:0% really having rights yeah big memory you're<00:11:56.959> offsetting<00:11:57.679> pointers<00:11:58.159> into<00:11:58.429> these 00:11:58.569 --> 00:11:58.579 align:start position:0% you're offsetting pointers into these 00:11:58.579 --> 00:11:59.890 align:start position:0% you're offsetting pointers into these structures<00:11:58.970> for 00:11:59.890 --> 00:11:59.900 align:start position:0% structures for 00:11:59.900 --> 00:12:02.579 align:start position:0% structures for nail<00:12:00.140> polish<00:12:00.700> disappear<00:12:01.700> recognize<00:12:02.120> them 00:12:02.579 --> 00:12:02.589 align:start position:0% nail polish disappear recognize them 00:12:02.589 --> 00:12:04.990 align:start position:0% nail polish disappear recognize them from<00:12:03.589> their<00:12:03.800> computer<00:12:04.190> science<00:12:04.490> class<00:12:04.670> right 00:12:04.990 --> 00:12:05.000 align:start position:0% from their computer science class right 00:12:05.000 --> 00:12:08.079 align:start position:0% from their computer science class right I<00:12:05.150> was<00:12:05.420> like<00:12:06.050> starting<00:12:06.680> like<00:12:07.339> here<00:12:07.520> we<00:12:07.580> have<00:12:07.640> no 00:12:08.079 --> 00:12:08.089 align:start position:0% I was like starting like here we have no 00:12:08.089 --> 00:12:09.700 align:start position:0% I was like starting like here we have no specific<00:12:08.510> knowledge<00:12:08.900> to<00:12:09.140> understand<00:12:09.500> what's 00:12:09.700 --> 00:12:09.710 align:start position:0% specific knowledge to understand what's 00:12:09.710 --> 00:12:16.630 align:start position:0% specific knowledge to understand what's going<00:12:09.920> on<00:12:13.480> and<00:12:14.480> finally<00:12:14.810> we<00:12:15.170> have<00:12:15.440> this<00:12:16.400> that 00:12:16.630 --> 00:12:16.640 align:start position:0% going on and finally we have this that 00:12:16.640 --> 00:12:20.080 align:start position:0% going on and finally we have this that we<00:12:16.700> have<00:12:17.390> these<00:12:17.600> this<00:12:17.900> another<00:12:18.230> system<00:12:18.650> wasn't 00:12:20.080 --> 00:12:20.090 align:start position:0% we have these this another system wasn't 00:12:20.090 --> 00:12:22.230 align:start position:0% we have these this another system wasn't [Music] 00:12:22.230 --> 00:12:22.240 align:start position:0% [Music] 00:12:22.240 --> 00:12:24.370 align:start position:0% [Music] LVN<00:12:23.240> register-based 00:12:24.370 --> 00:12:24.380 align:start position:0% LVN register-based 00:12:24.380 --> 00:12:28.120 align:start position:0% LVN register-based wasn't<00:12:25.070> snack<00:12:25.339> based<00:12:25.610> sled<00:12:26.770> two<00:12:27.770> ways<00:12:27.950> of 00:12:28.120 --> 00:12:28.130 align:start position:0% wasn't snack based sled two ways of 00:12:28.130 --> 00:12:29.620 align:start position:0% wasn't snack based sled two ways of looking<00:12:28.430> at<00:12:28.640> the<00:12:28.790> same<00:12:29.000> problem<00:12:29.120> this 00:12:29.620 --> 00:12:29.630 align:start position:0% looking at the same problem this 00:12:29.630 --> 00:12:32.920 align:start position:0% looking at the same problem this mismatch<00:12:30.820> is<00:12:31.820> one<00:12:32.029> of<00:12:32.150> the<00:12:32.300> reasons<00:12:32.540> why<00:12:32.690> some 00:12:32.920 --> 00:12:32.930 align:start position:0% mismatch is one of the reasons why some 00:12:32.930 --> 00:12:34.810 align:start position:0% mismatch is one of the reasons why some people<00:12:33.050> think<00:12:33.440> is<00:12:33.560> better<00:12:33.770> not<00:12:34.250> to<00:12:34.310> go<00:12:34.550> through 00:12:34.810 --> 00:12:34.820 align:start position:0% people think is better not to go through 00:12:34.820 --> 00:12:36.750 align:start position:0% people think is better not to go through again<00:12:35.180> and<00:12:35.660> you<00:12:35.839> create 00:12:36.750 --> 00:12:36.760 align:start position:0% again and you create 00:12:36.760 --> 00:12:40.050 align:start position:0% again and you create -<00:12:37.290> because<00:12:38.290> I'm<00:12:38.980> listening<00:12:39.250> every 00:12:40.050 --> 00:12:40.060 align:start position:0% - because I'm listening every 00:12:40.060 --> 00:12:42.870 align:start position:0% - because I'm listening every translation<00:12:40.900> step<00:12:41.590> you<00:12:42.220> lose<00:12:42.430> a<00:12:42.460> little<00:12:42.730> bit 00:12:42.870 --> 00:12:42.880 align:start position:0% translation step you lose a little bit 00:12:42.880 --> 00:12:45.480 align:start position:0% translation step you lose a little bit of<00:12:42.970> efficiency<00:12:43.630> and<00:12:44.380> that's<00:12:44.500> true<00:12:44.890> when 00:12:45.480 --> 00:12:45.490 align:start position:0% of efficiency and that's true when 00:12:45.490 --> 00:12:46.620 align:start position:0% of efficiency and that's true when you're<00:12:45.580> going<00:12:45.820> from<00:12:46.030> the<00:12:46.150> high<00:12:46.300> level 00:12:46.620 --> 00:12:46.630 align:start position:0% you're going from the high level 00:12:46.630 --> 00:12:49.380 align:start position:0% you're going from the high level constructs<00:12:47.200> like<00:12:47.650> the<00:12:48.580> medium<00:12:48.880> better<00:12:49.090> ones 00:12:49.380 --> 00:12:49.390 align:start position:0% constructs like the medium better ones 00:12:49.390 --> 00:12:51.630 align:start position:0% constructs like the medium better ones and<00:12:49.750> every<00:12:50.470> time<00:12:50.710> you<00:12:50.800> take<00:12:50.980> a<00:12:51.040> step<00:12:51.160> back<00:12:51.520> this 00:12:51.630 --> 00:12:51.640 align:start position:0% and every time you take a step back this 00:12:51.640 --> 00:12:54.780 align:start position:0% and every time you take a step back this one<00:12:51.850> tiny<00:12:52.810> little<00:12:52.930> bit<00:12:53.290> will<00:12:54.190> be<00:12:54.220> exploiting 00:12:54.780 --> 00:12:54.790 align:start position:0% one tiny little bit will be exploiting 00:12:54.790 --> 00:12:56.430 align:start position:0% one tiny little bit will be exploiting some<00:12:54.970> of<00:12:55.060> these<00:12:55.210> things<00:12:55.420> that<00:12:55.570> we<00:12:55.840> know<00:12:56.080> our 00:12:56.430 --> 00:12:56.440 align:start position:0% some of these things that we know our 00:12:56.440 --> 00:12:59.460 align:start position:0% some of these things that we know our losses<00:12:57.300> and<00:12:58.300> you<00:12:58.360> try<00:12:58.720> to<00:12:58.750> take<00:12:59.050> them<00:12:59.290> away 00:12:59.460 --> 00:12:59.470 align:start position:0% losses and you try to take them away 00:12:59.470 --> 00:13:08.960 align:start position:0% losses and you try to take them away right<00:13:00.060> by<00:13:01.060> being<00:13:01.570> smart<00:13:01.930> about<00:13:03.840> progression 00:13:08.960 --> 00:13:08.970 align:start position:0% 00:13:08.970 --> 00:13:11.910 align:start position:0% our<00:13:09.970> starting<00:13:10.330> point<00:13:10.570> is<00:13:10.690> rapid<00:13:11.110> four<00:13:11.380> four 00:13:11.910 --> 00:13:11.920 align:start position:0% our starting point is rapid four four 00:13:11.920 --> 00:13:14.220 align:start position:0% our starting point is rapid four four four<00:13:12.400> and<00:13:12.430> a<00:13:12.520> half<00:13:12.580> kilobytes<00:13:13.120> if<00:13:13.870> you<00:13:14.020> take 00:13:14.220 --> 00:13:14.230 align:start position:0% four and a half kilobytes if you take 00:13:14.230 --> 00:13:19.290 align:start position:0% four and a half kilobytes if you take like<00:13:14.440> that<00:13:14.680> smart<00:13:15.160> contract<00:13:15.580> code<00:13:17.880> you<00:13:18.880> end<00:13:19.120> up 00:13:19.290 --> 00:13:19.300 align:start position:0% like that smart contract code you end up 00:13:19.300 --> 00:13:22.740 align:start position:0% like that smart contract code you end up at<00:13:19.510> four<00:13:20.440> kilobytes<00:13:20.860> and<00:13:21.150> there<00:13:22.150> is<00:13:22.240> a<00:13:22.270> tool 00:13:22.740 --> 00:13:22.750 align:start position:0% at four kilobytes and there is a tool 00:13:22.750 --> 00:13:27.090 align:start position:0% at four kilobytes and there is a tool called<00:13:22.870> twitting<00:13:25.320> which<00:13:26.320> gives<00:13:26.650> you<00:13:26.890> like 00:13:27.090 --> 00:13:27.100 align:start position:0% called twitting which gives you like 00:13:27.100 --> 00:13:30.750 align:start position:0% called twitting which gives you like where<00:13:27.400> the<00:13:27.430> size<00:13:28.420> is<00:13:28.810> suspect<00:13:29.760> immensely 00:13:30.750 --> 00:13:30.760 align:start position:0% where the size is suspect immensely 00:13:30.760 --> 00:13:32.490 align:start position:0% where the size is suspect immensely useful<00:13:30.820> so<00:13:31.180> you<00:13:31.270> can<00:13:31.420> see<00:13:31.570> that<00:13:31.720> like<00:13:31.900> I<00:13:32.140> just 00:13:32.490 --> 00:13:32.500 align:start position:0% useful so you can see that like I just 00:13:32.500 --> 00:13:34.170 align:start position:0% useful so you can see that like I just the<00:13:32.830> fact<00:13:33.040> that<00:13:33.130> we're<00:13:33.370> saving<00:13:33.610> is<00:13:33.940> bond 00:13:34.170 --> 00:13:34.180 align:start position:0% the fact that we're saving is bond 00:13:34.180 --> 00:13:36.060 align:start position:0% the fact that we're saving is bond function<00:13:34.480> names<00:13:34.870> we<00:13:35.530> have<00:13:35.680> that<00:13:35.830> to<00:13:35.950> do 00:13:36.060 --> 00:13:36.070 align:start position:0% function names we have that to do 00:13:36.070 --> 00:13:38.160 align:start position:0% function names we have that to do transfer<00:13:36.580> takes<00:13:37.120> up<00:13:37.300> a<00:13:37.420> lot<00:13:37.600> of<00:13:37.630> space<00:13:37.900> in<00:13:38.080> a 00:13:38.160 --> 00:13:38.170 align:start position:0% transfer takes up a lot of space in a 00:13:38.170 --> 00:13:40.230 align:start position:0% transfer takes up a lot of space in a monitor<00:13:38.530> the<00:13:39.430> first<00:13:39.670> thing<00:13:39.820> you<00:13:39.910> want<00:13:40.060> to<00:13:40.120> do 00:13:40.230 --> 00:13:40.240 align:start position:0% monitor the first thing you want to do 00:13:40.240 --> 00:13:41.610 align:start position:0% monitor the first thing you want to do is<00:13:40.390> like<00:13:40.540> make<00:13:40.570> sure<00:13:40.930> that<00:13:41.080> you're<00:13:41.260> calling 00:13:41.610 --> 00:13:41.620 align:start position:0% is like make sure that you're calling 00:13:41.620 --> 00:13:44.040 align:start position:0% is like make sure that you're calling your<00:13:41.710> tools<00:13:42.010> correctly<00:13:42.510> that<00:13:43.510> you<00:13:43.630> want<00:13:43.840> that 00:13:44.040 --> 00:13:44.050 align:start position:0% your tools correctly that you want that 00:13:44.050 --> 00:13:46.490 align:start position:0% your tools correctly that you want that tools<00:13:44.320> that<00:13:44.590> I<00:13:44.710> strip<00:13:45.010> away<00:13:45.040> all<00:13:45.250> the<00:13:45.460> stuff 00:13:46.490 --> 00:13:46.500 align:start position:0% tools that I strip away all the stuff 00:13:46.500 --> 00:13:50.360 align:start position:0% tools that I strip away all the stuff and<00:13:47.500> try<00:13:48.460> to<00:13:48.490> do<00:13:48.970> some<00:13:49.270> basic<00:13:49.660> optimization 00:13:50.360 --> 00:13:50.370 align:start position:0% and try to do some basic optimization 00:13:50.370 --> 00:13:52.920 align:start position:0% and try to do some basic optimization just<00:13:51.370> by<00:13:51.580> using<00:13:51.820> the<00:13:52.120> compiler<00:13:52.540> and<00:13:52.780> I'm 00:13:52.920 --> 00:13:52.930 align:start position:0% just by using the compiler and I'm 00:13:52.930 --> 00:13:55.090 align:start position:0% just by using the compiler and I'm calling<00:13:53.620> it 00:13:55.090 --> 00:13:55.100 align:start position:0% calling it 00:13:55.100 --> 00:13:59.460 align:start position:0% calling it we<00:13:55.550> can<00:13:55.730> bring<00:13:55.880> them<00:13:56.180> to<00:13:56.870> clear<00:13:57.230> out<00:13:57.350> theater 00:13:59.460 --> 00:13:59.470 align:start position:0% we can bring them to clear out theater 00:13:59.470 --> 00:14:01.480 align:start position:0% we can bring them to clear out theater but<00:14:00.470> obviously<00:14:00.800> like<00:14:00.950> when<00:14:01.250> you're<00:14:01.400> looking 00:14:01.480 --> 00:14:01.490 align:start position:0% but obviously like when you're looking 00:14:01.490 --> 00:14:03.250 align:start position:0% but obviously like when you're looking at<00:14:01.730> the<00:14:01.850> boat<00:14:02.090> you<00:14:02.450> can't<00:14:02.660> really<00:14:02.810> tell<00:14:03.080> what's 00:14:03.250 --> 00:14:03.260 align:start position:0% at the boat you can't really tell what's 00:14:03.260 --> 00:14:05.140 align:start position:0% at the boat you can't really tell what's going<00:14:03.410> on<00:14:03.560> anymore<00:14:03.830> but<00:14:04.670> the<00:14:04.790> compiler 00:14:05.140 --> 00:14:05.150 align:start position:0% going on anymore but the compiler 00:14:05.150 --> 00:14:06.940 align:start position:0% going on anymore but the compiler doesn't<00:14:05.480> work<00:14:05.900> early<00:14:06.320> the<00:14:06.440> execution 00:14:06.940 --> 00:14:06.950 align:start position:0% doesn't work early the execution 00:14:06.950 --> 00:14:08.740 align:start position:0% doesn't work early the execution environment<00:14:07.370> doesn't<00:14:07.640> really<00:14:07.760> care<00:14:08.030> about<00:14:08.270> my 00:14:08.740 --> 00:14:08.750 align:start position:0% environment doesn't really care about my 00:14:08.750 --> 00:14:14.280 align:start position:0% environment doesn't really care about my special<00:14:09.200> messages<00:14:09.790> means<00:14:10.790> no<00:14:11.330> very<00:14:11.630> common<00:14:12.020> so 00:14:14.280 --> 00:14:14.290 align:start position:0% 00:14:14.290 --> 00:14:17.110 align:start position:0% the<00:14:15.290> second<00:14:15.620> thing<00:14:15.800> is<00:14:16.100> that<00:14:16.310> like<00:14:16.790> when<00:14:17.000> we 00:14:17.110 --> 00:14:17.120 align:start position:0% the second thing is that like when we 00:14:17.120 --> 00:14:18.940 align:start position:0% the second thing is that like when we started<00:14:17.450> doing<00:14:17.750> this<00:14:18.020> that<00:14:18.260> we<00:14:18.290> were<00:14:18.500> thinking 00:14:18.940 --> 00:14:18.950 align:start position:0% started doing this that we were thinking 00:14:18.950 --> 00:14:21.330 align:start position:0% started doing this that we were thinking like<00:14:18.980> alright<00:14:19.340> let's<00:14:19.400> do<00:14:19.760> an<00:14:20.180> elevated 00:14:21.330 --> 00:14:21.340 align:start position:0% like alright let's do an elevated 00:14:21.340 --> 00:14:25.770 align:start position:0% like alright let's do an elevated 128-bit<00:14:22.340> integers<00:14:23.590> and<00:14:24.590> this<00:14:24.740> is<00:14:24.890> like 00:14:25.770 --> 00:14:25.780 align:start position:0% 128-bit integers and this is like 00:14:25.780 --> 00:14:30.030 align:start position:0% 128-bit integers and this is like distance<00:14:26.780> of<00:14:26.960> really<00:14:27.200> not<00:14:27.350> understanding<00:14:27.980> us 00:14:30.030 --> 00:14:30.040 align:start position:0% distance of really not understanding us 00:14:30.040 --> 00:14:33.010 align:start position:0% distance of really not understanding us the<00:14:31.040> challenge<00:14:31.490> was<00:14:31.670> for<00:14:31.880> 64-bit<00:14:32.600> integers 00:14:33.010 --> 00:14:33.020 align:start position:0% the challenge was for 64-bit integers 00:14:33.020 --> 00:14:35.440 align:start position:0% the challenge was for 64-bit integers and<00:14:33.200> we<00:14:33.440> wrote<00:14:33.710> this<00:14:33.860> with<00:14:34.220> an<00:14:34.370> 8<00:14:34.850> bit<00:14:35.030> integers 00:14:35.440 --> 00:14:35.450 align:start position:0% and we wrote this with an 8 bit integers 00:14:35.450 --> 00:14:38.500 align:start position:0% and we wrote this with an 8 bit integers because<00:14:35.630> that's<00:14:35.930> what<00:14:36.080> using<00:14:36.890> material<00:14:37.510> for 00:14:38.500 --> 00:14:38.510 align:start position:0% because that's what using material for 00:14:38.510 --> 00:14:42.790 align:start position:0% because that's what using material for storing<00:14:38.780> way<00:14:38.930> values<00:14:41.470> well<00:14:42.470> them<00:14:42.680> in 00:14:42.790 --> 00:14:42.800 align:start position:0% storing way values well them in 00:14:42.800 --> 00:14:44.740 align:start position:0% storing way values well them in particular<00:14:43.340> has<00:14:43.730> issues<00:14:44.120> with<00:14:44.270> this<00:14:44.420> there's 00:14:44.740 --> 00:14:44.750 align:start position:0% particular has issues with this there's 00:14:44.750 --> 00:14:49.480 align:start position:0% particular has issues with this there's no<00:14:44.870> active<00:14:45.260> collaboration<00:14:46.100> for<00:14:46.250> example<00:14:48.490> so 00:14:49.480 --> 00:14:49.490 align:start position:0% no active collaboration for example so 00:14:49.490 --> 00:14:53.650 align:start position:0% no active collaboration for example so when<00:14:49.670> you<00:14:49.790> want<00:14:50.030> to<00:14:50.270> add<00:14:50.560> to<00:14:52.270> 128-bit<00:14:53.270> numbers 00:14:53.650 --> 00:14:53.660 align:start position:0% when you want to add to 128-bit numbers 00:14:53.660 --> 00:14:55.660 align:start position:0% when you want to add to 128-bit numbers together<00:14:53.870> you<00:14:54.350> have<00:14:54.710> to<00:14:54.830> do<00:14:54.980> piece<00:14:55.430> by<00:14:55.640> piece 00:14:55.660 --> 00:14:55.670 align:start position:0% together you have to do piece by piece 00:14:55.670 --> 00:15:00.130 align:start position:0% together you have to do piece by piece and<00:14:55.910> then<00:14:56.240> you<00:14:56.330> have<00:14:56.420> a<00:14:56.720> little<00:14:58.420> branch<00:14:59.420> to<00:14:59.960> see 00:15:00.130 --> 00:15:00.140 align:start position:0% and then you have a little branch to see 00:15:00.140 --> 00:15:02.590 align:start position:0% and then you have a little branch to see if<00:15:00.290> you<00:15:00.440> overload<00:15:01.070> and<00:15:01.370> then<00:15:01.940> you<00:15:02.150> need<00:15:02.300> to<00:15:02.420> add 00:15:02.590 --> 00:15:02.600 align:start position:0% if you overload and then you need to add 00:15:02.600 --> 00:15:06.850 align:start position:0% if you overload and then you need to add that<00:15:02.870> to<00:15:02.930> your<00:15:04.030> number<00:15:05.030> and<00:15:05.900> it<00:15:06.380> becomes<00:15:06.680> like 00:15:06.850 --> 00:15:06.860 align:start position:0% that to your number and it becomes like 00:15:06.860 --> 00:15:14.470 align:start position:0% that to your number and it becomes like a<00:15:07.130> fairly<00:15:07.640> big<00:15:10.030> chunk<00:15:11.030> of<00:15:11.210> rock<00:15:12.910> so<00:15:13.910> it<00:15:14.030> was<00:15:14.180> all 00:15:14.470 --> 00:15:14.480 align:start position:0% a fairly big chunk of rock so it was all 00:15:14.480 --> 00:15:18.310 align:start position:0% a fairly big chunk of rock so it was all right<00:15:14.540> fine<00:15:15.170> let's<00:15:15.530> skip<00:15:15.920> 220<00:15:16.790> bit<00:15:17.030> stuff<00:15:17.320> it's 00:15:18.310 --> 00:15:18.320 align:start position:0% right fine let's skip 220 bit stuff it's 00:15:18.320 --> 00:15:21.540 align:start position:0% right fine let's skip 220 bit stuff it's moved<00:15:18.590> to<00:15:18.800> 64-bit<00:15:19.340> value<00:15:19.610> struct 00:15:21.540 --> 00:15:21.550 align:start position:0% moved to 64-bit value struct 00:15:21.550 --> 00:15:25.090 align:start position:0% moved to 64-bit value struct there<00:15:22.550> we<00:15:22.670> go<00:15:23.200> 100<00:15:24.200> bytes<00:15:24.350> of<00:15:24.530> site 00:15:25.090 --> 00:15:25.100 align:start position:0% there we go 100 bytes of site 00:15:25.100 --> 00:15:29.890 align:start position:0% there we go 100 bytes of site I<00:15:25.930> thought<00:15:26.930> it<00:15:27.080> would<00:15:27.260> be<00:15:27.380> more<00:15:27.560> I<00:15:28.900> really 00:15:29.890 --> 00:15:29.900 align:start position:0% I thought it would be more I really 00:15:29.900 --> 00:15:31.510 align:start position:0% I thought it would be more I really thought<00:15:30.050> it<00:15:30.170> would<00:15:30.320> be<00:15:30.440> more<00:15:30.620> because<00:15:30.950> at 00:15:31.510 --> 00:15:31.520 align:start position:0% thought it would be more because at 00:15:31.520 --> 00:15:33.340 align:start position:0% thought it would be more because at these<00:15:31.760> ad<00:15:32.000> with<00:15:32.210> carries<00:15:32.600> and<00:15:32.780> so<00:15:32.930> on<00:15:33.110> the<00:15:33.230> you 00:15:33.340 --> 00:15:33.350 align:start position:0% these ad with carries and so on the you 00:15:33.350 --> 00:15:35.470 align:start position:0% these ad with carries and so on the you tend<00:15:33.920> to<00:15:34.010> take<00:15:34.190> up<00:15:34.400> a<00:15:34.610> lot<00:15:34.910> of<00:15:34.940> space<00:15:35.240> if<00:15:35.450> you 00:15:35.470 --> 00:15:35.480 align:start position:0% tend to take up a lot of space if you 00:15:35.480 --> 00:15:41.940 align:start position:0% tend to take up a lot of space if you lived<00:15:36.460> with<00:15:37.460> lives<00:15:39.460> but<00:15:40.460> it<00:15:40.580> turns<00:15:40.790> out<00:15:41.000> that 00:15:41.940 --> 00:15:41.950 align:start position:0% lived with lives but it turns out that 00:15:41.950 --> 00:15:44.350 align:start position:0% lived with lives but it turns out that we<00:15:42.950> meant<00:15:43.160> the<00:15:43.280> optimizer<00:15:43.730> does<00:15:43.970> the 00:15:44.350 --> 00:15:44.360 align:start position:0% we meant the optimizer does the 00:15:44.360 --> 00:15:47.740 align:start position:0% we meant the optimizer does the optimizer<00:15:44.750> do<00:15:45.050> well<00:15:45.320> the<00:15:46.220> optimizer<00:15:46.670> looks<00:15:47.540> at 00:15:47.740 --> 00:15:47.750 align:start position:0% optimizer do well the optimizer looks at 00:15:47.750 --> 00:15:50.260 align:start position:0% optimizer do well the optimizer looks at your<00:15:47.930> code<00:15:48.170> and<00:15:48.580> price<00:15:49.580> to<00:15:49.760> make<00:15:49.910> it<00:15:50.060> better 00:15:50.260 --> 00:15:50.270 align:start position:0% your code and price to make it better 00:15:50.270 --> 00:15:54.130 align:start position:0% your code and price to make it better right<00:15:51.610> and<00:15:52.610> one<00:15:53.390> of<00:15:53.510> the<00:15:53.660> functions<00:15:54.080> that 00:15:54.130 --> 00:15:54.140 align:start position:0% right and one of the functions that 00:15:54.140 --> 00:15:56.700 align:start position:0% right and one of the functions that graduates<00:15:54.650> is<00:15:54.770> begun<00:15:55.100> in<00:15:55.310> English 00:15:56.700 --> 00:15:56.710 align:start position:0% graduates is begun in English 00:15:56.710 --> 00:16:00.640 align:start position:0% graduates is begun in English implemented<00:15:57.710> in<00:15:58.520> a<00:15:58.600> bit<00:15:59.600> from<00:16:00.080> like<00:16:00.470> you<00:16:00.620> know 00:16:00.640 --> 00:16:00.650 align:start position:0% implemented in a bit from like you know 00:16:00.650 --> 00:16:02.620 align:start position:0% implemented in a bit from like you know by<00:16:01.430> following<00:16:01.730> the<00:16:01.910> bits<00:16:02.120> which<00:16:02.330> you<00:16:02.450> don't 00:16:02.620 --> 00:16:02.630 align:start position:0% by following the bits which you don't 00:16:02.630 --> 00:16:05.140 align:start position:0% by following the bits which you don't have<00:16:02.750> access<00:16:02.870> to<00:16:03.080> an<00:16:03.610> instruction<00:16:04.610> does<00:16:04.970> this 00:16:05.140 --> 00:16:05.150 align:start position:0% have access to an instruction does this 00:16:05.150 --> 00:16:07.840 align:start position:0% have access to an instruction does this for<00:16:05.450> you<00:16:05.740> this<00:16:06.740> is<00:16:06.890> what<00:16:07.070> you<00:16:07.190> need<00:16:07.310> to<00:16:07.430> do<00:16:07.580> in 00:16:07.840 --> 00:16:07.850 align:start position:0% for you this is what you need to do in 00:16:07.850 --> 00:16:09.750 align:start position:0% for you this is what you need to do in the<00:16:07.940> basic<00:16:08.240> operations 00:16:09.750 --> 00:16:09.760 align:start position:0% the basic operations 00:16:09.760 --> 00:16:13.170 align:start position:0% the basic operations and<00:16:09.940> juicy<00:16:10.630> stuff<00:16:11.130> but<00:16:12.130> Alabama<00:16:12.430> is<00:16:12.760> so<00:16:12.910> smart 00:16:13.170 --> 00:16:13.180 align:start position:0% and juicy stuff but Alabama is so smart 00:16:13.180 --> 00:16:16.220 align:start position:0% and juicy stuff but Alabama is so smart that<00:16:13.510> it<00:16:14.019> recognizes<00:16:14.680> this<00:16:15.010> pattern<00:16:15.430> and 00:16:16.220 --> 00:16:16.230 align:start position:0% that it recognizes this pattern and 00:16:16.230 --> 00:16:19.879 align:start position:0% that it recognizes this pattern and transition<00:16:17.230> to<00:16:17.260> a<00:16:17.410> peace<00:16:17.620> walk<00:16:17.940> intrinsic 00:16:19.879 --> 00:16:19.889 align:start position:0% transition to a peace walk intrinsic 00:16:19.889 --> 00:16:23.040 align:start position:0% transition to a peace walk intrinsic before<00:16:20.889> which<00:16:21.490> is<00:16:21.670> like<00:16:21.940> what<00:16:22.180> the<00:16:22.690> swapper 00:16:23.040 --> 00:16:23.050 align:start position:0% before which is like what the swapper 00:16:23.050 --> 00:16:25.079 align:start position:0% before which is like what the swapper bytes<00:16:23.380> one<00:16:24.040> more<00:16:24.279> thing<00:16:24.519> that<00:16:24.550> you<00:16:24.790> don't<00:16:24.880> have 00:16:25.079 --> 00:16:25.089 align:start position:0% bytes one more thing that you don't have 00:16:25.089 --> 00:16:33.210 align:start position:0% bytes one more thing that you don't have available<00:16:25.600> in<00:16:25.720> wasn't<00:16:28.740> but<00:16:30.300> when<00:16:31.589> we<00:16:32.589> take<00:16:32.920> the 00:16:33.210 --> 00:16:33.220 align:start position:0% available in wasn't but when we take the 00:16:33.220 --> 00:16:38.610 align:start position:0% available in wasn't but when we take the step<00:16:33.550> from<00:16:33.970> wasn't<00:16:34.510> from<00:16:35.110> LLVM<00:16:35.800> to<00:16:36.100> IR<00:16:37.620> Olivia 00:16:38.610 --> 00:16:38.620 align:start position:0% step from wasn't from LLVM to IR Olivia 00:16:38.620 --> 00:16:40.889 align:start position:0% step from wasn't from LLVM to IR Olivia does<00:16:38.860> not<00:16:39.040> know<00:16:39.279> about<00:16:39.310> this<00:16:39.790> really<00:16:40.180> so<00:16:40.810> it 00:16:40.889 --> 00:16:40.899 align:start position:0% does not know about this really so it 00:16:40.899 --> 00:16:43.350 align:start position:0% does not know about this really so it thinks<00:16:41.320> that<00:16:41.350> this<00:16:41.649> be<00:16:41.889> Spock<00:16:42.190> call<00:16:42.820> is<00:16:43.300> very 00:16:43.350 --> 00:16:43.360 align:start position:0% thinks that this be Spock call is very 00:16:43.360 --> 00:16:49.920 align:start position:0% thinks that this be Spock call is very cheap<00:16:43.810> and<00:16:44.470> in<00:16:45.220> light<00:16:45.399> sit<00:16:47.760> on<00:16:48.760> x86<00:16:49.240> that<00:16:49.750> makes 00:16:49.920 --> 00:16:49.930 align:start position:0% cheap and in light sit on x86 that makes 00:16:49.930 --> 00:16:50.639 align:start position:0% cheap and in light sit on x86 that makes perfect<00:16:50.110> sense 00:16:50.639 --> 00:16:50.649 align:start position:0% perfect sense 00:16:50.649 --> 00:16:54.060 align:start position:0% perfect sense it's<00:16:50.800> not<00:16:51.010> an<00:16:51.070> instruction<00:16:51.399> thing<00:16:52.920> and<00:16:53.920> you 00:16:54.060 --> 00:16:54.070 align:start position:0% it's not an instruction thing and you 00:16:54.070 --> 00:16:55.710 align:start position:0% it's not an instruction thing and you really<00:16:54.459> don't<00:16:54.639> want<00:16:54.820> to<00:16:54.850> be<00:16:54.970> making<00:16:55.510> a 00:16:55.710 --> 00:16:55.720 align:start position:0% really don't want to be making a 00:16:55.720 --> 00:16:57.240 align:start position:0% really don't want to be making a function<00:16:56.199> call<00:16:56.410> to<00:16:56.440> access<00:16:56.889> this<00:16:57.010> one 00:16:57.240 --> 00:16:57.250 align:start position:0% function call to access this one 00:16:57.250 --> 00:17:01.500 align:start position:0% function call to access this one instruction<00:16:57.870> was<00:16:58.870> it<00:16:59.050> not<00:16:59.199> so<00:17:00.329> all<00:17:01.329> right 00:17:01.500 --> 00:17:01.510 align:start position:0% instruction was it not so all right 00:17:01.510 --> 00:17:03.060 align:start position:0% instruction was it not so all right let's<00:17:01.870> start<00:17:02.079> up<00:17:02.230> in<00:17:02.410> lighting<00:17:02.769> for<00:17:02.949> this 00:17:03.060 --> 00:17:03.070 align:start position:0% let's start up in lighting for this 00:17:03.070 --> 00:17:05.760 align:start position:0% let's start up in lighting for this particular<00:17:03.490> function<00:17:03.760> in<00:17:04.059> something<00:17:04.449> look<00:17:04.770> we 00:17:05.760 --> 00:17:05.770 align:start position:0% particular function in something look we 00:17:05.770 --> 00:17:12.480 align:start position:0% particular function in something look we use<00:17:09.120> 50<00:17:10.120> months<00:17:10.270> something<00:17:11.079> like<00:17:11.230> this<00:17:11.530> just 00:17:12.480 --> 00:17:12.490 align:start position:0% use 50 months something like this just 00:17:12.490 --> 00:17:16.470 align:start position:0% use 50 months something like this just by<00:17:13.049> giving<00:17:14.049> the<00:17:14.740> optimizer<00:17:15.309> this<00:17:15.669> hint<00:17:15.970> we 00:17:16.470 --> 00:17:16.480 align:start position:0% by giving the optimizer this hint we 00:17:16.480 --> 00:17:18.770 align:start position:0% by giving the optimizer this hint we know<00:17:16.660> something<00:17:17.079> better<00:17:17.290> than<00:17:17.559> the<00:17:17.679> optimized 00:17:18.770 --> 00:17:18.780 align:start position:0% know something better than the optimized 00:17:18.780 --> 00:17:24.100 align:start position:0% know something better than the optimized [Music] 00:17:24.100 --> 00:17:24.110 align:start position:0% 00:17:24.110 --> 00:17:26.859 align:start position:0% moving<00:17:24.919> on<00:17:25.009> we<00:17:25.879> have<00:17:25.999> the<00:17:26.149> language<00:17:26.360> itself 00:17:26.859 --> 00:17:26.869 align:start position:0% moving on we have the language itself 00:17:26.869 --> 00:17:31.029 align:start position:0% moving on we have the language itself right<00:17:27.879> NIM<00:17:28.879> is<00:17:29.210> as<00:17:30.080> kind<00:17:30.529> of<00:17:30.590> like<00:17:30.649> the<00:17:30.769> same 00:17:31.029 --> 00:17:31.039 align:start position:0% right NIM is as kind of like the same 00:17:31.039 --> 00:17:33.249 align:start position:0% right NIM is as kind of like the same language<00:17:31.460> when<00:17:32.330> you<00:17:32.450> initialize<00:17:32.899> things 00:17:33.249 --> 00:17:33.259 align:start position:0% language when you initialize things 00:17:33.259 --> 00:17:35.470 align:start position:0% language when you initialize things depends<00:17:33.769> to<00:17:33.950> like<00:17:34.159> to<00:17:34.519> zero 00:17:35.470 --> 00:17:35.480 align:start position:0% depends to like to zero 00:17:35.480 --> 00:17:39.489 align:start position:0% depends to like to zero written<00:17:36.230> to<00:17:36.350> zeros<00:17:36.649> like<00:17:36.769> all<00:17:37.100> values<00:17:38.499> knowing 00:17:39.489 --> 00:17:39.499 align:start position:0% written to zeros like all values knowing 00:17:39.499 --> 00:17:42.039 align:start position:0% written to zeros like all values knowing this<00:17:39.759> we<00:17:40.759> haven't<00:17:40.940> really<00:17:41.240> told<00:17:41.450> him<00:17:41.809> that 00:17:42.039 --> 00:17:42.049 align:start position:0% this we haven't really told him that 00:17:42.049 --> 00:17:43.989 align:start position:0% this we haven't really told him that this<00:17:42.259> call<00:17:42.559> data<00:17:42.799> property<00:17:43.429> function<00:17:43.820> would 00:17:43.989 --> 00:17:43.999 align:start position:0% this call data property function would 00:17:43.999 --> 00:17:45.960 align:start position:0% this call data property function would overwrite<00:17:44.509> the<00:17:44.720> data 00:17:45.960 --> 00:17:45.970 align:start position:0% overwrite the data 00:17:45.970 --> 00:17:49.269 align:start position:0% overwrite the data so<00:17:46.970> what<00:17:47.749> NIM<00:17:48.019> does<00:17:48.259> here<00:17:48.559> in<00:17:48.679> this<00:17:48.830> instance 00:17:49.269 --> 00:17:49.279 align:start position:0% so what NIM does here in this instance 00:17:49.279 --> 00:17:52.539 align:start position:0% so what NIM does here in this instance is<00:17:50.029> that<00:17:50.090> it<00:17:50.360> first<00:17:50.629> writes<00:17:50.919> 32<00:17:51.919> zeros<00:17:52.279> to<00:17:52.460> this 00:17:52.539 --> 00:17:52.549 align:start position:0% is that it first writes 32 zeros to this 00:17:52.549 --> 00:17:57.009 align:start position:0% is that it first writes 32 zeros to this array<00:17:52.909> of<00:17:53.090> reusing<00:17:53.749> and<00:17:54.759> then<00:17:55.759> we<00:17:56.269> override<00:17:56.840> it 00:17:57.009 --> 00:17:57.019 align:start position:0% array of reusing and then we override it 00:17:57.019 --> 00:18:02.220 align:start position:0% array of reusing and then we override it with<00:17:57.820> the<00:17:58.820> day<00:17:58.999> other<00:17:59.210> puppy<00:18:00.309> so<00:18:01.309> in<00:18:01.429> order<00:18:01.580> to 00:18:02.220 --> 00:18:02.230 align:start position:0% with the day other puppy so in order to 00:18:02.230 --> 00:18:05.169 align:start position:0% with the day other puppy so in order to know<00:18:03.230> the<00:18:03.499> check<00:18:03.710> to<00:18:03.919> do<00:18:04.610> these<00:18:04.789> things<00:18:05.029> you 00:18:05.169 --> 00:18:05.179 align:start position:0% know the check to do these things you 00:18:05.179 --> 00:18:07.720 align:start position:0% know the check to do these things you can<00:18:05.419> go<00:18:05.539> back<00:18:05.720> and<00:18:05.960> look<00:18:06.019> at<00:18:06.200> the<00:18:06.320> assembly<00:18:06.830> it 00:18:07.720 --> 00:18:07.730 align:start position:0% can go back and look at the assembly it 00:18:07.730 --> 00:18:09.820 align:start position:0% can go back and look at the assembly it was<00:18:08.119> about<00:18:08.360> but<00:18:08.600> as<00:18:08.720> he<00:18:08.960> was<00:18:09.080> going<00:18:09.440> on<00:18:09.590> in<00:18:09.740> the 00:18:09.820 --> 00:18:09.830 align:start position:0% was about but as he was going on in the 00:18:09.830 --> 00:18:12.340 align:start position:0% was about but as he was going on in the earth<00:18:09.980> in<00:18:10.159> there<00:18:10.460> are<00:18:10.639> lots<00:18:11.629> of<00:18:11.749> zeros<00:18:12.080> and<00:18:12.110> I'm 00:18:12.340 --> 00:18:12.350 align:start position:0% earth in there are lots of zeros and I'm 00:18:12.350 --> 00:18:15.730 align:start position:0% earth in there are lots of zeros and I'm Grover<00:18:12.740> adding<00:18:13.070> those<00:18:13.190> zeros<00:18:14.470> with<00:18:15.470> data 00:18:15.730 --> 00:18:15.740 align:start position:0% Grover adding those zeros with data 00:18:15.740 --> 00:18:18.159 align:start position:0% Grover adding those zeros with data right<00:18:16.039> what<00:18:16.220> we<00:18:16.399> do<00:18:16.519> without<00:18:17.169> zero 00:18:18.159 --> 00:18:18.169 align:start position:0% right what we do without zero 00:18:18.169 --> 00:18:20.350 align:start position:0% right what we do without zero initialization<00:18:19.009> we<00:18:19.340> write<00:18:19.580> 20<00:18:20.029> bytes<00:18:20.210> of 00:18:20.350 --> 00:18:20.360 align:start position:0% initialization we write 20 bytes of 00:18:20.360 --> 00:18:22.720 align:start position:0% initialization we write 20 bytes of address<00:18:20.720> and<00:18:20.960> then<00:18:21.080> is<00:18:21.259> zero<00:18:21.440> the<00:18:21.590> rest<00:18:21.769> simple 00:18:22.720 --> 00:18:22.730 align:start position:0% address and then is zero the rest simple 00:18:22.730 --> 00:18:30.100 align:start position:0% address and then is zero the rest simple optimization<00:18:23.360> right<00:18:23.740> 200<00:18:24.740> price 00:18:30.100 --> 00:18:30.110 align:start position:0% 00:18:30.110 --> 00:18:32.799 align:start position:0% you<00:18:30.620> have<00:18:30.740> to<00:18:30.950> know<00:18:31.070> your<00:18:31.250> library<00:18:31.730> but<00:18:32.630> when 00:18:32.799 --> 00:18:32.809 align:start position:0% you have to know your library but when 00:18:32.809 --> 00:18:34.720 align:start position:0% you have to know your library but when you're<00:18:32.960> using<00:18:33.230> a<00:18:33.409> library<00:18:33.590> like<00:18:33.860> a<00:18:34.159> man<00:18:34.549> to 00:18:34.720 --> 00:18:34.730 align:start position:0% you're using a library like a man to 00:18:34.730 --> 00:18:36.039 align:start position:0% you're using a library like a man to really<00:18:34.970> understand<00:18:35.360> what<00:18:35.570> the<00:18:35.720> different 00:18:36.039 --> 00:18:36.049 align:start position:0% really understand what the different 00:18:36.049 --> 00:18:39.610 align:start position:0% really understand what the different functions<00:18:36.440> do<00:18:36.940> in<00:18:37.940> this<00:18:38.120> series<00:18:38.470> naively<00:18:39.470> we 00:18:39.610 --> 00:18:39.620 align:start position:0% functions do in this series naively we 00:18:39.620 --> 00:18:41.560 align:start position:0% functions do in this series naively we thought<00:18:39.799> we'd<00:18:40.010> be<00:18:40.130> safe<00:18:40.340> with<00:18:41.029> Christ<00:18:41.330> max 00:18:41.560 --> 00:18:41.570 align:start position:0% thought we'd be safe with Christ max 00:18:41.570 --> 00:18:43.330 align:start position:0% thought we'd be safe with Christ max passage<00:18:41.990> over<00:18:42.320> we<00:18:42.649> check<00:18:42.860> the<00:18:43.010> code<00:18:43.220> they 00:18:43.330 --> 00:18:43.340 align:start position:0% passage over we check the code they 00:18:43.340 --> 00:18:46.600 align:start position:0% passage over we check the code they decide<00:18:43.640> do<00:18:43.909> we<00:18:43.940> have<00:18:44.419> 24<00:18:44.899> fights<00:18:45.110> or<00:18:45.679> not<00:18:45.830> of 00:18:46.600 --> 00:18:46.610 align:start position:0% decide do we have 24 fights or not of 00:18:46.610 --> 00:18:48.639 align:start position:0% decide do we have 24 fights or not of call<00:18:46.880> later<00:18:47.120> that<00:18:47.330> they<00:18:47.630> really<00:18:47.870> present<00:18:48.409> an 00:18:48.639 --> 00:18:48.649 align:start position:0% call later that they really present an 00:18:48.649 --> 00:18:50.529 align:start position:0% call later that they really present an update<00:18:48.799> for<00:18:49.370> us<00:18:49.429> to<00:18:49.640> run<00:18:49.820> this<00:18:49.970> function<00:18:50.210> of 00:18:50.529 --> 00:18:50.539 align:start position:0% update for us to run this function of 00:18:50.539 --> 00:18:53.110 align:start position:0% update for us to run this function of day<00:18:50.690> as<00:18:50.960> they<00:18:51.140> want<00:18:51.440> us<00:18:51.559> to<00:18:51.789> all<00:18:52.789> right<00:18:52.970> let's 00:18:53.110 --> 00:18:53.120 align:start position:0% day as they want us to all right let's 00:18:53.120 --> 00:18:55.240 align:start position:0% day as they want us to all right let's check<00:18:53.179> in<00:18:53.510> Roberta<00:18:53.840> it<00:18:54.590> turns<00:18:54.860> out<00:18:55.100> the 00:18:55.240 --> 00:18:55.250 align:start position:0% check in Roberta it turns out the 00:18:55.250 --> 00:19:00.669 align:start position:0% check in Roberta it turns out the deposit<00:18:55.580> are<00:18:55.880> copy<00:18:56.409> if<00:18:57.409> you<00:18:57.470> just<00:18:57.919> call<00:18:58.730> it<00:18:59.679> and 00:19:00.669 --> 00:19:00.679 align:start position:0% deposit are copy if you just call it and 00:19:00.679 --> 00:19:03.129 align:start position:0% deposit are copy if you just call it and give<00:19:00.980> it<00:19:01.100> like<00:19:01.340> alright<00:19:01.880> I<00:19:01.940> want<00:19:02.330> to<00:19:02.450> last<00:19:02.630> 24 00:19:03.129 --> 00:19:03.139 align:start position:0% give it like alright I want to last 24 00:19:03.139 --> 00:19:08.669 align:start position:0% give it like alright I want to last 24 bytes<00:19:04.750> if<00:19:05.750> there's<00:19:06.049> not<00:19:06.169> 24<00:19:06.679> bytes<00:19:06.860> available 00:19:08.669 --> 00:19:08.679 align:start position:0% bytes if there's not 24 bytes available 00:19:08.679 --> 00:19:11.799 align:start position:0% bytes if there's not 24 bytes available it<00:19:09.679> will<00:19:09.889> reverse<00:19:10.279> it<00:19:10.970> will<00:19:11.179> do<00:19:11.389> this<00:19:11.539> work<00:19:11.750> for 00:19:11.799 --> 00:19:11.809 align:start position:0% it will reverse it will do this work for 00:19:11.809 --> 00:19:15.789 align:start position:0% it will reverse it will do this work for you<00:19:12.639> which<00:19:13.639> means<00:19:13.909> basically<00:19:14.149> lives<00:19:14.720> you<00:19:15.649> can 00:19:15.789 --> 00:19:15.799 align:start position:0% you which means basically lives you can 00:19:15.799 --> 00:19:17.830 align:start position:0% you which means basically lives you can just<00:19:15.980> remove<00:19:16.190> this<00:19:16.370> and<00:19:16.610> the<00:19:17.330> program<00:19:17.690> of 00:19:17.830 --> 00:19:17.840 align:start position:0% just remove this and the program of 00:19:17.840 --> 00:19:22.990 align:start position:0% just remove this and the program of function<00:19:18.169> exactly<00:19:18.590> the<00:19:18.649> same<00:19:21.519> the<00:19:22.519> optimizer 00:19:22.990 --> 00:19:23.000 align:start position:0% function exactly the same the optimizer 00:19:23.000 --> 00:19:28.090 align:start position:0% function exactly the same the optimizer well<00:19:25.570> the<00:19:26.570> optimizer<00:19:27.080> works<00:19:27.380> by<00:19:27.649> looking<00:19:27.980> at 00:19:28.090 --> 00:19:28.100 align:start position:0% well the optimizer works by looking at 00:19:28.100 --> 00:19:29.440 align:start position:0% well the optimizer works by looking at your<00:19:28.250> opponent<00:19:28.639> right<00:19:28.760> to<00:19:28.940> figure<00:19:29.090> out<00:19:29.299> the 00:19:29.440 --> 00:19:29.450 align:start position:0% your opponent right to figure out the 00:19:29.450 --> 00:19:31.029 align:start position:0% your opponent right to figure out the best<00:19:29.659> way<00:19:29.899> to<00:19:29.929> schedule<00:19:30.380> it<00:19:30.470> but<00:19:30.649> it<00:19:30.740> doesn't 00:19:31.029 --> 00:19:31.039 align:start position:0% best way to schedule it but it doesn't 00:19:31.039 --> 00:19:34.200 align:start position:0% best way to schedule it but it doesn't really<00:19:31.190> understand<00:19:32.000> all<00:19:32.360> of<00:19:32.539> your<00:19:32.750> functions 00:19:34.200 --> 00:19:34.210 align:start position:0% really understand all of your functions 00:19:34.210 --> 00:19:39.070 align:start position:0% really understand all of your functions so<00:19:35.799> what<00:19:36.799> do<00:19:36.919> we<00:19:36.980> know<00:19:37.250> well<00:19:37.490> we<00:19:37.850> know<00:19:38.029> that<00:19:38.269> if 00:19:39.070 --> 00:19:39.080 align:start position:0% so what do we know well we know that if 00:19:39.080 --> 00:19:43.169 align:start position:0% so what do we know well we know that if we're<00:19:39.380> doing<00:19:39.710> the<00:19:40.610> transfer<00:19:41.210> we're<00:19:42.019> removing 00:19:43.169 --> 00:19:43.179 align:start position:0% we're doing the transfer we're removing 00:19:43.179 --> 00:19:47.470 align:start position:0% we're doing the transfer we're removing the<00:19:44.500> value<00:19:45.500> from<00:19:45.740> the<00:19:46.159> sender<00:19:47.059> and<00:19:47.090> we're 00:19:47.470 --> 00:19:47.480 align:start position:0% the value from the sender and we're 00:19:47.480 --> 00:19:49.269 align:start position:0% the value from the sender and we're giving<00:19:47.779> it<00:19:47.870> to<00:19:47.899> the<00:19:48.049> receiver<00:19:48.590> in<00:19:49.159> the 00:19:49.269 --> 00:19:49.279 align:start position:0% giving it to the receiver in the 00:19:49.279 --> 00:19:52.930 align:start position:0% giving it to the receiver in the original<00:19:49.789> code<00:19:49.970> we<00:19:50.690> were<00:19:50.809> first<00:19:51.789> loading<00:19:52.789> all 00:19:52.930 --> 00:19:52.940 align:start position:0% original code we were first loading all 00:19:52.940 --> 00:19:55.419 align:start position:0% original code we were first loading all the<00:19:52.970> data<00:19:53.389> I<00:19:53.690> mean<00:19:54.289> the<00:19:54.409> transfers<00:19:54.860> and<00:19:55.039> saving 00:19:55.419 --> 00:19:55.429 align:start position:0% the data I mean the transfers and saving 00:19:55.429 --> 00:19:55.880 align:start position:0% the data I mean the transfers and saving of 00:19:55.880 --> 00:19:55.890 align:start position:0% of 00:19:55.890 --> 00:19:58.280 align:start position:0% of instead<00:19:56.460> we<00:19:56.640> recognize<00:19:57.450> that<00:19:57.480> like<00:19:57.929> we<00:19:58.110> don't 00:19:58.280 --> 00:19:58.290 align:start position:0% instead we recognize that like we don't 00:19:58.290 --> 00:19:59.960 align:start position:0% instead we recognize that like we don't need<00:19:58.470> all<00:19:58.679> this<00:19:58.830> data<00:19:59.040> available<00:19:59.580> at<00:19:59.700> the<00:19:59.790> same 00:19:59.960 --> 00:19:59.970 align:start position:0% need all this data available at the same 00:19:59.970 --> 00:20:05.410 align:start position:0% need all this data available at the same time<00:20:01.220> we<00:20:02.220> can<00:20:02.660> note<00:20:03.660> the<00:20:03.980> sender's<00:20:04.980> value 00:20:05.410 --> 00:20:05.420 align:start position:0% time we can note the sender's value 00:20:05.420 --> 00:20:08.780 align:start position:0% time we can note the sender's value subtract<00:20:06.420> it<00:20:06.620> save<00:20:07.620> it<00:20:07.650> and<00:20:08.010> then<00:20:08.220> we<00:20:08.340> can<00:20:08.549> load 00:20:08.780 --> 00:20:08.790 align:start position:0% subtract it save it and then we can load 00:20:08.790 --> 00:20:11.660 align:start position:0% subtract it save it and then we can load the<00:20:09.059> receivers<00:20:09.809> value<00:20:10.170> add<00:20:10.470> it<00:20:10.740> and<00:20:10.920> save<00:20:11.640> it 00:20:11.660 --> 00:20:11.670 align:start position:0% the receivers value add it and save it 00:20:11.670 --> 00:20:14.080 align:start position:0% the receivers value add it and save it and<00:20:12.210> this<00:20:12.540> means<00:20:12.780> that<00:20:12.990> we<00:20:13.110> don't<00:20:13.230> have<00:20:13.440> to<00:20:13.590> use 00:20:14.080 --> 00:20:14.090 align:start position:0% and this means that we don't have to use 00:20:14.090 --> 00:20:23.410 align:start position:0% and this means that we don't have to use memories<00:20:16.309> for<00:20:17.309> both<00:20:17.580> these<00:20:17.970> operations<00:20:21.620> so 00:20:23.410 --> 00:20:23.420 align:start position:0% memories for both these operations so 00:20:23.420 --> 00:20:32.150 align:start position:0% memories for both these operations so what's<00:20:24.420> left<00:20:24.660> here<00:20:24.990> well<00:20:30.740> what's<00:20:31.740> left<00:20:31.799> here 00:20:32.150 --> 00:20:32.160 align:start position:0% what's left here well what's left here 00:20:32.160 --> 00:20:33.860 align:start position:0% what's left here well what's left here when<00:20:32.549> we've<00:20:32.700> done<00:20:32.730> all<00:20:33.000> these<00:20:33.120> optimizations 00:20:33.860 --> 00:20:33.870 align:start position:0% when we've done all these optimizations 00:20:33.870 --> 00:20:36.530 align:start position:0% when we've done all these optimizations like<00:20:34.020> we<00:20:34.169> have<00:20:34.290> your<00:20:34.470> contract<00:20:34.890> code<00:20:35.270> and<00:20:36.270> we 00:20:36.530 --> 00:20:36.540 align:start position:0% like we have your contract code and we 00:20:36.540 --> 00:20:38.750 align:start position:0% like we have your contract code and we have<00:20:36.780> this<00:20:36.900> big<00:20:37.200> engine<00:20:37.410> optimization<00:20:38.250> and 00:20:38.750 --> 00:20:38.760 align:start position:0% have this big engine optimization and 00:20:38.760 --> 00:20:40.430 align:start position:0% have this big engine optimization and then<00:20:39.090> we<00:20:39.210> never<00:20:39.330> do<00:20:39.570> a<00:20:39.600> craft<00:20:39.960> that<00:20:40.020> you<00:20:40.230> can't 00:20:40.430 --> 00:20:40.440 align:start position:0% then we never do a craft that you can't 00:20:40.440 --> 00:20:44.960 align:start position:0% then we never do a craft that you can't really<00:20:40.620> get<00:20:40.770> rid<00:20:40.919> of<00:20:42.799> this<00:20:43.799> is<00:20:43.980> the<00:20:44.160> way<00:20:44.730> that 00:20:44.960 --> 00:20:44.970 align:start position:0% really get rid of this is the way that 00:20:44.970 --> 00:20:48.200 align:start position:0% really get rid of this is the way that we<00:20:45.150> tell<00:20:45.860> our<00:20:46.860> contract<00:20:47.429> about<00:20:47.910> the 00:20:48.200 --> 00:20:48.210 align:start position:0% we tell our contract about the 00:20:48.210 --> 00:20:52.400 align:start position:0% we tell our contract about the environment<00:20:49.730> part<00:20:50.730> of<00:20:50.790> the<00:20:50.880> space<00:20:51.210> so<00:20:51.510> if<00:20:52.290> you 00:20:52.400 --> 00:20:52.410 align:start position:0% environment part of the space so if you 00:20:52.410 --> 00:20:56.060 align:start position:0% environment part of the space so if you listen<00:20:52.770> to<00:20:53.000> Paul's<00:20:54.860> presentation<00:20:55.860> you<00:20:56.010> would 00:20:56.060 --> 00:20:56.070 align:start position:0% listen to Paul's presentation you would 00:20:56.070 --> 00:20:57.950 align:start position:0% listen to Paul's presentation you would know<00:20:56.280> that<00:20:56.309> we<00:20:56.610> can<00:20:56.760> also<00:20:56.880> compress<00:20:57.390> your 00:20:57.950 --> 00:20:57.960 align:start position:0% know that we can also compress your 00:20:57.960 --> 00:21:05.510 align:start position:0% know that we can also compress your contract<00:20:58.440> using<00:21:00.020> save<00:21:04.190> but<00:21:05.190> the<00:21:05.309> quick 00:21:05.510 --> 00:21:05.520 align:start position:0% contract using save but the quick 00:21:05.520 --> 00:21:07.669 align:start position:0% contract using save but the quick summary<00:21:05.910> here<00:21:05.940> is<00:21:06.270> that<00:21:06.450> like<00:21:06.630> no<00:21:07.110> every<00:21:07.440> step 00:21:07.669 --> 00:21:07.679 align:start position:0% summary here is that like no every step 00:21:07.679 --> 00:21:11.180 align:start position:0% summary here is that like no every step of<00:21:07.830> your<00:21:08.480> of<00:21:09.480> your<00:21:09.570> pipeline<00:21:10.140> and<00:21:10.320> you<00:21:10.410> can<00:21:10.679> use 00:21:11.180 --> 00:21:11.190 align:start position:0% of your of your pipeline and you can use 00:21:11.190 --> 00:21:17.289 align:start position:0% of your of your pipeline and you can use the<00:21:11.429> knowledge<00:21:11.809> across<00:21:12.809> the<00:21:12.960> board<00:21:14.960> all<00:21:15.960> right 00:21:17.289 --> 00:21:17.299 align:start position:0% the knowledge across the board all right 00:21:17.299 --> 00:21:19.410 align:start position:0% the knowledge across the board all right all<00:21:18.299> right<00:21:18.360> there<00:21:18.690> we<00:21:18.750> go 00:21:19.410 --> 00:21:19.420 align:start position:0% all right there we go 00:21:19.420 --> 00:21:23.830 align:start position:0% all right there we go [Music] 00:21:23.830 --> 00:21:23.840 align:start position:0% 00:21:23.840 --> 00:21:30.140 align:start position:0% [Applause]