WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:03.710 align:start position:0% yeah<00:00:00.480> hello<00:00:01.469> everyone<00:00:01.800> i'm<00:00:02.070> robert<00:00:02.879> i<00:00:03.179> worked 00:00:03.710 --> 00:00:03.720 align:start position:0% yeah hello everyone i'm robert i worked 00:00:03.720 --> 00:00:05.869 align:start position:0% yeah hello everyone i'm robert i worked primarily<00:00:04.080> on<00:00:04.529> a<00:00:04.560> project<00:00:05.220> called<00:00:05.250> polka<00:00:05.670> dot 00:00:05.869 --> 00:00:05.879 align:start position:0% primarily on a project called polka dot 00:00:05.879 --> 00:00:08.919 align:start position:0% primarily on a project called polka dot but<00:00:06.120> i<00:00:06.150> work<00:00:06.720> a<00:00:06.870> lot<00:00:07.020> with<00:00:07.849> parody 00:00:08.919 --> 00:00:08.929 align:start position:0% but i work a lot with parody 00:00:08.929 --> 00:00:10.940 align:start position:0% but i work a lot with parody technologies<00:00:09.929> i'll<00:00:10.260> be<00:00:10.380> talking<00:00:10.530> today<00:00:10.830> about 00:00:10.940 --> 00:00:10.950 align:start position:0% technologies i'll be talking today about 00:00:10.950 --> 00:00:14.870 align:start position:0% technologies i'll be talking today about parity<00:00:11.490> technologies<00:00:12.030> work<00:00:12.330> on<00:00:13.190> on<00:00:14.190> not 00:00:14.870 --> 00:00:14.880 align:start position:0% parity technologies work on on not 00:00:14.880 --> 00:00:20.750 align:start position:0% parity technologies work on on not jasper<00:00:15.450> very<00:00:16.049> sorry<00:00:16.410> on<00:00:16.710> serenity<00:00:19.760> basically 00:00:20.750 --> 00:00:20.760 align:start position:0% jasper very sorry on serenity basically 00:00:20.760 --> 00:00:22.939 align:start position:0% jasper very sorry on serenity basically what<00:00:21.090> we've<00:00:21.240> been<00:00:21.390> doing<00:00:21.689> so<00:00:21.930> far<00:00:21.960> we're 00:00:22.939 --> 00:00:22.949 align:start position:0% what we've been doing so far we're 00:00:22.949 --> 00:00:24.170 align:start position:0% what we've been doing so far we're building<00:00:23.220> it<00:00:23.310> on<00:00:23.340> this<00:00:23.519> platform<00:00:23.760> called 00:00:24.170 --> 00:00:24.180 align:start position:0% building it on this platform called 00:00:24.180 --> 00:00:26.000 align:start position:0% building it on this platform called substrate<00:00:24.689> first<00:00:25.019> i'm<00:00:25.170> gonna<00:00:25.260> go<00:00:25.470> into<00:00:25.769> what 00:00:26.000 --> 00:00:26.010 align:start position:0% substrate first i'm gonna go into what 00:00:26.010 --> 00:00:28.429 align:start position:0% substrate first i'm gonna go into what that<00:00:26.189> is<00:00:26.400> a<00:00:26.640> little<00:00:27.090> bit<00:00:27.240> of<00:00:27.330> background<00:00:27.510> on<00:00:27.990> on 00:00:28.429 --> 00:00:28.439 align:start position:0% that is a little bit of background on on 00:00:28.439 --> 00:00:31.339 align:start position:0% that is a little bit of background on on sharding<00:00:29.340> on<00:00:29.580> casper<00:00:30.090> on<00:00:30.240> serenity 00:00:31.339 --> 00:00:31.349 align:start position:0% sharding on casper on serenity 00:00:31.349 --> 00:00:33.920 align:start position:0% sharding on casper on serenity Vitalik<00:00:32.130> and<00:00:32.340> justin<00:00:32.880> and<00:00:33.390> the<00:00:33.480> others<00:00:33.690> can 00:00:33.920 --> 00:00:33.930 align:start position:0% Vitalik and justin and the others can 00:00:33.930 --> 00:00:35.660 align:start position:0% Vitalik and justin and the others can explain<00:00:34.469> that<00:00:34.590> way<00:00:34.739> better<00:00:34.950> than<00:00:35.130> I<00:00:35.250> can<00:00:35.460> so 00:00:35.660 --> 00:00:35.670 align:start position:0% explain that way better than I can so 00:00:35.670 --> 00:00:36.979 align:start position:0% explain that way better than I can so I'm<00:00:35.790> sure<00:00:35.969> you've<00:00:36.120> seen<00:00:36.180> their<00:00:36.570> talks<00:00:36.780> as<00:00:36.960> well 00:00:36.979 --> 00:00:36.989 align:start position:0% I'm sure you've seen their talks as well 00:00:36.989 --> 00:00:38.959 align:start position:0% I'm sure you've seen their talks as well and<00:00:37.710> then<00:00:37.860> basically<00:00:38.160> dive<00:00:38.370> into<00:00:38.579> what<00:00:38.820> we're 00:00:38.959 --> 00:00:38.969 align:start position:0% and then basically dive into what we're 00:00:38.969 --> 00:00:40.940 align:start position:0% and then basically dive into what we're what<00:00:39.270> we've<00:00:39.450> been<00:00:39.750> doing<00:00:40.170> what<00:00:40.379> we<00:00:40.469> are<00:00:40.649> doing 00:00:40.940 --> 00:00:40.950 align:start position:0% what we've been doing what we are doing 00:00:40.950 --> 00:00:42.770 align:start position:0% what we've been doing what we are doing in<00:00:41.190> the<00:00:41.280> future<00:00:41.610> and<00:00:42.300> what<00:00:42.450> we're<00:00:42.570> doing<00:00:42.600> now 00:00:42.770 --> 00:00:42.780 align:start position:0% in the future and what we're doing now 00:00:42.780 --> 00:00:47.270 align:start position:0% in the future and what we're doing now on<00:00:43.370> building<00:00:44.370> out<00:00:44.550> all<00:00:44.820> of<00:00:44.850> that<00:00:45.860> so<00:00:46.860> a<00:00:46.890> lot<00:00:47.219> of 00:00:47.270 --> 00:00:47.280 align:start position:0% on building out all of that so a lot of 00:00:47.280 --> 00:00:48.860 align:start position:0% on building out all of that so a lot of you<00:00:47.460> might<00:00:47.640> have<00:00:47.670> heard<00:00:47.789> recently<00:00:48.629> there's 00:00:48.860 --> 00:00:48.870 align:start position:0% you might have heard recently there's 00:00:48.870 --> 00:00:52.760 align:start position:0% you might have heard recently there's been<00:00:48.960> some<00:00:49.110> buzz<00:00:49.800> about<00:00:50.070> parody<00:00:50.879> substrate<00:00:51.770> so 00:00:52.760 --> 00:00:52.770 align:start position:0% been some buzz about parody substrate so 00:00:52.770 --> 00:00:54.889 align:start position:0% been some buzz about parody substrate so what<00:00:53.010> parody<00:00:53.460> fundamentally<00:00:54.300> is<00:00:54.539> is<00:00:54.870> a 00:00:54.889 --> 00:00:54.899 align:start position:0% what parody fundamentally is is a 00:00:54.899 --> 00:00:57.709 align:start position:0% what parody fundamentally is is a blockchain<00:00:55.670> development<00:00:56.670> outfit<00:00:57.120> like<00:00:57.360> we're 00:00:57.709 --> 00:00:57.719 align:start position:0% blockchain development outfit like we're 00:00:57.719 --> 00:00:59.360 align:start position:0% blockchain development outfit like we're we're<00:00:58.050> a<00:00:58.109> group<00:00:58.320> that's<00:00:58.559> built<00:00:58.800> a<00:00:58.980> lot<00:00:59.190> of 00:00:59.360 --> 00:00:59.370 align:start position:0% we're a group that's built a lot of 00:00:59.370 --> 00:01:00.680 align:start position:0% we're a group that's built a lot of different<00:00:59.699> nodes<00:00:59.850> for<00:01:00.120> a<00:01:00.149> lot<00:01:00.270> of<00:01:00.390> different 00:01:00.680 --> 00:01:00.690 align:start position:0% different nodes for a lot of different 00:01:00.690 --> 00:01:02.779 align:start position:0% different nodes for a lot of different chains<00:01:00.899> so<00:01:01.260> the<00:01:01.920> best-known<00:01:02.340> one<00:01:02.520> is<00:01:02.670> the 00:01:02.779 --> 00:01:02.789 align:start position:0% chains so the best-known one is the 00:01:02.789 --> 00:01:06.500 align:start position:0% chains so the best-known one is the parody<00:01:03.149> etherium<00:01:03.539> node<00:01:03.719> it's<00:01:03.899> the<00:01:05.119> other<00:01:06.119> than 00:01:06.500 --> 00:01:06.510 align:start position:0% parody etherium node it's the other than 00:01:06.510 --> 00:01:08.270 align:start position:0% parody etherium node it's the other than the<00:01:06.630> go<00:01:06.960> aetherium<00:01:07.380> client<00:01:07.770> it's<00:01:07.890> the<00:01:08.070> most 00:01:08.270 --> 00:01:08.280 align:start position:0% the go aetherium client it's the most 00:01:08.280 --> 00:01:11.600 align:start position:0% the go aetherium client it's the most widely<00:01:08.970> used<00:01:09.710> aetherium<00:01:10.710> node<00:01:10.920> it's<00:01:11.159> used<00:01:11.369> by 00:01:11.600 --> 00:01:11.610 align:start position:0% widely used aetherium node it's used by 00:01:11.610 --> 00:01:14.090 align:start position:0% widely used aetherium node it's used by infrastructure<00:01:12.450> it's<00:01:12.689> used<00:01:12.960> as<00:01:13.560> a<00:01:13.860> light 00:01:14.090 --> 00:01:14.100 align:start position:0% infrastructure it's used as a light 00:01:14.100 --> 00:01:15.320 align:start position:0% infrastructure it's used as a light client<00:01:14.580> it's<00:01:14.700> used<00:01:14.850> in<00:01:14.939> a<00:01:15.000> lot<00:01:15.119> of<00:01:15.150> different 00:01:15.320 --> 00:01:15.330 align:start position:0% client it's used in a lot of different 00:01:15.330 --> 00:01:17.810 align:start position:0% client it's used in a lot of different ways<00:01:15.600> it's<00:01:16.560> not<00:01:16.650> just<00:01:17.009> in<00:01:17.130> a<00:01:17.189> theorem<00:01:17.460> node<00:01:17.640> it 00:01:17.810 --> 00:01:17.820 align:start position:0% ways it's not just in a theorem node it 00:01:17.820 --> 00:01:18.770 align:start position:0% ways it's not just in a theorem node it supports<00:01:18.119> all<00:01:18.240> kinds<00:01:18.570> of<00:01:18.600> different 00:01:18.770 --> 00:01:18.780 align:start position:0% supports all kinds of different 00:01:18.780 --> 00:01:20.210 align:start position:0% supports all kinds of different consensus<00:01:19.290> algorithms<00:01:19.710> and<00:01:19.799> stuff<00:01:19.950> as<00:01:20.070> well 00:01:20.210 --> 00:01:20.220 align:start position:0% consensus algorithms and stuff as well 00:01:20.220 --> 00:01:23.380 align:start position:0% consensus algorithms and stuff as well we've<00:01:21.030> done<00:01:21.330> a<00:01:21.689> Bitcoin<00:01:22.320> implementation 00:01:23.380 --> 00:01:23.390 align:start position:0% we've done a Bitcoin implementation 00:01:23.390 --> 00:01:25.609 align:start position:0% we've done a Bitcoin implementation recently<00:01:24.390> announced<00:01:24.840> is<00:01:24.930> that<00:01:25.080> this<00:01:25.200> is<00:01:25.380> soon 00:01:25.609 --> 00:01:25.619 align:start position:0% recently announced is that this is soon 00:01:25.619 --> 00:01:28.190 align:start position:0% recently announced is that this is soon going<00:01:25.890> to<00:01:25.979> be<00:01:26.130> also<00:01:26.630> modified<00:01:27.630> somewhat<00:01:27.960> into 00:01:28.190 --> 00:01:28.200 align:start position:0% going to be also modified somewhat into 00:01:28.200 --> 00:01:30.289 align:start position:0% going to be also modified somewhat into the<00:01:28.439> first<00:01:28.860> alternative<00:01:29.610> Z<00:01:30.090> cash 00:01:30.289 --> 00:01:30.299 align:start position:0% the first alternative Z cash 00:01:30.299 --> 00:01:31.520 align:start position:0% the first alternative Z cash implementation<00:01:30.930> so<00:01:31.079> we're<00:01:31.229> we're<00:01:31.500> a 00:01:31.520 --> 00:01:31.530 align:start position:0% implementation so we're we're a 00:01:31.530 --> 00:01:34.880 align:start position:0% implementation so we're we're a blockchain<00:01:31.850> Development<00:01:32.850> outfit<00:01:33.180> and<00:01:34.140> at 00:01:34.880 --> 00:01:34.890 align:start position:0% blockchain Development outfit and at 00:01:34.890 --> 00:01:36.350 align:start position:0% blockchain Development outfit and at some<00:01:35.130> point<00:01:35.340> we<00:01:35.430> realize<00:01:35.700> like<00:01:36.000> we've<00:01:36.210> been 00:01:36.350 --> 00:01:36.360 align:start position:0% some point we realize like we've been 00:01:36.360 --> 00:01:37.819 align:start position:0% some point we realize like we've been writing<00:01:36.600> these<00:01:36.689> nodes<00:01:36.990> and<00:01:37.409> we're 00:01:37.819 --> 00:01:37.829 align:start position:0% writing these nodes and we're 00:01:37.829 --> 00:01:39.920 align:start position:0% writing these nodes and we're duplicating<00:01:38.790> a<00:01:38.850> lot<00:01:39.000> of<00:01:39.150> the<00:01:39.240> same<00:01:39.420> work<00:01:39.689> over 00:01:39.920 --> 00:01:39.930 align:start position:0% duplicating a lot of the same work over 00:01:39.930 --> 00:01:42.280 align:start position:0% duplicating a lot of the same work over and<00:01:40.200> over<00:01:40.439> again<00:01:40.640> so<00:01:41.640> stuff<00:01:41.880> like 00:01:42.280 --> 00:01:42.290 align:start position:0% and over again so stuff like 00:01:42.290 --> 00:01:45.010 align:start position:0% and over again so stuff like synchronization<00:01:43.290> peer-to-peer<00:01:44.009> networking 00:01:45.010 --> 00:01:45.020 align:start position:0% synchronization peer-to-peer networking 00:01:45.020 --> 00:01:48.950 align:start position:0% synchronization peer-to-peer networking database<00:01:46.020> Merkle<00:01:46.860> trees<00:01:47.450> light<00:01:48.450> client 00:01:48.950 --> 00:01:48.960 align:start position:0% database Merkle trees light client 00:01:48.960 --> 00:01:50.569 align:start position:0% database Merkle trees light client algorithms<00:01:49.470> that<00:01:49.799> kind<00:01:50.009> of<00:01:50.100> thing<00:01:50.310> it's 00:01:50.569 --> 00:01:50.579 align:start position:0% algorithms that kind of thing it's 00:01:50.579 --> 00:01:51.830 align:start position:0% algorithms that kind of thing it's actually<00:01:50.850> a<00:01:50.880> lot<00:01:51.090> of<00:01:51.119> infrastructure<00:01:51.750> that 00:01:51.830 --> 00:01:51.840 align:start position:0% actually a lot of infrastructure that 00:01:51.840 --> 00:01:53.780 align:start position:0% actually a lot of infrastructure that you<00:01:51.930> have<00:01:52.049> to<00:01:52.140> build<00:01:52.320> around<00:01:52.579> ultimately<00:01:53.579> what 00:01:53.780 --> 00:01:53.790 align:start position:0% you have to build around ultimately what 00:01:53.790 --> 00:01:55.429 align:start position:0% you have to build around ultimately what you<00:01:53.880> really<00:01:54.030> care<00:01:54.299> about<00:01:54.360> is<00:01:54.750> a<00:01:54.780> blockchain 00:01:55.429 --> 00:01:55.439 align:start position:0% you really care about is a blockchain 00:01:55.439 --> 00:01:57.319 align:start position:0% you really care about is a blockchain developer<00:01:56.100> which<00:01:56.250> is<00:01:56.460> the<00:01:56.610> state<00:01:56.820> transition 00:01:57.319 --> 00:01:57.329 align:start position:0% developer which is the state transition 00:01:57.329 --> 00:01:59.060 align:start position:0% developer which is the state transition system<00:01:57.360> that<00:01:57.780> you're<00:01:57.899> putting<00:01:58.049> together<00:01:58.200> so 00:01:59.060 --> 00:01:59.070 align:start position:0% system that you're putting together so 00:01:59.070 --> 00:02:00.830 align:start position:0% system that you're putting together so that's<00:01:59.219> basically<00:01:59.549> what<00:01:59.700> parody<00:02:00.479> substrate 00:02:00.830 --> 00:02:00.840 align:start position:0% that's basically what parody substrate 00:02:00.840 --> 00:02:02.389 align:start position:0% that's basically what parody substrate is<00:02:00.960> it's<00:02:01.259> something<00:02:01.560> like<00:02:01.710> a<00:02:01.770> blockchain<00:02:02.040> the 00:02:02.389 --> 00:02:02.399 align:start position:0% is it's something like a blockchain the 00:02:02.399 --> 00:02:05.569 align:start position:0% is it's something like a blockchain the box<00:02:02.610> that<00:02:02.820> you<00:02:02.880> can<00:02:03.740> build<00:02:04.740> a<00:02:04.890> chain<00:02:05.040> with<00:02:05.219> it's 00:02:05.569 --> 00:02:05.579 align:start position:0% box that you can build a chain with it's 00:02:05.579 --> 00:02:06.469 align:start position:0% box that you can build a chain with it's something<00:02:05.640> that's<00:02:05.880> going<00:02:05.969> to<00:02:06.030> be<00:02:06.149> useful<00:02:06.270> for 00:02:06.469 --> 00:02:06.479 align:start position:0% something that's going to be useful for 00:02:06.479 --> 00:02:09.410 align:start position:0% something that's going to be useful for for<00:02:07.200> side<00:02:07.380> chains<00:02:07.740> and<00:02:08.069> we're<00:02:08.789> also<00:02:08.940> using<00:02:09.360> it 00:02:09.410 --> 00:02:09.420 align:start position:0% for side chains and we're also using it 00:02:09.420 --> 00:02:11.029 align:start position:0% for side chains and we're also using it in<00:02:09.539> a<00:02:09.599> bunch<00:02:09.780> of<00:02:09.899> our<00:02:10.140> own<00:02:10.259> projects<00:02:10.800> like<00:02:10.920> to 00:02:11.029 --> 00:02:11.039 align:start position:0% in a bunch of our own projects like to 00:02:11.039 --> 00:02:12.740 align:start position:0% in a bunch of our own projects like to build<00:02:11.160> polka<00:02:11.430> dot<00:02:11.640> for<00:02:11.819> example<00:02:12.239> and<00:02:12.450> as<00:02:12.569> well 00:02:12.740 --> 00:02:12.750 align:start position:0% build polka dot for example and as well 00:02:12.750 --> 00:02:13.910 align:start position:0% build polka dot for example and as well to<00:02:12.959> build<00:02:13.080> the 00:02:13.910 --> 00:02:13.920 align:start position:0% to build the 00:02:13.920 --> 00:02:16.910 align:start position:0% to build the 2.0<00:02:14.610> client<00:02:14.970> so<00:02:15.540> the<00:02:16.230> way<00:02:16.349> that<00:02:16.380> substrate 00:02:16.910 --> 00:02:16.920 align:start position:0% 2.0 client so the way that substrate 00:02:16.920 --> 00:02:19.850 align:start position:0% 2.0 client so the way that substrate works<00:02:17.190> basically<00:02:17.760> is<00:02:17.910> you<00:02:18.090> have<00:02:18.300> lit<00:02:19.200> p2p 00:02:19.850 --> 00:02:19.860 align:start position:0% works basically is you have lit p2p 00:02:19.860 --> 00:02:21.589 align:start position:0% works basically is you have lit p2p networking<00:02:20.489> although<00:02:21.030> you<00:02:21.120> could<00:02:21.270> swap<00:02:21.420> that 00:02:21.589 --> 00:02:21.599 align:start position:0% networking although you could swap that 00:02:21.599 --> 00:02:23.390 align:start position:0% networking although you could swap that out<00:02:21.660> for<00:02:21.900> something<00:02:22.080> like<00:02:22.319> dev<00:02:22.590> p2p<00:02:23.099> my 00:02:23.390 --> 00:02:23.400 align:start position:0% out for something like dev p2p my 00:02:23.400 --> 00:02:25.160 align:start position:0% out for something like dev p2p my understanding<00:02:23.880> is<00:02:23.970> that<00:02:24.000> ether<00:02:24.510> 2.0<00:02:24.989> is 00:02:25.160 --> 00:02:25.170 align:start position:0% understanding is that ether 2.0 is 00:02:25.170 --> 00:02:26.870 align:start position:0% understanding is that ether 2.0 is heavily<00:02:25.440> leaning<00:02:25.830> towards<00:02:26.099> live<00:02:26.310> p2p<00:02:26.700> right 00:02:26.870 --> 00:02:26.880 align:start position:0% heavily leaning towards live p2p right 00:02:26.880 --> 00:02:28.550 align:start position:0% heavily leaning towards live p2p right now<00:02:27.000> so<00:02:27.720> that's<00:02:27.810> what<00:02:27.959> I'll<00:02:28.020> talk<00:02:28.170> about<00:02:28.410> for 00:02:28.550 --> 00:02:28.560 align:start position:0% now so that's what I'll talk about for 00:02:28.560 --> 00:02:32.750 align:start position:0% now so that's what I'll talk about for the<00:02:28.620> moment<00:02:29.239> will<00:02:30.239> a<00:02:30.270> p2p<00:02:30.680> networking<00:02:31.760> that 00:02:32.750 --> 00:02:32.760 align:start position:0% the moment will a p2p networking that 00:02:32.760 --> 00:02:35.449 align:start position:0% the moment will a p2p networking that lets<00:02:33.000> you<00:02:33.239> run<00:02:33.720> a<00:02:33.780> consensus<00:02:34.380> process<00:02:34.590> that 00:02:35.449 --> 00:02:35.459 align:start position:0% lets you run a consensus process that 00:02:35.459 --> 00:02:37.309 align:start position:0% lets you run a consensus process that does<00:02:35.640> agreement<00:02:36.180> over<00:02:36.540> state<00:02:36.810> transitions 00:02:37.309 --> 00:02:37.319 align:start position:0% does agreement over state transitions 00:02:37.319 --> 00:02:38.780 align:start position:0% does agreement over state transitions that<00:02:37.500> are<00:02:37.560> encoded<00:02:38.040> in<00:02:38.100> webassembly 00:02:38.780 --> 00:02:38.790 align:start position:0% that are encoded in webassembly 00:02:38.790 --> 00:02:40.580 align:start position:0% that are encoded in webassembly that<00:02:39.209> we<00:02:39.300> call<00:02:39.480> the<00:02:39.600> runtime<00:02:39.959> so<00:02:40.170> the<00:02:40.260> runtime 00:02:40.580 --> 00:02:40.590 align:start position:0% that we call the runtime so the runtime 00:02:40.590 --> 00:02:43.370 align:start position:0% that we call the runtime so the runtime is<00:02:40.709> the<00:02:40.800> actual<00:02:41.160> work<00:02:41.370> of<00:02:41.550> the<00:02:41.610> chain<00:02:41.940> and<00:02:42.930> this 00:02:43.370 --> 00:02:43.380 align:start position:0% is the actual work of the chain and this 00:02:43.380 --> 00:02:44.509 align:start position:0% is the actual work of the chain and this is<00:02:43.530> something<00:02:43.709> that<00:02:43.890> we've<00:02:44.010> designed<00:02:44.280> so<00:02:44.489> that 00:02:44.509 --> 00:02:44.519 align:start position:0% is something that we've designed so that 00:02:44.519 --> 00:02:46.009 align:start position:0% is something that we've designed so that you<00:02:44.640> can<00:02:44.760> upgrade<00:02:44.940> it<00:02:45.150> on<00:02:45.300> the<00:02:45.390> fly<00:02:45.599> for<00:02:45.959> a 00:02:46.009 --> 00:02:46.019 align:start position:0% you can upgrade it on the fly for a 00:02:46.019 --> 00:02:47.420 align:start position:0% you can upgrade it on the fly for a theorem<00:02:46.319> to<00:02:46.440> a<00:02:46.500> put<00:02:46.650> only<00:02:46.800> that's<00:02:46.950> not<00:02:47.160> really 00:02:47.420 --> 00:02:47.430 align:start position:0% theorem to a put only that's not really 00:02:47.430 --> 00:02:50.509 align:start position:0% theorem to a put only that's not really a<00:02:47.459> feature<00:02:48.030> that<00:02:48.300> you<00:02:48.420> need<00:02:48.739> so<00:02:49.739> you<00:02:50.100> know<00:02:50.459> you 00:02:50.509 --> 00:02:50.519 align:start position:0% a feature that you need so you know you 00:02:50.519 --> 00:02:52.070 align:start position:0% a feature that you need so you know you don't<00:02:50.790> need<00:02:51.060> it<00:02:51.120> to<00:02:51.390> be<00:02:51.420> web<00:02:51.630> assembly<00:02:52.019> it 00:02:52.070 --> 00:02:52.080 align:start position:0% don't need it to be web assembly it 00:02:52.080 --> 00:02:53.270 align:start position:0% don't need it to be web assembly it could<00:02:52.170> actually<00:02:52.290> be<00:02:52.470> native<00:02:52.799> code<00:02:53.010> in<00:02:53.160> this 00:02:53.270 --> 00:02:53.280 align:start position:0% could actually be native code in this 00:02:53.280 --> 00:02:55.699 align:start position:0% could actually be native code in this case<00:02:53.519> but<00:02:54.330> substrates<00:02:54.780> general<00:02:55.230> model<00:02:55.560> is 00:02:55.699 --> 00:02:55.709 align:start position:0% case but substrates general model is 00:02:55.709 --> 00:02:58.160 align:start position:0% case but substrates general model is around<00:02:56.120> web<00:02:57.120> assembly<00:02:57.510> state<00:02:57.690> transitions 00:02:58.160 --> 00:02:58.170 align:start position:0% around web assembly state transitions 00:02:58.170 --> 00:02:59.780 align:start position:0% around web assembly state transitions where<00:02:58.560> the<00:02:58.650> state<00:02:58.830> transition<00:02:59.220> logic<00:02:59.519> itself 00:02:59.780 --> 00:02:59.790 align:start position:0% where the state transition logic itself 00:02:59.790 --> 00:03:02.330 align:start position:0% where the state transition logic itself can<00:03:00.180> be<00:03:00.360> upgraded<00:03:00.799> and<00:03:01.799> that's<00:03:01.980> gonna<00:03:02.190> be 00:03:02.330 --> 00:03:02.340 align:start position:0% can be upgraded and that's gonna be 00:03:02.340 --> 00:03:03.800 align:start position:0% can be upgraded and that's gonna be composed<00:03:02.760> maybe<00:03:03.090> of<00:03:03.330> many<00:03:03.510> different 00:03:03.800 --> 00:03:03.810 align:start position:0% composed maybe of many different 00:03:03.810 --> 00:03:06.350 align:start position:0% composed maybe of many different reusable<00:03:04.620> components<00:03:05.190> or<00:03:05.310> modules<00:03:05.730> like 00:03:06.350 --> 00:03:06.360 align:start position:0% reusable components or modules like 00:03:06.360 --> 00:03:09.470 align:start position:0% reusable components or modules like governance<00:03:06.870> or<00:03:07.170> slashing<00:03:07.769> staking<00:03:08.430> for<00:03:09.239> polka 00:03:09.470 --> 00:03:09.480 align:start position:0% governance or slashing staking for polka 00:03:09.480 --> 00:03:13.430 align:start position:0% governance or slashing staking for polka dot<00:03:09.690> we<00:03:09.780> wrote<00:03:09.930> one<00:03:10.110> for<00:03:10.410> para<00:03:10.650> chains<00:03:11.510> and<00:03:12.510> for 00:03:13.430 --> 00:03:13.440 align:start position:0% dot we wrote one for para chains and for 00:03:13.440 --> 00:03:14.809 align:start position:0% dot we wrote one for para chains and for smart<00:03:13.650> contracts<00:03:14.130> and<00:03:14.250> that<00:03:14.310> sort<00:03:14.549> of<00:03:14.610> thing 00:03:14.809 --> 00:03:14.819 align:start position:0% smart contracts and that sort of thing 00:03:14.819 --> 00:03:17.000 align:start position:0% smart contracts and that sort of thing for<00:03:15.660> a<00:03:15.720> theorem<00:03:15.989> 2.0<00:03:16.350> we've<00:03:16.560> basically 00:03:17.000 --> 00:03:17.010 align:start position:0% for a theorem 2.0 we've basically 00:03:17.010 --> 00:03:19.009 align:start position:0% for a theorem 2.0 we've basically written<00:03:17.250> a<00:03:17.610> runtime<00:03:18.000> from<00:03:18.600> scratch<00:03:18.840> because 00:03:19.009 --> 00:03:19.019 align:start position:0% written a runtime from scratch because 00:03:19.019 --> 00:03:21.250 align:start position:0% written a runtime from scratch because the<00:03:19.290> beacon<00:03:19.650> chain<00:03:19.859> implementation<00:03:20.549> is<00:03:20.700> very 00:03:21.250 --> 00:03:21.260 align:start position:0% the beacon chain implementation is very 00:03:21.260 --> 00:03:23.660 align:start position:0% the beacon chain implementation is very very<00:03:22.260> unique 00:03:23.660 --> 00:03:23.670 align:start position:0% very unique 00:03:23.670 --> 00:03:26.470 align:start position:0% very unique so<00:03:24.269> what<00:03:24.900> substrate<00:03:25.260> gives<00:03:25.440> you<00:03:25.620> is<00:03:25.890> a 00:03:26.470 --> 00:03:26.480 align:start position:0% so what substrate gives you is a 00:03:26.480 --> 00:03:28.759 align:start position:0% so what substrate gives you is a abstract<00:03:27.480> block<00:03:28.109> format 00:03:28.759 --> 00:03:28.769 align:start position:0% abstract block format 00:03:28.769 --> 00:03:31.580 align:start position:0% abstract block format it's<00:03:29.420> agnostic<00:03:30.420> as<00:03:30.570> to<00:03:30.600> what<00:03:30.959> kind<00:03:31.230> of<00:03:31.380> backing 00:03:31.580 --> 00:03:31.590 align:start position:0% it's agnostic as to what kind of backing 00:03:31.590 --> 00:03:33.140 align:start position:0% it's agnostic as to what kind of backing database<00:03:32.130> you<00:03:32.250> use<00:03:32.280> so<00:03:32.579> it<00:03:32.700> could<00:03:32.850> be<00:03:32.970> like<00:03:33.120> a 00:03:33.140 --> 00:03:33.150 align:start position:0% database you use so it could be like a 00:03:33.150 --> 00:03:35.780 align:start position:0% database you use so it could be like a key<00:03:33.810> value<00:03:34.260> store<00:03:34.530> in<00:03:34.739> base<00:03:34.890> 16<00:03:35.160> a<00:03:35.400> miracle 00:03:35.780 --> 00:03:35.790 align:start position:0% key value store in base 16 a miracle 00:03:35.790 --> 00:03:37.750 align:start position:0% key value store in base 16 a miracle patricia<00:03:36.150> tree<00:03:36.450> it<00:03:36.630> could<00:03:37.109> be<00:03:37.230> a<00:03:37.260> binary 00:03:37.750 --> 00:03:37.760 align:start position:0% patricia tree it could be a binary 00:03:37.760 --> 00:03:40.490 align:start position:0% patricia tree it could be a binary Merkle<00:03:38.760> tree<00:03:38.970> it<00:03:39.630> could<00:03:39.900> be<00:03:40.049> something<00:03:40.470> like 00:03:40.490 --> 00:03:40.500 align:start position:0% Merkle tree it could be something like 00:03:40.500 --> 00:03:43.039 align:start position:0% Merkle tree it could be something like just<00:03:40.920> a<00:03:41.100> key<00:03:41.730> value<00:03:41.910> store<00:03:42.359> column<00:03:42.690> that's<00:03:42.870> not 00:03:43.039 --> 00:03:43.049 align:start position:0% just a key value store column that's not 00:03:43.049 --> 00:03:44.960 align:start position:0% just a key value store column that's not crypt<00:03:43.320> 'var<00:03:43.560> cryptographically<00:03:44.400> committed 00:03:44.960 --> 00:03:44.970 align:start position:0% crypt 'var cryptographically committed 00:03:44.970 --> 00:03:46.550 align:start position:0% crypt 'var cryptographically committed to<00:03:45.120> if<00:03:45.750> you<00:03:45.870> were<00:03:45.959> writing<00:03:46.140> something<00:03:46.380> like 00:03:46.550 --> 00:03:46.560 align:start position:0% to if you were writing something like 00:03:46.560 --> 00:03:48.710 align:start position:0% to if you were writing something like aut<00:03:46.890> EXO<00:03:47.310> base<00:03:47.519> chain 00:03:48.710 --> 00:03:48.720 align:start position:0% aut EXO base chain 00:03:48.720 --> 00:03:51.050 align:start position:0% aut EXO base chain at<00:03:49.200> its<00:03:49.650> core<00:03:49.890> basically<00:03:50.430> all<00:03:50.609> you<00:03:50.730> have<00:03:50.850> to<00:03:50.940> do 00:03:51.050 --> 00:03:51.060 align:start position:0% at its core basically all you have to do 00:03:51.060 --> 00:03:52.460 align:start position:0% at its core basically all you have to do to<00:03:51.180> write<00:03:51.329> a<00:03:51.359> chain<00:03:51.630> and<00:03:51.750> block<00:03:51.959> in<00:03:52.170> in 00:03:52.460 --> 00:03:52.470 align:start position:0% to write a chain and block in in 00:03:52.470 --> 00:03:54.849 align:start position:0% to write a chain and block in in substrate<00:03:52.950> is<00:03:53.160> put<00:03:53.970> together<00:03:54.090> a 00:03:54.849 --> 00:03:54.859 align:start position:0% substrate is put together a 00:03:54.859 --> 00:03:57.559 align:start position:0% substrate is put together a implementation<00:03:55.859> of<00:03:56.070> function<00:03:56.700> execute<00:03:57.299> block 00:03:57.559 --> 00:03:57.569 align:start position:0% implementation of function execute block 00:03:57.569 --> 00:03:59.539 align:start position:0% implementation of function execute block so<00:03:57.810> that<00:03:57.930> takes<00:03:58.079> in<00:03:58.350> a<00:03:58.380> blob<00:03:58.709> of<00:03:58.739> data<00:03:59.069> and<00:03:59.459> it 00:03:59.539 --> 00:03:59.549 align:start position:0% so that takes in a blob of data and it 00:03:59.549 --> 00:04:02.030 align:start position:0% so that takes in a blob of data and it tells<00:03:59.730> you<00:03:59.880> was<00:04:00.630> that<00:04:00.810> a<00:04:00.870> good<00:04:01.109> block<00:04:01.350> with<00:04:01.829> the 00:04:02.030 --> 00:04:02.040 align:start position:0% tells you was that a good block with the 00:04:02.040 --> 00:04:05.449 align:start position:0% tells you was that a good block with the with<00:04:02.340> the<00:04:02.519> backing<00:04:02.700> database<00:04:04.280> so<00:04:05.280> that's 00:04:05.449 --> 00:04:05.459 align:start position:0% with the backing database so that's 00:04:05.459 --> 00:04:07.819 align:start position:0% with the backing database so that's basically<00:04:05.819> what<00:04:06.000> we've<00:04:06.120> done<00:04:06.500> and<00:04:07.500> it's<00:04:07.620> got 00:04:07.819 --> 00:04:07.829 align:start position:0% basically what we've done and it's got 00:04:07.829 --> 00:04:09.470 align:start position:0% basically what we've done and it's got some<00:04:08.069> extensible<00:04:08.640> networking<00:04:09.209> and<00:04:09.390> other 00:04:09.470 --> 00:04:09.480 align:start position:0% some extensible networking and other 00:04:09.480 --> 00:04:13.220 align:start position:0% some extensible networking and other utilities<00:04:10.049> as<00:04:10.200> well<00:04:10.230> so<00:04:11.100> one<00:04:11.880> big<00:04:12.600> part<00:04:13.170> of 00:04:13.220 --> 00:04:13.230 align:start position:0% utilities as well so one big part of 00:04:13.230 --> 00:04:15.410 align:start position:0% utilities as well so one big part of what<00:04:13.380> we're<00:04:13.500> doing<00:04:13.590> is<00:04:14.100> pluggable<00:04:14.850> consensus 00:04:15.410 --> 00:04:15.420 align:start position:0% what we're doing is pluggable consensus 00:04:15.420 --> 00:04:18.050 align:start position:0% what we're doing is pluggable consensus so<00:04:15.630> that<00:04:15.840> was<00:04:15.959> a<00:04:15.989> feature<00:04:16.380> of<00:04:16.799> parody<00:04:17.669> etherium 00:04:18.050 --> 00:04:18.060 align:start position:0% so that was a feature of parody etherium 00:04:18.060 --> 00:04:19.849 align:start position:0% so that was a feature of parody etherium for<00:04:18.269> a<00:04:18.299> while<00:04:18.450> to<00:04:18.720> support<00:04:19.079> proof<00:04:19.320> of<00:04:19.470> work<00:04:19.620> as 00:04:19.849 --> 00:04:19.859 align:start position:0% for a while to support proof of work as 00:04:19.859 --> 00:04:22.399 align:start position:0% for a while to support proof of work as well<00:04:19.979> as<00:04:20.130> proof<00:04:20.340> of<00:04:20.459> authority<00:04:20.989> and<00:04:21.989> a 00:04:22.399 --> 00:04:22.409 align:start position:0% well as proof of authority and a 00:04:22.409 --> 00:04:24.620 align:start position:0% well as proof of authority and a contracting<00:04:23.159> system<00:04:23.310> around<00:04:23.640> that<00:04:23.789> but<00:04:24.450> for 00:04:24.620 --> 00:04:24.630 align:start position:0% contracting system around that but for 00:04:24.630 --> 00:04:26.029 align:start position:0% contracting system around that but for substrate<00:04:24.930> we've<00:04:25.110> come<00:04:25.289> up<00:04:25.320> with<00:04:25.470> a<00:04:25.620> pretty 00:04:26.029 --> 00:04:26.039 align:start position:0% substrate we've come up with a pretty 00:04:26.039 --> 00:04:27.320 align:start position:0% substrate we've come up with a pretty nice<00:04:26.460> set<00:04:26.820> of<00:04:26.909> abstract 00:04:27.320 --> 00:04:27.330 align:start position:0% nice set of abstract 00:04:27.330 --> 00:04:28.820 align:start position:0% nice set of abstract that<00:04:27.659> lets<00:04:27.810> us<00:04:27.900> do<00:04:28.050> a<00:04:28.080> lot<00:04:28.349> of<00:04:28.379> different 00:04:28.820 --> 00:04:28.830 align:start position:0% that lets us do a lot of different 00:04:28.830 --> 00:04:31.850 align:start position:0% that lets us do a lot of different complex<00:04:29.250> things<00:04:29.580> in<00:04:30.030> substrate<00:04:30.810> like<00:04:31.020> we've 00:04:31.850 --> 00:04:31.860 align:start position:0% complex things in substrate like we've 00:04:31.860 --> 00:04:35.029 align:start position:0% complex things in substrate like we've we've<00:04:32.340> done<00:04:33.409> rhododendron<00:04:34.439> which<00:04:34.800> is<00:04:35.009> a 00:04:35.029 --> 00:04:35.039 align:start position:0% we've done rhododendron which is a 00:04:35.039 --> 00:04:37.309 align:start position:0% we've done rhododendron which is a instant<00:04:35.879> finality<00:04:36.270> protocol<00:04:36.810> that's<00:04:37.020> derived 00:04:37.309 --> 00:04:37.319 align:start position:0% instant finality protocol that's derived 00:04:37.319 --> 00:04:40.369 align:start position:0% instant finality protocol that's derived from<00:04:37.469> pbft<00:04:38.009> we've<00:04:38.879> got<00:04:39.090> grandpa<00:04:39.599> and<00:04:39.960> or<00:04:40.139> and 00:04:40.369 --> 00:04:40.379 align:start position:0% from pbft we've got grandpa and or and 00:04:40.379 --> 00:04:43.070 align:start position:0% from pbft we've got grandpa and or and which<00:04:40.680> are<00:04:40.919> a<00:04:41.400> hybrid<00:04:42.030> consensus<00:04:42.810> together 00:04:43.070 --> 00:04:43.080 align:start position:0% which are a hybrid consensus together 00:04:43.080 --> 00:04:44.899 align:start position:0% which are a hybrid consensus together it's<00:04:43.289> something<00:04:43.439> like<00:04:43.740> Casper<00:04:44.039> FFG<00:04:44.639> in<00:04:44.819> the 00:04:44.899 --> 00:04:44.909 align:start position:0% it's something like Casper FFG in the 00:04:44.909 --> 00:04:47.059 align:start position:0% it's something like Casper FFG in the hybrid<00:04:45.270> model<00:04:45.419> you<00:04:45.719> could<00:04:45.900> do<00:04:46.110> Casper<00:04:46.530> FFG<00:04:46.919> as 00:04:47.059 --> 00:04:47.069 align:start position:0% hybrid model you could do Casper FFG as 00:04:47.069 --> 00:04:49.459 align:start position:0% hybrid model you could do Casper FFG as well<00:04:47.250> with<00:04:47.430> this<00:04:47.780> you<00:04:48.780> could<00:04:48.900> also<00:04:48.990> do<00:04:49.259> stuff 00:04:49.459 --> 00:04:49.469 align:start position:0% well with this you could also do stuff 00:04:49.469 --> 00:04:51.320 align:start position:0% well with this you could also do stuff like<00:04:49.560> Ava<00:04:49.860> that<00:04:50.219> Eman<00:04:50.639> was<00:04:50.789> just<00:04:51.000> talking 00:04:51.320 --> 00:04:51.330 align:start position:0% like Ava that Eman was just talking 00:04:51.330 --> 00:04:54.589 align:start position:0% like Ava that Eman was just talking about<00:04:51.419> fairly<00:04:52.319> easily<00:04:52.590> in<00:04:52.860> this<00:04:53.009> model<00:04:53.599> so 00:04:54.589 --> 00:04:54.599 align:start position:0% about fairly easily in this model so 00:04:54.599 --> 00:04:56.059 align:start position:0% about fairly easily in this model so it's<00:04:54.750> very<00:04:54.930> very<00:04:55.139> extensible<00:04:55.650> in<00:04:55.770> that<00:04:55.889> sense 00:04:56.059 --> 00:04:56.069 align:start position:0% it's very very extensible in that sense 00:04:56.069 --> 00:04:58.459 align:start position:0% it's very very extensible in that sense and<00:04:56.250> what<00:04:56.759> you<00:04:56.849> get<00:04:57.030> is<00:04:57.389> hot<00:04:57.990> swappable 00:04:58.459 --> 00:04:58.469 align:start position:0% and what you get is hot swappable 00:04:58.469 --> 00:05:00.290 align:start position:0% and what you get is hot swappable consensus<00:04:59.159> is<00:04:59.400> one<00:04:59.610> feature<00:04:59.789> we've<00:05:00.090> talked 00:05:00.290 --> 00:05:00.300 align:start position:0% consensus is one feature we've talked 00:05:00.300 --> 00:05:01.760 align:start position:0% consensus is one feature we've talked about<00:05:00.539> where<00:05:00.780> essentially<00:05:01.139> you<00:05:01.409> can<00:05:01.590> move 00:05:01.760 --> 00:05:01.770 align:start position:0% about where essentially you can move 00:05:01.770 --> 00:05:05.149 align:start position:0% about where essentially you can move between<00:05:01.979> consensus<00:05:02.879> algorithms<00:05:04.099> for<00:05:05.099> example 00:05:05.149 --> 00:05:05.159 align:start position:0% between consensus algorithms for example 00:05:05.159 --> 00:05:07.070 align:start position:0% between consensus algorithms for example if<00:05:05.669> you<00:05:05.789> deploy<00:05:06.090> your<00:05:06.270> chain<00:05:06.509> right<00:05:06.690> now<00:05:06.840> with 00:05:07.070 --> 00:05:07.080 align:start position:0% if you deploy your chain right now with 00:05:07.080 --> 00:05:09.709 align:start position:0% if you deploy your chain right now with some<00:05:07.229> relatively<00:05:07.919> simplistic<00:05:08.389> longest<00:05:09.389> chain 00:05:09.709 --> 00:05:09.719 align:start position:0% some relatively simplistic longest chain 00:05:09.719 --> 00:05:11.540 align:start position:0% some relatively simplistic longest chain rule<00:05:10.020> then<00:05:10.770> you<00:05:10.800> could<00:05:11.009> upgrade<00:05:11.400> it<00:05:11.520> to 00:05:11.540 --> 00:05:11.550 align:start position:0% rule then you could upgrade it to 00:05:11.550 --> 00:05:13.610 align:start position:0% rule then you could upgrade it to something<00:05:11.819> else<00:05:12.060> and<00:05:12.419> actually<00:05:13.139> fork<00:05:13.409> the 00:05:13.610 --> 00:05:13.620 align:start position:0% something else and actually fork the 00:05:13.620 --> 00:05:17.180 align:start position:0% something else and actually fork the chain<00:05:13.830> on<00:05:14.009> to<00:05:14.129> another<00:05:14.310> system<00:05:14.759> a<00:05:16.190> hot 00:05:17.180 --> 00:05:17.190 align:start position:0% chain on to another system a hot 00:05:17.190 --> 00:05:19.159 align:start position:0% chain on to another system a hot swappable<00:05:17.520> state<00:05:17.909> transition<00:05:18.330> function<00:05:18.360> I'm 00:05:19.159 --> 00:05:19.169 align:start position:0% swappable state transition function I'm 00:05:19.169 --> 00:05:20.600 align:start position:0% swappable state transition function I'm not<00:05:19.289> going<00:05:19.409> to<00:05:19.469> go<00:05:19.529> through<00:05:19.710> all<00:05:19.830> of<00:05:19.860> these<00:05:20.039> but 00:05:20.600 --> 00:05:20.610 align:start position:0% not going to go through all of these but 00:05:20.610 --> 00:05:22.279 align:start position:0% not going to go through all of these but one<00:05:21.150> of<00:05:21.180> the<00:05:21.330> ones<00:05:21.479> that<00:05:21.599> I<00:05:21.659> do<00:05:21.719> really<00:05:21.960> want<00:05:22.080> to 00:05:22.279 --> 00:05:22.289 align:start position:0% one of the ones that I do really want to 00:05:22.289 --> 00:05:24.230 align:start position:0% one of the ones that I do really want to stress<00:05:22.560> is<00:05:22.800> that<00:05:22.860> it's<00:05:23.460> got<00:05:23.550> a<00:05:23.610> light<00:05:23.819> client 00:05:24.230 --> 00:05:24.240 align:start position:0% stress is that it's got a light client 00:05:24.240 --> 00:05:25.939 align:start position:0% stress is that it's got a light client from<00:05:24.419> day<00:05:24.599> one 00:05:25.939 --> 00:05:25.949 align:start position:0% from day one 00:05:25.949 --> 00:05:28.730 align:start position:0% from day one I'm<00:05:26.490> one<00:05:26.819> of<00:05:26.849> the<00:05:27.210> few<00:05:27.810> people<00:05:28.050> who's<00:05:28.379> written 00:05:28.730 --> 00:05:28.740 align:start position:0% I'm one of the few people who's written 00:05:28.740 --> 00:05:31.879 align:start position:0% I'm one of the few people who's written a<00:05:29.159> light<00:05:29.490> client<00:05:29.909> for<00:05:30.090> a<00:05:30.120> theorem<00:05:30.539> I<00:05:31.169> can<00:05:31.710> tell 00:05:31.879 --> 00:05:31.889 align:start position:0% a light client for a theorem I can tell 00:05:31.889 --> 00:05:34.100 align:start position:0% a light client for a theorem I can tell you<00:05:32.039> that<00:05:32.219> adding<00:05:32.729> that<00:05:32.879> onto<00:05:33.240> a<00:05:33.840> blockchain 00:05:34.100 --> 00:05:34.110 align:start position:0% you that adding that onto a blockchain 00:05:34.110 --> 00:05:37.459 align:start position:0% you that adding that onto a blockchain node<00:05:34.500> after<00:05:34.650> the<00:05:34.949> fact<00:05:35.190> is<00:05:35.400> awful<00:05:35.940> it<00:05:36.779> is<00:05:36.930> a<00:05:36.960> lot 00:05:37.459 --> 00:05:37.469 align:start position:0% node after the fact is awful it is a lot 00:05:37.469 --> 00:05:39.379 align:start position:0% node after the fact is awful it is a lot of<00:05:37.500> work<00:05:37.889> so<00:05:38.190> having<00:05:38.400> that<00:05:38.639> supported<00:05:39.240> from 00:05:39.379 --> 00:05:39.389 align:start position:0% of work so having that supported from 00:05:39.389 --> 00:05:41.540 align:start position:0% of work so having that supported from day<00:05:39.599> one<00:05:39.840> having<00:05:40.169> networking<00:05:40.620> protocols<00:05:41.279> for 00:05:41.540 --> 00:05:41.550 align:start position:0% day one having networking protocols for 00:05:41.550 --> 00:05:44.180 align:start position:0% day one having networking protocols for it<00:05:41.699> from<00:05:42.479> day<00:05:42.659> one<00:05:42.870> is<00:05:43.529> really<00:05:43.949> really 00:05:44.180 --> 00:05:44.190 align:start position:0% it from day one is really really 00:05:44.190 --> 00:05:45.170 align:start position:0% it from day one is really really important<00:05:44.610> to<00:05:44.639> make<00:05:44.789> sure<00:05:44.849> that<00:05:44.940> you<00:05:45.089> can 00:05:45.170 --> 00:05:45.180 align:start position:0% important to make sure that you can 00:05:45.180 --> 00:05:46.219 align:start position:0% important to make sure that you can actually<00:05:45.330> have<00:05:45.659> light<00:05:45.930> client 00:05:46.219 --> 00:05:46.229 align:start position:0% actually have light client 00:05:46.229 --> 00:05:48.950 align:start position:0% actually have light client infrastructure<00:05:46.830> in<00:05:46.919> the<00:05:47.009> end<00:05:47.659> of<00:05:48.659> course 00:05:48.950 --> 00:05:48.960 align:start position:0% infrastructure in the end of course 00:05:48.960 --> 00:05:50.869 align:start position:0% infrastructure in the end of course there's<00:05:49.199> things<00:05:49.379> like<00:05:49.469> the<00:05:49.740> module<00:05:50.400> library 00:05:50.869 --> 00:05:50.879 align:start position:0% there's things like the module library 00:05:50.879 --> 00:05:52.369 align:start position:0% there's things like the module library and<00:05:51.210> if<00:05:51.360> you<00:05:51.449> want<00:05:51.599> to<00:05:51.690> plug<00:05:51.839> into<00:05:51.990> something 00:05:52.369 --> 00:05:52.379 align:start position:0% and if you want to plug into something 00:05:52.379 --> 00:05:54.529 align:start position:0% and if you want to plug into something like<00:05:52.529> polka<00:05:53.310> dot<00:05:53.520> that<00:05:53.729> is<00:05:53.759> that's<00:05:54.150> supported 00:05:54.529 --> 00:05:54.539 align:start position:0% like polka dot that is that's supported 00:05:54.539 --> 00:05:58.010 align:start position:0% like polka dot that is that's supported as<00:05:54.659> well<00:05:54.949> but<00:05:55.949> to<00:05:56.759> get<00:05:56.909> more<00:05:57.150> to<00:05:57.599> the<00:05:57.719> direct 00:05:58.010 --> 00:05:58.020 align:start position:0% as well but to get more to the direct 00:05:58.020 --> 00:06:00.559 align:start position:0% as well but to get more to the direct point<00:05:58.319> and<00:05:59.159> the<00:05:59.610> question<00:06:00.029> and<00:06:00.180> on<00:06:00.389> the 00:06:00.559 --> 00:06:00.569 align:start position:0% point and the question and on the 00:06:00.569 --> 00:06:02.029 align:start position:0% point and the question and on the forefront<00:06:01.020> of<00:06:01.110> a<00:06:01.199> lot<00:06:01.229> of<00:06:01.349> your<00:06:01.500> minds<00:06:01.889> with 00:06:02.029 --> 00:06:02.039 align:start position:0% forefront of a lot of your minds with 00:06:02.039 --> 00:06:03.920 align:start position:0% forefront of a lot of your minds with this<00:06:02.129> conference<00:06:02.520> is<00:06:02.759> that<00:06:02.930> aetherium 00:06:03.920 --> 00:06:03.930 align:start position:0% this conference is that aetherium 00:06:03.930 --> 00:06:06.980 align:start position:0% this conference is that aetherium basically<00:06:04.349> needs<00:06:04.560> to<00:06:04.860> scale<00:06:05.360> so<00:06:06.360> the<00:06:06.569> EVM 00:06:06.980 --> 00:06:06.990 align:start position:0% basically needs to scale so the EVM 00:06:06.990 --> 00:06:08.779 align:start position:0% basically needs to scale so the EVM can't<00:06:07.469> process<00:06:07.889> the<00:06:08.370> proof-of-work 00:06:08.779 --> 00:06:08.789 align:start position:0% can't process the proof-of-work 00:06:08.789 --> 00:06:12.200 align:start position:0% can't process the proof-of-work consensus<00:06:09.750> the<00:06:10.229> EVM<00:06:10.680> can't<00:06:11.460> process<00:06:11.789> enough 00:06:12.200 --> 00:06:12.210 align:start position:0% consensus the EVM can't process enough 00:06:12.210 --> 00:06:14.089 align:start position:0% consensus the EVM can't process enough transactions<00:06:12.900> for<00:06:13.289> the<00:06:13.440> uses<00:06:13.830> that<00:06:13.860> we're 00:06:14.089 --> 00:06:14.099 align:start position:0% transactions for the uses that we're 00:06:14.099 --> 00:06:19.430 align:start position:0% transactions for the uses that we're already<00:06:14.279> seeing<00:06:16.729> that's<00:06:17.729> just<00:06:18.029> the<00:06:18.120> case<00:06:18.440> side 00:06:19.430 --> 00:06:19.440 align:start position:0% already seeing that's just the case side 00:06:19.440 --> 00:06:21.499 align:start position:0% already seeing that's just the case side chains<00:06:19.800> and<00:06:19.979> bridges<00:06:20.370> which<00:06:20.819> Buuren<00:06:21.270> talked 00:06:21.499 --> 00:06:21.509 align:start position:0% chains and bridges which Buuren talked 00:06:21.509 --> 00:06:23.899 align:start position:0% chains and bridges which Buuren talked about<00:06:21.779> a<00:06:21.810> bit<00:06:22.020> earlier<00:06:22.319> on<00:06:22.440> the<00:06:22.529> mainstage<00:06:23.039> are 00:06:23.899 --> 00:06:23.909 align:start position:0% about a bit earlier on the mainstage are 00:06:23.909 --> 00:06:26.570 align:start position:0% about a bit earlier on the mainstage are a<00:06:24.150> temporary<00:06:24.690> solution<00:06:25.110> to<00:06:25.529> this<00:06:25.650> problem<00:06:25.860> but 00:06:26.570 --> 00:06:26.580 align:start position:0% a temporary solution to this problem but 00:06:26.580 --> 00:06:28.249 align:start position:0% a temporary solution to this problem but they<00:06:26.669> only<00:06:26.879> mitigate<00:06:27.569> it 00:06:28.249 --> 00:06:28.259 align:start position:0% they only mitigate it 00:06:28.259 --> 00:06:30.439 align:start position:0% they only mitigate it at<00:06:29.009> some<00:06:29.279> point<00:06:29.490> even<00:06:29.789> if<00:06:29.879> you<00:06:29.969> have<00:06:30.150> a<00:06:30.180> ton<00:06:30.419> of 00:06:30.439 --> 00:06:30.449 align:start position:0% at some point even if you have a ton of 00:06:30.449 --> 00:06:32.119 align:start position:0% at some point even if you have a ton of side<00:06:30.750> chains<00:06:31.050> and<00:06:31.199> a<00:06:31.289> ton<00:06:31.469> of<00:06:31.500> bridges<00:06:31.979> you're 00:06:32.119 --> 00:06:32.129 align:start position:0% side chains and a ton of bridges you're 00:06:32.129 --> 00:06:33.950 align:start position:0% side chains and a ton of bridges you're sort<00:06:32.339> of<00:06:32.370> fragmenting<00:06:33.089> the<00:06:33.210> ecosystem<00:06:33.810> which 00:06:33.950 --> 00:06:33.960 align:start position:0% sort of fragmenting the ecosystem which 00:06:33.960 --> 00:06:39.350 align:start position:0% sort of fragmenting the ecosystem which isn't<00:06:34.139> ideal<00:06:34.430> and<00:06:35.430> also<00:06:36.709> you're<00:06:38.360> just 00:06:39.350 --> 00:06:39.360 align:start position:0% isn't ideal and also you're just 00:06:39.360 --> 00:06:41.170 align:start position:0% isn't ideal and also you're just delaying<00:06:39.899> the<00:06:40.080> scaling<00:06:40.589> issues<00:06:40.919> but 00:06:41.170 --> 00:06:41.180 align:start position:0% delaying the scaling issues but 00:06:41.180 --> 00:06:42.730 align:start position:0% delaying the scaling issues but is<00:06:41.270> at<00:06:41.389> some<00:06:41.600> point<00:06:41.840> you<00:06:42.229> won't<00:06:42.350> be<00:06:42.560> able<00:06:42.680> to 00:06:42.730 --> 00:06:42.740 align:start position:0% is at some point you won't be able to 00:06:42.740 --> 00:06:44.529 align:start position:0% is at some point you won't be able to get<00:06:42.919> all<00:06:43.070> those<00:06:43.280> bridge<00:06:43.580> notifications<00:06:44.300> onto 00:06:44.529 --> 00:06:44.539 align:start position:0% get all those bridge notifications onto 00:06:44.539 --> 00:06:47.020 align:start position:0% get all those bridge notifications onto the<00:06:44.630> chain<00:06:44.780> as<00:06:44.930> well<00:06:45.520> so<00:06:46.520> you<00:06:46.610> really<00:06:46.850> need<00:06:46.970> a 00:06:47.020 --> 00:06:47.030 align:start position:0% the chain as well so you really need a 00:06:47.030 --> 00:06:50.050 align:start position:0% the chain as well so you really need a root<00:06:47.240> level<00:06:47.419> chain<00:06:47.750> that's<00:06:47.930> scaling<00:06:48.350> so<00:06:49.060> the 00:06:50.050 --> 00:06:50.060 align:start position:0% root level chain that's scaling so the 00:06:50.060 --> 00:06:53.499 align:start position:0% root level chain that's scaling so the solution<00:06:50.600> proposed<00:06:51.139> by<00:06:52.120> the<00:06:53.120> etherium 00:06:53.499 --> 00:06:53.509 align:start position:0% solution proposed by the etherium 00:06:53.509 --> 00:06:56.529 align:start position:0% solution proposed by the etherium research<00:06:53.810> team<00:06:54.020> is<00:06:54.259> serenity<00:06:55.130> aetherium<00:06:55.940> 2.0 00:06:56.529 --> 00:06:56.539 align:start position:0% research team is serenity aetherium 2.0 00:06:56.539 --> 00:06:58.420 align:start position:0% research team is serenity aetherium 2.0 so<00:06:56.960> this<00:06:57.110> is<00:06:57.289> this<00:06:57.560> is<00:06:57.680> a<00:06:57.710> name<00:06:57.979> that's<00:06:58.190> been 00:06:58.420 --> 00:06:58.430 align:start position:0% so this is this is a name that's been 00:06:58.430 --> 00:06:59.439 align:start position:0% so this is this is a name that's been around<00:06:58.520> for<00:06:58.970> a<00:06:59.000> while 00:06:59.439 --> 00:06:59.449 align:start position:0% around for a while 00:06:59.449 --> 00:07:01.510 align:start position:0% around for a while I<00:06:59.479> mean<00:06:59.930> serenity<00:07:00.680> has<00:07:00.800> been<00:07:00.949> on<00:07:01.070> the<00:07:01.160> etherium 00:07:01.510 --> 00:07:01.520 align:start position:0% I mean serenity has been on the etherium 00:07:01.520 --> 00:07:04.300 align:start position:0% I mean serenity has been on the etherium roadmaps<00:07:02.060> for<00:07:02.270> years<00:07:02.840> the<00:07:03.410> exact<00:07:03.710> feature<00:07:03.979> set 00:07:04.300 --> 00:07:04.310 align:start position:0% roadmaps for years the exact feature set 00:07:04.310 --> 00:07:05.800 align:start position:0% roadmaps for years the exact feature set that<00:07:04.340> it's<00:07:04.580> encompassing<00:07:05.240> is<00:07:05.360> just<00:07:05.600> being 00:07:05.800 --> 00:07:05.810 align:start position:0% that it's encompassing is just being 00:07:05.810 --> 00:07:07.090 align:start position:0% that it's encompassing is just being nailed<00:07:05.990> down<00:07:06.259> now 00:07:07.090 --> 00:07:07.100 align:start position:0% nailed down now 00:07:07.100 --> 00:07:09.249 align:start position:0% nailed down now so<00:07:07.370> the<00:07:07.490> spec<00:07:07.789> is<00:07:08.539> about<00:07:08.780> sixty<00:07:09.139> percent 00:07:09.249 --> 00:07:09.259 align:start position:0% so the spec is about sixty percent 00:07:09.259 --> 00:07:10.719 align:start position:0% so the spec is about sixty percent complete<00:07:09.770> now<00:07:09.889> it<00:07:10.039> doesn't<00:07:10.190> cover<00:07:10.430> everything 00:07:10.719 --> 00:07:10.729 align:start position:0% complete now it doesn't cover everything 00:07:10.729 --> 00:07:12.969 align:start position:0% complete now it doesn't cover everything like<00:07:11.000> block<00:07:11.270> authorship<00:07:11.810> but<00:07:12.530> it<00:07:12.620> does<00:07:12.770> get 00:07:12.969 --> 00:07:12.979 align:start position:0% like block authorship but it does get 00:07:12.979 --> 00:07:14.320 align:start position:0% like block authorship but it does get the<00:07:13.009> core<00:07:13.340> of<00:07:13.370> the<00:07:13.610> state<00:07:13.820> transition<00:07:14.300> system 00:07:14.320 --> 00:07:14.330 align:start position:0% the core of the state transition system 00:07:14.330 --> 00:07:16.629 align:start position:0% the core of the state transition system validator<00:07:15.139> shuffling<00:07:15.680> changing<00:07:16.190> validator 00:07:16.629 --> 00:07:16.639 align:start position:0% validator shuffling changing validator 00:07:16.639 --> 00:07:21.100 align:start position:0% validator shuffling changing validator dynasties<00:07:17.210> and<00:07:19.479> collecting<00:07:20.479> at<00:07:20.570> the<00:07:20.720> stations 00:07:21.100 --> 00:07:21.110 align:start position:0% dynasties and collecting at the stations 00:07:21.110 --> 00:07:21.909 align:start position:0% dynasties and collecting at the stations and<00:07:21.259> that<00:07:21.320> sort<00:07:21.530> of<00:07:21.590> thing 00:07:21.909 --> 00:07:21.919 align:start position:0% and that sort of thing 00:07:21.919 --> 00:07:28.300 align:start position:0% and that sort of thing so<00:07:23.229> the<00:07:24.229> main<00:07:24.860> piece<00:07:25.310> of<00:07:25.720> the<00:07:26.770> sharding<00:07:27.770> design 00:07:28.300 --> 00:07:28.310 align:start position:0% so the main piece of the sharding design 00:07:28.310 --> 00:07:31.180 align:start position:0% so the main piece of the sharding design is<00:07:28.610> a<00:07:28.880> beacon<00:07:29.210> chain<00:07:29.479> and<00:07:30.320> this<00:07:30.410> is<00:07:30.590> what<00:07:30.770> we're 00:07:31.180 --> 00:07:31.190 align:start position:0% is a beacon chain and this is what we're 00:07:31.190 --> 00:07:32.920 align:start position:0% is a beacon chain and this is what we're building<00:07:31.550> on<00:07:31.669> substrate<00:07:32.090> so<00:07:32.449> it's<00:07:32.630> sort<00:07:32.780> of<00:07:32.840> a 00:07:32.920 --> 00:07:32.930 align:start position:0% building on substrate so it's sort of a 00:07:32.930 --> 00:07:35.469 align:start position:0% building on substrate so it's sort of a shard<00:07:33.229> coordinator<00:07:34.009> it<00:07:34.250> manages<00:07:34.789> proof<00:07:35.330> of 00:07:35.469 --> 00:07:35.479 align:start position:0% shard coordinator it manages proof of 00:07:35.479 --> 00:07:37.420 align:start position:0% shard coordinator it manages proof of stake<00:07:35.720> validators<00:07:36.470> it<00:07:36.650> add<00:07:36.800> blocks<00:07:37.130> adds 00:07:37.420 --> 00:07:37.430 align:start position:0% stake validators it add blocks adds 00:07:37.430 --> 00:07:39.790 align:start position:0% stake validators it add blocks adds blocks<00:07:37.789> to<00:07:38.000> the<00:07:38.090> chain<00:07:38.300> it<00:07:38.570> finalizes<00:07:39.470> them<00:07:39.620> it 00:07:39.790 --> 00:07:39.800 align:start position:0% blocks to the chain it finalizes them it 00:07:39.800 --> 00:07:43.330 align:start position:0% blocks to the chain it finalizes them it gets<00:07:39.889> cross<00:07:40.310> links<00:07:40.759> from<00:07:41.419> shards<00:07:42.190> which<00:07:43.190> are 00:07:43.330 --> 00:07:43.340 align:start position:0% gets cross links from shards which are 00:07:43.340 --> 00:07:45.399 align:start position:0% gets cross links from shards which are attested<00:07:43.639> to<00:07:43.849> by<00:07:44.060> committees<00:07:44.750> of<00:07:44.960> validators 00:07:45.399 --> 00:07:45.409 align:start position:0% attested to by committees of validators 00:07:45.409 --> 00:07:46.870 align:start position:0% attested to by committees of validators so<00:07:45.620> all<00:07:45.770> the<00:07:45.889> valid<00:07:46.130> leaders<00:07:46.340> will<00:07:46.460> be<00:07:46.520> split 00:07:46.870 --> 00:07:46.880 align:start position:0% so all the valid leaders will be split 00:07:46.880 --> 00:07:49.089 align:start position:0% so all the valid leaders will be split up<00:07:46.909> into<00:07:47.330> small<00:07:47.990> committees<00:07:48.470> each<00:07:48.710> committee 00:07:49.089 --> 00:07:49.099 align:start position:0% up into small committees each committee 00:07:49.099 --> 00:07:51.040 align:start position:0% up into small committees each committee being<00:07:49.340> assigned<00:07:49.610> to<00:07:49.789> a<00:07:49.880> specific<00:07:50.030> shard<00:07:50.570> for<00:07:50.810> a 00:07:51.040 --> 00:07:51.050 align:start position:0% being assigned to a specific shard for a 00:07:51.050 --> 00:07:53.230 align:start position:0% being assigned to a specific shard for a period<00:07:51.590> of<00:07:51.680> time<00:07:51.889> the<00:07:52.430> assignment<00:07:52.880> is<00:07:52.970> done<00:07:53.060> by 00:07:53.230 --> 00:07:53.240 align:start position:0% period of time the assignment is done by 00:07:53.240 --> 00:07:55.000 align:start position:0% period of time the assignment is done by a<00:07:53.270> randomness<00:07:53.870> beacon<00:07:54.320> which<00:07:54.620> is<00:07:54.770> why<00:07:54.860> it's 00:07:55.000 --> 00:07:55.010 align:start position:0% a randomness beacon which is why it's 00:07:55.010 --> 00:07:58.390 align:start position:0% a randomness beacon which is why it's called<00:07:55.190> a<00:07:55.280> beacon<00:07:55.550> chain<00:07:56.020> and<00:07:57.400> basically 00:07:58.390 --> 00:07:58.400 align:start position:0% called a beacon chain and basically 00:07:58.400 --> 00:08:00.610 align:start position:0% called a beacon chain and basically these<00:07:58.610> guys<00:07:58.669> just<00:07:59.030> attest<00:07:59.720> to<00:07:59.840> blocks<00:08:00.380> that 00:08:00.610 --> 00:08:00.620 align:start position:0% these guys just attest to blocks that 00:08:00.620 --> 00:08:04.270 align:start position:0% these guys just attest to blocks that exist<00:08:00.949> on<00:08:01.070> sharts<00:08:02.530> it<00:08:03.530> operates<00:08:03.889> as<00:08:03.979> a<00:08:04.010> proof 00:08:04.270 --> 00:08:04.280 align:start position:0% exist on sharts it operates as a proof 00:08:04.280 --> 00:08:07.930 align:start position:0% exist on sharts it operates as a proof of<00:08:04.460> stake<00:08:04.909> chain<00:08:05.210> the<00:08:05.479> validators<00:08:06.400> might<00:08:07.400> take 00:08:07.930 --> 00:08:07.940 align:start position:0% of stake chain the validators might take 00:08:07.940 --> 00:08:10.899 align:start position:0% of stake chain the validators might take turns<00:08:08.750> proposing<00:08:09.620> blocks<00:08:09.830> which<00:08:10.639> would<00:08:10.789> be 00:08:10.899 --> 00:08:10.909 align:start position:0% turns proposing blocks which would be 00:08:10.909 --> 00:08:14.800 align:start position:0% turns proposing blocks which would be finalized<00:08:11.389> by<00:08:11.570> Casper<00:08:11.960> FFG<00:08:12.349> so<00:08:12.949> Casper<00:08:13.340> FFG<00:08:13.970> is 00:08:14.800 --> 00:08:14.810 align:start position:0% finalized by Casper FFG so Casper FFG is 00:08:14.810 --> 00:08:16.600 align:start position:0% finalized by Casper FFG so Casper FFG is is<00:08:15.110> one<00:08:15.349> of<00:08:15.470> the<00:08:15.590> Casper's<00:08:16.039> that's<00:08:16.280> floating 00:08:16.600 --> 00:08:16.610 align:start position:0% is one of the Casper's that's floating 00:08:16.610 --> 00:08:20.560 align:start position:0% is one of the Casper's that's floating around<00:08:17.860> it's<00:08:18.909> basically<00:08:19.909> just<00:08:20.030> a<00:08:20.240> finality 00:08:20.560 --> 00:08:20.570 align:start position:0% around it's basically just a finality 00:08:20.570 --> 00:08:24.249 align:start position:0% around it's basically just a finality gadget<00:08:21.169> so<00:08:21.610> the<00:08:22.610> term<00:08:22.849> finality<00:08:23.360> gadget<00:08:23.990> is<00:08:24.199> a 00:08:24.249 --> 00:08:24.259 align:start position:0% gadget so the term finality gadget is a 00:08:24.259 --> 00:08:27.820 align:start position:0% gadget so the term finality gadget is a bit<00:08:24.710> nebulous<00:08:24.949> but<00:08:26.110> it's<00:08:27.110> essentially<00:08:27.620> part 00:08:27.820 --> 00:08:27.830 align:start position:0% bit nebulous but it's essentially part 00:08:27.830 --> 00:08:29.740 align:start position:0% bit nebulous but it's essentially part of<00:08:27.889> a<00:08:27.949> hybrid<00:08:28.190> consensus<00:08:28.970> process<00:08:29.419> where<00:08:29.659> you 00:08:29.740 --> 00:08:29.750 align:start position:0% of a hybrid consensus process where you 00:08:29.750 --> 00:08:32.199 align:start position:0% of a hybrid consensus process where you have<00:08:29.930> a<00:08:30.349> probabilistic<00:08:31.070> consensus<00:08:31.789> algorithm 00:08:32.199 --> 00:08:32.209 align:start position:0% have a probabilistic consensus algorithm 00:08:32.209 --> 00:08:35.319 align:start position:0% have a probabilistic consensus algorithm adding<00:08:33.079> blocks<00:08:33.349> to<00:08:33.620> the<00:08:33.709> chain<00:08:33.950> and<00:08:34.339> then<00:08:35.240> you 00:08:35.319 --> 00:08:35.329 align:start position:0% adding blocks to the chain and then you 00:08:35.329 --> 00:08:37.569 align:start position:0% adding blocks to the chain and then you have<00:08:35.510> finality<00:08:36.140> gadget<00:08:36.709> adding<00:08:36.950> accountable 00:08:37.569 --> 00:08:37.579 align:start position:0% have finality gadget adding accountable 00:08:37.579 --> 00:08:39.550 align:start position:0% have finality gadget adding accountable safety<00:08:37.940> on<00:08:38.060> to<00:08:38.180> that<00:08:38.300> so<00:08:38.750> then<00:08:38.899> if<00:08:39.020> blocks<00:08:39.380> that 00:08:39.550 --> 00:08:39.560 align:start position:0% safety on to that so then if blocks that 00:08:39.560 --> 00:08:41.560 align:start position:0% safety on to that so then if blocks that are<00:08:39.620> finalized<00:08:40.250> by<00:08:40.520> the<00:08:40.550> gadget<00:08:41.029> are<00:08:41.149> reverted 00:08:41.560 --> 00:08:41.570 align:start position:0% are finalized by the gadget are reverted 00:08:41.570 --> 00:08:44.199 align:start position:0% are finalized by the gadget are reverted you<00:08:41.599> get<00:08:41.870> this<00:08:41.990> process<00:08:42.229> called<00:08:43.209> accountable 00:08:44.199 --> 00:08:44.209 align:start position:0% you get this process called accountable 00:08:44.209 --> 00:08:46.360 align:start position:0% you get this process called accountable safety<00:08:44.600> which<00:08:44.750> means<00:08:44.959> you<00:08:45.050> can<00:08:45.200> identify<00:08:45.370> who 00:08:46.360 --> 00:08:46.370 align:start position:0% safety which means you can identify who 00:08:46.370 --> 00:08:47.980 align:start position:0% safety which means you can identify who acted<00:08:46.790> in<00:08:46.880> reverting<00:08:47.300> those<00:08:47.450> blocks<00:08:47.750> and 00:08:47.980 --> 00:08:47.990 align:start position:0% acted in reverting those blocks and 00:08:47.990 --> 00:08:50.740 align:start position:0% acted in reverting those blocks and punished<00:08:48.649> them<00:08:48.680> so<00:08:49.070> Casper<00:08:49.610> FFG<00:08:50.150> does<00:08:50.360> that<00:08:50.540> by 00:08:50.740 --> 00:08:50.750 align:start position:0% punished them so Casper FFG does that by 00:08:50.750 --> 00:08:53.560 align:start position:0% punished them so Casper FFG does that by voting<00:08:51.320> on<00:08:51.650> checkpoints<00:08:52.400> every<00:08:52.760> n<00:08:52.910> blocks<00:08:53.240> and 00:08:53.560 --> 00:08:53.570 align:start position:0% voting on checkpoints every n blocks and 00:08:53.570 --> 00:08:54.610 align:start position:0% voting on checkpoints every n blocks and if<00:08:53.660> you<00:08:53.690> get<00:08:53.870> to<00:08:54.290> check 00:08:54.610 --> 00:08:54.620 align:start position:0% if you get to check 00:08:54.620 --> 00:08:56.290 align:start position:0% if you get to check points<00:08:54.890> in<00:08:54.980> a<00:08:55.040> row<00:08:55.070> that<00:08:55.430> gets<00:08:55.580> super<00:08:55.880> majority 00:08:56.290 --> 00:08:56.300 align:start position:0% points in a row that gets super majority 00:08:56.300 --> 00:08:59.829 align:start position:0% points in a row that gets super majority support<00:08:56.690> you've<00:08:56.839> finalized<00:08:57.710> a<00:08:57.830> block<00:08:58.839> it 00:08:59.829 --> 00:08:59.839 align:start position:0% support you've finalized a block it 00:08:59.839 --> 00:09:01.510 align:start position:0% support you've finalized a block it influences<00:09:00.350> the<00:09:00.470> fork<00:09:00.680> choice<00:09:00.920> rule<00:09:01.190> in 00:09:01.510 --> 00:09:01.520 align:start position:0% influences the fork choice rule in 00:09:01.520 --> 00:09:04.960 align:start position:0% influences the fork choice rule in charting<00:09:02.390> of<00:09:02.540> the<00:09:03.130> block<00:09:04.130> production<00:09:04.610> system 00:09:04.960 --> 00:09:04.970 align:start position:0% charting of the block production system 00:09:04.970 --> 00:09:07.660 align:start position:0% charting of the block production system as<00:09:05.120> well<00:09:05.529> the<00:09:06.529> cool<00:09:06.680> thing<00:09:06.710> about<00:09:06.860> cast<00:09:07.160> for<00:09:07.339> FG 00:09:07.660 --> 00:09:07.670 align:start position:0% as well the cool thing about cast for FG 00:09:07.670 --> 00:09:09.790 align:start position:0% as well the cool thing about cast for FG is<00:09:07.700> that<00:09:07.970> you<00:09:08.029> get<00:09:08.180> information<00:09:08.900> on<00:09:09.380> chain 00:09:09.790 --> 00:09:09.800 align:start position:0% is that you get information on chain 00:09:09.800 --> 00:09:11.260 align:start position:0% is that you get information on chain about<00:09:10.100> which<00:09:10.310> blocks<00:09:10.550> have<00:09:10.730> been<00:09:10.820> finalized 00:09:11.260 --> 00:09:11.270 align:start position:0% about which blocks have been finalized 00:09:11.270 --> 00:09:12.579 align:start position:0% about which blocks have been finalized and<00:09:11.420> the<00:09:11.480> slashing<00:09:11.870> conditions<00:09:12.260> are<00:09:12.380> really 00:09:12.579 --> 00:09:12.589 align:start position:0% and the slashing conditions are really 00:09:12.589 --> 00:09:15.430 align:start position:0% and the slashing conditions are really really<00:09:12.770> simple<00:09:13.360> so<00:09:14.360> this<00:09:14.870> is<00:09:15.050> sort<00:09:15.290> of<00:09:15.350> a 00:09:15.430 --> 00:09:15.440 align:start position:0% really simple so this is sort of a 00:09:15.440 --> 00:09:17.440 align:start position:0% really simple so this is sort of a diagram<00:09:15.620> from<00:09:16.339> the<00:09:16.460> sharding<00:09:16.880> website<00:09:17.240> of 00:09:17.440 --> 00:09:17.450 align:start position:0% diagram from the sharding website of 00:09:17.450 --> 00:09:20.860 align:start position:0% diagram from the sharding website of what<00:09:18.080> the<00:09:18.529> cast<00:09:18.770> for<00:09:18.950> FG<00:09:19.400> fork<00:09:20.029> choice<00:09:20.300> rule<00:09:20.720> is 00:09:20.860 --> 00:09:20.870 align:start position:0% what the cast for FG fork choice rule is 00:09:20.870 --> 00:09:23.980 align:start position:0% what the cast for FG fork choice rule is doing<00:09:21.110> so<00:09:21.320> you<00:09:21.410> have<00:09:21.440> some<00:09:22.630> you<00:09:23.630> have<00:09:23.750> some 00:09:23.980 --> 00:09:23.990 align:start position:0% doing so you have some you have some 00:09:23.990 --> 00:09:25.990 align:start position:0% doing so you have some you have some check<00:09:24.260> points<00:09:24.620> which<00:09:24.800> are<00:09:24.950> getting<00:09:25.730> closer 00:09:25.990 --> 00:09:26.000 align:start position:0% check points which are getting closer 00:09:26.000 --> 00:09:27.610 align:start position:0% check points which are getting closer and<00:09:26.150> closer<00:09:26.450> to<00:09:26.720> being<00:09:26.750> justified<00:09:27.200> like<00:09:27.560> you 00:09:27.610 --> 00:09:27.620 align:start position:0% and closer to being justified like you 00:09:27.620 --> 00:09:29.290 align:start position:0% and closer to being justified like you always<00:09:27.890> follow<00:09:28.580> the<00:09:28.700> most<00:09:28.970> recently 00:09:29.290 --> 00:09:29.300 align:start position:0% always follow the most recently 00:09:29.300 --> 00:09:30.760 align:start position:0% always follow the most recently justified<00:09:29.779> check<00:09:30.020> point<00:09:30.260> but<00:09:30.410> then<00:09:30.529> you<00:09:30.620> also 00:09:30.760 --> 00:09:30.770 align:start position:0% justified check point but then you also 00:09:30.770 --> 00:09:32.970 align:start position:0% justified check point but then you also look<00:09:31.070> at<00:09:31.220> which<00:09:31.790> messages<00:09:32.300> people<00:09:32.540> are 00:09:32.970 --> 00:09:32.980 align:start position:0% look at which messages people are 00:09:32.980 --> 00:09:35.530 align:start position:0% look at which messages people are passing<00:09:33.980> around<00:09:34.070> on<00:09:34.460> unjustified<00:09:35.300> check 00:09:35.530 --> 00:09:35.540 align:start position:0% passing around on unjustified check 00:09:35.540 --> 00:09:37.180 align:start position:0% passing around on unjustified check points<00:09:35.839> and<00:09:35.900> use<00:09:36.080> that<00:09:36.260> to<00:09:36.410> influence<00:09:36.740> your 00:09:37.180 --> 00:09:37.190 align:start position:0% points and use that to influence your 00:09:37.190 --> 00:09:40.950 align:start position:0% points and use that to influence your your<00:09:38.150> your<00:09:38.630> target<00:09:39.620> block<00:09:39.980> on<00:09:40.220> the<00:09:40.339> main<00:09:40.670> chain 00:09:40.950 --> 00:09:40.960 align:start position:0% your your target block on the main chain 00:09:40.960 --> 00:09:43.630 align:start position:0% your your target block on the main chain so<00:09:41.960> shards<00:09:42.440> are<00:09:42.710> basically<00:09:43.070> freestanding 00:09:43.630 --> 00:09:43.640 align:start position:0% so shards are basically freestanding 00:09:43.640 --> 00:09:45.070 align:start position:0% so shards are basically freestanding chains<00:09:44.060> they're<00:09:44.270> secured<00:09:44.660> by<00:09:44.779> their<00:09:44.930> own 00:09:45.070 --> 00:09:45.080 align:start position:0% chains they're secured by their own 00:09:45.080 --> 00:09:47.650 align:start position:0% chains they're secured by their own consensus<00:09:45.740> algum<00:09:46.220> they're<00:09:46.640> typically<00:09:47.060> proof 00:09:47.650 --> 00:09:47.660 align:start position:0% consensus algum they're typically proof 00:09:47.660 --> 00:09:49.930 align:start position:0% consensus algum they're typically proof of<00:09:47.839> stake<00:09:48.250> and<00:09:49.250> they're<00:09:49.460> linked<00:09:49.760> to<00:09:49.880> the 00:09:49.930 --> 00:09:49.940 align:start position:0% of stake and they're linked to the 00:09:49.940 --> 00:09:51.610 align:start position:0% of stake and they're linked to the beacon<00:09:50.210> chain<00:09:50.390> via<00:09:50.570> these<00:09:50.779> cross-links<00:09:51.110> these 00:09:51.610 --> 00:09:51.620 align:start position:0% beacon chain via these cross-links these 00:09:51.620 --> 00:09:53.680 align:start position:0% beacon chain via these cross-links these at<00:09:51.770> attested<00:09:52.430> to<00:09:52.460> statements<00:09:53.150> that<00:09:53.300> make 00:09:53.680 --> 00:09:53.690 align:start position:0% at attested to statements that make 00:09:53.690 --> 00:09:56.800 align:start position:0% at attested to statements that make their<00:09:53.900> way<00:09:53.990> onto<00:09:54.200> the<00:09:54.380> beacon<00:09:54.680> chain<00:09:55.750> so<00:09:56.750> to 00:09:56.800 --> 00:09:56.810 align:start position:0% their way onto the beacon chain so to 00:09:56.810 --> 00:10:00.100 align:start position:0% their way onto the beacon chain so to look<00:09:57.350> a<00:09:57.500> bit<00:09:57.529> at<00:09:58.190> this<00:09:58.640> diagram<00:09:59.209> that<00:09:59.839> we<00:09:59.959> got 00:10:00.100 --> 00:10:00.110 align:start position:0% look a bit at this diagram that we got 00:10:00.110 --> 00:10:05.890 align:start position:0% look a bit at this diagram that we got from<00:10:00.970> Sal<00:10:01.970> way<00:10:02.180> and<00:10:03.050> Ben<00:10:03.230> Edgington<00:10:03.680> we<00:10:04.900> can 00:10:05.890 --> 00:10:05.900 align:start position:0% from Sal way and Ben Edgington we can 00:10:05.900 --> 00:10:07.240 align:start position:0% from Sal way and Ben Edgington we can see<00:10:06.140> that<00:10:06.350> the<00:10:06.500> the<00:10:06.740> architecture<00:10:07.220> of 00:10:07.240 --> 00:10:07.250 align:start position:0% see that the the architecture of 00:10:07.250 --> 00:10:08.530 align:start position:0% see that the the architecture of sharding<00:10:07.550> looks<00:10:07.730> something<00:10:07.910> like<00:10:08.029> this<00:10:08.270> so 00:10:08.530 --> 00:10:08.540 align:start position:0% sharding looks something like this so 00:10:08.540 --> 00:10:10.240 align:start position:0% sharding looks something like this so the<00:10:08.690> the<00:10:08.900> proof-of-work<00:10:09.290> main<00:10:09.620> chain<00:10:09.920> is<00:10:10.100> the 00:10:10.240 --> 00:10:10.250 align:start position:0% the the proof-of-work main chain is the 00:10:10.250 --> 00:10:11.769 align:start position:0% the the proof-of-work main chain is the anchor<00:10:10.640> layer<00:10:10.820> this<00:10:11.120> is<00:10:11.270> actually<00:10:11.570> like<00:10:11.660> the 00:10:11.769 --> 00:10:11.779 align:start position:0% anchor layer this is actually like the 00:10:11.779 --> 00:10:14.110 align:start position:0% anchor layer this is actually like the etherium<00:10:12.230> 1.0<00:10:12.860> chain<00:10:13.130> it's<00:10:13.550> got<00:10:13.730> this<00:10:13.820> one 00:10:14.110 --> 00:10:14.120 align:start position:0% etherium 1.0 chain it's got this one 00:10:14.120 --> 00:10:16.780 align:start position:0% etherium 1.0 chain it's got this one directional<00:10:14.779> lock<00:10:15.709> up<00:10:15.950> stuff<00:10:16.220> where<00:10:16.490> you<00:10:16.550> can 00:10:16.780 --> 00:10:16.790 align:start position:0% directional lock up stuff where you can 00:10:16.790 --> 00:10:18.490 align:start position:0% directional lock up stuff where you can basically<00:10:17.270> lock<00:10:17.630> up<00:10:17.810> your<00:10:17.839> ether<00:10:18.260> on<00:10:18.380> the 00:10:18.490 --> 00:10:18.500 align:start position:0% basically lock up your ether on the 00:10:18.500 --> 00:10:21.280 align:start position:0% basically lock up your ether on the existing<00:10:18.980> chain<00:10:19.250> move<00:10:19.850> it<00:10:20.060> over<00:10:20.390> to<00:10:20.720> the<00:10:21.020> the 00:10:21.280 --> 00:10:21.290 align:start position:0% existing chain move it over to the the 00:10:21.290 --> 00:10:23.290 align:start position:0% existing chain move it over to the the beacon<00:10:21.620> chain<00:10:21.860> and<00:10:22.130> then<00:10:22.520> get<00:10:22.790> the<00:10:23.000> beacon 00:10:23.290 --> 00:10:23.300 align:start position:0% beacon chain and then get the beacon 00:10:23.300 --> 00:10:25.870 align:start position:0% beacon chain and then get the beacon chain<00:10:23.570> tokens<00:10:24.110> for<00:10:24.410> for<00:10:25.010> participating<00:10:25.640> as<00:10:25.850> a 00:10:25.870 --> 00:10:25.880 align:start position:0% chain tokens for for participating as a 00:10:25.880 --> 00:10:28.810 align:start position:0% chain tokens for for participating as a validator<00:10:26.300> there<00:10:27.130> other<00:10:28.130> than<00:10:28.370> that<00:10:28.490> it's<00:10:28.670> not 00:10:28.810 --> 00:10:28.820 align:start position:0% validator there other than that it's not 00:10:28.820 --> 00:10:32.740 align:start position:0% validator there other than that it's not particularly<00:10:29.270> relevant<00:10:31.209> the<00:10:32.209> beacon<00:10:32.540> chain 00:10:32.740 --> 00:10:32.750 align:start position:0% particularly relevant the beacon chain 00:10:32.750 --> 00:10:34.060 align:start position:0% particularly relevant the beacon chain is<00:10:32.930> doing<00:10:33.110> this<00:10:33.200> random<00:10:33.500> speakin<00:10:33.860> stuff 00:10:34.060 --> 00:10:34.070 align:start position:0% is doing this random speakin stuff 00:10:34.070 --> 00:10:36.120 align:start position:0% is doing this random speakin stuff coordinating<00:10:34.760> between<00:10:34.850> validator<00:10:35.450> sets<00:10:35.690> and 00:10:36.120 --> 00:10:36.130 align:start position:0% coordinating between validator sets and 00:10:36.130 --> 00:10:38.320 align:start position:0% coordinating between validator sets and the<00:10:37.130> shard<00:10:37.370> chains<00:10:37.730> are<00:10:37.910> actually<00:10:38.180> doing 00:10:38.320 --> 00:10:38.330 align:start position:0% the shard chains are actually doing 00:10:38.330 --> 00:10:40.510 align:start position:0% the shard chains are actually doing computations<00:10:39.140> with<00:10:39.350> a<00:10:39.380> web<00:10:39.830> assembly<00:10:40.190> virtual 00:10:40.510 --> 00:10:40.520 align:start position:0% computations with a web assembly virtual 00:10:40.520 --> 00:10:43.060 align:start position:0% computations with a web assembly virtual machine<00:10:40.930> so<00:10:41.930> now<00:10:42.050> I'll<00:10:42.170> get<00:10:42.290> into<00:10:42.470> the<00:10:42.770> the 00:10:43.060 --> 00:10:43.070 align:start position:0% machine so now I'll get into the the 00:10:43.070 --> 00:10:45.670 align:start position:0% machine so now I'll get into the the part<00:10:43.279> of<00:10:43.430> basically<00:10:43.850> our<00:10:44.680> implementation 00:10:45.670 --> 00:10:45.680 align:start position:0% part of basically our implementation 00:10:45.680 --> 00:10:47.860 align:start position:0% part of basically our implementation progress<00:10:46.339> like<00:10:46.730> wherewhere<00:10:47.330> are<00:10:47.360> we<00:10:47.480> with 00:10:47.860 --> 00:10:47.870 align:start position:0% progress like wherewhere are we with 00:10:47.870 --> 00:10:51.519 align:start position:0% progress like wherewhere are we with that<00:10:49.029> so<00:10:50.029> I'll<00:10:50.209> first<00:10:50.720> I'll<00:10:50.990> zoom<00:10:51.200> back<00:10:51.470> in 00:10:51.519 --> 00:10:51.529 align:start position:0% that so I'll first I'll zoom back in 00:10:51.529 --> 00:10:56.290 align:start position:0% that so I'll first I'll zoom back in time<00:10:54.100> originally<00:10:55.100> there<00:10:55.490> was<00:10:55.610> a<00:10:55.670> plan<00:10:55.940> to<00:10:55.970> have 00:10:56.290 --> 00:10:56.300 align:start position:0% time originally there was a plan to have 00:10:56.300 --> 00:11:00.040 align:start position:0% time originally there was a plan to have a<00:10:56.330> hard<00:10:56.630> fork<00:10:56.959> in<00:10:57.200> aetherium<00:10:58.029> to<00:10:59.029> to<00:10:59.630> implement 00:11:00.040 --> 00:11:00.050 align:start position:0% a hard fork in aetherium to to implement 00:11:00.050 --> 00:11:04.840 align:start position:0% a hard fork in aetherium to to implement casper<00:11:00.470> FFG<00:11:01.150> 2<00:11:02.150> to<00:11:02.780> hard<00:11:03.440> fork<00:11:03.800> the<00:11:04.520> etherion 00:11:04.840 --> 00:11:04.850 align:start position:0% casper FFG 2 to hard fork the etherion 00:11:04.850 --> 00:11:08.140 align:start position:0% casper FFG 2 to hard fork the etherion main<00:11:05.000> chain<00:11:05.240> that<00:11:05.329> we're<00:11:05.480> using<00:11:05.630> now<00:11:05.930> and<00:11:06.760> make 00:11:08.140 --> 00:11:08.150 align:start position:0% main chain that we're using now and make 00:11:08.150 --> 00:11:10.210 align:start position:0% main chain that we're using now and make Kaspar<00:11:08.480> FG<00:11:08.900> hybrid<00:11:09.380> consensus<00:11:09.830> model<00:11:10.070> with 00:11:10.210 --> 00:11:10.220 align:start position:0% Kaspar FG hybrid consensus model with 00:11:10.220 --> 00:11:11.410 align:start position:0% Kaspar FG hybrid consensus model with the<00:11:10.340> proof<00:11:10.520> of<00:11:10.610> work<00:11:10.760> that's<00:11:11.000> going<00:11:11.120> on<00:11:11.240> there 00:11:11.410 --> 00:11:11.420 align:start position:0% the proof of work that's going on there 00:11:11.420 --> 00:11:13.690 align:start position:0% the proof of work that's going on there so<00:11:11.570> we<00:11:11.720> the<00:11:12.380> first<00:11:12.650> step<00:11:13.190> that<00:11:13.220> we<00:11:13.520> took 00:11:13.690 --> 00:11:13.700 align:start position:0% so we the first step that we took 00:11:13.700 --> 00:11:16.000 align:start position:0% so we the first step that we took towards<00:11:13.910> sharding<00:11:14.480> shortly<00:11:15.440> after<00:11:15.710> the<00:11:15.830> Thai 00:11:16.000 --> 00:11:16.010 align:start position:0% towards sharding shortly after the Thai 00:11:16.010 --> 00:11:19.480 align:start position:0% towards sharding shortly after the Thai Taiwan<00:11:16.820> summit<00:11:17.320> was<00:11:18.320> to<00:11:18.620> do<00:11:19.100> this 00:11:19.480 --> 00:11:19.490 align:start position:0% Taiwan summit was to do this 00:11:19.490 --> 00:11:20.950 align:start position:0% Taiwan summit was to do this implementation<00:11:20.090> so<00:11:20.390> that's<00:11:20.540> been<00:11:20.720> closed 00:11:20.950 --> 00:11:20.960 align:start position:0% implementation so that's been closed 00:11:20.960 --> 00:11:23.620 align:start position:0% implementation so that's been closed because<00:11:21.200> this<00:11:21.440> plan<00:11:21.680> has<00:11:21.920> been<00:11:22.430> abandoned<00:11:22.910> but 00:11:23.620 --> 00:11:23.630 align:start position:0% because this plan has been abandoned but 00:11:23.630 --> 00:11:26.770 align:start position:0% because this plan has been abandoned but we<00:11:23.750> did<00:11:24.350> this<00:11:24.590> work<00:11:25.130> we<00:11:25.670> spun<00:11:26.150> up<00:11:26.300> a<00:11:26.390> test<00:11:26.600> net 00:11:26.770 --> 00:11:26.780 align:start position:0% we did this work we spun up a test net 00:11:26.780 --> 00:11:28.690 align:start position:0% we did this work we spun up a test net and<00:11:26.930> we<00:11:26.990> showed<00:11:27.230> that<00:11:27.260> it<00:11:27.680> was<00:11:27.710> at<00:11:28.190> least<00:11:28.430> in<00:11:28.610> a 00:11:28.690 --> 00:11:28.700 align:start position:0% and we showed that it was at least in a 00:11:28.700 --> 00:11:31.690 align:start position:0% and we showed that it was at least in a proof<00:11:28.880> of<00:11:28.940> concept<00:11:29.120> stage<00:11:29.980> so<00:11:30.980> now<00:11:31.160> that<00:11:31.220> the 00:11:31.690 --> 00:11:31.700 align:start position:0% proof of concept stage so now that the 00:11:31.700 --> 00:11:33.300 align:start position:0% proof of concept stage so now that the the<00:11:31.730> plan<00:11:32.000> has<00:11:32.210> pivoted<00:11:32.390> somewhat<00:11:32.930> to 00:11:33.300 --> 00:11:33.310 align:start position:0% the plan has pivoted somewhat to 00:11:33.310 --> 00:11:36.360 align:start position:0% the plan has pivoted somewhat to incorporate<00:11:34.310> this<00:11:34.460> beacon<00:11:34.820> chain 00:11:36.360 --> 00:11:36.370 align:start position:0% incorporate this beacon chain 00:11:36.370 --> 00:11:39.550 align:start position:0% incorporate this beacon chain architecture<00:11:37.370> and<00:11:37.550> we<00:11:38.330> are<00:11:38.450> doing<00:11:38.810> parody 00:11:39.550 --> 00:11:39.560 align:start position:0% architecture and we are doing parody 00:11:39.560 --> 00:11:43.270 align:start position:0% architecture and we are doing parody tech<00:11:39.760> /jasper<00:11:40.760> is<00:11:41.180> the<00:11:41.390> repository<00:11:42.040> so<00:11:43.040> the 00:11:43.270 --> 00:11:43.280 align:start position:0% tech /jasper is the repository so the 00:11:43.280 --> 00:11:44.590 align:start position:0% tech /jasper is the repository so the developer<00:11:43.700> who's<00:11:43.820> been<00:11:44.000> doing<00:11:44.120> most<00:11:44.420> of<00:11:44.540> the 00:11:44.590 --> 00:11:44.600 align:start position:0% developer who's been doing most of the 00:11:44.600 --> 00:11:46.240 align:start position:0% developer who's been doing most of the work<00:11:44.660> on<00:11:44.930> this<00:11:45.020> is<00:11:45.230> a<00:11:45.260> guy<00:11:45.530> called<00:11:45.740> wait<00:11:46.010> I'm 00:11:46.240 --> 00:11:46.250 align:start position:0% work on this is a guy called wait I'm 00:11:46.250 --> 00:11:49.960 align:start position:0% work on this is a guy called wait I'm from<00:11:46.550> China<00:11:48.130> we've<00:11:49.130> the<00:11:49.640> rest<00:11:49.790> of<00:11:49.910> the 00:11:49.960 --> 00:11:49.970 align:start position:0% from China we've the rest of the 00:11:49.970 --> 00:11:51.340 align:start position:0% from China we've the rest of the substrate<00:11:50.330> team<00:11:50.480> has<00:11:50.630> been<00:11:50.780> contributing 00:11:51.340 --> 00:11:51.350 align:start position:0% substrate team has been contributing 00:11:51.350 --> 00:11:53.110 align:start position:0% substrate team has been contributing bits<00:11:51.560> and<00:11:51.740> pieces<00:11:51.890> through<00:11:52.280> architecture<00:11:52.940> and 00:11:53.110 --> 00:11:53.120 align:start position:0% bits and pieces through architecture and 00:11:53.120 --> 00:11:54.580 align:start position:0% bits and pieces through architecture and pluggable<00:11:53.660> consensus<00:11:54.140> and<00:11:54.230> that<00:11:54.350> sort<00:11:54.530> of 00:11:54.580 --> 00:11:54.590 align:start position:0% pluggable consensus and that sort of 00:11:54.590 --> 00:11:56.500 align:start position:0% pluggable consensus and that sort of thing<00:11:54.770> basically<00:11:55.640> this<00:11:55.970> is<00:11:56.120> a<00:11:56.150> repository 00:11:56.500 --> 00:11:56.510 align:start position:0% thing basically this is a repository 00:11:56.510 --> 00:11:59.380 align:start position:0% thing basically this is a repository that<00:11:56.930> contains<00:11:57.520> more<00:11:58.520> or<00:11:58.670> less<00:11:58.820> everything 00:11:59.380 --> 00:11:59.390 align:start position:0% that contains more or less everything 00:11:59.390 --> 00:12:01.050 align:start position:0% that contains more or less everything that's<00:11:59.600> pecked<00:11:59.900> out<00:12:00.110> in<00:12:00.470> the 00:12:01.050 --> 00:12:01.060 align:start position:0% that's pecked out in the 00:12:01.060 --> 00:12:03.520 align:start position:0% that's pecked out in the state-transition<00:12:02.060> aspect<00:12:02.990> of<00:12:03.110> the<00:12:03.230> beacon 00:12:03.520 --> 00:12:03.530 align:start position:0% state-transition aspect of the beacon 00:12:03.530 --> 00:12:06.280 align:start position:0% state-transition aspect of the beacon chain<00:12:03.740> block<00:12:04.730> authorship<00:12:05.270> etc<00:12:05.720> is<00:12:05.810> still<00:12:06.050> to 00:12:06.280 --> 00:12:06.290 align:start position:0% chain block authorship etc is still to 00:12:06.290 --> 00:12:09.700 align:start position:0% chain block authorship etc is still to do<00:12:06.470> but<00:12:07.070> as<00:12:07.700> those<00:12:08.270> parts<00:12:08.600> are<00:12:08.720> further<00:12:09.410> Specht 00:12:09.700 --> 00:12:09.710 align:start position:0% do but as those parts are further Specht 00:12:09.710 --> 00:12:12.760 align:start position:0% do but as those parts are further Specht out<00:12:09.860> those<00:12:10.130> will<00:12:10.340> be<00:12:10.460> added<00:12:10.690> so<00:12:11.690> most<00:12:12.530> of<00:12:12.680> it 00:12:12.760 --> 00:12:12.770 align:start position:0% out those will be added so most of it 00:12:12.770 --> 00:12:15.520 align:start position:0% out those will be added so most of it exists<00:12:13.430> as<00:12:13.550> a<00:12:14.000> runtime<00:12:14.600> that<00:12:14.660> piece<00:12:15.110> of<00:12:15.320> web 00:12:15.520 --> 00:12:15.530 align:start position:0% exists as a runtime that piece of web 00:12:15.530 --> 00:12:18.010 align:start position:0% exists as a runtime that piece of web assembly<00:12:16.010> code<00:12:16.220> that<00:12:16.910> actually<00:12:17.030> processes 00:12:18.010 --> 00:12:18.020 align:start position:0% assembly code that actually processes 00:12:18.020 --> 00:12:21.940 align:start position:0% assembly code that actually processes the<00:12:18.170> logic<00:12:18.530> of<00:12:18.680> the<00:12:18.800> chain<00:12:19.010> so<00:12:20.560> what<00:12:21.560> this<00:12:21.680> is 00:12:21.940 --> 00:12:21.950 align:start position:0% the logic of the chain so what this is 00:12:21.950 --> 00:12:24.270 align:start position:0% the logic of the chain so what this is is<00:12:22.270> processing<00:12:23.270> new<00:12:23.450> at<00:12:23.600> two<00:12:23.780> stations 00:12:24.270 --> 00:12:24.280 align:start position:0% is processing new at two stations 00:12:24.280 --> 00:12:26.260 align:start position:0% is processing new at two stations crystallizing<00:12:25.280> them<00:12:25.460> handling<00:12:26.090> new 00:12:26.260 --> 00:12:26.270 align:start position:0% crystallizing them handling new 00:12:26.270 --> 00:12:28.540 align:start position:0% crystallizing them handling new validator<00:12:26.750> set<00:12:26.960> changes<00:12:27.440> and<00:12:28.070> that<00:12:28.250> sort<00:12:28.490> of 00:12:28.540 --> 00:12:28.550 align:start position:0% validator set changes and that sort of 00:12:28.550 --> 00:12:29.230 align:start position:0% validator set changes and that sort of thing 00:12:29.230 --> 00:12:29.240 align:start position:0% thing 00:12:29.240 --> 00:12:31.540 align:start position:0% thing substrates<00:12:30.020> native<00:12:30.470> block<00:12:30.740> formats<00:12:31.220> are<00:12:31.490> a 00:12:31.540 --> 00:12:31.550 align:start position:0% substrates native block formats are a 00:12:31.550 --> 00:12:34.420 align:start position:0% substrates native block formats are a bit<00:12:31.940> different<00:12:32.360> than<00:12:32.650> the<00:12:33.650> ones<00:12:33.860> that<00:12:34.190> the 00:12:34.420 --> 00:12:34.430 align:start position:0% bit different than the ones that the 00:12:34.430 --> 00:12:36.070 align:start position:0% bit different than the ones that the beacon<00:12:34.730> chain<00:12:34.970> uses<00:12:35.330> so<00:12:35.480> the<00:12:35.570> beacon<00:12:35.870> chain 00:12:36.070 --> 00:12:36.080 align:start position:0% beacon chain uses so the beacon chain 00:12:36.080 --> 00:12:38.050 align:start position:0% beacon chain uses so the beacon chain will<00:12:36.260> have<00:12:36.410> fields<00:12:36.830> like<00:12:36.980> the<00:12:37.460> R<00:12:37.490> and<00:12:37.850> I'll 00:12:38.050 --> 00:12:38.060 align:start position:0% will have fields like the R and I'll 00:12:38.060 --> 00:12:41.110 align:start position:0% will have fields like the R and I'll reveal<00:12:38.360> or<00:12:38.660> a<00:12:38.690> pin<00:12:39.200> to<00:12:39.560> the<00:12:40.120> proof-of-work 00:12:41.110 --> 00:12:41.120 align:start position:0% reveal or a pin to the proof-of-work 00:12:41.120 --> 00:12:42.670 align:start position:0% reveal or a pin to the proof-of-work chain<00:12:41.570> the<00:12:41.750> anchor<00:12:42.080> layer<00:12:42.290> that<00:12:42.530> it's 00:12:42.670 --> 00:12:42.680 align:start position:0% chain the anchor layer that it's 00:12:42.680 --> 00:12:44.020 align:start position:0% chain the anchor layer that it's attached<00:12:42.950> to 00:12:44.020 --> 00:12:44.030 align:start position:0% attached to 00:12:44.030 --> 00:12:46.030 align:start position:0% attached to but<00:12:44.510> substrates<00:12:44.990> native<00:12:45.260> lock<00:12:45.440> formats<00:12:45.830> don't 00:12:46.030 --> 00:12:46.040 align:start position:0% but substrates native lock formats don't 00:12:46.040 --> 00:12:48.130 align:start position:0% but substrates native lock formats don't really<00:12:46.250> have<00:12:46.430> that<00:12:46.460> stuff<00:12:46.970> so<00:12:47.780> we<00:12:47.870> use<00:12:47.990> an 00:12:48.130 --> 00:12:48.140 align:start position:0% really have that stuff so we use an 00:12:48.140 --> 00:12:51.960 align:start position:0% really have that stuff so we use an adaptor<00:12:48.680> so<00:12:48.710> basically<00:12:49.250> on<00:12:49.460> disk<00:12:50.200> we've<00:12:51.200> got<00:12:51.440> a 00:12:51.960 --> 00:12:51.970 align:start position:0% adaptor so basically on disk we've got a 00:12:51.970 --> 00:12:57.730 align:start position:0% adaptor so basically on disk we've got a like<00:12:52.970> one<00:12:53.270> one<00:12:53.720> set<00:12:54.050> of<00:12:54.230> of<00:12:55.840> block<00:12:56.840> types<00:12:57.140> which 00:12:57.730 --> 00:12:57.740 align:start position:0% like one one set of of block types which 00:12:57.740 --> 00:12:59.260 align:start position:0% like one one set of of block types which are<00:12:57.920> the<00:12:58.070> substrate<00:12:58.550> block<00:12:58.730> types<00:12:59.000> where 00:12:59.260 --> 00:12:59.270 align:start position:0% are the substrate block types where 00:12:59.270 --> 00:13:01.120 align:start position:0% are the substrate block types where these<00:12:59.390> extra<00:13:00.230> values<00:13:00.530> are<00:13:00.680> encoded<00:13:01.040> as 00:13:01.120 --> 00:13:01.130 align:start position:0% these extra values are encoded as 00:13:01.130 --> 00:13:05.830 align:start position:0% these extra values are encoded as extrinsic<00:13:01.610> s--<00:13:01.820> and<00:13:02.170> on<00:13:03.170> the<00:13:04.600> on<00:13:05.600> the 00:13:05.830 --> 00:13:05.840 align:start position:0% extrinsic s-- and on the on the 00:13:05.840 --> 00:13:07.690 align:start position:0% extrinsic s-- and on the on the networking<00:13:06.170> layer<00:13:06.320> we've<00:13:06.680> we've<00:13:07.010> transformed 00:13:07.690 --> 00:13:07.700 align:start position:0% networking layer we've we've transformed 00:13:07.700 --> 00:13:10.960 align:start position:0% networking layer we've we've transformed them<00:13:08.030> into<00:13:08.060> Shaffer<00:13:08.990> or<00:13:09.500> serenity<00:13:10.250> blocks<00:13:10.520> so 00:13:10.960 --> 00:13:10.970 align:start position:0% them into Shaffer or serenity blocks so 00:13:10.970 --> 00:13:12.310 align:start position:0% them into Shaffer or serenity blocks so that<00:13:11.120> when<00:13:11.540> you<00:13:11.660> communicate<00:13:11.840> with<00:13:12.260> other 00:13:12.310 --> 00:13:12.320 align:start position:0% that when you communicate with other 00:13:12.320 --> 00:13:14.350 align:start position:0% that when you communicate with other nodes<00:13:12.830> like<00:13:13.190> those<00:13:13.400> perhaps<00:13:13.970> built<00:13:14.210> by 00:13:14.350 --> 00:13:14.360 align:start position:0% nodes like those perhaps built by 00:13:14.360 --> 00:13:17.500 align:start position:0% nodes like those perhaps built by prismatic<00:13:14.900> labs<00:13:15.140> or<00:13:15.710> where<00:13:16.220> lighthouse<00:13:16.670> that 00:13:17.500 --> 00:13:17.510 align:start position:0% prismatic labs or where lighthouse that 00:13:17.510 --> 00:13:19.060 align:start position:0% prismatic labs or where lighthouse that they're<00:13:17.780> all<00:13:17.960> using<00:13:17.990> the<00:13:18.350> same<00:13:18.380> block<00:13:18.740> format 00:13:19.060 --> 00:13:19.070 align:start position:0% they're all using the same block format 00:13:19.070 --> 00:13:20.680 align:start position:0% they're all using the same block format but<00:13:19.190> actually<00:13:19.670> under<00:13:19.940> the<00:13:20.060> hood<00:13:20.240> it's<00:13:20.390> using<00:13:20.630> a 00:13:20.680 --> 00:13:20.690 align:start position:0% but actually under the hood it's using a 00:13:20.690 --> 00:13:23.010 align:start position:0% but actually under the hood it's using a different<00:13:21.020> block 00:13:23.010 --> 00:13:23.020 align:start position:0% different block 00:13:23.020 --> 00:13:24.660 align:start position:0% different block if<00:13:23.260> you're<00:13:23.440> into<00:13:23.680> porno<00:13:23.950> is<00:13:24.100> very<00:13:24.310> likely<00:13:24.490> to 00:13:24.660 --> 00:13:24.670 align:start position:0% if you're into porno is very likely to 00:13:24.670 --> 00:13:29.100 align:start position:0% if you're into porno is very likely to use<00:13:25.000> lib<00:13:25.660> p2p<00:13:26.230> for<00:13:26.820> networking<00:13:27.820> so<00:13:28.330> substrate 00:13:29.100 --> 00:13:29.110 align:start position:0% use lib p2p for networking so substrate 00:13:29.110 --> 00:13:32.580 align:start position:0% use lib p2p for networking so substrate has<00:13:29.920> been<00:13:30.700> using<00:13:31.030> lib<00:13:31.330> p2p<00:13:31.780> from<00:13:31.990> day<00:13:32.170> one<00:13:32.380> I 00:13:32.580 --> 00:13:32.590 align:start position:0% has been using lib p2p from day one I 00:13:32.590 --> 00:13:35.700 align:start position:0% has been using lib p2p from day one I parody<00:13:33.280> we<00:13:33.370> even<00:13:33.550> did<00:13:33.910> well<00:13:34.420> to<00:13:34.840> whine<00:13:35.440> back<00:13:35.680> a 00:13:35.700 --> 00:13:35.710 align:start position:0% parody we even did well to whine back a 00:13:35.710 --> 00:13:37.350 align:start position:0% parody we even did well to whine back a little<00:13:35.920> bit<00:13:36.100> lib<00:13:36.370> p2p<00:13:36.820> is<00:13:36.940> a<00:13:36.970> set<00:13:37.240> of 00:13:37.350 --> 00:13:37.360 align:start position:0% little bit lib p2p is a set of 00:13:37.360 --> 00:13:39.450 align:start position:0% little bit lib p2p is a set of networking<00:13:37.720> libraries<00:13:38.230> first<00:13:39.040> designed 00:13:39.450 --> 00:13:39.460 align:start position:0% networking libraries first designed 00:13:39.460 --> 00:13:42.200 align:start position:0% networking libraries first designed built<00:13:39.910> and<00:13:40.090> described<00:13:40.600> by<00:13:40.900> protocol<00:13:41.350> labs<00:13:41.590> of 00:13:42.200 --> 00:13:42.210 align:start position:0% built and described by protocol labs of 00:13:42.210 --> 00:13:46.860 align:start position:0% built and described by protocol labs of ipfs<00:13:43.210> and<00:13:43.540> file<00:13:43.900> coin<00:13:44.200> so<00:13:44.620> this<00:13:45.400> is<00:13:45.700> a<00:13:46.000> intended 00:13:46.860 --> 00:13:46.870 align:start position:0% ipfs and file coin so this is a intended 00:13:46.870 --> 00:13:48.690 align:start position:0% ipfs and file coin so this is a intended to<00:13:47.050> be<00:13:47.140> a<00:13:47.170> set<00:13:47.410> of<00:13:47.530> cross-platform<00:13:48.160> and 00:13:48.690 --> 00:13:48.700 align:start position:0% to be a set of cross-platform and 00:13:48.700 --> 00:13:51.060 align:start position:0% to be a set of cross-platform and future-proof<00:13:49.330> networking<00:13:49.810> libraries<00:13:50.320> at 00:13:51.060 --> 00:13:51.070 align:start position:0% future-proof networking libraries at 00:13:51.070 --> 00:13:52.770 align:start position:0% future-proof networking libraries at parity<00:13:51.460> we<00:13:51.580> did<00:13:51.730> an<00:13:51.820> implementation<00:13:52.540> of<00:13:52.660> those 00:13:52.770 --> 00:13:52.780 align:start position:0% parity we did an implementation of those 00:13:52.780 --> 00:13:55.440 align:start position:0% parity we did an implementation of those in<00:13:52.990> rust<00:13:53.230> and<00:13:53.560> we've<00:13:53.650> given<00:13:53.830> that<00:13:54.070> back<00:13:54.250> to<00:13:55.180> to 00:13:55.440 --> 00:13:55.450 align:start position:0% in rust and we've given that back to to 00:13:55.450 --> 00:13:57.980 align:start position:0% in rust and we've given that back to to open<00:13:55.570> source<00:13:55.870> and<00:13:56.140> we're<00:13:56.290> in<00:13:56.890> the<00:13:57.040> process<00:13:57.070> of 00:13:57.980 --> 00:13:57.990 align:start position:0% open source and we're in the process of 00:13:57.990 --> 00:14:01.500 align:start position:0% open source and we're in the process of moving<00:13:58.990> that<00:13:59.380> over<00:13:59.770> to<00:14:00.010> to<00:14:00.850> parity<00:14:01.150> etherium 00:14:01.500 --> 00:14:01.510 align:start position:0% moving that over to to parity etherium 00:14:01.510 --> 00:14:03.690 align:start position:0% moving that over to to parity etherium as<00:14:01.630> well<00:14:01.750> so<00:14:01.900> the<00:14:01.990> parity<00:14:02.290> etherium<00:14:02.650> can<00:14:02.950> use 00:14:03.690 --> 00:14:03.700 align:start position:0% as well so the parity etherium can use 00:14:03.700 --> 00:14:06.240 align:start position:0% as well so the parity etherium can use lib<00:14:04.420> p2p<00:14:04.780> as<00:14:04.870> a<00:14:04.900> backing<00:14:05.140> network<00:14:05.500> but<00:14:06.160> we're 00:14:06.240 --> 00:14:06.250 align:start position:0% lib p2p as a backing network but we're 00:14:06.250 --> 00:14:08.190 align:start position:0% lib p2p as a backing network but we're also<00:14:06.400> building<00:14:06.820> substrate<00:14:07.300> out<00:14:07.480> with<00:14:07.960> Libby 00:14:08.190 --> 00:14:08.200 align:start position:0% also building substrate out with Libby 00:14:08.200 --> 00:14:12.450 align:start position:0% also building substrate out with Libby TPS<00:14:08.590> first-class<00:14:09.100> networking<00:14:10.320> so<00:14:11.320> the<00:14:12.070> next 00:14:12.450 --> 00:14:12.460 align:start position:0% TPS first-class networking so the next 00:14:12.460 --> 00:14:15.090 align:start position:0% TPS first-class networking so the next steps<00:14:12.910> like<00:14:13.900> what's<00:14:14.170> what's<00:14:14.500> next<00:14:14.920> in<00:14:15.010> the 00:14:15.090 --> 00:14:15.100 align:start position:0% steps like what's what's next in the 00:14:15.100 --> 00:14:16.770 align:start position:0% steps like what's what's next in the implementation<00:14:15.370> side<00:14:15.970> of<00:14:16.150> things<00:14:16.360> for<00:14:16.480> if 00:14:16.770 --> 00:14:16.780 align:start position:0% implementation side of things for if 00:14:16.780 --> 00:14:20.210 align:start position:0% implementation side of things for if your<00:14:16.960> IAM<00:14:17.050> to<00:14:17.200> point<00:14:17.410> out<00:14:17.500> for<00:14:17.740> us<00:14:18.480> we<00:14:19.480> are 00:14:20.210 --> 00:14:20.220 align:start position:0% your IAM to point out for us we are 00:14:20.220 --> 00:14:22.980 align:start position:0% your IAM to point out for us we are going<00:14:21.220> to<00:14:21.400> see<00:14:21.580> this<00:14:21.760> through<00:14:22.150> the<00:14:22.510> parody<00:14:22.900> is 00:14:22.980 --> 00:14:22.990 align:start position:0% going to see this through the parody is 00:14:22.990 --> 00:14:25.980 align:start position:0% going to see this through the parody is 100%<00:14:23.500> committed<00:14:24.190> to<00:14:24.490> finishing<00:14:25.090> the<00:14:25.570> etherium 00:14:25.980 --> 00:14:25.990 align:start position:0% 100% committed to finishing the etherium 00:14:25.990 --> 00:14:35.790 align:start position:0% 100% committed to finishing the etherium 2.0<00:14:26.470> implementation<00:14:31.350> thank<00:14:32.350> you<00:14:34.110> so<00:14:35.110> the<00:14:35.770> next 00:14:35.790 --> 00:14:35.800 align:start position:0% 2.0 implementation thank you so the next 00:14:35.800 --> 00:14:38.310 align:start position:0% 2.0 implementation thank you so the next step<00:14:36.190> will<00:14:36.400> be<00:14:36.430> basically<00:14:37.030> better<00:14:37.720> pluggable 00:14:38.310 --> 00:14:38.320 align:start position:0% step will be basically better pluggable 00:14:38.320 --> 00:14:38.970 align:start position:0% step will be basically better pluggable consensus 00:14:38.970 --> 00:14:38.980 align:start position:0% consensus 00:14:38.980 --> 00:14:41.540 align:start position:0% consensus so<00:14:39.130> we've<00:14:39.490> now<00:14:40.000> just<00:14:40.450> in<00:14:40.570> the<00:14:40.630> past<00:14:40.870> few<00:14:41.050> days 00:14:41.540 --> 00:14:41.550 align:start position:0% so we've now just in the past few days 00:14:41.550 --> 00:14:44.010 align:start position:0% so we've now just in the past few days merged<00:14:42.550> the<00:14:42.880> commits<00:14:43.180> into<00:14:43.450> substrate<00:14:43.900> that 00:14:44.010 --> 00:14:44.020 align:start position:0% merged the commits into substrate that 00:14:44.020 --> 00:14:46.050 align:start position:0% merged the commits into substrate that generalized<00:14:44.650> the<00:14:44.860> consensus<00:14:45.430> framework<00:14:45.910> I 00:14:46.050 --> 00:14:46.060 align:start position:0% generalized the consensus framework I 00:14:46.060 --> 00:14:47.880 align:start position:0% generalized the consensus framework I think<00:14:46.090> I've<00:14:46.360> got<00:14:46.540> a<00:14:46.570> picture<00:14:47.080> of<00:14:47.200> this<00:14:47.350> so 00:14:47.880 --> 00:14:47.890 align:start position:0% think I've got a picture of this so 00:14:47.890 --> 00:14:50.100 align:start position:0% think I've got a picture of this so we've<00:14:48.880> merged<00:14:49.150> this<00:14:49.540> this<00:14:49.840> pull<00:14:50.080> request 00:14:50.100 --> 00:14:50.110 align:start position:0% we've merged this this pull request 00:14:50.110 --> 00:14:52.860 align:start position:0% we've merged this this pull request you've<00:14:50.590> got<00:14:50.710> a<00:14:50.740> few<00:14:51.010> more<00:14:51.130> coming<00:14:51.520> what's<00:14:52.510> next 00:14:52.860 --> 00:14:52.870 align:start position:0% you've got a few more coming what's next 00:14:52.870 --> 00:14:54.900 align:start position:0% you've got a few more coming what's next is<00:14:52.960> basically<00:14:53.080> to<00:14:53.560> implement<00:14:54.040> cast<00:14:54.250> for<00:14:54.460> FFG 00:14:54.900 --> 00:14:54.910 align:start position:0% is basically to implement cast for FFG 00:14:54.910 --> 00:14:57.060 align:start position:0% is basically to implement cast for FFG on<00:14:55.120> substrate<00:14:55.720> start<00:14:56.320> to<00:14:56.440> do<00:14:56.590> that<00:14:56.770> block 00:14:57.060 --> 00:14:57.070 align:start position:0% on substrate start to do that block 00:14:57.070 --> 00:15:00.300 align:start position:0% on substrate start to do that block authorship<00:14:57.700> work<00:14:58.050> so<00:14:59.050> that<00:14:59.230> not<00:15:00.010> just 00:15:00.300 --> 00:15:00.310 align:start position:0% authorship work so that not just 00:15:00.310 --> 00:15:02.490 align:start position:0% authorship work so that not just processing<00:15:00.880> the<00:15:01.030> blocks<00:15:01.330> is<00:15:01.540> done<00:15:01.720> on<00:15:01.960> our<00:15:02.110> on 00:15:02.490 --> 00:15:02.500 align:start position:0% processing the blocks is done on our on 00:15:02.500 --> 00:15:04.290 align:start position:0% processing the blocks is done on our on our<00:15:02.620> Shaffer<00:15:03.070> repo<00:15:03.370> but<00:15:03.550> actually<00:15:03.880> authoring 00:15:04.290 --> 00:15:04.300 align:start position:0% our Shaffer repo but actually authoring 00:15:04.300 --> 00:15:07.500 align:start position:0% our Shaffer repo but actually authoring them<00:15:04.450> as<00:15:04.600> well<00:15:05.850> one<00:15:06.850> other<00:15:07.000> thing<00:15:07.240> that<00:15:07.270> we'll 00:15:07.500 --> 00:15:07.510 align:start position:0% them as well one other thing that we'll 00:15:07.510 --> 00:15:10.470 align:start position:0% them as well one other thing that we'll need<00:15:07.660> is<00:15:08.020> multi<00:15:08.680> tree<00:15:08.920> support<00:15:09.370> so<00:15:09.820> the 00:15:10.470 --> 00:15:10.480 align:start position:0% need is multi tree support so the 00:15:10.480 --> 00:15:12.450 align:start position:0% need is multi tree support so the validator<00:15:10.930> set<00:15:11.230> might<00:15:11.590> grow<00:15:11.890> pretty<00:15:12.220> large 00:15:12.450 --> 00:15:12.460 align:start position:0% validator set might grow pretty large 00:15:12.460 --> 00:15:15.590 align:start position:0% validator set might grow pretty large right<00:15:12.970> now<00:15:13.000> it's<00:15:13.390> just<00:15:13.450> stored<00:15:14.020> in<00:15:14.320> this<00:15:14.800> ssz 00:15:15.590 --> 00:15:15.600 align:start position:0% right now it's just stored in this ssz 00:15:15.600 --> 00:15:17.460 align:start position:0% right now it's just stored in this ssz serialization<00:15:16.600> simple<00:15:17.050> simple 00:15:17.460 --> 00:15:17.470 align:start position:0% serialization simple simple 00:15:17.470 --> 00:15:20.160 align:start position:0% serialization simple simple serialization<00:15:18.280> format<00:15:18.670> that's<00:15:19.570> described<00:15:20.050> in 00:15:20.160 --> 00:15:20.170 align:start position:0% serialization format that's described in 00:15:20.170 --> 00:15:23.130 align:start position:0% serialization format that's described in the<00:15:20.290> sharding<00:15:20.590> spec<00:15:21.630> but<00:15:22.630> if<00:15:22.750> the<00:15:22.810> validator 00:15:23.130 --> 00:15:23.140 align:start position:0% the sharding spec but if the validator 00:15:23.140 --> 00:15:25.110 align:start position:0% the sharding spec but if the validator set<00:15:23.320> is<00:15:23.410> large<00:15:23.590> enough<00:15:23.920> and<00:15:24.040> continues<00:15:24.490> to<00:15:24.850> to 00:15:25.110 --> 00:15:25.120 align:start position:0% set is large enough and continues to to 00:15:25.120 --> 00:15:27.150 align:start position:0% set is large enough and continues to to grow<00:15:25.510> dynamically<00:15:26.170> then<00:15:26.620> you<00:15:26.800> would<00:15:26.920> need<00:15:27.100> to 00:15:27.150 --> 00:15:27.160 align:start position:0% grow dynamically then you would need to 00:15:27.160 --> 00:15:28.830 align:start position:0% grow dynamically then you would need to probably<00:15:27.580> encode<00:15:27.970> it<00:15:28.090> in<00:15:28.180> some<00:15:28.360> kind<00:15:28.540> of<00:15:28.600> tree 00:15:28.830 --> 00:15:28.840 align:start position:0% probably encode it in some kind of tree 00:15:28.840 --> 00:15:32.430 align:start position:0% probably encode it in some kind of tree structure<00:15:29.490> so<00:15:30.490> this<00:15:30.640> is<00:15:30.880> a<00:15:31.170> feature<00:15:32.170> where 00:15:32.430 --> 00:15:32.440 align:start position:0% structure so this is a feature where 00:15:32.440 --> 00:15:34.590 align:start position:0% structure so this is a feature where basically<00:15:32.890> rather<00:15:33.040> than<00:15:33.280> having<00:15:33.490> a<00:15:33.730> single 00:15:34.590 --> 00:15:34.600 align:start position:0% basically rather than having a single 00:15:34.600 --> 00:15:35.550 align:start position:0% basically rather than having a single store 00:15:35.550 --> 00:15:35.560 align:start position:0% store 00:15:35.560 --> 00:15:37.320 align:start position:0% store root<00:15:35.920> in<00:15:36.070> the<00:15:36.160> substrate<00:15:36.610> header<00:15:36.850> you<00:15:37.120> have 00:15:37.320 --> 00:15:37.330 align:start position:0% root in the substrate header you have 00:15:37.330 --> 00:15:40.230 align:start position:0% root in the substrate header you have one<00:15:38.260> that<00:15:38.560> references<00:15:39.040> a<00:15:39.100> few<00:15:39.310> others<00:15:39.550> but 00:15:40.230 --> 00:15:40.240 align:start position:0% one that references a few others but 00:15:40.240 --> 00:15:42.900 align:start position:0% one that references a few others but it's<00:15:40.390> also<00:15:40.540> a<00:15:40.750> valuable<00:15:40.990> feature<00:15:41.470> for<00:15:41.860> for<00:15:42.490> for 00:15:42.900 --> 00:15:42.910 align:start position:0% it's also a valuable feature for for for 00:15:42.910 --> 00:15:45.420 align:start position:0% it's also a valuable feature for for for example<00:15:43.000> building<00:15:43.690> and<00:15:44.350> if<00:15:44.590> during<00:15:44.770> 1.0 00:15:45.420 --> 00:15:45.430 align:start position:0% example building and if during 1.0 00:15:45.430 --> 00:15:48.360 align:start position:0% example building and if during 1.0 client<00:15:45.880> on<00:15:46.170> substrate<00:15:47.170> because<00:15:48.100> this<00:15:48.250> is 00:15:48.360 --> 00:15:48.370 align:start position:0% client on substrate because this is 00:15:48.370 --> 00:15:49.680 align:start position:0% client on substrate because this is roughly<00:15:48.670> the<00:15:48.820> same<00:15:49.000> model<00:15:49.390> that<00:15:49.480> you<00:15:49.570> would 00:15:49.680 --> 00:15:49.690 align:start position:0% roughly the same model that you would 00:15:49.690 --> 00:15:52.950 align:start position:0% roughly the same model that you would use<00:15:49.840> for<00:15:49.990> the<00:15:50.920> accounts<00:15:51.490> tree<00:15:51.790> versus<00:15:52.330> account 00:15:52.950 --> 00:15:52.960 align:start position:0% use for the accounts tree versus account 00:15:52.960 --> 00:15:55.230 align:start position:0% use for the accounts tree versus account storage<00:15:53.410> trees<00:15:53.740> in<00:15:53.920> a<00:15:53.980> theory<00:15:54.190> in<00:15:54.250> 1.0<00:15:54.790> so<00:15:55.089> one 00:15:55.230 --> 00:15:55.240 align:start position:0% storage trees in a theory in 1.0 so one 00:15:55.240 --> 00:15:57.240 align:start position:0% storage trees in a theory in 1.0 so one possible<00:15:55.720> application<00:15:56.290> of<00:15:56.380> that<00:15:56.470> could<00:15:56.950> be<00:15:57.070> to 00:15:57.240 --> 00:15:57.250 align:start position:0% possible application of that could be to 00:15:57.250 --> 00:15:59.160 align:start position:0% possible application of that could be to probably<00:15:57.520> fairly<00:15:57.790> easily<00:15:58.060> put<00:15:58.810> together<00:15:58.930> a 00:15:59.160 --> 00:15:59.170 align:start position:0% probably fairly easily put together a 00:15:59.170 --> 00:16:02.070 align:start position:0% probably fairly easily put together a light<00:15:59.440> client<00:15:59.860> in<00:16:00.010> substrate<00:16:00.750> for<00:16:01.750> a<00:16:01.779> theorem 00:16:02.070 --> 00:16:02.080 align:start position:0% light client in substrate for a theorem 00:16:02.080 --> 00:16:06.870 align:start position:0% light client in substrate for a theorem 1.0<00:16:02.589> or<00:16:02.620> for<00:16:03.279> a<00:16:03.700> theorem<00:16:04.240> 2.0<00:16:04.750> shard<00:16:05.020> chains<00:16:05.880> so 00:16:06.870 --> 00:16:06.880 align:start position:0% 1.0 or for a theorem 2.0 shard chains so 00:16:06.880 --> 00:16:11.160 align:start position:0% 1.0 or for a theorem 2.0 shard chains so I<00:16:07.180> guess<00:16:07.540> I'll<00:16:07.930> conclude<00:16:08.440> it<00:16:08.650> there<00:16:10.170> get 00:16:11.160 --> 00:16:11.170 align:start position:0% I guess I'll conclude it there get 00:16:11.170 --> 00:16:13.290 align:start position:0% I guess I'll conclude it there get substrate<00:16:11.710> give<00:16:12.279> it<00:16:12.400> a<00:16:12.460> try 00:16:13.290 --> 00:16:13.300 align:start position:0% substrate give it a try 00:16:13.300 --> 00:16:15.600 align:start position:0% substrate give it a try continue<00:16:14.260> to<00:16:14.350> follow<00:16:14.589> what's<00:16:14.890> going<00:16:15.160> on<00:16:15.339> with 00:16:15.600 --> 00:16:15.610 align:start position:0% continue to follow what's going on with 00:16:15.610 --> 00:16:19.350 align:start position:0% continue to follow what's going on with parodies<00:16:16.390> if<00:16:17.230> your<00:16:17.440> name<00:16:17.589> 2.0<00:16:18.070> work<00:16:18.360> we're 00:16:19.350 --> 00:16:19.360 align:start position:0% parodies if your name 2.0 work we're 00:16:19.360 --> 00:16:21.269 align:start position:0% parodies if your name 2.0 work we're doing<00:16:19.390> it<00:16:19.750> a<00:16:19.779> bit<00:16:19.870> quietly<00:16:20.529> in<00:16:20.920> the<00:16:21.070> background 00:16:21.269 --> 00:16:21.279 align:start position:0% doing it a bit quietly in the background 00:16:21.279 --> 00:16:25.590 align:start position:0% doing it a bit quietly in the background but<00:16:21.700> slowly<00:16:22.089> plugging<00:16:22.600> away<00:16:22.720> at<00:16:23.050> it<00:16:23.260> as<00:16:24.600> the 00:16:25.590 --> 00:16:25.600 align:start position:0% but slowly plugging away at it as the 00:16:25.600 --> 00:16:28.530 align:start position:0% but slowly plugging away at it as the specs<00:16:25.870> solidify<00:16:26.380> we<00:16:26.589> really<00:16:26.830> intend<00:16:27.250> to<00:16:27.640> keep 00:16:28.530 --> 00:16:28.540 align:start position:0% specs solidify we really intend to keep 00:16:28.540 --> 00:16:30.300 align:start position:0% specs solidify we really intend to keep it<00:16:28.750> up<00:16:28.900> to<00:16:29.080> date<00:16:29.110> keep<00:16:29.529> our<00:16:29.680> code<00:16:29.800> up<00:16:30.010> to<00:16:30.160> date 00:16:30.300 --> 00:16:30.310 align:start position:0% it up to date keep our code up to date 00:16:30.310 --> 00:16:32.490 align:start position:0% it up to date keep our code up to date with<00:16:30.460> what<00:16:30.580> the<00:16:30.670> specs<00:16:30.910> are<00:16:31.060> saying<00:16:31.350> so<00:16:32.350> that 00:16:32.490 --> 00:16:32.500 align:start position:0% with what the specs are saying so that 00:16:32.500 --> 00:16:34.019 align:start position:0% with what the specs are saying so that we're<00:16:32.620> always<00:16:32.770> on<00:16:33.010> the<00:16:33.100> ball<00:16:33.250> with<00:16:33.490> with<00:16:33.910> the 00:16:34.019 --> 00:16:34.029 align:start position:0% we're always on the ball with with the 00:16:34.029 --> 00:16:40.470 align:start position:0% we're always on the ball with with the sharding<00:16:34.330> stuff<00:16:34.540> thank<00:16:34.960> you<00:16:35.050> very<00:16:35.200> much 00:16:40.470 --> 00:16:40.480 align:start position:0% 00:16:40.480 --> 00:16:46.509 align:start position:0% it's<00:16:41.480> time<00:16:41.600> for<00:16:41.750> a<00:16:41.779> few<00:16:41.930> questions<00:16:45.190> hi<00:16:46.190> thank 00:16:46.509 --> 00:16:46.519 align:start position:0% it's time for a few questions hi thank 00:16:46.519 --> 00:16:49.960 align:start position:0% it's time for a few questions hi thank you<00:16:46.610> very<00:16:46.790> much<00:16:47.000> my<00:16:47.959> question<00:16:48.320> is<00:16:48.700> is<00:16:49.700> there 00:16:49.960 --> 00:16:49.970 align:start position:0% you very much my question is is there 00:16:49.970 --> 00:16:51.879 align:start position:0% you very much my question is is there could<00:16:50.720> you<00:16:50.750> maybe<00:16:50.959> elaborate<00:16:51.380> a<00:16:51.529> little<00:16:51.649> bit 00:16:51.879 --> 00:16:51.889 align:start position:0% could you maybe elaborate a little bit 00:16:51.889 --> 00:16:54.730 align:start position:0% could you maybe elaborate a little bit about<00:16:52.060> the<00:16:53.060> crystallites<00:16:53.600> states<00:16:53.990> like<00:16:54.320> in 00:16:54.730 --> 00:16:54.740 align:start position:0% about the crystallites states like in 00:16:54.740 --> 00:16:57.790 align:start position:0% about the crystallites states like in what<00:16:54.980> form<00:16:55.310> are<00:16:55.670> they<00:16:56.029> happening<00:16:56.360> and<00:16:56.930> if<00:16:57.529> it's 00:16:57.790 --> 00:16:57.800 align:start position:0% what form are they happening and if it's 00:16:57.800 --> 00:17:01.269 align:start position:0% what form are they happening and if it's kind<00:16:58.100> of<00:16:58.190> the<00:16:58.339> benchmarks<00:16:59.410> that<00:17:00.410> you<00:17:00.920> haven't 00:17:01.269 --> 00:17:01.279 align:start position:0% kind of the benchmarks that you haven't 00:17:01.279 --> 00:17:03.910 align:start position:0% kind of the benchmarks that you haven't proof<00:17:01.430> of<00:17:01.550> stake<00:17:01.820> and<00:17:02.449> like<00:17:03.079> yeah<00:17:03.350> if<00:17:03.620> this 00:17:03.910 --> 00:17:03.920 align:start position:0% proof of stake and like yeah if this 00:17:03.920 --> 00:17:06.789 align:start position:0% proof of stake and like yeah if this benchmarks<00:17:04.910> are<00:17:05.089> something<00:17:05.959> centralized<00:17:06.530> or 00:17:06.789 --> 00:17:06.799 align:start position:0% benchmarks are something centralized or 00:17:06.799 --> 00:17:10.270 align:start position:0% benchmarks are something centralized or is<00:17:06.949> done<00:17:07.189> in<00:17:07.339> a<00:17:07.429> decentralized<00:17:07.880> way<00:17:08.620> yeah<00:17:09.620> so 00:17:10.270 --> 00:17:10.280 align:start position:0% is done in a decentralized way yeah so 00:17:10.280 --> 00:17:12.250 align:start position:0% is done in a decentralized way yeah so so<00:17:10.549> benchmarking<00:17:11.209> the<00:17:11.270> the<00:17:11.750> crystallized 00:17:12.250 --> 00:17:12.260 align:start position:0% so benchmarking the the crystallized 00:17:12.260 --> 00:17:15.789 align:start position:0% so benchmarking the the crystallized state<00:17:12.559> is<00:17:12.740> the<00:17:13.160> question<00:17:14.740> so<00:17:15.740> the 00:17:15.789 --> 00:17:15.799 align:start position:0% state is the question so the 00:17:15.799 --> 00:17:17.380 align:start position:0% state is the question so the crystallized<00:17:16.220> state<00:17:16.459> is<00:17:16.640> just<00:17:16.850> something 00:17:17.380 --> 00:17:17.390 align:start position:0% crystallized state is just something 00:17:17.390 --> 00:17:19.870 align:start position:0% crystallized state is just something from<00:17:17.750> the<00:17:17.929> sharding<00:17:18.319> specification<00:17:19.130> it's 00:17:19.870 --> 00:17:19.880 align:start position:0% from the sharding specification it's 00:17:19.880 --> 00:17:21.610 align:start position:0% from the sharding specification it's basically<00:17:20.299> the<00:17:20.449> state<00:17:20.720> of<00:17:20.929> the<00:17:21.020> chain<00:17:21.230> is<00:17:21.410> spit 00:17:21.610 --> 00:17:21.620 align:start position:0% basically the state of the chain is spit 00:17:21.620 --> 00:17:24.400 align:start position:0% basically the state of the chain is spit into<00:17:21.860> two<00:17:22.100> parts<00:17:22.910> you<00:17:22.970> have<00:17:23.270> the<00:17:23.299> active<00:17:23.929> state 00:17:24.400 --> 00:17:24.410 align:start position:0% into two parts you have the active state 00:17:24.410 --> 00:17:26.799 align:start position:0% into two parts you have the active state and<00:17:24.589> the<00:17:24.799> crystallized<00:17:25.280> state<00:17:25.549> so<00:17:26.360> the<00:17:26.449> active 00:17:26.799 --> 00:17:26.809 align:start position:0% and the crystallized state so the active 00:17:26.809 --> 00:17:29.110 align:start position:0% and the crystallized state so the active state<00:17:27.049> contains<00:17:27.470> sort<00:17:27.919> of<00:17:27.980> Atta<00:17:28.429> stations 00:17:29.110 --> 00:17:29.120 align:start position:0% state contains sort of Atta stations 00:17:29.120 --> 00:17:32.020 align:start position:0% state contains sort of Atta stations that<00:17:29.900> have<00:17:30.140> not<00:17:30.350> been<00:17:30.530> processed<00:17:30.799> yet<00:17:31.250> and<00:17:31.490> the 00:17:32.020 --> 00:17:32.030 align:start position:0% that have not been processed yet and the 00:17:32.030 --> 00:17:33.549 align:start position:0% that have not been processed yet and the crystallized<00:17:32.480> state<00:17:32.750> stores<00:17:33.169> at<00:17:33.440> two 00:17:33.549 --> 00:17:33.559 align:start position:0% crystallized state stores at two 00:17:33.559 --> 00:17:35.110 align:start position:0% crystallized state stores at two stations<00:17:33.860> that<00:17:33.980> have<00:17:34.160> been<00:17:34.400> processed<00:17:34.669> and 00:17:35.110 --> 00:17:35.120 align:start position:0% stations that have been processed and 00:17:35.120 --> 00:17:38.890 align:start position:0% stations that have been processed and checked<00:17:35.390> and<00:17:36.970> and<00:17:37.970> as<00:17:38.179> well<00:17:38.360> like<00:17:38.600> what<00:17:38.780> the 00:17:38.890 --> 00:17:38.900 align:start position:0% checked and and as well like what the 00:17:38.900 --> 00:17:41.049 align:start position:0% checked and and as well like what the head<00:17:39.080> of<00:17:39.260> all<00:17:39.350> the<00:17:39.500> shards<00:17:39.710> are<00:17:39.950> that<00:17:40.790> sort<00:17:41.000> of 00:17:41.049 --> 00:17:41.059 align:start position:0% head of all the shards are that sort of 00:17:41.059 --> 00:17:44.140 align:start position:0% head of all the shards are that sort of thing<00:17:41.270> as<00:17:41.419> well<00:17:41.750> as<00:17:41.929> the<00:17:42.110> validator<00:17:43.100> set 00:17:44.140 --> 00:17:44.150 align:start position:0% thing as well as the validator set 00:17:44.150 --> 00:17:46.150 align:start position:0% thing as well as the validator set we<00:17:44.809> haven't<00:17:45.049> benchmarked<00:17:45.559> it<00:17:45.679> yet<00:17:45.830> it's<00:17:46.010> a<00:17:46.040> bit 00:17:46.150 --> 00:17:46.160 align:start position:0% we haven't benchmarked it yet it's a bit 00:17:46.160 --> 00:17:47.980 align:start position:0% we haven't benchmarked it yet it's a bit early<00:17:46.280> stage<00:17:46.640> for<00:17:46.880> that<00:17:47.000> I<00:17:47.030> mean<00:17:47.360> there's<00:17:47.840> not 00:17:47.980 --> 00:17:47.990 align:start position:0% early stage for that I mean there's not 00:17:47.990 --> 00:17:49.539 align:start position:0% early stage for that I mean there's not really<00:17:48.169> much<00:17:48.350> to<00:17:48.559> benchmark<00:17:48.830> until<00:17:49.280> you<00:17:49.400> have 00:17:49.539 --> 00:17:49.549 align:start position:0% really much to benchmark until you have 00:17:49.549 --> 00:17:52.020 align:start position:0% really much to benchmark until you have something<00:17:49.880> like<00:17:49.910> block<00:17:50.210> authorship<00:17:50.780> going 00:17:52.020 --> 00:17:52.030 align:start position:0% something like block authorship going 00:17:52.030 --> 00:17:54.760 align:start position:0% something like block authorship going but<00:17:53.030> you<00:17:53.299> know<00:17:53.390> as<00:17:53.600> soon<00:17:53.900> as<00:17:54.080> you<00:17:54.140> have<00:17:54.380> a<00:17:54.410> chain 00:17:54.760 --> 00:17:54.770 align:start position:0% but you know as soon as you have a chain 00:17:54.770 --> 00:17:56.650 align:start position:0% but you know as soon as you have a chain up<00:17:55.010> you<00:17:55.190> would<00:17:55.309> start<00:17:55.549> to<00:17:55.640> see<00:17:55.820> maybe<00:17:56.360> how<00:17:56.630> many 00:17:56.650 --> 00:17:56.660 align:start position:0% up you would start to see maybe how many 00:17:56.660 --> 00:17:58.960 align:start position:0% up you would start to see maybe how many transactions<00:17:57.410> you<00:17:57.530> can<00:17:57.679> process<00:17:57.890> but<00:17:58.850> right 00:17:58.960 --> 00:17:58.970 align:start position:0% transactions you can process but right 00:17:58.970 --> 00:18:00.190 align:start position:0% transactions you can process but right now<00:17:59.090> is<00:17:59.240> sort<00:17:59.390> of<00:17:59.450> the<00:17:59.570> stage<00:17:59.780> more<00:17:59.990> for 00:18:00.190 --> 00:18:00.200 align:start position:0% now is sort of the stage more for 00:18:00.200 --> 00:18:02.950 align:start position:0% now is sort of the stage more for experimentation<00:18:01.059> like<00:18:02.059> there<00:18:02.330> aren't<00:18:02.540> even 00:18:02.950 --> 00:18:02.960 align:start position:0% experimentation like there aren't even 00:18:02.960 --> 00:18:05.440 align:start position:0% experimentation like there aren't even really<00:18:03.549> none<00:18:04.549> of<00:18:04.580> the<00:18:04.850> beacon<00:18:05.210> chain 00:18:05.440 --> 00:18:05.450 align:start position:0% really none of the beacon chain 00:18:05.450 --> 00:18:07.240 align:start position:0% really none of the beacon chain implementations<00:18:06.230> are<00:18:06.470> really<00:18:06.650> at<00:18:06.799> the<00:18:06.980> stage 00:18:07.240 --> 00:18:07.250 align:start position:0% implementations are really at the stage 00:18:07.250 --> 00:18:09.970 align:start position:0% implementations are really at the stage where<00:18:07.850> you<00:18:08.540> could<00:18:08.750> attach<00:18:09.020> shards<00:18:09.590> to<00:18:09.799> them 00:18:09.970 --> 00:18:09.980 align:start position:0% where you could attach shards to them 00:18:09.980 --> 00:18:12.100 align:start position:0% where you could attach shards to them yet<00:18:10.190> so<00:18:10.400> I<00:18:11.150> don't<00:18:11.480> think<00:18:11.570> benchmarking 00:18:12.100 --> 00:18:12.110 align:start position:0% yet so I don't think benchmarking 00:18:12.110 --> 00:18:13.570 align:start position:0% yet so I don't think benchmarking sharding<00:18:12.530> makes<00:18:12.710> that<00:18:12.919> much<00:18:13.100> sense<00:18:13.309> and<00:18:13.520> so 00:18:13.570 --> 00:18:13.580 align:start position:0% sharding makes that much sense and so 00:18:13.580 --> 00:18:18.430 align:start position:0% sharding makes that much sense and so you<00:18:13.640> actually<00:18:13.790> have<00:18:14.090> shards<00:18:17.049> you<00:18:18.049> said<00:18:18.260> that 00:18:18.430 --> 00:18:18.440 align:start position:0% you actually have shards you said that 00:18:18.440 --> 00:18:21.760 align:start position:0% you actually have shards you said that the<00:18:19.690> substrate<00:18:20.690> works<00:18:21.110> with<00:18:21.350> the<00:18:21.470> beacon 00:18:21.760 --> 00:18:21.770 align:start position:0% the substrate works with the beacon 00:18:21.770 --> 00:18:23.110 align:start position:0% the substrate works with the beacon chain<00:18:22.040> but<00:18:22.250> does<00:18:22.370> it<00:18:22.460> work<00:18:22.490> with<00:18:22.760> the<00:18:22.790> shard 00:18:23.110 --> 00:18:23.120 align:start position:0% chain but does it work with the shard 00:18:23.120 --> 00:18:26.350 align:start position:0% chain but does it work with the shard chains<00:18:23.419> as<00:18:23.600> well<00:18:24.100> yeah<00:18:25.100> exactly<00:18:25.309> so<00:18:25.640> you<00:18:25.940> could 00:18:26.350 --> 00:18:26.360 align:start position:0% chains as well yeah exactly so you could 00:18:26.360 --> 00:18:28.630 align:start position:0% chains as well yeah exactly so you could you<00:18:26.660> could<00:18:26.809> use<00:18:26.960> substrate<00:18:27.350> to<00:18:27.530> write<00:18:27.770> the 00:18:28.630 --> 00:18:28.640 align:start position:0% you could use substrate to write the 00:18:28.640 --> 00:18:29.740 align:start position:0% you could use substrate to write the beacon<00:18:28.940> chain<00:18:29.120> which<00:18:29.270> is<00:18:29.299> what<00:18:29.450> we're<00:18:29.570> doing 00:18:29.740 --> 00:18:29.750 align:start position:0% beacon chain which is what we're doing 00:18:29.750 --> 00:18:32.260 align:start position:0% beacon chain which is what we're doing now<00:18:29.870> and<00:18:30.110> you<00:18:30.799> can<00:18:30.950> also<00:18:31.130> use<00:18:31.429> it<00:18:31.610> to<00:18:31.640> write<00:18:31.880> the 00:18:32.260 --> 00:18:32.270 align:start position:0% now and you can also use it to write the 00:18:32.270 --> 00:18:34.120 align:start position:0% now and you can also use it to write the shard<00:18:32.480> chains<00:18:32.809> like<00:18:33.049> those<00:18:33.559> are<00:18:33.770> most<00:18:33.919> likely 00:18:34.120 --> 00:18:34.130 align:start position:0% shard chains like those are most likely 00:18:34.130 --> 00:18:36.460 align:start position:0% shard chains like those are most likely going<00:18:34.280> to<00:18:34.520> be<00:18:34.790> proof<00:18:35.690> of<00:18:35.809> stake<00:18:36.049> chains<00:18:36.320> on 00:18:36.460 --> 00:18:36.470 align:start position:0% going to be proof of stake chains on 00:18:36.470 --> 00:18:38.500 align:start position:0% going to be proof of stake chains on their<00:18:36.590> own<00:18:36.710> that<00:18:36.950> are<00:18:37.010> running<00:18:37.250> you<00:18:37.940> azzam<00:18:38.360> as 00:18:38.500 --> 00:18:38.510 align:start position:0% their own that are running you azzam as 00:18:38.510 --> 00:18:40.990 align:start position:0% their own that are running you azzam as the<00:18:38.929> state<00:18:39.140> transition<00:18:39.910> from<00:18:40.910> the 00:18:40.990 --> 00:18:41.000 align:start position:0% the state transition from the 00:18:41.000 --> 00:18:42.370 align:start position:0% the state transition from the perspective<00:18:41.450> of<00:18:41.510> the<00:18:41.600> beacon<00:18:41.870> chain<00:18:42.110> the 00:18:42.370 --> 00:18:42.380 align:start position:0% perspective of the beacon chain the 00:18:42.380 --> 00:18:44.650 align:start position:0% perspective of the beacon chain the chain<00:18:42.410> the<00:18:42.890> the<00:18:43.490> shard<00:18:44.000> chains<00:18:44.299> are<00:18:44.480> just 00:18:44.650 --> 00:18:44.660 align:start position:0% chain the the shard chains are just 00:18:44.660 --> 00:18:46.659 align:start position:0% chain the the shard chains are just blobs<00:18:45.080> of<00:18:45.350> data<00:18:45.530> so<00:18:45.770> we<00:18:45.860> sort<00:18:46.010> of<00:18:46.100> step<00:18:46.370> aside 00:18:46.659 --> 00:18:46.669 align:start position:0% blobs of data so we sort of step aside 00:18:46.669 --> 00:18:48.880 align:start position:0% blobs of data so we sort of step aside from<00:18:46.880> that<00:18:46.970> problem<00:18:47.390> for<00:18:47.600> now<00:18:47.720> but<00:18:48.679> you<00:18:48.770> could 00:18:48.880 --> 00:18:48.890 align:start position:0% from that problem for now but you could 00:18:48.890 --> 00:18:50.169 align:start position:0% from that problem for now but you could definitely<00:18:49.010> write<00:18:49.400> in<00:18:49.490> aetherium<00:18:49.760> to<00:18:49.970> point 00:18:50.169 --> 00:18:50.179 align:start position:0% definitely write in aetherium to point 00:18:50.179 --> 00:18:52.180 align:start position:0% definitely write in aetherium to point out<00:18:50.240> client<00:18:50.630> for<00:18:51.200> the<00:18:51.320> shard<00:18:51.590> chains<00:18:51.919> in 00:18:52.180 --> 00:18:52.190 align:start position:0% out client for the shard chains in 00:18:52.190 --> 00:18:53.230 align:start position:0% out client for the shard chains in substrate<00:18:52.669> in 00:18:53.230 --> 00:18:53.240 align:start position:0% substrate in 00:18:53.240 --> 00:18:54.820 align:start position:0% substrate in that's<00:18:53.539> what<00:18:53.840> we<00:18:53.960> will<00:18:54.080> be<00:18:54.140> doing<00:18:54.380> as<00:18:54.649> one<00:18:54.770> of 00:18:54.820 --> 00:18:54.830 align:start position:0% that's what we will be doing as one of 00:18:54.830 --> 00:18:58.810 align:start position:0% that's what we will be doing as one of the<00:18:54.950> next<00:18:55.100> steps<00:18:57.039> so<00:18:58.039> do<00:18:58.159> you<00:18:58.220> have<00:18:58.370> any<00:18:58.490> plans 00:18:58.810 --> 00:18:58.820 align:start position:0% the next steps so do you have any plans 00:18:58.820 --> 00:19:01.090 align:start position:0% the next steps so do you have any plans to<00:18:59.240> upgrade<00:18:59.510> some<00:18:59.960> of<00:19:00.080> the<00:19:00.200> other<00:19:00.679> products 00:19:01.090 --> 00:19:01.100 align:start position:0% to upgrade some of the other products 00:19:01.100 --> 00:19:03.100 align:start position:0% to upgrade some of the other products you<00:19:01.159> support<00:19:01.549> like<00:19:01.700> you<00:19:02.149> know<00:19:02.390> the<00:19:02.539> Bitcoin<00:19:02.929> is 00:19:03.100 --> 00:19:03.110 align:start position:0% you support like you know the Bitcoin is 00:19:03.110 --> 00:19:05.560 align:start position:0% you support like you know the Bitcoin is e<00:19:03.230> cash<00:19:03.409> when<00:19:03.620> you<00:19:03.710> just<00:19:03.890> now<00:19:04.270> if<00:19:05.270> they're<00:19:05.450> in 00:19:05.560 --> 00:19:05.570 align:start position:0% e cash when you just now if they're in 00:19:05.570 --> 00:19:07.570 align:start position:0% e cash when you just now if they're in 1.0<00:19:06.049> with<00:19:06.350> substrate<00:19:06.890> once<00:19:07.159> it's<00:19:07.340> up<00:19:07.490> and 00:19:07.570 --> 00:19:07.580 align:start position:0% 1.0 with substrate once it's up and 00:19:07.580 --> 00:19:12.940 align:start position:0% 1.0 with substrate once it's up and running<00:19:07.669> and<00:19:07.940> ready<00:19:08.059> to<00:19:08.270> go<00:19:09.429> yeah<00:19:11.380> so<00:19:12.380> so<00:19:12.770> it's 00:19:12.940 --> 00:19:12.950 align:start position:0% running and ready to go yeah so so it's 00:19:12.950 --> 00:19:15.279 align:start position:0% running and ready to go yeah so so it's it's<00:19:13.309> quite<00:19:13.640> possible<00:19:14.240> that<00:19:14.299> you<00:19:14.690> could<00:19:15.080> do<00:19:15.260> a 00:19:15.279 --> 00:19:15.289 align:start position:0% it's quite possible that you could do a 00:19:15.289 --> 00:19:17.260 align:start position:0% it's quite possible that you could do a Bitcoin<00:19:15.770> implementation<00:19:16.399> on<00:19:16.520> substrate<00:19:17.029> I 00:19:17.260 --> 00:19:17.270 align:start position:0% Bitcoin implementation on substrate I 00:19:17.270 --> 00:19:19.090 align:start position:0% Bitcoin implementation on substrate I think<00:19:17.840> with<00:19:17.960> the<00:19:18.080> existing<00:19:18.529> products<00:19:18.980> like 00:19:19.090 --> 00:19:19.100 align:start position:0% think with the existing products like 00:19:19.100 --> 00:19:22.299 align:start position:0% think with the existing products like parity<00:19:19.520> aetherium<00:19:21.190> particularly<00:19:22.190> with 00:19:22.299 --> 00:19:22.309 align:start position:0% parity aetherium particularly with 00:19:22.309 --> 00:19:23.860 align:start position:0% parity aetherium particularly with parity<00:19:22.640> aetherium<00:19:23.000> there's<00:19:23.210> a<00:19:23.299> lot<00:19:23.450> of<00:19:23.600> extra 00:19:23.860 --> 00:19:23.870 align:start position:0% parity aetherium there's a lot of extra 00:19:23.870 --> 00:19:25.840 align:start position:0% parity aetherium there's a lot of extra code<00:19:24.169> around<00:19:24.440> it<00:19:24.679> like<00:19:24.830> things<00:19:25.070> like<00:19:25.220> warp 00:19:25.840 --> 00:19:25.850 align:start position:0% code around it like things like warp 00:19:25.850 --> 00:19:28.480 align:start position:0% code around it like things like warp sink<00:19:26.210> and<00:19:26.630> the<00:19:27.260> light<00:19:27.440> client<00:19:27.830> protocol<00:19:28.250> and 00:19:28.480 --> 00:19:28.490 align:start position:0% sink and the light client protocol and 00:19:28.490 --> 00:19:30.370 align:start position:0% sink and the light client protocol and stuff<00:19:28.640> like<00:19:28.760> that<00:19:29.000> that's<00:19:29.750> a<00:19:29.840> bit<00:19:29.990> different 00:19:30.370 --> 00:19:30.380 align:start position:0% stuff like that that's a bit different 00:19:30.380 --> 00:19:32.820 align:start position:0% stuff like that that's a bit different than<00:19:30.529> the<00:19:30.590> way<00:19:30.679> substrate<00:19:31.190> looks<00:19:31.429> at<00:19:31.580> things 00:19:32.820 --> 00:19:32.830 align:start position:0% than the way substrate looks at things 00:19:32.830 --> 00:19:36.460 align:start position:0% than the way substrate looks at things so<00:19:33.830> just<00:19:34.159> with<00:19:34.640> that<00:19:34.850> amount<00:19:35.659> of<00:19:35.960> like<00:19:36.140> three 00:19:36.460 --> 00:19:36.470 align:start position:0% so just with that amount of like three 00:19:36.470 --> 00:19:38.409 align:start position:0% so just with that amount of like three years<00:19:36.500> of<00:19:36.950> code<00:19:37.159> porting<00:19:37.669> that<00:19:37.700> all<00:19:38.000> over<00:19:38.330> to 00:19:38.409 --> 00:19:38.419 align:start position:0% years of code porting that all over to 00:19:38.419 --> 00:19:41.320 align:start position:0% years of code porting that all over to substrate<00:19:38.899> would<00:19:39.140> be<00:19:39.320> a<00:19:39.590> bit<00:19:40.340> too<00:19:40.580> much<00:19:41.090> work 00:19:41.320 --> 00:19:41.330 align:start position:0% substrate would be a bit too much work 00:19:41.330 --> 00:19:43.240 align:start position:0% substrate would be a bit too much work probably<00:19:41.690> you<00:19:42.350> could<00:19:42.500> definitely<00:19:42.649> write<00:19:43.070> in 00:19:43.240 --> 00:19:43.250 align:start position:0% probably you could definitely write in 00:19:43.250 --> 00:19:44.500 align:start position:0% probably you could definitely write in the<00:19:43.309> theorem<00:19:43.610> client<00:19:43.880> and<00:19:44.000> substrate<00:19:44.390> but 00:19:44.500 --> 00:19:44.510 align:start position:0% the theorem client and substrate but 00:19:44.510 --> 00:19:46.060 align:start position:0% the theorem client and substrate but it's<00:19:44.659> unlikely<00:19:44.990> that<00:19:45.140> the<00:19:45.350> parity<00:19:45.649> etherium 00:19:46.060 --> 00:19:46.070 align:start position:0% it's unlikely that the parity etherium 00:19:46.070 --> 00:19:47.769 align:start position:0% it's unlikely that the parity etherium codebase<00:19:46.490> would<00:19:46.700> migrate<00:19:46.909> over<00:19:47.299> to<00:19:47.330> substrate 00:19:47.769 --> 00:19:47.779 align:start position:0% codebase would migrate over to substrate 00:19:47.779 --> 00:19:49.960 align:start position:0% codebase would migrate over to substrate in<00:19:47.899> the<00:19:47.960> near<00:19:48.110> future<00:19:48.260> the<00:19:49.250> Bitcoin<00:19:49.549> client<00:19:49.730> is 00:19:49.960 --> 00:19:49.970 align:start position:0% in the near future the Bitcoin client is 00:19:49.970 --> 00:19:52.240 align:start position:0% in the near future the Bitcoin client is a<00:19:50.000> lot<00:19:50.240> less<00:19:51.080> complex<00:19:51.500> simply<00:19:51.980> because 00:19:52.240 --> 00:19:52.250 align:start position:0% a lot less complex simply because 00:19:52.250 --> 00:19:54.820 align:start position:0% a lot less complex simply because bitcoin<00:19:52.429> is<00:19:52.820> a<00:19:52.850> lot<00:19:53.029> less<00:19:53.240> complex<00:19:53.659> so<00:19:54.620> I<00:19:54.649> think 00:19:54.820 --> 00:19:54.830 align:start position:0% bitcoin is a lot less complex so I think 00:19:54.830 --> 00:19:57.370 align:start position:0% bitcoin is a lot less complex so I think it's<00:19:55.070> very<00:19:55.130> possible<00:19:55.760> to<00:19:55.820> do<00:19:56.120> a<00:19:56.149> at<00:19:56.990> the<00:19:57.169> very 00:19:57.370 --> 00:19:57.380 align:start position:0% it's very possible to do a at the very 00:19:57.380 --> 00:20:00.610 align:start position:0% it's very possible to do a at the very least<00:19:57.620> a<00:19:57.980> you<00:19:58.760> TXO<00:19:59.270> based<00:19:59.539> chain<00:19:59.899> on<00:20:00.110> substrate 00:20:00.610 --> 00:20:00.620 align:start position:0% least a you TXO based chain on substrate 00:20:00.620 --> 00:20:03.399 align:start position:0% least a you TXO based chain on substrate where<00:20:00.919> you<00:20:01.330> execute<00:20:02.330> Bitcoin<00:20:03.049> scripts 00:20:03.399 --> 00:20:03.409 align:start position:0% where you execute Bitcoin scripts 00:20:03.409 --> 00:20:05.590 align:start position:0% where you execute Bitcoin scripts transactions<00:20:04.039> the<00:20:04.820> question<00:20:05.149> at<00:20:05.240> that<00:20:05.299> point 00:20:05.590 --> 00:20:05.600 align:start position:0% transactions the question at that point 00:20:05.600 --> 00:20:07.149 align:start position:0% transactions the question at that point is<00:20:05.690> really<00:20:05.720> just<00:20:06.080> optimization<00:20:06.799> like<00:20:07.010> it's 00:20:07.149 --> 00:20:07.159 align:start position:0% is really just optimization like it's 00:20:07.159 --> 00:20:08.799 align:start position:0% is really just optimization like it's it's<00:20:07.370> for<00:20:07.610> sure<00:20:07.730> possible<00:20:08.270> to<00:20:08.360> optimize<00:20:08.779> a 00:20:08.799 --> 00:20:08.809 align:start position:0% it's for sure possible to optimize a 00:20:08.809 --> 00:20:10.960 align:start position:0% it's for sure possible to optimize a substrate<00:20:09.320> node<00:20:09.529> to<00:20:10.039> get<00:20:10.220> to<00:20:10.370> the<00:20:10.460> level<00:20:10.789> of 00:20:10.960 --> 00:20:10.970 align:start position:0% substrate node to get to the level of 00:20:10.970 --> 00:20:13.990 align:start position:0% substrate node to get to the level of like<00:20:11.210> a<00:20:11.240> specialized<00:20:12.080> Bitcoin<00:20:12.500> node<00:20:12.880> but<00:20:13.880> that 00:20:13.990 --> 00:20:14.000 align:start position:0% like a specialized Bitcoin node but that 00:20:14.000 --> 00:20:15.519 align:start position:0% like a specialized Bitcoin node but that would<00:20:14.120> just<00:20:14.149> at<00:20:14.480> this<00:20:14.630> point<00:20:14.870> be<00:20:15.020> duplicating 00:20:15.519 --> 00:20:15.529 align:start position:0% would just at this point be duplicating 00:20:15.529 --> 00:20:16.870 align:start position:0% would just at this point be duplicating efforts<00:20:15.830> since<00:20:15.980> we've<00:20:16.190> already<00:20:16.340> written<00:20:16.580> one 00:20:16.870 --> 00:20:16.880 align:start position:0% efforts since we've already written one 00:20:16.880 --> 00:20:18.940 align:start position:0% efforts since we've already written one I<00:20:17.059> think<00:20:17.539> substrate<00:20:18.020> sort<00:20:18.320> of<00:20:18.380> added<00:20:18.710> snitch 00:20:18.940 --> 00:20:18.950 align:start position:0% I think substrate sort of added snitch 00:20:18.950 --> 00:20:21.909 align:start position:0% I think substrate sort of added snitch is<00:20:19.190> more<00:20:19.480> focused<00:20:20.480> on<00:20:20.539> less<00:20:20.750> migrating<00:20:21.620> over 00:20:21.909 --> 00:20:21.919 align:start position:0% is more focused on less migrating over 00:20:21.919 --> 00:20:23.500 align:start position:0% is more focused on less migrating over existing<00:20:22.190> blockchain<00:20:22.820> products<00:20:23.240> because 00:20:23.500 --> 00:20:23.510 align:start position:0% existing blockchain products because 00:20:23.510 --> 00:20:24.820 align:start position:0% existing blockchain products because then<00:20:23.630> people<00:20:23.809> have<00:20:24.020> already<00:20:24.320> done<00:20:24.470> all<00:20:24.649> those 00:20:24.820 --> 00:20:24.830 align:start position:0% then people have already done all those 00:20:24.830 --> 00:20:26.139 align:start position:0% then people have already done all those pieces<00:20:25.070> of<00:20:25.279> work<00:20:25.399> that<00:20:25.700> substrate<00:20:26.000> is 00:20:26.139 --> 00:20:26.149 align:start position:0% pieces of work that substrate is 00:20:26.149 --> 00:20:27.610 align:start position:0% pieces of work that substrate is supposed<00:20:26.360> to<00:20:26.419> save<00:20:26.659> you<00:20:26.840> from<00:20:27.020> duplicating 00:20:27.610 --> 00:20:27.620 align:start position:0% supposed to save you from duplicating 00:20:27.620 --> 00:20:31.299 align:start position:0% supposed to save you from duplicating and<00:20:29.200> rather<00:20:30.200> focus<00:20:30.620> more<00:20:30.799> towards<00:20:31.039> like<00:20:31.070> new 00:20:31.299 --> 00:20:31.309 align:start position:0% and rather focus more towards like new 00:20:31.309 --> 00:20:32.740 align:start position:0% and rather focus more towards like new blockchain<00:20:31.789> products<00:20:32.149> to<00:20:32.240> get<00:20:32.360> people<00:20:32.600> off 00:20:32.740 --> 00:20:32.750 align:start position:0% blockchain products to get people off 00:20:32.750 --> 00:20:34.810 align:start position:0% blockchain products to get people off the<00:20:32.929> ground<00:20:33.169> a<00:20:33.320> bit<00:20:33.350> faster<00:20:33.860> like<00:20:34.370> we<00:20:34.490> found<00:20:34.669> it 00:20:34.810 --> 00:20:34.820 align:start position:0% the ground a bit faster like we found it 00:20:34.820 --> 00:20:36.700 align:start position:0% the ground a bit faster like we found it to<00:20:34.940> be<00:20:35.029> immensely<00:20:35.270> useful<00:20:35.480> for<00:20:36.080> the<00:20:36.289> charting 00:20:36.700 --> 00:20:36.710 align:start position:0% to be immensely useful for the charting 00:20:36.710 --> 00:20:39.100 align:start position:0% to be immensely useful for the charting stuff<00:20:36.950> they<00:20:37.730> wrote<00:20:38.000> up<00:20:38.179> the<00:20:38.360> state<00:20:38.659> transition 00:20:39.100 --> 00:20:39.110 align:start position:0% stuff they wrote up the state transition 00:20:39.110 --> 00:20:42.010 align:start position:0% stuff they wrote up the state transition in<00:20:39.230> like<00:20:39.409> two<00:20:40.130> weeks<00:20:40.539> which<00:20:41.539> you<00:20:41.690> would<00:20:41.809> think 00:20:42.010 --> 00:20:42.020 align:start position:0% in like two weeks which you would think 00:20:42.020 --> 00:20:43.659 align:start position:0% in like two weeks which you would think is<00:20:42.230> you<00:20:42.500> know<00:20:42.620> if<00:20:43.010> someone<00:20:43.370> told<00:20:43.490> you<00:20:43.640> that 00:20:43.659 --> 00:20:43.669 align:start position:0% is you know if someone told you that 00:20:43.669 --> 00:20:44.649 align:start position:0% is you know if someone told you that beforehand<00:20:44.179> you<00:20:44.240> would<00:20:44.270> think<00:20:44.419> that<00:20:44.510> that's 00:20:44.649 --> 00:20:44.659 align:start position:0% beforehand you would think that that's 00:20:44.659 --> 00:20:47.350 align:start position:0% beforehand you would think that that's impossible<00:20:45.190> but<00:20:46.190> managed<00:20:46.760> to<00:20:46.789> do<00:20:47.059> it<00:20:47.179> just 00:20:47.350 --> 00:20:47.360 align:start position:0% impossible but managed to do it just 00:20:47.360 --> 00:20:49.120 align:start position:0% impossible but managed to do it just because<00:20:47.480> all<00:20:47.870> of<00:20:48.080> this<00:20:48.200> stuff<00:20:48.409> was<00:20:48.679> completely 00:20:49.120 --> 00:20:49.130 align:start position:0% because all of this stuff was completely 00:20:49.130 --> 00:20:54.669 align:start position:0% because all of this stuff was completely taken<00:20:49.909> away<00:20:50.179> from<00:20:50.600> developers<00:20:53.230> are<00:20:54.230> you<00:20:54.470> using 00:20:54.669 --> 00:20:54.679 align:start position:0% taken away from developers are you using 00:20:54.679 --> 00:21:01.000 align:start position:0% taken away from developers are you using G<00:20:55.429> RPC<00:20:55.970> for<00:20:56.240> the<00:20:56.360> interface<00:20:58.210> gr<00:20:59.210> PC<00:20:59.539> yeah<00:21:00.020> is 00:21:01.000 --> 00:21:01.010 align:start position:0% G RPC for the interface gr PC yeah is 00:21:01.010 --> 00:21:03.820 align:start position:0% G RPC for the interface gr PC yeah is there<00:21:01.570> because<00:21:02.570> I<00:21:02.809> think<00:21:02.870> I'm<00:21:03.260> actually<00:21:03.559> not 00:21:03.820 --> 00:21:03.830 align:start position:0% there because I think I'm actually not 00:21:03.830 --> 00:21:06.039 align:start position:0% there because I think I'm actually not familiar<00:21:04.190> with<00:21:04.399> with<00:21:04.789> gr<00:21:05.120> we<00:21:05.270> are<00:21:05.389> using<00:21:05.539> JSON 00:21:06.039 --> 00:21:06.049 align:start position:0% familiar with with gr we are using JSON 00:21:06.049 --> 00:21:06.670 align:start position:0% familiar with with gr we are using JSON RPC 00:21:06.670 --> 00:21:06.680 align:start position:0% RPC 00:21:06.680 --> 00:21:09.160 align:start position:0% RPC like<00:21:06.800> there's<00:21:07.070> some<00:21:07.220> json-rpc<00:21:07.580> methods<00:21:08.330> but 00:21:09.160 --> 00:21:09.170 align:start position:0% like there's some json-rpc methods but 00:21:09.170 --> 00:21:16.230 align:start position:0% like there's some json-rpc methods but I'm<00:21:09.290> not<00:21:09.410> familiar<00:21:09.590> with<00:21:09.800> G<00:21:10.370> RPC<00:21:10.790> okay<00:21:11.390> Google 00:21:16.230 --> 00:21:16.240 align:start position:0% 00:21:16.240 --> 00:21:20.380 align:start position:0% okay<00:21:17.950> okay<00:21:18.950> so<00:21:19.010> like<00:21:19.400> as<00:21:19.640> like<00:21:19.880> a<00:21:19.910> JSON<00:21:20.300> RPC 00:21:20.380 --> 00:21:20.390 align:start position:0% okay okay so like as like a JSON RPC 00:21:20.390 --> 00:21:23.500 align:start position:0% okay okay so like as like a JSON RPC server<00:21:20.990> yeah<00:21:21.650> no<00:21:21.890> so<00:21:22.460> we've<00:21:22.640> we've<00:21:23.120> written 00:21:23.500 --> 00:21:23.510 align:start position:0% server yeah no so we've we've written 00:21:23.510 --> 00:21:26.440 align:start position:0% server yeah no so we've we've written like<00:21:23.900> parody<00:21:24.230> has<00:21:24.320> written<00:21:24.530> our<00:21:24.770> own<00:21:25.330> JSON<00:21:26.330> RPC 00:21:26.440 --> 00:21:26.450 align:start position:0% like parody has written our own JSON RPC 00:21:26.450 --> 00:21:28.120 align:start position:0% like parody has written our own JSON RPC library<00:21:27.140> and<00:21:27.290> rust<00:21:27.500> actually<00:21:27.890> the<00:21:27.950> guy<00:21:28.070> who 00:21:28.120 --> 00:21:28.130 align:start position:0% library and rust actually the guy who 00:21:28.130 --> 00:21:29.560 align:start position:0% library and rust actually the guy who wrote<00:21:28.580> most<00:21:28.760> of<00:21:28.910> it<00:21:28.970> is<00:21:29.090> sitting<00:21:29.300> right<00:21:29.330> behind 00:21:29.560 --> 00:21:29.570 align:start position:0% wrote most of it is sitting right behind 00:21:29.570 --> 00:21:33.190 align:start position:0% wrote most of it is sitting right behind you<00:21:31.690> talk<00:21:32.690> to<00:21:32.810> him 00:21:33.190 --> 00:21:33.200 align:start position:0% you talk to him 00:21:33.200 --> 00:21:36.730 align:start position:0% you talk to him but<00:21:34.120> yeah<00:21:35.120> so<00:21:35.570> a<00:21:35.930> lot<00:21:36.230> of<00:21:36.260> the<00:21:36.380> stuff<00:21:36.560> doesn't 00:21:36.730 --> 00:21:36.740 align:start position:0% but yeah so a lot of the stuff doesn't 00:21:36.740 --> 00:21:39.160 align:start position:0% but yeah so a lot of the stuff doesn't exist<00:21:37.100> in<00:21:37.250> rust<00:21:37.490> yet<00:21:37.790> when<00:21:38.420> we<00:21:38.570> started<00:21:38.870> to<00:21:39.020> use 00:21:39.160 --> 00:21:39.170 align:start position:0% exist in rust yet when we started to use 00:21:39.170 --> 00:21:41.710 align:start position:0% exist in rust yet when we started to use rust<00:21:39.440> like<00:21:39.680> these<00:21:39.860> libraries<00:21:40.400> like<00:21:40.760> we<00:21:41.510> had<00:21:41.630> to 00:21:41.710 --> 00:21:41.720 align:start position:0% rust like these libraries like we had to 00:21:41.720 --> 00:21:42.790 align:start position:0% rust like these libraries like we had to write<00:21:41.900> a<00:21:41.930> lot<00:21:42.110> of<00:21:42.230> them<00:21:42.320> ourselves 00:21:42.790 --> 00:21:42.800 align:start position:0% write a lot of them ourselves 00:21:42.800 --> 00:21:49.660 align:start position:0% write a lot of them ourselves so<00:21:43.510> mostly<00:21:44.510> our<00:21:44.660> own<00:21:44.750> code<00:21:47.770> just<00:21:48.770> another<00:21:49.490> one 00:21:49.660 --> 00:21:49.670 align:start position:0% so mostly our own code just another one 00:21:49.670 --> 00:21:50.500 align:start position:0% so mostly our own code just another one I'll<00:21:49.760> top<00:21:50.000> my<00:21:50.120> head 00:21:50.500 --> 00:21:50.510 align:start position:0% I'll top my head 00:21:50.510 --> 00:21:52.090 align:start position:0% I'll top my head you<00:21:50.630> mentioned<00:21:50.990> alternative<00:21:51.560> networking 00:21:52.090 --> 00:21:52.100 align:start position:0% you mentioned alternative networking 00:21:52.100 --> 00:21:55.360 align:start position:0% you mentioned alternative networking protocols<00:21:52.880> is<00:21:53.240> i2p<00:21:53.660> in<00:21:54.200> any<00:21:54.620> sort<00:21:54.860> of<00:21:54.920> plans<00:21:55.160> or 00:21:55.360 --> 00:21:55.370 align:start position:0% protocols is i2p in any sort of plans or 00:21:55.370 --> 00:22:00.090 align:start position:0% protocols is i2p in any sort of plans or anything<00:21:55.550> like<00:21:55.760> that<00:21:55.820> I<00:21:56.180> to<00:21:56.780> P<00:21:57.260> what's<00:21:58.100> I<00:21:58.190> to<00:21:58.250> P 00:22:00.090 --> 00:22:00.100 align:start position:0% anything like that I to P what's I to P 00:22:00.100 --> 00:22:02.560 align:start position:0% anything like that I to P what's I to P sorry<00:22:01.100> say<00:22:01.250> it<00:22:01.280> again<00:22:01.340> for<00:22:01.640> the<00:22:01.700> mic<00:22:01.820> over<00:22:02.330> efer 00:22:02.560 --> 00:22:02.570 align:start position:0% sorry say it again for the mic over efer 00:22:02.570 --> 00:22:03.430 align:start position:0% sorry say it again for the mic over efer Manero<00:22:02.870> suppose<00:22:03.110> to<00:22:03.170> have<00:22:03.260> additional 00:22:03.430 --> 00:22:03.440 align:start position:0% Manero suppose to have additional 00:22:03.440 --> 00:22:06.820 align:start position:0% Manero suppose to have additional privacy<00:22:04.040> here<00:22:04.190> at<00:22:04.280> ease<00:22:04.430> over<00:22:04.730> p<00:22:05.030> DB<00:22:05.260> okay<00:22:06.260> yeah 00:22:06.820 --> 00:22:06.830 align:start position:0% privacy here at ease over p DB okay yeah 00:22:06.830 --> 00:22:08.880 align:start position:0% privacy here at ease over p DB okay yeah I<00:22:07.760> don't<00:22:08.150> see<00:22:08.360> why<00:22:08.540> not 00:22:08.880 --> 00:22:08.890 align:start position:0% I don't see why not 00:22:08.890 --> 00:22:11.350 align:start position:0% I don't see why not basically<00:22:09.890> what<00:22:10.520> none<00:22:10.820> of<00:22:10.970> the<00:22:11.090> code<00:22:11.300> that 00:22:11.350 --> 00:22:11.360 align:start position:0% basically what none of the code that 00:22:11.360 --> 00:22:14.470 align:start position:0% basically what none of the code that uses<00:22:11.720> networking<00:22:12.760> assumes<00:22:13.760> anything<00:22:14.270> about 00:22:14.470 --> 00:22:14.480 align:start position:0% uses networking assumes anything about 00:22:14.480 --> 00:22:15.820 align:start position:0% uses networking assumes anything about the<00:22:14.630> networking<00:22:14.960> protocol<00:22:15.260> that's<00:22:15.680> being 00:22:15.820 --> 00:22:15.830 align:start position:0% the networking protocol that's being 00:22:15.830 --> 00:22:18.790 align:start position:0% the networking protocol that's being used<00:22:16.390> so<00:22:17.390> it's<00:22:17.540> fairly<00:22:17.750> generic<00:22:17.990> like<00:22:18.470> usually 00:22:18.790 --> 00:22:18.800 align:start position:0% used so it's fairly generic like usually 00:22:18.800 --> 00:22:19.870 align:start position:0% used so it's fairly generic like usually at<00:22:18.920> least<00:22:18.950> in<00:22:19.160> the<00:22:19.220> consensus<00:22:19.670> algorithm 00:22:19.870 --> 00:22:19.880 align:start position:0% at least in the consensus algorithm 00:22:19.880 --> 00:22:21.520 align:start position:0% at least in the consensus algorithm stuff<00:22:20.270> for<00:22:20.480> the<00:22:20.540> block<00:22:20.690> propagation<00:22:21.290> stuff 00:22:21.520 --> 00:22:21.530 align:start position:0% stuff for the block propagation stuff 00:22:21.530 --> 00:22:23.560 align:start position:0% stuff for the block propagation stuff it's<00:22:21.680> like<00:22:21.740> you<00:22:22.340> have<00:22:22.550> a<00:22:22.580> stream<00:22:23.060> of<00:22:23.240> incoming 00:22:23.560 --> 00:22:23.570 align:start position:0% it's like you have a stream of incoming 00:22:23.570 --> 00:22:24.910 align:start position:0% it's like you have a stream of incoming messages<00:22:23.750> in<00:22:24.140> a<00:22:24.200> stream<00:22:24.410> of<00:22:24.530> outgoing 00:22:24.910 --> 00:22:24.920 align:start position:0% messages in a stream of outgoing 00:22:24.920 --> 00:22:26.800 align:start position:0% messages in a stream of outgoing messages<00:22:25.310> on<00:22:25.460> some<00:22:25.640> topic<00:22:26.030> or<00:22:26.180> some<00:22:26.450> period<00:22:26.750> of 00:22:26.800 --> 00:22:26.810 align:start position:0% messages on some topic or some period of 00:22:26.810 --> 00:22:28.090 align:start position:0% messages on some topic or some period of your<00:22:26.870> connection<00:22:27.320> so<00:22:27.800> it<00:22:27.860> doesn't<00:22:28.040> really 00:22:28.090 --> 00:22:28.100 align:start position:0% your connection so it doesn't really 00:22:28.100 --> 00:22:29.560 align:start position:0% your connection so it doesn't really matter<00:22:28.310> what<00:22:28.610> you're<00:22:28.760> using<00:22:28.970> for<00:22:29.120> that<00:22:29.360> loopy 00:22:29.560 --> 00:22:29.570 align:start position:0% matter what you're using for that loopy 00:22:29.570 --> 00:22:31.150 align:start position:0% matter what you're using for that loopy TV<00:22:29.780> is<00:22:29.870> one<00:22:30.020> option<00:22:30.470> and<00:22:30.590> that's<00:22:30.710> the<00:22:30.950> one<00:22:31.070> that 00:22:31.150 --> 00:22:31.160 align:start position:0% TV is one option and that's the one that 00:22:31.160 --> 00:22:33.130 align:start position:0% TV is one option and that's the one that we've<00:22:31.250> coded<00:22:31.580> up<00:22:31.700> but<00:22:32.300> it<00:22:32.420> shouldn't<00:22:32.810> be<00:22:32.900> too 00:22:33.130 --> 00:22:33.140 align:start position:0% we've coded up but it shouldn't be too 00:22:33.140 --> 00:22:35.380 align:start position:0% we've coded up but it shouldn't be too hard<00:22:33.170> if<00:22:33.680> you<00:22:33.800> have<00:22:33.950> like<00:22:34.130> an<00:22:34.220> IP<00:22:34.400> to<00:22:34.730> P<00:22:34.910> library 00:22:35.380 --> 00:22:35.390 align:start position:0% hard if you have like an IP to P library 00:22:35.390 --> 00:22:36.850 align:start position:0% hard if you have like an IP to P library that<00:22:35.480> you<00:22:35.570> can<00:22:35.600> link<00:22:35.900> into<00:22:36.200> rust<00:22:36.380> or<00:22:36.590> do<00:22:36.710> an 00:22:36.850 --> 00:22:36.860 align:start position:0% that you can link into rust or do an 00:22:36.860 --> 00:22:39.280 align:start position:0% that you can link into rust or do an implementation<00:22:37.220> of<00:22:37.760> that<00:22:37.790> in<00:22:38.000> rust<00:22:38.180> to<00:22:38.840> slot 00:22:39.280 --> 00:22:39.290 align:start position:0% implementation of that in rust to slot 00:22:39.290 --> 00:22:40.810 align:start position:0% implementation of that in rust to slot that<00:22:39.500> in<00:22:39.590> as<00:22:39.710> well 00:22:40.810 --> 00:22:40.820 align:start position:0% that in as well 00:22:40.820 --> 00:22:43.450 align:start position:0% that in as well we're<00:22:41.720> not<00:22:41.950> probably<00:22:42.950> going<00:22:43.130> to<00:22:43.250> do<00:22:43.370> an 00:22:43.450 --> 00:22:43.460 align:start position:0% we're not probably going to do an 00:22:43.460 --> 00:22:45.130 align:start position:0% we're not probably going to do an implementation<00:22:43.640> of<00:22:44.060> that<00:22:44.120> ourselves<00:22:44.750> but 00:22:45.130 --> 00:22:45.140 align:start position:0% implementation of that ourselves but 00:22:45.140 --> 00:22:46.960 align:start position:0% implementation of that ourselves but it's<00:22:45.650> an<00:22:45.770> open<00:22:46.010> source<00:22:46.190> project<00:22:46.430> and<00:22:46.880> that 00:22:46.960 --> 00:22:46.970 align:start position:0% it's an open source project and that 00:22:46.970 --> 00:22:48.550 align:start position:0% it's an open source project and that kind<00:22:47.150> of<00:22:47.210> contribution<00:22:47.780> is<00:22:48.200> the<00:22:48.320> stuff<00:22:48.530> that 00:22:48.550 --> 00:22:48.560 align:start position:0% kind of contribution is the stuff that 00:22:48.560 --> 00:22:50.410 align:start position:0% kind of contribution is the stuff that we<00:22:48.740> actually<00:22:48.890> really<00:22:49.190> want<00:22:49.340> to<00:22:49.430> see<00:22:49.580> so<00:22:50.330> if 00:22:50.410 --> 00:22:50.420 align:start position:0% we actually really want to see so if 00:22:50.420 --> 00:22:52.030 align:start position:0% we actually really want to see so if there<00:22:50.540> were<00:22:50.660> to<00:22:50.750> be<00:22:50.810> a<00:22:50.870> pull<00:22:51.080> request<00:22:51.110> open<00:22:51.650> to 00:22:52.030 --> 00:22:52.040 align:start position:0% there were to be a pull request open to 00:22:52.040 --> 00:22:52.960 align:start position:0% there were to be a pull request open to implement<00:22:52.430> ITP 00:22:52.960 --> 00:22:52.970 align:start position:0% implement ITP 00:22:52.970 --> 00:22:54.430 align:start position:0% implement ITP support<00:22:53.780> and<00:22:53.900> substrate<00:22:54.260> we<00:22:54.320> would 00:22:54.430 --> 00:22:54.440 align:start position:0% support and substrate we would 00:22:54.440 --> 00:22:57.880 align:start position:0% support and substrate we would definitely<00:22:54.590> review<00:22:55.220> it<00:22:55.310> and<00:22:55.430> merge<00:22:55.580> it<00:22:56.890> yeah 00:22:57.880 --> 00:22:57.890 align:start position:0% definitely review it and merge it yeah 00:22:57.890 --> 00:23:02.320 align:start position:0% definitely review it and merge it yeah will<00:22:58.250> do<00:22:59.110> all<00:23:00.110> right<00:23:00.410> that<00:23:01.400> about<00:23:01.730> wraps<00:23:02.090> it<00:23:02.210> up 00:23:02.320 --> 00:23:02.330 align:start position:0% will do all right that about wraps it up 00:23:02.330 --> 00:23:04.150 align:start position:0% will do all right that about wraps it up for<00:23:02.390> this<00:23:02.660> room<00:23:02.930> I'm<00:23:03.200> Corey<00:23:03.530> petty<00:23:03.740> from<00:23:04.070> the 00:23:04.150 --> 00:23:04.160 align:start position:0% for this room I'm Corey petty from the 00:23:04.160 --> 00:23:06.070 align:start position:0% for this room I'm Corey petty from the Bitcoin<00:23:04.340> podcast<00:23:04.880> and<00:23:05.090> status<00:23:05.450> and<00:23:05.750> there's 00:23:06.070 --> 00:23:06.080 align:start position:0% Bitcoin podcast and status and there's 00:23:06.080 --> 00:23:07.270 align:start position:0% Bitcoin podcast and status and there's still<00:23:06.260> some<00:23:06.440> more<00:23:06.530> stuff<00:23:06.740> on<00:23:06.860> the<00:23:06.920> mainstage 00:23:07.270 --> 00:23:07.280 align:start position:0% still some more stuff on the mainstage 00:23:07.280 --> 00:23:08.530 align:start position:0% still some more stuff on the mainstage so<00:23:07.580> thanks<00:23:07.850> guys 00:23:08.530 --> 00:23:08.540 align:start position:0% so thanks guys 00:23:08.540 --> 00:23:18.259 align:start position:0% so thanks guys [Applause] 00:23:18.259 --> 00:23:18.269 align:start position:0% 00:23:18.269 --> 00:23:20.330 align:start position:0% you