WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.770 align:start position:0% [Applause] 00:00:12.770 --> 00:00:12.780 align:start position:0% 00:00:12.780 --> 00:00:16.260 align:start position:0% everyone<00:00:13.780> let's<00:00:13.990> get<00:00:14.170> started<00:00:14.969> the<00:00:15.969> my<00:00:16.119> name 00:00:16.260 --> 00:00:16.270 align:start position:0% everyone let's get started the my name 00:00:16.270 --> 00:00:18.000 align:start position:0% everyone let's get started the my name is<00:00:16.390> miracle<00:00:16.690> chef<00:00:16.990> Smith<00:00:17.230> there<00:00:17.560> we<00:00:17.680> talked 00:00:18.000 --> 00:00:18.010 align:start position:0% is miracle chef Smith there we talked 00:00:18.010 --> 00:00:21.810 align:start position:0% is miracle chef Smith there we talked about<00:00:18.599> shrubs<00:00:19.599> some<00:00:20.439> new<00:00:20.619> suits<00:00:21.220> have<00:00:21.430> style 00:00:21.810 --> 00:00:21.820 align:start position:0% about shrubs some new suits have style 00:00:21.820 --> 00:00:29.130 align:start position:0% about shrubs some new suits have style gas<00:00:22.480> efficient<00:00:23.279> privacy<00:00:24.279> protocol<00:00:28.050> it's<00:00:29.050> a 00:00:29.130 --> 00:00:29.140 align:start position:0% gas efficient privacy protocol it's a 00:00:29.140 --> 00:00:31.140 align:start position:0% gas efficient privacy protocol it's a mr.<00:00:29.410> joint<00:00:29.619> work<00:00:29.830> with<00:00:30.070> selling<00:00:30.609> herbs<00:00:30.760> and 00:00:31.140 --> 00:00:31.150 align:start position:0% mr. joint work with selling herbs and 00:00:31.150 --> 00:00:48.270 align:start position:0% mr. joint work with selling herbs and matter<00:00:32.020> labs<00:00:32.730> with<00:00:33.730> a<00:00:33.790> public<00:00:34.120> folks<00:00:47.160> first<00:00:48.160> of 00:00:48.270 --> 00:00:48.280 align:start position:0% matter labs with a public folks first of 00:00:48.280 --> 00:00:51.540 align:start position:0% matter labs with a public folks first of all<00:00:48.370> like<00:00:48.610> privacy<00:00:49.059> wine<00:00:49.719> shops<00:00:50.140> at<00:00:50.469> all<00:00:50.620> so 00:00:51.540 --> 00:00:51.550 align:start position:0% all like privacy wine shops at all so 00:00:51.550 --> 00:00:54.660 align:start position:0% all like privacy wine shops at all so maybe<00:00:51.670> this<00:00:51.879> is<00:00:52.090> some<00:00:52.270> quick<00:00:53.050> context<00:00:53.920> so 00:00:54.660 --> 00:00:54.670 align:start position:0% maybe this is some quick context so 00:00:54.670 --> 00:00:58.229 align:start position:0% maybe this is some quick context so seller<00:00:54.940> is<00:00:55.300> essentially<00:00:55.899> a<00:00:56.200> mobile-first<00:00:57.239> and 00:00:58.229 --> 00:00:58.239 align:start position:0% seller is essentially a mobile-first and 00:00:58.239 --> 00:01:03.389 align:start position:0% seller is essentially a mobile-first and a<00:00:58.329> theory<00:01:00.180> which<00:01:01.180> allows<00:01:02.170> us<00:01:02.500> to<00:01:02.649> build<00:01:02.829> a<00:01:03.070> user 00:01:03.389 --> 00:01:03.399 align:start position:0% a theory which allows us to build a user 00:01:03.399 --> 00:01:05.550 align:start position:0% a theory which allows us to build a user experience<00:01:03.579> like<00:01:04.030> this<00:01:04.210> and<00:01:04.509> stove<00:01:04.720> it<00:01:04.960> has<00:01:05.199> a 00:01:05.550 --> 00:01:05.560 align:start position:0% experience like this and stove it has a 00:01:05.560 --> 00:01:13.320 align:start position:0% experience like this and stove it has a lot<00:01:05.710> of<00:01:05.740> focus<00:01:06.009> on<00:01:07.110> like<00:01:08.110> planked<00:01:09.869> we<00:01:10.869> use 00:01:13.320 --> 00:01:13.330 align:start position:0% 00:01:13.330 --> 00:01:16.080 align:start position:0% to<00:01:13.780> change<00:01:14.020> we<00:01:14.770> have<00:01:14.800> a<00:01:15.010> stable<00:01:15.400> point<00:01:15.640> that's 00:01:16.080 --> 00:01:16.090 align:start position:0% to change we have a stable point that's 00:01:16.090 --> 00:01:17.880 align:start position:0% to change we have a stable point that's back<00:01:16.330> to<00:01:16.570> park<00:01:16.810> by<00:01:16.960> eat<00:01:17.140> which<00:01:17.440> is<00:01:17.470> why<00:01:17.740> it's 00:01:17.880 --> 00:01:17.890 align:start position:0% back to park by eat which is why it's 00:01:17.890 --> 00:01:20.640 align:start position:0% back to park by eat which is why it's relevant<00:01:18.070> to<00:01:18.430> the<00:01:18.550> community<00:01:19.530> and<00:01:20.530> then<00:01:20.620> we 00:01:20.640 --> 00:01:20.650 align:start position:0% relevant to the community and then we 00:01:20.650 --> 00:01:22.110 align:start position:0% relevant to the community and then we have<00:01:20.860> a<00:01:20.890> way<00:01:21.040> to<00:01:21.070> send<00:01:21.370> a<00:01:21.550> mistake<00:01:21.940> phone 00:01:22.110 --> 00:01:22.120 align:start position:0% have a way to send a mistake phone 00:01:22.120 --> 00:01:24.480 align:start position:0% have a way to send a mistake phone numbers<00:01:22.450> so<00:01:22.720> all<00:01:23.380> of<00:01:23.530> that<00:01:23.650> means<00:01:23.860> that<00:01:23.980> you 00:01:24.480 --> 00:01:24.490 align:start position:0% numbers so all of that means that you 00:01:24.490 --> 00:01:28.050 align:start position:0% numbers so all of that means that you want<00:01:24.670> to<00:01:24.820> send<00:01:25.060> the<00:01:25.120> payment<00:01:25.360> to<00:01:26.260> a<00:01:26.290> friend<00:01:27.060> say 00:01:28.050 --> 00:01:28.060 align:start position:0% want to send the payment to a friend say 00:01:28.060 --> 00:01:32.280 align:start position:0% want to send the payment to a friend say you<00:01:28.120> want<00:01:28.300> to<00:01:28.330> kiss<00:01:28.510> him<00:01:28.690> back<00:01:28.960> or<00:01:30.000> coffee<00:01:31.290> you 00:01:32.280 --> 00:01:32.290 align:start position:0% you want to kiss him back or coffee you 00:01:32.290 --> 00:01:34.020 align:start position:0% you want to kiss him back or coffee you can<00:01:32.410> find<00:01:32.680> them<00:01:32.830> in<00:01:32.920> your<00:01:32.950> contact<00:01:33.460> list<00:01:33.520> and 00:01:34.020 --> 00:01:34.030 align:start position:0% can find them in your contact list and 00:01:34.030 --> 00:01:38.150 align:start position:0% can find them in your contact list and since<00:01:34.780> hello<00:01:35.970> maybe<00:01:36.970> central<00:01:37.300> that's<00:01:37.450> where 00:01:38.150 --> 00:01:38.160 align:start position:0% since hello maybe central that's where 00:01:38.160 --> 00:01:43.260 align:start position:0% since hello maybe central that's where we<00:01:39.160> spend<00:01:39.880> say<00:01:40.260> 500<00:01:41.430> dollars<00:01:42.430> to<00:01:42.460> them<00:01:42.850> and 00:01:43.260 --> 00:01:43.270 align:start position:0% we spend say 500 dollars to them and 00:01:43.270 --> 00:01:49.280 align:start position:0% we spend say 500 dollars to them and since<00:01:43.750> it's<00:01:43.930> 2019<00:01:44.890> of<00:01:45.850> course<00:01:47.160> emoji<00:01:48.160> and 00:01:49.280 --> 00:01:49.290 align:start position:0% since it's 2019 of course emoji and 00:01:49.290 --> 00:01:51.600 align:start position:0% since it's 2019 of course emoji and uncritically<00:01:50.290> to<00:01:50.650> pay<00:01:50.890> for<00:01:51.160> this<00:01:51.250> transaction 00:01:51.600 --> 00:01:51.610 align:start position:0% uncritically to pay for this transaction 00:01:51.610 --> 00:01:54.690 align:start position:0% uncritically to pay for this transaction using<00:01:52.120> the<00:01:52.330> stable<00:01:52.690> target<00:01:53.020> itself<00:01:53.520> and<00:01:54.520> so 00:01:54.690 --> 00:01:54.700 align:start position:0% using the stable target itself and so 00:01:54.700 --> 00:01:56.910 align:start position:0% using the stable target itself and so the<00:01:54.820> whole<00:01:55.000> experience<00:01:55.420> is<00:01:55.720> quite<00:01:55.900> quick<00:01:56.229> it's 00:01:56.910 --> 00:01:56.920 align:start position:0% the whole experience is quite quick it's 00:01:56.920 --> 00:01:58.500 align:start position:0% the whole experience is quite quick it's fully<00:01:57.220> decentralized<00:01:57.400> this<00:01:58.060> is<00:01:58.180> going<00:01:58.360> to<00:01:58.420> go 00:01:58.500 --> 00:01:58.510 align:start position:0% fully decentralized this is going to go 00:01:58.510 --> 00:02:03.480 align:start position:0% fully decentralized this is going to go like<00:01:58.690> mine<00:02:00.750> it's<00:02:01.750> like<00:02:01.960> my<00:02:02.140> protocol<00:02:02.650> and<00:02:03.369> so 00:02:03.480 --> 00:02:03.490 align:start position:0% like mine it's like my protocol and so 00:02:03.490 --> 00:02:05.760 align:start position:0% like mine it's like my protocol and so it<00:02:03.550> allows<00:02:03.760> you<00:02:03.970> to<00:02:04.150> recreate<00:02:04.540> a<00:02:04.990> venmo<00:02:05.380> or 00:02:05.760 --> 00:02:05.770 align:start position:0% it allows you to recreate a venmo or 00:02:05.770 --> 00:02:09.090 align:start position:0% it allows you to recreate a venmo or PayPal<00:02:06.220> experience<00:02:07.560> that<00:02:08.560> is<00:02:08.800> fully 00:02:09.090 --> 00:02:09.100 align:start position:0% PayPal experience that is fully 00:02:09.100 --> 00:02:11.430 align:start position:0% PayPal experience that is fully permissionless<00:02:09.610> will<00:02:10.090> appear<00:02:10.390> here<00:02:10.630> so 00:02:11.430 --> 00:02:11.440 align:start position:0% permissionless will appear here so 00:02:11.440 --> 00:02:14.670 align:start position:0% permissionless will appear here so that's<00:02:11.620> though<00:02:11.890> and<00:02:12.990> given<00:02:13.990> that<00:02:14.080> it<00:02:14.200> has<00:02:14.320> this 00:02:14.670 --> 00:02:14.680 align:start position:0% that's though and given that it has this 00:02:14.680 --> 00:02:18.870 align:start position:0% that's though and given that it has this really<00:02:15.190> big<00:02:15.520> focus<00:02:16.150> on<00:02:17.430> some<00:02:18.430> of<00:02:18.459> the<00:02:18.610> things 00:02:18.870 --> 00:02:18.880 align:start position:0% really big focus on some of the things 00:02:18.880 --> 00:02:20.250 align:start position:0% really big focus on some of the things that<00:02:19.060> are<00:02:19.239> useful<00:02:19.360> as<00:02:19.690> a<00:02:19.720> medium<00:02:20.110> of<00:02:20.170> exchange 00:02:20.250 --> 00:02:20.260 align:start position:0% that are useful as a medium of exchange 00:02:20.260 --> 00:02:24.090 align:start position:0% that are useful as a medium of exchange sending<00:02:21.190> stable<00:02:21.790> value<00:02:22.140> we<00:02:23.140> hypothesize<00:02:24.070> that 00:02:24.090 --> 00:02:24.100 align:start position:0% sending stable value we hypothesize that 00:02:24.100 --> 00:02:27.440 align:start position:0% sending stable value we hypothesize that privacy<00:02:24.850> is<00:02:24.970> actually<00:02:25.420> even<00:02:26.350> more<00:02:26.709> important 00:02:27.440 --> 00:02:27.450 align:start position:0% privacy is actually even more important 00:02:27.450 --> 00:02:31.350 align:start position:0% privacy is actually even more important for<00:02:28.450> such<00:02:29.230> a<00:02:29.260> network<00:02:29.470> Bank<00:02:29.980> for<00:02:30.670> points<00:02:31.150> that 00:02:31.350 --> 00:02:31.360 align:start position:0% for such a network Bank for points that 00:02:31.360 --> 00:02:34.800 align:start position:0% for such a network Bank for points that are<00:02:31.660> primarily<00:02:32.260> store<00:02:32.739> of<00:02:32.830> elements<00:02:33.630> and<00:02:34.630> so 00:02:34.800 --> 00:02:34.810 align:start position:0% are primarily store of elements and so 00:02:34.810 --> 00:02:37.050 align:start position:0% are primarily store of elements and so we<00:02:34.900> spent<00:02:35.170> a<00:02:35.380> fair<00:02:35.650> amount<00:02:35.709> of<00:02:36.430> time<00:02:36.610> thinking 00:02:37.050 --> 00:02:37.060 align:start position:0% we spent a fair amount of time thinking 00:02:37.060 --> 00:02:40.740 align:start position:0% we spent a fair amount of time thinking about<00:02:37.300> that<00:02:38.140> privacy<00:02:38.800> or<00:02:39.519> so<00:02:39.760> and<00:02:40.150> again<00:02:40.239> solo 00:02:40.740 --> 00:02:40.750 align:start position:0% about that privacy or so and again solo 00:02:40.750 --> 00:02:43.890 align:start position:0% about that privacy or so and again solo is<00:02:41.220> here<00:02:42.220> a<00:02:42.250> minute<00:02:42.519> passed<00:02:42.850> the<00:02:43.060> DMV<00:02:43.209> so 00:02:43.890 --> 00:02:43.900 align:start position:0% is here a minute passed the DMV so 00:02:43.900 --> 00:02:49.920 align:start position:0% is here a minute passed the DMV so everything<00:02:44.290> that<00:02:48.269> so<00:02:49.269> we<00:02:49.360> have<00:02:49.510> three<00:02:49.750> goals 00:02:49.920 --> 00:02:49.930 align:start position:0% everything that so we have three goals 00:02:49.930 --> 00:02:55.259 align:start position:0% everything that so we have three goals we<00:02:50.920> wanted<00:02:51.340> to<00:02:52.950> make<00:02:53.950> the<00:02:54.250> balances<00:02:54.820> of<00:02:55.150> these 00:02:55.259 --> 00:02:55.269 align:start position:0% we wanted to make the balances of these 00:02:55.269 --> 00:02:58.080 align:start position:0% we wanted to make the balances of these reductions<00:02:55.630> only<00:02:56.260> private<00:02:56.730> we<00:02:57.730> didn't<00:02:57.970> want 00:02:58.080 --> 00:02:58.090 align:start position:0% reductions only private we didn't want 00:02:58.090 --> 00:03:00.390 align:start position:0% reductions only private we didn't want the<00:02:58.180> ability<00:02:58.420> we<00:02:59.230> wanted<00:02:59.560> to<00:02:59.709> keep<00:02:59.920> the 00:03:00.390 --> 00:03:00.400 align:start position:0% the ability we wanted to keep the 00:03:00.400 --> 00:03:03.630 align:start position:0% the ability we wanted to keep the recipient<00:03:01.239> and<00:03:01.510> send<00:03:01.810> their<00:03:01.930> addresses<00:03:02.640> as 00:03:03.630 --> 00:03:03.640 align:start position:0% recipient and send their addresses as 00:03:03.640 --> 00:03:10.110 align:start position:0% recipient and send their addresses as well<00:03:06.959> isn't<00:03:07.959> that<00:03:08.200> common<00:03:08.530> today<00:03:08.790> in<00:03:09.790> other 00:03:10.110 --> 00:03:10.120 align:start position:0% well isn't that common today in other 00:03:10.120 --> 00:03:13.229 align:start position:0% well isn't that common today in other theory<00:03:10.660> based<00:03:11.110> privacy<00:03:11.650> no<00:03:11.980> solutions<00:03:12.430> and 00:03:13.229 --> 00:03:13.239 align:start position:0% theory based privacy no solutions and 00:03:13.239 --> 00:03:14.670 align:start position:0% theory based privacy no solutions and then<00:03:13.330> finally<00:03:13.660> we<00:03:13.780> wanted<00:03:14.019> all<00:03:14.170> of<00:03:14.200> this<00:03:14.440> to 00:03:14.670 --> 00:03:14.680 align:start position:0% then finally we wanted all of this to 00:03:14.680 --> 00:03:17.370 align:start position:0% then finally we wanted all of this to work<00:03:14.709> really<00:03:15.340> well<00:03:15.459> on<00:03:16.060> mobile<00:03:16.299> again<00:03:17.110> it's 00:03:17.370 --> 00:03:17.380 align:start position:0% work really well on mobile again it's 00:03:17.380 --> 00:03:26.550 align:start position:0% work really well on mobile again it's mobile<00:03:17.590> first<00:03:17.860> so<00:03:18.700> we<00:03:18.790> want<00:03:19.000> to<00:03:24.990> look<00:03:25.990> at<00:03:26.200> seek 00:03:26.550 --> 00:03:26.560 align:start position:0% mobile first so we want to look at seek 00:03:26.560 --> 00:03:32.089 align:start position:0% mobile first so we want to look at seek apps<00:03:26.770> and<00:03:27.069> start<00:03:27.220> reporting<00:03:27.370> any<00:03:27.730> cash<00:03:28.080> into 00:03:32.089 --> 00:03:32.099 align:start position:0% 00:03:32.099 --> 00:03:34.940 align:start position:0% and<00:03:32.640> we<00:03:32.760> quickly<00:03:32.879> run<00:03:33.239> into<00:03:33.599> a<00:03:33.629> few<00:03:34.019> issues<00:03:34.080> so 00:03:34.940 --> 00:03:34.950 align:start position:0% and we quickly run into a few issues so 00:03:34.950 --> 00:03:38.000 align:start position:0% and we quickly run into a few issues so everyone<00:03:35.750> the<00:03:36.750> gas<00:03:36.900> cost<00:03:37.260> is<00:03:37.500> perhaps<00:03:37.650> not 00:03:38.000 --> 00:03:38.010 align:start position:0% everyone the gas cost is perhaps not 00:03:38.010 --> 00:03:40.880 align:start position:0% everyone the gas cost is perhaps not surprisingly<00:03:38.519> quite<00:03:38.849> high<00:03:39.409> and<00:03:40.409> number<00:03:40.709> two 00:03:40.880 --> 00:03:40.890 align:start position:0% surprisingly quite high and number two 00:03:40.890 --> 00:03:42.589 align:start position:0% surprisingly quite high and number two the<00:03:41.579> mobile<00:03:41.819> support<00:03:42.120> it's<00:03:42.209> actually<00:03:42.510> not 00:03:42.589 --> 00:03:42.599 align:start position:0% the mobile support it's actually not 00:03:42.599 --> 00:03:45.410 align:start position:0% the mobile support it's actually not that<00:03:42.659> great<00:03:43.159> except<00:03:44.159> for<00:03:44.189> this<00:03:44.370> talk<00:03:44.610> most<00:03:45.209> our 00:03:45.410 --> 00:03:45.420 align:start position:0% that great except for this talk most our 00:03:45.420 --> 00:03:48.860 align:start position:0% that great except for this talk most our focus<00:03:45.900> on<00:03:46.170> the<00:03:47.040> former<00:03:47.519> and<00:03:48.390> just<00:03:48.629> kind<00:03:48.810> of 00:03:48.860 --> 00:03:48.870 align:start position:0% focus on the former and just kind of 00:03:48.870 --> 00:03:50.569 align:start position:0% focus on the former and just kind of things<00:03:49.079> a<00:03:49.200> little<00:03:49.440> bit<00:03:49.560> about<00:03:49.769> possible 00:03:50.569 --> 00:03:50.579 align:start position:0% things a little bit about possible 00:03:50.579 --> 00:03:55.190 align:start position:0% things a little bit about possible solutions<00:03:51.060> for<00:03:51.360> the<00:03:52.140> light<00:03:53.930> so<00:03:54.930> maybe<00:03:55.079> just 00:03:55.190 --> 00:03:55.200 align:start position:0% solutions for the light so maybe just 00:03:55.200 --> 00:03:59.470 align:start position:0% solutions for the light so maybe just some<00:03:55.500> super<00:03:56.190> quick<00:03:56.400> background<00:03:56.819> on<00:03:57.239> Z<00:03:57.569> cash 00:03:59.470 --> 00:03:59.480 align:start position:0% some super quick background on Z cash 00:03:59.480 --> 00:04:02.899 align:start position:0% some super quick background on Z cash just<00:04:00.480> to<00:04:00.569> get<00:04:00.750> everyone<00:04:00.989> on<00:04:01.319> the<00:04:01.349> same<00:04:01.470> page<00:04:01.909> so 00:04:02.899 --> 00:04:02.909 align:start position:0% just to get everyone on the same page so 00:04:02.909 --> 00:04:05.149 align:start position:0% just to get everyone on the same page so NC<00:04:03.359> captures<00:04:03.840> a<00:04:03.900> number<00:04:04.170> of<00:04:04.260> operations<00:04:04.829> one 00:04:05.149 --> 00:04:05.159 align:start position:0% NC captures a number of operations one 00:04:05.159 --> 00:04:08.000 align:start position:0% NC captures a number of operations one of<00:04:05.280> which<00:04:05.459> is<00:04:05.760> the<00:04:06.510> stealing<00:04:07.079> operation<00:04:07.680> so 00:04:08.000 --> 00:04:08.010 align:start position:0% of which is the stealing operation so 00:04:08.010 --> 00:04:12.190 align:start position:0% of which is the stealing operation so that's<00:04:08.220> when<00:04:09.030> you<00:04:09.150> take<00:04:09.450> one<00:04:10.400> public<00:04:11.400> the<00:04:11.519> SEC 00:04:12.190 --> 00:04:12.200 align:start position:0% that's when you take one public the SEC 00:04:12.200 --> 00:04:15.410 align:start position:0% that's when you take one public the SEC and<00:04:13.200> eternities<00:04:14.010> for<00:04:14.040> one<00:04:14.370> private<00:04:14.700> sector 00:04:15.410 --> 00:04:15.420 align:start position:0% and eternities for one private sector 00:04:15.420 --> 00:04:17.000 align:start position:0% and eternities for one private sector lean<00:04:16.229> operation 00:04:17.000 --> 00:04:17.010 align:start position:0% lean operation 00:04:17.010 --> 00:04:19.280 align:start position:0% lean operation the<00:04:17.490> way<00:04:17.610> that<00:04:17.760> you<00:04:17.880> do<00:04:18.060> that<00:04:18.210> is<00:04:18.480> you<00:04:18.630> create<00:04:18.870> a 00:04:19.280 --> 00:04:19.290 align:start position:0% the way that you do that is you create a 00:04:19.290 --> 00:04:21.890 align:start position:0% the way that you do that is you create a serial<00:04:19.710> number<00:04:20.150> and<00:04:21.150> then<00:04:21.360> you<00:04:21.450> sent<00:04:21.690> us<00:04:21.810> and 00:04:21.890 --> 00:04:21.900 align:start position:0% serial number and then you sent us and 00:04:21.900 --> 00:04:24.320 align:start position:0% serial number and then you sent us and running<00:04:22.230> this<00:04:22.320> from<00:04:22.470> somewhere<00:04:22.830> and<00:04:23.640> you<00:04:23.970> can 00:04:24.320 --> 00:04:24.330 align:start position:0% running this from somewhere and you can 00:04:24.330 --> 00:04:28.070 align:start position:0% running this from somewhere and you can compute<00:04:25.200> a<00:04:25.470> commitment<00:04:26.570> to<00:04:27.570> that<00:04:27.750> serial 00:04:28.070 --> 00:04:28.080 align:start position:0% compute a commitment to that serial 00:04:28.080 --> 00:04:33.320 align:start position:0% compute a commitment to that serial number<00:04:28.670> yeah<00:04:30.380> and<00:04:31.380> then<00:04:31.590> you<00:04:31.710> create<00:04:32.070> a<00:04:32.460> public 00:04:33.320 --> 00:04:33.330 align:start position:0% number yeah and then you create a public 00:04:33.330 --> 00:04:35.840 align:start position:0% number yeah and then you create a public transaction<00:04:33.720> that<00:04:34.530> shares<00:04:34.920> that<00:04:35.280> commitment 00:04:35.840 --> 00:04:35.850 align:start position:0% transaction that shares that commitment 00:04:35.850 --> 00:04:39.440 align:start position:0% transaction that shares that commitment while<00:04:36.540> spending<00:04:36.930> and<00:04:37.440> one<00:04:37.650> sec<00:04:38.010> and<00:04:38.450> the 00:04:39.440 --> 00:04:39.450 align:start position:0% while spending and one sec and the 00:04:39.450 --> 00:04:41.480 align:start position:0% while spending and one sec and the miners<00:04:39.930> will<00:04:40.140> add<00:04:40.350> that<00:04:40.560> protection<00:04:41.190> will 00:04:41.480 --> 00:04:41.490 align:start position:0% miners will add that protection will 00:04:41.490 --> 00:04:44.720 align:start position:0% miners will add that protection will take<00:04:41.700> that<00:04:41.940> SEC<00:04:42.240> put<00:04:42.780> it<00:04:42.930> into<00:04:43.590> a<00:04:43.890> escrow<00:04:44.460> pool 00:04:44.720 --> 00:04:44.730 align:start position:0% take that SEC put it into a escrow pool 00:04:44.730 --> 00:04:46.850 align:start position:0% take that SEC put it into a escrow pool but<00:04:45.000> that's<00:04:45.270> basically<00:04:45.930> the<00:04:46.170> private<00:04:46.620> point 00:04:46.850 --> 00:04:46.860 align:start position:0% but that's basically the private point 00:04:46.860 --> 00:04:51.710 align:start position:0% but that's basically the private point and<00:04:47.760> then<00:04:48.060> adds<00:04:48.620> this<00:04:49.620> commitment<00:04:50.490> to<00:04:50.940> what's 00:04:51.710 --> 00:04:51.720 align:start position:0% and then adds this commitment to what's 00:04:51.720 --> 00:04:53.390 align:start position:0% and then adds this commitment to what's known 00:04:53.390 --> 00:04:53.400 align:start position:0% known 00:04:53.400 --> 00:04:55.680 align:start position:0% known and<00:04:54.400> once<00:04:54.580> that<00:04:54.699> came<00:04:55.030> in<00:04:55.180> is<00:04:55.330> a<00:04:55.360> member 00:04:55.680 --> 00:04:55.690 align:start position:0% and once that came in is a member 00:04:55.690 --> 00:04:58.350 align:start position:0% and once that came in is a member country<00:04:55.870> then<00:04:56.680> it<00:04:56.800> exists<00:04:57.400> and<00:04:57.669> that<00:04:57.909> ones 00:04:58.350 --> 00:04:58.360 align:start position:0% country then it exists and that ones 00:04:58.360 --> 00:05:02.040 align:start position:0% country then it exists and that ones that<00:04:58.659> exists<00:04:59.379> in<00:04:59.680> this<00:05:00.060> private<00:05:01.060> world<00:05:01.840> of 00:05:02.040 --> 00:05:02.050 align:start position:0% that exists in this private world of 00:05:02.050 --> 00:05:09.839 align:start position:0% that exists in this private world of succession<00:05:04.889> so<00:05:05.889> here<00:05:06.099> we<00:05:06.190> go<00:05:06.310> we<00:05:06.580> have<00:05:06.610> that<00:05:08.849> so 00:05:09.839 --> 00:05:09.849 align:start position:0% succession so here we go we have that so 00:05:09.849 --> 00:05:12.119 align:start position:0% succession so here we go we have that so mixed<00:05:10.120> up<00:05:10.210> how<00:05:10.599> do<00:05:10.659> you<00:05:10.780> then<00:05:11.050> spending<00:05:11.800> for 00:05:12.119 --> 00:05:12.129 align:start position:0% mixed up how do you then spending for 00:05:12.129 --> 00:05:15.240 align:start position:0% mixed up how do you then spending for this<00:05:12.250> private<00:05:12.849> point<00:05:13.409> I<00:05:14.409> think<00:05:14.830> one<00:05:15.009> of<00:05:15.039> the 00:05:15.240 --> 00:05:15.250 align:start position:0% this private point I think one of the 00:05:15.250 --> 00:05:16.980 align:start position:0% this private point I think one of the easier<00:05:15.819> things<00:05:15.849> to<00:05:16.180> understand<00:05:16.599> is<00:05:16.720> how<00:05:16.930> do 00:05:16.980 --> 00:05:16.990 align:start position:0% easier things to understand is how do 00:05:16.990 --> 00:05:19.170 align:start position:0% easier things to understand is how do you<00:05:17.050> turn<00:05:17.289> it<00:05:17.349> back<00:05:17.590> into<00:05:17.800> a<00:05:17.889> public<00:05:18.310> point<00:05:18.580> so 00:05:19.170 --> 00:05:19.180 align:start position:0% you turn it back into a public point so 00:05:19.180 --> 00:05:24.800 align:start position:0% you turn it back into a public point so that's<00:05:19.360> called<00:05:19.539> shooting<00:05:20.440> and<00:05:21.069> I<00:05:21.159> should<00:05:21.340> have 00:05:24.800 --> 00:05:24.810 align:start position:0% 00:05:24.810 --> 00:05:28.290 align:start position:0% actually<00:05:25.810> existed<00:05:26.229> zero<00:05:27.159> cash<00:05:27.400> paper<00:05:27.819> it's 00:05:28.290 --> 00:05:28.300 align:start position:0% actually existed zero cash paper it's 00:05:28.300 --> 00:05:38.450 align:start position:0% actually existed zero cash paper it's actually<00:05:28.599> a<00:05:28.629> little<00:05:28.840> more<00:05:28.960> than<00:05:29.710> this<00:05:36.569> but<00:05:37.569> as 00:05:38.450 --> 00:05:38.460 align:start position:0% actually a little more than this but as 00:05:38.460 --> 00:05:42.779 align:start position:0% actually a little more than this but as we're<00:05:39.569> turning<00:05:40.569> this<00:05:40.840> back<00:05:40.900> into<00:05:41.440> a<00:05:41.889> public 00:05:42.779 --> 00:05:42.789 align:start position:0% we're turning this back into a public 00:05:42.789 --> 00:05:46.820 align:start position:0% we're turning this back into a public asset<00:05:43.139> tea<00:05:44.139> either<00:05:44.259> side<00:05:45.180> you 00:05:46.820 --> 00:05:46.830 align:start position:0% asset tea either side you 00:05:46.830 --> 00:05:49.990 align:start position:0% asset tea either side you to<00:05:47.009> reveal<00:05:47.430> the<00:05:47.720> serial<00:05:48.720> number<00:05:49.020> to<00:05:49.770> your 00:05:49.990 --> 00:05:50.000 align:start position:0% to reveal the serial number to your 00:05:50.000 --> 00:05:52.369 align:start position:0% to reveal the serial number to your commitment<00:05:51.000> so<00:05:51.569> let's<00:05:51.720> assume<00:05:52.020> we're<00:05:52.229> using 00:05:52.369 --> 00:05:52.379 align:start position:0% commitment so let's assume we're using 00:05:52.379 --> 00:05:55.580 align:start position:0% commitment so let's assume we're using this<00:05:52.620> amendment<00:05:53.129> over<00:05:53.340> here<00:05:54.050> and<00:05:55.050> then<00:05:55.319> in 00:05:55.580 --> 00:05:55.590 align:start position:0% this amendment over here and then in 00:05:55.590 --> 00:05:57.980 align:start position:0% this amendment over here and then in your<00:05:55.979> knowledge<00:05:56.280> you<00:05:56.849> have<00:05:57.060> to<00:05:57.090> prove<00:05:57.599> that 00:05:57.980 --> 00:05:57.990 align:start position:0% your knowledge you have to prove that 00:05:57.990 --> 00:06:00.950 align:start position:0% your knowledge you have to prove that you<00:05:58.680> know<00:05:58.949> of<00:05:59.310> surroundings<00:05:59.909> you<00:06:00.150> know<00:06:00.360> of<00:06:00.629> our 00:06:00.950 --> 00:06:00.960 align:start position:0% you know of surroundings you know of our 00:06:00.960 --> 00:06:06.140 align:start position:0% you know of surroundings you know of our such<00:06:01.860> that<00:06:02.069> this<00:06:02.220> commitment<00:06:03.110> cm<00:06:04.639> appears<00:06:05.639> in 00:06:06.140 --> 00:06:06.150 align:start position:0% such that this commitment cm appears in 00:06:06.150 --> 00:06:10.159 align:start position:0% such that this commitment cm appears in this<00:06:07.789> and<00:06:08.789> the<00:06:09.000> way<00:06:09.120> you<00:06:09.180> do<00:06:09.360> that<00:06:09.539> is<00:06:09.930> you 00:06:10.159 --> 00:06:10.169 align:start position:0% this and the way you do that is you 00:06:10.169 --> 00:06:12.890 align:start position:0% this and the way you do that is you construct<00:06:10.650> a<00:06:10.970> vertical<00:06:11.970> path<00:06:12.150> that<00:06:12.569> goes<00:06:12.690> up 00:06:12.890 --> 00:06:12.900 align:start position:0% construct a vertical path that goes up 00:06:12.900 --> 00:06:15.950 align:start position:0% construct a vertical path that goes up to<00:06:13.050> the<00:06:13.139> roof<00:06:13.319> and<00:06:14.090> inside<00:06:15.090> it's<00:06:15.300> not<00:06:15.360> circuit 00:06:15.950 --> 00:06:15.960 align:start position:0% to the roof and inside it's not circuit 00:06:15.960 --> 00:06:22.070 align:start position:0% to the roof and inside it's not circuit if<00:06:16.050> I<00:06:16.379> could<00:06:16.530> prove<00:06:17.150> that<00:06:18.150> this<00:06:19.669> exists<00:06:21.080> and 00:06:22.070 --> 00:06:22.080 align:start position:0% if I could prove that this exists and 00:06:22.080 --> 00:06:25.070 align:start position:0% if I could prove that this exists and then<00:06:22.979> other<00:06:23.159> full<00:06:23.490> nodes<00:06:23.789> or<00:06:23.909> miners<00:06:24.270> would 00:06:25.070 --> 00:06:25.080 align:start position:0% then other full nodes or miners would 00:06:25.080 --> 00:06:29.689 align:start position:0% then other full nodes or miners would then<00:06:25.349> think<00:06:26.310> this<00:06:26.490> proof<00:06:28.280> verified<00:06:29.280> and<00:06:29.639> they 00:06:29.689 --> 00:06:29.699 align:start position:0% then think this proof verified and they 00:06:29.699 --> 00:06:33.080 align:start position:0% then think this proof verified and they verified<00:06:30.180> by<00:06:30.530> giving<00:06:31.530> them<00:06:31.680> to<00:06:31.919> prove<00:06:32.460> the 00:06:33.080 --> 00:06:33.090 align:start position:0% verified by giving them to prove the 00:06:33.090 --> 00:06:36.309 align:start position:0% verified by giving them to prove the same<00:06:33.419> are<00:06:34.020> both<00:06:34.259> leaders<00:06:35.069> themselves 00:06:36.309 --> 00:06:36.319 align:start position:0% same are both leaders themselves 00:06:36.319 --> 00:06:41.059 align:start position:0% same are both leaders themselves and<00:06:37.319> if<00:06:37.530> the<00:06:37.800> proof<00:06:38.129> verifies<00:06:39.120> then<00:06:39.780> they<00:06:40.069> add 00:06:41.059 --> 00:06:41.069 align:start position:0% and if the proof verifies then they add 00:06:41.069 --> 00:06:44.570 align:start position:0% and if the proof verifies then they add the<00:06:41.849> serial<00:06:42.300> number<00:06:43.039> that<00:06:44.039> you<00:06:44.129> just<00:06:44.310> revealed 00:06:44.570 --> 00:06:44.580 align:start position:0% the serial number that you just revealed 00:06:44.580 --> 00:06:48.050 align:start position:0% the serial number that you just revealed earlier<00:06:45.000> to<00:06:45.629> what's<00:06:45.930> another<00:06:46.349> fire<00:06:46.590> step<00:06:47.060> so 00:06:48.050 --> 00:06:48.060 align:start position:0% earlier to what's another fire step so 00:06:48.060 --> 00:06:49.760 align:start position:0% earlier to what's another fire step so that<00:06:48.090> you<00:06:48.210> can't<00:06:48.479> spend<00:06:48.990> that<00:06:49.110> commitment 00:06:49.760 --> 00:06:49.770 align:start position:0% that you can't spend that commitment 00:06:49.770 --> 00:06:56.330 align:start position:0% that you can't spend that commitment again<00:06:50.509> and<00:06:51.509> then<00:06:51.810> gives<00:06:52.680> you<00:06:52.919> the<00:06:53.310> ones<00:06:54.319> escrow 00:06:56.330 --> 00:06:56.340 align:start position:0% again and then gives you the ones escrow 00:06:56.340 --> 00:07:00.800 align:start position:0% again and then gives you the ones escrow it's<00:06:56.700> be<00:06:56.940> back<00:06:57.150> of<00:06:57.750> the<00:06:58.050> private<00:06:58.470> point<00:06:59.690> and<00:07:00.690> so 00:07:00.800 --> 00:07:00.810 align:start position:0% it's be back of the private point and so 00:07:00.810 --> 00:07:02.450 align:start position:0% it's be back of the private point and so if<00:07:00.870> you<00:07:00.990> wanted<00:07:01.230> to<00:07:01.290> them<00:07:01.590> exactly 00:07:02.450 --> 00:07:02.460 align:start position:0% if you wanted to them exactly 00:07:02.460 --> 00:07:05.660 align:start position:0% if you wanted to them exactly privately<00:07:03.470> you're<00:07:04.470> in<00:07:04.740> effect<00:07:05.010> doing<00:07:05.550> the 00:07:05.660 --> 00:07:05.670 align:start position:0% privately you're in effect doing the 00:07:05.670 --> 00:07:07.340 align:start position:0% privately you're in effect doing the deshielding<00:07:06.240> operation<00:07:06.750> in<00:07:06.900> the<00:07:06.990> shielding 00:07:07.340 --> 00:07:07.350 align:start position:0% deshielding operation in the shielding 00:07:07.350 --> 00:07:10.780 align:start position:0% deshielding operation in the shielding operation<00:07:07.910> back-to-back<00:07:09.050> so<00:07:10.050> you<00:07:10.170> first 00:07:10.780 --> 00:07:10.790 align:start position:0% operation back-to-back so you first 00:07:10.790 --> 00:07:14.060 align:start position:0% operation back-to-back so you first improve<00:07:11.790> that<00:07:12.150> you<00:07:12.330> have<00:07:12.950> one<00:07:13.950> of<00:07:13.980> these 00:07:14.060 --> 00:07:14.070 align:start position:0% improve that you have one of these 00:07:14.070 --> 00:07:15.890 align:start position:0% improve that you have one of these commitments<00:07:14.430> and<00:07:14.850> you<00:07:15.390> create<00:07:15.720> a<00:07:15.780> new 00:07:15.890 --> 00:07:15.900 align:start position:0% commitments and you create a new 00:07:15.900 --> 00:07:21.980 align:start position:0% commitments and you create a new commitment<00:07:16.820> usually<00:07:20.450> it's<00:07:21.450> not<00:07:21.510> more<00:07:21.780> or<00:07:21.870> less 00:07:21.980 --> 00:07:21.990 align:start position:0% commitment usually it's not more or less 00:07:21.990 --> 00:07:32.390 align:start position:0% commitment usually it's not more or less made<00:07:22.230> sense<00:07:22.470> so<00:07:27.980> why<00:07:28.980> is<00:07:29.040> this<00:07:31.160> you<00:07:32.160> know<00:07:32.250> the 00:07:32.390 --> 00:07:32.400 align:start position:0% made sense so why is this you know the 00:07:32.400 --> 00:07:34.550 align:start position:0% made sense so why is this you know the answer<00:07:32.700> is<00:07:32.850> it's<00:07:33.390> not<00:07:33.540> difficult<00:07:33.810> but<00:07:34.380> it<00:07:34.500> is 00:07:34.550 --> 00:07:34.560 align:start position:0% answer is it's not difficult but it is 00:07:34.560 --> 00:07:38.210 align:start position:0% answer is it's not difficult but it is expensive<00:07:35.600> so<00:07:36.600> if<00:07:36.750> you<00:07:36.930> were<00:07:37.200> to<00:07:37.470> use<00:07:37.740> a<00:07:37.770> tree 00:07:38.210 --> 00:07:38.220 align:start position:0% expensive so if you were to use a tree 00:07:38.220 --> 00:07:42.680 align:start position:0% expensive so if you were to use a tree that's<00:07:38.460> around<00:07:38.820> 32<00:07:39.480> above<00:07:40.410> the<00:07:40.530> time<00:07:41.690> then 00:07:42.680 --> 00:07:42.690 align:start position:0% that's around 32 above the time then 00:07:42.690 --> 00:07:46.100 align:start position:0% that's around 32 above the time then this<00:07:43.320> is<00:07:43.500> quasi<00:07:43.920> -<00:07:44.100> news<00:07:44.460> today<00:07:44.760> he<00:07:45.110> recommends 00:07:46.100 --> 00:07:46.110 align:start position:0% this is quasi - news today he recommends 00:07:46.110 --> 00:07:48.950 align:start position:0% this is quasi - news today he recommends a<00:07:46.530> bigger<00:07:46.860> tree<00:07:47.310> but<00:07:48.000> see<00:07:48.150> -<00:07:48.330> was<00:07:48.510> being<00:07:48.750> a 00:07:48.950 --> 00:07:48.960 align:start position:0% a bigger tree but see - was being a 00:07:48.960 --> 00:07:51.140 align:start position:0% a bigger tree but see - was being a steadily<00:07:49.230> increasing<00:07:49.530> their<00:07:50.070> decides<00:07:50.490> with 00:07:51.140 --> 00:07:51.150 align:start position:0% steadily increasing their decides with 00:07:51.150 --> 00:07:53.750 align:start position:0% steadily increasing their decides with every<00:07:51.330> upgrade<00:07:52.100> but<00:07:53.100> if<00:07:53.220> you<00:07:53.310> were<00:07:53.400> to<00:07:53.550> have<00:07:53.700> a 00:07:53.750 --> 00:07:53.760 align:start position:0% every upgrade but if you were to have a 00:07:53.760 --> 00:07:56.150 align:start position:0% every upgrade but if you were to have a tree<00:07:54.270> of<00:07:54.300> this<00:07:54.510> height<00:07:54.950> then<00:07:55.950> you<00:07:56.040> would 00:07:56.150 --> 00:07:56.160 align:start position:0% tree of this height then you would 00:07:56.160 --> 00:07:59.330 align:start position:0% tree of this height then you would require<00:07:56.490> around<00:07:56.850> 1.7<00:07:57.780> million<00:07:58.020> gasps<00:07:58.320> just<00:07:59.130> to 00:07:59.330 --> 00:07:59.340 align:start position:0% require around 1.7 million gasps just to 00:07:59.340 --> 00:08:02.990 align:start position:0% require around 1.7 million gasps just to make<00:07:59.550> an<00:07:59.910> insert<00:08:00.419> operation<00:08:01.430> into<00:08:02.430> this<00:08:02.700> train 00:08:02.990 --> 00:08:03.000 align:start position:0% make an insert operation into this train 00:08:03.000 --> 00:08:05.540 align:start position:0% make an insert operation into this train so<00:08:03.240> not<00:08:03.390> even<00:08:03.510> can't<00:08:03.810> even<00:08:03.960> kind<00:08:04.890> of<00:08:04.950> gas<00:08:05.130> you 00:08:05.540 --> 00:08:05.550 align:start position:0% so not even can't even kind of gas you 00:08:05.550 --> 00:08:09.050 align:start position:0% so not even can't even kind of gas you need<00:08:05.669> to<00:08:05.790> verify<00:08:06.210> the<00:08:06.270> actual<00:08:06.960> proof<00:08:07.850> and<00:08:08.850> this 00:08:09.050 --> 00:08:09.060 align:start position:0% need to verify the actual proof and this 00:08:09.060 --> 00:08:11.600 align:start position:0% need to verify the actual proof and this is<00:08:09.210> assuming<00:08:09.690> you're<00:08:10.560> using<00:08:10.590> the<00:08:10.950> MC<00:08:11.310> hash 00:08:11.600 --> 00:08:11.610 align:start position:0% is assuming you're using the MC hash 00:08:11.610 --> 00:08:14.780 align:start position:0% is assuming you're using the MC hash function<00:08:12.060> in<00:08:12.150> which<00:08:12.680> we<00:08:13.680> had<00:08:14.040> to<00:08:14.190> use<00:08:14.370> in<00:08:14.640> order 00:08:14.780 --> 00:08:14.790 align:start position:0% function in which we had to use in order 00:08:14.790 --> 00:08:17.909 align:start position:0% function in which we had to use in order to<00:08:15.000> have<00:08:16.010> official<00:08:17.010> proving<00:08:17.310> times 00:08:17.909 --> 00:08:17.919 align:start position:0% to have official proving times 00:08:17.919 --> 00:08:20.700 align:start position:0% to have official proving times devices<00:08:18.580> so<00:08:18.969> if<00:08:19.030> you<00:08:19.240> shot<00:08:19.629> six<00:08:20.259> this<00:08:20.469> would<00:08:20.620> be 00:08:20.700 --> 00:08:20.710 align:start position:0% devices so if you shot six this would be 00:08:20.710 --> 00:08:23.939 align:start position:0% devices so if you shot six this would be cheaper<00:08:21.069> but<00:08:21.789> it<00:08:22.060> would<00:08:22.210> just<00:08:22.240> be<00:08:22.539> very<00:08:23.080> very 00:08:23.939 --> 00:08:23.949 align:start position:0% cheaper but it would just be very very 00:08:23.949 --> 00:08:25.559 align:start position:0% cheaper but it would just be very very expensive<00:08:24.219> actually<00:08:24.879> construct<00:08:25.270> the<00:08:25.360> proofs 00:08:25.559 --> 00:08:25.569 align:start position:0% expensive actually construct the proofs 00:08:25.569 --> 00:08:27.619 align:start position:0% expensive actually construct the proofs of<00:08:25.719> constructor<00:08:26.199> as<00:08:26.620> actions<00:08:27.039> on<00:08:27.279> your<00:08:27.310> phone 00:08:27.619 --> 00:08:27.629 align:start position:0% of constructor as actions on your phone 00:08:27.629 --> 00:08:31.699 align:start position:0% of constructor as actions on your phone so<00:08:28.629> we've<00:08:28.779> put<00:08:28.960> them<00:08:29.139> in<00:08:29.319> C<00:08:29.560> in<00:08:30.340> our<00:08:30.759> contract 00:08:31.699 --> 00:08:31.709 align:start position:0% so we've put them in C in our contract 00:08:31.709 --> 00:08:36.139 align:start position:0% so we've put them in C in our contract and<00:08:32.709> if<00:08:33.610> you<00:08:33.849> include<00:08:34.029> that<00:08:34.419> and<00:08:34.890> it<00:08:35.890> takes 00:08:36.139 --> 00:08:36.149 align:start position:0% and if you include that and it takes 00:08:36.149 --> 00:08:41.069 align:start position:0% and if you include that and it takes everything<00:08:37.149> gets<00:08:37.930> it<00:08:38.640> and<00:08:39.640> this<00:08:40.240> is<00:08:40.360> even<00:08:40.750> with 00:08:41.069 --> 00:08:41.079 align:start position:0% everything gets it and this is even with 00:08:41.079 --> 00:08:43.589 align:start position:0% everything gets it and this is even with optimizations<00:08:41.800> to<00:08:41.919> the<00:08:42.310> J<00:08:42.459> structure<00:08:42.909> it's<00:08:43.360> a 00:08:43.589 --> 00:08:43.599 align:start position:0% optimizations to the J structure it's a 00:08:43.599 --> 00:08:44.819 align:start position:0% optimizations to the J structure it's a bit<00:08:43.719> of<00:08:43.810> time<00:08:43.990> did<00:08:44.200> I<00:08:44.260> make<00:08:44.470> this<00:08:44.589> quite 00:08:44.819 --> 00:08:44.829 align:start position:0% bit of time did I make this quite 00:08:44.829 --> 00:08:48.780 align:start position:0% bit of time did I make this quite efficient<00:08:46.680> so<00:08:47.680> again<00:08:47.920> why<00:08:48.100> is<00:08:48.160> it<00:08:48.279> expensive 00:08:48.780 --> 00:08:48.790 align:start position:0% efficient so again why is it expensive 00:08:48.790 --> 00:08:50.310 align:start position:0% efficient so again why is it expensive well<00:08:49.060> if<00:08:49.209> you<00:08:49.329> insert<00:08:49.690> one<00:08:49.720> of<00:08:50.019> these<00:08:50.140> leaf 00:08:50.310 --> 00:08:50.320 align:start position:0% well if you insert one of these leaf 00:08:50.320 --> 00:08:53.579 align:start position:0% well if you insert one of these leaf nodes<00:08:50.649> you<00:08:51.430> have<00:08:51.640> to<00:08:52.019> compute<00:08:53.019> the<00:08:53.140> hashes 00:08:53.579 --> 00:08:53.589 align:start position:0% nodes you have to compute the hashes 00:08:53.589 --> 00:08:57.569 align:start position:0% nodes you have to compute the hashes going<00:08:54.459> all<00:08:54.699> the<00:08:54.880> way<00:08:54.910> up<00:08:55.300> to<00:08:55.810> the<00:08:55.930> root<00:08:56.339> and<00:08:57.339> so 00:08:57.569 --> 00:08:57.579 align:start position:0% going all the way up to the root and so 00:08:57.579 --> 00:09:02.400 align:start position:0% going all the way up to the root and so that<00:08:57.730> you<00:08:57.820> can<00:08:57.970> update<00:08:58.149> the<00:09:00.839> and<00:09:01.839> that 00:09:02.400 --> 00:09:02.410 align:start position:0% that you can update the and that 00:09:02.410 --> 00:09:05.430 align:start position:0% that you can update the and that requires<00:09:02.800> each<00:09:03.459> ashes<00:09:04.300> and<00:09:04.660> depending<00:09:05.290> how 00:09:05.430 --> 00:09:05.440 align:start position:0% requires each ashes and depending how 00:09:05.440 --> 00:09:07.439 align:start position:0% requires each ashes and depending how you're<00:09:05.680> storing<00:09:05.980> the<00:09:06.100> tree<00:09:06.399> and<00:09:06.640> optimizing 00:09:07.439 --> 00:09:07.449 align:start position:0% you're storing the tree and optimizing 00:09:07.449 --> 00:09:10.620 align:start position:0% you're storing the tree and optimizing it's<00:09:07.630> potentially<00:09:08.199> up<00:09:08.440> to<00:09:08.800> each<00:09:09.630> storage 00:09:10.620 --> 00:09:10.630 align:start position:0% it's potentially up to each storage 00:09:10.630 --> 00:09:15.150 align:start position:0% it's potentially up to each storage updates<00:09:11.140> which<00:09:11.920> is<00:09:12.640> expensive<00:09:13.600> and<00:09:14.589> then<00:09:14.890> of 00:09:15.150 --> 00:09:15.160 align:start position:0% updates which is expensive and then of 00:09:15.160 --> 00:09:16.590 align:start position:0% updates which is expensive and then of course<00:09:15.250> as<00:09:15.640> you<00:09:15.670> make<00:09:16.029> them<00:09:16.209> to<00:09:16.300> be<00:09:16.390> bigger 00:09:16.590 --> 00:09:16.600 align:start position:0% course as you make them to be bigger 00:09:16.600 --> 00:09:18.360 align:start position:0% course as you make them to be bigger this<00:09:16.959> nation<00:09:17.260> support<00:09:17.620> more<00:09:17.890> total 00:09:18.360 --> 00:09:18.370 align:start position:0% this nation support more total 00:09:18.370 --> 00:09:23.370 align:start position:0% this nation support more total transactions<00:09:19.029> and<00:09:20.019> more<00:09:20.110> expensive<00:09:22.019> so<00:09:23.019> how 00:09:23.370 --> 00:09:23.380 align:start position:0% transactions and more expensive so how 00:09:23.380 --> 00:09:26.750 align:start position:0% transactions and more expensive so how do<00:09:23.440> we<00:09:23.500> improve<00:09:24.160> on<00:09:24.399> this<00:09:25.019> we<00:09:26.019> came<00:09:26.170> up<00:09:26.320> with 00:09:26.750 --> 00:09:26.760 align:start position:0% do we improve on this we came up with 00:09:26.760 --> 00:09:33.020 align:start position:0% do we improve on this we came up with drugs<00:09:27.760> and<00:09:28.120> the<00:09:29.019> basic<00:09:29.320> idea<00:09:29.769> is 00:09:33.020 --> 00:09:33.030 align:start position:0% 00:09:33.030 --> 00:09:36.290 align:start position:0% which<00:09:33.780> we<00:09:33.900> call<00:09:34.170> a<00:09:34.200> miracle<00:09:34.520> shrub<00:09:35.520> tree<00:09:35.820> and 00:09:36.290 --> 00:09:36.300 align:start position:0% which we call a miracle shrub tree and 00:09:36.300 --> 00:09:39.200 align:start position:0% which we call a miracle shrub tree and in<00:09:37.080> this<00:09:37.250> destruction<00:09:38.250> of<00:09:38.310> the<00:09:38.460> tree<00:09:38.760> is<00:09:39.000> not 00:09:39.200 --> 00:09:39.210 align:start position:0% in this destruction of the tree is not 00:09:39.210 --> 00:09:41.870 align:start position:0% in this destruction of the tree is not defined<00:09:39.690> by<00:09:40.050> the<00:09:40.110> room<00:09:40.530> but<00:09:41.250> it's<00:09:41.400> instead 00:09:41.870 --> 00:09:41.880 align:start position:0% defined by the room but it's instead 00:09:41.880 --> 00:09:45.080 align:start position:0% defined by the room but it's instead defined<00:09:42.360> by<00:09:42.900> the<00:09:43.770> path<00:09:44.100> to<00:09:44.460> the<00:09:44.580> right<00:09:44.790> most 00:09:45.080 --> 00:09:45.090 align:start position:0% defined by the path to the right most 00:09:45.090 --> 00:09:48.170 align:start position:0% defined by the path to the right most non<00:09:45.630> empty<00:09:45.830> so<00:09:46.830> that<00:09:46.860> means<00:09:47.160> to<00:09:47.550> me<00:09:47.760> basically 00:09:48.170 --> 00:09:48.180 align:start position:0% non empty so that means to me basically 00:09:48.180 --> 00:09:51.200 align:start position:0% non empty so that means to me basically the<00:09:48.540> frontier<00:09:49.230> of<00:09:49.500> this<00:09:50.280> tree<00:09:50.820> that<00:09:50.850> were 00:09:51.200 --> 00:09:51.210 align:start position:0% the frontier of this tree that were 00:09:51.210 --> 00:09:53.030 align:start position:0% the frontier of this tree that were filling<00:09:51.480> from<00:09:51.900> the<00:09:51.990> left<00:09:52.320> and<00:09:52.590> going<00:09:52.740> to<00:09:52.950> the 00:09:53.030 --> 00:09:53.040 align:start position:0% filling from the left and going to the 00:09:53.040 --> 00:09:57.230 align:start position:0% filling from the left and going to the right<00:09:53.220> and<00:09:54.650> as<00:09:55.650> an<00:09:56.160> optimization<00:09:56.520> instead<00:09:57.150> of 00:09:57.230 --> 00:09:57.240 align:start position:0% right and as an optimization instead of 00:09:57.240 --> 00:10:02.300 align:start position:0% right and as an optimization instead of storing<00:09:57.690> that<00:09:58.680> entire<00:09:59.160> path<00:10:00.260> since<00:10:01.280> some<00:10:02.280> of 00:10:02.300 --> 00:10:02.310 align:start position:0% storing that entire path since some of 00:10:02.310 --> 00:10:03.830 align:start position:0% storing that entire path since some of the<00:10:02.430> notes<00:10:02.640> on<00:10:02.850> that<00:10:03.000> path<00:10:03.180> may<00:10:03.420> not<00:10:03.600> have 00:10:03.830 --> 00:10:03.840 align:start position:0% the notes on that path may not have 00:10:03.840 --> 00:10:06.770 align:start position:0% the notes on that path may not have children<00:10:04.620> on<00:10:04.980> their<00:10:05.130> right<00:10:05.370> side<00:10:05.630> we<00:10:06.630> can 00:10:06.770 --> 00:10:06.780 align:start position:0% children on their right side we can 00:10:06.780 --> 00:10:08.660 align:start position:0% children on their right side we can actually<00:10:06.930> store<00:10:07.260> fewer<00:10:07.590> notes<00:10:07.920> and<00:10:08.310> all<00:10:08.460> page 00:10:08.660 --> 00:10:08.670 align:start position:0% actually store fewer notes and all page 00:10:08.670 --> 00:10:10.850 align:start position:0% actually store fewer notes and all page notes<00:10:08.970> and<00:10:09.720> so<00:10:09.930> we<00:10:10.080> only<00:10:10.230> store<00:10:10.500> in<00:10:10.680> those 00:10:10.850 --> 00:10:10.860 align:start position:0% notes and so we only store in those 00:10:10.860 --> 00:10:17.450 align:start position:0% notes and so we only store in those units<00:10:11.280> that<00:10:11.430> actually<00:10:11.660> calculate<00:10:12.660> that's<00:10:16.460> not 00:10:17.450 --> 00:10:17.460 align:start position:0% units that actually calculate that's not 00:10:17.460 --> 00:10:21.320 align:start position:0% units that actually calculate that's not responding<00:10:18.110> and<00:10:19.110> we<00:10:19.530> call<00:10:19.940> these<00:10:20.940> notes 00:10:21.320 --> 00:10:21.330 align:start position:0% responding and we call these notes 00:10:21.330 --> 00:10:23.660 align:start position:0% responding and we call these notes required<00:10:21.840> to<00:10:22.080> reconstruct<00:10:22.680> this<00:10:22.920> this<00:10:23.370> path 00:10:23.660 --> 00:10:23.670 align:start position:0% required to reconstruct this this path 00:10:23.670 --> 00:10:26.990 align:start position:0% required to reconstruct this this path adds<00:10:24.830> shrubs<00:10:25.830> and<00:10:26.550> we<00:10:26.670> call<00:10:26.850> them<00:10:26.970> that 00:10:26.990 --> 00:10:27.000 align:start position:0% adds shrubs and we call them that 00:10:27.000 --> 00:10:29.330 align:start position:0% adds shrubs and we call them that because<00:10:27.270> if<00:10:27.630> you<00:10:27.780> include<00:10:28.110> the<00:10:28.230> path<00:10:28.440> that's<00:10:29.130> a 00:10:29.330 --> 00:10:29.340 align:start position:0% because if you include the path that's a 00:10:29.340 --> 00:10:33.340 align:start position:0% because if you include the path that's a bit<00:10:29.670> like<00:10:29.790> a<00:10:29.820> stroke<00:10:30.150> not<00:10:30.810> quite<00:10:31.050> a<00:10:31.080> tree<00:10:31.380> and 00:10:33.340 --> 00:10:33.350 align:start position:0% bit like a stroke not quite a tree and 00:10:33.350 --> 00:10:38.270 align:start position:0% bit like a stroke not quite a tree and so<00:10:34.350> what<00:10:35.280> does<00:10:35.370> a<00:10:35.430> proof<00:10:35.820> look<00:10:36.120> like<00:10:37.130> you<00:10:38.130> can 00:10:38.270 --> 00:10:38.280 align:start position:0% so what does a proof look like you can 00:10:38.280 --> 00:10:41.570 align:start position:0% so what does a proof look like you can this<00:10:38.370> new<00:10:38.550> beta<00:10:38.760> structure<00:10:39.320> so<00:10:40.400> you<00:10:41.400> basically 00:10:41.570 --> 00:10:41.580 align:start position:0% this new beta structure so you basically 00:10:41.580 --> 00:10:43.490 align:start position:0% this new beta structure so you basically have<00:10:41.940> to<00:10:42.240> construct<00:10:42.630> the<00:10:42.900> vertical<00:10:43.260> proof 00:10:43.490 --> 00:10:43.500 align:start position:0% have to construct the vertical proof 00:10:43.500 --> 00:10:46.010 align:start position:0% have to construct the vertical proof that<00:10:43.920> doesn't<00:10:44.400> end<00:10:44.580> up<00:10:44.850> at<00:10:45.150> the<00:10:45.300> root<00:10:45.510> but 00:10:46.010 --> 00:10:46.020 align:start position:0% that doesn't end up at the root but 00:10:46.020 --> 00:10:49.700 align:start position:0% that doesn't end up at the root but instead<00:10:46.589> ends<00:10:47.130> up<00:10:47.310> at<00:10:48.120> this<00:10:48.390> frontier<00:10:48.960> town<00:10:49.200> so 00:10:49.700 --> 00:10:49.710 align:start position:0% instead ends up at this frontier town so 00:10:49.710 --> 00:10:50.940 align:start position:0% instead ends up at this frontier town so say<00:10:49.980> that<00:10:50.190> we<00:10:50.310> want<00:10:50.550> to 00:10:50.940 --> 00:10:50.950 align:start position:0% say that we want to 00:10:50.950 --> 00:10:55.889 align:start position:0% say that we want to but<00:10:51.760> this<00:10:52.000> note<00:10:52.329> is<00:10:52.660> part<00:10:52.990> of<00:10:53.279> the<00:10:54.779> part<00:10:55.779> of 00:10:55.889 --> 00:10:55.899 align:start position:0% but this note is part of the part of 00:10:55.899 --> 00:10:58.860 align:start position:0% but this note is part of the part of this<00:10:56.139> site<00:10:56.920> and<00:10:57.399> then<00:10:58.300> you<00:10:58.389> construct<00:10:58.570> the 00:10:58.860 --> 00:10:58.870 align:start position:0% this site and then you construct the 00:10:58.870 --> 00:11:00.389 align:start position:0% this site and then you construct the merkel<00:10:59.139> path<00:10:59.350> that<00:10:59.769> doesn't<00:11:00.130> go<00:11:00.220> with<00:11:00.250> a 00:11:00.389 --> 00:11:00.399 align:start position:0% merkel path that doesn't go with a 00:11:00.399 --> 00:11:02.040 align:start position:0% merkel path that doesn't go with a bitter<00:11:00.670> an<00:11:00.760> eclectic<00:11:00.970> ghost<00:11:01.389> to<00:11:01.630> this<00:11:01.750> note 00:11:02.040 --> 00:11:02.050 align:start position:0% bitter an eclectic ghost to this note 00:11:02.050 --> 00:11:05.579 align:start position:0% bitter an eclectic ghost to this note which<00:11:02.740> is<00:11:02.769> part<00:11:03.160> of<00:11:03.220> the<00:11:03.310> frontier<00:11:03.790> I<00:11:04.500> need<00:11:05.500> to 00:11:05.579 --> 00:11:05.589 align:start position:0% which is part of the frontier I need to 00:11:05.589 --> 00:11:10.069 align:start position:0% which is part of the frontier I need to do<00:11:05.709> that<00:11:05.860> you<00:11:06.070> need<00:11:06.250> this<00:11:06.670> no<00:11:06.940> just<00:11:07.449> note<00:11:07.690> that 00:11:10.069 --> 00:11:10.079 align:start position:0% 00:11:10.079 --> 00:11:13.800 align:start position:0% and<00:11:11.079> verify<00:11:11.560> that<00:11:11.589> it<00:11:11.860> matches<00:11:12.240> what's<00:11:13.240> there 00:11:13.800 --> 00:11:13.810 align:start position:0% and verify that it matches what's there 00:11:13.810 --> 00:11:17.129 align:start position:0% and verify that it matches what's there and<00:11:14.709> then<00:11:15.360> if<00:11:16.360> you<00:11:16.449> want<00:11:16.600> to<00:11:16.630> verify<00:11:16.870> this 00:11:17.129 --> 00:11:17.139 align:start position:0% and then if you want to verify this 00:11:17.139 --> 00:11:20.819 align:start position:0% and then if you want to verify this proof<00:11:17.560> you<00:11:18.010> need<00:11:18.190> to<00:11:18.430> know<00:11:18.779> the<00:11:19.779> frontier<00:11:20.470> one 00:11:20.819 --> 00:11:20.829 align:start position:0% proof you need to know the frontier one 00:11:20.829 --> 00:11:25.650 align:start position:0% proof you need to know the frontier one side<00:11:21.040> of<00:11:21.160> knowing<00:11:21.430> just<00:11:21.610> the<00:11:23.880> old<00:11:24.880> frontier<00:11:25.329> or 00:11:25.650 --> 00:11:25.660 align:start position:0% side of knowing just the old frontier or 00:11:25.660 --> 00:11:28.350 align:start position:0% side of knowing just the old frontier or again<00:11:26.350> s<00:11:26.529> optimization<00:11:27.220> the<00:11:27.820> strobus<00:11:28.120> that 00:11:28.350 --> 00:11:28.360 align:start position:0% again s optimization the strobus that 00:11:28.360 --> 00:11:31.110 align:start position:0% again s optimization the strobus that you<00:11:28.449> can<00:11:28.660> use<00:11:28.839> to<00:11:29.019> generate<00:11:29.199> definitely<00:11:30.120> so 00:11:31.110 --> 00:11:31.120 align:start position:0% you can use to generate definitely so 00:11:31.120 --> 00:11:32.910 align:start position:0% you can use to generate definitely so let's<00:11:31.269> look<00:11:31.389> at<00:11:31.540> another<00:11:31.630> example<00:11:31.839> say<00:11:32.769> that 00:11:32.910 --> 00:11:32.920 align:start position:0% let's look at another example say that 00:11:32.920 --> 00:11:38.220 align:start position:0% let's look at another example say that you<00:11:33.010> want<00:11:33.190> to<00:11:33.310> verify<00:11:33.610> this<00:11:34.120> guy<00:11:35.220> this<00:11:36.220> guy<00:11:37.230> go 00:11:38.220 --> 00:11:38.230 align:start position:0% you want to verify this guy this guy go 00:11:38.230 --> 00:11:39.569 align:start position:0% you want to verify this guy this guy go all<00:11:38.350> the<00:11:38.470> way<00:11:38.500> up<00:11:38.680> to<00:11:38.860> the<00:11:39.070> top 00:11:39.569 --> 00:11:39.579 align:start position:0% all the way up to the top 00:11:39.579 --> 00:11:42.850 align:start position:0% all the way up to the top well<00:11:40.420> intersect<00:11:41.199> the<00:11:41.350> frontier 00:11:42.850 --> 00:11:42.860 align:start position:0% well intersect the frontier 00:11:42.860 --> 00:11:44.769 align:start position:0% well intersect the frontier and<00:11:43.249> that's<00:11:43.459> fine<00:11:43.699> the<00:11:44.149> root<00:11:44.329> is<00:11:44.449> part<00:11:44.660> of<00:11:44.689> the 00:11:44.769 --> 00:11:44.779 align:start position:0% and that's fine the root is part of the 00:11:44.779 --> 00:11:48.669 align:start position:0% and that's fine the root is part of the frontier<00:11:45.139> as<00:11:45.290> well<00:11:46.089> works<00:11:47.089> just<00:11:47.239> before<00:11:48.050> you 00:11:48.669 --> 00:11:48.679 align:start position:0% frontier as well works just before you 00:11:48.679 --> 00:11:52.319 align:start position:0% frontier as well works just before you just<00:11:48.920> in<00:11:49.309> my<00:11:49.459> notes<00:11:49.670> as<00:11:50.300> part<00:11:50.629> of<00:11:50.689> your<00:11:50.839> move 00:11:52.319 --> 00:11:52.329 align:start position:0% just in my notes as part of your move 00:11:52.329 --> 00:11:55.150 align:start position:0% just in my notes as part of your move and<00:11:53.329> so<00:11:53.600> in<00:11:53.809> fact<00:11:53.929> what<00:11:54.350> we're<00:11:54.499> doing<00:11:54.829> is<00:11:54.980> we're 00:11:55.150 --> 00:11:55.160 align:start position:0% and so in fact what we're doing is we're 00:11:55.160 --> 00:11:57.189 align:start position:0% and so in fact what we're doing is we're trading<00:11:55.610> off<00:11:55.819> the<00:11:56.480> amount<00:11:56.749> of<00:11:56.839> work<00:11:56.989> that<00:11:57.019> you 00:11:57.189 --> 00:11:57.199 align:start position:0% trading off the amount of work that you 00:11:57.199 --> 00:12:00.340 align:start position:0% trading off the amount of work that you have<00:11:57.350> to<00:11:57.470> do<00:11:57.649> to<00:11:58.009> perform<00:11:58.369> these<00:11:58.489> inserts<00:11:59.350> with 00:12:00.340 --> 00:12:00.350 align:start position:0% have to do to perform these inserts with 00:12:00.350 --> 00:12:01.629 align:start position:0% have to do to perform these inserts with the<00:12:00.529> work<00:12:00.709> that<00:12:00.860> you<00:12:00.920> have<00:12:00.980> to<00:12:01.160> do<00:12:01.279> to<00:12:01.489> verify 00:12:01.629 --> 00:12:01.639 align:start position:0% the work that you have to do to verify 00:12:01.639 --> 00:12:04.419 align:start position:0% the work that you have to do to verify these<00:12:01.999> markers<00:12:02.649> to<00:12:03.649> verify<00:12:04.009> which<00:12:04.189> will<00:12:04.309> prove 00:12:04.419 --> 00:12:04.429 align:start position:0% these markers to verify which will prove 00:12:04.429 --> 00:12:07.109 align:start position:0% these markers to verify which will prove you<00:12:04.579> have<00:12:04.730> to<00:12:04.879> provide<00:12:05.239> more<00:12:05.569> public<00:12:06.470> inputs 00:12:07.109 --> 00:12:07.119 align:start position:0% you have to provide more public inputs 00:12:07.119 --> 00:12:09.340 align:start position:0% you have to provide more public inputs which<00:12:08.119> makes<00:12:08.360> the<00:12:08.509> verification<00:12:09.049> a<00:12:09.139> little 00:12:09.340 --> 00:12:09.350 align:start position:0% which makes the verification a little 00:12:09.350 --> 00:12:11.530 align:start position:0% which makes the verification a little bit<00:12:09.439> more<00:12:09.649> expensive<00:12:10.160> but<00:12:10.759> as<00:12:11.059> well<00:12:11.209> find<00:12:11.449> that 00:12:11.530 --> 00:12:11.540 align:start position:0% bit more expensive but as well find that 00:12:11.540 --> 00:12:13.650 align:start position:0% bit more expensive but as well find that the<00:12:11.779> trade<00:12:11.989> off<00:12:12.139> protection<00:12:12.559> well<00:12:12.769> worth<00:12:12.949> it 00:12:13.650 --> 00:12:13.660 align:start position:0% the trade off protection well worth it 00:12:13.660 --> 00:12:17.019 align:start position:0% the trade off protection well worth it so<00:12:14.769> it<00:12:15.769> all<00:12:15.860> comes<00:12:16.040> down<00:12:16.160> to<00:12:16.489> the<00:12:16.579> cost<00:12:16.819> of 00:12:17.019 --> 00:12:17.029 align:start position:0% so it all comes down to the cost of 00:12:17.029 --> 00:12:19.509 align:start position:0% so it all comes down to the cost of inserts<00:12:17.509> so<00:12:18.259> what<00:12:18.619> is<00:12:18.709> an<00:12:18.829> insert<00:12:19.100> that<00:12:19.369> look 00:12:19.509 --> 00:12:19.519 align:start position:0% inserts so what is an insert that look 00:12:19.519 --> 00:12:22.109 align:start position:0% inserts so what is an insert that look like<00:12:19.699> and<00:12:20.089> that<00:12:20.179> was<00:12:20.389> the<00:12:20.569> expensive<00:12:21.049> thing<00:12:21.290> in 00:12:22.109 --> 00:12:22.119 align:start position:0% like and that was the expensive thing in 00:12:22.119 --> 00:12:25.449 align:start position:0% like and that was the expensive thing in traditional<00:12:23.119> medical<00:12:23.389> treatment<00:12:24.279> say<00:12:25.279> that 00:12:25.449 --> 00:12:25.459 align:start position:0% traditional medical treatment say that 00:12:25.459 --> 00:12:28.929 align:start position:0% traditional medical treatment say that we<00:12:25.519> want<00:12:25.699> to<00:12:25.759> insert<00:12:26.029> this<00:12:26.470> over<00:12:27.470> here<00:12:27.769> so<00:12:28.189> we 00:12:28.929 --> 00:12:28.939 align:start position:0% we want to insert this over here so we 00:12:28.939 --> 00:12:32.019 align:start position:0% we want to insert this over here so we just<00:12:29.119> insert<00:12:29.480> it<00:12:29.660> into<00:12:29.989> the<00:12:30.829> next<00:12:31.100> love<00:12:31.369> I'm 00:12:32.019 --> 00:12:32.029 align:start position:0% just insert it into the next love I'm 00:12:32.029 --> 00:12:33.759 align:start position:0% just insert it into the next love I'm currently<00:12:32.600> building<00:12:32.899> the<00:12:33.110> street<00:12:33.529> from 00:12:33.759 --> 00:12:33.769 align:start position:0% currently building the street from 00:12:33.769 --> 00:12:36.699 align:start position:0% currently building the street from that's<00:12:33.980> right<00:12:34.509> and<00:12:35.509> then<00:12:35.809> we<00:12:36.049> have<00:12:36.199> to<00:12:36.350> compute 00:12:36.699 --> 00:12:36.709 align:start position:0% that's right and then we have to compute 00:12:36.709 --> 00:12:38.530 align:start position:0% that's right and then we have to compute all<00:12:37.009> the<00:12:37.100> hashes<00:12:37.639> and<00:12:37.670> update<00:12:38.089> all<00:12:38.119> of<00:12:38.420> the 00:12:38.530 --> 00:12:38.540 align:start position:0% all the hashes and update all of the 00:12:38.540 --> 00:12:40.689 align:start position:0% all the hashes and update all of the shrubs<00:12:38.869> that<00:12:39.170> are<00:12:39.589> needed<00:12:39.920> to<00:12:40.069> construct<00:12:40.309> this 00:12:40.689 --> 00:12:40.699 align:start position:0% shrubs that are needed to construct this 00:12:40.699 --> 00:12:46.030 align:start position:0% shrubs that are needed to construct this you<00:12:42.369> frontier<00:12:43.369> that<00:12:43.549> exists<00:12:44.059> and<00:12:44.839> so<00:12:45.410> look 00:12:46.030 --> 00:12:46.040 align:start position:0% you frontier that exists and so look 00:12:46.040 --> 00:12:48.129 align:start position:0% you frontier that exists and so look these<00:12:46.309> are<00:12:46.549> the<00:12:46.670> shrubs<00:12:47.240> needed<00:12:47.720> to<00:12:47.899> construct 00:12:48.129 --> 00:12:48.139 align:start position:0% these are the shrubs needed to construct 00:12:48.139 --> 00:12:51.609 align:start position:0% these are the shrubs needed to construct a<00:12:48.439> frontier<00:12:48.829> before<00:12:49.339> we<00:12:49.490> edit<00:12:49.730> this<00:12:49.850> note<00:12:50.619> and 00:12:51.609 --> 00:12:51.619 align:start position:0% a frontier before we edit this note and 00:12:51.619 --> 00:12:54.809 align:start position:0% a frontier before we edit this note and these<00:12:52.279> are<00:12:52.459> the<00:12:52.549> ones<00:12:52.730> that<00:12:52.850> are<00:12:53.059> needed 00:12:54.809 --> 00:12:54.819 align:start position:0% these are the ones that are needed 00:12:54.819 --> 00:12:59.129 align:start position:0% these are the ones that are needed here<00:12:55.109> after<00:12:56.109> we<00:12:56.229> have<00:12:56.470> noted<00:12:56.889> and<00:12:57.879> since<00:12:58.809> the 00:12:59.129 --> 00:12:59.139 align:start position:0% here after we have noted and since the 00:12:59.139 --> 00:13:00.779 align:start position:0% here after we have noted and since the only<00:12:59.169> new<00:12:59.589> struggle<00:12:59.859> is<00:13:00.069> that<00:13:00.189> will<00:13:00.399> actually 00:13:00.779 --> 00:13:00.789 align:start position:0% only new struggle is that will actually 00:13:00.789 --> 00:13:04.590 align:start position:0% only new struggle is that will actually snowed<00:13:01.689> that<00:13:02.019> we<00:13:02.139> have<00:13:02.529> already<00:13:02.739> added<00:13:03.600> you 00:13:04.590 --> 00:13:04.600 align:start position:0% snowed that we have already added you 00:13:04.600 --> 00:13:07.109 align:start position:0% snowed that we have already added you actually<00:13:05.109> only<00:13:05.289> need<00:13:05.470> one<00:13:06.189> updating<00:13:06.819> zero 00:13:07.109 --> 00:13:07.119 align:start position:0% actually only need one updating zero 00:13:07.119 --> 00:13:10.499 align:start position:0% actually only need one updating zero ashes<00:13:07.739> performance<00:13:08.739> and<00:13:08.919> sir<00:13:09.119> that's<00:13:10.119> pretty 00:13:10.499 --> 00:13:10.509 align:start position:0% ashes performance and sir that's pretty 00:13:10.509 --> 00:13:13.949 align:start position:0% ashes performance and sir that's pretty efficient<00:13:11.019> and<00:13:11.259> that<00:13:11.470> translates<00:13:12.009> into<00:13:12.959> very 00:13:13.949 --> 00:13:13.959 align:start position:0% efficient and that translates into very 00:13:13.959 --> 00:13:16.710 align:start position:0% efficient and that translates into very good<00:13:14.169> SATs<00:13:14.769> now<00:13:15.519> we're<00:13:15.669> not<00:13:15.759> going<00:13:16.299> to<00:13:16.359> be<00:13:16.509> so 00:13:16.710 --> 00:13:16.720 align:start position:0% good SATs now we're not going to be so 00:13:16.720 --> 00:13:25.729 align:start position:0% good SATs now we're not going to be so lucky 00:13:25.729 --> 00:13:25.739 align:start position:0% 00:13:25.739 --> 00:14:05.639 align:start position:0% so<00:13:26.739> let's<00:13:26.889> imagine<00:14:03.749> we<00:14:04.749> have<00:14:04.839> to<00:14:04.989> update<00:14:05.199> this 00:14:05.639 --> 00:14:05.649 align:start position:0% so let's imagine we have to update this 00:14:05.649 --> 00:14:09.149 align:start position:0% so let's imagine we have to update this and<00:14:06.009> pick<00:14:06.609> this<00:14:06.759> we<00:14:07.089> need<00:14:07.329> compute<00:14:08.049> the<00:14:09.009> hash 00:14:09.149 --> 00:14:09.159 align:start position:0% and pick this we need compute the hash 00:14:09.159 --> 00:14:17.960 align:start position:0% and pick this we need compute the hash of<00:14:09.429> this<00:14:10.259> and<00:14:11.259> the<00:14:11.409> hash<00:14:11.559> of<00:14:11.739> this<00:14:14.669> passionates 00:14:17.960 --> 00:14:17.970 align:start position:0% 00:14:17.970 --> 00:14:21.539 align:start position:0% and<00:14:18.970> so<00:14:19.229> in<00:14:20.229> the<00:14:20.350> expected<00:14:20.859> case<00:14:21.039> you<00:14:21.249> end<00:14:21.399> up 00:14:21.539 --> 00:14:21.549 align:start position:0% and so in the expected case you end up 00:14:21.549 --> 00:14:24.869 align:start position:0% and so in the expected case you end up having<00:14:21.669> to<00:14:21.909> do<00:14:22.059> about<00:14:22.329> 1.5<00:14:22.899> updates<00:14:23.579> and<00:14:24.579> about 00:14:24.869 --> 00:14:24.879 align:start position:0% having to do about 1.5 updates and about 00:14:24.879 --> 00:14:29.309 align:start position:0% having to do about 1.5 updates and about 1<00:14:25.179> hash<00:14:26.399> on<00:14:27.399> average<00:14:27.970> so<00:14:28.720> obviously<00:14:29.109> their 00:14:29.309 --> 00:14:29.319 align:start position:0% 1 hash on average so obviously their 00:14:29.319 --> 00:14:54.139 align:start position:0% 1 hash on average so obviously their worst<00:14:29.439> case<00:14:50.129> comes<00:14:51.129> by<00:14:51.429> seller<00:14:51.729> -<00:14:51.999> or<00:14:52.239> /<00:14:53.069> drugs 00:14:54.139 --> 00:14:54.149 align:start position:0% worst case comes by seller - or / drugs 00:14:54.149 --> 00:15:02.849 align:start position:0% worst case comes by seller - or / drugs just<00:14:55.149> questions<00:14:55.720> it<00:14:55.959> see<00:14:56.949> the<00:14:59.100> figure<00:15:01.859> when 00:15:02.849 --> 00:15:02.859 align:start position:0% just questions it see the figure when 00:15:02.859 --> 00:15:04.949 align:start position:0% just questions it see the figure when you<00:15:02.889> think<00:15:03.189> that<00:15:03.309> the<00:15:03.429> verifying<00:15:03.970> like<00:15:04.149> you 00:15:04.949 --> 00:15:04.959 align:start position:0% you think that the verifying like you 00:15:04.959 --> 00:15:10.090 align:start position:0% you think that the verifying like you know<00:15:05.169> you<00:15:06.039> know 00:15:10.090 --> 00:15:10.100 align:start position:0% 00:15:10.100 --> 00:15:13.670 align:start position:0% whether<00:15:11.100> you're<00:15:11.400> in<00:15:11.670> the<00:15:11.700> right<00:15:12.600> subtree<00:15:13.230> here 00:15:13.670 --> 00:15:13.680 align:start position:0% whether you're in the right subtree here 00:15:13.680 --> 00:15:16.970 align:start position:0% whether you're in the right subtree here in<00:15:13.860> the<00:15:13.950> left<00:15:14.160> subtree<00:15:14.400> here<00:15:15.560> is<00:15:16.560> our<00:15:16.710> fighter 00:15:16.970 --> 00:15:16.980 align:start position:0% in the left subtree here is our fighter 00:15:16.980 --> 00:15:20.060 align:start position:0% in the left subtree here is our fighter fire<00:15:17.480> only<00:15:18.480> has<00:15:18.839> to<00:15:18.990> fight<00:15:19.260> as<00:15:19.410> a<00:15:19.440> publican<00:15:19.890> but 00:15:20.060 --> 00:15:20.070 align:start position:0% fire only has to fight as a publican but 00:15:20.070 --> 00:15:23.480 align:start position:0% fire only has to fight as a publican but to<00:15:20.600> proof<00:15:21.600> the<00:15:21.960> actual<00:15:22.529> shrubs<00:15:23.070> you<00:15:23.190> need<00:15:23.400> to 00:15:23.480 --> 00:15:23.490 align:start position:0% to proof the actual shrubs you need to 00:15:23.490 --> 00:15:26.450 align:start position:0% to proof the actual shrubs you need to construct<00:15:23.880> the<00:15:24.210> frontier<00:15:24.720> and<00:15:25.080> then<00:15:25.860> in<00:15:26.190> zero 00:15:26.450 --> 00:15:26.460 align:start position:0% construct the frontier and then in zero 00:15:26.460 --> 00:15:27.980 align:start position:0% construct the frontier and then in zero knowledge<00:15:26.730> you're<00:15:27.210> actually<00:15:27.540> gonna<00:15:27.690> prove 00:15:27.980 --> 00:15:27.990 align:start position:0% knowledge you're actually gonna prove 00:15:27.990 --> 00:15:31.160 align:start position:0% knowledge you're actually gonna prove that<00:15:28.320> your<00:15:28.740> node<00:15:29.100> is<00:15:29.279> connected<00:15:30.050> so<00:15:31.050> the 00:15:31.160 --> 00:15:31.170 align:start position:0% that your node is connected so the 00:15:31.170 --> 00:15:34.630 align:start position:0% that your node is connected so the verifier<00:15:31.560> doesn't<00:15:32.100> actually<00:15:32.660> isn't<00:15:33.660> able<00:15:33.960> to 00:15:34.630 --> 00:15:34.640 align:start position:0% verifier doesn't actually isn't able to 00:15:34.640 --> 00:15:42.200 align:start position:0% verifier doesn't actually isn't able to wear 00:15:42.200 --> 00:15:42.210 align:start position:0% 00:15:42.210 --> 00:15:45.020 align:start position:0% folks<00:15:42.810> coming<00:15:43.230> back<00:15:43.350> reforms<00:15:43.860> we<00:15:44.250> implemented 00:15:45.020 --> 00:15:45.030 align:start position:0% folks coming back reforms we implemented 00:15:45.030 --> 00:15:48.380 align:start position:0% folks coming back reforms we implemented a<00:15:45.120> few<00:15:45.150> variants<00:15:45.900> of<00:15:47.240> different<00:15:48.240> countries 00:15:48.380 --> 00:15:48.390 align:start position:0% a few variants of different countries 00:15:48.390 --> 00:15:53.260 align:start position:0% a few variants of different countries and<00:15:48.900> been<00:15:49.470> to<00:15:49.590> Russia<00:15:49.740> for<00:15:50.190> a<00:15:50.250> free<00:15:50.910> type<00:15:51.150> of<00:15:51.860> 32 00:15:53.260 --> 00:15:53.270 align:start position:0% and been to Russia for a free type of 32 00:15:53.270 --> 00:15:57.130 align:start position:0% and been to Russia for a free type of 32 levels<00:15:54.890> and<00:15:55.890> the<00:15:56.130> basic<00:15:56.520> implementation 00:15:57.130 --> 00:15:57.140 align:start position:0% levels and the basic implementation 00:15:57.140 --> 00:16:01.270 align:start position:0% levels and the basic implementation surprisingly<00:15:58.140> is<00:15:58.560> slow<00:15:59.540> requiring<00:16:00.540> 1.8 00:16:01.270 --> 00:16:01.280 align:start position:0% surprisingly is slow requiring 1.8 00:16:01.280 --> 00:16:05.330 align:start position:0% surprisingly is slow requiring 1.8 million<00:16:02.280> guests<00:16:02.850> or<00:16:03.320> every<00:16:04.320> insert<00:16:04.770> it 00:16:05.330 --> 00:16:05.340 align:start position:0% million guests or every insert it 00:16:05.340 --> 00:16:06.770 align:start position:0% million guests or every insert it doesn't<00:16:05.670> matter<00:16:05.850> where<00:16:06.240> in<00:16:06.360> the<00:16:06.390> GB<00:16:06.660> you're 00:16:06.770 --> 00:16:06.780 align:start position:0% doesn't matter where in the GB you're 00:16:06.780 --> 00:16:08.060 align:start position:0% doesn't matter where in the GB you're inserting<00:16:07.020> you're<00:16:07.320> always<00:16:07.440> going<00:16:07.800> to<00:16:07.830> the 00:16:08.060 --> 00:16:08.070 align:start position:0% inserting you're always going to the 00:16:08.070 --> 00:16:10.400 align:start position:0% inserting you're always going to the root<00:16:08.310> of<00:16:08.490> the<00:16:08.610> tree<00:16:08.850> and<00:16:09.330> so<00:16:09.750> it's<00:16:10.110> always 00:16:10.400 --> 00:16:10.410 align:start position:0% root of the tree and so it's always 00:16:10.410 --> 00:16:13.960 align:start position:0% root of the tree and so it's always expensive<00:16:11.240> then<00:16:12.240> in<00:16:12.390> the<00:16:12.510> optimized<00:16:12.900> case 00:16:13.960 --> 00:16:13.970 align:start position:0% expensive then in the optimized case 00:16:13.970 --> 00:16:17.020 align:start position:0% expensive then in the optimized case we're<00:16:14.970> able<00:16:15.030> to<00:16:15.390> save<00:16:15.840> a<00:16:15.870> little<00:16:16.080> bit<00:16:16.230> of<00:16:16.350> time 00:16:17.020 --> 00:16:17.030 align:start position:0% we're able to save a little bit of time 00:16:17.030 --> 00:16:20.070 align:start position:0% we're able to save a little bit of time or<00:16:18.030> gas 00:16:20.070 --> 00:16:20.080 align:start position:0% or gas 00:16:20.080 --> 00:16:23.460 align:start position:0% or gas 1.7<00:16:21.040> million<00:16:21.730> got<00:16:22.030> and<00:16:22.420> then<00:16:22.630> it<00:16:22.750> rubs<00:16:23.080> the 00:16:23.460 --> 00:16:23.470 align:start position:0% 1.7 million got and then it rubs the 00:16:23.470 --> 00:16:26.940 align:start position:0% 1.7 million got and then it rubs the worst<00:16:23.650> a<00:16:24.030> 16.7<00:16:25.050> but<00:16:26.050> in<00:16:26.140> the<00:16:26.230> best<00:16:26.440> case<00:16:26.680> that 00:16:26.940 --> 00:16:26.950 align:start position:0% worst a 16.7 but in the best case that 00:16:26.950 --> 00:16:30.570 align:start position:0% worst a 16.7 but in the best case that can<00:16:27.100> be<00:16:27.220> as<00:16:27.370> low<00:16:27.580> as<00:16:28.440> 45,000<00:16:29.500> absent<00:16:30.190> is<00:16:30.340> quite 00:16:30.570 --> 00:16:30.580 align:start position:0% can be as low as 45,000 absent is quite 00:16:30.580 --> 00:16:33.600 align:start position:0% can be as low as 45,000 absent is quite incredible<00:16:30.880> and<00:16:31.560> then<00:16:32.560> in<00:16:32.800> the<00:16:32.920> mean<00:16:33.100> case<00:16:33.340> on 00:16:33.600 --> 00:16:33.610 align:start position:0% incredible and then in the mean case on 00:16:33.610 --> 00:16:36.000 align:start position:0% incredible and then in the mean case on average<00:16:33.940> that's<00:16:34.240> just<00:16:34.930> under<00:16:35.110> that's<00:16:35.590> all 00:16:36.000 --> 00:16:36.010 align:start position:0% average that's just under that's all 00:16:36.010 --> 00:16:40.170 align:start position:0% average that's just under that's all just<00:16:36.310> go<00:16:36.550> for<00:16:36.970> it<00:16:37.000> and<00:16:38.790> so<00:16:39.790> the<00:16:39.910> next<00:16:39.940> question 00:16:40.170 --> 00:16:40.180 align:start position:0% just go for it and so the next question 00:16:40.180 --> 00:16:42.240 align:start position:0% just go for it and so the next question is<00:16:40.510> okay<00:16:40.840> so<00:16:40.870> if<00:16:41.110> you<00:16:41.230> want<00:16:41.380> to<00:16:41.470> use<00:16:41.680> this<00:16:41.980> data 00:16:42.240 --> 00:16:42.250 align:start position:0% is okay so if you want to use this data 00:16:42.250 --> 00:16:43.560 align:start position:0% is okay so if you want to use this data structure<00:16:42.580> and<00:16:43.000> if<00:16:43.090> you<00:16:43.210> were<00:16:43.330> to<00:16:43.450> implement 00:16:43.560 --> 00:16:43.570 align:start position:0% structure and if you were to implement 00:16:43.570 --> 00:16:46.760 align:start position:0% structure and if you were to implement see<00:16:44.110> catch<00:16:44.320> what<00:16:44.890> would<00:16:45.040> the<00:16:45.160> actual<00:16:45.580> cost<00:16:45.910> of 00:16:46.760 --> 00:16:46.770 align:start position:0% see catch what would the actual cost of 00:16:46.770 --> 00:16:51.660 align:start position:0% see catch what would the actual cost of agents<00:16:47.770> actually<00:16:47.980> mean 00:16:51.660 --> 00:16:51.670 align:start position:0% 00:16:51.670 --> 00:16:54.180 align:start position:0% and<00:16:51.940> so<00:16:52.120> we<00:16:52.240> implemented<00:16:52.620> the<00:16:53.620> verification 00:16:54.180 --> 00:16:54.190 align:start position:0% and so we implemented the verification 00:16:54.190 --> 00:16:56.070 align:start position:0% and so we implemented the verification of<00:16:54.220> the<00:16:54.280> piece<00:16:54.520> of<00:16:55.060> that<00:16:55.300> we<00:16:55.570> brought<00:16:55.840> six 00:16:56.070 --> 00:16:56.080 align:start position:0% of the piece of that we brought six 00:16:56.080 --> 00:17:00.690 align:start position:0% of the piece of that we brought six teams<00:16:57.030> and<00:16:58.030> we<00:16:58.840> put<00:16:59.260> these<00:16:59.350> numbers<00:16:59.710> so<00:17:00.040> on 00:17:00.690 --> 00:17:00.700 align:start position:0% teams and we put these numbers so on 00:17:00.700 --> 00:17:06.540 align:start position:0% teams and we put these numbers so on average<00:17:02.460> around<00:17:03.460> 10,000<00:17:05.070> depending<00:17:06.070> on<00:17:06.400> the 00:17:06.540 --> 00:17:06.550 align:start position:0% average around 10,000 depending on the 00:17:06.550 --> 00:17:09.240 align:start position:0% average around 10,000 depending on the inputs<00:17:07.000> you<00:17:07.089> have<00:17:07.209> to<00:17:07.900> your<00:17:08.020> for<00:17:08.350> operation<00:17:09.070> so 00:17:09.240 --> 00:17:09.250 align:start position:0% inputs you have to your for operation so 00:17:09.250 --> 00:17:11.640 align:start position:0% inputs you have to your for operation so you<00:17:09.400> can<00:17:09.550> have<00:17:09.670> one<00:17:09.880> or<00:17:10.000> two<00:17:10.120> inputs<00:17:10.650> you're 00:17:11.640 --> 00:17:11.650 align:start position:0% you can have one or two inputs you're 00:17:11.650 --> 00:17:13.440 align:start position:0% you can have one or two inputs you're gonna<00:17:11.770> have<00:17:11.980> to<00:17:12.190> add<00:17:12.370> one<00:17:12.640> or<00:17:12.760> two<00:17:12.790> entries<00:17:13.209> to 00:17:13.440 --> 00:17:13.450 align:start position:0% gonna have to add one or two entries to 00:17:13.450 --> 00:17:15.060 align:start position:0% gonna have to add one or two entries to nullify<00:17:13.750> ourselves<00:17:14.410> for<00:17:14.560> this<00:17:14.650> we<00:17:14.830> take 00:17:15.060 --> 00:17:15.070 align:start position:0% nullify ourselves for this we take 00:17:15.070 --> 00:17:18.570 align:start position:0% nullify ourselves for this we take around<00:17:16.000> 26,000<00:17:16.959> or 00:17:18.570 --> 00:17:18.580 align:start position:0% around 26,000 or 00:17:18.580 --> 00:17:23.530 align:start position:0% around 26,000 or to<00:17:19.580> prevent<00:17:20.570> depends<00:17:21.200> on<00:17:21.680> return<00:17:22.240> and<00:17:23.240> then 00:17:23.530 --> 00:17:23.540 align:start position:0% to prevent depends on return and then 00:17:23.540 --> 00:17:25.720 align:start position:0% to prevent depends on return and then next<00:17:23.900> we<00:17:24.050> have<00:17:24.200> to<00:17:24.320> pre-process<00:17:24.710> the<00:17:25.220> in<00:17:25.520> the 00:17:25.720 --> 00:17:25.730 align:start position:0% next we have to pre-process the in the 00:17:25.730 --> 00:17:27.580 align:start position:0% next we have to pre-process the in the public<00:17:25.880> importance<00:17:26.180> so<00:17:26.810> in<00:17:26.930> this<00:17:27.050> case<00:17:27.320> the 00:17:27.580 --> 00:17:27.590 align:start position:0% public importance so in this case the 00:17:27.590 --> 00:17:30.820 align:start position:0% public importance so in this case the public<00:17:27.860> inputs<00:17:28.190> for<00:17:28.340> now<00:17:28.490> these<00:17:29.390> shrubs<00:17:29.830> so 00:17:30.820 --> 00:17:30.830 align:start position:0% public inputs for now these shrubs so 00:17:30.830 --> 00:17:32.860 align:start position:0% public inputs for now these shrubs so this<00:17:31.190> actually<00:17:31.610> costs<00:17:31.970> more<00:17:32.210> than<00:17:32.270> before 00:17:32.860 --> 00:17:32.870 align:start position:0% this actually costs more than before 00:17:32.870 --> 00:17:40.870 align:start position:0% this actually costs more than before before<00:17:33.200> we<00:17:33.230> only<00:17:33.470> had<00:17:37.960> but<00:17:38.960> we've<00:17:39.320> yet<00:17:40.190> key<00:17:40.520> one 00:17:40.870 --> 00:17:40.880 align:start position:0% before we only had but we've yet key one 00:17:40.880 --> 00:17:41.710 align:start position:0% before we only had but we've yet key one 108 00:17:41.710 --> 00:17:41.720 align:start position:0% 108 00:17:41.720 --> 00:17:44.080 align:start position:0% 108 this<00:17:42.140> is<00:17:42.380> gonna<00:17:42.950> be<00:17:43.130> a<00:17:43.160> lot<00:17:43.280> cheaper<00:17:43.340> over<00:17:44.000> the 00:17:44.080 --> 00:17:44.090 align:start position:0% this is gonna be a lot cheaper over the 00:17:44.090 --> 00:17:46.480 align:start position:0% this is gonna be a lot cheaper over the next<00:17:44.330> five<00:17:44.510> pork<00:17:44.840> and<00:17:45.500> so<00:17:45.800> it's<00:17:46.010> still<00:17:46.250> pretty 00:17:46.480 --> 00:17:46.490 align:start position:0% next five pork and so it's still pretty 00:17:46.490 --> 00:17:49.480 align:start position:0% next five pork and so it's still pretty reasonable<00:17:47.060> around<00:17:47.300> 300,000<00:17:48.170> and<00:17:48.740> finding 00:17:49.480 --> 00:17:49.490 align:start position:0% reasonable around 300,000 and finding 00:17:49.490 --> 00:17:51.820 align:start position:0% reasonable around 300,000 and finding out<00:17:49.610> to<00:17:49.880> do<00:17:50.300> the<00:17:50.450> actual<00:17:50.750> verification<00:17:51.200> which 00:17:51.820 --> 00:17:51.830 align:start position:0% out to do the actual verification which 00:17:51.830 --> 00:17:53.710 align:start position:0% out to do the actual verification which requires<00:17:52.250> around<00:17:52.550> for<00:17:52.820> pairing<00:17:53.180> operations 00:17:53.710 --> 00:17:53.720 align:start position:0% requires around for pairing operations 00:17:53.720 --> 00:17:57.450 align:start position:0% requires around for pairing operations that<00:17:53.870> believe<00:17:54.160> which<00:17:55.160> adds<00:17:55.370> another<00:17:55.540> profit 00:17:57.450 --> 00:17:57.460 align:start position:0% that believe which adds another profit 00:17:57.460 --> 00:18:01.240 align:start position:0% that believe which adds another profit and<00:17:58.460> so<00:17:58.670> the<00:17:58.790> total<00:17:58.940> cost<00:17:59.240> is<00:17:59.570> around<00:18:00.250> five 00:18:01.240 --> 00:18:01.250 align:start position:0% and so the total cost is around five 00:18:01.250 --> 00:18:03.910 align:start position:0% and so the total cost is around five hundred<00:18:01.280> thousand<00:18:02.440> pending<00:18:03.440> on<00:18:03.560> from<00:18:03.770> you 00:18:03.910 --> 00:18:03.920 align:start position:0% hundred thousand pending on from you 00:18:03.920 --> 00:18:08.560 align:start position:0% hundred thousand pending on from you puts<00:18:04.160> you<00:18:04.250> up<00:18:04.460> again<00:18:04.730> which<00:18:05.690> is<00:18:06.410> about<00:18:06.790> 2x<00:18:07.790> more 00:18:08.560 --> 00:18:08.570 align:start position:0% puts you up again which is about 2x more 00:18:08.570 --> 00:18:11.530 align:start position:0% puts you up again which is about 2x more expensive<00:18:09.080> and<00:18:09.260> a<00:18:09.440> step<00:18:09.800> but<00:18:10.670> you<00:18:11.060> get<00:18:11.360> no 00:18:11.530 --> 00:18:11.540 align:start position:0% expensive and a step but you get no 00:18:11.540 --> 00:18:13.610 align:start position:0% expensive and a step but you get no eligibility<00:18:12.050> so<00:18:12.650> all<00:18:12.980> over<00:18:13.190> here 00:18:13.610 --> 00:18:13.620 align:start position:0% eligibility so all over here 00:18:13.620 --> 00:18:17.530 align:start position:0% eligibility so all over here and<00:18:14.630> Senator<00:18:15.630> addresses<00:18:16.230> right<00:18:16.440> now<00:18:16.590> right 00:18:17.530 --> 00:18:17.540 align:start position:0% and Senator addresses right now right 00:18:17.540 --> 00:18:20.600 align:start position:0% and Senator addresses right now right now<00:18:18.540> we<00:18:18.600> also<00:18:18.900> look<00:18:19.170> at<00:18:19.200> that<00:18:19.470> what<00:18:20.309> this<00:18:20.430> would 00:18:20.600 --> 00:18:20.610 align:start position:0% now we also look at that what this would 00:18:20.610 --> 00:18:22.190 align:start position:0% now we also look at that what this would look<00:18:20.670> like<00:18:20.760> a<00:18:20.940> punk<00:18:21.240> we<00:18:21.510> didn't<00:18:21.840> implement 00:18:22.190 --> 00:18:22.200 align:start position:0% look like a punk we didn't implement 00:18:22.200 --> 00:18:24.590 align:start position:0% look like a punk we didn't implement this<00:18:22.740> like<00:18:22.950> we<00:18:23.070> did<00:18:23.220> across<00:18:23.580> 16<00:18:23.850> but<00:18:24.270> we<00:18:24.390> did 00:18:24.590 --> 00:18:24.600 align:start position:0% this like we did across 16 but we did 00:18:24.600 --> 00:18:27.110 align:start position:0% this like we did across 16 but we did his<00:18:25.110> estimates<00:18:25.650> and<00:18:26.370> the<00:18:26.490> reason<00:18:26.940> is 00:18:27.110 --> 00:18:27.120 align:start position:0% his estimates and the reason is 00:18:27.120 --> 00:18:29.390 align:start position:0% his estimates and the reason is interesting<00:18:27.540> because<00:18:27.870> the<00:18:28.350> processing<00:18:29.280> of 00:18:29.390 --> 00:18:29.400 align:start position:0% interesting because the processing of 00:18:29.400 --> 00:18:32.630 align:start position:0% interesting because the processing of the<00:18:29.520> public<00:18:29.790> inputs<00:18:30.120> it's<00:18:30.300> a<00:18:30.390> lot<00:18:30.540> cheaper<00:18:31.640> you 00:18:32.630 --> 00:18:32.640 align:start position:0% the public inputs it's a lot cheaper you 00:18:32.640 --> 00:18:37.120 align:start position:0% the public inputs it's a lot cheaper you don't<00:18:32.820> have<00:18:32.970> to<00:18:33.120> do<00:18:35.180> exponentiation<00:18:36.180> and<00:18:36.420> so 00:18:37.120 --> 00:18:37.130 align:start position:0% don't have to do exponentiation and so 00:18:37.130 --> 00:18:39.280 align:start position:0% don't have to do exponentiation and so this<00:18:38.130> is<00:18:38.280> actually<00:18:38.580> quite<00:18:38.700> cheaper 00:18:39.280 --> 00:18:39.290 align:start position:0% this is actually quite cheaper 00:18:39.290 --> 00:18:41.600 align:start position:0% this is actually quite cheaper unfortunately<00:18:40.290> this<00:18:40.410> ends<00:18:40.650> up<00:18:40.770> being<00:18:40.830> a<00:18:41.370> fair 00:18:41.600 --> 00:18:41.610 align:start position:0% unfortunately this ends up being a fair 00:18:41.610 --> 00:18:43.940 align:start position:0% unfortunately this ends up being a fair amount<00:18:41.760> more<00:18:42.120> expensive<00:18:42.690> so<00:18:43.470> the<00:18:43.590> overall 00:18:43.940 --> 00:18:43.950 align:start position:0% amount more expensive so the overall 00:18:43.950 --> 00:18:52.840 align:start position:0% amount more expensive so the overall price<00:18:44.309> overall<00:18:45.090> cost<00:18:45.390> of<00:18:45.570> the<00:18:45.660> gas<00:18:46.610> is<00:18:47.610> high 00:18:52.840 --> 00:18:52.850 align:start position:0% 00:18:52.850 --> 00:18:56.570 align:start position:0% country<00:18:53.850> you're<00:18:54.809> gonna<00:18:54.929> have<00:18:55.050> the<00:18:55.950> less<00:18:56.160> I 00:18:56.570 --> 00:18:56.580 align:start position:0% country you're gonna have the less I 00:18:56.580 --> 00:18:59.150 align:start position:0% country you're gonna have the less I guess<00:18:57.420> that<00:18:57.750> in<00:18:57.870> here<00:18:58.140> or<00:18:58.320> versus<00:18:58.590> your<00:18:58.890> here 00:18:59.150 --> 00:18:59.160 align:start position:0% guess that in here or versus your here 00:18:59.160 --> 00:19:02.890 align:start position:0% guess that in here or versus your here that's<00:18:59.309> Washington 00:19:02.890 --> 00:19:02.900 align:start position:0% 00:19:02.900 --> 00:19:07.720 align:start position:0% quite<00:19:03.530> a<00:19:03.560> bit<00:19:03.740> more<00:19:03.950> masculine<00:19:05.530> so<00:19:06.730> generally 00:19:07.720 --> 00:19:07.730 align:start position:0% quite a bit more masculine so generally 00:19:07.730 --> 00:19:09.670 align:start position:0% quite a bit more masculine so generally are<00:19:08.210> hopeful<00:19:08.570> that<00:19:08.600> with<00:19:08.930> some<00:19:09.050> transitions 00:19:09.670 --> 00:19:09.680 align:start position:0% are hopeful that with some transitions 00:19:09.680 --> 00:19:14.850 align:start position:0% are hopeful that with some transitions we<00:19:09.860> can<00:19:10.310> lower<00:19:10.490> this<00:19:10.730> and<00:19:11.120> potentially 00:19:14.850 --> 00:19:14.860 align:start position:0% 00:19:14.860 --> 00:19:18.190 align:start position:0% cheaper<00:19:15.860> than<00:19:16.010> she<00:19:16.130> brought<00:19:16.520> 16<00:19:17.030> with<00:19:17.780> an<00:19:17.960> even 00:19:18.190 --> 00:19:18.200 align:start position:0% cheaper than she brought 16 with an even 00:19:18.200 --> 00:19:22.360 align:start position:0% cheaper than she brought 16 with an even length 00:19:22.360 --> 00:19:22.370 align:start position:0% 00:19:22.370 --> 00:19:25.570 align:start position:0% I 00:19:25.570 --> 00:19:25.580 align:start position:0% 00:19:25.580 --> 00:19:29.830 align:start position:0% Oh<00:19:26.360> so<00:19:26.539> I<00:19:26.570> mentioned<00:19:26.960> mobile<00:19:28.059> what<00:19:29.059> about<00:19:29.299> it 00:19:29.830 --> 00:19:29.840 align:start position:0% Oh so I mentioned mobile what about it 00:19:29.840 --> 00:19:32.259 align:start position:0% Oh so I mentioned mobile what about it so<00:19:30.769> the<00:19:30.889> nice<00:19:31.039> thing<00:19:31.279> is<00:19:31.309> by<00:19:31.610> using<00:19:31.850> them<00:19:32.029> see 00:19:32.259 --> 00:19:32.269 align:start position:0% so the nice thing is by using them see 00:19:32.269 --> 00:19:34.180 align:start position:0% so the nice thing is by using them see the<00:19:32.539> tripping<00:19:32.840> times<00:19:33.110> are<00:19:33.409> quite<00:19:33.769> short 00:19:34.180 --> 00:19:34.190 align:start position:0% the tripping times are quite short 00:19:34.190 --> 00:19:37.019 align:start position:0% the tripping times are quite short that's<00:19:34.639> quite<00:19:34.879> elegant<00:19:35.269> so<00:19:36.259> you<00:19:36.440> can 00:19:37.019 --> 00:19:37.029 align:start position:0% that's quite elegant so you can 00:19:37.029 --> 00:19:39.609 align:start position:0% that's quite elegant so you can construct<00:19:38.029> these<00:19:38.269> transactions<00:19:38.960> in<00:19:39.259> just<00:19:39.470> a 00:19:39.609 --> 00:19:39.619 align:start position:0% construct these transactions in just a 00:19:39.619 --> 00:19:44.710 align:start position:0% construct these transactions in just a few<00:19:39.769> seconds<00:19:40.340> on<00:19:40.549> a<00:19:41.110> $200<00:19:42.110> phone<00:19:43.720> but 00:19:44.710 --> 00:19:44.720 align:start position:0% few seconds on a $200 phone but 00:19:44.720 --> 00:19:48.480 align:start position:0% few seconds on a $200 phone but unfortunately<00:19:45.999> for<00:19:46.999> that<00:19:47.090> my<00:19:47.419> client 00:19:48.480 --> 00:19:48.490 align:start position:0% unfortunately for that my client 00:19:48.490 --> 00:19:51.090 align:start position:0% unfortunately for that my client so<00:19:48.940> it's<00:19:49.570> hard<00:19:49.870> to<00:19:49.960> know<00:19:50.110> which<00:19:50.470> productions 00:19:51.090 --> 00:19:51.100 align:start position:0% so it's hard to know which productions 00:19:51.100 --> 00:19:52.860 align:start position:0% so it's hard to know which productions are<00:19:51.220> reviewable<00:19:51.670> since<00:19:52.030> they<00:19:52.180> are<00:19:52.330> encrypted 00:19:52.860 --> 00:19:52.870 align:start position:0% are reviewable since they are encrypted 00:19:52.870 --> 00:19:55.290 align:start position:0% are reviewable since they are encrypted you<00:19:53.560> would<00:19:53.710> have<00:19:53.860> to<00:19:53.980> try<00:19:54.430> to<00:19:54.490> decrypt<00:19:54.910> every 00:19:55.290 --> 00:19:55.300 align:start position:0% you would have to try to decrypt every 00:19:55.300 --> 00:19:57.630 align:start position:0% you would have to try to decrypt every transaction<00:19:55.660> in<00:19:56.440> every<00:19:56.710> block<00:19:56.920> to<00:19:57.160> find<00:19:57.400> which 00:19:57.630 --> 00:19:57.640 align:start position:0% transaction in every block to find which 00:19:57.640 --> 00:20:03.170 align:start position:0% transaction in every block to find which is<00:19:57.670> actually<00:19:58.210> smashing<00:19:59.010> so<00:20:00.010> that's<00:20:00.870> my<00:20:01.870> client 00:20:03.170 --> 00:20:03.180 align:start position:0% is actually smashing so that's my client 00:20:03.180 --> 00:20:06.930 align:start position:0% is actually smashing so that's my client and<00:20:04.180> it's<00:20:04.420> also<00:20:04.570> hard<00:20:04.960> to<00:20:05.490> know<00:20:06.490> when<00:20:06.790> you're 00:20:06.930 --> 00:20:06.940 align:start position:0% and it's also hard to know when you're 00:20:06.940 --> 00:20:08.550 align:start position:0% and it's also hard to know when you're hidden<00:20:07.120> in<00:20:07.330> which<00:20:07.480> to<00:20:07.630> be<00:20:07.810> to<00:20:07.990> construct<00:20:08.410> those 00:20:08.550 --> 00:20:08.560 align:start position:0% hidden in which to be to construct those 00:20:08.560 --> 00:20:11.600 align:start position:0% hidden in which to be to construct those working<00:20:09.010> groups<00:20:09.130> going<00:20:10.060> up<00:20:10.210> to<00:20:10.420> the<00:20:10.570> frontier 00:20:11.600 --> 00:20:11.610 align:start position:0% working groups going up to the frontier 00:20:11.610 --> 00:20:14.400 align:start position:0% working groups going up to the frontier a<00:20:12.610> full<00:20:13.060> note<00:20:13.270> in<00:20:13.570> figured<00:20:13.960> it's<00:20:14.080> uh<00:20:14.200> pretty 00:20:14.400 --> 00:20:14.410 align:start position:0% a full note in figured it's uh pretty 00:20:14.410 --> 00:20:16.080 align:start position:0% a full note in figured it's uh pretty easily<00:20:14.620> as<00:20:15.160> they<00:20:15.370> see<00:20:15.430> every<00:20:15.760> transaction 00:20:16.080 --> 00:20:16.090 align:start position:0% easily as they see every transaction 00:20:16.090 --> 00:20:20.130 align:start position:0% easily as they see every transaction they<00:20:16.710> maintain<00:20:17.710> the<00:20:18.070> piece<00:20:18.370> of<00:20:18.820> the<00:20:19.810> tree<00:20:20.110> that 00:20:20.130 --> 00:20:20.140 align:start position:0% they maintain the piece of the tree that 00:20:20.140 --> 00:20:22.910 align:start position:0% they maintain the piece of the tree that they<00:20:20.650> care<00:20:20.860> about<00:20:20.980> the<00:20:21.340> Constructors<00:20:21.880> groups 00:20:22.910 --> 00:20:22.920 align:start position:0% they care about the Constructors groups 00:20:22.920 --> 00:20:26.340 align:start position:0% they care about the Constructors groups but<00:20:23.920> my<00:20:24.460> client<00:20:24.940> you<00:20:25.780> wouldn't<00:20:26.110> want<00:20:26.290> to 00:20:26.340 --> 00:20:26.350 align:start position:0% but my client you wouldn't want to 00:20:26.350 --> 00:20:28.350 align:start position:0% but my client you wouldn't want to actually<00:20:26.590> various<00:20:27.160> will<00:20:27.370> note<00:20:27.550> find<00:20:28.090> those 00:20:28.350 --> 00:20:28.360 align:start position:0% actually various will note find those 00:20:28.360 --> 00:20:36.139 align:start position:0% actually various will note find those notes<00:20:28.740> because<00:20:29.740> I<00:20:29.830> would<00:20:29.980> reveal<00:20:30.250> which 00:20:36.139 --> 00:20:36.149 align:start position:0% 00:20:36.149 --> 00:20:40.590 align:start position:0% so<00:20:37.149> one<00:20:38.020> solution<00:20:38.200> is<00:20:38.649> to<00:20:38.799> use<00:20:38.890> operators<00:20:39.600> and 00:20:40.590 --> 00:20:40.600 align:start position:0% so one solution is to use operators and 00:20:40.600 --> 00:20:42.980 align:start position:0% so one solution is to use operators and to<00:20:40.960> introduce<00:20:41.320> the<00:20:41.470> concept<00:20:41.830> of<00:20:41.950> a<00:20:42.100> routine 00:20:42.980 --> 00:20:42.990 align:start position:0% to introduce the concept of a routine 00:20:42.990 --> 00:20:45.269 align:start position:0% to introduce the concept of a routine decryption<00:20:43.990> key<00:20:44.200> would<00:20:44.470> allow<00:20:44.710> for<00:20:45.070> twice 00:20:45.269 --> 00:20:45.279 align:start position:0% decryption key would allow for twice 00:20:45.279 --> 00:20:48.230 align:start position:0% decryption key would allow for twice encrypt<00:20:46.090> all<00:20:46.330> transactions<00:20:47.080> Center<00:20:47.350> for<00:20:47.559> you 00:20:48.230 --> 00:20:48.240 align:start position:0% encrypt all transactions Center for you 00:20:48.240 --> 00:20:53.700 align:start position:0% encrypt all transactions Center for you without<00:20:49.240> even<00:20:49.980> the<00:20:51.809> transactions<00:20:52.809> see<00:20:53.590> the 00:20:53.700 --> 00:20:53.710 align:start position:0% without even the transactions see the 00:20:53.710 --> 00:21:09.779 align:start position:0% without even the transactions see the balances<00:20:54.159> and<00:20:54.340> the<00:20:54.370> sender's<00:21:00.330> trust<00:21:08.789> any 00:21:09.779 --> 00:21:09.789 align:start position:0% balances and the sender's trust any 00:21:09.789 --> 00:21:26.940 align:start position:0% balances and the sender's trust any questions<00:21:24.299> so<00:21:25.299> the<00:21:25.390> sides<00:21:25.630> of<00:21:25.809> the<00:21:26.020> they've 00:21:26.940 --> 00:21:26.950 align:start position:0% questions so the sides of the they've 00:21:26.950 --> 00:21:29.909 align:start position:0% questions so the sides of the they've been<00:21:27.100> a<00:21:27.130> guess<00:21:27.399> that<00:21:27.940> you<00:21:28.059> have<00:21:28.330> to<00:21:28.919> approve 00:21:29.909 --> 00:21:29.919 align:start position:0% been a guess that you have to approve 00:21:29.919 --> 00:21:33.090 align:start position:0% been a guess that you have to approve and<00:21:30.309> I<00:21:30.399> guess<00:21:30.700> that<00:21:30.730> you<00:21:30.940> have<00:21:31.029> to<00:21:31.179> pay<00:21:31.830> will<00:21:32.830> be 00:21:33.090 --> 00:21:33.100 align:start position:0% and I guess that you have to pay will be 00:21:33.100 --> 00:21:34.980 align:start position:0% and I guess that you have to pay will be different<00:21:33.580> depending<00:21:33.700> on<00:21:34.059> where<00:21:34.360> you<00:21:34.539> are<00:21:34.570> in 00:21:34.980 --> 00:21:34.990 align:start position:0% different depending on where you are in 00:21:34.990 --> 00:21:38.250 align:start position:0% different depending on where you are in that<00:21:35.169> country<00:21:35.740> and<00:21:36.669> so<00:21:37.210> one<00:21:37.690> way<00:21:37.870> of<00:21:38.080> actually 00:21:38.250 --> 00:21:38.260 align:start position:0% that country and so one way of actually 00:21:38.260 --> 00:21:40.680 align:start position:0% that country and so one way of actually making<00:21:38.590> this<00:21:38.830> a<00:21:38.890> little<00:21:39.220> bit<00:21:39.490> more<00:21:39.669> uniform<00:21:40.240> is 00:21:40.680 --> 00:21:40.690 align:start position:0% making this a little bit more uniform is 00:21:40.690 --> 00:21:43.200 align:start position:0% making this a little bit more uniform is to<00:21:40.809> use<00:21:41.049> a<00:21:41.289> gas<00:21:41.470> token<00:21:41.919> so<00:21:42.669> that<00:21:42.850> everyone 00:21:43.200 --> 00:21:43.210 align:start position:0% to use a gas token so that everyone 00:21:43.210 --> 00:21:45.120 align:start position:0% to use a gas token so that everyone contributes<00:21:43.750> more<00:21:44.230> or<00:21:44.409> less<00:21:44.529> the<00:21:44.710> same<00:21:44.919> on<00:21:45.100> a 00:21:45.120 --> 00:21:45.130 align:start position:0% contributes more or less the same on a 00:21:45.130 --> 00:21:48.120 align:start position:0% contributes more or less the same on a gas<00:21:45.370> and<00:21:46.090> if<00:21:46.210> you<00:21:46.330> happen<00:21:46.809> to<00:21:46.840> be<00:21:46.960> unlucky<00:21:47.649> and 00:21:48.120 --> 00:21:48.130 align:start position:0% gas and if you happen to be unlucky and 00:21:48.130 --> 00:21:52.139 align:start position:0% gas and if you happen to be unlucky and go<00:21:48.940> all<00:21:49.029> the<00:21:49.090> way<00:21:49.120> to<00:21:49.240> the<00:21:49.360> room<00:21:49.679> then<00:21:51.000> mean<00:21:52.000> on 00:21:52.139 --> 00:21:52.149 align:start position:0% go all the way to the room then mean on 00:21:52.149 --> 00:21:54.230 align:start position:0% go all the way to the room then mean on that<00:21:52.179> guest<00:21:52.510> or<00:21:52.750> more<00:21:53.110> than<00:21:53.320> other<00:21:53.529> folks 00:21:54.230 --> 00:21:54.240 align:start position:0% that guest or more than other folks 00:21:54.240 --> 00:21:56.120 align:start position:0% that guest or more than other folks equation 00:21:56.120 --> 00:21:56.130 align:start position:0% equation 00:21:56.130 --> 00:21:58.590 align:start position:0% equation it's<00:21:57.130> not<00:21:57.280> about<00:21:57.370> the<00:21:57.669> size<00:21:57.850> of<00:21:58.030> the<00:21:58.150> pool<00:21:58.360> it's 00:21:58.590 --> 00:21:58.600 align:start position:0% it's not about the size of the pool it's 00:21:58.600 --> 00:22:04.850 align:start position:0% it's not about the size of the pool it's more<00:21:58.929> about<00:22:00.240> the<00:22:01.240> size 00:22:04.850 --> 00:22:04.860 align:start position:0% 00:22:04.860 --> 00:22:08.240 align:start position:0% and<00:22:05.790> for<00:22:06.210> you<00:22:06.450> under<00:22:07.200> the<00:22:07.230> Bible<00:22:07.950> as<00:22:08.040> the 00:22:08.240 --> 00:22:08.250 align:start position:0% and for you under the Bible as the 00:22:08.250 --> 00:22:14.710 align:start position:0% and for you under the Bible as the ontology<00:22:09.000> deter<00:22:10.309> always<00:22:11.309> fast-paced<00:22:12.090> action 00:22:14.710 --> 00:22:14.720 align:start position:0% ontology deter always fast-paced action 00:22:14.720 --> 00:22:19.080 align:start position:0% ontology deter always fast-paced action that's<00:22:15.720> what<00:22:16.160> puppetry 00:22:19.080 --> 00:22:19.090 align:start position:0% that's what puppetry 00:22:19.090 --> 00:22:21.019 align:start position:0% that's what puppetry [Music] 00:22:21.019 --> 00:22:21.029 align:start position:0% [Music] 00:22:21.029 --> 00:22:24.840 align:start position:0% [Music] every<00:22:21.689> joke 00:22:24.840 --> 00:22:24.850 align:start position:0% 00:22:24.850 --> 00:22:30.039 align:start position:0% have<00:22:25.850> any<00:22:26.030> differences 00:22:30.039 --> 00:22:30.049 align:start position:0% 00:22:30.049 --> 00:22:33.639 align:start position:0% I'm<00:22:30.740> married<00:22:31.039> so<00:22:31.070> but<00:22:31.520> I'm<00:22:31.640> not<00:22:31.820> the<00:22:32.649> Restless 00:22:33.639 --> 00:22:33.649 align:start position:0% I'm married so but I'm not the Restless 00:22:33.649 --> 00:22:39.680 align:start position:0% I'm married so but I'm not the Restless chat<00:22:33.890> why<00:22:35.440> so<00:22:36.440> you<00:22:36.529> get<00:22:37.279> slightly 00:22:39.680 --> 00:22:39.690 align:start position:0% 00:22:39.690 --> 00:22:41.940 align:start position:0% it<00:22:40.170> was<00:22:40.320> inspired<00:22:40.740> by 00:22:41.940 --> 00:22:41.950 align:start position:0% it was inspired by 00:22:41.950 --> 00:22:45.570 align:start position:0% it was inspired by it's<00:22:43.440> slightly<00:22:44.440> different<00:22:44.590> Boston<00:22:45.220> but 00:22:45.570 --> 00:22:45.580 align:start position:0% it's slightly different Boston but 00:22:45.580 --> 00:22:47.460 align:start position:0% it's slightly different Boston but concept<00:22:46.090> where<00:22:46.269> you<00:22:46.419> always<00:22:46.659> come<00:22:47.049> to<00:22:47.080> please 00:22:47.460 --> 00:22:47.470 align:start position:0% concept where you always come to please 00:22:47.470 --> 00:22:51.060 align:start position:0% concept where you always come to please sighs<00:22:48.309> a<00:22:48.700> minute<00:22:49.029> sit<00:22:49.809> in 00:22:51.060 --> 00:22:51.070 align:start position:0% sighs a minute sit in 00:22:51.070 --> 00:22:57.090 align:start position:0% sighs a minute sit in or<00:22:51.580> a<00:22:51.640> Taser<00:22:54.780> in<00:22:55.780> a<00:22:55.870> numerical<00:22:56.110> Trina<00:22:56.740> Merkley 00:22:57.090 --> 00:22:57.100 align:start position:0% or a Taser in a numerical Trina Merkley 00:22:57.100 --> 00:22:58.920 align:start position:0% or a Taser in a numerical Trina Merkley tree<00:22:57.280> is<00:22:57.640> a<00:22:57.700> cryptographic<00:22:58.180> accumulator 00:22:58.920 --> 00:22:58.930 align:start position:0% tree is a cryptographic accumulator 00:22:58.930 --> 00:23:00.750 align:start position:0% tree is a cryptographic accumulator which<00:22:59.290> gives<00:22:59.560> you<00:22:59.740> a<00:23:00.040> constant<00:23:00.430> size 00:23:00.750 --> 00:23:00.760 align:start position:0% which gives you a constant size 00:23:00.760 --> 00:23:03.210 align:start position:0% which gives you a constant size commitment<00:23:01.360> to<00:23:01.480> vector<00:23:01.870> phase<00:23:02.200> and<00:23:02.920> from<00:23:03.130> this 00:23:03.210 --> 00:23:03.220 align:start position:0% commitment to vector phase and from this 00:23:03.220 --> 00:23:06.090 align:start position:0% commitment to vector phase and from this commitment<00:23:03.520> is<00:23:03.910> the<00:23:04.630> root<00:23:04.870> of<00:23:05.020> the<00:23:05.080> tree<00:23:05.320> which 00:23:06.090 --> 00:23:06.100 align:start position:0% commitment is the root of the tree which 00:23:06.100 --> 00:23:09.600 align:start position:0% commitment is the root of the tree which wraps<00:23:06.430> is<00:23:07.240> also<00:23:07.750> a<00:23:07.780> generic<00:23:08.110> accumulator<00:23:08.680> with 00:23:09.600 --> 00:23:09.610 align:start position:0% wraps is also a generic accumulator with 00:23:09.610 --> 00:23:13.400 align:start position:0% wraps is also a generic accumulator with v<00:23:09.940> with<00:23:10.450> a<00:23:10.600> with<00:23:10.900> a<00:23:11.020> with<00:23:11.410> a<00:23:11.470> commitment<00:23:12.040> size 00:23:13.400 --> 00:23:13.410 align:start position:0% v with a with a with a commitment size 00:23:13.410 --> 00:23:15.480 align:start position:0% v with a with a with a commitment size proportional<00:23:14.410> to<00:23:14.530> this<00:23:14.650> height<00:23:15.040> of<00:23:15.190> the<00:23:15.310> tree 00:23:15.480 --> 00:23:15.490 align:start position:0% proportional to this height of the tree 00:23:15.490 --> 00:23:19.950 align:start position:0% proportional to this height of the tree and<00:23:15.760> it's<00:23:16.390> determined<00:23:16.750> by<00:23:16.960> the<00:23:17.080> edge<00:23:17.380> of<00:23:17.410> a<00:23:18.960> of 00:23:19.950 --> 00:23:19.960 align:start position:0% and it's determined by the edge of a of 00:23:19.960 --> 00:23:23.190 align:start position:0% and it's determined by the edge of a of the<00:23:20.470> treatment<00:23:20.920> of<00:23:21.040> the<00:23:21.970> entire<00:23:22.300> edge<00:23:22.540> with 00:23:23.190 --> 00:23:23.200 align:start position:0% the treatment of the entire edge with 00:23:23.200 --> 00:23:25.890 align:start position:0% the treatment of the entire edge with which<00:23:23.470> you<00:23:24.010> have<00:23:24.040> the<00:23:24.310> root<00:23:24.520> the<00:23:25.360> next<00:23:25.720> and 00:23:25.890 --> 00:23:25.900 align:start position:0% which you have the root the next and 00:23:25.900 --> 00:23:30.300 align:start position:0% which you have the root the next and next<00:23:26.080> element<00:23:26.620> on<00:23:26.740> the<00:23:26.830> right<00:23:29.070> yes 00:23:30.300 --> 00:23:30.310 align:start position:0% next element on the right yes 00:23:30.310 --> 00:23:34.350 align:start position:0% next element on the right yes and<00:23:30.930> this<00:23:31.930> edge<00:23:32.320> is<00:23:32.740> your<00:23:32.920> commitment<00:23:33.190> and<00:23:34.150> you 00:23:34.350 --> 00:23:34.360 align:start position:0% and this edge is your commitment and you 00:23:34.360 --> 00:23:35.820 align:start position:0% and this edge is your commitment and you will<00:23:34.510> have<00:23:34.660> to<00:23:34.810> pass<00:23:34.960> this<00:23:35.170> commitment<00:23:35.530> so 00:23:35.820 --> 00:23:35.830 align:start position:0% will have to pass this commitment so 00:23:35.830 --> 00:23:38.790 align:start position:0% will have to pass this commitment so like<00:23:35.950> all<00:23:36.190> the<00:23:36.490> items<00:23:37.480> on<00:23:37.660> the<00:23:37.750> edge<00:23:37.900> to<00:23:38.680> the 00:23:38.790 --> 00:23:38.800 align:start position:0% like all the items on the edge to the 00:23:38.800 --> 00:23:41.580 align:start position:0% like all the items on the edge to the start<00:23:39.100> but<00:23:39.880> since<00:23:40.300> we<00:23:40.510> have<00:23:40.660> a<00:23:40.690> tree<00:23:40.960> of<00:23:41.170> fixed 00:23:41.580 --> 00:23:41.590 align:start position:0% start but since we have a tree of fixed 00:23:41.590 --> 00:23:44.430 align:start position:0% start but since we have a tree of fixed size<00:23:41.920> we<00:23:42.760> just<00:23:43.150> dig<00:23:43.330> the<00:23:43.570> size<00:23:43.810> of<00:23:43.930> like<00:23:44.080> do<00:23:44.260> to 00:23:44.430 --> 00:23:44.440 align:start position:0% size we just dig the size of like do to 00:23:44.440 --> 00:23:48.420 align:start position:0% size we just dig the size of like do to it<00:23:44.560> power<00:23:44.950> 32<00:23:46.140> this<00:23:47.140> size<00:23:47.440> commitment<00:23:48.100> will<00:23:48.280> be 00:23:48.420 --> 00:23:48.430 align:start position:0% it power 32 this size commitment will be 00:23:48.430 --> 00:23:50.880 align:start position:0% it power 32 this size commitment will be also<00:23:48.730> fixed<00:23:49.210> which<00:23:49.900> is<00:23:49.930> just<00:23:50.200> logarithm<00:23:50.710> of 00:23:50.880 --> 00:23:50.890 align:start position:0% also fixed which is just logarithm of 00:23:50.890 --> 00:23:53.130 align:start position:0% also fixed which is just logarithm of this<00:23:51.130> we<00:23:51.400> should<00:23:51.430> send<00:23:51.730> it<00:23:51.820> which<00:23:52.720> which<00:23:52.930> we 00:23:53.130 --> 00:23:53.140 align:start position:0% this we should send it which which we 00:23:53.140 --> 00:23:56.790 align:start position:0% this we should send it which which we can<00:23:53.320> we<00:23:53.590> can<00:23:53.890> pass<00:23:54.070> as<00:23:54.340> inputs<00:23:54.970> to<00:23:55.090> the<00:23:55.840> start 00:23:56.790 --> 00:23:56.800 align:start position:0% can we can pass as inputs to the start 00:23:56.800 --> 00:24:00.450 align:start position:0% can we can pass as inputs to the start or<00:23:57.010> we<00:23:57.430> can<00:23:57.730> also<00:23:57.850> optimize<00:23:58.120> to<00:23:58.690> just<00:23:59.460> compress 00:24:00.450 --> 00:24:00.460 align:start position:0% or we can also optimize to just compress 00:24:00.460 --> 00:24:04.200 align:start position:0% or we can also optimize to just compress on<00:24:00.610> a<00:24:00.640> name<00:24:00.820> in<00:24:01.030> a<00:24:01.090> hash<00:24:02.670> thanks<00:24:03.670> guys<00:24:03.880> I<00:24:04.030> think 00:24:04.200 --> 00:24:04.210 align:start position:0% on a name in a hash thanks guys I think 00:24:04.210 --> 00:24:09.980 align:start position:0% on a name in a hash thanks guys I think that's<00:24:04.360> time<00:24:04.600> but<00:24:04.930> the<00:24:05.200> outside 00:24:09.980 --> 00:24:09.990 align:start position:0% 00:24:09.990 --> 00:24:16.400 align:start position:0% [Applause] 00:24:16.400 --> 00:24:16.410 align:start position:0% 00:24:16.410 --> 00:24:18.470 align:start position:0% you