WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.990 align:start position:0% [Applause] 00:00:11.990 --> 00:00:12.000 align:start position:0% 00:00:12.000 --> 00:00:16.560 align:start position:0% now<00:00:13.000> see<00:00:13.240> some<00:00:13.480> to<00:00:13.629> doodle<00:00:13.929> says<00:00:14.199> good<00:00:14.469> boy<00:00:15.570> he 00:00:16.560 --> 00:00:16.570 align:start position:0% now see some to doodle says good boy he 00:00:16.570 --> 00:00:19.650 align:start position:0% now see some to doodle says good boy he wants<00:00:16.900> to<00:00:17.110> try<00:00:17.410> to<00:00:17.890> do<00:00:18.070> some<00:00:18.340> programming<00:00:19.180> work 00:00:19.650 --> 00:00:19.660 align:start position:0% wants to try to do some programming work 00:00:19.660 --> 00:00:22.710 align:start position:0% wants to try to do some programming work with<00:00:19.840> you<00:00:19.990> together<00:00:21.119> in<00:00:22.119> the<00:00:22.180> begin<00:00:22.419> to<00:00:22.570> my 00:00:22.710 --> 00:00:22.720 align:start position:0% with you together in the begin to my 00:00:22.720 --> 00:00:24.179 align:start position:0% with you together in the begin to my adversity<00:00:22.989> I'm<00:00:23.410> Jeff<00:00:23.710> Brooks<00:00:23.919> from 00:00:24.179 --> 00:00:24.189 align:start position:0% adversity I'm Jeff Brooks from 00:00:24.189 --> 00:00:28.259 align:start position:0% adversity I'm Jeff Brooks from sloppiness<00:00:25.259> science<00:00:26.259> Roget<00:00:26.679> and<00:00:27.429> today<00:00:27.789> we 00:00:28.259 --> 00:00:28.269 align:start position:0% sloppiness science Roget and today we 00:00:28.269 --> 00:00:30.390 align:start position:0% sloppiness science Roget and today we want<00:00:28.390> to<00:00:28.539> talk<00:00:28.839> with<00:00:29.080> you<00:00:29.289> about<00:00:29.439> into<00:00:30.160> our 00:00:30.390 --> 00:00:30.400 align:start position:0% want to talk with you about into our 00:00:30.400 --> 00:00:34.439 align:start position:0% want to talk with you about into our injured<00:00:30.759> protocol<00:00:31.359> and<00:00:31.830> steer<00:00:32.830> with<00:00:33.339> a<00:00:34.210> will 00:00:34.439 --> 00:00:34.449 align:start position:0% injured protocol and steer with a will 00:00:34.449 --> 00:00:36.930 align:start position:0% injured protocol and steer with a will perfect<00:00:34.900> a<00:00:34.989> to<00:00:35.050> try<00:00:35.320> to<00:00:35.379> shoot<00:00:35.829> which<00:00:36.610> is<00:00:36.790> the 00:00:36.930 --> 00:00:36.940 align:start position:0% perfect a to try to shoot which is the 00:00:36.940 --> 00:00:40.020 align:start position:0% perfect a to try to shoot which is the small<00:00:37.239> smallest<00:00:38.110> clients<00:00:38.769> for<00:00:39.400> determine 00:00:40.020 --> 00:00:40.030 align:start position:0% small smallest clients for determine 00:00:40.030 --> 00:00:41.850 align:start position:0% small smallest clients for determine other<00:00:40.210> projects<00:00:40.659> business<00:00:41.050> in<00:00:41.260> this<00:00:41.590> type 00:00:41.850 --> 00:00:41.860 align:start position:0% other projects business in this type 00:00:41.860 --> 00:00:45.119 align:start position:0% other projects business in this type available<00:00:42.129> and<00:00:43.030> today<00:00:43.480> I<00:00:43.780> will<00:00:44.710> give<00:00:44.860> you<00:00:45.100> a 00:00:45.119 --> 00:00:45.129 align:start position:0% available and today I will give you a 00:00:45.129 --> 00:00:47.729 align:start position:0% available and today I will give you a short<00:00:45.520> introduction<00:00:45.910> how<00:00:46.840> the<00:00:46.899> system<00:00:47.350> grows 00:00:47.729 --> 00:00:47.739 align:start position:0% short introduction how the system grows 00:00:47.739 --> 00:00:52.680 align:start position:0% short introduction how the system grows and<00:00:48.309> then<00:00:48.699> we<00:00:48.879> will<00:00:49.090> have<00:00:49.260> time<00:00:50.260> to<00:00:50.760> do<00:00:51.760> some<00:00:52.000> we 00:00:52.680 --> 00:00:52.690 align:start position:0% and then we will have time to do some we 00:00:52.690 --> 00:00:55.619 align:start position:0% and then we will have time to do some we are<00:00:52.719> programming<00:00:53.199> together<00:00:54.010> assignment<00:00:54.820> he 00:00:55.619 --> 00:00:55.629 align:start position:0% are programming together assignment he 00:00:55.629 --> 00:00:57.420 align:start position:0% are programming together assignment he will<00:00:55.780> show<00:00:55.989> something<00:00:56.320> then<00:00:56.769> you<00:00:57.039> can<00:00:57.070> also 00:00:57.420 --> 00:00:57.430 align:start position:0% will show something then you can also 00:00:57.430 --> 00:01:00.779 align:start position:0% will show something then you can also practice<00:00:57.760> it<00:00:58.329> on<00:00:58.719> your<00:00:59.320> own<00:00:59.500> do<00:00:59.769> to<00:00:59.920> learn<00:01:00.070> and 00:01:00.779 --> 00:01:00.789 align:start position:0% practice it on your own do to learn and 00:01:00.789 --> 00:01:04.950 align:start position:0% practice it on your own do to learn and try<00:01:01.539> out<00:01:01.719> assistant 00:01:04.950 --> 00:01:04.960 align:start position:0% 00:01:04.960 --> 00:01:08.250 align:start position:0% to<00:01:05.530> be<00:01:05.710> pretty<00:01:06.100> helpful<00:01:06.370> there<00:01:06.880> or<00:01:07.780> traveling 00:01:08.250 --> 00:01:08.260 align:start position:0% to be pretty helpful there or traveling 00:01:08.260 --> 00:01:11.910 align:start position:0% to be pretty helpful there or traveling if<00:01:08.410> you<00:01:08.440> want<00:01:08.800> to<00:01:09.270> participate<00:01:10.270> live<00:01:10.920> it's 00:01:11.910 --> 00:01:11.920 align:start position:0% if you want to participate live it's 00:01:11.920 --> 00:01:16.890 align:start position:0% if you want to participate live it's good<00:01:12.190> to<00:01:12.430> have<00:01:13.170> some<00:01:14.170> software<00:01:14.770> available<00:01:15.900> the 00:01:16.890 --> 00:01:16.900 align:start position:0% good to have some software available the 00:01:16.900 --> 00:01:18.870 align:start position:0% good to have some software available the easy<00:01:17.080> thing<00:01:17.470> would<00:01:17.500> be<00:01:17.890> to<00:01:18.490> use<00:01:18.520> a<00:01:18.670> double 00:01:18.870 --> 00:01:18.880 align:start position:0% easy thing would be to use a double 00:01:18.880 --> 00:01:22.219 align:start position:0% easy thing would be to use a double match<00:01:19.210> you<00:01:20.170> know<00:01:20.350> the<00:01:20.860> internet<00:01:21.220> is<00:01:21.250> not<00:01:21.370> stats 00:01:22.219 --> 00:01:22.229 align:start position:0% match you know the internet is not stats 00:01:22.229 --> 00:01:27.750 align:start position:0% match you know the internet is not stats create<00:01:23.229> here<00:01:23.500> so<00:01:24.280> I<00:01:24.310> have<00:01:24.610> some<00:01:24.850> sticks<00:01:26.640> so<00:01:27.640> if 00:01:27.750 --> 00:01:27.760 align:start position:0% create here so I have some sticks so if 00:01:27.760 --> 00:01:30.990 align:start position:0% create here so I have some sticks so if you<00:01:27.880> want<00:01:28.119> to<00:01:28.800> install<00:01:29.800> a<00:01:29.950> double<00:01:30.310> each<00:01:30.460> time<00:01:30.850> a 00:01:30.990 --> 00:01:31.000 align:start position:0% you want to install a double each time a 00:01:31.000 --> 00:01:34.140 align:start position:0% you want to install a double each time a computer<00:01:31.720> you<00:01:31.869> can<00:01:32.110> just<00:01:32.500> take<00:01:33.160> one<00:01:33.850> of<00:01:34.000> these 00:01:34.140 --> 00:01:34.150 align:start position:0% computer you can just take one of these 00:01:34.150 --> 00:01:35.240 align:start position:0% computer you can just take one of these sticks 00:01:35.240 --> 00:01:35.250 align:start position:0% sticks 00:01:35.250 --> 00:01:38.100 align:start position:0% sticks there's<00:01:36.250> the<00:01:36.520> cooking<00:01:37.240> image<00:01:37.479> or<00:01:37.720> you<00:01:37.869> can 00:01:38.100 --> 00:01:38.110 align:start position:0% there's the cooking image or you can 00:01:38.110 --> 00:01:44.960 align:start position:0% there's the cooking image or you can download<00:01:38.979> it<00:01:39.520> directly<00:01:41.940> okay 00:01:44.960 --> 00:01:44.970 align:start position:0% 00:01:44.970 --> 00:01:54.340 align:start position:0% [Music] 00:01:54.340 --> 00:01:54.350 align:start position:0% 00:01:54.350 --> 00:01:56.950 align:start position:0% but<00:01:54.890> what<00:01:55.130> we<00:01:55.280> are<00:01:55.310> doing<00:01:55.580> today<00:01:55.760> so<00:01:56.420> in<00:01:56.810> the 00:01:56.950 --> 00:01:56.960 align:start position:0% but what we are doing today so in the 00:01:56.960 --> 00:01:59.800 align:start position:0% but what we are doing today so in the first<00:01:57.110> I<00:01:57.440> want<00:01:57.620> to<00:01:57.650> talk<00:01:57.920> about<00:01:58.510> what<00:01:59.510> it<00:01:59.630> is 00:01:59.800 --> 00:01:59.810 align:start position:0% first I want to talk about what it is 00:01:59.810 --> 00:02:02.170 align:start position:0% first I want to talk about what it is how<00:02:00.050> it<00:02:00.080> works<00:02:00.500> what<00:02:00.920> are<00:02:01.070> the<00:02:01.130> benefits<00:02:01.340> are 00:02:02.170 --> 00:02:02.180 align:start position:0% how it works what are the benefits are 00:02:02.180 --> 00:02:05.260 align:start position:0% how it works what are the benefits are the<00:02:02.360> boundaries<00:02:02.900> and<00:02:03.440> then<00:02:04.070> we<00:02:04.670> reduce<00:02:05.060> on 00:02:05.260 --> 00:02:05.270 align:start position:0% the boundaries and then we reduce on 00:02:05.270 --> 00:02:08.830 align:start position:0% the boundaries and then we reduce on from<00:02:05.479> training<00:02:06.520> different<00:02:07.520> platforms<00:02:08.330> power 00:02:08.830 --> 00:02:08.840 align:start position:0% from training different platforms power 00:02:08.840 --> 00:02:11.890 align:start position:0% from training different platforms power to<00:02:09.200> integrate<00:02:09.890> into<00:02:10.310> the<00:02:10.369> client<00:02:10.729> and<00:02:10.910> our 00:02:11.890 --> 00:02:11.900 align:start position:0% to integrate into the client and our 00:02:11.900 --> 00:02:16.240 align:start position:0% to integrate into the client and our second<00:02:13.390> topic<00:02:14.390> we<00:02:14.930> will<00:02:15.110> go<00:02:15.440> a<00:02:15.470> bit<00:02:15.860> more<00:02:15.890> in 00:02:16.240 --> 00:02:16.250 align:start position:0% second topic we will go a bit more in 00:02:16.250 --> 00:02:20.730 align:start position:0% second topic we will go a bit more in detail<00:02:16.459> how<00:02:17.270> to<00:02:17.300> push<00:02:17.750> we<00:02:18.020> are<00:02:18.140> using<00:02:18.380> to 00:02:20.730 --> 00:02:20.740 align:start position:0% 00:02:20.740 --> 00:02:24.160 align:start position:0% understand<00:02:21.740> of<00:02:22.250> the<00:02:22.370> sake<00:02:22.640> and<00:02:23.170> programming 00:02:24.160 --> 00:02:24.170 align:start position:0% understand of the sake and programming 00:02:24.170 --> 00:02:27.430 align:start position:0% understand of the sake and programming work<00:02:24.790> how<00:02:25.790> we<00:02:25.850> can<00:02:26.060> how<00:02:26.600> these<00:02:26.840> proofs<00:02:27.290> are 00:02:27.430 --> 00:02:27.440 align:start position:0% work how we can how these proofs are 00:02:27.440 --> 00:02:31.030 align:start position:0% work how we can how these proofs are cooking<00:02:28.160> how<00:02:28.400> they<00:02:28.640> can<00:02:28.880> do<00:02:29.000> it<00:02:29.090> myself<00:02:29.720> and<00:02:30.080> in 00:02:31.030 --> 00:02:31.040 align:start position:0% cooking how they can do it myself and in 00:02:31.040 --> 00:02:34.600 align:start position:0% cooking how they can do it myself and in the<00:02:31.070> end<00:02:31.190> we<00:02:31.700> will<00:02:32.270> show<00:02:32.510> how<00:02:32.989> to<00:02:33.020> install<00:02:33.860> into 00:02:34.600 --> 00:02:34.610 align:start position:0% the end we will show how to install into 00:02:34.610 --> 00:02:38.860 align:start position:0% the end we will show how to install into the<00:02:34.820> nodes<00:02:35.209> that<00:02:35.750> means<00:02:36.050> node<00:02:36.440> which<00:02:37.870> connects 00:02:38.860 --> 00:02:38.870 align:start position:0% the nodes that means node which connects 00:02:38.870 --> 00:02:43.960 align:start position:0% the nodes that means node which connects to<00:02:39.130> which<00:02:40.130> provides<00:02:40.550> services<00:02:40.850> for<00:02:41.120> them<00:02:42.970> okay 00:02:43.960 --> 00:02:43.970 align:start position:0% to which provides services for them okay 00:02:43.970 --> 00:02:46.870 align:start position:0% to which provides services for them okay first<00:02:44.300> I<00:02:44.720> will<00:02:45.290> I<00:02:45.560> want<00:02:45.920> to<00:02:46.100> introduce<00:02:46.430> your 00:02:46.870 --> 00:02:46.880 align:start position:0% first I will I want to introduce your 00:02:46.880 --> 00:02:50.370 align:start position:0% first I will I want to introduce your how<00:02:47.480> does<00:02:48.230> it<00:02:48.560> work 00:02:50.370 --> 00:02:50.380 align:start position:0% how does it work 00:02:50.380 --> 00:02:55.010 align:start position:0% how does it work so<00:02:51.380> this<00:02:51.620> when<00:02:52.340> you<00:02:52.519> see<00:02:52.700> this<00:02:52.880> is<00:02:53.360> the<00:02:53.780> vision 00:02:55.010 --> 00:02:55.020 align:start position:0% so this when you see this is the vision 00:02:55.020 --> 00:02:58.580 align:start position:0% so this when you see this is the vision everyone<00:02:55.740> heads<00:02:55.980> in<00:02:56.580> the<00:02:56.730> beginning<00:02:57.590> teacher 00:02:58.580 --> 00:02:58.590 align:start position:0% everyone heads in the beginning teacher 00:02:58.590 --> 00:03:01.340 align:start position:0% everyone heads in the beginning teacher water<00:02:59.010> fortunes<00:02:59.640> were<00:02:59.940> constructed<00:03:00.600> we<00:03:01.170> have 00:03:01.340 --> 00:03:01.350 align:start position:0% water fortunes were constructed we have 00:03:01.350 --> 00:03:04.550 align:start position:0% water fortunes were constructed we have a<00:03:01.650> decent<00:03:02.040> decent<00:03:02.670> price<00:03:03.030> network<00:03:03.450> with<00:03:04.230> nodes 00:03:04.550 --> 00:03:04.560 align:start position:0% a decent decent price network with nodes 00:03:04.560 --> 00:03:08.450 align:start position:0% a decent decent price network with nodes which<00:03:05.070> are<00:03:05.310> connected<00:03:06.230> directly<00:03:07.230> in<00:03:07.920> their 00:03:08.450 --> 00:03:08.460 align:start position:0% which are connected directly in their 00:03:08.460 --> 00:03:10.400 align:start position:0% which are connected directly in their apps<00:03:08.880> which<00:03:09.240> interact<00:03:09.660> with<00:03:09.900> these<00:03:10.050> clients 00:03:10.400 --> 00:03:10.410 align:start position:0% apps which interact with these clients 00:03:10.410 --> 00:03:14.120 align:start position:0% apps which interact with these clients and<00:03:11.780> accessed<00:03:12.780> information<00:03:12.990> of<00:03:13.860> the<00:03:13.980> table 00:03:14.120 --> 00:03:14.130 align:start position:0% and accessed information of the table 00:03:14.130 --> 00:03:16.630 align:start position:0% and accessed information of the table Jenny<00:03:14.430> who<00:03:15.360> thinks<00:03:15.750> that<00:03:15.960> this<00:03:16.140> is<00:03:16.200> the 00:03:16.630 --> 00:03:16.640 align:start position:0% Jenny who thinks that this is the 00:03:16.640 --> 00:03:19.460 align:start position:0% Jenny who thinks that this is the configuration<00:03:17.640> which<00:03:18.180> is<00:03:18.210> growing<00:03:19.020> at<00:03:19.350> the 00:03:19.460 --> 00:03:19.470 align:start position:0% configuration which is growing at the 00:03:19.470 --> 00:03:25.250 align:start position:0% configuration which is growing at the moment<00:03:22.700> in<00:03:23.700> the<00:03:23.850> moment<00:03:23.970> it<00:03:24.510> looks<00:03:24.660> mostly 00:03:25.250 --> 00:03:25.260 align:start position:0% moment in the moment it looks mostly 00:03:25.260 --> 00:03:30.000 align:start position:0% moment in the moment it looks mostly like<00:03:25.350> this 00:03:30.000 --> 00:03:30.010 align:start position:0% 00:03:30.010 --> 00:03:32.580 align:start position:0% we<00:03:30.520> have<00:03:30.670> this<00:03:30.819> nice<00:03:31.150> decent<00:03:31.540> Westnet<00:03:32.050> program 00:03:32.580 --> 00:03:32.590 align:start position:0% we have this nice decent Westnet program 00:03:32.590 --> 00:03:36.660 align:start position:0% we have this nice decent Westnet program but<00:03:33.520> most<00:03:33.940> of<00:03:34.239> the<00:03:34.480> depths<00:03:35.379> by<00:03:35.950> accessing<00:03:36.430> the 00:03:36.660 --> 00:03:36.670 align:start position:0% but most of the depths by accessing the 00:03:36.670 --> 00:03:40.259 align:start position:0% but most of the depths by accessing the information<00:03:37.000> of<00:03:37.690> the<00:03:37.840> Trojan<00:03:38.260> War<00:03:38.290> II<00:03:39.190> sent<00:03:40.030> by 00:03:40.259 --> 00:03:40.269 align:start position:0% information of the Trojan War II sent by 00:03:40.269 --> 00:03:43.170 align:start position:0% information of the Trojan War II sent by suppose<00:03:41.370> these<00:03:42.370> sentences<00:03:42.970> are<00:03:43.150> very 00:03:43.170 --> 00:03:43.180 align:start position:0% suppose these sentences are very 00:03:43.180 --> 00:03:47.759 align:start position:0% suppose these sentences are very important<00:03:43.959> for<00:03:44.890> the<00:03:45.040> time<00:03:45.550> now<00:03:46.300> to<00:03:46.810> put<00:03:47.440> these 00:03:47.759 --> 00:03:47.769 align:start position:0% important for the time now to put these 00:03:47.769 --> 00:03:50.610 align:start position:0% important for the time now to put these apps<00:03:48.040> but<00:03:48.640> when<00:03:48.790> you<00:03:48.910> think<00:03:49.150> to<00:03:49.569> the<00:03:49.630> future<00:03:50.050> we 00:03:50.610 --> 00:03:50.620 align:start position:0% apps but when you think to the future we 00:03:50.620 --> 00:03:52.589 align:start position:0% apps but when you think to the future we need<00:03:50.650> decentralized<00:03:51.640> way<00:03:51.790> to<00:03:51.970> access<00:03:52.450> the 00:03:52.589 --> 00:03:52.599 align:start position:0% need decentralized way to access the 00:03:52.599 --> 00:03:57.030 align:start position:0% need decentralized way to access the division<00:03:52.989> for<00:03:53.080> option<00:03:55.470> so<00:03:56.470> when<00:03:56.650> we<00:03:56.769> talk 00:03:57.030 --> 00:03:57.040 align:start position:0% division for option so when we talk 00:03:57.040 --> 00:04:02.070 align:start position:0% division for option so when we talk about<00:03:57.069> clients<00:03:59.400> then<00:04:00.400> if<00:04:00.849> different<00:04:01.599> types<00:04:01.870> of 00:04:02.070 --> 00:04:02.080 align:start position:0% about clients then if different types of 00:04:02.080 --> 00:04:04.830 align:start position:0% about clients then if different types of time<00:04:02.290> so<00:04:02.440> dinners<00:04:02.680> for<00:04:02.920> example<00:04:03.430> the<00:04:03.910> term<00:04:04.120> for 00:04:04.830 --> 00:04:04.840 align:start position:0% time so dinners for example the term for 00:04:04.840 --> 00:04:07.170 align:start position:0% time so dinners for example the term for other<00:04:04.989> opportunities<00:04:05.349> almost<00:04:06.250> the<00:04:06.370> same<00:04:06.549> we 00:04:07.170 --> 00:04:07.180 align:start position:0% other opportunities almost the same we 00:04:07.180 --> 00:04:09.030 align:start position:0% other opportunities almost the same we have<00:04:07.299> these<00:04:07.450> full<00:04:07.870> notes<00:04:08.110> or<00:04:08.319> even<00:04:08.470> archive 00:04:09.030 --> 00:04:09.040 align:start position:0% have these full notes or even archive 00:04:09.040 --> 00:04:11.789 align:start position:0% have these full notes or even archive notes<00:04:09.310> which<00:04:10.180> are<00:04:10.329> very<00:04:10.660> big<00:04:10.930> in<00:04:11.260> a<00:04:11.620> lot<00:04:11.769> of 00:04:11.789 --> 00:04:11.799 align:start position:0% notes which are very big in a lot of 00:04:11.799 --> 00:04:15.539 align:start position:0% notes which are very big in a lot of resources<00:04:12.370> and<00:04:13.470> then<00:04:14.470> even<00:04:14.980> if<00:04:15.250> we<00:04:15.400> have<00:04:15.519> a 00:04:15.539 --> 00:04:15.549 align:start position:0% resources and then even if we have a 00:04:15.549 --> 00:04:19.080 align:start position:0% resources and then even if we have a food<00:04:15.989> per<00:04:16.989> note<00:04:17.200> its<00:04:17.560> way<00:04:18.160> to<00:04:18.220> pick<00:04:18.519> to<00:04:18.729> run<00:04:18.940> it 00:04:19.080 --> 00:04:19.090 align:start position:0% food per note its way to pick to run it 00:04:19.090 --> 00:04:22.290 align:start position:0% food per note its way to pick to run it in<00:04:19.630> a<00:04:19.750> browser<00:04:19.780> or<00:04:20.470> on<00:04:20.500> an<00:04:20.859> int<00:04:21.310> device<00:04:21.579> and 00:04:22.290 --> 00:04:22.300 align:start position:0% in a browser or on an int device and 00:04:22.300 --> 00:04:24.900 align:start position:0% in a browser or on an int device and even<00:04:22.600> though<00:04:22.750> times<00:04:23.200> are<00:04:23.470> way<00:04:24.040> too<00:04:24.100> big<00:04:24.490> to<00:04:24.520> run 00:04:24.900 --> 00:04:24.910 align:start position:0% even though times are way too big to run 00:04:24.910 --> 00:04:27.690 align:start position:0% even though times are way too big to run but<00:04:25.810> I<00:04:25.900> achieve<00:04:26.229> the<00:04:26.350> rifle<00:04:26.740> sense<00:04:27.100> so<00:04:27.580> the 00:04:27.690 --> 00:04:27.700 align:start position:0% but I achieve the rifle sense so the 00:04:27.700 --> 00:04:29.580 align:start position:0% but I achieve the rifle sense so the minimum<00:04:27.970> configuration<00:04:28.419> for<00:04:29.020> a<00:04:29.050> right<00:04:29.290> time 00:04:29.580 --> 00:04:29.590 align:start position:0% minimum configuration for a right time 00:04:29.590 --> 00:04:31.710 align:start position:0% minimum configuration for a right time is<00:04:30.130> a<00:04:30.190> computer<00:04:30.790> in<00:04:31.030> the<00:04:31.120> size<00:04:31.360> of<00:04:31.510> Grass 00:04:31.710 --> 00:04:31.720 align:start position:0% is a computer in the size of Grass 00:04:31.720 --> 00:04:34.770 align:start position:0% is a computer in the size of Grass Valley<00:04:31.750> but<00:04:32.620> most<00:04:32.919> of<00:04:33.070> IT<00:04:33.490> devices<00:04:33.940> are<00:04:34.150> way 00:04:34.770 --> 00:04:34.780 align:start position:0% Valley but most of IT devices are way 00:04:34.780 --> 00:04:38.680 align:start position:0% Valley but most of IT devices are way smaller 00:04:38.680 --> 00:04:38.690 align:start position:0% 00:04:38.690 --> 00:04:41.810 align:start position:0% so<00:04:39.690> when<00:04:39.840> we<00:04:39.990> designed<00:04:40.830> the<00:04:40.980> system<00:04:41.010> we<00:04:41.670> had 00:04:41.810 --> 00:04:41.820 align:start position:0% so when we designed the system we had 00:04:41.820 --> 00:04:45.740 align:start position:0% so when we designed the system we had something<00:04:42.510> like<00:04:42.780> this<00:04:44.180> you<00:04:45.180> cannot<00:04:45.390> see<00:04:45.630> it 00:04:45.740 --> 00:04:45.750 align:start position:0% something like this you cannot see it 00:04:45.750 --> 00:04:47.780 align:start position:0% something like this you cannot see it much<00:04:45.930> because<00:04:46.470> this<00:04:47.040> is<00:04:47.190> a<00:04:47.250> small<00:04:47.520> microphone 00:04:47.780 --> 00:04:47.790 align:start position:0% much because this is a small microphone 00:04:47.790 --> 00:04:50.960 align:start position:0% much because this is a small microphone this<00:04:48.660> is<00:04:48.720> my<00:04:48.960> total<00:04:49.170> which<00:04:49.710> is<00:04:49.950> written<00:04:50.610> in<00:04:50.910> the 00:04:50.960 --> 00:04:50.970 align:start position:0% this is my total which is written in the 00:04:50.970 --> 00:04:55.010 align:start position:0% this is my total which is written in the dual<00:04:52.400> devices<00:04:53.400> and<00:04:53.550> of<00:04:54.420> course<00:04:54.720> such 00:04:55.010 --> 00:04:55.020 align:start position:0% dual devices and of course such 00:04:55.020 --> 00:04:58.010 align:start position:0% dual devices and of course such magnitude<00:04:55.860> is<00:04:56.100> not<00:04:56.220> able<00:04:56.520> to<00:04:56.850> run<00:04:57.360> and<00:04:57.690> I<00:04:57.750> tried 00:04:58.010 --> 00:04:58.020 align:start position:0% magnitude is not able to run and I tried 00:04:58.020 --> 00:05:01.430 align:start position:0% magnitude is not able to run and I tried that<00:04:58.140> and<00:04:58.770> what<00:04:59.190> are<00:04:59.400> doing<00:04:59.910> the<00:05:00.150> most<00:05:00.440> tell 00:05:01.430 --> 00:05:01.440 align:start position:0% that and what are doing the most tell 00:05:01.440 --> 00:05:03.920 align:start position:0% that and what are doing the most tell you<00:05:02.160> something<00:05:02.490> more<00:05:02.640> clients<00:05:03.000> meaning<00:05:03.210> they 00:05:03.920 --> 00:05:03.930 align:start position:0% you something more clients meaning they 00:05:03.930 --> 00:05:06.020 align:start position:0% you something more clients meaning they have<00:05:04.050> asked<00:05:04.740> the<00:05:04.980> roads<00:05:05.520> money<00:05:05.790> in<00:05:05.940> the 00:05:06.020 --> 00:05:06.030 align:start position:0% have asked the roads money in the 00:05:06.030 --> 00:05:07.670 align:start position:0% have asked the roads money in the internet<00:05:06.390> and<00:05:06.630> they<00:05:07.080> have<00:05:07.170> a<00:05:07.230> remote<00:05:07.500> of 00:05:07.670 --> 00:05:07.680 align:start position:0% internet and they have a remote of 00:05:07.680 --> 00:05:10.670 align:start position:0% internet and they have a remote of expertise<00:05:08.250> but<00:05:08.760> with<00:05:09.330> this<00:05:09.630> approach<00:05:10.080> the 00:05:10.670 --> 00:05:10.680 align:start position:0% expertise but with this approach the 00:05:10.680 --> 00:05:13.520 align:start position:0% expertise but with this approach the owners<00:05:11.300> disinterested<00:05:12.300> want<00:05:12.750> to<00:05:12.870> be<00:05:12.990> rely 00:05:13.520 --> 00:05:13.530 align:start position:0% owners disinterested want to be rely 00:05:13.530 --> 00:05:16.190 align:start position:0% owners disinterested want to be rely upon<00:05:13.710> said<00:05:14.370> last<00:05:14.610> note<00:05:14.910> and<00:05:15.210> we<00:05:15.780> are<00:05:15.870> seeing<00:05:16.110> a 00:05:16.190 --> 00:05:16.200 align:start position:0% upon said last note and we are seeing a 00:05:16.200 --> 00:05:18.500 align:start position:0% upon said last note and we are seeing a point<00:05:16.410> of<00:05:16.530> failure<00:05:16.710> you<00:05:17.190> don't<00:05:17.280> know<00:05:17.760> if<00:05:18.180> he 00:05:18.500 --> 00:05:18.510 align:start position:0% point of failure you don't know if he 00:05:18.510 --> 00:05:21.040 align:start position:0% point of failure you don't know if he asked<00:05:18.660> maybe<00:05:18.960> attack 00:05:21.040 --> 00:05:21.050 align:start position:0% asked maybe attack 00:05:21.050 --> 00:05:27.100 align:start position:0% asked maybe attack so<00:05:21.590> our<00:05:22.539> solution<00:05:23.539> our<00:05:23.629> approach<00:05:25.870> is<00:05:26.870> the 00:05:27.100 --> 00:05:27.110 align:start position:0% so our solution our approach is the 00:05:27.110 --> 00:05:32.260 align:start position:0% so our solution our approach is the imputed<00:05:27.620> client<00:05:28.840> richness<00:05:29.840> so<00:05:30.879> he<00:05:31.879> wants<00:05:32.210> to 00:05:32.260 --> 00:05:32.270 align:start position:0% imputed client richness so he wants to 00:05:32.270 --> 00:05:36.610 align:start position:0% imputed client richness so he wants to have<00:05:32.389> the<00:05:33.460> abilities<00:05:34.460> by<00:05:34.909> plant<00:05:35.330> the<00:05:35.870> security 00:05:36.610 --> 00:05:36.620 align:start position:0% have the abilities by plant the security 00:05:36.620 --> 00:05:39.969 align:start position:0% have the abilities by plant the security by<00:05:36.889> plant<00:05:37.280> but<00:05:38.210> this<00:05:38.539> one's<00:05:38.960> the<00:05:39.259> easiness<00:05:39.590> of 00:05:39.969 --> 00:05:39.979 align:start position:0% by plant but this one's the easiness of 00:05:39.979 --> 00:05:41.439 align:start position:0% by plant but this one's the easiness of remote<00:05:40.759> management 00:05:41.439 --> 00:05:41.449 align:start position:0% remote management 00:05:41.449 --> 00:05:48.250 align:start position:0% remote management I<00:05:41.629> will<00:05:42.169> now<00:05:42.409> explain<00:05:42.949> how<00:05:43.030> this<00:05:44.030> system<00:05:44.240> works 00:05:48.250 --> 00:05:48.260 align:start position:0% 00:05:48.260 --> 00:05:52.250 align:start position:0% before<00:05:49.260> I<00:05:49.290> thought<00:05:49.500> this<00:05:49.770> now<00:05:50.340> impute<00:05:51.300> we<00:05:51.900> are 00:05:52.250 --> 00:05:52.260 align:start position:0% before I thought this now impute we are 00:05:52.260 --> 00:05:54.200 align:start position:0% before I thought this now impute we are able<00:05:52.560> to<00:05:52.740> hear<00:05:53.040> the<00:05:53.160> complete<00:05:53.550> decentralized 00:05:54.200 --> 00:05:54.210 align:start position:0% able to hear the complete decentralized 00:05:54.210 --> 00:05:57.080 align:start position:0% able to hear the complete decentralized system<00:05:54.600> it<00:05:55.139> means<00:05:55.410> we<00:05:55.830> have<00:05:55.860> deaf<00:05:56.250> speech<00:05:56.610> run 00:05:57.080 --> 00:05:57.090 align:start position:0% system it means we have deaf speech run 00:05:57.090 --> 00:05:59.690 align:start position:0% system it means we have deaf speech run such<00:05:57.480> a<00:05:57.720> tribute<00:05:57.900> time<00:05:58.320> and<00:05:58.680> these<00:05:59.190> clients 00:05:59.690 --> 00:05:59.700 align:start position:0% such a tribute time and these clients 00:05:59.700 --> 00:06:02.540 align:start position:0% such a tribute time and these clients are<00:05:59.820> connecting<00:06:00.540> through<00:06:01.550> decentralized 00:06:02.540 --> 00:06:02.550 align:start position:0% are connecting through decentralized 00:06:02.550 --> 00:06:06.050 align:start position:0% are connecting through decentralized network<00:06:03.180> of<00:06:03.690> such<00:06:04.500> even<00:06:04.919> thoughts<00:06:05.280> which<00:06:05.820> are 00:06:06.050 --> 00:06:06.060 align:start position:0% network of such even thoughts which are 00:06:06.060 --> 00:06:08.840 align:start position:0% network of such even thoughts which are awesome<00:06:07.050> goods<00:06:07.320> of<00:06:07.530> the<00:06:07.710> decent<00:06:08.070> life<00:06:08.430> circle 00:06:08.840 --> 00:06:08.850 align:start position:0% awesome goods of the decent life circle 00:06:08.850 --> 00:06:13.909 align:start position:0% awesome goods of the decent life circle of<00:06:08.970> the<00:06:09.150> blockchain<00:06:11.690> so<00:06:12.690> I<00:06:12.720> want<00:06:13.230> I<00:06:13.380> will<00:06:13.650> use 00:06:13.909 --> 00:06:13.919 align:start position:0% of the blockchain so I want I will use 00:06:13.919 --> 00:06:16.700 align:start position:0% of the blockchain so I want I will use the<00:06:14.310> term<00:06:14.610> minimum<00:06:15.600> magnification<00:06:16.050> kind 00:06:16.700 --> 00:06:16.710 align:start position:0% the term minimum magnification kind 00:06:16.710 --> 00:06:20.360 align:start position:0% the term minimum magnification kind several<00:06:17.639> times<00:06:17.910> decide<00:06:18.389> I<00:06:18.600> want<00:06:19.200> to<00:06:19.320> give<00:06:20.250> you 00:06:20.360 --> 00:06:20.370 align:start position:0% several times decide I want to give you 00:06:20.370 --> 00:06:23.090 align:start position:0% several times decide I want to give you a<00:06:20.400> short<00:06:20.790> definition<00:06:21.090> what<00:06:22.020> we<00:06:22.290> mean<00:06:22.560> with<00:06:22.889> I 00:06:23.090 --> 00:06:23.100 align:start position:0% a short definition what we mean with I 00:06:23.100 --> 00:06:28.490 align:start position:0% a short definition what we mean with I said<00:06:24.710> so<00:06:25.710> this<00:06:25.889> is<00:06:26.010> the<00:06:26.130> client<00:06:26.960> which<00:06:27.960> is<00:06:27.990> able 00:06:28.490 --> 00:06:28.500 align:start position:0% said so this is the client which is able 00:06:28.500 --> 00:06:31.310 align:start position:0% said so this is the client which is able to<00:06:28.650> and<00:06:28.770> gratified<00:06:29.960> information<00:06:30.960> it<00:06:31.080> receives 00:06:31.310 --> 00:06:31.320 align:start position:0% to and gratified information it receives 00:06:31.320 --> 00:06:34.760 align:start position:0% to and gratified information it receives and<00:06:32.010> to<00:06:32.910> validate<00:06:33.180> that<00:06:33.810> this<00:06:34.080> vision<00:06:34.440> video 00:06:34.760 --> 00:06:34.770 align:start position:0% and to validate that this vision video 00:06:34.770 --> 00:06:38.090 align:start position:0% and to validate that this vision video belong<00:06:35.160> to<00:06:35.370> project<00:06:35.850> and<00:06:36.600> then<00:06:36.720> it's<00:06:37.169> very 00:06:38.090 --> 00:06:38.100 align:start position:0% belong to project and then it's very 00:06:38.100 --> 00:06:40.250 align:start position:0% belong to project and then it's very small<00:06:38.430> client<00:06:38.790> means<00:06:39.450> only<00:06:39.720> a<00:06:39.870> small<00:06:40.229> amount 00:06:40.250 --> 00:06:40.260 align:start position:0% small client means only a small amount 00:06:40.260 --> 00:06:44.050 align:start position:0% small client means only a small amount of<00:06:40.620> sources<00:06:41.220> as<00:06:41.940> only<00:06:42.360> obviously<00:06:42.780> publication 00:06:44.050 --> 00:06:44.060 align:start position:0% of sources as only obviously publication 00:06:44.060 --> 00:06:47.240 align:start position:0% of sources as only obviously publication ends<00:06:45.060> which<00:06:45.540> is<00:06:45.660> all<00:06:45.840> the<00:06:46.020> interesting<00:06:46.770> part 00:06:47.240 --> 00:06:47.250 align:start position:0% ends which is all the interesting part 00:06:47.250 --> 00:06:49.850 align:start position:0% ends which is all the interesting part of<00:06:47.400> the<00:06:47.580> concern<00:06:48.000> it<00:06:48.540> does<00:06:48.930> not<00:06:49.080> depend<00:06:49.260> on<00:06:49.770> a 00:06:49.850 --> 00:06:49.860 align:start position:0% of the concern it does not depend on a 00:06:49.860 --> 00:06:52.159 align:start position:0% of the concern it does not depend on a special<00:06:50.250> project<00:06:50.430> of<00:06:51.240> course<00:06:51.540> we<00:06:51.720> did<00:06:51.870> is<00:06:51.990> for 00:06:52.159 --> 00:06:52.169 align:start position:0% special project of course we did is for 00:06:52.169 --> 00:06:53.750 align:start position:0% special project of course we did is for children<00:06:52.650> because<00:06:52.800> we<00:06:53.070> are<00:06:53.190> coming<00:06:53.400> from<00:06:53.669> the 00:06:53.750 --> 00:06:53.760 align:start position:0% children because we are coming from the 00:06:53.760 --> 00:06:58.830 align:start position:0% children because we are coming from the third<00:06:54.060> world<00:06:54.300> but<00:06:55.050> it<00:06:55.229> can<00:06:55.530> grow<00:06:55.770> the<00:06:55.979> same 00:06:58.830 --> 00:06:58.840 align:start position:0% 00:06:58.840 --> 00:07:00.420 align:start position:0% and<00:06:59.260> the<00:06:59.350> very<00:06:59.500> important<00:06:59.949> thing<00:07:00.070> is<00:07:00.190> that 00:07:00.420 --> 00:07:00.430 align:start position:0% and the very important thing is that 00:07:00.430 --> 00:07:03.270 align:start position:0% and the very important thing is that this<00:07:01.120> client<00:07:01.479> is<00:07:01.600> a<00:07:01.630> stateless<00:07:02.080> client<00:07:02.830> that 00:07:03.270 --> 00:07:03.280 align:start position:0% this client is a stateless client that 00:07:03.280 --> 00:07:06.960 align:start position:0% this client is a stateless client that means<00:07:03.720> to<00:07:04.720> no<00:07:04.900> time<00:07:05.290> it<00:07:05.590> needs<00:07:05.949> to<00:07:06.280> synchronize 00:07:06.960 --> 00:07:06.970 align:start position:0% means to no time it needs to synchronize 00:07:06.970 --> 00:07:10.620 align:start position:0% means to no time it needs to synchronize with<00:07:07.300> the<00:07:07.660> information<00:07:08.380> of<00:07:08.410> the<00:07:08.530> object<00:07:09.630> only 00:07:10.620 --> 00:07:10.630 align:start position:0% with the information of the object only 00:07:10.630 --> 00:07:12.659 align:start position:0% with the information of the object only but<00:07:10.900> we<00:07:11.050> need<00:07:11.320> information<00:07:11.590> we<00:07:12.040> can<00:07:12.220> connect 00:07:12.659 --> 00:07:12.669 align:start position:0% but we need information we can connect 00:07:12.669 --> 00:07:15.270 align:start position:0% but we need information we can connect to<00:07:13.060> this<00:07:13.240> network<00:07:13.380> and<00:07:14.380> then<00:07:14.650> it<00:07:15.130> gets 00:07:15.270 --> 00:07:15.280 align:start position:0% to this network and then it gets 00:07:15.280 --> 00:07:17.610 align:start position:0% to this network and then it gets information<00:07:15.970> and<00:07:16.090> if<00:07:17.080> you<00:07:17.110> don't<00:07:17.410> need 00:07:17.610 --> 00:07:17.620 align:start position:0% information and if you don't need 00:07:17.620 --> 00:07:23.130 align:start position:0% information and if you don't need innovation<00:07:18.070> you<00:07:18.130> don't<00:07:18.370> either<00:07:18.669> pure<00:07:18.880> life 00:07:23.130 --> 00:07:23.140 align:start position:0% 00:07:23.140 --> 00:07:25.440 align:start position:0% for<00:07:23.560> the<00:07:23.620> center<00:07:23.980> of<00:07:24.130> their<00:07:24.370> in<00:07:25.030> tube<00:07:25.240> system 00:07:25.440 --> 00:07:25.450 align:start position:0% for the center of their in tube system 00:07:25.450 --> 00:07:29.850 align:start position:0% for the center of their in tube system is<00:07:25.900> the<00:07:27.120> future<00:07:28.120> registry<00:07:28.870> that<00:07:29.200> means<00:07:29.710> we 00:07:29.850 --> 00:07:29.860 align:start position:0% is the future registry that means we 00:07:29.860 --> 00:07:33.600 align:start position:0% is the future registry that means we have<00:07:30.070> someone's<00:07:31.060> this<00:07:31.510> all<00:07:32.010> footnotes<00:07:33.010> maybe 00:07:33.600 --> 00:07:33.610 align:start position:0% have someone's this all footnotes maybe 00:07:33.610 --> 00:07:35.880 align:start position:0% have someone's this all footnotes maybe archive<00:07:34.090> notes<00:07:34.360> with<00:07:35.050> additional<00:07:35.470> piece<00:07:35.860> of 00:07:35.880 --> 00:07:35.890 align:start position:0% archive notes with additional piece of 00:07:35.890 --> 00:07:38.550 align:start position:0% archive notes with additional piece of software<00:07:36.460> the<00:07:37.300> include<00:07:37.600> notes<00:07:37.900> of<00:07:38.110> them<00:07:38.350> and 00:07:38.550 --> 00:07:38.560 align:start position:0% software the include notes of them and 00:07:38.560 --> 00:07:41.670 align:start position:0% software the include notes of them and these<00:07:39.400> notes<00:07:39.760> register<00:07:40.600> to<00:07:40.810> a<00:07:40.840> smart<00:07:41.140> contract 00:07:41.670 --> 00:07:41.680 align:start position:0% these notes register to a smart contract 00:07:41.680 --> 00:07:45.180 align:start position:0% these notes register to a smart contract I<00:07:41.800> guess<00:07:41.950> the<00:07:42.100> contract<00:07:42.660> they<00:07:44.010> give<00:07:45.010> the 00:07:45.180 --> 00:07:45.190 align:start position:0% I guess the contract they give the 00:07:45.190 --> 00:07:47.340 align:start position:0% I guess the contract they give the deficit<00:07:45.760> security<00:07:46.510> person<00:07:46.750> I<00:07:46.840> will<00:07:47.020> explain 00:07:47.340 --> 00:07:47.350 align:start position:0% deficit security person I will explain 00:07:47.350 --> 00:07:49.710 align:start position:0% deficit security person I will explain later<00:07:47.650> by<00:07:47.950> Benitez<00:07:48.520> and<00:07:48.670> give<00:07:49.510> some 00:07:49.710 --> 00:07:49.720 align:start position:0% later by Benitez and give some 00:07:49.720 --> 00:07:50.990 align:start position:0% later by Benitez and give some information 00:07:50.990 --> 00:07:51.000 align:start position:0% information 00:07:51.000 --> 00:07:56.910 align:start position:0% information so<00:07:52.000> then<00:07:52.450> Dix<00:07:53.350> lines<00:07:54.420> they<00:07:55.420> can<00:07:55.870> get<00:07:56.350> this<00:07:56.680> list 00:07:56.910 --> 00:07:56.920 align:start position:0% so then Dix lines they can get this list 00:07:56.920 --> 00:08:01.080 align:start position:0% so then Dix lines they can get this list and<00:07:57.730> with<00:07:58.540> this<00:07:58.750> list<00:07:59.080> they<00:07:59.620> know<00:07:59.860> which<00:08:00.820> notes 00:08:01.080 --> 00:08:01.090 align:start position:0% and with this list they know which notes 00:08:01.090 --> 00:08:04.050 align:start position:0% and with this list they know which notes belong<00:08:01.510> to<00:08:01.720> the<00:08:01.840> network<00:08:02.200> and<00:08:02.490> then<00:08:03.490> they<00:08:03.760> can 00:08:04.050 --> 00:08:04.060 align:start position:0% belong to the network and then they can 00:08:04.060 --> 00:08:07.600 align:start position:0% belong to the network and then they can interact 00:08:07.600 --> 00:08:07.610 align:start position:0% 00:08:07.610 --> 00:08:12.010 align:start position:0% so<00:08:08.210> and<00:08:08.569> how<00:08:09.020> does<00:08:09.080> it<00:08:09.319> work<00:08:10.180> let's<00:08:11.180> start<00:08:11.780> with 00:08:12.010 --> 00:08:12.020 align:start position:0% so and how does it work let's start with 00:08:12.020 --> 00:08:14.830 align:start position:0% so and how does it work let's start with one<00:08:12.229> client<00:08:12.470> and<00:08:12.830> this<00:08:13.340> client<00:08:13.400> has<00:08:14.300> this<00:08:14.539> list 00:08:14.830 --> 00:08:14.840 align:start position:0% one client and this client has this list 00:08:14.840 --> 00:08:18.279 align:start position:0% one client and this client has this list of<00:08:15.110> positive<00:08:15.740> notes<00:08:16.159> so<00:08:16.699> in<00:08:16.849> this<00:08:17.000> list<00:08:17.569> is<00:08:18.110> the 00:08:18.279 --> 00:08:18.289 align:start position:0% of positive notes so in this list is the 00:08:18.289 --> 00:08:22.149 align:start position:0% of positive notes so in this list is the newest<00:08:18.650> outward<00:08:19.520> XS<00:08:20.389> this<00:08:20.629> node<00:08:20.840> it<00:08:21.650> knows<00:08:21.919> the 00:08:22.149 --> 00:08:22.159 align:start position:0% newest outward XS this node it knows the 00:08:22.159 --> 00:08:25.540 align:start position:0% newest outward XS this node it knows the securely<00:08:22.819> deficit<00:08:23.360> and<00:08:23.539> this<00:08:24.110> head<00:08:24.319> has<00:08:24.650> kind 00:08:25.540 --> 00:08:25.550 align:start position:0% securely deficit and this head has kind 00:08:25.550 --> 00:08:27.939 align:start position:0% securely deficit and this head has kind of<00:08:25.759> the<00:08:25.939> rotation<00:08:26.419> system<00:08:26.569> so<00:08:27.439> for<00:08:27.620> instance 00:08:27.939 --> 00:08:27.949 align:start position:0% of the rotation system so for instance 00:08:27.949 --> 00:08:30.339 align:start position:0% of the rotation system so for instance if<00:08:28.129> the<00:08:28.729> throws<00:08:29.000> of<00:08:29.030> a<00:08:29.270> this<00:08:29.479> road<00:08:29.960> is<00:08:30.199> not 00:08:30.339 --> 00:08:30.349 align:start position:0% if the throws of a this road is not 00:08:30.349 --> 00:08:31.029 align:start position:0% if the throws of a this road is not answering 00:08:31.029 --> 00:08:31.039 align:start position:0% answering 00:08:31.039 --> 00:08:33.850 align:start position:0% answering then<00:08:31.460> it<00:08:31.639> will<00:08:31.789> be<00:08:31.909> blacklisted<00:08:32.390> or<00:08:32.870> in<00:08:33.620> some 00:08:33.850 --> 00:08:33.860 align:start position:0% then it will be blacklisted or in some 00:08:33.860 --> 00:08:41.110 align:start position:0% then it will be blacklisted or in some way<00:08:36.219> so<00:08:37.870> then<00:08:38.870> now<00:08:39.649> the<00:08:40.519> client<00:08:40.909> needs 00:08:41.110 --> 00:08:41.120 align:start position:0% way so then now the client needs 00:08:41.120 --> 00:08:43.690 align:start position:0% way so then now the client needs information<00:08:41.539> it<00:08:42.200> can<00:08:42.409> excesses<00:08:42.800> list<00:08:43.190> when 00:08:43.690 --> 00:08:43.700 align:start position:0% information it can excesses list when 00:08:43.700 --> 00:08:46.389 align:start position:0% information it can excesses list when selects<00:08:44.360> one<00:08:44.660> of<00:08:45.260> these<00:08:45.470> nodes<00:08:45.740> in<00:08:45.950> this<00:08:46.100> case 00:08:46.389 --> 00:08:46.399 align:start position:0% selects one of these nodes in this case 00:08:46.399 --> 00:08:49.360 align:start position:0% selects one of these nodes in this case it's<00:08:47.300> an<00:08:47.420> ex-world<00:08:47.870> beam<00:08:48.200> and<00:08:48.560> since 00:08:49.360 --> 00:08:49.370 align:start position:0% it's an ex-world beam and since 00:08:49.370 --> 00:08:51.850 align:start position:0% it's an ex-world beam and since obviously<00:08:49.610> request<00:08:50.390> for<00:08:50.899> I<00:08:50.990> want<00:08:51.290> to<00:08:51.470> know<00:08:51.649> for 00:08:51.850 --> 00:08:51.860 align:start position:0% obviously request for I want to know for 00:08:51.860 --> 00:08:55.900 align:start position:0% obviously request for I want to know for instance<00:08:52.040> if<00:08:52.430> I<00:08:53.060> have<00:08:53.240> access<00:08:53.450> to<00:08:53.660> this<00:08:54.910> able 00:08:55.900 --> 00:08:55.910 align:start position:0% instance if I have access to this able 00:08:55.910 --> 00:08:59.160 align:start position:0% instance if I have access to this able to<00:08:56.149> disprove<00:08:56.589> and<00:08:57.589> it<00:08:57.769> receives<00:08:58.339> the<00:08:58.610> answer 00:08:59.160 --> 00:08:59.170 align:start position:0% to disprove and it receives the answer 00:08:59.170 --> 00:09:03.069 align:start position:0% to disprove and it receives the answer yes<00:09:00.170> what<00:09:01.070> about<00:09:01.100> the<00:09:01.579> answers<00:09:02.029> so<00:09:02.839> this<00:09:02.990> is 00:09:03.069 --> 00:09:03.079 align:start position:0% yes what about the answers so this is 00:09:03.079 --> 00:09:05.470 align:start position:0% yes what about the answers so this is the<00:09:03.230> same<00:09:03.470> thing<00:09:03.860> like<00:09:04.160> a<00:09:04.490> word<00:09:04.940> client<00:09:05.300> would 00:09:05.470 --> 00:09:05.480 align:start position:0% the same thing like a word client would 00:09:05.480 --> 00:09:08.440 align:start position:0% the same thing like a word client would receive<00:09:05.810> but<00:09:06.709> additional<00:09:07.640> to<00:09:07.760> this<00:09:07.910> we 00:09:08.440 --> 00:09:08.450 align:start position:0% receive but additional to this we 00:09:08.450 --> 00:09:10.690 align:start position:0% receive but additional to this we proceed<00:09:09.320> with<00:09:09.440> broker<00:09:09.860> food<00:09:10.100> for<00:09:10.550> this 00:09:10.690 --> 00:09:10.700 align:start position:0% proceed with broker food for this 00:09:10.700 --> 00:09:14.410 align:start position:0% proceed with broker food for this information<00:09:11.000> and<00:09:11.620> we<00:09:12.620> receive<00:09:12.890> to<00:09:13.010> Proctor<00:09:13.550> so 00:09:14.410 --> 00:09:14.420 align:start position:0% information and we receive to Proctor so 00:09:14.420 --> 00:09:16.300 align:start position:0% information and we receive to Proctor so in<00:09:14.540> 50s<00:09:14.870> information<00:09:15.350> declined<00:09:15.769> but<00:09:15.949> itself 00:09:16.300 --> 00:09:16.310 align:start position:0% in 50s information declined but itself 00:09:16.310 --> 00:09:19.540 align:start position:0% in 50s information declined but itself can<00:09:17.079> validate<00:09:18.079> okay<00:09:18.649> this<00:09:18.829> information<00:09:19.459> I 00:09:19.540 --> 00:09:19.550 align:start position:0% can validate okay this information I 00:09:19.550 --> 00:09:24.160 align:start position:0% can validate okay this information I received<00:09:20.000> belongs<00:09:20.959> to<00:09:21.350> this<00:09:21.740> partner<00:09:22.310> but<00:09:23.300> so 00:09:24.160 --> 00:09:24.170 align:start position:0% received belongs to this partner but so 00:09:24.170 --> 00:09:26.490 align:start position:0% received belongs to this partner but so at<00:09:24.529> this<00:09:24.740> point<00:09:25.040> we<00:09:25.279> don't<00:09:25.490> know<00:09:25.670> if<00:09:26.120> would<00:09:26.449> be 00:09:26.490 --> 00:09:26.500 align:start position:0% at this point we don't know if would be 00:09:26.500 --> 00:09:30.490 align:start position:0% at this point we don't know if would be maybe<00:09:27.500> did<00:09:28.490> send<00:09:28.760> us<00:09:28.940> a<00:09:29.180> manipulated<00:09:29.750> from<00:09:29.899> you 00:09:30.490 --> 00:09:30.500 align:start position:0% maybe did send us a manipulated from you 00:09:30.500 --> 00:09:32.560 align:start position:0% maybe did send us a manipulated from you know<00:09:30.680> this<00:09:31.190> block<00:09:31.490> and<00:09:31.820> this<00:09:32.029> information 00:09:32.560 --> 00:09:32.570 align:start position:0% know this block and this information 00:09:32.570 --> 00:09:35.139 align:start position:0% know this block and this information just<00:09:32.600> belongs<00:09:32.990> together<00:09:33.170> but<00:09:34.070> if<00:09:34.880> this 00:09:35.139 --> 00:09:35.149 align:start position:0% just belongs together but if this 00:09:35.149 --> 00:09:37.300 align:start position:0% just belongs together but if this committee<00:09:35.570> belongs<00:09:35.959> in<00:09:36.110> prop<00:09:36.320> chain<00:09:36.529> we<00:09:37.100> don't 00:09:37.300 --> 00:09:37.310 align:start position:0% committee belongs in prop chain we don't 00:09:37.310 --> 00:09:41.439 align:start position:0% committee belongs in prop chain we don't know<00:09:37.810> that's<00:09:38.810> why<00:09:39.050> we<00:09:39.829> also<00:09:40.579> sent<00:09:41.120> for 00:09:41.439 --> 00:09:41.449 align:start position:0% know that's why we also sent for 00:09:41.449 --> 00:09:43.689 align:start position:0% know that's why we also sent for additional<00:09:41.899> requests<00:09:42.380> to<00:09:42.920> visit<00:09:43.220> visit<00:09:43.459> like 00:09:43.689 --> 00:09:43.699 align:start position:0% additional requests to visit visit like 00:09:43.699 --> 00:09:46.810 align:start position:0% additional requests to visit visit like other<00:09:43.910> words<00:09:44.180> from<00:09:44.420> the<00:09:44.480> list<00:09:45.160> so<00:09:46.160> this<00:09:46.550> whole 00:09:46.810 --> 00:09:46.820 align:start position:0% other words from the list so this whole 00:09:46.820 --> 00:09:48.269 align:start position:0% other words from the list so this whole time<00:09:47.000> my<00:09:47.600> clients 00:09:48.269 --> 00:09:48.279 align:start position:0% time my clients 00:09:48.279 --> 00:09:51.360 align:start position:0% time my clients no<00:09:48.490> Desmond<00:09:48.970> transmitters<00:09:49.720> so<00:09:50.529> and<00:09:50.889> then<00:09:51.069> we 00:09:51.360 --> 00:09:51.370 align:start position:0% no Desmond transmitters so and then we 00:09:51.370 --> 00:09:55.579 align:start position:0% no Desmond transmitters so and then we asked<00:09:51.819> North<00:09:52.149> beam<00:09:52.860> the<00:09:53.860> disk<00:09:54.100> is<00:09:54.339> a<00:09:54.639> spoon<00:09:55.329> a 00:09:55.579 --> 00:09:55.589 align:start position:0% asked North beam the disk is a spoon a 00:09:55.589 --> 00:09:59.220 align:start position:0% asked North beam the disk is a spoon a and<00:09:56.589> also<00:09:56.860> the<00:09:57.069> note<00:09:57.249> seen<00:09:57.610> that<00:09:58.569> the<00:09:58.720> polity 00:09:59.220 --> 00:09:59.230 align:start position:0% and also the note seen that the polity 00:09:59.230 --> 00:10:01.290 align:start position:0% and also the note seen that the polity is<00:09:59.259> that<00:09:59.620> this<00:09:59.829> block<00:10:00.220> really<00:10:00.790> belongs<00:10:01.120> in 00:10:01.290 --> 00:10:01.300 align:start position:0% is that this block really belongs in 00:10:01.300 --> 00:10:05.610 align:start position:0% is that this block really belongs in culture<00:10:01.740> and<00:10:03.029> began<00:10:04.029> this<00:10:04.360> validation<00:10:04.990> by 00:10:05.610 --> 00:10:05.620 align:start position:0% culture and began this validation by 00:10:05.620 --> 00:10:10.110 align:start position:0% culture and began this validation by getting<00:10:06.370> a<00:10:06.610> science<00:10:07.209> job<00:10:07.839> -<00:10:08.459> so<00:10:09.459> I<00:10:09.759> introduced 00:10:10.110 --> 00:10:10.120 align:start position:0% getting a science job - so I introduced 00:10:10.120 --> 00:10:12.030 align:start position:0% getting a science job - so I introduced a<00:10:10.480> branch<00:10:10.899> because<00:10:11.259> the<00:10:11.379> progress<00:10:11.800> is<00:10:11.920> the 00:10:12.030 --> 00:10:12.040 align:start position:0% a branch because the progress is the 00:10:12.040 --> 00:10:14.489 align:start position:0% a branch because the progress is the only<00:10:12.189> information<00:10:12.370> we<00:10:13.059> can<00:10:13.600> validate<00:10:13.839> in<00:10:14.379> the 00:10:14.489 --> 00:10:14.499 align:start position:0% only information we can validate in the 00:10:14.499 --> 00:10:16.679 align:start position:0% only information we can validate in the past<00:10:14.829> or<00:10:15.160> the<00:10:15.279> proper<00:10:15.490> shape<00:10:15.699> so<00:10:16.420> it<00:10:16.540> means 00:10:16.679 --> 00:10:16.689 align:start position:0% past or the proper shape so it means 00:10:16.689 --> 00:10:18.960 align:start position:0% past or the proper shape so it means remember<00:10:17.529> this<00:10:17.920> smart<00:10:18.279> contract<00:10:18.759> the 00:10:18.960 --> 00:10:18.970 align:start position:0% remember this smart contract the 00:10:18.970 --> 00:10:22.769 align:start position:0% remember this smart contract the registry<00:10:19.649> all<00:10:20.649> these<00:10:21.399> nodes<00:10:21.879> are<00:10:22.120> registered 00:10:22.769 --> 00:10:22.779 align:start position:0% registry all these nodes are registered 00:10:22.779 --> 00:10:25.650 align:start position:0% registry all these nodes are registered in<00:10:22.959> this<00:10:23.110> registry<00:10:23.589> and<00:10:23.949> now<00:10:24.490> within<00:10:25.240> which<00:10:25.480> we 00:10:25.650 --> 00:10:25.660 align:start position:0% in this registry and now within which we 00:10:25.660 --> 00:10:30.780 align:start position:0% in this registry and now within which we can't<00:10:25.959> go<00:10:26.290> to<00:10:26.949> this<00:10:27.100> registry<00:10:27.610> and<00:10:28.589> can<00:10:29.790> check 00:10:30.780 --> 00:10:30.790 align:start position:0% can't go to this registry and can check 00:10:30.790 --> 00:10:34.170 align:start position:0% can't go to this registry and can check if<00:10:31.120> this<00:10:32.259> is<00:10:32.470> that<00:10:32.649> notice<00:10:32.860> really<00:10:33.459> the 00:10:34.170 --> 00:10:34.180 align:start position:0% if this is that notice really the 00:10:34.180 --> 00:10:36.470 align:start position:0% if this is that notice really the correct<00:10:34.569> profession<00:10:35.110> and<00:10:35.439> if<00:10:35.620> we<00:10:35.769> find<00:10:36.100> that 00:10:36.470 --> 00:10:36.480 align:start position:0% correct profession and if we find that 00:10:36.480 --> 00:10:39.569 align:start position:0% correct profession and if we find that one<00:10:37.480> of<00:10:37.629> these<00:10:37.749> nodes<00:10:38.050> is<00:10:38.319> not<00:10:38.980> this<00:10:39.249> one<00:10:39.459> in 00:10:39.569 --> 00:10:39.579 align:start position:0% one of these nodes is not this one in 00:10:39.579 --> 00:10:41.999 align:start position:0% one of these nodes is not this one in right<00:10:39.759> thing<00:10:40.079> meaning<00:10:41.079> that<00:10:41.230> he<00:10:41.410> is<00:10:41.439> science 00:10:41.999 --> 00:10:42.009 align:start position:0% right thing meaning that he is science 00:10:42.009 --> 00:10:44.489 align:start position:0% right thing meaning that he is science of<00:10:42.129> all<00:10:42.279> projects<00:10:42.730> we<00:10:43.149> can<00:10:43.360> convict<00:10:43.839> a<00:10:43.990> project 00:10:44.489 --> 00:10:44.499 align:start position:0% of all projects we can convict a project 00:10:44.499 --> 00:10:46.739 align:start position:0% of all projects we can convict a project turned<00:10:44.949> out<00:10:45.100> after<00:10:45.399> this<00:10:45.550> gets<00:10:46.120> his<00:10:46.300> deficit 00:10:46.739 --> 00:10:46.749 align:start position:0% turned out after this gets his deficit 00:10:46.749 --> 00:10:50.340 align:start position:0% turned out after this gets his deficit so<00:10:47.740> it<00:10:47.829> is<00:10:47.949> a<00:10:47.980> stun<00:10:48.420> we<00:10:49.420> call<00:10:49.629> it<00:10:49.749> virtual<00:10:49.959> box 00:10:50.340 --> 00:10:50.350 align:start position:0% so it is a stun we call it virtual box 00:10:50.350 --> 00:10:50.790 align:start position:0% so it is a stun we call it virtual box trucks 00:10:50.790 --> 00:10:50.800 align:start position:0% trucks 00:10:50.800 --> 00:10:54.809 align:start position:0% trucks it<00:10:51.459> means<00:10:51.699> if<00:10:51.939> one<00:10:52.449> of<00:10:52.660> these<00:10:52.779> nodes<00:10:53.819> sense 00:10:54.809 --> 00:10:54.819 align:start position:0% it means if one of these nodes sense 00:10:54.819 --> 00:10:58.110 align:start position:0% it means if one of these nodes sense from<00:10:55.269> nation<00:10:55.839> he<00:10:56.829> loses<00:10:57.160> his<00:10:57.309> deficit<00:10:57.759> that's 00:10:58.110 --> 00:10:58.120 align:start position:0% from nation he loses his deficit that's 00:10:58.120 --> 00:11:01.590 align:start position:0% from nation he loses his deficit that's why<00:10:58.269> this<00:10:58.750> deficit<00:10:59.230> is<00:10:59.350> important<00:11:00.370> hence<00:11:01.089> is 00:11:01.590 --> 00:11:01.600 align:start position:0% why this deficit is important hence is 00:11:01.600 --> 00:11:02.730 align:start position:0% why this deficit is important hence is thrown<00:11:01.959> out<00:11:02.139> of<00:11:02.170> the<00:11:02.379> list 00:11:02.730 --> 00:11:02.740 align:start position:0% thrown out of the list 00:11:02.740 --> 00:11:06.059 align:start position:0% thrown out of the list so<00:11:03.129> an<00:11:03.250> images<00:11:03.910> behave<00:11:04.870> there<00:11:05.500> will<00:11:05.680> be<00:11:05.709> no 00:11:06.059 --> 00:11:06.069 align:start position:0% so an images behave there will be no 00:11:06.069 --> 00:11:09.600 align:start position:0% so an images behave there will be no exactly<00:11:06.670> with<00:11:07.870> security<00:11:08.649> we<00:11:09.129> can<00:11:09.339> trust 00:11:09.600 --> 00:11:09.610 align:start position:0% exactly with security we can trust 00:11:09.610 --> 00:11:12.240 align:start position:0% exactly with security we can trust them<00:11:10.019> so<00:11:11.019> it<00:11:11.139> now<00:11:11.379> is<00:11:11.709> all<00:11:11.949> of<00:11:12.100> these 00:11:12.240 --> 00:11:12.250 align:start position:0% them so it now is all of these 00:11:12.250 --> 00:11:14.400 align:start position:0% them so it now is all of these deformations<00:11:12.639> we<00:11:13.000> get<00:11:13.149> into<00:11:13.720> the<00:11:13.930> program<00:11:14.139> per 00:11:14.400 --> 00:11:14.410 align:start position:0% deformations we get into the program per 00:11:14.410 --> 00:11:17.490 align:start position:0% deformations we get into the program per entity<00:11:14.800> side<00:11:15.189> perhaps<00:11:15.790> we<00:11:16.629> can<00:11:16.779> validate<00:11:16.930> that 00:11:17.490 --> 00:11:17.500 align:start position:0% entity side perhaps we can validate that 00:11:17.500 --> 00:11:19.980 align:start position:0% entity side perhaps we can validate that information<00:11:18.279> really<00:11:18.519> belongs<00:11:18.970> to<00:11:19.509> this<00:11:19.660> block 00:11:19.980 --> 00:11:19.990 align:start position:0% information really belongs to this block 00:11:19.990 --> 00:11:23.220 align:start position:0% information really belongs to this block and<00:11:20.230> this<00:11:20.889> that<00:11:21.430> this<00:11:21.790> block<00:11:22.089> is<00:11:22.300> part<00:11:22.990> of<00:11:23.110> the 00:11:23.220 --> 00:11:23.230 align:start position:0% and this that this block is part of the 00:11:23.230 --> 00:11:25.160 align:start position:0% and this that this block is part of the rupture 00:11:25.160 --> 00:11:25.170 align:start position:0% rupture 00:11:25.170 --> 00:11:27.799 align:start position:0% rupture so<00:11:25.709> additional<00:11:26.189> to<00:11:26.730> disruption<00:11:27.359> constructs 00:11:27.799 --> 00:11:27.809 align:start position:0% so additional to disruption constructs 00:11:27.809 --> 00:11:30.769 align:start position:0% so additional to disruption constructs of<00:11:28.019> course<00:11:28.290> you<00:11:28.769> could<00:11:28.949> also<00:11:29.160> run<00:11:29.600> active<00:11:30.600> hot 00:11:30.769 --> 00:11:30.779 align:start position:0% of course you could also run active hot 00:11:30.779 --> 00:11:33.559 align:start position:0% of course you could also run active hot stocks<00:11:31.109> which<00:11:31.799> is<00:11:32.009> the<00:11:32.209> additional<00:11:33.209> security 00:11:33.559 --> 00:11:33.569 align:start position:0% stocks which is the additional security 00:11:33.569 --> 00:11:37.460 align:start position:0% stocks which is the additional security property<00:11:34.350> so<00:11:34.980> they<00:11:35.069> can<00:11:35.279> run<00:11:35.459> in<00:11:36.389> client<00:11:36.959> which 00:11:37.460 --> 00:11:37.470 align:start position:0% property so they can run in client which 00:11:37.470 --> 00:11:41.329 align:start position:0% property so they can run in client which act<00:11:37.799> as<00:11:38.189> he<00:11:38.699> would<00:11:38.879> be<00:11:39.059> only<00:11:39.269> client<00:11:40.129> but<00:11:41.129> he 00:11:41.329 --> 00:11:41.339 align:start position:0% act as he would be only client but he 00:11:41.339 --> 00:11:45.259 align:start position:0% act as he would be only client but he has<00:11:41.660> connections<00:11:42.660> reduction<00:11:43.199> and<00:11:43.439> then<00:11:43.980> if<00:11:44.309> he 00:11:45.259 --> 00:11:45.269 align:start position:0% has connections reduction and then if he 00:11:45.269 --> 00:11:49.489 align:start position:0% has connections reduction and then if he finds<00:11:45.779> one<00:11:46.040> Road<00:11:47.040> which<00:11:47.779> answers<00:11:48.779> gives<00:11:49.319> him 00:11:49.489 --> 00:11:49.499 align:start position:0% finds one Road which answers gives him 00:11:49.499 --> 00:11:52.030 align:start position:0% finds one Road which answers gives him the<00:11:49.649> front<00:11:49.919> end<00:11:50.100> zone<00:11:50.279> he<00:11:50.730> can<00:11:50.939> direct<00:11:51.629> him 00:11:52.030 --> 00:11:52.040 align:start position:0% the front end zone he can direct him 00:11:52.040 --> 00:11:54.409 align:start position:0% the front end zone he can direct him convict<00:11:53.040> him<00:11:53.160> an<00:11:53.339> indirect<00:11:53.669> sale 00:11:54.409 --> 00:11:54.419 align:start position:0% convict him an indirect sale 00:11:54.419 --> 00:11:57.829 align:start position:0% convict him an indirect sale so<00:11:54.809> why<00:11:55.049> is<00:11:55.109> this<00:11:55.319> third<00:11:55.589> Horton<00:11:56.389> so<00:11:57.389> he<00:11:57.509> wants 00:11:57.829 --> 00:11:57.839 align:start position:0% so why is this third Horton so he wants 00:11:57.839 --> 00:12:00.379 align:start position:0% so why is this third Horton so he wants to<00:11:58.079> have<00:11:58.410> a<00:11:58.619> security<00:11:59.160> so<00:11:59.309> that<00:11:59.489> when<00:11:59.879> I<00:12:00.119> as 00:12:00.379 --> 00:12:00.389 align:start position:0% to have a security so that when I as 00:12:00.389 --> 00:12:03.799 align:start position:0% to have a security so that when I as client<00:12:00.989> asked<00:12:01.859> for<00:12:01.919> information<00:12:02.329> then<00:12:03.329> I<00:12:03.509> can 00:12:03.799 --> 00:12:03.809 align:start position:0% client asked for information then I can 00:12:03.809 --> 00:12:07.849 align:start position:0% client asked for information then I can rely<00:12:04.230> on<00:12:04.259> the<00:12:04.529> information<00:12:04.939> so<00:12:06.290> when<00:12:07.290> I<00:12:07.499> get 00:12:07.849 --> 00:12:07.859 align:start position:0% rely on the information so when I get 00:12:07.859 --> 00:12:09.979 align:start position:0% rely on the information so when I get information<00:12:08.160> before<00:12:08.699> of<00:12:09.119> this<00:12:09.299> proves<00:12:09.600> then<00:12:09.959> I 00:12:09.979 --> 00:12:09.989 align:start position:0% information before of this proves then I 00:12:09.989 --> 00:12:12.829 align:start position:0% information before of this proves then I can<00:12:10.319> be<00:12:10.499> sure<00:12:10.889> that<00:12:11.220> this<00:12:11.910> information<00:12:12.149> is 00:12:12.829 --> 00:12:12.839 align:start position:0% can be sure that this information is 00:12:12.839 --> 00:12:13.539 align:start position:0% can be sure that this information is secure 00:12:13.539 --> 00:12:13.549 align:start position:0% secure 00:12:13.549 --> 00:12:17.599 align:start position:0% secure of<00:12:14.549> course<00:12:14.929> including<00:12:15.929> secure<00:12:16.799> in<00:12:17.040> the<00:12:17.220> amount 00:12:17.599 --> 00:12:17.609 align:start position:0% of course including secure in the amount 00:12:17.609 --> 00:12:20.539 align:start position:0% of course including secure in the amount of<00:12:17.939> debt<00:12:18.359> were<00:12:18.509> often<00:12:18.869> in<00:12:19.079> the<00:12:19.169> deficit<00:12:19.949> which 00:12:20.539 --> 00:12:20.549 align:start position:0% of debt were often in the deficit which 00:12:20.549 --> 00:12:23.809 align:start position:0% of debt were often in the deficit which these<00:12:21.089> nodes<00:12:21.480> this<00:12:21.869> in<00:12:22.199> registry<00:12:22.829> so<00:12:23.369> instance 00:12:23.809 --> 00:12:23.819 align:start position:0% these nodes this in registry so instance 00:12:23.819 --> 00:12:27.739 align:start position:0% these nodes this in registry so instance if<00:12:23.999> these<00:12:24.899> nodes<00:12:25.249> made<00:12:26.249> the<00:12:26.369> deficit<00:12:26.730> of<00:12:26.879> one 00:12:27.739 --> 00:12:27.749 align:start position:0% if these nodes made the deficit of one 00:12:27.749 --> 00:12:31.039 align:start position:0% if these nodes made the deficit of one each<00:12:27.959> other<00:12:28.699> then<00:12:29.699> I<00:12:29.879> can<00:12:30.329> be<00:12:30.480> secure 00:12:31.039 --> 00:12:31.049 align:start position:0% each other then I can be secure 00:12:31.049 --> 00:12:34.970 align:start position:0% each other then I can be secure they<00:12:31.319> will<00:12:31.529> not<00:12:31.879> wins<00:12:32.879> to<00:12:33.569> lose<00:12:33.839> his<00:12:34.290> sister 00:12:34.970 --> 00:12:34.980 align:start position:0% they will not wins to lose his sister 00:12:34.980 --> 00:12:37.249 align:start position:0% they will not wins to lose his sister Emma<00:12:35.309> said<00:12:35.489> and<00:12:36.029> give<00:12:36.239> me<00:12:36.419> a<00:12:36.449> firm<00:12:36.869> hands<00:12:37.169> of 00:12:37.249 --> 00:12:37.259 align:start position:0% Emma said and give me a firm hands of 00:12:37.259 --> 00:12:41.390 align:start position:0% Emma said and give me a firm hands of world<00:12:37.850> for<00:12:38.850> for<00:12:39.660> infest 00:12:41.390 --> 00:12:41.400 align:start position:0% world for for infest 00:12:41.400 --> 00:12:45.710 align:start position:0% world for for infest hello<00:12:41.820> Ruth<00:12:42.420> princess<00:12:43.200> divine<00:12:44.480> send<00:12:45.480> it<00:12:45.630> to 00:12:45.710 --> 00:12:45.720 align:start position:0% hello Ruth princess divine send it to 00:12:45.720 --> 00:12:48.620 align:start position:0% hello Ruth princess divine send it to attention<00:12:46.230> to<00:12:46.410> pay<00:12:46.890> for<00:12:47.190> energy<00:12:47.630> businesses 00:12:48.620 --> 00:12:48.630 align:start position:0% attention to pay for energy businesses 00:12:48.630 --> 00:12:49.130 align:start position:0% attention to pay for energy businesses the<00:12:48.750> role<00:12:48.930> of 00:12:49.130 --> 00:12:49.140 align:start position:0% the role of 00:12:49.140 --> 00:12:52.880 align:start position:0% the role of mong-joon<00:12:49.860> and<00:12:50.460> I<00:12:50.940> know<00:12:51.050> the<00:12:52.050> system<00:12:52.290> in<00:12:52.650> here 00:12:52.880 --> 00:12:52.890 align:start position:0% mong-joon and I know the system in here 00:12:52.890 --> 00:12:56.540 align:start position:0% mong-joon and I know the system in here is<00:12:53.130> a<00:12:53.400> role<00:12:53.790> of<00:12:53.970> tenure<00:12:54.390> or<00:12:54.600> more<00:12:54.960> or<00:12:55.470> more<00:12:55.550> can 00:12:56.540 --> 00:12:56.550 align:start position:0% is a role of tenure or more or more can 00:12:56.550 --> 00:12:59.510 align:start position:0% is a role of tenure or more or more can be<00:12:56.580> secured<00:12:57.060> if<00:12:57.660> I<00:12:57.870> would<00:12:58.080> hope<00:12:59.040> that<00:12:59.070> much 00:12:59.510 --> 00:12:59.520 align:start position:0% be secured if I would hope that much 00:12:59.520 --> 00:13:02.570 align:start position:0% be secured if I would hope that much work<00:12:59.880> a<00:13:00.150> very<00:13:00.420> expensive<00:13:01.050> apartment<00:13:01.950> of 00:13:02.570 --> 00:13:02.580 align:start position:0% work a very expensive apartment of 00:13:02.580 --> 00:13:04.490 align:start position:0% work a very expensive apartment of course<00:13:02.640> I<00:13:02.940> need<00:13:03.120> a<00:13:03.270> higher<00:13:03.450> deficit<00:13:03.930> to<00:13:04.320> be 00:13:04.490 --> 00:13:04.500 align:start position:0% course I need a higher deficit to be 00:13:04.500 --> 00:13:07.010 align:start position:0% course I need a higher deficit to be secured<00:13:04.890> that<00:13:05.610> these<00:13:06.090> notes<00:13:06.360> are<00:13:06.600> not<00:13:06.750> trying 00:13:07.010 --> 00:13:07.020 align:start position:0% secured that these notes are not trying 00:13:07.020 --> 00:13:08.790 align:start position:0% secured that these notes are not trying to<00:13:07.140> betrayed 00:13:08.790 --> 00:13:08.800 align:start position:0% to betrayed 00:13:08.800 --> 00:13:14.590 align:start position:0% to betrayed [Music] 00:13:14.590 --> 00:13:14.600 align:start position:0% 00:13:14.600 --> 00:13:17.470 align:start position:0% so<00:13:15.140> it<00:13:15.320> the<00:13:15.800> disappointments<00:13:16.610> we<00:13:16.760> see<00:13:16.910> that 00:13:17.470 --> 00:13:17.480 align:start position:0% so it the disappointments we see that 00:13:17.480 --> 00:13:21.190 align:start position:0% so it the disappointments we see that the<00:13:18.050> only<00:13:18.260> thing<00:13:18.440> North's<00:13:19.340> can<00:13:19.910> do<00:13:20.300> our<00:13:20.480> Enzo 00:13:21.190 --> 00:13:21.200 align:start position:0% the only thing North's can do our Enzo 00:13:21.200 --> 00:13:23.440 align:start position:0% the only thing North's can do our Enzo incorrectly<00:13:21.740> for<00:13:22.460> if<00:13:22.640> the<00:13:22.820> ends<00:13:22.970> went<00:13:23.180> from 00:13:23.440 --> 00:13:23.450 align:start position:0% incorrectly for if the ends went from 00:13:23.450 --> 00:13:26.170 align:start position:0% incorrectly for if the ends went from then<00:13:23.810> they<00:13:23.960> lose<00:13:24.170> the<00:13:24.350> deficit<00:13:24.800> so<00:13:25.280> this<00:13:25.790> is 00:13:26.170 --> 00:13:26.180 align:start position:0% then they lose the deficit so this is 00:13:26.180 --> 00:13:34.750 align:start position:0% then they lose the deficit so this is not<00:13:26.510> a<00:13:26.540> good<00:13:32.560> like<00:13:33.560> how<00:13:33.860> can<00:13:33.920> someone<00:13:34.520> else 00:13:34.750 --> 00:13:34.760 align:start position:0% not a good like how can someone else 00:13:34.760 --> 00:13:42.720 align:start position:0% not a good like how can someone else check<00:13:37.540> and<00:13:38.540> see<00:13:38.750> if<00:13:38.900> they<00:13:39.050> don't<00:13:39.320> see<00:13:39.470> what<00:13:41.710> so 00:13:42.720 --> 00:13:42.730 align:start position:0% check and see if they don't see what so 00:13:42.730 --> 00:13:47.170 align:start position:0% check and see if they don't see what so you<00:13:43.730> just<00:13:44.680> if<00:13:45.680> these<00:13:45.920> new<00:13:46.070> to<00:13:46.280> make<00:13:46.640> sure<00:13:46.880> the 00:13:47.170 --> 00:13:47.180 align:start position:0% you just if these new to make sure the 00:13:47.180 --> 00:13:48.760 align:start position:0% you just if these new to make sure the client<00:13:47.540> will<00:13:47.660> never<00:13:47.840> know<00:13:48.080> whether<00:13:48.410> they<00:13:48.650> are 00:13:48.760 --> 00:13:48.770 align:start position:0% client will never know whether they are 00:13:48.770 --> 00:13:50.500 align:start position:0% client will never know whether they are answer<00:13:49.190> is<00:13:49.280> right<00:13:49.550> because<00:13:49.730> it<00:13:49.880> kind<00:13:50.210> of<00:13:50.270> check 00:13:50.500 --> 00:13:50.510 align:start position:0% answer is right because it kind of check 00:13:50.510 --> 00:13:53.440 align:start position:0% answer is right because it kind of check out<00:13:50.690> so<00:13:51.400> to<00:13:52.400> be<00:13:52.490> able<00:13:52.580> to<00:13:52.670> check<00:13:52.880> the<00:13:53.300> watch 00:13:53.440 --> 00:13:53.450 align:start position:0% out so to be able to check the watch 00:13:53.450 --> 00:13:54.940 align:start position:0% out so to be able to check the watch that<00:13:53.630> needs<00:13:53.840> to<00:13:54.020> see<00:13:54.230> what<00:13:54.470> the<00:13:54.590> client<00:13:54.920> is 00:13:54.940 --> 00:13:54.950 align:start position:0% that needs to see what the client is 00:13:54.950 --> 00:13:58.270 align:start position:0% that needs to see what the client is progressing<00:13:55.550> so<00:13:56.410> the<00:13:57.410> poor<00:13:57.620> children<00:13:57.920> this 00:13:58.270 --> 00:13:58.280 align:start position:0% progressing so the poor children this 00:13:58.280 --> 00:14:00.610 align:start position:0% progressing so the poor children this example<00:13:58.940> of<00:13:59.090> course<00:13:59.150> you<00:13:59.600> cannot<00:14:00.260> check 00:14:00.610 --> 00:14:00.620 align:start position:0% example of course you cannot check 00:14:00.620 --> 00:14:04.120 align:start position:0% example of course you cannot check directly<00:14:01.310> but<00:14:02.000> if<00:14:02.720> I<00:14:02.900> have<00:14:03.020> a<00:14:03.080> tool<00:14:03.290> or<00:14:03.320> if<00:14:03.980> a 00:14:04.120 --> 00:14:04.130 align:start position:0% directly but if I have a tool or if a 00:14:04.130 --> 00:14:05.920 align:start position:0% directly but if I have a tool or if a complete<00:14:04.520> hotel<00:14:05.000> there's<00:14:05.270> a<00:14:05.330> lot<00:14:05.450> of<00:14:05.540> products 00:14:05.920 --> 00:14:05.930 align:start position:0% complete hotel there's a lot of products 00:14:05.930 --> 00:14:09.310 align:start position:0% complete hotel there's a lot of products in<00:14:06.140> that<00:14:06.560> endless<00:14:06.830> construct<00:14:07.700> which<00:14:08.290> asks<00:14:09.290> the 00:14:09.310 --> 00:14:09.320 align:start position:0% in that endless construct which asks the 00:14:09.320 --> 00:14:11.710 align:start position:0% in that endless construct which asks the same<00:14:09.590> question<00:14:10.190> as<00:14:10.340> the<00:14:10.640> normal<00:14:10.940> rule<00:14:11.330> of<00:14:11.480> quiz 00:14:11.710 --> 00:14:11.720 align:start position:0% same question as the normal rule of quiz 00:14:11.720 --> 00:14:15.400 align:start position:0% same question as the normal rule of quiz tool<00:14:12.020> and<00:14:12.380> it<00:14:13.070> randomly<00:14:13.480> picks<00:14:14.480> north<00:14:14.870> network 00:14:15.400 --> 00:14:15.410 align:start position:0% tool and it randomly picks north network 00:14:15.410 --> 00:14:17.980 align:start position:0% tool and it randomly picks north network in<00:14:15.770> Austin<00:14:16.250> so<00:14:16.790> that<00:14:17.000> these<00:14:17.210> nodes<00:14:17.510> they<00:14:17.870> are 00:14:17.980 --> 00:14:17.990 align:start position:0% in Austin so that these nodes they are 00:14:17.990 --> 00:14:21.190 align:start position:0% in Austin so that these nodes they are do<00:14:18.650> not<00:14:18.800> know<00:14:18.980> if<00:14:19.160> this<00:14:19.400> the<00:14:20.270> state<00:14:20.570> line<00:14:20.900> which 00:14:21.190 --> 00:14:21.200 align:start position:0% do not know if this the state line which 00:14:21.200 --> 00:14:23.950 align:start position:0% do not know if this the state line which is<00:14:21.350> the<00:14:21.950> door<00:14:22.250> locked<00:14:22.280> I<00:14:22.730> thought<00:14:23.030> this<00:14:23.780> is<00:14:23.930> too 00:14:23.950 --> 00:14:23.960 align:start position:0% is the door locked I thought this is too 00:14:23.960 --> 00:14:26.430 align:start position:0% is the door locked I thought this is too strong 00:14:26.430 --> 00:14:26.440 align:start position:0% strong 00:14:26.440 --> 00:14:34.240 align:start position:0% strong yes<00:14:29.560> of<00:14:30.560> course<00:14:30.770> it's<00:14:31.610> not<00:14:31.820> free<00:14:33.130> it<00:14:34.130> would 00:14:34.240 --> 00:14:34.250 align:start position:0% yes of course it's not free it would 00:14:34.250 --> 00:14:39.270 align:start position:0% yes of course it's not free it would cost<00:14:34.550> me<00:14:34.870> something<00:14:35.870> to<00:14:36.290> make<00:14:36.650> this<00:14:37.550> request 00:14:39.270 --> 00:14:39.280 align:start position:0% cost me something to make this request 00:14:39.280 --> 00:14:43.620 align:start position:0% cost me something to make this request and<00:14:39.670> can<00:14:39.820> I<00:14:40.530> just<00:14:41.530> ask<00:14:41.830> the<00:14:42.610> same<00:14:42.880> question<00:14:43.450> of 00:14:43.620 --> 00:14:43.630 align:start position:0% and can I just ask the same question of 00:14:43.630 --> 00:14:47.790 align:start position:0% and can I just ask the same question of the<00:14:45.060> lifetime<00:14:46.060> of<00:14:46.330> it<00:14:46.630> which<00:14:46.930> is<00:14:47.110> kinda<00:14:47.620> past 00:14:47.790 --> 00:14:47.800 align:start position:0% the lifetime of it which is kinda past 00:14:47.800 --> 00:14:53.540 align:start position:0% the lifetime of it which is kinda past again<00:14:48.460> after<00:14:48.910> this<00:14:49.120> with<00:14:49.330> another<00:14:49.570> no<00:14:49.780> that<00:14:49.990> is 00:14:53.540 --> 00:14:53.550 align:start position:0% 00:14:53.550 --> 00:15:01.220 align:start position:0% if<00:14:54.550> I<00:14:55.060> could<00:14:55.690> do<00:14:55.810> this 00:15:01.220 --> 00:15:01.230 align:start position:0% 00:15:01.230 --> 00:15:04.369 align:start position:0% I<00:15:01.910> think<00:15:02.910> the<00:15:03.000> important<00:15:03.480> part<00:15:03.660> here<00:15:03.810> is<00:15:04.019> also 00:15:04.369 --> 00:15:04.379 align:start position:0% I think the important part here is also 00:15:04.379 --> 00:15:08.960 align:start position:0% I think the important part here is also that<00:15:06.110> again<00:15:07.110> what<00:15:07.889> would<00:15:08.370> it<00:15:08.490> comes<00:15:08.699> down<00:15:08.910> to 00:15:08.960 --> 00:15:08.970 align:start position:0% that again what would it comes down to 00:15:08.970 --> 00:15:10.759 align:start position:0% that again what would it comes down to it's<00:15:09.240> just<00:15:09.420> a<00:15:09.509> location<00:15:10.110> because<00:15:10.410> everything 00:15:10.759 --> 00:15:10.769 align:start position:0% it's just a location because everything 00:15:10.769 --> 00:15:13.579 align:start position:0% it's just a location because everything is<00:15:10.889> we<00:15:11.310> can<00:15:11.459> verify<00:15:12.139> locations<00:15:13.139> to<00:15:13.199> only 00:15:13.579 --> 00:15:13.589 align:start position:0% is we can verify locations to only 00:15:13.589 --> 00:15:15.639 align:start position:0% is we can verify locations to only information<00:15:14.040> we<00:15:14.910> can't<00:15:15.149> verify 00:15:15.639 --> 00:15:15.649 align:start position:0% information we can't verify 00:15:15.649 --> 00:15:18.470 align:start position:0% information we can't verify intrinsically<00:15:16.759> meaning<00:15:17.759> we<00:15:17.939> have<00:15:18.120> to<00:15:18.209> rely<00:15:18.449> on 00:15:18.470 --> 00:15:18.480 align:start position:0% intrinsically meaning we have to rely on 00:15:18.480 --> 00:15:20.569 align:start position:0% intrinsically meaning we have to rely on signatures<00:15:19.019> from<00:15:19.259> the<00:15:19.350> other<00:15:19.560> side<00:15:19.829> and 00:15:20.569 --> 00:15:20.579 align:start position:0% signatures from the other side and 00:15:20.579 --> 00:15:22.040 align:start position:0% signatures from the other side and that's<00:15:20.759> exactly<00:15:21.089> what<00:15:21.300> what<00:15:21.509> Chuck<00:15:21.720> is<00:15:21.810> doing 00:15:22.040 --> 00:15:22.050 align:start position:0% that's exactly what what Chuck is doing 00:15:22.050 --> 00:15:24.319 align:start position:0% that's exactly what what Chuck is doing is<00:15:22.319> just<00:15:22.709> checking<00:15:22.949> for<00:15:23.069> Rockets<00:15:23.790> because 00:15:24.319 --> 00:15:24.329 align:start position:0% is just checking for Rockets because 00:15:24.329 --> 00:15:26.629 align:start position:0% is just checking for Rockets because notate<00:15:25.139> and<00:15:25.379> see<00:15:25.589> how<00:15:25.709> all<00:15:25.949> these<00:15:26.069> signing<00:15:26.519> the 00:15:26.629 --> 00:15:26.639 align:start position:0% notate and see how all these signing the 00:15:26.639 --> 00:15:28.400 align:start position:0% notate and see how all these signing the rocket<00:15:27.060> you<00:15:27.300> don't<00:15:27.540> even<00:15:27.720> know<00:15:27.839> to<00:15:27.990> be<00:15:28.139> crest 00:15:28.400 --> 00:15:28.410 align:start position:0% rocket you don't even know to be crest 00:15:28.410 --> 00:15:30.769 align:start position:0% rocket you don't even know to be crest they<00:15:29.250> have<00:15:29.339> no<00:15:29.490> idea<00:15:29.790> what<00:15:29.939> it<00:15:30.089> they<00:15:30.269> have<00:15:30.420> this 00:15:30.769 --> 00:15:30.779 align:start position:0% they have no idea what it they have this 00:15:30.779 --> 00:15:33.559 align:start position:0% they have no idea what it they have this loop<00:15:31.410> is<00:15:31.620> simply<00:15:31.980> asking<00:15:32.129> please<00:15:32.639> sign<00:15:33.029> the 00:15:33.559 --> 00:15:33.569 align:start position:0% loop is simply asking please sign the 00:15:33.569 --> 00:15:37.249 align:start position:0% loop is simply asking please sign the block<00:15:33.839> number<00:15:34.050> X<00:15:34.529> and<00:15:35.569> what<00:15:36.569> shocking<00:15:36.959> make 00:15:37.249 --> 00:15:37.259 align:start position:0% block number X and what shocking make 00:15:37.259 --> 00:15:42.309 align:start position:0% block number X and what shocking make sure<00:15:37.589> that<00:15:38.009> he<00:15:38.129> will<00:15:38.250> never<00:15:38.430> sign<00:15:38.730> something 00:15:42.309 --> 00:15:42.319 align:start position:0% 00:15:42.319 --> 00:15:46.550 align:start position:0% publish<00:15:43.319> these<00:15:43.500> signatures<00:15:45.560> interactively 00:15:46.550 --> 00:15:46.560 align:start position:0% publish these signatures interactively 00:15:46.560 --> 00:15:48.590 align:start position:0% publish these signatures interactively to<00:15:46.740> because<00:15:47.220> they<00:15:47.339> send<00:15:47.579> in<00:15:47.670> transactions<00:15:48.180> on 00:15:48.590 --> 00:15:48.600 align:start position:0% to because they send in transactions on 00:15:48.600 --> 00:15:50.749 align:start position:0% to because they send in transactions on track<00:15:48.810> in<00:15:49.290> connect<00:15:49.680> them<00:15:49.889> or<00:15:50.220> they<00:15:50.399> do<00:15:50.550> that 00:15:50.749 --> 00:15:50.759 align:start position:0% track in connect them or they do that 00:15:50.759 --> 00:15:54.050 align:start position:0% track in connect them or they do that yeah<00:15:51.709> so<00:15:52.709> it<00:15:52.889> because<00:15:53.370> that's<00:15:53.519> why<00:15:53.790> you<00:15:53.850> use 00:15:54.050 --> 00:15:54.060 align:start position:0% yeah so it because that's why you use 00:15:54.060 --> 00:15:56.629 align:start position:0% yeah so it because that's why you use the<00:15:54.089> deficit<00:15:54.720> because<00:15:55.319> we<00:15:55.800> can<00:15:56.069> convict<00:15:56.490> them 00:15:56.629 --> 00:15:56.639 align:start position:0% the deficit because we can convict them 00:15:56.639 --> 00:16:00.290 align:start position:0% the deficit because we can convict them directly<00:15:57.120> on<00:15:57.779> chain<00:15:58.170> so<00:15:58.800> when<00:15:59.250> I<00:15:59.279> ask<00:15:59.579> you<00:15:59.939> time 00:16:00.290 --> 00:16:00.300 align:start position:0% directly on chain so when I ask you time 00:16:00.300 --> 00:16:02.119 align:start position:0% directly on chain so when I ask you time ask<00:16:00.629> me<00:16:01.410> to<00:16:01.680> ask 00:16:02.119 --> 00:16:02.129 align:start position:0% ask me to ask 00:16:02.129 --> 00:16:04.850 align:start position:0% ask me to ask AMC<00:16:03.120> and<00:16:03.600> what<00:16:03.750> they<00:16:03.870> actually<00:16:04.290> do<00:16:04.649> is<00:16:04.680> they 00:16:04.850 --> 00:16:04.860 align:start position:0% AMC and what they actually do is they 00:16:04.860 --> 00:16:07.550 align:start position:0% AMC and what they actually do is they will<00:16:05.130> sign<00:16:05.459> that<00:16:05.699> bar<00:16:05.910> cash<00:16:06.149> on<00:16:06.449> chain<00:16:06.839> rent 00:16:07.550 --> 00:16:07.560 align:start position:0% will sign that bar cash on chain rent 00:16:07.560 --> 00:16:10.519 align:start position:0% will sign that bar cash on chain rent because<00:16:08.130> obviously<00:16:08.490> note<00:16:09.089> B<00:16:09.300> cannot<00:16:09.779> take<00:16:10.199> the 00:16:10.519 --> 00:16:10.529 align:start position:0% because obviously note B cannot take the 00:16:10.529 --> 00:16:13.040 align:start position:0% because obviously note B cannot take the seepage<00:16:10.829> from<00:16:11.009> a<00:16:11.220> the<00:16:11.430> cement<00:16:11.790> that<00:16:11.930> to<00:16:12.930> my 00:16:13.040 --> 00:16:13.050 align:start position:0% seepage from a the cement that to my 00:16:13.050 --> 00:16:14.720 align:start position:0% seepage from a the cement that to my idea<00:16:13.350> for<00:16:13.649> what<00:16:13.800> the<00:16:13.829> box<00:16:13.949> like<00:16:14.250> that<00:16:14.310> work<00:16:14.579> at 00:16:14.720 --> 00:16:14.730 align:start position:0% idea for what the box like that work at 00:16:14.730 --> 00:16:18.790 align:start position:0% idea for what the box like that work at yeah<00:16:15.209> it's<00:16:15.509> a<00:16:15.630> doesn't<00:16:15.959> have<00:16:16.079> to<00:16:16.199> pay<00:16:16.380> it 00:16:18.790 --> 00:16:18.800 align:start position:0% 00:16:18.800 --> 00:16:25.370 align:start position:0% they<00:16:19.800> are<00:16:20.220> signing<00:16:20.640> of<00:16:20.760> the<00:16:24.260> deposit<00:16:25.260> on 00:16:25.370 --> 00:16:25.380 align:start position:0% they are signing of the deposit on 00:16:25.380 --> 00:16:27.140 align:start position:0% they are signing of the deposit on change<00:16:25.710> that<00:16:26.010> you<00:16:26.130> know<00:16:26.279> not<00:16:26.580> the<00:16:26.700> key<00:16:26.940> that 00:16:27.140 --> 00:16:27.150 align:start position:0% change that you know not the key that 00:16:27.150 --> 00:16:30.410 align:start position:0% change that you know not the key that you<00:16:27.240> know<00:16:27.420> the<00:16:28.400> statistic<00:16:29.400> EMSA<00:16:29.940> sights<00:16:30.210> on 00:16:30.410 --> 00:16:30.420 align:start position:0% you know the statistic EMSA sights on 00:16:30.420 --> 00:16:32.060 align:start position:0% you know the statistic EMSA sights on system<00:16:30.720> can<00:16:30.870> recover<00:16:31.200> and<00:16:31.560> recover<00:16:31.830> their 00:16:32.060 --> 00:16:32.070 align:start position:0% system can recover and recover their 00:16:32.070 --> 00:16:33.560 align:start position:0% system can recover and recover their property<00:16:32.400> and<00:16:32.640> you<00:16:32.850> know<00:16:33.000> that<00:16:33.180> it<00:16:33.270> is<00:16:33.330> for 00:16:33.560 --> 00:16:33.570 align:start position:0% property and you know that it is for 00:16:33.570 --> 00:16:38.390 align:start position:0% property and you know that it is for them<00:16:33.779> to<00:16:34.589> know<00:16:35.450> it<00:16:36.980> because<00:16:37.980> it<00:16:38.100> gives<00:16:38.220> us 00:16:38.390 --> 00:16:38.400 align:start position:0% them to know it because it gives us 00:16:38.400 --> 00:16:40.550 align:start position:0% them to know it because it gives us company<00:16:38.970> should<00:16:39.390> get<00:16:39.540> back<00:16:39.720> from<00:16:39.990> know<00:16:40.290> right 00:16:40.550 --> 00:16:40.560 align:start position:0% company should get back from know right 00:16:40.560 --> 00:16:42.290 align:start position:0% company should get back from know right like<00:16:40.710> you<00:16:40.890> just<00:16:41.100> take<00:16:41.310> a<00:16:41.520> signal<00:16:41.730> that<00:16:42.000> you<00:16:42.150> get 00:16:42.290 --> 00:16:42.300 align:start position:0% like you just take a signal that you get 00:16:42.300 --> 00:16:44.290 align:start position:0% like you just take a signal that you get back<00:16:42.510> because<00:16:42.660> it's<00:16:43.020> about<00:16:43.260> us<00:16:43.410> of<00:16:43.529> marketers 00:16:44.290 --> 00:16:44.300 align:start position:0% back because it's about us of marketers 00:16:44.300 --> 00:16:47.300 align:start position:0% back because it's about us of marketers you<00:16:45.300> know<00:16:45.420> if<00:16:45.870> you<00:16:46.020> get<00:16:46.200> from<00:16:46.440> the<00:16:46.620> be<00:16:46.890> the<00:16:47.130> top 00:16:47.300 --> 00:16:47.310 align:start position:0% you know if you get from the be the top 00:16:47.310 --> 00:17:00.730 align:start position:0% you know if you get from the be the top hitter<00:16:47.520> you<00:16:47.700> can<00:16:47.850> use<00:16:48.029> it 00:17:00.730 --> 00:17:00.740 align:start position:0% 00:17:00.740 --> 00:17:05.840 align:start position:0% I<00:17:02.450> mean<00:17:03.450> we<00:17:03.600> will<00:17:04.079> do<00:17:04.230> this<00:17:04.410> we<00:17:05.400> can<00:17:05.550> look<00:17:05.730> at 00:17:05.840 --> 00:17:05.850 align:start position:0% I mean we will do this we can look at 00:17:05.850 --> 00:17:08.210 align:start position:0% I mean we will do this we can look at the<00:17:05.970> proof<00:17:06.209> but<00:17:06.809> you<00:17:06.870> give<00:17:07.530> the<00:17:07.650> menu<00:17:07.890> look 00:17:08.210 --> 00:17:08.220 align:start position:0% the proof but you give the menu look 00:17:08.220 --> 00:17:10.100 align:start position:0% the proof but you give the menu look through<00:17:08.579> that<00:17:08.819> and<00:17:09.059> see<00:17:09.360> exactly<00:17:09.720> are<00:17:10.020> we 00:17:10.100 --> 00:17:10.110 align:start position:0% through that and see exactly are we 00:17:10.110 --> 00:17:12.559 align:start position:0% through that and see exactly are we doing<00:17:10.230> this<00:17:10.860> against<00:17:11.309> its<00:17:11.610> it<00:17:12.089> all<00:17:12.270> caps<00:17:12.480> out 00:17:12.559 --> 00:17:12.569 align:start position:0% doing this against its it all caps out 00:17:12.569 --> 00:17:14.990 align:start position:0% doing this against its it all caps out that<00:17:12.750> blockage<00:17:13.170> because<00:17:13.620> they<00:17:14.000> actually 00:17:14.990 --> 00:17:15.000 align:start position:0% that blockage because they actually 00:17:15.000 --> 00:17:18.079 align:start position:0% that blockage because they actually don't<00:17:15.270> even<00:17:15.780> provide<00:17:15.990> the<00:17:16.170> clock<00:17:16.470> and<00:17:17.459> by<00:17:18.030> the 00:17:18.079 --> 00:17:18.089 align:start position:0% don't even provide the clock and by the 00:17:18.089 --> 00:17:20.090 align:start position:0% don't even provide the clock and by the does<00:17:18.689> mean<00:17:18.929> anything<00:17:19.380> if<00:17:19.559> you 00:17:20.090 --> 00:17:20.100 align:start position:0% does mean anything if you 00:17:20.100 --> 00:17:22.280 align:start position:0% does mean anything if you even<00:17:20.340> the<00:17:20.430> truth<00:17:20.670> is<00:17:20.850> right<00:17:21.390> this<00:17:21.540> light<00:17:21.840> in 00:17:22.280 --> 00:17:22.290 align:start position:0% even the truth is right this light in 00:17:22.290 --> 00:17:31.010 align:start position:0% even the truth is right this light in see<00:17:22.650> me<00:17:23.160> to<00:17:23.220> silence<00:17:24.020> so<00:17:25.020> the<00:17:29.570> exact<00:17:30.570> result 00:17:31.010 --> 00:17:31.020 align:start position:0% see me to silence so the exact result 00:17:31.020 --> 00:17:34.850 align:start position:0% see me to silence so the exact result having<00:17:31.890> a<00:17:32.100> fix<00:17:32.580> for<00:17:33.030> again<00:17:33.330> old<00:17:33.750> so<00:17:34.440> in<00:17:34.740> the 00:17:34.850 --> 00:17:34.860 align:start position:0% having a fix for again old so in the 00:17:34.860 --> 00:17:38.240 align:start position:0% having a fix for again old so in the beginning<00:17:35.040> yes<00:17:35.490> it<00:17:36.350> was<00:17:37.350> in<00:17:37.500> this<00:17:37.680> line<00:17:37.920> after 00:17:38.240 --> 00:17:38.250 align:start position:0% beginning yes it was in this line after 00:17:38.250 --> 00:17:40.580 align:start position:0% beginning yes it was in this line after industry<00:17:38.670> today<00:17:39.300> in<00:17:39.690> the<00:17:39.810> first<00:17:40.050> instance 00:17:40.580 --> 00:17:40.590 align:start position:0% industry today in the first instance 00:17:40.590 --> 00:17:44.650 align:start position:0% industry today in the first instance constant<00:17:41.250> is<00:17:41.460> dead<00:17:42.390> polymers<00:17:43.230> and<00:17:44.070> then<00:17:44.430> he 00:17:44.650 --> 00:17:44.660 align:start position:0% constant is dead polymers and then he 00:17:44.660 --> 00:17:49.450 align:start position:0% constant is dead polymers and then he asked<00:17:45.660> his<00:17:46.200> apostles<00:17:46.680> from<00:17:47.460> the<00:17:47.580> list<00:17:47.790> if<00:17:48.690> he 00:17:49.450 --> 00:17:49.460 align:start position:0% asked his apostles from the list if he 00:17:49.460 --> 00:18:02.630 align:start position:0% asked his apostles from the list if he can<00:17:59.870> yeah<00:18:00.870> I<00:18:01.230> think<00:18:01.620> that's<00:18:01.890> why<00:18:02.010> a<00:18:02.220> good<00:18:02.400> as<00:18:02.610> a 00:18:02.630 --> 00:18:02.640 align:start position:0% can yeah I think that's why a good as a 00:18:02.640 --> 00:18:04.790 align:start position:0% can yeah I think that's why a good as a people<00:18:03.090> notes<00:18:03.330> is<00:18:03.630> even<00:18:04.050> if<00:18:04.170> you<00:18:04.320> started 00:18:04.790 --> 00:18:04.800 align:start position:0% people notes is even if you started 00:18:04.800 --> 00:18:06.770 align:start position:0% people notes is even if you started peridot<00:18:05.550> guess<00:18:05.820> today<00:18:06.120> there<00:18:06.450> are<00:18:06.600> some 00:18:06.770 --> 00:18:06.780 align:start position:0% peridot guess today there are some 00:18:06.780 --> 00:18:09.290 align:start position:0% peridot guess today there are some people<00:18:07.200> to<00:18:07.350> appear<00:18:07.710> so<00:18:07.920> you<00:18:08.010> start<00:18:08.310> with<00:18:08.370> but 00:18:09.290 --> 00:18:09.300 align:start position:0% people to appear so you start with but 00:18:09.300 --> 00:18:11.600 align:start position:0% people to appear so you start with but if<00:18:10.020> you<00:18:10.350> don't<00:18:10.680> trust<00:18:10.920> them<00:18:11.160> you<00:18:11.340> can 00:18:11.600 --> 00:18:11.610 align:start position:0% if you don't trust them you can 00:18:11.610 --> 00:18:16.520 align:start position:0% if you don't trust them you can configure<00:18:13.430> ok<00:18:14.430> so<00:18:14.910> now<00:18:15.090> so<00:18:15.480> we<00:18:15.600> discuss<00:18:16.050> that 00:18:16.520 --> 00:18:16.530 align:start position:0% configure ok so now so we discuss that 00:18:16.530 --> 00:18:20.600 align:start position:0% configure ok so now so we discuss that we<00:18:16.710> have<00:18:17.570> these<00:18:18.570> notes<00:18:18.780> they<00:18:19.250> give<00:18:20.250> us<00:18:20.430> the 00:18:20.600 --> 00:18:20.610 align:start position:0% we have these notes they give us the 00:18:20.610 --> 00:18:24.530 align:start position:0% we have these notes they give us the sign<00:18:20.820> information<00:18:21.780> if<00:18:22.500> they<00:18:22.740> are<00:18:22.860> from<00:18:23.420> if<00:18:24.420> the 00:18:24.530 --> 00:18:24.540 align:start position:0% sign information if they are from if the 00:18:24.540 --> 00:18:26.030 align:start position:0% sign information if they are from if the from<00:18:24.750> information<00:18:25.230> they<00:18:25.380> can<00:18:25.560> use<00:18:25.740> the 00:18:26.030 --> 00:18:26.040 align:start position:0% from information they can use the 00:18:26.040 --> 00:18:29.150 align:start position:0% from information they can use the deficit<00:18:26.660> so<00:18:27.660> there's<00:18:28.320> not<00:18:28.470> a<00:18:28.530> good<00:18:28.710> incentive 00:18:29.150 --> 00:18:29.160 align:start position:0% deficit so there's not a good incentive 00:18:29.160 --> 00:18:32.390 align:start position:0% deficit so there's not a good incentive for<00:18:30.030> people<00:18:30.210> to<00:18:30.360> run<00:18:30.630> such<00:18:30.840> notes<00:18:31.140> right<00:18:31.590> if<00:18:32.250> I 00:18:32.390 --> 00:18:32.400 align:start position:0% for people to run such notes right if I 00:18:32.400 --> 00:18:35.750 align:start position:0% for people to run such notes right if I if<00:18:32.700> only<00:18:32.970> thing<00:18:33.150> is<00:18:33.420> to<00:18:33.810> do<00:18:34.200> some<00:18:34.410> broke<00:18:34.680> and<00:18:35.010> do 00:18:35.750 --> 00:18:35.760 align:start position:0% if only thing is to do some broke and do 00:18:35.760 --> 00:18:37.940 align:start position:0% if only thing is to do some broke and do some<00:18:36.000> money<00:18:36.180> if<00:18:36.420> I<00:18:36.510> do<00:18:36.570> something<00:18:37.470> wrong<00:18:37.710> it's 00:18:37.940 --> 00:18:37.950 align:start position:0% some money if I do something wrong it's 00:18:37.950 --> 00:18:39.800 align:start position:0% some money if I do something wrong it's not<00:18:38.220> the<00:18:38.580> best<00:18:38.790> decision<00:18:38.970> to<00:18:39.420> run<00:18:39.540> such<00:18:39.780> a 00:18:39.800 --> 00:18:39.810 align:start position:0% not the best decision to run such a 00:18:39.810 --> 00:18:42.620 align:start position:0% not the best decision to run such a service<00:18:40.170> that's<00:18:40.740> when<00:18:41.010> we<00:18:41.490> also<00:18:41.670> build<00:18:42.390> an 00:18:42.620 --> 00:18:42.630 align:start position:0% service that's when we also build an 00:18:42.630 --> 00:18:45.590 align:start position:0% service that's when we also build an incentive<00:18:43.440> system<00:18:43.620> which<00:18:44.430> means<00:18:44.700> if<00:18:45.180> the 00:18:45.590 --> 00:18:45.600 align:start position:0% incentive system which means if the 00:18:45.600 --> 00:18:49.130 align:start position:0% incentive system which means if the client<00:18:46.170> asked<00:18:46.710> for<00:18:46.940> validators<00:18:48.140> information 00:18:49.130 --> 00:18:49.140 align:start position:0% client asked for validators information 00:18:49.140 --> 00:18:52.610 align:start position:0% client asked for validators information then<00:18:50.070> it<00:18:50.430> pays<00:18:50.940> a<00:18:51.300> very<00:18:51.780> small<00:18:52.080> amount<00:18:52.200> of 00:18:52.610 --> 00:18:52.620 align:start position:0% then it pays a very small amount of 00:18:52.620 --> 00:18:56.810 align:start position:0% then it pays a very small amount of money<00:18:52.800> to<00:18:53.190> these<00:18:54.030> nodes<00:18:54.300> for<00:18:55.610> getting<00:18:56.610> this 00:18:56.810 --> 00:18:56.820 align:start position:0% money to these nodes for getting this 00:18:56.820 --> 00:18:59.390 align:start position:0% money to these nodes for getting this information<00:18:57.170> this<00:18:58.170> edge<00:18:58.380> is<00:18:58.560> not<00:18:58.800> really<00:18:59.190> my 00:18:59.390 --> 00:18:59.400 align:start position:0% information this edge is not really my 00:18:59.400 --> 00:19:01.940 align:start position:0% information this edge is not really my cocaine<00:18:59.760> is<00:19:00.030> an<00:19:00.570> appearance<00:19:01.080> very<00:19:01.500> very<00:19:01.680> small 00:19:01.940 --> 00:19:01.950 align:start position:0% cocaine is an appearance very very small 00:19:01.950 --> 00:19:05.780 align:start position:0% cocaine is an appearance very very small amount<00:19:02.250> of<00:19:02.340> money<00:19:02.690> so<00:19:03.690> if<00:19:04.020> some<00:19:04.530> waters<00:19:05.160> so<00:19:05.760> I 00:19:05.780 --> 00:19:05.790 align:start position:0% amount of money so if some waters so I 00:19:05.790 --> 00:19:07.580 align:start position:0% amount of money so if some waters so I did<00:19:06.150> not 00:19:07.580 --> 00:19:07.590 align:start position:0% did not 00:19:07.590 --> 00:19:13.070 align:start position:0% did not detail<00:19:07.950> in<00:19:08.399> this<00:19:09.269> session<00:19:09.840> here<00:19:10.169> so<00:19:11.960> but<00:19:12.960> it 00:19:13.070 --> 00:19:13.080 align:start position:0% detail in this session here so but it 00:19:13.080 --> 00:19:16.700 align:start position:0% detail in this session here so but it originally<00:19:13.529> began<00:19:14.070> if<00:19:14.580> you<00:19:14.669> live<00:19:14.879> so<00:19:15.679> we<00:19:16.679> can 00:19:16.700 --> 00:19:16.710 align:start position:0% originally began if you live so we can 00:19:16.710 --> 00:19:19.369 align:start position:0% originally began if you live so we can do<00:19:17.399> some<00:19:17.759> different<00:19:18.090> incentive<00:19:18.899> a<00:19:18.960> shimada's 00:19:19.369 --> 00:19:19.379 align:start position:0% do some different incentive a shimada's 00:19:19.379 --> 00:19:21.200 align:start position:0% do some different incentive a shimada's could<00:19:19.620> be<00:19:19.799> a<00:19:19.879> infrastructure<00:19:20.879> ins<00:19:21.059> and 00:19:21.200 --> 00:19:21.210 align:start position:0% could be a infrastructure ins and 00:19:21.210 --> 00:19:23.869 align:start position:0% could be a infrastructure ins and division<00:19:21.720> being<00:19:22.230> given<00:19:22.710> reputation<00:19:23.580> for<00:19:23.789> as 00:19:23.869 --> 00:19:23.879 align:start position:0% division being given reputation for as 00:19:23.879 --> 00:19:26.389 align:start position:0% division being given reputation for as many<00:19:24.090> hood<00:19:24.360> or<00:19:24.870> it<00:19:25.019> can<00:19:25.289> be<00:19:25.440> monitoring<00:19:26.249> this 00:19:26.389 --> 00:19:26.399 align:start position:0% many hood or it can be monitoring this 00:19:26.399 --> 00:19:28.580 align:start position:0% many hood or it can be monitoring this innovation<00:19:26.940> that<00:19:27.059> we<00:19:27.480> give<00:19:27.899> such<00:19:28.200> a<00:19:28.230> viable 00:19:28.580 --> 00:19:28.590 align:start position:0% innovation that we give such a viable 00:19:28.590 --> 00:19:31.070 align:start position:0% innovation that we give such a viable payment<00:19:29.070> and<00:19:29.429> it's<00:19:29.789> this<00:19:30.090> system<00:19:30.299> we<00:19:31.049> can 00:19:31.070 --> 00:19:31.080 align:start position:0% payment and it's this system we can 00:19:31.080 --> 00:19:33.499 align:start position:0% payment and it's this system we can build<00:19:31.409> a<00:19:31.590> resistor<00:19:32.070> so<00:19:32.580> the<00:19:32.700> notes<00:19:32.970> they<00:19:33.240> run 00:19:33.499 --> 00:19:33.509 align:start position:0% build a resistor so the notes they run 00:19:33.509 --> 00:19:38.119 align:start position:0% build a resistor so the notes they run they<00:19:34.230> give<00:19:35.389> good<00:19:36.389> information<00:19:36.570> a<00:19:37.139> list<00:19:37.289> signed 00:19:38.119 --> 00:19:38.129 align:start position:0% they give good information a list signed 00:19:38.129 --> 00:19:42.220 align:start position:0% they give good information a list signed information<00:19:38.820> and<00:19:38.970> receive<00:19:39.779> some<00:19:40.139> money<00:19:40.559> in 00:19:42.220 --> 00:19:42.230 align:start position:0% information and receive some money in 00:19:42.230 --> 00:19:47.359 align:start position:0% information and receive some money in the<00:19:43.230> exchange<00:19:43.740> for<00:19:44.039> this<00:19:44.129> put<00:19:44.549> information<00:19:46.369> so 00:19:47.359 --> 00:19:47.369 align:start position:0% the exchange for this put information so 00:19:47.369 --> 00:19:49.369 align:start position:0% the exchange for this put information so as<00:19:47.490> I<00:19:47.519> said<00:19:47.789> the<00:19:47.940> beginning<00:19:48.330> it's<00:19:49.049> this 00:19:49.369 --> 00:19:49.379 align:start position:0% as I said the beginning it's this 00:19:49.379 --> 00:19:53.450 align:start position:0% as I said the beginning it's this clients<00:19:49.980> doesn't<00:19:50.639> meet<00:19:51.470> is<00:19:52.470> not<00:19:52.769> only<00:19:53.249> in 00:19:53.450 --> 00:19:53.460 align:start position:0% clients doesn't meet is not only in 00:19:53.460 --> 00:19:57.259 align:start position:0% clients doesn't meet is not only in between<00:19:53.779> talk<00:19:54.779> to<00:19:55.559> it<00:19:56.159> can<00:19:56.519> of<00:19:56.759> course<00:19:56.789> talk 00:19:57.259 --> 00:19:57.269 align:start position:0% between talk to it can of course talk 00:19:57.269 --> 00:19:59.840 align:start position:0% between talk to it can of course talk with<00:19:57.509> several<00:19:58.019> options<00:19:58.649> in<00:19:58.860> time<00:19:59.129> because 00:19:59.840 --> 00:19:59.850 align:start position:0% with several options in time because 00:19:59.850 --> 00:20:02.239 align:start position:0% with several options in time because this<00:20:00.149> kind<00:20:00.450> of<00:20:00.539> never<00:20:00.749> stores<00:20:01.259> some<00:20:01.649> stages 00:20:02.239 --> 00:20:02.249 align:start position:0% this kind of never stores some stages 00:20:02.249 --> 00:20:05.090 align:start position:0% this kind of never stores some stages not<00:20:02.490> supervised<00:20:03.029> so<00:20:03.779> we<00:20:03.869> have<00:20:04.049> to<00:20:04.110> say<00:20:04.289> ten 00:20:05.090 --> 00:20:05.100 align:start position:0% not supervised so we have to say ten 00:20:05.100 --> 00:20:08.539 align:start position:0% not supervised so we have to say ten reasons<00:20:05.460> to<00:20:05.820> talk<00:20:06.029> to<00:20:06.269> publicly<00:20:06.659> to<00:20:07.009> talk<00:20:08.009> to 00:20:08.539 --> 00:20:08.549 align:start position:0% reasons to talk to publicly to talk to 00:20:08.549 --> 00:20:11.480 align:start position:0% reasons to talk to publicly to talk to any<00:20:08.820> other<00:20:09.090> human<00:20:09.720> face<00:20:10.019> for<00:20:10.379> even<00:20:11.220> out<00:20:11.369> of 00:20:11.480 --> 00:20:11.490 align:start position:0% any other human face for even out of 00:20:11.490 --> 00:20:15.200 align:start position:0% any other human face for even out of jail<00:20:11.940> and<00:20:12.419> not<00:20:12.990> only<00:20:13.259> this<00:20:13.470> also<00:20:13.799> all<00:20:14.519> data 00:20:15.200 --> 00:20:15.210 align:start position:0% jail and not only this also all data 00:20:15.210 --> 00:20:17.720 align:start position:0% jail and not only this also all data services<00:20:15.990> which<00:20:16.350> can<00:20:16.619> give<00:20:17.190> us<00:20:17.220> a<00:20:17.340> proof<00:20:17.700> that 00:20:17.720 --> 00:20:17.730 align:start position:0% services which can give us a proof that 00:20:17.730 --> 00:20:20.389 align:start position:0% services which can give us a proof that the<00:20:18.179> information<00:20:18.779> sprites<00:20:19.110> can<00:20:19.409> be<00:20:19.919> concluded 00:20:20.389 --> 00:20:20.399 align:start position:0% the information sprites can be concluded 00:20:20.399 --> 00:20:28.369 align:start position:0% the information sprites can be concluded that<00:20:20.519> this<00:20:20.639> profile<00:20:21.119> is<00:20:21.389> this<00:20:21.690> idea<00:20:22.049> of<00:20:22.649> us<00:20:27.379> so 00:20:28.369 --> 00:20:28.379 align:start position:0% that this profile is this idea of us so 00:20:28.379 --> 00:20:31.100 align:start position:0% that this profile is this idea of us so as<00:20:28.950> I<00:20:29.190> said<00:20:29.399> we<00:20:29.909> have<00:20:30.119> different 00:20:31.100 --> 00:20:31.110 align:start position:0% as I said we have different 00:20:31.110 --> 00:20:34.190 align:start position:0% as I said we have different implementations<00:20:32.039> the<00:20:32.190> types<00:20:33.119> of<00:20:33.659> limitation 00:20:34.190 --> 00:20:34.200 align:start position:0% implementations the types of limitation 00:20:34.200 --> 00:20:36.379 align:start position:0% implementations the types of limitation which<00:20:34.350> is<00:20:34.529> good<00:20:34.799> to<00:20:35.220> be<00:20:35.340> included<00:20:35.759> in<00:20:35.909> websites 00:20:36.379 --> 00:20:36.389 align:start position:0% which is good to be included in websites 00:20:36.389 --> 00:20:39.560 align:start position:0% which is good to be included in websites or<00:20:36.899> mobile<00:20:37.200> applications<00:20:37.980> and<00:20:38.070> we<00:20:38.789> have<00:20:38.970> was<00:20:39.299> a 00:20:39.560 --> 00:20:39.570 align:start position:0% or mobile applications and we have was a 00:20:39.570 --> 00:20:41.899 align:start position:0% or mobile applications and we have was a see<00:20:39.779> implementation<00:20:40.499> which<00:20:40.919> is<00:20:40.950> small<00:20:41.789> enough 00:20:41.899 --> 00:20:41.909 align:start position:0% see implementation which is small enough 00:20:41.909 --> 00:20:45.739 align:start position:0% see implementation which is small enough to<00:20:42.360> run<00:20:42.809> it<00:20:42.960> on<00:20:43.200> such<00:20:43.860> money<00:20:44.159> and<00:20:44.909> instead<00:20:45.600> we 00:20:45.739 --> 00:20:45.749 align:start position:0% to run it on such money and instead we 00:20:45.749 --> 00:20:50.010 align:start position:0% to run it on such money and instead we have<00:20:45.950> several<00:20:46.950> implementations 00:20:50.010 --> 00:20:50.020 align:start position:0% 00:20:50.020 --> 00:20:53.840 align:start position:0% and<00:20:50.350> who<00:20:50.590> only<00:20:50.800> the<00:20:51.520> validation<00:20:52.420> of<00:20:52.540> that 00:20:53.840 --> 00:20:53.850 align:start position:0% and who only the validation of that 00:20:53.850 --> 00:20:57.600 align:start position:0% and who only the validation of that explosives<00:20:55.200> is<00:20:56.200> the<00:20:56.500> smallest<00:20:56.800> addition<00:20:57.190> and 00:20:57.600 --> 00:20:57.610 align:start position:0% explosives is the smallest addition and 00:20:57.610 --> 00:21:02.190 align:start position:0% explosives is the smallest addition and to<00:20:58.330> fully<00:20:58.600> to<00:20:58.870> find<00:20:59.230> its<00:20:59.740> own<00:21:00.370> EBM<00:21:01.210> and<00:21:01.480> can<00:21:02.020> do 00:21:02.190 --> 00:21:02.200 align:start position:0% to fully to find its own EBM and can do 00:21:02.200 --> 00:21:06.120 align:start position:0% to fully to find its own EBM and can do even<00:21:03.570> interactions<00:21:04.570> with<00:21:04.780> smart<00:21:05.620> contracts 00:21:06.120 --> 00:21:06.130 align:start position:0% even interactions with smart contracts 00:21:06.130 --> 00:21:08.460 align:start position:0% even interactions with smart contracts so<00:21:06.250> they<00:21:06.550> can<00:21:07.360> write<00:21:07.570> the<00:21:07.690> code<00:21:07.870> in<00:21:07.930> our<00:21:08.170> own 00:21:08.460 --> 00:21:08.470 align:start position:0% so they can write the code in our own 00:21:08.470 --> 00:21:13.910 align:start position:0% so they can write the code in our own ppm<00:21:10.590> okay<00:21:11.590> they<00:21:11.680> disappoint<00:21:12.360> under<00:21:13.360> some 00:21:13.910 --> 00:21:13.920 align:start position:0% ppm okay they disappoint under some 00:21:13.920 --> 00:21:18.200 align:start position:0% ppm okay they disappoint under some additional<00:21:14.920> questions 00:21:18.200 --> 00:21:18.210 align:start position:0% 00:21:18.210 --> 00:21:29.910 align:start position:0% so<00:21:25.380> this<00:21:26.380> RPC<00:21:26.710> request<00:21:27.510> you<00:21:28.510> can<00:21:28.750> ask<00:21:29.200> all<00:21:29.620> the 00:21:29.910 --> 00:21:29.920 align:start position:0% so this RPC request you can ask all the 00:21:29.920 --> 00:21:33.060 align:start position:0% so this RPC request you can ask all the opportunities<00:21:30.730> you<00:21:31.060> could<00:21:31.240> also<00:21:31.710> send<00:21:32.710> to<00:21:33.040> a 00:21:33.060 --> 00:21:33.070 align:start position:0% opportunities you could also send to a 00:21:33.070 --> 00:21:38.160 align:start position:0% opportunities you could also send to a warrant<00:21:33.940> so<00:21:34.630> basically<00:21:34.990> it's<00:21:35.200> like<00:21:35.290> yes<00:21:36.990> it<00:21:37.990> is 00:21:38.160 --> 00:21:38.170 align:start position:0% warrant so basically it's like yes it is 00:21:38.170 --> 00:21:40.130 align:start position:0% warrant so basically it's like yes it is the<00:21:38.260> same<00:21:38.410> option<00:21:38.770> additional<00:21:39.550> booster 00:21:40.130 --> 00:21:40.140 align:start position:0% the same option additional booster 00:21:40.140 --> 00:21:42.990 align:start position:0% the same option additional booster information<00:21:41.140> we<00:21:41.290> need<00:21:41.530> for<00:21:41.890> a<00:21:42.520> new<00:21:42.700> protocol 00:21:42.990 --> 00:21:43.000 align:start position:0% information we need for a new protocol 00:21:43.000 --> 00:21:45.930 align:start position:0% information we need for a new protocol means<00:21:43.570> today<00:21:44.170> by<00:21:44.440> a<00:21:44.470> professor<00:21:45.040> but<00:21:45.640> otherwise 00:21:45.930 --> 00:21:45.940 align:start position:0% means today by a professor but otherwise 00:21:45.940 --> 00:21:49.490 align:start position:0% means today by a professor but otherwise you<00:21:46.180> can<00:21:46.330> use<00:21:46.630> the<00:21:47.050> complete<00:21:47.500> obviously<00:21:48.310> this 00:21:49.490 --> 00:21:49.500 align:start position:0% you can use the complete obviously this 00:21:49.500 --> 00:21:53.640 align:start position:0% you can use the complete obviously this is<00:21:50.500> the<00:21:50.560> RPC<00:21:51.310> request<00:21:51.580> specific<00:21:52.150> to<00:21:52.810> your 00:21:53.640 --> 00:21:53.650 align:start position:0% is the RPC request specific to your 00:21:53.650 --> 00:21:57.170 align:start position:0% is the RPC request specific to your implementation<00:21:54.460> no<00:21:55.240> it's<00:21:56.170> exactly<00:21:56.410> the<00:21:56.950> same 00:21:57.170 --> 00:21:57.180 align:start position:0% implementation no it's exactly the same 00:21:57.180 --> 00:22:00.390 align:start position:0% implementation no it's exactly the same additional<00:21:58.180> parameter<00:21:58.440> is<00:21:59.440> just<00:21:59.740> one<00:22:00.010> it<00:22:00.250> is 00:22:00.390 --> 00:22:00.400 align:start position:0% additional parameter is just one it is 00:22:00.400 --> 00:22:03.810 align:start position:0% additional parameter is just one it is the<00:22:00.550> property<00:22:01.860> anything<00:22:02.860> else<00:22:03.040> is<00:22:03.220> just<00:22:03.250> same 00:22:03.810 --> 00:22:03.820 align:start position:0% the property anything else is just same 00:22:03.820 --> 00:22:06.660 align:start position:0% the property anything else is just same as<00:22:03.970> a<00:22:04.180> municipality<00:22:04.630> a<00:22:04.870> property<00:22:05.350> is<00:22:05.950> in<00:22:06.430> this 00:22:06.660 --> 00:22:06.670 align:start position:0% as a municipality a property is in this 00:22:06.670 --> 00:22:09.180 align:start position:0% as a municipality a property is in this request<00:22:07.480> it<00:22:07.960> defines<00:22:08.350> exactly<00:22:08.590> what<00:22:08.980> kind<00:22:09.160> of 00:22:09.180 --> 00:22:09.190 align:start position:0% request it defines exactly what kind of 00:22:09.190 --> 00:22:11.520 align:start position:0% request it defines exactly what kind of food<00:22:09.430> but<00:22:10.000> if<00:22:10.180> the<00:22:10.270> signatures<00:22:10.720> we<00:22:10.840> have<00:22:10.990> knows 00:22:11.520 --> 00:22:11.530 align:start position:0% food but if the signatures we have knows 00:22:11.530 --> 00:22:14.220 align:start position:0% food but if the signatures we have knows who<00:22:11.680> responds<00:22:12.160> contains<00:22:13.030> the<00:22:13.210> truth<00:22:13.420> but 00:22:14.220 --> 00:22:14.230 align:start position:0% who responds contains the truth but 00:22:14.230 --> 00:22:19.930 align:start position:0% who responds contains the truth but everything<00:22:14.860> else<00:22:15.010> exactly<00:22:15.610> the<00:22:15.730> same 00:22:19.930 --> 00:22:19.940 align:start position:0% 00:22:19.940 --> 00:22:22.460 align:start position:0% we<00:22:20.940> go<00:22:21.240> into<00:22:21.360> the<00:22:21.540> later<00:22:21.720> part<00:22:22.050> of<00:22:22.080> secession 00:22:22.460 --> 00:22:22.470 align:start position:0% we go into the later part of secession 00:22:22.470 --> 00:22:25.100 align:start position:0% we go into the later part of secession over<00:22:22.680> the<00:22:22.740> Occupy<00:22:23.460> us<00:22:23.640> give<00:22:24.150> me<00:22:24.360> the<00:22:24.660> head<00:22:24.900> we 00:22:25.100 --> 00:22:25.110 align:start position:0% over the Occupy us give me the head we 00:22:25.110 --> 00:22:27.560 align:start position:0% over the Occupy us give me the head we th<00:22:25.380> call<00:22:25.710> I<00:22:25.950> want<00:22:26.190> to<00:22:26.280> say<00:22:26.490> it's<00:22:27.030> upstate<00:22:27.420> from 00:22:27.560 --> 00:22:27.570 align:start position:0% th call I want to say it's upstate from 00:22:27.570 --> 00:22:30.980 align:start position:0% th call I want to say it's upstate from country<00:22:28.160> that<00:22:29.160> this<00:22:29.720> response<00:22:30.720> actually 00:22:30.980 --> 00:22:30.990 align:start position:0% country that this response actually 00:22:30.990 --> 00:22:33.140 align:start position:0% country that this response actually corresponds<00:22:31.710> to<00:22:31.800> the<00:22:32.040> real<00:22:32.190> estate<00:22:32.310> so<00:22:33.120> that 00:22:33.140 --> 00:22:33.150 align:start position:0% corresponds to the real estate so that 00:22:33.150 --> 00:22:34.820 align:start position:0% corresponds to the real estate so that does<00:22:33.450> have<00:22:33.600> about<00:22:33.930> the<00:22:34.110> exactly<00:22:34.650> these 00:22:34.820 --> 00:22:34.830 align:start position:0% does have about the exactly these 00:22:34.830 --> 00:22:36.890 align:start position:0% does have about the exactly these details<00:22:35.370> how<00:22:35.640> we<00:22:35.700> do<00:22:36.000> the<00:22:36.120> proof<00:22:36.390> because<00:22:36.660> it's 00:22:36.890 --> 00:22:36.900 align:start position:0% details how we do the proof because it's 00:22:36.900 --> 00:22:39.920 align:start position:0% details how we do the proof because it's an<00:22:37.140> very<00:22:37.290> interesting<00:22:37.980> thing<00:22:38.760> to<00:22:39.330> figure<00:22:39.810> out 00:22:39.920 --> 00:22:39.930 align:start position:0% an very interesting thing to figure out 00:22:39.930 --> 00:22:52.830 align:start position:0% an very interesting thing to figure out to<00:22:40.320> verify<00:22:40.770> each<00:22:41.070> detail<00:22:43.700> okay<00:22:48.560> otherwise 00:22:52.830 --> 00:22:52.840 align:start position:0% 00:22:52.840 --> 00:22:56.740 align:start position:0% [Music] 00:22:56.740 --> 00:22:56.750 align:start position:0% 00:22:56.750 --> 00:23:01.490 align:start position:0% necessity<00:22:57.750> being<00:22:58.380> a<00:22:58.530> factor<00:23:00.170> in<00:23:01.170> network 00:23:01.490 --> 00:23:01.500 align:start position:0% necessity being a factor in network 00:23:01.500 --> 00:23:03.560 align:start position:0% necessity being a factor in network really<00:23:01.740> how<00:23:02.340> many<00:23:02.550> of<00:23:02.700> the<00:23:02.820> actual<00:23:03.270> Hardware 00:23:03.560 --> 00:23:03.570 align:start position:0% really how many of the actual Hardware 00:23:03.570 --> 00:23:06.170 align:start position:0% really how many of the actual Hardware comedians<00:23:04.560> like<00:23:05.160> a<00:23:05.190> big<00:23:05.400> process<00:23:05.670> is<00:23:05.880> not 00:23:06.170 --> 00:23:06.180 align:start position:0% comedians like a big process is not 00:23:06.180 --> 00:23:09.650 align:start position:0% comedians like a big process is not wrong<00:23:06.800> you<00:23:07.800> mean<00:23:08.010> how<00:23:08.460> big<00:23:08.790> is<00:23:09.000> already<00:23:09.480> be<00:23:09.630> a 00:23:09.650 --> 00:23:09.660 align:start position:0% wrong you mean how big is already be a 00:23:09.660 --> 00:23:12.770 align:start position:0% wrong you mean how big is already be a more<00:23:10.110> direct<00:23:10.550> the<00:23:11.550> actual<00:23:11.850> deployments<00:23:12.510> was 00:23:12.770 --> 00:23:12.780 align:start position:0% more direct the actual deployments was 00:23:12.780 --> 00:23:14.990 align:start position:0% more direct the actual deployments was like<00:23:12.960> piece<00:23:13.500> of<00:23:13.740> hardware<00:23:14.130> like<00:23:14.280> how<00:23:14.640> many<00:23:14.700> I 00:23:14.990 --> 00:23:15.000 align:start position:0% like piece of hardware like how many I 00:23:15.000 --> 00:23:21.170 align:start position:0% like piece of hardware like how many I do<00:23:15.330> not<00:23:15.480> wanna<00:23:15.780> hear<00:23:16.910> so<00:23:19.340> it<00:23:20.340> depends<00:23:20.850> what<00:23:21.150> you 00:23:21.170 --> 00:23:21.180 align:start position:0% do not wanna hear so it depends what you 00:23:21.180 --> 00:23:23.270 align:start position:0% do not wanna hear so it depends what you want<00:23:21.510> to<00:23:21.660> do<00:23:21.810> with<00:23:21.960> this<00:23:22.110> type<00:23:22.380> of<00:23:22.410> course<00:23:22.770> so 00:23:23.270 --> 00:23:23.280 align:start position:0% want to do with this type of course so 00:23:23.280 --> 00:23:25.670 align:start position:0% want to do with this type of course so if<00:23:23.430> you<00:23:23.550> only<00:23:24.300> need<00:23:24.660> some<00:23:25.020> information<00:23:25.290> on 00:23:25.670 --> 00:23:25.680 align:start position:0% if you only need some information on 00:23:25.680 --> 00:23:28.700 align:start position:0% if you only need some information on approaching<00:23:26.250> you<00:23:26.850> don't<00:23:27.060> need<00:23:27.240> them<00:23:27.630> the<00:23:28.110> only 00:23:28.700 --> 00:23:28.710 align:start position:0% approaching you don't need them the only 00:23:28.710 --> 00:23:30.560 align:start position:0% approaching you don't need them the only meet<00:23:29.040> when<00:23:29.310> you<00:23:29.520> want<00:23:30.000> to<00:23:30.090> interact<00:23:30.420> with 00:23:30.560 --> 00:23:30.570 align:start position:0% meet when you want to interact with 00:23:30.570 --> 00:23:33.320 align:start position:0% meet when you want to interact with small<00:23:30.930> contracts<00:23:31.460> but<00:23:32.460> you<00:23:32.610> want<00:23:32.820> to<00:23:32.850> read<00:23:33.090> any 00:23:33.320 --> 00:23:33.330 align:start position:0% small contracts but you want to read any 00:23:33.330 --> 00:23:35.690 align:start position:0% small contracts but you want to read any storage<00:23:33.690> they<00:23:33.930> are<00:23:34.110> distortion<00:23:34.980> you<00:23:35.250> can<00:23:35.460> read 00:23:35.690 --> 00:23:35.700 align:start position:0% storage they are distortion you can read 00:23:35.700 --> 00:23:36.320 align:start position:0% storage they are distortion you can read without 00:23:36.320 --> 00:23:36.330 align:start position:0% without 00:23:36.330 --> 00:23:40.480 align:start position:0% without TVM<00:23:37.790> there's<00:23:38.790> no<00:23:38.970> API<00:23:39.150> for<00:23:39.690> that 00:23:40.480 --> 00:23:40.490 align:start position:0% TVM there's no API for that 00:23:40.490 --> 00:23:43.120 align:start position:0% TVM there's no API for that and<00:23:41.179> Paul<00:23:41.600> to<00:23:41.900> be<00:23:41.929> anything<00:23:42.500> and<00:23:42.770> they<00:23:42.980> have 00:23:43.120 --> 00:23:43.130 align:start position:0% and Paul to be anything and they have 00:23:43.130 --> 00:23:44.740 align:start position:0% and Paul to be anything and they have quite<00:23:43.370> how<00:23:43.610> I<00:23:43.640> know<00:23:43.850> it's<00:23:44.030> true<00:23:44.270> I<00:23:44.480> have<00:23:44.600> been 00:23:44.740 --> 00:23:44.750 align:start position:0% quite how I know it's true I have been 00:23:44.750 --> 00:23:46.630 align:start position:0% quite how I know it's true I have been in<00:23:44.870> the<00:23:44.960> enemy<00:23:45.230> right<00:23:45.559> exactly<00:23:46.309> that's<00:23:46.460> what 00:23:46.630 --> 00:23:46.640 align:start position:0% in the enemy right exactly that's what 00:23:46.640 --> 00:23:49.600 align:start position:0% in the enemy right exactly that's what if<00:23:47.030> we<00:23:47.150> have<00:23:47.300> to<00:23:47.420> EBM<00:23:47.690> implemented<00:23:48.410> but<00:23:49.309> of 00:23:49.600 --> 00:23:49.610 align:start position:0% if we have to EBM implemented but of 00:23:49.610 --> 00:23:51.220 align:start position:0% if we have to EBM implemented but of course<00:23:49.850> you<00:23:49.940> can<00:23:50.120> call<00:23:50.420> east<00:23:50.720> get<00:23:50.870> storage 00:23:51.220 --> 00:23:51.230 align:start position:0% course you can call east get storage 00:23:51.230 --> 00:23:55.930 align:start position:0% course you can call east get storage rent<00:23:51.440> if<00:23:52.250> you<00:23:52.370> know<00:23:52.520> what<00:23:52.670> yeah<00:23:53.860> but<00:23:54.860> in<00:23:55.190> for 00:23:55.930 --> 00:23:55.940 align:start position:0% rent if you know what yeah but in for 00:23:55.940 --> 00:23:57.850 align:start position:0% rent if you know what yeah but in for it's<00:23:56.270> called<00:23:56.570> that<00:23:56.900> was<00:23:57.170> the<00:23:57.320> reason<00:23:57.679> why<00:23:57.830> we 00:23:57.850 --> 00:23:57.860 align:start position:0% it's called that was the reason why we 00:23:57.860 --> 00:23:59.530 align:start position:0% it's called that was the reason why we started<00:23:58.160> implementing<00:23:58.820> the<00:23:58.970> whole<00:23:59.120> EBN 00:23:59.530 --> 00:23:59.540 align:start position:0% started implementing the whole EBN 00:23:59.540 --> 00:24:01.870 align:start position:0% started implementing the whole EBN because<00:23:59.840> the<00:24:00.020> only<00:24:00.170> way<00:24:00.410> to<00:24:00.470> verify<00:24:00.770> and<00:24:01.730> this 00:24:01.870 --> 00:24:01.880 align:start position:0% because the only way to verify and this 00:24:01.880 --> 00:24:03.910 align:start position:0% because the only way to verify and this is<00:24:02.000> correct<00:24:02.300> is<00:24:02.600> if<00:24:02.840> you<00:24:02.960> first<00:24:03.290> of<00:24:03.380> all<00:24:03.470> have 00:24:03.910 --> 00:24:03.920 align:start position:0% is correct is if you first of all have 00:24:03.920 --> 00:24:06.790 align:start position:0% is correct is if you first of all have all<00:24:04.220> the<00:24:04.340> storage<00:24:04.550> values<00:24:05.059> and<00:24:05.320> then<00:24:06.320> verify 00:24:06.790 --> 00:24:06.800 align:start position:0% all the storage values and then verify 00:24:06.800 --> 00:24:09.460 align:start position:0% all the storage values and then verify Hollywood<00:24:07.550> hotel<00:24:07.850> and<00:24:08.090> then<00:24:08.330> and<00:24:08.630> execute<00:24:09.410> the 00:24:09.460 --> 00:24:09.470 align:start position:0% Hollywood hotel and then and execute the 00:24:09.470 --> 00:24:11.470 align:start position:0% Hollywood hotel and then and execute the code<00:24:09.679> directly<00:24:10.250> inside<00:24:10.730> England<00:24:11.210> right<00:24:11.450> oh 00:24:11.470 --> 00:24:11.480 align:start position:0% code directly inside England right oh 00:24:11.480 --> 00:24:13.990 align:start position:0% code directly inside England right oh yeah<00:24:12.260> that<00:24:12.710> seems<00:24:12.920> very<00:24:13.010> happy<00:24:13.340> to<00:24:13.640> me<00:24:13.790> but<00:24:13.970> I 00:24:13.990 --> 00:24:14.000 align:start position:0% yeah that seems very happy to me but I 00:24:14.000 --> 00:24:16.060 align:start position:0% yeah that seems very happy to me but I don't<00:24:14.480> know<00:24:14.570> this<00:24:14.750> might<00:24:14.960> ask<00:24:15.200> you<00:24:15.440> it's<00:24:15.830> not 00:24:16.060 --> 00:24:16.070 align:start position:0% don't know this might ask you it's not 00:24:16.070 --> 00:24:17.790 align:start position:0% don't know this might ask you it's not happy<00:24:16.340> and<00:24:16.490> that<00:24:16.640> is<00:24:16.760> heavy<00:24:16.970> as<00:24:17.150> you<00:24:17.179> think 00:24:17.790 --> 00:24:17.800 align:start position:0% happy and that is heavy as you think 00:24:17.800 --> 00:24:21.970 align:start position:0% happy and that is heavy as you think because<00:24:18.800> at<00:24:19.550> least<00:24:19.790> this<00:24:20.210> chip<00:24:20.540> can<00:24:20.960> do<00:24:21.110> it<00:24:21.260> and 00:24:21.970 --> 00:24:21.980 align:start position:0% because at least this chip can do it and 00:24:21.980 --> 00:24:24.100 align:start position:0% because at least this chip can do it and if<00:24:22.100> this<00:24:22.400> chip<00:24:22.610> can<00:24:22.640> do<00:24:22.940> it<00:24:23.090> your<00:24:23.630> computer<00:24:23.809> can 00:24:24.100 --> 00:24:24.110 align:start position:0% if this chip can do it your computer can 00:24:24.110 --> 00:24:28.930 align:start position:0% if this chip can do it your computer can do<00:24:24.200> it<00:24:24.290> is<00:24:25.090> so<00:24:26.620> and<00:24:27.620> this<00:24:27.890> has<00:24:28.070> this<00:24:28.370> this<00:24:28.640> chip 00:24:28.930 --> 00:24:28.940 align:start position:0% do it is so and this has this this chip 00:24:28.940 --> 00:24:36.580 align:start position:0% do it is so and this has this this chip here<00:24:29.440> it<00:24:30.440> has<00:24:31.390> 256<00:24:32.390> kilobytes<00:24:34.840> are<00:24:35.840> you<00:24:36.080> that's 00:24:36.580 --> 00:24:36.590 align:start position:0% here it has 256 kilobytes are you that's 00:24:36.590 --> 00:24:39.250 align:start position:0% here it has 256 kilobytes are you that's an<00:24:36.800> F<00:24:37.220> and<00:24:37.610> not<00:24:37.760> accept<00:24:38.300> similar<00:24:38.660> diagram<00:24:39.080> and 00:24:39.250 --> 00:24:39.260 align:start position:0% an F and not accept similar diagram and 00:24:39.260 --> 00:24:43.090 align:start position:0% an F and not accept similar diagram and this<00:24:40.250> means<00:24:41.059> we're<00:24:41.990> one<00:24:42.230> thing<00:24:42.410> my<00:24:42.530> flash<00:24:42.830> and 00:24:43.090 --> 00:24:43.100 align:start position:0% this means we're one thing my flash and 00:24:43.100 --> 00:24:45.130 align:start position:0% this means we're one thing my flash and this<00:24:43.610> is<00:24:43.760> usually<00:24:43.940> the<00:24:44.240> biggest<00:24:44.750> limit 00:24:45.130 --> 00:24:45.140 align:start position:0% this is usually the biggest limit 00:24:45.140 --> 00:24:48.520 align:start position:0% this is usually the biggest limit tomorrow<00:24:45.559> and<00:24:46.130> you<00:24:46.940> know<00:24:47.240> that's<00:24:47.690> why<00:24:47.870> the 00:24:48.520 --> 00:24:48.530 align:start position:0% tomorrow and you know that's why the 00:24:48.530 --> 00:24:51.370 align:start position:0% tomorrow and you know that's why the biggest<00:24:48.740> issue<00:24:49.070> is<00:24:49.340> getting<00:24:50.000> the<00:24:50.150> code<00:24:50.450> inside 00:24:51.370 --> 00:24:51.380 align:start position:0% biggest issue is getting the code inside 00:24:51.380 --> 00:24:53.440 align:start position:0% biggest issue is getting the code inside the<00:24:51.440> revenues<00:24:51.890> because<00:24:52.640> we<00:24:52.820> need<00:24:52.970> it<00:24:53.090> down<00:24:53.270> as 00:24:53.440 --> 00:24:53.450 align:start position:0% the revenues because we need it down as 00:24:53.450 --> 00:24:54.970 align:start position:0% the revenues because we need it down as a<00:24:53.480> code<00:24:53.720> from<00:24:53.929> the<00:24:54.080> small<00:24:54.320> country<00:24:54.679> before<00:24:54.800> you 00:24:54.970 --> 00:24:54.980 align:start position:0% a code from the small country before you 00:24:54.980 --> 00:24:56.770 align:start position:0% a code from the small country before you execute<00:24:55.220> it<00:24:55.520> so<00:24:55.820> if<00:24:56.210> you<00:24:56.270> have<00:24:56.360> a<00:24:56.450> huge 00:24:56.770 --> 00:24:56.780 align:start position:0% execute it so if you have a huge 00:24:56.780 --> 00:25:03.529 align:start position:0% execute it so if you have a huge contract<00:24:57.620> you<00:24:57.800> might<00:24:57.980> have<00:24:58.130> issue 00:25:03.529 --> 00:25:03.539 align:start position:0% 00:25:03.539 --> 00:25:07.859 align:start position:0% okay<00:25:04.539> okay<00:25:05.039> no<00:25:06.039> no<00:25:06.549> sighs<00:25:07.239> see<00:25:07.450> what<00:25:07.479> time<00:25:07.839> it 00:25:07.859 --> 00:25:07.869 align:start position:0% okay okay no no sighs see what time it 00:25:07.869 --> 00:25:24.419 align:start position:0% okay okay no no sighs see what time it can<00:25:08.139> take<00:25:08.379> over<00:25:16.049> okay<00:25:18.719> okay<00:25:22.649> okay<00:25:23.679> this<00:25:24.279> is 00:25:24.419 --> 00:25:24.429 align:start position:0% can take over okay okay okay this is 00:25:24.429 --> 00:25:27.749 align:start position:0% can take over okay okay okay this is myself<00:25:24.580> and<00:25:25.029> Simon<00:25:25.719> and<00:25:26.589> the<00:25:26.739> c2<00:25:27.129> from<00:25:27.669> the 00:25:27.749 --> 00:25:27.759 align:start position:0% myself and Simon and the c2 from the 00:25:27.759 --> 00:25:31.409 align:start position:0% myself and Simon and the c2 from the socket<00:25:27.940> and<00:25:29.399> especially<00:25:30.399> for<00:25:30.789> the<00:25:30.909> into 00:25:31.409 --> 00:25:31.419 align:start position:0% socket and especially for the into 00:25:31.419 --> 00:25:34.289 align:start position:0% socket and especially for the into protract<00:25:31.960> and<00:25:32.229> then<00:25:32.519> also<00:25:33.519> delete<00:25:33.820> that<00:25:33.999> so<00:25:34.269> a 00:25:34.289 --> 00:25:34.299 align:start position:0% protract and then also delete that so a 00:25:34.299 --> 00:25:35.999 align:start position:0% protract and then also delete that so a lot<00:25:34.539> of<00:25:34.570> code<00:25:34.839> of<00:25:35.049> the<00:25:35.139> code<00:25:35.349> was<00:25:35.589> written<00:25:35.769> back 00:25:35.999 --> 00:25:36.009 align:start position:0% lot of code of the code was written back 00:25:36.009 --> 00:25:41.749 align:start position:0% lot of code of the code was written back and<00:25:36.779> it's<00:25:37.779> white<00:25:38.019> on<00:25:38.049> a<00:25:38.289> piece<00:25:38.799> of<00:25:39.299> magnet<00:25:40.299> so 00:25:41.749 --> 00:25:41.759 align:start position:0% and it's white on a piece of magnet so 00:25:41.759 --> 00:25:46.669 align:start position:0% and it's white on a piece of magnet so in<00:25:42.759> order<00:25:42.879> to<00:25:42.999> get<00:25:43.210> prepared<00:25:43.659> for<00:25:44.109> that<00:25:44.289> I 00:25:46.669 --> 00:25:46.679 align:start position:0% 00:25:46.679 --> 00:25:49.649 align:start position:0% wanted<00:25:47.679> one<00:25:48.070> in<00:25:48.099> actual<00:25:49.029> code<00:25:49.210> somethig 00:25:49.649 --> 00:25:49.659 align:start position:0% wanted one in actual code somethig 00:25:49.659 --> 00:25:51.769 align:start position:0% wanted one in actual code somethig because<00:25:49.960> they<00:25:50.080> only<00:25:50.320> wanted<00:25:50.619> to<00:25:50.710> re-enter 00:25:51.769 --> 00:25:51.779 align:start position:0% because they only wanted to re-enter 00:25:51.779 --> 00:25:54.329 align:start position:0% because they only wanted to re-enter this<00:25:52.779> is<00:25:52.929> the<00:25:53.019> token<00:25:53.229> image<00:25:53.559> this<00:25:54.070> is<00:25:54.309> a 00:25:54.329 --> 00:25:54.339 align:start position:0% this is the token image this is a 00:25:54.339 --> 00:25:57.060 align:start position:0% this is the token image this is a similar<00:25:55.019> image<00:25:56.019> has<00:25:56.259> all<00:25:56.469> the<00:25:56.589> food<00:25:56.830> chain 00:25:57.060 --> 00:25:57.070 align:start position:0% similar image has all the food chain 00:25:57.070 --> 00:25:58.889 align:start position:0% similar image has all the food chain that<00:25:57.099> you<00:25:57.279> need<00:25:57.549> through<00:25:58.210> two<00:25:58.450> mains<00:25:58.690> to 00:25:58.889 --> 00:25:58.899 align:start position:0% that you need through two mains to 00:25:58.899 --> 00:26:03.570 align:start position:0% that you need through two mains to compile<00:25:59.259> some<00:25:59.289> C<00:26:00.129> code<00:26:00.339> to<00:26:00.700> each<00:26:01.509> other<00:26:01.719> but<00:26:02.649> no 00:26:03.570 --> 00:26:03.580 align:start position:0% compile some C code to each other but no 00:26:03.580 --> 00:26:07.499 align:start position:0% compile some C code to each other but no java<00:26:03.999> code<00:26:05.159> if<00:26:06.159> you<00:26:06.249> want<00:26:06.369> you<00:26:06.519> can<00:26:06.669> already<00:26:06.999> or 00:26:07.499 --> 00:26:07.509 align:start position:0% java code if you want you can already or 00:26:07.509 --> 00:26:11.099 align:start position:0% java code if you want you can already or not<00:26:07.539> you<00:26:08.379> can<00:26:08.529> also<00:26:08.649> take<00:26:08.919> this<00:26:09.580> beast<00:26:10.109> exclude 00:26:11.099 --> 00:26:11.109 align:start position:0% not you can also take this beast exclude 00:26:11.109 --> 00:26:15.989 align:start position:0% not you can also take this beast exclude too<00:26:11.409> much<00:26:11.589> to<00:26:11.830> download<00:26:14.279> because<00:26:15.279> all<00:26:15.820> the 00:26:15.989 --> 00:26:15.999 align:start position:0% too much to download because all the 00:26:15.999 --> 00:26:18.209 align:start position:0% too much to download because all the things<00:26:16.239> I<00:26:16.389> will<00:26:16.539> show<00:26:16.570> I<00:26:16.929> will<00:26:17.080> just<00:26:17.289> call<00:26:17.950> talk 00:26:18.209 --> 00:26:18.219 align:start position:0% things I will show I will just call talk 00:26:18.219 --> 00:26:19.769 align:start position:0% things I will show I will just call talk a<00:26:18.309> run<00:26:18.460> and<00:26:18.700> use<00:26:19.210> the<00:26:19.359> same<00:26:19.570> type<00:26:19.749> of 00:26:19.769 --> 00:26:19.779 align:start position:0% a run and use the same type of 00:26:19.779 --> 00:26:21.919 align:start position:0% a run and use the same type of containers<00:26:20.349> away<00:26:20.649> as<00:26:20.710> the<00:26:20.889> same<00:26:21.070> environment 00:26:21.919 --> 00:26:21.929 align:start position:0% containers away as the same environment 00:26:21.929 --> 00:26:24.570 align:start position:0% containers away as the same environment we<00:26:22.929> don't<00:26:22.960> have<00:26:23.320> to<00:26:23.499> figure<00:26:23.679> out<00:26:23.799> why 00:26:24.570 --> 00:26:24.580 align:start position:0% we don't have to figure out why 00:26:24.580 --> 00:26:30.020 align:start position:0% we don't have to figure out why something<00:26:24.940> does<00:26:25.239> it's<00:26:25.450> done 00:26:30.020 --> 00:26:30.030 align:start position:0% 00:26:30.030 --> 00:26:32.810 align:start position:0% okay 00:26:32.810 --> 00:26:32.820 align:start position:0% 00:26:32.820 --> 00:26:35.330 align:start position:0% [Music] 00:26:35.330 --> 00:26:35.340 align:start position:0% [Music] 00:26:35.340 --> 00:26:38.220 align:start position:0% [Music] attached<00:26:35.730> anymore--<00:26:36.179> put<00:26:36.600> a<00:26:36.779> capital<00:26:37.110> buddy 00:26:38.220 --> 00:26:38.230 align:start position:0% attached anymore-- put a capital buddy 00:26:38.230 --> 00:26:46.300 align:start position:0% attached anymore-- put a capital buddy [Music] 00:26:46.300 --> 00:26:46.310 align:start position:0% [Music] 00:26:46.310 --> 00:26:48.650 align:start position:0% [Music] anybody<00:26:47.310> else 00:26:48.650 --> 00:26:48.660 align:start position:0% anybody else 00:26:48.660 --> 00:26:55.270 align:start position:0% anybody else okay 00:26:55.270 --> 00:26:55.280 align:start position:0% 00:26:55.280 --> 00:26:57.960 align:start position:0% [Music] 00:26:57.960 --> 00:26:57.970 align:start position:0% [Music] 00:26:57.970 --> 00:27:01.590 align:start position:0% [Music] ky<00:26:58.660> you're<00:26:58.870> downloading<00:26:59.620> some<00:27:00.400> imagery<00:27:00.910> and<00:27:01.510> I 00:27:01.590 --> 00:27:01.600 align:start position:0% ky you're downloading some imagery and I 00:27:01.600 --> 00:27:06.210 align:start position:0% ky you're downloading some imagery and I would<00:27:01.720> like<00:27:01.870> to<00:27:01.960> give<00:27:02.140> a<00:27:02.230> short<00:27:02.440> overview<00:27:05.220> also 00:27:06.210 --> 00:27:06.220 align:start position:0% would like to give a short overview also 00:27:06.220 --> 00:27:11.610 align:start position:0% would like to give a short overview also nice<00:27:09.000> because<00:27:10.000> we<00:27:10.630> need<00:27:10.750> to<00:27:10.840> give<00:27:10.990> you<00:27:11.080> where 00:27:11.610 --> 00:27:11.620 align:start position:0% nice because we need to give you where 00:27:11.620 --> 00:27:14.310 align:start position:0% nice because we need to give you where are<00:27:11.800> we<00:27:11.890> standing<00:27:12.100> today<00:27:12.870> just<00:27:13.870> a<00:27:13.960> few<00:27:14.140> weeks 00:27:14.310 --> 00:27:14.320 align:start position:0% are we standing today just a few weeks 00:27:14.320 --> 00:27:16.980 align:start position:0% are we standing today just a few weeks ago<00:27:14.500> what<00:27:15.010> we<00:27:15.130> did<00:27:15.310> this<00:27:15.490> VM<00:27:15.910> prepare<00:27:16.810> the 00:27:16.980 --> 00:27:16.990 align:start position:0% ago what we did this VM prepare the 00:27:16.990 --> 00:27:19.410 align:start position:0% ago what we did this VM prepare the googlies<00:27:17.410> candidate<00:27:17.830> one<00:27:18.060> set<00:27:19.060> of<00:27:19.150> final 00:27:19.410 --> 00:27:19.420 align:start position:0% googlies candidate one set of final 00:27:19.420 --> 00:27:21.060 align:start position:0% googlies candidate one set of final release<00:27:19.720> yet<00:27:19.960> because<00:27:20.560> we<00:27:20.710> went<00:27:20.890> to<00:27:21.040> a 00:27:21.060 --> 00:27:21.070 align:start position:0% release yet because we went to a 00:27:21.070 --> 00:27:23.190 align:start position:0% release yet because we went to a security<00:27:21.430> audit<00:27:21.670> and<00:27:22.150> this<00:27:22.480> video<00:27:22.810> is<00:27:22.960> not 00:27:23.190 --> 00:27:23.200 align:start position:0% security audit and this video is not 00:27:23.200 --> 00:27:25.740 align:start position:0% security audit and this video is not finished<00:27:23.560> yet<00:27:23.860> I<00:27:24.130> mean<00:27:24.490> that's<00:27:24.670> why<00:27:24.820> we<00:27:25.540> cannot 00:27:25.740 --> 00:27:25.750 align:start position:0% finished yet I mean that's why we cannot 00:27:25.750 --> 00:27:27.180 align:start position:0% finished yet I mean that's why we cannot have<00:27:26.140> been<00:27:26.260> productive<00:27:26.530> release<00:27:27.010> the 00:27:27.180 --> 00:27:27.190 align:start position:0% have been productive release the 00:27:27.190 --> 00:27:30.060 align:start position:0% have been productive release the students<00:27:27.580> finish<00:27:28.050> but<00:27:29.050> we<00:27:29.140> already<00:27:29.290> published 00:27:30.060 --> 00:27:30.070 align:start position:0% students finish but we already published 00:27:30.070 --> 00:27:33.330 align:start position:0% students finish but we already published everything<00:27:30.820> so<00:27:31.600> it's<00:27:31.780> ready<00:27:32.440> to<00:27:32.560> be<00:27:32.740> used<00:27:32.770> to 00:27:33.330 --> 00:27:33.340 align:start position:0% everything so it's ready to be used to 00:27:33.340 --> 00:27:35.640 align:start position:0% everything so it's ready to be used to be<00:27:33.430> tested<00:27:33.880> and<00:27:34.120> we<00:27:34.450> also<00:27:34.690> would<00:27:35.320> like<00:27:35.500> to 00:27:35.640 --> 00:27:35.650 align:start position:0% be tested and we also would like to 00:27:35.650 --> 00:27:38.580 align:start position:0% be tested and we also would like to invite<00:27:35.860> you<00:27:35.920> to<00:27:36.100> do<00:27:36.340> this<00:27:36.520> to<00:27:37.000> test<00:27:37.720> it<00:27:37.900> out<00:27:37.990> try 00:27:38.580 --> 00:27:38.590 align:start position:0% invite you to do this to test it out try 00:27:38.590 --> 00:27:41.130 align:start position:0% invite you to do this to test it out try it<00:27:38.650> out<00:27:38.800> to<00:27:39.370> see<00:27:39.550> how<00:27:39.700> it<00:27:39.760> works<00:27:40.000> for<00:27:40.120> you<00:27:40.210> what 00:27:41.130 --> 00:27:41.140 align:start position:0% it out to see how it works for you what 00:27:41.140 --> 00:27:43.560 align:start position:0% it out to see how it works for you what we<00:27:41.350> have<00:27:41.560> here<00:27:41.590> is<00:27:42.250> if<00:27:42.940> you<00:27:43.090> want<00:27:43.270> to<00:27:43.360> go<00:27:43.450> and 00:27:43.560 --> 00:27:43.570 align:start position:0% we have here is if you want to go and 00:27:43.570 --> 00:27:45.960 align:start position:0% we have here is if you want to go and get<00:27:43.780> hot<00:27:44.310> you<00:27:45.310> will<00:27:45.460> see<00:27:45.640> a<00:27:45.670> lot<00:27:45.940> of 00:27:45.960 --> 00:27:45.970 align:start position:0% get hot you will see a lot of 00:27:45.970 --> 00:27:47.910 align:start position:0% get hot you will see a lot of repositories<00:27:46.750> I<00:27:47.020> just<00:27:47.350> want<00:27:47.470> to<00:27:47.560> show<00:27:47.740> they 00:27:47.910 --> 00:27:47.920 align:start position:0% repositories I just want to show they 00:27:47.920 --> 00:27:50.010 align:start position:0% repositories I just want to show they explain<00:27:48.250> them<00:27:48.400> with<00:27:48.520> what<00:27:49.150> you<00:27:49.480> can<00:27:49.690> expect 00:27:50.010 --> 00:27:50.020 align:start position:0% explain them with what you can expect 00:27:50.020 --> 00:27:53.100 align:start position:0% explain them with what you can expect when<00:27:50.200> you<00:27:50.260> can<00:27:50.470> see<00:27:50.650> that<00:27:51.420> the<00:27:52.420> first<00:27:52.600> thing<00:27:52.870> is 00:27:53.100 --> 00:27:53.110 align:start position:0% when you can see that the first thing is 00:27:53.110 --> 00:27:54.840 align:start position:0% when you can see that the first thing is as<00:27:53.410> the<00:27:53.980> step<00:27:54.190> mentioned<00:27:54.580> we<00:27:54.640> have<00:27:54.730> two 00:27:54.840 --> 00:27:54.850 align:start position:0% as the step mentioned we have two 00:27:54.850 --> 00:27:56.880 align:start position:0% as the step mentioned we have two fermentation<00:27:55.690> the<00:27:56.470> typescript 00:27:56.880 --> 00:27:56.890 align:start position:0% fermentation the typescript 00:27:56.890 --> 00:27:59.310 align:start position:0% fermentation the typescript implementation<00:27:57.700> is<00:27:57.820> was<00:27:58.570> the<00:27:58.750> first<00:27:58.990> one<00:27:59.230> we 00:27:59.310 --> 00:27:59.320 align:start position:0% implementation is was the first one we 00:27:59.320 --> 00:28:01.800 align:start position:0% implementation is was the first one we did<00:27:59.460> actually<00:28:00.460> empowered<00:28:00.970> a<00:28:01.180> little<00:28:01.570> bit<00:28:01.690> over 00:28:01.800 --> 00:28:01.810 align:start position:0% did actually empowered a little bit over 00:28:01.810 --> 00:28:03.450 align:start position:0% did actually empowered a little bit over a<00:28:01.900> year<00:28:01.930> ago<00:28:02.350> this<00:28:02.530> time<00:28:02.590> of<00:28:02.920> the<00:28:03.040> tax<00:28:03.250> code 00:28:03.450 --> 00:28:03.460 align:start position:0% a year ago this time of the tax code 00:28:03.460 --> 00:28:05.490 align:start position:0% a year ago this time of the tax code first<00:28:04.180> and<00:28:04.450> more<00:28:04.600> like<00:28:04.870> a<00:28:04.900> feasibility<00:28:05.320> study 00:28:05.490 --> 00:28:05.500 align:start position:0% first and more like a feasibility study 00:28:05.500 --> 00:28:09.060 align:start position:0% first and more like a feasibility study can<00:28:06.010> we<00:28:06.220> really<00:28:06.610> verify<00:28:07.300> everything<00:28:07.660> and<00:28:08.230> we 00:28:09.060 --> 00:28:09.070 align:start position:0% can we really verify everything and we 00:28:09.070 --> 00:28:11.130 align:start position:0% can we really verify everything and we can<00:28:09.280> that's<00:28:09.640> why<00:28:09.820> that<00:28:09.940> okay<00:28:10.210> looks<00:28:10.660> great<00:28:10.930> the 00:28:11.130 --> 00:28:11.140 align:start position:0% can that's why that okay looks great the 00:28:11.140 --> 00:28:12.960 align:start position:0% can that's why that okay looks great the times<00:28:11.380> good<00:28:11.620> but<00:28:11.830> of<00:28:12.070> course<00:28:12.280> statute<00:28:12.730> itself 00:28:12.960 --> 00:28:12.970 align:start position:0% times good but of course statute itself 00:28:12.970 --> 00:28:14.610 align:start position:0% times good but of course statute itself and<00:28:13.120> around<00:28:13.450> the<00:28:13.630> bike<00:28:13.810> controllers<00:28:14.380> that's 00:28:14.610 --> 00:28:14.620 align:start position:0% and around the bike controllers that's 00:28:14.620 --> 00:28:16.890 align:start position:0% and around the bike controllers that's why<00:28:14.800> we<00:28:14.950> said<00:28:15.130> we<00:28:15.910> need<00:28:16.090> a<00:28:16.300> special 00:28:16.890 --> 00:28:16.900 align:start position:0% why we said we need a special 00:28:16.900 --> 00:28:18.960 align:start position:0% why we said we need a special implementation<00:28:17.650> for<00:28:18.100> the<00:28:18.190> microcontrollers 00:28:18.960 --> 00:28:18.970 align:start position:0% implementation for the microcontrollers 00:28:18.970 --> 00:28:22.500 align:start position:0% implementation for the microcontrollers and<00:28:20.160> of<00:28:21.160> course<00:28:21.430> we<00:28:21.550> thought<00:28:21.700> about<00:28:21.850> how<00:28:22.060> what 00:28:22.500 --> 00:28:22.510 align:start position:0% and of course we thought about how what 00:28:22.510 --> 00:28:23.850 align:start position:0% and of course we thought about how what what<00:28:22.750> kind<00:28:22.960> of<00:28:22.990> language<00:28:23.140> are<00:28:23.380> we<00:28:23.410> gonna<00:28:23.620> use 00:28:23.850 --> 00:28:23.860 align:start position:0% what kind of language are we gonna use 00:28:23.860 --> 00:28:26.730 align:start position:0% what kind of language are we gonna use it<00:28:24.090> would<00:28:25.090> I<00:28:25.270> would<00:28:25.600> have<00:28:25.690> loved<00:28:25.930> to<00:28:25.960> use<00:28:26.200> brass 00:28:26.730 --> 00:28:26.740 align:start position:0% it would I would have loved to use brass 00:28:26.740 --> 00:28:29.580 align:start position:0% it would I would have loved to use brass for<00:28:27.010> something<00:28:27.370> but<00:28:28.270> if<00:28:28.390> you<00:28:28.510> look<00:28:28.840> at<00:28:29.110> the 00:28:29.580 --> 00:28:29.590 align:start position:0% for something but if you look at the 00:28:29.590 --> 00:28:31.410 align:start position:0% for something but if you look at the industry<00:28:29.920> today<00:28:30.100> all<00:28:30.670> the<00:28:30.970> people<00:28:31.240> that<00:28:31.360> are 00:28:31.410 --> 00:28:31.420 align:start position:0% industry today all the people that are 00:28:31.420 --> 00:28:35.049 align:start position:0% industry today all the people that are building<00:28:32.410> stuff<00:28:32.830> on<00:28:33.040> my<00:28:33.280> an<00:28:33.640> IOT<00:28:34.030> device 00:28:35.049 --> 00:28:35.059 align:start position:0% building stuff on my an IOT device 00:28:35.059 --> 00:28:38.019 align:start position:0% building stuff on my an IOT device control<00:28:35.629> of<00:28:35.860> all<00:28:36.860> the<00:28:37.100> two<00:28:37.279> trains<00:28:37.639> and<00:28:37.909> all 00:28:38.019 --> 00:28:38.029 align:start position:0% control of all the two trains and all 00:28:38.029 --> 00:28:39.700 align:start position:0% control of all the two trains and all the<00:28:38.179> merriment<00:28:38.419> is<00:28:38.720> written<00:28:39.019> for<00:28:39.110> see<00:28:39.289> if<00:28:39.559> you 00:28:39.700 --> 00:28:39.710 align:start position:0% the merriment is written for see if you 00:28:39.710 --> 00:28:41.409 align:start position:0% the merriment is written for see if you write<00:28:39.919> something<00:28:39.950> in<00:28:40.370> C<00:28:40.580> it<00:28:40.789> will<00:28:40.999> light<00:28:41.240> them 00:28:41.409 --> 00:28:41.419 align:start position:0% write something in C it will light them 00:28:41.419 --> 00:28:44.739 align:start position:0% write something in C it will light them about<00:28:41.690> that's<00:28:42.350> why<00:28:42.879> as<00:28:43.879> well<00:28:44.090> so<00:28:44.330> we<00:28:44.419> did<00:28:44.570> some 00:28:44.739 --> 00:28:44.749 align:start position:0% about that's why as well so we did some 00:28:44.749 --> 00:28:47.649 align:start position:0% about that's why as well so we did some tests<00:28:45.139> you<00:28:45.649> can<00:28:45.860> get<00:28:46.039> very<00:28:46.399> very<00:28:46.759> small<00:28:47.269> binary 00:28:47.649 --> 00:28:47.659 align:start position:0% tests you can get very very small binary 00:28:47.659 --> 00:28:50.919 align:start position:0% tests you can get very very small binary service<00:28:48.110> so<00:28:49.039> so<00:28:49.999> that's<00:28:50.269> how<00:28:50.389> we<00:28:50.509> did<00:28:50.659> it<00:28:50.749> after 00:28:50.919 --> 00:28:50.929 align:start position:0% service so so that's how we did it after 00:28:50.929 --> 00:28:53.139 align:start position:0% service so so that's how we did it after implementing<00:28:51.559> the<00:28:52.399> whole<00:28:52.549> thing<00:28:52.759> in<00:28:52.850> C<00:28:53.029> as 00:28:53.139 --> 00:28:53.149 align:start position:0% implementing the whole thing in C as 00:28:53.149 --> 00:28:54.159 align:start position:0% implementing the whole thing in C as well<00:28:53.299> that's<00:28:53.509> alright<00:28:53.720> that's<00:28:53.899> one 00:28:54.159 --> 00:28:54.169 align:start position:0% well that's alright that's one 00:28:54.169 --> 00:28:58.029 align:start position:0% well that's alright that's one repository<00:28:54.470> it's<00:28:55.279> just<00:28:55.580> a<00:28:55.820> three<00:28:56.710> it<00:28:57.710> should 00:28:58.029 --> 00:28:58.039 align:start position:0% repository it's just a three it should 00:28:58.039 --> 00:29:00.489 align:start position:0% repository it's just a three it should have<00:28:58.190> been<00:28:58.429> called<00:28:58.669> iDream<00:28:59.210> minus<00:28:59.749> TS<00:29:00.200> because 00:29:00.489 --> 00:29:00.499 align:start position:0% have been called iDream minus TS because 00:29:00.499 --> 00:29:03.369 align:start position:0% have been called iDream minus TS because actually<00:29:00.830> that's<00:29:01.249> good<00:29:01.549> but<00:29:02.110> first<00:29:03.110> we<00:29:03.289> will 00:29:03.369 --> 00:29:03.379 align:start position:0% actually that's good but first we will 00:29:03.379 --> 00:29:05.680 align:start position:0% actually that's good but first we will be<00:29:03.440> set<00:29:03.679> up<00:29:03.710> in<00:29:03.860> his<00:29:03.980> name<00:29:04.149> and<00:29:05.149> we<00:29:05.389> have<00:29:05.419> this 00:29:05.680 --> 00:29:05.690 align:start position:0% be set up in his name and we have this 00:29:05.690 --> 00:29:07.480 align:start position:0% be set up in his name and we have this item<00:29:05.960> minus<00:29:06.499> C<00:29:06.710> which<00:29:07.070> is<00:29:07.190> the<00:29:07.309> same 00:29:07.480 --> 00:29:07.490 align:start position:0% item minus C which is the same 00:29:07.490 --> 00:29:09.279 align:start position:0% item minus C which is the same limitation<00:29:08.179> that's<00:29:08.659> why<00:29:08.869> between 00:29:09.279 --> 00:29:09.289 align:start position:0% limitation that's why between 00:29:09.289 --> 00:29:12.039 align:start position:0% limitation that's why between repositories<00:29:10.179> and<00:29:11.179> of<00:29:11.450> course<00:29:11.690> that's<00:29:11.809> what 00:29:12.039 --> 00:29:12.049 align:start position:0% repositories and of course that's what 00:29:12.049 --> 00:29:13.720 align:start position:0% repositories and of course that's what we<00:29:12.080> postulate<00:29:12.529> that<00:29:12.769> this<00:29:12.950> that<00:29:13.490> will 00:29:13.720 --> 00:29:13.730 align:start position:0% we postulate that this that will 00:29:13.730 --> 00:29:16.090 align:start position:0% we postulate that this that will represent<00:29:13.970> this<00:29:14.360> node<00:29:14.570> then<00:29:15.289> we<00:29:15.320> talked<00:29:15.980> about 00:29:16.090 --> 00:29:16.100 align:start position:0% represent this node then we talked about 00:29:16.100 --> 00:29:18.759 align:start position:0% represent this node then we talked about these<00:29:16.340> notes<00:29:16.580> it<00:29:16.730> will<00:29:16.850> provide<00:29:17.360> clues<00:29:17.779> this 00:29:18.759 --> 00:29:18.769 align:start position:0% these notes it will provide clues this 00:29:18.769 --> 00:29:21.820 align:start position:0% these notes it will provide clues this time<00:29:19.070> three<00:29:19.279> months<00:29:19.399> story<00:29:20.019> this<00:29:21.019> is<00:29:21.080> what<00:29:21.740> we 00:29:21.820 --> 00:29:21.830 align:start position:0% time three months story this is what we 00:29:21.830 --> 00:29:23.739 align:start position:0% time three months story this is what we connector<00:29:22.340> and<00:29:22.970> then<00:29:23.090> we<00:29:23.269> have<00:29:23.360> two<00:29:23.570> other 00:29:23.739 --> 00:29:23.749 align:start position:0% connector and then we have two other 00:29:23.749 --> 00:29:25.810 align:start position:0% connector and then we have two other repositories<00:29:24.350> the<00:29:25.100> common<00:29:25.399> is<00:29:25.490> more<00:29:25.669> like 00:29:25.810 --> 00:29:25.820 align:start position:0% repositories the common is more like 00:29:25.820 --> 00:29:28.810 align:start position:0% repositories the common is more like youth<00:29:25.999> utils<00:29:26.659> and<00:29:26.960> default<00:29:27.919> configurations 00:29:28.810 --> 00:29:28.820 align:start position:0% youth utils and default configurations 00:29:28.820 --> 00:29:30.609 align:start position:0% youth utils and default configurations of<00:29:28.909> the<00:29:29.029> default<00:29:29.419> lowest<00:29:29.840> who<00:29:30.169> don't<00:29:30.440> are 00:29:30.609 --> 00:29:30.619 align:start position:0% of the default lowest who don't are 00:29:30.619 --> 00:29:34.359 align:start position:0% of the default lowest who don't are configure<00:29:31.369> there<00:29:31.899> and<00:29:32.899> I<00:29:33.499> think<00:29:33.769> contracts 00:29:34.359 --> 00:29:34.369 align:start position:0% configure there and I think contracts 00:29:34.369 --> 00:29:36.310 align:start position:0% configure there and I think contracts this<00:29:34.639> is<00:29:34.789> just<00:29:35.119> on<00:29:35.419> the<00:29:35.539> closet<00:29:35.749> or<00:29:36.049> rather 00:29:36.310 --> 00:29:36.320 align:start position:0% this is just on the closet or rather 00:29:36.320 --> 00:29:38.019 align:start position:0% this is just on the closet or rather than<00:29:36.559> all<00:29:36.769> this<00:29:36.950> mother<00:29:37.190> comment<00:29:37.580> it's<00:29:37.789> not 00:29:38.019 --> 00:29:38.029 align:start position:0% than all this mother comment it's not 00:29:38.029 --> 00:29:40.419 align:start position:0% than all this mother comment it's not they<00:29:38.600> are<00:29:38.659> just<00:29:39.019> actually<00:29:39.860> two<00:29:40.159> small 00:29:40.419 --> 00:29:40.429 align:start position:0% they are just actually two small 00:29:40.429 --> 00:29:43.629 align:start position:0% they are just actually two small contracts<00:29:40.970> we<00:29:41.720> do<00:29:41.929> all<00:29:42.080> the<00:29:42.200> work<00:29:42.460> but<00:29:43.460> of 00:29:43.629 --> 00:29:43.639 align:start position:0% contracts we do all the work but of 00:29:43.639 --> 00:29:46.869 align:start position:0% contracts we do all the work but of course<00:29:43.879> they<00:29:43.999> are<00:29:44.029> very<00:29:44.269> crucial<00:29:45.700> with<00:29:46.700> all 00:29:46.869 --> 00:29:46.879 align:start position:0% course they are very crucial with all 00:29:46.879 --> 00:29:50.519 align:start position:0% course they are very crucial with all the<00:29:46.999> tests<00:29:47.799> so<00:29:48.799> this<00:29:49.100> is<00:29:49.220> the<00:29:49.309> common<00:29:49.580> github 00:29:50.519 --> 00:29:50.529 align:start position:0% the tests so this is the common github 00:29:50.529 --> 00:29:53.889 align:start position:0% the tests so this is the common github we<00:29:51.529> have<00:29:51.649> to<00:29:51.980> toughen<00:29:52.429> images<00:29:52.850> published<00:29:53.059> this 00:29:53.889 --> 00:29:53.899 align:start position:0% we have to toughen images published this 00:29:53.899 --> 00:29:57.310 align:start position:0% we have to toughen images published this one<00:29:54.230> is<00:29:54.470> into<00:29:55.249> client<00:29:55.730> itself<00:29:55.999> so<00:29:56.990> if<00:29:57.139> you 00:29:57.310 --> 00:29:57.320 align:start position:0% one is into client itself so if you 00:29:57.320 --> 00:29:59.019 align:start position:0% one is into client itself so if you don't<00:29:57.499> want<00:29:57.679> to<00:29:57.769> install<00:29:58.070> it<00:29:58.279> you<00:29:58.549> can<00:29:58.700> run<00:29:58.879> the 00:29:59.019 --> 00:29:59.029 align:start position:0% don't want to install it you can run the 00:29:59.029 --> 00:30:01.239 align:start position:0% don't want to install it you can run the into<00:29:59.240> plan<00:29:59.480> directly<00:29:59.840> as<00:30:00.590> a<00:30:00.649> toggle<00:30:00.950> run 00:30:01.239 --> 00:30:01.249 align:start position:0% into plan directly as a toggle run 00:30:01.249 --> 00:30:04.869 align:start position:0% into plan directly as a toggle run command<00:30:02.029> and<00:30:03.100> this<00:30:04.100> is<00:30:04.249> sometimes<00:30:04.580> very 00:30:04.869 --> 00:30:04.879 align:start position:0% command and this is sometimes very 00:30:04.879 --> 00:30:06.909 align:start position:0% command and this is sometimes very helpful<00:30:05.450> if<00:30:05.659> you<00:30:05.840> want<00:30:05.990> to<00:30:06.200> replace<00:30:06.590> a<00:30:06.649> light 00:30:06.909 --> 00:30:06.919 align:start position:0% helpful if you want to replace a light 00:30:06.919 --> 00:30:08.740 align:start position:0% helpful if you want to replace a light client<00:30:07.309> for<00:30:07.460> example<00:30:07.519> you<00:30:07.970> can 00:30:08.740 --> 00:30:08.750 align:start position:0% client for example you can 00:30:08.750 --> 00:30:13.090 align:start position:0% client for example you can run<00:30:10.030> commander<00:30:11.030> Zhou<00:30:11.570> Popovich<00:30:12.020> and<00:30:12.230> this 00:30:13.090 --> 00:30:13.100 align:start position:0% run commander Zhou Popovich and this 00:30:13.100 --> 00:30:14.800 align:start position:0% run commander Zhou Popovich and this will<00:30:13.280> open<00:30:13.430> up<00:30:13.640> the<00:30:13.850> chest<00:30:14.000> obviously<00:30:14.450> ports 00:30:14.800 --> 00:30:14.810 align:start position:0% will open up the chest obviously ports 00:30:14.810 --> 00:30:17.200 align:start position:0% will open up the chest obviously ports in<00:30:14.990> every<00:30:15.200> weakness<00:30:15.500> that<00:30:15.680> comes<00:30:15.890> into<00:30:16.070> it<00:30:16.280> if 00:30:17.200 --> 00:30:17.210 align:start position:0% in every weakness that comes into it if 00:30:17.210 --> 00:30:19.870 align:start position:0% in every weakness that comes into it if you<00:30:17.390> will<00:30:17.660> then<00:30:17.870> you<00:30:18.280> communicate<00:30:19.280> with<00:30:19.760> all 00:30:19.870 --> 00:30:19.880 align:start position:0% you will then you communicate with all 00:30:19.880 --> 00:30:22.870 align:start position:0% you will then you communicate with all the<00:30:19.970> words<00:30:20.150> so<00:30:20.590> it<00:30:21.590> can<00:30:21.800> replace<00:30:22.250> that<00:30:22.280> running 00:30:22.870 --> 00:30:22.880 align:start position:0% the words so it can replace that running 00:30:22.880 --> 00:30:25.060 align:start position:0% the words so it can replace that running client<00:30:23.270> and<00:30:23.570> of<00:30:24.290> course<00:30:24.500> the<00:30:24.590> other<00:30:24.680> one<00:30:24.890> is 00:30:25.060 --> 00:30:25.070 align:start position:0% client and of course the other one is 00:30:25.070 --> 00:30:27.100 align:start position:0% client and of course the other one is there<00:30:25.280> and<00:30:25.640> we<00:30:25.910> load<00:30:26.090> which<00:30:26.300> list<00:30:26.540> and<00:30:26.750> one 00:30:27.100 --> 00:30:27.110 align:start position:0% there and we load which list and one 00:30:27.110 --> 00:30:29.320 align:start position:0% there and we load which list and one point<00:30:27.710> is<00:30:27.890> not<00:30:28.070> this<00:30:28.460> is<00:30:28.580> also<00:30:28.730> what<00:30:29.000> you<00:30:29.030> can 00:30:29.320 --> 00:30:29.330 align:start position:0% point is not this is also what you can 00:30:29.330 --> 00:30:31.660 align:start position:0% point is not this is also what you can talk<00:30:29.810> about<00:30:29.870> later<00:30:30.380> how<00:30:30.710> you<00:30:30.770> say<00:30:31.160> you<00:30:31.520> know 00:30:31.660 --> 00:30:31.670 align:start position:0% talk about later how you say you know 00:30:31.670 --> 00:30:35.169 align:start position:0% talk about later how you say you know you<00:30:31.970> should<00:30:32.300> run 00:30:35.169 --> 00:30:35.179 align:start position:0% 00:30:35.179 --> 00:30:38.560 align:start position:0% and<00:30:36.179> then<00:30:36.330> of<00:30:36.450> course<00:30:36.480> was<00:30:37.140> presented<00:30:37.740> for<00:30:37.770> the 00:30:38.560 --> 00:30:38.570 align:start position:0% and then of course was presented for the 00:30:38.570 --> 00:30:42.020 align:start position:0% and then of course was presented for the typescript<00:30:40.370> JavaScript<00:30:41.370> we<00:30:41.610> have<00:30:41.760> something 00:30:42.020 --> 00:30:42.030 align:start position:0% typescript JavaScript we have something 00:30:42.030 --> 00:30:44.810 align:start position:0% typescript JavaScript we have something epic<00:30:42.299> address<00:30:42.809> we<00:30:43.260> have<00:30:43.350> the<00:30:43.470> most<00:30:44.309> important 00:30:44.810 --> 00:30:44.820 align:start position:0% epic address we have the most important 00:30:44.820 --> 00:30:49.640 align:start position:0% epic address we have the most important ones<00:30:44.970> in<00:30:45.240> the<00:30:45.360> plan<00:30:45.660> itself<00:30:46.940> the<00:30:47.940> target<00:30:48.650> for 00:30:49.640 --> 00:30:49.650 align:start position:0% ones in the plan itself the target for 00:30:49.650 --> 00:30:53.600 align:start position:0% ones in the plan itself the target for the<00:30:49.710> C<00:30:50.010> version<00:30:50.360> we<00:30:51.360> also<00:30:51.900> compiled<00:30:52.830> to<00:30:53.100> Bosman 00:30:53.600 --> 00:30:53.610 align:start position:0% the C version we also compiled to Bosman 00:30:53.610 --> 00:30:58.340 align:start position:0% the C version we also compiled to Bosman this<00:30:54.539> what<00:30:54.720> we<00:30:54.870> are<00:30:54.900> the<00:30:55.080> second 00:30:58.340 --> 00:30:58.350 align:start position:0% 00:30:58.350 --> 00:31:00.890 align:start position:0% and<00:30:59.280> the<00:30:59.490> moment<00:30:59.760> it's<00:30:59.880> experimental<00:31:00.450> at<00:31:00.780> the 00:31:00.890 --> 00:31:00.900 align:start position:0% and the moment it's experimental at the 00:31:00.900 --> 00:31:03.830 align:start position:0% and the moment it's experimental at the system<00:31:01.320> book<00:31:01.440> very<00:31:01.710> nicely<00:31:02.430> and<00:31:02.850> they<00:31:03.630> keep 00:31:03.830 --> 00:31:03.840 align:start position:0% system book very nicely and they keep 00:31:03.840 --> 00:31:05.960 align:start position:0% system book very nicely and they keep cool<00:31:04.500> to<00:31:04.650> see<00:31:04.860> if<00:31:04.920> you<00:31:05.040> come<00:31:05.250> at<00:31:05.430> them<00:31:05.580> I<00:31:05.790> mean 00:31:05.960 --> 00:31:05.970 align:start position:0% cool to see if you come at them I mean 00:31:05.970 --> 00:31:09.920 align:start position:0% cool to see if you come at them I mean even<00:31:06.240> will<00:31:06.480> bring<00:31:07.440> the<00:31:07.530> same<00:31:07.680> result<00:31:08.100> but<00:31:08.970> this 00:31:09.920 --> 00:31:09.930 align:start position:0% even will bring the same result but this 00:31:09.930 --> 00:31:12.560 align:start position:0% even will bring the same result but this one<00:31:10.230> the<00:31:10.770> tax<00:31:11.040> conversion<00:31:11.580> has<00:31:11.760> only<00:31:11.940> took<00:31:12.360> the 00:31:12.560 --> 00:31:12.570 align:start position:0% one the tax conversion has only took the 00:31:12.570 --> 00:31:14.720 align:start position:0% one the tax conversion has only took the dependencies<00:31:13.140> that<00:31:13.170> you<00:31:13.320> all<00:31:13.560> know<00:31:13.740> and<00:31:14.520> well 00:31:14.720 --> 00:31:14.730 align:start position:0% dependencies that you all know and well 00:31:14.730 --> 00:31:17.150 align:start position:0% dependencies that you all know and well then<00:31:15.200> tha<00:31:16.200> has<00:31:16.350> libraries<00:31:16.800> and<00:31:16.980> all<00:31:17.040> this 00:31:17.150 --> 00:31:17.160 align:start position:0% then tha has libraries and all this 00:31:17.160 --> 00:31:19.820 align:start position:0% then tha has libraries and all this stuff<00:31:17.250> and<00:31:18.410> usually<00:31:19.410> gave<00:31:19.530> a<00:31:19.560> lot<00:31:19.800> of 00:31:19.820 --> 00:31:19.830 align:start position:0% stuff and usually gave a lot of 00:31:19.830 --> 00:31:23.420 align:start position:0% stuff and usually gave a lot of different<00:31:20.490> modules<00:31:21.030> so<00:31:21.960> if<00:31:22.200> you<00:31:22.350> package<00:31:23.160> it 00:31:23.420 --> 00:31:23.430 align:start position:0% different modules so if you package it 00:31:23.430 --> 00:31:26.680 align:start position:0% different modules so if you package it comes<00:31:23.820> down<00:31:24.060> to<00:31:24.300> the<00:31:24.360> size<00:31:24.570> but<00:31:24.990> two<00:31:25.590> megabyte 00:31:26.680 --> 00:31:26.690 align:start position:0% comes down to the size but two megabyte 00:31:26.690 --> 00:31:28.970 align:start position:0% comes down to the size but two megabyte you<00:31:27.690> can<00:31:27.810> look<00:31:27.930> at<00:31:28.050> it<00:31:28.140> Boston<00:31:28.530> the<00:31:28.830> Boston 00:31:28.970 --> 00:31:28.980 align:start position:0% you can look at it Boston the Boston 00:31:28.980 --> 00:31:33.610 align:start position:0% you can look at it Boston the Boston planet<00:31:29.490> is<00:31:29.670> about<00:31:30.590> 170<00:31:31.590> kilo<00:31:31.890> byte<00:31:32.220> and 00:31:33.610 --> 00:31:33.620 align:start position:0% planet is about 170 kilo byte and 00:31:33.620 --> 00:31:37.310 align:start position:0% planet is about 170 kilo byte and everything<00:31:34.620> in<00:31:34.770> them<00:31:34.950> completely<00:31:35.550> VM<00:31:36.090> and<00:31:36.420> all 00:31:37.310 --> 00:31:37.320 align:start position:0% everything in them completely VM and all 00:31:37.320 --> 00:31:40.400 align:start position:0% everything in them completely VM and all the<00:31:37.530> stuff<00:31:37.740> in<00:31:37.920> his<00:31:38.100> no<00:31:38.370> dependency<00:31:39.000> at<00:31:39.090> all<00:31:39.410> so 00:31:40.400 --> 00:31:40.410 align:start position:0% the stuff in his no dependency at all so 00:31:40.410 --> 00:31:41.930 align:start position:0% the stuff in his no dependency at all so which<00:31:40.560> is<00:31:40.680> pretty<00:31:40.890> cool<00:31:41.130> aspect<00:31:41.520> was<00:31:41.700> from<00:31:41.910> a 00:31:41.930 --> 00:31:41.940 align:start position:0% which is pretty cool aspect was from a 00:31:41.940 --> 00:31:44.000 align:start position:0% which is pretty cool aspect was from a security<00:31:42.360> point<00:31:42.630> of<00:31:42.780> view<00:31:42.840> if<00:31:43.650> you<00:31:43.770> think 00:31:44.000 --> 00:31:44.010 align:start position:0% security point of view if you think 00:31:44.010 --> 00:31:47.330 align:start position:0% security point of view if you think about<00:31:44.100> it<00:31:44.450> and<00:31:45.450> having<00:31:45.780> an<00:31:45.960> module<00:31:46.590> with<00:31:47.070> no 00:31:47.330 --> 00:31:47.340 align:start position:0% about it and having an module with no 00:31:47.340 --> 00:31:50.210 align:start position:0% about it and having an module with no penances<00:31:47.910> where<00:31:48.180> I<00:31:48.210> cannot<00:31:48.710> mess<00:31:49.710> around<00:31:49.830> with 00:31:50.210 --> 00:31:50.220 align:start position:0% penances where I cannot mess around with 00:31:50.220 --> 00:31:52.760 align:start position:0% penances where I cannot mess around with brother-type<00:31:50.850> so<00:31:51.180> all<00:31:51.270> the<00:31:51.390> stuff<00:31:51.630> really 00:31:52.760 --> 00:31:52.770 align:start position:0% brother-type so all the stuff really 00:31:52.770 --> 00:31:57.760 align:start position:0% brother-type so all the stuff really despite<00:31:53.280> that<00:31:53.430> in<00:31:54.000> this<00:31:54.600> quite<00:31:55.170> fast<00:31:56.120> yeah 00:31:57.760 --> 00:31:57.770 align:start position:0% despite that in this quite fast yeah 00:31:57.770 --> 00:32:00.890 align:start position:0% despite that in this quite fast yeah seen<00:31:58.770> this<00:31:58.890> year<00:31:59.190> we've<00:31:59.850> covered<00:32:00.030> it's<00:32:00.270> just<00:32:00.390> a 00:32:00.890 --> 00:32:00.900 align:start position:0% seen this year we've covered it's just a 00:32:00.900 --> 00:32:04.599 align:start position:0% seen this year we've covered it's just a few<00:32:01.290> tips<00:32:01.440> how<00:32:01.710> to<00:32:01.740> centralize 00:32:04.599 --> 00:32:04.609 align:start position:0% 00:32:04.609 --> 00:32:08.359 align:start position:0% so<00:32:05.609> this<00:32:05.789> is<00:32:06.169> the<00:32:07.169> most<00:32:07.379> important<00:32:07.830> thing<00:32:07.919> and 00:32:08.359 --> 00:32:08.369 align:start position:0% so this is the most important thing and 00:32:08.369 --> 00:32:10.820 align:start position:0% so this is the most important thing and if<00:32:08.519> you<00:32:08.669> want<00:32:08.879> you<00:32:08.970> can<00:32:09.119> also<00:32:09.299> put<00:32:09.989> it<00:32:10.080> up<00:32:10.200> in 00:32:10.820 --> 00:32:10.830 align:start position:0% if you want you can also put it up in 00:32:10.830 --> 00:32:14.029 align:start position:0% if you want you can also put it up in video<00:32:11.129> Doc's<00:32:11.369> we<00:32:11.909> have<00:32:12.710> documentation<00:32:13.710> here 00:32:14.029 --> 00:32:14.039 align:start position:0% video Doc's we have documentation here 00:32:14.039 --> 00:32:17.749 align:start position:0% video Doc's we have documentation here we<00:32:14.909> try<00:32:15.090> to<00:32:15.179> put<00:32:15.479> in<00:32:15.629> as<00:32:15.779> much<00:32:16.080> as<00:32:16.320> we<00:32:16.379> can<00:32:16.759> and 00:32:17.749 --> 00:32:17.759 align:start position:0% we try to put in as much as we can and 00:32:17.759 --> 00:32:21.529 align:start position:0% we try to put in as much as we can and this<00:32:17.909> information<00:32:18.629> so<00:32:19.789> hopefully<00:32:20.789> in<00:32:20.999> and<00:32:21.239> you 00:32:21.529 --> 00:32:21.539 align:start position:0% this information so hopefully in and you 00:32:21.539 --> 00:32:24.139 align:start position:0% this information so hopefully in and you will<00:32:21.989> be<00:32:22.080> able<00:32:22.229> to<00:32:22.320> find<00:32:22.769> almost<00:32:23.190> any<00:32:23.669> answer 00:32:24.139 --> 00:32:24.149 align:start position:0% will be able to find almost any answer 00:32:24.149 --> 00:32:26.989 align:start position:0% will be able to find almost any answer in<00:32:24.450> there<00:32:24.659> if<00:32:24.929> not<00:32:25.229> let<00:32:25.619> us<00:32:25.739> know<00:32:25.769> that<00:32:26.159> we<00:32:26.340> if 00:32:26.989 --> 00:32:26.999 align:start position:0% in there if not let us know that we if 00:32:26.999 --> 00:32:29.960 align:start position:0% in there if not let us know that we if this<00:32:27.509> is<00:32:27.629> something<00:32:27.809> to<00:32:28.229> document<00:32:28.970> that's 00:32:29.960 --> 00:32:29.970 align:start position:0% this is something to document that's 00:32:29.970 --> 00:32:32.659 align:start position:0% this is something to document that's what<00:32:30.179> I'm<00:32:30.359> out<00:32:30.600> there<00:32:31.190> when<00:32:32.190> you<00:32:32.279> look<00:32:32.460> for 00:32:32.659 --> 00:32:32.669 align:start position:0% what I'm out there when you look for 00:32:32.669 --> 00:32:34.759 align:start position:0% what I'm out there when you look for information<00:32:32.940> it's<00:32:33.869> usually<00:32:34.049> a<00:32:34.229> good<00:32:34.409> starting 00:32:34.759 --> 00:32:34.769 align:start position:0% information it's usually a good starting 00:32:34.769 --> 00:32:37.639 align:start position:0% information it's usually a good starting point<00:32:35.009> to<00:32:35.340> start<00:32:35.429> with<00:32:35.669> redox<00:32:36.499> salts<00:32:37.499> also 00:32:37.639 --> 00:32:37.649 align:start position:0% point to start with redox salts also 00:32:37.649 --> 00:32:40.279 align:start position:0% point to start with redox salts also explain<00:32:38.279> the<00:32:38.369> content<00:32:38.820> of<00:32:39.029> chestnuts<00:32:39.479> then 00:32:40.279 --> 00:32:40.289 align:start position:0% explain the content of chestnuts then 00:32:40.289 --> 00:32:42.229 align:start position:0% explain the content of chestnuts then explain<00:32:40.799> the<00:32:41.099> background<00:32:41.220> and<00:32:41.759> all<00:32:42.059> the 00:32:42.229 --> 00:32:42.239 align:start position:0% explain the background and all the 00:32:42.239 --> 00:32:51.680 align:start position:0% explain the background and all the details<00:32:43.279> references<00:32:44.479> okay<00:32:49.879> good<00:32:50.879> so<00:32:51.389> I<00:32:51.419> don't 00:32:51.680 --> 00:32:51.690 align:start position:0% details references okay good so I don't 00:32:51.690 --> 00:32:52.159 align:start position:0% details references okay good so I don't I 00:32:52.159 --> 00:32:52.169 align:start position:0% I 00:32:52.169 --> 00:32:54.940 align:start position:0% I are<00:32:52.710> you<00:32:52.859> ready<00:32:53.099> so<00:32:53.340> far<00:32:53.580> to<00:32:53.970> start<00:32:54.330> the<00:32:54.419> topic 00:32:54.940 --> 00:32:54.950 align:start position:0% are you ready so far to start the topic 00:32:54.950 --> 00:32:58.260 align:start position:0% are you ready so far to start the topic image 00:32:58.260 --> 00:32:58.270 align:start position:0% 00:32:58.270 --> 00:33:00.060 align:start position:0% oh<00:32:58.300> you're<00:32:59.020> still<00:32:59.200> downloading<00:32:59.679> or 00:33:00.060 --> 00:33:00.070 align:start position:0% oh you're still downloading or 00:33:00.070 --> 00:33:06.150 align:start position:0% oh you're still downloading or installing<00:33:04.110> maybe<00:33:05.110> we<00:33:05.290> can<00:33:05.440> switch<00:33:05.679> cables 00:33:06.150 --> 00:33:06.160 align:start position:0% installing maybe we can switch cables 00:33:06.160 --> 00:33:20.549 align:start position:0% installing maybe we can switch cables now<00:33:07.380> because<00:33:11.610> especially 00:33:20.549 --> 00:33:20.559 align:start position:0% 00:33:20.559 --> 00:33:31.909 align:start position:0% that's<00:33:21.559> on<00:33:21.710> this<00:33:22.179> okay 00:33:31.909 --> 00:33:31.919 align:start position:0% 00:33:31.919 --> 00:33:36.320 align:start position:0% what 00:33:36.320 --> 00:33:36.330 align:start position:0% 00:33:36.330 --> 00:33:38.540 align:start position:0% maybe<00:33:36.930> just<00:33:37.290> you<00:33:37.590> know<00:33:37.830> with<00:33:37.980> you<00:33:38.160> what<00:33:38.340> we 00:33:38.540 --> 00:33:38.550 align:start position:0% maybe just you know with you what we 00:33:38.550 --> 00:33:56.790 align:start position:0% maybe just you know with you what we want<00:33:38.760> to<00:33:38.850> do<00:33:39.230> some<00:33:40.230> you<00:33:40.380> know<00:33:40.410> better<00:33:40.740> things 00:33:56.790 --> 00:33:56.800 align:start position:0% 00:33:56.800 --> 00:33:59.350 align:start position:0% okay<00:33:57.800> maybe<00:33:58.250> to<00:33:58.430> give<00:33:58.580> you<00:33:58.670> okay<00:33:58.970> what<00:33:59.180> we 00:33:59.350 --> 00:33:59.360 align:start position:0% okay maybe to give you okay what we 00:33:59.360 --> 00:34:03.580 align:start position:0% okay maybe to give you okay what we wanted<00:33:59.810> to<00:33:59.960> is<00:34:00.320> I<00:34:01.060> will<00:34:02.060> first<00:34:02.600> sure<00:34:02.900> a<00:34:03.260> small 00:34:03.580 --> 00:34:03.590 align:start position:0% wanted to is I will first sure a small 00:34:03.590 --> 00:34:07.000 align:start position:0% wanted to is I will first sure a small example<00:34:03.950> how<00:34:04.610> to<00:34:04.640> use<00:34:04.820> to<00:34:05.150> Tashkent<00:34:05.860> because<00:34:06.860> I 00:34:07.000 --> 00:34:07.010 align:start position:0% example how to use to Tashkent because I 00:34:07.010 --> 00:34:09.880 align:start position:0% example how to use to Tashkent because I think<00:34:07.070> the<00:34:07.250> touchdown<00:34:07.670> is<00:34:08.650> targeted<00:34:09.650> for<00:34:09.680> a 00:34:09.880 --> 00:34:09.890 align:start position:0% think the touchdown is targeted for a 00:34:09.890 --> 00:34:11.970 align:start position:0% think the touchdown is targeted for a study<00:34:10.220> most<00:34:10.520> def<00:34:10.820> developers<00:34:11.360> because 00:34:11.970 --> 00:34:11.980 align:start position:0% study most def developers because 00:34:11.980 --> 00:34:14.920 align:start position:0% study most def developers because javascript<00:34:12.980> today's<00:34:13.910> the<00:34:14.330> most<00:34:14.600> used 00:34:14.920 --> 00:34:14.930 align:start position:0% javascript today's the most used 00:34:14.930 --> 00:34:16.540 align:start position:0% javascript today's the most used language<00:34:15.230> when<00:34:15.380> it<00:34:15.440> comes<00:34:15.620> to<00:34:16.040> the<00:34:16.100> use<00:34:16.310> of<00:34:16.340> the 00:34:16.540 --> 00:34:16.550 align:start position:0% language when it comes to the use of the 00:34:16.550 --> 00:34:19.750 align:start position:0% language when it comes to the use of the face<00:34:16.730> there's<00:34:17.600> almost<00:34:17.870> no<00:34:18.580> alternative<00:34:19.580> right 00:34:19.750 --> 00:34:19.760 align:start position:0% face there's almost no alternative right 00:34:19.760 --> 00:34:22.630 align:start position:0% face there's almost no alternative right now<00:34:19.970> it's<00:34:20.720> fine<00:34:20.990> if<00:34:21.560> you<00:34:21.620> putting<00:34:22.310> it<00:34:22.430> there 00:34:22.630 --> 00:34:22.640 align:start position:0% now it's fine if you putting it there 00:34:22.640 --> 00:34:26.320 align:start position:0% now it's fine if you putting it there and<00:34:22.880> do<00:34:23.870> not<00:34:24.050> want<00:34:24.350> to<00:34:24.440> rely<00:34:24.560> on<00:34:24.740> their<00:34:25.340> brakes 00:34:26.320 --> 00:34:26.330 align:start position:0% and do not want to rely on their brakes 00:34:26.330 --> 00:34:29.560 align:start position:0% and do not want to rely on their brakes ever<00:34:26.510> an<00:34:26.690> extra<00:34:27.320> bucket<00:34:27.950> or<00:34:28.280> night<00:34:28.580> or 00:34:29.560 --> 00:34:29.570 align:start position:0% ever an extra bucket or night or 00:34:29.570 --> 00:34:31.450 align:start position:0% ever an extra bucket or night or environment<00:34:30.380> where<00:34:30.560> somebody<00:34:30.890> checks<00:34:31.250> that 00:34:31.450 --> 00:34:31.460 align:start position:0% environment where somebody checks that 00:34:31.460 --> 00:34:36.100 align:start position:0% environment where somebody checks that we<00:34:31.700> object<00:34:32.060> for<00:34:32.240> you<00:34:32.560> then<00:34:33.730> you<00:34:34.810> would<00:34:35.810> be<00:34:35.930> very 00:34:36.100 --> 00:34:36.110 align:start position:0% we object for you then you would be very 00:34:36.110 --> 00:34:37.660 align:start position:0% we object for you then you would be very interested<00:34:36.560> in<00:34:36.650> favor<00:34:36.890> is<00:34:37.190> that's<00:34:37.460> why<00:34:37.610> the 00:34:37.660 --> 00:34:37.670 align:start position:0% interested in favor is that's why the 00:34:37.670 --> 00:34:40.840 align:start position:0% interested in favor is that's why the first<00:34:37.880> thing<00:34:38.000> we've<00:34:38.270> just<00:34:39.160> to<00:34:40.160> the<00:34:40.220> JavaScript 00:34:40.840 --> 00:34:40.850 align:start position:0% first thing we've just to the JavaScript 00:34:40.850 --> 00:34:45.280 align:start position:0% first thing we've just to the JavaScript coding<00:34:41.410> party<00:34:42.410> types<00:34:42.710> of<00:34:42.920> time<00:34:43.100> and<00:34:43.990> then<00:34:44.990> we 00:34:45.280 --> 00:34:45.290 align:start position:0% coding party types of time and then we 00:34:45.290 --> 00:34:48.640 align:start position:0% coding party types of time and then we work<00:34:45.470> and<00:34:45.860> used<00:34:46.310> its<00:34:46.520> C<00:34:46.880> client<00:34:47.260> and<00:34:48.260> because 00:34:48.640 --> 00:34:48.650 align:start position:0% work and used its C client and because 00:34:48.650 --> 00:34:50.370 align:start position:0% work and used its C client and because you<00:34:48.890> proceed<00:34:49.310> like<00:34:49.460> there's<00:34:49.730> different 00:34:50.370 --> 00:34:50.380 align:start position:0% you proceed like there's different 00:34:50.380 --> 00:34:53.500 align:start position:0% you proceed like there's different targets<00:34:51.380> you<00:34:51.650> comparator<00:34:52.310> what<00:34:52.850> is<00:34:52.970> it<00:34:53.120> like 00:34:53.500 --> 00:34:53.510 align:start position:0% targets you comparator what is it like 00:34:53.510 --> 00:34:55.990 align:start position:0% targets you comparator what is it like it<00:34:53.720> just<00:34:54.080> a<00:34:54.170> similar<00:34:54.650> executable<00:34:55.310> that<00:34:55.850> you 00:34:55.990 --> 00:34:56.000 align:start position:0% it just a similar executable that you 00:34:56.000 --> 00:34:58.990 align:start position:0% it just a similar executable that you can<00:34:56.210> even<00:34:56.690> use<00:34:56.750> a<00:34:57.080> man<00:34:57.260> in<00:34:57.380> the<00:34:57.470> best<00:34:57.650> foot<00:34:58.000> we 00:34:58.990 --> 00:34:59.000 align:start position:0% can even use a man in the best foot we 00:34:59.000 --> 00:35:00.900 align:start position:0% can even use a man in the best foot we will<00:34:59.210> play<00:34:59.480> around<00:34:59.540> with<00:34:59.840> that<00:34:59.990> bit 00:35:00.900 --> 00:35:00.910 align:start position:0% will play around with that bit 00:35:00.910 --> 00:35:02.700 align:start position:0% will play around with that bit to<00:35:01.000> do<00:35:01.150> with<00:35:01.269> it<00:35:01.509> it's<00:35:01.960> actually<00:35:02.289> quite<00:35:02.410> a<00:35:02.500> lot 00:35:02.700 --> 00:35:02.710 align:start position:0% to do with it it's actually quite a lot 00:35:02.710 --> 00:35:07.140 align:start position:0% to do with it it's actually quite a lot but<00:35:02.920> you<00:35:03.069> could<00:35:03.250> just<00:35:03.930> use<00:35:05.789> command<00:35:06.789> line<00:35:06.880> you 00:35:07.140 --> 00:35:07.150 align:start position:0% but you could just use command line you 00:35:07.150 --> 00:35:10.410 align:start position:0% but you could just use command line you tell<00:35:07.359> and<00:35:08.349> then<00:35:08.500> we<00:35:08.880> look<00:35:09.880> at<00:35:09.970> the<00:35:10.150> seat 00:35:10.410 --> 00:35:10.420 align:start position:0% tell and then we look at the seat 00:35:10.420 --> 00:35:12.960 align:start position:0% tell and then we look at the seat directly<00:35:10.660> by<00:35:11.019> this<00:35:11.230> small<00:35:11.970> sample 00:35:12.960 --> 00:35:12.970 align:start position:0% directly by this small sample 00:35:12.970 --> 00:35:16.680 align:start position:0% directly by this small sample application<00:35:13.750> and<00:35:13.960> see<00:35:14.200> how<00:35:15.099> to<00:35:15.160> use<00:35:15.490> the<00:35:15.730> ink 00:35:16.680 --> 00:35:16.690 align:start position:0% application and see how to use the ink 00:35:16.690 --> 00:35:20.430 align:start position:0% application and see how to use the ink you<00:35:16.869> climb<00:35:17.200> there<00:35:18.240> and<00:35:19.240> then<00:35:19.809> maybe<00:35:19.990> we'll 00:35:20.430 --> 00:35:20.440 align:start position:0% you climb there and then maybe we'll 00:35:20.440 --> 00:35:22.230 align:start position:0% you climb there and then maybe we'll look<00:35:20.529> in<00:35:20.680> the<00:35:20.769> choppa<00:35:21.069> because<00:35:21.700> we<00:35:21.910> all<00:35:22.029> have 00:35:22.230 --> 00:35:22.240 align:start position:0% look in the choppa because we all have 00:35:22.240 --> 00:35:24.870 align:start position:0% look in the choppa because we all have binding<00:35:22.660> to<00:35:22.809> each<00:35:22.900> other<00:35:23.140> into<00:35:23.890> the<00:35:23.920> Chava<00:35:24.339> fly 00:35:24.870 --> 00:35:24.880 align:start position:0% binding to each other into the Chava fly 00:35:24.880 --> 00:35:27.420 align:start position:0% binding to each other into the Chava fly itself<00:35:25.329> will<00:35:25.599> only<00:35:25.779> use<00:35:26.170> the<00:35:26.230> C<00:35:26.799> client<00:35:27.279> in 00:35:27.420 --> 00:35:27.430 align:start position:0% itself will only use the C client in 00:35:27.430 --> 00:35:31.109 align:start position:0% itself will only use the C client in every<00:35:28.089> night<00:35:28.450> interface<00:35:28.960> but<00:35:29.819> binds<00:35:30.819> world 00:35:31.109 --> 00:35:31.119 align:start position:0% every night interface but binds world 00:35:31.119 --> 00:35:32.940 align:start position:0% every night interface but binds world and<00:35:31.720> the<00:35:31.809> natural<00:35:31.960> feeling<00:35:32.559> for<00:35:32.740> child 00:35:32.940 --> 00:35:32.950 align:start position:0% and the natural feeling for child 00:35:32.950 --> 00:35:35.099 align:start position:0% and the natural feeling for child develop<00:35:33.579> why<00:35:34.119> drama<00:35:34.450> because<00:35:34.839> especially 00:35:35.099 --> 00:35:35.109 align:start position:0% develop why drama because especially 00:35:35.109 --> 00:35:37.230 align:start position:0% develop why drama because especially when<00:35:35.559> you<00:35:35.680> were<00:35:35.829> appointed<00:35:36.160> develop<00:35:36.910> native 00:35:37.230 --> 00:35:37.240 align:start position:0% when you were appointed develop native 00:35:37.240 --> 00:35:44.329 align:start position:0% when you were appointed develop native Android<00:35:37.660> apps 00:35:44.329 --> 00:35:44.339 align:start position:0% 00:35:44.339 --> 00:35:48.359 align:start position:0% and<00:35:45.339> then<00:35:45.519> in<00:35:45.670> the<00:35:45.819> end<00:35:46.180> also<00:35:46.839> time<00:35:47.259> and<00:35:48.099> what 00:35:48.359 --> 00:35:48.369 align:start position:0% and then in the end also time and what 00:35:48.369 --> 00:35:51.390 align:start position:0% and then in the end also time and what we<00:35:48.640> almost<00:35:48.789> wanted<00:35:49.180> to<00:35:49.240> do<00:35:49.329> is<00:35:49.480> them<00:35:50.069> to<00:35:51.069> a<00:35:51.130> deep 00:35:51.390 --> 00:35:51.400 align:start position:0% we almost wanted to do is them to a deep 00:35:51.400 --> 00:35:53.160 align:start position:0% we almost wanted to do is them to a deep dive<00:35:51.640> and<00:35:52.059> may<00:35:52.599> actually<00:35:52.720> think<00:35:53.049> about 00:35:53.160 --> 00:35:53.170 align:start position:0% dive and may actually think about 00:35:53.170 --> 00:35:55.349 align:start position:0% dive and may actually think about switching<00:35:53.829> that<00:35:54.009> if<00:35:54.339> you<00:35:54.490> in<00:35:54.700> more<00:35:54.910> interested 00:35:55.349 --> 00:35:55.359 align:start position:0% switching that if you in more interested 00:35:55.359 --> 00:35:57.509 align:start position:0% switching that if you in more interested in<00:35:55.539> fact<00:35:55.809> when<00:35:55.990> university-type<00:35:56.680> about<00:35:57.309> how 00:35:57.509 --> 00:35:57.519 align:start position:0% in fact when university-type about how 00:35:57.519 --> 00:35:59.579 align:start position:0% in fact when university-type about how the<00:35:57.579> verification<00:35:58.299> work<00:35:58.450> what<00:35:59.170> you<00:35:59.319> want<00:35:59.500> to 00:35:59.579 --> 00:35:59.589 align:start position:0% the verification work what you want to 00:35:59.589 --> 00:36:02.120 align:start position:0% the verification work what you want to do<00:35:59.680> it<00:35:59.799> the<00:35:59.950> practical<00:36:00.400> things<00:36:00.609> first<00:36:00.880> right 00:36:02.120 --> 00:36:02.130 align:start position:0% do it the practical things first right 00:36:02.130 --> 00:36:03.480 align:start position:0% do it the practical things first right okay 00:36:03.480 --> 00:36:03.490 align:start position:0% okay 00:36:03.490 --> 00:36:05.309 align:start position:0% okay maybe<00:36:03.730> a<00:36:03.970> nice<00:36:04.210> to<00:36:04.420> think<00:36:04.690> that<00:36:04.839> now<00:36:05.049> because 00:36:05.309 --> 00:36:05.319 align:start position:0% maybe a nice to think that now because 00:36:05.319 --> 00:36:07.470 align:start position:0% maybe a nice to think that now because they're<00:36:05.859> already<00:36:06.400> a<00:36:06.549> few<00:36:06.759> question<00:36:07.180> about 00:36:07.470 --> 00:36:07.480 align:start position:0% they're already a few question about 00:36:07.480 --> 00:36:09.710 align:start position:0% they're already a few question about that<00:36:07.539> and<00:36:07.960> I<00:36:08.529> think<00:36:08.589> that<00:36:08.829> will<00:36:09.220> help<00:36:09.430> to 00:36:09.710 --> 00:36:09.720 align:start position:0% that and I think that will help to 00:36:09.720 --> 00:36:12.089 align:start position:0% that and I think that will help to understand<00:36:10.720> a<00:36:10.809> little<00:36:10.990> bit<00:36:11.109> more<00:36:11.200> how<00:36:11.529> exactly 00:36:12.089 --> 00:36:12.099 align:start position:0% understand a little bit more how exactly 00:36:12.099 --> 00:36:36.250 align:start position:0% understand a little bit more how exactly very<00:36:12.400> few<00:36:12.670> works<00:36:14.009> we<00:36:15.009> have<00:36:15.130> X<00:36:15.869> ok 00:36:36.250 --> 00:36:36.260 align:start position:0% 00:36:36.260 --> 00:36:40.690 align:start position:0% so<00:36:37.720> well<00:36:38.720> as<00:36:39.020> mentioned<00:36:39.500> before<00:36:39.590> what<00:36:40.280> we<00:36:40.460> said 00:36:40.690 --> 00:36:40.700 align:start position:0% so well as mentioned before what we said 00:36:40.700 --> 00:36:42.610 align:start position:0% so well as mentioned before what we said what<00:36:40.880> we<00:36:40.970> do<00:36:41.120> is<00:36:41.240> we<00:36:41.390> said<00:36:41.570> obviously<00:36:41.840> we<00:36:42.200> trust 00:36:42.610 --> 00:36:42.620 align:start position:0% what we do is we said obviously we trust 00:36:42.620 --> 00:36:44.790 align:start position:0% what we do is we said obviously we trust first<00:36:43.070> of<00:36:43.190> all<00:36:43.250> this<00:36:43.400> is<00:36:43.580> a<00:36:43.700> design<00:36:44.600> decision 00:36:44.790 --> 00:36:44.800 align:start position:0% first of all this is a design decision 00:36:44.800 --> 00:36:48.310 align:start position:0% first of all this is a design decision because<00:36:45.800> something's<00:36:46.640> mm<00:36:47.330> why<00:36:47.480> do<00:36:47.540> wrapped<00:36:48.140> up 00:36:48.310 --> 00:36:48.320 align:start position:0% because something's mm why do wrapped up 00:36:48.320 --> 00:36:53.680 align:start position:0% because something's mm why do wrapped up used<00:36:48.620> to<00:36:48.800> delight<00:36:49.430> time<00:36:49.730> to<00:36:50.500> do<00:36:51.640> well<00:36:52.690> there 00:36:53.680 --> 00:36:53.690 align:start position:0% used to delight time to do well there 00:36:53.690 --> 00:36:56.490 align:start position:0% used to delight time to do well there are<00:36:53.840> reasons<00:36:54.200> why<00:36:54.320> we<00:36:54.440> don't<00:36:54.700> one<00:36:55.700> of<00:36:55.820> them<00:36:56.000> is 00:36:56.490 --> 00:36:56.500 align:start position:0% are reasons why we don't one of them is 00:36:56.500 --> 00:37:00.730 align:start position:0% are reasons why we don't one of them is in<00:36:57.730> these<00:36:58.730> clients<00:36:59.360> if<00:36:59.690> they're<00:37:00.260> not<00:37:00.410> only 00:37:00.730 --> 00:37:00.740 align:start position:0% in these clients if they're not only 00:37:00.740 --> 00:37:02.620 align:start position:0% in these clients if they're not only stateless<00:37:01.250> some<00:37:01.580> of<00:37:01.700> them<00:37:01.910> don't<00:37:02.270> even<00:37:02.510> have 00:37:02.620 --> 00:37:02.630 align:start position:0% stateless some of them don't even have 00:37:02.630 --> 00:37:05.500 align:start position:0% stateless some of them don't even have internet<00:37:02.840> connection<00:37:03.700> being<00:37:04.700> made<00:37:04.850> using 00:37:05.500 --> 00:37:05.510 align:start position:0% internet connection being made using 00:37:05.510 --> 00:37:07.330 align:start position:0% internet connection being made using like<00:37:05.780> temporal<00:37:06.170> power<00:37:06.380> means<00:37:06.680> you<00:37:06.950> have<00:37:07.100> to<00:37:07.250> be 00:37:07.330 --> 00:37:07.340 align:start position:0% like temporal power means you have to be 00:37:07.340 --> 00:37:09.730 align:start position:0% like temporal power means you have to be part<00:37:07.670> of<00:37:07.820> the<00:37:07.940> peer<00:37:08.210> to<00:37:08.300> peer<00:37:08.330> network<00:37:08.740> and 00:37:09.730 --> 00:37:09.740 align:start position:0% part of the peer to peer network and 00:37:09.740 --> 00:37:13.390 align:start position:0% part of the peer to peer network and this<00:37:09.920> is<00:37:10.190> a<00:37:10.220> requirement<00:37:10.760> we<00:37:11.540> do<00:37:11.690> not<00:37:11.930> have<00:37:12.400> we 00:37:13.390 --> 00:37:13.400 align:start position:0% this is a requirement we do not have we 00:37:13.400 --> 00:37:15.640 align:start position:0% this is a requirement we do not have we don't<00:37:13.610> have<00:37:13.700> because<00:37:14.150> the<00:37:14.270> industry<00:37:14.570> does<00:37:15.440> not 00:37:15.640 --> 00:37:15.650 align:start position:0% don't have because the industry does not 00:37:15.650 --> 00:37:17.050 align:start position:0% don't have because the industry does not have<00:37:15.800> internet<00:37:16.160> connection 00:37:17.050 --> 00:37:17.060 align:start position:0% have internet connection 00:37:17.060 --> 00:37:19.030 align:start position:0% have internet connection but<00:37:17.540> we<00:37:17.660> can<00:37:17.840> still<00:37:18.050> use<00:37:18.110> it<00:37:18.500> because<00:37:18.650> we<00:37:18.890> can 00:37:19.030 --> 00:37:19.040 align:start position:0% but we can still use it because we can 00:37:19.040 --> 00:37:21.520 align:start position:0% but we can still use it because we can use<00:37:19.280> the<00:37:19.640> and<00:37:20.210> he<00:37:20.360> is<00:37:20.390> supposed<00:37:20.900> to<00:37:21.050> tools<00:37:21.290> for 00:37:21.520 --> 00:37:21.530 align:start position:0% use the and he is supposed to tools for 00:37:21.530 --> 00:37:24.010 align:start position:0% use the and he is supposed to tools for itself<00:37:21.740> so<00:37:22.100> it's<00:37:22.670> used<00:37:22.970> internet<00:37:23.330> connection 00:37:24.010 --> 00:37:24.020 align:start position:0% itself so it's used internet connection 00:37:24.020 --> 00:37:27.010 align:start position:0% itself so it's used internet connection out<00:37:24.170> of<00:37:24.410> your<00:37:24.530> phone<00:37:25.240> that's<00:37:26.240> what<00:37:26.360> we<00:37:26.660> have 00:37:27.010 --> 00:37:27.020 align:start position:0% out of your phone that's what we have 00:37:27.020 --> 00:37:28.570 align:start position:0% out of your phone that's what we have subtracted<00:37:27.530> this<00:37:27.830> transport<00:37:28.430> layer 00:37:28.570 --> 00:37:28.580 align:start position:0% subtracted this transport layer 00:37:28.580 --> 00:37:31.030 align:start position:0% subtracted this transport layer completely<00:37:29.360> it<00:37:29.540> tastes<00:37:29.780> obviously<00:37:30.230> exactly 00:37:31.030 --> 00:37:31.040 align:start position:0% completely it tastes obviously exactly 00:37:31.040 --> 00:37:33.790 align:start position:0% completely it tastes obviously exactly perfect<00:37:31.490> for<00:37:31.670> that<00:37:32.260> this<00:37:33.260> is<00:37:33.350> also<00:37:33.500> one<00:37:33.770> reason 00:37:33.790 --> 00:37:33.800 align:start position:0% perfect for that this is also one reason 00:37:33.800 --> 00:37:36.010 align:start position:0% perfect for that this is also one reason why<00:37:34.190> we<00:37:34.340> cannot<00:37:34.550> rely<00:37:34.910> on<00:37:34.940> the<00:37:35.180> p2p<00:37:35.510> network 00:37:36.010 --> 00:37:36.020 align:start position:0% why we cannot rely on the p2p network 00:37:36.020 --> 00:37:40.000 align:start position:0% why we cannot rely on the p2p network where<00:37:36.380> you<00:37:36.500> have<00:37:36.740> to<00:37:38.020> require<00:37:39.020> men<00:37:39.290> to<00:37:39.530> have<00:37:39.860> an 00:37:40.000 --> 00:37:40.010 align:start position:0% where you have to require men to have an 00:37:40.010 --> 00:37:42.790 align:start position:0% where you have to require men to have an active<00:37:40.400> internet<00:37:40.550> connection<00:37:41.380> so<00:37:42.380> that<00:37:42.410> books 00:37:42.790 --> 00:37:42.800 align:start position:0% active internet connection so that books 00:37:42.800 --> 00:37:47.080 align:start position:0% active internet connection so that books also<00:37:43.100> for<00:37:43.640> offline<00:37:44.450> devices<00:37:45.080> that's<00:37:46.090> yeah 00:37:47.080 --> 00:37:47.090 align:start position:0% also for offline devices that's yeah 00:37:47.090 --> 00:37:49.420 align:start position:0% also for offline devices that's yeah thing<00:37:47.780> is<00:37:47.810> of<00:37:48.080> course<00:37:48.110> usually<00:37:49.070> what<00:37:49.280> you<00:37:49.400> want 00:37:49.420 --> 00:37:49.430 align:start position:0% thing is of course usually what you want 00:37:49.430 --> 00:37:52.480 align:start position:0% thing is of course usually what you want to<00:37:49.670> do<00:37:49.820> is<00:37:50.120> most<00:37:51.080> these<00:37:51.350> mice<00:37:51.650> will<00:37:51.980> sleep<00:37:52.250> all 00:37:52.480 --> 00:37:52.490 align:start position:0% to do is most these mice will sleep all 00:37:52.490 --> 00:37:52.840 align:start position:0% to do is most these mice will sleep all the<00:37:52.550> time 00:37:52.840 --> 00:37:52.850 align:start position:0% the time 00:37:52.850 --> 00:37:54.970 align:start position:0% the time I'll<00:37:53.090> go<00:37:53.300> along<00:37:53.510> and<00:37:53.780> once<00:37:54.440> you<00:37:54.590> want<00:37:54.770> to<00:37:54.830> poke 00:37:54.970 --> 00:37:54.980 align:start position:0% I'll go along and once you want to poke 00:37:54.980 --> 00:37:57.490 align:start position:0% I'll go along and once you want to poke the<00:37:55.190> door<00:37:55.340> he<00:37:55.940> needs<00:37:56.150> an<00:37:56.300> instant<00:37:56.720> answer<00:37:57.080> and 00:37:57.490 --> 00:37:57.500 align:start position:0% the door he needs an instant answer and 00:37:57.500 --> 00:37:59.950 align:start position:0% the door he needs an instant answer and if<00:37:58.280> you<00:37:58.370> want<00:37:58.580> to<00:37:58.730> let<00:37:59.180> me<00:37:59.330> like<00:37:59.510> time<00:37:59.720> for<00:37:59.900> the 00:37:59.950 --> 00:37:59.960 align:start position:0% if you want to let me like time for the 00:37:59.960 --> 00:38:00.370 align:start position:0% if you want to let me like time for the call 00:38:00.370 --> 00:38:00.380 align:start position:0% call 00:38:00.380 --> 00:38:05.080 align:start position:0% call you<00:38:00.620> will<00:38:00.740> start<00:38:00.980> finding<00:38:01.490> ups<00:38:02.030> for<00:38:02.240> us<00:38:04.090> so 00:38:05.080 --> 00:38:05.090 align:start position:0% you will start finding ups for us so 00:38:05.090 --> 00:38:07.590 align:start position:0% you will start finding ups for us so that's<00:38:05.600> why<00:38:05.900> you<00:38:06.800> get<00:38:06.950> instance 00:38:07.590 --> 00:38:07.600 align:start position:0% that's why you get instance 00:38:07.600 --> 00:38:08.910 align:start position:0% that's why you get instance [Music] 00:38:08.910 --> 00:38:08.920 align:start position:0% [Music] 00:38:08.920 --> 00:38:11.040 align:start position:0% [Music] but<00:38:09.280> in<00:38:09.490> order<00:38:09.640> to<00:38:09.760> do<00:38:09.970> this<00:38:10.120> that's<00:38:10.780> all<00:38:10.930> we 00:38:11.040 --> 00:38:11.050 align:start position:0% but in order to do this that's all we 00:38:11.050 --> 00:38:13.050 align:start position:0% but in order to do this that's all we have<00:38:11.200> these<00:38:11.320> note<00:38:11.560> this<00:38:11.740> so<00:38:12.520> you<00:38:12.760> will<00:38:12.880> know 00:38:13.050 --> 00:38:13.060 align:start position:0% have these note this so you will know 00:38:13.060 --> 00:38:15.360 align:start position:0% have these note this so you will know your<00:38:13.360> peers<00:38:13.630> deployment<00:38:14.440> that's<00:38:14.800> important 00:38:15.360 --> 00:38:15.370 align:start position:0% your peers deployment that's important 00:38:15.370 --> 00:38:18.510 align:start position:0% your peers deployment that's important and<00:38:15.760> you<00:38:16.210> know<00:38:16.360> exactly<00:38:16.810> when<00:38:17.500> centers<00:38:18.070> you 00:38:18.510 --> 00:38:18.520 align:start position:0% and you know exactly when centers you 00:38:18.520 --> 00:38:21.240 align:start position:0% and you know exactly when centers you randomly<00:38:18.880> choose<00:38:19.270> one<00:38:19.300> and<00:38:19.870> say<00:38:20.020> okay<00:38:20.320> I<00:38:20.590> want 00:38:21.240 --> 00:38:21.250 align:start position:0% randomly choose one and say okay I want 00:38:21.250 --> 00:38:23.670 align:start position:0% randomly choose one and say okay I want this<00:38:21.520> prove<00:38:21.910> this<00:38:22.390> and<00:38:22.630> for<00:38:22.900> you<00:38:23.050> but<00:38:23.530> that's 00:38:23.670 --> 00:38:23.680 align:start position:0% this prove this and for you but that's 00:38:23.680 --> 00:38:26.780 align:start position:0% this prove this and for you but that's really<00:38:23.860> how<00:38:24.100> it<00:38:24.130> looks<00:38:24.520> like<00:38:24.700> you<00:38:25.330> see<00:38:25.540> this<00:38:26.380> is 00:38:26.780 --> 00:38:26.790 align:start position:0% really how it looks like you see this is 00:38:26.790 --> 00:38:30.390 align:start position:0% really how it looks like you see this is Petra<00:38:27.790> extra<00:38:28.270> seat<00:38:28.710> chest<00:38:29.710> obviously<00:38:30.130> and 00:38:30.390 --> 00:38:30.400 align:start position:0% Petra extra seat chest obviously and 00:38:30.400 --> 00:38:34.230 align:start position:0% Petra extra seat chest obviously and here<00:38:30.640> you<00:38:30.940> have<00:38:31.180> this<00:38:31.950> entry<00:38:32.950> property<00:38:33.520> where 00:38:34.230 --> 00:38:34.240 align:start position:0% here you have this entry property where 00:38:34.240 --> 00:38:35.400 align:start position:0% here you have this entry property where we<00:38:34.270> define<00:38:34.780> okay 00:38:35.400 --> 00:38:35.410 align:start position:0% we define okay 00:38:35.410 --> 00:38:37.590 align:start position:0% we define okay what<00:38:35.980> kind<00:38:36.250> of<00:38:36.310> education<00:38:36.880> do<00:38:37.000> we<00:38:37.120> want<00:38:37.360> and 00:38:37.590 --> 00:38:37.600 align:start position:0% what kind of education do we want and 00:38:37.600 --> 00:38:42.120 align:start position:0% what kind of education do we want and the<00:38:38.410> signatures<00:38:38.950> from<00:38:39.220> which<00:38:39.880> above<00:38:40.510> notes<00:38:41.130> so 00:38:42.120 --> 00:38:42.130 align:start position:0% the signatures from which above notes so 00:38:42.130 --> 00:38:49.650 align:start position:0% the signatures from which above notes so then<00:38:45.630> okay<00:38:46.710> the<00:38:47.710> response<00:38:48.130> looks<00:38:48.730> the<00:38:49.480> same 00:38:49.650 --> 00:38:49.660 align:start position:0% then okay the response looks the same 00:38:49.660 --> 00:38:53.790 align:start position:0% then okay the response looks the same way<00:38:49.870> you<00:38:50.200> see<00:38:50.230> it<00:38:50.950> gets<00:38:51.910> a<00:38:52.030> result<00:38:52.150> as<00:38:52.780> usual<00:38:53.290> to 00:38:53.790 --> 00:38:53.800 align:start position:0% way you see it gets a result as usual to 00:38:53.800 --> 00:38:57.660 align:start position:0% way you see it gets a result as usual to us<00:38:54.010> now<00:38:54.520> you<00:38:54.580> see<00:38:54.850> the<00:38:55.060> truth<00:38:55.360> out<00:38:55.750> there<00:38:56.670> so 00:38:57.660 --> 00:38:57.670 align:start position:0% us now you see the truth out there so 00:38:57.670 --> 00:38:59.490 align:start position:0% us now you see the truth out there so that<00:38:57.820> intrusion<00:38:58.240> I'll<00:38:58.600> talk<00:38:58.840> about<00:38:58.870> it<00:38:59.260> in<00:38:59.380> an 00:38:59.490 --> 00:38:59.500 align:start position:0% that intrusion I'll talk about it in an 00:38:59.500 --> 00:39:00.180 align:start position:0% that intrusion I'll talk about it in an event 00:39:00.180 --> 00:39:00.190 align:start position:0% event 00:39:00.190 --> 00:39:02.910 align:start position:0% event what<00:39:00.700> kind<00:39:00.970> of<00:39:01.030> who<00:39:01.480> exactly<00:39:01.660> are<00:39:02.020> but<00:39:02.770> we 00:39:02.910 --> 00:39:02.920 align:start position:0% what kind of who exactly are but we 00:39:02.920 --> 00:39:06.540 align:start position:0% what kind of who exactly are but we won't<00:39:03.220> approve<00:39:03.880> you<00:39:04.180> two<00:39:04.420> signatures<00:39:05.550> where 00:39:06.540 --> 00:39:06.550 align:start position:0% won't approve you two signatures where 00:39:06.550 --> 00:39:09.180 align:start position:0% won't approve you two signatures where requested<00:39:07.150> last<00:39:08.110> time<00:39:08.320> temperatures<00:39:08.590> other 00:39:09.180 --> 00:39:09.190 align:start position:0% requested last time temperatures other 00:39:09.190 --> 00:39:12.030 align:start position:0% requested last time temperatures other lights<00:39:09.520> last<00:39:09.880> notice<00:39:10.510> this<00:39:11.380> is<00:39:11.560> the<00:39:11.830> Bruckner 00:39:12.030 --> 00:39:12.040 align:start position:0% lights last notice this is the Bruckner 00:39:12.040 --> 00:39:14.040 align:start position:0% lights last notice this is the Bruckner home<00:39:12.490> where<00:39:12.760> the<00:39:13.030> last<00:39:13.240> event<00:39:13.600> have<00:39:13.840> the 00:39:14.040 --> 00:39:14.050 align:start position:0% home where the last event have the 00:39:14.050 --> 00:39:17.190 align:start position:0% home where the last event have the registry<00:39:14.650> meaning<00:39:15.610> whenever<00:39:15.910> a<00:39:16.390> new<00:39:16.600> note<00:39:16.870> was 00:39:17.190 --> 00:39:17.200 align:start position:0% registry meaning whenever a new note was 00:39:17.200 --> 00:39:20.940 align:start position:0% registry meaning whenever a new note was edit<00:39:17.670> this<00:39:18.670> last<00:39:18.970> note<00:39:19.240> list<00:39:19.480> will<00:39:19.750> change<00:39:20.110> and 00:39:20.940 --> 00:39:20.950 align:start position:0% edit this last note list will change and 00:39:20.950 --> 00:39:22.590 align:start position:0% edit this last note list will change and that's<00:39:21.250> why<00:39:21.490> the<00:39:21.550> client<00:39:21.880> will<00:39:22.090> figure<00:39:22.210> out<00:39:22.300> oh 00:39:22.590 --> 00:39:22.600 align:start position:0% that's why the client will figure out oh 00:39:22.600 --> 00:39:25.350 align:start position:0% that's why the client will figure out oh it's<00:39:22.990> time<00:39:23.230> to<00:39:23.410> act<00:39:23.500> in<00:39:23.650> my<00:39:23.740> own<00:39:23.890> system<00:39:24.360> so 00:39:25.350 --> 00:39:25.360 align:start position:0% it's time to act in my own system so 00:39:25.360 --> 00:39:27.540 align:start position:0% it's time to act in my own system so that's<00:39:25.540> why<00:39:25.690> it<00:39:26.440> because<00:39:27.040> it<00:39:27.190> I<00:39:27.310> need<00:39:27.520> to 00:39:27.540 --> 00:39:27.550 align:start position:0% that's why it because it I need to 00:39:27.550 --> 00:39:30.240 align:start position:0% that's why it because it I need to always<00:39:28.000> be<00:39:28.510> sure<00:39:28.870> that<00:39:28.900> these<00:39:29.290> notes<00:39:30.070> are 00:39:30.240 --> 00:39:30.250 align:start position:0% always be sure that these notes are 00:39:30.250 --> 00:39:34.000 align:start position:0% always be sure that these notes are still<00:39:30.430> male 00:39:34.000 --> 00:39:34.010 align:start position:0% 00:39:34.010 --> 00:39:38.690 align:start position:0% positive<00:39:35.010> yes<00:39:35.609> it<00:39:36.150> also<00:39:36.390> Victor<00:39:36.900> is<00:39:37.319> the<00:39:37.700> exact 00:39:38.690 --> 00:39:38.700 align:start position:0% positive yes it also Victor is the exact 00:39:38.700 --> 00:39:41.240 align:start position:0% positive yes it also Victor is the exact if<00:39:38.849> they<00:39:38.970> ever<00:39:39.029> convicted<00:39:39.510> get<00:39:40.440> kicked<00:39:40.680> out<00:39:40.859> of 00:39:41.240 --> 00:39:41.250 align:start position:0% if they ever convicted get kicked out of 00:39:41.250 --> 00:39:43.130 align:start position:0% if they ever convicted get kicked out of course<00:39:41.579> you've<00:39:41.849> won<00:39:42.480> make<00:39:42.690> sure<00:39:42.869> they<00:39:43.079> don't 00:39:43.130 --> 00:39:43.140 align:start position:0% course you've won make sure they don't 00:39:43.140 --> 00:39:58.519 align:start position:0% course you've won make sure they don't ask<00:39:55.789> what<00:39:56.789> you<00:39:57.210> can't<00:39:57.450> withdraw<00:39:57.630> it<00:39:57.839> if<00:39:58.289> there 00:39:58.519 --> 00:39:58.529 align:start position:0% ask what you can't withdraw it if there 00:39:58.529 --> 00:40:00.650 align:start position:0% ask what you can't withdraw it if there is<00:39:58.650> a<00:39:58.680> timeout<00:39:59.099> actually<00:39:59.819> before<00:40:00.269> you<00:40:00.390> can<00:40:00.539> be 00:40:00.650 --> 00:40:00.660 align:start position:0% is a timeout actually before you can be 00:40:00.660 --> 00:40:03.049 align:start position:0% is a timeout actually before you can be tried<00:40:00.869> because<00:40:01.349> the<00:40:02.130> one<00:40:02.490> of<00:40:02.519> the<00:40:02.730> attack 00:40:03.049 --> 00:40:03.059 align:start position:0% tried because the one of the attack 00:40:03.059 --> 00:40:05.390 align:start position:0% tried because the one of the attack vectors<00:40:03.510> would<00:40:03.690> be<00:40:03.900> you<00:40:04.500> can<00:40:04.710> do<00:40:05.010> the<00:40:05.069> wrong 00:40:05.390 --> 00:40:05.400 align:start position:0% vectors would be you can do the wrong 00:40:05.400 --> 00:40:12.829 align:start position:0% vectors would be you can do the wrong enzyme<00:40:05.940> and<00:40:06.210> then<00:40:06.510> with<00:40:10.519> a<00:40:11.519> 42<00:40:12.059> yeah 00:40:12.829 --> 00:40:12.839 align:start position:0% enzyme and then with a 42 yeah 00:40:12.839 --> 00:40:14.569 align:start position:0% enzyme and then with a 42 yeah so<00:40:13.019> when<00:40:13.410> you<00:40:13.529> register<00:40:13.710> you<00:40:14.099> even<00:40:14.400> came<00:40:14.549> to 00:40:14.569 --> 00:40:14.579 align:start position:0% so when you register you even came to 00:40:14.579 --> 00:40:18.349 align:start position:0% so when you register you even came to finance<00:40:15.089> a<00:40:15.269> maybe<00:40:16.019> it<00:40:16.170> does<00:40:16.289> exploration<00:40:17.359> time 00:40:18.349 --> 00:40:18.359 align:start position:0% finance a maybe it does exploration time 00:40:18.359 --> 00:40:20.779 align:start position:0% finance a maybe it does exploration time for<00:40:18.690> maybe<00:40:18.839> one<00:40:18.960> day<00:40:19.319> or<00:40:19.859> maybe<00:40:20.010> one<00:40:20.309> hour<00:40:20.490> need 00:40:20.779 --> 00:40:20.789 align:start position:0% for maybe one day or maybe one hour need 00:40:20.789 --> 00:40:22.789 align:start position:0% for maybe one day or maybe one hour need to<00:40:20.970> find<00:40:21.210> that<00:40:21.359> this<00:40:22.019> is<00:40:22.079> also<00:40:22.289> something<00:40:22.619> that 00:40:22.789 --> 00:40:22.799 align:start position:0% to find that this is also something that 00:40:22.799 --> 00:40:25.370 align:start position:0% to find that this is also something that inclined<00:40:23.279> it's<00:40:23.490> considered<00:40:24.029> because<00:40:24.450> even<00:40:24.750> if 00:40:25.370 --> 00:40:25.380 align:start position:0% inclined it's considered because even if 00:40:25.380 --> 00:40:28.130 align:start position:0% inclined it's considered because even if I'm<00:40:25.710> getting<00:40:26.549> the<00:40:26.730> signature<00:40:27.510> from<00:40:27.690> this<00:40:27.900> guy 00:40:28.130 --> 00:40:28.140 align:start position:0% I'm getting the signature from this guy 00:40:28.140 --> 00:40:30.589 align:start position:0% I'm getting the signature from this guy I<00:40:28.440> have<00:40:28.859> only<00:40:29.190> maybe<00:40:29.400> one<00:40:29.670> hour<00:40:29.910> to<00:40:30.119> convicted 00:40:30.589 --> 00:40:30.599 align:start position:0% I have only maybe one hour to convicted 00:40:30.599 --> 00:40:31.700 align:start position:0% I have only maybe one hour to convicted if<00:40:30.750> this<00:40:30.960> is<00:40:31.049> wrong 00:40:31.700 --> 00:40:31.710 align:start position:0% if this is wrong 00:40:31.710 --> 00:40:34.250 align:start position:0% if this is wrong well<00:40:32.519> this<00:40:32.760> guy<00:40:32.940> have<00:40:33.119> little<00:40:33.480> more<00:40:33.690> time<00:40:33.960> so 00:40:34.250 --> 00:40:34.260 align:start position:0% well this guy have little more time so 00:40:34.260 --> 00:40:36.890 align:start position:0% well this guy have little more time so this<00:40:34.769> means<00:40:35.010> I<00:40:35.250> would<00:40:35.490> probably<00:40:35.730> choose<00:40:36.089> what 00:40:36.890 --> 00:40:36.900 align:start position:0% this means I would probably choose what 00:40:36.900 --> 00:40:39.470 align:start position:0% this means I would probably choose what somebody<00:40:37.289> who<00:40:37.410> has<00:40:37.559> more<00:40:37.829> time<00:40:38.130> does<00:40:39.089> come<00:40:39.329> as 00:40:39.470 --> 00:40:39.480 align:start position:0% somebody who has more time does come as 00:40:39.480 --> 00:40:42.289 align:start position:0% somebody who has more time does come as a<00:40:39.509> hurricane<00:40:39.750> as<00:40:40.230> -<00:40:40.799> it's<00:40:41.309> hot<00:40:41.700> the<00:40:41.970> impetus 00:40:42.289 --> 00:40:42.299 align:start position:0% a hurricane as - it's hot the impetus 00:40:42.299 --> 00:40:44.390 align:start position:0% a hurricane as - it's hot the impetus for<00:40:42.509> contract<00:40:43.109> information<00:40:43.529> so<00:40:44.039> he<00:40:44.160> knows 00:40:44.390 --> 00:40:44.400 align:start position:0% for contract information so he knows 00:40:44.400 --> 00:40:48.960 align:start position:0% for contract information so he knows exactly<00:40:44.779> how<00:40:45.779> long<00:40:46.019> he<00:40:46.349> could 00:40:48.960 --> 00:40:48.970 align:start position:0% 00:40:48.970 --> 00:40:54.030 align:start position:0% but<00:40:50.339> okay<00:40:51.810> now<00:40:52.810> whatever<00:40:53.319> we<00:40:53.589> explain<00:40:53.920> that 00:40:54.030 --> 00:40:54.040 align:start position:0% but okay now whatever we explain that 00:40:54.040 --> 00:40:56.579 align:start position:0% but okay now whatever we explain that this<00:40:54.220> is<00:40:54.280> a<00:40:54.430> good<00:40:54.609> poem<00:40:54.880> on<00:40:55.200> how<00:40:56.200> this<00:40:56.349> deal 00:40:56.579 --> 00:40:56.589 align:start position:0% this is a good poem on how this deal 00:40:56.589 --> 00:40:59.400 align:start position:0% this is a good poem on how this deal works<00:40:56.730> internally<00:40:57.730> because<00:40:58.660> this<00:40:58.930> is<00:40:59.050> how 00:40:59.400 --> 00:40:59.410 align:start position:0% works internally because this is how 00:40:59.410 --> 00:41:03.569 align:start position:0% works internally because this is how these<00:40:59.589> booths<00:40:59.920> actually<00:41:00.430> work<00:41:02.550> trooping<00:41:03.550> the 00:41:03.569 --> 00:41:03.579 align:start position:0% these booths actually work trooping the 00:41:03.579 --> 00:41:05.640 align:start position:0% these booths actually work trooping the information<00:41:04.240> we<00:41:04.359> get<00:41:04.510> heads<00:41:04.960> of<00:41:05.079> what<00:41:05.349> kind<00:41:05.589> of 00:41:05.640 --> 00:41:05.650 align:start position:0% information we get heads of what kind of 00:41:05.650 --> 00:41:08.309 align:start position:0% information we get heads of what kind of initially<00:41:06.040> asked<00:41:06.599> so<00:41:07.599> if<00:41:07.750> you<00:41:07.839> can<00:41:07.930> ask<00:41:08.109> for 00:41:08.309 --> 00:41:08.319 align:start position:0% initially asked so if you can ask for 00:41:08.319 --> 00:41:09.839 align:start position:0% initially asked so if you can ask for example<00:41:08.440> for<00:41:08.859> plug<00:41:09.190> that<00:41:09.430> would<00:41:09.609> be<00:41:09.730> the 00:41:09.839 --> 00:41:09.849 align:start position:0% example for plug that would be the 00:41:09.849 --> 00:41:13.380 align:start position:0% example for plug that would be the easiest<00:41:10.150> use<00:41:10.450> kids<00:41:11.099> if<00:41:12.099> you<00:41:12.220> call<00:41:12.460> ISKCON<00:41:13.030> up<00:41:13.240> a 00:41:13.380 --> 00:41:13.390 align:start position:0% easiest use kids if you call ISKCON up a 00:41:13.390 --> 00:41:16.230 align:start position:0% easiest use kids if you call ISKCON up a number<00:41:13.720> you<00:41:14.470> get<00:41:14.589> is<00:41:14.859> the<00:41:15.280> data<00:41:15.819> of<00:41:15.940> the<00:41:16.030> block 00:41:16.230 --> 00:41:16.240 align:start position:0% number you get is the data of the block 00:41:16.240 --> 00:41:18.390 align:start position:0% number you get is the data of the block head<00:41:16.420> of<00:41:16.540> an<00:41:16.690> example<00:41:17.140> the<00:41:17.890> block<00:41:18.069> cannon 00:41:18.390 --> 00:41:18.400 align:start position:0% head of an example the block cannon 00:41:18.400 --> 00:41:21.000 align:start position:0% head of an example the block cannon itself<00:41:18.670> can<00:41:19.390> be<00:41:19.540> easily<00:41:19.720> verified<00:41:19.960> all<00:41:20.829> you 00:41:21.000 --> 00:41:21.010 align:start position:0% itself can be easily verified all you 00:41:21.010 --> 00:41:25.040 align:start position:0% itself can be easily verified all you have<00:41:21.130> to<00:41:21.280> do<00:41:21.430> is<00:41:21.609> you<00:41:21.730> take<00:41:22.000> this<00:41:22.869> data<00:41:23.230> and 00:41:25.040 --> 00:41:25.050 align:start position:0% have to do is you take this data and 00:41:25.050 --> 00:41:29.040 align:start position:0% have to do is you take this data and sterilize<00:41:26.050> them<00:41:26.290> as<00:41:26.589> block<00:41:27.720> that's<00:41:28.720> the<00:41:28.900> way 00:41:29.040 --> 00:41:29.050 align:start position:0% sterilize them as block that's the way 00:41:29.050 --> 00:41:31.349 align:start position:0% sterilize them as block that's the way we<00:41:29.230> do<00:41:29.349> it<00:41:29.470> here<00:41:29.500> so<00:41:29.950> you<00:41:30.579> just<00:41:30.940> need<00:41:31.060> to<00:41:31.180> make 00:41:31.349 --> 00:41:31.359 align:start position:0% we do it here so you just need to make 00:41:31.359 --> 00:41:33.210 align:start position:0% we do it here so you just need to make sure<00:41:31.420> you<00:41:32.020> bring<00:41:32.319> it<00:41:32.470> except<00:41:32.829> in<00:41:32.980> the<00:41:33.069> right 00:41:33.210 --> 00:41:33.220 align:start position:0% sure you bring it except in the right 00:41:33.220 --> 00:41:36.390 align:start position:0% sure you bring it except in the right all<00:41:33.460> the<00:41:33.670> end<00:41:34.000> and<00:41:34.530> there<00:41:35.530> are<00:41:35.619> some<00:41:35.829> small 00:41:36.390 --> 00:41:36.400 align:start position:0% all the end and there are some small 00:41:36.400 --> 00:41:38.190 align:start position:0% all the end and there are some small things<00:41:36.430> you<00:41:36.760> have<00:41:36.880> to<00:41:36.910> consider<00:41:37.089> but<00:41:37.960> if<00:41:38.109> you 00:41:38.190 --> 00:41:38.200 align:start position:0% things you have to consider but if you 00:41:38.200 --> 00:41:41.670 align:start position:0% things you have to consider but if you do<00:41:38.319> it<00:41:38.410> right<00:41:38.589> you<00:41:39.490> can<00:41:39.520> create<00:41:40.000> the<00:41:40.990> data<00:41:41.230> I'll 00:41:41.670 --> 00:41:41.680 align:start position:0% do it right you can create the data I'll 00:41:41.680 --> 00:41:46.410 align:start position:0% do it right you can create the data I'll be<00:41:42.490> encoded<00:41:42.849> and<00:41:43.650> this<00:41:44.650> byte<00:41:44.890> array<00:41:45.130> if<00:41:45.670> you<00:41:45.819> if 00:41:46.410 --> 00:41:46.420 align:start position:0% be encoded and this byte array if you if 00:41:46.420 --> 00:41:47.160 align:start position:0% be encoded and this byte array if you if you<00:41:46.569> like 00:41:47.160 --> 00:41:47.170 align:start position:0% you like 00:41:47.170 --> 00:41:49.980 align:start position:0% you like get<00:41:47.500> a<00:41:47.530> location<00:41:48.089> so<00:41:49.089> this<00:41:49.300> means<00:41:49.540> we<00:41:49.810> can<00:41:49.960> just 00:41:49.980 --> 00:41:49.990 align:start position:0% get a location so this means we can just 00:41:49.990 --> 00:41:52.650 align:start position:0% get a location so this means we can just take<00:41:50.349> the<00:41:50.500> data<00:41:50.890> rate<00:41:51.790> the<00:41:51.880> pro<00:41:52.060> cache<00:41:52.270> then 00:41:52.650 --> 00:41:52.660 align:start position:0% take the data rate the pro cache then 00:41:52.660 --> 00:41:54.839 align:start position:0% take the data rate the pro cache then compare<00:41:53.079> the<00:41:53.230> design<00:41:53.530> projects<00:41:54.040> and<00:41:54.220> if<00:41:54.700> this 00:41:54.839 --> 00:41:54.849 align:start position:0% compare the design projects and if this 00:41:54.849 --> 00:41:55.380 align:start position:0% compare the design projects and if this is<00:41:54.970> correct 00:41:55.380 --> 00:41:55.390 align:start position:0% is correct 00:41:55.390 --> 00:41:59.370 align:start position:0% is correct you<00:41:55.569> know<00:41:55.720> the<00:41:56.500> $20<00:41:57.369> right<00:41:58.020> this<00:41:59.020> is<00:41:59.170> probably 00:41:59.370 --> 00:41:59.380 align:start position:0% you know the $20 right this is probably 00:41:59.380 --> 00:42:07.650 align:start position:0% you know the $20 right this is probably the<00:41:59.650> easiest<00:42:00.599> step<00:42:01.890> to<00:42:02.890> verify<00:42:03.400> your<00:42:04.000> data<00:42:06.660> now 00:42:07.650 --> 00:42:07.660 align:start position:0% the easiest step to verify your data now 00:42:07.660 --> 00:42:11.069 align:start position:0% the easiest step to verify your data now the<00:42:07.690> next<00:42:08.109> thing<00:42:08.260> is<00:42:08.319> transactions<00:42:09.599> if<00:42:10.599> we 00:42:11.069 --> 00:42:11.079 align:start position:0% the next thing is transactions if we 00:42:11.079 --> 00:42:13.500 align:start position:0% the next thing is transactions if we want<00:42:11.319> to<00:42:11.410> make<00:42:11.740> sure<00:42:11.770> they<00:42:12.369> would<00:42:12.550> render<00:42:12.940> from 00:42:13.500 --> 00:42:13.510 align:start position:0% want to make sure they would render from 00:42:13.510 --> 00:42:15.390 align:start position:0% want to make sure they would render from the<00:42:13.690> poison<00:42:14.020> let's<00:42:14.260> say<00:42:14.410> we<00:42:14.680> call<00:42:14.859> this<00:42:14.920> get 00:42:15.390 --> 00:42:15.400 align:start position:0% the poison let's say we call this get 00:42:15.400 --> 00:42:17.490 align:start position:0% the poison let's say we call this get transaction<00:42:16.390> perhentian<00:42:16.839> where<00:42:17.380> the 00:42:17.490 --> 00:42:17.500 align:start position:0% transaction perhentian where the 00:42:17.500 --> 00:42:19.890 align:start position:0% transaction perhentian where the transaction<00:42:17.980> data<00:42:18.099> we<00:42:18.730> wanted<00:42:19.030> now<00:42:19.300> verify 00:42:19.890 --> 00:42:19.900 align:start position:0% transaction data we wanted now verify 00:42:19.900 --> 00:42:22.710 align:start position:0% transaction data we wanted now verify that<00:42:19.960> this<00:42:20.230> thing<00:42:20.560> about<00:42:20.800> correct<00:42:21.540> what<00:42:22.540> we 00:42:22.710 --> 00:42:22.720 align:start position:0% that this thing about correct what we 00:42:22.720 --> 00:42:25.650 align:start position:0% that this thing about correct what we need<00:42:22.869> to<00:42:22.960> do<00:42:23.050> is<00:42:23.349> we<00:42:24.250> already<00:42:24.609> have<00:42:25.150> to<00:42:25.300> block 00:42:25.650 --> 00:42:25.660 align:start position:0% need to do is we already have to block 00:42:25.660 --> 00:42:27.359 align:start position:0% need to do is we already have to block anyway<00:42:26.050> also<00:42:26.349> will<00:42:26.619> always<00:42:26.920> need<00:42:27.099> to<00:42:27.160> verify 00:42:27.359 --> 00:42:27.369 align:start position:0% anyway also will always need to verify 00:42:27.369 --> 00:42:30.120 align:start position:0% anyway also will always need to verify the<00:42:27.579> project<00:42:28.000> first<00:42:28.270> and<00:42:28.540> as<00:42:29.410> one<00:42:29.680> film<00:42:29.980> the 00:42:30.120 --> 00:42:30.130 align:start position:0% the project first and as one film the 00:42:30.130 --> 00:42:31.700 align:start position:0% the project first and as one film the pocket<00:42:30.430> has<00:42:30.579> called<00:42:30.819> the<00:42:30.880> transaction<00:42:31.359> would 00:42:31.700 --> 00:42:31.710 align:start position:0% pocket has called the transaction would 00:42:31.710 --> 00:42:35.220 align:start position:0% pocket has called the transaction would the<00:42:32.710> transaction<00:42:33.250> would<00:42:33.430> is<00:42:33.579> just<00:42:33.819> a<00:42:33.910> hash<00:42:34.230> 32 00:42:35.220 --> 00:42:35.230 align:start position:0% the transaction would is just a hash 32 00:42:35.230 --> 00:42:40.510 align:start position:0% the transaction would is just a hash 32 PI<00:42:35.380> and<00:42:36.390> this<00:42:37.390> traditional 00:42:40.510 --> 00:42:40.520 align:start position:0% 00:42:40.520 --> 00:42:42.940 align:start position:0% to<00:42:41.300> be<00:42:41.420> specific<00:42:41.660> with<00:42:42.080> an<00:42:42.200> attrition<00:42:42.530> of<00:42:42.830> the 00:42:42.940 --> 00:42:42.950 align:start position:0% to be specific with an attrition of the 00:42:42.950 --> 00:42:47.830 align:start position:0% to be specific with an attrition of the tree<00:42:43.120> and<00:42:45.610> each<00:42:46.610> transaction<00:42:47.240> in<00:42:47.510> the<00:42:47.600> clock 00:42:47.830 --> 00:42:47.840 align:start position:0% tree and each transaction in the clock 00:42:47.840 --> 00:42:51.670 align:start position:0% tree and each transaction in the clock is<00:42:48.260> part<00:42:48.560> of<00:42:48.680> this<00:42:48.800> poetry<00:42:49.130> and<00:42:50.000> if<00:42:50.990> you<00:42:51.140> want 00:42:51.670 --> 00:42:51.680 align:start position:0% is part of this poetry and if you want 00:42:51.680 --> 00:42:53.470 align:start position:0% is part of this poetry and if you want want<00:42:52.130> to<00:42:52.250> verified<00:42:52.820> you<00:42:53.000> need<00:42:53.150> to<00:42:53.210> know<00:42:53.330> the 00:42:53.470 --> 00:42:53.480 align:start position:0% want to verified you need to know the 00:42:53.480 --> 00:42:55.600 align:start position:0% want to verified you need to know the path<00:42:53.690> inside<00:42:54.170> remember<00:42:54.410> tree<00:42:54.710> and<00:42:54.890> business 00:42:55.600 --> 00:42:55.610 align:start position:0% path inside remember tree and business 00:42:55.610 --> 00:42:58.660 align:start position:0% path inside remember tree and business are<00:42:56.300> included<00:42:57.080> protection<00:42:57.800> you<00:42:57.890> take<00:42:58.430> the<00:42:58.520> pen 00:42:58.660 --> 00:42:58.670 align:start position:0% are included protection you take the pen 00:42:58.670 --> 00:43:01.330 align:start position:0% are included protection you take the pen actually<00:42:58.880> index<00:42:59.330> call<00:43:00.170> all<00:43:00.380> the<00:43:00.560> encode<00:43:01.040> and 00:43:01.330 --> 00:43:01.340 align:start position:0% actually index call all the encode and 00:43:01.340 --> 00:43:02.950 align:start position:0% actually index call all the encode and then<00:43:01.910> you<00:43:02.030> have<00:43:02.120> to<00:43:02.270> pass<00:43:02.480> inside<00:43:02.900> a 00:43:02.950 --> 00:43:02.960 align:start position:0% then you have to pass inside a 00:43:02.960 --> 00:43:07.900 align:start position:0% then you have to pass inside a transaction<00:43:03.800> tree<00:43:04.870> like<00:43:05.870> this<00:43:06.100> now<00:43:07.100> the<00:43:07.550> truth 00:43:07.900 --> 00:43:07.910 align:start position:0% transaction tree like this now the truth 00:43:07.910 --> 00:43:11.710 align:start position:0% transaction tree like this now the truth they<00:43:08.480> don't<00:43:08.540> deserve<00:43:09.080> a<00:43:09.140> we'll<00:43:10.030> give<00:43:11.030> you<00:43:11.240> is 00:43:11.710 --> 00:43:11.720 align:start position:0% they don't deserve a we'll give you is 00:43:11.720 --> 00:43:15.840 align:start position:0% they don't deserve a we'll give you is just<00:43:11.960> about<00:43:12.320> the<00:43:12.500> truth<00:43:12.770> of<00:43:13.540> this<00:43:14.540> protection 00:43:15.840 --> 00:43:15.850 align:start position:0% just about the truth of this protection 00:43:15.850 --> 00:43:19.650 align:start position:0% just about the truth of this protection would<00:43:16.850> sterilize<00:43:17.180> each<00:43:17.780> node<00:43:18.200> on<00:43:18.560> the<00:43:19.310> way<00:43:19.520> to 00:43:19.650 --> 00:43:19.660 align:start position:0% would sterilize each node on the way to 00:43:19.660 --> 00:43:23.890 align:start position:0% would sterilize each node on the way to the<00:43:20.660> protection<00:43:21.170> self<00:43:21.790> we<00:43:22.790> will<00:43:22.940> have<00:43:23.120> a<00:43:23.360> look 00:43:23.890 --> 00:43:23.900 align:start position:0% the protection self we will have a look 00:43:23.900 --> 00:43:26.710 align:start position:0% the protection self we will have a look how<00:43:24.410> this<00:43:24.560> think<00:43:24.920> he<00:43:25.010> looks<00:43:25.220> like<00:43:25.510> but<00:43:26.510> this 00:43:26.710 --> 00:43:26.720 align:start position:0% how this think he looks like but this 00:43:26.720 --> 00:43:29.710 align:start position:0% how this think he looks like but this way<00:43:26.990> you<00:43:27.920> can<00:43:28.130> then<00:43:28.460> create<00:43:29.000> a<00:43:29.180> hash<00:43:29.360> of<00:43:29.510> all 00:43:29.710 --> 00:43:29.720 align:start position:0% way you can then create a hash of all 00:43:29.720 --> 00:43:32.500 align:start position:0% way you can then create a hash of all these<00:43:29.900> noise<00:43:30.110> if<00:43:30.530> this<00:43:30.740> hash<00:43:30.950> and<00:43:31.510> executed 00:43:32.500 --> 00:43:32.510 align:start position:0% these noise if this hash and executed 00:43:32.510 --> 00:43:34.510 align:start position:0% these noise if this hash and executed protection<00:43:33.290> would<00:43:33.380> you<00:43:33.950> know<00:43:34.130> what<00:43:34.280> to<00:43:34.310> do 00:43:34.510 --> 00:43:34.520 align:start position:0% protection would you know what to do 00:43:34.520 --> 00:43:37.840 align:start position:0% protection would you know what to do that's<00:43:34.640> correct<00:43:36.040> but<00:43:37.040> in<00:43:37.160> what<00:43:37.340> is<00:43:37.490> of<00:43:37.640> here 00:43:37.840 --> 00:43:37.850 align:start position:0% that's correct but in what is of here 00:43:37.850 --> 00:43:39.640 align:start position:0% that's correct but in what is of here again<00:43:38.240> the<00:43:38.540> transaction<00:43:39.050> bill<00:43:39.170> I<00:43:39.290> need<00:43:39.440> to<00:43:39.560> be 00:43:39.640 --> 00:43:39.650 align:start position:0% again the transaction bill I need to be 00:43:39.650 --> 00:43:42.160 align:start position:0% again the transaction bill I need to be sterilized<00:43:40.130> in<00:43:40.310> the<00:43:40.370> current<00:43:40.670> way<00:43:40.990> that's<00:43:41.990> the 00:43:42.160 --> 00:43:42.170 align:start position:0% sterilized in the current way that's the 00:43:42.170 --> 00:43:44.380 align:start position:0% sterilized in the current way that's the way<00:43:42.200> you<00:43:42.350> do<00:43:42.560> it<00:43:42.710> it's<00:43:43.310> estate<00:43:43.760> on<00:43:44.180> these 00:43:44.380 --> 00:43:44.390 align:start position:0% way you do it it's estate on these 00:43:44.390 --> 00:43:47.560 align:start position:0% way you do it it's estate on these values<00:43:44.720> the<00:43:45.020> nonce<00:43:45.260> the<00:43:45.530> gas<00:43:45.710> price<00:43:46.070> to<00:43:46.450> put<00:43:47.450> it 00:43:47.560 --> 00:43:47.570 align:start position:0% values the nonce the gas price to put it 00:43:47.570 --> 00:43:50.620 align:start position:0% values the nonce the gas price to put it India<00:43:47.990> whose<00:43:48.440> Albion<00:43:48.920> code<00:43:49.160> and<00:43:49.910> get<00:43:50.180> the<00:43:50.420> bar 00:43:50.620 --> 00:43:50.630 align:start position:0% India whose Albion code and get the bar 00:43:50.630 --> 00:43:53.800 align:start position:0% India whose Albion code and get the bar transaction<00:43:51.280> this<00:43:52.280> one<00:43:52.520> transaction<00:43:52.850> can 00:43:53.800 --> 00:43:53.810 align:start position:0% transaction this one transaction can 00:43:53.810 --> 00:44:00.700 align:start position:0% transaction this one transaction can then<00:43:53.990> verify<00:43:54.350> the<00:43:54.740> movie<00:43:55.690> if<00:43:56.690> this<00:43:56.930> is<00:43:57.100> correct 00:44:00.700 --> 00:44:00.710 align:start position:0% 00:44:00.710 --> 00:44:03.560 align:start position:0% the<00:44:01.710> transaction<00:44:02.310> was<00:44:02.339> c-notes<00:44:02.940> exactly<00:44:03.480> the 00:44:03.560 --> 00:44:03.570 align:start position:0% the transaction was c-notes exactly the 00:44:03.570 --> 00:44:06.200 align:start position:0% the transaction was c-notes exactly the same<00:44:03.780> way<00:44:03.990> so<00:44:04.290> if<00:44:05.280> I<00:44:05.339> ask<00:44:05.550> for<00:44:05.640> transaction 00:44:06.200 --> 00:44:06.210 align:start position:0% same way so if I ask for transaction 00:44:06.210 --> 00:44:09.829 align:start position:0% same way so if I ask for transaction receipt<00:44:06.530> we<00:44:07.530> does<00:44:08.520> a<00:44:08.550> different<00:44:09.329> field<00:44:09.630> in<00:44:09.750> the 00:44:09.829 --> 00:44:09.839 align:start position:0% receipt we does a different field in the 00:44:09.839 --> 00:44:11.930 align:start position:0% receipt we does a different field in the block<00:44:10.020> and<00:44:10.170> escorted<00:44:10.650> to<00:44:10.920> the<00:44:11.040> seafood<00:44:11.490> and 00:44:11.930 --> 00:44:11.940 align:start position:0% block and escorted to the seafood and 00:44:11.940 --> 00:44:15.040 align:start position:0% block and escorted to the seafood and then<00:44:12.570> we<00:44:12.690> can<00:44:12.900> verify<00:44:13.290> it<00:44:13.619> exactly<00:44:14.430> only 00:44:15.040 --> 00:44:15.050 align:start position:0% then we can verify it exactly only 00:44:15.050 --> 00:44:17.900 align:start position:0% then we can verify it exactly only difference<00:44:16.050> here<00:44:16.170> is<00:44:16.500> the<00:44:17.190> way<00:44:17.369> we<00:44:17.550> sterilize 00:44:17.900 --> 00:44:17.910 align:start position:0% difference here is the way we sterilize 00:44:17.910 --> 00:44:21.620 align:start position:0% difference here is the way we sterilize it<00:44:18.349> DBC<00:44:19.349> desert<00:44:19.829> that<00:44:20.790> two<00:44:21.119> different<00:44:21.450> fields 00:44:21.620 --> 00:44:21.630 align:start position:0% it DBC desert that two different fields 00:44:21.630 --> 00:44:25.099 align:start position:0% it DBC desert that two different fields have<00:44:22.170> events<00:44:23.130> for<00:44:23.190> example<00:44:23.339> are<00:44:24.030> all<00:44:24.510> part<00:44:24.869> of 00:44:25.099 --> 00:44:25.109 align:start position:0% have events for example are all part of 00:44:25.109 --> 00:44:27.589 align:start position:0% have events for example are all part of this<00:44:25.410> protection<00:44:26.310> c2<00:44:27.119> need<00:44:27.300> to<00:44:27.390> sterilize 00:44:27.589 --> 00:44:27.599 align:start position:0% this protection c2 need to sterilize 00:44:27.599 --> 00:44:28.780 align:start position:0% this protection c2 need to sterilize them<00:44:28.020> as<00:44:28.170> well 00:44:28.780 --> 00:44:28.790 align:start position:0% them as well 00:44:28.790 --> 00:44:32.690 align:start position:0% them as well this<00:44:29.790> code<00:44:30.000> will<00:44:30.210> give<00:44:30.599> you<00:44:30.780> the<00:44:31.589> raw<00:44:31.800> bytes 00:44:32.690 --> 00:44:32.700 align:start position:0% this code will give you the raw bytes 00:44:32.700 --> 00:44:35.210 align:start position:0% this code will give you the raw bytes for<00:44:33.540> the<00:44:33.599> transaction<00:44:34.170> receipt<00:44:34.290> which<00:44:34.800> is<00:44:34.980> 10 00:44:35.210 --> 00:44:35.220 align:start position:0% for the transaction receipt which is 10 00:44:35.220 --> 00:44:41.100 align:start position:0% for the transaction receipt which is 10 poverty's<00:44:36.020> look<00:44:37.020> at<00:44:37.109> the<00:44:37.170> tree 00:44:41.100 --> 00:44:41.110 align:start position:0% 00:44:41.110 --> 00:44:43.260 align:start position:0% then<00:44:41.740> the<00:44:42.010> next<00:44:42.250> thing<00:44:42.370> is<00:44:42.730> with<00:44:42.880> you<00:44:43.030> call 00:44:43.260 --> 00:44:43.270 align:start position:0% then the next thing is with you call 00:44:43.270 --> 00:44:46.320 align:start position:0% then the next thing is with you call each<00:44:43.960> get<00:44:44.230> balanced<00:44:44.620> myself<00:44:45.070> or<00:44:45.610> you<00:44:46.030> get 00:44:46.320 --> 00:44:46.330 align:start position:0% each get balanced myself or you get 00:44:46.330 --> 00:44:48.480 align:start position:0% each get balanced myself or you get storage<00:44:46.780> that<00:44:46.990> or<00:44:47.590> get<00:44:47.920> friends<00:44:48.310> actually 00:44:48.480 --> 00:44:48.490 align:start position:0% storage that or get friends actually 00:44:48.490 --> 00:44:51.570 align:start position:0% storage that or get friends actually count<00:44:48.990> these<00:44:49.990> information<00:44:50.680> they<00:44:51.220> come<00:44:51.460> from 00:44:51.570 --> 00:44:51.580 align:start position:0% count these information they come from 00:44:51.580 --> 00:44:53.910 align:start position:0% count these information they come from the<00:44:51.730> account<00:44:52.060> object<00:44:52.470> and<00:44:53.470> then<00:44:53.590> account 00:44:53.910 --> 00:44:53.920 align:start position:0% the account object and then account 00:44:53.920 --> 00:44:56.970 align:start position:0% the account object and then account object<00:44:54.130> are<00:44:54.730> verified<00:44:55.570> as<00:44:56.200> all<00:44:56.410> apart<00:44:56.740> from 00:44:56.970 --> 00:44:56.980 align:start position:0% object are verified as all apart from 00:44:56.980 --> 00:44:59.010 align:start position:0% object are verified as all apart from the<00:44:57.100> retreat<00:44:57.370> by<00:44:57.610> the<00:44:57.670> different<00:44:58.060> one<00:44:58.180> this<00:44:58.840> is 00:44:59.010 --> 00:44:59.020 align:start position:0% the retreat by the different one this is 00:44:59.020 --> 00:45:02.190 align:start position:0% the retreat by the different one this is a<00:44:59.050> statement<00:44:59.640> so<00:45:00.640> if<00:45:00.790> we're<00:45:01.000> in<00:45:01.210> statehood<00:45:01.630> as 00:45:02.190 --> 00:45:02.200 align:start position:0% a statement so if we're in statehood as 00:45:02.200 --> 00:45:04.980 align:start position:0% a statement so if we're in statehood as part<00:45:02.560> of<00:45:02.710> them<00:45:02.920> the<00:45:03.160> prop<00:45:03.340> Hanna<00:45:03.690> and<00:45:04.690> then<00:45:04.870> you 00:45:04.980 --> 00:45:04.990 align:start position:0% part of them the prop Hanna and then you 00:45:04.990 --> 00:45:07.730 align:start position:0% part of them the prop Hanna and then you have<00:45:05.110> this<00:45:05.320> mode<00:45:05.590> tree<00:45:05.890> where<00:45:06.580> Ali's<00:45:07.030> accounts 00:45:07.730 --> 00:45:07.740 align:start position:0% have this mode tree where Ali's accounts 00:45:07.740 --> 00:45:14.250 align:start position:0% have this mode tree where Ali's accounts upon<00:45:08.970> stolen<00:45:09.970> so<00:45:10.930> it's<00:45:11.200> him<00:45:11.910> then<00:45:12.960> she<00:45:13.960> count 00:45:14.250 --> 00:45:14.260 align:start position:0% upon stolen so it's him then she count 00:45:14.260 --> 00:45:17.460 align:start position:0% upon stolen so it's him then she count it<00:45:15.190> has<00:45:15.550> four<00:45:16.060> fields<00:45:16.450> we<00:45:16.630> have<00:45:16.750> to<00:45:16.870> dance<00:45:17.080> of 00:45:17.460 --> 00:45:17.470 align:start position:0% it has four fields we have to dance of 00:45:17.470 --> 00:45:19.440 align:start position:0% it has four fields we have to dance of the<00:45:17.530> transaction<00:45:18.160> count<00:45:18.400> we<00:45:19.150> have<00:45:19.270> their 00:45:19.440 --> 00:45:19.450 align:start position:0% the transaction count we have their 00:45:19.450 --> 00:45:22.860 align:start position:0% the transaction count we have their balance<00:45:19.930> after<00:45:20.410> account<00:45:20.980> the<00:45:21.880> storage<00:45:22.360> nation 00:45:22.860 --> 00:45:22.870 align:start position:0% balance after account the storage nation 00:45:22.870 --> 00:45:26.640 align:start position:0% balance after account the storage nation which<00:45:23.710> is<00:45:23.920> again<00:45:24.610> in<00:45:24.880> the<00:45:25.150> mutant<00:45:25.600> for<00:45:25.900> another 00:45:26.640 --> 00:45:26.650 align:start position:0% which is again in the mutant for another 00:45:26.650 --> 00:45:30.690 align:start position:0% which is again in the mutant for another country<00:45:27.300> and<00:45:28.300> left<00:45:28.570> cortex<00:45:29.130> in<00:45:30.130> case<00:45:30.370> that<00:45:30.520> is 00:45:30.690 --> 00:45:30.700 align:start position:0% country and left cortex in case that is 00:45:30.700 --> 00:45:33.030 align:start position:0% country and left cortex in case that is code<00:45:30.940> doesn't<00:45:31.570> is<00:45:31.810> that<00:45:31.990> more<00:45:32.410> code<00:45:32.620> and<00:45:32.860> we 00:45:33.030 --> 00:45:33.040 align:start position:0% code doesn't is that more code and we 00:45:33.040 --> 00:45:35.690 align:start position:0% code doesn't is that more code and we get<00:45:33.220> always<00:45:33.460> this<00:45:33.760> fixed<00:45:34.540> value<00:45:34.870> for<00:45:34.900> rotation 00:45:35.690 --> 00:45:35.700 align:start position:0% get always this fixed value for rotation 00:45:35.700 --> 00:45:38.690 align:start position:0% get always this fixed value for rotation the<00:45:36.700> h4<00:45:37.030> empty<00:45:37.540> cold 00:45:38.690 --> 00:45:38.700 align:start position:0% the h4 empty cold 00:45:38.700 --> 00:45:42.930 align:start position:0% the h4 empty cold so<00:45:39.700> if<00:45:40.390> you<00:45:40.630> so<00:45:41.440> you<00:45:41.500> can<00:45:41.740> help<00:45:41.920> verify<00:45:42.130> they 00:45:42.930 --> 00:45:42.940 align:start position:0% so if you so you can help verify they 00:45:42.940 --> 00:45:44.190 align:start position:0% so if you so you can help verify they counted<00:45:43.630> out<00:45:43.750> correct 00:45:44.190 --> 00:45:44.200 align:start position:0% counted out correct 00:45:44.200 --> 00:45:46.500 align:start position:0% counted out correct it<00:45:44.530> wasn't<00:45:44.950> long<00:45:45.070> about<00:45:45.340> this<00:45:45.550> is<00:45:46.240> for<00:45:46.420> example 00:45:46.500 --> 00:45:46.510 align:start position:0% it wasn't long about this is for example 00:45:46.510 --> 00:45:49.500 align:start position:0% it wasn't long about this is for example than<00:45:46.900> the<00:45:47.530> stomach<00:45:47.920> cash<00:45:48.190> that<00:45:48.640> we<00:45:48.910> need<00:45:49.240> to 00:45:49.500 --> 00:45:49.510 align:start position:0% than the stomach cash that we need to 00:45:49.510 --> 00:45:52.620 align:start position:0% than the stomach cash that we need to verify<00:45:49.720> that<00:45:50.490> did<00:45:51.490> not<00:45:51.760> and<00:45:51.940> his<00:45:52.090> last<00:45:52.360> year 00:45:52.620 --> 00:45:52.630 align:start position:0% verify that did not and his last year 00:45:52.630 --> 00:45:55.530 align:start position:0% verify that did not and his last year and<00:45:52.810> was<00:45:53.800> not<00:45:54.040> really<00:45:54.370> part<00:45:54.670> of<00:45:54.820> any<00:45:55.240> how 00:45:55.530 --> 00:45:55.540 align:start position:0% and was not really part of any how 00:45:55.540 --> 00:45:57.870 align:start position:0% and was not really part of any how physically<00:45:56.170> you<00:45:56.590> were<00:45:56.830> not<00:45:57.040> able<00:45:57.250> to<00:45:57.400> get<00:45:57.640> this 00:45:57.870 --> 00:45:57.880 align:start position:0% physically you were not able to get this 00:45:57.880 --> 00:46:02.160 align:start position:0% physically you were not able to get this information<00:45:58.150> to<00:45:58.660> RBC<00:45:59.520> so<00:46:00.520> that<00:46:01.330> was<00:46:01.870> one 00:46:02.160 --> 00:46:02.170 align:start position:0% information to RBC so that was one 00:46:02.170 --> 00:46:03.660 align:start position:0% information to RBC so that was one reason<00:46:02.410> why<00:46:02.980> we<00:46:03.400> need 00:46:03.660 --> 00:46:03.670 align:start position:0% reason why we need 00:46:03.670 --> 00:46:05.849 align:start position:0% reason why we need another<00:46:03.880> function<00:46:04.420> for<00:46:04.809> that<00:46:04.859> and 00:46:05.849 --> 00:46:05.859 align:start position:0% another function for that and 00:46:05.859 --> 00:46:08.880 align:start position:0% another function for that and dysfunction<00:46:06.119> that's<00:46:07.119> why<00:46:07.299> we<00:46:08.020> created<00:46:08.740> this 00:46:08.880 --> 00:46:08.890 align:start position:0% dysfunction that's why we created this 00:46:08.890 --> 00:46:12.450 align:start position:0% dysfunction that's why we created this VIP<00:46:09.190> from<00:46:10.119> East<00:46:10.390> get<00:46:10.660> proof<00:46:10.990> and<00:46:11.460> I 00:46:12.450 --> 00:46:12.460 align:start position:0% VIP from East get proof and I 00:46:12.460 --> 00:46:15.660 align:start position:0% VIP from East get proof and I implemented<00:46:13.260> full<00:46:14.260> crest<00:46:14.589> for<00:46:14.920> gas<00:46:15.280> it<00:46:15.490> was<00:46:15.640> a 00:46:15.660 --> 00:46:15.670 align:start position:0% implemented full crest for gas it was a 00:46:15.670 --> 00:46:18.510 align:start position:0% implemented full crest for gas it was a cavity<00:46:16.470> and<00:46:17.470> then<00:46:17.650> they<00:46:17.799> were<00:46:17.920> up 00:46:18.510 --> 00:46:18.520 align:start position:0% cavity and then they were up 00:46:18.520 --> 00:46:20.549 align:start position:0% cavity and then they were up so<00:46:18.819> it's<00:46:18.970> in<00:46:19.150> there's<00:46:19.359> at<00:46:19.869> least<00:46:20.079> for<00:46:20.260> almost<00:46:20.440> a 00:46:20.549 --> 00:46:20.559 align:start position:0% so it's in there's at least for almost a 00:46:20.559 --> 00:46:22.740 align:start position:0% so it's in there's at least for almost a year<00:46:20.589> now<00:46:20.799> and<00:46:21.160> you<00:46:21.940> can<00:46:22.150> truth<00:46:22.359> is<00:46:22.540> exactly 00:46:22.740 --> 00:46:22.750 align:start position:0% year now and you can truth is exactly 00:46:22.750 --> 00:46:25.559 align:start position:0% year now and you can truth is exactly the<00:46:23.230> spectrum<00:46:23.650> it<00:46:23.770> will<00:46:23.980> he<00:46:24.700> developed<00:46:25.359> rules 00:46:25.559 --> 00:46:25.569 align:start position:0% the spectrum it will he developed rules 00:46:25.569 --> 00:46:28.230 align:start position:0% the spectrum it will he developed rules if<00:46:25.930> you<00:46:26.380> need<00:46:26.530> for<00:46:26.740> that<00:46:26.890> the<00:46:27.819> other<00:46:27.940> things 00:46:28.230 --> 00:46:28.240 align:start position:0% if you need for that the other things 00:46:28.240 --> 00:46:30.690 align:start position:0% if you need for that the other things for<00:46:28.359> the<00:46:28.569> transaction<00:46:29.140> and<00:46:29.470> traffic<00:46:30.069> Lucy<00:46:30.369> is 00:46:30.690 --> 00:46:30.700 align:start position:0% for the transaction and traffic Lucy is 00:46:30.700 --> 00:46:31.920 align:start position:0% for the transaction and traffic Lucy is something<00:46:31.030> you<00:46:31.119> can<00:46:31.299> build<00:46:31.420> up<00:46:31.540> from<00:46:31.780> the 00:46:31.920 --> 00:46:31.930 align:start position:0% something you can build up from the 00:46:31.930 --> 00:46:33.930 align:start position:0% something you can build up from the existing<00:46:32.319> data<00:46:32.500> you<00:46:33.160> can<00:46:33.280> just<00:46:33.309> collect<00:46:33.640> all 00:46:33.930 --> 00:46:33.940 align:start position:0% existing data you can just collect all 00:46:33.940 --> 00:46:35.460 align:start position:0% existing data you can just collect all the<00:46:34.030> transactions<00:46:34.569> each<00:46:34.720> stratum<00:46:35.049> oh<00:46:35.319> good 00:46:35.460 --> 00:46:35.470 align:start position:0% the transactions each stratum oh good 00:46:35.470 --> 00:46:38.309 align:start position:0% the transactions each stratum oh good free<00:46:35.710> and<00:46:35.920> and<00:46:36.790> get<00:46:37.000> through<00:46:37.270> but<00:46:37.660> here<00:46:38.020> you 00:46:38.309 --> 00:46:38.319 align:start position:0% free and and get through but here you 00:46:38.319 --> 00:46:40.230 align:start position:0% free and and get through but here you need<00:46:38.470> the<00:46:38.619> special<00:46:38.829> function<00:46:39.339> this<00:46:39.700> is<00:46:39.730> now<00:46:40.000> in 00:46:40.230 --> 00:46:40.240 align:start position:0% need the special function this is now in 00:46:40.240 --> 00:46:42.839 align:start position:0% need the special function this is now in there<00:46:40.450> and<00:46:40.720> I<00:46:41.680> guess<00:46:42.040> which<00:46:42.250> has<00:46:42.369> been<00:46:42.520> put<00:46:42.819> a 00:46:42.839 --> 00:46:42.849 align:start position:0% there and I guess which has been put a 00:46:42.849 --> 00:46:44.069 align:start position:0% there and I guess which has been put a little<00:46:43.089> more<00:46:43.329> now<00:46:43.540> to<00:46:43.720> make<00:46:43.900> it<00:46:43.930> official 00:46:44.069 --> 00:46:44.079 align:start position:0% little more now to make it official 00:46:44.079 --> 00:46:48.539 align:start position:0% little more now to make it official because<00:46:44.559> it's<00:46:45.339> still<00:46:45.700> trapped<00:46:47.160> it<00:46:48.160> should<00:46:48.369> go 00:46:48.539 --> 00:46:48.549 align:start position:0% because it's still trapped it should go 00:46:48.549 --> 00:46:52.609 align:start position:0% because it's still trapped it should go through<00:46:48.730> a<00:46:49.569> lot<00:46:50.079> of<00:46:50.170> people<00:46:50.440> already<00:46:50.559> using<00:46:51.069> it 00:46:52.609 --> 00:46:52.619 align:start position:0% through a lot of people already using it 00:46:52.619 --> 00:46:55.770 align:start position:0% through a lot of people already using it yeah<00:46:53.619> once<00:46:53.920> it's<00:46:54.280> why<00:46:54.460> we<00:46:54.730> here<00:46:55.299> like<00:46:55.540> two 00:46:55.770 --> 00:46:55.780 align:start position:0% yeah once it's why we here like two 00:46:55.780 --> 00:46:58.319 align:start position:0% yeah once it's why we here like two steps<00:46:56.020> actually<00:46:56.380> for<00:46:56.740> a<00:46:56.829> count<00:46:57.130> of<00:46:57.280> ten<00:46:57.520> first 00:46:58.319 --> 00:46:58.329 align:start position:0% steps actually for a count of ten first 00:46:58.329 --> 00:47:00.750 align:start position:0% steps actually for a count of ten first we<00:46:58.480> verify<00:46:58.630> the<00:46:58.930> account<00:46:59.200> object<00:46:59.490> and<00:47:00.490> then 00:47:00.750 --> 00:47:00.760 align:start position:0% we verify the account object and then 00:47:00.760 --> 00:47:04.740 align:start position:0% we verify the account object and then all<00:47:01.750> the<00:47:01.930> storage<00:47:02.290> values<00:47:02.770> did<00:47:02.950> you<00:47:03.069> meet<00:47:03.750> this 00:47:04.740 --> 00:47:04.750 align:start position:0% all the storage values did you meet this 00:47:04.750 --> 00:47:07.829 align:start position:0% all the storage values did you meet this one<00:47:04.960> contract<00:47:05.440> are<00:47:05.920> also<00:47:06.250> stored<00:47:06.819> in<00:47:07.150> the<00:47:07.540> tree 00:47:07.829 --> 00:47:07.839 align:start position:0% one contract are also stored in the tree 00:47:07.839 --> 00:47:13.200 align:start position:0% one contract are also stored in the tree and<00:47:08.430> this<00:47:09.430> tree<00:47:09.670> is<00:47:10.599> that<00:47:10.660> particle<00:47:11.849> so<00:47:12.849> you<00:47:13.000> go 00:47:13.200 --> 00:47:13.210 align:start position:0% and this tree is that particle so you go 00:47:13.210 --> 00:47:19.130 align:start position:0% and this tree is that particle so you go two<00:47:13.809> steps<00:47:14.049> yeah<00:47:17.130> yeah<00:47:18.130> this<00:47:18.430> is<00:47:18.579> how<00:47:18.760> you 00:47:19.130 --> 00:47:19.140 align:start position:0% two steps yeah yeah this is how you 00:47:19.140 --> 00:47:24.240 align:start position:0% two steps yeah yeah this is how you paralyze<00:47:20.140> the<00:47:20.290> account<00:47:20.559> object 00:47:24.240 --> 00:47:24.250 align:start position:0% 00:47:24.250 --> 00:47:29.440 align:start position:0% go<00:47:25.250> and<00:47:25.849> ask<00:47:26.859> that's<00:47:27.859> some<00:47:28.490> small<00:47:28.790> things<00:47:29.089> to 00:47:29.440 --> 00:47:29.450 align:start position:0% go and ask that's some small things to 00:47:29.450 --> 00:47:32.260 align:start position:0% go and ask that's some small things to have<00:47:29.690> to<00:47:29.810> watch<00:47:30.380> out<00:47:30.589> for<00:47:30.790> example<00:47:31.790> events<00:47:32.119> and 00:47:32.260 --> 00:47:32.270 align:start position:0% have to watch out for example events and 00:47:32.270 --> 00:47:35.500 align:start position:0% have to watch out for example events and then<00:47:32.420> if<00:47:33.140> this<00:47:33.380> doesn't<00:47:33.589> exist<00:47:34.010> that<00:47:34.510> that 00:47:35.500 --> 00:47:35.510 align:start position:0% then if this doesn't exist that that 00:47:35.510 --> 00:47:37.180 align:start position:0% then if this doesn't exist that that doesn't<00:47:35.690> mean<00:47:35.869> you<00:47:35.960> get<00:47:36.079> zero<00:47:36.440> out<00:47:36.710> of<00:47:36.740> it 00:47:37.180 --> 00:47:37.190 align:start position:0% doesn't mean you get zero out of it 00:47:37.190 --> 00:47:40.329 align:start position:0% doesn't mean you get zero out of it usually<00:47:37.490> because<00:47:37.940> you<00:47:37.970> get<00:47:38.390> the<00:47:39.349> nth<00:47:39.950> temp 00:47:40.329 --> 00:47:40.339 align:start position:0% usually because you get the nth temp 00:47:40.339 --> 00:47:41.890 align:start position:0% usually because you get the nth temp that's<00:47:40.640> why<00:47:40.790> it's<00:47:41.000> checks<00:47:41.329> if<00:47:41.599> it's<00:47:41.750> in<00:47:41.869> that 00:47:41.890 --> 00:47:41.900 align:start position:0% that's why it's checks if it's in that 00:47:41.900 --> 00:47:44.260 align:start position:0% that's why it's checks if it's in that existing<00:47:42.530> want<00:47:43.160> you<00:47:43.490> to<00:47:43.609> a<00:47:43.640> different<00:47:44.000> kind<00:47:44.119> of 00:47:44.260 --> 00:47:44.270 align:start position:0% existing want you to a different kind of 00:47:44.270 --> 00:47:45.700 align:start position:0% existing want you to a different kind of proof<00:47:44.510> because<00:47:44.990> this<00:47:45.200> was<00:47:45.319> more<00:47:45.500> than<00:47:45.530> a 00:47:45.700 --> 00:47:45.710 align:start position:0% proof because this was more than a 00:47:45.710 --> 00:47:48.520 align:start position:0% proof because this was more than a challenge<00:47:46.160> there<00:47:46.720> we<00:47:47.720> are<00:47:47.839> the<00:47:47.960> tools<00:47:48.260> are 00:47:48.520 --> 00:47:48.530 align:start position:0% challenge there we are the tools are 00:47:48.530 --> 00:47:51.819 align:start position:0% challenge there we are the tools are great<00:47:48.770> but<00:47:49.640> the<00:47:49.790> challenge<00:47:50.119> is<00:47:50.180> how<00:47:50.510> to<00:47:50.829> verify 00:47:51.819 --> 00:47:51.829 align:start position:0% great but the challenge is how to verify 00:47:51.829 --> 00:47:54.099 align:start position:0% great but the challenge is how to verify something<00:47:52.190> does<00:47:52.490> not<00:47:52.700> exist<00:47:53.210> for<00:47:53.569> example 00:47:54.099 --> 00:47:54.109 align:start position:0% something does not exist for example 00:47:54.109 --> 00:47:56.349 align:start position:0% something does not exist for example device<00:47:54.560> called<00:47:55.220> East<00:47:55.550> get<00:47:55.760> balanced<00:47:56.119> and<00:47:56.240> get 00:47:56.349 --> 00:47:56.359 align:start position:0% device called East get balanced and get 00:47:56.359 --> 00:47:58.300 align:start position:0% device called East get balanced and get zero<00:47:56.660> how<00:47:57.230> do<00:47:57.290> you<00:47:57.380> have<00:47:57.500> verified<00:47:57.829> with<00:47:58.280> the 00:47:58.300 --> 00:47:58.310 align:start position:0% zero how do you have verified with the 00:47:58.310 --> 00:48:00.880 align:start position:0% zero how do you have verified with the whirlpool<00:47:58.819> then<00:47:59.359> this<00:48:00.109> is<00:48:00.319> correct<00:48:00.650> and<00:48:00.800> it 00:48:00.880 --> 00:48:00.890 align:start position:0% whirlpool then this is correct and it 00:48:00.890 --> 00:48:02.559 align:start position:0% whirlpool then this is correct and it works<00:48:01.160> you<00:48:01.520> can<00:48:01.670> do<00:48:01.790> it<00:48:01.940> but<00:48:02.150> you<00:48:02.180> can<00:48:02.390> with<00:48:02.540> a 00:48:02.559 --> 00:48:02.569 align:start position:0% works you can do it but you can with a 00:48:02.569 --> 00:48:05.230 align:start position:0% works you can do it but you can with a Patricia<00:48:02.990> movie<00:48:03.319> three<00:48:03.760> either<00:48:04.760> to<00:48:04.940> a<00:48:04.970> little 00:48:05.230 --> 00:48:05.240 align:start position:0% Patricia movie three either to a little 00:48:05.240 --> 00:48:08.069 align:start position:0% Patricia movie three either to a little bit<00:48:05.359> tricky<00:48:05.660> to<00:48:05.869> figure<00:48:06.710> out<00:48:07.040> the 00:48:08.069 --> 00:48:08.079 align:start position:0% bit tricky to figure out the 00:48:08.079 --> 00:48:11.530 align:start position:0% bit tricky to figure out the correlations<00:48:09.079> where<00:48:09.730> you<00:48:10.730> can't<00:48:11.030> be<00:48:11.240> sure 00:48:11.530 --> 00:48:11.540 align:start position:0% correlations where you can't be sure 00:48:11.540 --> 00:48:13.839 align:start position:0% correlations where you can't be sure that<00:48:11.569> this<00:48:12.319> cannot<00:48:12.800> exist<00:48:13.220> because<00:48:13.430> there's 00:48:13.839 --> 00:48:13.849 align:start position:0% that this cannot exist because there's 00:48:13.849 --> 00:48:16.559 align:start position:0% that this cannot exist because there's remove<00:48:14.180> branches<00:48:14.450> and<00:48:14.839> some<00:48:15.530> French<00:48:15.800> nodes<00:48:16.160> is 00:48:16.559 --> 00:48:16.569 align:start position:0% remove branches and some French nodes is 00:48:16.569 --> 00:48:20.470 align:start position:0% remove branches and some French nodes is dimensional<00:48:17.599> for<00:48:17.780> example<00:48:18.170> lead<00:48:18.829> 2-0<00:48:19.609> mehendi 00:48:20.470 --> 00:48:20.480 align:start position:0% dimensional for example lead 2-0 mehendi 00:48:20.480 --> 00:48:24.380 align:start position:0% dimensional for example lead 2-0 mehendi branch<00:48:20.780> can<00:48:21.050> you<00:48:21.170> know<00:48:21.319> a<00:48:21.589> can<00:48:22.130> it<00:48:22.250> sister 00:48:24.380 --> 00:48:24.390 align:start position:0% branch can you know a can it sister 00:48:24.390 --> 00:48:26.359 align:start position:0% branch can you know a can it sister [Music] 00:48:26.359 --> 00:48:26.369 align:start position:0% [Music] 00:48:26.369 --> 00:48:29.280 align:start position:0% [Music] yeah<00:48:27.369> then<00:48:27.640> the<00:48:28.030> hardest<00:48:28.330> one<00:48:28.630> was<00:48:28.990> actually 00:48:29.280 --> 00:48:29.290 align:start position:0% yeah then the hardest one was actually 00:48:29.290 --> 00:48:32.339 align:start position:0% yeah then the hardest one was actually there<00:48:29.470> the<00:48:30.400> truth<00:48:30.640> for<00:48:30.910> youth<00:48:31.060> coal<00:48:31.349> because 00:48:32.339 --> 00:48:32.349 align:start position:0% there the truth for youth coal because 00:48:32.349 --> 00:48:36.120 align:start position:0% there the truth for youth coal because if<00:48:32.560> you<00:48:32.650> calling<00:48:32.980> a<00:48:33.040> function<00:48:34.859> you<00:48:35.859> need<00:48:36.010> to 00:48:36.120 --> 00:48:36.130 align:start position:0% if you calling a function you need to 00:48:36.130 --> 00:48:38.370 align:start position:0% if you calling a function you need to execute<00:48:36.430> it<00:48:36.730> locally<00:48:37.480> there<00:48:37.780> is<00:48:37.930> no<00:48:38.109> way<00:48:38.320> you 00:48:38.370 --> 00:48:38.380 align:start position:0% execute it locally there is no way you 00:48:38.380 --> 00:48:40.890 align:start position:0% execute it locally there is no way you can<00:48:38.710> simply<00:48:39.130> run<00:48:39.849> the<00:48:39.880> proof<00:48:40.270> on<00:48:40.510> the<00:48:40.690> door 00:48:40.890 --> 00:48:40.900 align:start position:0% can simply run the proof on the door 00:48:40.900 --> 00:48:45.000 align:start position:0% can simply run the proof on the door time<00:48:41.200> to<00:48:41.550> verify<00:48:42.550> the<00:48:42.609> truth<00:48:43.560> so<00:48:44.560> what<00:48:44.740> we<00:48:44.890> did 00:48:45.000 --> 00:48:45.010 align:start position:0% time to verify the truth so what we did 00:48:45.010 --> 00:48:47.580 align:start position:0% time to verify the truth so what we did here<00:48:45.070> is<00:48:46.030> the<00:48:46.900> first<00:48:47.109> thing<00:48:47.290> is<00:48:47.410> to<00:48:47.560> know 00:48:47.580 --> 00:48:47.590 align:start position:0% here is the first thing is to know 00:48:47.590 --> 00:48:49.890 align:start position:0% here is the first thing is to know itself<00:48:48.160> it's<00:48:48.520> collect<00:48:49.030> all<00:48:49.210> the<00:48:49.300> proofs 00:48:49.890 --> 00:48:49.900 align:start position:0% itself it's collect all the proofs 00:48:49.900 --> 00:48:54.960 align:start position:0% itself it's collect all the proofs how<00:48:50.890> does<00:48:51.070> it<00:48:51.099> work<00:48:51.780> for<00:48:53.220> cavity<00:48:54.220> we<00:48:54.760> used 00:48:54.960 --> 00:48:54.970 align:start position:0% how does it work for cavity we used 00:48:54.970 --> 00:48:57.540 align:start position:0% how does it work for cavity we used actually<00:48:55.359> a<00:48:55.450> trace<00:48:55.840> calls<00:48:56.190> which<00:48:57.190> is<00:48:57.340> quite 00:48:57.540 --> 00:48:57.550 align:start position:0% actually a trace calls which is quite 00:48:57.550 --> 00:48:58.080 align:start position:0% actually a trace calls which is quite nice 00:48:58.080 --> 00:48:58.090 align:start position:0% nice 00:48:58.090 --> 00:49:00.750 align:start position:0% nice meaning<00:48:58.930> we<00:48:59.170> are<00:48:59.200> asperity<00:48:59.740> it<00:49:00.250> give<00:49:00.609> us<00:49:00.730> a 00:49:00.750 --> 00:49:00.760 align:start position:0% meaning we are asperity it give us a 00:49:00.760 --> 00:49:04.650 align:start position:0% meaning we are asperity it give us a trace<00:49:01.119> of<00:49:01.420> this<00:49:01.599> call<00:49:02.260> and<00:49:02.560> we<00:49:03.210> went<00:49:04.210> to<00:49:04.359> each 00:49:04.650 --> 00:49:04.660 align:start position:0% trace of this call and we went to each 00:49:04.660 --> 00:49:07.500 align:start position:0% trace of this call and we went to each of<00:49:04.900> court<00:49:05.200> and<00:49:05.440> look<00:49:06.040> at<00:49:06.160> whenever<00:49:06.609> we<00:49:06.880> found 00:49:07.500 --> 00:49:07.510 align:start position:0% of court and look at whenever we found 00:49:07.510 --> 00:49:10.620 align:start position:0% of court and look at whenever we found something<00:49:07.900> that<00:49:08.820> they<00:49:09.820> realize<00:49:10.330> that<00:49:10.510> some 00:49:10.620 --> 00:49:10.630 align:start position:0% something that they realize that some 00:49:10.630 --> 00:49:12.839 align:start position:0% something that they realize that some kind<00:49:10.869> of<00:49:10.930> storage<00:49:11.170> value<00:49:11.590> then<00:49:12.369> we<00:49:12.520> know<00:49:12.670> we 00:49:12.839 --> 00:49:12.849 align:start position:0% kind of storage value then we know we 00:49:12.849 --> 00:49:14.820 align:start position:0% kind of storage value then we know we need<00:49:13.000> to<00:49:13.090> verify<00:49:13.300> this<00:49:13.660> we<00:49:14.380> need<00:49:14.530> to<00:49:14.619> create<00:49:14.800> a 00:49:14.820 --> 00:49:14.830 align:start position:0% need to verify this we need to create a 00:49:14.830 --> 00:49:18.450 align:start position:0% need to verify this we need to create a proof<00:49:15.310> of<00:49:15.430> this<00:49:15.580> torture<00:49:16.170> or<00:49:17.170> even<00:49:17.440> if<00:49:18.250> there's 00:49:18.450 --> 00:49:18.460 align:start position:0% proof of this torture or even if there's 00:49:18.460 --> 00:49:20.940 align:start position:0% proof of this torture or even if there's a<00:49:18.550> balance<00:49:18.910> of<00:49:19.060> cold<00:49:19.359> as<00:49:19.599> a<00:49:19.660> so<00:49:20.020> Apple<00:49:20.410> s<00:49:20.619> load 00:49:20.940 --> 00:49:20.950 align:start position:0% a balance of cold as a so Apple s load 00:49:20.950 --> 00:49:23.849 align:start position:0% a balance of cold as a so Apple s load or<00:49:21.310> I<00:49:21.609> will<00:49:21.970> call<00:49:22.240> some<00:49:22.630> other<00:49:22.690> contracts<00:49:23.349> we 00:49:23.849 --> 00:49:23.859 align:start position:0% or I will call some other contracts we 00:49:23.859 --> 00:49:25.950 align:start position:0% or I will call some other contracts we collect<00:49:24.220> them<00:49:24.460> and<00:49:24.670> then<00:49:25.330> continue<00:49:25.780> through 00:49:25.950 --> 00:49:25.960 align:start position:0% collect them and then continue through 00:49:25.960 --> 00:49:28.680 align:start position:0% collect them and then continue through the<00:49:26.020> process<00:49:26.500> so<00:49:27.400> then<00:49:27.550> we<00:49:27.670> have<00:49:27.820> a<00:49:27.849> and<00:49:28.240> just 00:49:28.680 --> 00:49:28.690 align:start position:0% the process so then we have a and just 00:49:28.690 --> 00:49:34.230 align:start position:0% the process so then we have a and just the<00:49:28.840> proof<00:49:29.080> all<00:49:29.349> the<00:49:29.730> storage<00:49:30.730> is<00:49:32.369> class<00:49:33.369> we 00:49:34.230 --> 00:49:34.240 align:start position:0% the proof all the storage is class we 00:49:34.240 --> 00:49:36.170 align:start position:0% the proof all the storage is class we needed<00:49:34.510> of<00:49:34.630> course<00:49:34.660> the<00:49:35.410> code<00:49:35.619> itself 00:49:36.170 --> 00:49:36.180 align:start position:0% needed of course the code itself 00:49:36.180 --> 00:49:39.720 align:start position:0% needed of course the code itself this<00:49:37.180> can<00:49:37.900> be<00:49:38.050> cached<00:49:38.290> at<00:49:38.500> least<00:49:38.710> so<00:49:39.400> the 00:49:39.720 --> 00:49:39.730 align:start position:0% this can be cached at least so the 00:49:39.730 --> 00:49:41.910 align:start position:0% this can be cached at least so the client<00:49:40.330> has<00:49:40.450> that<00:49:40.599> we<00:49:40.720> tell<00:49:40.930> her<00:49:41.140> to<00:49:41.260> education 00:49:41.910 --> 00:49:41.920 align:start position:0% client has that we tell her to education 00:49:41.920 --> 00:49:44.849 align:start position:0% client has that we tell her to education the<00:49:42.339> code<00:49:42.550> every<00:49:43.300> time<00:49:43.510> the<00:49:44.320> code<00:49:44.500> can<00:49:44.710> be 00:49:44.849 --> 00:49:44.859 align:start position:0% the code every time the code can be 00:49:44.859 --> 00:49:46.410 align:start position:0% the code every time the code can be easily<00:49:45.010> verified<00:49:45.369> because<00:49:45.790> we<00:49:46.030> have<00:49:46.150> to<00:49:46.240> call 00:49:46.410 --> 00:49:46.420 align:start position:0% easily verified because we have to call 00:49:46.420 --> 00:49:48.950 align:start position:0% easily verified because we have to call attention<00:49:46.480> as<00:49:46.960> part<00:49:47.200> of<00:49:47.230> their<00:49:47.440> account<00:49:48.310> truth 00:49:48.950 --> 00:49:48.960 align:start position:0% attention as part of their account truth 00:49:48.960 --> 00:49:51.660 align:start position:0% attention as part of their account truth so<00:49:49.960> after<00:49:50.260> we<00:49:50.349> collected<00:49:50.770> all<00:49:50.859> of<00:49:51.190> this<00:49:51.339> then 00:49:51.660 --> 00:49:51.670 align:start position:0% so after we collected all of this then 00:49:51.670 --> 00:49:54.410 align:start position:0% so after we collected all of this then the<00:49:51.790> client<00:49:52.359> needs<00:49:52.900> to<00:49:52.990> go<00:49:53.230> through<00:49:53.619> and 00:49:54.410 --> 00:49:54.420 align:start position:0% the client needs to go through and 00:49:54.420 --> 00:49:57.690 align:start position:0% the client needs to go through and execute<00:49:55.420> the<00:49:56.200> code<00:49:56.410> itself<00:49:56.830> this<00:49:57.400> means 00:49:57.690 --> 00:49:57.700 align:start position:0% execute the code itself this means 00:49:57.700 --> 00:49:59.550 align:start position:0% execute the code itself this means that's<00:49:57.970> what<00:49:58.240> is<00:49:58.359> called<00:49:58.630> kind<00:49:59.080> of<00:49:59.200> Cho<00:49:59.349> Seon 00:49:59.550 --> 00:49:59.560 align:start position:0% that's what is called kind of Cho Seon 00:49:59.560 --> 00:50:03.180 align:start position:0% that's what is called kind of Cho Seon what<00:50:00.430> we<00:50:00.550> did<00:50:01.089> here<00:50:01.330> is<00:50:01.359> VM<00:50:01.990> credit<00:50:02.650> and<00:50:02.890> above 00:50:03.180 --> 00:50:03.190 align:start position:0% what we did here is VM credit and above 00:50:03.190 --> 00:50:06.960 align:start position:0% what we did here is VM credit and above the<00:50:03.280> tree<00:50:03.510> we<00:50:04.510> created<00:50:04.869> in<00:50:05.020> new<00:50:05.200> EVM<00:50:05.680> to<00:50:06.520> verify 00:50:06.960 --> 00:50:06.970 align:start position:0% the tree we created in new EVM to verify 00:50:06.970 --> 00:50:08.940 align:start position:0% the tree we created in new EVM to verify that<00:50:07.270> we<00:50:07.810> went<00:50:08.020> through<00:50:08.200> all<00:50:08.230> the<00:50:08.530> comp 00:50:08.940 --> 00:50:08.950 align:start position:0% that we went through all the comp 00:50:08.950 --> 00:50:12.240 align:start position:0% that we went through all the comp objects<00:50:09.520> in<00:50:09.880> quantities<00:50:10.570> data<00:50:11.140> in<00:50:11.530> this 00:50:12.240 --> 00:50:12.250 align:start position:0% objects in quantities data in this 00:50:12.250 --> 00:50:15.690 align:start position:0% objects in quantities data in this and<00:50:13.440> after<00:50:14.440> this<00:50:14.590> we<00:50:14.830> create<00:50:15.099> a<00:50:15.280> transaction 00:50:15.690 --> 00:50:15.700 align:start position:0% and after this we create a transaction 00:50:15.700 --> 00:50:19.500 align:start position:0% and after this we create a transaction and<00:50:16.210> ran<00:50:16.869> it<00:50:16.990> in<00:50:17.140> this<00:50:17.230> together<00:50:17.710> and<00:50:18.609> then 00:50:19.500 --> 00:50:19.510 align:start position:0% and ran it in this together and then 00:50:19.510 --> 00:50:21.870 align:start position:0% and ran it in this together and then afterwards<00:50:20.260> we<00:50:20.290> just<00:50:20.590> pick<00:50:21.310> up<00:50:21.400> the<00:50:21.550> result 00:50:21.870 --> 00:50:21.880 align:start position:0% afterwards we just pick up the result 00:50:21.880 --> 00:50:24.300 align:start position:0% afterwards we just pick up the result but<00:50:22.869> it's<00:50:23.109> a<00:50:23.200> little<00:50:23.349> bit<00:50:23.470> simplified<00:50:23.830> but 00:50:24.300 --> 00:50:24.310 align:start position:0% but it's a little bit simplified but 00:50:24.310 --> 00:50:27.030 align:start position:0% but it's a little bit simplified but it's<00:50:24.490> basic<00:50:25.119> what<00:50:25.270> we<00:50:25.359> do<00:50:25.560> and<00:50:26.560> it's<00:50:26.770> what<00:50:26.950> the 00:50:27.030 --> 00:50:27.040 align:start position:0% it's basic what we do and it's what the 00:50:27.040 --> 00:50:29.460 align:start position:0% it's basic what we do and it's what the tax<00:50:27.280> plan<00:50:27.760> is<00:50:27.970> to<00:50:28.119> keep<00:50:28.930> in<00:50:29.080> the<00:50:29.170> time<00:50:29.349> scale 00:50:29.460 --> 00:50:29.470 align:start position:0% tax plan is to keep in the time scale 00:50:29.470 --> 00:50:32.300 align:start position:0% tax plan is to keep in the time scale and<00:50:29.680> we<00:50:29.890> used<00:50:30.070> a<00:50:30.280> steam<00:50:30.700> she<00:50:30.940> has<00:50:31.060> a<00:50:31.240> limitation 00:50:32.300 --> 00:50:32.310 align:start position:0% and we used a steam she has a limitation 00:50:32.310 --> 00:50:34.349 align:start position:0% and we used a steam she has a limitation we<00:50:33.310> don't<00:50:33.490> want<00:50:33.670> to<00:50:33.730> be<00:50:33.820> able<00:50:33.970> to<00:50:34.119> be<00:50:34.330> a 00:50:34.349 --> 00:50:34.359 align:start position:0% we don't want to be able to be a 00:50:34.359 --> 00:50:36.839 align:start position:0% we don't want to be able to be a platform<00:50:34.690> for<00:50:35.200> the<00:50:36.190> C<00:50:36.400> client<00:50:36.580> we<00:50:36.820> have 00:50:36.839 --> 00:50:36.849 align:start position:0% platform for the C client we have 00:50:36.849 --> 00:50:40.410 align:start position:0% platform for the C client we have implement<00:50:37.440> house<00:50:38.440> ups<00:50:38.710> because<00:50:39.099> this<00:50:39.730> is<00:50:39.880> not 00:50:40.410 --> 00:50:40.420 align:start position:0% implement house ups because this is not 00:50:40.420 --> 00:50:42.960 align:start position:0% implement house ups because this is not the<00:50:40.540> same<00:50:40.750> way<00:50:40.930> so<00:50:41.619> example<00:50:42.190> first<00:50:42.760> of<00:50:42.849> all 00:50:42.960 --> 00:50:42.970 align:start position:0% the same way so example first of all 00:50:42.970 --> 00:50:45.870 align:start position:0% the same way so example first of all verify<00:50:43.420> everything<00:50:43.630> and<00:50:44.080> then<00:50:44.520> won<00:50:45.520> the<00:50:45.550> Court 00:50:45.870 --> 00:50:45.880 align:start position:0% verify everything and then won the Court 00:50:45.880 --> 00:50:49.320 align:start position:0% verify everything and then won the Court itself<00:50:46.170> in<00:50:47.170> what<00:50:47.619> running<00:50:47.980> it<00:50:48.640> also<00:50:48.849> needs<00:50:49.150> to 00:50:49.320 --> 00:50:49.330 align:start position:0% itself in what running it also needs to 00:50:49.330 --> 00:50:52.460 align:start position:0% itself in what running it also needs to check<00:50:49.570> for<00:50:49.750> example<00:50:50.050> if<00:50:50.500> all<00:50:51.220> the<00:50:51.580> values 00:50:52.460 --> 00:50:52.470 align:start position:0% check for example if all the values 00:50:52.470 --> 00:50:56.640 align:start position:0% check for example if all the values needed<00:50:53.470> apology<00:50:54.869> it<00:50:55.869> cannot<00:50:56.109> be<00:50:56.349> anything 00:50:56.640 --> 00:50:56.650 align:start position:0% needed apology it cannot be anything 00:50:56.650 --> 00:51:03.030 align:start position:0% needed apology it cannot be anything that's<00:50:56.920> terrifying 00:51:03.030 --> 00:51:03.040 align:start position:0% 00:51:03.040 --> 00:51:05.190 align:start position:0% because<00:51:03.760> we<00:51:03.940> need<00:51:04.060> about<00:51:04.270> codes<00:51:04.510> we<00:51:04.840> didn't 00:51:05.190 --> 00:51:05.200 align:start position:0% because we need about codes we didn't 00:51:05.200 --> 00:51:09.359 align:start position:0% because we need about codes we didn't know<00:51:05.380> which<00:51:07.020> of<00:51:08.020> course<00:51:08.080> will<00:51:08.560> be<00:51:08.710> executed 00:51:09.359 --> 00:51:09.369 align:start position:0% know which of course will be executed 00:51:09.369 --> 00:51:12.330 align:start position:0% know which of course will be executed when<00:51:09.640> you<00:51:09.790> do<00:51:09.940> this<00:51:10.090> is<00:51:10.300> goal<00:51:10.980> to<00:51:11.980> because<00:51:12.220> we 00:51:12.330 --> 00:51:12.340 align:start position:0% when you do this is goal to because we 00:51:12.340 --> 00:51:14.370 align:start position:0% when you do this is goal to because we need<00:51:12.460> to<00:51:12.520> find<00:51:12.700> it<00:51:12.880> as<00:51:13.000> load<00:51:13.270> and<00:51:13.600> balance<00:51:14.170> of 00:51:14.370 --> 00:51:14.380 align:start position:0% need to find it as load and balance of 00:51:14.380 --> 00:51:16.920 align:start position:0% need to find it as load and balance of great<00:51:14.619> self<00:51:14.890> and<00:51:15.130> then<00:51:15.790> is<00:51:16.330> called<00:51:16.660> at<00:51:16.780> least 00:51:16.920 --> 00:51:16.930 align:start position:0% great self and then is called at least 00:51:16.930 --> 00:51:19.590 align:start position:0% great self and then is called at least makes<00:51:17.470> it<00:51:17.619> easy<00:51:17.859> because<00:51:18.130> you<00:51:18.369> get<00:51:18.730> it<00:51:18.850> all<00:51:19.030> in 00:51:19.590 --> 00:51:19.600 align:start position:0% makes it easy because you get it all in 00:51:19.600 --> 00:51:21.420 align:start position:0% makes it easy because you get it all in one<00:51:19.660> week<00:51:19.990> rest<00:51:20.230> and<00:51:20.950> then<00:51:21.070> we<00:51:21.190> absolutely 00:51:21.420 --> 00:51:21.430 align:start position:0% one week rest and then we absolutely 00:51:21.430 --> 00:51:23.640 align:start position:0% one week rest and then we absolutely need<00:51:21.820> to<00:51:21.910> find<00:51:22.180> the<00:51:22.330> ones<00:51:22.540> and<00:51:22.810> people<00:51:23.140> collect 00:51:23.640 --> 00:51:23.650 align:start position:0% need to find the ones and people collect 00:51:23.650 --> 00:51:26.220 align:start position:0% need to find the ones and people collect the<00:51:23.830> food<00:51:25.030> a<00:51:25.180> bit<00:51:25.390> if<00:51:25.630> again<00:51:25.900> it's<00:51:26.140> a 00:51:26.220 --> 00:51:26.230 align:start position:0% the food a bit if again it's a 00:51:26.230 --> 00:51:29.970 align:start position:0% the food a bit if again it's a little<00:51:26.440> bit<00:51:26.530> more<00:51:27.869> difficult<00:51:28.869> because<00:51:29.020> these 00:51:29.970 --> 00:51:29.980 align:start position:0% little bit more difficult because these 00:51:29.980 --> 00:51:33.690 align:start position:0% little bit more difficult because these trace<00:51:30.400> functions<00:51:30.970> that<00:51:31.869> gets<00:51:32.560> us<00:51:32.890> currently 00:51:33.690 --> 00:51:33.700 align:start position:0% trace functions that gets us currently 00:51:33.700 --> 00:51:36.660 align:start position:0% trace functions that gets us currently supporting<00:51:34.470> only<00:51:35.470> for<00:51:35.830> existing<00:51:36.280> transaction 00:51:36.660 --> 00:51:36.670 align:start position:0% supporting only for existing transaction 00:51:36.670 --> 00:51:38.940 align:start position:0% supporting only for existing transaction but<00:51:37.000> there<00:51:37.180> are<00:51:37.300> already<00:51:37.510> mind<00:51:37.960> it<00:51:38.650> doesn't 00:51:38.940 --> 00:51:38.950 align:start position:0% but there are already mind it doesn't 00:51:38.950 --> 00:51:41.700 align:start position:0% but there are already mind it doesn't help<00:51:39.070> with<00:51:39.220> it<00:51:39.400> it's<00:51:39.730> gone<00:51:39.940> that's<00:51:40.690> why<00:51:41.050> what 00:51:41.700 --> 00:51:41.710 align:start position:0% help with it it's gone that's why what 00:51:41.710 --> 00:51:43.290 align:start position:0% help with it it's gone that's why what we<00:51:41.740> do<00:51:41.980> at<00:51:42.250> the<00:51:42.310> moment<00:51:42.340> it's<00:51:42.850> a<00:51:42.940> little<00:51:43.150> bit 00:51:43.290 --> 00:51:43.300 align:start position:0% we do at the moment it's a little bit 00:51:43.300 --> 00:51:46.109 align:start position:0% we do at the moment it's a little bit slow<00:51:43.600> and<00:51:44.470> because<00:51:45.310> we<00:51:45.460> get<00:51:45.640> to<00:51:45.820> the<00:51:45.910> code 00:51:46.109 --> 00:51:46.119 align:start position:0% slow and because we get to the code 00:51:46.119 --> 00:51:48.720 align:start position:0% slow and because we get to the code execute<00:51:47.050> code<00:51:47.290> whenever<00:51:47.650> we<00:51:48.010> hit<00:51:48.220> something 00:51:48.720 --> 00:51:48.730 align:start position:0% execute code whenever we hit something 00:51:48.730 --> 00:51:52.020 align:start position:0% execute code whenever we hit something out<00:51:49.630> of<00:51:49.869> court<00:51:50.140> make<00:51:50.260> simpler<00:51:50.619> then<00:51:51.310> we<00:51:51.520> ask<00:51:51.700> it 00:51:52.020 --> 00:51:52.030 align:start position:0% out of court make simpler then we ask it 00:51:52.030 --> 00:51:55.260 align:start position:0% out of court make simpler then we ask it give<00:51:52.780> us<00:51:52.990> the<00:51:53.530> storage<00:51:54.010> value<00:51:54.369> and<00:51:55.119> then<00:51:55.240> we 00:51:55.260 --> 00:51:55.270 align:start position:0% give us the storage value and then we 00:51:55.270 --> 00:51:57.270 align:start position:0% give us the storage value and then we collect<00:51:55.690> this<00:51:56.080> in<00:51:56.290> this<00:51:56.410> way<00:51:56.560> but<00:51:56.800> this<00:51:57.010> means 00:51:57.270 --> 00:51:57.280 align:start position:0% collect this in this way but this means 00:51:57.280 --> 00:52:00.330 align:start position:0% collect this in this way but this means it<00:51:57.790> is<00:51:58.150> way<00:51:58.780> slower<00:51:58.990> because<00:51:59.560> you<00:51:59.890> need<00:52:00.040> more 00:52:00.330 --> 00:52:00.340 align:start position:0% it is way slower because you need more 00:52:00.340 --> 00:52:07.400 align:start position:0% it is way slower because you need more than<00:52:00.490> one<00:52:00.550> request<00:52:01.030> for<00:52:01.270> getting 00:52:07.400 --> 00:52:07.410 align:start position:0% 00:52:07.410 --> 00:52:10.430 align:start position:0% Norwich<00:52:08.250> storage<00:52:09.240> unit<00:52:09.509> ascendant<00:52:09.960> Integra 00:52:10.430 --> 00:52:10.440 align:start position:0% Norwich storage unit ascendant Integra 00:52:10.440 --> 00:52:12.920 align:start position:0% Norwich storage unit ascendant Integra yeah<00:52:11.130> so<00:52:11.430> that's<00:52:11.579> why<00:52:11.759> the<00:52:11.819> canola<00:52:12.390> collectors 00:52:12.920 --> 00:52:12.930 align:start position:0% yeah so that's why the canola collectors 00:52:12.930 --> 00:52:15.710 align:start position:0% yeah so that's why the canola collectors it<00:52:13.559> has<00:52:13.710> all<00:52:13.920> information<00:52:14.490> but<00:52:14.640> the<00:52:15.299> stateless 00:52:15.710 --> 00:52:15.720 align:start position:0% it has all information but the stateless 00:52:15.720 --> 00:52:18.099 align:start position:0% it has all information but the stateless client<00:52:16.200> needs<00:52:16.829> to<00:52:16.859> receive<00:52:17.220> all<00:52:17.490> information 00:52:18.099 --> 00:52:18.109 align:start position:0% client needs to receive all information 00:52:18.109 --> 00:52:21.259 align:start position:0% client needs to receive all information needed<00:52:19.109> to<00:52:19.319> toe<00:52:19.619> area<00:52:19.890> fries<00:52:20.250> within<00:52:21.180> the 00:52:21.259 --> 00:52:21.269 align:start position:0% needed to toe area fries within the 00:52:21.269 --> 00:52:29.720 align:start position:0% needed to toe area fries within the response<00:52:23.509> that's<00:52:24.509> why<00:52:24.829> that's<00:52:25.829> how<00:52:26.039> he's<00:52:26.220> cold 00:52:29.720 --> 00:52:29.730 align:start position:0% 00:52:29.730 --> 00:52:31.240 align:start position:0% [Music] 00:52:31.240 --> 00:52:31.250 align:start position:0% [Music] 00:52:31.250 --> 00:52:34.540 align:start position:0% [Music] okay<00:52:32.030> let's<00:52:32.720> do<00:52:32.990> some<00:52:33.500> practical<00:52:33.890> things<00:52:34.010> I 00:52:34.540 --> 00:52:34.550 align:start position:0% okay let's do some practical things I 00:52:34.550 --> 00:52:40.250 align:start position:0% okay let's do some practical things I don't<00:52:34.820> know<00:52:34.910> how<00:52:35.660> many<00:52:35.720> of<00:52:35.930> you<00:52:35.960> actually 00:52:40.250 --> 00:52:40.260 align:start position:0% 00:52:40.260 --> 00:52:44.099 align:start position:0% but<00:52:41.260> what<00:52:41.740> I'd<00:52:41.830> like<00:52:41.859> to<00:52:42.040> do<00:52:42.250> is<00:52:42.430> I<00:52:43.270> would<00:52:43.990> like 00:52:44.099 --> 00:52:44.109 align:start position:0% but what I'd like to do is I would like 00:52:44.109 --> 00:52:48.060 align:start position:0% but what I'd like to do is I would like to<00:52:44.260> go<00:52:44.470> through<00:52:44.609> to<00:52:45.609> manually<00:52:46.180> verify<00:52:47.080> just 00:52:48.060 --> 00:52:48.070 align:start position:0% to go through to manually verify just 00:52:48.070 --> 00:52:49.530 align:start position:0% to go through to manually verify just look<00:52:48.250> for<00:52:48.339> the<00:52:48.400> transaction<00:52:48.880> I<00:52:49.089> think<00:52:49.390> it's 00:52:49.530 --> 00:52:49.540 align:start position:0% look for the transaction I think it's 00:52:49.540 --> 00:52:51.359 align:start position:0% look for the transaction I think it's very<00:52:49.869> interesting<00:52:50.290> this<00:52:50.950> to<00:52:51.099> it<00:52:51.190> at<00:52:51.280> least 00:52:51.359 --> 00:52:51.369 align:start position:0% very interesting this to it at least 00:52:51.369 --> 00:52:53.430 align:start position:0% very interesting this to it at least once<00:52:51.670> I<00:52:51.880> mean<00:52:52.030> I<00:52:52.150> I<00:52:52.390> hate<00:52:52.570> to<00:52:52.690> do<00:52:52.839> it<00:52:52.960> a<00:52:53.140> lot<00:52:53.410> of 00:52:53.430 --> 00:52:53.440 align:start position:0% once I mean I I hate to do it a lot of 00:52:53.440 --> 00:52:55.589 align:start position:0% once I mean I I hate to do it a lot of times<00:52:53.740> when<00:52:54.460> I<00:52:54.490> was<00:52:54.730> debugging<00:52:55.359> all<00:52:55.510> this 00:52:55.589 --> 00:52:55.599 align:start position:0% times when I was debugging all this 00:52:55.599 --> 00:52:58.410 align:start position:0% times when I was debugging all this stuff<00:52:55.810> really<00:52:56.140> something<00:52:57.040> says<00:52:57.550> okay<00:52:57.880> the 00:52:58.410 --> 00:52:58.420 align:start position:0% stuff really something says okay the 00:52:58.420 --> 00:53:03.210 align:start position:0% stuff really something says okay the hash<00:52:58.599> doesn't<00:52:58.990> match<00:52:59.560> nice<00:53:00.510> why<00:53:01.530> so<00:53:02.530> it's<00:53:02.980> why 00:53:03.210 --> 00:53:03.220 align:start position:0% hash doesn't match nice why so it's why 00:53:03.220 --> 00:53:05.310 align:start position:0% hash doesn't match nice why so it's why when<00:53:03.520> you<00:53:03.609> go<00:53:03.790> to<00:53:03.940> the<00:53:04.089> mill<00:53:04.300> the<00:53:04.480> trees<00:53:04.720> and<00:53:05.200> to 00:53:05.310 --> 00:53:05.320 align:start position:0% when you go to the mill the trees and to 00:53:05.320 --> 00:53:06.870 align:start position:0% when you go to the mill the trees and to all<00:53:05.470> these<00:53:05.589> things<00:53:05.770> but<00:53:06.010> when<00:53:06.430> you<00:53:06.550> do<00:53:06.700> this 00:53:06.870 --> 00:53:06.880 align:start position:0% all these things but when you do this 00:53:06.880 --> 00:53:08.700 align:start position:0% all these things but when you do this you<00:53:07.119> really<00:53:07.390> try<00:53:07.750> to<00:53:07.780> understand<00:53:08.320> how<00:53:08.530> this 00:53:08.700 --> 00:53:08.710 align:start position:0% you really try to understand how this 00:53:08.710 --> 00:53:10.140 align:start position:0% you really try to understand how this one<00:53:08.890> fits<00:53:08.920> together<00:53:09.250> I<00:53:09.609> think<00:53:09.849> it's<00:53:09.970> very 00:53:10.140 --> 00:53:10.150 align:start position:0% one fits together I think it's very 00:53:10.150 --> 00:53:14.730 align:start position:0% one fits together I think it's very interesting<00:53:11.430> do<00:53:12.430> it<00:53:12.520> at<00:53:12.640> least<00:53:12.790> once<00:53:12.940> here<00:53:13.740> to 00:53:14.730 --> 00:53:14.740 align:start position:0% interesting do it at least once here to 00:53:14.740 --> 00:53:17.640 align:start position:0% interesting do it at least once here to go<00:53:15.190> through<00:53:15.430> that<00:53:15.520> to<00:53:15.700> actually<00:53:16.630> manually<00:53:16.960> go 00:53:17.640 --> 00:53:17.650 align:start position:0% go through that to actually manually go 00:53:17.650 --> 00:53:20.070 align:start position:0% go through that to actually manually go to<00:53:17.710> a<00:53:17.859> real<00:53:18.070> good<00:53:18.250> proof<00:53:18.640> and<00:53:18.970> see<00:53:19.300> how<00:53:20.020> this 00:53:20.070 --> 00:53:20.080 align:start position:0% to a real good proof and see how this 00:53:20.080 --> 00:53:21.770 align:start position:0% to a real good proof and see how this works 00:53:21.770 --> 00:53:21.780 align:start position:0% works 00:53:21.780 --> 00:53:34.210 align:start position:0% works okay 00:53:34.210 --> 00:53:34.220 align:start position:0% 00:53:34.220 --> 00:53:39.850 align:start position:0% okay<00:53:35.560> so<00:53:36.560> if<00:53:37.040> you<00:53:37.310> for<00:53:38.090> example<00:53:38.320> can<00:53:39.320> start<00:53:39.710> to 00:53:39.850 --> 00:53:39.860 align:start position:0% okay so if you for example can start to 00:53:39.860 --> 00:53:45.430 align:start position:0% okay so if you for example can start to talk<00:53:40.010> to<00:53:40.220> them<00:53:40.370> you<00:53:40.520> can<00:53:40.670> also<00:53:40.850> do<00:53:41.090> it 00:53:45.430 --> 00:53:45.440 align:start position:0% 00:53:45.440 --> 00:53:50.510 align:start position:0% [Music] 00:53:50.510 --> 00:53:50.520 align:start position:0% 00:53:50.520 --> 00:53:54.060 align:start position:0% a<00:53:50.550> decision<00:53:51.570> you<00:53:51.960> see<00:53:52.140> one<00:53:52.410> screen 00:53:54.060 --> 00:53:54.070 align:start position:0% a decision you see one screen 00:53:54.070 --> 00:53:58.470 align:start position:0% a decision you see one screen good<00:53:54.640> is<00:53:54.820> it<00:53:54.970> hope<00:53:55.210> it<00:53:55.900> gets<00:53:56.050> his<00:53:56.290> Camaro<00:53:57.030> I<00:53:58.030> get 00:53:58.470 --> 00:53:58.480 align:start position:0% good is it hope it gets his Camaro I get 00:53:58.480 --> 00:54:02.190 align:start position:0% good is it hope it gets his Camaro I get hospitalized<00:53:59.080> just<00:53:59.800> the<00:54:00.160> very<00:54:00.460> top<00:54:01.200> the 00:54:02.190 --> 00:54:02.200 align:start position:0% hospitalized just the very top the 00:54:02.200 --> 00:54:05.100 align:start position:0% hospitalized just the very top the plenty<00:54:02.590> the<00:54:02.740> right<00:54:02.920> home<00:54:03.310> for<00:54:03.340> the<00:54:03.640> right<00:54:04.110> to 00:54:05.100 --> 00:54:05.110 align:start position:0% plenty the right home for the right to 00:54:05.110 --> 00:54:07.860 align:start position:0% plenty the right home for the right to the<00:54:05.200> net<00:54:05.350> Delta<00:54:05.530> team<00:54:05.770> site<00:54:06.660> probably<00:54:07.660> miss 00:54:07.860 --> 00:54:07.870 align:start position:0% the net Delta team site probably miss 00:54:07.870 --> 00:54:11.030 align:start position:0% the net Delta team site probably miss your<00:54:07.900> presentation 00:54:11.030 --> 00:54:11.040 align:start position:0% 00:54:11.040 --> 00:54:24.060 align:start position:0% escape<00:54:12.040> the<00:54:12.070> presentation<00:54:12.790> one 00:54:24.060 --> 00:54:24.070 align:start position:0% 00:54:24.070 --> 00:54:29.220 align:start position:0% tuck<00:54:24.700> it<00:54:25.380> so<00:54:26.610> so<00:54:27.610> what<00:54:27.730> existed<00:54:28.270> here<00:54:28.540> thought 00:54:29.220 --> 00:54:29.230 align:start position:0% tuck it so so what existed here thought 00:54:29.230 --> 00:54:31.560 align:start position:0% tuck it so so what existed here thought the<00:54:29.470> same<00:54:29.680> time<00:54:29.860> container<00:54:30.280> that<00:54:30.790> we 00:54:31.560 --> 00:54:31.570 align:start position:0% the same time container that we 00:54:31.570 --> 00:54:36.230 align:start position:0% the same time container that we mentioned<00:54:31.960> here<00:54:32.110> beginning<00:54:32.850> and<00:54:33.850> as<00:54:34.800> part<00:54:35.800> of 00:54:36.230 --> 00:54:36.240 align:start position:0% mentioned here beginning and as part of 00:54:36.240 --> 00:54:39.300 align:start position:0% mentioned here beginning and as part of decency<00:54:37.240> China<00:54:37.600> was<00:54:37.810> a<00:54:37.840> small<00:54:38.200> beautiful<00:54:38.680> that 00:54:39.300 --> 00:54:39.310 align:start position:0% decency China was a small beautiful that 00:54:39.310 --> 00:54:41.910 align:start position:0% decency China was a small beautiful that this<00:54:40.030> is<00:54:40.210> Allah<00:54:40.450> P<00:54:40.660> utility<00:54:41.200> I<00:54:41.290> can<00:54:41.590> simply 00:54:41.910 --> 00:54:41.920 align:start position:0% this is Allah P utility I can simply 00:54:41.920 --> 00:54:46.820 align:start position:0% this is Allah P utility I can simply given<00:54:42.330> any<00:54:43.330> data<00:54:43.630> and<00:54:44.020> it<00:54:44.200> will<00:54:44.700> automatically 00:54:46.820 --> 00:54:46.830 align:start position:0% given any data and it will automatically 00:54:46.830 --> 00:54:51.230 align:start position:0% given any data and it will automatically not<00:54:47.830> like<00:54:48.160> ok<00:54:48.490> pika 00:54:51.230 --> 00:54:51.240 align:start position:0% 00:54:51.240 --> 00:54:53.190 align:start position:0% even<00:54:52.240> though<00:54:52.360> pickup<00:54:52.660> will<00:54:52.780> be<00:54:52.900> hot<00:54:53.080> because 00:54:53.190 --> 00:54:53.200 align:start position:0% even though pickup will be hot because 00:54:53.200 --> 00:54:55.800 align:start position:0% even though pickup will be hot because you<00:54:53.440> see<00:54:53.560> will<00:54:53.920> see<00:54:54.100> a<00:54:54.130> lot<00:54:54.340> of<00:54:54.370> numbers<00:54:54.810> ok 00:54:55.800 --> 00:54:55.810 align:start position:0% you see will see a lot of numbers ok 00:54:55.810 --> 00:55:09.120 align:start position:0% you see will see a lot of numbers ok let's<00:54:56.020> see<00:54:56.200> if<00:54:56.290> it<00:54:56.440> fits<00:54:56.590> in<00:54:56.860> there 00:55:09.120 --> 00:55:09.130 align:start position:0% 00:55:09.130 --> 00:55:20.439 align:start position:0% [Music] 00:55:20.439 --> 00:55:20.449 align:start position:0% 00:55:20.449 --> 00:55:23.559 align:start position:0% let's<00:55:20.989> pick<00:55:21.459> something<00:55:22.459> that<00:55:22.489> also<00:55:23.180> to<00:55:23.329> show 00:55:23.559 --> 00:55:23.569 align:start position:0% let's pick something that also to show 00:55:23.569 --> 00:55:26.769 align:start position:0% let's pick something that also to show you<00:55:23.630> all<00:55:24.699> the<00:55:25.699> stills<00:55:25.940> nation<00:55:26.239> from<00:55:26.329> all<00:55:26.449> test 00:55:26.769 --> 00:55:26.779 align:start position:0% you all the stills nation from all test 00:55:26.779 --> 00:55:33.079 align:start position:0% you all the stills nation from all test data 00:55:33.079 --> 00:55:33.089 align:start position:0% 00:55:33.089 --> 00:55:36.670 align:start position:0% so 00:55:36.670 --> 00:55:36.680 align:start position:0% 00:55:36.680 --> 00:55:40.930 align:start position:0% this<00:55:37.250> is<00:55:37.579> a<00:55:38.440> request<00:55:39.440> a<00:55:39.890> transaction<00:55:40.520> by<00:55:40.640> hench 00:55:40.930 --> 00:55:40.940 align:start position:0% this is a request a transaction by hench 00:55:40.940 --> 00:55:45.210 align:start position:0% this is a request a transaction by hench as<00:55:41.150> you<00:55:41.270> can<00:55:41.450> see<00:55:41.599> here<00:55:41.839> and<00:55:42.369> the<00:55:43.369> result<00:55:43.760> is 00:55:45.210 --> 00:55:45.220 align:start position:0% as you can see here and the result is 00:55:45.220 --> 00:55:49.720 align:start position:0% as you can see here and the result is the<00:55:46.220> transaction<00:55:46.609> data<00:55:47.299> itself<00:55:47.839> and<00:55:48.579> this<00:55:49.579> is 00:55:49.720 --> 00:55:49.730 align:start position:0% the transaction data itself and this is 00:55:49.730 --> 00:55:52.450 align:start position:0% the transaction data itself and this is the<00:55:49.849> truth<00:55:50.230> and<00:55:51.230> now<00:55:51.380> let<00:55:51.619> let's<00:55:51.920> just<00:55:52.309> go 00:55:52.450 --> 00:55:52.460 align:start position:0% the truth and now let let's just go 00:55:52.460 --> 00:55:54.490 align:start position:0% the truth and now let let's just go through<00:55:52.520> this<00:55:53.299> process<00:55:53.569> in<00:55:53.809> detail<00:55:53.960> what<00:55:54.380> it 00:55:54.490 --> 00:55:54.500 align:start position:0% through this process in detail what it 00:55:54.500 --> 00:55:57.779 align:start position:0% through this process in detail what it is<00:55:54.970> the<00:55:55.970> first<00:55:56.240> thing<00:55:56.359> that<00:55:56.539> we<00:55:56.809> see<00:55:56.839> here<00:55:57.049> is 00:55:57.779 --> 00:55:57.789 align:start position:0% is the first thing that we see here is 00:55:57.789 --> 00:56:02.109 align:start position:0% is the first thing that we see here is this<00:55:58.789> proof<00:55:59.029> contains<00:55:59.980> the<00:56:00.980> Kolkata<00:56:01.250> this<00:56:01.970> is 00:56:02.109 --> 00:56:02.119 align:start position:0% this proof contains the Kolkata this is 00:56:02.119 --> 00:56:06.010 align:start position:0% this proof contains the Kolkata this is the<00:56:02.240> complete<00:56:03.400> we<00:56:04.400> have<00:56:04.520> here<00:56:04.730> and<00:56:05.599> if<00:56:05.809> you 00:56:06.010 --> 00:56:06.020 align:start position:0% the complete we have here and if you 00:56:06.020 --> 00:56:15.519 align:start position:0% the complete we have here and if you were<00:56:06.260> to<00:56:06.410> take<00:56:06.619> this<00:56:11.859> if<00:56:12.859> I<00:56:13.069> do<00:56:13.130> this<00:56:13.400> I<00:56:14.529> just 00:56:15.519 --> 00:56:15.529 align:start position:0% were to take this if I do this I just 00:56:15.529 --> 00:56:18.549 align:start position:0% were to take this if I do this I just did<00:56:15.980> alveta<00:56:16.460> code<00:56:16.880> this<00:56:17.299> bucket<00:56:17.750> up<00:56:17.900> and<00:56:18.470> you 00:56:18.549 --> 00:56:18.559 align:start position:0% did alveta code this bucket up and you 00:56:18.559 --> 00:56:21.940 align:start position:0% did alveta code this bucket up and you will<00:56:18.680> see<00:56:18.890> here<00:56:19.190> a<00:56:19.460> parent<00:56:20.420> ash<00:56:20.599> -<00:56:21.470> improve 00:56:21.940 --> 00:56:21.950 align:start position:0% will see here a parent ash - improve 00:56:21.950 --> 00:56:24.579 align:start position:0% will see here a parent ash - improve detection<00:56:22.190> with<00:56:22.670> all<00:56:22.940> these<00:56:23.059> data<00:56:23.299> and<00:56:23.690> pulse 00:56:24.579 --> 00:56:24.589 align:start position:0% detection with all these data and pulse 00:56:24.589 --> 00:56:27.250 align:start position:0% detection with all these data and pulse it<00:56:24.710> will<00:56:24.920> calculate<00:56:25.299> the<00:56:26.299> hash<00:56:26.480> of<00:56:26.960> the<00:56:27.109> deal 00:56:27.250 --> 00:56:27.260 align:start position:0% it will calculate the hash of the deal 00:56:27.260 --> 00:56:31.329 align:start position:0% it will calculate the hash of the deal itself<00:56:28.119> if<00:56:29.119> we<00:56:29.180> look<00:56:29.480> in<00:56:29.809> here<00:56:30.020> the<00:56:30.920> response 00:56:31.329 --> 00:56:31.339 align:start position:0% itself if we look in here the response 00:56:31.339 --> 00:56:34.750 align:start position:0% itself if we look in here the response head<00:56:31.730> of<00:56:31.970> this<00:56:32.180> project<00:56:32.720> if<00:56:32.990> we<00:56:33.549> compare<00:56:34.549> them 00:56:34.750 --> 00:56:34.760 align:start position:0% head of this project if we compare them 00:56:34.760 --> 00:56:36.849 align:start position:0% head of this project if we compare them it<00:56:35.299> matches<00:56:35.750> so<00:56:35.960> maybe<00:56:36.319> we<00:56:36.470> know<00:56:36.619> at<00:56:36.829> least 00:56:36.849 --> 00:56:36.859 align:start position:0% it matches so maybe we know at least 00:56:36.859 --> 00:56:38.980 align:start position:0% it matches so maybe we know at least this<00:56:37.670> is<00:56:38.029> the<00:56:38.210> bucket<00:56:38.420> up 00:56:38.980 --> 00:56:38.990 align:start position:0% this is the bucket up 00:56:38.990 --> 00:56:41.470 align:start position:0% this is the bucket up and<00:56:39.680> of<00:56:39.770> course<00:56:39.980> if<00:56:40.309> we<00:56:40.460> have<00:56:40.549> the<00:56:40.970> signature 00:56:41.470 --> 00:56:41.480 align:start position:0% and of course if we have the signature 00:56:41.480 --> 00:56:42.609 align:start position:0% and of course if we have the signature for<00:56:41.630> this<00:56:41.720> block<00:56:41.960> engine<00:56:42.260> we<00:56:42.349> can<00:56:42.500> also 00:56:42.609 --> 00:56:42.619 align:start position:0% for this block engine we can also 00:56:42.619 --> 00:56:45.819 align:start position:0% for this block engine we can also confirm<00:56:42.980> with<00:56:43.130> this<00:56:43.279> with<00:56:44.349> so<00:56:45.349> now<00:56:45.380> that<00:56:45.589> we 00:56:45.819 --> 00:56:45.829 align:start position:0% confirm with this with so now that we 00:56:45.829 --> 00:56:47.440 align:start position:0% confirm with this with so now that we know<00:56:45.859> that<00:56:46.010> the<00:56:46.369> project<00:56:46.609> was<00:56:46.910> correct 00:56:47.440 --> 00:56:47.450 align:start position:0% know that the project was correct 00:56:47.450 --> 00:56:50.799 align:start position:0% know that the project was correct we<00:56:48.289> can<00:56:48.470> now<00:56:48.680> come<00:56:49.250> and<00:56:49.520> look<00:56:49.760> at<00:56:50.029> the 00:56:50.799 --> 00:56:50.809 align:start position:0% we can now come and look at the 00:56:50.809 --> 00:56:53.680 align:start position:0% we can now come and look at the transaction<00:56:51.200> data<00:56:51.559> itself<00:56:52.089> this<00:56:53.089> is<00:56:53.270> the<00:56:53.390> Moga 00:56:53.680 --> 00:56:53.690 align:start position:0% transaction data itself this is the Moga 00:56:53.690 --> 00:56:56.589 align:start position:0% transaction data itself this is the Moga truth<00:56:53.960> for<00:56:54.529> the<00:56:54.619> transaction<00:56:55.390> the<00:56:56.390> first 00:56:56.589 --> 00:56:56.599 align:start position:0% truth for the transaction the first 00:56:56.599 --> 00:56:58.359 align:start position:0% truth for the transaction the first thing<00:56:56.779> we<00:56:56.930> need<00:56:57.079> to<00:56:57.109> know<00:56:57.349> is<00:56:57.589> if<00:56:57.950> you<00:56:58.160> want<00:56:58.309> to 00:56:58.359 --> 00:56:58.369 align:start position:0% thing we need to know is if you want to 00:56:58.369 --> 00:56:59.859 align:start position:0% thing we need to know is if you want to verify<00:56:58.490> the<00:56:58.819> truth 00:56:59.859 --> 00:56:59.869 align:start position:0% verify the truth 00:56:59.869 --> 00:57:02.650 align:start position:0% verify the truth transaction<00:57:00.289> index<00:57:00.819> we<00:57:01.819> noted<00:57:02.180> transaction 00:57:02.650 --> 00:57:02.660 align:start position:0% transaction index we noted transaction 00:57:02.660 --> 00:57:08.380 align:start position:0% transaction index we noted transaction X's<00:57:05.440> 171<00:57:06.440> or<00:57:06.769> it<00:57:07.099> is<00:57:07.369> also<00:57:07.670> the<00:57:07.849> same<00:57:08.029> now<00:57:08.180> we're 00:57:08.380 --> 00:57:08.390 align:start position:0% X's 171 or it is also the same now we're 00:57:08.390 --> 00:57:12.599 align:start position:0% X's 171 or it is also the same now we're here 00:57:12.599 --> 00:57:12.609 align:start position:0% 00:57:12.609 --> 00:57:16.259 align:start position:0% it's<00:57:12.999> actually<00:57:13.269> a<00:57:13.390> B<00:57:13.890> so<00:57:14.890> now<00:57:15.160> we<00:57:15.910> have<00:57:16.029> to 00:57:16.259 --> 00:57:16.269 align:start position:0% it's actually a B so now we have to 00:57:16.269 --> 00:57:19.349 align:start position:0% it's actually a B so now we have to actually<00:57:16.449> fix<00:57:16.869> what<00:57:17.140> we<00:57:17.289> can<00:57:17.469> do<00:57:17.650> with<00:57:17.799> this<00:57:18.359> go 00:57:19.349 --> 00:57:19.359 align:start position:0% actually fix what we can do with this go 00:57:19.359 --> 00:57:22.140 align:start position:0% actually fix what we can do with this go exactly<00:57:19.749> the<00:57:20.049> same<00:57:20.229> things<00:57:20.679> and<00:57:21.039> through<00:57:21.729> what 00:57:22.140 --> 00:57:22.150 align:start position:0% exactly the same things and through what 00:57:22.150 --> 00:57:25.489 align:start position:0% exactly the same things and through what I<00:57:22.179> explained<00:57:23.069> we<00:57:24.069> stopped<00:57:24.339> with<00:57:24.519> dead 00:57:25.489 --> 00:57:25.499 align:start position:0% I explained we stopped with dead 00:57:25.499 --> 00:57:32.039 align:start position:0% I explained we stopped with dead transsexual<00:57:26.499> which<00:57:26.859> is<00:57:27.009> this<00:57:27.130> one<00:57:27.339> and<00:57:30.029> go<00:57:31.029> now 00:57:32.039 --> 00:57:32.049 align:start position:0% transsexual which is this one and go now 00:57:32.049 --> 00:57:35.549 align:start position:0% transsexual which is this one and go now this<00:57:32.259> path<00:57:32.609> the<00:57:33.609> path<00:57:33.789> itself<00:57:34.239> I<00:57:34.569> mean<00:57:35.170> we<00:57:35.380> can 00:57:35.549 --> 00:57:35.559 align:start position:0% this path the path itself I mean we can 00:57:35.559 --> 00:57:46.300 align:start position:0% this path the path itself I mean we can simply<00:57:36.099> calculate<00:57:41.579> the<00:57:42.579> transaction<00:57:43.119> index 00:57:46.300 --> 00:57:46.310 align:start position:0% 00:57:46.310 --> 00:57:52.950 align:start position:0% [Music] 00:57:52.950 --> 00:57:52.960 align:start position:0% 00:57:52.960 --> 00:57:56.770 align:start position:0% so<00:57:53.960> this<00:57:54.410> is<00:57:54.680> what<00:57:54.920> you<00:57:55.040> see<00:57:55.250> here<00:57:55.579> this<00:57:56.420> is<00:57:56.630> the 00:57:56.770 --> 00:57:56.780 align:start position:0% so this is what you see here this is the 00:57:56.780 --> 00:58:01.930 align:start position:0% so this is what you see here this is the path<00:57:57.190> inside<00:57:58.190> the<00:57:58.579> military<00:57:59.349> now<00:58:00.349> and<00:58:00.940> now 00:58:01.930 --> 00:58:01.940 align:start position:0% path inside the military now and now 00:58:01.940 --> 00:58:06.220 align:start position:0% path inside the military now and now what<00:58:02.750> we<00:58:02.900> can<00:58:03.079> do<00:58:03.230> is<00:58:03.380> we<00:58:03.560> take<00:58:04.599> the<00:58:05.599> first<00:58:05.630> note 00:58:06.220 --> 00:58:06.230 align:start position:0% what we can do is we take the first note 00:58:06.230 --> 00:58:14.520 align:start position:0% what we can do is we take the first note of<00:58:06.500> them 00:58:14.520 --> 00:58:14.530 align:start position:0% 00:58:14.530 --> 00:58:19.390 align:start position:0% and<00:58:16.869> these<00:58:17.869> surveillance<00:58:18.410> in<00:58:19.070> what<00:58:19.280> the 00:58:19.390 --> 00:58:19.400 align:start position:0% and these surveillance in what the 00:58:19.400 --> 00:58:22.030 align:start position:0% and these surveillance in what the cesium<00:58:19.880> is<00:58:20.090> that's<00:58:20.840> how<00:58:21.080> we<00:58:21.140> didn't<00:58:21.680> know<00:58:21.830> the 00:58:22.030 --> 00:58:22.040 align:start position:0% cesium is that's how we didn't know the 00:58:22.040 --> 00:58:25.390 align:start position:0% cesium is that's how we didn't know the new<00:58:22.130> military<00:58:22.280> looks<00:58:22.670> like<00:58:23.530> this<00:58:24.530> is<00:58:24.650> a<00:58:24.680> French 00:58:25.390 --> 00:58:25.400 align:start position:0% new military looks like this is a French 00:58:25.400 --> 00:58:29.830 align:start position:0% new military looks like this is a French note<00:58:25.700> and<00:58:26.270> these<00:58:27.200> are<00:58:27.470> in<00:58:27.770> each<00:58:28.160> member<00:58:28.580> has<00:58:28.840> 16 00:58:29.830 --> 00:58:29.840 align:start position:0% note and these are in each member has 16 00:58:29.840 --> 00:58:34.510 align:start position:0% note and these are in each member has 16 spots<00:58:30.500> can<00:58:31.070> say<00:58:31.310> and<00:58:32.950> these<00:58:33.950> are<00:58:34.070> the<00:58:34.160> six<00:58:34.310> is 00:58:34.510 --> 00:58:34.520 align:start position:0% spots can say and these are the six is 00:58:34.520 --> 00:58:36.550 align:start position:0% spots can say and these are the six is not<00:58:34.700> in<00:58:34.940> this<00:58:35.030> especially<00:58:35.690> the<00:58:36.140> henna<00:58:36.440> the 00:58:36.550 --> 00:58:36.560 align:start position:0% not in this especially the henna the 00:58:36.560 --> 00:58:38.650 align:start position:0% not in this especially the henna the first<00:58:36.830> node<00:58:37.010> must<00:58:37.220> be<00:58:37.460> at<00:58:37.580> the<00:58:37.730> root<00:58:37.940> H<00:58:38.180> it's 00:58:38.650 --> 00:58:38.660 align:start position:0% first node must be at the root H it's 00:58:38.660 --> 00:58:42.880 align:start position:0% first node must be at the root H it's also<00:58:38.900> broken<00:58:39.260> up<00:58:39.619> to<00:58:40.490> the<00:58:40.609> v8<00:58:40.760> b5<00:58:41.890> suddenly 00:58:42.880 --> 00:58:42.890 align:start position:0% also broken up to the v8 b5 suddenly 00:58:42.890 --> 00:58:48.160 align:start position:0% also broken up to the v8 b5 suddenly very<00:58:43.040> small<00:58:43.369> screen<00:58:43.960> we<00:58:45.400> with<00:58:46.400> here<00:58:47.000> at<00:58:47.270> age<00:58:47.450> 45 00:58:48.160 --> 00:58:48.170 align:start position:0% very small screen we with here at age 45 00:58:48.170 --> 00:58:51.490 align:start position:0% very small screen we with here at age 45 this<00:58:48.680> is<00:58:48.740> the<00:58:48.920> one<00:58:49.070> Ventress<00:58:50.140> so<00:58:51.140> that's<00:58:51.350> why 00:58:51.490 --> 00:58:51.500 align:start position:0% this is the one Ventress so that's why 00:58:51.500 --> 00:58:55.420 align:start position:0% this is the one Ventress so that's why we<00:58:51.650> know<00:58:51.940> okay<00:58:52.940> that's<00:58:53.150> one<00:58:53.540> now<00:58:54.350> we<00:58:54.410> looked<00:58:55.220> at 00:58:55.420 --> 00:58:55.430 align:start position:0% we know okay that's one now we looked at 00:58:55.430 --> 00:59:02.200 align:start position:0% we know okay that's one now we looked at our<00:58:55.700> path<00:58:56.600> eight<00:58:58.150> 118<00:58:59.560> so<00:59:00.560> the<00:59:00.680> first<00:59:01.210> part 00:59:02.200 --> 00:59:02.210 align:start position:0% our path eight 118 so the first part 00:59:02.210 --> 00:59:05.980 align:start position:0% our path eight 118 so the first part will<00:59:02.450> be<00:59:02.600> here<00:59:02.840> 8<00:59:03.940> which<00:59:04.940> is<00:59:04.970> this<00:59:05.510> distant 00:59:05.980 --> 00:59:05.990 align:start position:0% will be here 8 which is this distant 00:59:05.990 --> 00:59:09.880 align:start position:0% will be here 8 which is this distant attention<00:59:06.859> of<00:59:06.980> the<00:59:07.070> next<00:59:07.310> node<00:59:07.490> and<00:59:08.590> then<00:59:09.590> if 00:59:09.880 --> 00:59:09.890 align:start position:0% attention of the next node and then if 00:59:09.890 --> 00:59:14.020 align:start position:0% attention of the next node and then if we<00:59:10.040> go<00:59:10.190> in<00:59:11.920> we<00:59:12.920> can<00:59:13.100> now<00:59:13.430> take<00:59:13.490> the<00:59:13.730> next 00:59:14.020 --> 00:59:14.030 align:start position:0% we go in we can now take the next 00:59:14.030 --> 00:59:24.099 align:start position:0% we go in we can now take the next thought 00:59:24.099 --> 00:59:24.109 align:start position:0% 00:59:24.109 --> 00:59:26.530 align:start position:0% this<00:59:24.559> is<00:59:24.679> next<00:59:24.979> month 00:59:26.530 --> 00:59:26.540 align:start position:0% this is next month 00:59:26.540 --> 00:59:29.640 align:start position:0% this is next month this<00:59:27.080> is<00:59:27.230> fish 00:59:29.640 --> 00:59:29.650 align:start position:0% 00:59:29.650 --> 00:59:33.720 align:start position:0% and<00:59:29.859> eight<00:59:30.190> is<00:59:30.520> yellow<00:59:31.539> matches<00:59:32.279> so<00:59:33.279> this 00:59:33.720 --> 00:59:33.730 align:start position:0% and eight is yellow matches so this 00:59:33.730 --> 00:59:36.660 align:start position:0% and eight is yellow matches so this would<00:59:33.940> I<00:59:34.180> can<00:59:34.900> do<00:59:35.049> this<00:59:35.319> now<00:59:35.529> all<00:59:35.770> the<00:59:35.890> way<00:59:36.039> it 00:59:36.660 --> 00:59:36.670 align:start position:0% would I can do this now all the way it 00:59:36.670 --> 00:59:47.160 align:start position:0% would I can do this now all the way it will<00:59:36.819> look<00:59:36.970> bad<00:59:37.180> at<00:59:37.359> the<00:59:37.450> last<00:59:37.690> note 00:59:47.160 --> 00:59:47.170 align:start position:0% 00:59:47.170 --> 00:59:49.170 align:start position:0% the<00:59:47.650> last<00:59:47.860> one<00:59:48.100> is<00:59:48.280> at<00:59:48.400> least<00:59:48.640> a<00:59:48.880> leaf<00:59:49.150> node 00:59:49.170 --> 00:59:49.180 align:start position:0% the last one is at least a leaf node 00:59:49.180 --> 00:59:51.650 align:start position:0% the last one is at least a leaf node meaning<00:59:50.050> this<00:59:50.380> this<00:59:50.830> is<00:59:50.950> the<00:59:51.040> actual<00:59:51.310> value 00:59:51.650 --> 00:59:51.660 align:start position:0% meaning this this is the actual value 00:59:51.660 --> 00:59:54.500 align:start position:0% meaning this this is the actual value what<00:59:52.660> governments<00:59:53.080> were<00:59:53.170> just<00:59:53.410> a<00:59:53.500> bastard<00:59:53.980> and 00:59:54.500 --> 00:59:54.510 align:start position:0% what governments were just a bastard and 00:59:54.510 --> 00:59:57.810 align:start position:0% what governments were just a bastard and this<00:59:55.510> week<00:59:55.750> note<00:59:55.960> had<00:59:56.230> developed<00:59:57.100> is<00:59:57.220> known<00:59:57.580> is 00:59:57.810 --> 00:59:57.820 align:start position:0% this week note had developed is known is 00:59:57.820 --> 01:00:03.599 align:start position:0% this week note had developed is known is here 01:00:03.599 --> 01:00:03.609 align:start position:0% 01:00:03.609 --> 01:00:07.319 align:start position:0% this<01:00:04.180> this<01:00:04.779> is<01:00:04.930> a<01:00:04.959> bra<01:00:05.380> transaction<01:00:06.029> so<01:00:07.029> I<01:00:07.119> can 01:00:07.319 --> 01:00:07.329 align:start position:0% this this is a bra transaction so I can 01:00:07.329 --> 01:00:09.299 align:start position:0% this this is a bra transaction so I can take<01:00:07.630> now<01:00:07.839> these<01:00:08.410> data<01:00:08.709> from<01:00:09.009> the<01:00:09.069> spot 01:00:09.299 --> 01:00:09.309 align:start position:0% take now these data from the spot 01:00:09.309 --> 01:00:14.819 align:start position:0% take now these data from the spot transactions<01:00:09.910> and<01:00:11.609> in<01:00:12.630> compared<01:00:13.630> to<01:00:14.410> the<01:00:14.469> one 01:00:14.819 --> 01:00:14.829 align:start position:0% transactions and in compared to the one 01:00:14.829 --> 01:00:18.509 align:start position:0% transactions and in compared to the one we<01:00:15.099> have<01:00:15.249> here<01:00:15.329> to<01:00:16.329> solve<01:00:17.099> so<01:00:18.099> we<01:00:18.249> have<01:00:18.339> to 01:00:18.509 --> 01:00:18.519 align:start position:0% we have here to solve so we have to 01:00:18.519 --> 01:00:22.430 align:start position:0% we have here to solve so we have to guess<01:00:18.809> for<01:00:19.809> example<01:00:20.759> which<01:00:21.759> is<01:00:21.910> this<01:00:22.089> value 01:00:22.430 --> 01:00:22.440 align:start position:0% guess for example which is this value 01:00:22.440 --> 01:00:28.199 align:start position:0% guess for example which is this value matches<01:00:23.789> we<01:00:24.789> have<01:00:24.910> to<01:00:25.059> address<01:00:26.759> which<01:00:27.759> is<01:00:27.789> this 01:00:28.199 --> 01:00:28.209 align:start position:0% matches we have to address which is this 01:00:28.209 --> 01:00:31.170 align:start position:0% matches we have to address which is this one<01:00:28.450> matches<01:00:29.380> and<01:00:29.920> that<01:00:30.069> exactly<01:00:30.519> in<01:00:30.819> to<01:00:30.969> tie 01:00:31.170 --> 01:00:31.180 align:start position:0% one matches and that exactly in to tie 01:00:31.180 --> 01:00:34.410 align:start position:0% one matches and that exactly in to tie this<01:00:31.239> to<01:00:31.509> it<01:00:32.430> very<01:00:33.430> fast<01:00:33.759> to<01:00:33.910> know<01:00:34.059> the<01:00:34.180> truth 01:00:34.410 --> 01:00:34.420 align:start position:0% this to it very fast to know the truth 01:00:34.420 --> 01:00:37.339 align:start position:0% this to it very fast to know the truth just<01:00:35.289> as<01:00:35.469> we've<01:00:35.680> been<01:00:35.890> mainly<01:00:36.190> here<01:00:36.640> now<01:00:36.819> and 01:00:37.339 --> 01:00:37.349 align:start position:0% just as we've been mainly here now and 01:00:37.349 --> 01:00:41.729 align:start position:0% just as we've been mainly here now and then<01:00:38.349> compare<01:00:39.059> each<01:00:40.059> data<01:00:40.450> so<01:00:41.049> response<01:00:41.440> make 01:00:41.729 --> 01:00:41.739 align:start position:0% then compare each data so response make 01:00:41.739 --> 01:00:45.630 align:start position:0% then compare each data so response make sure<01:00:41.859> it's<01:00:42.039> product<01:00:44.219> and<01:00:45.219> they<01:00:45.339> should<01:00:45.519> we 01:00:45.630 --> 01:00:45.640 align:start position:0% sure it's product and they should we 01:00:45.640 --> 01:00:47.999 align:start position:0% sure it's product and they should we have<01:00:45.759> a<01:00:45.910> lot<01:00:46.089> of<01:00:46.119> chase<01:00:46.690> and<01:00:46.930> test<01:00:47.109> that<01:00:47.589> if<01:00:47.769> I 01:00:47.999 --> 01:00:48.009 align:start position:0% have a lot of chase and test that if I 01:00:48.009 --> 01:00:50.519 align:start position:0% have a lot of chase and test that if I promise<01:00:48.430> try<01:00:48.670> to<01:00:48.729> fuss<01:00:49.630> around<01:00:49.779> manipulate 01:00:50.519 --> 01:00:50.529 align:start position:0% promise try to fuss around manipulate 01:00:50.529 --> 01:00:52.829 align:start position:0% promise try to fuss around manipulate and<01:00:50.739> make<01:00:50.920> sure<01:00:51.160> that<01:00:51.459> it<01:00:51.849> will<01:00:51.999> detect<01:00:52.359> each 01:00:52.829 --> 01:00:52.839 align:start position:0% and make sure that it will detect each 01:00:52.839 --> 01:00:57.120 align:start position:0% and make sure that it will detect each change<01:00:54.839> okay<01:00:55.839> because<01:00:56.289> of<01:00:56.469> the<01:00:56.619> are<01:00:56.799> any 01:00:57.120 --> 01:00:57.130 align:start position:0% change okay because of the are any 01:00:57.130 --> 01:01:00.269 align:start position:0% change okay because of the are any questions<01:00:57.609> for<01:00:57.789> that<01:00:57.839> how<01:00:58.839> how<01:00:59.739> this<01:00:59.979> works 01:01:00.269 --> 01:01:00.279 align:start position:0% questions for that how how this works 01:01:00.279 --> 01:01:02.789 align:start position:0% questions for that how how this works all<01:01:00.789> this<01:01:01.029> I<01:01:01.239> mean<01:01:01.299> we<01:01:01.959> did<01:01:02.140> not<01:01:02.289> invent<01:01:02.650> this 01:01:02.789 --> 01:01:02.799 align:start position:0% all this I mean we did not invent this 01:01:02.799 --> 01:01:04.589 align:start position:0% all this I mean we did not invent this move<01:01:03.249> this<01:01:03.400> is<01:01:03.519> publish<01:01:03.849> the<01:01:03.969> same<01:01:04.150> protocol 01:01:04.589 --> 01:01:04.599 align:start position:0% move this is publish the same protocol 01:01:04.599 --> 01:01:07.469 align:start position:0% move this is publish the same protocol but<01:01:05.049> we<01:01:05.259> are<01:01:05.380> using<01:01:05.650> exactly<01:01:06.249> this<01:01:06.549> to<01:01:07.269> marry 01:01:07.469 --> 01:01:07.479 align:start position:0% but we are using exactly this to marry 01:01:07.479 --> 01:01:14.460 align:start position:0% but we are using exactly this to marry five 01:01:14.460 --> 01:01:14.470 align:start position:0% 01:01:14.470 --> 01:01:19.410 align:start position:0% it's<01:01:15.470> our<01:01:17.680> choice<01:01:18.680> of<01:01:18.920> those<01:01:19.040> accomplishments 01:01:19.410 --> 01:01:19.420 align:start position:0% it's our choice of those accomplishments 01:01:19.420 --> 01:01:22.240 align:start position:0% it's our choice of those accomplishments those<01:01:20.420> nation<01:01:20.750> LP<01:01:21.170> because<01:01:21.950> we<01:01:22.069> had<01:01:22.190> to 01:01:22.240 --> 01:01:22.250 align:start position:0% those nation LP because we had to 01:01:22.250 --> 01:01:23.859 align:start position:0% those nation LP because we had to implement<01:01:22.400> some<01:01:22.849> being<01:01:23.119> cooking<01:01:23.480> for<01:01:23.720> the 01:01:23.859 --> 01:01:23.869 align:start position:0% implement some being cooking for the 01:01:23.869 --> 01:01:25.750 align:start position:0% implement some being cooking for the season<01:01:24.230> anyways<01:01:24.650> into<01:01:24.950> it<01:01:25.010> that<01:01:25.130> was<01:01:25.309> its<01:01:25.460> mark 01:01:25.750 --> 01:01:25.760 align:start position:0% season anyways into it that was its mark 01:01:25.760 --> 01:01:29.819 align:start position:0% season anyways into it that was its mark events<01:01:26.150> and<01:01:26.300> due<01:01:26.450> to<01:01:26.480> that<01:01:27.849> that<01:01:28.849> just 01:01:29.819 --> 01:01:29.829 align:start position:0% events and due to that that just 01:01:29.829 --> 01:01:31.900 align:start position:0% events and due to that that just released<01:01:30.829> a<01:01:31.010> part<01:01:31.250> of<01:01:31.339> yours 01:01:31.900 --> 01:01:31.910 align:start position:0% released a part of yours 01:01:31.910 --> 01:01:33.819 align:start position:0% released a part of yours it's<01:01:32.059> part<01:01:32.540> of<01:01:32.630> you<01:01:32.809> about<01:01:33.170> I<01:01:33.230> didn't<01:01:33.650> see 01:01:33.819 --> 01:01:33.829 align:start position:0% it's part of you about I didn't see 01:01:33.829 --> 01:01:36.370 align:start position:0% it's part of you about I didn't see client<01:01:34.369> down<01:01:34.520> but<01:01:35.359> it<01:01:35.480> was<01:01:35.599> quite<01:01:35.809> helpful 01:01:36.370 --> 01:01:36.380 align:start position:0% client down but it was quite helpful 01:01:36.380 --> 01:01:39.280 align:start position:0% client down but it was quite helpful I<01:01:36.410> mean<01:01:36.589> I<01:01:36.710> know<01:01:36.770> guess<01:01:37.040> also<01:01:37.339> has<01:01:37.579> an<01:01:38.290> alky 01:01:39.280 --> 01:01:39.290 align:start position:0% I mean I know guess also has an alky 01:01:39.290 --> 01:01:41.319 align:start position:0% I mean I know guess also has an alky code<01:01:39.770> I<01:01:39.980> think<01:01:40.010> goes<01:01:40.339> up<01:01:40.490> like<01:01:40.640> this<01:01:40.700> the<01:01:41.240> only 01:01:41.319 --> 01:01:41.329 align:start position:0% code I think goes up like this the only 01:01:41.329 --> 01:01:43.299 align:start position:0% code I think goes up like this the only thing<01:01:41.599> he<01:01:41.780> entered<01:01:42.140> will<01:01:42.290> be<01:01:42.319> easier<01:01:42.800> I<01:01:43.040> put<01:01:43.280> a 01:01:43.299 --> 01:01:43.309 align:start position:0% thing he entered will be easier I put a 01:01:43.309 --> 01:01:45.430 align:start position:0% thing he entered will be easier I put a lot<01:01:43.520> of<01:01:43.640> tea<01:01:43.819> pockets<01:01:44.150> after<01:01:44.510> that<01:01:44.720> because 01:01:45.430 --> 01:01:45.440 align:start position:0% lot of tea pockets after that because 01:01:45.440 --> 01:01:48.250 align:start position:0% lot of tea pockets after that because you<01:01:45.680> it<01:01:46.160> kind<01:01:46.430> of<01:01:46.490> guests<01:01:46.849> what<01:01:47.030> it<01:01:47.150> is<01:01:47.300> looking 01:01:48.250 --> 01:01:48.260 align:start position:0% you it kind of guests what it is looking 01:01:48.260 --> 01:01:50.349 align:start position:0% you it kind of guests what it is looking at<01:01:48.440> now<01:01:48.680> appears<01:01:49.190> looks<01:01:49.819> like<01:01:49.970> a<01:01:50.000> blockhead 01:01:50.349 --> 01:01:50.359 align:start position:0% at now appears looks like a blockhead 01:01:50.359 --> 01:01:52.030 align:start position:0% at now appears looks like a blockhead out<01:01:50.540> of<01:01:50.630> this<01:01:50.809> look<01:01:50.960> like<01:01:51.079> a<01:01:51.140> transaction<01:01:51.710> and 01:01:52.030 --> 01:01:52.040 align:start position:0% out of this look like a transaction and 01:01:52.040 --> 01:01:54.460 align:start position:0% out of this look like a transaction and so<01:01:52.400> it<01:01:52.490> used<01:01:52.670> to<01:01:52.700> be<01:01:52.760> names<01:01:53.059> of<01:01:53.359> it<01:01:53.569> makes<01:01:54.319> it 01:01:54.460 --> 01:01:54.470 align:start position:0% so it used to be names of it makes it 01:01:54.470 --> 01:01:57.400 align:start position:0% so it used to be names of it makes it easier<01:01:54.740> to<01:01:54.800> read<01:01:55.569> but<01:01:56.569> this<01:01:56.720> is<01:01:56.839> more<01:01:56.990> like<01:01:57.050> in 01:01:57.400 --> 01:01:57.410 align:start position:0% easier to read but this is more like in 01:01:57.410 --> 01:02:00.579 align:start position:0% easier to read but this is more like in total<01:01:57.710> 12<01:01:57.950> to<01:01:58.790> play<01:01:59.540> around<01:01:59.750> it<01:02:00.050> but<01:02:00.140> really 01:02:00.579 --> 01:02:00.589 align:start position:0% total 12 to play around it but really 01:02:00.589 --> 01:02:02.470 align:start position:0% total 12 to play around it but really helps<01:02:00.829> understand<01:02:01.430> a<01:02:01.520> bit<01:02:01.700> what's<01:02:02.059> going<01:02:02.359> on 01:02:02.470 --> 01:02:02.480 align:start position:0% helps understand a bit what's going on 01:02:02.480 --> 01:02:12.190 align:start position:0% helps understand a bit what's going on inside<01:02:07.180> okay<01:02:09.250> if<01:02:10.250> you<01:02:10.490> want<01:02:10.790> you<01:02:11.540> can<01:02:11.630> try<01:02:11.930> I 01:02:12.190 --> 01:02:12.200 align:start position:0% inside okay if you want you can try I 01:02:12.200 --> 01:02:15.050 align:start position:0% inside okay if you want you can try I mean<01:02:12.230> in<01:02:13.069> the<01:02:13.220> target 01:02:15.050 --> 01:02:15.060 align:start position:0% mean in the target 01:02:15.060 --> 01:02:17.700 align:start position:0% mean in the target [Music] 01:02:17.700 --> 01:02:17.710 align:start position:0% [Music] 01:02:17.710 --> 01:02:21.940 align:start position:0% [Music] okay<01:02:20.590> maybe 01:02:21.940 --> 01:02:21.950 align:start position:0% okay maybe 01:02:21.950 --> 01:02:24.250 align:start position:0% okay maybe what<01:02:22.190> about<01:02:22.250> whatever<01:02:22.610> back<01:02:23.390> to<01:02:23.540> do<01:02:23.660> next<01:02:23.869> is 01:02:24.250 --> 01:02:24.260 align:start position:0% what about whatever back to do next is 01:02:24.260 --> 01:02:27.700 align:start position:0% what about whatever back to do next is just<01:02:25.070> to<01:02:25.550> show<01:02:25.730> you<01:02:25.790> that<01:02:26.660> execution<01:02:27.140> action 01:02:27.700 --> 01:02:27.710 align:start position:0% just to show you that execution action 01:02:27.710 --> 01:02:29.560 align:start position:0% just to show you that execution action would<01:02:28.040> after<01:02:28.400> if<01:02:28.550> you<01:02:28.850> can<01:02:29.060> do<01:02:29.270> it<01:02:29.390> for 01:02:29.560 --> 01:02:29.570 align:start position:0% would after if you can do it for 01:02:29.570 --> 01:02:33.070 align:start position:0% would after if you can do it for yourself<01:02:29.780> if<01:02:30.200> you<01:02:31.240> first<01:02:32.240> attach<01:02:32.540> the<01:02:32.570> client 01:02:33.070 --> 01:02:33.080 align:start position:0% yourself if you first attach the client 01:02:33.080 --> 01:02:34.900 align:start position:0% yourself if you first attach the client and<01:02:33.290> then<01:02:33.410> maybe<01:02:33.560> you<01:02:33.710> can<01:02:33.860> also<01:02:34.130> use<01:02:34.460> the<01:02:34.640> seat 01:02:34.900 --> 01:02:34.910 align:start position:0% and then maybe you can also use the seat 01:02:34.910 --> 01:02:36.960 align:start position:0% and then maybe you can also use the seat line<01:02:35.119> how<01:02:35.750> to<01:02:35.810> use<01:02:36.140> it<01:02:36.320> how<01:02:36.470> to<01:02:36.500> install 01:02:36.960 --> 01:02:36.970 align:start position:0% line how to use it how to install 01:02:36.970 --> 01:02:41.080 align:start position:0% line how to use it how to install attending<01:02:37.970> theme<01:02:38.440> it's<01:02:39.440> not<01:02:40.070> very<01:02:40.670> hard 01:02:41.080 --> 01:02:41.090 align:start position:0% attending theme it's not very hard 01:02:41.090 --> 01:02:43.090 align:start position:0% attending theme it's not very hard because<01:02:41.869> of<01:02:42.080> all<01:02:42.200> these<01:02:42.380> things<01:02:42.440> that<01:02:42.890> we<01:02:43.070> have 01:02:43.090 --> 01:02:43.100 align:start position:0% because of all these things that we have 01:02:43.100 --> 01:02:45.700 align:start position:0% because of all these things that we have seen<01:02:43.610> here<01:02:43.880> are<01:02:44.360> going<01:02:44.750> on<01:02:44.930> directly<01:02:45.350> inside 01:02:45.700 --> 01:02:45.710 align:start position:0% seen here are going on directly inside 01:02:45.710 --> 01:02:48.400 align:start position:0% seen here are going on directly inside the<01:02:45.770> client<01:02:46.660> from<01:02:47.660> a<01:02:47.810> developer's 01:02:48.400 --> 01:02:48.410 align:start position:0% the client from a developer's 01:02:48.410 --> 01:02:50.650 align:start position:0% the client from a developer's perspective<01:02:48.440> you<01:02:49.040> trustfully<01:02:49.730> use<01:02:49.970> it<01:02:50.180> you 01:02:50.650 --> 01:02:50.660 align:start position:0% perspective you trustfully use it you 01:02:50.660 --> 01:02:52.630 align:start position:0% perspective you trustfully use it you don't<01:02:50.690> even<01:02:50.990> have<01:02:51.140> to<01:02:51.290> care<01:02:51.530> about<01:02:51.560> them<01:02:51.980> the 01:02:52.630 --> 01:02:52.640 align:start position:0% don't even have to care about them the 01:02:52.640 --> 01:02:54.220 align:start position:0% don't even have to care about them the verification<01:02:53.330> is<01:02:53.480> just<01:02:53.720> taking<01:02:54.020> place 01:02:54.220 --> 01:02:54.230 align:start position:0% verification is just taking place 01:02:54.230 --> 01:02:57.340 align:start position:0% verification is just taking place meaning<01:02:55.160> you<01:02:55.460> just<01:02:55.700> use<01:02:56.030> it<01:02:56.060> and<01:02:56.720> when<01:02:57.050> you<01:02:57.170> do 01:02:57.340 --> 01:02:57.350 align:start position:0% meaning you just use it and when you do 01:02:57.350 --> 01:03:00.160 align:start position:0% meaning you just use it and when you do this<01:02:58.930> this 01:03:00.160 --> 01:03:00.170 align:start position:0% this this 01:03:00.170 --> 01:03:02.310 align:start position:0% this this [Music] 01:03:02.310 --> 01:03:02.320 align:start position:0% [Music] 01:03:02.320 --> 01:03:05.620 align:start position:0% [Music] then<01:03:03.320> screen<01:03:03.650> of<01:03:03.830> every<01:03:04.130> single<01:03:04.370> and<01:03:05.000> chance 01:03:05.620 --> 01:03:05.630 align:start position:0% then screen of every single and chance 01:03:05.630 --> 01:03:09.010 align:start position:0% then screen of every single and chance cook<01:03:05.930> I<01:03:06.340> do<01:03:07.340> in<01:03:07.610> terms<01:03:07.790> community<01:03:08.330> so<01:03:08.540> it's 01:03:09.010 --> 01:03:09.020 align:start position:0% cook I do in terms community so it's 01:03:09.020 --> 01:03:10.990 align:start position:0% cook I do in terms community so it's even<01:03:09.530> easier<01:03:09.860> than<01:03:09.920> taps<01:03:10.250> good<01:03:10.490> to<01:03:10.640> go<01:03:10.730> sittin 01:03:10.990 --> 01:03:11.000 align:start position:0% even easier than taps good to go sittin 01:03:11.000 --> 01:03:13.060 align:start position:0% even easier than taps good to go sittin after<01:03:11.300> except<01:03:11.870> a<01:03:11.990> pastor<01:03:12.350> but<01:03:12.530> the 01:03:13.060 --> 01:03:13.070 align:start position:0% after except a pastor but the 01:03:13.070 --> 01:03:15.990 align:start position:0% after except a pastor but the implementation<01:03:13.370> is<01:03:13.880> completely<01:03:14.360> done 01:03:15.990 --> 01:03:16.000 align:start position:0% implementation is completely done 01:03:16.000 --> 01:03:21.310 align:start position:0% implementation is completely done typescript<01:03:17.000> zone<01:03:18.010> in<01:03:19.010> the<01:03:19.750> image<01:03:20.750> itself<01:03:21.050> I 01:03:21.310 --> 01:03:21.320 align:start position:0% typescript zone in the image itself I 01:03:21.320 --> 01:03:23.320 align:start position:0% typescript zone in the image itself I hope<01:03:21.650> we've<01:03:22.010> also<01:03:22.340> done<01:03:22.730> it<01:03:22.910> all<01:03:23.030> the<01:03:23.180> node 01:03:23.320 --> 01:03:23.330 align:start position:0% hope we've also done it all the node 01:03:23.330 --> 01:03:25.420 align:start position:0% hope we've also done it all the node modules<01:03:23.540> is<01:03:24.050> all<01:03:24.230> install<01:03:24.710> to<01:03:24.860> don't<01:03:25.100> have<01:03:25.310> to 01:03:25.420 --> 01:03:25.430 align:start position:0% modules is all install to don't have to 01:03:25.430 --> 01:03:27.700 align:start position:0% modules is all install to don't have to call<01:03:25.610> Indian<01:03:25.970> install<01:03:26.390> but<01:03:27.080> if<01:03:27.290> you<01:03:27.530> will 01:03:27.700 --> 01:03:27.710 align:start position:0% call Indian install but if you will 01:03:27.710 --> 01:03:30.970 align:start position:0% call Indian install but if you will start<01:03:28.040> what<01:03:28.820> you<01:03:28.940> usually<01:03:29.150> return<01:03:29.770> we'd<01:03:30.770> call 01:03:30.970 --> 01:03:30.980 align:start position:0% start what you usually return we'd call 01:03:30.980 --> 01:03:36.630 align:start position:0% start what you usually return we'd call NPM<01:03:31.400> install<01:03:33.610> nine<01:03:34.610> three<01:03:34.970> more<01:03:35.290> positive 01:03:36.630 --> 01:03:36.640 align:start position:0% NPM install nine three more positive 01:03:36.640 --> 01:03:40.330 align:start position:0% NPM install nine three more positive you'll<01:03:37.640> save<01:03:37.910> it<01:03:38.090> like<01:03:38.870> this<01:03:39.110> I<01:03:39.350> guess<01:03:40.100> that's 01:03:40.330 --> 01:03:40.340 align:start position:0% you'll save it like this I guess that's 01:03:40.340 --> 01:03:42.700 align:start position:0% you'll save it like this I guess that's where<01:03:40.490> everybody<01:03:40.880> goes<01:03:40.940> home<01:03:41.200> but<01:03:42.200> in<01:03:42.470> the 01:03:42.700 --> 01:03:42.710 align:start position:0% where everybody goes home but in the 01:03:42.710 --> 01:03:48.070 align:start position:0% where everybody goes home but in the solid<01:03:43.160> include<01:03:43.550> by<01:03:44.800> modules<01:03:46.720> it's<01:03:47.720> already 01:03:48.070 --> 01:03:48.080 align:start position:0% solid include by modules it's already 01:03:48.080 --> 01:03:49.780 align:start position:0% solid include by modules it's already done<01:03:48.260> here<01:03:48.530> that's<01:03:48.770> why<01:03:49.010> I<01:03:49.070> don't<01:03:49.280> have<01:03:49.460> to<01:03:49.670> do 01:03:49.780 --> 01:03:49.790 align:start position:0% done here that's why I don't have to do 01:03:49.790 --> 01:03:55.980 align:start position:0% done here that's why I don't have to do it<01:03:49.870> that's<01:03:50.870> why<01:03:51.020> you<01:03:51.760> see<01:03:52.760> that's<01:03:54.340> right 01:03:55.980 --> 01:03:55.990 align:start position:0% it that's why you see that's right 01:03:55.990 --> 01:04:00.190 align:start position:0% it that's why you see that's right simple<01:03:56.990> theme<01:03:57.170> on<01:03:58.510> the<01:03:59.510> first<01:03:59.720> thing<01:03:59.930> you<01:04:00.080> have 01:04:00.190 --> 01:04:00.200 align:start position:0% simple theme on the first thing you have 01:04:00.200 --> 01:04:11.430 align:start position:0% simple theme on the first thing you have you<01:04:00.560> do<01:04:00.740> is<01:04:01.010> you<01:04:01.760> just<01:04:03.760> require 01:04:11.430 --> 01:04:11.440 align:start position:0% 01:04:11.440 --> 01:04:13.680 align:start position:0% this 01:04:13.680 --> 01:04:13.690 align:start position:0% this 01:04:13.690 --> 01:04:16.750 align:start position:0% this [Music] 01:04:16.750 --> 01:04:16.760 align:start position:0% 01:04:16.760 --> 01:04:20.590 align:start position:0% because<01:04:17.859> we<01:04:18.859> just<01:04:19.010> did<01:04:19.250> default<01:04:19.730> meaning<01:04:20.270> this 01:04:20.590 --> 01:04:20.600 align:start position:0% because we just did default meaning this 01:04:20.600 --> 01:04:25.210 align:start position:0% because we just did default meaning this is<01:04:20.720> the<01:04:20.869> class<01:04:21.109> that<01:04:21.140> into<01:04:21.920> class<01:04:22.250> and<01:04:24.070> now<01:04:25.070> we 01:04:25.210 --> 01:04:25.220 align:start position:0% is the class that into class and now we 01:04:25.220 --> 01:04:33.250 align:start position:0% is the class that into class and now we can<01:04:26.260> create<01:04:27.260> a<01:04:27.440> client<01:04:27.710> so<01:04:31.540> this<01:04:32.540> is<01:04:32.660> pretty 01:04:33.250 --> 01:04:33.260 align:start position:0% can create a client so this is pretty 01:04:33.260 --> 01:04:36.430 align:start position:0% can create a client so this is pretty easy<01:04:33.500> and<01:04:33.680> straightforward<01:04:34.990> if<01:04:35.990> you<01:04:36.200> do<01:04:36.350> it 01:04:36.430 --> 01:04:36.440 align:start position:0% easy and straightforward if you do it 01:04:36.440 --> 01:04:38.770 align:start position:0% easy and straightforward if you do it like<01:04:36.560> this<01:04:36.770> it<01:04:37.040> will<01:04:37.250> create<01:04:37.910> a<01:04:38.000> client<01:04:38.540> with 01:04:38.770 --> 01:04:38.780 align:start position:0% like this it will create a client with 01:04:38.780 --> 01:04:41.710 align:start position:0% like this it will create a client with the<01:04:38.900> defaults<01:04:39.700> but<01:04:40.700> if<01:04:40.940> you<01:04:41.030> want<01:04:41.270> to<01:04:41.390> can<01:04:41.600> of 01:04:41.710 --> 01:04:41.720 align:start position:0% the defaults but if you want to can of 01:04:41.720 --> 01:04:47.080 align:start position:0% the defaults but if you want to can of course<01:04:42.050> pass<01:04:45.580> there's<01:04:46.580> a<01:04:46.670> lot<01:04:46.910> of 01:04:47.080 --> 01:04:47.090 align:start position:0% course pass there's a lot of 01:04:47.090 --> 01:04:49.210 align:start position:0% course pass there's a lot of configuration<01:04:47.390> meaning<01:04:48.350> even<01:04:48.650> you<01:04:49.040> can 01:04:49.210 --> 01:04:49.220 align:start position:0% configuration meaning even you can 01:04:49.220 --> 01:04:51.340 align:start position:0% configuration meaning even you can define<01:04:49.580> your<01:04:50.000> notes<01:04:50.480> that<01:04:50.720> you<01:04:50.930> want<01:04:51.109> to<01:04:51.200> use 01:04:51.340 --> 01:04:51.350 align:start position:0% define your notes that you want to use 01:04:51.350 --> 01:04:54.370 align:start position:0% define your notes that you want to use became<01:04:52.250> a<01:04:52.310> time<01:04:52.790> like<01:04:53.330> there<01:04:53.570> because<01:04:54.109> count 01:04:54.370 --> 01:04:54.380 align:start position:0% became a time like there because count 01:04:54.380 --> 01:04:56.440 align:start position:0% became a time like there because count how<01:04:54.560> many<01:04:54.619> mystery<01:04:55.160> of<01:04:55.220> all<01:04:55.310> descent<01:04:55.670> on<01:04:56.300> the 01:04:56.440 --> 01:04:56.450 align:start position:0% how many mystery of all descent on the 01:04:56.450 --> 01:04:59.560 align:start position:0% how many mystery of all descent on the signatures<01:04:56.960> you<01:04:57.109> want<01:04:57.290> to<01:04:57.380> have<01:04:58.570> one 01:04:59.560 --> 01:04:59.570 align:start position:0% signatures you want to have one 01:04:59.570 --> 01:05:01.390 align:start position:0% signatures you want to have one important<01:05:00.109> parameters<01:05:00.560> explain<01:05:00.920> the<01:05:01.130> chain 01:05:01.390 --> 01:05:01.400 align:start position:0% important parameters explain the chain 01:05:01.400 --> 01:05:04.270 align:start position:0% important parameters explain the chain ID<01:05:01.720> which<01:05:02.720> scene<01:05:02.960> you<01:05:03.080> want<01:05:03.260> to<01:05:03.350> use<01:05:03.560> in<01:05:03.859> the 01:05:04.270 --> 01:05:04.280 align:start position:0% ID which scene you want to use in the 01:05:04.280 --> 01:05:07.080 align:start position:0% ID which scene you want to use in the moment<01:05:04.760> we<01:05:04.910> have<01:05:05.030> to<01:05:05.060> provide<01:05:05.480> on<01:05:05.869> a<01:05:06.050> girly<01:05:06.440> on 01:05:07.080 --> 01:05:07.090 align:start position:0% moment we have to provide on a girly on 01:05:07.090 --> 01:05:10.150 align:start position:0% moment we have to provide on a girly on comment<01:05:08.090> on<01:05:08.270> the<01:05:08.359> main<01:05:08.570> net<01:05:08.830> but<01:05:09.830> we<01:05:10.010> will 01:05:10.150 --> 01:05:10.160 align:start position:0% comment on the main net but we will 01:05:10.160 --> 01:05:16.250 align:start position:0% comment on the main net but we will probably<01:05:10.310> head<01:05:10.580> into<01:05:10.850> wrong<01:05:11.170> change<01:05:12.170> that 01:05:16.250 --> 01:05:16.260 align:start position:0% 01:05:16.260 --> 01:05:18.840 align:start position:0% how<01:05:17.260> do<01:05:17.320> you<01:05:17.530> establish<01:05:17.620> these<01:05:18.100> proofs<01:05:18.700> are 01:05:18.840 --> 01:05:18.850 align:start position:0% how do you establish these proofs are 01:05:18.850 --> 01:05:21.840 align:start position:0% how do you establish these proofs are going<01:05:19.750> through<01:05:20.230> their<01:05:20.410> roots<01:05:20.730> and<01:05:21.730> the 01:05:21.840 --> 01:05:21.850 align:start position:0% going through their roots and the 01:05:21.850 --> 01:05:24.210 align:start position:0% going through their roots and the treatment<01:05:22.270> is<01:05:22.360> part<01:05:22.630> of<01:05:22.690> the<01:05:22.780> head<01:05:22.900> to<01:05:23.770> the 01:05:24.210 --> 01:05:24.220 align:start position:0% treatment is part of the head to the 01:05:24.220 --> 01:05:29.010 align:start position:0% treatment is part of the head to the chamber<01:05:24.720> such<01:05:25.720> a<01:05:26.080> mood<01:05:27.510> recently<01:05:28.510> belongs<01:05:28.810> to 01:05:29.010 --> 01:05:29.020 align:start position:0% chamber such a mood recently belongs to 01:05:29.020 --> 01:05:33.510 align:start position:0% chamber such a mood recently belongs to the<01:05:29.110> chain<01:05:29.670> this<01:05:30.670> block<01:05:31.470> the<01:05:32.470> block<01:05:33.190> belongs 01:05:33.510 --> 01:05:33.520 align:start position:0% the chain this block the block belongs 01:05:33.520 --> 01:05:34.710 align:start position:0% the chain this block the block belongs to<01:05:33.640> the<01:05:33.730> tail<01:05:33.940> okay<01:05:34.240> yeah 01:05:34.710 --> 01:05:34.720 align:start position:0% to the tail okay yeah 01:05:34.720 --> 01:05:37.070 align:start position:0% to the tail okay yeah and<01:05:35.380> then<01:05:35.560> the<01:05:35.680> way<01:05:35.830> we<01:05:36.010> do<01:05:36.250> this<01:05:36.400> is<01:05:36.640> by 01:05:37.070 --> 01:05:37.080 align:start position:0% and then the way we do this is by 01:05:37.080 --> 01:05:40.290 align:start position:0% and then the way we do this is by getting<01:05:38.080> a<01:05:38.170> signature<01:05:38.790> from<01:05:39.790> gather<01:05:40.030> notes 01:05:40.290 --> 01:05:40.300 align:start position:0% getting a signature from gather notes 01:05:40.300 --> 01:05:42.720 align:start position:0% getting a signature from gather notes they<01:05:40.750> need<01:05:40.900> to<01:05:41.020> sign<01:05:41.320> but<01:05:41.890> this<01:05:42.040> location<01:05:42.490> is 01:05:42.720 --> 01:05:42.730 align:start position:0% they need to sign but this location is 01:05:42.730 --> 01:05:48.450 align:start position:0% they need to sign but this location is correct<01:05:43.440> and<01:05:44.440> the<01:05:44.890> reason<01:05:44.920> why<01:05:45.490> this<01:05:45.550> is<01:05:47.460> this 01:05:48.450 --> 01:05:48.460 align:start position:0% correct and the reason why this is this 01:05:48.460 --> 01:05:51.360 align:start position:0% correct and the reason why this is this works<01:05:48.790> is<01:05:49.090> because<01:05:49.150> the<01:05:50.140> signature<01:05:50.530> can<01:05:50.980> can 01:05:51.360 --> 01:05:51.370 align:start position:0% works is because the signature can can 01:05:51.370 --> 01:05:53.190 align:start position:0% works is because the signature can can then<01:05:51.520> be<01:05:51.670> passed<01:05:51.940> to<01:05:52.570> the<01:05:52.600> smart<01:05:52.930> contract 01:05:53.190 --> 01:05:53.200 align:start position:0% then be passed to the smart contract 01:05:53.200 --> 01:05:55.800 align:start position:0% then be passed to the smart contract itself<01:05:53.740> they<01:05:54.640> can<01:05:54.850> call<01:05:55.060> you<01:05:55.210> a<01:05:55.480> couple<01:05:55.750> to 01:05:55.800 --> 01:05:55.810 align:start position:0% itself they can call you a couple to 01:05:55.810 --> 01:05:57.540 align:start position:0% itself they can call you a couple to make<01:05:55.930> sure<01:05:56.050> that's<01:05:56.440> right<01:05:56.710> not<01:05:56.950> and<01:05:57.190> they<01:05:57.520> can 01:05:57.540 --> 01:05:57.550 align:start position:0% make sure that's right not and they can 01:05:57.550 --> 01:06:01.380 align:start position:0% make sure that's right not and they can also<01:05:58.030> verify<01:05:58.720> system<01:05:59.380> that<01:05:59.710> at<01:05:59.830> this<01:06:00.390> location 01:06:01.380 --> 01:06:01.390 align:start position:0% also verify system that at this location 01:06:01.390 --> 01:06:04.020 align:start position:0% also verify system that at this location is<01:06:02.110> correct<01:06:02.380> because<01:06:02.650> there's<01:06:02.980> opcode<01:06:03.460> ok 01:06:04.020 --> 01:06:04.030 align:start position:0% is correct because there's opcode ok 01:06:04.030 --> 01:06:06.660 align:start position:0% is correct because there's opcode ok popcorn<01:06:04.480> at<01:06:04.900> least<01:06:05.140> for<01:06:05.290> the<01:06:05.380> last<01:06:05.410> 150<01:06:06.370> six 01:06:06.660 --> 01:06:06.670 align:start position:0% popcorn at least for the last 150 six 01:06:06.670 --> 01:06:09.450 align:start position:0% popcorn at least for the last 150 six blocks<01:06:07.090> you<01:06:07.870> can<01:06:08.130> directing<01:06:09.130> the<01:06:09.250> spot 01:06:09.450 --> 01:06:09.460 align:start position:0% blocks you can directing the spot 01:06:09.460 --> 01:06:12.540 align:start position:0% blocks you can directing the spot contract<01:06:10.000> find<01:06:10.720> out<01:06:10.840> if<01:06:11.020> this<01:06:11.260> is<01:06:11.380> correct<01:06:11.590> so 01:06:12.540 --> 01:06:12.550 align:start position:0% contract find out if this is correct so 01:06:12.550 --> 01:06:15.030 align:start position:0% contract find out if this is correct so then<01:06:12.760> we<01:06:12.880> can<01:06:13.000> compare<01:06:13.360> and<01:06:13.630> we<01:06:14.230> know<01:06:14.380> even<01:06:14.740> the 01:06:15.030 --> 01:06:15.040 align:start position:0% then we can compare and we know even the 01:06:15.040 --> 01:06:16.350 align:start position:0% then we can compare and we know even the if<01:06:15.550> this<01:06:15.730> was<01:06:15.910> correct 01:06:16.350 --> 01:06:16.360 align:start position:0% if this was correct 01:06:16.360 --> 01:06:21.360 align:start position:0% if this was correct I<01:06:16.540> decide<01:06:17.020> it<01:06:17.680> was<01:06:18.070> not<01:06:18.540> and<01:06:19.540> it<01:06:19.660> was<01:06:19.840> not<01:06:20.140> then 01:06:21.360 --> 01:06:21.370 align:start position:0% I decide it was not and it was not then 01:06:21.370 --> 01:06:24.900 align:start position:0% I decide it was not and it was not then Cuba<01:06:21.760> two<01:06:21.880> systems<01:06:22.300> and<01:06:23.340> even<01:06:24.340> for<01:06:24.580> all<01:06:24.760> the 01:06:24.900 --> 01:06:24.910 align:start position:0% Cuba two systems and even for all the 01:06:24.910 --> 01:06:25.950 align:start position:0% Cuba two systems and even for all the clocks<01:06:25.090> because<01:06:25.330> this<01:06:25.510> was<01:06:25.630> in<01:06:25.780> the<01:06:25.870> beginning 01:06:25.950 --> 01:06:25.960 align:start position:0% clocks because this was in the beginning 01:06:25.960 --> 01:06:28.260 align:start position:0% clocks because this was in the beginning we<01:06:26.380> had<01:06:26.560> only<01:06:26.770> this<01:06:26.980> 256<01:06:27.880> box 01:06:28.260 --> 01:06:28.270 align:start position:0% we had only this 256 box 01:06:28.270 --> 01:06:30.900 align:start position:0% we had only this 256 box these<01:06:29.200> are<01:06:29.320> the<01:06:29.440> likely<01:06:29.770> low-hanging<01:06:30.460> food<01:06:30.760> is 01:06:30.900 --> 01:06:30.910 align:start position:0% these are the likely low-hanging food is 01:06:30.910 --> 01:06:33.760 align:start position:0% these are the likely low-hanging food is the<01:06:31.060> easy<01:06:31.270> one<01:06:31.480> but<01:06:32.290> also<01:06:32.530> if<01:06:32.830> you 01:06:33.760 --> 01:06:33.770 align:start position:0% the easy one but also if you 01:06:33.770 --> 01:06:37.240 align:start position:0% the easy one but also if you further<01:06:34.550> back<01:06:34.880> that<01:06:35.410> we<01:06:36.410> created<01:06:36.770> a<01:06:36.860> second 01:06:37.240 --> 01:06:37.250 align:start position:0% further back that we created a second 01:06:37.250 --> 01:06:38.710 align:start position:0% further back that we created a second contract<01:06:37.430> it's<01:06:37.760> a<01:06:37.820> professional<01:06:38.480> interest 01:06:38.710 --> 01:06:38.720 align:start position:0% contract it's a professional interest 01:06:38.720 --> 01:06:41.620 align:start position:0% contract it's a professional interest rate<01:06:38.930> where<01:06:39.890> you<01:06:40.160> can<01:06:40.460> then<01:06:40.670> construct<01:06:41.150> you 01:06:41.620 --> 01:06:41.630 align:start position:0% rate where you can then construct you 01:06:41.630 --> 01:06:42.430 align:start position:0% rate where you can then construct you know<01:06:41.780> Lovelock's 01:06:42.430 --> 01:06:42.440 align:start position:0% know Lovelock's 01:06:42.440 --> 01:06:44.380 align:start position:0% know Lovelock's you<01:06:43.010> need<01:06:43.190> to<01:06:43.280> deliver<01:06:43.580> the<01:06:43.790> proof<01:06:44.030> set<01:06:44.270> to 01:06:44.380 --> 01:06:44.390 align:start position:0% you need to deliver the proof set to 01:06:44.390 --> 01:06:46.840 align:start position:0% you need to deliver the proof set to work<01:06:44.570> on<01:06:44.750> the<01:06:45.170> truck<01:06:45.650> headers<01:06:46.010> and<01:06:46.520> out<01:06:46.700> of 01:06:46.840 --> 01:06:46.850 align:start position:0% work on the truck headers and out of 01:06:46.850 --> 01:06:49.360 align:start position:0% work on the truck headers and out of these<01:06:46.970> block<01:06:47.270> letters<01:06:47.660> you<01:06:48.260> can<01:06:48.500> then<01:06:48.710> prove 01:06:49.360 --> 01:06:49.370 align:start position:0% these block letters you can then prove 01:06:49.370 --> 01:06:51.790 align:start position:0% these block letters you can then prove that<01:06:49.610> certain<01:06:50.180> locations<01:06:50.930> -<01:06:51.110> one<01:06:51.470> for<01:06:51.680> this 01:06:51.790 --> 01:06:51.800 align:start position:0% that certain locations - one for this 01:06:51.800 --> 01:07:03.890 align:start position:0% that certain locations - one for this bubble 01:07:03.890 --> 01:07:03.900 align:start position:0% 01:07:03.900 --> 01:07:06.630 align:start position:0% exactly<01:07:04.900> that<01:07:05.530> we've<01:07:05.680> put<01:07:06.160> a<01:07:06.220> lot<01:07:06.310> of<01:07:06.430> thoughts 01:07:06.630 --> 01:07:06.640 align:start position:0% exactly that we've put a lot of thoughts 01:07:06.640 --> 01:07:09.000 align:start position:0% exactly that we've put a lot of thoughts in<01:07:06.820> it<01:07:06.970> as<01:07:07.120> well<01:07:07.420> because<01:07:07.690> you're<01:07:08.140> right<01:07:08.320> this 01:07:09.000 --> 01:07:09.010 align:start position:0% in it as well because you're right this 01:07:09.010 --> 01:07:11.660 align:start position:0% in it as well because you're right this is<01:07:09.070> something<01:07:09.700> again<01:07:10.000> that<01:07:10.350> too<01:07:11.350> many 01:07:11.660 --> 01:07:11.670 align:start position:0% is something again that too many 01:07:11.670 --> 01:07:13.800 align:start position:0% is something again that too many vegetables<01:07:12.670> don't<01:07:12.910> think<01:07:13.120> that<01:07:13.300> much<01:07:13.510> but 01:07:13.800 --> 01:07:13.810 align:start position:0% vegetables don't think that much but 01:07:13.810 --> 01:07:17.310 align:start position:0% vegetables don't think that much but fidelity<01:07:14.880> then<01:07:15.880> at<01:07:16.180> the<01:07:16.420> moment<01:07:16.570> there<01:07:17.140> is<01:07:17.290> a 01:07:17.310 --> 01:07:17.320 align:start position:0% fidelity then at the moment there is a 01:07:17.320 --> 01:07:19.380 align:start position:0% fidelity then at the moment there is a configuration<01:07:17.890> and<01:07:18.280> I<01:07:18.370> get<01:07:18.550> middle<01:07:19.150> box 01:07:19.380 --> 01:07:19.390 align:start position:0% configuration and I get middle box 01:07:19.390 --> 01:07:22.740 align:start position:0% configuration and I get middle box height<01:07:19.600> that<01:07:20.550> is<01:07:21.550> how<01:07:21.820> many<01:07:22.030> stalks<01:07:22.300> do<01:07:22.510> I<01:07:22.570> need 01:07:22.740 --> 01:07:22.750 align:start position:0% height that is how many stalks do I need 01:07:22.750 --> 01:07:24.990 align:start position:0% height that is how many stalks do I need away<01:07:22.930> before<01:07:23.200> I<01:07:23.500> actually<01:07:23.800> signing<01:07:24.220> location 01:07:24.990 --> 01:07:25.000 align:start position:0% away before I actually signing location 01:07:25.000 --> 01:07:26.760 align:start position:0% away before I actually signing location because<01:07:25.420> the<01:07:25.450> quality's<01:07:25.960> not<01:07:25.990> we'll<01:07:26.350> just<01:07:26.620> can 01:07:26.760 --> 01:07:26.770 align:start position:0% because the quality's not we'll just can 01:07:26.770 --> 01:07:29.940 align:start position:0% because the quality's not we'll just can we<01:07:26.800> trust<01:07:27.220> please<01:07:27.820> sign<01:07:28.360> up<01:07:28.660> number<01:07:29.020> X<01:07:29.230> and 01:07:29.940 --> 01:07:29.950 align:start position:0% we trust please sign up number X and 01:07:29.950 --> 01:07:32.400 align:start position:0% we trust please sign up number X and then<01:07:30.130> what<01:07:30.400> it<01:07:30.520> will<01:07:30.640> to<01:07:30.850> say<01:07:31.060> is<01:07:31.540> this<01:07:32.020> really 01:07:32.400 --> 01:07:32.410 align:start position:0% then what it will to say is this really 01:07:32.410 --> 01:07:35.100 align:start position:0% then what it will to say is this really final<01:07:32.920> because<01:07:33.850> if<01:07:34.030> it's<01:07:34.210> not<01:07:34.420> final<01:07:34.840> I<01:07:34.930> would 01:07:35.100 --> 01:07:35.110 align:start position:0% final because if it's not final I would 01:07:35.110 --> 01:07:38.610 align:start position:0% final because if it's not final I would risk<01:07:35.590> losing<01:07:35.950> that<01:07:36.640> deficit<01:07:37.210> chest<01:07:37.930> because<01:07:38.320> I 01:07:38.610 --> 01:07:38.620 align:start position:0% risk losing that deficit chest because I 01:07:38.620 --> 01:07:41.460 align:start position:0% risk losing that deficit chest because I know<01:07:38.680> they're<01:07:39.010> on<01:07:39.370> the<01:07:39.730> wrong<01:07:40.030> foot<01:07:40.390> I<01:07:40.720> mean<01:07:41.290> at 01:07:41.460 --> 01:07:41.470 align:start position:0% know they're on the wrong foot I mean at 01:07:41.470 --> 01:07:44.160 align:start position:0% know they're on the wrong foot I mean at the<01:07:41.530> moment<01:07:42.040> if<01:07:42.310> you<01:07:42.400> eat<01:07:42.790> ur<01:07:42.820> skin<01:07:43.660> packs<01:07:43.960> and 01:07:44.160 --> 01:07:44.170 align:start position:0% the moment if you eat ur skin packs and 01:07:44.170 --> 01:07:46.290 align:start position:0% the moment if you eat ur skin packs and what<01:07:44.320> the<01:07:44.530> f<01:07:44.680> this<01:07:44.830> is<01:07:45.040> nice<01:07:45.250> that<01:07:45.520> there<01:07:46.180> were 01:07:46.290 --> 01:07:46.300 align:start position:0% what the f this is nice that there were 01:07:46.300 --> 01:07:49.700 align:start position:0% what the f this is nice that there were max<01:07:47.430> greenbox<01:07:48.430> some<01:07:48.970> Reeboks 01:07:49.700 --> 01:07:49.710 align:start position:0% max greenbox some Reeboks 01:07:49.710 --> 01:07:52.800 align:start position:0% max greenbox some Reeboks this<01:07:50.710> kind<01:07:51.160> of<01:07:51.250> um<01:07:51.370> but<01:07:52.030> it<01:07:52.210> moment<01:07:52.690> as<01:07:52.780> a 01:07:52.800 --> 01:07:52.810 align:start position:0% this kind of um but it moment as a 01:07:52.810 --> 01:07:55.950 align:start position:0% this kind of um but it moment as a people<01:07:53.260> we<01:07:53.590> use<01:07:53.800> for<01:07:54.340> six<01:07:54.550> blocks<01:07:54.840> so<01:07:55.840> it 01:07:55.950 --> 01:07:55.960 align:start position:0% people we use for six blocks so it 01:07:55.960 --> 01:07:58.770 align:start position:0% people we use for six blocks so it usually<01:07:56.290> the<01:07:56.680> note<01:07:57.400> will<01:07:57.640> not<01:07:57.820> sign<01:07:58.180> any<01:07:58.480> drop 01:07:58.770 --> 01:07:58.780 align:start position:0% usually the note will not sign any drop 01:07:58.780 --> 01:08:02.700 align:start position:0% usually the note will not sign any drop that<01:07:58.990> is<01:07:59.170> younger<01:07:59.410> than<01:07:59.650> six<01:08:00.100> box<01:08:01.470> so<01:08:02.470> that's 01:08:02.700 --> 01:08:02.710 align:start position:0% that is younger than six box so that's 01:08:02.710 --> 01:08:05.520 align:start position:0% that is younger than six box so that's why<01:08:02.920> if<01:08:03.700> you<01:08:03.910> ask<01:08:04.180> for<01:08:04.360> something<01:08:04.690> that's 01:08:05.520 --> 01:08:05.530 align:start position:0% why if you ask for something that's 01:08:05.530 --> 01:08:07.560 align:start position:0% why if you ask for something that's under<01:08:05.830> this<01:08:06.220> you<01:08:06.910> will<01:08:07.030> not<01:08:07.180> get<01:08:07.390> any 01:08:07.560 --> 01:08:07.570 align:start position:0% under this you will not get any 01:08:07.570 --> 01:08:13.349 align:start position:0% under this you will not get any signature<01:08:08.490> the<01:08:09.490> latest<01:08:09.850> book<01:08:10.120> is<01:08:10.300> not<01:08:10.510> fine 01:08:13.349 --> 01:08:13.359 align:start position:0% 01:08:13.359 --> 01:08:17.800 align:start position:0% whose<01:08:14.359> RTC<01:08:14.900> qualify<01:08:15.380> us<01:08:15.559> for<01:08:15.589> latest<01:08:16.719> kind<01:08:17.719> of 01:08:17.800 --> 01:08:17.810 align:start position:0% whose RTC qualify us for latest kind of 01:08:17.810 --> 01:08:21.220 align:start position:0% whose RTC qualify us for latest kind of support<01:08:18.290> right<01:08:18.790> you<01:08:19.790> would<01:08:20.000> probably<01:08:20.299> have 01:08:21.220 --> 01:08:21.230 align:start position:0% support right you would probably have 01:08:21.230 --> 01:08:24.959 align:start position:0% support right you would probably have the<01:08:21.380> latest<01:08:21.560> but<01:08:21.980> tomorrow<01:08:22.339> for<01:08:23.139> latest<01:08:24.139> life 01:08:24.959 --> 01:08:24.969 align:start position:0% the latest but tomorrow for latest life 01:08:24.969 --> 01:08:27.760 align:start position:0% the latest but tomorrow for latest life checking<01:08:25.969> the<01:08:26.060> decision<01:08:26.569> for<01:08:26.960> the<01:08:27.049> thing<01:08:27.230> so 01:08:27.760 --> 01:08:27.770 align:start position:0% checking the decision for the thing so 01:08:27.770 --> 01:08:30.760 align:start position:0% checking the decision for the thing so nobody<01:08:28.159> thinks<01:08:28.250> about<01:08:28.639> it<01:08:29.060> asking<01:08:29.870> for<01:08:30.380> us<01:08:30.589> or 01:08:30.760 --> 01:08:30.770 align:start position:0% nobody thinks about it asking for us or 01:08:30.770 --> 01:08:32.919 align:start position:0% nobody thinks about it asking for us or four<01:08:31.009> days<01:08:31.190> ago<01:08:31.549> but<01:08:32.150> it<01:08:32.270> is<01:08:32.389> also<01:08:32.659> not<01:08:32.870> the 01:08:32.919 --> 01:08:32.929 align:start position:0% four days ago but it is also not the 01:08:32.929 --> 01:08:36.280 align:start position:0% four days ago but it is also not the security<01:08:33.560> vision<01:08:33.889> because<01:08:34.279> so<01:08:35.120> Sergio<01:08:35.569> puree 01:08:36.280 --> 01:08:36.290 align:start position:0% security vision because so Sergio puree 01:08:36.290 --> 01:08:39.760 align:start position:0% security vision because so Sergio puree is<01:08:36.589> the<01:08:36.739> only<01:08:37.040> little<01:08:37.580> pain<01:08:37.989> if<01:08:38.989> you<01:08:39.109> asked<01:08:39.589> for 01:08:39.760 --> 01:08:39.770 align:start position:0% is the only little pain if you asked for 01:08:39.770 --> 01:08:41.829 align:start position:0% is the only little pain if you asked for today's<01:08:40.190> product<01:08:40.790> you<01:08:41.179> will<01:08:41.330> never<01:08:41.480> get<01:08:41.750> the 01:08:41.829 --> 01:08:41.839 align:start position:0% today's product you will never get the 01:08:41.839 --> 01:08:52.180 align:start position:0% today's product you will never get the signature<01:08:42.139> because<01:08:42.589> no<01:08:42.980> note<01:08:43.639> will<01:08:43.940> sign<01:08:44.600> it<01:08:51.190> I 01:08:52.180 --> 01:08:52.190 align:start position:0% signature because no note will sign it I 01:08:52.190 --> 01:08:54.370 align:start position:0% signature because no note will sign it I mean<01:08:52.549> s<01:08:52.699> exactly<01:08:52.969> what<01:08:53.150> happened<01:08:53.569> we<01:08:53.659> can<01:08:54.199> test 01:08:54.370 --> 01:08:54.380 align:start position:0% mean s exactly what happened we can test 01:08:54.380 --> 01:08:55.899 align:start position:0% mean s exactly what happened we can test it<01:08:54.560> body<01:08:54.799> what's<01:08:55.040> happening<01:08:55.400> is<01:08:55.489> that<01:08:55.520> if<01:08:55.790> you 01:08:55.899 --> 01:08:55.909 align:start position:0% it body what's happening is that if you 01:08:55.909 --> 01:08:58.059 align:start position:0% it body what's happening is that if you climb<01:08:56.239> more<01:08:56.540> than<01:08:56.719> simply<01:08:56.989> say<01:08:57.230> you<01:08:57.799> will<01:08:57.920> be 01:08:58.059 --> 01:08:58.069 align:start position:0% climb more than simply say you will be 01:08:58.069 --> 01:08:59.919 align:start position:0% climb more than simply say you will be tracked<01:08:58.339> them<01:08:58.549> to<01:08:58.670> respond<01:08:59.029> to<01:08:59.060> us<01:08:59.210> to<01:08:59.480> set<01:08:59.659> I 01:08:59.919 --> 01:08:59.929 align:start position:0% tracked them to respond to us to set I 01:08:59.929 --> 01:09:03.500 align:start position:0% tracked them to respond to us to set I want<01:09:00.380> to<01:09:00.469> have<01:09:00.620> two<01:09:00.980> signatures 01:09:03.500 --> 01:09:03.510 align:start position:0% want to have two signatures 01:09:03.510 --> 01:09:09.970 align:start position:0% want to have two signatures [Applause] 01:09:09.970 --> 01:09:09.980 align:start position:0% 01:09:09.980 --> 01:09:12.040 align:start position:0% you