WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:14.419 align:start position:0% [Music] 00:00:14.419 --> 00:00:14.429 align:start position:0% [Music] 00:00:14.429 --> 00:00:17.279 align:start position:0% [Music] so<00:00:15.429> I<00:00:15.460> everyone<00:00:16.090> we're<00:00:16.779> gonna<00:00:16.960> speak<00:00:17.109> about 00:00:17.279 --> 00:00:17.289 align:start position:0% so I everyone we're gonna speak about 00:00:17.289 --> 00:00:20.579 align:start position:0% so I everyone we're gonna speak about random<00:00:17.890> numbers<00:00:18.189> so<00:00:19.089> first<00:00:19.599> a<00:00:19.929> small<00:00:20.230> course 00:00:20.579 --> 00:00:20.589 align:start position:0% random numbers so first a small course 00:00:20.589 --> 00:00:22.950 align:start position:0% random numbers so first a small course about<00:00:20.829> lactose<00:00:21.359> quantum<00:00:22.359> numbers<00:00:22.659> should<00:00:22.839> not 00:00:22.950 --> 00:00:22.960 align:start position:0% about lactose quantum numbers should not 00:00:22.960 --> 00:00:24.720 align:start position:0% about lactose quantum numbers should not be<00:00:23.109> generated<00:00:23.529> with<00:00:23.710> a<00:00:23.739> metal<00:00:24.069> children<00:00:24.369> at 00:00:24.720 --> 00:00:24.730 align:start position:0% be generated with a metal children at 00:00:24.730 --> 00:00:26.779 align:start position:0% be generated with a metal children at random<00:00:25.179> and<00:00:25.449> we've<00:00:26.169> seen<00:00:26.380> too<00:00:26.619> much 00:00:26.779 --> 00:00:26.789 align:start position:0% random and we've seen too much 00:00:26.789 --> 00:00:28.829 align:start position:0% random and we've seen too much application<00:00:27.789> just<00:00:28.119> within<00:00:28.329> the<00:00:28.479> block<00:00:28.630> cache 00:00:28.829 --> 00:00:28.839 align:start position:0% application just within the block cache 00:00:28.839 --> 00:00:30.779 align:start position:0% application just within the block cache or<00:00:29.319> using<00:00:29.829> multiple<00:00:30.130> block<00:00:30.279> cache 00:00:30.779 --> 00:00:30.789 align:start position:0% or using multiple block cache 00:00:30.789 --> 00:00:35.160 align:start position:0% or using multiple block cache why<00:00:31.149> it's<00:00:31.359> not<00:00:31.509> secure<00:00:33.210> when<00:00:34.210> you<00:00:34.750> are<00:00:34.900> on 00:00:35.160 --> 00:00:35.170 align:start position:0% why it's not secure when you are on 00:00:35.170 --> 00:00:36.960 align:start position:0% why it's not secure when you are on classical<00:00:35.590> computing<00:00:36.010> you<00:00:36.580> have<00:00:36.700> your<00:00:36.850> own 00:00:36.960 --> 00:00:36.970 align:start position:0% classical computing you have your own 00:00:36.970 --> 00:00:39.840 align:start position:0% classical computing you have your own computer<00:00:37.180> you<00:00:38.110> can<00:00:38.290> use<00:00:38.470> your<00:00:38.710> time<00:00:38.890> data<00:00:39.670> in 00:00:39.840 --> 00:00:39.850 align:start position:0% computer you can use your time data in 00:00:39.850 --> 00:00:42.570 align:start position:0% computer you can use your time data in your<00:00:39.940> computer<00:00:40.080> most<00:00:41.080> movements<00:00:41.560> to<00:00:42.220> get<00:00:42.400> a 00:00:42.570 --> 00:00:42.580 align:start position:0% your computer most movements to get a 00:00:42.580 --> 00:00:43.200 align:start position:0% your computer most movements to get a random<00:00:42.910> number 00:00:43.200 --> 00:00:43.210 align:start position:0% random number 00:00:43.210 --> 00:00:45.240 align:start position:0% random number I<00:00:43.390> remember<00:00:44.230> when<00:00:44.440> I<00:00:44.470> was<00:00:44.620> creating<00:00:44.800> my 00:00:45.240 --> 00:00:45.250 align:start position:0% I remember when I was creating my 00:00:45.250 --> 00:00:46.380 align:start position:0% I remember when I was creating my 12-inch<00:00:45.640> an<00:00:45.820> address 00:00:46.380 --> 00:00:46.390 align:start position:0% 12-inch an address 00:00:46.390 --> 00:00:48.450 align:start position:0% 12-inch an address they<00:00:47.080> asked<00:00:47.260> me<00:00:47.440> to<00:00:47.560> move<00:00:47.710> them<00:00:47.860> out<00:00:47.980> to<00:00:48.280> type 00:00:48.450 --> 00:00:48.460 align:start position:0% they asked me to move them out to type 00:00:48.460 --> 00:00:50.550 align:start position:0% they asked me to move them out to type random<00:00:48.730> stuff<00:00:48.940> on<00:00:49.000> the<00:00:49.120> keyboard<00:00:49.480> and<00:00:49.750> usually 00:00:50.550 --> 00:00:50.560 align:start position:0% random stuff on the keyboard and usually 00:00:50.560 --> 00:00:53.460 align:start position:0% random stuff on the keyboard and usually entropy<00:00:51.010> but<00:00:51.610> the<00:00:51.700> problem<00:00:52.120> is<00:00:52.480> if<00:00:52.810> you<00:00:52.870> want<00:00:53.200> a 00:00:53.460 --> 00:00:53.470 align:start position:0% entropy but the problem is if you want a 00:00:53.470 --> 00:00:55.770 align:start position:0% entropy but the problem is if you want a random<00:00:53.829> number<00:00:54.130> in<00:00:54.850> a<00:00:55.090> serum<00:00:55.420> which<00:00:55.660> is 00:00:55.770 --> 00:00:55.780 align:start position:0% random number in a serum which is 00:00:55.780 --> 00:00:57.870 align:start position:0% random number in a serum which is basically<00:00:56.050> the<00:00:56.260> world<00:00:56.440> in<00:00:56.620> future<00:00:56.860> you<00:00:57.850> will 00:00:57.870 --> 00:00:57.880 align:start position:0% basically the world in future you will 00:00:57.880 --> 00:01:00.030 align:start position:0% basically the world in future you will each<00:00:58.270> end<00:00:58.750> up<00:00:58.900> into<00:00:59.170> a<00:00:59.410> different<00:00:59.800> phone 00:01:00.030 --> 00:01:00.040 align:start position:0% each end up into a different phone 00:01:00.040 --> 00:01:02.400 align:start position:0% each end up into a different phone locally 00:01:02.400 --> 00:01:02.410 align:start position:0% locally 00:01:02.410 --> 00:01:05.219 align:start position:0% locally why<00:01:03.070> do<00:01:03.130> we<00:01:03.400> need<00:01:03.489> those<00:01:03.760> so<00:01:04.629> the<00:01:04.869> basic<00:01:05.110> use 00:01:05.219 --> 00:01:05.229 align:start position:0% why do we need those so the basic use 00:01:05.229 --> 00:01:09.510 align:start position:0% why do we need those so the basic use case<00:01:05.470> is<00:01:05.829> counting<00:01:06.899> we<00:01:07.899> use<00:01:08.140> improve<00:01:08.499> work<00:01:08.740> we 00:01:09.510 --> 00:01:09.520 align:start position:0% case is counting we use improve work we 00:01:09.520 --> 00:01:11.179 align:start position:0% case is counting we use improve work we need<00:01:09.700> using<00:01:09.969> complex<00:01:10.329> but<00:01:10.479> in<00:01:10.630> systems 00:01:11.179 --> 00:01:11.189 align:start position:0% need using complex but in systems 00:01:11.189 --> 00:01:13.919 align:start position:0% need using complex but in systems probably<00:01:12.189> Stefano's<00:01:12.700> Mossad<00:01:13.090> is<00:01:13.210> in<00:01:13.810> my 00:01:13.919 --> 00:01:13.929 align:start position:0% probably Stefano's Mossad is in my 00:01:13.929 --> 00:01:16.889 align:start position:0% probably Stefano's Mossad is in my opinion<00:01:14.380> the<00:01:15.009> state<00:01:15.909> of<00:01:15.999> the<00:01:16.149> art<00:01:16.329> in<00:01:16.630> terminal 00:01:16.889 --> 00:01:16.899 align:start position:0% opinion the state of the art in terminal 00:01:16.899 --> 00:01:20.279 align:start position:0% opinion the state of the art in terminal but<00:01:17.020> in<00:01:17.139> system<00:01:17.469> we<00:01:18.340> use<00:01:18.759> for<00:01:18.969> doing<00:01:19.060> jewels<00:01:19.479> in 00:01:20.279 --> 00:01:20.289 align:start position:0% but in system we use for doing jewels in 00:01:20.289 --> 00:01:21.359 align:start position:0% but in system we use for doing jewels in the<00:01:20.409> project<00:01:20.679> I'm<00:01:20.770> working<00:01:20.799> on 00:01:21.359 --> 00:01:21.369 align:start position:0% the project I'm working on 00:01:21.369 --> 00:01:25.800 align:start position:0% the project I'm working on that's<00:01:22.299> what<00:01:22.420> we<00:01:22.569> do<00:01:23.130> we<00:01:24.130> need<00:01:24.159> for<00:01:24.549> AI<00:01:24.810> to 00:01:25.800 --> 00:01:25.810 align:start position:0% that's what we do we need for AI to 00:01:25.810 --> 00:01:27.899 align:start position:0% that's what we do we need for AI to visualize<00:01:26.350> machine<00:01:26.679> learning<00:01:26.889> algorithms<00:01:27.429> so 00:01:27.899 --> 00:01:27.909 align:start position:0% visualize machine learning algorithms so 00:01:27.909 --> 00:01:29.489 align:start position:0% visualize machine learning algorithms so imagine<00:01:28.420> you<00:01:28.509> have<00:01:28.539> an<00:01:28.689> errand<00:01:29.049> blockchain 00:01:29.489 --> 00:01:29.499 align:start position:0% imagine you have an errand blockchain 00:01:29.499 --> 00:01:32.789 align:start position:0% imagine you have an errand blockchain with<00:01:30.249> some<00:01:30.670> academic<00:01:31.299> personality<00:01:31.810> if<00:01:32.740> you 00:01:32.789 --> 00:01:32.799 align:start position:0% with some academic personality if you 00:01:32.799 --> 00:01:35.999 align:start position:0% with some academic personality if you were<00:01:32.979> both<00:01:33.189> she<00:01:33.850> fix<00:01:34.630> the<00:01:35.289> initiation<00:01:35.740> number 00:01:35.999 --> 00:01:36.009 align:start position:0% were both she fix the initiation number 00:01:36.009 --> 00:01:38.550 align:start position:0% were both she fix the initiation number you<00:01:36.609> could<00:01:36.759> treat<00:01:36.939> the<00:01:37.060> III<00:01:37.209> into<00:01:38.139> learning 00:01:38.550 --> 00:01:38.560 align:start position:0% you could treat the III into learning 00:01:38.560 --> 00:01:41.789 align:start position:0% you could treat the III into learning valued<00:01:39.100> him<00:01:39.490> bad<00:01:39.819> decisions 00:01:41.789 --> 00:01:41.799 align:start position:0% valued him bad decisions 00:01:41.799 --> 00:01:45.209 align:start position:0% valued him bad decisions the<00:01:42.429> first<00:01:42.609> method<00:01:42.729> which<00:01:42.969> we<00:01:43.090> use<00:01:43.329> is<00:01:44.219> trusted 00:01:45.209 --> 00:01:45.219 align:start position:0% the first method which we use is trusted 00:01:45.219 --> 00:01:49.529 align:start position:0% the first method which we use is trusted path<00:01:45.389> so<00:01:46.389> you<00:01:46.810> have<00:01:47.020> some<00:01:47.229> mr.<00:01:47.799> meehan<00:01:48.539> where 00:01:49.529 --> 00:01:49.539 align:start position:0% path so you have some mr. meehan where 00:01:49.539 --> 00:01:51.389 align:start position:0% path so you have some mr. meehan where you<00:01:49.630> could<00:01:49.810> plug<00:01:50.200> in<00:01:50.289> a<00:01:50.350> wrapper<00:01:50.499> on<00:01:50.709> it<00:01:50.829> you 00:01:51.389 --> 00:01:51.399 align:start position:0% you could plug in a wrapper on it you 00:01:51.399 --> 00:01:53.489 align:start position:0% you could plug in a wrapper on it you can<00:01:51.579> directly<00:01:51.909> call<00:01:52.090> or<00:01:52.240> a<00:01:52.270> kite<00:01:52.539> but<00:01:53.380> the 00:01:53.489 --> 00:01:53.499 align:start position:0% can directly call or a kite but the 00:01:53.499 --> 00:01:55.919 align:start position:0% can directly call or a kite but the problem<00:01:53.799> isn't<00:01:53.979> alive<00:01:54.880> every<00:01:55.569> single<00:01:55.840> point 00:01:55.919 --> 00:01:55.929 align:start position:0% problem isn't alive every single point 00:01:55.929 --> 00:01:59.039 align:start position:0% problem isn't alive every single point of<00:01:56.079> failure<00:01:56.200> and<00:01:56.590> in<00:01:57.159> case<00:01:57.399> trusted<00:01:58.179> party<00:01:58.569> is 00:01:59.039 --> 00:01:59.049 align:start position:0% of failure and in case trusted party is 00:01:59.049 --> 00:02:02.209 align:start position:0% of failure and in case trusted party is cheating<00:01:59.469> you<00:01:59.679> having<00:02:00.009> a<00:02:00.099> way<00:02:00.219> to<00:02:00.249> detect<00:02:00.579> it 00:02:02.209 --> 00:02:02.219 align:start position:0% cheating you having a way to detect it 00:02:02.219 --> 00:02:05.219 align:start position:0% cheating you having a way to detect it within<00:02:03.219> a<00:02:03.369> lot<00:02:03.520> of<00:02:03.670> the<00:02:03.819> person<00:02:04.779> using<00:02:04.990> block 00:02:05.219 --> 00:02:05.229 align:start position:0% within a lot of the person using block 00:02:05.229 --> 00:02:09.359 align:start position:0% within a lot of the person using block hash<00:02:05.969> but<00:02:06.969> that<00:02:07.060> does<00:02:07.299> not<00:02:07.479> work<00:02:07.929> so<00:02:08.709> let's<00:02:09.280> go 00:02:09.359 --> 00:02:09.369 align:start position:0% hash but that does not work so let's go 00:02:09.369 --> 00:02:12.180 align:start position:0% hash but that does not work so let's go back<00:02:09.399> to<00:02:09.580> basic<00:02:10.390> walk 00:02:12.180 --> 00:02:12.190 align:start position:0% back to basic walk 00:02:12.190 --> 00:02:14.070 align:start position:0% back to basic walk the<00:02:12.310> graphic<00:02:12.610> function<00:02:12.970> if<00:02:13.660> you<00:02:13.720> want<00:02:13.900> to 00:02:14.070 --> 00:02:14.080 align:start position:0% the graphic function if you want to 00:02:14.080 --> 00:02:16.950 align:start position:0% the graphic function if you want to compute<00:02:14.320> H<00:02:14.590> of<00:02:14.800> X<00:02:15.040> it's<00:02:15.430> easy<00:02:15.700> but<00:02:16.570> if<00:02:16.660> you<00:02:16.810> want 00:02:16.950 --> 00:02:16.960 align:start position:0% compute H of X it's easy but if you want 00:02:16.960 --> 00:02:23.370 align:start position:0% compute H of X it's easy but if you want to<00:02:17.050> compute<00:02:17.350> X<00:02:17.710> that<00:02:18.370> X<00:02:18.520> of<00:02:18.970> X<00:02:19.330> is<00:02:19.870> y<00:02:22.050> so<00:02:23.050> into<00:02:23.320> a 00:02:23.370 --> 00:02:23.380 align:start position:0% to compute X that X of X is y so into a 00:02:23.380 --> 00:02:27.360 align:start position:0% to compute X that X of X is y so into a wok<00:02:23.650> basically<00:02:24.570> either<00:02:25.740> you<00:02:26.740> start<00:02:27.190> with<00:02:27.340> a 00:02:27.360 --> 00:02:27.370 align:start position:0% wok basically either you start with a 00:02:27.370 --> 00:02:31.140 align:start position:0% wok basically either you start with a new<00:02:27.520> ones<00:02:27.700> like<00:02:28.030> zero<00:02:28.450> and<00:02:29.440> you<00:02:29.950> a<00:02:30.340> and<00:02:30.550> it 00:02:31.140 --> 00:02:31.150 align:start position:0% new ones like zero and you a and it 00:02:31.150 --> 00:02:33.150 align:start position:0% new ones like zero and you a and it stores<00:02:31.570> and<00:02:31.690> target<00:02:32.050> you<00:02:32.410> for<00:02:32.560> the<00:02:32.650> block<00:02:32.800> and 00:02:33.150 --> 00:02:33.160 align:start position:0% stores and target you for the block and 00:02:33.160 --> 00:02:35.310 align:start position:0% stores and target you for the block and if<00:02:33.520> not<00:02:33.670> you<00:02:34.060> increment<00:02:34.270> announced<00:02:34.660> with<00:02:34.870> n 00:02:35.310 --> 00:02:35.320 align:start position:0% if not you increment announced with n 00:02:35.320 --> 00:02:37.620 align:start position:0% if not you increment announced with n equal<00:02:35.590> 1<00:02:35.620> 2<00:02:36.070> 3<00:02:36.250> up<00:02:36.520> to<00:02:36.670> the<00:02:36.760> point<00:02:36.970> you<00:02:37.180> find<00:02:37.330> or 00:02:37.620 --> 00:02:37.630 align:start position:0% equal 1 2 3 up to the point you find or 00:02:37.630 --> 00:02:40.320 align:start position:0% equal 1 2 3 up to the point you find or call<00:02:37.840> someone<00:02:38.110> happy<00:02:38.680> so<00:02:39.430> we<00:02:39.700> could<00:02:39.850> say<00:02:39.940> ok<00:02:40.210> at 00:02:40.320 --> 00:02:40.330 align:start position:0% call someone happy so we could say ok at 00:02:40.330 --> 00:02:43.470 align:start position:0% call someone happy so we could say ok at the<00:02:40.510> end<00:02:40.630> we<00:02:40.780> have<00:02:40.900> ash<00:02:41.140> which<00:02:41.440> is<00:02:41.470> random<00:02:42.480> no 00:02:43.470 --> 00:02:43.480 align:start position:0% the end we have ash which is random no 00:02:43.480 --> 00:02:46.530 align:start position:0% the end we have ash which is random no because<00:02:44.140> when<00:02:44.710> you<00:02:44.830> get<00:02:45.040> the<00:02:45.340> final<00:02:45.640> block<00:02:45.760> you 00:02:46.530 --> 00:02:46.540 align:start position:0% because when you get the final block you 00:02:46.540 --> 00:02:49.260 align:start position:0% because when you get the final block you can<00:02:46.660> choose<00:02:46.840> not<00:02:47.260> to<00:02:47.440> publish<00:02:47.710> it<00:02:47.860> and<00:02:48.340> even 00:02:49.260 --> 00:02:49.270 align:start position:0% can choose not to publish it and even 00:02:49.270 --> 00:02:51.930 align:start position:0% can choose not to publish it and even worse<00:02:49.450> with<00:02:50.170> smart<00:02:50.440> contract<00:02:50.830> you<00:02:51.460> can<00:02:51.640> bribe 00:02:51.930 --> 00:02:51.940 align:start position:0% worse with smart contract you can bribe 00:02:51.940 --> 00:02:54.270 align:start position:0% worse with smart contract you can bribe the<00:02:52.000> miner<00:02:52.330> trust<00:02:52.930> Leslie<00:02:53.260> into<00:02:54.100> not 00:02:54.270 --> 00:02:54.280 align:start position:0% the miner trust Leslie into not 00:02:54.280 --> 00:02:57.630 align:start position:0% the miner trust Leslie into not publishing<00:02:54.700> those<00:02:54.820> blocks<00:02:55.090> and<00:02:56.400> you<00:02:57.400> don't 00:02:57.630 --> 00:02:57.640 align:start position:0% publishing those blocks and you don't 00:02:57.640 --> 00:02:59.550 align:start position:0% publishing those blocks and you don't even<00:02:57.820> lose<00:02:58.240> the<00:02:58.450> world<00:02:58.660> box<00:02:58.870> well<00:02:59.110> because<00:02:59.470> you 00:02:59.550 --> 00:02:59.560 align:start position:0% even lose the world box well because you 00:02:59.560 --> 00:03:03.150 align:start position:0% even lose the world box well because you published<00:02:59.860> it<00:02:59.980> as<00:03:00.160> an<00:03:00.310> uncle<00:03:00.400> so<00:03:01.830> ok<00:03:02.860> only<00:03:03.070> the 00:03:03.150 --> 00:03:03.160 align:start position:0% published it as an uncle so ok only the 00:03:03.160 --> 00:03:05.700 align:start position:0% published it as an uncle so ok only the miner<00:03:03.340> can<00:03:03.520> do<00:03:03.640> this<00:03:03.760> attack<00:03:04.060> and<00:03:04.410> the<00:03:05.410> effect 00:03:05.700 --> 00:03:05.710 align:start position:0% miner can do this attack and the effect 00:03:05.710 --> 00:03:08.850 align:start position:0% miner can do this attack and the effect is<00:03:06.280> just<00:03:06.700> what<00:03:07.420> just<00:03:07.720> we're<00:03:08.440> rolling<00:03:08.740> the 00:03:08.850 --> 00:03:08.860 align:start position:0% is just what just we're rolling the 00:03:08.860 --> 00:03:10.980 align:start position:0% is just what just we're rolling the number<00:03:09.100> so<00:03:09.730> it<00:03:09.850> does<00:03:09.970> not<00:03:10.060> allow<00:03:10.300> you<00:03:10.330> to<00:03:10.540> fix 00:03:10.980 --> 00:03:10.990 align:start position:0% number so it does not allow you to fix 00:03:10.990 --> 00:03:12.750 align:start position:0% number so it does not allow you to fix it<00:03:11.140> to<00:03:11.230> a<00:03:11.260> particular<00:03:11.500> value<00:03:11.650> but<00:03:12.520> it<00:03:12.640> tells 00:03:12.750 --> 00:03:12.760 align:start position:0% it to a particular value but it tells 00:03:12.760 --> 00:03:16.680 align:start position:0% it to a particular value but it tells you<00:03:13.000> to<00:03:13.240> pay<00:03:13.900> a<00:03:13.930> small<00:03:14.260> cost<00:03:14.700> when<00:03:15.700> you<00:03:16.510> want 00:03:16.680 --> 00:03:16.690 align:start position:0% you to pay a small cost when you want 00:03:16.690 --> 00:03:18.680 align:start position:0% you to pay a small cost when you want through<00:03:16.870> some<00:03:17.080> so<00:03:17.200> on<00:03:17.440> and<00:03:17.680> get<00:03:17.980> a<00:03:18.010> new<00:03:18.160> one 00:03:18.680 --> 00:03:18.690 align:start position:0% through some so on and get a new one 00:03:18.690 --> 00:03:20.910 align:start position:0% through some so on and get a new one I've<00:03:19.690> seen<00:03:19.870> applications<00:03:19.990> we<00:03:20.650> are<00:03:20.740> saying 00:03:20.910 --> 00:03:20.920 align:start position:0% I've seen applications we are saying 00:03:20.920 --> 00:03:21.720 align:start position:0% I've seen applications we are saying okay 00:03:21.720 --> 00:03:21.730 align:start position:0% okay 00:03:21.730 --> 00:03:24.420 align:start position:0% okay the<00:03:22.480> cost<00:03:22.870> is<00:03:23.140> is<00:03:23.500> what<00:03:23.830> I<00:03:23.860> have<00:03:24.070> a<00:03:24.100> stake<00:03:24.400> in 00:03:24.420 --> 00:03:24.430 align:start position:0% the cost is is what I have a stake in 00:03:24.430 --> 00:03:26.790 align:start position:0% the cost is is what I have a stake in each<00:03:24.730> block<00:03:24.910> in<00:03:25.090> my<00:03:25.150> application<00:03:25.300> so<00:03:26.290> I<00:03:26.620> can 00:03:26.790 --> 00:03:26.800 align:start position:0% each block in my application so I can 00:03:26.800 --> 00:03:31.410 align:start position:0% each block in my application so I can rely<00:03:26.980> on<00:03:27.010> the<00:03:27.600> block<00:03:28.600> cash<00:03:28.780> to<00:03:29.290> get<00:03:30.180> but<00:03:31.180> no 00:03:31.410 --> 00:03:31.420 align:start position:0% rely on the block cash to get but no 00:03:31.420 --> 00:03:33.780 align:start position:0% rely on the block cash to get but no because<00:03:32.080> the<00:03:32.920> blockage<00:03:33.220> is<00:03:33.250> the<00:03:33.459> same<00:03:33.610> for 00:03:33.780 --> 00:03:33.790 align:start position:0% because the blockage is the same for 00:03:33.790 --> 00:03:35.940 align:start position:0% because the blockage is the same for everyone<00:03:34.030> so<00:03:34.630> perhaps<00:03:34.900> if<00:03:35.140> in<00:03:35.230> my<00:03:35.380> application 00:03:35.940 --> 00:03:35.950 align:start position:0% everyone so perhaps if in my application 00:03:35.950 --> 00:03:37.890 align:start position:0% everyone so perhaps if in my application it's<00:03:36.160> not<00:03:36.340> water<00:03:36.490> attacking<00:03:37.030> my<00:03:37.720> name 00:03:37.890 --> 00:03:37.900 align:start position:0% it's not water attacking my name 00:03:37.900 --> 00:03:39.870 align:start position:0% it's not water attacking my name replication<00:03:38.470> the<00:03:38.860> attacking<00:03:39.220> a<00:03:39.370> new 00:03:39.870 --> 00:03:39.880 align:start position:0% replication the attacking a new 00:03:39.880 --> 00:03:41.670 align:start position:0% replication the attacking a new application<00:03:40.180> that<00:03:40.480> was<00:03:40.600> attacking<00:03:40.840> but 00:03:41.670 --> 00:03:41.680 align:start position:0% application that was attacking but 00:03:41.680 --> 00:03:43.710 align:start position:0% application that was attacking but perhaps<00:03:41.890> you<00:03:42.070> can<00:03:42.160> do<00:03:42.280> an<00:03:42.370> attack<00:03:42.610> on<00:03:42.880> all<00:03:43.270> the 00:03:43.710 --> 00:03:43.720 align:start position:0% perhaps you can do an attack on all the 00:03:43.720 --> 00:03:45.390 align:start position:0% perhaps you can do an attack on all the suite<00:03:43.900> application<00:03:44.320> at<00:03:44.410> the<00:03:44.470> same<00:03:44.590> time<00:03:44.800> and 00:03:45.390 --> 00:03:45.400 align:start position:0% suite application at the same time and 00:03:45.400 --> 00:03:47.520 align:start position:0% suite application at the same time and in<00:03:45.670> this<00:03:45.790> case<00:03:46.030> you<00:03:46.480> may<00:03:46.600> be<00:03:46.750> more<00:03:46.959> than<00:03:47.410> the 00:03:47.520 --> 00:03:47.530 align:start position:0% in this case you may be more than the 00:03:47.530 --> 00:03:52.470 align:start position:0% in this case you may be more than the attack<00:03:49.530> 1<00:03:50.530> meter<00:03:50.800> which<00:03:51.010> is<00:03:51.190> really<00:03:51.640> useful 00:03:52.470 --> 00:03:52.480 align:start position:0% attack 1 meter which is really useful 00:03:52.480 --> 00:03:54.900 align:start position:0% attack 1 meter which is really useful when<00:03:52.690> you<00:03:52.989> don't<00:03:53.020> have<00:03:53.320> rate<00:03:53.500> of<00:03:53.620> parties<00:03:54.100> is 00:03:54.900 --> 00:03:54.910 align:start position:0% when you don't have rate of parties is 00:03:54.910 --> 00:03:57.630 align:start position:0% when you don't have rate of parties is committee<00:03:55.300> machines<00:03:55.680> so<00:03:56.680> the<00:03:57.040> IDE<00:03:57.310> you 00:03:57.630 --> 00:03:57.640 align:start position:0% committee machines so the IDE you 00:03:57.640 --> 00:04:00.960 align:start position:0% committee machines so the IDE you generate<00:03:58.060> a<00:03:58.090> number<00:03:58.270> locally<00:03:59.190> you<00:04:00.190> publish<00:04:00.670> it 00:04:00.960 --> 00:04:00.970 align:start position:0% generate a number locally you publish it 00:04:00.970 --> 00:04:04.080 align:start position:0% generate a number locally you publish it ash<00:04:01.500> you<00:04:02.500> had<00:04:02.590> tons<00:04:03.310> of<00:04:03.400> party<00:04:03.700> doing<00:04:03.820> that 00:04:04.080 --> 00:04:04.090 align:start position:0% ash you had tons of party doing that 00:04:04.090 --> 00:04:07.620 align:start position:0% ash you had tons of party doing that they<00:04:04.750> pay<00:04:04.900> a<00:04:04.930> deposit<00:04:05.110> and<00:04:06.180> in<00:04:07.180> a<00:04:07.239> second<00:04:07.480> phase 00:04:07.620 --> 00:04:07.630 align:start position:0% they pay a deposit and in a second phase 00:04:07.630 --> 00:04:11.190 align:start position:0% they pay a deposit and in a second phase the<00:04:08.230> Reavers<00:04:08.530> numbers<00:04:09.450> of<00:04:10.450> course<00:04:10.810> you<00:04:10.900> verify 00:04:11.190 --> 00:04:11.200 align:start position:0% the Reavers numbers of course you verify 00:04:11.200 --> 00:04:13.650 align:start position:0% the Reavers numbers of course you verify that<00:04:11.230> the<00:04:11.470> ash<00:04:11.590> corresponds<00:04:12.010> and<00:04:12.330> the<00:04:13.330> result 00:04:13.650 --> 00:04:13.660 align:start position:0% that the ash corresponds and the result 00:04:13.660 --> 00:04:18.629 align:start position:0% that the ash corresponds and the result is<00:04:13.930> the<00:04:14.380> extra<00:04:14.770> of<00:04:14.980> all<00:04:15.970> random<00:04:16.299> numbers<00:04:16.750> and 00:04:18.629 --> 00:04:18.639 align:start position:0% is the extra of all random numbers and 00:04:18.639 --> 00:04:20.789 align:start position:0% is the extra of all random numbers and interesting<00:04:19.120> property<00:04:19.509> of<00:04:19.539> Excel<00:04:20.079> if<00:04:20.560> you 00:04:20.789 --> 00:04:20.799 align:start position:0% interesting property of Excel if you 00:04:20.799 --> 00:04:22.830 align:start position:0% interesting property of Excel if you excel<00:04:21.189> something<00:04:21.489> went<00:04:21.669> down<00:04:21.699> with<00:04:22.030> whatever 00:04:22.830 --> 00:04:22.840 align:start position:0% excel something went down with whatever 00:04:22.840 --> 00:04:25.290 align:start position:0% excel something went down with whatever is<00:04:23.560> always<00:04:23.949> wonderful<00:04:24.159> so<00:04:24.819> you<00:04:24.879> just<00:04:25.120> need<00:04:25.240> to 00:04:25.290 --> 00:04:25.300 align:start position:0% is always wonderful so you just need to 00:04:25.300 --> 00:04:27.659 align:start position:0% is always wonderful so you just need to have<00:04:25.449> at<00:04:25.629> one<00:04:26.020> party<00:04:26.469> inputting<00:04:27.249> a<00:04:27.400> random 00:04:27.659 --> 00:04:27.669 align:start position:0% have at one party inputting a random 00:04:27.669 --> 00:04:29.149 align:start position:0% have at one party inputting a random number 00:04:29.149 --> 00:04:29.159 align:start position:0% number 00:04:29.159 --> 00:04:32.309 align:start position:0% number the<00:04:30.159> problem<00:04:30.520> is<00:04:30.879> that<00:04:31.060> parties<00:04:31.509> can<00:04:31.840> choose 00:04:32.309 --> 00:04:32.319 align:start position:0% the problem is that parties can choose 00:04:32.319 --> 00:04:34.320 align:start position:0% the problem is that parties can choose not<00:04:32.499> to<00:04:32.620> reveal<00:04:32.770> and<00:04:33.430> if<00:04:33.849> you<00:04:33.939> party<00:04:34.180> does<00:04:34.300> not 00:04:34.320 --> 00:04:34.330 align:start position:0% not to reveal and if you party does not 00:04:34.330 --> 00:04:38.640 align:start position:0% not to reveal and if you party does not reveal<00:04:34.659> the<00:04:35.319> generation<00:04:35.800> is<00:04:36.129> stopped<00:04:37.439> so<00:04:38.439> yeah 00:04:38.640 --> 00:04:38.650 align:start position:0% reveal the generation is stopped so yeah 00:04:38.650 --> 00:04:40.739 align:start position:0% reveal the generation is stopped so yeah you<00:04:38.860> pull<00:04:39.039> the<00:04:39.219> Misuari<00:04:39.879> deposit<00:04:40.360> of<00:04:40.599> the 00:04:40.739 --> 00:04:40.749 align:start position:0% you pull the Misuari deposit of the 00:04:40.749 --> 00:04:44.760 align:start position:0% you pull the Misuari deposit of the party<00:04:40.990> not<00:04:41.110> revealing<00:04:41.939> and<00:04:42.939> in<00:04:43.539> for<00:04:44.349> example<00:04:44.650> I 00:04:44.760 --> 00:04:44.770 align:start position:0% party not revealing and in for example I 00:04:44.770 --> 00:04:47.219 align:start position:0% party not revealing and in for example I want<00:04:44.949> to<00:04:45.009> flip<00:04:45.699> a<00:04:45.789> coin<00:04:45.909> with<00:04:46.120> you<00:04:46.270> that's<00:04:47.020> a 00:04:47.219 --> 00:04:47.229 align:start position:0% want to flip a coin with you that's a 00:04:47.229 --> 00:04:49.170 align:start position:0% want to flip a coin with you that's a really<00:04:47.439> good<00:04:47.529> method<00:04:47.710> because<00:04:48.610> it's<00:04:48.789> only<00:04:48.969> two 00:04:49.170 --> 00:04:49.180 align:start position:0% really good method because it's only two 00:04:49.180 --> 00:04:52.140 align:start position:0% really good method because it's only two of<00:04:49.300> us<00:04:49.529> we<00:04:50.529> fix<00:04:50.740> the<00:04:50.860> coin<00:04:51.069> and<00:04:51.400> if<00:04:51.669> I<00:04:51.759> want<00:04:52.000> to 00:04:52.140 --> 00:04:52.150 align:start position:0% of us we fix the coin and if I want to 00:04:52.150 --> 00:04:54.480 align:start position:0% of us we fix the coin and if I want to solve<00:04:52.569> the<00:04:52.689> flip<00:04:52.900> I<00:04:53.469> get<00:04:53.979> timed<00:04:54.159> up<00:04:54.310> by 00:04:54.480 --> 00:04:54.490 align:start position:0% solve the flip I get timed up by 00:04:54.490 --> 00:04:57.149 align:start position:0% solve the flip I get timed up by dribbling<00:04:54.909> and<00:04:55.240> I<00:04:55.870> was<00:04:56.080> deposited<00:04:56.620> and<00:04:56.830> we 00:04:57.149 --> 00:04:57.159 align:start position:0% dribbling and I was deposited and we 00:04:57.159 --> 00:04:58.709 align:start position:0% dribbling and I was deposited and we assume<00:04:57.400> that<00:04:57.460> you<00:04:57.639> want<00:04:57.819> to<00:04:57.909> flip<00:04:58.090> so<00:04:58.569> that 00:04:58.709 --> 00:04:58.719 align:start position:0% assume that you want to flip so that 00:04:58.719 --> 00:05:01.170 align:start position:0% assume that you want to flip so that works<00:04:58.960> very<00:04:59.110> well<00:04:59.199> but<00:05:00.009> now<00:05:00.279> imagine<00:05:00.699> you<00:05:01.150> have 00:05:01.170 --> 00:05:01.180 align:start position:0% works very well but now imagine you have 00:05:01.180 --> 00:05:04.019 align:start position:0% works very well but now imagine you have one<00:05:01.900> thousand<00:05:02.469> users<00:05:02.680> which<00:05:03.340> are<00:05:03.520> relying<00:05:03.939> on 00:05:04.019 --> 00:05:04.029 align:start position:0% one thousand users which are relying on 00:05:04.029 --> 00:05:06.320 align:start position:0% one thousand users which are relying on the<00:05:04.180> same<00:05:04.330> number<00:05:04.599> and<00:05:04.960> you<00:05:05.379> just<00:05:05.529> have<00:05:05.680> one 00:05:06.320 --> 00:05:06.330 align:start position:0% the same number and you just have one 00:05:06.330 --> 00:05:09.629 align:start position:0% the same number and you just have one not<00:05:07.330> revealing<00:05:07.689> to<00:05:08.080> prevent<00:05:08.379> generation<00:05:08.860> so 00:05:09.629 --> 00:05:09.639 align:start position:0% not revealing to prevent generation so 00:05:09.639 --> 00:05:12.240 align:start position:0% not revealing to prevent generation so you<00:05:10.120> will<00:05:10.270> need<00:05:10.419> each<00:05:10.689> party<00:05:11.229> twelve<00:05:12.189> you 00:05:12.240 --> 00:05:12.250 align:start position:0% you will need each party twelve you 00:05:12.250 --> 00:05:15.240 align:start position:0% you will need each party twelve you deposit<00:05:12.900> equal<00:05:13.900> to<00:05:14.110> what<00:05:14.289> at<00:05:14.439> stake<00:05:14.680> for<00:05:14.889> all 00:05:15.240 --> 00:05:15.250 align:start position:0% deposit equal to what at stake for all 00:05:15.250 --> 00:05:18.779 align:start position:0% deposit equal to what at stake for all the<00:05:15.430> others<00:05:15.699> so<00:05:16.800> this<00:05:17.800> scale<00:05:18.039> quadratically 00:05:18.779 --> 00:05:18.789 align:start position:0% the others so this scale quadratically 00:05:18.789 --> 00:05:22.559 align:start position:0% the others so this scale quadratically to<00:05:19.270> the<00:05:19.389> number<00:05:19.629> of<00:05:19.719> policies<00:05:20.699> so<00:05:21.699> it<00:05:22.060> made<00:05:22.330> me 00:05:22.559 --> 00:05:22.569 align:start position:0% to the number of policies so it made me 00:05:22.569 --> 00:05:27.059 align:start position:0% to the number of policies so it made me practice<00:05:22.870> okay<00:05:23.680> is<00:05:24.009> playing<00:05:24.250> poker<00:05:25.439> but<00:05:26.439> for 00:05:27.059 --> 00:05:27.069 align:start position:0% practice okay is playing poker but for 00:05:27.069 --> 00:05:31.409 align:start position:0% practice okay is playing poker but for other<00:05:27.219> person<00:05:27.669> it<00:05:28.180> won't<00:05:28.389> work<00:05:30.120> then<00:05:31.120> you<00:05:31.270> have 00:05:31.409 --> 00:05:31.419 align:start position:0% other person it won't work then you have 00:05:31.419 --> 00:05:34.260 align:start position:0% other person it won't work then you have special<00:05:31.659> signatures<00:05:32.279> so<00:05:33.279> special<00:05:33.849> signatures 00:05:34.260 --> 00:05:34.270 align:start position:0% special signatures so special signatures 00:05:34.270 --> 00:05:38.790 align:start position:0% special signatures so special signatures is<00:05:34.599> a<00:05:35.560> scenario<00:05:36.479> which<00:05:37.479> is<00:05:37.719> where<00:05:38.259> a<00:05:38.500> lot<00:05:38.770> of 00:05:38.790 --> 00:05:38.800 align:start position:0% is a scenario which is where a lot of 00:05:38.800 --> 00:05:42.889 align:start position:0% is a scenario which is where a lot of parties<00:05:39.279> get<00:05:40.029> part<00:05:40.449> of<00:05:40.930> the<00:05:41.110> key<00:05:41.289> and<00:05:41.529> design 00:05:42.889 --> 00:05:42.899 align:start position:0% parties get part of the key and design 00:05:42.899 --> 00:05:45.869 align:start position:0% parties get part of the key and design part<00:05:43.899> snatcher<00:05:44.139> and<00:05:44.469> if<00:05:45.279> you<00:05:45.370> get<00:05:45.520> at<00:05:45.699> least 00:05:45.869 --> 00:05:45.879 align:start position:0% part snatcher and if you get at least 00:05:45.879 --> 00:05:48.329 align:start position:0% part snatcher and if you get at least the<00:05:46.719> threshold<00:05:47.110> of<00:05:47.229> passive<00:05:47.560> nature<00:05:47.740> you 00:05:48.329 --> 00:05:48.339 align:start position:0% the threshold of passive nature you 00:05:48.339 --> 00:05:50.929 align:start position:0% the threshold of passive nature you combine<00:05:48.699> them<00:05:48.969> and<00:05:49.210> you<00:05:49.750> get<00:05:50.020> a<00:05:50.080> signature 00:05:50.929 --> 00:05:50.939 align:start position:0% combine them and you get a signature 00:05:50.939 --> 00:05:53.579 align:start position:0% combine them and you get a signature one<00:05:51.939> interesting<00:05:52.240> property<00:05:52.509> of<00:05:53.050> the<00:05:53.259> Senate 00:05:53.579 --> 00:05:53.589 align:start position:0% one interesting property of the Senate 00:05:53.589 --> 00:05:56.639 align:start position:0% one interesting property of the Senate regime<00:05:53.889> is<00:05:54.669> that<00:05:55.000> no<00:05:55.750> matter<00:05:55.899> which<00:05:56.199> party<00:05:56.409> are 00:05:56.639 --> 00:05:56.649 align:start position:0% regime is that no matter which party are 00:05:56.649 --> 00:05:59.939 align:start position:0% regime is that no matter which party are signing<00:05:57.069> as<00:05:57.219> long<00:05:58.029> as<00:05:58.419> we<00:05:58.599> get<00:05:58.719> a<00:05:58.779> threshold<00:05:59.080> we 00:05:59.939 --> 00:05:59.949 align:start position:0% signing as long as we get a threshold we 00:05:59.949 --> 00:06:01.589 align:start position:0% signing as long as we get a threshold we get<00:06:00.099> the<00:06:00.159> same<00:06:00.310> signature<00:06:00.580> so<00:06:01.029> if<00:06:01.120> it's<00:06:01.240> a<00:06:01.360> Oba 00:06:01.589 --> 00:06:01.599 align:start position:0% get the same signature so if it's a Oba 00:06:01.599 --> 00:06:05.159 align:start position:0% get the same signature so if it's a Oba signing<00:06:01.930> or<00:06:02.169> DLC<00:06:02.800> or<00:06:03.180> no<00:06:04.180> matter<00:06:04.300> what<00:06:04.539> we 00:06:05.159 --> 00:06:05.169 align:start position:0% signing or DLC or no matter what we 00:06:05.169 --> 00:06:08.510 align:start position:0% signing or DLC or no matter what we already<00:06:05.349> get<00:06:05.560> this<00:06:05.710> is<00:06:05.860> the<00:06:05.979> same<00:06:06.129> signature 00:06:08.510 --> 00:06:08.520 align:start position:0% 00:06:08.520 --> 00:06:12.480 align:start position:0% so<00:06:09.520> that's<00:06:10.509> really<00:06:10.689> good<00:06:10.930> if<00:06:11.589> you<00:06:11.860> are<00:06:11.919> in<00:06:12.250> the 00:06:12.480 --> 00:06:12.490 align:start position:0% so that's really good if you are in the 00:06:12.490 --> 00:06:16.079 align:start position:0% so that's really good if you are in the honest<00:06:12.909> majority<00:06:13.389> model<00:06:14.789> because<00:06:15.789> in<00:06:15.939> this 00:06:16.079 --> 00:06:16.089 align:start position:0% honest majority model because in this 00:06:16.089 --> 00:06:19.829 align:start position:0% honest majority model because in this case<00:06:16.300> I<00:06:17.639> thought<00:06:18.639> about<00:06:18.909> you<00:06:19.149> with<00:06:19.360> all<00:06:19.509> and 00:06:19.829 --> 00:06:19.839 align:start position:0% case I thought about you with all and 00:06:19.839 --> 00:06:22.499 align:start position:0% case I thought about you with all and everything<00:06:20.289> goes<00:06:20.409> right<00:06:20.620> but<00:06:21.610> the<00:06:21.699> problem<00:06:22.120> is 00:06:22.499 --> 00:06:22.509 align:start position:0% everything goes right but the problem is 00:06:22.509 --> 00:06:26.399 align:start position:0% everything goes right but the problem is if<00:06:23.469> you<00:06:23.529> can<00:06:24.069> get<00:06:24.219> attack<00:06:24.759> a<00:06:24.789> 50<00:06:25.180> percent<00:06:25.539> with 00:06:26.399 --> 00:06:26.409 align:start position:0% if you can get attack a 50 percent with 00:06:26.409 --> 00:06:29.209 align:start position:0% if you can get attack a 50 percent with party<00:06:26.830> proposing<00:06:27.580> to<00:06:27.699> revealed<00:06:28.000> a<00:06:28.180> design<00:06:28.509> or 00:06:29.209 --> 00:06:29.219 align:start position:0% party proposing to revealed a design or 00:06:29.219 --> 00:06:30.370 align:start position:0% party proposing to revealed a design or you 00:06:30.370 --> 00:06:30.380 align:start position:0% you 00:06:30.380 --> 00:06:34.420 align:start position:0% you walls<00:06:30.640> with<00:06:31.640> parties<00:06:32.180> we<00:06:32.960> will<00:06:33.110> collude<00:06:33.590> to 00:06:34.420 --> 00:06:34.430 align:start position:0% walls with parties we will collude to 00:06:34.430 --> 00:06:36.880 align:start position:0% walls with parties we will collude to get<00:06:34.580> to<00:06:34.700> know<00:06:34.850> the<00:06:35.060> random<00:06:35.330> number<00:06:35.570> and<00:06:35.890> they 00:06:36.880 --> 00:06:36.890 align:start position:0% get to know the random number and they 00:06:36.890 --> 00:06:41.400 align:start position:0% get to know the random number and they can<00:06:36.920> sum<00:06:37.250> sorry<00:06:37.540> by<00:06:38.540> making<00:06:38.870> some<00:06:39.020> cash<00:06:39.260> attack 00:06:41.400 --> 00:06:41.410 align:start position:0% can sum sorry by making some cash attack 00:06:41.410 --> 00:06:44.320 align:start position:0% can sum sorry by making some cash attack the<00:06:42.410> other<00:06:42.560> method<00:06:42.950> is<00:06:43.160> second<00:06:43.580> cell<00:06:43.790> prostate 00:06:44.320 --> 00:06:44.330 align:start position:0% the other method is second cell prostate 00:06:44.330 --> 00:06:47.110 align:start position:0% the other method is second cell prostate so<00:06:45.320> in<00:06:45.830> classical<00:06:46.280> proof<00:06:46.490> of<00:06:46.610> stage 00:06:47.110 --> 00:06:47.120 align:start position:0% so in classical proof of stage 00:06:47.120 --> 00:06:50.020 align:start position:0% so in classical proof of stage you<00:06:47.890> always<00:06:48.890> subtract<00:06:49.340> second<00:06:49.670> cell<00:06:49.790> probe 00:06:50.020 --> 00:06:50.030 align:start position:0% you always subtract second cell probe 00:06:50.030 --> 00:06:53.890 align:start position:0% you always subtract second cell probe walk<00:06:50.740> in<00:06:51.740> the<00:06:51.950> classical<00:06:52.370> probe<00:06:52.580> walk<00:06:52.790> you<00:06:53.690> can 00:06:53.890 --> 00:06:53.900 align:start position:0% walk in the classical probe walk you can 00:06:53.900 --> 00:06:57.300 align:start position:0% walk in the classical probe walk you can paralyze<00:06:54.380> it<00:06:54.820> so<00:06:55.820> you<00:06:56.510> get<00:06:56.660> one<00:06:56.840> computer 00:06:57.300 --> 00:06:57.310 align:start position:0% paralyze it so you get one computer 00:06:57.310 --> 00:07:00.750 align:start position:0% paralyze it so you get one computer having<00:06:58.310> a<00:06:58.370> known<00:06:58.550> sequel<00:06:58.940> hero<00:06:59.420> one<00:06:59.810> was<00:06:59.930> 0.1 00:07:00.750 --> 00:07:00.760 align:start position:0% having a known sequel hero one was 0.1 00:07:00.760 --> 00:07:03.370 align:start position:0% having a known sequel hero one was 0.1 and<00:07:01.760> the<00:07:02.060> more<00:07:02.210> computer<00:07:02.540> you<00:07:02.630> have<00:07:02.780> the 00:07:03.370 --> 00:07:03.380 align:start position:0% and the more computer you have the 00:07:03.380 --> 00:07:07.030 align:start position:0% and the more computer you have the faster<00:07:03.770> you<00:07:04.190> get<00:07:04.340> to<00:07:04.520> find<00:07:04.790> a<00:07:04.940> block<00:07:05.470> in<00:07:06.470> this 00:07:07.030 --> 00:07:07.040 align:start position:0% faster you get to find a block in this 00:07:07.040 --> 00:07:12.610 align:start position:0% faster you get to find a block in this one<00:07:08.110> it's<00:07:09.110> not<00:07:09.230> the<00:07:09.320> case<00:07:09.640> so<00:07:10.640> you<00:07:11.090> start<00:07:11.810> with 00:07:12.610 --> 00:07:12.620 align:start position:0% one it's not the case so you start with 00:07:12.620 --> 00:07:16.210 align:start position:0% one it's not the case so you start with the<00:07:13.460> block<00:07:13.580> cache<00:07:13.790> and<00:07:14.390> you<00:07:14.420> a<00:07:15.500> and<00:07:15.680> you<00:07:16.190> a 00:07:16.210 --> 00:07:16.220 align:start position:0% the block cache and you a and you a 00:07:16.220 --> 00:07:17.770 align:start position:0% the block cache and you a and you a and<00:07:16.700> you<00:07:16.880> are<00:07:17.150> initiated<00:07:17.540> a<00:07:17.750> a 00:07:17.770 --> 00:07:18.970 align:start position:0% and you are initiated a a 00:07:18.970 --> 00:07:18.980 align:start position:0% 00:07:18.980 --> 00:07:23.260 align:start position:0% so<00:07:19.400> at<00:07:19.640> each<00:07:19.820> step<00:07:19.930> you<00:07:20.930> need<00:07:21.760> the<00:07:22.760> result<00:07:23.090> of 00:07:23.260 --> 00:07:23.270 align:start position:0% so at each step you need the result of 00:07:23.270 --> 00:07:26.170 align:start position:0% so at each step you need the result of the<00:07:23.450> previous<00:07:23.810> step<00:07:24.020> so<00:07:24.760> even<00:07:25.760> if<00:07:25.850> you<00:07:25.970> get 00:07:26.170 --> 00:07:26.180 align:start position:0% the previous step so even if you get 00:07:26.180 --> 00:07:31.350 align:start position:0% the previous step so even if you get tons<00:07:26.840> of<00:07:27.110> hardware<00:07:27.580> you<00:07:28.580> won't<00:07:28.820> be<00:07:28.970> faster<00:07:29.360> so 00:07:31.350 --> 00:07:31.360 align:start position:0% tons of hardware you won't be faster so 00:07:31.360 --> 00:07:34.510 align:start position:0% tons of hardware you won't be faster so what<00:07:32.360> does<00:07:32.690> it<00:07:32.810> do<00:07:32.930> you<00:07:33.110> it's<00:07:33.830> a<00:07:33.950> time<00:07:34.400> lock 00:07:34.510 --> 00:07:34.520 align:start position:0% what does it do you it's a time lock 00:07:34.520 --> 00:07:38.350 align:start position:0% what does it do you it's a time lock cryptography<00:07:35.090> the<00:07:35.560> goal<00:07:36.560> is<00:07:36.860> to<00:07:36.890> ensure<00:07:37.360> take 00:07:38.350 --> 00:07:38.360 align:start position:0% cryptography the goal is to ensure take 00:07:38.360 --> 00:07:41.130 align:start position:0% cryptography the goal is to ensure take some<00:07:38.600> time<00:07:38.840> to<00:07:39.620> compute<00:07:40.010> the<00:07:40.460> random<00:07:40.730> number 00:07:41.130 --> 00:07:41.140 align:start position:0% some time to compute the random number 00:07:41.140 --> 00:07:44.950 align:start position:0% some time to compute the random number such<00:07:42.140> as<00:07:42.170> this<00:07:42.530> way<00:07:42.940> if<00:07:43.940> you<00:07:44.120> are<00:07:44.180> minor<00:07:44.450> and 00:07:44.950 --> 00:07:44.960 align:start position:0% such as this way if you are minor and 00:07:44.960 --> 00:07:48.490 align:start position:0% such as this way if you are minor and you<00:07:45.440> want<00:07:45.590> to<00:07:45.710> get<00:07:45.800> bribed<00:07:46.130> or<00:07:46.550> you<00:07:47.350> want<00:07:48.350> no 00:07:48.490 --> 00:07:48.500 align:start position:0% you want to get bribed or you want no 00:07:48.500 --> 00:07:52.000 align:start position:0% you want to get bribed or you want no tribute<00:07:48.740> for<00:07:49.070> yourself<00:07:49.510> at<00:07:50.510> the<00:07:50.720> point<00:07:51.010> where 00:07:52.000 --> 00:07:52.010 align:start position:0% tribute for yourself at the point where 00:07:52.010 --> 00:07:55.530 align:start position:0% tribute for yourself at the point where you<00:07:52.580> have<00:07:52.610> your<00:07:52.880> block<00:07:53.090> if<00:07:53.930> you<00:07:54.110> wait<00:07:54.380> to<00:07:55.160> know 00:07:55.530 --> 00:07:55.540 align:start position:0% you have your block if you wait to know 00:07:55.540 --> 00:07:59.320 align:start position:0% you have your block if you wait to know this<00:07:56.540> result<00:07:57.340> someone<00:07:58.340> else<00:07:58.550> will<00:07:59.000> already 00:07:59.320 --> 00:07:59.330 align:start position:0% this result someone else will already 00:07:59.330 --> 00:08:02.530 align:start position:0% this result someone else will already published<00:07:59.690> one<00:07:59.950> so<00:08:00.950> okay<00:08:01.490> you<00:08:01.670> can<00:08:01.910> some 00:08:02.530 --> 00:08:02.540 align:start position:0% published one so okay you can some 00:08:02.540 --> 00:08:05.710 align:start position:0% published one so okay you can some source<00:08:02.810> on<00:08:03.100> but<00:08:04.100> you<00:08:04.550> don't<00:08:05.150> know<00:08:05.360> what<00:08:05.600> you 00:08:05.710 --> 00:08:05.720 align:start position:0% source on but you don't know what you 00:08:05.720 --> 00:08:12.550 align:start position:0% source on but you don't know what you sound<00:08:05.900> so<00:08:06.080> so<00:08:06.770> it's<00:08:07.220> still<00:08:07.400> random<00:08:11.140> but<00:08:12.140> there 00:08:12.550 --> 00:08:12.560 align:start position:0% sound so so it's still random but there 00:08:12.560 --> 00:08:15.370 align:start position:0% sound so so it's still random but there is<00:08:12.650> still<00:08:12.770> some<00:08:13.400> catch<00:08:13.720> because<00:08:14.720> if<00:08:15.020> you<00:08:15.170> want 00:08:15.370 --> 00:08:15.380 align:start position:0% is still some catch because if you want 00:08:15.380 --> 00:08:17.680 align:start position:0% is still some catch because if you want to<00:08:15.530> compute<00:08:15.950> some<00:08:16.280> second<00:08:16.550> shell<00:08:16.700> -<00:08:16.880> something 00:08:17.680 --> 00:08:17.690 align:start position:0% to compute some second shell - something 00:08:17.690 --> 00:08:19.690 align:start position:0% to compute some second shell - something like<00:08:17.840> 1<00:08:18.020> million<00:08:18.200> time<00:08:18.470> and<00:08:18.830> you<00:08:19.460> do<00:08:19.520> that<00:08:19.610> to 00:08:19.690 --> 00:08:19.700 align:start position:0% like 1 million time and you do that to 00:08:19.700 --> 00:08:22.510 align:start position:0% like 1 million time and you do that to me<00:08:19.790> smart<00:08:20.030> contract<00:08:20.420> you<00:08:21.200> will<00:08:21.410> run<00:08:21.680> into<00:08:22.220> the 00:08:22.510 --> 00:08:22.520 align:start position:0% me smart contract you will run into the 00:08:22.520 --> 00:08:26.650 align:start position:0% me smart contract you will run into the gas<00:08:22.760> limit<00:08:23.500> so<00:08:24.500> to<00:08:24.920> solve<00:08:25.190> that<00:08:25.430> you<00:08:26.390> need<00:08:26.540> to 00:08:26.650 --> 00:08:26.660 align:start position:0% gas limit so to solve that you need to 00:08:26.660 --> 00:08:29.890 align:start position:0% gas limit so to solve that you need to use<00:08:26.810> interactive<00:08:27.350> verification<00:08:28.040> I<00:08:29.030> guess 00:08:29.890 --> 00:08:29.900 align:start position:0% use interactive verification I guess 00:08:29.900 --> 00:08:32.170 align:start position:0% use interactive verification I guess some<00:08:30.050> of<00:08:30.140> you<00:08:30.260> have<00:08:30.440> been<00:08:30.470> at<00:08:31.180> true--but 00:08:32.170 --> 00:08:32.180 align:start position:0% some of you have been at true--but 00:08:32.180 --> 00:08:34.990 align:start position:0% some of you have been at true--but foundation<00:08:32.690> so<00:08:33.530> that's<00:08:34.310> the<00:08:34.460> same<00:08:34.610> concept 00:08:34.990 --> 00:08:35.000 align:start position:0% foundation so that's the same concept 00:08:35.000 --> 00:08:37.300 align:start position:0% foundation so that's the same concept except<00:08:35.630> here<00:08:35.930> it's<00:08:36.080> quite<00:08:36.560> simpler<00:08:36.919> because 00:08:37.300 --> 00:08:37.310 align:start position:0% except here it's quite simpler because 00:08:37.310 --> 00:08:38.600 align:start position:0% except here it's quite simpler because we<00:08:37.610> just<00:08:37.760> assumed 00:08:38.600 --> 00:08:38.610 align:start position:0% we just assumed 00:08:38.610 --> 00:08:41.170 align:start position:0% we just assumed country<00:08:39.060> or<00:08:39.269> complicated<00:08:39.719> stuff<00:08:39.990> just<00:08:40.229> ashes 00:08:41.170 --> 00:08:41.180 align:start position:0% country or complicated stuff just ashes 00:08:41.180 --> 00:08:45.920 align:start position:0% country or complicated stuff just ashes so<00:08:42.180> you<00:08:43.019> let<00:08:43.140> every<00:08:43.409> party<00:08:44.209> post<00:08:45.209> the<00:08:45.360> result<00:08:45.690> a 00:08:45.920 --> 00:08:45.930 align:start position:0% so you let every party post the result a 00:08:45.930 --> 00:08:48.829 align:start position:0% so you let every party post the result a deposit<00:08:46.500> and<00:08:46.709> then<00:08:47.670> you<00:08:47.850> have<00:08:47.970> a<00:08:48.000> replication 00:08:48.829 --> 00:08:48.839 align:start position:0% deposit and then you have a replication 00:08:48.839 --> 00:08:52.840 align:start position:0% deposit and then you have a replication game<00:08:49.140> which<00:08:50.510> guarantee<00:08:51.510> that<00:08:51.720> each<00:08:51.990> party 00:08:52.840 --> 00:08:52.850 align:start position:0% game which guarantee that each party 00:08:52.850 --> 00:08:56.780 align:start position:0% game which guarantee that each party wins<00:08:53.850> honest<00:08:54.269> so<00:08:54.930> the<00:08:55.890> Challenger<00:08:56.310> of<00:08:56.490> a<00:08:56.579> fake 00:08:56.780 --> 00:08:56.790 align:start position:0% wins honest so the Challenger of a fake 00:08:56.790 --> 00:08:57.139 align:start position:0% wins honest so the Challenger of a fake number 00:08:57.139 --> 00:08:57.149 align:start position:0% number 00:08:57.149 --> 00:09:01.370 align:start position:0% number all<00:08:57.360> the<00:08:58.019> defender<00:08:58.529> of<00:08:59.430> the<00:08:59.760> right<00:09:00.240> one<00:09:00.450> will 00:09:01.370 --> 00:09:01.380 align:start position:0% all the defender of the right one will 00:09:01.380 --> 00:09:04.100 align:start position:0% all the defender of the right one will always<00:09:01.649> win<00:09:02.040> the<00:09:02.160> challenge<00:09:02.490> and<00:09:03.110> when 00:09:04.100 --> 00:09:04.110 align:start position:0% always win the challenge and when 00:09:04.110 --> 00:09:06.980 align:start position:0% always win the challenge and when someone<00:09:04.440> puts<00:09:04.709> fake<00:09:05.010> numbers<00:09:05.370> you<00:09:06.329> will 00:09:06.980 --> 00:09:06.990 align:start position:0% someone puts fake numbers you will 00:09:06.990 --> 00:09:08.870 align:start position:0% someone puts fake numbers you will possibly<00:09:07.410> deposit<00:09:07.800> and<00:09:08.070> give<00:09:08.399> thought<00:09:08.610> to 00:09:08.870 --> 00:09:08.880 align:start position:0% possibly deposit and give thought to 00:09:08.880 --> 00:09:13.360 align:start position:0% possibly deposit and give thought to challenges<00:09:10.610> so<00:09:11.610> one<00:09:11.730> charge<00:09:11.910> of<00:09:12.089> litigation 00:09:13.360 --> 00:09:13.370 align:start position:0% challenges so one charge of litigation 00:09:13.370 --> 00:09:15.650 align:start position:0% challenges so one charge of litigation that's<00:09:14.370> assumed<00:09:14.790> here<00:09:15.000> for<00:09:15.209> the<00:09:15.269> sake<00:09:15.420> of<00:09:15.450> the 00:09:15.650 --> 00:09:15.660 align:start position:0% that's assumed here for the sake of the 00:09:15.660 --> 00:09:17.569 align:start position:0% that's assumed here for the sake of the example<00:09:15.720> that<00:09:16.050> I<00:09:16.380> should<00:09:16.620> use<00:09:16.769> this<00:09:17.010> one<00:09:17.070> don't 00:09:17.569 --> 00:09:17.579 align:start position:0% example that I should use this one don't 00:09:17.579 --> 00:09:19.930 align:start position:0% example that I should use this one don't use<00:09:18.060> that<00:09:18.180> as<00:09:18.329> an<00:09:18.420> ash<00:09:18.540> at<00:09:18.899> least<00:09:19.110> for<00:09:19.230> example 00:09:19.930 --> 00:09:19.940 align:start position:0% use that as an ash at least for example 00:09:19.940 --> 00:09:23.180 align:start position:0% use that as an ash at least for example you<00:09:20.940> compute<00:09:21.360> you<00:09:21.630> get<00:09:21.779> seventeen<00:09:22.410> and<00:09:22.740> some 00:09:23.180 --> 00:09:23.190 align:start position:0% you compute you get seventeen and some 00:09:23.190 --> 00:09:27.290 align:start position:0% you compute you get seventeen and some of<00:09:23.310> the<00:09:23.370> party<00:09:23.779> said<00:09:24.779> 35<00:09:25.430> which<00:09:26.430> is<00:09:26.459> a<00:09:26.820> fake 00:09:27.290 --> 00:09:27.300 align:start position:0% of the party said 35 which is a fake 00:09:27.300 --> 00:09:31.430 align:start position:0% of the party said 35 which is a fake cancer<00:09:27.829> so<00:09:28.829> you<00:09:28.860> ask<00:09:29.250> at<00:09:29.490> this<00:09:29.610> party<00:09:30.000> what<00:09:30.720> is 00:09:31.430 --> 00:09:31.440 align:start position:0% cancer so you ask at this party what is 00:09:31.440 --> 00:09:34.220 align:start position:0% cancer so you ask at this party what is the<00:09:31.589> value<00:09:31.680> at<00:09:32.190> the<00:09:32.370> nine<00:09:32.519> step<00:09:32.790> and<00:09:33.750> he<00:09:33.990> says 00:09:34.220 --> 00:09:34.230 align:start position:0% the value at the nine step and he says 00:09:34.230 --> 00:09:37.490 align:start position:0% the value at the nine step and he says 27<00:09:35.010> so<00:09:35.940> now<00:09:36.269> you<00:09:36.329> know<00:09:36.570> that<00:09:36.810> made<00:09:37.110> mistake 00:09:37.490 --> 00:09:37.500 align:start position:0% 27 so now you know that made mistake 00:09:37.500 --> 00:09:43.130 align:start position:0% 27 so now you know that made mistake between<00:09:38.100> 0<00:09:39.029> and<00:09:39.450> 9<00:09:41.029> so<00:09:42.029> you<00:09:42.089> ask<00:09:42.329> except<00:09:42.690> for<00:09:42.930> it 00:09:43.130 --> 00:09:43.140 align:start position:0% between 0 and 9 so you ask except for it 00:09:43.140 --> 00:09:45.410 align:start position:0% between 0 and 9 so you ask except for it says<00:09:43.230> 4<00:09:43.470> 4<00:09:43.829> is<00:09:43.920> correct<00:09:44.100> so<00:09:44.880> you<00:09:44.910> know<00:09:45.329> it's 00:09:45.410 --> 00:09:45.420 align:start position:0% says 4 4 is correct so you know it's 00:09:45.420 --> 00:09:47.560 align:start position:0% says 4 4 is correct so you know it's mistake<00:09:45.690> is<00:09:45.810> between<00:09:46.050> 4<00:09:46.350> &<00:09:46.649> 9 00:09:47.560 --> 00:09:47.570 align:start position:0% mistake is between 4 & 9 00:09:47.570 --> 00:09:54.050 align:start position:0% mistake is between 4 & 9 you<00:09:48.570> ask<00:09:49.370> 6<00:09:50.370> he<00:09:51.029> says<00:09:51.209> 24<00:09:51.810> is<00:09:52.740> incorrect<00:09:53.459> you 00:09:54.050 --> 00:09:54.060 align:start position:0% you ask 6 he says 24 is incorrect you 00:09:54.060 --> 00:09:58.639 align:start position:0% you ask 6 he says 24 is incorrect you guys<00:09:54.209> got<00:09:54.360> five<00:09:54.570> and<00:09:54.899> now<00:09:55.579> you<00:09:56.579> show<00:09:56.790> 5<00:09:57.620> plus<00:09:58.620> 1 00:09:58.639 --> 00:09:58.649 align:start position:0% guys got five and now you show 5 plus 1 00:09:58.649 --> 00:10:03.829 align:start position:0% guys got five and now you show 5 plus 1 is<00:09:59.040> 6<00:09:59.480> not<00:10:00.480> 24<00:10:01.140> so<00:10:01.740> you've<00:10:02.130> proven<00:10:02.519> that<00:10:02.839> he 00:10:03.829 --> 00:10:03.839 align:start position:0% is 6 not 24 so you've proven that he 00:10:03.839 --> 00:10:10.579 align:start position:0% is 6 not 24 so you've proven that he admits<00:10:04.560> a<00:10:04.620> mistake<00:10:04.920> in<00:10:05.190> computation<00:10:09.589> but 00:10:10.579 --> 00:10:10.589 align:start position:0% admits a mistake in computation but 00:10:10.589 --> 00:10:12.500 align:start position:0% admits a mistake in computation but there<00:10:11.010> are<00:10:11.100> still<00:10:11.279> some<00:10:11.490> some<00:10:11.880> issue<00:10:12.089> with 00:10:12.500 --> 00:10:12.510 align:start position:0% there are still some some issue with 00:10:12.510 --> 00:10:19.160 align:start position:0% there are still some some issue with that<00:10:13.190> which<00:10:14.190> is<00:10:14.220> that<00:10:15.019> a<00:10:16.019> party<00:10:16.709> can<00:10:17.339> put<00:10:18.170> tech 00:10:19.160 --> 00:10:19.170 align:start position:0% that which is that a party can put tech 00:10:19.170 --> 00:10:23.750 align:start position:0% that which is that a party can put tech numbers<00:10:19.529> put<00:10:20.399> some<00:10:20.610> deposits<00:10:20.880> and<00:10:22.070> okay<00:10:23.070> this 00:10:23.750 --> 00:10:23.760 align:start position:0% numbers put some deposits and okay this 00:10:23.760 --> 00:10:27.230 align:start position:0% numbers put some deposits and okay this party<00:10:24.149> won't<00:10:24.360> be<00:10:24.600> able<00:10:25.279> to<00:10:26.279> change<00:10:26.820> a<00:10:26.940> number 00:10:27.230 --> 00:10:27.240 align:start position:0% party won't be able to change a number 00:10:27.240 --> 00:10:31.610 align:start position:0% party won't be able to change a number but<00:10:27.870> this<00:10:28.050> party<00:10:28.380> will<00:10:28.560> be<00:10:29.209> able<00:10:30.209> to<00:10:30.480> delay<00:10:30.959> the 00:10:31.610 --> 00:10:31.620 align:start position:0% but this party will be able to delay the 00:10:31.620 --> 00:10:39.250 align:start position:0% but this party will be able to delay the time<00:10:31.860> this<00:10:32.730> number<00:10:33.290> will<00:10:34.290> be<00:10:34.320> available<00:10:37.640> so 00:10:39.250 --> 00:10:39.260 align:start position:0% time this number will be available so 00:10:39.260 --> 00:10:44.569 align:start position:0% time this number will be available so also<00:10:40.640> if<00:10:41.640> we<00:10:41.940> implement<00:10:42.680> the<00:10:43.680> incentive<00:10:44.399> in 00:10:44.569 --> 00:10:44.579 align:start position:0% also if we implement the incentive in 00:10:44.579 --> 00:10:48.050 align:start position:0% also if we implement the incentive in the<00:10:44.730> challenge<00:10:45.000> naively<00:10:45.449> you<00:10:47.060> would 00:10:48.050 --> 00:10:48.060 align:start position:0% the challenge naively you would 00:10:48.060 --> 00:10:49.410 align:start position:0% the challenge naively you would challenge<00:10:48.240> a<00:10:48.420> number 00:10:49.410 --> 00:10:49.420 align:start position:0% challenge a number 00:10:49.420 --> 00:10:51.480 align:start position:0% challenge a number and<00:10:49.510> the<00:10:50.470> policies<00:10:50.860> we<00:10:50.980> put<00:10:51.190> in<00:10:51.400> effect 00:10:51.480 --> 00:10:51.490 align:start position:0% and the policies we put in effect 00:10:51.490 --> 00:10:54.150 align:start position:0% and the policies we put in effect numbers<00:10:51.970> would<00:10:52.630> challenge<00:10:52.870> is<00:10:53.230> own<00:10:53.590> number 00:10:54.150 --> 00:10:54.160 align:start position:0% numbers would challenge is own number 00:10:54.160 --> 00:10:59.010 align:start position:0% numbers would challenge is own number and<00:10:54.810> make<00:10:55.810> sure<00:10:56.080> to<00:10:56.500> lose<00:10:56.680> against<00:10:57.510> itself<00:10:58.510> in 00:10:59.010 --> 00:10:59.020 align:start position:0% and make sure to lose against itself in 00:10:59.020 --> 00:11:03.750 align:start position:0% and make sure to lose against itself in such<00:11:00.010> a<00:11:00.520> way<00:11:00.730> that<00:11:00.760> you<00:11:01.180> don't<00:11:01.420> win<00:11:02.050> the<00:11:02.980> part 00:11:03.750 --> 00:11:03.760 align:start position:0% such a way that you don't win the part 00:11:03.760 --> 00:11:08.640 align:start position:0% such a way that you don't win the part of<00:11:03.910> the<00:11:04.000> deposit<00:11:04.390> and<00:11:05.520> our<00:11:06.520> goal<00:11:06.820> is<00:11:07.500> to<00:11:08.500> design 00:11:08.640 --> 00:11:08.650 align:start position:0% of the deposit and our goal is to design 00:11:08.650 --> 00:11:12.660 align:start position:0% of the deposit and our goal is to design a<00:11:08.830> system<00:11:09.930> suggest<00:11:10.930> if<00:11:11.170> you<00:11:11.440> have<00:11:12.190> even<00:11:12.550> a 00:11:12.660 --> 00:11:12.670 align:start position:0% a system suggest if you have even a 00:11:12.670 --> 00:11:14.640 align:start position:0% a system suggest if you have even a small<00:11:12.850> deposit<00:11:13.540> that<00:11:13.990> you<00:11:14.050> can<00:11:14.260> use<00:11:14.440> to 00:11:14.640 --> 00:11:14.650 align:start position:0% small deposit that you can use to 00:11:14.650 --> 00:11:17.010 align:start position:0% small deposit that you can use to challenge<00:11:14.980> it<00:11:15.130> make<00:11:15.670> challenge<00:11:15.970> compared<00:11:16.840> to 00:11:17.010 --> 00:11:17.020 align:start position:0% challenge it make challenge compared to 00:11:17.020 --> 00:11:20.010 align:start position:0% challenge it make challenge compared to an<00:11:17.110> attacker<00:11:17.410> with<00:11:18.250> a<00:11:18.430> large<00:11:18.880> budget<00:11:19.150> making 00:11:20.010 --> 00:11:20.020 align:start position:0% an attacker with a large budget making 00:11:20.020 --> 00:11:22.740 align:start position:0% an attacker with a large budget making tons<00:11:20.590> of<00:11:20.800> fake<00:11:21.010> numbers<00:11:21.280> as<00:11:22.120> you<00:11:22.300> only<00:11:22.450> say 00:11:22.740 --> 00:11:22.750 align:start position:0% tons of fake numbers as you only say 00:11:22.750 --> 00:11:24.090 align:start position:0% tons of fake numbers as you only say okay<00:11:22.930> at<00:11:23.050> the<00:11:23.170> first<00:11:23.380> one<00:11:23.530> you<00:11:23.650> are<00:11:23.770> going<00:11:23.980> to 00:11:24.090 --> 00:11:24.100 align:start position:0% okay at the first one you are going to 00:11:24.100 --> 00:11:27.720 align:start position:0% okay at the first one you are going to challenge<00:11:24.250> one<00:11:24.520> number<00:11:24.730> you<00:11:25.410> win<00:11:26.410> and<00:11:26.770> you<00:11:26.800> get 00:11:27.720 --> 00:11:27.730 align:start position:0% challenge one number you win and you get 00:11:27.730 --> 00:11:29.910 align:start position:0% challenge one number you win and you get alpha<00:11:28.180> by<00:11:28.390> deposit<00:11:28.810> now<00:11:29.110> you<00:11:29.170> have<00:11:29.350> 1.5 00:11:29.910 --> 00:11:29.920 align:start position:0% alpha by deposit now you have 1.5 00:11:29.920 --> 00:11:32.220 align:start position:0% alpha by deposit now you have 1.5 deposit<00:11:30.520> the<00:11:31.090> second<00:11:31.390> step<00:11:31.570> you<00:11:31.810> do<00:11:31.870> it<00:11:31.960> again 00:11:32.220 --> 00:11:32.230 align:start position:0% deposit the second step you do it again 00:11:32.230 --> 00:11:34.530 align:start position:0% deposit the second step you do it again now<00:11:32.710> you<00:11:32.770> get<00:11:32.950> two<00:11:33.160> deposits<00:11:33.460> and<00:11:33.820> now<00:11:34.300> we<00:11:34.360> get 00:11:34.530 --> 00:11:34.540 align:start position:0% now you get two deposits and now we get 00:11:34.540 --> 00:11:36.180 align:start position:0% now you get two deposits and now we get to<00:11:34.660> deposit<00:11:34.930> so<00:11:35.440> you<00:11:35.530> can<00:11:35.680> challenge<00:11:35.860> two 00:11:36.180 --> 00:11:36.190 align:start position:0% to deposit so you can challenge two 00:11:36.190 --> 00:11:38.820 align:start position:0% to deposit so you can challenge two numbers<00:11:36.550> at<00:11:36.670> the<00:11:36.730> same<00:11:36.880> time<00:11:37.090> and<00:11:37.680> next<00:11:38.680> step 00:11:38.820 --> 00:11:38.830 align:start position:0% numbers at the same time and next step 00:11:38.830 --> 00:11:40.980 align:start position:0% numbers at the same time and next step you<00:11:39.070> get<00:11:39.160> really<00:11:39.520> posit<00:11:39.880> and<00:11:40.090> so<00:11:40.600> over<00:11:40.870> and 00:11:40.980 --> 00:11:40.990 align:start position:0% you get really posit and so over and 00:11:40.990 --> 00:11:43.740 align:start position:0% you get really posit and so over and over<00:11:41.230> and<00:11:42.010> you<00:11:42.070> deposit<00:11:42.760> is<00:11:43.030> increasing 00:11:43.740 --> 00:11:43.750 align:start position:0% over and you deposit is increasing 00:11:43.750 --> 00:11:45.900 align:start position:0% over and you deposit is increasing exponentially<00:11:44.290> of<00:11:44.890> course<00:11:45.250> to<00:11:45.580> the<00:11:45.670> point 00:11:45.900 --> 00:11:45.910 align:start position:0% exponentially of course to the point 00:11:45.910 --> 00:11:48.660 align:start position:0% exponentially of course to the point where<00:11:46.180> I<00:11:46.240> will<00:11:46.360> finish<00:11:46.570> to<00:11:46.810> disprove<00:11:47.740> all<00:11:48.100> the 00:11:48.660 --> 00:11:48.670 align:start position:0% where I will finish to disprove all the 00:11:48.670 --> 00:11:53.940 align:start position:0% where I will finish to disprove all the numbers<00:11:48.940> so<00:11:50.820> the<00:11:51.820> author<00:11:51.970> ID<00:11:52.180> is<00:11:52.840> the<00:11:53.380> splinter 00:11:53.940 --> 00:11:53.950 align:start position:0% numbers so the author ID is the splinter 00:11:53.950 --> 00:11:57.600 align:start position:0% numbers so the author ID is the splinter reward<00:11:54.510> between<00:11:55.510> each<00:11:55.780> party<00:11:56.170> challenging<00:11:56.620> no 00:11:57.600 --> 00:11:57.610 align:start position:0% reward between each party challenging no 00:11:57.610 --> 00:12:02.430 align:start position:0% reward between each party challenging no matter<00:11:57.790> which<00:11:58.480> challenge<00:11:59.040> is<00:12:00.040> winning<00:12:01.440> but 00:12:02.430 --> 00:12:02.440 align:start position:0% matter which challenge is winning but 00:12:02.440 --> 00:12:04.140 align:start position:0% matter which challenge is winning but there<00:12:02.530> is<00:12:02.650> still<00:12:02.740> a<00:12:03.340> catch<00:12:03.580> I<00:12:03.790> receive<00:12:04.060> an 00:12:04.140 --> 00:12:04.150 align:start position:0% there is still a catch I receive an 00:12:04.150 --> 00:12:08.820 align:start position:0% there is still a catch I receive an issue<00:12:04.470> where<00:12:05.470> the<00:12:06.070> attacker<00:12:06.930> can<00:12:07.930> when<00:12:08.740> you 00:12:08.820 --> 00:12:08.830 align:start position:0% issue where the attacker can when you 00:12:08.830 --> 00:12:12.840 align:start position:0% issue where the attacker can when you challenge<00:12:09.160> one<00:12:09.370> of<00:12:09.490> this<00:12:09.580> number<00:12:10.110> keep<00:12:11.110> a<00:12:11.850> huge 00:12:12.840 --> 00:12:12.850 align:start position:0% challenge one of this number keep a huge 00:12:12.850 --> 00:12:16.460 align:start position:0% challenge one of this number keep a huge part<00:12:13.150> of<00:12:13.270> this<00:12:13.360> budget<00:12:13.830> to<00:12:14.830> also<00:12:15.190> challenge<00:12:15.550> it 00:12:16.460 --> 00:12:16.470 align:start position:0% part of this budget to also challenge it 00:12:16.470 --> 00:12:19.770 align:start position:0% part of this budget to also challenge it such<00:12:17.470> as<00:12:17.620> this<00:12:17.770> way<00:12:18.010> you<00:12:18.730> will<00:12:18.880> get<00:12:19.060> almost<00:12:19.480> all 00:12:19.770 --> 00:12:19.780 align:start position:0% such as this way you will get almost all 00:12:19.780 --> 00:12:23.430 align:start position:0% such as this way you will get almost all the<00:12:19.930> reward<00:12:20.080> you<00:12:20.620> will<00:12:21.280> get<00:12:21.400> peanuts<00:12:21.790> and<00:12:22.440> you 00:12:23.430 --> 00:12:23.440 align:start position:0% the reward you will get peanuts and you 00:12:23.440 --> 00:12:26.460 align:start position:0% the reward you will get peanuts and you will<00:12:23.590> never<00:12:23.800> be<00:12:24.010> able<00:12:24.100> to<00:12:25.030> challenge<00:12:25.570> multiple 00:12:26.460 --> 00:12:26.470 align:start position:0% will never be able to challenge multiple 00:12:26.470 --> 00:12:34.970 align:start position:0% will never be able to challenge multiple numbers<00:12:27.570> in<00:12:28.570> any<00:12:29.170> one<00:12:29.440> run<00:12:29.980> of<00:12:30.010> challenge 00:12:34.970 --> 00:12:34.980 align:start position:0% 00:12:34.980 --> 00:12:39.710 align:start position:0% so<00:12:35.610> or<00:12:36.210> to<00:12:36.390> avoid<00:12:36.600> that<00:12:37.340> it's<00:12:38.340> with<00:12:39.180> committin 00:12:39.710 --> 00:12:39.720 align:start position:0% so or to avoid that it's with committin 00:12:39.720 --> 00:12:45.500 align:start position:0% so or to avoid that it's with committin reveal<00:12:41.330> so<00:12:42.800> you<00:12:43.800> commit<00:12:44.160> to<00:12:45.030> challenge<00:12:45.390> a 00:12:45.500 --> 00:12:45.510 align:start position:0% reveal so you commit to challenge a 00:12:45.510 --> 00:12:49.820 align:start position:0% reveal so you commit to challenge a particular<00:12:45.990> number<00:12:46.910> and<00:12:48.320> in<00:12:49.320> a<00:12:49.380> second<00:12:49.650> phase 00:12:49.820 --> 00:12:49.830 align:start position:0% particular number and in a second phase 00:12:49.830 --> 00:12:52.670 align:start position:0% particular number and in a second phase you<00:12:50.160> really<00:12:50.790> will<00:12:50.940> that<00:12:51.840> you<00:12:51.990> are<00:12:52.110> you<00:12:52.350> want<00:12:52.530> it 00:12:52.670 --> 00:12:52.680 align:start position:0% you really will that you are you want it 00:12:52.680 --> 00:12:55.310 align:start position:0% you really will that you are you want it to<00:12:52.740> change<00:12:52.770> this<00:12:53.130> one<00:12:53.370> an<00:12:54.090> in<00:12:54.240> such<00:12:54.390> a<00:12:54.420> way<00:12:54.660> the 00:12:55.310 --> 00:12:55.320 align:start position:0% to change this one an in such a way the 00:12:55.320 --> 00:12:58.070 align:start position:0% to change this one an in such a way the attacker<00:12:55.620> it<00:12:56.490> does<00:12:56.640> not<00:12:56.850> know<00:12:57.150> which<00:12:57.780> of<00:12:58.020> his 00:12:58.070 --> 00:12:58.080 align:start position:0% attacker it does not know which of his 00:12:58.080 --> 00:13:01.850 align:start position:0% attacker it does not know which of his number<00:12:58.440> you're<00:12:59.370> going<00:12:59.490> to<00:12:59.550> challenge<00:13:00.320> so<00:13:01.320> of 00:13:01.850 --> 00:13:01.860 align:start position:0% number you're going to challenge so of 00:13:01.860 --> 00:13:04.310 align:start position:0% number you're going to challenge so of who<00:13:02.130> we<00:13:02.790> can<00:13:03.000> try<00:13:03.270> to<00:13:03.330> challenge<00:13:03.840> number<00:13:04.170> one 00:13:04.310 --> 00:13:04.320 align:start position:0% who we can try to challenge number one 00:13:04.320 --> 00:13:07.550 align:start position:0% who we can try to challenge number one only<00:13:04.640> but<00:13:05.640> if<00:13:06.420> he's<00:13:06.690> gonna<00:13:06.870> challenge<00:13:07.140> a 00:13:07.550 --> 00:13:07.560 align:start position:0% only but if he's gonna challenge a 00:13:07.560 --> 00:13:09.350 align:start position:0% only but if he's gonna challenge a number<00:13:08.040> which<00:13:08.250> you<00:13:08.430> have<00:13:08.550> been<00:13:08.730> challenged 00:13:09.350 --> 00:13:09.360 align:start position:0% number which you have been challenged 00:13:09.360 --> 00:13:12.500 align:start position:0% number which you have been challenged it<00:13:09.960> will<00:13:10.140> either<00:13:10.380> loose<00:13:11.310> deposit<00:13:11.820> as<00:13:12.450> a 00:13:12.500 --> 00:13:12.510 align:start position:0% it will either loose deposit as a 00:13:12.510 --> 00:13:16.610 align:start position:0% it will either loose deposit as a challenger<00:13:13.050> all<00:13:13.910> remove<00:13:14.910> the<00:13:15.360> tech<00:13:15.510> number<00:13:15.690> so 00:13:16.610 --> 00:13:16.620 align:start position:0% challenger all remove the tech number so 00:13:16.620 --> 00:13:21.440 align:start position:0% challenger all remove the tech number so in<00:13:16.770> both<00:13:17.130> cases<00:13:17.570> is<00:13:18.570> losing<00:13:19.490> of<00:13:20.490> who's<00:13:20.880> in<00:13:21.240> the 00:13:21.440 --> 00:13:21.450 align:start position:0% in both cases is losing of who's in the 00:13:21.450 --> 00:13:23.450 align:start position:0% in both cases is losing of who's in the wall<00:13:21.660> scale<00:13:21.960> in<00:13:22.590> the<00:13:22.770> worst<00:13:22.950> case<00:13:23.160> you<00:13:23.190> have<00:13:23.430> a 00:13:23.450 --> 00:13:23.460 align:start position:0% wall scale in the worst case you have a 00:13:23.460 --> 00:13:26.210 align:start position:0% wall scale in the worst case you have a super<00:13:23.820> look<00:13:24.000> he<00:13:24.210> attack<00:13:24.540> her<00:13:24.690> and<00:13:25.020> each<00:13:25.890> time 00:13:26.210 --> 00:13:26.220 align:start position:0% super look he attack her and each time 00:13:26.220 --> 00:13:31.130 align:start position:0% super look he attack her and each time is<00:13:27.060> getting<00:13:27.330> right<00:13:28.340> in<00:13:29.360> the<00:13:30.360> number<00:13:30.600> that<00:13:31.050> you 00:13:31.130 --> 00:13:31.140 align:start position:0% is getting right in the number that you 00:13:31.140 --> 00:13:36.350 align:start position:0% is getting right in the number that you can<00:13:31.230> a<00:13:31.290> challenge<00:13:34.100> but<00:13:35.100> of<00:13:35.430> course<00:13:35.970> they'll 00:13:36.350 --> 00:13:36.360 align:start position:0% can a challenge but of course they'll 00:13:36.360 --> 00:13:38.810 align:start position:0% can a challenge but of course they'll just<00:13:36.540> relax<00:13:36.900> in<00:13:37.170> the<00:13:37.290> worst<00:13:37.470> case<00:13:37.650> so<00:13:38.520> we<00:13:38.670> can 00:13:38.810 --> 00:13:38.820 align:start position:0% just relax in the worst case so we can 00:13:38.820 --> 00:13:42.110 align:start position:0% just relax in the worst case so we can look<00:13:39.420> at<00:13:39.540> what<00:13:39.930> would<00:13:40.140> happen<00:13:40.800> in<00:13:41.340> the<00:13:41.610> average 00:13:42.110 --> 00:13:42.120 align:start position:0% look at what would happen in the average 00:13:42.120 --> 00:13:45.380 align:start position:0% look at what would happen in the average case<00:13:43.250> and<00:13:44.250> in<00:13:44.430> this<00:13:44.550> way<00:13:44.790> from<00:13:44.850> all<00:13:45.360> the 00:13:45.380 --> 00:13:45.390 align:start position:0% case and in this way from all the 00:13:45.390 --> 00:13:49.430 align:start position:0% case and in this way from all the strategy<00:13:46.050> I<00:13:46.470> such<00:13:47.160> an<00:13:47.430> attacker<00:13:47.700> could<00:13:48.000> have<00:13:48.440> I 00:13:49.430 --> 00:13:49.440 align:start position:0% strategy I such an attacker could have I 00:13:49.440 --> 00:13:52.760 align:start position:0% strategy I such an attacker could have I have<00:13:50.370> include<00:13:50.670> anyone<00:13:50.940> which<00:13:51.750> will<00:13:52.020> not<00:13:52.260> allow 00:13:52.760 --> 00:13:52.770 align:start position:0% have include anyone which will not allow 00:13:52.770 --> 00:13:57.620 align:start position:0% have include anyone which will not allow to<00:13:53.280> have<00:13:53.700> the<00:13:54.480> number<00:13:55.040> by<00:13:56.180> logarithmic<00:13:57.180> amount 00:13:57.620 --> 00:13:57.630 align:start position:0% to have the number by logarithmic amount 00:13:57.630 --> 00:14:02.620 align:start position:0% to have the number by logarithmic amount of<00:13:57.750> depth<00:14:00.500> so<00:14:01.500> that's<00:14:01.830> still<00:14:01.920> a<00:14:01.980> conjecture 00:14:02.620 --> 00:14:02.630 align:start position:0% of depth so that's still a conjecture 00:14:02.630 --> 00:14:05.870 align:start position:0% of depth so that's still a conjecture you<00:14:03.630> need<00:14:03.930> to<00:14:04.020> prove<00:14:04.200> it<00:14:04.260> because<00:14:05.010> you<00:14:05.640> need<00:14:05.790> to 00:14:05.870 --> 00:14:05.880 align:start position:0% you need to prove it because you need to 00:14:05.880 --> 00:14:08.060 align:start position:0% you need to prove it because you need to prove<00:14:06.090> that<00:14:06.120> there<00:14:06.330> is<00:14:06.360> no<00:14:06.720> strategy<00:14:07.070> are 00:14:08.060 --> 00:14:08.070 align:start position:0% prove that there is no strategy are 00:14:08.070 --> 00:14:11.300 align:start position:0% prove that there is no strategy are going<00:14:08.310> to<00:14:08.370> do<00:14:08.490> that<00:14:09.170> and<00:14:10.170> if<00:14:10.590> someone<00:14:11.220> is 00:14:11.300 --> 00:14:11.310 align:start position:0% going to do that and if someone is 00:14:11.310 --> 00:14:13.100 align:start position:0% going to do that and if someone is interested<00:14:11.610> by<00:14:12.000> having<00:14:12.450> this<00:14:12.510> proof<00:14:12.780> or 00:14:13.100 --> 00:14:13.110 align:start position:0% interested by having this proof or 00:14:13.110 --> 00:14:16.100 align:start position:0% interested by having this proof or someone<00:14:13.470> as<00:14:13.700> insight<00:14:14.700> in<00:14:14.850> this<00:14:15.000> proof<00:14:15.210> I<00:14:15.420> would 00:14:16.100 --> 00:14:16.110 align:start position:0% someone as insight in this proof I would 00:14:16.110 --> 00:14:21.320 align:start position:0% someone as insight in this proof I would be<00:14:16.290> really<00:14:16.740> happy<00:14:17.220> to<00:14:17.580> speak<00:14:17.940> about<00:14:18.030> that<00:14:20.330> so 00:14:21.320 --> 00:14:21.330 align:start position:0% be really happy to speak about that so 00:14:21.330 --> 00:14:24.020 align:start position:0% be really happy to speak about that so for<00:14:21.510> this<00:14:21.600> seconds<00:14:21.870> are<00:14:21.990> full<00:14:22.170> of<00:14:22.290> work<00:14:23.030> within 00:14:24.020 --> 00:14:24.030 align:start position:0% for this seconds are full of work within 00:14:24.030 --> 00:14:27.370 align:start position:0% for this seconds are full of work within the<00:14:24.470> problem<00:14:25.470> which<00:14:26.130> is<00:14:26.340> that<00:14:26.490> it<00:14:26.730> takes<00:14:26.880> time 00:14:27.370 --> 00:14:27.380 align:start position:0% the problem which is that it takes time 00:14:27.380 --> 00:14:30.560 align:start position:0% the problem which is that it takes time so<00:14:28.380> it's<00:14:29.040> not<00:14:29.250> suited<00:14:29.580> for<00:14:29.790> a<00:14:29.850> real-time 00:14:30.560 --> 00:14:30.570 align:start position:0% so it's not suited for a real-time 00:14:30.570 --> 00:14:34.310 align:start position:0% so it's not suited for a real-time application<00:14:31.550> if<00:14:32.550> you<00:14:32.610> want<00:14:32.760> to<00:14:33.060> bet<00:14:33.320> that's 00:14:34.310 --> 00:14:34.320 align:start position:0% application if you want to bet that's 00:14:34.320 --> 00:14:35.180 align:start position:0% application if you want to bet that's not<00:14:34.500> a<00:14:34.680> good<00:14:34.890> idea 00:14:35.180 --> 00:14:35.190 align:start position:0% not a good idea 00:14:35.190 --> 00:14:37.550 align:start position:0% not a good idea Wow<00:14:35.790> Oh<00:14:35.970> in<00:14:36.450> the<00:14:36.600> rotary<00:14:36.900> okay<00:14:37.170> but<00:14:37.320> if<00:14:37.440> you 00:14:37.550 --> 00:14:37.560 align:start position:0% Wow Oh in the rotary okay but if you 00:14:37.560 --> 00:14:39.950 align:start position:0% Wow Oh in the rotary okay but if you want<00:14:37.590> to<00:14:37.830> bet<00:14:38.010> in<00:14:38.160> real<00:14:38.370> time<00:14:38.600> that's<00:14:39.600> a<00:14:39.720> good 00:14:39.950 --> 00:14:39.960 align:start position:0% want to bet in real time that's a good 00:14:39.960 --> 00:14:40.420 align:start position:0% want to bet in real time that's a good idea 00:14:40.420 --> 00:14:40.430 align:start position:0% idea 00:14:40.430 --> 00:14:43.220 align:start position:0% idea if<00:14:41.430> you<00:14:41.580> can<00:14:41.700> wait<00:14:41.910> something<00:14:42.330> like<00:14:42.480> one<00:14:42.990> day 00:14:43.220 --> 00:14:43.230 align:start position:0% if you can wait something like one day 00:14:43.230 --> 00:14:44.420 align:start position:0% if you can wait something like one day or<00:14:43.620> I<00:14:43.860> guess 00:14:44.420 --> 00:14:44.430 align:start position:0% or I guess 00:14:44.430 --> 00:14:47.590 align:start position:0% or I guess even<00:14:44.970> less<00:14:45.150> that<00:14:46.220> should<00:14:47.220> be<00:14:47.370> really 00:14:47.590 --> 00:14:47.600 align:start position:0% even less that should be really 00:14:47.600 --> 00:14:51.940 align:start position:0% even less that should be really interesting<00:14:48.600> a<00:14:48.720> method<00:14:49.050> to<00:14:49.140> get<00:14:49.350> our<00:14:49.830> numbers 00:14:51.940 --> 00:14:51.950 align:start position:0% interesting a method to get our numbers 00:14:51.950 --> 00:14:54.019 align:start position:0% interesting a method to get our numbers the<00:14:52.950> Brazilian<00:14:53.279> nose<00:14:53.400> that<00:14:53.520> kind<00:14:53.640> of<00:14:53.730> attack 00:14:54.019 --> 00:14:54.029 align:start position:0% the Brazilian nose that kind of attack 00:14:54.029 --> 00:14:57.740 align:start position:0% the Brazilian nose that kind of attack which<00:14:54.930> would<00:14:55.110> be<00:14:55.290> an<00:14:55.890> adware<00:14:56.430> if<00:14:57.270> you<00:14:57.480> managed 00:14:57.740 --> 00:14:57.750 align:start position:0% which would be an adware if you managed 00:14:57.750 --> 00:15:00.790 align:start position:0% which would be an adware if you managed to<00:14:57.779> get<00:14:57.990> an<00:14:58.140> ad<00:14:58.260> were<00:14:58.500> able<00:14:59.370> to<00:14:59.400> compute<00:15:00.029> ashes 00:15:00.790 --> 00:15:00.800 align:start position:0% to get an ad were able to compute ashes 00:15:00.800 --> 00:15:03.680 align:start position:0% to get an ad were able to compute ashes order<00:15:01.800> of<00:15:01.890> magnitude<00:15:02.400> faster<00:15:02.550> than<00:15:03.390> the<00:15:03.510> other 00:15:03.680 --> 00:15:03.690 align:start position:0% order of magnitude faster than the other 00:15:03.690 --> 00:15:08.210 align:start position:0% order of magnitude faster than the other way<00:15:03.870> of<00:15:04.110> hosers<00:15:04.620> you<00:15:05.610> could<00:15:05.880> compute<00:15:06.750> it<00:15:07.220> super 00:15:08.210 --> 00:15:08.220 align:start position:0% way of hosers you could compute it super 00:15:08.220 --> 00:15:11.660 align:start position:0% way of hosers you could compute it super fast<00:15:08.400> and<00:15:09.350> know<00:15:10.350> what<00:15:10.980> the<00:15:11.100> number<00:15:11.339> will<00:15:11.490> be 00:15:11.660 --> 00:15:11.670 align:start position:0% fast and know what the number will be 00:15:11.670 --> 00:15:19.360 align:start position:0% fast and know what the number will be and<00:15:11.970> its<00:15:12.630> way<00:15:12.810> to<00:15:12.870> a<00:15:13.080> block<00:15:13.320> cache<00:15:13.470> attack<00:15:17.990> so 00:15:19.360 --> 00:15:19.370 align:start position:0% and its way to a block cache attack so 00:15:19.370 --> 00:15:23.690 align:start position:0% and its way to a block cache attack so thanks<00:15:20.370> everyone<00:15:20.880> and<00:15:21.380> if<00:15:22.380> you<00:15:22.620> have<00:15:23.040> a<00:15:23.070> other 00:15:23.690 --> 00:15:23.700 align:start position:0% thanks everyone and if you have a other 00:15:23.700 --> 00:15:27.230 align:start position:0% thanks everyone and if you have a other question<00:15:24.210> or<00:15:24.570> inside<00:15:25.260> feel<00:15:26.160> free<00:15:26.339> to<00:15:26.370> speak 00:15:27.230 --> 00:15:27.240 align:start position:0% question or inside feel free to speak 00:15:27.240 --> 00:15:31.170 align:start position:0% question or inside feel free to speak with<00:15:27.420> me<00:15:27.570> as<00:15:27.810> well<00:15:27.990> there<00:15:28.470> or<00:15:28.680> by<00:15:29.520> email 00:15:31.170 --> 00:15:31.180 align:start position:0% with me as well there or by email 00:15:31.180 --> 00:15:36.750 align:start position:0% with me as well there or by email [Applause] 00:15:36.750 --> 00:15:36.760 align:start position:0% 00:15:36.760 --> 00:15:37.460 align:start position:0% you 00:15:37.460 --> 00:15:37.470 align:start position:0% you 00:15:37.470 --> 00:15:45.059 align:start position:0% you [Music]