WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:16.870 align:start position:0% [Music] 00:00:16.870 --> 00:00:16.880 align:start position:0% 00:00:16.880 --> 00:00:20.029 align:start position:0% okay<00:00:17.119> hello<00:00:17.560> everyone<00:00:18.560> uh<00:00:18.760> today<00:00:19.400> I<00:00:19.680> we'<00:00:19.880> like 00:00:20.029 --> 00:00:20.039 align:start position:0% okay hello everyone uh today I we' like 00:00:20.039 --> 00:00:22.990 align:start position:0% okay hello everyone uh today I we' like to<00:00:20.199> talk<00:00:20.439> about<00:00:20.880> ZK<00:00:21.279> MPC<00:00:22.160> U<00:00:22.279> bringing<00:00:22.720> public 00:00:22.990 --> 00:00:23.000 align:start position:0% to talk about ZK MPC U bringing public 00:00:23.000 --> 00:00:26.189 align:start position:0% to talk about ZK MPC U bringing public audity<00:00:23.760> into<00:00:24.080> multiparty<00:00:25.039> computation<00:00:26.039> yeah 00:00:26.189 --> 00:00:26.199 align:start position:0% audity into multiparty computation yeah 00:00:26.199 --> 00:00:29.189 align:start position:0% audity into multiparty computation yeah or<00:00:26.519> MPC<00:00:27.519> uh<00:00:27.679> today<00:00:27.920> I'm<00:00:28.160> excited<00:00:28.599> to<00:00:28.720> share<00:00:28.960> our 00:00:29.189 --> 00:00:29.199 align:start position:0% or MPC uh today I'm excited to share our 00:00:29.199 --> 00:00:30.669 align:start position:0% or MPC uh today I'm excited to share our latest<00:00:29.560> advant 00:00:30.669 --> 00:00:30.679 align:start position:0% latest advant 00:00:30.679 --> 00:00:34.030 align:start position:0% latest advant advancement<00:00:31.240> in<00:00:31.439> this<00:00:31.679> field<00:00:32.000> for 00:00:34.030 --> 00:00:34.040 align:start position:0% advancement in this field for 00:00:34.040 --> 00:00:37.350 align:start position:0% advancement in this field for you<00:00:35.040> okay<00:00:35.239> this<00:00:35.360> is<00:00:35.520> the<00:00:35.680> today's<00:00:36.079> outline<00:00:36.879> but 00:00:37.350 --> 00:00:37.360 align:start position:0% you okay this is the today's outline but 00:00:37.360 --> 00:00:38.910 align:start position:0% you okay this is the today's outline but yeah<00:00:37.520> let's<00:00:37.680> start<00:00:38.000> from<00:00:38.239> introduction<00:00:38.800> and 00:00:38.910 --> 00:00:38.920 align:start position:0% yeah let's start from introduction and 00:00:38.920 --> 00:00:41.069 align:start position:0% yeah let's start from introduction and please<00:00:39.160> give<00:00:39.280> me<00:00:39.399> a<00:00:39.520> little<00:00:39.920> bit<00:00:40.120> time<00:00:40.320> to<00:00:40.719> yeah 00:00:41.069 --> 00:00:41.079 align:start position:0% please give me a little bit time to yeah 00:00:41.079 --> 00:00:43.910 align:start position:0% please give me a little bit time to yeah for<00:00:41.440> the<00:00:41.760> team<00:00:42.079> introduction<00:00:43.079> also<00:00:43.399> yoi<00:00:43.680> Inc 00:00:43.910 --> 00:00:43.920 align:start position:0% for the team introduction also yoi Inc 00:00:43.920 --> 00:00:46.110 align:start position:0% for the team introduction also yoi Inc is<00:00:44.039> a<00:00:44.200> Japanese<00:00:44.600> fintech<00:00:45.039> company<00:00:45.520> to<00:00:45.680> helps 00:00:46.110 --> 00:00:46.120 align:start position:0% is a Japanese fintech company to helps 00:00:46.120 --> 00:00:49.029 align:start position:0% is a Japanese fintech company to helps and<00:00:46.320> entrepreneurs<00:00:46.960> and<00:00:47.199> businesses<00:00:47.800> to<00:00:48.360> grow 00:00:49.029 --> 00:00:49.039 align:start position:0% and entrepreneurs and businesses to grow 00:00:49.039 --> 00:00:51.910 align:start position:0% and entrepreneurs and businesses to grow uh<00:00:49.719> interesting<00:00:50.719> uh<00:00:50.960> uh<00:00:51.120> increasing<00:00:51.640> asset 00:00:51.910 --> 00:00:51.920 align:start position:0% uh interesting uh uh increasing asset 00:00:51.920 --> 00:00:53.950 align:start position:0% uh interesting uh uh increasing asset liquidity<00:00:52.640> with<00:00:52.840> Innovative<00:00:53.440> Financial 00:00:53.950 --> 00:00:53.960 align:start position:0% liquidity with Innovative Financial 00:00:53.960 --> 00:00:56.709 align:start position:0% liquidity with Innovative Financial Solutions<00:00:54.960> and<00:00:55.160> we<00:00:55.280> are<00:00:55.399> doing<00:00:55.640> R&D<00:00:56.199> for<00:00:56.600> uh 00:00:56.709 --> 00:00:56.719 align:start position:0% Solutions and we are doing R&D for uh 00:00:56.719 --> 00:00:59.310 align:start position:0% Solutions and we are doing R&D for uh zkp<00:00:57.239> and<00:00:57.359> MPC<00:00:57.879> to<00:00:58.079> focus<00:00:58.399> on<00:00:58.640> secure<00:00:59.039> and 00:00:59.310 --> 00:00:59.320 align:start position:0% zkp and MPC to focus on secure and 00:00:59.320 --> 00:01:01.509 align:start position:0% zkp and MPC to focus on secure and efficient<00:00:59.960> computation<00:01:00.879> so<00:01:01.039> today<00:01:01.320> I<00:01:01.359> would 00:01:01.509 --> 00:01:01.519 align:start position:0% efficient computation so today I would 00:01:01.519 --> 00:01:03.590 align:start position:0% efficient computation so today I would like<00:01:01.640> to<00:01:01.800> talk<00:01:02.039> about<00:01:02.440> the<00:01:02.840> project<00:01:03.480> which 00:01:03.590 --> 00:01:03.600 align:start position:0% like to talk about the project which 00:01:03.600 --> 00:01:07.310 align:start position:0% like to talk about the project which have<00:01:03.960> received<00:01:04.159> two<00:01:04.360> ESP<00:01:04.760> grants<00:01:05.080> from<00:01:05.239> the<00:01:05.360> is 00:01:07.310 --> 00:01:07.320 align:start position:0% have received two ESP grants from the is 00:01:07.320 --> 00:01:09.870 align:start position:0% have received two ESP grants from the is foundation<00:01:08.320> and<00:01:08.560> this<00:01:08.680> is<00:01:08.840> our<00:01:09.040> team<00:01:09.280> member 00:01:09.870 --> 00:01:09.880 align:start position:0% foundation and this is our team member 00:01:09.880 --> 00:01:11.990 align:start position:0% foundation and this is our team member uh<00:01:10.000> This<00:01:10.119> Is<00:01:10.240> Us<00:01:10.720> Nakai<00:01:11.200> a<00:01:11.360> researcher<00:01:11.799> and 00:01:11.990 --> 00:01:12.000 align:start position:0% uh This Is Us Nakai a researcher and 00:01:12.000 --> 00:01:15.070 align:start position:0% uh This Is Us Nakai a researcher and developer<00:01:12.799> and<00:01:13.200> I'm<00:01:13.560> task<00:01:14.320> and<00:01:14.479> last<00:01:14.799> he<00:01:14.920> is 00:01:15.070 --> 00:01:15.080 align:start position:0% developer and I'm task and last he is 00:01:15.080 --> 00:01:18.270 align:start position:0% developer and I'm task and last he is not<00:01:15.360> here<00:01:15.640> but<00:01:15.840> we<00:01:16.080> have<00:01:16.280> Masa<00:01:17.080> Masa<00:01:17.840> uh 00:01:18.270 --> 00:01:18.280 align:start position:0% not here but we have Masa Masa uh 00:01:18.280 --> 00:01:19.590 align:start position:0% not here but we have Masa Masa uh co-founder 00:01:19.590 --> 00:01:19.600 align:start position:0% co-founder 00:01:19.600 --> 00:01:23.550 align:start position:0% co-founder CEO<00:01:20.600> so<00:01:20.960> uh<00:01:21.079> let's<00:01:21.280> go<00:01:21.479> into<00:01:21.720> the<00:01:21.920> topic<00:01:22.880> uh<00:01:23.200> let 00:01:23.550 --> 00:01:23.560 align:start position:0% CEO so uh let's go into the topic uh let 00:01:23.560 --> 00:01:25.630 align:start position:0% CEO so uh let's go into the topic uh let let<00:01:23.680> me<00:01:24.320> first<00:01:24.600> introduce<00:01:25.119> about<00:01:25.400> the 00:01:25.630 --> 00:01:25.640 align:start position:0% let me first introduce about the 00:01:25.640 --> 00:01:28.030 align:start position:0% let me first introduce about the importance<00:01:26.040> of<00:01:26.159> the<00:01:26.320> secure<00:01:26.799> computation<00:01:27.799> uh 00:01:28.030 --> 00:01:28.040 align:start position:0% importance of the secure computation uh 00:01:28.040 --> 00:01:30.950 align:start position:0% importance of the secure computation uh and<00:01:28.280> MPC<00:01:29.280> so<00:01:29.479> secure<00:01:29.960> computation<00:01:30.479> in<00:01:30.680> data 00:01:30.950 --> 00:01:30.960 align:start position:0% and MPC so secure computation in data 00:01:30.960 --> 00:01:34.830 align:start position:0% and MPC so secure computation in data driven<00:01:31.479> world<00:01:32.119> is<00:01:32.799> uh<00:01:33.520> is<00:01:33.799> really<00:01:34.079> essential 00:01:34.830 --> 00:01:34.840 align:start position:0% driven world is uh is really essential 00:01:34.840 --> 00:01:37.630 align:start position:0% driven world is uh is really essential it<00:01:35.000> allows<00:01:35.360> us<00:01:35.520> to<00:01:35.799> protect<00:01:36.360> the<00:01:36.600> sensitive<00:01:37.520> uh 00:01:37.630 --> 00:01:37.640 align:start position:0% it allows us to protect the sensitive uh 00:01:37.640 --> 00:01:39.630 align:start position:0% it allows us to protect the sensitive uh information<00:01:38.399> such<00:01:38.600> as<00:01:38.880> healthare<00:01:39.399> and 00:01:39.630 --> 00:01:39.640 align:start position:0% information such as healthare and 00:01:39.640 --> 00:01:42.310 align:start position:0% information such as healthare and financial<00:01:40.600> and<00:01:40.759> it<00:01:40.920> enables<00:01:41.399> useful<00:01:41.759> analysis 00:01:42.310 --> 00:01:42.320 align:start position:0% financial and it enables useful analysis 00:01:42.320 --> 00:01:44.630 align:start position:0% financial and it enables useful analysis without<00:01:42.680> exposing<00:01:43.479> information<00:01:44.479> and 00:01:44.630 --> 00:01:44.640 align:start position:0% without exposing information and 00:01:44.640 --> 00:01:47.350 align:start position:0% without exposing information and multiparty<00:01:45.280> computation<00:01:46.159> uh<00:01:46.280> or<00:01:46.479> MPC<00:01:47.040> is<00:01:47.159> a 00:01:47.350 --> 00:01:47.360 align:start position:0% multiparty computation uh or MPC is a 00:01:47.360 --> 00:01:50.469 align:start position:0% multiparty computation uh or MPC is a key<00:01:47.680> technology<00:01:48.240> for<00:01:48.479> this<00:01:49.000> purpose<00:01:50.000> uh<00:01:50.159> so 00:01:50.469 --> 00:01:50.479 align:start position:0% key technology for this purpose uh so 00:01:50.479 --> 00:01:53.749 align:start position:0% key technology for this purpose uh so yeah<00:01:51.280> uh<00:01:51.920> it<00:01:52.079> enables<00:01:52.520> multiple<00:01:52.960> parties<00:01:53.320> to 00:01:53.749 --> 00:01:53.759 align:start position:0% yeah uh it enables multiple parties to 00:01:53.759 --> 00:01:55.870 align:start position:0% yeah uh it enables multiple parties to jointly<00:01:54.200> comput<00:01:54.719> functions<00:01:55.360> while<00:01:55.560> keeping 00:01:55.870 --> 00:01:55.880 align:start position:0% jointly comput functions while keeping 00:01:55.880 --> 00:01:58.310 align:start position:0% jointly comput functions while keeping their<00:01:56.119> inputs<00:01:56.719> private<00:01:57.640> and<00:01:57.799> they<00:01:57.960> only<00:01:58.159> have 00:01:58.310 --> 00:01:58.320 align:start position:0% their inputs private and they only have 00:01:58.320 --> 00:02:00.590 align:start position:0% their inputs private and they only have to<00:01:58.399> share<00:01:58.680> the<00:01:58.840> final<00:01:59.280> results<00:01:59.960> so<00:02:00.200> this<00:02:00.360> will 00:02:00.590 --> 00:02:00.600 align:start position:0% to share the final results so this will 00:02:00.600 --> 00:02:02.870 align:start position:0% to share the final results so this will ensure<00:02:01.280> the<00:02:01.439> secure 00:02:02.870 --> 00:02:02.880 align:start position:0% ensure the secure 00:02:02.880 --> 00:02:06.190 align:start position:0% ensure the secure collaboration<00:02:03.880> so<00:02:04.280> uh<00:02:04.399> let's<00:02:04.640> think<00:02:05.240> why<00:02:06.079> uh 00:02:06.190 --> 00:02:06.200 align:start position:0% collaboration so uh let's think why uh 00:02:06.200 --> 00:02:09.510 align:start position:0% collaboration so uh let's think why uh the<00:02:06.320> third<00:02:06.680> party<00:02:06.920> verification<00:02:07.560> for<00:02:07.920> MPC<00:02:08.679> is 00:02:09.510 --> 00:02:09.520 align:start position:0% the third party verification for MPC is 00:02:09.520 --> 00:02:12.470 align:start position:0% the third party verification for MPC is essential<00:02:10.520> uh<00:02:11.200> especially<00:02:11.680> the<00:02:11.879> case<00:02:12.200> we<00:02:12.319> are 00:02:12.470 --> 00:02:12.480 align:start position:0% essential uh especially the case we are 00:02:12.480 --> 00:02:15.110 align:start position:0% essential uh especially the case we are using<00:02:12.879> dishonest<00:02:13.440> majority<00:02:13.959> protocols<00:02:14.519> like 00:02:15.110 --> 00:02:15.120 align:start position:0% using dishonest majority protocols like 00:02:15.120 --> 00:02:18.509 align:start position:0% using dishonest majority protocols like speeds<00:02:16.120> uh<00:02:16.280> when<00:02:16.480> we<00:02:16.680> are<00:02:16.879> using<00:02:17.800> uh<00:02:17.959> dishonest 00:02:18.509 --> 00:02:18.519 align:start position:0% speeds uh when we are using uh dishonest 00:02:18.519 --> 00:02:21.750 align:start position:0% speeds uh when we are using uh dishonest majority<00:02:19.480> protocols<00:02:20.480> uh<00:02:20.800> participants<00:02:21.560> like 00:02:21.750 --> 00:02:21.760 align:start position:0% majority protocols uh participants like 00:02:21.760 --> 00:02:26.150 align:start position:0% majority protocols uh participants like Alice<00:02:22.160> and<00:02:22.400> Bob<00:02:23.120> can<00:02:23.959> verify<00:02:24.920> them<00:02:25.680> within 00:02:26.150 --> 00:02:26.160 align:start position:0% Alice and Bob can verify them within 00:02:26.160 --> 00:02:28.070 align:start position:0% Alice and Bob can verify them within themselves<00:02:26.480> that<00:02:26.720> calculation<00:02:27.319> results<00:02:27.800> are 00:02:28.070 --> 00:02:28.080 align:start position:0% themselves that calculation results are 00:02:28.080 --> 00:02:30.309 align:start position:0% themselves that calculation results are computed<00:02:28.599> correctly 00:02:30.309 --> 00:02:30.319 align:start position:0% computed correctly 00:02:30.319 --> 00:02:32.910 align:start position:0% computed correctly however<00:02:30.840> they<00:02:31.000> cannot<00:02:31.400> directly<00:02:31.959> prove<00:02:32.800> uh 00:02:32.910 --> 00:02:32.920 align:start position:0% however they cannot directly prove uh 00:02:32.920 --> 00:02:34.790 align:start position:0% however they cannot directly prove uh the<00:02:33.080> correctness<00:02:33.560> to<00:02:33.720> the<00:02:33.879> third<00:02:34.200> party<00:02:34.599> such 00:02:34.790 --> 00:02:34.800 align:start position:0% the correctness to the third party such 00:02:34.800 --> 00:02:37.309 align:start position:0% the correctness to the third party such as<00:02:35.160> Charlie<00:02:36.000> so<00:02:36.160> in<00:02:36.319> this<00:02:36.519> case<00:02:36.680> Charlie<00:02:37.120> will 00:02:37.309 --> 00:02:37.319 align:start position:0% as Charlie so in this case Charlie will 00:02:37.319 --> 00:02:39.589 align:start position:0% as Charlie so in this case Charlie will think<00:02:37.879> can<00:02:38.000> I<00:02:38.160> trust<00:02:38.560> this 00:02:39.589 --> 00:02:39.599 align:start position:0% think can I trust this 00:02:39.599 --> 00:02:42.869 align:start position:0% think can I trust this result<00:02:40.599> uh<00:02:40.920> yeah<00:02:41.239> that's<00:02:41.480> why<00:02:42.000> uh<00:02:42.159> adding<00:02:42.480> C 00:02:42.869 --> 00:02:42.879 align:start position:0% result uh yeah that's why uh adding C 00:02:42.879 --> 00:02:47.589 align:start position:0% result uh yeah that's why uh adding C party<00:02:43.440> verification<00:02:44.000> to<00:02:44.159> MPC<00:02:44.720> is<00:02:44.920> a<00:02:45.159> very<00:02:45.760> uh 00:02:47.589 --> 00:02:47.599 align:start position:0% party verification to MPC is a very uh 00:02:47.599 --> 00:02:50.470 align:start position:0% party verification to MPC is a very uh essential<00:02:48.599> uh<00:02:49.040> uh<00:02:49.200> especially<00:02:49.560> for<00:02:49.840> use<00:02:50.120> cases 00:02:50.470 --> 00:02:50.480 align:start position:0% essential uh uh especially for use cases 00:02:50.480 --> 00:02:52.509 align:start position:0% essential uh uh especially for use cases like<00:02:50.720> application<00:02:51.200> to<00:02:51.440> blockchain<00:02:52.360> uh 00:02:52.509 --> 00:02:52.519 align:start position:0% like application to blockchain uh 00:02:52.519 --> 00:02:58.270 align:start position:0% like application to blockchain uh finance<00:02:53.360> and<00:02:53.519> medical<00:02:53.959> data 00:02:58.270 --> 00:02:58.280 align:start position:0% 00:02:58.280 --> 00:03:01.149 align:start position:0% analytics<00:02:59.280> so<00:02:59.959> uh<00:03:00.159> this<00:03:00.480> will<00:03:00.840> is<00:03:01.000> the 00:03:01.149 --> 00:03:01.159 align:start position:0% analytics so uh this will is the 00:03:01.159 --> 00:03:03.990 align:start position:0% analytics so uh this will is the overview<00:03:01.640> for<00:03:01.840> the<00:03:02.280> rest<00:03:02.519> of<00:03:02.680> the<00:03:03.239> uh 00:03:03.990 --> 00:03:04.000 align:start position:0% overview for the rest of the uh 00:03:04.000 --> 00:03:07.149 align:start position:0% overview for the rest of the uh presentation<00:03:05.000> uh<00:03:05.159> firstly<00:03:05.799> uh<00:03:05.920> we<00:03:06.040> will<00:03:07.040> uh 00:03:07.149 --> 00:03:07.159 align:start position:0% presentation uh firstly uh we will uh 00:03:07.159 --> 00:03:08.589 align:start position:0% presentation uh firstly uh we will uh show<00:03:07.480> how 00:03:08.589 --> 00:03:08.599 align:start position:0% show how 00:03:08.599 --> 00:03:12.270 align:start position:0% show how to<00:03:09.599> uh<00:03:09.840> introduce<00:03:10.360> the<00:03:10.560> public<00:03:10.840> ail<00:03:11.480> into<00:03:11.799> spe 00:03:12.270 --> 00:03:12.280 align:start position:0% to uh introduce the public ail into spe 00:03:12.280 --> 00:03:14.430 align:start position:0% to uh introduce the public ail into spe NPC<00:03:12.799> protocol<00:03:13.440> by<00:03:13.720> introducing<00:03:14.280> the 00:03:14.430 --> 00:03:14.440 align:start position:0% NPC protocol by introducing the 00:03:14.440 --> 00:03:17.630 align:start position:0% NPC protocol by introducing the collaborative<00:03:15.000> DK<00:03:15.640> snarks<00:03:16.640> uh<00:03:16.920> next<00:03:17.280> we<00:03:17.400> will 00:03:17.630 --> 00:03:17.640 align:start position:0% collaborative DK snarks uh next we will 00:03:17.640 --> 00:03:20.589 align:start position:0% collaborative DK snarks uh next we will secure<00:03:18.319> consistency<00:03:18.920> of<00:03:19.040> the<00:03:19.159> secret<00:03:19.599> input 00:03:20.589 --> 00:03:20.599 align:start position:0% secure consistency of the secret input 00:03:20.599 --> 00:03:23.110 align:start position:0% secure consistency of the secret input which<00:03:20.799> enable<00:03:21.280> third<00:03:21.640> party<00:03:21.959> to<00:03:22.280> verify<00:03:22.879> the 00:03:23.110 --> 00:03:23.120 align:start position:0% which enable third party to verify the 00:03:23.120 --> 00:03:26.070 align:start position:0% which enable third party to verify the input<00:03:23.480> conat<00:03:24.360> using<00:03:24.720> par<00:03:25.080> and 00:03:26.070 --> 00:03:26.080 align:start position:0% input conat using par and 00:03:26.080 --> 00:03:29.309 align:start position:0% input conat using par and commitment<00:03:27.080> and<00:03:27.360> next<00:03:27.680> we<00:03:27.799> will<00:03:28.519> uh<00:03:28.760> show<00:03:29.080> our 00:03:29.309 --> 00:03:29.319 align:start position:0% commitment and next we will uh show our 00:03:29.319 --> 00:03:32.110 align:start position:0% commitment and next we will uh show our enhanc<00:03:30.200> of<00:03:30.360> the<00:03:30.560> bitwise<00:03:31.080> support<00:03:31.480> for<00:03:31.760> public 00:03:32.110 --> 00:03:32.120 align:start position:0% enhanc of the bitwise support for public 00:03:32.120 --> 00:03:35.390 align:start position:0% enhanc of the bitwise support for public auditable<00:03:33.000> auditable<00:03:33.640> speeds<00:03:34.640> so<00:03:34.879> speeds<00:03:35.239> is 00:03:35.390 --> 00:03:35.400 align:start position:0% auditable auditable speeds so speeds is 00:03:35.400 --> 00:03:37.589 align:start position:0% auditable auditable speeds so speeds is well<00:03:35.560> suited<00:03:35.920> for<00:03:36.159> arithmetic<00:03:36.920> operations 00:03:37.589 --> 00:03:37.599 align:start position:0% well suited for arithmetic operations 00:03:37.599 --> 00:03:40.190 align:start position:0% well suited for arithmetic operations but<00:03:37.920> not<00:03:38.640> effective<00:03:39.080> for<00:03:39.519> uh<00:03:39.640> bitwise 00:03:40.190 --> 00:03:40.200 align:start position:0% but not effective for uh bitwise 00:03:40.200 --> 00:03:43.990 align:start position:0% but not effective for uh bitwise operation<00:03:41.200> so<00:03:41.519> we<00:03:41.840> support<00:03:42.840> uh<00:03:43.400> functions 00:03:43.990 --> 00:03:44.000 align:start position:0% operation so we support uh functions 00:03:44.000 --> 00:03:47.030 align:start position:0% operation so we support uh functions kind<00:03:44.239> of<00:03:44.560> such<00:03:44.879> kind<00:03:45.120> of<00:03:45.840> uh<00:03:46.040> comparisons 00:03:47.030 --> 00:03:47.040 align:start position:0% kind of such kind of uh comparisons 00:03:47.040 --> 00:03:48.710 align:start position:0% kind of such kind of uh comparisons conditional<00:03:47.360> branching<00:03:47.840> and<00:03:48.040> de<00:03:48.319> bit 00:03:48.710 --> 00:03:48.720 align:start position:0% conditional branching and de bit 00:03:48.720 --> 00:03:50.710 align:start position:0% conditional branching and de bit composition<00:03:49.280> and<00:03:49.439> so<00:03:49.640> on<00:03:50.159> and<00:03:50.319> this<00:03:50.439> will 00:03:50.710 --> 00:03:50.720 align:start position:0% composition and so on and this will 00:03:50.720 --> 00:03:53.390 align:start position:0% composition and so on and this will expand<00:03:51.200> the<00:03:51.400> range<00:03:51.720> of<00:03:52.079> possible 00:03:53.390 --> 00:03:53.400 align:start position:0% expand the range of possible 00:03:53.400 --> 00:03:56.589 align:start position:0% expand the range of possible applications<00:03:54.400> and<00:03:54.640> as<00:03:54.760> a<00:03:55.040> application<00:03:56.040> uh<00:03:56.280> we 00:03:56.589 --> 00:03:56.599 align:start position:0% applications and as a application uh we 00:03:56.599 --> 00:03:58.470 align:start position:0% applications and as a application uh we implemented<00:03:57.120> the<00:03:57.280> game<00:03:57.599> master<00:03:58.040> free 00:03:58.470 --> 00:03:58.480 align:start position:0% implemented the game master free 00:03:58.480 --> 00:04:01.429 align:start position:0% implemented the game master free werewolf<00:03:59.120> or<00:03:59.480> sometimes<00:03:59.840> called<00:04:00.079> Mafia<00:04:00.560> game 00:04:01.429 --> 00:04:01.439 align:start position:0% werewolf or sometimes called Mafia game 00:04:01.439 --> 00:04:03.990 align:start position:0% werewolf or sometimes called Mafia game uh<00:04:01.560> using<00:04:01.879> MPC<00:04:02.560> to<00:04:02.720> Showcase<00:04:03.360> how<00:04:03.760> our 00:04:03.990 --> 00:04:04.000 align:start position:0% uh using MPC to Showcase how our 00:04:04.000 --> 00:04:06.350 align:start position:0% uh using MPC to Showcase how our enhancement<00:04:04.640> will<00:04:05.000> make<00:04:05.200> the<00:04:05.360> MPC<00:04:05.840> more 00:04:06.350 --> 00:04:06.360 align:start position:0% enhancement will make the MPC more 00:04:06.360 --> 00:04:09.630 align:start position:0% enhancement will make the MPC more versatile<00:04:07.000> to<00:04:07.760> uh<00:04:07.920> collaborative<00:04:08.480> use 00:04:09.630 --> 00:04:09.640 align:start position:0% versatile to uh collaborative use 00:04:09.640 --> 00:04:13.550 align:start position:0% versatile to uh collaborative use cases<00:04:10.640> okay<00:04:11.000> I<00:04:11.239> I'll<00:04:11.480> pass<00:04:11.680> to 00:04:13.550 --> 00:04:13.560 align:start position:0% cases okay I I'll pass to 00:04:13.560 --> 00:04:17.590 align:start position:0% cases okay I I'll pass to yusuke<00:04:14.560> on<00:04:14.920> next<00:04:15.680> uh<00:04:16.359> to<00:04:16.720> achieve<00:04:17.199> what<00:04:17.400> we 00:04:17.590 --> 00:04:17.600 align:start position:0% yusuke on next uh to achieve what we 00:04:17.600 --> 00:04:20.349 align:start position:0% yusuke on next uh to achieve what we introduced<00:04:18.600> we<00:04:18.799> need<00:04:19.120> to<00:04:19.840> understand<00:04:20.120> the 00:04:20.349 --> 00:04:20.359 align:start position:0% introduced we need to understand the 00:04:20.359 --> 00:04:24.390 align:start position:0% introduced we need to understand the backgrounds<00:04:21.239> and<00:04:21.880> issues<00:04:22.880> uh<00:04:23.000> in<00:04:23.160> more<00:04:23.440> depths 00:04:24.390 --> 00:04:24.400 align:start position:0% backgrounds and issues uh in more depths 00:04:24.400 --> 00:04:28.710 align:start position:0% backgrounds and issues uh in more depths and<00:04:24.880> we<00:04:25.720> which<00:04:26.000> we<00:04:26.160> will 00:04:28.710 --> 00:04:28.720 align:start position:0% 00:04:28.720 --> 00:04:32.230 align:start position:0% explain<00:04:29.720> firstly<00:04:30.160> let<00:04:30.320> us<00:04:30.560> begin<00:04:31.080> with<00:04:31.440> the<00:04:32.039> uh 00:04:32.230 --> 00:04:32.240 align:start position:0% explain firstly let us begin with the uh 00:04:32.240 --> 00:04:36.870 align:start position:0% explain firstly let us begin with the uh MPC<00:04:32.919> protocol<00:04:33.720> Basics<00:04:34.720> uh<00:04:35.360> MPC<00:04:36.160> uses<00:04:36.639> the 00:04:36.870 --> 00:04:36.880 align:start position:0% MPC protocol Basics uh MPC uses the 00:04:36.880 --> 00:04:39.749 align:start position:0% MPC protocol Basics uh MPC uses the techniques<00:04:37.520> called<00:04:37.919> secret<00:04:38.520> sharing<00:04:39.520> uh 00:04:39.749 --> 00:04:39.759 align:start position:0% techniques called secret sharing uh 00:04:39.759 --> 00:04:43.270 align:start position:0% techniques called secret sharing uh which<00:04:40.160> is<00:04:40.800> uh<00:04:41.160> data<00:04:41.600> is<00:04:41.800> splitted<00:04:42.479> to<00:04:42.880> some 00:04:43.270 --> 00:04:43.280 align:start position:0% which is uh data is splitted to some 00:04:43.280 --> 00:04:47.510 align:start position:0% which is uh data is splitted to some shares<00:04:44.280> and<00:04:44.560> each<00:04:44.840> party<00:04:45.440> has<00:04:46.199> uh<00:04:46.680> it<00:04:46.919> shares 00:04:47.510 --> 00:04:47.520 align:start position:0% shares and each party has uh it shares 00:04:47.520 --> 00:04:50.710 align:start position:0% shares and each party has uh it shares one<00:04:47.759> by<00:04:48.240> one<00:04:49.240> and<00:04:49.560> there<00:04:49.680> are<00:04:49.919> some<00:04:50.199> kind<00:04:50.479> of 00:04:50.710 --> 00:04:50.720 align:start position:0% one by one and there are some kind of 00:04:50.720 --> 00:04:52.870 align:start position:0% one by one and there are some kind of secret<00:04:51.120> sharing<00:04:51.680> like<00:04:52.120> additive<00:04:52.520> secret 00:04:52.870 --> 00:04:52.880 align:start position:0% secret sharing like additive secret 00:04:52.880 --> 00:04:56.469 align:start position:0% secret sharing like additive secret sharing<00:04:53.360> and<00:04:53.520> Shia<00:04:53.960> SEC<00:04:54.320> Shing<00:04:54.759> and<00:04:54.919> so<00:04:55.479> on 00:04:56.469 --> 00:04:56.479 align:start position:0% sharing and Shia SEC Shing and so on 00:04:56.479 --> 00:04:59.710 align:start position:0% sharing and Shia SEC Shing and so on let's<00:04:56.759> consider<00:04:57.280> the<00:04:57.520> example<00:04:58.000> of<00:04:58.400> addition<00:04:59.400> X 00:04:59.710 --> 00:04:59.720 align:start position:0% let's consider the example of addition X 00:04:59.720 --> 00:05:03.310 align:start position:0% let's consider the example of addition X X<00:05:00.000> and<00:05:00.280> Y<00:05:00.759> is<00:05:00.960> shared<00:05:01.759> and<00:05:02.000> the<00:05:02.280> addition<00:05:02.800> of<00:05:03.000> X 00:05:03.310 --> 00:05:03.320 align:start position:0% X and Y is shared and the addition of X 00:05:03.320 --> 00:05:07.189 align:start position:0% X and Y is shared and the addition of X Plus<00:05:03.600> Y<00:05:04.440> is<00:05:05.000> uh<00:05:05.160> can<00:05:05.320> be<00:05:05.520> obtained<00:05:06.080> by<00:05:06.360> simply 00:05:07.189 --> 00:05:07.199 align:start position:0% Plus Y is uh can be obtained by simply 00:05:07.199 --> 00:05:11.590 align:start position:0% Plus Y is uh can be obtained by simply addition<00:05:07.840> of<00:05:08.199> the<00:05:08.759> their<00:05:09.240> shares<00:05:10.240> and<00:05:10.680> however 00:05:11.590 --> 00:05:11.600 align:start position:0% addition of the their shares and however 00:05:11.600 --> 00:05:14.230 align:start position:0% addition of the their shares and however multiplication<00:05:12.600> and<00:05:13.080> other<00:05:13.759> more 00:05:14.230 --> 00:05:14.240 align:start position:0% multiplication and other more 00:05:14.240 --> 00:05:18.909 align:start position:0% multiplication and other more complicated<00:05:15.240> operation<00:05:16.000> needs<00:05:16.880> uh<00:05:17.840> needs 00:05:18.909 --> 00:05:18.919 align:start position:0% complicated operation needs uh needs 00:05:18.919 --> 00:05:23.510 align:start position:0% complicated operation needs uh needs Communication<00:05:19.919> in<00:05:20.319> intermediate<00:05:21.479> steps<00:05:22.520> yeah 00:05:23.510 --> 00:05:23.520 align:start position:0% Communication in intermediate steps yeah 00:05:23.520 --> 00:05:26.670 align:start position:0% Communication in intermediate steps yeah and<00:05:23.800> space<00:05:24.759> space<00:05:25.280> is<00:05:25.479> one<00:05:25.639> of<00:05:25.800> the<00:05:26.080> well<00:05:26.319> known 00:05:26.670 --> 00:05:26.680 align:start position:0% and space space is one of the well known 00:05:26.680 --> 00:05:30.189 align:start position:0% and space space is one of the well known NPC<00:05:27.199> protocol<00:05:27.800> proposed<00:05:28.280> in<00:05:28.479> 2011 00:05:30.189 --> 00:05:30.199 align:start position:0% NPC protocol proposed in 2011 00:05:30.199 --> 00:05:33.710 align:start position:0% NPC protocol proposed in 2011 and<00:05:30.639> this<00:05:31.120> is<00:05:31.759> uh<00:05:32.000> use<00:05:32.400> this<00:05:32.639> uses<00:05:33.360> additive 00:05:33.710 --> 00:05:33.720 align:start position:0% and this is uh use this uses additive 00:05:33.720 --> 00:05:36.749 align:start position:0% and this is uh use this uses additive suet<00:05:34.120> sharing<00:05:34.680> so<00:05:35.000> it<00:05:35.120> is<00:05:35.280> suitable<00:05:35.800> for<00:05:36.479> uh 00:05:36.749 --> 00:05:36.759 align:start position:0% suet sharing so it is suitable for uh 00:05:36.759 --> 00:05:39.510 align:start position:0% suet sharing so it is suitable for uh arithmetic<00:05:37.319> operation<00:05:38.120> like<00:05:38.759> addition<00:05:39.280> and 00:05:39.510 --> 00:05:39.520 align:start position:0% arithmetic operation like addition and 00:05:39.520 --> 00:05:41.469 align:start position:0% arithmetic operation like addition and multiplication<00:05:40.520> and<00:05:40.720> so 00:05:41.469 --> 00:05:41.479 align:start position:0% multiplication and so 00:05:41.479 --> 00:05:45.990 align:start position:0% multiplication and so on<00:05:42.479> and<00:05:43.120> there<00:05:43.280> are<00:05:43.720> two<00:05:44.000> phases<00:05:44.919> uh<00:05:45.120> one<00:05:45.360> is 00:05:45.990 --> 00:05:46.000 align:start position:0% on and there are two phases uh one is 00:05:46.000 --> 00:05:50.590 align:start position:0% on and there are two phases uh one is preprocessing<00:05:47.000> and<00:05:47.199> the<00:05:47.360> other<00:05:47.759> is<00:05:48.000> online 00:05:50.590 --> 00:05:50.600 align:start position:0% 00:05:50.600 --> 00:05:54.430 align:start position:0% phase<00:05:51.600> and<00:05:51.759> the<00:05:51.960> next<00:05:52.800> we<00:05:53.000> talk<00:05:53.280> about<00:05:53.600> the<00:05:53.840> P 00:05:54.430 --> 00:05:54.440 align:start position:0% phase and the next we talk about the P 00:05:54.440 --> 00:05:58.110 align:start position:0% phase and the next we talk about the P MPC<00:05:55.440> uh<00:05:55.800> publicly<00:05:56.360> auditable<00:05:56.880> MPC<00:05:57.680> is<00:05:57.880> the 00:05:58.110 --> 00:05:58.120 align:start position:0% MPC uh publicly auditable MPC is the 00:05:58.120 --> 00:06:01.189 align:start position:0% MPC uh publicly auditable MPC is the most<00:05:58.520> important<00:05:59.080> concept<00:05:59.639> in<00:05:59.800> our<00:06:00.080> session<00:06:01.039> in 00:06:01.189 --> 00:06:01.199 align:start position:0% most important concept in our session in 00:06:01.199 --> 00:06:04.950 align:start position:0% most important concept in our session in order<00:06:01.680> NPC<00:06:02.639> uh<00:06:02.759> the<00:06:02.919> correctness<00:06:03.680> of<00:06:04.360> MPC 00:06:04.950 --> 00:06:04.960 align:start position:0% order NPC uh the correctness of MPC 00:06:04.960 --> 00:06:07.990 align:start position:0% order NPC uh the correctness of MPC calculation<00:06:05.759> can<00:06:05.960> be<00:06:06.160> verified<00:06:06.680> by<00:06:07.479> uh 00:06:07.990 --> 00:06:08.000 align:start position:0% calculation can be verified by uh 00:06:08.000 --> 00:06:12.950 align:start position:0% calculation can be verified by uh participants<00:06:09.000> however<00:06:09.919> pmpc<00:06:10.919> uh<00:06:11.080> impos<00:06:11.759> MPC 00:06:12.950 --> 00:06:12.960 align:start position:0% participants however pmpc uh impos MPC 00:06:12.960 --> 00:06:16.309 align:start position:0% participants however pmpc uh impos MPC on<00:06:13.960> uh<00:06:14.120> of<00:06:14.720> third<00:06:15.120> party 00:06:16.309 --> 00:06:16.319 align:start position:0% on uh of third party 00:06:16.319 --> 00:06:19.830 align:start position:0% on uh of third party verification<00:06:17.319> it<00:06:17.479> was<00:06:17.759> proposed<00:06:18.280> in<00:06:18.840> 2014 00:06:19.830 --> 00:06:19.840 align:start position:0% verification it was proposed in 2014 00:06:19.840 --> 00:06:22.550 align:start position:0% verification it was proposed in 2014 however<00:06:20.400> the<00:06:20.960> efficient<00:06:21.560> implementation 00:06:22.550 --> 00:06:22.560 align:start position:0% however the efficient implementation 00:06:22.560 --> 00:06:26.790 align:start position:0% however the efficient implementation does<00:06:22.800> not<00:06:23.160> exist<00:06:23.639> at<00:06:23.840> the 00:06:26.790 --> 00:06:26.800 align:start position:0% 00:06:26.800 --> 00:06:31.629 align:start position:0% time<00:06:27.800> however<00:06:28.639> uh<00:06:28.840> in<00:06:29.120> 20<00:06:29.840> 21<00:06:30.840> the<00:06:31.039> coopertive 00:06:31.629 --> 00:06:31.639 align:start position:0% time however uh in 20 21 the coopertive 00:06:31.639 --> 00:06:35.589 align:start position:0% time however uh in 20 21 the coopertive Z<00:06:32.039> snacks<00:06:32.880> which<00:06:33.080> is<00:06:33.520> the<00:06:33.680> one<00:06:33.960> of<00:06:34.599> efficient 00:06:35.589 --> 00:06:35.599 align:start position:0% Z snacks which is the one of efficient 00:06:35.599 --> 00:06:38.510 align:start position:0% Z snacks which is the one of efficient uh<00:06:36.039> implementation<00:06:36.880> of<00:06:37.240> public<00:06:37.840> auditable 00:06:38.510 --> 00:06:38.520 align:start position:0% uh implementation of public auditable 00:06:38.520 --> 00:06:42.309 align:start position:0% uh implementation of public auditable MPC<00:06:39.520> uh<00:06:39.680> was<00:06:39.919> proposed<00:06:40.479> by<00:06:40.759> oir<00:06:41.440> and 00:06:42.309 --> 00:06:42.319 align:start position:0% MPC uh was proposed by oir and 00:06:42.319 --> 00:06:47.710 align:start position:0% MPC uh was proposed by oir and Bon<00:06:43.319> the<00:06:43.560> idea<00:06:44.199> of<00:06:44.479> ctive<00:06:45.319> snack<00:06:45.919> is<00:06:46.280> to<00:06:46.720> prove 00:06:47.710 --> 00:06:47.720 align:start position:0% Bon the idea of ctive snack is to prove 00:06:47.720 --> 00:06:52.230 align:start position:0% Bon the idea of ctive snack is to prove uh<00:06:48.400> to<00:06:48.680> prove<00:06:49.160> by<00:06:49.400> m<00:06:50.400> m 00:06:52.230 --> 00:06:52.240 align:start position:0% uh to prove by m m 00:06:52.240 --> 00:06:57.309 align:start position:0% uh to prove by m m provs<00:06:53.240> and<00:06:53.680> the<00:06:53.880> call<00:06:54.520> KZ<00:06:55.560> commitment<00:06:56.560> uh<00:06:56.759> KZ 00:06:57.309 --> 00:06:57.319 align:start position:0% provs and the call KZ commitment uh KZ 00:06:57.319 --> 00:06:59.230 align:start position:0% provs and the call KZ commitment uh KZ commitment<00:06:58.000> is<00:06:58.120> a<00:06:58.280> kind<00:06:58.560> of<00:06:58.759> polinomial 00:06:59.230 --> 00:06:59.240 align:start position:0% commitment is a kind of polinomial 00:06:59.240 --> 00:07:03.670 align:start position:0% commitment is a kind of polinomial commit<00:06:59.759> M<00:07:00.520> uh<00:07:00.680> which<00:07:00.840> is<00:07:01.080> used<00:07:01.440> in<00:07:01.639> DK<00:07:02.120> s<00:07:03.120> and 00:07:03.670 --> 00:07:03.680 align:start position:0% commit M uh which is used in DK s and 00:07:03.680 --> 00:07:08.430 align:start position:0% commit M uh which is used in DK s and pro<00:07:04.680> and<00:07:05.800> verifier<00:07:06.800> uh<00:07:06.960> communicate<00:07:07.680> with<00:07:08.280> uh 00:07:08.430 --> 00:07:08.440 align:start position:0% pro and verifier uh communicate with uh 00:07:08.440 --> 00:07:10.469 align:start position:0% pro and verifier uh communicate with uh each<00:07:08.680> other<00:07:09.319> and 00:07:10.469 --> 00:07:10.479 align:start position:0% each other and 00:07:10.479 --> 00:07:15.150 align:start position:0% each other and commitment<00:07:11.479> uh<00:07:11.680> Pro<00:07:12.599> compute<00:07:13.080> commitment<00:07:14.160> and 00:07:15.150 --> 00:07:15.160 align:start position:0% commitment uh Pro compute commitment and 00:07:15.160 --> 00:07:19.550 align:start position:0% commitment uh Pro compute commitment and send<00:07:15.639> to<00:07:15.919> proof<00:07:16.360> to<00:07:17.160> verifier<00:07:18.160> and<00:07:18.560> verifier 00:07:19.550 --> 00:07:19.560 align:start position:0% send to proof to verifier and verifier 00:07:19.560 --> 00:07:24.189 align:start position:0% send to proof to verifier and verifier uh<00:07:19.840> last<00:07:20.479> check<00:07:20.960> that<00:07:21.240> the<00:07:21.440> pairing<00:07:22.240> of<00:07:23.240> uh 00:07:24.189 --> 00:07:24.199 align:start position:0% uh last check that the pairing of uh 00:07:24.199 --> 00:07:26.909 align:start position:0% uh last check that the pairing of uh specific 00:07:26.909 --> 00:07:26.919 align:start position:0% 00:07:26.919 --> 00:07:31.790 align:start position:0% calculation<00:07:28.039> and<00:07:29.039> uh<00:07:29.560> probative<00:07:30.120> ZK<00:07:30.440> SNS<00:07:31.240> uses 00:07:31.790 --> 00:07:31.800 align:start position:0% calculation and uh probative ZK SNS uses 00:07:31.800 --> 00:07:33.589 align:start position:0% calculation and uh probative ZK SNS uses the 00:07:33.589 --> 00:07:33.599 align:start position:0% the 00:07:33.599 --> 00:07:38.270 align:start position:0% the uh<00:07:34.599> poal<00:07:35.240> commitment<00:07:36.199> uh<00:07:36.360> in<00:07:36.800> dkp<00:07:37.800> uh<00:07:38.000> like 00:07:38.270 --> 00:07:38.280 align:start position:0% uh poal commitment uh in dkp uh like 00:07:38.280 --> 00:07:41.909 align:start position:0% uh poal commitment uh in dkp uh like Marin<00:07:38.840> and<00:07:39.039> pron<00:07:39.599> and<00:07:39.800> so 00:07:41.909 --> 00:07:41.919 align:start position:0% Marin and pron and so 00:07:41.919 --> 00:07:45.629 align:start position:0% Marin and pron and so on<00:07:42.919> and<00:07:43.400> we<00:07:43.639> focus<00:07:44.199> on<00:07:44.520> the<00:07:44.800> mathematically 00:07:45.629 --> 00:07:45.639 align:start position:0% on and we focus on the mathematically 00:07:45.639 --> 00:07:50.469 align:start position:0% on and we focus on the mathematically aspects<00:07:46.159> of<00:07:46.680> collaborative<00:07:47.879> snacks<00:07:48.879> uh<00:07:49.479> it's 00:07:50.469 --> 00:07:50.479 align:start position:0% aspects of collaborative snacks uh it's 00:07:50.479 --> 00:07:55.990 align:start position:0% aspects of collaborative snacks uh it's it<00:07:51.159> uh<00:07:51.360> idea<00:07:51.759> is<00:07:52.000> very<00:07:52.360> simple<00:07:53.360> uh<00:07:54.120> the<00:07:54.360> pi<00:07:54.840> I<00:07:55.840> is 00:07:55.990 --> 00:07:56.000 align:start position:0% it uh idea is very simple uh the pi I is 00:07:56.000 --> 00:07:57.990 align:start position:0% it uh idea is very simple uh the pi I is a<00:07:56.319> proof 00:07:57.990 --> 00:07:58.000 align:start position:0% a proof 00:07:58.000 --> 00:08:02.589 align:start position:0% a proof uh<00:07:59.000> proof<00:07:59.800> generated<00:08:00.440> by<00:08:00.680> Shadow<00:08:01.280> input<00:08:02.159> and 00:08:02.589 --> 00:08:02.599 align:start position:0% uh proof generated by Shadow input and 00:08:02.599 --> 00:08:05.189 align:start position:0% uh proof generated by Shadow input and Pi<00:08:03.360> is<00:08:03.520> the<00:08:03.759> total 00:08:05.189 --> 00:08:05.199 align:start position:0% Pi is the total 00:08:05.199 --> 00:08:08.629 align:start position:0% Pi is the total proof<00:08:06.199> this<00:08:06.479> techniques<00:08:07.120> uses<00:08:07.599> the<00:08:07.759> linearity 00:08:08.629 --> 00:08:08.639 align:start position:0% proof this techniques uses the linearity 00:08:08.639 --> 00:08:13.390 align:start position:0% proof this techniques uses the linearity of<00:08:08.919> polinomial<00:08:09.879> commitment<00:08:10.879> and<00:08:11.720> uh<00:08:12.520> if<00:08:12.759> we 00:08:13.390 --> 00:08:13.400 align:start position:0% of polinomial commitment and uh if we 00:08:13.400 --> 00:08:15.550 align:start position:0% of polinomial commitment and uh if we generate<00:08:14.360> uh 00:08:15.550 --> 00:08:15.560 align:start position:0% generate uh 00:08:15.560 --> 00:08:19.990 align:start position:0% generate uh the<00:08:16.560> proof<00:08:17.319> uh<00:08:17.560> each<00:08:18.039> party<00:08:18.879> then<00:08:19.280> this<00:08:19.479> is<00:08:19.800> a 00:08:19.990 --> 00:08:20.000 align:start position:0% the proof uh each party then this is a 00:08:20.000 --> 00:08:24.029 align:start position:0% the proof uh each party then this is a share<00:08:20.440> of<00:08:20.759> total 00:08:24.029 --> 00:08:24.039 align:start position:0% 00:08:24.039 --> 00:08:28.510 align:start position:0% proof<00:08:25.039> however<00:08:25.879> if<00:08:26.080> we<00:08:26.280> want<00:08:26.520> to<00:08:27.440> uh<00:08:27.879> use 00:08:28.510 --> 00:08:28.520 align:start position:0% proof however if we want to uh use 00:08:28.520 --> 00:08:32.310 align:start position:0% proof however if we want to uh use collaborative<00:08:29.080> ZK<00:08:29.599> or<00:08:29.879> pmpc<00:08:30.639> on<00:08:31.320> blockchain 00:08:32.310 --> 00:08:32.320 align:start position:0% collaborative ZK or pmpc on blockchain 00:08:32.320 --> 00:08:35.909 align:start position:0% collaborative ZK or pmpc on blockchain uh<00:08:32.640> there<00:08:32.760> are<00:08:33.200> some<00:08:33.560> issues<00:08:34.479> to<00:08:34.640> be 00:08:35.909 --> 00:08:35.919 align:start position:0% uh there are some issues to be 00:08:35.919 --> 00:08:39.310 align:start position:0% uh there are some issues to be solved<00:08:36.919> the<00:08:37.120> figure<00:08:37.560> shows<00:08:37.959> that<00:08:38.200> DK<00:08:38.599> snacks 00:08:39.310 --> 00:08:39.320 align:start position:0% solved the figure shows that DK snacks 00:08:39.320 --> 00:08:43.230 align:start position:0% solved the figure shows that DK snacks and<00:08:39.640> NPC<00:08:40.640> additive<00:08:41.120> oriented<00:08:42.120> and<00:08:42.719> bitwise 00:08:43.230 --> 00:08:43.240 align:start position:0% and NPC additive oriented and bitwise 00:08:43.240 --> 00:08:44.870 align:start position:0% and NPC additive oriented and bitwise oriented 00:08:44.870 --> 00:08:44.880 align:start position:0% oriented 00:08:44.880 --> 00:08:48.630 align:start position:0% oriented NPC<00:08:45.880> uh<00:08:46.600> roughly<00:08:47.080> speaking<00:08:47.800> we<00:08:47.920> want<00:08:48.120> to 00:08:48.630 --> 00:08:48.640 align:start position:0% NPC uh roughly speaking we want to 00:08:48.640 --> 00:08:52.829 align:start position:0% NPC uh roughly speaking we want to develop<00:08:49.240> techniques<00:08:50.160> in<00:08:50.560> this<00:08:51.279> Vision<00:08:52.279> uh 00:08:52.829 --> 00:08:52.839 align:start position:0% develop techniques in this Vision uh 00:08:52.839 --> 00:09:00.550 align:start position:0% develop techniques in this Vision uh which<00:08:53.160> satisfice<00:08:54.040> all<00:08:54.399> three<00:08:55.279> uh<00:08:55.480> Legions 00:09:00.550 --> 00:09:00.560 align:start position:0% 00:09:00.560 --> 00:09:03.470 align:start position:0% the<00:09:00.760> first<00:09:01.360> issue<00:09:01.959> is<00:09:02.360> the<00:09:02.560> consistency<00:09:03.279> of 00:09:03.470 --> 00:09:03.480 align:start position:0% the first issue is the consistency of 00:09:03.480 --> 00:09:08.470 align:start position:0% the first issue is the consistency of secret<00:09:04.200> inputs<00:09:05.240> space<00:09:06.240> uh<00:09:06.760> in<00:09:07.040> space<00:09:08.040> uh<00:09:08.320> there 00:09:08.470 --> 00:09:08.480 align:start position:0% secret inputs space uh in space uh there 00:09:08.480 --> 00:09:11.230 align:start position:0% secret inputs space uh in space uh there are<00:09:08.839> pre<00:09:09.399> preprocessing<00:09:10.279> phase<00:09:10.600> and<00:09:10.800> online 00:09:11.230 --> 00:09:11.240 align:start position:0% are pre preprocessing phase and online 00:09:11.240 --> 00:09:14.150 align:start position:0% are pre preprocessing phase and online phase<00:09:12.120> so<00:09:12.600> we<00:09:12.800> have<00:09:12.959> to<00:09:13.279> ensure<00:09:13.720> that<00:09:13.920> the 00:09:14.150 --> 00:09:14.160 align:start position:0% phase so we have to ensure that the 00:09:14.160 --> 00:09:18.870 align:start position:0% phase so we have to ensure that the consistency<00:09:14.760> of<00:09:15.000> secret 00:09:18.870 --> 00:09:18.880 align:start position:0% 00:09:18.880 --> 00:09:21.509 align:start position:0% inputs<00:09:19.880> and<00:09:20.279> this<00:09:20.519> figure<00:09:20.880> shows<00:09:21.240> that 00:09:21.509 --> 00:09:21.519 align:start position:0% inputs and this figure shows that 00:09:21.519 --> 00:09:24.590 align:start position:0% inputs and this figure shows that conventional<00:09:22.040> NPC<00:09:22.839> and<00:09:23.079> the<00:09:23.640> public 00:09:24.590 --> 00:09:24.600 align:start position:0% conventional NPC and the public 00:09:24.600 --> 00:09:27.310 align:start position:0% conventional NPC and the public auditable 00:09:27.310 --> 00:09:27.320 align:start position:0% 00:09:27.320 --> 00:09:30.670 align:start position:0% NPC<00:09:28.320> and<00:09:28.519> the<00:09:28.680> second<00:09:29.040> issue<00:09:29.720> is<00:09:30.079> requirement 00:09:30.670 --> 00:09:30.680 align:start position:0% NPC and the second issue is requirement 00:09:30.680 --> 00:09:32.630 align:start position:0% NPC and the second issue is requirement for<00:09:30.920> the<00:09:31.079> general<00:09:31.480> purpose 00:09:32.630 --> 00:09:32.640 align:start position:0% for the general purpose 00:09:32.640 --> 00:09:35.310 align:start position:0% for the general purpose computations<00:09:33.640> speace<00:09:34.000> based<00:09:34.360> NPC<00:09:35.120> is 00:09:35.310 --> 00:09:35.320 align:start position:0% computations speace based NPC is 00:09:35.320 --> 00:09:37.870 align:start position:0% computations speace based NPC is suitable<00:09:35.800> for<00:09:36.240> arithmetic<00:09:36.839> operations 00:09:37.870 --> 00:09:37.880 align:start position:0% suitable for arithmetic operations 00:09:37.880 --> 00:09:41.509 align:start position:0% suitable for arithmetic operations however<00:09:38.880> uh<00:09:39.519> not<00:09:39.800> suitable<00:09:40.320> for<00:09:40.600> bitwise 00:09:41.509 --> 00:09:41.519 align:start position:0% however uh not suitable for bitwise 00:09:41.519 --> 00:09:43.190 align:start position:0% however uh not suitable for bitwise operations 00:09:43.190 --> 00:09:43.200 align:start position:0% operations 00:09:43.200 --> 00:09:47.790 align:start position:0% operations so<00:09:44.200> we<00:09:44.440> have<00:09:44.640> to<00:09:45.240> uh<00:09:46.160> you<00:09:46.440> have<00:09:46.600> to<00:09:46.920> implement 00:09:47.790 --> 00:09:47.800 align:start position:0% so we have to uh you have to implement 00:09:47.800 --> 00:09:51.269 align:start position:0% so we have to uh you have to implement such<00:09:48.600> uh<00:09:48.880> bitwise<00:09:49.760> operations<00:09:50.760> uh<00:09:50.880> which<00:09:51.040> is 00:09:51.269 --> 00:09:51.279 align:start position:0% such uh bitwise operations uh which is 00:09:51.279 --> 00:09:55.430 align:start position:0% such uh bitwise operations uh which is efficient<00:09:51.800> for<00:09:52.480> Speed<00:09:53.480> yeah<00:09:54.399> and<00:09:54.640> this<00:09:55.279> uh 00:09:55.430 --> 00:09:55.440 align:start position:0% efficient for Speed yeah and this uh 00:09:55.440 --> 00:10:00.030 align:start position:0% efficient for Speed yeah and this uh effects<00:09:56.480> on<00:09:57.480> constraint<00:09:58.000> generation<00:09:58.519> in<00:09:58.720> zkp 00:10:00.030 --> 00:10:00.040 align:start position:0% effects on constraint generation in zkp 00:10:00.040 --> 00:10:03.230 align:start position:0% effects on constraint generation in zkp because<00:10:00.399> of<00:10:00.720> restriction<00:10:01.680> of<00:10:02.000> finite<00:10:02.399> felds 00:10:03.230 --> 00:10:03.240 align:start position:0% because of restriction of finite felds 00:10:03.240 --> 00:10:06.110 align:start position:0% because of restriction of finite felds which<00:10:03.440> can<00:10:03.600> be<00:10:03.800> used<00:10:04.200> in 00:10:06.110 --> 00:10:06.120 align:start position:0% which can be used in 00:10:06.120 --> 00:10:10.350 align:start position:0% which can be used in zkp<00:10:07.120> and<00:10:07.399> next<00:10:08.360> uh<00:10:08.480> we<00:10:08.720> focus<00:10:09.160> on<00:10:09.360> the<00:10:09.560> first 00:10:10.350 --> 00:10:10.360 align:start position:0% zkp and next uh we focus on the first 00:10:10.360 --> 00:10:12.829 align:start position:0% zkp and next uh we focus on the first challenges<00:10:11.360> the<00:10:11.519> secure<00:10:11.959> consistency<00:10:12.640> of 00:10:12.829 --> 00:10:12.839 align:start position:0% challenges the secure consistency of 00:10:12.839 --> 00:10:15.430 align:start position:0% challenges the secure consistency of secret 00:10:15.430 --> 00:10:15.440 align:start position:0% 00:10:15.440 --> 00:10:21.030 align:start position:0% inputs<00:10:16.440> in<00:10:16.959> MPC<00:10:17.959> uh<00:10:18.920> in<00:10:19.360> especially<00:10:19.839> in<00:10:20.040> space 00:10:21.030 --> 00:10:21.040 align:start position:0% inputs in MPC uh in especially in space 00:10:21.040 --> 00:10:24.750 align:start position:0% inputs in MPC uh in especially in space uh<00:10:21.200> the<00:10:21.440> data<00:10:22.120> input<00:10:22.640> data<00:10:23.399> uh<00:10:23.640> is<00:10:24.000> generated 00:10:24.750 --> 00:10:24.760 align:start position:0% uh the data input data uh is generated 00:10:24.760 --> 00:10:29.350 align:start position:0% uh the data input data uh is generated by<00:10:25.040> using<00:10:25.640> auxilary<00:10:26.399> data<00:10:27.399> uh<00:10:27.839> created<00:10:28.720> in<00:10:29.000> PR 00:10:29.350 --> 00:10:29.360 align:start position:0% by using auxilary data uh created in PR 00:10:29.360 --> 00:10:33.630 align:start position:0% by using auxilary data uh created in PR processing<00:10:29.920> phase<00:10:30.839> so<00:10:31.640> we<00:10:31.920> have<00:10:32.120> to 00:10:33.630 --> 00:10:33.640 align:start position:0% processing phase so we have to 00:10:33.640 --> 00:10:37.710 align:start position:0% processing phase so we have to uh<00:10:34.640> we<00:10:34.880> have<00:10:35.040> to<00:10:35.160> be<00:10:35.360> more<00:10:35.639> cautious<00:10:36.240> than 00:10:37.710 --> 00:10:37.720 align:start position:0% uh we have to be more cautious than 00:10:37.720 --> 00:10:42.629 align:start position:0% uh we have to be more cautious than usual<00:10:38.720> the<00:10:39.240> committed<00:10:40.000> data<00:10:41.000> uh<00:10:41.440> sorry<00:10:42.440> we 00:10:42.629 --> 00:10:42.639 align:start position:0% usual the committed data uh sorry we 00:10:42.639 --> 00:10:46.350 align:start position:0% usual the committed data uh sorry we solve<00:10:43.040> these<00:10:43.360> problems<00:10:43.959> by<00:10:44.160> using 00:10:46.350 --> 00:10:46.360 align:start position:0% solve these problems by using 00:10:46.360 --> 00:10:48.110 align:start position:0% solve these problems by using commitment 00:10:48.110 --> 00:10:48.120 align:start position:0% commitment 00:10:48.120 --> 00:10:54.110 align:start position:0% commitment uh<00:10:49.440> we<00:10:50.440> we<00:10:50.720> commit<00:10:51.480> uh<00:10:51.680> input<00:10:52.320> data<00:10:53.200> uh<00:10:53.680> before 00:10:54.110 --> 00:10:54.120 align:start position:0% uh we we commit uh input data uh before 00:10:54.120 --> 00:10:58.069 align:start position:0% uh we we commit uh input data uh before the<00:10:54.480> input<00:10:54.880> shares<00:10:56.200> generated 00:10:58.069 --> 00:10:58.079 align:start position:0% the input shares generated 00:10:58.079 --> 00:10:59.829 align:start position:0% the input shares generated so<00:10:59.079> and 00:10:59.829 --> 00:10:59.839 align:start position:0% so and 00:10:59.839 --> 00:11:04.629 align:start position:0% so and at<00:11:00.279> add<00:11:01.040> at<00:11:01.399> constraint<00:11:02.160> to<00:11:02.480> dkp<00:11:03.440> so<00:11:03.839> we<00:11:04.000> can 00:11:04.629 --> 00:11:04.639 align:start position:0% at add at constraint to dkp so we can 00:11:04.639 --> 00:11:07.990 align:start position:0% at add at constraint to dkp so we can verify<00:11:05.160> that<00:11:05.519> the 00:11:07.990 --> 00:11:08.000 align:start position:0% verify that the 00:11:08.000 --> 00:11:11.590 align:start position:0% verify that the uh<00:11:09.000> data<00:11:09.480> in<00:11:09.959> preprocessing<00:11:10.959> and<00:11:11.200> online 00:11:11.590 --> 00:11:11.600 align:start position:0% uh data in preprocessing and online 00:11:11.600 --> 00:11:16.030 align:start position:0% uh data in preprocessing and online phase<00:11:12.360> and<00:11:12.600> the<00:11:13.399> proving<00:11:13.959> phase<00:11:14.639> is<00:11:15.320> uh<00:11:15.800> must 00:11:16.030 --> 00:11:16.040 align:start position:0% phase and the proving phase is uh must 00:11:16.040 --> 00:11:18.190 align:start position:0% phase and the proving phase is uh must be 00:11:18.190 --> 00:11:18.200 align:start position:0% be 00:11:18.200 --> 00:11:22.190 align:start position:0% be same<00:11:19.200> and<00:11:19.720> we<00:11:19.920> choose<00:11:20.320> p<00:11:20.639> and<00:11:20.880> commitment<00:11:21.880> uh 00:11:22.190 --> 00:11:22.200 align:start position:0% same and we choose p and commitment uh 00:11:22.200 --> 00:11:23.110 align:start position:0% same and we choose p and commitment uh to 00:11:23.110 --> 00:11:23.120 align:start position:0% to 00:11:23.120 --> 00:11:25.910 align:start position:0% to implement 00:11:25.910 --> 00:11:25.920 align:start position:0% implement 00:11:25.920 --> 00:11:30.150 align:start position:0% implement and<00:11:26.920> there<00:11:27.040> are<00:11:27.760> some<00:11:28.760> constraints 00:11:30.150 --> 00:11:30.160 align:start position:0% and there are some constraints 00:11:30.160 --> 00:11:34.829 align:start position:0% and there are some constraints uh<00:11:30.360> we<00:11:30.560> implemented<00:11:31.360> for<00:11:32.160> example<00:11:33.240> uh<00:11:34.240> L 00:11:34.829 --> 00:11:34.839 align:start position:0% uh we implemented for example uh L 00:11:34.839 --> 00:11:38.629 align:start position:0% uh we implemented for example uh L constraint<00:11:35.800> and<00:11:36.120> and<00:11:36.399> so 00:11:38.629 --> 00:11:38.639 align:start position:0% 00:11:38.639 --> 00:11:42.110 align:start position:0% on<00:11:39.639> and<00:11:40.200> we<00:11:40.399> focus<00:11:40.800> on<00:11:41.000> second<00:11:41.440> changes 00:11:42.110 --> 00:11:42.120 align:start position:0% on and we focus on second changes 00:11:42.120 --> 00:11:44.350 align:start position:0% on and we focus on second changes bitwise<00:11:42.639> operation 00:11:44.350 --> 00:11:44.360 align:start position:0% bitwise operation 00:11:44.360 --> 00:11:47.829 align:start position:0% bitwise operation support<00:11:45.360> Recall<00:11:45.920> why<00:11:46.519> uh<00:11:46.680> bitwise<00:11:47.200> operation 00:11:47.829 --> 00:11:47.839 align:start position:0% support Recall why uh bitwise operation 00:11:47.839 --> 00:11:50.710 align:start position:0% support Recall why uh bitwise operation difficult<00:11:48.079> in<00:11:48.560> space<00:11:49.560> uh<00:11:49.720> space<00:11:50.160> uses 00:11:50.710 --> 00:11:50.720 align:start position:0% difficult in space uh space uses 00:11:50.720 --> 00:11:54.389 align:start position:0% difficult in space uh space uses additive<00:11:51.120> secret<00:11:51.519> sharing<00:11:52.200> so<00:11:53.040> bit<00:11:53.480> de<00:11:53.639> compos 00:11:54.389 --> 00:11:54.399 align:start position:0% additive secret sharing so bit de compos 00:11:54.399 --> 00:11:58.790 align:start position:0% additive secret sharing so bit de compos and<00:11:54.800> comparison<00:11:55.800> uh<00:11:56.000> such<00:11:56.839> operation<00:11:57.839> U<00:11:58.600> will 00:11:58.790 --> 00:11:58.800 align:start position:0% and comparison uh such operation U will 00:11:58.800 --> 00:12:04.389 align:start position:0% and comparison uh such operation U will be<00:11:59.000> more<00:11:59.279> more<00:11:59.920> costly<00:12:00.920> than<00:12:01.920> uh<00:12:02.399> addition<00:12:03.040> and 00:12:04.389 --> 00:12:04.399 align:start position:0% be more more costly than uh addition and 00:12:04.399 --> 00:12:07.670 align:start position:0% be more more costly than uh addition and multiplication<00:12:05.399> so<00:12:05.720> if<00:12:05.839> we<00:12:06.040> using<00:12:06.959> uh<00:12:07.200> larger 00:12:07.670 --> 00:12:07.680 align:start position:0% multiplication so if we using uh larger 00:12:07.680 --> 00:12:11.829 align:start position:0% multiplication so if we using uh larger finite<00:12:08.040> Fields<00:12:09.040> then<00:12:09.560> more<00:12:10.560> constraint<00:12:11.279> needs 00:12:11.829 --> 00:12:11.839 align:start position:0% finite Fields then more constraint needs 00:12:11.839 --> 00:12:15.470 align:start position:0% finite Fields then more constraint needs so<00:12:12.720> we<00:12:12.959> can't<00:12:13.880> uh<00:12:14.040> it<00:12:14.160> is<00:12:14.600> difficult<00:12:14.839> to 00:12:15.470 --> 00:12:15.480 align:start position:0% so we can't uh it is difficult to 00:12:15.480 --> 00:12:21.269 align:start position:0% so we can't uh it is difficult to implement<00:12:16.120> bitwise 00:12:21.269 --> 00:12:21.279 align:start position:0% 00:12:21.279 --> 00:12:25.990 align:start position:0% operations<00:12:22.279> uh<00:12:23.320> implementation<00:12:24.320> uh<00:12:24.560> we<00:12:25.000> added 00:12:25.990 --> 00:12:26.000 align:start position:0% operations uh implementation uh we added 00:12:26.000 --> 00:12:28.710 align:start position:0% operations uh implementation uh we added especially<00:12:26.839> uh<00:12:27.079> equality<00:12:27.600> zero<00:12:27.920> test<00:12:28.440> and 00:12:28.710 --> 00:12:28.720 align:start position:0% especially uh equality zero test and 00:12:28.720 --> 00:12:33.110 align:start position:0% especially uh equality zero test and comparison<00:12:29.480> test<00:12:30.440> and<00:12:31.199> uh<00:12:32.199> bit 00:12:33.110 --> 00:12:33.120 align:start position:0% comparison test and uh bit 00:12:33.120 --> 00:12:37.509 align:start position:0% comparison test and uh bit decomposition<00:12:34.120> uh<00:12:34.440> on<00:12:34.839> speace<00:12:35.360> based 00:12:37.509 --> 00:12:37.519 align:start position:0% decomposition uh on speace based 00:12:37.519 --> 00:12:40.910 align:start position:0% decomposition uh on speace based MPC<00:12:38.519> and<00:12:38.920> if<00:12:39.440> we<00:12:39.680> also<00:12:40.000> implemented<00:12:40.560> share 00:12:40.910 --> 00:12:40.920 align:start position:0% MPC and if we also implemented share 00:12:40.920 --> 00:12:43.910 align:start position:0% MPC and if we also implemented share conversion<00:12:41.800> protocol<00:12:42.800> because<00:12:43.440> Pedas<00:12:43.760> and 00:12:43.910 --> 00:12:43.920 align:start position:0% conversion protocol because Pedas and 00:12:43.920 --> 00:12:50.509 align:start position:0% conversion protocol because Pedas and commitment<00:12:44.440> needs<00:12:45.079> uh<00:12:45.279> two<00:12:45.600> different<00:12:46.600> finite 00:12:50.509 --> 00:12:50.519 align:start position:0% 00:12:50.519 --> 00:12:54.949 align:start position:0% fears<00:12:51.519> and<00:12:52.000> let's<00:12:53.000> look<00:12:53.480> the<00:12:53.959> uh<00:12:54.160> algorithm 00:12:54.949 --> 00:12:54.959 align:start position:0% fears and let's look the uh algorithm 00:12:54.959 --> 00:13:00.150 align:start position:0% fears and let's look the uh algorithm detail<00:12:55.959> this<00:12:56.519> shows<00:12:57.040> the<00:12:57.399> equality<00:12:57.920> zero<00:12:58.279> test 00:13:00.150 --> 00:13:00.160 align:start position:0% detail this shows the equality zero test 00:13:00.160 --> 00:13:04.470 align:start position:0% detail this shows the equality zero test let's<00:13:00.440> imagine<00:13:01.120> that<00:13:01.519> you<00:13:01.800> have<00:13:02.560> the<00:13:03.560> data<00:13:03.959> X 00:13:04.470 --> 00:13:04.480 align:start position:0% let's imagine that you have the data X 00:13:04.480 --> 00:13:08.829 align:start position:0% let's imagine that you have the data X of<00:13:05.160> share<00:13:05.600> of<00:13:05.839> data<00:13:06.160> X<00:13:07.000> and<00:13:07.480> we<00:13:07.639> want<00:13:07.800> to<00:13:08.680> uh 00:13:08.829 --> 00:13:08.839 align:start position:0% of share of data X and we want to uh 00:13:08.839 --> 00:13:11.750 align:start position:0% of share of data X and we want to uh calculate<00:13:09.680> X<00:13:10.079> is<00:13:10.360> zero<00:13:10.720> or 00:13:11.750 --> 00:13:11.760 align:start position:0% calculate X is zero or 00:13:11.760 --> 00:13:15.790 align:start position:0% calculate X is zero or not<00:13:12.800> firstly<00:13:13.800> we<00:13:14.279> generate<00:13:14.800> the<00:13:14.959> landom<00:13:15.360> share 00:13:15.790 --> 00:13:15.800 align:start position:0% not firstly we generate the landom share 00:13:15.800 --> 00:13:20.310 align:start position:0% not firstly we generate the landom share r<00:13:16.279> with<00:13:17.160> uh<00:13:17.839> Associated<00:13:18.560> bit<00:13:18.959> with<00:13:19.399> bwise 00:13:20.310 --> 00:13:20.320 align:start position:0% r with uh Associated bit with bwise 00:13:20.320 --> 00:13:26.150 align:start position:0% r with uh Associated bit with bwise share<00:13:21.320> and<00:13:22.279> uh<00:13:22.720> calculate<00:13:23.240> X+<00:13:23.800> R<00:13:24.160> and<00:13:24.519> publishe 00:13:26.150 --> 00:13:26.160 align:start position:0% share and uh calculate X+ R and publishe 00:13:26.160 --> 00:13:31.870 align:start position:0% share and uh calculate X+ R and publishe them<00:13:27.160> uh<00:13:27.360> this<00:13:27.560> denote<00:13:27.920> as<00:13:28.160> C<00:13:29.600> if<00:13:29.959> x<00:13:30.440> is<00:13:30.880> zero 00:13:31.870 --> 00:13:31.880 align:start position:0% them uh this denote as C if x is zero 00:13:31.880 --> 00:13:36.750 align:start position:0% them uh this denote as C if x is zero then<00:13:32.399> R<00:13:33.040> and<00:13:33.320> C<00:13:34.120> must<00:13:34.360> be<00:13:34.800> same<00:13:35.800> so<00:13:36.079> we<00:13:36.240> use<00:13:36.560> this 00:13:36.750 --> 00:13:36.760 align:start position:0% then R and C must be same so we use this 00:13:36.760 --> 00:13:42.310 align:start position:0% then R and C must be same so we use this fact<00:13:37.560> and<00:13:38.600> calculate<00:13:39.600> uh<00:13:40.279> AI<00:13:41.279> uh<00:13:41.760> this<00:13:41.920> is 00:13:42.310 --> 00:13:42.320 align:start position:0% fact and calculate uh AI uh this is 00:13:42.320 --> 00:13:47.790 align:start position:0% fact and calculate uh AI uh this is bitwise<00:13:43.519> and<00:13:44.519> output<00:13:45.320> the 00:13:47.790 --> 00:13:47.800 align:start position:0% bitwise and output the 00:13:47.800 --> 00:13:53.470 align:start position:0% bitwise and output the uh<00:13:48.800> total<00:13:49.199> an<00:13:49.720> of<00:13:49.920> all<00:13:50.759> AI<00:13:51.759> uh<00:13:51.959> this<00:13:52.199> means<00:13:53.000> uh 00:13:53.470 --> 00:13:53.480 align:start position:0% uh total an of all AI uh this means uh 00:13:53.480 --> 00:13:56.710 align:start position:0% uh total an of all AI uh this means uh one<00:13:53.920> if<00:13:54.120> xal<00:13:54.839> is<00:13:55.079> zero<00:13:55.680> and<00:13:55.959> otherwise<00:13:56.560> this 00:13:56.710 --> 00:13:56.720 align:start position:0% one if xal is zero and otherwise this 00:13:56.720 --> 00:14:01.030 align:start position:0% one if xal is zero and otherwise this means<00:13:57.079> zero 00:14:01.030 --> 00:14:01.040 align:start position:0% 00:14:01.040 --> 00:14:02.350 align:start position:0% and 00:14:02.350 --> 00:14:02.360 align:start position:0% and 00:14:02.360 --> 00:14:04.389 align:start position:0% and surprisingly<00:14:03.360> uh 00:14:04.389 --> 00:14:04.399 align:start position:0% surprisingly uh 00:14:04.399 --> 00:14:09.230 align:start position:0% surprisingly uh bitwise<00:14:05.399> operation<00:14:06.360> uh<00:14:06.720> doesn't<00:14:07.720> uh<00:14:08.199> need<00:14:08.519> for 00:14:09.230 --> 00:14:09.240 align:start position:0% bitwise operation uh doesn't uh need for 00:14:09.240 --> 00:14:10.389 align:start position:0% bitwise operation uh doesn't uh need for additional 00:14:10.389 --> 00:14:10.399 align:start position:0% additional 00:14:10.399 --> 00:14:14.230 align:start position:0% additional constraint<00:14:11.399> uh<00:14:11.800> for<00:14:12.199> each 00:14:14.230 --> 00:14:14.240 align:start position:0% constraint uh for each 00:14:14.240 --> 00:14:17.509 align:start position:0% constraint uh for each party<00:14:15.240> even<00:14:15.680> if 00:14:17.509 --> 00:14:17.519 align:start position:0% party even if 00:14:17.519 --> 00:14:21.150 align:start position:0% party even if uh<00:14:18.519> this<00:14:18.759> can<00:14:18.920> be<00:14:19.160> considered<00:14:19.759> as<00:14:20.320> separation 00:14:21.150 --> 00:14:21.160 align:start position:0% uh this can be considered as separation 00:14:21.160 --> 00:14:26.910 align:start position:0% uh this can be considered as separation of<00:14:21.440> dkp<00:14:22.000> programs<00:14:22.680> and<00:14:23.199> the<00:14:24.600> uh<00:14:25.600> NPC 00:14:26.910 --> 00:14:26.920 align:start position:0% of dkp programs and the uh NPC 00:14:26.920 --> 00:14:33.269 align:start position:0% of dkp programs and the uh NPC programs<00:14:27.920> so<00:14:28.279> we<00:14:28.519> focus<00:14:29.199> on<00:14:29.880> each 00:14:33.269 --> 00:14:33.279 align:start position:0% 00:14:33.279 --> 00:14:36.629 align:start position:0% Legions<00:14:34.279> and<00:14:34.560> next<00:14:35.240> we<00:14:35.360> want<00:14:35.560> to<00:14:35.759> show 00:14:36.629 --> 00:14:36.639 align:start position:0% Legions and next we want to show 00:14:36.639 --> 00:14:40.590 align:start position:0% Legions and next we want to show applications<00:14:37.639> and<00:14:37.880> demo 00:14:40.590 --> 00:14:40.600 align:start position:0% 00:14:40.600 --> 00:14:45.430 align:start position:0% video<00:14:41.600> we<00:14:41.880> developed<00:14:42.680> a<00:14:43.240> we<00:14:43.800> game<00:14:44.720> Sorry<00:14:45.199> game 00:14:45.430 --> 00:14:45.440 align:start position:0% video we developed a we game Sorry game 00:14:45.440 --> 00:14:48.670 align:start position:0% video we developed a we game Sorry game master<00:14:45.839> free<00:14:46.120> well<00:14:46.320> of<00:14:46.959> game<00:14:47.959> uh<00:14:48.120> this<00:14:48.279> flow 00:14:48.670 --> 00:14:48.680 align:start position:0% master free well of game uh this flow 00:14:48.680 --> 00:14:51.590 align:start position:0% master free well of game uh this flow chart<00:14:48.959> shows<00:14:49.399> that<00:14:50.160> uh<00:14:50.360> well<00:14:50.600> of<00:14:50.800> game<00:14:50.959> flow 00:14:51.590 --> 00:14:51.600 align:start position:0% chart shows that uh well of game flow 00:14:51.600 --> 00:14:56.829 align:start position:0% chart shows that uh well of game flow chart<00:14:52.600> wh<00:14:52.880> of<00:14:53.079> game<00:14:53.360> for<00:14:54.079> well<00:14:55.079> game<00:14:55.639> is<00:14:56.120> a<00:14:56.519> a 00:14:56.829 --> 00:14:56.839 align:start position:0% chart wh of game for well game is a a 00:14:56.839 --> 00:15:00.509 align:start position:0% chart wh of game for well game is a a game<00:14:57.720> uh<00:14:57.880> the<00:14:58.040> players<00:14:58.680> are<00:14:59.079> divided<00:14:59.600> into<00:15:00.079> two 00:15:00.509 --> 00:15:00.519 align:start position:0% game uh the players are divided into two 00:15:00.519 --> 00:15:04.110 align:start position:0% game uh the players are divided into two teams<00:15:01.440> one<00:15:01.600> is<00:15:01.800> Bard<00:15:02.360> team<00:15:03.040> and<00:15:03.320> the<00:15:03.480> other<00:15:03.839> is 00:15:04.110 --> 00:15:04.120 align:start position:0% teams one is Bard team and the other is 00:15:04.120 --> 00:15:10.110 align:start position:0% teams one is Bard team and the other is we<00:15:04.920> team<00:15:05.920> and<00:15:06.600> prayer<00:15:07.600> uh<00:15:07.959> whose<00:15:08.440> Ro<00:15:08.920> is<00:15:09.160> hidden 00:15:10.110 --> 00:15:10.120 align:start position:0% we team and prayer uh whose Ro is hidden 00:15:10.120 --> 00:15:14.030 align:start position:0% we team and prayer uh whose Ro is hidden and<00:15:11.000> uh<00:15:12.160> by 00:15:14.030 --> 00:15:14.040 align:start position:0% and uh by 00:15:14.040 --> 00:15:19.509 align:start position:0% and uh by using<00:15:15.040> specific<00:15:16.000> Ro<00:15:16.600> action<00:15:17.320> and<00:15:17.800> voting<00:15:18.800> and 00:15:19.509 --> 00:15:19.519 align:start position:0% using specific Ro action and voting and 00:15:19.519 --> 00:15:21.069 align:start position:0% using specific Ro action and voting and uh<00:15:19.680> player<00:15:20.120> aim 00:15:21.069 --> 00:15:21.079 align:start position:0% uh player aim 00:15:21.079 --> 00:15:25.629 align:start position:0% uh player aim to<00:15:22.079> victory<00:15:22.800> for<00:15:23.560> their 00:15:25.629 --> 00:15:25.639 align:start position:0% to victory for their 00:15:25.639 --> 00:15:29.910 align:start position:0% to victory for their teams<00:15:26.759> usually<00:15:27.759> we<00:15:28.040> of<00:15:28.279> game<00:15:28.800> is<00:15:29.000> is<00:15:29.199> necessary 00:15:29.910 --> 00:15:29.920 align:start position:0% teams usually we of game is is necessary 00:15:29.920 --> 00:15:31.069 align:start position:0% teams usually we of game is is necessary for 00:15:31.069 --> 00:15:31.079 align:start position:0% for 00:15:31.079 --> 00:15:34.430 align:start position:0% for necessary<00:15:32.160> sorry<00:15:33.160> game<00:15:33.399> master<00:15:33.800> is<00:15:34.000> necessary 00:15:34.430 --> 00:15:34.440 align:start position:0% necessary sorry game master is necessary 00:15:34.440 --> 00:15:38.150 align:start position:0% necessary sorry game master is necessary for<00:15:34.680> we<00:15:34.920> of<00:15:35.160> game<00:15:36.040> however<00:15:36.519> we<00:15:36.880> developed<00:15:37.880> uh 00:15:38.150 --> 00:15:38.160 align:start position:0% for we of game however we developed uh 00:15:38.160 --> 00:15:45.350 align:start position:0% for we of game however we developed uh game<00:15:38.399> master<00:15:38.800> free<00:15:39.319> wealth<00:15:39.800> game<00:15:40.759> by<00:15:41.079> our<00:15:41.759> CK 00:15:45.350 --> 00:15:45.360 align:start position:0% 00:15:45.360 --> 00:15:49.030 align:start position:0% MPC<00:15:46.360> here<00:15:46.519> is<00:15:46.680> the<00:15:46.920> list<00:15:47.519> of<00:15:47.800> we<00:15:48.160> implemented 00:15:49.030 --> 00:15:49.040 align:start position:0% MPC here is the list of we implemented 00:15:49.040 --> 00:15:52.910 align:start position:0% MPC here is the list of we implemented the<00:15:49.720> protocol<00:15:50.440> in<00:15:50.839> the<00:15:51.360> DK 00:15:52.910 --> 00:15:52.920 align:start position:0% the protocol in the DK 00:15:52.920 --> 00:15:57.189 align:start position:0% the protocol in the DK where<00:15:53.920> Ro<00:15:54.600> assignment<00:15:55.600> Anonymous<00:15:56.199> voting 00:15:57.189 --> 00:15:57.199 align:start position:0% where Ro assignment Anonymous voting 00:15:57.199 --> 00:16:01.710 align:start position:0% where Ro assignment Anonymous voting where<00:15:57.440> of<00:15:57.639> f<00:15:58.600> for<00:15:59.160> ter<00:15:59.480> check<00:16:00.440> and<00:16:00.680> victory 00:16:01.710 --> 00:16:01.720 align:start position:0% where of f for ter check and victory 00:16:01.720 --> 00:16:05.189 align:start position:0% where of f for ter check and victory condition<00:16:02.720> such<00:16:03.040> computation<00:16:03.880> is<00:16:04.240> done<00:16:04.639> by 00:16:05.189 --> 00:16:05.199 align:start position:0% condition such computation is done by 00:16:05.199 --> 00:16:09.509 align:start position:0% condition such computation is done by MPC<00:16:06.199> and<00:16:06.600> uh<00:16:06.959> we<00:16:07.120> can<00:16:07.440> check<00:16:08.160> the<00:16:08.480> con<00:16:09.160> check 00:16:09.509 --> 00:16:09.519 align:start position:0% MPC and uh we can check the con check 00:16:09.519 --> 00:16:15.550 align:start position:0% MPC and uh we can check the con check the<00:16:10.160> correctness<00:16:11.120> of<00:16:11.440> such 00:16:15.550 --> 00:16:15.560 align:start position:0% 00:16:15.560 --> 00:16:19.269 align:start position:0% actions<00:16:16.560> let's<00:16:16.839> pick<00:16:17.120> up<00:16:17.399> the<00:16:17.959> ler<00:16:18.440> assignment 00:16:19.269 --> 00:16:19.279 align:start position:0% actions let's pick up the ler assignment 00:16:19.279 --> 00:16:20.870 align:start position:0% actions let's pick up the ler assignment in 00:16:20.870 --> 00:16:20.880 align:start position:0% in 00:16:20.880 --> 00:16:26.110 align:start position:0% in dkw<00:16:21.880> uh<00:16:22.519> players<00:16:23.519> inputs<00:16:24.079> the<00:16:24.519> shuffle<00:16:25.120> Matrix 00:16:26.110 --> 00:16:26.120 align:start position:0% dkw uh players inputs the shuffle Matrix 00:16:26.120 --> 00:16:30.150 align:start position:0% dkw uh players inputs the shuffle Matrix uh<00:16:26.399> by<00:16:26.880> secret<00:16:27.759> shares 00:16:30.150 --> 00:16:30.160 align:start position:0% uh by secret shares 00:16:30.160 --> 00:16:35.509 align:start position:0% uh by secret shares and<00:16:31.160> then<00:16:31.720> compute<00:16:32.720> uh<00:16:33.199> the<00:16:33.360> lws<00:16:34.279> by<00:16:34.519> grouping 00:16:35.509 --> 00:16:35.519 align:start position:0% and then compute uh the lws by grouping 00:16:35.519 --> 00:16:39.110 align:start position:0% and then compute uh the lws by grouping protocol<00:16:36.839> and<00:16:37.839> they<00:16:38.079> generate<00:16:39.000> uh 00:16:39.110 --> 00:16:39.120 align:start position:0% protocol and they generate uh 00:16:39.120 --> 00:16:42.030 align:start position:0% protocol and they generate uh collaborative<00:16:39.839> proof<00:16:40.360> of<00:16:40.720> L<00:16:41.160> assignment 00:16:42.030 --> 00:16:42.040 align:start position:0% collaborative proof of L assignment 00:16:42.040 --> 00:16:46.470 align:start position:0% collaborative proof of L assignment protocol<00:16:43.040> then<00:16:43.959> uh<00:16:44.240> if<00:16:44.440> the<00:16:44.639> verification<00:16:45.480> is 00:16:46.470 --> 00:16:46.480 align:start position:0% protocol then uh if the verification is 00:16:46.480 --> 00:16:51.230 align:start position:0% protocol then uh if the verification is correct<00:16:47.480> uh<00:16:47.720> then<00:16:48.759> they<00:16:49.759> they<00:16:49.880> are<00:16:50.240> informed 00:16:51.230 --> 00:16:51.240 align:start position:0% correct uh then they they are informed 00:16:51.240 --> 00:16:54.069 align:start position:0% correct uh then they they are informed uh<00:16:51.560> their 00:16:54.069 --> 00:16:54.079 align:start position:0% 00:16:54.079 --> 00:17:00.110 align:start position:0% RS<00:16:55.079> this<00:16:55.360> is<00:16:56.000> a<00:16:56.480> demo<00:16:56.880> video<00:16:57.680> of<00:16:58.160> our 00:17:00.110 --> 00:17:00.120 align:start position:0% RS this is a demo video of our 00:17:00.120 --> 00:17:03.829 align:start position:0% RS this is a demo video of our bpc<00:17:01.120> uh<00:17:01.639> this<00:17:01.800> is<00:17:02.399> four<00:17:02.759> people 00:17:03.829 --> 00:17:03.839 align:start position:0% bpc uh this is four people 00:17:03.839 --> 00:17:05.789 align:start position:0% bpc uh this is four people case 00:17:05.789 --> 00:17:05.799 align:start position:0% case 00:17:05.799 --> 00:17:12.150 align:start position:0% case uh<00:17:06.799> the<00:17:06.959> Alice<00:17:07.799> and<00:17:08.240> Bob<00:17:09.240> and<00:17:09.839> charie<00:17:10.839> and<00:17:11.160> Dave 00:17:12.150 --> 00:17:12.160 align:start position:0% uh the Alice and Bob and charie and Dave 00:17:12.160 --> 00:17:16.789 align:start position:0% uh the Alice and Bob and charie and Dave they<00:17:12.400> legister<00:17:13.600> name<00:17:14.600> and<00:17:14.799> then<00:17:15.039> set<00:17:15.360> up<00:17:15.799> began 00:17:16.789 --> 00:17:16.799 align:start position:0% they legister name and then set up began 00:17:16.799 --> 00:17:18.470 align:start position:0% they legister name and then set up began uh<00:17:17.400> right<00:17:17.640> the 00:17:18.470 --> 00:17:18.480 align:start position:0% uh right the 00:17:18.480 --> 00:17:22.390 align:start position:0% uh right the way<00:17:19.480> and<00:17:19.640> the<00:17:19.760> L<00:17:20.280> assignment<00:17:21.280> protocol<00:17:22.039> is 00:17:22.390 --> 00:17:22.400 align:start position:0% way and the L assignment protocol is 00:17:22.400 --> 00:17:27.669 align:start position:0% way and the L assignment protocol is long<00:17:23.360> is<00:17:23.679> running<00:17:25.039> and<00:17:26.039> proof<00:17:26.760> here<00:17:27.120> is<00:17:27.280> proof 00:17:27.669 --> 00:17:27.679 align:start position:0% long is running and proof here is proof 00:17:27.679 --> 00:17:29.830 align:start position:0% long is running and proof here is proof generation 00:17:29.830 --> 00:17:29.840 align:start position:0% generation 00:17:29.840 --> 00:17:36.350 align:start position:0% generation by 00:17:36.350 --> 00:17:36.360 align:start position:0% 00:17:36.360 --> 00:17:38.909 align:start position:0% MPC<00:17:37.360> after<00:17:37.720> the<00:17:37.960> proof 00:17:38.909 --> 00:17:38.919 align:start position:0% MPC after the proof 00:17:38.919 --> 00:17:43.789 align:start position:0% MPC after the proof generation<00:17:39.919> uh<00:17:40.280> the<00:17:40.880> proof<00:17:41.960> is 00:17:43.789 --> 00:17:43.799 align:start position:0% generation uh the proof is 00:17:43.799 --> 00:17:45.950 align:start position:0% generation uh the proof is verified 00:17:45.950 --> 00:17:45.960 align:start position:0% verified 00:17:45.960 --> 00:17:49.669 align:start position:0% verified and<00:17:46.960> they<00:17:47.160> are<00:17:48.160> uh<00:17:48.480> Alice<00:17:48.960> is 00:17:49.669 --> 00:17:49.679 align:start position:0% and they are uh Alice is 00:17:49.679 --> 00:17:54.070 align:start position:0% and they are uh Alice is fortun<00:17:50.679> uh<00:17:50.919> both<00:17:51.840> Is<00:17:52.160> wealth<00:17:52.960> and<00:17:53.120> Charis<00:17:53.799> and 00:17:54.070 --> 00:17:54.080 align:start position:0% fortun uh both Is wealth and Charis and 00:17:54.080 --> 00:17:55.909 align:start position:0% fortun uh both Is wealth and Charis and Dave<00:17:54.679> are 00:17:55.909 --> 00:17:55.919 align:start position:0% Dave are 00:17:55.919 --> 00:17:59.990 align:start position:0% Dave are villagers<00:17:56.919> and<00:17:57.080> the<00:17:57.200> night<00:17:57.559> pH<00:17:58.480> uh<00:17:58.679> they<00:17:58.919> they 00:17:59.990 --> 00:18:00.000 align:start position:0% villagers and the night pH uh they they 00:18:00.000 --> 00:18:03.390 align:start position:0% villagers and the night pH uh they they do<00:18:01.000> uh<00:18:01.679> special 00:18:03.390 --> 00:18:03.400 align:start position:0% do uh special 00:18:03.400 --> 00:18:10.310 align:start position:0% do uh special action<00:18:04.400> AR<00:18:04.799> Fortune<00:18:05.400> teror<00:18:06.400> uh<00:18:07.240> Divine<00:18:08.280> B<00:18:09.320> and 00:18:10.310 --> 00:18:10.320 align:start position:0% action AR Fortune teror uh Divine B and 00:18:10.320 --> 00:18:12.630 align:start position:0% action AR Fortune teror uh Divine B and B<00:18:10.640> attacked<00:18:11.080> to 00:18:12.630 --> 00:18:12.640 align:start position:0% B attacked to 00:18:12.640 --> 00:18:15.430 align:start position:0% B attacked to char<00:18:13.640> and<00:18:13.799> the<00:18:14.000> discussion<00:18:14.480> phase<00:18:14.840> and<00:18:15.039> boting 00:18:15.430 --> 00:18:15.440 align:start position:0% char and the discussion phase and boting 00:18:15.440 --> 00:18:21.110 align:start position:0% char and the discussion phase and boting phase<00:18:15.760> is 00:18:21.110 --> 00:18:21.120 align:start position:0% 00:18:21.120 --> 00:18:26.669 align:start position:0% here<00:18:22.120> ice<00:18:22.640> and<00:18:23.000> Bob<00:18:23.559> and<00:18:23.919> Dave<00:18:24.559> are<00:18:25.159> both 00:18:26.669 --> 00:18:26.679 align:start position:0% here ice and Bob and Dave are both 00:18:26.679 --> 00:18:33.110 align:start position:0% here ice and Bob and Dave are both then<00:18:27.679> again<00:18:28.400> the<00:18:28.799> proof<00:18:29.080> generation<00:18:29.640> is 00:18:33.110 --> 00:18:33.120 align:start position:0% 00:18:33.120 --> 00:18:36.870 align:start position:0% started<00:18:34.120> after<00:18:34.520> the<00:18:35.320> verification<00:18:36.120> of<00:18:36.320> the 00:18:36.870 --> 00:18:36.880 align:start position:0% started after the verification of the 00:18:36.880 --> 00:18:40.549 align:start position:0% started after the verification of the proof<00:18:37.880> uh<00:18:38.880> Dae<00:18:39.559> was 00:18:40.549 --> 00:18:40.559 align:start position:0% proof uh Dae was 00:18:40.559 --> 00:18:42.110 align:start position:0% proof uh Dae was executed 00:18:42.110 --> 00:18:42.120 align:start position:0% executed 00:18:42.120 --> 00:18:46.070 align:start position:0% executed here<00:18:43.120> and<00:18:43.440> finally<00:18:44.440> the<00:18:44.600> vory<00:18:45.240> condition 00:18:46.070 --> 00:18:46.080 align:start position:0% here and finally the vory condition 00:18:46.080 --> 00:18:49.990 align:start position:0% here and finally the vory condition check<00:18:46.760> program<00:18:47.760> uh<00:18:47.880> is<00:18:48.080> running 00:18:49.990 --> 00:18:50.000 align:start position:0% check program uh is running 00:18:50.000 --> 00:18:54.029 align:start position:0% check program uh is running here<00:18:51.000> also<00:18:51.520> generating<00:18:52.520> uh<00:18:53.320> collaborative 00:18:54.029 --> 00:18:54.039 align:start position:0% here also generating uh collaborative 00:18:54.039 --> 00:18:59.149 align:start position:0% here also generating uh collaborative proof 00:18:59.149 --> 00:18:59.159 align:start position:0% 00:18:59.159 --> 00:19:03.070 align:start position:0% after<00:18:59.840> creating<00:19:00.840> and<00:19:01.640> verification<00:19:02.640> game<00:19:02.880> is 00:19:03.070 --> 00:19:03.080 align:start position:0% after creating and verification game is 00:19:03.080 --> 00:19:11.190 align:start position:0% after creating and verification game is over<00:19:03.880> weides<00:19:04.799> win 00:19:11.190 --> 00:19:11.200 align:start position:0% 00:19:11.200 --> 00:19:15.350 align:start position:0% here<00:19:12.200> at<00:19:12.440> trust<00:19:13.280> uh<00:19:13.440> we<00:19:13.720> looking<00:19:14.640> to<00:19:15.039> the 00:19:15.350 --> 00:19:15.360 align:start position:0% here at trust uh we looking to the 00:19:15.360 --> 00:19:18.909 align:start position:0% here at trust uh we looking to the Future<00:19:15.840> Prospect<00:19:16.640> of<00:19:16.840> our<00:19:17.120> zkm 00:19:18.909 --> 00:19:18.919 align:start position:0% Future Prospect of our zkm 00:19:18.919 --> 00:19:23.630 align:start position:0% Future Prospect of our zkm PC<00:19:19.919> if<00:19:20.280> it<00:19:20.520> is<00:19:21.280> it<00:19:21.760> becomes<00:19:22.320> available<00:19:22.840> on 00:19:23.630 --> 00:19:23.640 align:start position:0% PC if it is it becomes available on 00:19:23.640 --> 00:19:25.750 align:start position:0% PC if it is it becomes available on blockchain 00:19:25.750 --> 00:19:25.760 align:start position:0% blockchain 00:19:25.760 --> 00:19:31.830 align:start position:0% blockchain uh<00:19:26.760> it<00:19:27.640> it<00:19:27.799> can<00:19:28.039> be<00:19:28.320> used<00:19:29.080> as<00:19:29.320> a<00:19:30.400> more<00:19:31.400> it<00:19:31.520> can<00:19:31.679> be 00:19:31.830 --> 00:19:31.840 align:start position:0% uh it it can be used as a more it can be 00:19:31.840 --> 00:19:36.110 align:start position:0% uh it it can be used as a more it can be used<00:19:32.320> as<00:19:32.480> a<00:19:33.360> sty<00:19:33.679> NPC<00:19:34.159> module<00:19:34.640> on<00:19:35.120> blockchain 00:19:36.110 --> 00:19:36.120 align:start position:0% used as a sty NPC module on blockchain 00:19:36.120 --> 00:19:37.310 align:start position:0% used as a sty NPC module on blockchain with<00:19:36.320> smart 00:19:37.310 --> 00:19:37.320 align:start position:0% with smart 00:19:37.320 --> 00:19:41.510 align:start position:0% with smart contract<00:19:38.320> and<00:19:38.960> uh<00:19:39.960> it<00:19:40.120> can<00:19:40.320> be<00:19:40.600> also<00:19:41.000> applied 00:19:41.510 --> 00:19:41.520 align:start position:0% contract and uh it can be also applied 00:19:41.520 --> 00:19:44.510 align:start position:0% contract and uh it can be also applied to<00:19:42.000> some<00:19:42.280> regions<00:19:43.159> like<00:19:43.400> machine<00:19:43.760> learnings 00:19:44.510 --> 00:19:44.520 align:start position:0% to some regions like machine learnings 00:19:44.520 --> 00:19:49.549 align:start position:0% to some regions like machine learnings and<00:19:44.840> medical<00:19:45.760> and<00:19:46.039> financial<00:19:46.799> data 00:19:49.549 --> 00:19:49.559 align:start position:0% and medical and financial data 00:19:49.559 --> 00:19:52.789 align:start position:0% and medical and financial data uh<00:19:50.559> such<00:19:50.919> case<00:19:51.520> uh 00:19:52.789 --> 00:19:52.799 align:start position:0% uh such case uh 00:19:52.799 --> 00:19:56.630 align:start position:0% uh such case uh where<00:19:53.799> multiple<00:19:54.360> party<00:19:54.840> needs<00:19:55.159> to<00:19:55.320> share 00:19:56.630 --> 00:19:56.640 align:start position:0% where multiple party needs to share 00:19:56.640 --> 00:20:02.909 align:start position:0% where multiple party needs to share data<00:19:57.640> and<00:19:58.440> that's<00:19:58.720> DK<00:19:59.120> MPC<00:20:00.320> can<00:20:01.640> reduce<00:20:02.640> the 00:20:02.909 --> 00:20:02.919 align:start position:0% data and that's DK MPC can reduce the 00:20:02.919 --> 00:20:06.549 align:start position:0% data and that's DK MPC can reduce the security<00:20:03.559> risks<00:20:04.760> and<00:20:05.760> ensure<00:20:06.200> that<00:20:06.440> the 00:20:06.549 --> 00:20:06.559 align:start position:0% security risks and ensure that the 00:20:06.559 --> 00:20:09.830 align:start position:0% security risks and ensure that the correctness<00:20:07.240> of 00:20:09.830 --> 00:20:09.840 align:start position:0% 00:20:09.840 --> 00:20:16.630 align:start position:0% calculation<00:20:10.840> thank<00:20:11.000> you<00:20:11.120> for 00:20:16.630 --> 00:20:16.640 align:start position:0% 00:20:16.640 --> 00:20:19.470 align:start position:0% listening<00:20:17.640> thank<00:20:17.840> you<00:20:18.240> once<00:20:18.480> again<00:20:19.080> uh<00:20:19.240> very 00:20:19.470 --> 00:20:19.480 align:start position:0% listening thank you once again uh very 00:20:19.480 --> 00:20:21.590 align:start position:0% listening thank you once again uh very nice<00:20:19.720> talk<00:20:19.960> you<00:20:20.159> covered<00:20:20.640> many<00:20:20.919> things<00:20:21.320> uh<00:20:21.440> we 00:20:21.590 --> 00:20:21.600 align:start position:0% nice talk you covered many things uh we 00:20:21.600 --> 00:20:24.789 align:start position:0% nice talk you covered many things uh we got<00:20:21.720> an<00:20:22.000> overview<00:20:22.679> of<00:20:23.120> all<00:20:23.280> of<00:20:23.600> MPC<00:20:24.600> uh 00:20:24.789 --> 00:20:24.799 align:start position:0% got an overview of all of MPC uh 00:20:24.799 --> 00:20:26.909 align:start position:0% got an overview of all of MPC uh background<00:20:25.280> on<00:20:25.520> different<00:20:25.840> protocols<00:20:26.679> all 00:20:26.909 --> 00:20:26.919 align:start position:0% background on different protocols all 00:20:26.919 --> 00:20:28.909 align:start position:0% background on different protocols all that<00:20:27.039> you've<00:20:27.240> implemented<00:20:28.200> U<00:20:28.360> demo 00:20:28.909 --> 00:20:28.919 align:start position:0% that you've implemented U demo 00:20:28.919 --> 00:20:30.390 align:start position:0% that you've implemented U demo everything<00:20:29.360> and<00:20:29.520> future<00:20:30.000> I<00:20:30.080> think<00:20:30.159> it<00:20:30.280> was 00:20:30.390 --> 00:20:30.400 align:start position:0% everything and future I think it was 00:20:30.400 --> 00:20:32.390 align:start position:0% everything and future I think it was really<00:20:30.600> nice<00:20:30.840> talk<00:20:31.080> thank<00:20:31.200> you<00:20:31.360> very<00:20:31.520> much<00:20:32.280> H 00:20:32.390 --> 00:20:32.400 align:start position:0% really nice talk thank you very much H 00:20:32.400 --> 00:20:34.549 align:start position:0% really nice talk thank you very much H we<00:20:32.520> have<00:20:32.640> some<00:20:32.880> questions<00:20:33.760> um<00:20:34.080> maybe<00:20:34.320> I<00:20:34.400> will 00:20:34.549 --> 00:20:34.559 align:start position:0% we have some questions um maybe I will 00:20:34.559 --> 00:20:37.110 align:start position:0% we have some questions um maybe I will start<00:20:34.960> at<00:20:35.159> the<00:20:35.400> bottom<00:20:36.039> so<00:20:36.280> maybe<00:20:36.520> I<00:20:36.679> missed<00:20:36.919> it 00:20:37.110 --> 00:20:37.120 align:start position:0% start at the bottom so maybe I missed it 00:20:37.120 --> 00:20:39.230 align:start position:0% start at the bottom so maybe I missed it but<00:20:37.320> which<00:20:37.640> snark<00:20:38.120> did<00:20:38.280> you<00:20:38.400> implement<00:20:38.880> growth 00:20:39.230 --> 00:20:39.240 align:start position:0% but which snark did you implement growth 00:20:39.240 --> 00:20:45.830 align:start position:0% but which snark did you implement growth 16<00:20:40.080> or<00:20:40.400> something<00:20:40.919> else<00:20:41.919> uh<00:20:42.520> ah<00:20:42.760> sorry<00:20:43.520> uh<00:20:44.720> I<00:20:45.720> I 00:20:45.830 --> 00:20:45.840 align:start position:0% 16 or something else uh ah sorry uh I I 00:20:45.840 --> 00:20:50.149 align:start position:0% 16 or something else uh ah sorry uh I I don't<00:20:46.760> write<00:20:47.240> gross<00:20:47.520> 16<00:20:48.240> however<00:20:48.799> uh<00:20:48.960> gross<00:20:49.280> 16 00:20:50.149 --> 00:20:50.159 align:start position:0% don't write gross 16 however uh gross 16 00:20:50.159 --> 00:20:54.149 align:start position:0% don't write gross 16 however uh gross 16 is<00:20:50.440> also<00:20:50.799> implemented<00:20:51.559> for<00:20:51.799> our<00:20:52.039> zkm<00:20:52.760> PC<00:20:53.760> like 00:20:54.149 --> 00:20:54.159 align:start position:0% is also implemented for our zkm PC like 00:20:54.159 --> 00:20:58.070 align:start position:0% is also implemented for our zkm PC like Marlin<00:20:54.760> and<00:20:55.000> pron<00:20:55.880> yeah<00:20:56.799> so<00:20:57.080> plon<00:20:57.480> Marlin<00:20:57.880> and 00:20:58.070 --> 00:20:58.080 align:start position:0% Marlin and pron yeah so plon Marlin and 00:20:58.080 --> 00:20:59.710 align:start position:0% Marlin and pron yeah so plon Marlin and gr6 00:20:59.710 --> 00:20:59.720 align:start position:0% gr6 00:20:59.720 --> 00:21:02.870 align:start position:0% gr6 yes<00:20:59.919> very<00:21:00.159> nice<00:21:00.760> cool<00:21:01.760> uh<00:21:02.000> did<00:21:02.159> you<00:21:02.400> implement 00:21:02.870 --> 00:21:02.880 align:start position:0% yes very nice cool uh did you implement 00:21:02.880 --> 00:21:04.669 align:start position:0% yes very nice cool uh did you implement everything<00:21:03.240> from<00:21:03.440> scratch<00:21:03.919> or<00:21:04.120> did<00:21:04.280> you<00:21:04.440> use 00:21:04.669 --> 00:21:04.679 align:start position:0% everything from scratch or did you use 00:21:04.679 --> 00:21:09.630 align:start position:0% everything from scratch or did you use some<00:21:05.120> existing<00:21:06.000> libraries<00:21:07.000> uh<00:21:07.559> in<00:21:08.200> the<00:21:09.200> part 00:21:09.630 --> 00:21:09.640 align:start position:0% some existing libraries uh in the part 00:21:09.640 --> 00:21:14.149 align:start position:0% some existing libraries uh in the part of<00:21:10.279> our<00:21:10.600> program<00:21:11.400> is 00:21:14.149 --> 00:21:14.159 align:start position:0% of our program is 00:21:14.159 --> 00:21:19.070 align:start position:0% of our program is uh<00:21:15.159> existing<00:21:15.960> libraries<00:21:16.960> uh<00:21:17.480> for<00:21:17.679> example<00:21:18.480> the 00:21:19.070 --> 00:21:19.080 align:start position:0% uh existing libraries uh for example the 00:21:19.080 --> 00:21:23.750 align:start position:0% uh existing libraries uh for example the crypto<00:21:20.480> cryptographic<00:21:21.480> uh<00:21:22.240> Primitives<00:21:23.240> uh<00:21:23.559> we 00:21:23.750 --> 00:21:23.760 align:start position:0% crypto cryptographic uh Primitives uh we 00:21:23.760 --> 00:21:26.110 align:start position:0% crypto cryptographic uh Primitives uh we use<00:21:24.039> this<00:21:24.760> aqu<00:21:25.159> workx 00:21:26.110 --> 00:21:26.120 align:start position:0% use this aqu workx 00:21:26.120 --> 00:21:29.470 align:start position:0% use this aqu workx library<00:21:27.120> and<00:21:27.640> uh<00:21:28.360> the 00:21:29.470 --> 00:21:29.480 align:start position:0% library and uh the 00:21:29.480 --> 00:21:32.470 align:start position:0% library and uh the collaborate<00:21:30.000> with<00:21:30.400> s<00:21:30.799> part<00:21:31.480> uh<00:21:31.600> we<00:21:31.799> refer<00:21:32.240> to 00:21:32.470 --> 00:21:32.480 align:start position:0% collaborate with s part uh we refer to 00:21:32.480 --> 00:21:35.830 align:start position:0% collaborate with s part uh we refer to the<00:21:32.600> original<00:21:33.360> work<00:21:34.360> however<00:21:35.360> uh<00:21:35.520> in 00:21:35.830 --> 00:21:35.840 align:start position:0% the original work however uh in 00:21:35.840 --> 00:21:39.750 align:start position:0% the original work however uh in pre-processing<00:21:36.679> phase<00:21:37.279> of<00:21:37.720> spe<00:21:38.520> and<00:21:39.480> the 00:21:39.750 --> 00:21:39.760 align:start position:0% pre-processing phase of spe and the 00:21:39.760 --> 00:21:41.190 align:start position:0% pre-processing phase of spe and the bitwise 00:21:41.190 --> 00:21:41.200 align:start position:0% bitwise 00:21:41.200 --> 00:21:44.549 align:start position:0% bitwise operations<00:21:42.200> uh<00:21:42.720> bitwise<00:21:43.240> operation<00:21:43.720> region 00:21:44.549 --> 00:21:44.559 align:start position:0% operations uh bitwise operation region 00:21:44.559 --> 00:21:49.350 align:start position:0% operations uh bitwise operation region we<00:21:45.520> we<00:21:45.799> light<00:21:46.760> uh<00:21:47.320> from<00:21:47.840> scratch<00:21:48.840> nice 00:21:49.350 --> 00:21:49.360 align:start position:0% we we light uh from scratch nice 00:21:49.360 --> 00:21:51.909 align:start position:0% we we light uh from scratch nice impressive<00:21:50.360> cool<00:21:51.200> and<00:21:51.320> maybe<00:21:51.559> one<00:21:51.720> last 00:21:51.909 --> 00:21:51.919 align:start position:0% impressive cool and maybe one last 00:21:51.919 --> 00:21:55.029 align:start position:0% impressive cool and maybe one last question<00:21:52.200> for<00:21:52.360> me<00:21:52.559> is<00:21:53.400> um<00:21:54.000> where<00:21:54.240> would<00:21:54.440> you<00:21:54.679> be 00:21:55.029 --> 00:21:55.039 align:start position:0% question for me is um where would you be 00:21:55.039 --> 00:21:57.230 align:start position:0% question for me is um where would you be most<00:21:55.400> excited<00:21:55.799> to<00:21:55.960> see<00:21:56.200> this<00:21:56.400> used<00:21:56.919> what<00:21:57.039> sort 00:21:57.230 --> 00:21:57.240 align:start position:0% most excited to see this used what sort 00:21:57.240 --> 00:22:00.430 align:start position:0% most excited to see this used what sort of<00:21:58.679> developer<00:21:59.240> or<00:21:59.480> application<00:22:00.080> would<00:22:00.240> you 00:22:00.430 --> 00:22:00.440 align:start position:0% of developer or application would you 00:22:00.440 --> 00:22:02.750 align:start position:0% of developer or application would you really<00:22:01.279> love<00:22:01.559> to<00:22:01.720> see<00:22:02.000> building<00:22:02.360> this<00:22:02.559> I<00:22:02.640> think 00:22:02.750 --> 00:22:02.760 align:start position:0% really love to see building this I think 00:22:02.760 --> 00:22:04.590 align:start position:0% really love to see building this I think your<00:22:03.640> examples<00:22:04.039> that<00:22:04.159> you<00:22:04.240> did<00:22:04.400> with<00:22:04.520> the 00:22:04.590 --> 00:22:04.600 align:start position:0% your examples that you did with the 00:22:04.600 --> 00:22:06.630 align:start position:0% your examples that you did with the games<00:22:04.840> and<00:22:04.919> the<00:22:05.039> demo<00:22:05.279> is<00:22:05.440> super<00:22:05.679> nice<00:22:06.039> but 00:22:06.630 --> 00:22:06.640 align:start position:0% games and the demo is super nice but 00:22:06.640 --> 00:22:08.350 align:start position:0% games and the demo is super nice but outside<00:22:06.960> of<00:22:07.120> your<00:22:07.320> team<00:22:07.880> uh<00:22:08.000> who<00:22:08.120> would<00:22:08.240> you 00:22:08.350 --> 00:22:08.360 align:start position:0% outside of your team uh who would you 00:22:08.360 --> 00:22:10.029 align:start position:0% outside of your team uh who would you love<00:22:08.520> to<00:22:08.640> see<00:22:09.000> using 00:22:10.029 --> 00:22:10.039 align:start position:0% love to see using 00:22:10.039 --> 00:22:13.470 align:start position:0% love to see using it<00:22:11.039> ah<00:22:11.480> okay<00:22:11.919> I'm<00:22:12.240> really<00:22:12.640> interested<00:22:13.159> if<00:22:13.360> this 00:22:13.470 --> 00:22:13.480 align:start position:0% it ah okay I'm really interested if this 00:22:13.480 --> 00:22:17.430 align:start position:0% it ah okay I'm really interested if this is<00:22:13.679> used<00:22:14.080> in<00:22:14.360> kind<00:22:14.679> of<00:22:15.480> uh<00:22:15.799> medical<00:22:16.360> case<00:22:16.679> or<00:22:16.919> to 00:22:17.430 --> 00:22:17.440 align:start position:0% is used in kind of uh medical case or to 00:22:17.440 --> 00:22:19.789 align:start position:0% is used in kind of uh medical case or to make<00:22:17.640> the<00:22:17.799> machine<00:22:18.120> learning<00:22:18.640> model<00:22:19.480> uh 00:22:19.789 --> 00:22:19.799 align:start position:0% make the machine learning model uh 00:22:19.799 --> 00:22:22.070 align:start position:0% make the machine learning model uh together<00:22:20.240> with<00:22:20.600> a<00:22:20.799> different<00:22:21.240> organization 00:22:22.070 --> 00:22:22.080 align:start position:0% together with a different organization 00:22:22.080 --> 00:22:24.750 align:start position:0% together with a different organization so<00:22:22.360> if<00:22:22.799> each<00:22:23.039> organization<00:22:23.720> has<00:22:23.960> a<00:22:24.200> different 00:22:24.750 --> 00:22:24.760 align:start position:0% so if each organization has a different 00:22:24.760 --> 00:22:26.390 align:start position:0% so if each organization has a different secret<00:22:25.320> data<00:22:25.640> and<00:22:25.760> they<00:22:25.880> don't<00:22:26.120> want<00:22:26.240> to 00:22:26.390 --> 00:22:26.400 align:start position:0% secret data and they don't want to 00:22:26.400 --> 00:22:29.029 align:start position:0% secret data and they don't want to reveal<00:22:26.799> the<00:22:27.000> data<00:22:27.240> to<00:22:27.480> each<00:22:27.720> other<00:22:28.559> but<00:22:28.720> still 00:22:29.029 --> 00:22:29.039 align:start position:0% reveal the data to each other but still 00:22:29.039 --> 00:22:32.710 align:start position:0% reveal the data to each other but still they<00:22:29.200> can<00:22:29.960> make<00:22:30.520> learn<00:22:30.799> the<00:22:30.960> model<00:22:31.320> to<00:22:31.720> create 00:22:32.710 --> 00:22:32.720 align:start position:0% they can make learn the model to create 00:22:32.720 --> 00:22:36.029 align:start position:0% they can make learn the model to create uh<00:22:32.960> to<00:22:33.200> create<00:22:33.480> the<00:22:33.679> model<00:22:34.039> or<00:22:34.240> to<00:22:34.840> also<00:22:35.080> do<00:22:35.279> the 00:22:36.029 --> 00:22:36.039 align:start position:0% uh to create the model or to also do the 00:22:36.039 --> 00:22:40.350 align:start position:0% uh to create the model or to also do the yeah<00:22:36.960> um<00:22:37.840> estimation<00:22:38.440> from<00:22:38.640> the<00:22:38.840> model<00:22:39.279> so<00:22:39.760> I'm 00:22:40.350 --> 00:22:40.360 align:start position:0% yeah um estimation from the model so I'm 00:22:40.360 --> 00:22:44.549 align:start position:0% yeah um estimation from the model so I'm really<00:22:40.720> excited<00:22:41.279> to<00:22:42.279> combine<00:22:42.919> this<00:22:43.919> uh 00:22:44.549 --> 00:22:44.559 align:start position:0% really excited to combine this uh 00:22:44.559 --> 00:22:46.430 align:start position:0% really excited to combine this uh technology<00:22:45.080> with<00:22:45.240> machine<00:22:45.520> learning<00:22:46.039> yeah 00:22:46.430 --> 00:22:46.440 align:start position:0% technology with machine learning yeah 00:22:46.440 --> 00:22:47.950 align:start position:0% technology with machine learning yeah and<00:22:46.559> you<00:22:46.679> think<00:22:46.840> it's<00:22:47.039> efficient<00:22:47.480> enough<00:22:47.720> to 00:22:47.950 --> 00:22:47.960 align:start position:0% and you think it's efficient enough to 00:22:47.960 --> 00:22:51.149 align:start position:0% and you think it's efficient enough to do<00:22:48.960> um<00:22:49.159> some<00:22:49.440> machine<00:22:49.720> learning<00:22:50.240> in 00:22:51.149 --> 00:22:51.159 align:start position:0% do um some machine learning in 00:22:51.159 --> 00:22:55.350 align:start position:0% do um some machine learning in MPC<00:22:52.159> yes<00:22:52.520> yes<00:22:53.159> so<00:22:53.679> if<00:22:53.960> if<00:22:54.080> we<00:22:54.240> use<00:22:54.559> MPC<00:22:55.200> in 00:22:55.350 --> 00:22:55.360 align:start position:0% MPC yes yes so if if we use MPC in 00:22:55.360 --> 00:22:57.909 align:start position:0% MPC yes yes so if if we use MPC in machine<00:22:55.640> learning<00:22:56.159> we<00:22:56.559> the<00:22:56.679> model<00:22:57.080> itself<00:22:57.679> can 00:22:57.909 --> 00:22:57.919 align:start position:0% machine learning we the model itself can 00:22:57.919 --> 00:23:00.830 align:start position:0% machine learning we the model itself can be<00:22:58.679> private<00:22:59.159> or<00:22:59.440> don't<00:22:59.720> have<00:22:59.840> to<00:22:59.960> be<00:23:00.360> rebuilded 00:23:00.830 --> 00:23:00.840 align:start position:0% be private or don't have to be rebuilded 00:23:00.840 --> 00:23:03.870 align:start position:0% be private or don't have to be rebuilded to<00:23:01.039> anyone<00:23:01.520> yeah<00:23:02.039> very<00:23:02.279> nice<00:23:02.760> cool<00:23:03.520> well 00:23:03.870 --> 00:23:03.880 align:start position:0% to anyone yeah very nice cool well 00:23:03.880 --> 00:23:06.549 align:start position:0% to anyone yeah very nice cool well that's<00:23:04.120> all<00:23:04.279> the<00:23:04.440> questions<00:23:04.880> we<00:23:05.080> have<00:23:05.799> um<00:23:06.320> we'd 00:23:06.549 --> 00:23:06.559 align:start position:0% that's all the questions we have um we'd 00:23:06.559 --> 00:23:08.390 align:start position:0% that's all the questions we have um we'd like<00:23:06.720> to<00:23:06.919> thank<00:23:07.080> the<00:23:07.200> speakers<00:23:07.679> again<00:23:08.159> for<00:23:08.279> a 00:23:08.390 --> 00:23:08.400 align:start position:0% like to thank the speakers again for a 00:23:08.400 --> 00:23:11.230 align:start position:0% like to thank the speakers again for a very<00:23:08.600> nice<00:23:08.799> talk 00:23:11.230 --> 00:23:11.240 align:start position:0% very nice talk 00:23:11.240 --> 00:23:16.950 align:start position:0% very nice talk um<00:23:12.240> thank<00:23:12.440> you<00:23:13.320> thank<00:23:13.679> you<00:23:15.039> so<00:23:16.039> we<00:23:16.200> have<00:23:16.600> a<00:23:16.760> few 00:23:16.950 --> 00:23:16.960 align:start position:0% um thank you thank you so we have a few 00:23:16.960 --> 00:23:19.230 align:start position:0% um thank you thank you so we have a few minutes<00:23:17.320> six<00:23:17.559> minutes<00:23:17.919> before<00:23:18.159> the<00:23:18.760> LA<00:23:18.960> next 00:23:19.230 --> 00:23:19.240 align:start position:0% minutes six minutes before the LA next 00:23:19.240 --> 00:23:21.919 align:start position:0% minutes six minutes before the LA next and<00:23:19.440> last<00:23:19.679> session