WEBVTT Kind: captions Language: en 00:00:14.330 --> 00:00:17.779 align:start position:0% hi<00:00:15.330> guys<00:00:15.690> my<00:00:15.990> name<00:00:16.170> is<00:00:16.199> Patrick<00:00:16.650> McCrory<00:00:17.010> I'm<00:00:17.730> a 00:00:17.779 --> 00:00:17.789 align:start position:0% hi guys my name is Patrick McCrory I'm a 00:00:17.789 --> 00:00:20.569 align:start position:0% hi guys my name is Patrick McCrory I'm a researcher<00:00:18.599> at<00:00:18.720> UCL<00:00:19.259> and<00:00:19.859> I'm<00:00:20.009> gonna<00:00:20.130> talk<00:00:20.460> to 00:00:20.569 --> 00:00:20.579 align:start position:0% researcher at UCL and I'm gonna talk to 00:00:20.579 --> 00:00:21.859 align:start position:0% researcher at UCL and I'm gonna talk to you<00:00:20.640> about<00:00:20.699> some<00:00:20.939> work<00:00:21.089> I<00:00:21.210> did<00:00:21.390> last<00:00:21.599> summer 00:00:21.859 --> 00:00:21.869 align:start position:0% you about some work I did last summer 00:00:21.869 --> 00:00:24.229 align:start position:0% you about some work I did last summer while<00:00:22.289> I<00:00:22.320> was<00:00:22.529> doing<00:00:22.679> my<00:00:22.800> PhD<00:00:23.130> at<00:00:23.460> Newcastle<00:00:24.089> I 00:00:24.229 --> 00:00:24.239 align:start position:0% while I was doing my PhD at Newcastle I 00:00:24.239 --> 00:00:27.380 align:start position:0% while I was doing my PhD at Newcastle I did<00:00:24.900> it<00:00:24.989> in<00:00:25.140> Calabria<00:00:25.829> so<00:00:26.009> my<00:00:26.130> colleagues<00:00:26.640> Fong 00:00:27.380 --> 00:00:27.390 align:start position:0% did it in Calabria so my colleagues Fong 00:00:27.390 --> 00:00:30.470 align:start position:0% did it in Calabria so my colleagues Fong how<00:00:27.630> and<00:00:27.839> see<00:00:28.019> a<00:00:28.050> Mac<00:00:28.519> so<00:00:29.519> this<00:00:29.550> toast<00:00:30.119> gonna<00:00:30.359> be 00:00:30.470 --> 00:00:30.480 align:start position:0% how and see a Mac so this toast gonna be 00:00:30.480 --> 00:00:32.749 align:start position:0% how and see a Mac so this toast gonna be about<00:00:30.659> a<00:00:30.899> voting<00:00:31.289> but<00:00:31.890> before<00:00:32.250> I<00:00:32.279> really<00:00:32.610> get 00:00:32.749 --> 00:00:32.759 align:start position:0% about a voting but before I really get 00:00:32.759 --> 00:00:34.280 align:start position:0% about a voting but before I really get into<00:00:32.910> it<00:00:33.149> I<00:00:33.329> like<00:00:33.510> to<00:00:33.630> highlight<00:00:33.870> what 00:00:34.280 --> 00:00:34.290 align:start position:0% into it I like to highlight what 00:00:34.290 --> 00:00:35.900 align:start position:0% into it I like to highlight what researchers<00:00:34.859> tend<00:00:35.100> to<00:00:35.190> think<00:00:35.309> about<00:00:35.460> when<00:00:35.820> we 00:00:35.900 --> 00:00:35.910 align:start position:0% researchers tend to think about when we 00:00:35.910 --> 00:00:37.970 align:start position:0% researchers tend to think about when we say<00:00:36.090> e-voting<00:00:36.660> so<00:00:37.260> we<00:00:37.379> normally<00:00:37.530> think<00:00:37.739> about 00:00:37.970 --> 00:00:37.980 align:start position:0% say e-voting so we normally think about 00:00:37.980 --> 00:00:40.700 align:start position:0% say e-voting so we normally think about end-to-end<00:00:38.489> verifiable<00:00:39.449> systems<00:00:39.870> and<00:00:40.170> the 00:00:40.700 --> 00:00:40.710 align:start position:0% end-to-end verifiable systems and the 00:00:40.710 --> 00:00:42.380 align:start position:0% end-to-end verifiable systems and the break<00:00:40.920> that<00:00:41.129> down<00:00:41.370> the<00:00:41.609> idea<00:00:41.940> is<00:00:42.030> that<00:00:42.149> when<00:00:42.329> I 00:00:42.380 --> 00:00:42.390 align:start position:0% break that down the idea is that when I 00:00:42.390 --> 00:00:44.810 align:start position:0% break that down the idea is that when I go<00:00:42.539> to<00:00:42.570> a<00:00:42.690> polling<00:00:42.929> station<00:00:43.469> and<00:00:43.649> I<00:00:44.309> cast<00:00:44.609> my 00:00:44.810 --> 00:00:44.820 align:start position:0% go to a polling station and I cast my 00:00:44.820 --> 00:00:46.910 align:start position:0% go to a polling station and I cast my vote<00:00:44.850> I<00:00:45.359> did<00:00:45.870> have<00:00:45.960> confidence<00:00:46.469> that<00:00:46.679> Mary 00:00:46.910 --> 00:00:46.920 align:start position:0% vote I did have confidence that Mary 00:00:46.920 --> 00:00:49.310 align:start position:0% vote I did have confidence that Mary vote<00:00:47.190> has<00:00:47.429> been<00:00:47.460> cast<00:00:47.850> as<00:00:48.089> intended<00:00:48.420> when<00:00:49.289> I 00:00:49.310 --> 00:00:49.320 align:start position:0% vote has been cast as intended when I 00:00:49.320 --> 00:00:51.500 align:start position:0% vote has been cast as intended when I leave<00:00:49.589> the<00:00:49.739> polling<00:00:50.070> station<00:00:50.550> I<00:00:50.730> should<00:00:51.420> be 00:00:51.500 --> 00:00:51.510 align:start position:0% leave the polling station I should be 00:00:51.510 --> 00:00:52.549 align:start position:0% leave the polling station I should be able<00:00:51.570> to<00:00:51.660> look<00:00:51.780> at<00:00:51.929> this<00:00:52.079> public<00:00:52.440> bulletin 00:00:52.549 --> 00:00:52.559 align:start position:0% able to look at this public bulletin 00:00:52.559 --> 00:00:54.950 align:start position:0% able to look at this public bulletin board<00:00:53.039> and<00:00:53.309> verify<00:00:54.149> the<00:00:54.210> my<00:00:54.420> vote<00:00:54.660> has<00:00:54.929> been 00:00:54.950 --> 00:00:54.960 align:start position:0% board and verify the my vote has been 00:00:54.960 --> 00:00:56.869 align:start position:0% board and verify the my vote has been included<00:00:55.379> in<00:00:55.649> the<00:00:56.039> tally<00:00:56.249> we're<00:00:56.550> not<00:00:56.670> in<00:00:56.760> the 00:00:56.869 --> 00:00:56.879 align:start position:0% included in the tally we're not in the 00:00:56.879 --> 00:01:00.979 align:start position:0% included in the tally we're not in the tally<00:00:57.499> my<00:00:58.499> vote<00:00:58.769> has<00:00:58.890> been<00:00:58.920> cast<00:00:59.879> and<00:01:00.300> then 00:01:00.979 --> 00:01:00.989 align:start position:0% tally my vote has been cast and then 00:01:00.989 --> 00:01:03.200 align:start position:0% tally my vote has been cast and then after<00:01:01.499> the<00:01:01.649> election<00:01:02.159> I<00:01:02.339> should<00:01:02.879> be<00:01:02.969> able<00:01:03.120> to 00:01:03.200 --> 00:01:03.210 align:start position:0% after the election I should be able to 00:01:03.210 --> 00:01:06.020 align:start position:0% after the election I should be able to verify<00:01:03.480> that<00:01:03.870> my<00:01:03.989> vote<00:01:04.320> was<00:01:04.949> indeed<00:01:05.339> included 00:01:06.020 --> 00:01:06.030 align:start position:0% verify that my vote was indeed included 00:01:06.030 --> 00:01:08.000 align:start position:0% verify that my vote was indeed included in<00:01:06.120> the<00:01:06.240> tally<00:01:06.450> so<00:01:07.320> that<00:01:07.440> is<00:01:07.560> an<00:01:07.650> N<00:01:07.830> the<00:01:07.980> N 00:01:08.000 --> 00:01:08.010 align:start position:0% in the tally so that is an N the N 00:01:08.010 --> 00:01:10.670 align:start position:0% in the tally so that is an N the N verifiable<00:01:08.730> system<00:01:09.120> and<00:01:09.330> we<00:01:10.140> achieve<00:01:10.440> this 00:01:10.670 --> 00:01:10.680 align:start position:0% verifiable system and we achieve this 00:01:10.680 --> 00:01:12.800 align:start position:0% verifiable system and we achieve this system<00:01:11.130> we<00:01:11.430> normally<00:01:11.820> assume<00:01:12.090> the<00:01:12.240> existence 00:01:12.800 --> 00:01:12.810 align:start position:0% system we normally assume the existence 00:01:12.810 --> 00:01:14.450 align:start position:0% system we normally assume the existence of<00:01:12.990> his<00:01:13.500> public<00:01:13.860> bulletin<00:01:13.980> board<00:01:14.430> that 00:01:14.450 --> 00:01:14.460 align:start position:0% of his public bulletin board that 00:01:14.460 --> 00:01:17.270 align:start position:0% of his public bulletin board that everybody<00:01:14.940> can<00:01:15.180> see<00:01:15.410> but<00:01:16.410> for<00:01:16.620> the<00:01:16.710> past<00:01:16.890> I 00:01:17.270 --> 00:01:17.280 align:start position:0% everybody can see but for the past I 00:01:17.280 --> 00:01:19.490 align:start position:0% everybody can see but for the past I guess<00:01:17.400> 30<00:01:17.970> years<00:01:18.360> we've<00:01:18.990> not<00:01:19.170> really<00:01:19.380> been 00:01:19.490 --> 00:01:19.500 align:start position:0% guess 30 years we've not really been 00:01:19.500 --> 00:01:21.620 align:start position:0% guess 30 years we've not really been able<00:01:19.620> to<00:01:19.740> achieve<00:01:19.890> a<00:01:20.130> practical<00:01:20.820> public 00:01:21.620 --> 00:01:21.630 align:start position:0% able to achieve a practical public 00:01:21.630 --> 00:01:23.480 align:start position:0% able to achieve a practical public bulletin<00:01:21.990> board<00:01:22.200> the<00:01:22.710> best<00:01:22.950> we<00:01:23.130> have<00:01:23.340> is<00:01:23.460> a 00:01:23.480 --> 00:01:23.490 align:start position:0% bulletin board the best we have is a 00:01:23.490 --> 00:01:25.730 align:start position:0% bulletin board the best we have is a single<00:01:23.850> web<00:01:24.030> server<00:01:24.330> where<00:01:25.020> I<00:01:25.050> contact<00:01:25.650> the 00:01:25.730 --> 00:01:25.740 align:start position:0% single web server where I contact the 00:01:25.740 --> 00:01:28.400 align:start position:0% single web server where I contact the web<00:01:25.890> server<00:01:26.250> i<00:01:26.550> download<00:01:27.390> theater<00:01:27.780> and<00:01:27.960> i<00:01:28.290> have 00:01:28.400 --> 00:01:28.410 align:start position:0% web server i download theater and i have 00:01:28.410 --> 00:01:30.410 align:start position:0% web server i download theater and i have to<00:01:28.530> try<00:01:28.710> to<00:01:28.770> detect<00:01:29.190> that<00:01:29.640> that<00:01:29.790> web<00:01:30.000> server<00:01:30.300> is 00:01:30.410 --> 00:01:30.420 align:start position:0% to try to detect that that web server is 00:01:30.420 --> 00:01:32.600 align:start position:0% to try to detect that that web server is cheating<00:01:30.720> me<00:01:30.870> so<00:01:31.800> that's<00:01:31.920> not<00:01:32.160> really<00:01:32.310> good 00:01:32.600 --> 00:01:32.610 align:start position:0% cheating me so that's not really good 00:01:32.610 --> 00:01:34.730 align:start position:0% cheating me so that's not really good enough<00:01:32.700> so<00:01:33.510> now<00:01:33.660> people<00:01:33.900> are<00:01:34.080> thinking<00:01:34.110> okay 00:01:34.730 --> 00:01:34.740 align:start position:0% enough so now people are thinking okay 00:01:34.740 --> 00:01:36.610 align:start position:0% enough so now people are thinking okay can<00:01:35.010> we<00:01:35.130> use<00:01:35.280> the<00:01:35.430> blockchain<00:01:35.670> for<00:01:36.120> a<00:01:36.210> voting 00:01:36.610 --> 00:01:36.620 align:start position:0% can we use the blockchain for a voting 00:01:36.620 --> 00:01:38.900 align:start position:0% can we use the blockchain for a voting does<00:01:37.620> this<00:01:37.770> pervade<00:01:38.130> the<00:01:38.160> consistency 00:01:38.900 --> 00:01:38.910 align:start position:0% does this pervade the consistency 00:01:38.910 --> 00:01:41.150 align:start position:0% does this pervade the consistency property<00:01:39.210> that<00:01:39.510> we<00:01:39.660> want<00:01:39.840> and<00:01:40.290> I'm<00:01:40.890> going<00:01:41.100> to 00:01:41.150 --> 00:01:41.160 align:start position:0% property that we want and I'm going to 00:01:41.160 --> 00:01:43.700 align:start position:0% property that we want and I'm going to argue<00:01:41.340> potentially<00:01:42.120> and<00:01:43.110> I'm<00:01:43.350> going<00:01:43.500> to<00:01:43.590> say 00:01:43.700 --> 00:01:43.710 align:start position:0% argue potentially and I'm going to say 00:01:43.710 --> 00:01:44.840 align:start position:0% argue potentially and I'm going to say it's<00:01:43.860> probably<00:01:44.010> very<00:01:44.340> useful<00:01:44.700> for 00:01:44.840 --> 00:01:44.850 align:start position:0% it's probably very useful for 00:01:44.850 --> 00:01:46.640 align:start position:0% it's probably very useful for small-scale<00:01:45.150> accents<00:01:45.840> a<00:01:45.900> boardroom<00:01:46.200> voting 00:01:46.640 --> 00:01:46.650 align:start position:0% small-scale accents a boardroom voting 00:01:46.650 --> 00:01:48.890 align:start position:0% small-scale accents a boardroom voting because<00:01:47.460> it<00:01:47.760> does<00:01:47.910> pervade<00:01:48.210> this<00:01:48.360> consistency 00:01:48.890 --> 00:01:48.900 align:start position:0% because it does pervade this consistency 00:01:48.900 --> 00:01:51.320 align:start position:0% because it does pervade this consistency property<00:01:49.470> where<00:01:49.820> anybody<00:01:50.820> who<00:01:50.970> don't<00:01:51.150> lose 00:01:51.320 --> 00:01:51.330 align:start position:0% property where anybody who don't lose 00:01:51.330 --> 00:01:52.760 align:start position:0% property where anybody who don't lose the<00:01:51.480> blockchain<00:01:51.690> you<00:01:52.260> can<00:01:52.410> turn<00:01:52.530> over<00:01:52.710> the 00:01:52.760 --> 00:01:52.770 align:start position:0% the blockchain you can turn over the 00:01:52.770 --> 00:01:54.860 align:start position:0% the blockchain you can turn over the Genesis<00:01:53.190> block<00:01:53.310> and<00:01:53.700> you<00:01:54.210> can<00:01:54.360> verify<00:01:54.600> the 00:01:54.860 --> 00:01:54.870 align:start position:0% Genesis block and you can verify the 00:01:54.870 --> 00:01:57.290 align:start position:0% Genesis block and you can verify the entire<00:01:55.260> history<00:01:55.590> of<00:01:56.040> that<00:01:56.610> blockchain 00:01:57.290 --> 00:01:57.300 align:start position:0% entire history of that blockchain 00:01:57.300 --> 00:01:59.090 align:start position:0% entire history of that blockchain so<00:01:57.600> like<00:01:57.840> every<00:01:58.020> Bitcoin<00:01:58.260> transaction<00:01:59.010> in 00:01:59.090 --> 00:01:59.100 align:start position:0% so like every Bitcoin transaction in 00:01:59.100 --> 00:02:01.040 align:start position:0% so like every Bitcoin transaction in every<00:01:59.280> aetherium<00:01:59.820> transaction<00:02:00.450> and<00:02:00.690> I<00:02:00.990> don't 00:02:01.040 --> 00:02:01.050 align:start position:0% every aetherium transaction and I don't 00:02:01.050 --> 00:02:03.800 align:start position:0% every aetherium transaction and I don't need<00:02:01.230> to<00:02:01.380> trust<00:02:01.590> anyone<00:02:02.100> to<00:02:02.310> get<00:02:03.090> the<00:02:03.120> ensure 00:02:03.800 --> 00:02:03.810 align:start position:0% need to trust anyone to get the ensure 00:02:03.810 --> 00:02:04.940 align:start position:0% need to trust anyone to get the ensure that<00:02:03.930> I<00:02:03.990> have<00:02:04.020> a<00:02:04.140> consistent<00:02:04.650> view<00:02:04.770> of 00:02:04.940 --> 00:02:04.950 align:start position:0% that I have a consistent view of 00:02:04.950 --> 00:02:06.650 align:start position:0% that I have a consistent view of everybody<00:02:05.310> else<00:02:05.550> so<00:02:06.120> we<00:02:06.210> sort<00:02:06.360> of<00:02:06.420> think<00:02:06.570> is 00:02:06.650 --> 00:02:06.660 align:start position:0% everybody else so we sort of think is 00:02:06.660 --> 00:02:09.710 align:start position:0% everybody else so we sort of think is ideal<00:02:06.840> world<00:02:07.350> and<00:02:08.090> I'm<00:02:09.090> not<00:02:09.269> the<00:02:09.390> first<00:02:09.420> person 00:02:09.710 --> 00:02:09.720 align:start position:0% ideal world and I'm not the first person 00:02:09.720 --> 00:02:12.110 align:start position:0% ideal world and I'm not the first person to<00:02:10.080> notice<00:02:10.289> this<00:02:10.590> so<00:02:11.280> last<00:02:11.550> year<00:02:11.850> I<00:02:11.880> did<00:02:12.090> a 00:02:12.110 --> 00:02:12.120 align:start position:0% to notice this so last year I did a 00:02:12.120 --> 00:02:14.030 align:start position:0% to notice this so last year I did a Google<00:02:12.450> search<00:02:12.480> and<00:02:12.990> lots<00:02:13.530> of<00:02:13.650> people<00:02:13.830> were 00:02:14.030 --> 00:02:14.040 align:start position:0% Google search and lots of people were 00:02:14.040 --> 00:02:15.590 align:start position:0% Google search and lots of people were getting<00:02:14.160> excited<00:02:14.790> about<00:02:14.880> the<00:02:15.090> blockchain<00:02:15.330> and 00:02:15.590 --> 00:02:15.600 align:start position:0% getting excited about the blockchain and 00:02:15.600 --> 00:02:16.339 align:start position:0% getting excited about the blockchain and e-voting 00:02:16.339 --> 00:02:16.349 align:start position:0% e-voting 00:02:16.349 --> 00:02:18.709 align:start position:0% e-voting so<00:02:17.129> now<00:02:17.310> we<00:02:17.370> needed<00:02:17.609> to<00:02:17.790> say<00:02:17.969> it<00:02:17.999> okay<00:02:18.510> what 00:02:18.709 --> 00:02:18.719 align:start position:0% so now we needed to say it okay what 00:02:18.719 --> 00:02:20.239 align:start position:0% so now we needed to say it okay what blockchain<00:02:19.260> are<00:02:19.349> we<00:02:19.439> going<00:02:19.680> to<00:02:19.769> use 00:02:20.239 --> 00:02:20.249 align:start position:0% blockchain are we going to use 00:02:20.249 --> 00:02:23.149 align:start position:0% blockchain are we going to use what<00:02:21.030> about<00:02:21.150> Bitcoin<00:02:21.689> should<00:02:22.409> we<00:02:22.560> use<00:02:22.739> Bitcoin 00:02:23.149 --> 00:02:23.159 align:start position:0% what about Bitcoin should we use Bitcoin 00:02:23.159 --> 00:02:25.789 align:start position:0% what about Bitcoin should we use Bitcoin for<00:02:23.340> a<00:02:23.489> voting<00:02:23.849> and<00:02:24.120> I<00:02:24.749> want<00:02:24.989> to<00:02:25.049> summarize<00:02:25.409> and 00:02:25.789 --> 00:02:25.799 align:start position:0% for a voting and I want to summarize and 00:02:25.799 --> 00:02:27.500 align:start position:0% for a voting and I want to summarize and say<00:02:25.980> no<00:02:26.219> I<00:02:26.249> don't<00:02:26.549> think<00:02:26.609> bitcoins<00:02:27.180> are<00:02:27.329> very 00:02:27.500 --> 00:02:27.510 align:start position:0% say no I don't think bitcoins are very 00:02:27.510 --> 00:02:29.569 align:start position:0% say no I don't think bitcoins are very good<00:02:27.719> players<00:02:27.989> to<00:02:28.019> do<00:02:28.260> this<00:02:28.409> because<00:02:29.189> we<00:02:29.459> can 00:02:29.569 --> 00:02:29.579 align:start position:0% good players to do this because we can 00:02:29.579 --> 00:02:32.059 align:start position:0% good players to do this because we can only<00:02:29.730> store<00:02:30.030> 80<00:02:30.239> bytes<00:02:30.540> of<00:02:30.689> arbitrary<00:02:31.079> data<00:02:31.230> on 00:02:32.059 --> 00:02:32.069 align:start position:0% only store 80 bytes of arbitrary data on 00:02:32.069 --> 00:02:34.059 align:start position:0% only store 80 bytes of arbitrary data on Bitcoin<00:02:32.879> can<00:02:33.030> only<00:02:33.180> store<00:02:33.540> the<00:02:33.569> information 00:02:34.059 --> 00:02:34.069 align:start position:0% Bitcoin can only store the information 00:02:34.069 --> 00:02:37.030 align:start position:0% Bitcoin can only store the information it<00:02:35.069> cannot<00:02:35.400> verify<00:02:35.700> that<00:02:36.030> our<00:02:36.090> protocol<00:02:36.659> was 00:02:37.030 --> 00:02:37.040 align:start position:0% it cannot verify that our protocol was 00:02:37.040 --> 00:02:40.009 align:start position:0% it cannot verify that our protocol was correctly<00:02:38.040> executed<00:02:38.609> so<00:02:39.389> then<00:02:39.599> I'm<00:02:39.810> going<00:02:39.840> to 00:02:40.009 --> 00:02:40.019 align:start position:0% correctly executed so then I'm going to 00:02:40.019 --> 00:02:42.110 align:start position:0% correctly executed so then I'm going to go<00:02:40.170> okay<00:02:40.290> what<00:02:40.620> about<00:02:40.709> aetherium<00:02:41.189> and<00:02:41.730> I<00:02:42.060> don't 00:02:42.110 --> 00:02:42.120 align:start position:0% go okay what about aetherium and I don't 00:02:42.120 --> 00:02:43.429 align:start position:0% go okay what about aetherium and I don't really<00:02:42.450> need<00:02:42.599> a<00:02:42.659> preach<00:02:42.959> to<00:02:43.109> the<00:02:43.200> choir<00:02:43.319> here 00:02:43.429 --> 00:02:43.439 align:start position:0% really need a preach to the choir here 00:02:43.439 --> 00:02:45.500 align:start position:0% really need a preach to the choir here do<00:02:43.859> i<00:02:43.919> I<00:02:44.280> think<00:02:44.669> everybody<00:02:45.239> in<00:02:45.359> this<00:02:45.450> room 00:02:45.500 --> 00:02:45.510 align:start position:0% do i I think everybody in this room 00:02:45.510 --> 00:02:46.849 align:start position:0% do i I think everybody in this room understands<00:02:46.079> that<00:02:46.200> a<00:02:46.260> theorem<00:02:46.530> is<00:02:46.590> gonna<00:02:46.739> be 00:02:46.849 --> 00:02:46.859 align:start position:0% understands that a theorem is gonna be 00:02:46.859 --> 00:02:48.800 align:start position:0% understands that a theorem is gonna be amazing<00:02:47.129> and<00:02:47.489> when<00:02:48.120> I<00:02:48.150> made<00:02:48.359> this<00:02:48.510> slide<00:02:48.569> a 00:02:48.800 --> 00:02:48.810 align:start position:0% amazing and when I made this slide a 00:02:48.810 --> 00:02:50.119 align:start position:0% amazing and when I made this slide a theorem<00:02:49.290> was<00:02:49.379> worth<00:02:49.500> 20<00:02:49.709> billion<00:02:49.980> dollars 00:02:50.119 --> 00:02:50.129 align:start position:0% theorem was worth 20 billion dollars 00:02:50.129 --> 00:02:52.369 align:start position:0% theorem was worth 20 billion dollars it's<00:02:51.090> worth<00:02:51.209> more<00:02:51.540> now<00:02:51.599> I<00:02:51.780> don't<00:02:51.959> really<00:02:52.230> know 00:02:52.369 --> 00:02:52.379 align:start position:0% it's worth more now I don't really know 00:02:52.379 --> 00:02:54.140 align:start position:0% it's worth more now I don't really know how<00:02:52.530> much<00:02:52.680> it's<00:02:52.829> worth<00:02:52.859> now<00:02:53.189> but<00:02:53.790> the<00:02:53.879> point<00:02:54.120> of 00:02:54.140 --> 00:02:54.150 align:start position:0% how much it's worth now but the point of 00:02:54.150 --> 00:02:56.929 align:start position:0% how much it's worth now but the point of a<00:02:54.239> theorem<00:02:54.629> is<00:02:54.750> that<00:02:54.780> we<00:02:55.019> can<00:02:55.230> run<00:02:55.939> expressive 00:02:56.929 --> 00:02:56.939 align:start position:0% a theorem is that we can run expressive 00:02:56.939 --> 00:02:59.209 align:start position:0% a theorem is that we can run expressive but<00:02:57.120> bounded<00:02:57.599> programs<00:02:58.109> ie<00:02:58.650> new<00:02:58.919> the<00:02:59.040> gas 00:02:59.209 --> 00:02:59.219 align:start position:0% but bounded programs ie new the gas 00:02:59.219 --> 00:03:01.459 align:start position:0% but bounded programs ie new the gas metric<00:02:59.760> and<00:02:59.969> as<00:03:00.480> a<00:03:00.510> bit<00:03:00.719> like<00:03:00.870> a<00:03:00.959> computer<00:03:01.260> from 00:03:01.459 --> 00:03:01.469 align:start position:0% metric and as a bit like a computer from 00:03:01.469 --> 00:03:04.189 align:start position:0% metric and as a bit like a computer from the<00:03:01.620> 1970s<00:03:02.489> that<00:03:02.969> everybody<00:03:03.510> has<00:03:03.750> access<00:03:03.930> to 00:03:04.189 --> 00:03:04.199 align:start position:0% the 1970s that everybody has access to 00:03:04.199 --> 00:03:07.009 align:start position:0% the 1970s that everybody has access to it's<00:03:04.949> Sloane<00:03:05.250> as<00:03:05.459> expensive<00:03:06.090> but<00:03:06.780> we're<00:03:06.900> going 00:03:07.009 --> 00:03:07.019 align:start position:0% it's Sloane as expensive but we're going 00:03:07.019 --> 00:03:08.089 align:start position:0% it's Sloane as expensive but we're going to<00:03:07.079> get<00:03:07.230> away<00:03:07.349> and<00:03:07.560> we're<00:03:07.650> going<00:03:07.799> to<00:03:07.859> do<00:03:07.919> some 00:03:08.089 --> 00:03:08.099 align:start position:0% to get away and we're going to do some 00:03:08.099 --> 00:03:11.569 align:start position:0% to get away and we're going to do some avoiding<00:03:08.519> on<00:03:08.639> it<00:03:09.199> and<00:03:10.199> of<00:03:10.859> course<00:03:10.889> as<00:03:11.219> I<00:03:11.310> said 00:03:11.569 --> 00:03:11.579 align:start position:0% avoiding on it and of course as I said 00:03:11.579 --> 00:03:13.539 align:start position:0% avoiding on it and of course as I said this<00:03:11.699> votes<00:03:11.939> about<00:03:12.150> voting<00:03:12.449> and<00:03:12.750> not 00:03:13.539 --> 00:03:13.549 align:start position:0% this votes about voting and not 00:03:13.549 --> 00:03:17.420 align:start position:0% this votes about voting and not necessary<00:03:14.549> blockchains<00:03:15.090> so<00:03:16.010> last<00:03:17.010> who<00:03:17.280> this 00:03:17.420 --> 00:03:17.430 align:start position:0% necessary blockchains so last who this 00:03:17.430 --> 00:03:19.009 align:start position:0% necessary blockchains so last who this actually<00:03:17.760> it's<00:03:18.000> a<00:03:18.060> bit<00:03:18.150> of<00:03:18.239> a<00:03:18.299> story<00:03:18.540> behind<00:03:18.599> us 00:03:19.009 --> 00:03:19.019 align:start position:0% actually it's a bit of a story behind us 00:03:19.019 --> 00:03:21.289 align:start position:0% actually it's a bit of a story behind us here<00:03:19.230> okay<00:03:19.319> so<00:03:19.469> two<00:03:20.250> years<00:03:20.549> ago<00:03:20.819> at<00:03:21.000> end<00:03:21.209> of<00:03:21.239> the 00:03:21.289 --> 00:03:21.299 align:start position:0% here okay so two years ago at end of the 00:03:21.299 --> 00:03:23.360 align:start position:0% here okay so two years ago at end of the conference<00:03:21.689> and<00:03:22.189> everybody<00:03:23.189> was<00:03:23.310> really 00:03:23.360 --> 00:03:23.370 align:start position:0% conference and everybody was really 00:03:23.370 --> 00:03:24.920 align:start position:0% conference and everybody was really excited<00:03:24.030> about<00:03:24.090> a<00:03:24.209> theorem<00:03:24.599> and<00:03:24.720> smart 00:03:24.920 --> 00:03:24.930 align:start position:0% excited about a theorem and smart 00:03:24.930 --> 00:03:27.289 align:start position:0% excited about a theorem and smart contracts<00:03:25.409> and<00:03:25.769> I<00:03:26.669> was<00:03:26.790> drinking<00:03:26.939> a<00:03:27.090> pina 00:03:27.289 --> 00:03:27.299 align:start position:0% contracts and I was drinking a pina 00:03:27.299 --> 00:03:29.030 align:start position:0% contracts and I was drinking a pina colada<00:03:27.389> and<00:03:27.959> then<00:03:28.139> I<00:03:28.229> got<00:03:28.439> really<00:03:28.470> excited 00:03:29.030 --> 00:03:29.040 align:start position:0% colada and then I got really excited 00:03:29.040 --> 00:03:30.339 align:start position:0% colada and then I got really excited about<00:03:29.099> it 00:03:30.339 --> 00:03:30.349 align:start position:0% about it 00:03:30.349 --> 00:03:33.530 align:start position:0% about it so<00:03:31.349> when<00:03:31.620> I<00:03:31.650> go<00:03:31.889> back<00:03:31.919> to<00:03:32.250> the<00:03:32.340> England<00:03:32.729> I<00:03:33.030> went 00:03:33.530 --> 00:03:33.540 align:start position:0% so when I go back to the England I went 00:03:33.540 --> 00:03:35.749 align:start position:0% so when I go back to the England I went on<00:03:33.689> the<00:03:33.780> solidity<00:03:34.139> online<00:03:34.590> compiler<00:03:35.040> and<00:03:35.400> I 00:03:35.749 --> 00:03:35.759 align:start position:0% on the solidity online compiler and I 00:03:35.759 --> 00:03:37.670 align:start position:0% on the solidity online compiler and I noticed<00:03:36.150> that<00:03:36.299> this<00:03:36.449> voting<00:03:36.780> program<00:03:37.259> this 00:03:37.670 --> 00:03:37.680 align:start position:0% noticed that this voting program this 00:03:37.680 --> 00:03:39.199 align:start position:0% noticed that this voting program this was<00:03:37.859> like<00:03:37.979> there's<00:03:38.220> some<00:03:38.400> sample<00:03:38.849> code<00:03:39.000> and 00:03:39.199 --> 00:03:39.209 align:start position:0% was like there's some sample code and 00:03:39.209 --> 00:03:40.520 align:start position:0% was like there's some sample code and I'm<00:03:39.269> sure<00:03:39.419> most<00:03:39.659> people<00:03:39.780> in<00:03:40.049> this<00:03:40.169> room<00:03:40.349> have 00:03:40.520 --> 00:03:40.530 align:start position:0% I'm sure most people in this room have 00:03:40.530 --> 00:03:42.439 align:start position:0% I'm sure most people in this room have already<00:03:40.739> seen<00:03:41.009> it<00:03:41.159> but<00:03:41.849> the<00:03:41.939> idea<00:03:42.090> is<00:03:42.359> that 00:03:42.439 --> 00:03:42.449 align:start position:0% already seen it but the idea is that 00:03:42.449 --> 00:03:44.599 align:start position:0% already seen it but the idea is that there's<00:03:42.930> a<00:03:42.989> list<00:03:43.169> of<00:03:43.290> proposals<00:03:43.620> and<00:03:44.370> when<00:03:44.579> I 00:03:44.599 --> 00:03:44.609 align:start position:0% there's a list of proposals and when I 00:03:44.609 --> 00:03:46.670 align:start position:0% there's a list of proposals and when I want<00:03:44.819> to<00:03:44.879> cast<00:03:45.090> my<00:03:45.329> vote<00:03:45.359> I<00:03:45.870> call<00:03:46.379> the<00:03:46.500> vote 00:03:46.670 --> 00:03:46.680 align:start position:0% want to cast my vote I call the vote 00:03:46.680 --> 00:03:48.080 align:start position:0% want to cast my vote I call the vote function<00:03:47.159> and<00:03:47.310> I<00:03:47.370> say<00:03:47.549> I<00:03:47.579> want<00:03:47.609> to<00:03:47.790> vote<00:03:47.909> for 00:03:48.080 --> 00:03:48.090 align:start position:0% function and I say I want to vote for 00:03:48.090 --> 00:03:50.270 align:start position:0% function and I say I want to vote for this<00:03:48.180> proposal<00:03:48.569> now<00:03:49.379> the<00:03:49.439> guarantee<00:03:50.009> voter 00:03:50.270 --> 00:03:50.280 align:start position:0% this proposal now the guarantee voter 00:03:50.280 --> 00:03:52.819 align:start position:0% this proposal now the guarantee voter privacy<00:03:50.909> and<00:03:51.030> this<00:03:51.120> program<00:03:51.659> the<00:03:52.229> assumption 00:03:52.819 --> 00:03:52.829 align:start position:0% privacy and this program the assumption 00:03:52.829 --> 00:03:54.710 align:start position:0% privacy and this program the assumption is<00:03:52.949> that<00:03:52.979> we<00:03:53.189> cannot<00:03:53.489> link<00:03:53.849> of<00:03:54.120> orders 00:03:54.710 --> 00:03:54.720 align:start position:0% is that we cannot link of orders 00:03:54.720 --> 00:03:56.780 align:start position:0% is that we cannot link of orders real-world<00:03:55.139> identity<00:03:55.680> to<00:03:56.220> their<00:03:56.400> aetherium 00:03:56.780 --> 00:03:56.790 align:start position:0% real-world identity to their aetherium 00:03:56.790 --> 00:03:59.089 align:start position:0% real-world identity to their aetherium account<00:03:57.090> because<00:03:57.840> if<00:03:57.959> you<00:03:58.049> can<00:03:58.349> then<00:03:58.949> you<00:03:59.069> can 00:03:59.089 --> 00:03:59.099 align:start position:0% account because if you can then you can 00:03:59.099 --> 00:04:01.159 align:start position:0% account because if you can then you can see<00:03:59.400> how<00:03:59.549> somebody<00:03:59.819> voted<00:04:00.180> because<00:04:00.870> the<00:04:01.019> food 00:04:01.159 --> 00:04:01.169 align:start position:0% see how somebody voted because the food 00:04:01.169 --> 00:04:03.559 align:start position:0% see how somebody voted because the food is<00:04:01.290> in<00:04:01.409> plain<00:04:01.590> text<00:04:02.069> so<00:04:02.280> I<00:04:02.939> wanted<00:04:03.269> to<00:04:03.329> see<00:04:03.509> if 00:04:03.559 --> 00:04:03.569 align:start position:0% is in plain text so I wanted to see if 00:04:03.569 --> 00:04:05.599 align:start position:0% is in plain text so I wanted to see if we<00:04:03.659> can<00:04:03.810> do<00:04:03.900> something<00:04:04.139> better<00:04:04.379> can<00:04:05.370> we<00:04:05.459> build 00:04:05.599 --> 00:04:05.609 align:start position:0% we can do something better can we build 00:04:05.609 --> 00:04:07.550 align:start position:0% we can do something better can we build a<00:04:05.759> smart<00:04:06.030> contract<00:04:06.269> I<00:04:06.629> can<00:04:06.780> guarantee<00:04:07.169> voter 00:04:07.550 --> 00:04:07.560 align:start position:0% a smart contract I can guarantee voter 00:04:07.560 --> 00:04:10.309 align:start position:0% a smart contract I can guarantee voter privacy<00:04:08.180> and<00:04:09.180> there's<00:04:09.659> two<00:04:09.840> different<00:04:10.049> ways 00:04:10.309 --> 00:04:10.319 align:start position:0% privacy and there's two different ways 00:04:10.319 --> 00:04:12.080 align:start position:0% privacy and there's two different ways to<00:04:10.530> approach<00:04:10.709> this<00:04:11.009> one<00:04:11.669> is<00:04:11.849> Blayne 00:04:12.080 --> 00:04:12.090 align:start position:0% to approach this one is Blayne 00:04:12.090 --> 00:04:14.390 align:start position:0% to approach this one is Blayne signatures<00:04:12.689> and<00:04:12.930> the<00:04:13.500> other<00:04:13.620> one<00:04:13.859> is<00:04:14.099> where<00:04:14.370> I 00:04:14.390 --> 00:04:14.400 align:start position:0% signatures and the other one is where I 00:04:14.400 --> 00:04:17.360 align:start position:0% signatures and the other one is where I can<00:04:14.810> encrypt<00:04:15.810> my<00:04:15.989> vote<00:04:16.289> under<00:04:16.560> a<00:04:16.949> well-known 00:04:17.360 --> 00:04:17.370 align:start position:0% can encrypt my vote under a well-known 00:04:17.370 --> 00:04:19.459 align:start position:0% can encrypt my vote under a well-known public<00:04:17.639> key<00:04:18.060> I<00:04:18.299> could<00:04:18.659> store<00:04:19.109> that<00:04:19.169> on<00:04:19.380> the 00:04:19.459 --> 00:04:19.469 align:start position:0% public key I could store that on the 00:04:19.469 --> 00:04:21.649 align:start position:0% public key I could store that on the blockchain<00:04:19.709> and<00:04:20.130> then<00:04:20.759> I<00:04:20.849> could<00:04:21.030> shut<00:04:21.209> some<00:04:21.509> I 00:04:21.649 --> 00:04:21.659 align:start position:0% blockchain and then I could shut some I 00:04:21.659 --> 00:04:23.270 align:start position:0% blockchain and then I could shut some I then<00:04:21.930> there<00:04:22.109> could<00:04:22.229> be<00:04:22.289> an<00:04:22.409> Italian<00:04:22.800> authority 00:04:23.270 --> 00:04:23.280 align:start position:0% then there could be an Italian authority 00:04:23.280 --> 00:04:25.760 align:start position:0% then there could be an Italian authority who<00:04:23.729> after<00:04:24.150> the<00:04:24.270> election<00:04:24.779> will<00:04:25.199> decrypt<00:04:25.560> the 00:04:25.760 --> 00:04:25.770 align:start position:0% who after the election will decrypt the 00:04:25.770 --> 00:04:27.980 align:start position:0% who after the election will decrypt the vote<00:04:25.949> and<00:04:26.219> reveal<00:04:26.610> the<00:04:26.760> tally<00:04:27.000> but<00:04:27.750> both<00:04:27.960> of 00:04:27.980 --> 00:04:27.990 align:start position:0% vote and reveal the tally but both of 00:04:27.990 --> 00:04:30.250 align:start position:0% vote and reveal the tally but both of those<00:04:28.169> approaches<00:04:28.710> rely<00:04:28.860> on<00:04:28.979> some<00:04:29.370> type<00:04:29.610> of<00:04:29.639> a 00:04:30.250 --> 00:04:30.260 align:start position:0% those approaches rely on some type of a 00:04:30.260 --> 00:04:32.390 align:start position:0% those approaches rely on some type of a and<00:04:31.260> I<00:04:31.320> wanted<00:04:31.530> to<00:04:31.590> follow<00:04:31.830> the<00:04:31.920> example<00:04:32.250> of 00:04:32.390 --> 00:04:32.400 align:start position:0% and I wanted to follow the example of 00:04:32.400 --> 00:04:34.670 align:start position:0% and I wanted to follow the example of cryptocurrencies<00:04:32.910> can<00:04:33.900> we<00:04:33.990> remove<00:04:34.320> the<00:04:34.500> need 00:04:34.670 --> 00:04:34.680 align:start position:0% cryptocurrencies can we remove the need 00:04:34.680 --> 00:04:36.520 align:start position:0% cryptocurrencies can we remove the need for<00:04:34.710> an<00:04:35.010> Italian<00:04:35.550> Authority<00:04:35.970> and<00:04:36.120> an<00:04:36.210> election 00:04:36.520 --> 00:04:36.530 align:start position:0% for an Italian Authority and an election 00:04:36.530 --> 00:04:38.810 align:start position:0% for an Italian Authority and an election and<00:04:37.530> can<00:04:37.650> we<00:04:37.770> do<00:04:37.920> it<00:04:38.010> in<00:04:38.070> such<00:04:38.250> a<00:04:38.310> way<00:04:38.460> where<00:04:38.760> a 00:04:38.810 --> 00:04:38.820 align:start position:0% and can we do it in such a way where a 00:04:38.820 --> 00:04:41.180 align:start position:0% and can we do it in such a way where a voter<00:04:39.060> is<00:04:39.390> in<00:04:39.840> control<00:04:40.170> of<00:04:40.260> the<00:04:40.410> room<00:04:40.590> privacy 00:04:41.180 --> 00:04:41.190 align:start position:0% voter is in control of the room privacy 00:04:41.190 --> 00:04:43.910 align:start position:0% voter is in control of the room privacy and<00:04:41.780> there's<00:04:42.780> brought<00:04:43.020> me<00:04:43.140> to<00:04:43.290> self<00:04:43.530> tallying 00:04:43.910 --> 00:04:43.920 align:start position:0% and there's brought me to self tallying 00:04:43.920 --> 00:04:46.070 align:start position:0% and there's brought me to self tallying elections<00:04:44.400> which<00:04:45.120> was<00:04:45.300> first<00:04:45.540> made<00:04:45.810> back<00:04:46.050> in 00:04:46.070 --> 00:04:46.080 align:start position:0% elections which was first made back in 00:04:46.080 --> 00:04:48.890 align:start position:0% elections which was first made back in 2002<00:04:46.980> and<00:04:47.190> these<00:04:47.910> elections<00:04:48.480> have<00:04:48.630> three 00:04:48.890 --> 00:04:48.900 align:start position:0% 2002 and these elections have three 00:04:48.900 --> 00:04:51.470 align:start position:0% 2002 and these elections have three different<00:04:49.290> properties<00:04:49.550> first<00:04:50.550> is<00:04:50.910> perfect 00:04:51.470 --> 00:04:51.480 align:start position:0% different properties first is perfect 00:04:51.480 --> 00:04:54.140 align:start position:0% different properties first is perfect ballot<00:04:51.780> secrecy<00:04:52.290> a<00:04:52.470> voters<00:04:53.250> privacy<00:04:53.790> can<00:04:53.940> only 00:04:54.140 --> 00:04:54.150 align:start position:0% ballot secrecy a voters privacy can only 00:04:54.150 --> 00:04:56.060 align:start position:0% ballot secrecy a voters privacy can only be<00:04:54.360> breached<00:04:54.660> by<00:04:54.990> a<00:04:55.020> full<00:04:55.320> collusion<00:04:55.860> of<00:04:55.950> all 00:04:56.060 --> 00:04:56.070 align:start position:0% be breached by a full collusion of all 00:04:56.070 --> 00:04:58.700 align:start position:0% be breached by a full collusion of all other<00:04:56.280> voters<00:04:56.610> and<00:04:56.880> is<00:04:57.690> also<00:04:57.870> self<00:04:58.230> tallying 00:04:58.700 --> 00:04:58.710 align:start position:0% other voters and is also self tallying 00:04:58.710 --> 00:05:01.760 align:start position:0% other voters and is also self tallying so<00:04:59.370> after<00:04:59.700> the<00:04:59.790> election<00:05:00.350> anybody<00:05:01.350> can<00:05:01.560> count 00:05:01.760 --> 00:05:01.770 align:start position:0% so after the election anybody can count 00:05:01.770 --> 00:05:03.320 align:start position:0% so after the election anybody can count the<00:05:01.920> votes<00:05:02.100> we<00:05:02.640> don't<00:05:02.670> have<00:05:02.940> to<00:05:03.060> rely<00:05:03.300> on 00:05:03.320 --> 00:05:03.330 align:start position:0% the votes we don't have to rely on 00:05:03.330 --> 00:05:06.020 align:start position:0% the votes we don't have to rely on anybody<00:05:03.780> to<00:05:03.930> do<00:05:04.050> that<00:05:04.080> for<00:05:04.470> us<00:05:04.680> honest<00:05:05.610> dispute 00:05:06.020 --> 00:05:06.030 align:start position:0% anybody to do that for us honest dispute 00:05:06.030 --> 00:05:08.240 align:start position:0% anybody to do that for us honest dispute free<00:05:06.270> as<00:05:06.510> then<00:05:07.350> if<00:05:07.470> you<00:05:07.560> give<00:05:07.740> me<00:05:07.830> the<00:05:07.950> election 00:05:08.240 --> 00:05:08.250 align:start position:0% free as then if you give me the election 00:05:08.250 --> 00:05:11.270 align:start position:0% free as then if you give me the election transcript<00:05:09.000> I<00:05:09.180> can<00:05:09.660> verify<00:05:09.900> myself<00:05:10.650> that<00:05:11.160> the 00:05:11.270 --> 00:05:11.280 align:start position:0% transcript I can verify myself that the 00:05:11.280 --> 00:05:13.100 align:start position:0% transcript I can verify myself that the election<00:05:11.610> was<00:05:11.700> run<00:05:11.910> correctly<00:05:12.420> or<00:05:12.600> at<00:05:12.960> least 00:05:13.100 --> 00:05:13.110 align:start position:0% election was run correctly or at least 00:05:13.110 --> 00:05:15.350 align:start position:0% election was run correctly or at least the<00:05:13.200> protocol<00:05:13.620> but<00:05:14.340> my<00:05:14.460> disclaimer<00:05:14.880> is<00:05:15.180> that 00:05:15.350 --> 00:05:15.360 align:start position:0% the protocol but my disclaimer is that 00:05:15.360 --> 00:05:17.030 align:start position:0% the protocol but my disclaimer is that this<00:05:15.510> protocol<00:05:15.990> is<00:05:16.170> not<00:05:16.200> and<00:05:16.650> -<00:05:16.890> and 00:05:17.030 --> 00:05:17.040 align:start position:0% this protocol is not and - and 00:05:17.040 --> 00:05:18.800 align:start position:0% this protocol is not and - and verifiable<00:05:17.670> as<00:05:17.850> I<00:05:18.300> mentioned<00:05:18.660> at<00:05:18.720> the<00:05:18.750> very 00:05:18.800 --> 00:05:18.810 align:start position:0% verifiable as I mentioned at the very 00:05:18.810 --> 00:05:20.600 align:start position:0% verifiable as I mentioned at the very beginning<00:05:19.380> because<00:05:19.980> in<00:05:20.220> an<00:05:20.310> end-to-end 00:05:20.600 --> 00:05:20.610 align:start position:0% beginning because in an end-to-end 00:05:20.610 --> 00:05:23.420 align:start position:0% beginning because in an end-to-end verifiable<00:05:21.360> is<00:05:21.480> a<00:05:21.600> system<00:05:22.230> we<00:05:22.680> also<00:05:22.950> assume 00:05:23.420 --> 00:05:23.430 align:start position:0% verifiable is a system we also assume 00:05:23.430 --> 00:05:25.610 align:start position:0% verifiable is a system we also assume the<00:05:23.550> voting<00:05:23.850> machine<00:05:24.120> cannot<00:05:24.390> be<00:05:24.540> trusted<00:05:24.750> but 00:05:25.610 --> 00:05:25.620 align:start position:0% the voting machine cannot be trusted but 00:05:25.620 --> 00:05:27.440 align:start position:0% the voting machine cannot be trusted but this<00:05:25.800> is<00:05:25.920> a<00:05:25.950> fully<00:05:26.250> decentralized<00:05:26.520> voting 00:05:27.440 --> 00:05:27.450 align:start position:0% this is a fully decentralized voting 00:05:27.450 --> 00:05:29.780 align:start position:0% this is a fully decentralized voting protocol<00:05:27.900> we<00:05:28.650> have<00:05:28.770> no<00:05:28.950> central<00:05:29.340> authority<00:05:29.430> to 00:05:29.780 --> 00:05:29.790 align:start position:0% protocol we have no central authority to 00:05:29.790 --> 00:05:31.940 align:start position:0% protocol we have no central authority to provide<00:05:30.000> hardware<00:05:30.480> for<00:05:30.690> us<00:05:30.780> so<00:05:31.620> we<00:05:31.710> have<00:05:31.830> to 00:05:31.940 --> 00:05:31.950 align:start position:0% provide hardware for us so we have to 00:05:31.950 --> 00:05:33.440 align:start position:0% provide hardware for us so we have to assume<00:05:32.190> the<00:05:32.340> voting<00:05:32.610> machine<00:05:32.850> is<00:05:33.030> trustworthy 00:05:33.440 --> 00:05:33.450 align:start position:0% assume the voting machine is trustworthy 00:05:33.450 --> 00:05:35.210 align:start position:0% assume the voting machine is trustworthy and<00:05:33.870> I<00:05:34.470> think<00:05:34.710> that's<00:05:34.860> a<00:05:34.919> reasonable 00:05:35.210 --> 00:05:35.220 align:start position:0% and I think that's a reasonable 00:05:35.220 --> 00:05:37.490 align:start position:0% and I think that's a reasonable assumption<00:05:35.669> because<00:05:36.000> if<00:05:36.390> you<00:05:36.570> break<00:05:36.900> my<00:05:36.930> if 00:05:37.490 --> 00:05:37.500 align:start position:0% assumption because if you break my if 00:05:37.500 --> 00:05:38.450 align:start position:0% assumption because if you break my if you<00:05:37.560> hack<00:05:37.770> my<00:05:37.919> machine 00:05:38.450 --> 00:05:38.460 align:start position:0% you hack my machine 00:05:38.460 --> 00:05:40.040 align:start position:0% you hack my machine you're<00:05:38.820> probably<00:05:39.030> gonna<00:05:39.300> steal<00:05:39.540> all<00:05:39.570> my<00:05:39.720> coins 00:05:40.040 --> 00:05:40.050 align:start position:0% you're probably gonna steal all my coins 00:05:40.050 --> 00:05:42.560 align:start position:0% you're probably gonna steal all my coins so<00:05:40.980> have<00:05:41.100> an<00:05:41.190> incentive<00:05:41.730> that<00:05:41.760> do<00:05:42.000> my<00:05:42.150> best<00:05:42.360> to 00:05:42.560 --> 00:05:42.570 align:start position:0% so have an incentive that do my best to 00:05:42.570 --> 00:05:45.740 align:start position:0% so have an incentive that do my best to keep<00:05:42.720> my<00:05:42.780> machine<00:05:43.169> somewhat<00:05:43.830> trustworthy<00:05:44.750> but 00:05:45.740 --> 00:05:45.750 align:start position:0% keep my machine somewhat trustworthy but 00:05:45.750 --> 00:05:47.930 align:start position:0% keep my machine somewhat trustworthy but these<00:05:45.930> protocols<00:05:46.530> have<00:05:47.340> had<00:05:47.580> a<00:05:47.610> short-lived 00:05:47.930 --> 00:05:47.940 align:start position:0% these protocols have had a short-lived 00:05:47.940 --> 00:05:50.240 align:start position:0% these protocols have had a short-lived history<00:05:48.510> there<00:05:49.230> has<00:05:49.350> never<00:05:49.500> been<00:05:49.620> a<00:05:49.800> practical 00:05:50.240 --> 00:05:50.250 align:start position:0% history there has never been a practical 00:05:50.250 --> 00:05:51.770 align:start position:0% history there has never been a practical implementation<00:05:50.490> of<00:05:51.150> a<00:05:51.210> self<00:05:51.419> Italian 00:05:51.770 --> 00:05:51.780 align:start position:0% implementation of a self Italian 00:05:51.780 --> 00:05:53.930 align:start position:0% implementation of a self Italian election<00:05:52.230> because<00:05:53.010> one<00:05:53.220> it<00:05:53.490> requires<00:05:53.820> an 00:05:53.930 --> 00:05:53.940 align:start position:0% election because one it requires an 00:05:53.940 --> 00:05:56.000 align:start position:0% election because one it requires an authenticated<00:05:54.510> broadcast<00:05:55.050> channel<00:05:55.440> where 00:05:56.000 --> 00:05:56.010 align:start position:0% authenticated broadcast channel where 00:05:56.010 --> 00:05:58.010 align:start position:0% authenticated broadcast channel where everybody<00:05:56.460> can<00:05:56.669> communicate<00:05:57.180> and<00:05:57.450> it's<00:05:57.870> also 00:05:58.010 --> 00:05:58.020 align:start position:0% everybody can communicate and it's also 00:05:58.020 --> 00:05:59.570 align:start position:0% everybody can communicate and it's also very<00:05:58.260> beneficial<00:05:58.590> to<00:05:59.070> have<00:05:59.160> a<00:05:59.250> public 00:05:59.570 --> 00:05:59.580 align:start position:0% very beneficial to have a public 00:05:59.580 --> 00:06:01.430 align:start position:0% very beneficial to have a public bulletin<00:05:59.669> board<00:06:00.120> to<00:06:00.660> store<00:06:00.930> the<00:06:01.050> election 00:06:01.430 --> 00:06:01.440 align:start position:0% bulletin board to store the election 00:06:01.440 --> 00:06:04.220 align:start position:0% bulletin board to store the election transcript<00:06:01.980> and<00:06:02.910> these<00:06:03.270> protocols<00:06:03.600> also<00:06:04.020> have 00:06:04.220 --> 00:06:04.230 align:start position:0% transcript and these protocols also have 00:06:04.230 --> 00:06:06.980 align:start position:0% transcript and these protocols also have two<00:06:04.470> other<00:06:04.650> issues<00:06:05.100> a<00:06:05.370> single<00:06:06.330> voter<00:06:06.510> can<00:06:06.750> stop 00:06:06.980 --> 00:06:06.990 align:start position:0% two other issues a single voter can stop 00:06:06.990 --> 00:06:10.070 align:start position:0% two other issues a single voter can stop the<00:06:07.140> entire<00:06:07.440> election<00:06:08.510> so<00:06:09.510> they<00:06:09.660> don't<00:06:09.840> cast 00:06:10.070 --> 00:06:10.080 align:start position:0% the entire election so they don't cast 00:06:10.080 --> 00:06:12.409 align:start position:0% the entire election so they don't cast their<00:06:10.260> vote<00:06:10.470> we<00:06:11.010> don't<00:06:11.220> get<00:06:11.400> the<00:06:11.520> tally<00:06:11.730> they 00:06:12.409 --> 00:06:12.419 align:start position:0% their vote we don't get the tally they 00:06:12.419 --> 00:06:14.240 align:start position:0% their vote we don't get the tally they also<00:06:12.630> have<00:06:12.810> an<00:06:12.900> adoptive<00:06:13.380> issue<00:06:13.530> where<00:06:14.130> the 00:06:14.240 --> 00:06:14.250 align:start position:0% also have an adoptive issue where the 00:06:14.250 --> 00:06:15.980 align:start position:0% also have an adoptive issue where the final<00:06:14.610> voter<00:06:14.790> can<00:06:15.060> view<00:06:15.300> the<00:06:15.390> tally<00:06:15.630> before 00:06:15.980 --> 00:06:15.990 align:start position:0% final voter can view the tally before 00:06:15.990 --> 00:06:19.610 align:start position:0% final voter can view the tally before everybody<00:06:16.470> else<00:06:17.570> but<00:06:18.570> now<00:06:18.780> I<00:06:18.810> thought<00:06:19.230> okay 00:06:19.610 --> 00:06:19.620 align:start position:0% everybody else but now I thought okay 00:06:19.620 --> 00:06:21.380 align:start position:0% everybody else but now I thought okay can<00:06:20.070> we<00:06:20.100> combine<00:06:20.550> these<00:06:20.760> self-tanning 00:06:21.380 --> 00:06:21.390 align:start position:0% can we combine these self-tanning 00:06:21.390 --> 00:06:24.050 align:start position:0% can we combine these self-tanning elections<00:06:22.020> with<00:06:22.260> the<00:06:22.320> blockchain<00:06:22.640> so<00:06:23.640> I<00:06:23.669> built 00:06:24.050 --> 00:06:24.060 align:start position:0% elections with the blockchain so I built 00:06:24.060 --> 00:06:25.850 align:start position:0% elections with the blockchain so I built the<00:06:24.180> voting<00:06:24.450> protocol<00:06:24.870> as<00:06:24.990> a<00:06:25.110> smart<00:06:25.350> contract 00:06:25.850 --> 00:06:25.860 align:start position:0% the voting protocol as a smart contract 00:06:25.860 --> 00:06:28.040 align:start position:0% the voting protocol as a smart contract and<00:06:26.130> as<00:06:26.790> I<00:06:26.910> mentioned<00:06:27.330> most<00:06:27.390> beautiful<00:06:27.840> of<00:06:27.900> it 00:06:28.040 --> 00:06:28.050 align:start position:0% and as I mentioned most beautiful of it 00:06:28.050 --> 00:06:30.170 align:start position:0% and as I mentioned most beautiful of it what's<00:06:28.350> beautiful<00:06:28.560> about<00:06:28.890> aetherium<00:06:29.400> is<00:06:29.669> that 00:06:30.170 --> 00:06:30.180 align:start position:0% what's beautiful about aetherium is that 00:06:30.180 --> 00:06:31.670 align:start position:0% what's beautiful about aetherium is that it<00:06:30.300> can<00:06:30.419> enforce<00:06:30.780> the<00:06:30.960> voting<00:06:31.230> protocols 00:06:31.670 --> 00:06:31.680 align:start position:0% it can enforce the voting protocols 00:06:31.680 --> 00:06:34.070 align:start position:0% it can enforce the voting protocols correct<00:06:32.040> execution<00:06:32.370> and<00:06:33.210> we<00:06:33.600> can<00:06:33.750> also<00:06:33.930> have 00:06:34.070 --> 00:06:34.080 align:start position:0% correct execution and we can also have 00:06:34.080 --> 00:06:35.630 align:start position:0% correct execution and we can also have this<00:06:34.290> incentive<00:06:34.680> that<00:06:34.980> sort<00:06:35.190> of<00:06:35.250> the<00:06:35.310> crypto 00:06:35.630 --> 00:06:35.640 align:start position:0% this incentive that sort of the crypto 00:06:35.640 --> 00:06:37.640 align:start position:0% this incentive that sort of the crypto economic<00:06:36.180> security<00:06:36.630> engineering<00:06:36.990> philosophy 00:06:37.640 --> 00:06:37.650 align:start position:0% economic security engineering philosophy 00:06:37.650 --> 00:06:40.430 align:start position:0% economic security engineering philosophy where<00:06:38.400> when<00:06:38.880> you<00:06:39.000> register<00:06:39.810> for<00:06:39.990> the<00:06:40.050> election 00:06:40.430 --> 00:06:40.440 align:start position:0% where when you register for the election 00:06:40.440 --> 00:06:42.170 align:start position:0% where when you register for the election you<00:06:40.500> leave<00:06:40.650> a<00:06:40.680> deposit<00:06:41.190> and<00:06:41.370> when<00:06:41.850> you<00:06:41.940> cast 00:06:42.170 --> 00:06:42.180 align:start position:0% you leave a deposit and when you cast 00:06:42.180 --> 00:06:44.210 align:start position:0% you leave a deposit and when you cast your<00:06:42.360> vote<00:06:42.600> you<00:06:43.110> get<00:06:43.260> your<00:06:43.440> deposit 00:06:44.210 --> 00:06:44.220 align:start position:0% your vote you get your deposit 00:06:44.220 --> 00:06:45.770 align:start position:0% your vote you get your deposit so<00:06:44.610> now<00:06:44.760> we<00:06:44.820> can<00:06:45.000> access<00:06:45.120> some<00:06:45.450> Tiffin's 00:06:45.770 --> 00:06:45.780 align:start position:0% so now we can access some Tiffin's 00:06:45.780 --> 00:06:48.490 align:start position:0% so now we can access some Tiffin's incentive<00:06:46.440> for<00:06:46.590> people<00:06:46.740> to<00:06:46.860> participate<00:06:47.040> and 00:06:48.490 --> 00:06:48.500 align:start position:0% incentive for people to participate and 00:06:48.500 --> 00:06:50.630 align:start position:0% incentive for people to participate and there's<00:06:49.500> three<00:06:49.710> different<00:06:49.860> self<00:06:50.280> tallying 00:06:50.630 --> 00:06:50.640 align:start position:0% there's three different self tallying 00:06:50.640 --> 00:06:52.880 align:start position:0% there's three different self tallying protocols<00:06:51.090> we<00:06:51.210> could<00:06:51.360> have<00:06:51.450> chosen<00:06:51.890> my 00:06:52.880 --> 00:06:52.890 align:start position:0% protocols we could have chosen my 00:06:52.890 --> 00:06:54.530 align:start position:0% protocols we could have chosen my disclaimer<00:06:53.340> is<00:06:53.580> that<00:06:53.730> we<00:06:53.850> choose<00:06:54.060> the<00:06:54.120> one<00:06:54.360> by 00:06:54.530 --> 00:06:54.540 align:start position:0% disclaimer is that we choose the one by 00:06:54.540 --> 00:06:56.780 align:start position:0% disclaimer is that we choose the one by my<00:06:54.570> adviser<00:06:54.990> but<00:06:55.800> we<00:06:55.920> didn't<00:06:56.220> do<00:06:56.370> it<00:06:56.400> because 00:06:56.780 --> 00:06:56.790 align:start position:0% my adviser but we didn't do it because 00:06:56.790 --> 00:06:58.250 align:start position:0% my adviser but we didn't do it because it's<00:06:56.940> a<00:06:57.000> we<00:06:57.450> didn't<00:06:57.690> did<00:06:57.780> because<00:06:57.990> it's<00:06:58.110> his 00:06:58.250 --> 00:06:58.260 align:start position:0% it's a we didn't did because it's his 00:06:58.260 --> 00:07:00.200 align:start position:0% it's a we didn't did because it's his protocol<00:06:58.770> we<00:06:59.310> did<00:06:59.520> it<00:06:59.640> because<00:06:59.880> of<00:07:00.000> the<00:07:00.060> Meuse 00:07:00.200 --> 00:07:00.210 align:start position:0% protocol we did it because of the Meuse 00:07:00.210 --> 00:07:02.210 align:start position:0% protocol we did it because of the Meuse efficient<00:07:00.690> in<00:07:00.780> the<00:07:00.870> literature<00:07:01.140> it<00:07:01.860> requires 00:07:02.210 --> 00:07:02.220 align:start position:0% efficient in the literature it requires 00:07:02.220 --> 00:07:04.490 align:start position:0% efficient in the literature it requires two<00:07:02.520> rounds<00:07:02.970> and<00:07:03.150> there's<00:07:03.810> only<00:07:03.930> two<00:07:04.050> zero<00:07:04.470> and 00:07:04.490 --> 00:07:04.500 align:start position:0% two rounds and there's only two zero and 00:07:04.500 --> 00:07:06.890 align:start position:0% two rounds and there's only two zero and all<00:07:04.650> these<00:07:04.740> proofs<00:07:05.070> per<00:07:05.970> voter<00:07:06.240> so<00:07:06.780> it's 00:07:06.890 --> 00:07:06.900 align:start position:0% all these proofs per voter so it's 00:07:06.900 --> 00:07:09.920 align:start position:0% all these proofs per voter so it's highly<00:07:07.200> efficient<00:07:07.650> as<00:07:07.740> a<00:07:07.770> protocol<00:07:08.750> so<00:07:09.750> now 00:07:09.920 --> 00:07:09.930 align:start position:0% highly efficient as a protocol so now 00:07:09.930 --> 00:07:11.570 align:start position:0% highly efficient as a protocol so now I'm<00:07:09.990> going<00:07:10.170> to<00:07:10.260> explain<00:07:10.560> how<00:07:10.860> the<00:07:11.100> open<00:07:11.400> boot 00:07:11.570 --> 00:07:11.580 align:start position:0% I'm going to explain how the open boot 00:07:11.580 --> 00:07:13.570 align:start position:0% I'm going to explain how the open boot network<00:07:11.910> over<00:07:12.210> aetherium<00:07:12.510> works 00:07:13.570 --> 00:07:13.580 align:start position:0% network over aetherium works 00:07:13.580 --> 00:07:16.220 align:start position:0% network over aetherium works we<00:07:14.580> do<00:07:14.820> have<00:07:14.910> an<00:07:15.060> election<00:07:15.330> administrator<00:07:15.990> and 00:07:16.220 --> 00:07:16.230 align:start position:0% we do have an election administrator and 00:07:16.230 --> 00:07:19.550 align:start position:0% we do have an election administrator and his<00:07:16.620> only<00:07:16.800> job<00:07:17.190> is<00:07:17.460> one<00:07:18.170> authenticate<00:07:19.170> voters 00:07:19.550 --> 00:07:19.560 align:start position:0% his only job is one authenticate voters 00:07:19.560 --> 00:07:21.530 align:start position:0% his only job is one authenticate voters with<00:07:19.920> their<00:07:20.130> theorem<00:07:20.490> account<00:07:20.790> and<00:07:21.360> then 00:07:21.530 --> 00:07:21.540 align:start position:0% with their theorem account and then 00:07:21.540 --> 00:07:23.900 align:start position:0% with their theorem account and then update<00:07:22.020> the<00:07:22.140> smart<00:07:22.410> contract<00:07:22.700> with<00:07:23.700> that 00:07:23.900 --> 00:07:23.910 align:start position:0% update the smart contract with that 00:07:23.910 --> 00:07:25.760 align:start position:0% update the smart contract with that whitelist<00:07:24.390> so<00:07:24.960> we<00:07:25.050> can<00:07:25.140> at<00:07:25.230> least<00:07:25.350> know<00:07:25.500> who's 00:07:25.760 --> 00:07:25.770 align:start position:0% whitelist so we can at least know who's 00:07:25.770 --> 00:07:27.650 align:start position:0% whitelist so we can at least know who's going<00:07:25.950> to<00:07:26.070> vote<00:07:26.190> in<00:07:26.340> this<00:07:26.430> election<00:07:26.490> and<00:07:27.090> then 00:07:27.650 --> 00:07:27.660 align:start position:0% going to vote in this election and then 00:07:27.660 --> 00:07:29.840 align:start position:0% going to vote in this election and then his<00:07:27.780> other<00:07:27.930> job<00:07:28.170> is<00:07:28.350> to<00:07:28.470> poke<00:07:28.680> etherium<00:07:29.190> tutor 00:07:29.840 --> 00:07:29.850 align:start position:0% his other job is to poke etherium tutor 00:07:29.850 --> 00:07:32.060 align:start position:0% his other job is to poke etherium tutor to<00:07:30.060> transition<00:07:30.690> to<00:07:30.720> the<00:07:30.960> next<00:07:31.170> stage<00:07:31.380> although 00:07:32.060 --> 00:07:32.070 align:start position:0% to transition to the next stage although 00:07:32.070 --> 00:07:34.940 align:start position:0% to transition to the next stage although anyone<00:07:32.430> could<00:07:32.730> really<00:07:32.910> do<00:07:33.120> that<00:07:33.710> next 00:07:34.940 --> 00:07:34.950 align:start position:0% anyone could really do that next 00:07:34.950 --> 00:07:37.520 align:start position:0% anyone could really do that next he<00:07:35.460> sets<00:07:35.790> the<00:07:35.940> wait<00:07:36.060> list<00:07:36.180> available<00:07:36.530> eligible 00:07:37.520 --> 00:07:37.530 align:start position:0% he sets the wait list available eligible 00:07:37.530 --> 00:07:39.710 align:start position:0% he sets the wait list available eligible voters<00:07:37.830> he<00:07:38.430> will<00:07:38.580> set<00:07:38.790> the<00:07:38.910> voting<00:07:39.060> question 00:07:39.710 --> 00:07:39.720 align:start position:0% voters he will set the voting question 00:07:39.720 --> 00:07:41.780 align:start position:0% voters he will set the voting question and<00:07:39.900> then<00:07:40.260> he'll<00:07:40.380> notify<00:07:40.800> etherion<00:07:41.460> to<00:07:41.610> move 00:07:41.780 --> 00:07:41.790 align:start position:0% and then he'll notify etherion to move 00:07:41.790 --> 00:07:44.780 align:start position:0% and then he'll notify etherion to move on<00:07:42.000> to<00:07:42.720> the<00:07:42.870> sign-up<00:07:43.410> stage<00:07:43.800> and<00:07:44.130> I<00:07:44.550> Annie 00:07:44.780 --> 00:07:44.790 align:start position:0% on to the sign-up stage and I Annie 00:07:44.790 --> 00:07:46.970 align:start position:0% on to the sign-up stage and I Annie voter<00:07:45.210> can<00:07:45.510> look<00:07:45.630> at<00:07:45.750> the<00:07:45.840> question<00:07:46.380> and<00:07:46.530> then 00:07:46.970 --> 00:07:46.980 align:start position:0% voter can look at the question and then 00:07:46.980 --> 00:07:49.610 align:start position:0% voter can look at the question and then register<00:07:47.250> for<00:07:47.760> the<00:07:47.850> election<00:07:48.330> to<00:07:49.110> register 00:07:49.610 --> 00:07:49.620 align:start position:0% register for the election to register 00:07:49.620 --> 00:07:51.620 align:start position:0% register for the election to register the<00:07:50.430> voter<00:07:50.700> has<00:07:50.910> to<00:07:51.060> compute<00:07:51.420> a 00:07:51.620 --> 00:07:51.630 align:start position:0% the voter has to compute a 00:07:51.630 --> 00:07:53.930 align:start position:0% the voter has to compute a public/private<00:07:52.590> key<00:07:52.740> pair<00:07:52.770> and<00:07:53.280> this<00:07:53.820> is 00:07:53.930 --> 00:07:53.940 align:start position:0% public/private key pair and this is 00:07:53.940 --> 00:07:56.090 align:start position:0% public/private key pair and this is their<00:07:54.090> voting<00:07:54.300> key<00:07:54.600> and<00:07:54.840> then<00:07:55.800> alongside 00:07:56.090 --> 00:07:56.100 align:start position:0% their voting key and then alongside 00:07:56.100 --> 00:07:58.550 align:start position:0% their voting key and then alongside their<00:07:56.490> voting<00:07:56.670> key<00:07:56.940> they<00:07:57.540> critias<00:07:57.930> your<00:07:58.500> own 00:07:58.550 --> 00:07:58.560 align:start position:0% their voting key they critias your own 00:07:58.560 --> 00:08:00.590 align:start position:0% their voting key they critias your own ollies<00:07:58.770> proof<00:07:59.100> with<00:07:59.700> pretty<00:07:59.970> much<00:08:00.180> says<00:08:00.420> that 00:08:00.590 --> 00:08:00.600 align:start position:0% ollies proof with pretty much says that 00:08:00.600 --> 00:08:01.910 align:start position:0% ollies proof with pretty much says that they<00:08:00.720> knew<00:08:00.900> the<00:08:01.020> private<00:08:01.440> key<00:08:01.680> that 00:08:01.910 --> 00:08:01.920 align:start position:0% they knew the private key that 00:08:01.920 --> 00:08:04.730 align:start position:0% they knew the private key that corresponds<00:08:02.820> to<00:08:02.940> the<00:08:03.120> public<00:08:03.420> key<00:08:03.600> ie<00:08:04.110> they're 00:08:04.730 --> 00:08:04.740 align:start position:0% corresponds to the public key ie they're 00:08:04.740 --> 00:08:07.370 align:start position:0% corresponds to the public key ie they're the<00:08:04.890> owner<00:08:05.130> of<00:08:05.460> that<00:08:05.880> voting<00:08:06.240> key<00:08:06.420> and<00:08:06.750> now 00:08:07.370 --> 00:08:07.380 align:start position:0% the owner of that voting key and now 00:08:07.380 --> 00:08:08.480 align:start position:0% the owner of that voting key and now what<00:08:07.560> they<00:08:07.680> do<00:08:07.740> is<00:08:07.950> that<00:08:07.980> they<00:08:08.100> create<00:08:08.310> an 00:08:08.480 --> 00:08:08.490 align:start position:0% what they do is that they create an 00:08:08.490 --> 00:08:10.640 align:start position:0% what they do is that they create an aetherium<00:08:08.880> transaction<00:08:09.510> they<00:08:10.140> include<00:08:10.530> the 00:08:10.640 --> 00:08:10.650 align:start position:0% aetherium transaction they include the 00:08:10.650 --> 00:08:12.890 align:start position:0% aetherium transaction they include the voting<00:08:10.950> key<00:08:11.130> there's<00:08:11.910> proof<00:08:12.270> that<00:08:12.330> they<00:08:12.660> own 00:08:12.890 --> 00:08:12.900 align:start position:0% voting key there's proof that they own 00:08:12.900 --> 00:08:15.320 align:start position:0% voting key there's proof that they own this<00:08:13.110> voting<00:08:13.470> key<00:08:13.680> on<00:08:13.860> a<00:08:13.920> very<00:08:14.520> small<00:08:14.640> deposit 00:08:15.320 --> 00:08:15.330 align:start position:0% this voting key on a very small deposit 00:08:15.330 --> 00:08:18.080 align:start position:0% this voting key on a very small deposit and<00:08:16.160> every<00:08:17.160> voter<00:08:17.430> will<00:08:17.580> send<00:08:17.820> us<00:08:17.940> two 00:08:18.080 --> 00:08:18.090 align:start position:0% and every voter will send us two 00:08:18.090 --> 00:08:18.560 align:start position:0% and every voter will send us two aetherium 00:08:18.560 --> 00:08:18.570 align:start position:0% aetherium 00:08:18.570 --> 00:08:21.680 align:start position:0% aetherium and<00:08:18.720> a<00:08:19.260> very<00:08:19.500> earthy<00:08:19.890> Rifai<00:08:20.640> the<00:08:20.700> proof<00:08:21.030> it 00:08:21.680 --> 00:08:21.690 align:start position:0% and a very earthy Rifai the proof it 00:08:21.690 --> 00:08:23.600 align:start position:0% and a very earthy Rifai the proof it will<00:08:21.840> verify<00:08:22.080> the<00:08:22.260> proof<00:08:22.650> store<00:08:23.430> their 00:08:23.600 --> 00:08:23.610 align:start position:0% will verify the proof store their 00:08:23.610 --> 00:08:26.960 align:start position:0% will verify the proof store their deposit<00:08:24.090> and<00:08:24.270> store<00:08:24.600> the<00:08:24.690> encrypted<00:08:24.960> vote<00:08:25.970> and 00:08:26.960 --> 00:08:26.970 align:start position:0% deposit and store the encrypted vote and 00:08:26.970 --> 00:08:29.180 align:start position:0% deposit and store the encrypted vote and once<00:08:27.270> enough<00:08:27.600> voters<00:08:27.780> have<00:08:28.020> done<00:08:28.230> this<00:08:28.440> the 00:08:29.180 --> 00:08:29.190 align:start position:0% once enough voters have done this the 00:08:29.190 --> 00:08:31.070 align:start position:0% once enough voters have done this the elected<00:08:29.550> administrator<00:08:30.120> can<00:08:30.330> poke<00:08:30.540> aetherium 00:08:31.070 --> 00:08:31.080 align:start position:0% elected administrator can poke aetherium 00:08:31.080 --> 00:08:33.230 align:start position:0% elected administrator can poke aetherium to<00:08:31.650> move<00:08:31.860> on<00:08:32.070> to<00:08:32.250> the<00:08:32.340> voting<00:08:32.610> stage<00:08:32.880> and 00:08:33.230 --> 00:08:33.240 align:start position:0% to move on to the voting stage and 00:08:33.240 --> 00:08:36.440 align:start position:0% to move on to the voting stage and during<00:08:34.110> this<00:08:34.229> transition<00:08:34.950> from<00:08:35.790> the<00:08:36.030> sign<00:08:36.270> up 00:08:36.440 --> 00:08:36.450 align:start position:0% during this transition from the sign up 00:08:36.450 --> 00:08:38.780 align:start position:0% during this transition from the sign up to<00:08:36.810> the<00:08:36.900> voting<00:08:37.200> stage<00:08:37.440> a<00:08:37.740> theorem<00:08:38.640> will 00:08:38.780 --> 00:08:38.790 align:start position:0% to the voting stage a theorem will 00:08:38.790 --> 00:08:41.240 align:start position:0% to the voting stage a theorem will compute<00:08:39.210> a<00:08:39.360> second<00:08:40.140> key<00:08:40.349> for<00:08:40.650> every<00:08:40.800> single 00:08:41.240 --> 00:08:41.250 align:start position:0% compute a second key for every single 00:08:41.250 --> 00:08:43.460 align:start position:0% compute a second key for every single voter<00:08:41.430> and<00:08:41.970> we<00:08:42.180> call<00:08:42.450> this<00:08:42.599> the<00:08:42.780> reconstructed 00:08:43.460 --> 00:08:43.470 align:start position:0% voter and we call this the reconstructed 00:08:43.470 --> 00:08:45.020 align:start position:0% voter and we call this the reconstructed key<00:08:43.650> and<00:08:43.890> this<00:08:44.370> is<00:08:44.490> where<00:08:44.610> all<00:08:44.640> the<00:08:44.880> magic 00:08:45.020 --> 00:08:45.030 align:start position:0% key and this is where all the magic 00:08:45.030 --> 00:08:47.690 align:start position:0% key and this is where all the magic happens<00:08:45.240> in<00:08:45.690> terms<00:08:45.840> of<00:08:45.990> the<00:08:46.080> cryptography<00:08:46.700> so 00:08:47.690 --> 00:08:47.700 align:start position:0% happens in terms of the cryptography so 00:08:47.700 --> 00:08:49.250 align:start position:0% happens in terms of the cryptography so I've<00:08:47.790> got<00:08:47.910> this<00:08:48.030> really<00:08:48.240> ugly<00:08:48.390> formula<00:08:48.870> and 00:08:49.250 --> 00:08:49.260 align:start position:0% I've got this really ugly formula and 00:08:49.260 --> 00:08:51.050 align:start position:0% I've got this really ugly formula and that<00:08:49.620> means<00:08:49.800> not<00:08:50.010> nothing<00:08:50.460> to<00:08:50.550> anybody<00:08:50.790> in 00:08:51.050 --> 00:08:51.060 align:start position:0% that means not nothing to anybody in 00:08:51.060 --> 00:08:53.060 align:start position:0% that means not nothing to anybody in this<00:08:51.150> room<00:08:51.440> so<00:08:52.440> I'm<00:08:52.500> going<00:08:52.620> to<00:08:52.680> explain<00:08:52.920> it 00:08:53.060 --> 00:08:53.070 align:start position:0% this room so I'm going to explain it 00:08:53.070 --> 00:08:55.370 align:start position:0% this room so I'm going to explain it using<00:08:53.160> a<00:08:53.340> little<00:08:53.550> robot<00:08:53.880> so<00:08:54.570> if<00:08:54.660> I'm<00:08:54.780> voter<00:08:55.020> 3 00:08:55.370 --> 00:08:55.380 align:start position:0% using a little robot so if I'm voter 3 00:08:55.380 --> 00:08:57.830 align:start position:0% using a little robot so if I'm voter 3 the<00:08:56.280> way<00:08:56.430> I<00:08:56.460> can<00:08:56.700> put<00:08:56.910> my<00:08:57.060> reconstructed 00:08:57.830 --> 00:08:57.840 align:start position:0% the way I can put my reconstructed 00:08:57.840 --> 00:08:59.720 align:start position:0% the way I can put my reconstructed key<00:08:57.990> is<00:08:58.200> that<00:08:58.650> I<00:08:58.680> get<00:08:58.890> the<00:08:58.980> booting<00:08:59.310> key<00:08:59.520> of 00:08:59.720 --> 00:08:59.730 align:start position:0% key is that I get the booting key of 00:08:59.730 --> 00:09:02.030 align:start position:0% key is that I get the booting key of order<00:09:00.210> one<00:09:00.420> and<00:09:00.570> two<00:09:00.750> and<00:09:00.990> I<00:09:01.410> multiply<00:09:01.440> them 00:09:02.030 --> 00:09:02.040 align:start position:0% order one and two and I multiply them 00:09:02.040 --> 00:09:04.820 align:start position:0% order one and two and I multiply them together<00:09:02.160> I<00:09:02.640> get<00:09:03.270> the<00:09:03.510> voting<00:09:03.810> key<00:09:04.020> of<00:09:04.320> three 00:09:04.820 --> 00:09:04.830 align:start position:0% together I get the voting key of three 00:09:04.830 --> 00:09:06.860 align:start position:0% together I get the voting key of three are<00:09:05.040> four<00:09:05.370> and<00:09:05.460> five<00:09:05.700> and<00:09:06.120> I<00:09:06.300> multiply<00:09:06.510> them 00:09:06.860 --> 00:09:06.870 align:start position:0% are four and five and I multiply them 00:09:06.870 --> 00:09:09.500 align:start position:0% are four and five and I multiply them together<00:09:07.050> I<00:09:07.530> divide<00:09:08.490> those<00:09:08.820> two<00:09:08.880> you<00:09:09.390> know 00:09:09.500 --> 00:09:09.510 align:start position:0% together I divide those two you know 00:09:09.510 --> 00:09:11.690 align:start position:0% together I divide those two you know results<00:09:09.990> and<00:09:10.260> then<00:09:10.830> I<00:09:10.950> end<00:09:11.160> up<00:09:11.310> with<00:09:11.490> my<00:09:11.580> own 00:09:11.690 --> 00:09:11.700 align:start position:0% results and then I end up with my own 00:09:11.700 --> 00:09:13.820 align:start position:0% results and then I end up with my own voting<00:09:11.970> key<00:09:12.270> and<00:09:12.810> we<00:09:13.080> do<00:09:13.230> this<00:09:13.410> for<00:09:13.590> every 00:09:13.820 --> 00:09:13.830 align:start position:0% voting key and we do this for every 00:09:13.830 --> 00:09:15.950 align:start position:0% voting key and we do this for every single<00:09:13.860> voter<00:09:14.370> in<00:09:14.640> fact<00:09:15.090> aetherium<00:09:15.600> does<00:09:15.810> that 00:09:15.950 --> 00:09:15.960 align:start position:0% single voter in fact aetherium does that 00:09:15.960 --> 00:09:18.410 align:start position:0% single voter in fact aetherium does that for<00:09:16.140> every<00:09:16.350> single<00:09:16.560> voter<00:09:16.860> and<00:09:17.130> then<00:09:18.060> after 00:09:18.410 --> 00:09:18.420 align:start position:0% for every single voter and then after 00:09:18.420 --> 00:09:20.270 align:start position:0% for every single voter and then after that<00:09:18.570> we've<00:09:18.720> transitioned<00:09:19.140> and<00:09:19.590> once<00:09:20.130> we 00:09:20.270 --> 00:09:20.280 align:start position:0% that we've transitioned and once we 00:09:20.280 --> 00:09:22.340 align:start position:0% that we've transitioned and once we reach<00:09:20.310> the<00:09:20.640> voting<00:09:20.910> stage<00:09:21.150> every<00:09:21.990> single 00:09:22.340 --> 00:09:22.350 align:start position:0% reach the voting stage every single 00:09:22.350 --> 00:09:23.890 align:start position:0% reach the voting stage every single voter<00:09:22.560> has<00:09:22.770> a<00:09:22.800> voting<00:09:23.190> key<00:09:23.400> on<00:09:23.610> a 00:09:23.890 --> 00:09:23.900 align:start position:0% voter has a voting key on a 00:09:23.900 --> 00:09:26.770 align:start position:0% voter has a voting key on a reconstructed<00:09:24.900> key<00:09:25.050> now<00:09:25.830> at<00:09:25.920> a<00:09:25.980> cast<00:09:26.250> our<00:09:26.460> vote 00:09:26.770 --> 00:09:26.780 align:start position:0% reconstructed key now at a cast our vote 00:09:26.780 --> 00:09:29.360 align:start position:0% reconstructed key now at a cast our vote we<00:09:27.780> have<00:09:27.900> to<00:09:28.020> be<00:09:28.110> an<00:09:28.200> El<00:09:28.380> Gamal<00:09:28.620> encryption<00:09:29.250> of 00:09:29.360 --> 00:09:29.370 align:start position:0% we have to be an El Gamal encryption of 00:09:29.370 --> 00:09:32.690 align:start position:0% we have to be an El Gamal encryption of the<00:09:30.150> vote<00:09:30.330> and<00:09:30.920> that<00:09:31.920> is<00:09:32.040> essentially<00:09:32.520> this 00:09:32.690 --> 00:09:32.700 align:start position:0% the vote and that is essentially this 00:09:32.700 --> 00:09:35.000 align:start position:0% the vote and that is essentially this little<00:09:33.000> formula<00:09:33.450> so<00:09:33.930> it<00:09:34.050> hits<00:09:34.500> in<00:09:34.650> the<00:09:34.740> voting 00:09:35.000 --> 00:09:35.010 align:start position:0% little formula so it hits in the voting 00:09:35.010 --> 00:09:37.790 align:start position:0% little formula so it hits in the voting key<00:09:35.220> the<00:09:35.880> reconstructed<00:09:36.660> key<00:09:36.840> and<00:09:37.050> then<00:09:37.620> the 00:09:37.790 --> 00:09:37.800 align:start position:0% key the reconstructed key and then the 00:09:37.800 --> 00:09:40.250 align:start position:0% key the reconstructed key and then the vote<00:09:38.010> is<00:09:38.280> either<00:09:38.670> G<00:09:38.940> to<00:09:39.000> the<00:09:39.060> power<00:09:39.120> of<00:09:39.330> 0<00:09:39.630> or<00:09:39.840> G 00:09:40.250 --> 00:09:40.260 align:start position:0% vote is either G to the power of 0 or G 00:09:40.260 --> 00:09:41.900 align:start position:0% vote is either G to the power of 0 or G to<00:09:40.350> the<00:09:40.380> power<00:09:40.470> of<00:09:40.680> 1<00:09:40.860> and<00:09:41.100> that<00:09:41.460> pretty<00:09:41.730> much 00:09:41.900 --> 00:09:41.910 align:start position:0% to the power of 1 and that pretty much 00:09:41.910 --> 00:09:44.810 align:start position:0% to the power of 1 and that pretty much is<00:09:42.090> a<00:09:42.120> yes<00:09:42.420> or<00:09:42.600> no<00:09:42.780> vote<00:09:42.810> and<00:09:43.370> then<00:09:44.370> what<00:09:44.520> we<00:09:44.610> do 00:09:44.810 --> 00:09:44.820 align:start position:0% is a yes or no vote and then what we do 00:09:44.820 --> 00:09:47.720 align:start position:0% is a yes or no vote and then what we do is<00:09:44.940> we<00:09:45.060> construct<00:09:45.330> a<00:09:45.780> 1<00:09:46.380> out<00:09:46.530> of<00:09:46.590> 2<00:09:46.860> 0<00:09:47.430> nollies 00:09:47.720 --> 00:09:47.730 align:start position:0% is we construct a 1 out of 2 0 nollies 00:09:47.730 --> 00:09:50.030 align:start position:0% is we construct a 1 out of 2 0 nollies proof<00:09:47.970> and<00:09:48.270> this<00:09:48.870> pretty<00:09:49.110> much<00:09:49.200> says<00:09:49.590> that<00:09:49.830> I 00:09:50.030 --> 00:09:50.040 align:start position:0% proof and this pretty much says that I 00:09:50.040 --> 00:09:52.310 align:start position:0% proof and this pretty much says that I prove<00:09:50.580> to<00:09:50.610> you<00:09:50.790> that<00:09:50.970> my<00:09:51.420> encrypted<00:09:51.750> vote<00:09:52.080> is 00:09:52.310 --> 00:09:52.320 align:start position:0% prove to you that my encrypted vote is 00:09:52.320 --> 00:09:55.430 align:start position:0% prove to you that my encrypted vote is either<00:09:52.860> yes<00:09:53.130> or<00:09:53.280> no<00:09:53.340> and<00:09:53.960> that<00:09:54.960> means<00:09:55.170> the<00:09:55.320> vote 00:09:55.430 --> 00:09:55.440 align:start position:0% either yes or no and that means the vote 00:09:55.440 --> 00:09:57.470 align:start position:0% either yes or no and that means the vote is<00:09:55.590> well<00:09:55.740> formed<00:09:56.100> and<00:09:56.400> I<00:09:56.640> reveal<00:09:56.910> nothing<00:09:57.330> else 00:09:57.470 --> 00:09:57.480 align:start position:0% is well formed and I reveal nothing else 00:09:57.480 --> 00:09:59.660 align:start position:0% is well formed and I reveal nothing else about<00:09:57.630> my<00:09:57.870> vote<00:09:58.110> and<00:09:59.100> then<00:09:59.280> I<00:09:59.310> created 00:09:59.660 --> 00:09:59.670 align:start position:0% about my vote and then I created 00:09:59.670 --> 00:10:01.790 align:start position:0% about my vote and then I created aetherium<00:10:00.030> transaction<00:10:00.780> that<00:10:01.260> includes<00:10:01.650> my 00:10:01.790 --> 00:10:01.800 align:start position:0% aetherium transaction that includes my 00:10:01.800 --> 00:10:04.400 align:start position:0% aetherium transaction that includes my elgamal<00:10:02.220> encrypted<00:10:02.730> vote<00:10:02.910> my<00:10:03.600> one<00:10:03.870> out<00:10:04.020> of<00:10:04.050> two 00:10:04.400 --> 00:10:04.410 align:start position:0% elgamal encrypted vote my one out of two 00:10:04.410 --> 00:10:06.740 align:start position:0% elgamal encrypted vote my one out of two zero<00:10:04.950> nollies<00:10:05.250> proof<00:10:05.520> and<00:10:05.820> I<00:10:06.210> send<00:10:06.510> that<00:10:06.660> to 00:10:06.740 --> 00:10:06.750 align:start position:0% zero nollies proof and I send that to 00:10:06.750 --> 00:10:08.780 align:start position:0% zero nollies proof and I send that to the<00:10:06.840> contract<00:10:07.290> the<00:10:07.980> contract<00:10:08.460> will<00:10:08.580> verify 00:10:08.780 --> 00:10:08.790 align:start position:0% the contract the contract will verify 00:10:08.790 --> 00:10:10.820 align:start position:0% the contract the contract will verify that<00:10:09.180> my<00:10:09.300> vote<00:10:09.510> is<00:10:09.630> well<00:10:09.780> formed<00:10:10.140> and<00:10:10.440> then 00:10:10.820 --> 00:10:10.830 align:start position:0% that my vote is well formed and then 00:10:10.830 --> 00:10:12.710 align:start position:0% that my vote is well formed and then store<00:10:11.160> it<00:10:11.310> and<00:10:11.520> then<00:10:11.580> it<00:10:12.330> will<00:10:12.420> release<00:10:12.690> the 00:10:12.710 --> 00:10:12.720 align:start position:0% store it and then it will release the 00:10:12.720 --> 00:10:15.130 align:start position:0% store it and then it will release the deposit<00:10:13.350> and<00:10:13.500> give<00:10:14.010> me<00:10:14.100> my<00:10:14.220> money<00:10:14.370> back<00:10:14.460> and 00:10:15.130 --> 00:10:15.140 align:start position:0% deposit and give me my money back and 00:10:15.140 --> 00:10:18.080 align:start position:0% deposit and give me my money back and every<00:10:16.140> single<00:10:16.470> voter<00:10:16.650> will<00:10:16.800> do<00:10:16.950> this<00:10:17.160> and<00:10:17.460> once 00:10:18.080 --> 00:10:18.090 align:start position:0% every single voter will do this and once 00:10:18.090 --> 00:10:20.060 align:start position:0% every single voter will do this and once the<00:10:18.240> final<00:10:18.570> vote<00:10:18.720> has<00:10:18.840> been<00:10:18.870> cast<00:10:19.200> the 00:10:20.060 --> 00:10:20.070 align:start position:0% the final vote has been cast the 00:10:20.070 --> 00:10:22.910 align:start position:0% the final vote has been cast the election<00:10:20.520> is<00:10:20.640> over<00:10:20.760> and<00:10:21.260> anybody<00:10:22.260> can<00:10:22.590> compute 00:10:22.910 --> 00:10:22.920 align:start position:0% election is over and anybody can compute 00:10:22.920 --> 00:10:25.070 align:start position:0% election is over and anybody can compute the<00:10:23.010> tally<00:10:23.220> and<00:10:23.490> in<00:10:23.940> fact<00:10:24.150> so<00:10:24.390> can<00:10:24.570> aetherium 00:10:25.070 --> 00:10:25.080 align:start position:0% the tally and in fact so can aetherium 00:10:25.080 --> 00:10:27.560 align:start position:0% the tally and in fact so can aetherium so<00:10:25.860> the<00:10:26.370> election<00:10:26.730> administrator<00:10:27.210> can<00:10:27.390> poke 00:10:27.560 --> 00:10:27.570 align:start position:0% so the election administrator can poke 00:10:27.570 --> 00:10:30.160 align:start position:0% so the election administrator can poke aetherium<00:10:28.080> to<00:10:28.590> finally<00:10:28.980> compute<00:10:29.280> the<00:10:29.430> tally 00:10:30.160 --> 00:10:30.170 align:start position:0% aetherium to finally compute the tally 00:10:30.170 --> 00:10:32.900 align:start position:0% aetherium to finally compute the tally theorem<00:10:31.170> does<00:10:31.380> this<00:10:31.590> and<00:10:31.890> the<00:10:32.310> way<00:10:32.430> we<00:10:32.580> compute 00:10:32.900 --> 00:10:32.910 align:start position:0% theorem does this and the way we compute 00:10:32.910 --> 00:10:34.670 align:start position:0% theorem does this and the way we compute the<00:10:32.970> tally<00:10:33.210> is<00:10:33.360> really<00:10:33.630> straightforward<00:10:33.900> we 00:10:34.670 --> 00:10:34.680 align:start position:0% the tally is really straightforward we 00:10:34.680 --> 00:10:36.350 align:start position:0% the tally is really straightforward we just<00:10:34.920> have<00:10:35.010> the<00:10:35.100> odd<00:10:35.250> or<00:10:35.670> the<00:10:35.850> encrypted<00:10:36.090> votes 00:10:36.350 --> 00:10:36.360 align:start position:0% just have the odd or the encrypted votes 00:10:36.360 --> 00:10:38.600 align:start position:0% just have the odd or the encrypted votes together<00:10:36.660> and<00:10:37.290> once<00:10:37.740> you<00:10:37.830> add<00:10:38.040> the<00:10:38.070> final 00:10:38.600 --> 00:10:38.610 align:start position:0% together and once you add the final 00:10:38.610 --> 00:10:40.400 align:start position:0% together and once you add the final encrypted<00:10:39.000> vote<00:10:39.180> be<00:10:39.960> instant<00:10:40.260> heard<00:10:40.350> that 00:10:40.400 --> 00:10:40.410 align:start position:0% encrypted vote be instant heard that 00:10:40.410 --> 00:10:42.650 align:start position:0% encrypted vote be instant heard that el-gamal<00:10:40.770> encryption<00:10:41.040> was<00:10:41.490> set<00:10:41.700> up<00:10:41.880> all<00:10:42.240> the 00:10:42.650 --> 00:10:42.660 align:start position:0% el-gamal encryption was set up all the 00:10:42.660 --> 00:10:44.990 align:start position:0% el-gamal encryption was set up all the random<00:10:42.870> factors<00:10:43.440> are<00:10:43.590> cancelled<00:10:43.980> out<00:10:44.100> and<00:10:44.430> all 00:10:44.990 --> 00:10:45.000 align:start position:0% random factors are cancelled out and all 00:10:45.000 --> 00:10:47.870 align:start position:0% random factors are cancelled out and all we're<00:10:45.150> left<00:10:45.360> with<00:10:45.600> is<00:10:45.840> G<00:10:46.170> ^<00:10:46.290> vs<00:10:46.860> votes<00:10:47.100> as<00:10:47.820> a 00:10:47.870 --> 00:10:47.880 align:start position:0% we're left with is G ^ vs votes as a 00:10:47.880 --> 00:10:49.370 align:start position:0% we're left with is G ^ vs votes as a very<00:10:48.210> small<00:10:48.450> discrete<00:10:48.810> log<00:10:48.990> there<00:10:49.260> can<00:10:49.350> be 00:10:49.370 --> 00:10:49.380 align:start position:0% very small discrete log there can be 00:10:49.380 --> 00:10:51.710 align:start position:0% very small discrete log there can be brute<00:10:49.650> forced<00:10:50.010> by<00:10:50.250> the<00:10:50.310> smart<00:10:50.670> contract<00:10:51.150> which 00:10:51.710 --> 00:10:51.720 align:start position:0% brute forced by the smart contract which 00:10:51.720 --> 00:10:53.750 align:start position:0% brute forced by the smart contract which it<00:10:51.900> does<00:10:52.110> and<00:10:52.500> then<00:10:53.070> once<00:10:53.250> we<00:10:53.370> have<00:10:53.460> the<00:10:53.550> number 00:10:53.750 --> 00:10:53.760 align:start position:0% it does and then once we have the number 00:10:53.760 --> 00:10:55.580 align:start position:0% it does and then once we have the number of<00:10:53.850> yes<00:10:54.000> votes<00:10:54.270> it's<00:10:54.960> really<00:10:55.320> straightforward 00:10:55.580 --> 00:10:55.590 align:start position:0% of yes votes it's really straightforward 00:10:55.590 --> 00:10:57.280 align:start position:0% of yes votes it's really straightforward to<00:10:55.950> get<00:10:56.040> the<00:10:56.190> number<00:10:56.430> of<00:10:56.520> no<00:10:56.640> votes 00:10:57.280 --> 00:10:57.290 align:start position:0% to get the number of no votes 00:10:57.290 --> 00:11:00.800 align:start position:0% to get the number of no votes now<00:10:58.290> before<00:10:58.770> I<00:10:58.800> did<00:10:59.130> this<00:10:59.250> last<00:10:59.430> summer<00:10:59.810> before 00:11:00.800 --> 00:11:00.810 align:start position:0% now before I did this last summer before 00:11:00.810 --> 00:11:03.620 align:start position:0% now before I did this last summer before the<00:11:01.170> byzantium<00:11:01.770> heart<00:11:01.980> Fork<00:11:02.250> and<00:11:02.400> the<00:11:03.240> problem 00:11:03.620 --> 00:11:03.630 align:start position:0% the byzantium heart Fork and the problem 00:11:03.630 --> 00:11:05.480 align:start position:0% the byzantium heart Fork and the problem was<00:11:03.690> that<00:11:03.930> elliptic<00:11:04.500> curve<00:11:04.710> mathematics<00:11:05.370> was 00:11:05.480 --> 00:11:05.490 align:start position:0% was that elliptic curve mathematics was 00:11:05.490 --> 00:11:07.330 align:start position:0% was that elliptic curve mathematics was not<00:11:05.670> natively<00:11:06.030> supported<00:11:06.570> by<00:11:06.690> aetherium 00:11:07.330 --> 00:11:07.340 align:start position:0% not natively supported by aetherium 00:11:07.340 --> 00:11:10.430 align:start position:0% not natively supported by aetherium so<00:11:08.340> these<00:11:09.120> are<00:11:09.270> some<00:11:09.450> of<00:11:09.480> the<00:11:09.600> gas<00:11:09.780> costs<00:11:10.320> of 00:11:10.430 --> 00:11:10.440 align:start position:0% so these are some of the gas costs of 00:11:10.440 --> 00:11:11.570 align:start position:0% so these are some of the gas costs of trying<00:11:10.680> to<00:11:10.710> do<00:11:10.920> elliptic<00:11:11.250> curve 00:11:11.570 --> 00:11:11.580 align:start position:0% trying to do elliptic curve 00:11:11.580 --> 00:11:14.060 align:start position:0% trying to do elliptic curve monix<00:11:11.850> back<00:11:12.000> then<00:11:12.240> so<00:11:13.080> the<00:11:13.170> cast<00:11:13.410> of<00:11:13.590> vote<00:11:13.800> was 00:11:14.060 --> 00:11:14.070 align:start position:0% monix back then so the cast of vote was 00:11:14.070 --> 00:11:17.180 align:start position:0% monix back then so the cast of vote was 2.5<00:11:14.730> million<00:11:15.000> gasps<00:11:15.440> so<00:11:16.440> that<00:11:16.560> means<00:11:16.770> today 00:11:17.180 --> 00:11:17.190 align:start position:0% 2.5 million gasps so that means today 00:11:17.190 --> 00:11:18.710 align:start position:0% 2.5 million gasps so that means today you'd<00:11:17.400> be<00:11:17.550> able<00:11:17.610> to<00:11:17.730> fit<00:11:17.910> three<00:11:18.180> votes<00:11:18.480> in<00:11:18.660> a 00:11:18.710 --> 00:11:18.720 align:start position:0% you'd be able to fit three votes in a 00:11:18.720 --> 00:11:22.850 align:start position:0% you'd be able to fit three votes in a block<00:11:18.930> and<00:11:19.830> it<00:11:20.160> was<00:11:20.250> $2<00:11:20.820> on<00:11:21.230> the<00:11:22.230> register<00:11:22.650> for 00:11:22.850 --> 00:11:22.860 align:start position:0% block and it was $2 on the register for 00:11:22.860 --> 00:11:25.940 align:start position:0% block and it was $2 on the register for the<00:11:22.920> election<00:11:23.430> was<00:11:23.810> 60<00:11:24.810> cents<00:11:25.200> now 00:11:25.940 --> 00:11:25.950 align:start position:0% the election was 60 cents now 00:11:25.950 --> 00:11:28.640 align:start position:0% the election was 60 cents now unfortunately<00:11:26.460> I<00:11:27.150> haven't<00:11:28.020> monies<00:11:28.380> to<00:11:28.410> get 00:11:28.640 --> 00:11:28.650 align:start position:0% unfortunately I haven't monies to get 00:11:28.650 --> 00:11:30.740 align:start position:0% unfortunately I haven't monies to get the<00:11:28.770> new<00:11:28.860> opcode<00:11:29.310> to<00:11:29.490> work<00:11:29.670> yet<00:11:29.910> cuz<00:11:30.420> I<00:11:30.480> really 00:11:30.740 --> 00:11:30.750 align:start position:0% the new opcode to work yet cuz I really 00:11:30.750 --> 00:11:32.900 align:start position:0% the new opcode to work yet cuz I really wanted<00:11:30.960> to<00:11:31.050> have<00:11:31.230> exactly<00:11:31.800> the<00:11:31.920> new<00:11:32.100> gas<00:11:32.370> costs 00:11:32.900 --> 00:11:32.910 align:start position:0% wanted to have exactly the new gas costs 00:11:32.910 --> 00:11:34.910 align:start position:0% wanted to have exactly the new gas costs but<00:11:33.510> what<00:11:33.630> I<00:11:33.660> did<00:11:33.900> this<00:11:34.020> morning<00:11:34.290> was<00:11:34.440> I<00:11:34.680> worked 00:11:34.910 --> 00:11:34.920 align:start position:0% but what I did this morning was I worked 00:11:34.920 --> 00:11:37.640 align:start position:0% but what I did this morning was I worked at<00:11:35.100> roughly<00:11:35.850> how<00:11:36.000> much<00:11:36.150> it<00:11:36.330> would<00:11:36.450> be<00:11:36.650> using 00:11:37.640 --> 00:11:37.650 align:start position:0% at roughly how much it would be using 00:11:37.650 --> 00:11:39.830 align:start position:0% at roughly how much it would be using the<00:11:37.740> new<00:11:37.830> heart<00:11:38.130> forked<00:11:38.490> up<00:11:38.700> codes<00:11:39.120> because<00:11:39.570> my 00:11:39.830 --> 00:11:39.840 align:start position:0% the new heart forked up codes because my 00:11:39.840 --> 00:11:41.540 align:start position:0% the new heart forked up codes because my aetherium<00:11:40.560> support<00:11:40.950> elliptic<00:11:41.400> earth 00:11:41.540 --> 00:11:41.550 align:start position:0% aetherium support elliptic earth 00:11:41.550 --> 00:11:44.510 align:start position:0% aetherium support elliptic earth mathematics<00:11:42.090> so<00:11:43.080> the<00:11:43.410> cost<00:11:43.680> an<00:11:44.100> encrypted 00:11:44.510 --> 00:11:44.520 align:start position:0% mathematics so the cost an encrypted 00:11:44.520 --> 00:11:46.550 align:start position:0% mathematics so the cost an encrypted vote<00:11:44.820> with<00:11:45.420> the<00:11:45.570> one<00:11:45.750> out<00:11:45.900> of<00:11:45.930> two<00:11:46.260> zero 00:11:46.550 --> 00:11:46.560 align:start position:0% vote with the one out of two zero 00:11:46.560 --> 00:11:48.980 align:start position:0% vote with the one out of two zero Knollys<00:11:46.800> proofs<00:11:47.100> it<00:11:47.490> goes<00:11:48.150> from<00:11:48.360> two<00:11:48.540> dollars 00:11:48.980 --> 00:11:48.990 align:start position:0% Knollys proofs it goes from two dollars 00:11:48.990 --> 00:11:52.160 align:start position:0% Knollys proofs it goes from two dollars the<00:11:49.230> 60<00:11:49.740> cents<00:11:50.100> and<00:11:50.340> we<00:11:50.820> see<00:11:51.030> if<00:11:51.150> 1.7<00:11:51.990> million 00:11:52.160 --> 00:11:52.170 align:start position:0% the 60 cents and we see if 1.7 million 00:11:52.170 --> 00:11:54.740 align:start position:0% the 60 cents and we see if 1.7 million gasps<00:11:52.500> so<00:11:53.280> ever<00:11:53.610> maybe<00:11:53.940> we<00:11:54.090> have<00:11:54.240> a<00:11:54.300> big<00:11:54.480> club 00:11:54.740 --> 00:11:54.750 align:start position:0% gasps so ever maybe we have a big club 00:11:54.750 --> 00:11:56.870 align:start position:0% gasps so ever maybe we have a big club for<00:11:54.930> high<00:11:55.020> achievers<00:11:55.440> back<00:11:55.620> to<00:11:55.800> God<00:11:55.950> that 00:11:56.870 --> 00:11:56.880 align:start position:0% for high achievers back to God that 00:11:56.880 --> 00:11:57.770 align:start position:0% for high achievers back to God that makes<00:11:57.030> me<00:11:57.180> really<00:11:57.300> happy 00:11:57.770 --> 00:11:57.780 align:start position:0% makes me really happy 00:11:57.780 --> 00:12:01.160 align:start position:0% makes me really happy thank<00:11:58.290> you<00:11:59.960> yeah 00:12:01.160 --> 00:12:01.170 align:start position:0% thank you yeah 00:12:01.170 --> 00:12:03.920 align:start position:0% thank you yeah so<00:12:01.290> it's<00:12:01.440> those<00:12:01.880> 700,000<00:12:02.880> gasps<00:12:03.060> but<00:12:03.690> that's<00:12:03.840> a 00:12:03.920 --> 00:12:03.930 align:start position:0% so it's those 700,000 gasps but that's a 00:12:03.930 --> 00:12:05.690 align:start position:0% so it's those 700,000 gasps but that's a very<00:12:04.080> expensive<00:12:04.380> zero<00:12:04.890> knowledge<00:12:05.040> proof<00:12:05.190> and 00:12:05.690 --> 00:12:05.700 align:start position:0% very expensive zero knowledge proof and 00:12:05.700 --> 00:12:07.910 align:start position:0% very expensive zero knowledge proof and now<00:12:06.150> we<00:12:06.210> can<00:12:06.450> fit<00:12:06.690> what<00:12:06.900> nearly<00:12:07.350> 10<00:12:07.590> of<00:12:07.770> them 00:12:07.910 --> 00:12:07.920 align:start position:0% now we can fit what nearly 10 of them 00:12:07.920 --> 00:12:09.710 align:start position:0% now we can fit what nearly 10 of them inside<00:12:08.220> a<00:12:08.310> block<00:12:08.490> so<00:12:09.150> that's<00:12:09.300> much<00:12:09.510> better 00:12:09.710 --> 00:12:09.720 align:start position:0% inside a block so that's much better 00:12:09.720 --> 00:12:12.320 align:start position:0% inside a block so that's much better than<00:12:09.840> what<00:12:10.080> we<00:12:10.140> could<00:12:10.260> do<00:12:10.410> before<00:12:11.150> so<00:12:12.150> that's 00:12:12.320 --> 00:12:12.330 align:start position:0% than what we could do before so that's 00:12:12.330 --> 00:12:14.150 align:start position:0% than what we could do before so that's basically<00:12:12.840> you<00:12:12.990> know<00:12:13.110> the<00:12:13.290> new<00:12:13.440> cost<00:12:13.770> to<00:12:14.010> run 00:12:14.150 --> 00:12:14.160 align:start position:0% basically you know the new cost to run 00:12:14.160 --> 00:12:17.660 align:start position:0% basically you know the new cost to run this<00:12:14.280> protocol<00:12:14.940> roughly<00:12:15.860> and<00:12:16.860> now<00:12:17.400> I<00:12:17.430> have 00:12:17.660 --> 00:12:17.670 align:start position:0% this protocol roughly and now I have 00:12:17.670 --> 00:12:19.220 align:start position:0% this protocol roughly and now I have some<00:12:17.940> time<00:12:18.180> to<00:12:18.300> show<00:12:18.480> a<00:12:18.510> video<00:12:18.720> that's 00:12:19.220 --> 00:12:19.230 align:start position:0% some time to show a video that's 00:12:19.230 --> 00:12:21.020 align:start position:0% some time to show a video that's fantastic<00:12:19.890> I<00:12:20.010> try<00:12:20.220> my<00:12:20.340> best<00:12:20.490> to<00:12:20.640> see<00:12:20.790> of<00:12:20.880> some 00:12:21.020 --> 00:12:21.030 align:start position:0% fantastic I try my best to see of some 00:12:21.030 --> 00:12:24.170 align:start position:0% fantastic I try my best to see of some time<00:12:21.240> so<00:12:21.840> I'll<00:12:21.960> quickly<00:12:22.110> play<00:12:22.530> the<00:12:22.680> video<00:12:23.180> that 00:12:24.170 --> 00:12:24.180 align:start position:0% time so I'll quickly play the video that 00:12:24.180 --> 00:12:25.190 align:start position:0% time so I'll quickly play the video that was<00:12:24.270> the<00:12:24.390> code<00:12:24.600> else<00:12:24.780> looking<00:12:24.990> at<00:12:25.110> this 00:12:25.190 --> 00:12:25.200 align:start position:0% was the code else looking at this 00:12:25.200 --> 00:12:29.360 align:start position:0% was the code else looking at this morning<00:12:25.590> they<00:12:25.680> get<00:12:25.770> the<00:12:25.920> stats<00:12:28.370> unnecessary 00:12:29.360 --> 00:12:29.370 align:start position:0% morning they get the stats unnecessary 00:12:29.370 --> 00:12:31.700 align:start position:0% morning they get the stats unnecessary so<00:12:29.700> I<00:12:29.940> actually<00:12:30.180> built<00:12:30.600> it<00:12:30.720> as<00:12:30.810> a<00:12:30.840> website<00:12:31.320> and 00:12:31.700 --> 00:12:31.710 align:start position:0% so I actually built it as a website and 00:12:31.710 --> 00:12:33.500 align:start position:0% so I actually built it as a website and I<00:12:31.800> spoke<00:12:32.100> to<00:12:32.220> someone<00:12:32.490> last<00:12:32.670> night<00:12:32.880> Annapurna 00:12:33.500 --> 00:12:33.510 align:start position:0% I spoke to someone last night Annapurna 00:12:33.510 --> 00:12:35.060 align:start position:0% I spoke to someone last night Annapurna he<00:12:33.660> gets<00:12:33.810> really<00:12:34.020> easy<00:12:34.050> and<00:12:34.560> decreed<00:12:34.860> in<00:12:34.950> the 00:12:35.060 --> 00:12:35.070 align:start position:0% he gets really easy and decreed in the 00:12:35.070 --> 00:12:37.910 align:start position:0% he gets really easy and decreed in the mist<00:12:35.280> so<00:12:35.970> I'd<00:12:36.120> love<00:12:36.270> to<00:12:36.330> see<00:12:36.450> that<00:12:36.690> happen<00:12:36.920> but 00:12:37.910 --> 00:12:37.920 align:start position:0% mist so I'd love to see that happen but 00:12:37.920 --> 00:12:39.410 align:start position:0% mist so I'd love to see that happen but essentially<00:12:38.460> this<00:12:38.610> is<00:12:38.760> the<00:12:38.970> election 00:12:39.410 --> 00:12:39.420 align:start position:0% essentially this is the election 00:12:39.420 --> 00:12:41.780 align:start position:0% essentially this is the election administrator<00:12:40.110> screen<00:12:40.470> he's<00:12:40.980> logging<00:12:41.280> in<00:12:41.580> and 00:12:41.780 --> 00:12:41.790 align:start position:0% administrator screen he's logging in and 00:12:41.790 --> 00:12:43.910 align:start position:0% administrator screen he's logging in and he's<00:12:41.970> gonna<00:12:42.150> set<00:12:42.390> up<00:12:42.480> the<00:12:42.600> election<00:12:43.080> he<00:12:43.560> sets 00:12:43.910 --> 00:12:43.920 align:start position:0% he's gonna set up the election he sets 00:12:43.920 --> 00:12:46.040 align:start position:0% he's gonna set up the election he sets the<00:12:44.070> list<00:12:44.250> of<00:12:44.400> eligible<00:12:44.670> voters<00:12:44.910> all<00:12:45.540> they 00:12:46.040 --> 00:12:46.050 align:start position:0% the list of eligible voters all they 00:12:46.050 --> 00:12:47.660 align:start position:0% the list of eligible voters all they have<00:12:46.140> hard-coded<00:12:46.410> it<00:12:46.800> because<00:12:47.010> I'm<00:12:47.100> lazy<00:12:47.280> and 00:12:47.660 --> 00:12:47.670 align:start position:0% have hard-coded it because I'm lazy and 00:12:47.670 --> 00:12:50.990 align:start position:0% have hard-coded it because I'm lazy and really<00:12:47.960> struggled<00:12:48.960> with<00:12:48.990> it<00:12:49.170> as<00:12:49.290> well<00:12:49.700> we<00:12:50.700> send 00:12:50.990 --> 00:12:51.000 align:start position:0% really struggled with it as well we send 00:12:51.000 --> 00:12:52.640 align:start position:0% really struggled with it as well we send that<00:12:51.120> off<00:12:51.210> to<00:12:51.330> the<00:12:51.450> contract<00:12:52.230> and<00:12:52.470> now<00:12:52.590> the 00:12:52.640 --> 00:12:52.650 align:start position:0% that off to the contract and now the 00:12:52.650 --> 00:12:54.770 align:start position:0% that off to the contract and now the list<00:12:52.920> of<00:12:53.040> eligible<00:12:53.220> voters<00:12:53.640> are<00:12:53.760> set<00:12:53.940> up<00:12:54.150> we 00:12:54.770 --> 00:12:54.780 align:start position:0% list of eligible voters are set up we 00:12:54.780 --> 00:12:56.960 align:start position:0% list of eligible voters are set up we set<00:12:55.020> a<00:12:55.050> bunch<00:12:55.290> of<00:12:55.440> timers<00:12:55.980> for<00:12:56.010> the<00:12:56.400> election 00:12:56.960 --> 00:12:56.970 align:start position:0% set a bunch of timers for the election 00:12:56.970 --> 00:12:58.490 align:start position:0% set a bunch of timers for the election so<00:12:57.360> that<00:12:57.480> way<00:12:57.600> the<00:12:57.720> election<00:12:57.960> runs<00:12:58.290> in<00:12:58.440> a 00:12:58.490 --> 00:12:58.500 align:start position:0% so that way the election runs in a 00:12:58.500 --> 00:13:00.650 align:start position:0% so that way the election runs in a timely<00:12:58.860> manner<00:12:59.040> we<00:12:59.820> set<00:13:00.030> the<00:13:00.150> voting<00:13:00.240> question 00:13:00.650 --> 00:13:00.660 align:start position:0% timely manner we set the voting question 00:13:00.660 --> 00:13:03.620 align:start position:0% timely manner we set the voting question is<00:13:01.410> you<00:13:01.590> Satoshi<00:13:01.920> Nakamoto<00:13:02.520> reveal<00:13:03.270> Israel 00:13:03.620 --> 00:13:03.630 align:start position:0% is you Satoshi Nakamoto reveal Israel 00:13:03.630 --> 00:13:04.570 align:start position:0% is you Satoshi Nakamoto reveal Israel world<00:13:03.840> identity 00:13:04.570 --> 00:13:04.580 align:start position:0% world identity 00:13:04.580 --> 00:13:08.060 align:start position:0% world identity hopefully<00:13:05.580> everybody<00:13:05.850> says<00:13:06.090> no<00:13:06.350> and<00:13:07.350> then<00:13:07.950> we 00:13:08.060 --> 00:13:08.070 align:start position:0% hopefully everybody says no and then we 00:13:08.070 --> 00:13:10.550 align:start position:0% hopefully everybody says no and then we start<00:13:08.340> the<00:13:08.370> election<00:13:08.910> and<00:13:09.140> now<00:13:10.140> all<00:13:10.380> the 00:13:10.550 --> 00:13:10.560 align:start position:0% start the election and now all the 00:13:10.560 --> 00:13:13.460 align:start position:0% start the election and now all the voters<00:13:11.330> they<00:13:12.330> upload<00:13:12.750> their<00:13:12.780> voting<00:13:13.110> codes 00:13:13.460 --> 00:13:13.470 align:start position:0% voters they upload their voting codes 00:13:13.470 --> 00:13:14.600 align:start position:0% voters they upload their voting codes although<00:13:14.040> that's<00:13:14.160> more<00:13:14.460> of<00:13:14.520> an 00:13:14.600 --> 00:13:14.610 align:start position:0% although that's more of an 00:13:14.610 --> 00:13:16.940 align:start position:0% although that's more of an implementation<00:13:15.270> but<00:13:15.420> I'm<00:13:15.570> necessary<00:13:16.290> they 00:13:16.940 --> 00:13:16.950 align:start position:0% implementation but I'm necessary they 00:13:16.950 --> 00:13:19.580 align:start position:0% implementation but I'm necessary they log<00:13:17.160> into<00:13:17.340> their<00:13:17.550> theorem<00:13:17.910> account<00:13:18.240> and<00:13:18.590> then 00:13:19.580 --> 00:13:19.590 align:start position:0% log into their theorem account and then 00:13:19.590 --> 00:13:20.900 align:start position:0% log into their theorem account and then they<00:13:19.710> can<00:13:19.890> look<00:13:20.040> at<00:13:20.130> the<00:13:20.220> question<00:13:20.730> and 00:13:20.900 --> 00:13:20.910 align:start position:0% they can look at the question and 00:13:20.910 --> 00:13:23.120 align:start position:0% they can look at the question and register<00:13:21.540> for<00:13:21.720> the<00:13:21.780> election<00:13:22.260> now<00:13:22.890> in<00:13:23.040> this 00:13:23.120 --> 00:13:23.130 align:start position:0% register for the election now in this 00:13:23.130 --> 00:13:24.900 align:start position:0% register for the election now in this example<00:13:23.310> I'm<00:13:23.700> going<00:13:23.850> to<00:13:23.970> show<00:13:24.150> you<00:13:24.180> there 00:13:24.900 --> 00:13:24.910 align:start position:0% example I'm going to show you there 00:13:24.910 --> 00:13:26.610 align:start position:0% example I'm going to show you there actually<00:13:25.150> three<00:13:25.420> stages<00:13:25.780> to<00:13:25.990> the<00:13:26.200> protocol 00:13:26.610 --> 00:13:26.620 align:start position:0% actually three stages to the protocol 00:13:26.620 --> 00:13:28.860 align:start position:0% actually three stages to the protocol because<00:13:27.430> there's<00:13:27.790> a<00:13:27.850> third<00:13:28.330> round<00:13:28.630> you<00:13:28.780> can 00:13:28.860 --> 00:13:28.870 align:start position:0% because there's a third round you can 00:13:28.870 --> 00:13:31.290 align:start position:0% because there's a third round you can odd<00:13:29.050> to<00:13:29.620> get<00:13:29.770> around<00:13:29.980> that<00:13:30.100> adoptive<00:13:30.580> issue<00:13:30.760> so 00:13:31.290 --> 00:13:31.300 align:start position:0% odd to get around that adoptive issue so 00:13:31.300 --> 00:13:32.940 align:start position:0% odd to get around that adoptive issue so I<00:13:31.330> mentioned<00:13:31.750> the<00:13:31.810> Feiner<00:13:32.050> voter<00:13:32.350> can<00:13:32.590> see<00:13:32.770> the 00:13:32.940 --> 00:13:32.950 align:start position:0% I mentioned the Feiner voter can see the 00:13:32.950 --> 00:13:35.340 align:start position:0% I mentioned the Feiner voter can see the vote<00:13:33.130> the<00:13:33.370> tally<00:13:33.580> before<00:13:33.910> everybody<00:13:34.330> else<00:13:34.420> so 00:13:35.340 --> 00:13:35.350 align:start position:0% vote the tally before everybody else so 00:13:35.350 --> 00:13:36.810 align:start position:0% vote the tally before everybody else so what<00:13:35.440> you<00:13:35.590> can<00:13:35.710> do<00:13:35.860> is<00:13:36.010> that<00:13:36.190> everybody<00:13:36.640> can 00:13:36.810 --> 00:13:36.820 align:start position:0% what you can do is that everybody can 00:13:36.820 --> 00:13:39.510 align:start position:0% what you can do is that everybody can register<00:13:37.350> everybody<00:13:38.350> can<00:13:38.560> commit<00:13:38.950> to<00:13:39.370> their 00:13:39.510 --> 00:13:39.520 align:start position:0% register everybody can commit to their 00:13:39.520 --> 00:13:41.280 align:start position:0% register everybody can commit to their encrypted<00:13:39.910> vote<00:13:40.090> and<00:13:40.720> then<00:13:40.810> once<00:13:40.990> everyone 00:13:41.280 --> 00:13:41.290 align:start position:0% encrypted vote and then once everyone 00:13:41.290 --> 00:13:43.500 align:start position:0% encrypted vote and then once everyone actually<00:13:41.440> causes<00:13:42.040> their<00:13:42.220> vote<00:13:42.460> you<00:13:43.210> can't 00:13:43.500 --> 00:13:43.510 align:start position:0% actually causes their vote you can't 00:13:43.510 --> 00:13:45.390 align:start position:0% actually causes their vote you can't change<00:13:43.720> your<00:13:43.870> mind<00:13:44.200> if<00:13:44.530> you<00:13:44.800> can<00:13:44.950> compute<00:13:45.310> the 00:13:45.390 --> 00:13:45.400 align:start position:0% change your mind if you can compute the 00:13:45.400 --> 00:13:47.640 align:start position:0% change your mind if you can compute the tally<00:13:45.580> so<00:13:46.450> it<00:13:46.570> really<00:13:46.750> depends<00:13:47.170> if<00:13:47.320> you<00:13:47.410> think 00:13:47.640 --> 00:13:47.650 align:start position:0% tally so it really depends if you think 00:13:47.650 --> 00:13:49.230 align:start position:0% tally so it really depends if you think that's<00:13:47.830> a<00:13:47.920> big<00:13:48.070> issue<00:13:48.280> it<00:13:48.640> was<00:13:48.820> a<00:13:48.850> big<00:13:49.060> issue 00:13:49.230 --> 00:13:49.240 align:start position:0% that's a big issue it was a big issue 00:13:49.240 --> 00:13:50.790 align:start position:0% that's a big issue it was a big issue that<00:13:49.420> the<00:13:49.660> fan<00:13:49.840> of<00:13:49.990> voter<00:13:50.170> can<00:13:50.350> compute<00:13:50.710> the 00:13:50.790 --> 00:13:50.800 align:start position:0% that the fan of voter can compute the 00:13:50.800 --> 00:13:52.200 align:start position:0% that the fan of voter can compute the tally<00:13:51.040> before<00:13:51.400> everybody<00:13:51.820> else 00:13:52.200 --> 00:13:52.210 align:start position:0% tally before everybody else 00:13:52.210 --> 00:13:55.110 align:start position:0% tally before everybody else yeah<00:13:52.720> that's<00:13:53.110> out<00:13:53.290> third<00:13:53.650> round<00:13:53.980> if<00:13:54.400> you<00:13:54.910> don't 00:13:55.110 --> 00:13:55.120 align:start position:0% yeah that's out third round if you don't 00:13:55.120 --> 00:13:56.820 align:start position:0% yeah that's out third round if you don't think<00:13:55.300> that's<00:13:55.360> a<00:13:55.510> big<00:13:55.660> issue<00:13:55.810> you<00:13:56.440> keep<00:13:56.680> the 00:13:56.820 --> 00:13:56.830 align:start position:0% think that's a big issue you keep the 00:13:56.830 --> 00:13:58.830 align:start position:0% think that's a big issue you keep the two<00:13:57.010> rounds<00:13:57.520> you<00:13:57.760> know<00:13:57.880> you<00:13:57.940> vote<00:13:58.300> a<00:13:58.570> new 00:13:58.830 --> 00:13:58.840 align:start position:0% two rounds you know you vote a new 00:13:58.840 --> 00:14:01.190 align:start position:0% two rounds you know you vote a new register<00:13:59.290> so<00:13:59.920> now<00:14:00.040> every<00:14:00.190> voters<00:14:00.520> you<00:14:00.670> know 00:14:01.190 --> 00:14:01.200 align:start position:0% register so now every voters you know 00:14:01.200 --> 00:14:03.090 align:start position:0% register so now every voters you know yeah<00:14:02.200> they're<00:14:02.350> registering<00:14:02.800> for<00:14:03.040> the 00:14:03.090 --> 00:14:03.100 align:start position:0% yeah they're registering for the 00:14:03.100 --> 00:14:08.280 align:start position:0% yeah they're registering for the election<00:14:04.110> yep<00:14:05.140> and<00:14:05.350> then<00:14:06.130> eventually<00:14:07.290> yeah 00:14:08.280 --> 00:14:08.290 align:start position:0% election yep and then eventually yeah 00:14:08.290 --> 00:14:09.750 align:start position:0% election yep and then eventually yeah neither<00:14:08.530> basically<00:14:09.130> cost<00:14:09.340> in<00:14:09.460> their<00:14:09.580> vote 00:14:09.750 --> 00:14:09.760 align:start position:0% neither basically cost in their vote 00:14:09.760 --> 00:14:11.010 align:start position:0% neither basically cost in their vote while<00:14:10.030> they're<00:14:10.180> committing<00:14:10.600> to<00:14:10.750> their<00:14:10.870> vote 00:14:11.010 --> 00:14:11.020 align:start position:0% while they're committing to their vote 00:14:11.020 --> 00:14:13.440 align:start position:0% while they're committing to their vote so<00:14:11.260> they're<00:14:11.380> saying<00:14:11.590> yes<00:14:11.800> no<00:14:12.160> and<00:14:12.340> yes<00:14:12.520> so 00:14:13.440 --> 00:14:13.450 align:start position:0% so they're saying yes no and yes so 00:14:13.450 --> 00:14:14.820 align:start position:0% so they're saying yes no and yes so these<00:14:13.570> guys<00:14:13.780> are<00:14:13.930> going<00:14:14.080> to<00:14:14.140> say<00:14:14.260> yes<00:14:14.440> Satoshi 00:14:14.820 --> 00:14:14.830 align:start position:0% these guys are going to say yes Satoshi 00:14:14.830 --> 00:14:16.470 align:start position:0% these guys are going to say yes Satoshi Nakamoto<00:14:15.310> should<00:14:15.580> reveal<00:14:15.850> his<00:14:16.060> real<00:14:16.090> world 00:14:16.470 --> 00:14:16.480 align:start position:0% Nakamoto should reveal his real world 00:14:16.480 --> 00:14:20.040 align:start position:0% Nakamoto should reveal his real world identity<00:14:18.000> I'm<00:14:19.000> neither<00:14:19.270> going<00:14:19.540> to<00:14:19.630> cast<00:14:19.840> their 00:14:20.040 --> 00:14:20.050 align:start position:0% identity I'm neither going to cast their 00:14:20.050 --> 00:14:23.700 align:start position:0% identity I'm neither going to cast their vote<00:14:20.820> and<00:14:21.820> I<00:14:22.540> know<00:14:22.600> the<00:14:22.810> designs<00:14:23.110> horrible<00:14:23.620> I'm 00:14:23.700 --> 00:14:23.710 align:start position:0% vote and I know the designs horrible I'm 00:14:23.710 --> 00:14:27.090 align:start position:0% vote and I know the designs horrible I'm not<00:14:23.830> really<00:14:23.950> a<00:14:24.040> good<00:14:24.250> designer<00:14:26.100> graphic 00:14:27.090 --> 00:14:27.100 align:start position:0% not really a good designer graphic 00:14:27.100 --> 00:14:30.690 align:start position:0% not really a good designer graphic design<00:14:27.550> was<00:14:27.730> never<00:14:27.940> my<00:14:28.120> forte<00:14:28.360> but<00:14:29.400> now<00:14:30.400> that 00:14:30.690 --> 00:14:30.700 align:start position:0% design was never my forte but now that 00:14:30.700 --> 00:14:33.180 align:start position:0% design was never my forte but now that all<00:14:30.730> the<00:14:31.030> votes<00:14:31.210> have<00:14:31.270> been<00:14:31.360> cast<00:14:31.630> anyway<00:14:32.190> we 00:14:33.180 --> 00:14:33.190 align:start position:0% all the votes have been cast anyway we 00:14:33.190 --> 00:14:34.620 align:start position:0% all the votes have been cast anyway we will<00:14:33.340> eventually<00:14:33.640> be<00:14:33.850> able<00:14:33.970> to<00:14:34.120> see<00:14:34.330> the<00:14:34.450> tally 00:14:34.620 --> 00:14:34.630 align:start position:0% will eventually be able to see the tally 00:14:34.630 --> 00:14:37.260 align:start position:0% will eventually be able to see the tally so<00:14:35.440> the<00:14:35.560> election<00:14:35.770> administrator<00:14:36.460> will 00:14:37.260 --> 00:14:37.270 align:start position:0% so the election administrator will 00:14:37.270 --> 00:14:39.060 align:start position:0% so the election administrator will eventually<00:14:37.720> pop<00:14:37.930> up<00:14:38.170> and<00:14:38.410> he'll<00:14:38.560> say<00:14:38.740> okay<00:14:38.860> I 00:14:39.060 --> 00:14:39.070 align:start position:0% eventually pop up and he'll say okay I 00:14:39.070 --> 00:14:42.530 align:start position:0% eventually pop up and he'll say okay I want<00:14:39.430> you<00:14:39.520> to<00:14:39.580> compute<00:14:39.970> the<00:14:40.030> tally<00:14:40.240> etherium 00:14:42.530 --> 00:14:42.540 align:start position:0% want you to compute the tally etherium 00:14:42.540 --> 00:14:46.440 align:start position:0% want you to compute the tally etherium so<00:14:43.540> he<00:14:43.630> does<00:14:43.810> it<00:14:44.400> and<00:14:45.400> I<00:14:45.820> should<00:14:45.970> hopefully<00:14:46.300> say 00:14:46.440 --> 00:14:46.450 align:start position:0% so he does it and I should hopefully say 00:14:46.450 --> 00:14:48.980 align:start position:0% so he does it and I should hopefully say yep<00:14:46.630> two<00:14:46.870> years<00:14:47.110> foots<00:14:47.350> I'm<00:14:47.620> one<00:14:48.130> no<00:14:48.310> vote<00:14:48.340> and 00:14:48.980 --> 00:14:48.990 align:start position:0% yep two years foots I'm one no vote and 00:14:48.990 --> 00:14:51.420 align:start position:0% yep two years foots I'm one no vote and there's<00:14:49.990> actually<00:14:50.260> a<00:14:50.290> live<00:14:50.470> feed<00:14:50.800> pH<00:14:51.130> as<00:14:51.280> well 00:14:51.420 --> 00:14:51.430 align:start position:0% there's actually a live feed pH as well 00:14:51.430 --> 00:14:53.100 align:start position:0% there's actually a live feed pH as well where<00:14:52.120> we<00:14:52.210> can<00:14:52.330> actually<00:14:52.480> watch<00:14:52.750> the<00:14:52.930> election 00:14:53.100 --> 00:14:53.110 align:start position:0% where we can actually watch the election 00:14:53.110 --> 00:14:55.080 align:start position:0% where we can actually watch the election in<00:14:53.380> real<00:14:53.530> time<00:14:53.860> because<00:14:54.520> what's<00:14:54.700> really<00:14:54.940> cool 00:14:55.080 --> 00:14:55.090 align:start position:0% in real time because what's really cool 00:14:55.090 --> 00:14:56.790 align:start position:0% in real time because what's really cool about<00:14:55.150> this<00:14:55.480> system<00:14:55.900> is<00:14:56.050> that<00:14:56.080> you<00:14:56.440> can 00:14:56.790 --> 00:14:56.800 align:start position:0% about this system is that you can 00:14:56.800 --> 00:14:58.380 align:start position:0% about this system is that you can actually<00:14:57.100> registered<00:14:57.820> where<00:14:58.000> you<00:14:58.120> can<00:14:58.240> see 00:14:58.380 --> 00:14:58.390 align:start position:0% actually registered where you can see 00:14:58.390 --> 00:15:00.900 align:start position:0% actually registered where you can see that<00:14:58.540> Patrick<00:14:58.960> has<00:14:59.080> cast<00:14:59.350> his<00:14:59.500> vote<00:14:59.830> so<00:15:00.820> you 00:15:00.900 --> 00:15:00.910 align:start position:0% that Patrick has cast his vote so you 00:15:00.910 --> 00:15:02.460 align:start position:0% that Patrick has cast his vote so you can<00:15:01.000> actually<00:15:01.120> see<00:15:01.810> what's<00:15:02.080> a<00:15:02.170> theorem 00:15:02.460 --> 00:15:02.470 align:start position:0% can actually see what's a theorem 00:15:02.470 --> 00:15:04.200 align:start position:0% can actually see what's a theorem accounts<00:15:02.800> have<00:15:02.920> voted<00:15:03.220> but<00:15:03.640> you<00:15:03.760> can't<00:15:04.030> see 00:15:04.200 --> 00:15:04.210 align:start position:0% accounts have voted but you can't see 00:15:04.210 --> 00:15:06.540 align:start position:0% accounts have voted but you can't see their<00:15:04.420> vote<00:15:04.600> and<00:15:04.810> that<00:15:05.500> is<00:15:05.650> the<00:15:05.860> end<00:15:06.310> of<00:15:06.460> my 00:15:06.540 --> 00:15:06.550 align:start position:0% their vote and that is the end of my 00:15:06.550 --> 00:15:10.160 align:start position:0% their vote and that is the end of my video 00:15:10.160 --> 00:15:10.170 align:start position:0% 00:15:10.170 --> 00:15:14.139 align:start position:0% [Applause] 00:15:14.139 --> 00:15:14.149 align:start position:0% [Applause] 00:15:14.149 --> 00:15:16.999 align:start position:0% [Applause] and<00:15:15.149> I<00:15:15.269> just<00:15:15.419> want<00:15:15.599> the<00:15:15.719> ended<00:15:16.139> to<00:15:16.229> say<00:15:16.439> that<00:15:16.709> it 00:15:16.999 --> 00:15:17.009 align:start position:0% and I just want the ended to say that it 00:15:17.009 --> 00:15:19.279 align:start position:0% and I just want the ended to say that it is<00:15:17.279> on<00:15:17.459> github<00:15:17.729> and<00:15:18.269> I've<00:15:18.659> been<00:15:18.809> really<00:15:19.109> lucky 00:15:19.279 --> 00:15:19.289 align:start position:0% is on github and I've been really lucky 00:15:19.289 --> 00:15:21.409 align:start position:0% is on github and I've been really lucky to<00:15:19.529> say<00:15:19.679> that<00:15:19.859> it's<00:15:19.949> night<00:15:20.099> house<00:15:20.249> 113<00:15:21.089> stars 00:15:21.409 --> 00:15:21.419 align:start position:0% to say that it's night house 113 stars 00:15:21.419 --> 00:15:24.349 align:start position:0% to say that it's night house 113 stars which<00:15:22.169> for<00:15:22.439> me<00:15:22.529> was<00:15:22.559> amazing<00:15:23.399> because<00:15:24.119> when<00:15:24.299> I 00:15:24.349 --> 00:15:24.359 align:start position:0% which for me was amazing because when I 00:15:24.359 --> 00:15:26.239 align:start position:0% which for me was amazing because when I did<00:15:24.449> this<00:15:24.719> last<00:15:24.899> summer<00:15:25.199> I<00:15:25.469> was<00:15:25.799> finishing<00:15:26.129> my 00:15:26.239 --> 00:15:26.249 align:start position:0% did this last summer I was finishing my 00:15:26.249 --> 00:15:28.339 align:start position:0% did this last summer I was finishing my PhD<00:15:26.369> and<00:15:27.029> I<00:15:27.419> wanted<00:15:27.659> to<00:15:27.749> build<00:15:27.929> something<00:15:28.079> that 00:15:28.339 --> 00:15:28.349 align:start position:0% PhD and I wanted to build something that 00:15:28.349 --> 00:15:30.259 align:start position:0% PhD and I wanted to build something that people<00:15:28.589> could<00:15:28.829> use<00:15:28.889> in<00:15:29.129> the<00:15:29.219> community<00:15:29.369> and<00:15:29.969> it 00:15:30.259 --> 00:15:30.269 align:start position:0% people could use in the community and it 00:15:30.269 --> 00:15:31.249 align:start position:0% people could use in the community and it looks<00:15:30.419> like<00:15:30.509> the<00:15:30.659> people<00:15:30.899> have<00:15:30.989> actually 00:15:31.249 --> 00:15:31.259 align:start position:0% looks like the people have actually 00:15:31.259 --> 00:15:33.169 align:start position:0% looks like the people have actually picked<00:15:31.409> it<00:15:31.619> up<00:15:31.709> and<00:15:31.859> they're<00:15:32.009> trying<00:15:32.189> to<00:15:32.249> do 00:15:33.169 --> 00:15:33.179 align:start position:0% picked it up and they're trying to do 00:15:33.179 --> 00:15:34.729 align:start position:0% picked it up and they're trying to do cool<00:15:33.479> things<00:15:33.509> of<00:15:33.869> it<00:15:33.989> so<00:15:34.109> thank<00:15:34.319> you<00:15:34.409> very<00:15:34.559> much 00:15:34.729 --> 00:15:34.739 align:start position:0% cool things of it so thank you very much 00:15:34.739 --> 00:15:37.940 align:start position:0% cool things of it so thank you very much guys<00:15:34.919> for 00:15:37.940 --> 00:15:37.950 align:start position:0% 00:15:37.950 --> 00:15:45.270 align:start position:0% [Applause] 00:15:45.270 --> 00:15:45.280 align:start position:0% 00:15:45.280 --> 00:15:52.860 align:start position:0% [Music]