WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:15.270 align:start position:0% [Music] 00:00:15.270 --> 00:00:15.280 align:start position:0% [Music] 00:00:15.280 --> 00:00:20.200 align:start position:0% [Music] hi<00:00:16.280> guys<00:00:16.640> I'm<00:00:17.480> a<00:00:17.630> researcher<00:00:18.320> at<00:00:18.380> UCL<00:00:18.950> and<00:00:19.310> for 00:00:20.200 --> 00:00:20.210 align:start position:0% hi guys I'm a researcher at UCL and for 00:00:20.210 --> 00:00:21.490 align:start position:0% hi guys I'm a researcher at UCL and for the<00:00:20.270> past<00:00:20.510> year<00:00:20.900> I've<00:00:20.990> been<00:00:21.140> building<00:00:21.320> this 00:00:21.490 --> 00:00:21.500 align:start position:0% the past year I've been building this 00:00:21.500 --> 00:00:24.940 align:start position:0% the past year I've been building this cryptography<00:00:22.190> library<00:00:22.610> and<00:00:23.830> there's<00:00:24.830> gonna 00:00:24.940 --> 00:00:24.950 align:start position:0% cryptography library and there's gonna 00:00:24.950 --> 00:00:27.250 align:start position:0% cryptography library and there's gonna be<00:00:25.130> a<00:00:25.160> disclaimer<00:00:25.580> for<00:00:25.760> this<00:00:26.030> talk<00:00:26.360> I'm<00:00:26.840> not 00:00:27.250 --> 00:00:27.260 align:start position:0% be a disclaimer for this talk I'm not 00:00:27.260 --> 00:00:30.280 align:start position:0% be a disclaimer for this talk I'm not going<00:00:27.500> to<00:00:27.590> go<00:00:27.710> deep<00:00:27.950> into<00:00:28.190> the<00:00:28.400> math<00:00:28.660> the<00:00:29.660> Z<00:00:30.050> cos 00:00:30.280 --> 00:00:30.290 align:start position:0% going to go deep into the math the Z cos 00:00:30.290 --> 00:00:31.930 align:start position:0% going to go deep into the math the Z cos foundation<00:00:30.860> how<00:00:31.070> Privett<00:00:31.490> is<00:00:31.640> some<00:00:31.789> useful 00:00:31.930 --> 00:00:31.940 align:start position:0% foundation how Privett is some useful 00:00:31.940 --> 00:00:34.120 align:start position:0% foundation how Privett is some useful workshops<00:00:32.539> that<00:00:32.629> I'll<00:00:32.750> do<00:00:32.899> that<00:00:33.110> later<00:00:33.350> on<00:00:33.469> and 00:00:34.120 --> 00:00:34.130 align:start position:0% workshops that I'll do that later on and 00:00:34.130 --> 00:00:35.590 align:start position:0% workshops that I'll do that later on and I<00:00:34.220> only<00:00:34.370> have<00:00:34.520> 20<00:00:34.880> minutes<00:00:34.910> and<00:00:35.300> the<00:00:35.450> teach 00:00:35.590 --> 00:00:35.600 align:start position:0% I only have 20 minutes and the teach 00:00:35.600 --> 00:00:37.030 align:start position:0% I only have 20 minutes and the teach cryptography<00:00:36.230> you<00:00:36.290> need<00:00:36.470> more<00:00:36.620> than<00:00:36.770> 20 00:00:37.030 --> 00:00:37.040 align:start position:0% cryptography you need more than 20 00:00:37.040 --> 00:00:39.220 align:start position:0% cryptography you need more than 20 minutes<00:00:37.280> so<00:00:38.000> instead<00:00:38.360> what<00:00:38.480> I<00:00:38.540> want<00:00:38.810> to<00:00:38.930> do<00:00:39.079> is 00:00:39.220 --> 00:00:39.230 align:start position:0% minutes so instead what I want to do is 00:00:39.230 --> 00:00:40.090 align:start position:0% minutes so instead what I want to do is they<00:00:39.320> want<00:00:39.500> to<00:00:39.560> leave<00:00:39.739> you<00:00:39.829> with<00:00:39.980> an 00:00:40.090 --> 00:00:40.100 align:start position:0% they want to leave you with an 00:00:40.100 --> 00:00:42.460 align:start position:0% they want to leave you with an impression<00:00:40.489> that<00:00:41.140> cryptography<00:00:42.140> can<00:00:42.320> be 00:00:42.460 --> 00:00:42.470 align:start position:0% impression that cryptography can be 00:00:42.470 --> 00:00:44.850 align:start position:0% impression that cryptography can be really<00:00:42.829> useful<00:00:43.070> for<00:00:43.280> smart<00:00:43.670> contracts<00:00:44.180> if 00:00:44.850 --> 00:00:44.860 align:start position:0% really useful for smart contracts if 00:00:44.860 --> 00:00:48.190 align:start position:0% really useful for smart contracts if nearly<00:00:45.860> essential<00:00:46.399> as<00:00:46.489> well<00:00:46.670> but<00:00:47.660> first<00:00:47.870> what 00:00:48.190 --> 00:00:48.200 align:start position:0% nearly essential as well but first what 00:00:48.200 --> 00:00:51.010 align:start position:0% nearly essential as well but first what is<00:00:48.230> cryptography<00:00:49.060> well<00:00:50.060> when<00:00:50.329> I<00:00:50.360> talk<00:00:50.690> to<00:00:50.870> non 00:00:51.010 --> 00:00:51.020 align:start position:0% is cryptography well when I talk to non 00:00:51.020 --> 00:00:53.080 align:start position:0% is cryptography well when I talk to non experts<00:00:51.530> they<00:00:52.130> tend<00:00:52.489> to<00:00:52.579> say<00:00:52.820> that 00:00:53.080 --> 00:00:53.090 align:start position:0% experts they tend to say that 00:00:53.090 --> 00:00:55.270 align:start position:0% experts they tend to say that cryptography<00:00:54.020> is<00:00:54.079> about<00:00:54.350> designing<00:00:54.680> ciphers 00:00:55.270 --> 00:00:55.280 align:start position:0% cryptography is about designing ciphers 00:00:55.280 --> 00:00:58.240 align:start position:0% cryptography is about designing ciphers ie<00:00:55.940> encryption<00:00:56.809> and<00:00:56.899> decryption<00:00:57.250> but 00:00:58.240 --> 00:00:58.250 align:start position:0% ie encryption and decryption but 00:00:58.250 --> 00:00:59.500 align:start position:0% ie encryption and decryption but hopefully<00:00:58.610> has<00:00:58.700> some<00:00:58.880> people<00:00:59.059> in<00:00:59.210> this<00:00:59.300> room 00:00:59.500 --> 00:00:59.510 align:start position:0% hopefully has some people in this room 00:00:59.510 --> 00:01:01.840 align:start position:0% hopefully has some people in this room know<00:00:59.570> over<00:01:00.469> the<00:01:00.559> past<00:01:00.800> 30<00:01:01.130> years<00:01:01.250> and<00:01:01.610> if<00:01:01.760> the 00:01:01.840 --> 00:01:01.850 align:start position:0% know over the past 30 years and if the 00:01:01.850 --> 00:01:04.149 align:start position:0% know over the past 30 years and if the rise<00:01:02.059> of<00:01:02.210> the<00:01:02.360> internet<00:01:02.860> cryptography<00:01:03.860> is<00:01:03.980> so 00:01:04.149 --> 00:01:04.159 align:start position:0% rise of the internet cryptography is so 00:01:04.159 --> 00:01:06.280 align:start position:0% rise of the internet cryptography is so much<00:01:04.339> more<00:01:04.549> it's<00:01:05.329> a<00:01:05.449> bit<00:01:05.570> of<00:01:05.690> santak<00:01:06.049> hitting 00:01:06.280 --> 00:01:06.290 align:start position:0% much more it's a bit of santak hitting 00:01:06.290 --> 00:01:07.390 align:start position:0% much more it's a bit of santak hitting people<00:01:06.560> on<00:01:06.680> the<00:01:06.799> Internet 00:01:07.390 --> 00:01:07.400 align:start position:0% people on the Internet 00:01:07.400 --> 00:01:10.090 align:start position:0% people on the Internet ie<00:01:07.790> you're<00:01:08.240> a<00:01:08.270> theorem<00:01:08.630> account<00:01:08.930> or<00:01:09.170> endorsed 00:01:10.090 --> 00:01:10.100 align:start position:0% ie you're a theorem account or endorsed 00:01:10.100 --> 00:01:13.149 align:start position:0% ie you're a theorem account or endorsed an<00:01:10.280> information<00:01:11.060> ie<00:01:11.659> a<00:01:12.170> digital<00:01:12.650> signature 00:01:13.149 --> 00:01:13.159 align:start position:0% an information ie a digital signature 00:01:13.159 --> 00:01:14.500 align:start position:0% an information ie a digital signature you<00:01:13.610> know<00:01:13.729> that's<00:01:13.940> authorized<00:01:14.390> your 00:01:14.500 --> 00:01:14.510 align:start position:0% you know that's authorized your 00:01:14.510 --> 00:01:16.930 align:start position:0% you know that's authorized your transaction<00:01:15.140> span<00:01:15.409> some<00:01:15.590> coins<00:01:15.860> and<00:01:16.190> even 00:01:16.930 --> 00:01:16.940 align:start position:0% transaction span some coins and even 00:01:16.940 --> 00:01:18.940 align:start position:0% transaction span some coins and even more<00:01:17.210> it's<00:01:17.510> about<00:01:18.049> building<00:01:18.290> publicly 00:01:18.940 --> 00:01:18.950 align:start position:0% more it's about building publicly 00:01:18.950 --> 00:01:21.399 align:start position:0% more it's about building publicly verifiable<00:01:19.210> protocols<00:01:20.210> where<00:01:20.869> of<00:01:21.020> a<00:01:21.110> group<00:01:21.320> of 00:01:21.399 --> 00:01:21.409 align:start position:0% verifiable protocols where of a group of 00:01:21.409 --> 00:01:23.680 align:start position:0% verifiable protocols where of a group of people<00:01:21.619> run<00:01:22.340> a<00:01:22.369> protocol<00:01:22.909> and<00:01:23.420> I'm<00:01:23.540> not 00:01:23.680 --> 00:01:23.690 align:start position:0% people run a protocol and I'm not 00:01:23.690 --> 00:01:26.050 align:start position:0% people run a protocol and I'm not involved<00:01:24.020> they<00:01:24.770> can<00:01:24.979> send<00:01:25.250> me<00:01:25.280> the<00:01:25.460> transcript 00:01:26.050 --> 00:01:26.060 align:start position:0% involved they can send me the transcript 00:01:26.060 --> 00:01:28.450 align:start position:0% involved they can send me the transcript and<00:01:26.360> I<00:01:26.720> can<00:01:26.900> have<00:01:27.080> fifth<00:01:27.409> or<00:01:27.979> actually<00:01:28.250> I<00:01:28.280> can 00:01:28.450 --> 00:01:28.460 align:start position:0% and I can have fifth or actually I can 00:01:28.460 --> 00:01:30.490 align:start position:0% and I can have fifth or actually I can be<00:01:28.549> certain<00:01:28.820> that<00:01:29.119> that<00:01:29.630> protocol<00:01:30.140> was<00:01:30.320> run 00:01:30.490 --> 00:01:30.500 align:start position:0% be certain that that protocol was run 00:01:30.500 --> 00:01:33.850 align:start position:0% be certain that that protocol was run correctly<00:01:31.240> so<00:01:32.240> as<00:01:32.390> I<00:01:32.420> kept<00:01:32.630> tog<00:01:32.810> refer<00:01:33.110> when 00:01:33.850 --> 00:01:33.860 align:start position:0% correctly so as I kept tog refer when 00:01:33.860 --> 00:01:35.410 align:start position:0% correctly so as I kept tog refer when you<00:01:33.950> look<00:01:34.100> at<00:01:34.220> aetherium<00:01:34.610> you<00:01:34.909> wonder<00:01:35.210> what 00:01:35.410 --> 00:01:35.420 align:start position:0% you look at aetherium you wonder what 00:01:35.420 --> 00:01:36.550 align:start position:0% you look at aetherium you wonder what does<00:01:35.630> aetherium<00:01:35.960> offer 00:01:36.550 --> 00:01:36.560 align:start position:0% does aetherium offer 00:01:36.560 --> 00:01:39.670 align:start position:0% does aetherium offer well<00:01:37.189> another<00:01:37.520> goal<00:01:37.880> of<00:01:38.150> cryptography<00:01:38.810> is<00:01:38.990> to 00:01:39.670 --> 00:01:39.680 align:start position:0% well another goal of cryptography is to 00:01:39.680 --> 00:01:42.070 align:start position:0% well another goal of cryptography is to minimize<00:01:40.100> Trust<00:01:40.520> we<00:01:41.060> want<00:01:41.330> to<00:01:41.420> remove<00:01:41.630> as<00:01:41.840> much 00:01:42.070 --> 00:01:42.080 align:start position:0% minimize Trust we want to remove as much 00:01:42.080 --> 00:01:44.950 align:start position:0% minimize Trust we want to remove as much trust<00:01:42.439> from<00:01:42.619> this<00:01:42.770> system<00:01:42.950> as<00:01:43.189> we<00:01:43.310> can<00:01:43.780> but<00:01:44.780> in 00:01:44.950 --> 00:01:44.960 align:start position:0% trust from this system as we can but in 00:01:44.960 --> 00:01:46.600 align:start position:0% trust from this system as we can but in every<00:01:45.380> system<00:01:45.619> there's<00:01:45.979> always<00:01:46.130> a<00:01:46.250> little<00:01:46.430> bit 00:01:46.600 --> 00:01:46.610 align:start position:0% every system there's always a little bit 00:01:46.610 --> 00:01:48.899 align:start position:0% every system there's always a little bit of<00:01:46.729> trust<00:01:46.909> so<00:01:47.750> when<00:01:47.930> we<00:01:48.020> design<00:01:48.320> a<00:01:48.350> system 00:01:48.899 --> 00:01:48.909 align:start position:0% of trust so when we design a system 00:01:48.909 --> 00:01:51.070 align:start position:0% of trust so when we design a system sometimes<00:01:49.909> there's<00:01:50.090> a<00:01:50.150> trusted<00:01:50.509> third<00:01:50.659> party 00:01:51.070 --> 00:01:51.080 align:start position:0% sometimes there's a trusted third party 00:01:51.080 --> 00:01:52.960 align:start position:0% sometimes there's a trusted third party but<00:01:51.680> what's<00:01:51.830> really<00:01:51.979> cool<00:01:52.280> about<00:01:52.340> a<00:01:52.549> theorem 00:01:52.960 --> 00:01:52.970 align:start position:0% but what's really cool about a theorem 00:01:52.970 --> 00:01:55.030 align:start position:0% but what's really cool about a theorem is<00:01:53.090> that<00:01:53.119> a<00:01:53.509> smart<00:01:54.140> contract<00:01:54.380> can<00:01:54.799> be<00:01:54.920> your 00:01:55.030 --> 00:01:55.040 align:start position:0% is that a smart contract can be your 00:01:55.040 --> 00:01:58.560 align:start position:0% is that a smart contract can be your trusted<00:01:55.400> third<00:01:55.580> party<00:01:55.970> with<00:01:56.570> publix<00:01:57.020> did<00:01:57.259> so 00:01:58.560 --> 00:01:58.570 align:start position:0% trusted third party with publix did so 00:01:58.570 --> 00:02:00.819 align:start position:0% trusted third party with publix did so because<00:01:59.570> our<00:01:59.659> public's<00:02:00.200> did<00:02:00.350> and<00:02:00.619> it's<00:02:00.770> a 00:02:00.819 --> 00:02:00.829 align:start position:0% because our public's did and it's a 00:02:00.829 --> 00:02:03.280 align:start position:0% because our public's did and it's a little<00:02:00.950> robot<00:02:01.340> over<00:02:01.549> there<00:02:01.729> it<00:02:02.420> gossips<00:02:03.020> it 00:02:03.280 --> 00:02:03.290 align:start position:0% little robot over there it gossips it 00:02:03.290 --> 00:02:05.890 align:start position:0% little robot over there it gossips it reveals<00:02:04.040> all<00:02:04.220> our<00:02:04.400> secrets<00:02:04.610> but<00:02:05.600> it<00:02:05.720> never 00:02:05.890 --> 00:02:05.900 align:start position:0% reveals all our secrets but it never 00:02:05.900 --> 00:02:08.080 align:start position:0% reveals all our secrets but it never modifies<00:02:06.439> the<00:02:06.619> protocol<00:02:07.100> and<00:02:07.310> it<00:02:07.759> will<00:02:07.850> always 00:02:08.080 --> 00:02:08.090 align:start position:0% modifies the protocol and it will always 00:02:08.090 --> 00:02:10.600 align:start position:0% modifies the protocol and it will always faithfully<00:02:08.810> execute<00:02:09.409> our<00:02:09.649> protocol<00:02:10.340> in<00:02:10.489> our 00:02:10.600 --> 00:02:10.610 align:start position:0% faithfully execute our protocol in our 00:02:10.610 --> 00:02:13.720 align:start position:0% faithfully execute our protocol in our behalf<00:02:10.959> Ana's<00:02:11.959> atomic<00:02:12.440> either<00:02:13.069> it<00:02:13.340> runs<00:02:13.550> the 00:02:13.720 --> 00:02:13.730 align:start position:0% behalf Ana's atomic either it runs the 00:02:13.730 --> 00:02:15.190 align:start position:0% behalf Ana's atomic either it runs the function<00:02:14.150> or<00:02:14.300> it<00:02:14.480> won't 00:02:15.190 --> 00:02:15.200 align:start position:0% function or it won't 00:02:15.200 --> 00:02:16.839 align:start position:0% function or it won't I'm<00:02:15.290> using<00:02:15.560> smart<00:02:15.950> contracts<00:02:16.430> we<00:02:16.550> can<00:02:16.700> build 00:02:16.839 --> 00:02:16.849 align:start position:0% I'm using smart contracts we can build 00:02:16.849 --> 00:02:19.720 align:start position:0% I'm using smart contracts we can build really<00:02:17.120> cool<00:02:17.239> things<00:02:17.690> but<00:02:18.620> first<00:02:18.890> let's 00:02:19.720 --> 00:02:19.730 align:start position:0% really cool things but first let's 00:02:19.730 --> 00:02:21.990 align:start position:0% really cool things but first let's consider<00:02:20.120> a<00:02:20.269> really<00:02:20.599> simple<00:02:21.050> example 00:02:21.990 --> 00:02:22.000 align:start position:0% consider a really simple example 00:02:22.000 --> 00:02:23.199 align:start position:0% consider a really simple example rock-paper-scissors 00:02:23.199 --> 00:02:23.209 align:start position:0% rock-paper-scissors 00:02:23.209 --> 00:02:25.119 align:start position:0% rock-paper-scissors unless<00:02:23.660> considered<00:02:23.900> where<00:02:24.379> we<00:02:24.470> don't<00:02:24.739> use<00:02:24.920> any 00:02:25.119 --> 00:02:25.129 align:start position:0% unless considered where we don't use any 00:02:25.129 --> 00:02:28.150 align:start position:0% unless considered where we don't use any cryptography<00:02:26.140> so<00:02:27.140> our<00:02:27.290> contract<00:02:27.890> is<00:02:28.069> a 00:02:28.150 --> 00:02:28.160 align:start position:0% cryptography so our contract is a 00:02:28.160 --> 00:02:30.610 align:start position:0% cryptography so our contract is a matchmaking<00:02:28.760> service<00:02:28.819> if<00:02:29.390> I<00:02:30.019> want<00:02:30.260> to<00:02:30.319> start<00:02:30.530> a 00:02:30.610 --> 00:02:30.620 align:start position:0% matchmaking service if I want to start a 00:02:30.620 --> 00:02:32.860 align:start position:0% matchmaking service if I want to start a game<00:02:30.800> for<00:02:31.040> rock-paper-scissors<00:02:31.220> I<00:02:32.120> can<00:02:32.630> start 00:02:32.860 --> 00:02:32.870 align:start position:0% game for rock-paper-scissors I can start 00:02:32.870 --> 00:02:33.430 align:start position:0% game for rock-paper-scissors I can start a<00:02:32.959> game 00:02:33.430 --> 00:02:33.440 align:start position:0% a game 00:02:33.440 --> 00:02:35.650 align:start position:0% a game somebody<00:02:34.220> can<00:02:34.430> feign<00:02:34.670> my<00:02:34.880> game<00:02:35.150> on<00:02:35.269> the<00:02:35.390> smart 00:02:35.650 --> 00:02:35.660 align:start position:0% somebody can feign my game on the smart 00:02:35.660 --> 00:02:38.199 align:start position:0% somebody can feign my game on the smart contract<00:02:35.840> and<00:02:36.410> then<00:02:37.370> they<00:02:37.519> can<00:02:37.670> play<00:02:37.849> against 00:02:38.199 --> 00:02:38.209 align:start position:0% contract and then they can play against 00:02:38.209 --> 00:02:41.350 align:start position:0% contract and then they can play against me<00:02:38.650> so<00:02:39.650> Alice<00:02:40.099> with<00:02:40.340> the<00:02:40.459> little<00:02:40.730> Mexican<00:02:40.940> hut 00:02:41.350 --> 00:02:41.360 align:start position:0% me so Alice with the little Mexican hut 00:02:41.360 --> 00:02:43.839 align:start position:0% me so Alice with the little Mexican hut she<00:02:41.660> starts<00:02:42.650> a<00:02:42.739> game<00:02:42.769> I'm<00:02:43.220> because<00:02:43.640> we're<00:02:43.760> not 00:02:43.839 --> 00:02:43.849 align:start position:0% she starts a game I'm because we're not 00:02:43.849 --> 00:02:45.940 align:start position:0% she starts a game I'm because we're not using<00:02:44.030> any<00:02:44.180> cryptography<00:02:44.930> she's<00:02:45.620> going<00:02:45.860> to 00:02:45.940 --> 00:02:45.950 align:start position:0% using any cryptography she's going to 00:02:45.950 --> 00:02:48.370 align:start position:0% using any cryptography she's going to leak<00:02:46.129> rock<00:02:46.489> so<00:02:47.060> she'll<00:02:47.239> reveal<00:02:47.540> rock<00:02:47.870> and<00:02:48.170> say 00:02:48.370 --> 00:02:48.380 align:start position:0% leak rock so she'll reveal rock and say 00:02:48.380 --> 00:02:51.280 align:start position:0% leak rock so she'll reveal rock and say I<00:02:48.410> want<00:02:48.830> a<00:02:48.890> bad<00:02:49.069> 5<00:02:49.310> pound<00:02:49.700> or<00:02:50.140> $5<00:02:51.140> in<00:02:51.260> my 00:02:51.280 --> 00:02:51.290 align:start position:0% I want a bad 5 pound or $5 in my 00:02:51.290 --> 00:02:54.309 align:start position:0% I want a bad 5 pound or $5 in my rock-paper-scissors<00:02:52.040> game<00:02:52.220> Bob<00:02:53.079> can<00:02:54.079> look<00:02:54.230> at 00:02:54.309 --> 00:02:54.319 align:start position:0% rock-paper-scissors game Bob can look at 00:02:54.319 --> 00:02:55.839 align:start position:0% rock-paper-scissors game Bob can look at the<00:02:54.410> contract<00:02:54.860> and<00:02:55.010> say<00:02:55.130> well<00:02:55.310> Alice<00:02:55.640> has 00:02:55.839 --> 00:02:55.849 align:start position:0% the contract and say well Alice has 00:02:55.849 --> 00:02:58.240 align:start position:0% the contract and say well Alice has played<00:02:56.060> rock<00:02:56.329> so<00:02:57.170> you<00:02:57.230> know<00:02:57.560> I'm<00:02:57.950> just<00:02:58.010> gonna 00:02:58.240 --> 00:02:58.250 align:start position:0% played rock so you know I'm just gonna 00:02:58.250 --> 00:02:59.949 align:start position:0% played rock so you know I'm just gonna play<00:02:58.459> paper<00:02:58.670> I'm<00:02:59.060> when<00:02:59.239> the<00:02:59.390> and<00:02:59.569> win<00:02:59.690> five 00:02:59.949 --> 00:02:59.959 align:start position:0% play paper I'm when the and win five 00:02:59.959 --> 00:03:02.289 align:start position:0% play paper I'm when the and win five dollars<00:03:00.400> you<00:03:01.400> know<00:03:01.519> the<00:03:01.640> contractor<00:03:02.120> Valley 00:03:02.289 --> 00:03:02.299 align:start position:0% dollars you know the contractor Valley 00:03:02.299 --> 00:03:03.819 align:start position:0% dollars you know the contractor Valley we<00:03:02.480> had<00:03:02.569> static<00:03:02.780> cuts<00:03:03.049> back<00:03:03.170> to<00:03:03.230> say<00:03:03.530> oh<00:03:03.560> well 00:03:03.819 --> 00:03:03.829 align:start position:0% we had static cuts back to say oh well 00:03:03.829 --> 00:03:05.259 align:start position:0% we had static cuts back to say oh well you<00:03:03.860> you've<00:03:04.250> won<00:03:04.370> the<00:03:04.489> ten<00:03:04.670> dollars<00:03:05.030> you<00:03:05.090> won 00:03:05.259 --> 00:03:05.269 align:start position:0% you you've won the ten dollars you won 00:03:05.269 --> 00:03:07.960 align:start position:0% you you've won the ten dollars you won the<00:03:05.390> prize<00:03:05.510> so<00:03:06.010> really<00:03:07.010> we<00:03:07.489> can't<00:03:07.790> actually 00:03:07.960 --> 00:03:07.970 align:start position:0% the prize so really we can't actually 00:03:07.970 --> 00:03:10.479 align:start position:0% the prize so really we can't actually play<00:03:08.269> rock<00:03:08.630> paper<00:03:08.900> scissors<00:03:09.440> and<00:03:09.620> a<00:03:10.130> public 00:03:10.479 --> 00:03:10.489 align:start position:0% play rock paper scissors and a public 00:03:10.489 --> 00:03:12.520 align:start position:0% play rock paper scissors and a public setting<00:03:10.700> like<00:03:10.970> a<00:03:11.000> smart<00:03:11.329> contract<00:03:11.530> without 00:03:12.520 --> 00:03:12.530 align:start position:0% setting like a smart contract without 00:03:12.530 --> 00:03:15.009 align:start position:0% setting like a smart contract without using<00:03:12.890> any<00:03:13.069> cryptography<00:03:13.790> so<00:03:14.660> what<00:03:14.840> do<00:03:14.900> we 00:03:15.009 --> 00:03:15.019 align:start position:0% using any cryptography so what do we 00:03:15.019 --> 00:03:17.470 align:start position:0% using any cryptography so what do we need<00:03:15.260> to<00:03:15.470> actually<00:03:15.590> build<00:03:15.980> this<00:03:16.160> we<00:03:16.880> need<00:03:17.090> a<00:03:17.120> we 00:03:17.470 --> 00:03:17.480 align:start position:0% need to actually build this we need a we 00:03:17.480 --> 00:03:19.720 align:start position:0% need to actually build this we need a we need<00:03:17.660> a<00:03:17.690> function<00:03:18.019> where<00:03:18.470> are<00:03:19.220> we<00:03:19.430> need<00:03:19.579> some 00:03:19.720 --> 00:03:19.730 align:start position:0% need a function where are we need some 00:03:19.730 --> 00:03:21.460 align:start position:0% need a function where are we need some photography<00:03:20.299> where<00:03:20.510> I<00:03:20.540> can<00:03:20.750> hide<00:03:20.930> my<00:03:20.959> choice 00:03:21.460 --> 00:03:21.470 align:start position:0% photography where I can hide my choice 00:03:21.470 --> 00:03:23.830 align:start position:0% photography where I can hide my choice but<00:03:22.370> then<00:03:22.489> I<00:03:22.579> can<00:03:22.760> leader<00:03:22.940> reveal<00:03:23.329> my<00:03:23.510> choice 00:03:23.830 --> 00:03:23.840 align:start position:0% but then I can leader reveal my choice 00:03:23.840 --> 00:03:27.069 align:start position:0% but then I can leader reveal my choice and<00:03:24.139> I<00:03:24.709> cannot<00:03:25.040> change<00:03:25.280> my<00:03:25.549> mind<00:03:25.819> and<00:03:26.690> we<00:03:26.930> can 00:03:27.069 --> 00:03:27.079 align:start position:0% and I cannot change my mind and we can 00:03:27.079 --> 00:03:29.229 align:start position:0% and I cannot change my mind and we can do<00:03:27.230> this<00:03:27.380> using<00:03:27.530> trivial<00:03:28.040> crypto<00:03:28.430> and<00:03:28.639> as<00:03:29.030> most 00:03:29.229 --> 00:03:29.239 align:start position:0% do this using trivial crypto and as most 00:03:29.239 --> 00:03:30.460 align:start position:0% do this using trivial crypto and as most people<00:03:29.480> in<00:03:29.540> this<00:03:29.660> room<00:03:29.720> are<00:03:29.989> probably<00:03:30.019> aware 00:03:30.460 --> 00:03:30.470 align:start position:0% people in this room are probably aware 00:03:30.470 --> 00:03:32.140 align:start position:0% people in this room are probably aware of<00:03:30.680> there's<00:03:30.920> cryptographic<00:03:31.250> hash<00:03:31.670> functions 00:03:32.140 --> 00:03:32.150 align:start position:0% of there's cryptographic hash functions 00:03:32.150 --> 00:03:35.140 align:start position:0% of there's cryptographic hash functions so<00:03:32.989> if<00:03:33.109> I<00:03:33.230> want<00:03:33.410> to<00:03:33.470> choose<00:03:33.650> rock<00:03:33.950> I<00:03:34.280> put<00:03:35.060> it 00:03:35.140 --> 00:03:35.150 align:start position:0% so if I want to choose rock I put it 00:03:35.150 --> 00:03:37.270 align:start position:0% so if I want to choose rock I put it through<00:03:35.180> the<00:03:35.450> house<00:03:35.600> function<00:03:36.170> I'll<00:03:36.590> get<00:03:36.829> 32 00:03:37.270 --> 00:03:37.280 align:start position:0% through the house function I'll get 32 00:03:37.280 --> 00:03:39.550 align:start position:0% through the house function I'll get 32 bytes<00:03:37.549> of<00:03:37.700> random<00:03:38.060> theater<00:03:38.389> I'll<00:03:39.049> store<00:03:39.410> that 00:03:39.550 --> 00:03:39.560 align:start position:0% bytes of random theater I'll store that 00:03:39.560 --> 00:03:42.160 align:start position:0% bytes of random theater I'll store that in<00:03:39.650> the<00:03:39.739> contract<00:03:40.130> and<00:03:40.489> later<00:03:41.060> on<00:03:41.329> when<00:03:42.139> I 00:03:42.160 --> 00:03:42.170 align:start position:0% in the contract and later on when I 00:03:42.170 --> 00:03:44.800 align:start position:0% in the contract and later on when I reveal<00:03:42.560> Rock<00:03:42.859> the<00:03:43.670> contract<00:03:44.239> will<00:03:44.389> hash<00:03:44.600> it 00:03:44.800 --> 00:03:44.810 align:start position:0% reveal Rock the contract will hash it 00:03:44.810 --> 00:03:46.990 align:start position:0% reveal Rock the contract will hash it again<00:03:45.079> and<00:03:45.350> compare<00:03:46.069> the<00:03:46.220> result<00:03:46.609> with<00:03:46.730> the 00:03:46.990 --> 00:03:47.000 align:start position:0% again and compare the result with the 00:03:47.000 --> 00:03:49.840 align:start position:0% again and compare the result with the output<00:03:47.540> of<00:03:47.569> what<00:03:47.810> it<00:03:47.900> hashed<00:03:48.700> so<00:03:49.700> that's 00:03:49.840 --> 00:03:49.850 align:start position:0% output of what it hashed so that's 00:03:49.850 --> 00:03:51.520 align:start position:0% output of what it hashed so that's really<00:03:50.060> cool<00:03:50.389> I'm<00:03:50.630> what<00:03:50.810> I<00:03:50.840> also<00:03:51.019> wanna<00:03:51.319> yard 00:03:51.520 --> 00:03:51.530 align:start position:0% really cool I'm what I also wanna yard 00:03:51.530 --> 00:03:53.259 align:start position:0% really cool I'm what I also wanna yard are<00:03:51.829> two<00:03:52.040> really<00:03:52.340> cool<00:03:52.549> features<00:03:52.940> of<00:03:53.060> smart 00:03:53.259 --> 00:03:53.269 align:start position:0% are two really cool features of smart 00:03:53.269 --> 00:03:56.140 align:start position:0% are two really cool features of smart contracts<00:03:53.769> deposits<00:03:54.769> and<00:03:54.920> refunds<00:03:55.280> so<00:03:56.060> the 00:03:56.140 --> 00:03:56.150 align:start position:0% contracts deposits and refunds so the 00:03:56.150 --> 00:03:58.000 align:start position:0% contracts deposits and refunds so the idea<00:03:56.450> is<00:03:56.540> that<00:03:56.600> when<00:03:56.840> you<00:03:56.930> start<00:03:57.200> a<00:03:57.260> game<00:03:57.290> you 00:03:58.000 --> 00:03:58.010 align:start position:0% idea is that when you start a game you 00:03:58.010 --> 00:04:00.610 align:start position:0% idea is that when you start a game you send<00:03:58.280> a<00:03:58.340> deposit<00:03:58.790> and<00:03:59.139> then<00:04:00.139> when<00:04:00.319> you<00:04:00.440> finish 00:04:00.610 --> 00:04:00.620 align:start position:0% send a deposit and then when you finish 00:04:00.620 --> 00:04:02.589 align:start position:0% send a deposit and then when you finish the<00:04:00.889> game<00:04:00.920> you<00:04:01.340> get<00:04:01.549> your<00:04:01.700> deposit<00:04:01.910> back<00:04:02.150> and 00:04:02.589 --> 00:04:02.599 align:start position:0% the game you get your deposit back and 00:04:02.599 --> 00:04:04.240 align:start position:0% the game you get your deposit back and this<00:04:03.019> will<00:04:03.230> provide<00:04:03.530> a<00:04:03.590> financial<00:04:03.829> incentive 00:04:04.240 --> 00:04:04.250 align:start position:0% this will provide a financial incentive 00:04:04.250 --> 00:04:06.490 align:start position:0% this will provide a financial incentive for<00:04:04.790> people<00:04:04.940> to<00:04:05.090> finish<00:04:05.299> the<00:04:05.540> game<00:04:05.720> so<00:04:06.349> let's 00:04:06.490 --> 00:04:06.500 align:start position:0% for people to finish the game so let's 00:04:06.500 --> 00:04:08.229 align:start position:0% for people to finish the game so let's go<00:04:06.650> back<00:04:06.680> to<00:04:06.859> our<00:04:07.040> little<00:04:07.220> simple<00:04:07.639> example<00:04:08.120> of 00:04:08.229 --> 00:04:08.239 align:start position:0% go back to our little simple example of 00:04:08.239 --> 00:04:12.250 align:start position:0% go back to our little simple example of rock-paper-scissors<00:04:10.299> Alice<00:04:11.299> will<00:04:11.540> make<00:04:12.230> a 00:04:12.250 --> 00:04:12.260 align:start position:0% rock-paper-scissors Alice will make a 00:04:12.260 --> 00:04:14.409 align:start position:0% rock-paper-scissors Alice will make a choice<00:04:12.669> so<00:04:13.669> run<00:04:13.910> it<00:04:13.940> through<00:04:14.150> the<00:04:14.269> Hoss 00:04:14.409 --> 00:04:14.419 align:start position:0% choice so run it through the Hoss 00:04:14.419 --> 00:04:16.449 align:start position:0% choice so run it through the Hoss function<00:04:14.930> and<00:04:15.109> then<00:04:15.709> she'll<00:04:15.889> send<00:04:16.099> the<00:04:16.220> house 00:04:16.449 --> 00:04:16.459 align:start position:0% function and then she'll send the house 00:04:16.459 --> 00:04:19.180 align:start position:0% function and then she'll send the house of<00:04:16.669> her<00:04:16.760> choice<00:04:17.030> five<00:04:17.959> dollars<00:04:18.470> and<00:04:18.709> that 00:04:19.180 --> 00:04:19.190 align:start position:0% of her choice five dollars and that 00:04:19.190 --> 00:04:21.879 align:start position:0% of her choice five dollars and that small<00:04:19.489> little<00:04:19.639> deposit<00:04:20.209> now<00:04:20.900> Bob<00:04:21.229> comes<00:04:21.560> along 00:04:21.879 --> 00:04:21.889 align:start position:0% small little deposit now Bob comes along 00:04:21.889 --> 00:04:24.460 align:start position:0% small little deposit now Bob comes along and<00:04:22.130> Bob<00:04:22.700> can<00:04:22.940> look<00:04:23.060> at<00:04:23.150> the<00:04:23.240> contract<00:04:23.780> you<00:04:24.289> can 00:04:24.460 --> 00:04:24.470 align:start position:0% and Bob can look at the contract you can 00:04:24.470 --> 00:04:26.620 align:start position:0% and Bob can look at the contract you can see<00:04:24.620> that<00:04:24.770> Alice<00:04:25.070> wants<00:04:25.310> to<00:04:25.430> play<00:04:25.669> but<00:04:26.330> now<00:04:26.570> he 00:04:26.620 --> 00:04:26.630 align:start position:0% see that Alice wants to play but now he 00:04:26.630 --> 00:04:28.390 align:start position:0% see that Alice wants to play but now he can't<00:04:27.050> see<00:04:27.229> her<00:04:27.349> choice 00:04:28.390 --> 00:04:28.400 align:start position:0% can't see her choice 00:04:28.400 --> 00:04:30.820 align:start position:0% can't see her choice so<00:04:29.300> there's<00:04:29.660> a<00:04:29.690> bit<00:04:29.840> of<00:04:29.870> risk<00:04:30.139> it<00:04:30.440> could<00:04:30.710> be 00:04:30.820 --> 00:04:30.830 align:start position:0% so there's a bit of risk it could be 00:04:30.830 --> 00:04:33.370 align:start position:0% so there's a bit of risk it could be rock<00:04:31.010> paper<00:04:31.310> or<00:04:31.400> scissors<00:04:31.900> so<00:04:32.900> he'll<00:04:33.139> make<00:04:33.350> a 00:04:33.370 --> 00:04:33.380 align:start position:0% rock paper or scissors so he'll make a 00:04:33.380 --> 00:04:35.650 align:start position:0% rock paper or scissors so he'll make a choice<00:04:33.680> he'll<00:04:34.610> send<00:04:34.910> the<00:04:35.030> harsh<00:04:35.270> of<00:04:35.479> his 00:04:35.650 --> 00:04:35.660 align:start position:0% choice he'll send the harsh of his 00:04:35.660 --> 00:04:37.960 align:start position:0% choice he'll send the harsh of his choice<00:04:35.960> five<00:04:36.410> dollars<00:04:36.860> on<00:04:36.889> a<00:04:37.070> deposit<00:04:37.400> and 00:04:37.960 --> 00:04:37.970 align:start position:0% choice five dollars on a deposit and 00:04:37.970 --> 00:04:40.000 align:start position:0% choice five dollars on a deposit and it'll<00:04:38.300> tell<00:04:38.510> the<00:04:38.660> contract<00:04:39.199> that<00:04:39.650> he<00:04:39.770> wants<00:04:39.979> to 00:04:40.000 --> 00:04:40.010 align:start position:0% it'll tell the contract that he wants to 00:04:40.010 --> 00:04:42.400 align:start position:0% it'll tell the contract that he wants to play<00:04:40.220> rock<00:04:40.460> paper<00:04:40.639> scissors<00:04:40.790> with<00:04:41.180> vollis<00:04:41.479> now 00:04:42.400 --> 00:04:42.410 align:start position:0% play rock paper scissors with vollis now 00:04:42.410 --> 00:04:43.950 align:start position:0% play rock paper scissors with vollis now in<00:04:42.530> the<00:04:42.650> second<00:04:43.070> round<00:04:43.160> of<00:04:43.310> this<00:04:43.460> protocol 00:04:43.950 --> 00:04:43.960 align:start position:0% in the second round of this protocol 00:04:43.960 --> 00:04:46.510 align:start position:0% in the second round of this protocol everyone<00:04:44.960> must<00:04:45.229> reveal<00:04:45.620> their<00:04:45.860> choice<00:04:46.130> before 00:04:46.510 --> 00:04:46.520 align:start position:0% everyone must reveal their choice before 00:04:46.520 --> 00:04:49.659 align:start position:0% everyone must reveal their choice before time<00:04:46.970> T<00:04:47.270> if<00:04:47.680> you<00:04:48.680> don't<00:04:48.919> reveal<00:04:49.100> your<00:04:49.400> choice 00:04:49.659 --> 00:04:49.669 align:start position:0% time T if you don't reveal your choice 00:04:49.669 --> 00:04:52.870 align:start position:0% time T if you don't reveal your choice you<00:04:50.419> forfeit<00:04:50.900> your<00:04:50.930> deposit<00:04:51.880> unlikelihood 00:04:52.870 --> 00:04:52.880 align:start position:0% you forfeit your deposit unlikelihood 00:04:52.880 --> 00:04:54.430 align:start position:0% you forfeit your deposit unlikelihood the<00:04:53.240> Condor<00:04:53.540> party<00:04:53.870> party<00:04:54.290> will<00:04:54.410> probably 00:04:54.430 --> 00:04:54.440 align:start position:0% the Condor party party will probably 00:04:54.440 --> 00:04:56.129 align:start position:0% the Condor party party will probably automatically<00:04:55.280> win 00:04:56.129 --> 00:04:56.139 align:start position:0% automatically win 00:04:56.139 --> 00:05:00.430 align:start position:0% automatically win so<00:04:57.190> next<00:04:58.190> Alice<00:04:58.699> will<00:04:58.850> reveal<00:04:59.060> scissors<00:04:59.510> the 00:05:00.430 --> 00:05:00.440 align:start position:0% so next Alice will reveal scissors the 00:05:00.440 --> 00:05:02.409 align:start position:0% so next Alice will reveal scissors the contract<00:05:01.010> will<00:05:01.130> evaluate<00:05:01.400> to<00:05:01.850> say<00:05:02.030> that<00:05:02.240> well 00:05:02.409 --> 00:05:02.419 align:start position:0% contract will evaluate to say that well 00:05:02.419 --> 00:05:04.570 align:start position:0% contract will evaluate to say that well scissors<00:05:02.990> was<00:05:03.199> her<00:05:03.380> commitment<00:05:03.949> it<00:05:04.070> matches 00:05:04.570 --> 00:05:04.580 align:start position:0% scissors was her commitment it matches 00:05:04.580 --> 00:05:08.620 align:start position:0% scissors was her commitment it matches the<00:05:04.789> hashas<00:05:05.240> she<00:05:05.389> give<00:05:05.600> me<00:05:06.220> next<00:05:07.220> bob<00:05:08.150> can<00:05:08.419> see 00:05:08.620 --> 00:05:08.630 align:start position:0% the hashas she give me next bob can see 00:05:08.630 --> 00:05:10.629 align:start position:0% the hashas she give me next bob can see that<00:05:08.840> alice's<00:05:09.289> choice<00:05:09.500> for<00:05:09.710> scissors<00:05:10.039> so<00:05:10.460> now 00:05:10.629 --> 00:05:10.639 align:start position:0% that alice's choice for scissors so now 00:05:10.639 --> 00:05:14.379 align:start position:0% that alice's choice for scissors so now he<00:05:10.699> has<00:05:10.880> two<00:05:11.150> decisions<00:05:11.720> a<00:05:12.580> he<00:05:13.580> aboard<00:05:13.970> the 00:05:14.379 --> 00:05:14.389 align:start position:0% he has two decisions a he aboard the 00:05:14.389 --> 00:05:17.230 align:start position:0% he has two decisions a he aboard the protocol<00:05:14.870> because<00:05:15.169> he's<00:05:15.289> lost<00:05:15.530> or<00:05:15.889> two<00:05:16.699> he 00:05:17.230 --> 00:05:17.240 align:start position:0% protocol because he's lost or two he 00:05:17.240 --> 00:05:19.750 align:start position:0% protocol because he's lost or two he plays<00:05:17.780> the<00:05:17.990> protocol<00:05:18.500> evie<00:05:18.800> wins<00:05:19.190> or<00:05:19.400> loses 00:05:19.750 --> 00:05:19.760 align:start position:0% plays the protocol evie wins or loses 00:05:19.760 --> 00:05:22.240 align:start position:0% plays the protocol evie wins or loses now<00:05:20.300> because<00:05:20.660> he's<00:05:20.780> never<00:05:20.960> the<00:05:21.050> deposit<00:05:21.560> he's 00:05:22.240 --> 00:05:22.250 align:start position:0% now because he's never the deposit he's 00:05:22.250 --> 00:05:24.520 align:start position:0% now because he's never the deposit he's gonna<00:05:22.520> reveal<00:05:22.729> pepper<00:05:23.180> and<00:05:23.900> he's<00:05:24.110> lost<00:05:24.380> the 00:05:24.520 --> 00:05:24.530 align:start position:0% gonna reveal pepper and he's lost the 00:05:24.530 --> 00:05:26.650 align:start position:0% gonna reveal pepper and he's lost the game<00:05:24.740> but<00:05:25.550> he<00:05:25.639> does<00:05:25.850> this<00:05:25.970> because<00:05:26.150> he<00:05:26.330> wants 00:05:26.650 --> 00:05:26.660 align:start position:0% game but he does this because he wants 00:05:26.660 --> 00:05:28.900 align:start position:0% game but he does this because he wants to<00:05:26.750> get<00:05:26.840> his<00:05:26.990> deposit<00:05:27.410> back<00:05:27.490> the<00:05:28.490> contract 00:05:28.900 --> 00:05:28.910 align:start position:0% to get his deposit back the contract 00:05:28.910 --> 00:05:30.610 align:start position:0% to get his deposit back the contract will<00:05:29.030> evaluate<00:05:29.240> this<00:05:29.720> and<00:05:29.930> say<00:05:30.050> okay<00:05:30.350> but<00:05:30.530> I'm 00:05:30.610 --> 00:05:30.620 align:start position:0% will evaluate this and say okay but I'm 00:05:30.620 --> 00:05:34.120 align:start position:0% will evaluate this and say okay but I'm sorry<00:05:30.860> you<00:05:31.039> know<00:05:31.479> scissors<00:05:32.479> beats<00:05:32.690> paper<00:05:33.130> Bob 00:05:34.120 --> 00:05:34.130 align:start position:0% sorry you know scissors beats paper Bob 00:05:34.130 --> 00:05:36.550 align:start position:0% sorry you know scissors beats paper Bob gets<00:05:34.400> his<00:05:34.490> deposit<00:05:34.910> back<00:05:35.090> on<00:05:35.300> Alice<00:05:36.080> wins<00:05:36.320> and 00:05:36.550 --> 00:05:36.560 align:start position:0% gets his deposit back on Alice wins and 00:05:36.560 --> 00:05:40.420 align:start position:0% gets his deposit back on Alice wins and gets<00:05:36.680> $10<00:05:38.229> now<00:05:39.229> to<00:05:39.289> the<00:05:39.590> security<00:05:39.950> experts<00:05:40.310> in 00:05:40.420 --> 00:05:40.430 align:start position:0% gets $10 now to the security experts in 00:05:40.430 --> 00:05:42.430 align:start position:0% gets $10 now to the security experts in the<00:05:40.520> room<00:05:40.729> that's<00:05:41.240> my<00:05:41.450> little<00:05:41.630> disclaimer<00:05:42.080> you 00:05:42.430 --> 00:05:42.440 align:start position:0% the room that's my little disclaimer you 00:05:42.440 --> 00:05:44.350 align:start position:0% the room that's my little disclaimer you should<00:05:43.099> normally<00:05:43.400> use<00:05:43.490> an<00:05:43.610> ounce<00:05:43.789> when<00:05:44.090> you<00:05:44.180> do 00:05:44.350 --> 00:05:44.360 align:start position:0% should normally use an ounce when you do 00:05:44.360 --> 00:05:46.330 align:start position:0% should normally use an ounce when you do this<00:05:44.539> but<00:05:45.110> I<00:05:45.169> want<00:05:45.289> to<00:05:45.440> avoid<00:05:45.650> these<00:05:45.860> details 00:05:46.330 --> 00:05:46.340 align:start position:0% this but I want to avoid these details 00:05:46.340 --> 00:05:48.400 align:start position:0% this but I want to avoid these details because<00:05:46.639> I'm<00:05:46.760> not<00:05:46.880> here<00:05:47.120> to<00:05:47.270> you<00:05:47.840> know<00:05:47.900> present 00:05:48.400 --> 00:05:48.410 align:start position:0% because I'm not here to you know present 00:05:48.410 --> 00:05:50.620 align:start position:0% because I'm not here to you know present exact<00:05:48.950> secure<00:05:49.280> protocols<00:05:49.820> so<00:05:50.419> it's<00:05:50.570> the 00:05:50.620 --> 00:05:50.630 align:start position:0% exact secure protocols so it's the 00:05:50.630 --> 00:05:52.830 align:start position:0% exact secure protocols so it's the intuition<00:05:51.200> of<00:05:51.260> why<00:05:51.440> cryptography<00:05:52.039> is<00:05:52.099> useful 00:05:52.830 --> 00:05:52.840 align:start position:0% intuition of why cryptography is useful 00:05:52.840 --> 00:05:54.969 align:start position:0% intuition of why cryptography is useful so<00:05:53.840> what's<00:05:54.020> really<00:05:54.169> cool<00:05:54.320> about<00:05:54.530> the<00:05:54.740> previous 00:05:54.969 --> 00:05:54.979 align:start position:0% so what's really cool about the previous 00:05:54.979 --> 00:05:57.070 align:start position:0% so what's really cool about the previous example<00:05:55.610> is<00:05:55.820> that<00:05:55.849> the<00:05:56.150> deposit<00:05:56.599> of<00:05:56.690> refund 00:05:57.070 --> 00:05:57.080 align:start position:0% example is that the deposit of refund 00:05:57.080 --> 00:05:59.200 align:start position:0% example is that the deposit of refund scheme<00:05:57.169> pervaded<00:05:58.039> this<00:05:58.160> financial<00:05:58.520> incentive 00:05:59.200 --> 00:05:59.210 align:start position:0% scheme pervaded this financial incentive 00:05:59.210 --> 00:06:01.659 align:start position:0% scheme pervaded this financial incentive for<00:05:59.240> people<00:05:59.570> to<00:05:59.660> participate<00:05:59.810> um<00:06:00.470> or<00:06:01.340> the 00:06:01.659 --> 00:06:01.669 align:start position:0% for people to participate um or the 00:06:01.669 --> 00:06:04.629 align:start position:0% for people to participate um or the house<00:06:02.389> phone<00:06:02.660> pervades<00:06:03.470> that<00:06:03.680> ability<00:06:04.520> to 00:06:04.629 --> 00:06:04.639 align:start position:0% house phone pervades that ability to 00:06:04.639 --> 00:06:07.210 align:start position:0% house phone pervades that ability to hide<00:06:04.849> my<00:06:05.060> choice<00:06:05.389> but<00:06:06.199> also<00:06:06.440> commit<00:06:06.860> me<00:06:06.979> to<00:06:07.099> my 00:06:07.210 --> 00:06:07.220 align:start position:0% hide my choice but also commit me to my 00:06:07.220 --> 00:06:08.500 align:start position:0% hide my choice but also commit me to my choice<00:06:07.460> in<00:06:07.669> a<00:06:07.729> public<00:06:08.030> setting 00:06:08.500 --> 00:06:08.510 align:start position:0% choice in a public setting 00:06:08.510 --> 00:06:12.760 align:start position:0% choice in a public setting what's<00:06:09.440> not<00:06:09.710> really<00:06:10.010> good<00:06:10.280> is<00:06:10.550> that<00:06:11.770> when 00:06:12.760 --> 00:06:12.770 align:start position:0% what's not really good is that when 00:06:12.770 --> 00:06:14.290 align:start position:0% what's not really good is that when Alice<00:06:13.130> sends<00:06:13.430> her<00:06:13.699> hash 00:06:14.290 --> 00:06:14.300 align:start position:0% Alice sends her hash 00:06:14.300 --> 00:06:16.750 align:start position:0% Alice sends her hash there's<00:06:14.780> no<00:06:14.990> way<00:06:15.139> to<00:06:15.199> verify<00:06:15.320> that<00:06:16.099> was<00:06:16.580> either 00:06:16.750 --> 00:06:16.760 align:start position:0% there's no way to verify that was either 00:06:16.760 --> 00:06:19.600 align:start position:0% there's no way to verify that was either rock<00:06:17.060> paper<00:06:17.570> or<00:06:17.720> scissors<00:06:17.900> all<00:06:18.770> askew<00:06:19.250> dissent 00:06:19.600 --> 00:06:19.610 align:start position:0% rock paper or scissors all askew dissent 00:06:19.610 --> 00:06:22.900 align:start position:0% rock paper or scissors all askew dissent Spock<00:06:19.940> and<00:06:20.300> then<00:06:21.020> later<00:06:21.229> revealed<00:06:21.620> Spock<00:06:22.039> but 00:06:22.900 --> 00:06:22.910 align:start position:0% Spock and then later revealed Spock but 00:06:22.910 --> 00:06:24.909 align:start position:0% Spock and then later revealed Spock but in<00:06:23.060> this<00:06:23.240> setting<00:06:23.690> that<00:06:23.870> doesn't<00:06:24.770> really 00:06:24.909 --> 00:06:24.919 align:start position:0% in this setting that doesn't really 00:06:24.919 --> 00:06:27.339 align:start position:0% in this setting that doesn't really matter<00:06:25.190> because<00:06:26.060> if<00:06:26.180> I<00:06:26.270> was<00:06:26.449> dead<00:06:26.690> true<00:06:26.960> Spock 00:06:27.339 --> 00:06:27.349 align:start position:0% matter because if I was dead true Spock 00:06:27.349 --> 00:06:29.529 align:start position:0% matter because if I was dead true Spock the<00:06:27.860> contract<00:06:28.340> will<00:06:28.490> say<00:06:28.639> well<00:06:28.880> Spock<00:06:29.300> was<00:06:29.510> a 00:06:29.529 --> 00:06:29.539 align:start position:0% the contract will say well Spock was a 00:06:29.539 --> 00:06:32.700 align:start position:0% the contract will say well Spock was a Nevada<00:06:30.050> chase<00:06:30.440> so<00:06:31.220> Bob<00:06:31.460> automatically<00:06:32.060> wins 00:06:32.700 --> 00:06:32.710 align:start position:0% Nevada chase so Bob automatically wins 00:06:32.710 --> 00:06:34.719 align:start position:0% Nevada chase so Bob automatically wins but<00:06:33.710> what<00:06:33.860> have<00:06:33.979> we<00:06:34.099> said<00:06:34.310> when<00:06:34.490> we<00:06:34.520> have<00:06:34.699> a 00:06:34.719 --> 00:06:34.729 align:start position:0% but what have we said when we have a 00:06:34.729 --> 00:06:38.440 align:start position:0% but what have we said when we have a protocol<00:06:35.270> or<00:06:35.510> an<00:06:35.810> application<00:06:36.340> where<00:06:37.340> a<00:06:37.849> user 00:06:38.440 --> 00:06:38.450 align:start position:0% protocol or an application where a user 00:06:38.450 --> 00:06:40.810 align:start position:0% protocol or an application where a user can't<00:06:38.900> reveal<00:06:39.229> their<00:06:39.440> choice<00:06:39.680> so<00:06:40.039> all<00:06:40.669> the 00:06:40.810 --> 00:06:40.820 align:start position:0% can't reveal their choice so all the 00:06:40.820 --> 00:06:42.070 align:start position:0% can't reveal their choice so all the contract<00:06:41.300> houses<00:06:41.750> in 00:06:42.070 --> 00:06:42.080 align:start position:0% contract houses in 00:06:42.080 --> 00:06:44.559 align:start position:0% contract houses in that<00:06:42.259> information<00:06:42.919> and<00:06:43.099> the<00:06:43.729> classic<00:06:44.120> example 00:06:44.559 --> 00:06:44.569 align:start position:0% that information and the classic example 00:06:44.569 --> 00:06:45.189 align:start position:0% that information and the classic example is<00:06:44.629> e-voting 00:06:45.189 --> 00:06:45.199 align:start position:0% is e-voting 00:06:45.199 --> 00:06:48.490 align:start position:0% is e-voting where<00:06:46.099> we<00:06:46.220> want<00:06:46.430> a<00:06:46.520> maximized<00:06:47.090> voter<00:06:47.870> privacy 00:06:48.490 --> 00:06:48.500 align:start position:0% where we want a maximized voter privacy 00:06:48.500 --> 00:06:51.399 align:start position:0% where we want a maximized voter privacy so<00:06:49.009> the<00:06:49.129> idea<00:06:49.460> is<00:06:49.550> that<00:06:50.110> you<00:06:51.110> should<00:06:51.259> be<00:06:51.349> able 00:06:51.399 --> 00:06:51.409 align:start position:0% so the idea is that you should be able 00:06:51.409 --> 00:06:54.369 align:start position:0% so the idea is that you should be able to<00:06:51.560> see<00:06:51.680> the<00:06:51.830> patrick<00:06:52.280> has<00:06:52.610> cast<00:06:52.909> his<00:06:53.120> vote<00:06:53.379> but 00:06:54.369 --> 00:06:54.379 align:start position:0% to see the patrick has cast his vote but 00:06:54.379 --> 00:06:56.050 align:start position:0% to see the patrick has cast his vote but it's<00:06:54.500> encrypted<00:06:54.800> so<00:06:55.430> you<00:06:55.490> should<00:06:55.699> never<00:06:55.819> be 00:06:56.050 --> 00:06:56.060 align:start position:0% it's encrypted so you should never be 00:06:56.060 --> 00:06:58.360 align:start position:0% it's encrypted so you should never be able<00:06:56.090> to<00:06:56.270> see<00:06:56.449> what<00:06:56.689> I<00:06:56.719> vote<00:06:57.050> it<00:06:57.219> allows<00:06:58.219> the 00:06:58.360 --> 00:06:58.370 align:start position:0% able to see what I vote it allows the 00:06:58.370 --> 00:07:00.129 align:start position:0% able to see what I vote it allows the Mazda<00:06:58.669> may<00:06:58.789> have<00:06:58.879> for<00:06:59.120> encrypted<00:06:59.569> votes<00:06:59.780> and 00:07:00.129 --> 00:07:00.139 align:start position:0% Mazda may have for encrypted votes and 00:07:00.139 --> 00:07:02.499 align:start position:0% Mazda may have for encrypted votes and these<00:07:00.710> are<00:07:00.860> in<00:07:00.949> these<00:07:01.819> are<00:07:02.000> stored<00:07:02.330> on<00:07:02.389> the 00:07:02.499 --> 00:07:02.509 align:start position:0% these are in these are stored on the 00:07:02.509 --> 00:07:04.510 align:start position:0% these are in these are stored on the smart<00:07:02.780> contract<00:07:02.960> and<00:07:03.500> now<00:07:04.069> we<00:07:04.129> want<00:07:04.430> to 00:07:04.510 --> 00:07:04.520 align:start position:0% smart contract and now we want to 00:07:04.520 --> 00:07:06.339 align:start position:0% smart contract and now we want to compute<00:07:04.879> the<00:07:04.969> tally<00:07:05.180> we<00:07:05.900> should<00:07:06.110> be<00:07:06.169> able<00:07:06.229> to 00:07:06.339 --> 00:07:06.349 align:start position:0% compute the tally we should be able to 00:07:06.349 --> 00:07:09.670 align:start position:0% compute the tally we should be able to simply<00:07:06.710> add<00:07:06.889> these<00:07:07.069> votes<00:07:07.310> together<00:07:07.490> and<00:07:08.680> once 00:07:09.670 --> 00:07:09.680 align:start position:0% simply add these votes together and once 00:07:09.680 --> 00:07:10.959 align:start position:0% simply add these votes together and once all<00:07:09.860> the<00:07:09.889> encrypted<00:07:10.370> votes<00:07:10.550> are<00:07:10.699> added 00:07:10.959 --> 00:07:10.969 align:start position:0% all the encrypted votes are added 00:07:10.969 --> 00:07:12.879 align:start position:0% all the encrypted votes are added together<00:07:11.060> there'll<00:07:11.870> be<00:07:11.900> some<00:07:12.139> crypto<00:07:12.469> magic 00:07:12.879 --> 00:07:12.889 align:start position:0% together there'll be some crypto magic 00:07:12.889 --> 00:07:14.619 align:start position:0% together there'll be some crypto magic and<00:07:13.099> it<00:07:13.430> will<00:07:13.550> automatically<00:07:14.090> perform<00:07:14.539> the 00:07:14.619 --> 00:07:14.629 align:start position:0% and it will automatically perform the 00:07:14.629 --> 00:07:17.260 align:start position:0% and it will automatically perform the decryption<00:07:15.460> so<00:07:16.460> then<00:07:16.610> we<00:07:16.729> get<00:07:16.849> the<00:07:17.000> tally 00:07:17.260 --> 00:07:17.270 align:start position:0% decryption so then we get the tally 00:07:17.270 --> 00:07:19.469 align:start position:0% decryption so then we get the tally that's<00:07:17.569> one<00:07:17.780> yes<00:07:18.020> vote<00:07:18.289> and<00:07:18.530> three<00:07:18.860> new<00:07:19.039> votes 00:07:19.469 --> 00:07:19.479 align:start position:0% that's one yes vote and three new votes 00:07:19.479 --> 00:07:22.779 align:start position:0% that's one yes vote and three new votes now<00:07:20.479> in<00:07:20.659> this<00:07:20.840> setting<00:07:21.289> voters<00:07:22.159> cannot<00:07:22.490> reveal 00:07:22.779 --> 00:07:22.789 align:start position:0% now in this setting voters cannot reveal 00:07:22.789 --> 00:07:24.580 align:start position:0% now in this setting voters cannot reveal their<00:07:23.000> vote<00:07:23.210> so<00:07:23.750> we<00:07:23.780> can't<00:07:24.139> do<00:07:24.259> that<00:07:24.379> really 00:07:24.580 --> 00:07:24.590 align:start position:0% their vote so we can't do that really 00:07:24.590 --> 00:07:26.770 align:start position:0% their vote so we can't do that really nice<00:07:24.889> commit<00:07:25.310> and<00:07:25.460> reveal<00:07:25.729> trick<00:07:26.060> that<00:07:26.509> we<00:07:26.629> did 00:07:26.770 --> 00:07:26.780 align:start position:0% nice commit and reveal trick that we did 00:07:26.780 --> 00:07:29.170 align:start position:0% nice commit and reveal trick that we did with<00:07:26.900> Haas<00:07:27.050> functions<00:07:27.530> we<00:07:28.490> also<00:07:28.699> need<00:07:29.000> to<00:07:29.060> be 00:07:29.170 --> 00:07:29.180 align:start position:0% with Haas functions we also need to be 00:07:29.180 --> 00:07:31.629 align:start position:0% with Haas functions we also need to be confident<00:07:29.690> that<00:07:30.289> every<00:07:30.680> encrypted<00:07:31.159> vote<00:07:31.400> is 00:07:31.629 --> 00:07:31.639 align:start position:0% confident that every encrypted vote is 00:07:31.639 --> 00:07:34.480 align:start position:0% confident that every encrypted vote is either<00:07:32.210> yes<00:07:32.569> or<00:07:32.719> no<00:07:32.930> if<00:07:33.319> we<00:07:33.949> don't<00:07:34.190> know<00:07:34.310> about 00:07:34.480 --> 00:07:34.490 align:start position:0% either yes or no if we don't know about 00:07:34.490 --> 00:07:37.629 align:start position:0% either yes or no if we don't know about guarantee<00:07:35.029> then<00:07:35.990> an<00:07:36.169> attacker<00:07:36.529> could<00:07:37.310> create 00:07:37.629 --> 00:07:37.639 align:start position:0% guarantee then an attacker could create 00:07:37.639 --> 00:07:39.850 align:start position:0% guarantee then an attacker could create an<00:07:37.759> encrypted<00:07:37.940> vote<00:07:38.360> in<00:07:38.599> such<00:07:38.930> a<00:07:38.960> way<00:07:39.259> where 00:07:39.850 --> 00:07:39.860 align:start position:0% an encrypted vote in such a way where 00:07:39.860 --> 00:07:41.830 align:start position:0% an encrypted vote in such a way where they<00:07:40.069> change<00:07:40.460> somebody<00:07:40.789> else's<00:07:40.849> vote<00:07:41.330> they 00:07:41.830 --> 00:07:41.840 align:start position:0% they change somebody else's vote they 00:07:41.840 --> 00:07:44.080 align:start position:0% they change somebody else's vote they cancel<00:07:42.319> somebody<00:07:42.620> else's<00:07:42.949> vote<00:07:43.159> or<00:07:43.400> they<00:07:43.849> just 00:07:44.080 --> 00:07:44.090 align:start position:0% cancel somebody else's vote or they just 00:07:44.090 --> 00:07:45.969 align:start position:0% cancel somebody else's vote or they just vote<00:07:44.240> multiple<00:07:44.659> times<00:07:44.930> because<00:07:45.590> remember 00:07:45.969 --> 00:07:45.979 align:start position:0% vote multiple times because remember 00:07:45.979 --> 00:07:47.680 align:start position:0% vote multiple times because remember these<00:07:46.099> are<00:07:46.219> encrypted<00:07:46.610> votes<00:07:46.819> and<00:07:47.120> under<00:07:47.569> the 00:07:47.680 --> 00:07:47.690 align:start position:0% these are encrypted votes and under the 00:07:47.690 --> 00:07:49.089 align:start position:0% these are encrypted votes and under the hood<00:07:47.870> is<00:07:48.020> all<00:07:48.169> mathematics<00:07:48.740> they're<00:07:48.919> doing 00:07:49.089 --> 00:07:49.099 align:start position:0% hood is all mathematics they're doing 00:07:49.099 --> 00:07:51.100 align:start position:0% hood is all mathematics they're doing addition<00:07:49.550> subtraction<00:07:50.120> multiplication<00:07:50.150> etc 00:07:51.100 --> 00:07:51.110 align:start position:0% addition subtraction multiplication etc 00:07:51.110 --> 00:07:54.909 align:start position:0% addition subtraction multiplication etc etc<00:07:51.940> so<00:07:52.940> one<00:07:53.779> way<00:07:53.900> they<00:07:54.050> get<00:07:54.199> around<00:07:54.469> this<00:07:54.710> is 00:07:54.909 --> 00:07:54.919 align:start position:0% etc so one way they get around this is 00:07:54.919 --> 00:07:56.860 align:start position:0% etc so one way they get around this is the<00:07:54.979> users<00:07:55.370> here<00:07:55.520> in<00:07:55.610> all<00:07:55.699> these<00:07:55.789> proof<00:07:56.090> and 00:07:56.860 --> 00:07:56.870 align:start position:0% the users here in all these proof and 00:07:56.870 --> 00:07:58.899 align:start position:0% the users here in all these proof and when<00:07:57.020> I<00:07:57.050> can<00:07:57.259> prove<00:07:57.500> to<00:07:57.560> you<00:07:57.770> is<00:07:58.219> that<00:07:58.729> my 00:07:58.899 --> 00:07:58.909 align:start position:0% when I can prove to you is that my 00:07:58.909 --> 00:08:01.899 align:start position:0% when I can prove to you is that my encrypted<00:07:59.449> vote<00:07:59.690> is<00:07:59.930> either<00:08:00.560> yes<00:08:00.949> or<00:08:00.979> zero<00:08:01.610> on 00:08:01.899 --> 00:08:01.909 align:start position:0% encrypted vote is either yes or zero on 00:08:01.909 --> 00:08:05.079 align:start position:0% encrypted vote is either yes or zero on it<00:08:02.779> with<00:08:02.960> this<00:08:03.199> proof<00:08:03.529> all<00:08:04.069> and<00:08:04.610> that's<00:08:04.969> the 00:08:05.079 --> 00:08:05.089 align:start position:0% it with this proof all and that's the 00:08:05.089 --> 00:08:06.760 align:start position:0% it with this proof all and that's the only<00:08:05.270> thing<00:08:05.300> I<00:08:05.539> reveal<00:08:05.900> about<00:08:06.169> this<00:08:06.319> encrypted 00:08:06.760 --> 00:08:06.770 align:start position:0% only thing I reveal about this encrypted 00:08:06.770 --> 00:08:07.149 align:start position:0% only thing I reveal about this encrypted vote 00:08:07.149 --> 00:08:07.159 align:start position:0% vote 00:08:07.159 --> 00:08:09.550 align:start position:0% vote I<00:08:07.190> don't<00:08:07.909> reveal<00:08:08.120> the<00:08:08.270> vote<00:08:08.419> itself<00:08:08.779> I<00:08:09.139> just 00:08:09.550 --> 00:08:09.560 align:start position:0% I don't reveal the vote itself I just 00:08:09.560 --> 00:08:11.619 align:start position:0% I don't reveal the vote itself I just revealed<00:08:09.860> that<00:08:10.069> it's<00:08:10.279> well-formed<00:08:11.029> honest 00:08:11.619 --> 00:08:11.629 align:start position:0% revealed that it's well-formed honest 00:08:11.629 --> 00:08:14.529 align:start position:0% revealed that it's well-formed honest satisfy<00:08:12.080> some<00:08:12.409> type<00:08:12.620> of<00:08:12.650> criteria<00:08:13.300> so<00:08:14.300> now<00:08:14.479> we 00:08:14.529 --> 00:08:14.539 align:start position:0% satisfy some type of criteria so now we 00:08:14.539 --> 00:08:17.140 align:start position:0% satisfy some type of criteria so now we can<00:08:14.810> build<00:08:14.900> a<00:08:15.050> contract<00:08:15.560> where<00:08:16.400> each<00:08:16.789> voter 00:08:17.140 --> 00:08:17.150 align:start position:0% can build a contract where each voter 00:08:17.150 --> 00:08:19.510 align:start position:0% can build a contract where each voter they'll<00:08:17.930> do<00:08:18.139> an<00:08:18.199> L<00:08:18.319> Kamal<00:08:18.650> encrypted<00:08:19.069> vote<00:08:19.250> and 00:08:19.510 --> 00:08:19.520 align:start position:0% they'll do an L Kamal encrypted vote and 00:08:19.520 --> 00:08:21.279 align:start position:0% they'll do an L Kamal encrypted vote and they'll<00:08:20.270> stand<00:08:20.479> up<00:08:20.599> to<00:08:20.719> the<00:08:20.810> contract 00:08:21.279 --> 00:08:21.289 align:start position:0% they'll stand up to the contract 00:08:21.289 --> 00:08:24.579 align:start position:0% they'll stand up to the contract alongside<00:08:22.129> a<00:08:22.849> 1<00:08:23.270> out<00:08:23.419> of<00:08:23.509> 2<00:08:23.750> 0<00:08:24.080> Knollys<00:08:24.349> proof 00:08:24.579 --> 00:08:24.589 align:start position:0% alongside a 1 out of 2 0 Knollys proof 00:08:24.589 --> 00:08:27.399 align:start position:0% alongside a 1 out of 2 0 Knollys proof that<00:08:25.219> there's<00:08:25.460> voters<00:08:25.789> either<00:08:25.940> yes<00:08:26.240> or<00:08:26.389> no<00:08:26.449> the 00:08:27.399 --> 00:08:27.409 align:start position:0% that there's voters either yes or no the 00:08:27.409 --> 00:08:29.379 align:start position:0% that there's voters either yes or no the contract<00:08:27.860> will<00:08:28.009> accept<00:08:28.339> it<00:08:28.520> and<00:08:28.669> store<00:08:29.270> the 00:08:29.379 --> 00:08:29.389 align:start position:0% contract will accept it and store the 00:08:29.389 --> 00:08:31.450 align:start position:0% contract will accept it and store the encrypted<00:08:29.659> vote<00:08:29.960> and<00:08:30.259> every<00:08:30.919> single<00:08:31.129> voter 00:08:31.450 --> 00:08:31.460 align:start position:0% encrypted vote and every single voter 00:08:31.460 --> 00:08:33.550 align:start position:0% encrypted vote and every single voter will<00:08:31.669> do<00:08:31.819> this<00:08:32.060> then<00:08:32.990> at<00:08:33.110> the<00:08:33.229> end<00:08:33.260> of<00:08:33.440> the 00:08:33.550 --> 00:08:33.560 align:start position:0% will do this then at the end of the 00:08:33.560 --> 00:08:35.290 align:start position:0% will do this then at the end of the election<00:08:34.039> we<00:08:34.279> can<00:08:34.430> add<00:08:34.610> the<00:08:34.789> votes<00:08:34.969> together 00:08:35.290 --> 00:08:35.300 align:start position:0% election we can add the votes together 00:08:35.300 --> 00:08:38.409 align:start position:0% election we can add the votes together and<00:08:35.630> it<00:08:35.839> will<00:08:35.930> leak<00:08:36.079> the<00:08:36.199> tally<00:08:36.409> now<00:08:37.419> and 00:08:38.409 --> 00:08:38.419 align:start position:0% and it will leak the tally now and 00:08:38.419 --> 00:08:39.880 align:start position:0% and it will leak the tally now and people<00:08:38.719> want<00:08:38.930> to<00:08:38.990> know<00:08:39.079> more<00:08:39.320> about<00:08:39.440> this<00:08:39.680> type 00:08:39.880 --> 00:08:39.890 align:start position:0% people want to know more about this type 00:08:39.890 --> 00:08:42.279 align:start position:0% people want to know more about this type of<00:08:39.919> e<00:08:40.070> voting<00:08:40.399> smart<00:08:40.640> contract<00:08:41.089> I'll<00:08:41.390> be<00:08:41.990> given 00:08:42.279 --> 00:08:42.289 align:start position:0% of e voting smart contract I'll be given 00:08:42.289 --> 00:08:45.519 align:start position:0% of e voting smart contract I'll be given a<00:08:42.380> full<00:08:42.589> talk<00:08:42.890> about<00:08:43.219> it<00:08:43.430> a<00:08:43.610> tent<00:08:44.480> on<00:08:44.839> Friday 00:08:45.519 --> 00:08:45.529 align:start position:0% a full talk about it a tent on Friday 00:08:45.529 --> 00:08:47.769 align:start position:0% a full talk about it a tent on Friday morning<00:08:45.980> so<00:08:46.449> that's<00:08:47.449> just<00:08:47.630> a<00:08:47.750> little 00:08:47.769 --> 00:08:47.779 align:start position:0% morning so that's just a little 00:08:47.779 --> 00:08:49.750 align:start position:0% morning so that's just a little advertisement<00:08:48.470> for<00:08:48.769> my<00:08:48.860> talk<00:08:49.310> later<00:08:49.579> this 00:08:49.750 --> 00:08:49.760 align:start position:0% advertisement for my talk later this 00:08:49.760 --> 00:08:51.760 align:start position:0% advertisement for my talk later this week<00:08:50.029> but<00:08:50.300> let's<00:08:50.899> consider<00:08:51.230> another 00:08:51.760 --> 00:08:51.770 align:start position:0% week but let's consider another 00:08:51.770 --> 00:08:54.250 align:start position:0% week but let's consider another application<00:08:52.420> and<00:08:53.420> also<00:08:53.660> say<00:08:53.839> we<00:08:53.990> want<00:08:54.170> to 00:08:54.250 --> 00:08:54.260 align:start position:0% application and also say we want to 00:08:54.260 --> 00:08:56.030 align:start position:0% application and also say we want to source<00:08:54.709> some<00:08:54.920> type<00:08:54.949> of<00:08:55.100> competing 00:08:56.030 --> 00:08:56.040 align:start position:0% source some type of competing 00:08:56.040 --> 00:08:59.210 align:start position:0% source some type of competing so<00:08:56.779> Alice<00:08:57.779> houses<00:08:58.110> large<00:08:58.410> computations<00:08:59.100> he 00:08:59.210 --> 00:08:59.220 align:start position:0% so Alice houses large computations he 00:08:59.220 --> 00:09:02.300 align:start position:0% so Alice houses large computations he can't<00:08:59.460> to<00:08:59.580> yourself<00:08:59.970> and<00:09:00.360> now<00:09:01.080> he<00:09:01.710> finds<00:09:02.010> two 00:09:02.300 --> 00:09:02.310 align:start position:0% can't to yourself and now he finds two 00:09:02.310 --> 00:09:04.730 align:start position:0% can't to yourself and now he finds two different<00:09:02.700> cloud<00:09:02.910> providers<00:09:03.290> but<00:09:04.290> he<00:09:04.380> doesn't 00:09:04.730 --> 00:09:04.740 align:start position:0% different cloud providers but he doesn't 00:09:04.740 --> 00:09:05.930 align:start position:0% different cloud providers but he doesn't necessarily<00:09:04.800> trust<00:09:05.490> them 00:09:05.930 --> 00:09:05.940 align:start position:0% necessarily trust them 00:09:05.940 --> 00:09:08.480 align:start position:0% necessarily trust them so<00:09:06.450> she<00:09:06.510> makes<00:09:06.810> each<00:09:07.050> cloud<00:09:07.440> do<00:09:08.040> the<00:09:08.190> same 00:09:08.480 --> 00:09:08.490 align:start position:0% so she makes each cloud do the same 00:09:08.490 --> 00:09:11.510 align:start position:0% so she makes each cloud do the same exact<00:09:09.120> computation<00:09:09.570> and<00:09:10.230> then<00:09:11.190> if<00:09:11.339> she's 00:09:11.510 --> 00:09:11.520 align:start position:0% exact computation and then if she's 00:09:11.520 --> 00:09:13.820 align:start position:0% exact computation and then if she's given<00:09:11.850> the<00:09:11.940> same<00:09:12.180> result<00:09:12.570> from<00:09:13.200> both<00:09:13.500> clouds 00:09:13.820 --> 00:09:13.830 align:start position:0% given the same result from both clouds 00:09:13.830 --> 00:09:16.100 align:start position:0% given the same result from both clouds then<00:09:14.640> she<00:09:14.820> has<00:09:14.910> some<00:09:15.209> confidence<00:09:15.750> that<00:09:15.870> the 00:09:16.100 --> 00:09:16.110 align:start position:0% then she has some confidence that the 00:09:16.110 --> 00:09:18.290 align:start position:0% then she has some confidence that the competition<00:09:16.470> was<00:09:16.709> done<00:09:16.950> correctly<00:09:17.130> so<00:09:17.640> what 00:09:18.290 --> 00:09:18.300 align:start position:0% competition was done correctly so what 00:09:18.300 --> 00:09:20.930 align:start position:0% competition was done correctly so what she<00:09:18.450> wants<00:09:18.630> to<00:09:18.720> do<00:09:18.839> is<00:09:18.930> set<00:09:19.110> up<00:09:19.200> a<00:09:19.260> bounty<00:09:19.940> so 00:09:20.930 --> 00:09:20.940 align:start position:0% she wants to do is set up a bounty so 00:09:20.940 --> 00:09:22.250 align:start position:0% she wants to do is set up a bounty so now<00:09:21.089> they're<00:09:21.240> just<00:09:21.360> smart<00:09:21.600> contract<00:09:22.080> out 00:09:22.250 --> 00:09:22.260 align:start position:0% now they're just smart contract out 00:09:22.260 --> 00:09:25.100 align:start position:0% now they're just smart contract out there<00:09:22.500> and<00:09:22.770> if<00:09:23.580> the<00:09:23.730> contract<00:09:24.120> and<00:09:24.600> if<00:09:24.690> the<00:09:24.810> two 00:09:25.100 --> 00:09:25.110 align:start position:0% there and if the contract and if the two 00:09:25.110 --> 00:09:29.030 align:start position:0% there and if the contract and if the two clouds<00:09:25.529> can<00:09:25.860> prove<00:09:27.320> that<00:09:28.320> they<00:09:28.560> did<00:09:28.770> the<00:09:28.920> same 00:09:29.030 --> 00:09:29.040 align:start position:0% clouds can prove that they did the same 00:09:29.040 --> 00:09:30.920 align:start position:0% clouds can prove that they did the same computation<00:09:29.850> and<00:09:30.000> they<00:09:30.089> got<00:09:30.240> the<00:09:30.390> same<00:09:30.540> result 00:09:30.920 --> 00:09:30.930 align:start position:0% computation and they got the same result 00:09:30.930 --> 00:09:33.380 align:start position:0% computation and they got the same result the<00:09:31.830> contract<00:09:32.339> will<00:09:32.430> reward<00:09:32.580> the<00:09:32.880> clouds<00:09:33.149> for 00:09:33.380 --> 00:09:33.390 align:start position:0% the contract will reward the clouds for 00:09:33.390 --> 00:09:36.920 align:start position:0% the contract will reward the clouds for their<00:09:33.510> work<00:09:34.730> so<00:09:35.730> what<00:09:35.910> we<00:09:36.000> can<00:09:36.180> do<00:09:36.330> now<00:09:36.570> is<00:09:36.779> use 00:09:36.920 --> 00:09:36.930 align:start position:0% their work so what we can do now is use 00:09:36.930 --> 00:09:39.829 align:start position:0% their work so what we can do now is use a<00:09:36.959> Peterson<00:09:37.470> commitment<00:09:38.060> so<00:09:39.060> this<00:09:39.240> is<00:09:39.390> so<00:09:39.600> this 00:09:39.829 --> 00:09:39.839 align:start position:0% a Peterson commitment so this is so this 00:09:39.839 --> 00:09:42.290 align:start position:0% a Peterson commitment so this is so this is<00:09:40.020> different<00:09:40.410> than<00:09:40.470> a<00:09:40.529> hoss<00:09:40.770> funk<00:09:41.149> emit<00:09:42.149> Minh 00:09:42.290 --> 00:09:42.300 align:start position:0% is different than a hoss funk emit Minh 00:09:42.300 --> 00:09:44.510 align:start position:0% is different than a hoss funk emit Minh Thuy<00:09:42.390> can<00:09:43.080> do<00:09:43.230> some<00:09:43.500> type<00:09:43.649> of<00:09:43.680> computation<00:09:44.040> on 00:09:44.510 --> 00:09:44.520 align:start position:0% Thuy can do some type of computation on 00:09:44.520 --> 00:09:46.040 align:start position:0% Thuy can do some type of computation on it<00:09:44.670> wizard<00:09:45.060> known<00:09:45.180> as<00:09:45.330> echo<00:09:45.570> amorphic 00:09:46.040 --> 00:09:46.050 align:start position:0% it wizard known as echo amorphic 00:09:46.050 --> 00:09:47.990 align:start position:0% it wizard known as echo amorphic encryption<00:09:46.470> and<00:09:47.130> the<00:09:47.399> idea<00:09:47.730> is<00:09:47.790> that<00:09:47.820> is 00:09:47.990 --> 00:09:48.000 align:start position:0% encryption and the idea is that is 00:09:48.000 --> 00:09:50.269 align:start position:0% encryption and the idea is that is computationally<00:09:48.690> binding<00:09:49.110> on<00:09:49.290> his<00:09:49.770> infirmity 00:09:50.269 --> 00:09:50.279 align:start position:0% computationally binding on his infirmity 00:09:50.279 --> 00:09:52.430 align:start position:0% computationally binding on his infirmity pronounce<00:09:51.149> it<00:09:51.330> and<00:09:51.480> from<00:09:51.779> Mission 00:09:52.430 --> 00:09:52.440 align:start position:0% pronounce it and from Mission 00:09:52.440 --> 00:09:54.199 align:start position:0% pronounce it and from Mission theoretically<00:09:53.040> hiding<00:09:53.520> but<00:09:53.880> we<00:09:53.970> don't<00:09:54.089> have 00:09:54.199 --> 00:09:54.209 align:start position:0% theoretically hiding but we don't have 00:09:54.209 --> 00:09:55.910 align:start position:0% theoretically hiding but we don't have to<00:09:54.270> worry<00:09:54.420> about<00:09:54.510> those<00:09:54.750> two<00:09:54.779> properties<00:09:55.320> the 00:09:55.910 --> 00:09:55.920 align:start position:0% to worry about those two properties the 00:09:55.920 --> 00:09:57.380 align:start position:0% to worry about those two properties the idea<00:09:56.250> is<00:09:56.339> that<00:09:56.399> we<00:09:56.640> can<00:09:56.790> do<00:09:56.910> some<00:09:57.180> type<00:09:57.330> of 00:09:57.380 --> 00:09:57.390 align:start position:0% idea is that we can do some type of 00:09:57.390 --> 00:09:59.329 align:start position:0% idea is that we can do some type of commitment<00:09:57.810> on<00:09:58.170> the<00:09:58.560> fan<00:09:58.740> of<00:09:58.860> result<00:09:59.160> of<00:09:59.250> the 00:09:59.329 --> 00:09:59.339 align:start position:0% commitment on the fan of result of the 00:09:59.339 --> 00:10:02.300 align:start position:0% commitment on the fan of result of the competition<00:10:00.029> so<00:10:00.990> now<00:10:01.140> each<00:10:01.440> cloud<00:10:01.770> will<00:10:02.100> send 00:10:02.300 --> 00:10:02.310 align:start position:0% competition so now each cloud will send 00:10:02.310 --> 00:10:03.710 align:start position:0% competition so now each cloud will send their<00:10:02.430> commitment<00:10:02.820> to<00:10:02.850> the<00:10:03.000> contract<00:10:03.480> and 00:10:03.710 --> 00:10:03.720 align:start position:0% their commitment to the contract and 00:10:03.720 --> 00:10:08.329 align:start position:0% their commitment to the contract and that'll<00:10:04.320> be<00:10:04.440> stored<00:10:04.770> and<00:10:06.140> later<00:10:07.140> on<00:10:07.320> they<00:10:08.160> will 00:10:08.329 --> 00:10:08.339 align:start position:0% that'll be stored and later on they will 00:10:08.339 --> 00:10:10.880 align:start position:0% that'll be stored and later on they will reveal<00:10:08.760> an<00:10:09.089> open<00:10:09.420> our<00:10:09.570> commitment<00:10:10.080> to<00:10:10.529> Alice 00:10:10.880 --> 00:10:10.890 align:start position:0% reveal an open our commitment to Alice 00:10:10.890 --> 00:10:14.360 align:start position:0% reveal an open our commitment to Alice via<00:10:11.610> some<00:10:11.970> private<00:10:12.390> channel<00:10:12.890> Alice<00:10:13.890> can<00:10:14.220> then 00:10:14.360 --> 00:10:14.370 align:start position:0% via some private channel Alice can then 00:10:14.370 --> 00:10:16.400 align:start position:0% via some private channel Alice can then compare<00:10:14.820> proof<00:10:15.120> of<00:10:15.270> the<00:10:15.360> open<00:10:15.839> commitments 00:10:16.400 --> 00:10:16.410 align:start position:0% compare proof of the open commitments 00:10:16.410 --> 00:10:19.850 align:start position:0% compare proof of the open commitments and<00:10:16.620> she<00:10:17.370> can<00:10:17.550> see<00:10:18.080> so<00:10:19.080> you<00:10:19.140> can<00:10:19.170> see<00:10:19.500> that<00:10:19.740> they 00:10:19.850 --> 00:10:19.860 align:start position:0% and she can see so you can see that they 00:10:19.860 --> 00:10:22.550 align:start position:0% and she can see so you can see that they have<00:10:19.950> both<00:10:20.240> done<00:10:21.240> the<00:10:21.390> CM<00:10:21.630> competition<00:10:22.350> and 00:10:22.550 --> 00:10:22.560 align:start position:0% have both done the CM competition and 00:10:22.560 --> 00:10:24.320 align:start position:0% have both done the CM competition and got<00:10:22.800> the<00:10:22.920> same<00:10:23.130> result<00:10:23.550> and<00:10:23.760> they've<00:10:24.089> both 00:10:24.320 --> 00:10:24.330 align:start position:0% got the same result and they've both 00:10:24.330 --> 00:10:26.030 align:start position:0% got the same result and they've both committed<00:10:24.779> to<00:10:24.900> this<00:10:25.080> end<00:10:25.350> result<00:10:25.709> in<00:10:25.890> the 00:10:26.030 --> 00:10:26.040 align:start position:0% committed to this end result in the 00:10:26.040 --> 00:10:26.780 align:start position:0% committed to this end result in the contract 00:10:26.780 --> 00:10:26.790 align:start position:0% contract 00:10:26.790 --> 00:10:29.060 align:start position:0% contract now<00:10:27.420> what<00:10:27.600> Alice<00:10:27.959> needs<00:10:28.170> to<00:10:28.350> do<00:10:28.500> is<00:10:28.620> that<00:10:28.740> Alice 00:10:29.060 --> 00:10:29.070 align:start position:0% now what Alice needs to do is that Alice 00:10:29.070 --> 00:10:31.610 align:start position:0% now what Alice needs to do is that Alice needs<00:10:29.339> to<00:10:29.459> convince<00:10:29.760> the<00:10:30.000> contract<00:10:30.540> that<00:10:30.839> both 00:10:31.610 --> 00:10:31.620 align:start position:0% needs to convince the contract that both 00:10:31.620 --> 00:10:34.280 align:start position:0% needs to convince the contract that both of<00:10:31.650> the<00:10:31.830> clouds<00:10:32.480> did<00:10:33.480> the<00:10:33.630> computation 00:10:34.280 --> 00:10:34.290 align:start position:0% of the clouds did the computation 00:10:34.290 --> 00:10:36.710 align:start position:0% of the clouds did the computation correctly<00:10:34.770> and<00:10:34.980> that<00:10:35.640> they<00:10:35.850> did<00:10:36.089> both<00:10:36.300> indeed 00:10:36.710 --> 00:10:36.720 align:start position:0% correctly and that they did both indeed 00:10:36.720 --> 00:10:39.230 align:start position:0% correctly and that they did both indeed commit<00:10:37.140> to<00:10:37.410> the<00:10:37.529> CM<00:10:37.770> result<00:10:38.130> and<00:10:38.430> we<00:10:38.880> can<00:10:39.060> do 00:10:39.230 --> 00:10:39.240 align:start position:0% commit to the CM result and we can do 00:10:39.240 --> 00:10:41.210 align:start position:0% commit to the CM result and we can do this<00:10:39.420> using<00:10:39.630> an<00:10:39.870> equality<00:10:40.440> zero<00:10:41.040> knowledge 00:10:41.210 --> 00:10:41.220 align:start position:0% this using an equality zero knowledge 00:10:41.220 --> 00:10:44.030 align:start position:0% this using an equality zero knowledge proof<00:10:41.400> so<00:10:42.360> the<00:10:42.480> ideas<00:10:42.900> are<00:10:43.079> given<00:10:43.410> to<00:10:43.650> Peterson 00:10:44.030 --> 00:10:44.040 align:start position:0% proof so the ideas are given to Peterson 00:10:44.040 --> 00:10:48.290 align:start position:0% proof so the ideas are given to Peterson commitments<00:10:44.760> I<00:10:44.970> can<00:10:45.750> prove<00:10:45.990> to<00:10:46.050> you<00:10:46.290> that<00:10:47.300> they 00:10:48.290 --> 00:10:48.300 align:start position:0% commitments I can prove to you that they 00:10:48.300 --> 00:10:50.269 align:start position:0% commitments I can prove to you that they both<00:10:48.510> commit<00:10:48.990> to<00:10:49.170> the<00:10:49.290> same<00:10:49.529> message 00:10:50.269 --> 00:10:50.279 align:start position:0% both commit to the same message 00:10:50.279 --> 00:10:52.130 align:start position:0% both commit to the same message we're<00:10:50.790> very<00:10:51.060> revealing<00:10:51.420> about<00:10:51.630> the<00:10:51.810> message 00:10:52.130 --> 00:10:52.140 align:start position:0% we're very revealing about the message 00:10:52.140 --> 00:10:54.889 align:start position:0% we're very revealing about the message that<00:10:52.230> is<00:10:52.320> about<00:10:52.970> so<00:10:53.970> essentially<00:10:54.420> what<00:10:54.600> Alice 00:10:54.889 --> 00:10:54.899 align:start position:0% that is about so essentially what Alice 00:10:54.899 --> 00:10:57.650 align:start position:0% that is about so essentially what Alice can<00:10:55.110> do<00:10:55.290> is<00:10:55.500> that<00:10:56.370> so<00:10:56.790> you<00:10:56.850> can<00:10:57.000> say<00:10:57.149> okay<00:10:57.420> yes 00:10:57.650 --> 00:10:57.660 align:start position:0% can do is that so you can say okay yes 00:10:57.660 --> 00:11:00.590 align:start position:0% can do is that so you can say okay yes before<00:10:58.050> the<00:10:58.140> clouds<00:10:58.410> did<00:10:58.620> the<00:10:58.770> work<00:10:59.120> she<00:11:00.120> sends 00:11:00.590 --> 00:11:00.600 align:start position:0% before the clouds did the work she sends 00:11:00.600 --> 00:11:02.510 align:start position:0% before the clouds did the work she sends the<00:11:00.720> robot<00:11:01.079> or<00:11:01.290> smart<00:11:01.709> contract<00:11:02.130> as<00:11:02.250> equality 00:11:02.510 --> 00:11:02.520 align:start position:0% the robot or smart contract as equality 00:11:02.520 --> 00:11:05.720 align:start position:0% the robot or smart contract as equality proof<00:11:03.029> and<00:11:03.650> then<00:11:04.650> the<00:11:04.800> contract<00:11:05.310> will<00:11:05.459> get<00:11:05.610> the 00:11:05.720 --> 00:11:05.730 align:start position:0% proof and then the contract will get the 00:11:05.730 --> 00:11:07.340 align:start position:0% proof and then the contract will get the two<00:11:05.910> commitments<00:11:06.300> it<00:11:06.720> received<00:11:07.110> from<00:11:07.230> the 00:11:07.340 --> 00:11:07.350 align:start position:0% two commitments it received from the 00:11:07.350 --> 00:11:09.319 align:start position:0% two commitments it received from the cloud<00:11:07.620> it'll<00:11:08.550> run<00:11:08.790> it<00:11:08.910> then 00:11:09.319 --> 00:11:09.329 align:start position:0% cloud it'll run it then 00:11:09.329 --> 00:11:11.359 align:start position:0% cloud it'll run it then we'll<00:11:09.480> use<00:11:09.509> that<00:11:09.749> as<00:11:10.019> input<00:11:10.619> to<00:11:10.739> the<00:11:10.829> proof<00:11:11.100> and 00:11:11.359 --> 00:11:11.369 align:start position:0% we'll use that as input to the proof and 00:11:11.369 --> 00:11:14.179 align:start position:0% we'll use that as input to the proof and then<00:11:11.819> the<00:11:11.910> contract<00:11:12.329> will<00:11:12.480> be<00:11:12.589> convinced<00:11:13.589> that 00:11:14.179 --> 00:11:14.189 align:start position:0% then the contract will be convinced that 00:11:14.189 --> 00:11:16.539 align:start position:0% then the contract will be convinced that both<00:11:14.369> of<00:11:14.429> the<00:11:14.639> clouds<00:11:14.910> that<00:11:15.149> the<00:11:15.299> CM<00:11:15.540> work<00:11:15.749> and 00:11:16.539 --> 00:11:16.549 align:start position:0% both of the clouds that the CM work and 00:11:16.549 --> 00:11:18.679 align:start position:0% both of the clouds that the CM work and then<00:11:17.549> it<00:11:17.639> will<00:11:17.759> reward<00:11:17.879> the<00:11:18.149> cloud<00:11:18.389> for<00:11:18.660> the 00:11:18.679 --> 00:11:18.689 align:start position:0% then it will reward the cloud for the 00:11:18.689 --> 00:11:20.960 align:start position:0% then it will reward the cloud for the hard<00:11:18.929> work<00:11:19.160> so<00:11:20.160> that's<00:11:20.249> really<00:11:20.549> cool<00:11:20.819> that<00:11:20.850> we 00:11:20.960 --> 00:11:20.970 align:start position:0% hard work so that's really cool that we 00:11:20.970 --> 00:11:22.879 align:start position:0% hard work so that's really cool that we can<00:11:21.179> actually<00:11:21.329> do<00:11:21.600> this<00:11:21.749> now<00:11:22.410> of<00:11:22.529> course<00:11:22.619> in 00:11:22.879 --> 00:11:22.889 align:start position:0% can actually do this now of course in 00:11:22.889 --> 00:11:24.410 align:start position:0% can actually do this now of course in this<00:11:23.009> application<00:11:23.699> you<00:11:23.790> could<00:11:23.910> argue<00:11:24.269> well 00:11:24.410 --> 00:11:24.420 align:start position:0% this application you could argue well 00:11:24.420 --> 00:11:26.030 align:start position:0% this application you could argue well both<00:11:24.660> of<00:11:24.779> the<00:11:24.869> clouds<00:11:25.139> can<00:11:25.379> collude<00:11:25.679> and 00:11:26.030 --> 00:11:26.040 align:start position:0% both of the clouds can collude and 00:11:26.040 --> 00:11:28.249 align:start position:0% both of the clouds can collude and always<00:11:26.879> and<00:11:27.089> not<00:11:27.239> do<00:11:27.389> the<00:11:27.509> competition<00:11:28.139> but 00:11:28.249 --> 00:11:28.259 align:start position:0% always and not do the competition but 00:11:28.259 --> 00:11:30.109 align:start position:0% always and not do the competition but they<00:11:28.379> can<00:11:28.470> get<00:11:28.619> the<00:11:28.739> money<00:11:28.860> from<00:11:28.980> Alice<00:11:29.399> we're 00:11:30.109 --> 00:11:30.119 align:start position:0% they can get the money from Alice we're 00:11:30.119 --> 00:11:31.340 align:start position:0% they can get the money from Alice we're going<00:11:30.239> to<00:11:30.329> ignore<00:11:30.509> that<00:11:30.569> for<00:11:30.749> the<00:11:30.959> security 00:11:31.340 --> 00:11:31.350 align:start position:0% going to ignore that for the security 00:11:31.350 --> 00:11:33.350 align:start position:0% going to ignore that for the security experts<00:11:31.769> but<00:11:32.489> we<00:11:32.610> have<00:11:32.759> done<00:11:32.910> some<00:11:32.970> work<00:11:33.269> in 00:11:33.350 --> 00:11:33.360 align:start position:0% experts but we have done some work in 00:11:33.360 --> 00:11:34.460 align:start position:0% experts but we have done some work in this<00:11:33.480> area<00:11:33.720> so<00:11:34.079> if<00:11:34.139> you're<00:11:34.259> interested 00:11:34.460 --> 00:11:34.470 align:start position:0% this area so if you're interested 00:11:34.470 --> 00:11:36.109 align:start position:0% this area so if you're interested afterwards<00:11:35.129> I<00:11:35.220> can<00:11:35.279> talk<00:11:35.549> about<00:11:35.699> it<00:11:35.939> and 00:11:36.109 --> 00:11:36.119 align:start position:0% afterwards I can talk about it and 00:11:36.119 --> 00:11:39.350 align:start position:0% afterwards I can talk about it and offline<00:11:37.309> but<00:11:38.309> essentially<00:11:38.910> what<00:11:39.119> I<00:11:39.149> now<00:11:39.329> want 00:11:39.350 --> 00:11:39.360 align:start position:0% offline but essentially what I now want 00:11:39.360 --> 00:11:42.139 align:start position:0% offline but essentially what I now want to<00:11:39.540> talk<00:11:39.689> about<00:11:39.869> is<00:11:40.079> local<00:11:40.350> crypto<00:11:40.649> Sol<00:11:41.339> so 00:11:42.139 --> 00:11:42.149 align:start position:0% to talk about is local crypto Sol so 00:11:42.149 --> 00:11:43.519 align:start position:0% to talk about is local crypto Sol so these<00:11:42.329> cryptographic<00:11:42.689> primitives<00:11:43.379> are 00:11:43.519 --> 00:11:43.529 align:start position:0% these cryptographic primitives are 00:11:43.529 --> 00:11:45.829 align:start position:0% these cryptographic primitives are implemented<00:11:44.100> in<00:11:44.160> solidity<00:11:44.579> and<00:11:44.879> they're 00:11:45.829 --> 00:11:45.839 align:start position:0% implemented in solidity and they're 00:11:45.839 --> 00:11:48.439 align:start position:0% implemented in solidity and they're available<00:11:45.929> for<00:11:46.470> experiments<00:11:47.160> so<00:11:48.029> the<00:11:48.209> first 00:11:48.439 --> 00:11:48.449 align:start position:0% available for experiments so the first 00:11:48.449 --> 00:11:50.989 align:start position:0% available for experiments so the first three<00:11:48.689> were<00:11:48.959> used<00:11:49.259> for<00:11:49.410> my<00:11:49.559> voting<00:11:49.829> system<00:11:50.339> the 00:11:50.989 --> 00:11:50.999 align:start position:0% three were used for my voting system the 00:11:50.999 --> 00:11:53.329 align:start position:0% three were used for my voting system the second<00:11:51.509> two<00:11:51.689> were<00:11:52.199> used<00:11:52.470> in<00:11:52.619> that<00:11:52.739> antique 00:11:53.329 --> 00:11:53.339 align:start position:0% second two were used in that antique 00:11:53.339 --> 00:11:55.039 align:start position:0% second two were used in that antique illusion<00:11:53.819> smart<00:11:54.089> contracts<00:11:54.569> I<00:11:54.720> just<00:11:54.929> spoke 00:11:55.039 --> 00:11:55.049 align:start position:0% illusion smart contracts I just spoke 00:11:55.049 --> 00:11:56.689 align:start position:0% illusion smart contracts I just spoke about<00:11:55.350> and<00:11:55.739> that's<00:11:56.189> another<00:11:56.459> one<00:11:56.670> that's 00:11:56.689 --> 00:11:56.699 align:start position:0% about and that's another one that's 00:11:56.699 --> 00:11:58.549 align:start position:0% about and that's another one that's under<00:11:56.939> review<00:11:57.209> but<00:11:58.019> I<00:11:58.079> won't<00:11:58.230> go<00:11:58.350> into<00:11:58.470> that 00:11:58.549 --> 00:11:58.559 align:start position:0% under review but I won't go into that 00:11:58.559 --> 00:12:01.220 align:start position:0% under review but I won't go into that too<00:11:58.860> much<00:11:59.189> at<00:11:59.339> the<00:11:59.429> moment<00:11:59.809> but<00:12:00.809> what<00:12:00.989> would<00:12:01.139> be 00:12:01.220 --> 00:12:01.230 align:start position:0% too much at the moment but what would be 00:12:01.230 --> 00:12:03.829 align:start position:0% too much at the moment but what would be really<00:12:01.470> cool<00:12:01.799> is<00:12:02.069> that<00:12:02.660> ideally<00:12:03.660> what<00:12:03.809> I 00:12:03.829 --> 00:12:03.839 align:start position:0% really cool is that ideally what I 00:12:03.839 --> 00:12:05.150 align:start position:0% really cool is that ideally what I wanted<00:12:04.110> to<00:12:04.230> do<00:12:04.350> now<00:12:04.559> and<00:12:04.799> this<00:12:04.980> is<00:12:05.129> my 00:12:05.150 --> 00:12:05.160 align:start position:0% wanted to do now and this is my 00:12:05.160 --> 00:12:08.059 align:start position:0% wanted to do now and this is my disclaimer<00:12:05.610> I<00:12:05.999> wanted<00:12:06.989> to<00:12:07.079> have<00:12:07.199> gas<00:12:07.470> costs 00:12:08.059 --> 00:12:08.069 align:start position:0% disclaimer I wanted to have gas costs 00:12:08.069 --> 00:12:10.479 align:start position:0% disclaimer I wanted to have gas costs off<00:12:08.279> before<00:12:08.910> and<00:12:09.149> after<00:12:09.480> the<00:12:09.600> hard<00:12:09.809> fork 00:12:10.479 --> 00:12:10.489 align:start position:0% off before and after the hard fork 00:12:10.489 --> 00:12:13.249 align:start position:0% off before and after the hard fork because<00:12:11.489> now<00:12:11.939> a<00:12:11.970> theorem<00:12:12.480> supports<00:12:12.929> elliptic 00:12:13.249 --> 00:12:13.259 align:start position:0% because now a theorem supports elliptic 00:12:13.259 --> 00:12:14.889 align:start position:0% because now a theorem supports elliptic curve<00:12:13.439> mathematics<00:12:14.040> natively 00:12:14.889 --> 00:12:14.899 align:start position:0% curve mathematics natively 00:12:14.899 --> 00:12:16.699 align:start position:0% curve mathematics natively unfortunately<00:12:15.899> I've<00:12:15.989> not<00:12:16.139> money<00:12:16.350> to<00:12:16.499> get<00:12:16.589> the 00:12:16.699 --> 00:12:16.709 align:start position:0% unfortunately I've not money to get the 00:12:16.709 --> 00:12:18.739 align:start position:0% unfortunately I've not money to get the new<00:12:16.829> op<00:12:16.980> codes<00:12:17.279> to<00:12:17.459> work<00:12:17.639> so<00:12:18.269> someone<00:12:18.629> in<00:12:18.720> the 00:12:18.739 --> 00:12:18.749 align:start position:0% new op codes to work so someone in the 00:12:18.749 --> 00:12:20.659 align:start position:0% new op codes to work so someone in the room<00:12:18.809> is<00:12:19.019> very<00:12:19.230> familiar<00:12:19.470> with<00:12:19.709> that<00:12:19.980> you<00:12:20.519> can 00:12:20.659 --> 00:12:20.669 align:start position:0% room is very familiar with that you can 00:12:20.669 --> 00:12:22.669 align:start position:0% room is very familiar with that you can talk<00:12:20.850> to<00:12:20.999> me<00:12:21.119> afterwards<00:12:21.239> and<00:12:21.689> hopefully<00:12:22.529> for 00:12:22.669 --> 00:12:22.679 align:start position:0% talk to me afterwards and hopefully for 00:12:22.679 --> 00:12:24.769 align:start position:0% talk to me afterwards and hopefully for Fredi<00:12:22.980> I<00:12:23.100> can<00:12:23.369> have<00:12:23.459> updated<00:12:23.910> gas<00:12:24.209> costs<00:12:24.689> and 00:12:24.769 --> 00:12:24.779 align:start position:0% Fredi I can have updated gas costs and 00:12:24.779 --> 00:12:26.809 align:start position:0% Fredi I can have updated gas costs and how<00:12:24.869> expensive<00:12:25.049> this<00:12:25.470> is<00:12:25.529> I'll<00:12:26.279> give<00:12:26.610> you<00:12:26.699> an 00:12:26.809 --> 00:12:26.819 align:start position:0% how expensive this is I'll give you an 00:12:26.819 --> 00:12:28.999 align:start position:0% how expensive this is I'll give you an example<00:12:26.910> so<00:12:27.509> the<00:12:27.989> one<00:12:28.199> out<00:12:28.319> of<00:12:28.410> two<00:12:28.649> zero 00:12:28.999 --> 00:12:29.009 align:start position:0% example so the one out of two zero 00:12:29.009 --> 00:12:31.489 align:start position:0% example so the one out of two zero knowledge<00:12:29.160> proof<00:12:29.480> before<00:12:30.480> the<00:12:30.869> hard<00:12:31.110> fork 00:12:31.489 --> 00:12:31.499 align:start position:0% knowledge proof before the hard fork 00:12:31.499 --> 00:12:33.619 align:start position:0% knowledge proof before the hard fork would<00:12:31.980> cost<00:12:32.279> two<00:12:32.549> point<00:12:32.819> five<00:12:32.999> million<00:12:33.329> gas 00:12:33.619 --> 00:12:33.629 align:start position:0% would cost two point five million gas 00:12:33.629 --> 00:12:36.019 align:start position:0% would cost two point five million gas which<00:12:34.529> is<00:12:34.649> really<00:12:34.949> expensive<00:12:35.160> considering<00:12:35.850> a 00:12:36.019 --> 00:12:36.029 align:start position:0% which is really expensive considering a 00:12:36.029 --> 00:12:38.329 align:start position:0% which is really expensive considering a block<00:12:36.540> only<00:12:36.720> contain<00:12:37.110> seven<00:12:37.529> million<00:12:37.679> gas<00:12:37.980> I 00:12:38.329 --> 00:12:38.339 align:start position:0% block only contain seven million gas I 00:12:38.339 --> 00:12:40.100 align:start position:0% block only contain seven million gas I think<00:12:38.790> that's<00:12:38.939> roughly<00:12:39.149> like<00:12:39.269> three<00:12:39.809> or<00:12:39.929> four 00:12:40.100 --> 00:12:40.110 align:start position:0% think that's roughly like three or four 00:12:40.110 --> 00:12:42.379 align:start position:0% think that's roughly like three or four dollars<00:12:40.290> or<00:12:40.649> something<00:12:40.829> where<00:12:41.790> now<00:12:42.059> that<00:12:42.299> the 00:12:42.379 --> 00:12:42.389 align:start position:0% dollars or something where now that the 00:12:42.389 --> 00:12:44.509 align:start position:0% dollars or something where now that the hard<00:12:42.569> forks<00:12:42.869> happened<00:12:43.259> the<00:12:43.679> gas<00:12:43.949> cost<00:12:44.339> should 00:12:44.509 --> 00:12:44.519 align:start position:0% hard forks happened the gas cost should 00:12:44.519 --> 00:12:46.400 align:start position:0% hard forks happened the gas cost should hopefully<00:12:44.730> be<00:12:44.910> in<00:12:45.089> the<00:12:45.179> region<00:12:45.360> of<00:12:45.600> 200-300 00:12:46.400 --> 00:12:46.410 align:start position:0% hopefully be in the region of 200-300 00:12:46.410 --> 00:12:49.069 align:start position:0% hopefully be in the region of 200-300 thousand<00:12:47.009> gas<00:12:47.129> but<00:12:48.029> I<00:12:48.059> still<00:12:48.299> need<00:12:48.480> a<00:12:48.509> you<00:12:48.959> know 00:12:49.069 --> 00:12:49.079 align:start position:0% thousand gas but I still need a you know 00:12:49.079 --> 00:12:50.869 align:start position:0% thousand gas but I still need a you know get<00:12:49.259> experimental<00:12:49.949> results<00:12:50.309> to<00:12:50.429> say<00:12:50.579> yes<00:12:50.850> that 00:12:50.869 --> 00:12:50.879 align:start position:0% get experimental results to say yes that 00:12:50.879 --> 00:12:54.799 align:start position:0% get experimental results to say yes that is<00:12:51.209> actually<00:12:51.509> the<00:12:51.600> real<00:12:51.720> cost<00:12:51.779> cost<00:12:53.419> now<00:12:54.419> I 00:12:54.799 --> 00:12:54.809 align:start position:0% is actually the real cost cost now I 00:12:54.809 --> 00:12:56.900 align:start position:0% is actually the real cost cost now I like<00:12:55.769> the<00:12:55.889> finish<00:12:56.220> talking<00:12:56.459> about<00:12:56.610> other 00:12:56.900 --> 00:12:56.910 align:start position:0% like the finish talking about other 00:12:56.910 --> 00:12:58.699 align:start position:0% like the finish talking about other pieces<00:12:57.269> of<00:12:57.540> work<00:12:57.720> so<00:12:58.290> I'm<00:12:58.410> not<00:12:58.439> the<00:12:58.589> only 00:12:58.699 --> 00:12:58.709 align:start position:0% pieces of work so I'm not the only 00:12:58.709 --> 00:13:00.169 align:start position:0% pieces of work so I'm not the only researcher<00:12:59.489> who's<00:12:59.669> been<00:12:59.850> looking<00:12:59.970> at 00:13:00.169 --> 00:13:00.179 align:start position:0% researcher who's been looking at 00:13:00.179 --> 00:13:01.729 align:start position:0% researcher who's been looking at applications<00:13:00.839> of<00:13:00.899> cryptography<00:13:01.079> on<00:13:01.649> the 00:13:01.729 --> 00:13:01.739 align:start position:0% applications of cryptography on the 00:13:01.739 --> 00:13:03.530 align:start position:0% applications of cryptography on the blockchain<00:13:01.949> and<00:13:02.339> I'm<00:13:03.149> going<00:13:03.299> to<00:13:03.360> highlight 00:13:03.530 --> 00:13:03.540 align:start position:0% blockchain and I'm going to highlight 00:13:03.540 --> 00:13:04.909 align:start position:0% blockchain and I'm going to highlight some<00:13:03.689> papers<00:13:04.319> that<00:13:04.410> I<00:13:04.470> thought<00:13:04.769> were<00:13:04.889> really 00:13:04.909 --> 00:13:04.919 align:start position:0% some papers that I thought were really 00:13:04.919 --> 00:13:07.220 align:start position:0% some papers that I thought were really interesting<00:13:05.329> so<00:13:06.329> one<00:13:06.540> was<00:13:06.689> by<00:13:06.809> Andre<00:13:07.139> Miller 00:13:07.220 --> 00:13:07.230 align:start position:0% interesting so one was by Andre Miller 00:13:07.230 --> 00:13:09.949 align:start position:0% interesting so one was by Andre Miller called<00:13:07.919> decentralized<00:13:08.639> poker<00:13:09.029> and<00:13:09.179> the<00:13:09.660> idea 00:13:09.949 --> 00:13:09.959 align:start position:0% called decentralized poker and the idea 00:13:09.959 --> 00:13:11.989 align:start position:0% called decentralized poker and the idea is<00:13:10.049> that<00:13:10.079> a<00:13:10.199> group<00:13:10.470> of<00:13:10.589> people<00:13:10.739> can<00:13:11.549> play<00:13:11.730> poker 00:13:11.989 --> 00:13:11.999 align:start position:0% is that a group of people can play poker 00:13:11.999 --> 00:13:14.749 align:start position:0% is that a group of people can play poker as<00:13:12.239> a<00:13:12.269> smart<00:13:12.569> contract<00:13:12.779> and<00:13:13.669> everything<00:13:14.669> is 00:13:14.749 --> 00:13:14.759 align:start position:0% as a smart contract and everything is 00:13:14.759 --> 00:13:17.720 align:start position:0% as a smart contract and everything is done<00:13:14.939> using<00:13:15.119> cryptography<00:13:15.739> so<00:13:16.739> we<00:13:16.860> can<00:13:17.069> ensure 00:13:17.720 --> 00:13:17.730 align:start position:0% done using cryptography so we can ensure 00:13:17.730 --> 00:13:20.179 align:start position:0% done using cryptography so we can ensure that<00:13:17.970> the<00:13:18.209> cards<00:13:18.539> are<00:13:18.689> shuffled<00:13:19.189> correctly 00:13:20.179 --> 00:13:20.189 align:start position:0% that the cards are shuffled correctly 00:13:20.189 --> 00:13:22.189 align:start position:0% that the cards are shuffled correctly and<00:13:20.519> that<00:13:20.910> I<00:13:20.939> have<00:13:21.089> two<00:13:21.299> private<00:13:21.779> cars<00:13:21.990> and 00:13:22.189 --> 00:13:22.199 align:start position:0% and that I have two private cars and 00:13:22.199 --> 00:13:23.060 align:start position:0% and that I have two private cars and we're<00:13:22.289> actually<00:13:22.410> playing<00:13:22.679> this 00:13:23.060 --> 00:13:23.070 align:start position:0% we're actually playing this 00:13:23.070 --> 00:13:25.160 align:start position:0% we're actually playing this in<00:13:23.370> a<00:13:23.850> way<00:13:24.000> where<00:13:24.180> everybody<00:13:24.390> can<00:13:24.690> verify<00:13:24.960> that 00:13:25.160 --> 00:13:25.170 align:start position:0% in a way where everybody can verify that 00:13:25.170 --> 00:13:28.040 align:start position:0% in a way where everybody can verify that is<00:13:25.410> correct<00:13:25.980> the<00:13:26.580> second<00:13:27.060> one<00:13:27.180> is<00:13:27.390> by<00:13:27.660> Sarah 00:13:28.040 --> 00:13:28.050 align:start position:0% is correct the second one is by Sarah 00:13:28.050 --> 00:13:31.130 align:start position:0% is correct the second one is by Sarah Michael<00:13:28.380> John<00:13:28.590> he<00:13:29.070> works<00:13:29.310> with<00:13:29.430> me<00:13:29.580> at<00:13:29.670> UCL<00:13:30.150> and 00:13:31.130 --> 00:13:31.140 align:start position:0% Michael John he works with me at UCL and 00:13:31.140 --> 00:13:32.630 align:start position:0% Michael John he works with me at UCL and the<00:13:31.320> other<00:13:31.440> scheme<00:13:31.800> was<00:13:31.950> a<00:13:31.980> bit<00:13:32.220> similar<00:13:32.550> the 00:13:32.630 --> 00:13:32.640 align:start position:0% the other scheme was a bit similar the 00:13:32.640 --> 00:13:35.090 align:start position:0% the other scheme was a bit similar the coin<00:13:32.820> joint<00:13:33.150> so<00:13:33.750> everyone<00:13:34.200> can<00:13:34.380> deposit<00:13:34.680> coins 00:13:35.090 --> 00:13:35.100 align:start position:0% coin joint so everyone can deposit coins 00:13:35.100 --> 00:13:37.520 align:start position:0% coin joint so everyone can deposit coins and<00:13:35.490> the<00:13:35.940> essential<00:13:36.240> smart<00:13:36.630> contract<00:13:37.110> and 00:13:37.520 --> 00:13:37.530 align:start position:0% and the essential smart contract and 00:13:37.530 --> 00:13:39.890 align:start position:0% and the essential smart contract and then<00:13:37.890> using<00:13:38.190> ring<00:13:38.370> signatures<00:13:38.970> they<00:13:39.600> can<00:13:39.780> have 00:13:39.890 --> 00:13:39.900 align:start position:0% then using ring signatures they can have 00:13:39.900 --> 00:13:41.720 align:start position:0% then using ring signatures they can have draw<00:13:40.110> their<00:13:40.290> coins<00:13:40.560> back<00:13:40.920> from<00:13:41.130> the<00:13:41.250> contract 00:13:41.720 --> 00:13:41.730 align:start position:0% draw their coins back from the contract 00:13:41.730 --> 00:13:43.640 align:start position:0% draw their coins back from the contract in<00:13:41.940> such<00:13:42.480> a<00:13:42.510> way<00:13:42.720> where<00:13:42.930> they're<00:13:43.080> hiding<00:13:43.260> in<00:13:43.560> a 00:13:43.640 --> 00:13:43.650 align:start position:0% in such a way where they're hiding in a 00:13:43.650 --> 00:13:45.680 align:start position:0% in such a way where they're hiding in a group<00:13:43.890> so<00:13:44.520> that's<00:13:44.640> the<00:13:44.850> achieve<00:13:45.120> some<00:13:45.450> type<00:13:45.660> of 00:13:45.680 --> 00:13:45.690 align:start position:0% group so that's the achieve some type of 00:13:45.690 --> 00:13:47.780 align:start position:0% group so that's the achieve some type of financial<00:13:46.080> privacy<00:13:46.410> and<00:13:46.920> it's<00:13:47.520> actually 00:13:47.780 --> 00:13:47.790 align:start position:0% financial privacy and it's actually 00:13:47.790 --> 00:13:48.860 align:start position:0% financial privacy and it's actually really<00:13:47.970> cool<00:13:48.270> so<00:13:48.480> I<00:13:48.540> highly<00:13:48.780> recommend 00:13:48.860 --> 00:13:48.870 align:start position:0% really cool so I highly recommend 00:13:48.870 --> 00:13:51.620 align:start position:0% really cool so I highly recommend reading<00:13:49.410> that<00:13:49.710> one<00:13:49.890> the<00:13:50.580> second<00:13:51.000> ones<00:13:51.180> are<00:13:51.480> the 00:13:51.620 --> 00:13:51.630 align:start position:0% reading that one the second ones are the 00:13:51.630 --> 00:13:54.050 align:start position:0% reading that one the second ones are the third<00:13:51.840> ones<00:13:52.050> done<00:13:52.230> by<00:13:52.350> Arthur's<00:13:52.800> group<00:13:53.070> at<00:13:53.280> ETH 00:13:54.050 --> 00:13:54.060 align:start position:0% third ones done by Arthur's group at ETH 00:13:54.060 --> 00:13:55.970 align:start position:0% third ones done by Arthur's group at ETH Zurich<00:13:54.390> and<00:13:54.660> the<00:13:55.080> idea<00:13:55.410> is<00:13:55.500> that<00:13:55.590> lots<00:13:55.860> of 00:13:55.970 --> 00:13:55.980 align:start position:0% Zurich and the idea is that lots of 00:13:55.980 --> 00:13:57.950 align:start position:0% Zurich and the idea is that lots of Saveur<00:13:56.220> contract<00:13:56.760> is<00:13:56.940> a<00:13:57.000> padding<00:13:57.450> contract 00:13:57.950 --> 00:13:57.960 align:start position:0% Saveur contract is a padding contract 00:13:57.960 --> 00:14:00.110 align:start position:0% Saveur contract is a padding contract and<00:13:58.230> I<00:13:58.530> am<00:13:58.590> Betty<00:13:58.860> the<00:13:59.040> Newcastle<00:13:59.460> United<00:14:00.000> is 00:14:00.110 --> 00:14:00.120 align:start position:0% and I am Betty the Newcastle United is 00:14:00.120 --> 00:14:01.490 align:start position:0% and I am Betty the Newcastle United is finally<00:14:00.480> going<00:14:00.630> to<00:14:00.690> win<00:14:00.840> the<00:14:00.960> Premier<00:14:01.350> League 00:14:01.490 --> 00:14:01.500 align:start position:0% finally going to win the Premier League 00:14:01.500 --> 00:14:04.640 align:start position:0% finally going to win the Premier League we<00:14:02.010> still<00:14:02.250> never<00:14:02.400> do<00:14:02.700> but<00:14:03.510> let's<00:14:03.690> say<00:14:03.990> I<00:14:04.260> go<00:14:04.560> on 00:14:04.640 --> 00:14:04.650 align:start position:0% we still never do but let's say I go on 00:14:04.650 --> 00:14:06.950 align:start position:0% we still never do but let's say I go on the<00:14:04.740> BBC<00:14:05.190> website<00:14:05.220> and<00:14:05.880> then<00:14:06.420> the<00:14:06.510> BBC 00:14:06.950 --> 00:14:06.960 align:start position:0% the BBC website and then the BBC 00:14:06.960 --> 00:14:08.900 align:start position:0% the BBC website and then the BBC confirms<00:14:07.440> that<00:14:07.680> while<00:14:07.920> Newcastle<00:14:08.610> United 00:14:08.900 --> 00:14:08.910 align:start position:0% confirms that while Newcastle United 00:14:08.910 --> 00:14:10.550 align:start position:0% confirms that while Newcastle United actually<00:14:09.300> did<00:14:09.450> win<00:14:09.600> the<00:14:09.630> Premier<00:14:10.080> League<00:14:10.260> I 00:14:10.550 --> 00:14:10.560 align:start position:0% actually did win the Premier League I 00:14:10.560 --> 00:14:12.890 align:start position:0% actually did win the Premier League I can<00:14:11.310> they<00:14:11.430> improve<00:14:11.730> to<00:14:11.850> the<00:14:12.060> contract<00:14:12.630> that 00:14:12.890 --> 00:14:12.900 align:start position:0% can they improve to the contract that 00:14:12.900 --> 00:14:15.080 align:start position:0% can they improve to the contract that the<00:14:12.990> BBC<00:14:13.320> said<00:14:13.740> that<00:14:13.950> to<00:14:14.100> me<00:14:14.220> and<00:14:14.460> that's 00:14:15.080 --> 00:14:15.090 align:start position:0% the BBC said that to me and that's 00:14:15.090 --> 00:14:17.840 align:start position:0% the BBC said that to me and that's really<00:14:15.420> useful<00:14:15.990> for<00:14:16.890> any<00:14:17.070> Oracle<00:14:17.640> tape 00:14:17.840 --> 00:14:17.850 align:start position:0% really useful for any Oracle tape 00:14:17.850 --> 00:14:21.740 align:start position:0% really useful for any Oracle tape service<00:14:19.520> the<00:14:20.520> third<00:14:20.820> or<00:14:21.060> the<00:14:21.090> fourth<00:14:21.330> one<00:14:21.630> is 00:14:21.740 --> 00:14:21.750 align:start position:0% service the third or the fourth one is 00:14:21.750 --> 00:14:23.750 align:start position:0% service the third or the fourth one is publicly<00:14:22.170> verifiable<00:14:22.380> seeker<00:14:23.040> sharing<00:14:23.460> so 00:14:23.750 --> 00:14:23.760 align:start position:0% publicly verifiable seeker sharing so 00:14:23.760 --> 00:14:25.970 align:start position:0% publicly verifiable seeker sharing so this<00:14:23.910> is<00:14:24.030> the<00:14:24.150> scrape<00:14:24.420> protocol<00:14:24.960> and<00:14:25.230> the<00:14:25.650> idea 00:14:25.970 --> 00:14:25.980 align:start position:0% this is the scrape protocol and the idea 00:14:25.980 --> 00:14:28.310 align:start position:0% this is the scrape protocol and the idea is<00:14:26.070> that<00:14:26.100> they<00:14:26.340> design<00:14:26.730> this<00:14:26.940> scheme<00:14:27.300> the<00:14:28.050> work 00:14:28.310 --> 00:14:28.320 align:start position:0% is that they design this scheme the work 00:14:28.320 --> 00:14:29.960 align:start position:0% is that they design this scheme the work towards<00:14:28.800> building<00:14:28.980> a<00:14:29.280> publicly<00:14:29.730> verifiable 00:14:29.960 --> 00:14:29.970 align:start position:0% towards building a publicly verifiable 00:14:29.970 --> 00:14:32.510 align:start position:0% towards building a publicly verifiable random<00:14:30.720> beacon<00:14:31.080> and<00:14:31.290> this<00:14:31.920> means<00:14:32.160> that<00:14:32.310> you 00:14:32.510 --> 00:14:32.520 align:start position:0% random beacon and this means that you 00:14:32.520 --> 00:14:34.040 align:start position:0% random beacon and this means that you could<00:14:32.610> have<00:14:32.670> some<00:14:32.910> tape<00:14:33.060> a<00:14:33.090> random<00:14:33.510> number<00:14:33.690> on 00:14:34.040 --> 00:14:34.050 align:start position:0% could have some tape a random number on 00:14:34.050 --> 00:14:36.440 align:start position:0% could have some tape a random number on aetherium<00:14:34.440> every<00:14:35.310> so<00:14:35.490> often<00:14:35.700> and<00:14:36.090> that's 00:14:36.440 --> 00:14:36.450 align:start position:0% aetherium every so often and that's 00:14:36.450 --> 00:14:38.030 align:start position:0% aetherium every so often and that's really<00:14:36.750> useful<00:14:37.140> for<00:14:37.230> gambling<00:14:37.620> games<00:14:37.890> and 00:14:38.030 --> 00:14:38.040 align:start position:0% really useful for gambling games and 00:14:38.040 --> 00:14:38.800 align:start position:0% really useful for gambling games and everything<00:14:38.370> else 00:14:38.800 --> 00:14:38.810 align:start position:0% everything else 00:14:38.810 --> 00:14:41.300 align:start position:0% everything else we<00:14:39.810> built<00:14:40.080> that<00:14:40.140> in<00:14:40.380> as<00:14:40.470> well<00:14:40.650> I<00:14:40.680> built<00:14:40.980> that<00:14:41.190> in 00:14:41.300 --> 00:14:41.310 align:start position:0% we built that in as well I built that in 00:14:41.310 --> 00:14:43.490 align:start position:0% we built that in as well I built that in its<00:14:41.460> solidity<00:14:41.700> but<00:14:42.420> it's<00:14:42.570> only<00:14:42.930> towards<00:14:43.320> that 00:14:43.490 --> 00:14:43.500 align:start position:0% its solidity but it's only towards that 00:14:43.500 --> 00:14:45.650 align:start position:0% its solidity but it's only towards that goal<00:14:43.740> and<00:14:43.770> doesn't<00:14:44.280> achieve<00:14:44.370> it<00:14:44.700> yet<00:14:44.910> of 00:14:45.650 --> 00:14:45.660 align:start position:0% goal and doesn't achieve it yet of 00:14:45.660 --> 00:14:47.090 align:start position:0% goal and doesn't achieve it yet of course<00:14:45.960> there's<00:14:46.200> my<00:14:46.350> anonymous<00:14:46.890> voting 00:14:47.090 --> 00:14:47.100 align:start position:0% course there's my anonymous voting 00:14:47.100 --> 00:14:49.670 align:start position:0% course there's my anonymous voting protocol<00:14:47.700> on<00:14:47.910> the<00:14:48.780> country<00:14:49.290> collusion 00:14:49.670 --> 00:14:49.680 align:start position:0% protocol on the country collusion 00:14:49.680 --> 00:14:51.280 align:start position:0% protocol on the country collusion contracts<00:14:50.130> that<00:14:50.220> I<00:14:50.310> spoke<00:14:50.520> about<00:14:50.760> just<00:14:50.910> before 00:14:51.280 --> 00:14:51.290 align:start position:0% contracts that I spoke about just before 00:14:51.290 --> 00:14:53.720 align:start position:0% contracts that I spoke about just before so<00:14:52.290> thank<00:14:52.530> you<00:14:52.680> very<00:14:52.770> much<00:14:53.160> for<00:14:53.340> listening<00:14:53.400> to 00:14:53.720 --> 00:14:53.730 align:start position:0% so thank you very much for listening to 00:14:53.730 --> 00:14:56.900 align:start position:0% so thank you very much for listening to this<00:14:53.880> talk<00:14:54.150> before<00:14:55.110> I<00:14:55.140> finish<00:14:55.650> I<00:14:55.920> have<00:14:56.640> one 00:14:56.900 --> 00:14:56.910 align:start position:0% this talk before I finish I have one 00:14:56.910 --> 00:14:59.390 align:start position:0% this talk before I finish I have one takeaway<00:14:57.300> message<00:14:57.810> key<00:14:58.560> photography<00:14:59.130> is<00:14:59.250> only 00:14:59.390 --> 00:14:59.400 align:start position:0% takeaway message key photography is only 00:14:59.400 --> 00:15:02.450 align:start position:0% takeaway message key photography is only one<00:14:59.730> two<00:15:00.090> and<00:15:00.420> our<00:15:00.600> toolboxes<00:15:01.260> engineers<00:15:01.710> to 00:15:02.450 --> 00:15:02.460 align:start position:0% one two and our toolboxes engineers to 00:15:02.460 --> 00:15:04.970 align:start position:0% one two and our toolboxes engineers to solve<00:15:02.730> problems<00:15:03.270> and<00:15:03.540> if<00:15:04.500> you<00:15:04.650> think 00:15:04.970 --> 00:15:04.980 align:start position:0% solve problems and if you think 00:15:04.980 --> 00:15:06.380 align:start position:0% solve problems and if you think cryptography<00:15:05.730> can<00:15:05.910> solve<00:15:06.180> your<00:15:06.330> problem 00:15:06.380 --> 00:15:06.390 align:start position:0% cryptography can solve your problem 00:15:06.390 --> 00:15:08.750 align:start position:0% cryptography can solve your problem alone<00:15:07.050> then<00:15:07.890> there's<00:15:08.070> a<00:15:08.130> really<00:15:08.370> good<00:15:08.550> quote 00:15:08.750 --> 00:15:08.760 align:start position:0% alone then there's a really good quote 00:15:08.760 --> 00:15:10.700 align:start position:0% alone then there's a really good quote by<00:15:08.940> Roger<00:15:09.180> Needham<00:15:09.570> he<00:15:09.930> was<00:15:10.050> a<00:15:10.080> professor<00:15:10.440> at 00:15:10.700 --> 00:15:10.710 align:start position:0% by Roger Needham he was a professor at 00:15:10.710 --> 00:15:13.040 align:start position:0% by Roger Needham he was a professor at Cambridge<00:15:11.160> in<00:15:11.430> the<00:15:11.880> eighties<00:15:12.240> 90s<00:15:12.810> and 00:15:13.040 --> 00:15:13.050 align:start position:0% Cambridge in the eighties 90s and 00:15:13.050 --> 00:15:15.860 align:start position:0% Cambridge in the eighties 90s and eventually<00:15:13.620> in<00:15:13.890> the<00:15:14.400> early<00:15:14.640> 2000s<00:15:15.300> and<00:15:15.480> he 00:15:15.860 --> 00:15:15.870 align:start position:0% eventually in the early 2000s and he 00:15:15.870 --> 00:15:17.960 align:start position:0% eventually in the early 2000s and he said<00:15:16.140> if<00:15:16.440> you<00:15:16.890> think<00:15:17.190> of<00:15:17.310> tog<00:15:17.490> R<00:15:17.520> we<00:15:17.640> can<00:15:17.700> solve 00:15:17.960 --> 00:15:17.970 align:start position:0% said if you think of tog R we can solve 00:15:17.970 --> 00:15:19.760 align:start position:0% said if you think of tog R we can solve your<00:15:18.120> problem<00:15:18.630> you<00:15:18.990> either<00:15:19.080> don't<00:15:19.350> understand 00:15:19.760 --> 00:15:19.770 align:start position:0% your problem you either don't understand 00:15:19.770 --> 00:15:21.770 align:start position:0% your problem you either don't understand cryptography<00:15:20.400> or<00:15:20.730> you<00:15:21.180> don't<00:15:21.300> understand 00:15:21.770 --> 00:15:21.780 align:start position:0% cryptography or you don't understand 00:15:21.780 --> 00:15:34.500 align:start position:0% cryptography or you don't understand your<00:15:21.960> problem<00:15:22.190> thank<00:15:23.190> you<00:15:23.310> for<00:15:23.460> listening 00:15:34.500 --> 00:15:34.510 align:start position:0% 00:15:34.510 --> 00:15:42.090 align:start position:0% [Music]