WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.470 align:start position:0% [Applause] 00:00:12.470 --> 00:00:12.480 align:start position:0% 00:00:12.480 --> 00:00:18.180 align:start position:0% so<00:00:13.480> they<00:00:14.170> sing<00:00:14.500> along<00:00:14.770> I<00:00:15.490> do<00:00:16.680> 1910<00:00:17.680> foundation 00:00:18.180 --> 00:00:18.190 align:start position:0% so they sing along I do 1910 foundation 00:00:18.190 --> 00:00:21.660 align:start position:0% so they sing along I do 1910 foundation of<00:00:18.460> advocacy<00:00:18.940> and<00:00:19.420> large<00:00:19.930> applications<00:00:20.670> and 00:00:21.660 --> 00:00:21.670 align:start position:0% of advocacy and large applications and 00:00:21.670 --> 00:00:24.000 align:start position:0% of advocacy and large applications and today<00:00:22.360> I<00:00:22.390> tested<00:00:22.660> myself<00:00:22.990> on<00:00:23.350> Sunday<00:00:23.830> night 00:00:24.000 --> 00:00:24.010 align:start position:0% today I tested myself on Sunday night 00:00:24.010 --> 00:00:26.480 align:start position:0% today I tested myself on Sunday night working<00:00:24.430> on<00:00:24.490> our<00:00:24.730> past<00:00:24.939> two<00:00:25.090> weeks<00:00:25.320> in 00:00:26.480 --> 00:00:26.490 align:start position:0% working on our past two weeks in 00:00:26.490 --> 00:00:30.300 align:start position:0% working on our past two weeks in collaboration<00:00:27.490> with<00:00:28.439> and<00:00:29.439> then<00:00:29.619> Steve<00:00:30.009> that's 00:00:30.300 --> 00:00:30.310 align:start position:0% collaboration with and then Steve that's 00:00:30.310 --> 00:00:32.280 align:start position:0% collaboration with and then Steve that's Patricia<00:00:30.759> right<00:00:30.970> there<00:00:31.150> thank<00:00:31.960> you<00:00:32.050> so<00:00:32.169> much 00:00:32.280 --> 00:00:32.290 align:start position:0% Patricia right there thank you so much 00:00:32.290 --> 00:00:45.210 align:start position:0% Patricia right there thank you so much Patricia<00:00:42.270> yeah<00:00:43.270> so<00:00:43.960> today<00:00:44.410> is<00:00:44.470> all<00:00:44.740> about<00:00:44.800> how 00:00:45.210 --> 00:00:45.220 align:start position:0% Patricia yeah so today is all about how 00:00:45.220 --> 00:00:48.930 align:start position:0% Patricia yeah so today is all about how we<00:00:45.280> use<00:00:45.570> these<00:00:46.650> proven<00:00:47.650> tennis<00:00:47.950> tokens<00:00:48.340> to 00:00:48.930 --> 00:00:48.940 align:start position:0% we use these proven tennis tokens to 00:00:48.940 --> 00:00:51.780 align:start position:0% we use these proven tennis tokens to enable<00:00:49.690> anonymous<00:00:50.470> voting<00:00:50.950> using 00:00:51.780 --> 00:00:51.790 align:start position:0% enable anonymous voting using 00:00:51.790 --> 00:00:54.510 align:start position:0% enable anonymous voting using civilization<00:00:52.450> and<00:00:52.660> I<00:00:53.560> am<00:00:53.860> finished<00:00:54.100> and<00:00:54.400> go 00:00:54.510 --> 00:00:54.520 align:start position:0% civilization and I am finished and go 00:00:54.520 --> 00:00:56.340 align:start position:0% civilization and I am finished and go into<00:00:54.670> the<00:00:54.850> demo<00:00:55.090> I'm<00:00:55.480> gonna<00:00:55.660> go<00:00:55.870> into<00:00:56.050> the<00:00:56.140> code 00:00:56.340 --> 00:00:56.350 align:start position:0% into the demo I'm gonna go into the code 00:00:56.350 --> 00:00:58.730 align:start position:0% into the demo I'm gonna go into the code I'm<00:00:57.040> gonna<00:00:57.250> explain<00:00:57.610> my<00:00:57.760> system<00:00:58.120> works<00:00:58.330> and 00:00:58.730 --> 00:00:58.740 align:start position:0% I'm gonna explain my system works and 00:00:58.740 --> 00:01:03.960 align:start position:0% I'm gonna explain my system works and talk<00:00:59.740> about<00:01:00.040> how<00:01:00.580> these<00:01:01.240> two<00:01:02.850> applications<00:01:03.850> of 00:01:03.960 --> 00:01:03.970 align:start position:0% talk about how these two applications of 00:01:03.970 --> 00:01:08.749 align:start position:0% talk about how these two applications of oxytane<00:01:04.689> technology<00:01:05.710> I'll<00:01:06.520> give<00:01:06.759> you<00:01:07.590> so 00:01:08.749 --> 00:01:08.759 align:start position:0% oxytane technology I'll give you so 00:01:08.759 --> 00:01:12.480 align:start position:0% oxytane technology I'll give you so that's<00:01:09.759> just<00:01:09.909> think<00:01:10.180> about<00:01:10.270> like<00:01:11.020> a<00:01:11.049> juicer<00:01:11.490> so 00:01:12.480 --> 00:01:12.490 align:start position:0% that's just think about like a juicer so 00:01:12.490 --> 00:01:15.240 align:start position:0% that's just think about like a juicer so let's<00:01:13.360> say<00:01:13.570> if<00:01:14.080> even<00:01:14.590> there's<00:01:14.710> always<00:01:14.950> drama 00:01:15.240 --> 00:01:15.250 align:start position:0% let's say if even there's always drama 00:01:15.250 --> 00:01:16.920 align:start position:0% let's say if even there's always drama that's<00:01:15.670> always<00:01:15.850> nice<00:01:16.090> and<00:01:16.150> controller<00:01:16.750> issue 00:01:16.920 --> 00:01:16.930 align:start position:0% that's always nice and controller issue 00:01:16.930 --> 00:01:19.710 align:start position:0% that's always nice and controller issue and<00:01:17.640> there's<00:01:18.640> always<00:01:18.790> like<00:01:19.000> like<00:01:19.300> Precious 00:01:19.710 --> 00:01:19.720 align:start position:0% and there's always like like Precious 00:01:19.720 --> 00:01:20.820 align:start position:0% and there's always like like Precious about<00:01:19.750> where<00:01:20.140> that<00:01:20.260> we're<00:01:20.350> going<00:01:20.440> to<00:01:20.530> include 00:01:20.820 --> 00:01:20.830 align:start position:0% about where that we're going to include 00:01:20.830 --> 00:01:22.950 align:start position:0% about where that we're going to include this<00:01:21.040> get<00:01:21.340> into<00:01:21.610> this<00:01:21.820> handful<00:01:22.300> all<00:01:22.659> right 00:01:22.950 --> 00:01:22.960 align:start position:0% this get into this handful all right 00:01:22.960 --> 00:01:25.380 align:start position:0% this get into this handful all right everyone<00:01:23.200> to<00:01:23.470> come<00:01:24.430> to<00:01:24.550> second<00:01:24.909> and<00:01:25.000> community 00:01:25.380 --> 00:01:25.390 align:start position:0% everyone to come to second and community 00:01:25.390 --> 00:01:28.200 align:start position:0% everyone to come to second and community consensus<00:01:25.930> and<00:01:26.110> some<00:01:26.320> issue<00:01:26.560> and<00:01:26.970> some<00:01:27.970> people 00:01:28.200 --> 00:01:28.210 align:start position:0% consensus and some issue and some people 00:01:28.210 --> 00:01:30.899 align:start position:0% consensus and some issue and some people say<00:01:28.360> okay<00:01:28.690> we<00:01:28.840> can<00:01:29.050> try<00:01:29.229> to<00:01:29.320> use<00:01:29.430> an<00:01:30.430> election 00:01:30.899 --> 00:01:30.909 align:start position:0% say okay we can try to use an election 00:01:30.909 --> 00:01:33.750 align:start position:0% say okay we can try to use an election or<00:01:31.090> moving<00:01:31.390> to<00:01:31.960> together<00:01:32.500> to<00:01:33.220> get<00:01:33.370> some<00:01:33.640> kind 00:01:33.750 --> 00:01:33.760 align:start position:0% or moving to together to get some kind 00:01:33.760 --> 00:01:37.230 align:start position:0% or moving to together to get some kind of<00:01:33.850> fight<00:01:34.470> resolution<00:01:35.470> but<00:01:36.190> that's<00:01:36.970> that's 00:01:37.230 --> 00:01:37.240 align:start position:0% of fight resolution but that's that's 00:01:37.240 --> 00:01:41.639 align:start position:0% of fight resolution but that's that's fine<00:01:37.450> in<00:01:37.570> candy<00:01:37.900> but<00:01:38.530> they're<00:01:38.710> too<00:01:38.860> far<00:01:39.070> sir 00:01:41.639 --> 00:01:41.649 align:start position:0% 00:01:41.649 --> 00:01:46.480 align:start position:0% you<00:01:42.649> can<00:01:43.070> vote<00:01:43.700> as<00:01:44.210> long<00:01:44.479> as<00:01:44.659> you<00:01:45.310> have<00:01:46.310> an 00:01:46.480 --> 00:01:46.490 align:start position:0% you can vote as long as you have an 00:01:46.490 --> 00:01:48.160 align:start position:0% you can vote as long as you have an address<00:01:46.759> which<00:01:47.090> is<00:01:47.119> not<00:01:47.360> so<00:01:47.479> good<00:01:47.659> because<00:01:47.810> it 00:01:48.160 --> 00:01:48.170 align:start position:0% address which is not so good because it 00:01:48.170 --> 00:01:52.630 align:start position:0% address which is not so good because it printed<00:01:48.590> us<00:01:48.740> free<00:01:49.009> and<00:01:49.330> if<00:01:50.330> you<00:01:50.530> vote<00:01:51.530> you<00:01:52.040> can 00:01:52.630 --> 00:01:52.640 align:start position:0% printed us free and if you vote you can 00:01:52.640 --> 00:01:54.969 align:start position:0% printed us free and if you vote you can find<00:01:53.119> out<00:01:53.240> other<00:01:53.479> people's<00:01:53.869> but<00:01:54.500> anybody<00:01:54.710> can 00:01:54.969 --> 00:01:54.979 align:start position:0% find out other people's but anybody can 00:01:54.979 --> 00:01:57.580 align:start position:0% find out other people's but anybody can see<00:01:55.189> all<00:01:55.880> more<00:01:56.119> than<00:01:56.149> one<00:01:56.479> and<00:01:56.720> there's<00:01:57.380> a<00:01:57.439> lack 00:01:57.580 --> 00:01:57.590 align:start position:0% see all more than one and there's a lack 00:01:57.590 --> 00:02:04.960 align:start position:0% see all more than one and there's a lack of<00:01:57.619> privacy<00:01:59.020> so<00:02:00.729> for<00:02:01.729> this<00:02:02.439> use<00:02:03.439> case<00:02:03.610> we<00:02:04.610> solve 00:02:04.960 --> 00:02:04.970 align:start position:0% of privacy so for this use case we solve 00:02:04.970 --> 00:02:07.149 align:start position:0% of privacy so for this use case we solve for<00:02:06.039> privacy 00:02:07.149 --> 00:02:07.159 align:start position:0% for privacy 00:02:07.159 --> 00:02:09.160 align:start position:0% for privacy using<00:02:07.549> 7/4<00:02:08.239> which<00:02:08.269> is<00:02:08.509> a<00:02:08.539> civil<00:02:08.840> knowledge 00:02:09.160 --> 00:02:09.170 align:start position:0% using 7/4 which is a civil knowledge 00:02:09.170 --> 00:02:11.140 align:start position:0% using 7/4 which is a civil knowledge signaling<00:02:09.830> gadget<00:02:10.160> which<00:02:10.340> I<00:02:10.459> explain<00:02:10.819> a<00:02:11.030> bit 00:02:11.140 --> 00:02:11.150 align:start position:0% signaling gadget which I explain a bit 00:02:11.150 --> 00:02:13.750 align:start position:0% signaling gadget which I explain a bit later<00:02:11.209> and<00:02:12.019> we<00:02:12.110> saw<00:02:12.319> identity<00:02:12.890> by<00:02:13.280> using<00:02:13.610> the 00:02:13.750 --> 00:02:13.760 align:start position:0% later and we saw identity by using the 00:02:13.760 --> 00:02:17.259 align:start position:0% later and we saw identity by using the Pope<00:02:13.940> of<00:02:14.150> it<00:02:14.330> because<00:02:14.660> for<00:02:14.989> example<00:02:15.110> a<00:02:16.269> bass 00:02:17.259 --> 00:02:17.269 align:start position:0% Pope of it because for example a bass 00:02:17.269 --> 00:02:19.289 align:start position:0% Pope of it because for example a bass part<00:02:17.510> everybody<00:02:18.319> present<00:02:18.739> Agri<00:02:18.920> tourism 00:02:19.289 --> 00:02:19.299 align:start position:0% part everybody present Agri tourism 00:02:19.299 --> 00:02:21.610 align:start position:0% part everybody present Agri tourism officials<00:02:20.299> team<00:02:20.569> with<00:02:21.019> hand<00:02:21.200> upon<00:02:21.470> these 00:02:21.610 --> 00:02:21.620 align:start position:0% officials team with hand upon these 00:02:21.620 --> 00:02:23.320 align:start position:0% officials team with hand upon these tokens<00:02:21.830> and<00:02:22.190> each<00:02:22.400> was<00:02:22.580> an<00:02:22.700> early<00:02:22.940> experiment 00:02:23.320 --> 00:02:23.330 align:start position:0% tokens and each was an early experiment 00:02:23.330 --> 00:02:25.180 align:start position:0% tokens and each was an early experiment we<00:02:24.140> will<00:02:24.200> make<00:02:24.410> it<00:02:24.530> available<00:02:24.650> to<00:02:25.010> your 00:02:25.180 --> 00:02:25.190 align:start position:0% we will make it available to your 00:02:25.190 --> 00:02:29.530 align:start position:0% we will make it available to your address<00:02:25.430> and<00:02:25.819> I<00:02:26.209> want<00:02:26.690> that<00:02:27.130> energy<00:02:28.269> the<00:02:29.269> DSD 00:02:29.530 --> 00:02:29.540 align:start position:0% address and I want that energy the DSD 00:02:29.540 --> 00:02:33.280 align:start position:0% address and I want that energy the DSD 71<00:02:30.230> token<00:02:30.709> which<00:02:31.510> proves<00:02:32.510> that<00:02:32.630> you<00:02:32.780> had<00:02:33.019> an 00:02:33.280 --> 00:02:33.290 align:start position:0% 71 token which proves that you had an 00:02:33.290 --> 00:02:36.370 align:start position:0% 71 token which proves that you had an event<00:02:33.620> and<00:02:34.130> you<00:02:34.280> could<00:02:34.840> combine<00:02:35.840> these<00:02:36.140> tokens 00:02:36.370 --> 00:02:36.380 align:start position:0% event and you could combine these tokens 00:02:36.380 --> 00:02:38.530 align:start position:0% event and you could combine these tokens and<00:02:36.680> say<00:02:36.830> that<00:02:36.980> I<00:02:37.069> said<00:02:37.310> at<00:02:37.519> your<00:02:38.060> house<00:02:38.299> a 00:02:38.530 --> 00:02:38.540 align:start position:0% and say that I said at your house a 00:02:38.540 --> 00:02:43.979 align:start position:0% and say that I said at your house a single<00:02:38.870> one<00:02:39.019> of<00:02:39.230> the<00:02:39.380> DEF<00:02:39.709> CON<00:02:39.860> fact<00:02:40.180> that<00:02:41.650> so 00:02:43.979 --> 00:02:43.989 align:start position:0% single one of the DEF CON fact that so 00:02:43.989 --> 00:02:49.899 align:start position:0% single one of the DEF CON fact that so we<00:02:45.819> combine<00:02:46.819> these<00:02:47.120> two<00:02:47.390> components<00:02:47.900> until<00:02:48.909> do 00:02:49.899 --> 00:02:49.909 align:start position:0% we combine these two components until do 00:02:49.909 --> 00:03:01.649 align:start position:0% we combine these two components until do a<00:02:50.049> very<00:02:51.049> similar<00:02:57.999> so<00:02:58.999> let's<00:02:59.180> do<00:02:59.299> a<00:02:59.329> demo 00:03:01.649 --> 00:03:01.659 align:start position:0% 00:03:01.659 --> 00:03:03.729 align:start position:0% everybody<00:03:02.659> is<00:03:02.780> on<00:03:02.959> the<00:03:03.049> laptop<00:03:03.409> and<00:03:03.560> you 00:03:03.729 --> 00:03:03.739 align:start position:0% everybody is on the laptop and you 00:03:03.739 --> 00:03:07.420 align:start position:0% everybody is on the laptop and you already<00:03:04.010> have<00:03:04.459> the<00:03:04.489> energy<00:03:05.799> mobility<00:03:06.799> I<00:03:07.069> will 00:03:07.420 --> 00:03:07.430 align:start position:0% already have the energy mobility I will 00:03:07.430 --> 00:03:09.069 align:start position:0% already have the energy mobility I will encourage<00:03:07.670> you<00:03:07.819> to<00:03:08.000> go<00:03:08.120> to<00:03:08.180> one<00:03:08.510> another<00:03:08.810> app 00:03:09.069 --> 00:03:09.079 align:start position:0% encourage you to go to one another app 00:03:09.079 --> 00:03:17.770 align:start position:0% encourage you to go to one another app is<00:03:09.950> a<00:03:10.099> main<00:03:10.310> happy<00:03:10.519> so<00:03:11.239> okay<00:03:12.049> mask<00:03:12.650> mask<00:03:15.219> one<00:03:16.780> on 00:03:17.770 --> 00:03:17.780 align:start position:0% is a main happy so okay mask mask one on 00:03:17.780 --> 00:03:19.659 align:start position:0% is a main happy so okay mask mask one on the<00:03:17.959> address<00:03:18.319> that<00:03:18.530> owns<00:03:18.769> an<00:03:18.980> opening<00:03:19.430> and 00:03:19.659 --> 00:03:19.669 align:start position:0% the address that owns an opening and 00:03:19.669 --> 00:03:23.640 align:start position:0% the address that owns an opening and click<00:03:20.329> on<00:03:20.419> register<00:03:20.900> and<00:03:21.969> your<00:03:22.969> time<00:03:23.299> in<00:03:23.419> your 00:03:23.640 --> 00:03:23.650 align:start position:0% click on register and your time in your 00:03:23.650 --> 00:03:26.679 align:start position:0% click on register and your time in your your<00:03:24.650> pop-up<00:03:24.980> ID<00:03:25.430> which<00:03:26.150> you<00:03:26.180> can<00:03:26.389> find<00:03:26.540> an 00:03:26.679 --> 00:03:26.689 align:start position:0% your pop-up ID which you can find an 00:03:26.689 --> 00:03:27.550 align:start position:0% your pop-up ID which you can find an even<00:03:26.930> scan 00:03:27.550 --> 00:03:27.560 align:start position:0% even scan 00:03:27.560 --> 00:03:33.209 align:start position:0% even scan so<00:03:28.549> for<00:03:28.760> example<00:03:29.269> if<00:03:29.419> I<00:03:29.540> go<00:03:29.689> to<00:03:29.750> my<00:03:29.959> pen<00:03:30.500> and<00:03:30.530> ask 00:03:33.209 --> 00:03:33.219 align:start position:0% 00:03:33.219 --> 00:03:37.839 align:start position:0% forgiveness<00:03:34.219> can<00:03:34.819> I<00:03:34.969> look<00:03:35.180> at<00:03:35.329> right<00:03:36.730> yes<00:03:37.730> II 00:03:37.839 --> 00:03:37.849 align:start position:0% forgiveness can I look at right yes II 00:03:37.849 --> 00:03:40.809 align:start position:0% forgiveness can I look at right yes II 721<00:03:38.659> tokens<00:03:39.049> you<00:03:39.859> see<00:03:40.069> that<00:03:40.219> three<00:03:40.400> days<00:03:40.549> ago<00:03:40.579> I 00:03:40.809 --> 00:03:40.819 align:start position:0% 721 tokens you see that three days ago I 00:03:40.819 --> 00:03:45.429 align:start position:0% 721 tokens you see that three days ago I played<00:03:41.329> by<00:03:42.340> both<00:03:43.340> token<00:03:43.730> so<00:03:44.540> this<00:03:44.750> is<00:03:44.900> my<00:03:45.230> zone 00:03:45.429 --> 00:03:45.439 align:start position:0% played by both token so this is my zone 00:03:45.439 --> 00:03:48.069 align:start position:0% played by both token so this is my zone IDs<00:03:45.829> for<00:03:46.099> tonight<00:03:46.430> five<00:03:46.699> wishes<00:03:47.599> for<00:03:47.930> my 00:03:48.069 --> 00:03:48.079 align:start position:0% IDs for tonight five wishes for my 00:03:48.079 --> 00:03:51.099 align:start position:0% IDs for tonight five wishes for my fishes<00:03:48.769> for<00:03:48.889> DEFCON<00:03:49.250> 5<00:03:49.459> I<00:03:49.699> would<00:03:50.569> like<00:03:50.930> this 00:03:51.099 --> 00:03:51.109 align:start position:0% fishes for DEFCON 5 I would like this 00:03:51.109 --> 00:03:54.219 align:start position:0% fishes for DEFCON 5 I would like this organizing<00:03:52.069> into<00:03:52.310> the<00:03:52.519> box<00:03:52.790> and<00:03:53.060> I'm<00:03:53.780> register 00:03:54.219 --> 00:03:54.229 align:start position:0% organizing into the box and I'm register 00:03:54.229 --> 00:03:57.099 align:start position:0% organizing into the box and I'm register so<00:03:54.919> that's<00:03:55.069> just<00:03:55.159> one<00:03:55.400> protection<00:03:56.109> should 00:03:57.099 --> 00:03:57.109 align:start position:0% so that's just one protection should 00:03:57.109 --> 00:03:59.379 align:start position:0% so that's just one protection should cost<00:03:57.349> less<00:03:57.409> than<00:03:57.680> a<00:03:57.739> person<00:03:58.310> twice<00:03:58.519> by<00:03:59.030> five 00:03:59.379 --> 00:03:59.389 align:start position:0% cost less than a person twice by five 00:03:59.389 --> 00:04:03.670 align:start position:0% cost less than a person twice by five cents<00:04:00.009> and<00:04:01.009> then<00:04:01.310> once<00:04:02.090> you<00:04:02.239> do<00:04:02.389> that<00:04:02.500> you<00:04:03.500> can 00:04:03.670 --> 00:04:03.680 align:start position:0% cents and then once you do that you can 00:04:03.680 --> 00:04:06.670 align:start position:0% cents and then once you do that you can go<00:04:03.859> to<00:04:03.889> post<00:04:04.250> and<00:04:05.030> you'll<00:04:05.810> be<00:04:05.900> able<00:04:06.019> to<00:04:06.169> see<00:04:06.409> the 00:04:06.670 --> 00:04:06.680 align:start position:0% go to post and you'll be able to see the 00:04:06.680 --> 00:04:09.069 align:start position:0% go to post and you'll be able to see the list<00:04:07.189> of<00:04:07.370> questions<00:04:07.939> I<00:04:08.269> hardly<00:04:08.599> need<00:04:08.720> to<00:04:08.840> see 00:04:09.069 --> 00:04:09.079 align:start position:0% list of questions I hardly need to see 00:04:09.079 --> 00:04:13.899 align:start position:0% list of questions I hardly need to see that<00:04:09.229> it<00:04:09.349> with<00:04:09.560> and<00:04:10.220> you<00:04:10.250> can<00:04:12.699> know<00:04:13.699> things 00:04:13.899 --> 00:04:13.909 align:start position:0% that it with and you can know things 00:04:13.909 --> 00:04:19.120 align:start position:0% that it with and you can know things might<00:04:14.209> look<00:04:14.239> at<00:04:14.949> answers<00:04:15.949> so<00:04:17.349> so<00:04:18.349> we<00:04:18.739> can<00:04:18.889> see 00:04:19.120 --> 00:04:19.130 align:start position:0% might look at answers so so we can see 00:04:19.130 --> 00:04:20.649 align:start position:0% might look at answers so so we can see like<00:04:19.280> the<00:04:19.370> function<00:04:19.849> of<00:04:19.970> people<00:04:20.209> voting<00:04:20.479> yes 00:04:20.649 --> 00:04:20.659 align:start position:0% like the function of people voting yes 00:04:20.659 --> 00:04:24.430 align:start position:0% like the function of people voting yes or<00:04:20.690> no<00:04:20.989> and<00:04:22.509> now<00:04:23.509> is<00:04:23.630> just<00:04:23.810> gonna<00:04:23.930> do<00:04:24.169> it<00:04:24.259> with 00:04:24.430 --> 00:04:24.440 align:start position:0% or no and now is just gonna do it with 00:04:24.440 --> 00:04:26.620 align:start position:0% or no and now is just gonna do it with them<00:04:24.590> or<00:04:24.800> by<00:04:25.039> adding<00:04:25.280> a<00:04:25.460> question<00:04:25.639> and<00:04:26.120> answer 00:04:26.620 --> 00:04:26.630 align:start position:0% them or by adding a question and answer 00:04:26.630 --> 00:04:31.450 align:start position:0% them or by adding a question and answer a<00:04:26.780> question<00:04:29.289> any<00:04:30.289> suggestions<00:04:30.830> for<00:04:31.070> highly 00:04:31.450 --> 00:04:31.460 align:start position:0% a question any suggestions for highly 00:04:31.460 --> 00:04:35.290 align:start position:0% a question any suggestions for highly controversial<00:04:32.139> topics<00:04:33.219> that<00:04:34.219> happen 00:04:35.290 --> 00:04:35.300 align:start position:0% controversial topics that happen 00:04:35.300 --> 00:05:52.570 align:start position:0% controversial topics that happen [Music] 00:05:52.570 --> 00:05:52.580 align:start position:0% 00:05:52.580 --> 00:06:39.100 align:start position:0% so<00:06:33.499> so<00:06:34.499> it's<00:06:34.649> just<00:06:34.709> a<00:06:34.860> sign<00:06:35.870> of<00:06:36.870> encryption<00:06:37.259> and 00:06:39.100 --> 00:06:39.110 align:start position:0% so so it's just a sign of encryption and 00:06:39.110 --> 00:06:41.509 align:start position:0% so so it's just a sign of encryption and that<00:06:40.110> we<00:06:40.199> submitted<00:06:40.499> to<00:06:40.589> my<00:06:40.740> auction<00:06:41.129> database 00:06:41.509 --> 00:06:41.519 align:start position:0% that we submitted to my auction database 00:06:41.519 --> 00:06:47.839 align:start position:0% that we submitted to my auction database and<00:06:43.669> now<00:06:44.669> I'm<00:06:44.789> gonna<00:06:44.939> do<00:06:45.180> the<00:06:45.349> one<00:06:46.349> team<00:06:46.589> I<00:06:46.949> mean 00:06:47.839 --> 00:06:47.849 align:start position:0% and now I'm gonna do the one team I mean 00:06:47.849 --> 00:06:49.519 align:start position:0% and now I'm gonna do the one team I mean a<00:06:47.909> real<00:06:48.060> Airport<00:06:48.389> on<00:06:48.659> admission<00:06:49.110> and<00:06:49.199> this<00:06:49.409> is 00:06:49.519 --> 00:06:49.529 align:start position:0% a real Airport on admission and this is 00:06:49.529 --> 00:06:50.600 align:start position:0% a real Airport on admission and this is where<00:06:49.740> the<00:06:49.860> menu<00:06:50.129> items 00:06:50.600 --> 00:06:50.610 align:start position:0% where the menu items 00:06:50.610 --> 00:06:53.689 align:start position:0% where the menu items I'm<00:06:51.329> gonna<00:06:51.479> prove<00:06:51.870> that<00:06:51.899> I<00:06:52.349> am<00:06:52.529> in<00:06:53.039> a<00:06:53.129> set<00:06:53.399> of 00:06:53.689 --> 00:06:53.699 align:start position:0% I'm gonna prove that I am in a set of 00:06:53.699 --> 00:06:56.330 align:start position:0% I'm gonna prove that I am in a set of registered<00:06:54.689> identities 00:06:56.330 --> 00:06:56.340 align:start position:0% registered identities 00:06:56.340 --> 00:06:59.480 align:start position:0% registered identities and<00:06:57.000> also<00:06:57.240> at<00:06:57.420> the<00:06:57.480> same<00:06:57.630> time<00:06:57.740> send<00:06:58.740> a<00:06:59.070> signal 00:06:59.480 --> 00:06:59.490 align:start position:0% and also at the same time send a signal 00:06:59.490 --> 00:07:03.560 align:start position:0% and also at the same time send a signal which<00:07:00.030> disturb<00:07:00.390> answer<00:07:00.720> yes<00:07:01.380> to<00:07:02.360> to<00:07:03.360> the<00:07:03.420> back 00:07:03.560 --> 00:07:03.570 align:start position:0% which disturb answer yes to to the back 00:07:03.570 --> 00:07:06.350 align:start position:0% which disturb answer yes to to the back end<00:07:03.780> the<00:07:04.530> bank<00:07:04.740> is<00:07:04.860> gonna<00:07:05.040> verify<00:07:05.280> that<00:07:05.670> I<00:07:05.940> am<00:07:06.300> a 00:07:06.350 --> 00:07:06.360 align:start position:0% end the bank is gonna verify that I am a 00:07:06.360 --> 00:07:08.810 align:start position:0% end the bank is gonna verify that I am a participant<00:07:07.080> of<00:07:07.470> a<00:07:07.800> little<00:07:08.070> debt<00:07:08.250> they<00:07:08.580> don't 00:07:08.810 --> 00:07:08.820 align:start position:0% participant of a little debt they don't 00:07:08.820 --> 00:07:11.810 align:start position:0% participant of a little debt they don't know<00:07:09.000> which<00:07:09.390> identity<00:07:09.900> I<00:07:10.520> unless<00:07:11.520> I'm<00:07:11.730> the 00:07:11.810 --> 00:07:11.820 align:start position:0% know which identity I unless I'm the 00:07:11.820 --> 00:07:13.520 align:start position:0% know which identity I unless I'm the only<00:07:11.970> one<00:07:12.150> that<00:07:12.360> is<00:07:12.660> obvious<00:07:12.990> but<00:07:13.140> if<00:07:13.380> there 00:07:13.520 --> 00:07:13.530 align:start position:0% only one that is obvious but if there 00:07:13.530 --> 00:07:14.990 align:start position:0% only one that is obvious but if there were<00:07:13.590> like<00:07:13.740> ten<00:07:13.890> people<00:07:14.190> who<00:07:14.310> registered<00:07:14.760> and 00:07:14.990 --> 00:07:15.000 align:start position:0% were like ten people who registered and 00:07:15.000 --> 00:07:17.270 align:start position:0% were like ten people who registered and I<00:07:15.330> made<00:07:15.690> a<00:07:15.720> proof<00:07:15.960> it<00:07:16.200> only<00:07:16.590> shows<00:07:16.980> that<00:07:17.010> like 00:07:17.270 --> 00:07:17.280 align:start position:0% I made a proof it only shows that like 00:07:17.280 --> 00:07:23.720 align:start position:0% I made a proof it only shows that like one<00:07:17.430> of<00:07:17.520> these<00:07:17.640> times<00:07:17.850> so<00:07:22.220> this<00:07:23.220> is<00:07:23.490> like 00:07:23.720 --> 00:07:23.730 align:start position:0% one of these times so this is like 00:07:23.730 --> 00:07:26.210 align:start position:0% one of these times so this is like basically<00:07:24.450> a<00:07:24.630> schnapps<00:07:24.960> and<00:07:25.260> the<00:07:25.860> a<00:07:25.890> snacks 00:07:26.210 --> 00:07:26.220 align:start position:0% basically a schnapps and the a snacks 00:07:26.220 --> 00:07:30.040 align:start position:0% basically a schnapps and the a snacks basically<00:07:26.940> I<00:07:27.690> wait<00:07:28.560> for<00:07:28.890> you<00:07:29.160> to<00:07:29.400> verify 00:07:30.040 --> 00:07:30.050 align:start position:0% basically I wait for you to verify 00:07:30.050 --> 00:07:32.420 align:start position:0% basically I wait for you to verify commutation<00:07:31.050> without<00:07:31.800> running<00:07:32.280> the 00:07:32.420 --> 00:07:32.430 align:start position:0% commutation without running the 00:07:32.430 --> 00:07:36.290 align:start position:0% commutation without running the computation<00:07:32.880> itself<00:07:33.240> and<00:07:34.670> so<00:07:35.670> there's<00:07:36.180> like 00:07:36.290 --> 00:07:36.300 align:start position:0% computation itself and so there's like 00:07:36.300 --> 00:07:38.360 align:start position:0% computation itself and so there's like two<00:07:36.960> main<00:07:37.170> steps<00:07:37.530> the<00:07:37.710> first<00:07:37.860> step<00:07:37.980> is<00:07:38.190> to 00:07:38.360 --> 00:07:38.370 align:start position:0% two main steps the first step is to 00:07:38.370 --> 00:07:40.460 align:start position:0% two main steps the first step is to generate<00:07:38.550> proof<00:07:39.000> and<00:07:39.270> this<00:07:39.720> is<00:07:39.870> something<00:07:40.170> for 00:07:40.460 --> 00:07:40.470 align:start position:0% generate proof and this is something for 00:07:40.470 --> 00:07:42.740 align:start position:0% generate proof and this is something for the<00:07:40.550> converse<00:07:41.550> of<00:07:41.640> the<00:07:41.790> things<00:07:41.970> like<00:07:42.120> how<00:07:42.690> many 00:07:42.740 --> 00:07:42.750 align:start position:0% the converse of the things like how many 00:07:42.750 --> 00:07:45.380 align:start position:0% the converse of the things like how many to<00:07:43.170> do<00:07:43.290> that<00:07:43.950> the<00:07:44.220> improvement<00:07:44.760> vacation<00:07:45.180> have 00:07:45.380 --> 00:07:45.390 align:start position:0% to do that the improvement vacation have 00:07:45.390 --> 00:07:48.080 align:start position:0% to do that the improvement vacation have it<00:07:45.510> done<00:07:45.720> in<00:07:45.990> relational<00:07:46.650> time<00:07:46.890> and<00:07:47.850> it<00:07:47.970> can 00:07:48.080 --> 00:07:48.090 align:start position:0% it done in relational time and it can 00:07:48.090 --> 00:07:50.000 align:start position:0% it done in relational time and it can also<00:07:48.240> be<00:07:48.390> done<00:07:48.510> for<00:07:48.630> trade<00:07:48.840> for<00:07:49.080> the<00:07:49.770> sake<00:07:49.980> of 00:07:50.000 --> 00:07:50.010 align:start position:0% also be done for trade for the sake of 00:07:50.010 --> 00:07:52.910 align:start position:0% also be done for trade for the sake of this<00:07:50.280> demo<00:07:51.060> the<00:07:51.390> industry<00:07:52.080> the<00:07:52.200> recognition 00:07:52.910 --> 00:07:52.920 align:start position:0% this demo the industry the recognition 00:07:52.920 --> 00:07:57.680 align:start position:0% this demo the industry the recognition of<00:07:52.950> objects<00:07:53.370> in<00:07:53.790> the<00:07:54.000> MIT<00:07:54.410> someone<00:07:56.420> that<00:07:57.420> and 00:07:57.680 --> 00:07:57.690 align:start position:0% of objects in the MIT someone that and 00:07:57.690 --> 00:08:00.140 align:start position:0% of objects in the MIT someone that and you<00:07:58.380> can<00:07:58.560> generate<00:07:58.980> crews<00:07:59.220> any<00:07:59.430> possible<00:07:59.850> and 00:08:00.140 --> 00:08:00.150 align:start position:0% you can generate crews any possible and 00:08:00.150 --> 00:08:02.360 align:start position:0% you can generate crews any possible and so<00:08:00.960> what<00:08:01.110> happens<00:08:01.380> is<00:08:01.530> that<00:08:01.560> each<00:08:01.980> other<00:08:02.160> into 00:08:02.360 --> 00:08:02.370 align:start position:0% so what happens is that each other into 00:08:02.370 --> 00:08:04.670 align:start position:0% so what happens is that each other into that<00:08:02.520> process<00:08:02.730> into<00:08:03.180> an<00:08:03.240> API<00:08:03.450> sensor<00:08:04.440> that<00:08:04.530> I 00:08:04.670 --> 00:08:04.680 align:start position:0% that process into an API sensor that I 00:08:04.680 --> 00:08:08.000 align:start position:0% that process into an API sensor that I can<00:08:04.890> I<00:08:05.040> can<00:08:05.280> verify<00:08:05.520> the<00:08:05.700> truth<00:08:06.890> updates<00:08:07.890> the 00:08:08.000 --> 00:08:08.010 align:start position:0% can I can verify the truth updates the 00:08:08.010 --> 00:08:11.140 align:start position:0% can I can verify the truth updates the database<00:08:08.250> if<00:08:08.640> it<00:08:08.730> was<00:08:08.880> previously<00:08:09.410> we<00:08:10.410> also 00:08:11.140 --> 00:08:11.150 align:start position:0% database if it was previously we also 00:08:11.150 --> 00:08:13.820 align:start position:0% database if it was previously we also have<00:08:12.150> a<00:08:12.180> mechanism<00:08:12.390> where<00:08:12.930> you<00:08:13.380> cannot<00:08:13.680> vote 00:08:13.820 --> 00:08:13.830 align:start position:0% have a mechanism where you cannot vote 00:08:13.830 --> 00:08:18.110 align:start position:0% have a mechanism where you cannot vote twice<00:08:14.100> and<00:08:15.230> this<00:08:16.230> mimics<00:08:16.650> these<00:08:16.950> on<00:08:17.850> chain 00:08:18.110 --> 00:08:18.120 align:start position:0% twice and this mimics these on chain 00:08:18.120 --> 00:08:20.600 align:start position:0% twice and this mimics these on chain behavior<00:08:18.840> of<00:08:19.350> is<00:08:19.530> my<00:08:19.680> contract<00:08:20.100> that<00:08:20.190> prevents 00:08:20.600 --> 00:08:20.610 align:start position:0% behavior of is my contract that prevents 00:08:20.610 --> 00:08:25.360 align:start position:0% behavior of is my contract that prevents you<00:08:20.730> from<00:08:20.760> forty<00:08:21.510> twice<00:08:23.450> so<00:08:24.450> this<00:08:24.630> will<00:08:24.870> take<00:08:25.020> a 00:08:25.360 --> 00:08:25.370 align:start position:0% you from forty twice so this will take a 00:08:25.370 --> 00:08:29.100 align:start position:0% you from forty twice so this will take a comment 00:08:29.100 --> 00:08:29.110 align:start position:0% 00:08:29.110 --> 00:08:31.950 align:start position:0% and<00:08:29.200> I<00:08:29.800> can<00:08:30.010> Germany<00:08:30.550> to<00:08:30.670> like<00:08:30.850> me<00:08:31.060> mechanisms 00:08:31.950 --> 00:08:31.960 align:start position:0% and I can Germany to like me mechanisms 00:08:31.960 --> 00:08:34.200 align:start position:0% and I can Germany to like me mechanisms that<00:08:32.110> city<00:08:32.380> sucks<00:08:32.620> how<00:08:33.400> you<00:08:33.460> can<00:08:33.700> see<00:08:34.090> this 00:08:34.200 --> 00:08:34.210 align:start position:0% that city sucks how you can see this 00:08:34.210 --> 00:08:35.330 align:start position:0% that city sucks how you can see this next<00:08:34.420> website 00:08:35.330 --> 00:08:35.340 align:start position:0% next website 00:08:35.340 --> 00:08:39.600 align:start position:0% next website I<00:08:36.340> haven't<00:08:37.000> got<00:08:37.120> my<00:08:37.270> let's<00:08:38.050> say<00:08:38.200> I<00:08:38.460> have<00:08:39.460> the 00:08:39.600 --> 00:08:39.610 align:start position:0% I haven't got my let's say I have the 00:08:39.610 --> 00:08:42.350 align:start position:0% I haven't got my let's say I have the set<00:08:39.820> of<00:08:40.000> the<00:08:40.150> website<00:08:40.570> deposited<00:08:41.080> and<00:08:41.170> then<00:08:41.740> my 00:08:42.350 --> 00:08:42.360 align:start position:0% set of the website deposited and then my 00:08:42.360 --> 00:08:45.510 align:start position:0% set of the website deposited and then my means<00:08:43.360> the<00:08:43.480> new<00:08:43.630> plugin<00:08:44.350> because<00:08:44.800> I<00:08:44.950> came<00:08:45.340> like 00:08:45.510 --> 00:08:45.520 align:start position:0% means the new plugin because I came like 00:08:45.520 --> 00:08:48.050 align:start position:0% means the new plugin because I came like the<00:08:45.700> dead<00:08:45.850> fun<00:08:46.090> does<00:08:46.570> it<00:08:46.720> have<00:08:46.840> to<00:08:46.990> update<00:08:47.170> your 00:08:48.050 --> 00:08:48.060 align:start position:0% the dead fun does it have to update your 00:08:48.060 --> 00:08:50.670 align:start position:0% the dead fun does it have to update your registry 00:08:50.670 --> 00:08:50.680 align:start position:0% registry 00:08:50.680 --> 00:08:53.910 align:start position:0% registry you<00:08:51.130> just<00:08:51.340> have<00:08:51.460> to<00:08:51.490> register<00:08:52.500> it<00:08:53.530> well<00:08:53.800> it 00:08:53.910 --> 00:08:53.920 align:start position:0% you just have to register it well it 00:08:53.920 --> 00:08:55.710 align:start position:0% you just have to register it well it just<00:08:53.950> will<00:08:54.670> be<00:08:54.760> also<00:08:55.090> if<00:08:55.150> it's<00:08:55.360> be<00:08:55.510> able<00:08:55.660> to 00:08:55.710 --> 00:08:55.720 align:start position:0% just will be also if it's be able to 00:08:55.720 --> 00:08:58.080 align:start position:0% just will be also if it's be able to just<00:08:55.870> pull<00:08:56.140> from<00:08:56.380> the<00:08:56.980> 7:21<00:08:57.640> untrackable 00:08:58.080 --> 00:08:58.090 align:start position:0% just pull from the 7:21 untrackable 00:08:58.090 --> 00:09:02.280 align:start position:0% just pull from the 7:21 untrackable interactive<00:08:59.020> update<00:09:00.010> you'll<00:09:00.280> have<00:09:00.900> we<00:09:01.900> the 00:09:02.280 --> 00:09:02.290 align:start position:0% interactive update you'll have we the 00:09:02.290 --> 00:09:04.050 align:start position:0% interactive update you'll have we the miss<00:09:02.500> of<00:09:02.650> interest<00:09:02.920> of<00:09:03.010> my<00:09:03.100> dentist<00:09:03.640> who<00:09:03.820> ever 00:09:04.050 --> 00:09:04.060 align:start position:0% miss of interest of my dentist who ever 00:09:04.060 --> 00:09:07.110 align:start position:0% miss of interest of my dentist who ever registered<00:09:04.240> through<00:09:04.750> this<00:09:04.870> app<00:09:05.190> so<00:09:06.190> if<00:09:06.640> so 00:09:07.110 --> 00:09:07.120 align:start position:0% registered through this app so if so 00:09:07.120 --> 00:09:08.820 align:start position:0% registered through this app so if so even<00:09:07.420> take<00:09:07.810> the<00:09:07.990> don't<00:09:08.200> get<00:09:08.320> immunity<00:09:08.410> of<00:09:08.800> the 00:09:08.820 --> 00:09:08.830 align:start position:0% even take the don't get immunity of the 00:09:08.830 --> 00:09:13.590 align:start position:0% even take the don't get immunity of the register<00:09:09.280> I<00:09:09.580> use<00:09:09.970> this<00:09:10.090> app<00:09:11.940> alright<00:09:12.940> so<00:09:13.210> the 00:09:13.590 --> 00:09:13.600 align:start position:0% register I use this app alright so the 00:09:13.600 --> 00:09:16.260 align:start position:0% register I use this app alright so the answers<00:09:13.900> yes<00:09:14.130> and<00:09:15.130> I<00:09:15.250> reach<00:09:15.580> anybody<00:09:15.790> when<00:09:16.180> I 00:09:16.260 --> 00:09:16.270 align:start position:0% answers yes and I reach anybody when I 00:09:16.270 --> 00:09:17.280 align:start position:0% answers yes and I reach anybody when I talk<00:09:16.480> to<00:09:16.510> try<00:09:16.750> this<00:09:16.810> out 00:09:17.280 --> 00:09:17.290 align:start position:0% talk to try this out 00:09:17.290 --> 00:09:19.620 align:start position:0% talk to try this out unfortunately<00:09:18.250> it's<00:09:18.400> not<00:09:18.550> super<00:09:19.360> mobile 00:09:19.620 --> 00:09:19.630 align:start position:0% unfortunately it's not super mobile 00:09:19.630 --> 00:09:21.030 align:start position:0% unfortunately it's not super mobile friendly<00:09:19.900> so<00:09:20.170> I<00:09:20.230> don't<00:09:20.410> think<00:09:20.470> that<00:09:20.560> it<00:09:20.860> woke 00:09:21.030 --> 00:09:21.040 align:start position:0% friendly so I don't think that it woke 00:09:21.040 --> 00:09:30.400 align:start position:0% friendly so I don't think that it woke up<00:09:21.190> all<00:09:21.310> of<00:09:21.430> its<00:09:22.590> the<00:09:23.590> URL<00:09:24.060> one<00:09:25.060> of<00:09:25.210> us 00:09:30.400 --> 00:09:30.410 align:start position:0% 00:09:30.410 --> 00:09:34.160 align:start position:0% at<00:09:30.860> this<00:09:31.040> point<00:09:31.750> any<00:09:32.750> questions<00:09:33.230> before<00:09:33.620> I 00:09:34.160 --> 00:09:34.170 align:start position:0% at this point any questions before I 00:09:34.170 --> 00:09:36.270 align:start position:0% at this point any questions before I [Music] 00:09:36.270 --> 00:09:36.280 align:start position:0% [Music] 00:09:36.280 --> 00:09:40.960 align:start position:0% [Music] actually<00:09:38.020> make<00:09:39.020> a<00:09:39.500> trend<00:09:39.860> left<00:09:40.130> endpoint<00:09:40.340> and 00:09:40.960 --> 00:09:40.970 align:start position:0% actually make a trend left endpoint and 00:09:40.970 --> 00:09:43.630 align:start position:0% actually make a trend left endpoint and directly<00:09:41.360> but<00:09:41.540> travelin<00:09:42.200> API<00:09:42.650> so<00:09:43.220> that<00:09:43.250> you're 00:09:43.630 --> 00:09:43.640 align:start position:0% directly but travelin API so that you're 00:09:43.640 --> 00:09:47.580 align:start position:0% directly but travelin API so that you're asleep 00:09:47.580 --> 00:09:47.590 align:start position:0% 00:09:47.590 --> 00:09:56.400 align:start position:0% okay<00:09:48.590> so<00:09:50.800> in<00:09:51.800> this<00:09:52.670> case<00:09:53.290> we<00:09:54.290> send<00:09:54.740> the<00:09:55.190> vote<00:09:55.490> to 00:09:56.400 --> 00:09:56.410 align:start position:0% okay so in this case we send the vote to 00:09:56.410 --> 00:10:00.280 align:start position:0% okay so in this case we send the vote to object<00:09:57.410> to<00:09:57.560> the<00:09:58.280> again<00:09:58.880> but<00:09:59.780> that's<00:09:59.930> the 00:10:00.280 --> 00:10:00.290 align:start position:0% object to the again but that's the 00:10:00.290 --> 00:10:02.440 align:start position:0% object to the again but that's the reason<00:10:00.440> for<00:10:00.710> that<00:10:00.800> is<00:10:01.100> because<00:10:01.460> as<00:10:01.940> a<00:10:01.970> demo<00:10:02.270> and 00:10:02.440 --> 00:10:02.450 align:start position:0% reason for that is because as a demo and 00:10:02.450 --> 00:10:04.960 align:start position:0% reason for that is because as a demo and just<00:10:02.720> for<00:10:02.810> the<00:10:02.900> demonstrate<00:10:03.500> way<00:10:03.680> votes<00:10:03.970> you 00:10:04.960 --> 00:10:04.970 align:start position:0% just for the demonstrate way votes you 00:10:04.970 --> 00:10:06.730 align:start position:0% just for the demonstrate way votes you know<00:10:05.090> in<00:10:05.330> a<00:10:05.450> better<00:10:05.660> in<00:10:05.960> like<00:10:06.200> a<00:10:06.230> production 00:10:06.730 --> 00:10:06.740 align:start position:0% know in a better in like a production 00:10:06.740 --> 00:10:09.600 align:start position:0% know in a better in like a production application<00:10:07.360> the<00:10:08.360> you<00:10:08.600> would<00:10:08.780> send<00:10:09.170> that<00:10:09.260> vote 00:10:09.600 --> 00:10:09.610 align:start position:0% application the you would send that vote 00:10:09.610 --> 00:10:13.780 align:start position:0% application the you would send that vote like<00:10:10.610> through<00:10:10.880> tall<00:10:11.180> Sunday<00:10:11.690> to<00:10:12.290> an<00:10:12.710> API<00:10:13.070> of<00:10:13.550> a 00:10:13.780 --> 00:10:13.790 align:start position:0% like through tall Sunday to an API of a 00:10:13.790 --> 00:10:18.000 align:start position:0% like through tall Sunday to an API of a realtor<00:10:14.270> that<00:10:14.510> would<00:10:15.500> really<00:10:16.490> that<00:10:16.790> prove<00:10:17.300> to 00:10:18.000 --> 00:10:18.010 align:start position:0% realtor that would really that prove to 00:10:18.010 --> 00:10:21.430 align:start position:0% realtor that would really that prove to the<00:10:19.010> contract<00:10:19.460> and<00:10:19.850> receive<00:10:20.750> a<00:10:20.840> reward<00:10:20.990> from 00:10:21.430 --> 00:10:21.440 align:start position:0% the contract and receive a reward from 00:10:21.440 --> 00:10:27.760 align:start position:0% the contract and receive a reward from the<00:10:21.530> transaction<00:10:21.950> that<00:10:26.110> that<00:10:27.110> was<00:10:27.290> something 00:10:27.760 --> 00:10:27.770 align:start position:0% the transaction that that was something 00:10:27.770 --> 00:10:29.410 align:start position:0% the transaction that that was something that<00:10:27.800> would<00:10:27.980> cover<00:10:28.130> with<00:10:28.430> here<00:10:28.580> yeah<00:10:29.180> by<00:10:29.360> this 00:10:29.410 --> 00:10:29.420 align:start position:0% that would cover with here yeah by this 00:10:29.420 --> 00:10:31.360 align:start position:0% that would cover with here yeah by this case<00:10:29.840> we're<00:10:30.230> sending<00:10:30.440> through<00:10:30.650> an<00:10:30.710> API<00:10:30.950> in<00:10:31.190> not 00:10:31.360 --> 00:10:31.370 align:start position:0% case we're sending through an API in not 00:10:31.370 --> 00:10:33.910 align:start position:0% case we're sending through an API in not because<00:10:31.520> we<00:10:31.850> are<00:10:32.140> not<00:10:33.140> because<00:10:33.380> when<00:10:33.560> piracy 00:10:33.910 --> 00:10:33.920 align:start position:0% because we are not because when piracy 00:10:33.920 --> 00:10:35.980 align:start position:0% because we are not because when piracy but<00:10:34.070> because<00:10:34.400> first<00:10:35.120> of<00:10:35.180> all<00:10:35.240> is<00:10:35.330> a<00:10:35.390> demo<00:10:35.660> and 00:10:35.980 --> 00:10:35.990 align:start position:0% but because first of all is a demo and 00:10:35.990 --> 00:10:39.340 align:start position:0% but because first of all is a demo and second<00:10:36.710> of<00:10:36.800> all<00:10:36.980> even<00:10:37.310> in<00:10:37.970> production<00:10:38.230> we<00:10:39.230> were 00:10:39.340 --> 00:10:39.350 align:start position:0% second of all even in production we were 00:10:39.350 --> 00:10:41.260 align:start position:0% second of all even in production we were selling<00:10:39.680> fruit<00:10:39.830> okay<00:10:40.250> and<00:10:40.520> then<00:10:40.790> the<00:10:41.000> relay 00:10:41.260 --> 00:10:41.270 align:start position:0% selling fruit okay and then the relay 00:10:41.270 --> 00:10:43.210 align:start position:0% selling fruit okay and then the relay would<00:10:41.540> send<00:10:41.780> money<00:10:42.170> obviously<00:10:42.470> I'm<00:10:43.160> just 00:10:43.210 --> 00:10:43.220 align:start position:0% would send money obviously I'm just 00:10:43.220 --> 00:10:47.010 align:start position:0% would send money obviously I'm just gonna<00:10:43.550> try<00:10:43.790> to<00:10:43.820> do<00:10:44.450> division<00:10:44.780> syllable<00:10:45.260> but 00:10:47.010 --> 00:10:47.020 align:start position:0% gonna try to do division syllable but 00:10:47.020 --> 00:10:49.540 align:start position:0% gonna try to do division syllable but make<00:10:48.020> the<00:10:48.170> transaction<00:10:48.620> directly<00:10:49.340> then 00:10:49.540 --> 00:10:49.550 align:start position:0% make the transaction directly then 00:10:49.550 --> 00:10:51.170 align:start position:0% make the transaction directly then people<00:10:50.330> will 00:10:51.170 --> 00:10:51.180 align:start position:0% people will 00:10:51.180 --> 00:10:53.630 align:start position:0% people will you<00:10:51.420> are<00:10:51.690> able<00:10:51.930> to<00:10:51.990> use<00:10:52.260> it<00:10:52.410> so<00:10:53.040> that<00:10:53.070> we<00:10:53.520> are 00:10:53.630 --> 00:10:53.640 align:start position:0% you are able to use it so that we are 00:10:53.640 --> 00:10:57.200 align:start position:0% you are able to use it so that we are aware<00:10:53.790> right<00:10:54.600> so<00:10:55.190> the<00:10:56.190> only<00:10:56.220> transaction<00:10:57.030> that 00:10:57.200 --> 00:10:57.210 align:start position:0% aware right so the only transaction that 00:10:57.210 --> 00:10:59.030 align:start position:0% aware right so the only transaction that can<00:10:57.390> be<00:10:57.570> linked<00:10:57.810> to<00:10:57.900> your<00:10:58.170> address<00:10:58.620> is<00:10:58.920> the 00:10:59.030 --> 00:10:59.040 align:start position:0% can be linked to your address is the 00:10:59.040 --> 00:11:02.570 align:start position:0% can be linked to your address is the registration<00:10:59.540> transaction<00:11:00.540> or<00:11:01.140> the<00:11:01.400> on<00:11:02.400> the 00:11:02.570 --> 00:11:02.580 align:start position:0% registration transaction or the on the 00:11:02.580 --> 00:11:04.430 align:start position:0% registration transaction or the on the transaction<00:11:03.060> that<00:11:03.210> adds<00:11:03.510> an<00:11:03.840> impression<00:11:04.290> to 00:11:04.430 --> 00:11:04.440 align:start position:0% transaction that adds an impression to 00:11:04.440 --> 00:11:06.400 align:start position:0% transaction that adds an impression to the<00:11:04.470> system<00:11:05.040> but<00:11:05.610> may<00:11:05.730> answer<00:11:06.090> the<00:11:06.120> question 00:11:06.400 --> 00:11:06.410 align:start position:0% the system but may answer the question 00:11:06.410 --> 00:11:10.280 align:start position:0% the system but may answer the question we<00:11:07.410> generated<00:11:08.100> proven<00:11:08.400> Center<00:11:08.910> to<00:11:09.870> a<00:11:09.900> third 00:11:10.280 --> 00:11:10.290 align:start position:0% we generated proven Center to a third 00:11:10.290 --> 00:11:12.860 align:start position:0% we generated proven Center to a third party<00:11:10.440> video<00:11:10.940> that<00:11:11.940> does<00:11:12.180> the<00:11:12.300> transaction<00:11:12.630> it 00:11:12.860 --> 00:11:12.870 align:start position:0% party video that does the transaction it 00:11:12.870 --> 00:11:16.070 align:start position:0% party video that does the transaction it is<00:11:12.990> against<00:11:13.290> for<00:11:13.470> you<00:11:13.850> and<00:11:14.850> that<00:11:15.570> really<00:11:15.690> is 00:11:16.070 --> 00:11:16.080 align:start position:0% is against for you and that really is 00:11:16.080 --> 00:11:21.800 align:start position:0% is against for you and that really is rewarded<00:11:17.690> by<00:11:19.610> so<00:11:20.610> this<00:11:20.970> is<00:11:21.120> like<00:11:21.300> on<00:11:21.510> a<00:11:21.540> tangent 00:11:21.800 --> 00:11:21.810 align:start position:0% rewarded by so this is like on a tangent 00:11:21.810 --> 00:11:24.200 align:start position:0% rewarded by so this is like on a tangent but<00:11:22.140> I'm<00:11:22.770> just<00:11:22.980> going<00:11:23.160> to<00:11:23.220> anyway 00:11:24.200 --> 00:11:24.210 align:start position:0% but I'm just going to anyway 00:11:24.210 --> 00:11:26.420 align:start position:0% but I'm just going to anyway in<00:11:24.420> the<00:11:24.600> content<00:11:24.960> version<00:11:25.170> one<00:11:25.950> idea<00:11:26.190> that<00:11:26.250> we 00:11:26.420 --> 00:11:26.430 align:start position:0% in the content version one idea that we 00:11:26.430 --> 00:11:30.110 align:start position:0% in the content version one idea that we have<00:11:26.610> is<00:11:26.790> to<00:11:27.290> is<00:11:28.290> that<00:11:28.500> when<00:11:28.680> you<00:11:28.800> and<00:11:29.250> you<00:11:29.400> ask 00:11:30.110 --> 00:11:30.120 align:start position:0% have is to is that when you and you ask 00:11:30.120 --> 00:11:33.440 align:start position:0% have is to is that when you and you ask your<00:11:30.360> question<00:11:30.720> you<00:11:31.290> would<00:11:31.410> have<00:11:31.530> to<00:11:32.450> send 00:11:33.440 --> 00:11:33.450 align:start position:0% your question you would have to send 00:11:33.450 --> 00:11:35.630 align:start position:0% your question you would have to send some<00:11:33.690> along<00:11:34.260> the<00:11:34.440> question<00:11:34.830> and<00:11:35.070> it<00:11:35.460> need<00:11:35.610> to 00:11:35.630 --> 00:11:35.640 align:start position:0% some along the question and it need to 00:11:35.640 --> 00:11:38.030 align:start position:0% some along the question and it need to be<00:11:35.760> stored<00:11:36.000> in<00:11:36.150> the<00:11:36.240> contact<00:11:36.660> and<00:11:36.890> when<00:11:37.890> you 00:11:38.030 --> 00:11:38.040 align:start position:0% be stored in the contact and when you 00:11:38.040 --> 00:11:40.550 align:start position:0% be stored in the contact and when you answer<00:11:38.460> the<00:11:38.550> question<00:11:39.050> the<00:11:40.050> contract<00:11:40.440> needs 00:11:40.550 --> 00:11:40.560 align:start position:0% answer the question the contract needs 00:11:40.560 --> 00:11:44.030 align:start position:0% answer the question the contract needs that<00:11:41.360> small<00:11:42.360> reward<00:11:42.690> to<00:11:42.990> be<00:11:43.200> really 00:11:44.030 --> 00:11:44.040 align:start position:0% that small reward to be really 00:11:44.040 --> 00:11:46.010 align:start position:0% that small reward to be really understand<00:11:44.610> the<00:11:44.670> transaction<00:11:45.180> and<00:11:45.390> that's 00:11:46.010 --> 00:11:46.020 align:start position:0% understand the transaction and that's 00:11:46.020 --> 00:11:47.870 align:start position:0% understand the transaction and that's why<00:11:46.260> as<00:11:46.590> Holliday<00:11:47.160> is<00:11:47.280> incentivized<00:11:47.790> to 00:11:47.870 --> 00:11:47.880 align:start position:0% why as Holliday is incentivized to 00:11:47.880 --> 00:11:51.380 align:start position:0% why as Holliday is incentivized to relate<00:11:48.600> intersection<00:11:49.050> offenders<00:11:49.640> so<00:11:50.640> that's 00:11:51.380 --> 00:11:51.390 align:start position:0% relate intersection offenders so that's 00:11:51.390 --> 00:11:53.240 align:start position:0% relate intersection offenders so that's how<00:11:51.570> you<00:11:51.630> get<00:11:51.810> away<00:11:51.930> with<00:11:52.290> not<00:11:52.680> made<00:11:52.920> against 00:11:53.240 --> 00:11:53.250 align:start position:0% how you get away with not made against 00:11:53.250 --> 00:11:56.840 align:start position:0% how you get away with not made against for<00:11:53.640> fully<00:11:55.340> because<00:11:56.340> the<00:11:56.460> people<00:11:56.760> of 00:11:56.840 --> 00:11:56.850 align:start position:0% for fully because the people of 00:11:56.850 --> 00:11:58.610 align:start position:0% for fully because the people of expression<00:11:57.390> could<00:11:57.600> subsidize<00:11:58.050> the<00:11:58.440> case 00:11:58.610 --> 00:11:58.620 align:start position:0% expression could subsidize the case 00:11:58.620 --> 00:12:02.330 align:start position:0% expression could subsidize the case without<00:11:58.830> follow<00:11:59.520> the<00:11:59.970> recipe<00:12:01.070> but<00:12:02.070> for<00:12:02.280> this 00:12:02.330 --> 00:12:02.340 align:start position:0% without follow the recipe but for this 00:12:02.340 --> 00:12:03.800 align:start position:0% without follow the recipe but for this demo<00:12:02.580> is<00:12:02.760> and<00:12:02.970> how<00:12:03.120> the<00:12:03.180> opportunity<00:12:03.690> I<00:12:03.780> don't 00:12:03.800 --> 00:12:03.810 align:start position:0% demo is and how the opportunity I don't 00:12:03.810 --> 00:12:06.730 align:start position:0% demo is and how the opportunity I don't know<00:12:04.530> this<00:12:04.650> so<00:12:04.830> there's<00:12:05.010> no<00:12:05.130> comment<00:12:05.580> on<00:12:05.880> that 00:12:06.730 --> 00:12:06.740 align:start position:0% know this so there's no comment on that 00:12:06.740 --> 00:12:11.590 align:start position:0% know this so there's no comment on that okay<00:12:07.740> so<00:12:08.360> now<00:12:09.360> I<00:12:09.390> just<00:12:09.660> come<00:12:09.900> in<00:12:09.930> to<00:12:10.020> my<00:12:10.620> America 00:12:11.590 --> 00:12:11.600 align:start position:0% okay so now I just come in to my America 00:12:11.600 --> 00:12:18.019 align:start position:0% okay so now I just come in to my America is<00:12:12.600> my<00:12:12.750> nation<00:12:12.900> of<00:12:13.170> Pakistan 00:12:18.019 --> 00:12:18.029 align:start position:0% 00:12:18.029 --> 00:12:23.970 align:start position:0% okay<00:12:19.029> so<00:12:21.029> right<00:12:22.029> so<00:12:22.300> just<00:12:22.480> to<00:12:22.570> summarize<00:12:22.980> what 00:12:23.970 --> 00:12:23.980 align:start position:0% okay so right so just to summarize what 00:12:23.980 --> 00:12:27.050 align:start position:0% okay so right so just to summarize what is<00:12:24.100> false<00:12:24.490> and<00:12:24.519> telling<00:12:24.880> a<00:12:25.029> free<00:12:25.800> registration 00:12:27.050 --> 00:12:27.060 align:start position:0% is false and telling a free registration 00:12:27.060 --> 00:12:29.730 align:start position:0% is false and telling a free registration have<00:12:28.060> Asante<00:12:28.480> but<00:12:28.750> that's<00:12:28.899> only<00:12:29.050> one<00:12:29.260> that 00:12:29.730 --> 00:12:29.740 align:start position:0% have Asante but that's only one that 00:12:29.740 --> 00:12:32.160 align:start position:0% have Asante but that's only one that goes<00:12:29.889> on<00:12:30.040> chain<00:12:30.450> that's<00:12:31.450> a<00:12:31.600> back-end<00:12:31.810> server 00:12:32.160 --> 00:12:32.170 align:start position:0% goes on chain that's a back-end server 00:12:32.170 --> 00:12:35.220 align:start position:0% goes on chain that's a back-end server that<00:12:32.440> checks<00:12:32.740> whether<00:12:32.980> the<00:12:33.130> word<00:12:33.339> user<00:12:34.089> and<00:12:34.360> as 00:12:35.220 --> 00:12:35.230 align:start position:0% that checks whether the word user and as 00:12:35.230 --> 00:12:39.810 align:start position:0% that checks whether the word user and as a<00:12:35.290> token<00:12:37.050> it<00:12:38.050> does<00:12:38.620> the<00:12:38.860> is<00:12:39.100> it<00:12:39.279> is<00:12:39.399> not<00:12:39.610> proof 00:12:39.810 --> 00:12:39.820 align:start position:0% a token it does the is it is not proof 00:12:39.820 --> 00:12:41.699 align:start position:0% a token it does the is it is not proof verification<00:12:40.480> of<00:12:40.630> train<00:12:40.870> and<00:12:41.079> those 00:12:41.699 --> 00:12:41.709 align:start position:0% verification of train and those 00:12:41.709 --> 00:12:44.720 align:start position:0% verification of train and those installing<00:12:42.370> SQL<00:12:42.550> database<00:12:43.060> and<00:12:43.420> as<00:12:43.899> also<00:12:44.110> a 00:12:44.720 --> 00:12:44.730 align:start position:0% installing SQL database and as also a 00:12:44.730 --> 00:12:50.759 align:start position:0% installing SQL database and as also a they<00:12:45.730> also<00:12:45.880> check<00:12:46.240> the<00:12:46.480> cache<00:12:46.870> of<00:12:47.110> the<00:12:49.769> the 00:12:50.759 --> 00:12:50.769 align:start position:0% they also check the cache of the the 00:12:50.769 --> 00:12:54.030 align:start position:0% they also check the cache of the the answer<00:12:51.160> and<00:12:51.430> the<00:12:51.639> identity<00:12:52.620> to<00:12:53.620> prevent<00:12:53.920> our 00:12:54.030 --> 00:12:54.040 align:start position:0% answer and the identity to prevent our 00:12:54.040 --> 00:12:57.000 align:start position:0% answer and the identity to prevent our synthetic<00:12:54.370> so<00:12:54.760> I<00:12:55.350> can<00:12:56.350> explain<00:12:56.560> what<00:12:56.740> a<00:12:56.769> pixel 00:12:57.000 --> 00:12:57.010 align:start position:0% synthetic so I can explain what a pixel 00:12:57.010 --> 00:13:03.990 align:start position:0% synthetic so I can explain what a pixel antivirus<00:12:57.610> fail<00:12:59.430> this<00:13:00.430> is<00:13:00.639> what<00:13:00.790> prevents<00:13:03.000> the 00:13:03.990 --> 00:13:04.000 align:start position:0% antivirus fail this is what prevents the 00:13:04.000 --> 00:13:06.509 align:start position:0% antivirus fail this is what prevents the same<00:13:04.329> user<00:13:04.930> from<00:13:05.260> signaling<00:13:05.740> twice<00:13:06.010> to<00:13:06.490> a 00:13:06.509 --> 00:13:06.519 align:start position:0% same user from signaling twice to a 00:13:06.519 --> 00:13:09.410 align:start position:0% same user from signaling twice to a question<00:13:07.120> or<00:13:07.600> to<00:13:07.810> avoid<00:13:08.230> a<00:13:08.290> 2008<00:13:08.709> crash<00:13:08.920> and 00:13:09.410 --> 00:13:09.420 align:start position:0% question or to avoid a 2008 crash and 00:13:09.420 --> 00:13:13.340 align:start position:0% question or to avoid a 2008 crash and this<00:13:10.420> effect<00:13:11.139> this<00:13:11.350> mechanism<00:13:11.920> is<00:13:12.550> Pompey<00:13:12.910> is 00:13:13.340 --> 00:13:13.350 align:start position:0% this effect this mechanism is Pompey is 00:13:13.350 --> 00:13:15.990 align:start position:0% this effect this mechanism is Pompey is what<00:13:14.350> I'm<00:13:14.500> doing<00:13:14.620> to<00:13:14.949> mimic<00:13:15.399> what<00:13:15.850> the 00:13:15.990 --> 00:13:16.000 align:start position:0% what I'm doing to mimic what the 00:13:16.000 --> 00:13:18.420 align:start position:0% what I'm doing to mimic what the contract<00:13:16.389> with<00:13:16.540> the<00:13:16.660> contractor<00:13:17.040> so<00:13:18.040> one 00:13:18.420 --> 00:13:18.430 align:start position:0% contract with the contractor so one 00:13:18.430 --> 00:13:20.970 align:start position:0% contract with the contractor so one chain<00:13:18.730> as<00:13:19.510> messages<00:13:20.079> now<00:13:20.230> this<00:13:20.440> if<00:13:20.620> that<00:13:20.829> we 00:13:20.970 --> 00:13:20.980 align:start position:0% chain as messages now this if that we 00:13:20.980 --> 00:13:23.910 align:start position:0% chain as messages now this if that we later<00:13:21.250> we<00:13:21.519> want<00:13:21.699> a<00:13:21.790> chasm<00:13:22.180> and<00:13:22.420> the<00:13:23.110> spot 00:13:23.910 --> 00:13:23.920 align:start position:0% later we want a chasm and the spot 00:13:23.920 --> 00:13:27.269 align:start position:0% later we want a chasm and the spot contract<00:13:24.339> right<00:13:24.820> feisty<00:13:25.269> it<00:13:25.329> is<00:13:25.660> not<00:13:25.810> true<00:13:26.279> and 00:13:27.269 --> 00:13:27.279 align:start position:0% contract right feisty it is not true and 00:13:27.279 --> 00:13:31.620 align:start position:0% contract right feisty it is not true and only<00:13:28.320> drop<00:13:29.320> has<00:13:29.500> a<00:13:29.529> signal<00:13:29.980> on<00:13:30.100> both<00:13:30.449> big<00:13:31.449> food 00:13:31.620 --> 00:13:31.630 align:start position:0% only drop has a signal on both big food 00:13:31.630 --> 00:13:36.000 align:start position:0% only drop has a signal on both big food is<00:13:31.750> bad<00:13:32.940> so<00:13:33.940> what<00:13:33.970> is<00:13:34.570> great<00:13:34.750> on<00:13:34.930> yet<00:13:35.140> so<00:13:35.380> we 00:13:36.000 --> 00:13:36.010 align:start position:0% is bad so what is great on yet so we 00:13:36.010 --> 00:13:37.350 align:start position:0% is bad so what is great on yet so we have<00:13:36.040> two<00:13:36.339> layers<00:13:36.640> the<00:13:36.850> first<00:13:37.000> layer<00:13:37.149> is 00:13:37.350 --> 00:13:37.360 align:start position:0% have two layers the first layer is 00:13:37.360 --> 00:13:40.350 align:start position:0% have two layers the first layer is basically<00:13:37.899> the<00:13:38.170> toy<00:13:38.350> player<00:13:39.029> it's<00:13:40.029> a<00:13:40.120> smart 00:13:40.350 --> 00:13:40.360 align:start position:0% basically the toy player it's a smart 00:13:40.360 --> 00:13:42.389 align:start position:0% basically the toy player it's a smart contract<00:13:40.510> that<00:13:40.899> it's<00:13:41.560> in<00:13:41.709> the<00:13:41.800> question<00:13:42.130> and 00:13:42.389 --> 00:13:42.399 align:start position:0% contract that it's in the question and 00:13:42.399 --> 00:13:43.310 align:start position:0% contract that it's in the question and answer<00:13:42.430> and 00:13:43.310 --> 00:13:43.320 align:start position:0% answer and 00:13:43.320 --> 00:13:47.210 align:start position:0% answer and traitor<00:13:43.560> but<00:13:44.330> that's<00:13:45.330> the<00:13:45.830> interface<00:13:46.830> when 00:13:47.210 --> 00:13:47.220 align:start position:0% traitor but that's the interface when 00:13:47.220 --> 00:13:48.670 align:start position:0% traitor but that's the interface when atomic<00:13:47.370> what<00:13:47.670> we<00:13:47.760> call<00:13:47.940> semaphore<00:13:48.420> and 00:13:48.670 --> 00:13:48.680 align:start position:0% atomic what we call semaphore and 00:13:48.680 --> 00:13:52.120 align:start position:0% atomic what we call semaphore and semaphore<00:13:49.680> is<00:13:50.070> like<00:13:50.430> the<00:13:50.550> base<00:13:50.760> layer<00:13:51.030> for 00:13:52.120 --> 00:13:52.130 align:start position:0% semaphore is like the base layer for 00:13:52.130 --> 00:13:54.680 align:start position:0% semaphore is like the base layer for decades<00:13:53.130> now<00:13:53.400> osteo<00:13:53.880> knowledge<00:13:54.150> applications 00:13:54.680 --> 00:13:54.690 align:start position:0% decades now osteo knowledge applications 00:13:54.690 --> 00:13:57.650 align:start position:0% decades now osteo knowledge applications like<00:13:54.990> this<00:13:55.200> so<00:13:56.040> semaphores<00:13:56.610> what<00:13:56.880> we<00:13:57.240> also<00:13:57.420> use 00:13:57.650 --> 00:13:57.660 align:start position:0% like this so semaphores what we also use 00:13:57.660 --> 00:14:01.520 align:start position:0% like this so semaphores what we also use posnick<00:13:58.050> so<00:13:59.180> smoke<00:14:00.180> simplify<00:14:00.660> so<00:14:00.720> if<00:14:01.140> i<00:14:01.230> stupid 00:14:01.520 --> 00:14:01.530 align:start position:0% posnick so smoke simplify so if i stupid 00:14:01.530 --> 00:14:05.630 align:start position:0% posnick so smoke simplify so if i stupid generalize<00:14:02.010> what<00:14:02.640> it<00:14:02.790> does<00:14:03.000> basically<00:14:04.400> is<00:14:05.400> two 00:14:05.630 --> 00:14:05.640 align:start position:0% generalize what it does basically is two 00:14:05.640 --> 00:14:07.940 align:start position:0% generalize what it does basically is two things<00:14:05.960> first<00:14:06.960> thing<00:14:07.050> is<00:14:07.350> that<00:14:07.500> it<00:14:07.650> allows<00:14:07.770> you 00:14:07.940 --> 00:14:07.950 align:start position:0% things first thing is that it allows you 00:14:07.950 --> 00:14:09.440 align:start position:0% things first thing is that it allows you to<00:14:08.010> register<00:14:08.340> your<00:14:08.640> identity 00:14:09.440 --> 00:14:09.450 align:start position:0% to register your identity 00:14:09.450 --> 00:14:12.620 align:start position:0% to register your identity second<00:14:10.350> thing<00:14:10.530> allows<00:14:11.130> anybody<00:14:11.790> in<00:14:12.180> this<00:14:12.330> poor 00:14:12.620 --> 00:14:12.630 align:start position:0% second thing allows anybody in this poor 00:14:12.630 --> 00:14:16.880 align:start position:0% second thing allows anybody in this poor identities<00:14:13.170> to<00:14:13.670> signal<00:14:14.670> registry<00:14:15.470> by<00:14:16.470> signal 00:14:16.880 --> 00:14:16.890 align:start position:0% identities to signal registry by signal 00:14:16.890 --> 00:14:19.580 align:start position:0% identities to signal registry by signal and<00:14:17.010> means<00:14:17.160> like<00:14:17.400> comcast<00:14:18.030> any<00:14:18.570> string<00:14:19.110> to 00:14:19.580 --> 00:14:19.590 align:start position:0% and means like comcast any string to 00:14:19.590 --> 00:14:23.420 align:start position:0% and means like comcast any string to these<00:14:20.100> will<00:14:20.570> not<00:14:21.570> change<00:14:21.920> but<00:14:22.920> when<00:14:23.160> they<00:14:23.250> do 00:14:23.420 --> 00:14:23.430 align:start position:0% these will not change but when they do 00:14:23.430 --> 00:14:25.520 align:start position:0% these will not change but when they do that<00:14:23.610> they<00:14:24.000> have<00:14:24.210> to<00:14:24.240> prove<00:14:24.540> that<00:14:24.600> they<00:14:25.500> are 00:14:25.520 --> 00:14:25.530 align:start position:0% that they have to prove that they are 00:14:25.530 --> 00:14:28.250 align:start position:0% that they have to prove that they are one<00:14:25.920> of<00:14:26.040> the<00:14:26.160> registered<00:14:26.730> identities<00:14:27.260> that 00:14:28.250 --> 00:14:28.260 align:start position:0% one of the registered identities that 00:14:28.260 --> 00:14:31.850 align:start position:0% one of the registered identities that had<00:14:28.640> measures<00:14:29.640> on<00:14:29.760> their<00:14:29.880> self<00:14:30.180> study<00:14:30.560> so<00:14:31.560> from 00:14:31.850 --> 00:14:31.860 align:start position:0% had measures on their self study so from 00:14:31.860 --> 00:14:34.130 align:start position:0% had measures on their self study so from an<00:14:31.950> attackers<00:14:32.400> wannabe<00:14:33.030> all<00:14:33.750> they<00:14:33.930> know<00:14:34.110> is 00:14:34.130 --> 00:14:34.140 align:start position:0% an attackers wannabe all they know is 00:14:34.140 --> 00:14:36.560 align:start position:0% an attackers wannabe all they know is that<00:14:34.440> this<00:14:34.590> list<00:14:35.010> of<00:14:35.250> registered<00:14:35.760> identities 00:14:36.560 --> 00:14:36.570 align:start position:0% that this list of registered identities 00:14:36.570 --> 00:14:39.050 align:start position:0% that this list of registered identities and<00:14:37.040> that's<00:14:38.040> the<00:14:38.130> base<00:14:38.250> of<00:14:38.400> signals<00:14:38.820> but<00:14:39.000> you 00:14:39.050 --> 00:14:39.060 align:start position:0% and that's the base of signals but you 00:14:39.060 --> 00:14:42.710 align:start position:0% and that's the base of signals but you don't<00:14:39.300> know<00:14:39.480> which<00:14:39.660> singer<00:14:40.250> is<00:14:41.540> linked<00:14:42.540> to 00:14:42.710 --> 00:14:42.720 align:start position:0% don't know which singer is linked to 00:14:42.720 --> 00:14:49.210 align:start position:0% don't know which singer is linked to which<00:14:43.400> identity<00:14:45.230> so<00:14:46.230> in<00:14:46.730> the<00:14:47.730> same<00:14:47.970> way 00:14:49.210 --> 00:14:49.220 align:start position:0% which identity so in the same way 00:14:49.220 --> 00:14:50.800 align:start position:0% which identity so in the same way and<00:14:49.460> an<00:14:49.760> attack<00:14:50.060> that<00:14:50.120> noses<00:14:50.600> that<00:14:50.720> they 00:14:50.800 --> 00:14:50.810 align:start position:0% and an attack that noses that they 00:14:50.810 --> 00:14:52.720 align:start position:0% and an attack that noses that they stopped<00:14:51.050> attendees<00:14:51.620> who<00:14:51.980> have<00:14:52.220> registered<00:14:52.370> on 00:14:52.720 --> 00:14:52.730 align:start position:0% stopped attendees who have registered on 00:14:52.730 --> 00:14:55.630 align:start position:0% stopped attendees who have registered on his<00:14:52.970> lap<00:14:53.150> they<00:14:53.930> notice<00:14:54.320> a<00:14:54.350> bunch<00:14:54.590> of<00:14:54.770> votes<00:14:55.280> but 00:14:55.630 --> 00:14:55.640 align:start position:0% his lap they notice a bunch of votes but 00:14:55.640 --> 00:15:00.040 align:start position:0% his lap they notice a bunch of votes but I<00:14:56.300> don't<00:14:56.570> know<00:14:56.720> which<00:14:57.020> identity<00:14:58.630> is<00:14:59.630> meant<00:14:59.960> to 00:15:00.040 --> 00:15:00.050 align:start position:0% I don't know which identity is meant to 00:15:00.050 --> 00:15:02.890 align:start position:0% I don't know which identity is meant to wish<00:15:00.170> vote<00:15:00.460> unless<00:15:01.460> everybody<00:15:02.210> was<00:15:02.390> yes<00:15:02.660> to 00:15:02.890 --> 00:15:02.900 align:start position:0% wish vote unless everybody was yes to 00:15:02.900 --> 00:15:06.460 align:start position:0% wish vote unless everybody was yes to having<00:15:03.500> that<00:15:03.740> consistent<00:15:04.280> well<00:15:04.400> Cyrus<00:15:05.470> or 00:15:06.460 --> 00:15:06.470 align:start position:0% having that consistent well Cyrus or 00:15:06.470 --> 00:15:08.830 align:start position:0% having that consistent well Cyrus or unless<00:15:07.190> there<00:15:07.460> is<00:15:07.490> only<00:15:07.940> one<00:15:08.180> percent<00:15:08.480> voting 00:15:08.830 --> 00:15:08.840 align:start position:0% unless there is only one percent voting 00:15:08.840 --> 00:15:10.300 align:start position:0% unless there is only one percent voting they're<00:15:09.080> somewhat<00:15:09.740> obvious 00:15:10.300 --> 00:15:10.310 align:start position:0% they're somewhat obvious 00:15:10.310 --> 00:15:14.380 align:start position:0% they're somewhat obvious so<00:15:11.560> this<00:15:12.560> offensive<00:15:13.100> depends<00:15:13.580> on<00:15:13.730> fire<00:15:14.210> to 00:15:14.380 --> 00:15:14.390 align:start position:0% so this offensive depends on fire to 00:15:14.390 --> 00:15:16.270 align:start position:0% so this offensive depends on fire to succeed<00:15:14.720> invested<00:15:15.380> half<00:15:15.560> depends<00:15:16.070> on<00:15:16.160> having 00:15:16.270 --> 00:15:16.280 align:start position:0% succeed invested half depends on having 00:15:16.280 --> 00:15:20.610 align:start position:0% succeed invested half depends on having a<00:15:16.460> lot<00:15:16.640> of<00:15:17.000> poor<00:15:17.300> participants<00:15:18.080> in<00:15:18.260> school 00:15:20.610 --> 00:15:20.620 align:start position:0% a lot of poor participants in school 00:15:20.620 --> 00:15:24.010 align:start position:0% a lot of poor participants in school otherwise<00:15:21.760> you<00:15:22.760> can<00:15:23.000> use<00:15:23.030> two<00:15:23.390> restrictions<00:15:23.540> I 00:15:24.010 --> 00:15:24.020 align:start position:0% otherwise you can use two restrictions I 00:15:24.020 --> 00:15:28.300 align:start position:0% otherwise you can use two restrictions I got<00:15:24.230> over<00:15:25.160> it<00:15:25.190> or<00:15:25.400> not<00:15:25.520> and<00:15:27.070> semaphore<00:15:28.070> is 00:15:28.300 --> 00:15:28.310 align:start position:0% got over it or not and semaphore is 00:15:28.310 --> 00:15:30.250 align:start position:0% got over it or not and semaphore is basically<00:15:28.640> to<00:15:28.940> reiterate<00:15:29.210> is<00:15:29.600> a<00:15:29.630> base<00:15:29.870> layers 00:15:30.250 --> 00:15:30.260 align:start position:0% basically to reiterate is a base layers 00:15:30.260 --> 00:15:32.200 align:start position:0% basically to reiterate is a base layers for<00:15:30.470> these<00:15:30.770> applications<00:15:31.610> other 00:15:32.200 --> 00:15:32.210 align:start position:0% for these applications other 00:15:32.210 --> 00:15:35.410 align:start position:0% for these applications other applications<00:15:32.810> are<00:15:32.960> like<00:15:33.050> a<00:15:33.080> mixer<00:15:34.420> anonymous 00:15:35.410 --> 00:15:35.420 align:start position:0% applications are like a mixer anonymous 00:15:35.420 --> 00:15:41.290 align:start position:0% applications are like a mixer anonymous pocket<00:15:36.760> even<00:15:39.670> probabilistic<00:15:40.670> micro<00:15:40.910> payments 00:15:41.290 --> 00:15:41.300 align:start position:0% pocket even probabilistic micro payments 00:15:41.300 --> 00:15:45.010 align:start position:0% pocket even probabilistic micro payments so<00:15:41.930> there's<00:15:42.410> a<00:15:42.470> few<00:15:43.100> ideas<00:15:43.630> so<00:15:44.630> this<00:15:44.750> comes 00:15:45.010 --> 00:15:45.020 align:start position:0% so there's a few ideas so this comes 00:15:45.020 --> 00:15:46.900 align:start position:0% so there's a few ideas so this comes from<00:15:45.170> very<00:15:45.350> high<00:15:45.530> pan<00:15:45.770> and<00:15:46.010> Quebec<00:15:46.370> and<00:15:46.730> from 00:15:46.900 --> 00:15:46.910 align:start position:0% from very high pan and Quebec and from 00:15:46.910 --> 00:15:51.370 align:start position:0% from very high pan and Quebec and from here<00:15:47.060> and<00:15:47.650> they've<00:15:48.650> been<00:15:49.510> like<00:15:50.510> I<00:15:50.750> think<00:15:51.200> it 00:15:51.370 --> 00:15:51.380 align:start position:0% here and they've been like I think it 00:15:51.380 --> 00:15:52.420 align:start position:0% here and they've been like I think it under<00:15:51.620> stock<00:15:51.800> states<00:15:52.010> have<00:15:52.100> been<00:15:52.160> talking 00:15:52.420 --> 00:15:52.430 align:start position:0% under stock states have been talking 00:15:52.430 --> 00:15:54.370 align:start position:0% under stock states have been talking about<00:15:52.520> some<00:15:52.820> beforehand<00:15:53.360> this<00:15:53.870> is<00:15:53.990> just<00:15:54.170> one 00:15:54.370 --> 00:15:54.380 align:start position:0% about some beforehand this is just one 00:15:54.380 --> 00:15:56.550 align:start position:0% about some beforehand this is just one application 00:15:56.550 --> 00:15:56.560 align:start position:0% 00:15:56.560 --> 00:16:01.480 align:start position:0% yeah<00:15:58.180> okay<00:15:59.180> so<00:15:59.540> if<00:16:00.110> I<00:16:00.230> have<00:16:00.350> it<00:16:00.470> go<00:16:00.800> even<00:16:01.250> deeper 00:16:01.480 --> 00:16:01.490 align:start position:0% yeah okay so if I have it go even deeper 00:16:01.490 --> 00:16:04.540 align:start position:0% yeah okay so if I have it go even deeper into<00:16:01.880> the<00:16:02.060> Sun<00:16:02.810> the<00:16:03.650> Sun<00:16:03.890> opposing<00:16:04.280> a<00:16:04.370> star 00:16:04.540 --> 00:16:04.550 align:start position:0% into the Sun the Sun opposing a star 00:16:04.550 --> 00:16:12.710 align:start position:0% into the Sun the Sun opposing a star circuit<00:16:05.560> and<00:16:06.560> any<00:16:06.740> questions<00:16:07.160> about<00:16:07.670> this 00:16:12.710 --> 00:16:12.720 align:start position:0% 00:16:12.720 --> 00:16:16.730 align:start position:0% seem<00:16:13.350> to<00:16:13.910> do<00:16:14.910> like<00:16:15.209> conventional<00:16:15.740> election 00:16:16.730 --> 00:16:16.740 align:start position:0% seem to do like conventional election 00:16:16.740 --> 00:16:22.240 align:start position:0% seem to do like conventional election you<00:16:17.310> first<00:16:17.639> have<00:16:17.879> to<00:16:17.910> register<00:16:18.540> everyone 00:16:22.240 --> 00:16:22.250 align:start position:0% 00:16:22.250 --> 00:16:27.499 align:start position:0% expect<00:16:23.420> oh<00:16:24.420> well<00:16:24.930> I<00:16:25.829> I<00:16:26.459> can't<00:16:26.939> think<00:16:27.149> that<00:16:27.329> this 00:16:27.499 --> 00:16:27.509 align:start position:0% expect oh well I I can't think that this 00:16:27.509 --> 00:16:29.389 align:start position:0% expect oh well I I can't think that this would<00:16:27.689> be<00:16:27.899> useful<00:16:28.079> for<00:16:28.439> national<00:16:29.009> induction 00:16:29.389 --> 00:16:29.399 align:start position:0% would be useful for national induction 00:16:29.399 --> 00:16:33.290 align:start position:0% would be useful for national induction just<00:16:30.470> because<00:16:31.470> that's<00:16:31.589> what<00:16:31.709> the<00:16:32.300> logistics 00:16:33.290 --> 00:16:33.300 align:start position:0% just because that's what the logistics 00:16:33.300 --> 00:16:37.009 align:start position:0% just because that's what the logistics way<00:16:34.170> to<00:16:34.230> have<00:16:34.850> these<00:16:35.850> securities<00:16:36.329> the<00:16:36.779> stakes 00:16:37.009 --> 00:16:37.019 align:start position:0% way to have these securities the stakes 00:16:37.019 --> 00:16:40.309 align:start position:0% way to have these securities the stakes are<00:16:37.170> way<00:16:37.199> too<00:16:37.350> high<00:16:37.500> and<00:16:38.149> I<00:16:39.149> if<00:16:39.720> someone<00:16:40.050> if 00:16:40.309 --> 00:16:40.319 align:start position:0% are way too high and I if someone if 00:16:40.319 --> 00:16:43.550 align:start position:0% are way too high and I if someone if this<00:16:40.769> gets<00:16:40.949> hacked<00:16:41.250> then<00:16:41.579> then<00:16:42.509> the<00:16:42.779> country 00:16:43.550 --> 00:16:43.560 align:start position:0% this gets hacked then then the country 00:16:43.560 --> 00:16:47.829 align:start position:0% this gets hacked then then the country actually<00:16:44.189> gets<00:16:44.490> a<00:16:44.610> that<00:16:45.000> is<00:16:45.120> not<00:16:45.269> so<00:16:45.420> fun<00:16:45.779> oh 00:16:47.829 --> 00:16:47.839 align:start position:0% actually gets a that is not so fun oh 00:16:47.839 --> 00:16:53.900 align:start position:0% actually gets a that is not so fun oh but<00:16:48.839> what<00:16:49.230> is<00:16:49.800> like<00:16:50.160> analogous<00:16:50.850> to<00:16:51.800> like<00:16:52.910> so 00:16:53.900 --> 00:16:53.910 align:start position:0% but what is like analogous to like so 00:16:53.910 --> 00:16:56.230 align:start position:0% but what is like analogous to like so it's<00:16:54.060> for<00:16:54.300> example<00:16:54.600> Singapore<00:16:55.019> and<00:16:55.170> from 00:16:56.230 --> 00:16:56.240 align:start position:0% it's for example Singapore and from 00:16:56.240 --> 00:16:58.400 align:start position:0% it's for example Singapore and from that's<00:16:57.240> this<00:16:57.480> way 00:16:58.400 --> 00:16:58.410 align:start position:0% that's this way 00:16:58.410 --> 00:17:01.340 align:start position:0% that's this way so<00:16:59.250> Singapore's<00:17:00.149> independence<00:17:00.360> was<00:17:01.170> like 00:17:01.340 --> 00:17:01.350 align:start position:0% so Singapore's independence was like 00:17:01.350 --> 00:17:04.460 align:start position:0% so Singapore's independence was like 1965<00:17:02.160> and<00:17:02.819> even<00:17:03.089> then<00:17:03.329> when<00:17:03.750> there<00:17:03.930> was<00:17:04.020> there 00:17:04.460 --> 00:17:04.470 align:start position:0% 1965 and even then when there was there 00:17:04.470 --> 00:17:07.309 align:start position:0% 1965 and even then when there was there were<00:17:04.530> elections<00:17:05.839> people<00:17:06.839> weren't<00:17:06.959> all<00:17:07.140> that 00:17:07.309 --> 00:17:07.319 align:start position:0% were elections people weren't all that 00:17:07.319 --> 00:17:11.329 align:start position:0% were elections people weren't all that they<00:17:07.439> were<00:17:07.620> secret<00:17:08.209> and<00:17:09.209> after<00:17:09.780> today<00:17:10.159> and<00:17:11.159> we 00:17:11.329 --> 00:17:11.339 align:start position:0% they were secret and after today and we 00:17:11.339 --> 00:17:13.010 align:start position:0% they were secret and after today and we hear<00:17:11.520> this<00:17:11.730> I<00:17:11.939> mean<00:17:12.089> I<00:17:12.240> mean<00:17:12.360> every<00:17:12.510> five<00:17:12.809> years 00:17:13.010 --> 00:17:13.020 align:start position:0% hear this I mean I mean every five years 00:17:13.020 --> 00:17:15.049 align:start position:0% hear this I mean I mean every five years of<00:17:13.169> the<00:17:13.230> connection<00:17:13.620> the<00:17:14.549> government<00:17:14.880> says 00:17:15.049 --> 00:17:15.059 align:start position:0% of the connection the government says 00:17:15.059 --> 00:17:16.640 align:start position:0% of the connection the government says you're<00:17:15.449> vollis<00:17:15.750> secret<00:17:16.079> because<00:17:16.350> they<00:17:16.470> want 00:17:16.640 --> 00:17:16.650 align:start position:0% you're vollis secret because they want 00:17:16.650 --> 00:17:19.460 align:start position:0% you're vollis secret because they want to<00:17:16.679> instill<00:17:17.039> certain<00:17:17.309> a<00:17:17.549> lot<00:17:17.699> of<00:17:18.169> trust<00:17:19.169> that 00:17:19.460 --> 00:17:19.470 align:start position:0% to instill certain a lot of trust that 00:17:19.470 --> 00:17:23.120 align:start position:0% to instill certain a lot of trust that network<00:17:20.220> will<00:17:20.640> not<00:17:20.669> be<00:17:20.819> attractive<00:17:21.780> and<00:17:22.130> and 00:17:23.120 --> 00:17:23.130 align:start position:0% network will not be attractive and and 00:17:23.130 --> 00:17:24.350 align:start position:0% network will not be attractive and and it's<00:17:23.309> likes<00:17:23.579> to<00:17:23.760> like<00:17:23.939> to<00:17:24.089> believe<00:17:24.299> that 00:17:24.350 --> 00:17:24.360 align:start position:0% it's likes to like to believe that 00:17:24.360 --> 00:17:25.460 align:start position:0% it's likes to like to believe that because<00:17:24.839> if<00:17:24.990> they<00:17:25.049> don't<00:17:25.169> believe<00:17:25.439> that 00:17:25.460 --> 00:17:25.470 align:start position:0% because if they don't believe that 00:17:25.470 --> 00:17:29.870 align:start position:0% because if they don't believe that they're<00:17:25.799> not<00:17:25.890> gonna<00:17:26.069> vote<00:17:28.370> in<00:17:29.370> the<00:17:29.549> way<00:17:29.700> that 00:17:29.870 --> 00:17:29.880 align:start position:0% they're not gonna vote in the way that 00:17:29.880 --> 00:17:32.120 align:start position:0% they're not gonna vote in the way that they<00:17:30.000> want<00:17:30.210> to<00:17:30.270> become<00:17:30.870> feel<00:17:31.320> out<00:17:31.650> of<00:17:31.950> some 00:17:32.120 --> 00:17:32.130 align:start position:0% they want to become feel out of some 00:17:32.130 --> 00:17:35.419 align:start position:0% they want to become feel out of some kind<00:17:32.280> of<00:17:32.340> my<00:17:32.490> sense<00:17:32.730> of<00:17:33.230> anything<00:17:34.230> if<00:17:34.710> we<00:17:35.250> don't 00:17:35.419 --> 00:17:35.429 align:start position:0% kind of my sense of anything if we don't 00:17:35.429 --> 00:17:37.789 align:start position:0% kind of my sense of anything if we don't have<00:17:35.640> that<00:17:35.669> in<00:17:36.059> New<00:17:36.330> Zealand<00:17:36.360> than<00:17:36.900> plenty<00:17:37.679> but 00:17:37.789 --> 00:17:37.799 align:start position:0% have that in New Zealand than plenty but 00:17:37.799 --> 00:17:39.200 align:start position:0% have that in New Zealand than plenty but on<00:17:37.919> the<00:17:38.010> Dow<00:17:38.159> you<00:17:38.610> know<00:17:38.669> not<00:17:38.940> necessarily 00:17:39.200 --> 00:17:39.210 align:start position:0% on the Dow you know not necessarily 00:17:39.210 --> 00:17:41.090 align:start position:0% on the Dow you know not necessarily going<00:17:39.720> for<00:17:40.020> the<00:17:40.200> best<00:17:40.350> interest<00:17:40.740> of<00:17:40.799> the<00:17:40.890> doubt 00:17:41.090 --> 00:17:41.100 align:start position:0% going for the best interest of the doubt 00:17:41.100 --> 00:17:43.820 align:start position:0% going for the best interest of the doubt we<00:17:41.610> might<00:17:41.789> be<00:17:41.880> voting<00:17:42.150> for<00:17:42.179> some<00:17:42.630> kind<00:17:42.870> of<00:17:42.929> some 00:17:43.820 --> 00:17:43.830 align:start position:0% we might be voting for some kind of some 00:17:43.830 --> 00:17:46.279 align:start position:0% we might be voting for some kind of some other<00:17:44.429> generic<00:17:44.880> sensitive<00:17:45.299> which<00:17:45.929> we<00:17:46.110> don't 00:17:46.279 --> 00:17:46.289 align:start position:0% other generic sensitive which we don't 00:17:46.289 --> 00:17:47.480 align:start position:0% other generic sensitive which we don't really<00:17:46.559> want<00:17:46.860> to<00:17:46.890> rather<00:17:47.130> than<00:17:47.340> like 00:17:47.480 --> 00:17:47.490 align:start position:0% really want to rather than like 00:17:47.490 --> 00:17:49.520 align:start position:0% really want to rather than like incentives<00:17:47.789> to<00:17:48.299> try<00:17:48.360> to<00:17:48.510> spend<00:17:48.840> so<00:17:49.200> this<00:17:49.380> is 00:17:49.520 --> 00:17:49.530 align:start position:0% incentives to try to spend so this is 00:17:49.530 --> 00:17:51.260 align:start position:0% incentives to try to spend so this is just<00:17:49.650> one<00:17:49.860> option<00:17:50.039> that<00:17:50.220> might<00:17:50.760> be<00:17:50.970> able<00:17:51.120> to 00:17:51.260 --> 00:17:51.270 align:start position:0% just one option that might be able to 00:17:51.270 --> 00:17:54.330 align:start position:0% just one option that might be able to have<00:17:51.419> that<00:17:51.570> but<00:17:51.900> I<00:17:52.200> don't<00:17:52.650> anything<00:17:53.100> it<00:17:53.490> might 00:17:54.330 --> 00:17:54.340 align:start position:0% have that but I don't anything it might 00:17:54.340 --> 00:17:57.060 align:start position:0% have that but I don't anything it might election<00:17:54.900> then<00:17:55.900> it's<00:17:56.049> saying<00:17:56.200> how<00:17:56.380> they<00:17:56.770> burn 00:17:57.060 --> 00:17:57.070 align:start position:0% election then it's saying how they burn 00:17:57.070 --> 00:17:59.130 align:start position:0% election then it's saying how they burn three<00:17:57.490> votes<00:17:57.820> every<00:17:58.299> time<00:17:58.450> is<00:17:58.570> interaction<00:17:58.840> I 00:17:59.130 --> 00:17:59.140 align:start position:0% three votes every time is interaction I 00:17:59.140 --> 00:18:01.260 align:start position:0% three votes every time is interaction I mean<00:17:59.409> they'd<00:18:00.039> won<00:18:00.190> the<00:18:00.309> votes<00:18:00.490> have<00:18:00.909> been<00:18:00.970> one 00:18:01.260 --> 00:18:01.270 align:start position:0% mean they'd won the votes have been one 00:18:01.270 --> 00:18:04.529 align:start position:0% mean they'd won the votes have been one after<00:18:01.750> the<00:18:01.870> election<00:18:02.169> so<00:18:02.980> so<00:18:03.549> you<00:18:04.179> don't<00:18:04.419> know 00:18:04.529 --> 00:18:04.539 align:start position:0% after the election so so you don't know 00:18:04.539 --> 00:18:07.019 align:start position:0% after the election so so you don't know who<00:18:04.690> work<00:18:04.870> as<00:18:05.559> long<00:18:05.830> as<00:18:05.980> ya<00:18:06.340> telling<00:18:06.820> it<00:18:06.880> to<00:18:06.909> a 00:18:07.019 --> 00:18:07.029 align:start position:0% who work as long as ya telling it to a 00:18:07.029 --> 00:18:12.620 align:start position:0% who work as long as ya telling it to a friend<00:18:07.270> you<00:18:07.510> want<00:18:07.960> yes<00:18:08.169> yeah<00:18:10.049> yes<00:18:11.049> yeah 00:18:12.620 --> 00:18:12.630 align:start position:0% friend you want yes yeah yes yeah 00:18:12.630 --> 00:18:21.269 align:start position:0% friend you want yes yeah yes yeah managing<00:18:13.630> the<00:18:13.770> user<00:18:19.650> will<00:18:20.650> be<00:18:20.679> interesting<00:18:21.250> to 00:18:21.269 --> 00:18:21.279 align:start position:0% managing the user will be interesting to 00:18:21.279 --> 00:18:27.240 align:start position:0% managing the user will be interesting to let<00:18:21.700> me<00:18:22.240> use<00:18:22.510> this<00:18:22.779> other<00:18:24.029> these<00:18:25.350> like<00:18:26.350> to 00:18:27.240 --> 00:18:27.250 align:start position:0% let me use this other these like to 00:18:27.250 --> 00:18:30.600 align:start position:0% let me use this other these like to create<00:18:27.460> them<00:18:27.820> yourself<00:18:28.570> so<00:18:29.049> my<00:18:30.039> greatest<00:18:30.309> the 00:18:30.600 --> 00:18:30.610 align:start position:0% create them yourself so my greatest the 00:18:30.610 --> 00:18:41.090 align:start position:0% create them yourself so my greatest the other<00:18:32.220> is<00:18:33.220> myself<00:18:37.590> right<00:18:38.610> yeah<00:18:39.610> I<00:18:40.029> can<00:18:40.480> G<00:18:40.690> isn't 00:18:41.090 --> 00:18:41.100 align:start position:0% other is myself right yeah I can G isn't 00:18:41.100 --> 00:18:44.210 align:start position:0% other is myself right yeah I can G isn't but<00:18:42.100> it's<00:18:42.220> a<00:18:42.309> special 00:18:44.210 --> 00:18:44.220 align:start position:0% but it's a special 00:18:44.220 --> 00:18:49.649 align:start position:0% but it's a special so<00:18:46.890> that's<00:18:47.890> gladness<00:18:48.520> that<00:18:48.940> will<00:18:49.390> be<00:18:49.480> done 00:18:49.649 --> 00:18:49.659 align:start position:0% so that's gladness that will be done 00:18:49.659 --> 00:18:52.980 align:start position:0% so that's gladness that will be done suffered<00:18:50.140> of<00:18:50.260> the<00:18:50.440> affinities<00:18:50.980> up 00:18:52.980 --> 00:18:52.990 align:start position:0% suffered of the affinities up 00:18:52.990 --> 00:18:55.200 align:start position:0% suffered of the affinities up it<00:18:53.080> was<00:18:53.260> the<00:18:53.409> salt<00:18:53.649> all<00:18:53.890> six<00:18:54.399> people<00:18:54.640> ready<00:18:55.000> for 00:18:55.200 --> 00:18:55.210 align:start position:0% it was the salt all six people ready for 00:18:55.210 --> 00:18:56.909 align:start position:0% it was the salt all six people ready for what<00:18:55.360> a<00:18:55.390> serious<00:18:55.720> problem<00:18:55.929> so<00:18:56.110> I<00:18:56.289> put<00:18:56.649> a<00:18:56.679> bridge 00:18:56.909 --> 00:18:56.919 align:start position:0% what a serious problem so I put a bridge 00:18:56.919 --> 00:18:59.360 align:start position:0% what a serious problem so I put a bridge is<00:18:57.070> literally<00:18:57.370> there<00:18:58.149> this<00:18:58.299> six<00:18:58.570> thousand 00:18:59.360 --> 00:18:59.370 align:start position:0% is literally there this six thousand 00:18:59.370 --> 00:19:00.630 align:start position:0% is literally there this six thousand tokens 00:19:00.630 --> 00:19:00.640 align:start position:0% tokens 00:19:00.640 --> 00:19:02.880 align:start position:0% tokens I<00:19:00.779> could've<00:19:01.779> registered<00:19:01.960> like<00:19:02.409> a<00:19:02.440> couple 00:19:02.880 --> 00:19:02.890 align:start position:0% I could've registered like a couple 00:19:02.890 --> 00:19:04.889 align:start position:0% I could've registered like a couple other<00:19:03.399> one<00:19:03.669> that's<00:19:03.970> why<00:19:04.149> I<00:19:04.179> purchased<00:19:04.419> at<00:19:04.720> my 00:19:04.889 --> 00:19:04.899 align:start position:0% other one that's why I purchased at my 00:19:04.899 --> 00:19:07.769 align:start position:0% other one that's why I purchased at my I'm<00:19:05.260> certain<00:19:05.770> I<00:19:05.980> date<00:19:06.340> and<00:19:06.820> then<00:19:07.090> I<00:19:07.179> learned<00:19:07.360> I 00:19:07.769 --> 00:19:07.779 align:start position:0% I'm certain I date and then I learned I 00:19:07.779 --> 00:19:09.840 align:start position:0% I'm certain I date and then I learned I mean<00:19:08.559> we<00:19:08.679> are<00:19:08.770> assuming<00:19:09.039> that<00:19:09.250> each<00:19:09.669> of<00:19:09.700> us 00:19:09.840 --> 00:19:09.850 align:start position:0% mean we are assuming that each of us 00:19:09.850 --> 00:19:15.060 align:start position:0% mean we are assuming that each of us only<00:19:10.149> has<00:19:10.270> one<00:19:10.480> poor<00:19:10.840> talking<00:19:12.750> now<00:19:13.919> unless<00:19:14.919> you 00:19:15.060 --> 00:19:15.070 align:start position:0% only has one poor talking now unless you 00:19:15.070 --> 00:19:17.010 align:start position:0% only has one poor talking now unless you steal<00:19:15.580> someone<00:19:15.850> else's<00:19:15.880> condition<00:19:16.510> but 00:19:17.010 --> 00:19:17.020 align:start position:0% steal someone else's condition but 00:19:17.020 --> 00:19:19.980 align:start position:0% steal someone else's condition but nothing<00:19:17.289> I<00:19:17.380> do<00:19:17.500> about<00:19:17.590> that<00:19:17.830> I<00:19:18.720> think<00:19:19.720> he<00:19:19.809> met 00:19:19.980 --> 00:19:19.990 align:start position:0% nothing I do about that I think he met 00:19:19.990 --> 00:19:28.879 align:start position:0% nothing I do about that I think he met that<00:19:20.730> registry<00:19:21.730> registry<00:19:22.270> he<00:19:22.809> has 00:19:28.879 --> 00:19:28.889 align:start position:0% 00:19:28.889 --> 00:19:35.220 align:start position:0% yeah<00:19:29.889> yeah<00:19:30.220> yeah<00:19:33.600> yeah<00:19:34.600> that's<00:19:34.960> enough 00:19:35.220 --> 00:19:35.230 align:start position:0% yeah yeah yeah yeah that's enough 00:19:35.230 --> 00:19:37.139 align:start position:0% yeah yeah yeah yeah that's enough something<00:19:35.470> that<00:19:35.710> we<00:19:36.309> assume<00:19:36.639> that<00:19:36.700> there's<00:19:37.090> no 00:19:37.139 --> 00:19:37.149 align:start position:0% something that we assume that there's no 00:19:37.149 --> 00:19:41.490 align:start position:0% something that we assume that there's no collusion<00:19:37.860> yeah 00:19:41.490 --> 00:19:41.500 align:start position:0% 00:19:41.500 --> 00:19:43.529 align:start position:0% okay<00:19:42.190> so<00:19:42.549> this<00:19:42.850> is<00:19:43.000> officially<00:19:43.210> the<00:19:43.450> last 00:19:43.529 --> 00:19:43.539 align:start position:0% okay so this is officially the last 00:19:43.539 --> 00:19:46.799 align:start position:0% okay so this is officially the last light<00:19:44.190> because<00:19:45.190> I<00:19:45.519> expect<00:19:46.059> everything<00:19:46.330> to 00:19:46.799 --> 00:19:46.809 align:start position:0% light because I expect everything to 00:19:46.809 --> 00:19:49.220 align:start position:0% light because I expect everything to diving<00:19:47.799> into<00:19:48.070> nzk<00:19:48.370> stocks<00:19:48.610> might<00:19:48.820> be<00:19:48.970> a<00:19:49.000> bit 00:19:49.220 --> 00:19:49.230 align:start position:0% diving into nzk stocks might be a bit 00:19:49.230 --> 00:19:52.169 align:start position:0% diving into nzk stocks might be a bit complex<00:19:50.230> I<00:19:50.440> was<00:19:50.620> gonna<00:19:50.769> do<00:19:51.399> this<00:19:51.669> very<00:19:51.850> slowly 00:19:52.169 --> 00:19:52.179 align:start position:0% complex I was gonna do this very slowly 00:19:52.179 --> 00:19:56.100 align:start position:0% complex I was gonna do this very slowly and<00:19:52.510> the<00:19:52.570> survey<00:19:52.779> server<00:19:54.330> so<00:19:55.330> it<00:19:55.600> is<00:19:55.750> audience 00:19:56.100 --> 00:19:56.110 align:start position:0% and the survey server so it is audience 00:19:56.110 --> 00:19:58.320 align:start position:0% and the survey server so it is audience how<00:19:56.679> familiar<00:19:56.889> are<00:19:57.159> you<00:19:57.220> with<00:19:57.399> Stevie<00:19:57.909> snacks 00:19:58.320 --> 00:19:58.330 align:start position:0% how familiar are you with Stevie snacks 00:19:58.330 --> 00:20:00.840 align:start position:0% how familiar are you with Stevie snacks have<00:19:58.659> you<00:19:58.750> at<00:19:58.809> least<00:19:58.840> heard<00:19:59.110> about<00:19:59.289> it<00:19:59.850> alright 00:20:00.840 --> 00:20:00.850 align:start position:0% have you at least heard about it alright 00:20:00.850 --> 00:20:03.169 align:start position:0% have you at least heard about it alright as<00:20:01.029> anybody<00:20:01.360> you<00:20:01.419> go<00:20:01.570> to<00:20:01.630> see<00:20:01.840> a<00:20:01.870> star<00:20:02.169> circuit 00:20:03.169 --> 00:20:03.179 align:start position:0% as anybody you go to see a star circuit 00:20:03.179 --> 00:20:04.560 align:start position:0% as anybody you go to see a star circuit okay 00:20:04.560 --> 00:20:04.570 align:start position:0% okay 00:20:04.570 --> 00:20:09.180 align:start position:0% okay if<00:20:04.659> anybody's<00:20:07.380> alright<00:20:08.380> so<00:20:08.590> let's<00:20:08.769> just<00:20:08.830> drop 00:20:09.180 --> 00:20:09.190 align:start position:0% if anybody's alright so let's just drop 00:20:09.190 --> 00:20:14.580 align:start position:0% if anybody's alright so let's just drop into<00:20:09.370> the<00:20:09.490> coal<00:20:09.669> chubby 00:20:14.580 --> 00:20:14.590 align:start position:0% 00:20:14.590 --> 00:20:16.970 align:start position:0% [Music] 00:20:16.970 --> 00:20:16.980 align:start position:0% [Music] 00:20:16.980 --> 00:20:20.780 align:start position:0% [Music] we'll<00:20:17.970> listen<00:20:18.180> you<00:20:18.540> know<00:20:18.660> how<00:20:19.140> he<00:20:20.130> is<00:20:20.310> not<00:20:20.520> food 00:20:20.780 --> 00:20:20.790 align:start position:0% we'll listen you know how he is not food 00:20:20.790 --> 00:20:24.590 align:start position:0% we'll listen you know how he is not food what<00:20:21.090> so<00:20:21.980> who<00:20:22.980> doesn't<00:20:23.160> know<00:20:23.370> like<00:20:23.670> the<00:20:24.030> ABCs 00:20:24.590 --> 00:20:24.600 align:start position:0% what so who doesn't know like the ABCs 00:20:24.600 --> 00:20:26.900 align:start position:0% what so who doesn't know like the ABCs of<00:20:24.840> disaster<00:20:25.500> I<00:20:25.650> go<00:20:25.920> into<00:20:26.040> the<00:20:26.310> pipe<00:20:26.520> wall<00:20:26.700> and 00:20:26.900 --> 00:20:26.910 align:start position:0% of disaster I go into the pipe wall and 00:20:26.910 --> 00:20:29.330 align:start position:0% of disaster I go into the pipe wall and like<00:20:27.060> talk<00:20:27.210> about<00:20:27.420> ruining<00:20:27.870> my<00:20:28.110> vacation<00:20:28.340> key 00:20:29.330 --> 00:20:29.340 align:start position:0% like talk about ruining my vacation key 00:20:29.340 --> 00:20:33.170 align:start position:0% like talk about ruining my vacation key thing<00:20:29.610> again<00:20:31.310> okay<00:20:32.340> I<00:20:32.490> think<00:20:32.760> that's<00:20:32.880> just<00:20:32.970> I 00:20:33.170 --> 00:20:33.180 align:start position:0% thing again okay I think that's just I 00:20:33.180 --> 00:20:41.930 align:start position:0% thing again okay I think that's just I just<00:20:33.210> divided<00:20:33.630> up<00:20:33.840> on<00:20:33.960> one 00:20:41.930 --> 00:20:41.940 align:start position:0% 00:20:41.940 --> 00:20:50.730 align:start position:0% I<00:20:47.030> think<00:20:48.030> it<00:20:48.120> is 00:20:50.730 --> 00:20:50.740 align:start position:0% 00:20:50.740 --> 00:20:56.140 align:start position:0% [Music] 00:20:56.140 --> 00:20:56.150 align:start position:0% 00:20:56.150 --> 00:21:01.450 align:start position:0% I<00:21:00.130> mean 00:21:01.450 --> 00:21:01.460 align:start position:0% I mean 00:21:01.460 --> 00:21:10.350 align:start position:0% I mean [Music] 00:21:10.350 --> 00:21:10.360 align:start position:0% 00:21:10.360 --> 00:21:13.710 align:start position:0% okay<00:21:10.990> so<00:21:11.049> just<00:21:11.590> to<00:21:11.679> recap<00:21:12.309> Zika<00:21:13.240> snacks<00:21:13.480> are 00:21:13.710 --> 00:21:13.720 align:start position:0% okay so just to recap Zika snacks are 00:21:13.720 --> 00:21:16.799 align:start position:0% okay so just to recap Zika snacks are basically<00:21:14.730> the<00:21:15.730> ability<00:21:15.970> to<00:21:16.240> verify 00:21:16.799 --> 00:21:16.809 align:start position:0% basically the ability to verify 00:21:16.809 --> 00:21:20.759 align:start position:0% basically the ability to verify conversation<00:21:17.380> without<00:21:18.539> right<00:21:19.539> so<00:21:20.140> Zika 00:21:20.759 --> 00:21:20.769 align:start position:0% conversation without right so Zika 00:21:20.769 --> 00:21:22.139 align:start position:0% conversation without right so Zika snacks<00:21:20.980> and<00:21:21.130> basically<00:21:21.340> the<00:21:21.640> ability<00:21:21.880> to 00:21:22.139 --> 00:21:22.149 align:start position:0% snacks and basically the ability to 00:21:22.149 --> 00:21:24.840 align:start position:0% snacks and basically the ability to verify<00:21:22.480> interpretation<00:21:23.409> in<00:21:23.590> a<00:21:23.850> initial 00:21:24.840 --> 00:21:24.850 align:start position:0% verify interpretation in a initial 00:21:24.850 --> 00:21:26.370 align:start position:0% verify interpretation in a initial amount<00:21:25.000> of<00:21:25.059> time<00:21:25.210> dependent<00:21:25.870> understand<00:21:26.260> how 00:21:26.370 --> 00:21:26.380 align:start position:0% amount of time dependent understand how 00:21:26.380 --> 00:21:29.850 align:start position:0% amount of time dependent understand how the<00:21:26.440> national<00:21:26.890> competition<00:21:27.309> is<00:21:28.860> without 00:21:29.850 --> 00:21:29.860 align:start position:0% the national competition is without 00:21:29.860 --> 00:21:31.620 align:start position:0% the national competition is without revealing<00:21:30.279> certain<00:21:30.940> inputs<00:21:31.360> to<00:21:31.539> the 00:21:31.620 --> 00:21:31.630 align:start position:0% revealing certain inputs to the 00:21:31.630 --> 00:21:34.440 align:start position:0% revealing certain inputs to the commutation<00:21:32.220> so<00:21:33.220> for<00:21:33.669> example<00:21:34.090> let's<00:21:34.240> say<00:21:34.299> you 00:21:34.440 --> 00:21:34.450 align:start position:0% commutation so for example let's say you 00:21:34.450 --> 00:21:37.440 align:start position:0% commutation so for example let's say you want<00:21:34.510> to<00:21:34.750> say<00:21:34.929> that<00:21:36.120> you<00:21:37.120> have<00:21:37.240> a<00:21:37.299> function 00:21:37.440 --> 00:21:37.450 align:start position:0% want to say that you have a function 00:21:37.450 --> 00:21:48.210 align:start position:0% want to say that you have a function that<00:21:39.809> I<00:21:43.289> have<00:21:44.289> some<00:21:44.649> text<00:21:46.230> and<00:21:47.230> now<00:21:47.950> see<00:21:48.100> this 00:21:48.210 --> 00:21:48.220 align:start position:0% that I have some text and now see this 00:21:48.220 --> 00:21:53.159 align:start position:0% that I have some text and now see this is<00:21:48.340> a<00:21:48.370> hash<00:21:48.580> function<00:21:48.610> right<00:21:49.210> so<00:21:52.019> let's<00:21:53.019> say 00:21:53.159 --> 00:21:53.169 align:start position:0% is a hash function right so let's say 00:21:53.169 --> 00:21:54.779 align:start position:0% is a hash function right so let's say that<00:21:53.200> you<00:21:53.649> want<00:21:53.830> to<00:21:53.889> give<00:21:54.370> this<00:21:54.549> hash<00:21:54.760> function 00:21:54.779 --> 00:21:54.789 align:start position:0% that you want to give this hash function 00:21:54.789 --> 00:22:00.120 align:start position:0% that you want to give this hash function the<00:21:55.600> Hedgehog<00:21:56.080> W<00:21:56.500> is<00:21:57.210> some<00:21:58.210> consideration<00:21:59.130> so 00:22:00.120 --> 00:22:00.130 align:start position:0% the Hedgehog W is some consideration so 00:22:00.130 --> 00:22:02.610 align:start position:0% the Hedgehog W is some consideration so the<00:22:00.940> first<00:22:01.210> thing<00:22:01.450> we<00:22:01.570> do<00:22:01.720> is<00:22:02.049> that<00:22:02.380> you<00:22:02.470> can 00:22:02.610 --> 00:22:02.620 align:start position:0% the first thing we do is that you can 00:22:02.620 --> 00:22:03.690 align:start position:0% the first thing we do is that you can call<00:22:02.830> this<00:22:03.039> function<00:22:03.100> in<00:22:03.549> two<00:22:03.669> variables 00:22:03.690 --> 00:22:03.700 align:start position:0% call this function in two variables 00:22:03.700 --> 00:22:10.230 align:start position:0% call this function in two variables socket<00:22:06.029> and<00:22:07.500> now<00:22:08.500> we<00:22:08.590> have<00:22:08.860> now<00:22:09.490> we<00:22:09.519> have<00:22:09.669> a 00:22:10.230 --> 00:22:10.240 align:start position:0% socket and now we have now we have a 00:22:10.240 --> 00:22:12.690 align:start position:0% socket and now we have now we have a circuit<00:22:10.750> and<00:22:10.990> the<00:22:11.559> two<00:22:11.769> inputs<00:22:12.130> the<00:22:12.460> first 00:22:12.690 --> 00:22:12.700 align:start position:0% circuit and the two inputs the first 00:22:12.700 --> 00:22:15.720 align:start position:0% circuit and the two inputs the first thing<00:22:12.850> what<00:22:13.029> is<00:22:13.240> W<00:22:13.600> in<00:22:13.630> a<00:22:13.840> second<00:22:14.110> is<00:22:14.200> take<00:22:14.730> the 00:22:15.720 --> 00:22:15.730 align:start position:0% thing what is W in a second is take the 00:22:15.730 --> 00:22:19.769 align:start position:0% thing what is W in a second is take the code<00:22:16.029> of<00:22:16.210> F<00:22:16.450> is<00:22:16.840> incorrect<00:22:17.679> in<00:22:18.539> inliner<00:22:19.539> to 00:22:19.769 --> 00:22:19.779 align:start position:0% code of F is incorrect in inliner to 00:22:19.779 --> 00:22:21.779 align:start position:0% code of F is incorrect in inliner to make<00:22:19.929> specific<00:22:20.110> specific<00:22:20.740> language<00:22:21.070> as<00:22:21.279> used 00:22:21.779 --> 00:22:21.789 align:start position:0% make specific specific language as used 00:22:21.789 --> 00:22:26.250 align:start position:0% make specific specific language as used to<00:22:22.590> program<00:22:23.590> the<00:22:23.679> circuit<00:22:24.039> but<00:22:24.519> as<00:22:24.909> a<00:22:25.139> as<00:22:26.139> an 00:22:26.250 --> 00:22:26.260 align:start position:0% to program the circuit but as a as an 00:22:26.260 --> 00:22:32.399 align:start position:0% to program the circuit but as a as an input<00:22:26.590> of<00:22:26.710> you<00:22:26.950> and<00:22:27.450> an<00:22:28.450> input<00:22:28.630> H<00:22:29.429> so<00:22:31.169> we<00:22:32.169> want 00:22:32.399 --> 00:22:32.409 align:start position:0% input of you and an input H so we want 00:22:32.409 --> 00:22:38.460 align:start position:0% input of you and an input H so we want to<00:22:32.590> be<00:22:32.710> able<00:22:32.830> to<00:22:33.010> prove<00:22:33.669> that<00:22:33.909> we<00:22:34.269> know<00:22:35.700> W<00:22:37.470> you 00:22:38.460 --> 00:22:38.470 align:start position:0% to be able to prove that we know W you 00:22:38.470 --> 00:22:42.269 align:start position:0% to be able to prove that we know W you want<00:22:38.590> to<00:22:38.679> prove<00:22:38.860> that<00:22:38.889> we<00:22:39.039> know<00:22:39.399> that<00:22:39.669> we<00:22:41.279> that 00:22:42.269 --> 00:22:42.279 align:start position:0% want to prove that we know that we that 00:22:42.279 --> 00:22:48.330 align:start position:0% want to prove that we know that we that we<00:22:42.309> know<00:22:42.549> the<00:22:43.799> in<00:22:44.799> hex<00:22:45.100> of<00:22:45.370> a<00:22:45.549> hash<00:22:47.340> without 00:22:48.330 --> 00:22:48.340 align:start position:0% we know the in hex of a hash without 00:22:48.340 --> 00:22:51.990 align:start position:0% we know the in hex of a hash without rebuilding<00:22:48.730> one<00:22:48.880> in<00:22:49.120> Texas<00:22:50.190> so<00:22:51.190> this<00:22:51.549> matrix 00:22:51.990 --> 00:22:52.000 align:start position:0% rebuilding one in Texas so this matrix 00:22:52.000 --> 00:22:56.700 align:start position:0% rebuilding one in Texas so this matrix is<00:22:52.510> a<00:22:52.659> single<00:22:53.260> angle<00:22:53.409> and<00:22:55.080> this<00:22:56.080> is<00:22:56.139> a<00:22:56.289> common 00:22:56.700 --> 00:22:56.710 align:start position:0% is a single angle and this is a common 00:22:56.710 --> 00:22:58.550 align:start position:0% is a single angle and this is a common input 00:22:58.550 --> 00:22:58.560 align:start position:0% input 00:22:58.560 --> 00:23:01.190 align:start position:0% input so<00:22:59.480> even<00:23:00.480> though<00:23:00.570> I<00:23:00.630> say<00:23:00.810> that<00:23:00.960> this<00:23:01.050> is 00:23:01.190 --> 00:23:01.200 align:start position:0% so even though I say that this is 00:23:01.200 --> 00:23:03.590 align:start position:0% so even though I say that this is function<00:23:01.470> and<00:23:01.800> this<00:23:02.280> is<00:23:02.340> a<00:23:02.670> socket<00:23:03.030> it's 00:23:03.590 --> 00:23:03.600 align:start position:0% function and this is a socket it's 00:23:03.600 --> 00:23:05.540 align:start position:0% function and this is a socket it's important<00:23:04.110> to<00:23:04.230> know<00:23:04.380> that<00:23:04.410> we<00:23:05.130> don't<00:23:05.310> think 00:23:05.540 --> 00:23:05.550 align:start position:0% important to know that we don't think 00:23:05.550 --> 00:23:08.540 align:start position:0% important to know that we don't think about<00:23:05.730> circuits<00:23:06.270> like<00:23:06.800> like<00:23:07.800> black<00:23:07.980> boxes<00:23:08.400> we 00:23:08.540 --> 00:23:08.550 align:start position:0% about circuits like like black boxes we 00:23:08.550 --> 00:23:10.100 align:start position:0% about circuits like like black boxes we don't<00:23:08.700> think<00:23:08.820> about<00:23:08.970> them<00:23:09.270> as<00:23:09.390> input<00:23:09.810> and 00:23:10.100 --> 00:23:10.110 align:start position:0% don't think about them as input and 00:23:10.110 --> 00:23:14.360 align:start position:0% don't think about them as input and output<00:23:10.500> it's<00:23:11.130> something<00:23:11.490> that<00:23:13.070> we<00:23:14.070> thing<00:23:14.250> in 00:23:14.360 --> 00:23:14.370 align:start position:0% output it's something that we thing in 00:23:14.370 --> 00:23:18.710 align:start position:0% output it's something that we thing in terms<00:23:14.490> of<00:23:14.670> whether<00:23:15.080> this<00:23:16.220> equality<00:23:17.220> holds<00:23:17.720> we 00:23:18.710 --> 00:23:18.720 align:start position:0% terms of whether this equality holds we 00:23:18.720 --> 00:23:23.120 align:start position:0% terms of whether this equality holds we want<00:23:19.100> we<00:23:20.100> want<00:23:20.130> this<00:23:21.530> basically<00:23:22.530> encoding<00:23:23.040> a 00:23:23.120 --> 00:23:23.130 align:start position:0% want we want this basically encoding a 00:23:23.130 --> 00:23:24.470 align:start position:0% want we want this basically encoding a bunch<00:23:23.280> of<00:23:23.340> SS<00:23:23.670> statements<00:23:24.090> Antichrist 00:23:24.470 --> 00:23:24.480 align:start position:0% bunch of SS statements Antichrist 00:23:24.480 --> 00:23:26.690 align:start position:0% bunch of SS statements Antichrist statements<00:23:24.900> inside<00:23:25.620> the<00:23:25.680> socket<00:23:26.190> so<00:23:26.430> that 00:23:26.690 --> 00:23:26.700 align:start position:0% statements inside the socket so that 00:23:26.700 --> 00:23:29.570 align:start position:0% statements inside the socket so that this<00:23:27.600> circuit<00:23:28.050> or<00:23:28.230> this<00:23:28.770> proof<00:23:29.040> of<00:23:29.190> you<00:23:29.280> valid 00:23:29.570 --> 00:23:29.580 align:start position:0% this circuit or this proof of you valid 00:23:29.580 --> 00:23:32.530 align:start position:0% this circuit or this proof of you valid if<00:23:29.790> and<00:23:29.970> only<00:23:30.090> if<00:23:30.240> all<00:23:31.110> the<00:23:31.470> constraints<00:23:31.920> over 00:23:32.530 --> 00:23:32.540 align:start position:0% if and only if all the constraints over 00:23:32.540 --> 00:23:34.700 align:start position:0% if and only if all the constraints over so<00:23:33.540> we're<00:23:33.750> not<00:23:33.900> like<00:23:34.140> it's<00:23:34.440> not<00:23:34.470> like<00:23:34.590> a 00:23:34.700 --> 00:23:34.710 align:start position:0% so we're not like it's not like a 00:23:34.710 --> 00:23:37.900 align:start position:0% so we're not like it's not like a function<00:23:35.160> in<00:23:35.250> the<00:23:35.430> in<00:23:35.730> the<00:23:36.090> traditional<00:23:36.540> sense 00:23:37.900 --> 00:23:37.910 align:start position:0% function in the in the traditional sense 00:23:37.910 --> 00:23:45.340 align:start position:0% function in the in the traditional sense so<00:23:41.000> we<00:23:42.000> take<00:23:42.180> a<00:23:42.270> circuit<00:23:42.750> and<00:23:44.150> requires 00:23:45.340 --> 00:23:45.350 align:start position:0% so we take a circuit and requires 00:23:45.350 --> 00:23:49.880 align:start position:0% so we take a circuit and requires circuit<00:23:46.350> C<00:23:47.540> and<00:23:48.540> for<00:23:48.930> C<00:23:49.080> it's<00:23:49.290> not<00:23:49.350> going<00:23:49.680> to<00:23:49.740> do 00:23:49.880 --> 00:23:49.890 align:start position:0% circuit C and for C it's not going to do 00:23:49.890 --> 00:23:51.980 align:start position:0% circuit C and for C it's not going to do is<00:23:50.070> something<00:23:50.250> kind<00:23:50.490> of<00:23:50.520> trusted<00:23:50.940> set<00:23:51.120> up<00:23:51.240> so 00:23:51.980 --> 00:23:51.990 align:start position:0% is something kind of trusted set up so 00:23:51.990 --> 00:23:56.170 align:start position:0% is something kind of trusted set up so we<00:23:52.080> were<00:23:52.140> just<00:23:52.230> a<00:23:52.530> setup<00:23:52.770> you<00:23:53.210> will<00:23:54.210> take<00:23:54.600> in 00:23:56.170 --> 00:23:56.180 align:start position:0% we were just a setup you will take in 00:23:56.180 --> 00:23:59.990 align:start position:0% we were just a setup you will take in the<00:23:57.180> socket<00:23:57.630> and<00:23:58.340> then<00:23:59.340> you<00:23:59.460> run<00:23:59.640> this<00:23:59.760> process 00:23:59.990 --> 00:24:00.000 align:start position:0% the socket and then you run this process 00:24:00.000 --> 00:24:08.900 align:start position:0% the socket and then you run this process but<00:24:00.420> you<00:24:00.510> can<00:24:03.380> you<00:24:04.380> get<00:24:04.560> two<00:24:04.770> keys<00:24:05.420> and<00:24:07.670> you<00:24:08.670> get 00:24:08.900 --> 00:24:08.910 align:start position:0% but you can you get two keys and you get 00:24:08.910 --> 00:24:12.950 align:start position:0% but you can you get two keys and you get some<00:24:09.210> toxic<00:24:09.750> waste<00:24:10.250> so<00:24:11.690> you<00:24:12.690> might<00:24:12.870> this 00:24:12.950 --> 00:24:12.960 align:start position:0% some toxic waste so you might this 00:24:12.960 --> 00:24:14.510 align:start position:0% some toxic waste so you might this process<00:24:13.350> contrast<00:24:13.950> set<00:24:14.190> up<00:24:14.280> you<00:24:14.400> get 00:24:14.510 --> 00:24:14.520 align:start position:0% process contrast set up you get 00:24:14.520 --> 00:24:17.870 align:start position:0% process contrast set up you get verification<00:24:14.970> key<00:24:15.450> of<00:24:15.690> proving<00:24:16.440> key<00:24:16.650> and<00:24:16.920> it 00:24:17.870 --> 00:24:17.880 align:start position:0% verification key of proving key and it 00:24:17.880 --> 00:24:20.960 align:start position:0% verification key of proving key and it also<00:24:18.000> produces<00:24:18.390> some<00:24:18.800> toxic<00:24:19.800> waste<00:24:20.010> which<00:24:20.280> you 00:24:20.960 --> 00:24:20.970 align:start position:0% also produces some toxic waste which you 00:24:20.970 --> 00:24:23.540 align:start position:0% also produces some toxic waste which you must<00:24:21.240> discard<00:24:21.800> otherwise<00:24:22.800> you<00:24:22.980> can<00:24:23.160> prove<00:24:23.340> you 00:24:23.540 --> 00:24:23.550 align:start position:0% must discard otherwise you can prove you 00:24:23.550 --> 00:24:26.650 align:start position:0% must discard otherwise you can prove you can<00:24:23.730> generate<00:24:24.240> figures<00:24:24.660> and<00:24:25.410> I<00:24:25.500> get<00:24:25.650> Tom<00:24:25.800> on 00:24:26.650 --> 00:24:26.660 align:start position:0% can generate figures and I get Tom on 00:24:26.660 --> 00:24:30.740 align:start position:0% can generate figures and I get Tom on how<00:24:27.660> to<00:24:27.720> do<00:24:28.020> this<00:24:28.160> how<00:24:29.160> to<00:24:29.190> discount<00:24:29.640> this<00:24:29.790> in<00:24:30.660> a 00:24:30.740 --> 00:24:30.750 align:start position:0% how to do this how to discount this in a 00:24:30.750 --> 00:24:34.420 align:start position:0% how to do this how to discount this in a way<00:24:30.870> that's<00:24:31.110> less<00:24:32.360> non-transitive 00:24:34.420 --> 00:24:34.430 align:start position:0% way that's less non-transitive 00:24:34.430 --> 00:24:41.060 align:start position:0% way that's less non-transitive so<00:24:37.580> when<00:24:38.580> you<00:24:38.730> want<00:24:39.000> to<00:24:39.270> generate<00:24:39.990> the<00:24:40.950> exam 00:24:41.060 --> 00:24:41.070 align:start position:0% so when you want to generate the exam 00:24:41.070 --> 00:24:47.560 align:start position:0% so when you want to generate the exam proof<00:24:41.460> you<00:24:41.940> need<00:24:42.150> a<00:24:42.180> piggy<00:24:44.510> so<00:24:45.510> with<00:24:45.930> a<00:24:45.960> pinky 00:24:47.560 --> 00:24:47.570 align:start position:0% proof you need a piggy so with a pinky 00:24:47.570 --> 00:24:52.159 align:start position:0% proof you need a piggy so with a pinky so<00:24:48.570> in<00:24:48.720> generate<00:24:49.050> proof 00:24:52.159 --> 00:24:52.169 align:start position:0% 00:24:52.169 --> 00:24:55.980 align:start position:0% you<00:24:53.169> need<00:24:53.320> a<00:24:53.350> circuit<00:24:54.120> ended<00:24:55.120> up<00:24:55.270> proving<00:24:55.659> key 00:24:55.980 --> 00:24:55.990 align:start position:0% you need a circuit ended up proving key 00:24:55.990 --> 00:25:02.820 align:start position:0% you need a circuit ended up proving key and<00:24:56.350> you<00:24:57.250> need<00:24:57.490> the<00:25:00.419> witness<00:25:01.419> the<00:25:02.350> witness<00:25:02.500> is 00:25:02.820 --> 00:25:02.830 align:start position:0% and you need the witness the witness is 00:25:02.830 --> 00:25:07.169 align:start position:0% and you need the witness the witness is a<00:25:02.860> secret<00:25:03.279> agent<00:25:03.309> good<00:25:05.549> do<00:25:06.549> we<00:25:06.640> need<00:25:06.760> a<00:25:06.850> public 00:25:07.169 --> 00:25:07.179 align:start position:0% a secret agent good do we need a public 00:25:07.179 --> 00:25:14.070 align:start position:0% a secret agent good do we need a public input<00:25:08.760> don't<00:25:09.760> things<00:25:09.909> alright<00:25:12.390> well<00:25:13.390> major<00:25:13.929> it 00:25:14.070 --> 00:25:14.080 align:start position:0% input don't things alright well major it 00:25:14.080 --> 00:25:15.570 align:start position:0% input don't things alright well major it proved<00:25:14.380> to<00:25:14.500> me<00:25:14.590> in<00:25:14.650> the<00:25:14.740> public<00:25:15.039> I<00:25:15.190> don't<00:25:15.309> I 00:25:15.570 --> 00:25:15.580 align:start position:0% proved to me in the public I don't I 00:25:15.580 --> 00:25:17.700 align:start position:0% proved to me in the public I don't I don't<00:25:15.730> think<00:25:15.880> really<00:25:16.690> verify<00:25:17.289> it<00:25:17.350> when<00:25:17.650> you 00:25:17.700 --> 00:25:17.710 align:start position:0% don't think really verify it when you 00:25:17.710 --> 00:25:22.110 align:start position:0% don't think really verify it when you need<00:25:17.830> anybody's<00:25:18.340> money<00:25:18.370> money<00:25:20.850> let's<00:25:21.850> just<00:25:22.000> go 00:25:22.110 --> 00:25:22.120 align:start position:0% need anybody's money money let's just go 00:25:22.120 --> 00:25:34.620 align:start position:0% need anybody's money money let's just go a<00:25:22.149> bit<00:25:30.690> thank<00:25:31.690> you<00:25:31.840> yeah<00:25:32.799> so<00:25:33.309> this<00:25:33.610> it's<00:25:34.419> so 00:25:34.620 --> 00:25:34.630 align:start position:0% a bit thank you yeah so this it's so 00:25:34.630 --> 00:25:37.110 align:start position:0% a bit thank you yeah so this it's so it's<00:25:35.020> so<00:25:35.140> many<00:25:35.350> details<00:25:35.740> I<00:25:35.860> just<00:25:35.890> have<00:25:36.429> to<00:25:36.549> go 00:25:37.110 --> 00:25:37.120 align:start position:0% it's so many details I just have to go 00:25:37.120 --> 00:25:42.149 align:start position:0% it's so many details I just have to go up<00:25:37.240> there<00:25:39.480> so<00:25:40.480> we<00:25:41.230> generate<00:25:41.620> improve<00:25:41.980> this 00:25:42.149 --> 00:25:42.159 align:start position:0% up there so we generate improve this 00:25:42.159 --> 00:25:58.039 align:start position:0% up there so we generate improve this wait<00:25:44.340> and<00:25:45.340> then<00:25:53.909> let<00:25:54.909> me<00:25:54.940> get<00:25:55.179> the<00:25:55.299> truth<00:25:55.539> and 00:25:58.039 --> 00:25:58.049 align:start position:0% 00:25:58.049 --> 00:26:02.810 align:start position:0% when<00:25:59.049> you<00:25:59.080> want<00:25:59.320> to<00:25:59.350> verify<00:25:59.740> the<00:25:59.799> proof<00:26:00.070> be 00:26:02.810 --> 00:26:02.820 align:start position:0% 00:26:02.820 --> 00:26:10.549 align:start position:0% they<00:26:03.539> use<00:26:03.809> the<00:26:07.639> verification<00:26:08.639> key<00:26:08.849> and<00:26:09.559> the 00:26:10.549 --> 00:26:10.559 align:start position:0% they use the verification key and the 00:26:10.559 --> 00:26:18.739 align:start position:0% they use the verification key and the funding<00:26:10.949> inputs<00:26:11.279> H<00:26:13.190> so<00:26:14.779> if<00:26:15.779> this<00:26:16.679> is<00:26:16.859> true<00:26:17.749> it 00:26:18.739 --> 00:26:18.749 align:start position:0% funding inputs H so if this is true it 00:26:18.749 --> 00:26:22.219 align:start position:0% funding inputs H so if this is true it means<00:26:18.959> that<00:26:19.440> I<00:26:19.709> know<00:26:20.489> that<00:26:20.729> I<00:26:21.299> know<00:26:22.019> that 00:26:22.219 --> 00:26:22.229 align:start position:0% means that I know that I know that 00:26:22.229 --> 00:26:25.299 align:start position:0% means that I know that I know that witness<00:26:22.769> I<00:26:22.949> know<00:26:23.039> the<00:26:23.219> plain<00:26:23.429> text<00:26:23.639> of<00:26:24.359> the<00:26:24.629> of 00:26:25.299 --> 00:26:25.309 align:start position:0% witness I know the plain text of the of 00:26:25.309 --> 00:26:29.479 align:start position:0% witness I know the plain text of the of the<00:26:26.309> hatch<00:26:26.519> H<00:26:27.349> given<00:26:28.349> the<00:26:28.709> unification<00:26:29.309> key 00:26:29.479 --> 00:26:29.489 align:start position:0% the hatch H given the unification key 00:26:29.489 --> 00:26:31.609 align:start position:0% the hatch H given the unification key and<00:26:29.699> the<00:26:29.849> proof<00:26:30.119> it<00:26:30.719> was<00:26:30.899> fast<00:26:31.169> and<00:26:31.349> I<00:26:31.440> don't 00:26:31.609 --> 00:26:31.619 align:start position:0% and the proof it was fast and I don't 00:26:31.619 --> 00:26:39.649 align:start position:0% and the proof it was fast and I don't know<00:26:31.739> if<00:26:32.149> so<00:26:33.649> that's<00:26:34.649> C<00:26:35.249> it's<00:26:35.429> not<00:26:35.579> 101<00:26:36.349> the<00:26:38.659> big 00:26:39.649 --> 00:26:39.659 align:start position:0% know if so that's C it's not 101 the big 00:26:39.659 --> 00:26:41.869 align:start position:0% know if so that's C it's not 101 the big problem<00:26:40.409> with<00:26:40.589> taking<00:26:40.919> snacks<00:26:41.279> is<00:26:41.549> that<00:26:41.729> you 00:26:41.869 --> 00:26:41.879 align:start position:0% problem with taking snacks is that you 00:26:41.879 --> 00:26:43.579 align:start position:0% problem with taking snacks is that you have<00:26:41.999> this<00:26:42.149> classic<00:26:42.449> setup<00:26:42.779> where<00:26:43.169> you<00:26:43.379> need 00:26:43.579 --> 00:26:43.589 align:start position:0% have this classic setup where you need 00:26:43.589 --> 00:26:46.519 align:start position:0% have this classic setup where you need to<00:26:43.889> generate<00:26:44.219> a<00:26:45.119> proving<00:26:45.690> gamification<00:26:46.379> key 00:26:46.519 --> 00:26:46.529 align:start position:0% to generate a proving gamification key 00:26:46.529 --> 00:26:49.819 align:start position:0% to generate a proving gamification key but<00:26:46.799> you<00:26:46.829> also<00:26:47.039> need<00:26:47.279> to<00:26:47.599> this<00:26:48.599> can't<00:26:48.959> be<00:26:49.139> toxic 00:26:49.819 --> 00:26:49.829 align:start position:0% but you also need to this can't be toxic 00:26:49.829 --> 00:26:52.129 align:start position:0% but you also need to this can't be toxic waste<00:26:50.009> and<00:26:50.309> this<00:26:51.179> is<00:26:51.359> something<00:26:51.629> that<00:26:51.659> is 00:26:52.129 --> 00:26:52.139 align:start position:0% waste and this is something that is 00:26:52.139 --> 00:26:55.999 align:start position:0% waste and this is something that is really<00:26:52.919> troublesome<00:26:53.279> to<00:26:53.489> do<00:26:53.609> because<00:26:54.859> the<00:26:55.859> way 00:26:55.999 --> 00:26:56.009 align:start position:0% really troublesome to do because the way 00:26:56.009 --> 00:26:58.369 align:start position:0% really troublesome to do because the way that<00:26:56.219> the<00:26:56.879> best<00:26:57.089> way<00:26:57.239> to<00:26:57.269> do<00:26:57.479> this<00:26:57.629> is<00:26:57.839> to 00:26:58.369 --> 00:26:58.379 align:start position:0% that the best way to do this is to 00:26:58.379 --> 00:27:02.239 align:start position:0% that the best way to do this is to multiply<00:26:59.039> plan<00:26:59.279> accommodation<00:26:59.909> where<00:27:01.249> you 00:27:02.239 --> 00:27:02.249 align:start position:0% multiply plan accommodation where you 00:27:02.249 --> 00:27:04.999 align:start position:0% multiply plan accommodation where you have<00:27:02.489> a<00:27:02.759> bunch<00:27:03.029> of<00:27:03.089> people<00:27:03.269> to<00:27:03.659> do<00:27:03.869> the<00:27:04.649> Chester 00:27:04.999 --> 00:27:05.009 align:start position:0% have a bunch of people to do the Chester 00:27:05.009 --> 00:27:08.689 align:start position:0% have a bunch of people to do the Chester setup<00:27:05.309> in<00:27:06.019> step<00:27:07.019> by<00:27:07.049> step<00:27:07.349> phrases<00:27:07.709> and<00:27:08.279> you 00:27:08.689 --> 00:27:08.699 align:start position:0% setup in step by step phrases and you 00:27:08.699 --> 00:27:10.759 align:start position:0% setup in step by step phrases and you only<00:27:08.789> need<00:27:09.059> one<00:27:09.419> person<00:27:09.449> to<00:27:09.929> be<00:27:10.109> honest<00:27:10.469> on<00:27:10.709> a 00:27:10.759 --> 00:27:10.769 align:start position:0% only need one person to be honest on a 00:27:10.769 --> 00:27:12.859 align:start position:0% only need one person to be honest on a Polish<00:27:11.159> people<00:27:11.429> who<00:27:11.519> do<00:27:11.639> this<00:27:11.759> transit<00:27:12.089> setup 00:27:12.859 --> 00:27:12.869 align:start position:0% Polish people who do this transit setup 00:27:12.869 --> 00:27:14.919 align:start position:0% Polish people who do this transit setup it's<00:27:13.199> part<00:27:13.409> of<00:27:13.440> House<00:27:13.619> of<00:27:13.859> Taos<00:27:14.099> everybody<00:27:14.609> and 00:27:14.919 --> 00:27:14.929 align:start position:0% it's part of House of Taos everybody and 00:27:14.929 --> 00:27:17.749 align:start position:0% it's part of House of Taos everybody and for<00:27:16.039> semaphore<00:27:17.039> we<00:27:17.249> are<00:27:17.339> doing<00:27:17.609> this 00:27:17.749 --> 00:27:17.759 align:start position:0% for semaphore we are doing this 00:27:17.759 --> 00:27:20.659 align:start position:0% for semaphore we are doing this increment<00:27:18.149> potential<00:27:18.959> house<00:27:19.199> hotel<00:27:19.409> where<00:27:20.339> we 00:27:20.659 --> 00:27:20.669 align:start position:0% increment potential house hotel where we 00:27:20.669 --> 00:27:23.569 align:start position:0% increment potential house hotel where we are<00:27:20.789> coordinating<00:27:21.089> with<00:27:21.479> 120<00:27:22.379> people<00:27:22.559> so<00:27:23.339> far 00:27:23.569 --> 00:27:23.579 align:start position:0% are coordinating with 120 people so far 00:27:23.579 --> 00:27:27.129 align:start position:0% are coordinating with 120 people so far to<00:27:24.149> take<00:27:24.629> part<00:27:24.839> in<00:27:24.929> the<00:27:25.019> ceremony<00:27:25.199> to<00:27:26.190> generate 00:27:27.129 --> 00:27:27.139 align:start position:0% to take part in the ceremony to generate 00:27:27.139 --> 00:27:31.339 align:start position:0% to take part in the ceremony to generate to<00:27:28.139> do<00:27:28.319> the<00:27:28.940> multi-party<00:27:29.940> computation<00:27:30.349> for 00:27:31.339 --> 00:27:31.349 align:start position:0% to do the multi-party computation for 00:27:31.349 --> 00:27:34.249 align:start position:0% to do the multi-party computation for transit<00:27:31.739> setup<00:27:31.979> so<00:27:32.639> as<00:27:32.819> long<00:27:32.969> as<00:27:33.029> at<00:27:33.329> least<00:27:33.599> as 00:27:34.249 --> 00:27:34.259 align:start position:0% transit setup so as long as at least as 00:27:34.259 --> 00:27:35.989 align:start position:0% transit setup so as long as at least as long<00:27:34.499> as<00:27:34.619> only<00:27:34.769> one<00:27:34.859> of<00:27:35.039> these<00:27:35.219> people<00:27:35.459> is 00:27:35.989 --> 00:27:35.999 align:start position:0% long as only one of these people is 00:27:35.999 --> 00:27:39.099 align:start position:0% long as only one of these people is honest<00:27:36.449> the<00:27:37.440> whole<00:27:37.649> thing<00:27:37.889> can<00:27:38.159> be<00:27:38.190> trusted 00:27:39.099 --> 00:27:39.109 align:start position:0% honest the whole thing can be trusted 00:27:39.109 --> 00:27:42.799 align:start position:0% honest the whole thing can be trusted and<00:27:40.109> c-catch<00:27:40.679> did<00:27:40.949> this<00:27:41.209> in<00:27:42.209> two<00:27:42.389> years<00:27:42.599> ago 00:27:42.799 --> 00:27:42.809 align:start position:0% and c-catch did this in two years ago 00:27:42.809 --> 00:27:45.889 align:start position:0% and c-catch did this in two years ago without<00:27:43.379> sampling<00:27:43.859> of<00:27:44.389> thousand<00:27:45.389> calorie 00:27:45.889 --> 00:27:45.899 align:start position:0% without sampling of thousand calorie 00:27:45.899 --> 00:27:50.509 align:start position:0% without sampling of thousand calorie trance<00:27:46.799> L<00:27:47.149> so<00:27:48.149> this<00:27:48.989> stuff<00:27:49.289> is<00:27:49.409> not<00:27:49.559> new<00:27:49.739> the 00:27:50.509 --> 00:27:50.519 align:start position:0% trance L so this stuff is not new the 00:27:50.519 --> 00:27:54.229 align:start position:0% trance L so this stuff is not new the can<00:27:51.209> be<00:27:51.359> a<00:27:51.389> bit<00:27:51.629> like<00:27:51.839> mine<00:27:52.229> Danny<00:27:52.499> so<00:27:53.009> is<00:27:53.669> this 00:27:54.229 --> 00:27:54.239 align:start position:0% can be a bit like mine Danny so is this 00:27:54.239 --> 00:27:56.809 align:start position:0% can be a bit like mine Danny so is this be<00:27:54.419> patient<00:27:54.839> well<00:27:55.139> it<00:27:56.009> trying<00:27:56.279> to<00:27:56.369> navigate 00:27:56.809 --> 00:27:56.819 align:start position:0% be patient well it trying to navigate 00:27:56.819 --> 00:28:01.159 align:start position:0% be patient well it trying to navigate all<00:27:57.329> this<00:27:57.479> complex<00:27:57.989> stuff<00:27:59.209> so<00:28:00.209> we're<00:28:00.989> gonna 00:28:01.159 --> 00:28:01.169 align:start position:0% all this complex stuff so we're gonna 00:28:01.169 --> 00:28:05.479 align:start position:0% all this complex stuff so we're gonna take<00:28:01.349> this<00:28:01.499> and<00:28:01.739> apply<00:28:02.039> this<00:28:02.279> to<00:28:02.489> semaphore<00:28:04.489> so 00:28:05.479 --> 00:28:05.489 align:start position:0% take this and apply this to semaphore so 00:28:05.489 --> 00:28:07.860 align:start position:0% take this and apply this to semaphore so just<00:28:06.239> let<00:28:06.329> me<00:28:06.359> mentioned<00:28:06.719> how 00:28:07.860 --> 00:28:07.870 align:start position:0% just let me mentioned how 00:28:07.870 --> 00:28:10.830 align:start position:0% just let me mentioned how circuit<00:28:08.580> this<00:28:09.580> is<00:28:09.640> super<00:28:10.000> simple<00:28:10.360> circuit 00:28:10.830 --> 00:28:10.840 align:start position:0% circuit this is super simple circuit 00:28:10.840 --> 00:28:15.420 align:start position:0% circuit this is super simple circuit that<00:28:11.130> the<00:28:12.130> function<00:28:12.490> that<00:28:13.020> hashes<00:28:14.070> is<00:28:15.070> attacks 00:28:15.420 --> 00:28:15.430 align:start position:0% that the function that hashes is attacks 00:28:15.430 --> 00:28:17.190 align:start position:0% that the function that hashes is attacks there<00:28:16.150> returns<00:28:16.540> a<00:28:16.630> hash 00:28:17.190 --> 00:28:17.200 align:start position:0% there returns a hash 00:28:17.200 --> 00:28:22.530 align:start position:0% there returns a hash so<00:28:17.410> the<00:28:17.980> semaphore<00:28:18.309> is<00:28:18.670> basically<00:28:21.270> so<00:28:22.270> make 00:28:22.530 --> 00:28:22.540 align:start position:0% so the semaphore is basically so make 00:28:22.540 --> 00:28:24.000 align:start position:0% so the semaphore is basically so make the<00:28:22.690> circuit<00:28:23.050> checks<00:28:23.470> whether<00:28:23.620> the<00:28:23.740> hash 00:28:24.000 --> 00:28:24.010 align:start position:0% the circuit checks whether the hash 00:28:24.010 --> 00:28:28.830 align:start position:0% the circuit checks whether the hash nasty<00:28:25.980> the<00:28:26.980> hash<00:28:27.340> input<00:28:27.790> with<00:28:28.150> the<00:28:28.450> dominant 00:28:28.830 --> 00:28:28.840 align:start position:0% nasty the hash input with the dominant 00:28:28.840 --> 00:28:30.240 align:start position:0% nasty the hash input with the dominant good<00:28:28.930> measures<00:28:29.230> the<00:28:29.350> hash<00:28:29.530> of<00:28:29.680> the<00:28:29.770> witness<00:28:30.070> or 00:28:30.240 --> 00:28:30.250 align:start position:0% good measures the hash of the witness or 00:28:30.250 --> 00:28:32.100 align:start position:0% good measures the hash of the witness or the<00:28:30.430> secret<00:28:30.610> but<00:28:31.330> semaphore<00:28:31.780> is<00:28:31.870> doing 00:28:32.100 --> 00:28:32.110 align:start position:0% the secret but semaphore is doing 00:28:32.110 --> 00:28:34.710 align:start position:0% the secret but semaphore is doing something<00:28:32.290> a<00:28:32.680> bit<00:28:33.220> more<00:28:33.309> complex<00:28:33.640> what<00:28:34.600> we're 00:28:34.710 --> 00:28:34.720 align:start position:0% something a bit more complex what we're 00:28:34.720 --> 00:28:37.680 align:start position:0% something a bit more complex what we're doing<00:28:34.990> is<00:28:35.320> semaphore<00:28:35.860> is<00:28:36.450> proving<00:28:37.450> three 00:28:37.680 --> 00:28:37.690 align:start position:0% doing is semaphore is proving three 00:28:37.690 --> 00:28:41.400 align:start position:0% doing is semaphore is proving three things<00:28:38.100> the<00:28:39.100> first<00:28:39.130> thing<00:28:39.520> is<00:28:39.850> that<00:28:40.380> we<00:28:41.380> are 00:28:41.400 --> 00:28:41.410 align:start position:0% things the first thing is that we are 00:28:41.410 --> 00:28:45.380 align:start position:0% things the first thing is that we are proving<00:28:41.830> that<00:28:41.860> we<00:28:42.550> have<00:28:42.850> and<00:28:43.350> we<00:28:44.350> have<00:28:44.380> the 00:28:45.380 --> 00:28:45.390 align:start position:0% proving that we have and we have the 00:28:45.390 --> 00:28:50.180 align:start position:0% proving that we have and we have the valid<00:28:46.390> lover<00:28:46.660> proof<00:28:47.010> to<00:28:48.010> the<00:28:48.670> maca<00:28:49.570> root 00:28:50.180 --> 00:28:50.190 align:start position:0% valid lover proof to the maca root 00:28:50.190 --> 00:28:55.770 align:start position:0% valid lover proof to the maca root starting<00:28:51.190> the<00:28:51.309> smart<00:28:51.610> contract<00:28:53.010> given<00:28:54.780> given 00:28:55.770 --> 00:28:55.780 align:start position:0% starting the smart contract given given 00:28:55.780 --> 00:28:57.900 align:start position:0% starting the smart contract given given the<00:28:56.040> identity<00:28:57.040> commitment<00:28:57.490> that<00:28:57.640> we<00:28:57.760> might 00:28:57.900 --> 00:28:57.910 align:start position:0% the identity commitment that we might 00:28:57.910 --> 00:29:04.020 align:start position:0% the identity commitment that we might improve<00:28:58.710> knowledge<00:28:59.710> on<00:29:00.630> so<00:29:02.790> what<00:29:03.790> is<00:29:03.910> an 00:29:04.020 --> 00:29:04.030 align:start position:0% improve knowledge on so what is an 00:29:04.030 --> 00:29:06.240 align:start position:0% improve knowledge on so what is an identity<00:29:04.420> commitment<00:29:05.020> so<00:29:05.679> earlier<00:29:06.100> when 00:29:06.240 --> 00:29:06.250 align:start position:0% identity commitment so earlier when 00:29:06.250 --> 00:29:09.240 align:start position:0% identity commitment so earlier when we've<00:29:06.400> registered<00:29:06.520> our<00:29:07.770> identity<00:29:08.770> into<00:29:09.130> the 00:29:09.240 --> 00:29:09.250 align:start position:0% we've registered our identity into the 00:29:09.250 --> 00:29:14.250 align:start position:0% we've registered our identity into the app<00:29:09.429> we<00:29:11.040> what<00:29:12.040> we<00:29:12.160> did<00:29:12.370> was<00:29:12.850> not<00:29:12.880> just<00:29:13.480> some<00:29:14.170> a 00:29:14.250 --> 00:29:14.260 align:start position:0% app we what we did was not just some a 00:29:14.260 --> 00:29:16.530 align:start position:0% app we what we did was not just some a transaction<00:29:14.740> on<00:29:15.010> the<00:29:15.190> transaction<00:29:15.700> thus<00:29:16.360> the 00:29:16.530 --> 00:29:16.540 align:start position:0% transaction on the transaction thus the 00:29:16.540 --> 00:29:21.180 align:start position:0% transaction on the transaction thus the hash<00:29:16.840> of<00:29:17.110> an<00:29:17.530> EDD<00:29:18.400> as<00:29:18.610> a<00:29:18.929> colicky<00:29:19.929> and<00:29:20.190> two 00:29:21.180 --> 00:29:21.190 align:start position:0% hash of an EDD as a colicky and two 00:29:21.190 --> 00:29:27.870 align:start position:0% hash of an EDD as a colicky and two random<00:29:22.140> strings<00:29:24.510> so<00:29:25.510> this<00:29:26.080> is<00:29:26.820> these<00:29:27.820> are 00:29:27.870 --> 00:29:27.880 align:start position:0% random strings so this is these are 00:29:27.880 --> 00:29:29.820 align:start position:0% random strings so this is these are these<00:29:28.390> all<00:29:28.660> these<00:29:28.809> identity<00:29:29.350> commitments 00:29:29.820 --> 00:29:29.830 align:start position:0% these all these identity commitments 00:29:29.830 --> 00:29:32.220 align:start position:0% these all these identity commitments installed<00:29:30.130> in<00:29:30.280> your<00:29:30.400> country<00:29:30.870> as<00:29:31.870> an<00:29:32.050> leaves 00:29:32.220 --> 00:29:32.230 align:start position:0% installed in your country as an leaves 00:29:32.230 --> 00:29:34.350 align:start position:0% installed in your country as an leaves of<00:29:32.380> a<00:29:32.440> motor<00:29:32.590> free<00:29:32.860> and<00:29:33.100> they've<00:29:34.000> Ruthann 00:29:34.350 --> 00:29:34.360 align:start position:0% of a motor free and they've Ruthann 00:29:34.360 --> 00:29:36.390 align:start position:0% of a motor free and they've Ruthann about<00:29:34.540> the<00:29:34.630> free<00:29:34.809> store<00:29:35.080> in<00:29:35.320> a<00:29:35.350> contract<00:29:35.800> it's 00:29:36.390 --> 00:29:36.400 align:start position:0% about the free store in a contract it's 00:29:36.400 --> 00:29:39.260 align:start position:0% about the free store in a contract it's not<00:29:36.640> at<00:29:36.760> the<00:29:36.790> Center<00:29:37.210> for<00:29:37.240> contract<00:29:37.860> when<00:29:38.860> we 00:29:39.260 --> 00:29:39.270 align:start position:0% not at the Center for contract when we 00:29:39.270 --> 00:29:42.660 align:start position:0% not at the Center for contract when we generate<00:29:40.270> the<00:29:40.570> burglar-proof<00:29:41.010> we<00:29:42.010> download 00:29:42.660 --> 00:29:42.670 align:start position:0% generate the burglar-proof we download 00:29:42.670 --> 00:29:45.150 align:start position:0% generate the burglar-proof we download all<00:29:42.850> the<00:29:42.970> leaves<00:29:43.120> we<00:29:43.990> generate<00:29:44.440> the<00:29:44.620> marathas 00:29:45.150 --> 00:29:45.160 align:start position:0% all the leaves we generate the marathas 00:29:45.160 --> 00:29:49.590 align:start position:0% all the leaves we generate the marathas and<00:29:46.830> that's<00:29:47.830> the<00:29:48.040> maka<00:29:48.220> proof<00:29:48.490> and<00:29:48.730> we<00:29:49.480> see 00:29:49.590 --> 00:29:49.600 align:start position:0% and that's the maka proof and we see 00:29:49.600 --> 00:29:53.299 align:start position:0% and that's the maka proof and we see when<00:29:50.140> we<00:29:50.850> earned<00:29:51.850> let<00:29:52.510> me<00:29:52.570> generate<00:29:52.929> the<00:29:53.020> proof 00:29:53.299 --> 00:29:53.309 align:start position:0% when we earned let me generate the proof 00:29:53.309 --> 00:29:58.200 align:start position:0% when we earned let me generate the proof the<00:29:54.309> one<00:29:55.000> of<00:29:55.090> the<00:29:55.179> private<00:29:55.600> inputs<00:29:57.000> it<00:29:58.000> goes 00:29:58.200 --> 00:29:58.210 align:start position:0% the one of the private inputs it goes 00:29:58.210 --> 00:30:01.169 align:start position:0% the one of the private inputs it goes into<00:29:58.420> a<00:29:58.540> circuit<00:29:58.900> and<00:29:59.050> the<00:29:59.650> circuit<00:30:00.179> verifies 00:30:01.169 --> 00:30:01.179 align:start position:0% into a circuit and the circuit verifies 00:30:01.179 --> 00:30:06.919 align:start position:0% into a circuit and the circuit verifies the<00:30:01.510> locket<00:30:02.020> proof<00:30:02.230> and<00:30:03.540> only<00:30:04.540> analog<00:30:04.929> approve 00:30:06.919 --> 00:30:06.929 align:start position:0% the locket proof and only analog approve 00:30:06.929 --> 00:30:09.950 align:start position:0% the locket proof and only analog approve along<00:30:07.799> the<00:30:07.950> two<00:30:08.130> other<00:30:08.340> conditions<00:30:08.970> it<00:30:09.179> would 00:30:09.950 --> 00:30:09.960 align:start position:0% along the two other conditions it would 00:30:09.960 --> 00:30:11.899 align:start position:0% along the two other conditions it would be<00:30:10.080> a<00:30:10.340> very<00:30:11.340> truth 00:30:11.899 --> 00:30:11.909 align:start position:0% be a very truth 00:30:11.909 --> 00:30:14.600 align:start position:0% be a very truth so<00:30:12.750> this<00:30:12.870> that's<00:30:13.230> the<00:30:13.320> first<00:30:13.620> thing<00:30:13.799> we<00:30:14.010> do<00:30:14.190> to 00:30:14.600 --> 00:30:14.610 align:start position:0% so this that's the first thing we do to 00:30:14.610 --> 00:30:20.269 align:start position:0% so this that's the first thing we do to prove<00:30:15.059> that<00:30:15.590> the<00:30:16.590> user<00:30:16.799> is<00:30:17.279> indeed<00:30:19.100> those<00:30:20.100> are 00:30:20.269 --> 00:30:20.279 align:start position:0% prove that the user is indeed those are 00:30:20.279 --> 00:30:21.889 align:start position:0% prove that the user is indeed those are the<00:30:20.340> first<00:30:20.730> condition<00:30:21.299> that<00:30:21.390> needs<00:30:21.510> to<00:30:21.690> hold 00:30:21.889 --> 00:30:21.899 align:start position:0% the first condition that needs to hold 00:30:21.899 --> 00:30:32.500 align:start position:0% the first condition that needs to hold for<00:30:22.049> this<00:30:24.230> any<00:30:25.230> questions<00:30:25.710> so<00:30:25.860> far 00:30:32.500 --> 00:30:32.510 align:start position:0% 00:30:32.510 --> 00:30:35.480 align:start position:0% how<00:30:33.510> does<00:30:33.659> it<00:30:33.690> help<00:30:33.990> in<00:30:34.529> terms<00:30:34.679> of<00:30:34.860> complexity 00:30:35.480 --> 00:30:35.490 align:start position:0% how does it help in terms of complexity 00:30:35.490 --> 00:30:40.039 align:start position:0% how does it help in terms of complexity how<00:30:35.700> much<00:30:36.149> more<00:30:36.450> complex<00:30:36.840> is<00:30:37.110> this<00:30:37.289> then<00:30:39.049> this 00:30:40.039 --> 00:30:40.049 align:start position:0% how much more complex is this then this 00:30:40.049 --> 00:30:42.049 align:start position:0% how much more complex is this then this is<00:30:40.110> like<00:30:40.409> wasting<00:30:40.649> that<00:30:41.039> is<00:30:41.159> eternal<00:30:41.730> really 00:30:42.049 --> 00:30:42.059 align:start position:0% is like wasting that is eternal really 00:30:42.059 --> 00:30:42.860 align:start position:0% is like wasting that is eternal really yeah 00:30:42.860 --> 00:30:42.870 align:start position:0% yeah 00:30:42.870 --> 00:30:45.409 align:start position:0% yeah ZK<00:30:43.409> is<00:30:43.559> a<00:30:43.590> super<00:30:43.890> complex<00:30:44.159> right<00:30:44.460> because<00:30:45.029> this 00:30:45.409 --> 00:30:45.419 align:start position:0% ZK is a super complex right because this 00:30:45.419 --> 00:30:48.909 align:start position:0% ZK is a super complex right because this is<00:30:45.480> just<00:30:45.899> like<00:30:46.770> one<00:30:47.399> note<00:30:47.640> if<00:30:47.940> on<00:30:48.330> a<00:30:48.360> single 00:30:48.909 --> 00:30:48.919 align:start position:0% is just like one note if on a single 00:30:48.919 --> 00:30:54.049 align:start position:0% is just like one note if on a single denomination<00:30:51.200> so<00:30:52.200> what<00:30:53.159> I<00:30:53.190> mean<00:30:53.309> is<00:30:53.460> that<00:30:53.520> for 00:30:54.049 --> 00:30:54.059 align:start position:0% denomination so what I mean is that for 00:30:54.059 --> 00:30:55.990 align:start position:0% denomination so what I mean is that for mixer 00:30:55.990 --> 00:30:56.000 align:start position:0% mixer 00:30:56.000 --> 00:31:00.850 align:start position:0% mixer each<00:30:57.000> leaf<00:30:57.360> only<00:30:57.929> represents<00:30:58.470> a<00:30:58.559> fixed<00:30:58.799> amount 00:31:00.850 --> 00:31:00.860 align:start position:0% each leaf only represents a fixed amount 00:31:00.860 --> 00:31:02.620 align:start position:0% each leaf only represents a fixed amount [Music] 00:31:02.620 --> 00:31:02.630 align:start position:0% [Music] 00:31:02.630 --> 00:31:07.039 align:start position:0% [Music] in<00:31:03.630> this<00:31:03.779> case<00:31:04.250> it's<00:31:05.250> just<00:31:05.659> so<00:31:06.659> another<00:31:07.020> thing 00:31:07.039 --> 00:31:07.049 align:start position:0% in this case it's just so another thing 00:31:07.049 --> 00:31:09.350 align:start position:0% in this case it's just so another thing a<00:31:07.200> little<00:31:07.350> bit<00:31:07.470> with<00:31:07.820> sequence<00:31:08.820> but<00:31:09.000> this<00:31:09.210> is 00:31:09.350 --> 00:31:09.360 align:start position:0% a little bit with sequence but this is 00:31:09.360 --> 00:31:33.919 align:start position:0% a little bit with sequence but this is recently 00:31:33.919 --> 00:31:33.929 align:start position:0% 00:31:33.929 --> 00:31:54.440 align:start position:0% and<00:31:49.070> so<00:31:50.070> before<00:31:50.820> the<00:31:51.210> is<00:31:51.330> Michael<00:31:51.659> can<00:31:51.809> fall<00:31:53.450> if 00:31:54.440 --> 00:31:54.450 align:start position:0% and so before the is Michael can fall if 00:31:54.450 --> 00:31:59.389 align:start position:0% and so before the is Michael can fall if we<00:31:54.690> use<00:31:54.870> a<00:31:55.340> circuit<00:31:56.539> which<00:31:57.539> was<00:31:58.260> above<00:31:59.250> the 00:31:59.389 --> 00:31:59.399 align:start position:0% we use a circuit which was above the 00:31:59.399 --> 00:32:02.980 align:start position:0% we use a circuit which was above the treetops<00:31:59.760> 25<00:32:00.570> us<00:32:00.720> so<00:32:01.260> that's<00:32:01.710> to<00:32:01.980> the<00:32:02.070> company 00:32:02.980 --> 00:32:02.990 align:start position:0% treetops 25 us so that's to the company 00:32:02.990 --> 00:32:05.450 align:start position:0% treetops 25 us so that's to the company leaves<00:32:03.990> that<00:32:04.260> can<00:32:04.409> be<00:32:04.500> stories<00:32:05.279> and<00:32:05.429> a 00:32:05.450 --> 00:32:05.460 align:start position:0% leaves that can be stories and a 00:32:05.460 --> 00:32:07.669 align:start position:0% leaves that can be stories and a contract<00:32:06.019> which<00:32:07.019> is<00:32:07.049> facing<00:32:07.440> into<00:32:07.649> the 00:32:07.669 --> 00:32:07.679 align:start position:0% contract which is facing into the 00:32:07.679 --> 00:32:11.149 align:start position:0% contract which is facing into the company<00:32:08.210> registrations<00:32:09.210> that<00:32:09.419> takes<00:32:10.409> like<00:32:10.950> 30 00:32:11.149 --> 00:32:11.159 align:start position:0% company registrations that takes like 30 00:32:11.159 --> 00:32:13.399 align:start position:0% company registrations that takes like 30 seconds<00:32:11.580> to<00:32:11.850> generate<00:32:12.510> proof<00:32:13.019> on<00:32:13.169> a<00:32:13.200> laptop 00:32:13.399 --> 00:32:13.409 align:start position:0% seconds to generate proof on a laptop 00:32:13.409 --> 00:32:17.299 align:start position:0% seconds to generate proof on a laptop and<00:32:13.799> that<00:32:14.580> takes<00:32:14.789> like<00:32:15.649> 800<00:32:16.649> K<00:32:16.799> yes<00:32:17.010> -<00:32:17.220> very 00:32:17.299 --> 00:32:17.309 align:start position:0% and that takes like 800 K yes - very 00:32:17.309 --> 00:32:21.379 align:start position:0% and that takes like 800 K yes - very very<00:32:17.639> fun<00:32:18.559> yeah<00:32:19.559> I<00:32:19.860> think<00:32:20.580> it's<00:32:20.880> what<00:32:21.000> I<00:32:21.029> wonder 00:32:21.379 --> 00:32:21.389 align:start position:0% very fun yeah I think it's what I wonder 00:32:21.389 --> 00:32:23.960 align:start position:0% very fun yeah I think it's what I wonder it<00:32:21.510> has<00:32:21.539> to<00:32:21.840> be<00:32:21.929> positive<00:32:22.380> but<00:32:23.130> for<00:32:23.850> this 00:32:23.960 --> 00:32:23.970 align:start position:0% it has to be positive but for this 00:32:23.970 --> 00:32:26.299 align:start position:0% it has to be positive but for this year's<00:32:24.179> case<00:32:24.389> we<00:32:25.350> lower<00:32:25.649> the<00:32:25.830> number<00:32:26.070> of<00:32:26.159> these 00:32:26.299 --> 00:32:26.309 align:start position:0% year's case we lower the number of these 00:32:26.309 --> 00:32:28.430 align:start position:0% year's case we lower the number of these know<00:32:26.880> that<00:32:27.120> about<00:32:27.330> nervous<00:32:27.539> in<00:32:27.720> a<00:32:27.779> tree<00:32:27.929> to<00:32:28.080> 12 00:32:28.430 --> 00:32:28.440 align:start position:0% know that about nervous in a tree to 12 00:32:28.440 --> 00:32:32.269 align:start position:0% know that about nervous in a tree to 12 so<00:32:28.710> to<00:32:28.889> Travis<00:32:29.429> like<00:32:29.610> 4,000<00:32:30.179> basics<00:32:31.279> and 00:32:32.269 --> 00:32:32.279 align:start position:0% so to Travis like 4,000 basics and 00:32:32.279 --> 00:32:35.919 align:start position:0% so to Travis like 4,000 basics and that's<00:32:32.730> likely<00:32:33.029> the<00:32:33.210> attendance<00:32:33.960> of<00:32:34.080> that<00:32:34.260> car 00:32:35.919 --> 00:32:35.929 align:start position:0% that's likely the attendance of that car 00:32:35.929 --> 00:32:41.740 align:start position:0% that's likely the attendance of that car once<00:32:36.929> of<00:32:37.080> the<00:32:37.169> second<00:32:37.559> concussion<00:32:37.980> without 00:32:41.740 --> 00:32:41.750 align:start position:0% 00:32:41.750 --> 00:32:43.950 align:start position:0% driving 00:32:43.950 --> 00:32:43.960 align:start position:0% driving 00:32:43.960 --> 00:32:51.310 align:start position:0% driving the<00:32:44.380> power<00:32:44.680> of<00:32:44.770> the<00:32:44.950> polynomial 00:32:51.310 --> 00:32:51.320 align:start position:0% 00:32:51.320 --> 00:32:56.990 align:start position:0% so<00:32:53.210> you're<00:32:54.210> choosing<00:32:54.660> if<00:32:55.350> your<00:32:55.500> power<00:32:55.710> is<00:32:56.100> not 00:32:56.990 --> 00:32:57.000 align:start position:0% so you're choosing if your power is not 00:32:57.000 --> 00:32:58.310 align:start position:0% so you're choosing if your power is not high<00:32:57.960> enough 00:32:58.310 --> 00:32:58.320 align:start position:0% high enough 00:32:58.320 --> 00:33:04.220 align:start position:0% high enough right<00:32:59.100> then<00:33:00.440> the<00:33:01.440> verification<00:33:02.309> is<00:33:03.230> necessary 00:33:04.220 --> 00:33:04.230 align:start position:0% right then the verification is necessary 00:33:04.230 --> 00:33:06.230 align:start position:0% right then the verification is necessary even<00:33:04.740> if<00:33:04.830> it's<00:33:04.980> as<00:33:05.130> true<00:33:05.400> is<00:33:05.610> actually<00:33:06.000> false 00:33:06.230 --> 00:33:06.240 align:start position:0% even if it's as true is actually false 00:33:06.240 --> 00:33:08.600 align:start position:0% even if it's as true is actually false because<00:33:06.929> we<00:33:07.350> go<00:33:07.470> theory<00:33:07.740> because<00:33:08.130> because 00:33:08.600 --> 00:33:08.610 align:start position:0% because we go theory because because 00:33:08.610 --> 00:33:10.460 align:start position:0% because we go theory because because this<00:33:08.760> is<00:33:08.910> only<00:33:09.059> true<00:33:09.420> up<00:33:09.510> to<00:33:09.780> an<00:33:09.840> epsilon<00:33:10.260> and 00:33:10.460 --> 00:33:10.470 align:start position:0% this is only true up to an epsilon and 00:33:10.470 --> 00:33:13.400 align:start position:0% this is only true up to an epsilon and the<00:33:10.590> axle<00:33:10.890> on<00:33:11.070> is<00:33:11.370> is<00:33:11.970> a<00:33:12.030> function<00:33:12.540> of<00:33:12.660> a<00:33:12.929> of<00:33:13.170> the 00:33:13.400 --> 00:33:13.410 align:start position:0% the axle on is is a function of a of the 00:33:13.410 --> 00:33:17.090 align:start position:0% the axle on is is a function of a of the power<00:33:14.010> of<00:33:14.190> the<00:33:14.370> polynomial<00:33:15.950> all<00:33:16.950> right<00:33:17.040> I 00:33:17.090 --> 00:33:17.100 align:start position:0% power of the polynomial all right I 00:33:17.100 --> 00:33:19.040 align:start position:0% power of the polynomial all right I think<00:33:17.250> I'm<00:33:17.460> sure<00:33:17.610> the<00:33:17.670> D<00:33:17.820> for<00:33:18.000> their<00:33:18.120> customers 00:33:19.040 --> 00:33:19.050 align:start position:0% think I'm sure the D for their customers 00:33:19.050 --> 00:33:31.030 align:start position:0% think I'm sure the D for their customers we<00:33:19.260> most<00:33:19.470> have<00:33:19.620> met<00:33:29.059> right<00:33:30.059> not<00:33:30.360> super<00:33:30.570> sure 00:33:31.030 --> 00:33:31.040 align:start position:0% we most have met right not super sure 00:33:31.040 --> 00:33:44.270 align:start position:0% we most have met right not super sure like<00:33:32.040> he<00:33:32.220> catches<00:33:32.580> like<00:33:32.760> it<00:33:33.179> started<00:33:42.530> I<00:33:43.530> will 00:33:44.270 --> 00:33:44.280 align:start position:0% like he catches like it started I will 00:33:44.280 --> 00:33:45.919 align:start position:0% like he catches like it started I will have<00:33:44.460> to<00:33:44.550> check<00:33:44.700> with<00:33:44.880> people<00:33:45.240> who<00:33:45.390> know<00:33:45.540> the 00:33:45.919 --> 00:33:45.929 align:start position:0% have to check with people who know the 00:33:45.929 --> 00:33:51.830 align:start position:0% have to check with people who know the details<00:33:48.800> all<00:33:49.800> right<00:33:49.860> so<00:33:50.309> anyway<00:33:51.000> so<00:33:51.510> that<00:33:51.540> was 00:33:51.830 --> 00:33:51.840 align:start position:0% details all right so anyway so that was 00:33:51.840 --> 00:33:53.810 align:start position:0% details all right so anyway so that was just<00:33:52.020> the<00:33:52.140> first<00:33:52.410> part<00:33:52.679> of<00:33:52.770> the<00:33:52.920> proof<00:33:53.130> now<00:33:53.760> we 00:33:53.810 --> 00:33:53.820 align:start position:0% just the first part of the proof now we 00:33:53.820 --> 00:33:55.840 align:start position:0% just the first part of the proof now we want<00:33:54.090> to<00:33:54.150> prove<00:33:54.420> to<00:33:54.720> other<00:33:55.350> things 00:33:55.840 --> 00:33:55.850 align:start position:0% want to prove to other things 00:33:55.850 --> 00:33:58.070 align:start position:0% want to prove to other things the<00:33:56.850> second<00:33:57.210> thing<00:33:57.300> gotta<00:33:57.450> prove<00:33:57.660> is<00:33:57.840> that<00:33:57.870> the 00:33:58.070 --> 00:33:58.080 align:start position:0% the second thing gotta prove is that the 00:33:58.080 --> 00:34:00.280 align:start position:0% the second thing gotta prove is that the signal<00:33:58.590> was<00:33:58.710> winning<00:33:59.040> broadcast<00:33:59.400> at<00:33:59.520> once 00:34:00.280 --> 00:34:00.290 align:start position:0% signal was winning broadcast at once 00:34:00.290 --> 00:34:02.180 align:start position:0% signal was winning broadcast at once which<00:34:01.290> means<00:34:01.320> that<00:34:01.679> we<00:34:01.770> want<00:34:01.860> to<00:34:02.010> prove<00:34:02.160> that 00:34:02.180 --> 00:34:02.190 align:start position:0% which means that we want to prove that 00:34:02.190 --> 00:34:05.270 align:start position:0% which means that we want to prove that there<00:34:02.640> were<00:34:02.700> no<00:34:02.880> cover<00:34:03.770> that<00:34:04.770> we<00:34:04.860> were<00:34:05.220> to 00:34:05.270 --> 00:34:05.280 align:start position:0% there were no cover that we were to 00:34:05.280 --> 00:34:11.990 align:start position:0% there were no cover that we were to ensure<00:34:05.730> an<00:34:05.910> economical<00:34:06.809> price<00:34:08.810> so<00:34:10.790> that<00:34:11.790> is 00:34:11.990 --> 00:34:12.000 align:start position:0% ensure an economical price so that is 00:34:12.000 --> 00:34:13.790 align:start position:0% ensure an economical price so that is something<00:34:12.210> called<00:34:12.480> nullified<00:34:13.050> hash<00:34:13.320> which<00:34:13.679> is 00:34:13.790 --> 00:34:13.800 align:start position:0% something called nullified hash which is 00:34:13.800 --> 00:34:19.730 align:start position:0% something called nullified hash which is a<00:34:13.830> hash<00:34:14.100> of<00:34:14.340> the<00:34:15.919> identity<00:34:16.919> image<00:34:16.980> file<00:34:18.740> which 00:34:19.730 --> 00:34:19.740 align:start position:0% a hash of the identity image file which 00:34:19.740 --> 00:34:22.280 align:start position:0% a hash of the identity image file which is<00:34:19.889> one<00:34:20.040> of<00:34:20.070> the<00:34:20.280> rented<00:34:20.940> marrow<00:34:21.119> cells<00:34:21.450> has 00:34:22.280 --> 00:34:22.290 align:start position:0% is one of the rented marrow cells has 00:34:22.290 --> 00:34:26.300 align:start position:0% is one of the rented marrow cells has along<00:34:22.619> with<00:34:22.649> the<00:34:22.820> monkey<00:34:23.820> and<00:34:24.710> when<00:34:25.710> you<00:34:25.800> when 00:34:26.300 --> 00:34:26.310 align:start position:0% along with the monkey and when you when 00:34:26.310 --> 00:34:29.869 align:start position:0% along with the monkey and when you when you<00:34:26.629> register<00:34:27.629> it<00:34:27.840> was<00:34:27.960> a<00:34:27.990> contract<00:34:28.730> you<00:34:29.730> also 00:34:29.869 --> 00:34:29.879 align:start position:0% you register it was a contract you also 00:34:29.879 --> 00:34:31.770 align:start position:0% you register it was a contract you also had<00:34:30.119> a<00:34:30.149> passion<00:34:30.389> along<00:34:30.750> with<00:34:30.869> the<00:34:30.960> external 00:34:31.770 --> 00:34:31.780 align:start position:0% had a passion along with the external 00:34:31.780 --> 00:34:33.960 align:start position:0% had a passion along with the external which<00:34:31.960> is<00:34:32.080> a<00:34:32.110> hassle<00:34:32.560> that<00:34:32.590> question<00:34:33.100> masked 00:34:33.960 --> 00:34:33.970 align:start position:0% which is a hassle that question masked 00:34:33.970 --> 00:34:38.700 align:start position:0% which is a hassle that question masked by<00:34:34.179> the<00:34:34.210> users<00:34:34.600> and<00:34:35.380> finally<00:34:36.159> the<00:34:36.400> top<00:34:37.110> so<00:34:38.110> the 00:34:38.700 --> 00:34:38.710 align:start position:0% by the users and finally the top so the 00:34:38.710 --> 00:34:40.560 align:start position:0% by the users and finally the top so the contracts<00:34:39.250> thoughts<00:34:39.490> or<00:34:39.850> the<00:34:40.090> enzyme<00:34:40.210> size 00:34:40.560 --> 00:34:40.570 align:start position:0% contracts thoughts or the enzyme size 00:34:40.570 --> 00:34:44.490 align:start position:0% contracts thoughts or the enzyme size mattress<00:34:41.490> and<00:34:42.490> the<00:34:42.850> circuit<00:34:43.780> also<00:34:44.050> ensures 00:34:44.490 --> 00:34:44.500 align:start position:0% mattress and the circuit also ensures 00:34:44.500 --> 00:34:46.409 align:start position:0% mattress and the circuit also ensures that<00:34:44.530> the<00:34:45.159> hatch<00:34:45.400> is<00:34:45.850> valid 00:34:46.409 --> 00:34:46.419 align:start position:0% that the hatch is valid 00:34:46.419 --> 00:34:50.220 align:start position:0% that the hatch is valid just<00:34:46.630> like<00:34:46.750> my<00:34:46.870> passion<00:34:47.140> in<00:34:47.470> this<00:34:47.770> episode<00:34:49.230> and 00:34:50.220 --> 00:34:50.230 align:start position:0% just like my passion in this episode and 00:34:50.230 --> 00:34:54.810 align:start position:0% just like my passion in this episode and finally<00:34:50.890> we<00:34:51.640> also<00:34:51.669> do<00:34:52.890> EVPs<00:34:53.890> a<00:34:54.100> syndrome 00:34:54.810 --> 00:34:54.820 align:start position:0% finally we also do EVPs a syndrome 00:34:54.820 --> 00:34:58.500 align:start position:0% finally we also do EVPs a syndrome gratification<00:34:55.720> to<00:34:56.310> ensure<00:34:57.310> that<00:34:57.610> the<00:34:57.970> public 00:34:58.500 --> 00:34:58.510 align:start position:0% gratification to ensure that the public 00:34:58.510 --> 00:35:01.590 align:start position:0% gratification to ensure that the public key<00:34:58.780> that<00:34:59.170> was<00:34:59.580> that's<00:35:00.580> that<00:35:01.120> the<00:35:01.270> whole<00:35:01.450> name 00:35:01.590 --> 00:35:01.600 align:start position:0% key that was that's that the whole name 00:35:01.600 --> 00:35:05.940 align:start position:0% key that was that's that the whole name of<00:35:02.560> the<00:35:02.800> the<00:35:03.790> registrant<00:35:04.390> has<00:35:04.630> is<00:35:05.200> valid<00:35:05.740> and 00:35:05.940 --> 00:35:05.950 align:start position:0% of the the registrant has is valid and 00:35:05.950 --> 00:35:08.880 align:start position:0% of the the registrant has is valid and this<00:35:06.400> is<00:35:06.550> a<00:35:06.580> median<00:35:07.120> EVPs<00:35:07.900> be<00:35:08.080> a<00:35:08.110> kid<00:35:08.590> not<00:35:08.770> at 00:35:08.880 --> 00:35:08.890 align:start position:0% this is a median EVPs be a kid not at 00:35:08.890 --> 00:35:14.790 align:start position:0% this is a median EVPs be a kid not at ECDSA<00:35:09.630> tamaki<00:35:10.630> so<00:35:13.110> the<00:35:14.110> reason<00:35:14.410> for<00:35:14.500> that<00:35:14.560> is 00:35:14.790 --> 00:35:14.800 align:start position:0% ECDSA tamaki so the reason for that is 00:35:14.800 --> 00:35:17.220 align:start position:0% ECDSA tamaki so the reason for that is that<00:35:14.830> in<00:35:15.490> DDS<00:35:15.820> a<00:35:16.000> common<00:35:16.360> keys<00:35:16.570> are<00:35:16.780> much<00:35:17.020> more 00:35:17.220 --> 00:35:17.230 align:start position:0% that in DDS a common keys are much more 00:35:17.230 --> 00:35:19.800 align:start position:0% that in DDS a common keys are much more friendly<00:35:17.650> and<00:35:18.030> much<00:35:19.030> of<00:35:19.060> some<00:35:19.300> it<00:35:19.420> was<00:35:19.570> a<00:35:19.600> guess 00:35:19.800 --> 00:35:19.810 align:start position:0% friendly and much of some it was a guess 00:35:19.810 --> 00:35:23.600 align:start position:0% friendly and much of some it was a guess not<00:35:20.050> and<00:35:20.500> not<00:35:20.920> so<00:35:21.160> much<00:35:21.190> so<00:35:21.700> far<00:35:22.060> ECDSA<00:35:22.630> keys 00:35:23.600 --> 00:35:23.610 align:start position:0% not and not so much so far ECDSA keys 00:35:23.610 --> 00:35:28.410 align:start position:0% not and not so much so far ECDSA keys which<00:35:24.610> means<00:35:24.850> that<00:35:26.160> zk<00:35:27.160> stop<00:35:27.430> applications<00:35:28.180> on 00:35:28.410 --> 00:35:28.420 align:start position:0% which means that zk stop applications on 00:35:28.420 --> 00:35:30.780 align:start position:0% which means that zk stop applications on if<00:35:28.540> you<00:35:28.660> have<00:35:29.530> some<00:35:29.920> challenges<00:35:30.100> in<00:35:30.550> terms<00:35:30.670> of 00:35:30.780 --> 00:35:30.790 align:start position:0% if you have some challenges in terms of 00:35:30.790 --> 00:35:33.750 align:start position:0% if you have some challenges in terms of UI<00:35:31.000> UX<00:35:31.480> because<00:35:32.040> these<00:35:33.040> keys<00:35:33.460> have<00:35:33.640> to<00:35:33.670> be 00:35:33.750 --> 00:35:33.760 align:start position:0% UI UX because these keys have to be 00:35:33.760 --> 00:35:37.160 align:start position:0% UI UX because these keys have to be stored<00:35:34.060> somewhere<00:35:34.500> other<00:35:35.500> than<00:35:35.650> users<00:35:36.070> wallet 00:35:37.160 --> 00:35:37.170 align:start position:0% stored somewhere other than users wallet 00:35:37.170 --> 00:35:40.350 align:start position:0% stored somewhere other than users wallet such<00:35:38.170> as<00:35:38.320> such<00:35:38.710> as<00:35:38.740> in<00:35:39.010> local<00:35:39.280> storage<00:35:39.460> but 00:35:40.350 --> 00:35:40.360 align:start position:0% such as such as in local storage but 00:35:40.360 --> 00:35:42.240 align:start position:0% such as such as in local storage but just<00:35:40.600> yesterday<00:35:40.780> they're<00:35:41.680> also<00:35:41.800> big 00:35:42.240 --> 00:35:42.250 align:start position:0% just yesterday they're also big 00:35:42.250 --> 00:35:43.830 align:start position:0% just yesterday they're also big announcement<00:35:42.730> made<00:35:42.850> meta<00:35:43.030> masks<00:35:43.240> when<00:35:43.810> they 00:35:43.830 --> 00:35:43.840 align:start position:0% announcement made meta masks when they 00:35:43.840 --> 00:35:46.950 align:start position:0% announcement made meta masks when they have<00:35:44.110> a<00:35:44.140> plugin<00:35:44.590> system<00:35:44.950> that<00:35:45.520> as<00:35:45.670> you<00:35:45.960> have 00:35:46.950 --> 00:35:46.960 align:start position:0% have a plugin system that as you have 00:35:46.960 --> 00:35:48.840 align:start position:0% have a plugin system that as you have something<00:35:47.230> fun<00:35:47.440> at<00:35:47.620> keys<00:35:47.890> so<00:35:48.640> there's 00:35:48.840 --> 00:35:48.850 align:start position:0% something fun at keys so there's 00:35:48.850 --> 00:35:50.280 align:start position:0% something fun at keys so there's something<00:35:49.000> that<00:35:49.120> you<00:35:49.390> can<00:35:49.450> explore<00:35:49.930> and 00:35:50.280 --> 00:35:50.290 align:start position:0% something that you can explore and 00:35:50.290 --> 00:35:51.840 align:start position:0% something that you can explore and figure<00:35:50.590> out<00:35:50.740> if<00:35:50.860> there's<00:35:51.130> possibility<00:35:51.640> use 00:35:51.840 --> 00:35:51.850 align:start position:0% figure out if there's possibility use 00:35:51.850 --> 00:35:54.000 align:start position:0% figure out if there's possibility use instead<00:35:52.450> of<00:35:52.510> storing<00:35:53.200> their<00:35:53.440> keys<00:35:53.620> and<00:35:53.650> office 00:35:54.000 --> 00:35:54.010 align:start position:0% instead of storing their keys and office 00:35:54.010 --> 00:35:58.710 align:start position:0% instead of storing their keys and office operation<00:35:54.780> so<00:35:55.780> just<00:35:56.500> a<00:35:56.590> recap<00:35:57.420> this<00:35:58.420> time 00:35:58.710 --> 00:35:58.720 align:start position:0% operation so just a recap this time 00:35:58.720 --> 00:36:02.220 align:start position:0% operation so just a recap this time across<00:35:58.990> subject<00:36:00.030> proves<00:36:01.030> three<00:36:01.420> things<00:36:01.630> that 00:36:02.220 --> 00:36:02.230 align:start position:0% across subject proves three things that 00:36:02.230 --> 00:36:05.880 align:start position:0% across subject proves three things that the<00:36:02.980> users<00:36:03.400> identity<00:36:03.850> is<00:36:04.300> one<00:36:04.960> of<00:36:05.200> the<00:36:05.410> set<00:36:05.740> of 00:36:05.880 --> 00:36:05.890 align:start position:0% the users identity is one of the set of 00:36:05.890 --> 00:36:08.850 align:start position:0% the users identity is one of the set of register<00:36:06.520> identities<00:36:07.000> that<00:36:07.720> signal<00:36:08.590> was<00:36:08.680> one 00:36:08.850 --> 00:36:08.860 align:start position:0% register identities that signal was one 00:36:08.860 --> 00:36:11.580 align:start position:0% register identities that signal was one intercept<00:36:09.430> ones<00:36:09.640> and<00:36:09.940> that<00:36:10.720> the<00:36:10.900> user<00:36:11.110> truly 00:36:11.580 --> 00:36:11.590 align:start position:0% intercept ones and that the user truly 00:36:11.590 --> 00:36:12.760 align:start position:0% intercept ones and that the user truly almost<00:36:11.920> in<00:36:12.070> here 00:36:12.760 --> 00:36:12.770 align:start position:0% almost in here 00:36:12.770 --> 00:36:18.580 align:start position:0% almost in here there<00:36:12.920> was<00:36:13.040> used<00:36:13.280> to<00:36:15.730> that<00:36:17.170> like<00:36:18.170> to<00:36:18.350> Leo<00:36:18.470> Esaki 00:36:18.580 --> 00:36:18.590 align:start position:0% there was used to that like to Leo Esaki 00:36:18.590 --> 00:36:20.200 align:start position:0% there was used to that like to Leo Esaki because<00:36:19.070> they<00:36:19.190> had<00:36:19.310> a<00:36:19.400> sign<00:36:19.580> a<00:36:19.610> message<00:36:19.820> that 00:36:20.200 --> 00:36:20.210 align:start position:0% because they had a sign a message that 00:36:20.210 --> 00:36:23.920 align:start position:0% because they had a sign a message that is<00:36:20.630> the<00:36:20.840> circuit<00:36:22.270> the<00:36:23.270> circuit<00:36:23.300> breaker<00:36:23.750> is 00:36:23.920 --> 00:36:23.930 align:start position:0% is the circuit the circuit breaker is 00:36:23.930 --> 00:36:31.000 align:start position:0% is the circuit the circuit breaker is the<00:36:24.080> angel<00:36:25.630> so<00:36:27.369> and<00:36:29.050> also<00:36:30.050> that<00:36:30.260> we<00:36:30.350> have<00:36:30.560> the 00:36:31.000 --> 00:36:31.010 align:start position:0% the angel so and also that we have the 00:36:31.010 --> 00:36:33.850 align:start position:0% the angel so and also that we have the signal<00:36:31.970> that<00:36:32.780> we<00:36:32.900> are<00:36:32.930> broadcasting<00:36:33.200> ahead 00:36:33.850 --> 00:36:33.860 align:start position:0% signal that we are broadcasting ahead 00:36:33.860 --> 00:36:38.080 align:start position:0% signal that we are broadcasting ahead answer<00:36:34.630> we<00:36:35.630> are<00:36:35.900> broadcasting<00:36:36.260> a<00:36:36.800> signal<00:36:37.160> to<00:36:37.820> a 00:36:38.080 --> 00:36:38.090 align:start position:0% answer we are broadcasting a signal to a 00:36:38.090 --> 00:36:40.510 align:start position:0% answer we are broadcasting a signal to a question<00:36:38.660> which<00:36:39.170> is<00:36:39.410> hatch<00:36:39.710> to<00:36:39.920> become<00:36:40.220> a 00:36:40.510 --> 00:36:40.520 align:start position:0% question which is hatch to become a 00:36:40.520 --> 00:36:42.910 align:start position:0% question which is hatch to become a excellent<00:36:41.330> modifier<00:36:41.780> the<00:36:42.500> semaphore 00:36:42.910 --> 00:36:42.920 align:start position:0% excellent modifier the semaphore 00:36:42.920 --> 00:36:45.400 align:start position:0% excellent modifier the semaphore contract<00:36:43.490> supports<00:36:44.060> multiple<00:36:44.480> identifiers 00:36:45.400 --> 00:36:45.410 align:start position:0% contract supports multiple identifiers 00:36:45.410 --> 00:36:53.430 align:start position:0% contract supports multiple identifiers and<00:36:45.770> s<00:36:45.860> how<00:36:46.040> many<00:36:47.200> other<00:36:48.200> questions<00:36:49.690> yeah<00:36:51.490> so 00:36:53.430 --> 00:36:53.440 align:start position:0% and s how many other questions yeah so 00:36:53.440 --> 00:36:56.890 align:start position:0% and s how many other questions yeah so Before<00:36:54.440> we<00:36:54.470> jump<00:36:54.560> into<00:36:54.860> more<00:36:55.190> code<00:36:55.490> can<00:36:56.300> be<00:36:56.330> any 00:36:56.890 --> 00:36:56.900 align:start position:0% Before we jump into more code can be any 00:36:56.900 --> 00:37:10.720 align:start position:0% Before we jump into more code can be any questions<00:37:01.840> yeah<00:37:02.840> okay<00:37:08.890> yeah<00:37:09.890> okay<00:37:10.010> but<00:37:10.280> I<00:37:10.460> will 00:37:10.720 --> 00:37:10.730 align:start position:0% questions yeah okay yeah okay but I will 00:37:10.730 --> 00:37:14.770 align:start position:0% questions yeah okay yeah okay but I will join<00:37:10.970> it<00:37:11.119> to<00:37:11.210> the<00:37:12.610> maybe<00:37:13.610> I<00:37:14.000> will<00:37:14.390> join<00:37:14.540> it<00:37:14.600> to 00:37:14.770 --> 00:37:14.780 align:start position:0% join it to the maybe I will join it to 00:37:14.780 --> 00:37:18.310 align:start position:0% join it to the maybe I will join it to the<00:37:15.970> flow<00:37:16.970> of<00:37:17.000> how<00:37:17.540> this<00:37:17.810> whole<00:37:17.960> thing<00:37:18.140> works 00:37:18.310 --> 00:37:18.320 align:start position:0% the flow of how this whole thing works 00:37:18.320 --> 00:37:22.630 align:start position:0% the flow of how this whole thing works from<00:37:18.950> start<00:37:19.820> to<00:37:19.910> finish<00:37:20.320> from<00:37:21.320> the<00:37:21.410> UI<00:37:21.980> all<00:37:22.460> the 00:37:22.630 --> 00:37:22.640 align:start position:0% from start to finish from the UI all the 00:37:22.640 --> 00:37:25.270 align:start position:0% from start to finish from the UI all the way<00:37:22.730> to<00:37:22.790> the<00:37:23.030> secrets<00:37:23.750> of<00:37:24.020> it<00:37:24.200> just<00:37:25.010> look<00:37:25.130> at<00:37:25.220> it 00:37:25.270 --> 00:37:25.280 align:start position:0% way to the secrets of it just look at it 00:37:25.280 --> 00:37:53.290 align:start position:0% way to the secrets of it just look at it hope<00:37:25.490> some<00:37:26.390> good 00:37:53.290 --> 00:37:53.300 align:start position:0% 00:37:53.300 --> 00:37:55.390 align:start position:0% all<00:37:54.200> right<00:37:54.350> so<00:37:54.530> that's<00:37:54.680> staff<00:37:54.950> in<00:37:55.100> the<00:37:55.160> front 00:37:55.390 --> 00:37:55.400 align:start position:0% all right so that's staff in the front 00:37:55.400 --> 00:37:59.230 align:start position:0% all right so that's staff in the front and<00:37:55.900> look<00:37:56.900> at<00:37:56.990> what<00:37:57.140> we<00:37:57.230> do<00:37:57.700> when<00:37:58.700> we<00:37:58.790> register 00:37:59.230 --> 00:37:59.240 align:start position:0% and look at what we do when we register 00:37:59.240 --> 00:38:06.510 align:start position:0% and look at what we do when we register so<00:38:00.050> customs<00:38:00.560> at<00:38:00.680> first<00:38:00.860> everything<00:38:04.660> basically 00:38:06.510 --> 00:38:06.520 align:start position:0% so customs at first everything basically 00:38:06.520 --> 00:38:12.420 align:start position:0% so customs at first everything basically this<00:38:07.520> is<00:38:07.730> like<00:38:08.090> a<00:38:08.120> yeah<00:38:09.310> rather<00:38:10.990> when<00:38:11.990> we 00:38:12.420 --> 00:38:12.430 align:start position:0% this is like a yeah rather when we 00:38:12.430 --> 00:38:16.120 align:start position:0% this is like a yeah rather when we register<00:38:13.430> we<00:38:14.470> generate<00:38:15.470> an<00:38:15.620> identity 00:38:16.120 --> 00:38:16.130 align:start position:0% register we generate an identity 00:38:16.130 --> 00:38:20.400 align:start position:0% register we generate an identity commitment<00:38:16.670> and<00:38:17.650> this<00:38:18.650> function<00:38:18.860> basically 00:38:20.400 --> 00:38:20.410 align:start position:0% commitment and this function basically 00:38:20.410 --> 00:38:35.560 align:start position:0% commitment and this function basically hashes<00:38:21.410> together<00:38:21.710> those<00:38:22.460> three<00:38:22.490> things 00:38:35.560 --> 00:38:35.570 align:start position:0% 00:38:35.570 --> 00:38:38.380 align:start position:0% right<00:38:36.140> so<00:38:36.380> we<00:38:36.470> are<00:38:36.560> using<00:38:36.710> a<00:38:36.860> Peterson<00:38:37.730> hash<00:38:37.910> I 00:38:38.380 --> 00:38:38.390 align:start position:0% right so we are using a Peterson hash I 00:38:38.390 --> 00:38:41.830 align:start position:0% right so we are using a Peterson hash I mean<00:38:38.810> a<00:38:38.840> pleasant<00:38:39.260> commitment<00:38:39.650> to<00:38:40.640> have<00:38:41.090> the 00:38:41.830 --> 00:38:41.840 align:start position:0% mean a pleasant commitment to have the 00:38:41.840 --> 00:38:48.070 align:start position:0% mean a pleasant commitment to have the public<00:38:42.230> key<00:38:42.530> of<00:38:43.510> the<00:38:44.510> user<00:38:45.280> and<00:38:46.280> and<00:38:47.080> two 00:38:48.070 --> 00:38:48.080 align:start position:0% public key of the user and and two 00:38:48.080 --> 00:38:55.450 align:start position:0% public key of the user and and two random<00:38:48.590> values<00:38:48.860> and<00:38:53.020> this<00:38:54.020> UI<00:38:54.650> is<00:38:55.010> using 00:38:55.450 --> 00:38:55.460 align:start position:0% random values and this UI is using 00:38:55.460 --> 00:38:57.460 align:start position:0% random values and this UI is using something<00:38:55.790> that<00:38:56.000> lifts<00:38:56.540> and<00:38:56.690> publishes<00:38:57.290> the 00:38:57.460 --> 00:38:57.470 align:start position:0% something that lifts and publishes the 00:38:57.470 --> 00:39:01.150 align:start position:0% something that lifts and publishes the like<00:38:58.100> and<00:38:58.460> iam<00:38:58.670> might<00:38:58.880> be<00:38:59.680> extracts<00:39:00.680> over<00:39:01.040> a 00:39:01.150 --> 00:39:01.160 align:start position:0% like and iam might be extracts over a 00:39:01.160 --> 00:39:02.890 align:start position:0% like and iam might be extracts over a lot<00:39:01.340> of<00:39:01.430> people<00:39:01.730> graphic<00:39:02.150> populations<00:39:02.690> that 00:39:02.890 --> 00:39:02.900 align:start position:0% lot of people graphic populations that 00:39:02.900 --> 00:39:06.580 align:start position:0% lot of people graphic populations that need<00:39:02.960> to<00:39:03.470> use<00:39:03.650> to<00:39:03.950> use<00:39:04.100> and<00:39:04.780> so<00:39:05.780> it<00:39:06.110> says<00:39:06.290> it<00:39:06.470> to 00:39:06.580 --> 00:39:06.590 align:start position:0% need to use to use and so it says it to 00:39:06.590 --> 00:39:10.450 align:start position:0% need to use to use and so it says it to be<00:39:06.740> contract<00:39:07.900> just<00:39:08.900> a<00:39:08.990> transaction<00:39:09.340> when<00:39:10.340> it's 00:39:10.450 --> 00:39:10.460 align:start position:0% be contract just a transaction when it's 00:39:10.460 --> 00:39:16.240 align:start position:0% be contract just a transaction when it's done<00:39:12.340> we<00:39:13.340> just<00:39:13.550> have<00:39:13.700> a<00:39:13.760> user<00:39:13.940> and<00:39:14.650> then<00:39:15.650> when 00:39:16.240 --> 00:39:16.250 align:start position:0% done we just have a user and then when 00:39:16.250 --> 00:39:24.660 align:start position:0% done we just have a user and then when you<00:39:16.430> submit<00:39:17.360> a<00:39:17.390> question<00:39:20.650> this<00:39:21.650> is<00:39:21.710> where 00:39:24.660 --> 00:39:24.670 align:start position:0% 00:39:24.670 --> 00:39:31.520 align:start position:0% [Music] 00:39:31.520 --> 00:39:31.530 align:start position:0% 00:39:31.530 --> 00:39:36.530 align:start position:0% and<00:39:32.530> it's<00:39:32.890> like<00:39:33.040> a<00:39:33.160> so<00:39:34.090> we<00:39:34.270> have<00:39:35.080> to<00:39:35.290> question 00:39:36.530 --> 00:39:36.540 align:start position:0% and it's like a so we have to question 00:39:36.540 --> 00:39:40.380 align:start position:0% and it's like a so we have to question that<00:39:37.540> the<00:39:37.660> user<00:39:37.810> sign<00:39:38.110> it<00:39:38.910> you<00:39:39.910> think<00:39:40.090> it<00:39:40.210> was 00:39:40.380 --> 00:39:40.390 align:start position:0% that the user sign it you think it was 00:39:40.390 --> 00:39:44.100 align:start position:0% that the user sign it you think it was an<00:39:40.510> inside<00:39:40.690> function<00:39:40.900> and<00:39:42.180> we<00:39:43.180> studied<00:39:43.930> up<00:39:44.080> to 00:39:44.100 --> 00:39:44.110 align:start position:0% an inside function and we studied up to 00:39:44.110 --> 00:39:49.350 align:start position:0% an inside function and we studied up to the<00:39:44.350> backend<00:39:44.770> database<00:39:46.260> I<00:39:48.210> think<00:39:49.210> much<00:39:49.330> more 00:39:49.350 --> 00:39:49.360 align:start position:0% the backend database I think much more 00:39:49.360 --> 00:39:50.970 align:start position:0% the backend database I think much more interesting<00:39:49.870> if<00:39:49.990> I<00:39:50.110> show<00:39:50.320> you<00:39:50.350> what<00:39:50.620> happens 00:39:50.970 --> 00:39:50.980 align:start position:0% interesting if I show you what happens 00:39:50.980 --> 00:39:57.390 align:start position:0% interesting if I show you what happens of<00:39:51.160> a<00:39:51.340> Vista<00:39:51.640> project<00:39:54.270> if<00:39:55.650> it's<00:39:56.650> done<00:39:57.160> on 00:39:57.390 --> 00:39:57.400 align:start position:0% of a Vista project if it's done on 00:39:57.400 --> 00:40:00.750 align:start position:0% of a Vista project if it's done on training<00:39:58.830> registration<00:39:59.830> is<00:40:00.160> a<00:40:00.220> safe<00:40:00.520> because 00:40:00.750 --> 00:40:00.760 align:start position:0% training registration is a safe because 00:40:00.760 --> 00:40:03.570 align:start position:0% training registration is a safe because we<00:40:00.910> already<00:40:01.330> do<00:40:01.450> that<00:40:01.480> huh<00:40:01.720> train<00:40:02.250> for<00:40:03.250> one 00:40:03.570 --> 00:40:03.580 align:start position:0% we already do that huh train for one 00:40:03.580 --> 00:40:05.100 align:start position:0% we already do that huh train for one train<00:40:03.850> registrations<00:40:04.480> basically<00:40:04.870> you 00:40:05.100 --> 00:40:05.110 align:start position:0% train registrations basically you 00:40:05.110 --> 00:40:09.120 align:start position:0% train registrations basically you instead<00:40:05.770> you<00:40:06.220> just<00:40:06.270> pass<00:40:07.270> along<00:40:07.540> the<00:40:08.130> identity 00:40:09.120 --> 00:40:09.130 align:start position:0% instead you just pass along the identity 00:40:09.130 --> 00:40:10.590 align:start position:0% instead you just pass along the identity commitment<00:40:09.550> to<00:40:09.640> the<00:40:09.820> Center<00:40:10.060> for<00:40:10.090> contract 00:40:10.590 --> 00:40:10.600 align:start position:0% commitment to the Center for contract 00:40:10.600 --> 00:40:13.200 align:start position:0% commitment to the Center for contract when<00:40:11.410> you<00:40:11.500> submit<00:40:12.160> a<00:40:12.190> question<00:40:12.430> what<00:40:13.060> we're 00:40:13.200 --> 00:40:13.210 align:start position:0% when you submit a question what we're 00:40:13.210 --> 00:40:15.600 align:start position:0% when you submit a question what we're doing<00:40:13.510> is<00:40:13.720> we're<00:40:14.350> adding<00:40:14.500> it<00:40:14.800> we're<00:40:15.160> adding<00:40:15.490> an 00:40:15.600 --> 00:40:15.610 align:start position:0% doing is we're adding it we're adding an 00:40:15.610 --> 00:40:17.370 align:start position:0% doing is we're adding it we're adding an external<00:40:15.940> modifier<00:40:16.420> to<00:40:16.720> these<00:40:16.870> and<00:40:17.170> of<00:40:17.260> our 00:40:17.370 --> 00:40:17.380 align:start position:0% external modifier to these and of our 00:40:17.380 --> 00:40:23.160 align:start position:0% external modifier to these and of our project<00:40:17.680> and<00:40:19.350> we<00:40:20.350> also<00:40:21.600> for<00:40:22.600> this<00:40:22.750> version<00:40:22.960> of 00:40:23.160 --> 00:40:23.170 align:start position:0% project and we also for this version of 00:40:23.170 --> 00:40:28.560 align:start position:0% project and we also for this version of the<00:40:23.520> building<00:40:24.520> we<00:40:25.390> require<00:40:26.110> the<00:40:26.440> user<00:40:26.620> to<00:40:27.570> send 00:40:28.560 --> 00:40:28.570 align:start position:0% the building we require the user to send 00:40:28.570 --> 00:40:31.290 align:start position:0% the building we require the user to send some<00:40:28.810> keys<00:40:28.990> along<00:40:29.260> with<00:40:29.500> the<00:40:30.120> transaction<00:40:31.120> and 00:40:31.290 --> 00:40:31.300 align:start position:0% some keys along with the transaction and 00:40:31.300 --> 00:40:34.580 align:start position:0% some keys along with the transaction and this<00:40:31.570> is<00:40:31.720> what<00:40:31.870> pays<00:40:32.050> to<00:40:32.260> be<00:40:32.290> the<00:40:32.500> hospital<00:40:33.000> so 00:40:34.580 --> 00:40:34.590 align:start position:0% this is what pays to be the hospital so 00:40:34.590 --> 00:40:40.170 align:start position:0% this is what pays to be the hospital so this<00:40:35.590> fact<00:40:35.890> this<00:40:36.010> is<00:40:37.200> this<00:40:38.200> fee<00:40:38.470> could<00:40:38.920> be<00:40:39.180> any 00:40:40.170 --> 00:40:40.180 align:start position:0% this fact this is this fee could be any 00:40:40.180 --> 00:40:42.030 align:start position:0% this fact this is this fee could be any about<00:40:40.450> but<00:40:40.930> it<00:40:41.140> should<00:40:41.290> be<00:40:41.380> enough<00:40:41.620> to<00:40:41.650> cover 00:40:42.030 --> 00:40:42.040 align:start position:0% about but it should be enough to cover 00:40:42.040 --> 00:40:47.940 align:start position:0% about but it should be enough to cover is<00:40:42.520> a<00:40:42.550> field<00:40:43.020> of<00:40:44.020> pupils<00:40:44.410> and<00:40:46.260> then<00:40:47.260> when<00:40:47.800> you 00:40:47.940 --> 00:40:47.950 align:start position:0% is a field of pupils and then when you 00:40:47.950 --> 00:40:50.400 align:start position:0% is a field of pupils and then when you answer<00:40:48.760> that<00:40:48.790> question<00:40:49.270> we<00:40:49.660> have<00:40:49.690> to<00:40:50.260> answer 00:40:50.400 --> 00:40:50.410 align:start position:0% answer that question we have to answer 00:40:50.410 --> 00:40:56.610 align:start position:0% answer that question we have to answer and<00:40:50.950> we<00:40:53.160> first<00:40:54.160> of<00:40:54.280> all<00:40:55.140> check<00:40:56.140> whether<00:40:56.350> the 00:40:56.610 --> 00:40:56.620 align:start position:0% and we first of all check whether the 00:40:56.620 --> 00:40:59.040 align:start position:0% and we first of all check whether the question<00:40:57.430> that<00:40:57.550> is<00:40:57.670> answered<00:40:58.030> two<00:40:58.390> x's<00:40:58.870> and 00:40:59.040 --> 00:40:59.050 align:start position:0% question that is answered two x's and 00:40:59.050 --> 00:41:01.650 align:start position:0% question that is answered two x's and then<00:40:59.380> we<00:40:59.670> submit<00:41:00.670> this<00:41:00.850> to<00:41:00.910> this<00:41:01.150> semaphore 00:41:01.650 --> 00:41:01.660 align:start position:0% then we submit this to this semaphore 00:41:01.660 --> 00:41:04.730 align:start position:0% then we submit this to this semaphore contract<00:41:02.140> and<00:41:02.470> along<00:41:03.460> physique<00:41:03.850> is<00:41:04.000> not<00:41:04.150> proof 00:41:04.730 --> 00:41:04.740 align:start position:0% contract and along physique is not proof 00:41:04.740 --> 00:41:10.380 align:start position:0% contract and along physique is not proof whose<00:41:06.240> terminals<00:41:07.240> are<00:41:07.390> a<00:41:07.540> BST<00:41:08.670> cosmic<00:41:09.670> why<00:41:09.850> is 00:41:10.380 --> 00:41:10.390 align:start position:0% whose terminals are a BST cosmic why is 00:41:10.390 --> 00:41:12.000 align:start position:0% whose terminals are a BST cosmic why is my<00:41:10.630> agency<00:41:10.780> and 00:41:12.000 --> 00:41:12.010 align:start position:0% my agency and 00:41:12.010 --> 00:41:14.190 align:start position:0% my agency and and<00:41:12.430> but<00:41:13.120> also<00:41:13.300> these<00:41:13.540> are<00:41:13.600> the<00:41:13.810> public 00:41:14.190 --> 00:41:14.200 align:start position:0% and but also these are the public 00:41:14.200 --> 00:41:19.650 align:start position:0% and but also these are the public influence<00:41:14.470> to<00:41:14.770> the<00:41:14.920> Ziggy<00:41:15.760> stock<00:41:18.660> hash 00:41:19.650 --> 00:41:19.660 align:start position:0% influence to the Ziggy stock hash 00:41:19.660 --> 00:41:21.580 align:start position:0% influence to the Ziggy stock hash functions<00:41:20.020> are<00:41:20.140> second 00:41:21.580 --> 00:41:21.590 align:start position:0% functions are second 00:41:21.590 --> 00:41:24.050 align:start position:0% functions are second yeah 00:41:24.050 --> 00:41:24.060 align:start position:0% yeah 00:41:24.060 --> 00:41:38.190 align:start position:0% yeah [Music] 00:41:38.190 --> 00:41:38.200 align:start position:0% 00:41:38.200 --> 00:41:41.080 align:start position:0% yeah<00:41:39.200> but<00:41:40.100> as<00:41:40.250> far<00:41:40.400> as<00:41:40.430> every<00:41:40.670> times<00:41:40.850> identity 00:41:41.080 --> 00:41:41.090 align:start position:0% yeah but as far as every times identity 00:41:41.090 --> 00:41:50.870 align:start position:0% yeah but as far as every times identity bites 00:41:50.870 --> 00:41:50.880 align:start position:0% 00:41:50.880 --> 00:41:53.880 align:start position:0% right<00:41:51.880> so<00:41:52.059> now<00:41:52.210> let's<00:41:52.450> go<00:41:52.630> one<00:41:52.809> nearly<00:41:53.050> fell<00:41:53.349> by 00:41:53.880 --> 00:41:53.890 align:start position:0% right so now let's go one nearly fell by 00:41:53.890 --> 00:41:56.309 align:start position:0% right so now let's go one nearly fell by the<00:41:53.950> exception<00:41:54.460> dimensional<00:41:55.180> we're<00:41:56.170> going 00:41:56.309 --> 00:41:56.319 align:start position:0% the exception dimensional we're going 00:41:56.319 --> 00:42:03.870 align:start position:0% the exception dimensional we're going into<00:41:56.500> the<00:41:56.650> center<00:41:56.890> format<00:41:57.190> right 00:42:03.870 --> 00:42:03.880 align:start position:0% 00:42:03.880 --> 00:42:08.100 align:start position:0% so<00:42:04.510> all<00:42:05.320> this<00:42:05.470> is<00:42:05.590> all<00:42:05.740> it's<00:42:05.890> all<00:42:06.040> value<00:42:06.370> so<00:42:07.270> if 00:42:08.100 --> 00:42:08.110 align:start position:0% so all this is all it's all value so if 00:42:08.110 --> 00:42:09.600 align:start position:0% so all this is all it's all value so if you<00:42:08.230> won't<00:42:08.380> if<00:42:08.560> if<00:42:08.890> you<00:42:09.010> think<00:42:09.040> if<00:42:09.310> you<00:42:09.430> have 00:42:09.600 --> 00:42:09.610 align:start position:0% you won't if if you think if you have 00:42:09.610 --> 00:42:11.700 align:start position:0% you won't if if you think if you have nice<00:42:09.790> I'm<00:42:09.970> not<00:42:10.060> an<00:42:10.150> occasion<00:42:10.630> that<00:42:10.660> wants<00:42:11.620> to 00:42:11.700 --> 00:42:11.710 align:start position:0% nice I'm not an occasion that wants to 00:42:11.710 --> 00:42:13.290 align:start position:0% nice I'm not an occasion that wants to use<00:42:11.860> ideal<00:42:12.310> knowledge<00:42:12.610> but<00:42:12.880> you<00:42:12.940> don't<00:42:13.150> want 00:42:13.290 --> 00:42:13.300 align:start position:0% use ideal knowledge but you don't want 00:42:13.300 --> 00:42:15.000 align:start position:0% use ideal knowledge but you don't want to<00:42:13.420> play<00:42:13.930> around<00:42:13.960> with<00:42:14.350> building<00:42:14.680> a<00:42:14.710> whole<00:42:14.980> new 00:42:15.000 --> 00:42:15.010 align:start position:0% to play around with building a whole new 00:42:15.010 --> 00:42:20.220 align:start position:0% to play around with building a whole new circuit<00:42:15.490> this<00:42:16.210> might<00:42:16.420> be<00:42:16.570> why<00:42:17.140> keep<00:42:19.110> it<00:42:20.110> also 00:42:20.220 --> 00:42:20.230 align:start position:0% circuit this might be why keep it also 00:42:20.230 --> 00:42:21.480 align:start position:0% circuit this might be why keep it also helps<00:42:20.560> that<00:42:20.590> warm<00:42:20.860> it<00:42:20.980> through<00:42:21.010> p.m.<00:42:21.370> also 00:42:21.480 --> 00:42:21.490 align:start position:0% helps that warm it through p.m. also 00:42:21.490 --> 00:42:24.930 align:start position:0% helps that warm it through p.m. also doing<00:42:21.790> like<00:42:21.820> that<00:42:22.120> trust<00:42:22.450> set<00:42:22.720> up<00:42:23.310> an<00:42:24.310> audit 00:42:24.930 --> 00:42:24.940 align:start position:0% doing like that trust set up an audit 00:42:24.940 --> 00:42:27.090 align:start position:0% doing like that trust set up an audit for<00:42:25.210> the<00:42:25.330> central<00:42:25.690> code<00:42:25.930> so<00:42:26.590> what<00:42:26.770> was<00:42:26.920> I<00:42:27.040> done 00:42:27.090 --> 00:42:27.100 align:start position:0% for the central code so what was I done 00:42:27.100 --> 00:42:31.080 align:start position:0% for the central code so what was I done you<00:42:28.090> wouldn't<00:42:28.420> have<00:42:28.540> to<00:42:29.160> run<00:42:30.160> your<00:42:30.310> trust<00:42:30.640> as<00:42:31.060> a 00:42:31.080 --> 00:42:31.090 align:start position:0% you wouldn't have to run your trust as a 00:42:31.090 --> 00:42:35.210 align:start position:0% you wouldn't have to run your trust as a set<00:42:31.300> of<00:42:31.390> audit<00:42:31.690> for<00:42:31.990> this<00:42:32.260> component 00:42:35.210 --> 00:42:35.220 align:start position:0% 00:42:35.220 --> 00:42:38.490 align:start position:0% alright<00:42:36.220> so<00:42:36.460> insert<00:42:37.210> identity<00:42:37.660> this<00:42:37.930> is<00:42:37.990> the 00:42:38.490 --> 00:42:38.500 align:start position:0% alright so insert identity this is the 00:42:38.500 --> 00:42:41.430 align:start position:0% alright so insert identity this is the function<00:42:39.040> s<00:42:39.130> elephanta<00:42:39.700> LT<00:42:40.420> identity<00:42:41.200> to<00:42:41.410> be 00:42:41.430 --> 00:42:41.440 align:start position:0% function s elephanta LT identity to be 00:42:41.440 --> 00:42:46.950 align:start position:0% function s elephanta LT identity to be poetry<00:42:42.960> one<00:42:43.960> tree<00:42:44.140> and<00:42:45.930> broadcasting<00:42:46.930> a 00:42:46.950 --> 00:42:46.960 align:start position:0% poetry one tree and broadcasting a 00:42:46.960 --> 00:42:57.450 align:start position:0% poetry one tree and broadcasting a signal<00:42:47.230> is<00:42:48.600> where<00:42:49.650> we<00:42:53.400> first<00:42:54.400> base<00:42:55.120> V<00:42:56.460> check 00:42:57.450 --> 00:42:57.460 align:start position:0% signal is where we first base V check 00:42:57.460 --> 00:42:59.520 align:start position:0% signal is where we first base V check whether<00:42:57.670> it's<00:42:58.150> signal<00:42:58.780> whether<00:42:59.350> this 00:42:59.520 --> 00:42:59.530 align:start position:0% whether it's signal whether this 00:42:59.530 --> 00:43:01.710 align:start position:0% whether it's signal whether this security<00:42:59.950> system<00:43:00.520> through<00:43:01.030> this<00:43:01.150> valid<00:43:01.510> and 00:43:01.710 --> 00:43:01.720 align:start position:0% security system through this valid and 00:43:01.720 --> 00:43:05.010 align:start position:0% security system through this valid and then<00:43:02.320> we<00:43:02.950> just<00:43:03.760> added<00:43:04.090> to<00:43:04.420> the<00:43:04.510> mapping<00:43:04.690> of 00:43:05.010 --> 00:43:05.020 align:start position:0% then we just added to the mapping of 00:43:05.020 --> 00:43:08.670 align:start position:0% then we just added to the mapping of Cygnus<00:43:05.560> in<00:43:06.070> Astana<00:43:06.580> track<00:43:06.850> and<00:43:07.410> this<00:43:08.410> function 00:43:08.670 --> 00:43:08.680 align:start position:0% Cygnus in Astana track and this function 00:43:08.680 --> 00:43:11.400 align:start position:0% Cygnus in Astana track and this function to<00:43:09.040> check<00:43:09.250> whether<00:43:09.430> the<00:43:09.760> star<00:43:10.630> proof<00:43:10.900> is<00:43:11.050> valid 00:43:11.400 --> 00:43:11.410 align:start position:0% to check whether the star proof is valid 00:43:11.410 --> 00:43:16.170 align:start position:0% to check whether the star proof is valid is<00:43:11.770> here 00:43:16.170 --> 00:43:16.180 align:start position:0% 00:43:16.180 --> 00:43:20.380 align:start position:0% [Music] 00:43:20.380 --> 00:43:20.390 align:start position:0% 00:43:20.390 --> 00:43:31.830 align:start position:0% so<00:43:21.279> my<00:43:22.279> proof<00:43:22.630> is 00:43:31.830 --> 00:43:31.840 align:start position:0% 00:43:31.840 --> 00:43:34.870 align:start position:0% it's<00:43:32.840> like<00:43:32.990> this<00:43:33.200> my<00:43:33.530> contract<00:43:33.950> HUD<00:43:34.160> verified 00:43:34.870 --> 00:43:34.880 align:start position:0% it's like this my contract HUD verified 00:43:34.880 --> 00:43:38.770 align:start position:0% it's like this my contract HUD verified also<00:43:35.380> this<00:43:36.380> contract<00:43:37.220> is<00:43:37.490> auto-generated<00:43:38.030> by 00:43:38.770 --> 00:43:38.780 align:start position:0% also this contract is auto-generated by 00:43:38.780 --> 00:43:42.130 align:start position:0% also this contract is auto-generated by a<00:43:38.810> library<00:43:39.440> called<00:43:39.710> circle<00:43:40.160> and<00:43:40.540> circle<00:43:41.540> is 00:43:42.130 --> 00:43:42.140 align:start position:0% a library called circle and circle is 00:43:42.140 --> 00:43:44.740 align:start position:0% a library called circle and circle is the<00:43:42.470> JavaScript<00:43:43.220> based<00:43:43.370> by<00:43:43.550> B<00:43:43.700> by<00:43:43.730> an<00:43:44.150> f3 00:43:44.740 --> 00:43:44.750 align:start position:0% the JavaScript based by B by an f3 00:43:44.750 --> 00:43:46.600 align:start position:0% the JavaScript based by B by an f3 unless<00:43:45.140> you're<00:43:45.350> right<00:43:45.590> ziggy-zag<00:43:46.100> circuits 00:43:46.600 --> 00:43:46.610 align:start position:0% unless you're right ziggy-zag circuits 00:43:46.610 --> 00:43:49.680 align:start position:0% unless you're right ziggy-zag circuits and<00:43:47.020> when<00:43:48.020> you<00:43:48.110> buy<00:43:48.200> the<00:43:48.260> circuit<00:43:48.680> you<00:43:49.160> can 00:43:49.680 --> 00:43:49.690 align:start position:0% and when you buy the circuit you can 00:43:49.690 --> 00:43:51.880 align:start position:0% and when you buy the circuit you can complain<00:43:50.690> compound<00:43:51.140> a<00:43:51.200> circuit<00:43:51.500> you<00:43:51.590> can<00:43:51.650> also 00:43:51.880 --> 00:43:51.890 align:start position:0% complain compound a circuit you can also 00:43:51.890 --> 00:43:55.630 align:start position:0% complain compound a circuit you can also also<00:43:52.400> generate<00:43:52.850> this<00:43:53.860> solidity<00:43:54.860> contract 00:43:55.630 --> 00:43:55.640 align:start position:0% also generate this solidity contract 00:43:55.640 --> 00:43:59.290 align:start position:0% also generate this solidity contract that<00:43:55.790> allows<00:43:56.180> you<00:43:56.330> to<00:43:56.530> write<00:43:57.530> haikus<00:43:58.150> so<00:43:59.150> now 00:43:59.290 --> 00:43:59.300 align:start position:0% that allows you to write haikus so now 00:43:59.300 --> 00:44:01.330 align:start position:0% that allows you to write haikus so now let's<00:43:59.540> go<00:43:59.660> one<00:43:59.870> but<00:44:00.260> one<00:44:00.470> Monday<00:44:00.650> deeper<00:44:01.100> into 00:44:01.330 --> 00:44:01.340 align:start position:0% let's go one but one Monday deeper into 00:44:01.340 --> 00:44:09.650 align:start position:0% let's go one but one Monday deeper into the<00:44:01.520> set<00:44:02.030> of<00:44:02.060> all<00:44:02.330> Z<00:44:02.600> K<00:44:02.930> star<00:44:03.110> circuit 00:44:09.650 --> 00:44:09.660 align:start position:0% 00:44:09.660 --> 00:44:10.880 align:start position:0% [Music] 00:44:10.880 --> 00:44:10.890 align:start position:0% [Music] 00:44:10.890 --> 00:44:18.340 align:start position:0% [Music] so<00:44:12.740> in<00:44:14.150> this<00:44:15.150> case<00:44:15.720> we<00:44:17.000> looking<00:44:18.000> at 00:44:18.340 --> 00:44:18.350 align:start position:0% so in this case we looking at 00:44:18.350 --> 00:44:23.830 align:start position:0% so in this case we looking at [Music] 00:44:23.830 --> 00:44:23.840 align:start position:0% 00:44:23.840 --> 00:44:28.390 align:start position:0% alright<00:44:24.840> so<00:44:25.850> circuits<00:44:26.850> available<00:44:27.000> motors<00:44:27.720> and 00:44:28.390 --> 00:44:28.400 align:start position:0% alright so circuits available motors and 00:44:28.400 --> 00:44:31.070 align:start position:0% alright so circuits available motors and me<00:44:29.430> come<00:44:29.670> on<00:44:29.820> it<00:44:29.970> in<00:44:30.120> this<00:44:30.570> case<00:44:30.630> a<00:44:30.840> main 00:44:31.070 --> 00:44:31.080 align:start position:0% me come on it in this case a main 00:44:31.080 --> 00:44:35.330 align:start position:0% me come on it in this case a main component<00:44:31.530> is<00:44:31.620> the<00:44:31.830> phone<00:44:33.950> this<00:44:34.950> is<00:44:35.130> very 00:44:35.330 --> 00:44:35.340 align:start position:0% component is the phone this is very 00:44:35.340 --> 00:44:38.030 align:start position:0% component is the phone this is very defined<00:44:35.880> the<00:44:36.120> signals<00:44:36.540> so<00:44:37.110> these<00:44:37.320> are<00:44:37.530> public 00:44:38.030 --> 00:44:38.040 align:start position:0% defined the signals so these are public 00:44:38.040 --> 00:44:41.660 align:start position:0% defined the signals so these are public inputs<00:44:38.670> and<00:44:38.970> these<00:44:39.840> are<00:44:40.080> private<00:44:40.410> inputs<00:44:40.890> so<00:44:41.640> a 00:44:41.660 --> 00:44:41.670 align:start position:0% inputs and these are private inputs so a 00:44:41.670 --> 00:44:44.150 align:start position:0% inputs and these are private inputs so a permanent<00:44:42.150> list<00:44:42.300> included<00:44:42.750> the<00:44:42.900> identity<00:44:43.620> the 00:44:44.150 --> 00:44:44.160 align:start position:0% permanent list included the identity the 00:44:44.160 --> 00:44:49.030 align:start position:0% permanent list included the identity the public<00:44:44.700> key<00:44:44.910> as<00:44:45.420> a<00:44:46.110> component<00:44:47.150> propose<00:44:48.150> the 00:44:49.030 --> 00:44:49.040 align:start position:0% public key as a component propose the 00:44:49.040 --> 00:44:52.580 align:start position:0% public key as a component propose the identity<00:44:50.040> commitment<00:44:50.610> as<00:44:51.120> well<00:44:52.020> as<00:44:52.320> the 00:44:52.580 --> 00:44:52.590 align:start position:0% identity commitment as well as the 00:44:52.590 --> 00:44:55.900 align:start position:0% identity commitment as well as the second<00:44:53.100> child<00:44:53.340> that<00:44:54.060> was<00:44:54.440> generated<00:44:55.440> and<00:44:55.560> the 00:44:55.900 --> 00:44:55.910 align:start position:0% second child that was generated and the 00:44:55.910 --> 00:44:59.840 align:start position:0% second child that was generated and the mother<00:44:56.910> constant<00:44:58.040> as<00:44:59.040> for<00:44:59.280> the<00:44:59.340> timing<00:44:59.520> was 00:44:59.840 --> 00:44:59.850 align:start position:0% mother constant as for the timing was 00:44:59.850 --> 00:45:02.690 align:start position:0% mother constant as for the timing was those<00:45:00.180> police<00:45:00.480> actually<00:45:00.930> single<00:45:01.440> and<00:45:01.620> B<00:45:01.740> X<00:45:02.490> on 00:45:02.690 --> 00:45:02.700 align:start position:0% those police actually single and B X on 00:45:02.700 --> 00:45:07.820 align:start position:0% those police actually single and B X on a<00:45:02.730> non-fire<00:45:05.000> so<00:45:06.000> this<00:45:06.930> is<00:45:07.110> where<00:45:07.290> I<00:45:07.320> get<00:45:07.620> really 00:45:07.820 --> 00:45:07.830 align:start position:0% a non-fire so this is where I get really 00:45:07.830 --> 00:45:12.590 align:start position:0% a non-fire so this is where I get really detailed<00:45:08.430> and<00:45:09.230> a<00:45:10.880> lot<00:45:11.880> of<00:45:11.970> projects<00:45:12.300> using 00:45:12.590 --> 00:45:12.600 align:start position:0% detailed and a lot of projects using 00:45:12.600 --> 00:45:20.270 align:start position:0% detailed and a lot of projects using cell<00:45:13.230> phone<00:45:13.410> such<00:45:13.920> as<00:45:14.180> CT<00:45:18.170> lower-right<00:45:19.280> also 00:45:20.270 --> 00:45:20.280 align:start position:0% cell phone such as CT lower-right also 00:45:20.280 --> 00:45:23.210 align:start position:0% cell phone such as CT lower-right also to<00:45:20.700> a<00:45:20.730> lot<00:45:21.000> well<00:45:21.540> country<00:45:21.780> verification<00:45:22.530> I 00:45:23.210 --> 00:45:23.220 align:start position:0% to a lot well country verification I 00:45:23.220 --> 00:45:25.310 align:start position:0% to a lot well country verification I mean<00:45:23.910> signature<00:45:24.270> verification<00:45:24.330> about<00:45:25.080> Madrid 00:45:25.310 --> 00:45:25.320 align:start position:0% mean signature verification about Madrid 00:45:25.320 --> 00:45:28.910 align:start position:0% mean signature verification about Madrid about<00:45:26.310> the<00:45:26.400> truth<00:45:27.020> but<00:45:28.020> also<00:45:28.170> it<00:45:28.440> but<00:45:28.650> just<00:45:28.770> in 00:45:28.910 --> 00:45:28.920 align:start position:0% about the truth but also it but just in 00:45:28.920 --> 00:45:30.200 align:start position:0% about the truth but also it but just in a<00:45:28.980> different<00:45:29.010> way<00:45:29.280> because<00:45:29.490> they're<00:45:29.820> using<00:45:30.000> it 00:45:30.200 --> 00:45:30.210 align:start position:0% a different way because they're using it 00:45:30.210 --> 00:45:32.980 align:start position:0% a different way because they're using it for<00:45:31.010> verification 00:45:32.980 --> 00:45:32.990 align:start position:0% for verification 00:45:32.990 --> 00:45:39.730 align:start position:0% for verification so<00:45:35.030> this<00:45:36.030> so<00:45:36.990> that<00:45:37.170> students<00:45:37.560> in<00:45:37.770> my<00:45:37.890> example 00:45:39.730 --> 00:45:39.740 align:start position:0% so this so that students in my example 00:45:39.740 --> 00:45:42.820 align:start position:0% so this so that students in my example so<00:45:40.740> let's<00:45:40.920> say<00:45:41.070> what<00:45:41.280> to<00:45:41.400> verify<00:45:41.760> that<00:45:41.790> the 00:45:42.820 --> 00:45:42.830 align:start position:0% so let's say what to verify that the 00:45:42.830 --> 00:45:46.280 align:start position:0% so let's say what to verify that the identity<00:45:43.830> commitment<00:45:44.460> is<00:45:44.700> valid<00:45:45.140> which<00:45:46.140> is 00:45:46.280 --> 00:45:46.290 align:start position:0% identity commitment is valid which is 00:45:46.290 --> 00:45:48.170 align:start position:0% identity commitment is valid which is going<00:45:46.620> to<00:45:46.710> check<00:45:46.860> whether<00:45:47.010> the<00:45:47.250> hash<00:45:47.550> of<00:45:47.910> the 00:45:48.170 --> 00:45:48.180 align:start position:0% going to check whether the hash of the 00:45:48.180 --> 00:45:50.780 align:start position:0% going to check whether the hash of the three<00:45:48.780> components<00:45:49.500> for<00:45:49.920> the<00:45:49.980> key<00:45:50.190> identity 00:45:50.780 --> 00:45:50.790 align:start position:0% three components for the key identity 00:45:50.790 --> 00:45:53.360 align:start position:0% three components for the key identity trap<00:45:51.120> dog<00:45:51.300> energy<00:45:51.990> amplifier<00:45:52.220> matches<00:45:53.220> the 00:45:53.360 --> 00:45:53.370 align:start position:0% trap dog energy amplifier matches the 00:45:53.370 --> 00:45:58.100 align:start position:0% trap dog energy amplifier matches the given<00:45:53.630> intensity<00:45:54.630> competent<00:45:55.640> so<00:45:57.110> circuits 00:45:58.100 --> 00:45:58.110 align:start position:0% given intensity competent so circuits 00:45:58.110 --> 00:46:01.280 align:start position:0% given intensity competent so circuits have<00:45:58.320> inputs<00:45:58.950> and<00:45:59.040> outputs<00:45:59.660> no<00:46:00.660> submissive 00:46:01.280 --> 00:46:01.290 align:start position:0% have inputs and outputs no submissive 00:46:01.290 --> 00:46:04.100 align:start position:0% have inputs and outputs no submissive inputs<00:46:01.680> and<00:46:01.890> as<00:46:02.820> long<00:46:03.030> as<00:46:03.120> the<00:46:03.210> inputs<00:46:03.570> are 00:46:04.100 --> 00:46:04.110 align:start position:0% inputs and as long as the inputs are 00:46:04.110 --> 00:46:08.510 align:start position:0% inputs and as long as the inputs are valid<00:46:04.290> then<00:46:04.890> this<00:46:05.250> occurs<00:46:05.520> well<00:46:05.730> right<00:46:06.390> so<00:46:07.520> we 00:46:08.510 --> 00:46:08.520 align:start position:0% valid then this occurs well right so we 00:46:08.520 --> 00:46:12.500 align:start position:0% valid then this occurs well right so we have<00:46:08.970> a<00:46:09.300> component<00:46:09.930> color<00:46:10.260> person<00:46:10.680> come<00:46:11.190> on<00:46:11.510> it 00:46:12.500 --> 00:46:12.510 align:start position:0% have a component color person come on it 00:46:12.510 --> 00:46:14.690 align:start position:0% have a component color person come on it doesn't<00:46:13.440> commitment<00:46:13.890> which<00:46:14.160> is<00:46:14.280> like<00:46:14.430> the<00:46:14.520> - 00:46:14.690 --> 00:46:14.700 align:start position:0% doesn't commitment which is like the - 00:46:14.700 --> 00:46:16.780 align:start position:0% doesn't commitment which is like the - function<00:46:15.060> that's<00:46:15.210> for<00:46:15.480> need<00:46:15.660> for<00:46:15.870> staffs<00:46:16.110> and 00:46:16.780 --> 00:46:16.790 align:start position:0% function that's for need for staffs and 00:46:16.790 --> 00:46:22.340 align:start position:0% function that's for need for staffs and what<00:46:17.790> we<00:46:17.880> do<00:46:18.090> is<00:46:18.420> that<00:46:18.510> it<00:46:19.080> be<00:46:20.150> publicly<00:46:21.350> the 00:46:22.340 --> 00:46:22.350 align:start position:0% what we do is that it be publicly the 00:46:22.350 --> 00:46:26.050 align:start position:0% what we do is that it be publicly the bits<00:46:22.590> on<00:46:22.830> the<00:46:22.860> public<00:46:23.220> key<00:46:23.400> we<00:46:23.970> do<00:46:24.150> that<00:46:24.720> and 00:46:26.050 --> 00:46:26.060 align:start position:0% bits on the public key we do that and 00:46:26.060 --> 00:46:32.960 align:start position:0% bits on the public key we do that and assign<00:46:27.060> them<00:46:28.370> into<00:46:29.370> the<00:46:30.800> Edison<00:46:31.970> hash 00:46:32.960 --> 00:46:32.970 align:start position:0% assign them into the Edison hash 00:46:32.970 --> 00:46:35.060 align:start position:0% assign them into the Edison hash component<00:46:33.570> and<00:46:34.140> we<00:46:34.230> do<00:46:34.350> the<00:46:34.470> same<00:46:34.650> with<00:46:34.830> the 00:46:35.060 --> 00:46:35.070 align:start position:0% component and we do the same with the 00:46:35.070 --> 00:46:37.820 align:start position:0% component and we do the same with the identifier<00:46:36.030> and<00:46:36.390> intractable 00:46:37.820 --> 00:46:37.830 align:start position:0% identifier and intractable 00:46:37.830 --> 00:46:41.000 align:start position:0% identifier and intractable so<00:46:38.610> thinking<00:46:38.910> about<00:46:38.970> this<00:46:39.470> DSL<00:46:40.470> is<00:46:40.650> that<00:46:40.860> you 00:46:41.000 --> 00:46:41.010 align:start position:0% so thinking about this DSL is that you 00:46:41.010 --> 00:46:42.670 align:start position:0% so thinking about this DSL is that you need<00:46:41.160> to<00:46:41.250> do<00:46:41.370> a<00:46:41.400> lot<00:46:41.700> like<00:46:41.850> bit<00:46:42.120> level 00:46:42.670 --> 00:46:42.680 align:start position:0% need to do a lot like bit level 00:46:42.680 --> 00:46:46.490 align:start position:0% need to do a lot like bit level operations<00:46:43.680> which<00:46:44.280> is<00:46:44.400> super<00:46:44.670> tedious<00:46:45.110> and<00:46:46.110> so 00:46:46.490 --> 00:46:46.500 align:start position:0% operations which is super tedious and so 00:46:46.500 --> 00:46:54.200 align:start position:0% operations which is super tedious and so credits<00:46:46.950> all<00:46:47.100> go<00:46:47.280> to<00:46:47.780> college<00:46:53.030> someone<00:46:54.030> raised 00:46:54.200 --> 00:46:54.210 align:start position:0% credits all go to college someone raised 00:46:54.210 --> 00:46:58.360 align:start position:0% credits all go to college someone raised mother<00:46:54.450> right<00:46:55.790> and<00:46:56.790> we<00:46:57.330> do<00:46:57.720> the<00:46:57.870> same<00:46:58.080> for 00:46:58.360 --> 00:46:58.370 align:start position:0% mother right and we do the same for 00:46:58.370 --> 00:47:01.250 align:start position:0% mother right and we do the same for other<00:46:59.370> components 00:47:01.250 --> 00:47:01.260 align:start position:0% other components 00:47:01.260 --> 00:47:07.730 align:start position:0% other components it's<00:47:02.260> not<00:47:02.410> and<00:47:03.960> another<00:47:04.960> day<00:47:05.110> if<00:47:05.500> all<00:47:05.830> these 00:47:07.730 --> 00:47:07.740 align:start position:0% it's not and another day if all these 00:47:07.740 --> 00:47:09.720 align:start position:0% it's not and another day if all these all<00:47:08.740> these<00:47:08.950> constraints 00:47:09.720 --> 00:47:09.730 align:start position:0% all these constraints 00:47:09.730 --> 00:47:12.620 align:start position:0% all these constraints check<00:47:10.030> out<00:47:10.150> then<00:47:10.930> if<00:47:11.050> also<00:47:11.230> get<00:47:11.620> kissed<00:47:11.860> and 00:47:12.620 --> 00:47:12.630 align:start position:0% check out then if also get kissed and 00:47:12.630 --> 00:47:16.770 align:start position:0% check out then if also get kissed and the<00:47:13.860> and<00:47:14.860> moving<00:47:15.130> on<00:47:15.250> the<00:47:15.310> stack<00:47:15.570> you'll<00:47:16.570> see 00:47:16.770 --> 00:47:16.780 align:start position:0% the and moving on the stack you'll see 00:47:16.780 --> 00:47:20.400 align:start position:0% the and moving on the stack you'll see that<00:47:18.000> this<00:47:19.000> you'll<00:47:19.360> see<00:47:19.540> this<00:47:19.720> it's<00:47:20.080> not<00:47:20.230> on 00:47:20.400 --> 00:47:20.410 align:start position:0% that this you'll see this it's not on 00:47:20.410 --> 00:47:23.970 align:start position:0% that this you'll see this it's not on trying<00:47:20.620> to<00:47:20.770> verify<00:47:20.950> approved<00:47:21.840> potential<00:47:22.980> will 00:47:23.970 --> 00:47:23.980 align:start position:0% trying to verify approved potential will 00:47:23.980 --> 00:47:29.190 align:start position:0% trying to verify approved potential will go<00:47:24.220> back<00:47:24.640> to<00:47:24.670> the<00:47:24.940> semaphore<00:47:26.700> contract<00:47:28.200> that 00:47:29.190 --> 00:47:29.200 align:start position:0% go back to the semaphore contract that 00:47:29.200 --> 00:47:32.550 align:start position:0% go back to the semaphore contract that will<00:47:29.440> pass<00:47:30.330> this<00:47:31.330> function<00:47:31.510> will<00:47:32.230> execute 00:47:32.550 --> 00:47:32.560 align:start position:0% will pass this function will execute 00:47:32.560 --> 00:47:38.190 align:start position:0% will pass this function will execute successfully<00:47:33.070> and<00:47:35.640> and<00:47:36.900> that's<00:47:37.900> the<00:47:38.020> only 00:47:38.190 --> 00:47:38.200 align:start position:0% successfully and and that's the only 00:47:38.200 --> 00:47:43.470 align:start position:0% successfully and and that's the only rule<00:47:38.580> with<00:47:39.580> semaphore<00:47:40.530> so<00:47:42.090> yeah<00:47:43.090> I'd<00:47:43.210> like<00:47:43.420> to 00:47:43.470 --> 00:47:43.480 align:start position:0% rule with semaphore so yeah I'd like to 00:47:43.480 --> 00:47:45.690 align:start position:0% rule with semaphore so yeah I'd like to cover<00:47:43.780> a<00:47:43.870> lot<00:47:44.110> of<00:47:44.200> tight<00:47:44.440> detail<00:47:45.190> in<00:47:45.310> this<00:47:45.430> and 00:47:45.690 --> 00:47:45.700 align:start position:0% cover a lot of tight detail in this and 00:47:45.700 --> 00:47:48.810 align:start position:0% cover a lot of tight detail in this and there's<00:47:46.000> so<00:47:46.120> much<00:47:46.240> Monica<00:47:46.750> so<00:47:47.560> I<00:47:48.040> would 00:47:48.810 --> 00:47:48.820 align:start position:0% there's so much Monica so I would 00:47:48.820 --> 00:47:50.940 align:start position:0% there's so much Monica so I would encourage<00:47:48.940> I'm<00:47:49.390> ready<00:47:49.600> to<00:47:49.810> join<00:47:50.620> the 00:47:50.940 --> 00:47:50.950 align:start position:0% encourage I'm ready to join the 00:47:50.950 --> 00:48:03.660 align:start position:0% encourage I'm ready to join the semaphore<00:47:51.460> society<00:47:52.230> pentagram<00:47:53.230> so 00:48:03.660 --> 00:48:03.670 align:start position:0% 00:48:03.670 --> 00:48:06.849 align:start position:0% this<00:48:04.670> is<00:48:04.819> where<00:48:04.999> a<00:48:05.299> lot<00:48:05.509> of<00:48:05.539> the<00:48:05.839> research<00:48:06.619> and 00:48:06.849 --> 00:48:06.859 align:start position:0% this is where a lot of the research and 00:48:06.859 --> 00:48:10.180 align:start position:0% this is where a lot of the research and development<00:48:07.339> in<00:48:07.999> to<00:48:08.650> see<00:48:09.650> this<00:48:09.799> Knox's 00:48:10.180 --> 00:48:10.190 align:start position:0% development in to see this Knox's 00:48:10.190 --> 00:48:14.890 align:start position:0% development in to see this Knox's company<00:48:10.549> and<00:48:12.640> this<00:48:13.640> is<00:48:13.700> also<00:48:13.970> where<00:48:14.210> he<00:48:14.269> thinks 00:48:14.890 --> 00:48:14.900 align:start position:0% company and this is also where he thinks 00:48:14.900 --> 00:48:17.259 align:start position:0% company and this is also where he thinks a<00:48:15.019> party<00:48:15.799> that<00:48:16.309> mixer<00:48:16.640> that<00:48:16.789> gives<00:48:17.029> us<00:48:17.150> a 00:48:17.259 --> 00:48:17.269 align:start position:0% a party that mixer that gives us a 00:48:17.269 --> 00:48:21.579 align:start position:0% a party that mixer that gives us a fastball<00:48:18.609> it's<00:48:19.609> just<00:48:19.819> yeah<00:48:20.839> Internet's<00:48:21.470> not 00:48:21.579 --> 00:48:21.589 align:start position:0% fastball it's just yeah Internet's not 00:48:21.589 --> 00:48:30.980 align:start position:0% fastball it's just yeah Internet's not working<00:48:21.650> for<00:48:22.009> me<00:48:22.069> right<00:48:22.160> now<00:48:22.430> but<00:48:26.319> don't<00:48:27.319> deal 00:48:30.980 --> 00:48:30.990 align:start position:0% 00:48:30.990 --> 00:48:37.130 align:start position:0% [Music] 00:48:37.130 --> 00:48:37.140 align:start position:0% 00:48:37.140 --> 00:48:41.750 align:start position:0% yeah<00:48:39.170> so<00:48:40.170> be<00:48:40.620> good<00:48:40.770> when<00:48:41.160> we<00:48:41.280> go<00:48:41.490> kind<00:48:41.700> of 00:48:41.750 --> 00:48:41.760 align:start position:0% yeah so be good when we go kind of 00:48:41.760 --> 00:48:43.730 align:start position:0% yeah so be good when we go kind of github<00:48:42.060> you<00:48:42.330> can<00:48:42.390> see<00:48:42.750> the<00:48:43.260> link<00:48:43.560> to<00:48:43.620> the 00:48:43.730 --> 00:48:43.740 align:start position:0% github you can see the link to the 00:48:43.740 --> 00:48:46.280 align:start position:0% github you can see the link to the Democrat<00:48:44.220> group<00:48:44.400> and<00:48:45.000> how<00:48:45.660> much<00:48:45.780> anybody<00:48:45.990> to 00:48:46.280 --> 00:48:46.290 align:start position:0% Democrat group and how much anybody to 00:48:46.290 --> 00:48:48.200 align:start position:0% Democrat group and how much anybody to approach<00:48:46.680> me<00:48:46.890> for<00:48:47.250> different<00:48:47.610> questions 00:48:48.200 --> 00:48:48.210 align:start position:0% approach me for different questions 00:48:48.210 --> 00:48:51.020 align:start position:0% approach me for different questions about<00:48:48.360> how<00:48:48.630> to<00:48:48.660> use<00:48:49.140> simple<00:48:50.040> and<00:48:50.190> if<00:48:50.760> one<00:48:51.000> is 00:48:51.020 --> 00:48:51.030 align:start position:0% about how to use simple and if one is 00:48:51.030 --> 00:48:53.930 align:start position:0% about how to use simple and if one is not<00:48:51.180> real<00:48:51.390> and<00:48:51.630> if<00:48:51.840> you<00:48:51.930> wanna<00:48:52.460> apply<00:48:53.460> a<00:48:53.550> file 00:48:53.930 --> 00:48:53.940 align:start position:0% not real and if you wanna apply a file 00:48:53.940 --> 00:48:57.320 align:start position:0% not real and if you wanna apply a file applications<00:48:54.480> I<00:48:55.280> am<00:48:56.280> writing<00:48:56.580> myself<00:48:56.910> an 00:48:57.320 --> 00:48:57.330 align:start position:0% applications I am writing myself an 00:48:57.330 --> 00:48:59.180 align:start position:0% applications I am writing myself an ellipse<00:48:57.630> and<00:48:57.840> publishes<00:48:58.380> a<00:48:58.530> and<00:48:58.830> compact 00:48:59.180 --> 00:48:59.190 align:start position:0% ellipse and publishes a and compact 00:48:59.190 --> 00:49:01.730 align:start position:0% ellipse and publishes a and compact method<00:48:59.460> as<00:48:59.580> you<00:48:59.790> use<00:49:00.720> it<00:49:00.750> more<00:49:01.050> easily<00:49:01.200> and 00:49:01.730 --> 00:49:01.740 align:start position:0% method as you use it more easily and 00:49:01.740 --> 00:49:03.590 align:start position:0% method as you use it more easily and doesn't<00:49:02.430> write<00:49:02.700> blog<00:49:02.910> posts<00:49:02.940> and<00:49:03.270> a<00:49:03.360> comment 00:49:03.590 --> 00:49:03.600 align:start position:0% doesn't write blog posts and a comment 00:49:03.600 --> 00:49:07.220 align:start position:0% doesn't write blog posts and a comment Asia<00:49:03.780> to<00:49:04.110> help<00:49:04.820> developers<00:49:05.820> to<00:49:06.230> integrate 00:49:07.220 --> 00:49:07.230 align:start position:0% Asia to help developers to integrate 00:49:07.230 --> 00:49:25.970 align:start position:0% Asia to help developers to integrate this<00:49:07.590> into<00:49:11.180> yes<00:49:20.990> challenges<00:49:24.560> it's<00:49:25.560> not<00:49:25.740> in<00:49:25.860> two 00:49:25.970 --> 00:49:25.980 align:start position:0% this into yes challenges it's not in two 00:49:25.980 --> 00:49:27.710 align:start position:0% this into yes challenges it's not in two weeks<00:49:26.160> because<00:49:26.310> I<00:49:26.610> company<00:49:27.000> said<00:49:27.210> by<00:49:27.330> one<00:49:27.480> code 00:49:27.710 --> 00:49:27.720 align:start position:0% weeks because I company said by one code 00:49:27.720 --> 00:49:34.190 align:start position:0% weeks because I company said by one code from<00:49:28.170> the<00:49:28.650> mixer<00:49:30.530> by<00:49:31.530> Gooden<00:49:31.860> itself<00:49:33.020> this<00:49:34.020> is 00:49:34.190 --> 00:49:34.200 align:start position:0% from the mixer by Gooden itself this is 00:49:34.200 --> 00:49:37.310 align:start position:0% from the mixer by Gooden itself this is my<00:49:34.760> different<00:49:35.760> covet<00:49:36.060> test<00:49:36.270> that<00:49:36.420> you<00:49:37.140> see 00:49:37.310 --> 00:49:37.320 align:start position:0% my different covet test that you see 00:49:37.320 --> 00:49:39.980 align:start position:0% my different covet test that you see that<00:49:37.410> the<00:49:37.560> UI<00:49:37.910> the<00:49:38.910> UI<00:49:39.060> build<00:49:39.450> is<00:49:39.540> like<00:49:39.720> almost 00:49:39.980 --> 00:49:39.990 align:start position:0% that the UI the UI build is like almost 00:49:39.990 --> 00:49:46.790 align:start position:0% that the UI the UI build is like almost the<00:49:40.080> same<00:49:42.800> yeah<00:49:43.800> so<00:49:44.780> this<00:49:45.780> is<00:49:45.960> like<00:49:46.170> what 00:49:46.790 --> 00:49:46.800 align:start position:0% the same yeah so this is like what 00:49:46.800 --> 00:49:48.650 align:start position:0% the same yeah so this is like what another<00:49:47.070> application<00:49:47.400> of<00:49:47.640> all<00:49:48.030> fishes<00:49:48.540> the 00:49:48.650 --> 00:49:48.660 align:start position:0% another application of all fishes the 00:49:48.660 --> 00:49:51.110 align:start position:0% another application of all fishes the pizza<00:49:48.960> I<00:49:49.200> never<00:49:50.070> talked<00:49:50.280> about<00:49:50.400> this<00:49:50.610> two<00:49:51.000> days 00:49:51.110 --> 00:49:51.120 align:start position:0% pizza I never talked about this two days 00:49:51.120 --> 00:49:52.760 align:start position:0% pizza I never talked about this two days ago 00:49:52.760 --> 00:49:52.770 align:start position:0% ago 00:49:52.770 --> 00:49:55.070 align:start position:0% ago you<00:49:53.130> can<00:49:53.310> basically<00:49:53.460> write<00:49:54.030> when<00:49:54.630> you<00:49:54.720> deposit 00:49:55.070 --> 00:49:55.080 align:start position:0% you can basically write when you deposit 00:49:55.080 --> 00:49:57.590 align:start position:0% you can basically write when you deposit F<00:49:55.500> into<00:49:55.860> the<00:49:55.950> mixer<00:49:56.280> what<00:49:56.970> you're<00:49:57.090> doing<00:49:57.390> this 00:49:57.590 --> 00:49:57.600 align:start position:0% F into the mixer what you're doing this 00:49:57.600 --> 00:49:59.840 align:start position:0% F into the mixer what you're doing this which<00:49:58.050> measures<00:49:58.530> the<00:49:58.560> relative<00:49:58.740> identity<00:49:59.370> and 00:49:59.840 --> 00:49:59.850 align:start position:0% which measures the relative identity and 00:49:59.850 --> 00:50:01.790 align:start position:0% which measures the relative identity and then<00:50:00.000> you<00:50:00.090> draw<00:50:00.450> your<00:50:00.810> senator<00:50:01.230> sitter<00:50:01.470> and 00:50:01.790 --> 00:50:01.800 align:start position:0% then you draw your senator sitter and 00:50:01.800 --> 00:50:03.740 align:start position:0% then you draw your senator sitter and because<00:50:02.220> he<00:50:02.310> cannot<00:50:02.580> send<00:50:03.330> us<00:50:03.420> things<00:50:03.540> like 00:50:03.740 --> 00:50:03.750 align:start position:0% because he cannot send us things like 00:50:03.750 --> 00:50:06.050 align:start position:0% because he cannot send us things like that<00:50:03.870> price<00:50:04.080> you<00:50:04.350> cannot<00:50:04.500> expect<00:50:04.890> and<00:50:05.280> because 00:50:06.050 --> 00:50:06.060 align:start position:0% that price you cannot expect and because 00:50:06.060 --> 00:50:11.020 align:start position:0% that price you cannot expect and because we<00:50:06.210> have<00:50:06.450> and<00:50:06.690> because<00:50:07.410> it<00:50:07.710> cannot<00:50:09.920> link 00:50:11.020 --> 00:50:11.030 align:start position:0% we have and because it cannot link 00:50:11.030 --> 00:50:15.350 align:start position:0% we have and because it cannot link deposits<00:50:12.030> to<00:50:12.680> signals<00:50:13.680> it<00:50:14.580> because<00:50:15.030> it<00:50:15.180> cannot 00:50:15.350 --> 00:50:15.360 align:start position:0% deposits to signals it because it cannot 00:50:15.360 --> 00:50:17.270 align:start position:0% deposits to signals it because it cannot link<00:50:15.600> signals<00:50:16.020> to<00:50:16.140> identities<00:50:16.590> it's<00:50:17.130> not 00:50:17.270 --> 00:50:17.280 align:start position:0% link signals to identities it's not 00:50:17.280 --> 00:50:20.540 align:start position:0% link signals to identities it's not being<00:50:17.520> controllers<00:50:18.090> from<00:50:18.920> deposits<00:50:19.920> and<00:50:20.100> it's 00:50:20.540 --> 00:50:20.550 align:start position:0% being controllers from deposits and it's 00:50:20.550 --> 00:50:22.280 align:start position:0% being controllers from deposits and it's how<00:50:20.640> the<00:50:20.700> mixer<00:50:21.030> works<00:50:21.210> using<00:50:21.690> semaphore<00:50:21.960> the 00:50:22.280 --> 00:50:22.290 align:start position:0% how the mixer works using semaphore the 00:50:22.290 --> 00:50:26.240 align:start position:0% how the mixer works using semaphore the base<00:50:22.440> value<00:50:23.300> yeah<00:50:24.300> so<00:50:24.990> just<00:50:25.560> a<00:50:25.650> given<00:50:26.130> to 00:50:26.240 --> 00:50:26.250 align:start position:0% base value yeah so just a given to 00:50:26.250 --> 00:50:26.900 align:start position:0% base value yeah so just a given to demonstrate 00:50:26.900 --> 00:50:26.910 align:start position:0% demonstrate 00:50:26.910 --> 00:50:30.829 align:start position:0% demonstrate but<00:50:27.900> just<00:50:28.470> how<00:50:28.910> it's<00:50:29.910> going<00:50:30.329> to<00:50:30.390> download<00:50:30.539> the 00:50:30.829 --> 00:50:30.839 align:start position:0% but just how it's going to download the 00:50:30.839 --> 00:50:33.319 align:start position:0% but just how it's going to download the be<00:50:30.990> use<00:50:31.170> of<00:50:31.380> the<00:50:31.589> elderly<00:50:32.059> generally<00:50:33.059> the<00:50:33.180> book 00:50:33.319 --> 00:50:33.329 align:start position:0% be use of the elderly generally the book 00:50:33.329 --> 00:50:35.299 align:start position:0% be use of the elderly generally the book improve<00:50:33.690> something<00:50:34.589> that<00:50:34.740> proved<00:50:34.980> to<00:50:35.039> be<00:50:35.130> a 00:50:35.299 --> 00:50:35.309 align:start position:0% improve something that proved to be a 00:50:35.309 --> 00:50:37.460 align:start position:0% improve something that proved to be a young<00:50:35.609> which<00:50:36.119> sends<00:50:36.480> the<00:50:36.509> transaction<00:50:36.839> and<00:50:37.319> is 00:50:37.460 --> 00:50:37.470 align:start position:0% young which sends the transaction and is 00:50:37.470 --> 00:50:40.759 align:start position:0% young which sends the transaction and is a<00:50:37.500> guest<00:50:37.799> users<00:50:38.250> behalf<00:50:38.599> and<00:50:39.599> the<00:50:39.869> user<00:50:40.440> gets 00:50:40.759 --> 00:50:40.769 align:start position:0% a guest users behalf and the user gets 00:50:40.769 --> 00:50:44.089 align:start position:0% a guest users behalf and the user gets better<00:50:41.509> so<00:50:42.509> it's<00:50:42.900> like<00:50:43.079> a<00:50:43.109> safe<00:50:43.410> design<00:50:43.769> for 00:50:44.089 --> 00:50:44.099 align:start position:0% better so it's like a safe design for 00:50:44.099 --> 00:50:48.370 align:start position:0% better so it's like a safe design for identification 00:50:48.370 --> 00:50:48.380 align:start position:0% 00:50:48.380 --> 00:50:56.329 align:start position:0% any<00:50:49.380> challenges<00:50:50.039> or<00:50:50.099> right<00:50:55.009> there's<00:50:56.009> a<00:50:56.099> ton<00:50:56.309> of 00:50:56.329 --> 00:50:56.339 align:start position:0% any challenges or right there's a ton of 00:50:56.339 --> 00:51:03.769 align:start position:0% any challenges or right there's a ton of challengers<00:50:56.819> because<00:51:00.589> I<00:51:01.940> guess<00:51:02.940> I<00:51:03.240> guess<00:51:03.750> the 00:51:03.769 --> 00:51:03.779 align:start position:0% challengers because I guess I guess the 00:51:03.779 --> 00:51:05.660 align:start position:0% challengers because I guess I guess the first<00:51:04.049> thing<00:51:04.319> is<00:51:04.470> like<00:51:04.710> subscribing<00:51:05.369> a<00:51:05.519> head 00:51:05.660 --> 00:51:05.670 align:start position:0% first thing is like subscribing a head 00:51:05.670 --> 00:51:06.829 align:start position:0% first thing is like subscribing a head around<00:51:05.880> all<00:51:06.119> the<00:51:06.299> different<00:51:06.569> types<00:51:06.779> of 00:51:06.829 --> 00:51:06.839 align:start position:0% around all the different types of 00:51:06.839 --> 00:51:10.839 align:start position:0% around all the different types of materials<00:51:06.960> and<00:51:07.740> the<00:51:07.890> types<00:51:08.309> of<00:51:09.230> photographic 00:51:10.839 --> 00:51:10.849 align:start position:0% materials and the types of photographic 00:51:10.849 --> 00:51:13.579 align:start position:0% materials and the types of photographic primitives<00:51:11.849> that<00:51:12.059> I<00:51:12.119> use<00:51:12.329> but<00:51:13.049> you<00:51:13.289> can<00:51:13.440> even 00:51:13.579 --> 00:51:13.589 align:start position:0% primitives that I use but you can even 00:51:13.589 --> 00:51:15.470 align:start position:0% primitives that I use but you can even use<00:51:13.769> like<00:51:13.890> sha-256<00:51:14.640> hash<00:51:14.700> even<00:51:15.240> though<00:51:15.329> it's 00:51:15.470 --> 00:51:15.480 align:start position:0% use like sha-256 hash even though it's 00:51:15.480 --> 00:51:17.690 align:start position:0% use like sha-256 hash even though it's fastened<00:51:15.869> traditional<00:51:16.380> with<00:51:16.710> us<00:51:16.890> that<00:51:17.369> super 00:51:17.690 --> 00:51:17.700 align:start position:0% fastened traditional with us that super 00:51:17.700 --> 00:51:19.700 align:start position:0% fastened traditional with us that super slowly<00:51:17.910> stocks<00:51:18.269> and<00:51:18.539> get<00:51:19.349> into<00:51:19.559> them 00:51:19.700 --> 00:51:19.710 align:start position:0% slowly stocks and get into them 00:51:19.710 --> 00:51:22.519 align:start position:0% slowly stocks and get into them understanding<00:51:20.190> or<00:51:20.430> like<00:51:20.670> the<00:51:21.480> fact<00:51:21.720> that<00:51:21.779> the 00:51:22.519 --> 00:51:22.529 align:start position:0% understanding or like the fact that the 00:51:22.529 --> 00:51:23.900 align:start position:0% understanding or like the fact that the understand<00:51:22.890> hash<00:51:23.069> functions<00:51:23.490> at<00:51:23.609> the<00:51:23.640> top 00:51:23.900 --> 00:51:23.910 align:start position:0% understand hash functions at the top 00:51:23.910 --> 00:51:28.039 align:start position:0% understand hash functions at the top perform<00:51:24.269> differently<00:51:25.069> is<00:51:26.119> itself<00:51:27.119> like<00:51:27.839> one 00:51:28.039 --> 00:51:28.049 align:start position:0% perform differently is itself like one 00:51:28.049 --> 00:51:30.049 align:start position:0% perform differently is itself like one of<00:51:28.170> the<00:51:28.259> colors<00:51:28.589> that<00:51:28.619> that<00:51:29.490> people<00:51:29.789> have<00:51:29.940> to 00:51:30.049 --> 00:51:30.059 align:start position:0% of the colors that that people have to 00:51:30.059 --> 00:51:32.150 align:start position:0% of the colors that that people have to get<00:51:30.569> you<00:51:30.779> to<00:51:30.930> understand<00:51:31.349> this<00:51:31.500> whole<00:51:31.980> thing 00:51:32.150 --> 00:51:32.160 align:start position:0% get you to understand this whole thing 00:51:32.160 --> 00:51:35.029 align:start position:0% get you to understand this whole thing because<00:51:32.519> it<00:51:33.180> in<00:51:33.329> stocks<00:51:33.599> and<00:51:33.779> Memphis<00:51:34.170> kind<00:51:34.980> of 00:51:35.029 --> 00:51:35.039 align:start position:0% because it in stocks and Memphis kind of 00:51:35.039 --> 00:51:37.490 align:start position:0% because it in stocks and Memphis kind of different<00:51:35.369> so<00:51:36.079> that's<00:51:37.079> one<00:51:37.289> of<00:51:37.319> the 00:51:37.490 --> 00:51:37.500 align:start position:0% different so that's one of the 00:51:37.500 --> 00:51:42.579 align:start position:0% different so that's one of the extractions<00:51:38.130> that<00:51:38.900> we<00:51:39.900> want<00:51:40.230> to<00:51:41.269> help<00:51:42.269> people 00:51:42.579 --> 00:51:42.589 align:start position:0% extractions that we want to help people 00:51:42.589 --> 00:51:44.960 align:start position:0% extractions that we want to help people not<00:51:43.589> have<00:51:43.799> to<00:51:43.920> worry<00:51:44.069> about<00:51:44.190> and<00:51:44.640> they<00:51:44.759> use 00:51:44.960 --> 00:51:44.970 align:start position:0% not have to worry about and they use 00:51:44.970 --> 00:51:48.230 align:start position:0% not have to worry about and they use their<00:51:45.240> cell<00:51:45.450> phone<00:51:47.000> initially<00:51:48.000> the<00:51:48.119> name 00:51:48.230 --> 00:51:48.240 align:start position:0% their cell phone initially the name 00:51:48.240 --> 00:51:53.180 align:start position:0% their cell phone initially the name certifies<00:51:51.109> its<00:51:52.109> I'm<00:51:52.650> still<00:51:52.920> working 00:51:53.180 --> 00:51:53.190 align:start position:0% certifies its I'm still working 00:51:53.190 --> 00:51:55.579 align:start position:0% certifies its I'm still working documentation<00:51:53.849> and<00:51:54.539> guides<00:51:54.869> but<00:51:55.109> it's<00:51:55.410> an 00:51:55.579 --> 00:51:55.589 align:start position:0% documentation and guides but it's an 00:51:55.589 --> 00:52:01.849 align:start position:0% documentation and guides but it's an idea<00:51:55.680> and<00:51:59.630> so<00:52:00.630> all<00:52:00.839> these<00:52:00.960> functions<00:52:01.410> should 00:52:01.849 --> 00:52:01.859 align:start position:0% idea and so all these functions should 00:52:01.859 --> 00:52:09.349 align:start position:0% idea and so all these functions should help<00:52:02.160> developers<00:52:02.940> to<00:52:03.269> use<00:52:04.250> this<00:52:05.250> system<00:52:08.359> I 00:52:09.349 --> 00:52:09.359 align:start position:0% help developers to use this system I 00:52:09.359 --> 00:52:12.309 align:start position:0% help developers to use this system I will<00:52:10.019> have<00:52:10.230> by<00:52:10.349> 7<00:52:10.740> minutes<00:52:10.980> to<00:52:11.220> go 00:52:12.309 --> 00:52:12.319 align:start position:0% will have by 7 minutes to go 00:52:12.319 --> 00:52:15.600 align:start position:0% will have by 7 minutes to go maybe<00:52:13.319> I'll<00:52:13.470> take<00:52:13.589> like<00:52:13.740> two<00:52:14.160> more<00:52:14.309> questions 00:52:15.600 --> 00:52:15.610 align:start position:0% maybe I'll take like two more questions 00:52:15.610 --> 00:52:30.970 align:start position:0% maybe I'll take like two more questions [Music] 00:52:30.970 --> 00:52:30.980 align:start position:0% 00:52:30.980 --> 00:52:34.250 align:start position:0% like<00:52:31.980> they<00:52:32.700> thought<00:52:33.030> about<00:52:33.240> people<00:52:33.420> like<00:52:33.809> like 00:52:34.250 --> 00:52:34.260 align:start position:0% like they thought about people like like 00:52:34.260 --> 00:52:39.700 align:start position:0% like they thought about people like like sellout<00:52:34.680> down<00:52:34.920> to<00:52:35.220> Miami<00:52:35.790> but<00:52:35.940> it's<00:52:36.119> it<00:52:36.710> Wow 00:52:39.700 --> 00:52:39.710 align:start position:0% sellout down to Miami but it's it Wow 00:52:39.710 --> 00:52:42.410 align:start position:0% sellout down to Miami but it's it Wow the<00:52:40.710> juicer<00:52:40.950> is<00:52:41.099> around<00:52:41.700> telling<00:52:42.059> about<00:52:42.150> the 00:52:42.410 --> 00:52:42.420 align:start position:0% the juicer is around telling about the 00:52:42.420 --> 00:52:48.200 align:start position:0% the juicer is around telling about the book<00:52:42.630> what<00:52:43.140> is<00:52:43.260> there<00:52:43.470> is<00:52:44.000> through<00:52:45.000> that<00:52:47.210> the 00:52:48.200 --> 00:52:48.210 align:start position:0% book what is there is through that the 00:52:48.210 --> 00:52:51.680 align:start position:0% book what is there is through that the ability<00:52:48.690> to<00:52:48.720> any<00:52:49.730> maybe<00:52:50.730> you<00:52:51.180> know<00:52:51.359> if<00:52:51.480> Elvis 00:52:51.680 --> 00:52:51.690 align:start position:0% ability to any maybe you know if Elvis 00:52:51.690 --> 00:52:53.720 align:start position:0% ability to any maybe you know if Elvis fan<00:52:52.020> example<00:52:52.619> my<00:52:52.710> critics<00:52:53.130> of<00:52:53.220> my<00:52:53.339> features 00:52:53.720 --> 00:52:53.730 align:start position:0% fan example my critics of my features 00:52:53.730 --> 00:52:57.260 align:start position:0% fan example my critics of my features need<00:52:53.849> to<00:52:53.970> like<00:52:54.119> let<00:52:54.990> me<00:52:55.109> spend<00:52:55.380> once<00:52:56.270> but 00:52:57.260 --> 00:52:57.270 align:start position:0% need to like let me spend once but 00:52:57.270 --> 00:53:01.000 align:start position:0% need to like let me spend once but inviting<00:52:57.690> it<00:52:57.930> might<00:52:58.079> be<00:52:58.670> multiple<00:52:59.670> times 00:53:01.000 --> 00:53:01.010 align:start position:0% inviting it might be multiple times 00:53:01.010 --> 00:53:02.599 align:start position:0% inviting it might be multiple times right 00:53:02.599 --> 00:53:02.609 align:start position:0% right 00:53:02.609 --> 00:53:05.390 align:start position:0% right some<00:53:03.599> of<00:53:03.690> us<00:53:03.750> official<00:53:04.260> but<00:53:04.470> it<00:53:04.950> was<00:53:05.130> looking 00:53:05.390 --> 00:53:05.400 align:start position:0% some of us official but it was looking 00:53:05.400 --> 00:53:15.320 align:start position:0% some of us official but it was looking and<00:53:05.609> under<00:53:06.300> the<00:53:06.359> petition<00:53:06.900> that<00:53:06.930> lead<00:53:07.319> that's 00:53:15.320 --> 00:53:15.330 align:start position:0% 00:53:15.330 --> 00:53:34.270 align:start position:0% [Music] 00:53:34.270 --> 00:53:34.280 align:start position:0% 00:53:34.280 --> 00:53:37.620 align:start position:0% yeah<00:53:35.180> this<00:53:35.510> is<00:53:35.660> like<00:53:35.690> a<00:53:35.840> separate<00:53:36.200> project 00:53:37.620 --> 00:53:37.630 align:start position:0% yeah this is like a separate project 00:53:37.630 --> 00:53:41.200 align:start position:0% yeah this is like a separate project when<00:53:38.630> you<00:53:39.020> also<00:53:39.440> using<00:53:39.800> his<00:53:39.830> lungs<00:53:40.130> to<00:53:40.250> prevent 00:53:41.200 --> 00:53:41.210 align:start position:0% when you also using his lungs to prevent 00:53:41.210 --> 00:53:45.550 align:start position:0% when you also using his lungs to prevent pollution<00:53:41.599> in<00:53:42.010> Dallas<00:53:44.080> so<00:53:45.080> I<00:53:45.109> think<00:53:45.320> that 00:53:45.550 --> 00:53:45.560 align:start position:0% pollution in Dallas so I think that 00:53:45.560 --> 00:53:47.620 align:start position:0% pollution in Dallas so I think that ideally<00:53:45.859> -<00:53:46.099> is<00:53:46.369> that<00:53:46.550> using<00:53:47.000> a<00:53:47.180> safety<00:53:47.390> stock 00:53:47.620 --> 00:53:47.630 align:start position:0% ideally - is that using a safety stock 00:53:47.630 --> 00:53:50.470 align:start position:0% ideally - is that using a safety stock you<00:53:47.810> can<00:53:48.020> make<00:53:48.830> it<00:53:48.980> one<00:53:49.580> plus<00:53:49.790> to<00:53:50.000> buy<00:53:50.150> a<00:53:50.180> boat 00:53:50.470 --> 00:53:50.480 align:start position:0% you can make it one plus to buy a boat 00:53:50.480 --> 00:53:53.349 align:start position:0% you can make it one plus to buy a boat because<00:53:50.840> someone<00:53:51.320> could<00:53:51.530> pull<00:53:51.770> together<00:53:52.359> and 00:53:53.349 --> 00:53:53.359 align:start position:0% because someone could pull together and 00:53:53.359 --> 00:53:56.230 align:start position:0% because someone could pull together and make<00:53:53.390> you<00:53:53.720> all<00:53:53.750> you're<00:53:54.560> powerful<00:53:55.210> right<00:53:56.210> now 00:53:56.230 --> 00:53:56.240 align:start position:0% make you all you're powerful right now 00:53:56.240 --> 00:53:59.680 align:start position:0% make you all you're powerful right now I'd<00:53:56.480> rather<00:53:56.560> but<00:53:57.560> it's<00:53:58.310> like<00:53:58.580> I<00:53:59.030> don't<00:53:59.450> think 00:53:59.680 --> 00:53:59.690 align:start position:0% I'd rather but it's like I don't think 00:53:59.690 --> 00:54:02.410 align:start position:0% I'd rather but it's like I don't think it's<00:53:59.930> to<00:54:00.050> do<00:54:00.800> a<00:54:00.830> little<00:54:01.099> bit<00:54:01.280> of<00:54:01.310> wiping<00:54:01.970> this 00:54:02.410 --> 00:54:02.420 align:start position:0% it's to do a little bit of wiping this 00:54:02.420 --> 00:54:03.880 align:start position:0% it's to do a little bit of wiping this is<00:54:02.599> using<00:54:02.780> I<00:54:02.990> could<00:54:03.170> completely<00:54:03.560> this<00:54:03.740> red 00:54:03.880 --> 00:54:03.890 align:start position:0% is using I could completely this red 00:54:03.890 --> 00:54:06.609 align:start position:0% is using I could completely this red circle<00:54:04.070> but<00:54:05.000> it's<00:54:05.180> using<00:54:05.450> similar<00:54:05.900> videos<00:54:06.380> and 00:54:06.609 --> 00:54:06.619 align:start position:0% circle but it's using similar videos and 00:54:06.619 --> 00:54:09.460 align:start position:0% circle but it's using similar videos and similar<00:54:06.890> concepts<00:54:07.660> did<00:54:08.660> you<00:54:08.780> see<00:54:08.960> Phil<00:54:09.170> Diane 00:54:09.460 --> 00:54:09.470 align:start position:0% similar concepts did you see Phil Diane 00:54:09.470 --> 00:54:15.520 align:start position:0% similar concepts did you see Phil Diane stop<00:54:09.770> it<00:54:09.980> I<00:54:11.050> followed<00:54:13.990> his<00:54:14.990> research<00:54:15.380> is 00:54:15.520 --> 00:54:15.530 align:start position:0% stop it I followed his research is 00:54:15.530 --> 00:54:17.260 align:start position:0% stop it I followed his research is basically<00:54:15.890> how<00:54:16.099> can<00:54:16.280> you<00:54:16.340> prove<00:54:16.609> that<00:54:16.730> you<00:54:17.030> can 00:54:17.260 --> 00:54:17.270 align:start position:0% basically how can you prove that you can 00:54:17.270 --> 00:54:22.380 align:start position:0% basically how can you prove that you can likewise<00:54:17.900> nestle<00:54:19.390> this<00:54:20.390> is<00:54:20.540> a<00:54:20.570> very<00:54:20.869> similar 00:54:22.380 --> 00:54:22.390 align:start position:0% likewise nestle this is a very similar 00:54:22.390 --> 00:54:24.700 align:start position:0% likewise nestle this is a very similar collision<00:54:23.390> stuff<00:54:23.570> yeah<00:54:23.780> there's<00:54:24.440> a<00:54:24.500> bunch<00:54:24.590> of 00:54:24.700 --> 00:54:24.710 align:start position:0% collision stuff yeah there's a bunch of 00:54:24.710 --> 00:54:29.560 align:start position:0% collision stuff yeah there's a bunch of people<00:54:24.950> trying<00:54:25.040> to<00:54:25.160> do<00:54:25.250> this<00:54:28.359> thank<00:54:29.359> you<00:54:29.450> so 00:54:29.560 --> 00:54:29.570 align:start position:0% people trying to do this thank you so 00:54:29.570 --> 00:54:33.270 align:start position:0% people trying to do this thank you so much 00:54:33.270 --> 00:54:33.280 align:start position:0% 00:54:33.280 --> 00:54:40.210 align:start position:0% [Applause]