WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:11.570 align:start position:0% [Music] 00:00:11.570 --> 00:00:11.580 align:start position:0% 00:00:11.580 --> 00:00:13.190 align:start position:0% yeah<00:00:12.059> so<00:00:12.240> I'm<00:00:12.540> going<00:00:12.719> to<00:00:12.719> be<00:00:12.840> talking<00:00:12.960> about 00:00:13.190 --> 00:00:13.200 align:start position:0% yeah so I'm going to be talking about 00:00:13.200 --> 00:00:16.490 align:start position:0% yeah so I'm going to be talking about the<00:00:13.740> kzg<00:00:14.460> ceremony<00:00:15.000> or<00:00:15.719> how<00:00:16.020> I<00:00:16.199> learned<00:00:16.379> to 00:00:16.490 --> 00:00:16.500 align:start position:0% the kzg ceremony or how I learned to 00:00:16.500 --> 00:00:19.090 align:start position:0% the kzg ceremony or how I learned to stop<00:00:16.619> worrying<00:00:17.100> and<00:00:17.400> love<00:00:17.520> trusted<00:00:18.000> setups<00:00:18.420> so 00:00:19.090 --> 00:00:19.100 align:start position:0% stop worrying and love trusted setups so 00:00:19.100 --> 00:00:21.830 align:start position:0% stop worrying and love trusted setups so five<00:00:20.100> months<00:00:20.460> ago<00:00:20.699> I<00:00:21.240> think<00:00:21.300> I<00:00:21.480> wasn't<00:00:21.600> the 00:00:21.830 --> 00:00:21.840 align:start position:0% five months ago I think I wasn't the 00:00:21.840 --> 00:00:24.529 align:start position:0% five months ago I think I wasn't the only<00:00:21.960> one<00:00:22.199> who<00:00:22.800> stopped<00:00:23.460> using<00:00:23.699> the<00:00:23.820> chain<00:00:24.000> or 00:00:24.529 --> 00:00:24.539 align:start position:0% only one who stopped using the chain or 00:00:24.539 --> 00:00:27.769 align:start position:0% only one who stopped using the chain or started<00:00:25.080> using<00:00:25.380> it<00:00:25.619> very<00:00:26.460> sporadically 00:00:27.769 --> 00:00:27.779 align:start position:0% started using it very sporadically 00:00:27.779 --> 00:00:32.630 align:start position:0% started using it very sporadically and<00:00:28.699> the<00:00:29.720> the<00:00:30.720> demand<00:00:31.199> is<00:00:31.679> just<00:00:31.920> way<00:00:32.340> way 00:00:32.630 --> 00:00:32.640 align:start position:0% and the the demand is just way way 00:00:32.640 --> 00:00:35.569 align:start position:0% and the the demand is just way way outstrips<00:00:33.420> the<00:00:33.719> supply<00:00:33.899> of<00:00:34.260> block<00:00:34.559> space 00:00:35.569 --> 00:00:35.579 align:start position:0% outstrips the supply of block space 00:00:35.579 --> 00:00:39.530 align:start position:0% outstrips the supply of block space and<00:00:36.420> this<00:00:37.380> is<00:00:37.440> this<00:00:37.680> is<00:00:37.800> not<00:00:37.980> a<00:00:38.340> future<00:00:38.940> we<00:00:39.300> can 00:00:39.530 --> 00:00:39.540 align:start position:0% and this is this is not a future we can 00:00:39.540 --> 00:00:43.190 align:start position:0% and this is this is not a future we can continue<00:00:40.500> on<00:00:40.800> into<00:00:41.040> for<00:00:41.820> ethereum<00:00:42.360> so<00:00:42.719> we<00:00:43.020> need 00:00:43.190 --> 00:00:43.200 align:start position:0% continue on into for ethereum so we need 00:00:43.200 --> 00:00:44.869 align:start position:0% continue on into for ethereum so we need to<00:00:43.379> greatly<00:00:43.680> change<00:00:43.920> how<00:00:44.219> we're<00:00:44.399> doing<00:00:44.579> things 00:00:44.869 --> 00:00:44.879 align:start position:0% to greatly change how we're doing things 00:00:44.879 --> 00:00:48.770 align:start position:0% to greatly change how we're doing things to<00:00:45.840> scale<00:00:46.140> our<00:00:46.440> capabilities<00:00:46.980> the<00:00:47.700> l2s<00:00:48.300> are 00:00:48.770 --> 00:00:48.780 align:start position:0% to scale our capabilities the l2s are 00:00:48.780 --> 00:00:52.250 align:start position:0% to scale our capabilities the l2s are the<00:00:49.079> promise<00:00:49.620> way<00:00:50.219> of<00:00:50.460> doing<00:00:50.760> this 00:00:52.250 --> 00:00:52.260 align:start position:0% the promise way of doing this 00:00:52.260 --> 00:00:55.790 align:start position:0% the promise way of doing this um<00:00:52.320> for<00:00:53.219> your<00:00:53.399> multiple<00:00:54.180> years<00:00:54.420> now<00:00:54.899> we've 00:00:55.790 --> 00:00:55.800 align:start position:0% um for your multiple years now we've 00:00:55.800 --> 00:00:58.189 align:start position:0% um for your multiple years now we've been<00:00:55.920> hearing<00:00:56.219> about<00:00:56.460> the<00:00:57.059> roll-up<00:00:57.840> Centric 00:00:58.189 --> 00:00:58.199 align:start position:0% been hearing about the roll-up Centric 00:00:58.199 --> 00:01:00.650 align:start position:0% been hearing about the roll-up Centric design<00:00:58.460> and<00:00:59.460> how<00:00:59.640> l2s<00:01:00.239> aren't<00:01:00.420> going<00:01:00.600> to 00:01:00.650 --> 00:01:00.660 align:start position:0% design and how l2s aren't going to 00:01:00.660 --> 00:01:03.770 align:start position:0% design and how l2s aren't going to provide<00:01:00.899> us<00:01:01.140> with<00:01:01.820> what<00:01:02.820> we<00:01:02.940> need 00:01:03.770 --> 00:01:03.780 align:start position:0% provide us with what we need 00:01:03.780 --> 00:01:07.690 align:start position:0% provide us with what we need but<00:01:04.640> l2s<00:01:05.640> are<00:01:05.939> only<00:01:06.060> part<00:01:06.540> of 00:01:07.690 --> 00:01:07.700 align:start position:0% but l2s are only part of 00:01:07.700 --> 00:01:11.810 align:start position:0% but l2s are only part of what's<00:01:08.700> required<00:01:09.180> scale<00:01:10.080> incomes<00:01:10.560> in<00:01:11.040> sort<00:01:11.760> of 00:01:11.810 --> 00:01:11.820 align:start position:0% what's required scale incomes in sort of 00:01:11.820 --> 00:01:13.670 align:start position:0% what's required scale incomes in sort of two<00:01:12.000> variants<00:01:12.360> for<00:01:12.600> ethereum<00:01:13.080> there<00:01:13.439> is 00:01:13.670 --> 00:01:13.680 align:start position:0% two variants for ethereum there is 00:01:13.680 --> 00:01:16.450 align:start position:0% two variants for ethereum there is scaling<00:01:14.640> compute 00:01:16.450 --> 00:01:16.460 align:start position:0% scaling compute 00:01:16.460 --> 00:01:20.149 align:start position:0% scaling compute l2s<00:01:17.460> take<00:01:18.240> us<00:01:18.420> from<00:01:18.960> what<00:01:19.320> ethereum<00:01:19.799> is<00:01:19.920> right 00:01:20.149 --> 00:01:20.159 align:start position:0% l2s take us from what ethereum is right 00:01:20.159 --> 00:01:22.310 align:start position:0% l2s take us from what ethereum is right now<00:01:20.280> which<00:01:20.580> is<00:01:20.759> effectively<00:01:21.299> a<00:01:21.840> single 00:01:22.310 --> 00:01:22.320 align:start position:0% now which is effectively a single 00:01:22.320 --> 00:01:26.390 align:start position:0% now which is effectively a single threaded<00:01:22.799> very<00:01:23.220> slow<00:01:23.759> computer<00:01:24.860> to<00:01:25.860> a 00:01:26.390 --> 00:01:26.400 align:start position:0% threaded very slow computer to a 00:01:26.400 --> 00:01:28.609 align:start position:0% threaded very slow computer to a massively<00:01:26.820> multi-threaded<00:01:27.659> much<00:01:28.259> faster 00:01:28.609 --> 00:01:28.619 align:start position:0% massively multi-threaded much faster 00:01:28.619 --> 00:01:30.350 align:start position:0% massively multi-threaded much faster processor 00:01:30.350 --> 00:01:30.360 align:start position:0% processor 00:01:30.360 --> 00:01:32.690 align:start position:0% processor the<00:01:30.780> problem<00:01:30.900> is<00:01:31.140> is<00:01:31.439> that<00:01:31.680> l2s<00:01:32.340> on<00:01:32.460> their<00:01:32.580> own 00:01:32.690 --> 00:01:32.700 align:start position:0% the problem is is that l2s on their own 00:01:32.700 --> 00:01:35.030 align:start position:0% the problem is is that l2s on their own don't<00:01:33.060> have<00:01:33.299> a<00:01:33.600> way<00:01:33.720> of<00:01:34.080> storing<00:01:34.500> this<00:01:34.619> data 00:01:35.030 --> 00:01:35.040 align:start position:0% don't have a way of storing this data 00:01:35.040 --> 00:01:36.530 align:start position:0% don't have a way of storing this data enter 00:01:36.530 --> 00:01:36.540 align:start position:0% enter 00:01:36.540 --> 00:01:38.350 align:start position:0% enter proto-dunk<00:01:37.320> sharding<00:01:37.680> also<00:01:38.100> known<00:01:38.159> as 00:01:38.350 --> 00:01:38.360 align:start position:0% proto-dunk sharding also known as 00:01:38.360 --> 00:01:41.990 align:start position:0% proto-dunk sharding also known as eip4844<00:01:39.360> and<00:01:40.200> the<00:01:40.500> idea<00:01:40.680> behind<00:01:41.040> here<00:01:41.280> is<00:01:41.640> that 00:01:41.990 --> 00:01:42.000 align:start position:0% eip4844 and the idea behind here is that 00:01:42.000 --> 00:01:43.870 align:start position:0% eip4844 and the idea behind here is that we<00:01:42.479> enable 00:01:43.870 --> 00:01:43.880 align:start position:0% we enable 00:01:43.880 --> 00:01:47.330 align:start position:0% we enable incredible<00:01:44.880> amounts<00:01:45.240> of<00:01:45.540> data<00:01:46.020> for<00:01:46.500> these<00:01:46.799> l2s 00:01:47.330 --> 00:01:47.340 align:start position:0% incredible amounts of data for these l2s 00:01:47.340 --> 00:01:51.170 align:start position:0% incredible amounts of data for these l2s to<00:01:47.460> use<00:01:47.579> and<00:01:48.360> just<00:01:48.600> for<00:01:48.840> them<00:01:49.020> such<00:01:49.979> that<00:01:50.579> they 00:01:51.170 --> 00:01:51.180 align:start position:0% to use and just for them such that they 00:01:51.180 --> 00:01:52.270 align:start position:0% to use and just for them such that they can 00:01:52.270 --> 00:01:52.280 align:start position:0% can 00:01:52.280 --> 00:01:54.530 align:start position:0% can provide<00:01:53.280> if<00:01:53.579> they're<00:01:53.700> providing<00:01:54.060> the<00:01:54.180> compute 00:01:54.530 --> 00:01:54.540 align:start position:0% provide if they're providing the compute 00:01:54.540 --> 00:01:57.530 align:start position:0% provide if they're providing the compute here's<00:01:54.899> the<00:01:55.020> storage<00:01:55.259> to<00:01:55.740> match<00:01:56.220> that<00:01:56.540> and 00:01:57.530 --> 00:01:57.540 align:start position:0% here's the storage to match that and 00:01:57.540 --> 00:02:00.469 align:start position:0% here's the storage to match that and scale<00:01:57.960> ethereum<00:01:58.439> up<00:01:58.560> to<00:01:58.740> to<00:01:58.920> what<00:01:59.399> we<00:01:59.520> need<00:01:59.640> so 00:02:00.469 --> 00:02:00.479 align:start position:0% scale ethereum up to to what we need so 00:02:00.479 --> 00:02:03.170 align:start position:0% scale ethereum up to to what we need so what<00:02:00.960> does<00:02:01.259> this<00:02:01.740> protodank<00:02:02.579> sharding<00:02:03.000> look 00:02:03.170 --> 00:02:03.180 align:start position:0% what does this protodank sharding look 00:02:03.180 --> 00:02:06.950 align:start position:0% what does this protodank sharding look like<00:02:03.240> we<00:02:03.780> have<00:02:03.960> these<00:02:04.320> Notions<00:02:04.740> of<00:02:05.159> blobs<00:02:05.960> it's 00:02:06.950 --> 00:02:06.960 align:start position:0% like we have these Notions of blobs it's 00:02:06.960 --> 00:02:09.770 align:start position:0% like we have these Notions of blobs it's some<00:02:07.680> arbitrary<00:02:08.520> data<00:02:08.880> from<00:02:09.119> the<00:02:09.300> protocol's 00:02:09.770 --> 00:02:09.780 align:start position:0% some arbitrary data from the protocol's 00:02:09.780 --> 00:02:11.089 align:start position:0% some arbitrary data from the protocol's perspective<00:02:10.080> we<00:02:10.259> don't<00:02:10.380> really<00:02:10.560> care<00:02:10.739> what<00:02:10.979> it 00:02:11.089 --> 00:02:11.099 align:start position:0% perspective we don't really care what it 00:02:11.099 --> 00:02:14.449 align:start position:0% perspective we don't really care what it is<00:02:11.660> but<00:02:12.660> to<00:02:13.080> the<00:02:13.319> roll<00:02:13.500> ups<00:02:13.920> it's<00:02:14.160> basically 00:02:14.449 --> 00:02:14.459 align:start position:0% is but to the roll ups it's basically 00:02:14.459 --> 00:02:17.390 align:start position:0% is but to the roll ups it's basically going<00:02:14.700> to<00:02:14.879> be<00:02:15.000> compressed<00:02:15.900> transactions<00:02:16.739> and 00:02:17.390 --> 00:02:17.400 align:start position:0% going to be compressed transactions and 00:02:17.400 --> 00:02:19.309 align:start position:0% going to be compressed transactions and then<00:02:17.580> we<00:02:17.760> use<00:02:17.940> this<00:02:18.180> device<00:02:18.420> called<00:02:18.720> the<00:02:18.840> kzg 00:02:19.309 --> 00:02:19.319 align:start position:0% then we use this device called the kzg 00:02:19.319 --> 00:02:22.070 align:start position:0% then we use this device called the kzg commitment<00:02:19.800> to<00:02:20.700> compress<00:02:21.120> down<00:02:21.420> this<00:02:21.660> data 00:02:22.070 --> 00:02:22.080 align:start position:0% commitment to compress down this data 00:02:22.080 --> 00:02:24.170 align:start position:0% commitment to compress down this data and<00:02:22.379> Only<00:02:22.560> Store<00:02:22.860> a<00:02:23.280> small<00:02:23.400> reference<00:02:23.819> to<00:02:24.000> it 00:02:24.170 --> 00:02:24.180 align:start position:0% and Only Store a small reference to it 00:02:24.180 --> 00:02:28.910 align:start position:0% and Only Store a small reference to it on<00:02:24.300> chain<00:02:24.860> then<00:02:25.860> once<00:02:26.540> the<00:02:27.540> block<00:02:28.319> proposer 00:02:28.910 --> 00:02:28.920 align:start position:0% on chain then once the block proposer 00:02:28.920 --> 00:02:31.729 align:start position:0% on chain then once the block proposer has<00:02:29.459> proposed<00:02:30.239> this<00:02:30.360> data<00:02:30.780> the<00:02:31.260> validators 00:02:31.729 --> 00:02:31.739 align:start position:0% has proposed this data the validators 00:02:31.739 --> 00:02:33.949 align:start position:0% has proposed this data the validators there<00:02:31.980> in<00:02:32.099> the<00:02:32.220> bottom<00:02:32.459> check<00:02:33.180> that<00:02:33.420> this<00:02:33.599> data 00:02:33.949 --> 00:02:33.959 align:start position:0% there in the bottom check that this data 00:02:33.959 --> 00:02:35.570 align:start position:0% there in the bottom check that this data is<00:02:34.140> available<00:02:34.500> they<00:02:34.920> check<00:02:35.099> that<00:02:35.280> they<00:02:35.459> have 00:02:35.570 --> 00:02:35.580 align:start position:0% is available they check that they have 00:02:35.580 --> 00:02:39.250 align:start position:0% is available they check that they have access<00:02:35.760> to<00:02:36.060> it<00:02:36.420> and<00:02:37.020> that<00:02:37.260> the<00:02:37.560> network<00:02:38.340> has 00:02:39.250 --> 00:02:39.260 align:start position:0% access to it and that the network has 00:02:39.260 --> 00:02:44.150 align:start position:0% access to it and that the network has propagated<00:02:40.260> this<00:02:40.560> and<00:02:41.519> if<00:02:41.819> so<00:02:42.140> they<00:02:43.140> vote<00:02:43.980> that 00:02:44.150 --> 00:02:44.160 align:start position:0% propagated this and if so they vote that 00:02:44.160 --> 00:02:47.210 align:start position:0% propagated this and if so they vote that they've<00:02:44.459> seen<00:02:44.700> this<00:02:45.060> data<00:02:45.480> and<00:02:46.440> biscuits<00:02:47.040> also 00:02:47.210 --> 00:02:47.220 align:start position:0% they've seen this data and biscuits also 00:02:47.220 --> 00:02:48.290 align:start position:0% they've seen this data and biscuits also put<00:02:47.280> on<00:02:47.400> the<00:02:47.519> blockchain<00:02:47.819> so<00:02:48.060> from<00:02:48.239> the 00:02:48.290 --> 00:02:48.300 align:start position:0% put on the blockchain so from the 00:02:48.300 --> 00:02:49.670 align:start position:0% put on the blockchain so from the blockchain's<00:02:48.780> perspective<00:02:49.019> we<00:02:49.319> know<00:02:49.440> that 00:02:49.670 --> 00:02:49.680 align:start position:0% blockchain's perspective we know that 00:02:49.680 --> 00:02:51.650 align:start position:0% blockchain's perspective we know that this<00:02:49.860> data<00:02:50.280> was<00:02:50.640> around<00:02:50.819> there<00:02:51.300> was<00:02:51.480> an 00:02:51.650 --> 00:02:51.660 align:start position:0% this data was around there was an 00:02:51.660 --> 00:02:54.589 align:start position:0% this data was around there was an opportunity<00:02:52.019> at<00:02:52.319> some<00:02:52.500> point<00:02:52.700> for<00:02:53.700> all<00:02:54.420> the 00:02:54.589 --> 00:02:54.599 align:start position:0% opportunity at some point for all the 00:02:54.599 --> 00:02:56.150 align:start position:0% opportunity at some point for all the Roll-Ups<00:02:55.140> and<00:02:55.200> roll-up<00:02:55.440> users<00:02:55.800> to<00:02:55.980> download 00:02:56.150 --> 00:02:56.160 align:start position:0% Roll-Ups and roll-up users to download 00:02:56.160 --> 00:02:58.009 align:start position:0% Roll-Ups and roll-up users to download the<00:02:56.459> data<00:02:56.760> that<00:02:56.940> they<00:02:57.060> care<00:02:57.239> about<00:02:57.420> the 00:02:58.009 --> 00:02:58.019 align:start position:0% the data that they care about the 00:02:58.019 --> 00:03:00.410 align:start position:0% the data that they care about the validators<00:02:58.500> then<00:02:58.920> save<00:02:59.400> the<00:02:59.640> data<00:02:59.879> locally<00:03:00.180> to 00:03:00.410 --> 00:03:00.420 align:start position:0% validators then save the data locally to 00:03:00.420 --> 00:03:02.470 align:start position:0% validators then save the data locally to their<00:03:00.540> own<00:03:00.660> disks 00:03:02.470 --> 00:03:02.480 align:start position:0% their own disks 00:03:02.480 --> 00:03:06.650 align:start position:0% their own disks and<00:03:03.560> this<00:03:04.560> this<00:03:04.739> gets<00:03:05.340> stored<00:03:05.640> but<00:03:06.360> this<00:03:06.540> has 00:03:06.650 --> 00:03:06.660 align:start position:0% and this this gets stored but this has 00:03:06.660 --> 00:03:08.630 align:start position:0% and this this gets stored but this has the<00:03:06.900> problem<00:03:07.080> which<00:03:07.620> ethereum<00:03:08.040> has<00:03:08.220> right<00:03:08.400> now 00:03:08.630 --> 00:03:08.640 align:start position:0% the problem which ethereum has right now 00:03:08.640 --> 00:03:10.490 align:start position:0% the problem which ethereum has right now which<00:03:09.300> is<00:03:09.420> where<00:03:09.660> we're<00:03:09.840> storing<00:03:10.140> incredible 00:03:10.490 --> 00:03:10.500 align:start position:0% which is where we're storing incredible 00:03:10.500 --> 00:03:12.589 align:start position:0% which is where we're storing incredible amounts<00:03:10.800> of<00:03:10.860> data<00:03:11.220> again<00:03:11.400> and<00:03:12.060> the<00:03:12.239> idea 00:03:12.589 --> 00:03:12.599 align:start position:0% amounts of data again and the idea 00:03:12.599 --> 00:03:14.390 align:start position:0% amounts of data again and the idea behind<00:03:12.900> Bank<00:03:13.319> charting<00:03:13.860> is<00:03:14.040> that<00:03:14.220> we're 00:03:14.390 --> 00:03:14.400 align:start position:0% behind Bank charting is that we're 00:03:14.400 --> 00:03:15.830 align:start position:0% behind Bank charting is that we're scaling<00:03:14.819> This<00:03:14.879> Way<00:03:15.120> Beyond<00:03:15.360> ethereum's 00:03:15.830 --> 00:03:15.840 align:start position:0% scaling This Way Beyond ethereum's 00:03:15.840 --> 00:03:17.330 align:start position:0% scaling This Way Beyond ethereum's current<00:03:16.019> capabilities<00:03:16.560> which<00:03:16.920> would<00:03:17.159> mean 00:03:17.330 --> 00:03:17.340 align:start position:0% current capabilities which would mean 00:03:17.340 --> 00:03:18.830 align:start position:0% current capabilities which would mean for<00:03:18.180> the<00:03:18.300> people<00:03:18.420> who<00:03:18.659> are<00:03:18.720> already 00:03:18.830 --> 00:03:18.840 align:start position:0% for the people who are already 00:03:18.840 --> 00:03:21.110 align:start position:0% for the people who are already struggling<00:03:19.260> to<00:03:19.440> run<00:03:19.739> their<00:03:20.099> their<00:03:20.400> nodes<00:03:20.700> this 00:03:21.110 --> 00:03:21.120 align:start position:0% struggling to run their their nodes this 00:03:21.120 --> 00:03:22.610 align:start position:0% struggling to run their their nodes this would<00:03:21.300> be<00:03:21.420> unacceptable 00:03:22.610 --> 00:03:22.620 align:start position:0% would be unacceptable 00:03:22.620 --> 00:03:25.970 align:start position:0% would be unacceptable so<00:03:23.159> the<00:03:23.340> final<00:03:23.580> step<00:03:23.879> in<00:03:24.060> this<00:03:24.319> is<00:03:25.319> uh<00:03:25.680> two 00:03:25.970 --> 00:03:25.980 align:start position:0% so the final step in this is uh two 00:03:25.980 --> 00:03:27.170 align:start position:0% so the final step in this is uh two weeks<00:03:26.280> later 00:03:27.170 --> 00:03:27.180 align:start position:0% weeks later 00:03:27.180 --> 00:03:30.110 align:start position:0% weeks later we<00:03:27.720> throw<00:03:27.900> away<00:03:28.319> the<00:03:29.220> data 00:03:30.110 --> 00:03:30.120 align:start position:0% we throw away the data 00:03:30.120 --> 00:03:32.869 align:start position:0% we throw away the data so<00:03:30.720> it's<00:03:31.080> not<00:03:31.319> that<00:03:31.620> we<00:03:31.980> promise<00:03:32.340> to<00:03:32.519> keep<00:03:32.700> this 00:03:32.869 --> 00:03:32.879 align:start position:0% so it's not that we promise to keep this 00:03:32.879 --> 00:03:34.970 align:start position:0% so it's not that we promise to keep this data<00:03:33.300> around<00:03:33.780> forever<00:03:34.200> that's<00:03:34.620> not<00:03:34.800> what 00:03:34.970 --> 00:03:34.980 align:start position:0% data around forever that's not what 00:03:34.980 --> 00:03:37.190 align:start position:0% data around forever that's not what protodank<00:03:35.400> shotting<00:03:35.760> guarantees<00:03:36.239> protagon 00:03:37.190 --> 00:03:37.200 align:start position:0% protodank shotting guarantees protagon 00:03:37.200 --> 00:03:39.050 align:start position:0% protodank shotting guarantees protagon dank<00:03:37.739> shotting<00:03:38.159> guarantees<00:03:38.519> that<00:03:38.760> at<00:03:38.879> some 00:03:39.050 --> 00:03:39.060 align:start position:0% dank shotting guarantees that at some 00:03:39.060 --> 00:03:41.210 align:start position:0% dank shotting guarantees that at some point<00:03:39.300> in<00:03:40.200> the<00:03:40.319> past 00:03:41.210 --> 00:03:41.220 align:start position:0% point in the past 00:03:41.220 --> 00:03:43.250 align:start position:0% point in the past this<00:03:41.640> data<00:03:42.000> was<00:03:42.180> available<00:03:42.420> for<00:03:42.840> people<00:03:42.959> to 00:03:43.250 --> 00:03:43.260 align:start position:0% this data was available for people to 00:03:43.260 --> 00:03:46.550 align:start position:0% this data was available for people to download<00:03:43.819> and<00:03:44.900> should<00:03:45.900> they<00:03:46.019> have<00:03:46.200> wanted<00:03:46.319> to 00:03:46.550 --> 00:03:46.560 align:start position:0% download and should they have wanted to 00:03:46.560 --> 00:03:47.930 align:start position:0% download and should they have wanted to done<00:03:46.739> that<00:03:46.920> to<00:03:47.159> have<00:03:47.340> done<00:03:47.459> this<00:03:47.580> they<00:03:47.760> could 00:03:47.930 --> 00:03:47.940 align:start position:0% done that to have done this they could 00:03:47.940 --> 00:03:51.830 align:start position:0% done that to have done this they could it<00:03:48.659> is<00:03:48.780> then<00:03:48.959> on<00:03:49.500> the<00:03:50.220> Roll-Ups<00:03:50.819> on<00:03:51.360> the<00:03:51.540> users 00:03:51.830 --> 00:03:51.840 align:start position:0% it is then on the Roll-Ups on the users 00:03:51.840 --> 00:03:54.050 align:start position:0% it is then on the Roll-Ups on the users to<00:03:52.680> store<00:03:52.920> the<00:03:53.159> data<00:03:53.400> they're<00:03:53.580> interested<00:03:53.940> in 00:03:54.050 --> 00:03:54.060 align:start position:0% to store the data they're interested in 00:03:54.060 --> 00:03:55.369 align:start position:0% to store the data they're interested in so<00:03:54.299> if<00:03:54.420> you're<00:03:54.540> interested<00:03:54.900> in<00:03:55.019> certain 00:03:55.369 --> 00:03:55.379 align:start position:0% so if you're interested in certain 00:03:55.379 --> 00:03:56.930 align:start position:0% so if you're interested in certain transactions<00:03:56.040> you<00:03:56.220> could<00:03:56.340> store<00:03:56.459> just<00:03:56.760> your 00:03:56.930 --> 00:03:56.940 align:start position:0% transactions you could store just your 00:03:56.940 --> 00:03:59.750 align:start position:0% transactions you could store just your transactions<00:03:57.860> roll<00:03:58.860> up<00:03:59.099> sequences<00:03:59.519> could 00:03:59.750 --> 00:03:59.760 align:start position:0% transactions roll up sequences could 00:03:59.760 --> 00:04:01.690 align:start position:0% transactions roll up sequences could store<00:03:59.940> well<00:04:00.420> we'll<00:04:00.659> be<00:04:00.840> storing<00:04:01.200> everything 00:04:01.690 --> 00:04:01.700 align:start position:0% store well we'll be storing everything 00:04:01.700 --> 00:04:03.830 align:start position:0% store well we'll be storing everything but<00:04:02.700> it's<00:04:02.819> just<00:04:02.940> no<00:04:03.120> longer<00:04:03.299> the<00:04:03.480> Chain's 00:04:03.830 --> 00:04:03.840 align:start position:0% but it's just no longer the Chain's 00:04:03.840 --> 00:04:06.050 align:start position:0% but it's just no longer the Chain's responsibility<00:04:04.319> to<00:04:04.620> store<00:04:04.799> this<00:04:05.040> you<00:04:05.700> can<00:04:05.819> put 00:04:06.050 --> 00:04:06.060 align:start position:0% responsibility to store this you can put 00:04:06.060 --> 00:04:09.949 align:start position:0% responsibility to store this you can put a<00:04:06.239> host<00:04:06.480> on<00:04:06.599> ipfs<00:04:07.400> it<00:04:08.400> doesn't<00:04:08.459> really<00:04:08.640> matter 00:04:09.949 --> 00:04:09.959 align:start position:0% a host on ipfs it doesn't really matter 00:04:09.959 --> 00:04:12.589 align:start position:0% a host on ipfs it doesn't really matter just<00:04:10.620> that<00:04:10.920> validators<00:04:11.879> no<00:04:12.120> longer<00:04:12.360> need<00:04:12.480> to 00:04:12.589 --> 00:04:12.599 align:start position:0% just that validators no longer need to 00:04:12.599 --> 00:04:14.830 align:start position:0% just that validators no longer need to store<00:04:12.780> this<00:04:12.959> so<00:04:13.140> effectively<00:04:13.560> they<00:04:13.860> have<00:04:14.040> this 00:04:14.830 --> 00:04:14.840 align:start position:0% store this so effectively they have this 00:04:14.840 --> 00:04:17.090 align:start position:0% store this so effectively they have this sliding<00:04:15.840> window<00:04:16.019> of<00:04:16.320> the<00:04:16.440> past<00:04:16.560> two<00:04:16.739> weeks<00:04:16.979> of 00:04:17.090 --> 00:04:17.100 align:start position:0% sliding window of the past two weeks of 00:04:17.100 --> 00:04:18.890 align:start position:0% sliding window of the past two weeks of state<00:04:17.220> that<00:04:17.400> they<00:04:17.519> need<00:04:17.639> to<00:04:17.760> look<00:04:17.880> after<00:04:18.060> some 00:04:18.890 --> 00:04:18.900 align:start position:0% state that they need to look after some 00:04:18.900 --> 00:04:21.310 align:start position:0% state that they need to look after some may<00:04:19.139> ask<00:04:19.440> why<00:04:20.100> kzg 00:04:21.310 --> 00:04:21.320 align:start position:0% may ask why kzg 00:04:21.320 --> 00:04:23.749 align:start position:0% may ask why kzg there's<00:04:22.320> a<00:04:22.440> very<00:04:22.560> full<00:04:22.680> table<00:04:22.919> I'm<00:04:23.580> not 00:04:23.749 --> 00:04:23.759 align:start position:0% there's a very full table I'm not 00:04:23.759 --> 00:04:26.090 align:start position:0% there's a very full table I'm not expecting<00:04:24.060> you<00:04:24.180> to<00:04:24.300> take<00:04:24.419> all<00:04:24.540> of<00:04:24.660> it<00:04:24.780> in 00:04:26.090 --> 00:04:26.100 align:start position:0% expecting you to take all of it in 00:04:26.100 --> 00:04:26.749 align:start position:0% expecting you to take all of it in um 00:04:26.749 --> 00:04:26.759 align:start position:0% um 00:04:26.759 --> 00:04:28.850 align:start position:0% um the<00:04:27.360> current<00:04:27.600> solution<00:04:27.960> we<00:04:28.199> use<00:04:28.380> for<00:04:28.620> these 00:04:28.850 --> 00:04:28.860 align:start position:0% the current solution we use for these 00:04:28.860 --> 00:04:30.290 align:start position:0% the current solution we use for these kinds<00:04:29.100> of<00:04:29.100> commitments<00:04:29.520> on<00:04:29.639> chains<00:04:30.000> are<00:04:30.180> the 00:04:30.290 --> 00:04:30.300 align:start position:0% kinds of commitments on chains are the 00:04:30.300 --> 00:04:32.930 align:start position:0% kinds of commitments on chains are the are<00:04:30.479> Merkle<00:04:30.900> trees<00:04:31.520> but<00:04:32.520> as<00:04:32.639> you<00:04:32.759> can<00:04:32.880> see 00:04:32.930 --> 00:04:32.940 align:start position:0% are Merkle trees but as you can see 00:04:32.940 --> 00:04:34.730 align:start position:0% are Merkle trees but as you can see there's<00:04:33.180> lots<00:04:33.419> of<00:04:33.479> red<00:04:33.600> on<00:04:33.780> the<00:04:33.840> Merkel<00:04:34.259> that 00:04:34.730 --> 00:04:34.740 align:start position:0% there's lots of red on the Merkel that 00:04:34.740 --> 00:04:36.530 align:start position:0% there's lots of red on the Merkel that the<00:04:34.919> Char<00:04:35.400> Merkel<00:04:35.759> tree<00:04:35.880> column<00:04:36.180> on<00:04:36.300> the<00:04:36.419> left 00:04:36.530 --> 00:04:36.540 align:start position:0% the Char Merkel tree column on the left 00:04:36.540 --> 00:04:37.969 align:start position:0% the Char Merkel tree column on the left there 00:04:37.969 --> 00:04:37.979 align:start position:0% there 00:04:37.979 --> 00:04:39.890 align:start position:0% there um<00:04:38.040> what<00:04:38.699> and<00:04:38.820> what<00:04:39.060> we<00:04:39.180> really<00:04:39.300> care<00:04:39.540> about<00:04:39.720> is 00:04:39.890 --> 00:04:39.900 align:start position:0% um what and what we really care about is 00:04:39.900 --> 00:04:41.930 align:start position:0% um what and what we really care about is this<00:04:40.080> Top<00:04:40.259> Line<00:04:40.500> right<00:04:41.100> if<00:04:41.400> we're<00:04:41.520> trying<00:04:41.820> to 00:04:41.930 --> 00:04:41.940 align:start position:0% this Top Line right if we're trying to 00:04:41.940 --> 00:04:43.550 align:start position:0% this Top Line right if we're trying to enable 00:04:43.550 --> 00:04:43.560 align:start position:0% enable 00:04:43.560 --> 00:04:44.210 align:start position:0% enable um 00:04:44.210 --> 00:04:44.220 align:start position:0% um 00:04:44.220 --> 00:04:46.490 align:start position:0% um if<00:04:44.759> we're<00:04:44.940> trying<00:04:45.120> to<00:04:45.240> enable<00:04:45.479> Roll-Ups<00:04:46.380> and 00:04:46.490 --> 00:04:46.500 align:start position:0% if we're trying to enable Roll-Ups and 00:04:46.500 --> 00:04:49.370 align:start position:0% if we're trying to enable Roll-Ups and l2s<00:04:47.040> lots<00:04:47.580> of<00:04:47.699> them<00:04:47.759> are<00:04:48.060> ZK<00:04:48.360> EVMS<00:04:48.960> or<00:04:49.080> ZK 00:04:49.370 --> 00:04:49.380 align:start position:0% l2s lots of them are ZK EVMS or ZK 00:04:49.380 --> 00:04:51.530 align:start position:0% l2s lots of them are ZK EVMS or ZK Roll-Ups<00:04:49.919> and<00:04:50.400> they<00:04:50.639> care<00:04:50.820> about<00:04:51.000> being<00:04:51.300> able 00:04:51.530 --> 00:04:51.540 align:start position:0% Roll-Ups and they care about being able 00:04:51.540 --> 00:04:53.990 align:start position:0% Roll-Ups and they care about being able to<00:04:51.720> prove<00:04:52.139> things<00:04:53.040> about<00:04:53.280> this<00:04:53.520> data<00:04:53.820> inside 00:04:53.990 --> 00:04:54.000 align:start position:0% to prove things about this data inside 00:04:54.000 --> 00:04:56.270 align:start position:0% to prove things about this data inside the<00:04:54.240> roll<00:04:54.419> up<00:04:54.660> and<00:04:55.440> as<00:04:55.560> you<00:04:55.740> can<00:04:55.800> see<00:04:55.919> from<00:04:56.100> this 00:04:56.270 --> 00:04:56.280 align:start position:0% the roll up and as you can see from this 00:04:56.280 --> 00:04:58.249 align:start position:0% the roll up and as you can see from this Top<00:04:56.520> Line<00:04:56.699> if<00:04:57.360> we<00:04:57.479> stick<00:04:57.780> to<00:04:57.900> our<00:04:58.080> current 00:04:58.249 --> 00:04:58.259 align:start position:0% Top Line if we stick to our current 00:04:58.259 --> 00:05:00.050 align:start position:0% Top Line if we stick to our current mechanisms<00:04:58.979> it's<00:04:59.280> quite<00:04:59.520> literally<00:04:59.820> not 00:05:00.050 --> 00:05:00.060 align:start position:0% mechanisms it's quite literally not 00:05:00.060 --> 00:05:01.070 align:start position:0% mechanisms it's quite literally not possible 00:05:01.070 --> 00:05:01.080 align:start position:0% possible 00:05:01.080 --> 00:05:03.590 align:start position:0% possible the<00:05:01.800> only<00:05:01.979> realistic<00:05:02.460> or<00:05:02.639> other<00:05:02.820> alternative 00:05:03.590 --> 00:05:03.600 align:start position:0% the only realistic or other alternative 00:05:03.600 --> 00:05:05.450 align:start position:0% the only realistic or other alternative would<00:05:03.840> be<00:05:03.960> ipas<00:05:04.500> but<00:05:04.860> there<00:05:05.160> are<00:05:05.280> several 00:05:05.450 --> 00:05:05.460 align:start position:0% would be ipas but there are several 00:05:05.460 --> 00:05:08.210 align:start position:0% would be ipas but there are several other<00:05:05.580> trade-offs<00:05:06.180> that<00:05:07.020> they<00:05:07.139> make 00:05:08.210 --> 00:05:08.220 align:start position:0% other trade-offs that they make 00:05:08.220 --> 00:05:12.110 align:start position:0% other trade-offs that they make so<00:05:09.360> kcg<00:05:10.199> is<00:05:10.800> a<00:05:11.220> very<00:05:11.280> promising<00:05:11.639> looking<00:05:11.880> thing 00:05:12.110 --> 00:05:12.120 align:start position:0% so kcg is a very promising looking thing 00:05:12.120 --> 00:05:14.810 align:start position:0% so kcg is a very promising looking thing but<00:05:12.300> it<00:05:12.419> has<00:05:12.600> this<00:05:12.900> one<00:05:13.199> big<00:05:13.440> red<00:05:14.280> negative<00:05:14.639> as 00:05:14.810 --> 00:05:14.820 align:start position:0% but it has this one big red negative as 00:05:14.820 --> 00:05:16.129 align:start position:0% but it has this one big red negative as you<00:05:15.000> see<00:05:15.120> over<00:05:15.300> there<00:05:15.540> and<00:05:15.780> that's<00:05:15.900> this 00:05:16.129 --> 00:05:16.139 align:start position:0% you see over there and that's this 00:05:16.139 --> 00:05:17.629 align:start position:0% you see over there and that's this trusted<00:05:16.560> setup<00:05:16.919> and<00:05:17.220> that's<00:05:17.340> what<00:05:17.520> I'm 00:05:17.629 --> 00:05:17.639 align:start position:0% trusted setup and that's what I'm 00:05:17.639 --> 00:05:19.370 align:start position:0% trusted setup and that's what I'm speaking<00:05:18.000> to<00:05:18.120> you<00:05:18.180> about<00:05:18.300> today<00:05:18.600> trusted 00:05:19.370 --> 00:05:19.380 align:start position:0% speaking to you about today trusted 00:05:19.380 --> 00:05:21.350 align:start position:0% speaking to you about today trusted setups<00:05:19.860> thus<00:05:20.340> I<00:05:20.639> hope<00:05:20.759> should<00:05:21.000> make<00:05:21.240> everyone 00:05:21.350 --> 00:05:21.360 align:start position:0% setups thus I hope should make everyone 00:05:21.360 --> 00:05:23.570 align:start position:0% setups thus I hope should make everyone a<00:05:21.600> little<00:05:21.660> bit<00:05:21.780> nervous<00:05:22.139> trust<00:05:23.100> is<00:05:23.220> not<00:05:23.460> a 00:05:23.570 --> 00:05:23.580 align:start position:0% a little bit nervous trust is not a 00:05:23.580 --> 00:05:27.050 align:start position:0% a little bit nervous trust is not a thing<00:05:23.699> we<00:05:23.880> try<00:05:24.120> have<00:05:24.479> in<00:05:25.380> the<00:05:25.620> system<00:05:25.800> is<00:05:26.699> trust 00:05:27.050 --> 00:05:27.060 align:start position:0% thing we try have in the system is trust 00:05:27.060 --> 00:05:29.270 align:start position:0% thing we try have in the system is trust but<00:05:27.240> verify<00:05:27.720> so<00:05:28.020> ideally<00:05:28.440> you<00:05:28.919> shouldn't<00:05:29.160> need 00:05:29.270 --> 00:05:29.280 align:start position:0% but verify so ideally you shouldn't need 00:05:29.280 --> 00:05:30.890 align:start position:0% but verify so ideally you shouldn't need to<00:05:29.400> do<00:05:29.520> this<00:05:29.699> I'd<00:05:30.419> like<00:05:30.539> to<00:05:30.660> be<00:05:30.780> able<00:05:30.840> to 00:05:30.890 --> 00:05:30.900 align:start position:0% to do this I'd like to be able to 00:05:30.900 --> 00:05:33.529 align:start position:0% to do this I'd like to be able to convince<00:05:31.320> you<00:05:31.380> today<00:05:31.560> that<00:05:32.120> in<00:05:33.120> this<00:05:33.300> case 00:05:33.529 --> 00:05:33.539 align:start position:0% convince you today that in this case 00:05:33.539 --> 00:05:36.189 align:start position:0% convince you today that in this case this<00:05:34.500> is<00:05:34.680> something<00:05:34.860> you<00:05:35.100> should<00:05:35.220> be<00:05:35.340> able<00:05:35.580> to 00:05:36.189 --> 00:05:36.199 align:start position:0% this is something you should be able to 00:05:36.199 --> 00:05:39.230 align:start position:0% this is something you should be able to trust<00:05:37.199> and<00:05:37.860> that<00:05:38.100> you<00:05:38.280> can<00:05:38.400> verify<00:05:38.880> lots<00:05:39.180> of 00:05:39.230 --> 00:05:39.240 align:start position:0% trust and that you can verify lots of 00:05:39.240 --> 00:05:41.990 align:start position:0% trust and that you can verify lots of things<00:05:39.419> about<00:05:39.840> it<00:05:40.139> so<00:05:40.740> the<00:05:40.860> idea<00:05:41.160> is<00:05:41.520> that 00:05:41.990 --> 00:05:42.000 align:start position:0% things about it so the idea is that 00:05:42.000 --> 00:05:44.749 align:start position:0% things about it so the idea is that collectively<00:05:42.860> as<00:05:43.860> an<00:05:44.100> ethereum<00:05:44.520> community 00:05:44.749 --> 00:05:44.759 align:start position:0% collectively as an ethereum community 00:05:44.759 --> 00:05:46.430 align:start position:0% collectively as an ethereum community and<00:05:45.300> hopefully<00:05:45.600> including<00:05:46.020> many<00:05:46.199> of<00:05:46.380> those 00:05:46.430 --> 00:05:46.440 align:start position:0% and hopefully including many of those 00:05:46.440 --> 00:05:48.409 align:start position:0% and hopefully including many of those outside<00:05:46.680> of<00:05:47.039> our<00:05:47.160> community<00:05:47.400> we're<00:05:48.180> going<00:05:48.300> to 00:05:48.409 --> 00:05:48.419 align:start position:0% outside of our community we're going to 00:05:48.419 --> 00:05:49.909 align:start position:0% outside of our community we're going to summon<00:05:48.720> a<00:05:49.020> secret 00:05:49.909 --> 00:05:49.919 align:start position:0% summon a secret 00:05:49.919 --> 00:05:52.490 align:start position:0% summon a secret there's<00:05:50.400> not<00:05:50.639> a<00:05:50.759> single<00:05:51.060> person<00:05:51.500> entity 00:05:52.490 --> 00:05:52.500 align:start position:0% there's not a single person entity 00:05:52.500 --> 00:05:54.290 align:start position:0% there's not a single person entity doesn't<00:05:53.160> matter<00:05:53.340> what<00:05:53.580> scale<00:05:53.820> that<00:05:54.060> will<00:05:54.180> be 00:05:54.290 --> 00:05:54.300 align:start position:0% doesn't matter what scale that will be 00:05:54.300 --> 00:05:56.689 align:start position:0% doesn't matter what scale that will be able<00:05:54.479> to<00:05:54.600> know<00:05:55.020> what<00:05:55.199> the<00:05:55.380> secret<00:05:55.500> is 00:05:56.689 --> 00:05:56.699 align:start position:0% able to know what the secret is 00:05:56.699 --> 00:05:58.909 align:start position:0% able to know what the secret is but<00:05:57.300> together<00:05:57.539> we<00:05:57.900> will<00:05:58.080> have<00:05:58.199> generated<00:05:58.560> this 00:05:58.909 --> 00:05:58.919 align:start position:0% but together we will have generated this 00:05:58.919 --> 00:06:02.510 align:start position:0% but together we will have generated this it<00:05:59.400> runs<00:05:59.880> on<00:06:00.539> a<00:06:01.440> so-called<00:06:01.979> one<00:06:02.100> of<00:06:02.280> Interest 00:06:02.510 --> 00:06:02.520 align:start position:0% it runs on a so-called one of Interest 00:06:02.520 --> 00:06:03.770 align:start position:0% it runs on a so-called one of Interest assumption 00:06:03.770 --> 00:06:03.780 align:start position:0% assumption 00:06:03.780 --> 00:06:06.770 align:start position:0% assumption the<00:06:04.259> idea<00:06:04.560> here<00:06:04.800> is<00:06:05.100> that<00:06:05.400> we<00:06:05.699> need<00:06:05.880> one<00:06:06.539> person 00:06:06.770 --> 00:06:06.780 align:start position:0% the idea here is that we need one person 00:06:06.780 --> 00:06:09.469 align:start position:0% the idea here is that we need one person not<00:06:07.259> to<00:06:07.440> have<00:06:07.620> actively<00:06:07.979> been<00:06:08.100> malicious<00:06:08.639> it's 00:06:09.469 --> 00:06:09.479 align:start position:0% not to have actively been malicious it's 00:06:09.479 --> 00:06:11.210 align:start position:0% not to have actively been malicious it's not<00:06:09.720> that<00:06:10.020> we<00:06:10.320> need<00:06:10.440> one<00:06:10.620> person<00:06:10.800> to<00:06:10.979> be<00:06:11.100> good 00:06:11.210 --> 00:06:11.220 align:start position:0% not that we need one person to be good 00:06:11.220 --> 00:06:13.370 align:start position:0% not that we need one person to be good it's<00:06:11.400> we<00:06:11.639> need<00:06:11.759> one<00:06:12.300> person<00:06:12.539> not<00:06:12.900> to<00:06:13.080> be<00:06:13.139> bad 00:06:13.370 --> 00:06:13.380 align:start position:0% it's we need one person not to be bad 00:06:13.380 --> 00:06:16.010 align:start position:0% it's we need one person not to be bad and<00:06:14.039> to<00:06:14.220> actively<00:06:14.639> like<00:06:14.940> pull<00:06:15.300> apart<00:06:15.600> the<00:06:15.840> code 00:06:16.010 --> 00:06:16.020 align:start position:0% and to actively like pull apart the code 00:06:16.020 --> 00:06:17.450 align:start position:0% and to actively like pull apart the code and<00:06:16.320> try<00:06:16.440> to<00:06:16.560> figure<00:06:16.680> out<00:06:16.860> how<00:06:17.160> they<00:06:17.280> could 00:06:17.450 --> 00:06:17.460 align:start position:0% and try to figure out how they could 00:06:17.460 --> 00:06:19.370 align:start position:0% and try to figure out how they could corrupt<00:06:17.880> this<00:06:18.000> and<00:06:18.479> that<00:06:18.900> kind<00:06:19.020> of<00:06:19.080> thing<00:06:19.199> we 00:06:19.370 --> 00:06:19.380 align:start position:0% corrupt this and that kind of thing we 00:06:19.380 --> 00:06:20.749 align:start position:0% corrupt this and that kind of thing we just<00:06:19.500> need<00:06:19.620> one<00:06:19.860> person<00:06:20.039> not<00:06:20.340> to<00:06:20.460> have<00:06:20.580> done 00:06:20.749 --> 00:06:20.759 align:start position:0% just need one person not to have done 00:06:20.759 --> 00:06:21.950 align:start position:0% just need one person not to have done that 00:06:21.950 --> 00:06:21.960 align:start position:0% that 00:06:21.960 --> 00:06:23.029 align:start position:0% that um 00:06:23.029 --> 00:06:23.039 align:start position:0% um 00:06:23.039 --> 00:06:27.050 align:start position:0% um so<00:06:23.759> what<00:06:24.419> is<00:06:24.600> this<00:06:24.780> what<00:06:25.319> does<00:06:25.440> this<00:06:25.620> look<00:06:25.800> like 00:06:27.050 --> 00:06:27.060 align:start position:0% so what is this what does this look like 00:06:27.060 --> 00:06:29.570 align:start position:0% so what is this what does this look like um the<00:06:27.840> ceremony<00:06:28.259> is<00:06:29.039> going<00:06:29.160> to<00:06:29.280> be<00:06:29.340> written 00:06:29.570 --> 00:06:29.580 align:start position:0% um the ceremony is going to be written 00:06:29.580 --> 00:06:31.550 align:start position:0% um the ceremony is going to be written by<00:06:29.699> people<00:06:29.940> people<00:06:30.419> make<00:06:30.780> mistakes<00:06:31.139> so<00:06:31.440> there 00:06:31.550 --> 00:06:31.560 align:start position:0% by people people make mistakes so there 00:06:31.560 --> 00:06:34.129 align:start position:0% by people people make mistakes so there will<00:06:31.680> be<00:06:31.800> bugs<00:06:32.699> this<00:06:33.060> is<00:06:33.180> part<00:06:33.300> of<00:06:33.479> the<00:06:33.539> plan<00:06:33.720> so 00:06:34.129 --> 00:06:34.139 align:start position:0% will be bugs this is part of the plan so 00:06:34.139 --> 00:06:36.770 align:start position:0% will be bugs this is part of the plan so we<00:06:34.380> have<00:06:34.819> multiple<00:06:35.819> implementations<00:06:36.419> that 00:06:36.770 --> 00:06:36.780 align:start position:0% we have multiple implementations that 00:06:36.780 --> 00:06:38.150 align:start position:0% we have multiple implementations that people<00:06:36.900> can<00:06:37.139> use<00:06:37.319> you<00:06:37.620> can<00:06:37.740> write<00:06:37.860> your<00:06:38.039> own 00:06:38.150 --> 00:06:38.160 align:start position:0% people can use you can write your own 00:06:38.160 --> 00:06:40.430 align:start position:0% people can use you can write your own implementation<00:06:38.759> the<00:06:39.120> idea<00:06:39.419> being<00:06:39.600> that<00:06:39.960> even 00:06:40.430 --> 00:06:40.440 align:start position:0% implementation the idea being that even 00:06:40.440 --> 00:06:43.010 align:start position:0% implementation the idea being that even if<00:06:40.680> there<00:06:40.860> is<00:06:41.039> a<00:06:41.460> bug<00:06:41.639> in<00:06:42.600> one<00:06:42.840> of<00:06:42.900> the 00:06:43.010 --> 00:06:43.020 align:start position:0% if there is a bug in one of the 00:06:43.020 --> 00:06:45.710 align:start position:0% if there is a bug in one of the implementations<00:06:44.120> there<00:06:45.120> are<00:06:45.240> still<00:06:45.360> a<00:06:45.600> lot<00:06:45.660> of 00:06:45.710 --> 00:06:45.720 align:start position:0% implementations there are still a lot of 00:06:45.720 --> 00:06:47.749 align:start position:0% implementations there are still a lot of a<00:06:46.259> lot<00:06:46.440> of<00:06:46.560> contributions<00:06:47.220> that<00:06:47.460> people<00:06:47.639> have 00:06:47.749 --> 00:06:47.759 align:start position:0% a lot of contributions that people have 00:06:47.759 --> 00:06:49.309 align:start position:0% a lot of contributions that people have made<00:06:47.880> by<00:06:48.060> the<00:06:48.300> other<00:06:48.419> implementations<00:06:48.960> that 00:06:49.309 --> 00:06:49.319 align:start position:0% made by the other implementations that 00:06:49.319 --> 00:06:51.170 align:start position:0% made by the other implementations that keep<00:06:49.440> us<00:06:49.620> safe<00:06:49.860> there<00:06:50.340> will<00:06:50.460> be<00:06:50.580> malicious 00:06:51.170 --> 00:06:51.180 align:start position:0% keep us safe there will be malicious 00:06:51.180 --> 00:06:53.150 align:start position:0% keep us safe there will be malicious people<00:06:51.419> in<00:06:52.319> the<00:06:52.440> blockchain<00:06:52.680> setting<00:06:53.100> it's 00:06:53.150 --> 00:06:53.160 align:start position:0% people in the blockchain setting it's 00:06:53.160 --> 00:06:55.029 align:start position:0% people in the blockchain setting it's very<00:06:53.400> adversarial 00:06:55.029 --> 00:06:55.039 align:start position:0% very adversarial 00:06:55.039 --> 00:06:57.170 align:start position:0% very adversarial theoretically<00:06:56.039> if<00:06:56.280> you<00:06:56.400> could<00:06:56.520> collect<00:06:56.880> all 00:06:57.170 --> 00:06:57.180 align:start position:0% theoretically if you could collect all 00:06:57.180 --> 00:06:59.029 align:start position:0% theoretically if you could collect all of<00:06:57.300> these<00:06:57.600> secrets<00:06:58.080> that<00:06:58.199> people<00:06:58.380> contributed 00:06:59.029 --> 00:06:59.039 align:start position:0% of these secrets that people contributed 00:06:59.039 --> 00:07:00.290 align:start position:0% of these secrets that people contributed it<00:06:59.220> would<00:06:59.400> be<00:06:59.520> worth<00:06:59.639> a<00:06:59.819> lot<00:06:59.880> of<00:07:00.000> money<00:07:00.120> because 00:07:00.290 --> 00:07:00.300 align:start position:0% it would be worth a lot of money because 00:07:00.300 --> 00:07:02.210 align:start position:0% it would be worth a lot of money because you<00:07:00.479> could<00:07:00.539> do<00:07:00.660> a<00:07:00.780> lot<00:07:00.840> of<00:07:00.960> bad<00:07:01.080> things<00:07:01.259> so<00:07:01.680> in 00:07:02.210 --> 00:07:02.220 align:start position:0% you could do a lot of bad things so in 00:07:02.220 --> 00:07:03.409 align:start position:0% you could do a lot of bad things so in some<00:07:02.280> sense<00:07:02.460> there's<00:07:02.699> some<00:07:02.880> value<00:07:03.000> behind 00:07:03.409 --> 00:07:03.419 align:start position:0% some sense there's some value behind 00:07:03.419 --> 00:07:05.450 align:start position:0% some sense there's some value behind this<00:07:03.660> not<00:07:04.380> really<00:07:04.620> because<00:07:04.919> you<00:07:05.160> really<00:07:05.280> need 00:07:05.450 --> 00:07:05.460 align:start position:0% this not really because you really need 00:07:05.460 --> 00:07:07.370 align:start position:0% this not really because you really need to<00:07:05.580> get<00:07:05.699> all<00:07:05.819> of<00:07:06.000> them<00:07:06.120> having<00:07:06.539> one<00:07:06.960> short<00:07:07.199> is 00:07:07.370 --> 00:07:07.380 align:start position:0% to get all of them having one short is 00:07:07.380 --> 00:07:09.110 align:start position:0% to get all of them having one short is not<00:07:07.560> enough<00:07:07.680> but<00:07:08.100> there<00:07:08.460> will<00:07:08.639> be<00:07:08.759> some<00:07:08.940> people 00:07:09.110 --> 00:07:09.120 align:start position:0% not enough but there will be some people 00:07:09.120 --> 00:07:11.029 align:start position:0% not enough but there will be some people who<00:07:09.419> will<00:07:09.539> try<00:07:09.780> to<00:07:09.900> be<00:07:10.020> malicious<00:07:10.440> and<00:07:10.860> try 00:07:11.029 --> 00:07:11.039 align:start position:0% who will try to be malicious and try 00:07:11.039 --> 00:07:13.189 align:start position:0% who will try to be malicious and try spreadfad<00:07:11.639> so<00:07:12.240> we<00:07:12.360> lose<00:07:12.539> a<00:07:12.720> few<00:07:12.780> more<00:07:12.900> of<00:07:13.020> these 00:07:13.189 --> 00:07:13.199 align:start position:0% spreadfad so we lose a few more of these 00:07:13.199 --> 00:07:15.350 align:start position:0% spreadfad so we lose a few more of these contributions<00:07:13.680> but<00:07:14.400> the<00:07:14.580> idea<00:07:14.819> is<00:07:15.000> is<00:07:15.180> that 00:07:15.350 --> 00:07:15.360 align:start position:0% contributions but the idea is is that 00:07:15.360 --> 00:07:16.850 align:start position:0% contributions but the idea is is that there'll<00:07:15.600> still<00:07:15.660> be<00:07:15.840> many<00:07:16.199> contributions 00:07:16.850 --> 00:07:16.860 align:start position:0% there'll still be many contributions 00:07:16.860 --> 00:07:19.490 align:start position:0% there'll still be many contributions which<00:07:17.759> won't<00:07:18.060> have<00:07:18.360> this<00:07:18.539> problem<00:07:18.780> and<00:07:19.319> by 00:07:19.490 --> 00:07:19.500 align:start position:0% which won't have this problem and by 00:07:19.500 --> 00:07:21.830 align:start position:0% which won't have this problem and by many<00:07:19.680> contributions<00:07:20.280> I<00:07:20.639> really<00:07:20.759> mean<00:07:21.060> a<00:07:21.660> great 00:07:21.830 --> 00:07:21.840 align:start position:0% many contributions I really mean a great 00:07:21.840 --> 00:07:23.990 align:start position:0% many contributions I really mean a great scale<00:07:22.199> like<00:07:22.560> that's<00:07:22.740> not<00:07:22.979> even<00:07:23.099> close 00:07:23.990 --> 00:07:24.000 align:start position:0% scale like that's not even close 00:07:24.000 --> 00:07:26.870 align:start position:0% scale like that's not even close not<00:07:24.599> even<00:07:24.800> this<00:07:25.800> is<00:07:25.919> my<00:07:26.220> sort<00:07:26.400> of<00:07:26.460> lower<00:07:26.639> bound 00:07:26.870 --> 00:07:26.880 align:start position:0% not even this is my sort of lower bound 00:07:26.880 --> 00:07:28.309 align:start position:0% not even this is my sort of lower bound goal<00:07:27.300> for<00:07:27.419> the<00:07:27.539> number<00:07:27.660> of<00:07:27.780> people<00:07:27.960> I'd<00:07:28.199> like 00:07:28.309 --> 00:07:28.319 align:start position:0% goal for the number of people I'd like 00:07:28.319 --> 00:07:32.570 align:start position:0% goal for the number of people I'd like to<00:07:28.440> contribute<00:07:28.800> this<00:07:29.039> is<00:07:29.539> 8192<00:07:30.539> contributions 00:07:32.570 --> 00:07:32.580 align:start position:0% to contribute this is 8192 contributions 00:07:32.580 --> 00:07:33.170 align:start position:0% to contribute this is 8192 contributions um 00:07:33.170 --> 00:07:33.180 align:start position:0% um 00:07:33.180 --> 00:07:35.749 align:start position:0% um this<00:07:33.840> graph<00:07:34.199> is<00:07:34.919> something<00:07:35.220> I<00:07:35.520> personally 00:07:35.749 --> 00:07:35.759 align:start position:0% this graph is something I personally 00:07:35.759 --> 00:07:37.790 align:start position:0% this graph is something I personally care<00:07:36.000> about<00:07:36.180> it's<00:07:36.479> a<00:07:36.720> bit<00:07:36.780> silly<00:07:37.199> but 00:07:37.790 --> 00:07:37.800 align:start position:0% care about it's a bit silly but 00:07:37.800 --> 00:07:39.830 align:start position:0% care about it's a bit silly but hopefully<00:07:38.520> this<00:07:38.880> ceremony<00:07:39.360> we're<00:07:39.599> running 00:07:39.830 --> 00:07:39.840 align:start position:0% hopefully this ceremony we're running 00:07:39.840 --> 00:07:42.350 align:start position:0% hopefully this ceremony we're running will<00:07:40.139> be<00:07:40.319> the<00:07:40.500> first<00:07:40.620> ceremony<00:07:41.099> ever<00:07:41.460> where 00:07:42.350 --> 00:07:42.360 align:start position:0% will be the first ceremony ever where 00:07:42.360 --> 00:07:44.450 align:start position:0% will be the first ceremony ever where they<00:07:42.720> are<00:07:43.020> more<00:07:43.319> participants<00:07:43.860> than<00:07:44.160> we<00:07:44.340> have 00:07:44.450 --> 00:07:44.460 align:start position:0% they are more participants than we have 00:07:44.460 --> 00:07:47.089 align:start position:0% they are more participants than we have powers<00:07:45.020> so<00:07:46.020> normally<00:07:46.319> you<00:07:46.560> have<00:07:46.680> these<00:07:46.979> very 00:07:47.089 --> 00:07:47.099 align:start position:0% powers so normally you have these very 00:07:47.099 --> 00:07:48.710 align:start position:0% powers so normally you have these very big<00:07:47.280> hard<00:07:47.460> to<00:07:47.699> run<00:07:47.819> ceremonies<00:07:48.300> and<00:07:48.419> one<00:07:48.599> or 00:07:48.710 --> 00:07:48.720 align:start position:0% big hard to run ceremonies and one or 00:07:48.720 --> 00:07:51.710 align:start position:0% big hard to run ceremonies and one or two<00:07:48.840> people<00:07:49.020> contributing<00:07:49.620> here<00:07:50.280> we<00:07:50.639> have<00:07:50.880> a 00:07:51.710 --> 00:07:51.720 align:start position:0% two people contributing here we have a 00:07:51.720 --> 00:07:53.629 align:start position:0% two people contributing here we have a ceremony<00:07:52.199> with<00:07:52.500> that's<00:07:52.860> very<00:07:53.039> easy<00:07:53.220> to<00:07:53.460> run 00:07:53.629 --> 00:07:53.639 align:start position:0% ceremony with that's very easy to run 00:07:53.639 --> 00:07:55.370 align:start position:0% ceremony with that's very easy to run and<00:07:54.240> we<00:07:54.479> have 00:07:55.370 --> 00:07:55.380 align:start position:0% and we have 00:07:55.380 --> 00:07:57.110 align:start position:0% and we have ideally<00:07:56.039> tens<00:07:56.400> of<00:07:56.520> thousands<00:07:56.819> of<00:07:56.940> people 00:07:57.110 --> 00:07:57.120 align:start position:0% ideally tens of thousands of people 00:07:57.120 --> 00:07:59.629 align:start position:0% ideally tens of thousands of people getting<00:07:57.479> involved<00:07:58.280> ensuring<00:07:59.280> the<00:07:59.460> security 00:07:59.629 --> 00:07:59.639 align:start position:0% getting involved ensuring the security 00:07:59.639 --> 00:08:02.210 align:start position:0% getting involved ensuring the security of<00:08:00.060> of<00:08:00.300> all<00:08:00.539> of<00:08:00.660> this<00:08:00.840> making<00:08:01.440> sure<00:08:01.680> that<00:08:01.860> those 00:08:02.210 --> 00:08:02.220 align:start position:0% of of all of this making sure that those 00:08:02.220 --> 00:08:04.610 align:start position:0% of of all of this making sure that those candles<00:08:02.580> stay<00:08:02.759> lit<00:08:03.120> so<00:08:03.900> a<00:08:04.139> lot<00:08:04.259> of<00:08:04.380> this<00:08:04.440> came 00:08:04.610 --> 00:08:04.620 align:start position:0% candles stay lit so a lot of this came 00:08:04.620 --> 00:08:07.010 align:start position:0% candles stay lit so a lot of this came to<00:08:04.800> the<00:08:04.919> design<00:08:05.039> decisions<00:08:05.460> of<00:08:05.639> the<00:08:05.759> ceremony 00:08:07.010 --> 00:08:07.020 align:start position:0% to the design decisions of the ceremony 00:08:07.020 --> 00:08:08.689 align:start position:0% to the design decisions of the ceremony um<00:08:07.080> it's<00:08:07.680> designed<00:08:07.979> to<00:08:08.039> be<00:08:08.160> quick<00:08:08.340> and<00:08:08.520> easy 00:08:08.689 --> 00:08:08.699 align:start position:0% um it's designed to be quick and easy 00:08:08.699 --> 00:08:10.129 align:start position:0% um it's designed to be quick and easy for 00:08:10.129 --> 00:08:10.139 align:start position:0% for 00:08:10.139 --> 00:08:13.070 align:start position:0% for everyone<00:08:10.800> here<00:08:11.280> at<00:08:11.759> no<00:08:12.360> matter<00:08:12.720> what<00:08:12.900> your 00:08:13.070 --> 00:08:13.080 align:start position:0% everyone here at no matter what your 00:08:13.080 --> 00:08:14.170 align:start position:0% everyone here at no matter what your level<00:08:13.259> of 00:08:14.170 --> 00:08:14.180 align:start position:0% level of 00:08:14.180 --> 00:08:17.270 align:start position:0% level of technical<00:08:15.180> skills<00:08:15.660> there<00:08:16.380> is<00:08:16.620> an<00:08:16.860> easy<00:08:16.919> option 00:08:17.270 --> 00:08:17.280 align:start position:0% technical skills there is an easy option 00:08:17.280 --> 00:08:19.369 align:start position:0% technical skills there is an easy option which<00:08:17.520> is<00:08:17.639> there's<00:08:17.940> a<00:08:18.300> website<00:08:18.780> you<00:08:18.900> can<00:08:19.080> go<00:08:19.199> to 00:08:19.369 --> 00:08:19.379 align:start position:0% which is there's a website you can go to 00:08:19.379 --> 00:08:22.189 align:start position:0% which is there's a website you can go to click<00:08:20.039> contribute<00:08:20.520> and<00:08:21.300> it'll<00:08:22.020> walk<00:08:22.080> you 00:08:22.189 --> 00:08:22.199 align:start position:0% click contribute and it'll walk you 00:08:22.199 --> 00:08:23.570 align:start position:0% click contribute and it'll walk you through<00:08:22.379> it<00:08:22.500> in<00:08:22.620> about<00:08:22.740> five<00:08:22.979> minutes<00:08:23.160> very 00:08:23.570 --> 00:08:23.580 align:start position:0% through it in about five minutes very 00:08:23.580 --> 00:08:25.490 align:start position:0% through it in about five minutes very easy<00:08:23.759> to<00:08:23.940> run<00:08:24.060> on<00:08:24.180> your<00:08:24.300> computer<00:08:24.479> if<00:08:25.319> you<00:08:25.440> want 00:08:25.490 --> 00:08:25.500 align:start position:0% easy to run on your computer if you want 00:08:25.500 --> 00:08:27.309 align:start position:0% easy to run on your computer if you want to<00:08:25.620> write<00:08:25.740> your<00:08:25.919> own<00:08:26.039> implementation 00:08:27.309 --> 00:08:27.319 align:start position:0% to write your own implementation 00:08:27.319 --> 00:08:30.230 align:start position:0% to write your own implementation the<00:08:28.319> specifications<00:08:28.860> have<00:08:29.340> been<00:08:29.520> kept<00:08:29.879> to<00:08:30.060> an 00:08:30.230 --> 00:08:30.240 align:start position:0% the specifications have been kept to an 00:08:30.240 --> 00:08:31.850 align:start position:0% the specifications have been kept to an absolute<00:08:30.539> minimum<00:08:30.900> even<00:08:31.259> at<00:08:31.440> the<00:08:31.620> cost<00:08:31.680> of 00:08:31.850 --> 00:08:31.860 align:start position:0% absolute minimum even at the cost of 00:08:31.860 --> 00:08:33.290 align:start position:0% absolute minimum even at the cost of some<00:08:32.039> efficiency<00:08:32.399> of<00:08:32.580> the<00:08:32.700> setup<00:08:32.940> just<00:08:33.180> to 00:08:33.290 --> 00:08:33.300 align:start position:0% some efficiency of the setup just to 00:08:33.300 --> 00:08:36.469 align:start position:0% some efficiency of the setup just to ensure<00:08:33.599> that<00:08:33.899> it's<00:08:34.260> very<00:08:34.440> easy<00:08:34.620> to<00:08:34.860> do 00:08:36.469 --> 00:08:36.479 align:start position:0% ensure that it's very easy to do 00:08:36.479 --> 00:08:38.149 align:start position:0% ensure that it's very easy to do um<00:08:36.539> and<00:08:36.899> then<00:08:37.080> in<00:08:37.500> other<00:08:37.560> ways<00:08:37.860> we've<00:08:38.039> just 00:08:38.149 --> 00:08:38.159 align:start position:0% um and then in other ways we've just 00:08:38.159 --> 00:08:40.190 align:start position:0% um and then in other ways we've just tried<00:08:38.339> to<00:08:38.459> keep<00:08:38.640> the<00:08:38.940> ceremony<00:08:39.419> as<00:08:39.599> as<00:08:39.839> minimal 00:08:40.190 --> 00:08:40.200 align:start position:0% tried to keep the ceremony as as minimal 00:08:40.200 --> 00:08:41.389 align:start position:0% tried to keep the ceremony as as minimal as<00:08:40.380> possible 00:08:41.389 --> 00:08:41.399 align:start position:0% as possible 00:08:41.399 --> 00:08:43.190 align:start position:0% as possible there's<00:08:41.760> also<00:08:42.060> the<00:08:42.120> idea<00:08:42.360> of<00:08:42.479> the<00:08:42.599> ceremony<00:08:43.020> is 00:08:43.190 --> 00:08:43.200 align:start position:0% there's also the idea of the ceremony is 00:08:43.200 --> 00:08:44.510 align:start position:0% there's also the idea of the ceremony is updatable<00:08:43.680> which<00:08:43.919> will<00:08:44.039> mean<00:08:44.159> something<00:08:44.339> to 00:08:44.510 --> 00:08:44.520 align:start position:0% updatable which will mean something to 00:08:44.520 --> 00:08:48.110 align:start position:0% updatable which will mean something to the<00:08:44.760> cryptographers<00:08:45.360> but<00:08:46.200> for<00:08:46.380> us<00:08:46.560> is<00:08:46.860> that<00:08:47.220> in 00:08:48.110 --> 00:08:48.120 align:start position:0% the cryptographers but for us is that in 00:08:48.120 --> 00:08:51.350 align:start position:0% the cryptographers but for us is that in uh<00:08:48.899> 10<00:08:49.140> years<00:08:49.320> or<00:08:49.560> so<00:08:49.740> when<00:08:50.459> our<00:08:50.940> communities 00:08:51.350 --> 00:08:51.360 align:start position:0% uh 10 years or so when our communities 00:08:51.360 --> 00:08:53.389 align:start position:0% uh 10 years or so when our communities progress<00:08:51.839> when<00:08:52.140> hopefully<00:08:52.560> I'm<00:08:53.160> less 00:08:53.389 --> 00:08:53.399 align:start position:0% progress when hopefully I'm less 00:08:53.399 --> 00:08:55.310 align:start position:0% progress when hopefully I'm less relevant<00:08:53.820> to<00:08:53.940> the<00:08:54.060> protocol<00:08:54.360> because<00:08:54.839> we're 00:08:55.310 --> 00:08:55.320 align:start position:0% relevant to the protocol because we're 00:08:55.320 --> 00:08:58.670 align:start position:0% relevant to the protocol because we're less<00:08:55.620> capturable<00:08:56.220> and<00:08:56.940> we've<00:08:57.240> grown<00:08:57.480> further 00:08:58.670 --> 00:08:58.680 align:start position:0% less capturable and we've grown further 00:08:58.680 --> 00:09:00.650 align:start position:0% less capturable and we've grown further um<00:08:58.740> and<00:08:58.920> we've<00:08:59.339> adopted<00:09:00.060> many<00:09:00.240> more<00:09:00.480> people 00:09:00.650 --> 00:09:00.660 align:start position:0% um and we've adopted many more people 00:09:00.660 --> 00:09:02.810 align:start position:0% um and we've adopted many more people that<00:09:01.080> we<00:09:01.200> can<00:09:01.440> add<00:09:01.680> to<00:09:01.980> the<00:09:02.100> previous<00:09:02.279> ceremony 00:09:02.810 --> 00:09:02.820 align:start position:0% that we can add to the previous ceremony 00:09:02.820 --> 00:09:04.370 align:start position:0% that we can add to the previous ceremony build<00:09:03.000> upon<00:09:03.420> it 00:09:04.370 --> 00:09:04.380 align:start position:0% build upon it 00:09:04.380 --> 00:09:06.829 align:start position:0% build upon it um<00:09:04.440> to<00:09:04.740> update<00:09:05.040> it<00:09:05.279> such<00:09:06.000> that<00:09:06.300> we'll<00:09:06.600> have 00:09:06.829 --> 00:09:06.839 align:start position:0% um to update it such that we'll have 00:09:06.839 --> 00:09:08.750 align:start position:0% um to update it such that we'll have even<00:09:07.019> more<00:09:07.320> people<00:09:07.620> uh<00:09:08.339> keeping<00:09:08.640> those 00:09:08.750 --> 00:09:08.760 align:start position:0% even more people uh keeping those 00:09:08.760 --> 00:09:11.090 align:start position:0% even more people uh keeping those candles<00:09:09.060> alive<00:09:09.300> so<00:09:09.720> how<00:09:09.839> does<00:09:10.019> it<00:09:10.140> work<00:09:10.380> that 00:09:11.090 --> 00:09:11.100 align:start position:0% candles alive so how does it work that 00:09:11.100 --> 00:09:14.389 align:start position:0% candles alive so how does it work that sounds<00:09:11.279> like<00:09:11.459> some<00:09:11.880> big<00:09:12.540> scary<00:09:12.779> math<00:09:13.140> but<00:09:13.980> in 00:09:14.389 --> 00:09:14.399 align:start position:0% sounds like some big scary math but in 00:09:14.399 --> 00:09:15.650 align:start position:0% sounds like some big scary math but in reality<00:09:14.700> it's<00:09:14.940> not 00:09:15.650 --> 00:09:15.660 align:start position:0% reality it's not 00:09:15.660 --> 00:09:19.190 align:start position:0% reality it's not so<00:09:16.200> the<00:09:16.320> idea<00:09:16.620> is<00:09:17.040> that<00:09:17.660> each<00:09:18.660> individual 00:09:19.190 --> 00:09:19.200 align:start position:0% so the idea is that each individual 00:09:19.200 --> 00:09:21.650 align:start position:0% so the idea is that each individual generates<00:09:19.740> a<00:09:19.920> secret<00:09:20.100> and<00:09:20.820> they<00:09:21.060> mix<00:09:21.300> in<00:09:21.480> their 00:09:21.650 --> 00:09:21.660 align:start position:0% generates a secret and they mix in their 00:09:21.660 --> 00:09:23.690 align:start position:0% generates a secret and they mix in their secrets<00:09:22.080> with<00:09:22.200> everyone<00:09:22.380> else<00:09:22.680> so<00:09:23.399> in<00:09:23.519> this 00:09:23.690 --> 00:09:23.700 align:start position:0% secrets with everyone else so in this 00:09:23.700 --> 00:09:25.610 align:start position:0% secrets with everyone else so in this example<00:09:24.000> the<00:09:24.360> first<00:09:24.480> person<00:09:24.720> mixes<00:09:25.320> in<00:09:25.440> the 00:09:25.610 --> 00:09:25.620 align:start position:0% example the first person mixes in the 00:09:25.620 --> 00:09:27.230 align:start position:0% example the first person mixes in the number<00:09:25.740> three<00:09:25.980> into<00:09:26.399> like<00:09:26.700> the<00:09:26.880> overall 00:09:27.230 --> 00:09:27.240 align:start position:0% number three into like the overall 00:09:27.240 --> 00:09:28.250 align:start position:0% number three into like the overall Secret 00:09:28.250 --> 00:09:28.260 align:start position:0% Secret 00:09:28.260 --> 00:09:30.410 align:start position:0% Secret the<00:09:28.740> second<00:09:28.860> person<00:09:29.220> adds<00:09:30.000> the<00:09:30.060> number<00:09:30.240> five 00:09:30.410 --> 00:09:30.420 align:start position:0% the second person adds the number five 00:09:30.420 --> 00:09:32.509 align:start position:0% the second person adds the number five to<00:09:30.720> the<00:09:30.839> secret<00:09:31.019> and<00:09:31.680> then<00:09:31.800> the<00:09:31.980> third<00:09:32.160> person 00:09:32.509 --> 00:09:32.519 align:start position:0% to the secret and then the third person 00:09:32.519 --> 00:09:36.050 align:start position:0% to the secret and then the third person multiplies<00:09:33.120> the<00:09:33.360> number<00:09:33.540> two<00:09:34.200> in<00:09:34.500> so<00:09:34.920> the<00:09:35.820> idea 00:09:36.050 --> 00:09:36.060 align:start position:0% multiplies the number two in so the idea 00:09:36.060 --> 00:09:38.750 align:start position:0% multiplies the number two in so the idea is<00:09:36.300> that<00:09:36.660> this<00:09:37.080> this<00:09:37.380> brown<00:09:37.680> colored<00:09:38.160> 30<00:09:38.339> is 00:09:38.750 --> 00:09:38.760 align:start position:0% is that this this brown colored 30 is 00:09:38.760 --> 00:09:41.230 align:start position:0% is that this this brown colored 30 is the<00:09:39.120> mix<00:09:39.360> of<00:09:39.540> all<00:09:39.720> the<00:09:39.899> colors<00:09:40.200> slash<00:09:40.500> all<00:09:40.860> the 00:09:41.230 --> 00:09:41.240 align:start position:0% the mix of all the colors slash all the 00:09:41.240 --> 00:09:43.310 align:start position:0% the mix of all the colors slash all the secrets<00:09:42.240> from<00:09:42.420> the<00:09:42.600> various<00:09:42.839> people<00:09:43.019> that 00:09:43.310 --> 00:09:43.320 align:start position:0% secrets from the various people that 00:09:43.320 --> 00:09:44.449 align:start position:0% secrets from the various people that came<00:09:43.500> before 00:09:44.449 --> 00:09:44.459 align:start position:0% came before 00:09:44.459 --> 00:09:48.470 align:start position:0% came before and<00:09:45.360> that<00:09:46.019> it<00:09:46.800> represents<00:09:47.339> all<00:09:47.640> these<00:09:47.940> these 00:09:48.470 --> 00:09:48.480 align:start position:0% and that it represents all these these 00:09:48.480 --> 00:09:50.269 align:start position:0% and that it represents all these these these<00:09:48.779> secrets<00:09:49.080> and<00:09:49.260> these<00:09:49.560> people<00:09:49.680> generated 00:09:50.269 --> 00:09:50.279 align:start position:0% these secrets and these people generated 00:09:50.279 --> 00:09:52.190 align:start position:0% these secrets and these people generated these<00:09:50.580> numbers<00:09:50.700> randomly<00:09:51.240> but<00:09:51.899> there's<00:09:52.019> a 00:09:52.190 --> 00:09:52.200 align:start position:0% these numbers randomly but there's a 00:09:52.200 --> 00:09:53.990 align:start position:0% these numbers randomly but there's a problem<00:09:52.380> with<00:09:52.620> this<00:09:52.800> and<00:09:53.100> that's<00:09:53.279> that<00:09:53.519> as<00:09:53.760> it 00:09:53.990 --> 00:09:54.000 align:start position:0% problem with this and that's that as it 00:09:54.000 --> 00:09:56.030 align:start position:0% problem with this and that's that as it stands<00:09:54.300> here<00:09:54.480> anyone<00:09:55.440> can<00:09:55.560> read<00:09:55.680> this<00:09:55.860> right 00:09:56.030 --> 00:09:56.040 align:start position:0% stands here anyone can read this right 00:09:56.040 --> 00:09:57.350 align:start position:0% stands here anyone can read this right it's<00:09:56.160> just<00:09:56.279> a<00:09:56.459> number<00:09:56.580> 30<00:09:56.760> that's<00:09:57.000> not<00:09:57.180> a<00:09:57.300> great 00:09:57.350 --> 00:09:57.360 align:start position:0% it's just a number 30 that's not a great 00:09:57.360 --> 00:09:59.509 align:start position:0% it's just a number 30 that's not a great secret<00:09:57.600> so<00:09:58.260> you<00:09:58.440> need<00:09:58.500> to<00:09:58.680> encrypt<00:09:58.980> these<00:09:59.220> and 00:09:59.509 --> 00:09:59.519 align:start position:0% secret so you need to encrypt these and 00:09:59.519 --> 00:10:02.150 align:start position:0% secret so you need to encrypt these and we<00:09:59.640> encrypt<00:10:00.000> these<00:10:00.300> by 00:10:02.150 --> 00:10:02.160 align:start position:0% we encrypt these by 00:10:02.160 --> 00:10:03.710 align:start position:0% we encrypt these by um<00:10:02.220> quote<00:10:02.820> unquote<00:10:03.120> hiding<00:10:03.420> them<00:10:03.540> the 00:10:03.710 --> 00:10:03.720 align:start position:0% um quote unquote hiding them the 00:10:03.720 --> 00:10:05.389 align:start position:0% um quote unquote hiding them the exponent<00:10:04.019> we<00:10:04.200> turn<00:10:04.320> them<00:10:04.440> into<00:10:04.560> elliptical<00:10:04.980> of 00:10:05.389 --> 00:10:05.399 align:start position:0% exponent we turn them into elliptical of 00:10:05.399 --> 00:10:06.470 align:start position:0% exponent we turn them into elliptical of points 00:10:06.470 --> 00:10:06.480 align:start position:0% points 00:10:06.480 --> 00:10:08.690 align:start position:0% points um<00:10:06.600> this<00:10:07.140> allows<00:10:07.500> us<00:10:07.560> to<00:10:07.800> still<00:10:07.980> perform<00:10:08.220> the 00:10:08.690 --> 00:10:08.700 align:start position:0% um this allows us to still perform the 00:10:08.700 --> 00:10:10.670 align:start position:0% um this allows us to still perform the math<00:10:08.880> that<00:10:09.540> I<00:10:09.720> was<00:10:09.839> saying<00:10:10.080> it<00:10:10.200> is<00:10:10.380> quite 00:10:10.670 --> 00:10:10.680 align:start position:0% math that I was saying it is quite 00:10:10.680 --> 00:10:12.490 align:start position:0% math that I was saying it is quite literally<00:10:11.040> multiplication 00:10:12.490 --> 00:10:12.500 align:start position:0% literally multiplication 00:10:12.500 --> 00:10:16.430 align:start position:0% literally multiplication but<00:10:13.500> it<00:10:13.680> is<00:10:13.800> done<00:10:14.160> in<00:10:15.000> this<00:10:15.240> in<00:10:15.839> this<00:10:16.019> encrypted 00:10:16.430 --> 00:10:16.440 align:start position:0% but it is done in this in this encrypted 00:10:16.440 --> 00:10:18.650 align:start position:0% but it is done in this in this encrypted form<00:10:16.620> so<00:10:17.040> that<00:10:17.279> no<00:10:17.580> one<00:10:17.760> can<00:10:17.940> read<00:10:18.060> the<00:10:18.300> overall 00:10:18.650 --> 00:10:18.660 align:start position:0% form so that no one can read the overall 00:10:18.660 --> 00:10:20.210 align:start position:0% form so that no one can read the overall secret<00:10:18.839> there's<00:10:19.440> one<00:10:19.680> other<00:10:19.800> thing<00:10:20.040> and 00:10:20.210 --> 00:10:20.220 align:start position:0% secret there's one other thing and 00:10:20.220 --> 00:10:21.829 align:start position:0% secret there's one other thing and that's<00:10:20.339> that<00:10:20.519> we<00:10:20.700> have<00:10:20.820> the<00:10:20.940> role<00:10:21.240> of<00:10:21.540> the 00:10:21.829 --> 00:10:21.839 align:start position:0% that's that we have the role of the 00:10:21.839 --> 00:10:22.850 align:start position:0% that's that we have the role of the sequencer 00:10:22.850 --> 00:10:22.860 align:start position:0% sequencer 00:10:22.860 --> 00:10:26.090 align:start position:0% sequencer the<00:10:23.459> sequencer's<00:10:24.180> job<00:10:24.540> is<00:10:25.140> to<00:10:25.440> do<00:10:25.620> two<00:10:25.860> things 00:10:26.090 --> 00:10:26.100 align:start position:0% the sequencer's job is to do two things 00:10:26.100 --> 00:10:28.910 align:start position:0% the sequencer's job is to do two things one<00:10:26.519> is<00:10:26.700> to<00:10:26.880> decide<00:10:27.120> who's<00:10:27.300> going<00:10:27.540> next<00:10:27.920> there 00:10:28.910 --> 00:10:28.920 align:start position:0% one is to decide who's going next there 00:10:28.920 --> 00:10:30.350 align:start position:0% one is to decide who's going next there are<00:10:29.100> thousands<00:10:29.580> of<00:10:29.640> people<00:10:29.820> who<00:10:30.000> want<00:10:30.240> to 00:10:30.350 --> 00:10:30.360 align:start position:0% are thousands of people who want to 00:10:30.360 --> 00:10:32.870 align:start position:0% are thousands of people who want to participate<00:10:30.779> how<00:10:31.019> we<00:10:31.260> decide<00:10:31.620> who's<00:10:31.980> the<00:10:32.760> next 00:10:32.870 --> 00:10:32.880 align:start position:0% participate how we decide who's the next 00:10:32.880 --> 00:10:34.970 align:start position:0% participate how we decide who's the next the<00:10:33.120> next<00:10:33.360> contributor 00:10:34.970 --> 00:10:34.980 align:start position:0% the next contributor 00:10:34.980 --> 00:10:38.210 align:start position:0% the next contributor um<00:10:35.100> and<00:10:35.519> the<00:10:35.700> sequencer<00:10:36.180> basically<00:10:36.680> uh<00:10:37.680> holds 00:10:38.210 --> 00:10:38.220 align:start position:0% um and the sequencer basically uh holds 00:10:38.220 --> 00:10:40.310 align:start position:0% um and the sequencer basically uh holds the<00:10:38.339> files<00:10:38.700> and<00:10:39.000> when<00:10:39.300> there's<00:10:39.540> uh<00:10:40.080> when 00:10:40.310 --> 00:10:40.320 align:start position:0% the files and when there's uh when 00:10:40.320 --> 00:10:42.410 align:start position:0% the files and when there's uh when someone<00:10:40.440> asks<00:10:40.860> for<00:10:40.980> it<00:10:41.160> and<00:10:41.519> it's<00:10:41.880> they're 00:10:42.410 --> 00:10:42.420 align:start position:0% someone asks for it and it's they're 00:10:42.420 --> 00:10:44.329 align:start position:0% someone asks for it and it's they're available<00:10:42.600> they'll<00:10:43.440> pass<00:10:43.560> over<00:10:43.740> the<00:10:43.920> files<00:10:44.220> to 00:10:44.329 --> 00:10:44.339 align:start position:0% available they'll pass over the files to 00:10:44.339 --> 00:10:46.550 align:start position:0% available they'll pass over the files to the<00:10:44.459> next<00:10:44.579> person<00:10:44.760> to<00:10:45.120> contribute<00:10:45.959> the<00:10:46.380> second 00:10:46.550 --> 00:10:46.560 align:start position:0% the next person to contribute the second 00:10:46.560 --> 00:10:48.170 align:start position:0% the next person to contribute the second thing<00:10:46.740> they<00:10:46.920> do<00:10:47.100> is<00:10:47.339> they<00:10:47.519> verify<00:10:47.940> these 00:10:48.170 --> 00:10:48.180 align:start position:0% thing they do is they verify these 00:10:48.180 --> 00:10:50.389 align:start position:0% thing they do is they verify these contributions<00:10:48.660> so 00:10:50.389 --> 00:10:50.399 align:start position:0% contributions so 00:10:50.399 --> 00:10:52.430 align:start position:0% contributions so um<00:10:50.459> we<00:10:50.820> need<00:10:50.940> to<00:10:51.000> be<00:10:51.180> sure<00:10:51.420> that<00:10:51.839> these 00:10:52.430 --> 00:10:52.440 align:start position:0% um we need to be sure that these 00:10:52.440 --> 00:10:54.829 align:start position:0% um we need to be sure that these contributions<00:10:52.980> that<00:10:53.519> people<00:10:54.180> give<00:10:54.420> back<00:10:54.660> to 00:10:54.829 --> 00:10:54.839 align:start position:0% contributions that people give back to 00:10:54.839 --> 00:10:57.410 align:start position:0% contributions that people give back to the<00:10:54.959> sequencer<00:10:55.640> someone<00:10:56.640> hasn't<00:10:57.060> tried<00:10:57.300> to 00:10:57.410 --> 00:10:57.420 align:start position:0% the sequencer someone hasn't tried to 00:10:57.420 --> 00:10:59.329 align:start position:0% the sequencer someone hasn't tried to delete<00:10:57.660> some<00:10:58.019> of<00:10:58.140> the<00:10:58.260> points<00:10:58.560> or<00:10:58.860> try<00:10:59.040> to<00:10:59.220> do 00:10:59.329 --> 00:10:59.339 align:start position:0% delete some of the points or try to do 00:10:59.339 --> 00:11:01.850 align:start position:0% delete some of the points or try to do some<00:10:59.579> weird<00:10:59.820> crazy<00:11:00.060> math<00:11:00.360> that<00:11:00.600> breaks<00:11:00.899> it<00:11:01.079> so 00:11:01.850 --> 00:11:01.860 align:start position:0% some weird crazy math that breaks it so 00:11:01.860 --> 00:11:04.250 align:start position:0% some weird crazy math that breaks it so the<00:11:02.040> sequencer<00:11:02.640> just<00:11:03.060> double<00:11:03.300> checks<00:11:03.779> that 00:11:04.250 --> 00:11:04.260 align:start position:0% the sequencer just double checks that 00:11:04.260 --> 00:11:05.930 align:start position:0% the sequencer just double checks that the<00:11:04.740> files<00:11:04.980> that<00:11:05.160> they're<00:11:05.279> getting<00:11:05.459> back<00:11:05.640> are 00:11:05.930 --> 00:11:05.940 align:start position:0% the files that they're getting back are 00:11:05.940 --> 00:11:08.389 align:start position:0% the files that they're getting back are still<00:11:06.180> valid<00:11:06.540> files<00:11:07.380> so<00:11:07.800> that<00:11:07.980> the<00:11:08.100> ceremony 00:11:08.389 --> 00:11:08.399 align:start position:0% still valid files so that the ceremony 00:11:08.399 --> 00:11:10.550 align:start position:0% still valid files so that the ceremony can<00:11:08.640> keep<00:11:08.820> progressing<00:11:09.300> the<00:11:09.899> sounds<00:11:10.140> like<00:11:10.380> the 00:11:10.550 --> 00:11:10.560 align:start position:0% can keep progressing the sounds like the 00:11:10.560 --> 00:11:12.230 align:start position:0% can keep progressing the sounds like the sequencer<00:11:10.980> has<00:11:11.339> incredible<00:11:11.820> amounts<00:11:12.180> of 00:11:12.230 --> 00:11:12.240 align:start position:0% sequencer has incredible amounts of 00:11:12.240 --> 00:11:15.230 align:start position:0% sequencer has incredible amounts of power<00:11:12.480> this<00:11:13.200> is<00:11:13.320> not<00:11:13.500> true<00:11:13.740> so<00:11:14.519> the<00:11:14.700> sequence's 00:11:15.230 --> 00:11:15.240 align:start position:0% power this is not true so the sequence's 00:11:15.240 --> 00:11:17.870 align:start position:0% power this is not true so the sequence's abilities<00:11:15.600> are<00:11:16.440> basically<00:11:17.339> the<00:11:17.640> only<00:11:17.760> thing 00:11:17.870 --> 00:11:17.880 align:start position:0% abilities are basically the only thing 00:11:17.880 --> 00:11:19.790 align:start position:0% abilities are basically the only thing they<00:11:18.060> can<00:11:18.180> do<00:11:18.300> is<00:11:18.480> censor<00:11:18.959> things 00:11:19.790 --> 00:11:19.800 align:start position:0% they can do is censor things 00:11:19.800 --> 00:11:23.449 align:start position:0% they can do is censor things they<00:11:20.399> could<00:11:20.760> lie<00:11:21.600> and<00:11:22.079> say<00:11:22.260> that<00:11:22.620> the<00:11:23.100> file<00:11:23.220> you 00:11:23.449 --> 00:11:23.459 align:start position:0% they could lie and say that the file you 00:11:23.459 --> 00:11:26.150 align:start position:0% they could lie and say that the file you gave<00:11:23.579> them<00:11:23.700> was<00:11:23.940> corrupt<00:11:24.420> or<00:11:24.720> invalid<00:11:25.380> and 00:11:26.150 --> 00:11:26.160 align:start position:0% gave them was corrupt or invalid and 00:11:26.160 --> 00:11:27.530 align:start position:0% gave them was corrupt or invalid and they<00:11:26.339> could<00:11:26.519> also<00:11:26.700> just<00:11:26.820> not<00:11:26.940> give<00:11:27.120> you<00:11:27.240> a<00:11:27.420> turn 00:11:27.530 --> 00:11:27.540 align:start position:0% they could also just not give you a turn 00:11:27.540 --> 00:11:29.690 align:start position:0% they could also just not give you a turn so<00:11:28.320> you<00:11:28.560> would<00:11:28.680> log<00:11:28.860> in<00:11:28.980> with<00:11:29.160> your<00:11:29.279> ethereum 00:11:29.690 --> 00:11:29.700 align:start position:0% so you would log in with your ethereum 00:11:29.700 --> 00:11:31.069 align:start position:0% so you would log in with your ethereum account<00:11:29.820> and<00:11:30.060> then<00:11:30.180> they'd<00:11:30.360> be<00:11:30.480> like<00:11:30.660> oh<00:11:30.899> no 00:11:31.069 --> 00:11:31.079 align:start position:0% account and then they'd be like oh no 00:11:31.079 --> 00:11:33.889 align:start position:0% account and then they'd be like oh no sorry<00:11:31.320> your<00:11:31.620> therm<00:11:31.980> account's<00:11:32.279> not<00:11:32.399> valid 00:11:33.889 --> 00:11:33.899 align:start position:0% sorry your therm account's not valid 00:11:33.899 --> 00:11:36.350 align:start position:0% sorry your therm account's not valid um<00:11:34.380> or<00:11:35.100> we've<00:11:35.640> got<00:11:35.760> certain<00:11:35.880> validity 00:11:36.350 --> 00:11:36.360 align:start position:0% um or we've got certain validity 00:11:36.360 --> 00:11:39.470 align:start position:0% um or we've got certain validity conditions<00:11:36.899> it<00:11:37.200> doesn't<00:11:37.440> meet<00:11:37.740> those<00:11:38.360> in<00:11:39.360> this 00:11:39.470 --> 00:11:39.480 align:start position:0% conditions it doesn't meet those in this 00:11:39.480 --> 00:11:43.069 align:start position:0% conditions it doesn't meet those in this case<00:11:39.740> we<00:11:40.740> have<00:11:40.920> signatures<00:11:41.640> which<00:11:42.180> hold<00:11:42.779> the 00:11:43.069 --> 00:11:43.079 align:start position:0% case we have signatures which hold the 00:11:43.079 --> 00:11:45.350 align:start position:0% case we have signatures which hold the sequencer<00:11:43.500> accountable<00:11:43.980> for<00:11:44.279> this<00:11:44.459> role<00:11:44.820> so 00:11:45.350 --> 00:11:45.360 align:start position:0% sequencer accountable for this role so 00:11:45.360 --> 00:11:46.610 align:start position:0% sequencer accountable for this role so should<00:11:45.540> they<00:11:45.720> try<00:11:45.899> to<00:11:46.019> do<00:11:46.140> these<00:11:46.320> kinds<00:11:46.560> of 00:11:46.610 --> 00:11:46.620 align:start position:0% should they try to do these kinds of 00:11:46.620 --> 00:11:49.130 align:start position:0% should they try to do these kinds of things<00:11:47.000> we'll<00:11:48.000> have<00:11:48.180> a<00:11:48.300> proof<00:11:48.540> that<00:11:48.720> we<00:11:48.959> can 00:11:49.130 --> 00:11:49.140 align:start position:0% things we'll have a proof that we can 00:11:49.140 --> 00:11:51.769 align:start position:0% things we'll have a proof that we can publicize<00:11:49.760> to<00:11:50.760> show<00:11:51.240> that<00:11:51.480> this<00:11:51.600> was 00:11:51.769 --> 00:11:51.779 align:start position:0% publicize to show that this was 00:11:51.779 --> 00:11:53.630 align:start position:0% publicize to show that this was happening<00:11:52.140> and<00:11:52.680> we<00:11:52.920> can<00:11:53.040> decide<00:11:53.339> how<00:11:53.519> to 00:11:53.630 --> 00:11:53.640 align:start position:0% happening and we can decide how to 00:11:53.640 --> 00:11:55.490 align:start position:0% happening and we can decide how to progress<00:11:53.940> from<00:11:54.120> then 00:11:55.490 --> 00:11:55.500 align:start position:0% progress from then 00:11:55.500 --> 00:11:56.150 align:start position:0% progress from then um 00:11:56.150 --> 00:11:56.160 align:start position:0% um 00:11:56.160 --> 00:11:57.889 align:start position:0% um so<00:11:56.640> realistically<00:11:57.120> the<00:11:57.300> sequencer<00:11:57.720> doesn't 00:11:57.889 --> 00:11:57.899 align:start position:0% so realistically the sequencer doesn't 00:11:57.899 --> 00:12:00.410 align:start position:0% so realistically the sequencer doesn't have<00:11:58.140> any<00:11:58.440> weird<00:11:58.620> and<00:11:58.860> funny<00:11:58.980> Powers 00:12:00.410 --> 00:12:00.420 align:start position:0% have any weird and funny Powers 00:12:00.420 --> 00:12:03.590 align:start position:0% have any weird and funny Powers um<00:12:00.480> it<00:12:00.660> is<00:12:00.779> just<00:12:00.959> a<00:12:01.200> server<00:12:01.440> that<00:12:01.860> runs<00:12:02.480> a<00:12:03.480> very 00:12:03.590 --> 00:12:03.600 align:start position:0% um it is just a server that runs a very 00:12:03.600 --> 00:12:05.389 align:start position:0% um it is just a server that runs a very simple<00:12:03.779> algorithm<00:12:04.320> just<00:12:04.680> verifies<00:12:05.160> things 00:12:05.389 --> 00:12:05.399 align:start position:0% simple algorithm just verifies things 00:12:05.399 --> 00:12:08.090 align:start position:0% simple algorithm just verifies things and<00:12:05.579> passes<00:12:05.940> them<00:12:06.060> on 00:12:08.090 --> 00:12:08.100 align:start position:0% and passes them on 00:12:08.100 --> 00:12:11.030 align:start position:0% and passes them on in<00:12:08.519> the<00:12:08.700> end<00:12:08.880> it'll<00:12:09.360> be<00:12:09.540> up<00:12:09.779> to<00:12:10.079> the<00:12:10.920> community 00:12:11.030 --> 00:12:11.040 align:start position:0% in the end it'll be up to the community 00:12:11.040 --> 00:12:13.730 align:start position:0% in the end it'll be up to the community to<00:12:11.579> verify<00:12:12.120> that<00:12:12.899> the<00:12:13.019> sequencer<00:12:13.380> did<00:12:13.560> their 00:12:13.730 --> 00:12:13.740 align:start position:0% to verify that the sequencer did their 00:12:13.740 --> 00:12:15.470 align:start position:0% to verify that the sequencer did their job<00:12:13.860> correctly<00:12:14.279> so<00:12:14.760> there's<00:12:14.940> a<00:12:15.120> transcript 00:12:15.470 --> 00:12:15.480 align:start position:0% job correctly so there's a transcript 00:12:15.480 --> 00:12:16.850 align:start position:0% job correctly so there's a transcript file<00:12:15.720> that<00:12:15.959> should<00:12:16.079> be<00:12:16.200> split<00:12:16.440> out<00:12:16.560> of<00:12:16.740> the 00:12:16.850 --> 00:12:16.860 align:start position:0% file that should be split out of the 00:12:16.860 --> 00:12:18.470 align:start position:0% file that should be split out of the ceremony<00:12:17.160> at<00:12:17.339> the<00:12:17.459> end<00:12:17.579> which<00:12:17.820> contains<00:12:18.300> the 00:12:18.470 --> 00:12:18.480 align:start position:0% ceremony at the end which contains the 00:12:18.480 --> 00:12:21.230 align:start position:0% ceremony at the end which contains the secret<00:12:18.660> this<00:12:19.320> final<00:12:19.560> secret<00:12:19.880> and<00:12:20.880> we<00:12:21.060> can 00:12:21.230 --> 00:12:21.240 align:start position:0% secret this final secret and we can 00:12:21.240 --> 00:12:22.910 align:start position:0% secret this final secret and we can verify<00:12:21.660> that<00:12:21.959> what<00:12:22.140> the<00:12:22.260> sequencer<00:12:22.620> did<00:12:22.740> along 00:12:22.910 --> 00:12:22.920 align:start position:0% verify that what the sequencer did along 00:12:22.920 --> 00:12:26.810 align:start position:0% verify that what the sequencer did along the<00:12:23.160> way<00:12:23.220> was<00:12:24.180> correct<00:12:25.140> and<00:12:25.320> valid<00:12:25.740> I<00:12:26.519> kind<00:12:26.700> of 00:12:26.810 --> 00:12:26.820 align:start position:0% the way was correct and valid I kind of 00:12:26.820 --> 00:12:28.370 align:start position:0% the way was correct and valid I kind of lied<00:12:27.480> a<00:12:27.600> little<00:12:27.600> bit<00:12:27.779> earlier<00:12:28.019> when<00:12:28.140> I<00:12:28.260> said 00:12:28.370 --> 00:12:28.380 align:start position:0% lied a little bit earlier when I said 00:12:28.380 --> 00:12:29.630 align:start position:0% lied a little bit earlier when I said that's<00:12:28.500> how<00:12:28.680> it<00:12:28.800> works<00:12:29.040> is<00:12:29.160> a<00:12:29.339> little<00:12:29.399> bit<00:12:29.519> more 00:12:29.630 --> 00:12:29.640 align:start position:0% that's how it works is a little bit more 00:12:29.640 --> 00:12:31.190 align:start position:0% that's how it works is a little bit more complexity<00:12:30.120> so<00:12:30.300> how<00:12:30.420> does<00:12:30.600> it<00:12:30.720> really<00:12:30.959> work 00:12:31.190 --> 00:12:31.200 align:start position:0% complexity so how does it really work 00:12:31.200 --> 00:12:32.569 align:start position:0% complexity so how does it really work here<00:12:31.440> you<00:12:31.860> might<00:12:32.040> have<00:12:32.160> heard<00:12:32.279> of<00:12:32.399> something 00:12:32.569 --> 00:12:32.579 align:start position:0% here you might have heard of something 00:12:32.579 --> 00:12:34.190 align:start position:0% here you might have heard of something called<00:12:32.820> the<00:12:33.000> powers<00:12:33.120> of<00:12:33.420> Tau 00:12:34.190 --> 00:12:34.200 align:start position:0% called the powers of Tau 00:12:34.200 --> 00:12:35.990 align:start position:0% called the powers of Tau these<00:12:34.800> are<00:12:34.860> the<00:12:34.980> powers<00:12:35.160> so<00:12:35.640> it's<00:12:35.760> not 00:12:35.990 --> 00:12:36.000 align:start position:0% these are the powers so it's not 00:12:36.000 --> 00:12:38.449 align:start position:0% these are the powers so it's not actually<00:12:36.300> a<00:12:36.779> single<00:12:37.019> secret<00:12:37.200> we<00:12:38.160> store 00:12:38.449 --> 00:12:38.459 align:start position:0% actually a single secret we store 00:12:38.459 --> 00:12:40.009 align:start position:0% actually a single secret we store multiple<00:12:38.880> copies<00:12:39.180> of<00:12:39.360> the<00:12:39.420> secret<00:12:39.540> we<00:12:39.839> stole 00:12:40.009 --> 00:12:40.019 align:start position:0% multiple copies of the secret we stole 00:12:40.019 --> 00:12:41.750 align:start position:0% multiple copies of the secret we stole the<00:12:40.200> secret<00:12:40.380> the<00:12:40.800> Secret's<00:12:41.160> a<00:12:41.279> number<00:12:41.399> by<00:12:41.640> the 00:12:41.750 --> 00:12:41.760 align:start position:0% the secret the Secret's a number by the 00:12:41.760 --> 00:12:43.610 align:start position:0% the secret the Secret's a number by the way<00:12:41.820> we<00:12:42.180> saw<00:12:42.300> the<00:12:42.480> secret<00:12:42.660> the<00:12:42.959> secret<00:12:43.079> squared 00:12:43.610 --> 00:12:43.620 align:start position:0% way we saw the secret the secret squared 00:12:43.620 --> 00:12:46.069 align:start position:0% way we saw the secret the secret squared cubed<00:12:44.519> etc<00:12:45.000> etc<00:12:45.120> all<00:12:45.480> the<00:12:45.600> way<00:12:45.660> up<00:12:45.779> to<00:12:45.959> the 00:12:46.069 --> 00:12:46.079 align:start position:0% cubed etc etc all the way up to the 00:12:46.079 --> 00:12:47.389 align:start position:0% cubed etc etc all the way up to the secret<00:12:46.200> to<00:12:46.380> the<00:12:46.500> power<00:12:46.560> of<00:12:46.740> 2<00:12:46.860> to<00:12:46.980> the<00:12:47.100> twelve 00:12:47.389 --> 00:12:47.399 align:start position:0% secret to the power of 2 to the twelve 00:12:47.399 --> 00:12:50.690 align:start position:0% secret to the power of 2 to the twelve or<00:12:48.120> as<00:12:48.420> these<00:12:48.540> encrypted<00:12:49.019> points<00:12:49.380> then<00:12:50.100> when 00:12:50.690 --> 00:12:50.700 align:start position:0% or as these encrypted points then when 00:12:50.700 --> 00:12:52.069 align:start position:0% or as these encrypted points then when it's<00:12:50.880> your<00:12:51.060> turn<00:12:51.180> to<00:12:51.360> contribute<00:12:51.779> the 00:12:52.069 --> 00:12:52.079 align:start position:0% it's your turn to contribute the 00:12:52.079 --> 00:12:55.790 align:start position:0% it's your turn to contribute the sequencer<00:12:52.560> will<00:12:52.920> pass<00:12:53.399> you<00:12:53.820> this<00:12:54.300> this<00:12:54.540> file 00:12:55.790 --> 00:12:55.800 align:start position:0% sequencer will pass you this this file 00:12:55.800 --> 00:12:59.090 align:start position:0% sequencer will pass you this this file and<00:12:56.720> you<00:12:57.720> will<00:12:57.959> come<00:12:58.139> up<00:12:58.260> with<00:12:58.380> a<00:12:58.560> secret<00:12:58.680> with 00:12:59.090 --> 00:12:59.100 align:start position:0% and you will come up with a secret with 00:12:59.100 --> 00:13:00.290 align:start position:0% and you will come up with a secret with obviously<00:12:59.519> with<00:12:59.700> the<00:12:59.820> hope<00:12:59.940> of<00:13:00.060> your<00:13:00.180> computer 00:13:00.290 --> 00:13:00.300 align:start position:0% obviously with the hope of your computer 00:13:00.300 --> 00:13:03.350 align:start position:0% obviously with the hope of your computer right<00:13:00.740> and<00:13:01.740> you<00:13:01.920> do<00:13:02.160> some<00:13:02.399> some<00:13:02.700> computations 00:13:03.350 --> 00:13:03.360 align:start position:0% right and you do some some computations 00:13:03.360 --> 00:13:05.629 align:start position:0% right and you do some some computations so<00:13:03.839> you<00:13:04.019> also<00:13:04.260> calculate<00:13:04.740> your<00:13:05.040> own<00:13:05.279> personal 00:13:05.629 --> 00:13:05.639 align:start position:0% so you also calculate your own personal 00:13:05.639 --> 00:13:08.210 align:start position:0% so you also calculate your own personal local<00:13:06.180> secret<00:13:06.540> or<00:13:06.839> entropy<00:13:07.320> you<00:13:07.860> calculate 00:13:08.210 --> 00:13:08.220 align:start position:0% local secret or entropy you calculate 00:13:08.220 --> 00:13:10.490 align:start position:0% local secret or entropy you calculate the<00:13:08.399> powers<00:13:08.639> of<00:13:08.880> this<00:13:09.060> and<00:13:09.839> you<00:13:10.019> do<00:13:10.139> basic 00:13:10.490 --> 00:13:10.500 align:start position:0% the powers of this and you do basic 00:13:10.500 --> 00:13:13.810 align:start position:0% the powers of this and you do basic multiplication<00:13:11.339> so<00:13:11.880> you<00:13:12.000> multiply<00:13:12.420> the<00:13:12.899> the 00:13:13.810 --> 00:13:13.820 align:start position:0% multiplication so you multiply the the 00:13:13.820 --> 00:13:17.569 align:start position:0% multiplication so you multiply the the corresponding<00:13:14.820> power<00:13:15.120> with<00:13:15.600> the<00:13:16.500> uh<00:13:16.980> the 00:13:17.569 --> 00:13:17.579 align:start position:0% corresponding power with the uh the 00:13:17.579 --> 00:13:19.009 align:start position:0% corresponding power with the uh the corresponding<00:13:17.940> elliptical<00:13:18.300> Point<00:13:18.600> given<00:13:18.899> to 00:13:19.009 --> 00:13:19.019 align:start position:0% corresponding elliptical Point given to 00:13:19.019 --> 00:13:20.930 align:start position:0% corresponding elliptical Point given to you<00:13:19.079> from<00:13:19.260> the<00:13:19.380> sequencer 00:13:20.930 --> 00:13:20.940 align:start position:0% you from the sequencer 00:13:20.940 --> 00:13:22.610 align:start position:0% you from the sequencer and 00:13:22.610 --> 00:13:22.620 align:start position:0% and 00:13:22.620 --> 00:13:26.930 align:start position:0% and by<00:13:23.459> the<00:13:23.639> linear<00:13:24.600> properties<00:13:25.019> of 00:13:26.930 --> 00:13:26.940 align:start position:0% by the linear properties of 00:13:26.940 --> 00:13:29.509 align:start position:0% by the linear properties of elliptic<00:13:27.660> curve<00:13:27.980> multiplication<00:13:28.980> we<00:13:29.279> end<00:13:29.399> up 00:13:29.509 --> 00:13:29.519 align:start position:0% elliptic curve multiplication we end up 00:13:29.519 --> 00:13:31.069 align:start position:0% elliptic curve multiplication we end up with<00:13:29.700> this<00:13:29.880> final<00:13:30.060> thing<00:13:30.360> which<00:13:30.600> is<00:13:30.720> basically 00:13:31.069 --> 00:13:31.079 align:start position:0% with this final thing which is basically 00:13:31.079 --> 00:13:33.170 align:start position:0% with this final thing which is basically showing<00:13:31.560> that<00:13:32.100> now<00:13:32.220> your<00:13:32.519> secret<00:13:32.700> has<00:13:33.060> been 00:13:33.170 --> 00:13:33.180 align:start position:0% showing that now your secret has been 00:13:33.180 --> 00:13:35.509 align:start position:0% showing that now your secret has been incorporated<00:13:33.839> into<00:13:34.260> this<00:13:34.620> overall<00:13:35.279> secret 00:13:35.509 --> 00:13:35.519 align:start position:0% incorporated into this overall secret 00:13:35.519 --> 00:13:37.310 align:start position:0% incorporated into this overall secret and<00:13:36.060> you<00:13:36.180> can<00:13:36.240> now<00:13:36.420> pass<00:13:36.600> this<00:13:36.779> on<00:13:36.959> to<00:13:37.079> the<00:13:37.200> next 00:13:37.310 --> 00:13:37.320 align:start position:0% and you can now pass this on to the next 00:13:37.320 --> 00:13:40.370 align:start position:0% and you can now pass this on to the next person<00:13:37.560> that<00:13:38.279> you<00:13:38.399> then<00:13:38.579> take<00:13:38.880> this<00:13:39.480> powers 00:13:40.370 --> 00:13:40.380 align:start position:0% person that you then take this powers 00:13:40.380 --> 00:13:42.530 align:start position:0% person that you then take this powers and<00:13:40.680> hand<00:13:40.860> it<00:13:40.980> back<00:13:41.100> to<00:13:41.220> the<00:13:41.339> sequencer<00:13:41.880> who 00:13:42.530 --> 00:13:42.540 align:start position:0% and hand it back to the sequencer who 00:13:42.540 --> 00:13:45.170 align:start position:0% and hand it back to the sequencer who verifies<00:13:43.019> that<00:13:43.620> what<00:13:44.220> you<00:13:44.339> did<00:13:44.579> was<00:13:44.820> correct 00:13:45.170 --> 00:13:45.180 align:start position:0% verifies that what you did was correct 00:13:45.180 --> 00:13:47.110 align:start position:0% verifies that what you did was correct what<00:13:45.540> you<00:13:45.720> did<00:13:45.839> was<00:13:46.019> valid 00:13:47.110 --> 00:13:47.120 align:start position:0% what you did was valid 00:13:47.120 --> 00:13:49.730 align:start position:0% what you did was valid and<00:13:48.120> that<00:13:48.240> you<00:13:48.420> haven't<00:13:48.540> tried<00:13:48.899> to<00:13:49.019> to<00:13:49.620> to 00:13:49.730 --> 00:13:49.740 align:start position:0% and that you haven't tried to to to 00:13:49.740 --> 00:13:51.889 align:start position:0% and that you haven't tried to to to cheat<00:13:50.160> the<00:13:50.399> system<00:13:50.579> so<00:13:51.360> when<00:13:51.600> can<00:13:51.779> you 00:13:51.889 --> 00:13:51.899 align:start position:0% cheat the system so when can you 00:13:51.899 --> 00:13:53.509 align:start position:0% cheat the system so when can you participate 00:13:53.509 --> 00:13:53.519 align:start position:0% participate 00:13:53.519 --> 00:13:54.170 align:start position:0% participate um 00:13:54.170 --> 00:13:54.180 align:start position:0% um 00:13:54.180 --> 00:13:56.810 align:start position:0% um the<00:13:54.779> we<00:13:55.019> should<00:13:55.200> be<00:13:55.320> launching<00:13:56.279> a<00:13:56.459> test<00:13:56.579> net 00:13:56.810 --> 00:13:56.820 align:start position:0% the we should be launching a test net 00:13:56.820 --> 00:13:58.670 align:start position:0% the we should be launching a test net very<00:13:57.360> shortly<00:13:57.660> ideally<00:13:58.200> in<00:13:58.380> the<00:13:58.500> next<00:13:58.560> few 00:13:58.670 --> 00:13:58.680 align:start position:0% very shortly ideally in the next few 00:13:58.680 --> 00:14:00.170 align:start position:0% very shortly ideally in the next few days 00:14:00.170 --> 00:14:00.180 align:start position:0% days 00:14:00.180 --> 00:14:03.230 align:start position:0% days um<00:14:00.240> they<00:14:01.200> were<00:14:01.860> fairly<00:14:02.160> certain<00:14:02.339> that<00:14:02.880> most<00:14:03.120> of 00:14:03.230 --> 00:14:03.240 align:start position:0% um they were fairly certain that most of 00:14:03.240 --> 00:14:06.350 align:start position:0% um they were fairly certain that most of the<00:14:03.360> cryptography<00:14:03.959> is<00:14:04.500> uh<00:14:05.399> unlocked<00:14:06.060> we've 00:14:06.350 --> 00:14:06.360 align:start position:0% the cryptography is uh unlocked we've 00:14:06.360 --> 00:14:07.850 align:start position:0% the cryptography is uh unlocked we've that<00:14:06.600> that's<00:14:06.839> pretty<00:14:07.019> reasonable<00:14:07.380> we've 00:14:07.850 --> 00:14:07.860 align:start position:0% that that's pretty reasonable we've 00:14:07.860 --> 00:14:09.650 align:start position:0% that that's pretty reasonable we've already<00:14:07.980> had<00:14:08.100> a<00:14:08.220> first<00:14:08.339> audit<00:14:08.639> on<00:14:08.820> that<00:14:08.940> but 00:14:09.650 --> 00:14:09.660 align:start position:0% already had a first audit on that but 00:14:09.660 --> 00:14:11.090 align:start position:0% already had a first audit on that but there<00:14:09.839> are<00:14:09.899> a<00:14:09.959> bunch<00:14:10.079> of<00:14:10.139> ux<00:14:10.440> bugs<00:14:10.860> that<00:14:10.980> we 00:14:11.090 --> 00:14:11.100 align:start position:0% there are a bunch of ux bugs that we 00:14:11.100 --> 00:14:12.829 align:start position:0% there are a bunch of ux bugs that we need<00:14:11.220> to<00:14:11.339> sort<00:14:11.519> out<00:14:11.760> and<00:14:12.120> we're<00:14:12.240> handling<00:14:12.600> that 00:14:12.829 --> 00:14:12.839 align:start position:0% need to sort out and we're handling that 00:14:12.839 --> 00:14:14.750 align:start position:0% need to sort out and we're handling that and<00:14:13.440> that's<00:14:13.560> a<00:14:13.680> part<00:14:13.800> of<00:14:13.920> the<00:14:14.040> test<00:14:14.160> net<00:14:14.399> is<00:14:14.639> to 00:14:14.750 --> 00:14:14.760 align:start position:0% and that's a part of the test net is to 00:14:14.760 --> 00:14:17.990 align:start position:0% and that's a part of the test net is to get<00:14:14.880> people<00:14:15.060> to<00:14:15.480> participate<00:14:16.260> and<00:14:16.760> help<00:14:17.760> make 00:14:17.990 --> 00:14:18.000 align:start position:0% get people to participate and help make 00:14:18.000 --> 00:14:21.730 align:start position:0% get people to participate and help make this<00:14:18.240> the<00:14:18.600> the<00:14:19.380> best<00:14:19.800> process<00:14:20.700> it<00:14:20.940> could<00:14:21.060> be 00:14:21.730 --> 00:14:21.740 align:start position:0% this the the best process it could be 00:14:21.740 --> 00:14:25.190 align:start position:0% this the the best process it could be we've<00:14:22.740> got<00:14:22.860> a<00:14:22.980> final<00:14:23.100> audit<00:14:23.519> launching<00:14:24.200> early 00:14:25.190 --> 00:14:25.200 align:start position:0% we've got a final audit launching early 00:14:25.200 --> 00:14:27.170 align:start position:0% we've got a final audit launching early November<00:14:25.800> which<00:14:26.519> will<00:14:26.820> hopefully<00:14:27.120> be 00:14:27.170 --> 00:14:27.180 align:start position:0% November which will hopefully be 00:14:27.180 --> 00:14:30.470 align:start position:0% November which will hopefully be concluding<00:14:27.980> after<00:14:28.980> that<00:14:29.399> should<00:14:30.300> anything 00:14:30.470 --> 00:14:30.480 align:start position:0% concluding after that should anything 00:14:30.480 --> 00:14:32.870 align:start position:0% concluding after that should anything arise<00:14:30.899> in<00:14:31.019> that<00:14:31.139> audit<00:14:31.440> we'll<00:14:31.860> we'll<00:14:32.220> squash 00:14:32.870 --> 00:14:32.880 align:start position:0% arise in that audit we'll we'll squash 00:14:32.880 --> 00:14:34.730 align:start position:0% arise in that audit we'll we'll squash those<00:14:33.120> bugs<00:14:33.480> review<00:14:34.019> that<00:14:34.380> and<00:14:34.620> then 00:14:34.730 --> 00:14:34.740 align:start position:0% those bugs review that and then 00:14:34.740 --> 00:14:36.410 align:start position:0% those bugs review that and then hopefully<00:14:35.040> launch<00:14:35.399> the<00:14:35.639> ceremony<00:14:36.000> by<00:14:36.240> the<00:14:36.300> end 00:14:36.410 --> 00:14:36.420 align:start position:0% hopefully launch the ceremony by the end 00:14:36.420 --> 00:14:38.629 align:start position:0% hopefully launch the ceremony by the end of<00:14:36.540> November 00:14:38.629 --> 00:14:38.639 align:start position:0% of November 00:14:38.639 --> 00:14:39.790 align:start position:0% of November um 00:14:39.790 --> 00:14:39.800 align:start position:0% um 00:14:39.800 --> 00:14:42.530 align:start position:0% um eip4844<00:14:40.800> I<00:14:41.459> don't<00:14:41.760> show<00:14:42.000> lots<00:14:42.300> of<00:14:42.300> people<00:14:42.420> have 00:14:42.530 --> 00:14:42.540 align:start position:0% eip4844 I don't show lots of people have 00:14:42.540 --> 00:14:43.850 align:start position:0% eip4844 I don't show lots of people have heard<00:14:42.660> discussions<00:14:43.079> as<00:14:43.260> to<00:14:43.440> when<00:14:43.680> that's 00:14:43.850 --> 00:14:43.860 align:start position:0% heard discussions as to when that's 00:14:43.860 --> 00:14:45.230 align:start position:0% heard discussions as to when that's going<00:14:44.040> to<00:14:44.160> be 00:14:45.230 --> 00:14:45.240 align:start position:0% going to be 00:14:45.240 --> 00:14:47.210 align:start position:0% going to be um<00:14:45.300> ultimately<00:14:45.720> it's<00:14:46.079> up<00:14:46.260> to<00:14:46.380> the<00:14:46.500> client<00:14:46.740> devs 00:14:47.210 --> 00:14:47.220 align:start position:0% um ultimately it's up to the client devs 00:14:47.220 --> 00:14:50.509 align:start position:0% um ultimately it's up to the client devs and<00:14:47.519> the<00:14:47.699> community<00:14:47.940> demand<00:14:48.860> for<00:14:49.860> when<00:14:50.279> this 00:14:50.509 --> 00:14:50.519 align:start position:0% and the community demand for when this 00:14:50.519 --> 00:14:52.910 align:start position:0% and the community demand for when this gets<00:14:50.880> shipped<00:14:51.120> but<00:14:52.079> as<00:14:52.440> this<00:14:52.620> is<00:14:52.740> a 00:14:52.910 --> 00:14:52.920 align:start position:0% gets shipped but as this is a 00:14:52.920 --> 00:14:54.290 align:start position:0% gets shipped but as this is a prerequisite<00:14:53.459> we'll<00:14:53.699> basically<00:14:54.000> be<00:14:54.120> running 00:14:54.290 --> 00:14:54.300 align:start position:0% prerequisite we'll basically be running 00:14:54.300 --> 00:14:57.009 align:start position:0% prerequisite we'll basically be running the<00:14:54.600> ceremony<00:14:55.019> up<00:14:55.380> to<00:14:55.560> until<00:14:55.800> that<00:14:56.160> point 00:14:57.009 --> 00:14:57.019 align:start position:0% the ceremony up to until that point 00:14:57.019 --> 00:15:01.250 align:start position:0% the ceremony up to until that point which<00:14:58.019> is<00:14:58.260> a<00:14:59.040> minimum<00:14:59.279> of<00:14:59.459> two<00:14:59.699> months<00:15:00.260> but 00:15:01.250 --> 00:15:01.260 align:start position:0% which is a minimum of two months but 00:15:01.260 --> 00:15:03.350 align:start position:0% which is a minimum of two months but obviously<00:15:01.560> we'll<00:15:01.800> run<00:15:02.040> longer<00:15:02.519> should<00:15:02.820> it 00:15:03.350 --> 00:15:03.360 align:start position:0% obviously we'll run longer should it 00:15:03.360 --> 00:15:06.410 align:start position:0% obviously we'll run longer should it take<00:15:03.480> longer<00:15:03.779> to<00:15:03.959> get<00:15:04.139> to<00:15:04.639> eip4844<00:15:05.639> there<00:15:06.240> are 00:15:06.410 --> 00:15:06.420 align:start position:0% take longer to get to eip4844 there are 00:15:06.420 --> 00:15:07.670 align:start position:0% take longer to get to eip4844 there are grants 00:15:07.670 --> 00:15:07.680 align:start position:0% grants 00:15:07.680 --> 00:15:10.129 align:start position:0% grants um<00:15:07.740> I'm<00:15:07.980> sure<00:15:08.160> many<00:15:08.820> of<00:15:08.940> you<00:15:09.060> have<00:15:09.240> heard<00:15:09.959> never 00:15:10.129 --> 00:15:10.139 align:start position:0% um I'm sure many of you have heard never 00:15:10.139 --> 00:15:11.449 align:start position:0% um I'm sure many of you have heard never to<00:15:10.320> roll<00:15:10.500> your<00:15:10.680> own<00:15:10.740> crypto<00:15:11.040> I'm<00:15:11.220> trying<00:15:11.399> to 00:15:11.449 --> 00:15:11.459 align:start position:0% to roll your own crypto I'm trying to 00:15:11.459 --> 00:15:13.910 align:start position:0% to roll your own crypto I'm trying to tell<00:15:11.579> you<00:15:11.699> you<00:15:11.760> should<00:15:11.880> roll<00:15:12.060> your<00:15:12.300> own<00:15:12.420> crypto 00:15:13.910 --> 00:15:13.920 align:start position:0% tell you you should roll your own crypto 00:15:13.920 --> 00:15:17.569 align:start position:0% tell you you should roll your own crypto um<00:15:14.279> all<00:15:14.880> that's<00:15:15.060> needed<00:15:15.480> to<00:15:16.260> uh<00:15:16.980> to<00:15:17.339> implement 00:15:17.569 --> 00:15:17.579 align:start position:0% um all that's needed to uh to implement 00:15:17.579 --> 00:15:20.689 align:start position:0% um all that's needed to uh to implement this<00:15:17.880> like<00:15:18.240> from<00:15:18.600> scratch<00:15:19.019> is<00:15:19.920> to<00:15:20.160> do<00:15:20.279> elliptic 00:15:20.689 --> 00:15:20.699 align:start position:0% this like from scratch is to do elliptic 00:15:20.699 --> 00:15:22.790 align:start position:0% this like from scratch is to do elliptic curve<00:15:20.940> multiplication 00:15:22.790 --> 00:15:22.800 align:start position:0% curve multiplication 00:15:22.800 --> 00:15:24.769 align:start position:0% curve multiplication um<00:15:23.339> maybe<00:15:23.760> some<00:15:23.940> of<00:15:24.060> you<00:15:24.180> have<00:15:24.300> heard<00:15:24.480> of<00:15:24.660> this 00:15:24.769 --> 00:15:24.779 align:start position:0% um maybe some of you have heard of this 00:15:24.779 --> 00:15:26.629 align:start position:0% um maybe some of you have heard of this or<00:15:25.199> like<00:15:25.440> had<00:15:25.680> it<00:15:25.860> explained<00:15:26.220> to<00:15:26.279> you<00:15:26.399> on<00:15:26.519> a 00:15:26.629 --> 00:15:26.639 align:start position:0% or like had it explained to you on a 00:15:26.639 --> 00:15:28.490 align:start position:0% or like had it explained to you on a whiteboard<00:15:26.940> it<00:15:27.480> really<00:15:27.600> is<00:15:27.779> a<00:15:28.019> like 00:15:28.490 --> 00:15:28.500 align:start position:0% whiteboard it really is a like 00:15:28.500 --> 00:15:30.530 align:start position:0% whiteboard it really is a like relatively<00:15:29.040> simple<00:15:29.220> thing<00:15:29.459> to<00:15:29.699> do<00:15:29.820> you<00:15:30.420> have 00:15:30.530 --> 00:15:30.540 align:start position:0% relatively simple thing to do you have 00:15:30.540 --> 00:15:32.389 align:start position:0% relatively simple thing to do you have quite<00:15:30.779> a<00:15:30.899> lot<00:15:31.019> of<00:15:31.199> time<00:15:31.500> to<00:15:31.980> do<00:15:32.220> this 00:15:32.389 --> 00:15:32.399 align:start position:0% quite a lot of time to do this 00:15:32.399 --> 00:15:33.949 align:start position:0% quite a lot of time to do this participation<00:15:32.940> so<00:15:33.240> if<00:15:33.420> you<00:15:33.540> are<00:15:33.660> going<00:15:33.839> to 00:15:33.949 --> 00:15:33.959 align:start position:0% participation so if you are going to 00:15:33.959 --> 00:15:36.290 align:start position:0% participation so if you are going to write<00:15:34.079> your<00:15:34.260> own<00:15:34.380> implementation<00:15:35.000> uh<00:15:36.000> you 00:15:36.290 --> 00:15:36.300 align:start position:0% write your own implementation uh you 00:15:36.300 --> 00:15:37.129 align:start position:0% write your own implementation uh you don't<00:15:36.360> it<00:15:36.480> doesn't<00:15:36.660> need<00:15:36.839> to<00:15:36.899> be<00:15:37.019> super 00:15:37.129 --> 00:15:37.139 align:start position:0% don't it doesn't need to be super 00:15:37.139 --> 00:15:39.230 align:start position:0% don't it doesn't need to be super optimized<00:15:37.800> you<00:15:38.040> don't<00:15:38.220> need<00:15:38.399> to<00:15:38.519> read<00:15:38.940> all<00:15:39.120> the 00:15:39.230 --> 00:15:39.240 align:start position:0% optimized you don't need to read all the 00:15:39.240 --> 00:15:40.910 align:start position:0% optimized you don't need to read all the latest<00:15:39.360> papers 00:15:40.910 --> 00:15:40.920 align:start position:0% latest papers 00:15:40.920 --> 00:15:42.050 align:start position:0% latest papers um<00:15:40.980> so<00:15:41.160> if<00:15:41.279> you've<00:15:41.459> ever<00:15:41.579> wanted<00:15:41.820> to 00:15:42.050 --> 00:15:42.060 align:start position:0% um so if you've ever wanted to 00:15:42.060 --> 00:15:44.090 align:start position:0% um so if you've ever wanted to understand<00:15:42.660> what's<00:15:43.139> really<00:15:43.320> going<00:15:43.560> on<00:15:43.800> under 00:15:44.090 --> 00:15:44.100 align:start position:0% understand what's really going on under 00:15:44.100 --> 00:15:45.710 align:start position:0% understand what's really going on under the<00:15:44.279> hood<00:15:44.399> of<00:15:44.579> elliptic<00:15:45.000> curves<00:15:45.240> this<00:15:45.600> would 00:15:45.710 --> 00:15:45.720 align:start position:0% the hood of elliptic curves this would 00:15:45.720 --> 00:15:47.810 align:start position:0% the hood of elliptic curves this would be<00:15:45.839> a<00:15:45.899> great<00:15:46.019> way<00:15:46.199> of<00:15:46.320> doing<00:15:46.440> it 00:15:47.810 --> 00:15:47.820 align:start position:0% be a great way of doing it 00:15:47.820 --> 00:15:50.329 align:start position:0% be a great way of doing it um<00:15:47.880> alternatively<00:15:48.540> you<00:15:48.959> could<00:15:49.079> use<00:15:49.339> an 00:15:50.329 --> 00:15:50.339 align:start position:0% um alternatively you could use an 00:15:50.339 --> 00:15:52.910 align:start position:0% um alternatively you could use an existing<00:15:50.699> client<00:15:51.079> uh<00:15:52.079> sorry<00:15:52.260> an<00:15:52.500> existing 00:15:52.910 --> 00:15:52.920 align:start position:0% existing client uh sorry an existing 00:15:52.920 --> 00:15:55.189 align:start position:0% existing client uh sorry an existing elliptic<00:15:53.880> curve<00:15:54.120> library<00:15:54.300> and<00:15:54.720> on<00:15:54.899> top<00:15:55.019> of 00:15:55.189 --> 00:15:55.199 align:start position:0% elliptic curve library and on top of 00:15:55.199 --> 00:15:57.949 align:start position:0% elliptic curve library and on top of that<00:15:55.579> you<00:15:56.579> could<00:15:56.699> just<00:15:56.820> implement<00:15:57.180> the<00:15:57.660> client 00:15:57.949 --> 00:15:57.959 align:start position:0% that you could just implement the client 00:15:57.959 --> 00:15:59.030 align:start position:0% that you could just implement the client side<00:15:58.139> of<00:15:58.320> things<00:15:58.440> like<00:15:58.740> the<00:15:58.920> secret 00:15:59.030 --> 00:15:59.040 align:start position:0% side of things like the secret 00:15:59.040 --> 00:16:01.790 align:start position:0% side of things like the secret generation<00:15:59.899> how<00:16:00.899> you<00:16:00.959> how<00:16:01.139> you<00:16:01.320> sampling<00:16:01.620> that 00:16:01.790 --> 00:16:01.800 align:start position:0% generation how you how you sampling that 00:16:01.800 --> 00:16:05.090 align:start position:0% generation how you how you sampling that Randomness<00:16:02.240> and<00:16:03.240> how<00:16:03.600> that<00:16:03.779> gets<00:16:04.139> passed<00:16:05.040> on 00:16:05.090 --> 00:16:05.100 align:start position:0% Randomness and how that gets passed on 00:16:05.100 --> 00:16:07.850 align:start position:0% Randomness and how that gets passed on to<00:16:05.339> this<00:16:05.579> elliptic<00:16:06.300> curve<00:16:06.600> Library 00:16:07.850 --> 00:16:07.860 align:start position:0% to this elliptic curve Library 00:16:07.860 --> 00:16:09.530 align:start position:0% to this elliptic curve Library and<00:16:08.220> then<00:16:08.339> the<00:16:08.519> second<00:16:08.639> category<00:16:09.060> of<00:16:09.240> Grants 00:16:09.530 --> 00:16:09.540 align:start position:0% and then the second category of Grants 00:16:09.540 --> 00:16:12.530 align:start position:0% and then the second category of Grants is<00:16:09.899> for<00:16:10.440> crazy<00:16:10.920> Randomness<00:16:11.519> generation<00:16:12.060> and 00:16:12.530 --> 00:16:12.540 align:start position:0% is for crazy Randomness generation and 00:16:12.540 --> 00:16:13.790 align:start position:0% is for crazy Randomness generation and contribution 00:16:13.790 --> 00:16:13.800 align:start position:0% contribution 00:16:13.800 --> 00:16:17.090 align:start position:0% contribution so<00:16:14.760> if<00:16:15.240> you<00:16:15.300> would<00:16:15.420> like<00:16:15.660> to<00:16:15.959> go<00:16:16.380> on<00:16:16.740> some<00:16:16.920> weird 00:16:17.090 --> 00:16:17.100 align:start position:0% so if you would like to go on some weird 00:16:17.100 --> 00:16:19.850 align:start position:0% so if you would like to go on some weird Vision<00:16:17.339> trip<00:16:17.699> that<00:16:18.300> somehow<00:16:18.720> is<00:16:19.380> going<00:16:19.620> to 00:16:19.850 --> 00:16:19.860 align:start position:0% Vision trip that somehow is going to 00:16:19.860 --> 00:16:22.370 align:start position:0% Vision trip that somehow is going to bring<00:16:20.579> out<00:16:20.820> this<00:16:21.240> the<00:16:21.600> the<00:16:21.720> secret<00:16:22.019> that<00:16:22.320> you 00:16:22.370 --> 00:16:22.380 align:start position:0% bring out this the the secret that you 00:16:22.380 --> 00:16:23.750 align:start position:0% bring out this the the secret that you can<00:16:22.500> prove<00:16:22.800> to<00:16:22.920> other<00:16:23.040> people<00:16:23.220> has<00:16:23.459> been<00:16:23.579> done 00:16:23.750 --> 00:16:23.760 align:start position:0% can prove to other people has been done 00:16:23.760 --> 00:16:25.389 align:start position:0% can prove to other people has been done in<00:16:23.940> an<00:16:24.060> interesting<00:16:24.360> way 00:16:25.389 --> 00:16:25.399 align:start position:0% in an interesting way 00:16:25.399 --> 00:16:28.850 align:start position:0% in an interesting way or<00:16:26.399> you<00:16:26.639> want<00:16:26.880> to<00:16:27.180> have 00:16:28.850 --> 00:16:28.860 align:start position:0% or you want to have 00:16:28.860 --> 00:16:32.210 align:start position:0% or you want to have use<00:16:29.519> your<00:16:29.760> local<00:16:30.120> Ant<00:16:30.420> Farm<00:16:30.660> to<00:16:31.380> like<00:16:31.800> measure 00:16:32.210 --> 00:16:32.220 align:start position:0% use your local Ant Farm to like measure 00:16:32.220 --> 00:16:33.650 align:start position:0% use your local Ant Farm to like measure the<00:16:32.399> location<00:16:32.519> of<00:16:32.820> ants<00:16:33.120> or<00:16:33.180> something<00:16:33.360> weird 00:16:33.650 --> 00:16:33.660 align:start position:0% the location of ants or something weird 00:16:33.660 --> 00:16:36.829 align:start position:0% the location of ants or something weird to<00:16:34.040> sample<00:16:35.040> Randomness<00:16:35.820> something<00:16:36.420> that<00:16:36.720> is 00:16:36.829 --> 00:16:36.839 align:start position:0% to sample Randomness something that is 00:16:36.839 --> 00:16:39.110 align:start position:0% to sample Randomness something that is very<00:16:37.019> hard<00:16:37.199> to<00:16:37.380> bias<00:16:37.740> such<00:16:38.279> you<00:16:38.579> can<00:16:38.759> convince 00:16:39.110 --> 00:16:39.120 align:start position:0% very hard to bias such you can convince 00:16:39.120 --> 00:16:41.930 align:start position:0% very hard to bias such you can convince other<00:16:39.420> people<00:16:39.660> that<00:16:40.380> your<00:16:41.339> contribution<00:16:41.699> was 00:16:41.930 --> 00:16:41.940 align:start position:0% other people that your contribution was 00:16:41.940 --> 00:16:44.810 align:start position:0% other people that your contribution was valid<00:16:42.300> that<00:16:42.480> you<00:16:42.779> generated<00:16:43.259> Randomness<00:16:43.860> in<00:16:44.459> a 00:16:44.810 --> 00:16:44.820 align:start position:0% valid that you generated Randomness in a 00:16:44.820 --> 00:16:46.749 align:start position:0% valid that you generated Randomness in a novel<00:16:45.120> and<00:16:45.240> interesting<00:16:45.600> way 00:16:46.749 --> 00:16:46.759 align:start position:0% novel and interesting way 00:16:46.759 --> 00:16:48.550 align:start position:0% novel and interesting way functionally 00:16:48.550 --> 00:16:48.560 align:start position:0% functionally 00:16:48.560 --> 00:16:51.829 align:start position:0% functionally these<00:16:49.560> are<00:16:49.680> less<00:16:49.800> important<00:16:50.279> because<00:16:50.839> your 00:16:51.829 --> 00:16:51.839 align:start position:0% these are less important because your 00:16:51.839 --> 00:16:53.210 align:start position:0% these are less important because your computer<00:16:51.959> should<00:16:52.259> do<00:16:52.440> this<00:16:52.560> Randomness<00:16:52.980> for 00:16:53.210 --> 00:16:53.220 align:start position:0% computer should do this Randomness for 00:16:53.220 --> 00:16:54.889 align:start position:0% computer should do this Randomness for you<00:16:53.339> we<00:16:53.699> all<00:16:53.820> rely<00:16:54.180> on<00:16:54.420> our<00:16:54.540> computer's 00:16:54.889 --> 00:16:54.899 align:start position:0% you we all rely on our computer's 00:16:54.899 --> 00:16:56.509 align:start position:0% you we all rely on our computer's ability<00:16:55.199> to<00:16:55.380> generate<00:16:55.680> Randomness<00:16:56.160> already 00:16:56.509 --> 00:16:56.519 align:start position:0% ability to generate Randomness already 00:16:56.519 --> 00:16:58.970 align:start position:0% ability to generate Randomness already for<00:16:57.480> all<00:16:58.019> of<00:16:58.139> the<00:16:58.380> encryption<00:16:58.800> and 00:16:58.970 --> 00:16:58.980 align:start position:0% for all of the encryption and 00:16:58.980 --> 00:17:01.850 align:start position:0% for all of the encryption and cryptography<00:16:59.639> used<00:17:00.600> within<00:17:01.139> this<00:17:01.380> ecosystem 00:17:01.850 --> 00:17:01.860 align:start position:0% cryptography used within this ecosystem 00:17:01.860 --> 00:17:06.350 align:start position:0% cryptography used within this ecosystem and<00:17:02.519> like<00:17:03.120> The<00:17:03.300> Wider<00:17:03.660> web<00:17:03.919> but<00:17:05.179> it's<00:17:06.179> even 00:17:06.350 --> 00:17:06.360 align:start position:0% and like The Wider web but it's even 00:17:06.360 --> 00:17:08.510 align:start position:0% and like The Wider web but it's even more<00:17:06.660> interesting<00:17:07.020> and<00:17:07.559> we<00:17:07.860> can<00:17:07.980> make<00:17:08.280> even 00:17:08.510 --> 00:17:08.520 align:start position:0% more interesting and we can make even 00:17:08.520 --> 00:17:09.949 align:start position:0% more interesting and we can make even more<00:17:08.640> assurances<00:17:09.179> if<00:17:09.480> you<00:17:09.600> start<00:17:09.780> doing 00:17:09.949 --> 00:17:09.959 align:start position:0% more assurances if you start doing 00:17:09.959 --> 00:17:12.530 align:start position:0% more assurances if you start doing things<00:17:10.199> like<00:17:10.439> this<00:17:10.679> and<00:17:11.220> then<00:17:11.339> finally<00:17:11.699> as<00:17:12.360> I'm 00:17:12.530 --> 00:17:12.540 align:start position:0% things like this and then finally as I'm 00:17:12.540 --> 00:17:13.610 align:start position:0% things like this and then finally as I'm sure<00:17:12.660> some<00:17:12.839> people<00:17:12.959> have<00:17:13.140> seen<00:17:13.260> from<00:17:13.439> past 00:17:13.610 --> 00:17:13.620 align:start position:0% sure some people have seen from past 00:17:13.620 --> 00:17:15.770 align:start position:0% sure some people have seen from past ceremonies<00:17:14.160> you<00:17:14.280> can<00:17:14.400> destroy<00:17:14.760> that<00:17:15.360> destroy 00:17:15.770 --> 00:17:15.780 align:start position:0% ceremonies you can destroy that destroy 00:17:15.780 --> 00:17:18.049 align:start position:0% ceremonies you can destroy that destroy the<00:17:15.900> hardware<00:17:16.020> used<00:17:16.380> to<00:17:16.500> generate<00:17:16.799> the<00:17:16.980> secret 00:17:18.049 --> 00:17:18.059 align:start position:0% the hardware used to generate the secret 00:17:18.059 --> 00:17:19.490 align:start position:0% the hardware used to generate the secret what's<00:17:18.540> a<00:17:18.780> little<00:17:18.839> bit<00:17:18.959> different<00:17:19.079> from<00:17:19.380> our 00:17:19.490 --> 00:17:19.500 align:start position:0% what's a little bit different from our 00:17:19.500 --> 00:17:22.010 align:start position:0% what's a little bit different from our ceremony<00:17:19.980> is<00:17:20.400> that<00:17:20.699> the<00:17:20.939> secret<00:17:21.059> only<00:17:21.419> exists 00:17:22.010 --> 00:17:22.020 align:start position:0% ceremony is that the secret only exists 00:17:22.020 --> 00:17:24.350 align:start position:0% ceremony is that the secret only exists in<00:17:22.439> the<00:17:22.500> realm<00:17:22.740> of<00:17:22.860> your<00:17:22.980> computer<00:17:23.220> for<00:17:23.880> a<00:17:24.179> few 00:17:24.350 --> 00:17:24.360 align:start position:0% in the realm of your computer for a few 00:17:24.360 --> 00:17:28.669 align:start position:0% in the realm of your computer for a few seconds<00:17:24.600> 30<00:17:25.380> 40<00:17:25.679> seconds<00:17:25.860> or<00:17:26.160> so<00:17:26.339> so<00:17:27.319> it's<00:17:28.319> not 00:17:28.669 --> 00:17:28.679 align:start position:0% seconds 30 40 seconds or so so it's not 00:17:28.679 --> 00:17:30.230 align:start position:0% seconds 30 40 seconds or so so it's not some<00:17:28.919> something<00:17:29.160> that<00:17:29.400> gets<00:17:29.580> stored<00:17:29.820> to<00:17:29.940> disk 00:17:30.230 --> 00:17:30.240 align:start position:0% some something that gets stored to disk 00:17:30.240 --> 00:17:32.990 align:start position:0% some something that gets stored to disk that<00:17:30.360> you<00:17:30.480> need<00:17:30.600> to<00:17:31.220> get<00:17:32.220> rid<00:17:32.340> of<00:17:32.460> later<00:17:32.640> or 00:17:32.990 --> 00:17:33.000 align:start position:0% that you need to get rid of later or 00:17:33.000 --> 00:17:34.669 align:start position:0% that you need to get rid of later or something<00:17:33.179> like<00:17:33.480> that<00:17:33.660> so<00:17:34.140> destroying<00:17:34.559> your 00:17:34.669 --> 00:17:34.679 align:start position:0% something like that so destroying your 00:17:34.679 --> 00:17:36.950 align:start position:0% something like that so destroying your computer<00:17:34.860> is<00:17:35.100> much<00:17:35.280> less<00:17:35.400> necessary<00:17:35.960> but 00:17:36.950 --> 00:17:36.960 align:start position:0% computer is much less necessary but 00:17:36.960 --> 00:17:38.570 align:start position:0% computer is much less necessary but should<00:17:37.440> this<00:17:37.559> be<00:17:37.799> something<00:17:37.980> you<00:17:38.220> want<00:17:38.340> to<00:17:38.460> do 00:17:38.570 --> 00:17:38.580 align:start position:0% should this be something you want to do 00:17:38.580 --> 00:17:39.590 align:start position:0% should this be something you want to do or<00:17:38.760> should<00:17:38.880> you<00:17:39.059> think<00:17:39.179> that<00:17:39.360> you<00:17:39.480> can 00:17:39.590 --> 00:17:39.600 align:start position:0% or should you think that you can 00:17:39.600 --> 00:17:41.750 align:start position:0% or should you think that you can convince<00:17:39.960> more<00:17:40.200> people<00:17:40.440> that<00:17:40.860> this<00:17:41.280> is<00:17:41.460> secure 00:17:41.750 --> 00:17:41.760 align:start position:0% convince more people that this is secure 00:17:41.760 --> 00:17:45.409 align:start position:0% convince more people that this is secure by<00:17:41.940> doing<00:17:42.120> it<00:17:42.919> reach<00:17:43.919> out<00:17:43.980> to<00:17:44.220> to<00:17:44.760> myself<00:17:45.000> or 00:17:45.409 --> 00:17:45.419 align:start position:0% by doing it reach out to to myself or 00:17:45.419 --> 00:17:48.110 align:start position:0% by doing it reach out to to myself or Trent<00:17:45.780> and<00:17:46.260> we<00:17:46.919> can<00:17:47.100> be<00:17:47.580> and<00:17:47.820> you<00:17:47.940> should<00:17:48.059> be 00:17:48.110 --> 00:17:48.120 align:start position:0% Trent and we can be and you should be 00:17:48.120 --> 00:17:49.909 align:start position:0% Trent and we can be and you should be able<00:17:48.240> to<00:17:48.360> see<00:17:48.600> a<00:17:49.200> bit<00:17:49.260> of<00:17:49.380> shouting<00:17:49.679> about<00:17:49.740> this 00:17:49.909 --> 00:17:49.919 align:start position:0% able to see a bit of shouting about this 00:17:49.919 --> 00:17:51.830 align:start position:0% able to see a bit of shouting about this on<00:17:50.100> Twitter<00:17:50.220> about<00:17:50.520> what<00:17:51.179> are<00:17:51.360> good<00:17:51.600> places 00:17:51.830 --> 00:17:51.840 align:start position:0% on Twitter about what are good places 00:17:51.840 --> 00:17:54.650 align:start position:0% on Twitter about what are good places for<00:17:52.320> Grants<00:17:52.679> and<00:17:53.280> I<00:17:53.400> think<00:17:53.520> those<00:17:53.700> are<00:17:53.880> the<00:17:54.179> the 00:17:54.650 --> 00:17:54.660 align:start position:0% for Grants and I think those are the the 00:17:54.660 --> 00:17:57.590 align:start position:0% for Grants and I think those are the the major<00:17:55.380> points<00:17:55.799> I<00:17:55.860> wanted<00:17:56.039> to<00:17:56.280> top<00:17:56.640> on<00:17:56.880> so<00:17:57.120> are 00:17:57.590 --> 00:17:57.600 align:start position:0% major points I wanted to top on so are 00:17:57.600 --> 00:18:01.870 align:start position:0% major points I wanted to top on so are there<00:17:57.720> any<00:17:57.840> questions 00:18:01.870 --> 00:18:01.880 align:start position:0% 00:18:01.880 --> 00:18:07.669 align:start position:0% Y2<00:18:02.880> to<00:18:03.120> the<00:18:03.299> power<00:18:03.419> 12.<00:18:04.160> ah<00:18:05.660> we<00:18:06.660> actually<00:18:07.260> have 00:18:07.669 --> 00:18:07.679 align:start position:0% Y2 to the power 12. ah we actually have 00:18:07.679 --> 00:18:10.909 align:start position:0% Y2 to the power 12. ah we actually have several<00:18:08.400> ceremonies<00:18:09.000> so 00:18:10.909 --> 00:18:10.919 align:start position:0% several ceremonies so 00:18:10.919 --> 00:18:14.150 align:start position:0% several ceremonies so um<00:18:10.980> where<00:18:12.020> the<00:18:13.020> ceremony<00:18:13.320> is<00:18:13.740> consist 00:18:14.150 --> 00:18:14.160 align:start position:0% um where the ceremony is consist 00:18:14.160 --> 00:18:16.730 align:start position:0% um where the ceremony is consist consists<00:18:14.700> of<00:18:14.880> four<00:18:15.480> sub-ceremonies<00:18:16.320> two<00:18:16.559> to 00:18:16.730 --> 00:18:16.740 align:start position:0% consists of four sub-ceremonies two to 00:18:16.740 --> 00:18:20.930 align:start position:0% consists of four sub-ceremonies two to the<00:18:16.860> power<00:18:16.980> of<00:18:17.220> 12<00:18:17.580> 13<00:18:18.240> 14<00:18:18.600> and<00:18:18.960> 15<00:18:19.280> which<00:18:20.280> are 00:18:20.930 --> 00:18:20.940 align:start position:0% the power of 12 13 14 and 15 which are 00:18:20.940 --> 00:18:24.230 align:start position:0% the power of 12 13 14 and 15 which are basically<00:18:21.419> all<00:18:22.140> the<00:18:22.440> sizes<00:18:22.980> of<00:18:23.340> data<00:18:23.700> blobs<00:18:24.059> we 00:18:24.230 --> 00:18:24.240 align:start position:0% basically all the sizes of data blobs we 00:18:24.240 --> 00:18:27.169 align:start position:0% basically all the sizes of data blobs we could<00:18:24.360> see<00:18:24.480> ever<00:18:24.720> needing<00:18:25.140> for<00:18:25.260> dunk<00:18:25.500> sharding 00:18:27.169 --> 00:18:27.179 align:start position:0% could see ever needing for dunk sharding 00:18:27.179 --> 00:18:30.289 align:start position:0% could see ever needing for dunk sharding um<00:18:27.299> so<00:18:27.960> 2<00:18:28.740> to<00:18:28.919> the<00:18:29.039> power<00:18:29.160> of<00:18:29.340> 12<00:18:29.520> basically 00:18:30.289 --> 00:18:30.299 align:start position:0% um so 2 to the power of 12 basically 00:18:30.299 --> 00:18:33.289 align:start position:0% um so 2 to the power of 12 basically gives<00:18:30.600> us<00:18:30.780> one<00:18:31.080> megabyte<00:18:32.179> blocks<00:18:33.179> in 00:18:33.289 --> 00:18:33.299 align:start position:0% gives us one megabyte blocks in 00:18:33.299 --> 00:18:35.029 align:start position:0% gives us one megabyte blocks in expectation<00:18:33.840> that<00:18:34.380> could<00:18:34.559> grow<00:18:34.679> up<00:18:34.799> to<00:18:34.919> two 00:18:35.029 --> 00:18:35.039 align:start position:0% expectation that could grow up to two 00:18:35.039 --> 00:18:37.490 align:start position:0% expectation that could grow up to two megabytes<00:18:35.460> but<00:18:35.640> basically<00:18:35.940> that's<00:18:36.320> which<00:18:37.320> we 00:18:37.490 --> 00:18:37.500 align:start position:0% megabytes but basically that's which we 00:18:37.500 --> 00:18:39.169 align:start position:0% megabytes but basically that's which we think<00:18:37.620> is<00:18:37.740> a<00:18:37.919> reasonable<00:18:38.160> Target<00:18:38.400> and<00:18:39.000> should 00:18:39.169 --> 00:18:39.179 align:start position:0% think is a reasonable Target and should 00:18:39.179 --> 00:18:41.690 align:start position:0% think is a reasonable Target and should be<00:18:39.360> fine<00:18:39.600> with<00:18:39.960> current<00:18:40.260> technology<00:18:40.799> but<00:18:41.580> we 00:18:41.690 --> 00:18:41.700 align:start position:0% be fine with current technology but we 00:18:41.700 --> 00:18:45.110 align:start position:0% be fine with current technology but we give<00:18:41.820> ourselves<00:18:42.179> the<00:18:42.600> ability<00:18:42.960> to<00:18:43.500> scale 00:18:45.110 --> 00:18:45.120 align:start position:0% give ourselves the ability to scale 00:18:45.120 --> 00:18:47.570 align:start position:0% give ourselves the ability to scale um<00:18:45.179> what's<00:18:45.419> that<00:18:45.720> 16<00:18:46.320> times<00:18:46.620> over<00:18:46.860> that<00:18:47.100> should 00:18:47.570 --> 00:18:47.580 align:start position:0% um what's that 16 times over that should 00:18:47.580 --> 00:18:49.549 align:start position:0% um what's that 16 times over that should we<00:18:47.760> need<00:18:48.120> more<00:18:48.360> growth<00:18:48.660> in<00:18:48.720> the<00:18:48.900> future<00:18:49.020> and<00:18:49.380> if 00:18:49.549 --> 00:18:49.559 align:start position:0% we need more growth in the future and if 00:18:49.559 --> 00:18:51.770 align:start position:0% we need more growth in the future and if we<00:18:49.679> need<00:18:49.799> anything<00:18:49.919> beyond<00:18:50.400> that<00:18:50.700> we'll<00:18:51.360> rerun 00:18:51.770 --> 00:18:51.780 align:start position:0% we need anything beyond that we'll rerun 00:18:51.780 --> 00:18:54.049 align:start position:0% we need anything beyond that we'll rerun the<00:18:51.900> setup<00:18:52.220> there's<00:18:53.220> also<00:18:53.460> an<00:18:53.520> optimization 00:18:54.049 --> 00:18:54.059 align:start position:0% the setup there's also an optimization 00:18:54.059 --> 00:18:55.789 align:start position:0% the setup there's also an optimization we<00:18:54.299> made<00:18:54.480> which<00:18:54.840> is<00:18:55.020> pretty<00:18:55.440> fun<00:18:55.620> and 00:18:55.789 --> 00:18:55.799 align:start position:0% we made which is pretty fun and 00:18:55.799 --> 00:18:57.289 align:start position:0% we made which is pretty fun and interesting<00:18:56.220> which<00:18:56.520> is<00:18:56.640> where<00:18:56.880> instead<00:18:57.179> of 00:18:57.289 --> 00:18:57.299 align:start position:0% interesting which is where instead of 00:18:57.299 --> 00:18:58.850 align:start position:0% interesting which is where instead of having<00:18:57.419> one<00:18:57.720> large<00:18:57.960> setup<00:18:58.320> and<00:18:58.440> then<00:18:58.559> using 00:18:58.850 --> 00:18:58.860 align:start position:0% having one large setup and then using 00:18:58.860 --> 00:19:01.490 align:start position:0% having one large setup and then using subsections<00:18:59.520> we<00:19:00.360> can<00:19:00.480> instead<00:19:00.840> do<00:19:01.080> several 00:19:01.490 --> 00:19:01.500 align:start position:0% subsections we can instead do several 00:19:01.500 --> 00:19:03.710 align:start position:0% subsections we can instead do several smaller<00:19:01.919> setups 00:19:03.710 --> 00:19:03.720 align:start position:0% smaller setups 00:19:03.720 --> 00:19:05.570 align:start position:0% smaller setups um<00:19:03.780> and<00:19:04.200> then<00:19:04.320> we<00:19:04.500> can<00:19:04.679> skip<00:19:04.860> the<00:19:05.100> low<00:19:05.220> degree 00:19:05.570 --> 00:19:05.580 align:start position:0% um and then we can skip the low degree 00:19:05.580 --> 00:19:07.370 align:start position:0% um and then we can skip the low degree proofs<00:19:06.000> because<00:19:06.240> these<00:19:06.600> setups<00:19:06.900> are<00:19:07.020> disjoint 00:19:07.370 --> 00:19:07.380 align:start position:0% proofs because these setups are disjoint 00:19:07.380 --> 00:19:09.289 align:start position:0% proofs because these setups are disjoint so<00:19:07.740> you<00:19:07.919> don't<00:19:08.039> have<00:19:08.220> more<00:19:08.460> Powers<00:19:08.760> should<00:19:09.120> you 00:19:09.289 --> 00:19:09.299 align:start position:0% so you don't have more Powers should you 00:19:09.299 --> 00:19:11.390 align:start position:0% so you don't have more Powers should you need<00:19:09.419> them<00:19:09.600> but<00:19:10.200> that<00:19:10.559> like<00:19:10.860> the<00:19:11.100> low<00:19:11.220> degrees 00:19:11.390 --> 00:19:11.400 align:start position:0% need them but that like the low degrees 00:19:11.400 --> 00:19:13.430 align:start position:0% need them but that like the low degrees in<00:19:11.700> force<00:19:11.940> by<00:19:12.120> running<00:19:12.240> out<00:19:12.419> of<00:19:12.539> points<00:19:12.840> that 00:19:13.430 --> 00:19:13.440 align:start position:0% in force by running out of points that 00:19:13.440 --> 00:19:16.190 align:start position:0% in force by running out of points that sounds<00:19:13.620> like<00:19:13.740> the<00:19:13.860> max<00:19:13.980> live<00:19:14.280> okay<00:19:14.760> hello<00:19:15.200> uh 00:19:16.190 --> 00:19:16.200 align:start position:0% sounds like the max live okay hello uh 00:19:16.200 --> 00:19:17.630 align:start position:0% sounds like the max live okay hello uh if<00:19:16.380> I<00:19:16.500> stand<00:19:16.740> correct<00:19:16.980> if<00:19:17.400> I<00:19:17.520> understand 00:19:17.630 --> 00:19:17.640 align:start position:0% if I stand correct if I understand 00:19:17.640 --> 00:19:19.490 align:start position:0% if I stand correct if I understand correctly<00:19:18.179> then 00:19:19.490 --> 00:19:19.500 align:start position:0% correctly then 00:19:19.500 --> 00:19:20.450 align:start position:0% correctly then um everyone 00:19:20.450 --> 00:19:20.460 align:start position:0% um everyone 00:19:20.460 --> 00:19:21.409 align:start position:0% um everyone um 00:19:21.409 --> 00:19:21.419 align:start position:0% um 00:19:21.419 --> 00:19:24.890 align:start position:0% um who's<00:19:22.400> participating<00:19:23.400> in<00:19:23.640> a<00:19:23.820> ceremony 00:19:24.890 --> 00:19:24.900 align:start position:0% who's participating in a ceremony 00:19:24.900 --> 00:19:28.130 align:start position:0% who's participating in a ceremony could<00:19:25.440> have<00:19:25.620> like<00:19:25.980> the<00:19:26.160> chance<00:19:26.340> to<00:19:27.360> um 00:19:28.130 --> 00:19:28.140 align:start position:0% could have like the chance to um 00:19:28.140 --> 00:19:31.310 align:start position:0% could have like the chance to um uh<00:19:29.100> see<00:19:29.460> what<00:19:29.640> the<00:19:29.760> current<00:19:29.940> secret<00:19:30.179> is<00:19:30.539> so<00:19:31.080> is 00:19:31.310 --> 00:19:31.320 align:start position:0% uh see what the current secret is so is 00:19:31.320 --> 00:19:33.169 align:start position:0% uh see what the current secret is so is there<00:19:31.559> a<00:19:31.679> chance<00:19:31.799> that<00:19:32.039> if<00:19:32.220> you<00:19:32.400> we<00:19:32.640> the<00:19:33.059> last 00:19:33.169 --> 00:19:33.179 align:start position:0% there a chance that if you we the last 00:19:33.179 --> 00:19:35.870 align:start position:0% there a chance that if you we the last one<00:19:33.740> picked<00:19:34.740> in<00:19:34.860> the<00:19:35.039> sequence<00:19:35.340> then<00:19:35.580> you 00:19:35.870 --> 00:19:35.880 align:start position:0% one picked in the sequence then you 00:19:35.880 --> 00:19:37.850 align:start position:0% one picked in the sequence then you would<00:19:36.000> have<00:19:36.120> a<00:19:36.299> higher<00:19:36.539> chance<00:19:36.780> to 00:19:37.850 --> 00:19:37.860 align:start position:0% would have a higher chance to 00:19:37.860 --> 00:19:42.289 align:start position:0% would have a higher chance to um<00:19:37.919> kind<00:19:38.460> of<00:19:38.640> ruin<00:19:39.539> the<00:19:39.720> whole<00:19:39.840> process 00:19:42.289 --> 00:19:42.299 align:start position:0% 00:19:42.299 --> 00:19:44.750 align:start position:0% um<00:19:42.360> so<00:19:42.660> not<00:19:42.960> really<00:19:43.200> and<00:19:43.799> that's<00:19:44.039> because<00:19:44.280> we 00:19:44.750 --> 00:19:44.760 align:start position:0% um so not really and that's because we 00:19:44.760 --> 00:19:46.370 align:start position:0% um so not really and that's because we don't<00:19:44.880> operate<00:19:45.299> over<00:19:45.539> the<00:19:45.720> secret<00:19:45.900> and<00:19:46.200> plain 00:19:46.370 --> 00:19:46.380 align:start position:0% don't operate over the secret and plain 00:19:46.380 --> 00:19:49.070 align:start position:0% don't operate over the secret and plain text<00:19:46.620> we<00:19:47.400> operate<00:19:47.760> over<00:19:48.059> the<00:19:48.299> secret<00:19:48.480> encoded 00:19:49.070 --> 00:19:49.080 align:start position:0% text we operate over the secret encoded 00:19:49.080 --> 00:19:50.870 align:start position:0% text we operate over the secret encoded as<00:19:49.200> an<00:19:49.320> elliptic<00:19:49.620> curve<00:19:49.919> point 00:19:50.870 --> 00:19:50.880 align:start position:0% as an elliptic curve point 00:19:50.880 --> 00:19:54.529 align:start position:0% as an elliptic curve point so<00:19:51.539> it's<00:19:52.320> not<00:19:52.559> we<00:19:53.220> don't<00:19:53.340> use<00:19:53.640> it<00:19:54.059> in<00:19:54.360> my 00:19:54.529 --> 00:19:54.539 align:start position:0% so it's not we don't use it in my 00:19:54.539 --> 00:19:55.970 align:start position:0% so it's not we don't use it in my example<00:19:54.780> where<00:19:54.960> the<00:19:55.080> secret<00:19:55.200> was<00:19:55.440> 30<00:19:55.620> we<00:19:55.860> don't 00:19:55.970 --> 00:19:55.980 align:start position:0% example where the secret was 30 we don't 00:19:55.980 --> 00:19:59.870 align:start position:0% example where the secret was 30 we don't actually<00:19:56.100> use<00:19:56.340> 30.<00:19:56.880> we<00:19:57.720> use<00:19:57.960> uh<00:19:58.860> 30<00:19:59.160> times<00:19:59.580> the 00:19:59.870 --> 00:19:59.880 align:start position:0% actually use 30. we use uh 30 times the 00:19:59.880 --> 00:20:01.490 align:start position:0% actually use 30. we use uh 30 times the generator<00:20:00.240> of<00:20:00.419> the<00:20:00.539> curve<00:20:00.720> so<00:20:00.840> some<00:20:01.080> elliptic 00:20:01.490 --> 00:20:01.500 align:start position:0% generator of the curve so some elliptic 00:20:01.500 --> 00:20:02.450 align:start position:0% generator of the curve so some elliptic curve<00:20:01.740> point 00:20:02.450 --> 00:20:02.460 align:start position:0% curve point 00:20:02.460 --> 00:20:04.669 align:start position:0% curve point which<00:20:03.120> means<00:20:03.360> when<00:20:03.539> I<00:20:03.660> give<00:20:03.780> you<00:20:03.900> the<00:20:04.080> powers<00:20:04.260> I 00:20:04.669 --> 00:20:04.679 align:start position:0% which means when I give you the powers I 00:20:04.679 --> 00:20:05.990 align:start position:0% which means when I give you the powers I actually<00:20:04.799> hand<00:20:05.039> you<00:20:05.220> this<00:20:05.400> elliptic<00:20:05.760> curve 00:20:05.990 --> 00:20:06.000 align:start position:0% actually hand you this elliptic curve 00:20:06.000 --> 00:20:07.130 align:start position:0% actually hand you this elliptic curve point<00:20:06.120> which<00:20:06.360> means<00:20:06.539> you<00:20:06.660> can't<00:20:06.780> see<00:20:06.960> into 00:20:07.130 --> 00:20:07.140 align:start position:0% point which means you can't see into 00:20:07.140 --> 00:20:08.930 align:start position:0% point which means you can't see into what<00:20:07.380> the<00:20:07.500> secret<00:20:07.679> is<00:20:07.919> so<00:20:08.580> if<00:20:08.760> you<00:20:08.820> have 00:20:08.930 --> 00:20:08.940 align:start position:0% what the secret is so if you have 00:20:08.940 --> 00:20:10.850 align:start position:0% what the secret is so if you have something<00:20:09.120> you<00:20:09.360> build<00:20:09.480> on<00:20:09.720> top<00:20:09.840> of<00:20:10.020> there<00:20:10.260> it 00:20:10.850 --> 00:20:10.860 align:start position:0% something you build on top of there it 00:20:10.860 --> 00:20:12.409 align:start position:0% something you build on top of there it it's<00:20:11.280> useless<00:20:11.640> to<00:20:11.760> you<00:20:11.880> just<00:20:12.059> looks<00:20:12.240> like<00:20:12.299> a 00:20:12.409 --> 00:20:12.419 align:start position:0% it's useless to you just looks like a 00:20:12.419 --> 00:20:13.730 align:start position:0% it's useless to you just looks like a random<00:20:12.600> elliptical<00:20:13.020> point<00:20:13.320> which<00:20:13.500> is<00:20:13.620> the 00:20:13.730 --> 00:20:13.740 align:start position:0% random elliptical point which is the 00:20:13.740 --> 00:20:15.230 align:start position:0% random elliptical point which is the same<00:20:13.860> security<00:20:14.039> assumption<00:20:14.580> we<00:20:14.760> depend<00:20:15.059> on 00:20:15.230 --> 00:20:15.240 align:start position:0% same security assumption we depend on 00:20:15.240 --> 00:20:18.590 align:start position:0% same security assumption we depend on for<00:20:15.960> the<00:20:16.260> rest<00:20:16.380> of<00:20:16.500> ethereum's<00:20:17.039> signatures 00:20:18.590 --> 00:20:18.600 align:start position:0% for the rest of ethereum's signatures 00:20:18.600 --> 00:20:19.730 align:start position:0% for the rest of ethereum's signatures Etc 00:20:19.730 --> 00:20:19.740 align:start position:0% Etc 00:20:19.740 --> 00:20:23.570 align:start position:0% Etc okay<00:20:20.280> thank<00:20:20.700> you<00:20:20.820> ciao<00:20:21.780> hello<00:20:22.200> okay 00:20:23.570 --> 00:20:23.580 align:start position:0% okay thank you ciao hello okay 00:20:23.580 --> 00:20:25.549 align:start position:0% okay thank you ciao hello okay um<00:20:23.640> you<00:20:24.059> mentioned<00:20:24.360> the<00:20:24.600> quantum 00:20:25.549 --> 00:20:25.559 align:start position:0% um you mentioned the quantum 00:20:25.559 --> 00:20:27.770 align:start position:0% um you mentioned the quantum vulnerability<00:20:26.220> yes<00:20:26.760> uh<00:20:27.299> what<00:20:27.539> is<00:20:27.660> the 00:20:27.770 --> 00:20:27.780 align:start position:0% vulnerability yes uh what is the 00:20:27.780 --> 00:20:29.930 align:start position:0% vulnerability yes uh what is the mitigation<00:20:28.200> for<00:20:28.679> that<00:20:28.860> and<00:20:29.220> also<00:20:29.460> BLS 00:20:29.930 --> 00:20:29.940 align:start position:0% mitigation for that and also BLS 00:20:29.940 --> 00:20:32.390 align:start position:0% mitigation for that and also BLS signature<00:20:30.419> aggregation<00:20:30.900> and 00:20:32.390 --> 00:20:32.400 align:start position:0% signature aggregation and 00:20:32.400 --> 00:20:35.150 align:start position:0% signature aggregation and when<00:20:32.880> is<00:20:33.240> that<00:20:33.419> going<00:20:33.720> to<00:20:33.840> be<00:20:33.900> a<00:20:34.020> problem 00:20:35.150 --> 00:20:35.160 align:start position:0% when is that going to be a problem 00:20:35.160 --> 00:20:37.010 align:start position:0% when is that going to be a problem when<00:20:35.760> it's<00:20:35.940> going<00:20:36.059> to<00:20:36.120> be<00:20:36.179> a<00:20:36.299> problem<00:20:36.419> I<00:20:36.720> wish<00:20:36.900> I 00:20:37.010 --> 00:20:37.020 align:start position:0% when it's going to be a problem I wish I 00:20:37.020 --> 00:20:38.090 align:start position:0% when it's going to be a problem I wish I knew<00:20:37.260> I<00:20:37.380> think<00:20:37.500> there's<00:20:37.620> a<00:20:37.740> lot<00:20:37.799> of<00:20:37.860> money<00:20:37.980> to 00:20:38.090 --> 00:20:38.100 align:start position:0% knew I think there's a lot of money to 00:20:38.100 --> 00:20:40.370 align:start position:0% knew I think there's a lot of money to be<00:20:38.280> able<00:20:38.400> to<00:20:38.460> answer<00:20:38.580> that<00:20:38.880> question 00:20:40.370 --> 00:20:40.380 align:start position:0% be able to answer that question 00:20:40.380 --> 00:20:42.310 align:start position:0% be able to answer that question um<00:20:40.860> so 00:20:42.310 --> 00:20:42.320 align:start position:0% um so 00:20:42.320 --> 00:20:46.310 align:start position:0% um so if<00:20:43.320> we<00:20:43.440> want<00:20:43.559> to<00:20:43.679> switch<00:20:43.860> away<00:20:44.039> from<00:20:44.400> this<00:20:44.640> to<00:20:45.320> a 00:20:46.310 --> 00:20:46.320 align:start position:0% if we want to switch away from this to a 00:20:46.320 --> 00:20:47.990 align:start position:0% if we want to switch away from this to a less<00:20:46.559> Quantum<00:20:47.039> vulnerable<00:20:47.460> things<00:20:47.640> we<00:20:47.880> would 00:20:47.990 --> 00:20:48.000 align:start position:0% less Quantum vulnerable things we would 00:20:48.000 --> 00:20:49.970 align:start position:0% less Quantum vulnerable things we would have<00:20:48.179> to<00:20:48.299> switch<00:20:48.600> to 00:20:49.970 --> 00:20:49.980 align:start position:0% have to switch to 00:20:49.980 --> 00:20:52.970 align:start position:0% have to switch to um probably<00:20:50.580> hash<00:20:51.000> based<00:20:51.480> commitments<00:20:52.380> local 00:20:52.970 --> 00:20:52.980 align:start position:0% um probably hash based commitments local 00:20:52.980 --> 00:20:56.390 align:start position:0% um probably hash based commitments local trees<00:20:53.460> the<00:20:54.299> issue<00:20:54.600> about<00:20:54.780> it<00:20:55.080> being 00:20:56.390 --> 00:20:56.400 align:start position:0% trees the issue about it being 00:20:56.400 --> 00:20:57.169 align:start position:0% trees the issue about it being um 00:20:57.169 --> 00:20:57.179 align:start position:0% um 00:20:57.179 --> 00:20:59.630 align:start position:0% um not<00:20:58.020> verifiable<00:20:58.559> easily<00:20:58.919> inside<00:20:59.100> of<00:20:59.340> snox 00:20:59.630 --> 00:20:59.640 align:start position:0% not verifiable easily inside of snox 00:20:59.640 --> 00:21:01.190 align:start position:0% not verifiable easily inside of snox would<00:20:59.880> go<00:21:00.000> away<00:21:00.120> because<00:21:00.419> Snorks<00:21:00.900> would<00:21:01.020> also 00:21:01.190 --> 00:21:01.200 align:start position:0% would go away because Snorks would also 00:21:01.200 --> 00:21:02.870 align:start position:0% would go away because Snorks would also be<00:21:01.320> broken 00:21:02.870 --> 00:21:02.880 align:start position:0% be broken 00:21:02.880 --> 00:21:05.450 align:start position:0% be broken um<00:21:02.940> so<00:21:03.240> like<00:21:03.539> depending<00:21:03.960> on<00:21:04.380> like<00:21:04.980> what<00:21:05.280> your 00:21:05.450 --> 00:21:05.460 align:start position:0% um so like depending on like what your 00:21:05.460 --> 00:21:06.890 align:start position:0% um so like depending on like what your commitment<00:21:05.820> schemes<00:21:06.240> are<00:21:06.360> you<00:21:06.480> would<00:21:06.660> have<00:21:06.840> to 00:21:06.890 --> 00:21:06.900 align:start position:0% commitment schemes are you would have to 00:21:06.900 --> 00:21:08.210 align:start position:0% commitment schemes are you would have to tail<00:21:07.080> all<00:21:07.260> of<00:21:07.380> that<00:21:07.500> but<00:21:07.620> we'd<00:21:07.860> have<00:21:07.980> to<00:21:08.100> see 00:21:08.210 --> 00:21:08.220 align:start position:0% tail all of that but we'd have to see 00:21:08.220 --> 00:21:09.770 align:start position:0% tail all of that but we'd have to see quite<00:21:08.400> a<00:21:08.520> big<00:21:08.640> re-architecting<00:21:09.360> of<00:21:09.600> this 00:21:09.770 --> 00:21:09.780 align:start position:0% quite a big re-architecting of this 00:21:09.780 --> 00:21:11.870 align:start position:0% quite a big re-architecting of this entire<00:21:10.080> system<00:21:10.320> and<00:21:11.280> so<00:21:11.460> it's<00:21:11.520> not<00:21:11.700> something 00:21:11.870 --> 00:21:11.880 align:start position:0% entire system and so it's not something 00:21:11.880 --> 00:21:13.789 align:start position:0% entire system and so it's not something we<00:21:12.120> have<00:21:12.299> like<00:21:12.600> a<00:21:12.780> built-in<00:21:13.080> backup<00:21:13.380> like<00:21:13.620> we 00:21:13.789 --> 00:21:13.799 align:start position:0% we have like a built-in backup like we 00:21:13.799 --> 00:21:17.150 align:start position:0% we have like a built-in backup like we do<00:21:13.919> for<00:21:14.220> many<00:21:14.460> of<00:21:14.700> the<00:21:15.000> the<00:21:15.299> other<00:21:15.720> seams 00:21:17.150 --> 00:21:17.160 align:start position:0% do for many of the the other seams 00:21:17.160 --> 00:21:19.370 align:start position:0% do for many of the the other seams um in<00:21:17.700> answer<00:21:17.820> to<00:21:18.120> your<00:21:18.240> BLS<00:21:18.720> aggregation<00:21:19.140> or 00:21:19.370 --> 00:21:19.380 align:start position:0% um in answer to your BLS aggregation or 00:21:19.380 --> 00:21:20.570 align:start position:0% um in answer to your BLS aggregation or whatever<00:21:19.500> question<00:21:19.860> for<00:21:20.100> the<00:21:20.220> signatures 00:21:20.570 --> 00:21:20.580 align:start position:0% whatever question for the signatures 00:21:20.580 --> 00:21:23.450 align:start position:0% whatever question for the signatures we're<00:21:20.700> using<00:21:20.940> for<00:21:21.059> ethereum<00:21:21.539> right<00:21:21.780> now<00:21:22.460> under 00:21:23.450 --> 00:21:23.460 align:start position:0% we're using for ethereum right now under 00:21:23.460 --> 00:21:25.730 align:start position:0% we're using for ethereum right now under the<00:21:23.640> hood<00:21:23.820> for<00:21:24.480> your<00:21:24.900> private<00:21:25.260> Keys<00:21:25.559> there's 00:21:25.730 --> 00:21:25.740 align:start position:0% the hood for your private Keys there's 00:21:25.740 --> 00:21:29.510 align:start position:0% the hood for your private Keys there's also<00:21:26.160> a<00:21:26.960> Lamport<00:21:27.960> keeper<00:21:28.440> like<00:21:29.100> Lamport 00:21:29.510 --> 00:21:29.520 align:start position:0% also a Lamport keeper like Lamport 00:21:29.520 --> 00:21:31.490 align:start position:0% also a Lamport keeper like Lamport signature<00:21:29.880> key<00:21:30.000> pair<00:21:30.299> so<00:21:31.140> we<00:21:31.260> can<00:21:31.380> always 00:21:31.490 --> 00:21:31.500 align:start position:0% signature key pair so we can always 00:21:31.500 --> 00:21:33.590 align:start position:0% signature key pair so we can always revert<00:21:31.980> to<00:21:32.100> that<00:21:32.280> to<00:21:32.580> execute<00:21:33.000> a<00:21:33.179> one-time 00:21:33.590 --> 00:21:33.600 align:start position:0% revert to that to execute a one-time 00:21:33.600 --> 00:21:35.330 align:start position:0% revert to that to execute a one-time transfer<00:21:34.080> should<00:21:34.320> that<00:21:34.500> need<00:21:34.679> to<00:21:34.799> happen<00:21:34.919> so 00:21:35.330 --> 00:21:35.340 align:start position:0% transfer should that need to happen so 00:21:35.340 --> 00:21:40.490 align:start position:0% transfer should that need to happen so there's<00:21:35.960> more<00:21:37.100> uh<00:21:38.299> there's<00:21:39.299> resilience<00:21:40.260> built 00:21:40.490 --> 00:21:40.500 align:start position:0% there's more uh there's resilience built 00:21:40.500 --> 00:21:41.570 align:start position:0% there's more uh there's resilience built into<00:21:40.620> that<00:21:40.799> already 00:21:41.570 --> 00:21:41.580 align:start position:0% into that already 00:21:41.580 --> 00:21:42.950 align:start position:0% into that already and<00:21:42.120> you<00:21:42.240> don't<00:21:42.360> think<00:21:42.539> it's<00:21:42.659> going<00:21:42.780> to<00:21:42.840> be 00:21:42.950 --> 00:21:42.960 align:start position:0% and you don't think it's going to be 00:21:42.960 --> 00:21:44.330 align:start position:0% and you don't think it's going to be within<00:21:43.200> the<00:21:43.380> next<00:21:43.500> 10<00:21:43.679> years<00:21:43.799> that<00:21:44.159> the 00:21:44.330 --> 00:21:44.340 align:start position:0% within the next 10 years that the 00:21:44.340 --> 00:21:45.890 align:start position:0% within the next 10 years that the quantum<00:21:44.760> will<00:21:44.880> happen<00:21:45.059> then<00:21:45.299> I<00:21:45.600> don't<00:21:45.720> think 00:21:45.890 --> 00:21:45.900 align:start position:0% quantum will happen then I don't think 00:21:45.900 --> 00:21:47.870 align:start position:0% quantum will happen then I don't think so<00:21:46.020> or<00:21:46.260> at<00:21:46.380> least<00:21:46.500> not<00:21:46.679> at<00:21:46.799> the<00:21:46.980> rate<00:21:47.100> where<00:21:47.580> all 00:21:47.870 --> 00:21:47.880 align:start position:0% so or at least not at the rate where all 00:21:47.880 --> 00:21:48.770 align:start position:0% so or at least not at the rate where all of<00:21:48.000> a<00:21:48.000> sudden<00:21:48.059> we're<00:21:48.240> gonna<00:21:48.299> have<00:21:48.480> to<00:21:48.600> throw 00:21:48.770 --> 00:21:48.780 align:start position:0% of a sudden we're gonna have to throw 00:21:48.780 --> 00:21:50.930 align:start position:0% of a sudden we're gonna have to throw everything<00:21:49.679> away 00:21:50.930 --> 00:21:50.940 align:start position:0% everything away 00:21:50.940 --> 00:21:52.310 align:start position:0% everything away um<00:21:51.059> the<00:21:51.240> good<00:21:51.360> news<00:21:51.539> is<00:21:51.720> we<00:21:52.020> probably<00:21:52.140> won't 00:21:52.310 --> 00:21:52.320 align:start position:0% um the good news is we probably won't 00:21:52.320 --> 00:21:53.750 align:start position:0% um the good news is we probably won't need<00:21:52.500> a<00:21:52.620> trusted<00:21:52.860> setup<00:21:53.159> in<00:21:53.340> the<00:21:53.460> case<00:21:53.580> that 00:21:53.750 --> 00:21:53.760 align:start position:0% need a trusted setup in the case that 00:21:53.760 --> 00:21:55.490 align:start position:0% need a trusted setup in the case that Quantum<00:21:54.179> is<00:21:54.360> broken<00:21:54.480> so<00:21:54.840> we<00:21:54.960> should<00:21:55.200> just<00:21:55.320> be 00:21:55.490 --> 00:21:55.500 align:start position:0% Quantum is broken so we should just be 00:21:55.500 --> 00:21:58.190 align:start position:0% Quantum is broken so we should just be able<00:21:55.679> to<00:21:55.799> switch<00:21:56.580> out<00:21:57.000> the<00:21:57.480> commitment<00:21:57.840> scheme 00:21:58.190 --> 00:21:58.200 align:start position:0% able to switch out the commitment scheme 00:21:58.200 --> 00:21:59.690 align:start position:0% able to switch out the commitment scheme we're<00:21:58.260> using 00:21:59.690 --> 00:21:59.700 align:start position:0% we're using 00:21:59.700 --> 00:22:02.029 align:start position:0% we're using um<00:22:00.240> but<00:22:00.659> yeah<00:22:00.780> I<00:22:01.140> don't<00:22:01.440> see<00:22:01.620> it<00:22:01.740> happening<00:22:01.919> in 00:22:02.029 --> 00:22:02.039 align:start position:0% um but yeah I don't see it happening in 00:22:02.039 --> 00:22:04.190 align:start position:0% um but yeah I don't see it happening in the<00:22:02.159> next<00:22:02.280> 10<00:22:02.460> years<00:22:02.640> if<00:22:03.240> it<00:22:03.360> does<00:22:03.539> I<00:22:04.140> don't 00:22:04.190 --> 00:22:04.200 align:start position:0% the next 10 years if it does I don't 00:22:04.200 --> 00:22:06.169 align:start position:0% the next 10 years if it does I don't think<00:22:04.380> it'll<00:22:04.559> happen<00:22:04.679> overnight<00:22:05.100> thank<00:22:06.000> you 00:22:06.169 --> 00:22:06.179 align:start position:0% think it'll happen overnight thank you 00:22:06.179 --> 00:22:09.350 align:start position:0% think it'll happen overnight thank you uh<00:22:07.140> I<00:22:07.380> was<00:22:07.440> wondering<00:22:07.740> how<00:22:08.039> like<00:22:08.520> on<00:22:08.820> a<00:22:09.000> on<00:22:09.240> a 00:22:09.350 --> 00:22:09.360 align:start position:0% uh I was wondering how like on a on a 00:22:09.360 --> 00:22:11.090 align:start position:0% uh I was wondering how like on a on a test<00:22:09.480> net<00:22:09.659> do<00:22:10.020> you<00:22:10.200> what<00:22:10.620> kind<00:22:10.740> of<00:22:10.860> tooling 00:22:11.090 --> 00:22:11.100 align:start position:0% test net do you what kind of tooling 00:22:11.100 --> 00:22:12.590 align:start position:0% test net do you what kind of tooling you're<00:22:11.280> using<00:22:11.580> to<00:22:11.700> like<00:22:11.820> execute<00:22:12.299> these 00:22:12.590 --> 00:22:12.600 align:start position:0% you're using to like execute these 00:22:12.600 --> 00:22:16.010 align:start position:0% you're using to like execute these adversarial<00:22:13.200> conditions<00:22:13.940> so<00:22:14.940> the<00:22:15.659> thing<00:22:15.840> with 00:22:16.010 --> 00:22:16.020 align:start position:0% adversarial conditions so the thing with 00:22:16.020 --> 00:22:17.870 align:start position:0% adversarial conditions so the thing with a<00:22:16.380> do<00:22:16.860> you<00:22:17.039> mean<00:22:17.100> adversarial<00:22:17.580> against<00:22:17.640> the 00:22:17.870 --> 00:22:17.880 align:start position:0% a do you mean adversarial against the 00:22:17.880 --> 00:22:19.730 align:start position:0% a do you mean adversarial against the sequencer<00:22:18.360> or<00:22:18.539> against<00:22:18.780> the<00:22:19.080> like<00:22:19.260> setup<00:22:19.620> in 00:22:19.730 --> 00:22:19.740 align:start position:0% sequencer or against the like setup in 00:22:19.740 --> 00:22:22.010 align:start position:0% sequencer or against the like setup in general<00:22:19.919> uh<00:22:20.580> so<00:22:20.760> like<00:22:20.880> on<00:22:21.240> a<00:22:21.419> test<00:22:21.539> net<00:22:21.720> you 00:22:22.010 --> 00:22:22.020 align:start position:0% general uh so like on a test net you 00:22:22.020 --> 00:22:24.350 align:start position:0% general uh so like on a test net you wanted<00:22:22.200> to<00:22:22.500> actually<00:22:22.740> like<00:22:23.100> have<00:22:23.700> one<00:22:24.000> of<00:22:24.120> them 00:22:24.350 --> 00:22:24.360 align:start position:0% wanted to actually like have one of them 00:22:24.360 --> 00:22:26.870 align:start position:0% wanted to actually like have one of them like<00:22:24.720> hide<00:22:25.140> a<00:22:25.380> secret<00:22:25.559> or<00:22:25.980> like<00:22:26.220> not<00:22:26.700> make 00:22:26.870 --> 00:22:26.880 align:start position:0% like hide a secret or like not make 00:22:26.880 --> 00:22:29.029 align:start position:0% like hide a secret or like not make something<00:22:27.120> available<00:22:27.419> like<00:22:28.260> how<00:22:28.500> easy<00:22:28.679> it<00:22:28.919> is 00:22:29.029 --> 00:22:29.039 align:start position:0% something available like how easy it is 00:22:29.039 --> 00:22:30.950 align:start position:0% something available like how easy it is to<00:22:29.280> how<00:22:29.520> easy<00:22:29.760> is<00:22:29.940> it<00:22:30.120> to<00:22:30.299> do<00:22:30.419> that<00:22:30.600> on<00:22:30.840> these 00:22:30.950 --> 00:22:30.960 align:start position:0% to how easy is it to do that on these 00:22:30.960 --> 00:22:34.010 align:start position:0% to how easy is it to do that on these like<00:22:31.080> Live<00:22:31.320> Test<00:22:31.620> Nets<00:22:32.159> so<00:22:33.000> the<00:22:33.360> thing<00:22:33.539> here<00:22:33.780> is 00:22:34.010 --> 00:22:34.020 align:start position:0% like Live Test Nets so the thing here is 00:22:34.020 --> 00:22:35.450 align:start position:0% like Live Test Nets so the thing here is that 00:22:35.450 --> 00:22:35.460 align:start position:0% that 00:22:35.460 --> 00:22:36.430 align:start position:0% that um 00:22:36.430 --> 00:22:36.440 align:start position:0% um 00:22:36.440 --> 00:22:38.750 align:start position:0% um there<00:22:37.440> there's<00:22:37.860> basically<00:22:38.280> just<00:22:38.520> one 00:22:38.750 --> 00:22:38.760 align:start position:0% there there's basically just one 00:22:38.760 --> 00:22:41.090 align:start position:0% there there's basically just one validity<00:22:39.240> condition<00:22:39.480> I<00:22:40.020> can<00:22:40.200> sort<00:22:40.559> of<00:22:40.679> okay 00:22:41.090 --> 00:22:41.100 align:start position:0% validity condition I can sort of okay 00:22:41.100 --> 00:22:42.350 align:start position:0% validity condition I can sort of okay I'm<00:22:41.340> already<00:22:41.460> on<00:22:41.640> the<00:22:41.760> next<00:22:41.820> person's<00:22:42.120> slides 00:22:42.350 --> 00:22:42.360 align:start position:0% I'm already on the next person's slides 00:22:42.360 --> 00:22:44.510 align:start position:0% I'm already on the next person's slides never<00:22:42.480> mind<00:22:42.659> click<00:22:43.440> is<00:22:43.559> not<00:22:43.679> working<00:22:44.280> um<00:22:44.280> I 00:22:44.510 --> 00:22:44.520 align:start position:0% never mind click is not working um I 00:22:44.520 --> 00:22:45.710 align:start position:0% never mind click is not working um I just<00:22:44.700> slide<00:22:44.940> on<00:22:45.059> this<00:22:45.240> basically<00:22:45.539> one 00:22:45.710 --> 00:22:45.720 align:start position:0% just slide on this basically one 00:22:45.720 --> 00:22:47.930 align:start position:0% just slide on this basically one validity<00:22:46.200> condition<00:22:46.919> or<00:22:47.220> two<00:22:47.340> checks<00:22:47.700> we<00:22:47.820> need 00:22:47.930 --> 00:22:47.940 align:start position:0% validity condition or two checks we need 00:22:47.940 --> 00:22:52.310 align:start position:0% validity condition or two checks we need to<00:22:48.059> do<00:22:48.179> to<00:22:48.980> assert<00:22:49.980> that<00:22:50.400> the<00:22:51.059> uh<00:22:51.720> update<00:22:52.140> has 00:22:52.310 --> 00:22:52.320 align:start position:0% to do to assert that the uh update has 00:22:52.320 --> 00:22:54.710 align:start position:0% to do to assert that the uh update has been<00:22:52.440> done<00:22:52.620> correctly<00:22:53.039> so<00:22:53.880> it's<00:22:54.179> not<00:22:54.419> that 00:22:54.710 --> 00:22:54.720 align:start position:0% been done correctly so it's not that 00:22:54.720 --> 00:22:56.510 align:start position:0% been done correctly so it's not that like<00:22:55.020> there's<00:22:55.260> a<00:22:55.500> weird<00:22:55.620> subset<00:22:56.039> of<00:22:56.159> collusion 00:22:56.510 --> 00:22:56.520 align:start position:0% like there's a weird subset of collusion 00:22:56.520 --> 00:22:58.490 align:start position:0% like there's a weird subset of collusion or<00:22:56.700> something<00:22:56.820> that<00:22:57.059> can<00:22:57.240> break<00:22:57.360> things<00:22:57.659> it's 00:22:58.490 --> 00:22:58.500 align:start position:0% or something that can break things it's 00:22:58.500 --> 00:23:00.830 align:start position:0% or something that can break things it's that<00:22:58.740> have<00:22:59.100> we<00:22:59.340> built<00:22:59.760> the<00:23:00.059> sequencer<00:23:00.539> in<00:23:00.720> a 00:23:00.830 --> 00:23:00.840 align:start position:0% that have we built the sequencer in a 00:23:00.840 --> 00:23:02.930 align:start position:0% that have we built the sequencer in a way<00:23:00.960> that's<00:23:01.260> such<00:23:01.620> that<00:23:01.799> it<00:23:01.980> can't<00:23:02.100> be<00:23:02.340> dosed 00:23:02.930 --> 00:23:02.940 align:start position:0% way that's such that it can't be dosed 00:23:02.940 --> 00:23:05.149 align:start position:0% way that's such that it can't be dosed or<00:23:03.120> crashed<00:23:03.500> which<00:23:04.500> we<00:23:04.620> can<00:23:04.740> use<00:23:04.799> fairly 00:23:05.149 --> 00:23:05.159 align:start position:0% or crashed which we can use fairly 00:23:05.159 --> 00:23:08.090 align:start position:0% or crashed which we can use fairly standard<00:23:05.460> testing<00:23:05.880> infrastructure<00:23:06.780> for 00:23:08.090 --> 00:23:08.100 align:start position:0% standard testing infrastructure for 00:23:08.100 --> 00:23:10.669 align:start position:0% standard testing infrastructure for um<00:23:08.159> and<00:23:09.000> when<00:23:09.780> you're<00:23:09.960> submitting<00:23:10.320> these 00:23:10.669 --> 00:23:10.679 align:start position:0% um and when you're submitting these 00:23:10.679 --> 00:23:13.250 align:start position:0% um and when you're submitting these these<00:23:11.159> files<00:23:11.460> we<00:23:11.820> can<00:23:12.000> like<00:23:12.539> try<00:23:12.780> corrupt<00:23:13.140> them 00:23:13.250 --> 00:23:13.260 align:start position:0% these files we can like try corrupt them 00:23:13.260 --> 00:23:14.450 align:start position:0% these files we can like try corrupt them and<00:23:13.380> that<00:23:13.500> kind<00:23:13.620> of<00:23:13.740> thing<00:23:13.860> but<00:23:14.100> that's<00:23:14.280> going 00:23:14.450 --> 00:23:14.460 align:start position:0% and that kind of thing but that's going 00:23:14.460 --> 00:23:16.549 align:start position:0% and that kind of thing but that's going to<00:23:14.580> be<00:23:14.700> rejected<00:23:15.240> immediately<00:23:15.600> by<00:23:16.080> the 00:23:16.549 --> 00:23:16.559 align:start position:0% to be rejected immediately by the 00:23:16.559 --> 00:23:18.470 align:start position:0% to be rejected immediately by the sequencer<00:23:17.159> so<00:23:17.640> it's<00:23:17.760> a<00:23:17.880> bit<00:23:17.940> different<00:23:18.059> from 00:23:18.470 --> 00:23:18.480 align:start position:0% sequencer so it's a bit different from 00:23:18.480 --> 00:23:20.149 align:start position:0% sequencer so it's a bit different from standard<00:23:19.080> test<00:23:19.260> Nets<00:23:19.620> that<00:23:19.679> we<00:23:19.799> see<00:23:19.919> from 00:23:20.149 --> 00:23:20.159 align:start position:0% standard test Nets that we see from 00:23:20.159 --> 00:23:22.070 align:start position:0% standard test Nets that we see from blockchain<00:23:20.520> networks<00:23:21.000> because<00:23:21.179> the 00:23:22.070 --> 00:23:22.080 align:start position:0% blockchain networks because the 00:23:22.080 --> 00:23:24.230 align:start position:0% blockchain networks because the adversary<00:23:22.500> looks<00:23:22.799> very<00:23:22.919> different<00:23:23.159> it's<00:23:24.000> more 00:23:24.230 --> 00:23:24.240 align:start position:0% adversary looks very different it's more 00:23:24.240 --> 00:23:26.090 align:start position:0% adversary looks very different it's more of<00:23:24.360> a<00:23:24.480> web<00:23:24.659> 2<00:23:24.900> adversary<00:23:25.380> in<00:23:25.620> attacking<00:23:25.980> the 00:23:26.090 --> 00:23:26.100 align:start position:0% of a web 2 adversary in attacking the 00:23:26.100 --> 00:23:28.909 align:start position:0% of a web 2 adversary in attacking the sequencer<00:23:26.460> directly<00:23:27.140> than<00:23:28.140> what<00:23:28.799> would 00:23:28.909 --> 00:23:28.919 align:start position:0% sequencer directly than what would 00:23:28.919 --> 00:23:30.950 align:start position:0% sequencer directly than what would happen<00:23:29.100> otherwise<00:23:29.520> okay<00:23:30.120> it<00:23:30.480> makes<00:23:30.600> a<00:23:30.780> lot<00:23:30.840> of 00:23:30.950 --> 00:23:30.960 align:start position:0% happen otherwise okay it makes a lot of 00:23:30.960 --> 00:23:32.870 align:start position:0% happen otherwise okay it makes a lot of sense<00:23:31.140> sure 00:23:32.870 --> 00:23:32.880 align:start position:0% sense sure 00:23:32.880 --> 00:23:36.049 align:start position:0% sense sure thanks<00:23:33.360> very<00:23:33.600> much<00:23:33.780> for<00:23:34.020> this<00:23:34.340> for<00:23:35.340> smaller 00:23:36.049 --> 00:23:36.059 align:start position:0% thanks very much for this for smaller 00:23:36.059 --> 00:23:39.169 align:start position:0% thanks very much for this for smaller projects<00:23:36.539> would<00:23:37.200> you<00:23:37.380> still<00:23:37.679> trust<00:23:38.100> if<00:23:38.520> if 00:23:39.169 --> 00:23:39.179 align:start position:0% projects would you still trust if if 00:23:39.179 --> 00:23:40.610 align:start position:0% projects would you still trust if if we're<00:23:39.419> talking<00:23:39.600> about<00:23:39.720> a<00:23:39.960> separate<00:23:40.440> project 00:23:40.610 --> 00:23:40.620 align:start position:0% we're talking about a separate project 00:23:40.620 --> 00:23:42.830 align:start position:0% we're talking about a separate project would<00:23:41.100> you<00:23:41.280> still<00:23:41.520> trust<00:23:41.880> The<00:23:42.059> Trusted<00:23:42.480> setup 00:23:42.830 --> 00:23:42.840 align:start position:0% would you still trust The Trusted setup 00:23:42.840 --> 00:23:44.330 align:start position:0% would you still trust The Trusted setup or<00:23:43.020> would<00:23:43.200> you<00:23:43.320> think<00:23:43.440> about<00:23:43.620> different 00:23:44.330 --> 00:23:44.340 align:start position:0% or would you think about different 00:23:44.340 --> 00:23:45.789 align:start position:0% or would you think about different strategy<00:23:44.880> stocks<00:23:45.299> or<00:23:45.419> anything<00:23:45.539> else 00:23:45.789 --> 00:23:45.799 align:start position:0% strategy stocks or anything else 00:23:45.799 --> 00:23:48.169 align:start position:0% strategy stocks or anything else trusting<00:23:46.799> this<00:23:46.980> setup<00:23:47.280> or<00:23:47.520> their<00:23:47.700> own<00:23:47.820> setup 00:23:48.169 --> 00:23:48.179 align:start position:0% trusting this setup or their own setup 00:23:48.179 --> 00:23:51.770 align:start position:0% trusting this setup or their own setup no<00:23:48.659> if<00:23:48.960> you<00:23:49.140> would<00:23:49.320> work<00:23:49.860> on<00:23:50.100> a<00:23:50.220> project<00:23:50.400> a<00:23:51.299> ziki 00:23:51.770 --> 00:23:51.780 align:start position:0% no if you would work on a project a ziki 00:23:51.780 --> 00:23:53.750 align:start position:0% no if you would work on a project a ziki project<00:23:51.960> now<00:23:52.380> that<00:23:52.919> is<00:23:53.100> kind<00:23:53.340> of<00:23:53.460> thinking 00:23:53.750 --> 00:23:53.760 align:start position:0% project now that is kind of thinking 00:23:53.760 --> 00:23:56.390 align:start position:0% project now that is kind of thinking should<00:23:54.120> we<00:23:54.419> do<00:23:54.659> trusted<00:23:55.080> setup<00:23:55.500> should<00:23:55.980> we<00:23:56.220> go 00:23:56.390 --> 00:23:56.400 align:start position:0% should we do trusted setup should we go 00:23:56.400 --> 00:23:58.730 align:start position:0% should we do trusted setup should we go with<00:23:56.640> stock<00:23:56.940> with<00:23:57.299> something<00:23:57.539> else<00:23:57.900> it's<00:23:58.559> hard 00:23:58.730 --> 00:23:58.740 align:start position:0% with stock with something else it's hard 00:23:58.740 --> 00:24:00.409 align:start position:0% with stock with something else it's hard to<00:23:58.919> know<00:23:59.100> I<00:23:59.400> think<00:23:59.580> a<00:23:59.760> lot<00:23:59.820> of<00:23:59.880> that<00:24:00.000> comes<00:24:00.299> down 00:24:00.409 --> 00:24:00.419 align:start position:0% to know I think a lot of that comes down 00:24:00.419 --> 00:24:03.409 align:start position:0% to know I think a lot of that comes down to<00:24:00.600> the<00:24:00.720> execution<00:24:01.460> things<00:24:02.460> like<00:24:02.820> how<00:24:03.299> many 00:24:03.409 --> 00:24:03.419 align:start position:0% to the execution things like how many 00:24:03.419 --> 00:24:06.110 align:start position:0% to the execution things like how many participants<00:24:04.020> have<00:24:04.320> you<00:24:04.500> have<00:24:04.860> you<00:24:05.039> had<00:24:05.220> come 00:24:06.110 --> 00:24:06.120 align:start position:0% participants have you have you had come 00:24:06.120 --> 00:24:07.909 align:start position:0% participants have you have you had come on<00:24:06.299> board<00:24:06.419> or<00:24:06.960> how<00:24:07.559> many<00:24:07.740> different 00:24:07.909 --> 00:24:07.919 align:start position:0% on board or how many different 00:24:07.919 --> 00:24:09.950 align:start position:0% on board or how many different implementations<00:24:08.700> do<00:24:09.059> you<00:24:09.179> have<00:24:09.240> we<00:24:09.780> already 00:24:09.950 --> 00:24:09.960 align:start position:0% implementations do you have we already 00:24:09.960 --> 00:24:12.230 align:start position:0% implementations do you have we already have<00:24:10.140> a<00:24:10.260> few<00:24:10.380> floating<00:24:10.679> around<00:24:11.000> I<00:24:12.000> think<00:24:12.120> we 00:24:12.230 --> 00:24:12.240 align:start position:0% have a few floating around I think we 00:24:12.240 --> 00:24:13.490 align:start position:0% have a few floating around I think we could<00:24:12.360> get<00:24:12.539> something<00:24:12.720> like<00:24:12.960> 10<00:24:13.200> or<00:24:13.380> 12 00:24:13.490 --> 00:24:13.500 align:start position:0% could get something like 10 or 12 00:24:13.500 --> 00:24:15.409 align:start position:0% could get something like 10 or 12 different<00:24:13.740> implementations<00:24:14.400> these<00:24:15.240> kinds<00:24:15.419> of 00:24:15.409 --> 00:24:15.419 align:start position:0% different implementations these kinds of 00:24:15.419 --> 00:24:17.210 align:start position:0% different implementations these kinds of things<00:24:15.600> the<00:24:16.200> good<00:24:16.320> news<00:24:16.440> is<00:24:16.620> that<00:24:16.799> once<00:24:17.100> this 00:24:17.210 --> 00:24:17.220 align:start position:0% things the good news is that once this 00:24:17.220 --> 00:24:18.529 align:start position:0% things the good news is that once this is<00:24:17.340> up<00:24:17.460> there's<00:24:17.700> now<00:24:17.880> more<00:24:18.059> infrastructure 00:24:18.529 --> 00:24:18.539 align:start position:0% is up there's now more infrastructure 00:24:18.539 --> 00:24:20.570 align:start position:0% is up there's now more infrastructure for<00:24:18.840> smaller<00:24:19.260> projects<00:24:19.620> to<00:24:19.860> leverage<00:24:20.220> in 00:24:20.570 --> 00:24:20.580 align:start position:0% for smaller projects to leverage in 00:24:20.580 --> 00:24:21.890 align:start position:0% for smaller projects to leverage in terms<00:24:20.820> of 00:24:21.890 --> 00:24:21.900 align:start position:0% terms of 00:24:21.900 --> 00:24:23.570 align:start position:0% terms of um<00:24:21.960> like<00:24:22.440> just<00:24:22.559> extending<00:24:22.980> these<00:24:23.159> powers<00:24:23.280> that 00:24:23.570 --> 00:24:23.580 align:start position:0% um like just extending these powers that 00:24:23.580 --> 00:24:25.730 align:start position:0% um like just extending these powers that would<00:24:23.700> be<00:24:23.880> great<00:24:24.059> but 00:24:25.730 --> 00:24:25.740 align:start position:0% would be great but 00:24:25.740 --> 00:24:28.610 align:start position:0% would be great but it<00:24:26.220> like<00:24:26.520> in<00:24:26.700> intrinsically<00:24:27.419> that<00:24:27.960> it's<00:24:28.440> like 00:24:28.610 --> 00:24:28.620 align:start position:0% it like in intrinsically that it's like 00:24:28.620 --> 00:24:31.130 align:start position:0% it like in intrinsically that it's like very<00:24:28.740> much<00:24:28.860> a<00:24:28.980> case-to-case<00:24:29.640> based<00:24:30.360> thing 00:24:31.130 --> 00:24:31.140 align:start position:0% very much a case-to-case based thing 00:24:31.140 --> 00:24:33.230 align:start position:0% very much a case-to-case based thing um<00:24:31.260> I<00:24:31.799> I<00:24:31.980> don't<00:24:32.220> think<00:24:32.400> trusted<00:24:32.760> setups<00:24:33.179> in 00:24:33.230 --> 00:24:33.240 align:start position:0% um I I don't think trusted setups in 00:24:33.240 --> 00:24:34.789 align:start position:0% um I I don't think trusted setups in general<00:24:33.360> are<00:24:33.600> safe<00:24:33.840> I<00:24:34.200> think<00:24:34.320> there<00:24:34.440> are<00:24:34.620> ways 00:24:34.789 --> 00:24:34.799 align:start position:0% general are safe I think there are ways 00:24:34.799 --> 00:24:37.130 align:start position:0% general are safe I think there are ways of<00:24:34.860> executing<00:24:35.280> them<00:24:35.520> that<00:24:35.940> are<00:24:36.120> safe 00:24:37.130 --> 00:24:37.140 align:start position:0% of executing them that are safe 00:24:37.140 --> 00:24:39.470 align:start position:0% of executing them that are safe um<00:24:37.260> and<00:24:37.500> I<00:24:37.620> think<00:24:38.280> some<00:24:38.700> of<00:24:38.820> these<00:24:39.000> things<00:24:39.240> I 00:24:39.470 --> 00:24:39.480 align:start position:0% um and I think some of these things I 00:24:39.480 --> 00:24:40.730 align:start position:0% um and I think some of these things I touched<00:24:39.659> on<00:24:39.780> are<00:24:39.900> important<00:24:40.380> to<00:24:40.500> do<00:24:40.620> that 00:24:40.730 --> 00:24:40.740 align:start position:0% touched on are important to do that 00:24:40.740 --> 00:24:42.470 align:start position:0% touched on are important to do that thanks 00:24:42.470 --> 00:24:42.480 align:start position:0% thanks 00:24:42.480 --> 00:24:44.990 align:start position:0% thanks um<00:24:42.600> have<00:24:42.960> you<00:24:43.140> considered<00:24:43.740> starting<00:24:44.400> with<00:24:44.820> an 00:24:44.990 --> 00:24:45.000 align:start position:0% um have you considered starting with an 00:24:45.000 --> 00:24:48.470 align:start position:0% um have you considered starting with an already<00:24:45.260> established<00:24:46.260> setup<00:24:46.679> and 00:24:48.470 --> 00:24:48.480 align:start position:0% already established setup and 00:24:48.480 --> 00:24:50.690 align:start position:0% already established setup and basically<00:24:49.200> adding<00:24:49.620> your<00:24:49.740> Randomness<00:24:50.220> into<00:24:50.520> it 00:24:50.690 --> 00:24:50.700 align:start position:0% basically adding your Randomness into it 00:24:50.700 --> 00:24:53.570 align:start position:0% basically adding your Randomness into it and<00:24:51.000> if<00:24:51.299> you're<00:24:51.539> not<00:24:51.720> doing<00:24:51.900> this<00:24:52.200> why<00:24:52.559> not 00:24:53.570 --> 00:24:53.580 align:start position:0% and if you're not doing this why not 00:24:53.580 --> 00:24:55.669 align:start position:0% and if you're not doing this why not uh<00:24:54.240> yeah<00:24:54.419> we<00:24:54.659> have<00:24:54.840> there's<00:24:55.140> been<00:24:55.380> a<00:24:55.500> lot<00:24:55.559> of 00:24:55.669 --> 00:24:55.679 align:start position:0% uh yeah we have there's been a lot of 00:24:55.679 --> 00:24:57.409 align:start position:0% uh yeah we have there's been a lot of discussion<00:24:56.039> on<00:24:56.220> that 00:24:57.409 --> 00:24:57.419 align:start position:0% discussion on that 00:24:57.419 --> 00:24:59.870 align:start position:0% discussion on that um<00:24:57.480> so<00:24:57.960> we're<00:24:58.260> using<00:24:58.679> the<00:24:59.039> the<00:24:59.039> setup<00:24:59.520> is<00:24:59.700> done 00:24:59.870 --> 00:24:59.880 align:start position:0% um so we're using the the setup is done 00:24:59.880 --> 00:25:04.250 align:start position:0% um so we're using the the setup is done over<00:25:00.240> the<00:25:00.780> BLS<00:25:01.460> 1231<00:25:02.460> curves 00:25:04.250 --> 00:25:04.260 align:start position:0% over the BLS 1231 curves 00:25:04.260 --> 00:25:05.390 align:start position:0% over the BLS 1231 curves um<00:25:04.320> which 00:25:05.390 --> 00:25:05.400 align:start position:0% um which 00:25:05.400 --> 00:25:06.710 align:start position:0% um which I<00:25:05.820> mean<00:25:05.880> there<00:25:06.000> have<00:25:06.120> been<00:25:06.240> setups<00:25:06.600> done 00:25:06.710 --> 00:25:06.720 align:start position:0% I mean there have been setups done 00:25:06.720 --> 00:25:07.610 align:start position:0% I mean there have been setups done before 00:25:07.610 --> 00:25:07.620 align:start position:0% before 00:25:07.620 --> 00:25:10.310 align:start position:0% before um<00:25:07.679> but<00:25:08.100> not<00:25:08.640> that<00:25:08.760> many<00:25:08.880> anyway 00:25:10.310 --> 00:25:10.320 align:start position:0% um but not that many anyway 00:25:10.320 --> 00:25:12.049 align:start position:0% um but not that many anyway um<00:25:10.440> what<00:25:10.919> I<00:25:10.980> was<00:25:11.100> referencing<00:25:11.400> earlier<00:25:11.760> with 00:25:12.049 --> 00:25:12.059 align:start position:0% um what I was referencing earlier with 00:25:12.059 --> 00:25:14.510 align:start position:0% um what I was referencing earlier with this<00:25:12.240> optimization<00:25:12.900> where<00:25:13.799> we<00:25:14.159> stopped<00:25:14.460> doing 00:25:14.510 --> 00:25:14.520 align:start position:0% this optimization where we stopped doing 00:25:14.520 --> 00:25:16.250 align:start position:0% this optimization where we stopped doing the<00:25:14.700> low<00:25:14.820> degree<00:25:15.120> proofs<00:25:15.480> because<00:25:15.720> we<00:25:15.900> ran<00:25:16.140> out 00:25:16.250 --> 00:25:16.260 align:start position:0% the low degree proofs because we ran out 00:25:16.260 --> 00:25:18.230 align:start position:0% the low degree proofs because we ran out of<00:25:16.380> powers<00:25:16.559> so<00:25:17.280> we<00:25:17.460> don't<00:25:17.580> have<00:25:17.700> to<00:25:17.880> check<00:25:18.000> that 00:25:18.230 --> 00:25:18.240 align:start position:0% of powers so we don't have to check that 00:25:18.240 --> 00:25:20.690 align:start position:0% of powers so we don't have to check that the<00:25:18.419> polynomials<00:25:19.080> of<00:25:19.200> degree<00:25:19.559> less<00:25:20.220> than<00:25:20.400> 2<00:25:20.520> to 00:25:20.690 --> 00:25:20.700 align:start position:0% the polynomials of degree less than 2 to 00:25:20.700 --> 00:25:22.610 align:start position:0% the polynomials of degree less than 2 to the<00:25:20.820> power<00:25:20.940> of<00:25:21.059> 12<00:25:21.240> because<00:25:21.659> there<00:25:21.960> is<00:25:22.080> no<00:25:22.200> 2<00:25:22.440> to 00:25:22.610 --> 00:25:22.620 align:start position:0% the power of 12 because there is no 2 to 00:25:22.620 --> 00:25:24.649 align:start position:0% the power of 12 because there is no 2 to the<00:25:22.740> power<00:25:22.799> of<00:25:23.039> 12<00:25:23.159> plus<00:25:23.400> one<00:25:23.700> point<00:25:24.059> we 00:25:24.649 --> 00:25:24.659 align:start position:0% the power of 12 plus one point we 00:25:24.659 --> 00:25:27.110 align:start position:0% the power of 12 plus one point we literally<00:25:24.960> run<00:25:25.200> out<00:25:25.580> this<00:25:26.580> optimization 00:25:27.110 --> 00:25:27.120 align:start position:0% literally run out this optimization 00:25:27.120 --> 00:25:28.669 align:start position:0% literally run out this optimization Falls<00:25:27.480> away<00:25:27.779> when<00:25:28.020> we<00:25:28.200> use<00:25:28.320> these<00:25:28.559> other 00:25:28.669 --> 00:25:28.679 align:start position:0% Falls away when we use these other 00:25:28.679 --> 00:25:30.289 align:start position:0% Falls away when we use these other trusted<00:25:29.100> setups<00:25:29.400> that<00:25:29.520> exist<00:25:29.700> through<00:25:29.880> to<00:25:30.179> the 00:25:30.289 --> 00:25:30.299 align:start position:0% trusted setups that exist through to the 00:25:30.299 --> 00:25:34.549 align:start position:0% trusted setups that exist through to the safety<00:25:30.659> of<00:25:31.440> uh<00:25:32.340> the<00:25:33.240> the<00:25:33.360> kcg<00:25:33.900> commitments<00:25:34.380> and 00:25:34.549 --> 00:25:34.559 align:start position:0% safety of uh the the kcg commitments and 00:25:34.559 --> 00:25:36.529 align:start position:0% safety of uh the the kcg commitments and the<00:25:34.740> way<00:25:34.799> we're<00:25:34.919> using<00:25:35.100> them<00:25:35.220> in<00:25:35.340> 4844 00:25:36.529 --> 00:25:36.539 align:start position:0% the way we're using them in 4844 00:25:36.539 --> 00:25:38.510 align:start position:0% the way we're using them in 4844 so<00:25:37.020> for<00:25:37.200> asset<00:25:37.559> breaks<00:25:37.860> things<00:25:37.980> being<00:25:38.220> able<00:25:38.400> to 00:25:38.510 --> 00:25:38.520 align:start position:0% so for asset breaks things being able to 00:25:38.520 --> 00:25:40.850 align:start position:0% so for asset breaks things being able to use<00:25:38.700> it<00:25:38.820> so<00:25:39.299> while<00:25:39.779> it<00:25:39.960> would<00:25:40.140> be<00:25:40.320> a<00:25:40.500> good<00:25:40.620> base 00:25:40.850 --> 00:25:40.860 align:start position:0% use it so while it would be a good base 00:25:40.860 --> 00:25:42.950 align:start position:0% use it so while it would be a good base from<00:25:41.340> the<00:25:41.700> perspective<00:25:42.059> of<00:25:42.360> not<00:25:42.539> knowing<00:25:42.779> what 00:25:42.950 --> 00:25:42.960 align:start position:0% from the perspective of not knowing what 00:25:42.960 --> 00:25:45.289 align:start position:0% from the perspective of not knowing what the<00:25:43.080> secret<00:25:43.200> is<00:25:43.620> from<00:25:44.340> the<00:25:44.760> security<00:25:44.940> things 00:25:45.289 --> 00:25:45.299 align:start position:0% the secret is from the security things 00:25:45.299 --> 00:25:47.990 align:start position:0% the secret is from the security things we<00:25:45.480> care<00:25:45.659> about<00:25:45.840> in<00:25:46.500> our<00:25:47.220> application<00:25:47.640> it 00:25:47.990 --> 00:25:48.000 align:start position:0% we care about in our application it 00:25:48.000 --> 00:25:50.149 align:start position:0% we care about in our application it doesn't<00:25:48.120> add<00:25:48.360> anything<00:25:48.620> and<00:25:49.620> then<00:25:49.740> it's<00:25:49.919> more 00:25:50.149 --> 00:25:50.159 align:start position:0% doesn't add anything and then it's more 00:25:50.159 --> 00:25:51.649 align:start position:0% doesn't add anything and then it's more of<00:25:50.279> like<00:25:50.580> arguing<00:25:51.059> about<00:25:51.179> nothing<00:25:51.419> about 00:25:51.649 --> 00:25:51.659 align:start position:0% of like arguing about nothing about 00:25:51.659 --> 00:25:52.970 align:start position:0% of like arguing about nothing about Sleep<00:25:51.960> Numbers<00:25:52.260> kind<00:25:52.500> of<00:25:52.620> thing<00:25:52.679> it's<00:25:52.799> much 00:25:52.970 --> 00:25:52.980 align:start position:0% Sleep Numbers kind of thing it's much 00:25:52.980 --> 00:25:54.169 align:start position:0% Sleep Numbers kind of thing it's much easier<00:25:53.159> just<00:25:53.340> to<00:25:53.460> start<00:25:53.520> with<00:25:53.700> the<00:25:53.880> generator 00:25:54.169 --> 00:25:54.179 align:start position:0% easier just to start with the generator 00:25:54.179 --> 00:25:55.970 align:start position:0% easier just to start with the generator which<00:25:54.419> is<00:25:54.539> what<00:25:54.720> we're<00:25:54.840> going<00:25:54.960> to<00:25:55.080> be<00:25:55.140> doing<00:25:55.320> oh 00:25:55.970 --> 00:25:55.980 align:start position:0% which is what we're going to be doing oh 00:25:55.980 --> 00:25:58.250 align:start position:0% which is what we're going to be doing oh yes<00:25:56.279> it's<00:25:56.700> a<00:25:56.940> sequential<00:25:57.419> process<00:25:57.779> so<00:25:58.020> sorry 00:25:58.250 --> 00:25:58.260 align:start position:0% yes it's a sequential process so sorry 00:25:58.260 --> 00:25:59.570 align:start position:0% yes it's a sequential process so sorry the<00:25:58.440> question<00:25:58.620> was<00:25:58.799> do<00:25:58.980> you<00:25:59.159> run<00:25:59.220> it<00:25:59.400> in 00:25:59.570 --> 00:25:59.580 align:start position:0% the question was do you run it in 00:25:59.580 --> 00:26:01.310 align:start position:0% the question was do you run it in sequence<00:25:59.940> and<00:26:00.120> how<00:26:00.240> do<00:26:00.419> we<00:26:00.480> handle<00:26:00.960> civil 00:26:01.310 --> 00:26:01.320 align:start position:0% sequence and how do we handle civil 00:26:01.320 --> 00:26:03.970 align:start position:0% sequence and how do we handle civil attacks<00:26:01.679> so<00:26:02.640> yes<00:26:02.820> we<00:26:03.000> do<00:26:03.120> run<00:26:03.240> it<00:26:03.419> in<00:26:03.539> sequence 00:26:03.970 --> 00:26:03.980 align:start position:0% attacks so yes we do run it in sequence 00:26:03.980 --> 00:26:07.130 align:start position:0% attacks so yes we do run it in sequence because<00:26:04.980> of<00:26:05.279> the<00:26:05.520> way<00:26:05.820> the 00:26:07.130 --> 00:26:07.140 align:start position:0% because of the way the 00:26:07.140 --> 00:26:09.169 align:start position:0% because of the way the um<00:26:07.200> things<00:26:07.740> are<00:26:08.039> encrypted<00:26:08.580> or<00:26:08.760> whatever<00:26:08.880> it 00:26:09.169 --> 00:26:09.179 align:start position:0% um things are encrypted or whatever it 00:26:09.179 --> 00:26:10.909 align:start position:0% um things are encrypted or whatever it fundamentally<00:26:09.659> has<00:26:09.900> to<00:26:10.020> be<00:26:10.200> that<00:26:10.500> like<00:26:10.740> the 00:26:10.909 --> 00:26:10.919 align:start position:0% fundamentally has to be that like the 00:26:10.919 --> 00:26:12.230 align:start position:0% fundamentally has to be that like the way<00:26:11.039> the<00:26:11.159> math<00:26:11.279> works<00:26:11.580> out<00:26:11.640> it<00:26:11.820> fundamentally 00:26:12.230 --> 00:26:12.240 align:start position:0% way the math works out it fundamentally 00:26:12.240 --> 00:26:14.690 align:start position:0% way the math works out it fundamentally has<00:26:12.480> to<00:26:12.659> be<00:26:12.900> a<00:26:13.500> sequential<00:26:14.039> process<00:26:14.279> we<00:26:14.580> can't 00:26:14.690 --> 00:26:14.700 align:start position:0% has to be a sequential process we can't 00:26:14.700 --> 00:26:17.390 align:start position:0% has to be a sequential process we can't combine<00:26:15.059> two<00:26:15.240> parallel<00:26:15.539> ones<00:26:15.840> later 00:26:17.390 --> 00:26:17.400 align:start position:0% combine two parallel ones later 00:26:17.400 --> 00:26:19.870 align:start position:0% combine two parallel ones later um our<00:26:17.640> civil<00:26:18.120> processes<00:26:19.020> are<00:26:19.500> twofold 00:26:19.870 --> 00:26:19.880 align:start position:0% um our civil processes are twofold 00:26:19.880 --> 00:26:22.070 align:start position:0% um our civil processes are twofold that's<00:26:20.880> that<00:26:21.059> you<00:26:21.299> need<00:26:21.480> to<00:26:21.600> authenticate 00:26:22.070 --> 00:26:22.080 align:start position:0% that's that you need to authenticate 00:26:22.080 --> 00:26:23.930 align:start position:0% that's that you need to authenticate with<00:26:22.260> signing<00:26:22.679> in<00:26:22.860> with<00:26:23.039> ethereum<00:26:23.520> and<00:26:23.760> we 00:26:23.930 --> 00:26:23.940 align:start position:0% with signing in with ethereum and we 00:26:23.940 --> 00:26:25.610 align:start position:0% with signing in with ethereum and we check<00:26:24.059> certain<00:26:24.360> properties<00:26:24.779> of<00:26:25.320> your<00:26:25.440> account 00:26:25.610 --> 00:26:25.620 align:start position:0% check certain properties of your account 00:26:25.620 --> 00:26:27.169 align:start position:0% check certain properties of your account so<00:26:25.919> like<00:26:26.159> a<00:26:26.220> fresh<00:26:26.340> account<00:26:26.580> is<00:26:26.820> not<00:26:26.940> going<00:26:27.059> to 00:26:27.169 --> 00:26:27.179 align:start position:0% so like a fresh account is not going to 00:26:27.179 --> 00:26:29.390 align:start position:0% so like a fresh account is not going to work<00:26:27.299> but<00:26:28.080> an<00:26:28.320> account<00:26:28.500> that<00:26:28.799> you've<00:26:28.980> got<00:26:29.100> even 00:26:29.390 --> 00:26:29.400 align:start position:0% work but an account that you've got even 00:26:29.400 --> 00:26:32.269 align:start position:0% work but an account that you've got even like<00:26:30.179> you've<00:26:30.659> sent<00:26:30.960> one<00:26:31.200> of<00:26:31.320> two<00:26:31.559> transactions 00:26:32.269 --> 00:26:32.279 align:start position:0% like you've sent one of two transactions 00:26:32.279 --> 00:26:34.850 align:start position:0% like you've sent one of two transactions uh<00:26:33.000> should<00:26:33.179> be<00:26:33.360> good<00:26:33.419> enough<00:26:33.600> that<00:26:34.140> in<00:26:34.740> the 00:26:34.850 --> 00:26:34.860 align:start position:0% uh should be good enough that in the 00:26:34.860 --> 00:26:37.130 align:start position:0% uh should be good enough that in the past<00:26:34.980> the<00:26:35.940> alternative<00:26:36.419> to<00:26:36.659> this<00:26:36.779> should<00:26:36.960> you 00:26:37.130 --> 00:26:37.140 align:start position:0% past the alternative to this should you 00:26:37.140 --> 00:26:38.690 align:start position:0% past the alternative to this should you not<00:26:37.260> want<00:26:37.380> to<00:26:37.500> use<00:26:37.740> sign<00:26:38.039> in<00:26:38.220> with<00:26:38.340> ethereum 00:26:38.690 --> 00:26:38.700 align:start position:0% not want to use sign in with ethereum 00:26:38.700 --> 00:26:40.549 align:start position:0% not want to use sign in with ethereum because<00:26:38.880> you<00:26:39.120> like<00:26:39.539> only<00:26:39.720> ethereum<00:26:40.140> adjacent 00:26:40.549 --> 00:26:40.559 align:start position:0% because you like only ethereum adjacent 00:26:40.559 --> 00:26:42.710 align:start position:0% because you like only ethereum adjacent or<00:26:40.740> something<00:26:40.860> like<00:26:41.039> that<00:26:41.159> is<00:26:41.400> GitHub<00:26:41.820> and 00:26:42.710 --> 00:26:42.720 align:start position:0% or something like that is GitHub and 00:26:42.720 --> 00:26:44.870 align:start position:0% or something like that is GitHub and there<00:26:42.900> we're<00:26:43.080> verifying<00:26:43.740> that<00:26:44.039> in<00:26:44.700> the<00:26:44.760> past 00:26:44.870 --> 00:26:44.880 align:start position:0% there we're verifying that in the past 00:26:44.880 --> 00:26:48.649 align:start position:0% there we're verifying that in the past you've<00:26:45.360> had<00:26:45.480> a<00:26:45.779> commit<00:26:46.200> to<00:26:46.880> uh<00:26:47.880> on<00:26:48.179> on<00:26:48.299> some 00:26:48.649 --> 00:26:48.659 align:start position:0% you've had a commit to uh on on some 00:26:48.659 --> 00:26:49.690 align:start position:0% you've had a commit to uh on on some repo 00:26:49.690 --> 00:26:49.700 align:start position:0% repo 00:26:49.700 --> 00:26:53.029 align:start position:0% repo the<00:26:50.700> simple<00:26:50.940> attacks<00:26:51.539> here<00:26:51.659> in<00:26:52.440> the<00:26:52.559> black<00:26:52.740> low 00:26:53.029 --> 00:26:53.039 align:start position:0% the simple attacks here in the black low 00:26:53.039 --> 00:26:54.890 align:start position:0% the simple attacks here in the black low orders<00:26:53.340> like<00:26:53.640> if<00:26:53.760> we<00:26:53.880> have 00:26:54.890 --> 00:26:54.900 align:start position:0% orders like if we have 00:26:54.900 --> 00:26:56.630 align:start position:0% orders like if we have some<00:26:55.380> people<00:26:55.500> contributing<00:26:56.039> five<00:26:56.220> times<00:26:56.460> or 00:26:56.630 --> 00:26:56.640 align:start position:0% some people contributing five times or 00:26:56.640 --> 00:26:58.669 align:start position:0% some people contributing five times or so<00:26:56.760> it<00:26:56.880> doesn't<00:26:57.000> really<00:26:57.179> matter 00:26:58.669 --> 00:26:58.679 align:start position:0% so it doesn't really matter 00:26:58.679 --> 00:27:00.710 align:start position:0% so it doesn't really matter um<00:26:58.799> because<00:26:59.279> they<00:26:59.580> just<00:26:59.760> mix<00:26:59.880> in<00:27:00.059> five<00:27:00.240> sets<00:27:00.659> of 00:27:00.710 --> 00:27:00.720 align:start position:0% um because they just mix in five sets of 00:27:00.720 --> 00:27:03.470 align:start position:0% um because they just mix in five sets of Secrets<00:27:01.080> but<00:27:01.860> if<00:27:02.100> we<00:27:02.220> extend<00:27:02.520> this<00:27:02.760> out<00:27:03.000> it 00:27:03.470 --> 00:27:03.480 align:start position:0% Secrets but if we extend this out it 00:27:03.480 --> 00:27:05.269 align:start position:0% Secrets but if we extend this out it does<00:27:03.659> start<00:27:03.960> to<00:27:04.140> matter<00:27:04.320> so<00:27:04.559> if<00:27:04.679> everyone<00:27:04.860> like 00:27:05.269 --> 00:27:05.279 align:start position:0% does start to matter so if everyone like 00:27:05.279 --> 00:27:06.950 align:start position:0% does start to matter so if everyone like if<00:27:05.520> everyone<00:27:05.820> manages<00:27:06.240> to<00:27:06.419> sublet<00:27:06.720> and 00:27:06.950 --> 00:27:06.960 align:start position:0% if everyone manages to sublet and 00:27:06.960 --> 00:27:08.330 align:start position:0% if everyone manages to sublet and everyone<00:27:07.080> was<00:27:07.380> the<00:27:07.559> same<00:27:07.679> person<00:27:07.799> replicated 00:27:08.330 --> 00:27:08.340 align:start position:0% everyone was the same person replicated 00:27:08.340 --> 00:27:10.430 align:start position:0% everyone was the same person replicated that<00:27:08.580> would<00:27:08.760> be<00:27:08.880> bad<00:27:09.000> so<00:27:09.659> we<00:27:09.900> don't<00:27:10.020> need<00:27:10.140> per 00:27:10.430 --> 00:27:10.440 align:start position:0% that would be bad so we don't need per 00:27:10.440 --> 00:27:14.360 align:start position:0% that would be bad so we don't need per flexible<00:27:10.740> prevention<00:27:11.340> just<00:27:11.640> moderately<00:27:12.120> so