WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:17.510 align:start position:0% [Music] 00:00:17.510 --> 00:00:17.520 align:start position:0% 00:00:17.520 --> 00:00:20.109 align:start position:0% hey<00:00:17.840> I'm<00:00:18.039> Tyler<00:00:18.600> I<00:00:18.720> go<00:00:18.920> by<00:00:19.240> at<00:00:19.560> hard<00:00:19.720> engineer 00:00:20.109 --> 00:00:20.119 align:start position:0% hey I'm Tyler I go by at hard engineer 00:00:20.119 --> 00:00:23.109 align:start position:0% hey I'm Tyler I go by at hard engineer on<00:00:20.240> the<00:00:20.359> internet<00:00:21.080> and<00:00:21.320> this<00:00:21.439> is<00:00:21.720> ying<00:00:22.080> Tong<00:00:22.960> um 00:00:23.109 --> 00:00:23.119 align:start position:0% on the internet and this is ying Tong um 00:00:23.119 --> 00:00:25.589 align:start position:0% on the internet and this is ying Tong um so<00:00:23.279> I'm<00:00:23.359> an<00:00:23.519> engineer<00:00:24.119> she's<00:00:24.400> a<00:00:24.599> cryptographer 00:00:25.589 --> 00:00:25.599 align:start position:0% so I'm an engineer she's a cryptographer 00:00:25.599 --> 00:00:26.990 align:start position:0% so I'm an engineer she's a cryptographer so<00:00:25.720> we're<00:00:25.880> going<00:00:25.960> to<00:00:26.119> kind<00:00:26.279> of<00:00:26.480> go<00:00:26.679> back<00:00:26.800> and 00:00:26.990 --> 00:00:27.000 align:start position:0% so we're going to kind of go back and 00:00:27.000 --> 00:00:30.269 align:start position:0% so we're going to kind of go back and forth<00:00:27.760> between<00:00:28.760> uh<00:00:28.920> the<00:00:29.119> mathematical<00:00:29.720> View 00:00:30.269 --> 00:00:30.279 align:start position:0% forth between uh the mathematical View 00:00:30.279 --> 00:00:32.069 align:start position:0% forth between uh the mathematical View and<00:00:30.400> then<00:00:30.560> like<00:00:30.679> the<00:00:30.800> Layman's<00:00:31.279> explanations 00:00:32.069 --> 00:00:32.079 align:start position:0% and then like the Layman's explanations 00:00:32.079 --> 00:00:36.030 align:start position:0% and then like the Layman's explanations for<00:00:32.480> a<00:00:32.599> lot<00:00:32.800> of<00:00:33.800> uh<00:00:33.960> introductory 00:00:36.030 --> 00:00:36.040 align:start position:0% for a lot of uh introductory 00:00:36.040 --> 00:00:38.590 align:start position:0% for a lot of uh introductory cryptography<00:00:37.040> so<00:00:37.480> cryptography<00:00:38.160> really<00:00:38.399> is 00:00:38.590 --> 00:00:38.600 align:start position:0% cryptography so cryptography really is 00:00:38.600 --> 00:00:41.389 align:start position:0% cryptography so cryptography really is kind<00:00:38.719> of<00:00:38.840> a<00:00:39.040> blend<00:00:39.399> of<00:00:39.559> Art<00:00:39.800> and<00:00:40.239> Science<00:00:41.239> and 00:00:41.389 --> 00:00:41.399 align:start position:0% kind of a blend of Art and Science and 00:00:41.399 --> 00:00:46.029 align:start position:0% kind of a blend of Art and Science and it's<00:00:41.520> the<00:00:41.640> Art<00:00:41.760> and<00:00:41.879> Science<00:00:42.160> Of 00:00:46.029 --> 00:00:46.039 align:start position:0% 00:00:46.039 --> 00:00:48.630 align:start position:0% Secrets<00:00:47.039> um<00:00:47.239> all<00:00:47.320> right<00:00:47.520> yep<00:00:47.719> this<00:00:47.800> one's<00:00:48.079> you 00:00:48.630 --> 00:00:48.640 align:start position:0% Secrets um all right yep this one's you 00:00:48.640 --> 00:00:51.470 align:start position:0% Secrets um all right yep this one's you yeah<00:00:48.840> and<00:00:49.280> often<00:00:49.719> times<00:00:50.280> we<00:00:50.520> think<00:00:50.879> of<00:00:51.239> the 00:00:51.470 --> 00:00:51.480 align:start position:0% yeah and often times we think of the 00:00:51.480 --> 00:00:54.510 align:start position:0% yeah and often times we think of the purpose<00:00:52.120> of<00:00:52.280> a<00:00:52.440> cryptographic<00:00:53.359> system<00:00:54.359> in 00:00:54.510 --> 00:00:54.520 align:start position:0% purpose of a cryptographic system in 00:00:54.520 --> 00:00:59.029 align:start position:0% purpose of a cryptographic system in terms<00:00:55.120> of<00:00:56.120> um<00:00:56.359> these<00:00:56.640> three<00:00:56.960> properties<00:00:58.039> CIA 00:00:59.029 --> 00:00:59.039 align:start position:0% terms of um these three properties CIA 00:00:59.039 --> 00:01:02.270 align:start position:0% terms of um these three properties CIA um<00:00:59.640> so<00:01:00.199> firstly 00:01:02.270 --> 00:01:02.280 align:start position:0% um so firstly 00:01:02.280 --> 00:01:04.910 align:start position:0% um so firstly confidentiality<00:01:03.280> um<00:01:03.680> the<00:01:03.879> property<00:01:04.400> of 00:01:04.910 --> 00:01:04.920 align:start position:0% confidentiality um the property of 00:01:04.920 --> 00:01:07.310 align:start position:0% confidentiality um the property of keeping<00:01:05.239> your<00:01:05.439> messages<00:01:06.040> secret<00:01:07.000> and 00:01:07.310 --> 00:01:07.320 align:start position:0% keeping your messages secret and 00:01:07.320 --> 00:01:10.550 align:start position:0% keeping your messages secret and ensuring<00:01:07.880> that<00:01:08.200> they're<00:01:08.439> only<00:01:08.799> ever<00:01:09.119> read<00:01:10.080> by 00:01:10.550 --> 00:01:10.560 align:start position:0% ensuring that they're only ever read by 00:01:10.560 --> 00:01:12.630 align:start position:0% ensuring that they're only ever read by their<00:01:10.799> intended 00:01:12.630 --> 00:01:12.640 align:start position:0% their intended 00:01:12.640 --> 00:01:16.910 align:start position:0% their intended recipient<00:01:14.000> Integrity<00:01:15.000> um<00:01:15.720> being<00:01:16.159> assured 00:01:16.910 --> 00:01:16.920 align:start position:0% recipient Integrity um being assured 00:01:16.920 --> 00:01:19.469 align:start position:0% recipient Integrity um being assured that<00:01:17.080> the<00:01:17.320> message<00:01:18.320> at<00:01:18.479> the<00:01:18.640> time<00:01:18.799> of<00:01:18.960> reading 00:01:19.469 --> 00:01:19.479 align:start position:0% that the message at the time of reading 00:01:19.479 --> 00:01:21.950 align:start position:0% that the message at the time of reading has<00:01:19.640> not<00:01:19.920> been<00:01:20.159> tampered<00:01:20.759> with<00:01:21.400> um<00:01:21.600> from<00:01:21.840> the 00:01:21.950 --> 00:01:21.960 align:start position:0% has not been tampered with um from the 00:01:21.960 --> 00:01:23.429 align:start position:0% has not been tampered with um from the time<00:01:22.119> of 00:01:23.429 --> 00:01:23.439 align:start position:0% time of 00:01:23.439 --> 00:01:26.670 align:start position:0% time of sending<00:01:24.439> and<00:01:25.240> authenticity<00:01:26.240> that<00:01:26.479> the 00:01:26.670 --> 00:01:26.680 align:start position:0% sending and authenticity that the 00:01:26.680 --> 00:01:29.910 align:start position:0% sending and authenticity that the message<00:01:27.159> was<00:01:27.600> indeed<00:01:28.600> uh<00:01:28.759> sent<00:01:29.280> by<00:01:29.439> the<00:01:29.600> expt 00:01:29.910 --> 00:01:29.920 align:start position:0% message was indeed uh sent by the expt 00:01:29.920 --> 00:01:33.310 align:start position:0% message was indeed uh sent by the expt expected<00:01:30.560> sender<00:01:31.560> and<00:01:31.759> not<00:01:32.000> forged<00:01:32.960> um<00:01:33.159> by 00:01:33.310 --> 00:01:33.320 align:start position:0% expected sender and not forged um by 00:01:33.320 --> 00:01:36.310 align:start position:0% expected sender and not forged um by someone<00:01:33.680> else<00:01:34.560> so<00:01:34.880> a<00:01:35.079> cryptographic<00:01:35.840> system 00:01:36.310 --> 00:01:36.320 align:start position:0% someone else so a cryptographic system 00:01:36.320 --> 00:01:37.710 align:start position:0% someone else so a cryptographic system should<00:01:36.680> provide 00:01:37.710 --> 00:01:37.720 align:start position:0% should provide 00:01:37.720 --> 00:01:42.670 align:start position:0% should provide Assurance<00:01:38.720> of<00:01:39.000> these<00:01:39.200> three 00:01:42.670 --> 00:01:42.680 align:start position:0% 00:01:42.680 --> 00:01:46.190 align:start position:0% properties<00:01:43.680> so<00:01:44.439> this<00:01:44.680> really<00:01:44.960> comes<00:01:45.360> down 00:01:46.190 --> 00:01:46.200 align:start position:0% properties so this really comes down 00:01:46.200 --> 00:01:48.910 align:start position:0% properties so this really comes down to<00:01:47.200> uh<00:01:47.640> you<00:01:47.799> basically<00:01:48.159> have<00:01:48.320> these<00:01:48.520> puzzles 00:01:48.910 --> 00:01:48.920 align:start position:0% to uh you basically have these puzzles 00:01:48.920 --> 00:01:50.469 align:start position:0% to uh you basically have these puzzles that<00:01:49.040> are<00:01:49.200> very<00:01:49.399> easy<00:01:49.640> to<00:01:49.799> solve<00:01:50.119> if<00:01:50.240> you<00:01:50.360> have 00:01:50.469 --> 00:01:50.479 align:start position:0% that are very easy to solve if you have 00:01:50.479 --> 00:01:53.069 align:start position:0% that are very easy to solve if you have the<00:01:50.600> right<00:01:50.840> key<00:01:51.159> and<00:01:51.399> very<00:01:51.640> hard<00:01:51.920> to<00:01:52.119> solve<00:01:52.920> if 00:01:53.069 --> 00:01:53.079 align:start position:0% the right key and very hard to solve if 00:01:53.079 --> 00:01:55.749 align:start position:0% the right key and very hard to solve if you<00:01:53.280> don't<00:01:53.560> have<00:01:53.680> the<00:01:53.960> key<00:01:54.960> uh<00:01:55.479> there's<00:01:55.680> a 00:01:55.749 --> 00:01:55.759 align:start position:0% you don't have the key uh there's a 00:01:55.759 --> 00:01:57.310 align:start position:0% you don't have the key uh there's a little<00:01:55.920> note<00:01:56.200> at<00:01:56.320> the<00:01:56.439> bottom<00:01:56.759> there's<00:01:57.000> a<00:01:57.159> lot 00:01:57.310 --> 00:01:57.320 align:start position:0% little note at the bottom there's a lot 00:01:57.320 --> 00:02:00.190 align:start position:0% little note at the bottom there's a lot of<00:01:57.520> nuance<00:01:58.119> here<00:01:58.360> this<00:01:58.439> is<00:01:58.640> very<00:01:58.880> hand<00:01:59.159> wavy 00:02:00.190 --> 00:02:00.200 align:start position:0% of nuance here this is very hand wavy 00:02:00.200 --> 00:02:03.149 align:start position:0% of nuance here this is very hand wavy you're<00:02:00.360> G<00:02:00.439> to<00:02:00.520> hang<00:02:00.680> out<00:02:00.799> on<00:02:00.920> this<00:02:01.159> side 00:02:03.149 --> 00:02:03.159 align:start position:0% you're G to hang out on this side 00:02:03.159 --> 00:02:07.029 align:start position:0% you're G to hang out on this side okay<00:02:04.159> um<00:02:05.000> but<00:02:05.240> yeah<00:02:05.479> so<00:02:06.119> easy<00:02:06.360> to<00:02:06.479> solve<00:02:06.759> with<00:02:06.880> a 00:02:07.029 --> 00:02:07.039 align:start position:0% okay um but yeah so easy to solve with a 00:02:07.039 --> 00:02:10.229 align:start position:0% okay um but yeah so easy to solve with a key<00:02:07.520> if<00:02:07.600> you<00:02:07.680> don't<00:02:07.880> have<00:02:08.039> the<00:02:08.160> key<00:02:08.640> very<00:02:08.879> very 00:02:10.229 --> 00:02:10.239 align:start position:0% key if you don't have the key very very 00:02:10.239 --> 00:02:12.510 align:start position:0% key if you don't have the key very very hard<00:02:11.239> so<00:02:11.440> the<00:02:11.640> topics<00:02:11.920> we're<00:02:12.080> going<00:02:12.200> to<00:02:12.360> go 00:02:12.510 --> 00:02:12.520 align:start position:0% hard so the topics we're going to go 00:02:12.520 --> 00:02:16.910 align:start position:0% hard so the topics we're going to go over<00:02:13.000> are<00:02:13.440> hashing<00:02:14.000> encryption<00:02:15.319> signing<00:02:16.319> and 00:02:16.910 --> 00:02:16.920 align:start position:0% over are hashing encryption signing and 00:02:16.920 --> 00:02:18.509 align:start position:0% over are hashing encryption signing and what<00:02:17.120> we're<00:02:17.319> now<00:02:17.560> calling<00:02:17.920> programmable 00:02:18.509 --> 00:02:18.519 align:start position:0% what we're now calling programmable 00:02:18.519 --> 00:02:22.150 align:start position:0% what we're now calling programmable cryptography<00:02:19.280> which<00:02:19.440> is<00:02:19.760> ZK<00:02:20.280> MPC<00:02:20.879> and<00:02:21.040> fhe<00:02:22.040> and 00:02:22.150 --> 00:02:22.160 align:start position:0% cryptography which is ZK MPC and fhe and 00:02:22.160 --> 00:02:24.270 align:start position:0% cryptography which is ZK MPC and fhe and you<00:02:22.280> can<00:02:22.560> kind<00:02:22.680> of<00:02:22.959> think<00:02:23.160> of<00:02:23.360> this<00:02:23.519> breakdown 00:02:24.270 --> 00:02:24.280 align:start position:0% you can kind of think of this breakdown 00:02:24.280 --> 00:02:27.470 align:start position:0% you can kind of think of this breakdown as<00:02:24.599> corresponding<00:02:25.519> to<00:02:26.519> the<00:02:26.720> three<00:02:27.000> properties 00:02:27.470 --> 00:02:27.480 align:start position:0% as corresponding to the three properties 00:02:27.480 --> 00:02:30.509 align:start position:0% as corresponding to the three properties that<00:02:27.599> we<00:02:27.800> discussed<00:02:28.360> just<00:02:28.560> now<00:02:29.200> so<00:02:30.040> hashing<00:02:30.400> is 00:02:30.509 --> 00:02:30.519 align:start position:0% that we discussed just now so hashing is 00:02:30.519 --> 00:02:33.550 align:start position:0% that we discussed just now so hashing is a<00:02:30.680> primitive<00:02:31.200> that's<00:02:31.599> often<00:02:32.040> used<00:02:33.040> um<00:02:33.200> to 00:02:33.550 --> 00:02:33.560 align:start position:0% a primitive that's often used um to 00:02:33.560 --> 00:02:36.670 align:start position:0% a primitive that's often used um to provide<00:02:34.560> Integrity<00:02:35.440> assurances<00:02:36.000> of 00:02:36.670 --> 00:02:36.680 align:start position:0% provide Integrity assurances of 00:02:36.680 --> 00:02:39.830 align:start position:0% provide Integrity assurances of Integrity<00:02:37.680> um<00:02:38.159> encryption<00:02:39.159> helps<00:02:39.440> us<00:02:39.599> to 00:02:39.830 --> 00:02:39.840 align:start position:0% Integrity um encryption helps us to 00:02:39.840 --> 00:02:40.990 align:start position:0% Integrity um encryption helps us to preserve 00:02:40.990 --> 00:02:41.000 align:start position:0% preserve 00:02:41.000 --> 00:02:43.589 align:start position:0% preserve confidentiality<00:02:42.000> and<00:02:42.200> signing<00:02:42.640> is<00:02:42.760> a<00:02:42.959> way<00:02:43.360> to 00:02:43.589 --> 00:02:43.599 align:start position:0% confidentiality and signing is a way to 00:02:43.599 --> 00:02:44.710 align:start position:0% confidentiality and signing is a way to provide 00:02:44.710 --> 00:02:44.720 align:start position:0% provide 00:02:44.720 --> 00:02:48.430 align:start position:0% provide authenticity<00:02:45.720> um<00:02:46.159> and<00:02:46.440> these<00:02:46.760> three<00:02:47.480> former 00:02:48.430 --> 00:02:48.440 align:start position:0% authenticity um and these three former 00:02:48.440 --> 00:02:51.309 align:start position:0% authenticity um and these three former Primitives<00:02:49.000> and<00:02:49.239> Protocols<00:02:50.239> are<00:02:50.920> what<00:02:51.080> we 00:02:51.309 --> 00:02:51.319 align:start position:0% Primitives and Protocols are what we 00:02:51.319 --> 00:02:53.949 align:start position:0% Primitives and Protocols are what we consider<00:02:52.000> first<00:02:52.360> generation<00:02:52.959> cryptography 00:02:53.949 --> 00:02:53.959 align:start position:0% consider first generation cryptography 00:02:53.959 --> 00:02:55.869 align:start position:0% consider first generation cryptography in<00:02:54.080> the<00:02:54.280> sense<00:02:54.560> that<00:02:54.720> they're<00:02:55.040> purpose-built 00:02:55.869 --> 00:02:55.879 align:start position:0% in the sense that they're purpose-built 00:02:55.879 --> 00:03:01.350 align:start position:0% in the sense that they're purpose-built for<00:02:56.879> a<00:02:57.159> specific<00:02:58.040> protocol<00:02:59.040> um<00:02:59.480> and<00:03:00.280> um<00:03:00.920> in<00:03:01.239> the 00:03:01.350 --> 00:03:01.360 align:start position:0% for a specific protocol um and um in the 00:03:01.360 --> 00:03:03.550 align:start position:0% for a specific protocol um and um in the rest<00:03:01.599> of<00:03:01.800> Devcon<00:03:02.680> on<00:03:02.879> the<00:03:03.080> applied 00:03:03.550 --> 00:03:03.560 align:start position:0% rest of Devcon on the applied 00:03:03.560 --> 00:03:05.710 align:start position:0% rest of Devcon on the applied cryptography<00:03:04.280> track<00:03:04.959> you're<00:03:05.120> going<00:03:05.280> to<00:03:05.480> hear 00:03:05.710 --> 00:03:05.720 align:start position:0% cryptography track you're going to hear 00:03:05.720 --> 00:03:08.190 align:start position:0% cryptography track you're going to hear a<00:03:05.879> lot<00:03:06.080> more<00:03:06.400> about<00:03:07.159> programmable 00:03:08.190 --> 00:03:08.200 align:start position:0% a lot more about programmable 00:03:08.200 --> 00:03:10.910 align:start position:0% a lot more about programmable cryptography<00:03:09.200> um<00:03:09.440> which<00:03:09.680> usually<00:03:10.120> involve 00:03:10.910 --> 00:03:10.920 align:start position:0% cryptography um which usually involve 00:03:10.920 --> 00:03:13.550 align:start position:0% cryptography um which usually involve more<00:03:11.360> heavyweight<00:03:12.040> and<00:03:12.239> more<00:03:12.640> general 00:03:13.550 --> 00:03:13.560 align:start position:0% more heavyweight and more general 00:03:13.560 --> 00:03:18.949 align:start position:0% more heavyweight and more general purpose 00:03:18.949 --> 00:03:18.959 align:start position:0% 00:03:18.959 --> 00:03:23.390 align:start position:0% protocols<00:03:19.959> all<00:03:20.120> right<00:03:20.480> so<00:03:21.120> hashing<00:03:22.040> is<00:03:22.400> a 00:03:23.390 --> 00:03:23.400 align:start position:0% protocols all right so hashing is a 00:03:23.400 --> 00:03:25.350 align:start position:0% protocols all right so hashing is a one-way<00:03:24.080> function<00:03:24.720> that<00:03:24.840> basically<00:03:25.200> gives 00:03:25.350 --> 00:03:25.360 align:start position:0% one-way function that basically gives 00:03:25.360 --> 00:03:27.630 align:start position:0% one-way function that basically gives you<00:03:25.480> a<00:03:25.599> fingerprint<00:03:26.239> of<00:03:26.400> some 00:03:27.630 --> 00:03:27.640 align:start position:0% you a fingerprint of some 00:03:27.640 --> 00:03:30.910 align:start position:0% you a fingerprint of some data<00:03:28.640> you<00:03:28.799> can<00:03:29.000> think<00:03:29.159> of<00:03:29.400> this<00:03:29.959> as<00:03:30.439> just<00:03:30.640> this 00:03:30.910 --> 00:03:30.920 align:start position:0% data you can think of this as just this 00:03:30.920 --> 00:03:33.309 align:start position:0% data you can think of this as just this magic<00:03:31.360> machine<00:03:31.920> that<00:03:32.040> you<00:03:32.200> put<00:03:32.439> data<00:03:32.760> in<00:03:32.959> one 00:03:33.309 --> 00:03:33.319 align:start position:0% magic machine that you put data in one 00:03:33.319 --> 00:03:35.229 align:start position:0% magic machine that you put data in one side<00:03:33.760> and<00:03:33.879> then<00:03:34.000> that<00:03:34.159> fingerprint<00:03:34.680> comes<00:03:34.879> out 00:03:35.229 --> 00:03:35.239 align:start position:0% side and then that fingerprint comes out 00:03:35.239 --> 00:03:38.910 align:start position:0% side and then that fingerprint comes out the<00:03:35.360> other<00:03:36.080> side<00:03:37.080> so<00:03:37.360> this<00:03:37.439> is<00:03:37.599> an<00:03:37.920> example<00:03:38.640> of 00:03:38.910 --> 00:03:38.920 align:start position:0% the other side so this is an example of 00:03:38.920 --> 00:03:41.589 align:start position:0% the other side so this is an example of what<00:03:39.480> that<00:03:40.040> machine<00:03:40.480> looks<00:03:40.799> like<00:03:41.080> which<00:03:41.439> is 00:03:41.589 --> 00:03:41.599 align:start position:0% what that machine looks like which is 00:03:41.599 --> 00:03:43.670 align:start position:0% what that machine looks like which is pretty<00:03:41.799> gnarly<00:03:42.480> but<00:03:42.799> essentially<00:03:43.239> it<00:03:43.400> comes 00:03:43.670 --> 00:03:43.680 align:start position:0% pretty gnarly but essentially it comes 00:03:43.680 --> 00:03:45.789 align:start position:0% pretty gnarly but essentially it comes down<00:03:43.879> to<00:03:44.400> you<00:03:44.599> put<00:03:44.799> in<00:03:45.120> you<00:03:45.200> know<00:03:45.319> for<00:03:45.480> example 00:03:45.789 --> 00:03:45.799 align:start position:0% down to you put in you know for example 00:03:45.799 --> 00:03:48.470 align:start position:0% down to you put in you know for example a<00:03:46.000> password<00:03:46.760> it<00:03:46.920> gets<00:03:47.159> hashed<00:03:47.920> and<00:03:48.040> then<00:03:48.239> some 00:03:48.470 --> 00:03:48.480 align:start position:0% a password it gets hashed and then some 00:03:48.480 --> 00:03:51.670 align:start position:0% a password it gets hashed and then some fingerprint<00:03:49.040> comes<00:03:49.200> out<00:03:49.599> the<00:03:49.720> other 00:03:51.670 --> 00:03:51.680 align:start position:0% fingerprint comes out the other 00:03:51.680 --> 00:03:56.949 align:start position:0% fingerprint comes out the other side<00:03:52.879> um<00:03:53.879> oh<00:03:54.200> that's<00:03:54.360> so<00:03:54.640> weird<00:03:55.439> yeah<00:03:56.079> um<00:03:56.439> this 00:03:56.949 --> 00:03:56.959 align:start position:0% side um oh that's so weird yeah um this 00:03:56.959 --> 00:03:58.589 align:start position:0% side um oh that's so weird yeah um this a<00:03:57.079> good<00:03:57.280> analogy<00:03:57.720> for<00:03:57.920> this<00:03:58.040> is<00:03:58.239> like<00:03:58.519> uh 00:03:58.589 --> 00:03:58.599 align:start position:0% a good analogy for this is like uh 00:03:58.599 --> 00:04:00.309 align:start position:0% a good analogy for this is like uh blending<00:03:59.000> fruits<00:03:59.280> in<00:03:59.360> a<00:03:59.439> blender<00:04:00.079> right<00:04:00.239> like 00:04:00.309 --> 00:04:00.319 align:start position:0% blending fruits in a blender right like 00:04:00.319 --> 00:04:02.190 align:start position:0% blending fruits in a blender right like you<00:04:00.400> can't<00:04:00.560> get<00:04:00.680> the<00:04:00.760> fruits<00:04:01.120> back<00:04:01.280> out<00:04:02.079> but 00:04:02.190 --> 00:04:02.200 align:start position:0% you can't get the fruits back out but 00:04:02.200 --> 00:04:05.309 align:start position:0% you can't get the fruits back out but you<00:04:02.519> have<00:04:02.959> a<00:04:03.280> consistent<00:04:04.079> like<00:04:04.360> color<00:04:05.159> right 00:04:05.309 --> 00:04:05.319 align:start position:0% you have a consistent like color right 00:04:05.319 --> 00:04:06.710 align:start position:0% you have a consistent like color right if<00:04:05.400> you<00:04:05.560> add<00:04:05.760> just<00:04:05.920> bananas<00:04:06.360> in<00:04:06.519> you're<00:04:06.599> going 00:04:06.710 --> 00:04:06.720 align:start position:0% if you add just bananas in you're going 00:04:06.720 --> 00:04:08.309 align:start position:0% if you add just bananas in you're going to<00:04:06.799> get<00:04:06.920> the<00:04:07.040> same<00:04:07.239> color<00:04:07.760> basically<00:04:08.079> every 00:04:08.309 --> 00:04:08.319 align:start position:0% to get the same color basically every 00:04:08.319 --> 00:04:11.789 align:start position:0% to get the same color basically every time<00:04:09.239> um<00:04:09.360> so<00:04:09.599> unique<00:04:09.959> input<00:04:10.480> unique<00:04:10.799> output 00:04:11.789 --> 00:04:11.799 align:start position:0% time um so unique input unique output 00:04:11.799 --> 00:04:14.350 align:start position:0% time um so unique input unique output these<00:04:11.920> are<00:04:12.120> always<00:04:12.439> fixed<00:04:13.000> length<00:04:14.000> so<00:04:14.200> that's 00:04:14.350 --> 00:04:14.360 align:start position:0% these are always fixed length so that's 00:04:14.360 --> 00:04:16.150 align:start position:0% these are always fixed length so that's to<00:04:14.599> stop<00:04:15.040> certain<00:04:15.319> types<00:04:15.519> of<00:04:15.680> attacks<00:04:16.040> where 00:04:16.150 --> 00:04:16.160 align:start position:0% to stop certain types of attacks where 00:04:16.160 --> 00:04:17.390 align:start position:0% to stop certain types of attacks where you<00:04:16.239> can<00:04:16.320> try<00:04:16.440> to<00:04:16.560> like<00:04:16.680> infer<00:04:17.040> what<00:04:17.160> kind<00:04:17.280> of 00:04:17.390 --> 00:04:17.400 align:start position:0% you can try to like infer what kind of 00:04:17.400 --> 00:04:21.390 align:start position:0% you can try to like infer what kind of data<00:04:17.639> went<00:04:17.840> in<00:04:18.720> and<00:04:18.880> you<00:04:18.959> can<00:04:19.199> see<00:04:19.959> so<00:04:20.359> hi<00:04:20.880> hell 00:04:21.390 --> 00:04:21.400 align:start position:0% data went in and you can see so hi hell 00:04:21.400 --> 00:04:23.749 align:start position:0% data went in and you can see so hi hell help<00:04:21.720> and<00:04:22.080> hello<00:04:23.080> like<00:04:23.240> they<00:04:23.320> have<00:04:23.520> very 00:04:23.749 --> 00:04:23.759 align:start position:0% help and hello like they have very 00:04:23.759 --> 00:04:25.710 align:start position:0% help and hello like they have very similar<00:04:24.120> letters<00:04:24.759> but<00:04:24.960> they're<00:04:25.240> totally 00:04:25.710 --> 00:04:25.720 align:start position:0% similar letters but they're totally 00:04:25.720 --> 00:04:28.710 align:start position:0% similar letters but they're totally different 00:04:28.710 --> 00:04:28.720 align:start position:0% 00:04:28.720 --> 00:04:30.990 align:start position:0% fingerprints<00:04:29.720> you<00:04:29.759> want<00:04:29.880> to<00:04:29.919> talk<00:04:30.080> about<00:04:30.240> this 00:04:30.990 --> 00:04:31.000 align:start position:0% fingerprints you want to talk about this 00:04:31.000 --> 00:04:34.350 align:start position:0% fingerprints you want to talk about this yeah<00:04:31.280> so<00:04:31.600> we've<00:04:31.880> put<00:04:32.039> in<00:04:32.479> sort<00:04:32.720> of<00:04:33.000> Snippets<00:04:33.800> of 00:04:34.350 --> 00:04:34.360 align:start position:0% yeah so we've put in sort of Snippets of 00:04:34.360 --> 00:04:37.310 align:start position:0% yeah so we've put in sort of Snippets of the<00:04:34.840> relevant<00:04:35.360> Devcon<00:04:36.039> talks<00:04:36.720> um<00:04:37.000> throughout 00:04:37.310 --> 00:04:37.320 align:start position:0% the relevant Devcon talks um throughout 00:04:37.320 --> 00:04:40.870 align:start position:0% the relevant Devcon talks um throughout our<00:04:37.440> slides<00:04:37.880> to<00:04:38.039> help<00:04:38.240> you<00:04:38.720> Orient<00:04:39.720> um<00:04:40.240> and 00:04:40.870 --> 00:04:40.880 align:start position:0% our slides to help you Orient um and 00:04:40.880 --> 00:04:43.310 align:start position:0% our slides to help you Orient um and actually<00:04:41.639> um<00:04:42.160> oh<00:04:42.400> this<00:04:42.560> talk<00:04:42.880> already 00:04:43.310 --> 00:04:43.320 align:start position:0% actually um oh this talk already 00:04:43.320 --> 00:04:46.189 align:start position:0% actually um oh this talk already happened<00:04:44.320> but<00:04:44.600> it<00:04:44.720> was<00:04:44.919> an<00:04:45.160> example<00:04:45.800> of<00:04:46.000> how 00:04:46.189 --> 00:04:46.199 align:start position:0% happened but it was an example of how 00:04:46.199 --> 00:04:49.510 align:start position:0% happened but it was an example of how you<00:04:46.320> can<00:04:47.000> build<00:04:48.000> a<00:04:48.360> general<00:04:48.800> purpose<00:04:49.199> proof 00:04:49.510 --> 00:04:49.520 align:start position:0% you can build a general purpose proof 00:04:49.520 --> 00:04:52.510 align:start position:0% you can build a general purpose proof system<00:04:50.360> just<00:04:50.639> using<00:04:51.199> a<00:04:51.400> hash<00:04:51.680> function<00:04:52.160> as<00:04:52.240> a 00:04:52.510 --> 00:04:52.520 align:start position:0% system just using a hash function as a 00:04:52.520 --> 00:04:54.870 align:start position:0% system just using a hash function as a primitive<00:04:53.520> so<00:04:53.759> you<00:04:53.880> can<00:04:54.080> go<00:04:54.240> back<00:04:54.400> and<00:04:54.639> watch 00:04:54.870 --> 00:04:54.880 align:start position:0% primitive so you can go back and watch 00:04:54.880 --> 00:04:57.189 align:start position:0% primitive so you can go back and watch this<00:04:55.080> talk<00:04:55.639> you<00:04:55.759> can<00:04:55.919> do<00:04:56.120> a<00:04:56.240> lot<00:04:56.560> with<00:04:56.919> hash 00:04:57.189 --> 00:04:57.199 align:start position:0% this talk you can do a lot with hash 00:04:57.199 --> 00:04:59.950 align:start position:0% this talk you can do a lot with hash functions 00:04:59.950 --> 00:04:59.960 align:start position:0% functions 00:04:59.960 --> 00:05:03.070 align:start position:0% functions cool<00:05:00.360> so<00:05:00.759> a<00:05:01.320> common<00:05:02.320> reason<00:05:02.639> that<00:05:02.800> hash 00:05:03.070 --> 00:05:03.080 align:start position:0% cool so a common reason that hash 00:05:03.080 --> 00:05:05.469 align:start position:0% cool so a common reason that hash functions<00:05:03.400> are<00:05:03.600> used<00:05:04.039> is<00:05:04.280> passwords<00:05:04.919> but<00:05:05.360> as 00:05:05.469 --> 00:05:05.479 align:start position:0% functions are used is passwords but as 00:05:05.479 --> 00:05:07.510 align:start position:0% functions are used is passwords but as you<00:05:05.600> can<00:05:05.759> see<00:05:06.280> if<00:05:06.440> two<00:05:06.639> users<00:05:07.039> had<00:05:07.199> the<00:05:07.280> same 00:05:07.510 --> 00:05:07.520 align:start position:0% you can see if two users had the same 00:05:07.520 --> 00:05:09.749 align:start position:0% you can see if two users had the same password<00:05:08.400> they<00:05:08.520> have<00:05:08.680> the<00:05:08.840> same<00:05:09.360> password 00:05:09.749 --> 00:05:09.759 align:start position:0% password they have the same password 00:05:09.759 --> 00:05:13.029 align:start position:0% password they have the same password hash<00:05:10.199> right<00:05:10.840> so<00:05:11.840> this<00:05:12.080> allows<00:05:12.520> an<00:05:12.720> attack 00:05:13.029 --> 00:05:13.039 align:start position:0% hash right so this allows an attack 00:05:13.039 --> 00:05:15.110 align:start position:0% hash right so this allows an attack called<00:05:13.600> a<00:05:13.960> like<00:05:14.120> rainbow<00:05:14.520> table<00:05:14.840> attack 00:05:15.110 --> 00:05:15.120 align:start position:0% called a like rainbow table attack 00:05:15.120 --> 00:05:17.670 align:start position:0% called a like rainbow table attack basically<00:05:15.400> you<00:05:15.600> just<00:05:16.039> hash<00:05:16.840> like<00:05:17.000> all<00:05:17.280> common 00:05:17.670 --> 00:05:17.680 align:start position:0% basically you just hash like all common 00:05:17.680 --> 00:05:19.430 align:start position:0% basically you just hash like all common passwords<00:05:18.520> and<00:05:18.639> then<00:05:18.800> now<00:05:18.919> you<00:05:19.039> have<00:05:19.240> this 00:05:19.430 --> 00:05:19.440 align:start position:0% passwords and then now you have this 00:05:19.440 --> 00:05:21.830 align:start position:0% passwords and then now you have this known<00:05:19.880> fingerprint<00:05:20.880> and<00:05:21.000> you<00:05:21.080> can<00:05:21.400> you<00:05:21.520> know 00:05:21.830 --> 00:05:21.840 align:start position:0% known fingerprint and you can you know 00:05:21.840 --> 00:05:23.950 align:start position:0% known fingerprint and you can you know use<00:05:22.039> that<00:05:22.199> to<00:05:22.360> attack<00:05:22.600> people's<00:05:22.960> passwords 00:05:23.950 --> 00:05:23.960 align:start position:0% use that to attack people's passwords 00:05:23.960 --> 00:05:25.830 align:start position:0% use that to attack people's passwords but<00:05:24.199> there's<00:05:24.440> this<00:05:24.639> thing<00:05:24.880> called<00:05:25.240> assault 00:05:25.830 --> 00:05:25.840 align:start position:0% but there's this thing called assault 00:05:25.840 --> 00:05:28.629 align:start position:0% but there's this thing called assault you<00:05:25.960> can<00:05:26.319> add<00:05:27.319> which<00:05:27.600> is<00:05:28.000> essentially<00:05:28.440> just 00:05:28.629 --> 00:05:28.639 align:start position:0% you can add which is essentially just 00:05:28.639 --> 00:05:32.150 align:start position:0% you can add which is essentially just tacking<00:05:29.880> a<00:05:30.120> random<00:05:30.520> string<00:05:31.360> that's<00:05:31.800> specific 00:05:32.150 --> 00:05:32.160 align:start position:0% tacking a random string that's specific 00:05:32.160 --> 00:05:34.150 align:start position:0% tacking a random string that's specific to<00:05:32.360> each<00:05:32.600> user<00:05:33.080> to<00:05:33.240> the<00:05:33.319> end<00:05:33.479> of<00:05:33.600> the<00:05:33.759> password 00:05:34.150 --> 00:05:34.160 align:start position:0% to each user to the end of the password 00:05:34.160 --> 00:05:35.390 align:start position:0% to each user to the end of the password and<00:05:34.240> then<00:05:34.400> hashing<00:05:34.720> it<00:05:34.919> now<00:05:35.039> you<00:05:35.160> have<00:05:35.280> a 00:05:35.390 --> 00:05:35.400 align:start position:0% and then hashing it now you have a 00:05:35.400 --> 00:05:38.110 align:start position:0% and then hashing it now you have a unique<00:05:35.840> fingerprint<00:05:36.840> for<00:05:37.240> every<00:05:37.479> password 00:05:38.110 --> 00:05:38.120 align:start position:0% unique fingerprint for every password 00:05:38.120 --> 00:05:41.950 align:start position:0% unique fingerprint for every password hash<00:05:39.120> so<00:05:39.360> this<00:05:39.440> is<00:05:39.639> just<00:05:39.840> like<00:05:40.000> a<00:05:40.680> example<00:05:41.360> of 00:05:41.950 --> 00:05:41.960 align:start position:0% hash so this is just like a example of 00:05:41.960 --> 00:05:47.270 align:start position:0% hash so this is just like a example of how<00:05:42.960> um<00:05:43.960> hashing<00:05:44.319> is<00:05:44.520> used<00:05:45.479> very<00:05:45.800> commonly<00:05:46.680> so 00:05:47.270 --> 00:05:47.280 align:start position:0% how um hashing is used very commonly so 00:05:47.280 --> 00:05:49.670 align:start position:0% how um hashing is used very commonly so pretty<00:05:47.479> much<00:05:47.759> every<00:05:48.680> popular<00:05:49.080> website<00:05:49.479> that 00:05:49.670 --> 00:05:49.680 align:start position:0% pretty much every popular website that 00:05:49.680 --> 00:05:54.150 align:start position:0% pretty much every popular website that has<00:05:49.880> logins<00:05:51.039> uses<00:05:52.039> uh<00:05:52.199> bcrypt<00:05:52.919> with<00:05:53.720> per<00:05:53.919> user 00:05:54.150 --> 00:05:54.160 align:start position:0% has logins uses uh bcrypt with per user 00:05:54.160 --> 00:05:56.390 align:start position:0% has logins uses uh bcrypt with per user salts<00:05:54.680> like<00:05:54.840> this<00:05:54.960> is<00:05:55.600> a<00:05:55.759> pretty<00:05:56.160> pretty 00:05:56.390 --> 00:05:56.400 align:start position:0% salts like this is a pretty pretty 00:05:56.400 --> 00:05:57.749 align:start position:0% salts like this is a pretty pretty common 00:05:57.749 --> 00:05:57.759 align:start position:0% common 00:05:57.759 --> 00:06:00.950 align:start position:0% common technique<00:05:58.759> all<00:05:58.880> right<00:05:59.039> this<00:05:59.160> is<00:05:59.240> all<00:05:59.440> you 00:06:00.950 --> 00:06:00.960 align:start position:0% technique all right this is all you 00:06:00.960 --> 00:06:03.390 align:start position:0% technique all right this is all you yeah<00:06:01.280> and<00:06:01.759> I<00:06:01.840> think<00:06:02.080> hash<00:06:02.440> functions<00:06:02.919> are<00:06:03.120> a 00:06:03.390 --> 00:06:03.400 align:start position:0% yeah and I think hash functions are a 00:06:03.400 --> 00:06:07.230 align:start position:0% yeah and I think hash functions are a great<00:06:04.440> introduction<00:06:05.440> um<00:06:05.680> as<00:06:05.800> a<00:06:06.000> cryptographic 00:06:07.230 --> 00:06:07.240 align:start position:0% great introduction um as a cryptographic 00:06:07.240 --> 00:06:11.270 align:start position:0% great introduction um as a cryptographic primitive<00:06:08.240> because<00:06:09.120> they<00:06:09.280> seem<00:06:10.160> very<00:06:10.479> simple 00:06:11.270 --> 00:06:11.280 align:start position:0% primitive because they seem very simple 00:06:11.280 --> 00:06:14.350 align:start position:0% primitive because they seem very simple the<00:06:11.440> API<00:06:12.080> is<00:06:12.280> really<00:06:12.880> straightforward<00:06:13.880> but<00:06:14.160> a 00:06:14.350 --> 00:06:14.360 align:start position:0% the API is really straightforward but a 00:06:14.360 --> 00:06:16.870 align:start position:0% the API is really straightforward but a cryptographic<00:06:15.199> hash<00:06:15.599> function<00:06:16.360> actually<00:06:16.759> has 00:06:16.870 --> 00:06:16.880 align:start position:0% cryptographic hash function actually has 00:06:16.880 --> 00:06:18.790 align:start position:0% cryptographic hash function actually has to<00:06:17.080> fulfill<00:06:17.720> a<00:06:17.840> few 00:06:18.790 --> 00:06:18.800 align:start position:0% to fulfill a few 00:06:18.800 --> 00:06:22.670 align:start position:0% to fulfill a few properties<00:06:19.800> um<00:06:20.400> so<00:06:21.400> we<00:06:21.520> won't<00:06:21.880> go<00:06:22.160> over<00:06:22.479> them 00:06:22.670 --> 00:06:22.680 align:start position:0% properties um so we won't go over them 00:06:22.680 --> 00:06:25.710 align:start position:0% properties um so we won't go over them in<00:06:23.000> detail<00:06:24.000> but 00:06:25.710 --> 00:06:25.720 align:start position:0% in detail but 00:06:25.720 --> 00:06:29.110 align:start position:0% in detail but um<00:06:26.720> I<00:06:26.800> think<00:06:27.039> I<00:06:27.280> put<00:06:27.599> this<00:06:27.759> in<00:06:28.000> to<00:06:28.319> highlight 00:06:29.110 --> 00:06:29.120 align:start position:0% um I think I put this in to highlight 00:06:29.120 --> 00:06:31.950 align:start position:0% um I think I put this in to highlight also<00:06:29.759> that<00:06:30.080> there<00:06:30.319> exist<00:06:30.919> non-<00:06:31.280> cryptographic 00:06:31.950 --> 00:06:31.960 align:start position:0% also that there exist non- cryptographic 00:06:31.960 --> 00:06:35.390 align:start position:0% also that there exist non- cryptographic hash<00:06:32.199> functions<00:06:33.000> so<00:06:34.000> um<00:06:34.240> that<00:06:34.400> are<00:06:34.840> way<00:06:35.039> more 00:06:35.390 --> 00:06:35.400 align:start position:0% hash functions so um that are way more 00:06:35.400 --> 00:06:37.350 align:start position:0% hash functions so um that are way more efficient<00:06:36.240> than<00:06:36.440> cryptographic<00:06:37.120> hash 00:06:37.350 --> 00:06:37.360 align:start position:0% efficient than cryptographic hash 00:06:37.360 --> 00:06:40.189 align:start position:0% efficient than cryptographic hash functions<00:06:38.120> and<00:06:38.319> that<00:06:38.440> are<00:06:38.639> suitable 00:06:40.189 --> 00:06:40.199 align:start position:0% functions and that are suitable 00:06:40.199 --> 00:06:44.029 align:start position:0% functions and that are suitable for<00:06:41.199> um<00:06:41.720> use<00:06:42.080> cases<00:06:42.400> such<00:06:42.560> as<00:06:42.800> hash<00:06:43.080> tables 00:06:44.029 --> 00:06:44.039 align:start position:0% for um use cases such as hash tables 00:06:44.039 --> 00:06:47.830 align:start position:0% for um use cases such as hash tables which<00:06:44.199> are<00:06:44.400> not<00:06:45.039> um<00:06:45.960> sort<00:06:46.199> of<00:06:46.479> high<00:06:46.840> security 00:06:47.830 --> 00:06:47.840 align:start position:0% which are not um sort of high security 00:06:47.840 --> 00:06:50.909 align:start position:0% which are not um sort of high security so<00:06:48.080> in<00:06:48.280> hash<00:06:48.599> tables<00:06:49.400> for<00:06:49.639> instance<00:06:50.440> we<00:06:50.599> don't 00:06:50.909 --> 00:06:50.919 align:start position:0% so in hash tables for instance we don't 00:06:50.919 --> 00:06:53.270 align:start position:0% so in hash tables for instance we don't need<00:06:51.800> um<00:06:52.000> the<00:06:52.199> Collision<00:06:52.720> resistance 00:06:53.270 --> 00:06:53.280 align:start position:0% need um the Collision resistance 00:06:53.280 --> 00:06:56.869 align:start position:0% need um the Collision resistance property<00:06:53.840> in<00:06:54.000> fact<00:06:54.199> in<00:06:54.400> hash<00:06:54.800> tables<00:06:55.800> we<00:06:56.039> have 00:06:56.869 --> 00:06:56.879 align:start position:0% property in fact in hash tables we have 00:06:56.879 --> 00:07:00.749 align:start position:0% property in fact in hash tables we have many<00:06:57.879> um<00:06:58.160> techniques<00:06:58.599> to<00:06:59.000> handle<00:06:59.599> collisions 00:07:00.749 --> 00:07:00.759 align:start position:0% many um techniques to handle collisions 00:07:00.759 --> 00:07:07.110 align:start position:0% many um techniques to handle collisions buckets<00:07:01.759> um<00:07:02.840> so<00:07:03.840> and<00:07:04.479> at<00:07:04.639> the<00:07:04.800> same<00:07:05.160> time<00:07:06.120> um 00:07:07.110 --> 00:07:07.120 align:start position:0% buckets um so and at the same time um 00:07:07.120 --> 00:07:08.950 align:start position:0% buckets um so and at the same time um cryptographic<00:07:07.960> security<00:07:08.440> of<00:07:08.560> a<00:07:08.680> hash 00:07:08.950 --> 00:07:08.960 align:start position:0% cryptographic security of a hash 00:07:08.960 --> 00:07:12.629 align:start position:0% cryptographic security of a hash function<00:07:09.479> is<00:07:10.319> I<00:07:10.400> think<00:07:10.599> literally<00:07:11.199> defined<00:07:11.759> as 00:07:12.629 --> 00:07:12.639 align:start position:0% function is I think literally defined as 00:07:12.639 --> 00:07:15.749 align:start position:0% function is I think literally defined as um<00:07:13.479> for<00:07:13.960> how<00:07:14.199> long<00:07:14.560> has<00:07:14.720> this<00:07:14.919> hash<00:07:15.199> function 00:07:15.749 --> 00:07:15.759 align:start position:0% um for how long has this hash function 00:07:15.759 --> 00:07:20.350 align:start position:0% um for how long has this hash function remained<00:07:16.039> unbroken<00:07:16.680> for<00:07:17.680> um<00:07:18.479> and<00:07:19.080> the<00:07:20.039> that's 00:07:20.350 --> 00:07:20.360 align:start position:0% remained unbroken for um and the that's 00:07:20.360 --> 00:07:22.670 align:start position:0% remained unbroken for um and the that's that's<00:07:20.520> where<00:07:20.720> the<00:07:20.919> art<00:07:21.639> of<00:07:21.840> cryptography 00:07:22.670 --> 00:07:22.680 align:start position:0% that's where the art of cryptography 00:07:22.680 --> 00:07:25.909 align:start position:0% that's where the art of cryptography comes<00:07:22.960> in<00:07:23.800> um<00:07:24.000> Crypt<00:07:24.440> analysis<00:07:25.120> security 00:07:25.909 --> 00:07:25.919 align:start position:0% comes in um Crypt analysis security 00:07:25.919 --> 00:07:29.629 align:start position:0% comes in um Crypt analysis security analysis<00:07:26.919> um<00:07:27.479> and<00:07:28.160> reasoning<00:07:28.800> about<00:07:29.280> the 00:07:29.629 --> 00:07:29.639 align:start position:0% analysis um and reasoning about the 00:07:29.639 --> 00:07:31.830 align:start position:0% analysis um and reasoning about the cryptographic<00:07:30.400> security<00:07:31.199> of<00:07:31.360> a<00:07:31.479> certain 00:07:31.830 --> 00:07:31.840 align:start position:0% cryptographic security of a certain 00:07:31.840 --> 00:07:34.670 align:start position:0% cryptographic security of a certain primitive<00:07:32.639> so<00:07:33.400> yeah<00:07:33.639> hash<00:07:33.919> functions<00:07:34.520> we 00:07:34.670 --> 00:07:34.680 align:start position:0% primitive so yeah hash functions we 00:07:34.680 --> 00:07:37.309 align:start position:0% primitive so yeah hash functions we chose<00:07:35.080> to<00:07:35.720> as<00:07:35.840> an<00:07:36.039> introductory 00:07:37.309 --> 00:07:37.319 align:start position:0% chose to as an introductory 00:07:37.319 --> 00:07:41.230 align:start position:0% chose to as an introductory primitive<00:07:38.319> um<00:07:38.639> just<00:07:38.759> to<00:07:38.960> give<00:07:39.080> you<00:07:39.240> a<00:07:39.400> taste<00:07:40.240> of 00:07:41.230 --> 00:07:41.240 align:start position:0% primitive um just to give you a taste of 00:07:41.240 --> 00:07:43.830 align:start position:0% primitive um just to give you a taste of what<00:07:41.440> they<00:07:41.560> can<00:07:41.720> be<00:07:41.879> used<00:07:42.160> for<00:07:42.960> um<00:07:43.479> how<00:07:43.639> we 00:07:43.830 --> 00:07:43.840 align:start position:0% what they can be used for um how we 00:07:43.840 --> 00:07:46.710 align:start position:0% what they can be used for um how we reason<00:07:44.280> about<00:07:44.560> them 00:07:46.710 --> 00:07:46.720 align:start position:0% reason about them 00:07:46.720 --> 00:07:50.629 align:start position:0% reason about them um<00:07:47.720> yeah<00:07:48.280> another<00:07:49.280> very<00:07:49.560> common<00:07:49.840> use<00:07:50.199> case<00:07:50.479> is 00:07:50.629 --> 00:07:50.639 align:start position:0% um yeah another very common use case is 00:07:50.639 --> 00:07:52.710 align:start position:0% um yeah another very common use case is in<00:07:50.879> Merkel<00:07:51.360> trees<00:07:51.720> I'm<00:07:51.800> sure<00:07:52.039> we're<00:07:52.280> all 00:07:52.710 --> 00:07:52.720 align:start position:0% in Merkel trees I'm sure we're all 00:07:52.720 --> 00:07:55.790 align:start position:0% in Merkel trees I'm sure we're all familiar<00:07:53.720> um<00:07:53.840> it's<00:07:54.000> used<00:07:54.280> in<00:07:54.560> git 00:07:55.790 --> 00:07:55.800 align:start position:0% familiar um it's used in git 00:07:55.800 --> 00:08:00.430 align:start position:0% familiar um it's used in git to<00:07:56.800> produce<00:07:57.240> unique<00:07:57.680> digests<00:07:58.520> of<00:07:58.720> a 00:08:00.430 --> 00:08:00.440 align:start position:0% to produce unique digests of a 00:08:00.440 --> 00:08:05.110 align:start position:0% to produce unique digests of a repository<00:08:01.440> um<00:08:01.800> it's<00:08:02.039> used<00:08:02.800> in<00:08:04.120> blockchains 00:08:05.110 --> 00:08:05.120 align:start position:0% repository um it's used in blockchains 00:08:05.120 --> 00:08:06.270 align:start position:0% repository um it's used in blockchains um 00:08:06.270 --> 00:08:06.280 align:start position:0% um 00:08:06.280 --> 00:08:09.710 align:start position:0% um to<00:08:07.280> produce<00:08:07.840> L<00:08:08.120> cryptographically<00:08:09.000> linked 00:08:09.710 --> 00:08:09.720 align:start position:0% to produce L cryptographically linked 00:08:09.720 --> 00:08:12.790 align:start position:0% to produce L cryptographically linked headers<00:08:10.280> from<00:08:10.520> block<00:08:10.800> to<00:08:11.120> block<00:08:12.120> um<00:08:12.599> for 00:08:12.790 --> 00:08:12.800 align:start position:0% headers from block to block um for 00:08:12.800 --> 00:08:14.830 align:start position:0% headers from block to block um for instance<00:08:13.120> in<00:08:13.240> the<00:08:13.319> ethereum 00:08:14.830 --> 00:08:14.840 align:start position:0% instance in the ethereum 00:08:14.840 --> 00:08:16.790 align:start position:0% instance in the ethereum state 00:08:16.790 --> 00:08:16.800 align:start position:0% state 00:08:16.800 --> 00:08:19.510 align:start position:0% state yeah<00:08:17.800> all<00:08:17.960> right<00:08:18.319> so<00:08:18.800> now<00:08:18.960> we're<00:08:19.080> going<00:08:19.159> to<00:08:19.319> go 00:08:19.510 --> 00:08:19.520 align:start position:0% yeah all right so now we're going to go 00:08:19.520 --> 00:08:22.149 align:start position:0% yeah all right so now we're going to go over<00:08:20.400> encryption<00:08:20.960> real<00:08:21.159> quick<00:08:21.639> um<00:08:21.759> so<00:08:21.919> one<00:08:22.039> of 00:08:22.149 --> 00:08:22.159 align:start position:0% over encryption real quick um so one of 00:08:22.159 --> 00:08:24.189 align:start position:0% over encryption real quick um so one of the<00:08:22.319> original<00:08:22.919> like<00:08:23.120> encryption<00:08:23.720> algorithms 00:08:24.189 --> 00:08:24.199 align:start position:0% the original like encryption algorithms 00:08:24.199 --> 00:08:25.510 align:start position:0% the original like encryption algorithms that<00:08:24.319> were<00:08:24.440> used<00:08:24.720> it's<00:08:24.879> called<00:08:25.000> a<00:08:25.120> Caesar 00:08:25.510 --> 00:08:25.520 align:start position:0% that were used it's called a Caesar 00:08:25.520 --> 00:08:28.270 align:start position:0% that were used it's called a Caesar Cipher<00:08:26.400> and<00:08:26.560> it's<00:08:26.960> terrible<00:08:27.960> um<00:08:28.120> but 00:08:28.270 --> 00:08:28.280 align:start position:0% Cipher and it's terrible um but 00:08:28.280 --> 00:08:30.230 align:start position:0% Cipher and it's terrible um but basically<00:08:28.800> you<00:08:29.000> take<00:08:29.280> that<00:08:29.560> alphabet<00:08:30.000> and<00:08:30.120> you 00:08:30.230 --> 00:08:30.240 align:start position:0% basically you take that alphabet and you 00:08:30.240 --> 00:08:34.029 align:start position:0% basically you take that alphabet and you shift<00:08:30.599> it<00:08:31.120> by<00:08:31.720> you<00:08:31.879> know<00:08:32.080> some<00:08:32.560> number<00:08:33.560> and 00:08:34.029 --> 00:08:34.039 align:start position:0% shift it by you know some number and 00:08:34.039 --> 00:08:35.269 align:start position:0% shift it by you know some number and let's<00:08:34.200> say<00:08:34.320> if<00:08:34.399> we<00:08:34.479> want<00:08:34.599> to<00:08:34.719> write<00:08:34.919> hello 00:08:35.269 --> 00:08:35.279 align:start position:0% let's say if we want to write hello 00:08:35.279 --> 00:08:37.070 align:start position:0% let's say if we want to write hello you're<00:08:35.399> going<00:08:35.519> to<00:08:35.599> identify<00:08:36.159> those<00:08:36.560> letters 00:08:37.070 --> 00:08:37.080 align:start position:0% you're going to identify those letters 00:08:37.080 --> 00:08:38.509 align:start position:0% you're going to identify those letters and<00:08:37.200> then<00:08:37.360> basically<00:08:37.760> just 00:08:38.509 --> 00:08:38.519 align:start position:0% and then basically just 00:08:38.519 --> 00:08:43.750 align:start position:0% and then basically just translate<00:08:39.519> to<00:08:40.440> the<00:08:40.760> new<00:08:41.039> code<00:08:41.800> right<00:08:42.680> um<00:08:43.640> and 00:08:43.750 --> 00:08:43.760 align:start position:0% translate to the new code right um and 00:08:43.760 --> 00:08:44.990 align:start position:0% translate to the new code right um and if<00:08:43.839> you<00:08:43.919> want<00:08:44.039> to<00:08:44.159> reverse<00:08:44.480> it<00:08:44.600> you<00:08:44.720> basically 00:08:44.990 --> 00:08:45.000 align:start position:0% if you want to reverse it you basically 00:08:45.000 --> 00:08:46.430 align:start position:0% if you want to reverse it you basically just<00:08:45.080> shift<00:08:45.320> it<00:08:45.480> the<00:08:45.600> other<00:08:45.800> way<00:08:46.120> and<00:08:46.240> then<00:08:46.320> you 00:08:46.430 --> 00:08:46.440 align:start position:0% just shift it the other way and then you 00:08:46.440 --> 00:08:48.750 align:start position:0% just shift it the other way and then you get<00:08:46.600> the<00:08:46.760> original<00:08:47.160> message<00:08:47.519> back<00:08:47.680> out<00:08:48.560> uh 00:08:48.750 --> 00:08:48.760 align:start position:0% get the original message back out uh 00:08:48.760 --> 00:08:50.230 align:start position:0% get the original message back out uh this<00:08:48.920> is 00:08:50.230 --> 00:08:50.240 align:start position:0% this is 00:08:50.240 --> 00:08:53.070 align:start position:0% this is 4.6<00:08:51.240> bits<00:08:51.600> of<00:08:51.760> security<00:08:52.160> so<00:08:52.360> basically<00:08:52.640> 26 00:08:53.070 --> 00:08:53.080 align:start position:0% 4.6 bits of security so basically 26 00:08:53.080 --> 00:08:57.910 align:start position:0% 4.6 bits of security so basically 26 letters<00:08:53.920> minus<00:08:54.480> one<00:08:55.480> and<00:08:56.120> it's<00:08:56.600> terrible<00:08:57.519> um 00:08:57.910 --> 00:08:57.920 align:start position:0% letters minus one and it's terrible um 00:08:57.920 --> 00:09:00.750 align:start position:0% letters minus one and it's terrible um we<00:08:58.040> have<00:08:58.360> much<00:08:58.640> much<00:08:58.839> better<00:08:59.720> techniques 00:09:00.750 --> 00:09:00.760 align:start position:0% we have much much better techniques 00:09:00.760 --> 00:09:03.949 align:start position:0% we have much much better techniques nowadays<00:09:01.760> um<00:09:02.120> so<00:09:02.399> symmetric<00:09:02.839> key<00:09:03.040> encryption 00:09:03.949 --> 00:09:03.959 align:start position:0% nowadays um so symmetric key encryption 00:09:03.959 --> 00:09:04.990 align:start position:0% nowadays um so symmetric key encryption which<00:09:04.040> is<00:09:04.160> basically<00:09:04.480> what<00:09:04.720> you<00:09:04.800> know<00:09:04.920> a 00:09:04.990 --> 00:09:05.000 align:start position:0% which is basically what you know a 00:09:05.000 --> 00:09:07.310 align:start position:0% which is basically what you know a Caesar<00:09:05.320> Cipher<00:09:05.640> is<00:09:05.760> a<00:09:06.120> type<00:09:06.279> of<00:09:06.399> symmetric<00:09:06.800> key 00:09:07.310 --> 00:09:07.320 align:start position:0% Caesar Cipher is a type of symmetric key 00:09:07.320 --> 00:09:10.310 align:start position:0% Caesar Cipher is a type of symmetric key encryption<00:09:08.320> um<00:09:09.040> but<00:09:09.200> it's<00:09:09.399> when<00:09:09.880> all<00:09:10.120> the 00:09:10.310 --> 00:09:10.320 align:start position:0% encryption um but it's when all the 00:09:10.320 --> 00:09:12.069 align:start position:0% encryption um but it's when all the parties<00:09:10.800> that<00:09:10.920> are<00:09:11.079> participating<00:09:11.800> have<00:09:11.959> the 00:09:12.069 --> 00:09:12.079 align:start position:0% parties that are participating have the 00:09:12.079 --> 00:09:15.269 align:start position:0% parties that are participating have the same<00:09:12.440> key<00:09:13.079> right<00:09:13.920> so<00:09:14.120> use<00:09:14.320> the<00:09:14.480> same<00:09:14.720> key<00:09:14.959> to 00:09:15.269 --> 00:09:15.279 align:start position:0% same key right so use the same key to 00:09:15.279 --> 00:09:17.750 align:start position:0% same key right so use the same key to encrypt<00:09:15.760> and<00:09:16.279> decrypt<00:09:17.279> uh<00:09:17.399> there's<00:09:17.600> no 00:09:17.750 --> 00:09:17.760 align:start position:0% encrypt and decrypt uh there's no 00:09:17.760 --> 00:09:19.110 align:start position:0% encrypt and decrypt uh there's no authentication<00:09:18.399> so<00:09:18.519> you<00:09:18.600> don't<00:09:18.760> know<00:09:18.920> who 00:09:19.110 --> 00:09:19.120 align:start position:0% authentication so you don't know who 00:09:19.120 --> 00:09:21.910 align:start position:0% authentication so you don't know who encrypted<00:09:19.519> the<00:09:19.880> message<00:09:20.880> um<00:09:21.279> and<00:09:21.560> basically 00:09:21.910 --> 00:09:21.920 align:start position:0% encrypted the message um and basically 00:09:21.920 --> 00:09:23.790 align:start position:0% encrypted the message um and basically anyone<00:09:22.160> with<00:09:22.279> a<00:09:22.399> key<00:09:22.600> can<00:09:22.720> decrypt<00:09:23.160> it<00:09:23.519> but<00:09:23.680> it 00:09:23.790 --> 00:09:23.800 align:start position:0% anyone with a key can decrypt it but it 00:09:23.800 --> 00:09:27.030 align:start position:0% anyone with a key can decrypt it but it is<00:09:24.279> fast<00:09:24.720> and<00:09:24.800> it's<00:09:25.000> used<00:09:25.440> very<00:09:25.839> commonly<00:09:26.839> with 00:09:27.030 --> 00:09:27.040 align:start position:0% is fast and it's used very commonly with 00:09:27.040 --> 00:09:29.949 align:start position:0% is fast and it's used very commonly with like<00:09:27.200> data<00:09:27.480> at<00:09:27.720> rest<00:09:28.240> or<00:09:28.519> TLS<00:09:29.519> like<00:09:29.600> that<00:09:29.720> St 00:09:29.949 --> 00:09:29.959 align:start position:0% like data at rest or TLS like that St 00:09:29.959 --> 00:09:32.190 align:start position:0% like data at rest or TLS like that St where<00:09:30.120> you<00:09:30.200> need<00:09:30.399> like<00:09:30.560> high<00:09:30.959> bandwidth<00:09:31.959> uh 00:09:32.190 --> 00:09:32.200 align:start position:0% where you need like high bandwidth uh 00:09:32.200 --> 00:09:34.550 align:start position:0% where you need like high bandwidth uh common<00:09:32.519> examples<00:09:33.160> AES<00:09:33.640> for<00:09:33.800> like<00:09:33.920> an<00:09:34.079> actual 00:09:34.550 --> 00:09:34.560 align:start position:0% common examples AES for like an actual 00:09:34.560 --> 00:09:39.790 align:start position:0% common examples AES for like an actual algorithm<00:09:35.040> that's 00:09:39.790 --> 00:09:39.800 align:start position:0% 00:09:39.800 --> 00:09:43.990 align:start position:0% used<00:09:40.800> all<00:09:40.920> right<00:09:41.320> so<00:09:42.200> yeah<00:09:42.959> secret<00:09:43.399> key<00:09:43.720> plain 00:09:43.990 --> 00:09:44.000 align:start position:0% used all right so yeah secret key plain 00:09:44.000 --> 00:09:47.230 align:start position:0% used all right so yeah secret key plain text<00:09:44.399> go<00:09:44.560> in<00:09:45.480> you<00:09:45.560> get<00:09:45.720> some<00:09:45.880> Cipher<00:09:46.240> text<00:09:46.560> out 00:09:47.230 --> 00:09:47.240 align:start position:0% text go in you get some Cipher text out 00:09:47.240 --> 00:09:49.150 align:start position:0% text go in you get some Cipher text out to<00:09:47.480> decrypt<00:09:48.040> you<00:09:48.160> put<00:09:48.320> in<00:09:48.440> a<00:09:48.560> secret<00:09:48.880> key<00:09:49.079> in 00:09:49.150 --> 00:09:49.160 align:start position:0% to decrypt you put in a secret key in 00:09:49.160 --> 00:09:50.790 align:start position:0% to decrypt you put in a secret key in your<00:09:49.279> Cipher<00:09:49.640> text<00:09:50.079> you<00:09:50.160> have<00:09:50.279> a<00:09:50.360> decrypt 00:09:50.790 --> 00:09:50.800 align:start position:0% your Cipher text you have a decrypt 00:09:50.800 --> 00:09:52.990 align:start position:0% your Cipher text you have a decrypt function<00:09:51.720> and<00:09:51.880> then<00:09:52.079> you<00:09:52.320> get<00:09:52.480> your<00:09:52.720> plain 00:09:52.990 --> 00:09:53.000 align:start position:0% function and then you get your plain 00:09:53.000 --> 00:09:54.269 align:start position:0% function and then you get your plain text<00:09:53.240> back 00:09:54.269 --> 00:09:54.279 align:start position:0% text back 00:09:54.279 --> 00:09:55.990 align:start position:0% text back out<00:09:55.279> all 00:09:55.990 --> 00:09:56.000 align:start position:0% out all 00:09:56.000 --> 00:10:01.389 align:start position:0% out all right<00:09:57.160> um<00:09:58.160> yeah<00:09:58.440> and<00:09:58.920> um 00:10:01.389 --> 00:10:01.399 align:start position:0% 00:10:01.399 --> 00:10:04.069 align:start position:0% yeah<00:10:01.600> so<00:10:01.839> symmetric<00:10:02.399> encryption<00:10:03.040> is<00:10:03.240> suitable 00:10:04.069 --> 00:10:04.079 align:start position:0% yeah so symmetric encryption is suitable 00:10:04.079 --> 00:10:06.350 align:start position:0% yeah so symmetric encryption is suitable for<00:10:04.360> when<00:10:04.839> both<00:10:05.160> parties<00:10:05.640> are<00:10:05.839> able<00:10:06.120> to 00:10:06.350 --> 00:10:06.360 align:start position:0% for when both parties are able to 00:10:06.360 --> 00:10:08.990 align:start position:0% for when both parties are able to establish<00:10:06.959> a<00:10:07.120> common<00:10:07.440> shared<00:10:07.839> secret<00:10:08.720> um<00:10:08.880> and 00:10:08.990 --> 00:10:09.000 align:start position:0% establish a common shared secret um and 00:10:09.000 --> 00:10:12.230 align:start position:0% establish a common shared secret um and to<00:10:09.160> use<00:10:09.360> it<00:10:10.079> both<00:10:10.399> to<00:10:10.560> encrypt<00:10:11.040> and<00:10:11.120> to<00:10:11.279> decrypt 00:10:12.230 --> 00:10:12.240 align:start position:0% to use it both to encrypt and to decrypt 00:10:12.240 --> 00:10:14.509 align:start position:0% to use it both to encrypt and to decrypt but<00:10:12.480> in<00:10:12.680> many<00:10:12.959> use<00:10:13.360> cases<00:10:13.920> we<00:10:14.079> want<00:10:14.360> the 00:10:14.509 --> 00:10:14.519 align:start position:0% but in many use cases we want the 00:10:14.519 --> 00:10:17.110 align:start position:0% but in many use cases we want the ability<00:10:15.040> to<00:10:15.480> say<00:10:16.040> asynchronously<00:10:16.959> and 00:10:17.110 --> 00:10:17.120 align:start position:0% ability to say asynchronously and 00:10:17.120 --> 00:10:19.870 align:start position:0% ability to say asynchronously and non-interactively<00:10:17.920> encrypt<00:10:18.839> a<00:10:19.040> message<00:10:19.480> to<00:10:19.640> a 00:10:19.870 --> 00:10:19.880 align:start position:0% non-interactively encrypt a message to a 00:10:19.880 --> 00:10:23.150 align:start position:0% non-interactively encrypt a message to a recipient<00:10:20.880> and<00:10:21.000> in<00:10:21.200> this<00:10:21.440> case<00:10:22.000> um<00:10:22.519> asymmetric 00:10:23.150 --> 00:10:23.160 align:start position:0% recipient and in this case um asymmetric 00:10:23.160 --> 00:10:25.509 align:start position:0% recipient and in this case um asymmetric encryption<00:10:23.720> comes<00:10:23.920> in<00:10:24.120> really<00:10:24.399> handy<00:10:25.160> because 00:10:25.509 --> 00:10:25.519 align:start position:0% encryption comes in really handy because 00:10:25.519 --> 00:10:27.990 align:start position:0% encryption comes in really handy because all<00:10:25.680> you<00:10:25.839> need<00:10:26.079> to<00:10:26.279> know<00:10:26.959> is<00:10:27.240> the<00:10:27.480> public<00:10:27.760> key 00:10:27.990 --> 00:10:28.000 align:start position:0% all you need to know is the public key 00:10:28.000 --> 00:10:30.750 align:start position:0% all you need to know is the public key of<00:10:28.120> your<00:10:28.360> recipient<00:10:29.399> and<00:10:29.600> they<00:10:29.720> can<00:10:30.120> decrypt 00:10:30.750 --> 00:10:30.760 align:start position:0% of your recipient and they can decrypt 00:10:30.760 --> 00:10:32.550 align:start position:0% of your recipient and they can decrypt the<00:10:30.920> message<00:10:31.360> at<00:10:31.600> any<00:10:31.839> time<00:10:32.079> they<00:10:32.200> want 00:10:32.550 --> 00:10:32.560 align:start position:0% the message at any time they want 00:10:32.560 --> 00:10:36.350 align:start position:0% the message at any time they want without<00:10:33.279> um<00:10:34.279> without<00:10:34.519> your<00:10:34.720> help<00:10:35.440> so<00:10:35.959> we<00:10:36.160> put 00:10:36.350 --> 00:10:36.360 align:start position:0% without um without your help so we put 00:10:36.360 --> 00:10:39.230 align:start position:0% without um without your help so we put the<00:10:36.519> API<00:10:37.040> here<00:10:37.480> I<00:10:37.600> think<00:10:38.120> what's<00:10:38.600> important<00:10:39.040> to 00:10:39.230 --> 00:10:39.240 align:start position:0% the API here I think what's important to 00:10:39.240 --> 00:10:42.230 align:start position:0% the API here I think what's important to note<00:10:39.800> that's<00:10:40.279> different<00:10:41.279> um<00:10:41.480> from<00:10:41.720> symmetric 00:10:42.230 --> 00:10:42.240 align:start position:0% note that's different um from symmetric 00:10:42.240 --> 00:10:45.629 align:start position:0% note that's different um from symmetric encryption<00:10:43.240> is<00:10:43.480> that<00:10:43.920> the<00:10:44.880> encryption<00:10:45.440> and 00:10:45.629 --> 00:10:45.639 align:start position:0% encryption is that the encryption and 00:10:45.639 --> 00:10:49.550 align:start position:0% encryption is that the encryption and decryption<00:10:46.200> keys<00:10:46.639> are<00:10:47.040> different<00:10:47.959> and<00:10:48.160> the<00:10:48.480> in 00:10:49.550 --> 00:10:49.560 align:start position:0% decryption keys are different and the in 00:10:49.560 --> 00:10:53.790 align:start position:0% decryption keys are different and the in particular<00:10:50.560> um<00:10:50.880> when<00:10:51.079> we<00:10:51.560> encrypt<00:10:52.560> um<00:10:53.000> we<00:10:53.200> have 00:10:53.790 --> 00:10:53.800 align:start position:0% particular um when we encrypt um we have 00:10:53.800 --> 00:10:55.790 align:start position:0% particular um when we encrypt um we have when<00:10:53.920> we<00:10:54.120> encrypt<00:10:54.800> we<00:10:54.959> don't<00:10:55.200> need<00:10:55.519> any 00:10:55.790 --> 00:10:55.800 align:start position:0% when we encrypt we don't need any 00:10:55.800 --> 00:10:58.310 align:start position:0% when we encrypt we don't need any privileged<00:10:56.560> information<00:10:57.560> um<00:10:57.800> and<00:10:58.000> when<00:10:58.160> we 00:10:58.310 --> 00:10:58.320 align:start position:0% privileged information um and when we 00:10:58.320 --> 00:11:00.750 align:start position:0% privileged information um and when we decrypt<00:10:58.920> we<00:10:59.040> need<00:10:59.560> a<00:10:59.760> private<00:11:00.120> key<00:11:00.440> that 00:11:00.750 --> 00:11:00.760 align:start position:0% decrypt we need a private key that 00:11:00.760 --> 00:11:02.990 align:start position:0% decrypt we need a private key that should<00:11:01.120> absolutely<00:11:01.959> stay 00:11:02.990 --> 00:11:03.000 align:start position:0% should absolutely stay 00:11:03.000 --> 00:11:07.790 align:start position:0% should absolutely stay secret<00:11:04.040> um<00:11:05.040> so<00:11:05.839> a<00:11:06.200> very<00:11:06.560> closely<00:11:07.120> related 00:11:07.790 --> 00:11:07.800 align:start position:0% secret um so a very closely related 00:11:07.800 --> 00:11:11.190 align:start position:0% secret um so a very closely related primitive<00:11:08.519> in<00:11:08.720> public<00:11:09.000> key<00:11:09.320> cryptography<00:11:10.320> is 00:11:11.190 --> 00:11:11.200 align:start position:0% primitive in public key cryptography is 00:11:11.200 --> 00:11:13.150 align:start position:0% primitive in public key cryptography is signatures<00:11:12.200> and<00:11:12.320> you<00:11:12.440> can<00:11:12.639> think<00:11:12.839> of<00:11:12.959> a 00:11:13.150 --> 00:11:13.160 align:start position:0% signatures and you can think of a 00:11:13.160 --> 00:11:17.030 align:start position:0% signatures and you can think of a signature<00:11:13.800> as<00:11:14.040> a<00:11:14.160> sort<00:11:14.399> of<00:11:14.680> Watermark<00:11:15.880> so<00:11:16.880> the 00:11:17.030 --> 00:11:17.040 align:start position:0% signature as a sort of Watermark so the 00:11:17.040 --> 00:11:20.910 align:start position:0% signature as a sort of Watermark so the API<00:11:17.519> here<00:11:17.760> changes<00:11:18.880> slightly<00:11:19.880> um<00:11:20.279> in<00:11:20.519> this 00:11:20.910 --> 00:11:20.920 align:start position:0% API here changes slightly um in this 00:11:20.920 --> 00:11:24.550 align:start position:0% API here changes slightly um in this case<00:11:21.920> um<00:11:22.279> we're<00:11:22.920> using<00:11:23.399> a<00:11:23.639> private<00:11:24.000> key<00:11:24.360> to 00:11:24.550 --> 00:11:24.560 align:start position:0% case um we're using a private key to 00:11:24.560 --> 00:11:27.829 align:start position:0% case um we're using a private key to sign<00:11:24.800> a<00:11:25.200> message<00:11:26.200> and<00:11:26.720> using<00:11:27.079> the<00:11:27.279> public<00:11:27.600> key 00:11:27.829 --> 00:11:27.839 align:start position:0% sign a message and using the public key 00:11:27.839 --> 00:11:30.629 align:start position:0% sign a message and using the public key to<00:11:28.120> verify<00:11:29.079> um<00:11:29.399> um<00:11:29.680> that<00:11:29.839> it<00:11:29.959> was<00:11:30.160> indeed 00:11:30.629 --> 00:11:30.639 align:start position:0% to verify um um that it was indeed 00:11:30.639 --> 00:11:34.870 align:start position:0% to verify um um that it was indeed signed<00:11:31.200> by<00:11:31.639> who<00:11:31.839> we<00:11:32.320> expected<00:11:33.320> so<00:11:34.279> it's<00:11:34.600> really 00:11:34.870 --> 00:11:34.880 align:start position:0% signed by who we expected so it's really 00:11:34.880 --> 00:11:37.710 align:start position:0% signed by who we expected so it's really interesting<00:11:35.800> um<00:11:35.959> for<00:11:36.200> example<00:11:36.800> like<00:11:37.279> the<00:11:37.440> same 00:11:37.710 --> 00:11:37.720 align:start position:0% interesting um for example like the same 00:11:37.720 --> 00:11:41.550 align:start position:0% interesting um for example like the same crypto<00:11:38.160> system<00:11:38.639> RSA<00:11:39.639> can<00:11:39.839> be<00:11:40.000> used<00:11:40.360> for<00:11:40.760> both 00:11:41.550 --> 00:11:41.560 align:start position:0% crypto system RSA can be used for both 00:11:41.560 --> 00:11:44.750 align:start position:0% crypto system RSA can be used for both encryption<00:11:42.079> and<00:11:42.399> signing<00:11:43.399> and<00:11:43.800> often<00:11:44.160> times 00:11:44.750 --> 00:11:44.760 align:start position:0% encryption and signing and often times 00:11:44.760 --> 00:11:47.590 align:start position:0% encryption and signing and often times well<00:11:45.040> and<00:11:45.200> it<00:11:45.399> it<00:11:45.560> just<00:11:45.839> involves<00:11:46.839> flipping 00:11:47.590 --> 00:11:47.600 align:start position:0% well and it it just involves flipping 00:11:47.600 --> 00:11:52.990 align:start position:0% well and it it just involves flipping actually<00:11:48.079> which<00:11:48.320> key<00:11:48.600> you<00:11:49.160> use<00:11:50.399> um<00:11:51.399> so<00:11:52.360> I<00:11:52.519> think 00:11:52.990 --> 00:11:53.000 align:start position:0% actually which key you use um so I think 00:11:53.000 --> 00:11:56.750 align:start position:0% actually which key you use um so I think something<00:11:53.399> to<00:11:53.600> note<00:11:53.959> here<00:11:54.600> is<00:11:55.000> that<00:11:56.000> um<00:11:56.519> let's 00:11:56.750 --> 00:11:56.760 align:start position:0% something to note here is that um let's 00:11:56.760 --> 00:12:01.790 align:start position:0% something to note here is that um let's say<00:11:56.959> in<00:11:57.160> RSA<00:11:57.800> to<00:11:58.160> verify<00:11:59.600> um<00:12:00.440> a<00:12:00.800> signature 00:12:01.790 --> 00:12:01.800 align:start position:0% say in RSA to verify um a signature 00:12:01.800 --> 00:12:04.389 align:start position:0% say in RSA to verify um a signature you're<00:12:02.200> actually<00:12:02.560> you<00:12:02.760> actually<00:12:03.120> decrypt<00:12:03.680> it 00:12:04.389 --> 00:12:04.399 align:start position:0% you're actually you actually decrypt it 00:12:04.399 --> 00:12:09.310 align:start position:0% you're actually you actually decrypt it um<00:12:04.839> using<00:12:05.279> one<00:12:05.480> of<00:12:05.639> the<00:12:05.760> RS<00:12:06.639> a<00:12:07.000> key<00:12:07.440> Pairs<00:12:08.440> and 00:12:09.310 --> 00:12:09.320 align:start position:0% um using one of the RS a key Pairs and 00:12:09.320 --> 00:12:11.910 align:start position:0% um using one of the RS a key Pairs and um<00:12:09.600> this<00:12:09.760> means<00:12:10.120> that<00:12:10.440> anyone<00:12:11.240> can<00:12:11.440> read<00:12:11.760> the 00:12:11.910 --> 00:12:11.920 align:start position:0% um this means that anyone can read the 00:12:11.920 --> 00:12:14.389 align:start position:0% um this means that anyone can read the signed<00:12:12.279> message<00:12:12.800> so<00:12:13.079> it's<00:12:13.399> not<00:12:13.760> this<00:12:14.000> it<00:12:14.160> does 00:12:14.389 --> 00:12:14.399 align:start position:0% signed message so it's not this it does 00:12:14.399 --> 00:12:17.990 align:start position:0% signed message so it's not this it does not<00:12:14.680> give<00:12:14.800> you<00:12:14.959> the<00:12:15.199> same<00:12:16.120> um<00:12:16.320> properties<00:12:17.240> of 00:12:17.990 --> 00:12:18.000 align:start position:0% not give you the same um properties of 00:12:18.000 --> 00:12:20.910 align:start position:0% not give you the same um properties of confidentiality<00:12:19.000> but<00:12:19.240> it<00:12:19.360> does<00:12:19.680> give<00:12:19.800> you<00:12:20.680> uh 00:12:20.910 --> 00:12:20.920 align:start position:0% confidentiality but it does give you uh 00:12:20.920 --> 00:12:27.230 align:start position:0% confidentiality but it does give you uh authentic 00:12:27.230 --> 00:12:27.240 align:start position:0% 00:12:27.240 --> 00:12:31.030 align:start position:0% authenticity<00:12:28.240> um<00:12:28.839> and<00:12:29.320> you<00:12:29.440> can<00:12:29.680> look<00:12:29.880> out<00:12:30.120> for 00:12:31.030 --> 00:12:31.040 align:start position:0% authenticity um and you can look out for 00:12:31.040 --> 00:12:33.509 align:start position:0% authenticity um and you can look out for oh<00:12:31.240> this<00:12:31.399> talk<00:12:31.680> already<00:12:31.920> ended<00:12:32.440> but<00:12:32.680> in 00:12:33.509 --> 00:12:33.519 align:start position:0% oh this talk already ended but in 00:12:33.519 --> 00:12:37.230 align:start position:0% oh this talk already ended but in ethereum<00:12:34.519> um<00:12:35.160> they're<00:12:35.959> currently<00:12:36.440> using<00:12:36.959> a 00:12:37.230 --> 00:12:37.240 align:start position:0% ethereum um they're currently using a 00:12:37.240 --> 00:12:39.829 align:start position:0% ethereum um they're currently using a signature<00:12:37.800> scheme<00:12:38.680> that<00:12:38.800> is<00:12:39.040> not<00:12:39.320> postquantum 00:12:39.829 --> 00:12:39.839 align:start position:0% signature scheme that is not postquantum 00:12:39.839 --> 00:12:43.350 align:start position:0% signature scheme that is not postquantum secure<00:12:40.760> and<00:12:41.360> they're<00:12:41.800> actively<00:12:42.800> um<00:12:42.959> thinking 00:12:43.350 --> 00:12:43.360 align:start position:0% secure and they're actively um thinking 00:12:43.360 --> 00:12:44.790 align:start position:0% secure and they're actively um thinking about<00:12:43.880> how<00:12:44.000> to 00:12:44.790 --> 00:12:44.800 align:start position:0% about how to 00:12:44.800 --> 00:12:49.269 align:start position:0% about how to transition<00:12:45.800> uh<00:12:45.920> to<00:12:46.160> postquantum 00:12:49.269 --> 00:12:49.279 align:start position:0% 00:12:49.279 --> 00:12:52.710 align:start position:0% yeah<00:12:50.279> so<00:12:50.720> a<00:12:51.000> common<00:12:51.519> Paradigm<00:12:52.000> and<00:12:52.160> like<00:12:52.320> email 00:12:52.710 --> 00:12:52.720 align:start position:0% yeah so a common Paradigm and like email 00:12:52.720 --> 00:12:55.910 align:start position:0% yeah so a common Paradigm and like email for<00:12:52.880> example<00:12:53.360> is<00:12:53.680> used<00:12:54.680> uh<00:12:54.880> like<00:12:55.040> use<00:12:55.360> signing 00:12:55.910 --> 00:12:55.920 align:start position:0% for example is used uh like use signing 00:12:55.920 --> 00:12:58.030 align:start position:0% for example is used uh like use signing and<00:12:56.120> encryption<00:12:56.839> right<00:12:57.320> so<00:12:57.480> you<00:12:57.639> want<00:12:57.800> to<00:12:57.920> be 00:12:58.030 --> 00:12:58.040 align:start position:0% and encryption right so you want to be 00:12:58.040 --> 00:12:59.430 align:start position:0% and encryption right so you want to be able<00:12:58.160> to<00:12:58.360> prove<00:12:58.680> that<00:12:58.800> you're<00:12:58.959> the<00:12:59.240> one<00:12:59.360> that 00:12:59.430 --> 00:12:59.440 align:start position:0% able to prove that you're the one that 00:12:59.440 --> 00:13:01.430 align:start position:0% able to prove that you're the one that created<00:12:59.760> the<00:12:59.920> message<00:13:00.600> and<00:13:00.720> you<00:13:00.880> only<00:13:01.199> want 00:13:01.430 --> 00:13:01.440 align:start position:0% created the message and you only want 00:13:01.440 --> 00:13:03.269 align:start position:0% created the message and you only want the<00:13:01.600> recipient<00:13:02.000> to<00:13:02.079> be<00:13:02.199> able<00:13:02.320> to<00:13:02.440> read<00:13:02.600> it<00:13:03.079> so 00:13:03.269 --> 00:13:03.279 align:start position:0% the recipient to be able to read it so 00:13:03.279 --> 00:13:04.629 align:start position:0% the recipient to be able to read it so in<00:13:03.360> order<00:13:03.600> to<00:13:03.800> do<00:13:04.000> this<00:13:04.160> you<00:13:04.279> would<00:13:04.399> put<00:13:04.560> in 00:13:04.629 --> 00:13:04.639 align:start position:0% in order to do this you would put in 00:13:04.639 --> 00:13:05.990 align:start position:0% in order to do this you would put in your<00:13:04.800> private<00:13:05.079> key<00:13:05.199> in<00:13:05.279> a<00:13:05.440> message<00:13:05.760> you<00:13:05.839> would 00:13:05.990 --> 00:13:06.000 align:start position:0% your private key in a message you would 00:13:06.000 --> 00:13:07.389 align:start position:0% your private key in a message you would sign<00:13:06.240> the<00:13:06.399> message<00:13:06.720> and<00:13:06.880> you<00:13:06.959> would<00:13:07.040> take<00:13:07.240> that 00:13:07.389 --> 00:13:07.399 align:start position:0% sign the message and you would take that 00:13:07.399 --> 00:13:10.069 align:start position:0% sign the message and you would take that sign<00:13:07.760> message<00:13:08.360> take<00:13:08.959> the<00:13:09.120> other<00:13:09.399> party's 00:13:10.069 --> 00:13:10.079 align:start position:0% sign message take the other party's 00:13:10.079 --> 00:13:13.230 align:start position:0% sign message take the other party's public<00:13:10.720> key<00:13:11.720> and<00:13:12.079> encrypt<00:13:12.600> the<00:13:12.760> message<00:13:13.120> and 00:13:13.230 --> 00:13:13.240 align:start position:0% public key and encrypt the message and 00:13:13.240 --> 00:13:15.189 align:start position:0% public key and encrypt the message and then<00:13:13.360> send<00:13:13.600> it<00:13:13.720> to<00:13:13.880> them<00:13:14.320> so<00:13:14.560> they<00:13:14.720> can<00:13:14.920> take 00:13:15.189 --> 00:13:15.199 align:start position:0% then send it to them so they can take 00:13:15.199 --> 00:13:17.310 align:start position:0% then send it to them so they can take that<00:13:15.519> decrypt<00:13:16.040> it<00:13:16.320> and<00:13:16.440> then<00:13:16.600> also<00:13:16.880> verify 00:13:17.310 --> 00:13:17.320 align:start position:0% that decrypt it and then also verify 00:13:17.320 --> 00:13:19.629 align:start position:0% that decrypt it and then also verify that<00:13:17.440> you<00:13:17.560> are<00:13:17.720> the 00:13:19.629 --> 00:13:19.639 align:start position:0% that you are the 00:13:19.639 --> 00:13:24.110 align:start position:0% that you are the sender<00:13:20.639> all<00:13:20.800> right<00:13:21.160> so<00:13:22.000> https<00:13:22.920> everyone<00:13:23.360> knows 00:13:24.110 --> 00:13:24.120 align:start position:0% sender all right so https everyone knows 00:13:24.120 --> 00:13:26.189 align:start position:0% sender all right so https everyone knows what<00:13:24.320> this<00:13:24.519> is<00:13:24.760> it's<00:13:24.959> little<00:13:25.160> green<00:13:25.440> lock<00:13:26.079> you 00:13:26.189 --> 00:13:26.199 align:start position:0% what this is it's little green lock you 00:13:26.199 --> 00:13:27.990 align:start position:0% what this is it's little green lock you know<00:13:26.399> make<00:13:26.560> sure<00:13:26.760> you're<00:13:27.279> you<00:13:27.399> have<00:13:27.519> a<00:13:27.680> secure 00:13:27.990 --> 00:13:28.000 align:start position:0% know make sure you're you have a secure 00:13:28.000 --> 00:13:29.790 align:start position:0% know make sure you're you have a secure connection<00:13:28.279> to<00:13:28.440> the<00:13:28.519> server 00:13:29.790 --> 00:13:29.800 align:start position:0% connection to the server 00:13:29.800 --> 00:13:34.310 align:start position:0% connection to the server um<00:13:30.800> this<00:13:30.920> is<00:13:31.079> a<00:13:31.160> little<00:13:31.760> handwavy<00:13:32.839> but<00:13:33.839> uh<00:13:34.040> the 00:13:34.310 --> 00:13:34.320 align:start position:0% um this is a little handwavy but uh the 00:13:34.320 --> 00:13:36.629 align:start position:0% um this is a little handwavy but uh the general<00:13:34.680> explanation<00:13:35.279> is<00:13:35.800> if<00:13:35.920> you<00:13:36.240> connect<00:13:36.519> to 00:13:36.629 --> 00:13:36.639 align:start position:0% general explanation is if you connect to 00:13:36.639 --> 00:13:38.509 align:start position:0% general explanation is if you connect to a<00:13:36.760> server<00:13:37.160> you<00:13:37.279> do<00:13:37.480> this<00:13:37.680> key<00:13:37.920> exchange<00:13:38.360> it's 00:13:38.509 --> 00:13:38.519 align:start position:0% a server you do this key exchange it's 00:13:38.519 --> 00:13:39.829 align:start position:0% a server you do this key exchange it's called<00:13:38.720> Diffy<00:13:39.000> Helman<00:13:39.320> which<00:13:39.440> I'll<00:13:39.560> go<00:13:39.639> into 00:13:39.829 --> 00:13:39.839 align:start position:0% called Diffy Helman which I'll go into 00:13:39.839 --> 00:13:42.829 align:start position:0% called Diffy Helman which I'll go into in<00:13:39.920> the<00:13:40.079> next<00:13:40.240> slide<00:13:41.199> and<00:13:41.800> you<00:13:42.040> get<00:13:42.279> out<00:13:42.600> a 00:13:42.829 --> 00:13:42.839 align:start position:0% in the next slide and you get out a 00:13:42.839 --> 00:13:45.310 align:start position:0% in the next slide and you get out a symmetric<00:13:43.399> key<00:13:43.880> right<00:13:44.440> so<00:13:44.760> public<00:13:45.120> key 00:13:45.310 --> 00:13:45.320 align:start position:0% symmetric key right so public key 00:13:45.320 --> 00:13:48.030 align:start position:0% symmetric key right so public key cryptography<00:13:46.160> is<00:13:46.360> slow<00:13:46.959> compared<00:13:47.320> to 00:13:48.030 --> 00:13:48.040 align:start position:0% cryptography is slow compared to 00:13:48.040 --> 00:13:50.470 align:start position:0% cryptography is slow compared to symmetric<00:13:48.600> key 00:13:50.470 --> 00:13:50.480 align:start position:0% symmetric key 00:13:50.480 --> 00:13:53.350 align:start position:0% symmetric key so<00:13:51.480> um<00:13:51.800> yeah<00:13:52.079> basically<00:13:52.560> to<00:13:52.800> to<00:13:52.920> make<00:13:53.199> web 00:13:53.350 --> 00:13:53.360 align:start position:0% so um yeah basically to to make web 00:13:53.360 --> 00:13:55.310 align:start position:0% so um yeah basically to to make web pages<00:13:53.639> load<00:13:53.959> faster<00:13:54.759> you<00:13:54.880> would<00:13:55.040> do<00:13:55.199> this 00:13:55.310 --> 00:13:55.320 align:start position:0% pages load faster you would do this 00:13:55.320 --> 00:13:58.189 align:start position:0% pages load faster you would do this Diffy<00:13:55.600> Helman<00:13:55.880> key<00:13:56.120> exchange<00:13:57.120> and<00:13:57.360> then<00:13:58.079> get 00:13:58.189 --> 00:13:58.199 align:start position:0% Diffy Helman key exchange and then get 00:13:58.199 --> 00:14:00.310 align:start position:0% Diffy Helman key exchange and then get out<00:13:58.399> a<00:13:58.560> symmetric<00:13:59.160> key<00:13:59.360> that<00:13:59.560> only<00:13:59.920> you<00:14:00.160> and 00:14:00.310 --> 00:14:00.320 align:start position:0% out a symmetric key that only you and 00:14:00.320 --> 00:14:02.430 align:start position:0% out a symmetric key that only you and the<00:14:00.440> server<00:14:00.800> know<00:14:01.399> and<00:14:01.519> then<00:14:01.680> from<00:14:01.920> there<00:14:02.079> on 00:14:02.430 --> 00:14:02.440 align:start position:0% the server know and then from there on 00:14:02.440 --> 00:14:06.550 align:start position:0% the server know and then from there on you<00:14:02.560> can<00:14:02.800> do<00:14:03.759> um<00:14:04.279> faster<00:14:05.120> messages<00:14:06.120> so<00:14:06.279> the<00:14:06.399> way 00:14:06.550 --> 00:14:06.560 align:start position:0% you can do um faster messages so the way 00:14:06.560 --> 00:14:08.949 align:start position:0% you can do um faster messages so the way this<00:14:06.720> works<00:14:07.199> is<00:14:07.360> you<00:14:07.680> start<00:14:07.959> with<00:14:08.120> some<00:14:08.320> shared 00:14:08.949 --> 00:14:08.959 align:start position:0% this works is you start with some shared 00:14:08.959 --> 00:14:12.269 align:start position:0% this works is you start with some shared paint<00:14:09.600> right<00:14:09.759> some<00:14:09.920> shared<00:14:10.680> colors<00:14:11.680> and<00:14:12.199> this 00:14:12.269 --> 00:14:12.279 align:start position:0% paint right some shared colors and this 00:14:12.279 --> 00:14:14.110 align:start position:0% paint right some shared colors and this is<00:14:12.399> the<00:14:12.560> paint<00:14:12.839> analogy<00:14:13.360> for<00:14:13.639> for<00:14:13.800> Diffy 00:14:14.110 --> 00:14:14.120 align:start position:0% is the paint analogy for for Diffy 00:14:14.120 --> 00:14:17.069 align:start position:0% is the paint analogy for for Diffy helmet<00:14:15.079> but<00:14:16.000> you<00:14:16.120> start<00:14:16.480> with<00:14:16.600> some<00:14:16.720> shared 00:14:17.069 --> 00:14:17.079 align:start position:0% helmet but you start with some shared 00:14:17.079 --> 00:14:18.990 align:start position:0% helmet but you start with some shared paint<00:14:17.440> and<00:14:17.560> then<00:14:17.639> you<00:14:17.800> each<00:14:18.040> have<00:14:18.199> some<00:14:18.440> secret 00:14:18.990 --> 00:14:19.000 align:start position:0% paint and then you each have some secret 00:14:19.000 --> 00:14:22.350 align:start position:0% paint and then you each have some secret color<00:14:20.000> and<00:14:20.360> you<00:14:20.600> combine<00:14:21.120> those<00:14:21.440> to<00:14:21.800> create 00:14:22.350 --> 00:14:22.360 align:start position:0% color and you combine those to create 00:14:22.360 --> 00:14:26.629 align:start position:0% color and you combine those to create these<00:14:22.639> two<00:14:23.639> inputs<00:14:24.399> you<00:14:24.600> exchange<00:14:25.120> the<00:14:25.639> inputs 00:14:26.629 --> 00:14:26.639 align:start position:0% these two inputs you exchange the inputs 00:14:26.639 --> 00:14:28.430 align:start position:0% these two inputs you exchange the inputs you<00:14:26.880> add<00:14:27.120> back<00:14:27.240> in<00:14:27.399> your<00:14:27.600> secrets<00:14:28.199> and<00:14:28.320> then 00:14:28.430 --> 00:14:28.440 align:start position:0% you add back in your secrets and then 00:14:28.440 --> 00:14:30.430 align:start position:0% you add back in your secrets and then you<00:14:28.639> end<00:14:28.839> up<00:14:29.160> with<00:14:29.279> the<00:14:29.360> same<00:14:29.600> paint<00:14:29.880> color<00:14:30.240> on 00:14:30.430 --> 00:14:30.440 align:start position:0% you end up with the same paint color on 00:14:30.440 --> 00:14:32.470 align:start position:0% you end up with the same paint color on either<00:14:30.800> side<00:14:31.480> but<00:14:31.639> no<00:14:31.759> one<00:14:31.880> in<00:14:32.000> the<00:14:32.120> middle 00:14:32.470 --> 00:14:32.480 align:start position:0% either side but no one in the middle 00:14:32.480 --> 00:14:38.990 align:start position:0% either side but no one in the middle could<00:14:32.880> know<00:14:33.880> what<00:14:34.040> your<00:14:34.600> what<00:14:34.720> your<00:14:34.880> secrets 00:14:38.990 --> 00:14:39.000 align:start position:0% 00:14:39.000 --> 00:14:43.509 align:start position:0% are<00:14:40.000> yeah<00:14:40.440> so<00:14:41.440> um<00:14:41.720> we<00:14:41.880> went<00:14:42.240> through<00:14:42.959> hashing 00:14:43.509 --> 00:14:43.519 align:start position:0% are yeah so um we went through hashing 00:14:43.519 --> 00:14:48.509 align:start position:0% are yeah so um we went through hashing encryption<00:14:44.440> and<00:14:45.120> signatures<00:14:46.120> um<00:14:46.880> and<00:14:47.880> we<00:14:48.240> were 00:14:48.509 --> 00:14:48.519 align:start position:0% encryption and signatures um and we were 00:14:48.519 --> 00:14:50.910 align:start position:0% encryption and signatures um and we were considering<00:14:49.120> these<00:14:49.360> to<00:14:49.560> be<00:14:50.079> sort<00:14:50.279> of 00:14:50.910 --> 00:14:50.920 align:start position:0% considering these to be sort of 00:14:50.920 --> 00:14:52.749 align:start position:0% considering these to be sort of generation<00:14:51.600> one<00:14:52.079> purpose-built 00:14:52.749 --> 00:14:52.759 align:start position:0% generation one purpose-built 00:14:52.759 --> 00:14:55.509 align:start position:0% generation one purpose-built cryptography<00:14:53.759> that<00:14:54.160> are<00:14:54.399> really<00:14:54.680> lightweight 00:14:55.509 --> 00:14:55.519 align:start position:0% cryptography that are really lightweight 00:14:55.519 --> 00:14:59.150 align:start position:0% cryptography that are really lightweight and<00:14:56.360> um<00:14:57.360> just<00:14:57.560> do<00:14:58.120> their<00:14:58.360> task<00:14:58.720> really<00:14:58.880> well<00:14:59.040> as 00:14:59.150 --> 00:14:59.160 align:start position:0% and um just do their task really well as 00:14:59.160 --> 00:15:03.230 align:start position:0% and um just do their task really well as well<00:15:00.000> um<00:15:00.399> what's<00:15:00.680> been<00:15:01.360> emerging<00:15:02.360> um<00:15:02.920> and<00:15:03.120> what 00:15:03.230 --> 00:15:03.240 align:start position:0% well um what's been emerging um and what 00:15:03.240 --> 00:15:05.749 align:start position:0% well um what's been emerging um and what you'll<00:15:03.440> see<00:15:03.639> a<00:15:03.800> lot<00:15:04.079> of<00:15:04.680> at<00:15:04.839> Devcon<00:15:05.480> is 00:15:05.749 --> 00:15:05.759 align:start position:0% you'll see a lot of at Devcon is 00:15:05.759 --> 00:15:09.910 align:start position:0% you'll see a lot of at Devcon is programmable<00:15:06.880> cryptography<00:15:08.360> so<00:15:09.360> um<00:15:09.600> these 00:15:09.910 --> 00:15:09.920 align:start position:0% programmable cryptography so um these 00:15:09.920 --> 00:15:12.230 align:start position:0% programmable cryptography so um these include<00:15:10.440> zero<00:15:10.800> knowledge<00:15:11.079> proofs<00:15:11.959> um 00:15:12.230 --> 00:15:12.240 align:start position:0% include zero knowledge proofs um 00:15:12.240 --> 00:15:14.030 align:start position:0% include zero knowledge proofs um multi-party<00:15:12.920> computation<00:15:13.519> and<00:15:13.680> fully 00:15:14.030 --> 00:15:14.040 align:start position:0% multi-party computation and fully 00:15:14.040 --> 00:15:15.110 align:start position:0% multi-party computation and fully homomorphic 00:15:15.110 --> 00:15:15.120 align:start position:0% homomorphic 00:15:15.120 --> 00:15:18.710 align:start position:0% homomorphic encryption<00:15:16.120> and<00:15:16.480> these<00:15:16.720> Protocols<00:15:17.399> are<00:15:18.399> a<00:15:18.519> lot 00:15:18.710 --> 00:15:18.720 align:start position:0% encryption and these Protocols are a lot 00:15:18.720 --> 00:15:20.990 align:start position:0% encryption and these Protocols are a lot more<00:15:19.000> heavyweight<00:15:20.000> in<00:15:20.120> the<00:15:20.279> sense<00:15:20.600> that<00:15:20.759> they 00:15:20.990 --> 00:15:21.000 align:start position:0% more heavyweight in the sense that they 00:15:21.000 --> 00:15:25.550 align:start position:0% more heavyweight in the sense that they involve<00:15:21.720> usually<00:15:22.519> lots<00:15:23.000> more<00:15:23.920> um<00:15:24.560> assumptions 00:15:25.550 --> 00:15:25.560 align:start position:0% involve usually lots more um assumptions 00:15:25.560 --> 00:15:26.749 align:start position:0% involve usually lots more um assumptions security 00:15:26.749 --> 00:15:26.759 align:start position:0% security 00:15:26.759 --> 00:15:29.350 align:start position:0% security assumptions<00:15:27.759> um<00:15:28.240> but<00:15:28.560> on<00:15:28.680> the<00:15:29.040> other<00:15:29.199> hand 00:15:29.350 --> 00:15:29.360 align:start position:0% assumptions um but on the other hand 00:15:29.360 --> 00:15:31.749 align:start position:0% assumptions um but on the other hand they're<00:15:29.560> a<00:15:29.720> lot<00:15:29.880> more<00:15:30.160> general<00:15:30.600> purpose<00:15:31.600> in 00:15:31.749 --> 00:15:31.759 align:start position:0% they're a lot more general purpose in 00:15:31.759 --> 00:15:34.749 align:start position:0% they're a lot more general purpose in the<00:15:31.920> sense<00:15:32.319> that<00:15:32.639> the<00:15:32.800> end<00:15:33.120> user<00:15:33.920> is<00:15:34.079> free<00:15:34.440> to 00:15:34.749 --> 00:15:34.759 align:start position:0% the sense that the end user is free to 00:15:34.759 --> 00:15:38.350 align:start position:0% the sense that the end user is free to Define<00:15:35.680> any<00:15:35.959> arbitrary<00:15:36.880> relation<00:15:37.880> uh<00:15:38.079> they're 00:15:38.350 --> 00:15:38.360 align:start position:0% Define any arbitrary relation uh they're 00:15:38.360 --> 00:15:42.269 align:start position:0% Define any arbitrary relation uh they're not<00:15:39.160> um<00:15:39.399> limited<00:15:39.839> to<00:15:40.040> say<00:15:40.720> signatures 00:15:42.269 --> 00:15:42.279 align:start position:0% not um limited to say signatures 00:15:42.279 --> 00:15:46.269 align:start position:0% not um limited to say signatures encryption<00:15:43.279> um<00:15:44.199> and<00:15:44.600> in<00:15:44.959> that<00:15:45.199> sense<00:15:45.839> um<00:15:46.040> this 00:15:46.269 --> 00:15:46.279 align:start position:0% encryption um and in that sense um this 00:15:46.279 --> 00:15:51.110 align:start position:0% encryption um and in that sense um this Clause<00:15:46.639> of<00:15:47.240> Primitives<00:15:47.959> are 00:15:51.110 --> 00:15:51.120 align:start position:0% 00:15:51.120 --> 00:15:53.949 align:start position:0% programmable<00:15:52.120> yeah<00:15:52.440> I<00:15:52.560> think<00:15:53.360> these<00:15:53.560> talks 00:15:53.949 --> 00:15:53.959 align:start position:0% programmable yeah I think these talks 00:15:53.959 --> 00:15:56.710 align:start position:0% programmable yeah I think these talks happened 00:15:56.710 --> 00:15:56.720 align:start position:0% 00:15:56.720 --> 00:15:59.430 align:start position:0% already<00:15:57.720> um<00:15:58.199> but<00:15:58.399> introduct 00:15:59.430 --> 00:15:59.440 align:start position:0% already um but introduct 00:15:59.440 --> 00:16:03.309 align:start position:0% already um but introduct to<00:16:00.360> this<00:16:00.560> Paradigm<00:16:01.120> of<00:16:01.319> programmable 00:16:03.309 --> 00:16:03.319 align:start position:0% to this Paradigm of programmable 00:16:03.319 --> 00:16:06.189 align:start position:0% to this Paradigm of programmable cryptography<00:16:04.319> so<00:16:04.560> we'll<00:16:04.880> quickly<00:16:05.279> go<00:16:05.519> through 00:16:06.189 --> 00:16:06.199 align:start position:0% cryptography so we'll quickly go through 00:16:06.199 --> 00:16:09.910 align:start position:0% cryptography so we'll quickly go through the<00:16:06.399> three<00:16:06.920> categories<00:16:07.920> um<00:16:08.399> maybe<00:16:09.319> the<00:16:09.519> most 00:16:09.910 --> 00:16:09.920 align:start position:0% the three categories um maybe the most 00:16:09.920 --> 00:16:13.309 align:start position:0% the three categories um maybe the most popular<00:16:10.639> one<00:16:10.959> is<00:16:11.160> zero<00:16:11.560> knowledge 00:16:13.309 --> 00:16:13.319 align:start position:0% popular one is zero knowledge 00:16:13.319 --> 00:16:17.710 align:start position:0% popular one is zero knowledge um<00:16:14.319> yeah<00:16:14.480> that's<00:16:14.680> great<00:16:15.440> um<00:16:15.680> so<00:16:16.720> essentially 00:16:17.710 --> 00:16:17.720 align:start position:0% um yeah that's great um so essentially 00:16:17.720 --> 00:16:20.990 align:start position:0% um yeah that's great um so essentially zero<00:16:18.079> knowledge<00:16:18.360> ZK<00:16:18.880> is<00:16:19.000> a<00:16:19.120> way<00:16:19.240> for<00:16:19.399> aover<00:16:20.120> to 00:16:20.990 --> 00:16:21.000 align:start position:0% zero knowledge ZK is a way for aover to 00:16:21.000 --> 00:16:22.749 align:start position:0% zero knowledge ZK is a way for aover to prove<00:16:21.319> some<00:16:21.519> statement<00:16:21.880> to<00:16:22.040> somebody<00:16:22.399> else 00:16:22.749 --> 00:16:22.759 align:start position:0% prove some statement to somebody else 00:16:22.759 --> 00:16:25.389 align:start position:0% prove some statement to somebody else and<00:16:22.880> they<00:16:23.040> can<00:16:23.160> verify<00:16:23.560> it<00:16:23.759> so<00:16:23.959> for<00:16:24.199> example<00:16:25.199> um 00:16:25.389 --> 00:16:25.399 align:start position:0% and they can verify it so for example um 00:16:25.399 --> 00:16:28.110 align:start position:0% and they can verify it so for example um you<00:16:25.519> can<00:16:25.839> have<00:16:26.279> your<00:16:26.639> picture<00:16:27.279> and<00:16:27.399> then<00:16:27.759> some 00:16:28.110 --> 00:16:28.120 align:start position:0% you can have your picture and then some 00:16:28.120 --> 00:16:29.870 align:start position:0% you can have your picture and then some private<00:16:28.480> data<00:16:29.000> your<00:16:29.160> age<00:16:29.360> or<00:16:29.480> your<00:16:29.600> date<00:16:29.759> of 00:16:29.870 --> 00:16:29.880 align:start position:0% private data your age or your date of 00:16:29.880 --> 00:16:32.990 align:start position:0% private data your age or your date of birth<00:16:30.079> or<00:16:30.199> whatever<00:16:30.480> go<00:16:30.680> into<00:16:30.959> some<00:16:31.920> ckp<00:16:32.920> and 00:16:32.990 --> 00:16:33.000 align:start position:0% birth or whatever go into some ckp and 00:16:33.000 --> 00:16:35.470 align:start position:0% birth or whatever go into some ckp and then<00:16:33.240> out<00:16:33.560> comes<00:16:33.959> a<00:16:34.199> hash<00:16:34.519> of<00:16:34.639> your<00:16:34.839> photo<00:16:35.360> and 00:16:35.470 --> 00:16:35.480 align:start position:0% then out comes a hash of your photo and 00:16:35.480 --> 00:16:36.710 align:start position:0% then out comes a hash of your photo and then<00:16:35.600> basically<00:16:35.880> a<00:16:36.000> thumbs<00:16:36.240> up<00:16:36.440> that<00:16:36.560> you're 00:16:36.710 --> 00:16:36.720 align:start position:0% then basically a thumbs up that you're 00:16:36.720 --> 00:16:39.350 align:start position:0% then basically a thumbs up that you're like<00:16:36.920> over<00:16:37.120> 21<00:16:37.519> or<00:16:37.680> whatever<00:16:38.680> um<00:16:38.839> so<00:16:38.959> you<00:16:39.079> need 00:16:39.350 --> 00:16:39.360 align:start position:0% like over 21 or whatever um so you need 00:16:39.360 --> 00:16:41.790 align:start position:0% like over 21 or whatever um so you need that<00:16:39.680> hash<00:16:39.920> your<00:16:40.199> photo<00:16:41.079> to<00:16:41.279> make<00:16:41.440> sure<00:16:41.680> that 00:16:41.790 --> 00:16:41.800 align:start position:0% that hash your photo to make sure that 00:16:41.800 --> 00:16:43.150 align:start position:0% that hash your photo to make sure that someone<00:16:42.079> can<00:16:42.240> actually<00:16:42.480> authenticate<00:16:43.040> that 00:16:43.150 --> 00:16:43.160 align:start position:0% someone can actually authenticate that 00:16:43.160 --> 00:16:44.670 align:start position:0% someone can actually authenticate that it's<00:16:43.319> you<00:16:43.600> they<00:16:43.720> can<00:16:43.880> they<00:16:43.959> can<00:16:44.040> see<00:16:44.199> the<00:16:44.319> image 00:16:44.670 --> 00:16:44.680 align:start position:0% it's you they can they can see the image 00:16:44.680 --> 00:16:46.470 align:start position:0% it's you they can they can see the image make<00:16:44.880> sure<00:16:45.040> that<00:16:45.160> it<00:16:45.360> you<00:16:45.480> know<00:16:45.800> corresponds 00:16:46.470 --> 00:16:46.480 align:start position:0% make sure that it you know corresponds 00:16:46.480 --> 00:16:50.189 align:start position:0% make sure that it you know corresponds with<00:16:46.639> your<00:16:47.199> age<00:16:48.199> um<00:16:49.199> and<00:16:49.560> yeah<00:16:49.880> they<00:16:50.000> can<00:16:50.120> you 00:16:50.189 --> 00:16:50.199 align:start position:0% with your age um and yeah they can you 00:16:50.199 --> 00:16:51.829 align:start position:0% with your age um and yeah they can you know<00:16:50.319> you<00:16:50.399> can<00:16:50.519> prove<00:16:50.759> your<00:16:50.959> over<00:16:51.199> 21<00:16:51.639> without 00:16:51.829 --> 00:16:51.839 align:start position:0% know you can prove your over 21 without 00:16:51.839 --> 00:16:55.829 align:start position:0% know you can prove your over 21 without showing<00:16:52.079> your<00:16:52.399> license<00:16:52.720> or<00:16:52.880> your<00:16:53.040> passport<00:16:53.399> or 00:16:55.829 --> 00:16:55.839 align:start position:0% 00:16:55.839 --> 00:17:00.590 align:start position:0% whatever<00:16:56.839> yeah<00:16:57.240> so<00:16:57.920> the<00:16:58.399> over<00:16:58.920> 21<00:16:59.480> relation<00:17:00.120> is 00:17:00.590 --> 00:17:00.600 align:start position:0% whatever yeah so the over 21 relation is 00:17:00.600 --> 00:17:03.710 align:start position:0% whatever yeah so the over 21 relation is just<00:17:00.920> one<00:17:01.319> example<00:17:02.319> of<00:17:02.800> a<00:17:02.959> relation<00:17:03.480> that<00:17:03.600> you 00:17:03.710 --> 00:17:03.720 align:start position:0% just one example of a relation that you 00:17:03.720 --> 00:17:05.669 align:start position:0% just one example of a relation that you can<00:17:03.920> prove<00:17:04.199> in<00:17:04.360> zero<00:17:04.679> knowledge<00:17:05.120> the<00:17:05.319> point 00:17:05.669 --> 00:17:05.679 align:start position:0% can prove in zero knowledge the point 00:17:05.679 --> 00:17:08.150 align:start position:0% can prove in zero knowledge the point here<00:17:05.959> being<00:17:06.360> that<00:17:06.959> this<00:17:07.079> is<00:17:07.240> an<00:17:07.439> arbitrary 00:17:08.150 --> 00:17:08.160 align:start position:0% here being that this is an arbitrary 00:17:08.160 --> 00:17:12.909 align:start position:0% here being that this is an arbitrary user<00:17:08.640> defined<00:17:09.600> relation<00:17:10.600> and<00:17:11.240> as<00:17:11.439> Tyler<00:17:11.919> said 00:17:12.909 --> 00:17:12.919 align:start position:0% user defined relation and as Tyler said 00:17:12.919 --> 00:17:16.549 align:start position:0% user defined relation and as Tyler said the<00:17:13.120> pr<00:17:13.880> can<00:17:14.199> keep<00:17:14.559> their<00:17:14.880> secret<00:17:15.360> witness<00:17:16.360> um 00:17:16.549 --> 00:17:16.559 align:start position:0% the pr can keep their secret witness um 00:17:16.559 --> 00:17:19.189 align:start position:0% the pr can keep their secret witness um unknown<00:17:17.079> to<00:17:17.280> the<00:17:17.480> verifier<00:17:18.160> and<00:17:18.439> yet<00:17:18.839> still 00:17:19.189 --> 00:17:19.199 align:start position:0% unknown to the verifier and yet still 00:17:19.199 --> 00:17:21.630 align:start position:0% unknown to the verifier and yet still convince<00:17:19.600> the<00:17:19.760> verifier<00:17:20.679> that<00:17:20.839> it<00:17:21.079> satisfies 00:17:21.630 --> 00:17:21.640 align:start position:0% convince the verifier that it satisfies 00:17:21.640 --> 00:17:24.230 align:start position:0% convince the verifier that it satisfies the<00:17:22.039> relation<00:17:23.039> um<00:17:23.199> and<00:17:23.400> corresponds<00:17:23.919> to<00:17:24.079> a 00:17:24.230 --> 00:17:24.240 align:start position:0% the relation um and corresponds to a 00:17:24.240 --> 00:17:26.870 align:start position:0% the relation um and corresponds to a certain<00:17:24.839> agreed<00:17:25.280> upon<00:17:25.760> and<00:17:26.000> publicly<00:17:26.400> known 00:17:26.870 --> 00:17:26.880 align:start position:0% certain agreed upon and publicly known 00:17:26.880 --> 00:17:28.950 align:start position:0% certain agreed upon and publicly known output 00:17:28.950 --> 00:17:28.960 align:start position:0% output 00:17:28.960 --> 00:17:32.430 align:start position:0% output so<00:17:29.520> another<00:17:30.000> interesting<00:17:30.799> property<00:17:31.640> of<00:17:32.080> many 00:17:32.430 --> 00:17:32.440 align:start position:0% so another interesting property of many 00:17:32.440 --> 00:17:34.590 align:start position:0% so another interesting property of many zero<00:17:32.840> knowledge<00:17:33.160> proof<00:17:33.520> systems<00:17:33.960> is<00:17:34.160> sex 00:17:34.590 --> 00:17:34.600 align:start position:0% zero knowledge proof systems is sex 00:17:34.600 --> 00:17:37.909 align:start position:0% zero knowledge proof systems is sex synness<00:17:35.600> and<00:17:36.120> what<00:17:36.360> this<00:17:36.520> means<00:17:37.400> is<00:17:37.559> that<00:17:37.760> the 00:17:37.909 --> 00:17:37.919 align:start position:0% synness and what this means is that the 00:17:37.919 --> 00:17:41.350 align:start position:0% synness and what this means is that the PR's<00:17:38.760> communication<00:17:39.760> is<00:17:40.120> much<00:17:40.400> smaller<00:17:41.160> than 00:17:41.350 --> 00:17:41.360 align:start position:0% PR's communication is much smaller than 00:17:41.360 --> 00:17:44.590 align:start position:0% PR's communication is much smaller than the<00:17:41.559> size<00:17:41.760> of<00:17:41.919> the<00:17:42.080> relation<00:17:43.039> that<00:17:43.160> he<00:17:43.600> proved 00:17:44.590 --> 00:17:44.600 align:start position:0% the size of the relation that he proved 00:17:44.600 --> 00:17:47.950 align:start position:0% the size of the relation that he proved and<00:17:44.760> this<00:17:45.000> comes<00:17:45.280> in<00:17:45.919> handy<00:17:46.520> in<00:17:46.799> ZK<00:17:47.280> rollups 00:17:47.950 --> 00:17:47.960 align:start position:0% and this comes in handy in ZK rollups 00:17:47.960 --> 00:17:50.150 align:start position:0% and this comes in handy in ZK rollups which<00:17:48.720> I<00:17:48.840> think<00:17:49.120> many<00:17:49.360> of<00:17:49.520> us<00:17:49.679> have<00:17:49.840> heard 00:17:50.150 --> 00:17:50.160 align:start position:0% which I think many of us have heard 00:17:50.160 --> 00:17:54.190 align:start position:0% which I think many of us have heard about<00:17:50.760> where<00:17:51.640> whereby<00:17:52.039> we<00:17:52.200> Outsource<00:17:53.200> um<00:17:53.880> very 00:17:54.190 --> 00:17:54.200 align:start position:0% about where whereby we Outsource um very 00:17:54.200 --> 00:17:57.909 align:start position:0% about where whereby we Outsource um very heavy<00:17:54.600> computation<00:17:55.600> to<00:17:56.280> some<00:17:57.280> um<00:17:57.600> well 00:17:57.909 --> 00:17:57.919 align:start position:0% heavy computation to some um well 00:17:57.919 --> 00:18:01.870 align:start position:0% heavy computation to some um well resourced<00:17:58.840> machine<00:17:59.880> offchain<00:18:00.880> um<00:18:01.360> and<00:18:01.559> then 00:18:01.870 --> 00:18:01.880 align:start position:0% resourced machine offchain um and then 00:18:01.880 --> 00:18:05.230 align:start position:0% resourced machine offchain um and then simply<00:18:02.320> submit<00:18:03.000> a<00:18:03.280> very<00:18:03.640> small<00:18:04.080> proof<00:18:04.760> of<00:18:05.000> its 00:18:05.230 --> 00:18:05.240 align:start position:0% simply submit a very small proof of its 00:18:05.240 --> 00:18:08.590 align:start position:0% simply submit a very small proof of its validity<00:18:06.280> onchain<00:18:07.280> um<00:18:07.520> the<00:18:07.679> point<00:18:07.960> here<00:18:08.159> being 00:18:08.590 --> 00:18:08.600 align:start position:0% validity onchain um the point here being 00:18:08.600 --> 00:18:11.350 align:start position:0% validity onchain um the point here being that<00:18:08.880> verifying<00:18:09.480> the<00:18:09.840> computation<00:18:10.840> is<00:18:11.000> a<00:18:11.159> lot 00:18:11.350 --> 00:18:11.360 align:start position:0% that verifying the computation is a lot 00:18:11.360 --> 00:18:13.789 align:start position:0% that verifying the computation is a lot cheaper<00:18:12.120> and<00:18:12.679> we<00:18:12.840> we<00:18:12.960> don't<00:18:13.120> have<00:18:13.240> to<00:18:13.440> pay<00:18:13.640> that 00:18:13.789 --> 00:18:13.799 align:start position:0% cheaper and we we don't have to pay that 00:18:13.799 --> 00:18:18.110 align:start position:0% cheaper and we we don't have to pay that much<00:18:14.039> gas<00:18:14.320> for<00:18:14.799> it<00:18:15.799> um<00:18:16.159> there's<00:18:16.640> also<00:18:17.559> many 00:18:18.110 --> 00:18:18.120 align:start position:0% much gas for it um there's also many 00:18:18.120 --> 00:18:21.630 align:start position:0% much gas for it um there's also many other<00:18:19.120> um<00:18:19.960> sort<00:18:20.159> of<00:18:20.440> developments<00:18:21.080> in<00:18:21.280> zero 00:18:21.630 --> 00:18:21.640 align:start position:0% other um sort of developments in zero 00:18:21.640 --> 00:18:25.390 align:start position:0% other um sort of developments in zero knowledge<00:18:21.960> proof<00:18:22.360> systems<00:18:23.360> um<00:18:24.120> so<00:18:25.039> I<00:18:25.159> think 00:18:25.390 --> 00:18:25.400 align:start position:0% knowledge proof systems um so I think 00:18:25.400 --> 00:18:28.029 align:start position:0% knowledge proof systems um so I think youf<00:18:26.159> actually<00:18:26.440> will<00:18:26.679> talk<00:18:26.960> about<00:18:27.559> elliptic 00:18:28.029 --> 00:18:28.039 align:start position:0% youf actually will talk about elliptic 00:18:28.039 --> 00:18:32.230 align:start position:0% youf actually will talk about elliptic curves<00:18:28.320> and<00:18:28.440> SN<00:18:29.159> right<00:18:29.320> after<00:18:29.799> us 00:18:32.230 --> 00:18:32.240 align:start position:0% curves and SN right after us 00:18:32.240 --> 00:18:38.510 align:start position:0% curves and SN right after us um<00:18:33.240> and<00:18:33.760> many<00:18:34.640> more<00:18:35.320> exciting<00:18:36.320> examples<00:18:37.320> of<00:18:38.159> um 00:18:38.510 --> 00:18:38.520 align:start position:0% um and many more exciting examples of um 00:18:38.520 --> 00:18:40.950 align:start position:0% um and many more exciting examples of um applications<00:18:39.200> that<00:18:39.320> use<00:18:39.600> ZK<00:18:40.039> I<00:18:40.120> think<00:18:40.320> Prat 00:18:40.950 --> 00:18:40.960 align:start position:0% applications that use ZK I think Prat 00:18:40.960 --> 00:18:43.350 align:start position:0% applications that use ZK I think Prat right<00:18:41.159> before<00:18:41.440> us<00:18:41.760> for 00:18:43.350 --> 00:18:43.360 align:start position:0% right before us for 00:18:43.360 --> 00:18:48.909 align:start position:0% right before us for example<00:18:44.360> um<00:18:44.840> so<00:18:45.960> now<00:18:46.960> if<00:18:47.240> we<00:18:47.840> sort 00:18:48.909 --> 00:18:48.919 align:start position:0% example um so now if we sort 00:18:48.919 --> 00:18:50.669 align:start position:0% example um so now if we sort of 00:18:50.669 --> 00:18:50.679 align:start position:0% of 00:18:50.679 --> 00:18:57.270 align:start position:0% of um<00:18:51.679> if<00:18:51.799> we<00:18:52.400> introduce<00:18:53.400> um<00:18:54.159> this<00:18:54.960> setting<00:18:56.280> where 00:18:57.270 --> 00:18:57.280 align:start position:0% um if we introduce um this setting where 00:18:57.280 --> 00:18:59.549 align:start position:0% um if we introduce um this setting where the<00:18:57.480> witness<00:18:57.919> is<00:18:58.159> no<00:18:58.400> longer<00:18:58.960> held<00:18:59.320> by<00:18:59.440> a 00:18:59.549 --> 00:18:59.559 align:start position:0% the witness is no longer held by a 00:18:59.559 --> 00:19:03.070 align:start position:0% the witness is no longer held by a single<00:18:59.960> party<00:19:00.840> namely<00:19:01.159> the<00:19:01.280> prer<00:19:02.240> and<00:19:02.559> we<00:19:02.720> move 00:19:03.070 --> 00:19:03.080 align:start position:0% single party namely the prer and we move 00:19:03.080 --> 00:19:07.430 align:start position:0% single party namely the prer and we move to<00:19:03.760> consider<00:19:04.760> like<00:19:05.760> multiple<00:19:06.360> parties<00:19:07.120> um 00:19:07.430 --> 00:19:07.440 align:start position:0% to consider like multiple parties um 00:19:07.440 --> 00:19:11.190 align:start position:0% to consider like multiple parties um working<00:19:08.240> together<00:19:09.240> to<00:19:09.480> compete<00:19:09.919> a<00:19:10.200> relation 00:19:11.190 --> 00:19:11.200 align:start position:0% working together to compete a relation 00:19:11.200 --> 00:19:14.029 align:start position:0% working together to compete a relation um<00:19:11.400> this<00:19:11.520> would<00:19:11.679> bring<00:19:11.919> us<00:19:12.120> into<00:19:13.120> um<00:19:13.240> MPC 00:19:14.029 --> 00:19:14.039 align:start position:0% um this would bring us into um MPC 00:19:14.039 --> 00:19:18.710 align:start position:0% um this would bring us into um MPC multi-party<00:19:15.039> computation<00:19:16.039> and<00:19:16.720> um<00:19:17.400> this<00:19:17.640> is 00:19:18.710 --> 00:19:18.720 align:start position:0% multi-party computation and um this is 00:19:18.720 --> 00:19:23.070 align:start position:0% multi-party computation and um this is um<00:19:19.720> a<00:19:19.960> superet<00:19:20.679> of<00:19:20.840> zero<00:19:21.520> knowledge 00:19:23.070 --> 00:19:23.080 align:start position:0% um a superet of zero knowledge 00:19:23.080 --> 00:19:26.830 align:start position:0% um a superet of zero knowledge um<00:19:24.080> um<00:19:24.480> so<00:19:24.760> it<00:19:24.880> is<00:19:25.039> a<00:19:25.240> way<00:19:25.440> for 00:19:26.830 --> 00:19:26.840 align:start position:0% um um so it is a way for 00:19:26.840 --> 00:19:31.029 align:start position:0% um um so it is a way for multiple<00:19:27.840> um<00:19:28.320> parties<00:19:29.159> to<00:19:29.559> jointly<00:19:30.080> compute<00:19:30.840> a 00:19:31.029 --> 00:19:31.039 align:start position:0% multiple um parties to jointly compute a 00:19:31.039 --> 00:19:34.470 align:start position:0% multiple um parties to jointly compute a function<00:19:31.799> over<00:19:32.120> secret<00:19:32.559> inputs<00:19:33.559> so<00:19:34.159> yeah<00:19:34.320> I 00:19:34.470 --> 00:19:34.480 align:start position:0% function over secret inputs so yeah I 00:19:34.480 --> 00:19:38.630 align:start position:0% function over secret inputs so yeah I put<00:19:34.799> this<00:19:35.280> visual<00:19:35.760> here<00:19:36.440> to<00:19:36.679> show<00:19:37.039> that<00:19:37.640> um 00:19:38.630 --> 00:19:38.640 align:start position:0% put this visual here to show that um 00:19:38.640 --> 00:19:40.710 align:start position:0% put this visual here to show that um well<00:19:38.919> once<00:19:39.200> again<00:19:39.480> we<00:19:39.640> have<00:19:39.799> an<00:19:40.039> arbitrary 00:19:40.710 --> 00:19:40.720 align:start position:0% well once again we have an arbitrary 00:19:40.720 --> 00:19:43.909 align:start position:0% well once again we have an arbitrary function<00:19:41.720> um<00:19:41.919> but<00:19:42.159> what's<00:19:42.480> changed<00:19:43.120> is<00:19:43.360> that 00:19:43.909 --> 00:19:43.919 align:start position:0% function um but what's changed is that 00:19:43.919 --> 00:19:46.390 align:start position:0% function um but what's changed is that the<00:19:44.320> the<00:19:44.440> witness<00:19:44.960> the<00:19:45.159> secret<00:19:45.480> input<00:19:45.960> is<00:19:46.120> now 00:19:46.390 --> 00:19:46.400 align:start position:0% the the witness the secret input is now 00:19:46.400 --> 00:19:50.510 align:start position:0% the the witness the secret input is now split<00:19:47.240> um<00:19:47.440> across<00:19:47.919> multiple 00:19:50.510 --> 00:19:50.520 align:start position:0% 00:19:50.520 --> 00:19:55.149 align:start position:0% parties<00:19:51.520> um<00:19:52.080> and<00:19:53.080> we<00:19:53.280> can<00:19:53.679> actually<00:19:54.200> combine 00:19:55.149 --> 00:19:55.159 align:start position:0% parties um and we can actually combine 00:19:55.159 --> 00:19:57.630 align:start position:0% parties um and we can actually combine um<00:19:55.400> multi-party<00:19:56.039> computation<00:19:57.000> with<00:19:57.240> Zer 00:19:57.630 --> 00:19:57.640 align:start position:0% um multi-party computation with Zer 00:19:57.640 --> 00:19:59.270 align:start position:0% um multi-party computation with Zer knowledge<00:19:58.159> proofs 00:19:59.270 --> 00:19:59.280 align:start position:0% knowledge proofs 00:19:59.280 --> 00:20:04.470 align:start position:0% knowledge proofs um<00:20:00.120> and<00:20:00.400> get<00:20:00.919> um<00:20:01.200> publicly<00:20:01.799> auditable<00:20:02.960> NPC<00:20:03.960> so 00:20:04.470 --> 00:20:04.480 align:start position:0% um and get um publicly auditable NPC so 00:20:04.480 --> 00:20:08.190 align:start position:0% um and get um publicly auditable NPC so we<00:20:04.640> can<00:20:05.000> have<00:20:05.679> both<00:20:05.919> an<00:20:06.120> MPC<00:20:07.080> and<00:20:07.360> a<00:20:07.520> su<00:20:07.880> sync 00:20:08.190 --> 00:20:08.200 align:start position:0% we can have both an MPC and a su sync 00:20:08.200 --> 00:20:10.870 align:start position:0% we can have both an MPC and a su sync certificate<00:20:09.159> that<00:20:09.520> the<00:20:09.640> NPC<00:20:10.120> was<00:20:10.240> done 00:20:10.870 --> 00:20:10.880 align:start position:0% certificate that the NPC was done 00:20:10.880 --> 00:20:14.190 align:start position:0% certificate that the NPC was done correctly<00:20:11.880> um<00:20:12.360> and<00:20:12.640> you<00:20:12.799> can<00:20:13.640> Yeah<00:20:13.919> we 00:20:14.190 --> 00:20:14.200 align:start position:0% correctly um and you can Yeah we 00:20:14.200 --> 00:20:17.590 align:start position:0% correctly um and you can Yeah we actually<00:20:14.480> have<00:20:14.679> a<00:20:14.799> bunch<00:20:15.039> of<00:20:15.240> MPC<00:20:15.840> talks<00:20:16.520> um<00:20:17.360> at 00:20:17.590 --> 00:20:17.600 align:start position:0% actually have a bunch of MPC talks um at 00:20:17.600 --> 00:20:20.950 align:start position:0% actually have a bunch of MPC talks um at this<00:20:17.840> conference<00:20:18.840> so<00:20:19.159> yeah<00:20:19.559> this<00:20:19.760> ZK<00:20:20.159> MPC<00:20:20.720> is 00:20:20.950 --> 00:20:20.960 align:start position:0% this conference so yeah this ZK MPC is 00:20:20.960 --> 00:20:23.029 align:start position:0% this conference so yeah this ZK MPC is what<00:20:21.559> I<00:20:21.679> was<00:20:21.880> talking<00:20:22.200> about<00:20:22.679> publicly 00:20:23.029 --> 00:20:23.039 align:start position:0% what I was talking about publicly 00:20:23.039 --> 00:20:24.950 align:start position:0% what I was talking about publicly auditable 00:20:24.950 --> 00:20:24.960 align:start position:0% auditable 00:20:24.960 --> 00:20:27.310 align:start position:0% auditable MPC 00:20:27.310 --> 00:20:27.320 align:start position:0% MPC 00:20:27.320 --> 00:20:31.310 align:start position:0% MPC um<00:20:28.320> yeah<00:20:28.480> so<00:20:28.679> so<00:20:29.000> this<00:20:29.120> is<00:20:29.200> a<00:20:29.480> project<00:20:30.039> that<00:20:30.720> uh 00:20:31.310 --> 00:20:31.320 align:start position:0% um yeah so so this is a project that uh 00:20:31.320 --> 00:20:34.070 align:start position:0% um yeah so so this is a project that uh our<00:20:31.880> colleague<00:20:32.400> Andrew<00:20:32.880> wrote<00:20:33.480> so<00:20:33.679> it's<00:20:33.799> a 00:20:34.070 --> 00:20:34.080 align:start position:0% our colleague Andrew wrote so it's a 00:20:34.080 --> 00:20:36.630 align:start position:0% our colleague Andrew wrote so it's a game<00:20:34.600> where<00:20:34.720> you<00:20:34.799> can<00:20:35.000> play<00:20:35.760> Rock<00:20:36.159> a<00:20:36.240> modified 00:20:36.630 --> 00:20:36.640 align:start position:0% game where you can play Rock a modified 00:20:36.640 --> 00:20:39.390 align:start position:0% game where you can play Rock a modified version<00:20:36.880> of<00:20:36.960> rock<00:20:37.159> paper<00:20:37.400> scissors<00:20:38.120> over<00:20:38.400> NPC 00:20:39.390 --> 00:20:39.400 align:start position:0% version of rock paper scissors over NPC 00:20:39.400 --> 00:20:41.590 align:start position:0% version of rock paper scissors over NPC so<00:20:39.760> only<00:20:40.120> you<00:20:40.679> and<00:20:41.039> the<00:20:41.200> person<00:20:41.440> you're 00:20:41.590 --> 00:20:41.600 align:start position:0% so only you and the person you're 00:20:41.600 --> 00:20:42.830 align:start position:0% so only you and the person you're playing<00:20:41.919> with<00:20:42.080> are<00:20:42.240> like<00:20:42.480> actually 00:20:42.830 --> 00:20:42.840 align:start position:0% playing with are like actually 00:20:42.840 --> 00:20:44.510 align:start position:0% playing with are like actually participating<00:20:43.840> there's<00:20:44.000> no<00:20:44.200> like 00:20:44.510 --> 00:20:44.520 align:start position:0% participating there's no like 00:20:44.520 --> 00:20:47.789 align:start position:0% participating there's no like intermediate<00:20:45.520> party<00:20:46.400> and<00:20:46.559> you<00:20:46.679> can<00:20:46.919> trust 00:20:47.789 --> 00:20:47.799 align:start position:0% intermediate party and you can trust 00:20:47.799 --> 00:20:53.230 align:start position:0% intermediate party and you can trust that<00:20:48.039> each<00:20:48.159> other<00:20:48.400> aren't<00:20:48.799> cheating<00:20:49.799> so<00:20:50.159> fun 00:20:53.230 --> 00:20:53.240 align:start position:0% 00:20:53.240 --> 00:20:57.029 align:start position:0% game<00:20:54.240> right<00:20:55.000> yeah<00:20:55.400> these<00:20:55.559> are<00:20:56.320> some<00:20:56.679> other 00:20:57.029 --> 00:20:57.039 align:start position:0% game right yeah these are some other 00:20:57.039 --> 00:21:00.470 align:start position:0% game right yeah these are some other applications<00:20:57.559> of<00:20:57.679> NPC<00:20:58.320> that<00:20:58.640> you<00:20:58.720> can<00:20:58.960> hear 00:21:00.470 --> 00:21:00.480 align:start position:0% applications of NPC that you can hear 00:21:00.480 --> 00:21:04.789 align:start position:0% applications of NPC that you can hear about<00:21:01.480> so<00:21:01.840> the<00:21:02.080> final<00:21:02.720> sort<00:21:03.320> of<00:21:04.320> I<00:21:04.400> think<00:21:04.600> the 00:21:04.789 --> 00:21:04.799 align:start position:0% about so the final sort of I think the 00:21:04.799 --> 00:21:07.830 align:start position:0% about so the final sort of I think the most<00:21:05.120> heavyweight<00:21:06.080> um<00:21:07.000> um<00:21:07.159> primitive<00:21:07.600> in 00:21:07.830 --> 00:21:07.840 align:start position:0% most heavyweight um um primitive in 00:21:07.840 --> 00:21:09.590 align:start position:0% most heavyweight um um primitive in programmable<00:21:08.480> cryptography<00:21:09.120> is<00:21:09.320> fully 00:21:09.590 --> 00:21:09.600 align:start position:0% programmable cryptography is fully 00:21:09.600 --> 00:21:10.789 align:start position:0% programmable cryptography is fully homomorphic 00:21:10.789 --> 00:21:10.799 align:start position:0% homomorphic 00:21:10.799 --> 00:21:13.710 align:start position:0% homomorphic encryption<00:21:11.799> um<00:21:12.120> and<00:21:12.279> the<00:21:12.440> API<00:21:12.880> of<00:21:13.080> this<00:21:13.320> looks 00:21:13.710 --> 00:21:13.720 align:start position:0% encryption um and the API of this looks 00:21:13.720 --> 00:21:18.310 align:start position:0% encryption um and the API of this looks pretty<00:21:14.080> different<00:21:15.080> so<00:21:15.679> in<00:21:16.000> this<00:21:16.360> case 00:21:18.310 --> 00:21:18.320 align:start position:0% pretty different so in this case 00:21:18.320 --> 00:21:23.830 align:start position:0% pretty different so in this case um<00:21:19.320> um<00:21:20.080> the<00:21:20.600> holder<00:21:21.600> um<00:21:21.960> of<00:21:22.120> the<00:21:22.279> secret<00:21:22.840> data 00:21:23.830 --> 00:21:23.840 align:start position:0% um um the holder um of the secret data 00:21:23.840 --> 00:21:27.630 align:start position:0% um um the holder um of the secret data um<00:21:24.320> en<00:21:24.640> Crypts<00:21:25.039> it<00:21:25.880> homomorphically<00:21:26.880> so<00:21:27.159> it 00:21:27.630 --> 00:21:27.640 align:start position:0% um en Crypts it homomorphically so it 00:21:27.640 --> 00:21:29.110 align:start position:0% um en Crypts it homomorphically so it transforms<00:21:28.279> it 00:21:29.110 --> 00:21:29.120 align:start position:0% transforms it 00:21:29.120 --> 00:21:30.149 align:start position:0% transforms it um 00:21:30.149 --> 00:21:30.159 align:start position:0% um 00:21:30.159 --> 00:21:35.350 align:start position:0% um into<00:21:31.159> this<00:21:31.400> sort<00:21:31.640> of<00:21:32.159> um<00:21:32.600> Cipher<00:21:33.200> text<00:21:34.200> um<00:21:34.480> that 00:21:35.350 --> 00:21:35.360 align:start position:0% into this sort of um Cipher text um that 00:21:35.360 --> 00:21:38.350 align:start position:0% into this sort of um Cipher text um that preserves<00:21:36.000> the<00:21:36.240> privacy<00:21:36.679> of<00:21:36.840> the<00:21:37.000> data<00:21:37.760> but 00:21:38.350 --> 00:21:38.360 align:start position:0% preserves the privacy of the data but 00:21:38.360 --> 00:21:40.830 align:start position:0% preserves the privacy of the data but also<00:21:38.679> preserves<00:21:39.200> the<00:21:39.400> structure<00:21:39.840> of<00:21:40.000> it<00:21:40.559> such 00:21:40.830 --> 00:21:40.840 align:start position:0% also preserves the structure of it such 00:21:40.840 --> 00:21:44.190 align:start position:0% also preserves the structure of it such that<00:21:41.279> any<00:21:41.679> party<00:21:42.520> um<00:21:42.760> Can<00:21:43.360> Transform<00:21:43.960> it 00:21:44.190 --> 00:21:44.200 align:start position:0% that any party um Can Transform it 00:21:44.200 --> 00:21:46.950 align:start position:0% that any party um Can Transform it according<00:21:44.559> to<00:21:44.799> any<00:21:45.159> arbitrary<00:21:45.799> function<00:21:46.679> so 00:21:46.950 --> 00:21:46.960 align:start position:0% according to any arbitrary function so 00:21:46.960 --> 00:21:50.470 align:start position:0% according to any arbitrary function so once<00:21:47.200> again<00:21:47.640> this<00:21:47.760> is<00:21:47.919> fully<00:21:48.559> programmable<00:21:49.559> um 00:21:50.470 --> 00:21:50.480 align:start position:0% once again this is fully programmable um 00:21:50.480 --> 00:21:53.750 align:start position:0% once again this is fully programmable um but<00:21:51.480> all<00:21:51.640> the<00:21:51.840> work<00:21:52.080> is<00:21:52.320> kind<00:21:52.480> of<00:21:53.120> um 00:21:53.750 --> 00:21:53.760 align:start position:0% but all the work is kind of um 00:21:53.760 --> 00:21:56.950 align:start position:0% but all the work is kind of um outsourced<00:21:54.760> um<00:21:55.000> to<00:21:55.600> this<00:21:55.840> arbitrary<00:21:56.480> third 00:21:56.950 --> 00:21:56.960 align:start position:0% outsourced um to this arbitrary third 00:21:56.960 --> 00:22:01.549 align:start position:0% outsourced um to this arbitrary third party<00:21:57.960> um<00:21:58.600> so<00:21:58.960> this<00:21:59.159> third<00:21:59.480> party<00:22:00.320> performs<00:22:01.320> uh 00:22:01.549 --> 00:22:01.559 align:start position:0% party um so this third party performs uh 00:22:01.559 --> 00:22:04.630 align:start position:0% party um so this third party performs uh an<00:22:01.720> arbitrary<00:22:02.360> computation<00:22:03.360> and<00:22:03.559> then 00:22:04.630 --> 00:22:04.640 align:start position:0% an arbitrary computation and then 00:22:04.640 --> 00:22:06.230 align:start position:0% an arbitrary computation and then returns 00:22:06.230 --> 00:22:06.240 align:start position:0% returns 00:22:06.240 --> 00:22:09.149 align:start position:0% returns um<00:22:07.240> uh<00:22:07.760> so<00:22:08.000> this<00:22:08.159> third<00:22:08.400> party<00:22:08.640> is<00:22:08.760> working 00:22:09.149 --> 00:22:09.159 align:start position:0% um uh so this third party is working 00:22:09.159 --> 00:22:13.070 align:start position:0% um uh so this third party is working completely<00:22:10.039> blindly<00:22:11.039> um<00:22:11.720> and<00:22:12.039> ends<00:22:12.360> up<00:22:12.679> only 00:22:13.070 --> 00:22:13.080 align:start position:0% completely blindly um and ends up only 00:22:13.080 --> 00:22:16.870 align:start position:0% completely blindly um and ends up only with<00:22:13.480> a<00:22:13.679> cipher<00:22:14.080> text<00:22:14.360> form<00:22:14.880> of<00:22:15.039> the<00:22:15.480> output<00:22:16.480> um 00:22:16.870 --> 00:22:16.880 align:start position:0% with a cipher text form of the output um 00:22:16.880 --> 00:22:18.909 align:start position:0% with a cipher text form of the output um and<00:22:17.000> the<00:22:17.159> point<00:22:17.440> here<00:22:17.640> is<00:22:17.840> that<00:22:18.240> only<00:22:18.799> the 00:22:18.909 --> 00:22:18.919 align:start position:0% and the point here is that only the 00:22:18.919 --> 00:22:21.950 align:start position:0% and the point here is that only the holder<00:22:19.320> of<00:22:19.440> the<00:22:19.600> secret<00:22:20.120> key<00:22:21.120> um<00:22:21.279> is<00:22:21.480> able<00:22:21.760> to 00:22:21.950 --> 00:22:21.960 align:start position:0% holder of the secret key um is able to 00:22:21.960 --> 00:22:24.590 align:start position:0% holder of the secret key um is able to decrypt<00:22:22.880> the<00:22:23.039> output<00:22:23.559> to<00:22:23.799> some<00:22:24.080> sensible 00:22:24.590 --> 00:22:24.600 align:start position:0% decrypt the output to some sensible 00:22:24.600 --> 00:22:26.990 align:start position:0% decrypt the output to some sensible plain<00:22:25.360> text 00:22:26.990 --> 00:22:27.000 align:start position:0% plain text 00:22:27.000 --> 00:22:31.110 align:start position:0% plain text um<00:22:28.000> and<00:22:28.960> yeah<00:22:29.240> there's<00:22:29.640> actually<00:22:30.039> been<00:22:30.960> a 00:22:31.110 --> 00:22:31.120 align:start position:0% um and yeah there's actually been a 00:22:31.120 --> 00:22:36.350 align:start position:0% um and yeah there's actually been a bunch<00:22:31.360> of<00:22:31.520> cool<00:22:31.919> experiments<00:22:32.919> using<00:22:33.880> FHA<00:22:35.360> um 00:22:36.350 --> 00:22:36.360 align:start position:0% bunch of cool experiments using FHA um 00:22:36.360 --> 00:22:39.950 align:start position:0% bunch of cool experiments using FHA um by<00:22:36.840> cursive<00:22:37.840> so<00:22:38.320> you<00:22:38.440> can<00:22:38.640> check<00:22:38.960> that<00:22:39.120> out<00:22:39.799> uh 00:22:39.950 --> 00:22:39.960 align:start position:0% by cursive so you can check that out uh 00:22:39.960 --> 00:22:45.430 align:start position:0% by cursive so you can check that out uh no<00:22:40.440> yeah<00:22:40.880> that's<00:22:41.159> already<00:22:41.520> over<00:22:42.080> as<00:22:42.600> well<00:22:43.760> um 00:22:45.430 --> 00:22:45.440 align:start position:0% no yeah that's already over as well um 00:22:45.440 --> 00:22:49.510 align:start position:0% no yeah that's already over as well um so<00:22:46.440> yeah<00:22:46.640> I<00:22:46.760> think<00:22:47.000> that's<00:22:47.279> all<00:22:47.480> we<00:22:47.919> have<00:22:48.919> and 00:22:49.510 --> 00:22:49.520 align:start position:0% so yeah I think that's all we have and 00:22:49.520 --> 00:22:53.310 align:start position:0% so yeah I think that's all we have and do<00:22:49.679> we<00:22:49.840> have<00:22:50.000> time<00:22:50.120> for 00:22:53.310 --> 00:22:53.320 align:start position:0% 00:22:53.320 --> 00:22:55.149 align:start position:0% questions 00:22:55.149 --> 00:22:55.159 align:start position:0% questions 00:22:55.159 --> 00:22:57.990 align:start position:0% questions questions<00:22:56.159> thank<00:22:56.400> you<00:22:56.799> first<00:22:57.360> maybe<00:22:57.720> give<00:22:57.880> a 00:22:57.990 --> 00:22:58.000 align:start position:0% questions thank you first maybe give a 00:22:58.000 --> 00:22:59.470 align:start position:0% questions thank you first maybe give a round<00:22:58.159> of<00:22:58.240> app<00:22:58.559> off<00:22:58.679> to<00:22:58.760> the<00:22:58.840> speakers<00:22:59.159> for<00:22:59.360> a 00:22:59.470 --> 00:22:59.480 align:start position:0% round of app off to the speakers for a 00:22:59.480 --> 00:23:01.430 align:start position:0% round of app off to the speakers for a very<00:22:59.720> nice<00:22:59.919> overview<00:23:00.360> of 00:23:01.430 --> 00:23:01.440 align:start position:0% very nice overview of 00:23:01.440 --> 00:23:04.190 align:start position:0% very nice overview of cryptography<00:23:02.440> um<00:23:02.760> so<00:23:03.279> it's<00:23:03.440> a<00:23:03.679> little<00:23:03.960> bit 00:23:04.190 --> 00:23:04.200 align:start position:0% cryptography um so it's a little bit 00:23:04.200 --> 00:23:06.070 align:start position:0% cryptography um so it's a little bit over<00:23:04.440> time<00:23:04.640> so<00:23:04.880> we<00:23:05.039> have<00:23:05.240> maybe<00:23:05.520> time<00:23:05.679> for<00:23:05.880> one 00:23:06.070 --> 00:23:06.080 align:start position:0% over time so we have maybe time for one 00:23:06.080 --> 00:23:07.549 align:start position:0% over time so we have maybe time for one question<00:23:06.480> but<00:23:06.640> I<00:23:06.720> think<00:23:06.880> one<00:23:07.039> that<00:23:07.200> came<00:23:07.360> in 00:23:07.549 --> 00:23:07.559 align:start position:0% question but I think one that came in 00:23:07.559 --> 00:23:09.350 align:start position:0% question but I think one that came in very<00:23:07.760> early<00:23:08.039> and<00:23:08.159> was<00:23:08.320> uploaded<00:23:08.799> a<00:23:08.880> lot<00:23:09.159> very 00:23:09.350 --> 00:23:09.360 align:start position:0% very early and was uploaded a lot very 00:23:09.360 --> 00:23:11.789 align:start position:0% very early and was uploaded a lot very quickly<00:23:10.159> was<00:23:10.559> what<00:23:10.679> are<00:23:10.840> some<00:23:11.080> good<00:23:11.279> resources 00:23:11.789 --> 00:23:11.799 align:start position:0% quickly was what are some good resources 00:23:11.799 --> 00:23:13.830 align:start position:0% quickly was what are some good resources to<00:23:12.000> dive<00:23:12.279> deeper<00:23:12.640> into<00:23:12.880> formal<00:23:13.240> cryptography 00:23:13.830 --> 00:23:13.840 align:start position:0% to dive deeper into formal cryptography 00:23:13.840 --> 00:23:15.710 align:start position:0% to dive deeper into formal cryptography as<00:23:13.960> someone<00:23:14.200> with<00:23:14.400> no<00:23:14.720> prior 00:23:15.710 --> 00:23:15.720 align:start position:0% as someone with no prior 00:23:15.720 --> 00:23:19.950 align:start position:0% as someone with no prior experience<00:23:16.720> so<00:23:17.200> there<00:23:17.600> is<00:23:18.320> a<00:23:19.039> elliptic<00:23:19.559> curve 00:23:19.950 --> 00:23:19.960 align:start position:0% experience so there is a elliptic curve 00:23:19.960 --> 00:23:23.470 align:start position:0% experience so there is a elliptic curve cryptography<00:23:20.799> primer<00:23:21.679> by<00:23:22.200> Cloud<00:23:22.559> flare<00:23:23.360> that 00:23:23.470 --> 00:23:23.480 align:start position:0% cryptography primer by Cloud flare that 00:23:23.480 --> 00:23:26.470 align:start position:0% cryptography primer by Cloud flare that I<00:23:23.600> would<00:23:24.159> recommend<00:23:25.159> um 00:23:26.470 --> 00:23:26.480 align:start position:0% I would recommend um 00:23:26.480 --> 00:23:30.310 align:start position:0% I would recommend um it's<00:23:27.480> a<00:23:27.600> little<00:23:27.880> long<00:23:28.600> but<00:23:28.760> it's<00:23:29.320> very 00:23:30.310 --> 00:23:30.320 align:start position:0% it's a little long but it's very 00:23:30.320 --> 00:23:31.669 align:start position:0% it's a little long but it's very understandable<00:23:30.840> like<00:23:30.960> you<00:23:31.080> can<00:23:31.279> you<00:23:31.360> can<00:23:31.520> get 00:23:31.669 --> 00:23:31.679 align:start position:0% understandable like you can you can get 00:23:31.679 --> 00:23:34.029 align:start position:0% understandable like you can you can get through<00:23:31.840> that<00:23:32.039> pretty<00:23:32.279> well<00:23:33.200> um<00:23:33.480> three<00:23:33.760> blue 00:23:34.029 --> 00:23:34.039 align:start position:0% through that pretty well um three blue 00:23:34.039 --> 00:23:36.470 align:start position:0% through that pretty well um three blue one<00:23:34.320> brown<00:23:34.919> did<00:23:35.080> a<00:23:35.240> video<00:23:35.640> on<00:23:35.840> how<00:23:36.039> Bitcoin 00:23:36.470 --> 00:23:36.480 align:start position:0% one brown did a video on how Bitcoin 00:23:36.480 --> 00:23:38.470 align:start position:0% one brown did a video on how Bitcoin works<00:23:36.760> that<00:23:36.919> he<00:23:37.039> Dives<00:23:37.400> deep<00:23:38.080> and<00:23:38.200> it's<00:23:38.360> like 00:23:38.470 --> 00:23:38.480 align:start position:0% works that he Dives deep and it's like 00:23:38.480 --> 00:23:41.230 align:start position:0% works that he Dives deep and it's like 20<00:23:38.760> minutes<00:23:39.080> and<00:23:39.279> he<00:23:39.600> he<00:23:39.840> goes<00:23:40.120> over<00:23:41.080> uh 00:23:41.230 --> 00:23:41.240 align:start position:0% 20 minutes and he he goes over uh 00:23:41.240 --> 00:23:45.789 align:start position:0% 20 minutes and he he goes over uh hashing<00:23:41.760> and<00:23:41.919> signing<00:23:42.720> pretty<00:23:43.320> deeply<00:23:44.799> and 00:23:45.789 --> 00:23:45.799 align:start position:0% hashing and signing pretty deeply and 00:23:45.799 --> 00:23:47.190 align:start position:0% hashing and signing pretty deeply and yeah<00:23:46.120> I<00:23:46.200> think<00:23:46.320> those<00:23:46.440> are<00:23:46.600> probably<00:23:46.799> two<00:23:46.960> good 00:23:47.190 --> 00:23:47.200 align:start position:0% yeah I think those are probably two good 00:23:47.200 --> 00:23:50.230 align:start position:0% yeah I think those are probably two good options<00:23:48.039> oh<00:23:48.440> also<00:23:49.039> there's<00:23:49.320> this<00:23:49.600> legendary 00:23:50.230 --> 00:23:50.240 align:start position:0% options oh also there's this legendary 00:23:50.240 --> 00:23:52.830 align:start position:0% options oh also there's this legendary cryptographer<00:23:50.960> Dan<00:23:51.279> Bonet<00:23:52.000> who's<00:23:52.240> done<00:23:52.640> a 00:23:52.830 --> 00:23:52.840 align:start position:0% cryptographer Dan Bonet who's done a 00:23:52.840 --> 00:23:56.789 align:start position:0% cryptographer Dan Bonet who's done a bunch<00:23:53.080> of<00:23:53.440> open<00:23:54.080> courseware<00:23:55.080> um<00:23:55.480> courses<00:23:56.480> with 00:23:56.789 --> 00:23:56.799 align:start position:0% bunch of open courseware um courses with 00:23:56.799 --> 00:24:00.350 align:start position:0% bunch of open courseware um courses with like<00:23:57.159> videos<00:23:57.960> and<00:23:58.440> course<00:23:59.039> materials<00:24:00.039> um<00:24:00.279> I 00:24:00.350 --> 00:24:00.360 align:start position:0% like videos and course materials um I 00:24:00.360 --> 00:24:03.590 align:start position:0% like videos and course materials um I think<00:24:00.559> it's<00:24:00.720> on<00:24:00.960> corsera<00:24:01.919> actually<00:24:02.840> so<00:24:03.279> I 00:24:03.590 --> 00:24:03.600 align:start position:0% think it's on corsera actually so I 00:24:03.600 --> 00:24:05.870 align:start position:0% think it's on corsera actually so I highly<00:24:03.919> highly<00:24:04.240> recommend<00:24:05.120> that 00:24:05.870 --> 00:24:05.880 align:start position:0% highly highly recommend that 00:24:05.880 --> 00:24:08.430 align:start position:0% highly highly recommend that one<00:24:06.880> cool<00:24:07.120> I<00:24:07.240> maybe<00:24:07.559> watching<00:24:07.840> back<00:24:08.039> the<00:24:08.159> talks 00:24:08.430 --> 00:24:08.440 align:start position:0% one cool I maybe watching back the talks 00:24:08.440 --> 00:24:09.990 align:start position:0% one cool I maybe watching back the talks that<00:24:08.559> you<00:24:08.679> linked<00:24:09.039> as<00:24:09.159> well<00:24:09.400> so<00:24:09.640> watching<00:24:09.880> the 00:24:09.990 --> 00:24:10.000 align:start position:0% that you linked as well so watching the 00:24:10.000 --> 00:24:12.470 align:start position:0% that you linked as well so watching the videos<00:24:10.440> back<00:24:11.200> very<00:24:11.440> nice<00:24:11.799> so<00:24:12.080> I<00:24:12.159> think<00:24:12.320> we're 00:24:12.470 --> 00:24:12.480 align:start position:0% videos back very nice so I think we're 00:24:12.480 --> 00:24:14.110 align:start position:0% videos back very nice so I think we're at<00:24:12.679> time<00:24:12.919> we<00:24:13.000> have<00:24:13.120> a<00:24:13.200> few<00:24:13.360> minutes<00:24:13.640> to<00:24:13.840> switch 00:24:14.110 --> 00:24:14.120 align:start position:0% at time we have a few minutes to switch 00:24:14.120 --> 00:24:15.909 align:start position:0% at time we have a few minutes to switch over<00:24:14.400> for<00:24:14.520> the<00:24:14.640> next<00:24:14.799> session<00:24:15.240> but<00:24:15.559> yeah<00:24:15.720> we' 00:24:15.909 --> 00:24:15.919 align:start position:0% over for the next session but yeah we' 00:24:15.919 --> 00:24:17.549 align:start position:0% over for the next session but yeah we' like<00:24:16.039> to<00:24:16.159> thank<00:24:16.320> the<00:24:16.400> speakers<00:24:16.840> again<00:24:17.320> and<00:24:17.440> we 00:24:17.549 --> 00:24:17.559 align:start position:0% like to thank the speakers again and we 00:24:17.559 --> 00:24:18.870 align:start position:0% like to thank the speakers again and we see<00:24:17.760> you 00:24:18.870 --> 00:24:18.880 align:start position:0% see you 00:24:18.880 --> 00:24:21.990 align:start position:0% see you soon<00:24:19.880> so<00:24:20.600> uh<00:24:20.760> we'll<00:24:20.919> be<00:24:21.120> back<00:24:21.279> in<00:24:21.400> four<00:24:21.640> minutes 00:24:21.990 --> 00:24:22.000 align:start position:0% soon so uh we'll be back in four minutes 00:24:22.000 --> 00:24:23.870 align:start position:0% soon so uh we'll be back in four minutes but<00:24:22.120> I<00:24:22.200> was<00:24:22.400> just<00:24:22.600> advised<00:24:23.000> to<00:24:23.120> say<00:24:23.720> and 00:24:23.870 --> 00:24:23.880 align:start position:0% but I was just advised to say and 00:24:23.880 --> 00:24:25.430 align:start position:0% but I was just advised to say and there's<00:24:24.080> quite<00:24:24.200> a<00:24:24.320> lot<00:24:24.440> of<00:24:24.559> cans<00:24:25.000> and<00:24:25.200> stuff 00:24:25.430 --> 00:24:25.440 align:start position:0% there's quite a lot of cans and stuff 00:24:25.440 --> 00:24:28.039 align:start position:0% there's quite a lot of cans and stuff left<00:24:25.640> around