WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:14.120 align:start position:0% [Applause] 00:00:14.120 --> 00:00:14.130 align:start position:0% 00:00:14.130 --> 00:00:18.120 align:start position:0% or<00:00:15.130> adults<00:00:15.960> we<00:00:16.960> are 00:00:18.120 --> 00:00:18.130 align:start position:0% or adults we are 00:00:18.130 --> 00:00:22.050 align:start position:0% or adults we are Gorka<00:00:18.610> Damania<00:00:19.300> we<00:00:20.050> work<00:00:20.350> for<00:00:20.860> time<00:00:21.700> relax 00:00:22.050 --> 00:00:22.060 align:start position:0% Gorka Damania we work for time relax 00:00:22.060 --> 00:00:25.679 align:start position:0% Gorka Damania we work for time relax which<00:00:22.420> is<00:00:22.600> a<00:00:22.720> company<00:00:23.580> and<00:00:24.580> commissions<00:00:25.420> by 00:00:25.679 --> 00:00:25.689 align:start position:0% which is a company and commissions by 00:00:25.689 --> 00:00:27.269 align:start position:0% which is a company and commissions by and<00:00:26.140> we<00:00:26.230> met<00:00:26.380> Foundation<00:00:26.830> Florida 00:00:27.269 --> 00:00:27.279 align:start position:0% and we met Foundation Florida 00:00:27.279 --> 00:00:29.460 align:start position:0% and we met Foundation Florida development<00:00:27.759> and<00:00:28.090> implementation<00:00:28.960> of<00:00:29.410> the 00:00:29.460 --> 00:00:29.470 align:start position:0% development and implementation of the 00:00:29.470 --> 00:00:33.930 align:start position:0% development and implementation of the first<00:00:31.860> they<00:00:32.860> tell<00:00:33.010> they<00:00:33.220> open<00:00:33.490> them<00:00:33.610> for<00:00:33.790> our 00:00:33.930 --> 00:00:33.940 align:start position:0% first they tell they open them for our 00:00:33.940 --> 00:00:40.050 align:start position:0% first they tell they open them for our whole<00:00:35.520> objectives<00:00:36.520> of<00:00:36.850> these<00:00:38.100> session<00:00:39.100> which 00:00:40.050 --> 00:00:40.060 align:start position:0% whole objectives of these session which 00:00:40.060 --> 00:00:43.439 align:start position:0% whole objectives of these session which is<00:00:40.210> that<00:00:40.510> storm<00:00:40.900> oh<00:00:42.090> sure 00:00:43.439 --> 00:00:43.449 align:start position:0% is that storm oh sure 00:00:43.449 --> 00:00:47.760 align:start position:0% is that storm oh sure Adrianna<00:00:44.039> took<00:00:45.039> and<00:00:45.480> workshop<00:00:46.480> arm<00:00:47.230> and 00:00:47.760 --> 00:00:47.770 align:start position:0% Adrianna took and workshop arm and 00:00:47.770 --> 00:00:49.619 align:start position:0% Adrianna took and workshop arm and understand<00:00:48.129> look<00:00:48.609> decent<00:00:48.910> electrical 00:00:49.619 --> 00:00:49.629 align:start position:0% understand look decent electrical 00:00:49.629 --> 00:00:52.439 align:start position:0% understand look decent electrical networks<00:00:50.019> are<00:00:50.469> what's<00:00:51.100> their<00:00:51.399> used<00:00:51.640> white<00:00:52.059> we 00:00:52.439 --> 00:00:52.449 align:start position:0% networks are what's their used white we 00:00:52.449 --> 00:00:53.520 align:start position:0% networks are what's their used white we need<00:00:52.629> them 00:00:53.520 --> 00:00:53.530 align:start position:0% need them 00:00:53.530 --> 00:00:56.459 align:start position:0% need them it<00:00:53.949> you<00:00:54.100> know<00:00:54.250> radon<00:00:54.850> and<00:00:55.030> why<00:00:55.840> do<00:00:55.899> you<00:00:56.050> design 00:00:56.459 --> 00:00:56.469 align:start position:0% it you know radon and why do you design 00:00:56.469 --> 00:01:00.540 align:start position:0% it you know radon and why do you design and<00:00:56.800> as<00:00:57.160> it<00:00:57.609> is<00:00:57.730> today<00:00:58.420> and<00:00:59.199> then<00:00:59.410> how<00:00:59.769> we<00:01:00.340> met 00:01:00.540 --> 00:01:00.550 align:start position:0% and as it is today and then how we met 00:01:00.550 --> 00:01:04.710 align:start position:0% and as it is today and then how we met excusing<00:01:01.120> Reina<00:01:01.769> we<00:01:02.769> will<00:01:03.010> show<00:01:03.579> and<00:01:04.120> how<00:01:04.570> it 00:01:04.710 --> 00:01:04.720 align:start position:0% excusing Reina we will show and how it 00:01:04.720 --> 00:01:11.550 align:start position:0% excusing Reina we will show and how it works<00:01:04.960> in<00:01:05.710> real<00:01:05.740> life<00:01:07.620> and<00:01:08.620> you<00:01:10.200> what<00:01:11.200> we're 00:01:11.550 --> 00:01:11.560 align:start position:0% works in real life and you what we're 00:01:11.560 --> 00:01:15.179 align:start position:0% works in real life and you what we're working<00:01:12.070> we<00:01:12.880> were<00:01:13.120> moving<00:01:13.810> human<00:01:14.619> next<00:01:15.009> and 00:01:15.179 --> 00:01:15.189 align:start position:0% working we were moving human next and 00:01:15.189 --> 00:01:17.310 align:start position:0% working we were moving human next and what<00:01:15.369> the<00:01:15.520> future<00:01:15.939> or<00:01:16.479> a<00:01:16.659> dozen<00:01:16.869> women 00:01:17.310 --> 00:01:17.320 align:start position:0% what the future or a dozen women 00:01:17.320 --> 00:01:24.240 align:start position:0% what the future or a dozen women tomorrow's<00:01:19.170> so<00:01:20.170> on<00:01:20.920> the<00:01:21.100> centralized<00:01:21.549> or<00:01:23.250> you 00:01:24.240 --> 00:01:24.250 align:start position:0% tomorrow's so on the centralized or you 00:01:24.250 --> 00:01:25.910 align:start position:0% tomorrow's so on the centralized or you know<00:01:24.369> you're<00:01:24.729> the<00:01:24.909> problem 00:01:25.910 --> 00:01:25.920 align:start position:0% know you're the problem 00:01:25.920 --> 00:01:29.550 align:start position:0% know you're the problem 22<00:01:26.920> is<00:01:26.979> playing<00:01:27.220> that<00:01:27.369> anymore<00:01:28.560> probably 00:01:29.550 --> 00:01:29.560 align:start position:0% 22 is playing that anymore probably 00:01:29.560 --> 00:01:34.050 align:start position:0% 22 is playing that anymore probably every<00:01:30.189> every<00:01:30.640> single<00:01:31.860> people<00:01:32.860> here<00:01:33.220> already 00:01:34.050 --> 00:01:34.060 align:start position:0% every every single people here already 00:01:34.060 --> 00:01:37.590 align:start position:0% every every single people here already very<00:01:34.600> little<00:01:34.750> doubt<00:01:35.020> about<00:01:35.200> it<00:01:36.270> okay<00:01:37.270> it's 00:01:37.590 --> 00:01:37.600 align:start position:0% very little doubt about it okay it's 00:01:37.600 --> 00:01:40.560 align:start position:0% very little doubt about it okay it's it's<00:01:38.290> yes<00:01:38.950> mom<00:01:39.250> and<00:01:39.399> em<00:01:39.570> amassing 00:01:40.560 --> 00:01:40.570 align:start position:0% it's yes mom and em amassing 00:01:40.570 --> 00:01:43.050 align:start position:0% it's yes mom and em amassing mean<00:01:40.719> and<00:01:41.079> it's<00:01:41.860> not<00:01:42.130> formal<00:01:42.369> Isis<00:01:42.820> and<00:01:42.939> it's 00:01:43.050 --> 00:01:43.060 align:start position:0% mean and it's not formal Isis and it's 00:01:43.060 --> 00:01:45.179 align:start position:0% mean and it's not formal Isis and it's not<00:01:43.270> a<00:01:43.299> problem<00:01:43.570> that<00:01:43.750> anyone<00:01:44.619> has<00:01:44.829> defined 00:01:45.179 --> 00:01:45.189 align:start position:0% not a problem that anyone has defined 00:01:45.189 --> 00:01:47.520 align:start position:0% not a problem that anyone has defined its<00:01:45.399> death<00:01:45.640> marketing<00:01:46.360> so<00:01:46.840> what<00:01:47.110> you're 00:01:47.520 --> 00:01:47.530 align:start position:0% its death marketing so what you're 00:01:47.530 --> 00:01:49.950 align:start position:0% its death marketing so what you're talking<00:01:48.430> about<00:01:48.460> increasing<00:01:49.210> terrible 00:01:49.950 --> 00:01:49.960 align:start position:0% talking about increasing terrible 00:01:49.960 --> 00:01:51.359 align:start position:0% talking about increasing terrible problem<00:01:50.320> here 00:01:51.359 --> 00:01:51.369 align:start position:0% problem here 00:01:51.369 --> 00:01:54.459 align:start position:0% problem here that<00:01:52.369> the<00:01:52.789> fact<00:01:53.090> that<00:01:53.240> because<00:01:53.990> the<00:01:54.200> smart 00:01:54.459 --> 00:01:54.469 align:start position:0% that the fact that because the smart 00:01:54.469 --> 00:01:56.649 align:start position:0% that the fact that because the smart contracts<00:01:54.890> between<00:01:55.070> deterministic<00:01:56.060> we<00:01:56.450> can 00:01:56.649 --> 00:01:56.659 align:start position:0% contracts between deterministic we can 00:01:56.659 --> 00:01:59.529 align:start position:0% contracts between deterministic we can not<00:01:56.899> very<00:01:57.289> external<00:01:58.189> API<00:01:58.460> server<00:01:59.119> to<00:01:59.329> many 00:01:59.529 --> 00:01:59.539 align:start position:0% not very external API server to many 00:01:59.539 --> 00:02:02.289 align:start position:0% not very external API server to many kind<00:02:00.500> of<00:02:00.619> planet<00:02:01.219> whose<00:02:01.520> non-deterministic 00:02:02.289 --> 00:02:02.299 align:start position:0% kind of planet whose non-deterministic 00:02:02.299 --> 00:02:04.330 align:start position:0% kind of planet whose non-deterministic thing<00:02:02.750> that<00:02:02.929> communion<00:02:03.530> the<00:02:03.649> smart<00:02:03.890> contracts 00:02:04.330 --> 00:02:04.340 align:start position:0% thing that communion the smart contracts 00:02:04.340 --> 00:02:08.309 align:start position:0% thing that communion the smart contracts so<00:02:04.880> we<00:02:05.179> need<00:02:05.299> to<00:02:05.659> do<00:02:05.780> some<00:02:06.079> way<00:02:06.350> to<00:02:06.409> solve 00:02:08.309 --> 00:02:08.319 align:start position:0% so we need to do some way to solve 00:02:08.319 --> 00:02:10.419 align:start position:0% so we need to do some way to solve resolving<00:02:09.319> that<00:02:09.649> kind<00:02:09.979> of<00:02:10.099> in<00:02:10.340> the 00:02:10.419 --> 00:02:10.429 align:start position:0% resolving that kind of in the 00:02:10.429 --> 00:02:12.460 align:start position:0% resolving that kind of in the determination<00:02:10.940> of<00:02:11.060> that<00:02:11.120> arises<00:02:11.510> from<00:02:11.780> having 00:02:12.460 --> 00:02:12.470 align:start position:0% determination of that arises from having 00:02:12.470 --> 00:02:14.680 align:start position:0% determination of that arises from having some<00:02:12.739> computation<00:02:13.340> being<00:02:13.970> performed<00:02:14.450> on 00:02:14.680 --> 00:02:14.690 align:start position:0% some computation being performed on 00:02:14.690 --> 00:02:17.080 align:start position:0% some computation being performed on multiple<00:02:15.290> amounts<00:02:15.650> of<00:02:15.769> a<00:02:15.890> network<00:02:16.280> or<00:02:16.489> in<00:02:16.940> all 00:02:17.080 --> 00:02:17.090 align:start position:0% multiple amounts of a network or in all 00:02:17.090 --> 00:02:18.759 align:start position:0% multiple amounts of a network or in all the<00:02:17.209> nodes<00:02:17.390> in<00:02:17.540> a<00:02:17.629> network<00:02:17.660> like<00:02:18.170> is<00:02:18.349> the<00:02:18.560> case 00:02:18.759 --> 00:02:18.769 align:start position:0% the nodes in a network like is the case 00:02:18.769 --> 00:02:23.110 align:start position:0% the nodes in a network like is the case or<00:02:19.099> is<00:02:19.250> my<00:02:19.430> progress<00:02:19.670> in<00:02:20.260> etherium<00:02:21.260> and<00:02:21.879> at<00:02:22.879> the 00:02:23.110 --> 00:02:23.120 align:start position:0% or is my progress in etherium and at the 00:02:23.120 --> 00:02:26.380 align:start position:0% or is my progress in etherium and at the end<00:02:23.239> of<00:02:23.299> the<00:02:23.450> day<00:02:24.099> if<00:02:25.099> we<00:02:25.160> try<00:02:25.640> to<00:02:25.670> solve<00:02:26.120> that 00:02:26.380 --> 00:02:26.390 align:start position:0% end of the day if we try to solve that 00:02:26.390 --> 00:02:28.210 align:start position:0% end of the day if we try to solve that through<00:02:26.840> centralized<00:02:27.560> data<00:02:27.829> it<00:02:28.040> will 00:02:28.210 --> 00:02:28.220 align:start position:0% through centralized data it will 00:02:28.220 --> 00:02:32.170 align:start position:0% through centralized data it will basically<00:02:28.549> but<00:02:29.060> having<00:02:29.450> a<00:02:30.010> contract<00:02:31.010> have<00:02:31.970> an 00:02:32.170 --> 00:02:32.180 align:start position:0% basically but having a contract have an 00:02:32.180 --> 00:02:36.479 align:start position:0% basically but having a contract have an owner<00:02:32.630> that<00:02:33.049> can<00:02:33.290> all<00:02:34.280> ragged<00:02:35.269> met<00:02:35.450> on<00:02:35.660> that 00:02:36.479 --> 00:02:36.489 align:start position:0% owner that can all ragged met on that 00:02:36.489 --> 00:02:39.190 align:start position:0% owner that can all ragged met on that method<00:02:37.489> that<00:02:37.819> has<00:02:38.000> multiplier<00:02:38.450> so<00:02:38.810> that<00:02:38.989> only 00:02:39.190 --> 00:02:39.200 align:start position:0% method that has multiplier so that only 00:02:39.200 --> 00:02:42.539 align:start position:0% method that has multiplier so that only owner<00:02:39.709> can<00:02:40.670> input<00:02:41.090> data<00:02:41.150> we<00:02:41.780> are<00:02:41.870> breaking 00:02:42.539 --> 00:02:42.549 align:start position:0% owner can input data we are breaking 00:02:42.549 --> 00:02:45.460 align:start position:0% owner can input data we are breaking tampering<00:02:43.549> censorship<00:02:44.329> resistant<00:02:44.989> which<00:02:45.290> is 00:02:45.460 --> 00:02:45.470 align:start position:0% tampering censorship resistant which is 00:02:45.470 --> 00:02:48.880 align:start position:0% tampering censorship resistant which is a<00:02:45.849> the<00:02:46.849> goal<00:02:47.030> of<00:02:47.329> using<00:02:47.780> a<00:02:47.810> smart<00:02:48.290> contract<00:02:48.470> in 00:02:48.880 --> 00:02:48.890 align:start position:0% a the goal of using a smart contract in 00:02:48.890 --> 00:02:53.440 align:start position:0% a the goal of using a smart contract in with<00:02:49.430> Ruby<00:02:50.000> and<00:02:50.239> in<00:02:50.959> the<00:02:51.379> purpose<00:02:52.060> so<00:02:53.060> the 00:02:53.440 --> 00:02:53.450 align:start position:0% with Ruby and in the purpose so the 00:02:53.450 --> 00:02:54.460 align:start position:0% with Ruby and in the purpose so the question<00:02:53.840> is<00:02:53.930> how<00:02:54.140> do<00:02:54.200> you<00:02:54.290> build 00:02:54.460 --> 00:02:54.470 align:start position:0% question is how do you build 00:02:54.470 --> 00:02:56.559 align:start position:0% question is how do you build determination<00:02:55.160> without<00:02:55.569> centralization 00:02:56.559 --> 00:02:56.569 align:start position:0% determination without centralization 00:02:56.569 --> 00:02:58.900 align:start position:0% determination without centralization that's<00:02:56.750> that's<00:02:57.049> a<00:02:57.170> problem<00:02:57.500> that<00:02:57.709> we're<00:02:58.190> that 00:02:58.900 --> 00:02:58.910 align:start position:0% that's that's a problem that we're that 00:02:58.910 --> 00:03:01.449 align:start position:0% that's that's a problem that we're that we've<00:02:59.090> been<00:02:59.239> trying<00:03:00.200> to<00:03:00.290> solve<00:03:00.500> so<00:03:00.859> we<00:03:01.400> came 00:03:01.449 --> 00:03:01.459 align:start position:0% we've been trying to solve so we came 00:03:01.459 --> 00:03:03.430 align:start position:0% we've been trying to solve so we came with<00:03:01.940> the<00:03:02.120> concept<00:03:02.510> of<00:03:02.600> a<00:03:02.750> decentralized 00:03:03.430 --> 00:03:03.440 align:start position:0% with the concept of a decentralized 00:03:03.440 --> 00:03:05.349 align:start position:0% with the concept of a decentralized oracle<00:03:03.709> Network<00:03:04.340> where<00:03:04.730> this<00:03:04.940> centralized 00:03:05.349 --> 00:03:05.359 align:start position:0% oracle Network where this centralized 00:03:05.359 --> 00:03:08.590 align:start position:0% oracle Network where this centralized means<00:03:05.660> that<00:03:05.959> basically<00:03:06.530> it's<00:03:07.040> 10%<00:03:07.370> exists<00:03:08.359> and 00:03:08.590 --> 00:03:08.600 align:start position:0% means that basically it's 10% exists and 00:03:08.600 --> 00:03:11.349 align:start position:0% means that basically it's 10% exists and no<00:03:08.720> one<00:03:08.930> can<00:03:09.170> decide<00:03:09.950> with<00:03:10.280> will<00:03:10.519> watch<00:03:10.940> which 00:03:11.349 --> 00:03:11.359 align:start position:0% no one can decide with will watch which 00:03:11.359 --> 00:03:14.699 align:start position:0% no one can decide with will watch which will<00:03:11.600> be<00:03:11.750> the<00:03:12.049> result<00:03:12.440> of<00:03:12.709> the<00:03:13.130> contract 00:03:14.699 --> 00:03:14.709 align:start position:0% will be the result of the contract 00:03:14.709 --> 00:03:16.900 align:start position:0% will be the result of the contract decentralization<00:03:15.709> is<00:03:15.980> just<00:03:16.220> a<00:03:16.340> way<00:03:16.519> to<00:03:16.579> arrive 00:03:16.900 --> 00:03:16.910 align:start position:0% decentralization is just a way to arrive 00:03:16.910 --> 00:03:20.379 align:start position:0% decentralization is just a way to arrive to<00:03:17.090> that<00:03:17.269> madness<00:03:18.079> with<00:03:18.560> you<00:03:18.709> know<00:03:18.829> an<00:03:19.389> Oracle 00:03:20.379 --> 00:03:20.389 align:start position:0% to that madness with you know an Oracle 00:03:20.389 --> 00:03:23.199 align:start position:0% to that madness with you know an Oracle here<00:03:20.630> means<00:03:21.230> that<00:03:21.560> there<00:03:22.130> are<00:03:22.160> some<00:03:22.370> negative 00:03:23.199 --> 00:03:23.209 align:start position:0% here means that there are some negative 00:03:23.209 --> 00:03:24.880 align:start position:0% here means that there are some negative laning 00:03:24.880 --> 00:03:24.890 align:start position:0% laning 00:03:24.890 --> 00:03:29.050 align:start position:0% laning to<00:03:25.370> the<00:03:25.760> contracts<00:03:26.680> and<00:03:27.680> most<00:03:28.220> importantly 00:03:29.050 --> 00:03:29.060 align:start position:0% to the contracts and most importantly 00:03:29.060 --> 00:03:32.430 align:start position:0% to the contracts and most importantly an<00:03:29.780> inter<00:03:30.110> minor<00:03:30.320> basically<00:03:31.040> an<00:03:31.850> entity<00:03:32.330> that 00:03:32.430 --> 00:03:32.440 align:start position:0% an inter minor basically an entity that 00:03:32.440 --> 00:03:36.520 align:start position:0% an inter minor basically an entity that express<00:03:33.440> away<00:03:33.800> the<00:03:35.140> uncertainty<00:03:36.140> that<00:03:36.170> comes 00:03:36.520 --> 00:03:36.530 align:start position:0% express away the uncertainty that comes 00:03:36.530 --> 00:03:40.380 align:start position:0% express away the uncertainty that comes from<00:03:36.830> making<00:03:37.340> an<00:03:37.750> HTTP<00:03:38.750> query<00:03:38.960> where<00:03:39.380> you<00:03:39.650> can 00:03:40.380 --> 00:03:40.390 align:start position:0% from making an HTTP query where you can 00:03:40.390 --> 00:03:42.850 align:start position:0% from making an HTTP query where you can have<00:03:41.390> many<00:03:41.720> many<00:03:42.260> different<00:03:42.410> terrorist 00:03:42.850 --> 00:03:42.860 align:start position:0% have many many different terrorist 00:03:42.860 --> 00:03:44.140 align:start position:0% have many many different terrorist network<00:03:43.490> errors 00:03:44.140 --> 00:03:44.150 align:start position:0% network errors 00:03:44.150 --> 00:03:47.440 align:start position:0% network errors many<00:03:44.810> different<00:03:45.680> situations<00:03:46.450> comparing 00:03:47.440 --> 00:03:47.450 align:start position:0% many different situations comparing 00:03:47.450 --> 00:03:49.690 align:start position:0% many different situations comparing multiple<00:03:47.570> api's<00:03:48.350> for<00:03:48.650> the<00:03:48.800> Scimitar<00:03:49.310> for<00:03:49.580> the 00:03:49.690 --> 00:03:49.700 align:start position:0% multiple api's for the Scimitar for the 00:03:49.700 --> 00:03:52.870 align:start position:0% multiple api's for the Scimitar for the same<00:03:50.420> data<00:03:50.720> how<00:03:51.470> do<00:03:51.530> you<00:03:51.770> solve<00:03:52.010> the<00:03:52.490> fact<00:03:52.790> that 00:03:52.870 --> 00:03:52.880 align:start position:0% same data how do you solve the fact that 00:03:52.880 --> 00:03:56.710 align:start position:0% same data how do you solve the fact that they<00:03:53.300> could<00:03:53.810> be<00:03:54.080> different<00:03:54.920> and<00:03:55.640> so<00:03:56.240> on<00:03:56.480> that's 00:03:56.710 --> 00:03:56.720 align:start position:0% they could be different and so on that's 00:03:56.720 --> 00:03:58.630 align:start position:0% they could be different and so on that's that<00:03:57.020> fail<00:03:57.260> you<00:03:57.290> have<00:03:57.470> the<00:03:57.740> Oracle<00:03:58.250> and<00:03:58.490> the 00:03:58.630 --> 00:03:58.640 align:start position:0% that fail you have the Oracle and the 00:03:58.640 --> 00:04:01.930 align:start position:0% that fail you have the Oracle and the networking<00:03:59.140> means<00:04:00.140> that<00:04:00.500> there's<00:04:01.220> some<00:04:01.610> full 00:04:01.930 --> 00:04:01.940 align:start position:0% networking means that there's some full 00:04:01.940 --> 00:04:07.290 align:start position:0% networking means that there's some full of<00:04:02.240> notes<00:04:03.080> that<00:04:03.440> are<00:04:04.010> randomly<00:04:04.880> selected<00:04:05.740> for 00:04:07.290 --> 00:04:07.300 align:start position:0% of notes that are randomly selected for 00:04:07.300 --> 00:04:11.380 align:start position:0% of notes that are randomly selected for making<00:04:08.300> this<00:04:08.780> work<00:04:09.380> of<00:04:10.180> aggregating<00:04:11.180> and 00:04:11.380 --> 00:04:11.390 align:start position:0% making this work of aggregating and 00:04:11.390 --> 00:04:16.890 align:start position:0% making this work of aggregating and delivering<00:04:12.380> data<00:04:12.560> into<00:04:13.430> smartphones<00:04:13.840> okay<00:04:14.840> so 00:04:16.890 --> 00:04:16.900 align:start position:0% delivering data into smartphones okay so 00:04:16.900 --> 00:04:19.750 align:start position:0% delivering data into smartphones okay so this<00:04:17.900> centralized<00:04:18.320> data<00:04:18.560> networks<00:04:19.010> should<00:04:19.549> be 00:04:19.750 --> 00:04:19.760 align:start position:0% this centralized data networks should be 00:04:19.760 --> 00:04:22.720 align:start position:0% this centralized data networks should be about<00:04:20.299> speaking<00:04:20.870> power<00:04:21.170> so<00:04:21.950> as<00:04:22.220> meeting<00:04:22.580> and 00:04:22.720 --> 00:04:22.730 align:start position:0% about speaking power so as meeting and 00:04:22.730 --> 00:04:26.680 align:start position:0% about speaking power so as meeting and Trust<00:04:22.970> in<00:04:23.270> in<00:04:23.690> a<00:04:24.010> single<00:04:25.010> know<00:04:25.640> any<00:04:25.880> particular 00:04:26.680 --> 00:04:26.690 align:start position:0% Trust in in a single know any particular 00:04:26.690 --> 00:04:31.990 align:start position:0% Trust in in a single know any particular person<00:04:27.080> so<00:04:27.980> as<00:04:28.550> to<00:04:28.820> not<00:04:29.330> have<00:04:30.250> a<00:04:31.250> point<00:04:31.850> of 00:04:31.990 --> 00:04:32.000 align:start position:0% person so as to not have a point of 00:04:32.000 --> 00:04:37.390 align:start position:0% person so as to not have a point of failure<00:04:32.210> so<00:04:34.390> when<00:04:35.390> we<00:04:35.600> thought<00:04:36.110> that<00:04:36.650> we 00:04:37.390 --> 00:04:37.400 align:start position:0% failure so when we thought that we 00:04:37.400 --> 00:04:42.520 align:start position:0% failure so when we thought that we needed<00:04:37.430> to<00:04:38.170> find<00:04:39.170> a<00:04:39.410> way<00:04:39.560> to<00:04:40.510> have<00:04:41.510> a<00:04:41.540> DSL<00:04:42.200> for 00:04:42.520 --> 00:04:42.530 align:start position:0% needed to find a way to have a DSL for 00:04:42.530 --> 00:04:44.950 align:start position:0% needed to find a way to have a DSL for articles<00:04:43.190> why<00:04:43.670> why<00:04:44.090> are<00:04:44.300> programming 00:04:44.950 --> 00:04:44.960 align:start position:0% articles why why are programming 00:04:44.960 --> 00:04:48.520 align:start position:0% articles why why are programming languages<00:04:45.410> that<00:04:45.950> exist<00:04:46.520> today<00:04:46.850> not<00:04:47.360> enough<00:04:48.140> or 00:04:48.520 --> 00:04:48.530 align:start position:0% languages that exist today not enough or 00:04:48.530 --> 00:04:52.570 align:start position:0% languages that exist today not enough or something<00:04:49.190> like<00:04:49.610> a<00:04:49.640> decent<00:04:49.940> wise<00:04:50.330> work<00:04:50.540> so<00:04:51.580> if 00:04:52.570 --> 00:04:52.580 align:start position:0% something like a decent wise work so if 00:04:52.580 --> 00:04:55.090 align:start position:0% something like a decent wise work so if we<00:04:52.760> want<00:04:53.030> to<00:04:53.090> build<00:04:53.330> determinism<00:04:54.320> I<00:04:54.560> will 00:04:55.090 --> 00:04:55.100 align:start position:0% we want to build determinism I will 00:04:55.100 --> 00:04:58.900 align:start position:0% we want to build determinism I will require<00:04:55.490> explicitness<00:04:56.480> so<00:04:57.220> the<00:04:58.220> code<00:04:58.520> needs 00:04:58.900 --> 00:04:58.910 align:start position:0% require explicitness so the code needs 00:04:58.910 --> 00:05:02.170 align:start position:0% require explicitness so the code needs to<00:04:59.210> be<00:05:00.020> really<00:05:00.860> really<00:05:01.040> clear<00:05:01.370> about<00:05:01.940> the 00:05:02.170 --> 00:05:02.180 align:start position:0% to be really really clear about the 00:05:02.180 --> 00:05:05.200 align:start position:0% to be really really clear about the invention<00:05:02.930> of<00:05:03.170> the<00:05:03.740> of<00:05:04.130> the<00:05:04.280> requests<00:05:04.820> of<00:05:04.970> the 00:05:05.200 --> 00:05:05.210 align:start position:0% invention of the of the requests of the 00:05:05.210 --> 00:05:07.330 align:start position:0% invention of the of the requests of the big<00:05:05.420> of<00:05:05.570> the<00:05:05.600> bigger<00:05:06.080> requests<00:05:06.919> we<00:05:07.190> are 00:05:07.330 --> 00:05:07.340 align:start position:0% big of the bigger requests we are 00:05:07.340 --> 00:05:11.620 align:start position:0% big of the bigger requests we are performing<00:05:08.240> we<00:05:09.020> don't<00:05:09.350> want<00:05:09.620> and<00:05:10.120> any<00:05:11.120> imbuing 00:05:11.620 --> 00:05:11.630 align:start position:0% performing we don't want and any imbuing 00:05:11.630 --> 00:05:16.240 align:start position:0% performing we don't want and any imbuing but<00:05:12.700> of<00:05:13.700> course<00:05:14.000> the<00:05:14.660> human<00:05:15.169> languages<00:05:15.530> bit<00:05:16.070> of 00:05:16.240 --> 00:05:16.250 align:start position:0% but of course the human languages bit of 00:05:16.250 --> 00:05:18.110 align:start position:0% but of course the human languages bit of work<00:05:16.580> we<00:05:17.000> cannot<00:05:17.330> use 00:05:18.110 --> 00:05:18.120 align:start position:0% work we cannot use 00:05:18.120 --> 00:05:22.390 align:start position:0% work we cannot use two<00:05:18.210> languages<00:05:18.720> or<00:05:19.460> saying<00:05:20.460> I<00:05:20.760> want<00:05:21.120> to<00:05:21.180> know 00:05:22.390 --> 00:05:22.400 align:start position:0% two languages or saying I want to know 00:05:22.400 --> 00:05:25.879 align:start position:0% two languages or saying I want to know the<00:05:23.400> price<00:05:23.669> of<00:05:23.729> these<00:05:24.300> women<00:05:25.290> were<00:05:25.410> too<00:05:25.620> busy 00:05:25.879 --> 00:05:25.889 align:start position:0% the price of these women were too busy 00:05:25.889 --> 00:05:30.350 align:start position:0% the price of these women were too busy or<00:05:26.550> I<00:05:27.120> mean<00:05:27.570> in<00:05:27.750> my<00:05:27.990> contract<00:05:28.410> to<00:05:28.979> know<00:05:29.360> about 00:05:30.350 --> 00:05:30.360 align:start position:0% or I mean in my contract to know about 00:05:30.360 --> 00:05:32.330 align:start position:0% or I mean in my contract to know about the<00:05:30.690> temperature<00:05:31.080> in<00:05:31.260> second<00:05:31.650> tomorrow<00:05:31.979> and 00:05:32.330 --> 00:05:32.340 align:start position:0% the temperature in second tomorrow and 00:05:32.340 --> 00:05:35.270 align:start position:0% the temperature in second tomorrow and so<00:05:32.490> on<00:05:32.840> and<00:05:33.840> most<00:05:34.110> programming<00:05:34.560> languages<00:05:34.889> are 00:05:35.270 --> 00:05:35.280 align:start position:0% so on and most programming languages are 00:05:35.280 --> 00:05:38.120 align:start position:0% so on and most programming languages are also<00:05:35.820> not<00:05:36.360> suitable<00:05:36.810> because<00:05:36.870> they<00:05:37.320> are<00:05:37.650> to 00:05:38.120 --> 00:05:38.130 align:start position:0% also not suitable because they are to 00:05:38.130 --> 00:05:41.270 align:start position:0% also not suitable because they are to reach<00:05:38.790> in<00:05:39.150> their<00:05:39.800> comfort<00:05:40.800> floor<00:05:40.979> lowest 00:05:41.270 --> 00:05:41.280 align:start position:0% reach in their comfort floor lowest 00:05:41.280 --> 00:05:43.430 align:start position:0% reach in their comfort floor lowest cultures<00:05:41.699> so<00:05:42.060> imagine<00:05:42.510> for<00:05:42.540> example<00:05:42.690> solidity 00:05:43.430 --> 00:05:43.440 align:start position:0% cultures so imagine for example solidity 00:05:43.440 --> 00:05:45.800 align:start position:0% cultures so imagine for example solidity it<00:05:43.949> allows<00:05:44.250> you<00:05:44.460> to<00:05:44.610> do<00:05:44.729> looping<00:05:45.210> and<00:05:45.540> many 00:05:45.800 --> 00:05:45.810 align:start position:0% it allows you to do looping and many 00:05:45.810 --> 00:05:49.159 align:start position:0% it allows you to do looping and many fancy<00:05:46.620> stuff<00:05:46.860> and<00:05:47.190> that<00:05:47.880> is<00:05:48.570> not<00:05:48.810> really 00:05:49.159 --> 00:05:49.169 align:start position:0% fancy stuff and that is not really 00:05:49.169 --> 00:05:51.700 align:start position:0% fancy stuff and that is not really required<00:05:49.530> for<00:05:49.949> the<00:05:50.370> purpose<00:05:50.789> of<00:05:51.030> simply 00:05:51.700 --> 00:05:51.710 align:start position:0% required for the purpose of simply 00:05:51.710 --> 00:05:55.939 align:start position:0% required for the purpose of simply taking<00:05:52.710> data<00:05:53.100> from<00:05:53.660> memory<00:05:54.830> transforming<00:05:55.830> in 00:05:55.939 --> 00:05:55.949 align:start position:0% taking data from memory transforming in 00:05:55.949 --> 00:05:58.580 align:start position:0% taking data from memory transforming in its<00:05:56.160> way<00:05:56.460> at<00:05:56.820> making<00:05:57.330> aggregations<00:05:58.080> million 00:05:58.580 --> 00:05:58.590 align:start position:0% its way at making aggregations million 00:05:58.590 --> 00:06:00.620 align:start position:0% its way at making aggregations million so<00:05:59.010> mister<00:05:59.310> T<00:05:59.460> is<00:05:59.760> the<00:05:59.970> visiting<00:06:00.300> some 00:06:00.620 --> 00:06:00.630 align:start position:0% so mister T is the visiting some 00:06:00.630 --> 00:06:02.210 align:start position:0% so mister T is the visiting some computations<00:06:01.289> and<00:06:01.440> then<00:06:01.590> having<00:06:02.070> it 00:06:02.210 --> 00:06:02.220 align:start position:0% computations and then having it 00:06:02.220 --> 00:06:06.740 align:start position:0% computations and then having it delivered<00:06:02.580> to<00:06:03.419> your<00:06:03.870> mother<00:06:04.650> so<00:06:05.600> we<00:06:06.600> need 00:06:06.740 --> 00:06:06.750 align:start position:0% delivered to your mother so we need 00:06:06.750 --> 00:06:08.719 align:start position:0% delivered to your mother so we need something<00:06:07.050> that<00:06:07.229> is<00:06:07.470> we<00:06:08.039> focus<00:06:08.310> on 00:06:08.719 --> 00:06:08.729 align:start position:0% something that is we focus on 00:06:08.729 --> 00:06:11.450 align:start position:0% something that is we focus on information<00:06:09.110> aggregation<00:06:10.250> something<00:06:11.250> that 00:06:11.450 --> 00:06:11.460 align:start position:0% information aggregation something that 00:06:11.460 --> 00:06:14.240 align:start position:0% information aggregation something that is<00:06:11.699> between<00:06:12.120> two<00:06:12.300> things<00:06:12.510> of<00:06:12.720> more<00:06:13.590> similarity 00:06:14.240 --> 00:06:14.250 align:start position:0% is between two things of more similarity 00:06:14.250 --> 00:06:17.260 align:start position:0% is between two things of more similarity they<00:06:14.400> are<00:06:14.639> not<00:06:14.760> the<00:06:14.940> news<00:06:15.120> for<00:06:15.389> tonight<00:06:15.539> so 00:06:17.260 --> 00:06:17.270 align:start position:0% they are not the news for tonight so 00:06:17.270 --> 00:06:21.409 align:start position:0% they are not the news for tonight so when<00:06:18.270> we<00:06:18.600> started<00:06:19.110> thinking<00:06:19.500> of<00:06:19.919> of<00:06:20.370> this<00:06:20.760> ESL 00:06:21.409 --> 00:06:21.419 align:start position:0% when we started thinking of of this ESL 00:06:21.419 --> 00:06:25.159 align:start position:0% when we started thinking of of this ESL we<00:06:21.830> realized<00:06:22.830> that<00:06:23.450> it<00:06:24.450> needed<00:06:24.900> to<00:06:25.050> be 00:06:25.159 --> 00:06:25.169 align:start position:0% we realized that it needed to be 00:06:25.169 --> 00:06:28.010 align:start position:0% we realized that it needed to be mastered<00:06:25.889> so<00:06:26.220> that<00:06:26.729> is<00:06:27.000> happening<00:06:27.750> any 00:06:28.010 --> 00:06:28.020 align:start position:0% mastered so that is happening any 00:06:28.020 --> 00:06:31.180 align:start position:0% mastered so that is happening any specific<00:06:28.650> syntax<00:06:28.950> it's<00:06:29.580> not<00:06:29.849> tied<00:06:30.450> to<00:06:30.780> any 00:06:31.180 --> 00:06:31.190 align:start position:0% specific syntax it's not tied to any 00:06:31.190 --> 00:06:34.219 align:start position:0% specific syntax it's not tied to any syntax<00:06:32.190> so<00:06:32.669> that<00:06:32.849> you<00:06:33.060> don't<00:06:33.330> need<00:06:33.539> to<00:06:33.599> learn<00:06:33.990> a 00:06:34.219 --> 00:06:34.229 align:start position:0% syntax so that you don't need to learn a 00:06:34.229 --> 00:06:39.500 align:start position:0% syntax so that you don't need to learn a new<00:06:34.260> language<00:06:34.680> that<00:06:35.669> is<00:06:35.849> that<00:06:36.680> is<00:06:38.270> simply<00:06:39.270> like 00:06:39.500 --> 00:06:39.510 align:start position:0% new language that is that is simply like 00:06:39.510 --> 00:06:43.100 align:start position:0% new language that is that is simply like a<00:06:39.539> kind<00:06:39.960> of<00:06:40.080> grammar<00:06:40.740> or<00:06:41.490> defining<00:06:42.150> data<00:06:42.660> flows 00:06:43.100 --> 00:06:43.110 align:start position:0% a kind of grammar or defining data flows 00:06:43.110 --> 00:06:47.500 align:start position:0% a kind of grammar or defining data flows and<00:06:43.470> then<00:06:44.160> you<00:06:44.550> can<00:06:44.760> have<00:06:45.060> libraries<00:06:46.020> in<00:06:46.349> your 00:06:47.500 --> 00:06:47.510 align:start position:0% and then you can have libraries in your 00:06:47.510 --> 00:06:50.450 align:start position:0% and then you can have libraries in your programming<00:06:48.510> language<00:06:48.930> that<00:06:49.770> you<00:06:50.039> like<00:06:50.250> the 00:06:50.450 --> 00:06:50.460 align:start position:0% programming language that you like the 00:06:50.460 --> 00:06:54.740 align:start position:0% programming language that you like the most<00:06:51.830> JavaScript<00:06:52.830> or<00:06:52.979> whatever<00:06:53.490> that<00:06:54.330> you<00:06:54.510> can 00:06:54.740 --> 00:06:54.750 align:start position:0% most JavaScript or whatever that you can 00:06:54.750 --> 00:06:59.300 align:start position:0% most JavaScript or whatever that you can use<00:06:55.349> the<00:06:56.250> library<00:06:56.610> support<00:06:57.240> writing<00:06:58.130> great<00:06:59.130> on 00:06:59.300 --> 00:06:59.310 align:start position:0% use the library support writing great on 00:06:59.310 --> 00:07:03.500 align:start position:0% use the library support writing great on the<00:06:59.400> space<00:06:59.669> so<00:07:00.800> it's<00:07:01.800> totally<00:07:02.310> data<00:07:03.000> oriented 00:07:03.500 --> 00:07:03.510 align:start position:0% the space so it's totally data oriented 00:07:03.510 --> 00:07:05.879 align:start position:0% the space so it's totally data oriented it<00:07:03.990> means<00:07:04.229> that 00:07:05.879 --> 00:07:05.889 align:start position:0% it means that 00:07:05.889 --> 00:07:09.469 align:start position:0% it means that at<00:07:05.949> night<00:07:06.490> and<00:07:07.300> it's<00:07:07.840> free<00:07:08.590> so<00:07:08.620> it's<00:07:09.009> a 00:07:09.469 --> 00:07:09.479 align:start position:0% at night and it's free so it's a 00:07:09.479 --> 00:07:12.659 align:start position:0% at night and it's free so it's a sequence<00:07:10.479> of<00:07:10.750> operators<00:07:11.199> and<00:07:11.710> operate<00:07:12.430> on<00:07:12.550> the 00:07:12.659 --> 00:07:12.669 align:start position:0% sequence of operators and operate on the 00:07:12.669 --> 00:07:13.800 align:start position:0% sequence of operators and operate on the result<00:07:12.969> of<00:07:13.090> the<00:07:13.210> previous<00:07:13.389> one 00:07:13.800 --> 00:07:13.810 align:start position:0% result of the previous one 00:07:13.810 --> 00:07:16.350 align:start position:0% result of the previous one and<00:07:14.080> it<00:07:14.919> needs<00:07:15.159> to<00:07:15.219> be<00:07:15.310> really<00:07:15.759> really<00:07:16.090> focused 00:07:16.350 --> 00:07:16.360 align:start position:0% and it needs to be really really focused 00:07:16.360 --> 00:07:18.540 align:start position:0% and it needs to be really really focused on<00:07:16.750> what<00:07:17.050> we<00:07:17.199> are<00:07:17.229> doing<00:07:17.319> which<00:07:17.740> is<00:07:17.770> putting 00:07:18.540 --> 00:07:18.550 align:start position:0% on what we are doing which is putting 00:07:18.550 --> 00:07:20.820 align:start position:0% on what we are doing which is putting information<00:07:18.719> transfer<00:07:19.719> minute<00:07:20.050> I<00:07:20.259> have<00:07:20.620> it 00:07:20.820 --> 00:07:20.830 align:start position:0% information transfer minute I have it 00:07:20.830 --> 00:07:24.899 align:start position:0% information transfer minute I have it deliver<00:07:21.599> this<00:07:22.599> is<00:07:23.580> probably<00:07:24.580> the<00:07:24.789> most 00:07:24.899 --> 00:07:24.909 align:start position:0% deliver this is probably the most 00:07:24.909 --> 00:07:28.409 align:start position:0% deliver this is probably the most important<00:07:25.360> part<00:07:25.979> which<00:07:26.979> is<00:07:27.039> that<00:07:27.219> you<00:07:28.030> mean<00:07:28.270> to 00:07:28.409 --> 00:07:28.419 align:start position:0% important part which is that you mean to 00:07:28.419 --> 00:07:32.339 align:start position:0% important part which is that you mean to make<00:07:28.889> me<00:07:29.889> analyst<00:07:30.430> analyst<00:07:31.150> I<00:07:31.240> guess<00:07:31.900> so<00:07:32.319> that 00:07:32.339 --> 00:07:32.349 align:start position:0% make me analyst analyst I guess so that 00:07:32.349 --> 00:07:36.600 align:start position:0% make me analyst analyst I guess so that we<00:07:33.039> can<00:07:33.310> predict<00:07:33.930> the<00:07:34.930> computing<00:07:35.610> resources 00:07:36.600 --> 00:07:36.610 align:start position:0% we can predict the computing resources 00:07:36.610 --> 00:07:38.670 align:start position:0% we can predict the computing resources that<00:07:36.789> you<00:07:36.879> will<00:07:37.300> will<00:07:37.689> be<00:07:37.840> useless<00:07:38.020> to<00:07:38.259> us<00:07:38.409> to 00:07:38.670 --> 00:07:38.680 align:start position:0% that you will will be useless to us to 00:07:38.680 --> 00:07:41.969 align:start position:0% that you will will be useless to us to set<00:07:39.219> some<00:07:39.460> kind<00:07:39.639> of<00:07:40.020> price<00:07:41.020> model<00:07:41.229> it's 00:07:41.969 --> 00:07:41.979 align:start position:0% set some kind of price model it's 00:07:41.979 --> 00:07:44.149 align:start position:0% set some kind of price model it's similar<00:07:42.099> to<00:07:42.250> to<00:07:42.969> Casper<00:07:43.449> something<00:07:43.750> like<00:07:43.870> that 00:07:44.149 --> 00:07:44.159 align:start position:0% similar to to Casper something like that 00:07:44.159 --> 00:07:48.899 align:start position:0% similar to to Casper something like that and<00:07:45.159> you<00:07:45.430> also<00:07:45.759> to<00:07:46.090> detect<00:07:46.479> any<00:07:46.779> kind<00:07:47.199> of<00:07:47.909> wrong 00:07:48.899 --> 00:07:48.909 align:start position:0% and you also to detect any kind of wrong 00:07:48.909 --> 00:07:51.360 align:start position:0% and you also to detect any kind of wrong incentives<00:07:49.569> that<00:07:49.779> we<00:07:49.990> will<00:07:50.169> see<00:07:50.889> later 00:07:51.360 --> 00:07:51.370 align:start position:0% incentives that we will see later 00:07:51.370 --> 00:07:55.170 align:start position:0% incentives that we will see later our<00:07:52.289> security<00:07:53.289> issues<00:07:54.039> that<00:07:54.069> will<00:07:54.430> arise<00:07:54.580> from 00:07:55.170 --> 00:07:55.180 align:start position:0% our security issues that will arise from 00:07:55.180 --> 00:07:59.969 align:start position:0% our security issues that will arise from a<00:07:55.449> month<00:07:56.229> oran<00:07:56.710> first<00:07:57.539> so<00:07:58.560> we<00:07:59.560> introduced 00:07:59.969 --> 00:07:59.979 align:start position:0% a month oran first so we introduced 00:07:59.979 --> 00:08:02.429 align:start position:0% a month oran first so we introduced written<00:08:00.460> in<00:08:00.669> the<00:08:00.819> 2017<00:08:01.569> with<00:08:01.900> an<00:08:02.020> white<00:08:02.199> paper 00:08:02.429 --> 00:08:02.439 align:start position:0% written in the 2017 with an white paper 00:08:02.439 --> 00:08:06.480 align:start position:0% written in the 2017 with an white paper as<00:08:02.830> a<00:08:03.400> language<00:08:03.759> that<00:08:04.120> includes<00:08:04.930> most<00:08:05.770> of<00:08:06.340> the 00:08:06.480 --> 00:08:06.490 align:start position:0% as a language that includes most of the 00:08:06.490 --> 00:08:10.050 align:start position:0% as a language that includes most of the features<00:08:06.699> then<00:08:07.509> I<00:08:07.930> just<00:08:08.620> explained<00:08:09.400> and<00:08:09.669> radio 00:08:10.050 --> 00:08:10.060 align:start position:0% features then I just explained and radio 00:08:10.060 --> 00:08:12.600 align:start position:0% features then I just explained and radio messaging<00:08:10.589> for<00:08:11.589> retrieval<00:08:12.039> abbreviation<00:08:12.520> and 00:08:12.600 --> 00:08:12.610 align:start position:0% messaging for retrieval abbreviation and 00:08:12.610 --> 00:08:16.879 align:start position:0% messaging for retrieval abbreviation and the<00:08:12.729> literary<00:08:12.969> object<00:08:13.719> notation<00:08:14.190> so<00:08:15.810> freedom 00:08:16.879 --> 00:08:16.889 align:start position:0% the literary object notation so freedom 00:08:16.889 --> 00:08:20.040 align:start position:0% the literary object notation so freedom you<00:08:17.889> can<00:08:18.069> finger<00:08:18.639> feel<00:08:18.819> like<00:08:19.449> something<00:08:19.930> like 00:08:20.040 --> 00:08:20.050 align:start position:0% you can finger feel like something like 00:08:20.050 --> 00:08:22.230 align:start position:0% you can finger feel like something like this<00:08:20.080> that's<00:08:20.949> it<00:08:21.129> make<00:08:21.370> something<00:08:21.729> as<00:08:22.029> I<00:08:22.089> said 00:08:22.230 --> 00:08:22.240 align:start position:0% this that's it make something as I said 00:08:22.240 --> 00:08:25.519 align:start position:0% this that's it make something as I said it<00:08:22.509> is<00:08:22.539> abstract<00:08:23.199> so<00:08:23.469> it<00:08:24.039> doesn't<00:08:24.610> it<00:08:24.969> means 00:08:25.519 --> 00:08:25.529 align:start position:0% it is abstract so it doesn't it means 00:08:25.529 --> 00:08:28.200 align:start position:0% it is abstract so it doesn't it means it's<00:08:26.529> it<00:08:27.159> doesn't<00:08:27.490> have<00:08:27.610> a<00:08:27.639> literal 00:08:28.200 --> 00:08:28.210 align:start position:0% it's it doesn't have a literal 00:08:28.210 --> 00:08:31.890 align:start position:0% it's it doesn't have a literal representation<00:08:28.629> instead<00:08:29.940> so<00:08:30.940> a<00:08:31.240> schema<00:08:31.690> let's 00:08:31.890 --> 00:08:31.900 align:start position:0% representation instead so a schema let's 00:08:31.900 --> 00:08:34.290 align:start position:0% representation instead so a schema let's say<00:08:32.050> okay<00:08:32.769> this<00:08:33.070> is<00:08:33.130> not<00:08:33.459> any<00:08:33.760> particular 00:08:34.290 --> 00:08:34.300 align:start position:0% say okay this is not any particular 00:08:34.300 --> 00:08:36.389 align:start position:0% say okay this is not any particular language<00:08:34.479> is<00:08:34.959> it<00:08:35.110> this<00:08:35.380> is<00:08:35.560> just<00:08:35.740> representing 00:08:36.389 --> 00:08:36.399 align:start position:0% language is it this is just representing 00:08:36.399 --> 00:08:39.810 align:start position:0% language is it this is just representing three<00:08:37.060> operators<00:08:37.890> so<00:08:38.890> a<00:08:39.250> script<00:08:39.550> is<00:08:39.760> a 00:08:39.810 --> 00:08:39.820 align:start position:0% three operators so a script is a 00:08:39.820 --> 00:08:43.139 align:start position:0% three operators so a script is a pipeline<00:08:40.180> of<00:08:40.539> course<00:08:41.010> here<00:08:42.010> we're<00:08:42.219> bringing 00:08:43.139 --> 00:08:43.149 align:start position:0% pipeline of course here we're bringing 00:08:43.149 --> 00:08:46.310 align:start position:0% pipeline of course here we're bringing one<00:08:43.419> of<00:08:43.690> image<00:08:44.110> line<00:08:44.440> metal<00:08:45.130> can<00:08:45.310> be<00:08:45.339> either 00:08:46.310 --> 00:08:46.320 align:start position:0% one of image line metal can be either 00:08:46.320 --> 00:08:48.660 align:start position:0% one of image line metal can be either the<00:08:47.320> initial<00:08:47.740> panel<00:08:48.040> of<00:08:48.160> an<00:08:48.310> operator 00:08:48.660 --> 00:08:48.670 align:start position:0% the initial panel of an operator 00:08:48.670 --> 00:08:51.900 align:start position:0% the initial panel of an operator operator<00:08:49.449> gold<00:08:49.810> actually<00:08:50.380> for<00:08:51.160> an<00:08:51.459> operator 00:08:51.900 --> 00:08:51.910 align:start position:0% operator gold actually for an operator 00:08:51.910 --> 00:08:55.829 align:start position:0% operator gold actually for an operator followed<00:08:52.300> by<00:08:52.630> one<00:08:52.990> or<00:08:53.230> more<00:08:53.350> arguments<00:08:54.839> every 00:08:55.829 --> 00:08:55.839 align:start position:0% followed by one or more arguments every 00:08:55.839 --> 00:08:58.319 align:start position:0% followed by one or more arguments every operator<00:08:56.380> operates<00:08:57.010> on<00:08:57.550> the<00:08:57.699> output<00:08:58.060> of<00:08:58.209> the 00:08:58.319 --> 00:08:58.329 align:start position:0% operator operates on the output of the 00:08:58.329 --> 00:09:01.319 align:start position:0% operator operates on the output of the previous<00:08:58.480> one<00:08:58.899> and<00:08:59.140> then<00:08:59.760> that<00:09:00.760> obvious 00:09:01.319 --> 00:09:01.329 align:start position:0% previous one and then that obvious 00:09:01.329 --> 00:09:04.799 align:start position:0% previous one and then that obvious means<00:09:01.600> that<00:09:01.929> the<00:09:02.439> final<00:09:02.799> value<00:09:03.790> for<00:09:04.329> spring 00:09:04.799 --> 00:09:04.809 align:start position:0% means that the final value for spring 00:09:04.809 --> 00:09:09.780 align:start position:0% means that the final value for spring will<00:09:05.290> be<00:09:05.439> the<00:09:05.920> one<00:09:06.100> of<00:09:06.249> the<00:09:06.399> last<00:09:06.579> goal<00:09:07.799> easy<00:09:08.799> so 00:09:09.780 --> 00:09:09.790 align:start position:0% will be the one of the last goal easy so 00:09:09.790 --> 00:09:15.629 align:start position:0% will be the one of the last goal easy so as<00:09:10.089> a<00:09:10.480> type<00:09:10.809> system<00:09:11.309> Reagan<00:09:12.309> has<00:09:14.129> its<00:09:15.129> own<00:09:15.369> type 00:09:15.629 --> 00:09:15.639 align:start position:0% as a type system Reagan has its own type 00:09:15.639 --> 00:09:17.220 align:start position:0% as a type system Reagan has its own type system<00:09:16.059> let's<00:09:16.269> say<00:09:16.329> that<00:09:16.600> it's<00:09:16.749> independent 00:09:17.220 --> 00:09:17.230 align:start position:0% system let's say that it's independent 00:09:17.230 --> 00:09:20.999 align:start position:0% system let's say that it's independent from<00:09:17.670> the<00:09:18.670> one<00:09:19.029> that<00:09:19.329> you<00:09:19.389> know<00:09:19.720> for<00:09:20.079> Janice 00:09:20.999 --> 00:09:21.009 align:start position:0% from the one that you know for Janice 00:09:21.009 --> 00:09:23.030 align:start position:0% from the one that you know for Janice Priya<00:09:21.309> normally<00:09:22.089> need<00:09:22.329> you<00:09:22.449> for<00:09:22.720> any<00:09:22.869> other 00:09:23.030 --> 00:09:23.040 align:start position:0% Priya normally need you for any other 00:09:23.040 --> 00:09:26.910 align:start position:0% Priya normally need you for any other languages<00:09:24.540> it<00:09:25.540> is<00:09:25.569> scripted<00:09:26.319> which<00:09:26.679> means 00:09:26.910 --> 00:09:26.920 align:start position:0% languages it is scripted which means 00:09:26.920 --> 00:09:29.939 align:start position:0% languages it is scripted which means that<00:09:27.249> every<00:09:27.939> time<00:09:27.970> that<00:09:28.420> you<00:09:28.689> need<00:09:28.899> to<00:09:28.959> change 00:09:29.939 --> 00:09:29.949 align:start position:0% that every time that you need to change 00:09:29.949 --> 00:09:32.970 align:start position:0% that every time that you need to change from<00:09:30.279> one<00:09:30.369> time<00:09:30.970> to<00:09:30.999> another<00:09:31.259> and<00:09:32.259> you<00:09:32.619> need<00:09:32.860> to 00:09:32.970 --> 00:09:32.980 align:start position:0% from one time to another and you need to 00:09:32.980 --> 00:09:36.539 align:start position:0% from one time to another and you need to do<00:09:33.129> it<00:09:33.249> explicitly<00:09:33.759> random<00:09:34.720> so<00:09:35.379> the<00:09:35.980> types<00:09:36.279> are 00:09:36.539 --> 00:09:36.549 align:start position:0% do it explicitly random so the types are 00:09:36.549 --> 00:09:40.229 align:start position:0% do it explicitly random so the types are the<00:09:37.209> obvious<00:09:37.480> ones<00:09:37.949> for<00:09:38.949> value<00:09:39.249> types<00:09:39.519> of<00:09:39.910> pool 00:09:40.229 --> 00:09:40.239 align:start position:0% the obvious ones for value types of pool 00:09:40.239 --> 00:09:42.569 align:start position:0% the obvious ones for value types of pool and<00:09:40.269> integral<00:09:41.019> screening<00:09:41.589> and<00:09:41.799> there<00:09:42.429> are 00:09:42.569 --> 00:09:42.579 align:start position:0% and integral screening and there are 00:09:42.579 --> 00:09:45.389 align:start position:0% and integral screening and there are four<00:09:42.879> complex<00:09:43.299> types<00:09:43.540> or<00:09:43.749> structures<00:09:44.439> that<00:09:45.040> I 00:09:45.389 --> 00:09:45.399 align:start position:0% four complex types or structures that I 00:09:45.399 --> 00:09:50.579 align:start position:0% four complex types or structures that I love<00:09:45.730> for<00:09:45.999> more<00:09:46.269> fun<00:09:46.989> system<00:09:47.519> more<00:09:49.589> functional 00:09:50.579 --> 00:09:50.589 align:start position:0% love for more fun system more functional 00:09:50.589 --> 00:09:54.799 align:start position:0% love for more fun system more functional programming<00:09:51.160> knowledge<00:09:51.459> with<00:09:51.879> it<00:09:53.309> then 00:09:54.799 --> 00:09:54.809 align:start position:0% programming knowledge with it then 00:09:54.809 --> 00:09:58.590 align:start position:0% programming knowledge with it then one<00:09:55.809> next<00:09:56.049> thing<00:09:56.259> is<00:09:56.499> that<00:09:56.529> we<00:09:57.189> can<00:09:57.309> take<00:09:57.600> raid 00:09:58.590 --> 00:09:58.600 align:start position:0% one next thing is that we can take raid 00:09:58.600 --> 00:10:01.289 align:start position:0% one next thing is that we can take raid on<00:09:58.809> the<00:09:58.839> streets<00:09:59.259> and<00:09:59.529> serialized<00:10:00.489> data<00:10:00.699> using 00:10:01.289 --> 00:10:01.299 align:start position:0% on the streets and serialized data using 00:10:01.299 --> 00:10:03.269 align:start position:0% on the streets and serialized data using the<00:10:01.420> C<00:10:01.660> board<00:10:01.899> which<00:10:02.410> is<00:10:02.559> a<00:10:02.589> standard<00:10:03.129> for 00:10:03.269 --> 00:10:03.279 align:start position:0% the C board which is a standard for 00:10:03.279 --> 00:10:07.530 align:start position:0% the C board which is a standard for encoding<00:10:04.319> data<00:10:05.319> structures<00:10:05.980> in<00:10:06.309> the<00:10:06.519> Bible<00:10:07.089> so 00:10:07.530 --> 00:10:07.540 align:start position:0% encoding data structures in the Bible so 00:10:07.540 --> 00:10:10.019 align:start position:0% encoding data structures in the Bible so what<00:10:07.749> we<00:10:07.959> get<00:10:08.199> some<00:10:08.589> alignment<00:10:09.279> we<00:10:09.429> see<00:10:09.639> here 00:10:10.019 --> 00:10:10.029 align:start position:0% what we get some alignment we see here 00:10:10.029 --> 00:10:13.590 align:start position:0% what we get some alignment we see here that<00:10:10.480> we<00:10:10.929> can<00:10:11.379> feed<00:10:11.919> into<00:10:12.160> you<00:10:12.459> the<00:10:12.910> resonating 00:10:13.590 --> 00:10:13.600 align:start position:0% that we can feed into you the resonating 00:10:13.600 --> 00:10:16.919 align:start position:0% that we can feed into you the resonating which<00:10:13.989> is<00:10:14.139> an<00:10:14.319> interpreter<00:10:14.949> that<00:10:15.549> is<00:10:15.759> one<00:10:16.389> item 00:10:16.919 --> 00:10:16.929 align:start position:0% which is an interpreter that is one item 00:10:16.929 --> 00:10:20.220 align:start position:0% which is an interpreter that is one item that<00:10:16.959> is<00:10:17.350> at<00:10:17.559> machine<00:10:17.949> that<00:10:18.369> simply<00:10:19.019> takes<00:10:20.019> a 00:10:20.220 --> 00:10:20.230 align:start position:0% that is at machine that simply takes a 00:10:20.230 --> 00:10:23.159 align:start position:0% that is at machine that simply takes a humid<00:10:20.769> data<00:10:21.009> that<00:10:21.459> we<00:10:21.639> pray<00:10:22.209> from<00:10:22.540> name<00:10:22.929> guys 00:10:23.159 --> 00:10:23.169 align:start position:0% humid data that we pray from name guys 00:10:23.169 --> 00:10:26.699 align:start position:0% humid data that we pray from name guys for<00:10:23.470> example<00:10:23.919> and<00:10:24.100> start<00:10:24.730> interpreting<00:10:25.709> the 00:10:26.699 --> 00:10:26.709 align:start position:0% for example and start interpreting the 00:10:26.709 --> 00:10:29.669 align:start position:0% for example and start interpreting the speak<00:10:27.009> and<00:10:27.220> putting<00:10:27.970> operators<00:10:28.509> are<00:10:28.779> applying 00:10:29.669 --> 00:10:29.679 align:start position:0% speak and putting operators are applying 00:10:29.679 --> 00:10:31.859 align:start position:0% speak and putting operators are applying on<00:10:29.860> triggers<00:10:30.279> and<00:10:30.579> then<00:10:30.879> we<00:10:31.119> will<00:10:31.569> get<00:10:31.720> the 00:10:31.859 --> 00:10:31.869 align:start position:0% on triggers and then we will get the 00:10:31.869 --> 00:10:35.789 align:start position:0% on triggers and then we will get the final<00:10:33.029> the<00:10:34.029> final<00:10:34.209> result<00:10:34.689> basically<00:10:35.230> here 00:10:35.789 --> 00:10:35.799 align:start position:0% final the final result basically here 00:10:35.799 --> 00:10:38.249 align:start position:0% final the final result basically here this<00:10:36.040> is<00:10:36.189> business<00:10:36.879> is<00:10:37.059> just<00:10:37.389> saying<00:10:37.629> okay 00:10:38.249 --> 00:10:38.259 align:start position:0% this is business is just saying okay 00:10:38.259 --> 00:10:40.619 align:start position:0% this is business is just saying okay whatever<00:10:38.949> do<00:10:39.220> you<00:10:39.610> get<00:10:39.819> from<00:10:40.089> the<00:10:40.209> MEI 00:10:40.619 --> 00:10:40.629 align:start position:0% whatever do you get from the MEI 00:10:40.629 --> 00:10:43.439 align:start position:0% whatever do you get from the MEI parse<00:10:41.259> in<00:10:41.439> the<00:10:41.559> station<00:10:42.009> free<00:10:42.429> time<00:10:42.730> as<00:10:43.059> a<00:10:43.119> man 00:10:43.439 --> 00:10:43.449 align:start position:0% parse in the station free time as a man 00:10:43.449 --> 00:10:45.840 align:start position:0% parse in the station free time as a man as<00:10:43.809> a<00:10:43.929> hash<00:10:44.230> mark<00:10:44.439> let's<00:10:44.769> say<00:10:44.949> you<00:10:45.189> value<00:10:45.549> store 00:10:45.840 --> 00:10:45.850 align:start position:0% as a hash mark let's say you value store 00:10:45.850 --> 00:10:49.559 align:start position:0% as a hash mark let's say you value store and<00:10:46.230> product<00:10:47.230> get<00:10:47.679> the<00:10:47.980> value<00:10:48.569> associated 00:10:49.559 --> 00:10:49.569 align:start position:0% and product get the value associated 00:10:49.569 --> 00:10:53.249 align:start position:0% and product get the value associated with<00:10:50.169> an<00:10:50.290> EM<00:10:50.499> field<00:10:50.829> and<00:10:51.309> then<00:10:51.749> return<00:10:52.749> that<00:10:52.779> as 00:10:53.249 --> 00:10:53.259 align:start position:0% with an EM field and then return that as 00:10:53.259 --> 00:10:57.539 align:start position:0% with an EM field and then return that as a<00:10:53.319> boat<00:10:53.679> so<00:10:54.399> those<00:10:54.910> are<00:10:55.089> four<00:10:55.389> calls<00:10:55.749> and<00:10:56.549> once 00:10:57.539 --> 00:10:57.549 align:start position:0% a boat so those are four calls and once 00:10:57.549 --> 00:10:57.979 align:start position:0% a boat so those are four calls and once you 00:10:57.979 --> 00:10:57.989 align:start position:0% you 00:10:57.989 --> 00:11:01.649 align:start position:0% you like<00:10:58.989> this<00:10:59.259> if<00:10:59.709> you<00:11:00.039> created<00:11:00.519> like<00:11:00.759> Jason<00:11:01.479> and 00:11:01.649 --> 00:11:01.659 align:start position:0% like this if you created like Jason and 00:11:01.659 --> 00:11:03.809 align:start position:0% like this if you created like Jason and this<00:11:02.289> is<00:11:02.529> the<00:11:02.739> expo 00:11:03.809 --> 00:11:03.819 align:start position:0% this is the expo 00:11:03.819 --> 00:11:09.109 align:start position:0% this is the expo so<00:11:03.999> we're<00:11:04.509> saying<00:11:05.139> this<00:11:05.979> is<00:11:06.159> ivory<00:11:06.759> really 00:11:09.109 --> 00:11:09.119 align:start position:0% so we're saying this is ivory really 00:11:09.119 --> 00:11:13.079 align:start position:0% so we're saying this is ivory really come<00:11:10.119> on<00:11:10.149> a<00:11:10.749> screen<00:11:11.649> this<00:11:11.919> one<00:11:12.129> is<00:11:12.309> for<00:11:12.579> open 00:11:13.079 --> 00:11:13.089 align:start position:0% come on a screen this one is for open 00:11:13.089 --> 00:11:15.389 align:start position:0% come on a screen this one is for open weather<00:11:13.269> months<00:11:13.539> actually<00:11:13.809> so<00:11:14.619> we<00:11:14.949> have<00:11:15.159> a 00:11:15.389 --> 00:11:15.399 align:start position:0% weather months actually so we have a 00:11:15.399 --> 00:11:18.179 align:start position:0% weather months actually so we have a spring<00:11:16.299> that<00:11:16.509> says<00:11:16.929> all<00:11:17.259> of<00:11:17.499> that<00:11:17.709> you<00:11:18.159> know 00:11:18.179 --> 00:11:18.189 align:start position:0% spring that says all of that you know 00:11:18.189 --> 00:11:19.199 align:start position:0% spring that says all of that you know our<00:11:18.579> situation 00:11:19.199 --> 00:11:19.209 align:start position:0% our situation 00:11:19.209 --> 00:11:24.359 align:start position:0% our situation you<00:11:19.299> need<00:11:19.449> to<00:11:19.629> I<00:11:19.869> get<00:11:20.729> and<00:11:21.729> so<00:11:21.939> on<00:11:22.119> in<00:11:23.369> 1325 00:11:24.359 --> 00:11:24.369 align:start position:0% you need to I get and so on in 1325 00:11:24.369 --> 00:11:28.710 align:start position:0% you need to I get and so on in 1325 which<00:11:24.789> is<00:11:25.179> really<00:11:25.539> redundant<00:11:26.549> then<00:11:27.549> as<00:11:27.909> as<00:11:28.569> I 00:11:28.710 --> 00:11:28.720 align:start position:0% which is really redundant then as as I 00:11:28.720 --> 00:11:31.529 align:start position:0% which is really redundant then as as I say<00:11:28.929> we<00:11:29.439> can<00:11:29.679> we're<00:11:30.609> not<00:11:30.789> expecting<00:11:31.329> you<00:11:31.509> to 00:11:31.529 --> 00:11:31.539 align:start position:0% say we can we're not expecting you to 00:11:31.539 --> 00:11:34.919 align:start position:0% say we can we're not expecting you to write<00:11:32.699> bytecode<00:11:33.699> or<00:11:33.970> to<00:11:34.239> do<00:11:34.389> this<00:11:34.569> kind<00:11:34.839> of 00:11:34.919 --> 00:11:34.929 align:start position:0% write bytecode or to do this kind of 00:11:34.929 --> 00:11:37.379 align:start position:0% write bytecode or to do this kind of structures<00:11:35.470> because<00:11:35.799> and<00:11:36.129> this<00:11:36.639> is<00:11:36.819> not<00:11:37.359> a 00:11:37.379 --> 00:11:37.389 align:start position:0% structures because and this is not a 00:11:37.389 --> 00:11:40.429 align:start position:0% structures because and this is not a million<00:11:37.779> at<00:11:38.019> all<00:11:38.199> what<00:11:38.829> we<00:11:39.099> do<00:11:39.279> is<00:11:39.459> rub<00:11:39.789> that<00:11:39.970> we 00:11:40.429 --> 00:11:40.439 align:start position:0% million at all what we do is rub that we 00:11:40.439 --> 00:11:44.269 align:start position:0% million at all what we do is rub that we library<00:11:41.439> so<00:11:41.739> we<00:11:42.069> have<00:11:42.579> this<00:11:42.789> witness<00:11:43.209> request 00:11:44.269 --> 00:11:44.279 align:start position:0% library so we have this witness request 00:11:44.279 --> 00:11:47.609 align:start position:0% library so we have this witness request library<00:11:45.279> which<00:11:45.609> is<00:11:45.759> available<00:11:46.329> on<00:11:46.629> any<00:11:46.839> n<00:11:47.139> and 00:11:47.609 --> 00:11:47.619 align:start position:0% library which is available on any n and 00:11:47.619 --> 00:11:50.369 align:start position:0% library which is available on any n and you<00:11:47.919> can<00:11:48.129> just<00:11:48.609> you<00:11:49.179> with<00:11:49.359> at<00:11:49.509> spring<00:11:49.869> and<00:11:50.199> then 00:11:50.369 --> 00:11:50.379 align:start position:0% you can just you with at spring and then 00:11:50.379 --> 00:11:52.889 align:start position:0% you can just you with at spring and then start<00:11:50.919> pushing<00:11:51.429> operators<00:11:52.119> into<00:11:52.479> the<00:11:52.599> strip 00:11:52.889 --> 00:11:52.899 align:start position:0% start pushing operators into the strip 00:11:52.899 --> 00:11:56.609 align:start position:0% start pushing operators into the strip just<00:11:53.529> like<00:11:53.709> that<00:11:53.889> with<00:11:54.549> the<00:11:54.729> same<00:11:55.229> names<00:11:56.229> let's 00:11:56.609 --> 00:11:56.619 align:start position:0% just like that with the same names let's 00:11:56.619 --> 00:11:59.639 align:start position:0% just like that with the same names let's say<00:11:56.769> are<00:11:57.369> stationed<00:11:57.879> at<00:11:57.999> math<00:11:58.209> at<00:11:58.509> em<00:11:58.779> spot<00:11:59.259> and 00:11:59.639 --> 00:11:59.649 align:start position:0% say are stationed at math at em spot and 00:11:59.649 --> 00:12:01.619 align:start position:0% say are stationed at math at em spot and this<00:11:59.829> is<00:11:59.979> actually<00:12:00.339> metaprogramming<00:12:00.639> so<00:12:01.329> this 00:12:01.619 --> 00:12:01.629 align:start position:0% this is actually metaprogramming so this 00:12:01.629 --> 00:12:05.939 align:start position:0% this is actually metaprogramming so this is<00:12:02.399> the<00:12:03.399> writing<00:12:03.759> software<00:12:04.359> that<00:12:04.959> writes<00:12:05.589> over 00:12:05.939 --> 00:12:05.949 align:start position:0% is the writing software that writes over 00:12:05.949 --> 00:12:06.779 align:start position:0% is the writing software that writes over for<00:12:06.369> you 00:12:06.779 --> 00:12:06.789 align:start position:0% for you 00:12:06.789 --> 00:12:10.049 align:start position:0% for you this<00:12:06.939> is<00:12:07.089> an<00:12:07.539> internally<00:12:08.259> generated<00:12:08.879> in<00:12:09.879> this 00:12:10.049 --> 00:12:10.059 align:start position:0% this is an internally generated in this 00:12:10.059 --> 00:12:14.759 align:start position:0% this is an internally generated in this week<00:12:10.329> and<00:12:10.539> the<00:12:11.079> end<00:12:11.799> when<00:12:12.519> you<00:12:13.259> you<00:12:14.259> can<00:12:14.499> add 00:12:14.759 --> 00:12:14.769 align:start position:0% week and the end when you you can add 00:12:14.769 --> 00:12:17.399 align:start position:0% week and the end when you you can add one<00:12:15.339> more<00:12:15.549> like<00:12:15.789> saying<00:12:16.179> to<00:12:16.569> Jason<00:12:17.139> and<00:12:17.379> you 00:12:17.399 --> 00:12:17.409 align:start position:0% one more like saying to Jason and you 00:12:17.409 --> 00:12:20.219 align:start position:0% one more like saying to Jason and you get<00:12:17.949> this<00:12:18.339> structure<00:12:18.759> for<00:12:18.999> example<00:12:19.089> or<00:12:19.899> you<00:12:19.959> do 00:12:20.219 --> 00:12:20.229 align:start position:0% get this structure for example or you do 00:12:20.229 --> 00:12:24.960 align:start position:0% get this structure for example or you do to<00:12:20.559> seaboard<00:12:20.979> and<00:12:21.189> you<00:12:21.339> need<00:12:21.489> Michael<00:12:23.549> so<00:12:24.549> then 00:12:24.960 --> 00:12:24.970 align:start position:0% to seaboard and you need Michael so then 00:12:24.970 --> 00:12:38.690 align:start position:0% to seaboard and you need Michael so then we<00:12:25.089> explain<00:12:25.389> how<00:12:25.720> these<00:12:26.169> works<00:12:26.619> in<00:12:27.159> practice 00:12:38.690 --> 00:12:38.700 align:start position:0% 00:12:38.700 --> 00:12:45.050 align:start position:0% [Music] 00:12:45.050 --> 00:12:45.060 align:start position:0% 00:12:45.060 --> 00:12:49.650 align:start position:0% [Applause] 00:12:49.650 --> 00:12:49.660 align:start position:0% 00:12:49.660 --> 00:12:52.290 align:start position:0% so<00:12:50.200> basically<00:12:50.500> we<00:12:50.680> have<00:12:50.800> for<00:12:51.399> the<00:12:51.580> faces<00:12:52.089> we 00:12:52.290 --> 00:12:52.300 align:start position:0% so basically we have for the faces we 00:12:52.300 --> 00:12:58.430 align:start position:0% so basically we have for the faces we start<00:12:52.570> by<00:12:52.690> just<00:12:52.720> inserting<00:12:53.110> the<00:12:53.500> bike 00:12:58.430 --> 00:12:58.440 align:start position:0% 00:12:58.440 --> 00:13:01.980 align:start position:0% actually<00:12:59.440> well<00:12:59.800> done<00:13:00.360> with<00:13:01.360> that<00:13:01.510> what<00:13:01.810> we 00:13:01.980 --> 00:13:01.990 align:start position:0% actually well done with that what we 00:13:01.990 --> 00:13:05.190 align:start position:0% actually well done with that what we have<00:13:03.089> selected<00:13:04.089> to<00:13:04.540> perform<00:13:04.750> that<00:13:04.990> task 00:13:05.190 --> 00:13:05.200 align:start position:0% have selected to perform that task 00:13:05.200 --> 00:13:07.680 align:start position:0% have selected to perform that task because<00:13:05.709> those<00:13:05.890> notes<00:13:06.130> in<00:13:06.790> business<00:13:07.089> there 00:13:07.680 --> 00:13:07.690 align:start position:0% because those notes in business there 00:13:07.690 --> 00:13:09.660 align:start position:0% because those notes in business there may<00:13:07.870> be<00:13:07.899> selected<00:13:08.140> randomly<00:13:08.680> so<00:13:09.459> that<00:13:09.580> they 00:13:09.660 --> 00:13:09.670 align:start position:0% may be selected randomly so that they 00:13:09.670 --> 00:13:11.220 align:start position:0% may be selected randomly so that they can<00:13:09.820> correlate<00:13:10.240> with<00:13:10.330> each<00:13:10.570> other<00:13:10.810> and 00:13:11.220 --> 00:13:11.230 align:start position:0% can correlate with each other and 00:13:11.230 --> 00:13:13.500 align:start position:0% can correlate with each other and creating<00:13:11.740> graphics<00:13:12.130> relations<00:13:12.610> is<00:13:13.240> very 00:13:13.500 --> 00:13:13.510 align:start position:0% creating graphics relations is very 00:13:13.510 --> 00:13:17.010 align:start position:0% creating graphics relations is very vital<00:13:13.720> functions<00:13:14.970> so<00:13:15.970> basically<00:13:16.270> once<00:13:16.839> the 00:13:17.010 --> 00:13:17.020 align:start position:0% vital functions so basically once the 00:13:17.020 --> 00:13:19.560 align:start position:0% vital functions so basically once the subcommittee<00:13:17.920> of<00:13:18.459> the<00:13:18.520> house<00:13:18.790> is<00:13:19.060> selected 00:13:19.560 --> 00:13:19.570 align:start position:0% subcommittee of the house is selected 00:13:19.570 --> 00:13:22.260 align:start position:0% subcommittee of the house is selected their<00:13:19.930> graduation<00:13:20.560> transcripts<00:13:21.339> that<00:13:22.029> their 00:13:22.260 --> 00:13:22.270 align:start position:0% their graduation transcripts that their 00:13:22.270 --> 00:13:25.800 align:start position:0% their graduation transcripts that their victory<00:13:22.600> verses<00:13:22.990> specifies<00:13:24.330> the<00:13:25.330> data<00:13:25.360> under 00:13:25.800 --> 00:13:25.810 align:start position:0% victory verses specifies the data under 00:13:25.810 --> 00:13:30.630 align:start position:0% victory verses specifies the data under physical<00:13:26.260> specimens<00:13:28.230> passionate<00:13:29.640> acceptance 00:13:30.630 --> 00:13:30.640 align:start position:0% physical specimens passionate acceptance 00:13:30.640 --> 00:14:11.189 align:start position:0% physical specimens passionate acceptance we<00:13:31.240> met 00:14:11.189 --> 00:14:11.199 align:start position:0% 00:14:11.199 --> 00:14:17.189 align:start position:0% in<00:14:12.199> order<00:14:12.439> to<00:14:12.730> avoid<00:14:14.110> failures<00:14:15.489> provides<00:14:16.489> from 00:14:17.189 --> 00:14:17.199 align:start position:0% in order to avoid failures provides from 00:14:17.199 --> 00:14:22.150 align:start position:0% in order to avoid failures provides from American<00:14:18.199> sniper<00:14:18.819> so<00:14:20.259> radio<00:14:21.259> space<00:14:21.470> there<00:14:22.040> are 00:14:22.150 --> 00:14:22.160 align:start position:0% American sniper so radio space there are 00:14:22.160 --> 00:14:23.949 align:start position:0% American sniper so radio space there are three<00:14:22.339> different<00:14:22.759> stages<00:14:23.029> the<00:14:23.540> first<00:14:23.569> one<00:14:23.839> is 00:14:23.949 --> 00:14:23.959 align:start position:0% three different stages the first one is 00:14:23.959 --> 00:14:26.799 align:start position:0% three different stages the first one is the<00:14:24.049> source<00:14:24.290> this<00:14:24.470> means<00:14:24.799> that<00:14:25.579> they<00:14:26.480> relate 00:14:26.799 --> 00:14:26.809 align:start position:0% the source this means that they relate 00:14:26.809 --> 00:14:29.979 align:start position:0% the source this means that they relate to<00:14:26.839> the<00:14:27.379> US<00:14:27.709> because<00:14:28.369> it's<00:14:28.759> fun<00:14:29.269> and<00:14:29.540> they 00:14:29.979 --> 00:14:29.989 align:start position:0% to the US because it's fun and they 00:14:29.989 --> 00:14:32.979 align:start position:0% to the US because it's fun and they could<00:14:30.170> be<00:14:30.290> many<00:14:30.499> as<00:14:30.649> you<00:14:30.799> can<00:14:30.949> see<00:14:31.360> then<00:14:32.360> when 00:14:32.979 --> 00:14:32.989 align:start position:0% could be many as you can see then when 00:14:32.989 --> 00:14:34.900 align:start position:0% could be many as you can see then when we<00:14:33.139> aggregate<00:14:33.619> those<00:14:33.889> data<00:14:34.220> points<00:14:34.309> into 00:14:34.900 --> 00:14:34.910 align:start position:0% we aggregate those data points into 00:14:34.910 --> 00:14:36.879 align:start position:0% we aggregate those data points into singers<00:14:35.299> at<00:14:35.420> the<00:14:35.509> point<00:14:35.720> 5<00:14:36.049> negative<00:14:36.110> space 00:14:36.879 --> 00:14:36.889 align:start position:0% singers at the point 5 negative space 00:14:36.889 --> 00:14:39.609 align:start position:0% singers at the point 5 negative space similar<00:14:37.819> to<00:14:37.910> say<00:14:38.059> like<00:14:38.239> Moses<00:14:39.019> which<00:14:39.230> are<00:14:39.410> run 00:14:39.609 --> 00:14:39.619 align:start position:0% similar to say like Moses which are run 00:14:39.619 --> 00:14:42.129 align:start position:0% similar to say like Moses which are run by<00:14:39.649> the<00:14:39.829> witnessing<00:14:40.339> notes<00:14:40.549> themselves<00:14:41.139> and 00:14:42.129 --> 00:14:42.139 align:start position:0% by the witnessing notes themselves and 00:14:42.139 --> 00:14:44.769 align:start position:0% by the witnessing notes themselves and finally<00:14:42.410> if<00:14:42.980> we<00:14:43.100> have<00:14:43.249> moved<00:14:43.879> a<00:14:44.029> million<00:14:44.389> homes 00:14:44.769 --> 00:14:44.779 align:start position:0% finally if we have moved a million homes 00:14:44.779 --> 00:14:48.160 align:start position:0% finally if we have moved a million homes that<00:14:44.989> we<00:14:45.439> threw<00:14:45.619> ourselves<00:14:46.389> how<00:14:47.389> do<00:14:47.449> we<00:14:47.660> get 00:14:48.160 --> 00:14:48.170 align:start position:0% that we threw ourselves how do we get 00:14:48.170 --> 00:14:49.319 align:start position:0% that we threw ourselves how do we get this<00:14:48.589> data 00:14:49.319 --> 00:14:49.329 align:start position:0% this data 00:14:49.329 --> 00:14:53.499 align:start position:0% this data well<00:14:50.329> the<00:14:50.540> values<00:14:51.309> which<00:14:52.309> are<00:14:52.459> actually<00:14:53.059> from 00:14:53.499 --> 00:14:53.509 align:start position:0% well the values which are actually from 00:14:53.509 --> 00:14:55.660 align:start position:0% well the values which are actually from my<00:14:53.660> signals<00:14:54.199> but<00:14:54.439> I<00:14:54.709> thought<00:14:55.100> the<00:14:55.220> candy<00:14:55.519> house 00:14:55.660 --> 00:14:55.670 align:start position:0% my signals but I thought the candy house 00:14:55.670 --> 00:15:03.879 align:start position:0% my signals but I thought the candy house backed<00:14:55.939> up<00:14:56.089> to<00:14:56.239> -<00:15:01.749> so<00:15:02.749> further<00:15:03.230> information 00:15:03.879 --> 00:15:03.889 align:start position:0% backed up to - so further information 00:15:03.889 --> 00:15:06.039 align:start position:0% backed up to - so further information can<00:15:04.009> be<00:15:04.100> done<00:15:04.279> by<00:15:04.519> the<00:15:04.579> request<00:15:05.329> the<00:15:05.540> creators 00:15:06.039 --> 00:15:06.049 align:start position:0% can be done by the request the creators 00:15:06.049 --> 00:15:09.069 align:start position:0% can be done by the request the creators for<00:15:06.619> example<00:15:07.129> and<00:15:07.429> Apollo<00:15:07.910> is<00:15:08.540> setting<00:15:08.929> the 00:15:09.069 --> 00:15:09.079 align:start position:0% for example and Apollo is setting the 00:15:09.079 --> 00:16:06.050 align:start position:0% for example and Apollo is setting the number<00:15:09.199> of<00:15:09.470> witnesses 00:16:06.050 --> 00:16:06.060 align:start position:0% 00:16:06.060 --> 00:16:20.420 align:start position:0% and<00:16:07.060> what<00:16:07.330> we<00:16:07.450> selected<00:16:07.960> is<00:16:08.050> that<00:16:12.360> so<00:16:16.860> and<00:16:17.860> so 00:16:20.420 --> 00:16:20.430 align:start position:0% 00:16:20.430 --> 00:16:22.530 align:start position:0% what<00:16:21.430> they're<00:16:21.520> gonna<00:16:21.730> do<00:16:21.910> each<00:16:22.180> of<00:16:22.360> them 00:16:22.530 --> 00:16:22.540 align:start position:0% what they're gonna do each of them 00:16:22.540 --> 00:16:26.690 align:start position:0% what they're gonna do each of them they're<00:16:23.170> gonna<00:16:23.350> post<00:16:23.650> resources<00:16:24.340> as<00:16:24.550> the 00:16:26.690 --> 00:16:26.700 align:start position:0% they're gonna post resources as the 00:16:26.700 --> 00:16:30.360 align:start position:0% they're gonna post resources as the sources<00:16:28.200> the<00:16:29.200> aggregation<00:16:29.620> script<00:16:30.100> so<00:16:30.340> that 00:16:30.360 --> 00:16:30.370 align:start position:0% sources the aggregation script so that 00:16:30.370 --> 00:16:33.870 align:start position:0% sources the aggregation script so that those<00:16:31.360> three<00:16:31.660> points<00:16:31.840> and<00:16:32.610> integrated<00:16:33.610> into 00:16:33.870 --> 00:16:33.880 align:start position:0% those three points and integrated into 00:16:33.880 --> 00:16:37.860 align:start position:0% those three points and integrated into one<00:16:34.090> single<00:16:34.390> variable<00:16:34.890> after<00:16:35.890> that<00:16:36.840> there<00:16:37.840> is 00:16:37.860 --> 00:16:37.870 align:start position:0% one single variable after that there is 00:16:37.870 --> 00:16:40.290 align:start position:0% one single variable after that there is no<00:16:37.960> bigger<00:16:38.350> thing<00:16:38.530> to<00:16:38.980> win<00:16:39.130> them<00:16:39.310> but<00:16:39.460> I<00:16:39.520> am 00:16:40.290 --> 00:16:40.300 align:start position:0% no bigger thing to win them but I am 00:16:40.300 --> 00:16:41.700 align:start position:0% no bigger thing to win them but I am they<00:16:40.540> don't<00:16:40.570> do<00:16:40.810> it<00:16:40.900> the<00:16:40.990> straightaway<00:16:41.440> but 00:16:41.700 --> 00:16:41.710 align:start position:0% they don't do it the straightaway but 00:16:41.710 --> 00:16:43.980 align:start position:0% they don't do it the straightaway but they<00:16:41.890> just<00:16:42.130> use<00:16:42.310> the<00:16:42.490> recommend<00:16:43.030> removal 00:16:43.980 --> 00:16:43.990 align:start position:0% they just use the recommend removal 00:16:43.990 --> 00:16:44.710 align:start position:0% they just use the recommend removal scheme<00:16:44.200> press 00:16:44.710 --> 00:16:44.720 align:start position:0% scheme press 00:16:44.720 --> 00:16:53.860 align:start position:0% scheme press the<00:16:44.959> first<00:16:45.230> commentary 00:16:53.860 --> 00:16:53.870 align:start position:0% 00:16:53.870 --> 00:17:38.600 align:start position:0% [Music] 00:17:38.600 --> 00:17:38.610 align:start position:0% 00:17:38.610 --> 00:17:56.010 align:start position:0% [Music] 00:17:56.010 --> 00:17:56.020 align:start position:0% 00:17:56.020 --> 00:18:00.210 align:start position:0% so<00:17:57.220> it's<00:17:58.220> so<00:17:58.340> simple<00:17:58.460> to<00:17:58.669> understand<00:17:59.120> like<00:17:59.360> the 00:18:00.210 --> 00:18:00.220 align:start position:0% so it's so simple to understand like the 00:18:00.220 --> 00:18:08.080 align:start position:0% so it's so simple to understand like the because<00:18:01.220> it<00:18:01.309> doesn't<00:18:02.000> mean<00:18:02.240> to<00:18:02.390> know<00:18:06.909> see<00:18:07.909> the 00:18:08.080 --> 00:18:08.090 align:start position:0% because it doesn't mean to know see the 00:18:08.090 --> 00:18:17.450 align:start position:0% because it doesn't mean to know see the fabulous<00:18:08.270> Odyssey<00:18:09.220> so<00:18:10.220> once<00:18:10.970> they 00:18:17.450 --> 00:18:17.460 align:start position:0% 00:18:17.460 --> 00:18:28.420 align:start position:0% [Music] 00:18:28.420 --> 00:18:28.430 align:start position:0% 00:18:28.430 --> 00:18:58.370 align:start position:0% okay<00:18:54.200> so<00:18:55.200> once<00:18:56.160> a<00:18:56.280> result<00:18:56.610> is<00:18:56.790> included<00:18:57.380> with 00:18:58.370 --> 00:18:58.380 align:start position:0% okay so once a result is included with 00:18:58.380 --> 00:19:07.600 align:start position:0% okay so once a result is included with me<00:18:58.560> again<00:18:59.490> the<00:19:04.370> start<00:19:05.370> from<00:19:05.580> this<00:19:06.350> was<00:19:07.350> I<00:19:07.470> think 00:19:07.600 --> 00:19:07.610 align:start position:0% me again the start from this was I think 00:19:07.610 --> 00:19:11.060 align:start position:0% me again the start from this was I think they<00:19:08.610> will<00:19:08.790> take<00:19:08.970> it<00:19:09.210> and<00:19:09.840> you<00:19:10.020> will<00:19:10.230> a<00:19:10.470> poster 00:19:11.060 --> 00:19:11.070 align:start position:0% they will take it and you will a poster 00:19:11.070 --> 00:19:14.390 align:start position:0% they will take it and you will a poster something<00:19:11.460> original<00:19:12.210> things<00:19:12.690> the<00:19:13.680> component 00:19:14.390 --> 00:19:14.400 align:start position:0% something original things the component 00:19:14.400 --> 00:19:16.180 align:start position:0% something original things the component you<00:19:14.490> mention<00:19:14.850> is<00:19:14.940> that<00:19:15.030> with<00:19:15.150> a<00:19:15.210> population 00:19:16.180 --> 00:19:16.190 align:start position:0% you mention is that with a population 00:19:16.190 --> 00:19:23.720 align:start position:0% you mention is that with a population and<00:19:17.420> it<00:19:18.420> is<00:19:19.020> used<00:19:19.350> by<00:19:19.500> the<00:19:21.830> nose<00:19:22.830> here<00:19:23.430> to 00:19:23.720 --> 00:19:23.730 align:start position:0% and it is used by the nose here to 00:19:23.730 --> 00:19:26.300 align:start position:0% and it is used by the nose here to meditate<00:19:24.140> transaction<00:19:25.140> occurring<00:19:25.650> with<00:19:26.100> them 00:19:26.300 --> 00:19:26.310 align:start position:0% meditate transaction occurring with them 00:19:26.310 --> 00:19:28.960 align:start position:0% meditate transaction occurring with them and<00:19:26.940> showing<00:19:27.270> improve<00:19:27.780> it 00:19:28.960 --> 00:19:28.970 align:start position:0% and showing improve it 00:19:28.970 --> 00:20:08.040 align:start position:0% and showing improve it [Music] 00:20:08.040 --> 00:20:08.050 align:start position:0% 00:20:08.050 --> 00:20:29.350 align:start position:0% [Music] 00:20:29.350 --> 00:20:29.360 align:start position:0% 00:20:29.360 --> 00:20:32.450 align:start position:0% so<00:20:30.360> yeah<00:20:30.510> we<00:20:31.140> start<00:20:31.710> with<00:20:31.890> basically<00:20:32.340> the 00:20:32.450 --> 00:20:32.460 align:start position:0% so yeah we start with basically the 00:20:32.460 --> 00:20:36.040 align:start position:0% so yeah we start with basically the weights<00:20:32.760> a<00:20:33.590> package<00:20:34.590> with<00:20:34.770> the<00:20:34.890> string 00:20:36.040 --> 00:20:36.050 align:start position:0% weights a package with the string 00:20:36.050 --> 00:20:38.570 align:start position:0% weights a package with the string antennas<00:20:37.050> answer<00:20:37.410> you<00:20:37.560> can<00:20:37.710> see<00:20:37.860> how<00:20:37.980> they<00:20:38.160> can 00:20:38.570 --> 00:20:38.580 align:start position:0% antennas answer you can see how they can 00:20:38.580 --> 00:21:19.609 align:start position:0% antennas answer you can see how they can parse<00:20:38.880> it<00:20:39.030> Hodgman 00:21:19.609 --> 00:21:19.619 align:start position:0% 00:21:19.619 --> 00:21:22.799 align:start position:0% and<00:21:20.619> then<00:21:20.799> but<00:21:21.789> notice<00:21:22.119> that<00:21:22.179> both<00:21:22.450> of<00:21:22.509> them 00:21:22.799 --> 00:21:22.809 align:start position:0% and then but notice that both of them 00:21:22.809 --> 00:21:25.349 align:start position:0% and then but notice that both of them has<00:21:23.019> a<00:21:23.350> spoke<00:21:24.039> in<00:21:24.279> the<00:21:24.489> end<00:21:24.639> so<00:21:24.789> basically<00:21:25.149> that 00:21:25.349 --> 00:21:25.359 align:start position:0% has a spoke in the end so basically that 00:21:25.359 --> 00:21:27.359 align:start position:0% has a spoke in the end so basically that means<00:21:25.509> that<00:21:25.749> both<00:21:25.899> of<00:21:25.929> them<00:21:26.169> know<00:21:26.350> how<00:21:26.739> they 00:21:27.359 --> 00:21:27.369 align:start position:0% means that both of them know how they 00:21:27.369 --> 00:21:30.029 align:start position:0% means that both of them know how they referenced<00:21:27.850> in<00:21:27.970> the<00:21:28.090> invitation<00:21:28.779> so<00:21:29.590> then<00:21:29.919> we 00:21:30.029 --> 00:21:30.039 align:start position:0% referenced in the invitation so then we 00:21:30.039 --> 00:21:39.330 align:start position:0% referenced in the invitation so then we won't<00:21:30.190> have<00:21:30.279> a<00:21:37.200> now<00:21:38.200> and<00:21:38.679> we<00:21:38.769> have<00:21:38.919> always 00:21:39.330 --> 00:21:39.340 align:start position:0% won't have a now and we have always 00:21:39.340 --> 00:21:53.020 align:start position:0% won't have a now and we have always think 00:21:53.020 --> 00:21:53.030 align:start position:0% 00:21:53.030 --> 00:22:12.530 align:start position:0% which<00:22:02.810> will<00:22:03.810> be<00:22:10.250> you<00:22:11.250> have<00:22:11.430> as<00:22:11.640> an<00:22:11.880> example<00:22:11.970> a 00:22:12.530 --> 00:22:12.540 align:start position:0% which will be you have as an example a 00:22:12.540 --> 00:22:16.220 align:start position:0% which will be you have as an example a sample<00:22:13.530> trip<00:22:13.980> we<00:22:14.430> will<00:22:14.760> have<00:22:15.000> to<00:22:15.210> do<00:22:15.720> a<00:22:15.750> filter 00:22:16.220 --> 00:22:16.230 align:start position:0% sample trip we will have to do a filter 00:22:16.230 --> 00:22:18.530 align:start position:0% sample trip we will have to do a filter using<00:22:17.130> the<00:22:17.220> division<00:22:17.580> sound<00:22:17.820> and<00:22:18.300> then<00:22:18.420> our 00:22:18.530 --> 00:22:18.540 align:start position:0% using the division sound and then our 00:22:18.540 --> 00:22:24.320 align:start position:0% using the division sound and then our production<00:22:19.640> in<00:22:20.640> item<00:22:20.940> have<00:22:22.310> irrelevant<00:22:23.330> then 00:22:24.320 --> 00:22:24.330 align:start position:0% production in item have irrelevant then 00:22:24.330 --> 00:22:28.520 align:start position:0% production in item have irrelevant then the<00:22:25.050> mean<00:22:25.380> will<00:22:25.680> be<00:22:25.710> sent<00:22:26.310> in<00:22:26.520> but<00:22:27.150> if<00:22:27.390> we<00:22:27.630> want 00:22:28.520 --> 00:22:28.530 align:start position:0% the mean will be sent in but if we want 00:22:28.530 --> 00:22:33.610 align:start position:0% the mean will be sent in but if we want to<00:22:28.620> fit<00:22:28.860> around<00:22:29.040> the<00:22:29.400> earth<00:22:29.700> like<00:22:30.500> let's<00:22:31.500> say 00:22:33.610 --> 00:22:33.620 align:start position:0% to fit around the earth like let's say 00:22:33.620 --> 00:22:39.620 align:start position:0% to fit around the earth like let's say five<00:22:36.740> for<00:22:37.740> element<00:22:38.250> and<00:22:38.910> then<00:22:39.150> the<00:22:39.270> means<00:22:39.450> we 00:22:39.620 --> 00:22:39.630 align:start position:0% five for element and then the means we 00:22:39.630 --> 00:22:44.830 align:start position:0% five for element and then the means we change<00:22:39.660> into<00:22:40.670> more<00:22:41.670> smoothly<00:22:42.830> average<00:22:43.830> to<00:22:43.980> say 00:22:44.830 --> 00:22:44.840 align:start position:0% change into more smoothly average to say 00:22:44.840 --> 00:22:49.700 align:start position:0% change into more smoothly average to say I<00:22:46.190> almost<00:22:47.190> want<00:22:47.490> unit<00:22:47.870> this<00:22:48.870> is<00:22:48.930> normally<00:22:49.530> used 00:22:49.700 --> 00:22:49.710 align:start position:0% I almost want unit this is normally used 00:22:49.710 --> 00:22:55.060 align:start position:0% I almost want unit this is normally used in<00:22:49.890> order<00:22:50.070> to<00:22:50.250> as<00:22:50.430> I<00:22:50.580> said 00:22:55.060 --> 00:22:55.070 align:start position:0% 00:22:55.070 --> 00:22:57.610 align:start position:0% so<00:22:55.970> finally<00:22:56.660> the<00:22:56.780> tiny<00:22:56.990> Street<00:22:57.290> which<00:22:57.440> is<00:22:57.470> the 00:22:57.610 --> 00:22:57.620 align:start position:0% so finally the tiny Street which is the 00:22:57.620 --> 00:23:00.700 align:start position:0% so finally the tiny Street which is the one<00:22:57.890> where<00:22:58.400> we<00:22:59.270> reach<00:22:59.570> consensus<00:23:00.230> among<00:23:00.500> those 00:23:00.700 --> 00:23:00.710 align:start position:0% one where we reach consensus among those 00:23:00.710 --> 00:23:03.340 align:start position:0% one where we reach consensus among those are<00:23:01.010> values<00:23:01.610> that<00:23:01.640> witnesses<00:23:02.270> reported<00:23:02.750> so 00:23:03.340 --> 00:23:03.350 align:start position:0% are values that witnesses reported so 00:23:03.350 --> 00:23:04.870 align:start position:0% are values that witnesses reported so it's<00:23:03.560> gonna<00:23:03.710> it's<00:23:04.190> gonna<00:23:04.280> look<00:23:04.460> very<00:23:04.520> much 00:23:04.870 --> 00:23:04.880 align:start position:0% it's gonna it's gonna look very much 00:23:04.880 --> 00:23:07.630 align:start position:0% it's gonna it's gonna look very much like<00:23:04.940> the<00:23:05.240> regression<00:23:06.200> straight<00:23:06.620> but<00:23:06.920> this 00:23:07.630 --> 00:23:07.640 align:start position:0% like the regression straight but this 00:23:07.640 --> 00:23:11.500 align:start position:0% like the regression straight but this time<00:23:07.820> it's<00:23:08.120> gonna<00:23:08.240> be<00:23:08.420> run<00:23:08.600> by<00:23:09.080> minor<00:23:09.290> notes<00:23:10.510> so 00:23:11.500 --> 00:23:11.510 align:start position:0% time it's gonna be run by minor notes so 00:23:11.510 --> 00:23:13.590 align:start position:0% time it's gonna be run by minor notes so basically<00:23:11.810> it<00:23:12.170> takes<00:23:12.440> a<00:23:12.650> scheme<00:23:12.860> to<00:23:12.890> deal<00:23:13.250> the 00:23:13.590 --> 00:23:13.600 align:start position:0% basically it takes a scheme to deal the 00:23:13.600 --> 00:23:15.910 align:start position:0% basically it takes a scheme to deal the deck<00:23:14.600> the<00:23:14.810> data<00:23:15.020> points<00:23:15.410> that<00:23:15.440> business<00:23:15.770> is 00:23:15.910 --> 00:23:15.920 align:start position:0% deck the data points that business is 00:23:15.920 --> 00:23:17.620 align:start position:0% deck the data points that business is provided<00:23:16.370> from<00:23:16.730> the<00:23:16.790> aggregation<00:23:17.180> strengths 00:23:17.620 --> 00:23:17.630 align:start position:0% provided from the aggregation strengths 00:23:17.630 --> 00:23:20.320 align:start position:0% provided from the aggregation strengths and<00:23:18.200> introduces<00:23:18.830> proceed<00:23:19.340> over<00:23:19.490> the<00:23:20.180> output 00:23:20.320 --> 00:23:20.330 align:start position:0% and introduces proceed over the output 00:23:20.330 --> 00:23:22.330 align:start position:0% and introduces proceed over the output the<00:23:20.600> game<00:23:20.750> gets<00:23:20.930> written<00:23:21.080> two<00:23:21.320> books<00:23:21.470> and<00:23:21.800> one 00:23:22.330 --> 00:23:22.340 align:start position:0% the game gets written two books and one 00:23:22.340 --> 00:23:28.210 align:start position:0% the game gets written two books and one available<00:23:23.440> this<00:23:24.440> is<00:23:24.620> this<00:23:26.770> it's<00:23:27.770> very<00:23:27.830> similar 00:23:28.210 --> 00:23:28.220 align:start position:0% available this is this it's very similar 00:23:28.220 --> 00:23:30.190 align:start position:0% available this is this it's very similar to<00:23:28.370> the<00:23:28.550> previous<00:23:28.700> one<00:23:28.880> but<00:23:29.150> we<00:23:29.300> have<00:23:29.510> a<00:23:29.540> more 00:23:30.190 --> 00:23:30.200 align:start position:0% to the previous one but we have a more 00:23:30.200 --> 00:23:33.820 align:start position:0% to the previous one but we have a more harsh<00:23:30.680> internal<00:23:31.400> right<00:23:31.760> so<00:23:32.510> again<00:23:33.230> we<00:23:33.470> can<00:23:33.590> see 00:23:33.820 --> 00:23:33.830 align:start position:0% harsh internal right so again we can see 00:23:33.830 --> 00:23:36.520 align:start position:0% harsh internal right so again we can see how<00:23:34.100> this<00:23:34.580> future<00:23:34.940> is<00:23:35.000> important<00:23:35.660> then<00:23:35.960> nobody 00:23:36.520 --> 00:23:36.530 align:start position:0% how this future is important then nobody 00:23:36.530 --> 00:23:38.800 align:start position:0% how this future is important then nobody will<00:23:36.710> explain<00:23:37.010> values<00:23:37.490> notice<00:23:37.970> how<00:23:38.150> without 00:23:38.800 --> 00:23:38.810 align:start position:0% will explain values notice how without 00:23:38.810 --> 00:23:52.030 align:start position:0% will explain values notice how without the<00:23:39.080> filters<00:23:48.940> interesting<00:23:49.940> like<00:23:50.750> a<00:23:51.050> great 00:23:52.030 --> 00:23:52.040 align:start position:0% the filters interesting like a great 00:23:52.040 --> 00:23:59.010 align:start position:0% the filters interesting like a great integrity 00:23:59.010 --> 00:23:59.020 align:start position:0% 00:23:59.020 --> 00:24:04.240 align:start position:0% game<00:24:00.020> in<00:24:00.980> which<00:24:01.990> money<00:24:02.990> they<00:24:03.650> know<00:24:03.800> if<00:24:04.040> they 00:24:04.240 --> 00:24:04.250 align:start position:0% game in which money they know if they 00:24:04.250 --> 00:24:05.530 align:start position:0% game in which money they know if they haven't<00:24:04.640> organized<00:24:05.030> it<00:24:05.180> will<00:24:05.390> behave 00:24:05.530 --> 00:24:05.540 align:start position:0% haven't organized it will behave 00:24:05.540 --> 00:24:08.610 align:start position:0% haven't organized it will behave naturally<00:24:06.310> in<00:24:07.310> order<00:24:07.520> to<00:24:07.640> prototype<00:24:07.910> to 00:24:08.610 --> 00:24:08.620 align:start position:0% naturally in order to prototype to 00:24:08.620 --> 00:24:18.260 align:start position:0% naturally in order to prototype to maximize<00:24:09.620> the<00:24:09.770> profit<00:24:10.190> you<00:24:10.670> will<00:24:10.820> not<00:24:11.030> I<00:24:13.750> see 00:24:18.260 --> 00:24:18.270 align:start position:0% 00:24:18.270 --> 00:24:22.980 align:start position:0% and<00:24:19.289> also<00:24:20.340> what<00:24:21.340> we're<00:24:22.149> doing<00:24:22.419> is<00:24:22.510> like<00:24:22.659> most 00:24:22.980 --> 00:24:22.990 align:start position:0% and also what we're doing is like most 00:24:22.990 --> 00:24:25.560 align:start position:0% and also what we're doing is like most other<00:24:23.200> signal<00:24:23.710> in<00:24:23.950> this<00:24:24.039> last<00:24:24.340> stage<00:24:24.820> they<00:24:25.390> get 00:24:25.560 --> 00:24:25.570 align:start position:0% other signal in this last stage they get 00:24:25.570 --> 00:24:30.870 align:start position:0% other signal in this last stage they get slashed<00:24:28.020> why<00:24:29.020> it<00:24:29.080> is<00:24:29.320> really<00:24:29.830> important<00:24:30.429> and 00:24:30.870 --> 00:24:30.880 align:start position:0% slashed why it is really important and 00:24:30.880 --> 00:24:32.580 align:start position:0% slashed why it is really important and critical<00:24:31.059> because<00:24:31.450> they<00:24:31.870> read<00:24:32.260> intense 00:24:32.580 --> 00:24:32.590 align:start position:0% critical because they read intense 00:24:32.590 --> 00:24:34.799 align:start position:0% critical because they read intense whisper<00:24:32.770> to<00:24:33.070> be<00:24:33.279> tweeted<00:24:33.669> I<00:24:33.850> would<00:24:34.570> provide 00:24:34.799 --> 00:24:34.809 align:start position:0% whisper to be tweeted I would provide 00:24:34.809 --> 00:24:37.470 align:start position:0% whisper to be tweeted I would provide examples<00:24:35.409> understand<00:24:36.190> better<00:24:36.490> in<00:24:37.179> my<00:24:37.299> team 00:24:37.470 --> 00:24:37.480 align:start position:0% examples understand better in my team 00:24:37.480 --> 00:24:41.580 align:start position:0% examples understand better in my team way<00:24:37.720> we<00:24:38.049> have<00:24:38.340> a<00:24:39.340> gate<00:24:39.789> operator<00:24:40.149> it<00:24:40.659> means<00:24:40.899> we 00:24:41.580 --> 00:24:41.590 align:start position:0% way we have a gate operator it means we 00:24:41.590 --> 00:24:45.330 align:start position:0% way we have a gate operator it means we have<00:24:41.620> a<00:24:41.740> simple<00:24:42.610> an<00:24:42.820> array<00:24:43.149> of<00:24:43.950> different<00:24:44.950> with 00:24:45.330 --> 00:24:45.340 align:start position:0% have a simple an array of different with 00:24:45.340 --> 00:24:46.889 align:start position:0% have a simple an array of different with this<00:24:45.429> note<00:24:45.730> and<00:24:45.970> we<00:24:46.090> are<00:24:46.179> getting<00:24:46.450> only<00:24:46.630> the 00:24:46.889 --> 00:24:46.899 align:start position:0% this note and we are getting only the 00:24:46.899 --> 00:24:50.310 align:start position:0% this note and we are getting only the first<00:24:47.140> time<00:24:47.970> but<00:24:48.970> that's<00:24:49.210> me<00:24:49.390> it<00:24:49.750> means<00:24:49.990> like 00:24:50.310 --> 00:24:50.320 align:start position:0% first time but that's me it means like 00:24:50.320 --> 00:24:53.430 align:start position:0% first time but that's me it means like an<00:24:50.590> impact<00:24:51.279> reporter<00:24:52.059> and<00:24:52.840> you<00:24:52.990> will<00:24:53.110> be<00:24:53.200> some 00:24:53.430 --> 00:24:53.440 align:start position:0% an impact reporter and you will be some 00:24:53.440 --> 00:24:56.039 align:start position:0% an impact reporter and you will be some kind<00:24:53.710> of<00:24:53.799> a<00:24:54.070> witness<00:24:55.059> no<00:24:55.360> that<00:24:55.539> will<00:24:55.690> have<00:24:55.809> more 00:24:56.039 --> 00:24:56.049 align:start position:0% kind of a witness no that will have more 00:24:56.049 --> 00:25:00.120 align:start position:0% kind of a witness no that will have more power<00:24:56.500> influence<00:24:57.279> a<00:24:57.659> result<00:24:58.659> more<00:24:59.350> if<00:24:59.500> the 00:25:00.120 --> 00:25:00.130 align:start position:0% power influence a result more if the 00:25:00.130 --> 00:25:03.090 align:start position:0% power influence a result more if the chord<00:25:00.340> and<00:25:00.490> a<00:25:00.760> minor<00:25:01.289> choose<00:25:02.289> which<00:25:02.649> one<00:25:02.830> it<00:25:02.950> s 00:25:03.090 --> 00:25:03.100 align:start position:0% chord and a minor choose which one it s 00:25:03.100 --> 00:25:09.269 align:start position:0% chord and a minor choose which one it s the<00:25:03.250> first<00:25:03.279> he<00:25:03.789> can<00:25:07.110> then<00:25:08.110> analyze<00:25:08.590> how<00:25:08.919> is<00:25:09.100> the 00:25:09.269 --> 00:25:09.279 align:start position:0% the first he can then analyze how is the 00:25:09.279 --> 00:25:12.750 align:start position:0% the first he can then analyze how is the filter<00:25:09.760> gives<00:25:10.179> it<00:25:10.360> up<00:25:10.510> so<00:25:11.350> that<00:25:11.679> means<00:25:11.770> no<00:25:12.190> mean 00:25:12.750 --> 00:25:12.760 align:start position:0% filter gives it up so that means no mean 00:25:12.760 --> 00:25:25.909 align:start position:0% filter gives it up so that means no mean time<00:25:13.000> scripts<00:25:13.299> are<00:25:13.450> coming<00:25:13.840> so<00:25:14.500> a<00:25:24.360> similar 00:25:25.909 --> 00:25:25.919 align:start position:0% time scripts are coming so a similar 00:25:25.919 --> 00:25:29.960 align:start position:0% time scripts are coming so a similar reduced<00:25:26.919> average 00:25:29.960 --> 00:25:29.970 align:start position:0% 00:25:29.970 --> 00:25:33.070 align:start position:0% in<00:25:30.450> average<00:25:30.779> customer<00:25:31.409> again<00:25:31.799> so<00:25:32.519> you<00:25:32.580> just 00:25:33.070 --> 00:25:33.080 align:start position:0% in average customer again so you just 00:25:33.080 --> 00:25:49.820 align:start position:0% in average customer again so you just gotta<00:25:34.080> learn<00:25:34.379> to<00:25:34.549> fine-tune<00:25:35.549> them 00:25:49.820 --> 00:25:49.830 align:start position:0% 00:25:49.830 --> 00:25:55.120 align:start position:0% [Music] 00:25:55.120 --> 00:25:55.130 align:start position:0% 00:25:55.130 --> 00:26:27.540 align:start position:0% I<00:26:11.900> actually 00:26:27.540 --> 00:26:27.550 align:start position:0% 00:26:27.550 --> 00:26:31.760 align:start position:0% so<00:26:28.120> basically<00:26:29.400> this<00:26:30.400> is<00:26:30.580> this<00:26:31.060> is<00:26:31.240> using<00:26:31.540> the 00:26:31.760 --> 00:26:31.770 align:start position:0% so basically this is this is using the 00:26:31.770 --> 00:26:34.380 align:start position:0% so basically this is this is using the frontal<00:26:32.770> box<00:26:32.950> with<00:26:33.220> a<00:26:33.430> palette<00:26:33.760> retractable 00:26:34.380 --> 00:26:34.390 align:start position:0% frontal box with a palette retractable 00:26:34.390 --> 00:26:37.100 align:start position:0% frontal box with a palette retractable so<00:26:34.630> that<00:26:34.810> you<00:26:34.960> can<00:26:35.170> be<00:26:35.560> out<00:26:36.100> with<00:26:36.670> the<00:26:36.820> power 00:26:37.100 --> 00:26:37.110 align:start position:0% so that you can be out with the power 00:26:37.110 --> 00:26:41.310 align:start position:0% so that you can be out with the power projects<00:26:38.460> just<00:26:39.460> a<00:26:39.640> few<00:26:39.790> seconds<00:26:40.240> so<00:26:40.390> you<00:26:41.140> would 00:26:41.310 --> 00:26:41.320 align:start position:0% projects just a few seconds so you would 00:26:41.320 --> 00:26:45.930 align:start position:0% projects just a few seconds so you would start<00:26:41.770> just<00:26:42.070> by<00:26:42.280> doing<00:26:43.410> you<00:26:44.410> know<00:26:44.560> from<00:26:45.490> home 00:26:45.930 --> 00:26:45.940 align:start position:0% start just by doing you know from home 00:26:45.940 --> 00:26:51.510 align:start position:0% start just by doing you know from home and<00:26:46.330> walks<00:26:46.990> with<00:26:47.560> net<00:26:48.370> upwards<00:26:49.770> means<00:26:50.770> I<00:26:51.190> will 00:26:51.510 --> 00:26:51.520 align:start position:0% and walks with net upwards means I will 00:26:51.520 --> 00:26:53.430 align:start position:0% and walks with net upwards means I will not<00:26:51.640> do<00:26:51.790> it<00:26:51.850> right<00:26:51.970> now<00:26:52.210> because<00:26:52.540> it<00:26:52.900> takes<00:26:52.930> a 00:26:53.430 --> 00:26:53.440 align:start position:0% not do it right now because it takes a 00:26:53.440 --> 00:26:57.560 align:start position:0% not do it right now because it takes a minute<00:26:53.950> or<00:26:54.130> so<00:26:54.550> and<00:26:55.210> we're<00:26:55.630> not<00:26:55.810> that<00:26:55.990> time<00:26:56.830> so 00:26:57.560 --> 00:26:57.570 align:start position:0% minute or so and we're not that time so 00:26:57.570 --> 00:27:00.840 align:start position:0% minute or so and we're not that time so basically<00:26:58.570> this<00:26:59.110> is<00:26:59.440> our<00:26:59.890> women<00:27:00.340> request 00:27:00.840 --> 00:27:00.850 align:start position:0% basically this is our women request 00:27:00.850 --> 00:27:03.540 align:start position:0% basically this is our women request which<00:27:01.360> is<00:27:01.510> now<00:27:01.690> a<00:27:02.170> small<00:27:02.710> javascript<00:27:03.250> file 00:27:03.540 --> 00:27:03.550 align:start position:0% which is now a small javascript file 00:27:03.550 --> 00:27:06.900 align:start position:0% which is now a small javascript file where<00:27:03.970> I<00:27:04.210> imported<00:27:04.900> the<00:27:04.930> women<00:27:05.740> because<00:27:06.040> like 00:27:06.900 --> 00:27:06.910 align:start position:0% where I imported the women because like 00:27:06.910 --> 00:27:10.490 align:start position:0% where I imported the women because like me<00:27:07.150> okay<00:27:07.990> one<00:27:08.620> source<00:27:09.010> for<00:27:09.250> bitstamp<00:27:09.730> another 00:27:10.490 --> 00:27:10.500 align:start position:0% me okay one source for bitstamp another 00:27:10.500 --> 00:27:14.660 align:start position:0% me okay one source for bitstamp another pointless<00:27:11.500> and<00:27:12.190> then<00:27:12.610> I<00:27:12.820> got<00:27:13.780> the<00:27:13.990> applicator 00:27:14.660 --> 00:27:14.670 align:start position:0% pointless and then I got the applicator 00:27:14.670 --> 00:27:17.700 align:start position:0% pointless and then I got the applicator with<00:27:15.670> dolly<00:27:16.000> and<00:27:16.510> then<00:27:16.720> I<00:27:16.990> do<00:27:17.050> everything 00:27:17.700 --> 00:27:17.710 align:start position:0% with dolly and then I do everything 00:27:17.710 --> 00:27:18.360 align:start position:0% with dolly and then I do everything together 00:27:18.360 --> 00:27:18.370 align:start position:0% together 00:27:18.370 --> 00:27:21.540 align:start position:0% together yeah<00:27:19.030> like<00:27:19.840> this<00:27:20.020> human<00:27:20.530> and<00:27:20.710> request<00:27:21.070> at 00:27:21.540 --> 00:27:21.550 align:start position:0% yeah like this human and request at 00:27:21.550 --> 00:27:23.940 align:start position:0% yeah like this human and request at source<00:27:22.000> but<00:27:22.300> Saddam<00:27:22.600> has<00:27:22.870> started<00:27:23.230> to<00:27:23.380> test<00:27:23.620> I 00:27:23.940 --> 00:27:23.950 align:start position:0% source but Saddam has started to test I 00:27:23.950 --> 00:27:26.220 align:start position:0% source but Saddam has started to test I said<00:27:24.310> never<00:27:24.430> get<00:27:24.700> arrested<00:27:25.060> Natalia<00:27:25.690> and<00:27:25.840> then 00:27:26.220 --> 00:27:26.230 align:start position:0% said never get arrested Natalia and then 00:27:26.230 --> 00:27:27.960 align:start position:0% said never get arrested Natalia and then I<00:27:26.320> decide<00:27:26.650> or<00:27:26.980> am<00:27:27.160> I<00:27:27.280> want<00:27:27.550> this<00:27:27.700> they 00:27:27.960 --> 00:27:27.970 align:start position:0% I decide or am I want this they 00:27:27.970 --> 00:27:32.670 align:start position:0% I decide or am I want this they requested<00:27:28.570> me<00:27:29.070> to<00:27:30.070> be<00:27:30.840> performed<00:27:31.840> by<00:27:31.990> four 00:27:32.670 --> 00:27:32.680 align:start position:0% requested me to be performed by four 00:27:32.680 --> 00:27:34.800 align:start position:0% requested me to be performed by four different<00:27:32.950> witnesses<00:27:33.430> Frank<00:27:34.270> McCourt 00:27:34.800 --> 00:27:34.810 align:start position:0% different witnesses Frank McCourt 00:27:34.810 --> 00:27:37.800 align:start position:0% different witnesses Frank McCourt different<00:27:35.440> nodes<00:27:35.650> in<00:27:35.860> the<00:27:35.950> network<00:27:36.430> last<00:27:37.120> for 00:27:37.800 --> 00:27:37.810 align:start position:0% different nodes in the network last for 00:27:37.810 --> 00:27:39.210 align:start position:0% different nodes in the network last for backup 00:27:39.210 --> 00:27:39.220 align:start position:0% backup 00:27:39.220 --> 00:27:41.100 align:start position:0% backup that's<00:27:39.640> expect<00:27:40.300> better<00:27:40.450> explaining<00:27:41.020> a 00:27:41.100 --> 00:27:41.110 align:start position:0% that's expect better explaining a 00:27:41.110 --> 00:27:44.670 align:start position:0% that's expect better explaining a documentation<00:27:41.530> clustering<00:27:42.690> then<00:27:43.690> you<00:27:44.530> can 00:27:44.670 --> 00:27:44.680 align:start position:0% documentation clustering then you can 00:27:44.680 --> 00:27:48.330 align:start position:0% documentation clustering then you can set<00:27:44.920> the<00:27:44.950> peace<00:27:45.340> for<00:27:45.730> all<00:27:46.090> the<00:27:46.890> stages<00:27:47.890> or 00:27:48.330 --> 00:27:48.340 align:start position:0% set the peace for all the stages or 00:27:48.340 --> 00:27:51.270 align:start position:0% set the peace for all the stages or creating<00:27:48.760> incentives<00:27:49.030> for<00:27:49.890> the<00:27:50.890> minors 00:27:51.270 --> 00:27:51.280 align:start position:0% creating incentives for the minors 00:27:51.280 --> 00:27:54.630 align:start position:0% creating incentives for the minors including<00:27:51.490> those<00:27:52.740> those<00:27:53.740> transactions<00:27:54.370> you 00:27:54.630 --> 00:27:54.640 align:start position:0% including those those transactions you 00:27:54.640 --> 00:27:57.650 align:start position:0% including those those transactions you do<00:27:55.060> box<00:27:55.480> and<00:27:55.960> you<00:27:56.500> can<00:27:56.680> send<00:27:57.220> this<00:27:57.310> case 00:27:57.650 --> 00:27:57.660 align:start position:0% do box and you can send this case 00:27:57.660 --> 00:28:00.380 align:start position:0% do box and you can send this case in<00:27:57.900> this<00:27:58.020> case<00:27:58.290> there's<00:27:59.190> a<00:27:59.280> zero<00:27:59.520> within<00:28:00.090> which 00:28:00.380 --> 00:28:00.390 align:start position:0% in this case there's a zero within which 00:28:00.390 --> 00:28:02.030 align:start position:0% in this case there's a zero within which means<00:28:00.630> that<00:28:00.900> the<00:28:01.230> Reapers<00:28:01.590> can<00:28:01.830> be 00:28:02.030 --> 00:28:02.040 align:start position:0% means that the Reapers can be 00:28:02.040 --> 00:28:05.300 align:start position:0% means that the Reapers can be immediately<00:28:03.260> perform<00:28:04.260> enemy<00:28:04.770> doesn't<00:28:05.040> need 00:28:05.300 --> 00:28:05.310 align:start position:0% immediately perform enemy doesn't need 00:28:05.310 --> 00:28:07.820 align:start position:0% immediately perform enemy doesn't need to<00:28:05.460> be<00:28:05.610> known<00:28:06.180> in<00:28:06.210> the<00:28:06.450> future<00:28:06.900> although<00:28:07.290> for 00:28:07.820 --> 00:28:07.830 align:start position:0% to be known in the future although for 00:28:07.830 --> 00:28:11.420 align:start position:0% to be known in the future although for many<00:28:08.490> for<00:28:09.120> many<00:28:09.240> use<00:28:09.510> cases<00:28:09.650> it's<00:28:10.650> much<00:28:11.100> more 00:28:11.420 --> 00:28:11.430 align:start position:0% many for many use cases it's much more 00:28:11.430 --> 00:28:13.130 align:start position:0% many for many use cases it's much more convenient<00:28:11.790> to<00:28:12.000> have<00:28:12.180> it<00:28:12.210> scheduled<00:28:12.810> for<00:28:13.020> the 00:28:13.130 --> 00:28:13.140 align:start position:0% convenient to have it scheduled for the 00:28:13.140 --> 00:28:16.430 align:start position:0% convenient to have it scheduled for the future<00:28:13.500> or<00:28:13.890> we<00:28:14.160> can<00:28:14.510> delay<00:28:15.510> a<00:28:15.540> publication<00:28:16.140> of 00:28:16.430 --> 00:28:16.440 align:start position:0% future or we can delay a publication of 00:28:16.440 --> 00:28:20.330 align:start position:0% future or we can delay a publication of their<00:28:16.650> request<00:28:17.130> and<00:28:17.400> yes<00:28:18.590> zero<00:28:19.590> and<00:28:19.890> don't 00:28:20.330 --> 00:28:20.340 align:start position:0% their request and yes zero and don't 00:28:20.340 --> 00:28:23.540 align:start position:0% their request and yes zero and don't send<00:28:20.610> it<00:28:20.790> from<00:28:21.000> if<00:28:21.450> you<00:28:21.690> win<00:28:22.080> it<00:28:22.290> until<00:28:22.620> until 00:28:23.540 --> 00:28:23.550 align:start position:0% send it from if you win it until until 00:28:23.550 --> 00:28:29.420 align:start position:0% send it from if you win it until until we<00:28:23.610> know<00:28:23.820> it<00:28:24.240> can<00:28:24.480> be<00:28:24.510> it<00:28:25.140> can<00:28:25.200> be<00:28:26.720> so<00:28:28.430> that's 00:28:29.420 --> 00:28:29.430 align:start position:0% we know it can be it can be so that's 00:28:29.430 --> 00:28:34.280 align:start position:0% we know it can be it can be so that's that's<00:28:29.820> in<00:28:30.180> a<00:28:30.450> request<00:28:30.900> or<00:28:32.390> or<00:28:33.390> making<00:28:34.020> that 00:28:34.280 --> 00:28:34.290 align:start position:0% that's in a request or or making that 00:28:34.290 --> 00:28:55.040 align:start position:0% that's in a request or or making that word<00:28:46.940> so<00:28:48.050> we<00:28:49.050> asked<00:28:49.320> to<00:28:49.770> return<00:28:50.280> fire 00:28:55.040 --> 00:28:55.050 align:start position:0% 00:28:55.050 --> 00:28:57.110 align:start position:0% [Music] 00:28:57.110 --> 00:28:57.120 align:start position:0% [Music] 00:28:57.120 --> 00:29:00.300 align:start position:0% [Music] so<00:28:58.120> when<00:28:58.630> you<00:28:58.840> when<00:28:59.230> you<00:28:59.350> do<00:28:59.530> compile<00:28:59.890> it<00:29:00.070> all 00:29:00.300 --> 00:29:00.310 align:start position:0% so when you when you do compile it all 00:29:00.310 --> 00:29:04.680 align:start position:0% so when you when you do compile it all this<00:29:01.030> is<00:29:01.090> actually<00:29:01.630> just<00:29:01.780> winning<00:29:02.200> no<00:29:03.540> this<00:29:04.540> is 00:29:04.680 --> 00:29:04.690 align:start position:0% this is actually just winning no this is 00:29:04.690 --> 00:29:06.690 align:start position:0% this is actually just winning no this is big<00:29:04.900> in<00:29:05.140> the<00:29:05.380> name<00:29:05.500> be<00:29:05.680> compressed<00:29:06.040> this<00:29:06.520> is 00:29:06.690 --> 00:29:06.700 align:start position:0% big in the name be compressed this is 00:29:06.700 --> 00:29:09.540 align:start position:0% big in the name be compressed this is just<00:29:06.910> doing<00:29:07.030> a<00:29:07.480> note<00:29:07.990> if<00:29:08.650> compress<00:29:09.070> the<00:29:09.250> years 00:29:09.540 --> 00:29:09.550 align:start position:0% just doing a note if compress the years 00:29:09.550 --> 00:29:12.480 align:start position:0% just doing a note if compress the years it's<00:29:10.120> run<00:29:10.480> in<00:29:10.630> 2000<00:29:11.170> and<00:29:11.440> when<00:29:11.800> the<00:29:11.920> javascript 00:29:12.480 --> 00:29:12.490 align:start position:0% it's run in 2000 and when the javascript 00:29:12.490 --> 00:29:15.150 align:start position:0% it's run in 2000 and when the javascript is<00:29:12.670> run<00:29:13.030> is<00:29:13.330> producing<00:29:13.840> the<00:29:14.080> rain<00:29:14.230> okay 00:29:15.150 --> 00:29:15.160 align:start position:0% is run is producing the rain okay 00:29:15.160 --> 00:29:18.600 align:start position:0% is run is producing the rain okay so<00:29:15.490> when<00:29:15.700> it<00:29:16.680> creates<00:29:17.680> the<00:29:17.920> java<00:29:18.130> screen<00:29:18.430> and 00:29:18.600 --> 00:29:18.610 align:start position:0% so when it creates the java screen and 00:29:18.610 --> 00:29:22.470 align:start position:0% so when it creates the java screen and turn<00:29:18.850> that<00:29:19.090> into<00:29:19.480> engraven<00:29:20.470> it's<00:29:21.070> it's<00:29:21.550> doing 00:29:22.470 --> 00:29:22.480 align:start position:0% turn that into engraven it's it's doing 00:29:22.480 --> 00:29:24.660 align:start position:0% turn that into engraven it's it's doing some<00:29:22.810> static<00:29:23.170> analysis<00:29:23.650> and<00:29:24.130> it<00:29:24.250> can<00:29:24.430> tell 00:29:24.660 --> 00:29:24.670 align:start position:0% some static analysis and it can tell 00:29:24.670 --> 00:29:26.870 align:start position:0% some static analysis and it can tell that<00:29:24.910> the<00:29:25.030> sources<00:29:25.480> are<00:29:25.720> even<00:29:26.410> flows 00:29:26.870 --> 00:29:26.880 align:start position:0% that the sources are even flows 00:29:26.880 --> 00:29:29.160 align:start position:0% that the sources are even flows fabricators<00:29:27.880> given<00:29:28.240> flow<00:29:28.450> data<00:29:28.720> is<00:29:28.990> very 00:29:29.160 --> 00:29:29.170 align:start position:0% fabricators given flow data is very 00:29:29.170 --> 00:29:31.080 align:start position:0% fabricators given flow data is very focused<00:29:29.680> we<00:29:29.980> can<00:29:30.100> change<00:29:30.340> and<00:29:30.580> we<00:29:30.700> can<00:29:30.880> see 00:29:31.080 --> 00:29:31.090 align:start position:0% focused we can change and we can see 00:29:31.090 --> 00:29:34.950 align:start position:0% focused we can change and we can see here<00:29:31.630> what<00:29:31.930> learns<00:29:32.350> our<00:29:32.910> type<00:29:33.910> change<00:29:34.540> so<00:29:34.930> that 00:29:34.950 --> 00:29:34.960 align:start position:0% here what learns our type change so that 00:29:34.960 --> 00:29:37.470 align:start position:0% here what learns our type change so that we<00:29:35.380> make<00:29:35.890> sure<00:29:35.920> that<00:29:36.160> we<00:29:36.640> are<00:29:36.760> doing<00:29:36.910> things 00:29:37.470 --> 00:29:37.480 align:start position:0% we make sure that we are doing things 00:29:37.480 --> 00:29:40.220 align:start position:0% we make sure that we are doing things right<00:29:37.660> and<00:29:38.050> that<00:29:38.290> the<00:29:38.470> final<00:29:38.920> type<00:29:39.580> will<00:29:40.090> be 00:29:40.220 --> 00:29:40.230 align:start position:0% right and that the final type will be 00:29:40.230 --> 00:29:44.220 align:start position:0% right and that the final type will be one<00:29:41.230> thing<00:29:41.380> that<00:29:41.590> we<00:29:41.770> can<00:29:42.060> assume<00:29:43.060> from<00:29:43.330> from 00:29:44.220 --> 00:29:44.230 align:start position:0% one thing that we can assume from from 00:29:44.230 --> 00:29:51.260 align:start position:0% one thing that we can assume from from from<00:29:46.680> solidity<00:29:47.680> so<00:29:48.460> what<00:29:49.030> what<00:29:49.600> is<00:29:49.810> d<00:29:50.160> he's 00:29:51.260 --> 00:29:51.270 align:start position:0% from solidity so what what is d he's 00:29:51.270 --> 00:29:57.560 align:start position:0% from solidity so what what is d he's taking<00:29:52.270> a<00:29:52.540> nap<00:29:52.750> on<00:29:53.110> firing<00:29:53.710> in<00:29:53.950> through<00:29:54.160> in 00:29:57.560 --> 00:29:57.570 align:start position:0% 00:29:57.570 --> 00:30:00.450 align:start position:0% into<00:29:58.570> random<00:29:58.960> byte<00:29:59.200> code<00:29:59.440> and<00:29:59.650> putting<00:30:00.310> that 00:30:00.450 --> 00:30:00.460 align:start position:0% into random byte code and putting that 00:30:00.460 --> 00:30:05.340 align:start position:0% into random byte code and putting that inside<00:30:00.880> our<00:30:01.390> contracts<00:30:02.160> older<00:30:03.360> as<00:30:04.360> these<00:30:04.780> so 00:30:05.340 --> 00:30:05.350 align:start position:0% inside our contracts older as these so 00:30:05.350 --> 00:30:07.980 align:start position:0% inside our contracts older as these so this<00:30:05.590> is<00:30:05.770> a<00:30:05.800> Salinas<00:30:06.280> contract<00:30:06.790> that<00:30:07.270> has<00:30:07.630> the 00:30:07.980 --> 00:30:07.990 align:start position:0% this is a Salinas contract that has the 00:30:07.990 --> 00:30:11.250 align:start position:0% this is a Salinas contract that has the random<00:30:08.320> bytes<00:30:08.640> inside<00:30:09.640> so<00:30:10.270> if<00:30:10.630> we<00:30:10.840> instantiate 00:30:11.250 --> 00:30:11.260 align:start position:0% random bytes inside so if we instantiate 00:30:11.260 --> 00:30:13.740 align:start position:0% random bytes inside so if we instantiate these<00:30:11.890> in<00:30:12.310> our<00:30:12.490> salinity<00:30:13.180> with<00:30:13.420> salinity 00:30:13.740 --> 00:30:13.750 align:start position:0% these in our salinity with salinity 00:30:13.750 --> 00:30:15.840 align:start position:0% these in our salinity with salinity contracts<00:30:14.260> we<00:30:14.740> have<00:30:14.890> the<00:30:15.010> bytes<00:30:15.250> and<00:30:15.550> we<00:30:15.700> can 00:30:15.840 --> 00:30:15.850 align:start position:0% contracts we have the bytes and we can 00:30:15.850 --> 00:30:18.720 align:start position:0% contracts we have the bytes and we can send<00:30:16.180> that<00:30:16.240> into<00:30:16.870> into<00:30:17.710> the<00:30:17.830> double<00:30:18.160> bi<00:30:18.280> to<00:30:18.430> the 00:30:18.720 --> 00:30:18.730 align:start position:0% send that into into the double bi to the 00:30:18.730 --> 00:30:20.340 align:start position:0% send that into into the double bi to the winner<00:30:18.910> which<00:30:19.150> interface<00:30:19.660> for<00:30:19.960> it<00:30:20.080> to<00:30:20.200> be 00:30:20.340 --> 00:30:20.350 align:start position:0% winner which interface for it to be 00:30:20.350 --> 00:30:24.660 align:start position:0% winner which interface for it to be resolved<00:30:21.160> by<00:30:21.400> the<00:30:21.840> winner<00:30:22.840> so<00:30:23.350> to<00:30:23.890> use<00:30:24.190> it 00:30:24.660 --> 00:30:24.670 align:start position:0% resolved by the winner so to use it 00:30:24.670 --> 00:30:26.760 align:start position:0% resolved by the winner so to use it we<00:30:24.940> simulate<00:30:25.180> for<00:30:25.600> example<00:30:26.050> this<00:30:26.200> is<00:30:26.380> a<00:30:26.410> very 00:30:26.760 --> 00:30:26.770 align:start position:0% we simulate for example this is a very 00:30:26.770 --> 00:30:30.300 align:start position:0% we simulate for example this is a very very<00:30:27.040> simple<00:30:27.880> use<00:30:28.510> case<00:30:28.800> which<00:30:29.800> is<00:30:29.980> a<00:30:30.070> prize 00:30:30.300 --> 00:30:30.310 align:start position:0% very simple use case which is a prize 00:30:30.310 --> 00:30:32.490 align:start position:0% very simple use case which is a prize build<00:30:30.640> using<00:30:30.970> win<00:30:31.240> that<00:30:31.450> so<00:30:31.720> what<00:30:32.110> we<00:30:32.230> need<00:30:32.380> to 00:30:32.490 --> 00:30:32.500 align:start position:0% build using win that so what we need to 00:30:32.500 --> 00:30:34.560 align:start position:0% build using win that so what we need to do<00:30:32.590> is<00:30:32.740> import<00:30:33.100> in<00:30:33.310> the<00:30:33.340> day<00:30:33.910> using<00:30:34.300> women 00:30:34.560 --> 00:30:34.570 align:start position:0% do is import in the day using women 00:30:34.570 --> 00:30:37.590 align:start position:0% do is import in the day using women library<00:30:35.130> and<00:30:36.130> saying<00:30:36.430> contract<00:30:36.910> recipe<00:30:37.360> is 00:30:37.590 --> 00:30:37.600 align:start position:0% library and saying contract recipe is 00:30:37.600 --> 00:30:41.610 align:start position:0% library and saying contract recipe is using<00:30:38.020> women<00:30:38.350> then<00:30:39.010> that<00:30:39.580> by<00:30:40.540> emergence<00:30:41.410> we 00:30:41.610 --> 00:30:41.620 align:start position:0% using women then that by emergence we 00:30:41.620 --> 00:30:43.770 align:start position:0% using women then that by emergence we are<00:30:41.800> getting<00:30:42.160> a<00:30:42.340> lot<00:30:42.580> of<00:30:42.610> methods<00:30:43.120> that<00:30:43.450> we<00:30:43.750> can 00:30:43.770 --> 00:30:43.780 align:start position:0% are getting a lot of methods that we can 00:30:43.780 --> 00:30:47.880 align:start position:0% are getting a lot of methods that we can use<00:30:43.930> to<00:30:44.350> control<00:30:44.650> the<00:30:46.050> vigorous<00:30:47.050> lifecycle 00:30:47.880 --> 00:30:47.890 align:start position:0% use to control the vigorous lifecycle 00:30:47.890 --> 00:30:51.000 align:start position:0% use to control the vigorous lifecycle sending<00:30:48.340> requests<00:30:49.300> having<00:30:50.290> their<00:30:50.530> their 00:30:51.000 --> 00:30:51.010 align:start position:0% sending requests having their their 00:30:51.010 --> 00:30:55.590 align:start position:0% sending requests having their their souls<00:30:52.170> rent<00:30:53.170> and<00:30:53.470> so<00:30:53.620> on<00:30:53.800> so<00:30:54.210> here<00:30:55.210> we<00:30:55.570> are 00:30:55.590 --> 00:30:55.600 align:start position:0% souls rent and so on so here we are 00:30:55.600 --> 00:30:58.740 align:start position:0% souls rent and so on so here we are instantiating<00:30:56.230> their<00:30:56.950> request<00:30:57.730> we<00:30:58.300> need<00:30:58.630> to 00:30:58.740 --> 00:30:58.750 align:start position:0% instantiating their request we need to 00:30:58.750 --> 00:31:04.590 align:start position:0% instantiating their request we need to embrace<00:30:58.870> request<00:30:59.440> body<00:31:00.840> and<00:31:01.840> then<00:31:03.180> what<00:31:04.180> we<00:31:04.450> do 00:31:04.590 --> 00:31:04.600 align:start position:0% embrace request body and then what we do 00:31:04.600 --> 00:31:07.530 align:start position:0% embrace request body and then what we do is<00:31:04.810> send<00:31:05.470> in<00:31:05.590> the<00:31:05.740> request<00:31:06.100> like<00:31:06.400> this<00:31:06.640> we<00:31:07.330> met 00:31:07.530 --> 00:31:07.540 align:start position:0% is send in the request like this we met 00:31:07.540 --> 00:31:10.230 align:start position:0% is send in the request like this we met was<00:31:07.720> request<00:31:08.170> we<00:31:08.440> pass<00:31:08.650> the<00:31:08.800> request<00:31:09.160> and<00:31:09.400> they 00:31:10.230 --> 00:31:10.240 align:start position:0% was request we pass the request and they 00:31:10.240 --> 00:31:13.680 align:start position:0% was request we pass the request and they feel<00:31:10.510> that<00:31:11.140> you<00:31:11.620> want<00:31:11.830> to<00:31:11.980> want<00:31:12.280> to<00:31:12.430> set<00:31:12.670> for<00:31:13.330> as 00:31:13.680 --> 00:31:13.690 align:start position:0% feel that you want to want to set for as 00:31:13.690 --> 00:31:17.070 align:start position:0% feel that you want to want to set for as I<00:31:13.840> we<00:31:14.080> work<00:31:14.350> for<00:31:14.710> that<00:31:15.040> rich<00:31:15.340> notes<00:31:15.730> to<00:31:16.480> relay 00:31:17.070 --> 00:31:17.080 align:start position:0% I we work for that rich notes to relay 00:31:17.080 --> 00:31:20.360 align:start position:0% I we work for that rich notes to relay the<00:31:17.680> requests<00:31:18.040> into<00:31:18.280> into<00:31:18.820> weather<00:31:19.000> and<00:31:19.300> then 00:31:20.360 --> 00:31:20.370 align:start position:0% the requests into into weather and then 00:31:20.370 --> 00:31:23.610 align:start position:0% the requests into into weather and then when<00:31:21.370> the<00:31:21.520> result<00:31:22.030> is<00:31:22.150> ready<00:31:22.440> which<00:31:23.440> is 00:31:23.610 --> 00:31:23.620 align:start position:0% when the result is ready which is 00:31:23.620 --> 00:31:26.820 align:start position:0% when the result is ready which is guarded<00:31:23.950> by<00:31:24.160> this<00:31:24.340> modifier<00:31:25.050> we<00:31:26.050> can<00:31:26.290> read<00:31:26.680> the 00:31:26.820 --> 00:31:26.830 align:start position:0% guarded by this modifier we can read the 00:31:26.830 --> 00:31:29.550 align:start position:0% guarded by this modifier we can read the result<00:31:27.310> okay<00:31:27.790> we<00:31:28.060> read<00:31:28.270> the<00:31:28.420> result<00:31:28.780> within<00:31:29.110> a 00:31:29.550 --> 00:31:29.560 align:start position:0% result okay we read the result within a 00:31:29.560 --> 00:31:32.310 align:start position:0% result okay we read the result within a structure<00:31:30.160> focus<00:31:30.640> open<00:31:31.270> system<00:31:31.750> algebraic 00:31:32.310 --> 00:31:32.320 align:start position:0% structure focus open system algebraic 00:31:32.320 --> 00:31:35.340 align:start position:0% structure focus open system algebraic and<00:31:32.560> the<00:31:33.100> time<00:31:33.750> allows<00:31:34.750> your<00:31:34.780> mother's 00:31:35.340 --> 00:31:35.350 align:start position:0% and the time allows your mother's 00:31:35.350 --> 00:31:40.320 align:start position:0% and the time allows your mother's recipes<00:31:35.980> will<00:31:36.820> resemble<00:31:38.490> that<00:31:39.490> if<00:31:39.850> we<00:31:40.030> do<00:31:40.180> is 00:31:40.320 --> 00:31:40.330 align:start position:0% recipes will resemble that if we do is 00:31:40.330 --> 00:31:42.600 align:start position:0% recipes will resemble that if we do is okay<00:31:40.630> we<00:31:40.810> can<00:31:40.960> know<00:31:41.110> that<00:31:41.380> we<00:31:41.650> got<00:31:42.130> an<00:31:42.370> actual 00:31:42.600 --> 00:31:42.610 align:start position:0% okay we can know that we got an actual 00:31:42.610 --> 00:31:45.720 align:start position:0% okay we can know that we got an actual result<00:31:43.450> there<00:31:43.720> was<00:31:43.900> no<00:31:44.140> failure<00:31:44.710> or<00:31:45.190> if 00:31:45.720 --> 00:31:45.730 align:start position:0% result there was no failure or if 00:31:45.730 --> 00:31:47.580 align:start position:0% result there was no failure or if something<00:31:46.300> failed<00:31:46.600> because<00:31:46.840> they<00:31:47.200> gave<00:31:47.380> me 00:31:47.580 --> 00:31:47.590 align:start position:0% something failed because they gave me 00:31:47.590 --> 00:31:50.760 align:start position:0% something failed because they gave me ice<00:31:47.770> pain<00:31:48.220> or<00:31:48.610> anything<00:31:49.300> like<00:31:49.570> that<00:31:49.630> we<00:31:50.290> can<00:31:50.530> go 00:31:50.760 --> 00:31:50.770 align:start position:0% ice pain or anything like that we can go 00:31:50.770 --> 00:31:52.370 align:start position:0% ice pain or anything like that we can go into<00:31:51.040> a 00:31:52.370 --> 00:31:52.380 align:start position:0% into a 00:31:52.380 --> 00:31:56.659 align:start position:0% into a all<00:31:52.950> birthdays<00:31:54.260> so<00:31:55.260> much<00:31:55.470> weaker<00:31:55.740> from<00:31:56.220> from 00:31:56.659 --> 00:31:56.669 align:start position:0% all birthdays so much weaker from from 00:31:56.669 --> 00:32:00.860 align:start position:0% all birthdays so much weaker from from that<00:31:56.820> situation<00:31:57.000> I<00:31:59.120> used<00:32:00.120> to<00:32:00.240> think<00:32:00.480> of<00:32:00.630> this 00:32:00.860 --> 00:32:00.870 align:start position:0% that situation I used to think of this 00:32:00.870 --> 00:32:04.220 align:start position:0% that situation I used to think of this as<00:32:01.169> an<00:32:01.620> option<00:32:02.010> for<00:32:02.039> if<00:32:02.730> I<00:32:03.330> cannot<00:32:03.750> resolve 00:32:04.220 --> 00:32:04.230 align:start position:0% as an option for if I cannot resolve 00:32:04.230 --> 00:32:06.890 align:start position:0% as an option for if I cannot resolve this<00:32:04.530> contract<00:32:05.130> in<00:32:05.669> a<00:32:05.820> completely<00:32:06.720> flat 00:32:06.890 --> 00:32:06.900 align:start position:0% this contract in a completely flat 00:32:06.900 --> 00:32:09.650 align:start position:0% this contract in a completely flat trustless<00:32:07.650> manner<00:32:07.950> you<00:32:08.610> see<00:32:08.789> we<00:32:09.030> met<00:32:09.360> in<00:32:09.570> an 00:32:09.650 --> 00:32:09.660 align:start position:0% trustless manner you see we met in an 00:32:09.660 --> 00:32:12.710 align:start position:0% trustless manner you see we met in an automatic<00:32:09.990> way<00:32:10.200> with<00:32:10.950> no<00:32:11.250> latency<00:32:11.880> at<00:32:12.270> all<00:32:12.419> I 00:32:12.710 --> 00:32:12.720 align:start position:0% automatic way with no latency at all I 00:32:12.720 --> 00:32:15.890 align:start position:0% automatic way with no latency at all I can<00:32:13.169> make<00:32:13.950> this<00:32:14.160> price<00:32:14.460> in<00:32:14.700> half<00:32:15.000> and<00:32:15.299> really 00:32:15.890 --> 00:32:15.900 align:start position:0% can make this price in half and really 00:32:15.900 --> 00:32:19.789 align:start position:0% can make this price in half and really the<00:32:16.679> agency<00:32:17.460> that<00:32:18.059> we<00:32:18.299> work<00:32:18.539> great<00:32:19.470> if 00:32:19.789 --> 00:32:19.799 align:start position:0% the agency that we work great if 00:32:19.799 --> 00:32:24.580 align:start position:0% the agency that we work great if something<00:32:20.250> fails<00:32:20.460> I<00:32:20.820> can<00:32:21.450> go<00:32:21.600> into<00:32:21.960> some 00:32:24.580 --> 00:32:24.590 align:start position:0% something fails I can go into some 00:32:24.590 --> 00:32:28.310 align:start position:0% something fails I can go into some something<00:32:26.210> like<00:32:27.210> iron<00:32:27.480> or<00:32:27.720> something<00:32:28.230> like 00:32:28.310 --> 00:32:28.320 align:start position:0% something like iron or something like 00:32:28.320 --> 00:32:28.549 align:start position:0% something like iron or something like that 00:32:28.549 --> 00:32:28.559 align:start position:0% that 00:32:28.559 --> 00:32:30.649 align:start position:0% that or<00:32:29.010> recovering<00:32:29.820> in<00:32:30.059> that<00:32:30.240> in<00:32:30.480> that<00:32:30.510> case 00:32:30.649 --> 00:32:30.659 align:start position:0% or recovering in that in that case 00:32:30.659 --> 00:32:34.010 align:start position:0% or recovering in that in that case something<00:32:31.350> that<00:32:31.500> important<00:32:32.070> that<00:32:32.280> has<00:32:33.020> human 00:32:34.010 --> 00:32:34.020 align:start position:0% something that important that has human 00:32:34.020 --> 00:32:37.250 align:start position:0% something that important that has human intervention<00:32:34.679> but<00:32:35.159> I<00:32:35.370> wouldn't<00:32:35.850> be<00:32:36.480> 99 00:32:37.250 --> 00:32:37.260 align:start position:0% intervention but I wouldn't be 99 00:32:37.260 --> 00:32:39.919 align:start position:0% intervention but I wouldn't be 99 percent<00:32:37.289> of<00:32:37.740> time<00:32:38.070> running<00:32:38.929> automatically 00:32:39.919 --> 00:32:39.929 align:start position:0% percent of time running automatically 00:32:39.929 --> 00:32:42.470 align:start position:0% percent of time running automatically without<00:32:40.559> human<00:32:41.039> intervention<00:32:41.480> because 00:32:42.470 --> 00:32:42.480 align:start position:0% without human intervention because 00:32:42.480 --> 00:32:47.480 align:start position:0% without human intervention because that's<00:32:42.690> a<00:32:42.840> that's<00:32:43.020> point<00:32:43.350> so<00:32:45.140> these<00:32:46.490> in 00:32:47.480 --> 00:32:47.490 align:start position:0% that's a that's point so these in 00:32:47.490 --> 00:32:49.820 align:start position:0% that's a that's point so these in addition<00:32:47.760> to<00:32:48.090> producing<00:32:48.299> the<00:32:48.740> contract<00:32:49.740> that 00:32:49.820 --> 00:32:49.830 align:start position:0% addition to producing the contract that 00:32:49.830 --> 00:32:52.610 align:start position:0% addition to producing the contract that contains<00:32:50.010> device<00:32:50.789> like<00:32:51.059> these<00:32:51.620> something 00:32:52.610 --> 00:32:52.620 align:start position:0% contains device like these something 00:32:52.620 --> 00:32:56.480 align:start position:0% contains device like these something else<00:32:52.830> which<00:32:53.400> is<00:32:53.480> what<00:32:54.480> my<00:32:54.750> phone<00:32:55.309> which<00:32:56.309> is 00:32:56.480 --> 00:32:56.490 align:start position:0% else which is what my phone which is 00:32:56.490 --> 00:33:02.510 align:start position:0% else which is what my phone which is producing<00:33:00.080> default<00:33:01.080> constructor<00:33:02.070> arguments 00:33:02.510 --> 00:33:02.520 align:start position:0% producing default constructor arguments 00:33:02.520 --> 00:33:05.510 align:start position:0% producing default constructor arguments and<00:33:02.850> migrations<00:33:03.450> so<00:33:03.960> it<00:33:04.230> is<00:33:04.350> detected<00:33:04.710> that<00:33:05.190> at 00:33:05.510 --> 00:33:05.520 align:start position:0% and migrations so it is detected that at 00:33:05.520 --> 00:33:09.140 align:start position:0% and migrations so it is detected that at inside<00:33:06.270> my<00:33:06.390> project<00:33:06.600> I<00:33:07.110> have<00:33:07.799> using<00:33:08.760> women 00:33:09.140 --> 00:33:09.150 align:start position:0% inside my project I have using women 00:33:09.150 --> 00:33:12.950 align:start position:0% inside my project I have using women contract<00:33:09.900> so<00:33:10.320> in<00:33:10.620> created<00:33:11.159> here<00:33:11.960> in 00:33:12.950 --> 00:33:12.960 align:start position:0% contract so in created here in 00:33:12.960 --> 00:33:15.440 align:start position:0% contract so in created here in migrations<00:33:13.710> folder<00:33:14.100> that<00:33:14.460> you<00:33:14.850> will<00:33:15.360> be 00:33:15.440 --> 00:33:15.450 align:start position:0% migrations folder that you will be 00:33:15.450 --> 00:33:15.880 align:start position:0% migrations folder that you will be familiar 00:33:15.880 --> 00:33:15.890 align:start position:0% familiar 00:33:15.890 --> 00:33:24.130 align:start position:0% familiar a<00:33:20.080> truffle<00:33:21.080> to<00:33:22.070> to<00:33:22.400> migrations<00:33:23.090> one<00:33:23.480> is<00:33:23.690> me 00:33:24.130 --> 00:33:24.140 align:start position:0% a truffle to to migrations one is me 00:33:24.140 --> 00:33:29.530 align:start position:0% a truffle to to migrations one is me poor<00:33:24.410> that<00:33:25.900> imports<00:33:26.900> all<00:33:27.080> the<00:33:28.150> women<00:33:29.150> to<00:33:29.180> keep 00:33:29.530 --> 00:33:29.540 align:start position:0% poor that imports all the women to keep 00:33:29.540 --> 00:33:34.030 align:start position:0% poor that imports all the women to keep blessing<00:33:29.810> and<00:33:30.850> this<00:33:31.870> will<00:33:32.870> pass<00:33:33.080> but<00:33:33.830> it's 00:33:34.030 --> 00:33:34.040 align:start position:0% blessing and this will pass but it's 00:33:34.040 --> 00:33:37.150 align:start position:0% blessing and this will pass but it's doing<00:33:34.460> is<00:33:34.760> detecting<00:33:35.690> if<00:33:36.050> we<00:33:36.260> are<00:33:36.440> on<00:33:36.890> that 00:33:37.150 --> 00:33:37.160 align:start position:0% doing is detecting if we are on that 00:33:37.160 --> 00:33:39.550 align:start position:0% doing is detecting if we are on that public<00:33:37.550> into<00:33:38.060> your<00:33:38.210> network<00:33:38.600> and<00:33:38.930> then<00:33:39.170> we<00:33:39.470> are 00:33:39.550 --> 00:33:39.560 align:start position:0% public into your network and then we are 00:33:39.560 --> 00:33:41.650 align:start position:0% public into your network and then we are in<00:33:39.680> a<00:33:39.740> public<00:33:39.890> into<00:33:40.280> your<00:33:40.430> network<00:33:40.610> will<00:33:41.390> link 00:33:41.650 --> 00:33:41.660 align:start position:0% in a public into your network will link 00:33:41.660 --> 00:33:44.410 align:start position:0% in a public into your network will link all<00:33:41.810> the<00:33:42.260> things<00:33:42.920> related<00:33:43.370> to<00:33:43.400> this<00:33:43.670> when<00:33:44.270> its 00:33:44.410 --> 00:33:44.420 align:start position:0% all the things related to this when its 00:33:44.420 --> 00:33:47.830 align:start position:0% all the things related to this when its reach<00:33:44.570> interface<00:33:45.110> and<00:33:46.000> relay<00:33:47.000> and<00:33:47.210> so<00:33:47.360> on<00:33:47.510> and 00:33:47.830 --> 00:33:47.840 align:start position:0% reach interface and relay and so on and 00:33:47.840 --> 00:33:50.050 align:start position:0% reach interface and relay and so on and if<00:33:48.350> we<00:33:48.560> ran<00:33:48.740> a<00:33:48.830> private<00:33:49.010> network<00:33:49.280> it<00:33:49.850> will 00:33:50.050 --> 00:33:50.060 align:start position:0% if we ran a private network it will 00:33:50.060 --> 00:33:53.080 align:start position:0% if we ran a private network it will deploy<00:33:50.300> an<00:33:50.660> instance<00:33:51.140> of<00:33:51.380> the<00:33:52.250> WPI<00:33:52.730> and 00:33:53.080 --> 00:33:53.090 align:start position:0% deploy an instance of the WPI and 00:33:53.090 --> 00:33:55.510 align:start position:0% deploy an instance of the WPI and everything<00:33:53.600> and<00:33:53.840> they<00:33:54.560> get<00:33:54.770> that<00:33:54.950> into<00:33:55.400> your 00:33:55.510 --> 00:33:55.520 align:start position:0% everything and they get that into your 00:33:55.520 --> 00:33:59.110 align:start position:0% everything and they get that into your your<00:33:56.330> contracts<00:33:56.810> and<00:33:57.170> the<00:33:57.980> most<00:33:58.670> beautiful 00:33:59.110 --> 00:33:59.120 align:start position:0% your contracts and the most beautiful 00:33:59.120 --> 00:34:01.720 align:start position:0% your contracts and the most beautiful part<00:33:59.360> is<00:33:59.630> that<00:33:59.960> it<00:34:00.200> brought<00:34:00.470> also<00:34:00.890> the<00:34:01.040> day 00:34:01.720 --> 00:34:01.730 align:start position:0% part is that it brought also the day 00:34:01.730 --> 00:34:04.690 align:start position:0% part is that it brought also the day migrations<00:34:02.360> for<00:34:02.720> my<00:34:03.110> contract<00:34:03.680> and<00:34:03.800> inserted 00:34:04.690 --> 00:34:04.700 align:start position:0% migrations for my contract and inserted 00:34:04.700 --> 00:34:09.159 align:start position:0% migrations for my contract and inserted the<00:34:05.890> default<00:34:06.890> arguments<00:34:07.610> so<00:34:07.760> it<00:34:07.910> detects<00:34:08.870> it 00:34:09.159 --> 00:34:09.169 align:start position:0% the default arguments so it detects it 00:34:09.169 --> 00:34:11.770 align:start position:0% the default arguments so it detects it can<00:34:09.679> read<00:34:10.010> the<00:34:10.520> signature<00:34:11.000> of<00:34:11.450> the 00:34:11.770 --> 00:34:11.780 align:start position:0% can read the signature of the 00:34:11.780 --> 00:34:14.080 align:start position:0% can read the signature of the constructor<00:34:12.470> of<00:34:12.590> your<00:34:12.770> contracts<00:34:13.340> and<00:34:13.460> put 00:34:14.080 --> 00:34:14.090 align:start position:0% constructor of your contracts and put 00:34:14.090 --> 00:34:16.990 align:start position:0% constructor of your contracts and put the<00:34:14.270> all<00:34:14.510> values<00:34:14.929> so<00:34:15.140> that<00:34:15.290> you<00:34:15.500> you<00:34:16.490> only<00:34:16.730> need 00:34:16.990 --> 00:34:17.000 align:start position:0% the all values so that you you only need 00:34:17.000 --> 00:34:21.490 align:start position:0% the all values so that you you only need to<00:34:17.770> manually<00:34:18.770> said<00:34:19.360> anything<00:34:20.360> that<00:34:20.540> has<00:34:21.230> not 00:34:21.490 --> 00:34:21.500 align:start position:0% to manually said anything that has not 00:34:21.500 --> 00:34:23.350 align:start position:0% to manually said anything that has not that<00:34:21.679> before<00:34:21.980> party<00:34:22.310> let's<00:34:22.550> say<00:34:22.700> but<00:34:23.120> for 00:34:23.350 --> 00:34:23.360 align:start position:0% that before party let's say but for 00:34:23.360 --> 00:34:25.570 align:start position:0% that before party let's say but for example<00:34:23.750> it<00:34:23.870> detected<00:34:24.380> that<00:34:24.890> the<00:34:25.040> contract<00:34:25.429> is 00:34:25.570 --> 00:34:25.580 align:start position:0% example it detected that the contract is 00:34:25.580 --> 00:34:27.790 align:start position:0% example it detected that the contract is expecting<00:34:26.330> the<00:34:26.659> address<00:34:27.080> of<00:34:27.290> the<00:34:27.500> wooden 00:34:27.790 --> 00:34:27.800 align:start position:0% expecting the address of the wooden 00:34:27.800 --> 00:34:31.000 align:start position:0% expecting the address of the wooden bridge<00:34:27.980> interface<00:34:28.250> so<00:34:28.730> it<00:34:29.210> has<00:34:29.450> the<00:34:30.010> the 00:34:31.000 --> 00:34:31.010 align:start position:0% bridge interface so it has the the 00:34:31.010 --> 00:34:34.690 align:start position:0% bridge interface so it has the the address<00:34:31.130> right<00:34:31.909> there<00:34:31.970> it<00:34:32.540> just<00:34:33.070> okay<00:34:34.070> what<00:34:34.340> we 00:34:34.690 --> 00:34:34.700 align:start position:0% address right there it just okay what we 00:34:34.700 --> 00:34:37.419 align:start position:0% address right there it just okay what we the<00:34:35.120> women<00:34:35.360> which<00:34:35.659> interface<00:34:36.110> that<00:34:36.350> is<00:34:36.530> like 00:34:37.419 --> 00:34:37.429 align:start position:0% the women which interface that is like 00:34:37.429 --> 00:34:40.630 align:start position:0% the women which interface that is like right<00:34:37.760> now<00:34:37.909> and<00:34:38.480> it's<00:34:38.840> just<00:34:38.929> some<00:34:39.640> reference 00:34:40.630 --> 00:34:40.640 align:start position:0% right now and it's just some reference 00:34:40.640 --> 00:34:42.130 align:start position:0% right now and it's just some reference implementation<00:34:41.270> that<00:34:41.419> we<00:34:41.630> make<00:34:41.870> that<00:34:42.080> we 00:34:42.130 --> 00:34:42.140 align:start position:0% implementation that we make that we 00:34:42.140 --> 00:34:45.570 align:start position:0% implementation that we make that we expect<00:34:42.880> other<00:34:43.880> developers<00:34:44.540> to<00:34:44.690> create<00:34:44.840> other 00:34:45.570 --> 00:34:45.580 align:start position:0% expect other developers to create other 00:34:45.580 --> 00:34:48.250 align:start position:0% expect other developers to create other implementations<00:34:46.580> that<00:34:46.760> may<00:34:47.690> work<00:34:47.929> in<00:34:48.140> a 00:34:48.250 --> 00:34:48.260 align:start position:0% implementations that may work in a 00:34:48.260 --> 00:34:50.620 align:start position:0% implementations that may work in a different<00:34:48.679> way<00:34:48.860> but<00:34:49.159> there<00:34:49.490> is<00:34:50.000> an<00:34:50.179> interface 00:34:50.620 --> 00:34:50.630 align:start position:0% different way but there is an interface 00:34:50.630 --> 00:34:52.280 align:start position:0% different way but there is an interface with<00:34:50.960> asunder 00:34:52.280 --> 00:34:52.290 align:start position:0% with asunder 00:34:52.290 --> 00:34:56.599 align:start position:0% with asunder as<00:34:52.409> long<00:34:52.679> as<00:34:52.829> you<00:34:54.260> abide<00:34:55.260> by<00:34:55.800> the<00:34:55.859> internal 00:34:56.599 --> 00:34:56.609 align:start position:0% as long as you abide by the internal 00:34:56.609 --> 00:34:59.150 align:start position:0% as long as you abide by the internal interface<00:34:57.119> internally<00:34:57.780> I<00:34:57.810> work<00:34:58.680> differently 00:34:59.150 --> 00:34:59.160 align:start position:0% interface internally I work differently 00:34:59.160 --> 00:35:01.790 align:start position:0% interface internally I work differently so<00:34:59.490> the<00:34:59.670> developers<00:35:00.119> have<00:35:00.569> the<00:35:00.869> freedom<00:35:01.560> to 00:35:01.790 --> 00:35:01.800 align:start position:0% so the developers have the freedom to 00:35:01.800 --> 00:35:05.089 align:start position:0% so the developers have the freedom to use<00:35:02.250> and<00:35:02.700> other<00:35:03.089> women<00:35:03.869> women<00:35:04.650> reaching<00:35:04.980> the 00:35:05.089 --> 00:35:05.099 align:start position:0% use and other women women reaching the 00:35:05.099 --> 00:35:09.109 align:start position:0% use and other women women reaching the faces<00:35:05.520> that<00:35:05.609> is<00:35:05.880> not<00:35:06.119> there<00:35:07.310> the<00:35:08.310> one<00:35:08.520> provided 00:35:09.109 --> 00:35:09.119 align:start position:0% faces that is not there the one provided 00:35:09.119 --> 00:35:22.710 align:start position:0% faces that is not there the one provided by<00:35:09.150> by<00:35:09.780> us<00:35:13.069> so<00:35:14.810> one<00:35:15.810> man<00:35:16.050> to<00:35:17.030> life 00:35:22.710 --> 00:35:22.720 align:start position:0% 00:35:22.720 --> 00:35:32.640 align:start position:0% I<00:35:22.750> just<00:35:23.440> moved<00:35:23.650> here<00:35:24.099> as<00:35:24.940> in<00:35:25.180> case<00:35:27.000> work<00:35:30.150> so<00:35:31.650> on 00:35:32.640 --> 00:35:32.650 align:start position:0% I just moved here as in case work so on 00:35:32.650 --> 00:35:37.620 align:start position:0% I just moved here as in case work so on the<00:35:32.829> future<00:35:33.130> frame<00:35:35.280> one<00:35:36.280> what<00:35:36.819> the<00:35:37.180> first<00:35:37.420> the 00:35:37.620 --> 00:35:37.630 align:start position:0% the future frame one what the first the 00:35:37.630 --> 00:35:41.700 align:start position:0% the future frame one what the first the first<00:35:37.780> thing<00:35:38.819> we<00:35:39.819> think<00:35:39.849> about<00:35:40.300> is<00:35:40.780> going<00:35:41.380> be 00:35:41.700 --> 00:35:41.710 align:start position:0% first thing we think about is going be 00:35:41.710 --> 00:35:46.069 align:start position:0% first thing we think about is going be honest<00:35:42.010> in<00:35:42.250> the<00:35:42.369> best<00:35:42.869> Expedia's<00:35:43.869> basic<00:35:44.800> Irina 00:35:46.069 --> 00:35:46.079 align:start position:0% honest in the best Expedia's basic Irina 00:35:46.079 --> 00:35:50.040 align:start position:0% honest in the best Expedia's basic Irina Raiden<00:35:47.109> spot<00:35:47.980> used<00:35:48.310> on<00:35:48.609> precision<00:35:49.150> payloads 00:35:50.040 --> 00:35:50.050 align:start position:0% Raiden spot used on precision payloads 00:35:50.050 --> 00:35:54.599 align:start position:0% Raiden spot used on precision payloads coming<00:35:50.589> from<00:35:51.329> gift<00:35:52.329> requests<00:35:53.170> don't<00:35:54.160> using 00:35:54.599 --> 00:35:54.609 align:start position:0% coming from gift requests don't using 00:35:54.609 --> 00:35:57.710 align:start position:0% coming from gift requests don't using HTTP<00:35:55.329> but<00:35:56.140> we<00:35:56.680> can<00:35:56.920> think<00:35:57.160> of<00:35:57.369> other 00:35:57.710 --> 00:35:57.720 align:start position:0% HTTP but we can think of other 00:35:57.720 --> 00:36:05.069 align:start position:0% HTTP but we can think of other initiators<00:35:58.770> like<00:36:00.300> taking<00:36:02.910> data<00:36:03.910> from<00:36:04.119> IP<00:36:04.630> is 00:36:05.069 --> 00:36:05.079 align:start position:0% initiators like taking data from IP is 00:36:05.079 --> 00:36:09.770 align:start position:0% initiators like taking data from IP is scored<00:36:05.710> by<00:36:06.339> going<00:36:07.270> and<00:36:07.869> so<00:36:08.109> on<00:36:08.319> or<00:36:08.740> even 00:36:09.770 --> 00:36:09.780 align:start position:0% scored by going and so on or even 00:36:09.780 --> 00:36:11.760 align:start position:0% scored by going and so on or even reacting<00:36:10.780> to<00:36:10.960> weather<00:36:11.200> events 00:36:11.760 --> 00:36:11.770 align:start position:0% reacting to weather events 00:36:11.770 --> 00:36:13.920 align:start position:0% reacting to weather events so<00:36:11.980> basically<00:36:12.339> giving<00:36:13.089> your<00:36:13.270> contracts<00:36:13.750> a 00:36:13.920 --> 00:36:13.930 align:start position:0% so basically giving your contracts a 00:36:13.930 --> 00:36:18.480 align:start position:0% so basically giving your contracts a capability<00:36:14.410> of<00:36:15.240> sharing<00:36:16.240> events<00:36:17.220> thrown<00:36:18.220> by 00:36:18.480 --> 00:36:18.490 align:start position:0% capability of sharing events thrown by 00:36:18.490 --> 00:36:23.490 align:start position:0% capability of sharing events thrown by mother<00:36:20.099> during<00:36:21.099> contracts<00:36:21.700> or<00:36:22.319> if<00:36:23.319> you 00:36:23.490 --> 00:36:23.500 align:start position:0% mother during contracts or if you 00:36:23.500 --> 00:36:25.650 align:start position:0% mother during contracts or if you contract<00:36:24.040> selecting<00:36:25.030> contracts<00:36:25.390> that 00:36:25.650 --> 00:36:25.660 align:start position:0% contract selecting contracts that 00:36:25.660 --> 00:36:30.000 align:start position:0% contract selecting contracts that believe<00:36:26.440> on<00:36:26.790> another<00:36:28.170> network<00:36:29.170> which<00:36:29.740> is 00:36:30.000 --> 00:36:30.010 align:start position:0% believe on another network which is 00:36:30.010 --> 00:36:32.849 align:start position:0% believe on another network which is something<00:36:30.250> quite<00:36:30.609> interesting<00:36:31.260> or<00:36:32.260> events 00:36:32.849 --> 00:36:32.859 align:start position:0% something quite interesting or events 00:36:32.859 --> 00:36:36.380 align:start position:0% something quite interesting or events are<00:36:33.010> occurring<00:36:33.750> authenticated<00:36:34.750> experience 00:36:36.380 --> 00:36:36.390 align:start position:0% are occurring authenticated experience 00:36:36.390 --> 00:36:39.620 align:start position:0% are occurring authenticated experience one<00:36:37.390> other<00:36:37.690> thing<00:36:38.020> we're<00:36:38.230> working<00:36:38.440> on<00:36:38.740> is 00:36:39.620 --> 00:36:39.630 align:start position:0% one other thing we're working on is 00:36:39.630 --> 00:36:42.990 align:start position:0% one other thing we're working on is allowing<00:36:40.630> some<00:36:40.990> implicit<00:36:41.760> conversions<00:36:42.760> so 00:36:42.990 --> 00:36:43.000 align:start position:0% allowing some implicit conversions so 00:36:43.000 --> 00:36:46.140 align:start position:0% allowing some implicit conversions so basically<00:36:43.359> getting<00:36:44.109> rid<00:36:44.170> of<00:36:44.619> the<00:36:44.859> as<00:36:45.130> map<00:36:45.400> as<00:36:46.089> a 00:36:46.140 --> 00:36:46.150 align:start position:0% basically getting rid of the as map as a 00:36:46.150 --> 00:36:48.990 align:start position:0% basically getting rid of the as map as a whole<00:36:46.480> thing<00:36:47.020> and<00:36:47.200> so<00:36:47.410> on<00:36:47.650> we<00:36:48.550> can<00:36:48.730> do<00:36:48.849> that 00:36:48.990 --> 00:36:49.000 align:start position:0% whole thing and so on we can do that 00:36:49.000 --> 00:36:51.270 align:start position:0% whole thing and so on we can do that because<00:36:49.359> the<00:36:49.869> operators<00:36:50.500> are<00:36:50.770> actually 00:36:51.270 --> 00:36:51.280 align:start position:0% because the operators are actually 00:36:51.280 --> 00:36:55.260 align:start position:0% because the operators are actually defined<00:36:51.940> as<00:36:52.210> stream<00:36:52.960> part<00:36:53.260> station<00:36:53.980> by<00:36:54.790> SAS 00:36:55.260 --> 00:36:55.270 align:start position:0% defined as stream part station by SAS 00:36:55.270 --> 00:36:58.849 align:start position:0% defined as stream part station by SAS map<00:36:55.750> and<00:36:56.079> so<00:36:56.290> on<00:36:56.470> so<00:36:57.010> they<00:36:57.339> are<00:36:57.520> already 00:36:58.849 --> 00:36:58.859 align:start position:0% map and so on so they are already 00:36:58.859 --> 00:37:02.579 align:start position:0% map and so on so they are already explicit<00:36:59.859> of<00:37:00.210> from<00:37:01.210> which<00:37:01.510> type<00:37:01.839> to<00:37:02.349> which 00:37:02.579 --> 00:37:02.589 align:start position:0% explicit of from which type to which 00:37:02.589 --> 00:37:05.760 align:start position:0% explicit of from which type to which type<00:37:02.920> so<00:37:03.190> we<00:37:03.369> can<00:37:03.750> remove<00:37:04.750> that<00:37:04.810> because<00:37:05.319> and 00:37:05.760 --> 00:37:05.770 align:start position:0% type so we can remove that because and 00:37:05.770 --> 00:37:11.089 align:start position:0% type so we can remove that because and it<00:37:06.099> becomes<00:37:06.780> obvious<00:37:07.780> at<00:37:08.380> some<00:37:08.530> point<00:37:09.270> and 00:37:11.089 --> 00:37:11.099 align:start position:0% it becomes obvious at some point and 00:37:11.099 --> 00:37:14.339 align:start position:0% it becomes obvious at some point and this<00:37:12.099> this<00:37:12.400> is<00:37:12.579> one<00:37:12.970> thing<00:37:13.210> that<00:37:13.240> we<00:37:13.750> are<00:37:13.839> also 00:37:14.339 --> 00:37:14.349 align:start position:0% this this is one thing that we are also 00:37:14.349 --> 00:37:17.280 align:start position:0% this this is one thing that we are also quite<00:37:15.099> excited<00:37:15.700> about<00:37:15.910> is<00:37:16.180> done<00:37:16.390> because<00:37:17.230> of 00:37:17.280 --> 00:37:17.290 align:start position:0% quite excited about is done because of 00:37:17.290 --> 00:37:21.630 align:start position:0% quite excited about is done because of house<00:37:17.800> key<00:37:18.190> forwards<00:37:18.819> so<00:37:19.420> super<00:37:20.130> as<00:37:21.130> I'm 00:37:21.630 --> 00:37:21.640 align:start position:0% house key forwards so super as I'm 00:37:21.640 --> 00:37:23.990 align:start position:0% house key forwards so super as I'm looking<00:37:22.240> for<00:37:22.690> data<00:37:22.900> structures 00:37:23.990 --> 00:37:24.000 align:start position:0% looking for data structures 00:37:24.000 --> 00:37:28.670 align:start position:0% looking for data structures both<00:37:25.340> both<00:37:26.340> the<00:37:26.760> body<00:37:27.000> and<00:37:27.480> how<00:37:27.840> device<00:37:28.200> relate 00:37:28.670 --> 00:37:28.680 align:start position:0% both both the body and how device relate 00:37:28.680 --> 00:37:31.130 align:start position:0% both both the body and how device relate to<00:37:28.830> each<00:37:28.950> other<00:37:29.160> so<00:37:29.640> how<00:37:29.820> what's<00:37:30.720> they<00:37:30.900> hurt 00:37:31.130 --> 00:37:31.140 align:start position:0% to each other so how what's they hurt 00:37:31.140 --> 00:37:34.850 align:start position:0% to each other so how what's they hurt and<00:37:32.660> because<00:37:33.660> of<00:37:33.690> that<00:37:33.810> normally<00:37:34.650> there's 00:37:34.850 --> 00:37:34.860 align:start position:0% and because of that normally there's 00:37:34.860 --> 00:37:37.130 align:start position:0% and because of that normally there's some<00:37:35.070> kind<00:37:35.280> of<00:37:35.400> expansion<00:37:36.030> for<00:37:36.210> example<00:37:36.930> for 00:37:37.130 --> 00:37:37.140 align:start position:0% some kind of expansion for example for 00:37:37.140 --> 00:37:40.730 align:start position:0% some kind of expansion for example for representing<00:37:37.830> a<00:37:38.330> 45x<00:37:39.330> traditional<00:37:39.930> here<00:37:40.350> it's 00:37:40.730 --> 00:37:40.740 align:start position:0% representing a 45x traditional here it's 00:37:40.740 --> 00:37:45.800 align:start position:0% representing a 45x traditional here it's using<00:37:41.010> goodbyes<00:37:41.780> 1845<00:37:42.780> so<00:37:44.600> there's<00:37:45.600> no 00:37:45.800 --> 00:37:45.810 align:start position:0% using goodbyes 1845 so there's no 00:37:45.810 --> 00:37:48.860 align:start position:0% using goodbyes 1845 so there's no optimization<00:37:46.470> here<00:37:47.100> it's<00:37:47.580> for<00:37:48.390> a<00:37:48.630> small 00:37:48.860 --> 00:37:48.870 align:start position:0% optimization here it's for a small 00:37:48.870 --> 00:37:50.900 align:start position:0% optimization here it's for a small integer<00:37:49.200> so<00:37:49.440> small<00:37:49.680> new<00:37:49.770> takers<00:37:50.130> only<00:37:50.700> take 00:37:50.900 --> 00:37:50.910 align:start position:0% integer so small new takers only take 00:37:50.910 --> 00:37:53.930 align:start position:0% integer so small new takers only take one<00:37:51.300> bite<00:37:51.540> because<00:37:51.780> they<00:37:52.470> are<00:37:52.890> the<00:37:53.550> bodies 00:37:53.930 --> 00:37:53.940 align:start position:0% one bite because they are the bodies 00:37:53.940 --> 00:37:59.140 align:start position:0% one bite because they are the bodies below<00:37:54.600> 25<00:37:55.110> or<00:37:55.350> about<00:37:55.830> -<00:37:56.310> 25<00:37:57.830> impacting 00:37:59.140 --> 00:37:59.150 align:start position:0% below 25 or about - 25 impacting 00:37:59.150 --> 00:38:04.670 align:start position:0% below 25 or about - 25 impacting automatically<00:38:01.130> guesses<00:38:02.810> knows<00:38:03.810> that<00:38:04.170> it's<00:38:04.410> an 00:38:04.670 --> 00:38:04.680 align:start position:0% automatically guesses knows that it's an 00:38:04.680 --> 00:38:10.970 align:start position:0% automatically guesses knows that it's an integer<00:38:05.660> so<00:38:06.660> we<00:38:06.950> can<00:38:08.630> turn<00:38:09.630> this<00:38:09.870> screen<00:38:10.320> into 00:38:10.970 --> 00:38:10.980 align:start position:0% integer so we can turn this screen into 00:38:10.980 --> 00:38:13.840 align:start position:0% integer so we can turn this screen into this<00:38:11.160> other<00:38:11.460> in<00:38:11.940> which<00:38:12.210> we<00:38:12.480> are<00:38:12.660> in<00:38:12.900> basically 00:38:13.840 --> 00:38:13.850 align:start position:0% this other in which we are in basically 00:38:13.850 --> 00:38:18.770 align:start position:0% this other in which we are in basically model<00:38:15.410> 16<00:38:16.410> for<00:38:16.980> all<00:38:17.130> the<00:38:17.280> operators<00:38:17.790> and<00:38:18.180> as<00:38:18.570> we 00:38:18.770 --> 00:38:18.780 align:start position:0% model 16 for all the operators and as we 00:38:18.780 --> 00:38:21.770 align:start position:0% model 16 for all the operators and as we know<00:38:19.680> the<00:38:19.980> change<00:38:20.310> of<00:38:20.640> the<00:38:20.820> types<00:38:21.090> we<00:38:21.420> know 00:38:21.770 --> 00:38:21.780 align:start position:0% know the change of the types we know 00:38:21.780 --> 00:38:26.960 align:start position:0% know the change of the types we know actually<00:38:22.080> that<00:38:24.740> five<00:38:25.740> year<00:38:26.160> actually<00:38:26.430> means 00:38:26.960 --> 00:38:26.970 align:start position:0% actually that five year actually means 00:38:26.970 --> 00:38:32.060 align:start position:0% actually that five year actually means 45<00:38:27.680> one<00:38:28.680> is<00:38:29.180> 61<00:38:30.180> and<00:38:30.480> so<00:38:30.690> on<00:38:30.870> and<00:38:31.080> we<00:38:31.860> can 00:38:32.060 --> 00:38:32.070 align:start position:0% 45 one is 61 and so on and we can 00:38:32.070 --> 00:38:36.440 align:start position:0% 45 one is 61 and so on and we can leverage<00:38:32.520> that<00:38:33.710> the<00:38:34.710> way<00:38:34.890> that<00:38:35.130> works<00:38:35.790> and<00:38:36.270> we 00:38:36.440 --> 00:38:36.450 align:start position:0% leverage that the way that works and we 00:38:36.450 --> 00:38:39.170 align:start position:0% leverage that the way that works and we tend<00:38:36.660> those<00:38:36.930> operators<00:38:37.860> from<00:38:38.250> 2<00:38:38.520> bytes<00:38:38.760> into<00:38:39.060> a 00:38:39.170 --> 00:38:39.180 align:start position:0% tend those operators from 2 bytes into a 00:38:39.180 --> 00:38:42.380 align:start position:0% tend those operators from 2 bytes into a single<00:38:39.600> path<00:38:39.810> and<00:38:40.230> in<00:38:41.160> this<00:38:41.250> case<00:38:41.550> the 00:38:42.380 --> 00:38:42.390 align:start position:0% single path and in this case the 00:38:42.390 --> 00:38:45.680 align:start position:0% single path and in this case the reduction<00:38:42.990> is<00:38:43.170> around<00:38:43.740> 30%<00:38:44.280> because<00:38:44.880> we<00:38:45.480> have 00:38:45.680 --> 00:38:45.690 align:start position:0% reduction is around 30% because we have 00:38:45.690 --> 00:38:47.840 align:start position:0% reduction is around 30% because we have literal<00:38:46.170> span<00:38:46.560> in<00:38:46.800> the<00:38:46.890> Suites<00:38:47.220> where<00:38:47.490> we<00:38:47.670> have 00:38:47.840 --> 00:38:47.850 align:start position:0% literal span in the Suites where we have 00:38:47.850 --> 00:38:50.750 align:start position:0% literal span in the Suites where we have very<00:38:48.780> low<00:38:49.140> amount<00:38:49.470> of<00:38:49.620> leaders<00:38:49.950> and<00:38:50.250> we<00:38:50.640> are 00:38:50.750 --> 00:38:50.760 align:start position:0% very low amount of leaders and we are 00:38:50.760 --> 00:38:55.670 align:start position:0% very low amount of leaders and we are just<00:38:51.050> dealing<00:38:52.050> with<00:38:53.690> changing<00:38:54.690> the<00:38:54.720> shape<00:38:55.650> of 00:38:55.670 --> 00:38:55.680 align:start position:0% just dealing with changing the shape of 00:38:55.680 --> 00:39:00.950 align:start position:0% just dealing with changing the shape of the<00:38:56.490> data<00:38:56.670> and<00:38:57.480> not<00:38:59.030> using<00:39:00.030> gets<00:39:00.300> turn<00:39:00.660> deep 00:39:00.950 --> 00:39:00.960 align:start position:0% the data and not using gets turn deep 00:39:00.960 --> 00:39:04.670 align:start position:0% the data and not using gets turn deep like<00:39:01.500> this<00:39:01.680> and<00:39:02.100> so<00:39:02.280> on<00:39:02.430> we<00:39:02.910> can<00:39:02.940> get<00:39:03.300> after<00:39:03.680> 50% 00:39:04.670 --> 00:39:04.680 align:start position:0% like this and so on we can get after 50% 00:39:04.680 --> 00:39:07.610 align:start position:0% like this and so on we can get after 50% say<00:39:05.550> which<00:39:05.850> is<00:39:06.000> a<00:39:06.300> very<00:39:06.690> important<00:39:07.110> for<00:39:07.350> alert 00:39:07.610 --> 00:39:07.620 align:start position:0% say which is a very important for alert 00:39:07.620 --> 00:39:09.040 align:start position:0% say which is a very important for alert for<00:39:08.040> long<00:39:08.310> term 00:39:09.040 --> 00:39:09.050 align:start position:0% for long term 00:39:09.050 --> 00:39:15.340 align:start position:0% for long term ability<00:39:09.650> of<00:39:10.460> men<00:39:11.290> also<00:39:13.870> you<00:39:14.870> can<00:39:15.080> feel<00:39:15.320> that 00:39:15.340 --> 00:39:15.350 align:start position:0% ability of men also you can feel that 00:39:15.350 --> 00:39:18.070 align:start position:0% ability of men also you can feel that with<00:39:16.220> being<00:39:16.490> a<00:39:16.580> Frieden<00:39:17.030> as<00:39:17.330> something<00:39:18.050> that 00:39:18.070 --> 00:39:18.080 align:start position:0% with being a Frieden as something that 00:39:18.080 --> 00:39:21.340 align:start position:0% with being a Frieden as something that goes<00:39:18.380> beyond<00:39:19.160> witness<00:39:19.670> beyond<00:39:20.330> or<00:39:20.660> networks 00:39:21.340 --> 00:39:21.350 align:start position:0% goes beyond witness beyond or networks 00:39:21.350 --> 00:39:24.280 align:start position:0% goes beyond witness beyond or networks actually<00:39:21.590> because<00:39:22.520> on<00:39:22.820> Ibiza<00:39:23.270> at<00:39:23.930> the<00:39:24.080> end<00:39:24.200> of 00:39:24.280 --> 00:39:24.290 align:start position:0% actually because on Ibiza at the end of 00:39:24.290 --> 00:39:26.320 align:start position:0% actually because on Ibiza at the end of the<00:39:24.380> day<00:39:24.500> it's<00:39:24.650> a<00:39:24.710> versatile<00:39:25.130> a<00:39:25.460> sale<00:39:25.760> for 00:39:26.320 --> 00:39:26.330 align:start position:0% the day it's a versatile a sale for 00:39:26.330 --> 00:39:30.100 align:start position:0% the day it's a versatile a sale for performing<00:39:26.900> data<00:39:27.790> flows<00:39:28.790> for<00:39:29.150> the<00:39:29.360> final<00:39:29.930> data 00:39:30.100 --> 00:39:30.110 align:start position:0% performing data flows for the final data 00:39:30.110 --> 00:39:32.560 align:start position:0% performing data flows for the final data flows<00:39:30.410> and<00:39:30.800> performing<00:39:31.310> operations<00:39:31.580> on<00:39:32.120> the 00:39:32.560 --> 00:39:32.570 align:start position:0% flows and performing operations on the 00:39:32.570 --> 00:39:34.600 align:start position:0% flows and performing operations on the way<00:39:32.690> so<00:39:33.140> it<00:39:33.260> could<00:39:33.440> be<00:39:33.470> used<00:39:33.710> not<00:39:34.190> only<00:39:34.250> for 00:39:34.600 --> 00:39:34.610 align:start position:0% way so it could be used not only for 00:39:34.610 --> 00:39:37.960 align:start position:0% way so it could be used not only for women<00:39:35.510> but<00:39:35.810> for<00:39:35.870> other<00:39:36.290> particles<00:39:36.860> or<00:39:37.400> writing 00:39:37.960 --> 00:39:37.970 align:start position:0% women but for other particles or writing 00:39:37.970 --> 00:39:40.840 align:start position:0% women but for other particles or writing scrappers<00:39:38.750> for<00:39:39.320> the<00:39:39.650> indica<00:39:40.130> from<00:39:40.400> from 00:39:40.840 --> 00:39:40.850 align:start position:0% scrappers for the indica from from 00:39:40.850 --> 00:39:43.690 align:start position:0% scrappers for the indica from from angular<00:39:41.350> for<00:39:42.350> making<00:39:42.680> the<00:39:42.740> next<00:39:42.980> installment 00:39:43.690 --> 00:39:43.700 align:start position:0% angular for making the next installment 00:39:43.700 --> 00:39:47.770 align:start position:0% angular for making the next installment of<00:39:43.820> tools<00:39:44.150> which<00:39:44.600> are<00:39:45.730> quite<00:39:46.730> common<00:39:46.790> in<00:39:47.390> the 00:39:47.770 --> 00:39:47.780 align:start position:0% of tools which are quite common in the 00:39:47.780 --> 00:39:52.240 align:start position:0% of tools which are quite common in the banking<00:39:48.260> industry<00:39:49.190> for<00:39:49.370> example<00:39:50.290> and<00:39:51.290> so<00:39:51.950> the 00:39:52.240 --> 00:39:52.250 align:start position:0% banking industry for example and so the 00:39:52.250 --> 00:39:54.520 align:start position:0% banking industry for example and so the work<00:39:52.460> we<00:39:52.670> will<00:39:52.820> be<00:39:52.880> doing<00:39:53.000> a<00:39:53.390> brennan<00:39:53.810> in<00:39:54.140> the 00:39:54.520 --> 00:39:54.530 align:start position:0% work we will be doing a brennan in the 00:39:54.530 --> 00:39:59.220 align:start position:0% work we will be doing a brennan in the medium<00:39:55.220> term<00:39:55.660> making<00:39:56.660> a<00:39:56.720> generalization<00:39:57.880> and 00:39:59.220 --> 00:39:59.230 align:start position:0% medium term making a generalization and 00:39:59.230 --> 00:40:02.680 align:start position:0% medium term making a generalization and detaching<00:40:00.230> it<00:40:00.410> from<00:40:00.530> the<00:40:01.220> cabinet<00:40:01.430> from<00:40:02.150> from 00:40:02.680 --> 00:40:02.690 align:start position:0% detaching it from the cabinet from from 00:40:02.690 --> 00:40:06.220 align:start position:0% detaching it from the cabinet from from women<00:40:03.170> so<00:40:04.160> that<00:40:04.430> we<00:40:04.970> can<00:40:05.210> have<00:40:05.510> a<00:40:05.750> higher-order 00:40:06.220 --> 00:40:06.230 align:start position:0% women so that we can have a higher-order 00:40:06.230 --> 00:40:10.420 align:start position:0% women so that we can have a higher-order radon<00:40:06.980> in<00:40:07.190> which<00:40:07.840> developers<00:40:08.840> can<00:40:09.430> define 00:40:10.420 --> 00:40:10.430 align:start position:0% radon in which developers can define 00:40:10.430 --> 00:40:12.190 align:start position:0% radon in which developers can define their<00:40:10.640> own<00:40:10.670> stages<00:40:11.420> in<00:40:11.720> find<00:40:12.020> their<00:40:12.170> own 00:40:12.190 --> 00:40:12.200 align:start position:0% their own stages in find their own 00:40:12.200 --> 00:40:14.940 align:start position:0% their own stages in find their own operators<00:40:12.860> and<00:40:13.040> so<00:40:13.190> on<00:40:13.370> and<00:40:13.580> just<00:40:14.000> leverage 00:40:14.940 --> 00:40:14.950 align:start position:0% operators and so on and just leverage 00:40:14.950 --> 00:40:21.130 align:start position:0% operators and so on and just leverage let's<00:40:15.950> say<00:40:16.130> that<00:40:18.670> the<00:40:19.670> abstract<00:40:20.150> syntax 00:40:21.130 --> 00:40:21.140 align:start position:0% let's say that the abstract syntax 00:40:21.140 --> 00:40:24.420 align:start position:0% let's say that the abstract syntax behind<00:40:21.740> in<00:40:21.950> all<00:40:22.130> the<00:40:22.280> tooling<00:40:22.610> that<00:40:23.020> they<00:40:24.020> can 00:40:24.420 --> 00:40:24.430 align:start position:0% behind in all the tooling that they can 00:40:24.430 --> 00:40:28.330 align:start position:0% behind in all the tooling that they can transform<00:40:25.430> that<00:40:25.730> into<00:40:26.060> may<00:40:27.010> serve<00:40:28.010> in<00:40:28.160> their 00:40:28.330 --> 00:40:28.340 align:start position:0% transform that into may serve in their 00:40:28.340 --> 00:40:35.290 align:start position:0% transform that into may serve in their various<00:40:29.270> case<00:40:30.460> so<00:40:33.160> when<00:40:34.160> will<00:40:34.400> we<00:40:34.610> be<00:40:34.880> able<00:40:34.910> to 00:40:35.290 --> 00:40:35.300 align:start position:0% various case so when will we be able to 00:40:35.300 --> 00:40:38.260 align:start position:0% various case so when will we be able to use<00:40:35.860> within<00:40:36.860> frog<00:40:37.310> into<00:40:37.760> your<00:40:37.910> main<00:40:38.090> name 00:40:38.260 --> 00:40:38.270 align:start position:0% use within frog into your main name 00:40:38.270 --> 00:40:38.980 align:start position:0% use within frog into your main name again 00:40:38.980 --> 00:40:38.990 align:start position:0% again 00:40:38.990 --> 00:40:42.120 align:start position:0% again we<00:40:39.140> are<00:40:39.260> here<00:40:39.470> we<00:40:39.860> are<00:40:39.890> almost<00:40:40.190> there<00:40:40.520> okay<00:40:40.940> so 00:40:42.120 --> 00:40:42.130 align:start position:0% we are here we are almost there okay so 00:40:42.130 --> 00:40:45.280 align:start position:0% we are here we are almost there okay so we<00:40:43.130> need<00:40:43.280> itself<00:40:43.910> and<00:40:44.210> has<00:40:44.750> its<00:40:45.050> own 00:40:45.280 --> 00:40:45.290 align:start position:0% we need itself and has its own 00:40:45.290 --> 00:40:47.860 align:start position:0% we need itself and has its own blockchain<00:40:46.220> you<00:40:46.670> know<00:40:46.790> it's<00:40:47.090> like<00:40:47.390> a<00:40:47.420> nice 00:40:47.860 --> 00:40:47.870 align:start position:0% blockchain you know it's like a nice 00:40:47.870 --> 00:40:51.780 align:start position:0% blockchain you know it's like a nice change<00:40:48.290> to<00:40:48.650> a<00:40:49.190> few<00:40:49.580> exciting<00:40:50.240> by<00:40:50.960> this<00:40:51.230> email 00:40:51.780 --> 00:40:51.790 align:start position:0% change to a few exciting by this email 00:40:51.790 --> 00:40:56.340 align:start position:0% change to a few exciting by this email we<00:40:52.770> saw<00:40:53.770> before<00:40:54.160> with<00:40:54.760> a<00:40:54.970> rope<00:40:55.510> relay<00:40:55.870> and<00:40:56.200> so 00:40:56.340 --> 00:40:56.350 align:start position:0% we saw before with a rope relay and so 00:40:56.350 --> 00:41:00.480 align:start position:0% we saw before with a rope relay and so on<00:40:56.560> so<00:40:57.100> right<00:40:57.730> now<00:40:58.680> in<00:40:59.680> a<00:40:59.710> dissonant<00:41:00.280> is 00:41:00.480 --> 00:41:00.490 align:start position:0% on so right now in a dissonant is 00:41:00.490 --> 00:41:04.500 align:start position:0% on so right now in a dissonant is connected<00:41:01.030> to<00:41:01.530> two<00:41:02.530> difference<00:41:03.180> if<00:41:04.180> you're<00:41:04.420> in 00:41:04.500 --> 00:41:04.510 align:start position:0% connected to two difference if you're in 00:41:04.510 --> 00:41:07.740 align:start position:0% connected to two difference if you're in this<00:41:04.720> net<00:41:04.990> screen<00:41:05.350> to<00:41:05.470> be<00:41:05.590> inverting<00:41:06.130> and<00:41:06.750> it's 00:41:07.740 --> 00:41:07.750 align:start position:0% this net screen to be inverting and it's 00:41:07.750 --> 00:41:10.740 align:start position:0% this net screen to be inverting and it's pretty<00:41:07.990> too<00:41:08.140> late<00:41:08.410> we've<00:41:09.450> they're<00:41:10.450> all<00:41:10.630> the 00:41:10.740 --> 00:41:10.750 align:start position:0% pretty too late we've they're all the 00:41:10.750 --> 00:41:12.600 align:start position:0% pretty too late we've they're all the tooling<00:41:11.050> is<00:41:11.200> right<00:41:11.530> there<00:41:11.740> we<00:41:12.250> are<00:41:12.340> working 00:41:12.600 --> 00:41:12.610 align:start position:0% tooling is right there we are working 00:41:12.610 --> 00:41:16.380 align:start position:0% tooling is right there we are working heavy<00:41:13.000> on<00:41:14.520> improvement<00:41:15.520> illumination<00:41:16.120> and<00:41:16.240> so 00:41:16.380 --> 00:41:16.390 align:start position:0% heavy on improvement illumination and so 00:41:16.390 --> 00:41:18.960 align:start position:0% heavy on improvement illumination and so on<00:41:16.570> right<00:41:16.810> now<00:41:16.930> the<00:41:17.440> visual<00:41:17.740> information<00:41:17.970> that 00:41:18.960 --> 00:41:18.970 align:start position:0% on right now the visual information that 00:41:18.970 --> 00:41:23.400 align:start position:0% on right now the visual information that we<00:41:19.570> need<00:41:19.720> to<00:41:19.870> type<00:41:20.080> and<00:41:20.620> you<00:41:20.980> have<00:41:22.410> really 00:41:23.400 --> 00:41:23.410 align:start position:0% we need to type and you have really 00:41:23.410 --> 00:41:26.310 align:start position:0% we need to type and you have really comprehensive<00:41:23.950> tutorial<00:41:24.720> for<00:41:25.720> creating<00:41:25.930> the 00:41:26.310 --> 00:41:26.320 align:start position:0% comprehensive tutorial for creating the 00:41:26.320 --> 00:41:28.710 align:start position:0% comprehensive tutorial for creating the correct<00:41:26.560> speed<00:41:26.740> that<00:41:26.950> we<00:41:27.280> that<00:41:27.940> we<00:41:27.970> saw<00:41:28.270> before 00:41:28.710 --> 00:41:28.720 align:start position:0% correct speed that we that we saw before 00:41:28.720 --> 00:41:33.180 align:start position:0% correct speed that we that we saw before and<00:41:30.000> right<00:41:31.000> now<00:41:31.120> undergoing<00:41:32.020> audits<00:41:32.530> and<00:41:32.830> we 00:41:33.180 --> 00:41:33.190 align:start position:0% and right now undergoing audits and we 00:41:33.190 --> 00:41:36.360 align:start position:0% and right now undergoing audits and we are<00:41:33.310> doing<00:41:33.490> a<00:41:33.550> lot<00:41:33.760> of<00:41:33.790> distress<00:41:34.390> testing<00:41:35.370> or 00:41:36.360 --> 00:41:36.370 align:start position:0% are doing a lot of distress testing or 00:41:36.370 --> 00:41:39.840 align:start position:0% are doing a lot of distress testing or their<00:41:36.670> for<00:41:37.000> the<00:41:37.090> following<00:41:37.420> months<00:41:38.700> we<00:41:39.700> also 00:41:39.840 --> 00:41:39.850 align:start position:0% their for the following months we also 00:41:39.850 --> 00:41:44.550 align:start position:0% their for the following months we also want<00:41:40.750> to<00:41:40.870> work<00:41:41.770> on<00:41:42.160> more<00:41:42.790> bridges<00:41:43.150> too<00:41:43.660> because 00:41:44.550 --> 00:41:44.560 align:start position:0% want to work on more bridges too because 00:41:44.560 --> 00:41:46.920 align:start position:0% want to work on more bridges too because technically<00:41:44.980> them<00:41:45.400> is<00:41:45.580> done<00:41:45.820> and<00:41:46.120> some<00:41:46.780> way 00:41:46.920 --> 00:41:46.930 align:start position:0% technically them is done and some way 00:41:46.930 --> 00:41:50.490 align:start position:0% technically them is done and some way for<00:41:47.530> cannot<00:41:48.160> speak<00:41:48.430> I<00:41:48.580> mean<00:41:48.760> that<00:41:49.300> it's<00:41:49.690> it's 00:41:50.490 --> 00:41:50.500 align:start position:0% for cannot speak I mean that it's it's 00:41:50.500 --> 00:41:55.230 align:start position:0% for cannot speak I mean that it's it's bound<00:41:50.860> to<00:41:51.180> serve<00:41:52.180> as<00:41:52.570> many<00:41:52.990> different<00:41:54.240> my 00:41:55.230 --> 00:41:55.240 align:start position:0% bound to serve as many different my 00:41:55.240 --> 00:41:59.790 align:start position:0% bound to serve as many different my contract<00:41:55.720> platforms<00:41:56.440> as<00:41:57.100> possible<00:41:57.280> and<00:41:58.800> it's 00:41:59.790 --> 00:41:59.800 align:start position:0% contract platforms as possible and it's 00:41:59.800 --> 00:42:02.580 align:start position:0% contract platforms as possible and it's expected<00:42:00.310> to<00:42:00.490> be<00:42:01.240> launched<00:42:01.540> on<00:42:01.810> maintenance 00:42:02.580 --> 00:42:02.590 align:start position:0% expected to be launched on maintenance 00:42:02.590 --> 00:42:10.940 align:start position:0% expected to be launched on maintenance for<00:42:02.890> every<00:42:03.820> next<00:42:04.750> year<00:42:05.400> so<00:42:08.850> the<00:42:09.850> price<00:42:10.150> P<00:42:10.390> is 00:42:10.940 --> 00:42:10.950 align:start position:0% for every next year so the price P is 00:42:10.950 --> 00:42:15.800 align:start position:0% for every next year so the price P is pretty<00:42:11.950> low<00:42:12.340> level<00:42:12.600> affinity<00:42:13.600> for<00:42:14.440> writing 00:42:15.800 --> 00:42:15.810 align:start position:0% pretty low level affinity for writing 00:42:15.810 --> 00:42:21.780 align:start position:0% pretty low level affinity for writing things<00:42:16.810> like<00:42:16.900> define<00:42:18.270> utilities<00:42:19.270> that<00:42:20.610> we<00:42:21.610> can 00:42:21.780 --> 00:42:21.790 align:start position:0% things like define utilities that we can 00:42:21.790 --> 00:42:27.390 align:start position:0% things like define utilities that we can create<00:42:22.000> many<00:42:22.710> funny<00:42:23.710> things<00:42:24.990> in<00:42:25.990> in<00:42:26.620> a<00:42:26.830> really 00:42:27.390 --> 00:42:27.400 align:start position:0% create many funny things in in a really 00:42:27.400 --> 00:42:30.690 align:start position:0% create many funny things in in a really easy<00:42:27.910> way<00:42:28.300> and<00:42:28.660> in<00:42:29.260> a<00:42:29.380> decentralized<00:42:29.770> way<00:42:30.190> that 00:42:30.690 --> 00:42:30.700 align:start position:0% easy way and in a decentralized way that 00:42:30.700 --> 00:42:32.100 align:start position:0% easy way and in a decentralized way that was<00:42:30.940> not<00:42:31.180> possible<00:42:31.480> before 00:42:32.100 --> 00:42:32.110 align:start position:0% was not possible before 00:42:32.110 --> 00:42:36.890 align:start position:0% was not possible before so<00:42:33.150> or<00:42:34.150> especially<00:42:34.930> for<00:42:35.140> tech<00:42:35.320> con<00:42:35.560> we<00:42:36.160> try<00:42:36.610> to 00:42:36.890 --> 00:42:36.900 align:start position:0% so or especially for tech con we try to 00:42:36.900 --> 00:42:41.670 align:start position:0% so or especially for tech con we try to push<00:42:37.980> the<00:42:38.980> limits<00:42:39.010> of<00:42:39.550> what<00:42:40.300> we<00:42:40.930> have<00:42:41.230> ran<00:42:41.530> out 00:42:41.670 --> 00:42:41.680 align:start position:0% push the limits of what we have ran out 00:42:41.680 --> 00:42:44.130 align:start position:0% push the limits of what we have ran out of<00:42:41.710> all<00:42:42.130> the<00:42:42.280> tooling<00:42:42.550> and<00:42:43.030> what<00:42:43.360> tween<00:42:43.810> n<00:42:43.990> is 00:42:44.130 --> 00:42:44.140 align:start position:0% of all the tooling and what tween n is 00:42:44.140 --> 00:42:47.280 align:start position:0% of all the tooling and what tween n is right<00:42:44.380> now<00:42:44.530> and<00:42:44.980> we<00:42:45.640> came<00:42:46.150> up<00:42:46.330> in<00:42:46.600> this<00:42:46.810> small 00:42:47.280 --> 00:42:47.290 align:start position:0% right now and we came up in this small 00:42:47.290 --> 00:42:49.830 align:start position:0% right now and we came up in this small that<00:42:48.250> that<00:42:48.760> guy 00:42:49.830 --> 00:42:49.840 align:start position:0% that that guy 00:42:49.840 --> 00:42:53.970 align:start position:0% that that guy it's<00:42:50.410> called<00:42:51.120> impressive<00:42:52.120> it's<00:42:52.570> our<00:42:53.530> rinkeby 00:42:53.970 --> 00:42:53.980 align:start position:0% it's called impressive it's our rinkeby 00:42:53.980 --> 00:42:59.340 align:start position:0% it's called impressive it's our rinkeby Holly<00:42:54.370> story<00:42:56.040> complete<00:42:57.660> in<00:42:58.660> a<00:42:58.720> few<00:42:58.930> months<00:42:59.170> we 00:42:59.340 --> 00:42:59.350 align:start position:0% Holly story complete in a few months we 00:42:59.350 --> 00:43:01.980 align:start position:0% Holly story complete in a few months we can<00:42:59.560> migrate<00:42:59.980> time<00:43:00.810> maintenance<00:43:01.810> and 00:43:01.980 --> 00:43:01.990 align:start position:0% can migrate time maintenance and 00:43:01.990 --> 00:43:05.300 align:start position:0% can migrate time maintenance and basically<00:43:02.580> it's<00:43:03.580> a<00:43:03.670> potential<00:43:04.090> market<00:43:04.270> for 00:43:05.300 --> 00:43:05.310 align:start position:0% basically it's a potential market for 00:43:05.310 --> 00:43:15.210 align:start position:0% basically it's a potential market for the<00:43:06.870> point<00:43:07.870> prices 00:43:15.210 --> 00:43:15.220 align:start position:0% 00:43:15.220 --> 00:43:20.370 align:start position:0% [Music] 00:43:20.370 --> 00:43:20.380 align:start position:0% 00:43:20.380 --> 00:43:24.420 align:start position:0% so<00:43:20.920> you<00:43:21.339> can<00:43:21.579> try<00:43:21.970> to<00:43:22.029> predict<00:43:22.539> each<00:43:23.430> which 00:43:24.420 --> 00:43:24.430 align:start position:0% so you can try to predict each which 00:43:24.430 --> 00:43:28.049 align:start position:0% so you can try to predict each which point<00:43:25.420> we'll<00:43:25.630> be<00:43:25.869> performing<00:43:26.319> best<00:43:27.309> tomorrow 00:43:28.049 --> 00:43:28.059 align:start position:0% point we'll be performing best tomorrow 00:43:28.059 --> 00:43:33.239 align:start position:0% point we'll be performing best tomorrow so<00:43:29.789> you<00:43:30.789> can<00:43:30.849> see<00:43:31.239> here<00:43:31.930> all<00:43:32.229> day<00:43:32.619> all<00:43:33.039> the 00:43:33.239 --> 00:43:33.249 align:start position:0% so you can see here all day all the 00:43:33.249 --> 00:43:35.690 align:start position:0% so you can see here all day all the prediction<00:43:33.759> volumes<00:43:34.119> for<00:43:34.359> each<00:43:34.539> different 00:43:35.690 --> 00:43:35.700 align:start position:0% prediction volumes for each different 00:43:35.700 --> 00:43:38.249 align:start position:0% prediction volumes for each different for<00:43:36.700> each<00:43:36.729> different<00:43:37.239> comparing<00:43:37.930> different 00:43:38.249 --> 00:43:38.259 align:start position:0% for each different comparing different 00:43:38.259 --> 00:43:41.190 align:start position:0% for each different comparing different cryptocurrency<00:43:38.859> right<00:43:39.849> now<00:43:39.970> is<00:43:40.119> is<00:43:40.359> waiting 00:43:41.190 --> 00:43:41.200 align:start position:0% cryptocurrency right now is is waiting 00:43:41.200 --> 00:43:45.239 align:start position:0% cryptocurrency right now is is waiting in<00:43:41.650> a<00:43:41.769> surprise<00:43:42.690> and<00:43:43.690> here<00:43:44.170> are<00:43:44.349> your<00:43:44.559> return 00:43:45.239 --> 00:43:45.249 align:start position:0% in a surprise and here are your return 00:43:45.249 --> 00:43:48.539 align:start position:0% in a surprise and here are your return so<00:43:45.549> we<00:43:45.759> can<00:43:45.940> I<00:43:46.210> think<00:43:47.049> I<00:43:47.289> can<00:43:47.319> double<00:43:48.160> down<00:43:48.309> on 00:43:48.539 --> 00:43:48.549 align:start position:0% so we can I think I can double down on 00:43:48.549 --> 00:43:56.359 align:start position:0% so we can I think I can double down on Connie's<00:43:49.059> so<00:43:53.130> let's<00:43:54.130> go<00:43:54.339> with<00:43:54.609> speed<00:43:55.180> if<00:43:55.660> you 00:43:56.359 --> 00:43:56.369 align:start position:0% Connie's so let's go with speed if you 00:43:56.369 --> 00:44:07.280 align:start position:0% Connie's so let's go with speed if you see<00:43:57.369> you<00:43:57.489> point<00:43:57.849> to<00:43:58.170> send<00:43:59.170> dick 00:44:07.280 --> 00:44:07.290 align:start position:0% 00:44:07.290 --> 00:44:10.400 align:start position:0% so<00:44:07.860> this<00:44:08.130> is<00:44:08.280> for<00:44:09.180> tomorrow's<00:44:09.810> markets<00:44:10.050> so 00:44:10.400 --> 00:44:10.410 align:start position:0% so this is for tomorrow's markets so 00:44:10.410 --> 00:44:12.080 align:start position:0% so this is for tomorrow's markets so they<00:44:10.740> can<00:44:11.190> predict<00:44:11.520> what<00:44:11.820> will<00:44:12.030> happen 00:44:12.080 --> 00:44:12.090 align:start position:0% they can predict what will happen 00:44:12.090 --> 00:44:12.830 align:start position:0% they can predict what will happen tomorrow 00:44:12.830 --> 00:44:12.840 align:start position:0% tomorrow 00:44:12.840 --> 00:44:15.050 align:start position:0% tomorrow and<00:44:13.020> that's<00:44:13.470> when<00:44:13.620> as<00:44:13.770> tomorrow<00:44:14.100> finishes<00:44:14.790> I 00:44:15.050 --> 00:44:15.060 align:start position:0% and that's when as tomorrow finishes I 00:44:15.060 --> 00:44:18.710 align:start position:0% and that's when as tomorrow finishes I can<00:44:15.560> we<00:44:16.560> throw<00:44:16.770> my<00:44:17.130> price<00:44:17.460> and<00:44:17.850> buy<00:44:18.000> if<00:44:18.360> I'm<00:44:18.510> one 00:44:18.710 --> 00:44:18.720 align:start position:0% can we throw my price and buy if I'm one 00:44:18.720 --> 00:44:20.780 align:start position:0% can we throw my price and buy if I'm one of<00:44:18.900> the<00:44:19.020> winners<00:44:19.200> because<00:44:19.680> your<00:44:20.130> turn<00:44:20.340> your 00:44:20.780 --> 00:44:20.790 align:start position:0% of the winners because your turn your 00:44:20.790 --> 00:44:23.060 align:start position:0% of the winners because your turn your potential<00:44:21.540> we<00:44:21.840> pour<00:44:22.140> for<00:44:22.500> you<00:44:22.530> for<00:44:22.950> each 00:44:23.060 --> 00:44:23.070 align:start position:0% potential we pour for you for each 00:44:23.070 --> 00:44:25.460 align:start position:0% potential we pour for you for each option<00:44:23.430> and<00:44:24.030> then<00:44:24.270> for<00:44:24.540> example<00:44:24.630> we<00:44:25.050> can<00:44:25.230> see 00:44:25.460 --> 00:44:25.470 align:start position:0% option and then for example we can see 00:44:25.470 --> 00:44:30.280 align:start position:0% option and then for example we can see here<00:44:26.720> is<00:44:27.720> the<00:44:27.960> yesterday's<00:44:28.830> market 00:44:30.280 --> 00:44:30.290 align:start position:0% here is the yesterday's market 00:44:30.290 --> 00:44:33.610 align:start position:0% here is the yesterday's market predictions<00:44:31.290> for<00:44:31.770> yes<00:44:31.980> that<00:44:32.220> they<00:44:32.370> are<00:44:32.700> close 00:44:33.610 --> 00:44:33.620 align:start position:0% predictions for yes that they are close 00:44:33.620 --> 00:44:37.880 align:start position:0% predictions for yes that they are close okay<00:44:34.650> this<00:44:35.130> work<00:44:35.510> open<00:44:36.510> yesterday<00:44:37.290> but<00:44:37.530> uses 00:44:37.880 --> 00:44:37.890 align:start position:0% okay this work open yesterday but uses 00:44:37.890 --> 00:44:39.260 align:start position:0% okay this work open yesterday but uses the<00:44:38.160> market<00:44:38.460> work<00:44:38.820> today 00:44:39.260 --> 00:44:39.270 align:start position:0% the market work today 00:44:39.270 --> 00:44:42.200 align:start position:0% the market work today actually<00:44:39.750> this<00:44:40.170> is<00:44:40.640> tracking<00:44:41.640> what<00:44:41.850> is 00:44:42.200 --> 00:44:42.210 align:start position:0% actually this is tracking what is 00:44:42.210 --> 00:44:43.280 align:start position:0% actually this is tracking what is happening<00:44:42.780> today 00:44:43.280 --> 00:44:43.290 align:start position:0% happening today 00:44:43.290 --> 00:44:49.100 align:start position:0% happening today so<00:44:44.720> tonight<00:44:45.720> it<00:44:46.200> will<00:44:46.410> be<00:44:46.470> closed<00:44:46.830> and<00:44:48.110> and 00:44:49.100 --> 00:44:49.110 align:start position:0% so tonight it will be closed and and 00:44:49.110 --> 00:44:52.400 align:start position:0% so tonight it will be closed and and what<00:44:50.100> will<00:44:50.310> happen<00:44:50.640> is<00:44:50.790> that<00:44:51.030> the<00:44:51.600> contract 00:44:52.400 --> 00:44:52.410 align:start position:0% what will happen is that the contract 00:44:52.410 --> 00:44:55.730 align:start position:0% what will happen is that the contract behind<00:44:52.560> this<00:44:52.950> will<00:44:53.750> send<00:44:54.750> the<00:44:54.870> data<00:44:54.900> request 00:44:55.730 --> 00:44:55.740 align:start position:0% behind this will send the data request 00:44:55.740 --> 00:44:58.880 align:start position:0% behind this will send the data request with<00:44:56.310> that<00:44:56.520> women<00:44:57.180> will<00:44:57.390> attest<00:44:57.900> what's<00:44:58.530> the 00:44:58.880 --> 00:44:58.890 align:start position:0% with that women will attest what's the 00:44:58.890 --> 00:45:01.940 align:start position:0% with that women will attest what's the actual<00:44:59.550> result<00:45:00.120> and<00:45:00.360> consuming<00:45:01.140> from<00:45:01.470> three 00:45:01.940 --> 00:45:01.950 align:start position:0% actual result and consuming from three 00:45:01.950 --> 00:45:05.360 align:start position:0% actual result and consuming from three different<00:45:02.360> price<00:45:03.390> api's<00:45:04.110> and<00:45:04.710> will<00:45:04.980> aggregate 00:45:05.360 --> 00:45:05.370 align:start position:0% different price api's and will aggregate 00:45:05.370 --> 00:45:06.200 align:start position:0% different price api's and will aggregate everything 00:45:06.200 --> 00:45:06.210 align:start position:0% everything 00:45:06.210 --> 00:45:08.810 align:start position:0% everything push<00:45:06.720> the<00:45:06.960> result<00:45:07.530> into<00:45:08.010> the<00:45:08.190> smart<00:45:08.550> hunter 00:45:08.810 --> 00:45:08.820 align:start position:0% push the result into the smart hunter 00:45:08.820 --> 00:45:11.750 align:start position:0% push the result into the smart hunter behind<00:45:08.970> the<00:45:09.300> tablet<00:45:09.690> and<00:45:09.960> it<00:45:10.170> will<00:45:10.410> allow<00:45:11.370> the 00:45:11.750 --> 00:45:11.760 align:start position:0% behind the tablet and it will allow the 00:45:11.760 --> 00:45:15.170 align:start position:0% behind the tablet and it will allow the ones<00:45:12.060> that<00:45:12.420> hold<00:45:12.720> it<00:45:12.960> for<00:45:13.410> the<00:45:14.180> most 00:45:15.170 --> 00:45:15.180 align:start position:0% ones that hold it for the most 00:45:15.180 --> 00:45:17.840 align:start position:0% ones that hold it for the most performing<00:45:15.810> and<00:45:15.960> ripped<00:45:16.380> off<00:45:16.590> to<00:45:17.070> take<00:45:17.580> a 00:45:17.840 --> 00:45:17.850 align:start position:0% performing and ripped off to take a 00:45:17.850 --> 00:45:23.210 align:start position:0% performing and ripped off to take a share<00:45:18.330> of<00:45:18.360> the<00:45:18.690> other<00:45:19.170> price<00:45:19.530> okay<00:45:20.330> so<00:45:22.220> make 00:45:23.210 --> 00:45:23.220 align:start position:0% share of the other price okay so make 00:45:23.220 --> 00:45:25.850 align:start position:0% share of the other price okay so make sure<00:45:23.250> to<00:45:23.460> check<00:45:24.210> everything<00:45:25.050> so<00:45:25.650> that 00:45:25.850 --> 00:45:25.860 align:start position:0% sure to check everything so that 00:45:25.860 --> 00:45:28.430 align:start position:0% sure to check everything so that government<00:45:26.280> see<00:45:26.490> how<00:45:27.120> the<00:45:27.180> markets<00:45:27.750> all<00:45:28.080> paths 00:45:28.430 --> 00:45:28.440 align:start position:0% government see how the markets all paths 00:45:28.440 --> 00:45:31.610 align:start position:0% government see how the markets all paths which<00:45:28.770> are<00:45:28.920> the<00:45:29.100> winners<00:45:29.430> and<00:45:30.050> hopefully<00:45:31.050> get 00:45:31.610 --> 00:45:31.620 align:start position:0% which are the winners and hopefully get 00:45:31.620 --> 00:45:34.950 align:start position:0% which are the winners and hopefully get some<00:45:33.020> drinking<00:45:34.020> it 00:45:34.950 --> 00:45:34.960 align:start position:0% some drinking it 00:45:34.960 --> 00:45:37.290 align:start position:0% some drinking it game<00:45:35.109> so<00:45:36.069> the<00:45:36.160> witness<00:45:36.280> knows<00:45:36.609> only<00:45:37.030> you<00:45:37.150> guys 00:45:37.290 --> 00:45:37.300 align:start position:0% game so the witness knows only you guys 00:45:37.300 --> 00:45:40.200 align:start position:0% game so the witness knows only you guys right<00:45:37.599> now<00:45:37.630> behind<00:45:38.050> this<00:45:38.349> not<00:45:39.339> okay<00:45:39.940> actually 00:45:40.200 --> 00:45:40.210 align:start position:0% right now behind this not okay actually 00:45:40.210 --> 00:45:44.160 align:start position:0% right now behind this not okay actually it's<00:45:40.800> totally<00:45:41.800> like<00:45:42.760> an<00:45:43.030> open<00:45:43.599> for<00:45:43.839> anyone 00:45:44.160 --> 00:45:44.170 align:start position:0% it's totally like an open for anyone 00:45:44.170 --> 00:45:48.750 align:start position:0% it's totally like an open for anyone drama<00:45:44.680> doesn't<00:45:45.280> know<00:45:45.400> reason<00:45:46.890> very<00:45:47.890> simple 00:45:48.750 --> 00:45:48.760 align:start position:0% drama doesn't know reason very simple 00:45:48.760 --> 00:45:53.640 align:start position:0% drama doesn't know reason very simple I<00:45:48.930> can<00:45:49.930> follow<00:45:50.230> one<00:45:50.589> right<00:45:51.099> now<00:45:51.359> like<00:45:52.650> longer 00:45:53.640 --> 00:45:53.650 align:start position:0% I can follow one right now like longer 00:45:53.650 --> 00:46:18.290 align:start position:0% I can follow one right now like longer run<00:45:54.640> it<00:45:55.530> with<00:45:56.530> that<00:45:56.849> we<00:45:57.849> met<00:45:58.180> trust 00:46:18.290 --> 00:46:18.300 align:start position:0% 00:46:18.300 --> 00:46:25.410 align:start position:0% [Music] 00:46:25.410 --> 00:46:25.420 align:start position:0% 00:46:25.420 --> 00:46:30.350 align:start position:0% so<00:46:26.420> this<00:46:26.930> villainous<00:46:27.320> on<00:46:27.590> that<00:46:27.830> note<00:46:28.070> in<00:46:28.310> there 00:46:30.350 --> 00:46:30.360 align:start position:0% so this villainous on that note in there 00:46:30.360 --> 00:46:35.020 align:start position:0% so this villainous on that note in there [Music] 00:46:35.020 --> 00:46:35.030 align:start position:0% 00:46:35.030 --> 00:46:37.650 align:start position:0% so<00:46:35.570> many 00:46:37.650 --> 00:46:37.660 align:start position:0% so many 00:46:37.660 --> 00:46:40.420 align:start position:0% so many let's<00:46:38.660> verify<00:46:39.260> the<00:46:39.530> execution<00:46:40.190> of<00:46:40.250> the 00:46:40.420 --> 00:46:40.430 align:start position:0% let's verify the execution of the 00:46:40.430 --> 00:46:43.360 align:start position:0% let's verify the execution of the telling<00:46:40.790> on<00:46:40.910> face<00:46:41.290> yeah<00:46:42.290> what<00:46:42.740> what<00:46:43.010> happens 00:46:43.360 --> 00:46:43.370 align:start position:0% telling on face yeah what what happens 00:46:43.370 --> 00:46:45.750 align:start position:0% telling on face yeah what what happens is<00:46:43.520> that<00:46:43.760> as<00:46:44.090> soon<00:46:44.150> as<00:46:44.480> you<00:46:44.720> have<00:46:44.900> the<00:46:45.110> reveals 00:46:45.750 --> 00:46:45.760 align:start position:0% is that as soon as you have the reveals 00:46:45.760 --> 00:46:48.850 align:start position:0% is that as soon as you have the reveals anyone<00:46:46.760> everyone<00:46:47.300> knows<00:46:47.540> the<00:46:47.840> Italians<00:46:48.650> so 00:46:48.850 --> 00:46:48.860 align:start position:0% anyone everyone knows the Italians so 00:46:48.860 --> 00:46:51.100 align:start position:0% anyone everyone knows the Italians so they<00:46:49.040> come<00:46:49.220> free<00:46:49.490> communities<00:46:50.450> the<00:46:50.630> results 00:46:51.100 --> 00:46:51.110 align:start position:0% they come free communities the results 00:46:51.110 --> 00:46:53.710 align:start position:0% they come free communities the results of<00:46:51.260> Italian<00:46:51.680> and<00:46:51.860> n105<00:46:52.730> as<00:46:53.240> the<00:46:53.360> talents<00:46:53.660> of 00:46:53.710 --> 00:46:53.720 align:start position:0% of Italian and n105 as the talents of 00:46:53.720 --> 00:46:55.890 align:start position:0% of Italian and n105 as the talents of reasoning<00:46:54.260> blocks<00:46:54.620> what<00:46:54.920> that<00:46:55.370> means<00:46:55.610> is<00:46:55.820> that 00:46:55.890 --> 00:46:55.900 align:start position:0% reasoning blocks what that means is that 00:46:55.900 --> 00:46:59.560 align:start position:0% reasoning blocks what that means is that other<00:46:56.900> nodes<00:46:57.460> reject<00:46:58.460> blocks<00:46:58.880> at<00:46:59.150> the<00:46:59.210> named 00:46:59.560 --> 00:46:59.570 align:start position:0% other nodes reject blocks at the named 00:46:59.570 --> 00:47:02.440 align:start position:0% other nodes reject blocks at the named wrong<00:47:00.170> time<00:47:00.410> the<00:47:00.980> research<00:47:01.610> the<00:47:01.790> motivation 00:47:02.440 --> 00:47:02.450 align:start position:0% wrong time the research the motivation 00:47:02.450 --> 00:47:05.740 align:start position:0% wrong time the research the motivation that's<00:47:03.140> that's<00:47:03.560> no<00:47:03.770> one<00:47:03.980> there<00:47:04.190> citing<00:47:04.910> damn 00:47:05.740 --> 00:47:05.750 align:start position:0% that's that's no one there citing damn 00:47:05.750 --> 00:47:10.030 align:start position:0% that's that's no one there citing damn the<00:47:06.320> result<00:47:06.680> is<00:47:06.950> brought<00:47:07.820> about<00:47:08.300> you<00:47:08.630> too<00:47:09.170> for 00:47:10.030 --> 00:47:10.040 align:start position:0% the result is brought about you too for 00:47:10.040 --> 00:47:12.430 align:start position:0% the result is brought about you too for example<00:47:10.460> and<00:47:10.700> that's<00:47:11.210> very<00:47:11.870> funny 00:47:12.430 --> 00:47:12.440 align:start position:0% example and that's very funny 00:47:12.440 --> 00:47:15.430 align:start position:0% example and that's very funny so<00:47:12.860> there<00:47:13.460> the<00:47:14.300> winded<00:47:14.720> reach<00:47:14.930> interface 00:47:15.430 --> 00:47:15.440 align:start position:0% so there the winded reach interface 00:47:15.440 --> 00:47:19.180 align:start position:0% so there the winded reach interface actually<00:47:15.800> verifies<00:47:16.760> the<00:47:16.970> transaction<00:47:17.590> who<00:47:18.590> SP 00:47:19.180 --> 00:47:19.190 align:start position:0% actually verifies the transaction who SP 00:47:19.190 --> 00:47:22.090 align:start position:0% actually verifies the transaction who SP realization<00:47:19.880> it<00:47:20.180> verifies<00:47:20.720> that<00:47:21.100> the 00:47:22.090 --> 00:47:22.100 align:start position:0% realization it verifies that the 00:47:22.100 --> 00:47:24.310 align:start position:0% realization it verifies that the transaction<00:47:22.490> belongs<00:47:23.090> to<00:47:23.390> women<00:47:23.570> and<00:47:24.050> that 00:47:24.310 --> 00:47:24.320 align:start position:0% transaction belongs to women and that 00:47:24.320 --> 00:47:27.220 align:start position:0% transaction belongs to women and that that<00:47:24.860> has<00:47:25.280> been<00:47:25.520> accepted<00:47:26.000> as<00:47:26.420> they<00:47:26.690> dumped<00:47:26.990> by 00:47:27.220 --> 00:47:27.230 align:start position:0% that has been accepted as they dumped by 00:47:27.230 --> 00:47:29.740 align:start position:0% that has been accepted as they dumped by the<00:47:27.290> women<00:47:27.800> Network<00:47:28.190> as<00:47:28.550> they<00:47:28.880> tally<00:47:29.150> for<00:47:29.540> that 00:47:29.740 --> 00:47:29.750 align:start position:0% the women Network as they tally for that 00:47:29.750 --> 00:47:33.910 align:start position:0% the women Network as they tally for that particular<00:47:30.580> request<00:47:32.200> so<00:47:33.200> this<00:47:33.410> is<00:47:33.650> now 00:47:33.910 --> 00:47:33.920 align:start position:0% particular request so this is now 00:47:33.920 --> 00:47:40.190 align:start position:0% particular request so this is now singing 00:47:40.190 --> 00:47:40.200 align:start position:0% 00:47:40.200 --> 00:47:42.840 align:start position:0% you<00:47:41.200> know<00:47:41.320> right<00:47:41.530> now<00:47:41.680> look<00:47:42.100> what<00:47:42.430> happens<00:47:42.760> to 00:47:42.840 --> 00:47:42.850 align:start position:0% you know right now look what happens to 00:47:42.850 --> 00:47:45.360 align:start position:0% you know right now look what happens to the<00:47:43.000> bees<00:47:43.810> and<00:47:44.320> like<00:47:44.470> witness<00:47:44.770> presentation 00:47:45.360 --> 00:47:45.370 align:start position:0% the bees and like witness presentation 00:47:45.370 --> 00:47:46.800 align:start position:0% the bees and like witness presentation if<00:47:45.550> you<00:47:45.580> have<00:47:45.760> your<00:47:45.880> persistent<00:47:46.690> or 00:47:46.800 --> 00:47:46.810 align:start position:0% if you have your persistent or 00:47:46.810 --> 00:47:49.230 align:start position:0% if you have your persistent or intermittent<00:47:47.320> error<00:47:47.620> on<00:47:47.950> my<00:47:48.100> API<00:47:48.610> like<00:47:48.910> melmac 00:47:49.230 --> 00:47:49.240 align:start position:0% intermittent error on my API like melmac 00:47:49.240 --> 00:47:51.960 align:start position:0% intermittent error on my API like melmac peso<00:47:49.570> gets<00:47:49.960> 500<00:47:50.920> the<00:47:51.010> other<00:47:51.130> three<00:47:51.370> battle 00:47:51.960 --> 00:47:51.970 align:start position:0% peso gets 500 the other three battle 00:47:51.970 --> 00:47:54.810 align:start position:0% peso gets 500 the other three battle response<00:47:52.980> that's<00:47:53.980> that's<00:47:54.370> that's<00:47:54.670> quite 00:47:54.810 --> 00:47:54.820 align:start position:0% response that's that's that's quite 00:47:54.820 --> 00:48:00.080 align:start position:0% response that's that's that's quite important<00:47:56.910> dirt<00:47:57.910> in<00:47:58.330> two<00:47:58.450> different<00:47:58.600> things 00:48:00.080 --> 00:48:00.090 align:start position:0% important dirt in two different things 00:48:00.090 --> 00:48:03.570 align:start position:0% important dirt in two different things India<00:48:01.090> campaign<00:48:01.390> campaign<00:48:02.080> out<00:48:03.070> of<00:48:03.250> the<00:48:03.400> loop 00:48:03.570 --> 00:48:03.580 align:start position:0% India campaign campaign out of the loop 00:48:03.580 --> 00:48:06.930 align:start position:0% India campaign campaign out of the loop and<00:48:03.850> if<00:48:04.600> it's<00:48:04.960> true<00:48:05.350> that<00:48:05.440> I<00:48:05.980> know<00:48:06.490> want<00:48:06.610> you<00:48:06.850> to 00:48:06.930 --> 00:48:06.940 align:start position:0% and if it's true that I know want you to 00:48:06.940 --> 00:48:09.780 align:start position:0% and if it's true that I know want you to take<00:48:07.450> really<00:48:07.900> prominent<00:48:08.650> from<00:48:08.890> that<00:48:09.190> because 00:48:09.780 --> 00:48:09.790 align:start position:0% take really prominent from that because 00:48:09.790 --> 00:48:12.780 align:start position:0% take really prominent from that because they<00:48:10.120> are<00:48:10.270> not<00:48:10.510> guilty<00:48:11.020> for<00:48:11.410> that<00:48:11.560> the<00:48:12.490> witness 00:48:12.780 --> 00:48:12.790 align:start position:0% they are not guilty for that the witness 00:48:12.790 --> 00:48:16.590 align:start position:0% they are not guilty for that the witness in<00:48:12.910> notes<00:48:13.120> so<00:48:13.720> what<00:48:14.350> happens<00:48:14.740> is<00:48:15.010> that<00:48:15.600> the 00:48:16.590 --> 00:48:16.600 align:start position:0% in notes so what happens is that the 00:48:16.600 --> 00:48:20.010 align:start position:0% in notes so what happens is that the slashing<00:48:17.170> right<00:48:17.740> now<00:48:17.890> is<00:48:18.550> on<00:48:19.030> reputation<00:48:19.780> so 00:48:20.010 --> 00:48:20.020 align:start position:0% slashing right now is on reputation so 00:48:20.020 --> 00:48:22.170 align:start position:0% slashing right now is on reputation so there's<00:48:20.530> actually<00:48:20.770> some<00:48:21.190> repetition<00:48:21.820> system 00:48:22.170 --> 00:48:22.180 align:start position:0% there's actually some repetition system 00:48:22.180 --> 00:48:25.380 align:start position:0% there's actually some repetition system behind<00:48:22.780> these<00:48:22.960> which<00:48:23.230> simply<00:48:23.770> as<00:48:24.250> a<00:48:24.730> score<00:48:25.120> of 00:48:25.380 --> 00:48:25.390 align:start position:0% behind these which simply as a score of 00:48:25.390 --> 00:48:29.610 align:start position:0% behind these which simply as a score of how<00:48:26.610> often<00:48:27.610> and<00:48:27.910> how<00:48:27.940> often<00:48:28.540> every<00:48:28.990> single 00:48:29.610 --> 00:48:29.620 align:start position:0% how often and how often every single 00:48:29.620 --> 00:48:35.010 align:start position:0% how often and how often every single mode<00:48:30.990> and<00:48:32.400> most<00:48:33.400> part<00:48:33.730> of<00:48:33.970> the<00:48:34.120> majority<00:48:34.660> let's 00:48:35.010 --> 00:48:35.020 align:start position:0% mode and most part of the majority let's 00:48:35.020 --> 00:48:37.920 align:start position:0% mode and most part of the majority let's say<00:48:35.190> how<00:48:36.190> often<00:48:36.430> they<00:48:36.850> were<00:48:36.880> not<00:48:37.300> figured<00:48:37.780> out 00:48:37.920 --> 00:48:37.930 align:start position:0% say how often they were not figured out 00:48:37.930 --> 00:48:40.740 align:start position:0% say how often they were not figured out by<00:48:38.320> tally<00:48:38.860> function<00:48:39.580> title<00:48:39.940> is<00:48:40.060> pits<00:48:40.330> great 00:48:40.740 --> 00:48:40.750 align:start position:0% by tally function title is pits great 00:48:40.750 --> 00:48:46.800 align:start position:0% by tally function title is pits great mental<00:48:41.020> skills<00:48:41.410> so<00:48:43.950> it's<00:48:44.950> important<00:48:45.810> this 00:48:46.800 --> 00:48:46.810 align:start position:0% mental skills so it's important this 00:48:46.810 --> 00:48:50.070 align:start position:0% mental skills so it's important this like<00:48:47.470> to<00:48:47.680> design<00:48:48.070> the<00:48:48.790> tallies<00:48:49.180> very<00:48:49.810> very 00:48:50.070 --> 00:48:50.080 align:start position:0% like to design the tallies very very 00:48:50.080 --> 00:48:55.200 align:start position:0% like to design the tallies very very well<00:48:50.920> so<00:48:51.460> as<00:48:51.640> not<00:48:52.380> do<00:48:53.380> that<00:48:53.590> kind<00:48:53.890> of<00:48:54.040> stuff<00:48:54.760> but 00:48:55.200 --> 00:48:55.210 align:start position:0% well so as not do that kind of stuff but 00:48:55.210 --> 00:48:59.460 align:start position:0% well so as not do that kind of stuff but then<00:48:55.450> it's<00:48:55.990> true<00:48:56.640> what<00:48:57.640> some<00:48:58.630> attacker<00:48:59.080> who 00:48:59.460 --> 00:48:59.470 align:start position:0% then it's true what some attacker who 00:48:59.470 --> 00:49:02.730 align:start position:0% then it's true what some attacker who come<00:49:00.310> with<00:49:00.640> some<00:49:00.850> crazy<00:49:01.570> request<00:49:02.110> that<00:49:02.410> varies 00:49:02.730 --> 00:49:02.740 align:start position:0% come with some crazy request that varies 00:49:02.740 --> 00:49:05.580 align:start position:0% come with some crazy request that varies really<00:49:03.400> really<00:49:03.760> cheating<00:49:04.300> angry<00:49:04.690> eyes<00:49:04.840> so<00:49:05.470> as 00:49:05.580 --> 00:49:05.590 align:start position:0% really really cheating angry eyes so as 00:49:05.590 --> 00:49:08.610 align:start position:0% really really cheating angry eyes so as to<00:49:05.800> damage<00:49:06.220> the<00:49:06.520> system<00:49:06.910> but<00:49:07.500> actually<00:49:08.500> the 00:49:08.610 --> 00:49:08.620 align:start position:0% to damage the system but actually the 00:49:08.620 --> 00:49:11.090 align:start position:0% to damage the system but actually the way<00:49:08.770> that<00:49:09.190> the<00:49:09.370> reputation<00:49:09.580> system<00:49:10.270> works 00:49:11.090 --> 00:49:11.100 align:start position:0% way that the reputation system works 00:49:11.100 --> 00:49:15.990 align:start position:0% way that the reputation system works kind<00:49:12.100> of<00:49:13.050> prevents<00:49:14.050> that<00:49:14.410> because<00:49:15.190> repetition 00:49:15.990 --> 00:49:16.000 align:start position:0% kind of prevents that because repetition 00:49:16.000 --> 00:49:17.760 align:start position:0% kind of prevents that because repetition is<00:49:16.120> pretty<00:49:16.420> volatile<00:49:16.870> and 00:49:17.760 --> 00:49:17.770 align:start position:0% is pretty volatile and 00:49:17.770 --> 00:49:23.760 align:start position:0% is pretty volatile and change<00:49:18.070> has<00:49:18.400> really<00:49:18.760> really<00:49:19.450> fast<00:49:19.930> and<00:49:22.770> gives 00:49:23.760 --> 00:49:23.770 align:start position:0% change has really really fast and gives 00:49:23.770 --> 00:49:27.210 align:start position:0% change has really really fast and gives you<00:49:23.980> if<00:49:24.850> you<00:49:24.910> try<00:49:25.330> to<00:49:25.390> plan<00:49:25.840> such<00:49:26.560> a<00:49:26.590> thing<00:49:26.950> that 00:49:27.210 --> 00:49:27.220 align:start position:0% you if you try to plan such a thing that 00:49:27.220 --> 00:49:32.430 align:start position:0% you if you try to plan such a thing that the<00:49:28.210> point<00:49:28.450> is<00:49:28.600> that<00:49:28.780> you<00:49:29.560> cannot<00:49:30.990> decide<00:49:31.990> who 00:49:32.430 --> 00:49:32.440 align:start position:0% the point is that you cannot decide who 00:49:32.440 --> 00:49:34.620 align:start position:0% the point is that you cannot decide who to<00:49:32.560> punish<00:49:32.710> actually<00:49:33.610> because<00:49:33.850> there<00:49:34.090> because 00:49:34.620 --> 00:49:34.630 align:start position:0% to punish actually because there because 00:49:34.630 --> 00:49:36.900 align:start position:0% to punish actually because there because the<00:49:34.780> witnesses<00:49:35.290> are<00:49:35.470> randomly<00:49:36.220> selected<00:49:36.790> to 00:49:36.900 --> 00:49:36.910 align:start position:0% the witnesses are randomly selected to 00:49:36.910 --> 00:49:39.810 align:start position:0% the witnesses are randomly selected to do<00:49:37.030> so<00:49:37.210> okay<00:49:37.750> I<00:49:37.930> will<00:49:38.200> cause<00:49:38.470> some<00:49:39.160> notes<00:49:39.430> to<00:49:39.700> be 00:49:39.810 --> 00:49:39.820 align:start position:0% do so okay I will cause some notes to be 00:49:39.820 --> 00:49:41.670 align:start position:0% do so okay I will cause some notes to be managed<00:49:40.150> and<00:49:40.300> some<00:49:40.630> others<00:49:40.930> to<00:49:41.350> be<00:49:41.500> rewarded 00:49:41.670 --> 00:49:41.680 align:start position:0% managed and some others to be rewarded 00:49:41.680 --> 00:49:44.370 align:start position:0% managed and some others to be rewarded by<00:49:42.250> I<00:49:42.490> don't<00:49:42.670> know<00:49:42.790> who<00:49:43.300> they<00:49:43.450> are<00:49:43.480> so<00:49:43.900> this 00:49:44.370 --> 00:49:44.380 align:start position:0% by I don't know who they are so this 00:49:44.380 --> 00:49:47.850 align:start position:0% by I don't know who they are so this what<00:49:44.950> it's<00:49:45.160> actually<00:49:45.640> just<00:49:46.710> accelerated<00:49:47.710> in<00:49:47.800> a 00:49:47.850 --> 00:49:47.860 align:start position:0% what it's actually just accelerated in a 00:49:47.860 --> 00:49:50.240 align:start position:0% what it's actually just accelerated in a way<00:49:48.010> that<00:49:48.520> the<00:49:48.670> system<00:49:49.170> redistributes 00:49:50.240 --> 00:49:50.250 align:start position:0% way that the system redistributes 00:49:50.250 --> 00:49:53.370 align:start position:0% way that the system redistributes presentation.we<00:49:51.300> between<00:49:52.300> main<00:49:52.870> and<00:49:53.110> not 00:49:53.370 --> 00:49:53.380 align:start position:0% presentation.we between main and not 00:49:53.380 --> 00:49:55.830 align:start position:0% presentation.we between main and not because<00:49:53.980> and<00:49:54.310> at<00:49:55.060> the<00:49:55.180> end<00:49:55.330> of<00:49:55.390> the<00:49:55.450> day<00:49:55.570> their 00:49:55.830 --> 00:49:55.840 align:start position:0% because and at the end of the day their 00:49:55.840 --> 00:49:58.650 align:start position:0% because and at the end of the day their reputation<00:49:56.110> on<00:49:56.560> task<00:49:56.950> from<00:49:57.730> emigrate<00:49:58.300> which 00:49:58.650 --> 00:49:58.660 align:start position:0% reputation on task from emigrate which 00:49:58.660 --> 00:49:59.820 align:start position:0% reputation on task from emigrate which means<00:49:58.840> that<00:49:59.050> just<00:49:59.410> because<00:49:59.680> you<00:49:59.800> have 00:49:59.820 --> 00:49:59.830 align:start position:0% means that just because you have 00:49:59.830 --> 00:50:01.140 align:start position:0% means that just because you have repetition<00:50:00.220> you<00:50:00.700> lose<00:50:00.820> it 00:50:01.140 --> 00:50:01.150 align:start position:0% repetition you lose it 00:50:01.150 --> 00:50:03.690 align:start position:0% repetition you lose it so<00:50:01.450> basically<00:50:01.900> in<00:50:02.290> the<00:50:02.560> case<00:50:02.740> overtime<00:50:03.220> if<00:50:03.400> it 00:50:03.690 --> 00:50:03.700 align:start position:0% so basically in the case overtime if it 00:50:03.700 --> 00:50:06.060 align:start position:0% so basically in the case overtime if it expires<00:50:04.660> so<00:50:05.200> you<00:50:05.260> cannot<00:50:05.590> have<00:50:05.650> their 00:50:06.060 --> 00:50:06.070 align:start position:0% expires so you cannot have their 00:50:06.070 --> 00:50:08.160 align:start position:0% expires so you cannot have their purification<00:50:06.580> for<00:50:07.060> forever<00:50:07.480> and<00:50:07.900> it's<00:50:08.050> all 00:50:08.160 --> 00:50:08.170 align:start position:0% purification for forever and it's all 00:50:08.170 --> 00:50:10.470 align:start position:0% purification for forever and it's all the<00:50:08.260> changing<00:50:08.620> hands<00:50:08.860> so<00:50:09.310> if<00:50:09.670> you<00:50:09.820> do<00:50:09.970> that<00:50:10.150> you 00:50:10.470 --> 00:50:10.480 align:start position:0% the changing hands so if you do that you 00:50:10.480 --> 00:50:13.710 align:start position:0% the changing hands so if you do that you just<00:50:10.510> jack<00:50:10.930> you<00:50:11.440> are<00:50:11.620> just<00:50:12.030> accelerate<00:50:13.030> that 00:50:13.710 --> 00:50:13.720 align:start position:0% just jack you are just accelerate that 00:50:13.720 --> 00:50:19.460 align:start position:0% just jack you are just accelerate that process<00:50:14.790> so<00:50:15.790> it's<00:50:16.210> it's<00:50:16.570> good<00:50:16.960> for<00:50:17.200> the<00:50:17.290> system 00:50:19.460 --> 00:50:19.470 align:start position:0% 00:50:19.470 --> 00:50:22.940 align:start position:0% I<00:50:20.750> just<00:50:21.750> hope<00:50:21.960> you<00:50:22.110> didn't<00:50:22.320> on<00:50:22.410> this<00:50:22.560> time<00:50:22.740> and 00:50:22.940 --> 00:50:22.950 align:start position:0% I just hope you didn't on this time and 00:50:22.950 --> 00:50:25.160 align:start position:0% I just hope you didn't on this time and have<00:50:23.160> it<00:50:23.190> sitting<00:50:23.490> in<00:50:23.670> this<00:50:23.760> table<00:50:24.390> is<00:50:24.930> this 00:50:25.160 --> 00:50:25.170 align:start position:0% have it sitting in this table is this 00:50:25.170 --> 00:50:26.840 align:start position:0% have it sitting in this table is this something<00:50:25.470> about<00:50:25.920> if<00:50:26.340> I<00:50:26.430> read<00:50:26.580> the<00:50:26.700> white 00:50:26.840 --> 00:50:26.850 align:start position:0% something about if I read the white 00:50:26.850 --> 00:50:31.930 align:start position:0% something about if I read the white papers<00:50:27.300> that<00:50:27.420> sounds<00:50:28.290> pretty<00:50:28.380> interesting 00:50:31.930 --> 00:50:31.940 align:start position:0% 00:50:31.940 --> 00:50:38.650 align:start position:0% so<00:50:32.940> I<00:50:33.240> mean<00:50:36.230> in<00:50:37.230> those<00:50:37.710> in<00:50:38.040> these<00:50:38.130> two<00:50:38.340> years 00:50:38.650 --> 00:50:38.660 align:start position:0% so I mean in those in these two years 00:50:38.660 --> 00:50:43.310 align:start position:0% so I mean in those in these two years it's<00:50:39.660> 90<00:50:40.500> 20%<00:50:41.340> what<00:50:41.670> we<00:50:41.990> outlined<00:50:42.990> in<00:50:43.170> the 00:50:43.310 --> 00:50:43.320 align:start position:0% it's 90 20% what we outlined in the 00:50:43.320 --> 00:50:46.930 align:start position:0% it's 90 20% what we outlined in the white<00:50:43.590> paper<00:50:44.690> we<00:50:45.690> have<00:50:45.900> pioneered 00:50:46.930 --> 00:50:46.940 align:start position:0% white paper we have pioneered 00:50:46.940 --> 00:50:49.970 align:start position:0% white paper we have pioneered orientation<00:50:47.940> site<00:50:48.150> that<00:50:48.600> is<00:50:49.050> released<00:50:49.770> it 00:50:49.970 --> 00:50:49.980 align:start position:0% orientation site that is released it 00:50:49.980 --> 00:50:52.070 align:start position:0% orientation site that is released it down<00:50:50.220> into<00:50:50.640> the<00:50:50.820> basically<00:50:51.510> tending<00:50:51.960> to 00:50:52.070 --> 00:50:52.080 align:start position:0% down into the basically tending to 00:50:52.080 --> 00:50:54.890 align:start position:0% down into the basically tending to really<00:50:52.440> understand<00:50:52.890> what<00:50:53.280> we're<00:50:54.270> done<00:50:54.390> here 00:50:54.890 --> 00:50:54.900 align:start position:0% really understand what we're done here 00:50:54.900 --> 00:50:57.680 align:start position:0% really understand what we're done here so<00:50:55.710> I<00:50:55.740> think<00:50:55.950> that<00:50:56.280> will<00:50:56.520> be<00:50:56.550> quite<00:50:57.060> quiet 00:50:57.680 --> 00:50:57.690 align:start position:0% so I think that will be quite quiet 00:50:57.690 --> 00:51:00.440 align:start position:0% so I think that will be quite quiet because<00:50:57.990> they<00:50:58.290> the<00:50:59.070> white<00:50:59.760> paper<00:50:59.940> is<00:51:00.090> wet 00:51:00.440 --> 00:51:00.450 align:start position:0% because they the white paper is wet 00:51:00.450 --> 00:51:04.480 align:start position:0% because they the white paper is wet expensive<00:51:01.850> here<00:51:02.850> cousin<00:51:03.150> to<00:51:03.300> publish 00:51:04.480 --> 00:51:04.490 align:start position:0% expensive here cousin to publish 00:51:04.490 --> 00:51:08.990 align:start position:0% expensive here cousin to publish independent<00:51:05.660> research<00:51:06.660> but<00:51:06.930> and<00:51:08.000> technical 00:51:08.990 --> 00:51:09.000 align:start position:0% independent research but and technical 00:51:09.000 --> 00:51:12.320 align:start position:0% independent research but and technical content<00:51:09.240> on<00:51:09.420> our<00:51:09.780> video<00:51:10.440> a<00:51:10.560> lot<00:51:10.800> and<00:51:11.220> all<00:51:11.910> over 00:51:12.320 --> 00:51:12.330 align:start position:0% content on our video a lot and all over 00:51:12.330 --> 00:51:16.450 align:start position:0% content on our video a lot and all over a<00:51:12.540> specific<00:51:12.750> areas<00:51:13.530> like<00:51:13.880> repetitious<00:51:14.880> and 00:51:16.450 --> 00:51:16.460 align:start position:0% a specific areas like repetitious and 00:51:16.460 --> 00:51:29.420 align:start position:0% a specific areas like repetitious and many<00:51:17.460> different<00:51:17.670> parts<00:51:18.180> so<00:51:27.230> okay<00:51:28.400> thanks<00:51:29.400> for 00:51:29.420 --> 00:51:29.430 align:start position:0% many different parts so okay thanks for 00:51:29.430 --> 00:51:36.620 align:start position:0% many different parts so okay thanks for coming 00:51:36.620 --> 00:51:36.630 align:start position:0% 00:51:36.630 --> 00:51:41.079 align:start position:0% [Applause]