WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:13.749 align:start position:0% [Music] 00:00:13.749 --> 00:00:13.759 align:start position:0% 00:00:13.759 --> 00:00:16.670 align:start position:0% and<00:00:14.759> I'm<00:00:15.000> a<00:00:15.360> software<00:00:15.780> engineer<00:00:16.139> slash 00:00:16.670 --> 00:00:16.680 align:start position:0% and I'm a software engineer slash 00:00:16.680 --> 00:00:18.830 align:start position:0% and I'm a software engineer slash language<00:00:16.980> designer<00:00:17.580> here<00:00:18.119> at<00:00:18.300> Aztec<00:00:18.660> Network 00:00:18.830 --> 00:00:18.840 align:start position:0% language designer here at Aztec Network 00:00:18.840 --> 00:00:20.750 align:start position:0% language designer here at Aztec Network and<00:00:19.560> I'm<00:00:19.680> going<00:00:19.800> to<00:00:19.920> be<00:00:19.980> introducing<00:00:20.400> you<00:00:20.580> to 00:00:20.750 --> 00:00:20.760 align:start position:0% and I'm going to be introducing you to 00:00:20.760 --> 00:00:24.109 align:start position:0% and I'm going to be introducing you to Noir<00:00:21.300> today<00:00:21.500> Noir<00:00:22.500> is<00:00:22.859> our<00:00:23.119> rust-based 00:00:24.109 --> 00:00:24.119 align:start position:0% Noir today Noir is our rust-based 00:00:24.119 --> 00:00:26.150 align:start position:0% Noir today Noir is our rust-based domain-specific<00:00:25.019> language<00:00:25.320> for<00:00:25.800> writing 00:00:26.150 --> 00:00:26.160 align:start position:0% domain-specific language for writing 00:00:26.160 --> 00:00:28.250 align:start position:0% domain-specific language for writing zero<00:00:26.580> knowledge<00:00:26.820> circuits<00:00:27.300> I'm<00:00:28.019> going<00:00:28.140> to 00:00:28.250 --> 00:00:28.260 align:start position:0% zero knowledge circuits I'm going to 00:00:28.260 --> 00:00:30.410 align:start position:0% zero knowledge circuits I'm going to walk<00:00:28.380> you<00:00:28.500> through<00:00:28.740> a<00:00:29.039> basic<00:00:29.279> circuit<00:00:29.699> and 00:00:30.410 --> 00:00:30.420 align:start position:0% walk you through a basic circuit and 00:00:30.420 --> 00:00:31.669 align:start position:0% walk you through a basic circuit and then<00:00:30.539> also<00:00:30.900> show<00:00:31.019> you<00:00:31.140> how<00:00:31.380> to<00:00:31.439> go<00:00:31.560> about 00:00:31.669 --> 00:00:31.679 align:start position:0% then also show you how to go about 00:00:31.679 --> 00:00:34.130 align:start position:0% then also show you how to go about proving<00:00:32.279> and<00:00:32.880> verifying<00:00:33.480> that<00:00:33.660> circuit<00:00:34.020> in 00:00:34.130 --> 00:00:34.140 align:start position:0% proving and verifying that circuit in 00:00:34.140 --> 00:00:36.650 align:start position:0% proving and verifying that circuit in typescript<00:00:34.559> so<00:00:35.399> first<00:00:35.700> I<00:00:36.059> want<00:00:36.239> to<00:00:36.420> talk<00:00:36.480> about 00:00:36.650 --> 00:00:36.660 align:start position:0% typescript so first I want to talk about 00:00:36.660 --> 00:00:39.049 align:start position:0% typescript so first I want to talk about what<00:00:36.960> actually<00:00:37.140> makes<00:00:37.500> Noir<00:00:38.100> unique 00:00:39.049 --> 00:00:39.059 align:start position:0% what actually makes Noir unique 00:00:39.059 --> 00:00:41.569 align:start position:0% what actually makes Noir unique Noir<00:00:39.899> aims<00:00:40.379> to<00:00:40.440> be<00:00:40.559> more<00:00:40.739> flexible<00:00:41.100> in<00:00:41.340> its 00:00:41.569 --> 00:00:41.579 align:start position:0% Noir aims to be more flexible in its 00:00:41.579 --> 00:00:43.670 align:start position:0% Noir aims to be more flexible in its design<00:00:41.700> than<00:00:42.600> other<00:00:42.899> domain-specific 00:00:43.670 --> 00:00:43.680 align:start position:0% design than other domain-specific 00:00:43.680 --> 00:00:45.590 align:start position:0% design than other domain-specific languages<00:00:44.040> that<00:00:44.399> currently<00:00:44.700> exist<00:00:45.239> out<00:00:45.480> there 00:00:45.590 --> 00:00:45.600 align:start position:0% languages that currently exist out there 00:00:45.600 --> 00:00:48.170 align:start position:0% languages that currently exist out there and<00:00:46.200> we<00:00:46.379> do<00:00:46.500> this<00:00:46.680> by<00:00:47.100> rather<00:00:47.460> than<00:00:47.579> compiling 00:00:48.170 --> 00:00:48.180 align:start position:0% and we do this by rather than compiling 00:00:48.180 --> 00:00:50.810 align:start position:0% and we do this by rather than compiling to<00:00:48.840> a<00:00:49.140> specific<00:00:49.379> MP<00:00:49.739> complete<00:00:50.160> language<00:00:50.340> we're 00:00:50.810 --> 00:00:50.820 align:start position:0% to a specific MP complete language we're 00:00:50.820 --> 00:00:52.369 align:start position:0% to a specific MP complete language we're compiling<00:00:51.300> down<00:00:51.480> to<00:00:51.780> an<00:00:51.899> intermediate 00:00:52.369 --> 00:00:52.379 align:start position:0% compiling down to an intermediate 00:00:52.379 --> 00:00:55.189 align:start position:0% compiling down to an intermediate representation<00:00:53.160> we<00:00:54.120> call<00:00:54.300> this<00:00:54.539> intermediate 00:00:55.189 --> 00:00:55.199 align:start position:0% representation we call this intermediate 00:00:55.199 --> 00:00:57.049 align:start position:0% representation we call this intermediate representation<00:00:55.739> the<00:00:56.160> abstract<00:00:56.579> circuit 00:00:57.049 --> 00:00:57.059 align:start position:0% representation the abstract circuit 00:00:57.059 --> 00:00:59.450 align:start position:0% representation the abstract circuit intermediate<00:00:57.660> representation<00:00:58.140> or<00:00:58.860> the<00:00:58.980> Acer 00:00:59.450 --> 00:00:59.460 align:start position:0% intermediate representation or the Acer 00:00:59.460 --> 00:01:01.490 align:start position:0% intermediate representation or the Acer as<00:00:59.699> I'm<00:00:59.879> going<00:01:00.059> to<00:01:00.180> refer<00:01:00.539> to<00:01:00.660> it<00:01:00.840> throughout 00:01:01.490 --> 00:01:01.500 align:start position:0% as I'm going to refer to it throughout 00:01:01.500 --> 00:01:04.509 align:start position:0% as I'm going to refer to it throughout this<00:01:01.680> talk<00:01:01.920> this<00:01:02.760> IR<00:01:02.940> can<00:01:03.480> then<00:01:03.600> be 00:01:04.509 --> 00:01:04.519 align:start position:0% this talk this IR can then be 00:01:04.519 --> 00:01:06.950 align:start position:0% this talk this IR can then be compiled<00:01:05.519> down<00:01:05.640> to<00:01:05.939> a<00:01:06.119> rank<00:01:06.420> one<00:01:06.540> constraint 00:01:06.950 --> 00:01:06.960 align:start position:0% compiled down to a rank one constraint 00:01:06.960 --> 00:01:09.830 align:start position:0% compiled down to a rank one constraint system<00:01:07.200> or<00:01:08.159> plonkish<00:01:08.880> languages<00:01:09.180> whichever 00:01:09.830 --> 00:01:09.840 align:start position:0% system or plonkish languages whichever 00:01:09.840 --> 00:01:12.950 align:start position:0% system or plonkish languages whichever you<00:01:10.140> so<00:01:10.380> choose<00:01:10.820> this<00:01:11.820> is<00:01:11.939> analogous<00:01:12.479> to<00:01:12.780> the 00:01:12.950 --> 00:01:12.960 align:start position:0% you so choose this is analogous to the 00:01:12.960 --> 00:01:16.250 align:start position:0% you so choose this is analogous to the lovm<00:01:13.740> IR<00:01:14.159> but<00:01:15.119> rather<00:01:15.420> than<00:01:15.540> converting<00:01:16.020> down 00:01:16.250 --> 00:01:16.260 align:start position:0% lovm IR but rather than converting down 00:01:16.260 --> 00:01:18.649 align:start position:0% lovm IR but rather than converting down the<00:01:16.439> IR<00:01:16.619> to<00:01:17.220> a<00:01:17.520> specific<00:01:17.939> instruction<00:01:18.240> set 00:01:18.649 --> 00:01:18.659 align:start position:0% the IR to a specific instruction set 00:01:18.659 --> 00:01:21.170 align:start position:0% the IR to a specific instruction set architecture<00:01:19.260> we're<00:01:19.979> compiling<00:01:20.520> down<00:01:20.700> to<00:01:21.000> the 00:01:21.170 --> 00:01:21.180 align:start position:0% architecture we're compiling down to the 00:01:21.180 --> 00:01:23.510 align:start position:0% architecture we're compiling down to the constraint<00:01:21.479> system<00:01:21.780> of<00:01:22.200> a<00:01:22.320> given<00:01:22.619> ZK<00:01:23.220> proof 00:01:23.510 --> 00:01:23.520 align:start position:0% constraint system of a given ZK proof 00:01:23.520 --> 00:01:26.410 align:start position:0% constraint system of a given ZK proof construction<00:01:23.720> this<00:01:24.720> actually<00:01:24.900> enables<00:01:25.439> us<00:01:25.619> to 00:01:26.410 --> 00:01:26.420 align:start position:0% construction this actually enables us to 00:01:26.420 --> 00:01:29.330 align:start position:0% construction this actually enables us to essentially<00:01:27.420> decouple<00:01:28.020> the<00:01:28.560> back-end<00:01:28.920> proof 00:01:29.330 --> 00:01:29.340 align:start position:0% essentially decouple the back-end proof 00:01:29.340 --> 00:01:31.969 align:start position:0% essentially decouple the back-end proof system<00:01:29.520> and<00:01:30.299> the<00:01:30.540> language<00:01:30.720> we<00:01:31.619> currently 00:01:31.969 --> 00:01:31.979 align:start position:0% system and the language we currently 00:01:31.979 --> 00:01:34.550 align:start position:0% system and the language we currently have<00:01:32.100> one<00:01:32.400> fully<00:01:32.700> integrated<00:01:33.560> back-end 00:01:34.550 --> 00:01:34.560 align:start position:0% have one fully integrated back-end 00:01:34.560 --> 00:01:36.410 align:start position:0% have one fully integrated back-end system<00:01:34.799> and<00:01:35.100> that's<00:01:35.280> Aztecs<00:01:35.880> brettenberg 00:01:36.410 --> 00:01:36.420 align:start position:0% system and that's Aztecs brettenberg 00:01:36.420 --> 00:01:38.990 align:start position:0% system and that's Aztecs brettenberg library<00:01:36.799> and<00:01:37.799> we<00:01:38.040> also<00:01:38.280> have<00:01:38.460> plans<00:01:38.640> for 00:01:38.990 --> 00:01:39.000 align:start position:0% library and we also have plans for 00:01:39.000 --> 00:01:41.090 align:start position:0% library and we also have plans for Integrations<00:01:39.540> with<00:01:40.020> The<00:01:40.380> Arc<00:01:40.560> Works<00:01:40.799> proving 00:01:41.090 --> 00:01:41.100 align:start position:0% Integrations with The Arc Works proving 00:01:41.100 --> 00:01:43.670 align:start position:0% Integrations with The Arc Works proving systems<00:01:41.400> such<00:01:41.640> as<00:01:41.700> Marlin<00:01:42.060> and<00:01:42.240> growth<00:01:42.540> 16<00:01:42.780> but 00:01:43.670 --> 00:01:43.680 align:start position:0% systems such as Marlin and growth 16 but 00:01:43.680 --> 00:01:46.130 align:start position:0% systems such as Marlin and growth 16 but anyone<00:01:44.100> if<00:01:44.759> you<00:01:45.299> can<00:01:45.420> compile<00:01:45.720> it<00:01:45.900> down<00:01:46.020> to 00:01:46.130 --> 00:01:46.140 align:start position:0% anyone if you can compile it down to 00:01:46.140 --> 00:01:47.450 align:start position:0% anyone if you can compile it down to whatever<00:01:46.320> you'd<00:01:46.619> like 00:01:47.450 --> 00:01:47.460 align:start position:0% whatever you'd like 00:01:47.460 --> 00:01:49.910 align:start position:0% whatever you'd like this<00:01:48.180> to<00:01:48.479> our<00:01:48.659> knowledge<00:01:48.900> is<00:01:49.079> the<00:01:49.259> only<00:01:49.380> DSL 00:01:49.910 --> 00:01:49.920 align:start position:0% this to our knowledge is the only DSL 00:01:49.920 --> 00:01:51.530 align:start position:0% this to our knowledge is the only DSL that<00:01:50.220> currently<00:01:50.579> has<00:01:50.759> fully<00:01:51.180> integrated 00:01:51.530 --> 00:01:51.540 align:start position:0% that currently has fully integrated 00:01:51.540 --> 00:01:54.350 align:start position:0% that currently has fully integrated proving<00:01:52.020> system<00:01:52.340> optimizations<00:01:53.340> so<00:01:54.119> rather 00:01:54.350 --> 00:01:54.360 align:start position:0% proving system optimizations so rather 00:01:54.360 --> 00:01:56.630 align:start position:0% proving system optimizations so rather than<00:01:54.720> just<00:01:55.320> having<00:01:55.439> an<00:01:55.740> interface<00:01:56.159> for 00:01:56.630 --> 00:01:56.640 align:start position:0% than just having an interface for 00:01:56.640 --> 00:01:58.789 align:start position:0% than just having an interface for language<00:01:57.000> system<00:01:57.299> optimizations<00:01:58.020> we 00:01:58.789 --> 00:01:58.799 align:start position:0% language system optimizations we 00:01:58.799 --> 00:02:00.289 align:start position:0% language system optimizations we actually<00:01:58.920> have<00:01:59.220> it<00:01:59.340> on<00:01:59.460> the<00:01:59.579> proving<00:01:59.939> system 00:02:00.289 --> 00:02:00.299 align:start position:0% actually have it on the proving system 00:02:00.299 --> 00:02:02.990 align:start position:0% actually have it on the proving system as<00:02:00.780> well<00:02:00.899> but<00:02:01.860> like<00:02:02.220> where<00:02:02.579> do<00:02:02.700> we<00:02:02.820> actually 00:02:02.990 --> 00:02:03.000 align:start position:0% as well but like where do we actually 00:02:03.000 --> 00:02:04.490 align:start position:0% as well but like where do we actually get<00:02:03.420> from<00:02:03.659> this 00:02:04.490 --> 00:02:04.500 align:start position:0% get from this 00:02:04.500 --> 00:02:07.789 align:start position:0% get from this so<00:02:05.280> we<00:02:05.700> now<00:02:05.880> different<00:02:06.659> use<00:02:06.960> cases<00:02:07.320> require 00:02:07.789 --> 00:02:07.799 align:start position:0% so we now different use cases require 00:02:07.799 --> 00:02:11.390 align:start position:0% so we now different use cases require different<00:02:08.459> kinds<00:02:08.940> of<00:02:09.119> systems<00:02:10.020> and<00:02:10.920> now<00:02:11.160> we 00:02:11.390 --> 00:02:11.400 align:start position:0% different kinds of systems and now we 00:02:11.400 --> 00:02:13.309 align:start position:0% different kinds of systems and now we actually<00:02:11.580> have<00:02:12.060> a<00:02:12.360> language<00:02:12.540> that<00:02:12.900> separates 00:02:13.309 --> 00:02:13.319 align:start position:0% actually have a language that separates 00:02:13.319 --> 00:02:15.710 align:start position:0% actually have a language that separates the<00:02:13.980> middle<00:02:14.160> end<00:02:14.400> a<00:02:15.000> front<00:02:15.180> end<00:02:15.300> middle<00:02:15.480> end 00:02:15.710 --> 00:02:15.720 align:start position:0% the middle end a front end middle end 00:02:15.720 --> 00:02:17.390 align:start position:0% the middle end a front end middle end and<00:02:15.900> back<00:02:16.020> end<00:02:16.140> of<00:02:16.319> a<00:02:16.440> language<00:02:16.620> and 00:02:17.390 --> 00:02:17.400 align:start position:0% and back end of a language and 00:02:17.400 --> 00:02:19.190 align:start position:0% and back end of a language and developers<00:02:17.819> can<00:02:18.060> then<00:02:18.180> Converge<00:02:18.599> on<00:02:18.840> a<00:02:19.020> common 00:02:19.190 --> 00:02:19.200 align:start position:0% developers can then Converge on a common 00:02:19.200 --> 00:02:20.930 align:start position:0% developers can then Converge on a common architecture<00:02:19.920> standard 00:02:20.930 --> 00:02:20.940 align:start position:0% architecture standard 00:02:20.940 --> 00:02:23.390 align:start position:0% architecture standard the<00:02:21.540> fact<00:02:21.720> that<00:02:21.959> Noir<00:02:22.379> has<00:02:22.739> the<00:02:22.920> ability<00:02:23.099> to 00:02:23.390 --> 00:02:23.400 align:start position:0% the fact that Noir has the ability to 00:02:23.400 --> 00:02:24.970 align:start position:0% the fact that Noir has the ability to support<00:02:23.520> proving<00:02:24.000> system<00:02:24.120> optimizations 00:02:24.970 --> 00:02:24.980 align:start position:0% support proving system optimizations 00:02:24.980 --> 00:02:27.350 align:start position:0% support proving system optimizations enables<00:02:25.980> us<00:02:26.099> to<00:02:26.400> have<00:02:26.520> the<00:02:26.760> addition<00:02:27.000> of 00:02:27.350 --> 00:02:27.360 align:start position:0% enables us to have the addition of 00:02:27.360 --> 00:02:29.990 align:start position:0% enables us to have the addition of optimized<00:02:27.959> Black<00:02:28.080> Box<00:02:28.319> functions<00:02:28.860> a<00:02:29.520> few<00:02:29.640> that 00:02:29.990 --> 00:02:30.000 align:start position:0% optimized Black Box functions a few that 00:02:30.000 --> 00:02:33.050 align:start position:0% optimized Black Box functions a few that we<00:02:30.120> have<00:02:30.239> are<00:02:30.599> listed<00:02:31.080> right<00:02:31.260> there<00:02:31.500> but<00:02:32.340> if<00:02:32.700> a 00:02:33.050 --> 00:02:33.060 align:start position:0% we have are listed right there but if a 00:02:33.060 --> 00:02:35.930 align:start position:0% we have are listed right there but if a back-end<00:02:33.840> system<00:02:34.140> has<00:02:34.920> integrated<00:02:35.580> that 00:02:35.930 --> 00:02:35.940 align:start position:0% back-end system has integrated that 00:02:35.940 --> 00:02:37.790 align:start position:0% back-end system has integrated that specific<00:02:36.239> Black<00:02:36.480> Box<00:02:36.720> function<00:02:37.140> the<00:02:37.620> front 00:02:37.790 --> 00:02:37.800 align:start position:0% specific Black Box function the front 00:02:37.800 --> 00:02:40.309 align:start position:0% specific Black Box function the front end<00:02:37.920> can<00:02:38.220> then<00:02:38.400> access<00:02:38.640> it<00:02:39.060> the<00:02:39.720> ultimate<00:02:40.080> goal 00:02:40.309 --> 00:02:40.319 align:start position:0% end can then access it the ultimate goal 00:02:40.319 --> 00:02:42.350 align:start position:0% end can then access it the ultimate goal here<00:02:40.440> is<00:02:40.560> to<00:02:40.739> lower<00:02:40.920> the<00:02:41.160> barrier<00:02:41.519> to<00:02:41.940> Circuit 00:02:42.350 --> 00:02:42.360 align:start position:0% here is to lower the barrier to Circuit 00:02:42.360 --> 00:02:44.350 align:start position:0% here is to lower the barrier to Circuit development<00:02:42.780> by<00:02:43.560> incorporating 00:02:44.350 --> 00:02:44.360 align:start position:0% development by incorporating 00:02:44.360 --> 00:02:46.190 align:start position:0% development by incorporating cryptographic<00:02:45.360> safety<00:02:45.660> into<00:02:45.840> the<00:02:46.080> language 00:02:46.190 --> 00:02:46.200 align:start position:0% cryptographic safety into the language 00:02:46.200 --> 00:02:48.770 align:start position:0% cryptographic safety into the language itself<00:02:46.560> while<00:02:47.160> maintaining<00:02:47.819> performance<00:02:48.300> so 00:02:48.770 --> 00:02:48.780 align:start position:0% itself while maintaining performance so 00:02:48.780 --> 00:02:50.089 align:start position:0% itself while maintaining performance so I'm<00:02:48.900> mainly<00:02:49.140> going<00:02:49.260> to<00:02:49.379> be<00:02:49.440> talking<00:02:49.560> about<00:02:49.800> how 00:02:50.089 --> 00:02:50.099 align:start position:0% I'm mainly going to be talking about how 00:02:50.099 --> 00:02:52.190 align:start position:0% I'm mainly going to be talking about how to<00:02:50.160> prove<00:02:50.519> and<00:02:50.640> verify<00:02:51.000> in<00:02:51.120> typescript<00:02:51.540> this 00:02:52.190 --> 00:02:52.200 align:start position:0% to prove and verify in typescript this 00:02:52.200 --> 00:02:54.470 align:start position:0% to prove and verify in typescript this very<00:02:52.440> high<00:02:53.040> level<00:02:53.220> compilation<00:02:54.060> overview 00:02:54.470 --> 00:02:54.480 align:start position:0% very high level compilation overview 00:02:54.480 --> 00:02:57.229 align:start position:0% very high level compilation overview also<00:02:55.319> shows<00:02:55.680> our<00:02:56.099> package<00:02:56.459> manager<00:02:56.819> nargo 00:02:57.229 --> 00:02:57.239 align:start position:0% also shows our package manager nargo 00:02:57.239 --> 00:02:59.150 align:start position:0% also shows our package manager nargo that<00:02:57.840> I<00:02:58.019> specifically<00:02:58.500> want<00:02:58.620> to<00:02:58.800> note<00:02:58.860> that 00:02:59.150 --> 00:02:59.160 align:start position:0% that I specifically want to note that 00:02:59.160 --> 00:03:00.830 align:start position:0% that I specifically want to note that allows<00:02:59.459> for<00:02:59.700> approving<00:03:00.180> and<00:03:00.300> verifying 00:03:00.830 --> 00:03:00.840 align:start position:0% allows for approving and verifying 00:03:00.840 --> 00:03:03.470 align:start position:0% allows for approving and verifying circuits<00:03:01.319> this<00:03:01.920> is<00:03:02.040> very<00:03:02.220> similar<00:03:02.580> to<00:03:03.000> Cargo 00:03:03.470 --> 00:03:03.480 align:start position:0% circuits this is very similar to Cargo 00:03:03.480 --> 00:03:05.570 align:start position:0% circuits this is very similar to Cargo so<00:03:03.840> you<00:03:04.019> can<00:03:04.140> build<00:03:04.260> your<00:03:04.500> circuits<00:03:04.980> using 00:03:05.570 --> 00:03:05.580 align:start position:0% so you can build your circuits using 00:03:05.580 --> 00:03:08.509 align:start position:0% so you can build your circuits using this<00:03:05.760> but<00:03:06.540> because<00:03:06.959> to<00:03:07.680> actually<00:03:07.800> prove<00:03:08.280> you 00:03:08.509 --> 00:03:08.519 align:start position:0% this but because to actually prove you 00:03:08.519 --> 00:03:10.490 align:start position:0% this but because to actually prove you have<00:03:08.640> to<00:03:08.760> require<00:03:09.060> requires<00:03:10.019> a<00:03:10.140> proof<00:03:10.379> system 00:03:10.490 --> 00:03:10.500 align:start position:0% have to require requires a proof system 00:03:10.500 --> 00:03:12.770 align:start position:0% have to require requires a proof system you<00:03:10.800> see<00:03:10.920> that<00:03:11.099> line<00:03:11.280> on<00:03:11.580> the<00:03:11.700> top<00:03:11.879> going<00:03:12.599> all 00:03:12.770 --> 00:03:12.780 align:start position:0% you see that line on the top going all 00:03:12.780 --> 00:03:14.270 align:start position:0% you see that line on the top going all the<00:03:12.900> way<00:03:12.959> over<00:03:13.140> to<00:03:13.379> the<00:03:13.500> proof<00:03:13.739> system<00:03:13.920> as<00:03:14.159> well 00:03:14.270 --> 00:03:14.280 align:start position:0% the way over to the proof system as well 00:03:14.280 --> 00:03:16.490 align:start position:0% the way over to the proof system as well in<00:03:14.580> order<00:03:14.700> to<00:03:14.879> compile<00:03:15.120> nargo<00:03:15.599> you<00:03:16.080> need<00:03:16.260> all 00:03:16.490 --> 00:03:16.500 align:start position:0% in order to compile nargo you need all 00:03:16.500 --> 00:03:18.649 align:start position:0% in order to compile nargo you need all integrated<00:03:16.980> so<00:03:17.700> now<00:03:17.819> I'm<00:03:18.000> actually<00:03:18.239> going<00:03:18.540> to 00:03:18.649 --> 00:03:18.659 align:start position:0% integrated so now I'm actually going to 00:03:18.659 --> 00:03:20.030 align:start position:0% integrated so now I'm actually going to take<00:03:18.840> you<00:03:18.959> through<00:03:19.140> what<00:03:19.319> a<00:03:19.440> Noir<00:03:19.680> circuit 00:03:20.030 --> 00:03:20.040 align:start position:0% take you through what a Noir circuit 00:03:20.040 --> 00:03:21.830 align:start position:0% take you through what a Noir circuit looks<00:03:20.280> like<00:03:20.340> and<00:03:20.879> and<00:03:21.180> I'm<00:03:21.420> going<00:03:21.540> to<00:03:21.540> use<00:03:21.659> one 00:03:21.830 --> 00:03:21.840 align:start position:0% looks like and and I'm going to use one 00:03:21.840 --> 00:03:23.630 align:start position:0% looks like and and I'm going to use one of<00:03:21.959> the<00:03:22.019> most<00:03:22.140> common<00:03:22.260> examples<00:03:22.739> where<00:03:23.159> ZK 00:03:23.630 --> 00:03:23.640 align:start position:0% of the most common examples where ZK 00:03:23.640 --> 00:03:25.550 align:start position:0% of the most common examples where ZK proofs<00:03:24.060> are<00:03:24.300> used<00:03:24.480> to<00:03:24.720> enable<00:03:25.019> private 00:03:25.550 --> 00:03:25.560 align:start position:0% proofs are used to enable private 00:03:25.560 --> 00:03:27.589 align:start position:0% proofs are used to enable private transfers<00:03:25.920> and<00:03:26.580> rather<00:03:26.819> than<00:03:27.120> you<00:03:27.540> know 00:03:27.589 --> 00:03:27.599 align:start position:0% transfers and rather than you know 00:03:27.599 --> 00:03:29.990 align:start position:0% transfers and rather than you know simply<00:03:28.080> showing<00:03:28.980> you<00:03:29.099> the<00:03:29.280> entire<00:03:29.519> circuit<00:03:29.879> at 00:03:29.990 --> 00:03:30.000 align:start position:0% simply showing you the entire circuit at 00:03:30.000 --> 00:03:31.790 align:start position:0% simply showing you the entire circuit at once<00:03:30.239> I'm<00:03:30.540> going<00:03:30.720> to<00:03:30.840> walk<00:03:30.959> through<00:03:31.200> kind<00:03:31.680> of 00:03:31.790 --> 00:03:31.800 align:start position:0% once I'm going to walk through kind of 00:03:31.800 --> 00:03:33.649 align:start position:0% once I'm going to walk through kind of each<00:03:31.980> part<00:03:32.159> of<00:03:32.280> the<00:03:32.400> circuit<00:03:32.760> and<00:03:33.239> this<00:03:33.420> is<00:03:33.540> to 00:03:33.649 --> 00:03:33.659 align:start position:0% each part of the circuit and this is to 00:03:33.659 --> 00:03:36.470 align:start position:0% each part of the circuit and this is to highlight<00:03:33.959> noir's<00:03:34.860> unique<00:03:35.099> features<00:03:35.459> for<00:03:36.180> and 00:03:36.470 --> 00:03:36.480 align:start position:0% highlight noir's unique features for and 00:03:36.480 --> 00:03:38.030 align:start position:0% highlight noir's unique features for and also<00:03:36.780> for<00:03:36.959> those<00:03:37.140> who<00:03:37.260> may<00:03:37.379> be<00:03:37.500> unfamiliar 00:03:38.030 --> 00:03:38.040 align:start position:0% also for those who may be unfamiliar 00:03:38.040 --> 00:03:39.649 align:start position:0% also for those who may be unfamiliar with<00:03:38.159> how<00:03:38.340> to<00:03:38.459> write<00:03:38.640> a<00:03:38.879> private<00:03:39.120> transfer 00:03:39.649 --> 00:03:39.659 align:start position:0% with how to write a private transfer 00:03:39.659 --> 00:03:42.170 align:start position:0% with how to write a private transfer circuit<00:03:40.019> how<00:03:40.440> that<00:03:40.620> may<00:03:40.739> be<00:03:40.860> done<00:03:41.060> if<00:03:42.060> you're 00:03:42.170 --> 00:03:42.180 align:start position:0% circuit how that may be done if you're 00:03:42.180 --> 00:03:43.610 align:start position:0% circuit how that may be done if you're already<00:03:42.360> kind<00:03:42.659> of<00:03:42.780> familiar<00:03:43.080> with<00:03:43.200> it<00:03:43.319> you<00:03:43.500> may 00:03:43.610 --> 00:03:43.620 align:start position:0% already kind of familiar with it you may 00:03:43.620 --> 00:03:46.190 align:start position:0% already kind of familiar with it you may have<00:03:43.680> to<00:03:43.799> Do's<00:03:44.099> from<00:03:44.220> the<00:03:44.340> inputs<00:03:44.760> that<00:03:45.659> the 00:03:46.190 --> 00:03:46.200 align:start position:0% have to Do's from the inputs that the 00:03:46.200 --> 00:03:47.750 align:start position:0% have to Do's from the inputs that the circuit<00:03:46.560> essentially<00:03:46.920> boils<00:03:47.340> down<00:03:47.459> to<00:03:47.580> a 00:03:47.750 --> 00:03:47.760 align:start position:0% circuit essentially boils down to a 00:03:47.760 --> 00:03:50.330 align:start position:0% circuit essentially boils down to a Merkel<00:03:48.060> membership<00:03:48.360> proof<00:03:49.260> similar<00:03:49.920> to<00:03:50.040> how 00:03:50.330 --> 00:03:50.340 align:start position:0% Merkel membership proof similar to how 00:03:50.340 --> 00:03:52.309 align:start position:0% Merkel membership proof similar to how noir's<00:03:50.940> rust<00:03:51.120> based<00:03:51.480> the<00:03:51.659> syntax<00:03:52.019> is 00:03:52.309 --> 00:03:52.319 align:start position:0% noir's rust based the syntax is 00:03:52.319 --> 00:03:55.009 align:start position:0% noir's rust based the syntax is rust-like<00:03:53.040> as<00:03:53.220> well<00:03:53.879> but<00:03:54.420> the<00:03:54.599> main<00:03:54.720> thing<00:03:54.840> to 00:03:55.009 --> 00:03:55.019 align:start position:0% rust-like as well but the main thing to 00:03:55.019 --> 00:03:56.449 align:start position:0% rust-like as well but the main thing to note<00:03:55.140> here<00:03:55.379> is<00:03:55.560> the<00:03:55.739> usage<00:03:55.980> of<00:03:56.159> the<00:03:56.340> pub 00:03:56.449 --> 00:03:56.459 align:start position:0% note here is the usage of the pub 00:03:56.459 --> 00:03:58.850 align:start position:0% note here is the usage of the pub keyword<00:03:57.060> all<00:03:57.599> inputs<00:03:58.019> to<00:03:58.140> the<00:03:58.260> Noir<00:03:58.500> circuit 00:03:58.850 --> 00:03:58.860 align:start position:0% keyword all inputs to the Noir circuit 00:03:58.860 --> 00:04:00.830 align:start position:0% keyword all inputs to the Noir circuit are<00:03:58.980> going<00:03:59.099> to<00:03:59.159> be<00:03:59.220> private<00:03:59.580> by<00:03:59.760> default<00:04:00.060> and 00:04:00.830 --> 00:04:00.840 align:start position:0% are going to be private by default and 00:04:00.840 --> 00:04:02.990 align:start position:0% are going to be private by default and that<00:04:01.080> keyword<00:04:01.319> allows<00:04:01.739> you<00:04:01.799> to<00:04:01.980> then<00:04:02.099> say<00:04:02.459> this 00:04:02.990 --> 00:04:03.000 align:start position:0% that keyword allows you to then say this 00:04:03.000 --> 00:04:04.670 align:start position:0% that keyword allows you to then say this also<00:04:03.239> has<00:04:03.360> to<00:04:03.540> be<00:04:03.599> supplied<00:04:03.959> to<00:04:04.140> the<00:04:04.260> verifier 00:04:04.670 --> 00:04:04.680 align:start position:0% also has to be supplied to the verifier 00:04:04.680 --> 00:04:06.949 align:start position:0% also has to be supplied to the verifier as<00:04:04.920> well<00:04:05.099> currently<00:04:06.000> anything<00:04:06.360> outputted 00:04:06.949 --> 00:04:06.959 align:start position:0% as well currently anything outputted 00:04:06.959 --> 00:04:08.869 align:start position:0% as well currently anything outputted from<00:04:07.140> the<00:04:07.319> function<00:04:07.560> must<00:04:07.980> also<00:04:08.519> be<00:04:08.640> public 00:04:08.869 --> 00:04:08.879 align:start position:0% from the function must also be public 00:04:08.879 --> 00:04:11.630 align:start position:0% from the function must also be public and<00:04:09.659> to<00:04:09.840> take<00:04:10.260> note<00:04:10.439> of<00:04:10.739> our<00:04:10.920> native<00:04:11.159> data<00:04:11.580> type 00:04:11.630 --> 00:04:11.640 align:start position:0% and to take note of our native data type 00:04:11.640 --> 00:04:14.630 align:start position:0% and to take note of our native data type that's<00:04:12.000> called<00:04:12.239> the<00:04:12.480> field<00:04:13.099> this<00:04:14.099> is<00:04:14.220> in<00:04:14.519> the 00:04:14.630 --> 00:04:14.640 align:start position:0% that's called the field this is in the 00:04:14.640 --> 00:04:16.430 align:start position:0% that's called the field this is in the Aztec<00:04:15.000> brettenberg<00:04:15.420> back<00:04:15.659> end<00:04:15.780> a<00:04:15.959> field<00:04:16.139> on 00:04:16.430 --> 00:04:16.440 align:start position:0% Aztec brettenberg back end a field on 00:04:16.440 --> 00:04:19.250 align:start position:0% Aztec brettenberg back end a field on the<00:04:16.560> BN<00:04:16.919> 254<00:04:17.579> curve<00:04:18.000> but<00:04:18.660> we<00:04:18.840> also<00:04:19.079> support 00:04:19.250 --> 00:04:19.260 align:start position:0% the BN 254 curve but we also support 00:04:19.260 --> 00:04:22.370 align:start position:0% the BN 254 curve but we also support smaller<00:04:19.739> data<00:04:19.979> types<00:04:20.220> such<00:04:20.459> as<00:04:20.639> u32<00:04:21.540> u8<00:04:22.079> you 00:04:22.370 --> 00:04:22.380 align:start position:0% smaller data types such as u32 u8 you 00:04:22.380 --> 00:04:24.950 align:start position:0% smaller data types such as u32 u8 you can<00:04:22.500> even<00:04:22.620> have<00:04:22.800> u3<00:04:23.280> but<00:04:24.180> these<00:04:24.540> are<00:04:24.660> less 00:04:24.950 --> 00:04:24.960 align:start position:0% can even have u3 but these are less 00:04:24.960 --> 00:04:26.870 align:start position:0% can even have u3 but these are less efficient<00:04:25.380> as<00:04:26.040> they<00:04:26.220> require<00:04:26.400> range 00:04:26.870 --> 00:04:26.880 align:start position:0% efficient as they require range 00:04:26.880 --> 00:04:29.629 align:start position:0% efficient as they require range constraints<00:04:27.300> and<00:04:28.199> but<00:04:28.800> that's<00:04:29.160> all<00:04:29.340> to<00:04:29.520> the 00:04:29.629 --> 00:04:29.639 align:start position:0% constraints and but that's all to the 00:04:29.639 --> 00:04:31.310 align:start position:0% constraints and but that's all to the needs<00:04:29.820> of<00:04:29.880> the<00:04:30.000> circuit<00:04:30.240> developer<00:04:30.660> if<00:04:31.199> you 00:04:31.310 --> 00:04:31.320 align:start position:0% needs of the circuit developer if you 00:04:31.320 --> 00:04:33.469 align:start position:0% needs of the circuit developer if you want<00:04:31.500> to<00:04:31.680> constrain<00:04:32.160> using<00:04:32.759> our<00:04:32.880> data<00:04:33.180> types 00:04:33.469 --> 00:04:33.479 align:start position:0% want to constrain using our data types 00:04:33.479 --> 00:04:34.909 align:start position:0% want to constrain using our data types rather<00:04:33.840> than<00:04:33.960> directly<00:04:34.380> in<00:04:34.500> the<00:04:34.620> circuit 00:04:34.909 --> 00:04:34.919 align:start position:0% rather than directly in the circuit 00:04:34.919 --> 00:04:36.650 align:start position:0% rather than directly in the circuit yourself<00:04:35.220> now<00:04:35.759> we<00:04:35.880> can<00:04:36.000> actually<00:04:36.180> get<00:04:36.479> into 00:04:36.650 --> 00:04:36.660 align:start position:0% yourself now we can actually get into 00:04:36.660 --> 00:04:38.450 align:start position:0% yourself now we can actually get into the<00:04:36.960> logic<00:04:37.380> of<00:04:37.500> the<00:04:37.620> circuit<00:04:37.919> and<00:04:38.220> we're<00:04:38.340> going 00:04:38.450 --> 00:04:38.460 align:start position:0% the logic of the circuit and we're going 00:04:38.460 --> 00:04:39.710 align:start position:0% the logic of the circuit and we're going to<00:04:38.520> start<00:04:38.639> off<00:04:38.759> by<00:04:38.940> using<00:04:39.240> two<00:04:39.419> of<00:04:39.540> our 00:04:39.710 --> 00:04:39.720 align:start position:0% to start off by using two of our 00:04:39.720 --> 00:04:41.990 align:start position:0% to start off by using two of our standard<00:04:40.020> Library<00:04:40.259> functions<00:04:40.860> the<00:04:41.580> schnor 00:04:41.990 --> 00:04:42.000 align:start position:0% standard Library functions the schnor 00:04:42.000 --> 00:04:43.670 align:start position:0% standard Library functions the schnor fixed<00:04:42.360> base<00:04:42.540> scalar<00:04:42.900> multiplication<00:04:43.320> method 00:04:43.670 --> 00:04:43.680 align:start position:0% fixed base scalar multiplication method 00:04:43.680 --> 00:04:46.249 align:start position:0% fixed base scalar multiplication method so<00:04:43.919> we<00:04:44.100> can<00:04:44.280> construct<00:04:44.759> a<00:04:45.000> private<00:04:45.360> public<00:04:45.900> key 00:04:46.249 --> 00:04:46.259 align:start position:0% so we can construct a private public key 00:04:46.259 --> 00:04:47.870 align:start position:0% so we can construct a private public key from<00:04:46.740> the<00:04:46.860> private<00:04:47.160> key<00:04:47.220> that<00:04:47.460> was<00:04:47.580> supplied 00:04:47.870 --> 00:04:47.880 align:start position:0% from the private key that was supplied 00:04:47.880 --> 00:04:50.390 align:start position:0% from the private key that was supplied to<00:04:48.060> the<00:04:48.180> circuit<00:04:48.540> and<00:04:49.139> then<00:04:49.320> also<00:04:49.740> a<00:04:50.040> Pederson 00:04:50.390 --> 00:04:50.400 align:start position:0% to the circuit and then also a Pederson 00:04:50.400 --> 00:04:52.070 align:start position:0% to the circuit and then also a Pederson hash<00:04:50.759> function<00:04:51.060> which<00:04:51.540> is<00:04:51.660> going<00:04:51.780> to<00:04:51.840> take<00:04:51.960> in 00:04:52.070 --> 00:04:52.080 align:start position:0% hash function which is going to take in 00:04:52.080 --> 00:04:54.170 align:start position:0% hash function which is going to take in a<00:04:52.259> list<00:04:52.380> of<00:04:52.500> field<00:04:52.680> elements<00:04:53.160> and<00:04:53.520> return<00:04:53.820> turn 00:04:54.170 --> 00:04:54.180 align:start position:0% a list of field elements and return turn 00:04:54.180 --> 00:04:57.830 align:start position:0% a list of field elements and return turn a<00:04:54.419> point<00:04:54.600> on<00:04:55.080> the<00:04:55.199> bn254<00:04:56.100> Curve<00:04:56.940> we<00:04:57.419> first<00:04:57.600> you 00:04:57.830 --> 00:04:57.840 align:start position:0% a point on the bn254 Curve we first you 00:04:57.840 --> 00:04:59.930 align:start position:0% a point on the bn254 Curve we first you we<00:04:58.080> use<00:04:58.320> the<00:04:58.500> random<00:04:58.860> input<00:04:59.100> secret<00:04:59.400> that<00:04:59.820> was 00:04:59.930 --> 00:04:59.940 align:start position:0% we use the random input secret that was 00:04:59.940 --> 00:05:01.909 align:start position:0% we use the random input secret that was shown<00:05:00.120> in<00:05:00.360> the<00:05:00.540> previous<00:05:00.660> slide<00:05:01.139> to<00:05:01.680> keep<00:05:01.740> our 00:05:01.909 --> 00:05:01.919 align:start position:0% shown in the previous slide to keep our 00:05:01.919 --> 00:05:04.010 align:start position:0% shown in the previous slide to keep our note<00:05:02.100> commitment<00:05:02.520> private<00:05:03.479> and<00:05:03.780> not 00:05:04.010 --> 00:05:04.020 align:start position:0% note commitment private and not 00:05:04.020 --> 00:05:06.230 align:start position:0% note commitment private and not associated<00:05:04.500> with<00:05:04.979> any<00:05:05.220> one<00:05:05.460> account 00:05:06.230 --> 00:05:06.240 align:start position:0% associated with any one account 00:05:06.240 --> 00:05:08.390 align:start position:0% associated with any one account once<00:05:06.780> again<00:05:06.840> this<00:05:07.259> is<00:05:07.440> using<00:05:07.860> the<00:05:08.040> Aztec 00:05:08.390 --> 00:05:08.400 align:start position:0% once again this is using the Aztec 00:05:08.400 --> 00:05:10.129 align:start position:0% once again this is using the Aztec brettenberg<00:05:08.759> back<00:05:09.000> end<00:05:09.120> but<00:05:09.419> if<00:05:09.660> a<00:05:09.840> back<00:05:09.960> end 00:05:10.129 --> 00:05:10.139 align:start position:0% brettenberg back end but if a back end 00:05:10.139 --> 00:05:12.590 align:start position:0% brettenberg back end but if a back end supports<00:05:11.040> these<00:05:11.520> functions<00:05:11.820> then<00:05:12.240> the<00:05:12.479> front 00:05:12.590 --> 00:05:12.600 align:start position:0% supports these functions then the front 00:05:12.600 --> 00:05:14.510 align:start position:0% supports these functions then the front end<00:05:12.780> can<00:05:13.080> access<00:05:13.259> it<00:05:13.620> and<00:05:14.100> now<00:05:14.220> we<00:05:14.400> actually 00:05:14.510 --> 00:05:14.520 align:start position:0% end can access it and now we actually 00:05:14.520 --> 00:05:16.790 align:start position:0% end can access it and now we actually have<00:05:14.820> the<00:05:15.120> the<00:05:15.300> meat<00:05:15.600> of<00:05:15.720> the<00:05:15.840> circuit<00:05:16.139> where 00:05:16.790 --> 00:05:16.800 align:start position:0% have the the meat of the circuit where 00:05:16.800 --> 00:05:18.170 align:start position:0% have the the meat of the circuit where we're<00:05:17.040> first<00:05:17.220> going<00:05:17.400> to<00:05:17.520> generate<00:05:17.940> a 00:05:18.170 --> 00:05:18.180 align:start position:0% we're first going to generate a 00:05:18.180 --> 00:05:20.450 align:start position:0% we're first going to generate a nullifier<00:05:18.660> and<00:05:19.320> this<00:05:19.500> nullifier<00:05:19.979> has<00:05:20.220> to<00:05:20.340> be 00:05:20.450 --> 00:05:20.460 align:start position:0% nullifier and this nullifier has to be 00:05:20.460 --> 00:05:22.010 align:start position:0% nullifier and this nullifier has to be unique<00:05:20.759> and<00:05:21.180> this<00:05:21.360> is<00:05:21.479> used<00:05:21.600> to<00:05:21.780> prevent 00:05:22.010 --> 00:05:22.020 align:start position:0% unique and this is used to prevent 00:05:22.020 --> 00:05:24.110 align:start position:0% unique and this is used to prevent double<00:05:22.259> spends<00:05:22.860> and<00:05:23.280> the<00:05:23.460> circuit<00:05:23.759> the 00:05:24.110 --> 00:05:24.120 align:start position:0% double spends and the circuit the 00:05:24.120 --> 00:05:25.909 align:start position:0% double spends and the circuit the contract<00:05:24.600> that<00:05:24.840> integrates<00:05:25.259> the<00:05:25.440> circuit<00:05:25.800> is 00:05:25.909 --> 00:05:25.919 align:start position:0% contract that integrates the circuit is 00:05:25.919 --> 00:05:28.310 align:start position:0% contract that integrates the circuit is going<00:05:26.100> to<00:05:26.220> have<00:05:26.340> to<00:05:26.580> make<00:05:27.539> sure<00:05:27.660> make<00:05:27.960> sure<00:05:28.139> of 00:05:28.310 --> 00:05:28.320 align:start position:0% going to have to make sure make sure of 00:05:28.320 --> 00:05:31.249 align:start position:0% going to have to make sure make sure of that<00:05:28.860> where<00:05:29.759> we<00:05:30.120> provide<00:05:30.479> the<00:05:30.720> no<00:05:30.900> commitment 00:05:31.249 --> 00:05:31.259 align:start position:0% that where we provide the no commitment 00:05:31.259 --> 00:05:32.689 align:start position:0% that where we provide the no commitment that<00:05:31.440> we<00:05:31.620> just<00:05:31.740> calculated<00:05:32.160> in<00:05:32.400> the<00:05:32.580> previous 00:05:32.689 --> 00:05:32.699 align:start position:0% that we just calculated in the previous 00:05:32.699 --> 00:05:35.510 align:start position:0% that we just calculated in the previous in<00:05:33.479> the<00:05:33.600> previous<00:05:33.720> Slide<00:05:34.139> the<00:05:34.740> index<00:05:35.100> of<00:05:35.400> the 00:05:35.510 --> 00:05:35.520 align:start position:0% in the previous Slide the index of the 00:05:35.520 --> 00:05:37.370 align:start position:0% in the previous Slide the index of the snow<00:05:35.639> commitment<00:05:36.000> in<00:05:36.240> the<00:05:36.300> Merkle<00:05:36.600> tree<00:05:36.780> and 00:05:37.370 --> 00:05:37.380 align:start position:0% snow commitment in the Merkle tree and 00:05:37.380 --> 00:05:39.590 align:start position:0% snow commitment in the Merkle tree and then<00:05:37.620> the<00:05:38.160> private<00:05:38.460> key<00:05:38.639> to<00:05:39.000> act<00:05:39.120> as<00:05:39.360> that 00:05:39.590 --> 00:05:39.600 align:start position:0% then the private key to act as that 00:05:39.600 --> 00:05:41.390 align:start position:0% then the private key to act as that identity<00:05:40.020> differentiator 00:05:41.390 --> 00:05:41.400 align:start position:0% identity differentiator 00:05:41.400 --> 00:05:42.890 align:start position:0% identity differentiator and<00:05:41.759> then<00:05:41.880> finally<00:05:42.120> we<00:05:42.479> have<00:05:42.539> a<00:05:42.720> check 00:05:42.890 --> 00:05:42.900 align:start position:0% and then finally we have a check 00:05:42.900 --> 00:05:44.390 align:start position:0% and then finally we have a check membership<00:05:43.320> function<00:05:43.680> that's<00:05:43.979> going<00:05:44.160> to<00:05:44.280> take 00:05:44.390 --> 00:05:44.400 align:start position:0% membership function that's going to take 00:05:44.400 --> 00:05:47.390 align:start position:0% membership function that's going to take in<00:05:44.639> the<00:05:45.180> hash<00:05:45.419> path<00:05:45.660> the<00:05:46.139> index<00:05:46.620> that<00:05:47.160> note 00:05:47.390 --> 00:05:47.400 align:start position:0% in the hash path the index that note 00:05:47.400 --> 00:05:49.730 align:start position:0% in the hash path the index that note commitment<00:05:47.820> and<00:05:48.300> a<00:05:48.419> note<00:05:48.600> root<00:05:48.960> it's<00:05:49.380> going<00:05:49.620> to 00:05:49.730 --> 00:05:49.740 align:start position:0% commitment and a note root it's going to 00:05:49.740 --> 00:05:51.710 align:start position:0% commitment and a note root it's going to calculate<00:05:50.039> a<00:05:50.220> note<00:05:50.340> root<00:05:50.759> using<00:05:51.240> the<00:05:51.539> hash 00:05:51.710 --> 00:05:51.720 align:start position:0% calculate a note root using the hash 00:05:51.720 --> 00:05:53.689 align:start position:0% calculate a note root using the hash path<00:05:51.960> and<00:05:52.139> commitment<00:05:52.440> provided<00:05:52.979> and<00:05:53.400> if<00:05:53.520> it 00:05:53.689 --> 00:05:53.699 align:start position:0% path and commitment provided and if it 00:05:53.699 --> 00:05:57.050 align:start position:0% path and commitment provided and if it matches<00:05:54.120> the<00:05:55.080> the<00:05:55.740> note<00:05:55.979> route<00:05:56.220> there<00:05:56.460> that<00:05:56.880> we 00:05:57.050 --> 00:05:57.060 align:start position:0% matches the the note route there that we 00:05:57.060 --> 00:05:58.249 align:start position:0% matches the the note route there that we provided<00:05:57.360> from<00:05:57.539> the<00:05:57.660> circuit<00:05:57.960> which<00:05:58.139> is 00:05:58.249 --> 00:05:58.259 align:start position:0% provided from the circuit which is 00:05:58.259 --> 00:06:01.370 align:start position:0% provided from the circuit which is public<00:05:58.500> we<00:05:59.160> then<00:05:59.340> know<00:05:59.639> okay<00:06:00.240> that<00:06:00.660> this<00:06:00.960> that 00:06:01.370 --> 00:06:01.380 align:start position:0% public we then know okay that this that 00:06:01.380 --> 00:06:03.290 align:start position:0% public we then know okay that this that those<00:06:01.860> no<00:06:02.280> commitment<00:06:02.580> that<00:06:02.759> was<00:06:02.940> calculated 00:06:03.290 --> 00:06:03.300 align:start position:0% those no commitment that was calculated 00:06:03.300 --> 00:06:06.409 align:start position:0% those no commitment that was calculated within<00:06:03.720> the<00:06:03.900> circuit<00:06:04.259> is<00:06:05.039> actually 00:06:06.409 --> 00:06:06.419 align:start position:0% within the circuit is actually 00:06:06.419 --> 00:06:09.890 align:start position:0% within the circuit is actually the<00:06:07.020> the<00:06:07.259> person<00:06:07.860> proving<00:06:08.580> it<00:06:08.820> does<00:06:09.479> possess 00:06:09.890 --> 00:06:09.900 align:start position:0% the the person proving it does possess 00:06:09.900 --> 00:06:12.890 align:start position:0% the the person proving it does possess that<00:06:10.199> no<00:06:10.320> commitment<00:06:10.880> and<00:06:11.880> finally<00:06:12.300> we<00:06:12.660> return 00:06:12.890 --> 00:06:12.900 align:start position:0% that no commitment and finally we return 00:06:12.900 --> 00:06:15.950 align:start position:0% that no commitment and finally we return our<00:06:13.259> nullifier<00:06:13.800> and<00:06:14.039> our<00:06:14.220> recipient<00:06:15.060> this<00:06:15.720> uh 00:06:15.950 --> 00:06:15.960 align:start position:0% our nullifier and our recipient this uh 00:06:15.960 --> 00:06:17.810 align:start position:0% our nullifier and our recipient this uh is<00:06:16.380> actually<00:06:16.560> constraining<00:06:17.460> these<00:06:17.699> two 00:06:17.810 --> 00:06:17.820 align:start position:0% is actually constraining these two 00:06:17.820 --> 00:06:19.670 align:start position:0% is actually constraining these two values<00:06:18.120> with<00:06:18.360> the<00:06:18.479> outputs<00:06:18.900> it's<00:06:19.440> a<00:06:19.620> little 00:06:19.670 --> 00:06:19.680 align:start position:0% values with the outputs it's a little 00:06:19.680 --> 00:06:21.529 align:start position:0% values with the outputs it's a little syntactic<00:06:20.400> sugar<00:06:20.520> that<00:06:20.940> we<00:06:21.060> have<00:06:21.180> for<00:06:21.360> our 00:06:21.529 --> 00:06:21.539 align:start position:0% syntactic sugar that we have for our 00:06:21.539 --> 00:06:23.749 align:start position:0% syntactic sugar that we have for our return<00:06:21.720> values<00:06:22.259> you<00:06:22.979> could<00:06:23.100> instead<00:06:23.520> for 00:06:23.749 --> 00:06:23.759 align:start position:0% return values you could instead for 00:06:23.759 --> 00:06:26.689 align:start position:0% return values you could instead for example<00:06:24.120> not<00:06:25.080> have<00:06:25.440> the<00:06:25.740> nullifier<00:06:26.340> be 00:06:26.689 --> 00:06:26.699 align:start position:0% example not have the nullifier be 00:06:26.699 --> 00:06:28.430 align:start position:0% example not have the nullifier be returned<00:06:27.120> as<00:06:27.240> public<00:06:27.419> output<00:06:27.840> you<00:06:28.319> could 00:06:28.430 --> 00:06:28.440 align:start position:0% returned as public output you could 00:06:28.440 --> 00:06:30.650 align:start position:0% returned as public output you could instill<00:06:28.740> Supply<00:06:29.100> it<00:06:29.400> as<00:06:29.580> public<00:06:29.819> input<00:06:30.240> and 00:06:30.650 --> 00:06:30.660 align:start position:0% instill Supply it as public input and 00:06:30.660 --> 00:06:32.210 align:start position:0% instill Supply it as public input and you<00:06:30.840> would<00:06:30.960> have<00:06:31.080> to<00:06:31.199> then<00:06:31.319> write<00:06:31.560> constrain 00:06:32.210 --> 00:06:32.220 align:start position:0% you would have to then write constrain 00:06:32.220 --> 00:06:34.909 align:start position:0% you would have to then write constrain like<00:06:32.940> nullify<00:06:33.479> or<00:06:33.660> hash<00:06:33.900> equals<00:06:34.259> nullify<00:06:34.740> or 00:06:34.909 --> 00:06:34.919 align:start position:0% like nullify or hash equals nullify or 00:06:34.919 --> 00:06:37.490 align:start position:0% like nullify or hash equals nullify or index<00:06:35.220> 0<00:06:35.400> there<00:06:35.759> but<00:06:36.539> this<00:06:36.960> is<00:06:37.080> happening 00:06:37.490 --> 00:06:37.500 align:start position:0% index 0 there but this is happening 00:06:37.500 --> 00:06:39.350 align:start position:0% index 0 there but this is happening implicitly<00:06:38.100> when<00:06:38.340> we<00:06:38.460> return<00:06:38.639> it<00:06:38.940> from<00:06:39.240> the 00:06:39.350 --> 00:06:39.360 align:start position:0% implicitly when we return it from the 00:06:39.360 --> 00:06:41.390 align:start position:0% implicitly when we return it from the circuit<00:06:39.660> right<00:06:39.900> there<00:06:40.080> as<00:06:40.620> this<00:06:40.800> circuit<00:06:41.160> is 00:06:41.390 --> 00:06:41.400 align:start position:0% circuit right there as this circuit is 00:06:41.400 --> 00:06:43.550 align:start position:0% circuit right there as this circuit is the<00:06:41.639> title<00:06:42.060> of<00:06:42.180> this<00:06:42.300> the<00:06:42.660> presentation<00:06:43.259> is 00:06:43.550 --> 00:06:43.560 align:start position:0% the title of this the presentation is 00:06:43.560 --> 00:06:46.430 align:start position:0% the title of this the presentation is it's<00:06:43.979> Noir<00:06:44.580> uh<00:06:45.479> private<00:06:45.780> transfer<00:06:46.139> in<00:06:46.259> 10 00:06:46.430 --> 00:06:46.440 align:start position:0% it's Noir uh private transfer in 10 00:06:46.440 --> 00:06:48.469 align:start position:0% it's Noir uh private transfer in 10 lines<00:06:46.800> so<00:06:47.340> we<00:06:47.520> don't<00:06:47.639> really<00:06:47.759> show<00:06:48.000> a<00:06:48.240> lot<00:06:48.360> of 00:06:48.469 --> 00:06:48.479 align:start position:0% lines so we don't really show a lot of 00:06:48.479 --> 00:06:50.689 align:start position:0% lines so we don't really show a lot of what<00:06:48.780> the<00:06:49.139> Noir<00:06:49.440> syntax<00:06:49.919> looks<00:06:50.220> like<00:06:50.280> so<00:06:50.520> I 00:06:50.689 --> 00:06:50.699 align:start position:0% what the Noir syntax looks like so I 00:06:50.699 --> 00:06:52.670 align:start position:0% what the Noir syntax looks like so I wanted<00:06:50.819> to<00:06:51.120> quickly<00:06:51.419> highlight<00:06:52.259> what<00:06:52.620> else 00:06:52.670 --> 00:06:52.680 align:start position:0% wanted to quickly highlight what else 00:06:52.680 --> 00:06:55.670 align:start position:0% wanted to quickly highlight what else also<00:06:53.100> exists<00:06:53.400> in<00:06:53.580> Noir<00:06:54.419> we<00:06:55.020> do<00:06:55.199> have<00:06:55.319> compound 00:06:55.670 --> 00:06:55.680 align:start position:0% also exists in Noir we do have compound 00:06:55.680 --> 00:06:57.950 align:start position:0% also exists in Noir we do have compound data<00:06:56.039> types<00:06:56.280> such<00:06:56.520> as<00:06:56.639> arrays<00:06:57.180> tuples<00:06:57.660> and 00:06:57.950 --> 00:06:57.960 align:start position:0% data types such as arrays tuples and 00:06:57.960 --> 00:06:59.809 align:start position:0% data types such as arrays tuples and structs<00:06:58.380> as<00:06:58.500> you<00:06:58.620> can<00:06:58.740> see<00:06:58.860> right<00:06:59.039> there 00:06:59.809 --> 00:06:59.819 align:start position:0% structs as you can see right there 00:06:59.819 --> 00:07:01.730 align:start position:0% structs as you can see right there and<00:07:00.419> you<00:07:00.660> can<00:07:00.720> then<00:07:00.900> we<00:07:01.199> also<00:07:01.380> have<00:07:01.500> sub 00:07:01.730 --> 00:07:01.740 align:start position:0% and you can then we also have sub 00:07:01.740 --> 00:07:03.650 align:start position:0% and you can then we also have sub modules<00:07:02.160> so<00:07:02.400> you<00:07:02.580> can<00:07:02.639> easily<00:07:02.940> separate<00:07:03.419> your 00:07:03.650 --> 00:07:03.660 align:start position:0% modules so you can easily separate your 00:07:03.660 --> 00:07:06.230 align:start position:0% modules so you can easily separate your functions<00:07:04.080> as<00:07:04.319> you<00:07:04.500> as<00:07:04.740> you<00:07:04.919> see<00:07:05.039> fit<00:07:05.400> also 00:07:06.230 --> 00:07:06.240 align:start position:0% functions as you as you see fit also 00:07:06.240 --> 00:07:08.210 align:start position:0% functions as you as you see fit also just<00:07:06.419> recently<00:07:06.780> added<00:07:07.139> Global<00:07:07.500> consts<00:07:07.979> which 00:07:08.210 --> 00:07:08.220 align:start position:0% just recently added Global consts which 00:07:08.220 --> 00:07:09.710 align:start position:0% just recently added Global consts which you<00:07:08.400> can<00:07:08.460> also<00:07:08.699> import<00:07:08.880> as<00:07:09.180> you<00:07:09.300> would<00:07:09.419> in<00:07:09.600> any 00:07:09.710 --> 00:07:09.720 align:start position:0% you can also import as you would in any 00:07:09.720 --> 00:07:11.749 align:start position:0% you can also import as you would in any other<00:07:09.900> programming<00:07:10.800> language<00:07:10.919> such<00:07:11.280> as<00:07:11.400> rust 00:07:11.749 --> 00:07:11.759 align:start position:0% other programming language such as rust 00:07:11.759 --> 00:07:14.809 align:start position:0% other programming language such as rust or<00:07:12.479> control<00:07:12.720> flow<00:07:13.139> we<00:07:13.440> have<00:07:13.560> for<00:07:13.860> loops<00:07:14.280> and<00:07:14.580> if 00:07:14.809 --> 00:07:14.819 align:start position:0% or control flow we have for loops and if 00:07:14.819 --> 00:07:16.430 align:start position:0% or control flow we have for loops and if statements<00:07:15.360> and<00:07:15.720> we're<00:07:15.840> looking<00:07:16.080> to<00:07:16.259> add 00:07:16.430 --> 00:07:16.440 align:start position:0% statements and we're looking to add 00:07:16.440 --> 00:07:18.050 align:start position:0% statements and we're looking to add recursion<00:07:16.919> soon<00:07:17.160> as<00:07:17.340> well 00:07:18.050 --> 00:07:18.060 align:start position:0% recursion soon as well 00:07:18.060 --> 00:07:20.089 align:start position:0% recursion soon as well we<00:07:18.479> also<00:07:18.660> have<00:07:18.780> recently<00:07:19.080> added<00:07:19.380> to<00:07:19.500> generics 00:07:20.089 --> 00:07:20.099 align:start position:0% we also have recently added to generics 00:07:20.099 --> 00:07:22.010 align:start position:0% we also have recently added to generics which<00:07:20.340> is<00:07:20.520> highlighted<00:07:21.000> right<00:07:21.180> here<00:07:21.360> which<00:07:21.900> is 00:07:22.010 --> 00:07:22.020 align:start position:0% which is highlighted right here which is 00:07:22.020 --> 00:07:23.870 align:start position:0% which is highlighted right here which is a<00:07:22.199> great<00:07:22.319> benefit<00:07:22.560> to<00:07:23.099> the<00:07:23.280> developer 00:07:23.870 --> 00:07:23.880 align:start position:0% a great benefit to the developer 00:07:23.880 --> 00:07:26.270 align:start position:0% a great benefit to the developer experience<00:07:24.360> just<00:07:24.840> to<00:07:25.139> recap<00:07:25.440> we<00:07:25.860> try<00:07:25.979> and<00:07:26.160> be 00:07:26.270 --> 00:07:26.280 align:start position:0% experience just to recap we try and be 00:07:26.280 --> 00:07:29.089 align:start position:0% experience just to recap we try and be high<00:07:26.520> level<00:07:26.699> as<00:07:27.180> we<00:07:27.479> want<00:07:27.720> to<00:07:28.020> make<00:07:28.319> this<00:07:28.620> the 00:07:29.089 --> 00:07:29.099 align:start position:0% high level as we want to make this the 00:07:29.099 --> 00:07:31.129 align:start position:0% high level as we want to make this the development<00:07:29.520> experience<00:07:29.940> easier<00:07:30.360> but<00:07:30.720> also 00:07:31.129 --> 00:07:31.139 align:start position:0% development experience easier but also 00:07:31.139 --> 00:07:33.170 align:start position:0% development experience easier but also abstract<00:07:31.800> away<00:07:32.039> some<00:07:32.340> of<00:07:32.460> that<00:07:32.580> cryptographic 00:07:33.170 --> 00:07:33.180 align:start position:0% abstract away some of that cryptographic 00:07:33.180 --> 00:07:35.150 align:start position:0% abstract away some of that cryptographic safety<00:07:33.539> that<00:07:33.840> you<00:07:34.020> might<00:07:34.259> be<00:07:34.680> familiar<00:07:35.039> with 00:07:35.150 --> 00:07:35.160 align:start position:0% safety that you might be familiar with 00:07:35.160 --> 00:07:37.370 align:start position:0% safety that you might be familiar with in<00:07:35.340> other<00:07:35.460> ZK<00:07:35.880> circuit<00:07:36.300> languages<00:07:36.599> or<00:07:37.199> where 00:07:37.370 --> 00:07:37.380 align:start position:0% in other ZK circuit languages or where 00:07:37.380 --> 00:07:39.830 align:start position:0% in other ZK circuit languages or where you<00:07:37.560> have<00:07:37.740> to<00:07:38.039> directly<00:07:38.819> specify<00:07:39.300> essentially 00:07:39.830 --> 00:07:39.840 align:start position:0% you have to directly specify essentially 00:07:39.840 --> 00:07:42.110 align:start position:0% you have to directly specify essentially every<00:07:40.560> constraint<00:07:41.039> and<00:07:41.520> that's<00:07:41.639> the<00:07:41.819> ultimate 00:07:42.110 --> 00:07:42.120 align:start position:0% every constraint and that's the ultimate 00:07:42.120 --> 00:07:45.770 align:start position:0% every constraint and that's the ultimate goal<00:07:42.360> of<00:07:42.419> Noir<00:07:42.840> to<00:07:43.319> have<00:07:43.560> safety<00:07:44.039> and<00:07:44.819> the<00:07:45.539> a 00:07:45.770 --> 00:07:45.780 align:start position:0% goal of Noir to have safety and the a 00:07:45.780 --> 00:07:47.749 align:start position:0% goal of Noir to have safety and the a greater<00:07:46.080> development<00:07:46.440> experience<00:07:46.919> now<00:07:47.580> I'm 00:07:47.749 --> 00:07:47.759 align:start position:0% greater development experience now I'm 00:07:47.759 --> 00:07:48.830 align:start position:0% greater development experience now I'm actually<00:07:47.940> going<00:07:48.180> to<00:07:48.300> kind<00:07:48.419> of<00:07:48.479> walk<00:07:48.660> through 00:07:48.830 --> 00:07:48.840 align:start position:0% actually going to kind of walk through 00:07:48.840 --> 00:07:51.230 align:start position:0% actually going to kind of walk through how<00:07:49.139> you<00:07:49.380> would<00:07:49.500> use<00:07:49.620> our<00:07:49.860> wrapper<00:07:50.280> to<00:07:50.639> prove 00:07:51.230 --> 00:07:51.240 align:start position:0% how you would use our wrapper to prove 00:07:51.240 --> 00:07:52.969 align:start position:0% how you would use our wrapper to prove and<00:07:51.360> verify<00:07:51.780> this<00:07:51.960> circuit<00:07:52.380> in<00:07:52.620> typescript 00:07:52.969 --> 00:07:52.979 align:start position:0% and verify this circuit in typescript 00:07:52.979 --> 00:07:55.189 align:start position:0% and verify this circuit in typescript and<00:07:53.280> then<00:07:53.520> ultimately<00:07:54.180> in<00:07:54.419> the<00:07:54.539> browser<00:07:54.900> so 00:07:55.189 --> 00:07:55.199 align:start position:0% and then ultimately in the browser so 00:07:55.199 --> 00:07:58.249 align:start position:0% and then ultimately in the browser so that<00:07:55.500> clients<00:07:56.400> can<00:07:56.639> you<00:07:57.360> can<00:07:57.479> prove<00:07:57.900> on<00:07:58.139> the 00:07:58.249 --> 00:07:58.259 align:start position:0% that clients can you can prove on the 00:07:58.259 --> 00:07:59.450 align:start position:0% that clients can you can prove on the client<00:07:58.440> side 00:07:59.450 --> 00:07:59.460 align:start position:0% client side 00:07:59.460 --> 00:08:02.749 align:start position:0% client side we<00:08:00.060> have<00:08:00.180> a<00:08:00.300> Noir<00:08:00.660> JS<00:08:01.020> package<00:08:01.440> which<00:08:02.039> has<00:08:02.460> been 00:08:02.749 --> 00:08:02.759 align:start position:0% we have a Noir JS package which has been 00:08:02.759 --> 00:08:05.089 align:start position:0% we have a Noir JS package which has been created<00:08:03.060> to<00:08:03.300> allow<00:08:03.539> developer<00:08:04.080> to<00:08:04.500> you<00:08:04.979> can 00:08:05.089 --> 00:08:05.099 align:start position:0% created to allow developer to you can 00:08:05.099 --> 00:08:07.010 align:start position:0% created to allow developer to you can directly<00:08:05.699> compile<00:08:06.180> your<00:08:06.660> circuit<00:08:06.900> and 00:08:07.010 --> 00:08:07.020 align:start position:0% directly compile your circuit and 00:08:07.020 --> 00:08:09.350 align:start position:0% directly compile your circuit and typescript<00:08:07.380> as<00:08:07.620> you<00:08:07.740> see<00:08:07.860> there<00:08:08.099> but<00:08:08.759> in<00:08:09.180> this 00:08:09.350 --> 00:08:09.360 align:start position:0% typescript as you see there but in this 00:08:09.360 --> 00:08:11.990 align:start position:0% typescript as you see there but in this in<00:08:09.960> this<00:08:10.199> uh<00:08:10.440> package<00:08:10.919> you<00:08:11.160> can<00:08:11.220> also<00:08:11.520> read<00:08:11.759> in 00:08:11.990 --> 00:08:12.000 align:start position:0% in this uh package you can also read in 00:08:12.000 --> 00:08:14.210 align:start position:0% in this uh package you can also read in from<00:08:12.660> the<00:08:12.900> Acer<00:08:13.259> from<00:08:13.440> file<00:08:13.740> that<00:08:13.979> would<00:08:14.099> be 00:08:14.210 --> 00:08:14.220 align:start position:0% from the Acer from file that would be 00:08:14.220 --> 00:08:16.730 align:start position:0% from the Acer from file that would be generated<00:08:14.520> by<00:08:14.819> the<00:08:15.000> nargo<00:08:15.840> package<00:08:16.259> manager 00:08:16.730 --> 00:08:16.740 align:start position:0% generated by the nargo package manager 00:08:16.740 --> 00:08:19.430 align:start position:0% generated by the nargo package manager that's<00:08:17.520> a<00:08:17.940> choice<00:08:18.060> of<00:08:18.240> the<00:08:18.360> developer<00:08:18.780> but<00:08:19.139> in 00:08:19.430 --> 00:08:19.440 align:start position:0% that's a choice of the developer but in 00:08:19.440 --> 00:08:21.710 align:start position:0% that's a choice of the developer but in this<00:08:19.560> example<00:08:19.919> we<00:08:20.639> just<00:08:20.819> uh<00:08:21.120> we<00:08:21.360> just<00:08:21.479> show<00:08:21.599> you 00:08:21.710 --> 00:08:21.720 align:start position:0% this example we just uh we just show you 00:08:21.720 --> 00:08:23.990 align:start position:0% this example we just uh we just show you how<00:08:21.900> to<00:08:22.020> compile<00:08:22.319> it<00:08:22.500> directly<00:08:22.860> in<00:08:22.979> typescript 00:08:23.990 --> 00:08:24.000 align:start position:0% how to compile it directly in typescript 00:08:24.000 --> 00:08:26.390 align:start position:0% how to compile it directly in typescript so<00:08:24.660> after<00:08:24.960> we<00:08:25.199> have<00:08:25.319> an<00:08:25.500> object<00:08:25.740> representing 00:08:26.390 --> 00:08:26.400 align:start position:0% so after we have an object representing 00:08:26.400 --> 00:08:28.369 align:start position:0% so after we have an object representing our<00:08:26.580> Acer<00:08:27.000> we<00:08:27.300> then<00:08:27.479> just<00:08:27.599> have<00:08:27.780> to<00:08:27.900> specify 00:08:28.369 --> 00:08:28.379 align:start position:0% our Acer we then just have to specify 00:08:28.379 --> 00:08:30.950 align:start position:0% our Acer we then just have to specify our<00:08:28.620> ABI<00:08:29.099> and<00:08:29.759> the<00:08:29.879> ABI<00:08:30.300> is<00:08:30.419> what<00:08:30.599> the<00:08:30.720> prover 00:08:30.950 --> 00:08:30.960 align:start position:0% our ABI and the ABI is what the prover 00:08:30.960 --> 00:08:33.589 align:start position:0% our ABI and the ABI is what the prover is<00:08:31.440> going<00:08:31.560> to<00:08:31.680> be<00:08:31.740> providing<00:08:32.279> to<00:08:33.120> ultimately 00:08:33.589 --> 00:08:33.599 align:start position:0% is going to be providing to ultimately 00:08:33.599 --> 00:08:35.329 align:start position:0% is going to be providing to ultimately construct<00:08:34.020> our<00:08:34.200> proof<00:08:34.620> which<00:08:34.919> has<00:08:35.099> our 00:08:35.329 --> 00:08:35.339 align:start position:0% construct our proof which has our 00:08:35.339 --> 00:08:37.550 align:start position:0% construct our proof which has our private<00:08:35.820> and<00:08:36.419> public<00:08:36.599> inputs<00:08:37.200> and<00:08:37.440> that's 00:08:37.550 --> 00:08:37.560 align:start position:0% private and public inputs and that's 00:08:37.560 --> 00:08:39.050 align:start position:0% private and public inputs and that's going<00:08:37.740> to<00:08:37.860> be<00:08:37.919> used<00:08:38.099> to<00:08:38.399> generate<00:08:38.760> the<00:08:38.880> witness 00:08:39.050 --> 00:08:39.060 align:start position:0% going to be used to generate the witness 00:08:39.060 --> 00:08:41.930 align:start position:0% going to be used to generate the witness and<00:08:39.839> ultimately<00:08:40.440> generate<00:08:40.860> the<00:08:40.979> proof<00:08:41.279> so 00:08:41.930 --> 00:08:41.940 align:start position:0% and ultimately generate the proof so 00:08:41.940 --> 00:08:44.149 align:start position:0% and ultimately generate the proof so because<00:08:42.300> Noir<00:08:43.020> is<00:08:43.200> back<00:08:43.380> in<00:08:43.500> agnostic<00:08:43.979> though 00:08:44.149 --> 00:08:44.159 align:start position:0% because Noir is back in agnostic though 00:08:44.159 --> 00:08:46.490 align:start position:0% because Noir is back in agnostic though we<00:08:44.459> have<00:08:44.580> a<00:08:44.760> separate<00:08:45.060> wrapper<00:08:45.480> around<00:08:46.140> the 00:08:46.490 --> 00:08:46.500 align:start position:0% we have a separate wrapper around the 00:08:46.500 --> 00:08:49.250 align:start position:0% we have a separate wrapper around the Aztec<00:08:46.920> ruttenberg<00:08:47.399> back<00:08:47.640> end<00:08:47.760> and<00:08:48.480> that's<00:08:48.660> any 00:08:49.250 --> 00:08:49.260 align:start position:0% Aztec ruttenberg back end and that's any 00:08:49.260 --> 00:08:51.050 align:start position:0% Aztec ruttenberg back end and that's any other<00:08:49.440> backend<00:08:49.740> that's<00:08:49.980> gets<00:08:50.519> integrated<00:08:50.820> is 00:08:51.050 --> 00:08:51.060 align:start position:0% other backend that's gets integrated is 00:08:51.060 --> 00:08:52.190 align:start position:0% other backend that's gets integrated is going<00:08:51.240> to<00:08:51.360> have<00:08:51.420> to<00:08:51.540> do<00:08:51.660> the<00:08:51.779> same<00:08:51.899> thing<00:08:52.019> as 00:08:52.190 --> 00:08:52.200 align:start position:0% going to have to do the same thing as 00:08:52.200 --> 00:08:54.170 align:start position:0% going to have to do the same thing as well<00:08:52.380> because<00:08:52.920> this<00:08:53.339> backend<00:08:53.700> has<00:08:53.880> been<00:08:54.060> made 00:08:54.170 --> 00:08:54.180 align:start position:0% well because this backend has been made 00:08:54.180 --> 00:08:56.690 align:start position:0% well because this backend has been made to<00:08:54.480> match<00:08:54.660> the<00:08:55.019> Acer<00:08:55.380> interface<00:08:55.860> in<00:08:56.399> order<00:08:56.519> to 00:08:56.690 --> 00:08:56.700 align:start position:0% to match the Acer interface in order to 00:08:56.700 --> 00:08:58.850 align:start position:0% to match the Acer interface in order to set<00:08:56.820> up<00:08:56.880> the<00:08:57.060> prover<00:08:57.300> and<00:08:57.540> verifier<00:08:57.959> we<00:08:58.560> simply 00:08:58.850 --> 00:08:58.860 align:start position:0% set up the prover and verifier we simply 00:08:58.860 --> 00:09:01.070 align:start position:0% set up the prover and verifier we simply pass<00:08:59.160> in<00:08:59.339> the<00:08:59.519> Acer<00:08:59.940> and<00:09:00.540> as<00:09:00.779> you<00:09:00.899> can<00:09:00.959> see 00:09:01.070 --> 00:09:01.080 align:start position:0% pass in the Acer and as you can see 00:09:01.080 --> 00:09:03.530 align:start position:0% pass in the Acer and as you can see right<00:09:01.380> there<00:09:01.560> and<00:09:02.339> then<00:09:02.459> that<00:09:02.700> ABI<00:09:03.120> that<00:09:03.420> we 00:09:03.530 --> 00:09:03.540 align:start position:0% right there and then that ABI that we 00:09:03.540 --> 00:09:05.630 align:start position:0% right there and then that ABI that we specified<00:09:03.839> earlier<00:09:04.380> to<00:09:04.680> construct<00:09:05.040> our<00:09:05.220> proof 00:09:05.630 --> 00:09:05.640 align:start position:0% specified earlier to construct our proof 00:09:05.640 --> 00:09:07.490 align:start position:0% specified earlier to construct our proof and<00:09:06.180> then<00:09:06.300> we<00:09:06.480> just<00:09:06.600> pass<00:09:06.779> it<00:09:06.959> along<00:09:07.140> to<00:09:07.380> our 00:09:07.490 --> 00:09:07.500 align:start position:0% and then we just pass it along to our 00:09:07.500 --> 00:09:09.829 align:start position:0% and then we just pass it along to our verifier<00:09:07.980> one<00:09:08.640> thing<00:09:08.820> you<00:09:08.940> might<00:09:09.120> note<00:09:09.360> though 00:09:09.829 --> 00:09:09.839 align:start position:0% verifier one thing you might note though 00:09:09.839 --> 00:09:12.230 align:start position:0% verifier one thing you might note though is<00:09:10.260> that<00:09:10.680> you<00:09:11.040> don't<00:09:11.160> see<00:09:11.339> any<00:09:11.580> public<00:09:11.760> inputs 00:09:12.230 --> 00:09:12.240 align:start position:0% is that you don't see any public inputs 00:09:12.240 --> 00:09:13.910 align:start position:0% is that you don't see any public inputs being<00:09:12.420> passed<00:09:12.779> to<00:09:12.839> the<00:09:12.959> verifier<00:09:13.380> even<00:09:13.740> though 00:09:13.910 --> 00:09:13.920 align:start position:0% being passed to the verifier even though 00:09:13.920 --> 00:09:15.889 align:start position:0% being passed to the verifier even though we<00:09:14.160> have<00:09:14.279> we<00:09:14.940> had<00:09:15.060> that<00:09:15.240> in<00:09:15.420> our<00:09:15.540> circuit 00:09:15.889 --> 00:09:15.899 align:start position:0% we have we had that in our circuit 00:09:15.899 --> 00:09:17.810 align:start position:0% we have we had that in our circuit currently<00:09:16.620> the<00:09:16.860> proof<00:09:17.100> that<00:09:17.279> gets<00:09:17.519> spit<00:09:17.700> out 00:09:17.810 --> 00:09:17.820 align:start position:0% currently the proof that gets spit out 00:09:17.820 --> 00:09:20.449 align:start position:0% currently the proof that gets spit out by<00:09:17.940> brettenberg<00:09:18.540> is<00:09:18.899> pre-pending<00:09:19.500> those<00:09:19.740> as 00:09:20.449 --> 00:09:20.459 align:start position:0% by brettenberg is pre-pending those as 00:09:20.459 --> 00:09:23.509 align:start position:0% by brettenberg is pre-pending those as 32<00:09:20.940> byte<00:09:21.300> hex<00:09:21.480> string<00:09:21.720> inputs<00:09:22.200> but<00:09:22.800> we<00:09:23.100> plan<00:09:23.339> to 00:09:23.509 --> 00:09:23.519 align:start position:0% 32 byte hex string inputs but we plan to 00:09:23.519 --> 00:09:25.790 align:start position:0% 32 byte hex string inputs but we plan to separate<00:09:23.940> that<00:09:24.420> as<00:09:24.600> developers<00:09:25.019> might<00:09:25.380> like 00:09:25.790 --> 00:09:25.800 align:start position:0% separate that as developers might like 00:09:25.800 --> 00:09:27.769 align:start position:0% separate that as developers might like to<00:09:26.160> have<00:09:26.459> those<00:09:26.700> inputs<00:09:27.060> separated<00:09:27.360> for<00:09:27.660> their 00:09:27.769 --> 00:09:27.779 align:start position:0% to have those inputs separated for their 00:09:27.779 --> 00:09:30.470 align:start position:0% to have those inputs separated for their own<00:09:27.899> development<00:09:28.260> purposes<00:09:28.740> but<00:09:29.580> that's 00:09:30.470 --> 00:09:30.480 align:start position:0% own development purposes but that's 00:09:30.480 --> 00:09:31.970 align:start position:0% own development purposes but that's just<00:09:30.839> to<00:09:31.019> take<00:09:31.140> note<00:09:31.320> of<00:09:31.440> why<00:09:31.620> you<00:09:31.740> don't<00:09:31.860> see 00:09:31.970 --> 00:09:31.980 align:start position:0% just to take note of why you don't see 00:09:31.980 --> 00:09:33.470 align:start position:0% just to take note of why you don't see any<00:09:32.160> public<00:09:32.399> inputs<00:09:32.760> being<00:09:32.940> passed<00:09:33.300> to<00:09:33.360> the 00:09:33.470 --> 00:09:33.480 align:start position:0% any public inputs being passed to the 00:09:33.480 --> 00:09:36.410 align:start position:0% any public inputs being passed to the verifier<00:09:33.839> there<00:09:34.080> so<00:09:34.680> we<00:09:34.980> can<00:09:35.160> this<00:09:35.820> it's<00:09:36.180> cool 00:09:36.410 --> 00:09:36.420 align:start position:0% verifier there so we can this it's cool 00:09:36.420 --> 00:09:37.670 align:start position:0% verifier there so we can this it's cool that<00:09:36.660> we<00:09:36.779> can<00:09:36.899> actually<00:09:37.019> verify<00:09:37.500> in 00:09:37.670 --> 00:09:37.680 align:start position:0% that we can actually verify in 00:09:37.680 --> 00:09:39.470 align:start position:0% that we can actually verify in typescript<00:09:38.040> but<00:09:38.459> we<00:09:38.760> want<00:09:38.880> to<00:09:39.000> be<00:09:39.120> able<00:09:39.240> to 00:09:39.470 --> 00:09:39.480 align:start position:0% typescript but we want to be able to 00:09:39.480 --> 00:09:41.810 align:start position:0% typescript but we want to be able to also<00:09:39.779> enable<00:09:40.080> this<00:09:40.380> in<00:09:40.920> smart<00:09:41.100> contracts<00:09:41.640> as 00:09:41.810 --> 00:09:41.820 align:start position:0% also enable this in smart contracts as 00:09:41.820 --> 00:09:44.329 align:start position:0% also enable this in smart contracts as well<00:09:41.940> so<00:09:42.779> Aztecs<00:09:43.320> brettenberg<00:09:43.680> backend<00:09:44.100> does 00:09:44.329 --> 00:09:44.339 align:start position:0% well so Aztecs brettenberg backend does 00:09:44.339 --> 00:09:46.190 align:start position:0% well so Aztecs brettenberg backend does allow<00:09:44.640> you<00:09:44.700> to<00:09:44.880> compile<00:09:45.180> from<00:09:45.480> a<00:09:45.600> Noir<00:09:45.959> program 00:09:46.190 --> 00:09:46.200 align:start position:0% allow you to compile from a Noir program 00:09:46.200 --> 00:09:48.230 align:start position:0% allow you to compile from a Noir program to<00:09:46.740> an<00:09:46.920> ethereum<00:09:47.279> contract 00:09:48.230 --> 00:09:48.240 align:start position:0% to an ethereum contract 00:09:48.240 --> 00:09:50.210 align:start position:0% to an ethereum contract improving<00:09:48.899> systems<00:09:49.260> looking<00:09:49.560> to<00:09:49.860> integrate 00:09:50.210 --> 00:09:50.220 align:start position:0% improving systems looking to integrate 00:09:50.220 --> 00:09:51.889 align:start position:0% improving systems looking to integrate Noir<00:09:50.640> are<00:09:50.880> going<00:09:51.060> to<00:09:51.180> have<00:09:51.240> to<00:09:51.360> provide<00:09:51.660> their 00:09:51.889 --> 00:09:51.899 align:start position:0% Noir are going to have to provide their 00:09:51.899 --> 00:09:53.570 align:start position:0% Noir are going to have to provide their own<00:09:52.019> implementation<00:09:52.560> of<00:09:52.800> how<00:09:52.920> to<00:09:53.040> generate<00:09:53.399> a 00:09:53.570 --> 00:09:53.580 align:start position:0% own implementation of how to generate a 00:09:53.580 --> 00:09:56.210 align:start position:0% own implementation of how to generate a solidity<00:09:53.940> verifier<00:09:54.420> or<00:09:55.320> if<00:09:55.560> you<00:09:55.740> choose<00:09:56.100> to 00:09:56.210 --> 00:09:56.220 align:start position:0% solidity verifier or if you choose to 00:09:56.220 --> 00:09:57.590 align:start position:0% solidity verifier or if you choose to use<00:09:56.339> any<00:09:56.580> other<00:09:56.700> smart<00:09:56.940> contract<00:09:57.300> platform 00:09:57.590 --> 00:09:57.600 align:start position:0% use any other smart contract platform 00:09:57.600 --> 00:09:58.850 align:start position:0% use any other smart contract platform you're<00:09:57.839> going<00:09:57.959> to<00:09:58.080> have<00:09:58.140> to<00:09:58.260> provide<00:09:58.560> that 00:09:58.850 --> 00:09:58.860 align:start position:0% you're going to have to provide that 00:09:58.860 --> 00:10:00.590 align:start position:0% you're going to have to provide that implementation<00:09:59.580> yourself<00:09:59.880> if<00:10:00.480> you're 00:10:00.590 --> 00:10:00.600 align:start position:0% implementation yourself if you're 00:10:00.600 --> 00:10:02.930 align:start position:0% implementation yourself if you're integrating<00:10:00.959> a<00:10:01.140> back<00:10:01.260> end<00:10:01.920> this<00:10:02.459> script<00:10:02.700> here 00:10:02.930 --> 00:10:02.940 align:start position:0% integrating a back end this script here 00:10:02.940 --> 00:10:05.210 align:start position:0% integrating a back end this script here shows<00:10:03.420> you<00:10:03.540> how<00:10:03.779> to<00:10:03.959> generate<00:10:04.440> a<00:10:04.800> solidity 00:10:05.210 --> 00:10:05.220 align:start position:0% shows you how to generate a solidity 00:10:05.220 --> 00:10:07.190 align:start position:0% shows you how to generate a solidity verifier<00:10:05.640> using<00:10:06.120> that<00:10:06.300> Aztec<00:10:06.720> brettenberg 00:10:07.190 --> 00:10:07.200 align:start position:0% verifier using that Aztec brettenberg 00:10:07.200 --> 00:10:09.829 align:start position:0% verifier using that Aztec brettenberg back<00:10:07.440> end<00:10:08.040> and<00:10:08.760> it's<00:10:09.120> important<00:10:09.420> to<00:10:09.540> take<00:10:09.660> note 00:10:09.829 --> 00:10:09.839 align:start position:0% back end and it's important to take note 00:10:09.839 --> 00:10:11.509 align:start position:0% back end and it's important to take note though<00:10:10.019> if<00:10:10.200> you<00:10:10.260> change<00:10:10.440> your<00:10:10.620> circuit<00:10:10.980> and 00:10:11.509 --> 00:10:11.519 align:start position:0% though if you change your circuit and 00:10:11.519 --> 00:10:13.910 align:start position:0% though if you change your circuit and don't<00:10:11.700> change<00:10:12.000> your<00:10:12.959> you<00:10:13.200> don't<00:10:13.320> regenerate 00:10:13.910 --> 00:10:13.920 align:start position:0% don't change your you don't regenerate 00:10:13.920 --> 00:10:15.710 align:start position:0% don't change your you don't regenerate your<00:10:14.220> solidity<00:10:14.640> verifier<00:10:15.060> with<00:10:15.300> the<00:10:15.420> script 00:10:15.710 --> 00:10:15.720 align:start position:0% your solidity verifier with the script 00:10:15.720 --> 00:10:17.630 align:start position:0% your solidity verifier with the script your<00:10:16.320> circuit<00:10:16.620> is<00:10:16.800> ultimately<00:10:17.100> going<00:10:17.339> to<00:10:17.459> fail 00:10:17.630 --> 00:10:17.640 align:start position:0% your circuit is ultimately going to fail 00:10:17.640 --> 00:10:19.970 align:start position:0% your circuit is ultimately going to fail as<00:10:18.120> you're<00:10:18.300> going<00:10:18.420> to<00:10:18.540> have<00:10:18.600> a<00:10:18.779> new<00:10:18.899> Acer<00:10:19.380> and 00:10:19.970 --> 00:10:19.980 align:start position:0% as you're going to have a new Acer and 00:10:19.980 --> 00:10:21.230 align:start position:0% as you're going to have a new Acer and you're<00:10:20.100> going<00:10:20.279> to<00:10:20.399> have<00:10:20.519> a<00:10:20.760> you're<00:10:20.940> going<00:10:21.120> to 00:10:21.230 --> 00:10:21.240 align:start position:0% you're going to have a you're going to 00:10:21.240 --> 00:10:23.090 align:start position:0% you're going to have a you're going to need<00:10:21.300> to<00:10:21.420> regenerate<00:10:21.959> that<00:10:22.200> verifier<00:10:22.680> in 00:10:23.090 --> 00:10:23.100 align:start position:0% need to regenerate that verifier in 00:10:23.100 --> 00:10:25.910 align:start position:0% need to regenerate that verifier in order<00:10:23.220> to<00:10:23.640> have<00:10:24.180> accurate<00:10:24.540> verification<00:10:25.019> and 00:10:25.910 --> 00:10:25.920 align:start position:0% order to have accurate verification and 00:10:25.920 --> 00:10:28.310 align:start position:0% order to have accurate verification and finally<00:10:26.339> we<00:10:26.519> can<00:10:26.640> actually<00:10:26.820> have<00:10:27.120> our<00:10:27.480> ta-da 00:10:28.310 --> 00:10:28.320 align:start position:0% finally we can actually have our ta-da 00:10:28.320 --> 00:10:29.990 align:start position:0% finally we can actually have our ta-da moment<00:10:28.620> and<00:10:28.980> verify<00:10:29.459> our<00:10:29.580> circuit<00:10:29.880> and 00:10:29.990 --> 00:10:30.000 align:start position:0% moment and verify our circuit and 00:10:30.000 --> 00:10:32.269 align:start position:0% moment and verify our circuit and solidity<00:10:30.420> so<00:10:31.260> using<00:10:31.860> your<00:10:32.100> favorite 00:10:32.269 --> 00:10:32.279 align:start position:0% solidity so using your favorite 00:10:32.279 --> 00:10:35.210 align:start position:0% solidity so using your favorite deployment<00:10:33.120> method<00:10:33.600> you<00:10:34.200> can<00:10:34.380> deploy<00:10:35.040> your 00:10:35.210 --> 00:10:35.220 align:start position:0% deployment method you can deploy your 00:10:35.220 --> 00:10:36.769 align:start position:0% deployment method you can deploy your turbo<00:10:35.519> verifier<00:10:35.940> as<00:10:36.060> you<00:10:36.180> would<00:10:36.300> any<00:10:36.480> other 00:10:36.769 --> 00:10:36.779 align:start position:0% turbo verifier as you would any other 00:10:36.779 --> 00:10:39.829 align:start position:0% turbo verifier as you would any other smart<00:10:37.440> contract<00:10:38.000> and<00:10:39.000> then<00:10:39.240> you<00:10:39.480> can<00:10:39.600> take 00:10:39.829 --> 00:10:39.839 align:start position:0% smart contract and then you can take 00:10:39.839 --> 00:10:41.150 align:start position:0% smart contract and then you can take that<00:10:40.080> proof<00:10:40.440> that<00:10:40.560> was<00:10:40.740> spit<00:10:40.920> out<00:10:41.040> from 00:10:41.150 --> 00:10:41.160 align:start position:0% that proof that was spit out from 00:10:41.160 --> 00:10:43.310 align:start position:0% that proof that was spit out from brettenberg<00:10:41.700> in<00:10:41.940> the<00:10:42.060> exact<00:10:42.240> same<00:10:42.420> way<00:10:42.660> with 00:10:43.310 --> 00:10:43.320 align:start position:0% brettenberg in the exact same way with 00:10:43.320 --> 00:10:45.350 align:start position:0% brettenberg in the exact same way with the<00:10:43.500> pre<00:10:43.620> with<00:10:44.100> the<00:10:44.220> public<00:10:44.339> inputs<00:10:44.880> prepended 00:10:45.350 --> 00:10:45.360 align:start position:0% the pre with the public inputs prepended 00:10:45.360 --> 00:10:47.930 align:start position:0% the pre with the public inputs prepended pass<00:10:46.079> it<00:10:46.260> to<00:10:46.380> the<00:10:46.440> verifier<00:10:46.920> and<00:10:47.519> if<00:10:47.700> your 00:10:47.930 --> 00:10:47.940 align:start position:0% pass it to the verifier and if your 00:10:47.940 --> 00:10:50.389 align:start position:0% pass it to the verifier and if your public<00:10:48.180> inputs<00:10:48.660> are<00:10:48.779> correct<00:10:49.079> and<00:10:50.040> your 00:10:50.389 --> 00:10:50.399 align:start position:0% public inputs are correct and your 00:10:50.399 --> 00:10:52.370 align:start position:0% public inputs are correct and your specified<00:10:50.760> your<00:10:51.000> circuit<00:10:51.360> correctly<00:10:51.720> it 00:10:52.370 --> 00:10:52.380 align:start position:0% specified your circuit correctly it 00:10:52.380 --> 00:10:54.110 align:start position:0% specified your circuit correctly it should<00:10:52.560> it<00:10:52.860> should<00:10:53.040> ultimately<00:10:53.399> return<00:10:53.760> true 00:10:54.110 --> 00:10:54.120 align:start position:0% should it should ultimately return true 00:10:54.120 --> 00:10:57.110 align:start position:0% should it should ultimately return true in<00:10:54.959> the<00:10:55.079> case<00:10:55.260> of<00:10:55.800> our<00:10:56.160> private<00:10:56.760> transfer 00:10:57.110 --> 00:10:57.120 align:start position:0% in the case of our private transfer 00:10:57.120 --> 00:10:58.970 align:start position:0% in the case of our private transfer we're<00:10:57.660> going<00:10:57.839> to<00:10:57.899> be<00:10:57.959> checking<00:10:58.380> is<00:10:58.800> that 00:10:58.970 --> 00:10:58.980 align:start position:0% we're going to be checking is that 00:10:58.980 --> 00:11:01.069 align:start position:0% we're going to be checking is that nullifier<00:10:59.519> hash<00:10:59.820> been<00:11:00.000> used<00:11:00.180> before<00:11:00.360> is<00:11:00.839> the 00:11:01.069 --> 00:11:01.079 align:start position:0% nullifier hash been used before is the 00:11:01.079 --> 00:11:04.790 align:start position:0% nullifier hash been used before is the root<00:11:01.440> uh<00:11:02.160> the<00:11:02.399> correct<00:11:02.640> route<00:11:02.839> and<00:11:03.839> upon 00:11:04.790 --> 00:11:04.800 align:start position:0% root uh the correct route and upon 00:11:04.800 --> 00:11:07.370 align:start position:0% root uh the correct route and upon having<00:11:05.160> a<00:11:05.640> verified<00:11:06.000> proof<00:11:06.540> we<00:11:07.019> can<00:11:07.140> actually 00:11:07.370 --> 00:11:07.380 align:start position:0% having a verified proof we can actually 00:11:07.380 --> 00:11:10.009 align:start position:0% having a verified proof we can actually then<00:11:07.620> perform<00:11:07.980> a<00:11:08.399> private<00:11:08.700> with<00:11:08.940> a<00:11:09.300> withdrawal 00:11:10.009 --> 00:11:10.019 align:start position:0% then perform a private with a withdrawal 00:11:10.019 --> 00:11:12.470 align:start position:0% then perform a private with a withdrawal and<00:11:10.680> that<00:11:10.920> that<00:11:11.160> note<00:11:11.399> that<00:11:11.700> will<00:11:11.820> be<00:11:12.000> entirely 00:11:12.470 --> 00:11:12.480 align:start position:0% and that that note that will be entirely 00:11:12.480 --> 00:11:15.650 align:start position:0% and that that note that will be entirely private<00:11:13.260> so<00:11:13.980> that's<00:11:14.640> that's<00:11:15.060> it<00:11:15.300> there<00:11:15.540> and 00:11:15.650 --> 00:11:15.660 align:start position:0% private so that's that's it there and 00:11:15.660 --> 00:11:18.230 align:start position:0% private so that's that's it there and you<00:11:15.839> can<00:11:15.959> see<00:11:16.079> a<00:11:16.260> more<00:11:16.500> full<00:11:16.740> example<00:11:17.220> with<00:11:17.760> the 00:11:18.230 --> 00:11:18.240 align:start position:0% you can see a more full example with the 00:11:18.240 --> 00:11:21.350 align:start position:0% you can see a more full example with the uh<00:11:18.779> simple<00:11:19.260> Shield<00:11:19.560> but<00:11:20.519> ultimately<00:11:20.940> here<00:11:21.180> the 00:11:21.350 --> 00:11:21.360 align:start position:0% uh simple Shield but ultimately here the 00:11:21.360 --> 00:11:23.090 align:start position:0% uh simple Shield but ultimately here the benefit<00:11:21.480> is<00:11:21.779> that<00:11:21.959> we<00:11:22.079> can<00:11:22.200> enable<00:11:22.440> autonomous 00:11:23.090 --> 00:11:23.100 align:start position:0% benefit is that we can enable autonomous 00:11:23.100 --> 00:11:25.610 align:start position:0% benefit is that we can enable autonomous execution<00:11:23.640> in<00:11:24.480> contracts<00:11:25.019> based<00:11:25.560> off 00:11:25.610 --> 00:11:25.620 align:start position:0% execution in contracts based off 00:11:25.620 --> 00:11:28.610 align:start position:0% execution in contracts based off verification<00:11:26.279> of<00:11:26.519> Noir<00:11:26.880> circuits<00:11:27.360> and<00:11:28.200> I<00:11:28.440> want 00:11:28.610 --> 00:11:28.620 align:start position:0% verification of Noir circuits and I want 00:11:28.620 --> 00:11:31.490 align:start position:0% verification of Noir circuits and I want to<00:11:28.800> also<00:11:29.100> discuss<00:11:29.880> some<00:11:30.480> of<00:11:30.600> the<00:11:30.839> future<00:11:31.140> work 00:11:31.490 --> 00:11:31.500 align:start position:0% to also discuss some of the future work 00:11:31.500 --> 00:11:33.650 align:start position:0% to also discuss some of the future work that<00:11:31.920> we're<00:11:32.100> going<00:11:32.220> to<00:11:32.339> be<00:11:32.399> doing<00:11:32.519> in<00:11:32.760> Noir<00:11:33.120> one 00:11:33.650 --> 00:11:33.660 align:start position:0% that we're going to be doing in Noir one 00:11:33.660 --> 00:11:35.269 align:start position:0% that we're going to be doing in Noir one of<00:11:33.779> the<00:11:33.839> main<00:11:33.959> things<00:11:34.260> that<00:11:34.620> we<00:11:34.860> want<00:11:34.980> to<00:11:35.100> add 00:11:35.269 --> 00:11:35.279 align:start position:0% of the main things that we want to add 00:11:35.279 --> 00:11:38.090 align:start position:0% of the main things that we want to add is<00:11:35.880> verify<00:11:36.420> proof<00:11:36.839> this<00:11:37.620> will<00:11:37.860> actually 00:11:38.090 --> 00:11:38.100 align:start position:0% is verify proof this will actually 00:11:38.100 --> 00:11:39.829 align:start position:0% is verify proof this will actually enable<00:11:38.459> us<00:11:38.640> to<00:11:38.760> have<00:11:38.880> recursive<00:11:39.360> snarks 00:11:39.829 --> 00:11:39.839 align:start position:0% enable us to have recursive snarks 00:11:39.839 --> 00:11:42.650 align:start position:0% enable us to have recursive snarks inside<00:11:40.019> of<00:11:40.320> Noir<00:11:40.860> itself<00:11:41.100> which<00:11:41.820> enables<00:11:42.360> many 00:11:42.650 --> 00:11:42.660 align:start position:0% inside of Noir itself which enables many 00:11:42.660 --> 00:11:44.509 align:start position:0% inside of Noir itself which enables many more<00:11:42.839> use<00:11:43.079> cases<00:11:43.440> than<00:11:43.740> you<00:11:43.920> can<00:11:44.100> currently 00:11:44.509 --> 00:11:44.519 align:start position:0% more use cases than you can currently 00:11:44.519 --> 00:11:45.350 align:start position:0% more use cases than you can currently have 00:11:45.350 --> 00:11:45.360 align:start position:0% have 00:11:45.360 --> 00:11:48.829 align:start position:0% have uh<00:11:46.140> the<00:11:46.500> wrapper<00:11:46.920> itself<00:11:47.279> is<00:11:47.700> pretty<00:11:47.940> new<00:11:48.120> and 00:11:48.829 --> 00:11:48.839 align:start position:0% uh the wrapper itself is pretty new and 00:11:48.839 --> 00:11:50.509 align:start position:0% uh the wrapper itself is pretty new and we<00:11:49.079> want<00:11:49.200> to<00:11:49.440> improve<00:11:49.860> this<00:11:50.100> development 00:11:50.509 --> 00:11:50.519 align:start position:0% we want to improve this development 00:11:50.519 --> 00:11:53.210 align:start position:0% we want to improve this development signifi<00:11:51.420> these<00:11:52.200> development<00:11:52.500> tooling<00:11:52.860> submit 00:11:53.210 --> 00:11:53.220 align:start position:0% signifi these development tooling submit 00:11:53.220 --> 00:11:55.670 align:start position:0% signifi these development tooling submit significantly<00:11:53.940> to<00:11:54.420> make<00:11:54.899> it<00:11:55.019> easier<00:11:55.260> for 00:11:55.670 --> 00:11:55.680 align:start position:0% significantly to make it easier for 00:11:55.680 --> 00:11:58.009 align:start position:0% significantly to make it easier for anyone<00:11:56.100> looking<00:11:56.339> to<00:11:56.579> integrate<00:11:56.880> with<00:11:57.060> Noir 00:11:58.009 --> 00:11:58.019 align:start position:0% anyone looking to integrate with Noir 00:11:58.019 --> 00:11:59.990 align:start position:0% anyone looking to integrate with Noir we<00:11:58.560> also<00:11:58.740> want<00:11:58.860> to<00:11:59.040> integrate<00:11:59.339> it<00:11:59.459> with<00:11:59.640> Rebels 00:11:59.990 --> 00:12:00.000 align:start position:0% we also want to integrate it with Rebels 00:12:00.000 --> 00:12:01.910 align:start position:0% we also want to integrate it with Rebels such<00:12:00.180> as<00:12:00.300> ZK<00:12:00.660> Rebel<00:12:01.140> if<00:12:01.320> you're<00:12:01.440> familiar<00:12:01.740> with 00:12:01.910 --> 00:12:01.920 align:start position:0% such as ZK Rebel if you're familiar with 00:12:01.920 --> 00:12:04.009 align:start position:0% such as ZK Rebel if you're familiar with that<00:12:02.040> online<00:12:02.279> IDE<00:12:03.060> Integrations<00:12:03.660> other 00:12:04.009 --> 00:12:04.019 align:start position:0% that online IDE Integrations other 00:12:04.019 --> 00:12:07.069 align:start position:0% that online IDE Integrations other debugging<00:12:04.560> tools<00:12:04.920> a<00:12:05.579> language<00:12:05.760> server<00:12:06.240> lots 00:12:07.069 --> 00:12:07.079 align:start position:0% debugging tools a language server lots 00:12:07.079 --> 00:12:09.650 align:start position:0% debugging tools a language server lots of<00:12:07.140> development<00:12:07.560> tools<00:12:07.860> to<00:12:07.980> add<00:12:08.240> and<00:12:09.240> in<00:12:09.540> the 00:12:09.650 --> 00:12:09.660 align:start position:0% of development tools to add and in the 00:12:09.660 --> 00:12:11.569 align:start position:0% of development tools to add and in the medium<00:12:09.899> to<00:12:10.140> long<00:12:10.380> term<00:12:10.560> we're<00:12:11.339> going<00:12:11.459> to<00:12:11.519> be 00:12:11.569 --> 00:12:11.579 align:start position:0% medium to long term we're going to be 00:12:11.579 --> 00:12:14.269 align:start position:0% medium to long term we're going to be adding<00:12:11.820> Noir<00:12:12.240> contracts<00:12:12.720> and<00:12:13.440> Noir<00:12:13.860> contracts 00:12:14.269 --> 00:12:14.279 align:start position:0% adding Noir contracts and Noir contracts 00:12:14.279 --> 00:12:15.530 align:start position:0% adding Noir contracts and Noir contracts are<00:12:14.399> going<00:12:14.640> to<00:12:14.760> be<00:12:14.820> the<00:12:15.000> next<00:12:15.120> stage<00:12:15.360> of 00:12:15.530 --> 00:12:15.540 align:start position:0% are going to be the next stage of 00:12:15.540 --> 00:12:17.509 align:start position:0% are going to be the next stage of Aztec's<00:12:16.079> platform<00:12:16.440> where<00:12:17.100> we'll<00:12:17.279> actually 00:12:17.509 --> 00:12:17.519 align:start position:0% Aztec's platform where we'll actually 00:12:17.519 --> 00:12:20.509 align:start position:0% Aztec's platform where we'll actually have<00:12:17.820> public<00:12:18.180> and<00:12:18.420> private<00:12:18.839> state<00:12:19.339> which<00:12:20.339> is 00:12:20.509 --> 00:12:20.519 align:start position:0% have public and private state which is 00:12:20.519 --> 00:12:22.430 align:start position:0% have public and private state which is has<00:12:21.000> its<00:12:21.360> own<00:12:21.420> challenges<00:12:21.839> which<00:12:22.200> you<00:12:22.320> can 00:12:22.430 --> 00:12:22.440 align:start position:0% has its own challenges which you can 00:12:22.440 --> 00:12:24.650 align:start position:0% has its own challenges which you can attend<00:12:22.680> Mike<00:12:22.860> Connors<00:12:23.279> talk<00:12:23.519> at<00:12:23.820> 2<00:12:24.000> 30<00:12:24.240> from 00:12:24.650 --> 00:12:24.660 align:start position:0% attend Mike Connors talk at 2 30 from 00:12:24.660 --> 00:12:26.150 align:start position:0% attend Mike Connors talk at 2 30 from Aztec<00:12:25.140> who's<00:12:25.260> going<00:12:25.440> to<00:12:25.500> be<00:12:25.560> discussing<00:12:25.980> that 00:12:26.150 --> 00:12:26.160 align:start position:0% Aztec who's going to be discussing that 00:12:26.160 --> 00:12:28.490 align:start position:0% Aztec who's going to be discussing that infrastructure<00:12:26.760> and<00:12:27.660> how<00:12:27.899> we<00:12:28.079> actually<00:12:28.260> are 00:12:28.490 --> 00:12:28.500 align:start position:0% infrastructure and how we actually are 00:12:28.500 --> 00:12:31.130 align:start position:0% infrastructure and how we actually are going<00:12:28.680> to<00:12:28.860> enable<00:12:29.100> Smart<00:12:29.760> contracts<00:12:30.240> in<00:12:30.360> Noir 00:12:31.130 --> 00:12:31.140 align:start position:0% going to enable Smart contracts in Noir 00:12:31.140 --> 00:12:34.310 align:start position:0% going to enable Smart contracts in Noir if<00:12:31.860> you<00:12:32.100> have<00:12:32.459> any<00:12:32.700> questions<00:12:33.180> uh<00:12:34.079> please 00:12:34.310 --> 00:12:34.320 align:start position:0% if you have any questions uh please 00:12:34.320 --> 00:12:36.920 align:start position:0% if you have any questions uh please shoot<00:12:34.680> and<00:12:35.519> thank<00:12:35.760> you 00:12:36.920 --> 00:12:36.930 align:start position:0% shoot and thank you 00:12:36.930 --> 00:12:39.170 align:start position:0% shoot and thank you [Applause] 00:12:39.170 --> 00:12:39.180 align:start position:0% [Applause] 00:12:39.180 --> 00:12:41.870 align:start position:0% [Applause] thank<00:12:39.660> you<00:12:39.779> so<00:12:39.899> much<00:12:40.019> Maxim<00:12:40.680> so<00:12:41.459> we<00:12:41.640> have<00:12:41.700> two 00:12:41.870 --> 00:12:41.880 align:start position:0% thank you so much Maxim so we have two 00:12:41.880 --> 00:12:43.250 align:start position:0% thank you so much Maxim so we have two volunteers 00:12:43.250 --> 00:12:43.260 align:start position:0% volunteers 00:12:43.260 --> 00:12:45.410 align:start position:0% volunteers there<00:12:43.740> you<00:12:43.860> go<00:12:43.980> this<00:12:44.639> is<00:12:44.639> our<00:12:44.880> balloon<00:12:45.300> two 00:12:45.410 --> 00:12:45.420 align:start position:0% there you go this is our balloon two 00:12:45.420 --> 00:12:46.370 align:start position:0% there you go this is our balloon two coming 00:12:46.370 --> 00:12:46.380 align:start position:0% coming 00:12:46.380 --> 00:12:50.269 align:start position:0% coming hey<00:12:46.980> good<00:12:47.820> afternoon<00:12:48.000> uh<00:12:48.899> very<00:12:49.200> impressive 00:12:50.269 --> 00:12:50.279 align:start position:0% hey good afternoon uh very impressive 00:12:50.279 --> 00:12:52.490 align:start position:0% hey good afternoon uh very impressive um<00:12:50.399> right<00:12:50.940> now<00:12:51.120> how<00:12:51.420> does<00:12:51.600> the<00:12:51.839> how<00:12:52.139> does<00:12:52.260> your 00:12:52.490 --> 00:12:52.500 align:start position:0% um right now how does the how does your 00:12:52.500 --> 00:12:54.410 align:start position:0% um right now how does the how does your tooling<00:12:52.860> work<00:12:53.040> for<00:12:53.220> this<00:12:53.399> uh<00:12:53.940> you<00:12:54.120> have<00:12:54.240> to 00:12:54.410 --> 00:12:54.420 align:start position:0% tooling work for this uh you have to 00:12:54.420 --> 00:12:57.650 align:start position:0% tooling work for this uh you have to compile<00:12:54.839> the<00:12:55.380> Noir<00:12:55.740> contract<00:12:56.540> and<00:12:57.540> then 00:12:57.650 --> 00:12:57.660 align:start position:0% compile the Noir contract and then 00:12:57.660 --> 00:13:01.490 align:start position:0% compile the Noir contract and then deploy<00:12:58.079> it<00:12:58.200> into<00:12:58.560> into<00:12:59.220> the<00:12:59.940> layer<00:13:00.779> two<00:13:00.959> into 00:13:01.490 --> 00:13:01.500 align:start position:0% deploy it into into the layer two into 00:13:01.500 --> 00:13:03.710 align:start position:0% deploy it into into the layer two into the<00:13:01.800> layer<00:13:02.100> two<00:13:02.220> or<00:13:02.519> the<00:13:02.579> layer<00:13:02.940> two<00:13:03.120> test<00:13:03.480> net 00:13:03.710 --> 00:13:03.720 align:start position:0% the layer two or the layer two test net 00:13:03.720 --> 00:13:06.590 align:start position:0% the layer two or the layer two test net or<00:13:04.019> something<00:13:04.260> not<00:13:04.860> right<00:13:05.040> now<00:13:05.220> that's 00:13:06.590 --> 00:13:06.600 align:start position:0% or something not right now that's 00:13:06.600 --> 00:13:08.750 align:start position:0% or something not right now that's that's<00:13:07.200> the<00:13:07.500> next<00:13:07.680> iteration<00:13:08.100> of<00:13:08.279> Aztec's 00:13:08.750 --> 00:13:08.760 align:start position:0% that's the next iteration of Aztec's 00:13:08.760 --> 00:13:10.550 align:start position:0% that's the next iteration of Aztec's platform<00:13:09.060> when<00:13:09.240> we<00:13:09.420> add<00:13:09.540> the<00:13:09.720> Noir<00:13:10.019> contracts 00:13:10.550 --> 00:13:10.560 align:start position:0% platform when we add the Noir contracts 00:13:10.560 --> 00:13:14.090 align:start position:0% platform when we add the Noir contracts this<00:13:11.220> is<00:13:11.339> a<00:13:11.519> purely<00:13:11.820> a<00:13:12.060> zkevm<00:13:13.019> DSL<00:13:13.680> right<00:13:13.920> now 00:13:14.090 --> 00:13:14.100 align:start position:0% this is a purely a zkevm DSL right now 00:13:14.100 --> 00:13:17.329 align:start position:0% this is a purely a zkevm DSL right now where<00:13:15.060> Aztec<00:13:15.959> can<00:13:16.079> generate<00:13:16.500> that<00:13:16.800> solidity 00:13:17.329 --> 00:13:17.339 align:start position:0% where Aztec can generate that solidity 00:13:17.339 --> 00:13:19.430 align:start position:0% where Aztec can generate that solidity verifier<00:13:17.940> and<00:13:18.540> you're<00:13:18.660> going<00:13:18.779> to<00:13:18.899> be<00:13:19.019> proving 00:13:19.430 --> 00:13:19.440 align:start position:0% verifier and you're going to be proving 00:13:19.440 --> 00:13:23.269 align:start position:0% verifier and you're going to be proving circuits<00:13:20.100> on<00:13:20.760> a<00:13:20.940> evm<00:13:21.420> platform<00:13:21.899> uh<00:13:22.860> you<00:13:23.100> can 00:13:23.269 --> 00:13:23.279 align:start position:0% circuits on a evm platform uh you can 00:13:23.279 --> 00:13:25.069 align:start position:0% circuits on a evm platform uh you can you<00:13:23.639> can<00:13:23.760> gener<00:13:24.000> like<00:13:24.360> I<00:13:24.480> showed<00:13:24.839> in<00:13:24.959> that 00:13:25.069 --> 00:13:25.079 align:start position:0% you can gener like I showed in that 00:13:25.079 --> 00:13:26.629 align:start position:0% you can gener like I showed in that example<00:13:25.320> you<00:13:25.560> can<00:13:25.620> compile<00:13:25.980> your<00:13:26.160> circuit<00:13:26.519> in 00:13:26.629 --> 00:13:26.639 align:start position:0% example you can compile your circuit in 00:13:26.639 --> 00:13:28.430 align:start position:0% example you can compile your circuit in typescript<00:13:26.940> but<00:13:27.660> you<00:13:27.779> can<00:13:27.899> also<00:13:28.079> use<00:13:28.200> our 00:13:28.430 --> 00:13:28.440 align:start position:0% typescript but you can also use our 00:13:28.440 --> 00:13:30.470 align:start position:0% typescript but you can also use our package<00:13:28.740> manager<00:13:29.160> which<00:13:29.579> I<00:13:29.880> briefly 00:13:30.470 --> 00:13:30.480 align:start position:0% package manager which I briefly 00:13:30.480 --> 00:13:32.389 align:start position:0% package manager which I briefly mentioned<00:13:30.899> to<00:13:31.320> generate<00:13:31.680> that<00:13:31.920> intermediate 00:13:32.389 --> 00:13:32.399 align:start position:0% mentioned to generate that intermediate 00:13:32.399 --> 00:13:34.250 align:start position:0% mentioned to generate that intermediate representation<00:13:32.940> that<00:13:33.720> intermediate 00:13:34.250 --> 00:13:34.260 align:start position:0% representation that intermediate 00:13:34.260 --> 00:13:35.990 align:start position:0% representation that intermediate representation<00:13:34.800> can<00:13:35.160> be<00:13:35.279> used<00:13:35.459> the<00:13:35.700> same<00:13:35.820> way 00:13:35.990 --> 00:13:36.000 align:start position:0% representation can be used the same way 00:13:36.000 --> 00:13:38.389 align:start position:0% representation can be used the same way that<00:13:36.420> that<00:13:36.600> that<00:13:37.200> it<00:13:37.500> was<00:13:37.620> used<00:13:37.740> there<00:13:37.980> you 00:13:38.389 --> 00:13:38.399 align:start position:0% that that that it was used there you 00:13:38.399 --> 00:13:40.370 align:start position:0% that that that it was used there you just<00:13:38.639> have<00:13:39.180> to<00:13:39.300> read<00:13:39.420> it<00:13:39.660> you're<00:13:39.959> reading<00:13:40.260> it 00:13:40.370 --> 00:13:40.380 align:start position:0% just have to read it you're reading it 00:13:40.380 --> 00:13:43.610 align:start position:0% just have to read it you're reading it in<00:13:40.500> from<00:13:40.680> file<00:13:41.040> using<00:13:42.000> our<00:13:42.360> same<00:13:42.839> our<00:13:43.200> wrapper 00:13:43.610 --> 00:13:43.620 align:start position:0% in from file using our same our wrapper 00:13:43.620 --> 00:13:45.829 align:start position:0% in from file using our same our wrapper method<00:13:43.920> so<00:13:44.100> you<00:13:44.220> don't<00:13:44.339> have<00:13:44.519> to<00:13:45.180> do<00:13:45.660> anything 00:13:45.829 --> 00:13:45.839 align:start position:0% method so you don't have to do anything 00:13:45.839 --> 00:13:47.750 align:start position:0% method so you don't have to do anything extra<00:13:46.260> for<00:13:46.560> serialization<00:13:47.160> that's<00:13:47.399> handled 00:13:47.750 --> 00:13:47.760 align:start position:0% extra for serialization that's handled 00:13:47.760 --> 00:13:50.269 align:start position:0% extra for serialization that's handled that's<00:13:48.120> handled<00:13:48.420> by<00:13:48.660> our<00:13:48.899> wrapper<00:13:49.620> yeah<00:13:50.040> right 00:13:50.269 --> 00:13:50.279 align:start position:0% that's handled by our wrapper yeah right 00:13:50.279 --> 00:13:52.490 align:start position:0% that's handled by our wrapper yeah right now<00:13:50.459> but<00:13:50.760> you<00:13:51.120> can<00:13:51.240> also<00:13:51.540> you<00:13:51.899> know<00:13:51.959> ver<00:13:52.139> you 00:13:52.490 --> 00:13:52.500 align:start position:0% now but you can also you know ver you 00:13:52.500 --> 00:13:54.230 align:start position:0% now but you can also you know ver you can<00:13:52.620> verify<00:13:52.920> without<00:13:53.100> the<00:13:53.339> evm<00:13:53.700> as<00:13:53.880> well<00:13:54.000> you 00:13:54.230 --> 00:13:54.240 align:start position:0% can verify without the evm as well you 00:13:54.240 --> 00:13:56.990 align:start position:0% can verify without the evm as well you can<00:13:54.300> just<00:13:54.420> verify<00:13:54.959> using<00:13:55.620> typescript<00:13:56.040> and<00:13:56.820> you 00:13:56.990 --> 00:13:57.000 align:start position:0% can just verify using typescript and you 00:13:57.000 --> 00:13:59.090 align:start position:0% can just verify using typescript and you don't<00:13:57.120> have<00:13:57.300> to<00:13:57.480> necessarily<00:13:57.959> have<00:13:58.380> a 00:13:59.090 --> 00:13:59.100 align:start position:0% don't have to necessarily have a 00:13:59.100 --> 00:14:01.490 align:start position:0% don't have to necessarily have a verification<00:13:59.600> using<00:14:00.600> a<00:14:00.720> solidity<00:14:01.139> contract 00:14:01.490 --> 00:14:01.500 align:start position:0% verification using a solidity contract 00:14:01.500 --> 00:14:03.769 align:start position:0% verification using a solidity contract that<00:14:01.680> depends<00:14:01.980> on<00:14:02.100> your<00:14:02.279> needs<00:14:02.579> but<00:14:03.300> a<00:14:03.600> lot<00:14:03.720> of 00:14:03.769 --> 00:14:03.779 align:start position:0% that depends on your needs but a lot of 00:14:03.779 --> 00:14:05.449 align:start position:0% that depends on your needs but a lot of people<00:14:03.899> like<00:14:04.139> to<00:14:04.320> have<00:14:04.500> that<00:14:04.800> autonomous 00:14:05.449 --> 00:14:05.459 align:start position:0% people like to have that autonomous 00:14:05.459 --> 00:14:07.009 align:start position:0% people like to have that autonomous execution 00:14:07.009 --> 00:14:07.019 align:start position:0% execution 00:14:07.019 --> 00:14:09.829 align:start position:0% execution we<00:14:07.500> have<00:14:07.620> time<00:14:07.800> for<00:14:08.040> more<00:14:08.279> questions 00:14:09.829 --> 00:14:09.839 align:start position:0% we have time for more questions 00:14:09.839 --> 00:14:12.710 align:start position:0% we have time for more questions one<00:14:10.320> over<00:14:10.560> there<00:14:10.920> in<00:14:11.339> the<00:14:11.519> left<00:14:11.700> side<00:14:12.120> then<00:14:12.540> we 00:14:12.710 --> 00:14:12.720 align:start position:0% one over there in the left side then we 00:14:12.720 --> 00:14:15.290 align:start position:0% one over there in the left side then we have<00:14:12.899> two<00:14:13.200> more<00:14:13.560> here 00:14:15.290 --> 00:14:15.300 align:start position:0% have two more here 00:14:15.300 --> 00:14:18.590 align:start position:0% have two more here hey<00:14:15.959> hi<00:14:16.200> uh<00:14:16.620> it<00:14:16.740> was<00:14:16.860> amazing<00:14:17.279> uh<00:14:18.060> I<00:14:18.240> wanted<00:14:18.360> to 00:14:18.590 --> 00:14:18.600 align:start position:0% hey hi uh it was amazing uh I wanted to 00:14:18.600 --> 00:14:21.230 align:start position:0% hey hi uh it was amazing uh I wanted to ask<00:14:18.779> let's<00:14:19.139> say<00:14:19.380> as<00:14:19.980> a<00:14:20.160> developer<00:14:20.519> I<00:14:20.880> have<00:14:21.060> the 00:14:21.230 --> 00:14:21.240 align:start position:0% ask let's say as a developer I have the 00:14:21.240 --> 00:14:24.710 align:start position:0% ask let's say as a developer I have the choice<00:14:21.480> between<00:14:21.839> sarcom<00:14:22.500> and<00:14:22.860> Noir<00:14:23.220> now<00:14:23.720> both 00:14:24.710 --> 00:14:24.720 align:start position:0% choice between sarcom and Noir now both 00:14:24.720 --> 00:14:28.009 align:start position:0% choice between sarcom and Noir now both as<00:14:25.139> an<00:14:25.320> end<00:14:25.500> user<00:14:25.920> feature<00:14:26.760> provide<00:14:27.240> proof 00:14:28.009 --> 00:14:28.019 align:start position:0% as an end user feature provide proof 00:14:28.019 --> 00:14:30.110 align:start position:0% as an end user feature provide proof systems<00:14:28.380> with<00:14:28.560> Planck<00:14:28.980> and<00:14:29.040> growth<00:14:29.339> 16.<00:14:29.880> it's 00:14:30.110 --> 00:14:30.120 align:start position:0% systems with Planck and growth 16. it's 00:14:30.120 --> 00:14:32.449 align:start position:0% systems with Planck and growth 16. it's exactly<00:14:30.600> the<00:14:30.779> same<00:14:30.899> value<00:14:31.139> proposition<00:14:31.740> so 00:14:32.449 --> 00:14:32.459 align:start position:0% exactly the same value proposition so 00:14:32.459 --> 00:14:35.930 align:start position:0% exactly the same value proposition so why<00:14:32.700> would<00:14:32.940> you<00:14:33.120> say<00:14:33.420> that<00:14:34.399> uh<00:14:35.399> we<00:14:35.760> should 00:14:35.930 --> 00:14:35.940 align:start position:0% why would you say that uh we should 00:14:35.940 --> 00:14:37.730 align:start position:0% why would you say that uh we should experiment<00:14:36.480> with<00:14:36.720> Noir<00:14:37.139> instead<00:14:37.500> of<00:14:37.560> just 00:14:37.730 --> 00:14:37.740 align:start position:0% experiment with Noir instead of just 00:14:37.740 --> 00:14:39.889 align:start position:0% experiment with Noir instead of just going<00:14:37.920> with<00:14:38.220> sarcom<00:14:38.639> sorry<00:14:39.300> to<00:14:39.480> put<00:14:39.600> you<00:14:39.720> in<00:14:39.779> a 00:14:39.889 --> 00:14:39.899 align:start position:0% going with sarcom sorry to put you in a 00:14:39.899 --> 00:14:42.110 align:start position:0% going with sarcom sorry to put you in a position<00:14:40.019> no<00:14:40.260> no<00:14:40.320> it's<00:14:40.560> okay<00:14:40.740> uh<00:14:41.519> they<00:14:42.000> do 00:14:42.110 --> 00:14:42.120 align:start position:0% position no no it's okay uh they do 00:14:42.120 --> 00:14:44.210 align:start position:0% position no no it's okay uh they do serve<00:14:42.420> slightly<00:14:42.720> different<00:14:42.959> use<00:14:43.920> cases 00:14:44.210 --> 00:14:44.220 align:start position:0% serve slightly different use cases 00:14:44.220 --> 00:14:45.650 align:start position:0% serve slightly different use cases circum<00:14:44.760> is<00:14:44.880> definitely<00:14:45.120> a<00:14:45.240> much<00:14:45.360> more<00:14:45.480> low 00:14:45.650 --> 00:14:45.660 align:start position:0% circum is definitely a much more low 00:14:45.660 --> 00:14:47.689 align:start position:0% circum is definitely a much more low level<00:14:45.899> you're<00:14:46.740> going<00:14:46.920> to<00:14:47.040> have<00:14:47.160> to<00:14:47.399> be 00:14:47.689 --> 00:14:47.699 align:start position:0% level you're going to have to be 00:14:47.699 --> 00:14:49.490 align:start position:0% level you're going to have to be specifying<00:14:48.300> a<00:14:48.839> lot<00:14:48.899> of<00:14:49.019> the<00:14:49.139> constraints 00:14:49.490 --> 00:14:49.500 align:start position:0% specifying a lot of the constraints 00:14:49.500 --> 00:14:52.310 align:start position:0% specifying a lot of the constraints individually<00:14:50.040> while<00:14:50.820> in<00:14:51.060> the<00:14:51.240> language<00:14:51.420> we 00:14:52.310 --> 00:14:52.320 align:start position:0% individually while in the language we 00:14:52.320 --> 00:14:54.829 align:start position:0% individually while in the language we specify<00:14:52.740> those<00:14:52.920> constraints<00:14:53.399> for<00:14:53.639> you<00:14:53.839> a 00:14:54.829 --> 00:14:54.839 align:start position:0% specify those constraints for you a 00:14:54.839 --> 00:14:56.269 align:start position:0% specify those constraints for you a basic<00:14:55.139> example<00:14:55.440> there<00:14:55.620> when<00:14:55.860> I<00:14:55.980> talked<00:14:56.160> about 00:14:56.269 --> 00:14:56.279 align:start position:0% basic example there when I talked about 00:14:56.279 --> 00:14:58.850 align:start position:0% basic example there when I talked about if<00:14:56.519> statements<00:14:57.120> you<00:14:57.779> can<00:14:57.899> constrain<00:14:58.380> your 00:14:58.850 --> 00:14:58.860 align:start position:0% if statements you can constrain your 00:14:58.860 --> 00:15:01.610 align:start position:0% if statements you can constrain your your<00:14:59.399> on<00:15:00.300> if<00:15:00.540> statements<00:15:01.019> you<00:15:01.199> don't<00:15:01.320> have<00:15:01.500> to 00:15:01.610 --> 00:15:01.620 align:start position:0% your on if statements you don't have to 00:15:01.620 --> 00:15:04.430 align:start position:0% your on if statements you don't have to use<00:15:01.860> a<00:15:02.220> multiplexer<00:15:02.940> and<00:15:03.899> things<00:15:04.199> like<00:15:04.320> that 00:15:04.430 --> 00:15:04.440 align:start position:0% use a multiplexer and things like that 00:15:04.440 --> 00:15:05.750 align:start position:0% use a multiplexer and things like that that<00:15:04.620> make<00:15:04.860> it<00:15:04.980> just<00:15:05.160> easier<00:15:05.459> for<00:15:05.579> the 00:15:05.750 --> 00:15:05.760 align:start position:0% that make it just easier for the 00:15:05.760 --> 00:15:08.269 align:start position:0% that make it just easier for the developer<00:15:06.240> and<00:15:07.019> kind<00:15:07.260> of<00:15:07.380> lower<00:15:07.500> that<00:15:07.800> barrier 00:15:08.269 --> 00:15:08.279 align:start position:0% developer and kind of lower that barrier 00:15:08.279 --> 00:15:09.829 align:start position:0% developer and kind of lower that barrier from<00:15:08.579> someone<00:15:08.760> who's<00:15:09.000> maybe<00:15:09.180> moving<00:15:09.540> from 00:15:09.829 --> 00:15:09.839 align:start position:0% from someone who's maybe moving from 00:15:09.839 --> 00:15:13.069 align:start position:0% from someone who's maybe moving from who's<00:15:10.199> never<00:15:10.440> coded<00:15:10.800> ZK<00:15:11.100> circuits<00:15:11.579> before<00:15:12.079> and 00:15:13.069 --> 00:15:13.079 align:start position:0% who's never coded ZK circuits before and 00:15:13.079 --> 00:15:15.590 align:start position:0% who's never coded ZK circuits before and you<00:15:13.860> can<00:15:13.920> also<00:15:14.160> constrain<00:15:14.639> on<00:15:14.940> data<00:15:15.360> types 00:15:15.590 --> 00:15:15.600 align:start position:0% you can also constrain on data types 00:15:15.600 --> 00:15:17.569 align:start position:0% you can also constrain on data types outside<00:15:15.779> of<00:15:16.079> just<00:15:16.260> our<00:15:16.440> native<00:15:16.680> type<00:15:16.920> because 00:15:17.569 --> 00:15:17.579 align:start position:0% outside of just our native type because 00:15:17.579 --> 00:15:19.129 align:start position:0% outside of just our native type because they<00:15:17.940> everything<00:15:18.240> that<00:15:18.480> we<00:15:18.660> have<00:15:18.779> ultimately 00:15:19.129 --> 00:15:19.139 align:start position:0% they everything that we have ultimately 00:15:19.139 --> 00:15:22.310 align:start position:0% they everything that we have ultimately translates<00:15:19.680> to<00:15:20.100> that<00:15:20.279> and<00:15:21.120> we<00:15:21.360> do<00:15:21.480> have 00:15:22.310 --> 00:15:22.320 align:start position:0% translates to that and we do have 00:15:22.320 --> 00:15:26.210 align:start position:0% translates to that and we do have uh<00:15:23.579> I<00:15:24.180> know<00:15:24.300> you<00:15:24.779> can<00:15:25.019> currently<00:15:25.440> do<00:15:25.680> Planck 00:15:26.210 --> 00:15:26.220 align:start position:0% uh I know you can currently do Planck 00:15:26.220 --> 00:15:29.329 align:start position:0% uh I know you can currently do Planck but<00:15:26.820> I<00:15:27.060> believe<00:15:27.180> right<00:15:27.720> now<00:15:27.920> Noir<00:15:28.920> is<00:15:29.100> the<00:15:29.220> only 00:15:29.329 --> 00:15:29.339 align:start position:0% but I believe right now Noir is the only 00:15:29.339 --> 00:15:31.670 align:start position:0% but I believe right now Noir is the only language<00:15:29.579> that<00:15:29.940> actually<00:15:30.120> has<00:15:30.600> truly<00:15:31.260> fully 00:15:31.670 --> 00:15:31.680 align:start position:0% language that actually has truly fully 00:15:31.680 --> 00:15:34.310 align:start position:0% language that actually has truly fully integrated<00:15:32.220> Black<00:15:32.519> Box<00:15:32.760> functionality<00:15:33.480> where 00:15:34.310 --> 00:15:34.320 align:start position:0% integrated Black Box functionality where 00:15:34.320 --> 00:15:36.530 align:start position:0% integrated Black Box functionality where the<00:15:34.560> proving<00:15:34.800> system<00:15:35.040> is<00:15:35.399> specifying<00:15:36.000> the 00:15:36.530 --> 00:15:36.540 align:start position:0% the proving system is specifying the 00:15:36.540 --> 00:15:38.870 align:start position:0% the proving system is specifying the custom<00:15:36.720> Gates<00:15:37.139> and<00:15:37.500> making<00:15:37.740> those<00:15:38.399> functions 00:15:38.870 --> 00:15:38.880 align:start position:0% custom Gates and making those functions 00:15:38.880 --> 00:15:40.430 align:start position:0% custom Gates and making those functions faster 00:15:40.430 --> 00:15:40.440 align:start position:0% faster 00:15:40.440 --> 00:15:41.810 align:start position:0% faster hi 00:15:41.810 --> 00:15:41.820 align:start position:0% hi 00:15:41.820 --> 00:15:44.870 align:start position:0% hi um<00:15:41.940> why<00:15:42.660> base<00:15:42.899> Noir<00:15:43.500> off<00:15:43.860> rust<00:15:44.220> are<00:15:44.699> there 00:15:44.870 --> 00:15:44.880 align:start position:0% um why base Noir off rust are there 00:15:44.880 --> 00:15:46.670 align:start position:0% um why base Noir off rust are there certain<00:15:45.060> properties<00:15:45.480> of<00:15:45.660> rust<00:15:45.959> that<00:15:46.260> make<00:15:46.440> it 00:15:46.670 --> 00:15:46.680 align:start position:0% certain properties of rust that make it 00:15:46.680 --> 00:15:48.769 align:start position:0% certain properties of rust that make it you<00:15:46.980> know<00:15:47.040> a<00:15:47.279> better<00:15:47.399> language<00:15:47.699> for<00:15:48.060> this<00:15:48.240> well 00:15:48.769 --> 00:15:48.779 align:start position:0% you know a better language for this well 00:15:48.779 --> 00:15:50.569 align:start position:0% you know a better language for this well we<00:15:49.079> want<00:15:49.199> to<00:15:49.380> one<00:15:49.800> of<00:15:49.920> the<00:15:49.980> main<00:15:50.040> focuses<00:15:50.459> of 00:15:50.569 --> 00:15:50.579 align:start position:0% we want to one of the main focuses of 00:15:50.579 --> 00:15:54.050 align:start position:0% we want to one of the main focuses of noir's<00:15:51.060> safety<00:15:51.420> and<00:15:52.199> Noah<00:15:53.100> and<00:15:53.459> rust<00:15:53.699> that 00:15:54.050 --> 00:15:54.060 align:start position:0% noir's safety and Noah and rust that 00:15:54.060 --> 00:15:56.449 align:start position:0% noir's safety and Noah and rust that same<00:15:54.240> thing<00:15:54.360> in<00:15:54.480> Russ<00:15:54.720> right<00:15:55.139> and<00:15:55.860> rust<00:15:56.220> is 00:15:56.449 --> 00:15:56.459 align:start position:0% same thing in Russ right and rust is 00:15:56.459 --> 00:15:59.269 align:start position:0% same thing in Russ right and rust is also<00:15:57.019> just<00:15:58.019> a<00:15:58.260> nice<00:15:58.320> language 00:15:59.269 --> 00:15:59.279 align:start position:0% also just a nice language 00:15:59.279 --> 00:16:02.090 align:start position:0% also just a nice language uh<00:15:59.820> thanks<00:16:00.120> a<00:16:00.360> lot<00:16:00.480> for<00:16:00.600> for<00:16:00.839> the<00:16:01.019> talk<00:16:01.139> uh<00:16:01.920> I 00:16:02.090 --> 00:16:02.100 align:start position:0% uh thanks a lot for for the talk uh I 00:16:02.100 --> 00:16:03.530 align:start position:0% uh thanks a lot for for the talk uh I was<00:16:02.220> wondering<00:16:02.459> do<00:16:02.639> you<00:16:02.820> have<00:16:02.940> some<00:16:03.120> tools 00:16:03.530 --> 00:16:03.540 align:start position:0% was wondering do you have some tools 00:16:03.540 --> 00:16:05.629 align:start position:0% was wondering do you have some tools where<00:16:03.839> am<00:16:03.959> I<00:16:04.079> looking<00:16:04.199> sorry<00:16:04.440> I'm<00:16:04.920> here<00:16:05.040> oh<00:16:05.339> hey 00:16:05.629 --> 00:16:05.639 align:start position:0% where am I looking sorry I'm here oh hey 00:16:05.639 --> 00:16:07.970 align:start position:0% where am I looking sorry I'm here oh hey hello<00:16:05.940> uh<00:16:06.660> thanks<00:16:06.899> for<00:16:07.139> the<00:16:07.199> for<00:16:07.440> the<00:16:07.560> talk<00:16:07.680> uh 00:16:07.970 --> 00:16:07.980 align:start position:0% hello uh thanks for the for the talk uh 00:16:07.980 --> 00:16:10.129 align:start position:0% hello uh thanks for the for the talk uh do<00:16:08.220> you<00:16:08.339> have<00:16:08.399> some<00:16:08.579> tools<00:16:08.940> for<00:16:09.240> uh<00:16:09.779> testing 00:16:10.129 --> 00:16:10.139 align:start position:0% do you have some tools for uh testing 00:16:10.139 --> 00:16:13.189 align:start position:0% do you have some tools for uh testing the<00:16:10.320> logic<00:16:10.620> of<00:16:10.740> the<00:16:10.860> circuits<00:16:11.779> uh<00:16:12.779> right<00:16:13.019> now 00:16:13.189 --> 00:16:13.199 align:start position:0% the logic of the circuits uh right now 00:16:13.199 --> 00:16:14.930 align:start position:0% the logic of the circuits uh right now it's<00:16:13.680> essentially<00:16:14.040> you're<00:16:14.519> gonna<00:16:14.639> have<00:16:14.820> to 00:16:14.930 --> 00:16:14.940 align:start position:0% it's essentially you're gonna have to 00:16:14.940 --> 00:16:17.269 align:start position:0% it's essentially you're gonna have to write<00:16:15.060> your<00:16:15.300> tests<00:16:15.720> in<00:16:16.019> typescript<00:16:16.500> we<00:16:17.040> hope 00:16:17.269 --> 00:16:17.279 align:start position:0% write your tests in typescript we hope 00:16:17.279 --> 00:16:19.009 align:start position:0% write your tests in typescript we hope to<00:16:17.399> add<00:16:17.579> debugging<00:16:18.120> tools<00:16:18.420> that's<00:16:18.600> one<00:16:18.839> of<00:16:18.959> the 00:16:19.009 --> 00:16:19.019 align:start position:0% to add debugging tools that's one of the 00:16:19.019 --> 00:16:20.810 align:start position:0% to add debugging tools that's one of the main<00:16:19.139> things<00:16:19.380> that<00:16:20.160> need<00:16:20.279> to<00:16:20.399> be<00:16:20.519> added<00:16:20.760> to 00:16:20.810 --> 00:16:20.820 align:start position:0% main things that need to be added to 00:16:20.820 --> 00:16:23.569 align:start position:0% main things that need to be added to make<00:16:21.000> the<00:16:21.120> tooling<00:16:21.420> more<00:16:21.600> effective<00:16:22.220> uh<00:16:23.220> yeah 00:16:23.569 --> 00:16:23.579 align:start position:0% make the tooling more effective uh yeah 00:16:23.579 --> 00:16:25.370 align:start position:0% make the tooling more effective uh yeah you're<00:16:23.820> gonna<00:16:23.940> have<00:16:24.120> to<00:16:24.420> essentially<00:16:24.779> test<00:16:25.199> it 00:16:25.370 --> 00:16:25.380 align:start position:0% you're gonna have to essentially test it 00:16:25.380 --> 00:16:26.750 align:start position:0% you're gonna have to essentially test it either<00:16:25.500> in<00:16:25.680> typescript<00:16:25.980> you<00:16:26.220> can<00:16:26.339> test<00:16:26.459> it<00:16:26.639> in 00:16:26.750 --> 00:16:26.760 align:start position:0% either in typescript you can test it in 00:16:26.760 --> 00:16:29.150 align:start position:0% either in typescript you can test it in Rust<00:16:27.060> too<00:16:27.240> and<00:16:27.480> use<00:16:27.600> the<00:16:27.779> nargo<00:16:28.199> package 00:16:29.150 --> 00:16:29.160 align:start position:0% Rust too and use the nargo package 00:16:29.160 --> 00:16:31.490 align:start position:0% Rust too and use the nargo package manager<00:16:29.639> that's<00:16:30.480> up<00:16:30.660> to<00:16:30.779> you<00:16:30.899> but<00:16:31.199> I<00:16:31.380> only 00:16:31.490 --> 00:16:31.500 align:start position:0% manager that's up to you but I only 00:16:31.500 --> 00:16:33.170 align:start position:0% manager that's up to you but I only highlighted<00:16:31.980> typescript<00:16:32.399> here<00:16:32.639> because<00:16:32.880> most 00:16:33.170 --> 00:16:33.180 align:start position:0% highlighted typescript here because most 00:16:33.180 --> 00:16:34.790 align:start position:0% highlighted typescript here because most contract<00:16:33.899> developers<00:16:34.320> are<00:16:34.500> probably<00:16:34.680> going 00:16:34.790 --> 00:16:34.800 align:start position:0% contract developers are probably going 00:16:34.800 --> 00:16:36.170 align:start position:0% contract developers are probably going to<00:16:34.920> lean<00:16:35.100> towards<00:16:35.339> that 00:16:36.170 --> 00:16:36.180 align:start position:0% to lean towards that 00:16:36.180 --> 00:16:39.410 align:start position:0% to lean towards that okay<00:16:36.660> thanks<00:16:37.019> we<00:16:37.860> still<00:16:38.100> have<00:16:38.279> time<00:16:38.519> for<00:16:39.000> more 00:16:39.410 --> 00:16:39.420 align:start position:0% okay thanks we still have time for more 00:16:39.420 --> 00:16:41.810 align:start position:0% okay thanks we still have time for more questions<00:16:39.660> five<00:16:40.320> minutes<00:16:40.560> more<00:16:40.920> there<00:16:41.519> you<00:16:41.699> go 00:16:41.810 --> 00:16:41.820 align:start position:0% questions five minutes more there you go 00:16:41.820 --> 00:16:43.129 align:start position:0% questions five minutes more there you go on<00:16:42.120> the<00:16:42.240> right 00:16:43.129 --> 00:16:43.139 align:start position:0% on the right 00:16:43.139 --> 00:16:45.470 align:start position:0% on the right thank<00:16:43.680> you<00:16:43.800> uh<00:16:44.399> just<00:16:44.639> a<00:16:44.699> quick<00:16:44.820> question<00:16:45.060> on 00:16:45.470 --> 00:16:45.480 align:start position:0% thank you uh just a quick question on 00:16:45.480 --> 00:16:49.129 align:start position:0% thank you uh just a quick question on the<00:16:45.720> first<00:16:46.019> uh<00:16:46.500> like<00:16:47.040> code<00:16:47.399> sample<00:16:48.060> you<00:16:48.420> had<00:16:48.540> uh 00:16:49.129 --> 00:16:49.139 align:start position:0% the first uh like code sample you had uh 00:16:49.139 --> 00:16:51.410 align:start position:0% the first uh like code sample you had uh I<00:16:49.440> could<00:16:49.500> see<00:16:49.680> the<00:16:49.800> STD<00:16:50.279> the<00:16:50.399> STD<00:16:50.759> package<00:16:51.120> was 00:16:51.410 --> 00:16:51.420 align:start position:0% I could see the STD the STD package was 00:16:51.420 --> 00:16:54.110 align:start position:0% I could see the STD the STD package was under<00:16:51.660> a<00:16:52.019> depth<00:16:52.500> uh<00:16:53.100> namespace<00:16:53.639> and<00:16:53.880> I<00:16:54.000> was 00:16:54.110 --> 00:16:54.120 align:start position:0% under a depth uh namespace and I was 00:16:54.120 --> 00:16:55.610 align:start position:0% under a depth uh namespace and I was wondering<00:16:54.420> where<00:16:54.660> that<00:16:54.899> is 00:16:55.610 --> 00:16:55.620 align:start position:0% wondering where that is 00:16:55.620 --> 00:16:58.189 align:start position:0% wondering where that is that's<00:16:55.980> just<00:16:56.220> our<00:16:56.519> I<00:16:56.759> guess<00:16:56.880> native<00:16:57.480> kind<00:16:58.079> of 00:16:58.189 --> 00:16:58.199 align:start position:0% that's just our I guess native kind of 00:16:58.199 --> 00:16:59.870 align:start position:0% that's just our I guess native kind of dependencies<00:16:58.740> and<00:16:59.220> that's<00:16:59.339> how<00:16:59.519> we<00:16:59.639> do<00:16:59.820> it 00:16:59.870 --> 00:16:59.880 align:start position:0% dependencies and that's how we do it 00:16:59.880 --> 00:17:03.110 align:start position:0% dependencies and that's how we do it like<00:17:00.120> we<00:17:00.420> you<00:17:00.899> can<00:17:01.079> also<00:17:01.320> import<00:17:01.560> from<00:17:02.459> from 00:17:03.110 --> 00:17:03.120 align:start position:0% like we you can also import from from 00:17:03.120 --> 00:17:05.210 align:start position:0% like we you can also import from from GitHub<00:17:03.660> or<00:17:04.140> you<00:17:04.260> can<00:17:04.380> have<00:17:04.500> modules<00:17:04.919> as<00:17:05.100> you 00:17:05.210 --> 00:17:05.220 align:start position:0% GitHub or you can have modules as you 00:17:05.220 --> 00:17:07.669 align:start position:0% GitHub or you can have modules as you would<00:17:05.400> normally<00:17:05.939> in<00:17:06.120> Rust<00:17:06.360> within<00:17:06.900> your<00:17:07.199> uh 00:17:07.669 --> 00:17:07.679 align:start position:0% would normally in Rust within your uh 00:17:07.679 --> 00:17:11.090 align:start position:0% would normally in Rust within your uh where<00:17:07.919> it<00:17:08.100> would<00:17:08.220> be<00:17:08.339> like<00:17:08.579> mod<00:17:09.360> something<00:17:10.100> and 00:17:11.090 --> 00:17:11.100 align:start position:0% where it would be like mod something and 00:17:11.100 --> 00:17:13.429 align:start position:0% where it would be like mod something and you<00:17:11.339> can<00:17:11.400> also<00:17:11.699> import<00:17:12.179> packages<00:17:12.900> from<00:17:13.140> within 00:17:13.429 --> 00:17:13.439 align:start position:0% you can also import packages from within 00:17:13.439 --> 00:17:14.750 align:start position:0% you can also import packages from within a<00:17:13.559> crate<00:17:13.799> as<00:17:13.980> well<00:17:14.100> where<00:17:14.280> it<00:17:14.400> would<00:17:14.520> be<00:17:14.640> like 00:17:14.750 --> 00:17:14.760 align:start position:0% a crate as well where it would be like 00:17:14.760 --> 00:17:17.329 align:start position:0% a crate as well where it would be like create<00:17:15.000> this<00:17:15.839> uh<00:17:16.620> and<00:17:16.799> that<00:17:16.919> would<00:17:17.040> be<00:17:17.160> the 00:17:17.329 --> 00:17:17.339 align:start position:0% create this uh and that would be the 00:17:17.339 --> 00:17:19.309 align:start position:0% create this uh and that would be the import<00:17:17.459> that's<00:17:18.299> just<00:17:18.480> how<00:17:18.600> we<00:17:18.720> import<00:17:18.900> our 00:17:19.309 --> 00:17:19.319 align:start position:0% import that's just how we import our 00:17:19.319 --> 00:17:20.870 align:start position:0% import that's just how we import our standard<00:17:20.040> Library 00:17:20.870 --> 00:17:20.880 align:start position:0% standard Library 00:17:20.880 --> 00:17:23.630 align:start position:0% standard Library yeah<00:17:21.360> like<00:17:21.540> rust<00:17:21.839> crates<00:17:22.140> uh<00:17:22.559> our<00:17:22.799> our<00:17:23.220> nargo 00:17:23.630 --> 00:17:23.640 align:start position:0% yeah like rust crates uh our our nargo 00:17:23.640 --> 00:17:26.090 align:start position:0% yeah like rust crates uh our our nargo kind<00:17:24.059> of<00:17:24.179> it<00:17:24.419> it's<00:17:24.839> not<00:17:25.020> like<00:17:25.260> a<00:17:25.380> copy<00:17:25.679> of<00:17:25.799> cargo 00:17:26.090 --> 00:17:26.100 align:start position:0% kind of it it's not like a copy of cargo 00:17:26.100 --> 00:17:28.429 align:start position:0% kind of it it's not like a copy of cargo but<00:17:26.339> it<00:17:27.120> kind<00:17:27.480> of<00:17:27.600> mocks<00:17:27.900> that<00:17:28.020> functionality 00:17:28.429 --> 00:17:28.439 align:start position:0% but it kind of mocks that functionality 00:17:28.439 --> 00:17:31.310 align:start position:0% but it kind of mocks that functionality with<00:17:28.740> crates<00:17:29.040> and<00:17:29.520> modules<00:17:29.940> so<00:17:30.540> you<00:17:30.780> can<00:17:30.900> have 00:17:31.310 --> 00:17:31.320 align:start position:0% with crates and modules so you can have 00:17:31.320 --> 00:17:33.590 align:start position:0% with crates and modules so you can have you<00:17:31.919> can<00:17:32.040> import<00:17:32.280> modules<00:17:33.000> from<00:17:33.179> within<00:17:33.480> your 00:17:33.590 --> 00:17:33.600 align:start position:0% you can import modules from within your 00:17:33.600 --> 00:17:36.049 align:start position:0% you can import modules from within your crate<00:17:33.900> using<00:17:34.320> use<00:17:34.559> crate<00:17:34.980> and<00:17:35.460> then<00:17:35.580> whatever 00:17:36.049 --> 00:17:36.059 align:start position:0% crate using use crate and then whatever 00:17:36.059 --> 00:17:37.549 align:start position:0% crate using use crate and then whatever else<00:17:36.360> you'd<00:17:36.660> like 00:17:37.549 --> 00:17:37.559 align:start position:0% else you'd like 00:17:37.559 --> 00:17:40.669 align:start position:0% else you'd like it's<00:17:37.860> a<00:17:38.400> very<00:17:38.700> nice<00:17:38.880> talk<00:17:39.179> uh<00:17:40.080> in<00:17:40.260> the<00:17:40.440> next 00:17:40.669 --> 00:17:40.679 align:start position:0% it's a very nice talk uh in the next 00:17:40.679 --> 00:17:43.789 align:start position:0% it's a very nice talk uh in the next phase<00:17:40.919> of<00:17:41.160> of<00:17:41.640> Aztec<00:17:42.299> 3<00:17:42.480> uh<00:17:43.320> can<00:17:43.559> you<00:17:43.679> talk 00:17:43.789 --> 00:17:43.799 align:start position:0% phase of of Aztec 3 uh can you talk 00:17:43.799 --> 00:17:46.070 align:start position:0% phase of of Aztec 3 uh can you talk about<00:17:43.919> the<00:17:44.220> process<00:17:44.580> process<00:17:45.299> of<00:17:45.600> converting 00:17:46.070 --> 00:17:46.080 align:start position:0% about the process process of converting 00:17:46.080 --> 00:17:48.710 align:start position:0% about the process process of converting existing<00:17:46.620> circuits<00:17:47.100> to<00:17:47.340> Noir<00:17:47.880> what<00:17:48.539> do<00:17:48.660> you 00:17:48.710 --> 00:17:48.720 align:start position:0% existing circuits to Noir what do you 00:17:48.720 --> 00:17:49.909 align:start position:0% existing circuits to Noir what do you mean<00:17:48.780> existing<00:17:49.260> circuits<00:17:49.620> you<00:17:49.740> mean 00:17:49.909 --> 00:17:49.919 align:start position:0% mean existing circuits you mean 00:17:49.919 --> 00:17:53.510 align:start position:0% mean existing circuits you mean contracts<00:17:50.640> like<00:17:51.360> the<00:17:51.720> uh<00:17:52.440> so<00:17:52.559> in<00:17:52.799> Aztec<00:17:53.340> 3 00:17:53.510 --> 00:17:53.520 align:start position:0% contracts like the uh so in Aztec 3 00:17:53.520 --> 00:17:55.730 align:start position:0% contracts like the uh so in Aztec 3 you're<00:17:54.299> planning<00:17:54.600> on<00:17:54.720> converting<00:17:55.200> existing 00:17:55.730 --> 00:17:55.740 align:start position:0% you're planning on converting existing 00:17:55.740 --> 00:17:58.669 align:start position:0% you're planning on converting existing circuits<00:17:56.220> to<00:17:56.400> Noir<00:17:56.940> I<00:17:57.539> assume<00:17:57.960> so<00:17:58.380> that's 00:17:58.669 --> 00:17:58.679 align:start position:0% circuits to Noir I assume so that's 00:17:58.679 --> 00:18:00.169 align:start position:0% circuits to Noir I assume so that's actually<00:17:58.919> probably<00:17:59.400> you'd<00:17:59.820> want<00:17:59.940> to<00:18:00.000> go<00:18:00.120> to 00:18:00.169 --> 00:18:00.179 align:start position:0% actually probably you'd want to go to 00:18:00.179 --> 00:18:02.330 align:start position:0% actually probably you'd want to go to Mike's<00:18:00.480> talk<00:18:00.660> to<00:18:01.320> see<00:18:01.559> more<00:18:01.799> it's<00:18:02.100> very 00:18:02.330 --> 00:18:02.340 align:start position:0% Mike's talk to see more it's very 00:18:02.340 --> 00:18:04.970 align:start position:0% Mike's talk to see more it's very interesting<00:18:02.700> how<00:18:03.059> the<00:18:03.360> infrastructure<00:18:04.260> works 00:18:04.970 --> 00:18:04.980 align:start position:0% interesting how the infrastructure works 00:18:04.980 --> 00:18:07.669 align:start position:0% interesting how the infrastructure works essentially<00:18:05.820> though<00:18:06.660> each<00:18:07.080> function<00:18:07.380> in<00:18:07.559> the 00:18:07.669 --> 00:18:07.679 align:start position:0% essentially though each function in the 00:18:07.679 --> 00:18:09.169 align:start position:0% essentially though each function in the contract<00:18:07.919> is<00:18:08.100> going<00:18:08.280> to<00:18:08.340> be<00:18:08.400> a<00:18:08.580> circuit<00:18:08.880> but 00:18:09.169 --> 00:18:09.179 align:start position:0% contract is going to be a circuit but 00:18:09.179 --> 00:18:11.029 align:start position:0% contract is going to be a circuit but how<00:18:09.480> that<00:18:09.720> actually<00:18:09.960> gets<00:18:10.260> integrated<00:18:10.620> into 00:18:11.029 --> 00:18:11.039 align:start position:0% how that actually gets integrated into 00:18:11.039 --> 00:18:13.190 align:start position:0% how that actually gets integrated into the<00:18:11.700> system<00:18:11.880> you're<00:18:12.539> going<00:18:12.720> to<00:18:12.840> have<00:18:12.960> to 00:18:13.190 --> 00:18:13.200 align:start position:0% the system you're going to have to 00:18:13.200 --> 00:18:15.049 align:start position:0% the system you're going to have to attend<00:18:13.740> Mike's<00:18:14.100> talk<00:18:14.220> to<00:18:14.460> get<00:18:14.580> more<00:18:14.700> info<00:18:14.940> on 00:18:15.049 --> 00:18:15.059 align:start position:0% attend Mike's talk to get more info on 00:18:15.059 --> 00:18:16.850 align:start position:0% attend Mike's talk to get more info on that<00:18:15.240> it's<00:18:15.419> very<00:18:15.660> interesting<00:18:16.020> we<00:18:16.679> have 00:18:16.850 --> 00:18:16.860 align:start position:0% that it's very interesting we have 00:18:16.860 --> 00:18:18.590 align:start position:0% that it's very interesting we have someone<00:18:16.980> from<00:18:17.280> Team<00:18:17.520> here<00:18:17.760> as<00:18:18.000> well<00:18:18.120> if<00:18:18.419> you 00:18:18.590 --> 00:18:18.600 align:start position:0% someone from Team here as well if you 00:18:18.600 --> 00:18:21.049 align:start position:0% someone from Team here as well if you want<00:18:19.200> to<00:18:19.380> complement<00:18:19.860> anything<00:18:20.220> like<00:18:20.640> to<00:18:20.880> add 00:18:21.049 --> 00:18:21.059 align:start position:0% want to complement anything like to add 00:18:21.059 --> 00:18:24.230 align:start position:0% want to complement anything like to add on<00:18:21.539> top<00:18:21.660> of<00:18:21.840> the<00:18:21.900> conversation<00:18:22.320> hello<00:18:23.039> yeah<00:18:24.000> I 00:18:24.230 --> 00:18:24.240 align:start position:0% on top of the conversation hello yeah I 00:18:24.240 --> 00:18:26.930 align:start position:0% on top of the conversation hello yeah I just<00:18:24.419> want<00:18:24.660> to<00:18:24.840> ask<00:18:25.559> so<00:18:25.860> with<00:18:26.280> Aztec<00:18:26.760> free 00:18:26.930 --> 00:18:26.940 align:start position:0% just want to ask so with Aztec free 00:18:26.940 --> 00:18:29.510 align:start position:0% just want to ask so with Aztec free we're<00:18:27.419> not<00:18:27.600> actually<00:18:27.780> trying<00:18:28.140> to<00:18:28.260> be<00:18:28.380> ZK<00:18:28.860> evm 00:18:29.510 --> 00:18:29.520 align:start position:0% we're not actually trying to be ZK evm 00:18:29.520 --> 00:18:30.830 align:start position:0% we're not actually trying to be ZK evm compatible<00:18:29.940> right 00:18:30.830 --> 00:18:30.840 align:start position:0% compatible right 00:18:30.840 --> 00:18:33.650 align:start position:0% compatible right it's<00:18:31.380> a<00:18:31.740> separate<00:18:32.039> no<00:18:32.340> right 00:18:33.650 --> 00:18:33.660 align:start position:0% it's a separate no right 00:18:33.660 --> 00:18:35.450 align:start position:0% it's a separate no right yeah<00:18:33.720> just<00:18:34.200> making<00:18:34.440> sure 00:18:35.450 --> 00:18:35.460 align:start position:0% yeah just making sure 00:18:35.460 --> 00:18:39.590 align:start position:0% yeah just making sure cool<00:18:36.179> there's<00:18:36.660> one<00:18:36.960> more<00:18:37.340> over<00:18:38.340> there<00:18:38.640> this 00:18:39.590 --> 00:18:39.600 align:start position:0% cool there's one more over there this 00:18:39.600 --> 00:18:40.370 align:start position:0% cool there's one more over there this side 00:18:40.370 --> 00:18:40.380 align:start position:0% side 00:18:40.380 --> 00:18:42.950 align:start position:0% side oh<00:18:40.919> yeah<00:18:41.220> that<00:18:41.520> was<00:18:41.640> my<00:18:41.880> question<00:18:42.120> again 00:18:42.950 --> 00:18:42.960 align:start position:0% oh yeah that was my question again 00:18:42.960 --> 00:18:46.190 align:start position:0% oh yeah that was my question again um<00:18:43.080> that<00:18:43.440> was<00:18:43.679> he<00:18:43.980> said<00:18:44.220> he<00:18:44.640> was<00:18:44.760> he<00:18:45.020> they<00:18:46.020> made 00:18:46.190 --> 00:18:46.200 align:start position:0% um that was he said he was he they made 00:18:46.200 --> 00:18:48.110 align:start position:0% um that was he said he was he they made a<00:18:46.320> preamble<00:18:46.679> to<00:18:46.860> the<00:18:46.980> question<00:18:47.160> so<00:18:47.460> that<00:18:47.820> means 00:18:48.110 --> 00:18:48.120 align:start position:0% a preamble to the question so that means 00:18:48.120 --> 00:18:50.930 align:start position:0% a preamble to the question so that means that<00:18:48.299> Noir<00:18:48.780> the<00:18:49.260> since<00:18:49.799> Nora<00:18:50.400> is<00:18:50.520> going<00:18:50.700> to 00:18:50.930 --> 00:18:50.940 align:start position:0% that Noir the since Nora is going to 00:18:50.940 --> 00:18:54.049 align:start position:0% that Noir the since Nora is going to Target<00:18:51.120> to<00:18:51.419> EVMS<00:18:52.020> uh<00:18:52.860> Arctic<00:18:53.280> 3<00:18:53.460> is<00:18:53.700> not<00:18:53.880> going 00:18:54.049 --> 00:18:54.059 align:start position:0% Target to EVMS uh Arctic 3 is not going 00:18:54.059 --> 00:18:57.470 align:start position:0% Target to EVMS uh Arctic 3 is not going to<00:18:54.179> be<00:18:54.419> using<00:18:54.900> Noir<00:18:55.500> for<00:18:56.160> this<00:18:56.520> for<00:18:56.760> for<00:18:57.240> its 00:18:57.470 --> 00:18:57.480 align:start position:0% to be using Noir for this for for its 00:18:57.480 --> 00:18:59.870 align:start position:0% to be using Noir for this for for its inter<00:18:57.539> for<00:18:57.900> the<00:18:58.020> circuits<00:18:58.440> so<00:18:59.160> we're<00:18:59.640> going<00:18:59.760> to 00:18:59.870 --> 00:18:59.880 align:start position:0% inter for the circuits so we're going to 00:18:59.880 --> 00:19:01.490 align:start position:0% inter for the circuits so we're going to be using<00:19:00.120> Noir<00:19:00.419> for<00:19:00.600> circuits<00:19:00.960> but<00:19:01.080> you<00:19:01.380> don't 00:19:01.490 --> 00:19:01.500 align:start position:0% be using Noir for circuits but you don't 00:19:01.500 --> 00:19:03.770 align:start position:0% be using Noir for circuits but you don't necessarily<00:19:02.100> have<00:19:02.400> to<00:19:02.580> Target<00:19:02.940> the<00:19:03.179> evm<00:19:03.600> there 00:19:03.770 --> 00:19:03.780 align:start position:0% necessarily have to Target the evm there 00:19:03.780 --> 00:19:05.990 align:start position:0% necessarily have to Target the evm there we<00:19:04.140> just<00:19:04.380> Aztecs<00:19:05.160> backhand<00:19:05.460> does<00:19:05.640> allow<00:19:05.880> you 00:19:05.990 --> 00:19:06.000 align:start position:0% we just Aztecs backhand does allow you 00:19:06.000 --> 00:19:09.110 align:start position:0% we just Aztecs backhand does allow you to<00:19:06.360> compile<00:19:06.840> an<00:19:07.500> evm<00:19:07.980> verifier 00:19:09.110 --> 00:19:09.120 align:start position:0% to compile an evm verifier 00:19:09.120 --> 00:19:11.270 align:start position:0% to compile an evm verifier from<00:19:09.660> a<00:19:09.780> Noir<00:19:10.140> circuit<00:19:10.559> and<00:19:11.100> that 00:19:11.270 --> 00:19:11.280 align:start position:0% from a Noir circuit and that 00:19:11.280 --> 00:19:13.610 align:start position:0% from a Noir circuit and that functionality<00:19:11.760> will<00:19:12.000> still<00:19:12.179> exist<00:19:12.539> but<00:19:13.020> no<00:19:13.380> R 00:19:13.610 --> 00:19:13.620 align:start position:0% functionality will still exist but no R 00:19:13.620 --> 00:19:15.470 align:start position:0% functionality will still exist but no R contracts<00:19:14.100> and<00:19:14.280> Aztecs<00:19:14.820> platform<00:19:15.059> are<00:19:15.299> not 00:19:15.470 --> 00:19:15.480 align:start position:0% contracts and Aztecs platform are not 00:19:15.480 --> 00:19:18.169 align:start position:0% contracts and Aztecs platform are not going<00:19:15.600> to<00:19:15.720> be<00:19:15.860> ZK<00:19:16.860> VM<00:19:17.280> they're<00:19:17.880> going<00:19:18.059> to 00:19:18.169 --> 00:19:18.179 align:start position:0% going to be ZK VM they're going to 00:19:18.179 --> 00:19:21.710 align:start position:0% going to be ZK VM they're going to they're<00:19:18.600> going<00:19:18.720> to<00:19:18.900> be<00:19:19.020> Noir<00:19:20.220> so<00:19:20.820> yeah<00:19:21.120> so<00:19:21.539> that 00:19:21.710 --> 00:19:21.720 align:start position:0% they're going to be Noir so yeah so that 00:19:21.720 --> 00:19:23.870 align:start position:0% they're going to be Noir so yeah so that means<00:19:22.020> that<00:19:22.140> you<00:19:22.320> also<00:19:22.620> have<00:19:22.799> the<00:19:23.100> your<00:19:23.400> go<00:19:23.640> you 00:19:23.870 --> 00:19:23.880 align:start position:0% means that you also have the your go you 00:19:23.880 --> 00:19:25.850 align:start position:0% means that you also have the your go you right<00:19:24.120> now<00:19:24.240> have<00:19:24.419> the<00:19:24.600> target<00:19:24.780> for<00:19:25.140> Aztec<00:19:25.620> or 00:19:25.850 --> 00:19:25.860 align:start position:0% right now have the target for Aztec or 00:19:25.860 --> 00:19:27.710 align:start position:0% right now have the target for Aztec or you<00:19:26.100> are<00:19:26.220> going<00:19:26.400> to<00:19:26.640> have<00:19:26.820> or<00:19:27.059> you're<00:19:27.360> going<00:19:27.600> to 00:19:27.710 --> 00:19:27.720 align:start position:0% you are going to have or you're going to 00:19:27.720 --> 00:19:30.250 align:start position:0% you are going to have or you're going to build<00:19:27.840> it<00:19:28.080> yet<00:19:28.260> sorry<00:19:28.860> can<00:19:29.220> you<00:19:29.340> say<00:19:29.520> it<00:19:29.700> again 00:19:30.250 --> 00:19:30.260 align:start position:0% build it yet sorry can you say it again 00:19:30.260 --> 00:19:33.590 align:start position:0% build it yet sorry can you say it again the<00:19:31.260> start<00:19:31.740> the<00:19:32.039> compilation<00:19:32.760> Target<00:19:33.059> right 00:19:33.590 --> 00:19:33.600 align:start position:0% the start the compilation Target right 00:19:33.600 --> 00:19:35.690 align:start position:0% the start the compilation Target right now<00:19:33.720> it's<00:19:34.020> only<00:19:34.200> ebm<00:19:34.740> but<00:19:34.980> you<00:19:35.100> are<00:19:35.280> planning 00:19:35.690 --> 00:19:35.700 align:start position:0% now it's only ebm but you are planning 00:19:35.700 --> 00:19:38.630 align:start position:0% now it's only ebm but you are planning to<00:19:36.000> to<00:19:36.600> be<00:19:36.780> able<00:19:36.900> to<00:19:37.200> migrate<00:19:37.679> to<00:19:37.980> to<00:19:38.400> be<00:19:38.520> able 00:19:38.630 --> 00:19:38.640 align:start position:0% to to be able to migrate to to be able 00:19:38.640 --> 00:19:41.390 align:start position:0% to to be able to migrate to to be able to<00:19:38.820> compile<00:19:39.179> as<00:19:39.419> well<00:19:39.600> to<00:19:39.900> Aztec<00:19:40.620> in<00:19:41.340> the 00:19:41.390 --> 00:19:41.400 align:start position:0% to compile as well to Aztec in the 00:19:41.400 --> 00:19:45.110 align:start position:0% to compile as well to Aztec in the future<00:19:41.520> yes<00:19:42.120> yeah<00:19:42.840> so<00:19:43.200> currently<00:19:43.860> Noir<00:19:44.640> is 00:19:45.110 --> 00:19:45.120 align:start position:0% future yes yeah so currently Noir is 00:19:45.120 --> 00:19:48.049 align:start position:0% future yes yeah so currently Noir is just<00:19:45.299> a<00:19:45.480> language<00:19:45.660> for<00:19:46.080> creating<00:19:46.500> circuits 00:19:48.049 --> 00:19:48.059 align:start position:0% just a language for creating circuits 00:19:48.059 --> 00:19:49.789 align:start position:0% just a language for creating circuits um<00:19:48.120> and<00:19:48.419> you<00:19:48.539> can<00:19:48.660> create<00:19:48.900> a<00:19:49.320> solidity 00:19:49.789 --> 00:19:49.799 align:start position:0% um and you can create a solidity 00:19:49.799 --> 00:19:51.590 align:start position:0% um and you can create a solidity verifier<00:19:50.340> that<00:19:50.580> allows<00:19:50.820> you<00:19:50.880> to<00:19:51.059> verify<00:19:51.419> those 00:19:51.590 --> 00:19:51.600 align:start position:0% verifier that allows you to verify those 00:19:51.600 --> 00:19:55.190 align:start position:0% verifier that allows you to verify those proofs<00:19:52.080> uh<00:19:52.620> on<00:19:53.160> the<00:19:53.280> on<00:19:53.400> the<00:19:53.580> ethereum<00:19:54.080> once<00:19:55.080> we 00:19:55.190 --> 00:19:55.200 align:start position:0% proofs uh on the on the ethereum once we 00:19:55.200 --> 00:19:57.350 align:start position:0% proofs uh on the on the ethereum once we extend<00:19:55.500> extend<00:19:56.100> the<00:19:56.280> syntax<00:19:56.580> to<00:19:56.820> have<00:19:57.059> a 00:19:57.350 --> 00:19:57.360 align:start position:0% extend extend the syntax to have a 00:19:57.360 --> 00:19:59.930 align:start position:0% extend extend the syntax to have a contract<00:19:57.780> terminology<00:19:58.280> uh<00:19:59.280> Aztec<00:19:59.700> free<00:19:59.820> will 00:19:59.930 --> 00:19:59.940 align:start position:0% contract terminology uh Aztec free will 00:19:59.940 --> 00:20:02.570 align:start position:0% contract terminology uh Aztec free will be<00:20:00.120> built<00:20:00.360> and<00:20:00.539> it<00:20:00.660> will<00:20:00.780> have<00:20:00.960> its<00:20:01.260> own<00:20:01.320> VM<00:20:01.740> and 00:20:02.570 --> 00:20:02.580 align:start position:0% be built and it will have its own VM and 00:20:02.580 --> 00:20:05.029 align:start position:0% be built and it will have its own VM and you<00:20:02.940> can<00:20:03.059> compile<00:20:03.360> those<00:20:03.600> contracts<00:20:04.200> to<00:20:04.620> the 00:20:05.029 --> 00:20:05.039 align:start position:0% you can compile those contracts to the 00:20:05.039 --> 00:20:10.789 align:start position:0% you can compile those contracts to the Aztec<00:20:05.460> free<00:20:05.640> VM<00:20:06.000> not<00:20:06.299> the<00:20:06.539> ZK<00:20:06.900> evm<00:20:07.559> hi<00:20:08.660> hi<00:20:09.799> well 00:20:10.789 --> 00:20:10.799 align:start position:0% Aztec free VM not the ZK evm hi hi well 00:20:10.799 --> 00:20:14.090 align:start position:0% Aztec free VM not the ZK evm hi hi well I<00:20:11.280> am<00:20:11.460> now<00:20:11.640> in<00:20:11.940> nor<00:20:12.419> right<00:20:13.020> now<00:20:13.140> it's<00:20:13.559> so<00:20:13.860> new 00:20:14.090 --> 00:20:14.100 align:start position:0% I am now in nor right now it's so new 00:20:14.100 --> 00:20:16.970 align:start position:0% I am now in nor right now it's so new for<00:20:14.340> me<00:20:14.460> and<00:20:15.059> I<00:20:15.179> would<00:20:15.299> like<00:20:15.480> to<00:20:15.660> know<00:20:15.980> whether 00:20:16.970 --> 00:20:16.980 align:start position:0% for me and I would like to know whether 00:20:16.980 --> 00:20:19.070 align:start position:0% for me and I would like to know whether the<00:20:17.340> main<00:20:17.520> applications<00:20:18.059> that<00:20:18.660> they<00:20:18.900> are 00:20:19.070 --> 00:20:19.080 align:start position:0% the main applications that they are 00:20:19.080 --> 00:20:20.810 align:start position:0% the main applications that they are using<00:20:19.440> now<00:20:19.740> right<00:20:20.039> now 00:20:20.810 --> 00:20:20.820 align:start position:0% using now right now 00:20:20.820 --> 00:20:22.610 align:start position:0% using now right now the<00:20:21.299> main<00:20:21.480> applications<00:20:21.840> using<00:20:22.140> Noir<00:20:22.380> right 00:20:22.610 --> 00:20:22.620 align:start position:0% the main applications using Noir right 00:20:22.620 --> 00:20:25.810 align:start position:0% the main applications using Noir right now<00:20:22.740> yeah<00:20:23.400> uh<00:20:24.120> well<00:20:24.480> there<00:20:25.200> hasn't<00:20:25.440> been<00:20:25.500> many 00:20:25.810 --> 00:20:25.820 align:start position:0% now yeah uh well there hasn't been many 00:20:25.820 --> 00:20:28.610 align:start position:0% now yeah uh well there hasn't been many uh<00:20:26.820> mostly<00:20:27.660> the<00:20:27.780> examples<00:20:28.080> you<00:20:28.260> can<00:20:28.380> find<00:20:28.440> on 00:20:28.610 --> 00:20:28.620 align:start position:0% uh mostly the examples you can find on 00:20:28.620 --> 00:20:31.010 align:start position:0% uh mostly the examples you can find on my<00:20:28.799> GitHub<00:20:29.100> or<00:20:29.760> inside<00:20:30.000> the<00:20:30.299> Noir<00:20:30.660> repo 00:20:31.010 --> 00:20:31.020 align:start position:0% my GitHub or inside the Noir repo 00:20:31.020 --> 00:20:33.110 align:start position:0% my GitHub or inside the Noir repo testing<00:20:31.500> the<00:20:31.620> language 00:20:33.110 --> 00:20:33.120 align:start position:0% testing the language 00:20:33.120 --> 00:20:35.630 align:start position:0% testing the language um but<00:20:33.780> there's<00:20:34.140> anything<00:20:34.980> you<00:20:35.280> can<00:20:35.400> think<00:20:35.520> of 00:20:35.630 --> 00:20:35.640 align:start position:0% um but there's anything you can think of 00:20:35.640 --> 00:20:38.390 align:start position:0% um but there's anything you can think of where<00:20:35.880> you<00:20:36.059> would<00:20:36.240> need<00:20:36.480> to<00:20:36.900> verify<00:20:37.500> a<00:20:37.679> proof 00:20:38.390 --> 00:20:38.400 align:start position:0% where you would need to verify a proof 00:20:38.400 --> 00:20:41.150 align:start position:0% where you would need to verify a proof and<00:20:39.240> do<00:20:39.600> something<00:20:39.840> based<00:20:40.200> off<00:20:40.260> that<00:20:40.440> ZK<00:20:40.740> proof 00:20:41.150 --> 00:20:41.160 align:start position:0% and do something based off that ZK proof 00:20:41.160 --> 00:20:44.990 align:start position:0% and do something based off that ZK proof you<00:20:42.059> couldn't<00:20:42.480> theoretically<00:20:43.020> do<00:20:43.440> a<00:20:43.620> Noir<00:20:44.340> so 00:20:44.990 --> 00:20:45.000 align:start position:0% you couldn't theoretically do a Noir so 00:20:45.000 --> 00:20:46.909 align:start position:0% you couldn't theoretically do a Noir so that<00:20:45.360> can<00:20:45.539> be<00:20:45.720> quite<00:20:46.380> a<00:20:46.559> lot<00:20:46.620> of<00:20:46.740> things 00:20:46.909 --> 00:20:46.919 align:start position:0% that can be quite a lot of things 00:20:46.919 --> 00:20:50.029 align:start position:0% that can be quite a lot of things synonymous<00:20:47.460> proof<00:20:47.760> of<00:20:47.820> membership<00:20:48.120> uh 00:20:50.029 --> 00:20:50.039 align:start position:0% synonymous proof of membership uh 00:20:50.039 --> 00:20:52.430 align:start position:0% synonymous proof of membership uh private<00:20:50.700> games<00:20:50.880> on<00:20:51.240> on<00:20:51.419> public<00:20:51.660> blockchains 00:20:52.430 --> 00:20:52.440 align:start position:0% private games on on public blockchains 00:20:52.440 --> 00:20:55.370 align:start position:0% private games on on public blockchains lots<00:20:53.400> of<00:20:53.460> different<00:20:53.640> things<00:20:53.880> all<00:20:54.780> right<00:20:55.020> big 00:20:55.370 --> 00:20:55.380 align:start position:0% lots of different things all right big 00:20:55.380 --> 00:20:59.240 align:start position:0% lots of different things all right big round<00:20:55.620> of<00:20:55.799> applause<00:20:56.160> to<00:20:56.460> Maxim<00:20:57.000> from<00:20:57.480> Aztec 00:20:59.240 --> 00:20:59.250 align:start position:0% round of applause to Maxim from Aztec 00:20:59.250 --> 00:21:02.430 align:start position:0% round of applause to Maxim from Aztec [Music]