WEBVTT Kind: captions Language: en 00:00:16.539 --> 00:00:20.109 align:start position:0% hello<00:00:17.539> I'm<00:00:18.439> on<00:00:18.650> one<00:00:18.980> of<00:00:19.099> the<00:00:19.250> court<00:00:19.610> developers 00:00:20.109 --> 00:00:20.119 align:start position:0% hello I'm on one of the court developers 00:00:20.119 --> 00:00:22.409 align:start position:0% hello I'm on one of the court developers behind<00:00:20.270> parity<00:00:20.930> and<00:00:21.080> today<00:00:21.470> I'm<00:00:21.560> going<00:00:21.710> to 00:00:22.409 --> 00:00:22.419 align:start position:0% behind parity and today I'm going to 00:00:22.419 --> 00:00:25.960 align:start position:0% behind parity and today I'm going to speak<00:00:23.419> about<00:00:23.800> what<00:00:24.800> we<00:00:25.009> have<00:00:25.279> been<00:00:25.490> working<00:00:25.730> on 00:00:25.960 --> 00:00:25.970 align:start position:0% speak about what we have been working on 00:00:25.970 --> 00:00:28.060 align:start position:0% speak about what we have been working on the<00:00:26.060> past<00:00:26.270> few<00:00:26.480> months<00:00:26.689> and<00:00:27.140> what<00:00:27.590> we<00:00:27.740> have<00:00:27.919> in 00:00:28.060 --> 00:00:28.070 align:start position:0% the past few months and what we have in 00:00:28.070 --> 00:00:31.749 align:start position:0% the past few months and what we have in store<00:00:28.310> to<00:00:28.669> come<00:00:29.349> so<00:00:30.349> parities<00:00:31.099> you<00:00:31.309> know<00:00:31.489> is<00:00:31.640> it 00:00:31.749 --> 00:00:31.759 align:start position:0% store to come so parities you know is it 00:00:31.759 --> 00:00:34.000 align:start position:0% store to come so parities you know is it fully<00:00:32.000> featured<00:00:32.239> if<00:00:32.599> your<00:00:32.780> own<00:00:32.899> client<00:00:33.410> has 00:00:34.000 --> 00:00:34.010 align:start position:0% fully featured if your own client has 00:00:34.010 --> 00:00:36.280 align:start position:0% fully featured if your own client has everything<00:00:34.460> you<00:00:34.790> need<00:00:34.820> to<00:00:34.969> run<00:00:35.239> a<00:00:35.450> full<00:00:36.079> no 00:00:36.280 --> 00:00:36.290 align:start position:0% everything you need to run a full no 00:00:36.290 --> 00:00:38.650 align:start position:0% everything you need to run a full no ordinary<00:00:36.680> theorem<00:00:37.130> network<00:00:37.579> can<00:00:38.270> sync<00:00:38.570> the 00:00:38.650 --> 00:00:38.660 align:start position:0% ordinary theorem network can sync the 00:00:38.660 --> 00:00:40.959 align:start position:0% ordinary theorem network can sync the blockchain<00:00:38.989> it<00:00:39.469> can<00:00:39.739> do<00:00:39.950> mining<00:00:40.460> it<00:00:40.610> has<00:00:40.790> the 00:00:40.959 --> 00:00:40.969 align:start position:0% blockchain it can do mining it has the 00:00:40.969 --> 00:00:42.720 align:start position:0% blockchain it can do mining it has the API<00:00:41.420> compatible<00:00:42.200> with<00:00:42.379> other 00:00:42.720 --> 00:00:42.730 align:start position:0% API compatible with other 00:00:42.730 --> 00:00:45.790 align:start position:0% API compatible with other implementations<00:00:44.050> but<00:00:45.050> it<00:00:45.170> is<00:00:45.290> also<00:00:45.500> so<00:00:45.739> much 00:00:45.790 --> 00:00:45.800 align:start position:0% implementations but it is also so much 00:00:45.800 --> 00:00:48.489 align:start position:0% implementations but it is also so much more<00:00:46.280> so<00:00:47.149> yesterday<00:00:47.390> we've<00:00:47.870> seen<00:00:48.079> what<00:00:48.289> the 00:00:48.489 --> 00:00:48.499 align:start position:0% more so yesterday we've seen what the 00:00:48.499 --> 00:00:50.410 align:start position:0% more so yesterday we've seen what the user<00:00:48.920> experience<00:00:49.370> might<00:00:49.760> look<00:00:49.940> like<00:00:49.999> with 00:00:50.410 --> 00:00:50.420 align:start position:0% user experience might look like with 00:00:50.420 --> 00:00:53.439 align:start position:0% user experience might look like with parity<00:00:50.960> and<00:00:51.230> it<00:00:52.039> will<00:00:52.249> look<00:00:52.730> like<00:00:52.760> that<00:00:52.940> soon 00:00:53.439 --> 00:00:53.449 align:start position:0% parity and it will look like that soon 00:00:53.449 --> 00:00:55.649 align:start position:0% parity and it will look like that soon and<00:00:53.739> today<00:00:54.739> I'm<00:00:54.829> going<00:00:54.949> to<00:00:55.010> focus<00:00:55.070> on 00:00:55.649 --> 00:00:55.659 align:start position:0% and today I'm going to focus on 00:00:55.659 --> 00:00:59.410 align:start position:0% and today I'm going to focus on technical<00:00:56.659> features<00:00:57.199> that<00:00:57.409> are<00:00:58.179> would<00:00:59.179> be 00:00:59.410 --> 00:00:59.420 align:start position:0% technical features that are would be 00:00:59.420 --> 00:01:01.630 align:start position:0% technical features that are would be interesting<00:00:59.929> for<00:01:00.170> tap<00:01:00.829> developers<00:01:01.429> or 00:01:01.630 --> 00:01:01.640 align:start position:0% interesting for tap developers or 00:01:01.640 --> 00:01:14.680 align:start position:0% interesting for tap developers or watching<00:01:02.239> developers<00:01:02.719> in<00:01:02.870> general<00:01:12.490> so<00:01:13.690> parity 00:01:14.680 --> 00:01:14.690 align:start position:0% watching developers in general so parity 00:01:14.690 --> 00:01:17.500 align:start position:0% watching developers in general so parity is<00:01:14.750> written<00:01:15.050> in<00:01:15.200> rust<00:01:16.030> rust<00:01:17.030> is<00:01:17.330> the 00:01:17.500 --> 00:01:17.510 align:start position:0% is written in rust rust is the 00:01:17.510 --> 00:01:19.719 align:start position:0% is written in rust rust is the relatively<00:01:18.290> new<00:01:18.620> programming<00:01:19.189> language<00:01:19.520> out 00:01:19.719 --> 00:01:19.729 align:start position:0% relatively new programming language out 00:01:19.729 --> 00:01:21.910 align:start position:0% relatively new programming language out there<00:01:19.969> which<00:01:20.600> is<00:01:20.780> particularly<00:01:21.259> well<00:01:21.649> suited 00:01:21.910 --> 00:01:21.920 align:start position:0% there which is particularly well suited 00:01:21.920 --> 00:01:24.490 align:start position:0% there which is particularly well suited for<00:01:22.189> system<00:01:22.880> programming<00:01:23.360> and<00:01:23.630> building<00:01:23.689> fast 00:01:24.490 --> 00:01:24.500 align:start position:0% for system programming and building fast 00:01:24.500 --> 00:01:28.870 align:start position:0% for system programming and building fast and<00:01:24.920> reliable<00:01:25.520> software<00:01:26.979> it<00:01:27.979> has<00:01:28.250> memory 00:01:28.870 --> 00:01:28.880 align:start position:0% and reliable software it has memory 00:01:28.880 --> 00:01:31.359 align:start position:0% and reliable software it has memory safety<00:01:29.180> and<00:01:29.689> concurrency<00:01:30.500> safety<00:01:30.920> guarantees 00:01:31.359 --> 00:01:31.369 align:start position:0% safety and concurrency safety guarantees 00:01:31.369 --> 00:01:33.310 align:start position:0% safety and concurrency safety guarantees know<00:01:32.090> that<00:01:32.329> without<00:01:32.570> sacrificing 00:01:33.310 --> 00:01:33.320 align:start position:0% know that without sacrificing 00:01:33.320 --> 00:01:35.469 align:start position:0% know that without sacrificing performance<00:01:33.350> and<00:01:34.100> it<00:01:34.579> works<00:01:34.820> very<00:01:35.149> well<00:01:35.299> for 00:01:35.469 --> 00:01:35.479 align:start position:0% performance and it works very well for 00:01:35.479 --> 00:01:38.200 align:start position:0% performance and it works very well for whatching<00:01:36.350> applications<00:01:37.009> where<00:01:37.310> reliability 00:01:38.200 --> 00:01:38.210 align:start position:0% whatching applications where reliability 00:01:38.210 --> 00:01:41.469 align:start position:0% whatching applications where reliability and<00:01:39.020> speed<00:01:39.320> are<00:01:39.619> equally<00:01:40.009> important<00:01:40.490> and<00:01:40.700> it 00:01:41.469 --> 00:01:41.479 align:start position:0% and speed are equally important and it 00:01:41.479 --> 00:01:43.990 align:start position:0% and speed are equally important and it worked<00:01:41.780> very<00:01:41.869> well<00:01:42.110> for<00:01:42.259> us<00:01:42.469> or<00:01:42.950> Tim<00:01:43.520> was<00:01:43.729> quite 00:01:43.990 --> 00:01:44.000 align:start position:0% worked very well for us or Tim was quite 00:01:44.000 --> 00:01:49.270 align:start position:0% worked very well for us or Tim was quite happy<00:01:44.240> with<00:01:44.509> this<00:01:44.689> choice<00:01:45.049> and<00:01:46.539> yeah<00:01:47.539> we<00:01:48.280> saved 00:01:49.270 --> 00:01:49.280 align:start position:0% happy with this choice and yeah we saved 00:01:49.280 --> 00:01:52.179 align:start position:0% happy with this choice and yeah we saved us<00:01:49.399> a<00:01:49.430> lot<00:01:49.549> of<00:01:49.700> time<00:01:50.469> so<00:01:51.469> for<00:01:51.710> all<00:01:51.799> the 00:01:52.179 --> 00:01:52.189 align:start position:0% us a lot of time so for all the 00:01:52.189 --> 00:01:53.740 align:start position:0% us a lot of time so for all the developers<00:01:52.759> out<00:01:53.000> there<00:01:53.030> I<00:01:53.329> would<00:01:53.539> greatly 00:01:53.740 --> 00:01:53.750 align:start position:0% developers out there I would greatly 00:01:53.750 --> 00:01:55.840 align:start position:0% developers out there I would greatly recommend<00:01:54.079> to<00:01:54.560> take<00:01:54.890> a<00:01:54.920> look<00:01:55.189> into<00:01:55.490> it<00:01:55.549> and 00:01:55.840 --> 00:01:55.850 align:start position:0% recommend to take a look into it and 00:01:55.850 --> 00:01:58.029 align:start position:0% recommend to take a look into it and it's<00:01:56.659> also<00:01:56.840> one<00:01:57.140> of<00:01:57.170> the<00:01:57.380> reasons<00:01:57.710> that<00:01:57.770> we 00:01:58.029 --> 00:01:58.039 align:start position:0% it's also one of the reasons that we 00:01:58.039 --> 00:01:59.889 align:start position:0% it's also one of the reasons that we believe<00:01:58.070> parity<00:01:58.789> is<00:01:58.850> the<00:01:59.030> fastest<00:01:59.509> a<00:01:59.600> theorem 00:01:59.889 --> 00:01:59.899 align:start position:0% believe parity is the fastest a theorem 00:01:59.899 --> 00:02:02.429 align:start position:0% believe parity is the fastest a theorem point<00:02:00.170> out<00:02:00.380> there<00:02:00.619> but<00:02:01.579> more<00:02:01.909> on<00:02:02.030> that<00:02:02.060> later 00:02:02.429 --> 00:02:02.439 align:start position:0% point out there but more on that later 00:02:02.439 --> 00:02:07.120 align:start position:0% point out there but more on that later and<00:02:03.880> from<00:02:04.880> day<00:02:05.270> one<00:02:05.299> we<00:02:05.899> designed<00:02:06.500> parity<00:02:06.979> to 00:02:07.120 --> 00:02:07.130 align:start position:0% and from day one we designed parity to 00:02:07.130 --> 00:02:10.630 align:start position:0% and from day one we designed parity to be<00:02:07.250> modular<00:02:07.729> and<00:02:08.000> configurable<00:02:09.250> so<00:02:10.250> you<00:02:10.340> can 00:02:10.630 --> 00:02:10.640 align:start position:0% be modular and configurable so you can 00:02:10.640 --> 00:02:13.060 align:start position:0% be modular and configurable so you can use<00:02:10.880> it<00:02:11.030> as<00:02:11.210> a<00:02:11.240> library<00:02:11.510> we<00:02:11.960> have<00:02:11.990> what<00:02:12.950> we 00:02:13.060 --> 00:02:13.070 align:start position:0% use it as a library we have what we 00:02:13.070 --> 00:02:18.340 align:start position:0% use it as a library we have what we documented<00:02:14.140> internal<00:02:15.140> api's<00:02:16.990> then<00:02:17.990> there<00:02:18.230> is 00:02:18.340 --> 00:02:18.350 align:start position:0% documented internal api's then there is 00:02:18.350 --> 00:02:20.530 align:start position:0% documented internal api's then there is a<00:02:18.380> ton<00:02:18.980> of<00:02:19.010> command<00:02:19.520> line<00:02:19.700> options<00:02:20.180> to<00:02:20.420> tweak 00:02:20.530 --> 00:02:20.540 align:start position:0% a ton of command line options to tweak 00:02:20.540 --> 00:02:23.770 align:start position:0% a ton of command line options to tweak various<00:02:21.140> as<00:02:21.730> aspects<00:02:22.730> of<00:02:22.849> paratus<00:02:23.300> behavior 00:02:23.770 --> 00:02:23.780 align:start position:0% various as aspects of paratus behavior 00:02:23.780 --> 00:02:25.979 align:start position:0% various as aspects of paratus behavior and<00:02:24.560> soon<00:02:25.340> we'll<00:02:25.550> be<00:02:25.580> providing 00:02:25.979 --> 00:02:25.989 align:start position:0% and soon we'll be providing 00:02:25.989 --> 00:02:28.089 align:start position:0% and soon we'll be providing configuration<00:02:26.989> file<00:02:27.230> so<00:02:27.260> that<00:02:27.500> you<00:02:27.650> could 00:02:28.089 --> 00:02:28.099 align:start position:0% configuration file so that you could 00:02:28.099 --> 00:02:30.819 align:start position:0% configuration file so that you could easily<00:02:28.489> manage<00:02:28.519> all<00:02:28.999> these<00:02:29.180> options<00:02:29.359> and<00:02:29.840> then 00:02:30.819 --> 00:02:30.829 align:start position:0% easily manage all these options and then 00:02:30.829 --> 00:02:34.420 align:start position:0% easily manage all these options and then presets<00:02:31.450> so<00:02:32.450> that<00:02:32.719> you<00:02:33.230> would<00:02:33.409> have<00:02:34.370> a 00:02:34.420 --> 00:02:34.430 align:start position:0% presets so that you would have a 00:02:34.430 --> 00:02:37.149 align:start position:0% presets so that you would have a particular<00:02:35.090> set<00:02:35.269> of<00:02:36.159> configurations 00:02:37.149 --> 00:02:37.159 align:start position:0% particular set of configurations 00:02:37.159 --> 00:02:39.750 align:start position:0% particular set of configurations optimized<00:02:37.670> for<00:02:37.939> usage<00:02:38.719> scenarios<00:02:39.230> such<00:02:39.469> as 00:02:39.750 --> 00:02:39.760 align:start position:0% optimized for usage scenarios such as 00:02:39.760 --> 00:02:43.869 align:start position:0% optimized for usage scenarios such as mining<00:02:40.760> or<00:02:41.680> Runyon<00:02:42.680> and<00:02:42.799> the<00:02:42.920> Raspberry<00:02:43.310> Pi<00:02:43.370> or 00:02:43.869 --> 00:02:43.879 align:start position:0% mining or Runyon and the Raspberry Pi or 00:02:43.879 --> 00:02:48.309 align:start position:0% mining or Runyon and the Raspberry Pi or during<00:02:44.719> that<00:02:44.930> development<00:02:46.389> now<00:02:47.389> let's<00:02:47.599> get<00:02:48.019> to 00:02:48.309 --> 00:02:48.319 align:start position:0% during that development now let's get to 00:02:48.319 --> 00:02:50.349 align:start position:0% during that development now let's get to performance<00:02:49.069> a<00:02:49.280> bit<00:02:49.430> I'm<00:02:49.819> gonna<00:02:50.090> show<00:02:50.299> you 00:02:50.349 --> 00:02:50.359 align:start position:0% performance a bit I'm gonna show you 00:02:50.359 --> 00:02:54.490 align:start position:0% performance a bit I'm gonna show you just<00:02:50.569> one<00:02:50.810> figure<00:02:51.170> here<00:02:51.819> 20<00:02:53.079> 1910<00:02:54.079> sections 00:02:54.490 --> 00:02:54.500 align:start position:0% just one figure here 20 1910 sections 00:02:54.500 --> 00:02:57.459 align:start position:0% just one figure here 20 1910 sections per<00:02:54.650> second<00:02:55.069> you<00:02:56.030> know<00:02:56.209> that's<00:02:56.780> how<00:02:57.169> fast 00:02:57.459 --> 00:02:57.469 align:start position:0% per second you know that's how fast 00:02:57.469 --> 00:03:00.369 align:start position:0% per second you know that's how fast parity<00:02:58.040> can<00:02:58.219> handle<00:02:58.519> sink<00:02:58.879> in<00:02:59.090> the<00:02:59.379> bottom 00:03:00.369 --> 00:03:00.379 align:start position:0% parity can handle sink in the bottom 00:03:00.379 --> 00:03:03.099 align:start position:0% parity can handle sink in the bottom that's<00:03:00.590> the<00:03:00.799> main<00:03:00.980> homestead<00:03:01.909> watching<00:03:02.419> first 00:03:03.099 --> 00:03:03.109 align:start position:0% that's the main homestead watching first 00:03:03.109 --> 00:03:05.890 align:start position:0% that's the main homestead watching first 2.2<00:03:03.829> million<00:03:04.040> box<00:03:04.519> with<00:03:05.359> nine<00:03:05.629> and<00:03:05.659> a<00:03:05.870> half 00:03:05.890 --> 00:03:05.900 align:start position:0% 2.2 million box with nine and a half 00:03:05.900 --> 00:03:08.439 align:start position:0% 2.2 million box with nine and a half million<00:03:06.319> transactions<00:03:06.980> in<00:03:07.159> them<00:03:07.310> and<00:03:07.849> that 00:03:08.439 --> 00:03:08.449 align:start position:0% million transactions in them and that 00:03:08.449 --> 00:03:10.539 align:start position:0% million transactions in them and that includes<00:03:08.810> full<00:03:09.139> work<00:03:09.739> and<00:03:10.010> transaction 00:03:10.539 --> 00:03:10.549 align:start position:0% includes full work and transaction 00:03:10.549 --> 00:03:13.569 align:start position:0% includes full work and transaction validation<00:03:11.269> and<00:03:11.629> that's<00:03:11.810> how<00:03:12.530> fast<00:03:12.859> is<00:03:13.219> the 00:03:13.569 --> 00:03:13.579 align:start position:0% validation and that's how fast is the 00:03:13.579 --> 00:03:15.789 align:start position:0% validation and that's how fast is the that's<00:03:14.389> the<00:03:14.480> average<00:03:14.870> transaction<00:03:15.230> rate<00:03:15.590> at 00:03:15.789 --> 00:03:15.799 align:start position:0% that's the average transaction rate at 00:03:15.799 --> 00:03:18.970 align:start position:0% that's the average transaction rate at parity<00:03:16.189> can<00:03:16.370> do<00:03:17.199> and<00:03:18.199> there<00:03:18.469> is<00:03:18.500> still<00:03:18.799> room 00:03:18.970 --> 00:03:18.980 align:start position:0% parity can do and there is still room 00:03:18.980 --> 00:03:20.800 align:start position:0% parity can do and there is still room for<00:03:19.040> improvement<00:03:19.250> and<00:03:19.909> we're<00:03:20.150> still<00:03:20.419> working 00:03:20.800 --> 00:03:20.810 align:start position:0% for improvement and we're still working 00:03:20.810 --> 00:03:25.000 align:start position:0% for improvement and we're still working on<00:03:20.959> optimizing<00:03:21.409> this<00:03:22.040> even<00:03:22.340> further<00:03:23.799> now<00:03:24.799> we 00:03:25.000 --> 00:03:25.010 align:start position:0% on optimizing this even further now we 00:03:25.010 --> 00:03:26.740 align:start position:0% on optimizing this even further now we also<00:03:25.159> take<00:03:25.489> a<00:03:25.519> great<00:03:25.790> deal<00:03:25.969> of<00:03:26.060> effort<00:03:26.239> into 00:03:26.740 --> 00:03:26.750 align:start position:0% also take a great deal of effort into 00:03:26.750 --> 00:03:30.220 align:start position:0% also take a great deal of effort into optimizing<00:03:27.590> latencies<00:03:28.430> to<00:03:28.959> work<00:03:29.959> and 00:03:30.220 --> 00:03:30.230 align:start position:0% optimizing latencies to work and 00:03:30.230 --> 00:03:32.469 align:start position:0% optimizing latencies to work and transaction<00:03:30.709> import<00:03:31.040> times<00:03:31.310> when<00:03:32.239> the<00:03:32.329> new 00:03:32.469 --> 00:03:32.479 align:start position:0% transaction import times when the new 00:03:32.479 --> 00:03:34.839 align:start position:0% transaction import times when the new box<00:03:32.780> arrives<00:03:33.259> from<00:03:33.439> the<00:03:33.620> network<00:03:34.040> it<00:03:34.549> gets 00:03:34.839 --> 00:03:34.849 align:start position:0% box arrives from the network it gets 00:03:34.849 --> 00:03:38.439 align:start position:0% box arrives from the network it gets imported<00:03:35.479> and<00:03:35.989> propagated<00:03:36.949> in<00:03:37.909> the<00:03:37.970> least 00:03:38.439 --> 00:03:38.449 align:start position:0% imported and propagated in the least 00:03:38.449 --> 00:03:41.170 align:start position:0% imported and propagated in the least possible<00:03:38.629> time<00:03:39.169> and<00:03:39.699> all<00:03:40.699> of<00:03:40.729> that<00:03:40.819> comes 00:03:41.170 --> 00:03:41.180 align:start position:0% possible time and all of that comes 00:03:41.180 --> 00:03:44.110 align:start position:0% possible time and all of that comes without<00:03:41.540> using<00:03:41.989> too<00:03:42.139> much<00:03:42.290> memory<00:03:42.849> so<00:03:43.849> that 00:03:44.110 --> 00:03:44.120 align:start position:0% without using too much memory so that 00:03:44.120 --> 00:03:46.899 align:start position:0% without using too much memory so that you<00:03:44.509> can<00:03:44.720> easily<00:03:45.169> run<00:03:45.560> parity<00:03:46.129> on<00:03:46.340> a<00:03:46.370> second 00:03:46.899 --> 00:03:46.909 align:start position:0% you can easily run parity on a second 00:03:46.909 --> 00:03:49.539 align:start position:0% you can easily run parity on a second generation<00:03:47.060> Raspberry<00:03:47.840> Pi<00:03:48.189> and<00:03:49.189> it<00:03:49.340> won't 00:03:49.539 --> 00:03:49.549 align:start position:0% generation Raspberry Pi and it won't 00:03:49.549 --> 00:03:51.520 align:start position:0% generation Raspberry Pi and it won't break<00:03:49.879> a<00:03:49.939> sweat<00:03:50.180> and<00:03:50.509> you<00:03:50.629> can<00:03:50.810> even<00:03:51.079> use<00:03:51.229> it<00:03:51.259> as 00:03:51.520 --> 00:03:51.530 align:start position:0% break a sweat and you can even use it as 00:03:51.530 --> 00:03:58.210 align:start position:0% break a sweat and you can even use it as a<00:03:51.560> DEP<00:03:51.859> server<00:03:56.049> now<00:03:57.049> let's<00:03:57.319> talk<00:03:57.500> a<00:03:57.829> bit<00:03:58.009> more 00:03:58.210 --> 00:03:58.220 align:start position:0% a DEP server now let's talk a bit more 00:03:58.220 --> 00:04:01.240 align:start position:0% a DEP server now let's talk a bit more about<00:03:58.549> security<00:03:58.759> probably<00:03:59.750> heard<00:04:00.560> all<00:04:00.709> kinds 00:04:01.240 --> 00:04:01.250 align:start position:0% about security probably heard all kinds 00:04:01.250 --> 00:04:03.460 align:start position:0% about security probably heard all kinds of<00:04:01.970> security<00:04:02.449> issues<00:04:02.569> with<00:04:02.989> a<00:04:03.019> few<00:04:03.229> memory 00:04:03.460 --> 00:04:03.470 align:start position:0% of security issues with a few memory 00:04:03.470 --> 00:04:08.259 align:start position:0% of security issues with a few memory recently<00:04:03.970> so<00:04:04.970> one<00:04:05.120> example<00:04:05.299> is<00:04:05.780> if<00:04:06.650> you<00:04:07.269> expose 00:04:08.259 --> 00:04:08.269 align:start position:0% recently so one example is if you expose 00:04:08.269 --> 00:04:11.319 align:start position:0% recently so one example is if you expose your<00:04:08.569> RPC<00:04:09.079> to<00:04:09.799> the<00:04:09.949> external<00:04:10.400> Network<00:04:10.819> and<00:04:11.150> you 00:04:11.319 --> 00:04:11.329 align:start position:0% your RPC to the external Network and you 00:04:11.329 --> 00:04:13.390 align:start position:0% your RPC to the external Network and you unlock<00:04:11.959> your<00:04:11.989> account<00:04:12.229> even<00:04:12.799> for<00:04:13.069> a<00:04:13.099> short 00:04:13.390 --> 00:04:13.400 align:start position:0% unlock your account even for a short 00:04:13.400 --> 00:04:14.890 align:start position:0% unlock your account even for a short duration<00:04:13.549> you<00:04:13.969> will<00:04:14.090> probably<00:04:14.359> get<00:04:14.659> your 00:04:14.890 --> 00:04:14.900 align:start position:0% duration you will probably get your 00:04:14.900 --> 00:04:18.640 align:start position:0% duration you will probably get your phone<00:04:15.889> stolen<00:04:16.190> and<00:04:17.049> nowadays<00:04:18.049> most<00:04:18.500> of<00:04:18.590> the 00:04:18.640 --> 00:04:18.650 align:start position:0% phone stolen and nowadays most of the 00:04:18.650 --> 00:04:20.830 align:start position:0% phone stolen and nowadays most of the clients<00:04:18.919> work<00:04:19.250> around<00:04:19.519> that<00:04:19.729> by<00:04:19.880> duplicating 00:04:20.830 --> 00:04:20.840 align:start position:0% clients work around that by duplicating 00:04:20.840 --> 00:04:25.360 align:start position:0% clients work around that by duplicating unsafe<00:04:21.289> api's<00:04:21.829> and<00:04:23.740> we<00:04:24.740> took<00:04:24.889> it<00:04:25.039> one<00:04:25.310> step 00:04:25.360 --> 00:04:25.370 align:start position:0% unsafe api's and we took it one step 00:04:25.370 --> 00:04:28.050 align:start position:0% unsafe api's and we took it one step further<00:04:25.880> by<00:04:26.110> introducing<00:04:27.110> the<00:04:27.500> secure 00:04:28.050 --> 00:04:28.060 align:start position:0% further by introducing the secure 00:04:28.060 --> 00:04:31.749 align:start position:0% further by introducing the secure transaction<00:04:29.060> signer<00:04:29.300> architecture<00:04:30.460> the<00:04:31.460> idea 00:04:31.749 --> 00:04:31.759 align:start position:0% transaction signer architecture the idea 00:04:31.759 --> 00:04:34.300 align:start position:0% transaction signer architecture the idea is<00:04:32.000> that<00:04:32.210> all<00:04:32.479> the<00:04:32.810> api's<00:04:33.500> that<00:04:33.800> work<00:04:34.039> with 00:04:34.300 --> 00:04:34.310 align:start position:0% is that all the api's that work with 00:04:34.310 --> 00:04:36.219 align:start position:0% is that all the api's that work with private<00:04:34.729> keys<00:04:35.120> such<00:04:35.630> as<00:04:35.659> send<00:04:36.020> in<00:04:36.139> a 00:04:36.219 --> 00:04:36.229 align:start position:0% private keys such as send in a 00:04:36.229 --> 00:04:38.680 align:start position:0% private keys such as send in a transaction<00:04:36.620> and<00:04:37.580> they<00:04:37.880> become<00:04:38.150> privileged 00:04:38.680 --> 00:04:38.690 align:start position:0% transaction and they become privileged 00:04:38.690 --> 00:04:41.159 align:start position:0% transaction and they become privileged and<00:04:38.930> they<00:04:39.110> no<00:04:39.440> longer<00:04:39.469> execute<00:04:40.219> immediately 00:04:41.159 --> 00:04:41.169 align:start position:0% and they no longer execute immediately 00:04:41.169 --> 00:04:43.920 align:start position:0% and they no longer execute immediately instead<00:04:42.009> when<00:04:42.249> I<00:04:42.279> DEP<00:04:42.849> sends<00:04:43.240> a<00:04:43.300> transaction 00:04:43.920 --> 00:04:43.930 align:start position:0% instead when I DEP sends a transaction 00:04:43.930 --> 00:04:46.529 align:start position:0% instead when I DEP sends a transaction it<00:04:44.680> is<00:04:44.740> added<00:04:45.219> to<00:04:45.249> the<00:04:45.490> confirmation<00:04:46.240> queue 00:04:46.529 --> 00:04:46.539 align:start position:0% it is added to the confirmation queue 00:04:46.539 --> 00:04:49.619 align:start position:0% it is added to the confirmation queue and<00:04:47.319> it<00:04:47.860> stays<00:04:48.159> in<00:04:48.310> the<00:04:48.460> queue<00:04:48.729> until<00:04:48.879> user 00:04:49.619 --> 00:04:49.629 align:start position:0% and it stays in the queue until user 00:04:49.629 --> 00:04:53.129 align:start position:0% and it stays in the queue until user confirms<00:04:50.319> or<00:04:50.680> rejected<00:04:51.370> and<00:04:52.139> that 00:04:53.129 --> 00:04:53.139 align:start position:0% confirms or rejected and that 00:04:53.139 --> 00:04:55.080 align:start position:0% confirms or rejected and that confirmation<00:04:53.529> is<00:04:54.009> done<00:04:54.310> over<00:04:54.669> an<00:04:54.819> additional 00:04:55.080 --> 00:04:55.090 align:start position:0% confirmation is done over an additional 00:04:55.090 --> 00:04:57.689 align:start position:0% confirmation is done over an additional secure<00:04:55.719> channel<00:04:56.110> that<00:04:56.289> is<00:04:56.409> not<00:04:57.129> exposed<00:04:57.520> to 00:04:57.689 --> 00:04:57.699 align:start position:0% secure channel that is not exposed to 00:04:57.699 --> 00:05:01.260 align:start position:0% secure channel that is not exposed to the<00:04:57.870> external<00:04:58.870> Network<00:04:59.499> and<00:04:59.740> it<00:05:00.370> is<00:05:00.729> isolated 00:05:01.260 --> 00:05:01.270 align:start position:0% the external Network and it is isolated 00:05:01.270 --> 00:05:04.790 align:start position:0% the external Network and it is isolated from<00:05:01.749> the<00:05:01.840> abscess<00:05:02.529> run<00:05:03.099> runs<00:05:03.789> in<00:05:03.969> the<00:05:04.150> sandbox 00:05:04.790 --> 00:05:04.800 align:start position:0% from the abscess run runs in the sandbox 00:05:04.800 --> 00:05:08.640 align:start position:0% from the abscess run runs in the sandbox isolated<00:05:05.800> environment<00:05:07.199> and<00:05:08.199> it<00:05:08.499> also 00:05:08.640 --> 00:05:08.650 align:start position:0% isolated environment and it also 00:05:08.650 --> 00:05:10.649 align:start position:0% isolated environment and it also requires<00:05:09.099> additional<00:05:09.490> authorization<00:05:10.479> which 00:05:10.649 --> 00:05:10.659 align:start position:0% requires additional authorization which 00:05:10.659 --> 00:05:12.510 align:start position:0% requires additional authorization which comes<00:05:10.930> in<00:05:11.080> the<00:05:11.169> form<00:05:11.409> of<00:05:11.560> the<00:05:11.770> observation 00:05:12.510 --> 00:05:12.520 align:start position:0% comes in the form of the observation 00:05:12.520 --> 00:05:16.860 align:start position:0% comes in the form of the observation token<00:05:13.349> which<00:05:14.349> usually<00:05:14.949> needs<00:05:15.310> to<00:05:15.430> enter<00:05:15.870> first 00:05:16.860 --> 00:05:16.870 align:start position:0% token which usually needs to enter first 00:05:16.870 --> 00:05:22.110 align:start position:0% token which usually needs to enter first time<00:05:17.110> before<00:05:17.409> using<00:05:17.650> it<00:05:18.270> and<00:05:20.550> yeah<00:05:21.550> I<00:05:21.610> can<00:05:21.939> show 00:05:22.110 --> 00:05:22.120 align:start position:0% time before using it and yeah I can show 00:05:22.120 --> 00:05:26.760 align:start position:0% time before using it and yeah I can show you<00:05:22.180> the<00:05:22.810> UI<00:05:23.589> for<00:05:23.860> that<00:05:24.279> so<00:05:25.210> that's<00:05:25.330> a<00:05:25.770> bit 00:05:26.760 --> 00:05:26.770 align:start position:0% you the UI for that so that's a bit 00:05:26.770 --> 00:05:30.480 align:start position:0% you the UI for that so that's a bit outdated<00:05:27.039> version<00:05:27.810> but<00:05:28.810> still<00:05:29.110> so<00:05:29.949> there's<00:05:30.400> a 00:05:30.480 --> 00:05:30.490 align:start position:0% outdated version but still so there's a 00:05:30.490 --> 00:05:33.749 align:start position:0% outdated version but still so there's a UI<00:05:31.270> for<00:05:31.479> confirming<00:05:32.110> transactions<00:05:32.740> so<00:05:33.580> this 00:05:33.749 --> 00:05:33.759 align:start position:0% UI for confirming transactions so this 00:05:33.759 --> 00:05:35.670 align:start position:0% UI for confirming transactions so this is<00:05:33.909> a<00:05:33.939> version<00:05:34.180> which<00:05:34.659> is<00:05:34.839> the<00:05:34.870> Chrome 00:05:35.670 --> 00:05:35.680 align:start position:0% is a version which is the Chrome 00:05:35.680 --> 00:05:37.649 align:start position:0% is a version which is the Chrome extension<00:05:35.759> so<00:05:36.759> when<00:05:36.909> it's<00:05:37.060> absence<00:05:37.509> it's 00:05:37.649 --> 00:05:37.659 align:start position:0% extension so when it's absence it's 00:05:37.659 --> 00:05:40.260 align:start position:0% extension so when it's absence it's transaction<00:05:38.169> and<00:05:38.379> I<00:05:38.469> can<00:05:38.650> pops<00:05:38.860> up<00:05:39.039> and<00:05:39.939> there 00:05:40.260 --> 00:05:40.270 align:start position:0% transaction and I can pops up and there 00:05:40.270 --> 00:05:41.850 align:start position:0% transaction and I can pops up and there is<00:05:40.389> the<00:05:40.479> list<00:05:40.629> of<00:05:40.779> transaction<00:05:41.349> to<00:05:41.439> confirm 00:05:41.850 --> 00:05:41.860 align:start position:0% is the list of transaction to confirm 00:05:41.860 --> 00:05:46.550 align:start position:0% is the list of transaction to confirm and<00:05:42.310> you<00:05:43.150> can<00:05:43.949> do<00:05:44.949> that<00:05:45.129> informations<00:05:45.969> action 00:05:46.550 --> 00:05:46.560 align:start position:0% and you can do that informations action 00:05:46.560 --> 00:05:49.709 align:start position:0% and you can do that informations action now<00:05:47.560> we<00:05:47.620> have<00:05:47.830> further<00:05:48.069> plans<00:05:48.159> to<00:05:48.789> I<00:05:49.060> saw<00:05:49.539> is 00:05:49.709 --> 00:05:49.719 align:start position:0% now we have further plans to I saw is 00:05:49.719 --> 00:05:52.469 align:start position:0% now we have further plans to I saw is even<00:05:50.259> further<00:05:50.560> to<00:05:51.430> move<00:05:51.610> it<00:05:51.729> to<00:05:52.000> a<00:05:52.029> separate 00:05:52.469 --> 00:05:52.479 align:start position:0% even further to move it to a separate 00:05:52.479 --> 00:05:55.499 align:start position:0% even further to move it to a separate process<00:05:53.020> or<00:05:53.620> even<00:05:53.889> to<00:05:54.099> a<00:05:54.460> different<00:05:55.330> machine 00:05:55.499 --> 00:05:55.509 align:start position:0% process or even to a different machine 00:05:55.509 --> 00:05:57.719 align:start position:0% process or even to a different machine the<00:05:55.689> one<00:05:55.810> with<00:05:56.139> the<00:05:56.349> key<00:05:56.589> store<00:05:56.889> so<00:05:57.129> it<00:05:57.279> can<00:05:57.550> be 00:05:57.719 --> 00:05:57.729 align:start position:0% the one with the key store so it can be 00:05:57.729 --> 00:06:02.129 align:start position:0% the one with the key store so it can be secured<00:05:58.330> and<00:06:00.060> would<00:06:01.060> communicate<00:06:01.689> with<00:06:01.899> a 00:06:02.129 --> 00:06:02.139 align:start position:0% secured and would communicate with a 00:06:02.139 --> 00:06:08.519 align:start position:0% secured and would communicate with a node<00:06:02.469> over<00:06:02.830> a<00:06:02.860> secure<00:06:03.310> IPC<00:06:03.849> channel<00:06:07.529> again 00:06:08.519 --> 00:06:08.529 align:start position:0% node over a secure IPC channel again 00:06:08.529 --> 00:06:12.809 align:start position:0% node over a secure IPC channel again there's<00:06:08.889> a<00:06:09.009> lot<00:06:09.189> more<00:06:09.520> features<00:06:09.960> parity<00:06:11.819> start 00:06:12.809 --> 00:06:12.819 align:start position:0% there's a lot more features parity start 00:06:12.819 --> 00:06:15.059 align:start position:0% there's a lot more features parity start with<00:06:13.120> state<00:06:13.479> tree<00:06:13.719> pruning<00:06:14.020> this<00:06:14.919> is 00:06:15.059 --> 00:06:15.069 align:start position:0% with state tree pruning this is 00:06:15.069 --> 00:06:16.939 align:start position:0% with state tree pruning this is something<00:06:15.490> that<00:06:15.639> can<00:06:15.819> greatly<00:06:16.029> reduce 00:06:16.939 --> 00:06:16.949 align:start position:0% something that can greatly reduce 00:06:16.949 --> 00:06:21.389 align:start position:0% something that can greatly reduce watching<00:06:17.949> database<00:06:18.430> size<00:06:19.259> so<00:06:20.259> it<00:06:20.800> works<00:06:21.099> by 00:06:21.389 --> 00:06:21.399 align:start position:0% watching database size so it works by 00:06:21.399 --> 00:06:25.950 align:start position:0% watching database size so it works by discarding<00:06:21.909> the<00:06:22.300> all<00:06:23.699> watching<00:06:24.699> States<00:06:24.999> so 00:06:25.950 --> 00:06:25.960 align:start position:0% discarding the all watching States so 00:06:25.960 --> 00:06:28.739 align:start position:0% discarding the all watching States so that<00:06:25.990> the<00:06:26.830> state<00:06:27.129> is<00:06:27.370> preserved<00:06:27.849> only<00:06:28.089> for<00:06:28.629> the 00:06:28.739 --> 00:06:28.749 align:start position:0% that the state is preserved only for the 00:06:28.749 --> 00:06:30.570 align:start position:0% that the state is preserved only for the last<00:06:28.960> thousand<00:06:29.529> walks<00:06:29.770> and<00:06:30.069> the<00:06:30.219> rest<00:06:30.430> is 00:06:30.570 --> 00:06:30.580 align:start position:0% last thousand walks and the rest is 00:06:30.580 --> 00:06:33.300 align:start position:0% last thousand walks and the rest is discarded<00:06:31.199> this<00:06:32.199> means<00:06:32.529> you<00:06:32.740> won't<00:06:32.860> be<00:06:33.009> able 00:06:33.300 --> 00:06:33.310 align:start position:0% discarded this means you won't be able 00:06:33.310 --> 00:06:36.230 align:start position:0% discarded this means you won't be able to<00:06:33.520> say<00:06:34.089> query<00:06:34.449> parents<00:06:35.259> that<00:06:35.409> account<00:06:35.740> had 00:06:36.230 --> 00:06:36.240 align:start position:0% to say query parents that account had 00:06:36.240 --> 00:06:39.149 align:start position:0% to say query parents that account had thousand<00:06:37.240> Watts<00:06:37.449> ago<00:06:37.779> but<00:06:38.620> not<00:06:38.860> that<00:06:39.009> many 00:06:39.149 --> 00:06:39.159 align:start position:0% thousand Watts ago but not that many 00:06:39.159 --> 00:06:41.309 align:start position:0% thousand Watts ago but not that many users<00:06:39.580> or<00:06:39.879> applications<00:06:40.120> needed<00:06:41.020> information 00:06:41.309 --> 00:06:41.319 align:start position:0% users or applications needed information 00:06:41.319 --> 00:06:44.489 align:start position:0% users or applications needed information anyway<00:06:41.919> so<00:06:42.759> it<00:06:42.909> is<00:06:43.029> discarded<00:06:43.509> by<00:06:43.839> default<00:06:44.259> and 00:06:44.489 --> 00:06:44.499 align:start position:0% anyway so it is discarded by default and 00:06:44.499 --> 00:06:47.230 align:start position:0% anyway so it is discarded by default and that<00:06:44.529> saves<00:06:45.099> a<00:06:45.279> lot<00:06:45.399> of<00:06:45.460> disk<00:06:45.789> space 00:06:47.230 --> 00:06:47.240 align:start position:0% that saves a lot of disk space 00:06:47.240 --> 00:06:51.520 align:start position:0% that saves a lot of disk space no<00:06:47.750> the<00:06:48.970> database<00:06:49.970> I'm<00:06:50.270> size<00:06:50.870> for<00:06:51.169> the<00:06:51.319> way<00:06:51.470> the 00:06:51.520 --> 00:06:51.530 align:start position:0% no the database I'm size for the way the 00:06:51.530 --> 00:06:54.580 align:start position:0% no the database I'm size for the way the swamps<00:06:52.099> that<00:06:52.160> network<00:06:52.729> is<00:06:53.599> under<00:06:54.259> five 00:06:54.580 --> 00:06:54.590 align:start position:0% swamps that network is under five 00:06:54.590 --> 00:07:01.930 align:start position:0% swamps that network is under five gigabytes<00:06:55.069> that<00:06:55.509> feature<00:06:56.509> turned<00:06:56.960> on<00:07:00.669> but<00:07:01.669> if 00:07:01.930 --> 00:07:01.940 align:start position:0% gigabytes that feature turned on but if 00:07:01.940 --> 00:07:04.150 align:start position:0% gigabytes that feature turned on but if you<00:07:02.120> need<00:07:02.300> for<00:07:02.599> both<00:07:03.139> data<00:07:03.410> you<00:07:03.740> can<00:07:03.919> still 00:07:04.150 --> 00:07:04.160 align:start position:0% you need for both data you can still 00:07:04.160 --> 00:07:08.010 align:start position:0% you need for both data you can still have<00:07:04.340> that<00:07:04.370> there<00:07:04.940> is<00:07:04.970> an<00:07:05.180> option<00:07:05.539> to<00:07:05.569> keep<00:07:06.440> it 00:07:08.010 --> 00:07:08.020 align:start position:0% have that there is an option to keep it 00:07:08.020 --> 00:07:11.140 align:start position:0% have that there is an option to keep it transaction<00:07:09.020> Jason<00:07:09.500> that's<00:07:09.710> the<00:07:09.979> API<00:07:10.520> that 00:07:11.140 --> 00:07:11.150 align:start position:0% transaction Jason that's the API that 00:07:11.150 --> 00:07:13.420 align:start position:0% transaction Jason that's the API that we've<00:07:11.389> introduced<00:07:12.199> recently<00:07:12.710> it's<00:07:12.919> an 00:07:13.420 --> 00:07:13.430 align:start position:0% we've introduced recently it's an 00:07:13.430 --> 00:07:17.050 align:start position:0% we've introduced recently it's an extension<00:07:14.919> and<00:07:15.919> it<00:07:16.039> allows<00:07:16.250> you<00:07:16.520> to<00:07:16.550> query 00:07:17.050 --> 00:07:17.060 align:start position:0% extension and it allows you to query 00:07:17.060 --> 00:07:20.710 align:start position:0% extension and it allows you to query extended<00:07:17.840> transaction<00:07:18.740> information<00:07:19.720> for 00:07:20.710 --> 00:07:20.720 align:start position:0% extended transaction information for 00:07:20.720 --> 00:07:23.080 align:start position:0% extended transaction information for example<00:07:20.810> you<00:07:21.289> can<00:07:21.470> pick<00:07:21.800> an<00:07:21.919> account<00:07:22.280> or<00:07:22.550> a<00:07:22.610> set 00:07:23.080 --> 00:07:23.090 align:start position:0% example you can pick an account or a set 00:07:23.090 --> 00:07:26.409 align:start position:0% example you can pick an account or a set of<00:07:23.120> accounts<00:07:23.659> and<00:07:23.810> you<00:07:24.020> can<00:07:24.460> query<00:07:25.460> transfers 00:07:26.409 --> 00:07:26.419 align:start position:0% of accounts and you can query transfers 00:07:26.419 --> 00:07:29.200 align:start position:0% of accounts and you can query transfers involving<00:07:27.050> these<00:07:27.560> accounts<00:07:28.069> or<00:07:28.880> what<00:07:29.090> the 00:07:29.200 --> 00:07:29.210 align:start position:0% involving these accounts or what the 00:07:29.210 --> 00:07:31.379 align:start position:0% involving these accounts or what the hell<00:07:29.389> watching<00:07:29.960> and<00:07:30.199> this<00:07:30.800> will<00:07:30.979> include 00:07:31.379 --> 00:07:31.389 align:start position:0% hell watching and this will include 00:07:31.389 --> 00:07:33.640 align:start position:0% hell watching and this will include transversed<00:07:32.389> originating<00:07:33.169> from<00:07:33.199> smart 00:07:33.640 --> 00:07:33.650 align:start position:0% transversed originating from smart 00:07:33.650 --> 00:07:36.040 align:start position:0% transversed originating from smart contracts<00:07:34.300> something<00:07:35.300> which<00:07:35.449> is<00:07:35.599> very<00:07:35.659> hard 00:07:36.040 --> 00:07:36.050 align:start position:0% contracts something which is very hard 00:07:36.050 --> 00:07:40.749 align:start position:0% contracts something which is very hard to<00:07:36.199> do<00:07:36.349> using<00:07:36.740> the<00:07:36.889> standard<00:07:37.370> RPC<00:07:38.470> and<00:07:39.520> if<00:07:40.520> you 00:07:40.749 --> 00:07:40.759 align:start position:0% to do using the standard RPC and if you 00:07:40.759 --> 00:07:42.850 align:start position:0% to do using the standard RPC and if you run<00:07:40.940> this<00:07:41.150> query<00:07:41.449> over<00:07:41.900> the<00:07:42.020> whole<00:07:42.229> work<00:07:42.560> chain 00:07:42.850 --> 00:07:42.860 align:start position:0% run this query over the whole work chain 00:07:42.860 --> 00:07:45.460 align:start position:0% run this query over the whole work chain it<00:07:42.979> will<00:07:43.099> still<00:07:43.400> work<00:07:43.520> fast<00:07:43.940> because<00:07:44.240> we<00:07:44.419> use<00:07:45.349> a 00:07:45.460 --> 00:07:45.470 align:start position:0% it will still work fast because we use a 00:07:45.470 --> 00:07:47.140 align:start position:0% it will still work fast because we use a lot<00:07:45.620> of<00:07:45.650> optimizations<00:07:46.460> to<00:07:46.550> make<00:07:46.729> them<00:07:46.909> work 00:07:47.140 --> 00:07:47.150 align:start position:0% lot of optimizations to make them work 00:07:47.150 --> 00:07:50.409 align:start position:0% lot of optimizations to make them work past<00:07:47.509> this<00:07:48.220> small<00:07:49.220> to<00:07:49.400> have<00:07:49.550> a<00:07:49.610> boom<00:07:49.880> filters 00:07:50.409 --> 00:07:50.419 align:start position:0% past this small to have a boom filters 00:07:50.419 --> 00:07:52.620 align:start position:0% past this small to have a boom filters and<00:07:50.720> so<00:07:51.169> on 00:07:52.620 --> 00:07:52.630 align:start position:0% and so on 00:07:52.630 --> 00:07:56.770 align:start position:0% and so on and<00:07:53.630> this<00:07:54.440> is<00:07:54.620> something<00:07:55.009> can<00:07:55.460> be<00:07:55.880> useful<00:07:56.539> for 00:07:56.770 --> 00:07:56.780 align:start position:0% and this is something can be useful for 00:07:56.780 --> 00:07:59.350 align:start position:0% and this is something can be useful for writing<00:07:57.680> something<00:07:58.219> like<00:07:58.400> an<00:07:58.639> action 00:07:59.350 --> 00:07:59.360 align:start position:0% writing something like an action 00:07:59.360 --> 00:08:01.270 align:start position:0% writing something like an action Explorer<00:07:59.960> or<00:08:00.229> for<00:08:00.469> any<00:08:00.590> adept<00:08:00.919> it<00:08:01.070> needs 00:08:01.270 --> 00:08:01.280 align:start position:0% Explorer or for any adept it needs 00:08:01.280 --> 00:08:06.310 align:start position:0% Explorer or for any adept it needs extended<00:08:01.909> transaction<00:08:02.449> history<00:08:05.169> okay<00:08:06.169> it's 00:08:06.310 --> 00:08:06.320 align:start position:0% extended transaction history okay it's 00:08:06.320 --> 00:08:09.270 align:start position:0% extended transaction history okay it's an<00:08:06.680> app<00:08:06.889> shot<00:08:07.190> in<00:08:07.340> this<00:08:07.550> is<00:08:07.759> something<00:08:08.690> simple 00:08:09.270 --> 00:08:09.280 align:start position:0% an app shot in this is something simple 00:08:09.280 --> 00:08:15.100 align:start position:0% an app shot in this is something simple basically<00:08:10.280> you<00:08:10.490> can<00:08:11.620> save<00:08:13.719> state<00:08:14.719> of<00:08:14.960> your 00:08:15.100 --> 00:08:15.110 align:start position:0% basically you can save state of your 00:08:15.110 --> 00:08:18.719 align:start position:0% basically you can save state of your watch<00:08:15.409> into<00:08:15.830> a<00:08:15.860> file<00:08:16.240> that<00:08:17.240> file<00:08:17.569> contains<00:08:18.050> all 00:08:18.719 --> 00:08:18.729 align:start position:0% watch into a file that file contains all 00:08:18.729 --> 00:08:21.640 align:start position:0% watch into a file that file contains all the<00:08:19.729> state<00:08:20.000> information<00:08:20.719> of<00:08:20.990> the<00:08:21.110> recent 00:08:21.640 --> 00:08:21.650 align:start position:0% the state information of the recent 00:08:21.650 --> 00:08:23.920 align:start position:0% the state information of the recent state<00:08:21.860> information<00:08:22.159> and<00:08:22.669> a<00:08:23.210> few<00:08:23.389> thousand<00:08:23.840> of 00:08:23.920 --> 00:08:23.930 align:start position:0% state information and a few thousand of 00:08:23.930 --> 00:08:27.249 align:start position:0% state information and a few thousand of the<00:08:24.080> recent<00:08:24.440> Watts<00:08:24.680> and<00:08:25.900> it<00:08:26.900> is<00:08:27.020> heavily 00:08:27.249 --> 00:08:27.259 align:start position:0% the recent Watts and it is heavily 00:08:27.259 --> 00:08:30.129 align:start position:0% the recent Watts and it is heavily compressed<00:08:27.710> so<00:08:28.039> that<00:08:28.219> the<00:08:28.780> current<00:08:29.780> snapshot 00:08:30.129 --> 00:08:30.139 align:start position:0% compressed so that the current snapshot 00:08:30.139 --> 00:08:33.579 align:start position:0% compressed so that the current snapshot for<00:08:30.590> the<00:08:30.710> way<00:08:30.860> this<00:08:31.009> homestead<00:08:31.490> is<00:08:32.270> under<00:08:32.750> 150 00:08:33.579 --> 00:08:33.589 align:start position:0% for the way this homestead is under 150 00:08:33.589 --> 00:08:36.940 align:start position:0% for the way this homestead is under 150 megabytes<00:08:34.130> and<00:08:35.140> then<00:08:36.140> restoring<00:08:36.620> from<00:08:36.800> the 00:08:36.940 --> 00:08:36.950 align:start position:0% megabytes and then restoring from the 00:08:36.950 --> 00:08:38.500 align:start position:0% megabytes and then restoring from the snapshot<00:08:37.430> takes<00:08:37.669> only<00:08:37.849> a<00:08:37.969> couple<00:08:38.180> of<00:08:38.300> minutes 00:08:38.500 --> 00:08:38.510 align:start position:0% snapshot takes only a couple of minutes 00:08:38.510 --> 00:08:42.639 align:start position:0% snapshot takes only a couple of minutes yeah<00:08:39.110> use<00:08:39.940> run<00:08:40.940> restore<00:08:41.360> command<00:08:41.659> and<00:08:41.899> in<00:08:42.079> two 00:08:42.639 --> 00:08:42.649 align:start position:0% yeah use run restore command and in two 00:08:42.649 --> 00:08:45.280 align:start position:0% yeah use run restore command and in two or<00:08:42.680> three<00:08:42.800> minutes<00:08:43.010> you're<00:08:43.279> good<00:08:43.520> to<00:08:43.640> go 00:08:45.280 --> 00:08:45.290 align:start position:0% or three minutes you're good to go 00:08:45.290 --> 00:08:47.350 align:start position:0% or three minutes you're good to go now<00:08:45.770> as<00:08:46.070> I<00:08:46.160> mentioned<00:08:46.490> it<00:08:46.790> doesn't<00:08:47.090> contain 00:08:47.350 --> 00:08:47.360 align:start position:0% now as I mentioned it doesn't contain 00:08:47.360 --> 00:08:49.600 align:start position:0% now as I mentioned it doesn't contain all<00:08:47.600> the<00:08:47.780> blocks<00:08:48.020> at<00:08:48.290> first<00:08:48.740> you<00:08:49.130> end<00:08:49.310> up<00:08:49.430> with 00:08:49.600 --> 00:08:49.610 align:start position:0% all the blocks at first you end up with 00:08:49.610 --> 00:08:51.910 align:start position:0% all the blocks at first you end up with some<00:08:50.540> of<00:08:50.690> the<00:08:50.780> blocks<00:08:51.020> missing<00:08:51.470> the<00:08:51.620> older 00:08:51.910 --> 00:08:51.920 align:start position:0% some of the blocks missing the older 00:08:51.920 --> 00:08:53.830 align:start position:0% some of the blocks missing the older blocks<00:08:52.220> but<00:08:52.820> as<00:08:52.970> soon<00:08:53.120> as<00:08:53.150> the<00:08:53.360> node<00:08:53.510> starts 00:08:53.830 --> 00:08:53.840 align:start position:0% blocks but as soon as the node starts 00:08:53.840 --> 00:08:57.280 align:start position:0% blocks but as soon as the node starts working<00:08:54.380> let's<00:08:55.250> sink<00:08:55.550> to<00:08:55.820> ready<00:08:56.150> state<00:08:56.510> it 00:08:57.280 --> 00:08:57.290 align:start position:0% working let's sink to ready state it 00:08:57.290 --> 00:08:59.440 align:start position:0% working let's sink to ready state it will<00:08:57.500> download<00:08:57.770> of<00:08:58.250> the<00:08:58.430> missing<00:08:58.880> box<00:08:59.120> in<00:08:59.360> the 00:08:59.440 --> 00:08:59.450 align:start position:0% will download of the missing box in the 00:08:59.450 --> 00:09:02.800 align:start position:0% will download of the missing box in the background<00:09:00.070> so<00:09:01.070> you<00:09:01.130> end<00:09:01.490> up<00:09:01.670> with<00:09:01.880> the<00:09:02.630> whole 00:09:02.800 --> 00:09:02.810 align:start position:0% background so you end up with the whole 00:09:02.810 --> 00:09:05.170 align:start position:0% background so you end up with the whole watching<00:09:03.410> after<00:09:03.590> a<00:09:03.740> while<00:09:03.980> so<00:09:04.790> this<00:09:04.910> doesn't 00:09:05.170 --> 00:09:05.180 align:start position:0% watching after a while so this doesn't 00:09:05.180 --> 00:09:10.030 align:start position:0% watching after a while so this doesn't compromise<00:09:05.600> the<00:09:06.020> network<00:09:06.560> security<00:09:09.040> now 00:09:10.030 --> 00:09:10.040 align:start position:0% compromise the network security now 00:09:10.040 --> 00:09:13.780 align:start position:0% compromise the network security now we'll<00:09:10.220> be<00:09:10.370> taking<00:09:10.790> this<00:09:12.160> even<00:09:13.160> further<00:09:13.370> soon 00:09:13.780 --> 00:09:13.790 align:start position:0% we'll be taking this even further soon 00:09:13.790 --> 00:09:16.600 align:start position:0% we'll be taking this even further soon by<00:09:14.450> introducing<00:09:14.780> the<00:09:15.380> snapshot<00:09:15.890> sync<00:09:16.190> or<00:09:16.430> as 00:09:16.600 --> 00:09:16.610 align:start position:0% by introducing the snapshot sync or as 00:09:16.610 --> 00:09:20.260 align:start position:0% by introducing the snapshot sync or as we<00:09:16.760> call<00:09:16.940> the<00:09:17.510> work<00:09:17.750> think<00:09:18.430> the<00:09:19.430> idea<00:09:20.000> is<00:09:20.240> that 00:09:20.260 --> 00:09:20.270 align:start position:0% we call the work think the idea is that 00:09:20.270 --> 00:09:22.630 align:start position:0% we call the work think the idea is that every<00:09:20.930> node<00:09:21.320> well<00:09:21.620> every<00:09:21.860> parity<00:09:22.280> note<00:09:22.430> for 00:09:22.630 --> 00:09:22.640 align:start position:0% every node well every parity note for 00:09:22.640 --> 00:09:26.140 align:start position:0% every node well every parity note for now<00:09:22.780> on<00:09:23.780> the<00:09:24.140> network<00:09:24.500> will<00:09:25.280> take<00:09:25.460> a<00:09:25.490> periodic 00:09:26.140 --> 00:09:26.150 align:start position:0% now on the network will take a periodic 00:09:26.150 --> 00:09:28.270 align:start position:0% now on the network will take a periodic snapshot<00:09:26.660> every<00:09:27.020> eight<00:09:27.470> ten<00:09:27.650> thousand<00:09:28.040> walks 00:09:28.270 --> 00:09:28.280 align:start position:0% snapshot every eight ten thousand walks 00:09:28.280 --> 00:09:31.780 align:start position:0% snapshot every eight ten thousand walks and<00:09:29.320> that<00:09:30.320> snapshot<00:09:30.620> is<00:09:30.980> the<00:09:31.100> same<00:09:31.310> across<00:09:31.550> all 00:09:31.780 --> 00:09:31.790 align:start position:0% and that snapshot is the same across all 00:09:31.790 --> 00:09:35.140 align:start position:0% and that snapshot is the same across all nodes<00:09:32.060> and<00:09:32.860> the<00:09:33.860> nodes<00:09:34.010> that<00:09:34.190> start<00:09:34.610> syncing 00:09:35.140 --> 00:09:35.150 align:start position:0% nodes and the nodes that start syncing 00:09:35.150 --> 00:09:37.690 align:start position:0% nodes and the nodes that start syncing and<00:09:35.570> download<00:09:36.350> these<00:09:36.560> snapshots<00:09:36.890> from<00:09:37.460> other 00:09:37.690 --> 00:09:37.700 align:start position:0% and download these snapshots from other 00:09:37.700 --> 00:09:43.840 align:start position:0% and download these snapshots from other peers<00:09:38.090> and<00:09:39.400> sync<00:09:40.400> from<00:09:40.580> them<00:09:42.070> so<00:09:43.070> yeah 00:09:43.840 --> 00:09:43.850 align:start position:0% peers and sync from them so yeah 00:09:43.850 --> 00:09:46.540 align:start position:0% peers and sync from them so yeah basically<00:09:44.090> you<00:09:44.750> start<00:09:45.320> from<00:09:45.500> stretch<00:09:45.860> and<00:09:46.160> in 00:09:46.540 --> 00:09:46.550 align:start position:0% basically you start from stretch and in 00:09:46.550 --> 00:09:48.400 align:start position:0% basically you start from stretch and in two<00:09:46.880> or<00:09:46.910> three<00:09:47.180> minutes<00:09:47.510> on<00:09:47.660> a<00:09:47.690> fast<00:09:47.990> Network 00:09:48.400 --> 00:09:48.410 align:start position:0% two or three minutes on a fast Network 00:09:48.410 --> 00:09:50.530 align:start position:0% two or three minutes on a fast Network you<00:09:48.650> you<00:09:49.430> can<00:09:49.580> start<00:09:49.820> working<00:09:50.240> with<00:09:50.480> the 00:09:50.530 --> 00:09:50.540 align:start position:0% you you can start working with the 00:09:50.540 --> 00:09:55.350 align:start position:0% you you can start working with the theorem<00:09:50.870> doing<00:09:51.710> transactions<00:09:52.340> and<00:09:52.550> all<00:09:52.640> that 00:09:55.350 --> 00:09:55.360 align:start position:0% 00:09:55.360 --> 00:09:56.590 align:start position:0% okay 00:09:56.590 --> 00:09:56.600 align:start position:0% okay 00:09:56.600 --> 00:09:59.260 align:start position:0% okay private<00:09:57.200> chains<00:09:57.760> private<00:09:58.760> chains<00:09:59.060> are 00:09:59.260 --> 00:09:59.270 align:start position:0% private chains private chains are 00:09:59.270 --> 00:10:02.230 align:start position:0% private chains private chains are extremely<00:09:59.750> easy<00:09:59.780> with<00:10:00.140> parity<00:10:00.880> all<00:10:01.880> you<00:10:02.060> need 00:10:02.230 --> 00:10:02.240 align:start position:0% extremely easy with parity all you need 00:10:02.240 --> 00:10:03.370 align:start position:0% extremely easy with parity all you need is<00:10:02.360> one<00:10:02.810> files 00:10:03.370 --> 00:10:03.380 align:start position:0% is one files 00:10:03.380 --> 00:10:05.770 align:start position:0% is one files it's<00:10:04.070> a<00:10:04.130> JSON<00:10:04.580> file<00:10:04.790> that<00:10:04.820> lists<00:10:05.420> all<00:10:05.570> the 00:10:05.770 --> 00:10:05.780 align:start position:0% it's a JSON file that lists all the 00:10:05.780 --> 00:10:08.290 align:start position:0% it's a JSON file that lists all the private<00:10:06.200> chained<00:10:06.800> specification<00:10:07.430> we<00:10:08.120> have<00:10:08.270> a 00:10:08.290 --> 00:10:08.300 align:start position:0% private chained specification we have a 00:10:08.300 --> 00:10:13.420 align:start position:0% private chained specification we have a few<00:10:08.540> examples<00:10:09.610> basically<00:10:10.610> it<00:10:10.760> contains<00:10:11.210> of<00:10:12.430> it 00:10:13.420 --> 00:10:13.430 align:start position:0% few examples basically it contains of it 00:10:13.430 --> 00:10:15.670 align:start position:0% few examples basically it contains of it all<00:10:13.670> you<00:10:13.820> need<00:10:13.970> so<00:10:14.270> theorem<00:10:15.170> protocol 00:10:15.670 --> 00:10:15.680 align:start position:0% all you need so theorem protocol 00:10:15.680 --> 00:10:19.110 align:start position:0% all you need so theorem protocol parameters<00:10:15.920> such<00:10:16.490> as<00:10:16.520> the<00:10:16.910> target<00:10:17.360> walk<00:10:17.600> time 00:10:19.110 --> 00:10:19.120 align:start position:0% parameters such as the target walk time 00:10:19.120 --> 00:10:21.730 align:start position:0% parameters such as the target walk time Genesis<00:10:20.120> board<00:10:20.360> data<00:10:20.630> network<00:10:21.560> parameters 00:10:21.730 --> 00:10:21.740 align:start position:0% Genesis board data network parameters 00:10:21.740 --> 00:10:24.280 align:start position:0% Genesis board data network parameters such<00:10:22.310> as<00:10:22.340> network<00:10:22.880> ID<00:10:23.120> or<00:10:23.540> a<00:10:23.600> list<00:10:23.900> of<00:10:24.080> good 00:10:24.280 --> 00:10:24.290 align:start position:0% such as network ID or a list of good 00:10:24.290 --> 00:10:25.020 align:start position:0% such as network ID or a list of good nodes 00:10:25.020 --> 00:10:25.030 align:start position:0% nodes 00:10:25.030 --> 00:10:28.000 align:start position:0% nodes you<00:10:26.030> can<00:10:26.210> even<00:10:26.330> replace<00:10:26.900> proof<00:10:27.320> of<00:10:27.470> work<00:10:27.680> with 00:10:28.000 --> 00:10:28.010 align:start position:0% you can even replace proof of work with 00:10:28.010 --> 00:10:30.520 align:start position:0% you can even replace proof of work with proof<00:10:28.460> of<00:10:28.610> authority<00:10:29.150> which<00:10:29.810> is<00:10:29.960> basically<00:10:30.380> a 00:10:30.520 --> 00:10:30.530 align:start position:0% proof of authority which is basically a 00:10:30.530 --> 00:10:32.410 align:start position:0% proof of authority which is basically a list<00:10:30.770> of<00:10:30.980> notes<00:10:31.190> that<00:10:31.370> are<00:10:31.670> allowed<00:10:32.000> to 00:10:32.410 --> 00:10:32.420 align:start position:0% list of notes that are allowed to 00:10:32.420 --> 00:10:36.390 align:start position:0% list of notes that are allowed to produce<00:10:33.110> walks<00:10:33.650> without<00:10:34.040> doing<00:10:34.670> any<00:10:34.880> mining 00:10:36.390 --> 00:10:36.400 align:start position:0% produce walks without doing any mining 00:10:36.400 --> 00:10:39.670 align:start position:0% produce walks without doing any mining and<00:10:37.690> something<00:10:38.690> which<00:10:38.870> is<00:10:38.990> not<00:10:39.140> here<00:10:39.440> but 00:10:39.670 --> 00:10:39.680 align:start position:0% and something which is not here but 00:10:39.680 --> 00:10:41.860 align:start position:0% and something which is not here but which<00:10:40.220> something<00:10:40.790> that<00:10:40.970> we'll<00:10:41.240> be<00:10:41.600> adding 00:10:41.860 --> 00:10:41.870 align:start position:0% which something that we'll be adding 00:10:41.870 --> 00:10:46.360 align:start position:0% which something that we'll be adding soon<00:10:42.320> is<00:10:43.100> the<00:10:43.340> ability<00:10:43.790> to<00:10:43.820> include<00:10:45.370> building 00:10:46.360 --> 00:10:46.370 align:start position:0% soon is the ability to include building 00:10:46.370 --> 00:10:48.460 align:start position:0% soon is the ability to include building contracts<00:10:46.970> written<00:10:47.420> in<00:10:47.720> native<00:10:48.080> languages 00:10:48.460 --> 00:10:48.470 align:start position:0% contracts written in native languages 00:10:48.470 --> 00:10:50.970 align:start position:0% contracts written in native languages such<00:10:48.770> as<00:10:48.800> C<00:10:49.190> suppose<00:10:49.580> first<00:10:49.880> for<00:10:50.150> rust 00:10:50.970 --> 00:10:50.980 align:start position:0% such as C suppose first for rust 00:10:50.980 --> 00:10:54.070 align:start position:0% such as C suppose first for rust basically<00:10:51.980> you<00:10:52.070> just<00:10:52.510> declare<00:10:53.510> a<00:10:53.540> dynamic 00:10:54.070 --> 00:10:54.080 align:start position:0% basically you just declare a dynamic 00:10:54.080 --> 00:10:56.870 align:start position:0% basically you just declare a dynamic library<00:10:54.230> and<00:10:54.770> an<00:10:54.980> entry<00:10:55.250> point<00:10:55.280> into<00:10:55.670> that 00:10:56.870 --> 00:10:56.880 align:start position:0% library and an entry point into that 00:10:56.880 --> 00:10:59.270 align:start position:0% library and an entry point into that paraty<00:10:57.330> we'll<00:10:57.480> call<00:10:57.690> it<00:10:57.810> when<00:10:58.260> it's<00:10:58.890> time<00:10:59.070> to 00:10:59.270 --> 00:10:59.280 align:start position:0% paraty we'll call it when it's time to 00:10:59.280 --> 00:11:08.570 align:start position:0% paraty we'll call it when it's time to have<00:10:59.880> a<00:10:59.910> smart<00:11:00.210> contract<00:11:06.590> so<00:11:07.590> there<00:11:07.770> are<00:11:07.920> a<00:11:08.190> lot 00:11:08.570 --> 00:11:08.580 align:start position:0% have a smart contract so there are a lot 00:11:08.580 --> 00:11:13.400 align:start position:0% have a smart contract so there are a lot of<00:11:08.750> more<00:11:09.750> smaller<00:11:10.170> features<00:11:10.880> but<00:11:11.880> I'm<00:11:12.870> gonna 00:11:13.400 --> 00:11:13.410 align:start position:0% of more smaller features but I'm gonna 00:11:13.410 --> 00:11:17.380 align:start position:0% of more smaller features but I'm gonna focus<00:11:13.650> know<00:11:14.360> what's<00:11:15.360> about<00:11:15.510> to<00:11:15.660> come 00:11:17.380 --> 00:11:17.390 align:start position:0% focus know what's about to come 00:11:17.390 --> 00:11:20.000 align:start position:0% focus know what's about to come so<00:11:18.390> the<00:11:18.540> private<00:11:18.750> proof<00:11:19.200> of<00:11:19.320> a<00:11:19.410> forest<00:11:19.680> change 00:11:20.000 --> 00:11:20.010 align:start position:0% so the private proof of a forest change 00:11:20.010 --> 00:11:21.350 align:start position:0% so the private proof of a forest change that<00:11:20.130> have<00:11:20.250> mentioned<00:11:20.670> earlier<00:11:20.790> they're 00:11:21.350 --> 00:11:21.360 align:start position:0% that have mentioned earlier they're 00:11:21.360 --> 00:11:23.840 align:start position:0% that have mentioned earlier they're quite<00:11:21.630> basic<00:11:22.020> at<00:11:22.140> the<00:11:22.230> moment<00:11:22.590> we<00:11:23.580> want<00:11:23.760> to 00:11:23.840 --> 00:11:23.850 align:start position:0% quite basic at the moment we want to 00:11:23.850 --> 00:11:26.540 align:start position:0% quite basic at the moment we want to improve<00:11:24.060> them<00:11:24.300> by<00:11:24.530> making<00:11:25.530> them<00:11:25.830> Byzantine 00:11:26.540 --> 00:11:26.550 align:start position:0% improve them by making them Byzantine 00:11:26.550 --> 00:11:29.360 align:start position:0% improve them by making them Byzantine fault<00:11:26.850> tolerant<00:11:27.470> so<00:11:28.470> that<00:11:28.710> you<00:11:28.800> can<00:11:29.040> have<00:11:29.340> a 00:11:29.360 --> 00:11:29.370 align:start position:0% fault tolerant so that you can have a 00:11:29.370 --> 00:11:33.230 align:start position:0% fault tolerant so that you can have a full-blown<00:11:30.120> industrial<00:11:31.020> grade<00:11:32.240> permission 00:11:33.230 --> 00:11:33.240 align:start position:0% full-blown industrial grade permission 00:11:33.240 --> 00:11:37.360 align:start position:0% full-blown industrial grade permission box<00:11:33.540> in<00:11:33.780> solution<00:11:34.230> build<00:11:34.440> on<00:11:34.560> top<00:11:34.680> of<00:11:34.740> that 00:11:37.360 --> 00:11:37.370 align:start position:0% 00:11:37.370 --> 00:11:39.740 align:start position:0% stratum<00:11:38.370> protocol<00:11:38.790> something<00:11:39.180> requested<00:11:39.630> by 00:11:39.740 --> 00:11:39.750 align:start position:0% stratum protocol something requested by 00:11:39.750 --> 00:11:41.900 align:start position:0% stratum protocol something requested by our<00:11:39.780> a<00:11:40.020> miner's<00:11:40.440> community<00:11:40.980> also<00:11:41.310> coming<00:11:41.700> soon 00:11:41.900 --> 00:11:41.910 align:start position:0% our a miner's community also coming soon 00:11:41.910 --> 00:11:46.430 align:start position:0% our a miner's community also coming soon this<00:11:42.750> is<00:11:42.810> the<00:11:42.990> product<00:11:43.470> code<00:11:43.560> to<00:11:43.740> push<00:11:45.440> what 00:11:46.430 --> 00:11:46.440 align:start position:0% this is the product code to push what 00:11:46.440 --> 00:11:50.110 align:start position:0% this is the product code to push what work<00:11:46.830> notifications<00:11:47.640> to<00:11:47.790> minor<00:11:48.030> over<00:11:48.480> TCP 00:11:50.110 --> 00:11:50.120 align:start position:0% work notifications to minor over TCP 00:11:50.120 --> 00:11:53.570 align:start position:0% work notifications to minor over TCP wide<00:11:51.120> find<00:11:51.510> so<00:11:51.870> initial<00:11:52.620> work<00:11:52.860> has<00:11:53.130> started<00:11:53.370> on 00:11:53.570 --> 00:11:53.580 align:start position:0% wide find so initial work has started on 00:11:53.580 --> 00:11:55.550 align:start position:0% wide find so initial work has started on that<00:11:53.820> and<00:11:54.090> it<00:11:54.360> is<00:11:54.510> coming<00:11:54.750> out<00:11:54.960> eventually 00:11:55.550 --> 00:11:55.560 align:start position:0% that and it is coming out eventually 00:11:55.560 --> 00:11:58.220 align:start position:0% that and it is coming out eventually and<00:11:55.820> of<00:11:56.820> course<00:11:57.060> metropolis<00:11:57.570> transition<00:11:58.020> as 00:11:58.220 --> 00:11:58.230 align:start position:0% and of course metropolis transition as 00:11:58.230 --> 00:12:00.020 align:start position:0% and of course metropolis transition as soon<00:11:58.500> as<00:11:58.620> this<00:11:58.800> specification<00:11:59.340> is<00:11:59.790> ready 00:12:00.020 --> 00:12:00.030 align:start position:0% soon as this specification is ready 00:12:00.030 --> 00:12:02.540 align:start position:0% soon as this specification is ready we'll<00:12:00.870> start<00:12:00.990> working<00:12:01.470> on<00:12:01.680> it<00:12:01.830> and<00:12:02.040> be<00:12:02.310> sure<00:12:02.520> to 00:12:02.540 --> 00:12:02.550 align:start position:0% we'll start working on it and be sure to 00:12:02.550 --> 00:12:10.580 align:start position:0% we'll start working on it and be sure to release<00:12:02.940> it<00:12:03.120> as<00:12:03.300> soon<00:12:03.480> as<00:12:03.540> possible<00:12:09.380> yeah<00:12:10.380> this 00:12:10.580 --> 00:12:10.590 align:start position:0% release it as soon as possible yeah this 00:12:10.590 --> 00:12:12.410 align:start position:0% release it as soon as possible yeah this is<00:12:10.740> para<00:12:10.980> team<00:12:11.190> we<00:12:11.730> encourage<00:12:12.090> you<00:12:12.180> to<00:12:12.300> go 00:12:12.410 --> 00:12:12.420 align:start position:0% is para team we encourage you to go 00:12:12.420 --> 00:12:14.630 align:start position:0% is para team we encourage you to go check<00:12:12.480> it<00:12:12.780> out<00:12:12.870> check<00:12:13.290> out<00:12:13.380> our<00:12:13.590> wiki<00:12:14.070> if 00:12:14.630 --> 00:12:14.640 align:start position:0% check it out check out our wiki if 00:12:14.640 --> 00:12:16.460 align:start position:0% check it out check out our wiki if there's<00:12:15.120> features<00:12:15.870> that<00:12:15.990> you<00:12:16.170> might<00:12:16.290> be 00:12:16.460 --> 00:12:16.470 align:start position:0% there's features that you might be 00:12:16.470 --> 00:12:19.730 align:start position:0% there's features that you might be missing<00:12:16.830> in<00:12:17.040> other<00:12:17.310> clients<00:12:17.820> and<00:12:18.470> if<00:12:19.470> you<00:12:19.590> have 00:12:19.730 --> 00:12:19.740 align:start position:0% missing in other clients and if you have 00:12:19.740 --> 00:12:21.560 align:start position:0% missing in other clients and if you have any<00:12:19.890> questions<00:12:20.430> join<00:12:20.700> our<00:12:20.880> discussion<00:12:21.030> and 00:12:21.560 --> 00:12:21.570 align:start position:0% any questions join our discussion and 00:12:21.570 --> 00:12:25.540 align:start position:0% any questions join our discussion and guiter<00:12:21.750> will<00:12:22.080> be<00:12:22.260> happy<00:12:23.190> to<00:12:23.370> answer<00:12:23.760> them<00:12:24.420> all 00:12:25.540 --> 00:12:25.550 align:start position:0% guiter will be happy to answer them all 00:12:25.550 --> 00:12:30.960 align:start position:0% guiter will be happy to answer them all yeah<00:12:26.600> thank<00:12:27.600> you 00:12:30.960 --> 00:12:30.970 align:start position:0% 00:12:30.970 --> 00:12:34.230 align:start position:0% thank<00:12:31.300> you<00:12:31.480> very<00:12:31.540> much<00:12:31.840> agony