WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.320 align:start position:0% [Applause] 00:00:11.320 --> 00:00:11.330 align:start position:0% 00:00:11.330 --> 00:00:16.369 align:start position:0% okay<00:00:12.330> well<00:00:12.629> let's<00:00:12.869> let's<00:00:13.410> start<00:00:15.199> well<00:00:16.199> I'm 00:00:16.369 --> 00:00:16.379 align:start position:0% okay well let's let's start well I'm 00:00:16.379 --> 00:00:18.909 align:start position:0% okay well let's let's start well I'm totally<00:00:16.590> marina<00:00:16.980> and<00:00:17.250> the<00:00:17.340> technical<00:00:17.789> lead<00:00:17.939> of 00:00:18.909 --> 00:00:18.919 align:start position:0% totally marina and the technical lead of 00:00:18.919 --> 00:00:21.769 align:start position:0% totally marina and the technical lead of Legacy<00:00:19.919> Project<00:00:20.250> and<00:00:20.759> if<00:00:20.880> the<00:00:21.000> project<00:00:21.270> is<00:00:21.599> an 00:00:21.769 --> 00:00:21.779 align:start position:0% Legacy Project and if the project is an 00:00:21.779 --> 00:00:24.550 align:start position:0% Legacy Project and if the project is an identity<00:00:22.169> project<00:00:22.739> that<00:00:23.189> tries<00:00:23.340> to<00:00:23.640> solve 00:00:24.550 --> 00:00:24.560 align:start position:0% identity project that tries to solve 00:00:24.560 --> 00:00:27.920 align:start position:0% identity project that tries to solve self<00:00:25.560> sobriquet<00:00:26.009> identity<00:00:26.520> in<00:00:27.180> a<00:00:27.419> scalable 00:00:27.920 --> 00:00:27.930 align:start position:0% self sobriquet identity in a scalable 00:00:27.930 --> 00:00:30.859 align:start position:0% self sobriquet identity in a scalable manner<00:00:28.259> in<00:00:28.829> an<00:00:28.980> accessible<00:00:29.610> manner<00:00:29.939> so<00:00:30.660> that's 00:00:30.859 --> 00:00:30.869 align:start position:0% manner in an accessible manner so that's 00:00:30.869 --> 00:00:32.930 align:start position:0% manner in an accessible manner so that's available<00:00:31.079> for<00:00:31.469> the<00:00:31.590> users<00:00:31.919> once<00:00:32.640> that 00:00:32.930 --> 00:00:32.940 align:start position:0% available for the users once that 00:00:32.940 --> 00:00:36.470 align:start position:0% available for the users once that everybody<00:00:33.420> be<00:00:33.600> able<00:00:33.870> to<00:00:34.110> be<00:00:34.370> a<00:00:35.480> certification 00:00:36.470 --> 00:00:36.480 align:start position:0% everybody be able to be a certification 00:00:36.480 --> 00:00:39.170 align:start position:0% everybody be able to be a certification authority<00:00:37.050> Phi<00:00:37.200> itself<00:00:37.559> and<00:00:38.010> we<00:00:38.789> want<00:00:38.969> to<00:00:39.059> do 00:00:39.170 --> 00:00:39.180 align:start position:0% authority Phi itself and we want to do 00:00:39.180 --> 00:00:42.680 align:start position:0% authority Phi itself and we want to do that<00:00:39.329> in<00:00:39.690> a<00:00:40.160> privacy<00:00:41.160> by<00:00:41.370> default<00:00:41.760> my<00:00:42.060> design 00:00:42.680 --> 00:00:42.690 align:start position:0% that in a privacy by default my design 00:00:42.690 --> 00:00:46.010 align:start position:0% that in a privacy by default my design that's<00:00:42.989> the<00:00:43.079> main<00:00:43.230> goal<00:00:43.260> of<00:00:43.440> IV<00:00:44.220> 3<00:00:44.579> in<00:00:45.540> these 00:00:46.010 --> 00:00:46.020 align:start position:0% that's the main goal of IV 3 in these 00:00:46.020 --> 00:00:47.690 align:start position:0% that's the main goal of IV 3 in these when<00:00:46.350> we<00:00:46.470> talk<00:00:46.620> about<00:00:46.770> the<00:00:46.980> stability<00:00:47.220> of 00:00:47.690 --> 00:00:47.700 align:start position:0% when we talk about the stability of 00:00:47.700 --> 00:00:51.979 align:start position:0% when we talk about the stability of these<00:00:48.090> 1<00:00:48.480> 1<00:00:48.510> is<00:00:48.899> to<00:00:49.110> system<00:00:49.590> to<00:00:49.680> be<00:00:49.800> a<00:00:49.829> skill<00:00:50.989> we 00:00:51.979 --> 00:00:51.989 align:start position:0% these 1 1 is to system to be a skill we 00:00:51.989 --> 00:00:53.810 align:start position:0% these 1 1 is to system to be a skill we have<00:00:52.170> a<00:00:52.200> piece<00:00:52.530> we<00:00:53.040> call<00:00:53.220> it<00:00:53.310> the<00:00:53.399> trusted 00:00:53.810 --> 00:00:53.820 align:start position:0% have a piece we call it the trusted 00:00:53.820 --> 00:00:56.330 align:start position:0% have a piece we call it the trusted trusted<00:00:54.270> relay<00:00:54.750> here<00:00:54.930> mainly<00:00:55.890> is<00:00:56.010> a<00:00:56.040> piece 00:00:56.330 --> 00:00:56.340 align:start position:0% trusted relay here mainly is a piece 00:00:56.340 --> 00:00:59.690 align:start position:0% trusted relay here mainly is a piece that<00:00:56.370> puts<00:00:56.820> a<00:00:56.970> lot<00:00:57.149> of<00:00:57.360> claims<00:00:57.660> and<00:00:58.460> we<00:00:59.460> need 00:00:59.690 --> 00:00:59.700 align:start position:0% that puts a lot of claims and we need 00:00:59.700 --> 00:01:02.840 align:start position:0% that puts a lot of claims and we need that<00:00:59.970> is<00:01:00.149> earlier<00:01:01.250> what<00:01:02.250> you<00:01:02.370> don't<00:01:02.550> have<00:01:02.670> to 00:01:02.840 --> 00:01:02.850 align:start position:0% that is earlier what you don't have to 00:01:02.850 --> 00:01:05.870 align:start position:0% that is earlier what you don't have to trust<00:01:03.030> it<00:01:03.300> so<00:01:03.510> that<00:01:03.719> you<00:01:04.170> can<00:01:04.379> achieve<00:01:04.559> ok<00:01:05.460> and 00:01:05.870 --> 00:01:05.880 align:start position:0% trust it so that you can achieve ok and 00:01:05.880 --> 00:01:09.109 align:start position:0% trust it so that you can achieve ok and following<00:01:06.270> this<00:01:06.540> hour<00:01:06.899> later<00:01:07.860> we<00:01:08.549> we<00:01:09.000> are 00:01:09.109 --> 00:01:09.119 align:start position:0% following this hour later we we are 00:01:09.119 --> 00:01:10.999 align:start position:0% following this hour later we we are using<00:01:09.570> what<00:01:09.719> we<00:01:09.810> have<00:01:09.990> to<00:01:10.140> use<00:01:10.320> the<00:01:10.439> technology 00:01:10.999 --> 00:01:11.009 align:start position:0% using what we have to use the technology 00:01:11.009 --> 00:01:15.709 align:start position:0% using what we have to use the technology that's<00:01:11.540> mainly<00:01:12.540> the<00:01:12.890> the<00:01:13.890> sycamore<00:01:14.459> button<00:01:14.880> ok 00:01:15.709 --> 00:01:15.719 align:start position:0% that's mainly the the sycamore button ok 00:01:15.719 --> 00:01:18.279 align:start position:0% that's mainly the the sycamore button ok so<00:01:15.780> we<00:01:16.469> decided<00:01:16.859> in<00:01:17.159> item<00:01:17.429> free<00:01:17.639> to<00:01:17.909> implement 00:01:18.279 --> 00:01:18.289 align:start position:0% so we decided in item free to implement 00:01:18.289 --> 00:01:21.230 align:start position:0% so we decided in item free to implement also<00:01:19.289> the<00:01:19.469> Z<00:01:19.619> Carolla<00:01:20.009> because<00:01:20.369> most<00:01:20.939> of<00:01:21.119> the 00:01:21.230 --> 00:01:21.240 align:start position:0% also the Z Carolla because most of the 00:01:21.240 --> 00:01:23.179 align:start position:0% also the Z Carolla because most of the pieces<00:01:21.420> are<00:01:21.899> exactly<00:01:22.109> the<00:01:22.889> same 00:01:23.179 --> 00:01:23.189 align:start position:0% pieces are exactly the same 00:01:23.189 --> 00:01:25.639 align:start position:0% pieces are exactly the same ok<00:01:24.060> so<00:01:24.149> in<00:01:24.450> this<00:01:24.600> presentation<00:01:24.780> maybe<00:01:25.439> I'm 00:01:25.639 --> 00:01:25.649 align:start position:0% ok so in this presentation maybe I'm 00:01:25.649 --> 00:01:28.249 align:start position:0% ok so in this presentation maybe I'm gonna<00:01:25.859> talk<00:01:26.130> about<00:01:26.789> the<00:01:27.029> second<00:01:27.359> rule<00:01:27.539> of<00:01:27.630> hoho 00:01:28.249 --> 00:01:28.259 align:start position:0% gonna talk about the second rule of hoho 00:01:28.259 --> 00:01:30.199 align:start position:0% gonna talk about the second rule of hoho we<00:01:28.499> work<00:01:28.709> how<00:01:29.100> we<00:01:29.159> work<00:01:29.399> recommendation<00:01:30.090> that 00:01:30.199 --> 00:01:30.209 align:start position:0% we work how we work recommendation that 00:01:30.209 --> 00:01:32.539 align:start position:0% we work how we work recommendation that we<00:01:30.389> are<00:01:30.479> building<00:01:30.840> right<00:01:30.899> now<00:01:31.139> and<00:01:31.549> explain 00:01:32.539 --> 00:01:32.549 align:start position:0% we are building right now and explain 00:01:32.549 --> 00:01:35.059 align:start position:0% we are building right now and explain some<00:01:32.789> of<00:01:32.819> the<00:01:32.999> details<00:01:33.450> surface<00:01:34.009> okay<00:01:35.009> so 00:01:35.059 --> 00:01:35.069 align:start position:0% some of the details surface okay so 00:01:35.069 --> 00:01:38.599 align:start position:0% some of the details surface okay so let's<00:01:35.490> start<00:01:35.819> well<00:01:36.719> this<00:01:37.109> is<00:01:37.229> just<00:01:37.649> a<00:01:37.740> little 00:01:38.599 --> 00:01:38.609 align:start position:0% let's start well this is just a little 00:01:38.609 --> 00:01:43.359 align:start position:0% let's start well this is just a little bit<00:01:38.749> of<00:01:39.749> a<00:01:39.869> spoiler<00:01:40.490> this<00:01:41.490> is<00:01:41.639> the<00:01:41.729> results 00:01:43.359 --> 00:01:43.369 align:start position:0% bit of a spoiler this is the results 00:01:43.369 --> 00:01:45.830 align:start position:0% bit of a spoiler this is the results that<00:01:44.369> people<00:01:44.549> are<00:01:45.029> possible<00:01:45.539> with<00:01:45.749> this 00:01:45.830 --> 00:01:45.840 align:start position:0% that people are possible with this 00:01:45.840 --> 00:01:48.230 align:start position:0% that people are possible with this system<00:01:46.079> it's<00:01:46.799> important<00:01:47.429> important<00:01:48.029> to<00:01:48.090> see 00:01:48.230 --> 00:01:48.240 align:start position:0% system it's important important to see 00:01:48.240 --> 00:01:50.749 align:start position:0% system it's important important to see that<00:01:48.270> this<00:01:48.659> is<00:01:48.869> just<00:01:48.899> a<00:01:49.319> theory<00:01:49.499> of<00:01:49.619> 1.0<00:01:50.340> is<00:01:50.369> we 00:01:50.749 --> 00:01:50.759 align:start position:0% that this is just a theory of 1.0 is we 00:01:50.759 --> 00:01:52.489 align:start position:0% that this is just a theory of 1.0 is we are<00:01:50.819> not<00:01:50.969> talking<00:01:51.270> of<00:01:51.539> here<00:01:51.869> and<00:01:52.170> the<00:01:52.259> theorem 00:01:52.489 --> 00:01:52.499 align:start position:0% are not talking of here and the theorem 00:01:52.499 --> 00:01:54.739 align:start position:0% are not talking of here and the theorem 2.0<00:01:53.009> we<00:01:53.549> can<00:01:53.700> talking<00:01:54.060> about<00:01:54.299> anything<00:01:54.569> just 00:01:54.739 --> 00:01:54.749 align:start position:0% 2.0 we can talking about anything just 00:01:54.749 --> 00:01:59.239 align:start position:0% 2.0 we can talking about anything just is<00:01:55.109> just<00:01:55.679> using<00:01:56.069> if<00:01:56.939> you<00:01:57.149> see<00:01:57.810> one<00:01:58.469> of<00:01:58.499> 0<00:01:58.919> in<00:01:59.099> the 00:01:59.239 --> 00:01:59.249 align:start position:0% is just using if you see one of 0 in the 00:01:59.249 --> 00:02:01.069 align:start position:0% is just using if you see one of 0 in the lower<00:01:59.399> layer<00:01:59.700> ok<00:02:00.359> so<00:02:00.569> let's<00:02:00.749> see<00:02:00.869> how<00:02:01.020> we 00:02:01.069 --> 00:02:01.079 align:start position:0% lower layer ok so let's see how we 00:02:01.079 --> 00:02:04.940 align:start position:0% lower layer ok so let's see how we achieve<00:02:01.469> these<00:02:01.649> results<00:02:02.810> what's<00:02:03.810> the<00:02:04.499> general 00:02:04.940 --> 00:02:04.950 align:start position:0% achieve these results what's the general 00:02:04.950 --> 00:02:09.359 align:start position:0% achieve these results what's the general idea<00:02:05.490> of<00:02:05.549> the<00:02:05.909> roll-up<00:02:06.630> idea<00:02:07.409> here<00:02:08.190> is 00:02:09.359 --> 00:02:09.369 align:start position:0% idea of the roll-up idea here is 00:02:09.369 --> 00:02:11.759 align:start position:0% idea of the roll-up idea here is sidechain<00:02:10.060> like<00:02:10.569> plasma<00:02:10.840> if<00:02:11.349> some<00:02:11.560> of<00:02:11.650> you 00:02:11.759 --> 00:02:11.769 align:start position:0% sidechain like plasma if some of you 00:02:11.769 --> 00:02:16.369 align:start position:0% sidechain like plasma if some of you have<00:02:11.980> been<00:02:12.010> using<00:02:12.720> in<00:02:13.720> sidechain<00:02:14.500> we<00:02:14.860> have<00:02:15.129> our 00:02:16.369 --> 00:02:16.379 align:start position:0% have been using in sidechain we have our 00:02:16.379 --> 00:02:19.680 align:start position:0% have been using in sidechain we have our database<00:02:17.379> of<00:02:17.739> balances<00:02:18.400> all<00:02:18.670> these<00:02:19.180> balances 00:02:19.680 --> 00:02:19.690 align:start position:0% database of balances all these balances 00:02:19.690 --> 00:02:22.710 align:start position:0% database of balances all these balances is<00:02:19.920> Naaman<00:02:20.920> sustained<00:02:21.310> all<00:02:21.760> these<00:02:22.209> states<00:02:22.569> to 00:02:22.710 --> 00:02:22.720 align:start position:0% is Naaman sustained all these states to 00:02:22.720 --> 00:02:24.630 align:start position:0% is Naaman sustained all these states to create<00:02:23.110> like<00:02:23.290> a<00:02:23.319> merging<00:02:23.739> true<00:02:23.950> American<00:02:24.430> tree 00:02:24.630 --> 00:02:24.640 align:start position:0% create like a merging true American tree 00:02:24.640 --> 00:02:26.850 align:start position:0% create like a merging true American tree and<00:02:25.000> we<00:02:25.209> have<00:02:25.390> a<00:02:25.420> rule<00:02:25.690> we<00:02:25.840> have<00:02:25.989> a<00:02:26.019> hypothesis 00:02:26.850 --> 00:02:26.860 align:start position:0% and we have a rule we have a hypothesis 00:02:26.860 --> 00:02:29.670 align:start position:0% and we have a rule we have a hypothesis States<00:02:27.360> it<00:02:28.360> is<00:02:28.480> a<00:02:28.540> state<00:02:28.780> we<00:02:28.989> have<00:02:29.230> a<00:02:29.440> set<00:02:29.650> of 00:02:29.670 --> 00:02:29.680 align:start position:0% States it is a state we have a set of 00:02:29.680 --> 00:02:31.470 align:start position:0% States it is a state we have a set of transactions<00:02:30.400> that<00:02:30.519> we<00:02:30.700> were<00:02:30.909> that<00:02:31.329> we 00:02:31.470 --> 00:02:31.480 align:start position:0% transactions that we were that we 00:02:31.480 --> 00:02:33.180 align:start position:0% transactions that we were that we correct<00:02:31.780> that<00:02:31.959> we<00:02:32.140> put<00:02:32.290> in<00:02:32.409> a<00:02:32.500> batch<00:02:32.680> and<00:02:33.040> in 00:02:33.180 --> 00:02:33.190 align:start position:0% correct that we put in a batch and in 00:02:33.190 --> 00:02:36.119 align:start position:0% correct that we put in a batch and in each<00:02:33.310> much<00:02:33.549> we<00:02:34.360> create<00:02:34.720> new<00:02:35.470> estate<00:02:35.799> so<00:02:36.010> we 00:02:36.119 --> 00:02:36.129 align:start position:0% each much we create new estate so we 00:02:36.129 --> 00:02:37.860 align:start position:0% each much we create new estate so we process<00:02:36.610> a<00:02:36.640> set<00:02:36.879> of<00:02:37.030> transactions<00:02:37.569> for<00:02:37.750> each 00:02:37.860 --> 00:02:37.870 align:start position:0% process a set of transactions for each 00:02:37.870 --> 00:02:40.830 align:start position:0% process a set of transactions for each for<00:02:38.260> each<00:02:38.290> batch<00:02:38.620> and<00:02:38.920> the<00:02:39.760> thing<00:02:40.299> here<00:02:40.629> is 00:02:40.830 --> 00:02:40.840 align:start position:0% for each batch and the thing here is 00:02:40.840 --> 00:02:44.670 align:start position:0% for each batch and the thing here is that<00:02:40.870> in<00:02:41.319> the<00:02:41.440> in<00:02:42.340> the<00:02:42.549> blockchain<00:02:43.359> in<00:02:44.170> general 00:02:44.670 --> 00:02:44.680 align:start position:0% that in the in the blockchain in general 00:02:44.680 --> 00:02:46.920 align:start position:0% that in the in the blockchain in general we<00:02:44.920> just<00:02:45.280> put<00:02:45.609> this<00:02:46.060> state 00:02:46.920 --> 00:02:46.930 align:start position:0% we just put this state 00:02:46.930 --> 00:02:49.920 align:start position:0% we just put this state okay<00:02:47.349> so<00:02:47.980> impossible<00:02:48.700> for<00:02:49.030> example<00:02:49.480> this<00:02:49.660> is 00:02:49.920 --> 00:02:49.930 align:start position:0% okay so impossible for example this is 00:02:49.930 --> 00:02:52.050 align:start position:0% okay so impossible for example this is how<00:02:50.620> we<00:02:50.769> warranty<00:02:51.310> that<00:02:51.549> this<00:02:51.700> estate<00:02:52.030> is 00:02:52.050 --> 00:02:52.060 align:start position:0% how we warranty that this estate is 00:02:52.060 --> 00:02:54.180 align:start position:0% how we warranty that this estate is valid<00:02:52.599> pramana<00:02:52.780> tina<00:02:53.290> these<00:02:53.530> sanctions<00:02:53.980> are 00:02:54.180 --> 00:02:54.190 align:start position:0% valid pramana tina these sanctions are 00:02:54.190 --> 00:02:56.009 align:start position:0% valid pramana tina these sanctions are processes<00:02:54.640> in<00:02:54.700> the<00:02:54.819> right<00:02:55.000> order<00:02:55.569> in<00:02:55.959> the 00:02:56.009 --> 00:02:56.019 align:start position:0% processes in the right order in the 00:02:56.019 --> 00:02:57.539 align:start position:0% processes in the right order in the right<00:02:56.200> way<00:02:56.409> that<00:02:56.680> there<00:02:57.099> is<00:02:57.159> no<00:02:57.220> dollar 00:02:57.539 --> 00:02:57.549 align:start position:0% right way that there is no dollar 00:02:57.549 --> 00:02:59.550 align:start position:0% right way that there is no dollar spendings<00:02:58.090> that<00:02:58.390> everything<00:02:58.840> more<00:02:59.049> it's 00:02:59.550 --> 00:02:59.560 align:start position:0% spendings that everything more it's 00:02:59.560 --> 00:03:02.729 align:start position:0% spendings that everything more it's exactly<00:03:00.099> in<00:03:00.640> feeds<00:03:00.940> so<00:03:01.599> you<00:03:01.989> +<00:03:02.200> mother<00:03:02.409> is<00:03:02.590> this 00:03:02.729 --> 00:03:02.739 align:start position:0% exactly in feeds so you + mother is this 00:03:02.739 --> 00:03:04.740 align:start position:0% exactly in feeds so you + mother is this gaming<00:03:03.190> a<00:03:03.280> staff<00:03:03.519> in<00:03:03.790> zero<00:03:04.090> latency<00:03:04.269> that's 00:03:04.740 --> 00:03:04.750 align:start position:0% gaming a staff in zero latency that's 00:03:04.750 --> 00:03:07.080 align:start position:0% gaming a staff in zero latency that's not<00:03:04.930> in<00:03:05.049> sync<00:03:05.349> Aurora<00:03:05.769> maybe<00:03:06.340> what<00:03:06.579> we<00:03:06.730> do<00:03:06.879> is 00:03:07.080 --> 00:03:07.090 align:start position:0% not in sync Aurora maybe what we do is 00:03:07.090 --> 00:03:10.259 align:start position:0% not in sync Aurora maybe what we do is besides<00:03:07.870> just<00:03:07.930> the<00:03:08.200> needs<00:03:08.379> next<00:03:08.890> step<00:03:09.269> besides 00:03:10.259 --> 00:03:10.269 align:start position:0% besides just the needs next step besides 00:03:10.269 --> 00:03:15.479 align:start position:0% besides just the needs next step besides the<00:03:10.390> next<00:03:11.400> state<00:03:12.400> we<00:03:13.000> also<00:03:13.450> put<00:03:14.109> proof<00:03:14.799> that 00:03:15.479 --> 00:03:15.489 align:start position:0% the next state we also put proof that 00:03:15.489 --> 00:03:17.580 align:start position:0% the next state we also put proof that this<00:03:15.700> state<00:03:16.120> is<00:03:16.389> bombed<00:03:16.810> this<00:03:17.109> is<00:03:17.230> a<00:03:17.260> zero 00:03:17.580 --> 00:03:17.590 align:start position:0% this state is bombed this is a zero 00:03:17.590 --> 00:03:23.280 align:start position:0% this state is bombed this is a zero knowledge<00:03:17.769> proof<00:03:17.970> okay<00:03:18.970> so<00:03:19.599> here<00:03:20.560> is<00:03:22.079> the<00:03:23.079> keep 00:03:23.280 --> 00:03:23.290 align:start position:0% knowledge proof okay so here is the keep 00:03:23.290 --> 00:03:25.830 align:start position:0% knowledge proof okay so here is the keep is<00:03:23.470> the<00:03:23.799> key<00:03:23.980> technology<00:03:24.609> that<00:03:25.209> makes<00:03:25.660> this 00:03:25.830 --> 00:03:25.840 align:start position:0% is the key technology that makes this 00:03:25.840 --> 00:03:27.869 align:start position:0% is the key technology that makes this enable<00:03:26.349> this<00:03:26.739> is<00:03:26.889> the<00:03:27.040> sickest<00:03:27.370> Norris<00:03:27.790> the 00:03:27.869 --> 00:03:27.879 align:start position:0% enable this is the sickest Norris the 00:03:27.879 --> 00:03:30.240 align:start position:0% enable this is the sickest Norris the important<00:03:28.480> part<00:03:28.690> here<00:03:29.019> is<00:03:29.079> the<00:03:29.410> s<00:03:29.620> that's<00:03:30.010> just 00:03:30.240 --> 00:03:30.250 align:start position:0% important part here is the s that's just 00:03:30.250 --> 00:03:33.390 align:start position:0% important part here is the s that's just from<00:03:30.489> succeed<00:03:30.970> that<00:03:31.780> means<00:03:32.049> that<00:03:32.319> we<00:03:33.129> can 00:03:33.390 --> 00:03:33.400 align:start position:0% from succeed that means that we can 00:03:33.400 --> 00:03:36.479 align:start position:0% from succeed that means that we can generate<00:03:33.609> the<00:03:34.090> proof<00:03:34.359> that<00:03:34.989> maybe<00:03:35.400> 1,000<00:03:36.400> or 00:03:36.479 --> 00:03:36.489 align:start position:0% generate the proof that maybe 1,000 or 00:03:36.489 --> 00:03:39.089 align:start position:0% generate the proof that maybe 1,000 or even<00:03:36.579> 31<00:03:37.540> million<00:03:37.780> transactions<00:03:38.530> are<00:03:38.680> valid 00:03:39.089 --> 00:03:39.099 align:start position:0% even 31 million transactions are valid 00:03:39.099 --> 00:03:40.740 align:start position:0% even 31 million transactions are valid from<00:03:39.699> one<00:03:39.879> state<00:03:40.239> to<00:03:40.269> the<00:03:40.419> other 00:03:40.740 --> 00:03:40.750 align:start position:0% from one state to the other 00:03:40.750 --> 00:03:44.220 align:start position:0% from one state to the other so<00:03:41.230> we<00:03:41.319> have<00:03:41.500> one<00:03:41.709> 256<00:03:42.669> bytes<00:03:42.879> just<00:03:43.690> a<00:03:43.810> hot 00:03:44.220 --> 00:03:44.230 align:start position:0% so we have one 256 bytes just a hot 00:03:44.230 --> 00:03:46.259 align:start position:0% so we have one 256 bytes just a hot summer<00:03:44.470> state<00:03:44.709> we<00:03:45.250> go<00:03:45.430> to<00:03:45.489> the<00:03:45.730> next<00:03:45.910> state 00:03:46.259 --> 00:03:46.269 align:start position:0% summer state we go to the next state 00:03:46.269 --> 00:03:48.479 align:start position:0% summer state we go to the next state when<00:03:46.810> the<00:03:46.900> 56<00:03:47.349> points<00:03:47.650> and<00:03:47.829> we<00:03:48.010> can<00:03:48.190> have<00:03:48.340> the 00:03:48.479 --> 00:03:48.489 align:start position:0% when the 56 points and we can have the 00:03:48.489 --> 00:03:51.420 align:start position:0% when the 56 points and we can have the proof<00:03:48.760> that<00:03:49.260> proof<00:03:50.260> that's<00:03:50.590> one<00:03:50.949> and<00:03:51.280> this 00:03:51.420 --> 00:03:51.430 align:start position:0% proof that proof that's one and this 00:03:51.430 --> 00:03:53.759 align:start position:0% proof that proof that's one and this proof<00:03:51.760> it<00:03:52.180> can<00:03:52.419> take<00:03:52.629> long<00:03:52.930> in<00:03:53.260> to<00:03:53.440> generate 00:03:53.759 --> 00:03:53.769 align:start position:0% proof it can take long in to generate 00:03:53.769 --> 00:03:56.909 align:start position:0% proof it can take long in to generate but<00:03:54.250> in<00:03:54.400> order<00:03:54.730> to<00:03:54.940> verify<00:03:55.209> its<00:03:55.989> time<00:03:56.379> constant 00:03:56.909 --> 00:03:56.919 align:start position:0% but in order to verify its time constant 00:03:56.919 --> 00:03:59.759 align:start position:0% but in order to verify its time constant in<00:03:57.129> 10<00:03:57.639> milliseconds<00:03:58.269> don't<00:03:58.660> matter<00:03:58.930> how<00:03:59.500> many 00:03:59.759 --> 00:03:59.769 align:start position:0% in 10 milliseconds don't matter how many 00:03:59.769 --> 00:04:02.069 align:start position:0% in 10 milliseconds don't matter how many transactions<00:04:00.549> we<00:04:00.669> are<00:04:00.790> processing<00:04:00.970> in<00:04:01.810> 10 00:04:02.069 --> 00:04:02.079 align:start position:0% transactions we are processing in 10 00:04:02.079 --> 00:04:04.349 align:start position:0% transactions we are processing in 10 innings<00:04:02.470> or<00:04:02.799> in<00:04:02.919> 10<00:04:03.129> milliseconds<00:04:03.730> we<00:04:04.120> can 00:04:04.349 --> 00:04:04.359 align:start position:0% innings or in 10 milliseconds we can 00:04:04.359 --> 00:04:10.199 align:start position:0% innings or in 10 milliseconds we can verify<00:04:05.260> that<00:04:07.349> that<00:04:08.349> proof<00:04:08.620> and<00:04:09.160> that's<00:04:09.639> the 00:04:10.199 --> 00:04:10.209 align:start position:0% verify that that proof and that's the 00:04:10.209 --> 00:04:12.839 align:start position:0% verify that that proof and that's the key<00:04:10.720> part<00:04:10.989> of<00:04:11.260> all<00:04:11.859> those<00:04:12.069> it 00:04:12.839 --> 00:04:12.849 align:start position:0% key part of all those it 00:04:12.849 --> 00:04:18.779 align:start position:0% key part of all those it the<00:04:13.060> roll-up<00:04:13.389> stuff<00:04:13.989> ok<00:04:14.829> here<00:04:15.519> we<00:04:16.890> the<00:04:17.890> system 00:04:18.779 --> 00:04:18.789 align:start position:0% the roll-up stuff ok here we the system 00:04:18.789 --> 00:04:20.629 align:start position:0% the roll-up stuff ok here we the system is<00:04:18.940> like<00:04:19.120> perfect<00:04:19.659> but<00:04:19.810> there<00:04:20.200> is 00:04:20.629 --> 00:04:20.639 align:start position:0% is like perfect but there is 00:04:20.639 --> 00:04:22.760 align:start position:0% is like perfect but there is an<00:04:20.879> important<00:04:21.419> problem<00:04:21.599> that<00:04:22.319> needs<00:04:22.590> to<00:04:22.680> be 00:04:22.760 --> 00:04:22.770 align:start position:0% an important problem that needs to be 00:04:22.770 --> 00:04:25.490 align:start position:0% an important problem that needs to be solved<00:04:23.280> here<00:04:23.580> and<00:04:23.759> it's<00:04:24.539> what<00:04:24.810> happened<00:04:25.379> if 00:04:25.490 --> 00:04:25.500 align:start position:0% solved here and it's what happened if 00:04:25.500 --> 00:04:27.800 align:start position:0% solved here and it's what happened if this<00:04:25.710> operator<00:04:26.159> can<00:04:26.699> be<00:04:26.729> decentralized<00:04:27.300> that 00:04:27.800 --> 00:04:27.810 align:start position:0% this operator can be decentralized that 00:04:27.810 --> 00:04:30.200 align:start position:0% this operator can be decentralized that then<00:04:27.990> we<00:04:28.110> receive<00:04:28.439> home<00:04:28.590> or<00:04:28.860> it's<00:04:28.979> but<00:04:29.580> what 00:04:30.200 --> 00:04:30.210 align:start position:0% then we receive home or it's but what 00:04:30.210 --> 00:04:33.800 align:start position:0% then we receive home or it's but what happen<00:04:30.509> if<00:04:30.629> this<00:04:30.750> operator<00:04:31.460> just<00:04:32.689> compute<00:04:33.689> a 00:04:33.800 --> 00:04:33.810 align:start position:0% happen if this operator just compute a 00:04:33.810 --> 00:04:35.450 align:start position:0% happen if this operator just compute a new<00:04:33.930> estate<00:04:34.289> that's<00:04:34.530> actually<00:04:34.979> upon<00:04:35.250> the 00:04:35.450 --> 00:04:35.460 align:start position:0% new estate that's actually upon the 00:04:35.460 --> 00:04:37.490 align:start position:0% new estate that's actually upon the state<00:04:35.669> with<00:04:35.879> some<00:04:36.060> my<00:04:36.180> transactions<00:04:36.900> but<00:04:37.319> what 00:04:37.490 --> 00:04:37.500 align:start position:0% state with some my transactions but what 00:04:37.500 --> 00:04:39.709 align:start position:0% state with some my transactions but what happened<00:04:38.009> if<00:04:38.129> these<00:04:38.310> transactions<00:04:38.969> are<00:04:39.150> not<00:04:39.689> a 00:04:39.709 --> 00:04:39.719 align:start position:0% happened if these transactions are not a 00:04:39.719 --> 00:04:42.020 align:start position:0% happened if these transactions are not a viable<00:04:40.129> nobody<00:04:41.129> knows<00:04:41.340> what<00:04:41.729> are<00:04:41.849> those 00:04:42.020 --> 00:04:42.030 align:start position:0% viable nobody knows what are those 00:04:42.030 --> 00:04:43.969 align:start position:0% viable nobody knows what are those transactions<00:04:42.689> this<00:04:43.199> is<00:04:43.349> what's<00:04:43.560> called<00:04:43.830> the 00:04:43.969 --> 00:04:43.979 align:start position:0% transactions this is what's called the 00:04:43.979 --> 00:04:45.709 align:start position:0% transactions this is what's called the data<00:04:44.129> reliability<00:04:44.400> problem<00:04:45.150> that<00:04:45.300> I'm<00:04:45.449> sure 00:04:45.709 --> 00:04:45.719 align:start position:0% data reliability problem that I'm sure 00:04:45.719 --> 00:04:47.809 align:start position:0% data reliability problem that I'm sure many<00:04:45.960> of<00:04:46.139> you<00:04:46.259> have<00:04:46.289> been<00:04:46.560> hearing<00:04:46.919> so<00:04:47.610> the 00:04:47.809 --> 00:04:47.819 align:start position:0% many of you have been hearing so the 00:04:47.819 --> 00:04:49.850 align:start position:0% many of you have been hearing so the idea<00:04:48.000> is<00:04:48.180> that<00:04:48.360> we<00:04:48.750> need<00:04:48.780> to<00:04:48.960> warranty<00:04:49.530> that 00:04:49.850 --> 00:04:49.860 align:start position:0% idea is that we need to warranty that 00:04:49.860 --> 00:04:53.059 align:start position:0% idea is that we need to warranty that this<00:04:50.099> data<00:04:50.310> is<00:04:50.550> available<00:04:50.900> in<00:04:51.900> this<00:04:52.409> case<00:04:52.710> is 00:04:53.059 --> 00:04:53.069 align:start position:0% this data is available in this case is 00:04:53.069 --> 00:04:55.730 align:start position:0% this data is available in this case is implementation<00:04:53.580> first<00:04:54.150> is<00:04:54.300> data<00:04:54.509> can<00:04:54.750> be<00:04:54.780> put 00:04:55.730 --> 00:04:55.740 align:start position:0% implementation first is data can be put 00:04:55.740 --> 00:04:58.459 align:start position:0% implementation first is data can be put in<00:04:55.949> in<00:04:56.340> many<00:04:56.550> places<00:04:56.879> but<00:04:57.539> ABC<00:04:57.780> presentation 00:04:58.459 --> 00:04:58.469 align:start position:0% in in many places but ABC presentation 00:04:58.469 --> 00:05:01.279 align:start position:0% in in many places but ABC presentation what<00:04:58.650> it<00:04:58.800> does<00:04:58.979> is<00:04:59.250> put<00:05:00.120> the<00:05:00.360> minimal<00:05:00.780> data<00:05:01.050> of 00:05:01.279 --> 00:05:01.289 align:start position:0% what it does is put the minimal data of 00:05:01.289 --> 00:05:03.320 align:start position:0% what it does is put the minimal data of this<00:05:01.409> information<00:05:01.710> the<00:05:02.370> from<00:05:02.699> -<00:05:03.030> and<00:05:03.240> the 00:05:03.320 --> 00:05:03.330 align:start position:0% this information the from - and the 00:05:03.330 --> 00:05:05.899 align:start position:0% this information the from - and the amount<00:05:03.539> let's<00:05:04.139> say<00:05:04.259> we<00:05:04.919> put<00:05:05.099> it<00:05:05.190> that<00:05:05.340> in<00:05:05.610> the 00:05:05.899 --> 00:05:05.909 align:start position:0% amount let's say we put it that in the 00:05:05.909 --> 00:05:08.990 align:start position:0% amount let's say we put it that in the same<00:05:06.150> chain<00:05:06.539> so<00:05:07.500> we<00:05:07.530> put<00:05:07.800> it<00:05:07.889> in<00:05:07.979> the<00:05:08.099> data<00:05:08.340> the 00:05:08.990 --> 00:05:09.000 align:start position:0% same chain so we put it in the data the 00:05:09.000 --> 00:05:10.879 align:start position:0% same chain so we put it in the data the data<00:05:09.030> field<00:05:09.569> of<00:05:09.780> a<00:05:09.870> transaction<00:05:10.199> we<00:05:10.800> are 00:05:10.879 --> 00:05:10.889 align:start position:0% data field of a transaction we are 00:05:10.889 --> 00:05:12.709 align:start position:0% data field of a transaction we are putting<00:05:11.099> a<00:05:11.250> set<00:05:11.520> of<00:05:11.729> all<00:05:12.060> the<00:05:12.150> transactions 00:05:12.709 --> 00:05:12.719 align:start position:0% putting a set of all the transactions 00:05:12.719 --> 00:05:14.570 align:start position:0% putting a set of all the transactions that<00:05:12.779> are<00:05:12.900> putting<00:05:13.110> there<00:05:13.830> that's<00:05:14.250> a<00:05:14.400> lot<00:05:14.550> of 00:05:14.570 --> 00:05:14.580 align:start position:0% that are putting there that's a lot of 00:05:14.580 --> 00:05:16.760 align:start position:0% that are putting there that's a lot of data<00:05:14.909> there<00:05:15.180> but<00:05:15.719> that's<00:05:15.900> when<00:05:16.229> we<00:05:16.500> will<00:05:16.650> see 00:05:16.760 --> 00:05:16.770 align:start position:0% data there but that's when we will see 00:05:16.770 --> 00:05:18.200 align:start position:0% data there but that's when we will see the<00:05:16.889> calculus<00:05:17.250> and<00:05:17.279> we<00:05:17.460> will<00:05:17.669> see<00:05:17.849> that<00:05:17.879> that's 00:05:18.200 --> 00:05:18.210 align:start position:0% the calculus and we will see that that's 00:05:18.210 --> 00:05:21.290 align:start position:0% the calculus and we will see that that's not<00:05:18.389> that<00:05:18.449> much<00:05:19.159> okay<00:05:20.159> so<00:05:20.219> that's<00:05:20.490> amazing 00:05:21.290 --> 00:05:21.300 align:start position:0% not that much okay so that's amazing 00:05:21.300 --> 00:05:23.149 align:start position:0% not that much okay so that's amazing of<00:05:21.689> course<00:05:21.990> we<00:05:22.169> are<00:05:22.199> trying<00:05:22.500> to<00:05:22.650> compress<00:05:22.979> a 00:05:23.149 --> 00:05:23.159 align:start position:0% of course we are trying to compress a 00:05:23.159 --> 00:05:26.330 align:start position:0% of course we are trying to compress a lot<00:05:23.340> is<00:05:23.789> this<00:05:24.330> this<00:05:24.629> data<00:05:24.840> in<00:05:25.319> order<00:05:25.620> to<00:05:25.800> have 00:05:26.330 --> 00:05:26.340 align:start position:0% lot is this this data in order to have 00:05:26.340 --> 00:05:32.059 align:start position:0% lot is this this data in order to have more<00:05:26.879> transactions<00:05:29.180> okay<00:05:30.180> so<00:05:30.860> let's<00:05:31.860> go<00:05:32.039> a 00:05:32.059 --> 00:05:32.069 align:start position:0% more transactions okay so let's go a 00:05:32.069 --> 00:05:35.050 align:start position:0% more transactions okay so let's go a little<00:05:32.279> bit<00:05:32.550> in<00:05:32.909> the<00:05:33.090> pail<00:05:33.389> of<00:05:33.719> all<00:05:34.379> these 00:05:35.050 --> 00:05:35.060 align:start position:0% little bit in the pail of all these 00:05:35.060 --> 00:05:36.860 align:start position:0% little bit in the pail of all these silly<00:05:36.060> worries 00:05:36.860 --> 00:05:36.870 align:start position:0% silly worries 00:05:36.870 --> 00:05:38.839 align:start position:0% silly worries but<00:05:37.229> I<00:05:37.259> mean<00:05:37.500> secretly<00:05:38.009> who<00:05:38.339> we<00:05:38.520> should<00:05:38.550> write 00:05:38.839 --> 00:05:38.849 align:start position:0% but I mean secretly who we should write 00:05:38.849 --> 00:05:41.420 align:start position:0% but I mean secretly who we should write this<00:05:39.000> proof<00:05:39.300> is<00:05:40.080> proof<00:05:40.319> self<00:05:40.889> it<00:05:41.069> mainly<00:05:41.250> is 00:05:41.420 --> 00:05:41.430 align:start position:0% this proof is proof self it mainly is 00:05:41.430 --> 00:05:43.219 align:start position:0% this proof is proof self it mainly is when<00:05:41.759> he<00:05:41.849> sees<00:05:42.029> a<00:05:42.210> deterministic<00:05:42.839> program 00:05:43.219 --> 00:05:43.229 align:start position:0% when he sees a deterministic program 00:05:43.229 --> 00:05:46.909 align:start position:0% when he sees a deterministic program it's<00:05:43.589> a<00:05:43.680> program<00:05:43.710> that<00:05:44.779> put<00:05:45.779> an<00:05:45.900> input<00:05:46.080> without 00:05:46.909 --> 00:05:46.919 align:start position:0% it's a program that put an input without 00:05:46.919 --> 00:05:49.309 align:start position:0% it's a program that put an input without the<00:05:47.039> computation<00:05:47.699> it<00:05:48.389> has<00:05:48.569> an<00:05:48.719> output<00:05:48.870> in<00:05:49.199> this 00:05:49.309 --> 00:05:49.319 align:start position:0% the computation it has an output in this 00:05:49.319 --> 00:05:51.740 align:start position:0% the computation it has an output in this case<00:05:49.560> is<00:05:49.770> the<00:05:49.889> new<00:05:50.009> rule<00:05:50.219> and<00:05:50.400> we<00:05:51.300> prove<00:05:51.569> that 00:05:51.740 --> 00:05:51.750 align:start position:0% case is the new rule and we prove that 00:05:51.750 --> 00:05:55.129 align:start position:0% case is the new rule and we prove that actually<00:05:52.339> 10<00:05:53.339> good<00:05:53.580> matches<00:05:54.120> their<00:05:54.330> matches 00:05:55.129 --> 00:05:55.139 align:start position:0% actually 10 good matches their matches 00:05:55.139 --> 00:05:57.980 align:start position:0% actually 10 good matches their matches the<00:05:55.620> output<00:05:55.979> okay<00:05:56.339> so<00:05:56.400> this<00:05:56.610> is<00:05:56.759> it<00:05:57.150> does<00:05:57.839> it 00:05:57.980 --> 00:05:57.990 align:start position:0% the output okay so this is it does it 00:05:57.990 --> 00:06:00.850 align:start position:0% the output okay so this is it does it prove<00:05:58.620> a<00:05:58.800> zero<00:05:59.009> much<00:05:59.250> maybe<00:05:59.789> the<00:06:00.000> secret<00:06:00.240> has<00:06:00.779> a 00:06:00.850 --> 00:06:00.860 align:start position:0% prove a zero much maybe the secret has a 00:06:00.860 --> 00:06:03.370 align:start position:0% prove a zero much maybe the secret has a novice<00:06:01.860> and<00:06:02.039> all<00:06:02.190> pro<00:06:02.370> of<00:06:02.550> transaction 00:06:03.370 --> 00:06:03.380 align:start position:0% novice and all pro of transaction 00:06:03.380 --> 00:06:06.160 align:start position:0% novice and all pro of transaction so<00:06:03.890> we<00:06:03.980> cover<00:06:04.130> the<00:06:04.760> route<00:06:05.120> processing<00:06:05.900> section 00:06:06.160 --> 00:06:06.170 align:start position:0% so we cover the route processing section 00:06:06.170 --> 00:06:08.530 align:start position:0% so we cover the route processing section we<00:06:06.440> have<00:06:06.530> you<00:06:06.770> any<00:06:07.010> new<00:06:07.460> route<00:06:07.700> rasul'allah 00:06:08.530 --> 00:06:08.540 align:start position:0% we have you any new route rasul'allah 00:06:08.540 --> 00:06:10.480 align:start position:0% we have you any new route rasul'allah conundrum<00:06:09.050> have<00:06:09.170> a<00:06:09.260> new<00:06:09.350> route<00:06:09.530> and<00:06:09.650> maybe<00:06:10.160> I 00:06:10.480 --> 00:06:10.490 align:start position:0% conundrum have a new route and maybe I 00:06:10.490 --> 00:06:12.310 align:start position:0% conundrum have a new route and maybe I don't<00:06:10.700> know<00:06:10.820> two<00:06:11.000> thousand<00:06:11.330> transactions<00:06:11.900> and 00:06:12.310 --> 00:06:12.320 align:start position:0% don't know two thousand transactions and 00:06:12.320 --> 00:06:14.650 align:start position:0% don't know two thousand transactions and then<00:06:12.440> we<00:06:12.590> can<00:06:12.710> have<00:06:13.160> the<00:06:13.670> new<00:06:13.790> anymore 00:06:14.650 --> 00:06:14.660 align:start position:0% then we can have the new anymore 00:06:14.660 --> 00:06:17.350 align:start position:0% then we can have the new anymore okay<00:06:15.080> so<00:06:15.440> let's<00:06:15.680> swimming<00:06:16.070> in<00:06:16.670> one<00:06:16.970> of<00:06:17.210> those 00:06:17.350 --> 00:06:17.360 align:start position:0% okay so let's swimming in one of those 00:06:17.360 --> 00:06:19.240 align:start position:0% okay so let's swimming in one of those transactions<00:06:18.200> processors<00:06:18.650> what<00:06:18.830> we<00:06:18.980> have 00:06:19.240 --> 00:06:19.250 align:start position:0% transactions processors what we have 00:06:19.250 --> 00:06:22.930 align:start position:0% transactions processors what we have here<00:06:19.640> so<00:06:20.200> here<00:06:21.200> in<00:06:21.380> to<00:06:21.470> my<00:06:21.620> name<00:06:22.130> pieces<00:06:22.400> of 00:06:22.930 --> 00:06:22.940 align:start position:0% here so here in to my name pieces of 00:06:22.940 --> 00:06:25.810 align:start position:0% here so here in to my name pieces of these<00:06:23.300> of<00:06:24.230> these<00:06:24.440> silly<00:06:24.860> first<00:06:25.430> we<00:06:25.580> have<00:06:25.790> a 00:06:25.810 --> 00:06:25.820 align:start position:0% these of these silly first we have a 00:06:25.820 --> 00:06:27.370 align:start position:0% these of these silly first we have a signature<00:06:26.240> verification<00:06:26.450> this<00:06:27.080> is<00:06:27.200> very 00:06:27.370 --> 00:06:27.380 align:start position:0% signature verification this is very 00:06:27.380 --> 00:06:30.280 align:start position:0% signature verification this is very important<00:06:27.860> because<00:06:28.540> by<00:06:29.540> design<00:06:29.780> of<00:06:29.990> this 00:06:30.280 --> 00:06:30.290 align:start position:0% important because by design of this 00:06:30.290 --> 00:06:33.010 align:start position:0% important because by design of this simply<00:06:30.710> we<00:06:31.250> don't<00:06:31.400> need<00:06:31.610> to<00:06:32.060> store<00:06:32.450> the 00:06:33.010 --> 00:06:33.020 align:start position:0% simply we don't need to store the 00:06:33.020 --> 00:06:35.020 align:start position:0% simply we don't need to store the signature<00:06:33.590> on<00:06:33.920> change<00:06:34.220> the<00:06:34.430> signature<00:06:34.790> is<00:06:34.910> a 00:06:35.020 --> 00:06:35.030 align:start position:0% signature on change the signature is a 00:06:35.030 --> 00:06:37.420 align:start position:0% signature on change the signature is a very<00:06:35.300> big<00:06:35.540> piece<00:06:35.720> of<00:06:35.960> data<00:06:36.140> then<00:06:36.890> we<00:06:37.190> need<00:06:37.310> to 00:06:37.420 --> 00:06:37.430 align:start position:0% very big piece of data then we need to 00:06:37.430 --> 00:06:40.150 align:start position:0% very big piece of data then we need to put<00:06:37.550> plan<00:06:37.850> verifying<00:06:38.630> that<00:06:38.780> is<00:06:39.290> the<00:06:39.830> signature 00:06:40.150 --> 00:06:40.160 align:start position:0% put plan verifying that is the signature 00:06:40.160 --> 00:06:42.430 align:start position:0% put plan verifying that is the signature can<00:06:40.520> be<00:06:40.550> of<00:06:40.850> chain<00:06:41.120> the<00:06:41.690> transactions<00:06:42.230> can<00:06:42.380> be 00:06:42.430 --> 00:06:42.440 align:start position:0% can be of chain the transactions can be 00:06:42.440 --> 00:06:45.160 align:start position:0% can be of chain the transactions can be included<00:06:42.800> but<00:06:43.130> by<00:06:43.700> design<00:06:43.910> they<00:06:44.600> will<00:06:44.840> not<00:06:45.020> be 00:06:45.160 --> 00:06:45.170 align:start position:0% included but by design they will not be 00:06:45.170 --> 00:06:47.140 align:start position:0% included but by design they will not be valid<00:06:45.410> if<00:06:45.710> there<00:06:46.370> is<00:06:46.490> no<00:06:46.670> it's<00:06:46.850> not<00:06:47.000> a 00:06:47.140 --> 00:06:47.150 align:start position:0% valid if there is no it's not a 00:06:47.150 --> 00:06:49.480 align:start position:0% valid if there is no it's not a signature<00:06:47.540> that<00:06:47.840> if<00:06:48.650> does<00:06:48.890> not<00:06:48.920> exist<00:06:49.370> in<00:06:49.430> a 00:06:49.480 --> 00:06:49.490 align:start position:0% signature that if does not exist in a 00:06:49.490 --> 00:06:50.620 align:start position:0% signature that if does not exist in a single<00:06:49.670> tube<00:06:49.880> that's<00:06:50.000> valid<00:06:50.360> for<00:06:50.540> that 00:06:50.620 --> 00:06:50.630 align:start position:0% single tube that's valid for that 00:06:50.630 --> 00:06:52.870 align:start position:0% single tube that's valid for that transaction<00:06:51.100> but<00:06:52.100> if<00:06:52.220> it's<00:06:52.370> finally<00:06:52.700> it 00:06:52.870 --> 00:06:52.880 align:start position:0% transaction but if it's finally it 00:06:52.880 --> 00:06:54.760 align:start position:0% transaction but if it's finally it happens<00:06:53.300> and<00:06:53.510> if<00:06:53.600> it<00:06:53.930> is<00:06:54.140> so<00:06:54.290> we<00:06:54.470> don't<00:06:54.620> need<00:06:54.710> to 00:06:54.760 --> 00:06:54.770 align:start position:0% happens and if it is so we don't need to 00:06:54.770 --> 00:06:56.890 align:start position:0% happens and if it is so we don't need to store<00:06:55.160> this<00:06:55.580> another<00:06:55.970> so<00:06:56.090> this<00:06:56.240> is<00:06:56.360> important 00:06:56.890 --> 00:06:56.900 align:start position:0% store this another so this is important 00:06:56.900 --> 00:07:01.480 align:start position:0% store this another so this is important okay<00:06:57.430> then<00:06:58.430> we<00:06:58.640> have<00:06:59.890> of<00:07:00.890> course<00:07:00.950> we<00:07:01.190> need<00:07:01.370> to 00:07:01.480 --> 00:07:01.490 align:start position:0% okay then we have of course we need to 00:07:01.490 --> 00:07:04.270 align:start position:0% okay then we have of course we need to modify<00:07:01.760> the<00:07:01.940> state<00:07:02.330> of<00:07:02.600> the<00:07:02.780> center<00:07:03.680> of<00:07:03.890> the 00:07:04.270 --> 00:07:04.280 align:start position:0% modify the state of the center of the 00:07:04.280 --> 00:07:06.670 align:start position:0% modify the state of the center of the state<00:07:04.640> of<00:07:04.820> the<00:07:04.850> receiver<00:07:05.420> of<00:07:05.660> the<00:07:06.320> receiver 00:07:06.670 --> 00:07:06.680 align:start position:0% state of the receiver of the receiver 00:07:06.680 --> 00:07:11.650 align:start position:0% state of the receiver of the receiver and<00:07:07.990> so<00:07:08.990> we<00:07:09.110> have<00:07:10.040> this<00:07:10.220> process<00:07:10.520> of<00:07:10.850> vertical 00:07:11.650 --> 00:07:11.660 align:start position:0% and so we have this process of vertical 00:07:11.660 --> 00:07:13.690 align:start position:0% and so we have this process of vertical tree<00:07:11.870> process<00:07:12.590> sources<00:07:12.950> that<00:07:13.250> we<00:07:13.430> are<00:07:13.490> mainly 00:07:13.690 --> 00:07:13.700 align:start position:0% tree process sources that we are mainly 00:07:13.700 --> 00:07:16.270 align:start position:0% tree process sources that we are mainly what<00:07:13.940> we<00:07:14.210> are<00:07:14.300> just<00:07:14.990> updating<00:07:15.830> this<00:07:15.980> miracle 00:07:16.270 --> 00:07:16.280 align:start position:0% what we are just updating this miracle 00:07:16.280 --> 00:07:18.310 align:start position:0% what we are just updating this miracle tree<00:07:16.610> with<00:07:17.060> different<00:07:17.390> states<00:07:17.660> we<00:07:18.080> need<00:07:18.230> to 00:07:18.310 --> 00:07:18.320 align:start position:0% tree with different states we need to 00:07:18.320 --> 00:07:19.690 align:start position:0% tree with different states we need to have<00:07:18.470> two<00:07:18.650> of<00:07:18.770> them<00:07:18.890> from<00:07:19.100> the<00:07:19.280> center<00:07:19.580> of 00:07:19.690 --> 00:07:19.700 align:start position:0% have two of them from the center of 00:07:19.700 --> 00:07:21.640 align:start position:0% have two of them from the center of rotary<00:07:20.030> silver<00:07:20.480> saber<00:07:20.690> and<00:07:20.990> of<00:07:21.320> course<00:07:21.530> we 00:07:21.640 --> 00:07:21.650 align:start position:0% rotary silver saber and of course we 00:07:21.650 --> 00:07:23.290 align:start position:0% rotary silver saber and of course we have<00:07:21.830> all<00:07:22.040> the<00:07:22.220> logic<00:07:22.730> of<00:07:22.820> the<00:07:22.940> transaction 00:07:23.290 --> 00:07:23.300 align:start position:0% have all the logic of the transaction 00:07:23.300 --> 00:07:25.450 align:start position:0% have all the logic of the transaction processing<00:07:23.990> hearings<00:07:24.350> we<00:07:24.830> were<00:07:24.950> a<00:07:24.980> teen<00:07:25.280> and 00:07:25.450 --> 00:07:25.460 align:start position:0% processing hearings we were a teen and 00:07:25.460 --> 00:07:27.340 align:start position:0% processing hearings we were a teen and there<00:07:25.580> is<00:07:25.670> no<00:07:25.820> global<00:07:25.970> spans<00:07:26.420> that<00:07:27.050> we<00:07:27.200> have 00:07:27.340 --> 00:07:27.350 align:start position:0% there is no global spans that we have 00:07:27.350 --> 00:07:29.740 align:start position:0% there is no global spans that we have enough<00:07:27.590> money<00:07:27.830> into<00:07:28.130> sand<00:07:28.460> and<00:07:28.790> all<00:07:29.450> that 00:07:29.740 --> 00:07:29.750 align:start position:0% enough money into sand and all that 00:07:29.750 --> 00:07:33.910 align:start position:0% enough money into sand and all that logic<00:07:31.330> so<00:07:32.330> that's<00:07:32.510> made<00:07:32.870> pretty<00:07:33.140> much<00:07:33.320> the 00:07:33.910 --> 00:07:33.920 align:start position:0% logic so that's made pretty much the 00:07:33.920 --> 00:07:35.860 align:start position:0% logic so that's made pretty much the picture<00:07:34.370> of<00:07:34.880> the<00:07:35.030> same<00:07:35.210> thing<00:07:35.390> you<00:07:35.690> see<00:07:35.840> here 00:07:35.860 --> 00:07:35.870 align:start position:0% picture of the same thing you see here 00:07:35.870 --> 00:07:37.510 align:start position:0% picture of the same thing you see here it's<00:07:36.200> important<00:07:36.620> to<00:07:36.710> see<00:07:36.860> that<00:07:36.890> input<00:07:37.160> that 00:07:37.510 --> 00:07:37.520 align:start position:0% it's important to see that input that 00:07:37.520 --> 00:07:39.190 align:start position:0% it's important to see that input that there<00:07:37.730> are<00:07:37.880> of<00:07:38.210> course<00:07:38.270> there<00:07:38.570> is<00:07:38.690> public<00:07:38.960> it 00:07:39.190 --> 00:07:39.200 align:start position:0% there are of course there is public it 00:07:39.200 --> 00:07:45.220 align:start position:0% there are of course there is public it was<00:07:39.350> like<00:07:39.620> the<00:07:39.800> output<00:07:40.960> 3<00:07:41.960> some<00:07:43.720> parts<00:07:44.720> of<00:07:44.870> fan 00:07:45.220 --> 00:07:45.230 align:start position:0% was like the output 3 some parts of fan 00:07:45.230 --> 00:07:46.900 align:start position:0% was like the output 3 some parts of fan that<00:07:45.410> are<00:07:45.500> also<00:07:45.680> public<00:07:46.100> is<00:07:46.250> affirmed<00:07:46.550> to<00:07:46.790> an 00:07:46.900 --> 00:07:46.910 align:start position:0% that are also public is affirmed to an 00:07:46.910 --> 00:07:48.850 align:start position:0% that are also public is affirmed to an amount<00:07:47.150> as<00:07:47.390> a<00:07:47.420> minimum<00:07:47.840> part<00:07:48.140> that<00:07:48.530> needs<00:07:48.680> to 00:07:48.850 --> 00:07:48.860 align:start position:0% amount as a minimum part that needs to 00:07:48.860 --> 00:07:52.060 align:start position:0% amount as a minimum part that needs to be<00:07:49.900> available<00:07:50.900> for<00:07:51.440> computing<00:07:51.860> the<00:07:51.950> new 00:07:52.060 --> 00:07:52.070 align:start position:0% be available for computing the new 00:07:52.070 --> 00:07:53.650 align:start position:0% be available for computing the new estate<00:07:52.400> and<00:07:52.610> then<00:07:52.970> there<00:07:53.090> is<00:07:53.210> a<00:07:53.360> lot<00:07:53.630> of 00:07:53.650 --> 00:07:53.660 align:start position:0% estate and then there is a lot of 00:07:53.660 --> 00:07:55.350 align:start position:0% estate and then there is a lot of private<00:07:54.650> simple 00:07:55.350 --> 00:07:55.360 align:start position:0% private simple 00:07:55.360 --> 00:07:57.149 align:start position:0% private simple the<00:07:55.509> current<00:07:55.810> state<00:07:56.080> that<00:07:56.289> the<00:07:56.680> only<00:07:56.800> needs<00:07:57.009> to 00:07:57.149 --> 00:07:57.159 align:start position:0% the current state that the only needs to 00:07:57.159 --> 00:08:01.309 align:start position:0% the current state that the only needs to be<00:07:57.280> is<00:07:57.550> very<00:07:57.819> to<00:07:58.180> be<00:07:58.270> verified<00:07:58.689> with<00:07:58.840> the<00:07:59.050> rope 00:08:01.309 --> 00:08:01.319 align:start position:0% 00:08:01.319 --> 00:08:04.550 align:start position:0% so<00:08:02.319> let's<00:08:02.530> see<00:08:02.680> who<00:08:02.979> is<00:08:03.370> rollout<00:08:04.000> move<00:08:04.030> boy 00:08:04.550 --> 00:08:04.560 align:start position:0% so let's see who is rollout move boy 00:08:04.560 --> 00:08:07.140 align:start position:0% so let's see who is rollout move boy what<00:08:05.560> kind<00:08:05.800> of<00:08:05.949> transactions<00:08:06.580> imagine<00:08:07.000> that 00:08:07.140 --> 00:08:07.150 align:start position:0% what kind of transactions imagine that 00:08:07.150 --> 00:08:08.879 align:start position:0% what kind of transactions imagine that we<00:08:07.270> are<00:08:07.389> start<00:08:07.629> on<00:08:07.810> new<00:08:07.900> Rolla<00:08:08.139> we<00:08:08.409> have<00:08:08.590> a<00:08:08.620> man 00:08:08.879 --> 00:08:08.889 align:start position:0% we are start on new Rolla we have a man 00:08:08.889 --> 00:08:09.390 align:start position:0% we are start on new Rolla we have a man deal 00:08:09.390 --> 00:08:09.400 align:start position:0% deal 00:08:09.400 --> 00:08:11.879 align:start position:0% deal we<00:08:09.610> have<00:08:09.759> an<00:08:09.909> empty<00:08:10.150> moment<00:08:10.539> the<00:08:11.409> first<00:08:11.590> thing 00:08:11.879 --> 00:08:11.889 align:start position:0% we have an empty moment the first thing 00:08:11.889 --> 00:08:14.279 align:start position:0% we have an empty moment the first thing that<00:08:11.919> we<00:08:12.189> can<00:08:12.219> do<00:08:12.580> is<00:08:12.729> no<00:08:12.879> deposits<00:08:13.449> so<00:08:14.050> mainly 00:08:14.279 --> 00:08:14.289 align:start position:0% that we can do is no deposits so mainly 00:08:14.289 --> 00:08:16.619 align:start position:0% that we can do is no deposits so mainly how<00:08:14.650> it<00:08:14.830> will<00:08:15.009> work<00:08:15.039> you<00:08:15.699> will<00:08:15.909> send<00:08:16.210> you<00:08:16.479> will 00:08:16.619 --> 00:08:16.629 align:start position:0% how it will work you will send you will 00:08:16.629 --> 00:08:19.050 align:start position:0% how it will work you will send you will take<00:08:16.780> a<00:08:16.810> token<00:08:17.259> system<00:08:18.009> words<00:08:18.219> in<00:08:18.400> many<00:08:18.699> in<00:08:18.909> any 00:08:19.050 --> 00:08:19.060 align:start position:0% take a token system words in many in any 00:08:19.060 --> 00:08:20.909 align:start position:0% take a token system words in many in any token<00:08:19.449> so<00:08:19.659> can<00:08:19.870> this<00:08:19.960> multi<00:08:20.289> popping<00:08:20.560> system 00:08:20.909 --> 00:08:20.919 align:start position:0% token so can this multi popping system 00:08:20.919 --> 00:08:22.800 align:start position:0% token so can this multi popping system so<00:08:21.340> you<00:08:21.430> can<00:08:21.460> even<00:08:21.789> send<00:08:22.060> the<00:08:22.150> tokens<00:08:22.509> if 00:08:22.800 --> 00:08:22.810 align:start position:0% so you can even send the tokens if 00:08:22.810 --> 00:08:25.219 align:start position:0% so you can even send the tokens if either<00:08:23.110> or<00:08:23.319> whatever<00:08:23.830> to<00:08:24.340> a<00:08:24.400> smart<00:08:24.669> contract 00:08:25.219 --> 00:08:25.229 align:start position:0% either or whatever to a smart contract 00:08:25.229 --> 00:08:27.809 align:start position:0% either or whatever to a smart contract the<00:08:26.229> Ola<00:08:26.889> will<00:08:27.250> create<00:08:27.490> the<00:08:27.610> special 00:08:27.809 --> 00:08:27.819 align:start position:0% the Ola will create the special 00:08:27.819 --> 00:08:29.969 align:start position:0% the Ola will create the special transaction<00:08:28.539> that's<00:08:28.870> a<00:08:29.020> deposit<00:08:29.500> or<00:08:29.620> not<00:08:29.770> that 00:08:29.969 --> 00:08:29.979 align:start position:0% transaction that's a deposit or not that 00:08:29.979 --> 00:08:32.120 align:start position:0% transaction that's a deposit or not that mainly<00:08:30.310> what<00:08:30.430> it<00:08:30.580> does<00:08:30.729> is<00:08:31.000> creates<00:08:31.419> a<00:08:31.659> new 00:08:32.120 --> 00:08:32.130 align:start position:0% mainly what it does is creates a new 00:08:32.130 --> 00:08:37.319 align:start position:0% mainly what it does is creates a new leaf<00:08:33.130> in<00:08:33.459> the<00:08:33.760> in<00:08:34.539> the<00:08:34.870> in<00:08:35.229> the<00:08:35.289> state<00:08:35.620> with<00:08:36.490> the 00:08:37.319 --> 00:08:37.329 align:start position:0% leaf in the in the in the state with the 00:08:37.329 --> 00:08:39.480 align:start position:0% leaf in the in the in the state with the initial<00:08:37.779> amount<00:08:38.019> that<00:08:38.589> you<00:08:38.769> are<00:08:38.919> sending<00:08:39.339> out 00:08:39.480 --> 00:08:39.490 align:start position:0% initial amount that you are sending out 00:08:39.490 --> 00:08:43.970 align:start position:0% initial amount that you are sending out here<00:08:39.779> and<00:08:40.779> so<00:08:40.959> you<00:08:41.019> would<00:08:41.380> people<00:08:41.860> would<00:08:42.190> just 00:08:43.970 --> 00:08:43.980 align:start position:0% here and so you would people would just 00:08:43.980 --> 00:08:49.889 align:start position:0% here and so you would people would just move<00:08:44.980> either<00:08:45.910> to<00:08:46.329> the<00:08:46.510> to<00:08:47.230> the<00:08:47.730> to<00:08:48.730> that<00:08:48.910> to<00:08:49.779> the 00:08:49.889 --> 00:08:49.899 align:start position:0% move either to the to the to that to the 00:08:49.899 --> 00:08:53.579 align:start position:0% move either to the to the to that to the side<00:08:50.260> chain<00:08:50.640> okay<00:08:51.640> then<00:08:52.450> we<00:08:52.630> have<00:08:52.660> the<00:08:53.170> normal 00:08:53.579 --> 00:08:53.589 align:start position:0% side chain okay then we have the normal 00:08:53.589 --> 00:08:55.680 align:start position:0% side chain okay then we have the normal of<00:08:53.709> chains<00:08:54.040> and<00:08:54.220> sanctions<00:08:54.700> that<00:08:54.970> are<00:08:55.120> mainly 00:08:55.680 --> 00:08:55.690 align:start position:0% of chains and sanctions that are mainly 00:08:55.690 --> 00:08:58.740 align:start position:0% of chains and sanctions that are mainly just<00:08:56.610> transferring<00:08:57.610> from<00:08:58.060> one<00:08:58.149> account<00:08:58.570> to 00:08:58.740 --> 00:08:58.750 align:start position:0% just transferring from one account to 00:08:58.750 --> 00:09:00.900 align:start position:0% just transferring from one account to the<00:08:58.870> other<00:08:58.959> account<00:08:59.380> or<00:09:00.250> this<00:09:00.550> will<00:09:00.760> be<00:09:00.850> the 00:09:00.900 --> 00:09:00.910 align:start position:0% the other account or this will be the 00:09:00.910 --> 00:09:02.060 align:start position:0% the other account or this will be the same<00:09:01.180> coin 00:09:02.060 --> 00:09:02.070 align:start position:0% same coin 00:09:02.070 --> 00:09:05.490 align:start position:0% same coin now<00:09:03.070> all<00:09:03.279> the<00:09:03.430> hormones<00:09:03.670> here<00:09:04.390> and<00:09:05.170> then<00:09:05.350> we 00:09:05.490 --> 00:09:05.500 align:start position:0% now all the hormones here and then we 00:09:05.500 --> 00:09:07.769 align:start position:0% now all the hormones here and then we have<00:09:05.709> the<00:09:05.920> next<00:09:06.190> election<00:09:06.970> words<00:09:07.329> next<00:09:07.510> it<00:09:07.750> may 00:09:07.769 --> 00:09:07.779 align:start position:0% have the next election words next it may 00:09:07.779 --> 00:09:10.230 align:start position:0% have the next election words next it may mean<00:09:08.079> it<00:09:08.230> is<00:09:08.440> just<00:09:09.040> sending<00:09:09.279> the<00:09:09.399> money<00:09:09.550> to<00:09:09.699> 0<00:09:10.029> X 00:09:10.230 --> 00:09:10.240 align:start position:0% mean it is just sending the money to 0 X 00:09:10.240 --> 00:09:13.350 align:start position:0% mean it is just sending the money to 0 X 2<00:09:10.480> -<00:09:10.870> 0<00:09:10.899> X<00:09:11.230> 0<00:09:11.500> so<00:09:12.040> you<00:09:12.160> send<00:09:12.339> the<00:09:12.430> money<00:09:12.519> to<00:09:12.670> the<00:09:12.790> 0 00:09:13.350 --> 00:09:13.360 align:start position:0% 2 - 0 X 0 so you send the money to the 0 00:09:13.360 --> 00:09:17.160 align:start position:0% 2 - 0 X 0 so you send the money to the 0 address<00:09:13.540> and<00:09:13.990> this<00:09:14.560> wheel<00:09:15.779> maybe<00:09:16.779> one<00:09:17.050> thing 00:09:17.160 --> 00:09:17.170 align:start position:0% address and this wheel maybe one thing 00:09:17.170 --> 00:09:19.230 align:start position:0% address and this wheel maybe one thing will<00:09:17.350> do<00:09:17.440> is<00:09:17.589> this<00:09:18.070> will<00:09:18.130> create<00:09:18.610> like<00:09:18.940> another 00:09:19.230 --> 00:09:19.240 align:start position:0% will do is this will create like another 00:09:19.240 --> 00:09:21.000 align:start position:0% will do is this will create like another tree<00:09:19.570> for<00:09:20.019> each<00:09:20.050> body<00:09:20.350> we<00:09:20.620> have<00:09:20.740> like<00:09:20.980> a 00:09:21.000 --> 00:09:21.010 align:start position:0% tree for each body we have like a 00:09:21.010 --> 00:09:26.639 align:start position:0% tree for each body we have like a separate<00:09:21.399> tree<00:09:21.760> of<00:09:22.260> exits<00:09:25.050> so<00:09:26.050> you<00:09:26.560> are 00:09:26.639 --> 00:09:26.649 align:start position:0% separate tree of exits so you are 00:09:26.649 --> 00:09:28.650 align:start position:0% separate tree of exits so you are sending<00:09:27.070> them<00:09:27.250> to<00:09:27.399> that<00:09:27.550> to<00:09:28.000> that<00:09:28.029> tree<00:09:28.360> so<00:09:28.570> we 00:09:28.650 --> 00:09:28.660 align:start position:0% sending them to that to that tree so we 00:09:28.660 --> 00:09:30.360 align:start position:0% sending them to that to that tree so we are<00:09:28.750> disrupting<00:09:29.019> this<00:09:29.410> tree<00:09:29.649> of<00:09:29.769> exits 00:09:30.360 --> 00:09:30.370 align:start position:0% are disrupting this tree of exits 00:09:30.370 --> 00:09:32.490 align:start position:0% are disrupting this tree of exits so<00:09:30.970> with<00:09:31.180> this<00:09:31.360> from<00:09:31.990> the<00:09:32.110> smart<00:09:32.320> contract 00:09:32.490 --> 00:09:32.500 align:start position:0% so with this from the smart contract 00:09:32.500 --> 00:09:34.710 align:start position:0% so with this from the smart contract sign<00:09:32.949> again<00:09:33.399> in<00:09:33.550> the<00:09:33.640> main<00:09:33.820> chain<00:09:34.089> we<00:09:34.690> can 00:09:34.710 --> 00:09:34.720 align:start position:0% sign again in the main chain we can 00:09:34.720 --> 00:09:37.050 align:start position:0% sign again in the main chain we can withdraw<00:09:35.380> we<00:09:35.860> prove<00:09:36.160> that<00:09:36.430> when<00:09:36.790> you<00:09:36.880> have<00:09:37.029> a 00:09:37.050 --> 00:09:37.060 align:start position:0% withdraw we prove that when you have a 00:09:37.060 --> 00:09:40.920 align:start position:0% withdraw we prove that when you have a leaf<00:09:37.329> in<00:09:37.570> this<00:09:37.750> exit<00:09:38.110> tree<00:09:38.320> we<00:09:39.360> mark<00:09:40.360> it<00:09:40.570> with 00:09:40.920 --> 00:09:40.930 align:start position:0% leaf in this exit tree we mark it with 00:09:40.930 --> 00:09:43.920 align:start position:0% leaf in this exit tree we mark it with raggedness<00:09:41.350> are<00:09:41.760> with<00:09:42.760> Rowan<00:09:43.089> and<00:09:43.480> we<00:09:43.630> get<00:09:43.779> all 00:09:43.920 --> 00:09:43.930 align:start position:0% raggedness are with Rowan and we get all 00:09:43.930 --> 00:09:46.949 align:start position:0% raggedness are with Rowan and we get all done<00:09:44.519> and<00:09:45.519> we<00:09:45.699> get<00:09:45.820> the<00:09:45.940> money<00:09:45.970> back<00:09:46.269> so<00:09:46.510> here 00:09:46.949 --> 00:09:46.959 align:start position:0% done and we get the money back so here 00:09:46.959 --> 00:09:49.290 align:start position:0% done and we get the money back so here we<00:09:47.079> see<00:09:47.290> the<00:09:47.470> full<00:09:47.649> picture<00:09:47.800> for<00:09:48.519> we<00:09:48.670> deposit 00:09:49.290 --> 00:09:49.300 align:start position:0% we see the full picture for we deposit 00:09:49.300 --> 00:09:52.199 align:start position:0% we see the full picture for we deposit we<00:09:49.690> move<00:09:49.930> inside<00:09:50.290> and<00:09:50.829> then<00:09:51.220> we<00:09:51.399> exit<00:09:51.970> the 00:09:52.199 --> 00:09:52.209 align:start position:0% we move inside and then we exit the 00:09:52.209 --> 00:09:55.199 align:start position:0% we move inside and then we exit the stuff<00:09:52.420> of<00:09:52.899> course<00:09:53.079> we<00:09:53.290> can<00:09:53.440> do<00:09:53.880> we<00:09:54.880> can<00:09:55.089> do 00:09:55.199 --> 00:09:55.209 align:start position:0% stuff of course we can do we can do 00:09:55.209 --> 00:09:57.810 align:start position:0% stuff of course we can do we can do other<00:09:55.360> you<00:09:56.140> know<00:09:56.230> can<00:09:56.620> mix<00:09:56.890> things<00:09:57.160> we<00:09:57.370> can<00:09:57.550> mix 00:09:57.810 --> 00:09:57.820 align:start position:0% other you know can mix things we can mix 00:09:57.820 --> 00:10:01.230 align:start position:0% other you know can mix things we can mix between<00:09:58.260> one<00:09:59.260> chain<00:09:59.589> of<00:10:00.010> chain<00:10:00.370> transactions 00:10:01.230 --> 00:10:01.240 align:start position:0% between one chain of chain transactions 00:10:01.240 --> 00:10:03.570 align:start position:0% between one chain of chain transactions for<00:10:01.330> example<00:10:01.600> we<00:10:01.690> can<00:10:01.839> force<00:10:02.170> a<00:10:02.500> no<00:10:03.100> change<00:10:03.459> man 00:10:03.570 --> 00:10:03.580 align:start position:0% for example we can force a no change man 00:10:03.580 --> 00:10:06.269 align:start position:0% for example we can force a no change man we<00:10:04.180> can<00:10:04.330> force<00:10:04.630> a<00:10:04.899> transfer<00:10:05.649> from<00:10:05.830> on<00:10:06.040> a<00:10:06.100> chain 00:10:06.269 --> 00:10:06.279 align:start position:0% we can force a transfer from on a chain 00:10:06.279 --> 00:10:07.769 align:start position:0% we can force a transfer from on a chain transaction<00:10:06.850> this<00:10:07.029> is<00:10:07.089> very<00:10:07.240> convenient<00:10:07.600> for 00:10:07.769 --> 00:10:07.779 align:start position:0% transaction this is very convenient for 00:10:07.779 --> 00:10:11.730 align:start position:0% transaction this is very convenient for example<00:10:08.230> if<00:10:08.620> a<00:10:08.709> smart<00:10:08.950> contract<00:10:09.100> wants<00:10:09.580> to<00:10:10.740> do 00:10:11.730 --> 00:10:11.740 align:start position:0% example if a smart contract wants to do 00:10:11.740 --> 00:10:14.630 align:start position:0% example if a smart contract wants to do a<00:10:11.820> transfer<00:10:12.820> inside<00:10:13.209> the<00:10:13.360> other<00:10:13.510> chain<00:10:13.810> and 00:10:14.630 --> 00:10:14.640 align:start position:0% a transfer inside the other chain and 00:10:14.640 --> 00:10:17.190 align:start position:0% a transfer inside the other chain and the<00:10:15.640> last<00:10:15.850> one<00:10:16.029> probably<00:10:16.270> the<00:10:16.839> most<00:10:16.990> difficult 00:10:17.190 --> 00:10:17.200 align:start position:0% the last one probably the most difficult 00:10:17.200 --> 00:10:21.240 align:start position:0% the last one probably the most difficult one<00:10:17.620> is<00:10:17.860> that<00:10:18.100> we<00:10:18.190> can<00:10:18.399> so<00:10:19.149> we<00:10:19.240> can<00:10:19.740> deposit<00:10:20.740> on 00:10:21.240 --> 00:10:21.250 align:start position:0% one is that we can so we can deposit on 00:10:21.250 --> 00:10:23.790 align:start position:0% one is that we can so we can deposit on top<00:10:21.790> of<00:10:22.060> another<00:10:22.540> error<00:10:22.959> or<00:10:23.110> McCown<00:10:23.560> that's 00:10:23.790 --> 00:10:23.800 align:start position:0% top of another error or McCown that's 00:10:23.800 --> 00:10:24.990 align:start position:0% top of another error or McCown that's inside<00:10:24.160> and<00:10:24.399> maybe<00:10:24.550> doing<00:10:24.700> that 00:10:24.990 --> 00:10:25.000 align:start position:0% inside and maybe doing that 00:10:25.000 --> 00:10:26.850 align:start position:0% inside and maybe doing that transferring<00:10:25.720> the<00:10:25.810> same<00:10:25.990> as<00:10:26.350> you<00:10:26.470> can<00:10:26.620> see 00:10:26.850 --> 00:10:26.860 align:start position:0% transferring the same as you can see 00:10:26.860 --> 00:10:31.530 align:start position:0% transferring the same as you can see here<00:10:27.130> there<00:10:27.580> is<00:10:27.670> always<00:10:27.959> two<00:10:30.089> there<00:10:31.089> is<00:10:31.149> always 00:10:31.530 --> 00:10:31.540 align:start position:0% here there is always two there is always 00:10:31.540 --> 00:10:35.760 align:start position:0% here there is always two there is always two<00:10:32.100> medical<00:10:33.100> trade<00:10:33.660> processors<00:10:34.660> in<00:10:35.470> general 00:10:35.760 --> 00:10:35.770 align:start position:0% two medical trade processors in general 00:10:35.770 --> 00:10:37.769 align:start position:0% two medical trade processors in general is<00:10:35.860> from<00:10:36.100> the<00:10:36.250> sender<00:10:37.029> and<00:10:37.060> from<00:10:37.330> the<00:10:37.480> receiver 00:10:37.769 --> 00:10:37.779 align:start position:0% is from the sender and from the receiver 00:10:37.779 --> 00:10:39.840 align:start position:0% is from the sender and from the receiver but<00:10:38.230> you<00:10:38.380> are<00:10:38.500> using<00:10:38.740> accordingly<00:10:39.399> depending 00:10:39.840 --> 00:10:39.850 align:start position:0% but you are using accordingly depending 00:10:39.850 --> 00:10:43.760 align:start position:0% but you are using accordingly depending on<00:10:40.300> the<00:10:40.360> transaction<00:10:40.750> that<00:10:41.170> that<00:10:41.890> we<00:10:42.070> have 00:10:43.760 --> 00:10:43.770 align:start position:0% on the transaction that that we have 00:10:43.770 --> 00:10:45.170 align:start position:0% on the transaction that that we have okay 00:10:45.170 --> 00:10:45.180 align:start position:0% okay 00:10:45.180 --> 00:10:47.430 align:start position:0% okay so<00:10:46.180> we<00:10:46.300> explained<00:10:46.570> earlier<00:10:46.690> we<00:10:46.870> go<00:10:47.080> home<00:10:47.320> would 00:10:47.430 --> 00:10:47.440 align:start position:0% so we explained earlier we go home would 00:10:47.440 --> 00:10:54.840 align:start position:0% so we explained earlier we go home would exit<00:10:47.830> mechanism<00:10:48.339> works<00:10:49.920> ready<00:10:53.399> so<00:10:54.399> let's<00:10:54.610> talk 00:10:54.840 --> 00:10:54.850 align:start position:0% exit mechanism works ready so let's talk 00:10:54.850 --> 00:10:57.329 align:start position:0% exit mechanism works ready so let's talk about<00:10:55.050> the<00:10:56.050> operator<00:10:56.470> okay 00:10:57.329 --> 00:10:57.339 align:start position:0% about the operator okay 00:10:57.339 --> 00:11:01.920 align:start position:0% about the operator okay who's<00:10:58.080> forging<00:10:59.080> these<00:10:59.589> batches<00:11:00.930> who's 00:11:01.920 --> 00:11:01.930 align:start position:0% who's forging these batches who's 00:11:01.930 --> 00:11:04.110 align:start position:0% who's forging these batches who's writing<00:11:02.860> this<00:11:02.980> was<00:11:03.160> creating<00:11:03.610> these<00:11:03.790> proofs 00:11:04.110 --> 00:11:04.120 align:start position:0% writing this was creating these proofs 00:11:04.120 --> 00:11:05.160 align:start position:0% writing this was creating these proofs well 00:11:05.160 --> 00:11:05.170 align:start position:0% well 00:11:05.170 --> 00:11:07.079 align:start position:0% well well<00:11:05.380> Google<00:11:05.529> here<00:11:05.920> is<00:11:06.100> and<00:11:06.490> we<00:11:06.610> have<00:11:06.640> a<00:11:06.790> lot<00:11:07.060> of 00:11:07.079 --> 00:11:07.089 align:start position:0% well Google here is and we have a lot of 00:11:07.089 --> 00:11:10.620 align:start position:0% well Google here is and we have a lot of blocks<00:11:07.529> we<00:11:08.529> find<00:11:09.190> that<00:11:09.430> the<00:11:09.550> slot<00:11:09.850> is<00:11:10.149> a<00:11:10.180> number 00:11:10.620 --> 00:11:10.630 align:start position:0% blocks we find that the slot is a number 00:11:10.630 --> 00:11:12.329 align:start position:0% blocks we find that the slot is a number of<00:11:10.779> blocks<00:11:10.990> let's<00:11:11.410> say<00:11:11.560> for<00:11:11.770> example<00:11:11.800> 20 00:11:12.329 --> 00:11:12.339 align:start position:0% of blocks let's say for example 20 00:11:12.339 --> 00:11:15.180 align:start position:0% of blocks let's say for example 20 blocks<00:11:12.700> and<00:11:13.120> when<00:11:14.020> you<00:11:14.110> find<00:11:14.350> an<00:11:14.529> era<00:11:14.709> that's 00:11:15.180 --> 00:11:15.190 align:start position:0% blocks and when you find an era that's 00:11:15.190 --> 00:11:17.370 align:start position:0% blocks and when you find an era that's maybe<00:11:15.520> a<00:11:15.700> census<00:11:16.360> allotment<00:11:16.870> and<00:11:16.959> say<00:11:17.140> maybe 00:11:17.370 --> 00:11:17.380 align:start position:0% maybe a census allotment and say maybe 00:11:17.380 --> 00:11:23.579 align:start position:0% maybe a census allotment and say maybe 10<00:11:18.720> 10<00:11:19.720> slots<00:11:20.020> ok<00:11:20.980> so<00:11:21.660> here<00:11:22.660> you<00:11:22.839> works<00:11:23.350> very 00:11:23.579 --> 00:11:23.589 align:start position:0% 10 10 slots ok so here you works very 00:11:23.589 --> 00:11:25.050 align:start position:0% 10 10 slots ok so here you works very much<00:11:23.680> like<00:11:23.860> a<00:11:24.100> proof<00:11:24.370> of<00:11:24.459> mistake 00:11:25.050 --> 00:11:25.060 align:start position:0% much like a proof of mistake 00:11:25.060 --> 00:11:29.780 align:start position:0% much like a proof of mistake so<00:11:25.529> you<00:11:26.529> set<00:11:26.920> up<00:11:27.040> you<00:11:27.279> just<00:11:27.940> put<00:11:28.120> some<00:11:28.300> state<00:11:28.630> in 00:11:29.780 --> 00:11:29.790 align:start position:0% so you set up you just put some state in 00:11:29.790 --> 00:11:32.970 align:start position:0% so you set up you just put some state in you<00:11:30.790> just<00:11:31.000> put<00:11:31.240> mistakes<00:11:31.690> and<00:11:31.899> you<00:11:32.140> will<00:11:32.709> be 00:11:32.970 --> 00:11:32.980 align:start position:0% you just put mistakes and you will be 00:11:32.980 --> 00:11:36.420 align:start position:0% you just put mistakes and you will be able<00:11:33.279> to<00:11:33.690> forge<00:11:34.690> some<00:11:35.050> of<00:11:35.410> the<00:11:35.560> graphs<00:11:35.800> so<00:11:36.160> when 00:11:36.420 --> 00:11:36.430 align:start position:0% able to forge some of the graphs so when 00:11:36.430 --> 00:11:38.160 align:start position:0% able to forge some of the graphs so when you<00:11:36.550> put<00:11:36.730> a<00:11:36.760> state<00:11:37.000> you<00:11:37.180> will<00:11:37.420> start<00:11:37.660> so<00:11:37.990> you 00:11:38.160 --> 00:11:38.170 align:start position:0% you put a state you will start so you 00:11:38.170 --> 00:11:40.319 align:start position:0% you put a state you will start so you would<00:11:38.320> register<00:11:38.620> for<00:11:38.980> either<00:11:39.160> Roscoe<00:11:40.120> so 00:11:40.319 --> 00:11:40.329 align:start position:0% would register for either Roscoe so 00:11:40.329 --> 00:11:42.740 align:start position:0% would register for either Roscoe so fruit<00:11:40.570> were<00:11:40.720> dressing<00:11:41.020> from<00:11:41.490> okay<00:11:42.490> and 00:11:42.740 --> 00:11:42.750 align:start position:0% fruit were dressing from okay and 00:11:42.750 --> 00:11:46.650 align:start position:0% fruit were dressing from okay and furniture<00:11:43.750> and<00:11:43.959> the<00:11:44.050> recent<00:11:44.350> raffle<00:11:44.850> okay<00:11:45.880> the 00:11:46.650 --> 00:11:46.660 align:start position:0% furniture and the recent raffle okay the 00:11:46.660 --> 00:11:50.730 align:start position:0% furniture and the recent raffle okay the raffle<00:11:47.020> happens<00:11:48.240> like<00:11:49.240> one<00:11:49.480> year<00:11:49.630> before<00:11:49.930> okay 00:11:50.730 --> 00:11:50.740 align:start position:0% raffle happens like one year before okay 00:11:50.740 --> 00:11:53.340 align:start position:0% raffle happens like one year before okay oh<00:11:51.160> the<00:11:51.880> raffle<00:11:52.270> is<00:11:52.390> done<00:11:52.570> but<00:11:52.810> the<00:11:52.870> roughly<00:11:53.290> is 00:11:53.340 --> 00:11:53.350 align:start position:0% oh the raffle is done but the roughly is 00:11:53.350 --> 00:11:56.430 align:start position:0% oh the raffle is done but the roughly is is<00:11:54.420> the<00:11:55.420> random<00:11:55.750> number<00:11:56.050> the<00:11:56.170> way<00:11:56.290> of 00:11:56.430 --> 00:11:56.440 align:start position:0% is the random number the way of 00:11:56.440 --> 00:11:59.030 align:start position:0% is the random number the way of generating<00:11:56.740> the<00:11:56.950> random<00:11:57.070> number<00:11:57.520> mainly<00:11:57.880> is 00:11:59.030 --> 00:11:59.040 align:start position:0% generating the random number mainly is 00:11:59.040 --> 00:12:03.030 align:start position:0% generating the random number mainly is well<00:12:00.040> operators<00:12:00.910> they<00:12:01.540> commit<00:12:02.050> so<00:12:02.680> then<00:12:02.920> they 00:12:03.030 --> 00:12:03.040 align:start position:0% well operators they commit so then they 00:12:03.040 --> 00:12:06.170 align:start position:0% well operators they commit so then they crack<00:12:03.250> is<00:12:03.510> designed<00:12:04.510> they<00:12:04.839> decorate<00:12:05.380> this 00:12:06.170 --> 00:12:06.180 align:start position:0% crack is designed they decorate this 00:12:06.180 --> 00:12:07.490 align:start position:0% crack is designed they decorate this line 00:12:07.490 --> 00:12:07.500 align:start position:0% line 00:12:07.500 --> 00:12:09.500 align:start position:0% line while<00:12:08.040> these<00:12:08.190> chaining<00:12:08.730> of<00:12:08.850> clashes<00:12:09.270> so<00:12:09.480> I 00:12:09.500 --> 00:12:09.510 align:start position:0% while these chaining of clashes so I 00:12:09.510 --> 00:12:10.910 align:start position:0% while these chaining of clashes so I click<00:12:09.840> the<00:12:09.870> hash<00:12:10.140> of<00:12:10.290> the<00:12:10.410> hash<00:12:10.440> of<00:12:10.770> the<00:12:10.890> hash 00:12:10.910 --> 00:12:10.920 align:start position:0% click the hash of the hash of the hash 00:12:10.920 --> 00:12:13.040 align:start position:0% click the hash of the hash of the hash of<00:12:11.160> the<00:12:11.280> cartridge<00:12:11.880> I<00:12:12.150> commit<00:12:12.660> to<00:12:12.780> the<00:12:12.870> last 00:12:13.040 --> 00:12:13.050 align:start position:0% of the cartridge I commit to the last 00:12:13.050 --> 00:12:15.380 align:start position:0% of the cartridge I commit to the last one<00:12:13.260> and<00:12:13.470> then<00:12:14.010> for<00:12:14.430> every<00:12:14.520> four<00:12:14.880> for<00:12:15.180> every 00:12:15.380 --> 00:12:15.390 align:start position:0% one and then for every four for every 00:12:15.390 --> 00:12:19.130 align:start position:0% one and then for every four for every block<00:12:15.600> that's<00:12:15.930> that's<00:12:16.920> forge<00:12:17.220> it<00:12:17.820> reveals<00:12:18.810> the 00:12:19.130 --> 00:12:19.140 align:start position:0% block that's that's forge it reveals the 00:12:19.140 --> 00:12:21.020 align:start position:0% block that's that's forge it reveals the last<00:12:19.440> one<00:12:19.650> so<00:12:19.890> then<00:12:20.070> just<00:12:20.310> the<00:12:20.490> frame<00:12:20.700> is<00:12:20.850> one 00:12:21.020 --> 00:12:21.030 align:start position:0% last one so then just the frame is one 00:12:21.030 --> 00:12:22.760 align:start position:0% last one so then just the frame is one the<00:12:21.150> previous<00:12:21.300> one<00:12:21.630> the<00:12:21.750> previous<00:12:22.050> one<00:12:22.260> so<00:12:22.440> uh 00:12:22.760 --> 00:12:22.770 align:start position:0% the previous one the previous one so uh 00:12:22.770 --> 00:12:24.530 align:start position:0% the previous one the previous one so uh needs<00:12:23.130> to<00:12:23.280> be<00:12:23.370> matches<00:12:23.700> with<00:12:23.880> the<00:12:23.970> next<00:12:24.240> one<00:12:24.360> so 00:12:24.530 --> 00:12:24.540 align:start position:0% needs to be matches with the next one so 00:12:24.540 --> 00:12:25.940 align:start position:0% needs to be matches with the next one so it's<00:12:24.750> sempre<00:12:25.020> they're<00:12:25.170> present<00:12:25.470> it's<00:12:25.650> it's 00:12:25.940 --> 00:12:25.950 align:start position:0% it's sempre they're present it's it's 00:12:25.950 --> 00:12:29.030 align:start position:0% it's sempre they're present it's it's our<00:12:26.100> many<00:12:26.250> committed<00:12:27.110> random<00:12:28.110> number<00:12:28.410> and<00:12:28.590> the 00:12:29.030 --> 00:12:29.040 align:start position:0% our many committed random number and the 00:12:29.040 --> 00:12:33.080 align:start position:0% our many committed random number and the raffle<00:12:29.400> is<00:12:29.490> made<00:12:29.730> with<00:12:30.360> hash<00:12:31.110> of<00:12:31.470> all<00:12:31.740> the<00:12:32.090> of 00:12:33.080 --> 00:12:33.090 align:start position:0% raffle is made with hash of all the of 00:12:33.090 --> 00:12:36.470 align:start position:0% raffle is made with hash of all the of all<00:12:33.300> these<00:12:33.560> committed<00:12:34.560> random<00:12:34.980> numbers<00:12:35.480> from 00:12:36.470 --> 00:12:36.480 align:start position:0% all these committed random numbers from 00:12:36.480 --> 00:12:39.920 align:start position:0% all these committed random numbers from all<00:12:36.720> the<00:12:36.840> blocks<00:12:37.050> in<00:12:37.230> in<00:12:38.190> each<00:12:38.370> in<00:12:38.790> each<00:12:38.970> era<00:12:39.330> so 00:12:39.920 --> 00:12:39.930 align:start position:0% all the blocks in in each in each era so 00:12:39.930 --> 00:12:49.450 align:start position:0% all the blocks in in each in each era so it's<00:12:40.080> quite<00:12:40.260> random<00:12:40.760> open<00:12:41.760> this<00:12:45.740> so<00:12:47.120> here<00:12:48.120> is 00:12:49.450 --> 00:12:49.460 align:start position:0% it's quite random open this so here is 00:12:49.460 --> 00:12:51.250 align:start position:0% it's quite random open this so here is [Music] 00:12:51.250 --> 00:12:51.260 align:start position:0% [Music] 00:12:51.260 --> 00:12:55.550 align:start position:0% [Music] the<00:12:52.260> chances<00:12:52.800> that<00:12:52.830> you<00:12:53.630> are<00:12:54.630> assigned<00:12:55.110> to<00:12:55.410> a 00:12:55.550 --> 00:12:55.560 align:start position:0% the chances that you are assigned to a 00:12:55.560 --> 00:12:59.660 align:start position:0% the chances that you are assigned to a specific<00:12:56.030> slot<00:12:57.030> to<00:12:57.630> get<00:12:57.950> to<00:12:58.950> be<00:12:59.130> able<00:12:59.430> to 00:12:59.660 --> 00:12:59.670 align:start position:0% specific slot to get to be able to 00:12:59.670 --> 00:13:02.870 align:start position:0% specific slot to get to be able to forage<00:13:00.600> blocks<00:13:00.900> are<00:13:01.610> according<00:13:02.610> to<00:13:02.760> that 00:13:02.870 --> 00:13:02.880 align:start position:0% forage blocks are according to that 00:13:02.880 --> 00:13:04.460 align:start position:0% forage blocks are according to that quantity<00:13:03.300> of<00:13:03.390> the<00:13:03.450> state<00:13:03.690> that<00:13:03.840> you're<00:13:03.990> in 00:13:04.460 --> 00:13:04.470 align:start position:0% quantity of the state that you're in 00:13:04.470 --> 00:13:07.130 align:start position:0% quantity of the state that you're in actually<00:13:04.980> it's<00:13:05.130> a<00:13:05.310> little<00:13:05.580> before<00:13:06.140> complex's 00:13:07.130 --> 00:13:07.140 align:start position:0% actually it's a little before complex's 00:13:07.140 --> 00:13:09.080 align:start position:0% actually it's a little before complex's maybe<00:13:07.410> it's<00:13:07.620> just<00:13:07.710> like<00:13:07.920> a<00:13:07.950> square<00:13:08.400> or<00:13:08.730> it's 00:13:09.080 --> 00:13:09.090 align:start position:0% maybe it's just like a square or it's 00:13:09.090 --> 00:13:11.990 align:start position:0% maybe it's just like a square or it's like<00:13:09.360> a<00:13:09.390> hex<00:13:09.720> -<00:13:09.870> they're<00:13:10.020> 1.1<00:13:10.650> 1.2<00:13:11.160> we'll<00:13:11.820> see 00:13:11.990 --> 00:13:12.000 align:start position:0% like a hex - they're 1.1 1.2 we'll see 00:13:12.000 --> 00:13:14.120 align:start position:0% like a hex - they're 1.1 1.2 we'll see this<00:13:12.180> is<00:13:12.330> a<00:13:12.360> proportional<00:13:13.080> part<00:13:13.350> maybe<00:13:13.860> we 00:13:14.120 --> 00:13:14.130 align:start position:0% this is a proportional part maybe we 00:13:14.130 --> 00:13:16.910 align:start position:0% this is a proportional part maybe we want<00:13:14.400> that<00:13:14.880> the<00:13:15.120> people<00:13:15.150> that<00:13:15.920> concentrates 00:13:16.910 --> 00:13:16.920 align:start position:0% want that the people that concentrates 00:13:16.920 --> 00:13:19.610 align:start position:0% want that the people that concentrates but<00:13:17.520> it's<00:13:17.640> not<00:13:17.760> the<00:13:17.850> same<00:13:18.060> for<00:13:18.089> example<00:13:18.620> it's 00:13:19.610 --> 00:13:19.620 align:start position:0% but it's not the same for example it's 00:13:19.620 --> 00:13:21.770 align:start position:0% but it's not the same for example it's not<00:13:19.650> the<00:13:19.800> say<00:13:19.950> for<00:13:20.130> example<00:13:20.550> having<00:13:21.180> one 00:13:21.770 --> 00:13:21.780 align:start position:0% not the say for example having one 00:13:21.780 --> 00:13:24.890 align:start position:0% not the say for example having one sticker<00:13:22.170> with<00:13:22.830> 110<00:13:23.760> stickers<00:13:24.180> with<00:13:24.360> one<00:13:24.540> inch 00:13:24.890 --> 00:13:24.900 align:start position:0% sticker with 110 stickers with one inch 00:13:24.900 --> 00:13:27.230 align:start position:0% sticker with 110 stickers with one inch or<00:13:25.080> one<00:13:25.260> is<00:13:25.350> taken<00:13:25.650> with<00:13:25.830> a<00:13:25.980> meter<00:13:26.280> actually 00:13:27.230 --> 00:13:27.240 align:start position:0% or one is taken with a meter actually 00:13:27.240 --> 00:13:29.090 align:start position:0% or one is taken with a meter actually the<00:13:27.360> chances<00:13:27.720> would<00:13:27.810> be<00:13:27.870> the<00:13:28.050> same<00:13:28.290> but<00:13:28.770> in<00:13:28.920> one 00:13:29.090 --> 00:13:29.100 align:start position:0% the chances would be the same but in one 00:13:29.100 --> 00:13:32.210 align:start position:0% the chances would be the same but in one you<00:13:29.250> would<00:13:29.520> read<00:13:29.730> just<00:13:30.089> and<00:13:30.360> ethers<00:13:31.040> in<00:13:32.040> the 00:13:32.210 --> 00:13:32.220 align:start position:0% you would read just and ethers in the 00:13:32.220 --> 00:13:33.650 align:start position:0% you would read just and ethers in the other<00:13:32.370> which<00:13:32.580> reads<00:13:32.820> just<00:13:33.000> what<00:13:33.210> is<00:13:33.330> there<00:13:33.480> so 00:13:33.650 --> 00:13:33.660 align:start position:0% other which reads just what is there so 00:13:33.660 --> 00:13:36.829 align:start position:0% other which reads just what is there so we<00:13:33.839> are<00:13:34.550> compensating<00:13:35.580> the<00:13:36.089> accumulation 00:13:36.829 --> 00:13:36.839 align:start position:0% we are compensating the accumulation 00:13:36.839 --> 00:13:38.780 align:start position:0% we are compensating the accumulation with<00:13:37.110> the<00:13:37.230> people<00:13:37.500> that's<00:13:37.589> staking<00:13:38.580> more 00:13:38.780 --> 00:13:38.790 align:start position:0% with the people that's staking more 00:13:38.790 --> 00:13:40.760 align:start position:0% with the people that's staking more we'll<00:13:39.330> have<00:13:39.540> an<00:13:39.720> extra<00:13:40.200> just<00:13:40.680> for 00:13:40.760 --> 00:13:40.770 align:start position:0% we'll have an extra just for 00:13:40.770 --> 00:13:42.770 align:start position:0% we'll have an extra just for accumulating<00:13:41.580> data<00:13:41.700> we<00:13:42.000> are<00:13:42.030> doing<00:13:42.300> that<00:13:42.510> but 00:13:42.770 --> 00:13:42.780 align:start position:0% accumulating data we are doing that but 00:13:42.780 --> 00:13:46.579 align:start position:0% accumulating data we are doing that but just<00:13:43.460> creating<00:13:44.460> these<00:13:44.580> this<00:13:45.540> effective<00:13:46.260> State 00:13:46.579 --> 00:13:46.589 align:start position:0% just creating these this effective State 00:13:46.589 --> 00:13:52.210 align:start position:0% just creating these this effective State on<00:13:46.830> one<00:13:47.130> arm<00:13:47.280> oh<00:13:50.000> yeah<00:13:51.000> one<00:13:51.660> important<00:13:52.080> thing 00:13:52.210 --> 00:13:52.220 align:start position:0% on one arm oh yeah one important thing 00:13:52.220 --> 00:13:55.460 align:start position:0% on one arm oh yeah one important thing once<00:13:53.220> you<00:13:53.400> are<00:13:53.550> assigned<00:13:53.910> +1<00:13:54.540> in<00:13:54.960> that<00:13:55.140> swab 00:13:55.460 --> 00:13:55.470 align:start position:0% once you are assigned +1 in that swab 00:13:55.470 --> 00:13:59.290 align:start position:0% once you are assigned +1 in that swab the<00:13:55.770> operators<00:13:56.160> can<00:13:56.400> mine<00:13:56.610> can<00:13:57.300> forge<00:13:57.960> as<00:13:58.230> many 00:13:59.290 --> 00:13:59.300 align:start position:0% the operators can mine can forge as many 00:13:59.300 --> 00:14:01.850 align:start position:0% the operators can mine can forge as many as<00:14:00.300> many<00:14:00.570> batches<00:14:00.960> as<00:14:01.170> they<00:14:01.440> want 00:14:01.850 --> 00:14:01.860 align:start position:0% as many batches as they want 00:14:01.860 --> 00:14:03.800 align:start position:0% as many batches as they want so<00:14:02.370> that's<00:14:02.790> an<00:14:03.000> interesting<00:14:03.540> thing<00:14:03.660> because 00:14:03.800 --> 00:14:03.810 align:start position:0% so that's an interesting thing because 00:14:03.810 --> 00:14:06.050 align:start position:0% so that's an interesting thing because they<00:14:04.080> can<00:14:04.290> if<00:14:04.589> they<00:14:04.890> are<00:14:04.980> having<00:14:05.190> the<00:14:05.460> power<00:14:05.700> to 00:14:06.050 --> 00:14:06.060 align:start position:0% they can if they are having the power to 00:14:06.060 --> 00:14:08.570 align:start position:0% they can if they are having the power to generate<00:14:06.589> bunches<00:14:07.589> that's<00:14:07.800> good<00:14:08.010> for<00:14:08.190> them<00:14:08.370> so 00:14:08.570 --> 00:14:08.580 align:start position:0% generate bunches that's good for them so 00:14:08.580 --> 00:14:08.800 align:start position:0% generate bunches that's good for them so the 00:14:08.800 --> 00:14:08.810 align:start position:0% the 00:14:08.810 --> 00:14:10.180 align:start position:0% the something<00:14:09.170> same<00:14:09.440> things<00:14:09.620> that's<00:14:09.740> going<00:14:09.980> on 00:14:10.180 --> 00:14:10.190 align:start position:0% something same things that's going on 00:14:10.190 --> 00:14:12.700 align:start position:0% something same things that's going on there<00:14:10.520> another<00:14:11.300> important<00:14:11.900> characteristic 00:14:12.700 --> 00:14:12.710 align:start position:0% there another important characteristic 00:14:12.710 --> 00:14:16.840 align:start position:0% there another important characteristic here<00:14:13.190> is<00:14:13.370> the<00:14:13.670> kind<00:14:14.480> of<00:14:14.630> pipelining<00:14:15.590> so<00:14:16.160> the 00:14:16.840 --> 00:14:16.850 align:start position:0% here is the kind of pipelining so the 00:14:16.850 --> 00:14:22.330 align:start position:0% here is the kind of pipelining so the idea<00:14:17.360> is<00:14:17.510> that<00:14:17.540> the<00:14:18.440> blocks<00:14:18.980> are<00:14:19.160> not<00:14:20.500> Forge<00:14:21.500> so 00:14:22.330 --> 00:14:22.340 align:start position:0% idea is that the blocks are not Forge so 00:14:22.340 --> 00:14:23.680 align:start position:0% idea is that the blocks are not Forge so the<00:14:22.460> blocks<00:14:22.700> kept<00:14:22.940> so<00:14:23.150> the<00:14:23.270> for<00:14:23.420> the<00:14:23.510> knocks 00:14:23.680 --> 00:14:23.690 align:start position:0% the blocks kept so the for the knocks 00:14:23.690 --> 00:14:27.430 align:start position:0% the blocks kept so the for the knocks can<00:14:23.900> don<00:14:24.170> t<00:14:24.580> needs<00:14:25.580> to<00:14:25.730> be<00:14:25.820> committed<00:14:26.410> before<00:14:27.410> a 00:14:27.430 --> 00:14:27.440 align:start position:0% can don t needs to be committed before a 00:14:27.440 --> 00:14:29.530 align:start position:0% can don t needs to be committed before a specific<00:14:27.680> time<00:14:28.220> in<00:14:28.460> the<00:14:28.580> salon<00:14:28.760> so<00:14:29.120> in<00:14:29.420> the 00:14:29.530 --> 00:14:29.540 align:start position:0% specific time in the salon so in the 00:14:29.540 --> 00:14:31.570 align:start position:0% specific time in the salon so in the last<00:14:29.660> part<00:14:29.779> of<00:14:30.110> the<00:14:30.260> slot<00:14:30.500> you<00:14:30.740> cannot<00:14:31.160> commit 00:14:31.570 --> 00:14:31.580 align:start position:0% last part of the slot you cannot commit 00:14:31.580 --> 00:14:33.880 align:start position:0% last part of the slot you cannot commit the<00:14:31.730> new<00:14:31.880> rocks<00:14:32.120> you<00:14:32.270> can<00:14:32.450> forge<00:14:33.350> blocks<00:14:33.740> that 00:14:33.880 --> 00:14:33.890 align:start position:0% the new rocks you can forge blocks that 00:14:33.890 --> 00:14:35.140 align:start position:0% the new rocks you can forge blocks that are<00:14:34.010> committed<00:14:34.460> previously<00:14:34.970> in<00:14:35.029> the 00:14:35.140 --> 00:14:35.150 align:start position:0% are committed previously in the 00:14:35.150 --> 00:14:37.079 align:start position:0% are committed previously in the beginning<00:14:35.450> of<00:14:35.540> the<00:14:35.690> slot<00:14:35.870> but<00:14:36.290> you<00:14:36.470> cannot 00:14:37.079 --> 00:14:37.089 align:start position:0% beginning of the slot but you cannot 00:14:37.089 --> 00:14:38.890 align:start position:0% beginning of the slot but you cannot commit<00:14:38.089> the<00:14:38.270> new<00:14:38.390> boss 00:14:38.890 --> 00:14:38.900 align:start position:0% commit the new boss 00:14:38.900 --> 00:14:41.650 align:start position:0% commit the new boss this<00:14:39.140> allows<00:14:39.650> to<00:14:39.830> the<00:14:39.920> next<00:14:40.339> operator<00:14:40.790> the<00:14:41.390> one 00:14:41.650 --> 00:14:41.660 align:start position:0% this allows to the next operator the one 00:14:41.660 --> 00:14:43.650 align:start position:0% this allows to the next operator the one that's<00:14:41.839> coming<00:14:42.050> in<00:14:42.230> the<00:14:42.260> best<00:14:42.500> one<00:14:42.860> to<00:14:43.010> start 00:14:43.650 --> 00:14:43.660 align:start position:0% that's coming in the best one to start 00:14:43.660 --> 00:14:46.990 align:start position:0% that's coming in the best one to start to<00:14:44.660> start<00:14:44.930> mining<00:14:45.380> to<00:14:45.560> start<00:14:45.850> computing<00:14:46.850> the 00:14:46.990 --> 00:14:47.000 align:start position:0% to start mining to start computing the 00:14:47.000 --> 00:14:52.450 align:start position:0% to start mining to start computing the proof<00:14:47.240> for<00:14:47.720> for<00:14:48.200> furnace<00:14:48.710> okay<00:14:51.040> the<00:14:52.040> proof<00:14:52.279> is 00:14:52.450 --> 00:14:52.460 align:start position:0% proof for for furnace okay the proof is 00:14:52.460 --> 00:14:57.610 align:start position:0% proof for for furnace okay the proof is very<00:14:52.820> very<00:14:53.529> parallelism<00:14:55.240> pombaline<00:14:56.300> in<00:14:56.620> two 00:14:57.610 --> 00:14:57.620 align:start position:0% very very parallelism pombaline in two 00:14:57.620 --> 00:15:01.480 align:start position:0% very very parallelism pombaline in two ways<00:14:57.860> one<00:14:58.220> is<00:14:58.820> that<00:14:59.920> measure<00:15:00.920> that<00:15:01.100> I<00:15:01.220> have<00:15:01.460> a 00:15:01.480 --> 00:15:01.490 align:start position:0% ways one is that measure that I have a 00:15:01.490 --> 00:15:04.420 align:start position:0% ways one is that measure that I have a processor<00:15:02.150> that's<00:15:02.440> computing<00:15:03.440> a<00:15:03.529> proof 00:15:04.420 --> 00:15:04.430 align:start position:0% processor that's computing a proof 00:15:04.430 --> 00:15:08.260 align:start position:0% processor that's computing a proof well<00:15:04.910> if<00:15:05.210> I<00:15:05.390> have<00:15:06.250> stayed<00:15:07.250> here<00:15:07.550> I<00:15:07.610> can<00:15:07.820> start 00:15:08.260 --> 00:15:08.270 align:start position:0% well if I have stayed here I can start 00:15:08.270 --> 00:15:11.260 align:start position:0% well if I have stayed here I can start computing<00:15:08.480> the<00:15:08.779> proof<00:15:09.230> but<00:15:09.440> maybe<00:15:10.240> in<00:15:11.240> the 00:15:11.260 --> 00:15:11.270 align:start position:0% computing the proof but maybe in the 00:15:11.270 --> 00:15:14.560 align:start position:0% computing the proof but maybe in the reading<00:15:11.900> the<00:15:11.990> proof<00:15:12.200> I<00:15:12.380> can<00:15:12.820> forge<00:15:13.820> another 00:15:14.560 --> 00:15:14.570 align:start position:0% reading the proof I can forge another 00:15:14.570 --> 00:15:16.600 align:start position:0% reading the proof I can forge another block<00:15:14.990> and<00:15:15.320> start<00:15:15.830> computing<00:15:16.310> maybe<00:15:16.520> in 00:15:16.600 --> 00:15:16.610 align:start position:0% block and start computing maybe in 00:15:16.610 --> 00:15:18.340 align:start position:0% block and start computing maybe in another<00:15:16.760> processor<00:15:17.360> the<00:15:17.720> proof<00:15:17.930> that's<00:15:18.170> one 00:15:18.340 --> 00:15:18.350 align:start position:0% another processor the proof that's one 00:15:18.350 --> 00:15:21.340 align:start position:0% another processor the proof that's one way<00:15:18.560> of<00:15:18.670> paralyzing<00:15:19.670> but<00:15:20.660> another<00:15:20.990> way<00:15:21.200> of 00:15:21.340 --> 00:15:21.350 align:start position:0% way of paralyzing but another way of 00:15:21.350 --> 00:15:23.620 align:start position:0% way of paralyzing but another way of paralyzing<00:15:21.800> is<00:15:22.130> just<00:15:22.339> the<00:15:22.640> proof<00:15:22.880> computation 00:15:23.620 --> 00:15:23.630 align:start position:0% paralyzing is just the proof computation 00:15:23.630 --> 00:15:25.990 align:start position:0% paralyzing is just the proof computation just<00:15:23.900> by<00:15:24.230> itself<00:15:24.560> is<00:15:25.040> very<00:15:25.100> parallel<00:15:25.550> example 00:15:25.990 --> 00:15:26.000 align:start position:0% just by itself is very parallel example 00:15:26.000 --> 00:15:28.390 align:start position:0% just by itself is very parallel example itself<00:15:26.480> so<00:15:26.720> maybe<00:15:27.170> it's<00:15:27.410> more<00:15:27.530> convenient<00:15:27.920> to 00:15:28.390 --> 00:15:28.400 align:start position:0% itself so maybe it's more convenient to 00:15:28.400 --> 00:15:32.200 align:start position:0% itself so maybe it's more convenient to put<00:15:28.520> all<00:15:28.700> the<00:15:28.850> four<00:15:29.060> processors<00:15:29.540> just<00:15:29.839> to<00:15:31.210> help 00:15:32.200 --> 00:15:32.210 align:start position:0% put all the four processors just to help 00:15:32.210 --> 00:15:34.630 align:start position:0% put all the four processors just to help in<00:15:32.510> the<00:15:32.810> same<00:15:32.990> proof<00:15:33.350> that<00:15:33.890> would<00:15:34.040> be<00:15:34.190> like<00:15:34.400> the 00:15:34.630 --> 00:15:34.640 align:start position:0% in the same proof that would be like the 00:15:34.640 --> 00:15:36.190 align:start position:0% in the same proof that would be like the last<00:15:34.790> one<00:15:35.000> this<00:15:35.390> will<00:15:35.630> have<00:15:35.900> the<00:15:35.930> advantage 00:15:36.190 --> 00:15:36.200 align:start position:0% last one this will have the advantage 00:15:36.200 --> 00:15:39.850 align:start position:0% last one this will have the advantage that<00:15:36.860> the<00:15:37.430> finalization<00:15:38.089> of<00:15:38.630> our<00:15:38.870> list<00:15:39.350> the 00:15:39.850 --> 00:15:39.860 align:start position:0% that the finalization of our list the 00:15:39.860 --> 00:15:42.100 align:start position:0% that the finalization of our list the finalization<00:15:40.220> of<00:15:40.580> the<00:15:40.640> of<00:15:41.030> the<00:15:41.240> batch<00:15:41.600> would 00:15:42.100 --> 00:15:42.110 align:start position:0% finalization of the of the batch would 00:15:42.110 --> 00:15:44.290 align:start position:0% finalization of the of the batch would be<00:15:42.290> fast<00:15:42.530> will<00:15:42.920> be<00:15:43.040> faster<00:15:43.370> but<00:15:43.880> of<00:15:44.060> course 00:15:44.290 --> 00:15:44.300 align:start position:0% be fast will be faster but of course 00:15:44.300 --> 00:15:49.810 align:start position:0% be fast will be faster but of course require<00:15:44.780> more<00:15:44.990> investment<00:15:45.580> ok<00:15:48.820> swashing 00:15:49.810 --> 00:15:49.820 align:start position:0% require more investment ok swashing 00:15:49.820 --> 00:15:51.850 align:start position:0% require more investment ok swashing whether<00:15:50.360> you<00:15:50.600> slashing<00:15:51.080> where<00:15:51.350> many<00:15:51.530> who<00:15:51.709> are 00:15:51.850 --> 00:15:51.860 align:start position:0% whether you slashing where many who are 00:15:51.860 --> 00:15:56.050 align:start position:0% whether you slashing where many who are looking<00:15:52.250> for<00:15:52.430> those<00:15:52.550> things<00:15:52.610> first<00:15:53.390> the<00:15:55.060> the 00:15:56.050 --> 00:15:56.060 align:start position:0% looking for those things first the the 00:15:56.060 --> 00:15:58.630 align:start position:0% looking for those things first the the operators<00:15:56.570> needs<00:15:56.930> to<00:15:57.110> forge<00:15:57.440> a<00:15:57.709> block<00:15:57.980> from<00:15:58.520> me 00:15:58.630 --> 00:15:58.640 align:start position:0% operators needs to forge a block from me 00:15:58.640 --> 00:16:02.020 align:start position:0% operators needs to forge a block from me to<00:15:58.790> forge<00:15:59.060> a<00:15:59.420> bunch<00:15:59.780> in<00:16:00.050> each<00:16:00.230> aslam<00:16:01.130> if<00:16:01.850> they 00:16:02.020 --> 00:16:02.030 align:start position:0% to forge a bunch in each aslam if they 00:16:02.030 --> 00:16:04.300 align:start position:0% to forge a bunch in each aslam if they go<00:16:02.089> for<00:16:02.209> to<00:16:02.600> batch<00:16:02.839> they<00:16:03.350> are<00:16:03.470> sloshed 00:16:04.300 --> 00:16:04.310 align:start position:0% go for to batch they are sloshed 00:16:04.310 --> 00:16:06.400 align:start position:0% go for to batch they are sloshed just<00:16:04.550> who's<00:16:04.700> asleep<00:16:04.880> and<00:16:05.720> the<00:16:05.900> other<00:16:05.930> is<00:16:06.200> if 00:16:06.400 --> 00:16:06.410 align:start position:0% just who's asleep and the other is if 00:16:06.410 --> 00:16:09.850 align:start position:0% just who's asleep and the other is if they<00:16:06.620> come<00:16:06.890> in<00:16:07.010> to<00:16:07.580> a<00:16:07.610> to<00:16:08.540> a<00:16:08.570> bra<00:16:08.870> and<00:16:09.140> they<00:16:09.710> are 00:16:09.850 --> 00:16:09.860 align:start position:0% they come in to a to a bra and they are 00:16:09.860 --> 00:16:12.670 align:start position:0% they come in to a to a bra and they are not<00:16:10.300> forged<00:16:11.300> and<00:16:11.870> they<00:16:11.960> do<00:16:12.020> not<00:16:12.200> forage<00:16:12.560> that 00:16:12.670 --> 00:16:12.680 align:start position:0% not forged and they do not forage that 00:16:12.680 --> 00:16:14.860 align:start position:0% not forged and they do not forage that come<00:16:12.920> in<00:16:13.040> they<00:16:13.460> are<00:16:13.580> so<00:16:13.610> smashed<00:16:14.060> number<00:16:14.720> two 00:16:14.860 --> 00:16:14.870 align:start position:0% come in they are so smashed number two 00:16:14.870 --> 00:16:18.070 align:start position:0% come in they are so smashed number two things<00:16:15.080> that<00:16:15.290> they<00:16:15.560> are<00:16:15.650> as<00:16:15.800> much<00:16:15.950> with<00:16:17.080> okay 00:16:18.070 --> 00:16:18.080 align:start position:0% things that they are as much with okay 00:16:18.080 --> 00:16:21.190 align:start position:0% things that they are as much with okay here<00:16:18.740> you<00:16:18.980> see<00:16:19.190> the<00:16:19.970> format<00:16:20.450> of<00:16:20.630> that<00:16:20.720> that 00:16:21.190 --> 00:16:21.200 align:start position:0% here you see the format of that that 00:16:21.200 --> 00:16:22.900 align:start position:0% here you see the format of that that viability<00:16:21.650> this<00:16:21.980> is<00:16:22.100> the<00:16:22.220> part<00:16:22.580> of<00:16:22.760> the 00:16:22.900 --> 00:16:22.910 align:start position:0% viability this is the part of the 00:16:22.910 --> 00:16:25.240 align:start position:0% viability this is the part of the transaction<00:16:23.660> that<00:16:24.380> we<00:16:24.529> need<00:16:24.680> to<00:16:24.770> reconstruct 00:16:25.240 --> 00:16:25.250 align:start position:0% transaction that we need to reconstruct 00:16:25.250 --> 00:16:26.829 align:start position:0% transaction that we need to reconstruct the<00:16:25.670> from<00:16:25.820> the<00:16:25.910> statement<00:16:26.360> needs<00:16:26.510> to<00:16:26.690> be<00:16:26.810> a 00:16:26.829 --> 00:16:26.839 align:start position:0% the from the statement needs to be a 00:16:26.839 --> 00:16:28.660 align:start position:0% the from the statement needs to be a vitamin<00:16:27.290> and<00:16:27.440> we're<00:16:27.620> putting<00:16:27.890> these<00:16:28.070> on<00:16:28.339> chain 00:16:28.660 --> 00:16:28.670 align:start position:0% vitamin and we're putting these on chain 00:16:28.670 --> 00:16:31.690 align:start position:0% vitamin and we're putting these on chain okay<00:16:29.540> this<00:16:29.900> is<00:16:30.020> why<00:16:30.230> so<00:16:30.529> sure<00:16:30.800> we<00:16:31.310> have<00:16:31.490> only 00:16:31.690 --> 00:16:31.700 align:start position:0% okay this is why so sure we have only 00:16:31.700 --> 00:16:33.490 align:start position:0% okay this is why so sure we have only three<00:16:32.060> bytes<00:16:32.300> from<00:16:32.540> the<00:16:32.660> front<00:16:32.900> three<00:16:33.350> bite 00:16:33.490 --> 00:16:33.500 align:start position:0% three bytes from the front three bite 00:16:33.500 --> 00:16:35.350 align:start position:0% three bytes from the front three bite from<00:16:33.650> the<00:16:33.830> two<00:16:33.980> here<00:16:34.400> you<00:16:34.550> see<00:16:34.760> the<00:16:34.910> deposit 00:16:35.350 --> 00:16:35.360 align:start position:0% from the two here you see the deposit 00:16:35.360 --> 00:16:36.430 align:start position:0% from the two here you see the deposit when<00:16:35.510> you're<00:16:35.630> doing<00:16:35.839> the<00:16:35.900> deposit<00:16:36.290> are 00:16:36.430 --> 00:16:36.440 align:start position:0% when you're doing the deposit are 00:16:36.440 --> 00:16:38.079 align:start position:0% when you're doing the deposit are assigning<00:16:36.770> a<00:16:36.950> number<00:16:37.100> so<00:16:37.670> you<00:16:37.730> can't<00:16:37.970> like 00:16:38.079 --> 00:16:38.089 align:start position:0% assigning a number so you can't like 00:16:38.089 --> 00:16:40.150 align:start position:0% assigning a number so you can't like you're<00:16:38.360> doing<00:16:38.600> a<00:16:38.690> kind<00:16:38.930> of<00:16:39.020> logging<00:16:39.320> here<00:16:39.800> so 00:16:40.150 --> 00:16:40.160 align:start position:0% you're doing a kind of logging here so 00:16:40.160 --> 00:16:42.430 align:start position:0% you're doing a kind of logging here so you<00:16:40.279> get<00:16:40.430> a<00:16:40.490> very<00:16:40.610> very<00:16:41.000> short<00:16:41.270> address<00:16:41.870> here 00:16:42.430 --> 00:16:42.440 align:start position:0% you get a very very short address here 00:16:42.440 --> 00:16:44.820 align:start position:0% you get a very very short address here and<00:16:43.279> so<00:16:43.670> don't<00:16:43.880> shut<00:16:44.089> the<00:16:44.210> address<00:16:44.450> inside 00:16:44.820 --> 00:16:44.830 align:start position:0% and so don't shut the address inside 00:16:44.830 --> 00:16:48.990 align:start position:0% and so don't shut the address inside then<00:16:45.830> twice<00:16:46.130> is<00:16:46.430> a<00:16:46.460> floating-point<00:16:47.470> style 00:16:48.990 --> 00:16:49.000 align:start position:0% then twice is a floating-point style 00:16:49.000 --> 00:16:51.850 align:start position:0% then twice is a floating-point style number<00:16:50.000> so<00:16:50.450> in<00:16:50.600> two<00:16:50.750> bytes<00:16:50.930> we<00:16:51.260> can<00:16:51.440> put<00:16:51.650> almost 00:16:51.850 --> 00:16:51.860 align:start position:0% number so in two bytes we can put almost 00:16:51.860 --> 00:16:55.180 align:start position:0% number so in two bytes we can put almost any<00:16:52.360> three<00:16:53.440> decimal<00:16:54.440> number<00:16:54.830> three<00:16:55.010> and<00:16:55.130> a 00:16:55.180 --> 00:16:55.190 align:start position:0% any three decimal number three and a 00:16:55.190 --> 00:16:59.110 align:start position:0% any three decimal number three and a half<00:16:55.370> decimal<00:16:55.880> numbers<00:16:57.160> from<00:16:58.160> zero<00:16:58.520> to<00:16:58.640> two<00:16:58.970> to 00:16:59.110 --> 00:16:59.120 align:start position:0% half decimal numbers from zero to two to 00:16:59.120 --> 00:17:02.170 align:start position:0% half decimal numbers from zero to two to the<00:16:59.270> very<00:16:59.990> big<00:17:00.200> number<00:17:00.500> okay<00:17:01.339> so<00:17:01.910> that's 00:17:02.170 --> 00:17:02.180 align:start position:0% the very big number okay so that's 00:17:02.180 --> 00:17:03.850 align:start position:0% the very big number okay so that's that's<00:17:02.870> very<00:17:02.930> important<00:17:03.470> because<00:17:03.529> this<00:17:03.800> is 00:17:03.850 --> 00:17:03.860 align:start position:0% that's very important because this is 00:17:03.860 --> 00:17:06.429 align:start position:0% that's very important because this is what<00:17:04.189> allows<00:17:04.579> acid<00:17:05.000> was<00:17:05.209> many<00:17:05.780> transactions 00:17:06.429 --> 00:17:06.439 align:start position:0% what allows acid was many transactions 00:17:06.439 --> 00:17:12.010 align:start position:0% what allows acid was many transactions in<00:17:06.740> this<00:17:07.310> in<00:17:07.640> this<00:17:07.939> system<00:17:09.699> okay<00:17:10.730> well<00:17:11.600> here<00:17:11.900> is 00:17:12.010 --> 00:17:12.020 align:start position:0% in this in this system okay well here is 00:17:12.020 --> 00:17:16.480 align:start position:0% in this in this system okay well here is the<00:17:12.290> all<00:17:12.949> the<00:17:13.010> hashes<00:17:13.630> would<00:17:14.630> work<00:17:15.400> see<00:17:16.400> all 00:17:16.480 --> 00:17:16.490 align:start position:0% the all the hashes would work see all 00:17:16.490 --> 00:17:18.520 align:start position:0% the all the hashes would work see all the<00:17:16.610> transactions<00:17:17.240> that<00:17:17.929> we<00:17:18.079> need<00:17:18.199> to<00:17:18.319> hash 00:17:18.520 --> 00:17:18.530 align:start position:0% the transactions that we need to hash 00:17:18.530 --> 00:17:21.189 align:start position:0% the transactions that we need to hash see<00:17:19.339> the<00:17:19.400> ching<00:17:20.270> hai's<00:17:20.480> you<00:17:20.660> know<00:17:20.780> ching<00:17:21.020> hai's 00:17:21.189 --> 00:17:21.199 align:start position:0% see the ching hai's you know ching hai's 00:17:21.199 --> 00:17:22.960 align:start position:0% see the ching hai's you know ching hai's because<00:17:21.560> when<00:17:21.949> you<00:17:22.040> are<00:17:22.069> doing<00:17:22.220> a<00:17:22.429> well<00:17:22.880> you 00:17:22.960 --> 00:17:22.970 align:start position:0% because when you are doing a well you 00:17:22.970 --> 00:17:24.610 align:start position:0% because when you are doing a well you are<00:17:23.060> forcing<00:17:23.449> on<00:17:23.660> a<00:17:23.750> cycle<00:17:24.050> first<00:17:24.170> and<00:17:24.350> imagine 00:17:24.610 --> 00:17:24.620 align:start position:0% are forcing on a cycle first and imagine 00:17:24.620 --> 00:17:26.590 align:start position:0% are forcing on a cycle first and imagine that<00:17:24.740> you<00:17:24.829> want<00:17:25.010> to<00:17:25.100> force<00:17:25.339> an<00:17:25.550> exit<00:17:25.910> if<00:17:26.480> you 00:17:26.590 --> 00:17:26.600 align:start position:0% that you want to force an exit if you 00:17:26.600 --> 00:17:28.840 align:start position:0% that you want to force an exit if you want<00:17:26.810> to<00:17:26.900> force<00:17:27.079> an<00:17:27.199> exit<00:17:27.439> you<00:17:27.470> will<00:17:27.740> -<00:17:28.040> agilent 00:17:28.840 --> 00:17:28.850 align:start position:0% want to force an exit you will - agilent 00:17:28.850 --> 00:17:31.840 align:start position:0% want to force an exit you will - agilent chain<00:17:29.060> this<00:17:29.540> will<00:17:29.600> force<00:17:30.440> the<00:17:30.620> operator<00:17:31.340> to 00:17:31.840 --> 00:17:31.850 align:start position:0% chain this will force the operator to 00:17:31.850 --> 00:17:34.090 align:start position:0% chain this will force the operator to mine<00:17:32.060> that<00:17:32.330> transaction<00:17:32.980> transactions<00:17:33.980> that 00:17:34.090 --> 00:17:34.100 align:start position:0% mine that transaction transactions that 00:17:34.100 --> 00:17:35.860 align:start position:0% mine that transaction transactions that are<00:17:34.220> for<00:17:34.610> switch<00:17:34.880> that<00:17:35.120> are<00:17:35.240> born<00:17:35.450> on<00:17:35.600> chain 00:17:35.860 --> 00:17:35.870 align:start position:0% are for switch that are born on chain 00:17:35.870 --> 00:17:38.500 align:start position:0% are for switch that are born on chain are<00:17:36.170> forced<00:17:36.650> they<00:17:36.830> are<00:17:36.890> the<00:17:37.280> operator<00:17:37.610> er<00:17:37.700> have 00:17:38.500 --> 00:17:38.510 align:start position:0% are forced they are the operator er have 00:17:38.510 --> 00:17:41.320 align:start position:0% are forced they are the operator er have the<00:17:38.660> obligation<00:17:38.960> to<00:17:39.700> force<00:17:40.700> that<00:17:40.880> so<00:17:41.090> in<00:17:41.210> that 00:17:41.320 --> 00:17:41.330 align:start position:0% the obligation to force that so in that 00:17:41.330 --> 00:17:42.550 align:start position:0% the obligation to force that so in that such<00:17:41.690> as<00:17:41.840> there<00:17:41.990> are<00:17:42.080> more<00:17:42.200> in<00:17:42.320> the<00:17:42.350> community 00:17:42.550 --> 00:17:42.560 align:start position:0% such as there are more in the community 00:17:42.560 --> 00:17:46.210 align:start position:0% such as there are more in the community a<00:17:42.890> cumulative<00:17:43.840> cumulative<00:17:44.840> cash<00:17:45.320> and<00:17:45.620> for<00:17:46.070> the 00:17:46.210 --> 00:17:46.220 align:start position:0% a cumulative cumulative cash and for the 00:17:46.220 --> 00:17:48.090 align:start position:0% a cumulative cumulative cash and for the that<00:17:46.490> availability<00:17:46.880> park<00:17:47.330> is<00:17:47.510> just<00:17:47.720> an 00:17:48.090 --> 00:17:48.100 align:start position:0% that availability park is just an 00:17:48.100 --> 00:17:53.440 align:start position:0% that availability park is just an sha-256<00:17:49.100> of<00:17:49.280> the<00:17:49.429> other<00:17:49.640> than<00:17:50.030> them<00:17:52.150> fees<00:17:53.150> fees 00:17:53.440 --> 00:17:53.450 align:start position:0% sha-256 of the other than them fees fees 00:17:53.450 --> 00:17:55.150 align:start position:0% sha-256 of the other than them fees fees are<00:17:53.690> you<00:17:54.470> know<00:17:54.590> it<00:17:54.740> soggy 00:17:55.150 --> 00:17:55.160 align:start position:0% are you know it soggy 00:17:55.160 --> 00:17:57.330 align:start position:0% are you know it soggy it's<00:17:55.370> a<00:17:55.460> dictator<00:17:55.850> what's<00:17:56.090> important<00:17:56.690> because 00:17:57.330 --> 00:17:57.340 align:start position:0% it's a dictator what's important because 00:17:57.340 --> 00:17:59.440 align:start position:0% it's a dictator what's important because they<00:17:58.340> want<00:17:58.670> to<00:17:58.700> process<00:17:59.000> a<00:17:59.210> lot<00:17:59.360> of 00:17:59.440 --> 00:17:59.450 align:start position:0% they want to process a lot of 00:17:59.450 --> 00:18:02.080 align:start position:0% they want to process a lot of transactions<00:18:00.050> so<00:18:00.260> I<00:18:00.500> hope<00:18:01.370> you<00:18:01.490> calculate<00:18:01.940> the 00:18:02.080 --> 00:18:02.090 align:start position:0% transactions so I hope you calculate the 00:18:02.090 --> 00:18:05.830 align:start position:0% transactions so I hope you calculate the fees<00:18:02.270> we<00:18:02.450> cannot<00:18:03.400> the<00:18:04.400> operator<00:18:04.730> or<00:18:05.150> an<00:18:05.360> orange 00:18:05.830 --> 00:18:05.840 align:start position:0% fees we cannot the operator or an orange 00:18:05.840 --> 00:18:07.200 align:start position:0% fees we cannot the operator or an orange chain<00:18:06.170> in<00:18:06.530> the<00:18:06.679> chain 00:18:07.200 --> 00:18:07.210 align:start position:0% chain in the chain 00:18:07.210 --> 00:18:09.510 align:start position:0% chain in the chain we<00:18:07.510> cannot<00:18:07.930> put<00:18:08.200> a<00:18:08.230> lot<00:18:08.440> of<00:18:08.560> logic<00:18:09.010> there<00:18:09.190> so<00:18:09.400> we 00:18:09.510 --> 00:18:09.520 align:start position:0% we cannot put a lot of logic there so we 00:18:09.520 --> 00:18:12.060 align:start position:0% we cannot put a lot of logic there so we need<00:18:09.640> a<00:18:09.670> more<00:18:09.910> simplistic<00:18:10.500> manganese<00:18:11.500> so<00:18:11.860> what 00:18:12.060 --> 00:18:12.070 align:start position:0% need a more simplistic manganese so what 00:18:12.070 --> 00:18:14.340 align:start position:0% need a more simplistic manganese so what it<00:18:12.700> does<00:18:12.880> here<00:18:13.180> is<00:18:13.600> that<00:18:13.780> the<00:18:13.930> operator 00:18:14.340 --> 00:18:14.350 align:start position:0% it does here is that the operator 00:18:14.350 --> 00:18:17.790 align:start position:0% it does here is that the operator chooses<00:18:14.710> a<00:18:14.740> field<00:18:15.040> and<00:18:15.190> then<00:18:15.940> it's<00:18:16.510> able<00:18:17.380> in 00:18:17.790 --> 00:18:17.800 align:start position:0% chooses a field and then it's able in 00:18:17.800 --> 00:18:20.460 align:start position:0% chooses a field and then it's able in that<00:18:18.160> block<00:18:18.400> will<00:18:18.850> only<00:18:19.180> be<00:18:19.540> possible<00:18:19.780> to<00:18:20.320> my 00:18:20.460 --> 00:18:20.470 align:start position:0% that block will only be possible to my 00:18:20.470 --> 00:18:24.540 align:start position:0% that block will only be possible to my transactions<00:18:21.250> that<00:18:22.230> user<00:18:23.230> is<00:18:23.740> willing<00:18:24.250> to<00:18:24.280> pay 00:18:24.540 --> 00:18:24.550 align:start position:0% transactions that user is willing to pay 00:18:24.550 --> 00:18:27.990 align:start position:0% transactions that user is willing to pay more<00:18:24.880> than<00:18:24.910> that<00:18:25.210> fee<00:18:25.770> so<00:18:26.770> then<00:18:27.070> computing<00:18:27.850> how 00:18:27.990 --> 00:18:28.000 align:start position:0% more than that fee so then computing how 00:18:28.000 --> 00:18:30.960 align:start position:0% more than that fee so then computing how much<00:18:28.240> fee<00:18:28.900> the<00:18:29.230> operator<00:18:29.530> gets<00:18:29.830> through<00:18:30.760> Watts 00:18:30.960 --> 00:18:30.970 align:start position:0% much fee the operator gets through Watts 00:18:30.970 --> 00:18:33.660 align:start position:0% much fee the operator gets through Watts is<00:18:31.240> just<00:18:31.510> multiplication<00:18:31.930> and<00:18:32.470> these<00:18:33.460> people 00:18:33.660 --> 00:18:33.670 align:start position:0% is just multiplication and these people 00:18:33.670 --> 00:18:35.700 align:start position:0% is just multiplication and these people and<00:18:33.910> resourcefully<00:18:34.660> there<00:18:34.870> is<00:18:34.960> only<00:18:35.140> fifteen 00:18:35.700 --> 00:18:35.710 align:start position:0% and resourcefully there is only fifteen 00:18:35.710 --> 00:18:38.850 align:start position:0% and resourcefully there is only fifteen fifteen<00:18:36.700> as<00:18:37.420> well<00:18:37.630> so<00:18:37.780> you<00:18:37.870> can<00:18:38.050> select<00:18:38.290> fifty 00:18:38.850 --> 00:18:38.860 align:start position:0% fifteen as well so you can select fifty 00:18:38.860 --> 00:18:41.100 align:start position:0% fifteen as well so you can select fifty different<00:18:39.010> coins<00:18:39.370> which<00:18:40.000> field<00:18:40.330> you<00:18:40.450> want<00:18:41.020> to 00:18:41.100 --> 00:18:41.110 align:start position:0% different coins which field you want to 00:18:41.110 --> 00:18:42.510 align:start position:0% different coins which field you want to pay<00:18:41.260> for<00:18:41.500> each<00:18:41.560> coin<00:18:41.830> and<00:18:42.160> then<00:18:42.310> only 00:18:42.510 --> 00:18:42.520 align:start position:0% pay for each coin and then only 00:18:42.520 --> 00:18:45.710 align:start position:0% pay for each coin and then only transactions<00:18:43.180> of<00:18:43.300> that<00:18:43.450> kind<00:18:43.660> will<00:18:43.870> be<00:18:43.900> mind 00:18:45.710 --> 00:18:45.720 align:start position:0% transactions of that kind will be mind 00:18:45.720 --> 00:18:49.100 align:start position:0% transactions of that kind will be mind [Music] 00:18:49.100 --> 00:18:49.110 align:start position:0% 00:18:49.110 --> 00:18:51.690 align:start position:0% signature<00:18:50.110> verification<00:18:50.170> here<00:18:50.980> in<00:18:51.070> Theresa<00:18:51.430> I 00:18:51.690 --> 00:18:51.700 align:start position:0% signature verification here in Theresa I 00:18:51.700 --> 00:18:53.280 align:start position:0% signature verification here in Theresa I think<00:18:51.760> here<00:18:52.090> the<00:18:52.120> result<00:18:52.540> of<00:18:52.660> investigation 00:18:53.280 --> 00:18:53.290 align:start position:0% think here the result of investigation 00:18:53.290 --> 00:18:58.440 align:start position:0% think here the result of investigation to<00:18:53.610> where<00:18:54.610> we're<00:18:55.060> using<00:18:55.090> V<00:18:55.960> BSA<00:18:56.880> in<00:18:57.880> baby<00:18:58.150> job 00:18:58.440 --> 00:18:58.450 align:start position:0% to where we're using V BSA in baby job 00:18:58.450 --> 00:19:02.640 align:start position:0% to where we're using V BSA in baby job we're<00:18:58.720> using<00:18:58.930> the<00:18:59.250> Poseidon<00:19:01.350> function<00:19:02.350> it's<00:19:02.530> a 00:19:02.640 --> 00:19:02.650 align:start position:0% we're using the Poseidon function it's a 00:19:02.650 --> 00:19:05.400 align:start position:0% we're using the Poseidon function it's a function<00:19:02.680> that's<00:19:03.430> still<00:19:03.820> not<00:19:04.150> well<00:19:04.930> it's<00:19:05.110> safe 00:19:05.400 --> 00:19:05.410 align:start position:0% function that's still not well it's safe 00:19:05.410 --> 00:19:08.760 align:start position:0% function that's still not well it's safe what's<00:19:05.680> very<00:19:05.950> new<00:19:06.160> and<00:19:07.260> right<00:19:08.260> now<00:19:08.380> I<00:19:08.410> know 00:19:08.760 --> 00:19:08.770 align:start position:0% what's very new and right now I know 00:19:08.770 --> 00:19:10.470 align:start position:0% what's very new and right now I know that<00:19:08.800> that<00:19:08.980> is<00:19:09.280> the<00:19:09.460> foundation<00:19:10.210> and<00:19:10.390> our 00:19:10.470 --> 00:19:10.480 align:start position:0% that that is the foundation and our 00:19:10.480 --> 00:19:12.810 align:start position:0% that that is the foundation and our people<00:19:10.870> are<00:19:10.930> running<00:19:11.290> some<00:19:11.640> competitions<00:19:12.640> in 00:19:12.810 --> 00:19:12.820 align:start position:0% people are running some competitions in 00:19:12.820 --> 00:19:15.210 align:start position:0% people are running some competitions in trying<00:19:13.060> to<00:19:13.300> break<00:19:13.510> this<00:19:13.950> this<00:19:14.950> new 00:19:15.210 --> 00:19:15.220 align:start position:0% trying to break this this new 00:19:15.220 --> 00:19:17.730 align:start position:0% trying to break this this new cryptographic<00:19:16.120> futures<00:19:17.080> but<00:19:17.290> they<00:19:17.440> are<00:19:17.530> very 00:19:17.730 --> 00:19:17.740 align:start position:0% cryptographic futures but they are very 00:19:17.740 --> 00:19:19.400 align:start position:0% cryptographic futures but they are very efficient<00:19:18.160> and<00:19:18.250> it<00:19:18.340> works<00:19:18.580> very<00:19:18.790> very<00:19:19.000> well 00:19:19.400 --> 00:19:19.410 align:start position:0% efficient and it works very very well 00:19:19.410 --> 00:19:22.530 align:start position:0% efficient and it works very very well maybe<00:19:20.410> it's<00:19:20.650> possible<00:19:20.860> to<00:19:21.370> kampachi<00:19:21.700> inside 00:19:22.530 --> 00:19:22.540 align:start position:0% maybe it's possible to kampachi inside 00:19:22.540 --> 00:19:25.130 align:start position:0% maybe it's possible to kampachi inside the<00:19:22.750> eyes<00:19:22.960> inside<00:19:23.170> the<00:19:23.470> sword 00:19:25.130 --> 00:19:25.140 align:start position:0% the eyes inside the sword 00:19:25.140 --> 00:19:27.450 align:start position:0% the eyes inside the sword normal<00:19:26.140> batching<00:19:26.590> of<00:19:26.710> a<00:19:26.800> media<00:19:27.040> say<00:19:27.250> would 00:19:27.450 --> 00:19:27.460 align:start position:0% normal batching of a media say would 00:19:27.460 --> 00:19:31.800 align:start position:0% normal batching of a media say would require<00:19:28.650> to<00:19:29.650> work<00:19:30.090> with<00:19:31.090> model<00:19:31.600> with<00:19:31.780> a 00:19:31.800 --> 00:19:31.810 align:start position:0% require to work with model with a 00:19:31.810 --> 00:19:34.980 align:start position:0% require to work with model with a modular<00:19:32.290> math<00:19:32.820> that's<00:19:33.820> not<00:19:34.210> exactly<00:19:34.690> the<00:19:34.870> one 00:19:34.980 --> 00:19:34.990 align:start position:0% modular math that's not exactly the one 00:19:34.990 --> 00:19:37.590 align:start position:0% modular math that's not exactly the one that<00:19:35.170> starts<00:19:35.560> so<00:19:35.620> it's<00:19:35.860> not<00:19:36.070> as<00:19:36.400> easy<00:19:36.790> as<00:19:36.820> it 00:19:37.590 --> 00:19:37.600 align:start position:0% that starts so it's not as easy as it 00:19:37.600 --> 00:19:39.450 align:start position:0% that starts so it's not as easy as it looks<00:19:38.290> like<00:19:38.530> but<00:19:38.830> there<00:19:39.220> is<00:19:39.340> some 00:19:39.450 --> 00:19:39.460 align:start position:0% looks like but there is some 00:19:39.460 --> 00:19:41.220 align:start position:0% looks like but there is some investigation<00:19:40.060> there<00:19:40.270> but<00:19:40.750> mainly<00:19:40.990> what 00:19:41.220 --> 00:19:41.230 align:start position:0% investigation there but mainly what 00:19:41.230 --> 00:19:42.900 align:start position:0% investigation there but mainly what we're<00:19:41.440> doing<00:19:41.680> is<00:19:41.830> just<00:19:42.040> a<00:19:42.100> normally<00:19:42.430> media<00:19:42.700> say 00:19:42.900 --> 00:19:42.910 align:start position:0% we're doing is just a normally media say 00:19:42.910 --> 00:19:44.310 align:start position:0% we're doing is just a normally media say for<00:19:43.180> each<00:19:43.210> transaction<00:19:43.480> and<00:19:43.930> this<00:19:44.050> is<00:19:44.140> right 00:19:44.310 --> 00:19:44.320 align:start position:0% for each transaction and this is right 00:19:44.320 --> 00:19:47.130 align:start position:0% for each transaction and this is right now<00:19:44.440> one<00:19:44.620> of<00:19:44.650> the<00:19:44.860> most<00:19:44.980> important<00:19:46.140> consuming 00:19:47.130 --> 00:19:47.140 align:start position:0% now one of the most important consuming 00:19:47.140 --> 00:19:48.990 align:start position:0% now one of the most important consuming in<00:19:47.500> the<00:19:47.890> number<00:19:48.130> of<00:19:48.250> constraints<00:19:48.640> that<00:19:48.820> were 00:19:48.990 --> 00:19:49.000 align:start position:0% in the number of constraints that were 00:19:49.000 --> 00:19:50.590 align:start position:0% in the number of constraints that were having 00:19:50.590 --> 00:19:50.600 align:start position:0% having 00:19:50.600 --> 00:19:54.590 align:start position:0% having okay<00:19:51.800> here<00:19:52.800> is<00:19:53.010> we<00:19:53.760> already<00:19:54.060> talked<00:19:54.240> about<00:19:54.270> the 00:19:54.590 --> 00:19:54.600 align:start position:0% okay here is we already talked about the 00:19:54.600 --> 00:19:56.360 align:start position:0% okay here is we already talked about the chamber<00:19:54.870> instructions<00:19:55.320> yeah<00:19:56.040> another 00:19:56.360 --> 00:19:56.370 align:start position:0% chamber instructions yeah another 00:19:56.370 --> 00:19:59.120 align:start position:0% chamber instructions yeah another important<00:19:56.910> thing<00:19:57.120> that<00:19:57.350> the<00:19:58.350> system<00:19:58.680> have<00:19:58.920> is 00:19:59.120 --> 00:19:59.130 align:start position:0% important thing that the system have is 00:19:59.130 --> 00:20:01.580 align:start position:0% important thing that the system have is atomic<00:19:59.430> tommix<00:20:00.210> watts<00:20:00.480> atomic<00:20:00.870> forces<00:20:01.350> are 00:20:01.580 --> 00:20:01.590 align:start position:0% atomic tommix watts atomic forces are 00:20:01.590 --> 00:20:03.830 align:start position:0% atomic tommix watts atomic forces are transactions<00:20:02.280> just<00:20:02.940> but<00:20:03.150> without<00:20:03.510> adding 00:20:03.830 --> 00:20:03.840 align:start position:0% transactions just but without adding 00:20:03.840 --> 00:20:06.560 align:start position:0% transactions just but without adding anything<00:20:04.050> will<00:20:04.380> change<00:20:04.410> just<00:20:04.830> you<00:20:05.580> can<00:20:05.850> sign 00:20:06.560 --> 00:20:06.570 align:start position:0% anything will change just you can sign 00:20:06.570 --> 00:20:08.090 align:start position:0% anything will change just you can sign the<00:20:06.600> data<00:20:07.050> section<00:20:07.260> that<00:20:07.830> Eastern 00:20:08.090 --> 00:20:08.100 align:start position:0% the data section that Eastern 00:20:08.100 --> 00:20:10.370 align:start position:0% the data section that Eastern instruction<00:20:08.580> will<00:20:08.790> be<00:20:09.060> only<00:20:09.300> minded<00:20:09.810> if<00:20:09.960> these 00:20:10.370 --> 00:20:10.380 align:start position:0% instruction will be only minded if these 00:20:10.380 --> 00:20:12.320 align:start position:0% instruction will be only minded if these other<00:20:10.560> transactions<00:20:11.220> happen<00:20:11.550> and<00:20:12.030> the<00:20:12.150> same 00:20:12.320 --> 00:20:12.330 align:start position:0% other transactions happen and the same 00:20:12.330 --> 00:20:14.270 align:start position:0% other transactions happen and the same in<00:20:12.450> the<00:20:12.510> other<00:20:12.570> transaction<00:20:13.260> so<00:20:13.680> this<00:20:13.890> allows 00:20:14.270 --> 00:20:14.280 align:start position:0% in the other transaction so this allows 00:20:14.280 --> 00:20:15.800 align:start position:0% in the other transaction so this allows to<00:20:14.460> do<00:20:14.580> atomic<00:20:14.940> swaps<00:20:15.210> this<00:20:15.420> is<00:20:15.570> for<00:20:15.720> example 00:20:15.800 --> 00:20:15.810 align:start position:0% to do atomic swaps this is for example 00:20:15.810 --> 00:20:17.810 align:start position:0% to do atomic swaps this is for example for<00:20:16.140> exchanges<00:20:16.650> which<00:20:17.160> is<00:20:17.280> very<00:20:17.490> convenient 00:20:17.810 --> 00:20:17.820 align:start position:0% for exchanges which is very convenient 00:20:17.820 --> 00:20:19.580 align:start position:0% for exchanges which is very convenient for<00:20:18.030> doing<00:20:18.360> this<00:20:18.510> is<00:20:18.840> kind<00:20:19.170> of<00:20:19.260> a<00:20:19.350> public 00:20:19.580 --> 00:20:19.590 align:start position:0% for doing this is kind of a public 00:20:19.590 --> 00:20:21.890 align:start position:0% for doing this is kind of a public option<00:20:19.710> this<00:20:20.040> is<00:20:20.100> just<00:20:20.460> like<00:20:21.390> the<00:20:21.540> next<00:20:21.810> row 00:20:21.890 --> 00:20:21.900 align:start position:0% option this is just like the next row 00:20:21.900 --> 00:20:24.260 align:start position:0% option this is just like the next row field<00:20:22.140> that's<00:20:22.950> silent<00:20:23.670> when<00:20:24.060> you<00:20:24.150> are 00:20:24.260 --> 00:20:24.270 align:start position:0% field that's silent when you are 00:20:24.270 --> 00:20:27.950 align:start position:0% field that's silent when you are creating<00:20:24.750> the<00:20:25.460> of<00:20:26.460> chain<00:20:26.790> transactions<00:20:27.390> and 00:20:27.950 --> 00:20:27.960 align:start position:0% creating the of chain transactions and 00:20:27.960 --> 00:20:30.260 align:start position:0% creating the of chain transactions and this<00:20:28.080> is<00:20:28.200> on<00:20:28.380> without<00:20:28.560> adding<00:20:29.160> in<00:20:29.310> any<00:20:29.610> extra 00:20:30.260 --> 00:20:30.270 align:start position:0% this is on without adding in any extra 00:20:30.270 --> 00:20:37.880 align:start position:0% this is on without adding in any extra cost<00:20:30.600> in<00:20:31.410> their<00:20:31.800> own<00:20:32.010> chaining<00:20:32.370> part<00:20:36.890> well 00:20:37.880 --> 00:20:37.890 align:start position:0% cost in their own chaining part well 00:20:37.890 --> 00:20:40.330 align:start position:0% cost in their own chaining part well here<00:20:38.220> I<00:20:38.490> want<00:20:39.330> to<00:20:39.480> talk<00:20:39.660> a<00:20:39.690> little<00:20:39.810> bit<00:20:40.170> about 00:20:40.330 --> 00:20:40.340 align:start position:0% here I want to talk a little bit about 00:20:40.340 --> 00:20:42.830 align:start position:0% here I want to talk a little bit about the<00:20:41.340> improvements<00:20:41.940> that<00:20:41.970> we<00:20:42.120> are<00:20:42.390> doing<00:20:42.540> right 00:20:42.830 --> 00:20:42.840 align:start position:0% the improvements that we are doing right 00:20:42.840 --> 00:20:46.580 align:start position:0% the improvements that we are doing right now<00:20:44.090> and<00:20:45.090> we<00:20:45.240> have<00:20:45.390> a<00:20:45.420> full<00:20:45.690> implementation<00:20:45.900> of 00:20:46.580 --> 00:20:46.590 align:start position:0% now and we have a full implementation of 00:20:46.590 --> 00:20:52.940 align:start position:0% now and we have a full implementation of the<00:20:46.950> proof<00:20:47.400> generation<00:20:49.160> code<00:20:50.160> nine<00:20:50.570> GPUs<00:20:51.950> and 00:20:52.940 --> 00:20:52.950 align:start position:0% the proof generation code nine GPUs and 00:20:52.950 --> 00:20:58.370 align:start position:0% the proof generation code nine GPUs and again<00:20:53.400> the<00:20:54.360> N<00:20:54.450> 128<00:20:56.660> very<00:20:57.660> small<00:20:58.110> random 00:20:58.370 --> 00:20:58.380 align:start position:0% again the N 128 very small random 00:20:58.380 --> 00:21:00.800 align:start position:0% again the N 128 very small random numbers<00:20:58.860> it's<00:20:59.190> like<00:20:59.400> in<00:20:59.550> Allen<00:20:59.880> saying<00:21:00.240> this 00:21:00.800 --> 00:21:00.810 align:start position:0% numbers it's like in Allen saying this 00:21:00.810 --> 00:21:02.300 align:start position:0% numbers it's like in Allen saying this is<00:21:00.990> a<00:21:01.020> very<00:21:01.110> wrong<00:21:01.470> numbers<00:21:01.830> because<00:21:02.100> they<00:21:02.220> are 00:21:02.300 --> 00:21:02.310 align:start position:0% is a very wrong numbers because they are 00:21:02.310 --> 00:21:03.770 align:start position:0% is a very wrong numbers because they are still<00:21:02.580> optimizing<00:21:03.150> and<00:21:03.330> we<00:21:03.450> are<00:21:03.570> still 00:21:03.770 --> 00:21:03.780 align:start position:0% still optimizing and we are still 00:21:03.780 --> 00:21:08.360 align:start position:0% still optimizing and we are still working<00:21:03.900> but<00:21:04.260> in<00:21:04.470> a<00:21:04.590> soup<00:21:04.890> 10k<00:21:05.810> hard<00:21:06.810> work<00:21:07.370> we 00:21:08.360 --> 00:21:08.370 align:start position:0% working but in a soup 10k hard work we 00:21:08.370 --> 00:21:16.510 align:start position:0% working but in a soup 10k hard work we can<00:21:08.640> compute<00:21:12.230> 2048<00:21:14.000> transaction<00:21:15.000> proof<00:21:15.450> in 00:21:16.510 --> 00:21:16.520 align:start position:0% can compute 2048 transaction proof in 00:21:16.520 --> 00:21:18.230 align:start position:0% can compute 2048 transaction proof in about<00:21:17.520> 10<00:21:17.820> minutes 00:21:18.230 --> 00:21:18.240 align:start position:0% about 10 minutes 00:21:18.240 --> 00:21:20.570 align:start position:0% about 10 minutes that's<00:21:18.990> our<00:21:19.200> the<00:21:19.650> numbers<00:21:19.980> that<00:21:20.280> we<00:21:20.490> are 00:21:20.570 --> 00:21:20.580 align:start position:0% that's our the numbers that we are 00:21:20.580 --> 00:21:23.900 align:start position:0% that's our the numbers that we are working<00:21:21.450> right<00:21:21.780> now<00:21:21.840> so<00:21:22.590> there<00:21:22.770> are<00:21:22.910> their 00:21:23.900 --> 00:21:23.910 align:start position:0% working right now so there are their 00:21:23.910 --> 00:21:25.790 align:start position:0% working right now so there are their starting<00:21:24.300> point<00:21:24.750> what<00:21:24.930> there<00:21:25.230> are<00:21:25.380> still<00:21:25.620> some 00:21:25.790 --> 00:21:25.800 align:start position:0% starting point what there are still some 00:21:25.800 --> 00:21:27.950 align:start position:0% starting point what there are still some optimizations<00:21:26.430> that<00:21:26.490> we<00:21:26.640> can<00:21:26.760> do<00:21:26.910> here<00:21:27.120> we<00:21:27.720> are 00:21:27.950 --> 00:21:27.960 align:start position:0% optimizations that we can do here we are 00:21:27.960 --> 00:21:30.950 align:start position:0% optimizations that we can do here we are wising<00:21:28.800> maybe<00:21:29.400> is<00:21:29.580> working<00:21:29.970> with<00:21:30.120> FPGAs<00:21:30.780> and 00:21:30.950 --> 00:21:30.960 align:start position:0% wising maybe is working with FPGAs and 00:21:30.960 --> 00:21:33.350 align:start position:0% wising maybe is working with FPGAs and other<00:21:31.260> technologies<00:21:31.920> can<00:21:32.310> be<00:21:32.340> improving<00:21:33.090> here 00:21:33.350 --> 00:21:33.360 align:start position:0% other technologies can be improving here 00:21:33.360 --> 00:21:37.850 align:start position:0% other technologies can be improving here some<00:21:33.960> matter<00:21:34.140> of<00:21:34.550> speed<00:21:35.690> cost<00:21:36.860> complexity 00:21:37.850 --> 00:21:37.860 align:start position:0% some matter of speed cost complexity 00:21:37.860 --> 00:21:40.190 align:start position:0% some matter of speed cost complexity this<00:21:38.400> is<00:21:38.550> very<00:21:38.730> much<00:21:38.910> the<00:21:39.090> parking 00:21:40.190 --> 00:21:40.200 align:start position:0% this is very much the parking 00:21:40.200 --> 00:21:44.840 align:start position:0% this is very much the parking very<00:21:40.889> much<00:21:41.100> oh<00:21:41.279> oh<00:21:42.500> okay<00:21:43.500> here<00:21:44.279> is<00:21:44.399> a<00:21:44.429> numbers 00:21:44.840 --> 00:21:44.850 align:start position:0% very much oh oh okay here is a numbers 00:21:44.850 --> 00:21:48.500 align:start position:0% very much oh oh okay here is a numbers as<00:21:45.240> you<00:21:45.419> see<00:21:45.710> the<00:21:46.710> first<00:21:46.860> line<00:21:47.370> is<00:21:47.789> how<00:21:48.299> much 00:21:48.500 --> 00:21:48.510 align:start position:0% as you see the first line is how much 00:21:48.510 --> 00:21:50.629 align:start position:0% as you see the first line is how much cost<00:21:48.840> well<00:21:49.620> first<00:21:50.070> the<00:21:50.340> number<00:21:50.549> of 00:21:50.629 --> 00:21:50.639 align:start position:0% cost well first the number of 00:21:50.639 --> 00:21:51.620 align:start position:0% cost well first the number of transactions<00:21:51.120> that<00:21:51.179> we're<00:21:51.330> having<00:21:51.419> in 00:21:51.620 --> 00:21:51.630 align:start position:0% transactions that we're having in 00:21:51.630 --> 00:21:53.930 align:start position:0% transactions that we're having in February<00:21:52.019> now<00:21:52.200> is<00:21:52.440> about<00:21:52.710> 32<00:21:53.399> transactions 00:21:53.930 --> 00:21:53.940 align:start position:0% February now is about 32 transactions 00:21:53.940 --> 00:21:56.090 align:start position:0% February now is about 32 transactions here<00:21:54.090> I'm<00:21:54.210> talking<00:21:54.570> just<00:21:54.600> about<00:21:54.929> normally<00:21:55.740> 13 00:21:56.090 --> 00:21:56.100 align:start position:0% here I'm talking just about normally 13 00:21:56.100 --> 00:21:58.460 align:start position:0% here I'm talking just about normally 13 transfers<00:21:56.549> so<00:21:57.059> we<00:21:57.240> have<00:21:57.389> 10<00:21:57.600> millions<00:21:58.019> divided 00:21:58.460 --> 00:21:58.470 align:start position:0% transfers so we have 10 millions divided 00:21:58.470 --> 00:22:01.460 align:start position:0% transfers so we have 10 millions divided by<00:21:58.559> 21<00:21:59.010> K<00:21:59.279> this<00:22:00.120> is<00:22:00.179> 32<00:22:00.690> transactions<00:22:01.380> per 00:22:01.460 --> 00:22:01.470 align:start position:0% by 21 K this is 32 transactions per 00:22:01.470 --> 00:22:04.669 align:start position:0% by 21 K this is 32 transactions per second<00:22:01.769> divided<00:22:02.190> by<00:22:02.309> 15<00:22:02.700> we<00:22:03.149> get<00:22:03.360> 32<00:22:04.350> files 00:22:04.669 --> 00:22:04.679 align:start position:0% second divided by 15 we get 32 files 00:22:04.679 --> 00:22:06.259 align:start position:0% second divided by 15 we get 32 files such<00:22:05.130> as<00:22:05.159> per<00:22:05.399> sector<00:22:05.580> that<00:22:05.789> we<00:22:05.940> have<00:22:06.090> right 00:22:06.259 --> 00:22:06.269 align:start position:0% such as per sector that we have right 00:22:06.269 --> 00:22:08.060 align:start position:0% such as per sector that we have right now<00:22:06.360> normally<00:22:06.990> three<00:22:07.200> transactions<00:22:07.830> just<00:22:07.950> to 00:22:08.060 --> 00:22:08.070 align:start position:0% now normally three transactions just to 00:22:08.070 --> 00:22:11.509 align:start position:0% now normally three transactions just to have<00:22:08.220> a<00:22:08.250> reference<00:22:09.500> if<00:22:10.500> we<00:22:10.830> implement<00:22:11.279> a 00:22:11.509 --> 00:22:11.519 align:start position:0% have a reference if we implement a 00:22:11.519 --> 00:22:14.110 align:start position:0% have a reference if we implement a system<00:22:11.970> in<00:22:12.240> the<00:22:12.330> only<00:22:12.539> change<00:22:12.899> Nancy<00:22:13.230> is<00:22:13.289> now 00:22:14.110 --> 00:22:14.120 align:start position:0% system in the only change Nancy is now 00:22:14.120 --> 00:22:17.029 align:start position:0% system in the only change Nancy is now the<00:22:15.120> cost<00:22:15.419> of<00:22:15.630> putting<00:22:15.779> all<00:22:16.080> these<00:22:16.289> data 00:22:17.029 --> 00:22:17.039 align:start position:0% the cost of putting all these data 00:22:17.039 --> 00:22:19.399 align:start position:0% the cost of putting all these data valuable<00:22:17.580> chain<00:22:18.000> is<00:22:18.480> this<00:22:18.630> quite<00:22:18.899> high 00:22:19.399 --> 00:22:19.409 align:start position:0% valuable chain is this quite high 00:22:19.409 --> 00:22:24.440 align:start position:0% valuable chain is this quite high you<00:22:19.649> see<00:22:20.630> 2048<00:22:21.630> researchers<00:22:22.289> times<00:22:23.190> 8<00:22:23.639> bytes 00:22:24.440 --> 00:22:24.450 align:start position:0% you see 2048 researchers times 8 bytes 00:22:24.450 --> 00:22:25.430 align:start position:0% you see 2048 researchers times 8 bytes per<00:22:24.720> transaction 00:22:25.430 --> 00:22:25.440 align:start position:0% per transaction 00:22:25.440 --> 00:22:29.419 align:start position:0% per transaction I'm<00:22:25.860> size<00:22:26.250> 68<00:22:27.210> Gasper<00:22:27.990> right<00:22:28.169> that's<00:22:28.470> a<00:22:28.710> total 00:22:29.419 --> 00:22:29.429 align:start position:0% I'm size 68 Gasper right that's a total 00:22:29.429 --> 00:22:32.990 align:start position:0% I'm size 68 Gasper right that's a total number<00:22:29.610> of<00:22:30.320> 1<00:22:31.320> mil<00:22:31.529> more<00:22:31.860> than<00:22:32.039> 1<00:22:32.220> million<00:22:32.460> for 00:22:32.990 --> 00:22:33.000 align:start position:0% number of 1 mil more than 1 million for 00:22:33.000 --> 00:22:35.210 align:start position:0% number of 1 mil more than 1 million for 2000<00:22:33.600> rands<00:22:33.750> actions<00:22:34.110> okay<00:22:34.559> so<00:22:34.860> that<00:22:35.010> means 00:22:35.210 --> 00:22:35.220 align:start position:0% 2000 rands actions okay so that means 00:22:35.220 --> 00:22:36.740 align:start position:0% 2000 rands actions okay so that means that<00:22:35.399> we<00:22:35.580> would<00:22:35.730> be<00:22:35.880> able<00:22:36.179> to<00:22:36.330> put<00:22:36.510> five 00:22:36.740 --> 00:22:36.750 align:start position:0% that we would be able to put five 00:22:36.750 --> 00:22:39.259 align:start position:0% that we would be able to put five batches<00:22:37.049> in<00:22:37.710> a<00:22:37.889> block<00:22:38.100> so<00:22:38.639> that's<00:22:38.880> that<00:22:39.090> would 00:22:39.259 --> 00:22:39.269 align:start position:0% batches in a block so that's that would 00:22:39.269 --> 00:22:41.509 align:start position:0% batches in a block so that's that would be<00:22:39.389> the<00:22:39.570> if<00:22:40.169> the<00:22:40.320> the<00:22:40.350> relative<00:22:40.919> number<00:22:41.370> of 00:22:41.509 --> 00:22:41.519 align:start position:0% be the if the the relative number of 00:22:41.519 --> 00:22:44.149 align:start position:0% be the if the the relative number of about<00:22:42.049> 682<00:22:43.049> transactions<00:22:43.590> per<00:22:43.710> second<00:22:44.010> which 00:22:44.149 --> 00:22:44.159 align:start position:0% about 682 transactions per second which 00:22:44.159 --> 00:22:48.710 align:start position:0% about 682 transactions per second which is<00:22:44.309> not<00:22:44.850> bad<00:22:45.409> okay<00:22:46.409> but<00:22:46.980> in<00:22:47.250> the<00:22:47.480> after<00:22:48.480> the 00:22:48.710 --> 00:22:48.720 align:start position:0% is not bad okay but in the after the 00:22:48.720 --> 00:22:52.370 align:start position:0% is not bad okay but in the after the Istanbul<00:22:49.649> where<00:22:50.130> the<00:22:50.370> proofs<00:22:50.970> of<00:22:51.269> these<00:22:51.570> data 00:22:52.370 --> 00:22:52.380 align:start position:0% Istanbul where the proofs of these data 00:22:52.380 --> 00:22:57.950 align:start position:0% Istanbul where the proofs of these data bytes<00:22:52.769> in<00:22:53.159> chain<00:22:53.940> plus<00:22:56.149> the<00:22:57.149> reduction<00:22:57.690> cost 00:22:57.950 --> 00:22:57.960 align:start position:0% bytes in chain plus the reduction cost 00:22:57.960 --> 00:23:00.950 align:start position:0% bytes in chain plus the reduction cost of<00:22:58.320> the<00:22:58.470> of<00:22:58.980> the<00:22:59.190> proof<00:22:59.549> verification<00:23:00.240> okay 00:23:00.950 --> 00:23:00.960 align:start position:0% of the of the proof verification okay 00:23:00.960 --> 00:23:04.399 align:start position:0% of the of the proof verification okay this<00:23:01.350> reduced<00:23:02.720> doing<00:23:03.720> the<00:23:03.809> same<00:23:03.990> numbers<00:23:04.380> we 00:23:04.399 --> 00:23:04.409 align:start position:0% this reduced doing the same numbers we 00:23:04.409 --> 00:23:07.009 align:start position:0% this reduced doing the same numbers we would<00:23:04.679> be<00:23:04.860> able<00:23:05.100> to<00:23:05.190> put<00:23:05.370> 15<00:23:05.850> Manchester<00:23:06.750> walk 00:23:07.009 --> 00:23:07.019 align:start position:0% would be able to put 15 Manchester walk 00:23:07.019 --> 00:23:09.350 align:start position:0% would be able to put 15 Manchester walk and<00:23:07.289> then<00:23:07.830> the<00:23:08.250> number<00:23:08.580> the<00:23:08.850> theory<00:23:09.149> can<00:23:09.299> be 00:23:09.350 --> 00:23:09.360 align:start position:0% and then the number the theory can be 00:23:09.360 --> 00:23:11.180 align:start position:0% and then the number the theory can be beat<00:23:09.630> of<00:23:09.779> the<00:23:09.899> transaction<00:23:10.380> we're<00:23:10.559> talking 00:23:11.180 --> 00:23:11.190 align:start position:0% beat of the transaction we're talking 00:23:11.190 --> 00:23:14.060 align:start position:0% beat of the transaction we're talking always<00:23:11.340> about<00:23:11.460> the<00:23:11.850> DN<00:23:12.059> 128<00:23:12.779> card<00:23:13.169> just 00:23:14.060 --> 00:23:14.070 align:start position:0% always about the DN 128 card just 00:23:14.070 --> 00:23:15.769 align:start position:0% always about the DN 128 card just without<00:23:14.309> doing<00:23:14.549> any<00:23:14.700> special<00:23:15.059> things<00:23:15.269> we 00:23:15.769 --> 00:23:15.779 align:start position:0% without doing any special things we 00:23:15.779 --> 00:23:18.049 align:start position:0% without doing any special things we could<00:23:15.990> go<00:23:16.169> both<00:23:16.559> these<00:23:17.309> reasons<00:23:17.669> of<00:23:17.820> course 00:23:18.049 --> 00:23:18.059 align:start position:0% could go both these reasons of course 00:23:18.059 --> 00:23:19.490 align:start position:0% could go both these reasons of course what<00:23:18.269> we<00:23:18.360> are<00:23:18.480> working<00:23:18.690> with<00:23:18.990> is<00:23:19.139> number<00:23:19.380> of 00:23:19.490 --> 00:23:19.500 align:start position:0% what we are working with is number of 00:23:19.500 --> 00:23:21.169 align:start position:0% what we are working with is number of transactions<00:23:20.039> your<00:23:20.519> stuff<00:23:20.760> having<00:23:21.029> other 00:23:21.169 --> 00:23:21.179 align:start position:0% transactions your stuff having other 00:23:21.179 --> 00:23:22.940 align:start position:0% transactions your stuff having other problems<00:23:21.389> I<00:23:21.779> need<00:23:22.019> to<00:23:22.080> process<00:23:22.289> to<00:23:22.590> thousands 00:23:22.940 --> 00:23:22.950 align:start position:0% problems I need to process to thousands 00:23:22.950 --> 00:23:25.370 align:start position:0% problems I need to process to thousands of<00:23:23.039> sections<00:23:23.429> that<00:23:23.669> are<00:23:24.120> such<00:23:24.299> a<00:23:24.330> cool<00:23:24.690> song 00:23:25.370 --> 00:23:25.380 align:start position:0% of sections that are such a cool song 00:23:25.380 --> 00:23:27.049 align:start position:0% of sections that are such a cool song getting<00:23:25.649> more<00:23:25.860> complex<00:23:26.279> over<00:23:26.519> there<00:23:26.700> you<00:23:26.850> have 00:23:27.049 --> 00:23:27.059 align:start position:0% getting more complex over there you have 00:23:27.059 --> 00:23:29.380 align:start position:0% getting more complex over there you have other<00:23:27.240> people<00:23:27.630> tease<00:23:27.809> and<00:23:28.049> these<00:23:28.380> to<00:23:28.500> be<00:23:28.590> soft 00:23:29.380 --> 00:23:29.390 align:start position:0% other people tease and these to be soft 00:23:29.390 --> 00:23:31.299 align:start position:0% other people tease and these to be soft but<00:23:29.780> that's<00:23:29.990> but<00:23:30.530> a<00:23:30.620> lot<00:23:30.799> of<00:23:30.830> the<00:23:31.070> technical 00:23:31.299 --> 00:23:31.309 align:start position:0% but that's but a lot of the technical 00:23:31.309 --> 00:23:33.180 align:start position:0% but that's but a lot of the technical numbers<00:23:31.730> were<00:23:32.090> here 00:23:33.180 --> 00:23:33.190 align:start position:0% numbers were here 00:23:33.190 --> 00:23:35.980 align:start position:0% numbers were here some<00:23:34.190> of<00:23:34.280> you<00:23:34.429> may<00:23:34.580> think<00:23:34.610> that<00:23:35.030> okay<00:23:35.720> Gavin 00:23:35.980 --> 00:23:35.990 align:start position:0% some of you may think that okay Gavin 00:23:35.990 --> 00:23:39.010 align:start position:0% some of you may think that okay Gavin you<00:23:36.230> have<00:23:36.410> to<00:23:36.530> put<00:23:36.710> this<00:23:37.420> expensive<00:23:38.420> hardware 00:23:39.010 --> 00:23:39.020 align:start position:0% you have to put this expensive hardware 00:23:39.020 --> 00:23:47.049 align:start position:0% you have to put this expensive hardware in<00:23:39.799> order<00:23:39.920> pinion<00:23:42.010> okay<00:23:45.250> but<00:23:46.250> yes<00:23:46.490> yeah<00:23:46.820> the 00:23:47.049 --> 00:23:47.059 align:start position:0% in order pinion okay but yes yeah the 00:23:47.059 --> 00:23:49.360 align:start position:0% in order pinion okay but yes yeah the cost<00:23:47.330> of<00:23:47.510> the<00:23:47.630> hardware<00:23:47.840> should<00:23:48.620> be<00:23:48.830> less<00:23:49.130> if 00:23:49.360 --> 00:23:49.370 align:start position:0% cost of the hardware should be less if 00:23:49.370 --> 00:23:51.640 align:start position:0% cost of the hardware should be less if you<00:23:49.490> do<00:23:49.610> division<00:23:49.850> is<00:23:50.179> less<00:23:50.420> than<00:23:50.570> 1<00:23:50.809> 1<00:23:51.140> 1<00:23:51.380> sin 00:23:51.640 --> 00:23:51.650 align:start position:0% you do division is less than 1 1 1 sin 00:23:51.650 --> 00:23:54.610 align:start position:0% you do division is less than 1 1 1 sin okay<00:23:52.429> so<00:23:53.179> here<00:23:53.420> are<00:23:53.510> a<00:23:53.630> set<00:23:53.870> of<00:23:54.049> terms<00:23:54.200> of<00:23:54.440> our 00:23:54.610 --> 00:23:54.620 align:start position:0% okay so here are a set of terms of our 00:23:54.620 --> 00:23:59.860 align:start position:0% okay so here are a set of terms of our working<00:23:55.010> in<00:23:55.190> in<00:23:56.020> 93<00:23:57.020> we<00:23:57.530> have<00:23:57.740> a<00:23:58.450> circle<00:23:59.450> simcha 00:23:59.860 --> 00:23:59.870 align:start position:0% working in in 93 we have a circle simcha 00:23:59.870 --> 00:24:03.360 align:start position:0% working in in 93 we have a circle simcha bleep<00:24:00.250> many<00:24:01.250> of<00:24:01.370> you<00:24:01.490> are<00:24:01.790> here<00:24:02.390> Aires 00:24:03.360 --> 00:24:03.370 align:start position:0% bleep many of you are here Aires 00:24:03.370 --> 00:24:06.400 align:start position:0% bleep many of you are here Aires coolness<00:24:04.370> arts<00:24:04.700> other<00:24:05.480> things<00:24:05.780> is<00:24:05.960> working<00:24:06.140> is 00:24:06.400 --> 00:24:06.410 align:start position:0% coolness arts other things is working is 00:24:06.410 --> 00:24:09.430 align:start position:0% coolness arts other things is working is going<00:24:06.740> in<00:24:06.980> this<00:24:07.130> place<00:24:07.510> of<00:24:08.510> course<00:24:09.200> we<00:24:09.350> are 00:24:09.430 --> 00:24:09.440 align:start position:0% going in this place of course we are 00:24:09.440 --> 00:24:11.289 align:start position:0% going in this place of course we are still<00:24:09.470> working<00:24:10.040> there<00:24:10.250> any<00:24:10.400> deeper<00:24:10.730> hole<00:24:11.059> this 00:24:11.289 --> 00:24:11.299 align:start position:0% still working there any deeper hole this 00:24:11.299 --> 00:24:13.570 align:start position:0% still working there any deeper hole this is<00:24:11.419> just<00:24:11.660> a<00:24:11.750> specific<00:24:12.230> part<00:24:12.650> of<00:24:12.679> any<00:24:12.919> problem<00:24:13.429> I 00:24:13.570 --> 00:24:13.580 align:start position:0% is just a specific part of any problem I 00:24:13.580 --> 00:24:14.830 align:start position:0% is just a specific part of any problem I don't<00:24:13.760> know<00:24:13.820> if<00:24:13.880> you<00:24:13.940> have<00:24:14.090> seen<00:24:14.299> here<00:24:14.600> but<00:24:14.720> we 00:24:14.830 --> 00:24:14.840 align:start position:0% don't know if you have seen here but we 00:24:14.840 --> 00:24:16.810 align:start position:0% don't know if you have seen here but we are<00:24:14.960> running<00:24:15.200> this<00:24:15.440> game<00:24:15.710> for<00:24:16.070> just<00:24:16.340> verifying 00:24:16.810 --> 00:24:16.820 align:start position:0% are running this game for just verifying 00:24:16.820 --> 00:24:19.990 align:start position:0% are running this game for just verifying or<00:24:17.090> this<00:24:17.660> cannon<00:24:18.650> of<00:24:18.890> trust<00:24:19.220> and<00:24:19.370> network<00:24:19.790> you 00:24:19.990 --> 00:24:20.000 align:start position:0% or this cannon of trust and network you 00:24:20.000 --> 00:24:22.299 align:start position:0% or this cannon of trust and network you see<00:24:20.210> some<00:24:20.540> some<00:24:21.110> papers<00:24:21.470> here<00:24:21.710> if<00:24:21.980> you<00:24:22.070> want<00:24:22.250> to 00:24:22.299 --> 00:24:22.309 align:start position:0% see some some papers here if you want to 00:24:22.309 --> 00:24:24.100 align:start position:0% see some some papers here if you want to play<00:24:22.429> the<00:24:22.490> game<00:24:22.760> that's<00:24:23.030> up<00:24:23.419> to<00:24:23.480> you<00:24:23.720> that's<00:24:23.960> a 00:24:24.100 --> 00:24:24.110 align:start position:0% play the game that's up to you that's a 00:24:24.110 --> 00:24:28.360 align:start position:0% play the game that's up to you that's a nice<00:24:25.070> fun<00:24:25.760> game<00:24:26.210> to<00:24:26.240> play<00:24:26.419> and<00:24:26.960> say<00:24:27.919> yeah<00:24:28.100> we 00:24:28.360 --> 00:24:28.370 align:start position:0% nice fun game to play and say yeah we 00:24:28.370 --> 00:24:33.390 align:start position:0% nice fun game to play and say yeah we want<00:24:28.400> to<00:24:28.640> release<00:24:28.910> the<00:24:29.179> road<00:24:29.870> to<00:24:29.990> release<00:24:30.230> also 00:24:33.390 --> 00:24:33.400 align:start position:0% 00:24:33.400 --> 00:24:36.460 align:start position:0% we<00:24:34.400> want<00:24:34.580> to<00:24:34.610> release<00:24:34.880> all<00:24:35.120> the<00:24:35.330> other<00:24:35.929> API<00:24:36.380> for 00:24:36.460 --> 00:24:36.470 align:start position:0% we want to release all the other API for 00:24:36.470 --> 00:24:38.850 align:start position:0% we want to release all the other API for the<00:24:36.860> idea 00:24:38.850 --> 00:24:38.860 align:start position:0% the idea 00:24:38.860 --> 00:24:42.220 align:start position:0% the idea we<00:24:39.860> are<00:24:40.010> working<00:24:40.250> very<00:24:40.730> hard<00:24:41.150> on<00:24:41.480> the<00:24:41.780> wall<00:24:41.929> and 00:24:42.220 --> 00:24:42.230 align:start position:0% we are working very hard on the wall and 00:24:42.230 --> 00:24:44.100 align:start position:0% we are working very hard on the wall and we<00:24:42.350> hope<00:24:42.559> that<00:24:42.590> the<00:24:42.799> next<00:24:42.980> week's<00:24:43.309> we<00:24:43.429> believe 00:24:44.100 --> 00:24:44.110 align:start position:0% we hope that the next week's we believe 00:24:44.110 --> 00:24:48.550 align:start position:0% we hope that the next week's we believe in<00:24:45.110> essence<00:24:45.620> that's<00:24:46.280> very<00:24:46.549> much 00:24:48.550 --> 00:24:48.560 align:start position:0% in essence that's very much 00:24:48.560 --> 00:24:56.180 align:start position:0% in essence that's very much [Applause]