WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:14.909 align:start position:0% [Music] 00:00:14.909 --> 00:00:14.919 align:start position:0% [Music] 00:00:14.919 --> 00:00:21.280 align:start position:0% [Music] again<00:00:18.070> hi<00:00:19.070> my<00:00:19.280> name<00:00:19.460> is<00:00:19.490> Demetria<00:00:20.150> I'm<00:00:20.930> working 00:00:21.280 --> 00:00:21.290 align:start position:0% again hi my name is Demetria I'm working 00:00:21.290 --> 00:00:22.840 align:start position:0% again hi my name is Demetria I'm working with<00:00:21.410> a<00:00:21.440> foundation<00:00:22.070> for<00:00:22.310> about<00:00:22.520> three<00:00:22.790> years 00:00:22.840 --> 00:00:22.850 align:start position:0% with a foundation for about three years 00:00:22.850 --> 00:00:27.580 align:start position:0% with a foundation for about three years and<00:00:24.400> for<00:00:25.400> a<00:00:25.460> long<00:00:25.580> time<00:00:25.880> a<00:00:26.180> serum<00:00:26.990> testing<00:00:27.440> was 00:00:27.580 --> 00:00:27.590 align:start position:0% and for a long time a serum testing was 00:00:27.590 --> 00:00:30.060 align:start position:0% and for a long time a serum testing was performed<00:00:27.620> by<00:00:28.190> one<00:00:28.820> person<00:00:29.090> Christophe<00:00:29.720> judge 00:00:30.060 --> 00:00:30.070 align:start position:0% performed by one person Christophe judge 00:00:30.070 --> 00:00:32.889 align:start position:0% performed by one person Christophe judge he<00:00:31.070> neutrally<00:00:31.430> invited<00:00:31.970> me<00:00:32.090> to<00:00:32.270> the<00:00:32.329> Assyrian 00:00:32.889 --> 00:00:32.899 align:start position:0% he neutrally invited me to the Assyrian 00:00:32.899 --> 00:00:36.270 align:start position:0% he neutrally invited me to the Assyrian foundation<00:00:33.410> and<00:00:33.650> then<00:00:34.370> I<00:00:34.550> continued<00:00:35.090> his<00:00:35.840> work 00:00:36.270 --> 00:00:36.280 align:start position:0% foundation and then I continued his work 00:00:36.280 --> 00:00:40.390 align:start position:0% foundation and then I continued his work so<00:00:37.280> today<00:00:37.790> I<00:00:37.820> will<00:00:38.060> describe<00:00:38.810> you<00:00:39.079> for<00:00:39.829> you<00:00:39.950> how 00:00:40.390 --> 00:00:40.400 align:start position:0% so today I will describe you for you how 00:00:40.400 --> 00:00:42.430 align:start position:0% so today I will describe you for you how the<00:00:40.460> testing<00:00:41.150> process<00:00:41.360> goes<00:00:41.780> in<00:00:42.050> the<00:00:42.140> serum 00:00:42.430 --> 00:00:42.440 align:start position:0% the testing process goes in the serum 00:00:42.440 --> 00:00:45.430 align:start position:0% the testing process goes in the serum and<00:00:43.000> what<00:00:44.000> we<00:00:44.180> achieved<00:00:44.540> for<00:00:44.780> the<00:00:44.870> last<00:00:45.079> year 00:00:45.430 --> 00:00:45.440 align:start position:0% and what we achieved for the last year 00:00:45.440 --> 00:00:49.780 align:start position:0% and what we achieved for the last year science<00:00:46.100> Shanghai<00:00:47.230> so<00:00:48.230> what<00:00:48.410> we<00:00:48.530> have<00:00:48.800> is<00:00:49.579> a 00:00:49.780 --> 00:00:49.790 align:start position:0% science Shanghai so what we have is a 00:00:49.790 --> 00:00:54.729 align:start position:0% science Shanghai so what we have is a yellow<00:00:50.750> paper<00:00:50.989> which<00:00:51.620> is<00:00:51.950> a<00:00:52.010> protocol<00:00:53.739> yellow 00:00:54.729 --> 00:00:54.739 align:start position:0% yellow paper which is a protocol yellow 00:00:54.739 --> 00:00:56.920 align:start position:0% yellow paper which is a protocol yellow paper<00:00:54.950> describes<00:00:55.489> the<00:00:55.670> serum<00:00:55.940> protocol<00:00:56.450> what 00:00:56.920 --> 00:00:56.930 align:start position:0% paper describes the serum protocol what 00:00:56.930 --> 00:00:59.280 align:start position:0% paper describes the serum protocol what it<00:00:57.079> doesn't<00:00:57.260> make<00:00:57.590> it<00:00:57.620> easier<00:00:58.399> to<00:00:58.460> understand 00:00:59.280 --> 00:00:59.290 align:start position:0% it doesn't make it easier to understand 00:00:59.290 --> 00:01:01.720 align:start position:0% it doesn't make it easier to understand actually<00:01:00.290> this<00:01:00.620> picture<00:01:00.829> represents<00:01:01.130> yellow 00:01:01.720 --> 00:01:01.730 align:start position:0% actually this picture represents yellow 00:01:01.730 --> 00:01:05.680 align:start position:0% actually this picture represents yellow paper<00:01:02.000> really<00:01:02.450> well<00:01:03.549> nobody<00:01:04.549> able<00:01:05.089> to 00:01:05.680 --> 00:01:05.690 align:start position:0% paper really well nobody able to 00:01:05.690 --> 00:01:09.700 align:start position:0% paper really well nobody able to understand<00:01:06.320> this<00:01:06.560> unless<00:01:07.400> we<00:01:07.580> tell<00:01:07.790> it<00:01:07.909> my<00:01:08.710> and 00:01:09.700 --> 00:01:09.710 align:start position:0% understand this unless we tell it my and 00:01:09.710 --> 00:01:12.460 align:start position:0% understand this unless we tell it my and we<00:01:10.640> have<00:01:10.850> lots<00:01:11.090> of<00:01:11.360> implementation<00:01:12.170> of<00:01:12.290> this 00:01:12.460 --> 00:01:12.470 align:start position:0% we have lots of implementation of this 00:01:12.470 --> 00:01:14.289 align:start position:0% we have lots of implementation of this protocol<00:01:12.950> written<00:01:13.490> on<00:01:13.580> different<00:01:13.909> languages 00:01:14.289 --> 00:01:14.299 align:start position:0% protocol written on different languages 00:01:14.299 --> 00:01:18.219 align:start position:0% protocol written on different languages different<00:01:14.360> clients<00:01:15.049> and<00:01:16.750> the<00:01:17.750> testing 00:01:18.219 --> 00:01:18.229 align:start position:0% different clients and the testing 00:01:18.229 --> 00:01:20.980 align:start position:0% different clients and the testing problem<00:01:18.440> is<00:01:18.799> to<00:01:19.040> make<00:01:19.280> sure<00:01:19.340> that<00:01:20.150> every<00:01:20.780> of 00:01:20.980 --> 00:01:20.990 align:start position:0% problem is to make sure that every of 00:01:20.990 --> 00:01:23.590 align:start position:0% problem is to make sure that every of the<00:01:21.229> client<00:01:21.770> is<00:01:21.979> in<00:01:22.460> consensus<00:01:23.150> with<00:01:23.450> each 00:01:23.590 --> 00:01:23.600 align:start position:0% the client is in consensus with each 00:01:23.600 --> 00:01:27.420 align:start position:0% the client is in consensus with each other<00:01:23.840> and<00:01:24.170> they<00:01:25.299> interpret<00:01:26.299> they 00:01:27.420 --> 00:01:27.430 align:start position:0% other and they interpret they 00:01:27.430 --> 00:01:32.469 align:start position:0% other and they interpret they implemented<00:01:28.430> this<00:01:28.610> yellow<00:01:28.880> paper<00:01:29.180> rules<00:01:31.299> in<00:01:32.299> a 00:01:32.469 --> 00:01:32.479 align:start position:0% implemented this yellow paper rules in a 00:01:32.479 --> 00:01:34.600 align:start position:0% implemented this yellow paper rules in a way<00:01:32.659> that<00:01:33.229> there<00:01:33.380> are<00:01:33.470> no<00:01:33.530> consensus<00:01:34.280> issues 00:01:34.600 --> 00:01:34.610 align:start position:0% way that there are no consensus issues 00:01:34.610 --> 00:01:38.620 align:start position:0% way that there are no consensus issues between<00:01:34.880> themselves<00:01:35.240> how<00:01:35.900> to<00:01:36.860> do<00:01:37.010> that<00:01:37.630> we 00:01:38.620 --> 00:01:38.630 align:start position:0% between themselves how to do that we 00:01:38.630 --> 00:01:43.120 align:start position:0% between themselves how to do that we have<00:01:39.100> our<00:01:40.100> testing<00:01:40.729> sealed<00:01:41.470> each<00:01:42.470> test<00:01:42.860> file 00:01:43.120 --> 00:01:43.130 align:start position:0% have our testing sealed each test file 00:01:43.130 --> 00:01:48.490 align:start position:0% have our testing sealed each test file is<00:01:43.520> a<00:01:43.600> JSON<00:01:46.570> instructions<00:01:47.570> encoded<00:01:47.869> in<00:01:48.140> JSON 00:01:48.490 --> 00:01:48.500 align:start position:0% is a JSON instructions encoded in JSON 00:01:48.500 --> 00:01:53.350 align:start position:0% is a JSON instructions encoded in JSON file<00:01:48.740> and<00:01:50.229> we<00:01:51.229> could<00:01:51.380> select<00:01:51.970> three<00:01:52.970> main 00:01:53.350 --> 00:01:53.360 align:start position:0% file and we could select three main 00:01:53.360 --> 00:01:55.499 align:start position:0% file and we could select three main times<00:01:53.720> of<00:01:53.930> the<00:01:54.080> test<00:01:54.320> so<00:01:54.560> the<00:01:54.619> first<00:01:54.860> one<00:01:55.040> is 00:01:55.499 --> 00:01:55.509 align:start position:0% times of the test so the first one is 00:01:55.509 --> 00:02:00.609 align:start position:0% times of the test so the first one is the<00:01:56.509> VM<00:01:56.900> test<00:01:57.200> is<00:01:57.979> basically<00:01:59.409> number<00:02:00.409> of 00:02:00.609 --> 00:02:00.619 align:start position:0% the VM test is basically number of 00:02:00.619 --> 00:02:03.730 align:start position:0% the VM test is basically number of instruction<00:02:01.220> for<00:02:01.430> IBM<00:02:01.939> white<00:02:02.180> machine<00:02:02.740> it's 00:02:03.730 --> 00:02:03.740 align:start position:0% instruction for IBM white machine it's 00:02:03.740 --> 00:02:05.950 align:start position:0% instruction for IBM white machine it's the<00:02:04.460> most<00:02:04.610> simple<00:02:04.970> test<00:02:05.210> in<00:02:05.450> the<00:02:05.509> whole<00:02:05.720> test 00:02:05.950 --> 00:02:05.960 align:start position:0% the most simple test in the whole test 00:02:05.960 --> 00:02:09.940 align:start position:0% the most simple test in the whole test year<00:02:06.200> so<00:02:06.500> if<00:02:07.119> if<00:02:08.119> there<00:02:08.360> is<00:02:08.450> any<00:02:08.950> developers 00:02:09.940 --> 00:02:09.950 align:start position:0% year so if if there is any developers 00:02:09.950 --> 00:02:12.290 align:start position:0% year so if if there is any developers here<00:02:10.280> you<00:02:11.060> could 00:02:12.290 --> 00:02:12.300 align:start position:0% here you could 00:02:12.300 --> 00:02:15.350 align:start position:0% here you could if<00:02:12.900> you<00:02:13.590> implement<00:02:14.040> an<00:02:14.160> EVM<00:02:14.550> you<00:02:14.970> could<00:02:15.150> start 00:02:15.350 --> 00:02:15.360 align:start position:0% if you implement an EVM you could start 00:02:15.360 --> 00:02:18.560 align:start position:0% if you implement an EVM you could start with<00:02:15.510> VM<00:02:16.050> tests<00:02:16.530> a<00:02:16.650> most<00:02:16.860> simple<00:02:17.220> ones 00:02:18.560 --> 00:02:18.570 align:start position:0% with VM tests a most simple ones 00:02:18.570 --> 00:02:21.320 align:start position:0% with VM tests a most simple ones the<00:02:19.350> next<00:02:19.650> either<00:02:19.860> state<00:02:20.340> tests<00:02:20.850> is<00:02:21.000> a<00:02:21.030> bit 00:02:21.320 --> 00:02:21.330 align:start position:0% the next either state tests is a bit 00:02:21.330 --> 00:02:26.380 align:start position:0% the next either state tests is a bit more<00:02:21.510> complex<00:02:21.930> and<00:02:22.200> VM<00:02:23.010> tests<00:02:23.280> it<00:02:24.180> has 00:02:26.380 --> 00:02:26.390 align:start position:0% more complex and VM tests it has 00:02:26.390 --> 00:02:29.120 align:start position:0% more complex and VM tests it has accounts<00:02:27.390> transactions<00:02:28.050> and<00:02:28.380> state<00:02:28.650> changes 00:02:29.120 --> 00:02:29.130 align:start position:0% accounts transactions and state changes 00:02:29.130 --> 00:02:32.030 align:start position:0% accounts transactions and state changes state<00:02:29.850> hashes<00:02:30.420> and<00:02:30.450> so<00:02:31.170> it's<00:02:31.320> a<00:02:31.650> bit<00:02:31.860> more 00:02:32.030 --> 00:02:32.040 align:start position:0% state hashes and so it's a bit more 00:02:32.040 --> 00:02:35.000 align:start position:0% state hashes and so it's a bit more complex<00:02:32.400> and<00:02:32.640> the<00:02:33.360> most<00:02:33.600> sophisticated<00:02:34.170> s<00:02:34.860> is 00:02:35.000 --> 00:02:35.010 align:start position:0% complex and the most sophisticated s is 00:02:35.010 --> 00:02:36.680 align:start position:0% complex and the most sophisticated s is a<00:02:35.040> blockchain<00:02:35.310> it<00:02:35.760> has<00:02:35.970> actual<00:02:36.330> mining 00:02:36.680 --> 00:02:36.690 align:start position:0% a blockchain it has actual mining 00:02:36.690 --> 00:02:38.390 align:start position:0% a blockchain it has actual mining difficulty<00:02:37.170> and<00:02:37.530> those<00:02:37.710> algorithms 00:02:38.390 --> 00:02:38.400 align:start position:0% difficulty and those algorithms 00:02:38.400 --> 00:02:41.840 align:start position:0% difficulty and those algorithms implemented<00:02:39.410> well<00:02:40.410> and<00:02:40.770> for<00:02:41.040> a<00:02:41.070> long<00:02:41.250> time<00:02:41.520> we 00:02:41.840 --> 00:02:41.850 align:start position:0% implemented well and for a long time we 00:02:41.850 --> 00:02:43.960 align:start position:0% implemented well and for a long time we require<00:02:42.300> to<00:02:42.510> all<00:02:42.570> the<00:02:42.720> clients<00:02:43.170> to<00:02:43.290> implement 00:02:43.960 --> 00:02:43.970 align:start position:0% require to all the clients to implement 00:02:43.970 --> 00:02:45.950 align:start position:0% require to all the clients to implement custom<00:02:44.970> tests<00:02:45.450> though 00:02:45.950 --> 00:02:45.960 align:start position:0% custom tests though 00:02:45.960 --> 00:02:48.830 align:start position:0% custom tests though suppose<00:02:46.770> they<00:02:46.920> had<00:02:46.950> to<00:02:47.460> read<00:02:47.730> this<00:02:48.000> JSON<00:02:48.360> files 00:02:48.830 --> 00:02:48.840 align:start position:0% suppose they had to read this JSON files 00:02:48.840 --> 00:02:51.710 align:start position:0% suppose they had to read this JSON files and<00:02:49.290> implement<00:02:49.890> this<00:02:50.100> and<00:02:50.940> compare<00:02:51.540> the 00:02:51.710 --> 00:02:51.720 align:start position:0% and implement this and compare the 00:02:51.720 --> 00:02:59.300 align:start position:0% and implement this and compare the results<00:02:52.910> it<00:02:53.910> was<00:02:54.120> not<00:02:54.360> so<00:02:56.330> so<00:02:57.330> good<00:02:57.920> so<00:02:58.920> we<00:02:59.130> use 00:02:59.300 --> 00:02:59.310 align:start position:0% results it was not so so good so we use 00:02:59.310 --> 00:03:04.820 align:start position:0% results it was not so so good so we use a<00:02:59.340> C++<00:03:00.210> client<00:03:01.040> to<00:03:02.040> run<00:03:02.850> a<00:03:02.880> test<00:03:03.870> source<00:03:04.230> which 00:03:04.820 --> 00:03:04.830 align:start position:0% a C++ client to run a test source which 00:03:04.830 --> 00:03:08.300 align:start position:0% a C++ client to run a test source which is<00:03:05.700> my<00:03:05.880> job<00:03:06.120> is<00:03:06.330> to<00:03:06.870> keep<00:03:07.110> those<00:03:07.380> sources<00:03:08.070> for 00:03:08.300 --> 00:03:08.310 align:start position:0% is my job is to keep those sources for 00:03:08.310 --> 00:03:11.360 align:start position:0% is my job is to keep those sources for test<00:03:08.760> sources<00:03:09.950> updated<00:03:10.950> with<00:03:11.190> the<00:03:11.220> most 00:03:11.360 --> 00:03:11.370 align:start position:0% test sources updated with the most 00:03:11.370 --> 00:03:14.270 align:start position:0% test sources updated with the most recent<00:03:11.940> issues<00:03:12.210> discovered<00:03:12.750> and<00:03:13.070> what<00:03:14.070> we<00:03:14.220> are 00:03:14.270 --> 00:03:14.280 align:start position:0% recent issues discovered and what we are 00:03:14.280 --> 00:03:16.910 align:start position:0% recent issues discovered and what we are trying<00:03:14.460> to<00:03:14.640> achieve<00:03:14.730> is<00:03:15.120> to<00:03:15.480> create<00:03:16.380> lots<00:03:16.709> of 00:03:16.910 --> 00:03:16.920 align:start position:0% trying to achieve is to create lots of 00:03:16.920 --> 00:03:18.890 align:start position:0% trying to achieve is to create lots of lots<00:03:17.160> of<00:03:17.340> different<00:03:17.400> test<00:03:18.060> source<00:03:18.510> files 00:03:18.890 --> 00:03:18.900 align:start position:0% lots of different test source files 00:03:18.900 --> 00:03:21.170 align:start position:0% lots of different test source files describing<00:03:19.860> all<00:03:20.010> of<00:03:20.040> the<00:03:20.250> possible<00:03:20.640> situation 00:03:21.170 --> 00:03:21.180 align:start position:0% describing all of the possible situation 00:03:21.180 --> 00:03:24.980 align:start position:0% describing all of the possible situation which<00:03:21.540> we<00:03:21.750> could<00:03:22.820> get<00:03:23.820> in<00:03:23.970> a<00:03:24.120> VM<00:03:24.630> code 00:03:24.980 --> 00:03:24.990 align:start position:0% which we could get in a VM code 00:03:24.990 --> 00:03:28.550 align:start position:0% which we could get in a VM code execution<00:03:25.530> and<00:03:25.980> then<00:03:26.910> C++<00:03:27.660> clang<00:03:27.870> execute 00:03:28.550 --> 00:03:28.560 align:start position:0% execution and then C++ clang execute 00:03:28.560 --> 00:03:31.100 align:start position:0% execution and then C++ clang execute those<00:03:29.030> instructions<00:03:30.030> and<00:03:30.330> it<00:03:30.630> creates<00:03:30.990> a 00:03:31.100 --> 00:03:31.110 align:start position:0% those instructions and it creates a 00:03:31.110 --> 00:03:33.590 align:start position:0% those instructions and it creates a final<00:03:31.470> test<00:03:31.650> final<00:03:32.100> test<00:03:32.310> is<00:03:32.760> being<00:03:33.330> processed 00:03:33.590 --> 00:03:33.600 align:start position:0% final test final test is being processed 00:03:33.600 --> 00:03:36.800 align:start position:0% final test final test is being processed by<00:03:33.870> other<00:03:34.080> clients<00:03:34.380> and<00:03:35.120> say<00:03:36.120> compares<00:03:36.570> their 00:03:36.800 --> 00:03:36.810 align:start position:0% by other clients and say compares their 00:03:36.810 --> 00:03:38.990 align:start position:0% by other clients and say compares their results<00:03:37.350> to<00:03:37.380> the<00:03:37.650> C++<00:03:38.220> clients<00:03:38.700> and<00:03:38.880> that's 00:03:38.990 --> 00:03:39.000 align:start position:0% results to the C++ clients and that's 00:03:39.000 --> 00:03:41.150 align:start position:0% results to the C++ clients and that's how<00:03:39.209> we<00:03:39.270> see<00:03:39.600> if<00:03:39.840> everyone<00:03:40.320> agrees<00:03:40.650> with<00:03:40.890> C++ 00:03:41.150 --> 00:03:41.160 align:start position:0% how we see if everyone agrees with C++ 00:03:41.160 --> 00:03:45.830 align:start position:0% how we see if everyone agrees with C++ client<00:03:41.760> which<00:03:42.480> is<00:03:42.870> like<00:03:43.350> a<00:03:43.620> golden<00:03:44.220> star<00:03:44.840> user 00:03:45.830 --> 00:03:45.840 align:start position:0% client which is like a golden star user 00:03:45.840 --> 00:03:48.260 align:start position:0% client which is like a golden star user is<00:03:46.050> an<00:03:46.200> issue<00:03:46.350> we<00:03:47.040> open<00:03:47.490> up<00:03:47.550> these<00:03:47.700> put<00:03:47.970> and 00:03:48.260 --> 00:03:48.270 align:start position:0% is an issue we open up these put and 00:03:48.270 --> 00:03:50.120 align:start position:0% is an issue we open up these put and discuss<00:03:48.720> whether<00:03:48.990> we<00:03:49.170> have<00:03:49.380> to<00:03:49.410> make<00:03:49.680> a<00:03:49.709> change 00:03:50.120 --> 00:03:50.130 align:start position:0% discuss whether we have to make a change 00:03:50.130 --> 00:03:56.270 align:start position:0% discuss whether we have to make a change in<00:03:50.370> the<00:03:50.459> C++<00:03:50.670> client<00:03:51.270> or<00:03:51.420> other<00:03:51.720> clients<00:03:54.770> so<00:03:55.770> we 00:03:56.270 --> 00:03:56.280 align:start position:0% in the C++ client or other clients so we 00:03:56.280 --> 00:04:01.940 align:start position:0% in the C++ client or other clients so we had<00:03:57.090> a<00:03:57.120> couple<00:03:57.480> of<00:03:57.690> problems<00:04:00.800> the<00:04:01.800> first 00:04:01.940 --> 00:04:01.950 align:start position:0% had a couple of problems the first 00:04:01.950 --> 00:04:03.980 align:start position:0% had a couple of problems the first problem<00:04:02.070> is<00:04:02.459> to<00:04:02.730> create<00:04:03.030> an<00:04:03.360> ultimate<00:04:03.959> test 00:04:03.980 --> 00:04:03.990 align:start position:0% problem is to create an ultimate test 00:04:03.990 --> 00:04:06.860 align:start position:0% problem is to create an ultimate test which<00:04:04.800> covers<00:04:05.190> all<00:04:05.459> of<00:04:05.640> the<00:04:05.910> code<00:04:06.209> or<00:04:06.510> all<00:04:06.690> the 00:04:06.860 --> 00:04:06.870 align:start position:0% which covers all of the code or all the 00:04:06.870 --> 00:04:09.080 align:start position:0% which covers all of the code or all the possible<00:04:07.230> situations<00:04:07.440> which<00:04:08.070> could<00:04:08.610> run<00:04:08.790> and 00:04:09.080 --> 00:04:09.090 align:start position:0% possible situations which could run and 00:04:09.090 --> 00:04:11.180 align:start position:0% possible situations which could run and possibly<00:04:09.900> find<00:04:10.140> all<00:04:10.350> of<00:04:10.380> the<00:04:10.620> bugs<00:04:10.830> and 00:04:11.180 --> 00:04:11.190 align:start position:0% possibly find all of the bugs and 00:04:11.190 --> 00:04:13.550 align:start position:0% possibly find all of the bugs and concerns<00:04:11.760> to<00:04:11.820> see<00:04:12.030> here's<00:04:12.300> the<00:04:12.560> second 00:04:13.550 --> 00:04:13.560 align:start position:0% concerns to see here's the second 00:04:13.560 --> 00:04:17.330 align:start position:0% concerns to see here's the second problem<00:04:13.739> is<00:04:14.220> that<00:04:14.780> clients<00:04:15.780> they<00:04:16.770> should 00:04:17.330 --> 00:04:17.340 align:start position:0% problem is that clients they should 00:04:17.340 --> 00:04:20.479 align:start position:0% problem is that clients they should execute<00:04:17.940> our<00:04:18.299> tests<00:04:18.810> and<00:04:18.989> because<00:04:19.650> before<00:04:20.340> we 00:04:20.479 --> 00:04:20.489 align:start position:0% execute our tests and because before we 00:04:20.489 --> 00:04:22.430 align:start position:0% execute our tests and because before we are<00:04:20.580> required<00:04:20.940> to<00:04:21.090> my<00:04:21.390> exact<00:04:21.750> clients<00:04:22.229> this 00:04:22.430 --> 00:04:22.440 align:start position:0% are required to my exact clients this 00:04:22.440 --> 00:04:24.070 align:start position:0% are required to my exact clients this custom<00:04:23.040> tool 00:04:24.070 --> 00:04:24.080 align:start position:0% custom tool 00:04:24.080 --> 00:04:28.029 align:start position:0% custom tool I<00:04:25.419> had<00:04:26.419> to<00:04:26.599> manually<00:04:26.960> ask<00:04:27.319> every<00:04:27.710> client 00:04:28.029 --> 00:04:28.039 align:start position:0% I had to manually ask every client 00:04:28.039 --> 00:04:30.189 align:start position:0% I had to manually ask every client developer<00:04:28.550> have<00:04:28.819> you<00:04:28.970> run<00:04:29.120> this<00:04:29.300> test<00:04:29.509> have 00:04:30.189 --> 00:04:30.199 align:start position:0% developer have you run this test have 00:04:30.199 --> 00:04:32.110 align:start position:0% developer have you run this test have you<00:04:30.319> updated<00:04:30.650> the<00:04:30.800> test<00:04:31.099> repository<00:04:31.699> is<00:04:32.000> it 00:04:32.110 --> 00:04:32.120 align:start position:0% you updated the test repository is it 00:04:32.120 --> 00:04:34.210 align:start position:0% you updated the test repository is it updated<00:04:32.449> and<00:04:32.750> one<00:04:33.319> time<00:04:33.500> I<00:04:33.620> discovered<00:04:33.830> that 00:04:34.210 --> 00:04:34.220 align:start position:0% updated and one time I discovered that 00:04:34.220 --> 00:04:37.899 align:start position:0% updated and one time I discovered that core<00:04:34.550> client<00:04:35.030> wasn't<00:04:36.190> running<00:04:37.190> the<00:04:37.220> recent 00:04:37.899 --> 00:04:37.909 align:start position:0% core client wasn't running the recent 00:04:37.909 --> 00:04:40.330 align:start position:0% core client wasn't running the recent tests<00:04:38.120> for<00:04:38.330> about<00:04:38.539> half<00:04:38.810> of<00:04:38.930> one<00:04:39.139> a<00:04:39.169> year<00:04:39.470> and 00:04:40.330 --> 00:04:40.340 align:start position:0% tests for about half of one a year and 00:04:40.340 --> 00:04:42.100 align:start position:0% tests for about half of one a year and the<00:04:40.490> ghosa<00:04:40.669> there<00:04:41.300> was<00:04:41.419> a<00:04:41.449> heart<00:04:41.720> for<00:04:41.900> cover 00:04:42.100 --> 00:04:42.110 align:start position:0% the ghosa there was a heart for cover 00:04:42.110 --> 00:04:44.920 align:start position:0% the ghosa there was a heart for cover radiantly<00:04:42.590> it<00:04:42.889> still<00:04:43.250> not<00:04:43.520> cut<00:04:43.930> medication 00:04:44.920 --> 00:04:44.930 align:start position:0% radiantly it still not cut medication 00:04:44.930 --> 00:04:48.249 align:start position:0% radiantly it still not cut medication abuse<00:04:45.199> the<00:04:45.289> test<00:04:46.599> not<00:04:47.599> to<00:04:47.750> mention<00:04:47.930> that<00:04:48.139> I 00:04:48.249 --> 00:04:48.259 align:start position:0% abuse the test not to mention that I 00:04:48.259 --> 00:04:51.540 align:start position:0% abuse the test not to mention that I don't<00:04:48.470> know<00:04:48.620> the<00:04:48.830> status<00:04:49.039> of<00:04:49.310> other<00:04:49.490> clients 00:04:51.540 --> 00:04:51.550 align:start position:0% don't know the status of other clients 00:04:51.550 --> 00:04:53.010 align:start position:0% don't know the status of other clients [Music] 00:04:53.010 --> 00:04:53.020 align:start position:0% [Music] 00:04:53.020 --> 00:04:59.559 align:start position:0% [Music] so<00:04:54.460> how<00:04:55.460> we<00:04:56.030> solve<00:04:56.539> those<00:04:56.780> issues<00:04:58.210> to<00:04:59.210> get<00:04:59.360> the 00:04:59.559 --> 00:04:59.569 align:start position:0% so how we solve those issues to get the 00:04:59.569 --> 00:05:03.640 align:start position:0% so how we solve those issues to get the best<00:04:59.960> code<00:05:00.229> coverage<00:05:00.590> just<00:05:01.550> we<00:05:01.789> have<00:05:02.650> tests 00:05:03.640 --> 00:05:03.650 align:start position:0% best code coverage just we have tests 00:05:03.650 --> 00:05:05.770 align:start position:0% best code coverage just we have tests cases<00:05:04.159> list<00:05:04.400> which<00:05:04.759> could<00:05:05.000> be<00:05:05.180> found<00:05:05.389> on 00:05:05.770 --> 00:05:05.780 align:start position:0% cases list which could be found on 00:05:05.780 --> 00:05:10.719 align:start position:0% cases list which could be found on Google<00:05:07.120> Documents<00:05:08.919> this<00:05:09.919> is<00:05:10.039> the<00:05:10.129> many<00:05:10.340> o<00:05:10.430> test 00:05:10.719 --> 00:05:10.729 align:start position:0% Google Documents this is the many o test 00:05:10.729 --> 00:05:13.059 align:start position:0% Google Documents this is the many o test cases<00:05:11.000> if<00:05:11.539> you<00:05:11.750> came<00:05:12.169> up<00:05:12.199> with<00:05:12.530> an<00:05:12.680> idea<00:05:12.770> for 00:05:13.059 --> 00:05:13.069 align:start position:0% cases if you came up with an idea for 00:05:13.069 --> 00:05:15.580 align:start position:0% cases if you came up with an idea for test<00:05:13.460> case<00:05:13.699> you<00:05:13.879> could<00:05:14.120> manually<00:05:14.479> add<00:05:14.750> this<00:05:15.020> to 00:05:15.580 --> 00:05:15.590 align:start position:0% test case you could manually add this to 00:05:15.590 --> 00:05:21.249 align:start position:0% test case you could manually add this to this<00:05:17.560> also<00:05:18.560> I<00:05:19.099> want<00:05:19.849> to<00:05:19.879> mention<00:05:20.000> if<00:05:20.479> you<00:05:20.659> think 00:05:21.249 --> 00:05:21.259 align:start position:0% this also I want to mention if you think 00:05:21.259 --> 00:05:23.830 align:start position:0% this also I want to mention if you think you<00:05:21.469> know<00:05:21.710> how<00:05:21.979> to<00:05:22.039> make<00:05:22.610> a<00:05:22.639> consensus<00:05:23.360> Asian's 00:05:23.830 --> 00:05:23.840 align:start position:0% you know how to make a consensus Asian's 00:05:23.840 --> 00:05:27.100 align:start position:0% you know how to make a consensus Asian's is<00:05:24.020> a<00:05:24.069> reward<00:05:25.069> for<00:05:25.669> bug<00:05:25.940> bounty<00:05:26.509> from<00:05:26.930> the 00:05:27.100 --> 00:05:27.110 align:start position:0% is a reward for bug bounty from the 00:05:27.110 --> 00:05:29.019 align:start position:0% is a reward for bug bounty from the foundation<00:05:27.710> if<00:05:27.889> you<00:05:28.009> discover<00:05:28.400> a<00:05:28.460> consensus 00:05:29.019 --> 00:05:29.029 align:start position:0% foundation if you discover a consensus 00:05:29.029 --> 00:05:36.610 align:start position:0% foundation if you discover a consensus this<00:05:29.210> year<00:05:29.409> you<00:05:30.409> could<00:05:30.620> get<00:05:30.800> money<00:05:32.529> and<00:05:35.560> so<00:05:36.560> to 00:05:36.610 --> 00:05:36.620 align:start position:0% this year you could get money and so to 00:05:36.620 --> 00:05:39.640 align:start position:0% this year you could get money and so to cover<00:05:36.919> even<00:05:37.430> more<00:05:37.759> cases<00:05:38.029> you<00:05:38.539> can<00:05:38.750> you<00:05:39.469> can 00:05:39.640 --> 00:05:39.650 align:start position:0% cover even more cases you can you can 00:05:39.650 --> 00:05:41.589 align:start position:0% cover even more cases you can you can possibly<00:05:39.979> come<00:05:40.219> up<00:05:40.340> with<00:05:40.370> every<00:05:41.000> situation 00:05:41.589 --> 00:05:41.599 align:start position:0% possibly come up with every situation 00:05:41.599 --> 00:05:44.730 align:start position:0% possibly come up with every situation but<00:05:41.840> I<00:05:42.199> think<00:05:42.380> it's<00:05:42.740> impossible<00:05:43.009> so<00:05:43.550> we<00:05:43.849> did 00:05:44.730 --> 00:05:44.740 align:start position:0% but I think it's impossible so we did 00:05:44.740 --> 00:05:49.570 align:start position:0% but I think it's impossible so we did some<00:05:46.270> tools<00:05:47.270> that<00:05:48.199> basically<00:05:48.770> run<00:05:49.009> a<00:05:49.219> random 00:05:49.570 --> 00:05:49.580 align:start position:0% some tools that basically run a random 00:05:49.580 --> 00:05:52.719 align:start position:0% some tools that basically run a random code<00:05:49.880> random<00:05:50.360> even<00:05:50.569> bytecode<00:05:51.199> on<00:05:51.800> not<00:05:52.400> really 00:05:52.719 --> 00:05:52.729 align:start position:0% code random even bytecode on not really 00:05:52.729 --> 00:05:55.629 align:start position:0% code random even bytecode on not really random<00:05:53.090> like<00:05:53.270> fast<00:05:53.599> testing<00:05:54.110> is<00:05:54.379> a<00:05:54.639> smart 00:05:55.629 --> 00:05:55.639 align:start position:0% random like fast testing is a smart 00:05:55.639 --> 00:05:58.480 align:start position:0% random like fast testing is a smart random<00:05:56.060> code<00:05:56.300> and<00:05:56.779> this<00:05:57.319> code<00:05:57.379> hope<00:05:58.069> we<00:05:58.340> hope 00:05:58.480 --> 00:05:58.490 align:start position:0% random code and this code hope we hope 00:05:58.490 --> 00:06:01.450 align:start position:0% random code and this code hope we hope that<00:05:58.729> it<00:05:59.300> will<00:05:59.360> find<00:06:00.229> some<00:06:00.440> consensus<00:06:01.069> ratio 00:06:01.450 --> 00:06:01.460 align:start position:0% that it will find some consensus ratio 00:06:01.460 --> 00:06:04.930 align:start position:0% that it will find some consensus ratio and<00:06:01.699> it<00:06:02.000> did<00:06:02.889> another<00:06:03.889> approach<00:06:04.250> will<00:06:04.460> be<00:06:04.610> to 00:06:04.930 --> 00:06:04.940 align:start position:0% and it did another approach will be to 00:06:04.940 --> 00:06:09.040 align:start position:0% and it did another approach will be to use<00:06:05.150> a<00:06:05.229> fancy<00:06:06.229> tool<00:06:06.440> that<00:06:07.150> you<00:06:08.150> analyze<00:06:08.449> a 00:06:09.040 --> 00:06:09.050 align:start position:0% use a fancy tool that you analyze a 00:06:09.050 --> 00:06:10.959 align:start position:0% use a fancy tool that you analyze a source<00:06:09.500> of<00:06:09.740> a<00:06:09.860> client<00:06:10.250> and<00:06:10.310> then<00:06:10.729> run 00:06:10.959 --> 00:06:10.969 align:start position:0% source of a client and then run 00:06:10.969 --> 00:06:13.619 align:start position:0% source of a client and then run different<00:06:11.509> white-coat<00:06:12.409> executions<00:06:13.069> and 00:06:13.619 --> 00:06:13.629 align:start position:0% different white-coat executions and 00:06:13.629 --> 00:06:16.149 align:start position:0% different white-coat executions and maybe<00:06:14.629> some<00:06:14.900> fancy<00:06:15.289> other<00:06:15.409> reasons<00:06:15.830> and 00:06:16.149 --> 00:06:16.159 align:start position:0% maybe some fancy other reasons and 00:06:16.159 --> 00:06:24.790 align:start position:0% maybe some fancy other reasons and you'll<00:06:16.669> produce<00:06:16.849> a<00:06:18.250> very<00:06:19.250> very<00:06:19.520> good<00:06:19.759> test<00:06:23.770> ok 00:06:24.790 --> 00:06:24.800 align:start position:0% you'll produce a very very good test ok 00:06:24.800 --> 00:06:27.309 align:start position:0% you'll produce a very very good test ok two<00:06:25.190> solves<00:06:25.550> the<00:06:25.639> next<00:06:25.940> issue<00:06:26.090> is<00:06:26.599> the<00:06:26.900> clients 00:06:27.309 --> 00:06:27.319 align:start position:0% two solves the next issue is the clients 00:06:27.319 --> 00:06:30.010 align:start position:0% two solves the next issue is the clients being<00:06:27.500> updated<00:06:28.270> last<00:06:29.270> year<00:06:29.509> i<00:06:29.539> mentioned<00:06:29.990> that 00:06:30.010 --> 00:06:30.020 align:start position:0% being updated last year i mentioned that 00:06:30.020 --> 00:06:32.879 align:start position:0% being updated last year i mentioned that we<00:06:30.229> have<00:06:30.440> a<00:06:30.469> hive<00:06:31.430> tool<00:06:31.729> in<00:06:31.849> development<00:06:32.449> and 00:06:32.879 --> 00:06:32.889 align:start position:0% we have a hive tool in development and 00:06:32.889 --> 00:06:35.709 align:start position:0% we have a hive tool in development and now<00:06:33.889> it's<00:06:34.099> life<00:06:34.399> and<00:06:34.550> working<00:06:35.029> now<00:06:35.360> we<00:06:35.419> no 00:06:35.709 --> 00:06:35.719 align:start position:0% now it's life and working now we no 00:06:35.719 --> 00:06:36.629 align:start position:0% now it's life and working now we no longer<00:06:35.750> require 00:06:36.629 --> 00:06:36.639 align:start position:0% longer require 00:06:36.639 --> 00:06:38.969 align:start position:0% longer require time<00:06:36.849> to<00:06:36.999> implement<00:06:37.120> a<00:06:37.449> custom<00:06:37.659> test<00:06:38.110> oh<00:06:38.319> they 00:06:38.969 --> 00:06:38.979 align:start position:0% time to implement a custom test oh they 00:06:38.979 --> 00:06:41.249 align:start position:0% time to implement a custom test oh they just<00:06:39.009> need<00:06:39.430> to<00:06:39.580> provide<00:06:39.879> a<00:06:39.939> client<00:06:40.449> and<00:06:40.629> an<00:06:40.780> RPC 00:06:41.249 --> 00:06:41.259 align:start position:0% just need to provide a client and an RPC 00:06:41.259 --> 00:06:45.689 align:start position:0% just need to provide a client and an RPC interface<00:06:41.620> and<00:06:43.349> then<00:06:44.349> any<00:06:45.039> client<00:06:45.520> could<00:06:45.669> be 00:06:45.689 --> 00:06:45.699 align:start position:0% interface and then any client could be 00:06:45.699 --> 00:06:48.149 align:start position:0% interface and then any client could be integrated<00:06:46.270> in<00:06:46.389> a<00:06:46.509> hive<00:06:46.719> tool<00:06:47.050> and<00:06:47.349> this<00:06:47.889> have 00:06:48.149 --> 00:06:48.159 align:start position:0% integrated in a hive tool and this have 00:06:48.159 --> 00:06:51.050 align:start position:0% integrated in a hive tool and this have to<00:06:48.340> perform<00:06:48.939> a<00:06:49.150> test<00:06:49.449> execution 00:06:51.050 --> 00:06:51.060 align:start position:0% to perform a test execution 00:06:51.060 --> 00:06:54.300 align:start position:0% to perform a test execution automatically<00:06:52.060> and<00:06:52.300> we<00:06:52.779> have<00:06:53.080> results<00:06:53.800> equals 00:06:54.300 --> 00:06:54.310 align:start position:0% automatically and we have results equals 00:06:54.310 --> 00:06:57.209 align:start position:0% automatically and we have results equals C<00:06:54.490> on<00:06:54.759> a<00:06:54.789> high<00:06:55.120> stats<00:06:55.659> page<00:06:56.020> there<00:06:56.740> is<00:06:56.860> also<00:06:57.039> of 00:06:57.209 --> 00:06:57.219 align:start position:0% C on a high stats page there is also of 00:06:57.219 --> 00:07:01.219 align:start position:0% C on a high stats page there is also of all<00:06:57.490> the<00:06:57.669> rest<00:06:57.969> execution<00:06:58.749> on<00:06:58.960> every<00:06:59.379> client 00:07:01.219 --> 00:07:01.229 align:start position:0% all the rest execution on every client 00:07:01.229 --> 00:07:04.619 align:start position:0% all the rest execution on every client also<00:07:02.430> clients<00:07:03.430> have<00:07:03.639> continuous<00:07:04.419> integration 00:07:04.619 --> 00:07:04.629 align:start position:0% also clients have continuous integration 00:07:04.629 --> 00:07:09.119 align:start position:0% also clients have continuous integration bills<00:07:05.229> in<00:07:05.499> a<00:07:05.590> github<00:07:05.800> each<00:07:06.430> commit<00:07:08.129> executes 00:07:09.119 --> 00:07:09.129 align:start position:0% bills in a github each commit executes 00:07:09.129 --> 00:07:11.249 align:start position:0% bills in a github each commit executes this<00:07:09.310> continuous<00:07:10.150> integration<00:07:10.300> test<00:07:10.870> in<00:07:11.139> a 00:07:11.249 --> 00:07:11.259 align:start position:0% this continuous integration test in a 00:07:11.259 --> 00:07:14.309 align:start position:0% this continuous integration test in a github<00:07:11.469> which<00:07:12.129> synced<00:07:13.029> with<00:07:13.060> our<00:07:13.599> test<00:07:14.050> wrap 00:07:14.309 --> 00:07:14.319 align:start position:0% github which synced with our test wrap 00:07:14.319 --> 00:07:18.409 align:start position:0% github which synced with our test wrap or<00:07:14.529> a<00:07:14.710> serum<00:07:15.099> tests<00:07:15.460> and<00:07:16.710> I<00:07:17.710> still<00:07:18.159> personally 00:07:18.409 --> 00:07:18.419 align:start position:0% or a serum tests and I still personally 00:07:18.419 --> 00:07:22.379 align:start position:0% or a serum tests and I still personally do<00:07:19.419> ask<00:07:20.379> people<00:07:20.590> on<00:07:21.159> a<00:07:21.189> Skype<00:07:21.610> our<00:07:21.849> channels 00:07:22.379 --> 00:07:22.389 align:start position:0% do ask people on a Skype our channels 00:07:22.389 --> 00:07:24.420 align:start position:0% do ask people on a Skype our channels versus<00:07:22.810> a<00:07:22.900> pay<00:07:23.050> phone<00:07:23.229> most<00:07:23.889> recent<00:07:24.279> test 00:07:24.420 --> 00:07:24.430 align:start position:0% versus a pay phone most recent test 00:07:24.430 --> 00:07:30.240 align:start position:0% versus a pay phone most recent test executions<00:07:26.610> another<00:07:27.719> field<00:07:28.719> of<00:07:28.900> work<00:07:29.250> which 00:07:30.240 --> 00:07:30.250 align:start position:0% executions another field of work which 00:07:30.250 --> 00:07:33.929 align:start position:0% executions another field of work which was<00:07:30.550> performed<00:07:30.939> by<00:07:31.150> Casey<00:07:32.729> he<00:07:33.729> did 00:07:33.929 --> 00:07:33.939 align:start position:0% was performed by Casey he did 00:07:33.939 --> 00:07:38.010 align:start position:0% was performed by Casey he did standardization<00:07:34.839> of<00:07:35.370> IBM<00:07:36.370> logs<00:07:36.639> and<00:07:36.909> by<00:07:37.839> doing 00:07:38.010 --> 00:07:38.020 align:start position:0% standardization of IBM logs and by doing 00:07:38.020 --> 00:07:40.079 align:start position:0% standardization of IBM logs and by doing this<00:07:38.289> we<00:07:38.469> could<00:07:38.710> now<00:07:38.860> compare<00:07:39.370> that<00:07:39.400> not<00:07:39.789> only 00:07:40.079 --> 00:07:40.089 align:start position:0% this we could now compare that not only 00:07:40.089 --> 00:07:42.269 align:start position:0% this we could now compare that not only we<00:07:40.210> have<00:07:40.240> the<00:07:40.449> same<00:07:41.199> hash<00:07:41.469> after<00:07:41.919> the<00:07:42.069> test 00:07:42.269 --> 00:07:42.279 align:start position:0% we have the same hash after the test 00:07:42.279 --> 00:07:44.909 align:start position:0% we have the same hash after the test execution<00:07:42.550> but<00:07:43.449> the<00:07:43.990> way<00:07:44.169> we<00:07:44.349> get<00:07:44.589> to<00:07:44.740> that 00:07:44.909 --> 00:07:44.919 align:start position:0% execution but the way we get to that 00:07:44.919 --> 00:07:47.059 align:start position:0% execution but the way we get to that hash<00:07:45.129> is<00:07:45.430> exactly<00:07:46.060> the<00:07:46.240> same<00:07:46.419> on<00:07:46.479> every<00:07:46.839> client 00:07:47.059 --> 00:07:47.069 align:start position:0% hash is exactly the same on every client 00:07:47.069 --> 00:07:51.829 align:start position:0% hash is exactly the same on every client and<00:07:48.599> for<00:07:49.599> the<00:07:49.719> past<00:07:49.900> year<00:07:50.229> we<00:07:50.379> added<00:07:50.680> some 00:07:51.829 --> 00:07:51.839 align:start position:0% and for the past year we added some 00:07:51.839 --> 00:07:53.850 align:start position:0% and for the past year we added some debugging<00:07:52.839> for<00:07:53.379> the<00:07:53.529> test 00:07:53.850 --> 00:07:53.860 align:start position:0% debugging for the test 00:07:53.860 --> 00:07:59.519 align:start position:0% debugging for the test if<00:07:53.979> to<00:07:54.250> which<00:07:54.849> I'm<00:07:55.089> a<00:07:55.120> developer<00:07:55.689> and<00:07:58.529> it's 00:07:59.519 --> 00:07:59.529 align:start position:0% if to which I'm a developer and it's 00:07:59.529 --> 00:08:03.019 align:start position:0% if to which I'm a developer and it's basically<00:07:59.979> a<00:08:00.129> whole<00:08:00.610> new<00:08:01.210> field<00:08:01.509> of<00:08:01.689> work<00:08:01.990> with 00:08:03.019 --> 00:08:03.029 align:start position:0% basically a whole new field of work with 00:08:03.029 --> 00:08:06.719 align:start position:0% basically a whole new field of work with those<00:08:04.029> traces<00:08:04.659> for<00:08:05.020> again<00:08:05.259> and<00:08:05.729> better 00:08:06.719 --> 00:08:06.729 align:start position:0% those traces for again and better 00:08:06.729 --> 00:08:12.629 align:start position:0% those traces for again and better debugging<00:08:09.509> okay<00:08:10.509> and<00:08:10.750> another<00:08:11.379> update<00:08:12.099> for 00:08:12.629 --> 00:08:12.639 align:start position:0% debugging okay and another update for 00:08:12.639 --> 00:08:14.459 align:start position:0% debugging okay and another update for the<00:08:12.759> way<00:08:12.819> for<00:08:13.300> this<00:08:13.419> year<00:08:13.750> will<00:08:13.899> be<00:08:14.080> my 00:08:14.459 --> 00:08:14.469 align:start position:0% the way for this year will be my 00:08:14.469 --> 00:08:19.019 align:start position:0% the way for this year will be my personal<00:08:15.039> for<00:08:15.310> coverage<00:08:17.279> by<00:08:18.279> fork<00:08:18.610> I<00:08:18.789> mean 00:08:19.019 --> 00:08:19.029 align:start position:0% personal for coverage by fork I mean 00:08:19.029 --> 00:08:22.829 align:start position:0% personal for coverage by fork I mean serum<00:08:20.020> has<00:08:20.289> certain<00:08:21.039> hard<00:08:21.789> work<00:08:22.029> points<00:08:22.449> like 00:08:22.829 --> 00:08:22.839 align:start position:0% serum has certain hard work points like 00:08:22.839 --> 00:08:28.200 align:start position:0% serum has certain hard work points like constant<00:08:23.439> and<00:08:25.169> other<00:08:26.169> proposals<00:08:26.740> which<00:08:27.250> we 00:08:28.200 --> 00:08:28.210 align:start position:0% constant and other proposals which we 00:08:28.210 --> 00:08:30.029 align:start position:0% constant and other proposals which we actually<00:08:28.689> don't<00:08:28.839> have<00:08:29.139> a<00:08:29.169> consensus<00:08:29.919> about 00:08:30.029 --> 00:08:30.039 align:start position:0% actually don't have a consensus about 00:08:30.039 --> 00:08:34.050 align:start position:0% actually don't have a consensus about naming<00:08:30.460> those<00:08:30.789> Forks<00:08:31.149> I<00:08:31.300> called<00:08:31.539> like<00:08:31.870> EAP<00:08:33.060> 158 00:08:34.050 --> 00:08:34.060 align:start position:0% naming those Forks I called like EAP 158 00:08:34.060 --> 00:08:36.360 align:start position:0% naming those Forks I called like EAP 158 and<00:08:34.360> others<00:08:34.750> codes<00:08:35.079> and<00:08:35.409> some<00:08:35.620> kinds<00:08:35.919> of<00:08:36.039> beers 00:08:36.360 --> 00:08:36.370 align:start position:0% and others codes and some kinds of beers 00:08:36.370 --> 00:08:44.069 align:start position:0% and others codes and some kinds of beers dragons<00:08:36.849> and<00:08:39.360> those<00:08:40.890> points<00:08:41.890> means<00:08:42.640> that<00:08:43.269> from 00:08:44.069 --> 00:08:44.079 align:start position:0% dragons and those points means that from 00:08:44.079 --> 00:08:48.269 align:start position:0% dragons and those points means that from this<00:08:44.640> particular<00:08:45.640> block<00:08:46.589> the<00:08:47.589> protocol<00:08:48.069> has 00:08:48.269 --> 00:08:48.279 align:start position:0% this particular block the protocol has 00:08:48.279 --> 00:08:50.420 align:start position:0% this particular block the protocol has changed<00:08:48.760> and<00:08:48.910> we<00:08:49.420> have 00:08:50.420 --> 00:08:50.430 align:start position:0% changed and we have 00:08:50.430 --> 00:08:53.030 align:start position:0% changed and we have test<00:08:50.610> that<00:08:51.060> all<00:08:51.360> the<00:08:51.720> changes<00:08:52.170> and<00:08:52.440> all<00:08:52.680> of<00:08:52.890> the 00:08:53.030 --> 00:08:53.040 align:start position:0% test that all the changes and all of the 00:08:53.040 --> 00:09:01.850 align:start position:0% test that all the changes and all of the clients<00:08:57.230> implemented<00:08:58.230> correctly<00:08:59.899> but<00:09:00.899> we 00:09:01.850 --> 00:09:01.860 align:start position:0% clients implemented correctly but we 00:09:01.860 --> 00:09:09.320 align:start position:0% clients implemented correctly but we have<00:09:02.040> a<00:09:02.070> test<00:09:02.460> cases<00:09:02.790> and<00:09:03.589> there<00:09:04.610> I<00:09:07.880> had<00:09:08.880> many 00:09:09.320 --> 00:09:09.330 align:start position:0% have a test cases and there I had many 00:09:09.330 --> 00:09:11.300 align:start position:0% have a test cases and there I had many only<00:09:09.630> to<00:09:09.810> copy<00:09:10.020> all<00:09:10.290> of<00:09:10.320> the<00:09:10.500> test<00:09:10.740> cases<00:09:10.980> for 00:09:11.300 --> 00:09:11.310 align:start position:0% only to copy all of the test cases for 00:09:11.310 --> 00:09:12.199 align:start position:0% only to copy all of the test cases for each<00:09:11.339> heart<00:09:11.670> Fork 00:09:12.199 --> 00:09:12.209 align:start position:0% each heart Fork 00:09:12.209 --> 00:09:15.380 align:start position:0% each heart Fork and<00:09:12.649> then<00:09:13.649> I<00:09:13.890> came<00:09:14.160> up<00:09:14.399> with<00:09:14.580> an<00:09:14.700> idea<00:09:14.850> of 00:09:15.380 --> 00:09:15.390 align:start position:0% and then I came up with an idea of 00:09:15.390 --> 00:09:19.070 align:start position:0% and then I came up with an idea of general<00:09:16.290> test<00:09:16.700> format<00:09:17.700> so<00:09:18.149> now<00:09:18.420> I<00:09:18.450> described 00:09:19.070 --> 00:09:19.080 align:start position:0% general test format so now I described 00:09:19.080 --> 00:09:23.000 align:start position:0% general test format so now I described one<00:09:19.500> single<00:09:20.220> test<00:09:20.430> case<00:09:20.730> and<00:09:21.080> then<00:09:22.080> C++ 00:09:23.000 --> 00:09:23.010 align:start position:0% one single test case and then C++ 00:09:23.010 --> 00:09:25.910 align:start position:0% one single test case and then C++ convert<00:09:23.490> this<00:09:23.760> test<00:09:24.120> and<00:09:24.570> executed<00:09:25.200> on<00:09:25.410> every 00:09:25.910 --> 00:09:25.920 align:start position:0% convert this test and executed on every 00:09:25.920 --> 00:09:29.660 align:start position:0% convert this test and executed on every fork<00:09:26.459> and<00:09:27.450> produces<00:09:28.080> a<00:09:28.200> couple<00:09:28.529> of<00:09:28.670> output 00:09:29.660 --> 00:09:29.670 align:start position:0% fork and produces a couple of output 00:09:29.670 --> 00:09:33.380 align:start position:0% fork and produces a couple of output final<00:09:30.029> tests<00:09:30.390> it's<00:09:30.839> actually<00:09:31.550> a<00:09:32.550> result<00:09:33.000> of 00:09:33.380 --> 00:09:33.390 align:start position:0% final tests it's actually a result of 00:09:33.390 --> 00:09:35.480 align:start position:0% final tests it's actually a result of this<00:09:33.540> particular<00:09:33.779> test<00:09:34.290> cases<00:09:34.560> on<00:09:34.920> every<00:09:35.220> fork 00:09:35.480 --> 00:09:35.490 align:start position:0% this particular test cases on every fork 00:09:35.490 --> 00:09:37.910 align:start position:0% this particular test cases on every fork that<00:09:36.000> that<00:09:36.480> is<00:09:36.630> what<00:09:36.810> I<00:09:36.839> call<00:09:37.110> general<00:09:37.350> tests 00:09:37.910 --> 00:09:37.920 align:start position:0% that that is what I call general tests 00:09:37.920 --> 00:09:41.420 align:start position:0% that that is what I call general tests and<00:09:38.339> for<00:09:39.000> the<00:09:39.120> past<00:09:39.330> year<00:09:39.630> I<00:09:39.660> realized<00:09:40.430> state 00:09:41.420 --> 00:09:41.430 align:start position:0% and for the past year I realized state 00:09:41.430 --> 00:09:43.760 align:start position:0% and for the past year I realized state test<00:09:41.730> which<00:09:42.330> is<00:09:42.480> now<00:09:42.600> general<00:09:43.170> every<00:09:43.529> status 00:09:43.760 --> 00:09:43.770 align:start position:0% test which is now general every status 00:09:43.770 --> 00:09:46.160 align:start position:0% test which is now general every status being<00:09:44.279> executed<00:09:44.550> on<00:09:44.880> every<00:09:45.120> fork<00:09:45.510> and<00:09:45.810> in 00:09:46.160 --> 00:09:46.170 align:start position:0% being executed on every fork and in 00:09:46.170 --> 00:09:47.990 align:start position:0% being executed on every fork and in future<00:09:46.410> all<00:09:46.890> of<00:09:47.070> the<00:09:47.160> test<00:09:47.339> cases<00:09:47.610> that<00:09:47.880> we 00:09:47.990 --> 00:09:48.000 align:start position:0% future all of the test cases that we 00:09:48.000 --> 00:09:51.769 align:start position:0% future all of the test cases that we have<00:09:48.209> will<00:09:48.390> be<00:09:48.420> executed<00:09:49.140> I<00:09:50.300> just<00:09:51.300> have<00:09:51.510> to<00:09:51.690> run 00:09:51.769 --> 00:09:51.779 align:start position:0% have will be executed I just have to run 00:09:51.779 --> 00:09:53.600 align:start position:0% have will be executed I just have to run one<00:09:51.990> comment<00:09:52.410> and<00:09:52.529> all<00:09:52.680> the<00:09:52.860> test<00:09:53.040> cases<00:09:53.130> will 00:09:53.600 --> 00:09:53.610 align:start position:0% one comment and all the test cases will 00:09:53.610 --> 00:09:58.100 align:start position:0% one comment and all the test cases will be<00:09:54.500> generated<00:09:55.500> on<00:09:55.650> the<00:09:55.800> recent<00:09:56.100> Forks<00:09:57.110> same 00:09:58.100 --> 00:09:58.110 align:start position:0% be generated on the recent Forks same 00:09:58.110 --> 00:10:00.620 align:start position:0% be generated on the recent Forks same with<00:09:58.320> blockchain<00:09:58.800> tests<00:09:59.100> and<00:09:59.450> next<00:10:00.450> will<00:10:00.600> be 00:10:00.620 --> 00:10:00.630 align:start position:0% with blockchain tests and next will be 00:10:00.630 --> 00:10:10.730 align:start position:0% with blockchain tests and next will be the<00:10:00.810> transaction<00:10:01.410> tests<00:10:08.420> also<00:10:09.709> thanks<00:10:10.709> to 00:10:10.730 --> 00:10:10.740 align:start position:0% the transaction tests also thanks to 00:10:10.740 --> 00:10:14.510 align:start position:0% the transaction tests also thanks to your<00:10:11.040> G<00:10:11.310> he<00:10:11.940> did<00:10:12.240> awesome<00:10:13.520> documentation 00:10:14.510 --> 00:10:14.520 align:start position:0% your G he did awesome documentation 00:10:14.520 --> 00:10:17.030 align:start position:0% your G he did awesome documentation about<00:10:14.670> how<00:10:14.850> he<00:10:15.180> learned<00:10:15.779> because<00:10:16.080> he<00:10:16.440> has 00:10:17.030 --> 00:10:17.040 align:start position:0% about how he learned because he has 00:10:17.040 --> 00:10:20.930 align:start position:0% about how he learned because he has joined<00:10:17.279> us<00:10:17.700> this<00:10:18.420> year<00:10:18.770> he<00:10:19.850> created<00:10:20.850> the 00:10:20.930 --> 00:10:20.940 align:start position:0% joined us this year he created the 00:10:20.940 --> 00:10:24.590 align:start position:0% joined us this year he created the documentation<00:10:21.600> of<00:10:21.720> his<00:10:22.020> steps<00:10:22.320> when<00:10:23.190> he<00:10:23.600> was 00:10:24.590 --> 00:10:24.600 align:start position:0% documentation of his steps when he was 00:10:24.600 --> 00:10:27.579 align:start position:0% documentation of his steps when he was learning<00:10:25.020> the<00:10:25.680> process<00:10:25.920> of<00:10:26.310> test<00:10:26.580> generator 00:10:27.579 --> 00:10:27.589 align:start position:0% learning the process of test generator 00:10:27.589 --> 00:10:30.530 align:start position:0% learning the process of test generator generating<00:10:28.589> the<00:10:28.890> test<00:10:28.920> and<00:10:29.430> then<00:10:29.610> he<00:10:30.270> graded 00:10:30.530 --> 00:10:30.540 align:start position:0% generating the test and then he graded 00:10:30.540 --> 00:10:34.750 align:start position:0% generating the test and then he graded this<00:10:31.279> documentation<00:10:32.630> if<00:10:33.630> you<00:10:33.810> interested<00:10:34.050> in 00:10:34.750 --> 00:10:34.760 align:start position:0% this documentation if you interested in 00:10:34.760 --> 00:10:38.180 align:start position:0% this documentation if you interested in running<00:10:35.760> the<00:10:36.480> test<00:10:36.690> execution<00:10:36.920> yourself<00:10:37.920> or 00:10:38.180 --> 00:10:38.190 align:start position:0% running the test execution yourself or 00:10:38.190 --> 00:10:39.710 align:start position:0% running the test execution yourself or if<00:10:38.370> you<00:10:38.490> are<00:10:38.579> developer<00:10:39.000> and<00:10:39.209> you<00:10:39.360> need<00:10:39.510> to 00:10:39.710 --> 00:10:39.720 align:start position:0% if you are developer and you need to 00:10:39.720 --> 00:10:40.730 align:start position:0% if you are developer and you need to know<00:10:39.839> how<00:10:40.110> this<00:10:40.350> works 00:10:40.730 --> 00:10:40.740 align:start position:0% know how this works 00:10:40.740 --> 00:10:46.160 align:start position:0% know how this works there<00:10:41.700> is<00:10:41.790> no<00:10:41.910> updated<00:10:42.900> documentation<00:10:45.170> you 00:10:46.160 --> 00:10:46.170 align:start position:0% there is no updated documentation you 00:10:46.170 --> 00:10:49.630 align:start position:0% there is no updated documentation you could<00:10:46.380> take<00:10:46.589> the<00:10:46.770> pictures<00:10:47.160> of<00:10:47.370> the<00:10:47.430> links<00:10:47.730> and 00:10:49.630 --> 00:10:49.640 align:start position:0% could take the pictures of the links and 00:10:49.640 --> 00:10:52.940 align:start position:0% could take the pictures of the links and you<00:10:50.640> could<00:10:50.850> see<00:10:51.060> that<00:10:51.270> now<00:10:51.450> our<00:10:51.870> testing<00:10:52.709> team 00:10:52.940 --> 00:10:52.950 align:start position:0% you could see that now our testing team 00:10:52.950 --> 00:10:55.340 align:start position:0% you could see that now our testing team is<00:10:53.160> not<00:10:53.310> a<00:10:53.370> single<00:10:53.790> person<00:10:53.970> we<00:10:54.420> have<00:10:54.660> like<00:10:54.839> lots 00:10:55.340 --> 00:10:55.350 align:start position:0% is not a single person we have like lots 00:10:55.350 --> 00:10:57.380 align:start position:0% is not a single person we have like lots of<00:10:55.500> people<00:10:55.890> joining<00:10:56.160> and<00:10:56.700> most<00:10:57.000> of<00:10:57.180> them 00:10:57.380 --> 00:10:57.390 align:start position:0% of people joining and most of them 00:10:57.390 --> 00:11:01.540 align:start position:0% of people joining and most of them joining<00:10:57.990> us<00:10:58.410> this<00:10:58.980> year 00:11:01.540 --> 00:11:01.550 align:start position:0% 00:11:01.550 --> 00:11:04.819 align:start position:0% so<00:11:02.550> special<00:11:03.449> thanks<00:11:03.839> to<00:11:04.170> all<00:11:04.199> of<00:11:04.290> them<00:11:04.589> working 00:11:04.819 --> 00:11:04.829 align:start position:0% so special thanks to all of them working 00:11:04.829 --> 00:11:10.819 align:start position:0% so special thanks to all of them working together<00:11:05.129> on<00:11:05.699> tests<00:11:07.519> okay<00:11:09.439> we<00:11:10.439> still<00:11:10.680> have 00:11:10.819 --> 00:11:10.829 align:start position:0% together on tests okay we still have 00:11:10.829 --> 00:11:26.880 align:start position:0% together on tests okay we still have time<00:11:10.980> for<00:11:11.040> questions 00:11:26.880 --> 00:11:26.890 align:start position:0% 00:11:26.890 --> 00:11:29.940 align:start position:0% oh<00:11:27.390> yeah<00:11:28.390> not<00:11:28.750> all<00:11:29.080> of<00:11:29.260> the<00:11:29.380> tests<00:11:29.620> are<00:11:29.800> running 00:11:29.940 --> 00:11:29.950 align:start position:0% oh yeah not all of the tests are running 00:11:29.950 --> 00:11:35.730 align:start position:0% oh yeah not all of the tests are running on<00:11:30.160> a<00:11:30.190> -<00:11:30.460> portion<00:11:31.030> they're<00:11:34.050> so<00:11:35.050> general<00:11:35.470> state 00:11:35.730 --> 00:11:35.740 align:start position:0% on a - portion they're so general state 00:11:35.740 --> 00:11:37.980 align:start position:0% on a - portion they're so general state tests<00:11:35.980> are<00:11:36.820> being<00:11:37.120> converted<00:11:37.450> in<00:11:37.900> a 00:11:37.980 --> 00:11:37.990 align:start position:0% tests are being converted in a 00:11:37.990 --> 00:11:40.190 align:start position:0% tests are being converted in a blockchain<00:11:38.230> test<00:11:38.710> this<00:11:39.070> is<00:11:39.250> another<00:11:39.520> update 00:11:40.190 --> 00:11:40.200 align:start position:0% blockchain test this is another update 00:11:40.200 --> 00:11:42.780 align:start position:0% blockchain test this is another update so<00:11:41.200> I<00:11:41.230> just<00:11:41.740> run<00:11:41.950> a<00:11:41.980> common<00:11:42.400> and<00:11:42.580> although 00:11:42.780 --> 00:11:42.790 align:start position:0% so I just run a common and although 00:11:42.790 --> 00:11:44.220 align:start position:0% so I just run a common and although general<00:11:43.330> state<00:11:43.540> has<00:11:43.720> been<00:11:43.900> converted 00:11:44.220 --> 00:11:44.230 align:start position:0% general state has been converted 00:11:44.230 --> 00:11:46.440 align:start position:0% general state has been converted blockchain<00:11:44.770> tests<00:11:45.070> which<00:11:45.340> then<00:11:45.970> will<00:11:46.150> be<00:11:46.300> run 00:11:46.440 --> 00:11:46.450 align:start position:0% blockchain tests which then will be run 00:11:46.450 --> 00:12:00.700 align:start position:0% blockchain tests which then will be run on<00:11:46.480> hive<00:11:51.180> okay<00:11:52.210> thanks<00:11:52.450> Dimitri 00:12:00.700 --> 00:12:00.710 align:start position:0% 00:12:00.710 --> 00:12:08.289 align:start position:0% [Music]