WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:07.590 align:start position:0% [Music] 00:00:07.590 --> 00:00:07.600 align:start position:0% [Music] 00:00:07.600 --> 00:00:31.510 align:start position:0% l 00:00:31.510 --> 00:00:31.520 align:start position:0% 00:00:31.520 --> 00:00:48.070 align:start position:0% [Music] 00:00:48.070 --> 00:00:48.080 align:start position:0% 00:00:48.080 --> 00:01:06.750 align:start position:0% [Music] 00:01:06.750 --> 00:01:06.760 align:start position:0% [Music] 00:01:06.760 --> 00:01:11.109 align:start position:0% [Music] hello<00:01:07.200> hello<00:01:08.200> sorry<00:01:08.520> for<00:01:08.680> the<00:01:09.280> delay<00:01:10.280> uh<00:01:10.960> we 00:01:11.109 --> 00:01:11.119 align:start position:0% hello hello sorry for the delay uh we 00:01:11.119 --> 00:01:13.070 align:start position:0% hello hello sorry for the delay uh we had<00:01:11.240> a<00:01:11.400> different<00:01:11.720> plan<00:01:11.960> to<00:01:12.119> start<00:01:12.520> but<00:01:12.759> we<00:01:12.960> we 00:01:13.070 --> 00:01:13.080 align:start position:0% had a different plan to start but we we 00:01:13.080 --> 00:01:16.230 align:start position:0% had a different plan to start but we we will<00:01:13.240> show<00:01:13.520> a<00:01:13.640> few<00:01:13.880> things<00:01:14.280> which<00:01:14.520> are<00:01:15.520> one<00:01:15.759> is 00:01:16.230 --> 00:01:16.240 align:start position:0% will show a few things which are one is 00:01:16.240 --> 00:01:18.310 align:start position:0% will show a few things which are one is account<00:01:16.600> recovery<00:01:17.520> uh<00:01:17.640> we<00:01:17.759> have<00:01:17.840> a<00:01:17.960> generic 00:01:18.310 --> 00:01:18.320 align:start position:0% account recovery uh we have a generic 00:01:18.320 --> 00:01:20.390 align:start position:0% account recovery uh we have a generic relayer<00:01:18.799> to<00:01:18.920> send<00:01:19.200> transactions<00:01:19.720> on 00:01:20.390 --> 00:01:20.400 align:start position:0% relayer to send transactions on 00:01:20.400 --> 00:01:23.749 align:start position:0% relayer to send transactions on chain<00:01:21.400> and<00:01:21.799> one<00:01:22.000> other<00:01:22.240> thing<00:01:22.520> is<00:01:22.840> we<00:01:23.000> have<00:01:23.159> a 00:01:23.749 --> 00:01:23.759 align:start position:0% chain and one other thing is we have a 00:01:23.759 --> 00:01:26.350 align:start position:0% chain and one other thing is we have a registry<00:01:24.439> which<00:01:24.560> we<00:01:24.680> will<00:01:25.040> start<00:01:25.439> with<00:01:26.119> so<00:01:26.280> I 00:01:26.350 --> 00:01:26.360 align:start position:0% registry which we will start with so I 00:01:26.360 --> 00:01:31.749 align:start position:0% registry which we will start with so I was<00:01:26.520> plan<00:01:26.759> to<00:01:26.880> do<00:01:26.960> it<00:01:27.079> later<00:01:27.439> but<00:01:28.040> yeah 00:01:31.749 --> 00:01:31.759 align:start position:0% 00:01:31.759 --> 00:01:42.510 align:start position:0% um<00:01:32.759> so<00:01:33.119> let<00:01:33.240> me<00:01:33.360> show<00:01:33.600> you<00:01:33.920> wait 00:01:42.510 --> 00:01:42.520 align:start position:0% 00:01:42.520 --> 00:01:47.149 align:start position:0% one<00:01:43.520> okay<00:01:43.640> I'm<00:01:43.799> sorry 00:01:47.149 --> 00:01:47.159 align:start position:0% 00:01:47.159 --> 00:01:50.109 align:start position:0% red<00:01:48.159> so<00:01:48.360> anyway<00:01:48.880> hi<00:01:49.040> I'm<00:01:49.200> Dimitri<00:01:49.640> from<00:01:49.759> ZK 00:01:50.109 --> 00:01:50.119 align:start position:0% red so anyway hi I'm Dimitri from ZK 00:01:50.119 --> 00:01:52.389 align:start position:0% red so anyway hi I'm Dimitri from ZK email<00:01:51.000> and<00:01:51.159> I<00:01:51.240> would<00:01:51.399> want<00:01:51.520> to<00:01:51.640> show<00:01:51.799> you<00:01:52.040> first 00:01:52.389 --> 00:01:52.399 align:start position:0% email and I would want to show you first 00:01:52.399 --> 00:01:54.350 align:start position:0% email and I would want to show you first the<00:01:52.880> registry<00:01:53.360> we 00:01:54.350 --> 00:01:54.360 align:start position:0% the registry we 00:01:54.360 --> 00:01:57.310 align:start position:0% the registry we built<00:01:55.360> uh<00:01:55.759> can<00:01:55.880> you<00:01:56.000> see<00:01:56.320> that<00:01:56.840> I'll<00:01:57.039> make<00:01:57.159> it 00:01:57.310 --> 00:01:57.320 align:start position:0% built uh can you see that I'll make it 00:01:57.320 --> 00:02:08.949 align:start position:0% built uh can you see that I'll make it bigger<00:01:57.719> right 00:02:08.949 --> 00:02:08.959 align:start position:0% 00:02:08.959 --> 00:02:11.229 align:start position:0% sorry<00:02:09.959> so<00:02:10.399> what<00:02:10.520> you<00:02:10.640> can<00:02:10.800> do<00:02:10.920> with<00:02:11.080> this 00:02:11.229 --> 00:02:11.239 align:start position:0% sorry so what you can do with this 00:02:11.239 --> 00:02:14.270 align:start position:0% sorry so what you can do with this registry<00:02:12.000> is<00:02:12.239> basically<00:02:12.840> you<00:02:12.959> can<00:02:13.239> create<00:02:14.120> a 00:02:14.270 --> 00:02:14.280 align:start position:0% registry is basically you can create a 00:02:14.280 --> 00:02:17.790 align:start position:0% registry is basically you can create a blueprint<00:02:15.000> which<00:02:15.160> will<00:02:15.680> be<00:02:16.680> uh<00:02:17.519> like<00:02:17.640> a 00:02:17.790 --> 00:02:17.800 align:start position:0% blueprint which will be uh like a 00:02:17.800 --> 00:02:19.309 align:start position:0% blueprint which will be uh like a blueprint<00:02:18.280> for<00:02:18.480> what<00:02:18.599> you<00:02:18.720> want<00:02:18.879> to<00:02:19.040> prove 00:02:19.309 --> 00:02:19.319 align:start position:0% blueprint for what you want to prove 00:02:19.319 --> 00:02:21.830 align:start position:0% blueprint for what you want to prove about<00:02:19.519> an<00:02:19.680> email<00:02:20.040> what<00:02:20.160> you<00:02:20.280> want<00:02:20.360> to<00:02:20.519> show<00:02:21.519> and 00:02:21.830 --> 00:02:21.840 align:start position:0% about an email what you want to show and 00:02:21.840 --> 00:02:24.589 align:start position:0% about an email what you want to show and we<00:02:21.959> will<00:02:22.120> in<00:02:22.239> the<00:02:22.400> background<00:02:22.879> create<00:02:23.440> a<00:02:24.080> ZK 00:02:24.589 --> 00:02:24.599 align:start position:0% we will in the background create a ZK 00:02:24.599 --> 00:02:27.270 align:start position:0% we will in the background create a ZK circuit<00:02:25.599> and<00:02:25.800> with<00:02:25.959> this<00:02:26.160> you<00:02:26.280> can<00:02:26.560> then 00:02:27.270 --> 00:02:27.280 align:start position:0% circuit and with this you can then 00:02:27.280 --> 00:02:30.790 align:start position:0% circuit and with this you can then create<00:02:28.040> proofs<00:02:28.440> about<00:02:28.680> emails<00:02:29.280> with<00:02:29.440> an 00:02:30.790 --> 00:02:30.800 align:start position:0% create proofs about emails with an 00:02:30.800 --> 00:02:32.630 align:start position:0% create proofs about emails with an ZK 00:02:32.630 --> 00:02:32.640 align:start position:0% ZK 00:02:32.640 --> 00:02:36.949 align:start position:0% ZK so<00:02:33.640> uh<00:02:33.720> if<00:02:33.800> you<00:02:34.000> go<00:02:34.160> to<00:02:34.640> registry.<00:02:35.640> zk.<00:02:36.319> email 00:02:36.949 --> 00:02:36.959 align:start position:0% so uh if you go to registry. zk. email 00:02:36.959 --> 00:02:40.589 align:start position:0% so uh if you go to registry. zk. email you<00:02:37.120> can<00:02:37.920> check<00:02:38.120> out<00:02:38.280> the<00:02:38.840> site<00:02:39.840> um<00:02:40.319> and<00:02:40.440> we 00:02:40.589 --> 00:02:40.599 align:start position:0% you can check out the site um and we 00:02:40.599 --> 00:02:42.750 align:start position:0% you can check out the site um and we show<00:02:40.800> code<00:02:41.000> in<00:02:41.120> a<00:02:41.239> bit<00:02:41.519> but<00:02:41.680> basically<00:02:42.640> what 00:02:42.750 --> 00:02:42.760 align:start position:0% show code in a bit but basically what 00:02:42.760 --> 00:02:44.350 align:start position:0% show code in a bit but basically what you<00:02:42.879> will<00:02:43.040> do<00:02:43.319> here 00:02:44.350 --> 00:02:44.360 align:start position:0% you will do here 00:02:44.360 --> 00:02:47.470 align:start position:0% you will do here is<00:02:45.360> uh<00:02:45.599> yeah<00:02:45.879> log<00:02:46.040> in<00:02:46.280> first<00:02:47.000> if<00:02:47.120> you<00:02:47.200> want<00:02:47.319> to 00:02:47.470 --> 00:02:47.480 align:start position:0% is uh yeah log in first if you want to 00:02:47.480 --> 00:02:48.750 align:start position:0% is uh yeah log in first if you want to create<00:02:47.760> you<00:02:47.879> don't<00:02:48.040> have<00:02:48.120> to<00:02:48.239> log<00:02:48.440> in<00:02:48.560> but<00:02:48.680> if 00:02:48.750 --> 00:02:48.760 align:start position:0% create you don't have to log in but if 00:02:48.760 --> 00:02:49.949 align:start position:0% create you don't have to log in but if you<00:02:48.840> want<00:02:48.920> to<00:02:49.080> create<00:02:49.280> the<00:02:49.400> blueprint<00:02:49.800> you'll 00:02:49.949 --> 00:02:49.959 align:start position:0% you want to create the blueprint you'll 00:02:49.959 --> 00:02:52.589 align:start position:0% you want to create the blueprint you'll have<00:02:50.080> to<00:02:50.200> log<00:02:50.400> in<00:02:50.599> with 00:02:52.589 --> 00:02:52.599 align:start position:0% have to log in with 00:02:52.599 --> 00:02:56.670 align:start position:0% have to log in with GitHub<00:02:53.599> uh<00:02:53.760> let's<00:02:54.239> try<00:02:54.560> this<00:02:55.120> out<00:02:56.120> or<00:02:56.360> actually 00:02:56.670 --> 00:02:56.680 align:start position:0% GitHub uh let's try this out or actually 00:02:56.680 --> 00:02:58.869 align:start position:0% GitHub uh let's try this out or actually I'll<00:02:56.959> show<00:02:57.239> one<00:02:57.519> existing<00:02:57.879> one<00:02:58.080> to<00:02:58.239> make<00:02:58.440> it 00:02:58.869 --> 00:02:58.879 align:start position:0% I'll show one existing one to make it 00:02:58.879 --> 00:03:09.030 align:start position:0% I'll show one existing one to make it this<00:02:59.080> part<00:02:59.319> easier 00:03:09.030 --> 00:03:09.040 align:start position:0% 00:03:09.040 --> 00:03:11.470 align:start position:0% so<00:03:09.239> obviously<00:03:09.560> you<00:03:09.680> can<00:03:09.840> create<00:03:10.680> uh<00:03:10.959> any<00:03:11.200> proof 00:03:11.470 --> 00:03:11.480 align:start position:0% so obviously you can create uh any proof 00:03:11.480 --> 00:03:13.470 align:start position:0% so obviously you can create uh any proof about<00:03:11.680> any<00:03:11.879> email<00:03:12.640> but<00:03:12.760> I<00:03:12.799> will<00:03:12.959> show<00:03:13.120> you<00:03:13.239> a 00:03:13.470 --> 00:03:13.480 align:start position:0% about any email but I will show you a 00:03:13.480 --> 00:03:16.070 align:start position:0% about any email but I will show you a simple<00:03:13.879> example<00:03:14.360> which<00:03:14.480> is<00:03:14.680> just<00:03:15.280> proving 00:03:16.070 --> 00:03:16.080 align:start position:0% simple example which is just proving 00:03:16.080 --> 00:03:17.550 align:start position:0% simple example which is just proving that<00:03:16.239> I'm<00:03:16.440> part<00:03:16.599> of<00:03:16.720> a 00:03:17.550 --> 00:03:17.560 align:start position:0% that I'm part of a 00:03:17.560 --> 00:03:19.509 align:start position:0% that I'm part of a residency<00:03:18.560> so<00:03:18.760> basically<00:03:19.040> you<00:03:19.120> would<00:03:19.280> come 00:03:19.509 --> 00:03:19.519 align:start position:0% residency so basically you would come 00:03:19.519 --> 00:03:21.949 align:start position:0% residency so basically you would come here<00:03:19.920> put<00:03:20.120> some<00:03:20.360> inputs<00:03:21.360> can<00:03:21.519> upload<00:03:21.840> the 00:03:21.949 --> 00:03:21.959 align:start position:0% here put some inputs can upload the 00:03:21.959 --> 00:03:24.190 align:start position:0% here put some inputs can upload the email<00:03:22.200> to<00:03:22.400> test<00:03:22.799> which<00:03:22.920> I<00:03:23.040> will<00:03:23.239> do<00:03:23.959> a 00:03:24.190 --> 00:03:24.200 align:start position:0% email to test which I will do a 00:03:24.200 --> 00:03:26.949 align:start position:0% email to test which I will do a residency<00:03:25.159> email<00:03:26.159> and<00:03:26.360> you<00:03:26.440> will<00:03:26.599> fill<00:03:26.799> in 00:03:26.949 --> 00:03:26.959 align:start position:0% residency email and you will fill in 00:03:26.959 --> 00:03:28.030 align:start position:0% residency email and you will fill in some 00:03:28.030 --> 00:03:28.040 align:start position:0% some 00:03:28.040 --> 00:03:30.589 align:start position:0% some information<00:03:29.040> so 00:03:30.589 --> 00:03:30.599 align:start position:0% information so 00:03:30.599 --> 00:03:33.149 align:start position:0% information so Center<00:03:31.200> domain<00:03:32.200> the<00:03:32.319> thing<00:03:32.480> is<00:03:32.680> we<00:03:32.879> we<00:03:33.000> have 00:03:33.149 --> 00:03:33.159 align:start position:0% Center domain the thing is we we have 00:03:33.159 --> 00:03:34.830 align:start position:0% Center domain the thing is we we have this<00:03:33.319> chatbot<00:03:33.840> so<00:03:34.040> hopefully<00:03:34.360> it<00:03:34.480> works 00:03:34.830 --> 00:03:34.840 align:start position:0% this chatbot so hopefully it works 00:03:34.840 --> 00:03:36.229 align:start position:0% this chatbot so hopefully it works because<00:03:35.120> what<00:03:35.200> you<00:03:35.400> actually<00:03:35.599> have<00:03:35.720> to<00:03:35.840> do<00:03:36.040> is 00:03:36.229 --> 00:03:36.239 align:start position:0% because what you actually have to do is 00:03:36.239 --> 00:03:37.990 align:start position:0% because what you actually have to do is create<00:03:36.599> a 00:03:37.990 --> 00:03:38.000 align:start position:0% create a 00:03:38.000 --> 00:03:41.229 align:start position:0% create a Rex<00:03:39.000> uh<00:03:39.200> which<00:03:39.319> would<00:03:39.519> look<00:03:39.760> like<00:03:39.959> this<00:03:40.959> in<00:03:41.120> the 00:03:41.229 --> 00:03:41.239 align:start position:0% Rex uh which would look like this in the 00:03:41.239 --> 00:03:43.949 align:start position:0% Rex uh which would look like this in the very<00:03:41.439> end<00:03:41.640> you<00:03:41.720> would<00:03:41.959> add<00:03:42.159> some<00:03:42.799> values<00:03:43.799> and 00:03:43.949 --> 00:03:43.959 align:start position:0% very end you would add some values and 00:03:43.959 --> 00:03:45.229 align:start position:0% very end you would add some values and what<00:03:44.080> you<00:03:44.159> can<00:03:44.280> see<00:03:44.480> is<00:03:44.599> now<00:03:44.760> if<00:03:44.879> I<00:03:44.959> want<00:03:45.080> to 00:03:45.229 --> 00:03:45.239 align:start position:0% what you can see is now if I want to 00:03:45.239 --> 00:03:46.789 align:start position:0% what you can see is now if I want to prove<00:03:45.480> something<00:03:45.879> about<00:03:46.080> the<00:03:46.239> header<00:03:46.519> of<00:03:46.640> the 00:03:46.789 --> 00:03:46.799 align:start position:0% prove something about the header of the 00:03:46.799 --> 00:03:49.110 align:start position:0% prove something about the header of the email<00:03:47.680> I<00:03:47.760> would<00:03:47.959> select<00:03:48.280> like<00:03:48.439> the 00:03:49.110 --> 00:03:49.120 align:start position:0% email I would select like the 00:03:49.120 --> 00:03:52.670 align:start position:0% email I would select like the header<00:03:50.120> um<00:03:50.319> to<00:03:50.560> the<00:03:50.680> max<00:03:51.000> length<00:03:51.959> and<00:03:52.360> write 00:03:52.670 --> 00:03:52.680 align:start position:0% header um to the max length and write 00:03:52.680 --> 00:03:57.190 align:start position:0% header um to the max length and write this<00:03:53.280> reic<00:03:54.079> um<00:03:55.079> definition<00:03:56.079> so<00:03:56.760> this<00:03:56.840> is<00:03:57.000> the 00:03:57.190 --> 00:03:57.200 align:start position:0% this reic um definition so this is the 00:03:57.200 --> 00:03:59.069 align:start position:0% this reic um definition so this is the part<00:03:57.480> where<00:03:57.879> our<00:03:58.200> chatboard<00:03:58.640> will<00:03:58.760> hopefully 00:03:59.069 --> 00:03:59.079 align:start position:0% part where our chatboard will hopefully 00:03:59.079 --> 00:04:00.869 align:start position:0% part where our chatboard will hopefully help<00:03:59.360> it's<00:03:59.519> quite<00:03:59.879> new<00:04:00.079> so<00:04:00.280> please<00:04:00.599> give<00:04:00.720> us 00:04:00.869 --> 00:04:00.879 align:start position:0% help it's quite new so please give us 00:04:00.879 --> 00:04:02.670 align:start position:0% help it's quite new so please give us feedback<00:04:01.200> if<00:04:01.319> things<00:04:01.480> are<00:04:01.599> not<00:04:01.760> working<00:04:02.560> but 00:04:02.670 --> 00:04:02.680 align:start position:0% feedback if things are not working but 00:04:02.680 --> 00:04:05.229 align:start position:0% feedback if things are not working but in<00:04:02.840> this<00:04:03.040> case<00:04:03.280> what<00:04:03.360> I<00:04:03.480> want<00:04:03.599> to<00:04:03.799> do<00:04:04.000> is<00:04:04.760> I<00:04:04.840> will 00:04:05.229 --> 00:04:05.239 align:start position:0% in this case what I want to do is I will 00:04:05.239 --> 00:04:08.069 align:start position:0% in this case what I want to do is I will look<00:04:05.480> for<00:04:05.840> a<00:04:06.040> welcome<00:04:06.480> text<00:04:06.720> in<00:04:06.840> the 00:04:08.069 --> 00:04:08.079 align:start position:0% look for a welcome text in the 00:04:08.079 --> 00:04:10.630 align:start position:0% look for a welcome text in the header<00:04:09.079> and<00:04:09.319> say<00:04:09.680> I<00:04:09.760> don't<00:04:09.920> want<00:04:10.040> to<00:04:10.200> reveal 00:04:10.630 --> 00:04:10.640 align:start position:0% header and say I don't want to reveal 00:04:10.640 --> 00:04:13.830 align:start position:0% header and say I don't want to reveal this<00:04:11.319> and<00:04:11.439> the<00:04:11.640> next<00:04:11.920> part<00:04:12.319> is<00:04:12.799> I<00:04:12.879> want<00:04:13.079> to 00:04:13.830 --> 00:04:13.840 align:start position:0% this and the next part is I want to 00:04:13.840 --> 00:04:16.030 align:start position:0% this and the next part is I want to reveal<00:04:14.360> this<00:04:14.680> so<00:04:14.879> I<00:04:14.959> want<00:04:15.079> to<00:04:15.239> reveal<00:04:15.599> I'm<00:04:15.840> part 00:04:16.030 --> 00:04:16.040 align:start position:0% reveal this so I want to reveal I'm part 00:04:16.040 --> 00:04:18.870 align:start position:0% reveal this so I want to reveal I'm part of<00:04:16.239> this<00:04:16.440> residency<00:04:17.280> with<00:04:17.479> this 00:04:18.870 --> 00:04:18.880 align:start position:0% of this residency with this 00:04:18.880 --> 00:04:22.189 align:start position:0% of this residency with this text<00:04:19.880> so<00:04:20.160> you<00:04:20.280> can<00:04:20.440> do<00:04:20.720> all<00:04:21.120> kinds<00:04:21.320> of<00:04:21.519> proofs 00:04:22.189 --> 00:04:22.199 align:start position:0% text so you can do all kinds of proofs 00:04:22.199 --> 00:04:23.950 align:start position:0% text so you can do all kinds of proofs let's<00:04:22.400> imagine<00:04:22.800> like<00:04:22.960> for<00:04:23.120> example<00:04:23.440> you<00:04:23.560> want 00:04:23.950 --> 00:04:23.960 align:start position:0% let's imagine like for example you want 00:04:23.960 --> 00:04:27.310 align:start position:0% let's imagine like for example you want to<00:04:24.960> um<00:04:25.479> create<00:04:25.800> like<00:04:25.919> a<00:04:26.080> reimburse<00:04:26.880> platform 00:04:27.310 --> 00:04:27.320 align:start position:0% to um create like a reimburse platform 00:04:27.320 --> 00:04:28.590 align:start position:0% to um create like a reimburse platform which<00:04:27.479> someone's<00:04:27.840> building<00:04:28.160> and<00:04:28.280> you<00:04:28.360> want<00:04:28.440> to 00:04:28.590 --> 00:04:28.600 align:start position:0% which someone's building and you want to 00:04:28.600 --> 00:04:31.629 align:start position:0% which someone's building and you want to create<00:04:29.280> proofs<00:04:29.800> about<00:04:30.160> uh<00:04:30.600> Uber<00:04:30.919> receipt<00:04:31.440> so 00:04:31.629 --> 00:04:31.639 align:start position:0% create proofs about uh Uber receipt so 00:04:31.639 --> 00:04:34.310 align:start position:0% create proofs about uh Uber receipt so what<00:04:31.720> you<00:04:31.840> would<00:04:32.000> do<00:04:32.160> is<00:04:32.320> you<00:04:32.400> would<00:04:33.000> prove<00:04:34.000> uh 00:04:34.310 --> 00:04:34.320 align:start position:0% what you would do is you would prove uh 00:04:34.320 --> 00:04:36.670 align:start position:0% what you would do is you would prove uh you<00:04:34.440> would<00:04:34.639> prove<00:04:34.880> the<00:04:35.000> sender<00:04:35.400> is<00:04:35.880> Uber<00:04:36.520> and 00:04:36.670 --> 00:04:36.680 align:start position:0% you would prove the sender is Uber and 00:04:36.680 --> 00:04:39.230 align:start position:0% you would prove the sender is Uber and you<00:04:36.759> would<00:04:37.039> find 00:04:39.230 --> 00:04:39.240 align:start position:0% you would find 00:04:39.240 --> 00:04:42.870 align:start position:0% you would find the<00:04:40.240> the<00:04:40.520> like<00:04:40.680> the<00:04:40.880> amount<00:04:41.360> of<00:04:41.600> the<00:04:42.440> receipt 00:04:42.870 --> 00:04:42.880 align:start position:0% the the like the amount of the receipt 00:04:42.880 --> 00:04:44.830 align:start position:0% the the like the amount of the receipt from<00:04:43.080> Uber<00:04:43.880> and<00:04:44.039> then<00:04:44.160> you<00:04:44.240> can<00:04:44.560> prove 00:04:44.830 --> 00:04:44.840 align:start position:0% from Uber and then you can prove 00:04:44.840 --> 00:04:47.150 align:start position:0% from Uber and then you can prove automatically<00:04:45.560> hey<00:04:45.840> this<00:04:45.960> is<00:04:46.160> the<00:04:46.600> amount<00:04:46.960> of 00:04:47.150 --> 00:04:47.160 align:start position:0% automatically hey this is the amount of 00:04:47.160 --> 00:04:50.909 align:start position:0% automatically hey this is the amount of what<00:04:47.840> I<00:04:48.840> uh<00:04:49.280> the<00:04:49.400> receipt<00:04:49.759> I<00:04:49.840> got<00:04:50.080> from<00:04:50.759> from 00:04:50.909 --> 00:04:50.919 align:start position:0% what I uh the receipt I got from from 00:04:50.919 --> 00:04:52.870 align:start position:0% what I uh the receipt I got from from Uber<00:04:51.199> and<00:04:51.320> then<00:04:51.440> you<00:04:51.560> can<00:04:52.039> like<00:04:52.199> do<00:04:52.479> automatic 00:04:52.870 --> 00:04:52.880 align:start position:0% Uber and then you can like do automatic 00:04:52.880 --> 00:04:55.749 align:start position:0% Uber and then you can like do automatic reimbursement<00:04:53.440> from<00:04:53.600> that<00:04:53.800> for<00:04:54.400> example<00:04:55.400> and 00:04:55.749 --> 00:04:55.759 align:start position:0% reimbursement from that for example and 00:04:55.759 --> 00:04:58.670 align:start position:0% reimbursement from that for example and yeah<00:04:56.360> I<00:04:56.440> will<00:04:56.639> skip<00:04:56.960> this<00:04:57.160> cuz<00:04:57.639> right<00:04:57.840> now<00:04:58.160> this 00:04:58.670 --> 00:04:58.680 align:start position:0% yeah I will skip this cuz right now this 00:04:58.680 --> 00:05:00.749 align:start position:0% yeah I will skip this cuz right now this uh<00:04:58.880> like<00:04:59.240> creating<00:04:59.800> this<00:04:59.960> circuit<00:05:00.280> will<00:05:00.520> take 00:05:00.749 --> 00:05:00.759 align:start position:0% uh like creating this circuit will take 00:05:00.759 --> 00:05:03.590 align:start position:0% uh like creating this circuit will take a<00:05:00.880> few<00:05:01.120> hours<00:05:01.800> so<00:05:02.360> if<00:05:02.440> you<00:05:02.520> want<00:05:02.639> to<00:05:02.800> try<00:05:02.960> it<00:05:03.080> out 00:05:03.590 --> 00:05:03.600 align:start position:0% a few hours so if you want to try it out 00:05:03.600 --> 00:05:07.270 align:start position:0% a few hours so if you want to try it out try<00:05:03.880> one<00:05:04.160> existing<00:05:04.520> one<00:05:04.680> for<00:05:05.360> now<00:05:06.360> um<00:05:07.000> yeah 00:05:07.270 --> 00:05:07.280 align:start position:0% try one existing one for now um yeah 00:05:07.280 --> 00:05:10.510 align:start position:0% try one existing one for now um yeah after<00:05:07.479> you<00:05:07.680> create<00:05:08.240> it<00:05:09.240> it<00:05:09.440> will<00:05:10.000> appear<00:05:10.320> in 00:05:10.510 --> 00:05:10.520 align:start position:0% after you create it it will appear in 00:05:10.520 --> 00:05:15.189 align:start position:0% after you create it it will appear in the 00:05:15.189 --> 00:05:15.199 align:start position:0% 00:05:15.199 --> 00:05:17.110 align:start position:0% homepage 00:05:17.110 --> 00:05:17.120 align:start position:0% homepage 00:05:17.120 --> 00:05:19.510 align:start position:0% homepage sync<00:05:18.120> so<00:05:18.319> two<00:05:18.520> things<00:05:18.680> you<00:05:18.800> can<00:05:18.960> do<00:05:19.160> you<00:05:19.280> can 00:05:19.510 --> 00:05:19.520 align:start position:0% sync so two things you can do you can 00:05:19.520 --> 00:05:22.189 align:start position:0% sync so two things you can do you can first<00:05:20.080> of<00:05:20.240> course<00:05:20.560> just<00:05:21.440> create<00:05:21.720> proofs<00:05:22.000> on 00:05:22.189 --> 00:05:22.199 align:start position:0% first of course just create proofs on 00:05:22.199 --> 00:05:25.309 align:start position:0% first of course just create proofs on the<00:05:22.520> website<00:05:22.919> with<00:05:23.120> this<00:05:23.240> so<00:05:23.400> I<00:05:23.479> can<00:05:23.759> upload<00:05:24.120> my 00:05:25.309 --> 00:05:25.319 align:start position:0% the website with this so I can upload my 00:05:25.319 --> 00:05:30.150 align:start position:0% the website with this so I can upload my email<00:05:26.319> or<00:05:26.560> use<00:05:27.160> a<00:05:28.039> directed<00:05:28.479> Gmail<00:05:28.840> to<00:05:28.960> connect 00:05:30.150 --> 00:05:30.160 align:start position:0% email or use a directed Gmail to connect 00:05:30.160 --> 00:05:33.110 align:start position:0% email or use a directed Gmail to connect and<00:05:30.360> create<00:05:30.680> like<00:05:30.800> a<00:05:30.919> proof 00:05:33.110 --> 00:05:33.120 align:start position:0% and create like a proof 00:05:33.120 --> 00:05:36.830 align:start position:0% and create like a proof locally<00:05:34.120> um<00:05:35.039> we'll<00:05:35.240> take<00:05:35.400> a<00:05:35.479> few<00:05:35.720> seconds<00:05:36.680> but 00:05:36.830 --> 00:05:36.840 align:start position:0% locally um we'll take a few seconds but 00:05:36.840 --> 00:05:38.270 align:start position:0% locally um we'll take a few seconds but what's<00:05:37.000> more<00:05:37.199> interesting<00:05:37.560> is<00:05:37.759> you<00:05:37.880> can<00:05:38.039> now 00:05:38.270 --> 00:05:38.280 align:start position:0% what's more interesting is you can now 00:05:38.280 --> 00:05:41.280 align:start position:0% what's more interesting is you can now also<00:05:38.520> use<00:05:38.720> this<00:05:38.880> in<00:05:39.000> a<00:05:39.319> SDK<00:05:40.280> version 00:05:41.280 --> 00:05:41.290 align:start position:0% also use this in a SDK version 00:05:41.290 --> 00:05:43.230 align:start position:0% also use this in a SDK version [Music] 00:05:43.230 --> 00:05:43.240 align:start position:0% [Music] 00:05:43.240 --> 00:05:45.830 align:start position:0% [Music] so<00:05:44.240> uh<00:05:44.440> let<00:05:44.560> me 00:05:45.830 --> 00:05:45.840 align:start position:0% so uh let me 00:05:45.840 --> 00:05:48.830 align:start position:0% so uh let me see<00:05:46.840> yeah<00:05:47.000> so<00:05:47.280> there<00:05:47.440> is 00:05:48.830 --> 00:05:48.840 align:start position:0% see yeah so there is 00:05:48.840 --> 00:05:51.670 align:start position:0% see yeah so there is a<00:05:49.840> sorry<00:05:50.160> can<00:05:50.240> you<00:05:50.400> actually<00:05:51.120> can<00:05:51.240> you<00:05:51.400> see 00:05:51.670 --> 00:05:51.680 align:start position:0% a sorry can you actually can you see 00:05:51.680 --> 00:05:57.309 align:start position:0% a sorry can you actually can you see this<00:05:52.560> so<00:05:52.759> if<00:05:52.840> you<00:05:52.960> go<00:05:53.120> to<00:05:53.960> GitHub<00:05:55.000> SL<00:05:56.000> ZK<00:05:56.400> email/ 00:05:57.309 --> 00:05:57.319 align:start position:0% this so if you go to GitHub SL ZK email/ 00:05:57.319 --> 00:06:00.189 align:start position:0% this so if you go to GitHub SL ZK email/ SDK<00:05:58.240> typescript<00:05:58.759> demo<00:05:59.400> so<00:05:59.639> sorry<00:05:59.840> for<00:05:59.960> the 00:06:00.189 --> 00:06:00.199 align:start position:0% SDK typescript demo so sorry for the 00:06:00.199 --> 00:06:02.070 align:start position:0% SDK typescript demo so sorry for the naming<00:06:01.199> so 00:06:02.070 --> 00:06:02.080 align:start position:0% naming so 00:06:02.080 --> 00:06:05.550 align:start position:0% naming so basically<00:06:03.440> this<00:06:04.440> um<00:06:04.639> I<00:06:04.720> added<00:06:04.960> a<00:06:05.039> demo<00:06:05.319> how<00:06:05.440> you 00:06:05.550 --> 00:06:05.560 align:start position:0% basically this um I added a demo how you 00:06:05.560 --> 00:06:10.029 align:start position:0% basically this um I added a demo how you would<00:06:05.720> use<00:06:05.919> this<00:06:06.039> in<00:06:06.599> typescript 00:06:10.029 --> 00:06:10.039 align:start position:0% 00:06:10.039 --> 00:06:13.070 align:start position:0% so<00:06:11.039> let's<00:06:11.160> see<00:06:11.280> if<00:06:11.360> this<00:06:11.880> finishes<00:06:12.880> I<00:06:12.960> don't 00:06:13.070 --> 00:06:13.080 align:start position:0% so let's see if this finishes I don't 00:06:13.080 --> 00:06:14.309 align:start position:0% so let's see if this finishes I don't know<00:06:13.199> if<00:06:13.280> it's<00:06:13.440> the<00:06:13.560> internet<00:06:14.000> but<00:06:14.160> I<00:06:14.240> don't 00:06:14.309 --> 00:06:14.319 align:start position:0% know if it's the internet but I don't 00:06:14.319 --> 00:06:16.710 align:start position:0% know if it's the internet but I don't know<00:06:14.440> if<00:06:14.520> you<00:06:14.680> experienced<00:06:15.280> the<00:06:16.199> kind<00:06:16.319> of<00:06:16.440> slow 00:06:16.710 --> 00:06:16.720 align:start position:0% know if you experienced the kind of slow 00:06:16.720 --> 00:06:20.150 align:start position:0% know if you experienced the kind of slow internet<00:06:17.199> here<00:06:17.599> as<00:06:17.800> well<00:06:18.080> oh<00:06:18.199> yeah<00:06:18.319> anyway<00:06:19.280> so 00:06:20.150 --> 00:06:20.160 align:start position:0% internet here as well oh yeah anyway so 00:06:20.160 --> 00:06:22.510 align:start position:0% internet here as well oh yeah anyway so now<00:06:20.360> we<00:06:20.520> generated<00:06:20.960> a<00:06:21.120> proof<00:06:22.080> uh<00:06:22.160> you<00:06:22.240> can<00:06:22.400> look 00:06:22.510 --> 00:06:22.520 align:start position:0% now we generated a proof uh you can look 00:06:22.520 --> 00:06:24.629 align:start position:0% now we generated a proof uh you can look at<00:06:22.639> the<00:06:22.800> proof<00:06:23.360> it<00:06:23.479> will<00:06:23.680> show<00:06:23.919> you<00:06:24.240> generate 00:06:24.629 --> 00:06:24.639 align:start position:0% at the proof it will show you generate 00:06:24.639 --> 00:06:25.790 align:start position:0% at the proof it will show you generate some 00:06:25.790 --> 00:06:25.800 align:start position:0% some 00:06:25.800 --> 00:06:29.110 align:start position:0% some output<00:06:26.800> and<00:06:27.680> so<00:06:27.880> the<00:06:28.000> email<00:06:28.319> you<00:06:28.400> can<00:06:28.520> only<00:06:28.720> see 00:06:29.110 --> 00:06:29.120 align:start position:0% output and so the email you can only see 00:06:29.120 --> 00:06:31.110 align:start position:0% output and so the email you can only see in<00:06:29.240> local<00:06:29.800> so<00:06:29.880> we<00:06:30.000> don't<00:06:30.199> save<00:06:30.440> any 00:06:31.110 --> 00:06:31.120 align:start position:0% in local so we don't save any 00:06:31.120 --> 00:06:33.589 align:start position:0% in local so we don't save any emails<00:06:32.120> and<00:06:32.240> if<00:06:32.319> you<00:06:32.440> want<00:06:32.639> you<00:06:32.720> can<00:06:32.960> also<00:06:33.440> we 00:06:33.589 --> 00:06:33.599 align:start position:0% emails and if you want you can also we 00:06:33.599 --> 00:06:36.150 align:start position:0% emails and if you want you can also we always<00:06:34.319> deploy<00:06:34.919> a<00:06:35.080> verifier<00:06:35.639> contract<00:06:36.000> on 00:06:36.150 --> 00:06:36.160 align:start position:0% always deploy a verifier contract on 00:06:36.160 --> 00:06:38.309 align:start position:0% always deploy a verifier contract on chain<00:06:36.440> so<00:06:36.599> you<00:06:36.680> can<00:06:36.880> actually<00:06:37.240> verify<00:06:37.880> this 00:06:38.309 --> 00:06:38.319 align:start position:0% chain so you can actually verify this 00:06:38.319 --> 00:06:41.670 align:start position:0% chain so you can actually verify this proof<00:06:39.319> how<00:06:39.479> would<00:06:39.599> you<00:06:39.759> use<00:06:40.039> this<00:06:40.199> in<00:06:40.520> a 00:06:41.670 --> 00:06:41.680 align:start position:0% proof how would you use this in a 00:06:41.680 --> 00:06:46.110 align:start position:0% proof how would you use this in a SDK<00:06:42.680> I<00:06:42.800> guess<00:06:42.960> I<00:06:43.039> have<00:06:43.160> to<00:06:43.319> make<00:06:43.840> this<00:06:45.120> bigger 00:06:46.110 --> 00:06:46.120 align:start position:0% SDK I guess I have to make this bigger 00:06:46.120 --> 00:06:48.430 align:start position:0% SDK I guess I have to make this bigger so<00:06:46.319> if<00:06:46.479> you<00:06:47.160> if<00:06:47.280> you<00:06:47.400> clone<00:06:47.680> this<00:06:47.840> repo<00:06:48.319> you 00:06:48.430 --> 00:06:48.440 align:start position:0% so if you if you clone this repo you 00:06:48.440 --> 00:06:50.830 align:start position:0% so if you if you clone this repo you will<00:06:48.759> you<00:06:48.840> will<00:06:49.039> get<00:06:49.199> this<00:06:49.400> code<00:06:49.759> so<00:06:50.440> basically 00:06:50.830 --> 00:06:50.840 align:start position:0% will you will get this code so basically 00:06:50.840 --> 00:06:54.350 align:start position:0% will you will get this code so basically I<00:06:50.960> just<00:06:51.160> added<00:06:51.479> a<00:06:51.599> few<00:06:51.840> examples<00:06:52.520> here<00:06:53.520> um<00:06:54.240> like 00:06:54.350 --> 00:06:54.360 align:start position:0% I just added a few examples here um like 00:06:54.360 --> 00:06:56.350 align:start position:0% I just added a few examples here um like for<00:06:54.599> like<00:06:54.720> long<00:06:54.960> running<00:06:55.319> proofs<00:06:55.800> and<00:06:56.039> how<00:06:56.160> to 00:06:56.350 --> 00:06:56.360 align:start position:0% for like long running proofs and how to 00:06:56.360 --> 00:06:58.830 align:start position:0% for like long running proofs and how to validate<00:06:56.759> inputs<00:06:57.199> before<00:06:57.440> you<00:06:57.560> use<00:06:57.840> them<00:06:58.639> but 00:06:58.830 --> 00:06:58.840 align:start position:0% validate inputs before you use them but 00:06:58.840 --> 00:07:00.830 align:start position:0% validate inputs before you use them but in<00:06:59.039> this<00:06:59.599> I'll<00:06:59.759> just<00:06:59.919> give<00:07:00.000> you<00:07:00.120> the<00:07:00.280> short 00:07:00.830 --> 00:07:00.840 align:start position:0% in this I'll just give you the short 00:07:00.840 --> 00:07:03.150 align:start position:0% in this I'll just give you the short example<00:07:01.840> so<00:07:02.039> basically<00:07:02.440> what<00:07:02.560> we<00:07:02.720> have<00:07:02.960> here 00:07:03.150 --> 00:07:03.160 align:start position:0% example so basically what we have here 00:07:03.160 --> 00:07:04.629 align:start position:0% example so basically what we have here first<00:07:03.440> what<00:07:03.560> you<00:07:03.680> need<00:07:03.879> is<00:07:04.160> like<00:07:04.520> the 00:07:04.629 --> 00:07:04.639 align:start position:0% first what you need is like the 00:07:04.639 --> 00:07:07.270 align:start position:0% first what you need is like the blueprint<00:07:05.120> you<00:07:05.240> created<00:07:05.639> the<00:07:05.919> ID<00:07:06.919> for<00:07:07.160> this 00:07:07.270 --> 00:07:07.280 align:start position:0% blueprint you created the ID for this 00:07:07.280 --> 00:07:16.469 align:start position:0% blueprint you created the ID for this you<00:07:07.400> can<00:07:08.400> basically<00:07:09.400> if<00:07:09.479> you<00:07:09.639> go<00:07:09.759> to<00:07:09.879> our 00:07:16.469 --> 00:07:16.479 align:start position:0% 00:07:16.479 --> 00:07:19.230 align:start position:0% website<00:07:17.479> uh<00:07:17.919> like<00:07:18.280> all<00:07:18.440> of<00:07:18.599> these<00:07:18.800> have<00:07:19.000> like 00:07:19.230 --> 00:07:19.240 align:start position:0% website uh like all of these have like 00:07:19.240 --> 00:07:22.990 align:start position:0% website uh like all of these have like this<00:07:19.960> um<00:07:20.960> Slug<00:07:21.440> and<00:07:21.560> you<00:07:21.680> can<00:07:21.879> like<00:07:22.039> just<00:07:22.240> copy 00:07:22.990 --> 00:07:23.000 align:start position:0% this um Slug and you can like just copy 00:07:23.000 --> 00:07:27.990 align:start position:0% this um Slug and you can like just copy it<00:07:24.000> and<00:07:24.639> put<00:07:24.800> it<00:07:25.000> here<00:07:25.160> so<00:07:25.360> that's<00:07:25.520> one<00:07:26.280> already 00:07:27.990 --> 00:07:28.000 align:start position:0% it and put it here so that's one already 00:07:28.000 --> 00:07:30.589 align:start position:0% it and put it here so that's one already added<00:07:29.000> oh<00:07:29.199> sorry<00:07:29.560> for<00:07:29.759> these<00:07:30.000> inlay<00:07:30.360> hands 00:07:30.589 --> 00:07:30.599 align:start position:0% added oh sorry for these inlay hands 00:07:30.599 --> 00:07:31.670 align:start position:0% added oh sorry for these inlay hands that's<00:07:30.759> a 00:07:31.670 --> 00:07:31.680 align:start position:0% that's a 00:07:31.680 --> 00:07:35.629 align:start position:0% that's a bit<00:07:32.680> yeah<00:07:33.120> uh<00:07:33.240> anyway<00:07:33.560> you<00:07:33.680> would<00:07:34.360> you<00:07:34.599> just<00:07:35.080> um 00:07:35.629 --> 00:07:35.639 align:start position:0% bit yeah uh anyway you would you just um 00:07:35.639 --> 00:07:37.749 align:start position:0% bit yeah uh anyway you would you just um first<00:07:35.879> thing<00:07:36.000> you<00:07:36.080> do<00:07:36.280> you<00:07:36.400> import<00:07:36.680> the 00:07:37.749 --> 00:07:37.759 align:start position:0% first thing you do you import the 00:07:37.759 --> 00:07:40.990 align:start position:0% first thing you do you import the SDK<00:07:38.759> you<00:07:38.960> initialize<00:07:39.440> it<00:07:39.639> so<00:07:40.080> sorry<00:07:40.319> for<00:07:40.520> this 00:07:40.990 --> 00:07:41.000 align:start position:0% SDK you initialize it so sorry for this 00:07:41.000 --> 00:07:43.510 align:start position:0% SDK you initialize it so sorry for this but<00:07:42.000> you<00:07:42.120> can<00:07:42.400> you<00:07:42.479> will<00:07:42.639> in<00:07:42.759> future<00:07:43.199> pass 00:07:43.510 --> 00:07:43.520 align:start position:0% but you can you will in future pass 00:07:43.520 --> 00:07:44.629 align:start position:0% but you can you will in future pass other<00:07:43.759> options<00:07:44.080> like<00:07:44.199> if<00:07:44.280> you<00:07:44.360> want<00:07:44.479> to 00:07:44.629 --> 00:07:44.639 align:start position:0% other options like if you want to 00:07:44.639 --> 00:07:46.189 align:start position:0% other options like if you want to actually<00:07:44.840> create<00:07:45.080> blueprints<00:07:45.560> you<00:07:45.639> have<00:07:45.759> to 00:07:46.189 --> 00:07:46.199 align:start position:0% actually create blueprints you have to 00:07:46.199 --> 00:07:47.430 align:start position:0% actually create blueprints you have to pass<00:07:46.400> an 00:07:47.430 --> 00:07:47.440 align:start position:0% pass an 00:07:47.440 --> 00:07:49.149 align:start position:0% pass an authentication<00:07:48.440> this<00:07:48.560> is<00:07:48.720> where<00:07:48.879> you 00:07:49.149 --> 00:07:49.159 align:start position:0% authentication this is where you 00:07:49.159 --> 00:07:50.909 align:start position:0% authentication this is where you actually<00:07:49.400> get<00:07:49.560> the<00:07:49.680> blueprint<00:07:50.120> you<00:07:50.240> created 00:07:50.909 --> 00:07:50.919 align:start position:0% actually get the blueprint you created 00:07:50.919 --> 00:07:52.790 align:start position:0% actually get the blueprint you created by<00:07:51.080> the<00:07:51.199> ID<00:07:51.560> so<00:07:51.759> the<00:07:51.879> one<00:07:52.039> we<00:07:52.199> have<00:07:52.319> in<00:07:52.479> the 00:07:52.790 --> 00:07:52.800 align:start position:0% by the ID so the one we have in the 00:07:52.800 --> 00:07:54.270 align:start position:0% by the ID so the one we have in the front 00:07:54.270 --> 00:07:54.280 align:start position:0% front 00:07:54.280 --> 00:07:58.430 align:start position:0% front end<00:07:55.720> uh<00:07:56.720> and<00:07:57.440> from<00:07:57.680> this<00:07:57.800> you<00:07:57.919> can<00:07:58.039> create 00:07:58.430 --> 00:07:58.440 align:start position:0% end uh and from this you can create 00:07:58.440 --> 00:08:01.149 align:start position:0% end uh and from this you can create aover<00:07:59.520> so<00:07:59.599> we<00:07:59.720> did<00:07:59.919> this<00:08:00.440> uh<00:08:00.599> separately 00:08:01.149 --> 00:08:01.159 align:start position:0% aover so we did this uh separately 00:08:01.159 --> 00:08:02.909 align:start position:0% aover so we did this uh separately because<00:08:01.360> in<00:08:01.560> future<00:08:01.879> we<00:08:01.960> want<00:08:02.120> to<00:08:02.280> add<00:08:02.520> client 00:08:02.909 --> 00:08:02.919 align:start position:0% because in future we want to add client 00:08:02.919 --> 00:08:04.950 align:start position:0% because in future we want to add client side<00:08:03.080> proving<00:08:03.599> so<00:08:04.199> let's<00:08:04.400> say<00:08:04.520> if<00:08:04.599> you<00:08:04.680> build 00:08:04.950 --> 00:08:04.960 align:start position:0% side proving so let's say if you build 00:08:04.960 --> 00:08:07.230 align:start position:0% side proving so let's say if you build something<00:08:05.240> like<00:08:05.440> a<00:08:06.159> whistleblowing<00:08:06.840> platform 00:08:07.230 --> 00:08:07.240 align:start position:0% something like a whistleblowing platform 00:08:07.240 --> 00:08:09.510 align:start position:0% something like a whistleblowing platform you<00:08:07.479> would<00:08:08.159> you<00:08:08.319> wouldn't<00:08:08.639> want<00:08:08.840> to<00:08:09.120> do<00:08:09.360> this 00:08:09.510 --> 00:08:09.520 align:start position:0% you would you wouldn't want to do this 00:08:09.520 --> 00:08:11.830 align:start position:0% you would you wouldn't want to do this server<00:08:09.879> side<00:08:10.599> so<00:08:10.759> we're<00:08:10.960> working<00:08:11.199> on<00:08:11.360> a<00:08:11.479> Noir 00:08:11.830 --> 00:08:11.840 align:start position:0% server side so we're working on a Noir 00:08:11.840 --> 00:08:14.629 align:start position:0% server side so we're working on a Noir implementation<00:08:12.440> so<00:08:12.639> it<00:08:12.720> will<00:08:12.919> work<00:08:13.159> front<00:08:13.639> end 00:08:14.629 --> 00:08:14.639 align:start position:0% implementation so it will work front end 00:08:14.639 --> 00:08:16.029 align:start position:0% implementation so it will work front end anyway<00:08:14.879> and<00:08:15.000> all<00:08:15.120> you<00:08:15.199> have<00:08:15.319> to<00:08:15.479> do<00:08:15.599> is<00:08:15.800> then<00:08:15.919> in 00:08:16.029 --> 00:08:16.039 align:start position:0% anyway and all you have to do is then in 00:08:16.039 --> 00:08:18.110 align:start position:0% anyway and all you have to do is then in the<00:08:16.159> end<00:08:16.680> pass<00:08:16.919> in<00:08:17.120> an<00:08:17.280> email<00:08:17.680> which<00:08:17.800> I<00:08:17.919> read 00:08:18.110 --> 00:08:18.120 align:start position:0% the end pass in an email which I read 00:08:18.120 --> 00:08:20.589 align:start position:0% the end pass in an email which I read here<00:08:18.240> from<00:08:18.360> a<00:08:18.680> file<00:08:19.680> and<00:08:20.039> you<00:08:20.159> will<00:08:20.360> get<00:08:20.479> the 00:08:20.589 --> 00:08:20.599 align:start position:0% here from a file and you will get the 00:08:20.599 --> 00:08:23.869 align:start position:0% here from a file and you will get the proof<00:08:20.919> output<00:08:21.479> let's<00:08:21.759> actually<00:08:22.039> see<00:08:22.240> if<00:08:22.440> this 00:08:23.869 --> 00:08:23.879 align:start position:0% proof output let's actually see if this 00:08:23.879 --> 00:08:26.670 align:start position:0% proof output let's actually see if this works<00:08:24.879> uh<00:08:25.039> so<00:08:25.319> you<00:08:25.479> have<00:08:25.599> to<00:08:26.039> I<00:08:26.159> think<00:08:26.319> I<00:08:26.440> added 00:08:26.670 --> 00:08:26.680 align:start position:0% works uh so you have to I think I added 00:08:26.680 --> 00:08:30.589 align:start position:0% works uh so you have to I think I added the<00:08:26.800> commands<00:08:27.120> in<00:08:27.280> the<00:08:27.400> read<00:08:27.639> me<00:08:27.919> so<00:08:28.080> I<00:08:28.240> can 00:08:30.589 --> 00:08:30.599 align:start position:0% the commands in the read me so I can 00:08:30.599 --> 00:08:34.350 align:start position:0% the commands in the read me so I can uh<00:08:31.599> short 00:08:34.350 --> 00:08:34.360 align:start position:0% 00:08:34.360 --> 00:08:38.029 align:start position:0% example<00:08:35.360> so<00:08:36.000> yeah<00:08:37.000> it<00:08:37.159> will<00:08:37.479> proof<00:08:37.760> it<00:08:37.839> will 00:08:38.029 --> 00:08:38.039 align:start position:0% example so yeah it will proof it will 00:08:38.039 --> 00:08:39.310 align:start position:0% example so yeah it will proof it will wait<00:08:38.200> for<00:08:38.360> the 00:08:39.310 --> 00:08:39.320 align:start position:0% wait for the 00:08:39.320 --> 00:08:41.469 align:start position:0% wait for the proof<00:08:40.320> and<00:08:40.479> then<00:08:40.680> it<00:08:40.760> will<00:08:40.959> give<00:08:41.120> you<00:08:41.360> the 00:08:41.469 --> 00:08:41.479 align:start position:0% proof and then it will give you the 00:08:41.479 --> 00:08:45.870 align:start position:0% proof and then it will give you the proof<00:08:41.800> output<00:08:42.279> the<00:08:42.360> proof<00:08:43.000> data<00:08:44.160> so<00:08:45.160> yeah 00:08:45.870 --> 00:08:45.880 align:start position:0% proof output the proof data so yeah 00:08:45.880 --> 00:08:48.470 align:start position:0% proof output the proof data so yeah that's<00:08:46.120> basically<00:08:46.560> it<00:08:46.839> what<00:08:46.959> you<00:08:47.080> need<00:08:47.399> to<00:08:48.120> use 00:08:48.470 --> 00:08:48.480 align:start position:0% that's basically it what you need to use 00:08:48.480 --> 00:08:51.910 align:start position:0% that's basically it what you need to use a<00:08:48.839> proving<00:08:49.240> system<00:08:49.560> of<00:08:49.720> emails<00:08:50.160> in<00:08:50.640> your<00:08:51.640> front 00:08:51.910 --> 00:08:51.920 align:start position:0% a proving system of emails in your front 00:08:51.920 --> 00:08:54.750 align:start position:0% a proving system of emails in your front end<00:08:52.680> this<00:08:52.959> currently<00:08:53.360> only<00:08:53.720> works<00:08:54.480> in<00:08:54.600> the 00:08:54.750 --> 00:08:54.760 align:start position:0% end this currently only works in the 00:08:54.760 --> 00:08:58.350 align:start position:0% end this currently only works in the browser<00:08:55.360> no<00:08:55.680> JS<00:08:56.240> but<00:08:56.640> still<00:08:56.880> not<00:08:57.080> for<00:08:57.519> nextjs 00:08:58.350 --> 00:08:58.360 align:start position:0% browser no JS but still not for nextjs 00:08:58.360 --> 00:08:59.910 align:start position:0% browser no JS but still not for nextjs server<00:08:58.800> side<00:08:59.120> so<00:08:59.240> you<00:08:59.440> you<00:08:59.440> can<00:08:59.560> use<00:08:59.680> it<00:08:59.800> in 00:08:59.910 --> 00:08:59.920 align:start position:0% server side so you you can use it in 00:08:59.920 --> 00:09:02.230 align:start position:0% server side so you you can use it in like<00:09:00.079> next<00:09:00.360> ja<00:09:00.959> front<00:09:01.279> end<00:09:01.640> but<00:09:01.760> not<00:09:01.920> yet<00:09:02.079> in 00:09:02.230 --> 00:09:02.240 align:start position:0% like next ja front end but not yet in 00:09:02.240 --> 00:09:04.350 align:start position:0% like next ja front end but not yet in service<00:09:02.640> side<00:09:02.800> there's<00:09:03.000> some<00:09:03.839> weird<00:09:04.079> issues 00:09:04.350 --> 00:09:04.360 align:start position:0% service side there's some weird issues 00:09:04.360 --> 00:09:07.030 align:start position:0% service side there's some weird issues we're<00:09:04.480> working<00:09:04.720> on<00:09:04.920> with<00:09:05.040> bundlers<00:09:05.680> but<00:09:06.040> yeah 00:09:07.030 --> 00:09:07.040 align:start position:0% we're working on with bundlers but yeah 00:09:07.040 --> 00:09:11.030 align:start position:0% we're working on with bundlers but yeah all<00:09:07.360> right<00:09:08.360> that's<00:09:08.519> for<00:09:08.680> the<00:09:08.839> first<00:09:09.399> demo 00:09:11.030 --> 00:09:11.040 align:start position:0% all right that's for the first demo 00:09:11.040 --> 00:09:14.350 align:start position:0% all right that's for the first demo um<00:09:12.040> a<00:09:12.519> will<00:09:12.760> tell<00:09:12.920> you<00:09:13.040> a<00:09:13.160> bit<00:09:13.320> more<00:09:14.000> General 00:09:14.350 --> 00:09:14.360 align:start position:0% um a will tell you a bit more General 00:09:14.360 --> 00:09:16.150 align:start position:0% um a will tell you a bit more General things<00:09:14.560> about<00:09:14.720> ZK<00:09:15.040> email<00:09:15.399> and<00:09:15.480> then<00:09:15.640> we<00:09:15.720> will 00:09:16.150 --> 00:09:16.160 align:start position:0% things about ZK email and then we will 00:09:16.160 --> 00:09:19.750 align:start position:0% things about ZK email and then we will show<00:09:16.399> you<00:09:16.680> other<00:09:17.000> demos<00:09:17.839> thanks<00:09:18.040> a<00:09:18.200> lot<00:09:19.120> cool 00:09:19.750 --> 00:09:19.760 align:start position:0% show you other demos thanks a lot cool 00:09:19.760 --> 00:09:25.590 align:start position:0% show you other demos thanks a lot cool um 00:09:25.590 --> 00:09:25.600 align:start position:0% 00:09:25.600 --> 00:09:28.630 align:start position:0% okay<00:09:26.600> um<00:09:27.160> okay<00:09:27.360> so<00:09:27.760> I<00:09:27.880> think<00:09:28.160> the<00:09:28.279> way<00:09:28.480> we're 00:09:28.630 --> 00:09:28.640 align:start position:0% okay um okay so I think the way we're 00:09:28.640 --> 00:09:29.509 align:start position:0% okay um okay so I think the way we're probably<00:09:28.839> going<00:09:28.920> to<00:09:29.000> structure<00:09:29.279> this<00:09:29.440> now 00:09:29.509 --> 00:09:29.519 align:start position:0% probably going to structure this now 00:09:29.519 --> 00:09:31.190 align:start position:0% probably going to structure this now that<00:09:29.600> you<00:09:29.680> guys<00:09:29.800> have<00:09:29.920> a<00:09:30.000> sense<00:09:30.240> of<00:09:30.440> like<00:09:30.959> what 00:09:31.190 --> 00:09:31.200 align:start position:0% that you guys have a sense of like what 00:09:31.200 --> 00:09:32.509 align:start position:0% that you guys have a sense of like what is<00:09:31.320> the<00:09:31.440> registry<00:09:31.800> and<00:09:31.920> how<00:09:32.000> does<00:09:32.160> that<00:09:32.279> work 00:09:32.509 --> 00:09:32.519 align:start position:0% is the registry and how does that work 00:09:32.519 --> 00:09:33.949 align:start position:0% is the registry and how does that work is<00:09:32.680> trying<00:09:32.880> to<00:09:33.000> get<00:09:33.200> people<00:09:33.440> to<00:09:33.640> sort<00:09:33.800> of 00:09:33.949 --> 00:09:33.959 align:start position:0% is trying to get people to sort of 00:09:33.959 --> 00:09:37.230 align:start position:0% is trying to get people to sort of generate<00:09:34.560> their<00:09:34.680> own<00:09:34.920> proofs<00:09:35.399> and<00:09:35.519> so<00:09:36.399> um<00:09:36.959> it's 00:09:37.230 --> 00:09:37.240 align:start position:0% generate their own proofs and so um it's 00:09:37.240 --> 00:09:38.829 align:start position:0% generate their own proofs and so um it's pretty<00:09:37.560> big<00:09:37.760> crowd<00:09:38.120> but<00:09:38.240> I<00:09:38.320> think<00:09:38.519> maybe<00:09:38.760> what 00:09:38.829 --> 00:09:38.839 align:start position:0% pretty big crowd but I think maybe what 00:09:38.839 --> 00:09:41.509 align:start position:0% pretty big crowd but I think maybe what we'll<00:09:39.040> do<00:09:39.240> is<00:09:39.519> like<00:09:40.160> kind<00:09:40.320> of 00:09:41.509 --> 00:09:41.519 align:start position:0% we'll do is like kind of 00:09:41.519 --> 00:09:44.069 align:start position:0% we'll do is like kind of um<00:09:42.519> people<00:09:42.760> will<00:09:42.920> try<00:09:43.079> to<00:09:43.279> submit<00:09:43.720> like<00:09:43.839> choose 00:09:44.069 --> 00:09:44.079 align:start position:0% um people will try to submit like choose 00:09:44.079 --> 00:09:45.430 align:start position:0% um people will try to submit like choose an<00:09:44.200> email<00:09:44.440> from<00:09:44.560> their<00:09:44.680> inbox<00:09:45.079> and<00:09:45.160> we'll<00:09:45.279> try 00:09:45.430 --> 00:09:45.440 align:start position:0% an email from their inbox and we'll try 00:09:45.440 --> 00:09:47.030 align:start position:0% an email from their inbox and we'll try to<00:09:45.519> get<00:09:45.600> everybody<00:09:45.959> submit<00:09:46.399> a<00:09:46.519> blueprint<00:09:46.920> to 00:09:47.030 --> 00:09:47.040 align:start position:0% to get everybody submit a blueprint to 00:09:47.040 --> 00:09:48.470 align:start position:0% to get everybody submit a blueprint to that<00:09:47.200> registry<00:09:47.600> so<00:09:47.680> that<00:09:47.800> you<00:09:47.839> can<00:09:47.959> Define<00:09:48.279> new 00:09:48.470 --> 00:09:48.480 align:start position:0% that registry so that you can Define new 00:09:48.480 --> 00:09:50.630 align:start position:0% that registry so that you can Define new kind<00:09:48.600> of<00:09:48.720> approve<00:09:49.480> and<00:09:49.640> then<00:09:49.800> we'll<00:09:50.320> uh<00:09:50.399> send 00:09:50.630 --> 00:09:50.640 align:start position:0% kind of approve and then we'll uh send 00:09:50.640 --> 00:09:52.230 align:start position:0% kind of approve and then we'll uh send you<00:09:50.839> guys<00:09:51.040> so<00:09:51.240> the<00:09:51.399> the<00:09:51.480> repo<00:09:51.800> he<00:09:51.920> just<00:09:52.040> showed 00:09:52.230 --> 00:09:52.240 align:start position:0% you guys so the the repo he just showed 00:09:52.240 --> 00:09:53.590 align:start position:0% you guys so the the repo he just showed of<00:09:52.360> the<00:09:52.480> SDK<00:09:52.839> quick<00:09:53.079> start<00:09:53.200> to<00:09:53.399> actually 00:09:53.590 --> 00:09:53.600 align:start position:0% of the SDK quick start to actually 00:09:53.600 --> 00:09:55.310 align:start position:0% of the SDK quick start to actually putting<00:09:53.839> it<00:09:53.959> into<00:09:54.160> an<00:09:54.360> app<00:09:54.839> then<00:09:54.959> we'll<00:09:55.120> put<00:09:55.240> up 00:09:55.310 --> 00:09:55.320 align:start position:0% putting it into an app then we'll put up 00:09:55.320 --> 00:09:56.670 align:start position:0% putting it into an app then we'll put up a<00:09:55.399> QR<00:09:55.680> code<00:09:55.839> where<00:09:55.959> you<00:09:56.040> can<00:09:56.160> like<00:09:56.240> clone<00:09:56.560> that 00:09:56.670 --> 00:09:56.680 align:start position:0% a QR code where you can like clone that 00:09:56.680 --> 00:09:58.750 align:start position:0% a QR code where you can like clone that repo<00:09:57.200> and<00:09:57.360> then<00:09:57.839> start<00:09:58.120> working<00:09:58.360> on<00:09:58.560> actually 00:09:58.750 --> 00:09:58.760 align:start position:0% repo and then start working on actually 00:09:58.760 --> 00:09:59.910 align:start position:0% repo and then start working on actually getting<00:09:58.959> an<00:09:59.040> appli 00:09:59.910 --> 00:09:59.920 align:start position:0% getting an appli 00:09:59.920 --> 00:10:02.389 align:start position:0% getting an appli around<00:10:00.279> that<00:10:00.720> um<00:10:01.160> maybe<00:10:01.519> just<00:10:01.839> so<00:10:02.079> so<00:10:02.240> I<00:10:02.279> can 00:10:02.389 --> 00:10:02.399 align:start position:0% around that um maybe just so so I can 00:10:02.399 --> 00:10:04.430 align:start position:0% around that um maybe just so so I can get<00:10:02.519> like<00:10:02.640> a<00:10:02.720> sense<00:10:03.000> of<00:10:03.240> like<00:10:03.839> where<00:10:04.120> people 00:10:04.430 --> 00:10:04.440 align:start position:0% get like a sense of like where people 00:10:04.440 --> 00:10:06.310 align:start position:0% get like a sense of like where people are<00:10:04.880> at<00:10:05.040> their<00:10:05.200> level<00:10:05.560> like<00:10:05.680> maybe<00:10:05.959> raise<00:10:06.160> your 00:10:06.310 --> 00:10:06.320 align:start position:0% are at their level like maybe raise your 00:10:06.320 --> 00:10:07.870 align:start position:0% are at their level like maybe raise your hand<00:10:06.480> if<00:10:06.560> you've<00:10:06.760> like<00:10:06.880> heard<00:10:07.000> of<00:10:07.160> zkl<00:10:07.680> or<00:10:07.800> like 00:10:07.870 --> 00:10:07.880 align:start position:0% hand if you've like heard of zkl or like 00:10:07.880 --> 00:10:09.190 align:start position:0% hand if you've like heard of zkl or like are<00:10:07.959> familiar<00:10:08.240> with<00:10:08.320> zkl<00:10:08.720> and<00:10:08.839> like<00:10:08.959> know 00:10:09.190 --> 00:10:09.200 align:start position:0% are familiar with zkl and like know 00:10:09.200 --> 00:10:11.150 align:start position:0% are familiar with zkl and like know roughly<00:10:09.600> what<00:10:10.200> like<00:10:10.399> the<00:10:10.800> the<00:10:10.880> proof<00:10:11.079> that 00:10:11.150 --> 00:10:11.160 align:start position:0% roughly what like the the proof that 00:10:11.160 --> 00:10:13.509 align:start position:0% roughly what like the the proof that we're<00:10:11.279> actually<00:10:11.440> making<00:10:11.800> is<00:10:12.519> okay<00:10:13.120> something 00:10:13.509 --> 00:10:13.519 align:start position:0% we're actually making is okay something 00:10:13.519 --> 00:10:15.710 align:start position:0% we're actually making is okay something like<00:10:13.920> half<00:10:14.240> okay<00:10:14.399> maybe<00:10:14.600> we<00:10:14.720> should<00:10:15.440> also 00:10:15.710 --> 00:10:15.720 align:start position:0% like half okay maybe we should also 00:10:15.720 --> 00:10:18.590 align:start position:0% like half okay maybe we should also briefly<00:10:16.120> reintro<00:10:16.720> that<00:10:17.000> and<00:10:17.160> then<00:10:18.000> um<00:10:18.399> other 00:10:18.590 --> 00:10:18.600 align:start position:0% briefly reintro that and then um other 00:10:18.600 --> 00:10:21.750 align:start position:0% briefly reintro that and then um other thing<00:10:18.800> is<00:10:19.560> maybe<00:10:20.560> uh<00:10:20.720> raise<00:10:20.920> your<00:10:21.160> hand<00:10:21.560> if 00:10:21.750 --> 00:10:21.760 align:start position:0% thing is maybe uh raise your hand if 00:10:21.760 --> 00:10:23.990 align:start position:0% thing is maybe uh raise your hand if after<00:10:22.000> seeing<00:10:22.399> that<00:10:22.560> you<00:10:22.720> feel<00:10:23.680> kind<00:10:23.839> of 00:10:23.990 --> 00:10:24.000 align:start position:0% after seeing that you feel kind of 00:10:24.000 --> 00:10:25.430 align:start position:0% after seeing that you feel kind of confident<00:10:24.440> you<00:10:24.640> go<00:10:24.720> to<00:10:24.839> the<00:10:24.959> registry<00:10:25.360> and 00:10:25.430 --> 00:10:25.440 align:start position:0% confident you go to the registry and 00:10:25.440 --> 00:10:28.269 align:start position:0% confident you go to the registry and make<00:10:25.560> a<00:10:25.720> proof<00:10:25.920> of<00:10:26.079> yourself<00:10:27.079> um<00:10:27.680> and<00:10:27.959> if<00:10:28.120> not 00:10:28.269 --> 00:10:28.279 align:start position:0% make a proof of yourself um and if not 00:10:28.279 --> 00:10:29.829 align:start position:0% make a proof of yourself um and if not we'll<00:10:28.480> kind<00:10:28.560> of<00:10:28.720> come<00:10:28.880> around<00:10:29.000> and<00:10:29.120> help<00:10:29.720> okay 00:10:29.829 --> 00:10:29.839 align:start position:0% we'll kind of come around and help okay 00:10:29.839 --> 00:10:31.350 align:start position:0% we'll kind of come around and help okay so<00:10:29.959> raise<00:10:30.120> your<00:10:30.200> hand<00:10:30.320> if<00:10:30.399> you<00:10:30.519> feel<00:10:30.760> confident 00:10:31.350 --> 00:10:31.360 align:start position:0% so raise your hand if you feel confident 00:10:31.360 --> 00:10:34.230 align:start position:0% so raise your hand if you feel confident with<00:10:31.440> a<00:10:31.560> registry<00:10:32.360> demo<00:10:33.360> um<00:10:33.640> okay<00:10:33.839> a<00:10:33.920> handful 00:10:34.230 --> 00:10:34.240 align:start position:0% with a registry demo um okay a handful 00:10:34.240 --> 00:10:36.069 align:start position:0% with a registry demo um okay a handful of<00:10:34.360> people<00:10:34.720> Okay<00:10:34.880> cool<00:10:35.079> so<00:10:35.279> maybe<00:10:35.839> what<00:10:35.959> I'm 00:10:36.069 --> 00:10:36.079 align:start position:0% of people Okay cool so maybe what I'm 00:10:36.079 --> 00:10:37.509 align:start position:0% of people Okay cool so maybe what I'm going<00:10:36.160> to<00:10:36.279> do<00:10:36.480> then<00:10:36.600> is<00:10:36.760> I'm<00:10:36.839> just<00:10:36.959> going<00:10:37.079> to 00:10:37.509 --> 00:10:37.519 align:start position:0% going to do then is I'm just going to 00:10:37.519 --> 00:10:38.990 align:start position:0% going to do then is I'm just going to briefly<00:10:37.880> go<00:10:38.000> over<00:10:38.240> like<00:10:38.360> what<00:10:38.480> is<00:10:38.800> actually 00:10:38.990 --> 00:10:39.000 align:start position:0% briefly go over like what is actually 00:10:39.000 --> 00:10:40.069 align:start position:0% briefly go over like what is actually the<00:10:39.120> proof<00:10:39.320> that<00:10:39.440> we're<00:10:39.560> making<00:10:39.800> for<00:10:39.959> the 00:10:40.069 --> 00:10:40.079 align:start position:0% the proof that we're making for the 00:10:40.079 --> 00:10:42.269 align:start position:0% the proof that we're making for the people<00:10:40.279> who<00:10:40.519> didn't<00:10:41.519> uh<00:10:41.800> manage<00:10:42.040> to<00:10:42.160> make<00:10:42.240> it 00:10:42.269 --> 00:10:42.279 align:start position:0% people who didn't uh manage to make it 00:10:42.279 --> 00:10:44.949 align:start position:0% people who didn't uh manage to make it to<00:10:42.440> our<00:10:42.560> talk<00:10:42.720> yesterday<00:10:43.200> and<00:10:43.360> then<00:10:43.880> we'll<00:10:44.880> uh 00:10:44.949 --> 00:10:44.959 align:start position:0% to our talk yesterday and then we'll uh 00:10:44.959 --> 00:10:46.190 align:start position:0% to our talk yesterday and then we'll uh we'll<00:10:45.120> put<00:10:45.320> like<00:10:45.399> a<00:10:45.519> guide<00:10:45.680> up<00:10:45.800> for<00:10:45.920> how<00:10:46.000> to<00:10:46.079> use 00:10:46.190 --> 00:10:46.200 align:start position:0% we'll put like a guide up for how to use 00:10:46.200 --> 00:10:47.590 align:start position:0% we'll put like a guide up for how to use a<00:10:46.320> registry<00:10:46.760> and<00:10:46.839> then<00:10:47.000> go<00:10:47.160> around<00:10:47.320> and<00:10:47.440> help 00:10:47.590 --> 00:10:47.600 align:start position:0% a registry and then go around and help 00:10:47.600 --> 00:10:49.350 align:start position:0% a registry and then go around and help people<00:10:47.800> put<00:10:47.920> up<00:10:48.040> the<00:10:48.120> registry<00:10:48.519> proof<00:10:49.079> okay 00:10:49.350 --> 00:10:49.360 align:start position:0% people put up the registry proof okay 00:10:49.360 --> 00:10:52.590 align:start position:0% people put up the registry proof okay does<00:10:49.480> that<00:10:49.600> sound<00:10:49.800> good<00:10:49.920> to<00:10:50.040> folks<00:10:50.519> sweet<00:10:51.600> um 00:10:52.590 --> 00:10:52.600 align:start position:0% does that sound good to folks sweet um 00:10:52.600 --> 00:10:54.910 align:start position:0% does that sound good to folks sweet um okay<00:10:52.720> so<00:10:52.880> maybe<00:10:53.120> just<00:10:53.639> the<00:10:53.839> very<00:10:54.200> basics<00:10:54.680> of 00:10:54.910 --> 00:10:54.920 align:start position:0% okay so maybe just the very basics of 00:10:54.920 --> 00:10:57.829 align:start position:0% okay so maybe just the very basics of like<00:10:55.160> what<00:10:55.480> it<00:10:55.720> what<00:10:55.920> even<00:10:56.360> are<00:10:56.519> we<00:10:56.680> doing<00:10:57.040> here 00:10:57.829 --> 00:10:57.839 align:start position:0% like what it what even are we doing here 00:10:57.839 --> 00:11:00.110 align:start position:0% like what it what even are we doing here um<00:10:58.000> so<00:10:58.160> the<00:10:58.279> point<00:10:58.639> is<00:10:58.920> that<00:10:59.720> all<00:10:59.839> of<00:10:59.959> your 00:11:00.110 --> 00:11:00.120 align:start position:0% um so the point is that all of your 00:11:00.120 --> 00:11:01.910 align:start position:0% um so the point is that all of your emails<00:11:00.680> are<00:11:00.880> signed<00:11:01.279> according<00:11:01.560> to<00:11:01.720> this<00:11:01.839> like 00:11:01.910 --> 00:11:01.920 align:start position:0% emails are signed according to this like 00:11:01.920 --> 00:11:04.069 align:start position:0% emails are signed according to this like Deon<00:11:02.279> protocol<00:11:02.639> so<00:11:02.760> RSA<00:11:03.120> signature<00:11:03.519> of<00:11:03.639> a<00:11:03.800> hash 00:11:04.069 --> 00:11:04.079 align:start position:0% Deon protocol so RSA signature of a hash 00:11:04.079 --> 00:11:06.110 align:start position:0% Deon protocol so RSA signature of a hash of<00:11:04.200> all<00:11:04.320> the<00:11:04.480> data<00:11:04.680> in<00:11:04.800> the<00:11:04.920> email<00:11:05.760> and<00:11:05.880> what<00:11:06.000> we 00:11:06.110 --> 00:11:06.120 align:start position:0% of all the data in the email and what we 00:11:06.120 --> 00:11:08.310 align:start position:0% of all the data in the email and what we want<00:11:06.240> to<00:11:06.399> do<00:11:06.920> is<00:11:07.079> prove<00:11:07.480> some<00:11:07.680> subset<00:11:08.079> of<00:11:08.160> this 00:11:08.310 --> 00:11:08.320 align:start position:0% want to do is prove some subset of this 00:11:08.320 --> 00:11:10.190 align:start position:0% want to do is prove some subset of this data<00:11:08.519> on<00:11:08.680> chain<00:11:09.000> maybe<00:11:09.160> you<00:11:09.240> want<00:11:09.320> to<00:11:09.480> prove<00:11:10.040> oh 00:11:10.190 --> 00:11:10.200 align:start position:0% data on chain maybe you want to prove oh 00:11:10.200 --> 00:11:11.710 align:start position:0% data on chain maybe you want to prove oh the<00:11:10.320> subject<00:11:10.600> of<00:11:10.720> an<00:11:10.839> email<00:11:11.240> or<00:11:11.399> the<00:11:11.480> fact<00:11:11.639> that 00:11:11.710 --> 00:11:11.720 align:start position:0% the subject of an email or the fact that 00:11:11.720 --> 00:11:13.389 align:start position:0% the subject of an email or the fact that you<00:11:11.800> took<00:11:11.959> an<00:11:12.079> Uber<00:11:12.360> ride<00:11:12.560> for<00:11:12.600> $10<00:11:13.160> or<00:11:13.279> the 00:11:13.389 --> 00:11:13.399 align:start position:0% you took an Uber ride for $10 or the 00:11:13.399 --> 00:11:14.910 align:start position:0% you took an Uber ride for $10 or the fact<00:11:13.519> that<00:11:13.600> you<00:11:13.680> got<00:11:13.839> into<00:11:14.000> some<00:11:14.160> residency<00:11:14.639> or 00:11:14.910 --> 00:11:14.920 align:start position:0% fact that you got into some residency or 00:11:14.920 --> 00:11:18.269 align:start position:0% fact that you got into some residency or something<00:11:15.920> um<00:11:16.320> so<00:11:16.480> the<00:11:16.600> point<00:11:16.880> is<00:11:17.519> uh<00:11:17.600> zkl<00:11:18.160> will 00:11:18.269 --> 00:11:18.279 align:start position:0% something um so the point is uh zkl will 00:11:18.279 --> 00:11:19.710 align:start position:0% something um so the point is uh zkl will let<00:11:18.360> you<00:11:18.480> prove<00:11:18.760> this<00:11:18.880> whole<00:11:19.079> signature<00:11:19.600> and 00:11:19.710 --> 00:11:19.720 align:start position:0% let you prove this whole signature and 00:11:19.720 --> 00:11:21.230 align:start position:0% let you prove this whole signature and then<00:11:19.880> extract<00:11:20.240> the<00:11:20.360> information<00:11:20.760> you<00:11:20.880> want<00:11:21.040> to 00:11:21.230 --> 00:11:21.240 align:start position:0% then extract the information you want to 00:11:21.240 --> 00:11:23.030 align:start position:0% then extract the information you want to extract<00:11:21.920> so<00:11:22.079> maybe<00:11:22.279> you<00:11:22.360> can<00:11:22.480> extract<00:11:22.760> just<00:11:22.920> a 00:11:23.030 --> 00:11:23.040 align:start position:0% extract so maybe you can extract just a 00:11:23.040 --> 00:11:25.430 align:start position:0% extract so maybe you can extract just a two<00:11:23.279> field<00:11:23.760> or<00:11:24.480> apply<00:11:24.760> some<00:11:24.880> reject<00:11:25.200> to<00:11:25.320> the 00:11:25.430 --> 00:11:25.440 align:start position:0% two field or apply some reject to the 00:11:25.440 --> 00:11:27.069 align:start position:0% two field or apply some reject to the body<00:11:25.720> and<00:11:25.880> extract<00:11:26.200> some<00:11:26.360> other<00:11:26.600> selectively 00:11:27.069 --> 00:11:27.079 align:start position:0% body and extract some other selectively 00:11:27.079 --> 00:11:29.790 align:start position:0% body and extract some other selectively disclosed<00:11:27.560> thing<00:11:28.360> um<00:11:28.680> and<00:11:28.760> the<00:11:28.880> point<00:11:29.120> is<00:11:29.399> is 00:11:29.790 --> 00:11:29.800 align:start position:0% disclosed thing um and the point is is 00:11:29.800 --> 00:11:30.829 align:start position:0% disclosed thing um and the point is is all<00:11:29.920> these<00:11:30.040> tools<00:11:30.279> we've<00:11:30.399> put<00:11:30.600> together<00:11:30.760> the 00:11:30.829 --> 00:11:30.839 align:start position:0% all these tools we've put together the 00:11:30.839 --> 00:11:32.910 align:start position:0% all these tools we've put together the registry<00:11:31.200> SDK<00:11:31.600> Etc<00:11:32.000> make<00:11:32.120> it<00:11:32.320> very<00:11:32.480> easy<00:11:32.760> for 00:11:32.910 --> 00:11:32.920 align:start position:0% registry SDK Etc make it very easy for 00:11:32.920 --> 00:11:34.509 align:start position:0% registry SDK Etc make it very easy for you<00:11:33.079> so<00:11:33.240> you<00:11:33.360> don't<00:11:33.600> have<00:11:33.720> to<00:11:33.880> think<00:11:34.079> about 00:11:34.509 --> 00:11:34.519 align:start position:0% you so you don't have to think about 00:11:34.519 --> 00:11:36.190 align:start position:0% you so you don't have to think about which<00:11:34.720> ZK<00:11:35.079> proof<00:11:35.320> is<00:11:35.440> happening<00:11:35.720> in<00:11:35.839> the 00:11:36.190 --> 00:11:36.200 align:start position:0% which ZK proof is happening in the 00:11:36.200 --> 00:11:39.430 align:start position:0% which ZK proof is happening in the background<00:11:37.320> um<00:11:38.320> the<00:11:38.399> point<00:11:38.639> is<00:11:38.760> we<00:11:38.839> can<00:11:39.000> keep 00:11:39.430 --> 00:11:39.440 align:start position:0% background um the point is we can keep 00:11:39.440 --> 00:11:40.790 align:start position:0% background um the point is we can keep everything<00:11:39.720> you<00:11:39.880> don't<00:11:40.079> decide<00:11:40.320> to<00:11:40.440> reveal 00:11:40.790 --> 00:11:40.800 align:start position:0% everything you don't decide to reveal 00:11:40.800 --> 00:11:42.829 align:start position:0% everything you don't decide to reveal private<00:11:41.800> uh<00:11:41.920> it's<00:11:42.079> directly<00:11:42.399> verifying<00:11:42.760> the 00:11:42.829 --> 00:11:42.839 align:start position:0% private uh it's directly verifying the 00:11:42.839 --> 00:11:44.269 align:start position:0% private uh it's directly verifying the web<00:11:43.000> to<00:11:43.160> mail<00:11:43.360> service<00:11:43.639> and<00:11:43.760> not<00:11:43.880> some<00:11:44.040> third 00:11:44.269 --> 00:11:44.279 align:start position:0% web to mail service and not some third 00:11:44.279 --> 00:11:46.110 align:start position:0% web to mail service and not some third party<00:11:44.959> and<00:11:45.120> you're<00:11:45.320> verifying<00:11:45.760> these<00:11:45.920> on 00:11:46.110 --> 00:11:46.120 align:start position:0% party and you're verifying these on 00:11:46.120 --> 00:11:47.550 align:start position:0% party and you're verifying these on chain<00:11:46.399> so<00:11:46.519> we'll<00:11:46.680> deploy<00:11:47.040> we'll<00:11:47.200> help<00:11:47.360> you 00:11:47.550 --> 00:11:47.560 align:start position:0% chain so we'll deploy we'll help you 00:11:47.560 --> 00:11:49.350 align:start position:0% chain so we'll deploy we'll help you deploy<00:11:47.920> like<00:11:48.000> solidity<00:11:48.480> contracts<00:11:49.000> as<00:11:49.120> well 00:11:49.350 --> 00:11:49.360 align:start position:0% deploy like solidity contracts as well 00:11:49.360 --> 00:11:52.470 align:start position:0% deploy like solidity contracts as well if<00:11:49.440> you<00:11:49.519> want<00:11:49.639> to<00:11:49.800> do<00:11:50.000> that<00:11:51.000> um<00:11:52.000> for<00:11:52.240> some 00:11:52.470 --> 00:11:52.480 align:start position:0% if you want to do that um for some 00:11:52.480 --> 00:11:53.990 align:start position:0% if you want to do that um for some examples<00:11:52.920> I<00:11:53.000> guess<00:11:53.279> Dimitri<00:11:53.600> already<00:11:53.760> showed 00:11:53.990 --> 00:11:54.000 align:start position:0% examples I guess Dimitri already showed 00:11:54.000 --> 00:11:57.069 align:start position:0% examples I guess Dimitri already showed you<00:11:54.279> the<00:11:55.200> um<00:11:55.720> the<00:11:55.880> proof<00:11:56.040> of<00:11:56.200> residency<00:11:56.680> one 00:11:57.069 --> 00:11:57.079 align:start position:0% you the um the proof of residency one 00:11:57.079 --> 00:11:58.550 align:start position:0% you the um the proof of residency one you<00:11:57.160> can<00:11:57.320> imagine<00:11:57.720> something<00:11:58.160> like<00:11:58.320> you<00:11:58.399> can 00:11:58.550 --> 00:11:58.560 align:start position:0% you can imagine something like you can 00:11:58.560 --> 00:11:59.790 align:start position:0% you can imagine something like you can build<00:11:58.800> like<00:11:58.880> a<00:11:59.000> very<00:11:59.320> Simple<00:11:59.519> app<00:11:59.639> where<00:11:59.720> you 00:11:59.790 --> 00:11:59.800 align:start position:0% build like a very Simple app where you 00:11:59.800 --> 00:12:01.150 align:start position:0% build like a very Simple app where you can<00:11:59.920> redact<00:12:00.279> stuff<00:12:00.440> from<00:12:00.560> email<00:12:00.800> and<00:12:00.880> reveal 00:12:01.150 --> 00:12:01.160 align:start position:0% can redact stuff from email and reveal 00:12:01.160 --> 00:12:03.550 align:start position:0% can redact stuff from email and reveal it<00:12:01.800> um<00:12:01.959> The<00:12:02.120> Hope<00:12:02.399> is<00:12:02.600> that<00:12:03.079> all<00:12:03.200> of<00:12:03.320> you<00:12:03.440> can 00:12:03.550 --> 00:12:03.560 align:start position:0% it um The Hope is that all of you can 00:12:03.560 --> 00:12:05.590 align:start position:0% it um The Hope is that all of you can build<00:12:03.839> something<00:12:04.240> kind<00:12:04.399> of<00:12:04.519> similar<00:12:05.000> to<00:12:05.279> ZK 00:12:05.590 --> 00:12:05.600 align:start position:0% build something kind of similar to ZK 00:12:05.600 --> 00:12:07.829 align:start position:0% build something kind of similar to ZK PTP<00:12:05.959> with<00:12:06.040> the<00:12:06.160> knowledge<00:12:06.399> you<00:12:06.560> get<00:12:06.760> here<00:12:07.519> um 00:12:07.829 --> 00:12:07.839 align:start position:0% PTP with the knowledge you get here um 00:12:07.839 --> 00:12:09.629 align:start position:0% PTP with the knowledge you get here um one<00:12:08.040> example<00:12:08.320> of<00:12:08.399> how<00:12:08.519> zkp<00:12:09.120> works<00:12:09.320> is<00:12:09.440> they 00:12:09.629 --> 00:12:09.639 align:start position:0% one example of how zkp works is they 00:12:09.639 --> 00:12:11.310 align:start position:0% one example of how zkp works is they take<00:12:10.120> exactly<00:12:10.519> this<00:12:10.720> proof<00:12:11.000> that<00:12:11.079> we're<00:12:11.200> going 00:12:11.310 --> 00:12:11.320 align:start position:0% take exactly this proof that we're going 00:12:11.320 --> 00:12:12.870 align:start position:0% take exactly this proof that we're going to<00:12:11.399> help<00:12:11.560> you<00:12:11.680> guys<00:12:11.880> Define<00:12:12.279> of<00:12:12.600> here's<00:12:12.800> an 00:12:12.870 --> 00:12:12.880 align:start position:0% to help you guys Define of here's an 00:12:12.880 --> 00:12:14.670 align:start position:0% to help you guys Define of here's an email<00:12:13.120> from<00:12:13.240> my<00:12:13.360> inbox<00:12:13.720> they<00:12:13.839> do<00:12:14.040> specifically 00:12:14.670 --> 00:12:14.680 align:start position:0% email from my inbox they do specifically 00:12:14.680 --> 00:12:15.990 align:start position:0% email from my inbox they do specifically they<00:12:14.800> do<00:12:14.880> it<00:12:14.959> for<00:12:15.199> name<00:12:15.399> cheep<00:12:15.600> transfer 00:12:15.990 --> 00:12:16.000 align:start position:0% they do it for name cheep transfer 00:12:16.000 --> 00:12:17.790 align:start position:0% they do it for name cheep transfer emails<00:12:16.320> and<00:12:16.440> they<00:12:16.600> extract<00:12:17.160> the<00:12:17.320> domain<00:12:17.639> name 00:12:17.790 --> 00:12:17.800 align:start position:0% emails and they extract the domain name 00:12:17.800 --> 00:12:18.949 align:start position:0% emails and they extract the domain name that<00:12:17.920> was<00:12:18.040> transferred<00:12:18.399> on<00:12:18.480> name<00:12:18.680> cheep<00:12:18.880> and 00:12:18.949 --> 00:12:18.959 align:start position:0% that was transferred on name cheep and 00:12:18.959 --> 00:12:20.470 align:start position:0% that was transferred on name cheep and the<00:12:19.040> fact<00:12:19.199> that<00:12:19.279> it<00:12:19.399> came<00:12:19.560> from<00:12:19.720> name<00:12:19.959> cheep 00:12:20.470 --> 00:12:20.480 align:start position:0% the fact that it came from name cheep 00:12:20.480 --> 00:12:21.870 align:start position:0% the fact that it came from name cheep and<00:12:20.560> then<00:12:20.680> they<00:12:20.760> build<00:12:20.959> a<00:12:21.120> Marketplace<00:12:21.600> on<00:12:21.760> top 00:12:21.870 --> 00:12:21.880 align:start position:0% and then they build a Marketplace on top 00:12:21.880 --> 00:12:23.030 align:start position:0% and then they build a Marketplace on top of<00:12:22.000> that<00:12:22.199> right<00:12:22.279> so<00:12:22.399> now<00:12:22.519> this<00:12:22.639> lets<00:12:22.800> you<00:12:22.880> buy 00:12:23.030 --> 00:12:23.040 align:start position:0% of that right so now this lets you buy 00:12:23.040 --> 00:12:24.550 align:start position:0% of that right so now this lets you buy and<00:12:23.199> sell<00:12:23.399> name<00:12:23.600> CH<00:12:23.800> domains<00:12:24.120> directly<00:12:24.440> on 00:12:24.550 --> 00:12:24.560 align:start position:0% and sell name CH domains directly on 00:12:24.560 --> 00:12:26.470 align:start position:0% and sell name CH domains directly on train<00:12:25.320> and<00:12:25.399> so<00:12:25.519> the<00:12:25.639> hope<00:12:25.839> is<00:12:25.959> that<00:12:26.240> we<00:12:26.320> can 00:12:26.470 --> 00:12:26.480 align:start position:0% train and so the hope is that we can 00:12:26.480 --> 00:12:27.910 align:start position:0% train and so the hope is that we can kind<00:12:26.600> of<00:12:26.720> get<00:12:26.839> you<00:12:27.000> guys<00:12:27.120> to<00:12:27.240> the<00:12:27.399> point<00:12:27.680> where 00:12:27.910 --> 00:12:27.920 align:start position:0% kind of get you guys to the point where 00:12:27.920 --> 00:12:30.750 align:start position:0% kind of get you guys to the point where you've<00:12:28.440> you've<00:12:28.720> defined<00:12:29.320> this<00:12:29.440> kind<00:12:29.560> of<00:12:29.760> proof 00:12:30.750 --> 00:12:30.760 align:start position:0% you've you've defined this kind of proof 00:12:30.760 --> 00:12:32.910 align:start position:0% you've you've defined this kind of proof um<00:12:31.760> and<00:12:31.839> you<00:12:32.000> have<00:12:32.120> a<00:12:32.320> say<00:12:32.440> a<00:12:32.519> solidity 00:12:32.910 --> 00:12:32.920 align:start position:0% um and you have a say a solidity 00:12:32.920 --> 00:12:34.030 align:start position:0% um and you have a say a solidity contract<00:12:33.240> and<00:12:33.320> now<00:12:33.399> you<00:12:33.480> can<00:12:33.600> start<00:12:33.760> building 00:12:34.030 --> 00:12:34.040 align:start position:0% contract and now you can start building 00:12:34.040 --> 00:12:38.590 align:start position:0% contract and now you can start building on<00:12:34.199> top<00:12:34.360> of<00:12:34.600> that<00:12:35.519> okay<00:12:36.079> cool<00:12:37.199> um<00:12:38.199> yeah<00:12:38.399> so 00:12:38.590 --> 00:12:38.600 align:start position:0% on top of that okay cool um yeah so 00:12:38.600 --> 00:12:40.829 align:start position:0% on top of that okay cool um yeah so maybe<00:12:39.040> what<00:12:39.160> I'll<00:12:39.320> do<00:12:39.480> is<00:12:39.639> I'll<00:12:40.160> I'll<00:12:40.440> put<00:12:40.600> up 00:12:40.829 --> 00:12:40.839 align:start position:0% maybe what I'll do is I'll I'll put up 00:12:40.839 --> 00:12:43.949 align:start position:0% maybe what I'll do is I'll I'll put up two<00:12:41.120> QR<00:12:41.440> codes<00:12:42.240> uh<00:12:42.480> for<00:12:43.160> for<00:12:43.360> the<00:12:43.480> registry 00:12:43.949 --> 00:12:43.959 align:start position:0% two QR codes uh for for the registry 00:12:43.959 --> 00:12:46.189 align:start position:0% two QR codes uh for for the registry basically<00:12:44.360> and<00:12:44.480> we<00:12:44.600> can<00:12:44.800> kind<00:12:44.959> of<00:12:45.600> we<00:12:45.720> can<00:12:46.079> we 00:12:46.189 --> 00:12:46.199 align:start position:0% basically and we can kind of we can we 00:12:46.199 --> 00:12:48.230 align:start position:0% basically and we can kind of we can we can<00:12:46.360> get<00:12:46.560> folks<00:12:46.839> going<00:12:47.079> through<00:12:47.320> this<00:12:47.480> whole 00:12:48.230 --> 00:12:48.240 align:start position:0% can get folks going through this whole 00:12:48.240 --> 00:12:50.310 align:start position:0% can get folks going through this whole this<00:12:48.360> whole<00:12:48.560> sequence<00:12:49.320> um<00:12:49.800> and<00:12:49.959> as<00:12:50.120> people 00:12:50.310 --> 00:12:50.320 align:start position:0% this whole sequence um and as people 00:12:50.320 --> 00:12:51.590 align:start position:0% this whole sequence um and as people have<00:12:50.519> questions<00:12:50.880> like<00:12:51.079> our<00:12:51.199> team<00:12:51.360> will<00:12:51.519> kind 00:12:51.590 --> 00:12:51.600 align:start position:0% have questions like our team will kind 00:12:51.600 --> 00:12:52.790 align:start position:0% have questions like our team will kind of<00:12:51.720> come<00:12:51.880> around<00:12:52.120> and<00:12:52.240> also<00:12:52.480> ask<00:12:52.680> the 00:12:52.790 --> 00:12:52.800 align:start position:0% of come around and also ask the 00:12:52.800 --> 00:12:54.590 align:start position:0% of come around and also ask the neighbors<00:12:53.160> next<00:12:53.320> too<00:12:53.680> like<00:12:54.000> how<00:12:54.120> you<00:12:54.240> do<00:12:54.399> this 00:12:54.590 --> 00:12:54.600 align:start position:0% neighbors next too like how you do this 00:12:54.600 --> 00:12:57.150 align:start position:0% neighbors next too like how you do this thing<00:12:55.000> um<00:12:55.199> but<00:12:55.680> I'll<00:12:55.880> put<00:12:56.079> up<00:12:56.760> okay<00:12:56.880> so<00:12:57.000> this<00:12:57.079> is 00:12:57.150 --> 00:12:57.160 align:start position:0% thing um but I'll put up okay so this is 00:12:57.160 --> 00:12:58.590 align:start position:0% thing um but I'll put up okay so this is a<00:12:57.320> specific<00:12:57.600> QR<00:12:57.880> code<00:12:58.040> for<00:12:58.120> the<00:12:58.199> registry<00:12:58.519> that 00:12:58.590 --> 00:12:58.600 align:start position:0% a specific QR code for the registry that 00:12:58.600 --> 00:13:00.110 align:start position:0% a specific QR code for the registry that you<00:12:58.680> should<00:12:58.839> go<00:12:58.959> to 00:13:00.110 --> 00:13:00.120 align:start position:0% you should go to 00:13:00.120 --> 00:13:01.790 align:start position:0% you should go to um<00:13:01.120> if<00:13:01.199> you're<00:13:01.279> going<00:13:01.360> to<00:13:01.440> do<00:13:01.519> this<00:13:01.600> on<00:13:01.680> your 00:13:01.790 --> 00:13:01.800 align:start position:0% um if you're going to do this on your 00:13:01.800 --> 00:13:02.790 align:start position:0% um if you're going to do this on your laptop<00:13:02.079> you<00:13:02.120> should<00:13:02.279> probably<00:13:02.440> just<00:13:02.519> type<00:13:02.680> in 00:13:02.790 --> 00:13:02.800 align:start position:0% laptop you should probably just type in 00:13:02.800 --> 00:13:05.710 align:start position:0% laptop you should probably just type in registry.<00:13:03.720> zk.<00:13:04.720> um<00:13:05.199> and<00:13:05.279> then<00:13:05.399> what<00:13:05.519> I'm<00:13:05.600> going 00:13:05.710 --> 00:13:05.720 align:start position:0% registry. zk. um and then what I'm going 00:13:05.720 --> 00:13:06.870 align:start position:0% registry. zk. um and then what I'm going to<00:13:05.839> do<00:13:05.959> is<00:13:06.079> I'm<00:13:06.240> actually<00:13:06.440> also<00:13:06.600> going<00:13:06.680> to<00:13:06.760> put 00:13:06.870 --> 00:13:06.880 align:start position:0% to do is I'm actually also going to put 00:13:06.880 --> 00:13:09.470 align:start position:0% to do is I'm actually also going to put a<00:13:06.959> QR<00:13:07.279> code<00:13:07.519> to<00:13:07.720> the<00:13:08.600> uh<00:13:08.760> the<00:13:08.920> docs<00:13:09.199> on<00:13:09.320> the 00:13:09.470 --> 00:13:09.480 align:start position:0% a QR code to the uh the docs on the 00:13:09.480 --> 00:13:11.030 align:start position:0% a QR code to the uh the docs on the right<00:13:09.680> side<00:13:09.880> so<00:13:10.040> that<00:13:10.360> if<00:13:10.440> you<00:13:10.560> get<00:13:10.720> lost<00:13:10.959> you 00:13:11.030 --> 00:13:11.040 align:start position:0% right side so that if you get lost you 00:13:11.040 --> 00:13:12.150 align:start position:0% right side so that if you get lost you can<00:13:11.120> just<00:13:11.240> follow<00:13:11.480> the<00:13:11.600> docs<00:13:11.880> and<00:13:11.959> then<00:13:12.079> you 00:13:12.150 --> 00:13:12.160 align:start position:0% can just follow the docs and then you 00:13:12.160 --> 00:13:14.790 align:start position:0% can just follow the docs and then you should<00:13:12.399> be<00:13:12.800> hopefully<00:13:13.240> good<00:13:13.800> um<00:13:14.560> okay<00:13:14.680> I'll 00:13:14.790 --> 00:13:14.800 align:start position:0% should be hopefully good um okay I'll 00:13:14.800 --> 00:13:16.389 align:start position:0% should be hopefully good um okay I'll give<00:13:14.920> people<00:13:15.120> a<00:13:15.279> second<00:13:15.600> to<00:13:15.800> to<00:13:15.959> scan<00:13:16.199> this<00:13:16.279> and 00:13:16.389 --> 00:13:16.399 align:start position:0% give people a second to to scan this and 00:13:16.399 --> 00:13:18.949 align:start position:0% give people a second to to scan this and go<00:13:16.480> to<00:13:16.600> the<00:13:16.800> site<00:13:17.160> and<00:13:17.760> and<00:13:17.880> then<00:13:18.040> we'll<00:13:18.800> we'll 00:13:18.949 --> 00:13:18.959 align:start position:0% go to the site and and then we'll we'll 00:13:18.959 --> 00:13:20.189 align:start position:0% go to the site and and then we'll we'll kind<00:13:19.079> of<00:13:19.160> try<00:13:19.320> to<00:13:19.440> walk<00:13:19.600> people<00:13:19.839> through<00:13:20.120> now 00:13:20.189 --> 00:13:20.199 align:start position:0% kind of try to walk people through now 00:13:20.199 --> 00:13:21.230 align:start position:0% kind of try to walk people through now that<00:13:20.279> you've<00:13:20.440> seen<00:13:20.560> like<00:13:20.639> a<00:13:20.720> demo<00:13:20.920> of<00:13:21.040> what<00:13:21.120> it 00:13:21.230 --> 00:13:21.240 align:start position:0% that you've seen like a demo of what it 00:13:21.240 --> 00:13:22.550 align:start position:0% that you've seen like a demo of what it might<00:13:21.399> look<00:13:21.600> like<00:13:21.760> we'll<00:13:21.920> try<00:13:22.040> to<00:13:22.120> walk<00:13:22.320> people 00:13:22.550 --> 00:13:22.560 align:start position:0% might look like we'll try to walk people 00:13:22.560 --> 00:13:23.910 align:start position:0% might look like we'll try to walk people through<00:13:22.920> so<00:13:23.160> everyone<00:13:23.399> can<00:13:23.480> do<00:13:23.600> their<00:13:23.720> own 00:13:23.910 --> 00:13:23.920 align:start position:0% through so everyone can do their own 00:13:23.920 --> 00:13:26.150 align:start position:0% through so everyone can do their own proof 00:13:26.150 --> 00:13:26.160 align:start position:0% proof 00:13:26.160 --> 00:13:34.790 align:start position:0% proof um<00:13:27.160> okay<00:13:27.560> so<00:13:27.760> let<00:13:27.839> me<00:13:28.079> do 00:13:34.790 --> 00:13:34.800 align:start position:0% 00:13:34.800 --> 00:13:42.470 align:start position:0% uh 00:13:42.470 --> 00:13:42.480 align:start position:0% 00:13:42.480 --> 00:13:46.829 align:start position:0% um 00:13:46.829 --> 00:13:46.839 align:start position:0% 00:13:46.839 --> 00:13:52.030 align:start position:0% see 00:13:52.030 --> 00:13:52.040 align:start position:0% 00:13:52.040 --> 00:13:55.430 align:start position:0% so<00:13:53.040> do<00:13:53.079> you<00:13:53.199> have<00:13:53.399> doc<00:13:53.680> then<00:13:53.839> new<00:13:54.000> registry<00:13:54.880> H 00:13:55.430 --> 00:13:55.440 align:start position:0% so do you have doc then new registry H 00:13:55.440 --> 00:13:57.550 align:start position:0% so do you have doc then new registry H doc<00:13:55.680> then<00:13:55.920> reg<00:13:56.399> no<00:13:56.519> we<00:13:56.600> don't<00:13:56.759> have 00:13:57.550 --> 00:13:57.560 align:start position:0% doc then reg no we don't have 00:13:57.560 --> 00:14:03.389 align:start position:0% doc then reg no we don't have any<00:13:58.560> we<00:13:58.759> to<00:13:59.440> anyway<00:14:00.440> all<00:14:00.600> right<00:14:01.279> the 00:14:03.389 --> 00:14:03.399 align:start position:0% any we to anyway all right the 00:14:03.399 --> 00:14:06.389 align:start position:0% any we to anyway all right the same<00:14:04.399> cool<00:14:04.959> um<00:14:05.240> okay<00:14:05.360> so<00:14:05.639> the<00:14:05.759> first<00:14:06.000> thing<00:14:06.279> we 00:14:06.389 --> 00:14:06.399 align:start position:0% same cool um okay so the first thing we 00:14:06.399 --> 00:14:09.670 align:start position:0% same cool um okay so the first thing we want<00:14:06.800> I'll<00:14:07.000> put<00:14:07.160> this<00:14:07.279> QR<00:14:07.560> code<00:14:07.839> back<00:14:08.079> up 00:14:09.670 --> 00:14:09.680 align:start position:0% want I'll put this QR code back up 00:14:09.680 --> 00:14:12.509 align:start position:0% want I'll put this QR code back up um<00:14:10.680> okay<00:14:11.639> cool<00:14:11.839> yeah<00:14:11.959> this<00:14:12.040> looks<00:14:12.199> pretty<00:14:12.360> good 00:14:12.509 --> 00:14:12.519 align:start position:0% um okay cool yeah this looks pretty good 00:14:12.519 --> 00:14:13.749 align:start position:0% um okay cool yeah this looks pretty good okay<00:14:12.639> so<00:14:12.720> the<00:14:12.839> first<00:14:13.000> thing<00:14:13.120> we<00:14:13.240> want<00:14:13.399> folks<00:14:13.600> to 00:14:13.749 --> 00:14:13.759 align:start position:0% okay so the first thing we want folks to 00:14:13.759 --> 00:14:15.590 align:start position:0% okay so the first thing we want folks to do<00:14:14.000> is<00:14:14.160> find<00:14:14.399> an<00:14:14.560> email<00:14:14.839> from<00:14:15.000> your<00:14:15.160> inbox<00:14:15.480> you 00:14:15.590 --> 00:14:15.600 align:start position:0% do is find an email from your inbox you 00:14:15.600 --> 00:14:17.550 align:start position:0% do is find an email from your inbox you want<00:14:15.680> to<00:14:15.800> make<00:14:15.920> a<00:14:16.079> proof<00:14:16.360> of<00:14:16.880> it<00:14:17.000> can<00:14:17.199> kind<00:14:17.320> of 00:14:17.550 --> 00:14:17.560 align:start position:0% want to make a proof of it can kind of 00:14:17.560 --> 00:14:20.150 align:start position:0% want to make a proof of it can kind of be<00:14:18.560> uh<00:14:18.639> you<00:14:18.759> know<00:14:18.959> any<00:14:19.199> email<00:14:19.639> but<00:14:19.839> it<00:14:19.920> should 00:14:20.150 --> 00:14:20.160 align:start position:0% be uh you know any email but it should 00:14:20.160 --> 00:14:21.509 align:start position:0% be uh you know any email but it should have<00:14:20.320> some<00:14:20.600> data<00:14:20.800> you<00:14:20.880> want<00:14:21.000> to<00:14:21.120> parse<00:14:21.360> out<00:14:21.440> of 00:14:21.509 --> 00:14:21.519 align:start position:0% have some data you want to parse out of 00:14:21.519 --> 00:14:23.230 align:start position:0% have some data you want to parse out of the<00:14:21.639> subject<00:14:21.920> or<00:14:22.079> body<00:14:22.320> so<00:14:22.440> I'll<00:14:22.639> give<00:14:22.800> people 00:14:23.230 --> 00:14:23.240 align:start position:0% the subject or body so I'll give people 00:14:23.240 --> 00:14:25.670 align:start position:0% the subject or body so I'll give people like<00:14:23.720> I<00:14:23.800> don't<00:14:23.920> know<00:14:24.040> a<00:14:24.120> few<00:14:24.320> seconds<00:14:24.759> to<00:14:25.360> to<00:14:25.560> go 00:14:25.670 --> 00:14:25.680 align:start position:0% like I don't know a few seconds to to go 00:14:25.680 --> 00:14:27.829 align:start position:0% like I don't know a few seconds to to go to<00:14:25.839> their<00:14:26.000> inbox<00:14:26.399> and<00:14:26.600> find<00:14:26.959> some<00:14:27.519> some 00:14:27.829 --> 00:14:27.839 align:start position:0% to their inbox and find some some 00:14:27.839 --> 00:14:29.389 align:start position:0% to their inbox and find some some interesting<00:14:28.240> email<00:14:28.720> that<00:14:28.800> you<00:14:29.120> want<00:14:29.199> to<00:14:29.320> make 00:14:29.389 --> 00:14:29.399 align:start position:0% interesting email that you want to make 00:14:29.399 --> 00:14:30.949 align:start position:0% interesting email that you want to make a<00:14:29.519> proof<00:14:29.800> of<00:14:30.320> and<00:14:30.399> then<00:14:30.519> we're<00:14:30.680> kind<00:14:30.759> of<00:14:30.839> going 00:14:30.949 --> 00:14:30.959 align:start position:0% a proof of and then we're kind of going 00:14:30.959 --> 00:14:32.829 align:start position:0% a proof of and then we're kind of going to<00:14:31.120> go<00:14:31.320> through<00:14:31.839> actually<00:14:32.279> like<00:14:32.600> everyone 00:14:32.829 --> 00:14:32.839 align:start position:0% to go through actually like everyone 00:14:32.839 --> 00:14:33.749 align:start position:0% to go through actually like everyone should<00:14:32.959> be<00:14:33.040> following<00:14:33.320> through<00:14:33.440> on<00:14:33.519> their<00:14:33.639> own 00:14:33.749 --> 00:14:33.759 align:start position:0% should be following through on their own 00:14:33.759 --> 00:14:35.269 align:start position:0% should be following through on their own computer<00:14:34.120> like<00:14:34.240> trying<00:14:34.399> to<00:14:34.560> make<00:14:34.720> this<00:14:34.880> proof 00:14:35.269 --> 00:14:35.279 align:start position:0% computer like trying to make this proof 00:14:35.279 --> 00:14:37.990 align:start position:0% computer like trying to make this proof themselves<00:14:36.199> um 00:14:37.990 --> 00:14:38.000 align:start position:0% themselves um 00:14:38.000 --> 00:14:40.910 align:start position:0% themselves um cool<00:14:39.000> maybe<00:14:39.240> in<00:14:39.360> this<00:14:39.519> case<00:14:39.839> I'll<00:14:40.560> I'll<00:14:40.720> try<00:14:40.839> to 00:14:40.910 --> 00:14:40.920 align:start position:0% cool maybe in this case I'll I'll try to 00:14:40.920 --> 00:14:43.310 align:start position:0% cool maybe in this case I'll I'll try to use<00:14:41.079> this<00:14:41.240> email<00:14:41.480> as<00:14:41.600> an<00:14:42.000> example<00:14:43.000> okay<00:14:43.240> and 00:14:43.310 --> 00:14:43.320 align:start position:0% use this email as an example okay and 00:14:43.320 --> 00:14:44.550 align:start position:0% use this email as an example okay and then<00:14:43.440> do<00:14:43.600> folks<00:14:43.839> kind<00:14:43.920> of<00:14:44.040> want<00:14:44.120> to<00:14:44.320> walk 00:14:44.550 --> 00:14:44.560 align:start position:0% then do folks kind of want to walk 00:14:44.560 --> 00:14:46.189 align:start position:0% then do folks kind of want to walk around<00:14:45.160> and<00:14:45.279> then<00:14:45.519> make<00:14:45.639> sure<00:14:45.839> people<00:14:46.000> are 00:14:46.189 --> 00:14:46.199 align:start position:0% around and then make sure people are 00:14:46.199 --> 00:14:49.430 align:start position:0% around and then make sure people are like<00:14:46.320> finding<00:14:46.600> emails<00:14:46.920> from<00:14:47.040> their<00:14:47.199> inbox<00:14:48.360> um 00:14:49.430 --> 00:14:49.440 align:start position:0% like finding emails from their inbox um 00:14:49.440 --> 00:14:51.470 align:start position:0% like finding emails from their inbox um sweet<00:14:50.440> okay<00:14:50.560> I'll<00:14:50.720> give<00:14:50.839> people<00:14:51.079> like<00:14:51.199> 30 00:14:51.470 --> 00:14:51.480 align:start position:0% sweet okay I'll give people like 30 00:14:51.480 --> 00:14:53.350 align:start position:0% sweet okay I'll give people like 30 seconds<00:14:51.759> to<00:14:51.880> search<00:14:52.079> to<00:14:52.160> their<00:14:52.279> inbox<00:14:52.600> finding 00:14:53.350 --> 00:14:53.360 align:start position:0% seconds to search to their inbox finding 00:14:53.360 --> 00:15:17.389 align:start position:0% seconds to search to their inbox finding email<00:14:54.360> um 00:15:17.389 --> 00:15:17.399 align:start position:0% 00:15:17.399 --> 00:15:18.870 align:start position:0% okay<00:15:17.680> maybe<00:15:17.920> raise<00:15:18.079> your<00:15:18.240> hand<00:15:18.440> if<00:15:18.519> you<00:15:18.680> found 00:15:18.870 --> 00:15:18.880 align:start position:0% okay maybe raise your hand if you found 00:15:18.880 --> 00:15:20.150 align:start position:0% okay maybe raise your hand if you found an<00:15:19.000> interesting<00:15:19.320> email<00:15:19.600> you<00:15:19.680> want<00:15:19.839> to<00:15:19.920> make<00:15:20.040> a 00:15:20.150 --> 00:15:20.160 align:start position:0% an interesting email you want to make a 00:15:20.160 --> 00:15:21.829 align:start position:0% an interesting email you want to make a proof 00:15:21.829 --> 00:15:21.839 align:start position:0% proof 00:15:21.839 --> 00:15:24.389 align:start position:0% proof of<00:15:22.839> okay<00:15:23.040> about<00:15:23.320> half<00:15:23.680> maybe<00:15:23.920> raise<00:15:24.079> our<00:15:24.240> hand 00:15:24.389 --> 00:15:24.399 align:start position:0% of okay about half maybe raise our hand 00:15:24.399 --> 00:15:26.069 align:start position:0% of okay about half maybe raise our hand if<00:15:24.480> you<00:15:24.600> want<00:15:24.800> another<00:15:25.160> like 00:15:26.069 --> 00:15:26.079 align:start position:0% if you want another like 00:15:26.079 --> 00:15:28.590 align:start position:0% if you want another like minute<00:15:27.079> okay<00:15:27.639> handful<00:15:27.959> of<00:15:28.079> people<00:15:28.399> okay<00:15:28.480> we'll 00:15:28.590 --> 00:15:28.600 align:start position:0% minute okay handful of people okay we'll 00:15:28.600 --> 00:15:40.829 align:start position:0% minute okay handful of people okay we'll give<00:15:28.720> people<00:15:29.120> like<00:15:29.240> 30<00:15:29.440> seconds<00:15:29.720> or<00:15:29.880> so 00:15:40.829 --> 00:15:40.839 align:start position:0% 00:15:40.839 --> 00:15:45.430 align:start position:0% um<00:15:41.839> I'm 00:15:45.430 --> 00:15:45.440 align:start position:0% 00:15:45.440 --> 00:15:48.189 align:start position:0% exp<00:15:46.440> cool<00:15:46.880> yeah<00:15:47.079> so<00:15:47.360> once<00:15:47.560> you<00:15:47.759> found<00:15:47.959> this 00:15:48.189 --> 00:15:48.199 align:start position:0% exp cool yeah so once you found this 00:15:48.199 --> 00:15:50.629 align:start position:0% exp cool yeah so once you found this email<00:15:49.199> um<00:15:49.519> if<00:15:49.639> you're<00:15:49.800> in<00:15:49.959> Gmail<00:15:50.399> you're<00:15:50.560> going 00:15:50.629 --> 00:15:50.639 align:start position:0% email um if you're in Gmail you're going 00:15:50.639 --> 00:15:52.509 align:start position:0% email um if you're in Gmail you're going to<00:15:50.839> hit<00:15:51.079> these<00:15:51.319> like<00:15:51.480> three<00:15:51.720> dots<00:15:52.319> and<00:15:52.440> then 00:15:52.509 --> 00:15:52.519 align:start position:0% to hit these like three dots and then 00:15:52.519 --> 00:15:54.150 align:start position:0% to hit these like three dots and then you'll<00:15:52.639> see<00:15:52.800> a<00:15:52.959> little<00:15:53.120> thing<00:15:53.319> which<00:15:53.440> is<00:15:53.560> show 00:15:54.150 --> 00:15:54.160 align:start position:0% you'll see a little thing which is show 00:15:54.160 --> 00:15:56.509 align:start position:0% you'll see a little thing which is show original<00:15:55.160> um<00:15:55.440> and<00:15:55.560> you're<00:15:55.639> going<00:15:55.759> to<00:15:55.880> hit<00:15:56.160> that 00:15:56.509 --> 00:15:56.519 align:start position:0% original um and you're going to hit that 00:15:56.519 --> 00:15:57.829 align:start position:0% original um and you're going to hit that and<00:15:56.600> if<00:15:56.680> you're<00:15:56.800> in<00:15:56.959> Outlook<00:15:57.319> you'll<00:15:57.440> see<00:15:57.639> one 00:15:57.829 --> 00:15:57.839 align:start position:0% and if you're in Outlook you'll see one 00:15:57.839 --> 00:15:59.629 align:start position:0% and if you're in Outlook you'll see one which<00:15:57.920> is<00:15:58.040> like<00:15:58.160> download<00:15:58.480> original<00:15:59.040> message 00:15:59.629 --> 00:15:59.639 align:start position:0% which is like download original message 00:15:59.639 --> 00:16:00.990 align:start position:0% which is like download original message uh<00:15:59.800> similar<00:16:00.160> thing<00:16:00.360> you're<00:16:00.480> going<00:16:00.560> to<00:16:00.720> hit 00:16:00.990 --> 00:16:01.000 align:start position:0% uh similar thing you're going to hit 00:16:01.000 --> 00:16:07.309 align:start position:0% uh similar thing you're going to hit that<00:16:02.000> okay<00:16:02.120> so<00:16:02.240> I'm<00:16:02.319> going<00:16:02.399> to<00:16:02.519> hit 00:16:07.309 --> 00:16:07.319 align:start position:0% 00:16:07.319 --> 00:16:10.150 align:start position:0% this<00:16:08.319> okay<00:16:08.519> and<00:16:08.600> now<00:16:08.759> you<00:16:08.839> see<00:16:09.079> this<00:16:09.279> like<00:16:09.839> big 00:16:10.150 --> 00:16:10.160 align:start position:0% this okay and now you see this like big 00:16:10.160 --> 00:16:12.990 align:start position:0% this okay and now you see this like big document<00:16:10.880> uh<00:16:11.000> of<00:16:11.199> all<00:16:11.680> of<00:16:11.800> all<00:16:11.959> the<00:16:12.079> raw<00:16:12.399> data 00:16:12.990 --> 00:16:13.000 align:start position:0% document uh of all of all the raw data 00:16:13.000 --> 00:16:13.990 align:start position:0% document uh of all of all the raw data this<00:16:13.120> is<00:16:13.240> where<00:16:13.360> we're<00:16:13.519> actually<00:16:13.720> going<00:16:13.800> to 00:16:13.990 --> 00:16:14.000 align:start position:0% this is where we're actually going to 00:16:14.000 --> 00:16:20.269 align:start position:0% this is where we're actually going to extract<00:16:14.399> information<00:16:15.199> from 00:16:20.269 --> 00:16:20.279 align:start position:0% 00:16:20.279 --> 00:16:22.389 align:start position:0% um 00:16:22.389 --> 00:16:22.399 align:start position:0% um 00:16:22.399 --> 00:16:44.389 align:start position:0% um okay<00:16:23.399> cool<00:16:24.360> um 00:16:44.389 --> 00:16:44.399 align:start position:0% 00:16:44.399 --> 00:16:46.350 align:start position:0% let<00:16:44.480> me<00:16:44.639> try<00:16:44.880> to<00:16:45.079> format<00:16:45.440> this<00:16:45.600> QR<00:16:45.920> code<00:16:46.120> so<00:16:46.240> it 00:16:46.350 --> 00:16:46.360 align:start position:0% let me try to format this QR code so it 00:16:46.360 --> 00:16:49.189 align:start position:0% let me try to format this QR code so it shows<00:16:46.639> up<00:16:46.759> a<00:16:46.880> little 00:16:49.189 --> 00:16:49.199 align:start position:0% 00:16:49.199 --> 00:17:04.829 align:start position:0% better<00:16:50.199> okay<00:16:50.399> perfect<00:16:51.560> um<00:16:52.560> sweet 00:17:04.829 --> 00:17:04.839 align:start position:0% 00:17:04.839 --> 00:17:05.710 align:start position:0% okay<00:17:05.039> and<00:17:05.120> then<00:17:05.199> what<00:17:05.319> I'm<00:17:05.400> going<00:17:05.480> to<00:17:05.559> do<00:17:05.640> is 00:17:05.710 --> 00:17:05.720 align:start position:0% okay and then what I'm going to do is 00:17:05.720 --> 00:17:07.029 align:start position:0% okay and then what I'm going to do is I'm<00:17:05.799> going<00:17:05.919> to<00:17:06.000> log<00:17:06.199> in<00:17:06.360> into<00:17:06.559> the<00:17:06.640> registry 00:17:07.029 --> 00:17:07.039 align:start position:0% I'm going to log in into the registry 00:17:07.039 --> 00:17:08.110 align:start position:0% I'm going to log in into the registry I'm<00:17:07.079> going<00:17:07.199> to<00:17:07.280> start<00:17:07.439> making<00:17:07.679> a<00:17:07.799> proof<00:17:08.000> of 00:17:08.110 --> 00:17:08.120 align:start position:0% I'm going to start making a proof of 00:17:08.120 --> 00:17:10.390 align:start position:0% I'm going to start making a proof of that<00:17:08.199> email<00:17:08.520> so<00:17:09.039> I<00:17:09.160> hope<00:17:09.360> people<00:17:09.720> have<00:17:10.240> have 00:17:10.390 --> 00:17:10.400 align:start position:0% that email so I hope people have have 00:17:10.400 --> 00:17:12.390 align:start position:0% that email so I hope people have have kind<00:17:10.559> of<00:17:11.360> uh<00:17:11.520> found<00:17:11.799> an<00:17:11.919> email<00:17:12.160> they<00:17:12.240> want<00:17:12.319> to 00:17:12.390 --> 00:17:12.400 align:start position:0% kind of uh found an email they want to 00:17:12.400 --> 00:17:13.630 align:start position:0% kind of uh found an email they want to make<00:17:12.520> a<00:17:12.600> proof<00:17:12.799> of<00:17:12.959> open<00:17:13.160> the<00:17:13.280> original 00:17:13.630 --> 00:17:13.640 align:start position:0% make a proof of open the original 00:17:13.640 --> 00:17:15.230 align:start position:0% make a proof of open the original message<00:17:13.959> and<00:17:14.079> open<00:17:14.319> the<00:17:14.439> registry<00:17:14.799> and<00:17:14.959> logged 00:17:15.230 --> 00:17:15.240 align:start position:0% message and open the registry and logged 00:17:15.240 --> 00:17:18.429 align:start position:0% message and open the registry and logged in<00:17:15.799> and<00:17:15.959> gone<00:17:16.120> to<00:17:16.280> the<00:17:16.400> create<00:17:16.640> blueprint<00:17:17.400> page 00:17:18.429 --> 00:17:18.439 align:start position:0% in and gone to the create blueprint page 00:17:18.439 --> 00:17:21.350 align:start position:0% in and gone to the create blueprint page um<00:17:19.439> okay<00:17:19.600> so<00:17:19.760> if<00:17:19.919> you<00:17:20.400> you<00:17:20.520> know<00:17:20.799> emails<00:17:21.120> on<00:17:21.240> the 00:17:21.350 --> 00:17:21.360 align:start position:0% um okay so if you you know emails on the 00:17:21.360 --> 00:17:23.750 align:start position:0% um okay so if you you know emails on the top<00:17:21.559> right<00:17:21.880> uh<00:17:22.039> the<00:17:22.160> top<00:17:22.919> left<00:17:23.079> of<00:17:23.199> your<00:17:23.360> screen 00:17:23.750 --> 00:17:23.760 align:start position:0% top right uh the top left of your screen 00:17:23.760 --> 00:17:25.110 align:start position:0% top right uh the top left of your screen the<00:17:24.000> QR<00:17:24.240> code<00:17:24.400> is<00:17:24.480> on<00:17:24.600> the<00:17:24.679> top<00:17:24.839> right<00:17:24.959> this<00:17:25.039> is 00:17:25.110 --> 00:17:25.120 align:start position:0% the QR code is on the top right this is 00:17:25.120 --> 00:17:27.429 align:start position:0% the QR code is on the top right this is how<00:17:25.199> you<00:17:25.240> get<00:17:25.360> to<00:17:25.439> the<00:17:25.520> registry<00:17:26.480> um<00:17:26.760> okay<00:17:27.280> and 00:17:27.429 --> 00:17:27.439 align:start position:0% how you get to the registry um okay and 00:17:27.439 --> 00:17:29.190 align:start position:0% how you get to the registry um okay and here<00:17:27.640> I'm<00:17:27.799> going<00:17:28.000> to<00:17:28.280> to<00:17:28.400> name<00:17:28.559> the<00:17:28.679> p<00:17:28.880> patter 00:17:29.190 --> 00:17:29.200 align:start position:0% here I'm going to to name the p patter 00:17:29.200 --> 00:17:31.350 align:start position:0% here I'm going to to name the p patter let's<00:17:29.400> say<00:17:29.840> you<00:17:29.960> know 00:17:31.350 --> 00:17:31.360 align:start position:0% let's say you know 00:17:31.360 --> 00:17:34.070 align:start position:0% let's say you know alert 00:17:34.070 --> 00:17:34.080 align:start position:0% alert 00:17:34.080 --> 00:17:36.230 align:start position:0% alert uh 00:17:36.230 --> 00:17:36.240 align:start position:0% uh 00:17:36.240 --> 00:17:38.909 align:start position:0% uh Google<00:17:37.240> just<00:17:37.360> say<00:17:37.520> Google<00:17:37.799> Alerts<00:17:38.600> is<00:17:38.720> the<00:17:38.799> one 00:17:38.909 --> 00:17:38.919 align:start position:0% Google just say Google Alerts is the one 00:17:38.919 --> 00:17:43.270 align:start position:0% Google just say Google Alerts is the one I'm<00:17:39.039> going<00:17:39.120> to<00:17:39.280> do 00:17:43.270 --> 00:17:43.280 align:start position:0% 00:17:43.280 --> 00:17:46.110 align:start position:0% um<00:17:44.280> okay 00:17:46.110 --> 00:17:46.120 align:start position:0% um okay 00:17:46.120 --> 00:17:48.190 align:start position:0% um okay maybe<00:17:47.120> okay<00:17:47.280> maybe<00:17:47.520> raise<00:17:47.679> your<00:17:47.840> hand<00:17:48.039> if 00:17:48.190 --> 00:17:48.200 align:start position:0% maybe okay maybe raise your hand if 00:17:48.200 --> 00:17:50.070 align:start position:0% maybe okay maybe raise your hand if folks<00:17:48.480> have<00:17:48.679> like<00:17:48.799> opened<00:17:49.120> the<00:17:49.280> registry<00:17:49.880> and 00:17:50.070 --> 00:17:50.080 align:start position:0% folks have like opened the registry and 00:17:50.080 --> 00:17:51.750 align:start position:0% folks have like opened the registry and have<00:17:50.240> an<00:17:50.400> email<00:17:50.760> they<00:17:50.880> want<00:17:51.000> to<00:17:51.120> make<00:17:51.240> a<00:17:51.440> proof 00:17:51.750 --> 00:17:51.760 align:start position:0% have an email they want to make a proof 00:17:51.760 --> 00:17:56.110 align:start position:0% have an email they want to make a proof of<00:17:52.760> okay<00:17:53.600> okay<00:17:53.799> it's<00:17:53.960> like<00:17:54.120> about<00:17:54.400> half<00:17:55.080> um 00:17:56.110 --> 00:17:56.120 align:start position:0% of okay okay it's like about half um 00:17:56.120 --> 00:17:59.549 align:start position:0% of okay okay it's like about half um okay<00:17:57.200> um<00:17:58.200> cool<00:17:58.480> and<00:17:58.559> then<00:17:58.640> you<00:17:58.960> notice<00:17:59.440> this 00:17:59.549 --> 00:17:59.559 align:start position:0% okay um cool and then you notice this 00:17:59.559 --> 00:18:01.390 align:start position:0% okay um cool and then you notice this field<00:17:59.919> which<00:18:00.039> is<00:18:00.200> upload<00:18:00.520> test<00:18:00.760> EML<00:18:01.280> once 00:18:01.390 --> 00:18:01.400 align:start position:0% field which is upload test EML once 00:18:01.400 --> 00:18:03.029 align:start position:0% field which is upload test EML once you've<00:18:01.559> named<00:18:01.840> your<00:18:02.000> pattern<00:18:02.799> you're<00:18:02.960> going 00:18:03.029 --> 00:18:03.039 align:start position:0% you've named your pattern you're going 00:18:03.039 --> 00:18:04.870 align:start position:0% you've named your pattern you're going to<00:18:03.360> go<00:18:03.480> to<00:18:03.720> this<00:18:04.000> kind<00:18:04.120> of<00:18:04.240> raw<00:18:04.480> email<00:18:04.799> and 00:18:04.870 --> 00:18:04.880 align:start position:0% to go to this kind of raw email and 00:18:04.880 --> 00:18:07.190 align:start position:0% to go to this kind of raw email and you're<00:18:05.000> going<00:18:05.080> to<00:18:05.240> download<00:18:05.679> original<00:18:06.679> uh<00:18:07.039> in 00:18:07.190 --> 00:18:07.200 align:start position:0% you're going to download original uh in 00:18:07.200 --> 00:18:08.789 align:start position:0% you're going to download original uh in Gmail's<00:18:07.640> download<00:18:07.960> original<00:18:08.320> an<00:18:08.440> Outlook 00:18:08.789 --> 00:18:08.799 align:start position:0% Gmail's download original an Outlook 00:18:08.799 --> 00:18:10.430 align:start position:0% Gmail's download original an Outlook you'll<00:18:09.000> have<00:18:09.120> one<00:18:09.360> which<00:18:09.480> is<00:18:09.760> like<00:18:10.039> um 00:18:10.430 --> 00:18:10.440 align:start position:0% you'll have one which is like um 00:18:10.440 --> 00:18:11.870 align:start position:0% you'll have one which is like um download<00:18:10.799> original<00:18:11.200> message<00:18:11.480> and<00:18:11.600> you'll<00:18:11.760> get 00:18:11.870 --> 00:18:11.880 align:start position:0% download original message and you'll get 00:18:11.880 --> 00:18:13.950 align:start position:0% download original message and you'll get like<00:18:12.000> aeml<00:18:12.640> file<00:18:13.320> and<00:18:13.400> you'll<00:18:13.559> see<00:18:13.760> there's 00:18:13.950 --> 00:18:13.960 align:start position:0% like aeml file and you'll see there's 00:18:13.960 --> 00:18:16.750 align:start position:0% like aeml file and you'll see there's now<00:18:14.120> this<00:18:14.440> EML<00:18:14.840> file<00:18:15.799> um<00:18:16.360> that<00:18:16.480> just<00:18:16.600> got 00:18:16.750 --> 00:18:16.760 align:start position:0% now this EML file um that just got 00:18:16.760 --> 00:18:17.950 align:start position:0% now this EML file um that just got downloaded<00:18:17.159> and<00:18:17.240> you're<00:18:17.360> going<00:18:17.440> to<00:18:17.559> upload 00:18:17.950 --> 00:18:17.960 align:start position:0% downloaded and you're going to upload 00:18:17.960 --> 00:18:20.549 align:start position:0% downloaded and you're going to upload this<00:18:18.240> into<00:18:18.559> that<00:18:19.039> little<00:18:19.360> box<00:18:20.280> so<00:18:20.400> I'm<00:18:20.480> going 00:18:20.549 --> 00:18:20.559 align:start position:0% this into that little box so I'm going 00:18:20.559 --> 00:18:39.149 align:start position:0% this into that little box so I'm going to<00:18:20.679> click<00:18:20.840> to<00:18:21.000> upload 00:18:39.149 --> 00:18:39.159 align:start position:0% 00:18:39.159 --> 00:18:41.510 align:start position:0% okay 00:18:41.510 --> 00:18:41.520 align:start position:0% okay 00:18:41.520 --> 00:18:51.750 align:start position:0% okay um<00:18:42.520> be<00:18:43.480> um<00:18:43.960> can<00:18:44.120> you<00:18:45.120> you 00:18:51.750 --> 00:18:51.760 align:start position:0% 00:18:51.760 --> 00:18:53.750 align:start position:0% ever<00:18:52.760> whatever<00:18:52.960> that's<00:18:53.120> fine<00:18:53.440> give<00:18:53.520> me<00:18:53.679> give 00:18:53.750 --> 00:18:53.760 align:start position:0% ever whatever that's fine give me give 00:18:53.760 --> 00:18:57.710 align:start position:0% ever whatever that's fine give me give me<00:18:53.919> the<00:18:54.240> send<00:18:54.440> me 00:18:57.710 --> 00:18:57.720 align:start position:0% 00:18:57.720 --> 00:19:00.750 align:start position:0% um<00:18:58.799> send<00:18:58.960> send<00:18:59.120> me<00:18:59.200> a<00:18:59.320> link<00:18:59.480> to<00:18:59.720> the<00:19:00.200> um 00:19:00.750 --> 00:19:00.760 align:start position:0% um send send me a link to the um 00:19:00.760 --> 00:19:02.110 align:start position:0% um send send me a link to the um actually<00:19:00.960> we<00:19:01.080> have<00:19:01.159> the<00:19:01.280> chat<00:19:01.440> GPT<00:19:01.960> we're<00:19:02.039> just 00:19:02.110 --> 00:19:02.120 align:start position:0% actually we have the chat GPT we're just 00:19:02.120 --> 00:19:05.110 align:start position:0% actually we have the chat GPT we're just going<00:19:02.200> to<00:19:02.280> use<00:19:02.400> the<00:19:02.480> chat 00:19:05.110 --> 00:19:05.120 align:start position:0% 00:19:05.120 --> 00:19:17.149 align:start position:0% GPT<00:19:06.120> okay<00:19:06.400> that's<00:19:06.520> fine<00:19:06.640> we<00:19:07.039> yeah<00:19:07.159> what's 00:19:17.149 --> 00:19:17.159 align:start position:0% 00:19:17.159 --> 00:19:20.990 align:start position:0% up<00:19:18.440> um<00:19:19.440> cool<00:19:19.840> okay<00:19:20.120> maybe<00:19:20.400> raise<00:19:20.600> your<00:19:20.760> hand<00:19:20.919> if 00:19:20.990 --> 00:19:21.000 align:start position:0% up um cool okay maybe raise your hand if 00:19:21.000 --> 00:19:24.270 align:start position:0% up um cool okay maybe raise your hand if you've<00:19:21.200> uploaded<00:19:21.600> the<00:19:21.720> example<00:19:22.400> EML<00:19:23.400> um<00:19:23.720> sweet 00:19:24.270 --> 00:19:24.280 align:start position:0% you've uploaded the example EML um sweet 00:19:24.280 --> 00:19:26.110 align:start position:0% you've uploaded the example EML um sweet okay<00:19:24.919> and<00:19:25.039> then<00:19:25.280> we<00:19:25.400> can<00:19:25.520> start<00:19:25.679> filling<00:19:26.000> out 00:19:26.110 --> 00:19:26.120 align:start position:0% okay and then we can start filling out 00:19:26.120 --> 00:19:28.909 align:start position:0% okay and then we can start filling out the<00:19:26.400> fields<00:19:27.400> um<00:19:27.679> you<00:19:27.760> know<00:19:27.960> tags<00:19:28.280> this<00:19:28.400> is<00:19:28.559> like 00:19:28.909 --> 00:19:28.919 align:start position:0% the fields um you know tags this is like 00:19:28.919 --> 00:19:33.149 align:start position:0% the fields um you know tags this is like Google<00:19:29.320> alert<00:19:30.400> um<00:19:31.400> prove<00:19:31.760> you<00:19:32.000> got<00:19:32.280> a<00:19:32.480> Google 00:19:33.149 --> 00:19:33.159 align:start position:0% Google alert um prove you got a Google 00:19:33.159 --> 00:19:38.430 align:start position:0% Google alert um prove you got a Google alert<00:19:34.159> for<00:19:34.440> some<00:19:35.200> keyword<00:19:36.200> okay<00:19:37.080> um<00:19:38.080> email 00:19:38.430 --> 00:19:38.440 align:start position:0% alert for some keyword okay um email 00:19:38.440 --> 00:19:39.909 align:start position:0% alert for some keyword okay um email query<00:19:38.919> I<00:19:38.960> mean<00:19:39.120> Demitri<00:19:39.520> explained<00:19:39.799> this 00:19:39.909 --> 00:19:39.919 align:start position:0% query I mean Demitri explained this 00:19:39.919 --> 00:19:41.510 align:start position:0% query I mean Demitri explained this earlier<00:19:40.240> but<00:19:40.360> we're<00:19:40.480> going<00:19:40.559> to<00:19:40.720> fill<00:19:40.919> out<00:19:41.200> like 00:19:41.510 --> 00:19:41.520 align:start position:0% earlier but we're going to fill out like 00:19:41.520 --> 00:19:43.350 align:start position:0% earlier but we're going to fill out like when<00:19:41.720> I<00:19:41.919> actually<00:19:42.120> search<00:19:42.440> to<00:19:42.600> my<00:19:42.720> inbox<00:19:43.159> to 00:19:43.350 --> 00:19:43.360 align:start position:0% when I actually search to my inbox to 00:19:43.360 --> 00:19:45.310 align:start position:0% when I actually search to my inbox to get<00:19:43.679> this 00:19:45.310 --> 00:19:45.320 align:start position:0% get this 00:19:45.320 --> 00:19:49.270 align:start position:0% get this value<00:19:46.320> you<00:19:46.440> know<00:19:47.039> maybe<00:19:47.240> it'll<00:19:47.400> be<00:19:47.559> like<00:19:48.120> this 00:19:49.270 --> 00:19:49.280 align:start position:0% value you know maybe it'll be like this 00:19:49.280 --> 00:19:51.390 align:start position:0% value you know maybe it'll be like this um<00:19:50.280> this<00:19:50.360> is<00:19:50.480> going<00:19:50.559> to<00:19:50.679> be<00:19:50.760> the<00:19:50.960> string<00:19:51.280> we 00:19:51.390 --> 00:19:51.400 align:start position:0% um this is going to be the string we 00:19:51.400 --> 00:19:53.310 align:start position:0% um this is going to be the string we literally<00:19:51.840> put<00:19:52.080> into<00:19:52.320> your<00:19:52.480> email<00:19:52.760> search<00:19:53.080> bar 00:19:53.310 --> 00:19:53.320 align:start position:0% literally put into your email search bar 00:19:53.320 --> 00:19:55.430 align:start position:0% literally put into your email search bar to<00:19:53.480> fetch<00:19:53.720> that<00:19:53.880> email<00:19:54.200> out<00:19:54.720> automatically<00:19:55.320> so 00:19:55.430 --> 00:19:55.440 align:start position:0% to fetch that email out automatically so 00:19:55.440 --> 00:19:57.430 align:start position:0% to fetch that email out automatically so in<00:19:55.600> this<00:19:55.760> case<00:19:56.320> I'm<00:19:56.440> going<00:19:56.559> to<00:19:56.720> put<00:19:56.880> in<00:19:57.320> you 00:19:57.430 --> 00:19:57.440 align:start position:0% in this case I'm going to put in you 00:19:57.440 --> 00:19:59.669 align:start position:0% in this case I'm going to put in you know<00:19:57.600> Google<00:19:57.919> Alerts 00:19:59.669 --> 00:19:59.679 align:start position:0% know Google Alerts 00:19:59.679 --> 00:20:01.070 align:start position:0% know Google Alerts um<00:19:59.799> but<00:19:59.880> you<00:19:59.960> should<00:20:00.159> put<00:20:00.280> in<00:20:00.400> your<00:20:00.520> own<00:20:00.760> query 00:20:01.070 --> 00:20:01.080 align:start position:0% um but you should put in your own query 00:20:01.080 --> 00:20:02.630 align:start position:0% um but you should put in your own query for<00:20:01.320> what<00:20:01.480> would<00:20:01.720> result<00:20:02.200> when<00:20:02.320> you<00:20:02.400> search 00:20:02.630 --> 00:20:02.640 align:start position:0% for what would result when you search 00:20:02.640 --> 00:20:06.110 align:start position:0% for what would result when you search your<00:20:02.760> inbox<00:20:03.120> to<00:20:03.280> get<00:20:03.400> that<00:20:03.840> email 00:20:06.110 --> 00:20:06.120 align:start position:0% your inbox to get that email 00:20:06.120 --> 00:20:08.230 align:start position:0% your inbox to get that email um 00:20:08.230 --> 00:20:08.240 align:start position:0% um 00:20:08.240 --> 00:20:09.830 align:start position:0% um cool 00:20:09.830 --> 00:20:09.840 align:start position:0% cool 00:20:09.840 --> 00:20:14.149 align:start position:0% cool um<00:20:10.840> okay<00:20:11.360> and<00:20:11.480> then<00:20:12.159> skip<00:20:12.520> body<00:20:12.840> hash<00:20:13.120> check<00:20:14.000> uh 00:20:14.149 --> 00:20:14.159 align:start position:0% um okay and then skip body hash check uh 00:20:14.159 --> 00:20:15.710 align:start position:0% um okay and then skip body hash check uh this<00:20:14.280> is<00:20:14.799> will<00:20:14.960> depend<00:20:15.240> whether<00:20:15.400> you<00:20:15.480> want<00:20:15.600> to 00:20:15.710 --> 00:20:15.720 align:start position:0% this is will depend whether you want to 00:20:15.720 --> 00:20:17.470 align:start position:0% this is will depend whether you want to extract<00:20:16.080> information<00:20:16.559> out<00:20:16.720> of<00:20:17.080> the<00:20:17.159> email 00:20:17.470 --> 00:20:17.480 align:start position:0% extract information out of the email 00:20:17.480 --> 00:20:19.029 align:start position:0% extract information out of the email subject<00:20:17.760> or<00:20:17.919> body<00:20:18.200> in<00:20:18.320> this<00:20:18.440> case<00:20:18.640> I<00:20:18.760> only<00:20:18.919> want 00:20:19.029 --> 00:20:19.039 align:start position:0% subject or body in this case I only want 00:20:19.039 --> 00:20:21.070 align:start position:0% subject or body in this case I only want to<00:20:19.159> extract<00:20:19.480> information<00:20:19.840> out<00:20:19.960> of<00:20:20.080> the<00:20:20.200> email 00:20:21.070 --> 00:20:21.080 align:start position:0% to extract information out of the email 00:20:21.080 --> 00:20:23.149 align:start position:0% to extract information out of the email subject<00:20:21.440> like<00:20:21.559> I<00:20:21.679> want<00:20:21.760> to<00:20:21.880> extract<00:20:22.320> this<00:20:22.440> word 00:20:23.149 --> 00:20:23.159 align:start position:0% subject like I want to extract this word 00:20:23.159 --> 00:20:24.750 align:start position:0% subject like I want to extract this word and<00:20:23.280> so<00:20:23.400> I'm<00:20:23.520> going<00:20:23.679> to<00:20:23.840> skip<00:20:24.120> the<00:20:24.240> body<00:20:24.520> hash 00:20:24.750 --> 00:20:24.760 align:start position:0% and so I'm going to skip the body hash 00:20:24.760 --> 00:20:26.270 align:start position:0% and so I'm going to skip the body hash check<00:20:25.000> if<00:20:25.080> you<00:20:25.159> want<00:20:25.280> to<00:20:25.400> exract<00:20:25.880> value<00:20:26.080> out<00:20:26.200> of 00:20:26.270 --> 00:20:26.280 align:start position:0% check if you want to exract value out of 00:20:26.280 --> 00:20:29.590 align:start position:0% check if you want to exract value out of the<00:20:26.400> body<00:20:26.799> leave<00:20:27.080> the<00:20:27.200> body<00:20:27.480> hash<00:20:27.720> check<00:20:28.799> okay 00:20:29.590 --> 00:20:29.600 align:start position:0% the body leave the body hash check okay 00:20:29.600 --> 00:20:32.310 align:start position:0% the body leave the body hash check okay um<00:20:29.760> Center<00:20:30.120> domain<00:20:31.080> in<00:20:31.200> this<00:20:31.400> case<00:20:31.720> I<00:20:31.840> can<00:20:32.039> look 00:20:32.310 --> 00:20:32.320 align:start position:0% um Center domain in this case I can look 00:20:32.320 --> 00:20:36.029 align:start position:0% um Center domain in this case I can look at<00:20:32.600> the 00:20:36.029 --> 00:20:36.039 align:start position:0% 00:20:36.039 --> 00:20:39.270 align:start position:0% Domain<00:20:37.480> um<00:20:38.480> you<00:20:38.600> know<00:20:38.720> we'll<00:20:38.840> see<00:20:39.039> this<00:20:39.120> was 00:20:39.270 --> 00:20:39.280 align:start position:0% Domain um you know we'll see this was 00:20:39.280 --> 00:20:41.190 align:start position:0% Domain um you know we'll see this was sent<00:20:39.559> from<00:20:39.880> google.com<00:20:40.840> and<00:20:40.919> so<00:20:41.039> I'm<00:20:41.080> just 00:20:41.190 --> 00:20:41.200 align:start position:0% sent from google.com and so I'm just 00:20:41.200 --> 00:20:43.029 align:start position:0% sent from google.com and so I'm just going<00:20:41.280> to<00:20:41.360> take<00:20:41.480> this<00:20:41.720> Google.com<00:20:42.720> I'm<00:20:42.880> stick 00:20:43.029 --> 00:20:43.039 align:start position:0% going to take this Google.com I'm stick 00:20:43.039 --> 00:20:47.510 align:start position:0% going to take this Google.com I'm stick it<00:20:43.159> into<00:20:43.280> the<00:20:43.360> center<00:20:43.880> domain 00:20:47.510 --> 00:20:47.520 align:start position:0% 00:20:47.520 --> 00:20:51.549 align:start position:0% cool<00:20:48.520> okay 00:20:51.549 --> 00:20:51.559 align:start position:0% 00:20:51.559 --> 00:20:53.789 align:start position:0% um<00:20:52.559> and<00:20:52.799> actually<00:20:53.039> one<00:20:53.200> thing<00:20:53.360> I'm<00:20:53.480> going<00:20:53.640> to 00:20:53.789 --> 00:20:53.799 align:start position:0% um and actually one thing I'm going to 00:20:53.799 --> 00:20:57.390 align:start position:0% um and actually one thing I'm going to do<00:20:54.039> as<00:20:54.520> well<00:20:55.520> is<00:20:56.039> pull 00:20:57.390 --> 00:20:57.400 align:start position:0% do as well is pull 00:20:57.400 --> 00:21:14.830 align:start position:0% do as well is pull up<00:20:58.400> um 00:21:14.830 --> 00:21:14.840 align:start position:0% 00:21:14.840 --> 00:21:18.070 align:start position:0% let<00:21:15.000> me<00:21:15.240> see<00:21:15.600> if<00:21:15.799> I 00:21:18.070 --> 00:21:18.080 align:start position:0% 00:21:18.080 --> 00:21:21.549 align:start position:0% can<00:21:19.080> okay<00:21:19.400> and<00:21:19.559> then<00:21:20.159> um<00:21:20.679> this<00:21:20.919> AI<00:21:21.320> I<00:21:21.400> think 00:21:21.549 --> 00:21:21.559 align:start position:0% can okay and then um this AI I think 00:21:21.559 --> 00:21:23.909 align:start position:0% can okay and then um this AI I think there's<00:21:22.200> too<00:21:22.360> many<00:21:22.840> people<00:21:23.159> who<00:21:23.279> are<00:21:23.440> going<00:21:23.640> to 00:21:23.909 --> 00:21:23.919 align:start position:0% there's too many people who are going to 00:21:23.919 --> 00:21:27.310 align:start position:0% there's too many people who are going to trigger<00:21:25.120> the<00:21:26.120> uh<00:21:26.320> AI<00:21:26.559> Auto<00:21:26.840> extraction<00:21:27.240> right 00:21:27.310 --> 00:21:27.320 align:start position:0% trigger the uh AI Auto extraction right 00:21:27.320 --> 00:21:28.830 align:start position:0% trigger the uh AI Auto extraction right now<00:21:27.440> so<00:21:27.559> we're<00:21:27.880> likely<00:21:28.120> going<00:21:28.279> to<00:21:28.400> get<00:21:28.640> rate 00:21:28.830 --> 00:21:28.840 align:start position:0% now so we're likely going to get rate 00:21:28.840 --> 00:21:31.110 align:start position:0% now so we're likely going to get rate limited<00:21:29.640> but<00:21:29.799> if<00:21:29.880> you<00:21:30.000> use<00:21:30.120> a<00:21:30.240> chat<00:21:30.440> gbt<00:21:30.799> bot<00:21:31.039> on 00:21:31.110 --> 00:21:31.120 align:start position:0% limited but if you use a chat gbt bot on 00:21:31.120 --> 00:21:32.710 align:start position:0% limited but if you use a chat gbt bot on the<00:21:31.279> top<00:21:31.520> right<00:21:31.720> then<00:21:31.840> you<00:21:31.960> will<00:21:32.159> not<00:21:32.320> get<00:21:32.480> rate 00:21:32.710 --> 00:21:32.720 align:start position:0% the top right then you will not get rate 00:21:32.720 --> 00:21:34.149 align:start position:0% the top right then you will not get rate limited 00:21:34.149 --> 00:21:34.159 align:start position:0% limited 00:21:34.159 --> 00:21:36.029 align:start position:0% limited um<00:21:35.159> and<00:21:35.240> then<00:21:35.400> this<00:21:35.480> will<00:21:35.640> let<00:21:35.799> you 00:21:36.029 --> 00:21:36.039 align:start position:0% um and then this will let you 00:21:36.039 --> 00:21:37.510 align:start position:0% um and then this will let you automatically<00:21:36.600> extract<00:21:36.880> these<00:21:37.000> fields<00:21:37.360> I<00:21:37.440> can 00:21:37.510 --> 00:21:37.520 align:start position:0% automatically extract these fields I can 00:21:37.520 --> 00:21:39.950 align:start position:0% automatically extract these fields I can say<00:21:37.640> something<00:21:37.880> like<00:21:37.960> you<00:21:38.080> know<00:21:38.679> extract 00:21:39.950 --> 00:21:39.960 align:start position:0% say something like you know extract 00:21:39.960 --> 00:21:45.909 align:start position:0% say something like you know extract the<00:21:40.960> uh<00:21:41.840> actual<00:21:42.320> value<00:21:42.880> of<00:21:43.240> the<00:21:44.240> being<00:21:44.919> alerted 00:21:45.909 --> 00:21:45.919 align:start position:0% the uh actual value of the being alerted 00:21:45.919 --> 00:21:48.470 align:start position:0% the uh actual value of the being alerted for<00:21:46.360> from<00:21:46.640> the<00:21:46.840> subject<00:21:47.799> and<00:21:47.919> it<00:21:48.039> should 00:21:48.470 --> 00:21:48.480 align:start position:0% for from the subject and it should 00:21:48.480 --> 00:21:50.310 align:start position:0% for from the subject and it should automatically<00:21:48.960> fill<00:21:49.320> that<00:21:49.760> um<00:21:50.000> but<00:21:50.120> because 00:21:50.310 --> 00:21:50.320 align:start position:0% automatically fill that um but because 00:21:50.320 --> 00:21:51.269 align:start position:0% automatically fill that um but because we<00:21:50.400> might<00:21:50.520> get<00:21:50.600> very<00:21:50.760> limited<00:21:51.039> you<00:21:51.080> might<00:21:51.200> have 00:21:51.269 --> 00:21:51.279 align:start position:0% we might get very limited you might have 00:21:51.279 --> 00:21:52.990 align:start position:0% we might get very limited you might have to<00:21:51.360> scan<00:21:51.640> this<00:21:51.799> QR<00:21:52.039> code<00:21:52.200> for<00:21:52.279> the<00:21:52.360> chat<00:21:52.559> gbt 00:21:52.990 --> 00:21:53.000 align:start position:0% to scan this QR code for the chat gbt 00:21:53.000 --> 00:21:54.909 align:start position:0% to scan this QR code for the chat gbt bot<00:21:53.559> and<00:21:53.640> then<00:21:53.799> paste<00:21:54.000> in<00:21:54.120> the<00:21:54.240> email<00:21:54.600> and<00:21:54.799> and 00:21:54.909 --> 00:21:54.919 align:start position:0% bot and then paste in the email and and 00:21:54.919 --> 00:21:56.230 align:start position:0% bot and then paste in the email and and ask<00:21:55.120> you<00:21:55.200> know<00:21:55.320> I<00:21:55.400> want<00:21:55.480> to<00:21:55.600> extract<00:21:55.960> this<00:21:56.080> what 00:21:56.230 --> 00:21:56.240 align:start position:0% ask you know I want to extract this what 00:21:56.240 --> 00:21:58.230 align:start position:0% ask you know I want to extract this what Rex<00:21:56.600> should<00:21:56.720> I<00:21:56.880> use<00:21:57.440> or<00:21:57.600> you<00:21:57.720> can<00:21:57.880> kind<00:21:58.000> of<00:21:58.120> just 00:21:58.230 --> 00:21:58.240 align:start position:0% Rex should I use or you can kind of just 00:21:58.240 --> 00:22:01.510 align:start position:0% Rex should I use or you can kind of just man<00:21:58.840> ually<00:21:59.840> put<00:21:59.960> in<00:22:00.080> your<00:22:00.240> Rex<00:22:00.960> um<00:22:01.279> although 00:22:01.510 --> 00:22:01.520 align:start position:0% man ually put in your Rex um although 00:22:01.520 --> 00:22:04.830 align:start position:0% man ually put in your Rex um although that<00:22:01.640> might<00:22:01.840> be<00:22:02.000> a<00:22:02.080> little<00:22:02.240> bit<00:22:02.679> harder<00:22:03.840> um 00:22:04.830 --> 00:22:04.840 align:start position:0% that might be a little bit harder um 00:22:04.840 --> 00:22:07.830 align:start position:0% that might be a little bit harder um cool<00:22:05.120> and<00:22:05.240> then<00:22:05.960> uh<00:22:06.080> once<00:22:06.240> you're<00:22:06.520> ready<00:22:07.520> uh 00:22:07.830 --> 00:22:07.840 align:start position:0% cool and then uh once you're ready uh 00:22:07.840 --> 00:22:09.029 align:start position:0% cool and then uh once you're ready uh you<00:22:07.960> know<00:22:08.080> you<00:22:08.159> can<00:22:08.279> hit<00:22:08.400> save<00:22:08.559> as<00:22:08.720> draft<00:22:08.960> if 00:22:09.029 --> 00:22:09.039 align:start position:0% you know you can hit save as draft if 00:22:09.039 --> 00:22:10.710 align:start position:0% you know you can hit save as draft if you<00:22:09.120> want<00:22:09.200> to<00:22:09.320> come<00:22:09.440> back<00:22:09.559> to<00:22:09.679> this<00:22:09.840> later<00:22:10.440> or 00:22:10.710 --> 00:22:10.720 align:start position:0% you want to come back to this later or 00:22:10.720 --> 00:22:12.510 align:start position:0% you want to come back to this later or compile<00:22:11.120> blueprint<00:22:11.679> so<00:22:11.880> if<00:22:11.960> you<00:22:12.159> submit<00:22:12.440> the 00:22:12.510 --> 00:22:12.520 align:start position:0% compile blueprint so if you submit the 00:22:12.520 --> 00:22:14.990 align:start position:0% compile blueprint so if you submit the blueprint<00:22:13.320> then<00:22:13.480> that<00:22:13.600> will<00:22:13.799> basically<00:22:14.559> hit 00:22:14.990 --> 00:22:15.000 align:start position:0% blueprint then that will basically hit 00:22:15.000 --> 00:22:16.830 align:start position:0% blueprint then that will basically hit like<00:22:15.200> our<00:22:15.360> server<00:22:15.679> will<00:22:15.799> start<00:22:15.960> generating<00:22:16.320> ZK 00:22:16.830 --> 00:22:16.840 align:start position:0% like our server will start generating ZK 00:22:16.840 --> 00:22:18.669 align:start position:0% like our server will start generating ZK like<00:22:16.919> a<00:22:17.039> ZK<00:22:17.360> circuit<00:22:17.640> for<00:22:17.799> it<00:22:18.279> and<00:22:18.440> actually 00:22:18.669 --> 00:22:18.679 align:start position:0% like a ZK circuit for it and actually 00:22:18.679 --> 00:22:20.310 align:start position:0% like a ZK circuit for it and actually generating<00:22:19.039> a<00:22:19.120> unique<00:22:19.400> circuit<00:22:19.799> takes<00:22:20.080> like<00:22:20.240> a 00:22:20.310 --> 00:22:20.320 align:start position:0% generating a unique circuit takes like a 00:22:20.320 --> 00:22:22.110 align:start position:0% generating a unique circuit takes like a few<00:22:20.520> hours<00:22:20.760> the<00:22:20.919> first<00:22:21.080> time<00:22:21.240> you<00:22:21.360> do<00:22:21.520> it<00:22:22.000> and 00:22:22.110 --> 00:22:22.120 align:start position:0% few hours the first time you do it and 00:22:22.120 --> 00:22:24.230 align:start position:0% few hours the first time you do it and so<00:22:22.279> the<00:22:22.360> hope<00:22:22.559> is<00:22:22.760> by<00:22:22.880> the<00:22:22.960> end<00:22:23.159> of<00:22:23.480> you<00:22:23.640> know 00:22:24.230 --> 00:22:24.240 align:start position:0% so the hope is by the end of you know 00:22:24.240 --> 00:22:26.269 align:start position:0% so the hope is by the end of you know this<00:22:24.400> few<00:22:24.640> minute<00:22:24.960> process<00:22:25.279> everybody's<00:22:26.120> at 00:22:26.269 --> 00:22:26.279 align:start position:0% this few minute process everybody's at 00:22:26.279 --> 00:22:28.149 align:start position:0% this few minute process everybody's at least<00:22:26.640> submitted<00:22:27.039> a<00:22:27.120> blueprint<00:22:27.760> and<00:22:27.960> if<00:22:28.039> you 00:22:28.149 --> 00:22:28.159 align:start position:0% least submitted a blueprint and if you 00:22:28.159 --> 00:22:29.510 align:start position:0% least submitted a blueprint and if you come<00:22:28.320> back<00:22:28.600> tonight<00:22:28.880> or<00:22:29.000> tomorrow<00:22:29.360> or 00:22:29.510 --> 00:22:29.520 align:start position:0% come back tonight or tomorrow or 00:22:29.520 --> 00:22:31.230 align:start position:0% come back tonight or tomorrow or something<00:22:30.080> hopefully<00:22:30.440> it's<00:22:30.600> been<00:22:30.760> generated 00:22:31.230 --> 00:22:31.240 align:start position:0% something hopefully it's been generated 00:22:31.240 --> 00:22:32.269 align:start position:0% something hopefully it's been generated and<00:22:31.320> then<00:22:31.400> you<00:22:31.480> can<00:22:31.559> start<00:22:31.720> making<00:22:31.919> proofs<00:22:32.159> of 00:22:32.269 --> 00:22:32.279 align:start position:0% and then you can start making proofs of 00:22:32.279 --> 00:22:33.750 align:start position:0% and then you can start making proofs of it<00:22:32.400> but<00:22:32.520> we'll<00:22:32.880> do<00:22:33.000> the<00:22:33.120> rest<00:22:33.240> of<00:22:33.320> the<00:22:33.400> workshop 00:22:33.750 --> 00:22:33.760 align:start position:0% it but we'll do the rest of the workshop 00:22:33.760 --> 00:22:35.350 align:start position:0% it but we'll do the rest of the workshop with<00:22:33.919> like<00:22:34.039> our<00:22:34.240> existing<00:22:34.760> compiled 00:22:35.350 --> 00:22:35.360 align:start position:0% with like our existing compiled 00:22:35.360 --> 00:22:38.230 align:start position:0% with like our existing compiled blueprints<00:22:36.360> um<00:22:37.320> cool<00:22:37.520> do<00:22:37.640> people<00:22:37.919> like<00:22:38.039> have 00:22:38.230 --> 00:22:38.240 align:start position:0% blueprints um cool do people like have 00:22:38.240 --> 00:22:39.710 align:start position:0% blueprints um cool do people like have questions<00:22:38.760> because<00:22:38.960> I<00:22:39.039> know<00:22:39.200> only<00:22:39.440> half<00:22:39.559> the 00:22:39.710 --> 00:22:39.720 align:start position:0% questions because I know only half the 00:22:39.720 --> 00:22:52.830 align:start position:0% questions because I know only half the people<00:22:40.080> yeah<00:22:40.400> okay<00:22:40.679> people<00:22:40.799> want 00:22:52.830 --> 00:22:52.840 align:start position:0% 00:22:52.840 --> 00:22:57.430 align:start position:0% to<00:22:53.840> you<00:22:54.279> theem 00:22:57.430 --> 00:22:57.440 align:start position:0% 00:22:57.440 --> 00:23:02.269 align:start position:0% and<00:22:58.520> for<00:22:58.640> a<00:22:58.760> while<00:22:59.799> um<00:23:00.799> there<00:23:01.039> might<00:23:01.279> be<00:23:01.559> like<00:23:01.799> a 00:23:02.269 --> 00:23:02.279 align:start position:0% and for a while um there might be like a 00:23:02.279 --> 00:23:04.750 align:start position:0% and for a while um there might be like a r 00:23:04.750 --> 00:23:04.760 align:start position:0% 00:23:04.760 --> 00:23:08.510 align:start position:0% liting<00:23:05.760> right<00:23:06.159> now 00:23:08.510 --> 00:23:08.520 align:start position:0% liting right now 00:23:08.520 --> 00:23:11.909 align:start position:0% liting right now um<00:23:09.520> yeah<00:23:09.799> maybe<00:23:10.240> I<00:23:10.320> would<00:23:10.520> suggest<00:23:11.320> either<00:23:11.679> try 00:23:11.909 --> 00:23:11.919 align:start position:0% um yeah maybe I would suggest either try 00:23:11.919 --> 00:23:25.669 align:start position:0% um yeah maybe I would suggest either try a<00:23:12.080> different<00:23:12.480> patter<00:23:13.279> or 00:23:25.669 --> 00:23:25.679 align:start position:0% 00:23:25.679 --> 00:23:29.269 align:start position:0% try<00:23:26.679> um<00:23:26.799> so<00:23:26.960> if<00:23:27.039> I<00:23:27.159> go<00:23:27.320> up<00:23:27.559> here<00:23:28.760> this<00:23:28.960> email 00:23:29.269 --> 00:23:29.279 align:start position:0% try um so if I go up here this email 00:23:29.279 --> 00:23:30.870 align:start position:0% try um so if I go up here this email search<00:23:29.600> query<00:23:29.919> is<00:23:30.080> literally<00:23:30.440> going<00:23:30.600> to<00:23:30.720> be 00:23:30.870 --> 00:23:30.880 align:start position:0% search query is literally going to be 00:23:30.880 --> 00:23:33.190 align:start position:0% search query is literally going to be the<00:23:31.039> thing<00:23:31.400> in<00:23:31.600> this<00:23:31.760> search<00:23:32.039> bar<00:23:32.279> up<00:23:32.480> here<00:23:33.080> so 00:23:33.190 --> 00:23:33.200 align:start position:0% the thing in this search bar up here so 00:23:33.200 --> 00:23:34.590 align:start position:0% the thing in this search bar up here so it's<00:23:33.320> like<00:23:33.440> if<00:23:33.559> I<00:23:33.640> were<00:23:33.760> to<00:23:33.840> search<00:23:34.080> my<00:23:34.240> inbox 00:23:34.590 --> 00:23:34.600 align:start position:0% it's like if I were to search my inbox 00:23:34.600 --> 00:23:36.789 align:start position:0% it's like if I were to search my inbox to<00:23:34.720> try<00:23:34.880> to<00:23:35.039> extract<00:23:35.480> that<00:23:35.679> value<00:23:36.559> what<00:23:36.679> would 00:23:36.789 --> 00:23:36.799 align:start position:0% to try to extract that value what would 00:23:36.799 --> 00:23:37.950 align:start position:0% to try to extract that value what would I<00:23:36.880> literally<00:23:37.200> be<00:23:37.320> searching<00:23:37.600> for<00:23:37.799> and<00:23:37.880> that 00:23:37.950 --> 00:23:37.960 align:start position:0% I literally be searching for and that 00:23:37.960 --> 00:23:39.430 align:start position:0% I literally be searching for and that will<00:23:38.120> filter<00:23:38.400> my<00:23:38.559> inbox<00:23:38.880> and<00:23:39.000> say<00:23:39.200> these<00:23:39.279> are 00:23:39.430 --> 00:23:39.440 align:start position:0% will filter my inbox and say these are 00:23:39.440 --> 00:23:41.149 align:start position:0% will filter my inbox and say these are the<00:23:39.559> possible<00:23:39.880> emails<00:23:40.600> that<00:23:40.720> might<00:23:40.840> be<00:23:40.960> used 00:23:41.149 --> 00:23:41.159 align:start position:0% the possible emails that might be used 00:23:41.159 --> 00:23:46.870 align:start position:0% the possible emails that might be used as<00:23:41.240> a<00:23:41.360> valid<00:23:41.679> proof<00:23:42.120> in<00:23:42.520> this 00:23:46.870 --> 00:23:46.880 align:start position:0% 00:23:46.880 --> 00:23:49.110 align:start position:0% proof<00:23:47.880> so<00:23:48.159> the<00:23:48.240> point<00:23:48.440> is<00:23:48.600> when<00:23:48.760> people 00:23:49.110 --> 00:23:49.120 align:start position:0% proof so the point is when people 00:23:49.120 --> 00:23:51.190 align:start position:0% proof so the point is when people actually<00:23:49.440> try<00:23:49.720> this<00:23:49.919> out<00:23:50.520> they're<00:23:50.760> going<00:23:51.000> to 00:23:51.190 --> 00:23:51.200 align:start position:0% actually try this out they're going to 00:23:51.200 --> 00:23:56.390 align:start position:0% actually try this out they're going to you<00:23:51.320> know<00:23:51.960> go<00:23:52.240> to<00:23:52.799> to<00:23:52.960> the<00:23:53.480> registry 00:23:56.390 --> 00:23:56.400 align:start position:0% you know go to to the registry 00:23:56.400 --> 00:23:58.990 align:start position:0% you know go to to the registry um<00:23:57.400> and<00:23:57.559> then<00:23:57.760> maybe<00:23:58.000> they're<00:23:58.120> going<00:23:58.240> to<00:23:58.600> use 00:23:58.990 --> 00:23:59.000 align:start position:0% um and then maybe they're going to use 00:23:59.000 --> 00:24:02.470 align:start position:0% um and then maybe they're going to use let<00:23:59.120> me<00:23:59.480> find<00:23:59.720> one<00:23:59.799> of<00:23:59.919> these<00:24:00.080> patterns<00:24:01.279> um<00:24:02.279> you 00:24:02.470 --> 00:24:02.480 align:start position:0% let me find one of these patterns um you 00:24:02.480 --> 00:24:03.630 align:start position:0% let me find one of these patterns um you I<00:24:02.559> don't<00:24:02.679> know<00:24:02.919> what<00:24:03.000> is<00:24:03.080> a<00:24:03.200> pattern<00:24:03.480> I<00:24:03.559> can 00:24:03.630 --> 00:24:03.640 align:start position:0% I don't know what is a pattern I can 00:24:03.640 --> 00:24:05.870 align:start position:0% I don't know what is a pattern I can make<00:24:03.760> a<00:24:03.919> proof<00:24:04.200> of<00:24:04.799> um<00:24:05.360> maybe<00:24:05.559> like<00:24:05.679> Google 00:24:05.870 --> 00:24:05.880 align:start position:0% make a proof of um maybe like Google 00:24:05.880 --> 00:24:07.990 align:start position:0% make a proof of um maybe like Google alerts<00:24:06.159> or<00:24:06.240> something<00:24:06.600> and<00:24:06.799> then<00:24:07.480> I<00:24:07.559> am<00:24:07.799> going 00:24:07.990 --> 00:24:08.000 align:start position:0% alerts or something and then I am going 00:24:08.000 --> 00:24:11.430 align:start position:0% alerts or something and then I am going to<00:24:08.400> like<00:24:09.400> uh<00:24:09.640> hit<00:24:09.840> connect<00:24:10.559> like<00:24:10.720> most<00:24:10.919> people 00:24:11.430 --> 00:24:11.440 align:start position:0% to like uh hit connect like most people 00:24:11.440 --> 00:24:12.830 align:start position:0% to like uh hit connect like most people hit<00:24:11.559> connect<00:24:11.840> Gmail<00:24:12.200> account<00:24:12.520> and<00:24:12.640> then 00:24:12.830 --> 00:24:12.840 align:start position:0% hit connect Gmail account and then 00:24:12.840 --> 00:24:14.710 align:start position:0% hit connect Gmail account and then automatically<00:24:13.640> want<00:24:13.840> to<00:24:14.000> choose<00:24:14.400> which<00:24:14.480> email 00:24:14.710 --> 00:24:14.720 align:start position:0% automatically want to choose which email 00:24:14.720 --> 00:24:16.310 align:start position:0% automatically want to choose which email to<00:24:14.799> make<00:24:14.919> a<00:24:15.039> proof<00:24:15.240> of<00:24:15.360> and<00:24:15.480> the<00:24:15.559> point<00:24:15.799> is<00:24:16.159> once 00:24:16.310 --> 00:24:16.320 align:start position:0% to make a proof of and the point is once 00:24:16.320 --> 00:24:17.990 align:start position:0% to make a proof of and the point is once you<00:24:16.440> connect<00:24:16.760> it'll<00:24:16.919> filter<00:24:17.279> your<00:24:17.400> email<00:24:17.840> by 00:24:17.990 --> 00:24:18.000 align:start position:0% you connect it'll filter your email by 00:24:18.000 --> 00:24:22.669 align:start position:0% you connect it'll filter your email by that<00:24:18.159> email<00:24:18.760> query<00:24:19.760> yep<00:24:20.279> cool<00:24:20.559> good<00:24:20.960> question 00:24:22.669 --> 00:24:22.679 align:start position:0% that email query yep cool good question 00:24:22.679 --> 00:24:27.350 align:start position:0% that email query yep cool good question um<00:24:23.679> okay<00:24:24.559> uh<00:24:24.720> yeah 00:24:27.350 --> 00:24:27.360 align:start position:0% 00:24:27.360 --> 00:24:29.710 align:start position:0% question<00:24:28.399> the<00:24:28.679> BL<00:24:28.960> blueprint<00:24:29.360> the<00:24:29.440> submit 00:24:29.710 --> 00:24:29.720 align:start position:0% question the BL blueprint the submit 00:24:29.720 --> 00:24:31.630 align:start position:0% question the BL blueprint the submit blueprint<00:24:30.039> button<00:24:30.240> is<00:24:30.440> what<00:24:30.679> disabled<00:24:31.520> so 00:24:31.630 --> 00:24:31.640 align:start position:0% blueprint button is what disabled so 00:24:31.640 --> 00:24:33.389 align:start position:0% blueprint button is what disabled so that<00:24:31.760> means<00:24:31.960> you've<00:24:32.120> missed<00:24:32.399> some<00:24:32.600> field<00:24:33.200> so 00:24:33.389 --> 00:24:33.399 align:start position:0% that means you've missed some field so 00:24:33.399 --> 00:24:34.630 align:start position:0% that means you've missed some field so try<00:24:33.640> going<00:24:33.840> through<00:24:34.039> all<00:24:34.120> the<00:24:34.200> fields<00:24:34.520> and 00:24:34.630 --> 00:24:34.640 align:start position:0% try going through all the fields and 00:24:34.640 --> 00:24:36.350 align:start position:0% try going through all the fields and seeing<00:24:34.880> did<00:24:35.000> I<00:24:35.120> fill<00:24:35.480> a<00:24:35.600> field<00:24:35.880> in<00:24:36.039> like<00:24:36.159> did<00:24:36.240> I 00:24:36.350 --> 00:24:36.360 align:start position:0% seeing did I fill a field in like did I 00:24:36.360 --> 00:24:37.909 align:start position:0% seeing did I fill a field in like did I feel<00:24:36.520> something<00:24:36.679> in<00:24:36.760> the<00:24:36.840> Rex<00:24:37.240> did<00:24:37.320> I<00:24:37.440> feel 00:24:37.909 --> 00:24:37.919 align:start position:0% feel something in the Rex did I feel 00:24:37.919 --> 00:24:39.070 align:start position:0% feel something in the Rex did I feel like<00:24:38.039> there's<00:24:38.200> probably<00:24:38.480> some<00:24:38.640> validation 00:24:39.070 --> 00:24:39.080 align:start position:0% like there's probably some validation 00:24:39.080 --> 00:24:40.510 align:start position:0% like there's probably some validation that's<00:24:39.240> failing<00:24:39.559> or<00:24:39.880> you<00:24:39.960> didn't<00:24:40.200> run<00:24:40.399> the 00:24:40.510 --> 00:24:40.520 align:start position:0% that's failing or you didn't run the 00:24:40.520 --> 00:24:45.310 align:start position:0% that's failing or you didn't run the tests 00:24:45.310 --> 00:24:45.320 align:start position:0% 00:24:45.320 --> 00:24:49.430 align:start position:0% yeah<00:24:46.320> you're<00:24:46.480> getting<00:24:46.720> a 00:24:49.430 --> 00:24:49.440 align:start position:0% 00:24:49.440 --> 00:24:53.029 align:start position:0% yellow<00:24:50.600> um<00:24:51.600> yeah<00:24:51.760> so<00:24:51.960> so<00:24:52.440> it<00:24:52.559> took<00:24:52.679> you<00:24:52.799> back<00:24:52.919> to 00:24:53.029 --> 00:24:53.039 align:start position:0% yellow um yeah so so it took you back to 00:24:53.039 --> 00:24:55.870 align:start position:0% yellow um yeah so so it took you back to the<00:24:53.159> main<00:24:53.399> page<00:24:53.880> now<00:24:54.880> or<00:24:55.120> wait<00:24:55.240> so<00:24:55.360> so<00:24:55.520> sorry 00:24:55.870 --> 00:24:55.880 align:start position:0% the main page now or wait so so sorry 00:24:55.880 --> 00:25:03.590 align:start position:0% the main page now or wait so so sorry what<00:24:56.000> exactly<00:24:56.320> did<00:24:56.399> you<00:24:56.559> click 00:25:03.590 --> 00:25:03.600 align:start position:0% 00:25:03.600 --> 00:25:06.029 align:start position:0% uh<00:25:04.080> which<00:25:04.279> button<00:25:04.799> one<00:25:05.000> one<00:25:05.120> of 00:25:06.029 --> 00:25:06.039 align:start position:0% uh which button one one of 00:25:06.039 --> 00:25:08.909 align:start position:0% uh which button one one of these 00:25:08.909 --> 00:25:08.919 align:start position:0% these 00:25:08.919 --> 00:25:11.669 align:start position:0% these generate<00:25:09.919> oh<00:25:10.120> yes<00:25:10.360> yeah<00:25:10.559> sorry<00:25:11.039> so<00:25:11.279> so<00:25:11.440> I<00:25:11.520> think 00:25:11.669 --> 00:25:11.679 align:start position:0% generate oh yes yeah sorry so so I think 00:25:11.679 --> 00:25:13.310 align:start position:0% generate oh yes yeah sorry so so I think the<00:25:11.840> AI<00:25:12.200> is<00:25:12.360> probably<00:25:12.600> getting<00:25:12.799> rate<00:25:12.960> limited 00:25:13.310 --> 00:25:13.320 align:start position:0% the AI is probably getting rate limited 00:25:13.320 --> 00:25:14.750 align:start position:0% the AI is probably getting rate limited right<00:25:13.440> now<00:25:13.600> because<00:25:13.760> everybody's<00:25:14.080> quaring<00:25:14.480> it 00:25:14.750 --> 00:25:14.760 align:start position:0% right now because everybody's quaring it 00:25:14.760 --> 00:25:16.389 align:start position:0% right now because everybody's quaring it so<00:25:14.880> I'd<00:25:15.039> recommend<00:25:15.360> using<00:25:15.520> the<00:25:15.600> chat<00:25:15.799> gbt<00:25:16.200> bot 00:25:16.389 --> 00:25:16.399 align:start position:0% so I'd recommend using the chat gbt bot 00:25:16.399 --> 00:25:18.789 align:start position:0% so I'd recommend using the chat gbt bot in<00:25:16.520> the<00:25:16.640> top<00:25:16.799> right<00:25:17.000> instead 00:25:18.789 --> 00:25:18.799 align:start position:0% in the top right instead 00:25:18.799 --> 00:25:21.830 align:start position:0% in the top right instead yeah 00:25:21.830 --> 00:25:21.840 align:start position:0% 00:25:21.840 --> 00:25:30.310 align:start position:0% yeah<00:25:22.840> failed<00:25:23.320> test<00:25:23.679> what<00:25:23.840> what<00:25:23.919> did<00:25:24.039> it<00:25:24.200> say 00:25:30.310 --> 00:25:30.320 align:start position:0% 00:25:30.320 --> 00:25:34.070 align:start position:0% um<00:25:30.600> yeah<00:25:30.880> probably<00:25:31.600> the<00:25:31.799> Rex<00:25:32.360> format<00:25:32.960> wasn't 00:25:34.070 --> 00:25:34.080 align:start position:0% um yeah probably the Rex format wasn't 00:25:34.080 --> 00:25:36.710 align:start position:0% um yeah probably the Rex format wasn't exactly<00:25:35.080> correct<00:25:35.440> let<00:25:35.559> me<00:25:35.720> pull<00:25:35.919> up<00:25:36.440> for<00:25:36.600> you 00:25:36.710 --> 00:25:36.720 align:start position:0% exactly correct let me pull up for you 00:25:36.720 --> 00:25:38.389 align:start position:0% exactly correct let me pull up for you guys<00:25:36.919> what<00:25:37.080> exactly<00:25:37.399> the<00:25:37.480> Rex<00:25:37.880> format<00:25:38.200> should 00:25:38.389 --> 00:25:38.399 align:start position:0% guys what exactly the Rex format should 00:25:38.399 --> 00:25:45.909 align:start position:0% guys what exactly the Rex format should look<00:25:38.960> like 00:25:45.909 --> 00:25:45.919 align:start position:0% 00:25:45.919 --> 00:25:48.870 align:start position:0% um<00:25:46.919> yeah<00:25:47.520> um<00:25:47.679> let<00:25:47.799> me<00:25:48.080> just<00:25:48.360> pull<00:25:48.559> up<00:25:48.679> an 00:25:48.870 --> 00:25:48.880 align:start position:0% um yeah um let me just pull up an 00:25:48.880 --> 00:26:09.830 align:start position:0% um yeah um let me just pull up an example<00:25:49.640> kind<00:25:49.799> of<00:25:50.000> Parts<00:25:50.799> there<00:25:51.799> um 00:26:09.830 --> 00:26:09.840 align:start position:0% 00:26:09.840 --> 00:26:12.470 align:start position:0% um<00:26:10.840> right<00:26:11.039> maybe<00:26:11.480> one<00:26:11.640> thing<00:26:11.799> we<00:26:11.919> can<00:26:12.080> do<00:26:12.240> is 00:26:12.470 --> 00:26:12.480 align:start position:0% um right maybe one thing we can do is 00:26:12.480 --> 00:26:15.230 align:start position:0% um right maybe one thing we can do is provide<00:26:13.039> what<00:26:13.360> exactly<00:26:14.360> those<00:26:14.520> Rexes<00:26:15.039> look 00:26:15.230 --> 00:26:15.240 align:start position:0% provide what exactly those Rexes look 00:26:15.240 --> 00:26:16.990 align:start position:0% provide what exactly those Rexes look like<00:26:15.360> to<00:26:15.480> help<00:26:15.720> people<00:26:15.960> make<00:26:16.120> the 00:26:16.990 --> 00:26:17.000 align:start position:0% like to help people make the 00:26:17.000 --> 00:26:19.710 align:start position:0% like to help people make the definitions<00:26:18.000> um<00:26:18.840> okay<00:26:19.000> let<00:26:19.120> me<00:26:19.360> let<00:26:19.440> me<00:26:19.559> pull 00:26:19.710 --> 00:26:19.720 align:start position:0% definitions um okay let me let me pull 00:26:19.720 --> 00:26:22.070 align:start position:0% definitions um okay let me let me pull up<00:26:19.840> an<00:26:20.000> example<00:26:20.399> pattern<00:26:20.720> that<00:26:20.840> I<00:26:20.960> know<00:26:21.159> should 00:26:22.070 --> 00:26:22.080 align:start position:0% up an example pattern that I know should 00:26:22.080 --> 00:26:24.149 align:start position:0% up an example pattern that I know should compile 00:26:24.149 --> 00:26:24.159 align:start position:0% compile 00:26:24.159 --> 00:26:43.630 align:start position:0% compile um<00:26:25.159> probably<00:26:25.679> this<00:26:25.840> one 00:26:43.630 --> 00:26:43.640 align:start position:0% 00:26:43.640 --> 00:26:47.750 align:start position:0% okay<00:26:44.720> um<00:26:45.720> it's<00:26:45.960> like<00:26:46.080> a<00:26:46.320> bit<00:26:46.760> hard<00:26:47.000> to<00:26:47.240> parse<00:26:47.640> I 00:26:47.750 --> 00:26:47.760 align:start position:0% okay um it's like a bit hard to parse I 00:26:47.760 --> 00:26:49.190 align:start position:0% okay um it's like a bit hard to parse I guess<00:26:48.039> let 00:26:49.190 --> 00:26:49.200 align:start position:0% guess let 00:26:49.200 --> 00:26:50.240 align:start position:0% guess let me 00:26:50.240 --> 00:26:50.250 align:start position:0% me 00:26:50.250 --> 00:26:51.549 align:start position:0% me [Music] 00:26:51.549 --> 00:26:51.559 align:start position:0% [Music] 00:26:51.559 --> 00:27:10.750 align:start position:0% [Music] um<00:26:52.559> try<00:26:52.799> to<00:26:53.080> put<00:26:53.240> this<00:26:53.360> in<00:26:53.520> like<00:26:53.640> a<00:26:53.799> paste<00:26:54.120> bin 00:27:10.750 --> 00:27:10.760 align:start position:0% 00:27:10.760 --> 00:27:13.590 align:start position:0% um<00:27:11.760> okay<00:27:12.080> uh<00:27:12.200> we'll<00:27:12.399> probably<00:27:12.600> switch<00:27:12.799> in<00:27:13.000> like 00:27:13.590 --> 00:27:13.600 align:start position:0% um okay uh we'll probably switch in like 00:27:13.600 --> 00:27:16.389 align:start position:0% um okay uh we'll probably switch in like 20<00:27:13.960> 30<00:27:14.240> minutes<00:27:14.480> 20<00:27:14.679> minutes<00:27:14.880> or<00:27:15.039> so<00:27:16.000> um<00:27:16.240> are 00:27:16.389 --> 00:27:16.399 align:start position:0% 20 30 minutes 20 minutes or so um are 00:27:16.399 --> 00:27:21.029 align:start position:0% 20 30 minutes 20 minutes or so um are the<00:27:16.559> dots<00:27:16.840> updated<00:27:17.760> the<00:27:17.880> dot<00:27:18.200> Source 00:27:21.029 --> 00:27:21.039 align:start position:0% 00:27:21.039 --> 00:27:23.870 align:start position:0% okay<00:27:22.039> okay<00:27:22.440> right<00:27:22.640> so<00:27:23.080> this<00:27:23.159> is<00:27:23.399> kind<00:27:23.559> of<00:27:23.760> what 00:27:23.870 --> 00:27:23.880 align:start position:0% okay okay right so this is kind of what 00:27:23.880 --> 00:27:25.590 align:start position:0% okay okay right so this is kind of what you<00:27:24.000> might<00:27:24.240> imagine<00:27:25.039> I<00:27:25.120> think<00:27:25.279> some<00:27:25.440> folks 00:27:25.590 --> 00:27:25.600 align:start position:0% you might imagine I think some folks 00:27:25.600 --> 00:27:27.430 align:start position:0% you might imagine I think some folks were<00:27:25.720> having<00:27:25.880> trouble<00:27:26.080> with<00:27:26.159> the<00:27:26.279> Rex<00:27:27.200> this<00:27:27.279> is 00:27:27.430 --> 00:27:27.440 align:start position:0% were having trouble with the Rex this is 00:27:27.440 --> 00:27:28.990 align:start position:0% were having trouble with the Rex this is kind<00:27:27.559> of<00:27:27.720> how<00:27:27.799> you<00:27:27.919> need<00:27:28.000> to<00:27:28.240> structure<00:27:28.799> what 00:27:28.990 --> 00:27:29.000 align:start position:0% kind of how you need to structure what 00:27:29.000 --> 00:27:32.310 align:start position:0% kind of how you need to structure what goes<00:27:29.279> into<00:27:29.840> to<00:27:30.120> this<00:27:30.360> like<00:27:30.720> Parts<00:27:31.039> Json<00:27:31.559> field 00:27:32.310 --> 00:27:32.320 align:start position:0% goes into to this like Parts Json field 00:27:32.320 --> 00:27:34.190 align:start position:0% goes into to this like Parts Json field is<00:27:32.440> you<00:27:32.559> need<00:27:32.640> to<00:27:32.840> have<00:27:33.120> like<00:27:33.760> this<00:27:33.960> kind<00:27:34.080> of 00:27:34.190 --> 00:27:34.200 align:start position:0% is you need to have like this kind of 00:27:34.200 --> 00:27:35.430 align:start position:0% is you need to have like this kind of thing<00:27:34.360> where<00:27:34.440> you<00:27:34.520> have<00:27:34.679> is<00:27:34.880> public<00:27:35.279> and<00:27:35.360> then 00:27:35.430 --> 00:27:35.440 align:start position:0% thing where you have is public and then 00:27:35.440 --> 00:27:38.549 align:start position:0% thing where you have is public and then a<00:27:35.559> Rex<00:27:36.000> definition<00:27:37.000> is<00:27:37.200> public<00:27:37.520> re<00:27:37.880> definition 00:27:38.549 --> 00:27:38.559 align:start position:0% a Rex definition is public re definition 00:27:38.559 --> 00:27:40.070 align:start position:0% a Rex definition is public re definition in<00:27:38.679> this<00:27:38.840> case<00:27:39.039> I'm<00:27:39.200> extracting<00:27:39.640> some<00:27:39.840> value 00:27:40.070 --> 00:27:40.080 align:start position:0% in this case I'm extracting some value 00:27:40.080 --> 00:27:42.149 align:start position:0% in this case I'm extracting some value out<00:27:40.159> of<00:27:40.279> the<00:27:40.440> subject<00:27:41.360> um<00:27:41.559> maybe<00:27:41.799> to<00:27:41.919> make<00:27:42.000> it 00:27:42.149 --> 00:27:42.159 align:start position:0% out of the subject um maybe to make it 00:27:42.159 --> 00:27:44.389 align:start position:0% out of the subject um maybe to make it concrete<00:27:42.480> for<00:27:42.559> the<00:27:42.640> Google<00:27:42.880> Alerts<00:27:43.240> email<00:27:44.120> um 00:27:44.389 --> 00:27:44.399 align:start position:0% concrete for the Google Alerts email um 00:27:44.399 --> 00:27:46.470 align:start position:0% concrete for the Google Alerts email um we<00:27:44.480> can<00:27:44.640> try<00:27:44.840> to<00:27:45.000> do<00:27:45.760> this<00:27:45.919> as<00:27:46.000> well<00:27:46.159> where<00:27:46.279> we 00:27:46.470 --> 00:27:46.480 align:start position:0% we can try to do this as well where we 00:27:46.480 --> 00:27:48.230 align:start position:0% we can try to do this as well where we take<00:27:46.760> okay<00:27:46.880> we're<00:27:47.000> going<00:27:47.120> to<00:27:47.240> see<00:27:47.919> Google 00:27:48.230 --> 00:27:48.240 align:start position:0% take okay we're going to see Google 00:27:48.240 --> 00:27:50.029 align:start position:0% take okay we're going to see Google alert<00:27:49.120> um<00:27:49.200> so<00:27:49.320> I'm<00:27:49.399> going<00:27:49.480> to<00:27:49.559> say<00:27:49.679> you<00:27:49.760> know<00:27:49.919> in 00:27:50.029 --> 00:27:50.039 align:start position:0% alert um so I'm going to say you know in 00:27:50.039 --> 00:27:52.310 align:start position:0% alert um so I'm going to say you know in the<00:27:50.240> subject<00:27:50.720> so<00:27:51.559> before<00:27:51.760> the<00:27:51.880> field<00:27:52.159> you're 00:27:52.310 --> 00:27:52.320 align:start position:0% the subject so before the field you're 00:27:52.320 --> 00:27:54.669 align:start position:0% the subject so before the field you're extracting<00:27:53.200> you'll<00:27:53.440> have<00:27:53.640> this<00:27:53.799> little<00:27:54.159> like 00:27:54.669 --> 00:27:54.679 align:start position:0% extracting you'll have this little like 00:27:54.679 --> 00:27:57.269 align:start position:0% extracting you'll have this little like um<00:27:55.320> thing<00:27:55.440> you<00:27:55.559> have<00:27:55.640> to<00:27:55.799> put<00:27:56.039> of<00:27:56.640> the<00:27:56.760> delimer 00:27:57.269 --> 00:27:57.279 align:start position:0% um thing you have to put of the delimer 00:27:57.279 --> 00:27:59.470 align:start position:0% um thing you have to put of the delimer before<00:27:57.559> the<00:27:57.760> actual<00:27:58.360> value<00:27:58.720> so<00:27:59.000> here<00:27:59.120> I'm 00:27:59.470 --> 00:27:59.480 align:start position:0% before the actual value so here I'm 00:27:59.480 --> 00:28:00.630 align:start position:0% before the actual value so here I'm something<00:27:59.640> from<00:27:59.720> the<00:27:59.840> subject<00:28:00.320> you<00:28:00.440> might 00:28:00.630 --> 00:28:00.640 align:start position:0% something from the subject you might 00:28:00.640 --> 00:28:01.830 align:start position:0% something from the subject you might imagine<00:28:00.960> if<00:28:01.039> you're<00:28:01.240> extracting<00:28:01.640> something 00:28:01.830 --> 00:28:01.840 align:start position:0% imagine if you're extracting something 00:28:01.840 --> 00:28:03.310 align:start position:0% imagine if you're extracting something from<00:28:02.000> two<00:28:02.159> or<00:28:02.320> from<00:28:02.640> this<00:28:02.720> would<00:28:02.840> say<00:28:02.960> two<00:28:03.159> or 00:28:03.310 --> 00:28:03.320 align:start position:0% from two or from this would say two or 00:28:03.320 --> 00:28:05.310 align:start position:0% from two or from this would say two or from<00:28:04.320> um<00:28:04.480> and<00:28:04.559> then<00:28:04.640> you're<00:28:04.760> going<00:28:04.840> to<00:28:05.039> put<00:28:05.200> you 00:28:05.310 --> 00:28:05.320 align:start position:0% from um and then you're going to put you 00:28:05.320 --> 00:28:06.630 align:start position:0% from um and then you're going to put you know<00:28:05.960> I'm<00:28:06.039> going<00:28:06.159> to<00:28:06.240> see<00:28:06.360> this<00:28:06.440> in<00:28:06.519> the 00:28:06.630 --> 00:28:06.640 align:start position:0% know I'm going to see this in the 00:28:06.640 --> 00:28:08.509 align:start position:0% know I'm going to see this in the subject<00:28:07.000> and<00:28:07.080> then<00:28:07.240> I'm<00:28:07.360> going<00:28:07.519> to<00:28:07.640> see<00:28:08.279> any 00:28:08.509 --> 00:28:08.519 align:start position:0% subject and then I'm going to see any 00:28:08.519 --> 00:28:12.509 align:start position:0% subject and then I'm going to see any value<00:28:08.960> except<00:28:09.840> the<00:28:10.200> the<00:28:10.399> SLR<00:28:11.399> and<00:28:11.559> then<00:28:12.000> um<00:28:12.399> the 00:28:12.509 --> 00:28:12.519 align:start position:0% value except the the SLR and then um the 00:28:12.519 --> 00:28:14.470 align:start position:0% value except the the SLR and then um the end<00:28:12.679> of<00:28:12.840> it<00:28:13.080> and<00:28:13.200> so<00:28:13.679> mostly<00:28:14.159> what<00:28:14.240> you'll<00:28:14.399> be 00:28:14.470 --> 00:28:14.480 align:start position:0% end of it and so mostly what you'll be 00:28:14.480 --> 00:28:15.710 align:start position:0% end of it and so mostly what you'll be doing<00:28:14.679> is<00:28:14.799> editing<00:28:15.200> this<00:28:15.320> value<00:28:15.559> in<00:28:15.640> the 00:28:15.710 --> 00:28:15.720 align:start position:0% doing is editing this value in the 00:28:15.720 --> 00:28:17.789 align:start position:0% doing is editing this value in the middle<00:28:16.360> and<00:28:16.519> editing<00:28:17.120> this<00:28:17.279> value<00:28:17.559> whether<00:28:17.679> it 00:28:17.789 --> 00:28:17.799 align:start position:0% middle and editing this value whether it 00:28:17.799 --> 00:28:20.310 align:start position:0% middle and editing this value whether it says<00:28:18.000> subject<00:28:18.320> to<00:28:18.480> or<00:28:18.640> from<00:28:19.640> um<00:28:20.080> and<00:28:20.159> your 00:28:20.310 --> 00:28:20.320 align:start position:0% says subject to or from um and your 00:28:20.320 --> 00:28:21.549 align:start position:0% says subject to or from um and your casing<00:28:20.640> has<00:28:20.760> to<00:28:20.840> be<00:28:20.960> correct<00:28:21.200> like<00:28:21.279> it<00:28:21.399> has<00:28:21.480> to 00:28:21.549 --> 00:28:21.559 align:start position:0% casing has to be correct like it has to 00:28:21.559 --> 00:28:23.990 align:start position:0% casing has to be correct like it has to be<00:28:21.720> subject<00:28:22.159> to<00:28:22.399> from<00:28:22.760> lowercase<00:28:23.720> and<00:28:23.840> then 00:28:23.990 --> 00:28:24.000 align:start position:0% be subject to from lowercase and then 00:28:24.000 --> 00:28:25.509 align:start position:0% be subject to from lowercase and then here<00:28:24.159> you<00:28:24.320> put<00:28:24.519> in<00:28:24.760> like<00:28:24.919> what<00:28:25.080> exactly<00:28:25.440> you 00:28:25.509 --> 00:28:25.519 align:start position:0% here you put in like what exactly you 00:28:25.519 --> 00:28:28.110 align:start position:0% here you put in like what exactly you want<00:28:25.720> to<00:28:25.880> parse<00:28:26.640> and<00:28:26.799> then<00:28:27.080> probably<00:28:27.760> anything 00:28:28.110 --> 00:28:28.120 align:start position:0% want to parse and then probably anything 00:28:28.120 --> 00:28:30.549 align:start position:0% want to parse and then probably anything thing<00:28:28.279> until<00:28:28.480> the<00:28:28.600> end<00:28:28.960> and<00:28:29.120> then<00:28:29.840> the<00:28:29.960> end 00:28:30.549 --> 00:28:30.559 align:start position:0% thing until the end and then the end 00:28:30.559 --> 00:28:32.509 align:start position:0% thing until the end and then the end limiter 00:28:32.509 --> 00:28:32.519 align:start position:0% limiter 00:28:32.519 --> 00:28:36.110 align:start position:0% limiter um<00:28:33.519> okay<00:28:34.440> I<00:28:34.559> think<00:28:35.200> maybe<00:28:35.480> we'll<00:28:35.760> we'll<00:28:35.919> keep 00:28:36.110 --> 00:28:36.120 align:start position:0% um okay I think maybe we'll we'll keep 00:28:36.120 --> 00:28:37.389 align:start position:0% um okay I think maybe we'll we'll keep going<00:28:36.360> around<00:28:36.640> and<00:28:36.880> and<00:28:37.039> seeing<00:28:37.279> what 00:28:37.389 --> 00:28:37.399 align:start position:0% going around and and seeing what 00:28:37.399 --> 00:28:45.430 align:start position:0% going around and and seeing what people's<00:28:37.720> questions<00:28:38.039> are<00:28:38.919> uh 00:28:45.430 --> 00:28:45.440 align:start position:0% 00:28:45.440 --> 00:28:49.230 align:start position:0% yeah<00:28:46.440> uh<00:28:47.120> so<00:28:47.480> so<00:28:48.200> uh<00:28:48.360> you<00:28:48.440> mean<00:28:48.720> like<00:28:48.880> in<00:28:49.080> this 00:28:49.230 --> 00:28:49.240 align:start position:0% yeah uh so so uh you mean like in this 00:28:49.240 --> 00:28:53.269 align:start position:0% yeah uh so so uh you mean like in this Parts<00:28:49.519> Json 00:28:53.269 --> 00:28:53.279 align:start position:0% 00:28:53.279 --> 00:28:55.950 align:start position:0% or<00:28:54.279> you<00:28:54.440> could 00:28:55.950 --> 00:28:55.960 align:start position:0% or you could 00:28:55.960 --> 00:28:58.149 align:start position:0% or you could yeah<00:28:56.960> right<00:28:57.120> yeah<00:28:57.240> so<00:28:57.399> exactly<00:28:57.640> so<00:28:57.720> youd<00:28:57.880> add 00:28:58.149 --> 00:28:58.159 align:start position:0% yeah right yeah so exactly so youd add 00:28:58.159 --> 00:28:59.389 align:start position:0% yeah right yeah so exactly so youd add Valu<00:28:58.360> to<00:28:58.480> extract<00:28:58.760> and<00:28:58.799> you'd<00:28:58.960> put<00:28:59.080> a<00:28:59.159> second 00:28:59.389 --> 00:28:59.399 align:start position:0% Valu to extract and you'd put a second 00:28:59.399 --> 00:29:02.789 align:start position:0% Valu to extract and you'd put a second Rex<00:28:59.720> and<00:28:59.840> they'd<00:29:00.039> both<00:29:00.200> be<00:29:00.640> constrained<00:29:01.799> body 00:29:02.789 --> 00:29:02.799 align:start position:0% Rex and they'd both be constrained body 00:29:02.799 --> 00:29:04.110 align:start position:0% Rex and they'd both be constrained body it's<00:29:02.960> all<00:29:03.080> in<00:29:03.200> the<00:29:03.279> body<00:29:03.480> you<00:29:03.600> could<00:29:03.760> just<00:29:03.919> put 00:29:04.110 --> 00:29:04.120 align:start position:0% it's all in the body you could just put 00:29:04.120 --> 00:29:06.430 align:start position:0% it's all in the body you could just put one<00:29:04.919> um<00:29:05.120> it's<00:29:05.279> more<00:29:05.480> about<00:29:05.679> like<00:29:05.840> Clarity<00:29:06.279> of 00:29:06.430 --> 00:29:06.440 align:start position:0% one um it's more about like Clarity of 00:29:06.440 --> 00:29:08.110 align:start position:0% one um it's more about like Clarity of thought<00:29:06.640> to<00:29:06.760> make<00:29:06.880> sure<00:29:07.120> that<00:29:07.320> that<00:29:07.840> that<00:29:08.000> kind 00:29:08.110 --> 00:29:08.120 align:start position:0% thought to make sure that that that kind 00:29:08.120 --> 00:29:10.710 align:start position:0% thought to make sure that that that kind of<00:29:08.840> uh<00:29:09.559> like<00:29:09.960> you<00:29:10.080> feel<00:29:10.279> like<00:29:10.480> you're<00:29:10.600> not 00:29:10.710 --> 00:29:10.720 align:start position:0% of uh like you feel like you're not 00:29:10.720 --> 00:29:12.909 align:start position:0% of uh like you feel like you're not making<00:29:10.919> it<00:29:11.039> too<00:29:11.200> complicated<00:29:11.640> in<00:29:11.720> the<00:29:11.880> body<00:29:12.720> um 00:29:12.909 --> 00:29:12.919 align:start position:0% making it too complicated in the body um 00:29:12.919 --> 00:29:14.110 align:start position:0% making it too complicated in the body um if<00:29:13.000> you're<00:29:13.080> going<00:29:13.200> to<00:29:13.320> parse<00:29:13.519> in<00:29:13.640> the<00:29:13.720> body<00:29:13.960> by 00:29:14.110 --> 00:29:14.120 align:start position:0% if you're going to parse in the body by 00:29:14.120 --> 00:29:15.230 align:start position:0% if you're going to parse in the body by the<00:29:14.200> way<00:29:14.320> you<00:29:14.440> don't<00:29:14.600> need<00:29:14.799> something<00:29:15.080> that 00:29:15.230 --> 00:29:15.240 align:start position:0% the way you don't need something that 00:29:15.240 --> 00:29:17.389 align:start position:0% the way you don't need something that this<00:29:15.320> is<00:29:15.480> for<00:29:16.240> uh<00:29:16.360> things<00:29:16.519> in<00:29:16.600> the<00:29:16.720> header<00:29:17.200> or 00:29:17.389 --> 00:29:17.399 align:start position:0% this is for uh things in the header or 00:29:17.399 --> 00:29:18.350 align:start position:0% this is for uh things in the header or subject<00:29:17.679> if<00:29:17.760> you're<00:29:17.840> going<00:29:17.960> to<00:29:18.039> par<00:29:18.200> something 00:29:18.350 --> 00:29:18.360 align:start position:0% subject if you're going to par something 00:29:18.360 --> 00:29:19.669 align:start position:0% subject if you're going to par something in<00:29:18.440> the<00:29:18.519> body<00:29:18.720> maybe<00:29:18.919> let's<00:29:19.080> add<00:29:19.200> one<00:29:19.320> to<00:29:19.440> the 00:29:19.669 --> 00:29:19.679 align:start position:0% in the body maybe let's add one to the 00:29:19.679 --> 00:29:23.990 align:start position:0% in the body maybe let's add one to the body<00:29:20.760> um<00:29:21.760> alert<00:29:22.159> name<00:29:22.720> body<00:29:23.720> um<00:29:23.840> if<00:29:23.880> you're 00:29:23.990 --> 00:29:24.000 align:start position:0% body um alert name body um if you're 00:29:24.000 --> 00:29:24.990 align:start position:0% body um alert name body um if you're going<00:29:24.080> to<00:29:24.200> parse<00:29:24.399> in<00:29:24.480> the<00:29:24.600> body<00:29:24.799> you<00:29:24.880> can 00:29:24.990 --> 00:29:25.000 align:start position:0% going to parse in the body you can 00:29:25.000 --> 00:29:26.750 align:start position:0% going to parse in the body you can probably<00:29:25.360> just<00:29:25.480> directly<00:29:25.880> parse<00:29:26.600> what 00:29:26.750 --> 00:29:26.760 align:start position:0% probably just directly parse what 00:29:26.760 --> 00:29:28.990 align:start position:0% probably just directly parse what exactly<00:29:27.120> it<00:29:27.279> is<00:29:27.640> you<00:29:27.799> want<00:29:28.120> to<00:29:28.360> show<00:29:28.679> so<00:29:28.880> in 00:29:28.990 --> 00:29:29.000 align:start position:0% exactly it is you want to show so in 00:29:29.000 --> 00:29:30.320 align:start position:0% exactly it is you want to show so in this<00:29:29.279> case 00:29:30.320 --> 00:29:30.330 align:start position:0% this case 00:29:30.330 --> 00:29:36.149 align:start position:0% this case [Music] 00:29:36.149 --> 00:29:36.159 align:start position:0% 00:29:36.159 --> 00:29:39.389 align:start position:0% um<00:29:37.159> okay<00:29:37.440> so<00:29:38.360> in<00:29:38.480> this<00:29:38.640> case<00:29:38.840> maybe<00:29:39.039> I<00:29:39.120> want<00:29:39.240> to 00:29:39.389 --> 00:29:39.399 align:start position:0% um okay so in this case maybe I want to 00:29:39.399 --> 00:29:42.310 align:start position:0% um okay so in this case maybe I want to parse<00:29:39.679> out<00:29:39.919> I<00:29:40.000> see<00:29:40.279> this<00:29:40.399> in<00:29:40.519> the<00:29:41.000> body<00:29:42.000> um<00:29:42.200> what 00:29:42.310 --> 00:29:42.320 align:start position:0% parse out I see this in the body um what 00:29:42.320 --> 00:29:45.230 align:start position:0% parse out I see this in the body um what I'm<00:29:42.440> going<00:29:42.600> to<00:29:42.760> do<00:29:42.960> is<00:29:43.120> I'm<00:29:43.279> going<00:29:43.840> to<00:29:44.840> uh 00:29:45.230 --> 00:29:45.240 align:start position:0% I'm going to do is I'm going to uh 00:29:45.240 --> 00:29:48.710 align:start position:0% I'm going to do is I'm going to uh Define<00:29:46.240> okay<00:29:46.519> is<00:29:46.679> public<00:29:46.960> equals<00:29:47.559> false<00:29:48.559> uh 00:29:48.710 --> 00:29:48.720 align:start position:0% Define okay is public equals false uh 00:29:48.720 --> 00:29:52.470 align:start position:0% Define okay is public equals false uh okay<00:29:48.840> so<00:29:48.919> I'm<00:29:49.039> going<00:29:49.120> to<00:29:49.240> put<00:29:49.440> up<00:29:50.000> here<00:29:51.320> like 00:29:52.470 --> 00:29:52.480 align:start position:0% okay so I'm going to put up here like 00:29:52.480 --> 00:29:56.149 align:start position:0% okay so I'm going to put up here like subject<00:29:53.480> Parts<00:29:53.919> Json<00:29:54.919> I'm<00:29:55.039> going<00:29:55.120> to<00:29:55.279> hit<00:29:55.559> here 00:29:56.149 --> 00:29:56.159 align:start position:0% subject Parts Json I'm going to hit here 00:29:56.159 --> 00:30:12.470 align:start position:0% subject Parts Json I'm going to hit here body<00:29:56.919> parts<00:29:57.320> Json<00:29:58.480> Okay<00:29:58.799> cool<00:29:59.480> so 00:30:12.470 --> 00:30:12.480 align:start position:0% 00:30:12.480 --> 00:30:18.230 align:start position:0% um 00:30:18.230 --> 00:30:18.240 align:start position:0% 00:30:18.240 --> 00:30:20.430 align:start position:0% um<00:30:19.240> so<00:30:19.360> if<00:30:19.440> you're<00:30:19.519> going<00:30:19.640> to<00:30:19.720> do<00:30:19.840> body<00:30:20.039> parsing 00:30:20.430 --> 00:30:20.440 align:start position:0% um so if you're going to do body parsing 00:30:20.440 --> 00:30:22.389 align:start position:0% um so if you're going to do body parsing you<00:30:20.519> can<00:30:20.720> just<00:30:20.880> say<00:30:21.480> this<00:30:21.600> is<00:30:21.760> the<00:30:22.000> concrete 00:30:22.389 --> 00:30:22.399 align:start position:0% you can just say this is the concrete 00:30:22.399 --> 00:30:24.350 align:start position:0% you can just say this is the concrete thing<00:30:22.600> that<00:30:22.720> I'm<00:30:22.880> going<00:30:23.000> to<00:30:23.159> see<00:30:23.480> in<00:30:23.600> the<00:30:23.760> body 00:30:24.350 --> 00:30:24.360 align:start position:0% thing that I'm going to see in the body 00:30:24.360 --> 00:30:25.710 align:start position:0% thing that I'm going to see in the body and<00:30:24.480> then<00:30:24.600> I'm<00:30:24.720> going<00:30:24.880> to<00:30:25.039> extract<00:30:25.399> out 00:30:25.710 --> 00:30:25.720 align:start position:0% and then I'm going to extract out 00:30:25.720 --> 00:30:27.630 align:start position:0% and then I'm going to extract out everything<00:30:26.200> in<00:30:26.320> this<00:30:26.480> case<00:30:26.760> except<00:30:27.000> a<00:30:27.159> quote 00:30:27.630 --> 00:30:27.640 align:start position:0% everything in this case except a quote 00:30:27.640 --> 00:30:29.549 align:start position:0% everything in this case except a quote after<00:30:28.120> that<00:30:28.600> and<00:30:28.840> this<00:30:28.919> is<00:30:29.080> what's<00:30:29.279> going<00:30:29.440> to 00:30:29.549 --> 00:30:29.559 align:start position:0% after that and this is what's going to 00:30:29.559 --> 00:30:31.789 align:start position:0% after that and this is what's going to be<00:30:29.720> revealed<00:30:30.200> and<00:30:30.320> so<00:30:31.039> you<00:30:31.159> know<00:30:31.480> hopefully 00:30:31.789 --> 00:30:31.799 align:start position:0% be revealed and so you know hopefully 00:30:31.799 --> 00:30:33.389 align:start position:0% be revealed and so you know hopefully these<00:30:31.960> subject<00:30:32.240> and<00:30:32.399> body<00:30:32.559> parts<00:30:32.799> Json<00:30:33.200> help 00:30:33.389 --> 00:30:33.399 align:start position:0% these subject and body parts Json help 00:30:33.399 --> 00:30:35.549 align:start position:0% these subject and body parts Json help you<00:30:33.840> understand<00:30:34.240> like<00:30:34.720> if<00:30:34.840> I<00:30:34.960> want<00:30:35.080> to<00:30:35.200> par 00:30:35.549 --> 00:30:35.559 align:start position:0% you understand like if I want to par 00:30:35.559 --> 00:30:37.149 align:start position:0% you understand like if I want to par that<00:30:35.679> specific<00:30:36.080> value<00:30:36.399> from<00:30:36.559> my<00:30:36.679> subject<00:30:36.960> or 00:30:37.149 --> 00:30:37.159 align:start position:0% that specific value from my subject or 00:30:37.159 --> 00:30:39.470 align:start position:0% that specific value from my subject or body<00:30:37.399> how<00:30:37.600> exactly<00:30:37.880> I<00:30:38.000> need<00:30:38.120> to<00:30:38.279> do 00:30:39.470 --> 00:30:39.480 align:start position:0% body how exactly I need to do 00:30:39.480 --> 00:31:22.390 align:start position:0% body how exactly I need to do it<00:30:40.480> yeah 00:31:22.390 --> 00:31:22.400 align:start position:0% 00:31:22.400 --> 00:31:26.909 align:start position:0% [Music] 00:31:26.909 --> 00:31:26.919 align:start position:0% [Music] 00:31:26.919 --> 00:31:33.980 align:start position:0% [Music] Poss<00:31:27.919> for 00:31:33.980 --> 00:31:33.990 align:start position:0% 00:31:33.990 --> 00:31:56.390 align:start position:0% [Music] 00:31:56.390 --> 00:31:56.400 align:start position:0% 00:31:56.400 --> 00:32:04.530 align:start position:0% [Music] 00:32:04.530 --> 00:32:04.540 align:start position:0% 00:32:04.540 --> 00:32:16.110 align:start position:0% [Music] 00:32:16.110 --> 00:32:16.120 align:start position:0% 00:32:16.120 --> 00:32:18.629 align:start position:0% yeah<00:32:16.399> so<00:32:17.080> okay<00:32:17.799> yeah<00:32:18.000> great<00:32:18.200> question<00:32:18.480> if<00:32:18.559> you 00:32:18.629 --> 00:32:18.639 align:start position:0% yeah so okay yeah great question if you 00:32:18.639 --> 00:32:21.190 align:start position:0% yeah so okay yeah great question if you want<00:32:18.760> to<00:32:18.880> see<00:32:19.200> like<00:32:19.679> example<00:32:20.360> attributes<00:32:20.919> from 00:32:21.190 --> 00:32:21.200 align:start position:0% want to see like example attributes from 00:32:21.200 --> 00:32:23.549 align:start position:0% want to see like example attributes from from<00:32:21.440> other<00:32:21.919> patterns<00:32:22.919> uh<00:32:23.039> you<00:32:23.120> can<00:32:23.279> go<00:32:23.399> into 00:32:23.549 --> 00:32:23.559 align:start position:0% from other patterns uh you can go into 00:32:23.559 --> 00:32:25.590 align:start position:0% from other patterns uh you can go into the<00:32:23.639> registry<00:32:24.039> you<00:32:24.120> can<00:32:24.240> say<00:32:24.519> oh<00:32:25.080> I'm<00:32:25.240> kind<00:32:25.399> of 00:32:25.590 --> 00:32:25.600 align:start position:0% the registry you can say oh I'm kind of 00:32:25.600 --> 00:32:28.629 align:start position:0% the registry you can say oh I'm kind of curious<00:32:26.320> how<00:32:26.559> they<00:32:26.720> built<00:32:27.720> uh<00:32:28.000> um<00:32:28.440> I<00:32:28.519> don't 00:32:28.629 --> 00:32:28.639 align:start position:0% curious how they built uh um I don't 00:32:28.639 --> 00:32:29.990 align:start position:0% curious how they built uh um I don't know<00:32:28.799> this<00:32:28.919> Luma<00:32:29.279> Devcon<00:32:29.679> one<00:32:29.799> you're<00:32:29.919> going 00:32:29.990 --> 00:32:30.000 align:start position:0% know this Luma Devcon one you're going 00:32:30.000 --> 00:32:31.549 align:start position:0% know this Luma Devcon one you're going to<00:32:30.120> click<00:32:30.320> this<00:32:30.480> little<00:32:30.720> hyperlink<00:32:31.240> button<00:32:31.480> in 00:32:31.549 --> 00:32:31.559 align:start position:0% to click this little hyperlink button in 00:32:31.559 --> 00:32:34.230 align:start position:0% to click this little hyperlink button in the<00:32:31.919> middle<00:32:32.919> um<00:32:33.440> and<00:32:33.559> this<00:32:33.639> will<00:32:33.799> take<00:32:33.960> you<00:32:34.080> to 00:32:34.230 --> 00:32:34.240 align:start position:0% the middle um and this will take you to 00:32:34.240 --> 00:32:37.070 align:start position:0% the middle um and this will take you to the<00:32:34.840> actual<00:32:35.840> uh 00:32:37.070 --> 00:32:37.080 align:start position:0% the actual uh 00:32:37.080 --> 00:32:40.590 align:start position:0% the actual uh pattern<00:32:38.080> and<00:32:38.159> you're<00:32:38.279> going<00:32:38.360> to<00:32:38.440> hit<00:32:38.600> view<00:32:38.840> all 00:32:40.590 --> 00:32:40.600 align:start position:0% pattern and you're going to hit view all 00:32:40.600 --> 00:32:42.590 align:start position:0% pattern and you're going to hit view all versions<00:32:41.600> and<00:32:41.799> then<00:32:42.039> you'll<00:32:42.200> see<00:32:42.399> in<00:32:42.480> the 00:32:42.590 --> 00:32:42.600 align:start position:0% versions and then you'll see in the 00:32:42.600 --> 00:32:45.269 align:start position:0% versions and then you'll see in the version<00:32:42.919> history<00:32:43.279> you<00:32:43.399> can<00:32:43.559> now<00:32:43.760> edit<00:32:44.120> the<00:32:44.240> old 00:32:45.269 --> 00:32:45.279 align:start position:0% version history you can now edit the old 00:32:45.279 --> 00:32:48.269 align:start position:0% version history you can now edit the old patterns<00:32:46.279> right<00:32:46.720> if<00:32:46.799> you<00:32:46.960> see 00:32:48.269 --> 00:32:48.279 align:start position:0% patterns right if you see 00:32:48.279 --> 00:32:50.590 align:start position:0% patterns right if you see that<00:32:49.279> um<00:32:49.399> so<00:32:49.559> I<00:32:49.600> can<00:32:49.760> go<00:32:49.880> in<00:32:49.960> and<00:32:50.120> I<00:32:50.200> can<00:32:50.320> edit 00:32:50.590 --> 00:32:50.600 align:start position:0% that um so I can go in and I can edit 00:32:50.600 --> 00:32:52.389 align:start position:0% that um so I can go in and I can edit and<00:32:50.720> I<00:32:50.799> can<00:32:50.960> view<00:32:51.279> what<00:32:51.480> exactly<00:32:51.880> that<00:32:52.039> pattern 00:32:52.389 --> 00:32:52.399 align:start position:0% and I can view what exactly that pattern 00:32:52.399 --> 00:32:53.669 align:start position:0% and I can view what exactly that pattern looked 00:32:53.669 --> 00:32:53.679 align:start position:0% looked 00:32:53.679 --> 00:32:55.789 align:start position:0% looked like<00:32:54.679> and<00:32:54.799> you<00:32:54.880> can<00:32:55.039> see<00:32:55.320> oh<00:32:55.480> this<00:32:55.600> person 00:32:55.789 --> 00:32:55.799 align:start position:0% like and you can see oh this person 00:32:55.799 --> 00:32:57.430 align:start position:0% like and you can see oh this person defined<00:32:56.039> an<00:32:56.120> email<00:32:56.399> body<00:32:56.639> and<00:32:56.799> put<00:32:57.039> this<00:32:57.200> stuff 00:32:57.430 --> 00:32:57.440 align:start position:0% defined an email body and put this stuff 00:32:57.440 --> 00:33:01.909 align:start position:0% defined an email body and put this stuff into<00:32:57.639> the<00:32:58.200> parser<00:32:59.200> yeah<00:33:00.200> um<00:33:00.399> so<00:33:00.840> you<00:33:01.000> know 00:33:01.909 --> 00:33:01.919 align:start position:0% into the parser yeah um so you know 00:33:01.919 --> 00:33:03.230 align:start position:0% into the parser yeah um so you know maybe<00:33:02.159> if<00:33:02.240> you<00:33:02.360> look<00:33:02.480> at<00:33:02.600> some<00:33:02.880> especially<00:33:03.159> the 00:33:03.230 --> 00:33:03.240 align:start position:0% maybe if you look at some especially the 00:33:03.240 --> 00:33:05.269 align:start position:0% maybe if you look at some especially the older<00:33:03.480> ones<00:33:03.679> that<00:33:03.799> are<00:33:04.080> compiled<00:33:04.960> these<00:33:05.080> are 00:33:05.269 --> 00:33:05.279 align:start position:0% older ones that are compiled these are 00:33:05.279 --> 00:33:06.590 align:start position:0% older ones that are compiled these are ones<00:33:05.519> that<00:33:05.639> we<00:33:05.840> kind<00:33:05.919> of<00:33:06.039> looked<00:33:06.200> at<00:33:06.320> in<00:33:06.399> made 00:33:06.590 --> 00:33:06.600 align:start position:0% ones that we kind of looked at in made 00:33:06.600 --> 00:33:08.190 align:start position:0% ones that we kind of looked at in made sure<00:33:06.760> they<00:33:06.840> look<00:33:07.080> good<00:33:07.320> and<00:33:07.440> so<00:33:07.919> you<00:33:08.039> know 00:33:08.190 --> 00:33:08.200 align:start position:0% sure they look good and so you know 00:33:08.200 --> 00:33:10.230 align:start position:0% sure they look good and so you know clicking<00:33:08.519> one<00:33:08.639> of<00:33:08.840> these<00:33:09.279> and<00:33:09.399> then<00:33:09.639> seeing 00:33:10.230 --> 00:33:10.240 align:start position:0% clicking one of these and then seeing 00:33:10.240 --> 00:33:15.389 align:start position:0% clicking one of these and then seeing okay<00:33:11.200> um<00:33:12.039> view<00:33:12.320> all<00:33:12.519> versions<00:33:13.399> and<00:33:13.559> then<00:33:14.399> edit 00:33:15.389 --> 00:33:15.399 align:start position:0% okay um view all versions and then edit 00:33:15.399 --> 00:33:17.110 align:start position:0% okay um view all versions and then edit uh<00:33:15.519> will<00:33:15.679> help<00:33:15.840> you<00:33:16.000> see<00:33:16.279> what<00:33:16.480> exactly<00:33:16.880> should 00:33:17.110 --> 00:33:17.120 align:start position:0% uh will help you see what exactly should 00:33:17.120 --> 00:33:18.789 align:start position:0% uh will help you see what exactly should that<00:33:17.240> pattern<00:33:17.559> look<00:33:17.799> like<00:33:18.320> and<00:33:18.440> you<00:33:18.519> can<00:33:18.679> kind 00:33:18.789 --> 00:33:18.799 align:start position:0% that pattern look like and you can kind 00:33:18.799 --> 00:33:20.870 align:start position:0% that pattern look like and you can kind of<00:33:18.919> use<00:33:19.120> this<00:33:19.240> to<00:33:19.399> help<00:33:20.200> understand<00:33:20.559> okay<00:33:20.760> what 00:33:20.870 --> 00:33:20.880 align:start position:0% of use this to help understand okay what 00:33:20.880 --> 00:33:22.230 align:start position:0% of use this to help understand okay what should<00:33:21.080> my<00:33:21.320> like<00:33:21.440> pattern<00:33:21.720> in<00:33:21.840> this<00:33:21.960> Parts 00:33:22.230 --> 00:33:22.240 align:start position:0% should my like pattern in this Parts 00:33:22.240 --> 00:33:25.549 align:start position:0% should my like pattern in this Parts Json<00:33:22.639> actually<00:33:22.840> look<00:33:23.120> like 00:33:25.549 --> 00:33:25.559 align:start position:0% Json actually look like 00:33:25.559 --> 00:33:36.029 align:start position:0% Json actually look like sweet<00:33:26.559> okay<00:33:26.799> yeah 00:33:36.029 --> 00:33:36.039 align:start position:0% 00:33:36.039 --> 00:33:52.590 align:start position:0% yeah 00:33:52.590 --> 00:33:52.600 align:start position:0% 00:33:52.600 --> 00:33:54.950 align:start position:0% yeah<00:33:53.600> yeah<00:33:54.039> yeah<00:33:54.159> it's<00:33:54.279> a<00:33:54.399> great<00:33:54.600> question<00:33:54.799> so 00:33:54.950 --> 00:33:54.960 align:start position:0% yeah yeah yeah it's a great question so 00:33:54.960 --> 00:33:56.470 align:start position:0% yeah yeah yeah it's a great question so what<00:33:55.039> is<00:33:55.159> the<00:33:55.240> developer<00:33:55.720> experience<00:33:56.120> of<00:33:56.320> like 00:33:56.470 --> 00:33:56.480 align:start position:0% what is the developer experience of like 00:33:56.480 --> 00:33:58.350 align:start position:0% what is the developer experience of like actually<00:33:56.720> making<00:33:56.960> sure<00:33:57.159> it's<00:33:57.320> working<00:33:58.159> in 00:33:58.350 --> 00:33:58.360 align:start position:0% actually making sure it's working in 00:33:58.360 --> 00:34:00.029 align:start position:0% actually making sure it's working in generated<00:33:58.880> output<00:33:59.279> you<00:33:59.360> should<00:33:59.600> see<00:33:59.840> if<00:33:59.919> you 00:34:00.029 --> 00:34:00.039 align:start position:0% generated output you should see if you 00:34:00.039 --> 00:34:01.629 align:start position:0% generated output you should see if you did<00:34:00.159> it<00:34:00.279> correctly<00:34:00.720> like<00:34:00.880> the<00:34:01.039> actual<00:34:01.320> output 00:34:01.629 --> 00:34:01.639 align:start position:0% did it correctly like the actual output 00:34:01.639 --> 00:34:02.789 align:start position:0% did it correctly like the actual output that<00:34:01.760> will<00:34:01.880> be<00:34:02.000> generated<00:34:02.399> and<00:34:02.480> so<00:34:02.559> if<00:34:02.600> you<00:34:02.679> see 00:34:02.789 --> 00:34:02.799 align:start position:0% that will be generated and so if you see 00:34:02.799 --> 00:34:04.509 align:start position:0% that will be generated and so if you see an<00:34:02.919> error<00:34:03.159> like<00:34:03.279> this<00:34:03.480> oh<00:34:03.880> failed<00:34:04.159> to<00:34:04.320> test 00:34:04.509 --> 00:34:04.519 align:start position:0% an error like this oh failed to test 00:34:04.519 --> 00:34:06.430 align:start position:0% an error like this oh failed to test decompose<00:34:04.960> reject<00:34:05.279> on<00:34:05.360> EML<00:34:06.000> then<00:34:06.120> you<00:34:06.240> know 00:34:06.430 --> 00:34:06.440 align:start position:0% decompose reject on EML then you know 00:34:06.440 --> 00:34:09.629 align:start position:0% decompose reject on EML then you know you<00:34:06.600> made<00:34:06.840> some<00:34:07.120> bug<00:34:07.440> on<00:34:07.639> one<00:34:07.760> of<00:34:07.960> these<00:34:08.639> rexes 00:34:09.629 --> 00:34:09.639 align:start position:0% you made some bug on one of these rexes 00:34:09.639 --> 00:34:11.190 align:start position:0% you made some bug on one of these rexes and<00:34:09.800> so<00:34:10.240> you<00:34:10.320> know<00:34:10.480> I<00:34:10.560> can<00:34:10.679> go<00:34:10.839> through<00:34:11.000> and<00:34:11.119> I 00:34:11.190 --> 00:34:11.200 align:start position:0% and so you know I can go through and I 00:34:11.200 --> 00:34:13.109 align:start position:0% and so you know I can go through and I can<00:34:11.320> be<00:34:11.440> like<00:34:11.639> okay<00:34:11.839> like<00:34:11.960> let<00:34:12.040> me<00:34:12.200> try<00:34:12.359> to<00:34:12.960> try 00:34:13.109 --> 00:34:13.119 align:start position:0% can be like okay like let me try to try 00:34:13.119 --> 00:34:15.190 align:start position:0% can be like okay like let me try to try to<00:34:13.280> fix<00:34:13.560> this<00:34:14.200> you<00:34:14.280> know<00:34:14.440> in<00:34:14.560> this<00:34:14.720> case<00:34:15.040> this 00:34:15.190 --> 00:34:15.200 align:start position:0% to fix this you know in this case this 00:34:15.200 --> 00:34:17.149 align:start position:0% to fix this you know in this case this reject<00:34:15.760> you<00:34:15.879> know<00:34:16.079> High<00:34:16.399> Dot<00:34:16.639> is<00:34:16.760> probably<00:34:17.000> not 00:34:17.149 --> 00:34:17.159 align:start position:0% reject you know High Dot is probably not 00:34:17.159 --> 00:34:20.389 align:start position:0% reject you know High Dot is probably not correct<00:34:17.919> um<00:34:18.079> but<00:34:18.200> in<00:34:18.320> this<00:34:18.520> case<00:34:18.760> you<00:34:18.919> know<00:34:19.919> um 00:34:20.389 --> 00:34:20.399 align:start position:0% correct um but in this case you know um 00:34:20.399 --> 00:34:21.950 align:start position:0% correct um but in this case you know um I've<00:34:20.560> gotten<00:34:20.839> like<00:34:20.919> a<00:34:21.040> all<00:34:21.280> test<00:34:21.560> pass<00:34:21.800> ready 00:34:21.950 --> 00:34:21.960 align:start position:0% I've gotten like a all test pass ready 00:34:21.960 --> 00:34:24.589 align:start position:0% I've gotten like a all test pass ready to<00:34:22.119> compile<00:34:23.000> and<00:34:23.119> so<00:34:23.280> I<00:34:23.399> know<00:34:23.879> okay<00:34:24.359> like<00:34:24.480> it 00:34:24.589 --> 00:34:24.599 align:start position:0% to compile and so I know okay like it 00:34:24.599 --> 00:34:26.589 align:start position:0% to compile and so I know okay like it looks<00:34:24.800> like<00:34:25.000> this<00:34:25.200> parser<00:34:25.760> actually<00:34:26.040> ran<00:34:26.440> on 00:34:26.589 --> 00:34:26.599 align:start position:0% looks like this parser actually ran on 00:34:26.599 --> 00:34:28.629 align:start position:0% looks like this parser actually ran on my<00:34:26.760> email<00:34:27.159> and<00:34:27.240> so<00:34:27.359> I<00:34:27.440> should<00:34:27.879> be<00:34:28.280> you<00:34:28.359> know 00:34:28.629 --> 00:34:28.639 align:start position:0% my email and so I should be you know 00:34:28.639 --> 00:34:31.190 align:start position:0% my email and so I should be you know good<00:34:28.839> to<00:34:29.359> good<00:34:29.480> to<00:34:29.599> submit<00:34:29.839> the<00:34:30.000> blueprint<00:34:31.000> um 00:34:31.190 --> 00:34:31.200 align:start position:0% good to good to submit the blueprint um 00:34:31.200 --> 00:34:32.589 align:start position:0% good to good to submit the blueprint um or<00:34:31.320> at<00:34:31.440> least<00:34:31.639> at<00:34:31.720> the<00:34:31.839> very<00:34:32.000> least<00:34:32.200> save<00:34:32.320> it<00:34:32.440> as 00:34:32.589 --> 00:34:32.599 align:start position:0% or at least at the very least save it as 00:34:32.599 --> 00:34:33.869 align:start position:0% or at least at the very least save it as draft<00:34:32.879> and<00:34:33.000> come<00:34:33.159> back<00:34:33.280> to<00:34:33.399> it<00:34:33.480> later<00:34:33.720> if<00:34:33.800> I 00:34:33.869 --> 00:34:33.879 align:start position:0% draft and come back to it later if I 00:34:33.879 --> 00:34:34.909 align:start position:0% draft and come back to it later if I don't<00:34:33.960> want<00:34:34.040> to<00:34:34.159> start<00:34:34.320> the<00:34:34.440> compilation 00:34:34.909 --> 00:34:34.919 align:start position:0% don't want to start the compilation 00:34:34.919 --> 00:34:36.190 align:start position:0% don't want to start the compilation process<00:34:35.200> right<00:34:35.280> now<00:34:35.440> but<00:34:35.520> hopefully<00:34:36.079> the 00:34:36.190 --> 00:34:36.200 align:start position:0% process right now but hopefully the 00:34:36.200 --> 00:34:37.710 align:start position:0% process right now but hopefully the generative<00:34:36.560> output<00:34:36.839> lets<00:34:36.960> you<00:34:37.079> debug<00:34:37.480> did<00:34:37.599> it 00:34:37.710 --> 00:34:37.720 align:start position:0% generative output lets you debug did it 00:34:37.720 --> 00:34:45.310 align:start position:0% generative output lets you debug did it work<00:34:37.879> or<00:34:38.040> not 00:34:45.310 --> 00:34:45.320 align:start position:0% 00:34:45.320 --> 00:34:47.550 align:start position:0% sweet<00:34:46.320> yeah 00:34:47.550 --> 00:34:47.560 align:start position:0% sweet yeah 00:34:47.560 --> 00:34:50.470 align:start position:0% sweet yeah yeah<00:34:48.560> yeah<00:34:48.760> so<00:34:49.000> so<00:34:49.359> the<00:34:49.480> venmo<00:34:49.919> one<00:34:50.119> used<00:34:50.399> like 00:34:50.470 --> 00:34:50.480 align:start position:0% yeah yeah so so the venmo one used like 00:34:50.480 --> 00:34:52.270 align:start position:0% yeah yeah so so the venmo one used like an<00:34:50.599> older<00:34:50.879> version<00:34:51.119> of<00:34:51.320> this<00:34:51.800> where<00:34:52.000> they 00:34:52.270 --> 00:34:52.280 align:start position:0% an older version of this where they 00:34:52.280 --> 00:34:53.710 align:start position:0% an older version of this where they manually<00:34:52.839> kind<00:34:52.960> of<00:34:53.079> went<00:34:53.280> through<00:34:53.480> but<00:34:53.599> the 00:34:53.710 --> 00:34:53.720 align:start position:0% manually kind of went through but the 00:34:53.720 --> 00:34:55.829 align:start position:0% manually kind of went through but the VMO<00:34:54.000> one<00:34:54.159> they<00:34:54.639> defined<00:34:55.079> exactly<00:34:55.399> a<00:34:55.520> similar 00:34:55.829 --> 00:34:55.839 align:start position:0% VMO one they defined exactly a similar 00:34:55.839 --> 00:34:58.230 align:start position:0% VMO one they defined exactly a similar kind<00:34:55.960> of<00:34:56.119> Rex<00:34:56.520> definition<00:34:57.320> and<00:34:57.440> then<00:34:57.800> built 00:34:58.230 --> 00:34:58.240 align:start position:0% kind of Rex definition and then built 00:34:58.240 --> 00:35:00.069 align:start position:0% kind of Rex definition and then built precisely<00:34:59.240> uh<00:34:59.359> this<00:34:59.480> kind<00:34:59.599> of<00:34:59.720> thing<00:34:59.880> but<00:34:59.960> for 00:35:00.069 --> 00:35:00.079 align:start position:0% precisely uh this kind of thing but for 00:35:00.079 --> 00:35:01.550 align:start position:0% precisely uh this kind of thing but for them<00:35:00.200> the<00:35:00.280> dev<00:35:00.440> tooling<00:35:00.760> was<00:35:00.920> much<00:35:01.119> much<00:35:01.280> worse 00:35:01.550 --> 00:35:01.560 align:start position:0% them the dev tooling was much much worse 00:35:01.560 --> 00:35:02.910 align:start position:0% them the dev tooling was much much worse like<00:35:01.680> they<00:35:01.760> did<00:35:01.880> not<00:35:02.040> have<00:35:02.200> this<00:35:02.359> ability<00:35:02.720> to 00:35:02.910 --> 00:35:02.920 align:start position:0% like they did not have this ability to 00:35:02.920 --> 00:35:04.310 align:start position:0% like they did not have this ability to just<00:35:03.240> put<00:35:03.359> in<00:35:03.480> the<00:35:03.599> redx<00:35:03.960> and<00:35:04.079> everything 00:35:04.310 --> 00:35:04.320 align:start position:0% just put in the redx and everything 00:35:04.320 --> 00:35:05.470 align:start position:0% just put in the redx and everything happens<00:35:04.560> for<00:35:04.680> them<00:35:04.800> in<00:35:04.880> the<00:35:04.960> background<00:35:05.359> they 00:35:05.470 --> 00:35:05.480 align:start position:0% happens for them in the background they 00:35:05.480 --> 00:35:07.349 align:start position:0% happens for them in the background they had<00:35:05.560> to<00:35:05.720> kind<00:35:05.839> of<00:35:05.960> manually<00:35:06.320> do<00:35:06.520> everything<00:35:07.200> so 00:35:07.349 --> 00:35:07.359 align:start position:0% had to kind of manually do everything so 00:35:07.359 --> 00:35:09.109 align:start position:0% had to kind of manually do everything so this<00:35:07.440> will<00:35:07.640> let<00:35:07.760> you<00:35:07.880> build<00:35:08.119> the<00:35:08.520> the<00:35:08.640> venmo 00:35:09.109 --> 00:35:09.119 align:start position:0% this will let you build the the venmo 00:35:09.119 --> 00:35:11.270 align:start position:0% this will let you build the the venmo thing<00:35:09.400> ideally<00:35:10.000> in<00:35:10.200> like<00:35:10.480> one<00:35:10.720> session<00:35:11.079> like 00:35:11.270 --> 00:35:11.280 align:start position:0% thing ideally in like one session like 00:35:11.280 --> 00:35:14.150 align:start position:0% thing ideally in like one session like this<00:35:12.280> yep<00:35:12.599> yep<00:35:13.320> um<00:35:13.440> or<00:35:13.560> at<00:35:13.640> least<00:35:13.800> get<00:35:13.920> all<00:35:14.079> that 00:35:14.150 --> 00:35:14.160 align:start position:0% this yep yep um or at least get all that 00:35:14.160 --> 00:35:16.510 align:start position:0% this yep yep um or at least get all that solidity<00:35:14.560> verification<00:35:15.320> kind<00:35:15.440> of<00:35:16.000> done<00:35:16.240> for 00:35:16.510 --> 00:35:16.520 align:start position:0% solidity verification kind of done for 00:35:16.520 --> 00:35:18.150 align:start position:0% solidity verification kind of done for you<00:35:16.760> once<00:35:16.960> the<00:35:17.119> blueprint<00:35:17.599> is<00:35:17.839> finished 00:35:18.150 --> 00:35:18.160 align:start position:0% you once the blueprint is finished 00:35:18.160 --> 00:35:28.589 align:start position:0% you once the blueprint is finished submitted<00:35:18.480> and<00:35:19.040> compiling<00:35:20.400> um<00:35:21.400> sweet<00:35:21.880> yeah 00:35:28.589 --> 00:35:28.599 align:start position:0% 00:35:28.599 --> 00:35:31.589 align:start position:0% no<00:35:28.880> so<00:35:29.119> so<00:35:29.520> what<00:35:29.640> I'm<00:35:29.760> showing<00:35:30.119> right<00:35:30.280> now<00:35:30.599> so 00:35:31.589 --> 00:35:31.599 align:start position:0% no so so what I'm showing right now so 00:35:31.599 --> 00:35:33.270 align:start position:0% no so so what I'm showing right now so the<00:35:31.760> the<00:35:31.880> Gmail<00:35:32.200> login<00:35:32.560> stuff<00:35:32.760> is<00:35:32.920> included 00:35:33.270 --> 00:35:33.280 align:start position:0% the the Gmail login stuff is included 00:35:33.280 --> 00:35:36.470 align:start position:0% the the Gmail login stuff is included for<00:35:33.520> convenience<00:35:34.079> so<00:35:34.200> if<00:35:34.320> I<00:35:34.520> go<00:35:34.760> back<00:35:35.200> to<00:35:36.200> to 00:35:36.470 --> 00:35:36.480 align:start position:0% for convenience so if I go back to to 00:35:36.480 --> 00:35:39.470 align:start position:0% for convenience so if I go back to to here<00:35:36.960> um<00:35:37.440> but<00:35:37.599> if<00:35:37.680> you're<00:35:37.880> using<00:35:38.200> a<00:35:38.359> non-gmail 00:35:39.470 --> 00:35:39.480 align:start position:0% here um but if you're using a non-gmail 00:35:39.480 --> 00:35:42.910 align:start position:0% here um but if you're using a non-gmail client<00:35:40.480> uh<00:35:40.640> two<00:35:40.839> things<00:35:41.119> so<00:35:41.359> one<00:35:41.560> is<00:35:42.400> we<00:35:42.760> we 00:35:42.910 --> 00:35:42.920 align:start position:0% client uh two things so one is we we 00:35:42.920 --> 00:35:45.349 align:start position:0% client uh two things so one is we we plan<00:35:43.160> to<00:35:43.440> add<00:35:44.160> like<00:35:44.359> non-gmail<00:35:44.839> clients<00:35:45.200> into 00:35:45.349 --> 00:35:45.359 align:start position:0% plan to add like non-gmail clients into 00:35:45.359 --> 00:35:46.390 align:start position:0% plan to add like non-gmail clients into this<00:35:45.480> connect<00:35:45.680> Gmail<00:35:45.920> account<00:35:46.079> so<00:35:46.160> we'll<00:35:46.280> add 00:35:46.390 --> 00:35:46.400 align:start position:0% this connect Gmail account so we'll add 00:35:46.400 --> 00:35:48.069 align:start position:0% this connect Gmail account so we'll add you<00:35:46.480> know<00:35:46.680> connect<00:35:47.160> Outlook<00:35:47.599> account<00:35:47.839> connect 00:35:48.069 --> 00:35:48.079 align:start position:0% you know connect Outlook account connect 00:35:48.079 --> 00:35:49.470 align:start position:0% you know connect Outlook account connect all<00:35:48.200> this<00:35:48.320> other<00:35:48.560> stuff<00:35:49.000> and<00:35:49.119> if<00:35:49.200> you<00:35:49.280> use 00:35:49.470 --> 00:35:49.480 align:start position:0% all this other stuff and if you use 00:35:49.480 --> 00:35:50.829 align:start position:0% all this other stuff and if you use something<00:35:49.720> else<00:35:49.920> you<00:35:50.000> can<00:35:50.160> always<00:35:50.400> drag<00:35:50.640> and 00:35:50.829 --> 00:35:50.839 align:start position:0% something else you can always drag and 00:35:50.839 --> 00:35:53.230 align:start position:0% something else you can always drag and drop<00:35:51.200> and<00:35:51.359> upload<00:35:51.680> the<00:35:51.800> raw<00:35:52.000> EML<00:35:52.839> and<00:35:52.920> so<00:35:53.160> this 00:35:53.230 --> 00:35:53.240 align:start position:0% drop and upload the raw EML and so this 00:35:53.240 --> 00:35:55.510 align:start position:0% drop and upload the raw EML and so this will<00:35:53.400> let<00:35:53.520> it<00:35:53.680> work<00:35:53.880> for<00:35:54.040> all<00:35:54.240> non-gmail 00:35:55.510 --> 00:35:55.520 align:start position:0% will let it work for all non-gmail 00:35:55.520 --> 00:35:58.069 align:start position:0% will let it work for all non-gmail accounts<00:35:56.520> yeah<00:35:57.160> um<00:35:57.280> but<00:35:57.440> we<00:35:57.720> we'll<00:35:57.880> add 00:35:58.069 --> 00:35:58.079 align:start position:0% accounts yeah um but we we'll add 00:35:58.079 --> 00:36:01.030 align:start position:0% accounts yeah um but we we'll add ideally<00:35:58.720> connect<00:35:59.000> Outlook<00:35:59.440> pretty<00:36:00.040> soon 00:36:01.030 --> 00:36:01.040 align:start position:0% ideally connect Outlook pretty soon 00:36:01.040 --> 00:36:07.670 align:start position:0% ideally connect Outlook pretty soon sweet<00:36:01.560> Yeah<00:36:01.760> question<00:36:01.960> in<00:36:02.079> the 00:36:07.670 --> 00:36:07.680 align:start position:0% 00:36:07.680 --> 00:36:11.349 align:start position:0% back<00:36:08.680> yeah<00:36:09.200> okay<00:36:09.440> yeah<00:36:10.359> um<00:36:10.720> so<00:36:10.880> when<00:36:11.040> you<00:36:11.160> see 00:36:11.349 --> 00:36:11.359 align:start position:0% back yeah okay yeah um so when you see 00:36:11.359 --> 00:36:13.109 align:start position:0% back yeah okay yeah um so when you see the<00:36:11.480> error<00:36:11.839> like<00:36:12.000> fail<00:36:12.280> to<00:36:12.440> test<00:36:12.640> decomposed 00:36:13.109 --> 00:36:13.119 align:start position:0% the error like fail to test decomposed 00:36:13.119 --> 00:36:15.349 align:start position:0% the error like fail to test decomposed reic<00:36:13.400> on<00:36:13.520> email<00:36:14.200> that<00:36:14.359> means<00:36:14.640> this<00:36:14.800> Rex<00:36:15.200> you 00:36:15.349 --> 00:36:15.359 align:start position:0% reic on email that means this Rex you 00:36:15.359 --> 00:36:17.470 align:start position:0% reic on email that means this Rex you defined<00:36:16.119> does<00:36:16.319> not<00:36:16.599> accurately<00:36:17.000> parse<00:36:17.319> your 00:36:17.470 --> 00:36:17.480 align:start position:0% defined does not accurately parse your 00:36:17.480 --> 00:36:19.589 align:start position:0% defined does not accurately parse your email<00:36:18.280> so<00:36:18.440> what<00:36:18.520> I<00:36:18.599> would<00:36:18.760> recommend<00:36:19.160> doing<00:36:19.440> is 00:36:19.589 --> 00:36:19.599 align:start position:0% email so what I would recommend doing is 00:36:19.599 --> 00:36:21.190 align:start position:0% email so what I would recommend doing is like<00:36:19.760> remove<00:36:20.160> one<00:36:20.359> section<00:36:20.640> at<00:36:20.720> a<00:36:20.880> time<00:36:21.079> like 00:36:21.190 --> 00:36:21.200 align:start position:0% like remove one section at a time like 00:36:21.200 --> 00:36:23.270 align:start position:0% like remove one section at a time like maybe<00:36:21.599> cut<00:36:22.079> you<00:36:22.160> know<00:36:22.319> the<00:36:22.520> last<00:36:22.720> two<00:36:22.960> and<00:36:23.079> be 00:36:23.270 --> 00:36:23.280 align:start position:0% maybe cut you know the last two and be 00:36:23.280 --> 00:36:25.470 align:start position:0% maybe cut you know the last two and be like<00:36:23.520> okay<00:36:23.720> do<00:36:23.839> I<00:36:23.960> still<00:36:24.200> get<00:36:24.319> the<00:36:24.440> error<00:36:25.280> okay 00:36:25.470 --> 00:36:25.480 align:start position:0% like okay do I still get the error okay 00:36:25.480 --> 00:36:26.750 align:start position:0% like okay do I still get the error okay like<00:36:25.599> put<00:36:25.760> it<00:36:25.920> back<00:36:26.119> do<00:36:26.200> I<00:36:26.319> still<00:36:26.520> get<00:36:26.640> the 00:36:26.750 --> 00:36:26.760 align:start position:0% like put it back do I still get the 00:36:26.760 --> 00:36:28.630 align:start position:0% like put it back do I still get the error<00:36:27.319> and<00:36:27.599> kind<00:36:27.680> of<00:36:27.800> try<00:36:27.920> to<00:36:28.000> surgically<00:36:28.440> find 00:36:28.630 --> 00:36:28.640 align:start position:0% error and kind of try to surgically find 00:36:28.640 --> 00:36:30.470 align:start position:0% error and kind of try to surgically find out<00:36:28.839> okay<00:36:28.960> if<00:36:29.040> I<00:36:29.160> remove<00:36:29.520> you<00:36:29.640> know<00:36:30.079> maybe 00:36:30.470 --> 00:36:30.480 align:start position:0% out okay if I remove you know maybe 00:36:30.480 --> 00:36:33.030 align:start position:0% out okay if I remove you know maybe these<00:36:31.079> you<00:36:31.200> know<00:36:31.359> do<00:36:31.480> I<00:36:31.599> still<00:36:31.800> get<00:36:31.920> the<00:36:32.040> error 00:36:33.030 --> 00:36:33.040 align:start position:0% these you know do I still get the error 00:36:33.040 --> 00:36:35.150 align:start position:0% these you know do I still get the error um<00:36:33.240> and<00:36:33.359> try<00:36:33.520> to<00:36:33.680> kind<00:36:33.800> of<00:36:33.920> figure<00:36:34.160> out<00:36:34.960> where 00:36:35.150 --> 00:36:35.160 align:start position:0% um and try to kind of figure out where 00:36:35.160 --> 00:36:36.670 align:start position:0% um and try to kind of figure out where exactly<00:36:35.560> in<00:36:35.640> your<00:36:35.760> reject<00:36:36.119> you<00:36:36.200> made<00:36:36.319> the 00:36:36.670 --> 00:36:36.680 align:start position:0% exactly in your reject you made the 00:36:36.680 --> 00:36:38.829 align:start position:0% exactly in your reject you made the mistake 00:36:38.829 --> 00:36:38.839 align:start position:0% mistake 00:36:38.839 --> 00:36:44.109 align:start position:0% mistake yep 00:36:44.109 --> 00:36:44.119 align:start position:0% 00:36:44.119 --> 00:36:46.750 align:start position:0% yeah<00:36:45.119> the<00:36:45.240> prom<00:36:45.520> for<00:36:45.640> chat<00:36:45.839> GPT<00:36:46.319> yeah<00:36:46.440> so<00:36:46.599> so 00:36:46.750 --> 00:36:46.760 align:start position:0% yeah the prom for chat GPT yeah so so 00:36:46.760 --> 00:36:48.230 align:start position:0% yeah the prom for chat GPT yeah so so maybe<00:36:47.079> what<00:36:47.160> I'll<00:36:47.280> do<00:36:47.440> is<00:36:47.599> I'll<00:36:47.800> I'll<00:36:47.960> demo 00:36:48.230 --> 00:36:48.240 align:start position:0% maybe what I'll do is I'll I'll demo 00:36:48.240 --> 00:36:50.349 align:start position:0% maybe what I'll do is I'll I'll demo this<00:36:48.319> chat<00:36:48.520> GPT<00:36:48.880> bot<00:36:49.119> as<00:36:49.240> well<00:36:49.560> because<00:36:50.240> that 00:36:50.349 --> 00:36:50.359 align:start position:0% this chat GPT bot as well because that 00:36:50.359 --> 00:36:53.670 align:start position:0% this chat GPT bot as well because that will<00:36:50.560> really<00:36:50.760> help<00:36:51.040> folks<00:36:51.920> um<00:36:52.839> use 00:36:53.670 --> 00:36:53.680 align:start position:0% will really help folks um use 00:36:53.680 --> 00:36:55.710 align:start position:0% will really help folks um use it 00:36:55.710 --> 00:36:55.720 align:start position:0% it 00:36:55.720 --> 00:36:58.950 align:start position:0% it uh<00:36:56.720> okay<00:36:57.359> um 00:36:58.950 --> 00:36:58.960 align:start position:0% uh okay um 00:36:58.960 --> 00:37:01.990 align:start position:0% uh okay um um<00:36:59.960> so<00:37:00.359> so<00:37:00.680> the<00:37:00.760> point<00:37:01.040> is<00:37:01.200> you<00:37:01.400> this<00:37:01.520> will<00:37:01.720> help 00:37:01.990 --> 00:37:02.000 align:start position:0% um so so the point is you this will help 00:37:02.000 --> 00:37:03.710 align:start position:0% um so so the point is you this will help create<00:37:02.240> those<00:37:02.400> rexes<00:37:02.960> so<00:37:03.119> maybe<00:37:03.400> what<00:37:03.480> I<00:37:03.599> can 00:37:03.710 --> 00:37:03.720 align:start position:0% create those rexes so maybe what I can 00:37:03.720 --> 00:37:06.390 align:start position:0% create those rexes so maybe what I can do<00:37:03.880> is<00:37:04.040> I<00:37:04.119> can<00:37:04.880> I<00:37:05.000> can<00:37:05.200> take<00:37:05.560> this<00:37:05.920> uh<00:37:06.040> this<00:37:06.160> raw 00:37:06.390 --> 00:37:06.400 align:start position:0% do is I can I can take this uh this raw 00:37:06.400 --> 00:37:10.829 align:start position:0% do is I can I can take this uh this raw EML<00:37:06.880> so<00:37:07.079> let<00:37:07.240> me<00:37:07.839> let<00:37:07.920> me<00:37:08.079> pull<00:37:08.240> up<00:37:08.400> this<00:37:08.760> EML 00:37:10.829 --> 00:37:10.839 align:start position:0% EML so let me let me pull up this EML 00:37:10.839 --> 00:37:13.230 align:start position:0% EML so let me let me pull up this EML um<00:37:11.839> okay<00:37:11.960> so<00:37:12.119> I'm<00:37:12.200> going<00:37:12.280> to<00:37:12.560> like<00:37:12.720> copy<00:37:13.000> paste 00:37:13.230 --> 00:37:13.240 align:start position:0% um okay so I'm going to like copy paste 00:37:13.240 --> 00:37:15.670 align:start position:0% um okay so I'm going to like copy paste this<00:37:13.599> EML<00:37:13.960> file<00:37:14.200> I<00:37:14.359> downloaded<00:37:15.160> into<00:37:15.359> the<00:37:15.480> chat 00:37:15.670 --> 00:37:15.680 align:start position:0% this EML file I downloaded into the chat 00:37:15.680 --> 00:37:18.630 align:start position:0% this EML file I downloaded into the chat GPT<00:37:16.160> bot<00:37:17.000> and<00:37:17.079> then<00:37:17.240> I'm<00:37:17.359> going<00:37:17.520> to<00:37:17.680> say<00:37:18.359> help 00:37:18.630 --> 00:37:18.640 align:start position:0% GPT bot and then I'm going to say help 00:37:18.640 --> 00:37:20.030 align:start position:0% GPT bot and then I'm going to say help me 00:37:20.030 --> 00:37:20.040 align:start position:0% me 00:37:20.040 --> 00:37:25.390 align:start position:0% me extract<00:37:21.040> via<00:37:21.560> Rex<00:37:22.319> the<00:37:22.599> part<00:37:23.440> after<00:37:24.440> Google 00:37:25.390 --> 00:37:25.400 align:start position:0% extract via Rex the part after Google 00:37:25.400 --> 00:37:30.309 align:start position:0% extract via Rex the part after Google Alerts 00:37:30.309 --> 00:37:30.319 align:start position:0% 00:37:30.319 --> 00:37:32.670 align:start position:0% Alert<00:37:31.319> in<00:37:31.680> the 00:37:32.670 --> 00:37:32.680 align:start position:0% Alert in the 00:37:32.680 --> 00:37:34.670 align:start position:0% Alert in the body<00:37:33.680> something<00:37:34.000> like<00:37:34.200> this<00:37:34.319> so<00:37:34.440> I'm<00:37:34.520> going<00:37:34.599> to 00:37:34.670 --> 00:37:34.680 align:start position:0% body something like this so I'm going to 00:37:34.680 --> 00:37:35.990 align:start position:0% body something like this so I'm going to paste<00:37:34.839> in<00:37:34.920> the<00:37:35.000> email<00:37:35.200> I'm<00:37:35.280> going<00:37:35.359> to<00:37:35.560> ask<00:37:35.839> like 00:37:35.990 --> 00:37:36.000 align:start position:0% paste in the email I'm going to ask like 00:37:36.000 --> 00:37:38.470 align:start position:0% paste in the email I'm going to ask like you<00:37:36.119> know<00:37:36.280> help<00:37:36.440> me<00:37:36.640> generate<00:37:37.440> this<00:37:37.640> Rex<00:37:38.160> to<00:37:38.359> to 00:37:38.470 --> 00:37:38.480 align:start position:0% you know help me generate this Rex to to 00:37:38.480 --> 00:37:40.670 align:start position:0% you know help me generate this Rex to to do<00:37:38.680> this<00:37:38.800> kind<00:37:38.920> of<00:37:39.119> parsing<00:37:40.119> and<00:37:40.280> if<00:37:40.359> I<00:37:40.480> send 00:37:40.670 --> 00:37:40.680 align:start position:0% do this kind of parsing and if I send 00:37:40.680 --> 00:37:43.270 align:start position:0% do this kind of parsing and if I send this<00:37:40.960> out<00:37:41.960> um<00:37:42.280> you<00:37:42.359> know<00:37:42.480> it'll<00:37:42.839> take<00:37:42.960> a<00:37:43.079> second 00:37:43.270 --> 00:37:43.280 align:start position:0% this out um you know it'll take a second 00:37:43.280 --> 00:37:47.430 align:start position:0% this out um you know it'll take a second to 00:37:47.430 --> 00:37:47.440 align:start position:0% 00:37:47.440 --> 00:37:49.390 align:start position:0% process<00:37:48.440> then<00:37:48.560> it'll<00:37:48.720> show<00:37:48.839> us<00:37:49.040> okay<00:37:49.200> what<00:37:49.280> is 00:37:49.390 --> 00:37:49.400 align:start position:0% process then it'll show us okay what is 00:37:49.400 --> 00:37:50.790 align:start position:0% process then it'll show us okay what is the<00:37:49.520> name<00:37:49.880> where<00:37:50.000> should<00:37:50.160> I<00:37:50.280> parse<00:37:50.599> I<00:37:50.680> should 00:37:50.790 --> 00:37:50.800 align:start position:0% the name where should I parse I should 00:37:50.800 --> 00:37:52.910 align:start position:0% the name where should I parse I should parse<00:37:51.000> in<00:37:51.119> the<00:37:51.200> body<00:37:52.200> um<00:37:52.400> and<00:37:52.480> then<00:37:52.560> it'll<00:37:52.800> give 00:37:52.910 --> 00:37:52.920 align:start position:0% parse in the body um and then it'll give 00:37:52.920 --> 00:37:55.069 align:start position:0% parse in the body um and then it'll give me<00:37:53.079> the<00:37:53.200> parts<00:37:53.440> array<00:37:54.119> and<00:37:54.319> explain<00:37:54.680> each<00:37:54.880> part 00:37:55.069 --> 00:37:55.079 align:start position:0% me the parts array and explain each part 00:37:55.079 --> 00:37:58.630 align:start position:0% me the parts array and explain each part so<00:37:55.440> so<00:37:55.599> you<00:37:55.720> know<00:37:55.880> I'll<00:37:56.040> do<00:37:57.040> um 00:37:58.630 --> 00:37:58.640 align:start position:0% so so you know I'll do um 00:37:58.640 --> 00:38:01.950 align:start position:0% so so you know I'll do um let<00:37:58.720> me<00:37:58.880> pull<00:37:59.040> this<00:37:59.240> back<00:37:59.400> up<00:38:00.440> um<00:38:01.440> so<00:38:01.640> so<00:38:01.760> it'll 00:38:01.950 --> 00:38:01.960 align:start position:0% let me pull this back up um so so it'll 00:38:01.960 --> 00:38:03.430 align:start position:0% let me pull this back up um so so it'll tell<00:38:02.079> me<00:38:02.200> in<00:38:02.280> the<00:38:02.400> first<00:38:02.599> one<00:38:02.760> make<00:38:02.960> is<00:38:03.160> public 00:38:03.430 --> 00:38:03.440 align:start position:0% tell me in the first one make is public 00:38:03.440 --> 00:38:05.550 align:start position:0% tell me in the first one make is public false<00:38:03.760> and<00:38:03.920> put<00:38:04.040> you<00:38:04.119> know<00:38:04.240> Google<00:38:04.480> alert<00:38:04.880> Dash 00:38:05.550 --> 00:38:05.560 align:start position:0% false and put you know Google alert Dash 00:38:05.560 --> 00:38:07.510 align:start position:0% false and put you know Google alert Dash and<00:38:05.640> in<00:38:05.760> the<00:38:05.880> second<00:38:06.160> one<00:38:06.880> make<00:38:07.119> is<00:38:07.280> public 00:38:07.510 --> 00:38:07.520 align:start position:0% and in the second one make is public 00:38:07.520 --> 00:38:10.190 align:start position:0% and in the second one make is public equals<00:38:07.800> true<00:38:08.160> and<00:38:08.400> put<00:38:09.400> you<00:38:09.520> know<00:38:09.839> anything 00:38:10.190 --> 00:38:10.200 align:start position:0% equals true and put you know anything 00:38:10.200 --> 00:38:12.430 align:start position:0% equals true and put you know anything except<00:38:10.520> this<00:38:10.640> end<00:38:10.960> forward<00:38:11.480> and<00:38:11.599> so<00:38:12.119> here<00:38:12.319> you 00:38:12.430 --> 00:38:12.440 align:start position:0% except this end forward and so here you 00:38:12.440 --> 00:38:14.150 align:start position:0% except this end forward and so here you know<00:38:12.760> I've<00:38:12.880> changed<00:38:13.240> anything<00:38:13.560> but<00:38:13.680> the<00:38:13.800> quote 00:38:14.150 --> 00:38:14.160 align:start position:0% know I've changed anything but the quote 00:38:14.160 --> 00:38:16.030 align:start position:0% know I've changed anything but the quote because<00:38:14.359> the<00:38:14.480> quote<00:38:14.720> comes<00:38:14.960> afterwards<00:38:15.839> but 00:38:16.030 --> 00:38:16.040 align:start position:0% because the quote comes afterwards but 00:38:16.040 --> 00:38:17.230 align:start position:0% because the quote comes afterwards but this<00:38:16.119> is<00:38:16.319> like<00:38:16.440> somewhat<00:38:16.760> accurate<00:38:17.079> like<00:38:17.160> I 00:38:17.230 --> 00:38:17.240 align:start position:0% this is like somewhat accurate like I 00:38:17.240 --> 00:38:20.630 align:start position:0% this is like somewhat accurate like I can<00:38:17.440> take<00:38:18.160> these<00:38:18.720> little<00:38:19.040> is<00:38:19.280> public<00:38:20.119> and<00:38:20.240> Rex 00:38:20.630 --> 00:38:20.640 align:start position:0% can take these little is public and Rex 00:38:20.640 --> 00:38:22.190 align:start position:0% can take these little is public and Rex parts<00:38:20.920> and<00:38:21.079> and<00:38:21.160> plug<00:38:21.359> it<00:38:21.520> into<00:38:21.760> exactly<00:38:22.079> this 00:38:22.190 --> 00:38:22.200 align:start position:0% parts and and plug it into exactly this 00:38:22.200 --> 00:38:24.150 align:start position:0% parts and and plug it into exactly this kind<00:38:22.359> of<00:38:22.440> a<00:38:22.599> Json<00:38:23.400> and<00:38:23.480> then<00:38:23.599> if<00:38:23.680> I<00:38:23.800> dump<00:38:24.040> that 00:38:24.150 --> 00:38:24.160 align:start position:0% kind of a Json and then if I dump that 00:38:24.160 --> 00:38:25.550 align:start position:0% kind of a Json and then if I dump that in<00:38:24.280> I<00:38:24.359> should<00:38:24.520> be<00:38:24.640> good<00:38:24.760> to<00:38:24.920> go<00:38:25.160> and<00:38:25.280> in<00:38:25.400> fact 00:38:25.550 --> 00:38:25.560 align:start position:0% in I should be good to go and in fact 00:38:25.560 --> 00:38:27.510 align:start position:0% in I should be good to go and in fact it'll<00:38:25.800> give<00:38:25.920> me<00:38:26.079> this<00:38:26.240> like<00:38:26.400> Json<00:38:27.119> parts 00:38:27.510 --> 00:38:27.520 align:start position:0% it'll give me this like Json parts 00:38:27.520 --> 00:38:29.270 align:start position:0% it'll give me this like Json parts section<00:38:27.760> that<00:38:27.880> I<00:38:27.960> can<00:38:28.079> just<00:38:28.280> copy<00:38:28.560> out<00:38:29.160> the 00:38:29.270 --> 00:38:29.280 align:start position:0% section that I can just copy out the 00:38:29.280 --> 00:38:31.270 align:start position:0% section that I can just copy out the parts<00:38:29.640> directly<00:38:30.040> in<00:38:30.240> this<00:38:30.440> like<00:38:30.640> piece<00:38:30.880> of 00:38:31.270 --> 00:38:31.280 align:start position:0% parts directly in this like piece of 00:38:31.280 --> 00:38:33.349 align:start position:0% parts directly in this like piece of code<00:38:31.520> it<00:38:31.720> generates<00:38:32.720> um<00:38:32.839> so<00:38:32.960> hopefully<00:38:33.240> this 00:38:33.349 --> 00:38:33.359 align:start position:0% code it generates um so hopefully this 00:38:33.359 --> 00:38:35.589 align:start position:0% code it generates um so hopefully this chat<00:38:33.560> GPT<00:38:33.960> bot<00:38:34.520> helps<00:38:34.800> people<00:38:35.000> generate<00:38:35.240> the 00:38:35.589 --> 00:38:35.599 align:start position:0% chat GPT bot helps people generate the 00:38:35.599 --> 00:38:37.790 align:start position:0% chat GPT bot helps people generate the regexes<00:38:36.599> um<00:38:36.720> and<00:38:36.839> can<00:38:36.960> help<00:38:37.079> you<00:38:37.240> also<00:38:37.400> debug 00:38:37.790 --> 00:38:37.800 align:start position:0% regexes um and can help you also debug 00:38:37.800 --> 00:38:39.790 align:start position:0% regexes um and can help you also debug you<00:38:37.880> can<00:38:38.000> say<00:38:38.280> hey<00:38:38.720> I<00:38:38.839> use<00:38:39.119> this<00:38:39.240> as<00:38:39.400> my<00:38:39.560> parts 00:38:39.790 --> 00:38:39.800 align:start position:0% you can say hey I use this as my parts 00:38:39.800 --> 00:38:41.630 align:start position:0% you can say hey I use this as my parts Json<00:38:40.200> it's<00:38:40.359> not<00:38:40.520> working<00:38:41.079> why<00:38:41.319> where<00:38:41.480> might 00:38:41.630 --> 00:38:41.640 align:start position:0% Json it's not working why where might 00:38:41.640 --> 00:38:43.470 align:start position:0% Json it's not working why where might the<00:38:41.760> parts<00:38:41.960> thing<00:38:42.119> be<00:38:42.319> wrong<00:38:42.960> and<00:38:43.079> the<00:38:43.200> hope<00:38:43.359> is 00:38:43.470 --> 00:38:43.480 align:start position:0% the parts thing be wrong and the hope is 00:38:43.480 --> 00:38:44.990 align:start position:0% the parts thing be wrong and the hope is that<00:38:43.640> this<00:38:43.760> bot<00:38:44.040> has<00:38:44.200> enough<00:38:44.440> prompts<00:38:44.800> of 00:38:44.990 --> 00:38:45.000 align:start position:0% that this bot has enough prompts of 00:38:45.000 --> 00:38:46.390 align:start position:0% that this bot has enough prompts of example<00:38:45.400> patterns<00:38:45.680> from<00:38:45.800> our<00:38:45.920> registry<00:38:46.319> that 00:38:46.390 --> 00:38:46.400 align:start position:0% example patterns from our registry that 00:38:46.400 --> 00:38:49.190 align:start position:0% example patterns from our registry that it<00:38:46.480> can<00:38:46.640> help<00:38:46.839> you<00:38:47.560> debug 00:38:49.190 --> 00:38:49.200 align:start position:0% it can help you debug 00:38:49.200 --> 00:38:53.109 align:start position:0% it can help you debug that<00:38:50.200> cool<00:38:51.079> um<00:38:52.079> yeah<00:38:52.240> maybe<00:38:52.640> I'm<00:38:52.760> going<00:38:52.839> to<00:38:52.960> go 00:38:53.109 --> 00:38:53.119 align:start position:0% that cool um yeah maybe I'm going to go 00:38:53.119 --> 00:38:54.550 align:start position:0% that cool um yeah maybe I'm going to go around<00:38:53.440> and<00:38:53.640> keep<00:38:53.839> helping<00:38:54.079> people<00:38:54.280> oneon-one 00:38:54.550 --> 00:38:54.560 align:start position:0% around and keep helping people oneon-one 00:38:54.560 --> 00:38:57.630 align:start position:0% around and keep helping people oneon-one and<00:38:54.960> we'll<00:38:55.280> we'll<00:38:55.560> see<00:38:56.560> um<00:38:57.000> we'll<00:38:57.160> do<00:38:57.280> this<00:38:57.520> for 00:38:57.630 --> 00:38:57.640 align:start position:0% and we'll we'll see um we'll do this for 00:38:57.640 --> 00:38:58.710 align:start position:0% and we'll we'll see um we'll do this for about<00:38:57.800> seven<00:38:58.040> more<00:38:58.200> minutes<00:38:58.440> and<00:38:58.560> then 00:38:58.710 --> 00:38:58.720 align:start position:0% about seven more minutes and then 00:38:58.720 --> 00:39:01.069 align:start position:0% about seven more minutes and then transition<00:38:59.160> to<00:38:59.319> the<00:38:59.440> solidity<00:38:59.920> part<00:39:00.599> of<00:39:00.839> the 00:39:01.069 --> 00:39:01.079 align:start position:0% transition to the solidity part of the 00:39:01.079 --> 00:39:03.069 align:start position:0% transition to the solidity part of the of<00:39:01.200> the<00:39:01.319> workshop<00:39:01.880> so<00:39:02.359> even<00:39:02.560> if<00:39:02.640> you<00:39:02.760> got 00:39:03.069 --> 00:39:03.079 align:start position:0% of the workshop so even if you got 00:39:03.079 --> 00:39:06.670 align:start position:0% of the workshop so even if you got totally<00:39:03.599> super<00:39:03.920> duper<00:39:04.160> lost<00:39:04.520> here<00:39:05.400> um<00:39:06.359> we'll 00:39:06.670 --> 00:39:06.680 align:start position:0% totally super duper lost here um we'll 00:39:06.680 --> 00:39:07.950 align:start position:0% totally super duper lost here um we'll we'll<00:39:06.839> transition<00:39:07.200> to<00:39:07.319> Something<00:39:07.560> in<00:39:07.720> about 00:39:07.950 --> 00:39:07.960 align:start position:0% we'll transition to Something in about 00:39:07.960 --> 00:39:11.109 align:start position:0% we'll transition to Something in about five<00:39:08.119> minutes<00:39:08.400> or<00:39:08.520> so<00:39:08.839> so<00:39:09.480> yeah<00:39:10.359> sweet<00:39:10.839> I<00:39:11.000> I'll 00:39:11.109 --> 00:39:11.119 align:start position:0% five minutes or so so yeah sweet I I'll 00:39:11.119 --> 00:39:12.470 align:start position:0% five minutes or so so yeah sweet I I'll keep<00:39:11.240> going<00:39:11.440> around<00:39:11.680> answering<00:39:12.000> questions 00:39:12.470 --> 00:39:12.480 align:start position:0% keep going around answering questions 00:39:12.480 --> 00:39:38.750 align:start position:0% keep going around answering questions yeah 00:39:38.750 --> 00:39:38.760 align:start position:0% 00:39:38.760 --> 00:40:26.309 align:start position:0% I 00:40:26.309 --> 00:40:26.319 align:start position:0% 00:40:26.319 --> 00:41:02.700 align:start position:0% fi<00:40:27.319> e 00:41:02.700 --> 00:41:02.710 align:start position:0% 00:41:02.710 --> 00:41:08.100 align:start position:0% [Music] 00:41:08.100 --> 00:41:08.110 align:start position:0% 00:41:08.110 --> 00:41:21.270 align:start position:0% [Music] 00:41:21.270 --> 00:41:21.280 align:start position:0% 00:41:21.280 --> 00:41:30.920 align:start position:0% spe 00:41:30.920 --> 00:41:30.930 align:start position:0% 00:41:30.930 --> 00:41:56.230 align:start position:0% [Music] 00:41:56.230 --> 00:41:56.240 align:start position:0% 00:41:56.240 --> 00:42:15.560 align:start position:0% J 00:42:15.560 --> 00:42:15.570 align:start position:0% 00:42:15.570 --> 00:42:26.109 align:start position:0% [Music] 00:42:26.109 --> 00:42:26.119 align:start position:0% 00:42:26.119 --> 00:42:32.150 align:start position:0% let 00:42:32.150 --> 00:42:32.160 align:start position:0% 00:42:32.160 --> 00:42:56.109 align:start position:0% [Music] 00:42:56.109 --> 00:42:56.119 align:start position:0% 00:42:56.119 --> 00:42:58.610 align:start position:0% for 00:42:58.610 --> 00:42:58.620 align:start position:0% for 00:42:58.620 --> 00:43:26.109 align:start position:0% for [Music] 00:43:26.109 --> 00:43:26.119 align:start position:0% 00:43:26.119 --> 00:43:56.030 align:start position:0% e 00:43:56.030 --> 00:43:56.040 align:start position:0% 00:43:56.040 --> 00:44:15.900 align:start position:0% e<00:43:57.079> for 00:44:15.900 --> 00:44:15.910 align:start position:0% 00:44:15.910 --> 00:44:27.510 align:start position:0% [Music] 00:44:27.510 --> 00:44:27.520 align:start position:0% 00:44:27.520 --> 00:44:43.600 align:start position:0% um 00:44:43.600 --> 00:44:43.610 align:start position:0% 00:44:43.610 --> 00:45:19.550 align:start position:0% [Music] 00:45:19.550 --> 00:45:19.560 align:start position:0% 00:45:19.560 --> 00:45:25.950 align:start position:0% [Music] 00:45:25.950 --> 00:45:25.960 align:start position:0% [Music] 00:45:25.960 --> 00:45:27.130 align:start position:0% [Music] yeah 00:45:27.130 --> 00:45:27.140 align:start position:0% yeah 00:45:27.140 --> 00:45:46.090 align:start position:0% yeah [Music] 00:45:46.090 --> 00:45:46.100 align:start position:0% 00:45:46.100 --> 00:45:55.910 align:start position:0% [Music] 00:45:55.910 --> 00:45:55.920 align:start position:0% [Music] 00:45:55.920 --> 00:46:07.530 align:start position:0% [Music] for 00:46:07.530 --> 00:46:07.540 align:start position:0% 00:46:07.540 --> 00:46:22.990 align:start position:0% [Music] 00:46:22.990 --> 00:46:23.000 align:start position:0% 00:46:23.000 --> 00:46:25.910 align:start position:0% [Music] 00:46:25.910 --> 00:46:25.920 align:start position:0% [Music] 00:46:25.920 --> 00:46:29.370 align:start position:0% [Music] for<00:46:26.920> for 00:46:29.370 --> 00:46:29.380 align:start position:0% for for 00:46:29.380 --> 00:47:17.000 align:start position:0% for for [Music] 00:47:17.000 --> 00:47:17.010 align:start position:0% 00:47:17.010 --> 00:47:25.829 align:start position:0% [Music] 00:47:25.829 --> 00:47:25.839 align:start position:0% 00:47:25.839 --> 00:47:29.130 align:start position:0% that's 00:47:29.130 --> 00:47:29.140 align:start position:0% 00:47:29.140 --> 00:47:39.360 align:start position:0% [Music] 00:47:39.360 --> 00:47:39.370 align:start position:0% 00:47:39.370 --> 00:47:55.829 align:start position:0% [Music] 00:47:55.829 --> 00:47:55.839 align:start position:0% 00:47:55.839 --> 00:48:25.370 align:start position:0% e<00:47:56.839> e 00:48:25.370 --> 00:48:25.380 align:start position:0% 00:48:25.380 --> 00:49:17.470 align:start position:0% [Music] 00:49:17.470 --> 00:49:17.480 align:start position:0% 00:49:17.480 --> 00:49:37.910 align:start position:0% [Music] 00:49:37.910 --> 00:49:37.920 align:start position:0% 00:49:37.920 --> 00:49:47.020 align:start position:0% [Music] 00:49:47.020 --> 00:49:47.030 align:start position:0% 00:49:47.030 --> 00:49:56.270 align:start position:0% [Music] 00:49:56.270 --> 00:49:56.280 align:start position:0% 00:49:56.280 --> 00:50:01.030 align:start position:0% this 00:50:01.030 --> 00:50:01.040 align:start position:0% 00:50:01.040 --> 00:50:03.829 align:start position:0% Okay<00:50:01.319> cool<00:50:01.520> so<00:50:01.680> I'm<00:50:01.799> going<00:50:01.880> to<00:50:02.160> just<00:50:02.839> briefly 00:50:03.829 --> 00:50:03.839 align:start position:0% Okay cool so I'm going to just briefly 00:50:03.839 --> 00:50:05.589 align:start position:0% Okay cool so I'm going to just briefly uh<00:50:04.200> explain<00:50:04.599> the<00:50:04.760> main<00:50:05.040> issues<00:50:05.280> that<00:50:05.440> people 00:50:05.589 --> 00:50:05.599 align:start position:0% uh explain the main issues that people 00:50:05.599 --> 00:50:07.470 align:start position:0% uh explain the main issues that people have<00:50:05.720> been<00:50:05.960> having<00:50:06.799> and<00:50:06.960> then<00:50:07.119> we're<00:50:07.240> going<00:50:07.359> to 00:50:07.470 --> 00:50:07.480 align:start position:0% have been having and then we're going to 00:50:07.480 --> 00:50:09.950 align:start position:0% have been having and then we're going to transition<00:50:08.040> to<00:50:08.319> the<00:50:09.119> like<00:50:09.280> other<00:50:09.520> code 00:50:09.950 --> 00:50:09.960 align:start position:0% transition to the like other code 00:50:09.960 --> 00:50:12.349 align:start position:0% transition to the like other code sections<00:50:10.960> um<00:50:11.240> okay<00:50:11.400> so<00:50:11.839> some<00:50:12.040> issues<00:50:12.280> that 00:50:12.349 --> 00:50:12.359 align:start position:0% sections um okay so some issues that 00:50:12.359 --> 00:50:14.510 align:start position:0% sections um okay so some issues that people<00:50:12.480> were<00:50:12.720> having<00:50:13.000> as<00:50:13.119> I<00:50:13.240> noticed<00:50:14.160> um<00:50:14.319> for 00:50:14.510 --> 00:50:14.520 align:start position:0% people were having as I noticed um for 00:50:14.520 --> 00:50:15.990 align:start position:0% people were having as I noticed um for some<00:50:14.680> folks<00:50:14.920> the<00:50:15.040> submit<00:50:15.319> blueprint<00:50:15.720> button 00:50:15.990 --> 00:50:16.000 align:start position:0% some folks the submit blueprint button 00:50:16.000 --> 00:50:18.150 align:start position:0% some folks the submit blueprint button was<00:50:16.200> not<00:50:16.400> enabled<00:50:17.400> um<00:50:17.520> so<00:50:17.599> you<00:50:17.720> have<00:50:17.839> to<00:50:17.960> fill 00:50:18.150 --> 00:50:18.160 align:start position:0% was not enabled um so you have to fill 00:50:18.160 --> 00:50:20.710 align:start position:0% was not enabled um so you have to fill in<00:50:18.359> all<00:50:18.520> the<00:50:18.640> fields<00:50:19.079> so<00:50:19.319> like<00:50:19.640> you<00:50:19.760> know<00:50:19.960> 64 00:50:20.710 --> 00:50:20.720 align:start position:0% in all the fields so like you know 64 00:50:20.720 --> 00:50:22.430 align:start position:0% in all the fields so like you know 64 like<00:50:20.920> the<00:50:21.160> max<00:50:21.440> length<00:50:21.680> is<00:50:21.799> one<00:50:22.000> common<00:50:22.240> one 00:50:22.430 --> 00:50:22.440 align:start position:0% like the max length is one common one 00:50:22.440 --> 00:50:25.829 align:start position:0% like the max length is one common one people<00:50:22.799> missed<00:50:23.799> um<00:50:24.720> you<00:50:24.880> have<00:50:25.000> to<00:50:25.160> put<00:50:25.359> in<00:50:25.680> a 00:50:25.829 --> 00:50:25.839 align:start position:0% people missed um you have to put in a 00:50:25.839 --> 00:50:27.710 align:start position:0% people missed um you have to put in a like<00:50:26.000> description<00:50:26.720> you<00:50:26.839> have<00:50:26.960> to<00:50:27.079> put<00:50:27.200> in<00:50:27.480> a 00:50:27.710 --> 00:50:27.720 align:start position:0% like description you have to put in a 00:50:27.720 --> 00:50:29.430 align:start position:0% like description you have to put in a tag<00:50:28.119> and<00:50:28.200> then<00:50:28.359> click<00:50:28.599> enter<00:50:28.920> so<00:50:29.079> it<00:50:29.160> becomes 00:50:29.430 --> 00:50:29.440 align:start position:0% tag and then click enter so it becomes 00:50:29.440 --> 00:50:31.630 align:start position:0% tag and then click enter so it becomes like<00:50:29.559> a<00:50:29.720> tag<00:50:30.040> type<00:50:30.760> and<00:50:30.920> you<00:50:31.079> have<00:50:31.200> to<00:50:31.319> upload 00:50:31.630 --> 00:50:31.640 align:start position:0% like a tag type and you have to upload 00:50:31.640 --> 00:50:34.069 align:start position:0% like a tag type and you have to upload an<00:50:31.760> email<00:50:32.520> for<00:50:32.799> the<00:50:33.280> the<00:50:33.520> so<00:50:33.640> you<00:50:33.760> have<00:50:33.839> to<00:50:33.960> have 00:50:34.069 --> 00:50:34.079 align:start position:0% an email for the the so you have to have 00:50:34.079 --> 00:50:35.510 align:start position:0% an email for the the so you have to have like<00:50:34.160> an<00:50:34.240> uploaded<00:50:34.599> email<00:50:34.880> in<00:50:35.000> this<00:50:35.119> field<00:50:35.359> for 00:50:35.510 --> 00:50:35.520 align:start position:0% like an uploaded email in this field for 00:50:35.520 --> 00:50:36.789 align:start position:0% like an uploaded email in this field for the<00:50:35.640> submit<00:50:35.920> blueprint<00:50:36.240> button<00:50:36.480> to<00:50:36.559> be 00:50:36.789 --> 00:50:36.799 align:start position:0% the submit blueprint button to be 00:50:36.799 --> 00:50:38.950 align:start position:0% the submit blueprint button to be available<00:50:37.799> um<00:50:37.960> and<00:50:38.240> at<00:50:38.359> the<00:50:38.480> bottom<00:50:38.720> you<00:50:38.880> have 00:50:38.950 --> 00:50:38.960 align:start position:0% available um and at the bottom you have 00:50:38.960 --> 00:50:41.510 align:start position:0% available um and at the bottom you have to<00:50:39.079> see<00:50:39.319> like<00:50:39.480> test<00:50:39.920> pass<00:50:40.920> um<00:50:41.040> if<00:50:41.119> there's<00:50:41.319> no 00:50:41.510 --> 00:50:41.520 align:start position:0% to see like test pass um if there's no 00:50:41.520 --> 00:50:43.069 align:start position:0% to see like test pass um if there's no email<00:50:41.799> uploaded<00:50:42.200> here<00:50:42.359> it<00:50:42.440> won't<00:50:42.720> let<00:50:42.880> you 00:50:43.069 --> 00:50:43.079 align:start position:0% email uploaded here it won't let you 00:50:43.079 --> 00:50:44.870 align:start position:0% email uploaded here it won't let you submit<00:50:43.760> like<00:50:43.920> submit<00:50:44.200> the<00:50:44.280> actual<00:50:44.520> blueprint 00:50:44.870 --> 00:50:44.880 align:start position:0% submit like submit the actual blueprint 00:50:44.880 --> 00:50:47.230 align:start position:0% submit like submit the actual blueprint at<00:50:44.960> the<00:50:45.079> bottom<00:50:46.000> um<00:50:46.160> I<00:50:46.240> noticed<00:50:46.559> some<00:50:46.760> folks 00:50:47.230 --> 00:50:47.240 align:start position:0% at the bottom um I noticed some folks 00:50:47.240 --> 00:50:49.870 align:start position:0% at the bottom um I noticed some folks saved<00:50:47.680> as<00:50:47.880> draft<00:50:48.839> um<00:50:49.000> and<00:50:49.119> then<00:50:49.280> tried<00:50:49.640> the 00:50:49.870 --> 00:50:49.880 align:start position:0% saved as draft um and then tried the 00:50:49.880 --> 00:50:51.270 align:start position:0% saved as draft um and then tried the pattern<00:50:50.160> on<00:50:50.319> the<00:50:50.480> on<00:50:50.559> the<00:50:50.720> front<00:50:50.960> page<00:50:51.160> and 00:50:51.270 --> 00:50:51.280 align:start position:0% pattern on the on the front page and 00:50:51.280 --> 00:50:53.150 align:start position:0% pattern on the on the front page and realized<00:50:51.559> they<00:50:51.680> couldn't<00:50:51.920> hit<00:50:52.119> create<00:50:52.480> proof 00:50:53.150 --> 00:50:53.160 align:start position:0% realized they couldn't hit create proof 00:50:53.160 --> 00:50:54.990 align:start position:0% realized they couldn't hit create proof so<00:50:53.280> the<00:50:53.440> main<00:50:53.680> thing<00:50:53.920> there<00:50:54.079> is<00:50:54.240> that<00:50:54.680> you<00:50:54.799> can 00:50:54.990 --> 00:50:55.000 align:start position:0% so the main thing there is that you can 00:50:55.000 --> 00:50:56.670 align:start position:0% so the main thing there is that you can only<00:50:55.280> do<00:50:55.599> create<00:50:55.880> proof<00:50:56.079> on<00:50:56.200> the<00:50:56.280> main<00:50:56.440> page 00:50:56.670 --> 00:50:56.680 align:start position:0% only do create proof on the main page 00:50:56.680 --> 00:50:58.829 align:start position:0% only do create proof on the main page page<00:50:57.319> if<00:50:57.440> you've<00:50:57.640> submitted<00:50:58.000> the<00:50:58.079> blueprint 00:50:58.829 --> 00:50:58.839 align:start position:0% page if you've submitted the blueprint 00:50:58.839 --> 00:51:00.470 align:start position:0% page if you've submitted the blueprint and<00:50:58.960> you've<00:50:59.160> waited<00:50:59.440> a<00:50:59.559> few<00:50:59.760> hours<00:51:00.079> for<00:51:00.280> the 00:51:00.470 --> 00:51:00.480 align:start position:0% and you've waited a few hours for the 00:51:00.480 --> 00:51:02.150 align:start position:0% and you've waited a few hours for the thing<00:51:00.680> to<00:51:01.000> actually<00:51:01.319> compile<00:51:01.680> and<00:51:01.799> for<00:51:01.920> us<00:51:02.040> to 00:51:02.150 --> 00:51:02.160 align:start position:0% thing to actually compile and for us to 00:51:02.160 --> 00:51:03.109 align:start position:0% thing to actually compile and for us to make<00:51:02.280> the<00:51:02.400> circuit<00:51:02.680> for<00:51:02.760> you<00:51:02.880> in<00:51:03.000> the 00:51:03.109 --> 00:51:03.119 align:start position:0% make the circuit for you in the 00:51:03.119 --> 00:51:05.589 align:start position:0% make the circuit for you in the background<00:51:03.640> so<00:51:04.160> it'll<00:51:04.480> it'll<00:51:04.799> kind<00:51:04.880> of<00:51:05.079> take<00:51:05.319> a 00:51:05.589 --> 00:51:05.599 align:start position:0% background so it'll it'll kind of take a 00:51:05.599 --> 00:51:09.470 align:start position:0% background so it'll it'll kind of take a a<00:51:05.720> moment<00:51:06.000> for<00:51:06.160> that<00:51:06.280> to<00:51:06.440> work<00:51:07.400> um<00:51:08.400> yeah<00:51:08.640> so<00:51:09.359> uh 00:51:09.470 --> 00:51:09.480 align:start position:0% a moment for that to work um yeah so uh 00:51:09.480 --> 00:51:10.789 align:start position:0% a moment for that to work um yeah so uh and<00:51:09.559> then<00:51:09.680> one<00:51:09.839> thing<00:51:10.040> is<00:51:10.400> if<00:51:10.520> you<00:51:10.720> if 00:51:10.789 --> 00:51:10.799 align:start position:0% and then one thing is if you if 00:51:10.799 --> 00:51:12.069 align:start position:0% and then one thing is if you if something's<00:51:11.079> going<00:51:11.319> wrong<00:51:11.480> you<00:51:11.599> can't<00:51:11.799> submit 00:51:12.069 --> 00:51:12.079 align:start position:0% something's going wrong you can't submit 00:51:12.079 --> 00:51:13.910 align:start position:0% something's going wrong you can't submit the<00:51:12.119> blueprint<00:51:12.480> you<00:51:12.599> don't<00:51:12.799> know<00:51:13.079> why<00:51:13.680> I<00:51:13.760> would 00:51:13.910 --> 00:51:13.920 align:start position:0% the blueprint you don't know why I would 00:51:13.920 --> 00:51:16.190 align:start position:0% the blueprint you don't know why I would just<00:51:14.079> save<00:51:14.319> as<00:51:14.480> draft<00:51:14.760> for<00:51:14.960> now<00:51:15.680> and<00:51:15.799> then<00:51:16.040> we 00:51:16.190 --> 00:51:16.200 align:start position:0% just save as draft for now and then we 00:51:16.200 --> 00:51:18.589 align:start position:0% just save as draft for now and then we will<00:51:16.799> maybe<00:51:17.079> send<00:51:17.359> out<00:51:17.599> like<00:51:17.720> a<00:51:17.839> note<00:51:18.119> to<00:51:18.319> folks 00:51:18.589 --> 00:51:18.599 align:start position:0% will maybe send out like a note to folks 00:51:18.599 --> 00:51:21.190 align:start position:0% will maybe send out like a note to folks in<00:51:18.720> the<00:51:19.000> workshop<00:51:20.000> uh<00:51:20.599> saying<00:51:20.839> hey<00:51:21.000> you<00:51:21.079> know 00:51:21.190 --> 00:51:21.200 align:start position:0% in the workshop uh saying hey you know 00:51:21.200 --> 00:51:22.829 align:start position:0% in the workshop uh saying hey you know we<00:51:21.280> fixed<00:51:21.520> some<00:51:21.680> bug<00:51:21.880> where<00:51:22.040> the<00:51:22.160> thing<00:51:22.319> didn't 00:51:22.829 --> 00:51:22.839 align:start position:0% we fixed some bug where the thing didn't 00:51:22.839 --> 00:51:24.710 align:start position:0% we fixed some bug where the thing didn't uh<00:51:22.960> submit<00:51:23.240> the<00:51:23.319> blueprint<00:51:24.000> uh<00:51:24.280> try<00:51:24.440> it<00:51:24.559> again 00:51:24.710 --> 00:51:24.720 align:start position:0% uh submit the blueprint uh try it again 00:51:24.720 --> 00:51:27.109 align:start position:0% uh submit the blueprint uh try it again or<00:51:24.880> something<00:51:25.160> like<00:51:25.359> that<00:51:26.160> um<00:51:26.760> and<00:51:26.880> we'll 00:51:27.109 --> 00:51:27.119 align:start position:0% or something like that um and we'll 00:51:27.119 --> 00:51:29.589 align:start position:0% or something like that um and we'll we'll<00:51:27.240> put<00:51:27.359> a<00:51:27.480> telegram<00:51:28.000> URL<00:51:28.680> up<00:51:28.880> here<00:51:29.400> for 00:51:29.589 --> 00:51:29.599 align:start position:0% we'll put a telegram URL up here for 00:51:29.599 --> 00:51:31.309 align:start position:0% we'll put a telegram URL up here for folks<00:51:29.799> to<00:51:29.960> join<00:51:30.400> and<00:51:30.520> ask<00:51:30.760> questions<00:51:31.040> about 00:51:31.309 --> 00:51:31.319 align:start position:0% folks to join and ask questions about 00:51:31.319 --> 00:51:32.990 align:start position:0% folks to join and ask questions about hey<00:51:31.520> like<00:51:31.839> is<00:51:31.960> my<00:51:32.079> blueprint<00:51:32.440> compiled<00:51:32.839> yet 00:51:32.990 --> 00:51:33.000 align:start position:0% hey like is my blueprint compiled yet 00:51:33.000 --> 00:51:34.990 align:start position:0% hey like is my blueprint compiled yet kind<00:51:33.119> of<00:51:33.240> what's<00:51:33.440> going<00:51:33.599> on<00:51:34.240> and<00:51:34.359> we<00:51:34.559> can<00:51:34.880> we 00:51:34.990 --> 00:51:35.000 align:start position:0% kind of what's going on and we can we 00:51:35.000 --> 00:51:36.789 align:start position:0% kind of what's going on and we can we can<00:51:35.119> make<00:51:35.240> sure<00:51:35.359> we<00:51:35.520> help<00:51:35.720> out<00:51:35.960> there<00:51:36.480> um<00:51:36.640> so 00:51:36.789 --> 00:51:36.799 align:start position:0% can make sure we help out there um so 00:51:36.799 --> 00:51:39.750 align:start position:0% can make sure we help out there um so I'll<00:51:36.960> put<00:51:37.160> up<00:51:37.559> a<00:51:38.559> the<00:51:38.760> QR<00:51:39.040> code<00:51:39.319> let<00:51:39.400> me<00:51:39.520> see<00:51:39.680> if 00:51:39.750 --> 00:51:39.760 align:start position:0% I'll put up a the QR code let me see if 00:51:39.760 --> 00:51:44.789 align:start position:0% I'll put up a the QR code let me see if we<00:51:39.880> have<00:51:40.040> the<00:51:40.160> QR<00:51:40.440> code<00:51:40.760> somewhere 00:51:44.789 --> 00:51:44.799 align:start position:0% 00:51:44.799 --> 00:51:46.589 align:start position:0% um 00:51:46.589 --> 00:51:46.599 align:start position:0% um 00:51:46.599 --> 00:52:20.630 align:start position:0% um um<00:51:47.599> yeah<00:51:48.480> here<00:51:49.000> okay 00:52:20.630 --> 00:52:20.640 align:start position:0% 00:52:20.640 --> 00:52:22.870 align:start position:0% okay<00:52:20.760> so<00:52:20.880> what<00:52:20.960> I've<00:52:21.079> done<00:52:21.240> is<00:52:21.359> I've<00:52:21.520> stuck<00:52:21.920> the 00:52:22.870 --> 00:52:22.880 align:start position:0% okay so what I've done is I've stuck the 00:52:22.880 --> 00:52:26.030 align:start position:0% okay so what I've done is I've stuck the telegram<00:52:23.880> Link<00:52:24.119> in<00:52:24.240> a<00:52:24.440> QR<00:52:24.760> code<00:52:25.000> over<00:52:25.240> here<00:52:25.920> um 00:52:26.030 --> 00:52:26.040 align:start position:0% telegram Link in a QR code over here um 00:52:26.040 --> 00:52:28.470 align:start position:0% telegram Link in a QR code over here um it's<00:52:26.160> the<00:52:26.280> left<00:52:26.640> most<00:52:26.839> one<00:52:27.200> if<00:52:27.359> you<00:52:28.040> scan<00:52:28.319> that 00:52:28.470 --> 00:52:28.480 align:start position:0% it's the left most one if you scan that 00:52:28.480 --> 00:52:30.390 align:start position:0% it's the left most one if you scan that QR<00:52:28.760> code<00:52:29.000> you<00:52:29.079> can<00:52:29.240> ask<00:52:29.400> us<00:52:29.640> questions<00:52:30.160> in<00:52:30.240> the 00:52:30.390 --> 00:52:30.400 align:start position:0% QR code you can ask us questions in the 00:52:30.400 --> 00:52:32.789 align:start position:0% QR code you can ask us questions in the telegram<00:52:30.880> group<00:52:31.240> hey<00:52:31.640> did<00:52:31.760> my<00:52:31.920> patter<00:52:32.240> compile 00:52:32.789 --> 00:52:32.799 align:start position:0% telegram group hey did my patter compile 00:52:32.799 --> 00:52:34.270 align:start position:0% telegram group hey did my patter compile my<00:52:33.040> my<00:52:33.160> blueprint<00:52:33.599> still<00:52:33.760> not<00:52:33.880> working<00:52:34.160> I 00:52:34.270 --> 00:52:34.280 align:start position:0% my my blueprint still not working I 00:52:34.280 --> 00:52:35.549 align:start position:0% my my blueprint still not working I tried<00:52:34.480> to<00:52:34.559> save<00:52:34.760> draft<00:52:35.000> tried<00:52:35.200> to<00:52:35.280> compile 00:52:35.549 --> 00:52:35.559 align:start position:0% tried to save draft tried to compile 00:52:35.559 --> 00:52:37.390 align:start position:0% tried to save draft tried to compile it's<00:52:35.680> not<00:52:35.839> working<00:52:36.119> and<00:52:36.520> we<00:52:36.640> will<00:52:36.839> try<00:52:37.040> to<00:52:37.200> give 00:52:37.390 --> 00:52:37.400 align:start position:0% it's not working and we will try to give 00:52:37.400 --> 00:52:39.309 align:start position:0% it's not working and we will try to give support<00:52:37.920> after<00:52:38.119> the<00:52:38.240> workshop<00:52:38.920> and<00:52:39.079> over<00:52:39.240> the 00:52:39.309 --> 00:52:39.319 align:start position:0% support after the workshop and over the 00:52:39.319 --> 00:52:41.230 align:start position:0% support after the workshop and over the next<00:52:39.520> few<00:52:39.680> weeks<00:52:39.839> and<00:52:40.000> months<00:52:40.720> um<00:52:40.880> my<00:52:41.000> goal<00:52:41.119> is 00:52:41.230 --> 00:52:41.240 align:start position:0% next few weeks and months um my goal is 00:52:41.240 --> 00:52:42.630 align:start position:0% next few weeks and months um my goal is to<00:52:41.319> get<00:52:41.440> everybody<00:52:41.720> who<00:52:41.839> started<00:52:42.119> a<00:52:42.200> blueprint 00:52:42.630 --> 00:52:42.640 align:start position:0% to get everybody who started a blueprint 00:52:42.640 --> 00:52:44.230 align:start position:0% to get everybody who started a blueprint here<00:52:42.760> to<00:52:42.920> compile<00:52:43.240> it<00:52:43.640> there<00:52:43.760> are<00:52:44.000> there<00:52:44.119> might 00:52:44.230 --> 00:52:44.240 align:start position:0% here to compile it there are there might 00:52:44.240 --> 00:52:45.990 align:start position:0% here to compile it there are there might be<00:52:44.319> some<00:52:44.480> bugs<00:52:44.680> on<00:52:44.799> our<00:52:44.960> side<00:52:45.160> like<00:52:45.280> maybe<00:52:45.640> we 00:52:45.990 --> 00:52:46.000 align:start position:0% be some bugs on our side like maybe we 00:52:46.000 --> 00:52:47.630 align:start position:0% be some bugs on our side like maybe we we<00:52:46.119> can<00:52:46.319> make<00:52:46.559> the<00:52:46.839> the<00:52:46.960> clarity<00:52:47.319> of<00:52:47.440> why<00:52:47.559> the 00:52:47.630 --> 00:52:47.640 align:start position:0% we can make the the clarity of why the 00:52:47.640 --> 00:52:50.109 align:start position:0% we can make the the clarity of why the parsing<00:52:48.000> is<00:52:48.160> wrong<00:52:48.640> more<00:52:48.920> clear<00:52:49.760> and<00:52:49.920> things 00:52:50.109 --> 00:52:50.119 align:start position:0% parsing is wrong more clear and things 00:52:50.119 --> 00:52:51.190 align:start position:0% parsing is wrong more clear and things like<00:52:50.240> that<00:52:50.440> and<00:52:50.599> we'll<00:52:50.760> we'll<00:52:50.880> try<00:52:51.000> to<00:52:51.079> make 00:52:51.190 --> 00:52:51.200 align:start position:0% like that and we'll we'll try to make 00:52:51.200 --> 00:52:53.150 align:start position:0% like that and we'll we'll try to make this<00:52:51.319> better<00:52:51.520> over<00:52:51.680> the<00:52:51.799> next<00:52:52.000> few<00:52:52.839> uh<00:52:52.960> weeks 00:52:53.150 --> 00:52:53.160 align:start position:0% this better over the next few uh weeks 00:52:53.160 --> 00:52:54.870 align:start position:0% this better over the next few uh weeks and<00:52:53.319> months<00:52:54.000> um<00:52:54.119> but<00:52:54.240> at<00:52:54.319> least<00:52:54.480> it<00:52:54.559> sound<00:52:54.760> like 00:52:54.870 --> 00:52:54.880 align:start position:0% and months um but at least it sound like 00:52:54.880 --> 00:52:56.030 align:start position:0% and months um but at least it sound like some<00:52:55.040> people<00:52:55.200> were<00:52:55.319> able<00:52:55.520> to<00:52:55.599> fill<00:52:55.760> in<00:52:55.839> all<00:52:55.920> the 00:52:56.030 --> 00:52:56.040 align:start position:0% some people were able to fill in all the 00:52:56.040 --> 00:52:58.270 align:start position:0% some people were able to fill in all the fields<00:52:56.240> and<00:52:56.559> get<00:52:56.680> that<00:52:56.760> to<00:52:56.920> work 00:52:58.270 --> 00:52:58.280 align:start position:0% fields and get that to work 00:52:58.280 --> 00:53:02.349 align:start position:0% fields and get that to work um<00:52:59.280> yeah<00:53:00.280> uh<00:53:01.280> cool<00:53:01.599> so<00:53:01.799> yeah<00:53:01.880> if<00:53:01.960> you<00:53:02.079> have<00:53:02.200> more 00:53:02.349 --> 00:53:02.359 align:start position:0% um yeah uh cool so yeah if you have more 00:53:02.359 --> 00:53:03.589 align:start position:0% um yeah uh cool so yeah if you have more questions<00:53:02.640> I<00:53:02.720> would<00:53:02.839> send<00:53:03.000> to<00:53:03.079> the<00:53:03.160> telegram 00:53:03.589 --> 00:53:03.599 align:start position:0% questions I would send to the telegram 00:53:03.599 --> 00:53:06.750 align:start position:0% questions I would send to the telegram but<00:53:03.680> we're<00:53:03.799> going<00:53:03.880> to<00:53:04.319> Pivot<00:53:05.319> uh<00:53:05.440> a<00:53:05.599> little<00:53:05.799> bit 00:53:06.750 --> 00:53:06.760 align:start position:0% but we're going to Pivot uh a little bit 00:53:06.760 --> 00:53:08.990 align:start position:0% but we're going to Pivot uh a little bit um<00:53:07.480> and<00:53:07.720> maybe<00:53:08.000> one<00:53:08.160> thing<00:53:08.440> I'm<00:53:08.599> I'm<00:53:08.720> curious 00:53:08.990 --> 00:53:09.000 align:start position:0% um and maybe one thing I'm I'm curious 00:53:09.000 --> 00:53:11.190 align:start position:0% um and maybe one thing I'm I'm curious about<00:53:09.119> pivoting<00:53:09.440> too<00:53:09.680> is<00:53:10.000> should<00:53:10.280> we<00:53:11.079> I'm 00:53:11.190 --> 00:53:11.200 align:start position:0% about pivoting too is should we I'm 00:53:11.200 --> 00:53:13.150 align:start position:0% about pivoting too is should we I'm wondering<00:53:11.520> if<00:53:11.599> people<00:53:11.880> be<00:53:12.000> more<00:53:12.200> excited<00:53:12.960> to 00:53:13.150 --> 00:53:13.160 align:start position:0% wondering if people be more excited to 00:53:13.160 --> 00:53:15.309 align:start position:0% wondering if people be more excited to build<00:53:13.359> a<00:53:13.520> front<00:53:13.760> end<00:53:14.400> in<00:53:14.599> which<00:53:14.760> they<00:53:14.920> import 00:53:15.309 --> 00:53:15.319 align:start position:0% build a front end in which they import 00:53:15.319 --> 00:53:17.390 align:start position:0% build a front end in which they import this<00:53:15.520> proof<00:53:16.000> and<00:53:16.200> then<00:53:16.559> now<00:53:16.839> do<00:53:17.000> something<00:53:17.200> on 00:53:17.390 --> 00:53:17.400 align:start position:0% this proof and then now do something on 00:53:17.400 --> 00:53:18.950 align:start position:0% this proof and then now do something on top<00:53:17.520> of<00:53:17.720> that<00:53:18.079> or<00:53:18.359> people<00:53:18.520> will<00:53:18.640> be<00:53:18.799> more 00:53:18.950 --> 00:53:18.960 align:start position:0% top of that or people will be more 00:53:18.960 --> 00:53:21.630 align:start position:0% top of that or people will be more excited<00:53:19.280> to<00:53:19.359> do<00:53:19.640> solidity<00:53:20.640> uh<00:53:20.760> calling<00:53:21.079> zkl 00:53:21.630 --> 00:53:21.640 align:start position:0% excited to do solidity uh calling zkl 00:53:21.640 --> 00:53:23.829 align:start position:0% excited to do solidity uh calling zkl proofs<00:53:21.960> on<00:53:22.119> solidity<00:53:22.760> with<00:53:22.920> sent<00:53:23.240> emails<00:53:23.680> so 00:53:23.829 --> 00:53:23.839 align:start position:0% proofs on solidity with sent emails so 00:53:23.839 --> 00:53:25.789 align:start position:0% proofs on solidity with sent emails so concretely<00:53:24.640> you<00:53:24.760> know<00:53:24.880> you<00:53:25.040> do<00:53:25.280> something 00:53:25.789 --> 00:53:25.799 align:start position:0% concretely you know you do something 00:53:25.799 --> 00:53:27.309 align:start position:0% concretely you know you do something like<00:53:26.319> um 00:53:27.309 --> 00:53:27.319 align:start position:0% like um 00:53:27.319 --> 00:53:30.750 align:start position:0% like um um<00:53:28.319> our<00:53:28.480> email<00:53:28.720> based<00:53:28.960> account<00:53:29.440> recovery<00:53:30.440> um 00:53:30.750 --> 00:53:30.760 align:start position:0% um our email based account recovery um 00:53:30.760 --> 00:53:32.390 align:start position:0% um our email based account recovery um in<00:53:30.960> which<00:53:31.359> you<00:53:31.520> know<00:53:31.720> receiveing<00:53:32.079> email 00:53:32.390 --> 00:53:32.400 align:start position:0% in which you know receiveing email 00:53:32.400 --> 00:53:33.510 align:start position:0% in which you know receiveing email saying<00:53:32.680> do<00:53:32.799> you<00:53:32.880> want<00:53:32.960> to<00:53:33.079> recover<00:53:33.400> the 00:53:33.510 --> 00:53:33.520 align:start position:0% saying do you want to recover the 00:53:33.520 --> 00:53:35.270 align:start position:0% saying do you want to recover the account<00:53:33.720> to<00:53:33.880> some<00:53:34.160> some<00:53:34.359> address<00:53:34.920> you<00:53:35.040> receive 00:53:35.270 --> 00:53:35.280 align:start position:0% account to some some address you receive 00:53:35.280 --> 00:53:37.390 align:start position:0% account to some some address you receive an<00:53:35.400> email<00:53:35.760> you<00:53:35.920> reply<00:53:36.200> to<00:53:36.359> it<00:53:36.559> and<00:53:36.680> then<00:53:36.920> that 00:53:37.390 --> 00:53:37.400 align:start position:0% an email you reply to it and then that 00:53:37.400 --> 00:53:39.470 align:start position:0% an email you reply to it and then that transaction<00:53:37.920> Triggers<00:53:38.240> on<00:53:38.440> chain<00:53:39.240> um<00:53:39.319> so<00:53:39.440> I'm 00:53:39.470 --> 00:53:39.480 align:start position:0% transaction Triggers on chain um so I'm 00:53:39.480 --> 00:53:40.630 align:start position:0% transaction Triggers on chain um so I'm just<00:53:39.559> going<00:53:39.640> to<00:53:39.720> do<00:53:39.799> a<00:53:39.880> quick<00:53:40.000> PLL<00:53:40.240> maybe<00:53:40.480> raise 00:53:40.630 --> 00:53:40.640 align:start position:0% just going to do a quick PLL maybe raise 00:53:40.640 --> 00:53:42.950 align:start position:0% just going to do a quick PLL maybe raise your<00:53:40.799> hand<00:53:41.359> if<00:53:41.440> you<00:53:41.640> prefer<00:53:42.079> JavaScript<00:53:42.680> to 00:53:42.950 --> 00:53:42.960 align:start position:0% your hand if you prefer JavaScript to 00:53:42.960 --> 00:53:44.670 align:start position:0% your hand if you prefer JavaScript to solidity<00:53:43.680> and<00:53:43.760> you<00:53:43.880> want<00:53:44.000> to<00:53:44.119> go<00:53:44.280> over<00:53:44.480> like<00:53:44.559> a 00:53:44.670 --> 00:53:44.680 align:start position:0% solidity and you want to go over like a 00:53:44.680 --> 00:53:46.150 align:start position:0% solidity and you want to go over like a JavaScript<00:53:45.119> version<00:53:45.319> of<00:53:45.440> implementing<00:53:45.920> these 00:53:46.150 --> 00:53:46.160 align:start position:0% JavaScript version of implementing these 00:53:46.160 --> 00:53:49.309 align:start position:0% JavaScript version of implementing these proofs<00:53:47.160> okay<00:53:47.799> like<00:53:48.000> maybe<00:53:48.359> six<00:53:48.640> seven<00:53:48.880> people 00:53:49.309 --> 00:53:49.319 align:start position:0% proofs okay like maybe six seven people 00:53:49.319 --> 00:53:51.230 align:start position:0% proofs okay like maybe six seven people okay<00:53:49.880> um<00:53:50.040> raise<00:53:50.200> your<00:53:50.359> hand<00:53:50.599> if<00:53:50.680> you<00:53:50.920> prefer 00:53:51.230 --> 00:53:51.240 align:start position:0% okay um raise your hand if you prefer 00:53:51.240 --> 00:53:53.150 align:start position:0% okay um raise your hand if you prefer solidity<00:53:52.160> and<00:53:52.280> you<00:53:52.359> want<00:53:52.520> to<00:53:52.640> go<00:53:52.799> over<00:53:53.000> a 00:53:53.150 --> 00:53:53.160 align:start position:0% solidity and you want to go over a 00:53:53.160 --> 00:53:55.510 align:start position:0% solidity and you want to go over a version<00:53:53.520> of<00:53:53.720> triggering<00:53:54.359> transactions<00:53:55.359> in 00:53:55.510 --> 00:53:55.520 align:start position:0% version of triggering transactions in 00:53:55.520 --> 00:53:57.390 align:start position:0% version of triggering transactions in solidity<00:53:55.960> directly<00:53:56.480> okay<00:53:56.680> that's<00:53:56.920> like<00:53:57.079> 20 00:53:57.390 --> 00:53:57.400 align:start position:0% solidity directly okay that's like 20 00:53:57.400 --> 00:53:58.950 align:start position:0% solidity directly okay that's like 20 people<00:53:57.760> okay<00:53:57.880> so<00:53:58.040> I<00:53:58.160> think<00:53:58.640> what<00:53:58.720> we're<00:53:58.880> going 00:53:58.950 --> 00:53:58.960 align:start position:0% people okay so I think what we're going 00:53:58.960 --> 00:54:00.910 align:start position:0% people okay so I think what we're going to<00:53:59.040> do<00:53:59.200> is<00:53:59.280> we're<00:53:59.480> going<00:53:59.559> to<00:54:00.040> S<00:54:00.440> JavaScript 00:54:00.910 --> 00:54:00.920 align:start position:0% to do is we're going to S JavaScript 00:54:00.920 --> 00:54:02.990 align:start position:0% to do is we're going to S JavaScript people<00:54:01.359> um<00:54:01.520> I'll<00:54:01.680> put<00:54:01.799> a<00:54:01.920> link<00:54:02.160> to<00:54:02.400> the 00:54:02.990 --> 00:54:03.000 align:start position:0% people um I'll put a link to the 00:54:03.000 --> 00:54:04.789 align:start position:0% people um I'll put a link to the JavaScript<00:54:03.480> demo<00:54:04.040> after<00:54:04.240> we're<00:54:04.480> done<00:54:04.640> with 00:54:04.789 --> 00:54:04.799 align:start position:0% JavaScript demo after we're done with 00:54:04.799 --> 00:54:06.430 align:start position:0% JavaScript demo after we're done with this<00:54:05.000> and<00:54:05.119> the<00:54:05.280> docs<00:54:05.640> and<00:54:05.720> you<00:54:05.839> can<00:54:06.000> try<00:54:06.200> doing 00:54:06.430 --> 00:54:06.440 align:start position:0% this and the docs and you can try doing 00:54:06.440 --> 00:54:08.270 align:start position:0% this and the docs and you can try doing that<00:54:06.599> yourself<00:54:07.480> um<00:54:07.599> but<00:54:07.720> we'll<00:54:07.920> probably 00:54:08.270 --> 00:54:08.280 align:start position:0% that yourself um but we'll probably 00:54:08.280 --> 00:54:11.870 align:start position:0% that yourself um but we'll probably focus<00:54:08.559> on<00:54:08.720> solidity<00:54:09.480> this<00:54:09.640> time<00:54:10.000> around 00:54:11.870 --> 00:54:11.880 align:start position:0% focus on solidity this time around 00:54:11.880 --> 00:54:15.870 align:start position:0% focus on solidity this time around um<00:54:12.880> cool<00:54:13.960> um<00:54:14.960> yeah<00:54:15.160> and<00:54:15.400> again<00:54:15.559> if<00:54:15.640> you<00:54:15.720> have 00:54:15.870 --> 00:54:15.880 align:start position:0% um cool um yeah and again if you have 00:54:15.880 --> 00:54:17.349 align:start position:0% um cool um yeah and again if you have more<00:54:16.079> questions<00:54:16.559> like<00:54:16.799> if<00:54:16.880> you<00:54:17.000> hit<00:54:17.119> up<00:54:17.240> our 00:54:17.349 --> 00:54:17.359 align:start position:0% more questions like if you hit up our 00:54:17.359 --> 00:54:18.349 align:start position:0% more questions like if you hit up our telegram<00:54:17.720> you're<00:54:17.839> like<00:54:18.000> look<00:54:18.119> I<00:54:18.240> really 00:54:18.349 --> 00:54:18.359 align:start position:0% telegram you're like look I really 00:54:18.359 --> 00:54:19.470 align:start position:0% telegram you're like look I really wanted<00:54:18.640> the<00:54:18.760> JavaScript<00:54:19.200> part<00:54:19.319> of<00:54:19.400> the 00:54:19.470 --> 00:54:19.480 align:start position:0% wanted the JavaScript part of the 00:54:19.480 --> 00:54:21.150 align:start position:0% wanted the JavaScript part of the workshop<00:54:20.280> uh<00:54:20.440> where's<00:54:20.640> the<00:54:20.760> link<00:54:20.920> for<00:54:21.040> the 00:54:21.150 --> 00:54:21.160 align:start position:0% workshop uh where's the link for the 00:54:21.160 --> 00:54:22.630 align:start position:0% workshop uh where's the link for the docs<00:54:21.359> the<00:54:21.480> SDK<00:54:21.880> whatever<00:54:22.160> we'll<00:54:22.359> we'll<00:54:22.520> send 00:54:22.630 --> 00:54:22.640 align:start position:0% docs the SDK whatever we'll we'll send 00:54:22.640 --> 00:54:24.150 align:start position:0% docs the SDK whatever we'll we'll send it<00:54:22.720> to<00:54:22.839> you<00:54:22.960> so<00:54:23.040> the<00:54:23.160> telegram<00:54:23.559> is<00:54:23.720> is<00:54:23.880> really<00:54:24.040> a 00:54:24.150 --> 00:54:24.160 align:start position:0% it to you so the telegram is is really a 00:54:24.160 --> 00:54:26.589 align:start position:0% it to you so the telegram is is really a good<00:54:24.319> one<00:54:25.240> um<00:54:25.880> okay<00:54:26.040> we're<00:54:26.160> going<00:54:26.240> to<00:54:26.520> we're 00:54:26.589 --> 00:54:26.599 align:start position:0% good one um okay we're going to we're 00:54:26.599 --> 00:54:28.349 align:start position:0% good one um okay we're going to we're going<00:54:26.680> to<00:54:26.760> Pivot<00:54:27.040> a<00:54:27.119> little<00:54:27.280> bit<00:54:27.640> switch<00:54:28.040> gears 00:54:28.349 --> 00:54:28.359 align:start position:0% going to Pivot a little bit switch gears 00:54:28.359 --> 00:54:29.950 align:start position:0% going to Pivot a little bit switch gears if<00:54:28.440> your<00:54:28.559> pattern<00:54:28.799> didn't<00:54:29.079> compile<00:54:29.640> save<00:54:29.839> it 00:54:29.950 --> 00:54:29.960 align:start position:0% if your pattern didn't compile save it 00:54:29.960 --> 00:54:32.390 align:start position:0% if your pattern didn't compile save it as<00:54:30.119> draft<00:54:30.480> and<00:54:30.559> we'll<00:54:30.720> come<00:54:30.880> back<00:54:31.000> to<00:54:31.119> it<00:54:31.400> later 00:54:32.390 --> 00:54:32.400 align:start position:0% as draft and we'll come back to it later 00:54:32.400 --> 00:54:34.309 align:start position:0% as draft and we'll come back to it later um<00:54:32.760> so<00:54:33.000> just<00:54:33.079> you<00:54:33.200> know<00:54:33.400> H<00:54:33.599> hit<00:54:33.839> hit<00:54:34.000> save<00:54:34.160> as 00:54:34.309 --> 00:54:34.319 align:start position:0% um so just you know H hit hit save as 00:54:34.319 --> 00:54:37.390 align:start position:0% um so just you know H hit hit save as draft<00:54:34.599> down<00:54:34.799> here<00:54:35.680> um<00:54:36.480> and<00:54:36.760> we<00:54:36.839> can<00:54:37.000> help<00:54:37.200> give 00:54:37.390 --> 00:54:37.400 align:start position:0% draft down here um and we can help give 00:54:37.400 --> 00:54:39.829 align:start position:0% draft down here um and we can help give support<00:54:37.920> on<00:54:38.040> the<00:54:38.200> telegram<00:54:38.880> and<00:54:39.280> okay 00:54:39.829 --> 00:54:39.839 align:start position:0% support on the telegram and okay 00:54:39.839 --> 00:54:43.670 align:start position:0% support on the telegram and okay Switching<00:54:40.480> gears<00:54:40.839> a<00:54:40.960> little<00:54:41.200> bit<00:54:42.280> um<00:54:43.280> so<00:54:43.520> so 00:54:43.670 --> 00:54:43.680 align:start position:0% Switching gears a little bit um so so 00:54:43.680 --> 00:54:45.589 align:start position:0% Switching gears a little bit um so so maybe<00:54:44.040> briefly<00:54:44.480> before<00:54:44.720> we<00:54:45.119> even<00:54:45.359> like<00:54:45.480> kind 00:54:45.589 --> 00:54:45.599 align:start position:0% maybe briefly before we even like kind 00:54:45.599 --> 00:54:47.069 align:start position:0% maybe briefly before we even like kind of<00:54:45.720> dive<00:54:45.920> into<00:54:46.160> that<00:54:46.520> I'll<00:54:46.640> give<00:54:46.760> a<00:54:46.880> brief 00:54:47.069 --> 00:54:47.079 align:start position:0% of dive into that I'll give a brief 00:54:47.079 --> 00:54:49.349 align:start position:0% of dive into that I'll give a brief presentation<00:54:47.520> of<00:54:47.760> what<00:54:47.960> exactly<00:54:48.799> are<00:54:48.960> we<00:54:49.160> even 00:54:49.349 --> 00:54:49.359 align:start position:0% presentation of what exactly are we even 00:54:49.359 --> 00:54:52.230 align:start position:0% presentation of what exactly are we even doing<00:54:49.640> with<00:54:49.760> this<00:54:49.880> solidity<00:54:50.799> style 00:54:52.230 --> 00:54:52.240 align:start position:0% doing with this solidity style 00:54:52.240 --> 00:54:55.430 align:start position:0% doing with this solidity style transactions<00:54:53.559> um<00:54:54.559> so<00:54:54.720> this<00:54:54.799> will<00:54:54.960> be<00:54:55.079> maybe 00:54:55.430 --> 00:54:55.440 align:start position:0% transactions um so this will be maybe 00:54:55.440 --> 00:54:56.870 align:start position:0% transactions um so this will be maybe like<00:54:55.520> a<00:54:55.640> 2<00:54:55.880> three<00:54:56.000> minute<00:54:56.400> overview<00:54:56.720> and<00:54:56.799> then 00:54:56.870 --> 00:54:56.880 align:start position:0% like a 2 three minute overview and then 00:54:56.880 --> 00:54:58.670 align:start position:0% like a 2 three minute overview and then we'll<00:54:57.040> dive<00:54:57.280> into<00:54:57.559> actually<00:54:57.760> building<00:54:58.040> this 00:54:58.670 --> 00:54:58.680 align:start position:0% we'll dive into actually building this 00:54:58.680 --> 00:55:00.990 align:start position:0% we'll dive into actually building this ourselves<00:54:59.680> uh<00:54:59.799> so<00:55:00.000> so<00:55:00.200> far<00:55:00.520> what<00:55:00.640> we've<00:55:00.839> done 00:55:00.990 --> 00:55:01.000 align:start position:0% ourselves uh so so far what we've done 00:55:01.000 --> 00:55:03.390 align:start position:0% ourselves uh so so far what we've done in<00:55:01.079> the<00:55:01.200> workshop<00:55:01.720> is<00:55:01.920> proving<00:55:02.559> emails<00:55:03.000> you've 00:55:03.390 --> 00:55:03.400 align:start position:0% in the workshop is proving emails you've 00:55:03.400 --> 00:55:06.430 align:start position:0% in the workshop is proving emails you've received<00:55:03.640> in<00:55:03.720> your<00:55:04.280> inbox<00:55:05.280> um<00:55:06.079> you<00:55:06.200> know 00:55:06.430 --> 00:55:06.440 align:start position:0% received in your inbox um you know 00:55:06.440 --> 00:55:07.789 align:start position:0% received in your inbox um you know there's<00:55:06.640> all<00:55:06.760> sorts<00:55:07.000> of<00:55:07.119> weird<00:55:07.319> emails<00:55:07.720> but 00:55:07.789 --> 00:55:07.799 align:start position:0% there's all sorts of weird emails but 00:55:07.799 --> 00:55:09.150 align:start position:0% there's all sorts of weird emails but you<00:55:07.880> would<00:55:08.079> imagine<00:55:08.480> maybe<00:55:08.720> you<00:55:08.839> want<00:55:08.960> to 00:55:09.150 --> 00:55:09.160 align:start position:0% you would imagine maybe you want to 00:55:09.160 --> 00:55:11.270 align:start position:0% you would imagine maybe you want to trigger<00:55:09.799> an<00:55:09.960> onchain<00:55:10.400> smart<00:55:10.760> contract<00:55:11.160> by 00:55:11.270 --> 00:55:11.280 align:start position:0% trigger an onchain smart contract by 00:55:11.280 --> 00:55:14.069 align:start position:0% trigger an onchain smart contract by sending<00:55:11.640> an<00:55:11.839> email<00:55:12.559> so<00:55:12.680> you<00:55:12.799> have<00:55:12.960> an<00:55:13.079> email<00:55:13.920> a 00:55:14.069 --> 00:55:14.079 align:start position:0% sending an email so you have an email a 00:55:14.079 --> 00:55:15.789 align:start position:0% sending an email so you have an email a smart<00:55:14.319> contract<00:55:14.680> controlled<00:55:15.119> by<00:55:15.240> an<00:55:15.400> email 00:55:15.789 --> 00:55:15.799 align:start position:0% smart contract controlled by an email 00:55:15.799 --> 00:55:17.549 align:start position:0% smart contract controlled by an email address<00:55:16.599> right<00:55:16.720> so<00:55:16.839> this<00:55:16.960> allows<00:55:17.200> you<00:55:17.319> to<00:55:17.440> do 00:55:17.549 --> 00:55:17.559 align:start position:0% address right so this allows you to do 00:55:17.559 --> 00:55:19.109 align:start position:0% address right so this allows you to do something<00:55:17.839> like<00:55:18.040> account<00:55:18.319> recovery<00:55:19.040> where 00:55:19.109 --> 00:55:19.119 align:start position:0% something like account recovery where 00:55:19.119 --> 00:55:20.549 align:start position:0% something like account recovery where you<00:55:19.240> can<00:55:19.359> add<00:55:19.520> emails<00:55:19.839> as<00:55:20.000> Guardians<00:55:20.359> to<00:55:20.440> a 00:55:20.549 --> 00:55:20.559 align:start position:0% you can add emails as Guardians to a 00:55:20.559 --> 00:55:21.910 align:start position:0% you can add emails as Guardians to a Smart<00:55:20.799> wallet<00:55:21.079> and<00:55:21.200> then<00:55:21.319> use<00:55:21.520> those<00:55:21.680> email 00:55:21.910 --> 00:55:21.920 align:start position:0% Smart wallet and then use those email 00:55:21.920 --> 00:55:24.870 align:start position:0% Smart wallet and then use those email addresses<00:55:22.280> to<00:55:22.440> recover<00:55:22.839> that<00:55:23.280> account<00:55:24.280> um<00:55:24.799> you 00:55:24.870 --> 00:55:24.880 align:start position:0% addresses to recover that account um you 00:55:24.880 --> 00:55:26.950 align:start position:0% addresses to recover that account um you can<00:55:25.079> have<00:55:25.280> emails<00:55:25.720> on<00:55:25.880> Multi<00:55:26.359> Sig<00:55:26.559> or<00:55:26.720> directly 00:55:26.950 --> 00:55:26.960 align:start position:0% can have emails on Multi Sig or directly 00:55:26.960 --> 00:55:28.710 align:start position:0% can have emails on Multi Sig or directly on<00:55:27.039> a<00:55:27.200> safe<00:55:27.440> you<00:55:27.520> add<00:55:27.680> an<00:55:27.799> email<00:55:28.359> and<00:55:28.440> then<00:55:28.599> that 00:55:28.710 --> 00:55:28.720 align:start position:0% on a safe you add an email and then that 00:55:28.720 --> 00:55:30.109 align:start position:0% on a safe you add an email and then that email<00:55:29.000> recovers<00:55:29.440> the 00:55:30.109 --> 00:55:30.119 align:start position:0% email recovers the 00:55:30.119 --> 00:55:32.710 align:start position:0% email recovers the account<00:55:31.119> you<00:55:31.200> can<00:55:31.359> have<00:55:31.520> login<00:55:31.880> with<00:55:32.039> emails 00:55:32.710 --> 00:55:32.720 align:start position:0% account you can have login with emails 00:55:32.720 --> 00:55:33.910 align:start position:0% account you can have login with emails where<00:55:32.880> now<00:55:33.039> you<00:55:33.160> can<00:55:33.319> say<00:55:33.520> you<00:55:33.599> know<00:55:33.680> someone's 00:55:33.910 --> 00:55:33.920 align:start position:0% where now you can say you know someone's 00:55:33.920 --> 00:55:35.710 align:start position:0% where now you can say you know someone's put<00:55:34.039> an<00:55:34.119> email<00:55:34.359> in<00:55:34.480> an<00:55:34.599> interface<00:55:35.079> and<00:55:35.240> they've 00:55:35.710 --> 00:55:35.720 align:start position:0% put an email in an interface and they've 00:55:35.720 --> 00:55:38.430 align:start position:0% put an email in an interface and they've kind<00:55:35.839> of<00:55:36.039> imported<00:55:36.599> that<00:55:37.440> uh<00:55:37.599> that<00:55:37.760> login<00:55:38.359> and 00:55:38.430 --> 00:55:38.440 align:start position:0% kind of imported that uh that login and 00:55:38.440 --> 00:55:39.430 align:start position:0% kind of imported that uh that login and you<00:55:38.520> can<00:55:38.680> have<00:55:38.799> something<00:55:39.000> like<00:55:39.119> an<00:55:39.200> email 00:55:39.430 --> 00:55:39.440 align:start position:0% you can have something like an email 00:55:39.440 --> 00:55:40.910 align:start position:0% you can have something like an email wallet<00:55:39.720> where<00:55:39.839> you<00:55:40.000> receive<00:55:40.319> tokens<00:55:40.640> directly 00:55:40.910 --> 00:55:40.920 align:start position:0% wallet where you receive tokens directly 00:55:40.920 --> 00:55:43.150 align:start position:0% wallet where you receive tokens directly to<00:55:41.079> email<00:55:41.720> and<00:55:41.839> these<00:55:41.960> are<00:55:42.079> the<00:55:42.280> four<00:55:42.720> examples 00:55:43.150 --> 00:55:43.160 align:start position:0% to email and these are the four examples 00:55:43.160 --> 00:55:44.309 align:start position:0% to email and these are the four examples we've<00:55:43.319> shown<00:55:43.599> of<00:55:43.760> what<00:55:43.920> happens<00:55:44.119> when<00:55:44.240> an 00:55:44.309 --> 00:55:44.319 align:start position:0% we've shown of what happens when an 00:55:44.319 --> 00:55:46.630 align:start position:0% we've shown of what happens when an email<00:55:44.559> address<00:55:44.799> controls<00:55:45.079> a<00:55:45.200> smart<00:55:45.640> contract 00:55:46.630 --> 00:55:46.640 align:start position:0% email address controls a smart contract 00:55:46.640 --> 00:55:49.710 align:start position:0% email address controls a smart contract um<00:55:47.559> but<00:55:47.799> you<00:55:47.920> know<00:55:48.480> uh<00:55:49.000> you<00:55:49.119> can<00:55:49.280> either<00:55:49.520> use 00:55:49.710 --> 00:55:49.720 align:start position:0% um but you know uh you can either use 00:55:49.720 --> 00:55:51.349 align:start position:0% um but you know uh you can either use the<00:55:49.839> SDK<00:55:50.400> we've<00:55:50.559> put<00:55:50.680> out<00:55:50.799> for<00:55:50.920> these<00:55:51.039> four<00:55:51.240> and 00:55:51.349 --> 00:55:51.359 align:start position:0% the SDK we've put out for these four and 00:55:51.359 --> 00:55:52.589 align:start position:0% the SDK we've put out for these four and integrated<00:55:51.720> into<00:55:51.880> your<00:55:52.039> app<00:55:52.200> and<00:55:52.319> I'll<00:55:52.480> I'll 00:55:52.589 --> 00:55:52.599 align:start position:0% integrated into your app and I'll I'll 00:55:52.599 --> 00:55:54.190 align:start position:0% integrated into your app and I'll I'll put<00:55:52.720> out<00:55:52.839> the<00:55:52.920> QR<00:55:53.160> codes<00:55:53.359> for<00:55:53.559> those<00:55:53.960> or<00:55:54.079> you 00:55:54.190 --> 00:55:54.200 align:start position:0% put out the QR codes for those or you 00:55:54.200 --> 00:55:55.870 align:start position:0% put out the QR codes for those or you can<00:55:54.319> build<00:55:54.559> your<00:55:54.720> own<00:55:55.079> custom<00:55:55.400> kind<00:55:55.559> of<00:55:55.680> email 00:55:55.870 --> 00:55:55.880 align:start position:0% can build your own custom kind of email 00:55:55.880 --> 00:55:59.309 align:start position:0% can build your own custom kind of email trigger<00:55:56.720> transaction<00:55:57.880> um<00:55:58.880> what<00:55:59.000> does<00:55:59.160> this 00:55:59.309 --> 00:55:59.319 align:start position:0% trigger transaction um what does this 00:55:59.319 --> 00:56:01.510 align:start position:0% trigger transaction um what does this like<00:55:59.440> concretely<00:55:59.880> look<00:56:00.079> like<00:56:00.960> uh<00:56:01.280> you'll 00:56:01.510 --> 00:56:01.520 align:start position:0% like concretely look like uh you'll 00:56:01.520 --> 00:56:03.069 align:start position:0% like concretely look like uh you'll receive<00:56:01.799> an<00:56:01.960> email<00:56:02.359> saying<00:56:02.559> you<00:56:02.680> know<00:56:02.880> do<00:56:02.960> you 00:56:03.069 --> 00:56:03.079 align:start position:0% receive an email saying you know do you 00:56:03.079 --> 00:56:05.190 align:start position:0% receive an email saying you know do you want<00:56:03.280> to<00:56:03.559> say<00:56:04.000> recover<00:56:04.400> your<00:56:04.599> account<00:56:04.880> or<00:56:05.039> sign 00:56:05.190 --> 00:56:05.200 align:start position:0% want to say recover your account or sign 00:56:05.200 --> 00:56:07.390 align:start position:0% want to say recover your account or sign on<00:56:05.319> this<00:56:05.480> multisig<00:56:06.280> or<00:56:06.680> you<00:56:06.799> know<00:56:06.920> log<00:56:07.160> into 00:56:07.390 --> 00:56:07.400 align:start position:0% on this multisig or you know log into 00:56:07.400 --> 00:56:08.870 align:start position:0% on this multisig or you know log into this<00:56:07.559> website<00:56:08.200> and<00:56:08.319> all<00:56:08.400> you<00:56:08.480> have<00:56:08.559> to<00:56:08.640> do<00:56:08.760> is 00:56:08.870 --> 00:56:08.880 align:start position:0% this website and all you have to do is 00:56:08.880 --> 00:56:10.349 align:start position:0% this website and all you have to do is reply<00:56:09.200> confirm<00:56:09.559> and<00:56:09.640> it<00:56:09.760> lets<00:56:09.920> you<00:56:10.039> interact 00:56:10.349 --> 00:56:10.359 align:start position:0% reply confirm and it lets you interact 00:56:10.359 --> 00:56:11.710 align:start position:0% reply confirm and it lets you interact with<00:56:10.440> the<00:56:10.559> smart<00:56:10.799> contract<00:56:11.160> directly<00:56:11.599> when 00:56:11.710 --> 00:56:11.720 align:start position:0% with the smart contract directly when 00:56:11.720 --> 00:56:14.470 align:start position:0% with the smart contract directly when you<00:56:11.880> reply<00:56:12.640> we<00:56:12.760> make<00:56:12.960> a<00:56:13.079> ZK<00:56:13.480> proof<00:56:13.960> we<00:56:14.160> receive 00:56:14.470 --> 00:56:14.480 align:start position:0% you reply we make a ZK proof we receive 00:56:14.480 --> 00:56:15.950 align:start position:0% you reply we make a ZK proof we receive that<00:56:14.680> email<00:56:15.000> we<00:56:15.079> make<00:56:15.200> a<00:56:15.319> ZK<00:56:15.559> proof<00:56:15.760> of<00:56:15.839> that 00:56:15.950 --> 00:56:15.960 align:start position:0% that email we make a ZK proof of that 00:56:15.960 --> 00:56:17.950 align:start position:0% that email we make a ZK proof of that signature<00:56:16.280> and<00:56:16.359> we<00:56:16.480> prove<00:56:16.680> it<00:56:16.799> on<00:56:16.960> chain<00:56:17.839> um 00:56:17.950 --> 00:56:17.960 align:start position:0% signature and we prove it on chain um 00:56:17.960 --> 00:56:19.829 align:start position:0% signature and we prove it on chain um this<00:56:18.119> email<00:56:18.400> is<00:56:18.640> like<00:56:19.000> I've<00:56:19.160> moved<00:56:19.440> the<00:56:19.599> data 00:56:19.829 --> 00:56:19.839 align:start position:0% this email is like I've moved the data 00:56:19.839 --> 00:56:21.069 align:start position:0% this email is like I've moved the data that's<00:56:20.039> actually<00:56:20.319> being<00:56:20.480> proved<00:56:20.760> into<00:56:20.960> the 00:56:21.069 --> 00:56:21.079 align:start position:0% that's actually being proved into the 00:56:21.079 --> 00:56:22.589 align:start position:0% that's actually being proved into the subject<00:56:21.359> so<00:56:21.440> we<00:56:21.520> can<00:56:21.640> all<00:56:21.760> read<00:56:21.960> it<00:56:22.359> but<00:56:22.480> when 00:56:22.589 --> 00:56:22.599 align:start position:0% subject so we can all read it but when 00:56:22.599 --> 00:56:24.270 align:start position:0% subject so we can all read it but when you<00:56:22.799> actually<00:56:23.039> try<00:56:23.280> our<00:56:23.520> code<00:56:23.920> this<00:56:24.000> will<00:56:24.160> all 00:56:24.270 --> 00:56:24.280 align:start position:0% you actually try our code this will all 00:56:24.280 --> 00:56:26.910 align:start position:0% you actually try our code this will all be<00:56:24.400> embedded<00:56:24.799> into<00:56:24.960> the<00:56:25.119> body<00:56:26.039> um<00:56:26.559> but<00:56:26.680> you<00:56:26.799> can 00:56:26.910 --> 00:56:26.920 align:start position:0% be embedded into the body um but you can 00:56:26.920 --> 00:56:28.589 align:start position:0% be embedded into the body um but you can see<00:56:27.079> if<00:56:27.160> you<00:56:27.319> read<00:56:27.520> this<00:56:27.760> like<00:56:28.119> the<00:56:28.240> command 00:56:28.589 --> 00:56:28.599 align:start position:0% see if you read this like the command 00:56:28.599 --> 00:56:30.549 align:start position:0% see if you read this like the command you're<00:56:28.920> actually<00:56:29.240> signing<00:56:29.799> by<00:56:29.960> replying<00:56:30.359> to 00:56:30.549 --> 00:56:30.559 align:start position:0% you're actually signing by replying to 00:56:30.559 --> 00:56:32.829 align:start position:0% you're actually signing by replying to this<00:56:30.720> email<00:56:31.480> is<00:56:31.680> recover<00:56:32.200> account<00:56:32.559> eth 00:56:32.829 --> 00:56:32.839 align:start position:0% this email is recover account eth 00:56:32.839 --> 00:56:34.549 align:start position:0% this email is recover account eth address<00:56:33.160> from<00:56:33.319> Old<00:56:33.559> owner<00:56:33.839> eth<00:56:34.079> address<00:56:34.440> to 00:56:34.549 --> 00:56:34.559 align:start position:0% address from Old owner eth address to 00:56:34.559 --> 00:56:36.510 align:start position:0% address from Old owner eth address to new<00:56:34.720> owner<00:56:35.119> e<00:56:35.400> address<00:56:36.119> and<00:56:36.280> this<00:56:36.359> is 00:56:36.510 --> 00:56:36.520 align:start position:0% new owner e address and this is 00:56:36.520 --> 00:56:39.270 align:start position:0% new owner e address and this is concretely<00:56:37.000> what<00:56:37.119> we'll<00:56:37.280> execute<00:56:37.680> on<00:56:38.119> chain 00:56:39.270 --> 00:56:39.280 align:start position:0% concretely what we'll execute on chain 00:56:39.280 --> 00:56:41.750 align:start position:0% concretely what we'll execute on chain um<00:56:40.280> you<00:56:40.400> know<00:56:40.559> so<00:56:40.760> so<00:56:40.960> the<00:56:41.240> the<00:56:41.319> service<00:56:41.599> we're 00:56:41.750 --> 00:56:41.760 align:start position:0% um you know so so the the service we're 00:56:41.760 --> 00:56:42.910 align:start position:0% um you know so so the the service we're going<00:56:41.839> to<00:56:41.960> provide<00:56:42.280> is<00:56:42.559> we're<00:56:42.720> going<00:56:42.799> to 00:56:42.910 --> 00:56:42.920 align:start position:0% going to provide is we're going to 00:56:42.920 --> 00:56:44.950 align:start position:0% going to provide is we're going to deploy<00:56:43.200> a<00:56:43.280> relayer<00:56:43.680> for<00:56:43.880> you<00:56:44.200> and<00:56:44.599> allow<00:56:44.839> you 00:56:44.950 --> 00:56:44.960 align:start position:0% deploy a relayer for you and allow you 00:56:44.960 --> 00:56:46.549 align:start position:0% deploy a relayer for you and allow you the<00:56:45.079> option<00:56:45.240> to<00:56:45.359> self<00:56:45.640> host<00:56:45.799> it<00:56:45.920> when<00:56:46.039> you<00:56:46.119> want 00:56:46.549 --> 00:56:46.559 align:start position:0% the option to self host it when you want 00:56:46.559 --> 00:56:48.309 align:start position:0% the option to self host it when you want the<00:56:46.680> relayer<00:56:47.119> sends<00:56:47.359> and<00:56:47.680> receives<00:56:47.920> emails 00:56:48.309 --> 00:56:48.319 align:start position:0% the relayer sends and receives emails 00:56:48.319 --> 00:56:50.470 align:start position:0% the relayer sends and receives emails and<00:56:48.440> makes<00:56:48.760> proofs<00:56:49.599> so<00:56:49.760> the<00:56:49.880> user<00:56:50.119> will<00:56:50.280> say 00:56:50.470 --> 00:56:50.480 align:start position:0% and makes proofs so the user will say 00:56:50.480 --> 00:56:52.510 align:start position:0% and makes proofs so the user will say them<00:56:50.599> like<00:56:50.799> I<00:56:50.880> want<00:56:51.000> to<00:56:51.160> recover<00:56:51.559> my<00:56:51.720> account 00:56:52.510 --> 00:56:52.520 align:start position:0% them like I want to recover my account 00:56:52.520 --> 00:56:54.109 align:start position:0% them like I want to recover my account the<00:56:52.839> relayer<00:56:53.280> will<00:56:53.400> send<00:56:53.599> them<00:56:53.720> an<00:56:53.839> email 00:56:54.109 --> 00:56:54.119 align:start position:0% the relayer will send them an email 00:56:54.119 --> 00:56:55.309 align:start position:0% the relayer will send them an email saying<00:56:54.319> are<00:56:54.400> you<00:56:54.480> sure<00:56:54.640> you<00:56:54.799> want<00:56:54.880> to<00:56:55.000> recover 00:56:55.309 --> 00:56:55.319 align:start position:0% saying are you sure you want to recover 00:56:55.319 --> 00:56:57.230 align:start position:0% saying are you sure you want to recover the<00:56:55.480> account<00:56:55.920> if<00:56:56.039> you<00:56:56.280> do<00:56:56.440> reply<00:56:56.720> confirmed<00:56:57.079> to 00:56:57.230 --> 00:56:57.240 align:start position:0% the account if you do reply confirmed to 00:56:57.240 --> 00:56:59.910 align:start position:0% the account if you do reply confirmed to this<00:56:57.400> email<00:56:58.079> the<00:56:58.200> user<00:56:58.480> replies<00:56:58.960> confirm<00:56:59.799> and 00:56:59.910 --> 00:56:59.920 align:start position:0% this email the user replies confirm and 00:56:59.920 --> 00:57:01.990 align:start position:0% this email the user replies confirm and then<00:57:00.039> the<00:57:00.160> relayer<00:57:00.920> takes<00:57:01.240> that<00:57:01.400> reply<00:57:01.799> makes 00:57:01.990 --> 00:57:02.000 align:start position:0% then the relayer takes that reply makes 00:57:02.000 --> 00:57:03.710 align:start position:0% then the relayer takes that reply makes a<00:57:02.119> ZK<00:57:02.400> proof<00:57:02.640> of<00:57:02.720> it<00:57:02.839> sends<00:57:03.039> it<00:57:03.160> on<00:57:03.319> chain<00:57:03.640> and 00:57:03.710 --> 00:57:03.720 align:start position:0% a ZK proof of it sends it on chain and 00:57:03.720 --> 00:57:06.029 align:start position:0% a ZK proof of it sends it on chain and triggers<00:57:04.039> that<00:57:04.240> smart 00:57:06.029 --> 00:57:06.039 align:start position:0% triggers that smart 00:57:06.039 --> 00:57:09.829 align:start position:0% triggers that smart contract<00:57:07.119> cool<00:57:08.119> um<00:57:09.119> you<00:57:09.240> know<00:57:09.359> you<00:57:09.440> can<00:57:09.559> accept 00:57:09.829 --> 00:57:09.839 align:start position:0% contract cool um you know you can accept 00:57:09.839 --> 00:57:12.029 align:start position:0% contract cool um you know you can accept Guardian<00:57:10.240> requests<00:57:11.240> um<00:57:11.359> you<00:57:11.440> can<00:57:11.599> anonymize 00:57:12.029 --> 00:57:12.039 align:start position:0% Guardian requests um you can anonymize 00:57:12.039 --> 00:57:13.430 align:start position:0% Guardian requests um you can anonymize your<00:57:12.200> email<00:57:12.480> address<00:57:12.720> on<00:57:12.880> chain<00:57:13.240> will 00:57:13.430 --> 00:57:13.440 align:start position:0% your email address on chain will 00:57:13.440 --> 00:57:15.029 align:start position:0% your email address on chain will automatically<00:57:14.000> handle<00:57:14.520> making<00:57:14.720> sure<00:57:14.920> the 00:57:15.029 --> 00:57:15.039 align:start position:0% automatically handle making sure the 00:57:15.039 --> 00:57:18.510 align:start position:0% automatically handle making sure the email<00:57:15.319> is<00:57:15.440> anonymous<00:57:15.880> on<00:57:16.240> chain<00:57:17.240> um<00:57:18.000> and<00:57:18.400> the 00:57:18.510 --> 00:57:18.520 align:start position:0% email is anonymous on chain um and the 00:57:18.520 --> 00:57:19.910 align:start position:0% email is anonymous on chain um and the point<00:57:18.680> is<00:57:18.799> a<00:57:18.880> relay<00:57:19.240> decentralized<00:57:19.760> so<00:57:19.839> you 00:57:19.910 --> 00:57:19.920 align:start position:0% point is a relay decentralized so you 00:57:19.920 --> 00:57:21.270 align:start position:0% point is a relay decentralized so you can<00:57:20.000> start<00:57:20.280> with<00:57:20.400> our<00:57:20.520> hosted<00:57:20.760> relayer<00:57:21.200> just 00:57:21.270 --> 00:57:21.280 align:start position:0% can start with our hosted relayer just 00:57:21.280 --> 00:57:22.910 align:start position:0% can start with our hosted relayer just so<00:57:21.359> you<00:57:21.440> can<00:57:21.520> get<00:57:21.599> a<00:57:21.720> prototype<00:57:22.160> up<00:57:22.640> and<00:57:22.760> then 00:57:22.910 --> 00:57:22.920 align:start position:0% so you can get a prototype up and then 00:57:22.920 --> 00:57:24.630 align:start position:0% so you can get a prototype up and then run<00:57:23.079> your<00:57:23.240> own<00:57:23.400> server<00:57:23.760> when<00:57:23.880> you<00:57:23.960> feel<00:57:24.240> ready 00:57:24.630 --> 00:57:24.640 align:start position:0% run your own server when you feel ready 00:57:24.640 --> 00:57:27.069 align:start position:0% run your own server when you feel ready to<00:57:25.640> um 00:57:27.069 --> 00:57:27.079 align:start position:0% to um 00:57:27.079 --> 00:57:30.390 align:start position:0% to um sweet<00:57:28.079> um<00:57:28.480> so<00:57:28.680> maybe<00:57:28.960> what<00:57:29.039> I'll<00:57:29.240> do<00:57:29.400> is<00:57:29.640> I<00:57:29.760> will 00:57:30.390 --> 00:57:30.400 align:start position:0% sweet um so maybe what I'll do is I will 00:57:30.400 --> 00:57:32.789 align:start position:0% sweet um so maybe what I'll do is I will put<00:57:30.680> up<00:57:31.680> uh<00:57:31.960> I'll<00:57:32.119> briefly<00:57:32.400> go<00:57:32.520> through<00:57:32.680> what 00:57:32.789 --> 00:57:32.799 align:start position:0% put up uh I'll briefly go through what 00:57:32.799 --> 00:57:34.069 align:start position:0% put up uh I'll briefly go through what the<00:57:32.880> interface<00:57:33.280> actually<00:57:33.480> looks<00:57:33.720> like<00:57:33.960> and 00:57:34.069 --> 00:57:34.079 align:start position:0% the interface actually looks like and 00:57:34.079 --> 00:57:37.309 align:start position:0% the interface actually looks like and then<00:57:34.319> we<00:57:34.559> can<00:57:35.680> um<00:57:36.680> we<00:57:36.799> can<00:57:36.920> look<00:57:37.079> at<00:57:37.200> the 00:57:37.309 --> 00:57:37.319 align:start position:0% then we can um we can look at the 00:57:37.319 --> 00:57:42.109 align:start position:0% then we can um we can look at the various<00:57:37.720> sdks<00:57:38.319> and<00:57:38.440> things<00:57:38.680> like<00:57:38.839> that<00:57:39.760> um<00:57:41.119> so 00:57:42.109 --> 00:57:42.119 align:start position:0% various sdks and things like that um so 00:57:42.119 --> 00:57:43.630 align:start position:0% various sdks and things like that um so uh<00:57:42.480> okay 00:57:43.630 --> 00:57:43.640 align:start position:0% uh okay 00:57:43.640 --> 00:57:45.829 align:start position:0% uh okay so<00:57:44.640> I<00:57:44.720> guess<00:57:44.960> maybe<00:57:45.160> the<00:57:45.240> first<00:57:45.400> thing<00:57:45.520> I'll<00:57:45.680> go 00:57:45.829 --> 00:57:45.839 align:start position:0% so I guess maybe the first thing I'll go 00:57:45.839 --> 00:57:47.349 align:start position:0% so I guess maybe the first thing I'll go over<00:57:46.039> is<00:57:46.160> if<00:57:46.240> you<00:57:46.440> actually<00:57:46.680> want<00:57:46.799> to<00:57:47.039> add 00:57:47.349 --> 00:57:47.359 align:start position:0% over is if you actually want to add 00:57:47.359 --> 00:57:48.829 align:start position:0% over is if you actually want to add let's<00:57:47.480> say<00:57:47.599> you<00:57:47.680> want<00:57:47.760> to<00:57:47.880> add<00:57:48.000> a<00:57:48.200> specific 00:57:48.829 --> 00:57:48.839 align:start position:0% let's say you want to add a specific 00:57:48.839 --> 00:57:50.430 align:start position:0% let's say you want to add a specific version<00:57:49.119> of<00:57:49.240> one<00:57:49.359> of<00:57:49.480> those<00:57:49.640> four<00:57:49.839> ideas<00:57:50.319> like 00:57:50.430 --> 00:57:50.440 align:start position:0% version of one of those four ideas like 00:57:50.440 --> 00:57:52.470 align:start position:0% version of one of those four ideas like say<00:57:50.640> account<00:57:50.880> recovery<00:57:51.240> to<00:57:51.359> your<00:57:51.520> application 00:57:52.470 --> 00:57:52.480 align:start position:0% say account recovery to your application 00:57:52.480 --> 00:57:54.510 align:start position:0% say account recovery to your application you<00:57:52.720> probably<00:57:53.079> wouldn't<00:57:53.440> use<00:57:54.039> a<00:57:54.200> generic 00:57:54.510 --> 00:57:54.520 align:start position:0% you probably wouldn't use a generic 00:57:54.520 --> 00:57:55.950 align:start position:0% you probably wouldn't use a generic transaction<00:57:54.960> Builder<00:57:55.280> you'd<00:57:55.480> automatically 00:57:55.950 --> 00:57:55.960 align:start position:0% transaction Builder you'd automatically 00:57:55.960 --> 00:57:57.789 align:start position:0% transaction Builder you'd automatically use<00:57:56.200> use<00:57:56.359> the<00:57:56.520> recovery<00:57:57.240> version<00:57:57.520> that<00:57:57.640> we 00:57:57.789 --> 00:57:57.799 align:start position:0% use use the recovery version that we 00:57:57.799 --> 00:57:59.789 align:start position:0% use use the recovery version that we deployed<00:57:58.640> so<00:57:58.799> in<00:57:58.920> this<00:57:59.039> case<00:57:59.200> you<00:57:59.280> know<00:57:59.400> we've 00:57:59.789 --> 00:57:59.799 align:start position:0% deployed so in this case you know we've 00:57:59.799 --> 00:58:01.710 align:start position:0% deployed so in this case you know we've deployed<00:58:00.119> a<00:58:00.200> recovery<00:58:00.640> module<00:58:01.400> that<00:58:01.480> you<00:58:01.559> can 00:58:01.710 --> 00:58:01.720 align:start position:0% deployed a recovery module that you can 00:58:01.720 --> 00:58:03.470 align:start position:0% deployed a recovery module that you can just<00:58:01.960> add<00:58:02.160> to<00:58:02.319> any<00:58:02.520> smart<00:58:02.839> account<00:58:03.240> so<00:58:03.359> how 00:58:03.470 --> 00:58:03.480 align:start position:0% just add to any smart account so how 00:58:03.480 --> 00:58:06.270 align:start position:0% just add to any smart account so how would<00:58:03.599> you<00:58:03.760> do<00:58:03.920> that<00:58:04.720> um<00:58:05.079> you<00:58:05.240> would<00:58:05.920> take<00:58:06.079> our 00:58:06.270 --> 00:58:06.280 align:start position:0% would you do that um you would take our 00:58:06.280 --> 00:58:08.230 align:start position:0% would you do that um you would take our solidity<00:58:07.280> you<00:58:07.400> know<00:58:07.520> smart<00:58:07.799> contract<00:58:08.039> you'd 00:58:08.230 --> 00:58:08.240 align:start position:0% solidity you know smart contract you'd 00:58:08.240 --> 00:58:09.390 align:start position:0% solidity you know smart contract you'd install<00:58:08.440> it<00:58:08.559> on<00:58:08.640> your<00:58:08.760> wallet<00:58:09.039> and<00:58:09.079> then<00:58:09.160> You' 00:58:09.390 --> 00:58:09.400 align:start position:0% install it on your wallet and then You' 00:58:09.400 --> 00:58:11.390 align:start position:0% install it on your wallet and then You' hit<00:58:09.520> our<00:58:09.720> API<00:58:10.599> with<00:58:10.799> these<00:58:11.039> different 00:58:11.390 --> 00:58:11.400 align:start position:0% hit our API with these different 00:58:11.400 --> 00:58:12.670 align:start position:0% hit our API with these different acceptance<00:58:11.760> request<00:58:12.039> recovery<00:58:12.400> request 00:58:12.670 --> 00:58:12.680 align:start position:0% acceptance request recovery request 00:58:12.680 --> 00:58:14.710 align:start position:0% acceptance request recovery request complete<00:58:13.000> request<00:58:13.720> again<00:58:13.960> keeping<00:58:14.240> in<00:58:14.440> mind 00:58:14.710 --> 00:58:14.720 align:start position:0% complete request again keeping in mind 00:58:14.720 --> 00:58:16.390 align:start position:0% complete request again keeping in mind you<00:58:14.839> can<00:58:15.039> always<00:58:15.280> self-host<00:58:15.760> this<00:58:15.880> API<00:58:16.200> if<00:58:16.280> you 00:58:16.390 --> 00:58:16.400 align:start position:0% you can always self-host this API if you 00:58:16.400 --> 00:58:17.630 align:start position:0% you can always self-host this API if you want<00:58:16.680> but<00:58:16.760> you<00:58:16.839> can<00:58:16.960> start<00:58:17.119> with<00:58:17.280> ours<00:58:17.520> just 00:58:17.630 --> 00:58:17.640 align:start position:0% want but you can start with ours just 00:58:17.640 --> 00:58:19.910 align:start position:0% want but you can start with ours just for<00:58:17.799> ease<00:58:18.160> of<00:58:18.480> convenience<00:58:19.480> um<00:58:19.680> when<00:58:19.760> you 00:58:19.910 --> 00:58:19.920 align:start position:0% for ease of convenience um when you 00:58:19.920 --> 00:58:21.829 align:start position:0% for ease of convenience um when you actually<00:58:20.200> want<00:58:20.319> to<00:58:20.520> add<00:58:20.680> the<00:58:20.839> smart<00:58:21.160> account 00:58:21.829 --> 00:58:21.839 align:start position:0% actually want to add the smart account 00:58:21.839 --> 00:58:24.870 align:start position:0% actually want to add the smart account into<00:58:22.640> you<00:58:22.760> know<00:58:23.400> a<00:58:23.599> wallet<00:58:24.079> on<00:58:24.200> a<00:58:24.319> front<00:58:24.559> end 00:58:24.870 --> 00:58:24.880 align:start position:0% into you know a wallet on a front end 00:58:24.880 --> 00:58:26.589 align:start position:0% into you know a wallet on a front end you<00:58:25.000> can<00:58:25.160> use<00:58:25.359> some<00:58:25.599> code<00:58:25.839> like<00:58:25.960> this<00:58:26.480> that 00:58:26.589 --> 00:58:26.599 align:start position:0% you can use some code like this that 00:58:26.599 --> 00:58:28.230 align:start position:0% you can use some code like this that we've<00:58:26.880> already<00:58:27.200> kind<00:58:27.319> of<00:58:27.480> configured<00:58:27.960> for 00:58:28.230 --> 00:58:28.240 align:start position:0% we've already kind of configured for 00:58:28.240 --> 00:58:30.109 align:start position:0% we've already kind of configured for people<00:58:28.559> deploying<00:58:28.960> this<00:58:29.119> account<00:58:29.359> recovery 00:58:30.109 --> 00:58:30.119 align:start position:0% people deploying this account recovery 00:58:30.119 --> 00:58:33.549 align:start position:0% people deploying this account recovery to<00:58:30.280> a<00:58:30.480> wallet<00:58:31.480> um<00:58:32.480> the<00:58:32.680> docs<00:58:33.000> will<00:58:33.160> be<00:58:33.400> like 00:58:33.549 --> 00:58:33.559 align:start position:0% to a wallet um the docs will be like 00:58:33.559 --> 00:58:35.589 align:start position:0% to a wallet um the docs will be like your<00:58:33.760> your<00:58:33.920> friend<00:58:34.280> here<00:58:34.760> so<00:58:34.880> if<00:58:35.000> you<00:58:35.119> look<00:58:35.480> oh 00:58:35.589 --> 00:58:35.599 align:start position:0% your your friend here so if you look oh 00:58:35.599 --> 00:58:36.750 align:start position:0% your your friend here so if you look oh I<00:58:35.640> want<00:58:35.760> to<00:58:35.839> do<00:58:35.960> account<00:58:36.160> recovery<00:58:36.520> you<00:58:36.599> search 00:58:36.750 --> 00:58:36.760 align:start position:0% I want to do account recovery you search 00:58:36.760 --> 00:58:38.230 align:start position:0% I want to do account recovery you search it<00:58:36.839> in<00:58:36.960> the<00:58:37.039> docs<00:58:37.480> you'll<00:58:37.640> be<00:58:37.720> able<00:58:37.880> to<00:58:37.960> pull<00:58:38.119> up 00:58:38.230 --> 00:58:38.240 align:start position:0% it in the docs you'll be able to pull up 00:58:38.240 --> 00:58:39.430 align:start position:0% it in the docs you'll be able to pull up that<00:58:38.359> page<00:58:38.520> and<00:58:38.680> like<00:58:38.839> okay<00:58:38.960> this<00:58:39.039> is<00:58:39.200> exactly 00:58:39.430 --> 00:58:39.440 align:start position:0% that page and like okay this is exactly 00:58:39.440 --> 00:58:42.630 align:start position:0% that page and like okay this is exactly what<00:58:39.559> I<00:58:39.599> need<00:58:39.720> to<00:58:39.799> do<00:58:39.920> to<00:58:40.079> integrate<00:58:40.440> it<00:58:41.440> um<00:58:42.440> but 00:58:42.630 --> 00:58:42.640 align:start position:0% what I need to do to integrate it um but 00:58:42.640 --> 00:58:44.190 align:start position:0% what I need to do to integrate it um but maybe<00:58:42.839> the<00:58:42.960> thing<00:58:43.119> we'll<00:58:43.359> focus<00:58:43.640> on<00:58:44.000> this 00:58:44.190 --> 00:58:44.200 align:start position:0% maybe the thing we'll focus on this 00:58:44.200 --> 00:58:46.950 align:start position:0% maybe the thing we'll focus on this Workshop<00:58:45.000> is<00:58:45.200> getting<00:58:45.760> generic<00:58:46.359> solidity 00:58:46.950 --> 00:58:46.960 align:start position:0% Workshop is getting generic solidity 00:58:46.960 --> 00:58:49.750 align:start position:0% Workshop is getting generic solidity commands<00:58:47.359> to<00:58:47.559> work<00:58:48.520> um<00:58:48.799> so<00:58:48.960> you<00:58:49.079> know<00:58:49.480> in<00:58:49.640> this 00:58:49.750 --> 00:58:49.760 align:start position:0% commands to work um so you know in this 00:58:49.760 --> 00:58:51.069 align:start position:0% commands to work um so you know in this case<00:58:49.920> you<00:58:50.000> would<00:58:50.160> maybe<00:58:50.400> want<00:58:50.480> to<00:58:50.599> build<00:58:50.880> your 00:58:51.069 --> 00:58:51.079 align:start position:0% case you would maybe want to build your 00:58:51.079 --> 00:58:54.150 align:start position:0% case you would maybe want to build your own<00:58:51.920> version<00:58:52.520> of<00:58:53.079> this<00:58:53.280> kind<00:58:53.440> of<00:58:53.880> email 00:58:54.150 --> 00:58:54.160 align:start position:0% own version of this kind of email 00:58:54.160 --> 00:58:55.789 align:start position:0% own version of this kind of email trigger<00:58:54.520> transaction<00:58:55.359> let's<00:58:55.480> say<00:58:55.599> you<00:58:55.640> wanted 00:58:55.789 --> 00:58:55.799 align:start position:0% trigger transaction let's say you wanted 00:58:55.799 --> 00:58:57.309 align:start position:0% trigger transaction let's say you wanted to<00:58:55.880> build<00:58:56.240> account<00:58:56.480> recovery<00:58:57.000> you<00:58:57.079> would 00:58:57.309 --> 00:58:57.319 align:start position:0% to build account recovery you would 00:58:57.319 --> 00:58:59.150 align:start position:0% to build account recovery you would Define<00:58:57.920> something<00:58:58.240> like<00:58:58.400> recover<00:58:58.880> account 00:58:59.150 --> 00:58:59.160 align:start position:0% Define something like recover account 00:58:59.160 --> 00:59:01.230 align:start position:0% Define something like recover account eth<00:58:59.400> address<00:58:59.680> to<00:58:59.799> new<00:58:59.960> owner<00:59:00.280> eth<00:59:00.520> address<00:59:01.039> you 00:59:01.230 --> 00:59:01.240 align:start position:0% eth address to new owner eth address you 00:59:01.240 --> 00:59:03.029 align:start position:0% eth address to new owner eth address you define<00:59:01.440> a<00:59:01.559> solidity<00:59:02.000> function<00:59:02.359> looks<00:59:02.599> exactly 00:59:03.029 --> 00:59:03.039 align:start position:0% define a solidity function looks exactly 00:59:03.039 --> 00:59:05.549 align:start position:0% define a solidity function looks exactly like<00:59:03.240> this<00:59:03.640> a<00:59:03.760> recovery<00:59:04.240> subject<00:59:04.599> template 00:59:05.549 --> 00:59:05.559 align:start position:0% like this a recovery subject template 00:59:05.559 --> 00:59:07.150 align:start position:0% like this a recovery subject template that<00:59:05.760> you<00:59:05.839> know<00:59:06.000> takes<00:59:06.160> in<00:59:06.319> string<00:59:06.599> memory 00:59:07.150 --> 00:59:07.160 align:start position:0% that you know takes in string memory 00:59:07.160 --> 00:59:09.109 align:start position:0% that you know takes in string memory returns<00:59:07.520> templates<00:59:08.160> that<00:59:08.319> just<00:59:08.520> defines<00:59:08.920> the 00:59:09.109 --> 00:59:09.119 align:start position:0% returns templates that just defines the 00:59:09.119 --> 00:59:11.109 align:start position:0% returns templates that just defines the pattern<00:59:09.839> and<00:59:09.960> you<00:59:10.119> plug<00:59:10.359> in<00:59:10.680> you<00:59:10.799> know<00:59:10.880> in<00:59:11.000> this 00:59:11.109 --> 00:59:11.119 align:start position:0% pattern and you plug in you know in this 00:59:11.119 --> 00:59:13.910 align:start position:0% pattern and you plug in you know in this case<00:59:11.319> I've<00:59:11.480> done<00:59:12.000> you<00:59:12.160> know<00:59:12.680> um<00:59:13.240> curly<00:59:13.559> braces 00:59:13.910 --> 00:59:13.920 align:start position:0% case I've done you know um curly braces 00:59:13.920 --> 00:59:15.270 align:start position:0% case I've done you know um curly braces eth<00:59:14.119> address<00:59:14.400> or<00:59:14.480> I<00:59:14.520> want<00:59:14.680> eth<00:59:14.839> addresses<00:59:15.200> you 00:59:15.270 --> 00:59:15.280 align:start position:0% eth address or I want eth addresses you 00:59:15.280 --> 00:59:17.109 align:start position:0% eth address or I want eth addresses you can<00:59:15.400> also<00:59:15.559> put<00:59:15.720> strings<00:59:16.119> numbers<00:59:16.520> whatever 00:59:17.109 --> 00:59:17.119 align:start position:0% can also put strings numbers whatever 00:59:17.119 --> 00:59:18.990 align:start position:0% can also put strings numbers whatever and<00:59:17.280> so<00:59:17.480> let<00:59:17.640> you<00:59:17.920> automatically<00:59:18.680> access 00:59:18.990 --> 00:59:19.000 align:start position:0% and so let you automatically access 00:59:19.000 --> 00:59:21.270 align:start position:0% and so let you automatically access those<00:59:19.200> values<00:59:19.520> from<00:59:19.680> within<00:59:20.039> solidity<00:59:21.039> um<00:59:21.119> and 00:59:21.270 --> 00:59:21.280 align:start position:0% those values from within solidity um and 00:59:21.280 --> 00:59:23.069 align:start position:0% those values from within solidity um and you<00:59:21.359> would<00:59:21.480> hit<00:59:21.640> our<00:59:21.799> API<00:59:22.280> with<00:59:22.359> a<00:59:22.480> query<00:59:22.880> like 00:59:23.069 --> 00:59:23.079 align:start position:0% you would hit our API with a query like 00:59:23.079 --> 00:59:24.829 align:start position:0% you would hit our API with a query like this<00:59:23.520> our<00:59:23.720> quick<00:59:24.000> start<00:59:24.200> will<00:59:24.359> automatically 00:59:24.829 --> 00:59:24.839 align:start position:0% this our quick start will automatically 00:59:24.839 --> 00:59:26.349 align:start position:0% this our quick start will automatically do<00:59:25.000> this<00:59:25.119> end<00:59:25.280> to<00:59:25.359> end<00:59:25.599> thing<00:59:25.720> for<00:59:25.920> you<00:59:26.200> and<00:59:26.280> you 00:59:26.349 --> 00:59:26.359 align:start position:0% do this end to end thing for you and you 00:59:26.359 --> 00:59:27.910 align:start position:0% do this end to end thing for you and you can<00:59:26.480> kind<00:59:26.559> of<00:59:26.680> just<00:59:26.799> fiddle<00:59:27.079> with<00:59:27.200> it<00:59:27.640> oh<00:59:27.799> what 00:59:27.910 --> 00:59:27.920 align:start position:0% can kind of just fiddle with it oh what 00:59:27.920 --> 00:59:29.950 align:start position:0% can kind of just fiddle with it oh what if<00:59:28.039> I<00:59:28.119> change<00:59:28.359> the<00:59:28.440> word<00:59:28.720> account<00:59:29.559> uh<00:59:29.720> from 00:59:29.950 --> 00:59:29.960 align:start position:0% if I change the word account uh from 00:59:29.960 --> 00:59:31.789 align:start position:0% if I change the word account uh from account<00:59:30.319> to<00:59:30.559> wallet<00:59:31.160> what<00:59:31.280> if<00:59:31.359> I<00:59:31.480> change<00:59:31.680> an 00:59:31.789 --> 00:59:31.799 align:start position:0% account to wallet what if I change an 00:59:31.799 --> 00:59:33.069 align:start position:0% account to wallet what if I change an eth<00:59:32.000> address<00:59:32.240> from<00:59:32.319> an<00:59:32.400> eth<00:59:32.599> address<00:59:32.839> to<00:59:32.960> a 00:59:33.069 --> 00:59:33.079 align:start position:0% eth address from an eth address to a 00:59:33.079 --> 00:59:34.829 align:start position:0% eth address from an eth address to a string<00:59:33.640> and<00:59:33.720> this<00:59:33.839> so<00:59:33.960> let<00:59:34.119> you<00:59:34.280> experiment 00:59:34.829 --> 00:59:34.839 align:start position:0% string and this so let you experiment 00:59:34.839 --> 00:59:39.230 align:start position:0% string and this so let you experiment with<00:59:35.039> this<00:59:35.280> as<00:59:35.359> a<00:59:35.520> starting<00:59:36.039> point<00:59:37.319> um<00:59:38.319> okay<00:59:38.599> so 00:59:39.230 --> 00:59:39.240 align:start position:0% with this as a starting point um okay so 00:59:39.240 --> 00:59:41.670 align:start position:0% with this as a starting point um okay so what<00:59:39.359> we're<00:59:39.480> going<00:59:39.640> to<00:59:39.760> do<00:59:39.960> is<00:59:40.039> we're<00:59:40.240> going<00:59:40.680> to 00:59:41.670 --> 00:59:41.680 align:start position:0% what we're going to do is we're going to 00:59:41.680 --> 00:59:42.910 align:start position:0% what we're going to do is we're going to um<00:59:41.799> maybe<00:59:42.119> what<00:59:42.240> I'll<00:59:42.359> even<00:59:42.480> do<00:59:42.599> is<00:59:42.640> I'll<00:59:42.760> link 00:59:42.910 --> 00:59:42.920 align:start position:0% um maybe what I'll even do is I'll link 00:59:42.920 --> 00:59:45.670 align:start position:0% um maybe what I'll even do is I'll link to<00:59:43.000> a<00:59:43.119> more<00:59:43.359> specific<00:59:43.680> point<00:59:43.920> in<00:59:44.000> the<00:59:44.480> docs<00:59:45.480> um 00:59:45.670 --> 00:59:45.680 align:start position:0% to a more specific point in the docs um 00:59:45.680 --> 00:59:47.190 align:start position:0% to a more specific point in the docs um where<00:59:45.799> we<00:59:46.039> have<00:59:46.280> this<00:59:46.520> kind 00:59:47.190 --> 00:59:47.200 align:start position:0% where we have this kind 00:59:47.200 --> 00:59:50.270 align:start position:0% where we have this kind of<00:59:48.200> uh<00:59:48.920> this<00:59:49.039> sort<00:59:49.240> of<00:59:49.359> generic<00:59:49.640> relayer<00:59:50.079> thing 00:59:50.270 --> 00:59:50.280 align:start position:0% of uh this sort of generic relayer thing 00:59:50.280 --> 00:59:52.789 align:start position:0% of uh this sort of generic relayer thing going<00:59:50.480> on<00:59:50.760> let<00:59:50.880> me<00:59:51.160> pull<00:59:51.359> up<00:59:52.039> where<00:59:52.240> exactly<00:59:52.599> we 00:59:52.789 --> 00:59:52.799 align:start position:0% going on let me pull up where exactly we 00:59:52.799 --> 00:59:56.069 align:start position:0% going on let me pull up where exactly we have<00:59:53.200> this<00:59:54.200> um<00:59:54.440> quick<00:59:54.760> start<00:59:55.760> okay<00:59:55.880> so<00:59:55.920> I'm<00:59:56.039> I'm 00:59:56.069 --> 00:59:56.079 align:start position:0% have this um quick start okay so I'm I'm 00:59:56.079 --> 01:00:12.950 align:start position:0% have this um quick start okay so I'm I'm going<00:59:56.160> to<00:59:56.240> link<00:59:56.440> everyone<00:59:56.640> to<00:59:56.839> this<00:59:56.960> quick 01:00:12.950 --> 01:00:12.960 align:start position:0% 01:00:12.960 --> 01:00:15.950 align:start position:0% start<01:00:13.960> um<01:00:14.160> this<01:00:14.240> is<01:00:14.480> concretely 01:00:15.950 --> 01:00:15.960 align:start position:0% start um this is concretely 01:00:15.960 --> 01:00:27.750 align:start position:0% start um this is concretely in<01:00:16.960> email 01:00:27.750 --> 01:00:27.760 align:start position:0% 01:00:27.760 --> 01:00:30.270 align:start position:0% um<01:00:28.760> cool<01:00:29.039> so<01:00:29.160> you<01:00:29.280> can<01:00:29.559> either<01:00:29.760> go<01:00:29.839> to<01:00:29.960> docs 01:00:30.270 --> 01:00:30.280 align:start position:0% um cool so you can either go to docs 01:00:30.280 --> 01:00:32.109 align:start position:0% um cool so you can either go to docs email<01:00:30.839> email<01:00:31.160> transaction<01:00:31.599> off<01:00:31.799> this<01:00:31.880> is<01:00:31.960> our 01:00:32.109 --> 01:00:32.119 align:start position:0% email email transaction off this is our 01:00:32.119 --> 01:00:34.069 align:start position:0% email email transaction off this is our email<01:00:32.400> transaction<01:00:32.880> Builder<01:00:33.680> and<01:00:33.799> then<01:00:33.960> the 01:00:34.069 --> 01:00:34.079 align:start position:0% email transaction Builder and then the 01:00:34.079 --> 01:00:36.029 align:start position:0% email transaction Builder and then the quick<01:00:34.280> start<01:00:34.799> or<01:00:34.960> you<01:00:35.039> can<01:00:35.200> just<01:00:35.319> scan<01:00:35.559> this<01:00:35.720> QR 01:00:36.029 --> 01:00:36.039 align:start position:0% quick start or you can just scan this QR 01:00:36.039 --> 01:00:37.549 align:start position:0% quick start or you can just scan this QR code 01:00:37.549 --> 01:00:37.559 align:start position:0% code 01:00:37.559 --> 01:00:39.789 align:start position:0% code um<01:00:38.559> if<01:00:38.680> you're<01:00:38.799> on<01:00:38.960> your<01:00:39.160> laptop<01:00:39.440> you<01:00:39.520> play<01:00:39.680> one 01:00:39.789 --> 01:00:39.799 align:start position:0% um if you're on your laptop you play one 01:00:39.799 --> 01:00:41.950 align:start position:0% um if you're on your laptop you play one to<01:00:39.920> the<01:00:40.000> bottom<01:00:40.200> one<01:00:40.400> if<01:00:40.480> you're<01:00:40.720> on<01:00:40.880> your<01:00:41.799> it's 01:00:41.950 --> 01:00:41.960 align:start position:0% to the bottom one if you're on your it's 01:00:41.960 --> 01:00:43.069 align:start position:0% to the bottom one if you're on your it's not<01:00:42.079> really<01:00:42.240> possible<01:00:42.440> to<01:00:42.520> run<01:00:42.640> solidity<01:00:43.000> on 01:00:43.069 --> 01:00:43.079 align:start position:0% not really possible to run solidity on 01:00:43.079 --> 01:00:44.910 align:start position:0% not really possible to run solidity on your<01:00:43.160> mobile<01:00:43.440> so<01:00:43.559> I<01:00:43.640> wouldn't<01:00:43.920> recommend 01:00:44.910 --> 01:00:44.920 align:start position:0% your mobile so I wouldn't recommend 01:00:44.920 --> 01:00:46.390 align:start position:0% your mobile so I wouldn't recommend scanning<01:00:45.319> from<01:00:45.520> your<01:00:45.680> your<01:00:45.839> phone<01:00:46.119> and<01:00:46.200> then 01:00:46.390 --> 01:00:46.400 align:start position:0% scanning from your your phone and then 01:00:46.400 --> 01:00:48.470 align:start position:0% scanning from your your phone and then we'll<01:00:46.920> we'll<01:00:47.119> basically<01:00:47.480> show<01:00:47.880> once<01:00:48.119> you've 01:00:48.470 --> 01:00:48.480 align:start position:0% we'll we'll basically show once you've 01:00:48.480 --> 01:00:50.910 align:start position:0% we'll we'll basically show once you've got<01:00:49.480> uh<01:00:49.640> okay<01:00:49.760> so<01:00:50.079> I'll<01:00:50.280> I'll<01:00:50.400> leave<01:00:50.559> this<01:00:50.680> QR 01:00:50.910 --> 01:00:50.920 align:start position:0% got uh okay so I'll I'll leave this QR 01:00:50.920 --> 01:00:52.990 align:start position:0% got uh okay so I'll I'll leave this QR code<01:00:51.119> up<01:00:51.240> for<01:00:51.319> a<01:00:51.440> little<01:00:51.599> bit<01:00:52.039> once<01:00:52.240> you've<01:00:52.520> got 01:00:52.990 --> 01:00:53.000 align:start position:0% code up for a little bit once you've got 01:00:53.000 --> 01:00:57.589 align:start position:0% code up for a little bit once you've got this<01:00:54.000> uh<01:00:54.160> this<01:00:54.319> QR<01:00:54.599> code<01:00:54.839> scanned<01:00:55.799> um<01:00:56.079> um 01:00:57.589 --> 01:00:57.599 align:start position:0% this uh this QR code scanned um um 01:00:57.599 --> 01:00:59.950 align:start position:0% this uh this QR code scanned um um then<01:00:58.599> I<01:00:58.680> guess<01:00:58.799> the<01:00:58.960> did<01:00:59.240> will<01:00:59.359> take<01:00:59.480> over<01:00:59.839> what 01:00:59.950 --> 01:00:59.960 align:start position:0% then I guess the did will take over what 01:00:59.960 --> 01:01:01.630 align:start position:0% then I guess the did will take over what exactly<01:01:00.280> should<01:01:00.440> you<01:01:00.599> do<01:01:01.160> with<01:01:01.280> this<01:01:01.440> quick 01:01:01.630 --> 01:01:01.640 align:start position:0% exactly should you do with this quick 01:01:01.640 --> 01:01:03.390 align:start position:0% exactly should you do with this quick start<01:01:01.880> running<01:01:02.240> through<01:01:02.799> actually<01:01:03.079> cloning 01:01:03.390 --> 01:01:03.400 align:start position:0% start running through actually cloning 01:01:03.400 --> 01:01:05.549 align:start position:0% start running through actually cloning the<01:01:03.480> repo<01:01:03.839> going<01:01:04.039> through<01:01:04.240> these<01:01:04.359> docs<01:01:04.720> Etc<01:01:05.440> so 01:01:05.549 --> 01:01:05.559 align:start position:0% the repo going through these docs Etc so 01:01:05.559 --> 01:01:06.950 align:start position:0% the repo going through these docs Etc so I'll<01:01:05.720> give<01:01:05.880> people<01:01:06.160> like<01:01:06.280> 30<01:01:06.480> seconds<01:01:06.720> to<01:01:06.880> make 01:01:06.950 --> 01:01:06.960 align:start position:0% I'll give people like 30 seconds to make 01:01:06.960 --> 01:01:08.430 align:start position:0% I'll give people like 30 seconds to make sure<01:01:07.079> you've<01:01:07.240> scan<01:01:07.559> this<01:01:07.680> QR<01:01:07.960> code<01:01:08.200> make<01:01:08.319> sure 01:01:08.430 --> 01:01:08.440 align:start position:0% sure you've scan this QR code make sure 01:01:08.440 --> 01:01:10.150 align:start position:0% sure you've scan this QR code make sure you<01:01:08.599> have<01:01:08.760> this<01:01:08.960> link<01:01:09.520> on<01:01:09.680> your<01:01:09.839> computer 01:01:10.150 --> 01:01:10.160 align:start position:0% you have this link on your computer 01:01:10.160 --> 01:01:11.990 align:start position:0% you have this link on your computer you're<01:01:10.319> at<01:01:10.440> docs<01:01:10.720> email<01:01:11.039> email<01:01:11.319> txo<01:01:11.799> quick 01:01:11.990 --> 01:01:12.000 align:start position:0% you're at docs email email txo quick 01:01:12.000 --> 01:01:15.750 align:start position:0% you're at docs email email txo quick start<01:01:12.599> and<01:01:12.760> we'll<01:01:13.039> we'll<01:01:13.200> go<01:01:13.359> from<01:01:13.680> there 01:01:15.750 --> 01:01:15.760 align:start position:0% start and we'll we'll go from there 01:01:15.760 --> 01:01:19.990 align:start position:0% start and we'll we'll go from there um<01:01:16.760> I'll<01:01:16.920> make<01:01:17.160> this<01:01:17.599> uh<01:01:18.160> bigger<01:01:19.160> okay<01:01:19.680> and<01:01:19.799> we 01:01:19.990 --> 01:01:20.000 align:start position:0% um I'll make this uh bigger okay and we 01:01:20.000 --> 01:01:21.069 align:start position:0% um I'll make this uh bigger okay and we give<01:01:20.079> you<01:01:20.160> 10<01:01:20.319> seconds<01:01:20.559> to<01:01:20.720> take<01:01:20.880> this<01:01:21.000> and 01:01:21.069 --> 01:01:21.079 align:start position:0% give you 10 seconds to take this and 01:01:21.079 --> 01:01:22.069 align:start position:0% give you 10 seconds to take this and then<01:01:21.200> we're<01:01:21.319> going<01:01:21.400> to<01:01:21.599> we're<01:01:21.720> going<01:01:21.839> to<01:01:21.920> move 01:01:22.069 --> 01:01:22.079 align:start position:0% then we're going to we're going to move 01:01:22.079 --> 01:01:26.390 align:start position:0% then we're going to we're going to move to<01:01:22.200> what<01:01:22.359> exactly<01:01:22.640> do<01:01:22.760> with<01:01:22.880> the<01:01:22.960> Quick<01:01:23.160> Start 01:01:26.390 --> 01:01:26.400 align:start position:0% 01:01:26.400 --> 01:01:29.910 align:start position:0% okay<01:01:26.880> everybody<01:01:27.480> has<01:01:27.960> scanned<01:01:28.960> I<01:01:29.119> hope<01:01:29.319> so<01:01:29.720> you 01:01:29.910 --> 01:01:29.920 align:start position:0% okay everybody has scanned I hope so you 01:01:29.920 --> 01:01:32.870 align:start position:0% okay everybody has scanned I hope so you have<01:01:30.160> like<01:01:30.359> three<01:01:30.760> seconds<01:01:31.760> um<01:01:32.359> okay<01:01:32.559> cool<01:01:32.799> now 01:01:32.870 --> 01:01:32.880 align:start position:0% have like three seconds um okay cool now 01:01:32.880 --> 01:01:34.109 align:start position:0% have like three seconds um okay cool now we're<01:01:33.000> going<01:01:33.079> to<01:01:33.160> swap<01:01:33.440> to<01:01:33.640> once<01:01:33.880> you're<01:01:34.000> on 01:01:34.109 --> 01:01:34.119 align:start position:0% we're going to swap to once you're on 01:01:34.119 --> 01:01:36.430 align:start position:0% we're going to swap to once you're on this<01:01:34.240> quick<01:01:34.440> start<01:01:34.720> page<01:01:35.640> um<01:01:36.039> you<01:01:36.160> know<01:01:36.280> we're 01:01:36.430 --> 01:01:36.440 align:start position:0% this quick start page um you know we're 01:01:36.440 --> 01:01:38.029 align:start position:0% this quick start page um you know we're going<01:01:36.520> to<01:01:37.039> actually<01:01:37.319> go<01:01:37.520> through<01:01:37.720> this<01:01:37.880> git 01:01:38.029 --> 01:01:38.039 align:start position:0% going to actually go through this git 01:01:38.039 --> 01:01:41.589 align:start position:0% going to actually go through this git cloning<01:01:38.960> CD<01:01:39.760> in<01:01:40.760> um<01:01:41.160> setting<01:01:41.440> your 01:01:41.589 --> 01:01:41.599 align:start position:0% cloning CD in um setting your 01:01:41.599 --> 01:01:43.950 align:start position:0% cloning CD in um setting your environment<01:01:42.359> and<01:01:42.520> then<01:01:42.920> actually<01:01:43.240> deploying 01:01:43.950 --> 01:01:43.960 align:start position:0% environment and then actually deploying 01:01:43.960 --> 01:01:59.470 align:start position:0% environment and then actually deploying cool<01:01:44.319> you<01:01:44.440> want<01:01:44.520> to<01:01:44.760> take<01:01:44.960> over<01:01:45.400> sure 01:01:59.470 --> 01:01:59.480 align:start position:0% 01:01:59.480 --> 01:02:03.589 align:start position:0% cool<01:02:00.480> um<01:02:01.200> so<01:02:01.559> hey<01:02:01.760> everyone<01:02:02.440> um<01:02:02.640> I'm<01:02:02.799> a<01:02:03.319> here 01:02:03.589 --> 01:02:03.599 align:start position:0% cool um so hey everyone um I'm a here 01:02:03.599 --> 01:02:05.910 align:start position:0% cool um so hey everyone um I'm a here and<01:02:03.880> the<01:02:04.240> entire<01:02:04.680> point<01:02:04.880> for<01:02:05.160> this<01:02:05.400> particular 01:02:05.910 --> 01:02:05.920 align:start position:0% and the entire point for this particular 01:02:05.920 --> 01:02:09.549 align:start position:0% and the entire point for this particular section<01:02:06.599> of<01:02:06.880> the<01:02:07.319> workshop<01:02:07.960> is<01:02:08.200> to<01:02:08.559> show<01:02:09.000> that 01:02:09.549 --> 01:02:09.559 align:start position:0% section of the workshop is to show that 01:02:09.559 --> 01:02:12.190 align:start position:0% section of the workshop is to show that how<01:02:09.720> easy<01:02:10.039> we<01:02:10.200> have<01:02:10.359> sort<01:02:10.520> of<01:02:10.760> made<01:02:11.119> to<01:02:11.880> do<01:02:12.079> an 01:02:12.190 --> 01:02:12.200 align:start position:0% how easy we have sort of made to do an 01:02:12.200 --> 01:02:13.630 align:start position:0% how easy we have sort of made to do an onchain 01:02:13.630 --> 01:02:13.640 align:start position:0% onchain 01:02:13.640 --> 01:02:16.029 align:start position:0% onchain transaction<01:02:14.640> like<01:02:15.000> specifically<01:02:15.599> to<01:02:15.799> a 01:02:16.029 --> 01:02:16.039 align:start position:0% transaction like specifically to a 01:02:16.039 --> 01:02:18.230 align:start position:0% transaction like specifically to a contract<01:02:16.559> function<01:02:17.279> purely<01:02:17.640> by<01:02:17.760> replying<01:02:18.119> to 01:02:18.230 --> 01:02:18.240 align:start position:0% contract function purely by replying to 01:02:18.240 --> 01:02:20.910 align:start position:0% contract function purely by replying to an<01:02:18.359> email<01:02:18.839> so<01:02:19.000> if<01:02:19.079> you<01:02:19.200> want<01:02:19.319> to<01:02:19.680> integrate<01:02:20.680> um 01:02:20.910 --> 01:02:20.920 align:start position:0% an email so if you want to integrate um 01:02:20.920 --> 01:02:22.710 align:start position:0% an email so if you want to integrate um people<01:02:21.200> just<01:02:21.400> replying<01:02:21.760> to<01:02:21.920> emails<01:02:22.319> and<01:02:22.559> that 01:02:22.710 --> 01:02:22.720 align:start position:0% people just replying to emails and that 01:02:22.720 --> 01:02:24.630 align:start position:0% people just replying to emails and that triggering<01:02:23.160> an<01:02:23.279> onchain<01:02:23.680> transaction<01:02:24.480> this 01:02:24.630 --> 01:02:24.640 align:start position:0% triggering an onchain transaction this 01:02:24.640 --> 01:02:29.190 align:start position:0% triggering an onchain transaction this is<01:02:24.920> like<01:02:25.039> a<01:02:25.359> really<01:02:26.119> demo<01:02:26.400> for<01:02:26.799> that<01:02:27.799> um<01:02:28.640> cool 01:02:29.190 --> 01:02:29.200 align:start position:0% is like a really demo for that um cool 01:02:29.200 --> 01:02:31.430 align:start position:0% is like a really demo for that um cool so<01:02:30.079> maybe<01:02:30.279> justly<01:02:30.680> one<01:02:30.839> question<01:02:31.039> can<01:02:31.200> people 01:02:31.430 --> 01:02:31.440 align:start position:0% so maybe justly one question can people 01:02:31.440 --> 01:02:33.230 align:start position:0% so maybe justly one question can people read<01:02:31.680> the<01:02:31.799> screen<01:02:32.200> like<01:02:32.400> from<01:02:32.640> the<01:02:32.799> back<01:02:33.079> it 01:02:33.230 --> 01:02:33.240 align:start position:0% read the screen like from the back it 01:02:33.240 --> 01:02:34.870 align:start position:0% read the screen like from the back it looks<01:02:33.400> a<01:02:33.480> little<01:02:33.640> bit<01:02:34.400> raise<01:02:34.559> your<01:02:34.680> hand<01:02:34.799> if 01:02:34.870 --> 01:02:34.880 align:start position:0% looks a little bit raise your hand if 01:02:34.880 --> 01:02:37.990 align:start position:0% looks a little bit raise your hand if you<01:02:35.000> can<01:02:35.119> read<01:02:35.359> the<01:02:36.359> that's<01:02:36.599> good<01:02:37.599> good<01:02:37.799> okay 01:02:37.990 --> 01:02:38.000 align:start position:0% you can read the that's good good okay 01:02:38.000 --> 01:02:42.349 align:start position:0% you can read the that's good good okay should<01:02:38.119> be<01:02:38.240> fine<01:02:39.279> cool<01:02:40.279> um<01:02:40.680> yeah<01:02:41.160> so<01:02:41.640> if<01:02:41.960> anyone 01:02:42.349 --> 01:02:42.359 align:start position:0% should be fine cool um yeah so if anyone 01:02:42.359 --> 01:02:44.630 align:start position:0% should be fine cool um yeah so if anyone hasn't<01:02:42.760> been<01:02:42.960> to<01:02:43.119> the<01:02:43.279> docs<01:02:43.599> page<01:02:43.920> yet<01:02:44.359> it's 01:02:44.630 --> 01:02:44.640 align:start position:0% hasn't been to the docs page yet it's 01:02:44.640 --> 01:02:47.549 align:start position:0% hasn't been to the docs page yet it's docs.<01:02:45.279> proof.<01:02:45.720> email<01:02:46.279> you<01:02:46.599> come<01:02:46.839> to<01:02:47.000> the<01:02:47.160> email 01:02:47.549 --> 01:02:47.559 align:start position:0% docs. proof. email you come to the email 01:02:47.559 --> 01:02:50.109 align:start position:0% docs. proof. email you come to the email transaction<01:02:48.200> a<01:02:48.599> section<01:02:49.359> and<01:02:49.520> in<01:02:49.680> there<01:02:49.960> you 01:02:50.109 --> 01:02:50.119 align:start position:0% transaction a section and in there you 01:02:50.119 --> 01:02:53.269 align:start position:0% transaction a section and in there you just<01:02:50.400> click<01:02:50.640> to<01:02:50.920> Quick 01:02:53.269 --> 01:02:53.279 align:start position:0% 01:02:53.279 --> 01:02:56.670 align:start position:0% Start<01:02:54.279> I'll<01:02:54.599> give<01:02:54.920> people<01:02:56.000> half<01:02:56.200> a<01:02:56.319> minute<01:02:56.520> to 01:02:56.670 --> 01:02:56.680 align:start position:0% Start I'll give people half a minute to 01:02:56.680 --> 01:03:17.789 align:start position:0% Start I'll give people half a minute to a<01:02:56.799> minute<01:02:57.039> to<01:02:57.160> do 01:03:17.789 --> 01:03:17.799 align:start position:0% 01:03:17.799 --> 01:03:21.109 align:start position:0% this<01:03:18.799> um<01:03:19.279> yeah<01:03:19.880> just<01:03:20.119> do<01:03:20.319> the<01:03:20.480> first<01:03:20.720> step<01:03:20.960> you 01:03:21.109 --> 01:03:21.119 align:start position:0% this um yeah just do the first step you 01:03:21.119 --> 01:03:23.789 align:start position:0% this um yeah just do the first step you just<01:03:21.279> need<01:03:21.440> to<01:03:21.640> clone<01:03:22.400> um<01:03:22.599> a<01:03:22.760> get<01:03:22.960> reppel<01:03:23.559> and 01:03:23.789 --> 01:03:23.799 align:start position:0% just need to clone um a get reppel and 01:03:23.799 --> 01:03:35.910 align:start position:0% just need to clone um a get reppel and CD<01:03:24.200> into<01:03:24.400> the<01:03:24.559> directory 01:03:35.910 --> 01:03:35.920 align:start position:0% 01:03:35.920 --> 01:03:38.069 align:start position:0% can<01:03:36.039> I<01:03:36.160> have<01:03:36.279> a<01:03:36.359> show<01:03:36.680> off<01:03:36.880> hands<01:03:37.200> of<01:03:37.720> um<01:03:37.920> of 01:03:38.069 --> 01:03:38.079 align:start position:0% can I have a show off hands of um of 01:03:38.079 --> 01:03:39.549 align:start position:0% can I have a show off hands of um of people<01:03:38.359> that<01:03:38.480> have<01:03:38.680> done 01:03:39.549 --> 01:03:39.559 align:start position:0% people that have done 01:03:39.559 --> 01:03:43.069 align:start position:0% people that have done this<01:03:40.559> cool<01:03:40.839> I<01:03:40.920> can<01:03:41.039> see<01:03:41.440> five<01:03:42.039> six<01:03:42.319> hands<01:03:42.760> seven 01:03:43.069 --> 01:03:43.079 align:start position:0% this cool I can see five six hands seven 01:03:43.079 --> 01:03:47.069 align:start position:0% this cool I can see five six hands seven eight<01:03:43.440> nine<01:03:43.880> cool<01:03:44.839> um<01:03:45.119> yeah<01:03:45.319> so<01:03:45.440> I'll<01:03:46.079> continue 01:03:47.069 --> 01:03:47.079 align:start position:0% eight nine cool um yeah so I'll continue 01:03:47.079 --> 01:03:48.589 align:start position:0% eight nine cool um yeah so I'll continue I'll 01:03:48.589 --> 01:03:48.599 align:start position:0% I'll 01:03:48.599 --> 01:03:51.470 align:start position:0% I'll just<01:03:49.599> so<01:03:49.880> once<01:03:50.039> you<01:03:50.160> have<01:03:50.279> sort<01:03:50.480> of<01:03:50.799> um<01:03:51.000> cded 01:03:51.470 --> 01:03:51.480 align:start position:0% just so once you have sort of um cded 01:03:51.480 --> 01:03:54.470 align:start position:0% just so once you have sort of um cded into<01:03:51.680> the<01:03:51.880> directory<01:03:52.880> um<01:03:53.119> I<01:03:53.240> would<01:03:54.079> recommend 01:03:54.470 --> 01:03:54.480 align:start position:0% into the directory um I would recommend 01:03:54.480 --> 01:03:58.470 align:start position:0% into the directory um I would recommend you<01:03:54.599> to<01:03:54.760> run<01:03:55.039> this<01:03:55.240> one<01:03:55.839> on<01:03:56.119> this<01:03:56.400> is<01:03:57.400> um<01:03:58.039> one 01:03:58.470 --> 01:03:58.480 align:start position:0% you to run this one on this is um one 01:03:58.480 --> 01:04:01.029 align:start position:0% you to run this one on this is um one package<01:03:58.960> that<01:03:59.160> you<01:03:59.640> might<01:03:59.960> need<01:04:00.440> I'll<01:04:00.640> just 01:04:01.029 --> 01:04:01.039 align:start position:0% package that you might need I'll just 01:04:01.039 --> 01:04:06.829 align:start position:0% package that you might need I'll just screen<01:04:02.079> yeah<01:04:03.079> so<01:04:03.640> it's<01:04:03.920> bre<01:04:04.520> install<01:04:05.480> JQ<01:04:06.480> just 01:04:06.829 --> 01:04:06.839 align:start position:0% screen yeah so it's bre install JQ just 01:04:06.839 --> 01:04:09.510 align:start position:0% screen yeah so it's bre install JQ just do<01:04:07.079> this<01:04:07.279> if<01:04:07.400> you<01:04:07.520> don't<01:04:07.799> have<01:04:08.440> a<01:04:08.559> few<01:04:08.760> of<01:04:08.960> Macs 01:04:09.510 --> 01:04:09.520 align:start position:0% do this if you don't have a few of Macs 01:04:09.520 --> 01:04:11.670 align:start position:0% do this if you don't have a few of Macs probably<01:04:10.039> have<01:04:10.359> this<01:04:10.720> couple<01:04:10.920> of<01:04:11.079> don't<01:04:11.400> so 01:04:11.670 --> 01:04:11.680 align:start position:0% probably have this couple of don't so 01:04:11.680 --> 01:04:17.829 align:start position:0% probably have this couple of don't so this<01:04:11.839> is<01:04:12.000> just<01:04:12.160> like<01:04:12.279> a<01:04:12.480> stive<01:04:13.599> installation 01:04:17.829 --> 01:04:17.839 align:start position:0% 01:04:17.839 --> 01:04:19.510 align:start position:0% um 01:04:19.510 --> 01:04:19.520 align:start position:0% um 01:04:19.520 --> 01:04:22.390 align:start position:0% um cool<01:04:20.520> and<01:04:20.799> once<01:04:21.160> you<01:04:21.440> have<01:04:21.880> done<01:04:22.119> the 01:04:22.390 --> 01:04:22.400 align:start position:0% cool and once you have done the 01:04:22.400 --> 01:04:24.349 align:start position:0% cool and once you have done the installation<01:04:23.400> um<01:04:23.599> just<01:04:23.760> go<01:04:23.960> back<01:04:24.079> to<01:04:24.200> the 01:04:24.349 --> 01:04:24.359 align:start position:0% installation um just go back to the 01:04:24.359 --> 01:04:27.630 align:start position:0% installation um just go back to the docks<01:04:24.760> page<01:04:25.599> uh<01:04:25.880> um<01:04:26.160> scroll<01:04:26.839> down<01:04:27.359> and<01:04:27.520> you 01:04:27.630 --> 01:04:27.640 align:start position:0% docks page uh um scroll down and you 01:04:27.640 --> 01:04:30.950 align:start position:0% docks page uh um scroll down and you would<01:04:27.839> see<01:04:28.119> this<01:04:28.319> one<01:04:28.720> make<01:04:29.520> Command<01:04:30.520> um<01:04:30.880> I 01:04:30.950 --> 01:04:30.960 align:start position:0% would see this one make Command um I 01:04:30.960 --> 01:04:33.230 align:start position:0% would see this one make Command um I would<01:04:31.160> ask<01:04:31.319> you<01:04:31.440> to<01:04:31.680> copy<01:04:32.000> this<01:04:32.200> command<01:04:32.960> paste 01:04:33.230 --> 01:04:33.240 align:start position:0% would ask you to copy this command paste 01:04:33.240 --> 01:04:36.950 align:start position:0% would ask you to copy this command paste it<01:04:33.359> into<01:04:33.599> your<01:04:34.160> terminal<01:04:35.160> and 01:04:36.950 --> 01:04:36.960 align:start position:0% it into your terminal and 01:04:36.960 --> 01:04:39.710 align:start position:0% it into your terminal and then<01:04:37.960> just<01:04:38.240> enter<01:04:38.559> your<01:04:38.760> email<01:04:39.079> address<01:04:39.400> so 01:04:39.710 --> 01:04:39.720 align:start position:0% then just enter your email address so 01:04:39.720 --> 01:04:42.910 align:start position:0% then just enter your email address so this<01:04:39.839> is<01:04:40.240> my<01:04:40.440> email<01:04:40.880> address<01:04:41.880> um<01:04:42.559> and<01:04:42.680> you<01:04:42.760> can 01:04:42.910 --> 01:04:42.920 align:start position:0% this is my email address um and you can 01:04:42.920 --> 01:04:45.870 align:start position:0% this is my email address um and you can enter<01:04:43.160> your<01:04:43.359> email<01:04:43.680> addresses<01:04:44.160> as<01:04:44.599> well<01:04:45.599> once 01:04:45.870 --> 01:04:45.880 align:start position:0% enter your email addresses as well once 01:04:45.880 --> 01:04:48.950 align:start position:0% enter your email addresses as well once you<01:04:46.119> submit<01:04:46.559> this<01:04:47.200> you<01:04:47.400> should<01:04:47.839> receive<01:04:48.680> a 01:04:48.950 --> 01:04:48.960 align:start position:0% you submit this you should receive a 01:04:48.960 --> 01:04:56.990 align:start position:0% you submit this you should receive a response<01:04:49.680> with<01:04:49.839> the<01:04:49.960> status<01:04:50.440> success 01:04:56.990 --> 01:04:57.000 align:start position:0% 01:04:57.000 --> 01:04:58.630 align:start position:0% got<01:04:57.119> it 01:04:58.630 --> 01:04:58.640 align:start position:0% got it 01:04:58.640 --> 01:05:00.829 align:start position:0% got it cool<01:04:59.640> got 01:05:00.829 --> 01:05:00.839 align:start position:0% cool got 01:05:00.839 --> 01:05:03.470 align:start position:0% cool got it<01:05:01.839> um<01:05:02.000> the<01:05:02.079> command<01:05:02.400> is<01:05:02.520> in<01:05:02.640> the<01:05:02.799> docs<01:05:03.240> so<01:05:03.400> if 01:05:03.470 --> 01:05:03.480 align:start position:0% it um the command is in the docs so if 01:05:03.480 --> 01:05:06.029 align:start position:0% it um the command is in the docs so if you<01:05:03.680> just<01:05:03.839> scroll<01:05:04.319> a<01:05:04.480> bit<01:05:04.760> down<01:05:05.200> it<01:05:05.279> is<01:05:05.640> make 01:05:06.029 --> 01:05:06.039 align:start position:0% you just scroll a bit down it is make 01:05:06.039 --> 01:05:09.309 align:start position:0% you just scroll a bit down it is make space<01:05:06.440> Sumit<01:05:06.920> space<01:05:07.520> Capital<01:05:07.960> email<01:05:08.720> equals 01:05:09.309 --> 01:05:09.319 align:start position:0% space Sumit space Capital email equals 01:05:09.319 --> 01:05:13.950 align:start position:0% space Sumit space Capital email equals your<01:05:09.559> email 01:05:13.950 --> 01:05:13.960 align:start position:0% 01:05:13.960 --> 01:05:16.470 align:start position:0% address<01:05:14.960> and<01:05:15.319> for<01:05:15.559> people<01:05:15.799> who<01:05:15.960> have<01:05:16.200> done 01:05:16.470 --> 01:05:16.480 align:start position:0% address and for people who have done 01:05:16.480 --> 01:05:17.990 align:start position:0% address and for people who have done this<01:05:16.680> already<01:05:17.119> what<01:05:17.240> you<01:05:17.359> would<01:05:17.559> have 01:05:17.990 --> 01:05:18.000 align:start position:0% this already what you would have 01:05:18.000 --> 01:05:20.150 align:start position:0% this already what you would have received<01:05:18.359> is<01:05:18.520> that<01:05:18.680> if<01:05:18.799> you<01:05:18.920> go<01:05:19.039> to<01:05:19.160> your<01:05:19.359> email 01:05:20.150 --> 01:05:20.160 align:start position:0% received is that if you go to your email 01:05:20.160 --> 01:05:22.549 align:start position:0% received is that if you go to your email you<01:05:20.279> would<01:05:20.520> have<01:05:20.920> received<01:05:21.240> a<01:05:21.520> very<01:05:21.839> templated 01:05:22.549 --> 01:05:22.559 align:start position:0% you would have received a very templated 01:05:22.559 --> 01:05:24.789 align:start position:0% you would have received a very templated email<01:05:23.480> um<01:05:23.760> it<01:05:23.839> would<01:05:24.039> look<01:05:24.240> something<01:05:24.559> like 01:05:24.789 --> 01:05:24.799 align:start position:0% email um it would look something like 01:05:24.799 --> 01:05:30.430 align:start position:0% email um it would look something like this 01:05:30.430 --> 01:05:30.440 align:start position:0% 01:05:30.440 --> 01:05:33.190 align:start position:0% once<01:05:30.920> this<01:05:31.079> step<01:05:31.359> is<01:05:31.520> complete<01:05:32.039> and<01:05:32.400> um<01:05:32.799> yeah<01:05:33.079> I 01:05:33.190 --> 01:05:33.200 align:start position:0% once this step is complete and um yeah I 01:05:33.200 --> 01:05:35.829 align:start position:0% once this step is complete and um yeah I would<01:05:33.440> recommend<01:05:34.039> you<01:05:34.240> to<01:05:34.799> just<01:05:35.039> reply<01:05:35.359> to<01:05:35.520> it 01:05:35.829 --> 01:05:35.839 align:start position:0% would recommend you to just reply to it 01:05:35.839 --> 01:05:38.269 align:start position:0% would recommend you to just reply to it it<01:05:36.079> doesn't<01:05:36.640> matter<01:05:37.039> what<01:05:37.160> you're<01:05:37.559> typing<01:05:37.920> in 01:05:38.269 --> 01:05:38.279 align:start position:0% it doesn't matter what you're typing in 01:05:38.279 --> 01:05:40.309 align:start position:0% it doesn't matter what you're typing in as<01:05:38.400> long<01:05:38.599> as<01:05:38.720> you're<01:05:38.920> replying<01:05:39.279> to<01:05:39.400> the<01:05:39.520> email 01:05:40.309 --> 01:05:40.319 align:start position:0% as long as you're replying to the email 01:05:40.319 --> 01:05:51.349 align:start position:0% as long as you're replying to the email um<01:05:40.480> it<01:05:40.559> is<01:05:40.760> good 01:05:51.349 --> 01:05:51.359 align:start position:0% 01:05:51.359 --> 01:05:53.750 align:start position:0% enough<01:05:52.359> show<01:05:52.720> off<01:05:52.920> hands<01:05:53.279> people<01:05:53.480> who<01:05:53.559> have 01:05:53.750 --> 01:05:53.760 align:start position:0% enough show off hands people who have 01:05:53.760 --> 01:05:56.589 align:start position:0% enough show off hands people who have done<01:05:53.920> it 01:05:56.589 --> 01:05:56.599 align:start position:0% done it 01:05:56.599 --> 01:05:58.990 align:start position:0% done it cool<01:05:57.319> five 01:05:58.990 --> 01:05:59.000 align:start position:0% cool five 01:05:59.000 --> 01:06:03.510 align:start position:0% cool five people<01:06:00.000> anyone<01:06:00.319> from<01:06:00.559> there<01:06:00.799> having<01:06:01.079> any 01:06:03.510 --> 01:06:03.520 align:start position:0% 01:06:03.520 --> 01:06:06.230 align:start position:0% issues 01:06:06.230 --> 01:06:06.240 align:start position:0% issues 01:06:06.240 --> 01:06:09.510 align:start position:0% issues 5022<01:06:07.240> um<01:06:07.440> just<01:06:07.559> run<01:06:07.880> again<01:06:08.119> this<01:06:08.240> is<01:06:08.599> okay<01:06:09.240> so 01:06:09.510 --> 01:06:09.520 align:start position:0% 5022 um just run again this is okay so 01:06:09.520 --> 01:06:11.630 align:start position:0% 5022 um just run again this is okay so why<01:06:09.720> you<01:06:09.880> would<01:06:10.079> have<01:06:10.240> been<01:06:10.599> receiving<01:06:10.799> 502<01:06:11.400> is 01:06:11.630 --> 01:06:11.640 align:start position:0% why you would have been receiving 502 is 01:06:11.640 --> 01:06:13.870 align:start position:0% why you would have been receiving 502 is that<01:06:11.880> we<01:06:11.960> are<01:06:12.119> also<01:06:12.359> making<01:06:12.640> an<01:06:12.839> Alchemy<01:06:13.319> check 01:06:13.870 --> 01:06:13.880 align:start position:0% that we are also making an Alchemy check 01:06:13.880 --> 01:06:17.670 align:start position:0% that we are also making an Alchemy check for<01:06:14.720> checking<01:06:15.160> that<01:06:16.039> is<01:06:16.520> any<01:06:17.000> transfer<01:06:17.480> of 01:06:17.670 --> 01:06:17.680 align:start position:0% for checking that is any transfer of 01:06:17.680 --> 01:06:19.870 align:start position:0% for checking that is any transfer of data<01:06:18.039> or<01:06:18.240> approval<01:06:18.599> of<01:06:18.720> erc20<01:06:19.359> tokens<01:06:19.720> are 01:06:19.870 --> 01:06:19.880 align:start position:0% data or approval of erc20 tokens are 01:06:19.880 --> 01:06:22.670 align:start position:0% data or approval of erc20 tokens are sort<01:06:20.079> of<01:06:20.480> being<01:06:20.760> done<01:06:21.599> um<01:06:21.920> and<01:06:22.000> to<01:06:22.200> avoid<01:06:22.520> that 01:06:22.670 --> 01:06:22.680 align:start position:0% sort of being done um and to avoid that 01:06:22.680 --> 01:06:24.430 align:start position:0% sort of being done um and to avoid that there's<01:06:22.839> an<01:06:22.960> Alchemy<01:06:23.359> simulation<01:06:23.799> check<01:06:24.160> and 01:06:24.430 --> 01:06:24.440 align:start position:0% there's an Alchemy simulation check and 01:06:24.440 --> 01:06:29.510 align:start position:0% there's an Alchemy simulation check and that<01:06:24.559> would<01:06:24.720> have<01:06:24.839> rate<01:06:25.079> limited<01:06:25.400> so<01:06:25.599> just<01:06:25.760> try 01:06:29.510 --> 01:06:29.520 align:start position:0% 01:06:29.520 --> 01:06:33.230 align:start position:0% again<01:06:30.520> and<01:06:31.279> um<01:06:32.279> I<01:06:32.400> will<01:06:32.599> be<01:06:32.799> giving<01:06:33.039> the 01:06:33.230 --> 01:06:33.240 align:start position:0% again and um I will be giving the 01:06:33.240 --> 01:06:44.500 align:start position:0% again and um I will be giving the overview<01:06:34.000> of<01:06:34.240> this<01:06:34.520> as<01:06:34.720> well 01:06:44.500 --> 01:06:44.510 align:start position:0% 01:06:44.510 --> 01:06:57.910 align:start position:0% [Music] 01:06:57.910 --> 01:06:57.920 align:start position:0% 01:06:57.920 --> 01:07:01.190 align:start position:0% cool<01:06:58.240> so<01:06:58.640> for<01:06:58.920> people<01:06:59.160> sort<01:06:59.720> of<01:07:00.720> basically 01:07:01.190 --> 01:07:01.200 align:start position:0% cool so for people sort of basically 01:07:01.200 --> 01:07:03.269 align:start position:0% cool so for people sort of basically asking<01:07:01.599> that<01:07:01.960> what<01:07:02.119> did<01:07:02.279> we<01:07:02.480> actually<01:07:02.799> do<01:07:03.160> okay 01:07:03.269 --> 01:07:03.279 align:start position:0% asking that what did we actually do okay 01:07:03.279 --> 01:07:06.390 align:start position:0% asking that what did we actually do okay we<01:07:03.480> reped<01:07:03.839> to<01:07:03.960> an<01:07:04.079> email<01:07:04.680> and<01:07:05.079> um<01:07:05.640> if<01:07:05.799> I<01:07:06.000> was<01:07:06.279> to 01:07:06.390 --> 01:07:06.400 align:start position:0% we reped to an email and um if I was to 01:07:06.400 --> 01:07:12.269 align:start position:0% we reped to an email and um if I was to show<01:07:06.640> you<01:07:06.799> the<01:07:07.279> email<01:07:08.279> um<01:07:09.039> just<01:07:09.279> give<01:07:09.400> it<01:07:09.559> some 01:07:12.269 --> 01:07:12.279 align:start position:0% 01:07:12.279 --> 01:07:14.549 align:start position:0% time<01:07:13.279> yeah<01:07:13.520> some<01:07:13.760> few<01:07:13.960> of<01:07:14.039> the<01:07:14.160> folks<01:07:14.440> would 01:07:14.549 --> 01:07:14.559 align:start position:0% time yeah some few of the folks would 01:07:14.559 --> 01:07:16.430 align:start position:0% time yeah some few of the folks would have<01:07:14.920> received<01:07:15.079> an<01:07:15.200> email<01:07:15.520> like<01:07:15.760> this<01:07:16.079> where 01:07:16.430 --> 01:07:16.440 align:start position:0% have received an email like this where 01:07:16.440 --> 01:07:18.390 align:start position:0% have received an email like this where it<01:07:16.520> would<01:07:16.680> have<01:07:16.839> said<01:07:17.079> your<01:07:17.520> request<01:07:17.920> ID<01:07:18.240> has 01:07:18.390 --> 01:07:18.400 align:start position:0% it would have said your request ID has 01:07:18.400 --> 01:07:21.390 align:start position:0% it would have said your request ID has been<01:07:18.680> complete<01:07:19.559> view<01:07:19.760> on<01:07:20.000> Explorer<01:07:20.960> you<01:07:21.119> can 01:07:21.390 --> 01:07:21.400 align:start position:0% been complete view on Explorer you can 01:07:21.400 --> 01:07:23.230 align:start position:0% been complete view on Explorer you can see<01:07:21.799> this<01:07:21.960> one<01:07:22.240> transaction<01:07:22.880> that<01:07:23.000> has 01:07:23.230 --> 01:07:23.240 align:start position:0% see this one transaction that has 01:07:23.240 --> 01:07:25.950 align:start position:0% see this one transaction that has happened<01:07:23.640> so<01:07:23.960> what<01:07:24.160> did<01:07:24.359> you<01:07:24.799> really<01:07:25.039> do<01:07:25.359> by<01:07:25.559> by 01:07:25.950 --> 01:07:25.960 align:start position:0% happened so what did you really do by by 01:07:25.960 --> 01:07:28.950 align:start position:0% happened so what did you really do by by replying<01:07:26.359> to<01:07:26.440> an<01:07:26.599> email<01:07:27.599> um<01:07:28.240> if<01:07:28.359> you<01:07:28.520> sort<01:07:28.720> of 01:07:28.950 --> 01:07:28.960 align:start position:0% replying to an email um if you sort of 01:07:28.960 --> 01:07:31.510 align:start position:0% replying to an email um if you sort of go<01:07:29.200> over<01:07:30.079> the<01:07:30.559> actual 01:07:31.510 --> 01:07:31.520 align:start position:0% go over the actual 01:07:31.520 --> 01:07:34.950 align:start position:0% go over the actual contract<01:07:32.520> in<01:07:33.000> the<01:07:33.920> repository<01:07:34.559> that<01:07:34.680> you<01:07:34.799> just 01:07:34.950 --> 01:07:34.960 align:start position:0% contract in the repository that you just 01:07:34.960 --> 01:07:38.109 align:start position:0% contract in the repository that you just cloned<01:07:35.520> you<01:07:35.640> would<01:07:35.920> find<01:07:36.559> yourself<01:07:37.559> um<01:07:37.920> a 01:07:38.109 --> 01:07:38.119 align:start position:0% cloned you would find yourself um a 01:07:38.119 --> 01:07:40.269 align:start position:0% cloned you would find yourself um a contract<01:07:38.920> that<01:07:39.079> is<01:07:39.359> already<01:07:39.680> been<01:07:39.880> deployed 01:07:40.269 --> 01:07:40.279 align:start position:0% contract that is already been deployed 01:07:40.279 --> 01:07:41.789 align:start position:0% contract that is already been deployed you<01:07:40.359> could<01:07:40.480> have<01:07:40.640> deployed<01:07:41.039> this<01:07:41.200> yourself 01:07:41.789 --> 01:07:41.799 align:start position:0% you could have deployed this yourself 01:07:41.799 --> 01:07:44.470 align:start position:0% you could have deployed this yourself and<01:07:42.000> then<01:07:42.200> made<01:07:42.480> few<01:07:42.760> changes<01:07:43.760> but<01:07:44.279> what 01:07:44.470 --> 01:07:44.480 align:start position:0% and then made few changes but what 01:07:44.480 --> 01:07:46.390 align:start position:0% and then made few changes but what essentially<01:07:44.960> is<01:07:45.559> being<01:07:45.839> done<01:07:46.039> in<01:07:46.200> this 01:07:46.390 --> 01:07:46.400 align:start position:0% essentially is being done in this 01:07:46.400 --> 01:07:48.109 align:start position:0% essentially is being done in this particular<01:07:46.799> contract<01:07:47.200> is<01:07:47.359> that<01:07:47.720> we<01:07:47.880> have 01:07:48.109 --> 01:07:48.119 align:start position:0% particular contract is that we have 01:07:48.119 --> 01:07:50.589 align:start position:0% particular contract is that we have created<01:07:48.520> an<01:07:48.760> email<01:07:49.119> off<01:07:49.480> contract<01:07:49.839> for<01:07:50.039> you 01:07:50.589 --> 01:07:50.599 align:start position:0% created an email off contract for you 01:07:50.599 --> 01:07:52.670 align:start position:0% created an email off contract for you and<01:07:51.000> what<01:07:51.319> it<01:07:51.520> does<01:07:51.799> essentially<01:07:52.240> is<01:07:52.400> that<01:07:52.520> it 01:07:52.670 --> 01:07:52.680 align:start position:0% and what it does essentially is that it 01:07:52.680 --> 01:07:55.109 align:start position:0% and what it does essentially is that it allows<01:07:52.960> you<01:07:53.079> to<01:07:53.279> create<01:07:53.839> commands<01:07:54.839> um<01:07:55.000> and 01:07:55.109 --> 01:07:55.119 align:start position:0% allows you to create commands um and 01:07:55.119 --> 01:07:57.269 align:start position:0% allows you to create commands um and what<01:07:55.240> do<01:07:55.559> I<01:07:55.680> mean<01:07:55.839> by<01:07:56.000> commands<01:07:56.559> commands<01:07:57.000> look 01:07:57.269 --> 01:07:57.279 align:start position:0% what do I mean by commands commands look 01:07:57.279 --> 01:07:58.950 align:start position:0% what do I mean by commands commands look something<01:07:57.640> like<01:07:57.920> this<01:07:58.480> you<01:07:58.599> can<01:07:58.760> have 01:07:58.950 --> 01:07:58.960 align:start position:0% something like this you can have 01:07:58.960 --> 01:08:01.190 align:start position:0% something like this you can have multiple<01:07:59.440> commands<01:08:00.279> and<01:08:00.440> the<01:08:00.599> meaning<01:08:00.920> of<01:08:01.039> a 01:08:01.190 --> 01:08:01.200 align:start position:0% multiple commands and the meaning of a 01:08:01.200 --> 01:08:03.750 align:start position:0% multiple commands and the meaning of a command<01:08:01.720> is<01:08:01.920> that<01:08:02.119> you<01:08:02.240> can<01:08:02.520> trigger<01:08:03.279> things 01:08:03.750 --> 01:08:03.760 align:start position:0% command is that you can trigger things 01:08:03.760 --> 01:08:06.430 align:start position:0% command is that you can trigger things with<01:08:03.880> it<01:08:04.319> so<01:08:04.880> every<01:08:05.240> specific<01:08:05.640> command<01:08:06.160> does 01:08:06.430 --> 01:08:06.440 align:start position:0% with it so every specific command does 01:08:06.440 --> 01:08:08.190 align:start position:0% with it so every specific command does something<01:08:07.240> if<01:08:07.400> you<01:08:07.559> could<01:08:07.760> have<01:08:07.920> like<01:08:08.039> an 01:08:08.190 --> 01:08:08.200 align:start position:0% something if you could have like an 01:08:08.200 --> 01:08:10.630 align:start position:0% something if you could have like an approv<01:08:08.559> erc20<01:08:09.200> command<01:08:09.559> you<01:08:09.680> could<01:08:09.960> have<01:08:10.240> that 01:08:10.630 --> 01:08:10.640 align:start position:0% approv erc20 command you could have that 01:08:10.640 --> 01:08:13.150 align:start position:0% approv erc20 command you could have that oh<01:08:10.960> swap<01:08:11.359> my<01:08:11.799> erc20<01:08:12.480> token<01:08:12.839> if<01:08:13.000> this 01:08:13.150 --> 01:08:13.160 align:start position:0% oh swap my erc20 token if this 01:08:13.160 --> 01:08:15.150 align:start position:0% oh swap my erc20 token if this particular<01:08:13.440> command<01:08:13.720> is<01:08:13.839> Rong<01:08:14.319> or<01:08:14.559> send<01:08:14.880> money 01:08:15.150 --> 01:08:15.160 align:start position:0% particular command is Rong or send money 01:08:15.160 --> 01:08:16.789 align:start position:0% particular command is Rong or send money to<01:08:15.359> this<01:08:15.520> particular<01:08:15.839> e<01:08:16.120> address<01:08:16.400> if<01:08:16.640> that 01:08:16.789 --> 01:08:16.799 align:start position:0% to this particular e address if that 01:08:16.799 --> 01:08:19.229 align:start position:0% to this particular e address if that particular<01:08:17.080> command<01:08:17.359> is<01:08:17.440> Rong<01:08:18.319> um<01:08:18.960> for<01:08:19.120> the 01:08:19.229 --> 01:08:19.239 align:start position:0% particular command is Rong um for the 01:08:19.239 --> 01:08:21.470 align:start position:0% particular command is Rong um for the sake<01:08:19.400> of<01:08:19.600> this<01:08:19.759> particular<01:08:20.279> demonstration<01:08:21.279> um 01:08:21.470 --> 01:08:21.480 align:start position:0% sake of this particular demonstration um 01:08:21.480 --> 01:08:24.309 align:start position:0% sake of this particular demonstration um all<01:08:21.600> of<01:08:21.799> these<01:08:22.000> commands<01:08:22.560> emit<01:08:23.199> um<01:08:23.359> an<01:08:23.520> event 01:08:24.309 --> 01:08:24.319 align:start position:0% all of these commands emit um an event 01:08:24.319 --> 01:08:26.910 align:start position:0% all of these commands emit um an event and<01:08:24.719> um<01:08:25.000> they<01:08:25.120> are<01:08:25.520> different<01:08:26.000> sort<01:08:26.239> of<01:08:26.759> uh 01:08:26.910 --> 01:08:26.920 align:start position:0% and um they are different sort of uh 01:08:26.920 --> 01:08:28.510 align:start position:0% and um they are different sort of uh templates<01:08:27.400> or<01:08:27.560> placeholders<01:08:28.120> that<01:08:28.239> you<01:08:28.319> can 01:08:28.510 --> 01:08:28.520 align:start position:0% templates or placeholders that you can 01:08:28.520 --> 01:08:31.470 align:start position:0% templates or placeholders that you can use<01:08:29.120> you<01:08:29.199> can<01:08:29.359> use<01:08:29.560> a<01:08:29.719> string<01:08:30.199> you<01:08:30.279> can<01:08:30.480> use<01:08:30.759> U 01:08:31.470 --> 01:08:31.480 align:start position:0% use you can use a string you can use U 01:08:31.480 --> 01:08:34.149 align:start position:0% use you can use a string you can use U eth<01:08:31.799> address<01:08:32.199> etc<01:08:32.640> etc<01:08:33.000> and<01:08:33.120> you<01:08:33.239> can<01:08:33.719> have<01:08:33.920> the 01:08:34.149 --> 01:08:34.159 align:start position:0% eth address etc etc and you can have the 01:08:34.159 --> 01:08:36.789 align:start position:0% eth address etc etc and you can have the complexity<01:08:34.719> of<01:08:34.839> the<01:08:34.960> command<01:08:35.440> as<01:08:35.560> you<01:08:35.759> want<01:08:36.600> so 01:08:36.789 --> 01:08:36.799 align:start position:0% complexity of the command as you want so 01:08:36.799 --> 01:08:40.189 align:start position:0% complexity of the command as you want so if<01:08:37.000> I<01:08:37.159> if<01:08:37.279> you<01:08:37.359> were<01:08:37.560> to<01:08:37.679> go<01:08:37.839> into<01:08:38.199> docs<01:08:39.199> um<01:08:39.719> I 01:08:40.189 --> 01:08:40.199 align:start position:0% if I if you were to go into docs um I 01:08:40.199 --> 01:08:42.070 align:start position:0% if I if you were to go into docs um I have 01:08:42.070 --> 01:08:42.080 align:start position:0% have 01:08:42.080 --> 01:08:45.630 align:start position:0% have this<01:08:43.359> example<01:08:44.359> of<01:08:44.640> commands<01:08:45.199> that<01:08:45.319> you<01:08:45.440> could 01:08:45.630 --> 01:08:45.640 align:start position:0% this example of commands that you could 01:08:45.640 --> 01:08:47.630 align:start position:0% this example of commands that you could have 01:08:47.630 --> 01:08:47.640 align:start position:0% have 01:08:47.640 --> 01:08:49.669 align:start position:0% have used 01:08:49.669 --> 01:08:49.679 align:start position:0% used 01:08:49.679 --> 01:08:52.749 align:start position:0% used um<01:08:50.679> where<01:08:50.839> is 01:08:52.749 --> 01:08:52.759 align:start position:0% um where is 01:08:52.759 --> 01:08:56.070 align:start position:0% um where is it<01:08:53.759> cool<01:08:54.319> so<01:08:54.719> the<01:08:54.880> example<01:08:55.199> of<01:08:55.480> commands<01:08:55.920> can 01:08:56.070 --> 01:08:56.080 align:start position:0% it cool so the example of commands can 01:08:56.080 --> 01:08:59.110 align:start position:0% it cool so the example of commands can be<01:08:56.239> for<01:08:56.400> example<01:08:56.799> send<01:08:57.440> decimals<01:08:58.040> tokens<01:08:58.520> to<01:08:58.759> e 01:08:59.110 --> 01:08:59.120 align:start position:0% be for example send decimals tokens to e 01:08:59.120 --> 01:09:01.269 align:start position:0% be for example send decimals tokens to e address<01:08:59.480> and<01:08:59.600> this<01:08:59.719> is<01:08:59.799> a<01:09:00.000> templated<01:09:00.520> command 01:09:01.269 --> 01:09:01.279 align:start position:0% address and this is a templated command 01:09:01.279 --> 01:09:02.990 align:start position:0% address and this is a templated command and<01:09:01.440> while<01:09:01.600> filling<01:09:02.080> the<01:09:02.279> parameters<01:09:02.880> you 01:09:02.990 --> 01:09:03.000 align:start position:0% and while filling the parameters you 01:09:03.000 --> 01:09:06.030 align:start position:0% and while filling the parameters you could<01:09:03.159> have<01:09:03.400> specified<01:09:04.080> 2.5<01:09:04.839> tokens<01:09:05.520> to<01:09:05.799> this 01:09:06.030 --> 01:09:06.040 align:start position:0% could have specified 2.5 tokens to this 01:09:06.040 --> 01:09:08.510 align:start position:0% could have specified 2.5 tokens to this particular<01:09:06.560> address<01:09:07.520> and<01:09:07.640> you<01:09:07.880> create<01:09:08.279> these 01:09:08.510 --> 01:09:08.520 align:start position:0% particular address and you create these 01:09:08.520 --> 01:09:10.910 align:start position:0% particular address and you create these commands<01:09:09.080> and<01:09:09.400> essentially<01:09:10.239> you<01:09:10.400> would<01:09:10.679> be 01:09:10.910 --> 01:09:10.920 align:start position:0% commands and essentially you would be 01:09:10.920 --> 01:09:14.189 align:start position:0% commands and essentially you would be creating<01:09:11.560> this<01:09:12.080> contract<01:09:13.080> um<01:09:13.719> where<01:09:13.880> you<01:09:14.040> have 01:09:14.189 --> 01:09:14.199 align:start position:0% creating this contract um where you have 01:09:14.199 --> 01:09:16.229 align:start position:0% creating this contract um where you have the<01:09:14.319> command<01:09:14.679> templates<01:09:15.319> and<01:09:15.520> the<01:09:15.799> actual 01:09:16.229 --> 01:09:16.239 align:start position:0% the command templates and the actual 01:09:16.239 --> 01:09:18.550 align:start position:0% the command templates and the actual function<01:09:16.679> that<01:09:16.799> we<01:09:16.920> are<01:09:17.080> hitting<01:09:17.759> with<01:09:18.040> the 01:09:18.550 --> 01:09:18.560 align:start position:0% function that we are hitting with the 01:09:18.560 --> 01:09:21.110 align:start position:0% function that we are hitting with the make<01:09:18.920> Command<01:09:19.520> is<01:09:19.640> the<01:09:19.799> emit<01:09:20.120> email<01:09:20.480> command 01:09:21.110 --> 01:09:21.120 align:start position:0% make Command is the emit email command 01:09:21.120 --> 01:09:23.709 align:start position:0% make Command is the emit email command function<01:09:22.120> and<01:09:22.679> what<01:09:22.799> it<01:09:23.159> essentially<01:09:23.560> is 01:09:23.709 --> 01:09:23.719 align:start position:0% function and what it essentially is 01:09:23.719 --> 01:09:25.110 align:start position:0% function and what it essentially is doing<01:09:24.040> is<01:09:24.239> that<01:09:24.400> you<01:09:24.520> have<01:09:24.679> something<01:09:24.920> called 01:09:25.110 --> 01:09:25.120 align:start position:0% doing is that you have something called 01:09:25.120 --> 01:09:26.950 align:start position:0% doing is that you have something called as<01:09:25.520> template<01:09:25.960> ID<01:09:26.239> you're<01:09:26.440> Computing<01:09:26.839> the 01:09:26.950 --> 01:09:26.960 align:start position:0% as template ID you're Computing the 01:09:26.960 --> 01:09:30.110 align:start position:0% as template ID you're Computing the template<01:09:27.359> ID<01:09:27.880> and<01:09:28.120> if<01:09:28.359> the<01:09:28.560> email<01:09:29.000> proof<01:09:29.799> is 01:09:30.110 --> 01:09:30.120 align:start position:0% template ID and if the email proof is 01:09:30.120 --> 01:09:32.269 align:start position:0% template ID and if the email proof is being<01:09:30.440> verified<01:09:31.359> then<01:09:31.520> at<01:09:31.679> the<01:09:31.799> end<01:09:32.040> you're 01:09:32.269 --> 01:09:32.279 align:start position:0% being verified then at the end you're 01:09:32.279 --> 01:09:34.510 align:start position:0% being verified then at the end you're emitting<01:09:32.640> an<01:09:32.839> event<01:09:33.839> so<01:09:34.000> you<01:09:34.120> can<01:09:34.239> have<01:09:34.400> your 01:09:34.510 --> 01:09:34.520 align:start position:0% emitting an event so you can have your 01:09:34.520 --> 01:09:37.269 align:start position:0% emitting an event so you can have your own<01:09:34.799> custom<01:09:35.159> logic<01:09:35.679> at<01:09:35.839> the<01:09:35.960> end<01:09:36.159> of<01:09:36.440> the<01:09:36.880> email 01:09:37.269 --> 01:09:37.279 align:start position:0% own custom logic at the end of the email 01:09:37.279 --> 01:09:40.550 align:start position:0% own custom logic at the end of the email proving<01:09:38.040> um<01:09:38.279> step<01:09:39.199> and<01:09:39.759> once<01:09:39.960> the<01:09:40.120> email<01:09:40.440> has 01:09:40.550 --> 01:09:40.560 align:start position:0% proving um step and once the email has 01:09:40.560 --> 01:09:42.510 align:start position:0% proving um step and once the email has been<01:09:40.719> proven<01:09:41.279> and<01:09:41.480> a<01:09:41.640> particular<01:09:42.040> command<01:09:42.359> has 01:09:42.510 --> 01:09:42.520 align:start position:0% been proven and a particular command has 01:09:42.520 --> 01:09:44.510 align:start position:0% been proven and a particular command has been<01:09:42.679> run<01:09:43.279> then<01:09:43.440> you<01:09:43.560> can<01:09:43.799> have<01:09:43.960> your<01:09:44.199> whatever 01:09:44.510 --> 01:09:44.520 align:start position:0% been run then you can have your whatever 01:09:44.520 --> 01:09:45.950 align:start position:0% been run then you can have your whatever logic<01:09:44.799> you<01:09:44.880> want<01:09:45.080> at<01:09:45.239> the<01:09:45.400> end<01:09:45.679> of<01:09:45.839> the 01:09:45.950 --> 01:09:45.960 align:start position:0% logic you want at the end of the 01:09:45.960 --> 01:09:48.149 align:start position:0% logic you want at the end of the function<01:09:46.719> and<01:09:47.040> what<01:09:47.199> is<01:09:47.440> it<01:09:47.839> it'll 01:09:48.149 --> 01:09:48.159 align:start position:0% function and what is it it'll 01:09:48.159 --> 01:09:50.390 align:start position:0% function and what is it it'll essentially<01:09:48.600> do<01:09:48.799> is<01:09:48.960> that<01:09:49.440> it'll<01:09:49.759> verify<01:09:50.199> your 01:09:50.390 --> 01:09:50.400 align:start position:0% essentially do is that it'll verify your 01:09:50.400 --> 01:09:53.590 align:start position:0% essentially do is that it'll verify your email<01:09:50.799> proof<01:09:51.319> and<01:09:51.520> then<01:09:51.679> at<01:09:51.799> the<01:09:51.880> end<01:09:52.080> run<01:09:52.319> that 01:09:53.590 --> 01:09:53.600 align:start position:0% email proof and then at the end run that 01:09:53.600 --> 01:09:56.630 align:start position:0% email proof and then at the end run that command<01:09:54.600> and<01:09:54.800> if<01:09:54.920> I<01:09:55.080> was<01:09:55.480> to<01:09:55.600> show<01:09:55.800> you<01:09:56.000> the<01:09:56.159> API 01:09:56.630 --> 01:09:56.640 align:start position:0% command and if I was to show you the API 01:09:56.640 --> 01:09:59.200 align:start position:0% command and if I was to show you the API call<01:09:57.000> that<01:09:57.120> is<01:09:57.280> getting<01:09:57.600> made<01:09:57.880> at<01:09:58.080> the 01:09:59.200 --> 01:09:59.210 align:start position:0% call that is getting made at the 01:09:59.210 --> 01:10:00.630 align:start position:0% call that is getting made at the [Music] 01:10:00.630 --> 01:10:00.640 align:start position:0% [Music] 01:10:00.640 --> 01:10:04.470 align:start position:0% [Music] end<01:10:01.640> the<01:10:01.800> call<01:10:02.080> looks<01:10:02.440> like<01:10:02.960> this<01:10:03.960> I<01:10:04.120> hope<01:10:04.360> this 01:10:04.470 --> 01:10:04.480 align:start position:0% end the call looks like this I hope this 01:10:04.480 --> 01:10:08.910 align:start position:0% end the call looks like this I hope this is 01:10:08.910 --> 01:10:08.920 align:start position:0% 01:10:08.920 --> 01:10:13.830 align:start position:0% visible<01:10:10.040> okay<01:10:11.040> cool<01:10:11.960> um<01:10:12.960> the<01:10:13.120> contract 01:10:13.830 --> 01:10:13.840 align:start position:0% visible okay cool um the contract 01:10:13.840 --> 01:10:16.350 align:start position:0% visible okay cool um the contract address<01:10:14.239> is<01:10:14.440> the<01:10:14.640> contract<01:10:15.199> address<01:10:16.080> that<01:10:16.239> you 01:10:16.350 --> 01:10:16.360 align:start position:0% address is the contract address that you 01:10:16.360 --> 01:10:18.110 align:start position:0% address is the contract address that you would<01:10:16.520> have<01:10:16.679> deployed<01:10:17.199> in<01:10:17.440> this<01:10:17.640> particular 01:10:18.110 --> 01:10:18.120 align:start position:0% would have deployed in this particular 01:10:18.120 --> 01:10:20.110 align:start position:0% would have deployed in this particular case<01:10:18.360> the<01:10:18.520> contract<01:10:19.000> address<01:10:19.400> is<01:10:19.520> for<01:10:19.840> this 01:10:20.110 --> 01:10:20.120 align:start position:0% case the contract address is for this 01:10:20.120 --> 01:10:21.669 align:start position:0% case the contract address is for this particular<01:10:20.560> contract<01:10:21.000> that's<01:10:21.199> the<01:10:21.360> emit 01:10:21.669 --> 01:10:21.679 align:start position:0% particular contract that's the emit 01:10:21.679 --> 01:10:24.149 align:start position:0% particular contract that's the emit email<01:10:22.000> command<01:10:22.400> contract<01:10:23.320> you<01:10:23.480> have<01:10:23.600> a<01:10:23.719> dkim 01:10:24.149 --> 01:10:24.159 align:start position:0% email command contract you have a dkim 01:10:24.159 --> 01:10:26.630 align:start position:0% email command contract you have a dkim contract<01:10:24.679> address<01:10:25.440> um<01:10:25.679> this<01:10:25.880> DM<01:10:26.280> address 01:10:26.630 --> 01:10:26.640 align:start position:0% contract address um this DM address 01:10:26.640 --> 01:10:30.709 align:start position:0% contract address um this DM address contract<01:10:27.600> um<01:10:27.920> can<01:10:28.120> be<01:10:28.360> found<01:10:28.880> in<01:10:29.199> The<01:10:30.199> Ether 01:10:30.709 --> 01:10:30.719 align:start position:0% contract um can be found in The Ether 01:10:30.719 --> 01:10:36.750 align:start position:0% contract um can be found in The Ether email<01:10:31.159> or<01:10:31.920> rer 01:10:36.750 --> 01:10:36.760 align:start position:0% 01:10:36.760 --> 01:10:39.470 align:start position:0% so<01:10:37.760> if<01:10:37.840> you<01:10:38.000> go<01:10:38.120> to<01:10:38.320> this<01:10:38.520> particular<01:10:38.840> repo<01:10:39.360> you 01:10:39.470 --> 01:10:39.480 align:start position:0% so if you go to this particular repo you 01:10:39.480 --> 01:10:41.870 align:start position:0% so if you go to this particular repo you will<01:10:39.760> find<01:10:40.159> the<01:10:40.360> deim<01:10:40.840> contract<01:10:41.520> so<01:10:41.679> you 01:10:41.870 --> 01:10:41.880 align:start position:0% will find the deim contract so you 01:10:41.880 --> 01:10:43.590 align:start position:0% will find the deim contract so you mention<01:10:42.320> that<01:10:42.480> you<01:10:42.600> can<01:10:42.760> also<01:10:43.000> use<01:10:43.239> the 01:10:43.590 --> 01:10:43.600 align:start position:0% mention that you can also use the 01:10:43.600 --> 01:10:45.030 align:start position:0% mention that you can also use the existing<01:10:43.960> dkim<01:10:44.360> contract<01:10:44.719> which<01:10:44.840> you<01:10:44.920> can 01:10:45.030 --> 01:10:45.040 align:start position:0% existing dkim contract which you can 01:10:45.040 --> 01:10:47.830 align:start position:0% existing dkim contract which you can file<01:10:45.320> in<01:10:45.440> the<01:10:45.560> make 01:10:47.830 --> 01:10:47.840 align:start position:0% file in the make 01:10:47.840 --> 01:10:51.229 align:start position:0% file in the make file<01:10:48.840> account<01:10:49.280> code<01:10:49.840> function<01:10:50.199> ABI<01:10:50.679> so<01:10:50.960> this 01:10:51.229 --> 01:10:51.239 align:start position:0% file account code function ABI so this 01:10:51.239 --> 01:10:53.110 align:start position:0% file account code function ABI so this is<01:10:51.480> basically<01:10:51.960> the<01:10:52.159> ABI<01:10:52.560> of<01:10:52.640> the<01:10:52.760> function 01:10:53.110 --> 01:10:53.120 align:start position:0% is basically the ABI of the function 01:10:53.120 --> 01:10:55.910 align:start position:0% is basically the ABI of the function that<01:10:53.199> you<01:10:53.320> want<01:10:53.440> to<01:10:53.679> hit<01:10:54.040> in<01:10:54.280> our<01:10:54.880> uh<01:10:55.040> case 01:10:55.910 --> 01:10:55.920 align:start position:0% that you want to hit in our uh case 01:10:55.920 --> 01:10:59.030 align:start position:0% that you want to hit in our uh case it<01:10:56.199> is<01:10:56.560> the<01:10:56.840> emit<01:10:57.159> email<01:10:57.520> command<01:10:58.159> so<01:10:58.440> the<01:10:58.600> ABI 01:10:59.030 --> 01:10:59.040 align:start position:0% it is the emit email command so the ABI 01:10:59.040 --> 01:11:00.470 align:start position:0% it is the emit email command so the ABI that<01:10:59.120> is<01:10:59.239> getting<01:10:59.480> used<01:10:59.880> is<01:11:00.000> for<01:11:00.280> this 01:11:00.470 --> 01:11:00.480 align:start position:0% that is getting used is for this 01:11:00.480 --> 01:11:03.910 align:start position:0% that is getting used is for this particular 01:11:03.910 --> 01:11:03.920 align:start position:0% 01:11:03.920 --> 01:11:06.790 align:start position:0% command<01:11:04.920> thank 01:11:06.790 --> 01:11:06.800 align:start position:0% command thank 01:11:06.800 --> 01:11:09.990 align:start position:0% command thank you<01:11:07.800> you<01:11:07.960> can<01:11:08.400> specify<01:11:09.000> which<01:11:09.199> email<01:11:09.560> address 01:11:09.990 --> 01:11:10.000 align:start position:0% you you can specify which email address 01:11:10.000 --> 01:11:11.990 align:start position:0% you you can specify which email address it<01:11:10.120> is<01:11:10.280> getting<01:11:10.520> sent<01:11:10.840> to<01:11:11.199> you<01:11:11.360> can<01:11:11.560> specify 01:11:11.990 --> 01:11:12.000 align:start position:0% it is getting sent to you can specify 01:11:12.000 --> 01:11:13.750 align:start position:0% it is getting sent to you can specify the<01:11:12.159> subject<01:11:12.520> you<01:11:12.640> want<01:11:12.920> you<01:11:13.040> can<01:11:13.199> specify<01:11:13.600> the 01:11:13.750 --> 01:11:13.760 align:start position:0% the subject you want you can specify the 01:11:13.760 --> 01:11:16.229 align:start position:0% the subject you want you can specify the body<01:11:14.400> and<01:11:14.600> the<01:11:14.760> chain<01:11:15.120> you<01:11:15.239> want<01:11:15.400> to<01:11:15.560> do<01:11:15.719> it 01:11:16.229 --> 01:11:16.239 align:start position:0% body and the chain you want to do it 01:11:16.239 --> 01:11:17.990 align:start position:0% body and the chain you want to do it also<01:11:16.520> your<01:11:16.800> function<01:11:17.199> can<01:11:17.440> have<01:11:17.640> more 01:11:17.990 --> 01:11:18.000 align:start position:0% also your function can have more 01:11:18.000 --> 01:11:20.590 align:start position:0% also your function can have more parameters<01:11:18.760> other<01:11:19.000> than<01:11:19.600> the<01:11:19.800> struct<01:11:20.360> that<01:11:20.520> we 01:11:20.590 --> 01:11:20.600 align:start position:0% parameters other than the struct that we 01:11:20.600 --> 01:11:22.470 align:start position:0% parameters other than the struct that we are<01:11:20.800> constructing<01:11:21.520> so<01:11:21.679> for<01:11:21.840> example<01:11:22.159> in<01:11:22.320> this 01:11:22.470 --> 01:11:22.480 align:start position:0% are constructing so for example in this 01:11:22.480 --> 01:11:24.229 align:start position:0% are constructing so for example in this particular<01:11:22.840> function<01:11:23.239> you<01:11:23.360> have<01:11:23.600> the<01:11:23.760> owner 01:11:24.229 --> 01:11:24.239 align:start position:0% particular function you have the owner 01:11:24.239 --> 01:11:26.950 align:start position:0% particular function you have the owner address<01:11:24.800> and<01:11:25.520> template<01:11:25.880> index<01:11:26.520> that<01:11:26.640> is<01:11:26.760> an 01:11:26.950 --> 01:11:26.960 align:start position:0% address and template index that is an 01:11:26.960 --> 01:11:29.790 align:start position:0% address and template index that is an address<01:11:27.199> and<01:11:27.320> a<01:11:27.480> un<01:11:27.920> type<01:11:28.600> so<01:11:28.920> you<01:11:29.000> can<01:11:29.239> add<01:11:29.480> the 01:11:29.790 --> 01:11:29.800 align:start position:0% address and a un type so you can add the 01:11:29.800 --> 01:11:32.229 align:start position:0% address and a un type so you can add the remaining<01:11:30.159> arguments<01:11:30.600> at<01:11:30.760> the<01:11:30.840> end<01:11:31.000> of<01:11:31.159> it<01:11:32.000> and 01:11:32.229 --> 01:11:32.239 align:start position:0% remaining arguments at the end of it and 01:11:32.239 --> 01:11:35.030 align:start position:0% remaining arguments at the end of it and what<01:11:32.440> this<01:11:32.640> essentially<01:11:33.040> does<01:11:33.600> is<01:11:33.880> that<01:11:34.719> you 01:11:35.030 --> 01:11:35.040 align:start position:0% what this essentially does is that you 01:11:35.040 --> 01:11:38.149 align:start position:0% what this essentially does is that you trigger<01:11:35.560> a<01:11:36.080> relayer<01:11:37.080> which<01:11:37.280> would<01:11:37.560> send<01:11:37.920> a 01:11:38.149 --> 01:11:38.159 align:start position:0% trigger a relayer which would send a 01:11:38.159 --> 01:11:40.709 align:start position:0% trigger a relayer which would send a email<01:11:38.480> to<01:11:38.639> the<01:11:38.800> user<01:11:39.719> once<01:11:40.080> the<01:11:40.199> user<01:11:40.560> has 01:11:40.709 --> 01:11:40.719 align:start position:0% email to the user once the user has 01:11:40.719 --> 01:11:42.990 align:start position:0% email to the user once the user has replied<01:11:41.120> to<01:11:41.320> the<01:11:41.480> email<01:11:41.920> our<01:11:42.199> IMAP<01:11:42.679> server 01:11:42.990 --> 01:11:43.000 align:start position:0% replied to the email our IMAP server 01:11:43.000 --> 01:11:45.430 align:start position:0% replied to the email our IMAP server will<01:11:43.199> pick<01:11:43.360> up<01:11:43.520> the<01:11:43.719> email<01:11:44.719> it<01:11:44.840> will<01:11:45.080> send<01:11:45.320> it 01:11:45.430 --> 01:11:45.440 align:start position:0% will pick up the email it will send it 01:11:45.440 --> 01:11:47.270 align:start position:0% will pick up the email it will send it to<01:11:45.560> our<01:11:45.760> approver<01:11:46.199> which<01:11:46.320> will<01:11:46.520> create<01:11:46.760> a<01:11:46.920> ZK 01:11:47.270 --> 01:11:47.280 align:start position:0% to our approver which will create a ZK 01:11:47.280 --> 01:11:49.950 align:start position:0% to our approver which will create a ZK proof<01:11:47.520> of<01:11:47.639> that<01:11:47.800> particular<01:11:48.199> email<01:11:49.040> and<01:11:49.280> then 01:11:49.950 --> 01:11:49.960 align:start position:0% proof of that particular email and then 01:11:49.960 --> 01:11:52.510 align:start position:0% proof of that particular email and then um<01:11:50.120> it<01:11:50.239> will<01:11:50.480> hit<01:11:50.719> on<01:11:50.960> chain<01:11:51.280> the<01:11:51.520> transaction 01:11:52.510 --> 01:11:52.520 align:start position:0% um it will hit on chain the transaction 01:11:52.520 --> 01:11:55.870 align:start position:0% um it will hit on chain the transaction that<01:11:52.639> you<01:11:52.800> want<01:11:53.000> to<01:11:53.239> hit<01:11:53.480> so<01:11:53.960> the<01:11:54.360> command<01:11:54.840> SL 01:11:55.870 --> 01:11:55.880 align:start position:0% that you want to hit so the command SL 01:11:55.880 --> 01:11:57.669 align:start position:0% that you want to hit so the command SL function<01:11:56.600> in<01:11:56.719> the<01:11:56.920> contract<01:11:57.360> that<01:11:57.440> you<01:11:57.560> want 01:11:57.669 --> 01:11:57.679 align:start position:0% function in the contract that you want 01:11:57.679 --> 01:12:00.070 align:start position:0% function in the contract that you want to<01:11:57.840> hit<01:11:58.320> so<01:11:58.560> all<01:11:58.679> of<01:11:58.880> this<01:11:59.280> is<01:11:59.560> actually 01:12:00.070 --> 01:12:00.080 align:start position:0% to hit so all of this is actually 01:12:00.080 --> 01:12:02.590 align:start position:0% to hit so all of this is actually abstracted<01:12:00.679> for<01:12:00.960> you<01:12:01.639> and<01:12:01.880> we<01:12:02.000> are<01:12:02.199> handling 01:12:02.590 --> 01:12:02.600 align:start position:0% abstracted for you and we are handling 01:12:02.600 --> 01:12:04.790 align:start position:0% abstracted for you and we are handling all<01:12:02.800> these<01:12:02.960> process<01:12:03.560> so<01:12:03.719> for<01:12:03.920> you<01:12:04.199> you<01:12:04.400> only 01:12:04.790 --> 01:12:04.800 align:start position:0% all these process so for you you only 01:12:04.800 --> 01:12:06.830 align:start position:0% all these process so for you you only would<01:12:04.960> be<01:12:05.120> needing<01:12:05.360> to<01:12:05.560> deploy<01:12:05.920> a<01:12:06.080> contract 01:12:06.830 --> 01:12:06.840 align:start position:0% would be needing to deploy a contract 01:12:06.840 --> 01:12:09.390 align:start position:0% would be needing to deploy a contract and<01:12:07.080> hit<01:12:07.400> our<01:12:07.719> API<01:12:08.360> with<01:12:08.520> the<01:12:08.679> specifications 01:12:09.390 --> 01:12:09.400 align:start position:0% and hit our API with the specifications 01:12:09.400 --> 01:12:12.950 align:start position:0% and hit our API with the specifications that<01:12:09.600> me<01:12:09.920> uh<01:12:10.040> that<01:12:10.159> was 01:12:12.950 --> 01:12:12.960 align:start position:0% 01:12:12.960 --> 01:12:18.750 align:start position:0% mentioned<01:12:13.960> cool 01:12:18.750 --> 01:12:18.760 align:start position:0% 01:12:18.760 --> 01:12:24.149 align:start position:0% um<01:12:19.760> all<01:12:20.080> this<01:12:20.199> is<01:12:20.360> taking 01:12:24.149 --> 01:12:24.159 align:start position:0% 01:12:24.159 --> 01:12:29.350 align:start position:0% time<01:12:25.239> was<01:12:25.600> this<01:12:26.400> clear<01:12:27.400> anyone<01:12:27.760> having 01:12:29.350 --> 01:12:29.360 align:start position:0% time was this clear anyone having 01:12:29.360 --> 01:13:19.669 align:start position:0% time was this clear anyone having issues<01:12:30.360> yes 01:13:19.669 --> 01:13:19.679 align:start position:0% 01:13:19.679 --> 01:13:43.510 align:start position:0% that<01:13:19.880> sh 01:13:43.510 --> 01:13:43.520 align:start position:0% 01:13:43.520 --> 01:14:24.030 align:start position:0% I<01:13:43.960> think<01:13:44.960> stage 01:14:24.030 --> 01:14:24.040 align:start position:0% 01:14:24.040 --> 01:14:53.990 align:start position:0% think 01:14:53.990 --> 01:14:54.000 align:start position:0% 01:14:54.000 --> 01:15:23.950 align:start position:0% e 01:15:23.950 --> 01:15:23.960 align:start position:0% 01:15:23.960 --> 01:15:33.030 align:start position:0% for 01:15:33.030 --> 01:15:33.040 align:start position:0% 01:15:33.040 --> 01:15:53.910 align:start position:0% [Music] 01:15:53.910 --> 01:15:53.920 align:start position:0% 01:15:53.920 --> 01:16:20.870 align:start position:0% for<01:15:54.960> for 01:16:20.870 --> 01:16:20.880 align:start position:0% 01:16:20.880 --> 01:16:32.790 align:start position:0% [Music] 01:16:32.790 --> 01:16:32.800 align:start position:0% 01:16:32.800 --> 01:17:04.500 align:start position:0% [Music] 01:17:04.500 --> 01:17:04.510 align:start position:0% 01:17:04.510 --> 01:17:31.590 align:start position:0% [Music] 01:17:31.590 --> 01:17:31.600 align:start position:0% 01:17:31.600 --> 01:17:33.790 align:start position:0% uh<01:17:32.600> okay<01:17:32.920> can<01:17:33.000> you<01:17:33.120> just<01:17:33.199> tell<01:17:33.320> them<01:17:33.440> to 01:17:33.790 --> 01:17:33.800 align:start position:0% uh okay can you just tell them to 01:17:33.800 --> 01:17:36.980 align:start position:0% uh okay can you just tell them to minutes<01:17:34.120> late<01:17:34.320> and<01:17:34.880> help<01:17:35.880> can<01:17:35.960> you<01:17:36.159> can<01:17:36.239> you 01:17:36.980 --> 01:17:36.990 align:start position:0% minutes late and help can you can you 01:17:36.990 --> 01:17:42.470 align:start position:0% minutes late and help can you can you [Music] 01:17:42.470 --> 01:17:42.480 align:start position:0% [Music] 01:17:42.480 --> 01:17:53.830 align:start position:0% [Music] help<01:17:43.480> okay<01:17:43.679> that's<01:17:43.880> fine<01:17:44.280> okay<01:17:44.480> yeah<01:17:45.120> see 01:17:53.830 --> 01:17:53.840 align:start position:0% 01:17:53.840 --> 01:18:49.470 align:start position:0% you<01:17:54.840> for 01:18:49.470 --> 01:18:49.480 align:start position:0% 01:18:49.480 --> 01:18:58.030 align:start position:0% good 01:18:58.030 --> 01:18:58.040 align:start position:0% 01:18:58.040 --> 01:18:59.550 align:start position:0% Okay<01:18:58.320> cool<01:18:58.520> so<01:18:58.679> as<01:18:58.760> we're<01:18:58.920> coming<01:18:59.080> to<01:18:59.239> the<01:18:59.400> last 01:18:59.550 --> 01:18:59.560 align:start position:0% Okay cool so as we're coming to the last 01:18:59.560 --> 01:19:00.830 align:start position:0% Okay cool so as we're coming to the last seven<01:18:59.800> minutes<01:19:00.120> here<01:19:00.320> maybe<01:19:00.560> I'll<01:19:00.719> just 01:19:00.830 --> 01:19:00.840 align:start position:0% seven minutes here maybe I'll just 01:19:00.840 --> 01:19:03.350 align:start position:0% seven minutes here maybe I'll just address<01:19:01.120> some<01:19:01.239> of<01:19:01.360> the<01:19:01.560> last<01:19:01.800> few<01:19:02.800> uh<01:19:03.000> last<01:19:03.159> few 01:19:03.350 --> 01:19:03.360 align:start position:0% address some of the last few uh last few 01:19:03.360 --> 01:19:05.430 align:start position:0% address some of the last few uh last few notes<01:19:03.920> um<01:19:04.120> some<01:19:04.280> folks<01:19:04.520> mentioned<01:19:05.000> wanting<01:19:05.280> to 01:19:05.430 --> 01:19:05.440 align:start position:0% notes um some folks mentioned wanting to 01:19:05.440 --> 01:19:07.750 align:start position:0% notes um some folks mentioned wanting to self<01:19:05.840> host<01:19:06.440> if<01:19:06.520> you<01:19:06.639> go<01:19:06.760> to<01:19:06.920> this<01:19:07.040> repo<01:19:07.440> on 01:19:07.750 --> 01:19:07.760 align:start position:0% self host if you go to this repo on 01:19:07.760 --> 01:19:10.189 align:start position:0% self host if you go to this repo on GitHub<01:19:08.760> um<01:19:09.320> you<01:19:09.400> can<01:19:09.560> basically<01:19:09.840> clone<01:19:10.080> it 01:19:10.189 --> 01:19:10.199 align:start position:0% GitHub um you can basically clone it 01:19:10.199 --> 01:19:11.470 align:start position:0% GitHub um you can basically clone it locally<01:19:10.480> and<01:19:10.560> you'll<01:19:10.760> see<01:19:10.920> all<01:19:11.040> the<01:19:11.159> packages 01:19:11.470 --> 01:19:11.480 align:start position:0% locally and you'll see all the packages 01:19:11.480 --> 01:19:13.310 align:start position:0% locally and you'll see all the packages and<01:19:11.600> infrastructure<01:19:12.199> that<01:19:12.639> this<01:19:12.840> relies<01:19:13.159> on 01:19:13.310 --> 01:19:13.320 align:start position:0% and infrastructure that this relies on 01:19:13.320 --> 01:19:14.910 align:start position:0% and infrastructure that this relies on and<01:19:13.400> you<01:19:13.520> can<01:19:13.760> self<01:19:14.080> host<01:19:14.280> the<01:19:14.360> relayer<01:19:14.760> if<01:19:14.840> you 01:19:14.910 --> 01:19:14.920 align:start position:0% and you can self host the relayer if you 01:19:14.920 --> 01:19:17.070 align:start position:0% and you can self host the relayer if you want<01:19:15.760> um<01:19:15.880> and<01:19:16.040> the<01:19:16.199> API<01:19:16.520> interface<01:19:16.800> should<01:19:16.920> be 01:19:17.070 --> 01:19:17.080 align:start position:0% want um and the API interface should be 01:19:17.080 --> 01:19:19.750 align:start position:0% want um and the API interface should be exactly<01:19:17.400> the<01:19:17.520> same<01:19:18.520> um<01:19:19.320> if<01:19:19.400> you<01:19:19.520> want<01:19:19.639> to 01:19:19.750 --> 01:19:19.760 align:start position:0% exactly the same um if you want to 01:19:19.760 --> 01:19:21.149 align:start position:0% exactly the same um if you want to integrate<01:19:20.120> any<01:19:20.239> one<01:19:20.360> of<01:19:20.440> the<01:19:20.639> specific<01:19:20.960> things 01:19:21.149 --> 01:19:21.159 align:start position:0% integrate any one of the specific things 01:19:21.159 --> 01:19:22.470 align:start position:0% integrate any one of the specific things like<01:19:21.320> account<01:19:21.560> recovery<01:19:21.880> on<01:19:21.960> the<01:19:22.040> left<01:19:22.239> email 01:19:22.470 --> 01:19:22.480 align:start position:0% like account recovery on the left email 01:19:22.480 --> 01:19:24.270 align:start position:0% like account recovery on the left email signers<01:19:23.040> oath<01:19:23.360> login<01:19:23.560> or<01:19:23.679> email<01:19:23.920> wall<01:19:24.159> that's 01:19:24.270 --> 01:19:24.280 align:start position:0% signers oath login or email wall that's 01:19:24.280 --> 01:19:25.550 align:start position:0% signers oath login or email wall that's already<01:19:24.440> been<01:19:24.520> built<01:19:24.719> built<01:19:24.880> and<01:19:25.000> audited<01:19:25.360> for 01:19:25.550 --> 01:19:25.560 align:start position:0% already been built built and audited for 01:19:25.560 --> 01:19:27.870 align:start position:0% already been built built and audited for you<01:19:26.239> um<01:19:26.400> you<01:19:26.480> can<01:19:26.600> use<01:19:26.719> one<01:19:26.840> of<01:19:26.920> these<01:19:27.040> four<01:19:27.280> QR 01:19:27.870 --> 01:19:27.880 align:start position:0% you um you can use one of these four QR 01:19:27.880 --> 01:19:31.430 align:start position:0% you um you can use one of these four QR codes<01:19:28.880> um<01:19:29.440> and<01:19:29.600> if<01:19:29.679> you<01:19:30.000> want<01:19:31.000> um<01:19:31.199> these<01:19:31.280> are 01:19:31.430 --> 01:19:31.440 align:start position:0% codes um and if you want um these are 01:19:31.440 --> 01:19:33.510 align:start position:0% codes um and if you want um these are the<01:19:31.520> main<01:19:31.960> QR<01:19:32.280> codes<01:19:32.800> questions<01:19:33.080> on<01:19:33.199> the<01:19:33.320> left 01:19:33.510 --> 01:19:33.520 align:start position:0% the main QR codes questions on the left 01:19:33.520 --> 01:19:35.310 align:start position:0% the main QR codes questions on the left side<01:19:33.719> on<01:19:33.840> the<01:19:33.960> telegram<01:19:34.679> our<01:19:34.880> website<01:19:35.159> in<01:19:35.239> the 01:19:35.310 --> 01:19:35.320 align:start position:0% side on the telegram our website in the 01:19:35.320 --> 01:19:37.590 align:start position:0% side on the telegram our website in the middle<01:19:35.520> at<01:19:35.600> zk.<01:19:36.000> email<01:19:36.719> and<01:19:37.080> these<01:19:37.199> slides<01:19:37.520> on 01:19:37.590 --> 01:19:37.600 align:start position:0% middle at zk. email and these slides on 01:19:37.600 --> 01:19:38.870 align:start position:0% middle at zk. email and these slides on the<01:19:37.719> right<01:19:37.920> side<01:19:38.120> so<01:19:38.239> you<01:19:38.320> can<01:19:38.480> kind<01:19:38.600> of<01:19:38.719> go 01:19:38.870 --> 01:19:38.880 align:start position:0% the right side so you can kind of go 01:19:38.880 --> 01:19:40.229 align:start position:0% the right side so you can kind of go through<01:19:39.040> yourself<01:19:39.400> and<01:19:39.520> be<01:19:39.639> like<01:19:39.840> oh<01:19:40.159> what 01:19:40.229 --> 01:19:40.239 align:start position:0% through yourself and be like oh what 01:19:40.239 --> 01:19:41.629 align:start position:0% through yourself and be like oh what were<01:19:40.400> all<01:19:40.480> those<01:19:40.639> other<01:19:40.840> QR<01:19:41.159> codes<01:19:41.400> that<01:19:41.520> I 01:19:41.629 --> 01:19:41.639 align:start position:0% were all those other QR codes that I 01:19:41.639 --> 01:19:44.590 align:start position:0% were all those other QR codes that I missed<01:19:42.639> um<01:19:43.159> so<01:19:43.360> these<01:19:43.480> are<01:19:43.719> kind<01:19:43.840> of<01:19:44.000> the<01:19:44.159> most 01:19:44.590 --> 01:19:44.600 align:start position:0% missed um so these are kind of the most 01:19:44.600 --> 01:19:46.790 align:start position:0% missed um so these are kind of the most important<01:19:44.960> things<01:19:45.120> to<01:19:45.280> scan<01:19:46.280> um<01:19:46.520> and<01:19:46.639> we'll 01:19:46.790 --> 01:19:46.800 align:start position:0% important things to scan um and we'll 01:19:46.800 --> 01:19:47.910 align:start position:0% important things to scan um and we'll kind<01:19:46.920> of<01:19:47.040> be<01:19:47.199> around<01:19:47.400> to<01:19:47.520> keep<01:19:47.679> taking 01:19:47.910 --> 01:19:47.920 align:start position:0% kind of be around to keep taking 01:19:47.920 --> 01:19:49.470 align:start position:0% kind of be around to keep taking questions<01:19:48.280> but<01:19:48.440> I'm<01:19:48.719> I'm<01:19:48.880> hoping<01:19:49.120> that<01:19:49.280> people 01:19:49.470 --> 01:19:49.480 align:start position:0% questions but I'm I'm hoping that people 01:19:49.480 --> 01:19:52.870 align:start position:0% questions but I'm I'm hoping that people came<01:19:49.679> away<01:19:49.920> from<01:19:50.159> this<01:19:51.120> um<01:19:52.120> with<01:19:52.239> a<01:19:52.400> sense<01:19:52.639> of 01:19:52.870 --> 01:19:52.880 align:start position:0% came away from this um with a sense of 01:19:52.880 --> 01:19:54.990 align:start position:0% came away from this um with a sense of like<01:19:53.280> one<01:19:53.560> how<01:19:53.679> can<01:19:53.800> I<01:19:53.960> define<01:19:54.280> proofs<01:19:54.840> of 01:19:54.990 --> 01:19:55.000 align:start position:0% like one how can I define proofs of 01:19:55.000 --> 01:19:57.669 align:start position:0% like one how can I define proofs of emails<01:19:55.360> in<01:19:55.480> my<01:19:55.600> inbox<01:19:56.400> even<01:19:56.600> if<01:19:56.800> potentially 01:19:57.669 --> 01:19:57.679 align:start position:0% emails in my inbox even if potentially 01:19:57.679 --> 01:20:00.510 align:start position:0% emails in my inbox even if potentially you<01:19:57.800> know<01:19:58.080> we<01:19:58.320> we<01:19:58.440> didn't<01:19:59.199> exactly<01:20:00.120> get<01:20:00.280> all<01:20:00.400> of 01:20:00.510 --> 01:20:00.520 align:start position:0% you know we we didn't exactly get all of 01:20:00.520 --> 01:20:02.350 align:start position:0% you know we we didn't exactly get all of them<01:20:00.679> compiling<01:20:01.480> um<01:20:01.639> hopefully<01:20:02.159> that<01:20:02.280> at 01:20:02.350 --> 01:20:02.360 align:start position:0% them compiling um hopefully that at 01:20:02.360 --> 01:20:04.149 align:start position:0% them compiling um hopefully that at least<01:20:02.600> gave<01:20:02.800> folks<01:20:03.040> some<01:20:03.199> insight<01:20:03.880> and<01:20:03.960> then 01:20:04.149 --> 01:20:04.159 align:start position:0% least gave folks some insight and then 01:20:04.159 --> 01:20:06.350 align:start position:0% least gave folks some insight and then also<01:20:04.440> how<01:20:04.560> can<01:20:04.679> I<01:20:04.840> get<01:20:05.000> proofs<01:20:05.880> of<01:20:06.040> emails 01:20:06.350 --> 01:20:06.360 align:start position:0% also how can I get proofs of emails 01:20:06.360 --> 01:20:07.790 align:start position:0% also how can I get proofs of emails triggering<01:20:06.679> onchain<01:20:07.040> transactions<01:20:07.600> I<01:20:07.679> hope 01:20:07.790 --> 01:20:07.800 align:start position:0% triggering onchain transactions I hope 01:20:07.800 --> 01:20:09.390 align:start position:0% triggering onchain transactions I hope people<01:20:08.000> got<01:20:08.120> at<01:20:08.239> least<01:20:08.360> an<01:20:08.480> idea<01:20:08.719> of<01:20:09.040> here's<01:20:09.239> an 01:20:09.390 --> 01:20:09.400 align:start position:0% people got at least an idea of here's an 01:20:09.400 --> 01:20:11.270 align:start position:0% people got at least an idea of here's an MVP<01:20:09.800> way<01:20:09.920> to<01:20:10.040> do<01:20:10.199> it<01:20:10.440> when<01:20:10.600> I<01:20:10.719> want<01:20:10.840> to<01:20:10.920> put<01:20:11.080> into 01:20:11.270 --> 01:20:11.280 align:start position:0% MVP way to do it when I want to put into 01:20:11.280 --> 01:20:12.590 align:start position:0% MVP way to do it when I want to put into production<01:20:11.639> I<01:20:11.679> can<01:20:11.800> use<01:20:11.960> one<01:20:12.040> of<01:20:12.120> the<01:20:12.239> audited 01:20:12.590 --> 01:20:12.600 align:start position:0% production I can use one of the audited 01:20:12.600 --> 01:20:15.510 align:start position:0% production I can use one of the audited versions<01:20:12.920> up<01:20:13.159> here<01:20:13.639> or<01:20:13.880> I<01:20:13.960> can<01:20:14.239> kind<01:20:14.440> of<01:20:14.880> uh<01:20:15.400> you 01:20:15.510 --> 01:20:15.520 align:start position:0% versions up here or I can kind of uh you 01:20:15.520 --> 01:20:17.430 align:start position:0% versions up here or I can kind of uh you know<01:20:15.719> read<01:20:15.920> the<01:20:16.080> docs<01:20:16.440> and<01:20:16.679> and<01:20:16.920> build<01:20:17.159> one 01:20:17.430 --> 01:20:17.440 align:start position:0% know read the docs and and build one 01:20:17.440 --> 01:20:19.510 align:start position:0% know read the docs and and build one myself<01:20:18.360> um<01:20:18.560> again<01:20:18.800> please<01:20:19.000> ask<01:20:19.199> questions<01:20:19.400> in 01:20:19.510 --> 01:20:19.520 align:start position:0% myself um again please ask questions in 01:20:19.520 --> 01:20:22.070 align:start position:0% myself um again please ask questions in our<01:20:19.679> Telegram<01:20:20.679> and<01:20:20.840> we<01:20:20.960> will<01:20:21.120> be<01:20:21.320> around<01:20:21.960> the 01:20:22.070 --> 01:20:22.080 align:start position:0% our Telegram and we will be around the 01:20:22.080 --> 01:20:23.950 align:start position:0% our Telegram and we will be around the ZK<01:20:22.400> email<01:20:22.719> impact<01:20:23.040> booth<01:20:23.320> for<01:20:23.440> the<01:20:23.560> next<01:20:23.719> two 01:20:23.950 --> 01:20:23.960 align:start position:0% ZK email impact booth for the next two 01:20:23.960 --> 01:20:26.830 align:start position:0% ZK email impact booth for the next two days<01:20:24.920> um<01:20:25.280> it's<01:20:25.520> kind<01:20:25.679> of<01:20:26.239> on<01:20:26.400> the<01:20:26.520> opposite 01:20:26.830 --> 01:20:26.840 align:start position:0% days um it's kind of on the opposite 01:20:26.840 --> 01:20:29.709 align:start position:0% days um it's kind of on the opposite corner<01:20:27.199> of<01:20:27.320> the<01:20:27.440> building<01:20:27.920> on<01:20:28.120> this<01:20:28.400> floor<01:20:29.400> um 01:20:29.709 --> 01:20:29.719 align:start position:0% corner of the building on this floor um 01:20:29.719 --> 01:20:31.110 align:start position:0% corner of the building on this floor um there's<01:20:29.880> a<01:20:30.000> bunch<01:20:30.159> of<01:20:30.320> impact<01:20:30.600> boots<01:20:30.960> and<01:20:31.040> you 01:20:31.110 --> 01:20:31.120 align:start position:0% there's a bunch of impact boots and you 01:20:31.120 --> 01:20:32.470 align:start position:0% there's a bunch of impact boots and you can<01:20:31.239> see<01:20:31.440> us<01:20:31.560> you<01:20:31.679> can<01:20:31.800> come<01:20:31.920> to<01:20:32.040> us<01:20:32.159> you<01:20:32.280> can<01:20:32.360> be 01:20:32.470 --> 01:20:32.480 align:start position:0% can see us you can come to us you can be 01:20:32.480 --> 01:20:34.110 align:start position:0% can see us you can come to us you can be like<01:20:32.679> hey<01:20:33.159> I<01:20:33.280> really<01:20:33.480> wanted<01:20:33.760> to<01:20:33.880> get<01:20:34.000> the 01:20:34.110 --> 01:20:34.120 align:start position:0% like hey I really wanted to get the 01:20:34.120 --> 01:20:36.350 align:start position:0% like hey I really wanted to get the proof<01:20:34.440> from<01:20:34.600> my<01:20:34.800> workshop<01:20:35.199> compiling<01:20:36.080> can<01:20:36.239> you 01:20:36.350 --> 01:20:36.360 align:start position:0% proof from my workshop compiling can you 01:20:36.360 --> 01:20:37.470 align:start position:0% proof from my workshop compiling can you help<01:20:36.560> me<01:20:36.679> and<01:20:36.800> some<01:20:36.920> of<01:20:37.000> them<01:20:37.080> will<01:20:37.199> be<01:20:37.320> at<01:20:37.400> the 01:20:37.470 --> 01:20:37.480 align:start position:0% help me and some of them will be at the 01:20:37.480 --> 01:20:38.590 align:start position:0% help me and some of them will be at the booth<01:20:37.679> and<01:20:37.800> we<01:20:37.880> will<01:20:38.080> get<01:20:38.199> the<01:20:38.360> thing 01:20:38.590 --> 01:20:38.600 align:start position:0% booth and we will get the thing 01:20:38.600 --> 01:20:41.350 align:start position:0% booth and we will get the thing compiling<01:20:39.480> um<01:20:40.199> and<01:20:40.360> so<01:20:40.719> yeah<01:20:40.880> definitely<01:20:41.199> meet 01:20:41.350 --> 01:20:41.360 align:start position:0% compiling um and so yeah definitely meet 01:20:41.360 --> 01:20:42.990 align:start position:0% compiling um and so yeah definitely meet us<01:20:41.440> at<01:20:41.560> the<01:20:41.639> impact<01:20:41.920> Booth<01:20:42.159> if<01:20:42.239> you<01:20:42.360> want<01:20:42.600> more 01:20:42.990 --> 01:20:43.000 align:start position:0% us at the impact Booth if you want more 01:20:43.000 --> 01:20:44.910 align:start position:0% us at the impact Booth if you want more information<01:20:44.000> um<01:20:44.280> and<01:20:44.360> if<01:20:44.440> you<01:20:44.560> like<01:20:44.679> account 01:20:44.910 --> 01:20:44.920 align:start position:0% information um and if you like account 01:20:44.920 --> 01:20:46.110 align:start position:0% information um and if you like account atraction<01:20:45.400> you<01:20:45.440> want<01:20:45.520> to<01:20:45.600> debate<01:20:45.840> it<01:20:45.920> with<01:20:46.000> us 01:20:46.110 --> 01:20:46.120 align:start position:0% atraction you want to debate it with us 01:20:46.120 --> 01:20:47.110 align:start position:0% atraction you want to debate it with us we'll<01:20:46.239> be<01:20:46.320> at<01:20:46.400> the<01:20:46.480> account<01:20:46.760> exraction 01:20:47.110 --> 01:20:47.120 align:start position:0% we'll be at the account exraction 01:20:47.120 --> 01:20:49.709 align:start position:0% we'll be at the account exraction Community<01:20:47.560> Hub<01:20:48.480> um<01:20:49.080> yeah<01:20:49.280> definitely<01:20:49.560> come 01:20:49.709 --> 01:20:49.719 align:start position:0% Community Hub um yeah definitely come 01:20:49.719 --> 01:20:51.750 align:start position:0% Community Hub um yeah definitely come see<01:20:49.880> us<01:20:49.960> at<01:20:50.120> any<01:20:50.239> of<01:20:50.440> these<01:20:51.159> um<01:20:51.280> but<01:20:51.360> I'll<01:20:51.520> leave 01:20:51.750 --> 01:20:51.760 align:start position:0% see us at any of these um but I'll leave 01:20:51.760 --> 01:20:53.590 align:start position:0% see us at any of these um but I'll leave these<01:20:51.960> up<01:20:52.480> for<01:20:52.880> for<01:20:53.040> another<01:20:53.320> like<01:20:53.440> few 01:20:53.590 --> 01:20:53.600 align:start position:0% these up for for another like few 01:20:53.600 --> 01:20:56.149 align:start position:0% these up for for another like few minutes<01:20:53.960> and<01:20:54.080> hopefully<01:20:54.360> folks<01:20:54.920> can<01:20:55.360> uh<01:20:55.960> can 01:20:56.149 --> 01:20:56.159 align:start position:0% minutes and hopefully folks can uh can 01:20:56.159 --> 01:20:57.910 align:start position:0% minutes and hopefully folks can uh can grab<01:20:56.600> these 01:20:57.910 --> 01:20:57.920 align:start position:0% grab these 01:20:57.920 --> 01:21:00.070 align:start position:0% grab these and<01:20:58.920> yeah<01:20:59.120> keep<01:20:59.280> keep<01:20:59.440> asking<01:20:59.639> us<01:20:59.840> questions 01:21:00.070 --> 01:21:00.080 align:start position:0% and yeah keep keep asking us questions 01:21:00.080 --> 01:21:01.189 align:start position:0% and yeah keep keep asking us questions me<01:21:00.280> said<01:21:00.360> the<01:21:00.440> impact<01:21:00.679> Bo<01:21:00.800> if<01:21:00.840> you<01:21:01.000> didn't<01:21:01.120> get 01:21:01.189 --> 01:21:01.199 align:start position:0% me said the impact Bo if you didn't get 01:21:01.199 --> 01:21:03.669 align:start position:0% me said the impact Bo if you didn't get it<01:21:01.320> compiled<01:21:02.239> um<01:21:02.600> sweet<01:21:02.960> thank<01:21:03.120> you<01:21:03.199> for 01:21:03.669 --> 01:21:03.679 align:start position:0% it compiled um sweet thank you for 01:21:03.679 --> 01:21:06.590 align:start position:0% it compiled um sweet thank you for coming<01:21:04.679> um<01:21:05.440> and<01:21:05.600> I<01:21:05.719> hope<01:21:05.960> that<01:21:06.199> people<01:21:06.400> were 01:21:06.590 --> 01:21:06.600 align:start position:0% coming um and I hope that people were 01:21:06.600 --> 01:21:07.950 align:start position:0% coming um and I hope that people were able<01:21:06.760> to<01:21:06.880> learn<01:21:07.120> at<01:21:07.239> least<01:21:07.400> something<01:21:07.719> from 01:21:07.950 --> 01:21:07.960 align:start position:0% able to learn at least something from 01:21:07.960 --> 01:21:09.110 align:start position:0% able to learn at least something from this<01:21:08.120> and<01:21:08.239> we<01:21:08.360> also<01:21:08.480> have<01:21:08.560> a<01:21:08.679> talk<01:21:08.920> that<01:21:09.000> we 01:21:09.110 --> 01:21:09.120 align:start position:0% this and we also have a talk that we 01:21:09.120 --> 01:21:10.990 align:start position:0% this and we also have a talk that we gave<01:21:09.320> yesterday<01:21:09.800> that<01:21:10.120> will<01:21:10.280> be<01:21:10.440> live<01:21:10.719> stream 01:21:10.990 --> 01:21:11.000 align:start position:0% gave yesterday that will be live stream 01:21:11.000 --> 01:21:12.709 align:start position:0% gave yesterday that will be live stream that<01:21:11.120> you<01:21:11.440> um<01:21:11.920> that<01:21:12.040> was<01:21:12.239> live<01:21:12.400> stream<01:21:12.639> that 01:21:12.709 --> 01:21:12.719 align:start position:0% that you um that was live stream that 01:21:12.719 --> 01:21:14.990 align:start position:0% that you um that was live stream that you<01:21:12.800> can<01:21:13.000> go<01:21:13.239> and<01:21:13.760> and<01:21:13.920> listen<01:21:14.239> on<01:21:14.520> like<01:21:14.760> okay 01:21:14.990 --> 01:21:15.000 align:start position:0% you can go and and listen on like okay 01:21:15.000 --> 01:21:16.550 align:start position:0% you can go and and listen on like okay how<01:21:15.400> exactly<01:21:15.760> does<01:21:15.880> all<01:21:16.040> this<01:21:16.159> stuff<01:21:16.320> even 01:21:16.550 --> 01:21:16.560 align:start position:0% how exactly does all this stuff even 01:21:16.560 --> 01:21:18.070 align:start position:0% how exactly does all this stuff even work<01:21:17.280> like<01:21:17.400> what<01:21:17.520> is<01:21:17.639> happening<01:21:17.880> in<01:21:17.960> the 01:21:18.070 --> 01:21:18.080 align:start position:0% work like what is happening in the 01:21:18.080 --> 01:21:19.189 align:start position:0% work like what is happening in the background<01:21:18.400> and<01:21:18.480> you<01:21:18.600> can<01:21:18.719> get<01:21:18.800> a<01:21:18.920> lot<01:21:19.040> more 01:21:19.189 --> 01:21:19.199 align:start position:0% background and you can get a lot more 01:21:19.199 --> 01:21:21.310 align:start position:0% background and you can get a lot more insight<01:21:19.480> from<01:21:19.679> that<01:21:19.840> and<01:21:19.960> our<01:21:20.199> docs<01:21:21.000> okay 01:21:21.310 --> 01:21:21.320 align:start position:0% insight from that and our docs okay 01:21:21.320 --> 01:21:53.510 align:start position:0% insight from that and our docs okay thank<01:21:21.480> you<01:21:21.679> guys 01:21:53.510 --> 01:21:53.520 align:start position:0% 01:21:53.520 --> 01:22:24.629 align:start position:0% dish<01:21:54.560> for 01:22:24.629 --> 01:22:24.639 align:start position:0% 01:22:24.639 --> 01:22:27.639 align:start position:0% to