WEBVTT Kind: captions Language: en 00:00:18.220 --> 00:00:21.940 align:start position:0% alright<00:00:19.220> great<00:00:20.080> my<00:00:21.080> name<00:00:21.200> is<00:00:21.290> Nikolai<00:00:21.650> I'm 00:00:21.940 --> 00:00:21.950 align:start position:0% alright great my name is Nikolai I'm 00:00:21.950 --> 00:00:23.740 align:start position:0% alright great my name is Nikolai I'm here<00:00:22.310> representing<00:00:22.700> Nexus<00:00:23.150> developments 00:00:23.740 --> 00:00:23.750 align:start position:0% here representing Nexus developments 00:00:23.750 --> 00:00:26.679 align:start position:0% here representing Nexus developments where<00:00:24.350> a<00:00:24.650> athyrium<00:00:25.340> R&D<00:00:26.150> shop<00:00:26.390> and 00:00:26.679 --> 00:00:26.689 align:start position:0% where a athyrium R&D shop and 00:00:26.689 --> 00:00:29.109 align:start position:0% where a athyrium R&D shop and consultancy<00:00:27.470> and<00:00:27.619> among<00:00:28.369> other<00:00:28.520> things<00:00:28.610> we 00:00:29.109 --> 00:00:29.119 align:start position:0% consultancy and among other things we 00:00:29.119 --> 00:00:30.909 align:start position:0% consultancy and among other things we publish<00:00:29.570> open<00:00:29.900> source<00:00:30.110> software<00:00:30.320> to<00:00:30.890> help 00:00:30.909 --> 00:00:30.919 align:start position:0% publish open source software to help 00:00:30.919 --> 00:00:32.830 align:start position:0% publish open source software to help other<00:00:31.430> developers<00:00:31.970> what<00:00:32.540> I'm<00:00:32.630> going<00:00:32.750> to<00:00:32.780> focus 00:00:32.830 --> 00:00:32.840 align:start position:0% other developers what I'm going to focus 00:00:32.840 --> 00:00:35.069 align:start position:0% other developers what I'm going to focus on<00:00:33.079> today<00:00:33.140> is<00:00:33.350> called<00:00:33.560> dapple<00:00:34.040> so<00:00:34.430> it<00:00:34.579> is<00:00:34.610> Apple 00:00:35.069 --> 00:00:35.079 align:start position:0% on today is called dapple so it is Apple 00:00:35.079 --> 00:00:37.540 align:start position:0% on today is called dapple so it is Apple dabble<00:00:36.079> is<00:00:36.260> a<00:00:36.290> developer<00:00:36.890> tool<00:00:37.160> for<00:00:37.430> people 00:00:37.540 --> 00:00:37.550 align:start position:0% dabble is a developer tool for people 00:00:37.550 --> 00:00:39.250 align:start position:0% dabble is a developer tool for people targeting<00:00:38.090> the<00:00:38.300> etherium<00:00:38.660> virtual<00:00:38.989> machine 00:00:39.250 --> 00:00:39.260 align:start position:0% targeting the etherium virtual machine 00:00:39.260 --> 00:00:41.950 align:start position:0% targeting the etherium virtual machine it's<00:00:39.980> a<00:00:40.340> collection<00:00:40.640> of<00:00:40.850> utilities<00:00:41.420> that<00:00:41.900> are 00:00:41.950 --> 00:00:41.960 align:start position:0% it's a collection of utilities that are 00:00:41.960 --> 00:00:44.350 align:start position:0% it's a collection of utilities that are mostly<00:00:42.440> loosely<00:00:43.100> coupled<00:00:43.310> but<00:00:43.730> they<00:00:44.120> all 00:00:44.350 --> 00:00:44.360 align:start position:0% mostly loosely coupled but they all 00:00:44.360 --> 00:00:46.870 align:start position:0% mostly loosely coupled but they all center<00:00:44.720> around<00:00:44.750> a<00:00:45.170> common<00:00:45.950> data<00:00:46.340> model<00:00:46.430> which 00:00:46.870 --> 00:00:46.880 align:start position:0% center around a common data model which 00:00:46.880 --> 00:00:49.600 align:start position:0% center around a common data model which is<00:00:46.910> one<00:00:47.240> of<00:00:47.360> our<00:00:47.450> major<00:00:48.110> key<00:00:48.620> innovations<00:00:49.280> from 00:00:49.600 --> 00:00:49.610 align:start position:0% is one of our major key innovations from 00:00:49.610 --> 00:00:51.400 align:start position:0% is one of our major key innovations from my<00:00:49.760> point<00:00:49.940> of<00:00:50.060> view<00:00:50.120> so<00:00:50.720> I'll<00:00:50.960> go<00:00:51.050> through<00:00:51.290> all 00:00:51.400 --> 00:00:51.410 align:start position:0% my point of view so I'll go through all 00:00:51.410 --> 00:00:52.600 align:start position:0% my point of view so I'll go through all these<00:00:51.530> real<00:00:51.710> quick<00:00:51.890> and<00:00:52.010> then<00:00:52.070> I'll<00:00:52.220> go<00:00:52.340> into<00:00:52.490> a 00:00:52.600 --> 00:00:52.610 align:start position:0% these real quick and then I'll go into a 00:00:52.610 --> 00:00:55.480 align:start position:0% these real quick and then I'll go into a little<00:00:52.640> more<00:00:52.820> detail<00:00:53.560> the<00:00:54.560> main<00:00:55.220> thing<00:00:55.250> is 00:00:55.480 --> 00:00:55.490 align:start position:0% little more detail the main thing is 00:00:55.490 --> 00:00:57.070 align:start position:0% little more detail the main thing is this<00:00:55.790> shared<00:00:56.210> data<00:00:56.390> model<00:00:56.660> which<00:00:56.750> we<00:00:56.870> call<00:00:56.990> the 00:00:57.070 --> 00:00:57.080 align:start position:0% this shared data model which we call the 00:00:57.080 --> 00:00:59.620 align:start position:0% this shared data model which we call the DAP<00:00:57.260> file<00:00:57.470> and<00:00:58.460> it's<00:00:58.820> a<00:00:58.970> basically<00:00:59.510> a 00:00:59.620 --> 00:00:59.630 align:start position:0% DAP file and it's a basically a 00:00:59.630 --> 00:01:02.020 align:start position:0% DAP file and it's a basically a descriptor<00:01:00.080> for<00:01:00.230> both<00:01:00.430> code<00:01:01.430> packages<00:01:01.880> and 00:01:02.020 --> 00:01:02.030 align:start position:0% descriptor for both code packages and 00:01:02.030 --> 00:01:04.420 align:start position:0% descriptor for both code packages and also<00:01:02.210> deployed<00:01:02.570> systems<00:01:03.170> and<00:01:03.590> then<00:01:04.040> chain 00:01:04.420 --> 00:01:04.430 align:start position:0% also deployed systems and then chain 00:01:04.430 --> 00:01:06.249 align:start position:0% also deployed systems and then chain forking<00:01:04.879> creating<00:01:05.390> local<00:01:05.540> chain<00:01:05.840> Forks<00:01:06.170> and 00:01:06.249 --> 00:01:06.259 align:start position:0% forking creating local chain Forks and 00:01:06.259 --> 00:01:08.410 align:start position:0% forking creating local chain Forks and then<00:01:06.409> having<00:01:06.619> modified<00:01:07.549> evm<00:01:07.939> behavior<00:01:08.299> on 00:01:08.410 --> 00:01:08.420 align:start position:0% then having modified evm behavior on 00:01:08.420 --> 00:01:10.060 align:start position:0% then having modified evm behavior on those<00:01:08.540> local<00:01:08.869> chain<00:01:09.020> Forks<00:01:09.350> these<00:01:09.860> three 00:01:10.060 --> 00:01:10.070 align:start position:0% those local chain Forks these three 00:01:10.070 --> 00:01:11.140 align:start position:0% those local chain Forks these three things<00:01:10.100> together<00:01:10.400> like<00:01:10.670> you<00:01:10.759> do<00:01:10.820> some<00:01:10.970> really 00:01:11.140 --> 00:01:11.150 align:start position:0% things together like you do some really 00:01:11.150 --> 00:01:13.179 align:start position:0% things together like you do some really interesting<00:01:11.360> things<00:01:11.570> and<00:01:12.049> in<00:01:12.380> particular<00:01:13.040> the 00:01:13.179 --> 00:01:13.189 align:start position:0% interesting things and in particular the 00:01:13.189 --> 00:01:15.010 align:start position:0% interesting things and in particular the entire<00:01:13.490> like<00:01:13.790> development<00:01:14.240> workflow<00:01:14.689> of 00:01:15.010 --> 00:01:15.020 align:start position:0% entire like development workflow of 00:01:15.020 --> 00:01:16.899 align:start position:0% entire like development workflow of creating<00:01:15.799> contract<00:01:16.220> systems<00:01:16.520> that<00:01:16.640> talk<00:01:16.790> to 00:01:16.899 --> 00:01:16.909 align:start position:0% creating contract systems that talk to 00:01:16.909 --> 00:01:19.990 align:start position:0% creating contract systems that talk to other<00:01:17.000> contract<00:01:17.420> systems<00:01:17.750> kids<00:01:18.290> really<00:01:18.619> a<00:01:19.000> it 00:01:19.990 --> 00:01:20.000 align:start position:0% other contract systems kids really a it 00:01:20.000 --> 00:01:21.310 align:start position:0% other contract systems kids really a it helps<00:01:20.210> a<00:01:20.300> lot<00:01:20.420> to<00:01:20.540> how<00:01:20.630> these<00:01:20.750> features<00:01:21.050> so<00:01:21.170> let 00:01:21.310 --> 00:01:21.320 align:start position:0% helps a lot to how these features so let 00:01:21.320 --> 00:01:24.030 align:start position:0% helps a lot to how these features so let me<00:01:21.380> just<00:01:21.620> go<00:01:21.770> through<00:01:22.210> you<00:01:23.210> should<00:01:23.360> use<00:01:23.450> again 00:01:24.030 --> 00:01:24.040 align:start position:0% me just go through you should use again 00:01:24.040 --> 00:01:26.560 align:start position:0% me just go through you should use again the<00:01:25.040> first<00:01:25.280> thing<00:01:25.430> is<00:01:25.490> that<00:01:25.550> the<00:01:25.730> key<00:01:25.970> insight 00:01:26.560 --> 00:01:26.570 align:start position:0% the first thing is that the key insight 00:01:26.570 --> 00:01:28.330 align:start position:0% the first thing is that the key insight that<00:01:26.780> drives<00:01:27.020> this<00:01:27.230> first<00:01:27.500> innovation<00:01:27.770> is 00:01:28.330 --> 00:01:28.340 align:start position:0% that drives this first innovation is 00:01:28.340 --> 00:01:30.190 align:start position:0% that drives this first innovation is that<00:01:28.580> if<00:01:29.030> theory<00:01:29.420> em<00:01:29.540> land<00:01:29.720> is<00:01:29.870> slightly 00:01:30.190 --> 00:01:30.200 align:start position:0% that if theory em land is slightly 00:01:30.200 --> 00:01:33.850 align:start position:0% that if theory em land is slightly different<00:01:30.440> from<00:01:30.909> most<00:01:31.909> of<00:01:32.090> the<00:01:32.150> other<00:01:32.860> you 00:01:33.850 --> 00:01:33.860 align:start position:0% different from most of the other you 00:01:33.860 --> 00:01:35.070 align:start position:0% different from most of the other you know<00:01:33.890> programming<00:01:34.340> language<00:01:34.640> environment 00:01:35.070 --> 00:01:35.080 align:start position:0% know programming language environment 00:01:35.080 --> 00:01:37.810 align:start position:0% know programming language environment worlds<00:01:36.080> because<00:01:36.260> in<00:01:36.770> a<00:01:37.040> theory<00:01:37.370> i<00:01:37.400> mean<00:01:37.580> we 00:01:37.810 --> 00:01:37.820 align:start position:0% worlds because in a theory i mean we 00:01:37.820 --> 00:01:40.360 align:start position:0% worlds because in a theory i mean we actually<00:01:37.850> all<00:01:38.300> share<00:01:38.690> a<00:01:38.930> global<00:01:39.560> runtime 00:01:40.360 --> 00:01:40.370 align:start position:0% actually all share a global runtime 00:01:40.370 --> 00:01:41.980 align:start position:0% actually all share a global runtime environment<00:01:40.850> and<00:01:40.970> so<00:01:41.060> this<00:01:41.210> blurs<00:01:41.630> the<00:01:41.659> line 00:01:41.980 --> 00:01:41.990 align:start position:0% environment and so this blurs the line 00:01:41.990 --> 00:01:43.510 align:start position:0% environment and so this blurs the line between<00:01:42.020> something<00:01:42.500> that's<00:01:42.620> a<00:01:42.800> code<00:01:43.010> package 00:01:43.510 --> 00:01:43.520 align:start position:0% between something that's a code package 00:01:43.520 --> 00:01:46.030 align:start position:0% between something that's a code package and<00:01:43.760> something<00:01:44.540> that's<00:01:44.570> it<00:01:44.930> like<00:01:45.530> an<00:01:45.650> instance 00:01:46.030 --> 00:01:46.040 align:start position:0% and something that's it like an instance 00:01:46.040 --> 00:01:48.580 align:start position:0% and something that's it like an instance or<00:01:46.220> like<00:01:46.460> a<00:01:46.490> deployed<00:01:46.850> code<00:01:47.630> object<00:01:48.020> so<00:01:48.440> this 00:01:48.580 --> 00:01:48.590 align:start position:0% or like a deployed code object so this 00:01:48.590 --> 00:01:51.640 align:start position:0% or like a deployed code object so this would<00:01:48.740> be<00:01:48.770> like<00:01:49.060> if<00:01:50.060> you<00:01:50.420> hard<00:01:50.960> code<00:01:51.260> like<00:01:51.620> a 00:01:51.640 --> 00:01:51.650 align:start position:0% would be like if you hard code like a 00:01:51.650 --> 00:01:54.130 align:start position:0% would be like if you hard code like a web<00:01:52.010> endpoints<00:01:52.700> into<00:01:53.030> your<00:01:53.240> JavaScript 00:01:54.130 --> 00:01:54.140 align:start position:0% web endpoints into your JavaScript 00:01:54.140 --> 00:01:55.480 align:start position:0% web endpoints into your JavaScript package<00:01:54.440> or<00:01:54.560> something<00:01:54.830> that's<00:01:55.159> considered 00:01:55.480 --> 00:01:55.490 align:start position:0% package or something that's considered 00:01:55.490 --> 00:01:58.180 align:start position:0% package or something that's considered bad<00:01:55.610> practice<00:01:56.030> you<00:01:56.960> want<00:01:57.140> it<00:01:57.229> like<00:01:57.320> separately 00:01:58.180 --> 00:01:58.190 align:start position:0% bad practice you want it like separately 00:01:58.190 --> 00:01:59.740 align:start position:0% bad practice you want it like separately how<00:01:58.369> to<00:01:58.430> depend<00:01:58.820> on<00:01:58.940> a<00:01:58.970> configuration<00:01:59.720> where 00:01:59.740 --> 00:01:59.750 align:start position:0% how to depend on a configuration where 00:01:59.750 --> 00:02:01.210 align:start position:0% how to depend on a configuration where there<00:02:00.080> you<00:02:00.229> configure<00:02:00.590> your<00:02:00.740> endpoints<00:02:01.190> and 00:02:01.210 --> 00:02:01.220 align:start position:0% there you configure your endpoints and 00:02:01.220 --> 00:02:03.190 align:start position:0% there you configure your endpoints and then<00:02:01.369> have<00:02:01.520> all<00:02:01.670> that<00:02:01.790> logic<00:02:02.210> in<00:02:02.360> your<00:02:02.990> code 00:02:03.190 --> 00:02:03.200 align:start position:0% then have all that logic in your code 00:02:03.200 --> 00:02:06.070 align:start position:0% then have all that logic in your code but<00:02:04.130> in<00:02:04.250> a<00:02:04.310> theory<00:02:04.520> immunes<00:02:05.180> like<00:02:05.450> say<00:02:05.810> the 00:02:06.070 --> 00:02:06.080 align:start position:0% but in a theory immunes like say the 00:02:06.080 --> 00:02:08.529 align:start position:0% but in a theory immunes like say the ether<00:02:06.590> token<00:02:07.010> wrapper<00:02:07.220> which<00:02:07.549> is<00:02:07.790> stateful 00:02:08.529 --> 00:02:08.539 align:start position:0% ether token wrapper which is stateful 00:02:08.539 --> 00:02:10.240 align:start position:0% ether token wrapper which is stateful it's<00:02:08.810> a<00:02:08.929> deployed<00:02:09.349> object<00:02:09.769> that<00:02:09.830> you<00:02:09.920> interact 00:02:10.240 --> 00:02:10.250 align:start position:0% it's a deployed object that you interact 00:02:10.250 --> 00:02:13.570 align:start position:0% it's a deployed object that you interact with<00:02:10.340> but<00:02:10.700> it's<00:02:11.269> also<00:02:11.599> not<00:02:12.590> there's<00:02:13.489> an 00:02:13.570 --> 00:02:13.580 align:start position:0% with but it's also not there's an 00:02:13.580 --> 00:02:14.860 align:start position:0% with but it's also not there's an absolutely<00:02:13.939> no<00:02:14.150> reason<00:02:14.360> to<00:02:14.480> redeploy 00:02:14.860 --> 00:02:14.870 align:start position:0% absolutely no reason to redeploy 00:02:14.870 --> 00:02:16.479 align:start position:0% absolutely no reason to redeploy everyone<00:02:15.290> should<00:02:15.409> be<00:02:15.530> treating<00:02:15.920> it<00:02:16.040> sort<00:02:16.430> of 00:02:16.479 --> 00:02:16.489 align:start position:0% everyone should be treating it sort of 00:02:16.489 --> 00:02:17.770 align:start position:0% everyone should be treating it sort of like<00:02:16.580> a<00:02:16.640> library<00:02:17.120> like<00:02:17.299> you<00:02:17.420> know<00:02:17.510> you<00:02:17.569> have 00:02:17.770 --> 00:02:17.780 align:start position:0% like a library like you know you have 00:02:17.780 --> 00:02:19.390 align:start position:0% like a library like you know you have the<00:02:17.810> math<00:02:18.019> library<00:02:18.530> on<00:02:18.680> a<00:02:18.709> theorem<00:02:19.040> everyone 00:02:19.390 --> 00:02:19.400 align:start position:0% the math library on a theorem everyone 00:02:19.400 --> 00:02:21.309 align:start position:0% the math library on a theorem everyone uses<00:02:20.000> the<00:02:20.120> same<00:02:20.299> address<00:02:20.689> or<00:02:20.870> in<00:02:20.989> theory<00:02:21.230> we 00:02:21.309 --> 00:02:21.319 align:start position:0% uses the same address or in theory we 00:02:21.319 --> 00:02:23.140 align:start position:0% uses the same address or in theory we should<00:02:21.680> be<00:02:21.769> doing<00:02:21.890> that<00:02:22.129> for<00:02:22.430> the<00:02:22.970> math 00:02:23.140 --> 00:02:23.150 align:start position:0% should be doing that for the math 00:02:23.150 --> 00:02:24.460 align:start position:0% should be doing that for the math functions<00:02:23.599> likewise<00:02:24.020> we<00:02:24.230> should<00:02:24.380> all<00:02:24.440> be 00:02:24.460 --> 00:02:24.470 align:start position:0% functions likewise we should all be 00:02:24.470 --> 00:02:26.310 align:start position:0% functions likewise we should all be using<00:02:24.770> the<00:02:24.860> same 00:02:26.310 --> 00:02:26.320 align:start position:0% using the same 00:02:26.320 --> 00:02:28.690 align:start position:0% using the same package<00:02:27.320> for<00:02:27.500> like<00:02:27.680> the<00:02:27.830> ether<00:02:28.130> token<00:02:28.520> wrapper 00:02:28.690 --> 00:02:28.700 align:start position:0% package for like the ether token wrapper 00:02:28.700 --> 00:02:30.760 align:start position:0% package for like the ether token wrapper which<00:02:28.910> creates<00:02:29.240> it<00:02:29.330> into<00:02:29.540> an<00:02:29.690> erc<00:02:30.110> 20<00:02:30.470> token 00:02:30.760 --> 00:02:30.770 align:start position:0% which creates it into an erc 20 token 00:02:30.770 --> 00:02:32.650 align:start position:0% which creates it into an erc 20 token but<00:02:31.430> that<00:02:31.550> hasn't<00:02:31.700> address<00:02:32.120> in<00:02:32.360> it<00:02:32.480> that's 00:02:32.650 --> 00:02:32.660 align:start position:0% but that hasn't address in it that's 00:02:32.660 --> 00:02:34.210 align:start position:0% but that hasn't address in it that's part<00:02:32.870> of<00:02:32.930> the<00:02:33.080> definition<00:02:33.290> of<00:02:33.650> that<00:02:33.710> code 00:02:34.210 --> 00:02:34.220 align:start position:0% part of the definition of that code 00:02:34.220 --> 00:02:37.440 align:start position:0% part of the definition of that code packages<00:02:34.790> that<00:02:34.910> there's<00:02:35.060> an<00:02:35.180> object<00:02:35.600> deployed 00:02:37.440 --> 00:02:37.450 align:start position:0% packages that there's an object deployed 00:02:37.450 --> 00:02:40.120 align:start position:0% packages that there's an object deployed so<00:02:38.450> yeah<00:02:38.990> so<00:02:39.140> this<00:02:39.290> is<00:02:39.350> an<00:02:39.440> example<00:02:39.500> job<00:02:39.920> file 00:02:40.120 --> 00:02:40.130 align:start position:0% so yeah so this is an example job file 00:02:40.130 --> 00:02:41.920 align:start position:0% so yeah so this is an example job file don't<00:02:40.460> worry<00:02:40.610> about<00:02:40.640> it<00:02:40.850> too<00:02:41.000> much<00:02:41.030> the<00:02:41.480> key 00:02:41.920 --> 00:02:41.930 align:start position:0% don't worry about it too much the key 00:02:41.930 --> 00:02:43.180 align:start position:0% don't worry about it too much the key thing<00:02:42.170> is<00:02:42.200> this<00:02:42.470> highlighted<00:02:42.800> thing<00:02:43.010> which<00:02:43.160> is 00:02:43.180 --> 00:02:43.190 align:start position:0% thing is this highlighted thing which is 00:02:43.190 --> 00:02:45.820 align:start position:0% thing is this highlighted thing which is that<00:02:43.400> the<00:02:43.520> the<00:02:43.730> type<00:02:44.210> information<00:02:44.600> is<00:02:45.530> very 00:02:45.820 --> 00:02:45.830 align:start position:0% that the the type information is very 00:02:45.830 --> 00:02:48.250 align:start position:0% that the the type information is very rich<00:02:46.040> it<00:02:46.190> has<00:02:46.310> all<00:02:46.550> the<00:02:46.580> metadata<00:02:47.450> we<00:02:47.780> need<00:02:48.020> to 00:02:48.250 --> 00:02:48.260 align:start position:0% rich it has all the metadata we need to 00:02:48.260 --> 00:02:50.140 align:start position:0% rich it has all the metadata we need to just<00:02:48.470> fully<00:02:48.680> recreate<00:02:49.220> how<00:02:49.550> this<00:02:49.790> thing<00:02:50.000> got 00:02:50.140 --> 00:02:50.150 align:start position:0% just fully recreate how this thing got 00:02:50.150 --> 00:02:53.380 align:start position:0% just fully recreate how this thing got here<00:02:51.220> so<00:02:52.220> the<00:02:52.400> next<00:02:52.430> innovation<00:02:52.880> is<00:02:53.120> chained 00:02:53.380 --> 00:02:53.390 align:start position:0% here so the next innovation is chained 00:02:53.390 --> 00:02:56.380 align:start position:0% here so the next innovation is chained forking<00:02:53.780> you'll<00:02:54.350> notice<00:02:54.650> it's<00:02:55.100> a<00:02:55.390> user 00:02:56.380 --> 00:02:56.390 align:start position:0% forking you'll notice it's a user 00:02:56.390 --> 00:02:57.940 align:start position:0% forking you'll notice it's a user experience<00:02:56.660> very<00:02:57.110> similar<00:02:57.350> to<00:02:57.410> get<00:02:57.680> that 00:02:57.940 --> 00:02:57.950 align:start position:0% experience very similar to get that 00:02:57.950 --> 00:02:58.990 align:start position:0% experience very similar to get that because<00:02:58.250> they're<00:02:58.400> very<00:02:58.550> similar<00:02:58.700> data 00:02:58.990 --> 00:02:59.000 align:start position:0% because they're very similar data 00:02:59.000 --> 00:03:01.120 align:start position:0% because they're very similar data structures<00:02:59.420> the<00:03:00.020> missing<00:03:00.380> part<00:03:00.620> here<00:03:00.920> is 00:03:01.120 --> 00:03:01.130 align:start position:0% structures the missing part here is 00:03:01.130 --> 00:03:03.640 align:start position:0% structures the missing part here is merged<00:03:01.520> because<00:03:02.090> there's<00:03:02.390> no<00:03:02.630> analogue<00:03:03.320> to 00:03:03.640 --> 00:03:03.650 align:start position:0% merged because there's no analogue to 00:03:03.650 --> 00:03:05.470 align:start position:0% merged because there's no analogue to resolving<00:03:04.160> merge<00:03:04.340> conflicts<00:03:04.910> automatically 00:03:05.470 --> 00:03:05.480 align:start position:0% resolving merge conflicts automatically 00:03:05.480 --> 00:03:07.240 align:start position:0% resolving merge conflicts automatically when<00:03:05.630> you<00:03:05.690> try<00:03:05.870> to<00:03:05.900> replay<00:03:06.350> Center 00:03:07.240 --> 00:03:07.250 align:start position:0% when you try to replay Center 00:03:07.250 --> 00:03:08.470 align:start position:0% when you try to replay Center transactions<00:03:07.880> and<00:03:08.000> it<00:03:08.120> doesn't<00:03:08.360> have<00:03:08.450> the 00:03:08.470 --> 00:03:08.480 align:start position:0% transactions and it doesn't have the 00:03:08.480 --> 00:03:11.320 align:start position:0% transactions and it doesn't have the same<00:03:08.570> result<00:03:09.190> so<00:03:10.190> that's<00:03:10.370> chain<00:03:10.730> forking<00:03:11.150> and 00:03:11.320 --> 00:03:11.330 align:start position:0% same result so that's chain forking and 00:03:11.330 --> 00:03:13.020 align:start position:0% same result so that's chain forking and finally<00:03:11.840> okay<00:03:12.080> this<00:03:12.290> is<00:03:12.350> an<00:03:12.410> example<00:03:12.650> of 00:03:13.020 --> 00:03:13.030 align:start position:0% finally okay this is an example of 00:03:13.030 --> 00:03:15.420 align:start position:0% finally okay this is an example of basically<00:03:14.030> you<00:03:14.210> can<00:03:14.360> actually<00:03:14.480> fork<00:03:14.840> any 00:03:15.420 --> 00:03:15.430 align:start position:0% basically you can actually fork any 00:03:15.430 --> 00:03:17.680 align:start position:0% basically you can actually fork any public<00:03:16.430> athyrium<00:03:16.790> chain<00:03:17.000> without<00:03:17.360> their 00:03:17.680 --> 00:03:17.690 align:start position:0% public athyrium chain without their 00:03:17.690 --> 00:03:18.940 align:start position:0% public athyrium chain without their permission<00:03:17.780> basically<00:03:18.380> just<00:03:18.500> because<00:03:18.740> of<00:03:18.830> how 00:03:18.940 --> 00:03:18.950 align:start position:0% permission basically just because of how 00:03:18.950 --> 00:03:20.920 align:start position:0% permission basically just because of how the<00:03:19.010> data<00:03:19.220> structure<00:03:19.610> works<00:03:19.790> but<00:03:20.540> by<00:03:20.630> default 00:03:20.920 --> 00:03:20.930 align:start position:0% the data structure works but by default 00:03:20.930 --> 00:03:23.680 align:start position:0% the data structure works but by default we<00:03:21.170> let<00:03:21.770> you<00:03:21.920> specify<00:03:22.910> remote<00:03:23.360> one<00:03:23.510> and 00:03:23.680 --> 00:03:23.690 align:start position:0% we let you specify remote one and 00:03:23.690 --> 00:03:25.720 align:start position:0% we let you specify remote one and internal<00:03:24.170> just<00:03:24.350> means<00:03:24.500> a<00:03:24.590> brand<00:03:25.130> new<00:03:25.280> blankie 00:03:25.720 --> 00:03:25.730 align:start position:0% internal just means a brand new blankie 00:03:25.730 --> 00:03:28.690 align:start position:0% internal just means a brand new blankie vm<00:03:26.030> on<00:03:26.690> your<00:03:26.930> machine<00:03:27.080> and<00:03:27.500> for<00:03:27.860> QVC<00:03:28.310> and<00:03:28.580> where 00:03:28.690 --> 00:03:28.700 align:start position:0% vm on your machine and for QVC and where 00:03:28.700 --> 00:03:31.090 align:start position:0% vm on your machine and for QVC and where it<00:03:28.760> should<00:03:29.000> be<00:03:29.030> self-explanatory<00:03:30.100> and 00:03:31.090 --> 00:03:31.100 align:start position:0% it should be self-explanatory and 00:03:31.100 --> 00:03:34.030 align:start position:0% it should be self-explanatory and finally<00:03:31.970> EVM<00:03:32.330> extensions<00:03:32.930> are<00:03:33.170> when<00:03:33.830> you 00:03:34.030 --> 00:03:34.040 align:start position:0% finally EVM extensions are when you 00:03:34.040 --> 00:03:35.320 align:start position:0% finally EVM extensions are when you slightly<00:03:34.340> change<00:03:34.700> the<00:03:34.820> behavior<00:03:35.150> of<00:03:35.180> the 00:03:35.320 --> 00:03:35.330 align:start position:0% slightly change the behavior of the 00:03:35.330 --> 00:03:37.060 align:start position:0% slightly change the behavior of the virtual<00:03:35.660> machine<00:03:35.750> on<00:03:36.140> your<00:03:36.470> private<00:03:36.830> chain 00:03:37.060 --> 00:03:37.070 align:start position:0% virtual machine on your private chain 00:03:37.070 --> 00:03:38.830 align:start position:0% virtual machine on your private chain and<00:03:37.970> this<00:03:38.180> lets<00:03:38.420> you<00:03:38.480> do<00:03:38.570> some<00:03:38.720> really 00:03:38.830 --> 00:03:38.840 align:start position:0% and this lets you do some really 00:03:38.840 --> 00:03:41.230 align:start position:0% and this lets you do some really interesting<00:03:38.990> things<00:03:39.170> as<00:03:39.530> you'll<00:03:39.680> see<00:03:39.880> so<00:03:40.880> now 00:03:41.230 --> 00:03:41.240 align:start position:0% interesting things as you'll see so now 00:03:41.240 --> 00:03:43.270 align:start position:0% interesting things as you'll see so now let's<00:03:41.510> go<00:03:41.960> through<00:03:42.230> the<00:03:42.410> workflow<00:03:42.560> how<00:03:42.860> have 00:03:43.270 --> 00:03:43.280 align:start position:0% let's go through the workflow how have 00:03:43.280 --> 00:03:46.060 align:start position:0% let's go through the workflow how have we<00:03:43.490> developed<00:03:44.210> apps<00:03:44.390> using<00:03:44.720> double<00:03:45.110> first 00:03:46.060 --> 00:03:46.070 align:start position:0% we developed apps using double first 00:03:46.070 --> 00:03:47.740 align:start position:0% we developed apps using double first thing<00:03:46.310> find<00:03:46.820> some<00:03:46.970> dependencies<00:03:47.450> this<00:03:47.630> is 00:03:47.740 --> 00:03:47.750 align:start position:0% thing find some dependencies this is 00:03:47.750 --> 00:03:49.390 align:start position:0% thing find some dependencies this is like<00:03:47.870> a<00:03:47.900> habit<00:03:48.710> that<00:03:48.740> you<00:03:48.860> have<00:03:49.100> in<00:03:49.250> every 00:03:49.390 --> 00:03:49.400 align:start position:0% like a habit that you have in every 00:03:49.400 --> 00:03:50.590 align:start position:0% like a habit that you have in every other<00:03:49.490> language<00:03:49.880> for<00:03:50.000> some<00:03:50.180> reason<00:03:50.420> everyone 00:03:50.590 --> 00:03:50.600 align:start position:0% other language for some reason everyone 00:03:50.600 --> 00:03:51.730 align:start position:0% other language for some reason everyone wants<00:03:50.840> to<00:03:50.870> start<00:03:51.080> from<00:03:51.170> scratch<00:03:51.380> from<00:03:51.560> there 00:03:51.730 --> 00:03:51.740 align:start position:0% wants to start from scratch from there 00:03:51.740 --> 00:03:54.550 align:start position:0% wants to start from scratch from there creating<00:03:52.100> their<00:03:52.220> own<00:03:52.250> contracts<00:03:53.260> this<00:03:54.260> is<00:03:54.410> our 00:03:54.550 --> 00:03:54.560 align:start position:0% creating their own contracts this is our 00:03:54.560 --> 00:03:56.380 align:start position:0% creating their own contracts this is our as<00:03:55.070> a<00:03:55.130> hint<00:03:55.400> so<00:03:55.520> we<00:03:55.610> suggest<00:03:55.760> that<00:03:56.120> we<00:03:56.270> have 00:03:56.380 --> 00:03:56.390 align:start position:0% as a hint so we suggest that we have 00:03:56.390 --> 00:03:57.460 align:start position:0% as a hint so we suggest that we have like<00:03:56.570> something<00:03:56.870> like<00:03:56.990> sort<00:03:57.260> of<00:03:57.320> like<00:03:57.440> a 00:03:57.460 --> 00:03:57.470 align:start position:0% like something like sort of like a 00:03:57.470 --> 00:04:00.280 align:start position:0% like something like sort of like a standard<00:03:57.860> library<00:03:58.280> which<00:03:59.150> we<00:03:59.570> are<00:03:59.930> keen<00:04:00.260> to 00:04:00.280 --> 00:04:00.290 align:start position:0% standard library which we are keen to 00:04:00.290 --> 00:04:02.260 align:start position:0% standard library which we are keen to get<00:04:00.530> formally<00:04:00.920> verified<00:04:00.950> and<00:04:01.850> it<00:04:01.940> has<00:04:02.030> a<00:04:02.060> lot 00:04:02.260 --> 00:04:02.270 align:start position:0% get formally verified and it has a lot 00:04:02.270 --> 00:04:03.790 align:start position:0% get formally verified and it has a lot of<00:04:02.300> stuff<00:04:02.540> like<00:04:02.720> Roxy<00:04:03.050> actors<00:04:03.320> tokens<00:04:03.650> by<00:04:03.740> the 00:04:03.790 --> 00:04:03.800 align:start position:0% of stuff like Roxy actors tokens by the 00:04:03.800 --> 00:04:06.190 align:start position:0% of stuff like Roxy actors tokens by the way<00:04:03.920> you<00:04:03.980> can<00:04:04.130> read<00:04:04.250> the<00:04:04.370> list<00:04:04.550> I'm<00:04:05.510> sure<00:04:05.750> the 00:04:06.190 --> 00:04:06.200 align:start position:0% way you can read the list I'm sure the 00:04:06.200 --> 00:04:07.750 align:start position:0% way you can read the list I'm sure the other<00:04:06.320> ideas<00:04:06.620> that<00:04:06.740> these<00:04:06.860> are<00:04:06.980> like 00:04:07.750 --> 00:04:07.760 align:start position:0% other ideas that these are like 00:04:07.760 --> 00:04:09.760 align:start position:0% other ideas that these are like composable<00:04:08.330> building<00:04:08.660> blocks<00:04:08.870> each<00:04:09.110> is<00:04:09.590> very 00:04:09.760 --> 00:04:09.770 align:start position:0% composable building blocks each is very 00:04:09.770 --> 00:04:13.180 align:start position:0% composable building blocks each is very simple<00:04:10.070> and<00:04:10.400> easy<00:04:10.820> to<00:04:11.120> verify<00:04:11.240> and<00:04:11.840> then<00:04:12.190> you 00:04:13.180 --> 00:04:13.190 align:start position:0% simple and easy to verify and then you 00:04:13.190 --> 00:04:14.830 align:start position:0% simple and easy to verify and then you actually<00:04:13.400> most<00:04:13.760> apps<00:04:13.970> can<00:04:14.180> be<00:04:14.240> built<00:04:14.510> out<00:04:14.630> of 00:04:14.830 --> 00:04:14.840 align:start position:0% actually most apps can be built out of 00:04:14.840 --> 00:04:16.090 align:start position:0% actually most apps can be built out of just<00:04:15.080> a<00:04:15.170> collection<00:04:15.320> things<00:04:15.740> like<00:04:15.830> very<00:04:15.980> few 00:04:16.090 --> 00:04:16.100 align:start position:0% just a collection things like very few 00:04:16.100 --> 00:04:19.060 align:start position:0% just a collection things like very few like<00:04:16.370> each<00:04:17.239> DAP<00:04:17.630> that<00:04:17.960> each<00:04:18.140> new<00:04:18.470> system<00:04:19.040> that 00:04:19.060 --> 00:04:19.070 align:start position:0% like each DAP that each new system that 00:04:19.070 --> 00:04:20.590 align:start position:0% like each DAP that each new system that we<00:04:19.250> make<00:04:19.400> usually<00:04:19.760> only<00:04:19.910> has<00:04:20.090> like<00:04:20.239> one<00:04:20.450> or<00:04:20.570> two 00:04:20.590 --> 00:04:20.600 align:start position:0% we make usually only has like one or two 00:04:20.600 --> 00:04:22.300 align:start position:0% we make usually only has like one or two contracts<00:04:21.260> with<00:04:21.410> custom<00:04:21.739> logic<00:04:21.859> and<00:04:22.130> then<00:04:22.220> it 00:04:22.300 --> 00:04:22.310 align:start position:0% contracts with custom logic and then it 00:04:22.310 --> 00:04:24.310 align:start position:0% contracts with custom logic and then it has<00:04:22.400> like<00:04:22.430> five<00:04:23.060> dependent<00:04:23.660> contracts<00:04:24.080> that 00:04:24.310 --> 00:04:24.320 align:start position:0% has like five dependent contracts that 00:04:24.320 --> 00:04:26.950 align:start position:0% has like five dependent contracts that are<00:04:24.350> just<00:04:24.560> things<00:04:24.740> we've<00:04:24.890> built<00:04:25.100> before<00:04:25.960> so 00:04:26.950 --> 00:04:26.960 align:start position:0% are just things we've built before so 00:04:26.960 --> 00:04:27.880 align:start position:0% are just things we've built before so again<00:04:27.140> yeah<00:04:27.290> if<00:04:27.440> you're<00:04:27.530> interested<00:04:27.860> in 00:04:27.880 --> 00:04:27.890 align:start position:0% again yeah if you're interested in 00:04:27.890 --> 00:04:30.160 align:start position:0% again yeah if you're interested in formal<00:04:28.190> verification<00:04:28.310> this<00:04:29.210> is<00:04:29.360> a<00:04:29.390> this<00:04:29.990> I 00:04:30.160 --> 00:04:30.170 align:start position:0% formal verification this is a this I 00:04:30.170 --> 00:04:32.320 align:start position:0% formal verification this is a this I mean<00:04:30.320> these<00:04:30.830> again<00:04:31.490> it's<00:04:31.880> very<00:04:32.060> simple 00:04:32.320 --> 00:04:32.330 align:start position:0% mean these again it's very simple 00:04:32.330 --> 00:04:34.659 align:start position:0% mean these again it's very simple contracts<00:04:33.200> but<00:04:33.470> they<00:04:33.620> are<00:04:33.800> in<00:04:33.950> production 00:04:34.659 --> 00:04:34.669 align:start position:0% contracts but they are in production 00:04:34.669 --> 00:04:36.310 align:start position:0% contracts but they are in production systems<00:04:35.120> right<00:04:35.270> now<00:04:35.360> in<00:04:35.570> multiple<00:04:35.960> systems 00:04:36.310 --> 00:04:36.320 align:start position:0% systems right now in multiple systems 00:04:36.320 --> 00:04:38.470 align:start position:0% systems right now in multiple systems like<00:04:36.560> nothing<00:04:36.980> in<00:04:37.070> here<00:04:37.310> is<00:04:37.490> something<00:04:38.360> that 00:04:38.470 --> 00:04:38.480 align:start position:0% like nothing in here is something that 00:04:38.480 --> 00:04:39.030 align:start position:0% like nothing in here is something that hasn't<00:04:38.660> been 00:04:39.030 --> 00:04:39.040 align:start position:0% hasn't been 00:04:39.040 --> 00:04:42.210 align:start position:0% hasn't been used<00:04:39.930> so<00:04:40.930> the<00:04:41.290> next<00:04:41.320> step<00:04:41.530> is<00:04:41.770> building<00:04:42.100> and 00:04:42.210 --> 00:04:42.220 align:start position:0% used so the next step is building and 00:04:42.220 --> 00:04:44.640 align:start position:0% used so the next step is building and linking<00:04:42.460> which<00:04:42.580> is<00:04:42.700> boring<00:04:43.030> but<00:04:43.360> it's<00:04:43.990> worth 00:04:44.640 --> 00:04:44.650 align:start position:0% linking which is boring but it's worth 00:04:44.650 --> 00:04:46.320 align:start position:0% linking which is boring but it's worth noting<00:04:44.830> that<00:04:45.010> solidity<00:04:45.430> has<00:04:45.580> no<00:04:45.700> name<00:04:45.880> spaces 00:04:46.320 --> 00:04:46.330 align:start position:0% noting that solidity has no name spaces 00:04:46.330 --> 00:04:47.700 align:start position:0% noting that solidity has no name spaces and<00:04:46.510> this<00:04:46.660> is<00:04:46.780> kind<00:04:46.960> of<00:04:46.990> a<00:04:47.080> smell<00:04:47.320> that<00:04:47.350> our 00:04:47.700 --> 00:04:47.710 align:start position:0% and this is kind of a smell that our 00:04:47.710 --> 00:04:49.050 align:start position:0% and this is kind of a smell that our contract<00:04:48.280> systems<00:04:48.520> haven't<00:04:48.730> really<00:04:48.880> gotten 00:04:49.050 --> 00:04:49.060 align:start position:0% contract systems haven't really gotten 00:04:49.060 --> 00:04:51.540 align:start position:0% contract systems haven't really gotten that<00:04:49.240> complicated<00:04:49.750> yet<00:04:50.070> maker<00:04:51.070> core<00:04:51.370> for 00:04:51.540 --> 00:04:51.550 align:start position:0% that complicated yet maker core for 00:04:51.550 --> 00:04:52.890 align:start position:0% that complicated yet maker core for example<00:04:51.850> has<00:04:51.940> four<00:04:52.270> different<00:04:52.420> deployed 00:04:52.890 --> 00:04:52.900 align:start position:0% example has four different deployed 00:04:52.900 --> 00:04:55.290 align:start position:0% example has four different deployed abscess<00:04:53.410> versions<00:04:53.860> and<00:04:54.100> being<00:04:55.000> able<00:04:55.120> to 00:04:55.290 --> 00:04:55.300 align:start position:0% abscess versions and being able to 00:04:55.300 --> 00:04:56.550 align:start position:0% abscess versions and being able to reproduce<00:04:55.600> and<00:04:55.900> compile<00:04:56.110> without<00:04:56.350> having 00:04:56.550 --> 00:04:56.560 align:start position:0% reproduce and compile without having 00:04:56.560 --> 00:04:58.530 align:start position:0% reproduce and compile without having like<00:04:56.710> type<00:04:56.890> name<00:04:57.340> collisions<00:04:57.550> requires<00:04:58.240> us<00:04:58.510> to 00:04:58.530 --> 00:04:58.540 align:start position:0% like type name collisions requires us to 00:04:58.540 --> 00:04:59.730 align:start position:0% like type name collisions requires us to have<00:04:58.750> a<00:04:58.780> custom<00:04:59.110> linker<00:04:59.350> so<00:04:59.470> we're<00:04:59.560> going<00:04:59.650> to 00:04:59.730 --> 00:04:59.740 align:start position:0% have a custom linker so we're going to 00:04:59.740 --> 00:05:01.680 align:start position:0% have a custom linker so we're going to maintain<00:04:59.890> that<00:05:00.250> until<00:05:00.700> solidity<00:05:01.480> gets 00:05:01.680 --> 00:05:01.690 align:start position:0% maintain that until solidity gets 00:05:01.690 --> 00:05:07.380 align:start position:0% maintain that until solidity gets namespaces<00:05:03.660> so<00:05:05.670> after<00:05:06.670> you've<00:05:06.880> written<00:05:07.030> some 00:05:07.380 --> 00:05:07.390 align:start position:0% namespaces so after you've written some 00:05:07.390 --> 00:05:08.580 align:start position:0% namespaces so after you've written some contracts<00:05:07.810> and<00:05:07.930> you've<00:05:08.020> built<00:05:08.170> them<00:05:08.320> you 00:05:08.580 --> 00:05:08.590 align:start position:0% contracts and you've built them you 00:05:08.590 --> 00:05:10.620 align:start position:0% contracts and you've built them you obviously<00:05:08.860> want<00:05:08.980> to<00:05:09.040> test<00:05:09.190> them<00:05:09.310> and<00:05:09.630> our 00:05:10.620 --> 00:05:10.630 align:start position:0% obviously want to test them and our 00:05:10.630 --> 00:05:12.270 align:start position:0% obviously want to test them and our perspective<00:05:11.170> on<00:05:11.320> this<00:05:11.440> is<00:05:11.680> that<00:05:11.860> the<00:05:11.980> primary 00:05:12.270 --> 00:05:12.280 align:start position:0% perspective on this is that the primary 00:05:12.280 --> 00:05:14.760 align:start position:0% perspective on this is that the primary consumer<00:05:13.000> of<00:05:13.150> contracts<00:05:13.630> is<00:05:13.870> other<00:05:14.260> contracts 00:05:14.760 --> 00:05:14.770 align:start position:0% consumer of contracts is other contracts 00:05:14.770 --> 00:05:18.420 align:start position:0% consumer of contracts is other contracts and<00:05:15.130> so<00:05:15.640> we<00:05:16.260> emphasize<00:05:17.260> writing<00:05:18.010> your<00:05:18.100> test<00:05:18.310> of 00:05:18.420 --> 00:05:18.430 align:start position:0% and so we emphasize writing your test of 00:05:18.430 --> 00:05:20.010 align:start position:0% and so we emphasize writing your test of solidity<00:05:18.730> pretending<00:05:19.210> your<00:05:19.330> other<00:05:19.480> contracts 00:05:20.010 --> 00:05:20.020 align:start position:0% solidity pretending your other contracts 00:05:20.020 --> 00:05:22.380 align:start position:0% solidity pretending your other contracts in<00:05:20.410> communicating<00:05:20.950> with<00:05:20.950> it<00:05:21.190> and<00:05:21.370> for<00:05:22.210> this<00:05:22.240> we 00:05:22.380 --> 00:05:22.390 align:start position:0% in communicating with it and for this we 00:05:22.390 --> 00:05:26.160 align:start position:0% in communicating with it and for this we have<00:05:22.630> a<00:05:23.080> magic<00:05:23.470> test<00:05:23.740> contract<00:05:24.810> where<00:05:25.810> it<00:05:26.080> has 00:05:26.160 --> 00:05:26.170 align:start position:0% have a magic test contract where it has 00:05:26.170 --> 00:05:27.900 align:start position:0% have a magic test contract where it has an<00:05:26.290> Associated<00:05:26.740> harness<00:05:27.070> that<00:05:27.220> understands 00:05:27.900 --> 00:05:27.910 align:start position:0% an Associated harness that understands 00:05:27.910 --> 00:05:29.790 align:start position:0% an Associated harness that understands how<00:05:28.000> to<00:05:28.060> interpret<00:05:28.380> the<00:05:29.380> functions<00:05:29.680> defined 00:05:29.790 --> 00:05:29.800 align:start position:0% how to interpret the functions defined 00:05:29.800 --> 00:05:32.400 align:start position:0% how to interpret the functions defined on<00:05:30.070> it<00:05:30.220> so<00:05:31.000> this<00:05:31.270> is<00:05:31.420> our<00:05:31.540> first<00:05:31.780> example<00:05:31.930> of<00:05:32.350> a 00:05:32.400 --> 00:05:32.410 align:start position:0% on it so this is our first example of a 00:05:32.410 --> 00:05:35.370 align:start position:0% on it so this is our first example of a chain<00:05:33.340> for<00:05:33.370> key<00:05:33.670> so<00:05:33.790> this<00:05:33.910> this<00:05:34.360> is<00:05:34.510> an<00:05:34.750> example 00:05:35.370 --> 00:05:35.380 align:start position:0% chain for key so this this is an example 00:05:35.380 --> 00:05:37.530 align:start position:0% chain for key so this this is an example test<00:05:35.800> if<00:05:36.460> you<00:05:36.580> use<00:05:36.760> any<00:05:36.910> unit<00:05:37.300> testing 00:05:37.530 --> 00:05:37.540 align:start position:0% test if you use any unit testing 00:05:37.540 --> 00:05:39.090 align:start position:0% test if you use any unit testing framework<00:05:37.780> another<00:05:38.020> in<00:05:38.440> other<00:05:38.650> languages 00:05:39.090 --> 00:05:39.100 align:start position:0% framework another in other languages 00:05:39.100 --> 00:05:41.520 align:start position:0% framework another in other languages this<00:05:39.370> should<00:05:39.700> be<00:05:40.210> familiar<00:05:40.390> setup<00:05:41.350> gets 00:05:41.520 --> 00:05:41.530 align:start position:0% this should be familiar setup gets 00:05:41.530 --> 00:05:42.780 align:start position:0% this should be familiar setup gets called<00:05:41.770> every<00:05:42.010> time<00:05:42.220> and<00:05:42.490> then<00:05:42.580> if<00:05:42.640> you<00:05:42.700> have 00:05:42.780 --> 00:05:42.790 align:start position:0% called every time and then if you have 00:05:42.790 --> 00:05:44.400 align:start position:0% called every time and then if you have multiple<00:05:43.000> test<00:05:43.480> functions<00:05:43.870> they<00:05:44.020> each<00:05:44.230> get 00:05:44.400 --> 00:05:44.410 align:start position:0% multiple test functions they each get 00:05:44.410 --> 00:05:47.400 align:start position:0% multiple test functions they each get called<00:05:44.620> an<00:05:44.740> isolation<00:05:45.360> so<00:05:46.360> our<00:05:47.080> first<00:05:47.200> example 00:05:47.400 --> 00:05:47.410 align:start position:0% called an isolation so our first example 00:05:47.410 --> 00:05:49.560 align:start position:0% called an isolation so our first example of<00:05:47.860> a<00:05:47.980> using<00:05:48.460> chain<00:05:48.670> forking<00:05:48.970> this<00:05:49.210> is<00:05:49.360> a 00:05:49.560 --> 00:05:49.570 align:start position:0% of a using chain forking this is a 00:05:49.570 --> 00:05:51.840 align:start position:0% of a using chain forking this is a suppose<00:05:50.170> we<00:05:50.290> did<00:05:50.440> Apple<00:05:51.100> chain<00:05:51.310> new<00:05:51.520> and<00:05:51.730> use 00:05:51.840 --> 00:05:51.850 align:start position:0% suppose we did Apple chain new and use 00:05:51.850 --> 00:05:55.800 align:start position:0% suppose we did Apple chain new and use and<00:05:52.210> we<00:05:53.520> specified<00:05:54.520> the<00:05:54.640> internal<00:05:55.120> vm<00:05:55.660> which 00:05:55.800 --> 00:05:55.810 align:start position:0% and we specified the internal vm which 00:05:55.810 --> 00:05:58.740 align:start position:0% and we specified the internal vm which means<00:05:56.020> like<00:05:56.110> a<00:05:56.140> brand-new<00:05:56.920> fresh<00:05:57.370> EVM<00:05:58.000> then<00:05:58.600> we 00:05:58.740 --> 00:05:58.750 align:start position:0% means like a brand-new fresh EVM then we 00:05:58.750 --> 00:06:00.870 align:start position:0% means like a brand-new fresh EVM then we deploy<00:05:58.990> our<00:05:59.020> contract<00:05:59.590> to<00:05:59.770> it<00:05:59.890> call<00:06:00.370> setup<00:06:00.640> and 00:06:00.870 --> 00:06:00.880 align:start position:0% deploy our contract to it call setup and 00:06:00.880 --> 00:06:02.460 align:start position:0% deploy our contract to it call setup and then<00:06:00.970> concurrently<00:06:01.510> we<00:06:01.720> can<00:06:01.870> fork<00:06:02.140> it<00:06:02.290> and 00:06:02.460 --> 00:06:02.470 align:start position:0% then concurrently we can fork it and 00:06:02.470 --> 00:06:05.490 align:start position:0% then concurrently we can fork it and then<00:06:02.980> run<00:06:03.250> each<00:06:03.400> test<00:06:03.730> independently<00:06:04.500> so 00:06:05.490 --> 00:06:05.500 align:start position:0% then run each test independently so 00:06:05.500 --> 00:06:10.250 align:start position:0% then run each test independently so that's<00:06:05.680> nice<00:06:05.910> but<00:06:06.910> we<00:06:07.630> really<00:06:07.870> wanted<00:06:08.490> so<00:06:09.490> like 00:06:10.250 --> 00:06:10.260 align:start position:0% that's nice but we really wanted so like 00:06:10.260 --> 00:06:12.510 align:start position:0% that's nice but we really wanted so like part<00:06:11.260> of<00:06:11.290> the<00:06:11.350> value<00:06:11.620> of<00:06:11.710> dapple<00:06:12.040> is<00:06:12.160> that<00:06:12.400> we 00:06:12.510 --> 00:06:12.520 align:start position:0% part of the value of dapple is that we 00:06:12.520 --> 00:06:14.880 align:start position:0% part of the value of dapple is that we can<00:06:12.790> take<00:06:13.360> these<00:06:13.570> dependence<00:06:14.110> systems<00:06:14.710> and 00:06:14.880 --> 00:06:14.890 align:start position:0% can take these dependence systems and 00:06:14.890 --> 00:06:16.680 align:start position:0% can take these dependence systems and make<00:06:15.130> a<00:06:15.160> very<00:06:15.550> accurate<00:06:15.760> mock<00:06:16.180> of<00:06:16.330> them<00:06:16.480> and<00:06:16.600> we 00:06:16.680 --> 00:06:16.690 align:start position:0% make a very accurate mock of them and we 00:06:16.690 --> 00:06:17.760 align:start position:0% make a very accurate mock of them and we preserve<00:06:16.960> all<00:06:17.080> the<00:06:17.140> type<00:06:17.320> of<00:06:17.350> information<00:06:17.560> you 00:06:17.760 --> 00:06:17.770 align:start position:0% preserve all the type of information you 00:06:17.770 --> 00:06:19.020 align:start position:0% preserve all the type of information you can<00:06:17.890> be<00:06:17.950> very<00:06:18.160> certain<00:06:18.460> that<00:06:18.610> the<00:06:18.910> behavior 00:06:19.020 --> 00:06:19.030 align:start position:0% can be very certain that the behavior 00:06:19.030 --> 00:06:21.810 align:start position:0% can be very certain that the behavior will<00:06:19.810> be<00:06:19.900> similar<00:06:20.170> on<00:06:20.530> the<00:06:20.680> live<00:06:21.130> chain<00:06:21.460> and<00:06:21.700> on 00:06:21.810 --> 00:06:21.820 align:start position:0% will be similar on the live chain and on 00:06:21.820 --> 00:06:25.080 align:start position:0% will be similar on the live chain and on your<00:06:22.120> fake<00:06:22.570> local<00:06:23.110> chain<00:06:23.320> but<00:06:24.220> you<00:06:24.910> might<00:06:25.060> as 00:06:25.080 --> 00:06:25.090 align:start position:0% your fake local chain but you might as 00:06:25.090 --> 00:06:26.520 align:start position:0% your fake local chain but you might as well<00:06:25.240> just<00:06:25.450> use<00:06:25.600> the<00:06:25.720> real<00:06:25.870> thing<00:06:26.050> I<00:06:26.200> mean<00:06:26.410> it's 00:06:26.520 --> 00:06:26.530 align:start position:0% well just use the real thing I mean it's 00:06:26.530 --> 00:06:30.660 align:start position:0% well just use the real thing I mean it's even<00:06:26.710> better<00:06:26.940> so<00:06:28.080> in<00:06:29.080> this<00:06:29.230> example<00:06:29.670> basically 00:06:30.660 --> 00:06:30.670 align:start position:0% even better so in this example basically 00:06:30.670 --> 00:06:32.370 align:start position:0% even better so in this example basically you<00:06:30.910> write<00:06:31.090> a<00:06:31.120> test<00:06:31.450> and<00:06:31.660> you<00:06:31.750> assume<00:06:32.140> that<00:06:32.290> the 00:06:32.370 --> 00:06:32.380 align:start position:0% you write a test and you assume that the 00:06:32.380 --> 00:06:34.890 align:start position:0% you write a test and you assume that the contract<00:06:32.830> is<00:06:32.920> running<00:06:33.400> in<00:06:33.760> the<00:06:34.120> context<00:06:34.810> of 00:06:34.890 --> 00:06:34.900 align:start position:0% contract is running in the context of 00:06:34.900 --> 00:06:38.310 align:start position:0% contract is running in the context of like<00:06:35.110> a<00:06:35.430> chain<00:06:36.430> but<00:06:37.120> you<00:06:37.270> can<00:06:37.450> do<00:06:37.600> more<00:06:38.050> stuff 00:06:38.310 --> 00:06:38.320 align:start position:0% like a chain but you can do more stuff 00:06:38.320 --> 00:06:39.720 align:start position:0% like a chain but you can do more stuff with<00:06:38.350> it<00:06:38.530> in<00:06:38.740> your<00:06:38.860> private<00:06:39.190> context<00:06:39.580> that 00:06:39.720 --> 00:06:39.730 align:start position:0% with it in your private context that 00:06:39.730 --> 00:06:43.800 align:start position:0% with it in your private context that lets<00:06:39.910> you<00:06:40.410> test<00:06:41.410> a<00:06:41.530> few<00:06:41.650> more<00:06:41.740> features<00:06:41.920> so<00:06:42.810> to 00:06:43.800 --> 00:06:43.810 align:start position:0% lets you test a few more features so to 00:06:43.810 --> 00:06:47.220 align:start position:0% lets you test a few more features so to give<00:06:44.050> a<00:06:44.080> concrete<00:06:44.290> example<00:06:44.560> of<00:06:45.040> this<00:06:45.480> if<00:06:46.480> you 00:06:47.220 --> 00:06:47.230 align:start position:0% give a concrete example of this if you 00:06:47.230 --> 00:06:50.490 align:start position:0% give a concrete example of this if you run<00:06:47.410> this<00:06:47.740> in<00:06:48.010> the<00:06:48.280> Morton<00:06:48.669> context<00:06:49.330> this<00:06:50.290> will 00:06:50.490 --> 00:06:50.500 align:start position:0% run this in the Morton context this will 00:06:50.500 --> 00:06:52.230 align:start position:0% run this in the Morton context this will work<00:06:50.770> but<00:06:50.830> if<00:06:51.160> you<00:06:51.220> run<00:06:51.370> this<00:06:51.490> on<00:06:51.669> a<00:06:51.700> private 00:06:52.230 --> 00:06:52.240 align:start position:0% work but if you run this on a private 00:06:52.240 --> 00:06:52.999 align:start position:0% work but if you run this on a private internal 00:06:52.999 --> 00:06:53.009 align:start position:0% internal 00:06:53.009 --> 00:06:55.429 align:start position:0% internal this<00:06:53.999> won't<00:06:54.150> work<00:06:54.330> because<00:06:54.539> you<00:06:55.169> know<00:06:55.289> unless 00:06:55.429 --> 00:06:55.439 align:start position:0% this won't work because you know unless 00:06:55.439 --> 00:07:00.230 align:start position:0% this won't work because you know unless you<00:06:55.529> burn<00:06:55.770> some<00:06:55.979> ether<00:06:56.879> first<00:06:57.150> so<00:06:57.839> I<00:06:59.240> should 00:07:00.230 --> 00:07:00.240 align:start position:0% you burn some ether first so I should 00:07:00.240 --> 00:07:01.879 align:start position:0% you burn some ether first so I should have<00:07:00.330> like<00:07:00.509> written<00:07:01.169> the<00:07:01.289> usage<00:07:01.589> behind<00:07:01.830> this 00:07:01.879 --> 00:07:01.889 align:start position:0% have like written the usage behind this 00:07:01.889 --> 00:07:03.739 align:start position:0% have like written the usage behind this but<00:07:02.039> basically<00:07:02.279> what<00:07:02.460> happens<00:07:02.699> is<00:07:02.789> first<00:07:03.449> you 00:07:03.739 --> 00:07:03.749 align:start position:0% but basically what happens is first you 00:07:03.749 --> 00:07:06.200 align:start position:0% but basically what happens is first you enter<00:07:04.499> the<00:07:04.619> answer<00:07:05.069> the<00:07:05.249> Morton<00:07:05.550> context<00:07:06.119> and 00:07:06.200 --> 00:07:06.210 align:start position:0% enter the answer the Morton context and 00:07:06.210 --> 00:07:08.779 align:start position:0% enter the answer the Morton context and then<00:07:06.360> you<00:07:06.449> do<00:07:06.569> dapple<00:07:06.899> test<00:07:07.169> on<00:07:07.409> this<00:07:07.949> contract 00:07:08.779 --> 00:07:08.789 align:start position:0% then you do dapple test on this contract 00:07:08.789 --> 00:07:11.839 align:start position:0% then you do dapple test on this contract and<00:07:09.029> the<00:07:09.119> result<00:07:09.449> is<00:07:09.659> that<00:07:09.719> it<00:07:10.529> works<00:07:10.849> this 00:07:11.839 --> 00:07:11.849 align:start position:0% and the result is that it works this 00:07:11.849 --> 00:07:15.499 align:start position:0% and the result is that it works this address<00:07:12.300> zero<00:07:12.619> refers<00:07:13.619> to<00:07:14.149> address<00:07:15.149> your<00:07:15.360> own 00:07:15.499 --> 00:07:15.509 align:start position:0% address zero refers to address your own 00:07:15.509 --> 00:07:17.899 align:start position:0% address zero refers to address your own morden<00:07:15.899> and<00:07:16.080> so<00:07:16.499> when<00:07:17.189> you<00:07:17.399> assert<00:07:17.699> that<00:07:17.729> the 00:07:17.899 --> 00:07:17.909 align:start position:0% morden and so when you assert that the 00:07:17.909 --> 00:07:19.639 align:start position:0% morden and so when you assert that the burned<00:07:18.119> balance<00:07:18.509> is<00:07:18.629> more<00:07:18.809> than<00:07:18.899> zero<00:07:19.139> it's 00:07:19.639 --> 00:07:19.649 align:start position:0% burned balance is more than zero it's 00:07:19.649 --> 00:07:22.399 align:start position:0% burned balance is more than zero it's true<00:07:20.330> all<00:07:21.330> right<00:07:21.509> so<00:07:21.659> testing<00:07:22.080> is<00:07:22.169> kind<00:07:22.349> of 00:07:22.399 --> 00:07:22.409 align:start position:0% true all right so testing is kind of 00:07:22.409 --> 00:07:23.480 align:start position:0% true all right so testing is kind of interesting<00:07:22.529> but<00:07:22.860> it<00:07:23.129> gets<00:07:23.249> really 00:07:23.480 --> 00:07:23.490 align:start position:0% interesting but it gets really 00:07:23.490 --> 00:07:25.850 align:start position:0% interesting but it gets really interesting<00:07:23.610> when<00:07:24.149> we<00:07:24.300> want<00:07:24.479> to<00:07:24.860> deploy 00:07:25.850 --> 00:07:25.860 align:start position:0% interesting when we want to deploy 00:07:25.860 --> 00:07:27.320 align:start position:0% interesting when we want to deploy contracts<00:07:26.580> which<00:07:26.759> is<00:07:26.879> one<00:07:27.089> of<00:07:27.210> the 00:07:27.320 --> 00:07:27.330 align:start position:0% contracts which is one of the 00:07:27.330 --> 00:07:28.579 align:start position:0% contracts which is one of the applications<00:07:27.479> of<00:07:27.930> what<00:07:28.020> we<00:07:28.080> called<00:07:28.259> wallet 00:07:28.579 --> 00:07:28.589 align:start position:0% applications of what we called wallet 00:07:28.589 --> 00:07:31.399 align:start position:0% applications of what we called wallet side<00:07:28.770> scripting<00:07:29.249> which<00:07:29.939> is<00:07:30.120> another<00:07:30.409> magic 00:07:31.399 --> 00:07:31.409 align:start position:0% side scripting which is another magic 00:07:31.409 --> 00:07:34.249 align:start position:0% side scripting which is another magic EVM<00:07:31.909> contract<00:07:32.909> but<00:07:32.999> it's<00:07:33.210> harness<00:07:33.689> has 00:07:34.249 --> 00:07:34.259 align:start position:0% EVM contract but it's harness has 00:07:34.259 --> 00:07:36.260 align:start position:0% EVM contract but it's harness has hijacked<00:07:34.800> that<00:07:34.919> creates<00:07:35.249> and<00:07:35.460> call<00:07:35.729> off<00:07:35.969> codes 00:07:36.260 --> 00:07:36.270 align:start position:0% hijacked that creates and call off codes 00:07:36.270 --> 00:07:39.170 align:start position:0% hijacked that creates and call off codes and<00:07:36.509> makes<00:07:37.069> instead<00:07:38.069> what<00:07:38.399> usually<00:07:38.610> when<00:07:39.089> you 00:07:39.170 --> 00:07:39.180 align:start position:0% and makes instead what usually when you 00:07:39.180 --> 00:07:40.579 align:start position:0% and makes instead what usually when you have<00:07:39.509> payer<00:07:39.719> call<00:07:39.960> it<00:07:40.050> creates<00:07:40.229> a<00:07:40.289> message 00:07:40.579 --> 00:07:40.589 align:start position:0% have payer call it creates a message 00:07:40.589 --> 00:07:42.200 align:start position:0% have payer call it creates a message costs<00:07:40.949> like<00:07:41.129> internal<00:07:41.490> to<00:07:41.699> one<00:07:41.849> transaction 00:07:42.200 --> 00:07:42.210 align:start position:0% costs like internal to one transaction 00:07:42.210 --> 00:07:43.820 align:start position:0% costs like internal to one transaction but<00:07:42.930> instead<00:07:43.139> what<00:07:43.289> we<00:07:43.379> do<00:07:43.469> is<00:07:43.620> actually 00:07:43.820 --> 00:07:43.830 align:start position:0% but instead what we do is actually 00:07:43.830 --> 00:07:45.739 align:start position:0% but instead what we do is actually create<00:07:44.279> a<00:07:44.309> full<00:07:44.610> transaction<00:07:45.209> and<00:07:45.360> then<00:07:45.449> block 00:07:45.739 --> 00:07:45.749 align:start position:0% create a full transaction and then block 00:07:45.749 --> 00:07:47.839 align:start position:0% create a full transaction and then block the<00:07:45.930> wall<00:07:46.050> outside<00:07:46.199> EVM<00:07:46.620> execution<00:07:47.159> until<00:07:47.399> it 00:07:47.839 --> 00:07:47.849 align:start position:0% the wall outside EVM execution until it 00:07:47.849 --> 00:07:51.350 align:start position:0% the wall outside EVM execution until it gets<00:07:47.969> confirmed<00:07:49.219> you<00:07:50.219> combine<00:07:50.610> this<00:07:50.789> with<00:07:51.029> the 00:07:51.350 --> 00:07:51.360 align:start position:0% gets confirmed you combine this with the 00:07:51.360 --> 00:07:53.299 align:start position:0% gets confirmed you combine this with the chain<00:07:51.569> forking<00:07:51.930> feature<00:07:52.080> what<00:07:52.680> you<00:07:52.770> can<00:07:52.919> do<00:07:53.069> is 00:07:53.299 --> 00:07:53.309 align:start position:0% chain forking feature what you can do is 00:07:53.309 --> 00:07:54.980 align:start position:0% chain forking feature what you can do is simulate<00:07:53.729> live<00:07:54.089> deployments<00:07:54.689> before<00:07:54.930> you 00:07:54.980 --> 00:07:54.990 align:start position:0% simulate live deployments before you 00:07:54.990 --> 00:07:56.659 align:start position:0% simulate live deployments before you actually<00:07:55.139> do<00:07:55.409> them<00:07:55.559> do<00:07:55.830> dry<00:07:56.099> runs<00:07:56.339> and<00:07:56.550> then 00:07:56.659 --> 00:07:56.669 align:start position:0% actually do them do dry runs and then 00:07:56.669 --> 00:07:58.369 align:start position:0% actually do them do dry runs and then you<00:07:56.789> can<00:07:56.939> run<00:07:57.149> consistency<00:07:57.719> checks<00:07:57.990> on<00:07:58.199> the 00:07:58.369 --> 00:07:58.379 align:start position:0% you can run consistency checks on the 00:07:58.379 --> 00:08:00.079 align:start position:0% you can run consistency checks on the results<00:07:58.680> of<00:07:58.709> your<00:07:58.770> system<00:07:59.189> like<00:07:59.370> make<00:07:59.909> sure 00:08:00.079 --> 00:08:00.089 align:start position:0% results of your system like make sure 00:08:00.089 --> 00:08:01.670 align:start position:0% results of your system like make sure that<00:08:00.240> you're<00:08:00.569> up<00:08:00.599> the<00:08:00.899> update<00:08:01.379> that<00:08:01.499> you<00:08:01.559> want 00:08:01.670 --> 00:08:01.680 align:start position:0% that you're up the update that you want 00:08:01.680 --> 00:08:04.309 align:start position:0% that you're up the update that you want to<00:08:01.740> do<00:08:01.830> it<00:08:02.729> doesn't<00:08:03.029> screw<00:08:03.180> anything<00:08:03.360> up<00:08:03.509> so 00:08:04.309 --> 00:08:04.319 align:start position:0% to do it doesn't screw anything up so 00:08:04.319 --> 00:08:06.409 align:start position:0% to do it doesn't screw anything up so here's<00:08:05.129> a<00:08:05.189> real<00:08:05.339> world<00:08:05.520> example<00:08:05.639> of<00:08:06.059> like<00:08:06.180> we 00:08:06.409 --> 00:08:06.419 align:start position:0% here's a real world example of like we 00:08:06.419 --> 00:08:08.719 align:start position:0% here's a real world example of like we want<00:08:06.689> we<00:08:07.199> might<00:08:07.229> want<00:08:07.409> to<00:08:07.680> do<00:08:07.770> this<00:08:07.919> you're<00:08:08.639> on 00:08:08.719 --> 00:08:08.729 align:start position:0% want we might want to do this you're on 00:08:08.729 --> 00:08:10.100 align:start position:0% want we might want to do this you're on slack<00:08:09.029> and<00:08:09.209> you<00:08:09.269> get<00:08:09.360> a<00:08:09.389> message<00:08:09.509> for<00:08:09.839> me<00:08:09.870> that 00:08:10.100 --> 00:08:10.110 align:start position:0% slack and you get a message for me that 00:08:10.110 --> 00:08:12.649 align:start position:0% slack and you get a message for me that says<00:08:10.259> hey<00:08:10.379> please<00:08:10.769> confirm<00:08:11.129> proposal<00:08:11.669> 66<00:08:12.240> it 00:08:12.649 --> 00:08:12.659 align:start position:0% says hey please confirm proposal 66 it 00:08:12.659 --> 00:08:14.149 align:start position:0% says hey please confirm proposal 66 it is<00:08:12.809> a<00:08:12.839> critical<00:08:13.259> bug<00:08:13.379> fix<00:08:13.589> it's<00:08:13.769> going<00:08:13.889> to<00:08:13.949> swap 00:08:14.149 --> 00:08:14.159 align:start position:0% is a critical bug fix it's going to swap 00:08:14.159 --> 00:08:15.860 align:start position:0% is a critical bug fix it's going to swap out<00:08:14.309> some<00:08:14.519> of<00:08:14.580> the<00:08:14.639> contracts<00:08:15.059> this<00:08:15.240> ones<00:08:15.479> that 00:08:15.860 --> 00:08:15.870 align:start position:0% out some of the contracts this ones that 00:08:15.870 --> 00:08:18.799 align:start position:0% out some of the contracts this ones that have<00:08:16.589> don't<00:08:17.009> have<00:08:17.129> this<00:08:17.219> book<00:08:17.339> so<00:08:18.089> if<00:08:18.569> you're<00:08:18.779> a 00:08:18.799 --> 00:08:18.809 align:start position:0% have don't have this book so if you're a 00:08:18.809 --> 00:08:20.959 align:start position:0% have don't have this book so if you're a responsible<00:08:19.459> administer<00:08:20.459> of<00:08:20.519> multi<00:08:20.789> sig 00:08:20.959 --> 00:08:20.969 align:start position:0% responsible administer of multi sig 00:08:20.969 --> 00:08:22.429 align:start position:0% responsible administer of multi sig folder<00:08:21.269> of<00:08:21.389> whatever<00:08:21.659> system<00:08:21.899> you're<00:08:22.110> running 00:08:22.429 --> 00:08:22.439 align:start position:0% folder of whatever system you're running 00:08:22.439 --> 00:08:25.820 align:start position:0% folder of whatever system you're running you<00:08:22.860> will<00:08:23.039> of<00:08:23.189> course<00:08:23.479> do<00:08:24.479> a<00:08:24.509> mock<00:08:24.809> chain<00:08:25.469> fork 00:08:25.820 --> 00:08:25.830 align:start position:0% you will of course do a mock chain fork 00:08:25.830 --> 00:08:28.969 align:start position:0% you will of course do a mock chain fork and<00:08:26.209> run<00:08:27.209> this<00:08:27.559> transaction<00:08:28.559> a<00:08:28.620> simulated 00:08:28.969 --> 00:08:28.979 align:start position:0% and run this transaction a simulated 00:08:28.979 --> 00:08:30.259 align:start position:0% and run this transaction a simulated environment<00:08:29.399> to<00:08:29.490> make<00:08:29.639> sure<00:08:29.819> that<00:08:29.969> it<00:08:30.059> still 00:08:30.259 --> 00:08:30.269 align:start position:0% environment to make sure that it still 00:08:30.269 --> 00:08:32.180 align:start position:0% environment to make sure that it still passes<00:08:30.659> whatever<00:08:30.930> consistency<00:08:31.439> checks<00:08:31.740> you 00:08:32.180 --> 00:08:32.190 align:start position:0% passes whatever consistency checks you 00:08:32.190 --> 00:08:34.430 align:start position:0% passes whatever consistency checks you guys<00:08:32.370> have<00:08:32.579> defined<00:08:32.940> in<00:08:33.240> our<00:08:33.659> case<00:08:33.899> let<00:08:34.380> me 00:08:34.430 --> 00:08:34.440 align:start position:0% guys have defined in our case let me 00:08:34.440 --> 00:08:40.100 align:start position:0% guys have defined in our case let me show<00:08:34.620> you<00:08:34.680> the<00:08:34.860> example<00:08:36.199> so<00:08:37.199> this<00:08:37.919> is<00:08:38.099> why<00:08:39.110> this 00:08:40.100 --> 00:08:40.110 align:start position:0% show you the example so this is why this 00:08:40.110 --> 00:08:43.159 align:start position:0% show you the example so this is why this this<00:08:40.529> type<00:08:40.979> information<00:08:42.079> preserving<00:08:43.079> this 00:08:43.159 --> 00:08:43.169 align:start position:0% this type information preserving this 00:08:43.169 --> 00:08:44.870 align:start position:0% this type information preserving this type<00:08:43.349> of<00:08:43.380> information<00:08:43.560> in<00:08:43.979> the<00:08:44.159> default<00:08:44.550> is<00:08:44.699> so 00:08:44.870 --> 00:08:44.880 align:start position:0% type of information in the default is so 00:08:44.880 --> 00:08:46.400 align:start position:0% type of information in the default is so powerful<00:08:45.060> is<00:08:45.389> that<00:08:45.420> then<00:08:45.660> we<00:08:45.779> can<00:08:45.810> hoist<00:08:46.170> it 00:08:46.400 --> 00:08:46.410 align:start position:0% powerful is that then we can hoist it 00:08:46.410 --> 00:08:48.710 align:start position:0% powerful is that then we can hoist it into<00:08:47.220> the<00:08:47.940> wallet<00:08:48.209> side<00:08:48.360> scripting 00:08:48.710 --> 00:08:48.720 align:start position:0% into the wallet side scripting 00:08:48.720 --> 00:08:50.240 align:start position:0% into the wallet side scripting environment<00:08:48.839> and<00:08:49.319> have<00:08:49.500> the<00:08:49.680> full<00:08:49.949> type 00:08:50.240 --> 00:08:50.250 align:start position:0% environment and have the full type 00:08:50.250 --> 00:08:52.340 align:start position:0% environment and have the full type system<00:08:50.670> there<00:08:50.870> with<00:08:51.870> all<00:08:52.050> the<00:08:52.170> type<00:08:52.319> of 00:08:52.340 --> 00:08:52.350 align:start position:0% system there with all the type of 00:08:52.350 --> 00:08:55.009 align:start position:0% system there with all the type of immunities<00:08:52.860> to<00:08:52.889> make<00:08:53.160> sure<00:08:53.310> that<00:08:53.579> this<00:08:54.019> you 00:08:55.009 --> 00:08:55.019 align:start position:0% immunities to make sure that this you 00:08:55.019 --> 00:08:55.910 align:start position:0% immunities to make sure that this you know<00:08:55.110> what<00:08:55.260> you're<00:08:55.380> doing<00:08:55.560> makes<00:08:55.680> sense 00:08:55.910 --> 00:08:55.920 align:start position:0% know what you're doing makes sense 00:08:55.920 --> 00:08:57.559 align:start position:0% know what you're doing makes sense there's<00:08:56.100> actually<00:08:56.459> a<00:08:56.490> token<00:08:56.880> defined<00:08:57.420> in<00:08:57.510> the 00:08:57.559 --> 00:08:57.569 align:start position:0% there's actually a token defined in the 00:08:57.569 --> 00:08:59.120 align:start position:0% there's actually a token defined in the environment<00:08:57.779> it's<00:08:58.110> actually<00:08:58.470> typed<00:08:58.889> as<00:08:59.100> a 00:08:59.120 --> 00:08:59.130 align:start position:0% environment it's actually typed as a 00:08:59.130 --> 00:09:00.920 align:start position:0% environment it's actually typed as a token<00:08:59.370> it<00:08:59.610> has<00:08:59.699> a<00:08:59.730> confirmed<00:09:00.120> puncturing<00:09:00.510> blah 00:09:00.920 --> 00:09:00.930 align:start position:0% token it has a confirmed puncturing blah 00:09:00.930 --> 00:09:03.050 align:start position:0% token it has a confirmed puncturing blah blah<00:09:01.019> blah<00:09:01.170> and<00:09:02.100> so<00:09:02.250> in<00:09:02.370> this<00:09:02.459> case<00:09:02.639> what<00:09:02.910> we're 00:09:03.050 --> 00:09:03.060 align:start position:0% blah blah and so in this case what we're 00:09:03.060 --> 00:09:04.670 align:start position:0% blah blah and so in this case what we're doing<00:09:03.360> is<00:09:03.510> we're<00:09:03.899> confirming<00:09:04.230> it's<00:09:04.470> from<00:09:04.620> our 00:09:04.670 --> 00:09:04.680 align:start position:0% doing is we're confirming it's from our 00:09:04.680 --> 00:09:05.810 align:start position:0% doing is we're confirming it's from our address<00:09:05.010> but<00:09:05.189> then<00:09:05.279> we're<00:09:05.430> fit 00:09:05.810 --> 00:09:05.820 align:start position:0% address but then we're fit 00:09:05.820 --> 00:09:08.090 align:start position:0% address but then we're fit tending<00:09:06.120> to<00:09:06.570> set<00:09:06.780> the<00:09:06.870> origin<00:09:07.320> to<00:09:07.650> a<00:09:07.680> different 00:09:08.090 --> 00:09:08.100 align:start position:0% tending to set the origin to a different 00:09:08.100 --> 00:09:09.260 align:start position:0% tending to set the origin to a different address<00:09:08.130> which<00:09:08.490> is<00:09:08.520> one<00:09:08.790> of<00:09:08.820> the<00:09:08.940> magic 00:09:09.260 --> 00:09:09.270 align:start position:0% address which is one of the magic 00:09:09.270 --> 00:09:11.480 align:start position:0% address which is one of the magic features<00:09:09.630> of<00:09:09.840> the<00:09:09.930> script<00:09:10.200> contract<00:09:10.560> so<00:09:11.460> that 00:09:11.480 --> 00:09:11.490 align:start position:0% features of the script contract so that 00:09:11.490 --> 00:09:14.090 align:start position:0% features of the script contract so that the<00:09:11.760> origin<00:09:12.240> is<00:09:12.450> mocked<00:09:12.750> then<00:09:13.590> we<00:09:13.920> do<00:09:14.070> a 00:09:14.090 --> 00:09:14.100 align:start position:0% the origin is mocked then we do a 00:09:14.100 --> 00:09:16.250 align:start position:0% the origin is mocked then we do a confirmation<00:09:14.760> from<00:09:14.940> that<00:09:15.120> origin<00:09:15.510> and<00:09:15.690> then 00:09:16.250 --> 00:09:16.260 align:start position:0% confirmation from that origin and then 00:09:16.260 --> 00:09:18.620 align:start position:0% confirmation from that origin and then we<00:09:16.410> show<00:09:17.130> in<00:09:17.220> this<00:09:17.250> example<00:09:17.670> to<00:09:17.910> confirm<00:09:18.300> also 00:09:18.620 --> 00:09:18.630 align:start position:0% we show in this example to confirm also 00:09:18.630 --> 00:09:20.780 align:start position:0% we show in this example to confirm also does<00:09:18.750> the<00:09:18.780> trigger<00:09:19.110> so<00:09:19.470> the<00:09:19.890> update<00:09:20.220> runs<00:09:20.460> and 00:09:20.780 --> 00:09:20.790 align:start position:0% does the trigger so the update runs and 00:09:20.790 --> 00:09:22.730 align:start position:0% does the trigger so the update runs and then<00:09:21.030> we<00:09:21.120> do<00:09:21.210> a<00:09:21.240> consistency<00:09:21.780> check<00:09:21.810> and<00:09:22.260> in 00:09:22.730 --> 00:09:22.740 align:start position:0% then we do a consistency check and in 00:09:22.740 --> 00:09:25.070 align:start position:0% then we do a consistency check and in this<00:09:22.920> example<00:09:23.280> you<00:09:23.490> can<00:09:23.520> see<00:09:23.670> our<00:09:24.090> maid<00:09:24.960> of 00:09:25.070 --> 00:09:25.080 align:start position:0% this example you can see our maid of 00:09:25.080 --> 00:09:27.200 align:start position:0% this example you can see our maid of consistency<00:09:25.650> check<00:09:25.890> failed<00:09:26.220> so<00:09:26.820> you<00:09:26.880> know 00:09:27.200 --> 00:09:27.210 align:start position:0% consistency check failed so you know 00:09:27.210 --> 00:09:28.640 align:start position:0% consistency check failed so you know that<00:09:27.390> this<00:09:27.480> wasn't<00:09:27.690> actually<00:09:28.110> me<00:09:28.260> this<00:09:28.500> was 00:09:28.640 --> 00:09:28.650 align:start position:0% that this wasn't actually me this was 00:09:28.650 --> 00:09:30.320 align:start position:0% that this wasn't actually me this was some<00:09:28.890> hacker<00:09:29.100> that<00:09:29.250> is<00:09:29.490> trying<00:09:29.730> to<00:09:29.850> run<00:09:30.000> a<00:09:30.030> bad 00:09:30.320 --> 00:09:30.330 align:start position:0% some hacker that is trying to run a bad 00:09:30.330 --> 00:09:32.660 align:start position:0% some hacker that is trying to run a bad update<00:09:30.690> on<00:09:30.840> the<00:09:30.930> system<00:09:31.230> but<00:09:31.620> each<00:09:31.830> multi<00:09:32.520> sig 00:09:32.660 --> 00:09:32.670 align:start position:0% update on the system but each multi sig 00:09:32.670 --> 00:09:34.400 align:start position:0% update on the system but each multi sig member<00:09:32.850> can<00:09:32.970> easily<00:09:33.390> independently<00:09:33.930> verify 00:09:34.400 --> 00:09:34.410 align:start position:0% member can easily independently verify 00:09:34.410 --> 00:09:35.990 align:start position:0% member can easily independently verify what<00:09:34.680> the<00:09:34.800> resulting<00:09:35.250> state<00:09:35.550> of<00:09:35.730> actually 00:09:35.990 --> 00:09:36.000 align:start position:0% what the resulting state of actually 00:09:36.000 --> 00:09:40.030 align:start position:0% what the resulting state of actually running<00:09:36.270> those<00:09:36.540> transactions<00:09:37.200> are<00:09:38.720> all<00:09:39.720> right 00:09:40.030 --> 00:09:40.040 align:start position:0% running those transactions are all right 00:09:40.040 --> 00:09:43.700 align:start position:0% running those transactions are all right and<00:09:41.040> then<00:09:41.880> the<00:09:41.970> final<00:09:42.000> step<00:09:42.390> is<00:09:42.840> publish<00:09:43.560> your 00:09:43.700 --> 00:09:43.710 align:start position:0% and then the final step is publish your 00:09:43.710 --> 00:09:45.950 align:start position:0% and then the final step is publish your job<00:09:43.950> file<00:09:44.160> yet<00:09:44.520> other<00:09:44.760> people<00:09:45.270> to<00:09:45.300> import<00:09:45.840> your 00:09:45.950 --> 00:09:45.960 align:start position:0% job file yet other people to import your 00:09:45.960 --> 00:09:47.690 align:start position:0% job file yet other people to import your code<00:09:46.230> and<00:09:46.260> have<00:09:46.710> some<00:09:46.890> code<00:09:47.100> reuse<00:09:47.280> because 00:09:47.690 --> 00:09:47.700 align:start position:0% code and have some code reuse because 00:09:47.700 --> 00:09:49.310 align:start position:0% code and have some code reuse because there's<00:09:47.940> so<00:09:48.150> much<00:09:48.360> duplication<00:09:48.690> of<00:09:49.080> effort 00:09:49.310 --> 00:09:49.320 align:start position:0% there's so much duplication of effort 00:09:49.320 --> 00:09:50.540 align:start position:0% there's so much duplication of effort going<00:09:49.440> on<00:09:49.620> in<00:09:49.680> the<00:09:49.740> ecosystem<00:09:49.890> right<00:09:50.280> now<00:09:50.400> is 00:09:50.540 --> 00:09:50.550 align:start position:0% going on in the ecosystem right now is 00:09:50.550 --> 00:09:51.980 align:start position:0% going on in the ecosystem right now is partially<00:09:51.120> because<00:09:51.240> it's<00:09:51.450> just<00:09:51.510> so<00:09:51.630> hard<00:09:51.930> to 00:09:51.980 --> 00:09:51.990 align:start position:0% partially because it's just so hard to 00:09:51.990 --> 00:09:55.760 align:start position:0% partially because it's just so hard to reuse<00:09:52.380> other<00:09:52.560> people's<00:09:52.800> code<00:09:54.290> so<00:09:55.290> I'm<00:09:55.620> going 00:09:55.760 --> 00:09:55.770 align:start position:0% reuse other people's code so I'm going 00:09:55.770 --> 00:09:57.980 align:start position:0% reuse other people's code so I'm going to<00:09:55.800> very<00:09:56.220> quickly<00:09:56.520> give<00:09:57.270> very<00:09:57.510> small<00:09:57.780> sneak 00:09:57.980 --> 00:09:57.990 align:start position:0% to very quickly give very small sneak 00:09:57.990 --> 00:09:59.120 align:start position:0% to very quickly give very small sneak peak<00:09:58.140> about<00:09:58.440> what<00:09:58.680> are<00:09:58.800> some<00:09:58.950> other<00:09:59.100> things 00:09:59.120 --> 00:09:59.130 align:start position:0% peak about what are some other things 00:09:59.130 --> 00:10:01.310 align:start position:0% peak about what are some other things that<00:09:59.400> are<00:09:59.550> coming<00:09:59.730> basically<00:10:00.450> all<00:10:00.810> the<00:10:01.140> things 00:10:01.310 --> 00:10:01.320 align:start position:0% that are coming basically all the things 00:10:01.320 --> 00:10:03.980 align:start position:0% that are coming basically all the things I<00:10:01.440> described<00:10:01.830> could<00:10:02.100> be<00:10:02.220> done<00:10:02.400> in<00:10:02.580> a<00:10:02.760> GUI<00:10:02.990> so 00:10:03.980 --> 00:10:03.990 align:start position:0% I described could be done in a GUI so 00:10:03.990 --> 00:10:06.440 align:start position:0% I described could be done in a GUI so you<00:10:04.080> could<00:10:04.530> you<00:10:05.490> know<00:10:05.580> do<00:10:05.760> your<00:10:05.940> own<00:10:06.090> the<00:10:06.300> Dow 00:10:06.440 --> 00:10:06.450 align:start position:0% you could you know do your own the Dow 00:10:06.450 --> 00:10:09.260 align:start position:0% you could you know do your own the Dow hack<00:10:06.750> through<00:10:07.050> a<00:10:07.110> through<00:10:07.560> a<00:10:07.620> clicky<00:10:07.890> you<00:10:08.340> I<00:10:08.370> if 00:10:09.260 --> 00:10:09.270 align:start position:0% hack through a through a clicky you I if 00:10:09.270 --> 00:10:13.730 align:start position:0% hack through a through a clicky you I if you<00:10:09.420> want<00:10:09.600> to<00:10:10.580> let's<00:10:11.580> and<00:10:12.090> then<00:10:12.990> some<00:10:13.560> more 00:10:13.730 --> 00:10:13.740 align:start position:0% you want to let's and then some more 00:10:13.740 --> 00:10:15.530 align:start position:0% you want to let's and then some more things<00:10:14.040> that<00:10:14.100> we<00:10:14.250> have<00:10:14.370> in<00:10:14.430> the<00:10:14.550> pipeline<00:10:14.700> a 00:10:15.530 --> 00:10:15.540 align:start position:0% things that we have in the pipeline a 00:10:15.540 --> 00:10:18.680 align:start position:0% things that we have in the pipeline a better<00:10:16.130> more<00:10:17.130> wallets<00:10:17.790> I<00:10:17.910> DVM<00:10:18.270> extension 00:10:18.680 --> 00:10:18.690 align:start position:0% better more wallets I DVM extension 00:10:18.690 --> 00:10:21.680 align:start position:0% better more wallets I DVM extension features<00:10:19.050> so<00:10:19.350> one<00:10:19.650> thing<00:10:19.860> is<00:10:19.920> uh<00:10:20.300> having<00:10:21.300> one 00:10:21.680 --> 00:10:21.690 align:start position:0% features so one thing is uh having one 00:10:21.690 --> 00:10:23.720 align:start position:0% features so one thing is uh having one of<00:10:21.720> the<00:10:21.960> addresses<00:10:22.680> be<00:10:23.100> like<00:10:23.280> a<00:10:23.310> hard-coded 00:10:23.720 --> 00:10:23.730 align:start position:0% of the addresses be like a hard-coded 00:10:23.730 --> 00:10:25.910 align:start position:0% of the addresses be like a hard-coded contract<00:10:24.300> which<00:10:24.420> is<00:10:24.540> a<00:10:24.570> thin<00:10:24.780> client<00:10:25.140> and<00:10:25.260> so 00:10:25.910 --> 00:10:25.920 align:start position:0% contract which is a thin client and so 00:10:25.920 --> 00:10:27.590 align:start position:0% contract which is a thin client and so this<00:10:26.190> is<00:10:26.280> call<00:10:26.430> i<00:10:26.460> call<00:10:26.670> it<00:10:26.760> DIY<00:10:27.090> sharding 00:10:27.590 --> 00:10:27.600 align:start position:0% this is call i call it DIY sharding 00:10:27.600 --> 00:10:29.240 align:start position:0% this is call i call it DIY sharding basically<00:10:28.080> if<00:10:28.350> you<00:10:28.440> have<00:10:28.560> to<00:10:28.710> private<00:10:29.010> chains 00:10:29.240 --> 00:10:29.250 align:start position:0% basically if you have to private chains 00:10:29.250 --> 00:10:30.770 align:start position:0% basically if you have to private chains you<00:10:29.460> can<00:10:29.580> make<00:10:29.730> up<00:10:29.850> your<00:10:29.880> own<00:10:30.000> interpret<00:10:30.690> and 00:10:30.770 --> 00:10:30.780 align:start position:0% you can make up your own interpret and 00:10:30.780 --> 00:10:32.120 align:start position:0% you can make up your own interpret and communication<00:10:31.230> scheme<00:10:31.410> very<00:10:31.590> easily<00:10:31.740> if<00:10:32.010> you 00:10:32.120 --> 00:10:32.130 align:start position:0% communication scheme very easily if you 00:10:32.130 --> 00:10:34.910 align:start position:0% communication scheme very easily if you have<00:10:32.870> the<00:10:33.870> thin<00:10:34.020> clients<00:10:34.440> for<00:10:34.710> the<00:10:34.770> other 00:10:34.910 --> 00:10:34.920 align:start position:0% have the thin clients for the other 00:10:34.920 --> 00:10:37.070 align:start position:0% have the thin clients for the other chain<00:10:35.160> as<00:10:35.340> a<00:10:35.370> like<00:10:35.970> EDM<00:10:36.300> extension<00:10:36.810> or<00:10:36.900> like<00:10:37.050> a 00:10:37.070 --> 00:10:37.080 align:start position:0% chain as a like EDM extension or like a 00:10:37.080 --> 00:10:40.880 align:start position:0% chain as a like EDM extension or like a hard-coded<00:10:37.440> contract<00:10:37.950> likewise<00:10:39.890> creating 00:10:40.880 --> 00:10:40.890 align:start position:0% hard-coded contract likewise creating 00:10:40.890 --> 00:10:43.240 align:start position:0% hard-coded contract likewise creating like<00:10:41.010> a<00:10:41.040> mint<00:10:41.340> opcode<00:10:41.760> would<00:10:42.300> allow<00:10:42.480> you<00:10:42.540> to 00:10:43.240 --> 00:10:43.250 align:start position:0% like a mint opcode would allow you to 00:10:43.250 --> 00:10:45.740 align:start position:0% like a mint opcode would allow you to write<00:10:44.250> your<00:10:44.280> private<00:10:44.910> chains<00:10:45.150> consensus 00:10:45.740 --> 00:10:45.750 align:start position:0% write your private chains consensus 00:10:45.750 --> 00:10:50.030 align:start position:0% write your private chains consensus mechanism<00:10:46.260> in<00:10:46.440> the<00:10:46.470> evm<00:10:46.980> and<00:10:47.240> finally<00:10:49.040> system 00:10:50.030 --> 00:10:50.040 align:start position:0% mechanism in the evm and finally system 00:10:50.040 --> 00:10:52.190 align:start position:0% mechanism in the evm and finally system calls<00:10:50.250> allow<00:10:50.610> you<00:10:51.210> to<00:10:51.420> bridge<00:10:51.660> the<00:10:51.840> old<00:10:52.020> world 00:10:52.190 --> 00:10:52.200 align:start position:0% calls allow you to bridge the old world 00:10:52.200 --> 00:10:55.910 align:start position:0% calls allow you to bridge the old world web<00:10:52.500> with<00:10:52.860> the<00:10:53.780> new<00:10:54.780> world<00:10:54.990> you<00:10:55.560> know<00:10:55.680> thin 00:10:55.910 --> 00:10:55.920 align:start position:0% web with the new world you know thin 00:10:55.920 --> 00:10:57.800 align:start position:0% web with the new world you know thin proofs<00:10:56.220> for<00:10:56.400> everything<00:10:56.760> and<00:10:57.450> you<00:10:57.570> can<00:10:57.690> have 00:10:57.800 --> 00:10:57.810 align:start position:0% proofs for everything and you can have 00:10:57.810 --> 00:10:59.900 align:start position:0% proofs for everything and you can have like<00:10:57.960> a<00:10:57.990> dedicated<00:10:58.440> side<00:10:59.190> chain<00:10:59.520> that<00:10:59.700> say 00:10:59.900 --> 00:10:59.910 align:start position:0% like a dedicated side chain that say 00:10:59.910 --> 00:11:02.300 align:start position:0% like a dedicated side chain that say does<00:11:00.240> SMS<00:11:01.080> relay<00:11:01.470> like<00:11:01.680> this<00:11:01.830> is<00:11:01.950> the<00:11:02.040> example 00:11:02.300 --> 00:11:02.310 align:start position:0% does SMS relay like this is the example 00:11:02.310 --> 00:11:04.460 align:start position:0% does SMS relay like this is the example we<00:11:02.550> have<00:11:02.700> right<00:11:02.910> so<00:11:03.090> it<00:11:03.450> does<00:11:03.660> this<00:11:03.810> it<00:11:04.290> does 00:11:04.460 --> 00:11:04.470 align:start position:0% we have right so it does this it does 00:11:04.470 --> 00:11:06.830 align:start position:0% we have right so it does this it does SMS<00:11:04.860> n<00:11:05.220> but<00:11:05.400> it<00:11:05.490> might<00:11:05.640> inside<00:11:06.480> this<00:11:06.630> function 00:11:06.830 --> 00:11:06.840 align:start position:0% SMS n but it might inside this function 00:11:06.840 --> 00:11:09.200 align:start position:0% SMS n but it might inside this function and<00:11:07.740> it<00:11:07.860> emits<00:11:08.130> an<00:11:08.310> event<00:11:08.580> and<00:11:08.820> this<00:11:08.880> is<00:11:09.060> like<00:11:09.180> a 00:11:09.200 --> 00:11:09.210 align:start position:0% and it emits an event and this is like a 00:11:09.210 --> 00:11:10.820 align:start position:0% and it emits an event and this is like a proof<00:11:09.570> that<00:11:09.810> this<00:11:09.900> company<00:11:10.170> claimed<00:11:10.650> that 00:11:10.820 --> 00:11:10.830 align:start position:0% proof that this company claimed that 00:11:10.830 --> 00:11:13.400 align:start position:0% proof that this company claimed that they<00:11:10.980> sent<00:11:11.430> an<00:11:11.610> SMS<00:11:11.880> at<00:11:12.240> this<00:11:12.420> time<00:11:12.690> in 00:11:13.400 --> 00:11:13.410 align:start position:0% they sent an SMS at this time in 00:11:13.410 --> 00:11:15.020 align:start position:0% they sent an SMS at this time in response<00:11:13.830> to<00:11:13.980> some<00:11:14.130> action<00:11:14.430> that<00:11:14.580> use<00:11:14.700> it<00:11:14.850> and 00:11:15.020 --> 00:11:15.030 align:start position:0% response to some action that use it and 00:11:15.030 --> 00:11:17.480 align:start position:0% response to some action that use it and so<00:11:15.150> this<00:11:15.330> is<00:11:15.590> the<00:11:16.590> general<00:11:16.620> direction<00:11:16.980> we're 00:11:17.480 --> 00:11:17.490 align:start position:0% so this is the general direction we're 00:11:17.490 --> 00:11:19.220 align:start position:0% so this is the general direction we're moving<00:11:17.520> towards<00:11:18.090> and<00:11:18.870> so<00:11:18.960> that's<00:11:19.080> actually 00:11:19.220 --> 00:11:19.230 align:start position:0% moving towards and so that's actually 00:11:19.230 --> 00:11:19.680 align:start position:0% moving towards and so that's actually only 00:11:19.680 --> 00:11:19.690 align:start position:0% only 00:11:19.690 --> 00:11:20.640 align:start position:0% only to<00:11:19.780> talk<00:11:19.960> about<00:11:20.050> thank<00:11:20.320> you<00:11:20.410> for<00:11:20.560> listening 00:11:20.640 --> 00:11:20.650 align:start position:0% to talk about thank you for listening 00:11:20.650 --> 00:11:23.820 align:start position:0% to talk about thank you for listening let's<00:11:21.460> go<00:11:21.550> to<00:11:21.610> lunch