WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:16.670 align:start position:0% [Music] 00:00:16.670 --> 00:00:16.680 align:start position:0% 00:00:16.680 --> 00:00:18.769 align:start position:0% welcome<00:00:17.340> back 00:00:18.769 --> 00:00:18.779 align:start position:0% welcome back 00:00:18.779 --> 00:00:22.130 align:start position:0% welcome back um our<00:00:19.260> next<00:00:19.440> speaker<00:00:19.800> is<00:00:20.160> Chance<00:00:20.580> Hudson<00:00:21.420> and 00:00:22.130 --> 00:00:22.140 align:start position:0% um our next speaker is Chance Hudson and 00:00:22.140 --> 00:00:24.410 align:start position:0% um our next speaker is Chance Hudson and he'll<00:00:22.380> be<00:00:22.500> talking<00:00:22.740> about<00:00:23.039> how<00:00:23.699> to<00:00:23.820> build<00:00:24.060> an 00:00:24.410 --> 00:00:24.420 align:start position:0% he'll be talking about how to build an 00:00:24.420 --> 00:00:28.009 align:start position:0% he'll be talking about how to build an identity<00:00:24.900> ecosystem<00:00:25.500> on<00:00:26.039> unirp<00:00:26.760> and<00:00:27.420> unirp 00:00:28.009 --> 00:00:28.019 align:start position:0% identity ecosystem on unirp and unirp 00:00:28.019 --> 00:00:31.130 align:start position:0% identity ecosystem on unirp and unirp itself<00:00:28.500> is<00:00:29.220> an<00:00:29.760> anonymous<00:00:30.180> reputation<00:00:30.779> system 00:00:31.130 --> 00:00:31.140 align:start position:0% itself is an anonymous reputation system 00:00:31.140 --> 00:00:33.290 align:start position:0% itself is an anonymous reputation system so<00:00:32.040> chance 00:00:33.290 --> 00:00:33.300 align:start position:0% so chance 00:00:33.300 --> 00:00:38.990 align:start position:0% so chance thank<00:00:33.840> you 00:00:38.990 --> 00:00:39.000 align:start position:0% 00:00:39.000 --> 00:00:40.790 align:start position:0% all<00:00:39.540> right<00:00:39.600> so<00:00:39.840> thank<00:00:40.140> you<00:00:40.260> all<00:00:40.379> for<00:00:40.620> being 00:00:40.790 --> 00:00:40.800 align:start position:0% all right so thank you all for being 00:00:40.800 --> 00:00:41.810 align:start position:0% all right so thank you all for being here 00:00:41.810 --> 00:00:41.820 align:start position:0% here 00:00:41.820 --> 00:00:44.270 align:start position:0% here um<00:00:41.879> oops<00:00:42.960> I'm<00:00:43.320> excited<00:00:43.680> to<00:00:43.800> talk<00:00:43.920> to<00:00:44.040> you<00:00:44.160> guys 00:00:44.270 --> 00:00:44.280 align:start position:0% um oops I'm excited to talk to you guys 00:00:44.280 --> 00:00:46.310 align:start position:0% um oops I'm excited to talk to you guys today<00:00:44.460> about<00:00:44.820> a<00:00:45.120> protocol<00:00:45.420> I<00:00:45.600> work<00:00:45.780> on<00:00:45.899> called 00:00:46.310 --> 00:00:46.320 align:start position:0% today about a protocol I work on called 00:00:46.320 --> 00:00:47.750 align:start position:0% today about a protocol I work on called unirp 00:00:47.750 --> 00:00:47.760 align:start position:0% unirp 00:00:47.760 --> 00:00:49.790 align:start position:0% unirp so<00:00:48.180> before<00:00:48.360> we<00:00:48.600> get<00:00:48.719> into<00:00:48.840> it<00:00:49.079> this<00:00:49.379> is<00:00:49.500> a<00:00:49.680> quick 00:00:49.790 --> 00:00:49.800 align:start position:0% so before we get into it this is a quick 00:00:49.800 --> 00:00:51.410 align:start position:0% so before we get into it this is a quick road<00:00:49.980> map<00:00:50.219> of<00:00:50.520> how<00:00:50.760> this<00:00:50.879> presentation<00:00:51.239> is 00:00:51.410 --> 00:00:51.420 align:start position:0% road map of how this presentation is 00:00:51.420 --> 00:00:53.330 align:start position:0% road map of how this presentation is going<00:00:51.600> to<00:00:51.719> go<00:00:51.840> first<00:00:52.559> I'm<00:00:52.800> going<00:00:52.980> to<00:00:53.039> give<00:00:53.219> a 00:00:53.330 --> 00:00:53.340 align:start position:0% going to go first I'm going to give a 00:00:53.340 --> 00:00:55.069 align:start position:0% going to go first I'm going to give a semi-technical<00:00:54.059> overview<00:00:54.420> of<00:00:54.539> what<00:00:54.840> unit 00:00:55.069 --> 00:00:55.079 align:start position:0% semi-technical overview of what unit 00:00:55.079 --> 00:00:57.470 align:start position:0% semi-technical overview of what unit protocol<00:00:55.739> is<00:00:56.100> then<00:00:56.760> I'll<00:00:56.940> talk<00:00:57.059> a<00:00:57.239> little<00:00:57.300> bit 00:00:57.470 --> 00:00:57.480 align:start position:0% protocol is then I'll talk a little bit 00:00:57.480 --> 00:00:59.510 align:start position:0% protocol is then I'll talk a little bit about<00:00:57.780> improving<00:00:58.440> the<00:00:58.620> user<00:00:58.920> experience<00:00:59.280> of 00:00:59.510 --> 00:00:59.520 align:start position:0% about improving the user experience of 00:00:59.520 --> 00:01:01.430 align:start position:0% about improving the user experience of ZK<00:00:59.879> and<00:01:00.180> blockchain<00:01:00.539> applications<00:01:01.079> in 00:01:01.430 --> 00:01:01.440 align:start position:0% ZK and blockchain applications in 00:01:01.440 --> 00:01:03.049 align:start position:0% ZK and blockchain applications in general<00:01:01.559> and<00:01:02.340> then<00:01:02.460> I'll<00:01:02.579> talk<00:01:02.699> a<00:01:02.820> little<00:01:02.940> bit 00:01:03.049 --> 00:01:03.059 align:start position:0% general and then I'll talk a little bit 00:01:03.059 --> 00:01:04.789 align:start position:0% general and then I'll talk a little bit about<00:01:03.239> how<00:01:03.539> we<00:01:03.660> can<00:01:03.780> scale<00:01:04.080> ZK<00:01:04.440> on<00:01:04.680> the 00:01:04.789 --> 00:01:04.799 align:start position:0% about how we can scale ZK on the 00:01:04.799 --> 00:01:06.410 align:start position:0% about how we can scale ZK on the blockchain<00:01:05.159> and<00:01:05.580> sort<00:01:05.760> of<00:01:05.880> where<00:01:06.060> we're<00:01:06.240> at 00:01:06.410 --> 00:01:06.420 align:start position:0% blockchain and sort of where we're at 00:01:06.420 --> 00:01:09.469 align:start position:0% blockchain and sort of where we're at with<00:01:06.720> the<00:01:06.900> capacity<00:01:07.320> right<00:01:07.619> now 00:01:09.469 --> 00:01:09.479 align:start position:0% with the capacity right now 00:01:09.479 --> 00:01:12.109 align:start position:0% with the capacity right now right<00:01:09.960> so<00:01:10.200> let's<00:01:10.439> dive<00:01:10.680> into<00:01:10.799> it<00:01:11.040> uh<00:01:11.460> unirp<00:01:12.000> is 00:01:12.109 --> 00:01:12.119 align:start position:0% right so let's dive into it uh unirp is 00:01:12.119 --> 00:01:14.630 align:start position:0% right so let's dive into it uh unirp is short<00:01:12.299> for<00:01:12.540> Universal<00:01:13.439> reputation<00:01:13.920> and<00:01:14.520> you 00:01:14.630 --> 00:01:14.640 align:start position:0% short for Universal reputation and you 00:01:14.640 --> 00:01:16.250 align:start position:0% short for Universal reputation and you can<00:01:14.700> think<00:01:14.820> of<00:01:15.000> it<00:01:15.180> as<00:01:15.420> two<00:01:15.780> different<00:01:15.960> things 00:01:16.250 --> 00:01:16.260 align:start position:0% can think of it as two different things 00:01:16.260 --> 00:01:18.530 align:start position:0% can think of it as two different things first<00:01:17.100> it's<00:01:17.400> an<00:01:17.520> identity<00:01:17.939> system<00:01:18.119> that<00:01:18.420> gives 00:01:18.530 --> 00:01:18.540 align:start position:0% first it's an identity system that gives 00:01:18.540 --> 00:01:20.330 align:start position:0% first it's an identity system that gives you<00:01:18.659> anonymity<00:01:19.200> and<00:01:19.680> it<00:01:19.740> does<00:01:19.920> this<00:01:20.100> by 00:01:20.330 --> 00:01:20.340 align:start position:0% you anonymity and it does this by 00:01:20.340 --> 00:01:21.830 align:start position:0% you anonymity and it does this by creating<00:01:20.640> public<00:01:20.820> keys<00:01:21.299> that<00:01:21.420> change<00:01:21.600> over 00:01:21.830 --> 00:01:21.840 align:start position:0% creating public keys that change over 00:01:21.840 --> 00:01:23.990 align:start position:0% creating public keys that change over time<00:01:22.619> the<00:01:23.040> second<00:01:23.100> component<00:01:23.580> is<00:01:23.759> this 00:01:23.990 --> 00:01:24.000 align:start position:0% time the second component is this 00:01:24.000 --> 00:01:26.330 align:start position:0% time the second component is this attestation<00:01:24.600> system<00:01:25.020> uh<00:01:25.799> within<00:01:26.100> the<00:01:26.220> system 00:01:26.330 --> 00:01:26.340 align:start position:0% attestation system uh within the system 00:01:26.340 --> 00:01:27.950 align:start position:0% attestation system uh within the system we<00:01:26.640> have<00:01:26.700> a<00:01:26.820> testers<00:01:27.240> which<00:01:27.540> you<00:01:27.659> can<00:01:27.780> also 00:01:27.950 --> 00:01:27.960 align:start position:0% we have a testers which you can also 00:01:27.960 --> 00:01:29.570 align:start position:0% we have a testers which you can also think<00:01:28.080> of<00:01:28.259> as<00:01:28.380> applications<00:01:28.920> or<00:01:29.220> just<00:01:29.400> smart 00:01:29.570 --> 00:01:29.580 align:start position:0% think of as applications or just smart 00:01:29.580 --> 00:01:31.550 align:start position:0% think of as applications or just smart contracts<00:01:30.119> and<00:01:30.600> these<00:01:30.780> are<00:01:30.960> testers<00:01:31.259> give 00:01:31.550 --> 00:01:31.560 align:start position:0% contracts and these are testers give 00:01:31.560 --> 00:01:34.010 align:start position:0% contracts and these are testers give reputation<00:01:32.100> to<00:01:32.460> users<00:01:32.880> and<00:01:33.600> you<00:01:33.720> can<00:01:33.780> think<00:01:33.900> of 00:01:34.010 --> 00:01:34.020 align:start position:0% reputation to users and you can think of 00:01:34.020 --> 00:01:36.490 align:start position:0% reputation to users and you can think of an<00:01:34.200> attest<00:01:34.500> or<00:01:34.680> to<00:01:34.799> reputation<00:01:35.280> like<00:01:35.700> erc20 00:01:36.490 --> 00:01:36.500 align:start position:0% an attest or to reputation like erc20 00:01:36.500 --> 00:01:39.530 align:start position:0% an attest or to reputation like erc20 contracts<00:01:37.500> to<00:01:37.680> tokens<00:01:38.159> they<00:01:38.700> create<00:01:39.240> the 00:01:39.530 --> 00:01:39.540 align:start position:0% contracts to tokens they create the 00:01:39.540 --> 00:01:41.210 align:start position:0% contracts to tokens they create the system<00:01:39.720> to<00:01:39.960> find<00:01:40.200> how<00:01:40.439> the<00:01:40.619> reputation<00:01:40.979> is 00:01:41.210 --> 00:01:41.220 align:start position:0% system to find how the reputation is 00:01:41.220 --> 00:01:43.130 align:start position:0% system to find how the reputation is distributed<00:01:41.700> and<00:01:42.060> spent<00:01:42.420> and<00:01:42.600> destroyed<00:01:43.020> and 00:01:43.130 --> 00:01:43.140 align:start position:0% distributed and spent and destroyed and 00:01:43.140 --> 00:01:45.289 align:start position:0% distributed and spent and destroyed and everything<00:01:43.320> like<00:01:43.619> that 00:01:45.289 --> 00:01:45.299 align:start position:0% everything like that 00:01:45.299 --> 00:01:48.289 align:start position:0% everything like that and<00:01:45.900> so<00:01:46.140> we<00:01:46.560> Define<00:01:46.740> reputation<00:01:47.340> as<00:01:47.880> two 00:01:48.289 --> 00:01:48.299 align:start position:0% and so we Define reputation as two 00:01:48.299 --> 00:01:50.030 align:start position:0% and so we Define reputation as two different<00:01:48.479> integers<00:01:49.020> uh<00:01:49.560> positive<00:01:49.920> and 00:01:50.030 --> 00:01:50.040 align:start position:0% different integers uh positive and 00:01:50.040 --> 00:01:52.069 align:start position:0% different integers uh positive and negative<00:01:50.340> reputation<00:01:50.759> and<00:01:51.299> we<00:01:51.420> do<00:01:51.600> this<00:01:51.720> so<00:01:51.899> we 00:01:52.069 --> 00:01:52.079 align:start position:0% negative reputation and we do this so we 00:01:52.079 --> 00:01:53.690 align:start position:0% negative reputation and we do this so we can<00:01:52.140> represent<00:01:52.500> negative<00:01:52.920> reputation<00:01:53.399> like 00:01:53.690 --> 00:01:53.700 align:start position:0% can represent negative reputation like 00:01:53.700 --> 00:01:56.450 align:start position:0% can represent negative reputation like net<00:01:53.939> negative<00:01:54.299> reputation<00:01:54.780> in<00:01:55.500> CK<00:01:55.920> proofs<00:01:56.280> and 00:01:56.450 --> 00:01:56.460 align:start position:0% net negative reputation in CK proofs and 00:01:56.460 --> 00:01:57.830 align:start position:0% net negative reputation in CK proofs and in<00:01:56.640> smart<00:01:56.820> contracts<00:01:57.240> without<00:01:57.420> having<00:01:57.720> to 00:01:57.830 --> 00:01:57.840 align:start position:0% in smart contracts without having to 00:01:57.840 --> 00:01:59.870 align:start position:0% in smart contracts without having to deal<00:01:57.960> with<00:01:58.259> assigned<00:01:58.799> integers<00:01:59.159> or<00:01:59.460> wrapping 00:01:59.870 --> 00:01:59.880 align:start position:0% deal with assigned integers or wrapping 00:01:59.880 --> 00:02:01.370 align:start position:0% deal with assigned integers or wrapping around<00:02:00.000> unsigned<00:02:00.659> integers<00:02:01.079> or<00:02:01.259> anything 00:02:01.370 --> 00:02:01.380 align:start position:0% around unsigned integers or anything 00:02:01.380 --> 00:02:02.929 align:start position:0% around unsigned integers or anything like<00:02:01.560> that 00:02:02.929 --> 00:02:02.939 align:start position:0% like that 00:02:02.939 --> 00:02:04.670 align:start position:0% like that so<00:02:03.240> that's<00:02:03.360> one<00:02:03.600> component<00:02:03.960> of<00:02:04.259> the<00:02:04.380> user 00:02:04.670 --> 00:02:04.680 align:start position:0% so that's one component of the user 00:02:04.680 --> 00:02:06.950 align:start position:0% so that's one component of the user State<00:02:04.860> the<00:02:05.579> other<00:02:05.640> is<00:02:06.000> this<00:02:06.299> graffiti<00:02:06.780> value 00:02:06.950 --> 00:02:06.960 align:start position:0% State the other is this graffiti value 00:02:06.960 --> 00:02:10.249 align:start position:0% State the other is this graffiti value which<00:02:07.380> the<00:02:07.740> uh<00:02:07.860> the<00:02:08.220> a<00:02:08.280> tester<00:02:08.640> can<00:02:08.759> use<00:02:08.940> for<00:02:09.360> uh 00:02:10.249 --> 00:02:10.259 align:start position:0% which the uh the a tester can use for uh 00:02:10.259 --> 00:02:12.410 align:start position:0% which the uh the a tester can use for uh anything<00:02:10.619> in<00:02:11.039> anything<00:02:11.580> they<00:02:11.760> want<00:02:11.940> to<00:02:12.060> within 00:02:12.410 --> 00:02:12.420 align:start position:0% anything in anything they want to within 00:02:12.420 --> 00:02:14.449 align:start position:0% anything in anything they want to within the<00:02:12.540> application<00:02:12.959> and<00:02:13.560> this<00:02:13.680> is<00:02:13.800> just<00:02:13.980> 32 00:02:14.449 --> 00:02:14.459 align:start position:0% the application and this is just 32 00:02:14.459 --> 00:02:16.490 align:start position:0% the application and this is just 32 bytes<00:02:14.879> uh<00:02:15.420> and<00:02:15.660> yeah<00:02:15.780> the<00:02:15.959> assessor<00:02:16.260> can<00:02:16.379> use 00:02:16.490 --> 00:02:16.500 align:start position:0% bytes uh and yeah the assessor can use 00:02:16.500 --> 00:02:18.589 align:start position:0% bytes uh and yeah the assessor can use it<00:02:16.560> as<00:02:16.680> they<00:02:16.860> like<00:02:17.040> and<00:02:17.760> so<00:02:17.879> one<00:02:18.060> example<00:02:18.420> use 00:02:18.589 --> 00:02:18.599 align:start position:0% it as they like and so one example use 00:02:18.599 --> 00:02:20.930 align:start position:0% it as they like and so one example use case<00:02:18.840> of<00:02:19.020> this<00:02:19.200> is<00:02:19.560> and<00:02:19.860> a<00:02:20.040> tester<00:02:20.340> can<00:02:20.640> allow 00:02:20.930 --> 00:02:20.940 align:start position:0% case of this is and a tester can allow 00:02:20.940 --> 00:02:23.449 align:start position:0% case of this is and a tester can allow users<00:02:21.300> to<00:02:21.540> register<00:02:21.840> a<00:02:22.080> username<00:02:22.500> and<00:02:23.160> so<00:02:23.280> the 00:02:23.449 --> 00:02:23.459 align:start position:0% users to register a username and so the 00:02:23.459 --> 00:02:25.430 align:start position:0% users to register a username and so the user<00:02:23.760> requests<00:02:24.360> a<00:02:24.480> username<00:02:24.840> and<00:02:25.200> then<00:02:25.319> the 00:02:25.430 --> 00:02:25.440 align:start position:0% user requests a username and then the 00:02:25.440 --> 00:02:27.830 align:start position:0% user requests a username and then the tester<00:02:25.920> attests<00:02:26.520> giving<00:02:26.819> the<00:02:27.180> hash<00:02:27.360> of<00:02:27.660> the 00:02:27.830 --> 00:02:27.840 align:start position:0% tester attests giving the hash of the 00:02:27.840 --> 00:02:30.710 align:start position:0% tester attests giving the hash of the username<00:02:28.260> as<00:02:28.500> graffiti<00:02:29.040> to<00:02:29.160> the<00:02:29.340> user<00:02:30.000> now 00:02:30.710 --> 00:02:30.720 align:start position:0% username as graffiti to the user now 00:02:30.720 --> 00:02:33.050 align:start position:0% username as graffiti to the user now when<00:02:31.080> the<00:02:31.200> user<00:02:31.560> takes<00:02:31.860> an<00:02:32.040> action<00:02:32.280> or<00:02:32.580> makes<00:02:32.879> a 00:02:33.050 --> 00:02:33.060 align:start position:0% when the user takes an action or makes a 00:02:33.060 --> 00:02:34.670 align:start position:0% when the user takes an action or makes a proof<00:02:33.300> they<00:02:33.599> can<00:02:33.720> prove<00:02:34.020> the<00:02:34.140> pre-image<00:02:34.560> of 00:02:34.670 --> 00:02:34.680 align:start position:0% proof they can prove the pre-image of 00:02:34.680 --> 00:02:37.190 align:start position:0% proof they can prove the pre-image of the<00:02:34.800> graffiti<00:02:35.280> and<00:02:35.700> move<00:02:35.819> from<00:02:36.180> anonymity<00:02:36.720> to 00:02:37.190 --> 00:02:37.200 align:start position:0% the graffiti and move from anonymity to 00:02:37.200 --> 00:02:39.710 align:start position:0% the graffiti and move from anonymity to pseudonymity<00:02:37.920> so<00:02:38.700> that's<00:02:38.819> one<00:02:39.180> example<00:02:39.480> use 00:02:39.710 --> 00:02:39.720 align:start position:0% pseudonymity so that's one example use 00:02:39.720 --> 00:02:41.630 align:start position:0% pseudonymity so that's one example use case<00:02:39.900> that's<00:02:40.200> relatively<00:02:40.739> simple<00:02:40.920> a<00:02:41.519> more 00:02:41.630 --> 00:02:41.640 align:start position:0% case that's relatively simple a more 00:02:41.640 --> 00:02:43.250 align:start position:0% case that's relatively simple a more complex<00:02:41.879> example<00:02:42.300> would<00:02:42.540> be<00:02:42.660> storing<00:02:43.080> the 00:02:43.250 --> 00:02:43.260 align:start position:0% complex example would be storing the 00:02:43.260 --> 00:02:45.530 align:start position:0% complex example would be storing the state<00:02:43.440> route<00:02:43.620> of<00:02:43.860> a<00:02:43.980> Merkle<00:02:44.340> tree<00:02:44.519> inside<00:02:45.180> of 00:02:45.530 --> 00:02:45.540 align:start position:0% state route of a Merkle tree inside of 00:02:45.540 --> 00:02:47.809 align:start position:0% state route of a Merkle tree inside of this<00:02:45.840> graffiti<00:02:46.440> and<00:02:46.980> then<00:02:47.099> the<00:02:47.220> attester<00:02:47.700> can 00:02:47.809 --> 00:02:47.819 align:start position:0% this graffiti and then the attester can 00:02:47.819 --> 00:02:49.610 align:start position:0% this graffiti and then the attester can extend<00:02:48.180> the<00:02:48.360> ZK<00:02:48.720> proof<00:02:49.019> system<00:02:49.140> to<00:02:49.379> prove 00:02:49.610 --> 00:02:49.620 align:start position:0% extend the ZK proof system to prove 00:02:49.620 --> 00:02:51.650 align:start position:0% extend the ZK proof system to prove things<00:02:49.800> about<00:02:50.099> the<00:02:50.760> contents<00:02:51.180> of<00:02:51.300> that<00:02:51.480> tree 00:02:51.650 --> 00:02:51.660 align:start position:0% things about the contents of that tree 00:02:51.660 --> 00:02:53.330 align:start position:0% things about the contents of that tree that's<00:02:51.900> in<00:02:52.080> the<00:02:52.200> graffiti<00:02:52.620> so<00:02:53.040> for<00:02:53.160> example 00:02:53.330 --> 00:02:53.340 align:start position:0% that's in the graffiti so for example 00:02:53.340 --> 00:02:55.309 align:start position:0% that's in the graffiti so for example they<00:02:53.640> could<00:02:53.760> use<00:02:53.940> an<00:02:54.060> incremental<00:02:54.959> Merkle 00:02:55.309 --> 00:02:55.319 align:start position:0% they could use an incremental Merkle 00:02:55.319 --> 00:02:57.290 align:start position:0% they could use an incremental Merkle tree<00:02:55.440> to<00:02:55.980> give<00:02:56.160> achievements<00:02:56.700> to<00:02:56.819> the<00:02:56.940> user<00:02:57.180> or 00:02:57.290 --> 00:02:57.300 align:start position:0% tree to give achievements to the user or 00:02:57.300 --> 00:02:59.330 align:start position:0% tree to give achievements to the user or to<00:02:57.480> track<00:02:57.720> actions<00:02:58.379> the<00:02:58.560> user<00:02:58.860> has<00:02:58.980> taken 00:02:59.330 --> 00:02:59.340 align:start position:0% to track actions the user has taken 00:02:59.340 --> 00:03:01.790 align:start position:0% to track actions the user has taken anything<00:02:59.879> like<00:03:00.180> that<00:03:00.360> so<00:03:01.019> very<00:03:01.379> extensible 00:03:01.790 --> 00:03:01.800 align:start position:0% anything like that so very extensible 00:03:01.800 --> 00:03:03.170 align:start position:0% anything like that so very extensible system 00:03:03.170 --> 00:03:03.180 align:start position:0% system 00:03:03.180 --> 00:03:06.589 align:start position:0% system so<00:03:03.720> the<00:03:03.900> two<00:03:04.140> main<00:03:04.440> properties<00:03:04.920> of<00:03:05.459> unirp<00:03:06.239> are 00:03:06.589 --> 00:03:06.599 align:start position:0% so the two main properties of unirp are 00:03:06.599 --> 00:03:08.990 align:start position:0% so the two main properties of unirp are anonymity<00:03:07.200> and<00:03:07.440> non-confidentiality<00:03:08.400> that 00:03:08.990 --> 00:03:09.000 align:start position:0% anonymity and non-confidentiality that 00:03:09.000 --> 00:03:10.369 align:start position:0% anonymity and non-confidentiality that means<00:03:09.239> we<00:03:09.480> can<00:03:09.599> see<00:03:09.780> everything<00:03:10.080> that's 00:03:10.369 --> 00:03:10.379 align:start position:0% means we can see everything that's 00:03:10.379 --> 00:03:11.990 align:start position:0% means we can see everything that's happening<00:03:10.739> inside<00:03:10.980> of<00:03:11.280> the<00:03:11.400> system<00:03:11.519> how<00:03:11.879> much 00:03:11.990 --> 00:03:12.000 align:start position:0% happening inside of the system how much 00:03:12.000 --> 00:03:13.250 align:start position:0% happening inside of the system how much reputation<00:03:12.420> is<00:03:12.599> being<00:03:12.720> transferred<00:03:13.200> and 00:03:13.250 --> 00:03:13.260 align:start position:0% reputation is being transferred and 00:03:13.260 --> 00:03:15.050 align:start position:0% reputation is being transferred and whatnot<00:03:13.620> but<00:03:14.099> we<00:03:14.280> don't<00:03:14.400> know<00:03:14.580> who's<00:03:14.760> doing 00:03:15.050 --> 00:03:15.060 align:start position:0% whatnot but we don't know who's doing 00:03:15.060 --> 00:03:17.050 align:start position:0% whatnot but we don't know who's doing what 00:03:17.050 --> 00:03:17.060 align:start position:0% what 00:03:17.060 --> 00:03:19.490 align:start position:0% what so<00:03:18.060> let's<00:03:18.180> talk<00:03:18.420> a<00:03:18.599> little<00:03:18.720> bit<00:03:18.959> about<00:03:19.140> the 00:03:19.490 --> 00:03:19.500 align:start position:0% so let's talk a little bit about the 00:03:19.500 --> 00:03:22.070 align:start position:0% so let's talk a little bit about the unirap<00:03:19.980> identity<00:03:20.459> system<00:03:20.700> we<00:03:21.540> build<00:03:21.720> on<00:03:21.959> top 00:03:22.070 --> 00:03:22.080 align:start position:0% unirap identity system we build on top 00:03:22.080 --> 00:03:23.809 align:start position:0% unirap identity system we build on top of<00:03:22.200> a<00:03:22.319> system<00:03:22.500> called<00:03:22.739> semaphore<00:03:23.340> which<00:03:23.700> is 00:03:23.809 --> 00:03:23.819 align:start position:0% of a system called semaphore which is 00:03:23.819 --> 00:03:25.430 align:start position:0% of a system called semaphore which is also<00:03:24.060> developed<00:03:24.420> by<00:03:24.780> the<00:03:24.959> privacy<00:03:25.319> and 00:03:25.430 --> 00:03:25.440 align:start position:0% also developed by the privacy and 00:03:25.440 --> 00:03:26.930 align:start position:0% also developed by the privacy and scalability<00:03:25.980> team 00:03:26.930 --> 00:03:26.940 align:start position:0% scalability team 00:03:26.940 --> 00:03:28.729 align:start position:0% scalability team uh<00:03:27.360> and<00:03:27.480> with<00:03:27.659> some<00:03:27.840> before<00:03:28.019> we<00:03:28.440> have<00:03:28.560> this 00:03:28.729 --> 00:03:28.739 align:start position:0% uh and with some before we have this 00:03:28.739 --> 00:03:30.229 align:start position:0% uh and with some before we have this public<00:03:28.920> private<00:03:29.280> Key<00:03:29.400> System<00:03:29.640> that's<00:03:30.060> the 00:03:30.229 --> 00:03:30.239 align:start position:0% public private Key System that's the 00:03:30.239 --> 00:03:32.390 align:start position:0% public private Key System that's the most<00:03:30.360> simple<00:03:30.540> explanation<00:03:31.140> it<00:03:32.040> has<00:03:32.220> two 00:03:32.390 --> 00:03:32.400 align:start position:0% most simple explanation it has two 00:03:32.400 --> 00:03:34.550 align:start position:0% most simple explanation it has two Secrets<00:03:32.760> a<00:03:32.940> chapter<00:03:33.120> and<00:03:33.420> a<00:03:33.540> nullifier<00:03:33.959> and<00:03:34.440> we 00:03:34.550 --> 00:03:34.560 align:start position:0% Secrets a chapter and a nullifier and we 00:03:34.560 --> 00:03:36.649 align:start position:0% Secrets a chapter and a nullifier and we defined<00:03:34.920> a<00:03:35.040> public<00:03:35.159> key<00:03:35.400> as<00:03:35.760> the<00:03:36.060> hash<00:03:36.239> of<00:03:36.480> the 00:03:36.649 --> 00:03:36.659 align:start position:0% defined a public key as the hash of the 00:03:36.659 --> 00:03:38.990 align:start position:0% defined a public key as the hash of the hash<00:03:36.900> of<00:03:37.200> those<00:03:37.379> two<00:03:37.560> secrets<00:03:38.040> we<00:03:38.700> also<00:03:38.879> call 00:03:38.990 --> 00:03:39.000 align:start position:0% hash of those two secrets we also call 00:03:39.000 --> 00:03:40.850 align:start position:0% hash of those two secrets we also call this<00:03:39.180> an<00:03:39.420> identity<00:03:39.780> commitment<00:03:40.140> in<00:03:40.379> semaphore 00:03:40.850 --> 00:03:40.860 align:start position:0% this an identity commitment in semaphore 00:03:40.860 --> 00:03:43.430 align:start position:0% this an identity commitment in semaphore talk<00:03:41.099> and<00:03:42.000> we<00:03:42.120> use<00:03:42.299> the<00:03:42.659> Poseidon<00:03:43.200> hash 00:03:43.430 --> 00:03:43.440 align:start position:0% talk and we use the Poseidon hash 00:03:43.440 --> 00:03:45.470 align:start position:0% talk and we use the Poseidon hash function<00:03:43.799> to<00:03:44.220> calculate<00:03:44.640> these<00:03:44.879> values<00:03:45.239> which 00:03:45.470 --> 00:03:45.480 align:start position:0% function to calculate these values which 00:03:45.480 --> 00:03:48.110 align:start position:0% function to calculate these values which makes<00:03:45.659> it<00:03:45.959> a<00:03:46.319> ZK<00:03:46.560> friendly<00:03:46.980> protocol<00:03:47.340> and<00:03:48.060> that 00:03:48.110 --> 00:03:48.120 align:start position:0% makes it a ZK friendly protocol and that 00:03:48.120 --> 00:03:49.430 align:start position:0% makes it a ZK friendly protocol and that means<00:03:48.360> that<00:03:48.420> you<00:03:48.599> can<00:03:48.720> extend<00:03:49.019> it<00:03:49.140> to<00:03:49.260> do 00:03:49.430 --> 00:03:49.440 align:start position:0% means that you can extend it to do 00:03:49.440 --> 00:03:51.170 align:start position:0% means that you can extend it to do arbitrary<00:03:49.920> things<00:03:50.099> so<00:03:50.519> so<00:03:50.640> in<00:03:50.819> this<00:03:50.940> example 00:03:51.170 --> 00:03:51.180 align:start position:0% arbitrary things so so in this example 00:03:51.180 --> 00:03:53.030 align:start position:0% arbitrary things so so in this example we<00:03:51.480> have<00:03:51.599> just<00:03:51.900> a<00:03:52.140> public<00:03:52.260> private<00:03:52.680> key<00:03:52.799> system 00:03:53.030 --> 00:03:53.040 align:start position:0% we have just a public private key system 00:03:53.040 --> 00:03:55.009 align:start position:0% we have just a public private key system which<00:03:53.400> isn't<00:03:53.700> particularly<00:03:54.060> useful<00:03:54.420> but 00:03:55.009 --> 00:03:55.019 align:start position:0% which isn't particularly useful but 00:03:55.019 --> 00:03:57.110 align:start position:0% which isn't particularly useful but using<00:03:55.319> a<00:03:55.440> ZK<00:03:55.739> proof<00:03:56.040> you<00:03:56.220> could<00:03:56.340> extend<00:03:56.640> it<00:03:56.760> to 00:03:57.110 --> 00:03:57.120 align:start position:0% using a ZK proof you could extend it to 00:03:57.120 --> 00:03:59.210 align:start position:0% using a ZK proof you could extend it to do<00:03:57.299> signatures<00:03:57.840> for<00:03:58.080> example<00:03:58.319> by<00:03:58.799> writing<00:03:59.159> a 00:03:59.210 --> 00:03:59.220 align:start position:0% do signatures for example by writing a 00:03:59.220 --> 00:04:01.490 align:start position:0% do signatures for example by writing a proof<00:03:59.459> that<00:03:59.640> proves<00:04:00.120> the<00:04:00.480> secret<00:04:00.659> values<00:04:01.140> as 00:04:01.490 --> 00:04:01.500 align:start position:0% proof that proves the secret values as 00:04:01.500 --> 00:04:03.770 align:start position:0% proof that proves the secret values as well<00:04:01.680> as<00:04:01.799> the<00:04:02.099> hash<00:04:02.340> of<00:04:02.700> some<00:04:03.180> data<00:04:03.599> that<00:04:03.659> you 00:04:03.770 --> 00:04:03.780 align:start position:0% well as the hash of some data that you 00:04:03.780 --> 00:04:06.229 align:start position:0% well as the hash of some data that you want<00:04:03.900> to<00:04:04.019> assign<00:04:04.739> uh<00:04:05.280> yes<00:04:05.400> you<00:04:05.640> can<00:04:05.760> extend<00:04:05.940> ZK 00:04:06.229 --> 00:04:06.239 align:start position:0% want to assign uh yes you can extend ZK 00:04:06.239 --> 00:04:08.149 align:start position:0% want to assign uh yes you can extend ZK proofs<00:04:06.599> in<00:04:06.720> our<00:04:06.840> in<00:04:07.200> arbitrary<00:04:07.680> ways<00:04:08.040> like 00:04:08.149 --> 00:04:08.159 align:start position:0% proofs in our in arbitrary ways like 00:04:08.159 --> 00:04:09.410 align:start position:0% proofs in our in arbitrary ways like this 00:04:09.410 --> 00:04:09.420 align:start position:0% this 00:04:09.420 --> 00:04:11.449 align:start position:0% this another<00:04:09.900> way<00:04:10.140> you<00:04:10.260> can<00:04:10.379> extend<00:04:10.620> it<00:04:10.799> is<00:04:11.099> by 00:04:11.449 --> 00:04:11.459 align:start position:0% another way you can extend it is by 00:04:11.459 --> 00:04:13.910 align:start position:0% another way you can extend it is by building<00:04:11.760> something<00:04:12.000> like<00:04:12.239> unirap<00:04:12.780> so<00:04:13.560> we 00:04:13.910 --> 00:04:13.920 align:start position:0% building something like unirap so we 00:04:13.920 --> 00:04:15.170 align:start position:0% building something like unirap so we have<00:04:14.040> these<00:04:14.220> public<00:04:14.340> keys<00:04:14.700> that<00:04:14.819> change<00:04:14.939> over 00:04:15.170 --> 00:04:15.180 align:start position:0% have these public keys that change over 00:04:15.180 --> 00:04:17.330 align:start position:0% have these public keys that change over time<00:04:15.420> and<00:04:15.900> we<00:04:16.019> call<00:04:16.199> these<00:04:16.440> epoc<00:04:16.799> keys<00:04:17.160> because 00:04:17.330 --> 00:04:17.340 align:start position:0% time and we call these epoc keys because 00:04:17.340 --> 00:04:19.189 align:start position:0% time and we call these epoc keys because they<00:04:17.639> are<00:04:17.820> valid<00:04:18.060> for<00:04:18.299> the<00:04:18.600> length<00:04:18.840> of<00:04:18.959> one 00:04:19.189 --> 00:04:19.199 align:start position:0% they are valid for the length of one 00:04:19.199 --> 00:04:21.469 align:start position:0% they are valid for the length of one Epoch<00:04:19.799> uh<00:04:20.400> and<00:04:20.579> this<00:04:20.699> is<00:04:20.820> some<00:04:20.940> amount<00:04:21.180> of<00:04:21.359> time 00:04:21.469 --> 00:04:21.479 align:start position:0% Epoch uh and this is some amount of time 00:04:21.479 --> 00:04:23.510 align:start position:0% Epoch uh and this is some amount of time that<00:04:21.780> is<00:04:21.900> set<00:04:22.199> by<00:04:22.440> the<00:04:22.620> tester<00:04:23.100> in<00:04:23.340> question 00:04:23.510 --> 00:04:23.520 align:start position:0% that is set by the tester in question 00:04:23.520 --> 00:04:26.150 align:start position:0% that is set by the tester in question and<00:04:24.240> so<00:04:24.360> the<00:04:24.479> epoch<00:04:24.900> key<00:04:25.020> is<00:04:25.259> the<00:04:25.560> hash<00:04:25.680> of<00:04:26.040> the 00:04:26.150 --> 00:04:26.160 align:start position:0% and so the epoch key is the hash of the 00:04:26.160 --> 00:04:28.490 align:start position:0% and so the epoch key is the hash of the nullifier<00:04:26.699> the<00:04:27.000> tester<00:04:27.300> ID<00:04:27.419> Epoch<00:04:28.139> and<00:04:28.199> Knots 00:04:28.490 --> 00:04:28.500 align:start position:0% nullifier the tester ID Epoch and Knots 00:04:28.500 --> 00:04:30.290 align:start position:0% nullifier the tester ID Epoch and Knots and<00:04:28.919> so<00:04:29.040> as<00:04:29.160> you<00:04:29.280> can<00:04:29.400> see<00:04:29.460> because<00:04:29.699> the<00:04:29.880> epoch 00:04:30.290 --> 00:04:30.300 align:start position:0% and so as you can see because the epoch 00:04:30.300 --> 00:04:32.210 align:start position:0% and so as you can see because the epoch is<00:04:30.360> part<00:04:30.479> of<00:04:30.540> the<00:04:30.600> hash<00:04:30.840> it<00:04:31.139> changes<00:04:31.500> uh<00:04:32.040> every 00:04:32.210 --> 00:04:32.220 align:start position:0% is part of the hash it changes uh every 00:04:32.220 --> 00:04:34.550 align:start position:0% is part of the hash it changes uh every epoch<00:04:33.060> we<00:04:33.540> also<00:04:33.720> have<00:04:33.900> this<00:04:34.080> nonce<00:04:34.380> value 00:04:34.550 --> 00:04:34.560 align:start position:0% epoch we also have this nonce value 00:04:34.560 --> 00:04:37.490 align:start position:0% epoch we also have this nonce value which<00:04:35.160> is<00:04:35.340> a<00:04:35.820> value<00:04:36.180> between<00:04:36.419> like<00:04:36.720> one<00:04:36.900> and<00:04:37.139> or 00:04:37.490 --> 00:04:37.500 align:start position:0% which is a value between like one and or 00:04:37.500 --> 00:04:39.469 align:start position:0% which is a value between like one and or zero<00:04:37.800> and<00:04:37.860> two<00:04:38.040> by<00:04:38.280> default<00:04:38.580> and<00:04:39.060> it<00:04:39.180> allows<00:04:39.419> us 00:04:39.469 --> 00:04:39.479 align:start position:0% zero and two by default and it allows us 00:04:39.479 --> 00:04:41.390 align:start position:0% zero and two by default and it allows us to<00:04:39.660> give<00:04:39.780> the<00:04:39.960> user<00:04:40.199> multiple<00:04:40.620> Epoch<00:04:41.100> keys<00:04:41.340> for 00:04:41.390 --> 00:04:41.400 align:start position:0% to give the user multiple Epoch keys for 00:04:41.400 --> 00:04:43.249 align:start position:0% to give the user multiple Epoch keys for a<00:04:41.520> single<00:04:41.699> Epoch<00:04:42.180> so<00:04:42.540> if<00:04:42.720> your<00:04:42.840> user<00:04:43.020> wants<00:04:43.199> to 00:04:43.249 --> 00:04:43.259 align:start position:0% a single Epoch so if your user wants to 00:04:43.259 --> 00:04:44.629 align:start position:0% a single Epoch so if your user wants to commit<00:04:43.500> an<00:04:43.620> action<00:04:43.860> and<00:04:44.160> then<00:04:44.220> wants<00:04:44.460> to<00:04:44.520> give 00:04:44.629 --> 00:04:44.639 align:start position:0% commit an action and then wants to give 00:04:44.639 --> 00:04:45.890 align:start position:0% commit an action and then wants to give it<00:04:44.820> another<00:04:44.880> action<00:04:45.240> but<00:04:45.479> doesn't<00:04:45.600> want<00:04:45.840> to 00:04:45.890 --> 00:04:45.900 align:start position:0% it another action but doesn't want to 00:04:45.900 --> 00:04:47.810 align:start position:0% it another action but doesn't want to link<00:04:46.020> their<00:04:46.199> identity<00:04:46.620> between<00:04:46.919> uh<00:04:47.520> the<00:04:47.759> two 00:04:47.810 --> 00:04:47.820 align:start position:0% link their identity between uh the two 00:04:47.820 --> 00:04:50.390 align:start position:0% link their identity between uh the two keys<00:04:48.180> they<00:04:48.479> can<00:04:48.600> use<00:04:48.720> different<00:04:48.960> epochies<00:04:49.740> uh 00:04:50.390 --> 00:04:50.400 align:start position:0% keys they can use different epochies uh 00:04:50.400 --> 00:04:51.890 align:start position:0% keys they can use different epochies uh and<00:04:50.580> still<00:04:50.759> be<00:04:50.940> able<00:04:51.120> to<00:04:51.240> prove<00:04:51.660> the<00:04:51.780> same 00:04:51.890 --> 00:04:51.900 align:start position:0% and still be able to prove the same 00:04:51.900 --> 00:04:53.930 align:start position:0% and still be able to prove the same amount<00:04:52.020> of<00:04:52.199> reputation<00:04:52.560> and<00:04:52.740> whatnot<00:04:53.460> and 00:04:53.930 --> 00:04:53.940 align:start position:0% amount of reputation and whatnot and 00:04:53.940 --> 00:04:55.610 align:start position:0% amount of reputation and whatnot and just<00:04:54.120> like<00:04:54.240> some<00:04:54.419> of<00:04:54.540> our<00:04:54.720> this<00:04:55.020> system<00:04:55.139> is<00:04:55.320> ZK 00:04:55.610 --> 00:04:55.620 align:start position:0% just like some of our this system is ZK 00:04:55.620 --> 00:04:58.129 align:start position:0% just like some of our this system is ZK friendly<00:04:55.979> and<00:04:56.280> therefore<00:04:56.520> extensible<00:04:57.180> so<00:04:57.840> if 00:04:58.129 --> 00:04:58.139 align:start position:0% friendly and therefore extensible so if 00:04:58.139 --> 00:04:59.210 align:start position:0% friendly and therefore extensible so if you<00:04:58.199> want<00:04:58.320> to<00:04:58.440> make<00:04:58.560> a<00:04:58.680> signature<00:04:59.040> system 00:04:59.210 --> 00:04:59.220 align:start position:0% you want to make a signature system 00:04:59.220 --> 00:05:01.430 align:start position:0% you want to make a signature system using<00:04:59.639> these<00:04:59.820> epochies<00:05:00.419> you<00:05:00.840> would<00:05:01.020> use<00:05:01.199> the 00:05:01.430 --> 00:05:01.440 align:start position:0% using these epochies you would use the 00:05:01.440 --> 00:05:03.950 align:start position:0% using these epochies you would use the exact<00:05:01.740> same<00:05:01.919> approach<00:05:02.400> where<00:05:03.000> you<00:05:03.360> prove<00:05:03.720> the 00:05:03.950 --> 00:05:03.960 align:start position:0% exact same approach where you prove the 00:05:03.960 --> 00:05:05.990 align:start position:0% exact same approach where you prove the proof<00:05:04.740> control<00:05:04.919> of<00:05:05.100> the<00:05:05.220> nullifier<00:05:05.639> and<00:05:05.880> the 00:05:05.990 --> 00:05:06.000 align:start position:0% proof control of the nullifier and the 00:05:06.000 --> 00:05:07.610 align:start position:0% proof control of the nullifier and the public<00:05:06.120> signals<00:05:06.600> and<00:05:07.020> then<00:05:07.080> you<00:05:07.259> pass<00:05:07.440> in 00:05:07.610 --> 00:05:07.620 align:start position:0% public signals and then you pass in 00:05:07.620 --> 00:05:09.230 align:start position:0% public signals and then you pass in whatever<00:05:07.979> you<00:05:08.280> want<00:05:08.400> to<00:05:08.520> hash<00:05:08.699> and<00:05:08.940> it<00:05:09.060> all 00:05:09.230 --> 00:05:09.240 align:start position:0% whatever you want to hash and it all 00:05:09.240 --> 00:05:11.990 align:start position:0% whatever you want to hash and it all gets<00:05:09.540> output 00:05:11.990 --> 00:05:12.000 align:start position:0% 00:05:12.000 --> 00:05:13.490 align:start position:0% yeah<00:05:12.240> so<00:05:12.600> now<00:05:12.720> I<00:05:12.840> want<00:05:12.960> to<00:05:13.080> talk<00:05:13.199> a<00:05:13.259> little<00:05:13.320> bit 00:05:13.490 --> 00:05:13.500 align:start position:0% yeah so now I want to talk a little bit 00:05:13.500 --> 00:05:14.870 align:start position:0% yeah so now I want to talk a little bit about<00:05:13.680> data<00:05:14.220> structures<00:05:14.460> that<00:05:14.580> we<00:05:14.699> use<00:05:14.820> in 00:05:14.870 --> 00:05:14.880 align:start position:0% about data structures that we use in 00:05:14.880 --> 00:05:16.430 align:start position:0% about data structures that we use in unit<00:05:15.000> so<00:05:15.600> we<00:05:15.720> have<00:05:15.840> like<00:05:15.960> this<00:05:16.080> identity 00:05:16.430 --> 00:05:16.440 align:start position:0% unit so we have like this identity 00:05:16.440 --> 00:05:18.290 align:start position:0% unit so we have like this identity system<00:05:16.680> but<00:05:16.979> how<00:05:17.160> do<00:05:17.280> we<00:05:17.400> assign<00:05:17.759> reputation 00:05:18.290 --> 00:05:18.300 align:start position:0% system but how do we assign reputation 00:05:18.300 --> 00:05:20.330 align:start position:0% system but how do we assign reputation and<00:05:18.540> graffiti<00:05:19.020> to<00:05:19.259> users<00:05:19.620> in<00:05:19.800> the<00:05:19.919> system<00:05:20.040> and 00:05:20.330 --> 00:05:20.340 align:start position:0% and graffiti to users in the system and 00:05:20.340 --> 00:05:22.790 align:start position:0% and graffiti to users in the system and then<00:05:20.460> like<00:05:20.699> continue<00:05:21.000> to<00:05:21.300> prove<00:05:21.600> it 00:05:22.790 --> 00:05:22.800 align:start position:0% then like continue to prove it 00:05:22.800 --> 00:05:25.010 align:start position:0% then like continue to prove it so<00:05:23.220> we<00:05:23.400> really<00:05:23.580> have<00:05:23.759> two<00:05:23.940> structures 00:05:25.010 --> 00:05:25.020 align:start position:0% so we really have two structures 00:05:25.020 --> 00:05:27.110 align:start position:0% so we really have two structures um<00:05:25.080> we<00:05:25.380> have<00:05:25.500> this<00:05:25.680> state<00:05:25.979> tree<00:05:26.220> first<00:05:26.460> which 00:05:27.110 --> 00:05:27.120 align:start position:0% um we have this state tree first which 00:05:27.120 --> 00:05:29.210 align:start position:0% um we have this state tree first which controls<00:05:27.660> uh<00:05:28.139> or<00:05:28.259> measures<00:05:28.620> whether<00:05:28.860> or<00:05:28.979> not<00:05:29.039> a 00:05:29.210 --> 00:05:29.220 align:start position:0% controls uh or measures whether or not a 00:05:29.220 --> 00:05:31.010 align:start position:0% controls uh or measures whether or not a user<00:05:29.460> is<00:05:29.580> a<00:05:29.759> member<00:05:30.000> of<00:05:30.120> the<00:05:30.240> current<00:05:30.360> Epoch 00:05:31.010 --> 00:05:31.020 align:start position:0% user is a member of the current Epoch 00:05:31.020 --> 00:05:32.570 align:start position:0% user is a member of the current Epoch and<00:05:31.380> as<00:05:31.560> you<00:05:31.680> can<00:05:31.740> see<00:05:31.860> it's<00:05:32.039> an<00:05:32.160> incremental 00:05:32.570 --> 00:05:32.580 align:start position:0% and as you can see it's an incremental 00:05:32.580 --> 00:05:34.010 align:start position:0% and as you can see it's an incremental Merkel<00:05:32.880> tree<00:05:33.000> that<00:05:33.240> we<00:05:33.300> store<00:05:33.479> completely<00:05:33.840> on 00:05:34.010 --> 00:05:34.020 align:start position:0% Merkel tree that we store completely on 00:05:34.020 --> 00:05:36.590 align:start position:0% Merkel tree that we store completely on chain<00:05:34.220> and<00:05:35.220> the<00:05:35.520> the<00:05:35.639> leaves<00:05:36.000> themselves<00:05:36.360> are 00:05:36.590 --> 00:05:36.600 align:start position:0% chain and the the leaves themselves are 00:05:36.600 --> 00:05:38.210 align:start position:0% chain and the the leaves themselves are the<00:05:36.720> hash<00:05:36.900> of<00:05:37.259> this<00:05:37.560> private<00:05:37.919> identity 00:05:38.210 --> 00:05:38.220 align:start position:0% the hash of this private identity 00:05:38.220 --> 00:05:40.670 align:start position:0% the hash of this private identity nullifier<00:05:38.820> the<00:05:39.539> tester<00:05:39.900> in<00:05:40.020> the<00:05:40.080> epoch<00:05:40.500> and 00:05:40.670 --> 00:05:40.680 align:start position:0% nullifier the tester in the epoch and 00:05:40.680 --> 00:05:42.650 align:start position:0% nullifier the tester in the epoch and then<00:05:40.740> the<00:05:41.039> reputation<00:05:41.400> the<00:05:41.699> user<00:05:42.000> has<00:05:42.240> at<00:05:42.539> the 00:05:42.650 --> 00:05:42.660 align:start position:0% then the reputation the user has at the 00:05:42.660 --> 00:05:44.629 align:start position:0% then the reputation the user has at the start<00:05:42.840> of<00:05:43.080> the<00:05:43.199> epoch<00:05:43.680> so<00:05:44.039> this<00:05:44.220> tree<00:05:44.400> control 00:05:44.629 --> 00:05:44.639 align:start position:0% start of the epoch so this tree control 00:05:44.639 --> 00:05:46.850 align:start position:0% start of the epoch so this tree control or<00:05:45.060> this<00:05:45.240> tree<00:05:45.360> has<00:05:45.660> leaves<00:05:46.020> that<00:05:46.199> a<00:05:46.620> user 00:05:46.850 --> 00:05:46.860 align:start position:0% or this tree has leaves that a user 00:05:46.860 --> 00:05:48.590 align:start position:0% or this tree has leaves that a user inserts<00:05:47.160> into<00:05:47.280> when<00:05:47.639> they<00:05:47.880> join<00:05:48.360> the<00:05:48.479> current 00:05:48.590 --> 00:05:48.600 align:start position:0% inserts into when they join the current 00:05:48.600 --> 00:05:50.749 align:start position:0% inserts into when they join the current Epoch<00:05:49.199> so<00:05:49.620> for<00:05:49.740> example<00:05:49.919> when<00:05:50.100> a<00:05:50.220> user<00:05:50.460> signs 00:05:50.749 --> 00:05:50.759 align:start position:0% Epoch so for example when a user signs 00:05:50.759 --> 00:05:53.510 align:start position:0% Epoch so for example when a user signs up<00:05:50.880> we<00:05:51.180> insert<00:05:51.539> a<00:05:51.720> leaf<00:05:52.020> or<00:05:52.440> the<00:05:52.740> the<00:05:53.220> user 00:05:53.510 --> 00:05:53.520 align:start position:0% up we insert a leaf or the the user 00:05:53.520 --> 00:05:55.430 align:start position:0% up we insert a leaf or the the user makes<00:05:53.580> a<00:05:53.759> ZK<00:05:54.000> proof<00:05:54.360> and<00:05:54.479> then<00:05:54.660> creates<00:05:55.020> a<00:05:55.139> leaf 00:05:55.430 --> 00:05:55.440 align:start position:0% makes a ZK proof and then creates a leaf 00:05:55.440 --> 00:05:56.870 align:start position:0% makes a ZK proof and then creates a leaf with<00:05:55.680> zero<00:05:56.100> positive<00:05:56.400> and<00:05:56.580> negative 00:05:56.870 --> 00:05:56.880 align:start position:0% with zero positive and negative 00:05:56.880 --> 00:05:58.310 align:start position:0% with zero positive and negative reputation<00:05:57.300> because<00:05:57.600> they're<00:05:57.840> just<00:05:58.020> joining 00:05:58.310 --> 00:05:58.320 align:start position:0% reputation because they're just joining 00:05:58.320 --> 00:06:00.650 align:start position:0% reputation because they're just joining the<00:05:58.500> system<00:05:58.620> so<00:05:58.800> they<00:05:58.979> start<00:05:59.160> with<00:05:59.280> zero 00:06:00.650 --> 00:06:00.660 align:start position:0% the system so they start with zero 00:06:00.660 --> 00:06:02.510 align:start position:0% the system so they start with zero the<00:06:01.139> other<00:06:01.259> structure<00:06:01.620> we<00:06:01.740> have<00:06:01.919> is<00:06:02.220> what<00:06:02.400> we 00:06:02.510 --> 00:06:02.520 align:start position:0% the other structure we have is what we 00:06:02.520 --> 00:06:04.969 align:start position:0% the other structure we have is what we call<00:06:02.639> an<00:06:02.759> epoxy<00:06:03.360> so<00:06:04.020> the<00:06:04.139> state<00:06:04.320> tree<00:06:04.500> tracks 00:06:04.969 --> 00:06:04.979 align:start position:0% call an epoxy so the state tree tracks 00:06:04.979 --> 00:06:07.189 align:start position:0% call an epoxy so the state tree tracks the<00:06:05.220> starting<00:06:05.400> ballots<00:06:05.880> for<00:06:06.479> the<00:06:06.539> epoch<00:06:07.020> and 00:06:07.189 --> 00:06:07.199 align:start position:0% the starting ballots for the epoch and 00:06:07.199 --> 00:06:09.290 align:start position:0% the starting ballots for the epoch and the<00:06:07.320> epoch<00:06:07.740> tree<00:06:07.919> uh<00:06:08.400> tracks<00:06:08.820> the<00:06:08.940> amount<00:06:09.180> of 00:06:09.290 --> 00:06:09.300 align:start position:0% the epoch tree uh tracks the amount of 00:06:09.300 --> 00:06:11.390 align:start position:0% the epoch tree uh tracks the amount of reputation<00:06:09.840> that<00:06:10.139> was<00:06:10.259> received<00:06:10.860> during<00:06:11.160> the 00:06:11.390 --> 00:06:11.400 align:start position:0% reputation that was received during the 00:06:11.400 --> 00:06:13.969 align:start position:0% reputation that was received during the epoch<00:06:12.360> and<00:06:12.780> as<00:06:12.900> you<00:06:13.020> can<00:06:13.080> see<00:06:13.199> it's<00:06:13.500> a<00:06:13.680> sparse 00:06:13.969 --> 00:06:13.979 align:start position:0% epoch and as you can see it's a sparse 00:06:13.979 --> 00:06:16.370 align:start position:0% epoch and as you can see it's a sparse Miracle<00:06:14.220> tree<00:06:14.460> and<00:06:15.300> we<00:06:15.419> store<00:06:15.660> only<00:06:15.960> the<00:06:16.139> root 00:06:16.370 --> 00:06:16.380 align:start position:0% Miracle tree and we store only the root 00:06:16.380 --> 00:06:18.350 align:start position:0% Miracle tree and we store only the root of<00:06:16.500> this<00:06:16.680> tree<00:06:16.860> on<00:06:17.100> chain<00:06:17.340> and<00:06:17.699> we<00:06:17.820> use<00:06:17.940> ZK 00:06:18.350 --> 00:06:18.360 align:start position:0% of this tree on chain and we use ZK 00:06:18.360 --> 00:06:20.570 align:start position:0% of this tree on chain and we use ZK proof's<00:06:18.780> off<00:06:18.960> chain<00:06:19.199> to<00:06:19.740> insert<00:06:20.039> and<00:06:20.280> update 00:06:20.570 --> 00:06:20.580 align:start position:0% proof's off chain to insert and update 00:06:20.580 --> 00:06:22.550 align:start position:0% proof's off chain to insert and update leaves<00:06:21.000> in<00:06:21.479> the<00:06:21.660> street<00:06:21.840> and<00:06:22.139> then<00:06:22.259> we<00:06:22.440> just 00:06:22.550 --> 00:06:22.560 align:start position:0% leaves in the street and then we just 00:06:22.560 --> 00:06:24.830 align:start position:0% leaves in the street and then we just post<00:06:22.919> the<00:06:23.220> new<00:06:23.340> route<00:06:23.580> along<00:06:24.240> with<00:06:24.479> the<00:06:24.600> ZK 00:06:24.830 --> 00:06:24.840 align:start position:0% post the new route along with the ZK 00:06:24.840 --> 00:06:26.570 align:start position:0% post the new route along with the ZK proof<00:06:25.139> to<00:06:25.319> the<00:06:25.500> chain 00:06:26.570 --> 00:06:26.580 align:start position:0% proof to the chain 00:06:26.580 --> 00:06:28.670 align:start position:0% proof to the chain and<00:06:27.060> you<00:06:27.120> can<00:06:27.240> see<00:06:27.360> that<00:06:27.539> the<00:06:27.780> leaf<00:06:28.020> values<00:06:28.380> in 00:06:28.670 --> 00:06:28.680 align:start position:0% and you can see that the leaf values in 00:06:28.680 --> 00:06:30.529 align:start position:0% and you can see that the leaf values in this<00:06:28.800> tree<00:06:28.979> are<00:06:29.400> the<00:06:29.580> hash<00:06:29.759> of<00:06:30.120> the<00:06:30.300> total 00:06:30.529 --> 00:06:30.539 align:start position:0% this tree are the hash of the total 00:06:30.539 --> 00:06:32.990 align:start position:0% this tree are the hash of the total reputation<00:06:30.960> owned<00:06:31.380> by<00:06:31.500> this<00:06:31.680> Epoch<00:06:32.220> key 00:06:32.990 --> 00:06:33.000 align:start position:0% reputation owned by this Epoch key 00:06:33.000 --> 00:06:35.629 align:start position:0% reputation owned by this Epoch key and<00:06:33.479> so<00:06:33.720> we<00:06:33.960> determined<00:06:34.380> the<00:06:34.560> index<00:06:34.919> of<00:06:35.340> the 00:06:35.629 --> 00:06:35.639 align:start position:0% and so we determined the index of the 00:06:35.639 --> 00:06:37.430 align:start position:0% and so we determined the index of the user's<00:06:35.940> Leaf<00:06:36.240> in<00:06:36.360> the<00:06:36.479> tree<00:06:36.600> in<00:06:37.080> the<00:06:37.259> tree 00:06:37.430 --> 00:06:37.440 align:start position:0% user's Leaf in the tree in the tree 00:06:37.440 --> 00:06:39.529 align:start position:0% user's Leaf in the tree in the tree using<00:06:37.979> the<00:06:38.100> epoch<00:06:38.580> key<00:06:38.699> so<00:06:39.180> in<00:06:39.300> the<00:06:39.419> previous 00:06:39.529 --> 00:06:39.539 align:start position:0% using the epoch key so in the previous 00:06:39.539 --> 00:06:41.390 align:start position:0% using the epoch key so in the previous slide<00:06:39.840> you<00:06:40.020> saw<00:06:40.199> that<00:06:40.440> the<00:06:40.620> epoch<00:06:41.039> key<00:06:41.160> is<00:06:41.280> just 00:06:41.390 --> 00:06:41.400 align:start position:0% slide you saw that the epoch key is just 00:06:41.400 --> 00:06:43.610 align:start position:0% slide you saw that the epoch key is just smash<00:06:41.759> of<00:06:41.940> some<00:06:42.120> arbitrary<00:06:42.479> data<00:06:42.900> and<00:06:43.500> we're 00:06:43.610 --> 00:06:43.620 align:start position:0% smash of some arbitrary data and we're 00:06:43.620 --> 00:06:47.029 align:start position:0% smash of some arbitrary data and we're able<00:06:43.919> to<00:06:44.039> uh<00:06:44.900> apply<00:06:45.900> or<00:06:46.139> were<00:06:46.740> able<00:06:46.979> to 00:06:47.029 --> 00:06:47.039 align:start position:0% able to uh apply or were able to 00:06:47.039 --> 00:06:48.890 align:start position:0% able to uh apply or were able to determine<00:06:47.460> a<00:06:47.580> leaf<00:06:47.819> in<00:06:47.940> the<00:06:48.060> tree<00:06:48.240> by<00:06:48.780> taking 00:06:48.890 --> 00:06:48.900 align:start position:0% determine a leaf in the tree by taking 00:06:48.900 --> 00:06:52.249 align:start position:0% determine a leaf in the tree by taking the<00:06:49.259> modulus<00:06:49.740> of<00:06:49.919> that<00:06:50.100> hash<00:06:50.419> uh<00:06:51.419> across<00:06:52.080> the 00:06:52.249 --> 00:06:52.259 align:start position:0% the modulus of that hash uh across the 00:06:52.259 --> 00:06:54.230 align:start position:0% the modulus of that hash uh across the the<00:06:52.440> number<00:06:52.680> of<00:06:52.860> leaves<00:06:53.160> in<00:06:53.280> the<00:06:53.400> tree<00:06:53.520> so<00:06:54.060> if 00:06:54.230 --> 00:06:54.240 align:start position:0% the number of leaves in the tree so if 00:06:54.240 --> 00:06:56.450 align:start position:0% the number of leaves in the tree so if we<00:06:54.360> use<00:06:54.539> this<00:06:54.780> exact<00:06:55.199> tree<00:06:55.440> we<00:06:55.860> would<00:06:55.979> take<00:06:56.160> the 00:06:56.450 --> 00:06:56.460 align:start position:0% we use this exact tree we would take the 00:06:56.460 --> 00:06:58.430 align:start position:0% we use this exact tree we would take the hash<00:06:56.819> modulus<00:06:57.479> two<00:06:57.720> to<00:06:57.960> the<00:06:58.080> third<00:06:58.199> because 00:06:58.430 --> 00:06:58.440 align:start position:0% hash modulus two to the third because 00:06:58.440 --> 00:07:00.110 align:start position:0% hash modulus two to the third because it's<00:06:58.680> only<00:06:58.800> three<00:06:58.979> levels<00:06:59.280> deep<00:06:59.460> but<00:07:00.000> of 00:07:00.110 --> 00:07:00.120 align:start position:0% it's only three levels deep but of 00:07:00.120 --> 00:07:01.430 align:start position:0% it's only three levels deep but of course<00:07:00.180> if<00:07:00.300> we<00:07:00.419> did<00:07:00.539> that<00:07:00.660> we<00:07:00.780> would<00:07:00.900> have<00:07:01.020> lots 00:07:01.430 --> 00:07:01.440 align:start position:0% course if we did that we would have lots 00:07:01.440 --> 00:07:03.590 align:start position:0% course if we did that we would have lots of collisions<00:07:01.860> so<00:07:02.639> when<00:07:02.880> we<00:07:03.000> operate<00:07:03.419> this 00:07:03.590 --> 00:07:03.600 align:start position:0% of collisions so when we operate this 00:07:03.600 --> 00:07:07.010 align:start position:0% of collisions so when we operate this tree<00:07:03.840> in<00:07:04.199> production<00:07:04.560> we<00:07:04.979> use<00:07:05.160> a<00:07:05.460> depth<00:07:05.880> of<00:07:06.060> 128 00:07:07.010 --> 00:07:07.020 align:start position:0% tree in production we use a depth of 128 00:07:07.020 --> 00:07:09.469 align:start position:0% tree in production we use a depth of 128 so<00:07:07.500> we<00:07:07.680> take<00:07:07.860> the<00:07:08.039> hash<00:07:08.280> modulus<00:07:08.940> 2<00:07:09.180> to<00:07:09.360> the 00:07:09.469 --> 00:07:09.479 align:start position:0% so we take the hash modulus 2 to the 00:07:09.479 --> 00:07:11.629 align:start position:0% so we take the hash modulus 2 to the 128th<00:07:10.080> and<00:07:10.380> now<00:07:10.620> everyone<00:07:10.860> gets<00:07:11.280> a<00:07:11.400> unique 00:07:11.629 --> 00:07:11.639 align:start position:0% 128th and now everyone gets a unique 00:07:11.639 --> 00:07:14.150 align:start position:0% 128th and now everyone gets a unique Epoch<00:07:12.180> key<00:07:12.300> and<00:07:12.539> we<00:07:12.780> have<00:07:12.900> 128<00:07:13.620> bits<00:07:13.979> of 00:07:14.150 --> 00:07:14.160 align:start position:0% Epoch key and we have 128 bits of 00:07:14.160 --> 00:07:15.710 align:start position:0% Epoch key and we have 128 bits of collision<00:07:14.520> resistance 00:07:15.710 --> 00:07:15.720 align:start position:0% collision resistance 00:07:15.720 --> 00:07:18.170 align:start position:0% collision resistance so<00:07:16.199> the<00:07:16.380> whole<00:07:16.500> idea<00:07:16.740> behind<00:07:16.979> unirp<00:07:17.460> is<00:07:17.639> users 00:07:18.170 --> 00:07:18.180 align:start position:0% so the whole idea behind unirp is users 00:07:18.180 --> 00:07:19.730 align:start position:0% so the whole idea behind unirp is users have<00:07:18.419> these<00:07:18.720> identities 00:07:19.730 --> 00:07:19.740 align:start position:0% have these identities 00:07:19.740 --> 00:07:21.469 align:start position:0% have these identities um<00:07:19.800> for<00:07:19.979> that<00:07:20.220> are<00:07:20.280> valid<00:07:20.520> for<00:07:20.639> an<00:07:20.699> Epoch<00:07:21.180> and 00:07:21.469 --> 00:07:21.479 align:start position:0% um for that are valid for an Epoch and 00:07:21.479 --> 00:07:22.790 align:start position:0% um for that are valid for an Epoch and then<00:07:21.599> at<00:07:21.720> the<00:07:21.840> end<00:07:21.900> of<00:07:22.020> that<00:07:22.080> Epoch<00:07:22.560> they<00:07:22.680> pack 00:07:22.790 --> 00:07:22.800 align:start position:0% then at the end of that Epoch they pack 00:07:22.800 --> 00:07:24.830 align:start position:0% then at the end of that Epoch they pack up<00:07:22.919> their<00:07:23.099> reputation<00:07:23.520> and<00:07:24.060> they<00:07:24.180> move<00:07:24.360> to<00:07:24.599> a 00:07:24.830 --> 00:07:24.840 align:start position:0% up their reputation and they move to a 00:07:24.840 --> 00:07:26.629 align:start position:0% up their reputation and they move to a new<00:07:24.900> identity<00:07:25.259> and<00:07:25.440> the<00:07:25.560> next<00:07:25.680> Epoch<00:07:26.220> by 00:07:26.629 --> 00:07:26.639 align:start position:0% new identity and the next Epoch by 00:07:26.639 --> 00:07:30.350 align:start position:0% new identity and the next Epoch by inserting<00:07:27.120> a<00:07:27.360> leaf<00:07:28.139> into<00:07:28.440> the<00:07:29.099> new<00:07:29.220> state<00:07:29.400> tree 00:07:30.350 --> 00:07:30.360 align:start position:0% inserting a leaf into the new state tree 00:07:30.360 --> 00:07:32.270 align:start position:0% inserting a leaf into the new state tree uh<00:07:30.900> I<00:07:31.199> didn't<00:07:31.259> say<00:07:31.440> this<00:07:31.500> before<00:07:31.680> but<00:07:31.860> we<00:07:32.099> have 00:07:32.270 --> 00:07:32.280 align:start position:0% uh I didn't say this before but we have 00:07:32.280 --> 00:07:34.670 align:start position:0% uh I didn't say this before but we have a<00:07:32.639> copy<00:07:32.819> of<00:07:32.940> these<00:07:33.180> trees<00:07:33.479> every<00:07:33.720> Epoch<00:07:34.380> that 00:07:34.670 --> 00:07:34.680 align:start position:0% a copy of these trees every Epoch that 00:07:34.680 --> 00:07:37.249 align:start position:0% a copy of these trees every Epoch that we<00:07:34.800> that<00:07:35.160> we<00:07:35.400> use 00:07:37.249 --> 00:07:37.259 align:start position:0% we that we use 00:07:37.259 --> 00:07:38.870 align:start position:0% we that we use right<00:07:37.500> so<00:07:37.860> let's<00:07:37.979> change<00:07:38.220> gears<00:07:38.580> a<00:07:38.699> little<00:07:38.759> bit 00:07:38.870 --> 00:07:38.880 align:start position:0% right so let's change gears a little bit 00:07:38.880 --> 00:07:41.450 align:start position:0% right so let's change gears a little bit and<00:07:39.180> talk<00:07:39.300> about<00:07:39.539> the<00:07:40.020> user<00:07:40.319> experience<00:07:40.800> for 00:07:41.450 --> 00:07:41.460 align:start position:0% and talk about the user experience for 00:07:41.460 --> 00:07:44.029 align:start position:0% and talk about the user experience for uh<00:07:42.060> zero<00:07:42.419> knowledge<00:07:42.660> applications<00:07:43.139> so<00:07:43.919> we 00:07:44.029 --> 00:07:44.039 align:start position:0% uh zero knowledge applications so we 00:07:44.039 --> 00:07:46.010 align:start position:0% uh zero knowledge applications so we have<00:07:44.160> these<00:07:44.400> proofs<00:07:44.759> with<00:07:45.000> unrap<00:07:45.599> and<00:07:45.780> we<00:07:45.900> want 00:07:46.010 --> 00:07:46.020 align:start position:0% have these proofs with unrap and we want 00:07:46.020 --> 00:07:49.129 align:start position:0% have these proofs with unrap and we want the<00:07:46.139> users<00:07:46.380> to<00:07:46.560> be<00:07:46.680> able<00:07:46.860> to<00:07:46.979> uh<00:07:48.240> make<00:07:48.900> these 00:07:49.129 --> 00:07:49.139 align:start position:0% the users to be able to uh make these 00:07:49.139 --> 00:07:50.629 align:start position:0% the users to be able to uh make these proofs<00:07:49.440> inside<00:07:49.620> of<00:07:49.860> like<00:07:49.979> their<00:07:50.160> browser<00:07:50.460> for 00:07:50.629 --> 00:07:50.639 align:start position:0% proofs inside of like their browser for 00:07:50.639 --> 00:07:52.010 align:start position:0% proofs inside of like their browser for example<00:07:50.819> on<00:07:51.000> a<00:07:51.120> computer 00:07:52.010 --> 00:07:52.020 align:start position:0% example on a computer 00:07:52.020 --> 00:07:54.770 align:start position:0% example on a computer so<00:07:52.680> here<00:07:53.160> we<00:07:53.340> have<00:07:53.460> a<00:07:53.580> graph<00:07:53.819> of<00:07:54.180> the<00:07:54.479> proving 00:07:54.770 --> 00:07:54.780 align:start position:0% so here we have a graph of the proving 00:07:54.780 --> 00:07:56.930 align:start position:0% so here we have a graph of the proving time<00:07:54.960> for<00:07:55.259> proofs<00:07:55.620> of<00:07:55.740> various<00:07:56.039> sizes<00:07:56.400> on<00:07:56.819> a 00:07:56.930 --> 00:07:56.940 align:start position:0% time for proofs of various sizes on a 00:07:56.940 --> 00:07:59.029 align:start position:0% time for proofs of various sizes on a few<00:07:57.060> different<00:07:57.240> devices<00:07:57.660> and<00:07:58.560> yeah<00:07:58.800> you<00:07:58.979> can 00:07:59.029 --> 00:07:59.039 align:start position:0% few different devices and yeah you can 00:07:59.039 --> 00:08:01.129 align:start position:0% few different devices and yeah you can read<00:07:59.160> it<00:07:59.340> pretty<00:07:59.460> well<00:07:59.639> uh<00:08:00.419> so<00:08:00.720> you<00:08:00.900> can<00:08:00.960> see 00:08:01.129 --> 00:08:01.139 align:start position:0% read it pretty well uh so you can see 00:08:01.139 --> 00:08:04.189 align:start position:0% read it pretty well uh so you can see that<00:08:01.560> there's<00:08:02.160> a<00:08:02.340> sweet<00:08:02.520> spot<00:08:02.759> below<00:08:03.300> 30<00:08:04.080> 000 00:08:04.189 --> 00:08:04.199 align:start position:0% that there's a sweet spot below 30 000 00:08:04.199 --> 00:08:06.170 align:start position:0% that there's a sweet spot below 30 000 constraints<00:08:04.680> where<00:08:05.160> any<00:08:05.340> proof<00:08:05.639> you<00:08:05.759> make<00:08:05.940> is 00:08:06.170 --> 00:08:06.180 align:start position:0% constraints where any proof you make is 00:08:06.180 --> 00:08:08.150 align:start position:0% constraints where any proof you make is going<00:08:06.300> to<00:08:06.419> take<00:08:06.539> less<00:08:06.780> than<00:08:06.960> five<00:08:07.139> seconds<00:08:07.380> on 00:08:08.150 --> 00:08:08.160 align:start position:0% going to take less than five seconds on 00:08:08.160 --> 00:08:10.550 align:start position:0% going to take less than five seconds on most<00:08:08.340> modern<00:08:08.639> devices<00:08:09.120> that<00:08:09.840> purple<00:08:10.080> line<00:08:10.319> at 00:08:10.550 --> 00:08:10.560 align:start position:0% most modern devices that purple line at 00:08:10.560 --> 00:08:13.550 align:start position:0% most modern devices that purple line at the<00:08:10.680> top<00:08:10.740> is<00:08:11.099> uh<00:08:11.520> an<00:08:11.819> iPhone<00:08:11.940> from<00:08:12.360> like<00:08:12.560> 2016. 00:08:13.550 --> 00:08:13.560 align:start position:0% the top is uh an iPhone from like 2016. 00:08:13.560 --> 00:08:15.350 align:start position:0% the top is uh an iPhone from like 2016. so<00:08:13.919> like<00:08:14.039> older<00:08:14.400> mobile<00:08:14.580> devices<00:08:14.819> can<00:08:15.180> still 00:08:15.350 --> 00:08:15.360 align:start position:0% so like older mobile devices can still 00:08:15.360 --> 00:08:17.270 align:start position:0% so like older mobile devices can still do<00:08:15.479> that<00:08:15.660> in<00:08:15.900> less<00:08:16.020> than<00:08:16.139> 10<00:08:16.319> seconds<00:08:16.560> which<00:08:17.039> is 00:08:17.270 --> 00:08:17.280 align:start position:0% do that in less than 10 seconds which is 00:08:17.280 --> 00:08:19.670 align:start position:0% do that in less than 10 seconds which is pretty<00:08:17.759> acceptable<00:08:18.180> performance 00:08:19.670 --> 00:08:19.680 align:start position:0% pretty acceptable performance 00:08:19.680 --> 00:08:21.770 align:start position:0% pretty acceptable performance so<00:08:20.220> where's<00:08:20.400> unirup<00:08:21.000> where<00:08:21.360> where<00:08:21.479> are<00:08:21.660> our 00:08:21.770 --> 00:08:21.780 align:start position:0% so where's unirup where where are our 00:08:21.780 --> 00:08:23.029 align:start position:0% so where's unirup where where are our proofs<00:08:22.020> on<00:08:22.139> this<00:08:22.259> graph 00:08:23.029 --> 00:08:23.039 align:start position:0% proofs on this graph 00:08:23.039 --> 00:08:24.710 align:start position:0% proofs on this graph the<00:08:23.460> first<00:08:23.699> proof<00:08:23.940> we<00:08:24.060> have<00:08:24.180> is<00:08:24.300> a<00:08:24.419> sign<00:08:24.539> up 00:08:24.710 --> 00:08:24.720 align:start position:0% the first proof we have is a sign up 00:08:24.720 --> 00:08:26.210 align:start position:0% the first proof we have is a sign up proof<00:08:24.960> it's<00:08:25.259> very<00:08:25.440> small<00:08:25.620> it's<00:08:25.800> 700 00:08:26.210 --> 00:08:26.220 align:start position:0% proof it's very small it's 700 00:08:26.220 --> 00:08:28.249 align:start position:0% proof it's very small it's 700 constraints<00:08:26.639> and<00:08:26.940> all<00:08:27.060> it<00:08:27.240> does<00:08:27.360> is<00:08:27.599> output<00:08:28.020> a 00:08:28.249 --> 00:08:28.259 align:start position:0% constraints and all it does is output a 00:08:28.259 --> 00:08:31.070 align:start position:0% constraints and all it does is output a hash<00:08:28.440> value<00:08:28.680> so<00:08:29.639> less<00:08:29.879> than<00:08:30.000> one<00:08:30.180> second 00:08:31.070 --> 00:08:31.080 align:start position:0% hash value so less than one second 00:08:31.080 --> 00:08:32.690 align:start position:0% hash value so less than one second a<00:08:31.379> little<00:08:31.560> bit<00:08:31.680> bigger<00:08:31.919> we<00:08:32.039> have<00:08:32.159> an<00:08:32.279> Epoch 00:08:32.690 --> 00:08:32.700 align:start position:0% a little bit bigger we have an Epoch 00:08:32.700 --> 00:08:34.310 align:start position:0% a little bit bigger we have an Epoch keep<00:08:32.760> proof<00:08:33.120> this<00:08:33.479> proves<00:08:33.779> control<00:08:33.959> of<00:08:34.200> an 00:08:34.310 --> 00:08:34.320 align:start position:0% keep proof this proves control of an 00:08:34.320 --> 00:08:36.409 align:start position:0% keep proof this proves control of an Epoch<00:08:34.680> key<00:08:34.800> and<00:08:34.919> also<00:08:35.159> proves<00:08:35.520> a<00:08:35.820> leaf<00:08:36.120> in<00:08:36.300> the 00:08:36.409 --> 00:08:36.419 align:start position:0% Epoch key and also proves a leaf in the 00:08:36.419 --> 00:08:38.089 align:start position:0% Epoch key and also proves a leaf in the state<00:08:36.539> tree<00:08:36.779> so<00:08:37.260> it's<00:08:37.440> a<00:08:37.560> little<00:08:37.620> bit<00:08:37.740> bigger 00:08:38.089 --> 00:08:38.099 align:start position:0% state tree so it's a little bit bigger 00:08:38.099 --> 00:08:40.370 align:start position:0% state tree so it's a little bit bigger 3000<00:08:38.880> constraints<00:08:39.300> still<00:08:39.779> less<00:08:40.020> than<00:08:40.200> one 00:08:40.370 --> 00:08:40.380 align:start position:0% 3000 constraints still less than one 00:08:40.380 --> 00:08:42.889 align:start position:0% 3000 constraints still less than one second<00:08:40.560> on<00:08:40.800> most<00:08:40.979> devices<00:08:41.279> and<00:08:42.240> way<00:08:42.599> over<00:08:42.719> here 00:08:42.889 --> 00:08:42.899 align:start position:0% second on most devices and way over here 00:08:42.899 --> 00:08:45.050 align:start position:0% second on most devices and way over here we<00:08:43.380> have<00:08:43.500> this<00:08:43.740> user<00:08:44.099> State<00:08:44.219> transition<00:08:44.640> proof 00:08:45.050 --> 00:08:45.060 align:start position:0% we have this user State transition proof 00:08:45.060 --> 00:08:47.630 align:start position:0% we have this user State transition proof and<00:08:45.600> in<00:08:45.779> this<00:08:45.959> proof<00:08:46.260> we<00:08:46.560> add<00:08:46.740> up<00:08:46.920> the<00:08:47.100> value<00:08:47.339> in 00:08:47.630 --> 00:08:47.640 align:start position:0% and in this proof we add up the value in 00:08:47.640 --> 00:08:49.190 align:start position:0% and in this proof we add up the value in the<00:08:47.820> state<00:08:47.940> tree<00:08:48.120> leaf<00:08:48.540> as<00:08:48.720> well<00:08:48.899> as<00:08:49.019> the 00:08:49.190 --> 00:08:49.200 align:start position:0% the state tree leaf as well as the 00:08:49.200 --> 00:08:50.990 align:start position:0% the state tree leaf as well as the values<00:08:49.500> in<00:08:49.680> all<00:08:49.860> of<00:08:49.920> the<00:08:50.040> epoch<00:08:50.459> tree<00:08:50.580> leaves 00:08:50.990 --> 00:08:51.000 align:start position:0% values in all of the epoch tree leaves 00:08:51.000 --> 00:08:52.850 align:start position:0% values in all of the epoch tree leaves and<00:08:51.360> output<00:08:51.720> a<00:08:51.899> new<00:08:52.019> state<00:08:52.140> tree<00:08:52.320> leaf<00:08:52.680> with 00:08:52.850 --> 00:08:52.860 align:start position:0% and output a new state tree leaf with 00:08:52.860 --> 00:08:55.250 align:start position:0% and output a new state tree leaf with the<00:08:53.040> sum<00:08:53.220> of<00:08:53.760> the<00:08:53.880> reputation<00:08:54.300> the<00:08:54.600> user<00:08:54.899> owns 00:08:55.250 --> 00:08:55.260 align:start position:0% the sum of the reputation the user owns 00:08:55.260 --> 00:08:56.870 align:start position:0% the sum of the reputation the user owns so<00:08:55.680> we<00:08:55.860> have<00:08:55.980> to<00:08:56.100> do<00:08:56.160> multiple<00:08:56.459> inclusion 00:08:56.870 --> 00:08:56.880 align:start position:0% so we have to do multiple inclusion 00:08:56.880 --> 00:08:58.670 align:start position:0% so we have to do multiple inclusion inclusion<00:08:57.600> proofs<00:08:57.899> over<00:08:58.019> trees<00:08:58.440> that<00:08:58.560> are 00:08:58.670 --> 00:08:58.680 align:start position:0% inclusion proofs over trees that are 00:08:58.680 --> 00:09:00.530 align:start position:0% inclusion proofs over trees that are quite<00:08:58.800> large<00:08:59.040> but<00:08:59.700> we<00:08:59.880> still<00:09:00.060> end<00:09:00.240> up<00:09:00.360> with 00:09:00.530 --> 00:09:00.540 align:start position:0% quite large but we still end up with 00:09:00.540 --> 00:09:02.930 align:start position:0% quite large but we still end up with about<00:09:00.720> 29<00:09:01.380> 000<00:09:01.440> constraints<00:09:01.920> so<00:09:02.459> less<00:09:02.820> than 00:09:02.930 --> 00:09:02.940 align:start position:0% about 29 000 constraints so less than 00:09:02.940 --> 00:09:05.030 align:start position:0% about 29 000 constraints so less than five<00:09:03.120> seconds<00:09:03.300> on<00:09:03.540> Modern<00:09:03.720> devices<00:09:04.080> and<00:09:04.860> we 00:09:05.030 --> 00:09:05.040 align:start position:0% five seconds on Modern devices and we 00:09:05.040 --> 00:09:06.410 align:start position:0% five seconds on Modern devices and we can<00:09:05.160> also<00:09:05.399> execute<00:09:05.760> this<00:09:05.940> proof<00:09:06.180> in<00:09:06.300> the 00:09:06.410 --> 00:09:06.420 align:start position:0% can also execute this proof in the 00:09:06.420 --> 00:09:07.730 align:start position:0% can also execute this proof in the background<00:09:06.600> so<00:09:06.839> the<00:09:07.019> user<00:09:07.260> doesn't<00:09:07.440> have<00:09:07.620> to 00:09:07.730 --> 00:09:07.740 align:start position:0% background so the user doesn't have to 00:09:07.740 --> 00:09:12.050 align:start position:0% background so the user doesn't have to know<00:09:07.860> about<00:09:07.980> it<00:09:08.100> and<00:09:08.279> doesn't<00:09:08.459> have<00:09:08.700> to<00:09:08.760> wait 00:09:12.050 --> 00:09:12.060 align:start position:0% 00:09:12.060 --> 00:09:15.230 align:start position:0% right<00:09:12.660> so<00:09:13.200> I<00:09:13.680> think<00:09:13.800> a<00:09:14.040> good<00:09:14.160> goal<00:09:14.519> for<00:09:14.760> zika 00:09:15.230 --> 00:09:15.240 align:start position:0% right so I think a good goal for zika 00:09:15.240 --> 00:09:16.670 align:start position:0% right so I think a good goal for zika applications<00:09:15.660> and<00:09:15.959> for<00:09:16.080> blockchain<00:09:16.440> in 00:09:16.670 --> 00:09:16.680 align:start position:0% applications and for blockchain in 00:09:16.680 --> 00:09:18.949 align:start position:0% applications and for blockchain in general<00:09:16.800> is<00:09:17.580> users<00:09:18.000> not<00:09:18.240> being<00:09:18.420> aware<00:09:18.720> that 00:09:18.949 --> 00:09:18.959 align:start position:0% general is users not being aware that 00:09:18.959 --> 00:09:20.389 align:start position:0% general is users not being aware that they're<00:09:19.140> using<00:09:19.380> the<00:09:19.500> blockchain<00:09:19.920> while 00:09:20.389 --> 00:09:20.399 align:start position:0% they're using the blockchain while 00:09:20.399 --> 00:09:22.550 align:start position:0% they're using the blockchain while they're<00:09:20.580> using<00:09:20.880> the<00:09:21.000> blockchain<00:09:21.420> so<00:09:22.140> a<00:09:22.320> lot<00:09:22.440> of 00:09:22.550 --> 00:09:22.560 align:start position:0% they're using the blockchain so a lot of 00:09:22.560 --> 00:09:23.810 align:start position:0% they're using the blockchain so a lot of you<00:09:22.620> probably<00:09:22.860> use<00:09:23.100> websites<00:09:23.700> or 00:09:23.810 --> 00:09:23.820 align:start position:0% you probably use websites or 00:09:23.820 --> 00:09:26.750 align:start position:0% you probably use websites or applications<00:09:24.240> like<00:09:24.720> Spotify<00:09:25.100> or<00:09:26.100> Twitter<00:09:26.459> or 00:09:26.750 --> 00:09:26.760 align:start position:0% applications like Spotify or Twitter or 00:09:26.760 --> 00:09:29.150 align:start position:0% applications like Spotify or Twitter or Reddit<00:09:26.940> or<00:09:27.240> stack<00:09:27.480> Overflow<00:09:27.959> uh<00:09:28.800> just<00:09:28.980> raise 00:09:29.150 --> 00:09:29.160 align:start position:0% Reddit or stack Overflow uh just raise 00:09:29.160 --> 00:09:30.350 align:start position:0% Reddit or stack Overflow uh just raise your<00:09:29.339> hand<00:09:29.459> if<00:09:29.640> you<00:09:29.820> know<00:09:29.940> what<00:09:30.180> kind<00:09:30.300> of 00:09:30.350 --> 00:09:30.360 align:start position:0% your hand if you know what kind of 00:09:30.360 --> 00:09:33.889 align:start position:0% your hand if you know what kind of database<00:09:30.779> those<00:09:31.140> applications<00:09:31.620> are<00:09:31.920> using 00:09:33.889 --> 00:09:33.899 align:start position:0% database those applications are using 00:09:33.899 --> 00:09:35.449 align:start position:0% database those applications are using right<00:09:34.140> no<00:09:34.560> one<00:09:34.680> raised<00:09:34.920> okay<00:09:35.220> one<00:09:35.339> person 00:09:35.449 --> 00:09:35.459 align:start position:0% right no one raised okay one person 00:09:35.459 --> 00:09:36.769 align:start position:0% right no one raised okay one person raised<00:09:35.820> their<00:09:35.880> hand<00:09:36.000> we<00:09:36.120> have<00:09:36.240> at<00:09:36.540> least<00:09:36.600> one 00:09:36.769 --> 00:09:36.779 align:start position:0% raised their hand we have at least one 00:09:36.779 --> 00:09:38.509 align:start position:0% raised their hand we have at least one nerd<00:09:37.019> in<00:09:37.140> the<00:09:37.260> crowd<00:09:37.500> but<00:09:37.920> for<00:09:38.100> the<00:09:38.279> most<00:09:38.399> part 00:09:38.509 --> 00:09:38.519 align:start position:0% nerd in the crowd but for the most part 00:09:38.519 --> 00:09:40.370 align:start position:0% nerd in the crowd but for the most part users<00:09:39.060> don't<00:09:39.240> really<00:09:39.420> care<00:09:39.660> about<00:09:39.899> the<00:09:40.080> data 00:09:40.370 --> 00:09:40.380 align:start position:0% users don't really care about the data 00:09:40.380 --> 00:09:41.389 align:start position:0% users don't really care about the data structures<00:09:40.620> that<00:09:40.860> are<00:09:40.980> backing<00:09:41.279> the 00:09:41.389 --> 00:09:41.399 align:start position:0% structures that are backing the 00:09:41.399 --> 00:09:43.430 align:start position:0% structures that are backing the applications<00:09:41.820> they're<00:09:42.180> using<00:09:42.540> and 00:09:43.430 --> 00:09:43.440 align:start position:0% applications they're using and 00:09:43.440 --> 00:09:45.170 align:start position:0% applications they're using and blockchains<00:09:44.160> are<00:09:44.279> really<00:09:44.519> the<00:09:44.700> same<00:09:44.880> they're 00:09:45.170 --> 00:09:45.180 align:start position:0% blockchains are really the same they're 00:09:45.180 --> 00:09:46.790 align:start position:0% blockchains are really the same they're just<00:09:45.360> databases<00:09:45.899> with<00:09:46.140> different<00:09:46.320> properties 00:09:46.790 --> 00:09:46.800 align:start position:0% just databases with different properties 00:09:46.800 --> 00:09:48.829 align:start position:0% just databases with different properties and<00:09:47.220> so<00:09:47.459> the<00:09:47.940> user<00:09:48.180> shouldn't<00:09:48.480> have<00:09:48.600> to<00:09:48.720> be 00:09:48.829 --> 00:09:48.839 align:start position:0% and so the user shouldn't have to be 00:09:48.839 --> 00:09:52.090 align:start position:0% and so the user shouldn't have to be aware<00:09:49.140> that<00:09:49.320> they're<00:09:49.500> using<00:09:49.740> the<00:09:49.800> blockchain 00:09:52.090 --> 00:09:52.100 align:start position:0% aware that they're using the blockchain 00:09:52.100 --> 00:09:55.190 align:start position:0% aware that they're using the blockchain so<00:09:53.100> this<00:09:53.339> is<00:09:53.459> the<00:09:53.760> the<00:09:54.000> architecture<00:09:54.779> of<00:09:55.080> a 00:09:55.190 --> 00:09:55.200 align:start position:0% so this is the the architecture of a 00:09:55.200 --> 00:09:57.590 align:start position:0% so this is the the architecture of a traditional<00:09:55.500> dap<00:09:55.860> and<00:09:56.700> as<00:09:57.000> an<00:09:57.120> engineer<00:09:57.420> I 00:09:57.590 --> 00:09:57.600 align:start position:0% traditional dap and as an engineer I 00:09:57.600 --> 00:09:58.670 align:start position:0% traditional dap and as an engineer I really<00:09:57.720> like<00:09:57.899> this<00:09:58.019> architecture<00:09:58.500> because 00:09:58.670 --> 00:09:58.680 align:start position:0% really like this architecture because 00:09:58.680 --> 00:10:00.290 align:start position:0% really like this architecture because it's<00:09:58.920> simple<00:09:59.160> and<00:09:59.760> it's<00:09:59.940> sort<00:10:00.180> of 00:10:00.290 --> 00:10:00.300 align:start position:0% it's simple and it's sort of 00:10:00.300 --> 00:10:02.329 align:start position:0% it's simple and it's sort of unprecedented<00:10:00.839> before<00:10:01.080> blockchain<00:10:01.620> but<00:10:02.220> for 00:10:02.329 --> 00:10:02.339 align:start position:0% unprecedented before blockchain but for 00:10:02.339 --> 00:10:04.009 align:start position:0% unprecedented before blockchain but for the<00:10:02.459> reasons<00:10:02.700> that<00:10:02.820> I<00:10:03.000> like<00:10:03.120> it<00:10:03.300> I<00:10:03.660> think<00:10:03.779> that 00:10:04.009 --> 00:10:04.019 align:start position:0% the reasons that I like it I think that 00:10:04.019 --> 00:10:05.750 align:start position:0% the reasons that I like it I think that users<00:10:04.380> kind<00:10:04.560> of<00:10:04.680> hate<00:10:04.800> it<00:10:04.980> because<00:10:05.160> they<00:10:05.640> have 00:10:05.750 --> 00:10:05.760 align:start position:0% users kind of hate it because they have 00:10:05.760 --> 00:10:07.250 align:start position:0% users kind of hate it because they have to<00:10:05.880> learn<00:10:06.000> about<00:10:06.180> the<00:10:06.360> blockchain<00:10:06.720> and<00:10:07.200> then 00:10:07.250 --> 00:10:07.260 align:start position:0% to learn about the blockchain and then 00:10:07.260 --> 00:10:08.389 align:start position:0% to learn about the blockchain and then they<00:10:07.380> have<00:10:07.500> to<00:10:07.620> learn<00:10:07.680> about<00:10:07.860> wallets<00:10:08.220> like 00:10:08.389 --> 00:10:08.399 align:start position:0% they have to learn about wallets like 00:10:08.399 --> 00:10:10.370 align:start position:0% they have to learn about wallets like metamask<00:10:08.820> and<00:10:09.120> transactions<00:10:09.779> and<00:10:10.019> gas<00:10:10.200> and 00:10:10.370 --> 00:10:10.380 align:start position:0% metamask and transactions and gas and 00:10:10.380 --> 00:10:12.410 align:start position:0% metamask and transactions and gas and gas<00:10:10.620> prices<00:10:10.800> and<00:10:11.160> way<00:10:11.459> and<00:10:11.880> ether<00:10:12.120> and<00:10:12.360> they 00:10:12.410 --> 00:10:12.420 align:start position:0% gas prices and way and ether and they 00:10:12.420 --> 00:10:14.090 align:start position:0% gas prices and way and ether and they have<00:10:12.480> to<00:10:12.600> get<00:10:12.720> ether<00:10:13.019> and<00:10:13.500> it's<00:10:13.620> a<00:10:13.800> whole<00:10:13.920> thing 00:10:14.090 --> 00:10:14.100 align:start position:0% have to get ether and it's a whole thing 00:10:14.100 --> 00:10:15.530 align:start position:0% have to get ether and it's a whole thing and<00:10:14.279> it's<00:10:14.459> it's<00:10:14.640> a<00:10:14.880> lot<00:10:14.940> for<00:10:15.120> them<00:10:15.240> to<00:10:15.420> learn 00:10:15.530 --> 00:10:15.540 align:start position:0% and it's it's a lot for them to learn 00:10:15.540 --> 00:10:18.170 align:start position:0% and it's it's a lot for them to learn just<00:10:15.839> to<00:10:16.019> use<00:10:16.200> a<00:10:16.500> single<00:10:16.740> dab 00:10:18.170 --> 00:10:18.180 align:start position:0% just to use a single dab 00:10:18.180 --> 00:10:20.810 align:start position:0% just to use a single dab so<00:10:18.720> luckily<00:10:19.080> if<00:10:19.440> we<00:10:19.560> use<00:10:19.740> ZK<00:10:20.279> identities 00:10:20.810 --> 00:10:20.820 align:start position:0% so luckily if we use ZK identities 00:10:20.820 --> 00:10:22.670 align:start position:0% so luckily if we use ZK identities instead<00:10:21.300> of<00:10:21.420> wallets<00:10:21.720> we<00:10:22.260> can<00:10:22.320> build<00:10:22.500> this 00:10:22.670 --> 00:10:22.680 align:start position:0% instead of wallets we can build this 00:10:22.680 --> 00:10:24.350 align:start position:0% instead of wallets we can build this more<00:10:22.860> traditional<00:10:23.220> three-tier<00:10:23.820> architecture 00:10:24.350 --> 00:10:24.360 align:start position:0% more traditional three-tier architecture 00:10:24.360 --> 00:10:27.530 align:start position:0% more traditional three-tier architecture where<00:10:24.899> we<00:10:25.080> introduce<00:10:25.440> a<00:10:25.620> relay<00:10:25.980> uh<00:10:26.880> that<00:10:27.120> that 00:10:27.530 --> 00:10:27.540 align:start position:0% where we introduce a relay uh that that 00:10:27.540 --> 00:10:29.449 align:start position:0% where we introduce a relay uh that that bundles<00:10:27.959> the<00:10:28.140> transaction<00:10:28.440> and<00:10:28.680> sends<00:10:29.040> it<00:10:29.160> so 00:10:29.449 --> 00:10:29.459 align:start position:0% bundles the transaction and sends it so 00:10:29.459 --> 00:10:31.250 align:start position:0% bundles the transaction and sends it so the<00:10:29.640> flow<00:10:29.820> would<00:10:30.000> be<00:10:30.120> the<00:10:30.540> web<00:10:30.660> app<00:10:30.839> generates 00:10:31.250 --> 00:10:31.260 align:start position:0% the flow would be the web app generates 00:10:31.260 --> 00:10:33.350 align:start position:0% the flow would be the web app generates a<00:10:31.440> ZK<00:10:31.740> proof<00:10:32.040> gives<00:10:32.339> it<00:10:32.459> to<00:10:32.580> the<00:10:32.640> relay<00:10:32.940> the 00:10:33.350 --> 00:10:33.360 align:start position:0% a ZK proof gives it to the relay the 00:10:33.360 --> 00:10:34.850 align:start position:0% a ZK proof gives it to the relay the relay<00:10:33.600> creates<00:10:33.959> a<00:10:34.080> transaction<00:10:34.440> and<00:10:34.740> then 00:10:34.850 --> 00:10:34.860 align:start position:0% relay creates a transaction and then 00:10:34.860 --> 00:10:36.829 align:start position:0% relay creates a transaction and then post<00:10:35.040> it<00:10:35.220> to<00:10:35.339> the<00:10:35.459> blockchain<00:10:35.820> and<00:10:36.720> the 00:10:36.829 --> 00:10:36.839 align:start position:0% post it to the blockchain and the 00:10:36.839 --> 00:10:38.630 align:start position:0% post it to the blockchain and the economics<00:10:37.320> of<00:10:37.500> why<00:10:37.740> the<00:10:37.920> relay<00:10:38.160> would<00:10:38.399> do<00:10:38.519> this 00:10:38.630 --> 00:10:38.640 align:start position:0% economics of why the relay would do this 00:10:38.640 --> 00:10:40.070 align:start position:0% economics of why the relay would do this are<00:10:39.000> sort<00:10:39.180> of<00:10:39.300> there<00:10:39.600> are<00:10:39.720> a<00:10:39.779> lot<00:10:39.839> of<00:10:39.959> different 00:10:40.070 --> 00:10:40.080 align:start position:0% are sort of there are a lot of different 00:10:40.080 --> 00:10:41.210 align:start position:0% are sort of there are a lot of different schemes<00:10:40.560> you<00:10:40.680> could<00:10:40.740> build<00:10:40.920> like 00:10:41.210 --> 00:10:41.220 align:start position:0% schemes you could build like 00:10:41.220 --> 00:10:42.530 align:start position:0% schemes you could build like subscription<00:10:41.519> models<00:10:41.880> or<00:10:42.060> just<00:10:42.240> like<00:10:42.360> free 00:10:42.530 --> 00:10:42.540 align:start position:0% subscription models or just like free 00:10:42.540 --> 00:10:44.810 align:start position:0% subscription models or just like free trial<00:10:42.779> models<00:10:43.260> uh<00:10:44.160> all<00:10:44.459> sorts<00:10:44.640> of<00:10:44.700> different 00:10:44.810 --> 00:10:44.820 align:start position:0% trial models uh all sorts of different 00:10:44.820 --> 00:10:47.269 align:start position:0% trial models uh all sorts of different things<00:10:45.000> you<00:10:45.180> could<00:10:45.300> do<00:10:45.899> and<00:10:46.380> so<00:10:46.560> one<00:10:46.800> one<00:10:46.980> note 00:10:47.269 --> 00:10:47.279 align:start position:0% things you could do and so one one note 00:10:47.279 --> 00:10:49.250 align:start position:0% things you could do and so one one note about<00:10:47.459> like<00:10:47.760> this<00:10:47.940> architecture<00:10:48.420> the<00:10:49.019> relay 00:10:49.250 --> 00:10:49.260 align:start position:0% about like this architecture the relay 00:10:49.260 --> 00:10:51.829 align:start position:0% about like this architecture the relay is<00:10:49.560> not<00:10:49.680> a<00:10:49.860> trusted<00:10:50.220> entity<00:10:50.519> uh<00:10:51.120> the<00:10:51.240> Relay<00:10:51.540> can 00:10:51.829 --> 00:10:51.839 align:start position:0% is not a trusted entity uh the Relay can 00:10:51.839 --> 00:10:53.509 align:start position:0% is not a trusted entity uh the Relay can censor<00:10:52.320> transactions<00:10:52.800> that<00:10:52.920> can<00:10:53.100> go<00:10:53.220> offline 00:10:53.509 --> 00:10:53.519 align:start position:0% censor transactions that can go offline 00:10:53.519 --> 00:10:55.610 align:start position:0% censor transactions that can go offline it<00:10:54.060> doesn't<00:10:54.180> matter<00:10:54.420> uh<00:10:54.779> the<00:10:54.959> web<00:10:55.079> applicant 00:10:55.610 --> 00:10:55.620 align:start position:0% it doesn't matter uh the web applicant 00:10:55.620 --> 00:10:57.470 align:start position:0% it doesn't matter uh the web applicant or<00:10:55.860> the<00:10:56.040> user<00:10:56.339> can<00:10:56.459> only<00:10:56.579> send<00:10:56.760> their<00:10:56.940> ZK<00:10:57.180> proof 00:10:57.470 --> 00:10:57.480 align:start position:0% or the user can only send their ZK proof 00:10:57.480 --> 00:10:59.269 align:start position:0% or the user can only send their ZK proof with<00:10:57.600> a<00:10:57.779> different<00:10:57.899> relay<00:10:58.260> or<00:10:58.680> broadcast<00:10:58.920> it 00:10:59.269 --> 00:10:59.279 align:start position:0% with a different relay or broadcast it 00:10:59.279 --> 00:11:01.069 align:start position:0% with a different relay or broadcast it to<00:10:59.399> the<00:10:59.459> blockchain<00:10:59.760> themselves<00:11:00.180> uh<00:11:00.899> the 00:11:01.069 --> 00:11:01.079 align:start position:0% to the blockchain themselves uh the 00:11:01.079 --> 00:11:03.530 align:start position:0% to the blockchain themselves uh the relay<00:11:01.380> also<00:11:01.740> can't<00:11:02.040> compromise<00:11:02.700> the<00:11:02.940> ZK<00:11:03.180> proof 00:11:03.530 --> 00:11:03.540 align:start position:0% relay also can't compromise the ZK proof 00:11:03.540 --> 00:11:04.730 align:start position:0% relay also can't compromise the ZK proof itself<00:11:03.779> because<00:11:04.019> if<00:11:04.200> they<00:11:04.380> change<00:11:04.560> anything 00:11:04.730 --> 00:11:04.740 align:start position:0% itself because if they change anything 00:11:04.740 --> 00:11:06.290 align:start position:0% itself because if they change anything about<00:11:05.100> it<00:11:05.279> the<00:11:05.579> proof<00:11:05.820> itself<00:11:06.000> will<00:11:06.180> be 00:11:06.290 --> 00:11:06.300 align:start position:0% about it the proof itself will be 00:11:06.300 --> 00:11:08.150 align:start position:0% about it the proof itself will be invalid<00:11:06.779> and<00:11:07.200> the<00:11:07.320> proof<00:11:07.500> determines<00:11:07.920> what 00:11:08.150 --> 00:11:08.160 align:start position:0% invalid and the proof determines what 00:11:08.160 --> 00:11:10.730 align:start position:0% invalid and the proof determines what the<00:11:08.279> user<00:11:08.579> wants<00:11:08.820> to<00:11:08.880> do<00:11:09.000> on<00:11:09.180> chain 00:11:10.730 --> 00:11:10.740 align:start position:0% the user wants to do on chain 00:11:10.740 --> 00:11:12.889 align:start position:0% the user wants to do on chain so<00:11:11.040> I<00:11:11.100> think<00:11:11.220> a<00:11:11.399> good<00:11:11.519> goal<00:11:11.820> for<00:11:12.000> this<00:11:12.180> would<00:11:12.720> be 00:11:12.889 --> 00:11:12.899 align:start position:0% so I think a good goal for this would be 00:11:12.899 --> 00:11:15.110 align:start position:0% so I think a good goal for this would be uh<00:11:13.680> from<00:11:13.920> a<00:11:14.040> user<00:11:14.279> experience<00:11:14.519> perspective<00:11:14.940> a 00:11:15.110 --> 00:11:15.120 align:start position:0% uh from a user experience perspective a 00:11:15.120 --> 00:11:16.970 align:start position:0% uh from a user experience perspective a user<00:11:15.420> clicks<00:11:15.720> a<00:11:15.839> button<00:11:16.140> and<00:11:16.500> then<00:11:16.620> in<00:11:16.800> less 00:11:16.970 --> 00:11:16.980 align:start position:0% user clicks a button and then in less 00:11:16.980 --> 00:11:18.590 align:start position:0% user clicks a button and then in less than<00:11:17.160> five<00:11:17.459> seconds<00:11:17.700> we<00:11:18.060> show<00:11:18.180> a<00:11:18.360> loading 00:11:18.590 --> 00:11:18.600 align:start position:0% than five seconds we show a loading 00:11:18.600 --> 00:11:20.750 align:start position:0% than five seconds we show a loading animation<00:11:18.899> and<00:11:19.200> we<00:11:19.320> generate<00:11:19.680> a<00:11:20.100> ZK<00:11:20.399> proof 00:11:20.750 --> 00:11:20.760 align:start position:0% animation and we generate a ZK proof 00:11:20.760 --> 00:11:22.730 align:start position:0% animation and we generate a ZK proof give<00:11:20.940> it<00:11:21.120> to<00:11:21.180> the<00:11:21.300> relayer<00:11:21.779> the<00:11:22.140> relay<00:11:22.380> then 00:11:22.730 --> 00:11:22.740 align:start position:0% give it to the relayer the relay then 00:11:22.740 --> 00:11:24.650 align:start position:0% give it to the relayer the relay then packages<00:11:23.160> it<00:11:23.399> into<00:11:23.519> a<00:11:23.760> transaction<00:11:24.120> and<00:11:24.480> gives 00:11:24.650 --> 00:11:24.660 align:start position:0% packages it into a transaction and gives 00:11:24.660 --> 00:11:26.870 align:start position:0% packages it into a transaction and gives it<00:11:24.839> to<00:11:24.959> an<00:11:25.200> L2<00:11:25.560> node<00:11:25.860> who<00:11:26.160> then<00:11:26.339> returns<00:11:26.760> an 00:11:26.870 --> 00:11:26.880 align:start position:0% it to an L2 node who then returns an 00:11:26.880 --> 00:11:28.970 align:start position:0% it to an L2 node who then returns an instant<00:11:27.120> finality<00:11:27.600> guarantee<00:11:28.079> and<00:11:28.740> at<00:11:28.860> that 00:11:28.970 --> 00:11:28.980 align:start position:0% instant finality guarantee and at that 00:11:28.980 --> 00:11:31.430 align:start position:0% instant finality guarantee and at that point<00:11:29.100> we<00:11:29.519> can<00:11:29.700> stop<00:11:30.240> the<00:11:30.839> loading<00:11:31.140> animation 00:11:31.430 --> 00:11:31.440 align:start position:0% point we can stop the loading animation 00:11:31.440 --> 00:11:33.290 align:start position:0% point we can stop the loading animation on<00:11:31.620> the<00:11:31.740> front<00:11:31.860> end<00:11:31.980> and<00:11:32.399> say<00:11:32.579> okay<00:11:33.000> your 00:11:33.290 --> 00:11:33.300 align:start position:0% on the front end and say okay your 00:11:33.300 --> 00:11:35.509 align:start position:0% on the front end and say okay your action<00:11:33.540> is<00:11:33.779> complete<00:11:34.140> and<00:11:34.800> even<00:11:34.920> if<00:11:35.100> we<00:11:35.220> get<00:11:35.339> a 00:11:35.509 --> 00:11:35.519 align:start position:0% action is complete and even if we get a 00:11:35.519 --> 00:11:37.370 align:start position:0% action is complete and even if we get a weak<00:11:35.820> economic<00:11:36.240> guarantee<00:11:36.600> from<00:11:36.839> this<00:11:37.019> L2 00:11:37.370 --> 00:11:37.380 align:start position:0% weak economic guarantee from this L2 00:11:37.380 --> 00:11:39.350 align:start position:0% weak economic guarantee from this L2 node<00:11:37.740> we<00:11:38.220> can<00:11:38.339> still<00:11:38.519> do<00:11:38.820> this<00:11:38.940> on<00:11:39.180> the<00:11:39.240> front 00:11:39.350 --> 00:11:39.360 align:start position:0% node we can still do this on the front 00:11:39.360 --> 00:11:41.509 align:start position:0% node we can still do this on the front end<00:11:39.540> and<00:11:39.899> then<00:11:40.079> have<00:11:40.380> an<00:11:40.680> alternate<00:11:41.040> code<00:11:41.220> path 00:11:41.509 --> 00:11:41.519 align:start position:0% end and then have an alternate code path 00:11:41.519 --> 00:11:43.190 align:start position:0% end and then have an alternate code path where<00:11:41.700> if<00:11:41.940> the<00:11:42.060> sequencer<00:11:42.540> doesn't<00:11:42.839> include 00:11:43.190 --> 00:11:43.200 align:start position:0% where if the sequencer doesn't include 00:11:43.200 --> 00:11:45.230 align:start position:0% where if the sequencer doesn't include the<00:11:43.320> transaction<00:11:43.800> we<00:11:44.459> show<00:11:44.640> a<00:11:44.820> notification 00:11:45.230 --> 00:11:45.240 align:start position:0% the transaction we show a notification 00:11:45.240 --> 00:11:47.630 align:start position:0% the transaction we show a notification saying<00:11:45.720> oh<00:11:46.019> this<00:11:46.500> action<00:11:46.680> failed<00:11:47.040> or<00:11:47.160> do<00:11:47.579> you 00:11:47.630 --> 00:11:47.640 align:start position:0% saying oh this action failed or do you 00:11:47.640 --> 00:11:49.430 align:start position:0% saying oh this action failed or do you want<00:11:47.700> to<00:11:47.820> try<00:11:47.880> again<00:11:48.060> or<00:11:48.360> not<00:11:48.540> and<00:11:49.140> hopefully 00:11:49.430 --> 00:11:49.440 align:start position:0% want to try again or not and hopefully 00:11:49.440 --> 00:11:51.230 align:start position:0% want to try again or not and hopefully that<00:11:49.620> code<00:11:49.740> path<00:11:50.040> is<00:11:50.220> relatively<00:11:50.579> cold<00:11:50.820> and 00:11:51.230 --> 00:11:51.240 align:start position:0% that code path is relatively cold and 00:11:51.240 --> 00:11:53.750 align:start position:0% that code path is relatively cold and sequencers<00:11:52.140> include<00:11:52.920> transactions<00:11:53.459> as<00:11:53.640> they 00:11:53.750 --> 00:11:53.760 align:start position:0% sequencers include transactions as they 00:11:53.760 --> 00:11:56.090 align:start position:0% sequencers include transactions as they say<00:11:53.940> they're<00:11:54.060> going<00:11:54.240> to 00:11:56.090 --> 00:11:56.100 align:start position:0% say they're going to 00:11:56.100 --> 00:11:58.610 align:start position:0% say they're going to right<00:11:56.519> so<00:11:56.760> how<00:11:57.000> can<00:11:57.120> we<00:11:57.360> build<00:11:57.839> an<00:11:58.079> ecosystem 00:11:58.610 --> 00:11:58.620 align:start position:0% right so how can we build an ecosystem 00:11:58.620 --> 00:12:00.889 align:start position:0% right so how can we build an ecosystem using<00:11:59.339> like<00:11:59.579> ZK<00:11:59.940> proofs<00:12:00.300> in<00:12:00.420> this<00:12:00.600> sort<00:12:00.779> of 00:12:00.889 --> 00:12:00.899 align:start position:0% using like ZK proofs in this sort of 00:12:00.899 --> 00:12:02.750 align:start position:0% using like ZK proofs in this sort of abstracted<00:12:01.620> architecture 00:12:02.750 --> 00:12:02.760 align:start position:0% abstracted architecture 00:12:02.760 --> 00:12:05.269 align:start position:0% abstracted architecture uh<00:12:03.480> one<00:12:03.720> approach<00:12:04.019> I<00:12:04.200> think<00:12:04.320> is<00:12:04.800> sort<00:12:05.160> of 00:12:05.269 --> 00:12:05.279 align:start position:0% uh one approach I think is sort of 00:12:05.279 --> 00:12:06.889 align:start position:0% uh one approach I think is sort of detailed<00:12:05.519> in<00:12:05.700> this<00:12:05.820> diagram<00:12:06.060> you<00:12:06.660> can<00:12:06.779> see 00:12:06.889 --> 00:12:06.899 align:start position:0% detailed in this diagram you can see 00:12:06.899 --> 00:12:08.210 align:start position:0% detailed in this diagram you can see there<00:12:07.200> are<00:12:07.320> three<00:12:07.440> different<00:12:07.620> attestra 00:12:08.210 --> 00:12:08.220 align:start position:0% there are three different attestra 00:12:08.220 --> 00:12:11.030 align:start position:0% there are three different attestra applications<00:12:08.640> and<00:12:09.240> a<00:12:09.480> user's<00:12:09.839> browser<00:12:10.260> and 00:12:11.030 --> 00:12:11.040 align:start position:0% applications and a user's browser and 00:12:11.040 --> 00:12:13.550 align:start position:0% applications and a user's browser and each<00:12:11.220> tester<00:12:11.760> application<00:12:12.180> is<00:12:12.480> managing<00:12:13.019> a 00:12:13.550 --> 00:12:13.560 align:start position:0% each tester application is managing a 00:12:13.560 --> 00:12:16.069 align:start position:0% each tester application is managing a unique<00:12:13.800> identity<00:12:14.339> for<00:12:14.820> the<00:12:15.120> user<00:12:15.420> inside<00:12:15.779> of 00:12:16.069 --> 00:12:16.079 align:start position:0% unique identity for the user inside of 00:12:16.079 --> 00:12:18.530 align:start position:0% unique identity for the user inside of the<00:12:16.260> browser<00:12:16.620> local<00:12:16.860> storage<00:12:17.360> and<00:12:18.360> the 00:12:18.530 --> 00:12:18.540 align:start position:0% the browser local storage and the 00:12:18.540 --> 00:12:20.269 align:start position:0% the browser local storage and the advantage<00:12:18.839> to<00:12:19.019> this<00:12:19.140> is<00:12:19.440> we<00:12:19.740> can<00:12:19.860> treat<00:12:20.040> these 00:12:20.269 --> 00:12:20.279 align:start position:0% advantage to this is we can treat these 00:12:20.279 --> 00:12:21.710 align:start position:0% advantage to this is we can treat these identities<00:12:20.700> more<00:12:21.060> like<00:12:21.240> web<00:12:21.480> 2 00:12:21.710 --> 00:12:21.720 align:start position:0% identities more like web 2 00:12:21.720 --> 00:12:23.810 align:start position:0% identities more like web 2 authentication<00:12:22.380> tokens<00:12:22.800> and<00:12:23.339> less<00:12:23.519> like 00:12:23.810 --> 00:12:23.820 align:start position:0% authentication tokens and less like 00:12:23.820 --> 00:12:26.150 align:start position:0% authentication tokens and less like Bitcoin<00:12:24.240> or<00:12:24.420> ethereum<00:12:24.899> private<00:12:25.260> keys<00:12:25.620> so 00:12:26.150 --> 00:12:26.160 align:start position:0% Bitcoin or ethereum private keys so 00:12:26.160 --> 00:12:27.829 align:start position:0% Bitcoin or ethereum private keys so instead<00:12:26.519> of<00:12:26.579> prompting<00:12:27.000> the<00:12:27.120> user<00:12:27.420> for 00:12:27.829 --> 00:12:27.839 align:start position:0% instead of prompting the user for 00:12:27.839 --> 00:12:29.569 align:start position:0% instead of prompting the user for permission<00:12:28.380> to<00:12:28.620> do<00:12:28.740> a<00:12:28.860> signature<00:12:29.220> or<00:12:29.279> make<00:12:29.459> a 00:12:29.569 --> 00:12:29.579 align:start position:0% permission to do a signature or make a 00:12:29.579 --> 00:12:32.350 align:start position:0% permission to do a signature or make a transaction<00:12:29.940> we<00:12:30.660> just<00:12:30.899> in<00:12:31.860> the<00:12:31.980> background 00:12:32.350 --> 00:12:32.360 align:start position:0% transaction we just in the background 00:12:32.360 --> 00:12:34.610 align:start position:0% transaction we just in the background make<00:12:33.360> these<00:12:33.540> ZK<00:12:33.779> proofs<00:12:34.140> and<00:12:34.260> give<00:12:34.380> them<00:12:34.500> to 00:12:34.610 --> 00:12:34.620 align:start position:0% make these ZK proofs and give them to 00:12:34.620 --> 00:12:36.829 align:start position:0% make these ZK proofs and give them to the<00:12:34.740> relayers<00:12:35.220> and<00:12:36.000> at<00:12:36.180> the<00:12:36.300> same<00:12:36.420> time<00:12:36.600> when 00:12:36.829 --> 00:12:36.839 align:start position:0% the relayers and at the same time when 00:12:36.839 --> 00:12:38.389 align:start position:0% the relayers and at the same time when we<00:12:37.019> use<00:12:37.140> different<00:12:37.380> identities<00:12:37.920> for<00:12:38.160> each<00:12:38.279> of 00:12:38.389 --> 00:12:38.399 align:start position:0% we use different identities for each of 00:12:38.399 --> 00:12:40.370 align:start position:0% we use different identities for each of these<00:12:38.519> websites<00:12:39.000> if<00:12:39.660> one<00:12:39.779> of<00:12:39.899> the<00:12:40.019> identities 00:12:40.370 --> 00:12:40.380 align:start position:0% these websites if one of the identities 00:12:40.380 --> 00:12:41.990 align:start position:0% these websites if one of the identities is<00:12:40.680> compromised<00:12:41.220> because<00:12:41.339> the<00:12:41.640> website 00:12:41.990 --> 00:12:42.000 align:start position:0% is compromised because the website 00:12:42.000 --> 00:12:43.610 align:start position:0% is compromised because the website injects<00:12:42.360> some<00:12:42.480> malicious<00:12:42.839> JavaScript<00:12:43.260> or 00:12:43.610 --> 00:12:43.620 align:start position:0% injects some malicious JavaScript or 00:12:43.620 --> 00:12:46.129 align:start position:0% injects some malicious JavaScript or does<00:12:43.920> something<00:12:44.160> like<00:12:44.339> this<00:12:44.720> the<00:12:45.720> damage<00:12:45.959> is 00:12:46.129 --> 00:12:46.139 align:start position:0% does something like this the damage is 00:12:46.139 --> 00:12:49.430 align:start position:0% does something like this the damage is contained<00:12:46.680> to<00:12:47.040> that<00:12:47.399> single<00:12:47.760> a<00:12:48.000> tester 00:12:49.430 --> 00:12:49.440 align:start position:0% contained to that single a tester 00:12:49.440 --> 00:12:51.350 align:start position:0% contained to that single a tester but<00:12:49.980> at<00:12:50.160> the<00:12:50.279> same<00:12:50.399> time<00:12:50.519> we<00:12:50.760> want<00:12:50.880> a<00:12:51.060> testers 00:12:51.350 --> 00:12:51.360 align:start position:0% but at the same time we want a testers 00:12:51.360 --> 00:12:53.930 align:start position:0% but at the same time we want a testers to<00:12:51.540> be<00:12:51.660> interoperable<00:12:52.139> so<00:12:52.920> if<00:12:53.519> for<00:12:53.700> example 00:12:53.930 --> 00:12:53.940 align:start position:0% to be interoperable so if for example 00:12:53.940 --> 00:12:55.910 align:start position:0% to be interoperable so if for example this<00:12:54.240> to<00:12:54.420> review<00:12:54.540> a<00:12:54.779> tester<00:12:55.079> wanted<00:12:55.380> to<00:12:55.560> get<00:12:55.740> a 00:12:55.910 --> 00:12:55.920 align:start position:0% this to review a tester wanted to get a 00:12:55.920 --> 00:12:57.949 align:start position:0% this to review a tester wanted to get a proof<00:12:56.220> of<00:12:56.639> from<00:12:57.120> the<00:12:57.180> Cyber<00:12:57.540> resistance 00:12:57.949 --> 00:12:57.959 align:start position:0% proof of from the Cyber resistance 00:12:57.959 --> 00:13:00.590 align:start position:0% proof of from the Cyber resistance tester<00:12:58.440> how<00:12:58.860> could<00:12:58.980> we<00:12:59.100> do<00:12:59.279> that<00:12:59.459> and<00:13:00.360> the 00:13:00.590 --> 00:13:00.600 align:start position:0% tester how could we do that and the 00:13:00.600 --> 00:13:03.889 align:start position:0% tester how could we do that and the answer<00:13:00.779> is<00:13:01.320> basically<00:13:02.040> oauth<00:13:02.519> for<00:13:02.760> ZK<00:13:03.060> so<00:13:03.720> for 00:13:03.889 --> 00:13:03.899 align:start position:0% answer is basically oauth for ZK so for 00:13:03.899 --> 00:13:05.930 align:start position:0% answer is basically oauth for ZK so for so<00:13:04.139> in<00:13:04.320> this<00:13:04.500> example<00:13:04.800> flow<00:13:05.100> I'm<00:13:05.639> trying<00:13:05.820> to 00:13:05.930 --> 00:13:05.940 align:start position:0% so in this example flow I'm trying to 00:13:05.940 --> 00:13:08.389 align:start position:0% so in this example flow I'm trying to sign<00:13:06.120> up<00:13:06.300> for<00:13:06.540> this<00:13:06.720> review<00:13:06.959> a<00:13:07.260> tester<00:13:07.620> and<00:13:08.279> the 00:13:08.389 --> 00:13:08.399 align:start position:0% sign up for this review a tester and the 00:13:08.399 --> 00:13:10.550 align:start position:0% sign up for this review a tester and the reviewer<00:13:08.760> tester<00:13:09.000> wants<00:13:09.420> a<00:13:09.540> proof<00:13:09.839> that<00:13:10.019> I<00:13:10.320> am 00:13:10.550 --> 00:13:10.560 align:start position:0% reviewer tester wants a proof that I am 00:13:10.560 --> 00:13:12.949 align:start position:0% reviewer tester wants a proof that I am a<00:13:10.800> human<00:13:10.920> being<00:13:11.360> in<00:13:12.360> the<00:13:12.480> form<00:13:12.600> of<00:13:12.839> a 00:13:12.949 --> 00:13:12.959 align:start position:0% a human being in the form of a 00:13:12.959 --> 00:13:14.870 align:start position:0% a human being in the form of a reputation<00:13:13.380> proof<00:13:13.740> from<00:13:13.980> this<00:13:14.220> cyber 00:13:14.870 --> 00:13:14.880 align:start position:0% reputation proof from this cyber 00:13:14.880 --> 00:13:17.210 align:start position:0% reputation proof from this cyber resistance<00:13:15.240> attester<00:13:15.720> and<00:13:16.500> so<00:13:16.620> in<00:13:16.800> this<00:13:16.920> flow 00:13:17.210 --> 00:13:17.220 align:start position:0% resistance attester and so in this flow 00:13:17.220 --> 00:13:19.250 align:start position:0% resistance attester and so in this flow I<00:13:17.820> create<00:13:17.940> the<00:13:18.120> sine<00:13:18.360> of<00:13:18.480> proof<00:13:18.720> from<00:13:19.139> the 00:13:19.250 --> 00:13:19.260 align:start position:0% I create the sine of proof from the 00:13:19.260 --> 00:13:20.690 align:start position:0% I create the sine of proof from the reviewer<00:13:19.560> tester<00:13:19.860> and<00:13:20.339> then<00:13:20.459> I<00:13:20.579> get 00:13:20.690 --> 00:13:20.700 align:start position:0% reviewer tester and then I get 00:13:20.700 --> 00:13:22.670 align:start position:0% reviewer tester and then I get redirected<00:13:21.300> to<00:13:21.660> the<00:13:21.779> Cyber<00:13:22.139> resistance<00:13:22.560> to 00:13:22.670 --> 00:13:22.680 align:start position:0% redirected to the Cyber resistance to 00:13:22.680 --> 00:13:25.610 align:start position:0% redirected to the Cyber resistance to tester<00:13:23.040> and<00:13:23.339> I<00:13:23.579> get<00:13:23.700> prompted<00:13:24.180> to<00:13:24.540> make<00:13:25.380> a 00:13:25.610 --> 00:13:25.620 align:start position:0% tester and I get prompted to make a 00:13:25.620 --> 00:13:28.490 align:start position:0% tester and I get prompted to make a proof<00:13:25.860> from<00:13:26.639> this<00:13:27.000> identity<00:13:27.480> and<00:13:28.260> in<00:13:28.380> this 00:13:28.490 --> 00:13:28.500 align:start position:0% proof from this identity and in this 00:13:28.500 --> 00:13:30.050 align:start position:0% proof from this identity and in this case<00:13:28.620> we<00:13:28.860> shouldn't<00:13:29.100> operate<00:13:29.399> silently<00:13:29.760> we 00:13:30.050 --> 00:13:30.060 align:start position:0% case we shouldn't operate silently we 00:13:30.060 --> 00:13:32.329 align:start position:0% case we shouldn't operate silently we should<00:13:30.180> definitely<00:13:30.620> request<00:13:31.620> that<00:13:31.860> the<00:13:32.040> user 00:13:32.329 --> 00:13:32.339 align:start position:0% should definitely request that the user 00:13:32.339 --> 00:13:33.710 align:start position:0% should definitely request that the user Make<00:13:32.519> This<00:13:32.700> proof<00:13:33.000> because<00:13:33.180> we're<00:13:33.480> going<00:13:33.660> to 00:13:33.710 --> 00:13:33.720 align:start position:0% Make This proof because we're going to 00:13:33.720 --> 00:13:36.230 align:start position:0% Make This proof because we're going to hand<00:13:33.839> it<00:13:34.019> to<00:13:34.200> a<00:13:34.620> different<00:13:34.740> third<00:13:34.980> party<00:13:35.240> and 00:13:36.230 --> 00:13:36.240 align:start position:0% hand it to a different third party and 00:13:36.240 --> 00:13:37.850 align:start position:0% hand it to a different third party and so<00:13:36.360> if<00:13:36.480> the<00:13:36.540> user<00:13:36.779> says<00:13:36.959> yes<00:13:37.079> then<00:13:37.320> we<00:13:37.500> prove 00:13:37.850 --> 00:13:37.860 align:start position:0% so if the user says yes then we prove 00:13:37.860 --> 00:13:40.009 align:start position:0% so if the user says yes then we prove that<00:13:38.100> we<00:13:38.220> have<00:13:38.339> like<00:13:38.459> the<00:13:38.639> reputation<00:13:39.120> and<00:13:39.779> we 00:13:40.009 --> 00:13:40.019 align:start position:0% that we have like the reputation and we 00:13:40.019 --> 00:13:41.690 align:start position:0% that we have like the reputation and we sign<00:13:40.200> the<00:13:40.440> hash<00:13:40.680> of<00:13:40.860> the<00:13:41.100> sign<00:13:41.220> up<00:13:41.399> proof<00:13:41.639> to 00:13:41.690 --> 00:13:41.700 align:start position:0% sign the hash of the sign up proof to 00:13:41.700 --> 00:13:43.310 align:start position:0% sign the hash of the sign up proof to prove<00:13:41.880> that<00:13:42.000> we're<00:13:42.180> the<00:13:42.360> same<00:13:42.480> person<00:13:42.660> and 00:13:43.310 --> 00:13:43.320 align:start position:0% prove that we're the same person and 00:13:43.320 --> 00:13:45.290 align:start position:0% prove that we're the same person and then<00:13:43.380> we<00:13:43.500> get<00:13:43.620> redirected<00:13:44.160> back<00:13:44.459> to<00:13:44.760> the<00:13:45.120> the 00:13:45.290 --> 00:13:45.300 align:start position:0% then we get redirected back to the the 00:13:45.300 --> 00:13:46.790 align:start position:0% then we get redirected back to the the original<00:13:45.540> application<00:13:46.139> and<00:13:46.380> we<00:13:46.560> can<00:13:46.620> continue 00:13:46.790 --> 00:13:46.800 align:start position:0% original application and we can continue 00:13:46.800 --> 00:13:50.210 align:start position:0% original application and we can continue sign<00:13:47.160> up<00:13:47.339> so<00:13:48.000> using<00:13:48.420> this<00:13:48.540> flow<00:13:48.839> we<00:13:49.019> can<00:13:49.139> get<00:13:49.380> ZK 00:13:50.210 --> 00:13:50.220 align:start position:0% sign up so using this flow we can get ZK 00:13:50.220 --> 00:13:52.250 align:start position:0% sign up so using this flow we can get ZK proofs<00:13:50.700> from<00:13:50.940> different<00:13:51.120> applications<00:13:51.720> into 00:13:52.250 --> 00:13:52.260 align:start position:0% proofs from different applications into 00:13:52.260 --> 00:13:55.670 align:start position:0% proofs from different applications into different<00:13:52.740> sort<00:13:53.100> of<00:13:53.220> Origins 00:13:55.670 --> 00:13:55.680 align:start position:0% different sort of Origins 00:13:55.680 --> 00:13:57.710 align:start position:0% different sort of Origins okay<00:13:56.100> so<00:13:56.579> this<00:13:56.940> is<00:13:57.120> part<00:13:57.300> three<00:13:57.540> of<00:13:57.660> the 00:13:57.710 --> 00:13:57.720 align:start position:0% okay so this is part three of the 00:13:57.720 --> 00:13:58.910 align:start position:0% okay so this is part three of the presentation 00:13:58.910 --> 00:13:58.920 align:start position:0% presentation 00:13:58.920 --> 00:14:02.030 align:start position:0% presentation um how<00:13:59.459> can<00:13:59.579> we<00:13:59.760> scale<00:14:00.120> ZK<00:14:00.600> so<00:14:01.440> first<00:14:01.620> I<00:14:01.920> want 00:14:02.030 --> 00:14:02.040 align:start position:0% um how can we scale ZK so first I want 00:14:02.040 --> 00:14:03.829 align:start position:0% um how can we scale ZK so first I want to<00:14:02.160> talk<00:14:02.279> about<00:14:02.459> uh<00:14:03.180> like<00:14:03.300> where<00:14:03.540> we're<00:14:03.660> at 00:14:03.829 --> 00:14:03.839 align:start position:0% to talk about uh like where we're at 00:14:03.839 --> 00:14:06.829 align:start position:0% to talk about uh like where we're at right<00:14:04.079> now<00:14:04.260> and<00:14:04.740> the<00:14:04.920> limitations<00:14:05.279> of<00:14:05.839> our 00:14:06.829 --> 00:14:06.839 align:start position:0% right now and the limitations of our 00:14:06.839 --> 00:14:08.690 align:start position:0% right now and the limitations of our current<00:14:07.019> infrastructure<00:14:08.160> so<00:14:08.399> when<00:14:08.459> we<00:14:08.579> talk 00:14:08.690 --> 00:14:08.700 align:start position:0% current infrastructure so when we talk 00:14:08.700 --> 00:14:11.090 align:start position:0% current infrastructure so when we talk about<00:14:08.820> scaling<00:14:09.120> ZK<00:14:09.420> there's<00:14:09.899> two<00:14:10.500> limitations 00:14:11.090 --> 00:14:11.100 align:start position:0% about scaling ZK there's two limitations 00:14:11.100 --> 00:14:13.730 align:start position:0% about scaling ZK there's two limitations one<00:14:11.760> is<00:14:11.940> the<00:14:12.180> the<00:14:12.300> call<00:14:12.480> data<00:14:12.899> itself<00:14:13.079> and<00:14:13.560> two 00:14:13.730 --> 00:14:13.740 align:start position:0% one is the the call data itself and two 00:14:13.740 --> 00:14:15.410 align:start position:0% one is the the call data itself and two is<00:14:13.920> actually<00:14:14.160> executing<00:14:14.760> the<00:14:14.880> verification 00:14:15.410 --> 00:14:15.420 align:start position:0% is actually executing the verification 00:14:15.420 --> 00:14:18.350 align:start position:0% is actually executing the verification on<00:14:15.959> chain<00:14:16.860> so<00:14:17.339> let's<00:14:17.459> talk<00:14:17.639> about<00:14:17.700> call<00:14:17.940> data 00:14:18.350 --> 00:14:18.360 align:start position:0% on chain so let's talk about call data 00:14:18.360 --> 00:14:22.190 align:start position:0% on chain so let's talk about call data first<00:14:18.540> so<00:14:19.380> for<00:14:19.680> graph<00:14:19.980> 16<00:14:20.220> we<00:14:21.120> have<00:14:21.240> about<00:14:21.360> 130 00:14:22.190 --> 00:14:22.200 align:start position:0% first so for graph 16 we have about 130 00:14:22.200 --> 00:14:24.350 align:start position:0% first so for graph 16 we have about 130 bytes<00:14:22.620> per<00:14:23.040> proof<00:14:23.399> and<00:14:23.639> for<00:14:23.760> plonk<00:14:24.180> we<00:14:24.240> have 00:14:24.350 --> 00:14:24.360 align:start position:0% bytes per proof and for plonk we have 00:14:24.360 --> 00:14:26.930 align:start position:0% bytes per proof and for plonk we have about<00:14:24.480> half<00:14:24.720> a<00:14:24.899> kilobyte<00:14:25.380> per<00:14:25.740> proof<00:14:26.160> so 00:14:26.930 --> 00:14:26.940 align:start position:0% about half a kilobyte per proof so 00:14:26.940 --> 00:14:28.850 align:start position:0% about half a kilobyte per proof so assume<00:14:27.360> that<00:14:27.420> we're<00:14:27.600> talking<00:14:27.720> about<00:14:27.959> EIP<00:14:28.440> like 00:14:28.850 --> 00:14:28.860 align:start position:0% assume that we're talking about EIP like 00:14:28.860 --> 00:14:31.850 align:start position:0% assume that we're talking about EIP like a<00:14:28.980> post<00:14:29.240> eip4844<00:14:30.240> world<00:14:30.600> and<00:14:31.260> we<00:14:31.380> have<00:14:31.560> two 00:14:31.850 --> 00:14:31.860 align:start position:0% a post eip4844 world and we have two 00:14:31.860 --> 00:14:33.949 align:start position:0% a post eip4844 world and we have two megabytes<00:14:32.399> per<00:14:32.579> block<00:14:32.820> that<00:14:33.240> we<00:14:33.360> can<00:14:33.480> use<00:14:33.600> for 00:14:33.949 --> 00:14:33.959 align:start position:0% megabytes per block that we can use for 00:14:33.959 --> 00:14:36.650 align:start position:0% megabytes per block that we can use for blob<00:14:34.320> data<00:14:34.740> so<00:14:35.399> at<00:14:35.519> that<00:14:35.700> point<00:14:35.880> we're<00:14:36.300> able<00:14:36.540> to 00:14:36.650 --> 00:14:36.660 align:start position:0% blob data so at that point we're able to 00:14:36.660 --> 00:14:39.410 align:start position:0% blob data so at that point we're able to do<00:14:36.779> 1300<00:14:37.380> across<00:14:37.860> 16<00:14:38.040> fruits<00:14:38.459> per<00:14:38.579> second<00:14:38.760> and 00:14:39.410 --> 00:14:39.420 align:start position:0% do 1300 across 16 fruits per second and 00:14:39.420 --> 00:14:42.170 align:start position:0% do 1300 across 16 fruits per second and 330<00:14:40.139> plonkers<00:14:40.980> per<00:14:41.220> second 00:14:42.170 --> 00:14:42.180 align:start position:0% 330 plonkers per second 00:14:42.180 --> 00:14:44.389 align:start position:0% 330 plonkers per second uh<00:14:42.779> it's<00:14:42.959> not<00:14:43.199> not<00:14:43.380> terrible<00:14:43.740> so<00:14:44.100> let's<00:14:44.220> open 00:14:44.389 --> 00:14:44.399 align:start position:0% uh it's not not terrible so let's open 00:14:44.399 --> 00:14:45.710 align:start position:0% uh it's not not terrible so let's open door<00:14:44.639> number<00:14:44.880> two<00:14:45.060> and<00:14:45.180> look<00:14:45.360> at<00:14:45.480> the 00:14:45.710 --> 00:14:45.720 align:start position:0% door number two and look at the 00:14:45.720 --> 00:14:47.810 align:start position:0% door number two and look at the verification<00:14:46.139> costs 00:14:47.810 --> 00:14:47.820 align:start position:0% verification costs 00:14:47.820 --> 00:14:49.790 align:start position:0% verification costs so<00:14:48.120> across<00:14:48.480> 16<00:14:48.600> of<00:14:48.839> Planck<00:14:49.199> both<00:14:49.380> cost<00:14:49.560> about 00:14:49.790 --> 00:14:49.800 align:start position:0% so across 16 of Planck both cost about 00:14:49.800 --> 00:14:52.129 align:start position:0% so across 16 of Planck both cost about 250<00:14:50.579> 000<00:14:50.699> gas<00:14:50.880> to<00:14:51.120> verify 00:14:52.129 --> 00:14:52.139 align:start position:0% 250 000 gas to verify 00:14:52.139 --> 00:14:54.230 align:start position:0% 250 000 gas to verify this<00:14:52.560> isn't<00:14:52.800> totally<00:14:52.980> true<00:14:53.220> cross<00:14:53.579> 16<00:14:53.820> is<00:14:54.060> a 00:14:54.230 --> 00:14:54.240 align:start position:0% this isn't totally true cross 16 is a 00:14:54.240 --> 00:14:55.550 align:start position:0% this isn't totally true cross 16 is a little<00:14:54.300> bit<00:14:54.420> cheaper<00:14:54.720> and<00:14:54.959> they<00:14:55.079> both<00:14:55.260> scale 00:14:55.550 --> 00:14:55.560 align:start position:0% little bit cheaper and they both scale 00:14:55.560 --> 00:14:56.990 align:start position:0% little bit cheaper and they both scale up<00:14:55.680> with<00:14:55.920> the<00:14:56.040> number<00:14:56.160> of<00:14:56.279> public<00:14:56.459> signals<00:14:56.940> in 00:14:56.990 --> 00:14:57.000 align:start position:0% up with the number of public signals in 00:14:57.000 --> 00:14:59.150 align:start position:0% up with the number of public signals in the<00:14:57.180> proof<00:14:57.420> but<00:14:57.899> for<00:14:58.260> this<00:14:58.500> example<00:14:58.800> we're 00:14:59.150 --> 00:14:59.160 align:start position:0% the proof but for this example we're 00:14:59.160 --> 00:15:00.949 align:start position:0% the proof but for this example we're just<00:14:59.279> going<00:14:59.399> to<00:14:59.519> say<00:14:59.579> they<00:14:59.760> both<00:14:59.940> cost<00:15:00.120> 250 00:15:00.949 --> 00:15:00.959 align:start position:0% just going to say they both cost 250 00:15:00.959 --> 00:15:02.090 align:start position:0% just going to say they both cost 250 000. 00:15:02.090 --> 00:15:02.100 align:start position:0% 000. 00:15:02.100 --> 00:15:03.949 align:start position:0% 000. so<00:15:02.279> the<00:15:02.459> ethereum<00:15:02.820> maina<00:15:03.180> is<00:15:03.300> doing<00:15:03.420> two<00:15:03.720> and<00:15:03.839> a 00:15:03.949 --> 00:15:03.959 align:start position:0% so the ethereum maina is doing two and a 00:15:03.959 --> 00:15:05.509 align:start position:0% so the ethereum maina is doing two and a half<00:15:04.019> million<00:15:04.440> gas<00:15:04.620> per<00:15:04.860> second<00:15:05.040> right<00:15:05.399> now 00:15:05.509 --> 00:15:05.519 align:start position:0% half million gas per second right now 00:15:05.519 --> 00:15:08.389 align:start position:0% half million gas per second right now they're<00:15:06.000> doing<00:15:06.300> uh<00:15:07.260> 30<00:15:07.440> million<00:15:07.740> gas<00:15:07.920> every<00:15:08.160> 12 00:15:08.389 --> 00:15:08.399 align:start position:0% they're doing uh 30 million gas every 12 00:15:08.399 --> 00:15:10.129 align:start position:0% they're doing uh 30 million gas every 12 seconds<00:15:08.579> which<00:15:08.820> comes<00:15:09.060> down<00:15:09.180> to<00:15:09.300> this<00:15:09.540> so<00:15:09.899> it 00:15:10.129 --> 00:15:10.139 align:start position:0% seconds which comes down to this so it 00:15:10.139 --> 00:15:12.230 align:start position:0% seconds which comes down to this so it gets<00:15:10.440> to<00:15:10.500> verify<00:15:10.920> 10<00:15:11.279> proofs<00:15:11.699> per<00:15:11.820> second<00:15:12.000> on 00:15:12.230 --> 00:15:12.240 align:start position:0% gets to verify 10 proofs per second on 00:15:12.240 --> 00:15:13.730 align:start position:0% gets to verify 10 proofs per second on ethereum<00:15:12.660> Main<00:15:12.839> net 00:15:13.730 --> 00:15:13.740 align:start position:0% ethereum Main net 00:15:13.740 --> 00:15:15.889 align:start position:0% ethereum Main net so<00:15:14.339> on<00:15:14.519> arbitrum<00:15:15.000> and<00:15:15.120> L2<00:15:15.420> for<00:15:15.720> example 00:15:15.889 --> 00:15:15.899 align:start position:0% so on arbitrum and L2 for example 00:15:15.899 --> 00:15:17.629 align:start position:0% so on arbitrum and L2 for example they're<00:15:16.320> doing<00:15:16.500> 7<00:15:16.740> million<00:15:17.040> gas<00:15:17.220> per<00:15:17.459> second 00:15:17.629 --> 00:15:17.639 align:start position:0% they're doing 7 million gas per second 00:15:17.639 --> 00:15:20.389 align:start position:0% they're doing 7 million gas per second so<00:15:18.180> that<00:15:18.360> number<00:15:18.540> is<00:15:18.720> bumped<00:15:19.139> to<00:15:19.199> 24<00:15:19.860> proofs 00:15:20.389 --> 00:15:20.399 align:start position:0% so that number is bumped to 24 proofs 00:15:20.399 --> 00:15:21.769 align:start position:0% so that number is bumped to 24 proofs per<00:15:20.519> second 00:15:21.769 --> 00:15:21.779 align:start position:0% per second 00:15:21.779 --> 00:15:23.689 align:start position:0% per second so<00:15:22.320> we<00:15:22.620> see<00:15:22.680> an<00:15:22.860> obvious<00:15:23.100> bottleneck<00:15:23.459> here 00:15:23.689 --> 00:15:23.699 align:start position:0% so we see an obvious bottleneck here 00:15:23.699 --> 00:15:26.569 align:start position:0% so we see an obvious bottleneck here it's<00:15:24.000> the<00:15:24.240> verification<00:15:24.660> cost<00:15:25.079> on<00:15:25.620> chain<00:15:25.860> uh 00:15:26.569 --> 00:15:26.579 align:start position:0% it's the verification cost on chain uh 00:15:26.579 --> 00:15:28.310 align:start position:0% it's the verification cost on chain uh and<00:15:26.699> these<00:15:26.880> numbers<00:15:27.000> are<00:15:27.300> also<00:15:27.600> extreme<00:15:27.959> upper 00:15:28.310 --> 00:15:28.320 align:start position:0% and these numbers are also extreme upper 00:15:28.320 --> 00:15:29.629 align:start position:0% and these numbers are also extreme upper bounds<00:15:28.620> this<00:15:28.740> assumes<00:15:29.100> that<00:15:29.160> we're<00:15:29.279> filling 00:15:29.629 --> 00:15:29.639 align:start position:0% bounds this assumes that we're filling 00:15:29.639 --> 00:15:32.750 align:start position:0% bounds this assumes that we're filling entire<00:15:30.199> uh<00:15:31.199> The<00:15:31.740> Blob<00:15:32.040> blocks<00:15:32.459> with<00:15:32.579> two 00:15:32.750 --> 00:15:32.760 align:start position:0% entire uh The Blob blocks with two 00:15:32.760 --> 00:15:34.970 align:start position:0% entire uh The Blob blocks with two megabytes<00:15:33.480> of<00:15:33.600> ZK<00:15:33.899> proofs<00:15:34.260> and<00:15:34.560> we're<00:15:34.680> filling 00:15:34.970 --> 00:15:34.980 align:start position:0% megabytes of ZK proofs and we're filling 00:15:34.980 --> 00:15:37.490 align:start position:0% megabytes of ZK proofs and we're filling entire<00:15:35.220> blocks<00:15:35.639> with<00:15:36.000> verification<00:15:36.600> of<00:15:37.199> ZK 00:15:37.490 --> 00:15:37.500 align:start position:0% entire blocks with verification of ZK 00:15:37.500 --> 00:15:40.129 align:start position:0% entire blocks with verification of ZK proofs<00:15:37.920> and<00:15:38.040> not<00:15:38.160> even<00:15:38.279> factoring<00:15:38.760> call<00:15:38.880> data 00:15:40.129 --> 00:15:40.139 align:start position:0% proofs and not even factoring call data 00:15:40.139 --> 00:15:42.170 align:start position:0% proofs and not even factoring call data all<00:15:40.500> right<00:15:40.500> so<00:15:40.800> how<00:15:40.980> can<00:15:41.160> we<00:15:41.339> scale<00:15:41.699> unit<00:15:41.880> up 00:15:42.170 --> 00:15:42.180 align:start position:0% all right so how can we scale unit up 00:15:42.180 --> 00:15:43.790 align:start position:0% all right so how can we scale unit up and<00:15:42.300> how<00:15:42.420> can<00:15:42.480> we<00:15:42.600> scale<00:15:42.779> ZK<00:15:43.260> proofs<00:15:43.680> in 00:15:43.790 --> 00:15:43.800 align:start position:0% and how can we scale ZK proofs in 00:15:43.800 --> 00:15:46.670 align:start position:0% and how can we scale ZK proofs in general<00:15:43.920> given<00:15:44.639> those<00:15:44.940> bottlenecks 00:15:46.670 --> 00:15:46.680 align:start position:0% general given those bottlenecks 00:15:46.680 --> 00:15:49.610 align:start position:0% general given those bottlenecks so<00:15:47.220> this<00:15:47.579> is<00:15:47.699> a<00:15:48.180> proof<00:15:48.720> from<00:15:48.959> the<00:15:49.019> U<00:15:49.139> interrupt 00:15:49.610 --> 00:15:49.620 align:start position:0% so this is a proof from the U interrupt 00:15:49.620 --> 00:15:51.410 align:start position:0% so this is a proof from the U interrupt system<00:15:49.740> where<00:15:50.399> we're<00:15:50.579> generating<00:15:50.940> a<00:15:51.120> user 00:15:51.410 --> 00:15:51.420 align:start position:0% system where we're generating a user 00:15:51.420 --> 00:15:53.329 align:start position:0% system where we're generating a user State<00:15:51.600> transition<00:15:52.019> and<00:15:52.800> as<00:15:52.980> you<00:15:53.160> can<00:15:53.220> see 00:15:53.329 --> 00:15:53.339 align:start position:0% State transition and as you can see 00:15:53.339 --> 00:15:55.790 align:start position:0% State transition and as you can see there's<00:15:53.760> I<00:15:54.060> think<00:15:54.180> seven<00:15:54.420> public<00:15:54.720> signals<00:15:55.260> and 00:15:55.790 --> 00:15:55.800 align:start position:0% there's I think seven public signals and 00:15:55.800 --> 00:15:57.230 align:start position:0% there's I think seven public signals and for<00:15:55.980> every<00:15:56.100> user<00:15:56.459> that<00:15:56.639> wants<00:15:56.820> to<00:15:56.880> join<00:15:57.000> a<00:15:57.120> new 00:15:57.230 --> 00:15:57.240 align:start position:0% for every user that wants to join a new 00:15:57.240 --> 00:15:58.790 align:start position:0% for every user that wants to join a new Epoch<00:15:57.720> we<00:15:57.779> make<00:15:57.959> one<00:15:58.079> of<00:15:58.260> these<00:15:58.320> and<00:15:58.440> put<00:15:58.620> it<00:15:58.680> on 00:15:58.790 --> 00:15:58.800 align:start position:0% Epoch we make one of these and put it on 00:15:58.800 --> 00:16:01.189 align:start position:0% Epoch we make one of these and put it on the<00:15:58.860> blockchain<00:15:59.279> and<00:15:59.459> verify<00:15:59.880> it<00:16:00.420> so<00:16:00.899> how<00:16:01.079> can 00:16:01.189 --> 00:16:01.199 align:start position:0% the blockchain and verify it so how can 00:16:01.199 --> 00:16:03.170 align:start position:0% the blockchain and verify it so how can we<00:16:01.320> make<00:16:01.440> this<00:16:01.560> a<00:16:01.680> little<00:16:01.740> bit<00:16:01.920> more<00:16:02.100> efficient 00:16:03.170 --> 00:16:03.180 align:start position:0% we make this a little bit more efficient 00:16:03.180 --> 00:16:05.509 align:start position:0% we make this a little bit more efficient we<00:16:03.600> can<00:16:03.660> do<00:16:03.779> recursive<00:16:04.440> proofs<00:16:04.800> so<00:16:05.160> we<00:16:05.399> have 00:16:05.509 --> 00:16:05.519 align:start position:0% we can do recursive proofs so we have 00:16:05.519 --> 00:16:07.430 align:start position:0% we can do recursive proofs so we have the<00:16:05.699> users<00:16:06.000> make<00:16:06.180> a<00:16:06.360> proof<00:16:06.600> and<00:16:06.959> then<00:16:07.079> it<00:16:07.199> gets 00:16:07.430 --> 00:16:07.440 align:start position:0% the users make a proof and then it gets 00:16:07.440 --> 00:16:08.990 align:start position:0% the users make a proof and then it gets sent<00:16:07.500> to<00:16:07.620> an<00:16:07.800> aggregator<00:16:08.160> and<00:16:08.760> then<00:16:08.820> the 00:16:08.990 --> 00:16:09.000 align:start position:0% sent to an aggregator and then the 00:16:09.000 --> 00:16:11.329 align:start position:0% sent to an aggregator and then the aggregator<00:16:09.420> proves<00:16:09.959> that<00:16:10.260> four<00:16:10.620> proofs<00:16:11.040> are 00:16:11.329 --> 00:16:11.339 align:start position:0% aggregator proves that four proofs are 00:16:11.339 --> 00:16:13.550 align:start position:0% aggregator proves that four proofs are valid<00:16:11.699> and<00:16:11.880> outputs<00:16:12.360> one<00:16:12.540> proof<00:16:12.959> and<00:16:13.320> so<00:16:13.440> we're 00:16:13.550 --> 00:16:13.560 align:start position:0% valid and outputs one proof and so we're 00:16:13.560 --> 00:16:15.530 align:start position:0% valid and outputs one proof and so we're able<00:16:13.800> to<00:16:13.860> reduce<00:16:14.040> it<00:16:14.339> by<00:16:14.579> in<00:16:15.060> this<00:16:15.180> case<00:16:15.300> a 00:16:15.530 --> 00:16:15.540 align:start position:0% able to reduce it by in this case a 00:16:15.540 --> 00:16:16.790 align:start position:0% able to reduce it by in this case a factor<00:16:15.899> of<00:16:16.019> four 00:16:16.790 --> 00:16:16.800 align:start position:0% factor of four 00:16:16.800 --> 00:16:18.889 align:start position:0% factor of four there<00:16:17.279> are<00:16:17.459> other<00:16:17.519> things<00:16:17.760> we<00:16:17.940> can<00:16:18.120> do<00:16:18.240> like<00:16:18.600> to 00:16:18.889 --> 00:16:18.899 align:start position:0% there are other things we can do like to 00:16:18.899 --> 00:16:20.629 align:start position:0% there are other things we can do like to reduce<00:16:19.019> the<00:16:19.380> public<00:16:19.500> signals<00:16:19.980> as<00:16:20.100> well<00:16:20.279> like 00:16:20.629 --> 00:16:20.639 align:start position:0% reduce the public signals as well like 00:16:20.639 --> 00:16:22.730 align:start position:0% reduce the public signals as well like cue<00:16:21.000> the<00:16:21.120> ZK<00:16:21.360> proofs<00:16:21.720> on<00:16:21.839> chain<00:16:21.959> and<00:16:22.500> then<00:16:22.560> form 00:16:22.730 --> 00:16:22.740 align:start position:0% cue the ZK proofs on chain and then form 00:16:22.740 --> 00:16:24.410 align:start position:0% cue the ZK proofs on chain and then form a<00:16:22.920> hash<00:16:23.040> chain<00:16:23.279> of<00:16:23.579> the<00:16:23.699> public<00:16:23.820> signals<00:16:24.300> and 00:16:24.410 --> 00:16:24.420 align:start position:0% a hash chain of the public signals and 00:16:24.420 --> 00:16:26.810 align:start position:0% a hash chain of the public signals and the<00:16:24.600> proof<00:16:25.079> stuff<00:16:25.260> uh<00:16:25.980> to<00:16:26.160> reduce<00:16:26.279> it<00:16:26.519> so<00:16:26.639> that 00:16:26.810 --> 00:16:26.820 align:start position:0% the proof stuff uh to reduce it so that 00:16:26.820 --> 00:16:28.250 align:start position:0% the proof stuff uh to reduce it so that we<00:16:26.940> don't<00:16:27.060> have<00:16:27.180> to<00:16:27.300> Output<00:16:27.600> all<00:16:27.899> these<00:16:28.079> public 00:16:28.250 --> 00:16:28.260 align:start position:0% we don't have to Output all these public 00:16:28.260 --> 00:16:29.750 align:start position:0% we don't have to Output all these public signals<00:16:28.740> at<00:16:28.860> once 00:16:29.750 --> 00:16:29.760 align:start position:0% signals at once 00:16:29.760 --> 00:16:31.250 align:start position:0% signals at once which<00:16:30.060> will<00:16:30.240> also<00:16:30.480> reduce<00:16:30.600> the<00:16:30.839> verification 00:16:31.250 --> 00:16:31.260 align:start position:0% which will also reduce the verification 00:16:31.260 --> 00:16:32.210 align:start position:0% which will also reduce the verification cost 00:16:32.210 --> 00:16:32.220 align:start position:0% cost 00:16:32.220 --> 00:16:33.829 align:start position:0% cost and<00:16:32.519> so<00:16:32.579> recursive<00:16:33.120> proving<00:16:33.480> is<00:16:33.660> really 00:16:33.829 --> 00:16:33.839 align:start position:0% and so recursive proving is really 00:16:33.839 --> 00:16:35.329 align:start position:0% and so recursive proving is really important<00:16:34.139> because<00:16:34.440> it<00:16:34.800> changes<00:16:35.100> the 00:16:35.329 --> 00:16:35.339 align:start position:0% important because it changes the 00:16:35.339 --> 00:16:37.730 align:start position:0% important because it changes the approach<00:16:35.639> from<00:16:36.000> scaling<00:16:36.779> the<00:16:36.899> throughput<00:16:37.500> of 00:16:37.730 --> 00:16:37.740 align:start position:0% approach from scaling the throughput of 00:16:37.740 --> 00:16:40.430 align:start position:0% approach from scaling the throughput of decentralized<00:16:38.339> network<00:16:38.540> to<00:16:39.540> instead<00:16:39.959> scaling 00:16:40.430 --> 00:16:40.440 align:start position:0% decentralized network to instead scaling 00:16:40.440 --> 00:16:42.530 align:start position:0% decentralized network to instead scaling off-chain<00:16:40.980> computational<00:16:41.459> power<00:16:41.820> which 00:16:42.530 --> 00:16:42.540 align:start position:0% off-chain computational power which 00:16:42.540 --> 00:16:44.150 align:start position:0% off-chain computational power which we're<00:16:42.720> much<00:16:42.959> more<00:16:43.079> able<00:16:43.320> to<00:16:43.440> do<00:16:43.620> like<00:16:43.860> Intel 00:16:44.150 --> 00:16:44.160 align:start position:0% we're much more able to do like Intel 00:16:44.160 --> 00:16:46.129 align:start position:0% we're much more able to do like Intel and<00:16:44.339> AMD<00:16:44.639> do<00:16:44.880> this<00:16:45.000> every<00:16:45.180> year<00:16:45.420> we<00:16:45.839> can<00:16:45.959> also 00:16:46.129 --> 00:16:46.139 align:start position:0% and AMD do this every year we can also 00:16:46.139 --> 00:16:49.249 align:start position:0% and AMD do this every year we can also build<00:16:46.320> Asics<00:16:46.880> to<00:16:47.880> make<00:16:48.360> proof<00:16:48.660> of<00:16:48.720> it<00:16:48.839> make 00:16:49.249 --> 00:16:49.259 align:start position:0% build Asics to make proof of it make 00:16:49.259 --> 00:16:51.530 align:start position:0% build Asics to make proof of it make proofs<00:16:49.620> very<00:16:49.800> quickly<00:16:50.100> and<00:16:51.000> then<00:16:51.120> we're<00:16:51.300> able 00:16:51.530 --> 00:16:51.540 align:start position:0% proofs very quickly and then we're able 00:16:51.540 --> 00:16:53.870 align:start position:0% proofs very quickly and then we're able to<00:16:51.660> see<00:16:51.899> the<00:16:52.380> sort<00:16:52.620> of<00:16:52.740> uh<00:16:53.040> improvements<00:16:53.759> that 00:16:53.870 --> 00:16:53.880 align:start position:0% to see the sort of uh improvements that 00:16:53.880 --> 00:16:55.069 align:start position:0% to see the sort of uh improvements that we<00:16:54.000> want<00:16:54.120> to<00:16:54.300> see<00:16:54.360> like<00:16:54.600> if<00:16:54.720> we're<00:16:54.839> able<00:16:54.959> to 00:16:55.069 --> 00:16:55.079 align:start position:0% we want to see like if we're able to 00:16:55.079 --> 00:16:56.810 align:start position:0% we want to see like if we're able to bundle<00:16:55.440> 10<00:16:55.560> proofs<00:16:55.860> at<00:16:55.980> a<00:16:56.100> time<00:16:56.160> we<00:16:56.339> get<00:16:56.459> a<00:16:56.519> 10x 00:16:56.810 --> 00:16:56.820 align:start position:0% bundle 10 proofs at a time we get a 10x 00:16:56.820 --> 00:16:59.090 align:start position:0% bundle 10 proofs at a time we get a 10x Improvement<00:16:57.240> 100x 00:16:59.090 --> 00:16:59.100 align:start position:0% Improvement 100x 00:16:59.100 --> 00:16:59.990 align:start position:0% Improvement 100x Etc 00:16:59.990 --> 00:17:00.000 align:start position:0% Etc 00:17:00.000 --> 00:17:01.970 align:start position:0% Etc and<00:17:00.600> and<00:17:00.779> this<00:17:01.019> does<00:17:01.199> introduce<00:17:01.620> a<00:17:01.800> little<00:17:01.860> bit 00:17:01.970 --> 00:17:01.980 align:start position:0% and and this does introduce a little bit 00:17:01.980 --> 00:17:03.350 align:start position:0% and and this does introduce a little bit of<00:17:02.100> complexity<00:17:02.579> because<00:17:02.940> we<00:17:03.120> have<00:17:03.180> to<00:17:03.300> deal 00:17:03.350 --> 00:17:03.360 align:start position:0% of complexity because we have to deal 00:17:03.360 --> 00:17:05.030 align:start position:0% of complexity because we have to deal with<00:17:03.540> approved<00:17:03.959> aggregator<00:17:04.319> and<00:17:04.679> now<00:17:04.799> the 00:17:05.030 --> 00:17:05.040 align:start position:0% with approved aggregator and now the 00:17:05.040 --> 00:17:06.470 align:start position:0% with approved aggregator and now the user<00:17:05.339> potentially<00:17:05.640> has<00:17:05.760> to<00:17:05.939> like<00:17:06.059> wait<00:17:06.240> on 00:17:06.470 --> 00:17:06.480 align:start position:0% user potentially has to like wait on 00:17:06.480 --> 00:17:08.510 align:start position:0% user potentially has to like wait on that<00:17:06.660> or<00:17:07.199> potentially<00:17:07.620> optimistically 00:17:08.510 --> 00:17:08.520 align:start position:0% that or potentially optimistically 00:17:08.520 --> 00:17:12.110 align:start position:0% that or potentially optimistically evaluate<00:17:09.000> the<00:17:09.299> aggregator<00:17:09.900> but<00:17:10.740> this<00:17:11.459> is<00:17:11.579> a 00:17:12.110 --> 00:17:12.120 align:start position:0% evaluate the aggregator but this is a 00:17:12.120 --> 00:17:14.510 align:start position:0% evaluate the aggregator but this is a decent<00:17:12.419> approach<00:17:12.660> to<00:17:12.839> scaling 00:17:14.510 --> 00:17:14.520 align:start position:0% decent approach to scaling 00:17:14.520 --> 00:17:16.909 align:start position:0% decent approach to scaling right<00:17:15.480> so<00:17:15.660> now<00:17:16.199> um<00:17:16.260> that's<00:17:16.439> most<00:17:16.679> of<00:17:16.799> the 00:17:16.909 --> 00:17:16.919 align:start position:0% right so now um that's most of the 00:17:16.919 --> 00:17:17.870 align:start position:0% right so now um that's most of the presentation<00:17:17.220> I'm<00:17:17.459> just<00:17:17.579> going<00:17:17.699> to<00:17:17.819> talk 00:17:17.870 --> 00:17:17.880 align:start position:0% presentation I'm just going to talk 00:17:17.880 --> 00:17:19.610 align:start position:0% presentation I'm just going to talk about<00:17:18.059> like<00:17:18.360> some<00:17:18.600> of<00:17:18.720> my<00:17:18.780> tester<00:17:19.079> ideas<00:17:19.260> that 00:17:19.610 --> 00:17:19.620 align:start position:0% about like some of my tester ideas that 00:17:19.620 --> 00:17:20.870 align:start position:0% about like some of my tester ideas that I<00:17:19.740> think<00:17:19.860> are<00:17:19.980> kind<00:17:20.220> of<00:17:20.339> cool<00:17:20.400> that<00:17:20.699> we<00:17:20.819> can 00:17:20.870 --> 00:17:20.880 align:start position:0% I think are kind of cool that we can 00:17:20.880 --> 00:17:22.730 align:start position:0% I think are kind of cool that we can build<00:17:21.000> with<00:17:21.179> unirp<00:17:21.720> or<00:17:21.959> the<00:17:22.199> other<00:17:22.319> Universe 00:17:22.730 --> 00:17:22.740 align:start position:0% build with unirp or the other Universe 00:17:22.740 --> 00:17:23.569 align:start position:0% build with unirp or the other Universe protocol 00:17:23.569 --> 00:17:23.579 align:start position:0% protocol 00:17:23.579 --> 00:17:26.329 align:start position:0% protocol so<00:17:23.939> the<00:17:24.059> first<00:17:24.240> is<00:17:24.419> just<00:17:24.600> like<00:17:24.780> ZK<00:17:25.199> Dows<00:17:25.740> we<00:17:26.220> can 00:17:26.329 --> 00:17:26.339 align:start position:0% so the first is just like ZK Dows we can 00:17:26.339 --> 00:17:28.789 align:start position:0% so the first is just like ZK Dows we can keep<00:17:26.579> the<00:17:27.120> balance<00:17:27.480> uh<00:17:27.959> hidden<00:17:28.260> or<00:17:28.620> the 00:17:28.789 --> 00:17:28.799 align:start position:0% keep the balance uh hidden or the 00:17:28.799 --> 00:17:30.230 align:start position:0% keep the balance uh hidden or the balance<00:17:29.100> controlled<00:17:29.400> by<00:17:29.580> a<00:17:29.700> user<00:17:29.940> hidden 00:17:30.230 --> 00:17:30.240 align:start position:0% balance controlled by a user hidden 00:17:30.240 --> 00:17:31.970 align:start position:0% balance controlled by a user hidden within<00:17:30.480> the<00:17:30.600> Dow<00:17:30.840> we<00:17:31.320> could<00:17:31.380> also<00:17:31.679> do<00:17:31.799> things 00:17:31.970 --> 00:17:31.980 align:start position:0% within the Dow we could also do things 00:17:31.980 --> 00:17:35.029 align:start position:0% within the Dow we could also do things like<00:17:32.400> vote<00:17:32.880> for<00:17:33.120> proposals<00:17:33.720> anonymously 00:17:35.029 --> 00:17:35.039 align:start position:0% like vote for proposals anonymously 00:17:35.039 --> 00:17:36.770 align:start position:0% like vote for proposals anonymously um a<00:17:35.400> lot<00:17:35.520> of<00:17:35.580> interesting<00:17:36.000> ideas<00:17:36.179> a<00:17:36.660> lot<00:17:36.720> of 00:17:36.770 --> 00:17:36.780 align:start position:0% um a lot of interesting ideas a lot of 00:17:36.780 --> 00:17:38.270 align:start position:0% um a lot of interesting ideas a lot of interesting<00:17:37.020> things<00:17:37.200> that<00:17:37.380> can<00:17:37.919> be<00:17:37.980> done<00:17:38.100> with 00:17:38.270 --> 00:17:38.280 align:start position:0% interesting things that can be done with 00:17:38.280 --> 00:17:39.710 align:start position:0% interesting things that can be done with this 00:17:39.710 --> 00:17:39.720 align:start position:0% this 00:17:39.720 --> 00:17:42.470 align:start position:0% this the<00:17:40.200> next<00:17:40.380> is<00:17:40.620> anticipal<00:17:41.340> reputation<00:17:41.760> I<00:17:42.360> use 00:17:42.470 --> 00:17:42.480 align:start position:0% the next is anticipal reputation I use 00:17:42.480 --> 00:17:44.270 align:start position:0% the next is anticipal reputation I use this<00:17:42.720> as<00:17:43.020> an<00:17:43.260> example<00:17:43.559> in<00:17:43.980> one<00:17:44.100> of<00:17:44.220> the 00:17:44.270 --> 00:17:44.280 align:start position:0% this as an example in one of the 00:17:44.280 --> 00:17:46.370 align:start position:0% this as an example in one of the previous<00:17:44.400> slides<00:17:44.820> but<00:17:45.600> what<00:17:45.720> you<00:17:45.840> could<00:17:45.960> do<00:17:46.140> is 00:17:46.370 --> 00:17:46.380 align:start position:0% previous slides but what you could do is 00:17:46.380 --> 00:17:48.590 align:start position:0% previous slides but what you could do is basically<00:17:46.799> take<00:17:47.520> like<00:17:47.760> proofs<00:17:48.179> that<00:17:48.360> you<00:17:48.480> have 00:17:48.590 --> 00:17:48.600 align:start position:0% basically take like proofs that you have 00:17:48.600 --> 00:17:50.630 align:start position:0% basically take like proofs that you have a<00:17:48.780> web<00:17:48.840> 2<00:17:49.080> identity<00:17:49.559> and<00:17:49.799> give<00:17:49.980> reputation<00:17:50.460> for 00:17:50.630 --> 00:17:50.640 align:start position:0% a web 2 identity and give reputation for 00:17:50.640 --> 00:17:52.669 align:start position:0% a web 2 identity and give reputation for that<00:17:50.820> or<00:17:51.539> potentially<00:17:51.900> use<00:17:52.080> like<00:17:52.260> bright<00:17:52.380> ID 00:17:52.669 --> 00:17:52.679 align:start position:0% that or potentially use like bright ID 00:17:52.679 --> 00:17:54.890 align:start position:0% that or potentially use like bright ID or<00:17:53.039> or<00:17:53.340> approve<00:17:53.940> that<00:17:54.059> you<00:17:54.179> have<00:17:54.240> like<00:17:54.360> poapps 00:17:54.890 --> 00:17:54.900 align:start position:0% or or approve that you have like poapps 00:17:54.900 --> 00:17:56.990 align:start position:0% or or approve that you have like poapps for<00:17:55.080> example<00:17:55.320> and<00:17:55.740> just<00:17:55.919> get<00:17:56.220> reputation<00:17:56.700> and 00:17:56.990 --> 00:17:57.000 align:start position:0% for example and just get reputation and 00:17:57.000 --> 00:17:58.730 align:start position:0% for example and just get reputation and then<00:17:57.120> use<00:17:57.360> that<00:17:57.600> to<00:17:57.840> sign<00:17:58.080> up<00:17:58.260> for<00:17:58.559> other 00:17:58.730 --> 00:17:58.740 align:start position:0% then use that to sign up for other 00:17:58.740 --> 00:18:00.890 align:start position:0% then use that to sign up for other testers 00:18:00.890 --> 00:18:00.900 align:start position:0% testers 00:18:00.900 --> 00:18:02.690 align:start position:0% testers the<00:18:01.320> third<00:18:01.380> is<00:18:01.620> like<00:18:01.860> really<00:18:02.280> simple<00:18:02.460> and 00:18:02.690 --> 00:18:02.700 align:start position:0% the third is like really simple and 00:18:02.700 --> 00:18:04.669 align:start position:0% the third is like really simple and generic<00:18:03.120> which<00:18:03.360> is<00:18:03.539> a<00:18:03.900> recommendation<00:18:04.380> system 00:18:04.669 --> 00:18:04.679 align:start position:0% generic which is a recommendation system 00:18:04.679 --> 00:18:07.070 align:start position:0% generic which is a recommendation system as<00:18:04.919> a<00:18:05.039> web<00:18:05.160> app<00:18:05.340> everyone<00:18:05.760> has<00:18:06.179> things<00:18:06.840> that 00:18:07.070 --> 00:18:07.080 align:start position:0% as a web app everyone has things that 00:18:07.080 --> 00:18:08.630 align:start position:0% as a web app everyone has things that they<00:18:07.200> use<00:18:07.380> or<00:18:07.679> that<00:18:07.860> they<00:18:08.039> would<00:18:08.400> want<00:18:08.520> to 00:18:08.630 --> 00:18:08.640 align:start position:0% they use or that they would want to 00:18:08.640 --> 00:18:11.330 align:start position:0% they use or that they would want to recommend<00:18:08.940> to<00:18:09.179> other<00:18:09.299> people<00:18:09.539> you<00:18:10.799> having 00:18:11.330 --> 00:18:11.340 align:start position:0% recommend to other people you having 00:18:11.340 --> 00:18:13.370 align:start position:0% recommend to other people you having like<00:18:11.640> reputation<00:18:12.120> for<00:18:12.539> good<00:18:12.840> recommendations 00:18:13.370 --> 00:18:13.380 align:start position:0% like reputation for good recommendations 00:18:13.380 --> 00:18:15.830 align:start position:0% like reputation for good recommendations seems<00:18:13.919> like<00:18:14.039> a<00:18:14.220> good<00:18:14.400> use<00:18:14.520> of<00:18:14.700> the<00:18:14.820> system 00:18:15.830 --> 00:18:15.840 align:start position:0% seems like a good use of the system 00:18:15.840 --> 00:18:17.390 align:start position:0% seems like a good use of the system and<00:18:16.260> then<00:18:16.380> the<00:18:16.500> final<00:18:16.620> one<00:18:16.799> is<00:18:16.980> one<00:18:17.160> that<00:18:17.280> I 00:18:17.390 --> 00:18:17.400 align:start position:0% and then the final one is one that I 00:18:17.400 --> 00:18:18.830 align:start position:0% and then the final one is one that I thought<00:18:17.520> of<00:18:17.640> when<00:18:17.820> I<00:18:18.000> was<00:18:18.059> given<00:18:18.299> the<00:18:18.480> Devcon 00:18:18.830 --> 00:18:18.840 align:start position:0% thought of when I was given the Devcon 00:18:18.840 --> 00:18:21.409 align:start position:0% thought of when I was given the Devcon poapp<00:18:19.320> I<00:18:19.860> I<00:18:20.039> really<00:18:20.220> hate<00:18:20.400> claiming<00:18:20.820> co-ops<00:18:21.240> on 00:18:21.409 --> 00:18:21.419 align:start position:0% poapp I I really hate claiming co-ops on 00:18:21.419 --> 00:18:23.570 align:start position:0% poapp I I really hate claiming co-ops on chain<00:18:21.600> because<00:18:22.020> I'm<00:18:22.559> just<00:18:22.740> giving<00:18:23.100> people<00:18:23.340> a 00:18:23.570 --> 00:18:23.580 align:start position:0% chain because I'm just giving people a 00:18:23.580 --> 00:18:24.950 align:start position:0% chain because I'm just giving people a history<00:18:23.700> of<00:18:23.940> like<00:18:24.120> the<00:18:24.240> places<00:18:24.419> I've<00:18:24.720> been<00:18:24.840> in 00:18:24.950 --> 00:18:24.960 align:start position:0% history of like the places I've been in 00:18:24.960 --> 00:18:26.510 align:start position:0% history of like the places I've been in the<00:18:25.140> real<00:18:25.260> world<00:18:25.440> which<00:18:25.919> I<00:18:26.039> think<00:18:26.160> is<00:18:26.280> kind<00:18:26.460> of 00:18:26.510 --> 00:18:26.520 align:start position:0% the real world which I think is kind of 00:18:26.520 --> 00:18:28.909 align:start position:0% the real world which I think is kind of weird<00:18:26.700> uh<00:18:27.600> so<00:18:27.780> we<00:18:27.900> can<00:18:28.020> use<00:18:28.080> unirp<00:18:28.620> to<00:18:28.740> like 00:18:28.909 --> 00:18:28.919 align:start position:0% weird uh so we can use unirp to like 00:18:28.919 --> 00:18:30.950 align:start position:0% weird uh so we can use unirp to like claim<00:18:29.340> pull-ups<00:18:29.760> anonymously<00:18:30.240> and<00:18:30.720> then<00:18:30.780> we 00:18:30.950 --> 00:18:30.960 align:start position:0% claim pull-ups anonymously and then we 00:18:30.960 --> 00:18:32.450 align:start position:0% claim pull-ups anonymously and then we could<00:18:31.140> make<00:18:31.440> a<00:18:31.559> proof<00:18:31.799> that<00:18:31.919> you<00:18:32.039> have<00:18:32.160> like<00:18:32.340> a 00:18:32.450 --> 00:18:32.460 align:start position:0% could make a proof that you have like a 00:18:32.460 --> 00:18:34.370 align:start position:0% could make a proof that you have like a co-op<00:18:32.760> and<00:18:32.940> a<00:18:33.059> set<00:18:33.179> like<00:18:33.480> for<00:18:33.600> example<00:18:33.900> I<00:18:34.320> could 00:18:34.370 --> 00:18:34.380 align:start position:0% co-op and a set like for example I could 00:18:34.380 --> 00:18:36.289 align:start position:0% co-op and a set like for example I could prove<00:18:34.620> that<00:18:34.740> I<00:18:34.919> have<00:18:35.039> two<00:18:35.220> apps<00:18:35.820> from<00:18:35.940> the<00:18:36.120> set 00:18:36.289 --> 00:18:36.299 align:start position:0% prove that I have two apps from the set 00:18:36.299 --> 00:18:38.330 align:start position:0% prove that I have two apps from the set of<00:18:36.480> all<00:18:36.660> Defcon<00:18:37.200> pop-ups<00:18:37.799> something<00:18:38.100> like 00:18:38.330 --> 00:18:38.340 align:start position:0% of all Defcon pop-ups something like 00:18:38.340 --> 00:18:40.010 align:start position:0% of all Defcon pop-ups something like that 00:18:40.010 --> 00:18:40.020 align:start position:0% that 00:18:40.020 --> 00:18:42.169 align:start position:0% that uh<00:18:40.799> and<00:18:41.039> then<00:18:41.160> just<00:18:41.400> some<00:18:41.580> nice<00:18:41.820> to<00:18:42.000> have 00:18:42.169 --> 00:18:42.179 align:start position:0% uh and then just some nice to have 00:18:42.179 --> 00:18:44.150 align:start position:0% uh and then just some nice to have things<00:18:42.480> for<00:18:42.960> sort<00:18:43.260> of<00:18:43.320> the<00:18:43.500> ecosystem<00:18:43.860> like 00:18:44.150 --> 00:18:44.160 align:start position:0% things for sort of the ecosystem like 00:18:44.160 --> 00:18:46.490 align:start position:0% things for sort of the ecosystem like infrastructure<00:18:44.700> wise<00:18:45.419> the<00:18:45.900> first<00:18:46.080> is<00:18:46.260> like<00:18:46.440> a 00:18:46.490 --> 00:18:46.500 align:start position:0% infrastructure wise the first is like a 00:18:46.500 --> 00:18:49.130 align:start position:0% infrastructure wise the first is like a ZK<00:18:46.799> directory<00:18:47.400> this<00:18:48.120> just<00:18:48.360> a<00:18:48.539> directory<00:18:48.960> of 00:18:49.130 --> 00:18:49.140 align:start position:0% ZK directory this just a directory of 00:18:49.140 --> 00:18:50.810 align:start position:0% ZK directory this just a directory of the<00:18:49.320> hashes<00:18:49.620> of<00:18:49.860> proofs<00:18:50.100> and<00:18:50.280> human<00:18:50.400> readable 00:18:50.810 --> 00:18:50.820 align:start position:0% the hashes of proofs and human readable 00:18:50.820 --> 00:18:53.150 align:start position:0% the hashes of proofs and human readable descriptions<00:18:51.299> of<00:18:51.660> what<00:18:51.840> the<00:18:52.020> proofs<00:18:52.320> do<00:18:52.500> and 00:18:53.150 --> 00:18:53.160 align:start position:0% descriptions of what the proofs do and 00:18:53.160 --> 00:18:54.770 align:start position:0% descriptions of what the proofs do and this<00:18:53.280> would<00:18:53.400> be<00:18:53.520> really<00:18:53.760> important<00:18:54.179> if<00:18:54.660> we're 00:18:54.770 --> 00:18:54.780 align:start position:0% this would be really important if we're 00:18:54.780 --> 00:18:55.909 align:start position:0% this would be really important if we're going<00:18:54.900> to<00:18:54.960> oauth<00:18:55.440> between<00:18:55.559> different 00:18:55.909 --> 00:18:55.919 align:start position:0% going to oauth between different 00:18:55.919 --> 00:18:57.890 align:start position:0% going to oauth between different applications<00:18:56.460> and<00:18:56.820> request<00:18:57.059> ZK<00:18:57.480> proofs 00:18:57.890 --> 00:18:57.900 align:start position:0% applications and request ZK proofs 00:18:57.900 --> 00:18:59.390 align:start position:0% applications and request ZK proofs because<00:18:58.200> they're<00:18:58.440> potentially<00:18:58.799> requests 00:18:59.390 --> 00:18:59.400 align:start position:0% because they're potentially requests 00:18:59.400 --> 00:19:01.370 align:start position:0% because they're potentially requests just<00:18:59.760> random<00:19:00.240> proofs<00:19:00.539> that<00:19:00.720> are<00:19:00.900> specific<00:19:01.140> to 00:19:01.370 --> 00:19:01.380 align:start position:0% just random proofs that are specific to 00:19:01.380 --> 00:19:03.470 align:start position:0% just random proofs that are specific to their<00:19:01.620> application<00:19:02.100> and<00:19:02.760> so<00:19:02.940> applications 00:19:03.470 --> 00:19:03.480 align:start position:0% their application and so applications 00:19:03.480 --> 00:19:04.610 align:start position:0% their application and so applications should<00:19:03.720> have<00:19:03.900> a<00:19:04.020> place<00:19:04.200> where<00:19:04.380> they<00:19:04.500> can 00:19:04.610 --> 00:19:04.620 align:start position:0% should have a place where they can 00:19:04.620 --> 00:19:06.830 align:start position:0% should have a place where they can request<00:19:04.919> information<00:19:05.220> about<00:19:05.760> a<00:19:06.059> proof<00:19:06.419> and 00:19:06.830 --> 00:19:06.840 align:start position:0% request information about a proof and 00:19:06.840 --> 00:19:09.529 align:start position:0% request information about a proof and then<00:19:06.960> return<00:19:07.140> it<00:19:07.440> to<00:19:07.559> the<00:19:07.679> user 00:19:09.529 --> 00:19:09.539 align:start position:0% then return it to the user 00:19:09.539 --> 00:19:11.690 align:start position:0% then return it to the user the<00:19:10.020> next<00:19:10.140> thing<00:19:10.260> is<00:19:10.380> planck<00:19:10.860> we<00:19:11.340> already<00:19:11.460> have 00:19:11.690 --> 00:19:11.700 align:start position:0% the next thing is planck we already have 00:19:11.700 --> 00:19:13.370 align:start position:0% the next thing is planck we already have this<00:19:11.940> but<00:19:12.240> I<00:19:12.480> just<00:19:12.600> want<00:19:12.720> to<00:19:12.840> talk<00:19:12.960> about<00:19:13.080> it<00:19:13.260> a 00:19:13.370 --> 00:19:13.380 align:start position:0% this but I just want to talk about it a 00:19:13.380 --> 00:19:14.630 align:start position:0% this but I just want to talk about it a little<00:19:13.440> bit<00:19:13.559> more 00:19:14.630 --> 00:19:14.640 align:start position:0% little bit more 00:19:14.640 --> 00:19:16.850 align:start position:0% little bit more um<00:19:15.120> the<00:19:15.600> most<00:19:15.660> important<00:19:15.900> part<00:19:16.080> of<00:19:16.200> Planck<00:19:16.620> to 00:19:16.850 --> 00:19:16.860 align:start position:0% um the most important part of Planck to 00:19:16.860 --> 00:19:18.169 align:start position:0% um the most important part of Planck to me<00:19:16.919> at<00:19:17.100> least<00:19:17.220> is<00:19:17.400> we<00:19:17.640> don't<00:19:17.700> have<00:19:17.880> the<00:19:18.000> space 00:19:18.169 --> 00:19:18.179 align:start position:0% me at least is we don't have the space 00:19:18.179 --> 00:19:19.789 align:start position:0% me at least is we don't have the space to<00:19:18.360> use<00:19:18.539> trusted<00:19:18.840> setup<00:19:19.140> that<00:19:19.320> is<00:19:19.440> circuit 00:19:19.789 --> 00:19:19.799 align:start position:0% to use trusted setup that is circuit 00:19:19.799 --> 00:19:22.370 align:start position:0% to use trusted setup that is circuit specific<00:19:20.100> so<00:19:20.880> with<00:19:21.120> unirp<00:19:21.600> we<00:19:21.780> want<00:19:21.960> people<00:19:22.080> to 00:19:22.370 --> 00:19:22.380 align:start position:0% specific so with unirp we want people to 00:19:22.380 --> 00:19:24.289 align:start position:0% specific so with unirp we want people to extend<00:19:22.740> the<00:19:22.919> proofs<00:19:23.400> that<00:19:23.520> we've<00:19:23.640> written<00:19:23.940> and 00:19:24.289 --> 00:19:24.299 align:start position:0% extend the proofs that we've written and 00:19:24.299 --> 00:19:25.549 align:start position:0% extend the proofs that we've written and write<00:19:24.419> their<00:19:24.660> own<00:19:24.780> to<00:19:25.080> build<00:19:25.200> their<00:19:25.380> own 00:19:25.549 --> 00:19:25.559 align:start position:0% write their own to build their own 00:19:25.559 --> 00:19:28.190 align:start position:0% write their own to build their own functionality<00:19:26.220> and<00:19:27.000> with<00:19:27.299> Ross<00:19:27.660> 16<00:19:27.840> that's 00:19:28.190 --> 00:19:28.200 align:start position:0% functionality and with Ross 16 that's 00:19:28.200 --> 00:19:29.690 align:start position:0% functionality and with Ross 16 that's very<00:19:28.380> difficult<00:19:28.679> to<00:19:28.919> do<00:19:29.039> because<00:19:29.340> they<00:19:29.580> have 00:19:29.690 --> 00:19:29.700 align:start position:0% very difficult to do because they have 00:19:29.700 --> 00:19:31.909 align:start position:0% very difficult to do because they have to<00:19:29.820> run<00:19:30.000> a<00:19:30.299> trusted<00:19:30.660> setup<00:19:30.960> ceremony<00:19:31.380> for<00:19:31.740> the 00:19:31.909 --> 00:19:31.919 align:start position:0% to run a trusted setup ceremony for the 00:19:31.919 --> 00:19:33.710 align:start position:0% to run a trusted setup ceremony for the circuits<00:19:32.280> that<00:19:32.400> they<00:19:32.580> build<00:19:32.760> and<00:19:33.360> this<00:19:33.480> is<00:19:33.600> a 00:19:33.710 --> 00:19:33.720 align:start position:0% circuits that they build and this is a 00:19:33.720 --> 00:19:35.810 align:start position:0% circuits that they build and this is a huge<00:19:33.900> amount<00:19:34.080> of<00:19:34.260> coordination<00:19:34.620> and<00:19:34.919> effort 00:19:35.810 --> 00:19:35.820 align:start position:0% huge amount of coordination and effort 00:19:35.820 --> 00:19:38.510 align:start position:0% huge amount of coordination and effort can't<00:19:36.299> really<00:19:36.539> expect<00:19:36.840> most<00:19:37.620> developers<00:19:38.160> to 00:19:38.510 --> 00:19:38.520 align:start position:0% can't really expect most developers to 00:19:38.520 --> 00:19:40.610 align:start position:0% can't really expect most developers to reasonably<00:19:38.940> do<00:19:39.179> so<00:19:39.600> with<00:19:39.780> Planck<00:19:40.200> we<00:19:40.380> cut<00:19:40.500> all 00:19:40.610 --> 00:19:40.620 align:start position:0% reasonably do so with Planck we cut all 00:19:40.620 --> 00:19:42.650 align:start position:0% reasonably do so with Planck we cut all the<00:19:40.740> head<00:19:40.860> out<00:19:41.039> we<00:19:41.280> get<00:19:41.400> to<00:19:41.520> just<00:19:41.700> use<00:19:42.000> some 00:19:42.650 --> 00:19:42.660 align:start position:0% the head out we get to just use some 00:19:42.660 --> 00:19:44.570 align:start position:0% the head out we get to just use some phase<00:19:43.080> one<00:19:43.260> trusted<00:19:43.679> setup<00:19:43.980> made<00:19:44.160> by<00:19:44.400> some 00:19:44.570 --> 00:19:44.580 align:start position:0% phase one trusted setup made by some 00:19:44.580 --> 00:19:46.669 align:start position:0% phase one trusted setup made by some trusted<00:19:44.880> density<00:19:45.179> or<00:19:45.780> some<00:19:46.020> trusted<00:19:46.380> entities 00:19:46.669 --> 00:19:46.679 align:start position:0% trusted density or some trusted entities 00:19:46.679 --> 00:19:50.330 align:start position:0% trusted density or some trusted entities and<00:19:47.340> then<00:19:47.400> you<00:19:47.640> have<00:19:47.820> secure<00:19:48.419> proofs 00:19:50.330 --> 00:19:50.340 align:start position:0% and then you have secure proofs 00:19:50.340 --> 00:19:52.610 align:start position:0% and then you have secure proofs and<00:19:50.880> the<00:19:51.059> last<00:19:51.179> thing<00:19:51.360> is<00:19:51.720> easier<00:19:52.200> browser 00:19:52.610 --> 00:19:52.620 align:start position:0% and the last thing is easier browser 00:19:52.620 --> 00:19:55.549 align:start position:0% and the last thing is easier browser proofs<00:19:52.980> so<00:19:53.460> we<00:19:54.000> have<00:19:54.240> proofs<00:19:55.020> in<00:19:55.140> the<00:19:55.260> browser 00:19:55.549 --> 00:19:55.559 align:start position:0% proofs so we have proofs in the browser 00:19:55.559 --> 00:19:58.549 align:start position:0% proofs so we have proofs in the browser using<00:19:55.860> snark.js<00:19:56.460> but<00:19:57.360> you<00:19:58.200> have<00:19:58.320> to<00:19:58.440> like 00:19:58.549 --> 00:19:58.559 align:start position:0% using snark.js but you have to like 00:19:58.559 --> 00:20:00.289 align:start position:0% using snark.js but you have to like configure<00:19:59.160> webpack<00:19:59.580> really<00:19:59.760> specifically 00:20:00.289 --> 00:20:00.299 align:start position:0% configure webpack really specifically 00:20:00.299 --> 00:20:02.750 align:start position:0% configure webpack really specifically and<00:20:01.080> it<00:20:01.320> also<00:20:01.559> uses<00:20:01.799> like<00:20:02.039> Z<00:20:02.280> key<00:20:02.520> and 00:20:02.750 --> 00:20:02.760 align:start position:0% and it also uses like Z key and 00:20:02.760 --> 00:20:03.890 align:start position:0% and it also uses like Z key and webassembly<00:20:03.299> file<00:20:03.480> and<00:20:03.660> a<00:20:03.780> second 00:20:03.890 --> 00:20:03.900 align:start position:0% webassembly file and a second 00:20:03.900 --> 00:20:05.750 align:start position:0% webassembly file and a second webassembly<00:20:04.440> file<00:20:04.620> for<00:20:04.799> a<00:20:04.919> curve<00:20:05.220> and<00:20:05.520> it'd<00:20:05.700> be 00:20:05.750 --> 00:20:05.760 align:start position:0% webassembly file for a curve and it'd be 00:20:05.760 --> 00:20:07.250 align:start position:0% webassembly file for a curve and it'd be much<00:20:05.880> easier<00:20:06.120> if<00:20:06.299> we<00:20:06.419> had<00:20:06.480> a<00:20:06.660> tool<00:20:06.900> that<00:20:07.080> just 00:20:07.250 --> 00:20:07.260 align:start position:0% much easier if we had a tool that just 00:20:07.260 --> 00:20:09.230 align:start position:0% much easier if we had a tool that just sort<00:20:07.440> of<00:20:07.559> bundles<00:20:07.860> all<00:20:08.100> of<00:20:08.220> that<00:20:08.400> into<00:20:08.760> a 00:20:09.230 --> 00:20:09.240 align:start position:0% sort of bundles all of that into a 00:20:09.240 --> 00:20:11.330 align:start position:0% sort of bundles all of that into a single<00:20:09.480> web<00:20:09.660> assembly<00:20:10.140> that<00:20:10.620> we<00:20:10.740> can<00:20:10.860> run<00:20:11.039> in 00:20:11.330 --> 00:20:11.340 align:start position:0% single web assembly that we can run in 00:20:11.340 --> 00:20:13.789 align:start position:0% single web assembly that we can run in the<00:20:11.400> browser<00:20:11.760> just<00:20:12.059> pass<00:20:12.539> in<00:20:12.780> signals<00:20:13.440> and<00:20:13.620> get 00:20:13.789 --> 00:20:13.799 align:start position:0% the browser just pass in signals and get 00:20:13.799 --> 00:20:16.070 align:start position:0% the browser just pass in signals and get the<00:20:14.039> proof<00:20:14.340> back<00:20:14.580> this<00:20:15.480> will<00:20:15.600> give<00:20:15.780> us<00:20:15.900> like 00:20:16.070 --> 00:20:16.080 align:start position:0% the proof back this will give us like 00:20:16.080 --> 00:20:18.230 align:start position:0% the proof back this will give us like three<00:20:16.200> asynchronous<00:20:16.860> operation<00:20:17.280> as<00:20:17.520> well 00:20:18.230 --> 00:20:18.240 align:start position:0% three asynchronous operation as well 00:20:18.240 --> 00:20:19.730 align:start position:0% three asynchronous operation as well um<00:20:18.299> yeah<00:20:18.720> it<00:20:18.900> would<00:20:18.960> just<00:20:19.140> be<00:20:19.200> a<00:20:19.320> nice<00:20:19.440> thing<00:20:19.559> to 00:20:19.730 --> 00:20:19.740 align:start position:0% um yeah it would just be a nice thing to 00:20:19.740 --> 00:20:21.289 align:start position:0% um yeah it would just be a nice thing to have 00:20:21.289 --> 00:20:21.299 align:start position:0% have 00:20:21.299 --> 00:20:23.150 align:start position:0% have uh<00:20:21.900> yeah<00:20:22.020> that's<00:20:22.380> pretty<00:20:22.679> much<00:20:22.799> the<00:20:22.919> end<00:20:23.039> of 00:20:23.150 --> 00:20:23.160 align:start position:0% uh yeah that's pretty much the end of 00:20:23.160 --> 00:20:24.650 align:start position:0% uh yeah that's pretty much the end of the<00:20:23.220> talk<00:20:23.340> we<00:20:23.700> have<00:20:23.820> a<00:20:23.940> few<00:20:24.059> events<00:20:24.360> happening 00:20:24.650 --> 00:20:24.660 align:start position:0% the talk we have a few events happening 00:20:24.660 --> 00:20:26.810 align:start position:0% the talk we have a few events happening related<00:20:25.020> to<00:20:25.200> unirap<00:20:25.740> so<00:20:26.160> first<00:20:26.280> we<00:20:26.520> have<00:20:26.640> a 00:20:26.810 --> 00:20:26.820 align:start position:0% related to unirap so first we have a 00:20:26.820 --> 00:20:29.150 align:start position:0% related to unirap so first we have a unwrap<00:20:27.240> workshop<00:20:27.600> on<00:20:27.840> Friday<00:20:28.020> at<00:20:28.380> 10<00:20:28.500> 30<00:20:28.740> a.m 00:20:29.150 --> 00:20:29.160 align:start position:0% unwrap workshop on Friday at 10 30 a.m 00:20:29.160 --> 00:20:31.010 align:start position:0% unwrap workshop on Friday at 10 30 a.m that's<00:20:29.640> going<00:20:29.880> to<00:20:29.940> be<00:20:30.000> on<00:20:30.240> the<00:20:30.360> first<00:20:30.480> floor<00:20:30.720> at 00:20:31.010 --> 00:20:31.020 align:start position:0% that's going to be on the first floor at 00:20:31.020 --> 00:20:33.409 align:start position:0% that's going to be on the first floor at the<00:20:31.140> ZK<00:20:31.440> Community<00:20:31.679> Hub<00:20:32.039> we<00:20:32.700> also<00:20:32.880> have<00:20:33.000> a<00:20:33.120> demo 00:20:33.409 --> 00:20:33.419 align:start position:0% the ZK Community Hub we also have a demo 00:20:33.419 --> 00:20:35.450 align:start position:0% the ZK Community Hub we also have a demo at<00:20:33.780> Thursday<00:20:34.020> at<00:20:34.380> three<00:20:34.559> o'clock<00:20:34.860> in<00:20:35.160> the<00:20:35.280> same 00:20:35.450 --> 00:20:35.460 align:start position:0% at Thursday at three o'clock in the same 00:20:35.460 --> 00:20:38.029 align:start position:0% at Thursday at three o'clock in the same place<00:20:35.700> a<00:20:36.480> big<00:20:36.780> thank<00:20:36.900> you<00:20:37.020> to<00:20:37.140> Xerox<00:20:37.500> park<00:20:37.799> for 00:20:38.029 --> 00:20:38.039 align:start position:0% place a big thank you to Xerox park for 00:20:38.039 --> 00:20:39.529 align:start position:0% place a big thank you to Xerox park for putting<00:20:38.280> on<00:20:38.400> those<00:20:38.640> events<00:20:38.940> and<00:20:39.059> inviting<00:20:39.480> us 00:20:39.529 --> 00:20:39.539 align:start position:0% putting on those events and inviting us 00:20:39.539 --> 00:20:40.789 align:start position:0% putting on those events and inviting us to<00:20:39.780> participate 00:20:40.789 --> 00:20:40.799 align:start position:0% to participate 00:20:40.799 --> 00:20:42.110 align:start position:0% to participate uh<00:20:41.160> and<00:20:41.280> then<00:20:41.400> if<00:20:41.580> you<00:20:41.640> want<00:20:41.760> more<00:20:41.940> information 00:20:42.110 --> 00:20:42.120 align:start position:0% uh and then if you want more information 00:20:42.120 --> 00:20:44.330 align:start position:0% uh and then if you want more information about<00:20:42.539> unirp<00:20:43.200> you<00:20:43.500> can<00:20:43.559> go<00:20:43.679> to<00:20:43.740> github.com 00:20:44.330 --> 00:20:44.340 align:start position:0% about unirp you can go to github.com 00:20:44.340 --> 00:20:47.090 align:start position:0% about unirp you can go to github.com unit<00:20:44.940> or<00:20:45.480> you<00:20:45.600> can<00:20:45.660> scan<00:20:45.840> this<00:20:46.020> QR<00:20:46.440> and<00:20:46.919> it'll 00:20:47.090 --> 00:20:47.100 align:start position:0% unit or you can scan this QR and it'll 00:20:47.100 --> 00:20:48.650 align:start position:0% unit or you can scan this QR and it'll take<00:20:47.220> you<00:20:47.340> to<00:20:47.520> our<00:20:47.820> organization<00:20:48.299> homepage 00:20:48.650 --> 00:20:48.660 align:start position:0% take you to our organization homepage 00:20:48.660 --> 00:20:50.810 align:start position:0% take you to our organization homepage where<00:20:48.960> you<00:20:49.080> can<00:20:49.200> find<00:20:49.440> documentation<00:20:50.340> links 00:20:50.810 --> 00:20:50.820 align:start position:0% where you can find documentation links 00:20:50.820 --> 00:20:53.150 align:start position:0% where you can find documentation links uh<00:20:51.299> links<00:20:51.600> to<00:20:51.720> our<00:20:51.840> Discord<00:20:52.140> and<00:20:52.559> a<00:20:52.679> link<00:20:52.799> to<00:20:52.980> a 00:20:53.150 --> 00:20:53.160 align:start position:0% uh links to our Discord and a link to a 00:20:53.160 --> 00:20:55.130 align:start position:0% uh links to our Discord and a link to a demo<00:20:53.460> application<00:20:53.880> that<00:20:54.179> we<00:20:54.299> have<00:20:54.419> running<00:20:54.660> on 00:20:55.130 --> 00:20:55.140 align:start position:0% demo application that we have running on 00:20:55.140 --> 00:20:56.510 align:start position:0% demo application that we have running on this<00:20:55.380> protocol 00:20:56.510 --> 00:20:56.520 align:start position:0% this protocol 00:20:56.520 --> 00:20:59.620 align:start position:0% this protocol uh<00:20:57.120> yeah<00:20:57.240> that's<00:20:57.539> it<00:20:57.780> uh<00:20:58.200> any<00:20:58.440> questions 00:20:59.620 --> 00:20:59.630 align:start position:0% uh yeah that's it uh any questions 00:20:59.630 --> 00:21:11.630 align:start position:0% uh yeah that's it uh any questions [Applause] 00:21:11.630 --> 00:21:11.640 align:start position:0% 00:21:11.640 --> 00:21:13.549 align:start position:0% um<00:21:11.760> first<00:21:12.120> of<00:21:12.360> all<00:21:12.360> cool<00:21:12.660> cool<00:21:12.720> presentation 00:21:13.549 --> 00:21:13.559 align:start position:0% um first of all cool cool presentation 00:21:13.559 --> 00:21:16.010 align:start position:0% um first of all cool cool presentation thank<00:21:13.919> you<00:21:13.980> for<00:21:14.160> all<00:21:14.280> the<00:21:14.400> information<00:21:14.900> uh<00:21:15.900> I 00:21:16.010 --> 00:21:16.020 align:start position:0% thank you for all the information uh I 00:21:16.020 --> 00:21:17.390 align:start position:0% thank you for all the information uh I was<00:21:16.140> wondering<00:21:16.380> from<00:21:16.559> a<00:21:16.740> product<00:21:16.860> standpoint 00:21:17.390 --> 00:21:17.400 align:start position:0% was wondering from a product standpoint 00:21:17.400 --> 00:21:19.190 align:start position:0% was wondering from a product standpoint or<00:21:17.580> maybe<00:21:17.760> from<00:21:18.000> the<00:21:18.179> user<00:21:18.480> perspective<00:21:18.840> how 00:21:19.190 --> 00:21:19.200 align:start position:0% or maybe from the user perspective how 00:21:19.200 --> 00:21:20.870 align:start position:0% or maybe from the user perspective how do<00:21:19.320> you<00:21:19.440> explain 00:21:20.870 --> 00:21:20.880 align:start position:0% do you explain 00:21:20.880 --> 00:21:24.770 align:start position:0% do you explain um<00:21:21.000> the<00:21:21.840> need<00:21:22.020> to<00:21:22.820> sequentially<00:21:23.820> create<00:21:24.419> new 00:21:24.770 --> 00:21:24.780 align:start position:0% um the need to sequentially create new 00:21:24.780 --> 00:21:25.909 align:start position:0% um the need to sequentially create new identities 00:21:25.909 --> 00:21:25.919 align:start position:0% identities 00:21:25.919 --> 00:21:29.210 align:start position:0% identities in<00:21:26.340> order<00:21:26.400> to<00:21:26.580> remain<00:21:26.880> anonymous<00:21:27.679> and<00:21:28.679> also<00:21:29.100> if 00:21:29.210 --> 00:21:29.220 align:start position:0% in order to remain anonymous and also if 00:21:29.220 --> 00:21:30.770 align:start position:0% in order to remain anonymous and also if there's<00:21:29.340> a<00:21:29.580> way<00:21:29.700> to<00:21:29.820> apps<00:21:30.179> like<00:21:30.360> that<00:21:30.539> maybe 00:21:30.770 --> 00:21:30.780 align:start position:0% there's a way to apps like that maybe 00:21:30.780 --> 00:21:33.230 align:start position:0% there's a way to apps like that maybe save<00:21:31.080> it<00:21:31.320> in<00:21:31.500> the<00:21:31.679> session<00:21:32.159> in<00:21:32.700> the<00:21:32.820> browser 00:21:33.230 --> 00:21:33.240 align:start position:0% save it in the session in the browser 00:21:33.240 --> 00:21:35.870 align:start position:0% save it in the session in the browser you<00:21:33.539> know<00:21:33.659> appstock<00:21:34.380> the<00:21:34.500> user<00:21:34.799> away<00:21:34.919> from 00:21:35.870 --> 00:21:35.880 align:start position:0% you know appstock the user away from 00:21:35.880 --> 00:21:39.110 align:start position:0% you know appstock the user away from such<00:21:36.659> a<00:21:36.840> involved<00:21:37.380> mechanism<00:21:37.740> of<00:21:38.460> creating 00:21:39.110 --> 00:21:39.120 align:start position:0% such a involved mechanism of creating 00:21:39.120 --> 00:21:41.029 align:start position:0% such a involved mechanism of creating like<00:21:39.299> a<00:21:39.539> sudden<00:21:39.900> anonymous 00:21:41.029 --> 00:21:41.039 align:start position:0% like a sudden anonymous 00:21:41.039 --> 00:21:43.909 align:start position:0% like a sudden anonymous name<00:21:41.580> every<00:21:41.880> every<00:21:42.179> Epoch<00:21:42.780> sure 00:21:43.909 --> 00:21:43.919 align:start position:0% name every every Epoch sure 00:21:43.919 --> 00:21:46.669 align:start position:0% name every every Epoch sure yeah<00:21:44.520> so<00:21:44.880> well<00:21:45.600> the<00:21:45.780> reason<00:21:45.900> we<00:21:46.080> do<00:21:46.200> this<00:21:46.380> is 00:21:46.669 --> 00:21:46.679 align:start position:0% yeah so well the reason we do this is 00:21:46.679 --> 00:21:49.130 align:start position:0% yeah so well the reason we do this is because<00:21:46.919> they<00:21:47.580> need<00:21:47.760> to<00:21:47.880> have<00:21:48.179> uh<00:21:48.840> they<00:21:49.080> need 00:21:49.130 --> 00:21:49.140 align:start position:0% because they need to have uh they need 00:21:49.140 --> 00:21:50.870 align:start position:0% because they need to have uh they need to<00:21:49.260> be<00:21:49.320> able<00:21:49.440> to<00:21:49.500> prove<00:21:49.799> a<00:21:49.919> leaf<00:21:50.220> in<00:21:50.400> the<00:21:50.460> epoch 00:21:50.870 --> 00:21:50.880 align:start position:0% to be able to prove a leaf in the epoch 00:21:50.880 --> 00:21:53.510 align:start position:0% to be able to prove a leaf in the epoch tree<00:21:51.000> to<00:21:51.179> claim<00:21:51.480> reputation<00:21:52.100> uh<00:21:53.100> but<00:21:53.280> I<00:21:53.460> would 00:21:53.510 --> 00:21:53.520 align:start position:0% tree to claim reputation uh but I would 00:21:53.520 --> 00:21:55.130 align:start position:0% tree to claim reputation uh but I would say<00:21:53.700> it's<00:21:54.059> not<00:21:54.179> as<00:21:54.360> involved<00:21:54.720> as<00:21:54.840> it<00:21:55.020> might 00:21:55.130 --> 00:21:55.140 align:start position:0% say it's not as involved as it might 00:21:55.140 --> 00:21:56.870 align:start position:0% say it's not as involved as it might seem<00:21:55.380> we<00:21:55.679> can<00:21:55.860> do<00:21:55.980> this<00:21:56.100> silently<00:21:56.580> in<00:21:56.760> the 00:21:56.870 --> 00:21:56.880 align:start position:0% seem we can do this silently in the 00:21:56.880 --> 00:21:58.490 align:start position:0% seem we can do this silently in the background<00:21:57.059> in<00:21:57.299> the<00:21:57.480> browser<00:21:57.780> so<00:21:58.140> like<00:21:58.320> the 00:21:58.490 --> 00:21:58.500 align:start position:0% background in the browser so like the 00:21:58.500 --> 00:22:00.289 align:start position:0% background in the browser so like the user<00:21:58.740> enters<00:21:59.039> the<00:21:59.159> the<00:21:59.340> web<00:21:59.580> page<00:21:59.820> and<00:22:00.179> then 00:22:00.289 --> 00:22:00.299 align:start position:0% user enters the the web page and then 00:22:00.299 --> 00:22:01.850 align:start position:0% user enters the the web page and then the<00:22:00.419> web<00:22:00.539> page<00:22:00.780> checks<00:22:01.200> if<00:22:01.440> they<00:22:01.620> need<00:22:01.740> to 00:22:01.850 --> 00:22:01.860 align:start position:0% the web page checks if they need to 00:22:01.860 --> 00:22:03.529 align:start position:0% the web page checks if they need to generate<00:22:02.159> a<00:22:02.280> new<00:22:02.400> identity<00:22:02.820> and<00:22:03.179> if<00:22:03.299> they<00:22:03.419> do 00:22:03.529 --> 00:22:03.539 align:start position:0% generate a new identity and if they do 00:22:03.539 --> 00:22:05.330 align:start position:0% generate a new identity and if they do they<00:22:03.780> generate<00:22:04.020> a<00:22:04.140> ZK<00:22:04.440> proof<00:22:04.799> in<00:22:05.159> the 00:22:05.330 --> 00:22:05.340 align:start position:0% they generate a ZK proof in the 00:22:05.340 --> 00:22:07.250 align:start position:0% they generate a ZK proof in the background<00:22:05.700> and<00:22:06.240> submit<00:22:06.480> it<00:22:06.600> to<00:22:06.720> a<00:22:06.840> relayer 00:22:07.250 --> 00:22:07.260 align:start position:0% background and submit it to a relayer 00:22:07.260 --> 00:22:09.049 align:start position:0% background and submit it to a relayer and<00:22:07.500> it's<00:22:07.799> done 00:22:09.049 --> 00:22:09.059 align:start position:0% and it's done 00:22:09.059 --> 00:22:09.830 align:start position:0% and it's done um 00:22:09.830 --> 00:22:09.840 align:start position:0% um 00:22:09.840 --> 00:22:11.390 align:start position:0% um yeah<00:22:10.380> there's<00:22:10.559> not<00:22:10.740> a<00:22:10.860> way<00:22:10.919> to<00:22:11.039> make<00:22:11.159> that<00:22:11.280> less 00:22:11.390 --> 00:22:11.400 align:start position:0% yeah there's not a way to make that less 00:22:11.400 --> 00:22:13.430 align:start position:0% yeah there's not a way to make that less manual<00:22:11.820> without<00:22:12.120> changing<00:22:12.900> the<00:22:13.080> architecture 00:22:13.430 --> 00:22:13.440 align:start position:0% manual without changing the architecture 00:22:13.440 --> 00:22:14.930 align:start position:0% manual without changing the architecture of<00:22:13.620> the<00:22:13.740> system<00:22:13.860> like<00:22:14.159> pretty<00:22:14.400> substantially 00:22:14.930 --> 00:22:14.940 align:start position:0% of the system like pretty substantially 00:22:14.940 --> 00:22:21.230 align:start position:0% of the system like pretty substantially though 00:22:21.230 --> 00:22:21.240 align:start position:0% 00:22:21.240 --> 00:22:24.110 align:start position:0% hello<00:22:21.659> so 00:22:24.110 --> 00:22:24.120 align:start position:0% hello so 00:22:24.120 --> 00:22:26.270 align:start position:0% hello so how<00:22:24.659> often<00:22:24.960> do<00:22:25.140> you<00:22:25.320> see<00:22:25.500> the<00:22:25.799> state 00:22:26.270 --> 00:22:26.280 align:start position:0% how often do you see the state 00:22:26.280 --> 00:22:28.610 align:start position:0% how often do you see the state transition<00:22:26.640> happen<00:22:27.140> is<00:22:28.140> it<00:22:28.320> going<00:22:28.440> to<00:22:28.500> be 00:22:28.610 --> 00:22:28.620 align:start position:0% transition happen is it going to be 00:22:28.620 --> 00:22:31.070 align:start position:0% transition happen is it going to be peripoc<00:22:29.220> or<00:22:29.460> maybe<00:22:29.640> there<00:22:30.000> can<00:22:30.120> be<00:22:30.240> some 00:22:31.070 --> 00:22:31.080 align:start position:0% peripoc or maybe there can be some 00:22:31.080 --> 00:22:31.730 align:start position:0% peripoc or maybe there can be some um 00:22:31.730 --> 00:22:31.740 align:start position:0% um 00:22:31.740 --> 00:22:34.310 align:start position:0% um tricky<00:22:32.280> there<00:22:32.520> to<00:22:32.760> maybe<00:22:32.880> avoid<00:22:33.480> this 00:22:34.310 --> 00:22:34.320 align:start position:0% tricky there to maybe avoid this 00:22:34.320 --> 00:22:36.950 align:start position:0% tricky there to maybe avoid this Kevin<00:22:34.799> load<00:22:35.280> in<00:22:35.460> the<00:22:35.640> computation 00:22:36.950 --> 00:22:36.960 align:start position:0% Kevin load in the computation 00:22:36.960 --> 00:22:38.990 align:start position:0% Kevin load in the computation uh<00:22:37.500> yeah<00:22:37.620> so<00:22:37.799> the<00:22:37.980> state<00:22:38.100> transition<00:22:38.460> happens 00:22:38.990 --> 00:22:39.000 align:start position:0% uh yeah so the state transition happens 00:22:39.000 --> 00:22:41.090 align:start position:0% uh yeah so the state transition happens anytime<00:22:39.659> you<00:22:39.840> want<00:22:39.960> to<00:22:40.080> move<00:22:40.200> to<00:22:40.380> a<00:22:40.500> new<00:22:40.620> Epoch 00:22:41.090 --> 00:22:41.100 align:start position:0% anytime you want to move to a new Epoch 00:22:41.100 --> 00:22:42.770 align:start position:0% anytime you want to move to a new Epoch so<00:22:41.220> if<00:22:41.460> you<00:22:41.580> are<00:22:41.700> participating<00:22:42.240> consistently 00:22:42.770 --> 00:22:42.780 align:start position:0% so if you are participating consistently 00:22:42.780 --> 00:22:45.289 align:start position:0% so if you are participating consistently then<00:22:43.020> yeah<00:22:43.200> it's<00:22:43.380> every<00:22:43.620> Epoch<00:22:44.280> we<00:22:44.880> can<00:22:45.000> adjust 00:22:45.289 --> 00:22:45.299 align:start position:0% then yeah it's every Epoch we can adjust 00:22:45.299 --> 00:22:47.270 align:start position:0% then yeah it's every Epoch we can adjust or<00:22:45.720> testers<00:22:46.140> can<00:22:46.380> set<00:22:46.559> the<00:22:46.679> epoch<00:22:47.100> length 00:22:47.270 --> 00:22:47.280 align:start position:0% or testers can set the epoch length 00:22:47.280 --> 00:22:49.250 align:start position:0% or testers can set the epoch length themselves<00:22:47.700> though<00:22:47.940> so<00:22:48.240> this<00:22:48.360> could<00:22:48.600> be<00:22:48.780> like 00:22:49.250 --> 00:22:49.260 align:start position:0% themselves though so this could be like 00:22:49.260 --> 00:22:50.810 align:start position:0% themselves though so this could be like pretty<00:22:49.380> short<00:22:49.559> maybe<00:22:49.799> one<00:22:50.100> hour<00:22:50.280> or<00:22:50.520> it<00:22:50.700> could 00:22:50.810 --> 00:22:50.820 align:start position:0% pretty short maybe one hour or it could 00:22:50.820 --> 00:22:52.310 align:start position:0% pretty short maybe one hour or it could be<00:22:50.940> like<00:22:51.059> a<00:22:51.240> week<00:22:51.299> or<00:22:51.480> it<00:22:51.600> could<00:22:51.659> be<00:22:51.780> a<00:22:51.900> month<00:22:52.020> or 00:22:52.310 --> 00:22:52.320 align:start position:0% be like a week or it could be a month or 00:22:52.320 --> 00:22:53.810 align:start position:0% be like a week or it could be a month or anything<00:22:52.559> like<00:22:52.799> that<00:22:52.980> and<00:22:53.460> we're<00:22:53.580> also 00:22:53.810 --> 00:22:53.820 align:start position:0% anything like that and we're also 00:22:53.820 --> 00:22:55.850 align:start position:0% anything like that and we're also planning<00:22:54.120> to<00:22:54.240> make<00:22:54.480> it<00:22:54.659> so<00:22:54.780> a<00:22:55.020> testers<00:22:55.320> can<00:22:55.620> set 00:22:55.850 --> 00:22:55.860 align:start position:0% planning to make it so a testers can set 00:22:55.860 --> 00:22:58.190 align:start position:0% planning to make it so a testers can set the<00:22:56.340> max<00:22:56.520> knots<00:22:56.880> value<00:22:57.120> to<00:22:57.419> change<00:22:57.659> like<00:22:58.020> the 00:22:58.190 --> 00:22:58.200 align:start position:0% the max knots value to change like the 00:22:58.200 --> 00:23:00.830 align:start position:0% the max knots value to change like the number<00:22:58.320> of<00:22:58.500> keys<00:22:58.799> the<00:22:58.980> user<00:22:59.220> has<00:22:59.400> for<00:22:59.580> Epoch<00:23:00.120> so 00:23:00.830 --> 00:23:00.840 align:start position:0% number of keys the user has for Epoch so 00:23:00.840 --> 00:23:03.890 align:start position:0% number of keys the user has for Epoch so that<00:23:01.620> would<00:23:01.980> sort<00:23:02.159> of<00:23:02.340> make<00:23:02.640> it<00:23:02.820> so<00:23:03.000> that<00:23:03.179> the 00:23:03.890 --> 00:23:03.900 align:start position:0% that would sort of make it so that the 00:23:03.900 --> 00:23:06.230 align:start position:0% that would sort of make it so that the power<00:23:04.320> key<00:23:04.500> proof<00:23:04.799> is<00:23:04.919> longer<00:23:05.340> but<00:23:05.820> you<00:23:06.000> also 00:23:06.230 --> 00:23:06.240 align:start position:0% power key proof is longer but you also 00:23:06.240 --> 00:23:08.570 align:start position:0% power key proof is longer but you also have<00:23:06.299> like<00:23:06.419> longer<00:23:06.720> epochs<00:23:07.320> so<00:23:07.919> there's<00:23:08.400> sort 00:23:08.570 --> 00:23:08.580 align:start position:0% have like longer epochs so there's sort 00:23:08.580 --> 00:23:11.510 align:start position:0% have like longer epochs so there's sort of<00:23:08.640> a<00:23:08.760> lot<00:23:08.880> of<00:23:09.000> tuning<00:23:09.360> we<00:23:09.539> can<00:23:09.659> do<00:23:09.780> with<00:23:10.200> that 00:23:11.510 --> 00:23:11.520 align:start position:0% of a lot of tuning we can do with that 00:23:11.520 --> 00:23:12.549 align:start position:0% of a lot of tuning we can do with that okay 00:23:12.549 --> 00:23:12.559 align:start position:0% okay 00:23:12.559 --> 00:23:15.770 align:start position:0% okay any<00:23:13.559> thoughts<00:23:13.919> about<00:23:14.039> using<00:23:14.640> dids<00:23:15.299> and<00:23:15.419> VCC 00:23:15.770 --> 00:23:15.780 align:start position:0% any thoughts about using dids and VCC 00:23:15.780 --> 00:23:18.649 align:start position:0% any thoughts about using dids and VCC standards<00:23:16.500> in<00:23:16.799> this<00:23:16.980> implementation<00:23:17.580> uh<00:23:18.539> any 00:23:18.649 --> 00:23:18.659 align:start position:0% standards in this implementation uh any 00:23:18.659 --> 00:23:20.510 align:start position:0% standards in this implementation uh any thoughts<00:23:18.960> about<00:23:19.080> using<00:23:19.320> what<00:23:19.520> decentralized 00:23:20.510 --> 00:23:20.520 align:start position:0% thoughts about using what decentralized 00:23:20.520 --> 00:23:23.029 align:start position:0% thoughts about using what decentralized identifiers<00:23:21.419> and<00:23:21.720> verifiable<00:23:22.260> credentials 00:23:23.029 --> 00:23:23.039 align:start position:0% identifiers and verifiable credentials 00:23:23.039 --> 00:23:24.830 align:start position:0% identifiers and verifiable credentials from<00:23:23.460> the<00:23:23.580> w3c 00:23:24.830 --> 00:23:24.840 align:start position:0% from the w3c 00:23:24.840 --> 00:23:27.470 align:start position:0% from the w3c no<00:23:25.919> um<00:23:26.039> no<00:23:26.520> I<00:23:26.640> have<00:23:26.820> to<00:23:26.880> look<00:23:27.000> into<00:23:27.120> that<00:23:27.299> I'm 00:23:27.470 --> 00:23:27.480 align:start position:0% no um no I have to look into that I'm 00:23:27.480 --> 00:23:28.970 align:start position:0% no um no I have to look into that I'm not<00:23:27.659> aware<00:23:27.900> of<00:23:28.020> actually<00:23:28.200> that<00:23:28.440> but<00:23:28.679> thank<00:23:28.860> you 00:23:28.970 --> 00:23:28.980 align:start position:0% not aware of actually that but thank you 00:23:28.980 --> 00:23:32.090 align:start position:0% not aware of actually that but thank you thank<00:23:29.100> you 00:23:32.090 --> 00:23:32.100 align:start position:0% 00:23:32.100 --> 00:23:33.770 align:start position:0% uh<00:23:32.700> quick<00:23:32.940> question<00:23:33.120> you<00:23:33.360> talked<00:23:33.659> about 00:23:33.770 --> 00:23:33.780 align:start position:0% uh quick question you talked about 00:23:33.780 --> 00:23:37.490 align:start position:0% uh quick question you talked about growth<00:23:34.440> 16<00:23:34.620> verification<00:23:35.159> after<00:23:35.460> eip4844 00:23:37.490 --> 00:23:37.500 align:start position:0% growth 16 verification after eip4844 00:23:37.500 --> 00:23:38.750 align:start position:0% growth 16 verification after eip4844 um I<00:23:37.679> would<00:23:37.799> be<00:23:37.919> curious<00:23:38.159> to<00:23:38.280> understand<00:23:38.400> if 00:23:38.750 --> 00:23:38.760 align:start position:0% um I would be curious to understand if 00:23:38.760 --> 00:23:40.909 align:start position:0% um I would be curious to understand if you<00:23:38.880> have<00:23:39.000> like<00:23:39.120> more<00:23:39.360> detailed<00:23:39.780> thoughts<00:23:40.200> in 00:23:40.909 --> 00:23:40.919 align:start position:0% you have like more detailed thoughts in 00:23:40.919 --> 00:23:42.230 align:start position:0% you have like more detailed thoughts in particular<00:23:41.159> two<00:23:41.400> questions<00:23:41.640> I<00:23:41.940> was<00:23:42.059> thinking 00:23:42.230 --> 00:23:42.240 align:start position:0% particular two questions I was thinking 00:23:42.240 --> 00:23:45.230 align:start position:0% particular two questions I was thinking of<00:23:42.419> those<00:23:42.539> like<00:23:42.840> one<00:23:43.620> uh<00:23:44.340> if<00:23:44.700> you<00:23:44.880> don't<00:23:45.000> have 00:23:45.230 --> 00:23:45.240 align:start position:0% of those like one uh if you don't have 00:23:45.240 --> 00:23:48.110 align:start position:0% of those like one uh if you don't have your<00:23:45.840> uh<00:23:46.260> I<00:23:46.559> guess<00:23:46.620> proof<00:23:47.340> in<00:23:47.460> call<00:23:47.700> data 00:23:48.110 --> 00:23:48.120 align:start position:0% your uh I guess proof in call data 00:23:48.120 --> 00:23:50.029 align:start position:0% your uh I guess proof in call data instead<00:23:48.720> it's<00:23:48.900> in<00:23:49.080> the<00:23:49.200> blob<00:23:49.440> you<00:23:49.740> would<00:23:49.860> have 00:23:50.029 --> 00:23:50.039 align:start position:0% instead it's in the blob you would have 00:23:50.039 --> 00:23:52.310 align:start position:0% instead it's in the blob you would have to<00:23:50.100> verify<00:23:50.400> there's<00:23:50.700> some<00:23:50.940> batch<00:23:51.299> proof<00:23:52.080> right 00:23:52.310 --> 00:23:52.320 align:start position:0% to verify there's some batch proof right 00:23:52.320 --> 00:23:55.909 align:start position:0% to verify there's some batch proof right opening<00:23:53.100> your<00:23:53.360> Kate<00:23:54.360> polynomial<00:23:54.960> inside<00:23:55.620> this 00:23:55.909 --> 00:23:55.919 align:start position:0% opening your Kate polynomial inside this 00:23:55.919 --> 00:23:58.909 align:start position:0% opening your Kate polynomial inside this narc<00:23:56.280> and<00:23:56.520> then<00:23:56.640> doing<00:23:56.940> recursive<00:23:57.539> rules<00:23:57.840> or<00:23:58.620> I 00:23:58.909 --> 00:23:58.919 align:start position:0% narc and then doing recursive rules or I 00:23:58.919 --> 00:24:00.110 align:start position:0% narc and then doing recursive rules or I guess<00:23:59.100> what<00:23:59.220> is<00:23:59.400> the<00:23:59.520> exact<00:23:59.760> setup<00:24:00.000> you're 00:24:00.110 --> 00:24:00.120 align:start position:0% guess what is the exact setup you're 00:24:00.120 --> 00:24:03.470 align:start position:0% guess what is the exact setup you're thinking<00:24:00.419> of<00:24:00.960> uh<00:24:01.919> do<00:24:02.520> you<00:24:02.640> mean<00:24:02.700> gross16<00:24:03.120> or<00:24:03.360> do 00:24:03.470 --> 00:24:03.480 align:start position:0% thinking of uh do you mean gross16 or do 00:24:03.480 --> 00:24:05.990 align:start position:0% thinking of uh do you mean gross16 or do you<00:24:03.539> mean<00:24:03.659> Planck<00:24:04.140> either<00:24:04.620> one<00:24:04.860> I<00:24:05.159> guess<00:24:05.340> right 00:24:05.990 --> 00:24:06.000 align:start position:0% you mean Planck either one I guess right 00:24:06.000 --> 00:24:07.970 align:start position:0% you mean Planck either one I guess right so<00:24:06.720> sorry<00:24:07.020> that<00:24:07.260> makes<00:24:07.440> a<00:24:07.559> little<00:24:07.620> bit<00:24:07.740> hard<00:24:07.860> to 00:24:07.970 --> 00:24:07.980 align:start position:0% so sorry that makes a little bit hard to 00:24:07.980 --> 00:24:09.590 align:start position:0% so sorry that makes a little bit hard to hear<00:24:08.340> but<00:24:08.520> it's<00:24:08.700> just<00:24:08.820> like<00:24:09.000> a<00:24:09.179> question<00:24:09.360> about 00:24:09.590 --> 00:24:09.600 align:start position:0% hear but it's just like a question about 00:24:09.600 --> 00:24:11.390 align:start position:0% hear but it's just like a question about how<00:24:10.080> do<00:24:10.260> we<00:24:10.440> aggregate<00:24:10.799> these<00:24:10.980> proofs<00:24:11.159> or<00:24:11.280> how 00:24:11.390 --> 00:24:11.400 align:start position:0% how do we aggregate these proofs or how 00:24:11.400 --> 00:24:13.250 align:start position:0% how do we aggregate these proofs or how do<00:24:11.520> we<00:24:11.580> sequence<00:24:11.820> them<00:24:12.000> for<00:24:12.240> aggregation 00:24:13.250 --> 00:24:13.260 align:start position:0% do we sequence them for aggregation 00:24:13.260 --> 00:24:17.390 align:start position:0% do we sequence them for aggregation in<00:24:13.740> a<00:24:13.860> post<00:24:13.980> eip44<00:24:14.700> world<00:24:15.179> right<00:24:15.539> yeah<00:24:16.039> yeah<00:24:17.039> so 00:24:17.390 --> 00:24:17.400 align:start position:0% in a post eip44 world right yeah yeah so 00:24:17.400 --> 00:24:18.770 align:start position:0% in a post eip44 world right yeah yeah so I<00:24:17.700> sort<00:24:17.820> of<00:24:17.940> touched<00:24:18.179> on<00:24:18.240> it<00:24:18.360> a<00:24:18.480> little<00:24:18.539> bit<00:24:18.659> but 00:24:18.770 --> 00:24:18.780 align:start position:0% I sort of touched on it a little bit but 00:24:18.780 --> 00:24:20.270 align:start position:0% I sort of touched on it a little bit but I<00:24:18.900> didn't<00:24:18.960> talk<00:24:19.140> about<00:24:19.200> it<00:24:19.380> much<00:24:19.500> but<00:24:20.100> one 00:24:20.270 --> 00:24:20.280 align:start position:0% I didn't talk about it much but one 00:24:20.280 --> 00:24:22.850 align:start position:0% I didn't talk about it much but one approach<00:24:20.640> is<00:24:21.000> users<00:24:21.480> can't<00:24:21.960> send<00:24:22.440> the<00:24:22.740> public 00:24:22.850 --> 00:24:22.860 align:start position:0% approach is users can't send the public 00:24:22.860 --> 00:24:24.409 align:start position:0% approach is users can't send the public signals<00:24:23.220> of<00:24:23.340> the<00:24:23.460> proof<00:24:23.760> and<00:24:24.000> then<00:24:24.120> the<00:24:24.240> hash 00:24:24.409 --> 00:24:24.419 align:start position:0% signals of the proof and then the hash 00:24:24.419 --> 00:24:26.270 align:start position:0% signals of the proof and then the hash of<00:24:24.600> the<00:24:24.720> proof<00:24:25.020> onto<00:24:25.260> the<00:24:25.380> blockchain<00:24:25.740> and 00:24:26.270 --> 00:24:26.280 align:start position:0% of the proof onto the blockchain and 00:24:26.280 --> 00:24:28.490 align:start position:0% of the proof onto the blockchain and then<00:24:26.340> we<00:24:26.520> form<00:24:26.700> a<00:24:26.880> hash<00:24:27.059> chain<00:24:27.299> on<00:24:27.480> chain<00:24:27.720> and 00:24:28.490 --> 00:24:28.500 align:start position:0% then we form a hash chain on chain and 00:24:28.500 --> 00:24:30.350 align:start position:0% then we form a hash chain on chain and then<00:24:28.620> the<00:24:28.919> aggregator<00:24:29.340> is<00:24:29.520> able<00:24:29.760> to<00:24:29.820> make<00:24:30.120> a 00:24:30.350 --> 00:24:30.360 align:start position:0% then the aggregator is able to make a 00:24:30.360 --> 00:24:32.990 align:start position:0% then the aggregator is able to make a recursive<00:24:30.720> proof<00:24:31.080> using<00:24:31.620> that<00:24:32.039> data<00:24:32.400> and<00:24:32.820> only 00:24:32.990 --> 00:24:33.000 align:start position:0% recursive proof using that data and only 00:24:33.000 --> 00:24:35.029 align:start position:0% recursive proof using that data and only put<00:24:33.240> a<00:24:33.360> hash<00:24:33.480> chain<00:24:33.720> on<00:24:33.960> chain 00:24:35.029 --> 00:24:35.039 align:start position:0% put a hash chain on chain 00:24:35.039 --> 00:24:36.890 align:start position:0% put a hash chain on chain um<00:24:35.100> but<00:24:35.280> this<00:24:35.400> still<00:24:35.580> involves<00:24:36.000> like<00:24:36.360> the 00:24:36.890 --> 00:24:36.900 align:start position:0% um but this still involves like the 00:24:36.900 --> 00:24:38.630 align:start position:0% um but this still involves like the aggregator<00:24:37.320> receiving<00:24:37.740> the<00:24:37.980> full<00:24:38.159> proof<00:24:38.460> and 00:24:38.630 --> 00:24:38.640 align:start position:0% aggregator receiving the full proof and 00:24:38.640 --> 00:24:40.789 align:start position:0% aggregator receiving the full proof and then<00:24:38.760> like<00:24:38.940> calculating<00:24:39.299> the<00:24:39.539> hash 00:24:40.789 --> 00:24:40.799 align:start position:0% then like calculating the hash 00:24:40.799 --> 00:24:41.690 align:start position:0% then like calculating the hash um 00:24:41.690 --> 00:24:41.700 align:start position:0% um 00:24:41.700 --> 00:24:44.149 align:start position:0% um we<00:24:42.240> honestly<00:24:42.600> we<00:24:42.840> haven't<00:24:42.960> gotten 00:24:44.149 --> 00:24:44.159 align:start position:0% we honestly we haven't gotten 00:24:44.159 --> 00:24:46.250 align:start position:0% we honestly we haven't gotten uh<00:24:44.880> we're<00:24:45.120> not<00:24:45.360> really<00:24:45.480> close<00:24:45.659> to<00:24:45.840> doing<00:24:46.080> that 00:24:46.250 --> 00:24:46.260 align:start position:0% uh we're not really close to doing that 00:24:46.260 --> 00:24:48.710 align:start position:0% uh we're not really close to doing that yet<00:24:46.500> like<00:24:46.980> we're<00:24:47.159> proving<00:24:48.059> especially<00:24:48.539> for 00:24:48.710 --> 00:24:48.720 align:start position:0% yet like we're proving especially for 00:24:48.720 --> 00:24:50.090 align:start position:0% yet like we're proving especially for like<00:24:48.840> solidity<00:24:49.260> approvers<00:24:49.679> are<00:24:49.799> a<00:24:49.919> little<00:24:49.980> bit 00:24:50.090 --> 00:24:50.100 align:start position:0% like solidity approvers are a little bit 00:24:50.100 --> 00:24:51.470 align:start position:0% like solidity approvers are a little bit far<00:24:50.280> out 00:24:51.470 --> 00:24:51.480 align:start position:0% far out 00:24:51.480 --> 00:24:52.970 align:start position:0% far out um<00:24:51.600> but<00:24:52.080> yeah<00:24:52.200> it's<00:24:52.380> probably<00:24:52.620> going<00:24:52.799> to<00:24:52.919> be 00:24:52.970 --> 00:24:52.980 align:start position:0% um but yeah it's probably going to be 00:24:52.980 --> 00:24:54.770 align:start position:0% um but yeah it's probably going to be some<00:24:53.340> sort<00:24:53.460> of<00:24:53.580> optimistic<00:24:54.120> system<00:24:54.299> so<00:24:54.600> the 00:24:54.770 --> 00:24:54.780 align:start position:0% some sort of optimistic system so the 00:24:54.780 --> 00:25:03.190 align:start position:0% some sort of optimistic system so the user<00:24:55.080> experience<00:24:55.440> is<00:24:55.679> pretty<00:24:55.980> good 00:25:03.190 --> 00:25:03.200 align:start position:0% 00:25:03.200 --> 00:25:06.740 align:start position:0% thank<00:25:04.200> you<00:25:04.320> thank<00:25:04.559> you<00:25:04.679> all