WEBVTT Kind: captions Language: en 00:00:05.070 --> 00:00:14.910 align:start position:0% [Music] 00:00:14.910 --> 00:00:14.920 align:start position:0% 00:00:14.920 --> 00:00:19.349 align:start position:0% [Music] 00:00:19.349 --> 00:00:19.359 align:start position:0% 00:00:19.359 --> 00:00:22.310 align:start position:0% hello<00:00:20.359> my<00:00:20.480> name<00:00:20.680> is<00:00:20.840> Connor<00:00:21.600> and<00:00:21.920> I<00:00:22.000> am<00:00:22.160> a 00:00:22.310 --> 00:00:22.320 align:start position:0% hello my name is Connor and I am a 00:00:22.320 --> 00:00:25.310 align:start position:0% hello my name is Connor and I am a developer<00:00:22.800> at<00:00:23.400> consensus<00:00:24.400> um<00:00:25.000> I've<00:00:25.199> been 00:00:25.310 --> 00:00:25.320 align:start position:0% developer at consensus um I've been 00:00:25.320 --> 00:00:28.349 align:start position:0% developer at consensus um I've been working<00:00:25.680> on<00:00:26.160> a<00:00:26.800> uh<00:00:26.960> platform<00:00:27.480> for<00:00:28.119> having 00:00:28.349 --> 00:00:28.359 align:start position:0% working on a uh platform for having 00:00:28.359 --> 00:00:30.550 align:start position:0% working on a uh platform for having threaded<00:00:28.840> discussions<00:00:29.720> that<00:00:30.000> are<00:00:30.439> difficult 00:00:30.550 --> 00:00:30.560 align:start position:0% threaded discussions that are difficult 00:00:30.560 --> 00:00:33.750 align:start position:0% threaded discussions that are difficult to<00:00:31.040> censor<00:00:32.040> um<00:00:32.279> they<00:00:32.520> are<00:00:32.800> built<00:00:33.239> using 00:00:33.750 --> 00:00:33.760 align:start position:0% to censor um they are built using 00:00:33.760 --> 00:00:35.869 align:start position:0% to censor um they are built using ethereum<00:00:34.640> ipfs<00:00:35.160> and 00:00:35.869 --> 00:00:35.879 align:start position:0% ethereum ipfs and 00:00:35.879 --> 00:00:38.430 align:start position:0% ethereum ipfs and Whisper<00:00:36.879> and<00:00:37.280> I'm<00:00:37.719> the<00:00:37.800> first<00:00:38.079> part<00:00:38.200> of<00:00:38.280> my 00:00:38.430 --> 00:00:38.440 align:start position:0% Whisper and I'm the first part of my 00:00:38.440 --> 00:00:40.270 align:start position:0% Whisper and I'm the first part of my talk<00:00:38.640> I'm<00:00:38.719> going<00:00:38.840> to<00:00:39.520> explain<00:00:39.879> how<00:00:40.039> you<00:00:40.120> could 00:00:40.270 --> 00:00:40.280 align:start position:0% talk I'm going to explain how you could 00:00:40.280 --> 00:00:42.389 align:start position:0% talk I'm going to explain how you could use<00:00:40.559> this<00:00:40.800> as<00:00:40.920> a<00:00:41.280> a<00:00:41.399> foundation<00:00:41.879> for<00:00:42.079> building 00:00:42.389 --> 00:00:42.399 align:start position:0% use this as a a foundation for building 00:00:42.399 --> 00:00:44.630 align:start position:0% use this as a a foundation for building a<00:00:42.559> decentralized<00:00:43.200> Reddit<00:00:44.000> really<00:00:44.320> like<00:00:44.480> an 00:00:44.630 --> 00:00:44.640 align:start position:0% a decentralized Reddit really like an 00:00:44.640 --> 00:00:46.630 align:start position:0% a decentralized Reddit really like an ecosystem<00:00:45.320> more<00:00:45.520> than<00:00:45.719> like<00:00:45.960> one<00:00:46.199> particular 00:00:46.630 --> 00:00:46.640 align:start position:0% ecosystem more than like one particular 00:00:46.640 --> 00:00:49.389 align:start position:0% ecosystem more than like one particular app<00:00:47.559> um<00:00:47.960> and<00:00:48.239> later<00:00:48.480> I'll<00:00:48.600> give<00:00:48.719> a<00:00:48.800> demo<00:00:49.079> and 00:00:49.389 --> 00:00:49.399 align:start position:0% app um and later I'll give a demo and 00:00:49.399 --> 00:00:51.830 align:start position:0% app um and later I'll give a demo and explain<00:00:49.680> some<00:00:49.800> more<00:00:50.039> technical<00:00:50.600> details<00:00:51.600> um 00:00:51.830 --> 00:00:51.840 align:start position:0% explain some more technical details um 00:00:51.840 --> 00:00:53.069 align:start position:0% explain some more technical details um so<00:00:52.039> the<00:00:52.120> working<00:00:52.399> title<00:00:52.680> right<00:00:52.800> now<00:00:52.920> is 00:00:53.069 --> 00:00:53.079 align:start position:0% so the working title right now is 00:00:53.079 --> 00:00:56.590 align:start position:0% so the working title right now is nonsense<00:00:53.559> like<00:00:53.680> not<00:00:53.800> easy<00:00:54.079> to<00:00:54.520> censor<00:00:55.520> um<00:00:55.960> and 00:00:56.590 --> 00:00:56.600 align:start position:0% nonsense like not easy to censor um and 00:00:56.600 --> 00:00:58.389 align:start position:0% nonsense like not easy to censor um and why<00:00:56.719> would<00:00:56.879> we<00:00:57.000> want<00:00:57.160> a<00:00:57.280> decentralized<00:00:57.879> Reddit 00:00:58.389 --> 00:00:58.399 align:start position:0% why would we want a decentralized Reddit 00:00:58.399 --> 00:01:01.470 align:start position:0% why would we want a decentralized Reddit so<00:00:59.199> many<00:00:59.399> people<00:00:59.719> here<00:01:00.199> probably<00:01:01.000> uh<00:01:01.160> Venture 00:01:01.470 --> 00:01:01.480 align:start position:0% so many people here probably uh Venture 00:01:01.480 --> 00:01:03.389 align:start position:0% so many people here probably uh Venture into<00:01:01.719> the<00:01:01.840> r<00:01:02.039> Bitcoin<00:01:02.600> sometimes<00:01:03.000> and<00:01:03.239> have 00:01:03.389 --> 00:01:03.399 align:start position:0% into the r Bitcoin sometimes and have 00:01:03.399 --> 00:01:05.189 align:start position:0% into the r Bitcoin sometimes and have noticed<00:01:03.760> that<00:01:03.960> they<00:01:04.479> generally<00:01:05.080> the 00:01:05.189 --> 00:01:05.199 align:start position:0% noticed that they generally the 00:01:05.199 --> 00:01:08.550 align:start position:0% noticed that they generally the moderators<00:01:05.640> receive<00:01:05.880> a<00:01:05.960> lot<00:01:06.040> of<00:01:06.159> heat<00:01:06.880> for<00:01:07.759> um 00:01:08.550 --> 00:01:08.560 align:start position:0% moderators receive a lot of heat for um 00:01:08.560 --> 00:01:11.590 align:start position:0% moderators receive a lot of heat for um questionable<00:01:09.560> uh<00:01:09.680> moderation<00:01:10.240> policies<00:01:11.240> um 00:01:11.590 --> 00:01:11.600 align:start position:0% questionable uh moderation policies um 00:01:11.600 --> 00:01:13.350 align:start position:0% questionable uh moderation policies um and<00:01:12.040> I<00:01:12.240> personally<00:01:12.600> noticed<00:01:12.960> that<00:01:13.119> as<00:01:13.240> the 00:01:13.350 --> 00:01:13.360 align:start position:0% and I personally noticed that as the 00:01:13.360 --> 00:01:15.230 align:start position:0% and I personally noticed that as the community<00:01:13.680> grew<00:01:14.320> during<00:01:14.799> the<00:01:14.920> rise<00:01:15.119> of 00:01:15.230 --> 00:01:15.240 align:start position:0% community grew during the rise of 00:01:15.240 --> 00:01:17.749 align:start position:0% community grew during the rise of Bitcoin<00:01:16.159> um<00:01:16.520> that<00:01:16.799> the<00:01:17.119> quality<00:01:17.520> of<00:01:17.640> the 00:01:17.749 --> 00:01:17.759 align:start position:0% Bitcoin um that the quality of the 00:01:17.759 --> 00:01:20.550 align:start position:0% Bitcoin um that the quality of the content<00:01:18.159> on<00:01:18.280> the<00:01:18.439> Moder<00:01:18.840> on<00:01:18.920> the<00:01:19.560> site 00:01:20.550 --> 00:01:20.560 align:start position:0% content on the Moder on the site 00:01:20.560 --> 00:01:22.950 align:start position:0% content on the Moder on the site actually<00:01:21.479> uh<00:01:21.759> suffered<00:01:22.159> more<00:01:22.280> and<00:01:22.439> more<00:01:22.799> due 00:01:22.950 --> 00:01:22.960 align:start position:0% actually uh suffered more and more due 00:01:22.960 --> 00:01:25.190 align:start position:0% actually uh suffered more and more due to<00:01:23.119> the<00:01:23.200> moderators<00:01:24.159> um<00:01:24.680> expressing<00:01:25.040> their 00:01:25.190 --> 00:01:25.200 align:start position:0% to the moderators um expressing their 00:01:25.200 --> 00:01:28.990 align:start position:0% to the moderators um expressing their own<00:01:25.520> agendas<00:01:26.600> so<00:01:27.600> this<00:01:27.759> even<00:01:28.040> applies<00:01:28.400> to<00:01:28.759> um 00:01:28.990 --> 00:01:29.000 align:start position:0% own agendas so this even applies to um 00:01:29.000 --> 00:01:31.190 align:start position:0% own agendas so this even applies to um to<00:01:29.159> people<00:01:29.400> who<00:01:29.520> are<00:01:30.360> uh<00:01:30.479> deeply<00:01:30.799> involved<00:01:31.079> in 00:01:31.190 --> 00:01:31.200 align:start position:0% to people who are uh deeply involved in 00:01:31.200 --> 00:01:32.710 align:start position:0% to people who are uh deeply involved in the<00:01:31.280> Bitcoin<00:01:31.600> space<00:01:31.880> where<00:01:32.200> we're<00:01:32.399> not<00:01:32.560> being 00:01:32.710 --> 00:01:32.720 align:start position:0% the Bitcoin space where we're not being 00:01:32.720 --> 00:01:34.749 align:start position:0% the Bitcoin space where we're not being able<00:01:32.920> to<00:01:33.040> voice<00:01:33.360> their<00:01:33.640> their<00:01:33.799> own<00:01:34.640> uh 00:01:34.749 --> 00:01:34.759 align:start position:0% able to voice their their own uh 00:01:34.759 --> 00:01:37.670 align:start position:0% able to voice their their own uh opinions<00:01:35.759> so<00:01:36.560> uh<00:01:36.720> that<00:01:37.000> that's<00:01:37.200> one<00:01:37.399> reason 00:01:37.670 --> 00:01:37.680 align:start position:0% opinions so uh that that's one reason 00:01:37.680 --> 00:01:40.389 align:start position:0% opinions so uh that that's one reason but<00:01:37.920> that<00:01:38.240> that<00:01:38.439> same<00:01:39.119> uh<00:01:39.280> thing<00:01:39.560> applies<00:01:39.920> to 00:01:40.389 --> 00:01:40.399 align:start position:0% but that that same uh thing applies to 00:01:40.399 --> 00:01:43.910 align:start position:0% but that that same uh thing applies to pretty<00:01:40.600> much<00:01:40.840> any<00:01:41.840> uh<00:01:42.040> open<00:01:42.600> public<00:01:43.320> uh<00:01:43.439> online 00:01:43.910 --> 00:01:43.920 align:start position:0% pretty much any uh open public uh online 00:01:43.920 --> 00:01:46.590 align:start position:0% pretty much any uh open public uh online Forum<00:01:44.920> uh<00:01:45.040> you<00:01:45.159> can<00:01:45.439> you<00:01:45.520> can<00:01:45.640> see<00:01:45.960> the<00:01:46.119> same 00:01:46.590 --> 00:01:46.600 align:start position:0% Forum uh you can you can see the same 00:01:46.600 --> 00:01:50.469 align:start position:0% Forum uh you can you can see the same ways<00:01:47.159> that<00:01:47.680> uh<00:01:48.200> companies<00:01:48.840> or<00:01:49.200> investors<00:01:49.920> or 00:01:50.469 --> 00:01:50.479 align:start position:0% ways that uh companies or investors or 00:01:50.479 --> 00:01:53.149 align:start position:0% ways that uh companies or investors or corporations<00:01:51.280> or<00:01:52.280> uh<00:01:52.360> organizations<00:01:53.000> with 00:01:53.149 --> 00:01:53.159 align:start position:0% corporations or uh organizations with 00:01:53.159 --> 00:01:57.510 align:start position:0% corporations or uh organizations with like<00:01:53.280> legal<00:01:53.759> agendas<00:01:54.759> May<00:01:55.600> uh<00:01:56.079> censor<00:01:56.680> certain 00:01:57.510 --> 00:01:57.520 align:start position:0% like legal agendas May uh censor certain 00:01:57.520 --> 00:02:00.830 align:start position:0% like legal agendas May uh censor certain voices<00:01:58.119> on<00:01:58.640> on<00:01:59.039> on<00:01:59.200> the<00:01:59.360> internet<00:02:00.079> and<00:02:00.560> uh<00:02:00.759> I 00:02:00.830 --> 00:02:00.840 align:start position:0% voices on on on the internet and uh I 00:02:00.840 --> 00:02:02.870 align:start position:0% voices on on on the internet and uh I think<00:02:01.119> that<00:02:01.640> that<00:02:01.759> we<00:02:01.840> should<00:02:02.039> change<00:02:02.719> the 00:02:02.870 --> 00:02:02.880 align:start position:0% think that that we should change the 00:02:02.880 --> 00:02:05.910 align:start position:0% think that that we should change the Paradigm<00:02:03.479> and<00:02:03.680> and<00:02:03.840> look<00:02:04.039> for<00:02:04.520> ways<00:02:04.799> to<00:02:05.320> have 00:02:05.910 --> 00:02:05.920 align:start position:0% Paradigm and and look for ways to have 00:02:05.920 --> 00:02:09.630 align:start position:0% Paradigm and and look for ways to have uh<00:02:06.399> censorship<00:02:07.079> to<00:02:07.280> be<00:02:07.479> hard<00:02:08.080> by<00:02:08.360> default<00:02:09.360> um 00:02:09.630 --> 00:02:09.640 align:start position:0% uh censorship to be hard by default um 00:02:09.640 --> 00:02:12.030 align:start position:0% uh censorship to be hard by default um so<00:02:09.959> how<00:02:10.119> could<00:02:10.239> you<00:02:10.399> do<00:02:10.599> this<00:02:10.720> on<00:02:10.879> ethereum<00:02:11.879> uh 00:02:12.030 --> 00:02:12.040 align:start position:0% so how could you do this on ethereum uh 00:02:12.040 --> 00:02:13.670 align:start position:0% so how could you do this on ethereum uh what<00:02:12.160> I've<00:02:12.319> built<00:02:12.680> uses<00:02:13.160> the<00:02:13.319> the<00:02:13.400> middle 00:02:13.670 --> 00:02:13.680 align:start position:0% what I've built uses the the middle 00:02:13.680 --> 00:02:16.150 align:start position:0% what I've built uses the the middle pieces<00:02:14.080> ipfs<00:02:14.720> whisper<00:02:15.120> and<00:02:15.239> ethereum<00:02:15.680> to<00:02:16.000> to 00:02:16.150 --> 00:02:16.160 align:start position:0% pieces ipfs whisper and ethereum to to 00:02:16.160 --> 00:02:19.150 align:start position:0% pieces ipfs whisper and ethereum to to structure<00:02:16.800> a<00:02:17.000> very<00:02:17.560> basic<00:02:18.560> U<00:02:18.720> threaded 00:02:19.150 --> 00:02:19.160 align:start position:0% structure a very basic U threaded 00:02:19.160 --> 00:02:21.630 align:start position:0% structure a very basic U threaded discussion<00:02:19.640> system<00:02:20.400> but<00:02:21.200> one<00:02:21.319> of<00:02:21.480> the 00:02:21.630 --> 00:02:21.640 align:start position:0% discussion system but one of the 00:02:21.640 --> 00:02:23.509 align:start position:0% discussion system but one of the benefits<00:02:22.080> of<00:02:22.239> building<00:02:22.560> on<00:02:22.680> a<00:02:22.840> public 00:02:23.509 --> 00:02:23.519 align:start position:0% benefits of building on a public 00:02:23.519 --> 00:02:26.070 align:start position:0% benefits of building on a public blockchain<00:02:24.519> uh<00:02:24.640> Julian<00:02:25.400> alluded<00:02:25.760> to<00:02:25.920> this 00:02:26.070 --> 00:02:26.080 align:start position:0% blockchain uh Julian alluded to this 00:02:26.080 --> 00:02:28.790 align:start position:0% blockchain uh Julian alluded to this earlier<00:02:26.440> in<00:02:26.680> the<00:02:26.879> the<00:02:27.040> game<00:02:28.040> uh<00:02:28.200> panel<00:02:28.680> the 00:02:28.790 --> 00:02:28.800 align:start position:0% earlier in the the game uh panel the 00:02:28.800 --> 00:02:32.309 align:start position:0% earlier in the the game uh panel the game<00:02:29.440> uh<00:02:30.000> developer<00:02:30.440> panel<00:02:31.319> uh<00:02:31.680> that<00:02:32.120> on 00:02:32.309 --> 00:02:32.319 align:start position:0% game uh developer panel uh that on 00:02:32.319 --> 00:02:35.110 align:start position:0% game uh developer panel uh that on ethereum<00:02:33.319> it's<00:02:33.680> it's<00:02:34.000> unrestricted<00:02:34.599> for<00:02:34.959> any 00:02:35.110 --> 00:02:35.120 align:start position:0% ethereum it's it's unrestricted for any 00:02:35.120 --> 00:02:37.589 align:start position:0% ethereum it's it's unrestricted for any third<00:02:35.360> party<00:02:35.599> to<00:02:35.720> build<00:02:35.959> services<00:02:36.360> on<00:02:36.599> top<00:02:36.800> of 00:02:37.589 --> 00:02:37.599 align:start position:0% third party to build services on top of 00:02:37.599 --> 00:02:39.550 align:start position:0% third party to build services on top of uh<00:02:38.080> content<00:02:38.480> that<00:02:38.599> is<00:02:38.720> on<00:02:38.879> the<00:02:39.000> blockchain<00:02:39.400> or 00:02:39.550 --> 00:02:39.560 align:start position:0% uh content that is on the blockchain or 00:02:39.560 --> 00:02:42.390 align:start position:0% uh content that is on the blockchain or on<00:02:39.920> ipfs<00:02:40.920> and<00:02:41.120> and<00:02:41.239> so<00:02:41.480> that<00:02:41.599> is<00:02:41.920> that<00:02:42.040> is<00:02:42.200> one 00:02:42.390 --> 00:02:42.400 align:start position:0% on ipfs and and so that is that is one 00:02:42.400 --> 00:02:45.470 align:start position:0% on ipfs and and so that is that is one way<00:02:42.640> I<00:02:42.879> I<00:02:42.959> could<00:02:43.120> definitely<00:02:43.440> see<00:02:44.440> uh<00:02:45.000> a<00:02:45.120> Reddit 00:02:45.470 --> 00:02:45.480 align:start position:0% way I I could definitely see uh a Reddit 00:02:45.480 --> 00:02:48.910 align:start position:0% way I I could definitely see uh a Reddit type<00:02:45.640> of<00:02:45.879> ecosystem<00:02:46.640> developing<00:02:47.599> serving<00:02:48.599> see 00:02:48.910 --> 00:02:48.920 align:start position:0% type of ecosystem developing serving see 00:02:48.920 --> 00:02:50.949 align:start position:0% type of ecosystem developing serving see all<00:02:49.040> of<00:02:49.200> these<00:02:49.599> pieces<00:02:50.440> uh<00:02:50.560> permissions 00:02:50.949 --> 00:02:50.959 align:start position:0% all of these pieces uh permissions 00:02:50.959 --> 00:02:53.110 align:start position:0% all of these pieces uh permissions moderation<00:02:51.400> notification<00:02:51.920> search<00:02:52.800> and<00:02:52.959> and 00:02:53.110 --> 00:02:53.120 align:start position:0% moderation notification search and and 00:02:53.120 --> 00:02:56.350 align:start position:0% moderation notification search and and so<00:02:53.280> on<00:02:53.599> are<00:02:54.280> currently<00:02:54.640> done<00:02:55.000> by<00:02:55.640> uh<00:02:56.040> the<00:02:56.239> the 00:02:56.350 --> 00:02:56.360 align:start position:0% so on are currently done by uh the the 00:02:56.360 --> 00:02:57.949 align:start position:0% so on are currently done by uh the the centralized<00:02:56.879> Reddit<00:02:57.239> or<00:02:57.440> Facebook<00:02:57.800> or 00:02:57.949 --> 00:02:57.959 align:start position:0% centralized Reddit or Facebook or 00:02:57.959 --> 00:03:01.030 align:start position:0% centralized Reddit or Facebook or Twitter<00:02:58.560> organizations<00:02:59.560> and<00:03:00.080> uh<00:03:00.440> on<00:03:00.599> ethereum 00:03:01.030 --> 00:03:01.040 align:start position:0% Twitter organizations and uh on ethereum 00:03:01.040 --> 00:03:02.550 align:start position:0% Twitter organizations and uh on ethereum we<00:03:01.159> can<00:03:01.319> actually<00:03:01.599> have<00:03:01.800> competing<00:03:02.200> services 00:03:02.550 --> 00:03:02.560 align:start position:0% we can actually have competing services 00:03:02.560 --> 00:03:04.910 align:start position:0% we can actually have competing services in<00:03:02.720> each<00:03:02.840> of<00:03:03.000> those<00:03:03.360> areas<00:03:04.360> uh<00:03:04.480> offering 00:03:04.910 --> 00:03:04.920 align:start position:0% in each of those areas uh offering 00:03:04.920 --> 00:03:07.869 align:start position:0% in each of those areas uh offering different<00:03:05.920> uh<00:03:06.239> services<00:03:06.799> for<00:03:07.280> a<00:03:07.680> uh 00:03:07.869 --> 00:03:07.879 align:start position:0% different uh services for a uh 00:03:07.879 --> 00:03:10.390 align:start position:0% different uh services for a uh discussion<00:03:08.280> platform<00:03:09.040> so<00:03:09.599> the<00:03:09.720> colors<00:03:10.040> mean 00:03:10.390 --> 00:03:10.400 align:start position:0% discussion platform so the colors mean 00:03:10.400 --> 00:03:12.589 align:start position:0% discussion platform so the colors mean just<00:03:10.560> briefly<00:03:11.040> that<00:03:11.280> the<00:03:11.400> blue<00:03:11.720> is<00:03:12.040> like<00:03:12.360> stuff 00:03:12.589 --> 00:03:12.599 align:start position:0% just briefly that the blue is like stuff 00:03:12.599 --> 00:03:14.430 align:start position:0% just briefly that the blue is like stuff that<00:03:12.760> has<00:03:12.879> to<00:03:12.959> be<00:03:13.080> on<00:03:13.239> Shain<00:03:13.720> and<00:03:13.920> trustless 00:03:14.430 --> 00:03:14.440 align:start position:0% that has to be on Shain and trustless 00:03:14.440 --> 00:03:16.309 align:start position:0% that has to be on Shain and trustless and<00:03:14.519> you<00:03:14.640> have<00:03:14.720> to<00:03:14.840> pay<00:03:15.000> for<00:03:15.159> it<00:03:15.599> but<00:03:15.920> the<00:03:16.200> the 00:03:16.309 --> 00:03:16.319 align:start position:0% and you have to pay for it but the the 00:03:16.319 --> 00:03:19.149 align:start position:0% and you have to pay for it but the the purple<00:03:17.159> is<00:03:17.560> a<00:03:17.760> combination<00:03:18.159> of<00:03:18.280> onchain<00:03:19.000> and 00:03:19.149 --> 00:03:19.159 align:start position:0% purple is a combination of onchain and 00:03:19.159 --> 00:03:23.070 align:start position:0% purple is a combination of onchain and or<00:03:19.360> offchain<00:03:19.760> or<00:03:20.000> both<00:03:20.799> and<00:03:21.519> uh<00:03:22.200> ipfs<00:03:22.760> swarm 00:03:23.070 --> 00:03:23.080 align:start position:0% or offchain or both and uh ipfs swarm 00:03:23.080 --> 00:03:25.030 align:start position:0% or offchain or both and uh ipfs swarm whisper<00:03:23.400> notifications<00:03:23.920> are<00:03:24.319> offchain 00:03:25.030 --> 00:03:25.040 align:start position:0% whisper notifications are offchain 00:03:25.040 --> 00:03:28.190 align:start position:0% whisper notifications are offchain services<00:03:25.519> that<00:03:25.640> could<00:03:25.760> be<00:03:25.959> provided<00:03:26.959> um<00:03:27.560> so 00:03:28.190 --> 00:03:28.200 align:start position:0% services that could be provided um so 00:03:28.200 --> 00:03:30.270 align:start position:0% services that could be provided um so that's<00:03:28.519> that's<00:03:28.680> how<00:03:28.799> I<00:03:28.920> see<00:03:29.159> that<00:03:29.319> evolving 00:03:30.270 --> 00:03:30.280 align:start position:0% that's that's how I see that evolving 00:03:30.280 --> 00:03:31.990 align:start position:0% that's that's how I see that evolving um<00:03:30.560> I<00:03:30.760> I'll<00:03:31.000> go<00:03:31.120> ahead<00:03:31.319> and<00:03:31.439> talk<00:03:31.640> about<00:03:31.840> what 00:03:31.990 --> 00:03:32.000 align:start position:0% um I I'll go ahead and talk about what 00:03:32.000 --> 00:03:34.910 align:start position:0% um I I'll go ahead and talk about what I'm<00:03:32.200> what<00:03:32.280> I<00:03:32.360> built<00:03:32.640> and<00:03:32.799> how<00:03:33.239> um<00:03:34.239> onchain 00:03:34.910 --> 00:03:34.920 align:start position:0% I'm what I built and how um onchain 00:03:34.920 --> 00:03:36.509 align:start position:0% I'm what I built and how um onchain storage<00:03:35.319> works<00:03:35.799> so<00:03:35.959> there's<00:03:36.120> two<00:03:36.280> ways<00:03:36.439> you 00:03:36.509 --> 00:03:36.519 align:start position:0% storage works so there's two ways you 00:03:36.519 --> 00:03:38.830 align:start position:0% storage works so there's two ways you could<00:03:36.680> do<00:03:36.879> this<00:03:37.239> uh<00:03:37.400> one<00:03:37.760> is 00:03:38.830 --> 00:03:38.840 align:start position:0% could do this uh one is 00:03:38.840 --> 00:03:41.670 align:start position:0% could do this uh one is with<00:03:39.840> contract<00:03:40.239> structs<00:03:41.159> uh<00:03:41.280> that<00:03:41.360> we<00:03:41.480> all 00:03:41.670 --> 00:03:41.680 align:start position:0% with contract structs uh that we all 00:03:41.680 --> 00:03:43.509 align:start position:0% with contract structs uh that we all know<00:03:41.879> and<00:03:42.040> love<00:03:42.400> but<00:03:42.560> the<00:03:42.640> other<00:03:42.799> way<00:03:42.959> is<00:03:43.080> logs 00:03:43.509 --> 00:03:43.519 align:start position:0% know and love but the other way is logs 00:03:43.519 --> 00:03:45.309 align:start position:0% know and love but the other way is logs and<00:03:43.640> I'll<00:03:44.040> describe<00:03:44.439> the<00:03:44.519> trade-offs<00:03:45.040> between 00:03:45.309 --> 00:03:45.319 align:start position:0% and I'll describe the trade-offs between 00:03:45.319 --> 00:03:48.110 align:start position:0% and I'll describe the trade-offs between those<00:03:46.000> so<00:03:46.560> for<00:03:46.799> onchain<00:03:47.280> storage<00:03:47.959> uh 00:03:48.110 --> 00:03:48.120 align:start position:0% those so for onchain storage uh 00:03:48.120 --> 00:03:50.149 align:start position:0% those so for onchain storage uh basically<00:03:48.560> there's<00:03:48.840> two<00:03:49.519> two<00:03:49.760> methods<00:03:50.080> that 00:03:50.149 --> 00:03:50.159 align:start position:0% basically there's two two methods that 00:03:50.159 --> 00:03:52.550 align:start position:0% basically there's two two methods that are<00:03:50.319> important<00:03:50.720> add<00:03:50.879> and<00:03:51.080> edit<00:03:51.720> when<00:03:51.840> you<00:03:52.079> add 00:03:52.550 --> 00:03:52.560 align:start position:0% are important add and edit when you add 00:03:52.560 --> 00:03:55.990 align:start position:0% are important add and edit when you add a<00:03:53.079> a<00:03:53.280> post<00:03:53.599> you<00:03:53.760> are<00:03:54.640> designating<00:03:55.200> a<00:03:55.360> parent 00:03:55.990 --> 00:03:56.000 align:start position:0% a a post you are designating a parent 00:03:56.000 --> 00:03:58.270 align:start position:0% a a post you are designating a parent that<00:03:56.519> that<00:03:56.720> post<00:03:56.920> will<00:03:57.079> be<00:03:57.519> referenced<00:03:57.959> to<00:03:58.159> as 00:03:58.270 --> 00:03:58.280 align:start position:0% that that post will be referenced to as 00:03:58.280 --> 00:04:01.630 align:start position:0% that that post will be referenced to as a<00:03:58.480> child<00:03:59.480> um<00:03:59.920> and<00:04:00.360> a<00:04:00.480> string<00:04:00.760> of<00:04:00.920> data<00:04:01.480> which 00:04:01.630 --> 00:04:01.640 align:start position:0% a child um and a string of data which 00:04:01.640 --> 00:04:03.509 align:start position:0% a child um and a string of data which could<00:04:01.760> be<00:04:01.920> anything<00:04:02.680> I<00:04:02.879> like<00:04:03.040> I<00:04:03.120> like<00:04:03.319> using 00:04:03.509 --> 00:04:03.519 align:start position:0% could be anything I like I like using 00:04:03.519 --> 00:04:05.110 align:start position:0% could be anything I like I like using strings<00:04:03.879> there<00:04:04.040> because<00:04:04.280> they<00:04:04.400> could<00:04:04.519> be<00:04:04.720> a 00:04:05.110 --> 00:04:05.120 align:start position:0% strings there because they could be a 00:04:05.120 --> 00:04:08.750 align:start position:0% strings there because they could be a ipfs<00:04:05.640> hash<00:04:06.159> a<00:04:06.280> URL<00:04:07.159> or<00:04:07.599> uh<00:04:07.920> potentially<00:04:08.400> just 00:04:08.750 --> 00:04:08.760 align:start position:0% ipfs hash a URL or uh potentially just 00:04:08.760 --> 00:04:13.149 align:start position:0% ipfs hash a URL or uh potentially just raw<00:04:09.120> text<00:04:10.040> so<00:04:10.560> then<00:04:11.439> uh<00:04:11.720> the<00:04:12.079> the<00:04:12.480> that<00:04:13.000> will 00:04:13.149 --> 00:04:13.159 align:start position:0% raw text so then uh the the that will 00:04:13.159 --> 00:04:14.670 align:start position:0% raw text so then uh the the that will create<00:04:13.400> a<00:04:13.519> struct<00:04:13.920> which<00:04:14.040> will<00:04:14.159> be<00:04:14.239> saved<00:04:14.519> in 00:04:14.670 --> 00:04:14.680 align:start position:0% create a struct which will be saved in 00:04:14.680 --> 00:04:17.590 align:start position:0% create a struct which will be saved in this<00:04:14.799> array<00:04:15.480> right<00:04:15.640> here<00:04:16.600> um<00:04:17.040> it<00:04:17.239> it<00:04:17.359> just 00:04:17.590 --> 00:04:17.600 align:start position:0% this array right here um it it just 00:04:17.600 --> 00:04:20.509 align:start position:0% this array right here um it it just expands<00:04:18.440> uh<00:04:19.160> with<00:04:19.280> each<00:04:19.479> new<00:04:19.680> post<00:04:20.040> and<00:04:20.199> that 00:04:20.509 --> 00:04:20.519 align:start position:0% expands uh with each new post and that 00:04:20.519 --> 00:04:22.790 align:start position:0% expands uh with each new post and that that<00:04:20.959> index<00:04:21.239> of<00:04:21.400> the<00:04:21.479> array<00:04:22.160> is<00:04:22.320> implicitly 00:04:22.790 --> 00:04:22.800 align:start position:0% that index of the array is implicitly 00:04:22.800 --> 00:04:24.670 align:start position:0% that index of the array is implicitly the<00:04:22.880> ID<00:04:23.120> of<00:04:23.240> the<00:04:23.360> post<00:04:23.919> which<00:04:24.040> is<00:04:24.160> used<00:04:24.400> in<00:04:24.479> this 00:04:24.670 --> 00:04:24.680 align:start position:0% the ID of the post which is used in this 00:04:24.680 --> 00:04:27.670 align:start position:0% the ID of the post which is used in this mapping<00:04:25.160> of<00:04:25.479> uh<00:04:25.600> post<00:04:25.840> to<00:04:26.160> children<00:04:27.160> and<00:04:27.360> edit 00:04:27.670 --> 00:04:27.680 align:start position:0% mapping of uh post to children and edit 00:04:27.680 --> 00:04:30.909 align:start position:0% mapping of uh post to children and edit is<00:04:28.000> is<00:04:28.560> a<00:04:28.720> method<00:04:29.000> I<00:04:29.120> wanted<00:04:29.320> to<00:04:29.479> add<00:04:30.080> so<00:04:30.560> um<00:04:30.800> if 00:04:30.909 --> 00:04:30.919 align:start position:0% is is a method I wanted to add so um if 00:04:30.919 --> 00:04:32.590 align:start position:0% is is a method I wanted to add so um if you<00:04:31.160> if<00:04:31.240> you<00:04:31.360> submit<00:04:31.600> a<00:04:31.720> post<00:04:31.960> you<00:04:32.080> can<00:04:32.360> you<00:04:32.440> can 00:04:32.590 --> 00:04:32.600 align:start position:0% you if you submit a post you can you can 00:04:32.600 --> 00:04:33.870 align:start position:0% you if you submit a post you can you can edit<00:04:32.840> the<00:04:32.960> content<00:04:33.240> of<00:04:33.360> it<00:04:33.479> if<00:04:33.560> you<00:04:33.639> are<00:04:33.800> the 00:04:33.870 --> 00:04:33.880 align:start position:0% edit the content of it if you are the 00:04:33.880 --> 00:04:36.029 align:start position:0% edit the content of it if you are the owner<00:04:34.320> and<00:04:34.440> so<00:04:34.639> that<00:04:34.720> is<00:04:34.880> checked<00:04:35.280> from<00:04:35.600> this 00:04:36.029 --> 00:04:36.039 align:start position:0% owner and so that is checked from this 00:04:36.039 --> 00:04:38.590 align:start position:0% owner and so that is checked from this address<00:04:37.039> uh<00:04:37.400> and<00:04:37.520> I'll<00:04:37.680> go<00:04:37.840> through<00:04:38.039> the<00:04:38.240> the 00:04:38.590 --> 00:04:38.600 align:start position:0% address uh and I'll go through the the 00:04:38.600 --> 00:04:42.550 align:start position:0% address uh and I'll go through the the other<00:04:39.240> data<00:04:39.520> types<00:04:39.840> so<00:04:40.360> we<00:04:40.479> have<00:04:40.759> uh<00:04:40.919> two<00:04:41.120> U<00:04:41.600> for 00:04:42.550 --> 00:04:42.560 align:start position:0% other data types so we have uh two U for 00:04:42.560 --> 00:04:44.230 align:start position:0% other data types so we have uh two U for for<00:04:42.840> timestamps<00:04:43.400> for<00:04:43.600> when<00:04:43.759> the<00:04:43.880> post<00:04:44.120> is 00:04:44.230 --> 00:04:44.240 align:start position:0% for timestamps for when the post is 00:04:44.240 --> 00:04:46.830 align:start position:0% for timestamps for when the post is created<00:04:44.520> and<00:04:44.639> when<00:04:44.759> it<00:04:44.840> is<00:04:45.080> edited<00:04:46.080> um<00:04:46.400> we<00:04:46.560> also 00:04:46.830 --> 00:04:46.840 align:start position:0% created and when it is edited um we also 00:04:46.840 --> 00:04:49.270 align:start position:0% created and when it is edited um we also have<00:04:47.160> a<00:04:47.759> number<00:04:48.039> of<00:04:48.160> children<00:04:48.880> which<00:04:49.039> makes 00:04:49.270 --> 00:04:49.280 align:start position:0% have a number of children which makes 00:04:49.280 --> 00:04:50.629 align:start position:0% have a number of children which makes lookups<00:04:49.720> easy<00:04:49.960> if<00:04:50.039> you're<00:04:50.199> looking<00:04:50.400> up<00:04:50.520> an 00:04:50.629 --> 00:04:50.639 align:start position:0% lookups easy if you're looking up an 00:04:50.639 --> 00:04:52.230 align:start position:0% lookups easy if you're looking up an array<00:04:51.199> you<00:04:51.440> you<00:04:51.520> would<00:04:51.680> like<00:04:51.759> to<00:04:51.840> know<00:04:51.960> how<00:04:52.080> big 00:04:52.230 --> 00:04:52.240 align:start position:0% array you you would like to know how big 00:04:52.240 --> 00:04:54.310 align:start position:0% array you you would like to know how big it<00:04:52.360> is<00:04:52.759> um<00:04:52.840> you<00:04:52.919> don't<00:04:53.039> want<00:04:53.120> to<00:04:53.240> look<00:04:53.360> up<00:04:53.840> 10<00:04:54.199> if 00:04:54.310 --> 00:04:54.320 align:start position:0% it is um you don't want to look up 10 if 00:04:54.320 --> 00:04:56.150 align:start position:0% it is um you don't want to look up 10 if there's<00:04:54.520> only<00:04:54.720> two<00:04:55.320> objects<00:04:55.720> in<00:04:55.919> in<00:04:56.039> the 00:04:56.150 --> 00:04:56.160 align:start position:0% there's only two objects in in the 00:04:56.160 --> 00:04:59.749 align:start position:0% there's only two objects in in the children<00:04:57.039> uh<00:04:57.160> and<00:04:57.280> then<00:04:57.400> the<00:04:57.520> data<00:04:57.800> type<00:04:58.400> so<00:04:59.400> uh 00:04:59.749 --> 00:04:59.759 align:start position:0% children uh and then the data type so uh 00:04:59.759 --> 00:05:02.469 align:start position:0% children uh and then the data type so uh just<00:04:59.880> to<00:05:00.000> point<00:05:00.199> out<00:05:00.680> something<00:05:01.680> uh<00:05:01.919> I<00:05:02.199> wanted 00:05:02.469 --> 00:05:02.479 align:start position:0% just to point out something uh I wanted 00:05:02.479 --> 00:05:07.070 align:start position:0% just to point out something uh I wanted to<00:05:02.680> cast<00:05:03.039> these<00:05:03.280> to<00:05:03.600> un<00:05:03.960> 32s<00:05:04.919> they're<00:05:05.440> U<00:05:06.360> on<00:05:06.800> the 00:05:07.070 --> 00:05:07.080 align:start position:0% to cast these to un 32s they're U on the 00:05:07.080 --> 00:05:08.749 align:start position:0% to cast these to un 32s they're U on the as<00:05:07.320> environment<00:05:07.759> variables<00:05:08.120> to<00:05:08.360> contracts 00:05:08.749 --> 00:05:08.759 align:start position:0% as environment variables to contracts 00:05:08.759 --> 00:05:10.310 align:start position:0% as environment variables to contracts and<00:05:09.160> would<00:05:09.360> make<00:05:09.520> sense<00:05:09.680> to<00:05:09.800> store<00:05:10.120> time 00:05:10.310 --> 00:05:10.320 align:start position:0% and would make sense to store time 00:05:10.320 --> 00:05:12.469 align:start position:0% and would make sense to store time stamps<00:05:10.560> as<00:05:10.680> un<00:05:10.960> and<00:05:11.080> I<00:05:11.160> was<00:05:11.240> able<00:05:11.400> to<00:05:11.520> save<00:05:12.400> a 00:05:12.469 --> 00:05:12.479 align:start position:0% stamps as un and I was able to save a 00:05:12.479 --> 00:05:14.350 align:start position:0% stamps as un and I was able to save a storage<00:05:12.759> slot<00:05:13.039> by<00:05:13.120> doing<00:05:13.360> that<00:05:13.639> but<00:05:14.039> it<00:05:14.160> does 00:05:14.350 --> 00:05:14.360 align:start position:0% storage slot by doing that but it does 00:05:14.360 --> 00:05:17.230 align:start position:0% storage slot by doing that but it does limit<00:05:14.639> me<00:05:14.800> to<00:05:15.280> uh<00:05:15.440> to<00:05:15.680> 90<00:05:16.000> years<00:05:16.720> so<00:05:17.080> maybe 00:05:17.230 --> 00:05:17.240 align:start position:0% limit me to uh to 90 years so maybe 00:05:17.240 --> 00:05:19.909 align:start position:0% limit me to uh to 90 years so maybe you'd<00:05:17.440> want<00:05:17.520> to<00:05:17.639> go<00:05:17.759> with<00:05:17.880> un<00:05:18.160> 40s<00:05:18.800> but<00:05:19.479> um 00:05:19.909 --> 00:05:19.919 align:start position:0% you'd want to go with un 40s but um 00:05:19.919 --> 00:05:21.029 align:start position:0% you'd want to go with un 40s but um that's<00:05:20.120> worth<00:05:20.440> considering<00:05:20.800> if<00:05:20.880> you're 00:05:21.029 --> 00:05:21.039 align:start position:0% that's worth considering if you're 00:05:21.039 --> 00:05:23.270 align:start position:0% that's worth considering if you're developer<00:05:21.800> also<00:05:22.759> uh<00:05:22.919> yeah<00:05:23.039> I<00:05:23.120> already 00:05:23.270 --> 00:05:23.280 align:start position:0% developer also uh yeah I already 00:05:23.280 --> 00:05:25.909 align:start position:0% developer also uh yeah I already mentioned<00:05:23.680> data<00:05:23.840> strings<00:05:24.280> are<00:05:24.440> very<00:05:24.919> flexible 00:05:25.909 --> 00:05:25.919 align:start position:0% mentioned data strings are very flexible 00:05:25.919 --> 00:05:27.950 align:start position:0% mentioned data strings are very flexible uh<00:05:26.039> so<00:05:26.240> what's<00:05:26.600> what's<00:05:26.840> the<00:05:27.039> upside<00:05:27.400> of<00:05:27.560> events 00:05:27.950 --> 00:05:27.960 align:start position:0% uh so what's what's the upside of events 00:05:27.960 --> 00:05:29.309 align:start position:0% uh so what's what's the upside of events why<00:05:28.039> would<00:05:28.160> you<00:05:28.240> use<00:05:28.400> events<00:05:28.639> instead<00:05:28.880> of<00:05:29.199> uh 00:05:29.309 --> 00:05:29.319 align:start position:0% why would you use events instead of uh 00:05:29.319 --> 00:05:30.710 align:start position:0% why would you use events instead of uh stru 00:05:30.710 --> 00:05:30.720 align:start position:0% stru 00:05:30.720 --> 00:05:34.270 align:start position:0% stru events<00:05:31.000> are<00:05:31.160> much<00:05:31.319> cheaper<00:05:32.240> they<00:05:33.240> um<00:05:33.680> they 00:05:34.270 --> 00:05:34.280 align:start position:0% events are much cheaper they um they 00:05:34.280 --> 00:05:37.110 align:start position:0% events are much cheaper they um they require<00:05:35.280> uh<00:05:35.680> a<00:05:35.800> lot<00:05:36.000> less<00:05:36.199> gas<00:05:36.400> to<00:05:36.560> use<00:05:36.880> they're 00:05:37.110 --> 00:05:37.120 align:start position:0% require uh a lot less gas to use they're 00:05:37.120 --> 00:05:41.430 align:start position:0% require uh a lot less gas to use they're pended<00:05:37.360> only<00:05:37.880> logs<00:05:38.880> and<00:05:39.720> uh<00:05:40.520> the<00:05:40.880> the<00:05:41.160> other 00:05:41.430 --> 00:05:41.440 align:start position:0% pended only logs and uh the the other 00:05:41.440 --> 00:05:42.990 align:start position:0% pended only logs and uh the the other upside<00:05:41.960> is<00:05:42.120> that<00:05:42.240> they're<00:05:42.400> very<00:05:42.560> light<00:05:42.759> client 00:05:42.990 --> 00:05:43.000 align:start position:0% upside is that they're very light client 00:05:43.000 --> 00:05:46.029 align:start position:0% upside is that they're very light client friendly<00:05:43.919> so<00:05:44.479> the<00:05:44.759> the<00:05:44.960> downside<00:05:45.360> of<00:05:45.479> using<00:05:45.840> a 00:05:46.029 --> 00:05:46.039 align:start position:0% friendly so the the downside of using a 00:05:46.039 --> 00:05:47.830 align:start position:0% friendly so the the downside of using a a<00:05:46.160> log<00:05:46.520> though<00:05:46.800> is<00:05:46.960> that<00:05:47.240> they're<00:05:47.479> more 00:05:47.830 --> 00:05:47.840 align:start position:0% a log though is that they're more 00:05:47.840 --> 00:05:50.350 align:start position:0% a log though is that they're more difficult<00:05:47.960> to<00:05:48.120> edit<00:05:48.919> so<00:05:49.199> you<00:05:49.680> with<00:05:49.919> the<00:05:50.160> the 00:05:50.350 --> 00:05:50.360 align:start position:0% difficult to edit so you with the the 00:05:50.360 --> 00:05:52.710 align:start position:0% difficult to edit so you with the the struct<00:05:50.759> for<00:05:51.039> posts<00:05:51.639> it<00:05:51.840> you<00:05:52.199> you<00:05:52.280> store<00:05:52.639> the 00:05:52.710 --> 00:05:52.720 align:start position:0% struct for posts it you you store the 00:05:52.720 --> 00:05:54.309 align:start position:0% struct for posts it you you store the owner<00:05:53.120> in<00:05:53.400> one<00:05:53.560> of<00:05:53.680> the<00:05:53.759> fields<00:05:54.080> and<00:05:54.199> the 00:05:54.309 --> 00:05:54.319 align:start position:0% owner in one of the fields and the 00:05:54.319 --> 00:05:55.990 align:start position:0% owner in one of the fields and the contract<00:05:54.680> can<00:05:54.800> look<00:05:54.960> that<00:05:55.120> up<00:05:55.520> and<00:05:55.639> verify 00:05:55.990 --> 00:05:56.000 align:start position:0% contract can look that up and verify 00:05:56.000 --> 00:05:58.270 align:start position:0% contract can look that up and verify that<00:05:56.160> only<00:05:56.479> the<00:05:56.919> the<00:05:57.039> message<00:05:57.440> sender<00:05:58.120> that 00:05:58.270 --> 00:05:58.280 align:start position:0% that only the the message sender that 00:05:58.280 --> 00:05:59.990 align:start position:0% that only the the message sender that equals<00:05:58.639> that<00:05:58.759> owner<00:05:59.120> can<00:05:59.319> actually<00:05:59.720> change 00:05:59.990 --> 00:06:00.000 align:start position:0% equals that owner can actually change 00:06:00.000 --> 00:06:04.469 align:start position:0% equals that owner can actually change the<00:06:00.120> data<00:06:00.680> but<00:06:00.840> for<00:06:01.440> uh<00:06:01.680> a<00:06:01.840> post<00:06:02.080> event<00:06:02.840> or<00:06:03.479> log 00:06:04.469 --> 00:06:04.479 align:start position:0% the data but for uh a post event or log 00:06:04.479 --> 00:06:05.670 align:start position:0% the data but for uh a post event or log uh<00:06:04.560> the<00:06:04.680> contract<00:06:05.000> doesn't<00:06:05.160> have<00:06:05.280> any<00:06:05.400> way<00:06:05.520> to 00:06:05.670 --> 00:06:05.680 align:start position:0% uh the contract doesn't have any way to 00:06:05.680 --> 00:06:07.909 align:start position:0% uh the contract doesn't have any way to read<00:06:06.199> the<00:06:06.360> the<00:06:06.479> data<00:06:06.759> from<00:06:07.000> from<00:06:07.240> past<00:06:07.440> log<00:06:07.800> so 00:06:07.909 --> 00:06:07.919 align:start position:0% read the the data from from past log so 00:06:07.919 --> 00:06:10.070 align:start position:0% read the the data from from past log so it<00:06:08.039> can't<00:06:08.360> verify<00:06:09.360> uh<00:06:09.560> that<00:06:09.680> the<00:06:09.800> message 00:06:10.070 --> 00:06:10.080 align:start position:0% it can't verify uh that the message 00:06:10.080 --> 00:06:11.670 align:start position:0% it can't verify uh that the message sender<00:06:10.400> is<00:06:10.520> equal<00:06:10.759> to<00:06:11.160> the<00:06:11.240> owner<00:06:11.440> of<00:06:11.560> a 00:06:11.670 --> 00:06:11.680 align:start position:0% sender is equal to the owner of a 00:06:11.680 --> 00:06:14.710 align:start position:0% sender is equal to the owner of a particular<00:06:12.120> log<00:06:12.960> so<00:06:13.720> what<00:06:13.880> you<00:06:14.000> can<00:06:14.240> do<00:06:14.520> maybe 00:06:14.710 --> 00:06:14.720 align:start position:0% particular log so what you can do maybe 00:06:14.720 --> 00:06:16.749 align:start position:0% particular log so what you can do maybe to<00:06:14.840> get<00:06:14.960> around<00:06:15.240> this<00:06:15.400> is<00:06:15.759> have<00:06:15.919> an<00:06:16.120> event<00:06:16.440> for 00:06:16.749 --> 00:06:16.759 align:start position:0% to get around this is have an event for 00:06:16.759 --> 00:06:19.589 align:start position:0% to get around this is have an event for editing<00:06:17.319> and<00:06:17.479> let<00:06:17.639> the<00:06:17.720> front<00:06:17.960> end<00:06:18.880> uh<00:06:19.160> filter 00:06:19.589 --> 00:06:19.599 align:start position:0% editing and let the front end uh filter 00:06:19.599 --> 00:06:22.029 align:start position:0% editing and let the front end uh filter through<00:06:20.280> the<00:06:20.680> the<00:06:20.800> edits<00:06:21.240> to<00:06:21.520> to<00:06:21.680> find<00:06:21.919> the 00:06:22.029 --> 00:06:22.039 align:start position:0% through the the edits to to find the 00:06:22.039 --> 00:06:23.710 align:start position:0% through the the edits to to find the ones<00:06:22.319> where<00:06:22.560> the<00:06:22.800> owner<00:06:23.120> matches<00:06:23.520> the 00:06:23.710 --> 00:06:23.720 align:start position:0% ones where the owner matches the 00:06:23.720 --> 00:06:27.469 align:start position:0% ones where the owner matches the original<00:06:24.479> log<00:06:24.960> ID<00:06:25.919> but<00:06:26.319> um<00:06:26.759> that<00:06:27.039> that<00:06:27.360> that 00:06:27.469 --> 00:06:27.479 align:start position:0% original log ID but um that that that 00:06:27.479 --> 00:06:30.150 align:start position:0% original log ID but um that that that seems<00:06:27.759> a<00:06:27.880> little<00:06:28.120> bit<00:06:28.520> annoying<00:06:29.280> and<00:06:29.840> uh<00:06:30.039> it 00:06:30.150 --> 00:06:30.160 align:start position:0% seems a little bit annoying and uh it 00:06:30.160 --> 00:06:31.350 align:start position:0% seems a little bit annoying and uh it just<00:06:30.319> kind<00:06:30.440> of<00:06:30.560> depends<00:06:30.919> I<00:06:31.000> guess<00:06:31.120> on<00:06:31.280> what 00:06:31.350 --> 00:06:31.360 align:start position:0% just kind of depends I guess on what 00:06:31.360 --> 00:06:32.390 align:start position:0% just kind of depends I guess on what your<00:06:31.479> use<00:06:31.759> case<00:06:31.919> is<00:06:32.039> if<00:06:32.120> you're<00:06:32.240> an 00:06:32.390 --> 00:06:32.400 align:start position:0% your use case is if you're an 00:06:32.400 --> 00:06:33.589 align:start position:0% your use case is if you're an application<00:06:32.800> that<00:06:32.919> doesn't<00:06:33.120> want<00:06:33.240> to<00:06:33.360> allow 00:06:33.589 --> 00:06:33.599 align:start position:0% application that doesn't want to allow 00:06:33.599 --> 00:06:35.150 align:start position:0% application that doesn't want to allow edits<00:06:33.960> then<00:06:34.319> logs<00:06:34.639> would<00:06:34.800> probably<00:06:34.960> be<00:06:35.080> the 00:06:35.150 --> 00:06:35.160 align:start position:0% edits then logs would probably be the 00:06:35.160 --> 00:06:37.309 align:start position:0% edits then logs would probably be the way<00:06:35.280> to<00:06:35.400> go<00:06:35.639> if<00:06:36.240> if<00:06:36.560> you<00:06:36.720> do<00:06:36.880> want<00:06:36.960> to<00:06:37.080> allow 00:06:37.309 --> 00:06:37.319 align:start position:0% way to go if if you do want to allow 00:06:37.319 --> 00:06:38.749 align:start position:0% way to go if if you do want to allow them<00:06:37.680> you<00:06:37.840> you<00:06:37.919> may<00:06:38.120> have<00:06:38.199> to<00:06:38.400> consider<00:06:38.680> the 00:06:38.749 --> 00:06:38.759 align:start position:0% them you you may have to consider the 00:06:38.759 --> 00:06:41.150 align:start position:0% them you you may have to consider the trade-offs<00:06:39.280> there<00:06:39.800> post<00:06:40.120> count<00:06:40.400> is<00:06:40.680> necessary 00:06:41.150 --> 00:06:41.160 align:start position:0% trade-offs there post count is necessary 00:06:41.160 --> 00:06:43.230 align:start position:0% trade-offs there post count is necessary here<00:06:41.680> so<00:06:41.919> that<00:06:42.120> each<00:06:42.599> each<00:06:42.800> event<00:06:43.000> would<00:06:43.160> have 00:06:43.230 --> 00:06:43.240 align:start position:0% here so that each each event would have 00:06:43.240 --> 00:06:44.189 align:start position:0% here so that each each event would have its<00:06:43.360> own 00:06:44.189 --> 00:06:44.199 align:start position:0% its own 00:06:44.199 --> 00:06:48.589 align:start position:0% its own ID<00:06:45.199> um<00:06:46.440> right<00:06:47.440> and<00:06:47.599> those<00:06:47.720> are<00:06:47.840> the<00:06:47.960> guas<00:06:48.240> cost 00:06:48.589 --> 00:06:48.599 align:start position:0% ID um right and those are the guas cost 00:06:48.599 --> 00:06:52.670 align:start position:0% ID um right and those are the guas cost trade-offs<00:06:49.080> for<00:06:49.280> logs<00:06:50.000> versus<00:06:51.000> uh<00:06:51.599> s<00:06:51.840> stores 00:06:52.670 --> 00:06:52.680 align:start position:0% trade-offs for logs versus uh s stores 00:06:52.680 --> 00:06:57.670 align:start position:0% trade-offs for logs versus uh s stores uh<00:06:52.800> where<00:06:52.960> each<00:06:53.160> log<00:06:53.400> is<00:06:54.280> uh<00:06:54.680> 375<00:06:55.680> plus<00:06:56.360> 375<00:06:57.360> per 00:06:57.670 --> 00:06:57.680 align:start position:0% uh where each log is uh 375 plus 375 per 00:06:57.680 --> 00:06:59.070 align:start position:0% uh where each log is uh 375 plus 375 per topic<00:06:58.080> which<00:06:58.199> I<00:06:58.280> think<00:06:58.400> you<00:06:58.479> can<00:06:58.599> go<00:06:58.840> up<00:06:58.960> to 00:06:59.070 --> 00:06:59.080 align:start position:0% topic which I think you can go up to 00:06:59.080 --> 00:07:01.950 align:start position:0% topic which I think you can go up to three<00:06:59.199> or<00:06:59.280> four<00:06:59.680> topics<00:07:00.440> and<00:07:00.560> then<00:07:00.759> eight<00:07:01.560> gas 00:07:01.950 --> 00:07:01.960 align:start position:0% three or four topics and then eight gas 00:07:01.960 --> 00:07:03.670 align:start position:0% three or four topics and then eight gas per 00:07:03.670 --> 00:07:03.680 align:start position:0% per 00:07:03.680 --> 00:07:06.869 align:start position:0% per bite<00:07:04.680> all<00:07:04.840> right<00:07:05.160> so<00:07:05.639> I'll<00:07:05.840> show<00:07:06.120> you<00:07:06.440> a<00:07:06.639> very 00:07:06.869 --> 00:07:06.879 align:start position:0% bite all right so I'll show you a very 00:07:06.879 --> 00:07:09.790 align:start position:0% bite all right so I'll show you a very Alpha<00:07:07.199> demo<00:07:08.039> of<00:07:08.360> of<00:07:08.479> what<00:07:08.599> I've<00:07:08.720> built<00:07:08.960> so<00:07:09.160> far 00:07:09.790 --> 00:07:09.800 align:start position:0% Alpha demo of of what I've built so far 00:07:09.800 --> 00:07:14.350 align:start position:0% Alpha demo of of what I've built so far um<00:07:10.680> this<00:07:10.840> is<00:07:11.160> a<00:07:11.400> video<00:07:12.240> so<00:07:13.240> we'll<00:07:13.840> start<00:07:14.160> by 00:07:14.350 --> 00:07:14.360 align:start position:0% um this is a video so we'll start by 00:07:14.360 --> 00:07:16.150 align:start position:0% um this is a video so we'll start by adding<00:07:14.720> a<00:07:14.879> couple<00:07:15.080> of<00:07:15.280> accounts<00:07:15.639> that<00:07:15.840> I 00:07:16.150 --> 00:07:16.160 align:start position:0% adding a couple of accounts that I 00:07:16.160 --> 00:07:18.909 align:start position:0% adding a couple of accounts that I already<00:07:16.400> generated<00:07:17.120> with<00:07:17.319> these<00:07:17.520> seeds<00:07:18.400> that 00:07:18.909 --> 00:07:18.919 align:start position:0% already generated with these seeds that 00:07:18.919 --> 00:07:20.950 align:start position:0% already generated with these seeds that uh<00:07:19.039> I<00:07:19.120> was<00:07:19.240> able<00:07:19.400> to<00:07:19.560> get<00:07:19.720> using<00:07:20.520> uh<00:07:20.639> cooworker 00:07:20.950 --> 00:07:20.960 align:start position:0% uh I was able to get using uh cooworker 00:07:20.960 --> 00:07:23.710 align:start position:0% uh I was able to get using uh cooworker Christian<00:07:21.360> lonquist<00:07:22.160> Library<00:07:22.800> e<00:07:23.199> Das<00:07:23.560> light 00:07:23.710 --> 00:07:23.720 align:start position:0% Christian lonquist Library e Das light 00:07:23.720 --> 00:07:25.469 align:start position:0% Christian lonquist Library e Das light wallet<00:07:24.560> um<00:07:24.680> so<00:07:24.879> this<00:07:24.960> is<00:07:25.080> how<00:07:25.199> you<00:07:25.280> would 00:07:25.469 --> 00:07:25.479 align:start position:0% wallet um so this is how you would 00:07:25.479 --> 00:07:27.990 align:start position:0% wallet um so this is how you would create<00:07:25.720> one<00:07:26.000> in<00:07:26.160> the<00:07:26.360> app<00:07:27.360> um<00:07:27.560> but<00:07:27.680> I'll<00:07:27.840> just 00:07:27.990 --> 00:07:28.000 align:start position:0% create one in the app um but I'll just 00:07:28.000 --> 00:07:30.710 align:start position:0% create one in the app um but I'll just go<00:07:28.120> ahead<00:07:28.319> and<00:07:28.599> import<00:07:29.000> an<00:07:29.160> existing<00:07:29.759> one<00:07:30.560> uh 00:07:30.710 --> 00:07:30.720 align:start position:0% go ahead and import an existing one uh 00:07:30.720 --> 00:07:32.230 align:start position:0% go ahead and import an existing one uh these<00:07:30.879> seeds<00:07:31.319> have<00:07:31.440> been<00:07:31.680> pre-loaded<00:07:32.120> with 00:07:32.230 --> 00:07:32.240 align:start position:0% these seeds have been pre-loaded with 00:07:32.240 --> 00:07:35.749 align:start position:0% these seeds have been pre-loaded with some<00:07:32.560> ether<00:07:33.560> I'll<00:07:33.879> add<00:07:34.000> a<00:07:34.199> password<00:07:34.759> to<00:07:35.400> uh<00:07:35.599> to 00:07:35.749 --> 00:07:35.759 align:start position:0% some ether I'll add a password to uh to 00:07:35.759 --> 00:07:38.029 align:start position:0% some ether I'll add a password to uh to encrypt<00:07:36.120> them<00:07:36.199> in<00:07:36.319> my<00:07:36.440> browser<00:07:36.800> so<00:07:36.960> I<00:07:37.039> can<00:07:37.879> uh 00:07:38.029 --> 00:07:38.039 align:start position:0% encrypt them in my browser so I can uh 00:07:38.039 --> 00:07:39.629 align:start position:0% encrypt them in my browser so I can uh unencrypt<00:07:38.560> them<00:07:38.680> when<00:07:38.800> I<00:07:38.919> need<00:07:39.080> to<00:07:39.199> sign 00:07:39.629 --> 00:07:39.639 align:start position:0% unencrypt them when I need to sign 00:07:39.639 --> 00:07:42.029 align:start position:0% unencrypt them when I need to sign transactions<00:07:40.639> and<00:07:40.759> you<00:07:40.840> can<00:07:40.960> see<00:07:41.280> my<00:07:41.400> initials 00:07:42.029 --> 00:07:42.039 align:start position:0% transactions and you can see my initials 00:07:42.039 --> 00:07:45.550 align:start position:0% transactions and you can see my initials CK<00:07:42.879> under<00:07:43.160> the<00:07:43.319> accounts<00:07:44.159> um<00:07:44.479> comes<00:07:44.800> from<00:07:45.159> the 00:07:45.550 --> 00:07:45.560 align:start position:0% CK under the accounts um comes from the 00:07:45.560 --> 00:07:48.149 align:start position:0% CK under the accounts um comes from the the<00:07:45.680> uport<00:07:46.520> Persona<00:07:47.120> schema<00:07:47.599> that's<00:07:47.759> saved<00:07:48.000> an 00:07:48.149 --> 00:07:48.159 align:start position:0% the uport Persona schema that's saved an 00:07:48.159 --> 00:07:51.670 align:start position:0% the uport Persona schema that's saved an ipfs<00:07:48.919> I<00:07:49.400> I<00:07:49.520> use<00:07:49.840> that<00:07:50.240> to<00:07:50.560> associate<00:07:51.039> names<00:07:51.400> and 00:07:51.670 --> 00:07:51.680 align:start position:0% ipfs I I use that to associate names and 00:07:51.680 --> 00:07:54.070 align:start position:0% ipfs I I use that to associate names and images<00:07:52.240> with<00:07:52.840> ether 00:07:54.070 --> 00:07:54.080 align:start position:0% images with ether 00:07:54.080 --> 00:07:56.390 align:start position:0% images with ether addresses<00:07:55.080> so<00:07:55.240> we'll<00:07:55.479> add<00:07:55.800> the<00:07:55.960> the<00:07:56.080> second 00:07:56.390 --> 00:07:56.400 align:start position:0% addresses so we'll add the the second 00:07:56.400 --> 00:07:58.149 align:start position:0% addresses so we'll add the the second account<00:07:56.800> to<00:07:57.039> demonstrate<00:07:57.560> one<00:07:57.800> without<00:07:58.000> a 00:07:58.149 --> 00:07:58.159 align:start position:0% account to demonstrate one without a 00:07:58.159 --> 00:08:00.110 align:start position:0% account to demonstrate one without a Persona<00:07:58.960> and<00:07:59.120> you'll<00:07:59.280> see<00:07:59.560> see<00:07:59.680> that<00:07:59.840> in<00:08:00.000> in 00:08:00.110 --> 00:08:00.120 align:start position:0% Persona and you'll see see that in in 00:08:00.120 --> 00:08:03.550 align:start position:0% Persona and you'll see see that in in the<00:08:00.280> next<00:08:01.000> videos<00:08:02.000> so<00:08:02.440> that<00:08:02.560> is<00:08:02.720> adding<00:08:02.960> an 00:08:03.550 --> 00:08:03.560 align:start position:0% the next videos so that is adding an 00:08:03.560 --> 00:08:05.430 align:start position:0% the next videos so that is adding an account<00:08:04.560> um<00:08:04.680> and<00:08:04.800> this<00:08:04.879> is<00:08:05.000> the<00:08:05.080> identity 00:08:05.430 --> 00:08:05.440 align:start position:0% account um and this is the identity 00:08:05.440 --> 00:08:08.589 align:start position:0% account um and this is the identity schema<00:08:05.759> for<00:08:06.120> um<00:08:06.599> the<00:08:07.080> ort<00:08:08.080> uh<00:08:08.199> where<00:08:08.280> we<00:08:08.400> have 00:08:08.589 --> 00:08:08.599 align:start position:0% schema for um the ort uh where we have 00:08:08.599 --> 00:08:11.629 align:start position:0% schema for um the ort uh where we have name<00:08:09.360> and<00:08:09.840> content<00:08:10.159> URL<00:08:10.639> are<00:08:10.840> really<00:08:11.159> the<00:08:11.520> the 00:08:11.629 --> 00:08:11.639 align:start position:0% name and content URL are really the the 00:08:11.639 --> 00:08:13.909 align:start position:0% name and content URL are really the the important<00:08:11.960> Fields<00:08:12.360> there<00:08:12.919> but<00:08:13.240> but<00:08:13.440> this<00:08:13.560> is 00:08:13.909 --> 00:08:13.919 align:start position:0% important Fields there but but this is 00:08:13.919 --> 00:08:15.950 align:start position:0% important Fields there but but this is cool<00:08:14.240> because<00:08:14.440> it's<00:08:14.759> just<00:08:14.960> a<00:08:15.240> a<00:08:15.360> Json<00:08:15.759> so<00:08:15.879> you 00:08:15.950 --> 00:08:15.960 align:start position:0% cool because it's just a a Json so you 00:08:15.960 --> 00:08:17.469 align:start position:0% cool because it's just a a Json so you could<00:08:16.159> add<00:08:16.440> other<00:08:16.599> schemas<00:08:17.000> for<00:08:17.199> different 00:08:17.469 --> 00:08:17.479 align:start position:0% could add other schemas for different 00:08:17.479 --> 00:08:19.790 align:start position:0% could add other schemas for different use<00:08:17.759> cases<00:08:18.639> and<00:08:18.960> they<00:08:19.240> they<00:08:19.319> could<00:08:19.479> all<00:08:19.639> be 00:08:19.790 --> 00:08:19.800 align:start position:0% use cases and they they could all be 00:08:19.800 --> 00:08:22.390 align:start position:0% use cases and they they could all be derived<00:08:20.199> from<00:08:20.400> one<00:08:20.720> the<00:08:20.840> same<00:08:21.000> ether<00:08:21.400> address 00:08:22.390 --> 00:08:22.400 align:start position:0% derived from one the same ether address 00:08:22.400 --> 00:08:26.869 align:start position:0% derived from one the same ether address um<00:08:22.520> so<00:08:22.639> now<00:08:22.759> I'll<00:08:22.879> create<00:08:23.080> a<00:08:23.159> couple 00:08:26.869 --> 00:08:26.879 align:start position:0% 00:08:26.879 --> 00:08:30.469 align:start position:0% threads<00:08:27.879> right<00:08:28.080> so<00:08:28.360> I'll<00:08:28.560> use<00:08:28.840> my<00:08:29.720> my<00:08:29.960> named 00:08:30.469 --> 00:08:30.479 align:start position:0% threads right so I'll use my my named 00:08:30.479 --> 00:08:32.709 align:start position:0% threads right so I'll use my my named account<00:08:31.120> and<00:08:31.720> write<00:08:31.919> an<00:08:32.039> enter<00:08:32.279> in<00:08:32.399> a<00:08:32.479> thread 00:08:32.709 --> 00:08:32.719 align:start position:0% account and write an enter in a thread 00:08:32.719 --> 00:08:34.469 align:start position:0% account and write an enter in a thread name<00:08:32.959> this<00:08:33.039> is<00:08:33.159> going<00:08:33.240> to<00:08:33.360> use<00:08:33.479> a<00:08:33.640> string<00:08:34.159> data 00:08:34.469 --> 00:08:34.479 align:start position:0% name this is going to use a string data 00:08:34.479 --> 00:08:38.190 align:start position:0% name this is going to use a string data type<00:08:34.919> so<00:08:35.320> I<00:08:35.479> found<00:08:35.880> the<00:08:36.360> exact<00:08:36.800> gas<00:08:37.120> cost<00:08:37.560> per 00:08:38.190 --> 00:08:38.200 align:start position:0% type so I found the exact gas cost per 00:08:38.200 --> 00:08:39.870 align:start position:0% type so I found the exact gas cost per character<00:08:38.680> count<00:08:39.159> on<00:08:39.279> the<00:08:39.399> right<00:08:39.560> you'll<00:08:39.719> see 00:08:39.870 --> 00:08:39.880 align:start position:0% character count on the right you'll see 00:08:39.880 --> 00:08:41.550 align:start position:0% character count on the right you'll see that<00:08:40.080> transaction<00:08:40.560> price<00:08:40.800> increases<00:08:41.360> with 00:08:41.550 --> 00:08:41.560 align:start position:0% that transaction price increases with 00:08:41.560 --> 00:08:43.230 align:start position:0% that transaction price increases with each<00:08:41.839> character<00:08:42.240> that<00:08:42.360> I<00:08:42.519> add<00:08:42.800> so<00:08:43.000> this<00:08:43.120> is 00:08:43.230 --> 00:08:43.240 align:start position:0% each character that I add so this is 00:08:43.240 --> 00:08:45.870 align:start position:0% each character that I add so this is going<00:08:43.360> to<00:08:43.479> be<00:08:44.039> half<00:08:44.200> a<00:08:44.399> Cent<00:08:45.240> and<00:08:45.399> I'll<00:08:45.600> make<00:08:45.720> a 00:08:45.870 --> 00:08:45.880 align:start position:0% going to be half a Cent and I'll make a 00:08:45.880 --> 00:08:48.110 align:start position:0% going to be half a Cent and I'll make a random<00:08:46.200> one<00:08:47.040> and<00:08:47.160> a<00:08:47.279> meta<00:08:47.600> one<00:08:47.839> and<00:08:47.959> this 00:08:48.110 --> 00:08:48.120 align:start position:0% random one and a meta one and this 00:08:48.120 --> 00:08:49.910 align:start position:0% random one and a meta one and this bubble<00:08:48.399> on<00:08:48.519> the<00:08:48.640> left<00:08:48.880> means<00:08:49.200> that<00:08:49.440> the 00:08:49.910 --> 00:08:49.920 align:start position:0% bubble on the left means that the 00:08:49.920 --> 00:08:52.470 align:start position:0% bubble on the left means that the transaction<00:08:50.760> is<00:08:51.560> pending<00:08:51.920> it<00:08:52.040> hasn't<00:08:52.240> been 00:08:52.470 --> 00:08:52.480 align:start position:0% transaction is pending it hasn't been 00:08:52.480 --> 00:08:53.829 align:start position:0% transaction is pending it hasn't been received<00:08:52.600> in<00:08:52.640> a<00:08:52.760> block<00:08:53.000> real<00:08:53.200> quick<00:08:53.360> I'll<00:08:53.560> do<00:08:53.720> a 00:08:53.829 --> 00:08:53.839 align:start position:0% received in a block real quick I'll do a 00:08:53.839 --> 00:08:55.670 align:start position:0% received in a block real quick I'll do a Refresh<00:08:54.200> on<00:08:54.320> the<00:08:54.440> browser<00:08:54.959> just<00:08:55.080> to<00:08:55.279> prove 00:08:55.670 --> 00:08:55.680 align:start position:0% Refresh on the browser just to prove 00:08:55.680 --> 00:08:58.069 align:start position:0% Refresh on the browser just to prove that<00:08:56.240> I<00:08:56.360> keep<00:08:56.680> that<00:08:56.839> data<00:08:57.160> around<00:08:57.640> associated 00:08:58.069 --> 00:08:58.079 align:start position:0% that I keep that data around associated 00:08:58.079 --> 00:08:59.870 align:start position:0% that I keep that data around associated with<00:08:58.200> the<00:08:58.279> transaction<00:08:58.839> before<00:08:59.040> it<00:08:59.160> gets 00:08:59.870 --> 00:08:59.880 align:start position:0% with the transaction before it gets 00:08:59.880 --> 00:09:02.190 align:start position:0% with the transaction before it gets received<00:09:00.160> in<00:09:00.320> Block<00:09:00.680> so<00:09:01.440> um<00:09:01.600> that<00:09:01.760> tends<00:09:01.959> to<00:09:02.079> be 00:09:02.190 --> 00:09:02.200 align:start position:0% received in Block so um that tends to be 00:09:02.200 --> 00:09:03.430 align:start position:0% received in Block so um that tends to be something<00:09:02.440> that<00:09:02.519> users<00:09:02.880> like<00:09:03.000> to<00:09:03.160> do<00:09:03.320> when 00:09:03.430 --> 00:09:03.440 align:start position:0% something that users like to do when 00:09:03.440 --> 00:09:04.590 align:start position:0% something that users like to do when they<00:09:03.560> don't<00:09:03.920> understand<00:09:04.079> what's<00:09:04.240> going<00:09:04.399> on 00:09:04.590 --> 00:09:04.600 align:start position:0% they don't understand what's going on 00:09:04.600 --> 00:09:06.470 align:start position:0% they don't understand what's going on they'll<00:09:04.800> refresh<00:09:05.120> the<00:09:05.279> page<00:09:05.600> and<00:09:06.040> and<00:09:06.200> if<00:09:06.320> I 00:09:06.470 --> 00:09:06.480 align:start position:0% they'll refresh the page and and if I 00:09:06.480 --> 00:09:08.790 align:start position:0% they'll refresh the page and and if I don't<00:09:06.839> if<00:09:06.920> it's<00:09:07.079> just<00:09:07.200> blank<00:09:07.680> because<00:09:08.480> the<00:09:08.680> the 00:09:08.790 --> 00:09:08.800 align:start position:0% don't if it's just blank because the the 00:09:08.800 --> 00:09:10.990 align:start position:0% don't if it's just blank because the the data<00:09:09.000> is<00:09:09.120> not<00:09:09.240> on<00:09:09.399> chain<00:09:09.760> yet<00:09:10.000> then<00:09:10.680> uh<00:09:10.920> I 00:09:10.990 --> 00:09:11.000 align:start position:0% data is not on chain yet then uh I 00:09:11.000 --> 00:09:12.710 align:start position:0% data is not on chain yet then uh I wanted<00:09:11.200> to<00:09:11.320> prevented<00:09:11.720> that<00:09:11.839> scenario<00:09:12.360> so 00:09:12.710 --> 00:09:12.720 align:start position:0% wanted to prevented that scenario so 00:09:12.720 --> 00:09:15.389 align:start position:0% wanted to prevented that scenario so it'll<00:09:12.920> get<00:09:13.279> received<00:09:14.120> and<00:09:14.320> I<00:09:14.480> have<00:09:14.800> uh<00:09:15.000> another 00:09:15.389 --> 00:09:15.399 align:start position:0% it'll get received and I have uh another 00:09:15.399 --> 00:09:17.670 align:start position:0% it'll get received and I have uh another method<00:09:15.839> that<00:09:16.600> that<00:09:16.760> you<00:09:16.880> can<00:09:17.000> use<00:09:17.200> to<00:09:17.360> wrap 00:09:17.670 --> 00:09:17.680 align:start position:0% method that that you can use to wrap 00:09:17.680 --> 00:09:19.790 align:start position:0% method that that you can use to wrap components<00:09:18.360> that<00:09:18.560> that<00:09:18.680> use<00:09:19.040> that<00:09:19.279> mechanism 00:09:19.790 --> 00:09:19.800 align:start position:0% components that that use that mechanism 00:09:19.800 --> 00:09:23.790 align:start position:0% components that that use that mechanism for<00:09:20.320> TR<00:09:20.640> tracking<00:09:21.079> State<00:09:22.079> uh<00:09:22.640> to<00:09:23.120> to<00:09:23.399> determine 00:09:23.790 --> 00:09:23.800 align:start position:0% for TR tracking State uh to to determine 00:09:23.800 --> 00:09:25.470 align:start position:0% for TR tracking State uh to to determine based<00:09:24.000> on<00:09:24.120> the<00:09:24.200> current<00:09:24.480> block<00:09:25.040> which<00:09:25.320> which 00:09:25.470 --> 00:09:25.480 align:start position:0% based on the current block which which 00:09:25.480 --> 00:09:26.949 align:start position:0% based on the current block which which they'll<00:09:25.800> all<00:09:26.200> they'll<00:09:26.399> receive<00:09:26.720> as<00:09:26.839> it 00:09:26.949 --> 00:09:26.959 align:start position:0% they'll all they'll receive as it 00:09:26.959 --> 00:09:29.430 align:start position:0% they'll all they'll receive as it updates<00:09:27.720> what<00:09:27.959> the<00:09:28.480> the<00:09:28.600> percentage<00:09:29.040> of 00:09:29.430 --> 00:09:29.440 align:start position:0% updates what the the percentage of 00:09:29.440 --> 00:09:32.110 align:start position:0% updates what the the percentage of confirmation<00:09:29.920> is<00:09:30.120> given<00:09:30.399> some<00:09:30.920> confirm<00:09:31.360> count 00:09:32.110 --> 00:09:32.120 align:start position:0% confirmation is given some confirm count 00:09:32.120 --> 00:09:34.790 align:start position:0% confirmation is given some confirm count so<00:09:32.360> this<00:09:32.519> will<00:09:33.519> this<00:09:33.640> will<00:09:33.800> increment<00:09:34.200> up<00:09:34.360> to 00:09:34.790 --> 00:09:34.800 align:start position:0% so this will this will increment up to 00:09:34.800 --> 00:09:37.509 align:start position:0% so this will this will increment up to um<00:09:35.399> the<00:09:35.519> height<00:09:35.720> of<00:09:35.800> the<00:09:35.920> div<00:09:36.800> and<00:09:36.920> I'll<00:09:37.120> just 00:09:37.509 --> 00:09:37.519 align:start position:0% um the height of the div and I'll just 00:09:37.519 --> 00:09:39.670 align:start position:0% um the height of the div and I'll just skip<00:09:37.839> through<00:09:38.440> so<00:09:38.680> this<00:09:38.800> is<00:09:39.040> that<00:09:39.200> utility<00:09:39.600> I 00:09:39.670 --> 00:09:39.680 align:start position:0% skip through so this is that utility I 00:09:39.680 --> 00:09:42.110 align:start position:0% skip through so this is that utility I mentioned<00:09:40.160> it<00:09:40.480> it<00:09:40.800> it's<00:09:40.959> a<00:09:41.240> way<00:09:41.440> to<00:09:41.680> keep<00:09:41.880> track 00:09:42.110 --> 00:09:42.120 align:start position:0% mentioned it it it's a way to keep track 00:09:42.120 --> 00:09:45.350 align:start position:0% mentioned it it it's a way to keep track of<00:09:42.320> transaction<00:09:42.920> State<00:09:43.920> um<00:09:44.320> you<00:09:45.040> add 00:09:45.350 --> 00:09:45.360 align:start position:0% of transaction State um you add 00:09:45.360 --> 00:09:47.190 align:start position:0% of transaction State um you add transaction<00:09:45.880> hashes<00:09:46.519> and<00:09:46.640> you<00:09:46.800> associate 00:09:47.190 --> 00:09:47.200 align:start position:0% transaction hashes and you associate 00:09:47.200 --> 00:09:50.310 align:start position:0% transaction hashes and you associate some<00:09:47.360> data<00:09:47.560> with<00:09:47.680> those<00:09:47.880> hashes<00:09:48.880> and<00:09:49.519> you<00:09:49.680> can 00:09:50.310 --> 00:09:50.320 align:start position:0% some data with those hashes and you can 00:09:50.320 --> 00:09:53.790 align:start position:0% some data with those hashes and you can filter<00:09:50.880> through<00:09:51.600> uh<00:09:51.760> that<00:09:51.959> data<00:09:52.640> to<00:09:53.079> match 00:09:53.790 --> 00:09:53.800 align:start position:0% filter through uh that data to match 00:09:53.800 --> 00:09:55.590 align:start position:0% filter through uh that data to match those<00:09:54.000> transactions<00:09:54.600> to<00:09:55.000> components<00:09:55.360> on<00:09:55.480> your 00:09:55.590 --> 00:09:55.600 align:start position:0% those transactions to components on your 00:09:55.600 --> 00:09:58.430 align:start position:0% those transactions to components on your front<00:09:55.760> end<00:09:56.519> and<00:09:56.880> select<00:09:57.200> to<00:09:57.640> receive<00:09:58.000> any 00:09:58.430 --> 00:09:58.440 align:start position:0% front end and select to receive any 00:09:58.440 --> 00:10:00.910 align:start position:0% front end and select to receive any updates<00:09:58.800> from<00:09:58.959> these<00:09:59.120> St<00:09:59.720> from<00:10:00.399> transactions 00:10:00.910 --> 00:10:00.920 align:start position:0% updates from these St from transactions 00:10:00.920 --> 00:10:02.910 align:start position:0% updates from these St from transactions that<00:10:01.040> match<00:10:01.240> that<00:10:01.399> filter<00:10:02.399> um<00:10:02.519> so<00:10:02.680> for<00:10:02.800> this 00:10:02.910 --> 00:10:02.920 align:start position:0% that match that filter um so for this 00:10:02.920 --> 00:10:04.590 align:start position:0% that match that filter um so for this I'm<00:10:03.040> just<00:10:03.160> using<00:10:03.399> pending<00:10:03.640> and<00:10:03.959> received<00:10:04.320> but 00:10:04.590 --> 00:10:04.600 align:start position:0% I'm just using pending and received but 00:10:04.600 --> 00:10:05.990 align:start position:0% I'm just using pending and received but the<00:10:04.680> arrows<00:10:05.040> indicate<00:10:05.440> the<00:10:05.640> different 00:10:05.990 --> 00:10:06.000 align:start position:0% the arrows indicate the different 00:10:06.000 --> 00:10:07.750 align:start position:0% the arrows indicate the different directions<00:10:06.560> that<00:10:06.760> those<00:10:06.959> transitions<00:10:07.519> can 00:10:07.750 --> 00:10:07.760 align:start position:0% directions that those transitions can 00:10:07.760 --> 00:10:10.790 align:start position:0% directions that those transitions can happen<00:10:08.959> um<00:10:09.959> and<00:10:10.120> that's<00:10:10.320> that's<00:10:10.480> been<00:10:10.640> really 00:10:10.790 --> 00:10:10.800 align:start position:0% happen um and that's that's been really 00:10:10.800 --> 00:10:15.750 align:start position:0% happen um and that's that's been really helpful<00:10:11.800> so<00:10:12.560> let's<00:10:12.800> do<00:10:13.640> um<00:10:14.640> some<00:10:15.040> chat<00:10:15.519> and 00:10:15.750 --> 00:10:15.760 align:start position:0% helpful so let's do um some chat and 00:10:15.760 --> 00:10:18.470 align:start position:0% helpful so let's do um some chat and comment 00:10:18.470 --> 00:10:18.480 align:start position:0% 00:10:18.480 --> 00:10:21.110 align:start position:0% example<00:10:19.480> so<00:10:19.640> we'll<00:10:19.800> go<00:10:19.920> into<00:10:20.240> the<00:10:20.399> random 00:10:21.110 --> 00:10:21.120 align:start position:0% example so we'll go into the random 00:10:21.120 --> 00:10:24.310 align:start position:0% example so we'll go into the random thread<00:10:22.120> and<00:10:22.360> with<00:10:22.480> the<00:10:22.640> CK<00:10:23.320> account<00:10:24.000> we'll 00:10:24.310 --> 00:10:24.320 align:start position:0% thread and with the CK account we'll 00:10:24.320 --> 00:10:27.870 align:start position:0% thread and with the CK account we'll write<00:10:24.720> some<00:10:25.279> uh<00:10:25.600> yeah<00:10:25.760> so<00:10:25.880> this<00:10:26.000> is<00:10:26.440> 7<00:10:26.760> cents<00:10:27.680> at 00:10:27.870 --> 00:10:27.880 align:start position:0% write some uh yeah so this is 7 cents at 00:10:27.880 --> 00:10:31.870 align:start position:0% write some uh yeah so this is 7 cents at current<00:10:28.240> cost<00:10:28.680> so<00:10:29.399> yeah<00:10:29.600> first<00:10:30.320> post<00:10:31.320> um<00:10:31.600> sign 00:10:31.870 --> 00:10:31.880 align:start position:0% current cost so yeah first post um sign 00:10:31.880 --> 00:10:34.509 align:start position:0% current cost so yeah first post um sign the<00:10:32.480> transaction<00:10:33.480> and<00:10:33.640> it<00:10:33.760> will<00:10:33.920> do<00:10:34.160> the<00:10:34.279> same 00:10:34.509 --> 00:10:34.519 align:start position:0% the transaction and it will do the same 00:10:34.519 --> 00:10:36.470 align:start position:0% the transaction and it will do the same thing<00:10:34.839> and<00:10:34.959> you<00:10:35.079> see<00:10:35.560> uh<00:10:35.839> a<00:10:35.959> picture<00:10:36.240> that's 00:10:36.470 --> 00:10:36.480 align:start position:0% thing and you see uh a picture that's 00:10:36.480 --> 00:10:39.110 align:start position:0% thing and you see uh a picture that's associated<00:10:36.920> with<00:10:37.040> that<00:10:37.320> account<00:10:37.880> there<00:10:38.880> um 00:10:39.110 --> 00:10:39.120 align:start position:0% associated with that account there um 00:10:39.120 --> 00:10:40.269 align:start position:0% associated with that account there um and<00:10:39.200> now<00:10:39.320> we're<00:10:39.399> going<00:10:39.519> to<00:10:39.600> send<00:10:39.800> a<00:10:39.959> whisper 00:10:40.269 --> 00:10:40.279 align:start position:0% and now we're going to send a whisper 00:10:40.279 --> 00:10:41.870 align:start position:0% and now we're going to send a whisper message<00:10:40.680> while<00:10:40.920> that's<00:10:41.279> waiting<00:10:41.519> to<00:10:41.639> get 00:10:41.870 --> 00:10:41.880 align:start position:0% message while that's waiting to get 00:10:41.880 --> 00:10:42.949 align:start position:0% message while that's waiting to get received<00:10:42.000> in<00:10:42.160> Block<00:10:42.399> because<00:10:42.519> this<00:10:42.600> is<00:10:42.760> much 00:10:42.949 --> 00:10:42.959 align:start position:0% received in Block because this is much 00:10:42.959 --> 00:10:44.990 align:start position:0% received in Block because this is much faster<00:10:43.360> and<00:10:43.519> it's<00:10:43.680> free<00:10:44.360> so<00:10:44.560> some<00:10:44.760> people 00:10:44.990 --> 00:10:45.000 align:start position:0% faster and it's free so some people 00:10:45.000 --> 00:10:47.110 align:start position:0% faster and it's free so some people might<00:10:45.399> find<00:10:45.560> a<00:10:45.680> use<00:10:45.880> for<00:10:46.079> that<00:10:46.639> um<00:10:46.760> if<00:10:46.920> they<00:10:47.040> if 00:10:47.110 --> 00:10:47.120 align:start position:0% might find a use for that um if they if 00:10:47.120 --> 00:10:49.030 align:start position:0% might find a use for that um if they if they<00:10:47.200> don't<00:10:47.360> have<00:10:47.480> any<00:10:47.639> ether<00:10:48.160> or<00:10:48.720> don't<00:10:48.880> want 00:10:49.030 --> 00:10:49.040 align:start position:0% they don't have any ether or don't want 00:10:49.040 --> 00:10:51.190 align:start position:0% they don't have any ether or don't want their<00:10:49.200> message<00:10:49.440> to<00:10:49.600> live<00:10:49.760> forever<00:10:50.600> so<00:10:51.079> I'll 00:10:51.190 --> 00:10:51.200 align:start position:0% their message to live forever so I'll 00:10:51.200 --> 00:10:53.990 align:start position:0% their message to live forever so I'll demonstrate<00:10:51.680> how<00:10:51.920> this<00:10:52.240> wizzywig<00:10:52.839> editor<00:10:53.680> can 00:10:53.990 --> 00:10:54.000 align:start position:0% demonstrate how this wizzywig editor can 00:10:54.000 --> 00:10:55.829 align:start position:0% demonstrate how this wizzywig editor can can<00:10:54.240> throw<00:10:54.480> in<00:10:54.600> some<00:10:54.800> arbitrary 00:10:55.829 --> 00:10:55.839 align:start position:0% can throw in some arbitrary 00:10:55.839 --> 00:10:58.310 align:start position:0% can throw in some arbitrary HTML<00:10:56.839> that<00:10:56.959> my<00:10:57.079> front<00:10:57.320> end<00:10:57.560> will<00:10:58.000> uh<00:10:58.160> will 00:10:58.310 --> 00:10:58.320 align:start position:0% HTML that my front end will uh will 00:10:58.320 --> 00:11:00.590 align:start position:0% HTML that my front end will uh will sanitize<00:10:58.959> when<00:10:59.120> it<00:10:59.440> picks<00:10:59.639> it<00:10:59.760> up<00:11:00.320> and<00:11:00.440> I'll 00:11:00.590 --> 00:11:00.600 align:start position:0% sanitize when it picks it up and I'll 00:11:00.600 --> 00:11:03.269 align:start position:0% sanitize when it picks it up and I'll also<00:11:00.880> add<00:11:01.399> um<00:11:01.720> an<00:11:01.839> array<00:11:02.120> of<00:11:02.279> files<00:11:02.800> just<00:11:02.959> one 00:11:03.269 --> 00:11:03.279 align:start position:0% also add um an array of files just one 00:11:03.279 --> 00:11:05.949 align:start position:0% also add um an array of files just one for<00:11:03.519> this<00:11:04.079> demo<00:11:04.399> but<00:11:04.519> you<00:11:04.600> can<00:11:04.760> add<00:11:04.959> multiple 00:11:05.949 --> 00:11:05.959 align:start position:0% for this demo but you can add multiple 00:11:05.959 --> 00:11:07.629 align:start position:0% for this demo but you can add multiple um<00:11:06.079> you<00:11:06.160> can<00:11:06.279> rename<00:11:06.600> the<00:11:06.680> file<00:11:06.920> name<00:11:07.120> add<00:11:07.240> a 00:11:07.629 --> 00:11:07.639 align:start position:0% um you can rename the file name add a 00:11:07.639 --> 00:11:12.790 align:start position:0% um you can rename the file name add a description<00:11:08.639> to<00:11:08.839> the<00:11:08.959> Moon<00:11:10.160> um<00:11:11.240> and<00:11:12.240> so<00:11:12.560> you 00:11:12.790 --> 00:11:12.800 align:start position:0% description to the Moon um and so you 00:11:12.800 --> 00:11:14.350 align:start position:0% description to the Moon um and so you actually<00:11:13.120> also<00:11:13.440> sign<00:11:13.839> these<00:11:14.000> whisper 00:11:14.350 --> 00:11:14.360 align:start position:0% actually also sign these whisper 00:11:14.360 --> 00:11:17.350 align:start position:0% actually also sign these whisper messages<00:11:14.959> with<00:11:15.200> your<00:11:15.440> same<00:11:16.440> uh<00:11:16.760> light<00:11:17.040> wallet 00:11:17.350 --> 00:11:17.360 align:start position:0% messages with your same uh light wallet 00:11:17.360 --> 00:11:19.509 align:start position:0% messages with your same uh light wallet accounts<00:11:17.800> so<00:11:18.360> that<00:11:18.519> signature<00:11:18.959> gets<00:11:19.160> appended 00:11:19.509 --> 00:11:19.519 align:start position:0% accounts so that signature gets appended 00:11:19.519 --> 00:11:22.550 align:start position:0% accounts so that signature gets appended to<00:11:19.639> the<00:11:19.720> payload<00:11:20.680> so<00:11:21.200> the<00:11:21.440> front<00:11:21.680> end<00:11:22.040> can 00:11:22.550 --> 00:11:22.560 align:start position:0% to the payload so the front end can 00:11:22.560 --> 00:11:24.350 align:start position:0% to the payload so the front end can derive<00:11:23.079> the<00:11:23.399> The<00:11:23.519> Ether<00:11:23.839> address<00:11:24.160> of<00:11:24.279> the 00:11:24.350 --> 00:11:24.360 align:start position:0% derive the The Ether address of the 00:11:24.360 --> 00:11:26.829 align:start position:0% derive the The Ether address of the sender<00:11:25.240> otherwise<00:11:25.639> it's<00:11:26.120> it's<00:11:26.240> stored<00:11:26.600> on<00:11:26.720> the 00:11:26.829 --> 00:11:26.839 align:start position:0% sender otherwise it's it's stored on the 00:11:26.839 --> 00:11:28.870 align:start position:0% sender otherwise it's it's stored on the client<00:11:27.200> it's<00:11:27.320> not<00:11:27.560> really<00:11:27.880> usable<00:11:28.519> for<00:11:28.720> for 00:11:28.870 --> 00:11:28.880 align:start position:0% client it's not really usable for for 00:11:28.880 --> 00:11:31.190 align:start position:0% client it's not really usable for for these<00:11:29.000> types<00:11:29.360> of<00:11:29.480> apps<00:11:30.240> so<00:11:30.440> I<00:11:30.560> switch<00:11:30.880> accounts 00:11:31.190 --> 00:11:31.200 align:start position:0% these types of apps so I switch accounts 00:11:31.200 --> 00:11:33.310 align:start position:0% these types of apps so I switch accounts I'm<00:11:31.279> going<00:11:31.399> to<00:11:31.680> reply<00:11:32.680> very<00:11:32.880> cool<00:11:33.160> I'm<00:11:33.240> going 00:11:33.310 --> 00:11:33.320 align:start position:0% I'm going to reply very cool I'm going 00:11:33.320 --> 00:11:35.829 align:start position:0% I'm going to reply very cool I'm going to<00:11:33.440> save<00:11:33.800> this<00:11:34.800> and<00:11:34.920> you<00:11:35.000> see<00:11:35.200> how<00:11:35.399> there's<00:11:35.760> a 00:11:35.829 --> 00:11:35.839 align:start position:0% to save this and you see how there's a 00:11:35.839 --> 00:11:37.470 align:start position:0% to save this and you see how there's a jenton<00:11:36.600> associated<00:11:37.000> with<00:11:37.120> that<00:11:37.279> because<00:11:37.399> it 00:11:37.470 --> 00:11:37.480 align:start position:0% jenton associated with that because it 00:11:37.480 --> 00:11:40.030 align:start position:0% jenton associated with that because it doesn't<00:11:37.680> have<00:11:37.760> a<00:11:37.880> Persona<00:11:38.680> and<00:11:38.800> I<00:11:38.920> just<00:11:39.120> saved 00:11:40.030 --> 00:11:40.040 align:start position:0% doesn't have a Persona and I just saved 00:11:40.040 --> 00:11:42.910 align:start position:0% doesn't have a Persona and I just saved the<00:11:40.240> other<00:11:40.560> accounts<00:11:41.279> whisper<00:11:41.720> message<00:11:42.600> into 00:11:42.910 --> 00:11:42.920 align:start position:0% the other accounts whisper message into 00:11:42.920 --> 00:11:45.829 align:start position:0% the other accounts whisper message into ipfs<00:11:43.440> and<00:11:43.560> stored<00:11:43.920> that<00:11:44.200> that<00:11:44.399> ipfs<00:11:44.959> hash<00:11:45.600> on 00:11:45.829 --> 00:11:45.839 align:start position:0% ipfs and stored that that ipfs hash on 00:11:45.839 --> 00:11:48.269 align:start position:0% ipfs and stored that that ipfs hash on chain<00:11:46.399> and<00:11:46.519> the<00:11:46.639> front<00:11:46.839> end<00:11:47.079> was<00:11:47.240> able<00:11:47.480> to<00:11:48.120> to 00:11:48.269 --> 00:11:48.279 align:start position:0% chain and the front end was able to to 00:11:48.279 --> 00:11:49.910 align:start position:0% chain and the front end was able to to figure<00:11:48.600> that<00:11:48.760> out<00:11:49.200> that<00:11:49.440> that<00:11:49.560> this<00:11:49.680> was<00:11:49.800> a 00:11:49.910 --> 00:11:49.920 align:start position:0% figure that out that that this was a 00:11:49.920 --> 00:11:51.829 align:start position:0% figure that out that that this was a whisper<00:11:50.320> object<00:11:50.800> looks<00:11:51.000> at<00:11:51.160> the<00:11:51.320> signature 00:11:51.829 --> 00:11:51.839 align:start position:0% whisper object looks at the signature 00:11:51.839 --> 00:11:55.030 align:start position:0% whisper object looks at the signature deres<00:11:52.200> the<00:11:52.320> sender<00:11:52.720> address<00:11:53.680> and<00:11:53.880> uses<00:11:54.279> CK<00:11:54.800> as 00:11:55.030 --> 00:11:55.040 align:start position:0% deres the sender address and uses CK as 00:11:55.040 --> 00:11:57.870 align:start position:0% deres the sender address and uses CK as the<00:11:55.279> as<00:11:55.399> the<00:11:55.519> center<00:11:55.959> of<00:11:56.200> that<00:11:57.160> comments<00:11:57.639> even 00:11:57.870 --> 00:11:57.880 align:start position:0% the as the center of that comments even 00:11:57.880 --> 00:12:00.790 align:start position:0% the as the center of that comments even though<00:11:58.600> even<00:11:58.760> though<00:11:58.920> 3<00:11:59.240> 1<00:11:59.440> D<00:11:59.639> is<00:11:59.880> the<00:12:00.040> owner<00:12:00.480> of 00:12:00.790 --> 00:12:00.800 align:start position:0% though even though 3 1 D is the owner of 00:12:00.800 --> 00:12:02.190 align:start position:0% though even though 3 1 D is the owner of of<00:12:00.959> that<00:12:01.160> post 00:12:02.190 --> 00:12:02.200 align:start position:0% of that post 00:12:02.200 --> 00:12:04.670 align:start position:0% of that post object<00:12:03.200> um 00:12:04.670 --> 00:12:04.680 align:start position:0% object um 00:12:04.680 --> 00:12:09.790 align:start position:0% object um so<00:12:05.680> yeah<00:12:05.839> offer<00:12:06.240> a<00:12:06.440> thank<00:12:06.639> you<00:12:07.800> and<00:12:08.800> that's 00:12:09.790 --> 00:12:09.800 align:start position:0% so yeah offer a thank you and that's 00:12:09.800 --> 00:12:12.389 align:start position:0% so yeah offer a thank you and that's pretty<00:12:10.040> much<00:12:11.000> the<00:12:11.120> meat<00:12:11.399> of<00:12:11.639> this<00:12:12.040> the<00:12:12.240> the 00:12:12.389 --> 00:12:12.399 align:start position:0% pretty much the meat of this the the 00:12:12.399 --> 00:12:14.069 align:start position:0% pretty much the meat of this the the rest<00:12:12.600> is<00:12:12.920> I'll<00:12:13.120> just<00:12:13.360> go<00:12:13.519> through<00:12:13.760> and<00:12:13.880> show 00:12:14.069 --> 00:12:14.079 align:start position:0% rest is I'll just go through and show 00:12:14.079 --> 00:12:15.870 align:start position:0% rest is I'll just go through and show that<00:12:14.199> you<00:12:14.320> can<00:12:14.519> chat<00:12:14.720> and<00:12:14.880> comment<00:12:15.240> on<00:12:15.480> on<00:12:15.680> any 00:12:15.870 --> 00:12:15.880 align:start position:0% that you can chat and comment on on any 00:12:15.880 --> 00:12:19.509 align:start position:0% that you can chat and comment on on any of<00:12:16.120> these<00:12:17.040> uh<00:12:17.639> onchain<00:12:18.160> posts<00:12:18.639> or<00:12:18.920> whisper 00:12:19.509 --> 00:12:19.519 align:start position:0% of these uh onchain posts or whisper 00:12:19.519 --> 00:12:22.629 align:start position:0% of these uh onchain posts or whisper messages<00:12:20.519> but<00:12:20.959> uh<00:12:21.360> yeah<00:12:21.519> so<00:12:21.680> we'll<00:12:21.839> move 00:12:22.629 --> 00:12:22.639 align:start position:0% messages but uh yeah so we'll move 00:12:22.639 --> 00:12:26.310 align:start position:0% messages but uh yeah so we'll move on<00:12:23.639> this<00:12:23.760> is<00:12:23.920> a<00:12:24.279> schema<00:12:24.720> of<00:12:25.000> the<00:12:25.240> ipfs<00:12:25.880> content 00:12:26.310 --> 00:12:26.320 align:start position:0% on this is a schema of the ipfs content 00:12:26.320 --> 00:12:28.269 align:start position:0% on this is a schema of the ipfs content that<00:12:26.440> I<00:12:26.560> save<00:12:27.279> pretty<00:12:27.519> straightforward<00:12:28.160> just 00:12:28.269 --> 00:12:28.279 align:start position:0% that I save pretty straightforward just 00:12:28.279 --> 00:12:32.230 align:start position:0% that I save pretty straightforward just an<00:12:28.399> HTML<00:12:28.839> string<00:12:29.360> and<00:12:29.560> an<00:12:29.720> array<00:12:30.199> of<00:12:31.120> uh<00:12:31.279> file 00:12:32.230 --> 00:12:32.240 align:start position:0% an HTML string and an array of uh file 00:12:32.240 --> 00:12:34.629 align:start position:0% an HTML string and an array of uh file descriptions<00:12:33.240> uh<00:12:33.360> and<00:12:33.519> IP<00:12:33.800> Fest<00:12:34.000> hashes<00:12:34.519> and 00:12:34.629 --> 00:12:34.639 align:start position:0% descriptions uh and IP Fest hashes and 00:12:34.639 --> 00:12:36.629 align:start position:0% descriptions uh and IP Fest hashes and then<00:12:34.880> on<00:12:35.000> the<00:12:35.160> right<00:12:35.399> is<00:12:35.680> the<00:12:35.839> whisper<00:12:36.240> object 00:12:36.629 --> 00:12:36.639 align:start position:0% then on the right is the whisper object 00:12:36.639 --> 00:12:38.710 align:start position:0% then on the right is the whisper object that<00:12:36.760> I've<00:12:37.160> modified<00:12:37.560> a<00:12:37.639> little<00:12:37.839> bit<00:12:38.519> uh<00:12:38.600> with 00:12:38.710 --> 00:12:38.720 align:start position:0% that I've modified a little bit uh with 00:12:38.720 --> 00:12:43.110 align:start position:0% that I've modified a little bit uh with the<00:12:38.839> signature<00:12:39.480> recovery<00:12:39.920> pram<00:12:40.639> and<00:12:41.560> the<00:12:42.120> hash 00:12:43.110 --> 00:12:43.120 align:start position:0% the signature recovery pram and the hash 00:12:43.120 --> 00:12:45.590 align:start position:0% the signature recovery pram and the hash uh<00:12:43.320> the<00:12:43.560> topic<00:12:44.079> that<00:12:44.199> I<00:12:44.320> use<00:12:44.639> for<00:12:44.880> whisper<00:12:45.320> is<00:12:45.440> a 00:12:45.590 --> 00:12:45.600 align:start position:0% uh the topic that I use for whisper is a 00:12:45.600 --> 00:12:47.949 align:start position:0% uh the topic that I use for whisper is a hash<00:12:45.839> of<00:12:46.199> the<00:12:46.639> the<00:12:46.800> contract<00:12:47.199> address<00:12:47.639> and<00:12:47.800> the 00:12:47.949 --> 00:12:47.959 align:start position:0% hash of the the contract address and the 00:12:47.959 --> 00:12:51.389 align:start position:0% hash of the the contract address and the post<00:12:48.199> ID<00:12:49.000> that<00:12:49.120> you're<00:12:50.040> whispering 00:12:51.389 --> 00:12:51.399 align:start position:0% post ID that you're whispering 00:12:51.399 --> 00:12:53.790 align:start position:0% post ID that you're whispering to<00:12:52.399> and<00:12:52.519> these<00:12:52.639> are<00:12:52.760> the<00:12:52.880> libraries<00:12:53.279> that<00:12:53.399> I<00:12:53.480> Ed 00:12:53.790 --> 00:12:53.800 align:start position:0% to and these are the libraries that I Ed 00:12:53.800 --> 00:12:55.150 align:start position:0% to and these are the libraries that I Ed that<00:12:54.079> that<00:12:54.160> were<00:12:54.320> really<00:12:54.519> helpful<00:12:54.800> for<00:12:54.959> me 00:12:55.150 --> 00:12:55.160 align:start position:0% that that were really helpful for me 00:12:55.160 --> 00:12:58.910 align:start position:0% that that were really helpful for me obviously<00:12:55.519> web<00:12:55.720> 3<00:12:56.680> um<00:12:57.320> the<00:12:57.760> the<00:12:57.880> ipfs<00:12:58.360> teams<00:12:58.720> I 00:12:58.910 --> 00:12:58.920 align:start position:0% obviously web 3 um the the ipfs teams I 00:12:58.920 --> 00:13:01.870 align:start position:0% obviously web 3 um the the ipfs teams I know<00:12:59.240> IPS<00:12:59.639> API<00:13:00.600> exposes<00:13:01.040> pretty<00:13:01.199> much<00:13:01.360> every 00:13:01.870 --> 00:13:01.880 align:start position:0% know IPS API exposes pretty much every 00:13:01.880 --> 00:13:04.629 align:start position:0% know IPS API exposes pretty much every ipfs<00:13:02.320> command<00:13:02.760> to<00:13:03.040> http<00:13:03.959> so<00:13:04.279> that<00:13:04.360> was<00:13:04.480> really 00:13:04.629 --> 00:13:04.639 align:start position:0% ipfs command to http so that was really 00:13:04.639 --> 00:13:06.670 align:start position:0% ipfs command to http so that was really helpful<00:13:05.240> hooked<00:13:05.519> web<00:13:05.680> 3<00:13:05.839> provider<00:13:06.160> Tim<00:13:06.360> couter 00:13:06.670 --> 00:13:06.680 align:start position:0% helpful hooked web 3 provider Tim couter 00:13:06.680 --> 00:13:09.150 align:start position:0% helpful hooked web 3 provider Tim couter wrote<00:13:07.440> uh<00:13:07.519> it's<00:13:07.680> a<00:13:07.920> super<00:13:08.160> easy<00:13:08.480> way<00:13:08.639> to<00:13:08.880> sign 00:13:09.150 --> 00:13:09.160 align:start position:0% wrote uh it's a super easy way to sign 00:13:09.160 --> 00:13:11.310 align:start position:0% wrote uh it's a super easy way to sign transactions<00:13:09.639> in<00:13:09.760> your<00:13:09.880> browser<00:13:10.720> uh<00:13:10.839> E<00:13:11.120> Light 00:13:11.310 --> 00:13:11.320 align:start position:0% transactions in your browser uh E Light 00:13:11.320 --> 00:13:14.230 align:start position:0% transactions in your browser uh E Light wallet<00:13:12.120> um<00:13:12.360> is<00:13:12.560> what<00:13:12.760> Christian<00:13:13.120> wrote<00:13:13.880> and 00:13:14.230 --> 00:13:14.240 align:start position:0% wallet um is what Christian wrote and 00:13:14.240 --> 00:13:16.189 align:start position:0% wallet um is what Christian wrote and that's<00:13:14.680> uh<00:13:14.839> a<00:13:14.959> key<00:13:15.199> store<00:13:15.519> and<00:13:15.680> man<00:13:15.959> key 00:13:16.189 --> 00:13:16.199 align:start position:0% that's uh a key store and man key 00:13:16.199 --> 00:13:18.430 align:start position:0% that's uh a key store and man key manager<00:13:16.959> for<00:13:17.199> for<00:13:17.360> signing<00:13:17.680> transactions 00:13:18.430 --> 00:13:18.440 align:start position:0% manager for for signing transactions 00:13:18.440 --> 00:13:20.509 align:start position:0% manager for for signing transactions those<00:13:18.920> that<00:13:19.079> and<00:13:19.199> hooked<00:13:19.440> web<00:13:19.639> 3<00:13:19.959> go<00:13:20.160> go<00:13:20.360> really 00:13:20.509 --> 00:13:20.519 align:start position:0% those that and hooked web 3 go go really 00:13:20.519 --> 00:13:22.790 align:start position:0% those that and hooked web 3 go go really easily<00:13:21.079> together<00:13:22.000> um<00:13:22.240> and<00:13:22.360> then<00:13:22.519> finally 00:13:22.790 --> 00:13:22.800 align:start position:0% easily together um and then finally 00:13:22.800 --> 00:13:24.870 align:start position:0% easily together um and then finally reflex<00:13:23.240> TX<00:13:23.519> is<00:13:23.720> the<00:13:23.920> transaction<00:13:24.360> manager<00:13:24.720> I 00:13:24.870 --> 00:13:24.880 align:start position:0% reflex TX is the transaction manager I 00:13:24.880 --> 00:13:27.550 align:start position:0% reflex TX is the transaction manager I wrote<00:13:25.880> um<00:13:26.079> so<00:13:26.279> that's<00:13:26.480> all<00:13:26.839> if<00:13:27.120> there<00:13:27.240> are<00:13:27.360> any 00:13:27.550 --> 00:13:27.560 align:start position:0% wrote um so that's all if there are any 00:13:27.560 --> 00:13:29.750 align:start position:0% wrote um so that's all if there are any questions<00:13:28.040> I<00:13:28.240> have<00:13:28.720> uh 00:13:29.750 --> 00:13:29.760 align:start position:0% questions I have uh 00:13:29.760 --> 00:13:39.350 align:start position:0% questions I have uh few<00:13:29.959> minutes<00:13:30.720> two 00:13:39.350 --> 00:13:39.360 align:start position:0% 00:13:39.360 --> 00:13:48.629 align:start position:0% minutes<00:13:40.360> yeah<00:13:40.480> we<00:13:40.560> have<00:13:40.680> time<00:13:40.839> for<00:13:41.000> one 00:13:48.629 --> 00:13:48.639 align:start position:0% 00:13:48.639 --> 00:13:51.030 align:start position:0% question<00:13:49.639> so<00:13:49.800> I<00:13:49.920> think<00:13:50.120> one<00:13:50.240> of<00:13:50.399> the<00:13:50.600> bigger 00:13:51.030 --> 00:13:51.040 align:start position:0% question so I think one of the bigger 00:13:51.040 --> 00:13:53.670 align:start position:0% question so I think one of the bigger problems<00:13:51.560> with<00:13:51.800> Reddit<00:13:52.240> and<00:13:52.399> any<00:13:52.720> tread<00:13:53.320> is 00:13:53.670 --> 00:13:53.680 align:start position:0% problems with Reddit and any tread is 00:13:53.680 --> 00:13:57.590 align:start position:0% problems with Reddit and any tread is the<00:13:54.320> the<00:13:54.480> matter<00:13:55.040> of<00:13:56.000> how<00:13:56.160> do<00:13:56.320> you<00:13:57.320> get 00:13:57.590 --> 00:13:57.600 align:start position:0% the the matter of how do you get 00:13:57.600 --> 00:14:00.590 align:start position:0% the the matter of how do you get reputation<00:13:58.360> how<00:13:58.480> do<00:13:58.600> you<00:13:58.759> count<00:13:59.279> Karma<00:13:59.720> or<00:14:00.399> in 00:14:00.590 --> 00:14:00.600 align:start position:0% reputation how do you count Karma or in 00:14:00.600 --> 00:14:02.990 align:start position:0% reputation how do you count Karma or in any<00:14:00.800> sort<00:14:01.079> of<00:14:01.240> system<00:14:01.560> on<00:14:01.720> how<00:14:01.959> do<00:14:02.279> how<00:14:02.399> do<00:14:02.560> you 00:14:02.990 --> 00:14:03.000 align:start position:0% any sort of system on how do how do you 00:14:03.000 --> 00:14:06.829 align:start position:0% any sort of system on how do how do you fight<00:14:03.480> spam<00:14:04.079> while<00:14:04.399> keeping<00:14:04.839> good<00:14:05.160> content<00:14:05.839> to 00:14:06.829 --> 00:14:06.839 align:start position:0% fight spam while keeping good content to 00:14:06.839 --> 00:14:09.550 align:start position:0% fight spam while keeping good content to on<00:14:06.959> the<00:14:07.199> top<00:14:07.759> how<00:14:07.920> do<00:14:08.079> you<00:14:08.720> want<00:14:09.160> how<00:14:09.320> do<00:14:09.399> you 00:14:09.550 --> 00:14:09.560 align:start position:0% on the top how do you want how do you 00:14:09.560 --> 00:14:12.069 align:start position:0% on the top how do you want how do you plan<00:14:09.839> to<00:14:10.199> solve<00:14:10.639> that<00:14:10.920> in<00:14:11.040> a<00:14:11.279> system<00:14:11.839> where 00:14:12.069 --> 00:14:12.079 align:start position:0% plan to solve that in a system where 00:14:12.079 --> 00:14:16.069 align:start position:0% plan to solve that in a system where without<00:14:12.480> having<00:14:13.279> single<00:14:13.880> single<00:14:14.240> user<00:14:14.680> single 00:14:16.069 --> 00:14:16.079 align:start position:0% without having single single user single 00:14:16.079 --> 00:14:18.910 align:start position:0% without having single single user single person<00:14:17.079> yeah<00:14:17.240> so<00:14:17.480> I<00:14:17.560> think<00:14:18.040> uh<00:14:18.399> that<00:14:18.600> is<00:14:18.720> a 00:14:18.910 --> 00:14:18.920 align:start position:0% person yeah so I think uh that is a 00:14:18.920 --> 00:14:21.470 align:start position:0% person yeah so I think uh that is a really<00:14:19.120> hard<00:14:19.399> problem<00:14:20.079> and<00:14:20.759> uh<00:14:21.000> I<00:14:21.120> don't<00:14:21.240> claim 00:14:21.470 --> 00:14:21.480 align:start position:0% really hard problem and uh I don't claim 00:14:21.480 --> 00:14:23.389 align:start position:0% really hard problem and uh I don't claim to<00:14:21.560> know<00:14:21.680> the<00:14:21.839> answer<00:14:22.360> but<00:14:22.720> I<00:14:22.880> I<00:14:22.959> think<00:14:23.199> that<00:14:23.320> we 00:14:23.389 --> 00:14:23.399 align:start position:0% to know the answer but I I think that we 00:14:23.399 --> 00:14:25.110 align:start position:0% to know the answer but I I think that we should<00:14:23.560> all<00:14:24.040> anybody<00:14:24.440> interested<00:14:24.880> should 00:14:25.110 --> 00:14:25.120 align:start position:0% should all anybody interested should 00:14:25.120 --> 00:14:26.629 align:start position:0% should all anybody interested should should<00:14:25.320> try<00:14:25.480> to<00:14:25.600> build<00:14:25.839> something<00:14:26.120> like<00:14:26.320> that 00:14:26.629 --> 00:14:26.639 align:start position:0% should try to build something like that 00:14:26.639 --> 00:14:29.069 align:start position:0% should try to build something like that and<00:14:27.000> and<00:14:27.360> I'd<00:14:27.560> Advocate<00:14:27.920> using<00:14:28.519> some<00:14:28.639> of<00:14:28.759> these 00:14:29.069 --> 00:14:29.079 align:start position:0% and and I'd Advocate using some of these 00:14:29.079 --> 00:14:31.350 align:start position:0% and and I'd Advocate using some of these tools<00:14:29.320> to<00:14:29.480> do<00:14:29.639> so<00:14:30.360> um<00:14:30.519> I'll<00:14:30.720> also<00:14:30.959> be<00:14:31.120> working 00:14:31.350 --> 00:14:31.360 align:start position:0% tools to do so um I'll also be working 00:14:31.360 --> 00:14:32.629 align:start position:0% tools to do so um I'll also be working on 00:14:32.629 --> 00:14:32.639 align:start position:0% on 00:14:32.639 --> 00:14:34.749 align:start position:0% on that<00:14:33.639> unfortunately<00:14:34.199> we<00:14:34.320> do<00:14:34.399> not<00:14:34.519> have<00:14:34.639> any 00:14:34.749 --> 00:14:34.759 align:start position:0% that unfortunately we do not have any 00:14:34.759 --> 00:14:36.150 align:start position:0% that unfortunately we do not have any more<00:14:34.920> time<00:14:35.040> for<00:14:35.240> questions<00:14:35.720> thank<00:14:35.880> you<00:14:36.000> so 00:14:36.150 --> 00:14:36.160 align:start position:0% more time for questions thank you so 00:14:36.160 --> 00:14:42.620 align:start position:0% more time for questions thank you so much<00:14:36.399> Conor<00:14:36.839> and<00:14:37.000> your<00:14:37.279> decentralized 00:14:42.620 --> 00:14:42.630 align:start position:0% 00:14:42.630 --> 00:14:46.960 align:start position:0% [Music]