WEBVTT Kind: captions Language: en 00:00:04.690 --> 00:00:07.140 align:start position:0% a<00:00:04.770> short<00:00:05.770> introduction<00:00:06.160> about<00:00:06.430> me<00:00:06.760> so<00:00:07.029> I'm 00:00:07.140 --> 00:00:07.150 align:start position:0% a short introduction about me so I'm 00:00:07.150 --> 00:00:08.910 align:start position:0% a short introduction about me so I'm retime<00:00:07.569> ecology<00:00:08.140> well<00:00:08.290> tonight<00:00:08.559> party 00:00:08.910 --> 00:00:08.920 align:start position:0% retime ecology well tonight party 00:00:08.920 --> 00:00:12.570 align:start position:0% retime ecology well tonight party technologies<00:00:09.900> and<00:00:10.900> I<00:00:11.680> worked<00:00:11.920> on<00:00:12.070> in<00:00:12.250> serum 00:00:12.570 --> 00:00:12.580 align:start position:0% technologies and I worked on in serum 00:00:12.580 --> 00:00:16.470 align:start position:0% technologies and I worked on in serum and<00:00:12.730> eye<00:00:12.760> serum<00:00:12.910> 2.0<00:00:14.430> so<00:00:15.430> in<00:00:15.940> this<00:00:16.090> talk<00:00:16.270> I'm 00:00:16.470 --> 00:00:16.480 align:start position:0% and eye serum 2.0 so in this talk I'm 00:00:16.480 --> 00:00:18.269 align:start position:0% and eye serum 2.0 so in this talk I'm going<00:00:16.540> to<00:00:16.750> talk<00:00:16.869> about<00:00:17.279> backward 00:00:18.269 --> 00:00:18.279 align:start position:0% going to talk about backward 00:00:18.279 --> 00:00:21.330 align:start position:0% going to talk about backward compatibility<00:00:19.230> so<00:00:20.230> in<00:00:20.439> different<00:00:20.890> contexts 00:00:21.330 --> 00:00:21.340 align:start position:0% compatibility so in different contexts 00:00:21.340 --> 00:00:24.120 align:start position:0% compatibility so in different contexts we<00:00:21.579> have<00:00:21.790> different<00:00:22.779> definitions<00:00:23.500> for 00:00:24.120 --> 00:00:24.130 align:start position:0% we have different definitions for 00:00:24.130 --> 00:00:26.400 align:start position:0% we have different definitions for backward<00:00:24.759> ability<00:00:25.210> for<00:00:25.450> example<00:00:25.540> in<00:00:26.259> the 00:00:26.400 --> 00:00:26.410 align:start position:0% backward ability for example in the 00:00:26.410 --> 00:00:30.510 align:start position:0% backward ability for example in the context<00:00:26.860> of<00:00:28.050> system<00:00:29.050> interface<00:00:29.560> is<00:00:29.950> mostly 00:00:30.510 --> 00:00:30.520 align:start position:0% context of system interface is mostly 00:00:30.520 --> 00:00:33.990 align:start position:0% context of system interface is mostly about<00:00:31.590> internal<00:00:32.590> with<00:00:32.890> an<00:00:33.100> older<00:00:33.370> version<00:00:33.520> of 00:00:33.990 --> 00:00:34.000 align:start position:0% about internal with an older version of 00:00:34.000 --> 00:00:36.960 align:start position:0% about internal with an older version of the<00:00:34.390> interface<00:00:34.840> and<00:00:35.230> also<00:00:35.710> for<00:00:36.399> things<00:00:36.790> that 00:00:36.960 --> 00:00:36.970 align:start position:0% the interface and also for things that 00:00:36.970 --> 00:00:39.330 align:start position:0% the interface and also for things that handle<00:00:37.360> files<00:00:37.660> and<00:00:38.050> objects 00:00:39.330 --> 00:00:39.340 align:start position:0% handle files and objects 00:00:39.340 --> 00:00:42.320 align:start position:0% handle files and objects it's<00:00:39.730> about<00:00:40.170> handling<00:00:41.170> those<00:00:41.410> things 00:00:42.320 --> 00:00:42.330 align:start position:0% it's about handling those things 00:00:42.330 --> 00:00:46.620 align:start position:0% it's about handling those things produced<00:00:43.330> by<00:00:43.660> older<00:00:43.990> versions<00:00:44.940> so<00:00:45.940> we're 00:00:46.620 --> 00:00:46.630 align:start position:0% produced by older versions so we're 00:00:46.630 --> 00:00:48.270 align:start position:0% produced by older versions so we're talking<00:00:46.750> about<00:00:46.990> backward<00:00:47.590> ability<00:00:48.070> in<00:00:48.250> a 00:00:48.270 --> 00:00:48.280 align:start position:0% talking about backward ability in a 00:00:48.280 --> 00:00:50.010 align:start position:0% talking about backward ability in a blockchain<00:00:48.670> context<00:00:49.390> so<00:00:49.540> we<00:00:49.720> are<00:00:49.810> really 00:00:50.010 --> 00:00:50.020 align:start position:0% blockchain context so we are really 00:00:50.020 --> 00:00:51.660 align:start position:0% blockchain context so we are really talking<00:00:50.170> about<00:00:50.380> smartphones<00:00:51.010> smart 00:00:51.660 --> 00:00:51.670 align:start position:0% talking about smartphones smart 00:00:51.670 --> 00:00:55.470 align:start position:0% talking about smartphones smart contracts<00:00:52.260> and<00:00:53.370> the<00:00:54.370> definition<00:00:54.910> here<00:00:55.150> I<00:00:55.180> gave 00:00:55.470 --> 00:00:55.480 align:start position:0% contracts and the definition here I gave 00:00:55.480 --> 00:00:58.160 align:start position:0% contracts and the definition here I gave is<00:00:55.720> if<00:00:56.079> a<00:00:56.290> smart<00:00:56.560> contract<00:00:56.710> works<00:00:57.520> in<00:00:57.730> the<00:00:57.820> past 00:00:58.160 --> 00:00:58.170 align:start position:0% is if a smart contract works in the past 00:00:58.170 --> 00:01:00.960 align:start position:0% is if a smart contract works in the past they<00:00:59.170> need<00:00:59.320> to<00:00:59.410> continue<00:00:59.829> to<00:00:59.950> work<00:00:59.980> in<00:01:00.640> the 00:01:00.960 --> 00:01:00.970 align:start position:0% they need to continue to work in the 00:01:00.970 --> 00:01:04.319 align:start position:0% they need to continue to work in the future<00:01:01.300> no<00:01:01.450> matter<00:01:01.660> how<00:01:02.260> many<00:01:03.329> future 00:01:04.319 --> 00:01:04.329 align:start position:0% future no matter how many future 00:01:04.329 --> 00:01:09.330 align:start position:0% future no matter how many future upgrades<00:01:04.720> we<00:01:04.900> add<00:01:06.750> so<00:01:07.829> the<00:01:08.829> scene<00:01:09.039> we<00:01:09.159> talked 00:01:09.330 --> 00:01:09.340 align:start position:0% upgrades we add so the scene we talked 00:01:09.340 --> 00:01:12.569 align:start position:0% upgrades we add so the scene we talked about<00:01:09.490> here<00:01:09.969> today<00:01:10.240> is<00:01:10.920> that<00:01:11.920> is<00:01:12.280> the 00:01:12.569 --> 00:01:12.579 align:start position:0% about here today is that is the 00:01:12.579 --> 00:01:14.789 align:start position:0% about here today is that is the not-so-nice<00:01:13.179> lowry<00:01:13.659> about<00:01:13.960> died<00:01:14.140> portability 00:01:14.789 --> 00:01:14.799 align:start position:0% not-so-nice lowry about died portability 00:01:14.799 --> 00:01:18.179 align:start position:0% not-so-nice lowry about died portability in<00:01:14.979> science<00:01:15.310> erm<00:01:15.579> so<00:01:16.560> Michael<00:01:17.560> can<00:01:17.679> really<00:01:17.979> can 00:01:18.179 --> 00:01:18.189 align:start position:0% in science erm so Michael can really can 00:01:18.189 --> 00:01:20.459 align:start position:0% in science erm so Michael can really can be<00:01:18.310> really<00:01:18.579> easy<00:01:18.729> to<00:01:18.819> be<00:01:19.210> broken<00:01:19.539> for<00:01:19.749> a<00:01:20.229> lot<00:01:20.350> of 00:01:20.459 --> 00:01:20.469 align:start position:0% be really easy to be broken for a lot of 00:01:20.469 --> 00:01:23.010 align:start position:0% be really easy to be broken for a lot of times<00:01:20.710> I<00:01:21.100> intentionally<00:01:21.789> or<00:01:22.270> intentionally 00:01:23.010 --> 00:01:23.020 align:start position:0% times I intentionally or intentionally 00:01:23.020 --> 00:01:27.450 align:start position:0% times I intentionally or intentionally as<00:01:23.289> we<00:01:23.679> demonstrated<00:01:24.490> I<00:01:24.700> assume<00:01:25.469> so<00:01:26.469> this<00:01:27.249> is<00:01:27.429> a 00:01:27.450 --> 00:01:27.460 align:start position:0% as we demonstrated I assume so this is a 00:01:27.460 --> 00:01:30.779 align:start position:0% as we demonstrated I assume so this is a huge<00:01:27.759> issue<00:01:28.179> because<00:01:28.380> I'm<00:01:29.380> 10<00:01:29.679> contracts<00:01:30.369> are 00:01:30.779 --> 00:01:30.789 align:start position:0% huge issue because I'm 10 contracts are 00:01:30.789 --> 00:01:33.569 align:start position:0% huge issue because I'm 10 contracts are affected<00:01:31.420> and<00:01:31.659> also<00:01:32.499> a<00:01:32.770> lot<00:01:33.100> of<00:01:33.130> real<00:01:33.399> money 00:01:33.569 --> 00:01:33.579 align:start position:0% affected and also a lot of real money 00:01:33.579 --> 00:01:38.849 align:start position:0% affected and also a lot of real money involved<00:01:36.119> for<00:01:37.259> unintentional<00:01:38.259> background 00:01:38.849 --> 00:01:38.859 align:start position:0% involved for unintentional background 00:01:38.859 --> 00:01:42.199 align:start position:0% involved for unintentional background copy<00:01:38.979> breakage<00:01:39.850> we<00:01:40.209> have<00:01:40.420> the<00:01:40.780> example<00:01:41.499> of<00:01:41.679> ERP 00:01:42.199 --> 00:01:42.209 align:start position:0% copy breakage we have the example of ERP 00:01:42.209 --> 00:01:46.349 align:start position:0% copy breakage we have the example of ERP 1283<00:01:43.590> which<00:01:44.590> is<00:01:44.979> to<00:01:45.280> change<00:01:45.520> to<00:01:45.909> decrease 00:01:46.349 --> 00:01:46.359 align:start position:0% 1283 which is to change to decrease 00:01:46.359 --> 00:01:49.830 align:start position:0% 1283 which is to change to decrease guest<00:01:46.659> host<00:01:46.899> but<00:01:47.350> unfortunately<00:01:48.659> we<00:01:49.659> found 00:01:49.830 --> 00:01:49.840 align:start position:0% guest host but unfortunately we found 00:01:49.840 --> 00:01:53.370 align:start position:0% guest host but unfortunately we found that<00:01:50.609> if<00:01:51.609> we<00:01:51.729> do<00:01:51.999> that<00:01:52.029> and<00:01:52.600> there<00:01:52.990> are<00:01:53.139> some 00:01:53.370 --> 00:01:53.380 align:start position:0% that if we do that and there are some 00:01:53.380 --> 00:01:55.859 align:start position:0% that if we do that and there are some issues<00:01:53.560> with<00:01:54.039> high<00:01:54.670> probability<00:01:54.850> because<00:01:55.539> it 00:01:55.859 --> 00:01:55.869 align:start position:0% issues with high probability because it 00:01:55.869 --> 00:01:57.629 align:start position:0% issues with high probability because it can<00:01:56.229> cause<00:01:56.499> some<00:01:56.709> contracts<00:01:57.159> to<00:01:57.310> have<00:01:57.490> new 00:01:57.629 --> 00:01:57.639 align:start position:0% can cause some contracts to have new 00:01:57.639 --> 00:02:00.959 align:start position:0% can cause some contracts to have new entry<00:01:57.819> attacks<00:01:58.799> and<00:01:59.799> we<00:02:00.189> also<00:02:00.340> have<00:02:00.579> a<00:02:00.729> ready 00:02:00.959 --> 00:02:00.969 align:start position:0% entry attacks and we also have a ready 00:02:00.969 --> 00:02:05.069 align:start position:0% entry attacks and we also have a ready for<00:02:01.090> instant<00:02:01.959> war<00:02:02.170> which<00:02:02.979> is<00:02:03.749> VIP<00:02:04.749> who 00:02:05.069 --> 00:02:05.079 align:start position:0% for instant war which is VIP who 00:02:05.079 --> 00:02:06.809 align:start position:0% for instant war which is VIP who increase<00:02:05.499> cash<00:02:05.709> flows<00:02:05.979> we<00:02:06.189> also<00:02:06.340> figure<00:02:06.789> out 00:02:06.809 --> 00:02:06.819 align:start position:0% increase cash flows we also figure out 00:02:06.819 --> 00:02:11.309 align:start position:0% increase cash flows we also figure out this<00:02:07.090> country<00:02:07.569> by<00:02:07.929> probability<00:02:09.869> because<00:02:10.869> you 00:02:11.309 --> 00:02:11.319 align:start position:0% this country by probability because you 00:02:11.319 --> 00:02:13.560 align:start position:0% this country by probability because you can<00:02:11.620> just<00:02:12.160> call<00:02:12.400> some<00:02:12.700> functions<00:02:13.180> of<00:02:13.390> some 00:02:13.560 --> 00:02:13.570 align:start position:0% can just call some functions of some 00:02:13.570 --> 00:02:17.280 align:start position:0% can just call some functions of some contract<00:02:14.080> to<00:02:14.200> be<00:02:14.320> frozen 00:02:17.280 --> 00:02:17.290 align:start position:0% 00:02:17.290 --> 00:02:20.500 align:start position:0% so<00:02:18.290> those<00:02:18.709> are<00:02:19.069> intentional<00:02:19.940> Packer<00:02:20.209> have 00:02:20.500 --> 00:02:20.510 align:start position:0% so those are intentional Packer have 00:02:20.510 --> 00:02:24.339 align:start position:0% so those are intentional Packer have real<00:02:20.690> breakage<00:02:21.110> are<00:02:21.410> nearly<00:02:22.330> missed<00:02:23.330> in<00:02:23.900> the 00:02:24.339 --> 00:02:24.349 align:start position:0% real breakage are nearly missed in the 00:02:24.349 --> 00:02:26.500 align:start position:0% real breakage are nearly missed in the holy<00:02:24.709> deity<00:02:25.130> auditing<00:02:25.670> process<00:02:25.849> we<00:02:26.270> nearly 00:02:26.500 --> 00:02:26.510 align:start position:0% holy deity auditing process we nearly 00:02:26.510 --> 00:02:29.199 align:start position:0% holy deity auditing process we nearly found<00:02:26.780> it<00:02:26.989> for<00:02:27.680> the<00:02:27.739> last<00:02:27.920> minutes<00:02:28.280> and<00:02:28.910> it 00:02:29.199 --> 00:02:29.209 align:start position:0% found it for the last minutes and it 00:02:29.209 --> 00:02:33.339 align:start position:0% found it for the last minutes and it caused<00:02:29.450> some<00:02:29.540> a<00:02:30.050> lot<00:02:30.470> of<00:02:30.530> issues<00:02:31.930> so<00:02:32.930> you<00:02:33.230> know 00:02:33.339 --> 00:02:33.349 align:start position:0% caused some a lot of issues so you know 00:02:33.349 --> 00:02:35.589 align:start position:0% caused some a lot of issues so you know patch<00:02:33.530> may<00:02:33.739> also<00:02:33.890> have<00:02:34.130> debate<00:02:34.459> about<00:02:34.700> my<00:02:35.330> very 00:02:35.589 --> 00:02:35.599 align:start position:0% patch may also have debate about my very 00:02:35.599 --> 00:02:37.210 align:start position:0% patch may also have debate about my very increasing<00:02:36.080> guys<00:02:36.230> thoughts<00:02:36.500> or<00:02:36.709> decreasing 00:02:37.210 --> 00:02:37.220 align:start position:0% increasing guys thoughts or decreasing 00:02:37.220 --> 00:02:39.160 align:start position:0% increasing guys thoughts or decreasing class<00:02:37.400> codes<00:02:37.640> will<00:02:37.760> be<00:02:37.790> better<00:02:38.030> and<00:02:38.630> it<00:02:38.989> turns 00:02:39.160 --> 00:02:39.170 align:start position:0% class codes will be better and it turns 00:02:39.170 --> 00:02:42.490 align:start position:0% class codes will be better and it turns out<00:02:39.349> both<00:02:39.860> scenarios<00:02:40.550> can<00:02:41.150> break<00:02:41.500> hydrography 00:02:42.490 --> 00:02:42.500 align:start position:0% out both scenarios can break hydrography 00:02:42.500 --> 00:02:47.860 align:start position:0% out both scenarios can break hydrography so<00:02:42.830> is<00:02:43.160> the<00:02:44.030> same<00:02:44.239> vaccine<00:02:44.920> and<00:02:46.480> in<00:02:47.480> the<00:02:47.569> future 00:02:47.860 --> 00:02:47.870 align:start position:0% so is the same vaccine and in the future 00:02:47.870 --> 00:02:50.289 align:start position:0% so is the same vaccine and in the future we<00:02:48.019> may<00:02:48.140> also<00:02:48.260> have<00:02:48.880> intentional<00:02:49.880> pack<00:02:50.120> of 00:02:50.289 --> 00:02:50.299 align:start position:0% we may also have intentional pack of 00:02:50.299 --> 00:02:52.990 align:start position:0% we may also have intentional pack of heavy<00:02:50.600> breakage<00:02:51.049> so<00:02:51.470> for<00:02:51.799> example<00:02:52.250> if<00:02:52.430> nobody 00:02:52.990 --> 00:02:53.000 align:start position:0% heavy breakage so for example if nobody 00:02:53.000 --> 00:02:55.509 align:start position:0% heavy breakage so for example if nobody knows<00:02:53.209> that<00:02:53.360> guys<00:02:53.600> cause<00:02:53.870> pre<00:02:54.140> kerosene<00:02:54.650> so<00:02:54.890> in 00:02:55.509 --> 00:02:55.519 align:start position:0% knows that guys cause pre kerosene so in 00:02:55.519 --> 00:02:58.900 align:start position:0% knows that guys cause pre kerosene so in the<00:02:55.610> future<00:02:55.970> we<00:02:56.540> might<00:02:57.350> just<00:02:57.890> go<00:02:58.310> ahead<00:02:58.640> with 00:02:58.900 --> 00:02:58.910 align:start position:0% the future we might just go ahead with 00:02:58.910 --> 00:03:01.180 align:start position:0% the future we might just go ahead with some<00:02:58.940> some<00:02:59.540> guys<00:02:59.720> for<00:02:59.989> changes<00:03:00.440> if<00:03:00.650> that's 00:03:01.180 --> 00:03:01.190 align:start position:0% some some guys for changes if that's 00:03:01.190 --> 00:03:03.220 align:start position:0% some some guys for changes if that's really<00:03:01.400> pricing<00:03:02.299> and<00:03:02.510> we<00:03:02.690> want<00:03:02.870> to<00:03:02.989> reflect 00:03:03.220 --> 00:03:03.230 align:start position:0% really pricing and we want to reflect 00:03:03.230 --> 00:03:05.970 align:start position:0% really pricing and we want to reflect the<00:03:03.530> real<00:03:03.709> computation<00:03:04.160> computation<00:03:04.670> cost 00:03:05.970 --> 00:03:05.980 align:start position:0% the real computation computation cost 00:03:05.980 --> 00:03:11.170 align:start position:0% the real computation computation cost and<00:03:06.980> also<00:03:07.280> the<00:03:07.610> example<00:03:08.120> for<00:03:08.420> statement<00:03:10.180> which 00:03:11.170 --> 00:03:11.180 align:start position:0% and also the example for statement which 00:03:11.180 --> 00:03:14.680 align:start position:0% and also the example for statement which is<00:03:11.209> a<00:03:11.769> I<00:03:12.769> don't<00:03:13.489> know<00:03:13.549> my<00:03:14.090> very<00:03:14.330> well<00:03:14.569> to 00:03:14.680 --> 00:03:14.690 align:start position:0% is a I don't know my very well to 00:03:14.690 --> 00:03:16.570 align:start position:0% is a I don't know my very well to adopting<00:03:15.080> now<00:03:15.260> but<00:03:15.500> we<00:03:15.950> probably<00:03:16.190> want<00:03:16.489> to 00:03:16.570 --> 00:03:16.580 align:start position:0% adopting now but we probably want to 00:03:16.580 --> 00:03:18.670 align:start position:0% adopting now but we probably want to have<00:03:17.030> something<00:03:17.269> there<00:03:17.569> proposals<00:03:18.140> to<00:03:18.650> fix 00:03:18.670 --> 00:03:18.680 align:start position:0% have something there proposals to fix 00:03:18.680 --> 00:03:22.300 align:start position:0% have something there proposals to fix state<00:03:19.190> floats<00:03:19.720> which<00:03:20.799> can<00:03:21.799> also<00:03:21.980> bring<00:03:22.250> back 00:03:22.300 --> 00:03:22.310 align:start position:0% state floats which can also bring back 00:03:22.310 --> 00:03:23.170 align:start position:0% state floats which can also bring back workability 00:03:23.170 --> 00:03:23.180 align:start position:0% workability 00:03:23.180 --> 00:03:26.280 align:start position:0% workability and<00:03:23.329> we<00:03:23.780> also<00:03:23.900> have<00:03:24.260> to<00:03:24.530> engage<00:03:24.680> from<00:03:24.980> conduct 00:03:26.280 --> 00:03:26.290 align:start position:0% and we also have to engage from conduct 00:03:26.290 --> 00:03:32.349 align:start position:0% and we also have to engage from conduct to<00:03:27.290> ETH<00:03:27.970> 200<00:03:28.970> chart<00:03:29.209> in<00:03:30.310> that<00:03:31.310> case<00:03:31.519> some<00:03:31.819> comic 00:03:32.349 --> 00:03:32.359 align:start position:0% to ETH 200 chart in that case some comic 00:03:32.359 --> 00:03:36.610 align:start position:0% to ETH 200 chart in that case some comic rights<00:03:32.540> can<00:03:32.810> be<00:03:32.959> broken<00:03:33.350> as<00:03:33.620> well<00:03:35.380> so<00:03:36.380> this 00:03:36.610 --> 00:03:36.620 align:start position:0% rights can be broken as well so this 00:03:36.620 --> 00:03:39.250 align:start position:0% rights can be broken as well so this forms<00:03:37.010> to<00:03:37.340> a<00:03:37.549> conversion<00:03:38.000> II<00:03:38.269> it's<00:03:39.019> really 00:03:39.250 --> 00:03:39.260 align:start position:0% forms to a conversion II it's really 00:03:39.260 --> 00:03:41.080 align:start position:0% forms to a conversion II it's really about<00:03:39.470> that<00:03:40.010> we<00:03:40.340> currently<00:03:40.609> don't<00:03:40.880> have 00:03:41.080 --> 00:03:41.090 align:start position:0% about that we currently don't have 00:03:41.090 --> 00:03:42.970 align:start position:0% about that we currently don't have really<00:03:41.239> card<00:03:41.600> for<00:03:41.930> a<00:03:41.959> background<00:03:42.290> LP<00:03:42.560> that<00:03:42.799> is 00:03:42.970 --> 00:03:42.980 align:start position:0% really card for a background LP that is 00:03:42.980 --> 00:03:45.550 align:start position:0% really card for a background LP that is so<00:03:43.670> easy<00:03:43.910> to<00:03:44.030> be<00:03:44.239> broken<00:03:44.480> so<00:03:45.139> we're<00:03:45.380> probably 00:03:45.550 --> 00:03:45.560 align:start position:0% so easy to be broken so we're probably 00:03:45.560 --> 00:03:49.930 align:start position:0% so easy to be broken so we're probably about<00:03:45.769> to<00:03:46.100> do<00:03:46.220> something<00:03:46.489> with<00:03:46.850> it<00:03:48.370> so<00:03:49.370> in<00:03:49.760> this 00:03:49.930 --> 00:03:49.940 align:start position:0% about to do something with it so in this 00:03:49.940 --> 00:03:51.879 align:start position:0% about to do something with it so in this section<00:03:50.150> I'm<00:03:50.329> going<00:03:50.510> to<00:03:50.600> talk<00:03:50.780> about<00:03:50.889> three 00:03:51.879 --> 00:03:51.889 align:start position:0% section I'm going to talk about three 00:03:51.889 --> 00:03:56.670 align:start position:0% section I'm going to talk about three different<00:03:52.040> versions<00:03:52.430> of<00:03:54.430> account<00:03:55.430> versioning 00:03:56.670 --> 00:03:56.680 align:start position:0% different versions of account versioning 00:03:56.680 --> 00:04:01.479 align:start position:0% different versions of account versioning from<00:03:57.760> code<00:03:58.760> prefix<00:03:59.209> to<00:03:59.530> special<00:04:00.530> contracts<00:04:01.250> to 00:04:01.479 --> 00:04:01.489 align:start position:0% from code prefix to special contracts to 00:04:01.489 --> 00:04:03.849 align:start position:0% from code prefix to special contracts to arrow<00:04:01.850> key<00:04:02.090> fields<00:04:02.420> just<00:04:03.380> give<00:04:03.650> you<00:04:03.769> an<00:04:03.829> idea 00:04:03.849 --> 00:04:03.859 align:start position:0% arrow key fields just give you an idea 00:04:03.859 --> 00:04:06.699 align:start position:0% arrow key fields just give you an idea about<00:04:04.459> how<00:04:04.700> this<00:04:04.880> involves<00:04:05.540> and<00:04:05.840> the<00:04:06.410> same<00:04:06.620> we 00:04:06.699 --> 00:04:06.709 align:start position:0% about how this involves and the same we 00:04:06.709 --> 00:04:10.150 align:start position:0% about how this involves and the same we finally<00:04:07.040> settled<00:04:07.430> on<00:04:08.410> so<00:04:09.410> the<00:04:09.620> earliest<00:04:09.950> is 00:04:10.150 --> 00:04:10.160 align:start position:0% finally settled on so the earliest is 00:04:10.160 --> 00:04:13.740 align:start position:0% finally settled on so the earliest is probably<00:04:10.609> the<00:04:10.790> code<00:04:10.970> prefix<00:04:11.269> which<00:04:11.870> was<00:04:12.440> in 00:04:13.740 --> 00:04:13.750 align:start position:0% probably the code prefix which was in 00:04:13.750 --> 00:04:16.800 align:start position:0% probably the code prefix which was in yeah<00:04:14.750> p.1154 00:04:16.800 --> 00:04:16.810 align:start position:0% yeah p.1154 00:04:16.810 --> 00:04:20.979 align:start position:0% yeah p.1154 in<00:04:17.810> 2016<00:04:18.680> so<00:04:18.859> it<00:04:19.700> did<00:04:20.209> a<00:04:20.359> little<00:04:20.690> scallion 00:04:20.979 --> 00:04:20.989 align:start position:0% in 2016 so it did a little scallion 00:04:20.989 --> 00:04:22.930 align:start position:0% in 2016 so it did a little scallion account<00:04:21.410> resolving<00:04:21.889> give<00:04:22.190> us<00:04:22.310> some<00:04:22.490> support 00:04:22.930 --> 00:04:22.940 align:start position:0% account resolving give us some support 00:04:22.940 --> 00:04:26.790 align:start position:0% account resolving give us some support insurance<00:04:23.599> so<00:04:24.159> the<00:04:25.159> idea<00:04:25.610> is<00:04:25.700> quite<00:04:25.880> simple 00:04:26.790 --> 00:04:26.800 align:start position:0% insurance so the idea is quite simple 00:04:26.800 --> 00:04:29.340 align:start position:0% insurance so the idea is quite simple I'd<00:04:26.949> add<00:04:27.880> a<00:04:27.940> small<00:04:28.330> country<00:04:28.570> fiction<00:04:29.169> I<00:04:29.289> read 00:04:29.340 --> 00:04:29.350 align:start position:0% I'd add a small country fiction I read 00:04:29.350 --> 00:04:31.980 align:start position:0% I'd add a small country fiction I read contracts<00:04:30.070> and<00:04:30.340> if<00:04:30.789> the<00:04:31.300> contract<00:04:31.600> attack 00:04:31.980 --> 00:04:31.990 align:start position:0% contracts and if the contract attack 00:04:31.990 --> 00:04:35.279 align:start position:0% contracts and if the contract attack that<00:04:32.199> that<00:04:32.830> prefix<00:04:33.220> and<00:04:33.520> we<00:04:33.610> just<00:04:34.289> execute 00:04:35.279 --> 00:04:35.289 align:start position:0% that that prefix and we just execute 00:04:35.289 --> 00:04:37.710 align:start position:0% that that prefix and we just execute using<00:04:35.590> that<00:04:35.740> version<00:04:35.979> nation<00:04:36.639> of<00:04:36.820> the<00:04:37.330> default 00:04:37.710 --> 00:04:37.720 align:start position:0% using that version nation of the default 00:04:37.720 --> 00:04:41.909 align:start position:0% using that version nation of the default version<00:04:39.270> so<00:04:40.270> this<00:04:40.419> is<00:04:40.570> later<00:04:40.780> expanded<00:04:41.350> into 00:04:41.909 --> 00:04:41.919 align:start position:0% version so this is later expanded into 00:04:41.919 --> 00:04:46.560 align:start position:0% version so this is later expanded into year<00:04:42.220> key<00:04:42.660> 7007<00:04:43.949> so<00:04:44.949> we<00:04:45.759> did<00:04:46.060> have<00:04:46.090> some<00:04:46.389> issues 00:04:46.560 --> 00:04:46.570 align:start position:0% year key 7007 so we did have some issues 00:04:46.570 --> 00:04:50.159 align:start position:0% year key 7007 so we did have some issues so<00:04:46.990> this<00:04:47.590> code<00:04:48.039> prefix<00:04:48.370> along<00:04:48.759> the<00:04:49.690> issue<00:04:49.870> is 00:04:50.159 --> 00:04:50.169 align:start position:0% so this code prefix along the issue is 00:04:50.169 --> 00:04:53.100 align:start position:0% so this code prefix along the issue is that<00:04:50.380> some<00:04:50.740> we<00:04:51.580> can<00:04:51.759> deploy<00:04:52.000> data<00:04:52.330> internally 00:04:53.100 --> 00:04:53.110 align:start position:0% that some we can deploy data internally 00:04:53.110 --> 00:04:55.230 align:start position:0% that some we can deploy data internally so<00:04:53.530> some<00:04:54.220> that<00:04:54.400> have<00:04:54.580> match<00:04:54.759> just 00:04:55.230 --> 00:04:55.240 align:start position:0% so some that have match just 00:04:55.240 --> 00:05:01.379 align:start position:0% so some that have match just accidentally<00:04:56.199> have<00:04:56.610> prefix<00:04:58.470> and<00:04:59.910> what<00:05:00.910> is<00:05:01.030> the 00:05:01.379 --> 00:05:01.389 align:start position:0% accidentally have prefix and what is the 00:05:01.389 --> 00:05:04.110 align:start position:0% accidentally have prefix and what is the Coulomb<00:05:01.810> chance<00:05:02.110> so<00:05:02.380> this<00:05:03.370> is<00:05:03.490> a<00:05:03.520> huge<00:05:03.940> issue 00:05:04.110 --> 00:05:04.120 align:start position:0% Coulomb chance so this is a huge issue 00:05:04.120 --> 00:05:07.560 align:start position:0% Coulomb chance so this is a huge issue for<00:05:04.360> me<00:05:04.750> and<00:05:04.780> that<00:05:05.199> requires<00:05:05.650> validation<00:05:06.570> so 00:05:07.560 --> 00:05:07.570 align:start position:0% for me and that requires validation so 00:05:07.570 --> 00:05:11.670 align:start position:0% for me and that requires validation so it's<00:05:08.320> just<00:05:08.620> really<00:05:08.949> light<00:05:09.130> and<00:05:10.380> we<00:05:11.380> can<00:05:11.410> do 00:05:11.670 --> 00:05:11.680 align:start position:0% it's just really light and we can do 00:05:11.680 --> 00:05:13.439 align:start position:0% it's just really light and we can do something<00:05:12.009> about<00:05:12.099> this<00:05:12.340> so<00:05:12.699> there's<00:05:13.090> a<00:05:13.270> way 00:05:13.439 --> 00:05:13.449 align:start position:0% something about this so there's a way 00:05:13.449 --> 00:05:16.200 align:start position:0% something about this so there's a way that<00:05:13.750> we<00:05:13.900> can<00:05:14.050> discuss<00:05:14.440> all<00:05:14.470> I<00:05:14.740> use<00:05:15.039> up<00:05:15.940> code 00:05:16.200 --> 00:05:16.210 align:start position:0% that we can discuss all I use up code 00:05:16.210 --> 00:05:19.890 align:start position:0% that we can discuss all I use up code deployments<00:05:17.160> so<00:05:18.160> that<00:05:18.460> we<00:05:18.789> don't<00:05:19.330> have<00:05:19.539> those 00:05:19.890 --> 00:05:19.900 align:start position:0% deployments so that we don't have those 00:05:19.900 --> 00:05:23.159 align:start position:0% deployments so that we don't have those data<00:05:20.830> function<00:05:21.490> that<00:05:21.759> accidentally<00:05:22.660> had<00:05:22.900> the 00:05:23.159 --> 00:05:23.169 align:start position:0% data function that accidentally had the 00:05:23.169 --> 00:05:26.460 align:start position:0% data function that accidentally had the prefix<00:05:24.120> but<00:05:25.120> the<00:05:25.240> issue<00:05:25.389> is<00:05:25.509> that<00:05:25.630> is<00:05:25.900> not<00:05:26.259> back 00:05:26.460 --> 00:05:26.470 align:start position:0% prefix but the issue is that is not back 00:05:26.470 --> 00:05:32.700 align:start position:0% prefix but the issue is that is not back workable<00:05:27.099> so<00:05:28.949> the<00:05:29.949> second<00:05:31.169> variations<00:05:32.169> we<00:05:32.500> had 00:05:32.700 --> 00:05:32.710 align:start position:0% workable so the second variations we had 00:05:32.710 --> 00:05:35.580 align:start position:0% workable so the second variations we had was<00:05:33.039> using<00:05:33.940> Excel<00:05:34.330> returning<00:05:34.780> were<00:05:34.960> special 00:05:35.580 --> 00:05:35.590 align:start position:0% was using Excel returning were special 00:05:35.590 --> 00:05:41.689 align:start position:0% was using Excel returning were special contacts<00:05:36.270> so<00:05:37.270> this<00:05:37.659> was<00:05:38.020> the<00:05:38.470> FE<00:05:38.940> 1891<00:05:39.940> in<00:05:40.389> 2019 00:05:41.689 --> 00:05:41.699 align:start position:0% contacts so this was the FE 1891 in 2019 00:05:41.699 --> 00:05:44.370 align:start position:0% contacts so this was the FE 1891 in 2019 so<00:05:42.699> basically<00:05:43.120> the<00:05:43.389> idea<00:05:43.599> is<00:05:43.659> pressing<00:05:44.080> for<00:05:44.110> we 00:05:44.370 --> 00:05:44.380 align:start position:0% so basically the idea is pressing for we 00:05:44.380 --> 00:05:47.969 align:start position:0% so basically the idea is pressing for we just<00:05:44.590> store<00:05:44.830> the<00:05:45.300> version<00:05:46.300> information<00:05:47.199> of 00:05:47.969 --> 00:05:47.979 align:start position:0% just store the version information of 00:05:47.979 --> 00:05:50.899 align:start position:0% just store the version information of account<00:05:48.669> you<00:05:48.940> know<00:05:49.180> special<00:05:49.599> contract<00:05:50.020> status 00:05:50.899 --> 00:05:50.909 align:start position:0% account you know special contract status 00:05:50.909 --> 00:05:54.210 align:start position:0% account you know special contract status starting<00:05:51.909> a<00:05:51.970> loan<00:05:52.120> location<00:05:52.860> and<00:05:53.860> then 00:05:54.210 --> 00:05:54.220 align:start position:0% starting a loan location and then 00:05:54.220 --> 00:05:57.589 align:start position:0% starting a loan location and then whenever<00:05:54.849> we<00:05:55.060> execute<00:05:55.780> a<00:05:56.110> contract<00:05:56.409> we<00:05:56.979> just 00:05:57.589 --> 00:05:57.599 align:start position:0% whenever we execute a contract we just 00:05:57.599 --> 00:05:59.969 align:start position:0% whenever we execute a contract we just reach<00:05:58.599> the<00:05:58.630> version<00:05:59.169> from<00:05:59.500> that<00:05:59.770> special 00:05:59.969 --> 00:05:59.979 align:start position:0% reach the version from that special 00:05:59.979 --> 00:06:02.399 align:start position:0% reach the version from that special contract<00:06:00.460> first<00:06:00.729> and<00:06:01.060> then<00:06:01.479> decide<00:06:01.870> which<00:06:02.169> for 00:06:02.399 --> 00:06:02.409 align:start position:0% contract first and then decide which for 00:06:02.409 --> 00:06:05.969 align:start position:0% contract first and then decide which for young<00:06:02.560> widows<00:06:04.050> so<00:06:05.050> this<00:06:05.199> is<00:06:05.320> quite<00:06:05.530> simple 00:06:05.969 --> 00:06:05.979 align:start position:0% young widows so this is quite simple 00:06:05.979 --> 00:06:08.100 align:start position:0% young widows so this is quite simple it<00:06:06.099> does<00:06:06.550> not<00:06:06.729> require<00:06:06.909> anything<00:06:07.509> to<00:06:07.840> state 00:06:08.100 --> 00:06:08.110 align:start position:0% it does not require anything to state 00:06:08.110 --> 00:06:10.980 align:start position:0% it does not require anything to state the<00:06:08.740> issue<00:06:08.919> however<00:06:09.849> is<00:06:10.180> that<00:06:10.539> we<00:06:10.780> need<00:06:10.960> a 00:06:10.980 --> 00:06:10.990 align:start position:0% the issue however is that we need a 00:06:10.990 --> 00:06:13.320 align:start position:0% the issue however is that we need a different<00:06:11.349> node<00:06:11.680> tree<00:06:11.860> operation<00:06:12.400> which<00:06:13.300> is 00:06:13.320 --> 00:06:13.330 align:start position:0% different node tree operation which is 00:06:13.330 --> 00:06:18.629 align:start position:0% different node tree operation which is kind<00:06:14.169> of<00:06:14.229> tired<00:06:14.530> because<00:06:14.800> I<00:06:15.870> mean<00:06:16.870> each<00:06:17.770> trail 00:06:18.629 --> 00:06:18.639 align:start position:0% kind of tired because I mean each trail 00:06:18.639 --> 00:06:23.520 align:start position:0% kind of tired because I mean each trail fishing<00:06:19.150> for<00:06:19.389> all<00:06:19.720> accounts<00:06:20.409> is<00:06:22.349> means<00:06:23.349> we 00:06:23.520 --> 00:06:23.530 align:start position:0% fishing for all accounts is means we 00:06:23.530 --> 00:06:25.890 align:start position:0% fishing for all accounts is means we double<00:06:23.830> the<00:06:23.919> tree<00:06:24.099> access<00:06:24.430> and<00:06:24.729> even<00:06:25.690> the 00:06:25.890 --> 00:06:25.900 align:start position:0% double the tree access and even the 00:06:25.900 --> 00:06:27.899 align:start position:0% double the tree access and even the current<00:06:26.259> free<00:06:26.680> access<00:06:26.979> is<00:06:27.159> not<00:06:27.370> really<00:06:27.669> fast 00:06:27.899 --> 00:06:27.909 align:start position:0% current free access is not really fast 00:06:27.909 --> 00:06:32.610 align:start position:0% current free access is not really fast so<00:06:28.300> just<00:06:28.630> as<00:06:29.080> I<00:06:29.199> give<00:06:29.380> you<00:06:30.030> and<00:06:31.259> late 00:06:32.610 --> 00:06:32.620 align:start position:0% so just as I give you and late 00:06:32.620 --> 00:06:35.100 align:start position:0% so just as I give you and late finally<00:06:33.130> we<00:06:33.250> have<00:06:33.460> the<00:06:33.669> conversion<00:06:34.509> in<00:06:34.750> we<00:06:34.900> are 00:06:35.100 --> 00:06:35.110 align:start position:0% finally we have the conversion in we are 00:06:35.110 --> 00:06:39.730 align:start position:0% finally we have the conversion in we are field<00:06:35.590> so<00:06:36.090> this<00:06:37.090> was<00:06:37.539> originally<00:06:37.979> CICS<00:06:38.979> and 00:06:39.730 --> 00:06:39.740 align:start position:0% field so this was originally CICS and 00:06:39.740 --> 00:06:44.290 align:start position:0% field so this was originally CICS and 14<00:06:40.100> in<00:06:40.520> 2017<00:06:41.920> the<00:06:42.920> idea<00:06:43.160> is<00:06:43.280> quite<00:06:43.400> simple<00:06:43.520> also 00:06:44.290 --> 00:06:44.300 align:start position:0% 14 in 2017 the idea is quite simple also 00:06:44.300 --> 00:06:47.650 align:start position:0% 14 in 2017 the idea is quite simple also quite<00:06:44.630> simple<00:06:44.810> so<00:06:45.230> we<00:06:45.380> have<00:06:45.680> for<00:06:46.280> our<00:06:47.180> P 00:06:47.650 --> 00:06:47.660 align:start position:0% quite simple so we have for our P 00:06:47.660 --> 00:06:50.110 align:start position:0% quite simple so we have for our P encoding<00:06:48.140> currently<00:06:48.620> lunge<00:06:49.280> silenced<00:06:49.940> or 00:06:50.110 --> 00:06:50.120 align:start position:0% encoding currently lunge silenced or 00:06:50.120 --> 00:06:51.820 align:start position:0% encoding currently lunge silenced or root<00:06:50.360> code<00:06:50.630> hash<00:06:50.840> which<00:06:51.110> aside<00:06:51.470> another 00:06:51.820 --> 00:06:51.830 align:start position:0% root code hash which aside another 00:06:51.830 --> 00:06:54.190 align:start position:0% root code hash which aside another inversion<00:06:52.250> and<00:06:52.580> we<00:06:53.330> use<00:06:53.660> that<00:06:53.690> to<00:06:53.900> determine 00:06:54.190 --> 00:06:54.200 align:start position:0% inversion and we use that to determine 00:06:54.200 --> 00:06:56.980 align:start position:0% inversion and we use that to determine the<00:06:54.560> words<00:06:54.800> or<00:06:54.980> three<00:06:55.220> amigos 00:06:56.980 --> 00:06:56.990 align:start position:0% the words or three amigos 00:06:56.990 --> 00:07:00.930 align:start position:0% the words or three amigos so<00:06:57.380> later<00:06:57.590> this<00:06:57.830> is<00:06:57.890> expanded<00:06:58.880> into<00:06:59.530> 7002 00:07:00.930 --> 00:07:00.940 align:start position:0% so later this is expanded into 7002 00:07:00.940 --> 00:07:04.990 align:start position:0% so later this is expanded into 7002 and<00:07:02.470> this<00:07:03.470> is<00:07:03.620> actually<00:07:04.250> quite<00:07:04.310> robust<00:07:04.760> and 00:07:04.990 --> 00:07:05.000 align:start position:0% and this is actually quite robust and 00:07:05.000 --> 00:07:08.590 align:start position:0% and this is actually quite robust and entirely<00:07:05.690> backward<00:07:06.110> compatible<00:07:06.880> so<00:07:07.880> there<00:07:08.510> is 00:07:08.590 --> 00:07:08.600 align:start position:0% entirely backward compatible so there is 00:07:08.600 --> 00:07:11.620 align:start position:0% entirely backward compatible so there is also<00:07:09.020> strongly<00:07:09.560> favored<00:07:10.010> by<00:07:10.250> the<00:07:10.280> six<00:07:11.150> one 00:07:11.620 --> 00:07:11.630 align:start position:0% also strongly favored by the six one 00:07:11.630 --> 00:07:14.980 align:start position:0% also strongly favored by the six one five<00:07:12.200> team<00:07:13.270> during<00:07:14.270> the<00:07:14.510> recent<00:07:14.720> board 00:07:14.980 --> 00:07:14.990 align:start position:0% five team during the recent board 00:07:14.990 --> 00:07:17.410 align:start position:0% five team during the recent board discussion<00:07:15.520> we<00:07:16.520> had<00:07:16.700> less<00:07:16.940> culture<00:07:17.360> in 00:07:17.410 --> 00:07:17.420 align:start position:0% discussion we had less culture in 00:07:17.420 --> 00:07:20.530 align:start position:0% discussion we had less culture in science<00:07:17.780> right<00:07:17.990> if<00:07:18.200> so<00:07:18.410> now<00:07:18.650> cast<00:07:19.040> and<00:07:19.540> party 00:07:20.530 --> 00:07:20.540 align:start position:0% science right if so now cast and party 00:07:20.540 --> 00:07:25.030 align:start position:0% science right if so now cast and party and<00:07:20.840> I<00:07:21.170> believe<00:07:21.470> another<00:07:21.800> and<00:07:22.720> AR<00:07:23.720> th<00:07:23.990> of<00:07:24.380> Oh 00:07:25.030 --> 00:07:25.040 align:start position:0% and I believe another and AR th of Oh 00:07:25.040 --> 00:07:30.870 align:start position:0% and I believe another and AR th of Oh half<00:07:25.660> of<00:07:26.660> TR<00:07:26.990> open<00:07:27.320> for<00:07:28.010> this<00:07:28.670> conversion<00:07:29.630> II 00:07:30.870 --> 00:07:30.880 align:start position:0% half of TR open for this conversion II 00:07:30.880 --> 00:07:35.110 align:start position:0% half of TR open for this conversion II implementation<00:07:32.170> is<00:07:33.170> also<00:07:33.490> slightly<00:07:34.490> good<00:07:34.820> for 00:07:35.110 --> 00:07:35.120 align:start position:0% implementation is also slightly good for 00:07:35.120 --> 00:07:37.180 align:start position:0% implementation is also slightly good for the<00:07:35.330> storage<00:07:35.750> proposal<00:07:36.470> because<00:07:36.830> now<00:07:37.130> you 00:07:37.180 --> 00:07:37.190 align:start position:0% the storage proposal because now you 00:07:37.190 --> 00:07:39.250 align:start position:0% the storage proposal because now you have<00:07:37.340> used<00:07:37.790> this<00:07:38.030> version<00:07:38.720> field<00:07:38.930> to 00:07:39.250 --> 00:07:39.260 align:start position:0% have used this version field to 00:07:39.260 --> 00:07:43.030 align:start position:0% have used this version field to determine<00:07:40.750> determine<00:07:41.750> what<00:07:42.290> the<00:07:42.470> rest<00:07:42.680> of<00:07:42.860> the 00:07:43.030 --> 00:07:43.040 align:start position:0% determine determine what the rest of the 00:07:43.040 --> 00:07:45.730 align:start position:0% determine determine what the rest of the arc<00:07:43.250> you<00:07:43.340> feel<00:07:43.730> that<00:07:44.000> story<00:07:44.390> might<00:07:44.810> act<00:07:44.990> means 00:07:45.730 --> 00:07:45.740 align:start position:0% arc you feel that story might act means 00:07:45.740 --> 00:07:48.520 align:start position:0% arc you feel that story might act means so<00:07:46.070> if<00:07:46.430> we<00:07:47.090> provide<00:07:47.450> some<00:07:47.630> semantics<00:07:48.140> for<00:07:48.260> them 00:07:48.520 --> 00:07:48.530 align:start position:0% so if we provide some semantics for them 00:07:48.530 --> 00:07:50.830 align:start position:0% so if we provide some semantics for them and<00:07:48.800> it's<00:07:49.550> a<00:07:49.640> current<00:07:49.970> selected<00:07:50.570> are 00:07:50.830 --> 00:07:50.840 align:start position:0% and it's a current selected are 00:07:50.840 --> 00:07:54.640 align:start position:0% and it's a current selected are conversing<00:07:51.350> in<00:07:51.440> solution<00:07:52.930> so<00:07:53.930> for 00:07:54.640 --> 00:07:54.650 align:start position:0% conversing in solution so for 00:07:54.650 --> 00:07:56.650 align:start position:0% conversing in solution so for completeness<00:07:55.100> there's<00:07:55.550> also<00:07:55.790> one<00:07:56.330> thing<00:07:56.510> we 00:07:56.650 --> 00:07:56.660 align:start position:0% completeness there's also one thing we 00:07:56.660 --> 00:07:59.530 align:start position:0% completeness there's also one thing we need<00:07:56.720> to<00:07:56.840> talk<00:07:57.050> about<00:07:57.110> is<00:07:57.740> about<00:07:58.370> using<00:07:59.270> this 00:07:59.530 --> 00:07:59.540 align:start position:0% need to talk about is about using this 00:07:59.540 --> 00:08:03.670 align:start position:0% need to talk about is about using this portion<00:08:00.040> then<00:08:01.040> how<00:08:01.730> what<00:08:02.600> is<00:08:02.720> the<00:08:02.750> version<00:08:03.140> the 00:08:03.670 --> 00:08:03.680 align:start position:0% portion then how what is the version the 00:08:03.680 --> 00:08:05.590 align:start position:0% portion then how what is the version the child<00:08:03.950> contracts<00:08:04.490> that<00:08:04.730> created<00:08:05.120> five<00:08:05.330> heart 00:08:05.590 --> 00:08:05.600 align:start position:0% child contracts that created five heart 00:08:05.600 --> 00:08:09.580 align:start position:0% child contracts that created five heart contracts<00:08:06.160> so<00:08:07.160> in<00:08:07.880> yaki<00:08:08.480> 7002<00:08:08.960> they<00:08:09.350> speak 00:08:09.580 --> 00:08:09.590 align:start position:0% contracts so in yaki 7002 they speak 00:08:09.590 --> 00:08:12.640 align:start position:0% contracts so in yaki 7002 they speak what<00:08:10.040> kind<00:08:10.280> of<00:08:10.400> Concord<00:08:10.880> family<00:08:11.240> and<00:08:11.450> later<00:08:12.380> we 00:08:12.640 --> 00:08:12.650 align:start position:0% what kind of Concord family and later we 00:08:12.650 --> 00:08:15.430 align:start position:0% what kind of Concord family and later we can<00:08:12.860> discount<00:08:13.730> Rama<00:08:14.120> can<00:08:14.450> be<00:08:14.570> extended<00:08:14.930> so<00:08:15.260> we 00:08:15.430 --> 00:08:15.440 align:start position:0% can discount Rama can be extended so we 00:08:15.440 --> 00:08:17.920 align:start position:0% can discount Rama can be extended so we can<00:08:15.620> have<00:08:15.830> some<00:08:16.070> extensions<00:08:16.880> to<00:08:17.150> Yankee<00:08:17.720> from 00:08:17.920 --> 00:08:17.930 align:start position:0% can have some extensions to Yankee from 00:08:17.930 --> 00:08:21.240 align:start position:0% can have some extensions to Yankee from Teochew<00:08:18.290> that<00:08:19.330> allows<00:08:20.330> different 00:08:21.240 --> 00:08:21.250 align:start position:0% Teochew that allows different 00:08:21.250 --> 00:08:24.280 align:start position:0% Teochew that allows different conversions<00:08:22.250> to<00:08:22.430> be<00:08:22.550> created<00:08:22.940> but<00:08:23.750> it's<00:08:23.990> easy 00:08:24.280 --> 00:08:24.290 align:start position:0% conversions to be created but it's easy 00:08:24.290 --> 00:08:26.650 align:start position:0% conversions to be created but it's easy for<00:08:24.440> companies<00:08:24.950> so<00:08:25.100> we<00:08:25.250> can<00:08:25.400> release<00:08:25.700> this<00:08:25.850> if 00:08:26.650 --> 00:08:26.660 align:start position:0% for companies so we can release this if 00:08:26.660 --> 00:08:29.560 align:start position:0% for companies so we can release this if you<00:08:26.840> want<00:08:27.610> and<00:08:28.610> then<00:08:28.850> we<00:08:29.000> have<00:08:29.210> the<00:08:29.390> version 00:08:29.560 --> 00:08:29.570 align:start position:0% you want and then we have the version 00:08:29.570 --> 00:08:33.520 align:start position:0% you want and then we have the version list<00:08:29.990> evn<00:08:31.450> so<00:08:32.450> what<00:08:32.990> we<00:08:33.110> are<00:08:33.200> talking<00:08:33.350> about 00:08:33.520 --> 00:08:33.530 align:start position:0% list evn so what we are talking about 00:08:33.530 --> 00:08:36.280 align:start position:0% list evn so what we are talking about here<00:08:33.980> is<00:08:34.100> really<00:08:34.360> if<00:08:35.360> we<00:08:35.540> only<00:08:35.720> have<00:08:35.960> a<00:08:36.020> count 00:08:36.280 --> 00:08:36.290 align:start position:0% here is really if we only have a count 00:08:36.290 --> 00:08:36.790 align:start position:0% here is really if we only have a count versioning 00:08:36.790 --> 00:08:36.800 align:start position:0% versioning 00:08:36.800 --> 00:08:39.520 align:start position:0% versioning so<00:08:36.980> issue<00:08:37.190> is<00:08:37.550> every<00:08:38.060> six<00:08:38.270> months<00:08:38.600> we<00:08:38.960> want<00:08:39.380> to 00:08:39.520 --> 00:08:39.530 align:start position:0% so issue is every six months we want to 00:08:39.530 --> 00:08:42.250 align:start position:0% so issue is every six months we want to deploy<00:08:39.920> a<00:08:39.950> new<00:08:39.980> version<00:08:40.600> that<00:08:41.600> for<00:08:41.840> some<00:08:42.050> teams 00:08:42.250 --> 00:08:42.260 align:start position:0% deploy a new version that for some teams 00:08:42.260 --> 00:08:44.830 align:start position:0% deploy a new version that for some teams is<00:08:42.530> not<00:08:42.890> so<00:08:43.100> sensible<00:08:43.610> so<00:08:43.970> that<00:08:44.420> that<00:08:44.660> is<00:08:44.810> a 00:08:44.830 --> 00:08:44.840 align:start position:0% is not so sensible so that that is a 00:08:44.840 --> 00:08:46.960 align:start position:0% is not so sensible so that that is a huge<00:08:44.960> pushback<00:08:45.470> during<00:08:46.460> this<00:08:46.640> time 00:08:46.960 --> 00:08:46.970 align:start position:0% huge pushback during this time 00:08:46.970 --> 00:08:49.319 align:start position:0% huge pushback during this time for<00:08:47.540> discussion<00:08:47.750> some<00:08:48.350> people<00:08:48.920> just<00:08:49.100> think 00:08:49.319 --> 00:08:49.329 align:start position:0% for discussion some people just think 00:08:49.329 --> 00:08:52.540 align:start position:0% for discussion some people just think our<00:08:50.329> conversion<00:08:50.810> is<00:08:50.930> cool<00:08:51.110> but<00:08:51.290> if<00:08:52.040> we<00:08:52.250> need<00:08:52.430> to 00:08:52.540 --> 00:08:52.550 align:start position:0% our conversion is cool but if we need to 00:08:52.550 --> 00:08:55.780 align:start position:0% our conversion is cool but if we need to mention<00:08:52.730> too<00:08:53.089> many<00:08:53.240> conversions<00:08:54.230> and<00:08:54.639> that<00:08:55.639> is 00:08:55.780 --> 00:08:55.790 align:start position:0% mention too many conversions and that is 00:08:55.790 --> 00:08:58.329 align:start position:0% mention too many conversions and that is a<00:08:55.819> huge<00:08:56.180> maintenance<00:08:57.079> cost<00:08:57.350> and<00:08:57.560> we<00:08:57.889> may<00:08:58.040> not 00:08:58.329 --> 00:08:58.339 align:start position:0% a huge maintenance cost and we may not 00:08:58.339 --> 00:09:01.179 align:start position:0% a huge maintenance cost and we may not want<00:08:58.579> to<00:08:58.639> do<00:08:58.790> that<00:08:59.019> so<00:09:00.019> version<00:09:00.379> is<00:09:00.500> VM<00:09:00.980> is 00:09:01.179 --> 00:09:01.189 align:start position:0% want to do that so version is VM is 00:09:01.189 --> 00:09:06.009 align:start position:0% want to do that so version is VM is fixed<00:09:02.060> to<00:09:02.389> try<00:09:02.569> to<00:09:02.629> authorize<00:09:03.019> lads<00:09:04.540> so<00:09:05.540> what 00:09:06.009 --> 00:09:06.019 align:start position:0% fixed to try to authorize lads so what 00:09:06.019 --> 00:09:08.470 align:start position:0% fixed to try to authorize lads so what we<00:09:06.199> do<00:09:06.350> is<00:09:06.529> we<00:09:06.769> design<00:09:06.920> design<00:09:07.759> things<00:09:08.029> ways 00:09:08.470 --> 00:09:08.480 align:start position:0% we do is we design design things ways 00:09:08.480 --> 00:09:11.800 align:start position:0% we do is we design design things ways for<00:09:08.720> workability<00:09:09.170> diamond<00:09:09.819> and<00:09:10.819> we<00:09:11.389> remove 00:09:11.800 --> 00:09:11.810 align:start position:0% for workability diamond and we remove 00:09:11.810 --> 00:09:14.679 align:start position:0% for workability diamond and we remove some<00:09:11.990> offenders<00:09:12.470> that<00:09:13.189> Greeks<00:09:13.639> buy<00:09:14.089> property 00:09:14.679 --> 00:09:14.689 align:start position:0% some offenders that Greeks buy property 00:09:14.689 --> 00:09:18.429 align:start position:0% some offenders that Greeks buy property in<00:09:14.959> the<00:09:15.110> VM<00:09:15.850> so<00:09:16.850> in<00:09:17.420> the<00:09:17.569> end<00:09:17.660> we<00:09:17.930> just<00:09:17.959> have<00:09:18.259> one 00:09:18.429 --> 00:09:18.439 align:start position:0% in the VM so in the end we just have one 00:09:18.439 --> 00:09:22.059 align:start position:0% in the VM so in the end we just have one inversion<00:09:18.980> so<00:09:19.279> so<00:09:20.029> the<00:09:20.509> current<00:09:20.839> UV<00:09:21.649> immersion 00:09:22.059 --> 00:09:22.069 align:start position:0% inversion so so the current UV immersion 00:09:22.069 --> 00:09:24.220 align:start position:0% inversion so so the current UV immersion will<00:09:22.250> be<00:09:22.399> the<00:09:22.519> legacy<00:09:22.670> version<00:09:23.209> and<00:09:23.389> we<00:09:24.019> just 00:09:24.220 --> 00:09:24.230 align:start position:0% will be the legacy version and we just 00:09:24.230 --> 00:09:25.749 align:start position:0% will be the legacy version and we just have<00:09:24.350> one<00:09:24.589> more<00:09:24.620> version<00:09:24.980> which<00:09:25.550> is<00:09:25.730> a 00:09:25.749 --> 00:09:25.759 align:start position:0% have one more version which is a 00:09:25.759 --> 00:09:28.179 align:start position:0% have one more version which is a personalized<00:09:26.300> evn<00:09:26.720> and<00:09:26.930> we<00:09:27.589> can<00:09:27.800> add<00:09:28.040> new 00:09:28.179 --> 00:09:28.189 align:start position:0% personalized evn and we can add new 00:09:28.189 --> 00:09:30.220 align:start position:0% personalized evn and we can add new features<00:09:28.430> change<00:09:29.120> guys<00:09:29.360> goes<00:09:29.600> on<00:09:29.870> that 00:09:30.220 --> 00:09:30.230 align:start position:0% features change guys goes on that 00:09:30.230 --> 00:09:36.819 align:start position:0% features change guys goes on that conversion<00:09:31.930> so<00:09:32.930> talking<00:09:33.350> about<00:09:34.509> like<00:09:35.829> general 00:09:36.819 --> 00:09:36.829 align:start position:0% conversion so talking about like general 00:09:36.829 --> 00:09:39.040 align:start position:0% conversion so talking about like general things<00:09:37.339> about<00:09:37.519> interface<00:09:38.329> design<00:09:38.779> there's 00:09:39.040 --> 00:09:39.050 align:start position:0% things about interface design there's 00:09:39.050 --> 00:09:40.329 align:start position:0% things about interface design there's something<00:09:39.439> really<00:09:39.620> important<00:09:40.069> it's<00:09:40.160> called 00:09:40.329 --> 00:09:40.339 align:start position:0% something really important it's called 00:09:40.339 --> 00:09:43.329 align:start position:0% something really important it's called form<00:09:40.550> so<00:09:40.759> it<00:09:41.480> basically<00:09:41.629> said<00:09:42.410> that<00:09:42.439> if<00:09:42.980> you 00:09:43.329 --> 00:09:43.339 align:start position:0% form so it basically said that if you 00:09:43.339 --> 00:09:46.119 align:start position:0% form so it basically said that if you have<00:09:43.519> a<00:09:43.550> sufficient<00:09:44.329> number<00:09:44.810> of<00:09:44.839> users<00:09:45.350> so<00:09:46.040> it 00:09:46.119 --> 00:09:46.129 align:start position:0% have a sufficient number of users so it 00:09:46.129 --> 00:09:48.460 align:start position:0% have a sufficient number of users so it really<00:09:46.370> doesn't<00:09:46.550> matter<00:09:46.790> what<00:09:47.180> you<00:09:47.470> promised 00:09:48.460 --> 00:09:48.470 align:start position:0% really doesn't matter what you promised 00:09:48.470 --> 00:09:51.549 align:start position:0% really doesn't matter what you promised in<00:09:49.129> the<00:09:49.370> API<00:09:49.639> like<00:09:49.970> all<00:09:50.209> the<00:09:50.559> observable 00:09:51.549 --> 00:09:51.559 align:start position:0% in the API like all the observable 00:09:51.559 --> 00:09:54.579 align:start position:0% in the API like all the observable behaviors<00:09:52.129> in<00:09:52.459> your<00:09:52.670> system<00:09:53.139> will<00:09:54.139> be<00:09:54.259> used<00:09:54.439> by 00:09:54.579 --> 00:09:54.589 align:start position:0% behaviors in your system will be used by 00:09:54.589 --> 00:09:58.780 align:start position:0% behaviors in your system will be used by someone<00:09:54.980> so<00:09:56.379> so<00:09:57.379> assume<00:09:57.769> with<00:09:58.009> definitely<00:09:58.550> has 00:09:58.780 --> 00:09:58.790 align:start position:0% someone so so assume with definitely has 00:09:58.790 --> 00:10:01.660 align:start position:0% someone so so assume with definitely has sufficient<00:09:59.529> number<00:10:00.529> of<00:10:00.589> users<00:10:01.069> so<00:10:01.399> here 00:10:01.660 --> 00:10:01.670 align:start position:0% sufficient number of users so here 00:10:01.670 --> 00:10:05.199 align:start position:0% sufficient number of users so here install<00:10:02.000> definitely<00:10:02.480> applied<00:10:02.750> to<00:10:02.930> us<00:10:03.079> and<00:10:04.209> I 00:10:05.199 --> 00:10:05.209 align:start position:0% install definitely applied to us and I 00:10:05.209 --> 00:10:08.259 align:start position:0% install definitely applied to us and I mean<00:10:06.019> during<00:10:06.829> the<00:10:07.100> back<00:10:07.250> recovery<00:10:07.699> discussion 00:10:08.259 --> 00:10:08.269 align:start position:0% mean during the back recovery discussion 00:10:08.269 --> 00:10:10.329 align:start position:0% mean during the back recovery discussion many<00:10:08.600> people<00:10:09.050> man<00:10:09.379> equality<00:10:09.920> well<00:10:10.040> first 00:10:10.329 --> 00:10:10.339 align:start position:0% many people man equality well first 00:10:10.339 --> 00:10:12.509 align:start position:0% many people man equality well first we're<00:10:10.550> talking<00:10:10.939> about<00:10:11.149> the<00:10:11.930> promise<00:10:12.350> of 00:10:12.509 --> 00:10:12.519 align:start position:0% we're talking about the promise of 00:10:12.519 --> 00:10:16.929 align:start position:0% we're talking about the promise of million<00:10:13.519> of<00:10:13.790> your<00:10:14.389> money<00:10:14.689> via<00:10:15.220> the<00:10:16.220> issue<00:10:16.399> is 00:10:16.929 --> 00:10:16.939 align:start position:0% million of your money via the issue is 00:10:16.939 --> 00:10:20.499 align:start position:0% million of your money via the issue is that<00:10:17.259> there<00:10:18.259> will<00:10:18.439> be<00:10:18.470> someone<00:10:18.829> who<00:10:19.509> that 00:10:20.499 --> 00:10:20.509 align:start position:0% that there will be someone who that 00:10:20.509 --> 00:10:23.499 align:start position:0% that there will be someone who that don't<00:10:20.779> follow<00:10:21.019> the<00:10:21.319> promise<00:10:22.160> or<00:10:22.399> if<00:10:22.699> something 00:10:23.499 --> 00:10:23.509 align:start position:0% don't follow the promise or if something 00:10:23.509 --> 00:10:25.840 align:start position:0% don't follow the promise or if something is<00:10:23.689> bad<00:10:24.019> practice<00:10:24.769> in<00:10:24.949> the<00:10:25.040> past<00:10:25.250> it<00:10:25.519> may<00:10:25.670> not 00:10:25.840 --> 00:10:25.850 align:start position:0% is bad practice in the past it may not 00:10:25.850 --> 00:10:30.400 align:start position:0% is bad practice in the past it may not be<00:10:26.000> best<00:10:26.870> practice<00:10:27.319> in<00:10:27.439> the<00:10:27.500> future<00:10:28.660> so<00:10:29.660> what 00:10:30.400 --> 00:10:30.410 align:start position:0% be best practice in the future so what 00:10:30.410 --> 00:10:32.379 align:start position:0% be best practice in the future so what I'm<00:10:30.559> saying<00:10:30.829> here<00:10:30.980> is<00:10:31.399> that<00:10:31.670> instead<00:10:32.180> of<00:10:32.329> doing 00:10:32.379 --> 00:10:32.389 align:start position:0% I'm saying here is that instead of doing 00:10:32.389 --> 00:10:35.110 align:start position:0% I'm saying here is that instead of doing all<00:10:32.750> the<00:10:32.990> social<00:10:33.529> promising<00:10:34.129> maybe<00:10:34.759> you<00:10:34.939> can 00:10:35.110 --> 00:10:35.120 align:start position:0% all the social promising maybe you can 00:10:35.120 --> 00:10:37.319 align:start position:0% all the social promising maybe you can just<00:10:35.269> use<00:10:35.509> some<00:10:35.720> social<00:10:35.959> engineering 00:10:37.319 --> 00:10:37.329 align:start position:0% just use some social engineering 00:10:37.329 --> 00:10:40.449 align:start position:0% just use some social engineering techniques<00:10:38.329> to<00:10:38.660> fix<00:10:38.899> those<00:10:39.079> issues<00:10:39.230> so<00:10:39.649> the 00:10:40.449 --> 00:10:40.459 align:start position:0% techniques to fix those issues so the 00:10:40.459 --> 00:10:42.100 align:start position:0% techniques to fix those issues so the fix<00:10:40.670> is<00:10:40.819> quite<00:10:41.029> simple<00:10:41.329> we<00:10:41.449> just<00:10:41.569> remove<00:10:41.990> all 00:10:42.100 --> 00:10:42.110 align:start position:0% fix is quite simple we just remove all 00:10:42.110 --> 00:10:45.160 align:start position:0% fix is quite simple we just remove all those<00:10:43.149> observed<00:10:44.149> behavior<00:10:44.600> that<00:10:44.750> we<00:10:44.959> don't 00:10:45.160 --> 00:10:45.170 align:start position:0% those observed behavior that we don't 00:10:45.170 --> 00:10:49.840 align:start position:0% those observed behavior that we don't want<00:10:45.439> smart<00:10:45.800> contracts<00:10:46.250> to<00:10:46.339> absorb<00:10:48.579> so<00:10:49.579> the 00:10:49.840 --> 00:10:49.850 align:start position:0% want smart contracts to absorb so the 00:10:49.850 --> 00:10:52.269 align:start position:0% want smart contracts to absorb so the biggest<00:10:50.180> offender<00:10:50.509> is<00:10:50.809> recently<00:10:51.500> gas<00:10:51.680> cost<00:10:51.949> so 00:10:52.269 --> 00:10:52.279 align:start position:0% biggest offender is recently gas cost so 00:10:52.279 --> 00:10:55.540 align:start position:0% biggest offender is recently gas cost so we<00:10:52.459> actually<00:10:52.879> I<00:10:53.839> mean<00:10:54.439> a<00:10:54.740> lot<00:10:55.069> of<00:10:55.100> core 00:10:55.540 --> 00:10:55.550 align:start position:0% we actually I mean a lot of core 00:10:55.550 --> 00:10:57.970 align:start position:0% we actually I mean a lot of core developers<00:10:56.059> has<00:10:56.329> expired<00:10:56.990> that<00:10:57.259> smart 00:10:57.970 --> 00:10:57.980 align:start position:0% developers has expired that smart 00:10:57.980 --> 00:10:58.800 align:start position:0% developers has expired that smart comfort<00:10:58.399> food 00:10:58.800 --> 00:10:58.810 align:start position:0% comfort food 00:10:58.810 --> 00:11:01.019 align:start position:0% comfort food make<00:10:58.960> any<00:10:59.170> assumptions<00:10:59.920> about<00:11:00.100> gas<00:11:00.700> costs 00:11:01.019 --> 00:11:01.029 align:start position:0% make any assumptions about gas costs 00:11:01.029 --> 00:11:03.710 align:start position:0% make any assumptions about gas costs because<00:11:01.330> cash<00:11:01.630> cows<00:11:01.870> can<00:11:02.170> change<00:11:02.410> a<00:11:02.710> lot<00:11:03.040> and 00:11:03.710 --> 00:11:03.720 align:start position:0% because cash cows can change a lot and 00:11:03.720 --> 00:11:07.620 align:start position:0% because cash cows can change a lot and so<00:11:04.720> we<00:11:04.900> just<00:11:05.050> remove<00:11:05.920> any<00:11:06.250> observe<00:11:06.880> observe 00:11:07.620 --> 00:11:07.630 align:start position:0% so we just remove any observe observe 00:11:07.630 --> 00:11:12.870 align:start position:0% so we just remove any observe observe behavior<00:11:08.529> within<00:11:08.890> the<00:11:09.400> um<00:11:09.820> about<00:11:10.270> gas<00:11:10.690> cost<00:11:11.880> in 00:11:12.870 --> 00:11:12.880 align:start position:0% behavior within the um about gas cost in 00:11:12.880 --> 00:11:15.150 align:start position:0% behavior within the um about gas cost in detail<00:11:13.240> is<00:11:13.360> basically<00:11:13.779> removing<00:11:14.320> the<00:11:14.650> gas<00:11:14.830> of 00:11:15.150 --> 00:11:15.160 align:start position:0% detail is basically removing the gas of 00:11:15.160 --> 00:11:17.550 align:start position:0% detail is basically removing the gas of code<00:11:15.580> and<00:11:15.850> for<00:11:16.510> calc<00:11:16.930> alcohol 00:11:17.550 --> 00:11:17.560 align:start position:0% code and for calc alcohol 00:11:17.560 --> 00:11:19.410 align:start position:0% code and for calc alcohol delegate<00:11:17.980> car<00:11:18.190> we<00:11:18.400> just<00:11:18.430> take<00:11:18.910> it<00:11:19.060> take<00:11:19.270> the 00:11:19.410 --> 00:11:19.420 align:start position:0% delegate car we just take it take the 00:11:19.420 --> 00:11:22.350 align:start position:0% delegate car we just take it take the fuel<00:11:19.600> gas<00:11:19.830> and<00:11:20.830> if<00:11:20.980> any<00:11:21.279> cost<00:11:21.610> act<00:11:21.850> is<00:11:22.060> out<00:11:22.330> of 00:11:22.350 --> 00:11:22.360 align:start position:0% fuel gas and if any cost act is out of 00:11:22.360 --> 00:11:25.920 align:start position:0% fuel gas and if any cost act is out of gas<00:11:22.660> and<00:11:23.110> we<00:11:23.200> just<00:11:23.670> reverse<00:11:24.670> all<00:11:25.060> of<00:11:25.450> the<00:11:25.720> cows 00:11:25.920 --> 00:11:25.930 align:start position:0% gas and we just reverse all of the cows 00:11:25.930 --> 00:11:29.100 align:start position:0% gas and we just reverse all of the cows tax<00:11:26.279> the<00:11:27.279> third<00:11:27.550> item<00:11:27.820> is<00:11:28.150> because<00:11:28.360> we<00:11:28.870> don't 00:11:29.100 --> 00:11:29.110 align:start position:0% tax the third item is because we don't 00:11:29.110 --> 00:11:33.090 align:start position:0% tax the third item is because we don't want<00:11:29.350> to<00:11:29.610> accidentally<00:11:30.610> reveal<00:11:31.740> the<00:11:32.740> current 00:11:33.090 --> 00:11:33.100 align:start position:0% want to accidentally reveal the current 00:11:33.100 --> 00:11:37.470 align:start position:0% want to accidentally reveal the current gas<00:11:33.370> information<00:11:34.890> for<00:11:35.890> an<00:11:36.190> apparent<00:11:36.910> contract 00:11:37.470 --> 00:11:37.480 align:start position:0% gas information for an apparent contract 00:11:37.480 --> 00:11:40.640 align:start position:0% gas information for an apparent contract if<00:11:37.660> a<00:11:37.779> child<00:11:38.050> contracts<00:11:38.589> succeed<00:11:39.279> or<00:11:39.460> fails 00:11:40.640 --> 00:11:40.650 align:start position:0% if a child contracts succeed or fails 00:11:40.650 --> 00:11:44.610 align:start position:0% if a child contracts succeed or fails so<00:11:41.650> we<00:11:41.920> also<00:11:42.100> deny<00:11:43.089> any<00:11:43.450> use<00:11:43.839> of<00:11:43.870> codes<00:11:44.350> to 00:11:44.610 --> 00:11:44.620 align:start position:0% so we also deny any use of codes to 00:11:44.620 --> 00:11:47.880 align:start position:0% so we also deny any use of codes to beatified<00:11:45.570> so<00:11:46.570> this<00:11:47.140> is<00:11:47.290> basically<00:11:47.650> the<00:11:47.800> idea 00:11:47.880 --> 00:11:47.890 align:start position:0% beatified so this is basically the idea 00:11:47.890 --> 00:11:51.780 align:start position:0% beatified so this is basically the idea idea<00:11:48.580> extremely<00:11:49.480> simple<00:11:50.070> validation<00:11:51.070> process 00:11:51.780 --> 00:11:51.790 align:start position:0% idea extremely simple validation process 00:11:51.790 --> 00:11:55.110 align:start position:0% idea extremely simple validation process between<00:11:52.029> contract<00:11:52.600> deployment<00:11:53.110> so<00:11:54.000> in<00:11:55.000> this 00:11:55.110 --> 00:11:55.120 align:start position:0% between contract deployment so in this 00:11:55.120 --> 00:11:56.970 align:start position:0% between contract deployment so in this case<00:11:55.360> we<00:11:55.570> have<00:11:55.750> made<00:11:55.960> future<00:11:56.410> upgrades<00:11:56.860> that 00:11:56.970 --> 00:11:56.980 align:start position:0% case we have made future upgrades that 00:11:56.980 --> 00:11:59.220 align:start position:0% case we have made future upgrades that added<00:11:57.520> additional<00:11:58.240> of<00:11:58.450> course<00:11:58.690> much<00:11:58.990> more 00:11:59.220 --> 00:11:59.230 align:start position:0% added additional of course much more 00:11:59.230 --> 00:12:01.950 align:start position:0% added additional of course much more safer<00:11:59.620> so<00:12:00.490> there<00:12:00.730> are<00:12:00.760> extra<00:12:01.390> goodies<00:12:01.660> for 00:12:01.950 --> 00:12:01.960 align:start position:0% safer so there are extra goodies for 00:12:01.960 --> 00:12:04.320 align:start position:0% safer so there are extra goodies for example<00:12:02.350> we<00:12:02.500> have<00:12:03.190> a<00:12:03.220> hash<00:12:03.670> feature<00:12:03.940> probe 00:12:04.320 --> 00:12:04.330 align:start position:0% example we have a hash feature probe 00:12:04.330 --> 00:12:07.050 align:start position:0% example we have a hash feature probe which<00:12:05.290> makes<00:12:05.620> some<00:12:05.980> contract<00:12:06.520> can<00:12:06.700> be<00:12:06.820> pretty 00:12:07.050 --> 00:12:07.060 align:start position:0% which makes some contract can be pretty 00:12:07.060 --> 00:12:10.290 align:start position:0% which makes some contract can be pretty fly<00:12:07.450> dong<00:12:07.690> Chan<00:12:08.589> that<00:12:09.580> can<00:12:09.730> later<00:12:09.940> take 00:12:10.290 --> 00:12:10.300 align:start position:0% fly dong Chan that can later take 00:12:10.300 --> 00:12:14.910 align:start position:0% fly dong Chan that can later take advantage<00:12:11.080> of<00:12:11.380> new<00:12:11.770> feature<00:12:12.010> upgrades<00:12:13.920> so 00:12:14.910 --> 00:12:14.920 align:start position:0% advantage of new feature upgrades so 00:12:14.920 --> 00:12:17.160 align:start position:0% advantage of new feature upgrades so using<00:12:15.550> a<00:12:15.580> conversion<00:12:16.000> inadvertently<00:12:16.780> samia 00:12:17.160 --> 00:12:17.170 align:start position:0% using a conversion inadvertently samia 00:12:17.170 --> 00:12:20.329 align:start position:0% using a conversion inadvertently samia may<00:12:17.530> actually<00:12:17.800> have<00:12:18.339> a<00:12:18.370> pretty<00:12:18.940> robust 00:12:20.329 --> 00:12:20.339 align:start position:0% may actually have a pretty robust 00:12:20.339 --> 00:12:24.960 align:start position:0% may actually have a pretty robust backward-compatible<00:12:23.250> solutions<00:12:24.250> for<00:12:24.880> you 00:12:24.960 --> 00:12:24.970 align:start position:0% backward-compatible solutions for you 00:12:24.970 --> 00:12:29.310 align:start position:0% backward-compatible solutions for you serum<00:12:25.589> so<00:12:26.820> using<00:12:27.820> this<00:12:27.970> we<00:12:28.750> now<00:12:28.930> can<00:12:29.110> freely 00:12:29.310 --> 00:12:29.320 align:start position:0% serum so using this we now can freely 00:12:29.320 --> 00:12:32.250 align:start position:0% serum so using this we now can freely change<00:12:29.589> guys<00:12:29.890> post<00:12:30.330> because<00:12:31.330> it's<00:12:31.750> now<00:12:32.020> an 00:12:32.250 --> 00:12:32.260 align:start position:0% change guys post because it's now an 00:12:32.260 --> 00:12:34.770 align:start position:0% change guys post because it's now an observable<00:12:33.250> behavior<00:12:33.730> and<00:12:33.910> no<00:12:34.120> contract<00:12:34.600> can 00:12:34.770 --> 00:12:34.780 align:start position:0% observable behavior and no contract can 00:12:34.780 --> 00:12:36.329 align:start position:0% observable behavior and no contract can depend<00:12:35.110> on<00:12:35.200> it 00:12:36.329 --> 00:12:36.339 align:start position:0% depend on it 00:12:36.339 --> 00:12:39.600 align:start position:0% depend on it introversion<00:12:36.910> listeria<00:12:37.780> question<00:12:38.460> we<00:12:39.460> can 00:12:39.600 --> 00:12:39.610 align:start position:0% introversion listeria question we can 00:12:39.610 --> 00:12:42.030 align:start position:0% introversion listeria question we can also<00:12:39.820> really<00:12:40.390> add<00:12:40.570> view<00:12:40.780> of<00:12:40.930> course<00:12:41.170> because 00:12:42.030 --> 00:12:42.040 align:start position:0% also really add view of course because 00:12:42.040 --> 00:12:45.300 align:start position:0% also really add view of course because now<00:12:42.490> it<00:12:42.670> is<00:12:42.760> throughout<00:12:43.150> the<00:12:43.600> deployment<00:12:44.440> of<00:12:44.980> a 00:12:45.300 --> 00:12:45.310 align:start position:0% now it is throughout the deployment of a 00:12:45.310 --> 00:12:48.690 align:start position:0% now it is throughout the deployment of a news<00:12:45.520> of<00:12:45.760> course<00:12:46.140> so<00:12:47.140> the<00:12:47.800> coverage<00:12:48.190> will<00:12:48.580> not 00:12:48.690 --> 00:12:48.700 align:start position:0% news of course so the coverage will not 00:12:48.700 --> 00:12:51.990 align:start position:0% news of course so the coverage will not be<00:12:48.820> an<00:12:48.910> issue<00:12:49.060> anymore<00:12:49.420> and<00:12:50.550> for<00:12:51.550> since<00:12:51.760> like 00:12:51.990 --> 00:12:52.000 align:start position:0% be an issue anymore and for since like 00:12:52.000 --> 00:12:54.180 align:start position:0% be an issue anymore and for since like statement<00:12:52.570> I'd<00:12:52.959> still<00:12:53.380> really<00:12:53.530> encounters 00:12:54.180 --> 00:12:54.190 align:start position:0% statement I'd still really encounters 00:12:54.190 --> 00:12:58.140 align:start position:0% statement I'd still really encounters from<00:12:54.310> the<00:12:54.520> state<00:12:54.730> but<00:12:56.339> for<00:12:57.339> all<00:12:57.610> the<00:12:57.820> rest<00:12:57.940> of 00:12:58.140 --> 00:12:58.150 align:start position:0% from the state but for all the rest of 00:12:58.150 --> 00:13:00.449 align:start position:0% from the state but for all the rest of the<00:12:58.300> parts<00:12:58.660> the<00:12:58.900> state<00:12:59.290> execution<00:13:00.010> they<00:13:00.250> can 00:13:00.449 --> 00:13:00.459 align:start position:0% the parts the state execution they can 00:13:00.459 --> 00:13:05.040 align:start position:0% the parts the state execution they can be<00:13:00.610> back<00:13:00.790> work<00:13:00.970> avoidable<00:13:03.209> it's<00:13:04.209> not<00:13:04.570> at<00:13:04.990> the 00:13:05.040 --> 00:13:05.050 align:start position:0% be back work avoidable it's not at the 00:13:05.050 --> 00:13:07.230 align:start position:0% be back work avoidable it's not at the operate<00:13:05.500> we<00:13:05.620> will<00:13:05.950> not<00:13:06.130> be<00:13:06.459> like<00:13:06.700> totally 00:13:07.230 --> 00:13:07.240 align:start position:0% operate we will not be like totally 00:13:07.240 --> 00:13:07.949 align:start position:0% operate we will not be like totally hassle-free 00:13:07.949 --> 00:13:07.959 align:start position:0% hassle-free 00:13:07.959 --> 00:13:09.570 align:start position:0% hassle-free there<00:13:08.560> are<00:13:08.680> something<00:13:09.040> we<00:13:09.130> need<00:13:09.250> to<00:13:09.280> care 00:13:09.570 --> 00:13:09.580 align:start position:0% there are something we need to care 00:13:09.580 --> 00:13:12.090 align:start position:0% there are something we need to care about<00:13:10.050> for<00:13:11.050> example 00:13:12.090 --> 00:13:12.100 align:start position:0% about for example 00:13:12.100 --> 00:13:14.070 align:start position:0% about for example we<00:13:12.250> need<00:13:12.400> to<00:13:12.490> change<00:13:12.700> this<00:13:13.030> already<00:13:13.420> compeller 00:13:14.070 --> 00:13:14.080 align:start position:0% we need to change this already compeller 00:13:14.080 --> 00:13:19.260 align:start position:0% we need to change this already compeller a<00:13:14.200> little<00:13:14.470> bit<00:13:14.670> so<00:13:15.670> that<00:13:15.810> we<00:13:16.810> can<00:13:17.400> use<00:13:18.400> because 00:13:19.260 --> 00:13:19.270 align:start position:0% a little bit so that we can use because 00:13:19.270 --> 00:13:20.880 align:start position:0% a little bit so that we can use because so<00:13:19.450> reading<00:13:19.660> compeller<00:13:20.020> actually<00:13:20.470> make<00:13:20.650> some 00:13:20.880 --> 00:13:20.890 align:start position:0% so reading compeller actually make some 00:13:20.890 --> 00:13:23.130 align:start position:0% so reading compeller actually make some assumptions<00:13:21.730> about<00:13:21.880> guys<00:13:22.210> post<00:13:22.480> and<00:13:22.750> we<00:13:22.930> need 00:13:23.130 --> 00:13:23.140 align:start position:0% assumptions about guys post and we need 00:13:23.140 --> 00:13:26.070 align:start position:0% assumptions about guys post and we need to<00:13:23.520> make<00:13:24.520> the<00:13:24.640> compeller<00:13:25.030> not<00:13:25.510> make<00:13:25.900> that 00:13:26.070 --> 00:13:26.080 align:start position:0% to make the compeller not make that 00:13:26.080 --> 00:13:28.260 align:start position:0% to make the compeller not make that those<00:13:26.380> assumptions<00:13:26.770> anymore 00:13:28.260 --> 00:13:28.270 align:start position:0% those assumptions anymore 00:13:28.270 --> 00:13:31.590 align:start position:0% those assumptions anymore the<00:13:28.720> second<00:13:29.020> issue<00:13:29.170> is<00:13:30.150> emergency<00:13:31.150> hard<00:13:31.390> work 00:13:31.590 --> 00:13:31.600 align:start position:0% the second issue is emergency hard work 00:13:31.600 --> 00:13:33.960 align:start position:0% the second issue is emergency hard work which<00:13:32.020> I<00:13:32.470> guess<00:13:32.920> probably<00:13:33.190> nobody<00:13:33.670> can<00:13:33.850> do 00:13:33.960 --> 00:13:33.970 align:start position:0% which I guess probably nobody can do 00:13:33.970 --> 00:13:35.850 align:start position:0% which I guess probably nobody can do anything<00:13:34.210> about<00:13:34.390> it<00:13:34.570> if<00:13:34.960> there<00:13:35.350> is<00:13:35.470> really<00:13:35.770> a 00:13:35.850 --> 00:13:35.860 align:start position:0% anything about it if there is really a 00:13:35.860 --> 00:13:38.940 align:start position:0% anything about it if there is really a denial<00:13:36.790> service<00:13:37.120> attack<00:13:37.450> I<00:13:37.930> assumed<00:13:38.680> and 00:13:38.940 --> 00:13:38.950 align:start position:0% denial service attack I assumed and 00:13:38.950 --> 00:13:41.190 align:start position:0% denial service attack I assumed and micro<00:13:39.850> Calgary<00:13:40.210> has<00:13:40.420> to<00:13:40.570> be<00:13:40.690> broken<00:13:40.930> because 00:13:41.190 --> 00:13:41.200 align:start position:0% micro Calgary has to be broken because 00:13:41.200 --> 00:13:45.060 align:start position:0% micro Calgary has to be broken because those<00:13:41.620> attack<00:13:42.240> contracts<00:13:43.240> cannot<00:13:43.770> exist<00:13:44.770> on 00:13:45.060 --> 00:13:45.070 align:start position:0% those attack contracts cannot exist on 00:13:45.070 --> 00:13:48.510 align:start position:0% those attack contracts cannot exist on chat<00:13:46.650> and<00:13:47.650> the<00:13:47.800> system<00:13:48.190> is<00:13:48.310> something 00:13:48.510 --> 00:13:48.520 align:start position:0% chat and the system is something 00:13:48.520 --> 00:13:51.150 align:start position:0% chat and the system is something actuaries<00:13:49.090> you<00:13:49.600> have<00:13:49.780> boundaries<00:13:50.110> so<00:13:50.890> in<00:13:51.040> this 00:13:51.150 --> 00:13:51.160 align:start position:0% actuaries you have boundaries so in this 00:13:51.160 --> 00:13:55.190 align:start position:0% actuaries you have boundaries so in this section<00:13:51.460> we're<00:13:51.850> basically<00:13:52.120> talking<00:13:52.450> about 00:13:55.190 --> 00:13:55.200 align:start position:0% 00:13:55.200 --> 00:13:58.560 align:start position:0% what<00:13:56.200> a<00:13:56.470> bridge<00:13:56.890> will<00:13:57.220> break<00:13:57.460> and<00:13:57.670> what<00:13:58.360> will 00:13:58.560 --> 00:13:58.570 align:start position:0% what a bridge will break and what will 00:13:58.570 --> 00:14:00.660 align:start position:0% what a bridge will break and what will never<00:13:58.780> break<00:13:59.050> has<00:13:59.290> never<00:13:59.890> been<00:14:00.160> really<00:14:00.550> be 00:14:00.660 --> 00:14:00.670 align:start position:0% never break has never been really be 00:14:00.670 --> 00:14:06.090 align:start position:0% never break has never been really be communicated<00:14:01.570> clearly<00:14:02.490> so<00:14:04.200> the<00:14:05.200> thing<00:14:05.590> is<00:14:05.620> no 00:14:06.090 --> 00:14:06.100 align:start position:0% communicated clearly so the thing is no 00:14:06.100 --> 00:14:08.460 align:start position:0% communicated clearly so the thing is no matter<00:14:06.130> how<00:14:06.580> we<00:14:06.640> come<00:14:06.910> into<00:14:07.060> it<00:14:07.390> the<00:14:08.170> loo<00:14:08.320> is 00:14:08.460 --> 00:14:08.470 align:start position:0% matter how we come into it the loo is 00:14:08.470 --> 00:14:10.470 align:start position:0% matter how we come into it the loo is quite<00:14:08.680> complex<00:14:09.040> currently<00:14:09.670> like<00:14:09.910> we<00:14:10.180> need<00:14:10.330> to 00:14:10.470 --> 00:14:10.480 align:start position:0% quite complex currently like we need to 00:14:10.480 --> 00:14:12.390 align:start position:0% quite complex currently like we need to make<00:14:10.930> assumption<00:14:11.440> make<00:14:11.620> some<00:14:11.830> or<00:14:11.950> something 00:14:12.390 --> 00:14:12.400 align:start position:0% make assumption make some or something 00:14:12.400 --> 00:14:14.450 align:start position:0% make assumption make some or something don't<00:14:12.640> pick<00:14:12.820> make<00:14:13.120> other<00:14:13.510> assumptions<00:14:14.170> and 00:14:14.450 --> 00:14:14.460 align:start position:0% don't pick make other assumptions and 00:14:14.460 --> 00:14:17.730 align:start position:0% don't pick make other assumptions and the<00:14:15.460> distinct<00:14:16.240> between<00:14:16.420> them<00:14:16.720> is<00:14:16.840> not<00:14:17.440> yet 00:14:17.730 --> 00:14:17.740 align:start position:0% the distinct between them is not yet 00:14:17.740 --> 00:14:21.300 align:start position:0% the distinct between them is not yet obvious<00:14:18.420> and<00:14:19.420> many<00:14:19.990> smart<00:14:20.920> comfort 00:14:21.300 --> 00:14:21.310 align:start position:0% obvious and many smart comfort 00:14:21.310 --> 00:14:23.820 align:start position:0% obvious and many smart comfort developers<00:14:21.910> and<00:14:22.240> even<00:14:22.780> called<00:14:22.990> Cod<00:14:23.320> rappers 00:14:23.820 --> 00:14:23.830 align:start position:0% developers and even called Cod rappers 00:14:23.830 --> 00:14:29.340 align:start position:0% developers and even called Cod rappers misunderstood<00:14:24.820> them<00:14:26.460> so<00:14:27.870> this<00:14:28.870> section<00:14:29.080> is 00:14:29.340 --> 00:14:29.350 align:start position:0% misunderstood them so this section is 00:14:29.350 --> 00:14:32.010 align:start position:0% misunderstood them so this section is basically<00:14:29.800> an<00:14:30.040> actual<00:14:30.460> propose<00:14:30.820> that<00:14:31.120> we<00:14:31.420> may 00:14:32.010 --> 00:14:32.020 align:start position:0% basically an actual propose that we may 00:14:32.020 --> 00:14:33.840 align:start position:0% basically an actual propose that we may want<00:14:32.290> to<00:14:32.410> have<00:14:32.530> a<00:14:32.740> really<00:14:33.190> clear<00:14:33.340> thought 00:14:33.840 --> 00:14:33.850 align:start position:0% want to have a really clear thought 00:14:33.850 --> 00:14:36.990 align:start position:0% want to have a really clear thought redesign<00:14:34.420> for<00:14:35.260> backward<00:14:35.680> ecology<00:14:36.100> about<00:14:36.610> what 00:14:36.990 --> 00:14:37.000 align:start position:0% redesign for backward ecology about what 00:14:37.000 --> 00:14:39.240 align:start position:0% redesign for backward ecology about what we<00:14:37.240> can<00:14:37.390> change<00:14:37.600> the<00:14:37.750> VM<00:14:38.110> and<00:14:38.350> what<00:14:38.770> we<00:14:38.920> cannot 00:14:39.240 --> 00:14:39.250 align:start position:0% we can change the VM and what we cannot 00:14:39.250 --> 00:14:43.110 align:start position:0% we can change the VM and what we cannot change<00:14:39.630> so<00:14:41.010> all<00:14:42.010> the<00:14:42.370> counter<00:14:42.670> developer 00:14:43.110 --> 00:14:43.120 align:start position:0% change so all the counter developer 00:14:43.120 --> 00:14:46.470 align:start position:0% change so all the counter developer knows<00:14:43.390> that<00:14:44.130> for<00:14:45.130> each<00:14:45.460> contracts<00:14:46.030> we<00:14:46.450> have 00:14:46.470 --> 00:14:46.480 align:start position:0% knows that for each contracts we have 00:14:46.480 --> 00:14:49.490 align:start position:0% knows that for each contracts we have coped<00:14:46.870> we<00:14:47.260> had<00:14:47.470> the<00:14:48.220> relative<00:14:48.670> stores<00:14:49.000> and 00:14:49.490 --> 00:14:49.500 align:start position:0% coped we had the relative stores and 00:14:49.500 --> 00:14:52.770 align:start position:0% coped we had the relative stores and also<00:14:50.500> each<00:14:50.770> contract<00:14:51.280> can<00:14:51.730> oxidize<00:14:51.910> extra 00:14:52.770 --> 00:14:52.780 align:start position:0% also each contract can oxidize extra 00:14:52.780 --> 00:14:56.220 align:start position:0% also each contract can oxidize extra contracts<00:14:53.230> and<00:14:54.160> three<00:14:54.460> compounds<00:14:54.790> so<00:14:55.510> this<00:14:56.080> is 00:14:56.220 --> 00:14:56.230 align:start position:0% contracts and three compounds so this is 00:14:56.230 --> 00:14:58.530 align:start position:0% contracts and three compounds so this is a<00:14:56.260> clear<00:14:56.530> distinction<00:14:57.100> so<00:14:57.610> what<00:14:57.880> we<00:14:58.030> can<00:14:58.180> do<00:14:58.330> is 00:14:58.530 --> 00:14:58.540 align:start position:0% a clear distinction so what we can do is 00:14:58.540 --> 00:15:02.340 align:start position:0% a clear distinction so what we can do is we<00:14:58.750> just<00:14:58.990> say<00:14:59.260> that<00:15:00.360> the<00:15:01.360> cold<00:15:01.660> and<00:15:01.900> the<00:15:02.050> crypt 00:15:02.340 --> 00:15:02.350 align:start position:0% we just say that the cold and the crypt 00:15:02.350 --> 00:15:04.950 align:start position:0% we just say that the cold and the crypt corresponding<00:15:03.250> slot<00:15:03.580> will<00:15:03.790> never<00:15:04.030> change<00:15:04.270> but 00:15:04.950 --> 00:15:04.960 align:start position:0% corresponding slot will never change but 00:15:04.960 --> 00:15:08.700 align:start position:0% corresponding slot will never change but we<00:15:05.350> are<00:15:05.530> now<00:15:05.710> change<00:15:06.040> of<00:15:06.720> anything<00:15:07.720> that<00:15:08.020> is<00:15:08.680> in 00:15:08.700 --> 00:15:08.710 align:start position:0% we are now change of anything that is in 00:15:08.710 --> 00:15:10.170 align:start position:0% we are now change of anything that is in the<00:15:09.130> in<00:15:09.340> the<00:15:09.490> state<00:15:09.700> like 00:15:10.170 --> 00:15:10.180 align:start position:0% the in the state like 00:15:10.180 --> 00:15:12.480 align:start position:0% the in the state like external<00:15:10.930> contracts<00:15:11.410> or<00:15:11.650> external<00:15:12.310> three 00:15:12.480 --> 00:15:12.490 align:start position:0% external contracts or external three 00:15:12.490 --> 00:15:18.390 align:start position:0% external contracts or external three compounds<00:15:15.120> so<00:15:16.140> this<00:15:17.140> basically<00:15:17.530> gives<00:15:17.770> us<00:15:18.010> a 00:15:18.390 --> 00:15:18.400 align:start position:0% compounds so this basically gives us a 00:15:18.400 --> 00:15:20.430 align:start position:0% compounds so this basically gives us a boundary<00:15:18.760> and<00:15:18.940> what<00:15:19.540> we<00:15:19.690> need<00:15:20.140> to<00:15:20.290> do<00:15:20.410> right 00:15:20.430 --> 00:15:20.440 align:start position:0% boundary and what we need to do right 00:15:20.440 --> 00:15:22.980 align:start position:0% boundary and what we need to do right now<00:15:20.770> is<00:15:20.950> basically<00:15:21.240> build<00:15:22.240> on<00:15:22.390> top<00:15:22.600> of<00:15:22.660> the 00:15:22.980 --> 00:15:22.990 align:start position:0% now is basically build on top of the 00:15:22.990 --> 00:15:24.780 align:start position:0% now is basically build on top of the version<00:15:23.350> a<00:15:23.440> civilian<00:15:23.920> and 00:15:24.780 --> 00:15:24.790 align:start position:0% version a civilian and 00:15:24.790 --> 00:15:26.939 align:start position:0% version a civilian and moves<00:15:25.149> or<00:15:25.510> some<00:15:25.720> code<00:15:25.930> that<00:15:25.959> we<00:15:26.410> might<00:15:26.680> want<00:15:26.860> to 00:15:26.939 --> 00:15:26.949 align:start position:0% moves or some code that we might want to 00:15:26.949 --> 00:15:29.280 align:start position:0% moves or some code that we might want to change<00:15:27.279> in<00:15:27.399> the<00:15:27.519> future<00:15:27.699> into<00:15:28.660> a<00:15:28.690> big<00:15:28.899> compel 00:15:29.280 --> 00:15:29.290 align:start position:0% change in the future into a big compel 00:15:29.290 --> 00:15:31.970 align:start position:0% change in the future into a big compel for<00:15:29.649> so<00:15:29.980> for<00:15:30.190> example<00:15:30.639> this<00:15:30.970> basically<00:15:31.510> is 00:15:31.970 --> 00:15:31.980 align:start position:0% for so for example this basically is 00:15:31.980 --> 00:15:35.189 align:start position:0% for so for example this basically is balance<00:15:32.980> those<00:15:33.610> theta<00:15:34.060> kind<00:15:34.449> of<00:15:34.660> sets<00:15:34.959> of 00:15:35.189 --> 00:15:35.199 align:start position:0% balance those theta kind of sets of 00:15:35.199 --> 00:15:37.590 align:start position:0% balance those theta kind of sets of codes<00:15:35.440> and<00:15:35.680> some<00:15:36.430> of<00:15:36.639> course<00:15:36.940> that<00:15:37.180> requires 00:15:37.590 --> 00:15:37.600 align:start position:0% codes and some of course that requires 00:15:37.600 --> 00:15:41.550 align:start position:0% codes and some of course that requires both<00:15:38.320> information<00:15:39.010> so<00:15:39.820> we<00:15:40.750> just<00:15:40.899> provide<00:15:41.529> a 00:15:41.550 --> 00:15:41.560 align:start position:0% both information so we just provide a 00:15:41.560 --> 00:15:43.139 align:start position:0% both information so we just provide a free<00:15:41.949> cocktail<00:15:42.160> to<00:15:42.490> outside<00:15:42.910> source 00:15:43.139 --> 00:15:43.149 align:start position:0% free cocktail to outside source 00:15:43.149 --> 00:15:49.199 align:start position:0% free cocktail to outside source information<00:15:46.620> so<00:15:47.670> we<00:15:48.670> can<00:15:48.790> have<00:15:48.970> a<00:15:49.000> better 00:15:49.199 --> 00:15:49.209 align:start position:0% information so we can have a better 00:15:49.209 --> 00:15:51.389 align:start position:0% information so we can have a better design<00:15:49.660> to<00:15:50.290> communicate<00:15:50.860> or<00:15:51.100> backward 00:15:51.389 --> 00:15:51.399 align:start position:0% design to communicate or backward 00:15:51.399 --> 00:15:54.990 align:start position:0% design to communicate or backward heavily<00:15:51.760> model<00:15:52.149> and<00:15:52.560> in<00:15:53.560> that<00:15:53.829> case<00:15:54.040> seems 00:15:54.990 --> 00:15:55.000 align:start position:0% heavily model and in that case seems 00:15:55.000 --> 00:15:57.870 align:start position:0% heavily model and in that case seems like<00:15:55.240> statement<00:15:55.750> or<00:15:56.019> the<00:15:56.050> migration<00:15:57.010> from<00:15:57.279> ETH 00:15:57.870 --> 00:15:57.880 align:start position:0% like statement or the migration from ETH 00:15:57.880 --> 00:16:01.290 align:start position:0% like statement or the migration from ETH 100<00:15:58.449> to<00:15:58.660> 200<00:15:59.490> can<00:16:00.490> be<00:16:00.610> much<00:16:00.820> more<00:16:01.000> clearly 00:16:01.290 --> 00:16:01.300 align:start position:0% 100 to 200 can be much more clearly 00:16:01.300 --> 00:16:04.079 align:start position:0% 100 to 200 can be much more clearly communicated<00:16:02.139> and<00:16:02.320> it<00:16:03.130> would<00:16:03.370> cause<00:16:03.699> more 00:16:04.079 --> 00:16:04.089 align:start position:0% communicated and it would cause more 00:16:04.089 --> 00:16:06.750 align:start position:0% communicated and it would cause more much<00:16:04.420> less<00:16:04.740> surprise<00:16:05.740> for<00:16:06.160> contract 00:16:06.750 --> 00:16:06.760 align:start position:0% much less surprise for contract 00:16:06.760 --> 00:16:13.829 align:start position:0% much less surprise for contract developers<00:16:09.779> so<00:16:11.339> in<00:16:12.339> this<00:16:12.610> Hawk<00:16:12.790> this<00:16:13.690> is 00:16:13.829 --> 00:16:13.839 align:start position:0% developers so in this Hawk this is 00:16:13.839 --> 00:16:15.930 align:start position:0% developers so in this Hawk this is conclusion<00:16:14.440> so<00:16:14.680> basically<00:16:15.100> we<00:16:15.399> are<00:16:15.430> talking 00:16:15.930 --> 00:16:15.940 align:start position:0% conclusion so basically we are talking 00:16:15.940 --> 00:16:19.590 align:start position:0% conclusion so basically we are talking about<00:16:17.040> nearly<00:16:18.040> complete<00:16:18.430> complete<00:16:19.029> fix<00:16:19.329> for 00:16:19.590 --> 00:16:19.600 align:start position:0% about nearly complete complete fix for 00:16:19.600 --> 00:16:22.230 align:start position:0% about nearly complete complete fix for our<00:16:19.779> current<00:16:20.019> pack<00:16:20.320> workability<00:16:20.740> model<00:16:21.279> that 00:16:22.230 --> 00:16:22.240 align:start position:0% our current pack workability model that 00:16:22.240 --> 00:16:26.100 align:start position:0% our current pack workability model that consists<00:16:22.810> of<00:16:23.110> a<00:16:23.410> conversion<00:16:24.329> which<00:16:25.329> allows 00:16:26.100 --> 00:16:26.110 align:start position:0% consists of a conversion which allows 00:16:26.110 --> 00:16:28.590 align:start position:0% consists of a conversion which allows smart<00:16:26.529> contracts<00:16:27.070> not<00:16:27.730> to<00:16:27.910> be<00:16:28.029> affected<00:16:28.449> by 00:16:28.590 --> 00:16:28.600 align:start position:0% smart contracts not to be affected by 00:16:28.600 --> 00:16:31.559 align:start position:0% smart contracts not to be affected by new<00:16:28.779> versions<00:16:29.199> and<00:16:29.949> we<00:16:30.730> also<00:16:30.880> have<00:16:31.360> the 00:16:31.559 --> 00:16:31.569 align:start position:0% new versions and we also have the 00:16:31.569 --> 00:16:35.129 align:start position:0% new versions and we also have the version<00:16:31.750> list<00:16:32.110> EVM<00:16:32.649> design<00:16:33.480> which<00:16:34.480> enables 00:16:35.129 --> 00:16:35.139 align:start position:0% version list EVM design which enables 00:16:35.139 --> 00:16:37.530 align:start position:0% version list EVM design which enables for<00:16:35.350> work<00:16:35.529> apology<00:16:36.160> I<00:16:36.370> believe<00:16:36.970> those<00:16:37.149> two 00:16:37.530 --> 00:16:37.540 align:start position:0% for work apology I believe those two 00:16:37.540 --> 00:16:39.780 align:start position:0% for work apology I believe those two combined<00:16:38.050> can<00:16:38.410> provide<00:16:38.889> a<00:16:38.949> really<00:16:39.339> good<00:16:39.519> and 00:16:39.780 --> 00:16:39.790 align:start position:0% combined can provide a really good and 00:16:39.790 --> 00:16:42.120 align:start position:0% combined can provide a really good and robust<00:16:40.510> package<00:16:40.779> of<00:16:41.170> this<00:16:41.319> model<00:16:41.709> for<00:16:41.949> us 00:16:42.120 --> 00:16:42.130 align:start position:0% robust package of this model for us 00:16:42.130 --> 00:16:47.280 align:start position:0% robust package of this model for us Curley<00:16:42.730> and<00:16:43.529> there's<00:16:44.529> also<00:16:45.000> a<00:16:46.050> proposal<00:16:47.050> that 00:16:47.280 --> 00:16:47.290 align:start position:0% Curley and there's also a proposal that 00:16:47.290 --> 00:16:50.189 align:start position:0% Curley and there's also a proposal that we<00:16:48.160> in<00:16:48.519> the<00:16:48.670> future<00:16:49.149> we<00:16:49.360> might<00:16:49.540> want<00:16:49.870> to<00:16:49.930> do 00:16:50.189 --> 00:16:50.199 align:start position:0% we in the future we might want to do 00:16:50.199 --> 00:16:52.680 align:start position:0% we in the future we might want to do some<00:16:50.470> additional<00:16:51.040> change<00:16:51.310> to<00:16:52.000> also<00:16:52.360> design 00:16:52.680 --> 00:16:52.690 align:start position:0% some additional change to also design 00:16:52.690 --> 00:16:55.620 align:start position:0% some additional change to also design the<00:16:52.720> UVM<00:16:53.319> for<00:16:53.589> better<00:16:53.800> programming<00:16:54.370> and<00:16:54.630> model 00:16:55.620 --> 00:16:55.630 align:start position:0% the UVM for better programming and model 00:16:55.630 --> 00:16:57.870 align:start position:0% the UVM for better programming and model communication<00:16:56.290> so<00:16:56.889> we<00:16:56.920> define<00:16:57.399> a<00:16:57.610> really 00:16:57.870 --> 00:16:57.880 align:start position:0% communication so we define a really 00:16:57.880 --> 00:17:00.480 align:start position:0% communication so we define a really clear<00:16:58.209> model<00:16:59.019> about<00:16:59.380> what<00:16:59.740> we<00:16:59.920> can<00:17:00.100> change<00:17:00.310> and 00:17:00.480 --> 00:17:00.490 align:start position:0% clear model about what we can change and 00:17:00.490 --> 00:17:04.140 align:start position:0% clear model about what we can change and what<00:17:01.029> we<00:17:01.260> definitely<00:17:02.260> won't<00:17:02.410> change<00:17:02.910> so<00:17:03.910> it 00:17:04.140 --> 00:17:04.150 align:start position:0% what we definitely won't change so it 00:17:04.150 --> 00:17:07.470 align:start position:0% what we definitely won't change so it becomes<00:17:05.110> harder<00:17:05.530> to<00:17:05.799> misuse<00:17:06.429> those<00:17:07.240> things 00:17:07.470 --> 00:17:07.480 align:start position:0% becomes harder to misuse those things 00:17:07.480 --> 00:17:11.610 align:start position:0% becomes harder to misuse those things and<00:17:09.179> that's<00:17:10.179> all<00:17:10.419> if<00:17:10.630> you<00:17:10.689> have<00:17:10.959> any<00:17:11.110> questions 00:17:11.610 --> 00:17:11.620 align:start position:0% and that's all if you have any questions 00:17:11.620 --> 00:17:15.329 align:start position:0% and that's all if you have any questions feel<00:17:11.860> free<00:17:11.980> to<00:17:12.160> ask<00:17:12.549> me<00:17:13.000> after<00:17:13.929> the<00:17:14.319> talk<00:17:14.860> so 00:17:15.329 --> 00:17:15.339 align:start position:0% feel free to ask me after the talk so 00:17:15.339 --> 00:17:27.319 align:start position:0% feel free to ask me after the talk so thank<00:17:15.880> you 00:17:27.319 --> 00:17:27.329 align:start position:0% 00:17:27.329 --> 00:17:29.390 align:start position:0% you