WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:13.990 align:start position:0% [Applause] 00:00:13.990 --> 00:00:14.000 align:start position:0% 00:00:14.000 --> 00:00:15.480 align:start position:0% [Music] 00:00:15.480 --> 00:00:15.490 align:start position:0% [Music] 00:00:15.490 --> 00:00:18.370 align:start position:0% [Music] this<00:00:16.490> is<00:00:16.580> Harry's<00:00:16.940> hello<00:00:17.510> we<00:00:18.080> work<00:00:18.230> on 00:00:18.370 --> 00:00:18.380 align:start position:0% this is Harry's hello we work on 00:00:18.380 --> 00:00:22.630 align:start position:0% this is Harry's hello we work on truffles<00:00:18.800> and<00:00:19.730> I<00:00:19.880> wasn't<00:00:20.210> about<00:00:20.360> your<00:00:20.510> guy 00:00:22.630 --> 00:00:22.640 align:start position:0% truffles and I wasn't about your guy 00:00:22.640 --> 00:00:25.060 align:start position:0% truffles and I wasn't about your guy we<00:00:23.300> decide<00:00:23.930> you<00:00:23.990> gonna<00:00:24.259> get<00:00:24.380> through<00:00:24.590> then 00:00:25.060 --> 00:00:25.070 align:start position:0% we decide you gonna get through then 00:00:25.070 --> 00:00:26.319 align:start position:0% we decide you gonna get through then we're<00:00:25.160> gonna<00:00:25.250> talk<00:00:25.550> about<00:00:25.579> the<00:00:25.849> current<00:00:26.150> state 00:00:26.319 --> 00:00:26.329 align:start position:0% we're gonna talk about the current state 00:00:26.329 --> 00:00:28.540 align:start position:0% we're gonna talk about the current state of<00:00:26.390> smart<00:00:26.720> contractor<00:00:27.230> baggage<00:00:27.560> I<00:00:28.130> just<00:00:28.340> gonna 00:00:28.540 --> 00:00:28.550 align:start position:0% of smart contractor baggage I just gonna 00:00:28.550 --> 00:00:30.580 align:start position:0% of smart contractor baggage I just gonna talk<00:00:28.759> about<00:00:28.880> debugging<00:00:29.720> data<00:00:29.899> formats<00:00:30.320> what 00:00:30.580 --> 00:00:30.590 align:start position:0% talk about debugging data formats what 00:00:30.590 --> 00:00:31.720 align:start position:0% talk about debugging data formats what are<00:00:30.739> they<00:00:30.890> what<00:00:31.160> do<00:00:31.220> they<00:00:31.310> do 00:00:31.720 --> 00:00:31.730 align:start position:0% are they what do they do 00:00:31.730 --> 00:00:34.479 align:start position:0% are they what do they do why<00:00:32.119> does<00:00:32.419> every<00:00:32.960> other<00:00:33.470> computing<00:00:34.130> platform 00:00:34.479 --> 00:00:34.489 align:start position:0% why does every other computing platform 00:00:34.489 --> 00:00:37.090 align:start position:0% why does every other computing platform use<00:00:34.610> them<00:00:34.820> and<00:00:35.649> we're<00:00:36.649> going<00:00:36.770> to<00:00:36.829> talk<00:00:36.980> about 00:00:37.090 --> 00:00:37.100 align:start position:0% use them and we're going to talk about 00:00:37.100 --> 00:00:38.670 align:start position:0% use them and we're going to talk about some<00:00:37.309> of<00:00:37.370> the<00:00:37.460> design<00:00:37.670> challenges<00:00:38.270> with 00:00:38.670 --> 00:00:38.680 align:start position:0% some of the design challenges with 00:00:38.680 --> 00:00:41.110 align:start position:0% some of the design challenges with coming<00:00:39.680> from<00:00:39.710> a<00:00:39.860> solidity<00:00:40.250> perspective<00:00:40.910> but 00:00:41.110 --> 00:00:41.120 align:start position:0% coming from a solidity perspective but 00:00:41.120 --> 00:00:43.779 align:start position:0% coming from a solidity perspective but for<00:00:41.480> smart<00:00:41.719> contracts<00:00:42.170> in<00:00:42.320> general<00:00:42.789> then 00:00:43.779 --> 00:00:43.789 align:start position:0% for smart contracts in general then 00:00:43.789 --> 00:00:46.810 align:start position:0% for smart contracts in general then we're<00:00:44.420> gonna<00:00:44.510> make<00:00:44.660> this<00:00:44.809> interactive<00:00:45.109> so<00:00:45.949> it 00:00:46.810 --> 00:00:46.820 align:start position:0% we're gonna make this interactive so it 00:00:46.820 --> 00:00:48.729 align:start position:0% we're gonna make this interactive so it is<00:00:47.030> a<00:00:47.089> hopefully<00:00:47.929> we'll<00:00:48.079> break<00:00:48.230> into<00:00:48.410> groups 00:00:48.729 --> 00:00:48.739 align:start position:0% is a hopefully we'll break into groups 00:00:48.739 --> 00:00:51.130 align:start position:0% is a hopefully we'll break into groups and<00:00:49.039> kind<00:00:49.609> of<00:00:49.640> talk<00:00:49.820> about<00:00:50.089> what<00:00:50.269> would<00:00:50.390> it<00:00:50.510> one 00:00:51.130 --> 00:00:51.140 align:start position:0% and kind of talk about what would it one 00:00:51.140 --> 00:00:53.110 align:start position:0% and kind of talk about what would it one of<00:00:51.230> these<00:00:51.370> debugging<00:00:52.370> data<00:00:52.519> formats<00:00:52.879> look 00:00:53.110 --> 00:00:53.120 align:start position:0% of these debugging data formats look 00:00:53.120 --> 00:00:57.790 align:start position:0% of these debugging data formats look like<00:00:53.980> we'll<00:00:54.980> see<00:00:55.640> if<00:00:55.760> people<00:00:55.910> are<00:00:56.589> not<00:00:57.589> too 00:00:57.790 --> 00:00:57.800 align:start position:0% like we'll see if people are not too 00:00:57.800 --> 00:01:00.279 align:start position:0% like we'll see if people are not too afraid<00:00:57.980> to<00:00:58.070> share<00:00:58.280> their<00:00:58.460> findings<00:00:59.289> then 00:01:00.279 --> 00:01:00.289 align:start position:0% afraid to share their findings then 00:01:00.289 --> 00:01:01.930 align:start position:0% afraid to share their findings then we'll<00:01:00.440> talk<00:01:00.679> about<00:01:00.829> specific<00:01:01.370> areas<00:01:01.670> of<00:01:01.789> work 00:01:01.930 --> 00:01:01.940 align:start position:0% we'll talk about specific areas of work 00:01:01.940 --> 00:01:04.060 align:start position:0% we'll talk about specific areas of work like<00:01:02.749> what<00:01:02.960> one<00:01:03.469> of<00:01:03.499> the<00:01:03.649> specific<00:01:03.829> challenges 00:01:04.060 --> 00:01:04.070 align:start position:0% like what one of the specific challenges 00:01:04.070 --> 00:01:05.439 align:start position:0% like what one of the specific challenges is<00:01:04.550> not<00:01:04.580> from<00:01:04.790> a<00:01:04.850> high<00:01:04.970> level<00:01:05.300> but 00:01:05.439 --> 00:01:05.449 align:start position:0% is not from a high level but 00:01:05.449 --> 00:01:09.330 align:start position:0% is not from a high level but specifically<00:01:06.370> break<00:01:07.370> into<00:01:07.550> groups<00:01:07.580> again<00:01:08.030> and 00:01:09.330 --> 00:01:09.340 align:start position:0% specifically break into groups again and 00:01:09.340 --> 00:01:13.149 align:start position:0% specifically break into groups again and now<00:01:10.340> settings<00:01:11.060> again<00:01:11.650> no<00:01:12.650> one<00:01:12.770> ever<00:01:12.890> want<00:01:13.100> to 00:01:13.149 --> 00:01:13.159 align:start position:0% now settings again no one ever want to 00:01:13.159 --> 00:01:19.630 align:start position:0% now settings again no one ever want to go 00:01:19.630 --> 00:01:19.640 align:start position:0% 00:01:19.640 --> 00:01:24.500 align:start position:0% it's<00:01:20.640> trying<00:01:22.190> and<00:01:23.190> then<00:01:23.370> we'll<00:01:23.490> complete<00:01:23.820> so 00:01:24.500 --> 00:01:24.510 align:start position:0% it's trying and then we'll complete so 00:01:24.510 --> 00:01:28.820 align:start position:0% it's trying and then we'll complete so you<00:01:25.320> see<00:01:25.470> how<00:01:25.530> this<00:01:25.710> all<00:01:25.890> goes<00:01:27.650> did<00:01:28.650> that 00:01:28.820 --> 00:01:28.830 align:start position:0% you see how this all goes did that 00:01:28.830 --> 00:01:50.910 align:start position:0% you see how this all goes did that already<00:01:28.979> hurt<00:01:29.370> they<00:01:29.640> lost<00:01:29.850> ischemic<00:01:30.300> our<00:01:30.630> code 00:01:50.910 --> 00:01:50.920 align:start position:0% 00:01:50.920 --> 00:01:54.620 align:start position:0% [Music] 00:01:54.620 --> 00:01:54.630 align:start position:0% 00:01:54.630 --> 00:01:56.820 align:start position:0% now<00:01:55.630> thumbs<00:01:56.200> down 00:01:56.820 --> 00:01:56.830 align:start position:0% now thumbs down 00:01:56.830 --> 00:01:59.550 align:start position:0% now thumbs down great<00:01:57.280> let's<00:01:57.909> do<00:01:58.180> bugging<00:01:58.450> like<00:01:58.630> on<00:01:59.020> aetherium 00:01:59.550 --> 00:01:59.560 align:start position:0% great let's do bugging like on aetherium 00:01:59.560 --> 00:02:04.469 align:start position:0% great let's do bugging like on aetherium today<00:02:00.330> well<00:02:02.610> we<00:02:03.610> have<00:02:03.759> solidity<00:02:04.119> source 00:02:04.469 --> 00:02:04.479 align:start position:0% today well we have solidity source 00:02:04.479 --> 00:02:07.139 align:start position:0% today well we have solidity source mappings<00:02:04.930> these<00:02:05.140> are<00:02:05.290> extremely<00:02:05.860> useful<00:02:06.280> they 00:02:07.139 --> 00:02:07.149 align:start position:0% mappings these are extremely useful they 00:02:07.149 --> 00:02:11.309 align:start position:0% mappings these are extremely useful they are<00:02:07.180> fantastic<00:02:09.360> you<00:02:10.360> have<00:02:10.539> some<00:02:10.959> bike<00:02:11.110> coats 00:02:11.309 --> 00:02:11.319 align:start position:0% are fantastic you have some bike coats 00:02:11.319 --> 00:02:14.550 align:start position:0% are fantastic you have some bike coats literally<00:02:11.739> gives<00:02:11.890> us<00:02:12.040> bytecode<00:02:12.459> by<00:02:13.420> codes<00:02:13.690> we 00:02:14.550 --> 00:02:14.560 align:start position:0% literally gives us bytecode by codes we 00:02:14.560 --> 00:02:16.220 align:start position:0% literally gives us bytecode by codes we can<00:02:14.709> model<00:02:14.950> it<00:02:15.010> as<00:02:15.160> a<00:02:15.190> list<00:02:15.459> of<00:02:15.580> instructions 00:02:16.220 --> 00:02:16.230 align:start position:0% can model it as a list of instructions 00:02:16.230 --> 00:02:19.380 align:start position:0% can model it as a list of instructions and<00:02:17.459> it's<00:02:18.459> literally<00:02:18.670> gives<00:02:18.850> us<00:02:18.970> these<00:02:19.120> source 00:02:19.380 --> 00:02:19.390 align:start position:0% and it's literally gives us these source 00:02:19.390 --> 00:02:20.820 align:start position:0% and it's literally gives us these source mappings<00:02:19.840> which<00:02:20.050> correspond<00:02:20.650> to<00:02:20.739> a 00:02:20.820 --> 00:02:20.830 align:start position:0% mappings which correspond to a 00:02:20.830 --> 00:02:23.130 align:start position:0% mappings which correspond to a particular<00:02:21.010> byte<00:02:21.610> code<00:02:21.849> and<00:02:22.360> we<00:02:22.750> think<00:02:22.989> of<00:02:23.050> it 00:02:23.130 --> 00:02:23.140 align:start position:0% particular byte code and we think of it 00:02:23.140 --> 00:02:24.570 align:start position:0% particular byte code and we think of it like<00:02:23.290> an<00:02:23.380> array<00:02:23.590> there's<00:02:24.310> an<00:02:24.370> array<00:02:24.550> of 00:02:24.570 --> 00:02:24.580 align:start position:0% like an array there's an array of 00:02:24.580 --> 00:02:26.309 align:start position:0% like an array there's an array of instructions<00:02:25.209> and<00:02:25.780> there's<00:02:26.019> an<00:02:26.110> array<00:02:26.290> of 00:02:26.309 --> 00:02:26.319 align:start position:0% instructions and there's an array of 00:02:26.319 --> 00:02:28.740 align:start position:0% instructions and there's an array of source<00:02:26.620> maps<00:02:27.000> and<00:02:28.000> for<00:02:28.150> each<00:02:28.269> of<00:02:28.420> the<00:02:28.480> entries 00:02:28.740 --> 00:02:28.750 align:start position:0% source maps and for each of the entries 00:02:28.750 --> 00:02:31.890 align:start position:0% source maps and for each of the entries in<00:02:28.870> the<00:02:29.200> source<00:02:29.470> map<00:02:30.299> it<00:02:31.299> corresponds<00:02:31.720> to<00:02:31.780> the 00:02:31.890 --> 00:02:31.900 align:start position:0% in the source map it corresponds to the 00:02:31.900 --> 00:02:33.690 align:start position:0% in the source map it corresponds to the one<00:02:32.019> byte<00:02:32.230> code<00:02:32.470> you<00:02:33.040> know<00:02:33.130> the<00:02:33.250> corresponding 00:02:33.690 --> 00:02:33.700 align:start position:0% one byte code you know the corresponding 00:02:33.700 --> 00:02:36.930 align:start position:0% one byte code you know the corresponding byte<00:02:34.060> code<00:02:34.299> instruction<00:02:35.260> and<00:02:35.500> it<00:02:36.220> tells<00:02:36.760> you 00:02:36.930 --> 00:02:36.940 align:start position:0% byte code instruction and it tells you 00:02:36.940 --> 00:02:39.420 align:start position:0% byte code instruction and it tells you the<00:02:37.120> file<00:02:37.420> the<00:02:37.840> end<00:02:38.019> the<00:02:38.110> source<00:02:38.290> range<00:02:38.560> and 00:02:39.420 --> 00:02:39.430 align:start position:0% the file the end the source range and 00:02:39.430 --> 00:02:40.590 align:start position:0% the file the end the source range and some<00:02:39.610> other<00:02:39.760> stuff<00:02:40.000> I<00:02:40.120> don't<00:02:40.269> fit<00:02:40.390> into<00:02:40.510> that 00:02:40.590 --> 00:02:40.600 align:start position:0% some other stuff I don't fit into that 00:02:40.600 --> 00:02:43.140 align:start position:0% some other stuff I don't fit into that then<00:02:41.410> what<00:02:41.560> you<00:02:41.650> can<00:02:41.769> do<00:02:41.920> is<00:02:42.190> you<00:02:42.610> can<00:02:42.760> take 00:02:43.140 --> 00:02:43.150 align:start position:0% then what you can do is you can take 00:02:43.150 --> 00:02:44.729 align:start position:0% then what you can do is you can take this<00:02:43.360> source<00:02:43.660> map<00:02:43.900> you<00:02:44.170> can<00:02:44.290> take<00:02:44.470> the<00:02:44.590> byte 00:02:44.729 --> 00:02:44.739 align:start position:0% this source map you can take the byte 00:02:44.739 --> 00:02:46.500 align:start position:0% this source map you can take the byte code<00:02:44.769> and<00:02:45.370> you<00:02:45.430> have<00:02:45.580> some<00:02:45.819> running<00:02:46.120> program 00:02:46.500 --> 00:02:46.510 align:start position:0% code and you have some running program 00:02:46.510 --> 00:02:47.850 align:start position:0% code and you have some running program that<00:02:46.660> you're<00:02:46.780> looking<00:02:47.049> at<00:02:47.140> you<00:02:47.290> can<00:02:47.410> get<00:02:47.560> the 00:02:47.850 --> 00:02:47.860 align:start position:0% that you're looking at you can get the 00:02:47.860 --> 00:02:49.800 align:start position:0% that you're looking at you can get the trace<00:02:48.100> you<00:02:48.549> know<00:02:49.000> you<00:02:49.120> look<00:02:49.269> at<00:02:49.390> the<00:02:49.540> execution 00:02:49.800 --> 00:02:49.810 align:start position:0% trace you know you look at the execution 00:02:49.810 --> 00:02:52.559 align:start position:0% trace you know you look at the execution of<00:02:50.200> your<00:02:50.350> smart<00:02:50.590> contract<00:02:51.250> transaction<00:02:51.880> you 00:02:52.559 --> 00:02:52.569 align:start position:0% of your smart contract transaction you 00:02:52.569 --> 00:02:53.580 align:start position:0% of your smart contract transaction you see<00:02:52.720> everything<00:02:53.049> that<00:02:53.140> happened<00:02:53.440> on<00:02:53.470> the 00:02:53.580 --> 00:02:53.590 align:start position:0% see everything that happened on the 00:02:53.590 --> 00:02:55.590 align:start position:0% see everything that happened on the opcodes<00:02:53.950> and<00:02:54.100> you<00:02:54.220> get<00:02:54.370> this<00:02:54.880> company<00:02:55.239> called 00:02:55.590 --> 00:02:55.600 align:start position:0% opcodes and you get this company called 00:02:55.600 --> 00:02:57.900 align:start position:0% opcodes and you get this company called a<00:02:55.690> program<00:02:56.140> counter<00:02:56.380> the<00:02:57.220> program<00:02:57.519> counter<00:02:57.700> is 00:02:57.900 --> 00:02:57.910 align:start position:0% a program counter the program counter is 00:02:57.910 --> 00:03:00.330 align:start position:0% a program counter the program counter is where<00:02:58.690> where<00:02:59.290> am<00:02:59.500> i<00:02:59.650> and<00:02:59.680> the<00:03:00.010> currently 00:03:00.330 --> 00:03:00.340 align:start position:0% where where am i and the currently 00:03:00.340 --> 00:03:02.759 align:start position:0% where where am i and the currently executing<00:03:00.510> contents<00:03:01.510> what<00:03:02.350> you<00:03:02.440> do<00:03:02.560> is<00:03:02.680> you 00:03:02.759 --> 00:03:02.769 align:start position:0% executing contents what you do is you 00:03:02.769 --> 00:03:04.949 align:start position:0% executing contents what you do is you take<00:03:02.950> the<00:03:03.070> program<00:03:03.400> counter<00:03:03.579> you<00:03:04.390> convert<00:03:04.750> you 00:03:04.949 --> 00:03:04.959 align:start position:0% take the program counter you convert you 00:03:04.959 --> 00:03:06.840 align:start position:0% take the program counter you convert you figure<00:03:05.230> out<00:03:05.290> which<00:03:05.650> bytecode<00:03:06.250> instruction 00:03:06.840 --> 00:03:06.850 align:start position:0% figure out which bytecode instruction 00:03:06.850 --> 00:03:09.539 align:start position:0% figure out which bytecode instruction that<00:03:06.970> refers<00:03:07.269> to<00:03:07.590> so<00:03:08.590> if<00:03:08.680> you<00:03:08.739> have<00:03:08.890> you<00:03:09.459> know 00:03:09.539 --> 00:03:09.549 align:start position:0% that refers to so if you have you know 00:03:09.549 --> 00:03:10.830 align:start position:0% that refers to so if you have you know you're<00:03:09.730> a<00:03:09.760> program<00:03:10.060> counter<00:03:10.209> ten<00:03:10.600> maybe 00:03:10.830 --> 00:03:10.840 align:start position:0% you're a program counter ten maybe 00:03:10.840 --> 00:03:12.360 align:start position:0% you're a program counter ten maybe that's<00:03:11.109> wherever<00:03:11.890> it<00:03:11.980> is<00:03:12.070> in<00:03:12.130> the<00:03:12.220> bytecode 00:03:12.360 --> 00:03:12.370 align:start position:0% that's wherever it is in the bytecode 00:03:12.370 --> 00:03:13.830 align:start position:0% that's wherever it is in the bytecode you<00:03:12.700> find<00:03:12.910> out<00:03:13.030> what<00:03:13.180> instruction<00:03:13.630> number 00:03:13.830 --> 00:03:13.840 align:start position:0% you find out what instruction number 00:03:13.840 --> 00:03:16.979 align:start position:0% you find out what instruction number that<00:03:13.959> is<00:03:14.109> then<00:03:14.890> you<00:03:15.130> take<00:03:15.940> that<00:03:15.970> index<00:03:16.450> I<00:03:16.750> or 00:03:16.979 --> 00:03:16.989 align:start position:0% that is then you take that index I or 00:03:16.989 --> 00:03:19.560 align:start position:0% that is then you take that index I or whatever<00:03:17.260> you<00:03:17.799> go<00:03:17.950> to<00:03:18.010> the<00:03:18.100> source<00:03:18.340> map<00:03:18.579> that 00:03:19.560 --> 00:03:19.570 align:start position:0% whatever you go to the source map that 00:03:19.570 --> 00:03:21.390 align:start position:0% whatever you go to the source map that tells<00:03:19.660> you<00:03:19.810> what<00:03:19.900> you<00:03:19.930> need<00:03:20.109> to<00:03:20.200> know<00:03:20.400> so 00:03:21.390 --> 00:03:21.400 align:start position:0% tells you what you need to know so 00:03:21.400 --> 00:03:24.390 align:start position:0% tells you what you need to know so that's<00:03:21.459> pretty<00:03:22.120> handy<00:03:23.130> truffles<00:03:24.130> are<00:03:24.220> always 00:03:24.390 --> 00:03:24.400 align:start position:0% that's pretty handy truffles are always 00:03:24.400 --> 00:03:25.860 align:start position:0% that's pretty handy truffles are always version<00:03:24.730> of<00:03:24.790> our<00:03:24.880> debugger<00:03:25.150> that's<00:03:25.630> all<00:03:25.780> it 00:03:25.860 --> 00:03:25.870 align:start position:0% version of our debugger that's all it 00:03:25.870 --> 00:03:27.650 align:start position:0% version of our debugger that's all it did<00:03:25.989> is<00:03:26.410> it<00:03:26.470> translated<00:03:26.950> from<00:03:27.160> the<00:03:27.340> low-level 00:03:27.650 --> 00:03:27.660 align:start position:0% did is it translated from the low-level 00:03:27.660 --> 00:03:30.660 align:start position:0% did is it translated from the low-level evm<00:03:28.660> opcode<00:03:29.109> instructions<00:03:29.739> up<00:03:30.340> to<00:03:30.579> the 00:03:30.660 --> 00:03:30.670 align:start position:0% evm opcode instructions up to the 00:03:30.670 --> 00:03:33.990 align:start position:0% evm opcode instructions up to the high-level<00:03:30.820> source 00:03:33.990 --> 00:03:34.000 align:start position:0% 00:03:34.000 --> 00:03:36.250 align:start position:0% this<00:03:35.000> is<00:03:35.120> what<00:03:35.270> all<00:03:35.540> of<00:03:35.660> these<00:03:35.780> markets<00:03:35.990> do 00:03:36.250 --> 00:03:36.260 align:start position:0% this is what all of these markets do 00:03:36.260 --> 00:03:37.900 align:start position:0% this is what all of these markets do these<00:03:36.470> are<00:03:36.620> the<00:03:36.709> three<00:03:36.950> dividers<00:03:37.340> that<00:03:37.370> I<00:03:37.760> am 00:03:37.900 --> 00:03:37.910 align:start position:0% these are the three dividers that I am 00:03:37.910 --> 00:03:40.360 align:start position:0% these are the three dividers that I am aware<00:03:38.150> of<00:03:38.360> or<00:03:38.870> solidity<00:03:39.319> I<00:03:39.620> don't<00:03:40.069> think<00:03:40.250> there 00:03:40.360 --> 00:03:40.370 align:start position:0% aware of or solidity I don't think there 00:03:40.370 --> 00:03:42.100 align:start position:0% aware of or solidity I don't think there are<00:03:40.490> any<00:03:40.910> other<00:03:41.180> high-level<00:03:41.450> Imperium 00:03:42.100 --> 00:03:42.110 align:start position:0% are any other high-level Imperium 00:03:42.110 --> 00:03:43.680 align:start position:0% are any other high-level Imperium languages<00:03:42.560> that<00:03:42.709> have<00:03:42.920> debuggers<00:03:43.430> today 00:03:43.680 --> 00:03:43.690 align:start position:0% languages that have debuggers today 00:03:43.690 --> 00:03:45.970 align:start position:0% languages that have debuggers today apologies<00:03:44.690> if<00:03:45.110> I'm<00:03:45.319> missing<00:03:45.470> something 00:03:45.970 --> 00:03:45.980 align:start position:0% apologies if I'm missing something 00:03:45.980 --> 00:03:48.610 align:start position:0% apologies if I'm missing something that's<00:03:46.340> hard<00:03:46.670> work<00:03:46.790> to<00:03:47.030> build<00:03:47.870> a<00:03:47.990> debugger<00:03:48.290> so 00:03:48.610 --> 00:03:48.620 align:start position:0% that's hard work to build a debugger so 00:03:48.620 --> 00:03:51.820 align:start position:0% that's hard work to build a debugger so I<00:03:48.650> hate<00:03:48.890> to<00:03:48.920> leave<00:03:49.340> anyone<00:03:49.670> out<00:03:50.590> but<00:03:51.590> we<00:03:51.709> have 00:03:51.820 --> 00:03:51.830 align:start position:0% I hate to leave anyone out but we have 00:03:51.830 --> 00:03:54.490 align:start position:0% I hate to leave anyone out but we have trouble<00:03:52.100> debugger<00:03:53.020> capitalist<00:03:54.020> not<00:03:54.200> my<00:03:54.319> first 00:03:54.490 --> 00:03:54.500 align:start position:0% trouble debugger capitalist not my first 00:03:54.500 --> 00:03:57.430 align:start position:0% trouble debugger capitalist not my first remix<00:03:54.980> has<00:03:55.190> a<00:03:55.220> debugger<00:03:55.550> and<00:03:55.910> the<00:03:56.870> meadowsweet 00:03:57.430 --> 00:03:57.440 align:start position:0% remix has a debugger and the meadowsweet 00:03:57.440 --> 00:04:08.620 align:start position:0% remix has a debugger and the meadowsweet has<00:03:57.709> the<00:03:57.860> debugger<00:04:03.580> so<00:04:04.580> these<00:04:05.300> do<00:04:05.860> well<00:04:07.630> they 00:04:08.620 --> 00:04:08.630 align:start position:0% has the debugger so these do well they 00:04:08.630 --> 00:04:11.380 align:start position:0% has the debugger so these do well they figure<00:04:09.440> out<00:04:09.500> how<00:04:09.830> solidity<00:04:10.400> works<00:04:10.730> through 00:04:11.380 --> 00:04:11.390 align:start position:0% figure out how solidity works through 00:04:11.390 --> 00:04:16.810 align:start position:0% figure out how solidity works through trial<00:04:11.720> and<00:04:11.840> error<00:04:11.989> and<00:04:15.280> yeah<00:04:16.280> well<00:04:16.730> so 00:04:16.810 --> 00:04:16.820 align:start position:0% trial and error and yeah well so 00:04:16.820 --> 00:04:18.310 align:start position:0% trial and error and yeah well so literally<00:04:17.060> does<00:04:17.239> document<00:04:17.690> quite<00:04:17.900> a<00:04:17.930> lot<00:04:18.109> like 00:04:18.310 --> 00:04:18.320 align:start position:0% literally does document quite a lot like 00:04:18.320 --> 00:04:20.770 align:start position:0% literally does document quite a lot like storage<00:04:18.980> allocation<00:04:19.239> program<00:04:20.239> does<00:04:20.630> not 00:04:20.770 --> 00:04:20.780 align:start position:0% storage allocation program does not 00:04:20.780 --> 00:04:22.300 align:start position:0% storage allocation program does not figure<00:04:20.989> things<00:04:21.290> out<00:04:21.380> the<00:04:21.620> fraud<00:04:21.829> letter<00:04:22.070> do 00:04:22.300 --> 00:04:22.310 align:start position:0% figure things out the fraud letter do 00:04:22.310 --> 00:04:24.370 align:start position:0% figure things out the fraud letter do you<00:04:22.490> built<00:04:22.880> the<00:04:23.090> program<00:04:23.360> figure<00:04:23.990> things<00:04:24.230> out 00:04:24.370 --> 00:04:24.380 align:start position:0% you built the program figure things out 00:04:24.380 --> 00:04:26.800 align:start position:0% you built the program figure things out right<00:04:24.770> yeah<00:04:25.340> so<00:04:25.669> we<00:04:25.820> can't<00:04:26.060> decide<00:04:26.360> travels 00:04:26.800 --> 00:04:26.810 align:start position:0% right yeah so we can't decide travels 00:04:26.810 --> 00:04:29.560 align:start position:0% right yeah so we can't decide travels debugger<00:04:27.220> how<00:04:28.220> do<00:04:28.280> you<00:04:28.460> figure<00:04:28.760> out<00:04:28.940> what<00:04:29.360> a 00:04:29.560 --> 00:04:29.570 align:start position:0% debugger how do you figure out what a 00:04:29.570 --> 00:04:34.540 align:start position:0% debugger how do you figure out what a variable<00:04:30.140> is<00:04:32.650> well<00:04:33.650> you<00:04:34.070> observe<00:04:34.310> it<00:04:34.400> in<00:04:34.460> the 00:04:34.540 --> 00:04:34.550 align:start position:0% variable is well you observe it in the 00:04:34.550 --> 00:04:38.020 align:start position:0% variable is well you observe it in the wild<00:04:34.960> and<00:04:36.250> the<00:04:37.250> reason<00:04:37.550> for<00:04:37.580> that<00:04:37.729> is<00:04:37.940> because 00:04:38.020 --> 00:04:38.030 align:start position:0% wild and the reason for that is because 00:04:38.030 --> 00:04:41.170 align:start position:0% wild and the reason for that is because solidity<00:04:38.450> is<00:04:38.600> no<00:04:38.720> way<00:04:38.810> of<00:04:38.870> telling<00:04:39.080> us<00:04:40.180> so 00:04:41.170 --> 00:04:41.180 align:start position:0% solidity is no way of telling us so 00:04:41.180 --> 00:04:45.300 align:start position:0% solidity is no way of telling us so hopefully<00:04:41.780> we'll<00:04:41.930> change<00:04:42.110> that<00:04:43.090> we're<00:04:44.090> down 00:04:45.300 --> 00:04:45.310 align:start position:0% hopefully we'll change that we're down 00:04:45.310 --> 00:04:49.960 align:start position:0% hopefully we'll change that we're down great<00:04:47.470> so<00:04:48.470> of<00:04:49.070> course<00:04:49.250> it's<00:04:49.640> not<00:04:49.729> like 00:04:49.960 --> 00:04:49.970 align:start position:0% great so of course it's not like 00:04:49.970 --> 00:04:51.640 align:start position:0% great so of course it's not like solidity<00:04:50.360> gives<00:04:50.600> us<00:04:50.720> nothing<00:04:50.960> because<00:04:51.440> that 00:04:51.640 --> 00:04:51.650 align:start position:0% solidity gives us nothing because that 00:04:51.650 --> 00:04:53.529 align:start position:0% solidity gives us nothing because that mean<00:04:51.800> truly<00:04:52.160> would<00:04:52.490> be<00:04:52.669> pretty<00:04:53.270> stuck 00:04:53.529 --> 00:04:53.539 align:start position:0% mean truly would be pretty stuck 00:04:53.539 --> 00:04:55.659 align:start position:0% mean truly would be pretty stuck hopefully<00:04:54.050> it<00:04:54.140> does<00:04:54.320> give<00:04:54.530> us<00:04:54.650> the<00:04:54.890> abstracts 00:04:55.659 --> 00:04:55.669 align:start position:0% hopefully it does give us the abstracts 00:04:55.669 --> 00:04:56.350 align:start position:0% hopefully it does give us the abstracts and<00:04:55.820> texture 00:04:56.350 --> 00:04:56.360 align:start position:0% and texture 00:04:56.360 --> 00:05:01.480 align:start position:0% and texture and<00:04:58.960> so<00:04:59.960> you<00:05:00.710> know<00:05:00.830> for<00:05:01.039> those<00:05:01.129> who<00:05:01.310> are<00:05:01.370> not 00:05:01.480 --> 00:05:01.490 align:start position:0% and so you know for those who are not 00:05:01.490 --> 00:05:03.399 align:start position:0% and so you know for those who are not familiar<00:05:01.639> right<00:05:02.090> you<00:05:02.240> parse<00:05:02.539> the<00:05:02.720> code<00:05:02.930> into 00:05:03.399 --> 00:05:03.409 align:start position:0% familiar right you parse the code into 00:05:03.409 --> 00:05:06.070 align:start position:0% familiar right you parse the code into it<00:05:03.530> into<00:05:04.099> a<00:05:04.220> structured<00:05:04.759> tree<00:05:05.120> which<00:05:05.629> contains 00:05:06.070 --> 00:05:06.080 align:start position:0% it into a structured tree which contains 00:05:06.080 --> 00:05:08.020 align:start position:0% it into a structured tree which contains all<00:05:06.439> the<00:05:07.069> loops<00:05:07.400> to<00:05:07.460> contain<00:05:07.819> all<00:05:08.000> the 00:05:08.020 --> 00:05:08.030 align:start position:0% all the loops to contain all the 00:05:08.030 --> 00:05:10.059 align:start position:0% all the loops to contain all the information<00:05:08.150> and<00:05:08.990> it's<00:05:09.469> you<00:05:09.590> know<00:05:09.650> much<00:05:09.860> more 00:05:10.059 --> 00:05:10.069 align:start position:0% information and it's you know much more 00:05:10.069 --> 00:05:11.890 align:start position:0% information and it's you know much more received<00:05:10.699> machine<00:05:11.000> readable<00:05:11.330> workable 00:05:11.890 --> 00:05:11.900 align:start position:0% received machine readable workable 00:05:11.900 --> 00:05:14.770 align:start position:0% received machine readable workable rather<00:05:12.110> than<00:05:12.259> a<00:05:12.289> giant<00:05:12.560> string<00:05:13.240> and<00:05:14.240> so<00:05:14.389> we<00:05:14.599> use 00:05:14.770 --> 00:05:14.780 align:start position:0% rather than a giant string and so we use 00:05:14.780 --> 00:05:20.499 align:start position:0% rather than a giant string and so we use this<00:05:15.310> for<00:05:16.310> a<00:05:16.639> number<00:05:17.270> of<00:05:17.599> things<00:05:19.360> and<00:05:20.360> in 00:05:20.499 --> 00:05:20.509 align:start position:0% this for a number of things and in 00:05:20.509 --> 00:05:23.080 align:start position:0% this for a number of things and in particularly<00:05:20.840> the<00:05:21.020> music<00:05:21.319> for<00:05:21.590> locating<00:05:22.550> the 00:05:23.080 --> 00:05:23.090 align:start position:0% particularly the music for locating the 00:05:23.090 --> 00:05:25.990 align:start position:0% particularly the music for locating the variables<00:05:23.599> um<00:05:24.080> we<00:05:24.979> use<00:05:25.159> it<00:05:25.340> to<00:05:25.550> determine 00:05:25.990 --> 00:05:26.000 align:start position:0% variables um we use it to determine 00:05:26.000 --> 00:05:27.700 align:start position:0% variables um we use it to determine where<00:05:26.300> the<00:05:26.330> state<00:05:26.659> variables<00:05:27.110> are<00:05:27.169> located 00:05:27.700 --> 00:05:27.710 align:start position:0% where the state variables are located 00:05:27.710 --> 00:05:31.959 align:start position:0% where the state variables are located and<00:05:28.490> we<00:05:29.479> use<00:05:29.719> it<00:05:29.930> and<00:05:30.430> we<00:05:31.430> combined<00:05:31.789> it<00:05:31.940> with 00:05:31.959 --> 00:05:31.969 align:start position:0% and we use it and we combined it with 00:05:31.969 --> 00:05:33.939 align:start position:0% and we use it and we combined it with source<00:05:32.389> map<00:05:32.659> right<00:05:32.840> so<00:05:32.990> the<00:05:33.080> source<00:05:33.289> map<00:05:33.500> tells 00:05:33.939 --> 00:05:33.949 align:start position:0% source map right so the source map tells 00:05:33.949 --> 00:05:36.029 align:start position:0% source map right so the source map tells us<00:05:34.159> where<00:05:34.460> we<00:05:34.639> are<00:05:34.669> in<00:05:35.150> the<00:05:35.330> source<00:05:35.539> code 00:05:36.029 --> 00:05:36.039 align:start position:0% us where we are in the source code 00:05:36.039 --> 00:05:38.409 align:start position:0% us where we are in the source code considering<00:05:37.039> the<00:05:37.159> source<00:05:37.340> code<00:05:37.610> has<00:05:37.969> a<00:05:38.000> string 00:05:38.409 --> 00:05:38.419 align:start position:0% considering the source code has a string 00:05:38.419 --> 00:05:39.610 align:start position:0% considering the source code has a string but<00:05:38.659> then<00:05:38.780> we<00:05:38.900> combine<00:05:39.229> this<00:05:39.409> with<00:05:39.469> our 00:05:39.610 --> 00:05:39.620 align:start position:0% but then we combine this with our 00:05:39.620 --> 00:05:41.860 align:start position:0% but then we combine this with our knowledge<00:05:40.099> the<00:05:40.340> abstract<00:05:40.849> syntax<00:05:40.969> tree<00:05:41.389> that 00:05:41.860 --> 00:05:41.870 align:start position:0% knowledge the abstract syntax tree that 00:05:41.870 --> 00:05:44.649 align:start position:0% knowledge the abstract syntax tree that the<00:05:42.110> debugger<00:05:42.949> sorry<00:05:43.520> that's<00:05:43.789> solidity 00:05:44.649 --> 00:05:44.659 align:start position:0% the debugger sorry that's solidity 00:05:44.659 --> 00:05:47.860 align:start position:0% the debugger sorry that's solidity compiler<00:05:45.229> provides<00:05:46.069> us<00:05:46.250> with<00:05:46.300> which<00:05:47.300> gives 00:05:47.860 --> 00:05:47.870 align:start position:0% compiler provides us with which gives 00:05:47.870 --> 00:05:49.540 align:start position:0% compiler provides us with which gives these<00:05:48.020> source<00:05:48.259> ranges<00:05:48.650> on<00:05:48.770> each<00:05:48.889> no<00:05:49.159> and<00:05:49.430> we 00:05:49.540 --> 00:05:49.550 align:start position:0% these source ranges on each no and we 00:05:49.550 --> 00:05:51.010 align:start position:0% these source ranges on each no and we use<00:05:49.669> this<00:05:49.819> to<00:05:49.969> determine<00:05:50.210> not<00:05:50.449> only<00:05:50.509> where<00:05:50.870> we 00:05:51.010 --> 00:05:51.020 align:start position:0% use this to determine not only where we 00:05:51.020 --> 00:05:53.920 align:start position:0% use this to determine not only where we are<00:05:51.169> in<00:05:51.440> the<00:05:51.889> source<00:05:52.129> in<00:05:52.370> terms<00:05:52.400> of<00:05:52.819> a<00:05:52.930> string 00:05:53.920 --> 00:05:53.930 align:start position:0% are in the source in terms of a string 00:05:53.930 --> 00:05:55.689 align:start position:0% are in the source in terms of a string in<00:05:54.050> disease<00:05:54.349> but<00:05:54.590> also<00:05:54.650> in<00:05:55.009> terms<00:05:55.159> of<00:05:55.370> what<00:05:55.520> no 00:05:55.689 --> 00:05:55.699 align:start position:0% in disease but also in terms of what no 00:05:55.699 --> 00:05:59.080 align:start position:0% in disease but also in terms of what no rod<00:05:56.060> and<00:05:56.870> so<00:05:57.080> using<00:05:57.740> this<00:05:57.830> we<00:05:57.979> can<00:05:58.009> do<00:05:58.250> a<00:05:58.879> bunch 00:05:59.080 --> 00:05:59.090 align:start position:0% rod and so using this we can do a bunch 00:05:59.090 --> 00:06:01.360 align:start position:0% rod and so using this we can do a bunch of<00:05:59.210> processing<00:05:59.810> to<00:06:00.080> determine<00:06:00.800> where<00:06:01.340> the 00:06:01.360 --> 00:06:01.370 align:start position:0% of processing to determine where the 00:06:01.370 --> 00:06:03.430 align:start position:0% of processing to determine where the local<00:06:01.729> variables<00:06:02.090> on<00:06:02.210> the<00:06:02.300> stack<00:06:02.539> are<00:06:02.840> and 00:06:03.430 --> 00:06:03.440 align:start position:0% local variables on the stack are and 00:06:03.440 --> 00:06:05.290 align:start position:0% local variables on the stack are and also<00:06:04.279> other<00:06:04.490> things<00:06:04.580> but<00:06:04.909> note<00:06:05.120> there 00:06:05.290 --> 00:06:05.300 align:start position:0% also other things but note there 00:06:05.300 --> 00:06:07.119 align:start position:0% also other things but note there portrait<00:06:05.659> was<00:06:06.110> relying<00:06:06.500> on<00:06:06.620> the<00:06:06.770> abstract 00:06:07.119 --> 00:06:07.129 align:start position:0% portrait was relying on the abstract 00:06:07.129 --> 00:06:08.830 align:start position:0% portrait was relying on the abstract syntax<00:06:07.219> tree<00:06:07.580> we're<00:06:07.729> also<00:06:07.909> lying<00:06:08.270> on<00:06:08.479> our 00:06:08.830 --> 00:06:08.840 align:start position:0% syntax tree we're also lying on our 00:06:08.840 --> 00:06:11.860 align:start position:0% syntax tree we're also lying on our particular<00:06:09.500> knowledge<00:06:10.009> of<00:06:10.430> how<00:06:11.300> solidity 00:06:11.860 --> 00:06:11.870 align:start position:0% particular knowledge of how solidity 00:06:11.870 --> 00:06:15.490 align:start position:0% particular knowledge of how solidity stores<00:06:12.259> data<00:06:12.819> which<00:06:13.819> is<00:06:14.180> not<00:06:14.750> supplied<00:06:15.229> to<00:06:15.469> us 00:06:15.490 --> 00:06:15.500 align:start position:0% stores data which is not supplied to us 00:06:15.500 --> 00:06:18.010 align:start position:0% stores data which is not supplied to us in<00:06:15.860> any<00:06:16.129> format<00:06:16.550> that's<00:06:16.849> just<00:06:17.120> stuff<00:06:17.960> we 00:06:18.010 --> 00:06:18.020 align:start position:0% in any format that's just stuff we 00:06:18.020 --> 00:06:21.149 align:start position:0% in any format that's just stuff we programmed<00:06:18.620> into<00:06:18.830> the<00:06:18.949> debugger<00:06:19.129> yeah<00:06:20.080> yeah 00:06:21.149 --> 00:06:21.159 align:start position:0% programmed into the debugger yeah yeah 00:06:21.159 --> 00:06:25.659 align:start position:0% programmed into the debugger yeah yeah figuring<00:06:22.159> that<00:06:22.250> out<00:06:22.310> slowly<00:06:23.319> yeah<00:06:24.520> how's<00:06:25.520> that 00:06:25.659 --> 00:06:25.669 align:start position:0% figuring that out slowly yeah how's that 00:06:25.669 --> 00:06:29.230 align:start position:0% figuring that out slowly yeah how's that sound<00:06:25.849> good<00:06:26.389> build<00:06:26.960> a<00:06:27.050> bugger 00:06:29.230 --> 00:06:29.240 align:start position:0% sound good build a bugger 00:06:29.240 --> 00:06:32.900 align:start position:0% sound good build a bugger it<00:06:30.240> doesn't<00:06:30.539> work<00:06:30.660> on<00:06:30.870> other<00:06:31.110> platforms<00:06:31.910> the 00:06:32.900 --> 00:06:32.910 align:start position:0% it doesn't work on other platforms the 00:06:32.910 --> 00:06:35.170 align:start position:0% it doesn't work on other platforms the pile<00:06:33.240> C<00:06:33.539> program<00:06:33.960> how<00:06:34.169> can<00:06:34.320> you<00:06:34.380> do<00:06:34.500> bug<00:06:34.650> that 00:06:35.170 --> 00:06:35.180 align:start position:0% pile C program how can you do bug that 00:06:35.180 --> 00:06:38.540 align:start position:0% pile C program how can you do bug that well<00:06:36.180> there's<00:06:37.110> this<00:06:37.830> concept<00:06:38.250> called<00:06:38.430> a 00:06:38.540 --> 00:06:38.550 align:start position:0% well there's this concept called a 00:06:38.550 --> 00:06:43.219 align:start position:0% well there's this concept called a debugging<00:06:38.880> data<00:06:39.210> format<00:06:39.690> which<00:06:42.020> comes<00:06:43.020> from 00:06:43.219 --> 00:06:43.229 align:start position:0% debugging data format which comes from 00:06:43.229 --> 00:06:45.290 align:start position:0% debugging data format which comes from the<00:06:43.380> compiler<00:06:43.830> the<00:06:44.009> compiler<00:06:44.520> provides<00:06:45.060> the 00:06:45.290 --> 00:06:45.300 align:start position:0% the compiler the compiler provides the 00:06:45.300 --> 00:06:47.900 align:start position:0% the compiler the compiler provides the information<00:06:45.810> about<00:06:46.680> a<00:06:46.710> particular<00:06:47.460> program 00:06:47.900 --> 00:06:47.910 align:start position:0% information about a particular program 00:06:47.910 --> 00:06:51.140 align:start position:0% information about a particular program and<00:06:48.720> says<00:06:49.580> well<00:06:50.580> it<00:06:50.820> gives<00:06:50.940> you<00:06:51.030> that 00:06:51.140 --> 00:06:51.150 align:start position:0% and says well it gives you that 00:06:51.150 --> 00:06:52.909 align:start position:0% and says well it gives you that translation<00:06:51.720> right<00:06:51.840> you<00:06:51.960> can<00:06:52.110> given<00:06:52.680> any 00:06:52.909 --> 00:06:52.919 align:start position:0% translation right you can given any 00:06:52.919 --> 00:06:55.550 align:start position:0% translation right you can given any machine<00:06:53.370> State<00:06:53.669> here's<00:06:54.570> how<00:06:54.750> you<00:06:54.810> can<00:06:55.110> get<00:06:55.289> the 00:06:55.550 --> 00:06:55.560 align:start position:0% machine State here's how you can get the 00:06:55.560 --> 00:06:57.560 align:start position:0% machine State here's how you can get the high-level<00:06:55.949> source<00:06:56.400> code<00:06:56.759> state<00:06:57.120> so<00:06:57.449> it's 00:06:57.560 --> 00:06:57.570 align:start position:0% high-level source code state so it's 00:06:57.570 --> 00:07:00.050 align:start position:0% high-level source code state so it's like<00:06:57.690> give<00:06:58.080> wonder<00:06:58.350> bites<00:06:58.610> you<00:06:59.610> stack<00:07:00.030> your 00:07:00.050 --> 00:07:00.060 align:start position:0% like give wonder bites you stack your 00:07:00.060 --> 00:07:03.379 align:start position:0% like give wonder bites you stack your memory<00:07:00.660> of<00:07:00.870> storage<00:07:01.759> here's<00:07:02.759> how<00:07:03.030> you<00:07:03.090> can<00:07:03.270> get 00:07:03.379 --> 00:07:03.389 align:start position:0% memory of storage here's how you can get 00:07:03.389 --> 00:07:08.960 align:start position:0% memory of storage here's how you can get variables<00:07:03.930> out<00:07:04.080> of<00:07:04.169> that<00:07:04.610> and<00:07:07.820> this<00:07:08.820> is 00:07:08.960 --> 00:07:08.970 align:start position:0% variables out of that and this is 00:07:08.970 --> 00:07:10.400 align:start position:0% variables out of that and this is extremely<00:07:09.270> useful<00:07:09.389> there's<00:07:09.900> a<00:07:09.960> number<00:07:10.320> of 00:07:10.400 --> 00:07:10.410 align:start position:0% extremely useful there's a number of 00:07:10.410 --> 00:07:12.140 align:start position:0% extremely useful there's a number of these<00:07:10.500> there's<00:07:10.919> dwarf<00:07:11.280> is<00:07:11.460> probably<00:07:11.940> the<00:07:12.060> most 00:07:12.140 --> 00:07:12.150 align:start position:0% these there's dwarf is probably the most 00:07:12.150 --> 00:07:16.180 align:start position:0% these there's dwarf is probably the most popular<00:07:13.370> you<00:07:14.370> can<00:07:14.520> read<00:07:14.729> about<00:07:14.970> it<00:07:15.180> it<00:07:15.270> has<00:07:15.389> a<00:07:15.509> 5 00:07:16.180 --> 00:07:16.190 align:start position:0% popular you can read about it it has a 5 00:07:16.190 --> 00:07:20.060 align:start position:0% popular you can read about it it has a 5 477<00:07:17.190> page<00:07:17.419> specification<00:07:18.560> it's<00:07:19.560> a<00:07:19.800> binary 00:07:20.060 --> 00:07:20.070 align:start position:0% 477 page specification it's a binary 00:07:20.070 --> 00:07:27.170 align:start position:0% 477 page specification it's a binary format 00:07:27.170 --> 00:07:27.180 align:start position:0% 00:07:27.180 --> 00:07:29.730 align:start position:0% yes<00:07:28.180> so<00:07:28.330> you<00:07:28.420> have<00:07:28.540> these<00:07:28.660> concentrate<00:07:29.590> so 00:07:29.730 --> 00:07:29.740 align:start position:0% yes so you have these concentrate so 00:07:29.740 --> 00:07:31.500 align:start position:0% yes so you have these concentrate so here's<00:07:29.920> a<00:07:29.980> simple<00:07:30.280> program<00:07:30.700> that<00:07:31.210> these<00:07:31.390> are 00:07:31.500 --> 00:07:31.510 align:start position:0% here's a simple program that these are 00:07:31.510 --> 00:07:32.970 align:start position:0% here's a simple program that these are related<00:07:31.780> examples<00:07:32.380> that<00:07:32.470> defenders<00:07:32.830> took 00:07:32.970 --> 00:07:32.980 align:start position:0% related examples that defenders took 00:07:32.980 --> 00:07:35.160 align:start position:0% related examples that defenders took them<00:07:33.130> from<00:07:33.250> that<00:07:33.400> paper<00:07:33.640> but<00:07:34.330> you<00:07:34.390> have<00:07:34.600> these 00:07:35.160 --> 00:07:35.170 align:start position:0% them from that paper but you have these 00:07:35.170 --> 00:07:37.560 align:start position:0% them from that paper but you have these tags<00:07:35.440> in<00:07:35.830> those<00:07:36.040> sodas<00:07:36.370> subprogram<00:07:37.120> tag<00:07:37.330> which 00:07:37.560 --> 00:07:37.570 align:start position:0% tags in those sodas subprogram tag which 00:07:37.570 --> 00:07:40.380 align:start position:0% tags in those sodas subprogram tag which says<00:07:37.780> oh<00:07:37.990> this<00:07:38.170> is<00:07:38.320> this<00:07:38.590> is<00:07:38.740> food<00:07:39.010> and<00:07:39.390> there's 00:07:40.380 --> 00:07:40.390 align:start position:0% says oh this is this is food and there's 00:07:40.390 --> 00:07:43.290 align:start position:0% says oh this is this is food and there's a<00:07:40.450> variable<00:07:40.900> there<00:07:41.110> and<00:07:41.820> the<00:07:42.820> very<00:07:42.970> long<00:07:43.120> is<00:07:43.270> a 00:07:43.290 --> 00:07:43.300 align:start position:0% a variable there and the very long is a 00:07:43.300 --> 00:07:47.160 align:start position:0% a variable there and the very long is a type<00:07:43.600> and<00:07:43.840> it<00:07:43.960> has<00:07:44.050> a<00:07:44.080> location<00:07:44.470> and<00:07:46.170> health 00:07:47.160 --> 00:07:47.170 align:start position:0% type and it has a location and health 00:07:47.170 --> 00:07:49.010 align:start position:0% type and it has a location and health and<00:07:47.410> even<00:07:47.620> your<00:07:47.740> clear<00:07:47.950> stuff<00:07:48.220> so<00:07:48.310> you<00:07:48.400> can<00:07:48.520> say 00:07:49.010 --> 00:07:49.020 align:start position:0% and even your clear stuff so you can say 00:07:49.020 --> 00:07:51.540 align:start position:0% and even your clear stuff so you can say we're<00:07:50.020> going<00:07:50.140> to<00:07:50.200> be<00:07:50.290> dealing<00:07:50.560> with<00:07:50.590> this<00:07:50.770> so 00:07:51.540 --> 00:07:51.550 align:start position:0% we're going to be dealing with this so 00:07:51.550 --> 00:07:52.950 align:start position:0% we're going to be dealing with this so the<00:07:51.670> compiler<00:07:51.850> will<00:07:52.060> say<00:07:52.180> this<00:07:52.360> is<00:07:52.510> an<00:07:52.600> INT<00:07:52.750> in 00:07:52.950 --> 00:07:52.960 align:start position:0% the compiler will say this is an INT in 00:07:52.960 --> 00:07:57.540 align:start position:0% the compiler will say this is an INT in size<00:07:53.620> four<00:07:53.920> I<00:07:54.660> guess<00:07:55.660> it's<00:07:55.810> all<00:07:56.190> inside<00:07:57.190> right 00:07:57.540 --> 00:07:57.550 align:start position:0% size four I guess it's all inside right 00:07:57.550 --> 00:08:00.810 align:start position:0% size four I guess it's all inside right so<00:07:57.850> you<00:07:58.540> do<00:07:58.810> that<00:07:58.990> you<00:07:59.170> say<00:07:59.350> oh<00:07:59.380> what's<00:07:59.770> CC<00:08:00.520> has 00:08:00.810 --> 00:08:00.820 align:start position:0% so you do that you say oh what's CC has 00:08:00.820 --> 00:08:04.110 align:start position:0% so you do that you say oh what's CC has is<00:08:01.540> a<00:08:01.600> base<00:08:01.990> type<00:08:02.200> of<00:08:02.650> an<00:08:02.770> int<00:08:02.920> as<00:08:03.550> a<00:08:03.700> particular 00:08:04.110 --> 00:08:04.120 align:start position:0% is a base type of an int as a particular 00:08:04.120 --> 00:08:06.330 align:start position:0% is a base type of an int as a particular location<00:08:04.420> this<00:08:05.230> is<00:08:05.440> the<00:08:05.590> frame<00:08:05.920> pointer 00:08:06.330 --> 00:08:06.340 align:start position:0% location this is the frame pointer 00:08:06.340 --> 00:08:09.870 align:start position:0% location this is the frame pointer offset<00:08:07.000> so<00:08:07.270> it's<00:08:07.440> when<00:08:08.440> you<00:08:08.530> find<00:08:08.800> it<00:08:08.950> it's<00:08:09.160> 12 00:08:09.870 --> 00:08:09.880 align:start position:0% offset so it's when you find it it's 12 00:08:09.880 --> 00:08:12.450 align:start position:0% offset so it's when you find it it's 12 items<00:08:10.480> from<00:08:10.630> the<00:08:10.780> top<00:08:10.930> of<00:08:11.050> the<00:08:11.110> stack<00:08:11.400> this<00:08:12.400> is 00:08:12.450 --> 00:08:12.460 align:start position:0% items from the top of the stack this is 00:08:12.460 --> 00:08:14.940 align:start position:0% items from the top of the stack this is pretty<00:08:12.670> useful<00:08:12.850> right<00:08:13.240> but<00:08:13.660> you<00:08:14.620> know<00:08:14.710> this 00:08:14.940 --> 00:08:14.950 align:start position:0% pretty useful right but you know this 00:08:14.950 --> 00:08:18.510 align:start position:0% pretty useful right but you know this gets<00:08:15.220> encoded<00:08:15.640> as<00:08:16.030> binary<00:08:16.860> and<00:08:17.860> gets<00:08:18.070> embedded 00:08:18.510 --> 00:08:18.520 align:start position:0% gets encoded as binary and gets embedded 00:08:18.520 --> 00:08:21.540 align:start position:0% gets encoded as binary and gets embedded into<00:08:19.090> the<00:08:19.210> output<00:08:19.660> right<00:08:20.140> if<00:08:20.350> you've<00:08:20.530> used<00:08:21.130> a 00:08:21.540 --> 00:08:21.550 align:start position:0% into the output right if you've used a 00:08:21.550 --> 00:08:23.400 align:start position:0% into the output right if you've used a traditional<00:08:21.850> computing<00:08:22.480> language<00:08:22.900> and<00:08:23.200> you 00:08:23.400 --> 00:08:23.410 align:start position:0% traditional computing language and you 00:08:23.410 --> 00:08:26.520 align:start position:0% traditional computing language and you output<00:08:24.250> it<00:08:24.400> the<00:08:24.850> debug<00:08:25.120> information<00:08:25.530> and 00:08:26.520 --> 00:08:26.530 align:start position:0% output it the debug information and 00:08:26.530 --> 00:08:32.730 align:start position:0% output it the debug information and using<00:08:27.040> GCC<00:08:27.370> for<00:08:27.670> instances<00:08:28.120> like<00:08:28.330> -<00:08:31.320> but<00:08:32.320> you 00:08:32.730 --> 00:08:32.740 align:start position:0% using GCC for instances like - but you 00:08:32.740 --> 00:08:34.770 align:start position:0% using GCC for instances like - but you you<00:08:33.130> specify<00:08:33.520> a<00:08:33.550> flag<00:08:33.849> that<00:08:34.180> says<00:08:34.419> I<00:08:34.539> want<00:08:34.719> to 00:08:34.770 --> 00:08:34.780 align:start position:0% you specify a flag that says I want to 00:08:34.780 --> 00:08:35.969 align:start position:0% you specify a flag that says I want to divide<00:08:34.960> the<00:08:35.110> ampulla<00:08:35.410> and<00:08:35.530> you<00:08:35.590> get<00:08:35.710> a<00:08:35.740> binary 00:08:35.969 --> 00:08:35.979 align:start position:0% divide the ampulla and you get a binary 00:08:35.979 --> 00:08:37.980 align:start position:0% divide the ampulla and you get a binary that's<00:08:36.370> twice<00:08:36.820> the<00:08:37.060> size<00:08:37.090> or<00:08:37.539> three<00:08:37.690> times<00:08:37.900> the 00:08:37.980 --> 00:08:37.990 align:start position:0% that's twice the size or three times the 00:08:37.990 --> 00:08:40.820 align:start position:0% that's twice the size or three times the size<00:08:38.080> and<00:08:38.530> has<00:08:38.650> all<00:08:38.770> this<00:08:38.860> extra<00:08:39.099> information 00:08:40.820 --> 00:08:40.830 align:start position:0% size and has all this extra information 00:08:40.830 --> 00:08:44.490 align:start position:0% size and has all this extra information which<00:08:41.830> you<00:08:42.190> know<00:08:42.310> you<00:08:42.370> would<00:08:42.580> then<00:08:43.290> if<00:08:44.290> you're 00:08:44.490 --> 00:08:44.500 align:start position:0% which you know you would then if you're 00:08:44.500 --> 00:08:46.050 align:start position:0% which you know you would then if you're in<00:08:44.650> you<00:08:44.770> deploy<00:08:45.100> that<00:08:45.370> and<00:08:45.610> you<00:08:45.670> paid<00:08:45.880> three 00:08:46.050 --> 00:08:46.060 align:start position:0% in you deploy that and you paid three 00:08:46.060 --> 00:08:47.400 align:start position:0% in you deploy that and you paid three times<00:08:46.150> too<00:08:46.450> much<00:08:46.600> and<00:08:46.840> you've<00:08:46.930> seen<00:08:47.110> the<00:08:47.230> block 00:08:47.400 --> 00:08:47.410 align:start position:0% times too much and you've seen the block 00:08:47.410 --> 00:08:51.900 align:start position:0% times too much and you've seen the block gas<00:08:47.620> limit<00:08:49.920> you<00:08:50.920> know<00:08:51.040> it's<00:08:51.280> all<00:08:51.370> set<00:08:51.550> to<00:08:51.640> parse 00:08:51.900 --> 00:08:51.910 align:start position:0% gas limit you know it's all set to parse 00:08:51.910 --> 00:08:53.550 align:start position:0% gas limit you know it's all set to parse this 00:08:53.550 --> 00:08:53.560 align:start position:0% this 00:08:53.560 --> 00:08:56.400 align:start position:0% this but<00:08:54.560> I<00:08:54.800> mean<00:08:54.920> work<00:08:55.730> works<00:08:55.970> pretty<00:08:56.149> well 00:08:56.400 --> 00:08:56.410 align:start position:0% but I mean work works pretty well 00:08:56.410 --> 00:08:58.840 align:start position:0% but I mean work works pretty well there's<00:08:57.410> there's<00:08:57.680> others<00:08:57.949> too<00:08:58.130> I<00:08:58.160> mentioned 00:08:58.840 --> 00:08:58.850 align:start position:0% there's there's others too I mentioned 00:08:58.850 --> 00:09:01.810 align:start position:0% there's there's others too I mentioned them<00:08:58.940> here<00:08:59.420> there's<00:08:59.720> PDV<00:09:00.470> as<00:09:00.560> Microsoft's<00:09:01.250> to 00:09:01.810 --> 00:09:01.820 align:start position:0% them here there's PDV as Microsoft's to 00:09:01.820 --> 00:09:04.569 align:start position:0% them here there's PDV as Microsoft's to use<00:09:02.000> it<00:09:02.209> as<00:09:02.660> a<00:09:02.779> proprietary<00:09:03.290> format<00:09:03.769> it<00:09:04.339> seems 00:09:04.569 --> 00:09:04.579 align:start position:0% use it as a proprietary format it seems 00:09:04.579 --> 00:09:06.699 align:start position:0% use it as a proprietary format it seems to<00:09:04.699> be<00:09:04.760> better<00:09:04.940> it<00:09:05.329> lives<00:09:05.690> externally<00:09:06.380> so<00:09:06.620> you 00:09:06.699 --> 00:09:06.709 align:start position:0% to be better it lives externally so you 00:09:06.709 --> 00:09:10.210 align:start position:0% to be better it lives externally so you get<00:09:06.949> a<00:09:06.980> dot<00:09:07.250> peb<00:09:07.699> file<00:09:08.230> rather<00:09:09.230> than<00:09:09.380> loading 00:09:10.210 --> 00:09:10.220 align:start position:0% get a dot peb file rather than loading 00:09:10.220 --> 00:09:15.610 align:start position:0% get a dot peb file rather than loading your<00:09:10.399> actual<00:09:11.029> binary<00:09:11.209> output<00:09:14.320> coffee<00:09:15.320> is 00:09:15.610 --> 00:09:15.620 align:start position:0% your actual binary output coffee is 00:09:15.620 --> 00:09:17.379 align:start position:0% your actual binary output coffee is interesting<00:09:16.040> because<00:09:16.190> coffee<00:09:16.519> is<00:09:16.730> of<00:09:16.910> an 00:09:17.379 --> 00:09:17.389 align:start position:0% interesting because coffee is of an 00:09:17.389 --> 00:09:19.000 align:start position:0% interesting because coffee is of an actual<00:09:17.570> binary<00:09:18.019> a<00:09:18.260> performant<00:09:18.769> that's<00:09:18.889> what 00:09:19.000 --> 00:09:19.010 align:start position:0% actual binary a performant that's what 00:09:19.010 --> 00:09:21.400 align:start position:0% actual binary a performant that's what the<00:09:19.070> compiler<00:09:19.310> gives<00:09:19.610> you<00:09:19.730> regardless<00:09:20.329> but<00:09:21.139> it 00:09:21.400 --> 00:09:21.410 align:start position:0% the compiler gives you regardless but it 00:09:21.410 --> 00:09:24.730 align:start position:0% the compiler gives you regardless but it includes<00:09:22.100> the<00:09:22.220> specification<00:09:22.910> that<00:09:23.529> like<00:09:24.529> has 00:09:24.730 --> 00:09:24.740 align:start position:0% includes the specification that like has 00:09:24.740 --> 00:09:26.379 align:start position:0% includes the specification that like has de<00:09:24.949> buggy<00:09:25.100> information<00:09:25.699> so<00:09:25.850> you've<00:09:26.149> got<00:09:26.269> this 00:09:26.379 --> 00:09:26.389 align:start position:0% de buggy information so you've got this 00:09:26.389 --> 00:09:28.210 align:start position:0% de buggy information so you've got this binary<00:09:26.600> in<00:09:26.930> the<00:09:27.050> binary<00:09:27.199> may<00:09:27.800> or<00:09:27.860> may<00:09:27.949> not<00:09:28.040> have 00:09:28.210 --> 00:09:28.220 align:start position:0% binary in the binary may or may not have 00:09:28.220 --> 00:09:30.490 align:start position:0% binary in the binary may or may not have the<00:09:28.339> debug<00:09:28.519> information<00:09:29.230> whereas<00:09:30.230> the<00:09:30.350> work 00:09:30.490 --> 00:09:30.500 align:start position:0% the debug information whereas the work 00:09:30.500 --> 00:09:31.900 align:start position:0% the debug information whereas the work is<00:09:30.620> like<00:09:30.769> Bolton<00:09:31.100> on<00:09:31.190> that<00:09:31.339> was<00:09:31.459> the<00:09:31.579> separate 00:09:31.900 --> 00:09:31.910 align:start position:0% is like Bolton on that was the separate 00:09:31.910 --> 00:09:35.439 align:start position:0% is like Bolton on that was the separate standard<00:09:32.949> if<00:09:33.949> anyone's<00:09:34.310> familiar<00:09:34.370> with<00:09:34.790> e.l.f 00:09:35.439 --> 00:09:35.449 align:start position:0% standard if anyone's familiar with e.l.f 00:09:35.449 --> 00:09:37.600 align:start position:0% standard if anyone's familiar with e.l.f binaries<00:09:36.019> that's<00:09:36.230> the<00:09:36.320> linux<00:09:36.649> native<00:09:37.130> binary 00:09:37.600 --> 00:09:37.610 align:start position:0% binaries that's the linux native binary 00:09:37.610 --> 00:09:44.340 align:start position:0% binaries that's the linux native binary format<00:09:37.940> that's<00:09:38.120> why<00:09:38.240> they<00:09:38.360> got<00:09:38.510> the<00:09:38.540> name<00:09:38.720> for 00:09:44.340 --> 00:09:44.350 align:start position:0% 00:09:44.350 --> 00:09:46.439 align:start position:0% alright<00:09:45.350> so<00:09:45.470> here<00:09:45.620> are<00:09:45.709> some<00:09:45.800> requirements 00:09:46.439 --> 00:09:46.449 align:start position:0% alright so here are some requirements 00:09:46.449 --> 00:09:49.900 align:start position:0% alright so here are some requirements that<00:09:47.449> you<00:09:47.690> come<00:09:47.870> up<00:09:47.990> with<00:09:48.820> naturally<00:09:49.820> it<00:09:49.880> has 00:09:49.900 --> 00:09:49.910 align:start position:0% that you come up with naturally it has 00:09:49.910 --> 00:09:53.050 align:start position:0% that you come up with naturally it has to<00:09:50.060> live<00:09:50.209> outside<00:09:50.329> the<00:09:50.570> bytecode<00:09:50.750> give<00:09:51.440> gas<00:09:52.060> it 00:09:53.050 --> 00:09:53.060 align:start position:0% to live outside the bytecode give gas it 00:09:53.060 --> 00:09:54.490 align:start position:0% to live outside the bytecode give gas it should<00:09:53.180> be<00:09:53.240> easy<00:09:53.449> to<00:09:53.570> generate<00:09:54.050> because<00:09:54.350> I 00:09:54.490 --> 00:09:54.500 align:start position:0% should be easy to generate because I 00:09:54.500 --> 00:09:56.199 align:start position:0% should be easy to generate because I want<00:09:54.829> to<00:09:54.860> make<00:09:55.010> this<00:09:55.130> litany<00:09:55.459> of<00:09:55.579> developers 00:09:56.199 --> 00:09:56.209 align:start position:0% want to make this litany of developers 00:09:56.209 --> 00:09:59.110 align:start position:0% want to make this litany of developers lives<00:09:56.420> terrible<00:09:57.079> and<00:09:57.670> it<00:09:58.670> must<00:09:58.790> be<00:09:58.850> easy<00:09:59.029> to 00:09:59.110 --> 00:09:59.120 align:start position:0% lives terrible and it must be easy to 00:09:59.120 --> 00:10:00.490 align:start position:0% lives terrible and it must be easy to read<00:09:59.300> because<00:09:59.449> I<00:09:59.600> don't<00:09:59.750> want<00:09:59.870> Aries<00:10:00.170> life<00:10:00.350> to 00:10:00.490 --> 00:10:00.500 align:start position:0% read because I don't want Aries life to 00:10:00.500 --> 00:10:03.430 align:start position:0% read because I don't want Aries life to be<00:10:00.560> terrible<00:10:00.980> and<00:10:01.690> it<00:10:02.690> should<00:10:02.810> be<00:10:02.899> extensible 00:10:03.430 --> 00:10:03.440 align:start position:0% be terrible and it should be extensible 00:10:03.440 --> 00:10:05.500 align:start position:0% be terrible and it should be extensible because<00:10:03.769> we<00:10:04.100> don't<00:10:04.699> only<00:10:04.910> want<00:10:05.149> to<00:10:05.240> support 00:10:05.500 --> 00:10:05.510 align:start position:0% because we don't only want to support 00:10:05.510 --> 00:10:07.059 align:start position:0% because we don't only want to support solidity<00:10:05.899> we<00:10:06.110> also<00:10:06.260> want<00:10:06.500> to<00:10:06.529> support<00:10:06.680> Viper 00:10:07.059 --> 00:10:07.069 align:start position:0% solidity we also want to support Viper 00:10:07.069 --> 00:10:08.230 align:start position:0% solidity we also want to support Viper and<00:10:07.370> all<00:10:07.430> the<00:10:07.550> other<00:10:07.670> smart<00:10:07.850> contract 00:10:08.230 --> 00:10:08.240 align:start position:0% and all the other smart contract 00:10:08.240 --> 00:10:09.670 align:start position:0% and all the other smart contract languages<00:10:08.600> and<00:10:08.779> also<00:10:09.050> you<00:10:09.260> know<00:10:09.350> he<00:10:09.500> was 00:10:09.670 --> 00:10:09.680 align:start position:0% languages and also you know he was 00:10:09.680 --> 00:10:12.129 align:start position:0% languages and also you know he was coming<00:10:10.069> and<00:10:10.569> that's<00:10:11.569> gonna<00:10:11.779> break<00:10:11.959> our 00:10:12.129 --> 00:10:12.139 align:start position:0% coming and that's gonna break our 00:10:12.139 --> 00:10:14.850 align:start position:0% coming and that's gonna break our debugger 00:10:14.850 --> 00:10:14.860 align:start position:0% 00:10:14.860 --> 00:10:17.980 align:start position:0% so<00:10:15.860> get<00:10:16.459> your<00:10:16.610> super<00:10:16.819> fireman<00:10:17.209> suite<00:10:17.420> there 00:10:17.980 --> 00:10:17.990 align:start position:0% so get your super fireman suite there 00:10:17.990 --> 00:10:20.350 align:start position:0% so get your super fireman suite there probably<00:10:18.319> others<00:10:19.029> anyway 00:10:20.350 --> 00:10:20.360 align:start position:0% probably others anyway 00:10:20.360 --> 00:10:23.699 align:start position:0% probably others anyway Mary<00:10:21.050> tell<00:10:21.470> us<00:10:21.529> why<00:10:21.649> it's<00:10:21.769> difficult<00:10:21.920> okay<00:10:22.730> so 00:10:23.699 --> 00:10:23.709 align:start position:0% Mary tell us why it's difficult okay so 00:10:23.709 --> 00:10:26.460 align:start position:0% Mary tell us why it's difficult okay so there's<00:10:24.709> a<00:10:24.800> lot<00:10:25.009> of<00:10:25.129> guns<00:10:25.279> that<00:10:25.399> going<00:10:25.790> to<00:10:25.939> uh 00:10:26.460 --> 00:10:26.470 align:start position:0% there's a lot of guns that going to uh 00:10:26.470 --> 00:10:29.049 align:start position:0% there's a lot of guns that going to uh designing<00:10:27.470> for<00:10:27.620> these<00:10:27.800> and<00:10:27.980> actually<00:10:28.790> post 00:10:29.049 --> 00:10:29.059 align:start position:0% designing for these and actually post 00:10:29.059 --> 00:10:30.309 align:start position:0% designing for these and actually post these<00:10:29.209> for<00:10:29.420> questions<00:10:29.839> probably<00:10:30.050> the<00:10:30.199> one 00:10:30.309 --> 00:10:30.319 align:start position:0% these for questions probably the one 00:10:30.319 --> 00:10:31.509 align:start position:0% these for questions probably the one that<00:10:30.439> make<00:10:30.589> put<00:10:30.829> last<00:10:31.069> year 00:10:31.509 --> 00:10:31.519 align:start position:0% that make put last year 00:10:31.519 --> 00:10:34.749 align:start position:0% that make put last year what's<00:10:31.730> this<00:10:32.029> format<00:10:32.480> even<00:10:32.720> look<00:10:33.050> like<00:10:33.699> now<00:10:34.699> we 00:10:34.749 --> 00:10:34.759 align:start position:0% what's this format even look like now we 00:10:34.759 --> 00:10:37.840 align:start position:0% what's this format even look like now we take<00:10:35.420> inspiration<00:10:35.749> from<00:10:36.230> dwarf<00:10:36.740> now<00:10:37.610> Nick 00:10:37.840 --> 00:10:37.850 align:start position:0% take inspiration from dwarf now Nick 00:10:37.850 --> 00:10:41.860 align:start position:0% take inspiration from dwarf now Nick guys<00:10:37.999> make<00:10:38.329> sure<00:10:38.360> you<00:10:39.160> dwarf<00:10:40.160> uses<00:10:40.970> this<00:10:41.180> idea 00:10:41.860 --> 00:10:41.870 align:start position:0% guys make sure you dwarf uses this idea 00:10:41.870 --> 00:10:48.220 align:start position:0% guys make sure you dwarf uses this idea of<00:10:42.050> declaring<00:10:42.769> types<00:10:44.350> so<00:10:46.689> yeah<00:10:47.689> so<00:10:47.959> like<00:10:48.110> you 00:10:48.220 --> 00:10:48.230 align:start position:0% of declaring types so yeah so like you 00:10:48.230 --> 00:10:50.110 align:start position:0% of declaring types so yeah so like you can<00:10:48.379> declare<00:10:48.499> types<00:10:49.040> and<00:10:49.339> then<00:10:49.430> add<00:10:49.610> variables 00:10:50.110 --> 00:10:50.120 align:start position:0% can declare types and then add variables 00:10:50.120 --> 00:10:51.879 align:start position:0% can declare types and then add variables we<00:10:50.329> of<00:10:50.600> those<00:10:50.930> types<00:10:51.230> and<00:10:51.379> that's<00:10:51.499> really<00:10:51.680> nice 00:10:51.879 --> 00:10:51.889 align:start position:0% we of those types and that's really nice 00:10:51.889 --> 00:10:53.439 align:start position:0% we of those types and that's really nice because<00:10:52.189> it's<00:10:52.459> like<00:10:52.639> you<00:10:53.059> know<00:10:53.149> you're<00:10:53.360> not 00:10:53.439 --> 00:10:53.449 align:start position:0% because it's like you know you're not 00:10:53.449 --> 00:10:57.670 align:start position:0% because it's like you know you're not limited<00:10:54.230> to<00:10:54.459> this<00:10:55.459> preset<00:10:56.319> you<00:10:57.319> know<00:10:57.410> just 00:10:57.670 --> 00:10:57.680 align:start position:0% limited to this preset you know just 00:10:57.680 --> 00:10:59.410 align:start position:0% limited to this preset you know just like<00:10:57.829> a<00:10:58.009> few<00:10:58.220> preset<00:10:58.639> types<00:10:58.850> that<00:10:59.120> would<00:10:59.269> be 00:10:59.410 --> 00:10:59.420 align:start position:0% like a few preset types that would be 00:10:59.420 --> 00:11:02.280 align:start position:0% like a few preset types that would be not<00:11:00.379> very<00:11:00.680> useful 00:11:02.280 --> 00:11:02.290 align:start position:0% not very useful 00:11:02.290 --> 00:11:04.809 align:start position:0% not very useful maybe<00:11:03.290> there's<00:11:03.470> sort<00:11:04.279> of<00:11:04.339> this<00:11:04.490> the 00:11:04.809 --> 00:11:04.819 align:start position:0% maybe there's sort of this the 00:11:04.819 --> 00:11:06.400 align:start position:0% maybe there's sort of this the alternative<00:11:05.329> approach<00:11:05.509> you<00:11:05.870> know<00:11:05.959> if<00:11:06.110> you<00:11:06.230> can 00:11:06.400 --> 00:11:06.410 align:start position:0% alternative approach you know if you can 00:11:06.410 --> 00:11:07.900 align:start position:0% alternative approach you know if you can here<00:11:06.620> prepare<00:11:06.949> types<00:11:07.189> and<00:11:07.459> you<00:11:07.519> also<00:11:07.699> don't 00:11:07.900 --> 00:11:07.910 align:start position:0% here prepare types and you also don't 00:11:07.910 --> 00:11:10.449 align:start position:0% here prepare types and you also don't want<00:11:08.089> to<00:11:08.180> limit<00:11:08.779> yourself<00:11:08.930> to<00:11:09.199> and<00:11:09.740> depending 00:11:10.449 --> 00:11:10.459 align:start position:0% want to limit yourself to and depending 00:11:10.459 --> 00:11:12.189 align:start position:0% want to limit yourself to and depending if<00:11:10.519> you're<00:11:10.610> kind<00:11:10.759> of<00:11:10.910> stuck<00:11:11.180> when<00:11:11.839> it<00:11:11.930> comes<00:11:12.079> to 00:11:12.189 --> 00:11:12.199 align:start position:0% if you're kind of stuck when it comes to 00:11:12.199 --> 00:11:15.280 align:start position:0% if you're kind of stuck when it comes to like<00:11:12.350> and<00:11:12.589> when<00:11:12.769> arrays<00:11:13.040> or<00:11:13.959> sorry<00:11:14.959> I<00:11:15.050> didn't 00:11:15.280 --> 00:11:15.290 align:start position:0% like and when arrays or sorry I didn't 00:11:15.290 --> 00:11:19.960 align:start position:0% like and when arrays or sorry I didn't explain<00:11:15.499> that<00:11:15.649> well<00:11:17.439> you<00:11:18.439> can<00:11:18.559> start<00:11:18.800> if<00:11:19.790> you 00:11:19.960 --> 00:11:19.970 align:start position:0% explain that well you can start if you 00:11:19.970 --> 00:11:21.519 align:start position:0% explain that well you can start if you can't<00:11:20.209> declare<00:11:20.629> types<00:11:21.019> and<00:11:21.230> you<00:11:21.290> have<00:11:21.410> to 00:11:21.519 --> 00:11:21.529 align:start position:0% can't declare types and you have to 00:11:21.529 --> 00:11:22.929 align:start position:0% can't declare types and you have to associate<00:11:21.920> a<00:11:22.040> separate<00:11:22.399> type<00:11:22.610> with<00:11:22.790> each 00:11:22.929 --> 00:11:22.939 align:start position:0% associate a separate type with each 00:11:22.939 --> 00:11:24.879 align:start position:0% associate a separate type with each variable<00:11:23.809> then<00:11:24.019> you<00:11:24.110> get<00:11:24.230> kind<00:11:24.470> of<00:11:24.499> stuck<00:11:24.709> when 00:11:24.879 --> 00:11:24.889 align:start position:0% variable then you get kind of stuck when 00:11:24.889 --> 00:11:26.350 align:start position:0% variable then you get kind of stuck when you<00:11:24.980> have<00:11:25.129> to<00:11:25.249> handle<00:11:25.490> compound<00:11:25.970> things<00:11:26.209> like 00:11:26.350 --> 00:11:26.360 align:start position:0% you have to handle compound things like 00:11:26.360 --> 00:11:28.119 align:start position:0% you have to handle compound things like a<00:11:26.389> race<00:11:26.629> like<00:11:26.839> are<00:11:26.990> you<00:11:27.079> going<00:11:27.319> to<00:11:27.499> you<00:11:28.040> know 00:11:28.119 --> 00:11:28.129 align:start position:0% a race like are you going to you know 00:11:28.129 --> 00:11:29.860 align:start position:0% a race like are you going to you know associate<00:11:28.550> a<00:11:28.579> thing<00:11:28.759> to<00:11:28.910> every<00:11:29.120> entry<00:11:29.569> of<00:11:29.749> a 00:11:29.860 --> 00:11:29.870 align:start position:0% associate a thing to every entry of a 00:11:29.870 --> 00:11:32.769 align:start position:0% associate a thing to every entry of a dynamically<00:11:30.860> sized<00:11:31.129> or<00:11:31.429> alien<00:11:31.819> no<00:11:32.389> you<00:11:32.449> can't 00:11:32.769 --> 00:11:32.779 align:start position:0% dynamically sized or alien no you can't 00:11:32.779 --> 00:11:34.869 align:start position:0% dynamically sized or alien no you can't do<00:11:32.899> that<00:11:33.050> so<00:11:33.259> this<00:11:33.800> ability<00:11:34.189> to<00:11:34.339> their<00:11:34.550> type<00:11:34.730> is 00:11:34.869 --> 00:11:34.879 align:start position:0% do that so this ability to their type is 00:11:34.879 --> 00:11:36.669 align:start position:0% do that so this ability to their type is quite<00:11:35.089> useful<00:11:35.269> and<00:11:35.629> we<00:11:36.050> will<00:11:36.170> like<00:11:36.319> to<00:11:36.499> want 00:11:36.669 --> 00:11:36.679 align:start position:0% quite useful and we will like to want 00:11:36.679 --> 00:11:38.470 align:start position:0% quite useful and we will like to want that<00:11:36.829> oil<00:11:37.009> I<00:11:37.429> don't<00:11:37.879> know<00:11:37.970> I<00:11:38.149> don't<00:11:38.209> know<00:11:38.360> much 00:11:38.470 --> 00:11:38.480 align:start position:0% that oil I don't know I don't know much 00:11:38.480 --> 00:11:40.329 align:start position:0% that oil I don't know I don't know much about<00:11:38.540> designing<00:11:38.990> data<00:11:39.259> but<00:11:39.709> data<00:11:39.740> format<00:11:40.220> but 00:11:40.329 --> 00:11:40.339 align:start position:0% about designing data but data format but 00:11:40.339 --> 00:11:41.530 align:start position:0% about designing data but data format but there's<00:11:40.490> all<00:11:40.639> sorts<00:11:40.850> of<00:11:40.910> other<00:11:41.029> challenges 00:11:41.530 --> 00:11:41.540 align:start position:0% there's all sorts of other challenges 00:11:41.540 --> 00:11:44.259 align:start position:0% there's all sorts of other challenges and<00:11:42.439> a<00:11:43.009> lot<00:11:43.160> of<00:11:43.189> these<00:11:43.370> by<00:11:43.730> the<00:11:43.790> way<00:11:43.939> a<00:11:43.970> lot<00:11:44.149> of 00:11:44.259 --> 00:11:44.269 align:start position:0% and a lot of these by the way a lot of 00:11:44.269 --> 00:11:47.259 align:start position:0% and a lot of these by the way a lot of these<00:11:44.329> points<00:11:44.569> are<00:11:44.929> fair<00:11:45.920> our<00:11:46.189> are<00:11:46.399> inspired 00:11:47.259 --> 00:11:47.269 align:start position:0% these points are fair our are inspired 00:11:47.269 --> 00:11:49.929 align:start position:0% these points are fair our are inspired by<00:11:47.420> solidity<00:11:48.230> at<00:11:48.499> least<00:11:48.800> you<00:11:49.069> know<00:11:49.189> you<00:11:49.730> want 00:11:49.929 --> 00:11:49.939 align:start position:0% by solidity at least you know you want 00:11:49.939 --> 00:11:51.090 align:start position:0% by solidity at least you know you want to<00:11:50.029> be<00:11:50.149> more<00:11:50.300> general<00:11:50.689> than 00:11:51.090 --> 00:11:51.100 align:start position:0% to be more general than 00:11:51.100 --> 00:11:52.680 align:start position:0% to be more general than these<00:11:51.310> are<00:11:51.460> particular<00:11:52.000> talents<00:11:52.390> that<00:11:52.510> come 00:11:52.680 --> 00:11:52.690 align:start position:0% these are particular talents that come 00:11:52.690 --> 00:11:54.000 align:start position:0% these are particular talents that come up<00:11:52.750> with<00:11:52.900> solidity<00:11:53.260> in<00:11:53.410> particular<00:11:53.890> and 00:11:54.000 --> 00:11:54.010 align:start position:0% up with solidity in particular and 00:11:54.010 --> 00:11:55.710 align:start position:0% up with solidity in particular and therefore<00:11:54.520> and<00:11:54.970> if<00:11:55.060> they<00:11:55.300> come<00:11:55.450> up<00:11:55.540> with<00:11:55.660> a 00:11:55.710 --> 00:11:55.720 align:start position:0% therefore and if they come up with a 00:11:55.720 --> 00:11:57.960 align:start position:0% therefore and if they come up with a person<00:11:56.380> like<00:11:56.650> if<00:11:57.400> we<00:11:57.490> need<00:11:57.610> to<00:11:57.700> solve<00:11:57.850> these 00:11:57.960 --> 00:11:57.970 align:start position:0% person like if we need to solve these 00:11:57.970 --> 00:11:59.190 align:start position:0% person like if we need to solve these just<00:11:58.210> handle<00:11:58.510> solidity<00:11:58.840> then<00:11:59.080> we're 00:11:59.190 --> 00:11:59.200 align:start position:0% just handle solidity then we're 00:11:59.200 --> 00:12:00.800 align:start position:0% just handle solidity then we're certainly<00:11:59.470> gonna<00:11:59.740> need<00:11:59.980> to<00:12:00.040> solve<00:12:00.220> these<00:12:00.400> Tom 00:12:00.800 --> 00:12:00.810 align:start position:0% certainly gonna need to solve these Tom 00:12:00.810 --> 00:12:05.190 align:start position:0% certainly gonna need to solve these Tom so<00:12:03.210> location<00:12:04.210> dependent<00:12:04.540> representation 00:12:05.190 --> 00:12:05.200 align:start position:0% so location dependent representation 00:12:05.200 --> 00:12:06.810 align:start position:0% so location dependent representation salinity<00:12:05.710> represents<00:12:06.220> data<00:12:06.370> differently 00:12:06.810 --> 00:12:06.820 align:start position:0% salinity represents data differently 00:12:06.820 --> 00:12:10.110 align:start position:0% salinity represents data differently depending<00:12:07.060> on<00:12:07.720> whether<00:12:08.260> it's<00:12:08.590> in<00:12:09.250> storage<00:12:09.730> in 00:12:10.110 --> 00:12:10.120 align:start position:0% depending on whether it's in storage in 00:12:10.120 --> 00:12:14.580 align:start position:0% depending on whether it's in storage in memory<00:12:10.630> in<00:12:11.290> call<00:12:11.500> data<00:12:11.680> or<00:12:12.040> on<00:12:12.220> the<00:12:12.340> stack<00:12:13.590> do 00:12:14.580 --> 00:12:14.590 align:start position:0% memory in call data or on the stack do 00:12:14.590 --> 00:12:18.900 align:start position:0% memory in call data or on the stack do we<00:12:14.800> you<00:12:15.790> know<00:12:15.940> to<00:12:16.360> meet<00:12:16.540> in<00:12:16.750> the<00:12:16.840> up<00:12:17.020> just<00:12:17.910> make 00:12:18.900 --> 00:12:18.910 align:start position:0% we you know to meet in the up just make 00:12:18.910 --> 00:12:20.280 align:start position:0% we you know to meet in the up just make it<00:12:19.060> so<00:12:19.180> that<00:12:19.210> to<00:12:19.780> where<00:12:19.930> when<00:12:20.080> you<00:12:20.140> declare 00:12:20.280 --> 00:12:20.290 align:start position:0% it so that to where when you declare 00:12:20.290 --> 00:12:22.310 align:start position:0% it so that to where when you declare tight<00:12:20.770> you<00:12:21.040> have<00:12:21.070> to<00:12:21.700> describe<00:12:22.000> its 00:12:22.310 --> 00:12:22.320 align:start position:0% tight you have to describe its 00:12:22.320 --> 00:12:24.330 align:start position:0% tight you have to describe its representation<00:12:23.320> in<00:12:23.380> all<00:12:23.530> locations<00:12:23.680> or<00:12:24.190> maybe 00:12:24.330 --> 00:12:24.340 align:start position:0% representation in all locations or maybe 00:12:24.340 --> 00:12:25.860 align:start position:0% representation in all locations or maybe between<00:12:24.460> these<00:12:24.760> it's<00:12:24.940> four<00:12:25.090> different<00:12:25.240> you 00:12:25.860 --> 00:12:25.870 align:start position:0% between these it's four different you 00:12:25.870 --> 00:12:27.000 align:start position:0% between these it's four different you know<00:12:25.990> it's<00:12:26.110> three<00:12:26.260> or<00:12:26.290> four<00:12:26.380> different<00:12:26.680> types 00:12:27.000 --> 00:12:27.010 align:start position:0% know it's three or four different types 00:12:27.010 --> 00:12:31.620 align:start position:0% know it's three or four different types you<00:12:27.250> know<00:12:27.430> declare<00:12:28.270> mole<00:12:28.420> separately<00:12:28.930> and<00:12:30.630> how 00:12:31.620 --> 00:12:31.630 align:start position:0% you know declare mole separately and how 00:12:31.630 --> 00:12:34.290 align:start position:0% you know declare mole separately and how do<00:12:31.690> we<00:12:31.900> represent<00:12:32.500> the<00:12:33.340> way<00:12:33.460> that<00:12:33.730> solidity 00:12:34.290 --> 00:12:34.300 align:start position:0% do we represent the way that solidity 00:12:34.300 --> 00:12:36.270 align:start position:0% do we represent the way that solidity does<00:12:34.600> dynamic<00:12:35.350> arrays<00:12:35.590> and<00:12:35.830> mappings<00:12:36.160> and 00:12:36.270 --> 00:12:36.280 align:start position:0% does dynamic arrays and mappings and 00:12:36.280 --> 00:12:39.660 align:start position:0% does dynamic arrays and mappings and storage<00:12:36.640> which<00:12:36.880> has<00:12:37.060> this<00:12:37.240> uh<00:12:37.450> you<00:12:38.200> know<00:12:38.670> catch 00:12:39.660 --> 00:12:39.670 align:start position:0% storage which has this uh you know catch 00:12:39.670 --> 00:12:41.610 align:start position:0% storage which has this uh you know catch act<00:12:39.940> based<00:12:40.210> location<00:12:40.840> scheme<00:12:41.140> that's<00:12:41.410> like 00:12:41.610 --> 00:12:41.620 align:start position:0% act based location scheme that's like 00:12:41.620 --> 00:12:43.050 align:start position:0% act based location scheme that's like it's<00:12:41.980> like<00:12:42.130> you<00:12:42.220> guys<00:12:42.370> wanna<00:12:42.610> be<00:12:42.700> putting<00:12:42.970> that 00:12:43.050 --> 00:12:43.060 align:start position:0% it's like you guys wanna be putting that 00:12:43.060 --> 00:12:45.960 align:start position:0% it's like you guys wanna be putting that in<00:12:43.360> your<00:12:43.420> debug<00:12:43.780> data<00:12:43.990> format<00:12:44.440> like<00:12:45.220> like<00:12:45.730> I 00:12:45.960 --> 00:12:45.970 align:start position:0% in your debug data format like like I 00:12:45.970 --> 00:12:47.670 align:start position:0% in your debug data format like like I mean<00:12:46.300> yeah<00:12:46.420> we<00:12:46.570> can<00:12:46.690> put<00:12:46.840> a<00:12:46.900> flag<00:12:47.140> for<00:12:47.440> it<00:12:47.590> or 00:12:47.670 --> 00:12:47.680 align:start position:0% mean yeah we can put a flag for it or 00:12:47.680 --> 00:12:49.490 align:start position:0% mean yeah we can put a flag for it or something<00:12:48.100> but<00:12:48.280> it's<00:12:48.400> like<00:12:48.580> it's<00:12:49.120> a<00:12:49.180> little 00:12:49.490 --> 00:12:49.500 align:start position:0% something but it's like it's a little 00:12:49.500 --> 00:12:52.950 align:start position:0% something but it's like it's a little it's<00:12:50.500> a<00:12:50.590> little<00:12:50.800> bunch<00:12:50.980> maybe<00:12:51.310> um<00:12:51.610> Nick<00:12:52.150> here 00:12:52.950 --> 00:12:52.960 align:start position:0% it's a little bunch maybe um Nick here 00:12:52.960 --> 00:12:55.640 align:start position:0% it's a little bunch maybe um Nick here has<00:12:53.590> this<00:12:53.710> whole<00:12:53.890> idea<00:12:54.040> that<00:12:54.400> we<00:12:55.270> should<00:12:55.450> make 00:12:55.640 --> 00:12:55.650 align:start position:0% has this whole idea that we should make 00:12:55.650 --> 00:12:59.490 align:start position:0% has this whole idea that we should make button<00:12:56.650> data<00:12:57.100> format<00:12:57.490> maybe<00:12:58.020> maybe<00:12:59.020> less<00:12:59.230> data 00:12:59.490 --> 00:12:59.500 align:start position:0% button data format maybe maybe less data 00:12:59.500 --> 00:13:02.700 align:start position:0% button data format maybe maybe less data based<00:12:59.800> and<00:13:00.070> more<00:13:00.310> code<00:13:01.000> based<00:13:01.390> and<00:13:02.350> you'd<00:13:02.500> have 00:13:02.700 --> 00:13:02.710 align:start position:0% based and more code based and you'd have 00:13:02.710 --> 00:13:04.710 align:start position:0% based and more code based and you'd have these<00:13:03.130> common<00:13:03.640> extension<00:13:03.940> this<00:13:04.270> baby<00:13:04.510> would 00:13:04.710 --> 00:13:04.720 align:start position:0% these common extension this baby would 00:13:04.720 --> 00:13:06.270 align:start position:0% these common extension this baby would be<00:13:04.750> a<00:13:04.870> good<00:13:05.050> candidate<00:13:05.500> for<00:13:05.560> that<00:13:05.710> like<00:13:06.190> a 00:13:06.270 --> 00:13:06.280 align:start position:0% be a good candidate for that like a 00:13:06.280 --> 00:13:08.430 align:start position:0% be a good candidate for that like a mapping<00:13:06.640> accessibility<00:13:07.480> mapping<00:13:07.840> extension 00:13:08.430 --> 00:13:08.440 align:start position:0% mapping accessibility mapping extension 00:13:08.440 --> 00:13:09.900 align:start position:0% mapping accessibility mapping extension where<00:13:08.590> the<00:13:08.710> solidity<00:13:09.100> compiler<00:13:09.610> would<00:13:09.730> say 00:13:09.900 --> 00:13:09.910 align:start position:0% where the solidity compiler would say 00:13:09.910 --> 00:13:13.230 align:start position:0% where the solidity compiler would say this<00:13:10.060> is<00:13:10.210> a<00:13:10.270> mapping<00:13:11.310> into<00:13:12.310> int<00:13:12.490> or<00:13:12.880> into 00:13:13.230 --> 00:13:13.240 align:start position:0% this is a mapping into int or into 00:13:13.240 --> 00:13:15.630 align:start position:0% this is a mapping into int or into address<00:13:13.600> or<00:13:13.750> whatever<00:13:13.870> and<00:13:14.640> whatever 00:13:15.630 --> 00:13:15.640 align:start position:0% address or whatever and whatever 00:13:15.640 --> 00:13:18.240 align:start position:0% address or whatever and whatever debugger<00:13:16.090> builds<00:13:16.900> its<00:13:17.020> own<00:13:17.250> implementation 00:13:18.240 --> 00:13:18.250 align:start position:0% debugger builds its own implementation 00:13:18.250 --> 00:13:20.850 align:start position:0% debugger builds its own implementation of<00:13:18.340> what<00:13:18.550> that<00:13:18.820> mapping<00:13:19.090> means<00:13:19.480> and<00:13:19.900> you<00:13:20.740> know 00:13:20.850 --> 00:13:20.860 align:start position:0% of what that mapping means and you know 00:13:20.860 --> 00:13:23.370 align:start position:0% of what that mapping means and you know the<00:13:21.010> the<00:13:21.040> solidity<00:13:21.730> compiler<00:13:22.090> would<00:13:22.990> make<00:13:23.290> me 00:13:23.370 --> 00:13:23.380 align:start position:0% the the solidity compiler would make me 00:13:23.380 --> 00:13:25.860 align:start position:0% the the solidity compiler would make me provide<00:13:23.680> you<00:13:24.610> know<00:13:24.670> the<00:13:24.820> natural<00:13:25.750> language 00:13:25.860 --> 00:13:25.870 align:start position:0% provide you know the natural language 00:13:25.870 --> 00:13:27.210 align:start position:0% provide you know the natural language represent<00:13:26.560> like<00:13:26.740> a<00:13:26.770> natural<00:13:27.100> language 00:13:27.210 --> 00:13:27.220 align:start position:0% represent like a natural language 00:13:27.220 --> 00:13:29.310 align:start position:0% represent like a natural language specification<00:13:28.150> but<00:13:28.420> when<00:13:28.600> the<00:13:28.690> translating 00:13:29.310 --> 00:13:29.320 align:start position:0% specification but when the translating 00:13:29.320 --> 00:13:31.820 align:start position:0% specification but when the translating code<00:13:29.500> and<00:13:29.830> then<00:13:30.730> it<00:13:31.030> would<00:13:31.300> be<00:13:31.330> a<00:13:31.420> primitive 00:13:31.820 --> 00:13:31.830 align:start position:0% code and then it would be a primitive 00:13:31.830 --> 00:13:33.870 align:start position:0% code and then it would be a primitive address<00:13:32.830> book<00:13:32.980> perhaps<00:13:33.340> to<00:13:33.550> be<00:13:33.640> a<00:13:33.670> primitive 00:13:33.870 --> 00:13:33.880 align:start position:0% address book perhaps to be a primitive 00:13:33.880 --> 00:13:36.480 align:start position:0% address book perhaps to be a primitive but<00:13:34.330> you<00:13:34.810> know<00:13:34.930> wherever<00:13:35.080> there's<00:13:35.350> a<00:13:35.440> gap<00:13:35.620> how 00:13:36.480 --> 00:13:36.490 align:start position:0% but you know wherever there's a gap how 00:13:36.490 --> 00:13:38.070 align:start position:0% but you know wherever there's a gap how do<00:13:36.550> you<00:13:36.640> represent<00:13:36.790> what<00:13:37.300> a<00:13:37.510> mapping<00:13:37.990> is 00:13:38.070 --> 00:13:38.080 align:start position:0% do you represent what a mapping is 00:13:38.080 --> 00:13:41.550 align:start position:0% do you represent what a mapping is primitively<00:13:38.910> well<00:13:39.910> i<00:13:39.940> mean<00:13:40.240> permanent<00:13:41.170> is<00:13:41.230> the 00:13:41.550 --> 00:13:41.560 align:start position:0% primitively well i mean permanent is the 00:13:41.560 --> 00:13:42.660 align:start position:0% primitively well i mean permanent is the wrong<00:13:41.770> word<00:13:41.980> here 00:13:42.660 --> 00:13:42.670 align:start position:0% wrong word here 00:13:42.670 --> 00:13:46.050 align:start position:0% wrong word here but<00:13:42.970> well<00:13:43.630> so<00:13:43.930> maybe<00:13:44.170> we<00:13:44.260> should<00:13:44.550> who<00:13:45.550> here<00:13:45.850> has 00:13:46.050 --> 00:13:46.060 align:start position:0% but well so maybe we should who here has 00:13:46.060 --> 00:13:49.110 align:start position:0% but well so maybe we should who here has seen<00:13:46.720> their<00:13:47.410> what<00:13:47.620> depe<00:13:47.830> way<00:13:48.520> that<00:13:48.760> solidity 00:13:49.110 --> 00:13:49.120 align:start position:0% seen their what depe way that solidity 00:13:49.120 --> 00:13:54.210 align:start position:0% seen their what depe way that solidity does<00:13:49.390> mappings<00:13:49.900> under<00:13:50.230> the<00:13:50.350> hood<00:13:50.500> I<00:13:53.220> don't 00:13:54.210 --> 00:13:54.220 align:start position:0% does mappings under the hood I don't 00:13:54.220 --> 00:13:55.950 align:start position:0% does mappings under the hood I don't know<00:13:54.310> if<00:13:54.400> we<00:13:54.490> should<00:13:54.520> get<00:13:54.760> into<00:13:55.030> it<00:13:55.180> yeah<00:13:55.630> so 00:13:55.950 --> 00:13:55.960 align:start position:0% know if we should get into it yeah so 00:13:55.960 --> 00:13:59.850 align:start position:0% know if we should get into it yeah so I'll<00:13:56.050> get<00:13:56.230> into<00:13:56.350> it<00:13:57.510> right<00:13:58.510> now<00:13:58.570> I<00:13:58.720> had<00:13:59.590> to<00:13:59.680> get 00:13:59.850 --> 00:13:59.860 align:start position:0% I'll get into it right now I had to get 00:13:59.860 --> 00:14:07.460 align:start position:0% I'll get into it right now I had to get through<00:14:00.040> all<00:14:00.250> right<00:14:03.120> yes<00:14:04.120> so<00:14:05.100> then<00:14:06.100> you<00:14:06.280> get<00:14:06.430> to 00:14:07.460 --> 00:14:07.470 align:start position:0% through all right yes so then you get to 00:14:07.470 --> 00:14:11.160 align:start position:0% through all right yes so then you get to relatively<00:14:08.470> what<00:14:09.370> about<00:14:09.580> call<00:14:10.540> data<00:14:10.720> pointers 00:14:11.160 --> 00:14:11.170 align:start position:0% relatively what about call data pointers 00:14:11.170 --> 00:14:13.200 align:start position:0% relatively what about call data pointers pointers<00:14:11.680> and<00:14:11.890> call<00:14:12.040> data<00:14:12.280> are<00:14:12.490> relative<00:14:12.940> but 00:14:13.200 --> 00:14:13.210 align:start position:0% pointers and call data are relative but 00:14:13.210 --> 00:14:14.670 align:start position:0% pointers and call data are relative but they're<00:14:13.390> not<00:14:13.480> relative<00:14:13.870> to<00:14:13.900> themselves<00:14:14.350> their 00:14:14.670 --> 00:14:14.680 align:start position:0% they're not relative to themselves their 00:14:14.680 --> 00:14:16.350 align:start position:0% they're not relative to themselves their relative<00:14:15.100> to<00:14:15.340> the<00:14:15.520> beginning<00:14:16.180> of<00:14:16.270> the 00:14:16.350 --> 00:14:16.360 align:start position:0% relative to the beginning of the 00:14:16.360 --> 00:14:20.240 align:start position:0% relative to the beginning of the structure<00:14:16.690> that<00:14:16.720> contains<00:14:16.990> them<00:14:18.120> so<00:14:19.140> that 00:14:20.240 --> 00:14:20.250 align:start position:0% structure that contains them so that 00:14:20.250 --> 00:14:24.060 align:start position:0% structure that contains them so that potentially<00:14:21.250> poses<00:14:21.550> some<00:14:21.670> problems<00:14:22.560> out<00:14:23.560> of 00:14:24.060 --> 00:14:24.070 align:start position:0% potentially poses some problems out of 00:14:24.070 --> 00:14:26.880 align:start position:0% potentially poses some problems out of it<00:14:24.250> represent<00:14:24.640> composite<00:14:25.090> types<00:14:25.650> like<00:14:26.650> how<00:14:26.830> do 00:14:26.880 --> 00:14:26.890 align:start position:0% it represent composite types like how do 00:14:26.890 --> 00:14:28.860 align:start position:0% it represent composite types like how do we<00:14:27.040> need<00:14:27.520> to<00:14:27.580> give<00:14:27.730> you<00:14:28.180> presumably<00:14:28.510> we<00:14:28.720> need 00:14:28.860 --> 00:14:28.870 align:start position:0% we need to give you presumably we need 00:14:28.870 --> 00:14:30.810 align:start position:0% we need to give you presumably we need to<00:14:28.930> give<00:14:29.050> the<00:14:29.800> people<00:14:29.950> using<00:14:30.280> this<00:14:30.460> more<00:14:30.640> map<00:14:30.790> a 00:14:30.810 --> 00:14:30.820 align:start position:0% to give the people using this more map a 00:14:30.820 --> 00:14:33.480 align:start position:0% to give the people using this more map a way<00:14:31.000> to<00:14:31.060> specify<00:14:31.510> in<00:14:32.470> composite<00:14:33.070> types<00:14:33.250> than 00:14:33.480 --> 00:14:33.490 align:start position:0% way to specify in composite types than 00:14:33.490 --> 00:14:35.160 align:start position:0% way to specify in composite types than like<00:14:33.640> how<00:14:33.790> they<00:14:34.000> work<00:14:34.180> and<00:14:34.420> these<00:14:34.750> could<00:14:35.020> be 00:14:35.160 --> 00:14:35.170 align:start position:0% like how they work and these could be 00:14:35.170 --> 00:14:36.990 align:start position:0% like how they work and these could be structs<00:14:35.920> but<00:14:36.280> they<00:14:36.370> could<00:14:36.490> also<00:14:36.610> be<00:14:36.730> things 00:14:36.990 --> 00:14:37.000 align:start position:0% structs but they could also be things 00:14:37.000 --> 00:14:39.210 align:start position:0% structs but they could also be things that<00:14:37.060> in<00:14:37.270> solidity<00:14:37.630> are<00:14:37.810> our<00:14:38.320> primitives<00:14:39.010> but 00:14:39.210 --> 00:14:39.220 align:start position:0% that in solidity are our primitives but 00:14:39.220 --> 00:14:41.400 align:start position:0% that in solidity are our primitives but that<00:14:39.400> are<00:14:39.550> logically<00:14:40.450> speaking<00:14:40.600> composite 00:14:41.400 --> 00:14:41.410 align:start position:0% that are logically speaking composite 00:14:41.410 --> 00:14:43.560 align:start position:0% that are logically speaking composite such<00:14:41.590> as<00:14:41.740> for<00:14:41.860> instance<00:14:41.890> an<00:14:42.700> extra<00:14:43.150> function 00:14:43.560 --> 00:14:43.570 align:start position:0% such as for instance an extra function 00:14:43.570 --> 00:14:45.120 align:start position:0% such as for instance an extra function pointer<00:14:43.870> which<00:14:44.080> after<00:14:44.410> all<00:14:44.470> consists<00:14:44.890> of<00:14:44.950> an 00:14:45.120 --> 00:14:45.130 align:start position:0% pointer which after all consists of an 00:14:45.130 --> 00:14:48.270 align:start position:0% pointer which after all consists of an address<00:14:45.370> and<00:14:45.700> a<00:14:45.760> selector<00:14:46.470> or<00:14:47.470> an<00:14:47.920> internal 00:14:48.270 --> 00:14:48.280 align:start position:0% address and a selector or an internal 00:14:48.280 --> 00:14:50.370 align:start position:0% address and a selector or an internal function<00:14:48.670> pointer<00:14:49.000> which<00:14:49.210> table<00:14:49.450> consists<00:14:50.320> of 00:14:50.370 --> 00:14:50.380 align:start position:0% function pointer which table consists of 00:14:50.380 --> 00:14:52.560 align:start position:0% function pointer which table consists of two<00:14:50.860> separate<00:14:51.580> values<00:14:51.670> a<00:14:51.880> program<00:14:52.390> counter 00:14:52.560 --> 00:14:52.570 align:start position:0% two separate values a program counter 00:14:52.570 --> 00:14:55.140 align:start position:0% two separate values a program counter plug<00:14:52.960> for<00:14:53.140> the<00:14:53.610> constructor<00:14:54.610> bytecode<00:14:54.940> one 00:14:55.140 --> 00:14:55.150 align:start position:0% plug for the constructor bytecode one 00:14:55.150 --> 00:14:56.670 align:start position:0% plug for the constructor bytecode one for<00:14:55.300> the<00:14:55.360> deployment<00:14:55.630> it's<00:14:55.930> really<00:14:56.350> really 00:14:56.670 --> 00:14:56.680 align:start position:0% for the deployment it's really really 00:14:56.680 --> 00:14:58.830 align:start position:0% for the deployment it's really really interesting<00:14:56.800> how<00:14:57.340> its<00:14:57.730> internal<00:14:58.510> function 00:14:58.830 --> 00:14:58.840 align:start position:0% interesting how its internal function 00:14:58.840 --> 00:15:00.810 align:start position:0% interesting how its internal function pointers<00:14:59.110> are<00:14:59.230> in<00:14:59.380> solidity<00:14:59.680> like<00:15:00.250> how<00:15:00.700> he's 00:15:00.810 --> 00:15:00.820 align:start position:0% pointers are in solidity like how he's 00:15:00.820 --> 00:15:05.660 align:start position:0% pointers are in solidity like how he's saying<00:15:01.090> is<00:15:01.300> that<00:15:01.600> it's<00:15:02.470> an<00:15:02.650> 8<00:15:02.920> byte<00:15:04.020> value 00:15:05.660 --> 00:15:05.670 align:start position:0% saying is that it's an 8 byte value 00:15:05.670 --> 00:15:08.820 align:start position:0% saying is that it's an 8 byte value where<00:15:06.670> the<00:15:06.940> first<00:15:07.210> byte<00:15:07.480> is<00:15:07.720> if<00:15:08.050> for<00:15:08.410> like 00:15:08.820 --> 00:15:08.830 align:start position:0% where the first byte is if for like 00:15:08.830 --> 00:15:12.240 align:start position:0% where the first byte is if for like first<00:15:09.160> 4<00:15:09.400> bytes<00:15:09.720> are<00:15:10.720> for<00:15:11.140> the<00:15:11.230> constructor<00:15:11.860> so 00:15:12.240 --> 00:15:12.250 align:start position:0% first 4 bytes are for the constructor so 00:15:12.250 --> 00:15:14.040 align:start position:0% first 4 bytes are for the constructor so you<00:15:12.970> know<00:15:13.090> you<00:15:13.210> have<00:15:13.300> a<00:15:13.390> pointer<00:15:13.720> to<00:15:13.750> some 00:15:14.040 --> 00:15:14.050 align:start position:0% you know you have a pointer to some 00:15:14.050 --> 00:15:16.890 align:start position:0% you know you have a pointer to some function<00:15:14.260> and<00:15:14.590> like<00:15:15.370> a<00:15:15.400> you<00:15:16.330> know<00:15:16.420> an<00:15:16.540> internal 00:15:16.890 --> 00:15:16.900 align:start position:0% function and like a you know an internal 00:15:16.900 --> 00:15:18.570 align:start position:0% function and like a you know an internal function<00:15:17.260> you<00:15:17.350> want<00:15:17.800> to<00:15:17.920> store<00:15:18.310> that<00:15:18.460> in<00:15:18.550> a 00:15:18.570 --> 00:15:18.580 align:start position:0% function you want to store that in a 00:15:18.580 --> 00:15:20.460 align:start position:0% function you want to store that in a variable<00:15:18.610> it's<00:15:19.510> like<00:15:19.660> maybe<00:15:19.870> you<00:15:20.020> have<00:15:20.200> a<00:15:20.290> math 00:15:20.460 --> 00:15:20.470 align:start position:0% variable it's like maybe you have a math 00:15:20.470 --> 00:15:22.200 align:start position:0% variable it's like maybe you have a math function<00:15:20.650> that<00:15:21.160> takes<00:15:21.310> another<00:15:21.580> function 00:15:22.200 --> 00:15:22.210 align:start position:0% function that takes another function 00:15:22.210 --> 00:15:25.740 align:start position:0% function that takes another function if<00:15:23.050> you<00:15:23.770> need<00:15:24.670> to<00:15:24.820> point<00:15:25.120> to<00:15:25.270> that<00:15:25.390> in<00:15:25.630> the 00:15:25.740 --> 00:15:25.750 align:start position:0% if you need to point to that in the 00:15:25.750 --> 00:15:28.050 align:start position:0% if you need to point to that in the actual<00:15:25.870> evm<00:15:26.680> bytecode<00:15:27.190> you<00:15:27.520> just<00:15:27.730> you<00:15:27.910> have<00:15:27.940> to 00:15:28.050 --> 00:15:28.060 align:start position:0% actual evm bytecode you just you have to 00:15:28.060 --> 00:15:31.800 align:start position:0% actual evm bytecode you just you have to point<00:15:28.300> to<00:15:28.420> some<00:15:28.720> some<00:15:29.380> byte<00:15:29.589> offset<00:15:30.360> but<00:15:31.360> with 00:15:31.800 --> 00:15:31.810 align:start position:0% point to some some byte offset but with 00:15:31.810 --> 00:15:33.870 align:start position:0% point to some some byte offset but with smart<00:15:32.440> contracts<00:15:32.800> you<00:15:32.950> have<00:15:32.980> the<00:15:33.279> constructor 00:15:33.870 --> 00:15:33.880 align:start position:0% smart contracts you have the constructor 00:15:33.880 --> 00:15:35.970 align:start position:0% smart contracts you have the constructor byte<00:15:34.089> code<00:15:34.360> the<00:15:35.050> code<00:15:35.230> that<00:15:35.410> runs<00:15:35.589> when<00:15:35.890> you 00:15:35.970 --> 00:15:35.980 align:start position:0% byte code the code that runs when you 00:15:35.980 --> 00:15:37.950 align:start position:0% byte code the code that runs when you deploy<00:15:36.190> the<00:15:36.430> contract<00:15:36.910> and<00:15:37.060> you<00:15:37.570> have<00:15:37.750> the 00:15:37.950 --> 00:15:37.960 align:start position:0% deploy the contract and you have the 00:15:37.960 --> 00:15:40.170 align:start position:0% deploy the contract and you have the runtime<00:15:38.500> byte<00:15:38.770> code<00:15:39.070> which<00:15:39.700> runs<00:15:39.940> when<00:15:40.089> you 00:15:40.170 --> 00:15:40.180 align:start position:0% runtime byte code which runs when you 00:15:40.180 --> 00:15:41.970 align:start position:0% runtime byte code which runs when you send<00:15:40.360> a<00:15:40.420> transaction<00:15:40.750> to<00:15:41.050> the<00:15:41.140> contract<00:15:41.589> and 00:15:41.970 --> 00:15:41.980 align:start position:0% send a transaction to the contract and 00:15:41.980 --> 00:15:44.160 align:start position:0% send a transaction to the contract and they're<00:15:42.430> not<00:15:42.580> the<00:15:42.700> same<00:15:42.820> byte<00:15:43.060> code<00:15:43.330> so<00:15:43.990> if<00:15:44.080> you 00:15:44.160 --> 00:15:44.170 align:start position:0% they're not the same byte code so if you 00:15:44.170 --> 00:15:45.630 align:start position:0% they're not the same byte code so if you want<00:15:44.320> to<00:15:44.380> point<00:15:44.620> to<00:15:44.800> a<00:15:44.830> function<00:15:45.310> you<00:15:45.459> know<00:15:45.580> you 00:15:45.630 --> 00:15:45.640 align:start position:0% want to point to a function you know you 00:15:45.640 --> 00:15:47.280 align:start position:0% want to point to a function you know you have<00:15:45.790> these<00:15:45.880> two<00:15:46.089> separate<00:15:46.420> byte<00:15:46.600> codes<00:15:46.839> you 00:15:47.280 --> 00:15:47.290 align:start position:0% have these two separate byte codes you 00:15:47.290 --> 00:15:48.389 align:start position:0% have these two separate byte codes you want<00:15:47.410> to<00:15:47.470> point<00:15:47.649> to<00:15:47.770> some<00:15:47.950> words<00:15:48.070> you<00:15:48.130> need<00:15:48.279> to 00:15:48.389 --> 00:15:48.399 align:start position:0% want to point to some words you need to 00:15:48.399 --> 00:15:53.960 align:start position:0% want to point to some words you need to represent<00:15:48.850> both<00:15:49.029> of<00:15:49.089> those<00:15:51.959> anyway<00:15:52.959> moving<00:15:53.230> on 00:15:53.960 --> 00:15:53.970 align:start position:0% represent both of those anyway moving on 00:15:53.970 --> 00:15:56.430 align:start position:0% represent both of those anyway moving on well<00:15:54.970> this<00:15:55.089> second<00:15:55.779> last<00:15:55.959> one<00:15:56.140> I've<00:15:56.260> already 00:15:56.430 --> 00:15:56.440 align:start position:0% well this second last one I've already 00:15:56.440 --> 00:15:57.030 align:start position:0% well this second last one I've already talked<00:15:56.740> about 00:15:57.030 --> 00:15:57.040 align:start position:0% talked about 00:15:57.040 --> 00:15:58.560 align:start position:0% talked about where's<00:15:57.399> how<00:15:57.790> do<00:15:57.850> we<00:15:58.000> draw<00:15:58.180> the<00:15:58.270> line<00:15:58.540> between 00:15:58.560 --> 00:15:58.570 align:start position:0% where's how do we draw the line between 00:15:58.570 --> 00:16:00.420 align:start position:0% where's how do we draw the line between you<00:15:59.350> know<00:15:59.380> to<00:15:59.709> what<00:15:59.830> extent<00:15:59.860> to<00:16:00.160> be<00:16:00.220> water 00:16:00.420 --> 00:16:00.430 align:start position:0% you know to what extent to be water 00:16:00.430 --> 00:16:02.370 align:start position:0% you know to what extent to be water reliant<00:16:00.880> home<00:16:01.029> base<00:16:01.270> extensions<00:16:01.810> persons<00:16:02.290> to 00:16:02.370 --> 00:16:02.380 align:start position:0% reliant home base extensions persons to 00:16:02.380 --> 00:16:04.620 align:start position:0% reliant home base extensions persons to what<00:16:02.529> extent<00:16:02.800> do<00:16:02.890> we<00:16:02.920> want<00:16:03.190> to<00:16:03.250> rely<00:16:03.459> on<00:16:03.630> data 00:16:04.620 --> 00:16:04.630 align:start position:0% what extent do we want to rely on data 00:16:04.630 --> 00:16:07.139 align:start position:0% what extent do we want to rely on data that<00:16:04.990> you<00:16:05.709> know<00:16:05.830> and<00:16:06.040> just<00:16:06.399> building<00:16:07.029> that 00:16:07.139 --> 00:16:07.149 align:start position:0% that you know and just building that 00:16:07.149 --> 00:16:11.100 align:start position:0% that you know and just building that stuff<00:16:07.390> into<00:16:07.630> the<00:16:07.930> format<00:16:08.649> I<00:16:09.930> have<00:16:10.930> had 00:16:11.100 --> 00:16:11.110 align:start position:0% stuff into the format I have had 00:16:11.110 --> 00:16:12.630 align:start position:0% stuff into the format I have had differing<00:16:11.560> opinions<00:16:11.950> on<00:16:12.070> this<00:16:12.220> but<00:16:12.279> let's 00:16:12.630 --> 00:16:12.640 align:start position:0% differing opinions on this but let's 00:16:12.640 --> 00:16:14.160 align:start position:0% differing opinions on this but let's save<00:16:13.420> that<00:16:13.450> for<00:16:13.630> another<00:16:13.779> time 00:16:14.160 --> 00:16:14.170 align:start position:0% save that for another time 00:16:14.170 --> 00:16:19.769 align:start position:0% save that for another time and<00:16:14.940> the<00:16:15.940> first<00:16:16.209> one<00:16:16.450> how<00:16:16.810> do<00:16:16.870> we<00:16:18.570> how<00:16:19.570> do<00:16:19.630> we 00:16:19.769 --> 00:16:19.779 align:start position:0% and the first one how do we how do we 00:16:19.779 --> 00:16:21.480 align:start position:0% and the first one how do we how do we determine<00:16:20.110> how<00:16:20.680> many<00:16:20.830> members<00:16:21.010> that<00:16:21.220> we're 00:16:21.480 --> 00:16:21.490 align:start position:0% determine how many members that we're 00:16:21.490 --> 00:16:24.780 align:start position:0% determine how many members that we're local<00:16:21.730> variables<00:16:22.270> are<00:16:22.740> not<00:16:23.740> a<00:16:24.040> fixed<00:16:24.640> location 00:16:24.780 --> 00:16:24.790 align:start position:0% local variables are not a fixed location 00:16:24.790 --> 00:16:26.310 align:start position:0% local variables are not a fixed location right<00:16:25.270> I<00:16:25.330> mean<00:16:25.480> newest<00:16:25.660> state<00:16:25.870> variables 00:16:26.310 --> 00:16:26.320 align:start position:0% right I mean newest state variables 00:16:26.320 --> 00:16:27.780 align:start position:0% right I mean newest state variables these<00:16:26.470> live<00:16:26.650> in<00:16:26.770> a<00:16:26.800> fixed<00:16:27.040> location<00:16:27.190> local 00:16:27.780 --> 00:16:27.790 align:start position:0% these live in a fixed location local 00:16:27.790 --> 00:16:30.240 align:start position:0% these live in a fixed location local variables<00:16:28.300> these<00:16:28.690> live<00:16:28.900> on<00:16:29.020> the<00:16:29.140> stack<00:16:29.410> it's 00:16:30.240 --> 00:16:30.250 align:start position:0% variables these live on the stack it's 00:16:30.250 --> 00:16:32.970 align:start position:0% variables these live on the stack it's going<00:16:30.490> to<00:16:30.610> depend<00:16:30.910> on<00:16:31.360> you<00:16:32.050> know<00:16:32.080> what's<00:16:32.650> below 00:16:32.970 --> 00:16:32.980 align:start position:0% going to depend on you know what's below 00:16:32.980 --> 00:16:35.510 align:start position:0% going to depend on you know what's below you<00:16:33.130> on<00:16:33.310> the<00:16:33.430> stack<00:16:33.640> how<00:16:34.300> far<00:16:34.600> up<00:16:34.779> monthly 00:16:35.510 --> 00:16:35.520 align:start position:0% you on the stack how far up monthly 00:16:35.520 --> 00:16:38.880 align:start position:0% you on the stack how far up monthly weird<00:16:36.520> dysfunction<00:16:37.240> snap<00:16:37.510> frames<00:16:37.870> start<00:16:38.200> now 00:16:38.880 --> 00:16:38.890 align:start position:0% weird dysfunction snap frames start now 00:16:38.890 --> 00:16:41.010 align:start position:0% weird dysfunction snap frames start now you<00:16:39.190> know<00:16:39.310> if<00:16:39.490> you're<00:16:39.730> used<00:16:40.270> to<00:16:40.390> running<00:16:40.570> you 00:16:41.010 --> 00:16:41.020 align:start position:0% you know if you're used to running you 00:16:41.020 --> 00:16:43.170 align:start position:0% you know if you're used to running you know<00:16:41.140> things<00:16:41.440> on<00:16:41.620> you<00:16:41.800> know<00:16:41.830> x86<00:16:42.730> or<00:16:42.850> whatever 00:16:43.170 --> 00:16:43.180 align:start position:0% know things on you know x86 or whatever 00:16:43.180 --> 00:16:44.699 align:start position:0% know things on you know x86 or whatever it's<00:16:43.390> like<00:16:43.540> oh<00:16:43.690> you<00:16:43.870> look<00:16:43.900> at<00:16:44.170> the<00:16:44.260> frame<00:16:44.410> water 00:16:44.699 --> 00:16:44.709 align:start position:0% it's like oh you look at the frame water 00:16:44.709 --> 00:16:45.960 align:start position:0% it's like oh you look at the frame water we<00:16:44.890> don't<00:16:44.980> there's<00:16:45.250> no<00:16:45.370> silly<00:16:45.610> personal 00:16:45.960 --> 00:16:45.970 align:start position:0% we don't there's no silly personal 00:16:45.970 --> 00:16:48.530 align:start position:0% we don't there's no silly personal three-pointers<00:16:46.420> in<00:16:46.450> the<00:16:46.600> solidity<00:16:47.070> there 00:16:48.530 --> 00:16:48.540 align:start position:0% three-pointers in the solidity there 00:16:48.540 --> 00:16:50.790 align:start position:0% three-pointers in the solidity there there<00:16:49.540> are<00:16:49.630> no<00:16:49.750> free<00:16:49.900> pointers<00:16:50.230> in<00:16:50.410> solidity 00:16:50.790 --> 00:16:50.800 align:start position:0% there are no free pointers in solidity 00:16:50.800 --> 00:16:54.000 align:start position:0% there are no free pointers in solidity other<00:16:51.700> words<00:16:52.029> maybe<00:16:53.020> to<00:16:53.290> try<00:16:53.500> and<00:16:53.620> write<00:16:53.980> a 00:16:54.000 --> 00:16:54.010 align:start position:0% other words maybe to try and write a 00:16:54.010 --> 00:16:56.070 align:start position:0% other words maybe to try and write a second<00:16:54.400> explanation<00:16:54.750> let's<00:16:55.750> say<00:16:55.839> you<00:16:55.900> call 00:16:56.070 --> 00:16:56.080 align:start position:0% second explanation let's say you call 00:16:56.080 --> 00:17:00.000 align:start position:0% second explanation let's say you call function<00:16:56.529> when<00:16:57.459> you<00:16:57.490> call<00:16:57.730> that<00:16:57.850> function<00:16:59.010> it 00:17:00.000 --> 00:17:00.010 align:start position:0% function when you call that function it 00:17:00.010 --> 00:17:02.010 align:start position:0% function when you call that function it goes<00:17:00.190> on<00:17:00.370> the<00:17:00.430> call<00:17:00.610> stack<00:17:00.910> as<00:17:01.150> a<00:17:01.209> frame<00:17:01.690> and 00:17:02.010 --> 00:17:02.020 align:start position:0% goes on the call stack as a frame and 00:17:02.020 --> 00:17:03.810 align:start position:0% goes on the call stack as a frame and there's<00:17:02.860> a<00:17:02.920> bunch<00:17:03.040> of<00:17:03.100> variables<00:17:03.459> maybe<00:17:03.580> your 00:17:03.810 --> 00:17:03.820 align:start position:0% there's a bunch of variables maybe your 00:17:03.820 --> 00:17:06.809 align:start position:0% there's a bunch of variables maybe your function<00:17:04.270> declares<00:17:04.569> a<00:17:04.720> B<00:17:04.900> and<00:17:05.020> C<00:17:05.250> those<00:17:06.250> three 00:17:06.809 --> 00:17:06.819 align:start position:0% function declares a B and C those three 00:17:06.819 --> 00:17:09.179 align:start position:0% function declares a B and C those three variables<00:17:07.120> go<00:17:07.449> on<00:17:07.569> the<00:17:07.660> stack<00:17:07.900> and<00:17:08.170> then<00:17:08.260> you 00:17:09.179 --> 00:17:09.189 align:start position:0% variables go on the stack and then you 00:17:09.189 --> 00:17:12.329 align:start position:0% variables go on the stack and then you have<00:17:09.309> some<00:17:09.640> working<00:17:10.260> space<00:17:11.260> for<00:17:11.589> like<00:17:12.040> maybe 00:17:12.329 --> 00:17:12.339 align:start position:0% have some working space for like maybe 00:17:12.339 --> 00:17:15.000 align:start position:0% have some working space for like maybe you<00:17:12.490> do<00:17:12.640> some<00:17:13.199> complex<00:17:14.199> expression<00:17:14.800> and<00:17:14.949> you 00:17:15.000 --> 00:17:15.010 align:start position:0% you do some complex expression and you 00:17:15.010 --> 00:17:16.310 align:start position:0% you do some complex expression and you have<00:17:15.100> to<00:17:15.220> add<00:17:15.339> and<00:17:15.730> multiply 00:17:16.310 --> 00:17:16.320 align:start position:0% have to add and multiply 00:17:16.320 --> 00:17:17.360 align:start position:0% have to add and multiply that's<00:17:16.470> Armand<00:17:16.770> so<00:17:16.860> you<00:17:16.950> have<00:17:17.040> a<00:17:17.070> bunch<00:17:17.190> of 00:17:17.360 --> 00:17:17.370 align:start position:0% that's Armand so you have a bunch of 00:17:17.370 --> 00:17:18.830 align:start position:0% that's Armand so you have a bunch of other<00:17:17.490> bad<00:17:17.670> loops<00:17:17.850> on<00:17:17.970> the<00:17:18.060> stack<00:17:18.300> on<00:17:18.570> top<00:17:18.630> of 00:17:18.830 --> 00:17:18.840 align:start position:0% other bad loops on the stack on top of 00:17:18.840 --> 00:17:22.520 align:start position:0% other bad loops on the stack on top of the<00:17:19.020> variables<00:17:19.970> you<00:17:20.970> have<00:17:21.030> to<00:17:21.270> know<00:17:21.840> where 00:17:22.520 --> 00:17:22.530 align:start position:0% the variables you have to know where 00:17:22.530 --> 00:17:24.670 align:start position:0% the variables you have to know where that<00:17:22.770> frame<00:17:23.070> begins 00:17:24.670 --> 00:17:24.680 align:start position:0% that frame begins 00:17:24.680 --> 00:17:29.000 align:start position:0% that frame begins why<00:17:25.680> can<00:17:25.890> you<00:17:25.920> get<00:17:26.190> frame<00:17:26.640> pointer<00:17:27.770> I'm<00:17:28.770> some 00:17:29.000 --> 00:17:29.010 align:start position:0% why can you get frame pointer I'm some 00:17:29.010 --> 00:17:30.620 align:start position:0% why can you get frame pointer I'm some nosh-nosh<00:17:29.190> there's<00:17:29.700> no<00:17:29.880> it<00:17:30.120> doesn't<00:17:30.570> make 00:17:30.620 --> 00:17:30.630 align:start position:0% nosh-nosh there's no it doesn't make 00:17:30.630 --> 00:17:34.300 align:start position:0% nosh-nosh there's no it doesn't make access<00:17:30.990> to<00:17:31.140> the<00:17:31.230> stack 00:17:34.300 --> 00:17:34.310 align:start position:0% 00:17:34.310 --> 00:17:37.510 align:start position:0% oh<00:17:34.390> that's<00:17:35.390> a<00:17:35.660> really<00:17:35.960> good<00:17:36.170> point<00:17:36.440> I<00:17:37.010> mean 00:17:37.510 --> 00:17:37.520 align:start position:0% oh that's a really good point I mean 00:17:37.520 --> 00:17:39.070 align:start position:0% oh that's a really good point I mean they're<00:17:37.970> thinking<00:17:38.360> about<00:17:38.450> adding<00:17:38.960> those 00:17:39.070 --> 00:17:39.080 align:start position:0% they're thinking about adding those 00:17:39.080 --> 00:17:41.860 align:start position:0% they're thinking about adding those opcodes<00:17:39.590> but<00:17:39.830> they<00:17:39.980> told<00:17:40.220> ya<00:17:40.520> those<00:17:40.850> in<00:17:41.090> those 00:17:41.860 --> 00:17:41.870 align:start position:0% opcodes but they told ya those in those 00:17:41.870 --> 00:17:43.570 align:start position:0% opcodes but they told ya those in those simply<00:17:42.290> do<00:17:42.470> not<00:17:42.620> exist<00:17:42.770> in<00:17:43.130> like<00:17:43.310> there's<00:17:43.490> no 00:17:43.570 --> 00:17:43.580 align:start position:0% simply do not exist in like there's no 00:17:43.580 --> 00:17:45.100 align:start position:0% simply do not exist in like there's no way<00:17:43.670> you<00:17:43.760> could've<00:17:44.000> anticipated<00:17:44.150> that<00:17:44.900> or 00:17:45.100 --> 00:17:45.110 align:start position:0% way you could've anticipated that or 00:17:45.110 --> 00:17:46.240 align:start position:0% way you could've anticipated that or like<00:17:45.290> you're<00:17:45.530> like<00:17:45.680> oh<00:17:45.800> yeah<00:17:45.860> we're<00:17:46.160> gonna 00:17:46.240 --> 00:17:46.250 align:start position:0% like you're like oh yeah we're gonna 00:17:46.250 --> 00:17:48.040 align:start position:0% like you're like oh yeah we're gonna wait<00:17:46.460> for<00:17:46.640> them<00:17:46.700> to<00:17:46.760> add<00:17:47.030> dynamic<00:17:47.570> access<00:17:47.750> to 00:17:48.040 --> 00:17:48.050 align:start position:0% wait for them to add dynamic access to 00:17:48.050 --> 00:17:50.890 align:start position:0% wait for them to add dynamic access to the<00:17:48.110> stack<00:17:48.440> like<00:17:49.190> yeah<00:17:50.060> that's<00:17:50.450> actually<00:17:50.720> a 00:17:50.890 --> 00:17:50.900 align:start position:0% the stack like yeah that's actually a 00:17:50.900 --> 00:17:51.970 align:start position:0% the stack like yeah that's actually a really<00:17:51.050> good<00:17:51.290> reason<00:17:51.440> that<00:17:51.620> I<00:17:51.710> didn't<00:17:51.890> think 00:17:51.970 --> 00:17:51.980 align:start position:0% really good reason that I didn't think 00:17:51.980 --> 00:17:55.150 align:start position:0% really good reason that I didn't think of<00:17:52.190> oh<00:17:52.660> well<00:17:53.660> okay<00:17:54.140> now<00:17:54.410> we're<00:17:54.560> not<00:17:54.950> dealing 00:17:55.150 --> 00:17:55.160 align:start position:0% of oh well okay now we're not dealing 00:17:55.160 --> 00:17:57.310 align:start position:0% of oh well okay now we're not dealing the<00:17:55.340> freeing<00:17:55.520> point<00:17:55.730> your<00:17:55.850> son<00:17:56.060> yeah<00:17:56.420> there's 00:17:57.310 --> 00:17:57.320 align:start position:0% the freeing point your son yeah there's 00:17:57.320 --> 00:18:01.300 align:start position:0% the freeing point your son yeah there's no<00:17:57.440> point<00:17:59.140> also<00:18:00.140> I<00:18:00.350> want<00:18:00.770> to<00:18:00.830> make<00:18:01.010> the<00:18:01.130> tag 00:18:01.300 --> 00:18:01.310 align:start position:0% no point also I want to make the tag 00:18:01.310 --> 00:18:02.920 align:start position:0% no point also I want to make the tag onto<00:18:01.490> that<00:18:01.700> is<00:18:01.910> that<00:18:02.090> salinities<00:18:02.750> of<00:18:02.870> a 00:18:02.920 --> 00:18:02.930 align:start position:0% onto that is that salinities of a 00:18:02.930 --> 00:18:04.360 align:start position:0% onto that is that salinities of a modifier<00:18:03.380> feature<00:18:03.800> poses<00:18:04.250> additional 00:18:04.360 --> 00:18:04.370 align:start position:0% modifier feature poses additional 00:18:04.370 --> 00:18:06.400 align:start position:0% modifier feature poses additional problems<00:18:05.120> which<00:18:05.330> I'm<00:18:05.510> not<00:18:05.690> going<00:18:05.900> to<00:18:06.050> go<00:18:06.170> into 00:18:06.400 --> 00:18:06.410 align:start position:0% problems which I'm not going to go into 00:18:06.410 --> 00:18:07.840 align:start position:0% problems which I'm not going to go into right<00:18:06.560> now<00:18:06.620> because<00:18:07.190> that<00:18:07.370> would<00:18:07.550> take<00:18:07.700> us 00:18:07.840 --> 00:18:07.850 align:start position:0% right now because that would take us 00:18:07.850 --> 00:18:09.430 align:start position:0% right now because that would take us well<00:18:08.120> our<00:18:08.390> fields<00:18:08.780> suffice<00:18:09.020> it<00:18:09.200> to<00:18:09.230> say<00:18:09.320> that 00:18:09.430 --> 00:18:09.440 align:start position:0% well our fields suffice it to say that 00:18:09.440 --> 00:18:13.870 align:start position:0% well our fields suffice it to say that they<00:18:09.710> they<00:18:09.980> complicate<00:18:10.370> the<00:18:10.580> matter<00:18:12.310> great<00:18:13.310> so 00:18:13.870 --> 00:18:13.880 align:start position:0% they they complicate the matter great so 00:18:13.880 --> 00:18:14.920 align:start position:0% they they complicate the matter great so these<00:18:14.030> are<00:18:14.210> some<00:18:14.330> of<00:18:14.360> the<00:18:14.450> problems<00:18:14.630> we<00:18:14.840> want 00:18:14.920 --> 00:18:14.930 align:start position:0% these are some of the problems we want 00:18:14.930 --> 00:18:16.270 align:start position:0% these are some of the problems we want to<00:18:15.020> solve<00:18:15.170> anyone<00:18:15.680> else<00:18:15.800> have<00:18:15.920> anything<00:18:16.100> else 00:18:16.270 --> 00:18:16.280 align:start position:0% to solve anyone else have anything else 00:18:16.280 --> 00:18:19.840 align:start position:0% to solve anyone else have anything else I<00:18:16.610> can<00:18:17.210> edit<00:18:17.360> the<00:18:17.540> slides<00:18:17.780> down<00:18:18.740> and<00:18:19.490> anyone 00:18:19.840 --> 00:18:19.850 align:start position:0% I can edit the slides down and anyone 00:18:19.850 --> 00:18:26.380 align:start position:0% I can edit the slides down and anyone know<00:18:22.000> yeah<00:18:23.000> maybe<00:18:24.130> also<00:18:25.130> take<00:18:25.400> an<00:18:26.120> approach 00:18:26.380 --> 00:18:26.390 align:start position:0% know yeah maybe also take an approach 00:18:26.390 --> 00:18:31.350 align:start position:0% know yeah maybe also take an approach from<00:18:26.570> the<00:18:26.720> other<00:18:26.840> side<00:18:29.620> they've<00:18:30.620> let's<00:18:30.830> start 00:18:31.350 --> 00:18:31.360 align:start position:0% from the other side they've let's start 00:18:31.360 --> 00:18:34.510 align:start position:0% from the other side they've let's start how<00:18:32.360> do<00:18:32.420> we<00:18:32.600> do<00:18:32.690> it<00:18:32.840> but<00:18:33.260> rather<00:18:33.530> what<00:18:34.310> is<00:18:34.400> the 00:18:34.510 --> 00:18:34.520 align:start position:0% how do we do it but rather what is the 00:18:34.520 --> 00:18:35.920 align:start position:0% how do we do it but rather what is the information<00:18:34.700> we<00:18:35.090> want<00:18:35.180> to<00:18:35.330> have<00:18:35.540> during<00:18:35.870> the 00:18:35.920 --> 00:18:35.930 align:start position:0% information we want to have during the 00:18:35.930 --> 00:18:45.240 align:start position:0% information we want to have during the debugging<00:18:36.140> process<00:18:36.290> oh<00:18:42.460> yeah<00:18:43.460> absolutely 00:18:45.240 --> 00:18:45.250 align:start position:0% debugging process oh yeah absolutely 00:18:45.250 --> 00:18:55.370 align:start position:0% debugging process oh yeah absolutely anything<00:18:46.250> else 00:18:55.370 --> 00:18:55.380 align:start position:0% 00:18:55.380 --> 00:19:02.830 align:start position:0% and<00:18:55.500> that<00:18:56.130> another<00:18:56.280> thing 00:19:02.830 --> 00:19:02.840 align:start position:0% 00:19:02.840 --> 00:19:08.820 align:start position:0% oh<00:19:02.870> I<00:19:03.799> see 00:19:08.820 --> 00:19:08.830 align:start position:0% 00:19:08.830 --> 00:19:14.250 align:start position:0% there<00:19:09.310> we<00:19:09.370> go<00:19:10.050> Amy 00:19:14.250 --> 00:19:14.260 align:start position:0% 00:19:14.260 --> 00:19:21.000 align:start position:0% right<00:19:17.430> I'm<00:19:18.430> sorry<00:19:18.640> Chris<00:19:18.910> gone<00:19:19.620> how<00:19:20.620> to<00:19:20.680> deal 00:19:21.000 --> 00:19:21.010 align:start position:0% right I'm sorry Chris gone how to deal 00:19:21.010 --> 00:19:23.010 align:start position:0% right I'm sorry Chris gone how to deal with<00:19:21.040> in<00:19:21.820> the<00:19:21.970> mediator<00:19:22.210> presentation<00:19:22.810> so<00:19:22.990> if 00:19:23.010 --> 00:19:23.020 align:start position:0% with in the mediator presentation so if 00:19:23.020 --> 00:19:24.750 align:start position:0% with in the mediator presentation so if you<00:19:23.170> can<00:19:23.320> fight<00:19:23.530> through<00:19:23.740> you'll<00:19:24.070> do<00:19:24.370> we<00:19:24.490> also 00:19:24.750 --> 00:19:24.760 align:start position:0% you can fight through you'll do we also 00:19:24.760 --> 00:19:33.460 align:start position:0% you can fight through you'll do we also want<00:19:25.180> to<00:19:25.270> represent<00:19:25.480> excellent 00:19:33.460 --> 00:19:33.470 align:start position:0% 00:19:33.470 --> 00:19:35.440 align:start position:0% so<00:19:33.919> if<00:19:34.009> you<00:19:34.100> have<00:19:34.190> a<00:19:34.220> valley<00:19:34.820> on<00:19:34.940> the<00:19:35.000> stack<00:19:35.269> we 00:19:35.440 --> 00:19:35.450 align:start position:0% so if you have a valley on the stack we 00:19:35.450 --> 00:19:37.629 align:start position:0% so if you have a valley on the stack we want<00:19:35.629> to<00:19:35.720> do<00:19:35.809> only<00:19:36.019> video<00:19:36.620> we<00:19:37.100> only<00:19:37.309> want<00:19:37.580> to 00:19:37.629 --> 00:19:37.639 align:start position:0% want to do only video we only want to 00:19:37.639 --> 00:19:40.539 align:start position:0% want to do only video we only want to know<00:19:37.750> which<00:19:39.070> certificate<00:19:40.070> variable<00:19:40.429> that 00:19:40.539 --> 00:19:40.549 align:start position:0% know which certificate variable that 00:19:40.549 --> 00:19:42.700 align:start position:0% know which certificate variable that represents<00:19:40.730> or<00:19:41.570> we<00:19:41.779> also<00:19:42.019> want<00:19:42.320> to<00:19:42.350> know<00:19:42.500> which 00:19:42.700 --> 00:19:42.710 align:start position:0% represents or we also want to know which 00:19:42.710 --> 00:19:49.940 align:start position:0% represents or we also want to know which you<00:19:42.950> will<00:19:43.070> but<00:19:43.250> ever<00:19:43.639> since 00:19:49.940 --> 00:19:49.950 align:start position:0% 00:19:49.950 --> 00:19:57.590 align:start position:0% [Music] 00:19:57.590 --> 00:19:57.600 align:start position:0% 00:19:57.600 --> 00:19:59.930 align:start position:0% that's<00:19:58.259> interesting<00:19:58.710> them<00:19:58.950> to<00:19:59.519> do<00:19:59.609> that<00:19:59.759> the 00:19:59.930 --> 00:19:59.940 align:start position:0% that's interesting them to do that the 00:19:59.940 --> 00:20:01.759 align:start position:0% that's interesting them to do that the same<00:20:00.119> in<00:20:00.509> the<00:20:00.600> same<00:20:00.749> location<00:20:01.229> like<00:20:01.470> oh<00:20:01.590> this 00:20:01.759 --> 00:20:01.769 align:start position:0% same in the same location like oh this 00:20:01.769 --> 00:20:18.739 align:start position:0% same in the same location like oh this is<00:20:01.919> this<00:20:02.039> variable<00:20:02.429> is<00:20:02.519> this<00:20:02.729> variable<00:20:17.749> we 00:20:18.739 --> 00:20:18.749 align:start position:0% is this variable is this variable we 00:20:18.749 --> 00:20:20.450 align:start position:0% is this variable is this variable we want<00:20:18.989> it<00:20:19.049> to<00:20:19.169> be<00:20:19.259> more<00:20:19.499> general<00:20:19.859> than<00:20:19.979> just<00:20:20.220> for 00:20:20.450 --> 00:20:20.460 align:start position:0% want it to be more general than just for 00:20:20.460 --> 00:20:22.879 align:start position:0% want it to be more general than just for solidity<00:20:21.059> and<00:20:21.330> part<00:20:21.659> of<00:20:21.749> the<00:20:21.899> idea<00:20:21.960> of<00:20:22.590> having 00:20:22.879 --> 00:20:22.889 align:start position:0% solidity and part of the idea of having 00:20:22.889 --> 00:20:25.759 align:start position:0% solidity and part of the idea of having a<00:20:23.039> debugging<00:20:23.369> the<00:20:23.519> apartment<00:20:23.940> is<00:20:24.450> to<00:20:25.200> help 00:20:25.759 --> 00:20:25.769 align:start position:0% a debugging the apartment is to help 00:20:25.769 --> 00:20:27.169 align:start position:0% a debugging the apartment is to help provide<00:20:26.129> that<00:20:26.159> decoupling<00:20:26.789> right<00:20:26.970> because 00:20:27.169 --> 00:20:27.179 align:start position:0% provide that decoupling right because 00:20:27.179 --> 00:20:29.629 align:start position:0% provide that decoupling right because right<00:20:27.359> now<00:20:27.479> our<00:20:27.509> debugger<00:20:27.989> is<00:20:28.639> specifically 00:20:29.629 --> 00:20:29.639 align:start position:0% right now our debugger is specifically 00:20:29.639 --> 00:20:31.489 align:start position:0% right now our debugger is specifically at<00:20:29.729> the<00:20:29.849> solidity<00:20:30.599> to<00:20:30.720> Dugger<00:20:31.019> it<00:20:31.169> relies 00:20:31.489 --> 00:20:31.499 align:start position:0% at the solidity to Dugger it relies 00:20:31.499 --> 00:20:32.989 align:start position:0% at the solidity to Dugger it relies heavily<00:20:31.529> on<00:20:31.950> specific<00:20:32.549> knowledge<00:20:32.700> about 00:20:32.989 --> 00:20:32.999 align:start position:0% heavily on specific knowledge about 00:20:32.999 --> 00:20:34.549 align:start position:0% heavily on specific knowledge about slitted<00:20:33.479> we're<00:20:33.720> hoping<00:20:33.869> that<00:20:34.019> with<00:20:34.349> a 00:20:34.549 --> 00:20:34.559 align:start position:0% slitted we're hoping that with a 00:20:34.559 --> 00:20:37.039 align:start position:0% slitted we're hoping that with a debugging<00:20:35.099> data<00:20:35.369> format<00:20:35.789> the<00:20:36.330> whatever 00:20:37.039 --> 00:20:37.049 align:start position:0% debugging data format the whatever 00:20:37.049 --> 00:20:38.749 align:start position:0% debugging data format the whatever compiler<00:20:37.679> could<00:20:37.950> provide<00:20:38.340> a<00:20:38.399> lot<00:20:38.729> of 00:20:38.749 --> 00:20:38.759 align:start position:0% compiler could provide a lot of 00:20:38.759 --> 00:20:42.560 align:start position:0% compiler could provide a lot of disinformation<00:20:39.179> in<00:20:39.599> the<00:20:39.749> format<00:20:40.109> I<00:20:41.179> mean<00:20:42.179> as<00:20:42.419> I 00:20:42.560 --> 00:20:42.570 align:start position:0% disinformation in the format I mean as I 00:20:42.570 --> 00:20:45.169 align:start position:0% disinformation in the format I mean as I mentioned<00:20:42.929> you<00:20:43.019> know<00:20:43.049> I<00:20:43.379> talked<00:20:44.009> a<00:20:44.099> lot<00:20:44.249> in<00:20:44.549> the 00:20:45.169 --> 00:20:45.179 align:start position:0% mentioned you know I talked a lot in the 00:20:45.179 --> 00:20:47.749 align:start position:0% mentioned you know I talked a lot in the other<00:20:45.809> slide<00:20:46.049> about<00:20:46.470> solidity<00:20:47.159> specific 00:20:47.749 --> 00:20:47.759 align:start position:0% other slide about solidity specific 00:20:47.759 --> 00:20:49.629 align:start position:0% other slide about solidity specific challenges<00:20:48.179> but<00:20:48.359> you<00:20:48.419> know<00:20:48.599> the<00:20:48.779> idea<00:20:48.809> is<00:20:49.080> that 00:20:49.629 --> 00:20:49.639 align:start position:0% challenges but you know the idea is that 00:20:49.639 --> 00:20:51.769 align:start position:0% challenges but you know the idea is that any<00:20:50.639> challenge<00:20:51.149> we<00:20:51.239> have<00:20:51.359> to<00:20:51.389> solve<00:20:51.659> for 00:20:51.769 --> 00:20:51.779 align:start position:0% any challenge we have to solve for 00:20:51.779 --> 00:20:55.009 align:start position:0% any challenge we have to solve for solidity<00:20:52.259> is<00:20:52.499> at<00:20:53.009> the<00:20:53.159> very<00:20:53.429> least<00:20:53.669> a<00:20:54.019> they 00:20:55.009 --> 00:20:55.019 align:start position:0% solidity is at the very least a they 00:20:55.019 --> 00:20:56.299 align:start position:0% solidity is at the very least a they probably<00:20:55.289> have<00:20:55.499> to<00:20:55.559> salt<00:20:55.739> lick<00:20:55.859> the<00:20:55.950> problem 00:20:56.299 --> 00:20:56.309 align:start position:0% probably have to salt lick the problem 00:20:56.309 --> 00:20:59.479 align:start position:0% probably have to salt lick the problem is<00:20:56.429> at<00:20:56.700> least<00:20:57.149> this<00:20:57.479> hard<00:20:57.950> right<00:20:58.950> I'm<00:20:59.309> not 00:20:59.479 --> 00:20:59.489 align:start position:0% is at least this hard right I'm not 00:20:59.489 --> 00:21:01.369 align:start position:0% is at least this hard right I'm not trying<00:21:00.059> to<00:21:00.119> exclude<00:21:00.509> other<00:21:00.779> things<00:21:01.019> I'm<00:21:01.169> just 00:21:01.369 --> 00:21:01.379 align:start position:0% trying to exclude other things I'm just 00:21:01.379 --> 00:21:05.029 align:start position:0% trying to exclude other things I'm just trying<00:21:01.649> to<00:21:02.149> list<00:21:03.149> like<00:21:03.379> the<00:21:04.379> problem<00:21:04.769> is<00:21:04.919> at 00:21:05.029 --> 00:21:05.039 align:start position:0% trying to list like the problem is at 00:21:05.039 --> 00:21:09.379 align:start position:0% trying to list like the problem is at least<00:21:05.249> this<00:21:05.519> hard<00:21:06.679> yeah<00:21:07.739> to<00:21:08.279> your<00:21:08.399> point<00:21:08.729> you 00:21:09.379 --> 00:21:09.389 align:start position:0% least this hard yeah to your point you 00:21:09.389 --> 00:21:11.899 align:start position:0% least this hard yeah to your point you can<00:21:09.539> look<00:21:09.690> at<00:21:09.809> this<00:21:10.340> you<00:21:11.340> can<00:21:11.369> declare<00:21:11.700> these 00:21:11.899 --> 00:21:11.909 align:start position:0% can look at this you can declare these 00:21:11.909 --> 00:21:13.399 align:start position:0% can look at this you can declare these base<00:21:12.119> types<00:21:12.389> and<00:21:12.509> this<00:21:12.570> F<00:21:12.720> work<00:21:12.929> works<00:21:13.139> work 00:21:13.399 --> 00:21:13.409 align:start position:0% base types and this F work works work 00:21:13.409 --> 00:21:14.899 align:start position:0% base types and this F work works work works<00:21:13.649> on<00:21:13.799> any<00:21:13.950> language<00:21:14.279> you<00:21:14.309> you<00:21:14.729> need<00:21:14.849> a 00:21:14.899 --> 00:21:14.909 align:start position:0% works on any language you you need a 00:21:14.909 --> 00:21:17.119 align:start position:0% works on any language you you need a pork<00:21:15.330> output<00:21:15.690> on<00:21:15.809> the<00:21:15.929> scene<00:21:16.200> import<00:21:16.769> help<00:21:16.950> it 00:21:17.119 --> 00:21:17.129 align:start position:0% pork output on the scene import help it 00:21:17.129 --> 00:21:21.169 align:start position:0% pork output on the scene import help it on<00:21:17.249> Pascal<00:21:17.789> and<00:21:18.359> so<00:21:19.289> on<00:21:19.440> and<00:21:19.799> it<00:21:20.639> kind<00:21:20.789> of<00:21:20.940> Rises 00:21:21.169 --> 00:21:21.179 align:start position:0% on Pascal and so on and it kind of Rises 00:21:21.179 --> 00:21:22.909 align:start position:0% on Pascal and so on and it kind of Rises these<00:21:21.269> mechanisms<00:21:21.690> where<00:21:22.049> you<00:21:22.470> can<00:21:22.649> specify 00:21:22.909 --> 00:21:22.919 align:start position:0% these mechanisms where you can specify 00:21:22.919 --> 00:21:26.330 align:start position:0% these mechanisms where you can specify that<00:21:23.220> an<00:21:23.549> int<00:21:23.849> is<00:21:24.389> sized<00:21:24.690> for<00:21:24.989> four<00:21:25.349> bytes<00:21:25.529> but 00:21:26.330 --> 00:21:26.340 align:start position:0% that an int is sized for four bytes but 00:21:26.340 --> 00:21:27.769 align:start position:0% that an int is sized for four bytes but you<00:21:26.460> know<00:21:26.549> on<00:21:26.669> another<00:21:26.759> platform<00:21:27.210> or<00:21:27.659> on 00:21:27.769 --> 00:21:27.779 align:start position:0% you know on another platform or on 00:21:27.779 --> 00:21:28.940 align:start position:0% you know on another platform or on another<00:21:27.840> language<00:21:28.379> you<00:21:28.499> might<00:21:28.619> have<00:21:28.769> eight 00:21:28.940 --> 00:21:28.950 align:start position:0% another language you might have eight 00:21:28.950 --> 00:21:32.779 align:start position:0% another language you might have eight byte<00:21:29.159> integers<00:21:30.109> so<00:21:31.129> the<00:21:32.129> dwarf<00:21:32.429> provides 00:21:32.779 --> 00:21:32.789 align:start position:0% byte integers so the dwarf provides 00:21:32.789 --> 00:21:36.109 align:start position:0% byte integers so the dwarf provides mechanisms<00:21:32.999> for<00:21:33.450> doing<00:21:33.570> this<00:21:33.840> but<00:21:34.759> it<00:21:35.759> doesn't 00:21:36.109 --> 00:21:36.119 align:start position:0% mechanisms for doing this but it doesn't 00:21:36.119 --> 00:21:39.320 align:start position:0% mechanisms for doing this but it doesn't get<00:21:36.239> as<00:21:36.359> complicated<00:21:36.749> as<00:21:37.139> say<00:21:38.330> salinity 00:21:39.320 --> 00:21:39.330 align:start position:0% get as complicated as say salinity 00:21:39.330 --> 00:21:41.749 align:start position:0% get as complicated as say salinity storage<00:21:39.869> arrays<00:21:40.440> versus<00:21:41.039> solidity<00:21:41.399> memory 00:21:41.749 --> 00:21:41.759 align:start position:0% storage arrays versus solidity memory 00:21:41.759 --> 00:21:45.729 align:start position:0% storage arrays versus solidity memory array<00:21:42.090> is<00:21:42.299> like<00:21:43.109> structs<00:21:43.679> insulin<00:21:44.340> via<00:21:44.549> memory 00:21:45.729 --> 00:21:45.739 align:start position:0% array is like structs insulin via memory 00:21:45.739 --> 00:21:48.349 align:start position:0% array is like structs insulin via memory which<00:21:46.739> one<00:21:46.919> ones<00:21:47.309> tightly<00:21:47.729> packed<00:21:47.970> ones<00:21:48.210> not 00:21:48.349 --> 00:21:48.359 align:start position:0% which one ones tightly packed ones not 00:21:48.359 --> 00:21:49.879 align:start position:0% which one ones tightly packed ones not coming<00:21:48.659> back<00:21:48.779> to<00:21:48.929> store<00:21:49.109> integers<00:21:49.289> Oh 00:21:49.879 --> 00:21:49.889 align:start position:0% coming back to store integers Oh 00:21:49.889 --> 00:21:51.529 align:start position:0% coming back to store integers Oh storage<00:21:50.460> is<00:21:50.580> tightly<00:21:50.789> packed<00:21:51.090> it's<00:21:51.389> the 00:21:51.529 --> 00:21:51.539 align:start position:0% storage is tightly packed it's the 00:21:51.539 --> 00:21:52.730 align:start position:0% storage is tightly packed it's the storage<00:21:51.779> arrays<00:21:52.139> are<00:21:52.289> typed 00:21:52.730 --> 00:21:52.740 align:start position:0% storage arrays are typed 00:21:52.740 --> 00:21:54.529 align:start position:0% storage arrays are typed the<00:21:52.950> memory<00:21:53.250> erase<00:21:53.490> are<00:21:53.820> not<00:21:53.970> tightly<00:21:54.240> packed 00:21:54.529 --> 00:21:54.539 align:start position:0% the memory erase are not tightly packed 00:21:54.539 --> 00:21:57.110 align:start position:0% the memory erase are not tightly packed and<00:21:54.779> so<00:21:54.870> how<00:21:54.960> do<00:21:55.020> you<00:21:55.080> represent<00:21:55.500> that<00:21:56.120> with 00:21:57.110 --> 00:21:57.120 align:start position:0% and so how do you represent that with 00:21:57.120 --> 00:21:59.539 align:start position:0% and so how do you represent that with something<00:21:57.450> like<00:21:57.570> this<00:21:58.130> perhaps<00:21:59.130> it<00:21:59.460> is 00:21:59.539 --> 00:21:59.549 align:start position:0% something like this perhaps it is 00:21:59.549 --> 00:22:02.360 align:start position:0% something like this perhaps it is unclear<00:21:59.909> I<00:22:00.149> mean<00:22:00.390> that's<00:22:00.570> not<00:22:00.779> even<00:22:01.220> not<00:22:02.220> maybe 00:22:02.360 --> 00:22:02.370 align:start position:0% unclear I mean that's not even not maybe 00:22:02.370 --> 00:22:04.940 align:start position:0% unclear I mean that's not even not maybe even<00:22:02.610> cook<00:22:02.820> say<00:22:03.450> that<00:22:03.630> I'm<00:22:04.470> not<00:22:04.620> sure<00:22:04.710> I'd 00:22:04.940 --> 00:22:04.950 align:start position:0% even cook say that I'm not sure I'd 00:22:04.950 --> 00:22:06.769 align:start position:0% even cook say that I'm not sure I'd here's<00:22:05.820> an<00:22:05.940> it<00:22:06.029> here's<00:22:06.210> a<00:22:06.270> question<00:22:06.450> for<00:22:06.720> you 00:22:06.769 --> 00:22:06.779 align:start position:0% here's an it here's a question for you 00:22:06.779 --> 00:22:08.180 align:start position:0% here's an it here's a question for you is<00:22:07.020> do<00:22:07.110> you<00:22:07.169> represent<00:22:07.320> that<00:22:07.679> is<00:22:07.799> a<00:22:07.830> property 00:22:08.180 --> 00:22:08.190 align:start position:0% is do you represent that is a property 00:22:08.190 --> 00:22:09.680 align:start position:0% is do you represent that is a property of<00:22:08.279> her<00:22:08.399> upper<00:22:08.700> race<00:22:08.880> I<00:22:09.149> probably<00:22:09.450> would<00:22:09.659> have 00:22:09.680 --> 00:22:09.690 align:start position:0% of her upper race I probably would have 00:22:09.690 --> 00:22:11.360 align:start position:0% of her upper race I probably would have represented<00:22:10.380> it<00:22:10.440> as<00:22:10.559> a<00:22:10.620> property<00:22:11.010> of<00:22:11.100> the 00:22:11.360 --> 00:22:11.370 align:start position:0% represented it as a property of the 00:22:11.370 --> 00:22:15.470 align:start position:0% represented it as a property of the underlying<00:22:12.120> types<00:22:13.909> like<00:22:14.909> I<00:22:15.029> probably<00:22:15.270> would 00:22:15.470 --> 00:22:15.480 align:start position:0% underlying types like I probably would 00:22:15.480 --> 00:22:18.590 align:start position:0% underlying types like I probably would have<00:22:15.510> said<00:22:15.690> oh<00:22:15.840> yeah<00:22:16.110> and<00:22:16.320> in<00:22:16.590> memory<00:22:17.520> if<00:22:18.240> Dade 00:22:18.590 --> 00:22:18.600 align:start position:0% have said oh yeah and in memory if Dade 00:22:18.600 --> 00:22:20.510 align:start position:0% have said oh yeah and in memory if Dade is<00:22:18.630> 32<00:22:19.289> bytes<00:22:19.500> even<00:22:19.919> though<00:22:20.010> it's<00:22:20.159> called<00:22:20.309> an 00:22:20.510 --> 00:22:20.520 align:start position:0% is 32 bytes even though it's called an 00:22:20.520 --> 00:22:22.460 align:start position:0% is 32 bytes even though it's called an end<00:22:20.669> date<00:22:20.789> and<00:22:21.029> in<00:22:21.270> storage<00:22:21.750> means<00:22:21.990> B<00:22:22.169> is<00:22:22.200> 8 00:22:22.460 --> 00:22:22.470 align:start position:0% end date and in storage means B is 8 00:22:22.470 --> 00:22:25.940 align:start position:0% end date and in storage means B is 8 bytes<00:22:22.679> but<00:22:23.039> you<00:22:23.159> know<00:22:23.309> both<00:22:23.789> those<00:22:24.000> are<00:22:24.950> viable 00:22:25.940 --> 00:22:25.950 align:start position:0% bytes but you know both those are viable 00:22:25.950 --> 00:22:28.220 align:start position:0% bytes but you know both those are viable representations<00:22:26.940> so<00:22:27.240> you<00:22:27.870> need<00:22:27.990> to<00:22:28.080> figure 00:22:28.220 --> 00:22:28.230 align:start position:0% representations so you need to figure 00:22:28.230 --> 00:22:29.450 align:start position:0% representations so you need to figure out<00:22:28.350> which<00:22:28.529> one<00:22:28.740> to<00:22:28.860> go<00:22:28.950> with<00:22:28.980> because<00:22:29.279> there's 00:22:29.450 --> 00:22:29.460 align:start position:0% out which one to go with because there's 00:22:29.460 --> 00:22:31.549 align:start position:0% out which one to go with because there's other<00:22:29.640> differences<00:22:30.270> between<00:22:30.450> memory<00:22:31.289> erase 00:22:31.549 --> 00:22:31.559 align:start position:0% other differences between memory erase 00:22:31.559 --> 00:22:33.710 align:start position:0% other differences between memory erase and<00:22:31.770> storage<00:22:32.070> array<00:22:32.309> it's<00:22:32.490> like<00:22:32.669> I<00:22:33.120> mean<00:22:33.539> I'd 00:22:33.710 --> 00:22:33.720 align:start position:0% and storage array it's like I mean I'd 00:22:33.720 --> 00:22:34.880 align:start position:0% and storage array it's like I mean I'd say<00:22:33.750> the<00:22:33.990> bigger<00:22:34.200> difference<00:22:34.350> is<00:22:34.620> how<00:22:34.740> they 00:22:34.880 --> 00:22:34.890 align:start position:0% say the bigger difference is how they 00:22:34.890 --> 00:22:40.419 align:start position:0% say the bigger difference is how they handle<00:22:35.159> reference<00:22:35.549> types<00:22:35.730> but<00:22:38.090> neat<00:22:39.090> stuff 00:22:40.419 --> 00:22:40.429 align:start position:0% handle reference types but neat stuff 00:22:40.429 --> 00:22:44.169 align:start position:0% handle reference types but neat stuff all<00:22:41.429> right<00:22:41.580> so<00:22:42.230> there's<00:22:43.230> some<00:22:43.409> links<00:22:43.740> for<00:22:43.799> you 00:22:44.169 --> 00:22:44.179 align:start position:0% all right so there's some links for you 00:22:44.179 --> 00:22:47.389 align:start position:0% all right so there's some links for you how<00:22:45.179> you<00:22:45.240> wrote<00:22:45.480> a<00:22:45.510> paper<00:22:45.750> that<00:22:46.220> documents<00:22:47.220> all 00:22:47.389 --> 00:22:47.399 align:start position:0% how you wrote a paper that documents all 00:22:47.399 --> 00:22:50.630 align:start position:0% how you wrote a paper that documents all of<00:22:47.720> salinities<00:22:48.750> data<00:22:49.230> representation<00:22:50.039> yeah<00:22:50.610> I 00:22:50.630 --> 00:22:50.640 align:start position:0% of salinities data representation yeah I 00:22:50.640 --> 00:22:52.340 align:start position:0% of salinities data representation yeah I mean<00:22:50.850> those<00:22:51.000> of<00:22:51.179> you<00:22:51.270> who<00:22:51.450> work<00:22:51.809> on<00:22:51.960> solidity 00:22:52.340 --> 00:22:52.350 align:start position:0% mean those of you who work on solidity 00:22:52.350 --> 00:22:56.029 align:start position:0% mean those of you who work on solidity I'm<00:22:52.529> just<00:22:53.600> recapitulating<00:22:54.600> all<00:22:54.809> the<00:22:54.960> work<00:22:55.830> you 00:22:56.029 --> 00:22:56.039 align:start position:0% I'm just recapitulating all the work you 00:22:56.039 --> 00:22:58.610 align:start position:0% I'm just recapitulating all the work you did<00:22:56.220> and<00:22:56.659> putting<00:22:57.659> it<00:22:57.779> in<00:22:57.870> a<00:22:57.990> form<00:22:58.289> that<00:22:58.320> I<00:22:58.470> hope 00:22:58.610 --> 00:22:58.620 align:start position:0% did and putting it in a form that I hope 00:22:58.620 --> 00:23:04.549 align:start position:0% did and putting it in a form that I hope is<00:22:58.740> readable<00:22:59.039> but<00:22:59.429> up<00:22:59.840> as<00:23:00.840> tables<00:23:03.440> here<00:23:04.440> my 00:23:04.549 --> 00:23:04.559 align:start position:0% is readable but up as tables here my 00:23:04.559 --> 00:23:09.110 align:start position:0% is readable but up as tables here my tables<00:23:06.080> they<00:23:07.080> are<00:23:07.230> so<00:23:08.130> truffle<00:23:08.760> is<00:23:08.850> about<00:23:09.029> to 00:23:09.110 --> 00:23:09.120 align:start position:0% tables they are so truffle is about to 00:23:09.120 --> 00:23:11.210 align:start position:0% tables they are so truffle is about to release<00:23:09.360> a<00:23:09.720> library<00:23:10.409> called<00:23:10.620> truffle<00:23:10.919> Kodak 00:23:11.210 --> 00:23:11.220 align:start position:0% release a library called truffle Kodak 00:23:11.220 --> 00:23:13.669 align:start position:0% release a library called truffle Kodak which<00:23:11.429> handles<00:23:11.909> any<00:23:12.090> coding<00:23:12.419> and<00:23:12.539> decoding<00:23:12.679> of 00:23:13.669 --> 00:23:13.679 align:start position:0% which handles any coding and decoding of 00:23:13.679 --> 00:23:16.820 align:start position:0% which handles any coding and decoding of values<00:23:14.630> not<00:23:15.630> only<00:23:15.690> solidity<00:23:16.260> values<00:23:16.620> but<00:23:16.740> also 00:23:16.820 --> 00:23:16.830 align:start position:0% values not only solidity values but also 00:23:16.830 --> 00:23:21.169 align:start position:0% values not only solidity values but also API<00:23:17.250> values<00:23:18.289> and<00:23:19.289> you<00:23:20.100> can<00:23:20.250> see<00:23:20.490> and<00:23:21.000> we'll 00:23:21.169 --> 00:23:21.179 align:start position:0% API values and you can see and we'll 00:23:21.179 --> 00:23:23.750 align:start position:0% API values and you can see and we'll just<00:23:21.330> kind<00:23:22.320> of<00:23:22.409> show<00:23:22.529> you<00:23:22.559> what<00:23:22.649> dealing<00:23:23.640> with 00:23:23.750 --> 00:23:23.760 align:start position:0% just kind of show you what dealing with 00:23:23.760 --> 00:23:25.610 align:start position:0% just kind of show you what dealing with we<00:23:23.909> have<00:23:24.059> this<00:23:24.210> representation<00:23:25.020> of<00:23:25.409> all 00:23:25.610 --> 00:23:25.620 align:start position:0% we have this representation of all 00:23:25.620 --> 00:23:27.560 align:start position:0% we have this representation of all values<00:23:26.190> in<00:23:26.220> solidity<00:23:26.880> this<00:23:27.179> is<00:23:27.299> the<00:23:27.419> output 00:23:27.560 --> 00:23:27.570 align:start position:0% values in solidity this is the output 00:23:27.570 --> 00:23:29.810 align:start position:0% values in solidity this is the output format<00:23:28.020> that<00:23:28.770> Trump<00:23:29.250> Lakota<00:23:29.520> will<00:23:29.730> be 00:23:29.810 --> 00:23:29.820 align:start position:0% format that Trump Lakota will be 00:23:29.820 --> 00:23:31.669 align:start position:0% format that Trump Lakota will be providing<00:23:30.360> and<00:23:30.899> these<00:23:31.020> are<00:23:31.140> JavaScript 00:23:31.669 --> 00:23:31.679 align:start position:0% providing and these are JavaScript 00:23:31.679 --> 00:23:33.440 align:start position:0% providing and these are JavaScript objects<00:23:32.070> and<00:23:32.190> you<00:23:32.250> can<00:23:32.399> see<00:23:32.610> we<00:23:32.789> model<00:23:33.330> the 00:23:33.440 --> 00:23:33.450 align:start position:0% objects and you can see we model the 00:23:33.450 --> 00:23:37.970 align:start position:0% objects and you can see we model the types<00:23:34.190> so<00:23:35.190> each<00:23:35.610> result<00:23:36.539> will<00:23:37.470> have<00:23:37.649> a<00:23:37.679> type 00:23:37.970 --> 00:23:37.980 align:start position:0% types so each result will have a type 00:23:37.980 --> 00:23:40.730 align:start position:0% types so each result will have a type field<00:23:38.309> in<00:23:38.490> a<00:23:38.580> value<00:23:38.909> field<00:23:39.210> and<00:23:39.570> the<00:23:40.559> type 00:23:40.730 --> 00:23:40.740 align:start position:0% field in a value field and the type 00:23:40.740 --> 00:23:43.940 align:start position:0% field in a value field and the type field<00:23:40.980> represents<00:23:41.820> one<00:23:41.909> of<00:23:42.000> these<00:23:42.830> you<00:23:43.830> know 00:23:43.940 --> 00:23:43.950 align:start position:0% field represents one of these you know 00:23:43.950 --> 00:23:46.970 align:start position:0% field represents one of these you know generally<00:23:44.490> tight<00:23:45.110> yeah<00:23:46.110> I<00:23:46.440> should<00:23:46.860> know<00:23:46.950> that 00:23:46.970 --> 00:23:46.980 align:start position:0% generally tight yeah I should know that 00:23:46.980 --> 00:23:49.010 align:start position:0% generally tight yeah I should know that this<00:23:47.279> is<00:23:47.460> very<00:23:47.730> that<00:23:48.240> this<00:23:48.419> Park 00:23:49.010 --> 00:23:49.020 align:start position:0% this is very that this Park 00:23:49.020 --> 00:23:51.140 align:start position:0% this is very that this Park thing<00:23:49.260> is<00:23:49.440> very<00:23:49.650> salinity<00:23:50.160> specific<00:23:50.640> but<00:23:50.850> so 00:23:51.140 --> 00:23:51.150 align:start position:0% thing is very salinity specific but so 00:23:51.150 --> 00:23:53.570 align:start position:0% thing is very salinity specific but so so<00:23:51.390> don't<00:23:52.050> look<00:23:52.680> to<00:23:52.920> this<00:23:53.070> too<00:23:53.400> much 00:23:53.570 --> 00:23:53.580 align:start position:0% so don't look to this too much 00:23:53.580 --> 00:23:55.340 align:start position:0% so don't look to this too much necessarily<00:23:54.300> for<00:23:54.480> the<00:23:54.570> debugging<00:23:54.870> data<00:23:55.080> part 00:23:55.340 --> 00:23:55.350 align:start position:0% necessarily for the debugging data part 00:23:55.350 --> 00:23:56.780 align:start position:0% necessarily for the debugging data part because<00:23:55.620> that<00:23:55.650> we<00:23:55.950> really<00:23:56.250> do<00:23:56.430> want<00:23:56.640> to<00:23:56.730> be 00:23:56.780 --> 00:23:56.790 align:start position:0% because that we really do want to be 00:23:56.790 --> 00:23:59.720 align:start position:0% because that we really do want to be more<00:23:57.210> tenable<00:23:57.650> right<00:23:58.650> but<00:23:58.860> this<00:23:59.130> is<00:23:59.310> a<00:23:59.340> start 00:23:59.720 --> 00:23:59.730 align:start position:0% more tenable right but this is a start 00:23:59.730 --> 00:24:00.110 align:start position:0% more tenable right but this is a start right 00:24:00.110 --> 00:24:00.120 align:start position:0% right 00:24:00.120 --> 00:24:03.380 align:start position:0% right because<00:24:00.480> you<00:24:00.960> can<00:24:01.110> say<00:24:01.790> we<00:24:02.790> have<00:24:02.940> a<00:24:02.970> struct 00:24:03.380 --> 00:24:03.390 align:start position:0% because you can say we have a struct 00:24:03.390 --> 00:24:08.300 align:start position:0% because you can say we have a struct type<00:24:03.710> well<00:24:04.710> let's<00:24:04.920> just<00:24:05.130> do<00:24:06.530> like<00:24:07.530> a<00:24:07.650> dynamic 00:24:08.300 --> 00:24:08.310 align:start position:0% type well let's just do like a dynamic 00:24:08.310 --> 00:24:11.450 align:start position:0% type well let's just do like a dynamic array<00:24:08.480> right<00:24:09.650> dynamic<00:24:10.650> array<00:24:10.890> has<00:24:11.160> a<00:24:11.190> base 00:24:11.450 --> 00:24:11.460 align:start position:0% array right dynamic array has a base 00:24:11.460 --> 00:24:13.100 align:start position:0% array right dynamic array has a base type<00:24:11.790> which<00:24:11.970> is<00:24:12.090> another<00:24:12.330> type<00:24:12.600> so<00:24:12.840> that<00:24:12.870> might 00:24:13.100 --> 00:24:13.110 align:start position:0% type which is another type so that might 00:24:13.110 --> 00:24:16.550 align:start position:0% type which is another type so that might be<00:24:13.200> an<00:24:13.290> integer<00:24:13.500> and<00:24:15.050> it<00:24:16.050> has<00:24:16.170> a<00:24:16.200> location 00:24:16.550 --> 00:24:16.560 align:start position:0% be an integer and it has a location 00:24:16.560 --> 00:24:18.740 align:start position:0% be an integer and it has a location which<00:24:16.980> might<00:24:17.160> be<00:24:17.340> a<00:24:17.370> memory<00:24:17.790> storage<00:24:18.060> called 00:24:18.740 --> 00:24:18.750 align:start position:0% which might be a memory storage called 00:24:18.750 --> 00:24:20.990 align:start position:0% which might be a memory storage called it<00:24:18.930> out<00:24:19.080> of<00:24:19.200> the<00:24:19.320> staff<00:24:19.730> that's<00:24:20.730> a<00:24:20.820> raised 00:24:20.990 --> 00:24:21.000 align:start position:0% it out of the staff that's a raised 00:24:21.000 --> 00:24:24.590 align:start position:0% it out of the staff that's a raised again<00:24:21.300> no<00:24:21.800> constant<00:24:22.800> but<00:24:23.730> yeah<00:24:23.850> so<00:24:24.120> those<00:24:24.450> are 00:24:24.590 --> 00:24:24.600 align:start position:0% again no constant but yeah so those are 00:24:24.600 --> 00:24:27.950 align:start position:0% again no constant but yeah so those are types<00:24:24.810> and<00:24:25.020> then<00:24:25.110> we<00:24:25.200> also<00:24:25.350> have<00:24:25.680> values<00:24:26.960> which 00:24:27.950 --> 00:24:27.960 align:start position:0% types and then we also have values which 00:24:27.960 --> 00:24:29.990 align:start position:0% types and then we also have values which represent<00:24:28.440> the<00:24:28.470> corresponding<00:24:29.010> value<00:24:29.280> so<00:24:29.520> you 00:24:29.990 --> 00:24:30.000 align:start position:0% represent the corresponding value so you 00:24:30.000 --> 00:24:32.090 align:start position:0% represent the corresponding value so you know<00:24:30.120> a<00:24:30.270> pair<00:24:30.510> of<00:24:30.540> tightened<00:24:31.320> value<00:24:31.620> gives<00:24:31.920> you 00:24:32.090 --> 00:24:32.100 align:start position:0% know a pair of tightened value gives you 00:24:32.100 --> 00:24:35.480 align:start position:0% know a pair of tightened value gives you a<00:24:32.400> representation<00:24:33.210> of<00:24:33.600> your<00:24:34.050> source<00:24:34.590> variable 00:24:35.480 --> 00:24:35.490 align:start position:0% a representation of your source variable 00:24:35.490 --> 00:24:38.930 align:start position:0% a representation of your source variable or<00:24:35.610> whatever<00:24:35.940> they<00:24:36.090> trying<00:24:36.360> to<00:24:36.390> decode<00:24:37.940> so 00:24:38.930 --> 00:24:38.940 align:start position:0% or whatever they trying to decode so 00:24:38.940 --> 00:24:42.650 align:start position:0% or whatever they trying to decode so maybe<00:24:39.800> the<00:24:40.800> at<00:24:41.400> least<00:24:41.550> something<00:24:41.910> our<00:24:42.060> hope<00:24:42.360> is 00:24:42.650 --> 00:24:42.660 align:start position:0% maybe the at least something our hope is 00:24:42.660 --> 00:24:44.990 align:start position:0% maybe the at least something our hope is that<00:24:43.260> this<00:24:43.920> kind<00:24:44.130> of<00:24:44.220> approach<00:24:44.550> will<00:24:44.850> lend 00:24:44.990 --> 00:24:45.000 align:start position:0% that this kind of approach will lend 00:24:45.000 --> 00:24:49.170 align:start position:0% that this kind of approach will lend itself<00:24:45.300> to<00:24:45.570> a<00:24:46.020> more<00:24:46.200> general<00:24:46.350> solution 00:24:49.170 --> 00:24:49.180 align:start position:0% 00:24:49.180 --> 00:24:51.090 align:start position:0% currently<00:24:49.930> this<00:24:50.110> is<00:24:50.230> not<00:24:50.380> serializable 00:24:51.090 --> 00:24:51.100 align:start position:0% currently this is not serializable 00:24:51.100 --> 00:24:54.840 align:start position:0% currently this is not serializable because<00:24:51.490> data<00:24:53.220> values<00:24:54.220> this<00:24:54.370> limine<00:24:54.670> can<00:24:54.790> be 00:24:54.840 --> 00:24:54.850 align:start position:0% because data values this limine can be 00:24:54.850 --> 00:24:56.490 align:start position:0% because data values this limine can be circular<00:24:55.360> and<00:24:55.540> we<00:24:55.690> can't<00:24:55.870> really<00:24:55.960> serialize 00:24:56.490 --> 00:24:56.500 align:start position:0% circular and we can't really serialize 00:24:56.500 --> 00:25:00.450 align:start position:0% circular and we can't really serialize them<00:24:56.680> to<00:24:56.890> json<00:24:57.250> very<00:24:57.460> easily<00:24:58.290> so<00:24:59.290> the<00:25:00.280> more 00:25:00.450 --> 00:25:00.460 align:start position:0% them to json very easily so the more 00:25:00.460 --> 00:25:02.520 align:start position:0% them to json very easily so the more work<00:25:00.610> you<00:25:00.760> done<00:25:00.970> for<00:25:01.150> Shore 00:25:02.520 --> 00:25:02.530 align:start position:0% work you done for Shore 00:25:02.530 --> 00:25:04.200 align:start position:0% work you done for Shore and<00:25:02.950> then<00:25:03.040> of<00:25:03.190> course<00:25:03.220> shout<00:25:03.670> out<00:25:03.820> to<00:25:04.030> these 00:25:04.200 --> 00:25:04.210 align:start position:0% and then of course shout out to these 00:25:04.210 --> 00:25:10.830 align:start position:0% and then of course shout out to these soliciting<00:25:04.840> dogs<00:25:05.550> for<00:25:06.550> being<00:25:06.700> excellent 00:25:10.830 --> 00:25:10.840 align:start position:0% 00:25:10.840 --> 00:25:13.110 align:start position:0% oh<00:25:10.870> wait<00:25:11.740> am<00:25:11.860> i<00:25:11.920> all<00:25:12.430> right<00:25:12.460> anyway<00:25:12.850> that's<00:25:13.000> not 00:25:13.110 --> 00:25:13.120 align:start position:0% oh wait am i all right anyway that's not 00:25:13.120 --> 00:25:15.210 align:start position:0% oh wait am i all right anyway that's not that's<00:25:13.480> not<00:25:13.600> relevant<00:25:13.900> circuit<00:25:14.710> circular 00:25:15.210 --> 00:25:15.220 align:start position:0% that's not relevant circuit circular 00:25:15.220 --> 00:25:16.980 align:start position:0% that's not relevant circuit circular stuff<00:25:15.430> is<00:25:15.610> not<00:25:16.060> particularly<00:25:16.780> relevant 00:25:16.980 --> 00:25:16.990 align:start position:0% stuff is not particularly relevant 00:25:16.990 --> 00:25:21.260 align:start position:0% stuff is not particularly relevant particularly<00:25:17.650> relevant<00:25:18.130> right<00:25:18.430> now<00:25:18.520> we<00:25:18.580> have 00:25:21.260 --> 00:25:21.270 align:start position:0% 00:25:21.270 --> 00:25:25.680 align:start position:0% all<00:25:22.270> right<00:25:22.570> so<00:25:23.440> I<00:25:23.880> hope<00:25:24.880> yours<00:25:25.240> we<00:25:25.420> could<00:25:25.540> break 00:25:25.680 --> 00:25:25.690 align:start position:0% all right so I hope yours we could break 00:25:25.690 --> 00:25:27.000 align:start position:0% all right so I hope yours we could break into<00:25:25.870> groups<00:25:25.960> and<00:25:26.350> kind<00:25:26.650> of<00:25:26.680> talk<00:25:26.830> about<00:25:26.920> a 00:25:27.000 --> 00:25:27.010 align:start position:0% into groups and kind of talk about a 00:25:27.010 --> 00:25:28.500 align:start position:0% into groups and kind of talk about a high-level<00:25:27.310> structure<00:25:27.850> like<00:25:28.030> what<00:25:28.210> might 00:25:28.500 --> 00:25:28.510 align:start position:0% high-level structure like what might 00:25:28.510 --> 00:25:31.650 align:start position:0% high-level structure like what might this<00:25:28.660> look<00:25:28.720> like<00:25:29.730> give<00:25:30.730> us<00:25:30.850> 20<00:25:31.240> minutes<00:25:31.270> for 00:25:31.650 --> 00:25:31.660 align:start position:0% this look like give us 20 minutes for 00:25:31.660 --> 00:25:34.230 align:start position:0% this look like give us 20 minutes for that<00:25:31.870> unless<00:25:32.290> everyone<00:25:32.620> is<00:25:32.650> bored<00:25:33.210> you<00:25:34.210> know 00:25:34.230 --> 00:25:34.240 align:start position:0% that unless everyone is bored you know 00:25:34.240 --> 00:25:37.920 align:start position:0% that unless everyone is bored you know come<00:25:34.570> here<00:25:34.720> with<00:25:34.870> dwarf<00:25:36.600> maybe<00:25:37.600> we<00:25:37.720> can<00:25:37.870> dig 00:25:37.920 --> 00:25:37.930 align:start position:0% come here with dwarf maybe we can dig 00:25:37.930 --> 00:25:40.770 align:start position:0% come here with dwarf maybe we can dig listen<00:25:38.230> I<00:25:38.440> can't<00:25:38.680> a<00:25:38.830> sign<00:25:39.100> at<00:25:39.310> least<00:25:39.550> maybe<00:25:40.540> we 00:25:40.770 --> 00:25:40.780 align:start position:0% listen I can't a sign at least maybe we 00:25:40.780 --> 00:25:45.630 align:start position:0% listen I can't a sign at least maybe we can<00:25:40.930> get<00:25:41.050> the<00:25:41.200> spec<00:25:41.500> under<00:25:41.800> 400<00:25:42.310> pages<00:25:44.430> so<00:25:45.430> it 00:25:45.630 --> 00:25:45.640 align:start position:0% can get the spec under 400 pages so it 00:25:45.640 --> 00:25:47.970 align:start position:0% can get the spec under 400 pages so it into<00:25:45.940> ARF<00:25:46.150> the<00:25:46.600> the<00:25:46.960> top-level<00:25:47.320> concept<00:25:47.860> they 00:25:47.970 --> 00:25:47.980 align:start position:0% into ARF the the top-level concept they 00:25:47.980 --> 00:25:49.680 align:start position:0% into ARF the the top-level concept they call<00:25:48.130> the<00:25:48.280> diee<00:25:48.850> of<00:25:49.090> debugging<00:25:49.540> information 00:25:49.680 --> 00:25:49.690 align:start position:0% call the diee of debugging information 00:25:49.690 --> 00:25:51.810 align:start position:0% call the diee of debugging information entry<00:25:50.440> so<00:25:50.860> that's<00:25:51.040> the<00:25:51.160> thing<00:25:51.370> with<00:25:51.460> the<00:25:51.610> tag 00:25:51.810 --> 00:25:51.820 align:start position:0% entry so that's the thing with the tag 00:25:51.820 --> 00:25:54.750 align:start position:0% entry so that's the thing with the tag each<00:25:52.150> diee<00:25:52.660> has<00:25:52.930> a<00:25:52.960> tag<00:25:53.260> and<00:25:53.770> then<00:25:53.950> the<00:25:54.520> tag 00:25:54.750 --> 00:25:54.760 align:start position:0% each diee has a tag and then the tag 00:25:54.760 --> 00:25:56.880 align:start position:0% each diee has a tag and then the tag each<00:25:55.090> tag<00:25:55.360> has<00:25:55.390> a<00:25:55.570> number<00:25:55.810> of<00:25:55.840> attributes<00:25:56.020> and 00:25:56.880 --> 00:25:56.890 align:start position:0% each tag has a number of attributes and 00:25:56.890 --> 00:25:58.410 align:start position:0% each tag has a number of attributes and so<00:25:57.010> I<00:25:57.040> don't<00:25:57.190> know<00:25:57.250> maybe<00:25:57.370> a<00:25:57.520> start<00:25:58.150> here<00:25:58.300> will 00:25:58.410 --> 00:25:58.420 align:start position:0% so I don't know maybe a start here will 00:25:58.420 --> 00:25:59.550 align:start position:0% so I don't know maybe a start here will be<00:25:58.510> to<00:25:58.630> figure<00:25:58.870> out<00:25:59.020> how<00:25:59.080> we<00:25:59.140> can<00:25:59.230> do<00:25:59.320> this<00:25:59.410> in 00:25:59.550 --> 00:25:59.560 align:start position:0% be to figure out how we can do this in 00:25:59.560 --> 00:26:02.790 align:start position:0% be to figure out how we can do this in JSON<00:26:00.870> I'm<00:26:01.870> gonna<00:26:01.990> scratch<00:26:02.320> paper 00:26:02.790 --> 00:26:02.800 align:start position:0% JSON I'm gonna scratch paper 00:26:02.800 --> 00:26:04.380 align:start position:0% JSON I'm gonna scratch paper I<00:26:03.220> don't<00:26:03.610> know<00:26:03.670> I'm<00:26:03.790> talking<00:26:04.060> about<00:26:04.090> your 00:26:04.380 --> 00:26:04.390 align:start position:0% I don't know I'm talking about your 00:26:04.390 --> 00:26:06.600 align:start position:0% I don't know I'm talking about your cells<00:26:04.570> there's<00:26:04.900> a<00:26:05.140> lot<00:26:05.410> of<00:26:05.500> people<00:26:05.800> here<00:26:06.010> yeah 00:26:06.600 --> 00:26:06.610 align:start position:0% cells there's a lot of people here yeah 00:26:06.610 --> 00:26:10.110 align:start position:0% cells there's a lot of people here yeah I<00:26:06.850> was<00:26:07.060> expecting<00:26:07.450> tables<00:26:07.810> but<00:26:08.910> now<00:26:09.910> you<00:26:10.060> just 00:26:10.110 --> 00:26:10.120 align:start position:0% I was expecting tables but now you just 00:26:10.120 --> 00:26:14.150 align:start position:0% I was expecting tables but now you just have<00:26:10.330> chairs<00:26:10.950> all<00:26:11.950> right<00:26:12.070> I'll<00:26:12.400> give<00:26:12.790> everyone 00:26:14.150 --> 00:26:14.160 align:start position:0% have chairs all right I'll give everyone 00:26:14.160 --> 00:26:18.360 align:start position:0% have chairs all right I'll give everyone some<00:26:15.160> people<00:26:15.400> are<00:26:15.460> talking<00:26:17.070> design<00:26:18.070> a<00:26:18.100> data 00:26:18.360 --> 00:26:18.370 align:start position:0% some people are talking design a data 00:26:18.370 --> 00:26:22.379 align:start position:0% some people are talking design a data format<00:26:18.550> today 00:26:22.379 --> 00:26:22.389 align:start position:0% 00:26:22.389 --> 00:26:32.560 align:start position:0% it's<00:26:23.389> perfect<00:26:23.899> oh<00:26:27.580> yeah<00:26:28.580> sure<00:26:31.419> alright<00:26:32.419> maybe 00:26:32.560 --> 00:26:32.570 align:start position:0% it's perfect oh yeah sure alright maybe 00:26:32.570 --> 00:26:47.030 align:start position:0% it's perfect oh yeah sure alright maybe just<00:26:32.809> maybe<00:26:33.200> it's<00:26:33.379> what's<00:26:33.769> the<00:26:33.919> top<00:26:34.099> level 00:26:47.030 --> 00:26:47.040 align:start position:0% 00:26:47.040 --> 00:26:51.510 align:start position:0% [Applause]