WEBVTT Kind: captions Language: en 00:00:18.490 --> 00:00:20.200 align:start position:0% okay<00:00:19.490> cool 00:00:20.200 --> 00:00:20.210 align:start position:0% okay cool 00:00:20.210 --> 00:00:23.590 align:start position:0% okay cool so<00:00:21.020> today<00:00:21.680> I'm<00:00:21.800> going<00:00:22.460> to<00:00:22.580> talk<00:00:22.850> about<00:00:23.029> a 00:00:23.590 --> 00:00:23.600 align:start position:0% so today I'm going to talk about a 00:00:23.600 --> 00:00:25.570 align:start position:0% so today I'm going to talk about a recent<00:00:23.900> project<00:00:24.290> in<00:00:24.710> smartphone<00:00:25.430> check 00:00:25.570 --> 00:00:25.580 align:start position:0% recent project in smartphone check 00:00:25.580 --> 00:00:28.150 align:start position:0% recent project in smartphone check security<00:00:25.900> namely<00:00:26.900> eientei<00:00:27.470> making<00:00:27.860> smart 00:00:28.150 --> 00:00:28.160 align:start position:0% security namely eientei making smart 00:00:28.160 --> 00:00:30.340 align:start position:0% security namely eientei making smart engage<00:00:28.369> smarter<00:00:28.760> to<00:00:29.390> see<00:00:29.570> the<00:00:29.689> joint<00:00:29.930> project 00:00:30.340 --> 00:00:30.350 align:start position:0% engage smarter to see the joint project 00:00:30.350 --> 00:00:33.520 align:start position:0% engage smarter to see the joint project with<00:00:30.610> my<00:00:31.610> team<00:00:31.970> from<00:00:32.270> NUS<00:00:32.780> and<00:00:32.810> yo<00:00:33.170> and<00:00:33.350> us 00:00:33.520 --> 00:00:33.530 align:start position:0% with my team from NUS and yo and us 00:00:33.530 --> 00:00:44.200 align:start position:0% with my team from NUS and yo and us college<00:00:36.310> so<00:00:42.100> okay<00:00:43.100> so<00:00:43.400> we<00:00:43.880> all<00:00:44.060> know<00:00:44.180> that 00:00:44.200 --> 00:00:44.210 align:start position:0% college so okay so we all know that 00:00:44.210 --> 00:00:46.180 align:start position:0% college so okay so we all know that programming<00:00:44.870> security<00:00:45.320> is<00:00:45.530> hard<00:00:45.890> because 00:00:46.180 --> 00:00:46.190 align:start position:0% programming security is hard because 00:00:46.190 --> 00:00:48.640 align:start position:0% programming security is hard because especially<00:00:47.180> for<00:00:47.630> you<00:00:47.840> know<00:00:47.870> complex<00:00:48.200> program 00:00:48.640 --> 00:00:48.650 align:start position:0% especially for you know complex program 00:00:48.650 --> 00:00:50.620 align:start position:0% especially for you know complex program because<00:00:49.340> your<00:00:49.490> system<00:00:49.880> or<00:00:50.090> your<00:00:50.240> program<00:00:50.540> may 00:00:50.620 --> 00:00:50.630 align:start position:0% because your system or your program may 00:00:50.630 --> 00:00:52.120 align:start position:0% because your system or your program may have<00:00:50.780> you<00:00:50.960> know<00:00:50.990> multiple<00:00:51.200> components<00:00:51.950> and 00:00:52.120 --> 00:00:52.130 align:start position:0% have you know multiple components and 00:00:52.130 --> 00:00:55.270 align:start position:0% have you know multiple components and the<00:00:52.760> adversary<00:00:53.270> or<00:00:53.600> the<00:00:54.080> attacker<00:00:54.620> can<00:00:54.950> choose 00:00:55.270 --> 00:00:55.280 align:start position:0% the adversary or the attacker can choose 00:00:55.280 --> 00:00:56.830 align:start position:0% the adversary or the attacker can choose you<00:00:55.700> know<00:00:55.790> to<00:00:55.940> attack<00:00:56.240> you<00:00:56.480> know<00:00:56.570> any 00:00:56.830 --> 00:00:56.840 align:start position:0% you know to attack you know any 00:00:56.840 --> 00:00:59.920 align:start position:0% you know to attack you know any component<00:00:57.410> and<00:00:57.590> to<00:00:57.770> exploit<00:00:58.160> your<00:00:58.370> system<00:00:58.930> so 00:00:59.920 --> 00:00:59.930 align:start position:0% component and to exploit your system so 00:00:59.930 --> 00:01:01.900 align:start position:0% component and to exploit your system so that's<00:01:00.080> well<00:01:00.290> you<00:01:00.440> know<00:01:00.560> people<00:01:00.710> say<00:01:01.040> security 00:01:01.900 --> 00:01:01.910 align:start position:0% that's well you know people say security 00:01:01.910 --> 00:01:04.329 align:start position:0% that's well you know people say security can<00:01:02.120> be<00:01:02.150> no<00:01:02.450> stronger<00:01:02.720> than<00:01:02.900> its<00:01:03.140> quickly<00:01:03.740> you 00:01:04.329 --> 00:01:04.339 align:start position:0% can be no stronger than its quickly you 00:01:04.339 --> 00:01:08.770 align:start position:0% can be no stronger than its quickly you know<00:01:04.430> component<00:01:05.710> so<00:01:06.850> programming<00:01:07.850> smart<00:01:08.150> CQ 00:01:08.770 --> 00:01:08.780 align:start position:0% know component so programming smart CQ 00:01:08.780 --> 00:01:11.160 align:start position:0% know component so programming smart CQ smart<00:01:09.080> conjecture<00:01:09.409> is<00:01:09.530> even<00:01:09.860> harder<00:01:10.220> because 00:01:11.160 --> 00:01:11.170 align:start position:0% smart conjecture is even harder because 00:01:11.170 --> 00:01:13.149 align:start position:0% smart conjecture is even harder because because<00:01:12.170> of<00:01:12.200> several<00:01:12.470> reasons 00:01:13.149 --> 00:01:13.159 align:start position:0% because of several reasons 00:01:13.159 --> 00:01:15.700 align:start position:0% because of several reasons so<00:01:13.579> I<00:01:13.880> myself<00:01:14.600> you<00:01:14.720> know<00:01:14.990> smartphone<00:01:15.380> jackass 00:01:15.700 --> 00:01:15.710 align:start position:0% so I myself you know smartphone jackass 00:01:15.710 --> 00:01:17.530 align:start position:0% so I myself you know smartphone jackass on<00:01:15.890> short<00:01:16.159> programs<00:01:16.520> because<00:01:16.939> you<00:01:17.119> have<00:01:17.299> only 00:01:17.530 --> 00:01:17.540 align:start position:0% on short programs because you have only 00:01:17.540 --> 00:01:19.630 align:start position:0% on short programs because you have only cha<00:01:17.720> only<00:01:18.170> one<00:01:18.320> chance<00:01:18.590> to<00:01:18.890> make<00:01:19.040> it<00:01:19.070> right 00:01:19.630 --> 00:01:19.640 align:start position:0% cha only one chance to make it right 00:01:19.640 --> 00:01:21.730 align:start position:0% cha only one chance to make it right once<00:01:20.240> you<00:01:20.540> deploy<00:01:20.780> it<00:01:21.020> you<00:01:21.050> know<00:01:21.320> it's<00:01:21.530> really 00:01:21.730 --> 00:01:21.740 align:start position:0% once you deploy it you know it's really 00:01:21.740 --> 00:01:23.740 align:start position:0% once you deploy it you know it's really hard<00:01:21.860> nearly<00:01:22.490> impossible<00:01:22.730> to<00:01:23.210> you<00:01:23.630> know 00:01:23.740 --> 00:01:23.750 align:start position:0% hard nearly impossible to you know 00:01:23.750 --> 00:01:26.980 align:start position:0% hard nearly impossible to you know change<00:01:24.170> it<00:01:24.409> if<00:01:24.830> if<00:01:25.400> you<00:01:25.580> find<00:01:25.909> any<00:01:26.240> flaw<00:01:26.450> in<00:01:26.750> the 00:01:26.980 --> 00:01:26.990 align:start position:0% change it if if you find any flaw in the 00:01:26.990 --> 00:01:29.890 align:start position:0% change it if if you find any flaw in the you<00:01:27.590> know<00:01:27.710> contract<00:01:28.430> and<00:01:28.700> secondly<00:01:29.480> you<00:01:29.810> know 00:01:29.890 --> 00:01:29.900 align:start position:0% you know contract and secondly you know 00:01:29.900 --> 00:01:32.200 align:start position:0% you know contract and secondly you know the<00:01:30.170> execution<00:01:31.130> model<00:01:31.280> of<00:01:31.520> this<00:01:31.640> mark<00:01:31.909> inject 00:01:32.200 --> 00:01:32.210 align:start position:0% the execution model of this mark inject 00:01:32.210 --> 00:01:34.840 align:start position:0% the execution model of this mark inject is<00:01:32.330> a<00:01:32.360> little<00:01:32.870> bit<00:01:32.960> different<00:01:33.350> it<00:01:34.010> is<00:01:34.040> executed 00:01:34.840 --> 00:01:34.850 align:start position:0% is a little bit different it is executed 00:01:34.850 --> 00:01:36.490 align:start position:0% is a little bit different it is executed by<00:01:35.000> the<00:01:35.060> consensus<00:01:35.659> model<00:01:35.690> running<00:01:36.170> on<00:01:36.380> the 00:01:36.490 --> 00:01:36.500 align:start position:0% by the consensus model running on the 00:01:36.500 --> 00:01:39.670 align:start position:0% by the consensus model running on the blockchain<00:01:37.060> and<00:01:38.060> the<00:01:38.720> third<00:01:38.900> reason<00:01:39.020> is<00:01:39.290> a<00:01:39.350> you 00:01:39.670 --> 00:01:39.680 align:start position:0% blockchain and the third reason is a you 00:01:39.680 --> 00:01:43.780 align:start position:0% blockchain and the third reason is a you know<00:01:39.800> we<00:01:40.370> use<00:01:40.610> new<00:01:40.970> language<00:01:41.840> with<00:01:42.229> a<00:01:42.790> little 00:01:43.780 --> 00:01:43.790 align:start position:0% know we use new language with a little 00:01:43.790 --> 00:01:46.210 align:start position:0% know we use new language with a little bit<00:01:43.880> we<00:01:44.479> we<00:01:44.840> have<00:01:45.020> a<00:01:45.049> pretty<00:01:45.530> much<00:01:45.799> similar<00:01:46.040> to 00:01:46.210 --> 00:01:46.220 align:start position:0% bit we we have a pretty much similar to 00:01:46.220 --> 00:01:48.399 align:start position:0% bit we we have a pretty much similar to the<00:01:46.460> existing<00:01:46.909> language<00:01:47.030> so<00:01:47.750> often<00:01:48.170> people 00:01:48.399 --> 00:01:48.409 align:start position:0% the existing language so often people 00:01:48.409 --> 00:01:51.010 align:start position:0% the existing language so often people you<00:01:49.310> know<00:01:49.430> make<00:01:49.940> some<00:01:50.120> assumption<00:01:50.690> about<00:01:50.870> the 00:01:51.010 --> 00:01:51.020 align:start position:0% you know make some assumption about the 00:01:51.020 --> 00:01:53.740 align:start position:0% you know make some assumption about the language<00:01:51.710> which<00:01:52.130> exists<00:01:52.670> in<00:01:52.820> JavaScript<00:01:53.630> and 00:01:53.740 --> 00:01:53.750 align:start position:0% language which exists in JavaScript and 00:01:53.750 --> 00:01:56.320 align:start position:0% language which exists in JavaScript and Python<00:01:53.960> but<00:01:54.770> do<00:01:55.130> not<00:01:55.280> exist<00:01:55.670> in<00:01:55.820> solidity<00:01:56.210> and 00:01:56.320 --> 00:01:56.330 align:start position:0% Python but do not exist in solidity and 00:01:56.330 --> 00:01:58.899 align:start position:0% Python but do not exist in solidity and answer<00:01:56.900> pen<00:01:57.110> so<00:01:58.010> that's<00:01:58.220> why<00:01:58.369> you<00:01:58.640> know<00:01:58.729> we 00:01:58.899 --> 00:01:58.909 align:start position:0% answer pen so that's why you know we 00:01:58.909 --> 00:02:01.270 align:start position:0% answer pen so that's why you know we have<00:01:59.030> seen<00:01:59.240> a<00:01:59.299> lot<00:01:59.570> of<00:01:59.600> you<00:01:59.930> know<00:01:59.960> problem<00:02:00.500> in 00:02:01.270 --> 00:02:01.280 align:start position:0% have seen a lot of you know problem in 00:02:01.280 --> 00:02:03.760 align:start position:0% have seen a lot of you know problem in our<00:02:01.400> smartphone<00:02:01.850> checks<00:02:02.060> for<00:02:02.570> example<00:02:02.930> you 00:02:03.760 --> 00:02:03.770 align:start position:0% our smartphone checks for example you 00:02:03.770 --> 00:02:05.200 align:start position:0% our smartphone checks for example you know<00:02:03.860> the<00:02:03.890> Dow<00:02:04.250> with<00:02:04.549> our<00:02:04.670> tree<00:02:04.820> engine<00:02:05.060> see 00:02:05.200 --> 00:02:05.210 align:start position:0% know the Dow with our tree engine see 00:02:05.210 --> 00:02:07.750 align:start position:0% know the Dow with our tree engine see work<00:02:05.650> you<00:02:06.650> know<00:02:06.740> eater<00:02:06.950> dies<00:02:07.190> with<00:02:07.460> a<00:02:07.490> gas 00:02:07.750 --> 00:02:07.760 align:start position:0% work you know eater dies with a gas 00:02:07.760 --> 00:02:11.830 align:start position:0% work you know eater dies with a gas problem<00:02:08.349> can<00:02:09.349> you<00:02:09.470> be<00:02:09.679> thrown<00:02:10.459> with<00:02:10.759> the<00:02:11.390> same 00:02:11.830 --> 00:02:11.840 align:start position:0% problem can you be thrown with the same 00:02:11.840 --> 00:02:14.890 align:start position:0% problem can you be thrown with the same you<00:02:12.409> know<00:02:12.439> instruction<00:02:13.189> so<00:02:14.090> the<00:02:14.510> question 00:02:14.890 --> 00:02:14.900 align:start position:0% you know instruction so the question 00:02:14.900 --> 00:02:16.929 align:start position:0% you know instruction so the question that<00:02:14.930> we<00:02:15.170> asked<00:02:15.560> before<00:02:15.799> we<00:02:16.189> started<00:02:16.760> our 00:02:16.929 --> 00:02:16.939 align:start position:0% that we asked before we started our 00:02:16.939 --> 00:02:20.020 align:start position:0% that we asked before we started our project<00:02:17.090> is<00:02:17.510> you<00:02:17.989> know<00:02:18.080> others<00:02:18.760> others<00:02:19.760> buffs 00:02:20.020 --> 00:02:20.030 align:start position:0% project is you know others others buffs 00:02:20.030 --> 00:02:21.910 align:start position:0% project is you know others others buffs that<00:02:20.269> we<00:02:20.390> don't<00:02:20.599> know<00:02:20.780> you<00:02:21.290> know<00:02:21.439> you<00:02:21.890> know 00:02:21.910 --> 00:02:21.920 align:start position:0% that we don't know you know you know 00:02:21.920 --> 00:02:25.150 align:start position:0% that we don't know you know you know existing<00:02:22.640> platform<00:02:23.090> and<00:02:23.349> secondly<00:02:24.349> you<00:02:25.040> know 00:02:25.150 --> 00:02:25.160 align:start position:0% existing platform and secondly you know 00:02:25.160 --> 00:02:27.100 align:start position:0% existing platform and secondly you know how<00:02:25.340> many<00:02:25.550> smart<00:02:26.270> contracts<00:02:26.599> are<00:02:26.750> there<00:02:26.930> are 00:02:27.100 --> 00:02:27.110 align:start position:0% how many smart contracts are there are 00:02:27.110 --> 00:02:28.100 align:start position:0% how many smart contracts are there are vulnerable 00:02:28.100 --> 00:02:28.110 align:start position:0% vulnerable 00:02:28.110 --> 00:02:30.440 align:start position:0% vulnerable so<00:02:28.670> surprisingly<00:02:29.670> you<00:02:29.940> know<00:02:30.030> the<00:02:30.180> number<00:02:30.420> of 00:02:30.440 --> 00:02:30.450 align:start position:0% so surprisingly you know the number of 00:02:30.450 --> 00:02:33.140 align:start position:0% so surprisingly you know the number of smartphone<00:02:31.290> checks<00:02:31.710> is<00:02:31.890> increasingly<00:02:32.460> it 00:02:33.140 --> 00:02:33.150 align:start position:0% smartphone checks is increasingly it 00:02:33.150 --> 00:02:36.620 align:start position:0% smartphone checks is increasingly it post<00:02:33.570> it<00:02:33.810> potentially<00:02:35.030> starting<00:02:36.030> from<00:02:36.270> you 00:02:36.620 --> 00:02:36.630 align:start position:0% post it potentially starting from you 00:02:36.630 --> 00:02:42.340 align:start position:0% post it potentially starting from you know<00:02:37.670> 2015<00:02:38.670> so<00:02:39.660> right<00:02:40.590> now<00:02:40.740> we<00:02:40.800> have<00:02:40.950> roughly 00:02:42.340 --> 00:02:42.350 align:start position:0% know 2015 so right now we have roughly 00:02:42.350 --> 00:02:45.500 align:start position:0% know 2015 so right now we have roughly 120,000<00:02:43.350> smartphone<00:02:43.710> jars<00:02:43.920> and<00:02:44.130> we<00:02:44.940> want<00:02:45.150> we 00:02:45.500 --> 00:02:45.510 align:start position:0% 120,000 smartphone jars and we want we 00:02:45.510 --> 00:02:47.540 align:start position:0% 120,000 smartphone jars and we want we really<00:02:45.810> want<00:02:45.990> to<00:02:46.080> quantify<00:02:46.830> you<00:02:47.310> know 00:02:47.540 --> 00:02:47.550 align:start position:0% really want to quantify you know 00:02:47.550 --> 00:02:49.640 align:start position:0% really want to quantify you know among<00:02:47.820> these<00:02:48.000> con<00:02:48.330> smartphone<00:02:48.900> choice<00:02:49.080> how 00:02:49.640 --> 00:02:49.650 align:start position:0% among these con smartphone choice how 00:02:49.650 --> 00:02:53.570 align:start position:0% among these con smartphone choice how many<00:02:49.860> of<00:02:49.980> them<00:02:50.130> are<00:02:50.250> vulnerable<00:02:52.280> so<00:02:53.280> there<00:02:53.520> are 00:02:53.570 --> 00:02:53.580 align:start position:0% many of them are vulnerable so there are 00:02:53.580 --> 00:02:56.600 align:start position:0% many of them are vulnerable so there are several<00:02:53.790> challenges<00:02:54.800> first<00:02:55.800> of<00:02:55.980> all<00:02:56.130> you<00:02:56.520> know 00:02:56.600 --> 00:02:56.610 align:start position:0% several challenges first of all you know 00:02:56.610 --> 00:02:58.720 align:start position:0% several challenges first of all you know contract<00:02:57.000> costs<00:02:57.240> are<00:02:57.360> not<00:02:57.510> always<00:02:57.660> available 00:02:58.720 --> 00:02:58.730 align:start position:0% contract costs are not always available 00:02:58.730 --> 00:03:01.370 align:start position:0% contract costs are not always available see<00:02:59.730> see<00:02:59.880> what<00:03:00.090> we<00:03:00.210> see<00:03:00.390> when<00:03:00.600> we<00:03:00.780> write<00:03:01.350> a 00:03:01.370 --> 00:03:01.380 align:start position:0% see see what we see when we write a 00:03:01.380 --> 00:03:03.890 align:start position:0% see see what we see when we write a smart<00:03:01.800> contract<00:03:01.920> but<00:03:02.790> what<00:03:03.210> is<00:03:03.450> eventually 00:03:03.890 --> 00:03:03.900 align:start position:0% smart contract but what is eventually 00:03:03.900 --> 00:03:06.170 align:start position:0% smart contract but what is eventually stall<00:03:04.410> on<00:03:04.650> the<00:03:04.680> blockchain<00:03:04.950> is<00:03:05.340> a<00:03:05.460> binary<00:03:05.820> code 00:03:06.170 --> 00:03:06.180 align:start position:0% stall on the blockchain is a binary code 00:03:06.180 --> 00:03:07.940 align:start position:0% stall on the blockchain is a binary code which<00:03:06.390> is<00:03:06.690> compiled<00:03:07.110> from<00:03:07.230> the<00:03:07.380> high<00:03:07.680> level 00:03:07.940 --> 00:03:07.950 align:start position:0% which is compiled from the high level 00:03:07.950 --> 00:03:11.740 align:start position:0% which is compiled from the high level code<00:03:08.160> and<00:03:08.570> you<00:03:09.570> know<00:03:09.660> you<00:03:09.990> can<00:03:10.200> use<00:03:10.350> some 00:03:11.740 --> 00:03:11.750 align:start position:0% code and you know you can use some 00:03:11.750 --> 00:03:16.070 align:start position:0% code and you know you can use some disassembler<00:03:12.750> to<00:03:13.050> you<00:03:13.470> know<00:03:14.090> to<00:03:15.090> translate 00:03:16.070 --> 00:03:16.080 align:start position:0% disassembler to you know to translate 00:03:16.080 --> 00:03:18.230 align:start position:0% disassembler to you know to translate the<00:03:16.320> binary<00:03:16.740> code<00:03:16.950> into<00:03:17.250> the<00:03:17.280> by<00:03:17.490> code<00:03:17.760> but 00:03:18.230 --> 00:03:18.240 align:start position:0% the binary code into the by code but 00:03:18.240 --> 00:03:19.850 align:start position:0% the binary code into the by code but it's<00:03:18.390> still<00:03:18.570> really<00:03:18.810> hard<00:03:19.020> for<00:03:19.170> you<00:03:19.290> to<00:03:19.440> make 00:03:19.850 --> 00:03:19.860 align:start position:0% it's still really hard for you to make 00:03:19.860 --> 00:03:22.340 align:start position:0% it's still really hard for you to make any<00:03:19.980> sense<00:03:20.280> of<00:03:20.459> this<00:03:20.490> and<00:03:20.930> secondly<00:03:21.930> we<00:03:22.230> have 00:03:22.340 --> 00:03:22.350 align:start position:0% any sense of this and secondly we have 00:03:22.350 --> 00:03:24.500 align:start position:0% any sense of this and secondly we have so<00:03:22.620> many<00:03:22.770> smart<00:03:23.310> contracts<00:03:23.700> to<00:03:23.910> and<00:03:24.060> analyze 00:03:24.500 --> 00:03:24.510 align:start position:0% so many smart contracts to and analyze 00:03:24.510 --> 00:03:26.990 align:start position:0% so many smart contracts to and analyze and<00:03:24.780> you<00:03:25.650> know<00:03:25.740> if<00:03:25.950> we<00:03:26.130> have<00:03:26.250> someone<00:03:26.670> really 00:03:26.990 --> 00:03:27.000 align:start position:0% and you know if we have someone really 00:03:27.000 --> 00:03:28.910 align:start position:0% and you know if we have someone really good<00:03:27.180> who<00:03:27.480> can<00:03:27.720> you<00:03:28.020> know<00:03:28.050> read<00:03:28.440> the<00:03:28.470> bytecode 00:03:28.910 --> 00:03:28.920 align:start position:0% good who can you know read the bytecode 00:03:28.920 --> 00:03:31.190 align:start position:0% good who can you know read the bytecode is<00:03:29.459> still<00:03:30.180> you<00:03:30.360> know<00:03:30.390> takes<00:03:30.720> them<00:03:30.900> several 00:03:31.190 --> 00:03:31.200 align:start position:0% is still you know takes them several 00:03:31.200 --> 00:03:34.130 align:start position:0% is still you know takes them several years<00:03:31.230> to<00:03:31.650> analyze<00:03:32.580> all<00:03:32.820> the<00:03:33.140> 120,000 00:03:34.130 --> 00:03:34.140 align:start position:0% years to analyze all the 120,000 00:03:34.140 --> 00:03:39.140 align:start position:0% years to analyze all the 120,000 smartphone<00:03:35.040> charts<00:03:35.810> so<00:03:36.810> what<00:03:37.530> we<00:03:38.489> contribute 00:03:39.140 --> 00:03:39.150 align:start position:0% smartphone charts so what we contribute 00:03:39.150 --> 00:03:41.330 align:start position:0% smartphone charts so what we contribute in<00:03:39.480> this<00:03:39.690> project<00:03:39.959> is<00:03:40.350> first<00:03:40.860> of<00:03:40.950> all<00:03:41.100> we 00:03:41.330 --> 00:03:41.340 align:start position:0% in this project is first of all we 00:03:41.340 --> 00:03:43.490 align:start position:0% in this project is first of all we identify<00:03:42.060> new<00:03:42.209> smartphone<00:03:42.630> check<00:03:42.750> box<00:03:42.959> namely 00:03:43.490 --> 00:03:43.500 align:start position:0% identify new smartphone check box namely 00:03:43.500 --> 00:03:45.740 align:start position:0% identify new smartphone check box namely generation<00:03:44.489> Auto<00:03:44.670> independence<00:03:45.239> and<00:03:45.510> tons 00:03:45.740 --> 00:03:45.750 align:start position:0% generation Auto independence and tons 00:03:45.750 --> 00:03:48.400 align:start position:0% generation Auto independence and tons time<00:03:45.989> dependence<00:03:46.440> and<00:03:47.310> we<00:03:47.400> talk<00:03:47.610> about<00:03:47.730> them 00:03:48.400 --> 00:03:48.410 align:start position:0% time dependence and we talk about them 00:03:48.410 --> 00:03:50.050 align:start position:0% time dependence and we talk about them shortly 00:03:50.050 --> 00:03:50.060 align:start position:0% shortly 00:03:50.060 --> 00:03:54.290 align:start position:0% shortly second<00:03:51.060> we<00:03:51.239> introduce<00:03:51.660> Oriente<00:03:52.230> the<00:03:52.560> new<00:03:53.300> the 00:03:54.290 --> 00:03:54.300 align:start position:0% second we introduce Oriente the new the 00:03:54.300 --> 00:03:56.360 align:start position:0% second we introduce Oriente the new the analyzer<00:03:55.080> for<00:03:55.380> smart<00:03:55.650> contracts<00:03:55.980> which<00:03:56.340> is 00:03:56.360 --> 00:03:56.370 align:start position:0% analyzer for smart contracts which is 00:03:56.370 --> 00:03:59.690 align:start position:0% analyzer for smart contracts which is beyond<00:03:56.970> simply<00:03:57.660> execution<00:03:58.320> so<00:03:58.920> eientei<00:03:59.489> can 00:03:59.690 --> 00:03:59.700 align:start position:0% beyond simply execution so eientei can 00:03:59.700 --> 00:04:03.080 align:start position:0% beyond simply execution so eientei can detect<00:04:00.060> all<00:04:00.209> the<00:04:00.330> popular<00:04:00.750> box<00:04:01.970> including<00:04:02.970> the 00:04:03.080 --> 00:04:03.090 align:start position:0% detect all the popular box including the 00:04:03.090 --> 00:04:05.960 align:start position:0% detect all the popular box including the known<00:04:03.269> and<00:04:03.510> their<00:04:03.750> new<00:04:03.900> ones<00:04:04.610> so<00:04:05.610> we<00:04:05.760> one 00:04:05.960 --> 00:04:05.970 align:start position:0% known and their new ones so we one 00:04:05.970 --> 00:04:08.870 align:start position:0% known and their new ones so we one oriented<00:04:06.630> with<00:04:06.860> almost<00:04:07.860> 20,000<00:04:08.519> smartphone 00:04:08.870 --> 00:04:08.880 align:start position:0% oriented with almost 20,000 smartphone 00:04:08.880 --> 00:04:11.060 align:start position:0% oriented with almost 20,000 smartphone charts<00:04:09.120> and<00:04:09.330> we<00:04:09.900> were<00:04:10.050> able<00:04:10.140> to<00:04:10.320> flag<00:04:10.709> you<00:04:10.980> know 00:04:11.060 --> 00:04:11.070 align:start position:0% charts and we were able to flag you know 00:04:11.070 --> 00:04:13.160 align:start position:0% charts and we were able to flag you know roughly<00:04:11.459> night<00:04:11.910> of<00:04:12.090> Zen<00:04:12.239> of<00:04:12.269> them<00:04:12.540> as<00:04:12.780> for 00:04:13.160 --> 00:04:13.170 align:start position:0% roughly night of Zen of them as for 00:04:13.170 --> 00:04:18.380 align:start position:0% roughly night of Zen of them as for narubu<00:04:15.709> okay<00:04:16.709> so<00:04:17.489> what<00:04:17.700> is<00:04:17.820> generation<00:04:18.209> order 00:04:18.380 --> 00:04:18.390 align:start position:0% narubu okay so what is generation order 00:04:18.390 --> 00:04:21.199 align:start position:0% narubu okay so what is generation order independence<00:04:18.930> so<00:04:19.470> I<00:04:19.500> will<00:04:19.769> use<00:04:20.010> a<00:04:20.400> simple 00:04:21.199 --> 00:04:21.209 align:start position:0% independence so I will use a simple 00:04:21.209 --> 00:04:23.900 align:start position:0% independence so I will use a simple smartphone<00:04:22.049> check<00:04:22.320> to<00:04:22.440> Allah<00:04:22.680> to<00:04:23.370> illustrate 00:04:23.900 --> 00:04:23.910 align:start position:0% smartphone check to Allah to illustrate 00:04:23.910 --> 00:04:26.719 align:start position:0% smartphone check to Allah to illustrate this<00:04:24.090> problem<00:04:24.830> so<00:04:25.830> here<00:04:26.040> we<00:04:26.190> have<00:04:26.310> the<00:04:26.520> the 00:04:26.719 --> 00:04:26.729 align:start position:0% this problem so here we have the the 00:04:26.729 --> 00:04:29.440 align:start position:0% this problem so here we have the the puzzle<00:04:27.330> solver<00:04:27.630> contract<00:04:28.080> break<00:04:28.500> you<00:04:29.190> know 00:04:29.440 --> 00:04:29.450 align:start position:0% puzzle solver contract break you know 00:04:29.450 --> 00:04:32.210 align:start position:0% puzzle solver contract break you know allows<00:04:30.450> the<00:04:30.660> owner<00:04:30.690> to<00:04:30.990> set<00:04:31.560> up<00:04:31.650> some<00:04:31.830> puzzle 00:04:32.210 --> 00:04:32.220 align:start position:0% allows the owner to set up some puzzle 00:04:32.220 --> 00:04:35.390 align:start position:0% allows the owner to set up some puzzle and<00:04:32.430> you<00:04:33.180> know<00:04:33.270> anyone<00:04:33.540> can<00:04:33.660> and<00:04:34.470> and<00:04:35.070> then<00:04:35.220> he 00:04:35.390 --> 00:04:35.400 align:start position:0% and you know anyone can and and then he 00:04:35.400 --> 00:04:37.430 align:start position:0% and you know anyone can and and then he deposit<00:04:35.880> some<00:04:36.150> ether<00:04:36.360> so<00:04:36.870> that<00:04:37.050> anyone<00:04:37.350> can 00:04:37.430 --> 00:04:37.440 align:start position:0% deposit some ether so that anyone can 00:04:37.440 --> 00:04:40.219 align:start position:0% deposit some ether so that anyone can submit<00:04:37.830> the<00:04:38.070> solution<00:04:38.520> for<00:04:39.120> the<00:04:39.210> Paso<00:04:39.539> to 00:04:40.219 --> 00:04:40.229 align:start position:0% submit the solution for the Paso to 00:04:40.229 --> 00:04:41.480 align:start position:0% submit the solution for the Paso to collect<00:04:40.530> the<00:04:40.620> reward 00:04:41.480 --> 00:04:41.490 align:start position:0% collect the reward 00:04:41.490 --> 00:04:44.960 align:start position:0% collect the reward and<00:04:41.630> you<00:04:42.630> know<00:04:42.720> if<00:04:42.930> the<00:04:43.080> owners<00:04:43.440> see<00:04:43.680> that<00:04:43.970> the 00:04:44.960 --> 00:04:44.970 align:start position:0% and you know if the owners see that the 00:04:44.970 --> 00:04:48.170 align:start position:0% and you know if the owners see that the prewar<00:04:45.419> is<00:04:45.750> a<00:04:45.780> little<00:04:46.590> bit<00:04:46.680> low<00:04:46.979> and<00:04:47.250> the 00:04:48.170 --> 00:04:48.180 align:start position:0% prewar is a little bit low and the 00:04:48.180 --> 00:04:51.529 align:start position:0% prewar is a little bit low and the pizzoli<00:04:48.690> is<00:04:48.930> so<00:04:49.710> hot<00:04:49.949> so<00:04:50.370> so<00:04:50.940> he<00:04:51.150> can<00:04:51.360> update 00:04:51.529 --> 00:04:51.539 align:start position:0% pizzoli is so hot so so he can update 00:04:51.539 --> 00:04:53.740 align:start position:0% pizzoli is so hot so so he can update the<00:04:51.780> reward<00:04:52.110> to<00:04:52.319> attract<00:04:52.620> more<00:04:52.770> more<00:04:53.160> uterus 00:04:53.740 --> 00:04:53.750 align:start position:0% the reward to attract more more uterus 00:04:53.750 --> 00:04:59.230 align:start position:0% the reward to attract more more uterus so<00:04:56.449> now<00:04:57.449> let's<00:04:58.050> consider<00:04:58.289> this<00:04:58.650> scenario 00:04:59.230 --> 00:04:59.240 align:start position:0% so now let's consider this scenario 00:04:59.240 --> 00:05:02.480 align:start position:0% so now let's consider this scenario where<00:05:00.240> you<00:05:00.539> know<00:05:00.660> some<00:05:01.169> users<00:05:01.470> submit<00:05:01.770> the<00:05:01.949> the 00:05:02.480 --> 00:05:02.490 align:start position:0% where you know some users submit the the 00:05:02.490 --> 00:05:05.689 align:start position:0% where you know some users submit the the a<00:05:02.699> solution<00:05:03.330> would<00:05:03.870> include<00:05:04.229> their<00:05:04.580> some<00:05:05.580> of 00:05:05.689 --> 00:05:05.699 align:start position:0% a solution would include their some of 00:05:05.699 --> 00:05:07.640 align:start position:0% a solution would include their some of the<00:05:05.819> same<00:05:06.389> generation<00:05:06.900> would<00:05:07.259> include<00:05:07.590> a 00:05:07.640 --> 00:05:07.650 align:start position:0% the same generation would include a 00:05:07.650 --> 00:05:11.540 align:start position:0% the same generation would include a solution<00:05:08.250> to<00:05:09.000> the<00:05:09.150> to<00:05:09.990> the<00:05:10.110> contract<00:05:10.500> so<00:05:11.190> some 00:05:11.540 --> 00:05:11.550 align:start position:0% solution to the to the contract so some 00:05:11.550 --> 00:05:15.080 align:start position:0% solution to the to the contract so some miners<00:05:11.910> they<00:05:12.389> include<00:05:12.780> the<00:05:13.020> generation<00:05:13.880> in<00:05:14.880> in 00:05:15.080 --> 00:05:15.090 align:start position:0% miners they include the generation in in 00:05:15.090 --> 00:05:17.149 align:start position:0% miners they include the generation in in his<00:05:15.240> block<00:05:15.539> and<00:05:15.810> then<00:05:16.169> the<00:05:16.409> submit<00:05:16.800> solution 00:05:17.149 --> 00:05:17.159 align:start position:0% his block and then the submit solution 00:05:17.159 --> 00:05:19.969 align:start position:0% his block and then the submit solution is<00:05:17.280> trigger<00:05:18.080> the<00:05:19.080> others<00:05:19.440> received<00:05:19.680> the 00:05:19.969 --> 00:05:19.979 align:start position:0% is trigger the others received the 00:05:19.979 --> 00:05:21.950 align:start position:0% is trigger the others received the reward<00:05:20.310> if<00:05:20.490> his<00:05:20.759> solution<00:05:20.940> is<00:05:21.270> correct<00:05:21.449> so 00:05:21.950 --> 00:05:21.960 align:start position:0% reward if his solution is correct so 00:05:21.960 --> 00:05:25.189 align:start position:0% reward if his solution is correct so this<00:05:22.409> is<00:05:22.620> totally<00:05:23.250> fine<00:05:23.490> but<00:05:24.479> let's<00:05:24.780> consider 00:05:25.189 --> 00:05:25.199 align:start position:0% this is totally fine but let's consider 00:05:25.199 --> 00:05:28.939 align:start position:0% this is totally fine but let's consider this<00:05:25.500> scenario<00:05:25.669> where<00:05:26.669> you<00:05:27.180> know<00:05:27.560> we<00:05:28.560> have<00:05:28.590> the 00:05:28.939 --> 00:05:28.949 align:start position:0% this scenario where you know we have the 00:05:28.949 --> 00:05:31.670 align:start position:0% this scenario where you know we have the owner<00:05:29.330> saying<00:05:30.330> a<00:05:30.509> different<00:05:30.900> generation<00:05:31.110> at 00:05:31.670 --> 00:05:31.680 align:start position:0% owner saying a different generation at 00:05:31.680 --> 00:05:33.770 align:start position:0% owner saying a different generation at the<00:05:31.860> same<00:05:32.039> time<00:05:32.280> to<00:05:32.940> update<00:05:33.120> that<00:05:33.389> we<00:05:33.449> were<00:05:33.599> to 00:05:33.770 --> 00:05:33.780 align:start position:0% the same time to update that we were to 00:05:33.780 --> 00:05:37.129 align:start position:0% the same time to update that we were to 0<00:05:34.159> so<00:05:35.159> now<00:05:35.340> the<00:05:35.789> miners<00:05:36.090> can<00:05:36.360> you<00:05:36.659> know<00:05:36.780> see 00:05:37.129 --> 00:05:37.139 align:start position:0% 0 so now the miners can you know see 00:05:37.139 --> 00:05:39.469 align:start position:0% 0 so now the miners can you know see like<00:05:37.319> a<00:05:37.830> set<00:05:38.400> of<00:05:38.520> generation<00:05:38.940> in<00:05:39.060> his<00:05:39.210> block 00:05:39.469 --> 00:05:39.479 align:start position:0% like a set of generation in his block 00:05:39.479 --> 00:05:41.420 align:start position:0% like a set of generation in his block and<00:05:39.750> he<00:05:39.990> can<00:05:40.169> freely<00:05:40.380> decide<00:05:41.039> which 00:05:41.420 --> 00:05:41.430 align:start position:0% and he can freely decide which 00:05:41.430 --> 00:05:43.339 align:start position:0% and he can freely decide which generation<00:05:41.849> to<00:05:42.030> include<00:05:42.479> and<00:05:42.720> which<00:05:43.169> an 00:05:43.339 --> 00:05:43.349 align:start position:0% generation to include and which an 00:05:43.349 --> 00:05:46.029 align:start position:0% generation to include and which an adjacent<00:05:43.620> to<00:05:43.710> it<00:05:43.800> know<00:05:43.979> and<00:05:44.310> which<00:05:45.150> order 00:05:46.029 --> 00:05:46.039 align:start position:0% adjacent to it know and which order 00:05:46.039 --> 00:05:48.950 align:start position:0% adjacent to it know and which order between<00:05:47.039> the<00:05:47.340> generations<00:05:47.820> so<00:05:48.539> for<00:05:48.810> some 00:05:48.950 --> 00:05:48.960 align:start position:0% between the generations so for some 00:05:48.960 --> 00:05:51.260 align:start position:0% between the generations so for some reasons<00:05:49.380> he<00:05:50.099> includes<00:05:50.460> the<00:05:50.610> generation<00:05:51.030> which 00:05:51.260 --> 00:05:51.270 align:start position:0% reasons he includes the generation which 00:05:51.270 --> 00:05:53.540 align:start position:0% reasons he includes the generation which update<00:05:51.719> the<00:05:51.900> reward<00:05:52.259> first<00:05:52.710> and<00:05:52.919> then<00:05:53.400> the 00:05:53.540 --> 00:05:53.550 align:start position:0% update the reward first and then the 00:05:53.550 --> 00:05:56.360 align:start position:0% update the reward first and then the submit<00:05:53.849> solution<00:05:54.210> generation<00:05:54.630> later<00:05:55.159> so<00:05:56.159> now 00:05:56.360 --> 00:05:56.370 align:start position:0% submit solution generation later so now 00:05:56.370 --> 00:05:59.209 align:start position:0% submit solution generation later so now there<00:05:56.849> appear<00:05:57.090> reward<00:05:57.389> is<00:05:58.039> executed<00:05:59.039> first 00:05:59.209 --> 00:05:59.219 align:start position:0% there appear reward is executed first 00:05:59.219 --> 00:06:02.360 align:start position:0% there appear reward is executed first and<00:05:59.520> the<00:05:59.880> Ballon<00:06:00.180> is<00:06:00.300> set<00:06:00.479> to<00:06:00.630> zero<00:06:00.840> and<00:06:01.370> then 00:06:02.360 --> 00:06:02.370 align:start position:0% and the Ballon is set to zero and then 00:06:02.370 --> 00:06:03.980 align:start position:0% and the Ballon is set to zero and then the<00:06:02.610> submit<00:06:02.969> solution<00:06:03.330> generation<00:06:03.539> is 00:06:03.980 --> 00:06:03.990 align:start position:0% the submit solution generation is 00:06:03.990 --> 00:06:07.270 align:start position:0% the submit solution generation is executed<00:06:04.800> now<00:06:05.550> although<00:06:06.240> the<00:06:06.539> you<00:06:06.659> to<00:06:06.810> submit 00:06:07.270 --> 00:06:07.280 align:start position:0% executed now although the you to submit 00:06:07.280 --> 00:06:10.339 align:start position:0% executed now although the you to submit submitted<00:06:08.280> a<00:06:08.490> correct<00:06:09.030> solution<00:06:09.150> he<00:06:10.020> still 00:06:10.339 --> 00:06:10.349 align:start position:0% submitted a correct solution he still 00:06:10.349 --> 00:06:13.010 align:start position:0% submitted a correct solution he still get<00:06:10.560> 0<00:06:10.590> reward<00:06:11.219> for<00:06:11.370> his<00:06:11.520> solution<00:06:12.360> but<00:06:12.840> he's 00:06:13.010 --> 00:06:13.020 align:start position:0% get 0 reward for his solution but he's 00:06:13.020 --> 00:06:18.469 align:start position:0% get 0 reward for his solution but he's unfair<00:06:14.330> so<00:06:15.650> the<00:06:16.650> problem<00:06:17.099> in<00:06:17.880> this<00:06:18.150> generation 00:06:18.469 --> 00:06:18.479 align:start position:0% unfair so the problem in this generation 00:06:18.479 --> 00:06:21.649 align:start position:0% unfair so the problem in this generation are<00:06:18.750> independent<00:06:19.530> dependence<00:06:20.460> Bob<00:06:20.729> is<00:06:20.940> a<00:06:20.969> you 00:06:21.649 --> 00:06:21.659 align:start position:0% are independent dependence Bob is a you 00:06:21.659 --> 00:06:23.839 align:start position:0% are independent dependence Bob is a you know<00:06:21.750> they're<00:06:22.080> the<00:06:22.710> state<00:06:23.009> that<00:06:23.310> the<00:06:23.580> the 00:06:23.839 --> 00:06:23.849 align:start position:0% know they're the state that the the 00:06:23.849 --> 00:06:25.909 align:start position:0% know they're the state that the the either<00:06:24.030> observed<00:06:24.630> when<00:06:25.050> he<00:06:25.169> when<00:06:25.500> he<00:06:25.530> submit 00:06:25.909 --> 00:06:25.919 align:start position:0% either observed when he when he submit 00:06:25.919 --> 00:06:27.920 align:start position:0% either observed when he when he submit the<00:06:26.069> generation<00:06:26.550> is<00:06:26.789> different<00:06:27.330> from<00:06:27.690> the 00:06:27.920 --> 00:06:27.930 align:start position:0% the generation is different from the 00:06:27.930 --> 00:06:29.779 align:start position:0% the generation is different from the actual<00:06:28.710> state<00:06:28.949> of<00:06:29.099> the<00:06:29.190> smartphone<00:06:29.490> check 00:06:29.779 --> 00:06:29.789 align:start position:0% actual state of the smartphone check 00:06:29.789 --> 00:06:34.999 align:start position:0% actual state of the smartphone check when<00:06:30.419> the<00:06:30.539> connection<00:06:30.840> is<00:06:31.110> executed<00:06:33.110> and<00:06:34.110> this 00:06:34.999 --> 00:06:35.009 align:start position:0% when the connection is executed and this 00:06:35.009 --> 00:06:37.249 align:start position:0% when the connection is executed and this can<00:06:35.280> be<00:06:35.430> a<00:06:35.610> you<00:06:36.270> know<00:06:36.360> coincidence<00:06:36.990> because 00:06:37.249 --> 00:06:37.259 align:start position:0% can be a you know coincidence because 00:06:37.259 --> 00:06:39.409 align:start position:0% can be a you know coincidence because you<00:06:37.620> know<00:06:37.710> to<00:06:37.919> generation<00:06:38.400> can<00:06:38.580> happen<00:06:38.880> at<00:06:39.270> the 00:06:39.409 --> 00:06:39.419 align:start position:0% you know to generation can happen at the 00:06:39.419 --> 00:06:42.080 align:start position:0% you know to generation can happen at the same<00:06:39.630> time<00:06:39.840> or<00:06:40.050> the<00:06:40.169> term<00:06:40.349> right<00:06:40.639> but<00:06:41.639> it<00:06:41.880> can 00:06:42.080 --> 00:06:42.090 align:start position:0% same time or the term right but it can 00:06:42.090 --> 00:06:45.110 align:start position:0% same time or the term right but it can be<00:06:42.240> a<00:06:42.449> malicious<00:06:42.900> scenario<00:06:43.740> because<00:06:44.310> you<00:06:45.000> know 00:06:45.110 --> 00:06:45.120 align:start position:0% be a malicious scenario because you know 00:06:45.120 --> 00:06:47.480 align:start position:0% be a malicious scenario because you know if<00:06:45.780> the<00:06:45.960> owner<00:06:46.139> saw<00:06:46.440> the<00:06:46.500> targeted<00:06:47.069> generation 00:06:47.480 --> 00:06:47.490 align:start position:0% if the owner saw the targeted generation 00:06:47.490 --> 00:06:49.640 align:start position:0% if the owner saw the targeted generation from<00:06:47.639> the<00:06:47.729> victim<00:06:48.150> which<00:06:48.509> includes<00:06:48.900> a<00:06:49.080> you 00:06:49.640 --> 00:06:49.650 align:start position:0% from the victim which includes a you 00:06:49.650 --> 00:06:52.579 align:start position:0% from the victim which includes a you know<00:06:49.770> correct<00:06:50.270> solution<00:06:51.270> for<00:06:51.449> the<00:06:51.510> puzzle<00:06:51.870> he 00:06:52.579 --> 00:06:52.589 align:start position:0% know correct solution for the puzzle he 00:06:52.589 --> 00:06:54.439 align:start position:0% know correct solution for the puzzle he can<00:06:52.800> you<00:06:53.010> know<00:06:53.039> on<00:06:53.219> second<00:06:53.550> letter<00:06:53.729> saying<00:06:54.360> a 00:06:54.439 --> 00:06:54.449 align:start position:0% can you know on second letter saying a 00:06:54.449 --> 00:06:55.129 align:start position:0% can you know on second letter saying a different 00:06:55.129 --> 00:06:55.139 align:start position:0% different 00:06:55.139 --> 00:06:57.739 align:start position:0% different Chanin<00:06:55.770> to<00:06:56.099> abate<00:06:56.340> the<00:06:56.370> reward<00:06:56.789> and<00:06:57.240> now<00:06:57.689> the 00:06:57.739 --> 00:06:57.749 align:start position:0% Chanin to abate the reward and now the 00:06:57.749 --> 00:06:59.959 align:start position:0% Chanin to abate the reward and now the to<00:06:57.990> generation<00:06:58.409> until<00:06:58.499> enter<00:06:59.340> the<00:06:59.460> race<00:06:59.639> and 00:06:59.959 --> 00:06:59.969 align:start position:0% to generation until enter the race and 00:06:59.969 --> 00:07:03.769 align:start position:0% to generation until enter the race and you<00:07:00.599> know<00:07:00.719> the<00:07:01.229> owner<00:07:01.439> has<00:07:01.740> some<00:07:02.120> non<00:07:03.120> zero 00:07:03.769 --> 00:07:03.779 align:start position:0% you know the owner has some non zero 00:07:03.779 --> 00:07:07.640 align:start position:0% you know the owner has some non zero probability<00:07:03.900> of<00:07:04.650> winning<00:07:04.770> the<00:07:05.069> race<00:07:06.650> so 00:07:07.640 --> 00:07:07.650 align:start position:0% probability of winning the race so 00:07:07.650 --> 00:07:09.890 align:start position:0% probability of winning the race so that's<00:07:08.430> it<00:07:08.639> for<00:07:08.879> their<00:07:09.120> generation<00:07:09.599> or 00:07:09.890 --> 00:07:09.900 align:start position:0% that's it for their generation or 00:07:09.900 --> 00:07:13.519 align:start position:0% that's it for their generation or independence<00:07:11.719> next<00:07:12.719> thing<00:07:12.840> you<00:07:12.960> can<00:07:12.990> spend 00:07:13.519 --> 00:07:13.529 align:start position:0% independence next thing you can spend 00:07:13.529 --> 00:07:15.499 align:start position:0% independence next thing you can spend time<00:07:13.889> stem<00:07:14.159> dependence<00:07:14.669> so<00:07:15.120> we<00:07:15.360> know<00:07:15.479> that 00:07:15.499 --> 00:07:15.509 align:start position:0% time stem dependence so we know that 00:07:15.509 --> 00:07:17.360 align:start position:0% time stem dependence so we know that interim<00:07:16.110> allows<00:07:16.439> this<00:07:16.680> mark<00:07:16.949> on<00:07:17.039> check<00:07:17.249> to 00:07:17.360 --> 00:07:17.370 align:start position:0% interim allows this mark on check to 00:07:17.370 --> 00:07:19.429 align:start position:0% interim allows this mark on check to access<00:07:17.849> the<00:07:18.120> block<00:07:18.300> times<00:07:18.569> time<00:07:18.810> within<00:07:19.229> the 00:07:19.429 --> 00:07:19.439 align:start position:0% access the block times time within the 00:07:19.439 --> 00:07:23.450 align:start position:0% access the block times time within the contract<00:07:20.090> and<00:07:21.229> really<00:07:22.229> we<00:07:22.439> we<00:07:22.770> have<00:07:22.949> seen<00:07:23.189> two 00:07:23.450 --> 00:07:23.460 align:start position:0% contract and really we we have seen two 00:07:23.460 --> 00:07:27.110 align:start position:0% contract and really we we have seen two main<00:07:23.669> use<00:07:24.360> case<00:07:24.599> of<00:07:24.629> these<00:07:25.080> thumbs<00:07:25.529> them<00:07:26.120> first 00:07:27.110 --> 00:07:27.120 align:start position:0% main use case of these thumbs them first 00:07:27.120 --> 00:07:29.269 align:start position:0% main use case of these thumbs them first people<00:07:27.599> use<00:07:27.779> the<00:07:27.960> thumbs<00:07:28.229> them<00:07:28.439> as<00:07:28.710> a<00:07:28.770> random 00:07:29.269 --> 00:07:29.279 align:start position:0% people use the thumbs them as a random 00:07:29.279 --> 00:07:32.379 align:start position:0% people use the thumbs them as a random seed<00:07:29.490> to<00:07:29.819> generate<00:07:30.180> the<00:07:30.389> random<00:07:30.569> number<00:07:31.020> and 00:07:32.379 --> 00:07:32.389 align:start position:0% seed to generate the random number and 00:07:32.389 --> 00:07:37.850 align:start position:0% seed to generate the random number and secondly<00:07:33.389> they<00:07:33.840> use<00:07:34.050> the<00:07:34.319> timestamp<00:07:34.889> to<00:07:36.860> to 00:07:37.850 --> 00:07:37.860 align:start position:0% secondly they use the timestamp to to 00:07:37.860 --> 00:07:40.909 align:start position:0% secondly they use the timestamp to to simulate<00:07:38.159> the<00:07:38.520> real<00:07:38.550> time<00:07:38.969> and<00:07:39.710> the<00:07:40.710> problem 00:07:40.909 --> 00:07:40.919 align:start position:0% simulate the real time and the problem 00:07:40.919 --> 00:07:43.070 align:start position:0% simulate the real time and the problem with<00:07:41.250> with<00:07:41.520> with<00:07:41.849> these<00:07:42.150> two<00:07:42.360> Eve's<00:07:42.539> case<00:07:42.810> is 00:07:43.070 --> 00:07:43.080 align:start position:0% with with with these two Eve's case is 00:07:43.080 --> 00:07:44.990 align:start position:0% with with with these two Eve's case is that<00:07:43.349> you<00:07:43.680> know<00:07:43.800> the<00:07:43.979> tough<00:07:44.159> stem<00:07:44.400> can<00:07:44.610> be<00:07:44.639> many 00:07:44.990 --> 00:07:45.000 align:start position:0% that you know the tough stem can be many 00:07:45.000 --> 00:07:48.439 align:start position:0% that you know the tough stem can be many manipulated<00:07:45.990> and<00:07:46.169> the<00:07:46.729> miners<00:07:47.729> they<00:07:48.060> can<00:07:48.210> vary 00:07:48.439 --> 00:07:48.449 align:start position:0% manipulated and the miners they can vary 00:07:48.449 --> 00:07:51.079 align:start position:0% manipulated and the miners they can vary their<00:07:48.719> block<00:07:48.930> times<00:07:49.169> them<00:07:49.430> to<00:07:50.430> you<00:07:50.789> know<00:07:50.879> the 00:07:51.079 --> 00:07:51.089 align:start position:0% their block times them to you know the 00:07:51.089 --> 00:07:53.869 align:start position:0% their block times them to you know the value<00:07:51.389> of<00:07:51.479> weight<00:07:51.659> by<00:07:52.020> us<00:07:52.169> them<00:07:52.469> so<00:07:53.400> they<00:07:53.699> can 00:07:53.869 --> 00:07:53.879 align:start position:0% value of weight by us them so they can 00:07:53.879 --> 00:07:55.579 align:start position:0% value of weight by us them so they can totally<00:07:54.029> buy<00:07:54.360> out<00:07:54.689> the<00:07:54.900> output<00:07:55.199> of<00:07:55.349> the 00:07:55.579 --> 00:07:55.589 align:start position:0% totally buy out the output of the 00:07:55.589 --> 00:07:57.679 align:start position:0% totally buy out the output of the execution<00:07:56.249> to<00:07:56.460> their<00:07:56.610> benefit<00:07:56.999> you<00:07:57.569> know 00:07:57.679 --> 00:07:57.689 align:start position:0% execution to their benefit you know 00:07:57.689 --> 00:07:58.399 align:start position:0% execution to their benefit you know either 00:07:58.399 --> 00:07:58.409 align:start position:0% either 00:07:58.409 --> 00:08:02.119 align:start position:0% either in<00:07:59.129> both<00:07:59.610> of<00:07:59.729> their<00:07:59.879> use<00:08:00.060> cases<00:08:00.319> so<00:08:01.319> in<00:08:02.039> our 00:08:02.119 --> 00:08:02.129 align:start position:0% in both of their use cases so in our 00:08:02.129 --> 00:08:04.189 align:start position:0% in both of their use cases so in our papers<00:08:02.490> we<00:08:02.759> propose<00:08:03.150> the<00:08:03.449> solution<00:08:03.870> for<00:08:04.020> both 00:08:04.189 --> 00:08:04.199 align:start position:0% papers we propose the solution for both 00:08:04.199 --> 00:08:06.890 align:start position:0% papers we propose the solution for both of<00:08:04.349> their<00:08:04.789> problems<00:08:05.789> so<00:08:06.330> I<00:08:06.360> think<00:08:06.479> you<00:08:06.719> can 00:08:06.890 --> 00:08:06.900 align:start position:0% of their problems so I think you can 00:08:06.900 --> 00:08:09.079 align:start position:0% of their problems so I think you can take<00:08:07.050> a<00:08:07.110> look<00:08:07.289> at<00:08:07.469> the<00:08:08.159> paper<00:08:08.339> you<00:08:09.060> are 00:08:09.079 --> 00:08:09.089 align:start position:0% take a look at the paper you are 00:08:09.089 --> 00:08:12.529 align:start position:0% take a look at the paper you are interested<00:08:10.099> next<00:08:11.099> I<00:08:11.189> will<00:08:11.370> talk<00:08:11.639> about<00:08:11.849> int 00:08:12.529 --> 00:08:12.539 align:start position:0% interested next I will talk about int 00:08:12.539 --> 00:08:16.249 align:start position:0% interested next I will talk about int their<00:08:13.669> analyze<00:08:14.669> analyze<00:08:15.419> that<00:08:15.810> for<00:08:15.870> smart 00:08:16.249 --> 00:08:16.259 align:start position:0% their analyze analyze that for smart 00:08:16.259 --> 00:08:18.860 align:start position:0% their analyze analyze that for smart contracts<00:08:16.849> so<00:08:17.849> here's<00:08:18.210> a<00:08:18.300> high-level 00:08:18.860 --> 00:08:18.870 align:start position:0% contracts so here's a high-level 00:08:18.870 --> 00:08:21.889 align:start position:0% contracts so here's a high-level architecture<00:08:19.139> of<00:08:19.830> int<00:08:20.330> which<00:08:21.330> is<00:08:21.449> based<00:08:21.719> on 00:08:21.889 --> 00:08:21.899 align:start position:0% architecture of int which is based on 00:08:21.899 --> 00:08:24.469 align:start position:0% architecture of int which is based on symbolic<00:08:22.110> execution<00:08:22.550> so<00:08:23.550> eientei<00:08:24.060> takes<00:08:24.330> the 00:08:24.469 --> 00:08:24.479 align:start position:0% symbolic execution so eientei takes the 00:08:24.479 --> 00:08:26.719 align:start position:0% symbolic execution so eientei takes the bike<00:08:24.689> or<00:08:24.870> as<00:08:25.050> an<00:08:25.229> input<00:08:25.500> and<00:08:25.680> then<00:08:26.399> based<00:08:26.610> on 00:08:26.719 --> 00:08:26.729 align:start position:0% bike or as an input and then based on 00:08:26.729 --> 00:08:29.089 align:start position:0% bike or as an input and then based on the<00:08:26.849> bike<00:08:27.029> code<00:08:27.300> we<00:08:27.719> generate<00:08:28.439> the<00:08:28.740> control 00:08:29.089 --> 00:08:29.099 align:start position:0% the bike code we generate the control 00:08:29.099 --> 00:08:31.519 align:start position:0% the bike code we generate the control flow<00:08:29.250> graph<00:08:29.279> and<00:08:29.849> from<00:08:30.539> the<00:08:30.659> control<00:08:31.379> flow 00:08:31.519 --> 00:08:31.529 align:start position:0% flow graph and from the control flow 00:08:31.529 --> 00:08:36.589 align:start position:0% flow graph and from the control flow graph<00:08:31.560> we<00:08:32.339> pass<00:08:32.579> it<00:08:32.760> to<00:08:32.909> the<00:08:34.789> simple<00:08:35.789> Explorer 00:08:36.589 --> 00:08:36.599 align:start position:0% graph we pass it to the simple Explorer 00:08:36.599 --> 00:08:39.439 align:start position:0% graph we pass it to the simple Explorer and<00:08:37.320> we<00:08:37.529> will<00:08:37.740> explore<00:08:38.159> the<00:08:38.519> possible<00:08:38.940> part<00:08:39.240> of 00:08:39.439 --> 00:08:39.449 align:start position:0% and we will explore the possible part of 00:08:39.449 --> 00:08:42.110 align:start position:0% and we will explore the possible part of the<00:08:39.570> program<00:08:39.930> so<00:08:40.800> for<00:08:41.099> every<00:08:41.459> part<00:08:41.760> that<00:08:41.880> we 00:08:42.110 --> 00:08:42.120 align:start position:0% the program so for every part that we 00:08:42.120 --> 00:08:45.319 align:start position:0% the program so for every part that we can<00:08:42.269> explore<00:08:42.630> we<00:08:43.409> we<00:08:43.740> said<00:08:44.010> we<00:08:44.250> forgot<00:08:45.029> it<00:08:45.149> to 00:08:45.319 --> 00:08:45.329 align:start position:0% can explore we we said we forgot it to 00:08:45.329 --> 00:08:47.449 align:start position:0% can explore we we said we forgot it to the<00:08:45.449> core<00:08:45.660> analysis<00:08:46.230> which<00:08:46.949> will<00:08:47.070> be<00:08:47.220> take 00:08:47.449 --> 00:08:47.459 align:start position:0% the core analysis which will be take 00:08:47.459 --> 00:08:50.829 align:start position:0% the core analysis which will be take whether<00:08:47.670> the<00:08:48.029> part<00:08:48.959> of<00:08:49.079> the<00:08:49.199> program<00:08:49.560> we 00:08:50.829 --> 00:08:50.839 align:start position:0% whether the part of the program we 00:08:50.839 --> 00:08:53.449 align:start position:0% whether the part of the program we detect<00:08:51.839> whether<00:08:52.050> the<00:08:52.380> part<00:08:52.740> has<00:08:52.949> some<00:08:53.220> you 00:08:53.449 --> 00:08:53.459 align:start position:0% detect whether the part has some you 00:08:53.459 --> 00:08:55.340 align:start position:0% detect whether the part has some you know<00:08:53.550> prop<00:08:53.790> some<00:08:54.300> problem<00:08:54.750> that<00:08:54.990> we<00:08:55.110> want<00:08:55.290> to 00:08:55.340 --> 00:08:55.350 align:start position:0% know prop some problem that we want to 00:08:55.350 --> 00:08:57.920 align:start position:0% know prop some problem that we want to be<00:08:55.440> take<00:08:55.620> and<00:08:56.399> if<00:08:56.640> there<00:08:56.850> is<00:08:56.970> we<00:08:57.510> will<00:08:57.540> forward 00:08:57.920 --> 00:08:57.930 align:start position:0% be take and if there is we will forward 00:08:57.930 --> 00:09:01.069 align:start position:0% be take and if there is we will forward to<00:08:58.829> the<00:08:59.399> result<00:09:00.029> to<00:09:00.240> the<00:09:00.269> validator<00:09:00.750> to 00:09:01.069 --> 00:09:01.079 align:start position:0% to the result to the validator to 00:09:01.079 --> 00:09:04.630 align:start position:0% to the result to the validator to validate<00:09:01.649> whether<00:09:01.860> the<00:09:02.180> the<00:09:03.199> Rizal<00:09:04.199> is 00:09:04.630 --> 00:09:04.640 align:start position:0% validate whether the the Rizal is 00:09:04.640 --> 00:09:07.790 align:start position:0% validate whether the the Rizal is positive<00:09:06.560> so 00:09:07.790 --> 00:09:07.800 align:start position:0% positive so 00:09:07.800 --> 00:09:09.290 align:start position:0% positive so a<00:09:07.860> little<00:09:08.250> bit<00:09:08.370> more<00:09:08.550> about<00:09:08.820> symbolic 00:09:09.290 --> 00:09:09.300 align:start position:0% a little bit more about symbolic 00:09:09.300 --> 00:09:11.840 align:start position:0% a little bit more about symbolic execution<00:09:09.740> so<00:09:10.740> this<00:09:10.920> is<00:09:11.070> our<00:09:11.279> control<00:09:11.580> flow 00:09:11.840 --> 00:09:11.850 align:start position:0% execution so this is our control flow 00:09:11.850 --> 00:09:15.190 align:start position:0% execution so this is our control flow graph<00:09:12.860> we<00:09:13.860> will<00:09:14.040> visit<00:09:14.279> every<00:09:14.790> single 00:09:15.190 --> 00:09:15.200 align:start position:0% graph we will visit every single 00:09:15.200 --> 00:09:18.199 align:start position:0% graph we will visit every single execution<00:09:16.200> choice<00:09:16.560> at<00:09:16.769> the<00:09:16.890> program<00:09:17.220> so<00:09:17.880> given 00:09:18.199 --> 00:09:18.209 align:start position:0% execution choice at the program so given 00:09:18.209 --> 00:09:22.310 align:start position:0% execution choice at the program so given some<00:09:18.240> input<00:09:18.810> X<00:09:19.250> we<00:09:20.250> will<00:09:20.430> you<00:09:21.089> know<00:09:21.320> collect 00:09:22.310 --> 00:09:22.320 align:start position:0% some input X we will you know collect 00:09:22.320 --> 00:09:24.290 align:start position:0% some input X we will you know collect all<00:09:22.470> the<00:09:22.589> part<00:09:22.830> condition<00:09:23.250> which<00:09:23.730> eventually 00:09:24.290 --> 00:09:24.300 align:start position:0% all the part condition which eventually 00:09:24.300 --> 00:09:28.550 align:start position:0% all the part condition which eventually we<00:09:24.930> essentially<00:09:26.990> summarize<00:09:27.990> or<00:09:28.320> the 00:09:28.550 --> 00:09:28.560 align:start position:0% we essentially summarize or the 00:09:28.560 --> 00:09:30.769 align:start position:0% we essentially summarize or the execution<00:09:29.240> characteristic<00:09:30.240> of<00:09:30.329> that<00:09:30.390> part 00:09:30.769 --> 00:09:30.779 align:start position:0% execution characteristic of that part 00:09:30.779 --> 00:09:33.470 align:start position:0% execution characteristic of that part and<00:09:31.050> for<00:09:31.890> example<00:09:32.279> we<00:09:32.579> want<00:09:32.790> to<00:09:32.910> check<00:09:33.180> this 00:09:33.470 --> 00:09:33.480 align:start position:0% and for example we want to check this 00:09:33.480 --> 00:09:36.970 align:start position:0% and for example we want to check this property<00:09:33.990> whether<00:09:34.649> Z<00:09:35.250> is<00:09:35.310> equal<00:09:35.730> to<00:09:35.760> X<00:09:35.970> plus<00:09:36.089> 2 00:09:36.970 --> 00:09:36.980 align:start position:0% property whether Z is equal to X plus 2 00:09:36.980 --> 00:09:39.710 align:start position:0% property whether Z is equal to X plus 2 with<00:09:37.980> us<00:09:38.160> you<00:09:38.399> know<00:09:38.519> most<00:09:38.910> other<00:09:39.180> condition 00:09:39.710 --> 00:09:39.720 align:start position:0% with us you know most other condition 00:09:39.720 --> 00:09:41.930 align:start position:0% with us you know most other condition together<00:09:40.050> into<00:09:40.620> one<00:09:40.800> which<00:09:41.010> simplex<00:09:41.490> formula 00:09:41.930 --> 00:09:41.940 align:start position:0% together into one which simplex formula 00:09:41.940 --> 00:09:45.500 align:start position:0% together into one which simplex formula and<00:09:43.220> the<00:09:44.220> rest<00:09:44.430> is<00:09:44.610> used<00:09:44.760> to<00:09:44.910> ask<00:09:45.209> whether 00:09:45.500 --> 00:09:45.510 align:start position:0% and the rest is used to ask whether 00:09:45.510 --> 00:09:47.780 align:start position:0% and the rest is used to ask whether there<00:09:45.959> exists<00:09:46.440> any<00:09:46.589> instant<00:09:47.220> of<00:09:47.370> the<00:09:47.459> input 00:09:47.780 --> 00:09:47.790 align:start position:0% there exists any instant of the input 00:09:47.790 --> 00:09:50.150 align:start position:0% there exists any instant of the input that<00:09:48.000> satisfies<00:09:48.180> this<00:09:48.720> formula<00:09:49.170> so<00:09:49.800> in<00:09:50.040> order 00:09:50.150 --> 00:09:50.160 align:start position:0% that satisfies this formula so in order 00:09:50.160 --> 00:09:52.930 align:start position:0% that satisfies this formula so in order to<00:09:50.310> answer<00:09:50.519> this<00:09:50.820> question<00:09:51.140> we<00:09:52.140> send<00:09:52.649> the 00:09:52.930 --> 00:09:52.940 align:start position:0% to answer this question we send the 00:09:52.940 --> 00:09:55.639 align:start position:0% to answer this question we send the formula<00:09:53.940> to<00:09:54.149> the<00:09:54.269> theorem<00:09:54.600> prover<00:09:54.990> which<00:09:55.290> ec3 00:09:55.639 --> 00:09:55.649 align:start position:0% formula to the theorem prover which ec3 00:09:55.649 --> 00:09:59.630 align:start position:0% formula to the theorem prover which ec3 in<00:09:56.130> int<00:09:56.579> and<00:09:56.970> this<00:09:57.779> theorem<00:09:58.380> prover<00:09:58.829> we<00:09:59.130> say 00:09:59.630 --> 00:09:59.640 align:start position:0% in int and this theorem prover we say 00:09:59.640 --> 00:10:03.110 align:start position:0% in int and this theorem prover we say whether<00:09:59.940> there<00:10:00.450> exist<00:10:01.100> input<00:10:02.100> or<00:10:02.250> not<00:10:02.399> and<00:10:02.610> if 00:10:03.110 --> 00:10:03.120 align:start position:0% whether there exist input or not and if 00:10:03.120 --> 00:10:06.470 align:start position:0% whether there exist input or not and if there<00:10:03.329> is<00:10:03.480> it<00:10:04.260> will<00:10:04.470> generate<00:10:04.769> an<00:10:05.250> example<00:10:06.089> for 00:10:06.470 --> 00:10:06.480 align:start position:0% there is it will generate an example for 00:10:06.480 --> 00:10:11.090 align:start position:0% there is it will generate an example for us<00:10:06.740> so<00:10:07.940> what<00:10:08.940> can<00:10:09.120> orient<00:10:09.450> they<00:10:09.540> do<00:10:09.720> Oh<00:10:10.100> aunt 00:10:11.090 --> 00:10:11.100 align:start position:0% us so what can orient they do Oh aunt 00:10:11.100 --> 00:10:12.829 align:start position:0% us so what can orient they do Oh aunt they<00:10:11.190> can<00:10:11.430> detect<00:10:11.730> but<00:10:11.940> in<00:10:12.180> existing<00:10:12.630> smart 00:10:12.829 --> 00:10:12.839 align:start position:0% they can detect but in existing smart 00:10:12.839 --> 00:10:17.389 align:start position:0% they can detect but in existing smart contracts<00:10:13.260> as<00:10:13.740> Isis<00:10:15.140> described<00:10:16.140> and<00:10:16.440> we<00:10:17.220> run 00:10:17.389 --> 00:10:17.399 align:start position:0% contracts as Isis described and we run 00:10:17.399 --> 00:10:20.900 align:start position:0% contracts as Isis described and we run eientei<00:10:17.850> with<00:10:18.060> you<00:10:18.240> know<00:10:18.560> almost<00:10:19.910> 20,000 00:10:20.900 --> 00:10:20.910 align:start position:0% eientei with you know almost 20,000 00:10:20.910 --> 00:10:24.740 align:start position:0% eientei with you know almost 20,000 smart<00:10:21.149> contracts<00:10:21.480> back<00:10:22.170> in<00:10:22.320> May<00:10:22.470> 2016<00:10:23.279> and<00:10:23.750> we 00:10:24.740 --> 00:10:24.750 align:start position:0% smart contracts back in May 2016 and we 00:10:24.750 --> 00:10:26.960 align:start position:0% smart contracts back in May 2016 and we were<00:10:25.380> able<00:10:25.529> to<00:10:25.709> detect<00:10:26.070> all<00:10:26.250> the<00:10:26.399> popular<00:10:26.790> box 00:10:26.960 --> 00:10:26.970 align:start position:0% were able to detect all the popular box 00:10:26.970 --> 00:10:30.500 align:start position:0% were able to detect all the popular box back<00:10:27.360> then<00:10:27.770> this<00:10:28.770> is<00:10:28.890> the<00:10:29.010> number<00:10:29.160> of<00:10:29.370> box<00:10:29.550> for 00:10:30.500 --> 00:10:30.510 align:start position:0% back then this is the number of box for 00:10:30.510 --> 00:10:34.970 align:start position:0% back then this is the number of box for each<00:10:30.660> category<00:10:31.260> and<00:10:32.270> second<00:10:33.380> orion<00:10:34.380> taken<00:10:34.800> you 00:10:34.970 --> 00:10:34.980 align:start position:0% each category and second orion taken you 00:10:34.980 --> 00:10:38.410 align:start position:0% each category and second orion taken you can<00:10:35.339> be<00:10:35.459> used<00:10:35.670> to<00:10:36.000> prove<00:10:36.990> the<00:10:37.050> test<00:10:37.380> generation 00:10:38.410 --> 00:10:38.420 align:start position:0% can be used to prove the test generation 00:10:38.420 --> 00:10:41.540 align:start position:0% can be used to prove the test generation because<00:10:39.420> symbolic<00:10:40.350> execution<00:10:40.470> allows<00:10:41.160> us<00:10:41.370> to 00:10:41.540 --> 00:10:41.550 align:start position:0% because symbolic execution allows us to 00:10:41.550 --> 00:10:43.340 align:start position:0% because symbolic execution allows us to cover<00:10:41.760> all<00:10:42.120> the<00:10:42.300> possible<00:10:42.660> paths<00:10:42.930> of<00:10:43.140> each 00:10:43.340 --> 00:10:43.350 align:start position:0% cover all the possible paths of each 00:10:43.350 --> 00:10:45.440 align:start position:0% cover all the possible paths of each program<00:10:43.770> understand<00:10:44.160> we<00:10:44.279> can<00:10:44.520> based<00:10:45.120> on<00:10:45.270> that 00:10:45.440 --> 00:10:45.450 align:start position:0% program understand we can based on that 00:10:45.450 --> 00:10:47.780 align:start position:0% program understand we can based on that path<00:10:45.720> we<00:10:46.260> can<00:10:46.290> generate<00:10:46.740> one<00:10:47.040> example<00:10:47.520> input 00:10:47.780 --> 00:10:47.790 align:start position:0% path we can generate one example input 00:10:47.790 --> 00:10:50.449 align:start position:0% path we can generate one example input that<00:10:48.209> drives<00:10:48.510> the<00:10:48.779> smartphone<00:10:49.170> check<00:10:49.350> to<00:10:50.279> that 00:10:50.449 --> 00:10:50.459 align:start position:0% that drives the smartphone check to that 00:10:50.459 --> 00:10:55.100 align:start position:0% that drives the smartphone check to that I<00:10:50.760> secrets<00:10:51.329> in<00:10:51.420> part<00:10:52.279> and<00:10:53.279> I<00:10:54.120> thing<00:10:54.570> is<00:10:54.720> open 00:10:55.100 --> 00:10:55.110 align:start position:0% I secrets in part and I thing is open 00:10:55.110 --> 00:10:56.930 align:start position:0% I secrets in part and I thing is open source<00:10:55.350> business<00:10:55.620> really<00:10:56.190> believes<00:10:56.610> it<00:10:56.790> two 00:10:56.930 --> 00:10:56.940 align:start position:0% source business really believes it two 00:10:56.940 --> 00:10:59.480 align:start position:0% source business really believes it two days<00:10:57.089> ago<00:10:57.149> you<00:10:58.020> can<00:10:58.230> go<00:10:58.589> to<00:10:58.649> that<00:10:58.920> to<00:10:59.279> that 00:10:59.480 --> 00:10:59.490 align:start position:0% days ago you can go to that to that 00:10:59.490 --> 00:11:02.210 align:start position:0% days ago you can go to that to that github<00:10:59.820> repo<00:11:00.240> -<00:11:00.600> you<00:11:01.020> know<00:11:01.140> clone<00:11:01.410> to<00:11:01.949> and 00:11:02.210 --> 00:11:02.220 align:start position:0% github repo - you know clone to and 00:11:02.220 --> 00:11:05.269 align:start position:0% github repo - you know clone to and contribute<00:11:02.940> to<00:11:02.970> the<00:11:03.149> project<00:11:04.160> there<00:11:05.160> are<00:11:05.190> a 00:11:05.269 --> 00:11:05.279 align:start position:0% contribute to the project there are a 00:11:05.279 --> 00:11:06.889 align:start position:0% contribute to the project there are a lot<00:11:05.399> of<00:11:05.430> future<00:11:05.760> work<00:11:05.910> that<00:11:06.120> that<00:11:06.420> we<00:11:06.570> can<00:11:06.720> do 00:11:06.889 --> 00:11:06.899 align:start position:0% lot of future work that that we can do 00:11:06.899 --> 00:11:09.949 align:start position:0% lot of future work that that we can do to<00:11:07.170> improve<00:11:07.620> their<00:11:08.180> you<00:11:09.180> know<00:11:09.209> performance 00:11:09.949 --> 00:11:09.959 align:start position:0% to improve their you know performance 00:11:09.959 --> 00:11:12.680 align:start position:0% to improve their you know performance and<00:11:10.260> functionality<00:11:10.680> of<00:11:10.949> their<00:11:11.220> project<00:11:12.000> us 00:11:12.680 --> 00:11:12.690 align:start position:0% and functionality of their project us 00:11:12.690 --> 00:11:14.449 align:start position:0% and functionality of their project us for<00:11:13.290> example<00:11:13.620> we<00:11:13.740> can<00:11:13.860> support<00:11:14.220> more<00:11:14.399> of 00:11:14.449 --> 00:11:14.459 align:start position:0% for example we can support more of 00:11:14.459 --> 00:11:16.730 align:start position:0% for example we can support more of course<00:11:14.760> right<00:11:15.480> now<00:11:15.600> we<00:11:15.660> discover<00:11:16.140> you<00:11:16.440> know<00:11:16.529> a 00:11:16.730 --> 00:11:16.740 align:start position:0% course right now we discover you know a 00:11:16.740 --> 00:11:19.490 align:start position:0% course right now we discover you know a large<00:11:17.010> fraction<00:11:17.430> of<00:11:17.490> the<00:11:17.640> EVM<00:11:18.449> of<00:11:18.630> code<00:11:18.839> but 00:11:19.490 --> 00:11:19.500 align:start position:0% large fraction of the EVM of code but 00:11:19.500 --> 00:11:20.710 align:start position:0% large fraction of the EVM of code but not<00:11:19.560> all<00:11:19.829> of<00:11:19.860> them 00:11:20.710 --> 00:11:20.720 align:start position:0% not all of them 00:11:20.720 --> 00:11:23.019 align:start position:0% not all of them we<00:11:21.019> can<00:11:21.199> also<00:11:21.350> handle<00:11:21.680> the<00:11:21.860> loops<00:11:22.190> precisely 00:11:23.019 --> 00:11:23.029 align:start position:0% we can also handle the loops precisely 00:11:23.029 --> 00:11:25.360 align:start position:0% we can also handle the loops precisely or<00:11:23.449> we<00:11:23.870> can<00:11:24.050> combine<00:11:24.319> you<00:11:24.709> know<00:11:24.800> static<00:11:25.069> or 00:11:25.360 --> 00:11:25.370 align:start position:0% or we can combine you know static or 00:11:25.370 --> 00:11:28.389 align:start position:0% or we can combine you know static or dynamic<00:11:25.430> a<00:11:26.180> simple<00:11:26.600> execution<00:11:27.230> to<00:11:27.529> reduce<00:11:28.190> a 00:11:28.389 --> 00:11:28.399 align:start position:0% dynamic a simple execution to reduce a 00:11:28.399 --> 00:11:32.499 align:start position:0% dynamic a simple execution to reduce a rate<00:11:28.579> of<00:11:28.790> fun<00:11:29.089> positive<00:11:30.699> so<00:11:31.699> with<00:11:31.940> that<00:11:32.089> I<00:11:32.149> want 00:11:32.499 --> 00:11:32.509 align:start position:0% rate of fun positive so with that I want 00:11:32.509 --> 00:11:40.400 align:start position:0% rate of fun positive so with that I want to<00:11:32.720> conclude<00:11:33.139> my<00:11:33.319> presentation<00:11:33.730> thanks 00:11:40.400 --> 00:11:40.410 align:start position:0% 00:11:40.410 --> 00:11:43.940 align:start position:0% thank<00:11:41.100> you<00:11:41.220> very<00:11:41.250> much<00:11:41.520> light