WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:14.990 align:start position:0% [Music] 00:00:14.990 --> 00:00:15.000 align:start position:0% 00:00:15.000 --> 00:00:18.470 align:start position:0% all<00:00:15.520> right<00:00:16.520> um<00:00:16.960> thank<00:00:17.119> you<00:00:17.240> for<00:00:17.480> that<00:00:18.199> uh<00:00:18.279> it's 00:00:18.470 --> 00:00:18.480 align:start position:0% all right um thank you for that uh it's 00:00:18.480 --> 00:00:20.189 align:start position:0% all right um thank you for that uh it's one<00:00:18.600> of<00:00:18.720> the<00:00:18.880> last<00:00:19.080> talks<00:00:19.320> of<00:00:19.480> the<00:00:19.640> day<00:00:20.039> we 00:00:20.189 --> 00:00:20.199 align:start position:0% one of the last talks of the day we 00:00:20.199 --> 00:00:23.029 align:start position:0% one of the last talks of the day we don't<00:00:20.400> have<00:00:20.560> much<00:00:20.800> time<00:00:21.119> so<00:00:21.840> hope<00:00:22.000> it'll<00:00:22.279> be<00:00:22.880> a 00:00:23.029 --> 00:00:23.039 align:start position:0% don't have much time so hope it'll be a 00:00:23.039 --> 00:00:24.990 align:start position:0% don't have much time so hope it'll be a good<00:00:23.199> one<00:00:23.359> for<00:00:23.560> you<00:00:23.760> guys<00:00:24.320> yeah<00:00:24.439> so<00:00:24.599> my<00:00:24.720> name<00:00:24.840> is 00:00:24.990 --> 00:00:25.000 align:start position:0% good one for you guys yeah so my name is 00:00:25.000 --> 00:00:27.630 align:start position:0% good one for you guys yeah so my name is Arun<00:00:25.680> I<00:00:26.039> uh<00:00:26.160> work<00:00:26.400> with<00:00:26.560> UNICEF<00:00:27.320> I<00:00:27.480> the 00:00:27.630 --> 00:00:27.640 align:start position:0% Arun I uh work with UNICEF I the 00:00:27.640 --> 00:00:29.429 align:start position:0% Arun I uh work with UNICEF I the blockchain<00:00:28.080> lead<00:00:28.480> at<00:00:28.599> the<00:00:28.720> ventures<00:00:29.199> team 00:00:29.429 --> 00:00:29.439 align:start position:0% blockchain lead at the ventures team 00:00:29.439 --> 00:00:31.990 align:start position:0% blockchain lead at the ventures team within<00:00:29.640> the<00:00:29.720> UN<00:00:30.279> office<00:00:30.519> of<00:00:31.320> uh<00:00:31.439> Innovation 00:00:31.990 --> 00:00:32.000 align:start position:0% within the UN office of uh Innovation 00:00:32.000 --> 00:00:34.510 align:start position:0% within the UN office of uh Innovation and<00:00:32.160> we<00:00:32.239> are<00:00:32.399> here<00:00:32.559> to<00:00:33.239> uh<00:00:33.360> chat<00:00:33.800> with<00:00:34.239> one<00:00:34.399> of 00:00:34.510 --> 00:00:34.520 align:start position:0% and we are here to uh chat with one of 00:00:34.520 --> 00:00:36.389 align:start position:0% and we are here to uh chat with one of our<00:00:34.719> portfolio<00:00:35.200> companies<00:00:35.600> stawick<00:00:36.160> around 00:00:36.389 --> 00:00:36.399 align:start position:0% our portfolio companies stawick around 00:00:36.399 --> 00:00:37.869 align:start position:0% our portfolio companies stawick around the<00:00:36.520> supply<00:00:36.840> chain<00:00:37.079> solution<00:00:37.559> that<00:00:37.680> they 00:00:37.869 --> 00:00:37.879 align:start position:0% the supply chain solution that they 00:00:37.879 --> 00:00:38.990 align:start position:0% the supply chain solution that they worked<00:00:38.120> on<00:00:38.239> and<00:00:38.360> the<00:00:38.480> impact<00:00:38.800> they<00:00:38.879> are 00:00:38.990 --> 00:00:39.000 align:start position:0% worked on and the impact they are 00:00:39.000 --> 00:00:41.990 align:start position:0% worked on and the impact they are creating<00:00:39.800> along<00:00:40.160> with<00:00:40.680> uh<00:00:41.239> uh<00:00:41.360> a<00:00:41.520> partner<00:00:41.840> of 00:00:41.990 --> 00:00:42.000 align:start position:0% creating along with uh uh a partner of 00:00:42.000 --> 00:00:43.950 align:start position:0% creating along with uh uh a partner of ours<00:00:42.239> on<00:00:42.399> you<00:00:42.480> know<00:00:42.640> how<00:00:42.800> to<00:00:43.039> get<00:00:43.399> these<00:00:43.600> open- 00:00:43.950 --> 00:00:43.960 align:start position:0% ours on you know how to get these open- 00:00:43.960 --> 00:00:47.430 align:start position:0% ours on you know how to get these open- Source<00:00:44.600> uh<00:00:44.800> digital<00:00:45.200> public<00:00:45.520> goods<00:00:46.280> funded<00:00:47.280> um 00:00:47.430 --> 00:00:47.440 align:start position:0% Source uh digital public goods funded um 00:00:47.440 --> 00:00:48.830 align:start position:0% Source uh digital public goods funded um may<00:00:47.520> I<00:00:47.640> ask<00:00:47.800> you<00:00:47.960> guys<00:00:48.079> to<00:00:48.199> quickly<00:00:48.480> introduce 00:00:48.830 --> 00:00:48.840 align:start position:0% may I ask you guys to quickly introduce 00:00:48.840 --> 00:00:51.630 align:start position:0% may I ask you guys to quickly introduce yourself<00:00:49.199> starting<00:00:49.480> with<00:00:49.640> Mani<00:00:50.520> yeah<00:00:50.800> sure<00:00:51.480> uh 00:00:51.630 --> 00:00:51.640 align:start position:0% yourself starting with Mani yeah sure uh 00:00:51.640 --> 00:00:54.310 align:start position:0% yourself starting with Mani yeah sure uh thanks<00:00:51.879> a<00:00:52.520> uh<00:00:52.760> hi<00:00:53.039> good<00:00:53.160> evening<00:00:53.559> everyone<00:00:54.160> my 00:00:54.310 --> 00:00:54.320 align:start position:0% thanks a uh hi good evening everyone my 00:00:54.320 --> 00:00:56.549 align:start position:0% thanks a uh hi good evening everyone my name<00:00:54.520> is<00:00:54.680> Mani<00:00:55.320> I'm<00:00:55.559> the<00:00:55.760> head<00:00:55.920> of<00:00:56.079> product<00:00:56.399> at 00:00:56.549 --> 00:00:56.559 align:start position:0% name is Mani I'm the head of product at 00:00:56.559 --> 00:00:58.389 align:start position:0% name is Mani I'm the head of product at statway<00:00:57.359> we<00:00:57.480> are<00:00:57.600> a<00:00:57.719> blockchain<00:00:58.120> based 00:00:58.389 --> 00:00:58.399 align:start position:0% statway we are a blockchain based 00:00:58.399 --> 00:01:00.389 align:start position:0% statway we are a blockchain based company<00:00:58.840> where<00:00:59.039> we<00:00:59.120> are<00:00:59.480> basically<00:01:00.039> focused 00:01:00.389 --> 00:01:00.399 align:start position:0% company where we are basically focused 00:01:00.399 --> 00:01:02.310 align:start position:0% company where we are basically focused on<00:01:00.559> enhancing<00:01:01.079> the<00:01:01.280> transparency<00:01:01.920> and 00:01:02.310 --> 00:01:02.320 align:start position:0% on enhancing the transparency and 00:01:02.320 --> 00:01:04.390 align:start position:0% on enhancing the transparency and efficiency<00:01:03.320> uh<00:01:03.480> in<00:01:03.600> the<00:01:03.800> global<00:01:04.119> Health 00:01:04.390 --> 00:01:04.400 align:start position:0% efficiency uh in the global Health 00:01:04.400 --> 00:01:06.670 align:start position:0% efficiency uh in the global Health public<00:01:04.720> Supply<00:01:05.040> chains<00:01:05.799> what<00:01:05.960> we<00:01:06.159> essentially 00:01:06.670 --> 00:01:06.680 align:start position:0% public Supply chains what we essentially 00:01:06.680 --> 00:01:09.550 align:start position:0% public Supply chains what we essentially do<00:01:07.159> is<00:01:07.640> uh<00:01:07.840> help<00:01:08.159> stakeholders<00:01:08.880> keep<00:01:09.040> a<00:01:09.240> track 00:01:09.550 --> 00:01:09.560 align:start position:0% do is uh help stakeholders keep a track 00:01:09.560 --> 00:01:12.149 align:start position:0% do is uh help stakeholders keep a track of<00:01:09.720> all<00:01:09.920> their<00:01:10.400> transactions<00:01:11.400> and<00:01:11.759> give<00:01:11.960> end 00:01:12.149 --> 00:01:12.159 align:start position:0% of all their transactions and give end 00:01:12.159 --> 00:01:14.590 align:start position:0% of all their transactions and give end to<00:01:12.280> end<00:01:12.520> visibility<00:01:13.000> in<00:01:13.119> the<00:01:13.280> supply 00:01:14.590 --> 00:01:14.600 align:start position:0% to end visibility in the supply 00:01:14.600 --> 00:01:16.950 align:start position:0% to end visibility in the supply chains<00:01:15.600> thank<00:01:15.759> you<00:01:16.040> and<00:01:16.400> thank<00:01:16.520> you<00:01:16.680> both<00:01:16.799> for 00:01:16.950 --> 00:01:16.960 align:start position:0% chains thank you and thank you both for 00:01:16.960 --> 00:01:20.109 align:start position:0% chains thank you and thank you both for the<00:01:17.080> invitation<00:01:17.759> today<00:01:18.759> uh<00:01:18.920> David<00:01:19.200> Casey<00:01:19.680> here 00:01:20.109 --> 00:01:20.119 align:start position:0% the invitation today uh David Casey here 00:01:20.119 --> 00:01:22.670 align:start position:0% the invitation today uh David Casey here director<00:01:20.680> of<00:01:20.840> funding<00:01:21.240> the<00:01:21.560> commons<00:01:22.560> uh 00:01:22.670 --> 00:01:22.680 align:start position:0% director of funding the commons uh 00:01:22.680 --> 00:01:24.950 align:start position:0% director of funding the commons uh funding<00:01:22.960> the<00:01:23.119> commons<00:01:23.560> is<00:01:23.759> a<00:01:24.079> community<00:01:24.680> and 00:01:24.950 --> 00:01:24.960 align:start position:0% funding the commons is a community and 00:01:24.960 --> 00:01:27.870 align:start position:0% funding the commons is a community and event<00:01:25.280> series<00:01:25.840> focused<00:01:26.280> around<00:01:26.880> exploring 00:01:27.870 --> 00:01:27.880 align:start position:0% event series focused around exploring 00:01:27.880 --> 00:01:30.710 align:start position:0% event series focused around exploring public<00:01:28.159> goods<00:01:28.479> funding<00:01:29.119> mechanisms<00:01:30.360> and<00:01:30.560> we 00:01:30.710 --> 00:01:30.720 align:start position:0% public goods funding mechanisms and we 00:01:30.720 --> 00:01:33.830 align:start position:0% public goods funding mechanisms and we do<00:01:31.000> conferences<00:01:32.200> hackathons<00:01:33.200> uh<00:01:33.320> open<00:01:33.560> source 00:01:33.830 --> 00:01:33.840 align:start position:0% do conferences hackathons uh open source 00:01:33.840 --> 00:01:35.630 align:start position:0% do conferences hackathons uh open source developer<00:01:34.320> residencies<00:01:34.920> we<00:01:35.079> just<00:01:35.200> completed 00:01:35.630 --> 00:01:35.640 align:start position:0% developer residencies we just completed 00:01:35.640 --> 00:01:38.590 align:start position:0% developer residencies we just completed one<00:01:35.759> in<00:01:35.920> changai<00:01:36.560> last<00:01:36.759> month<00:01:37.600> and<00:01:38.200> uh<00:01:38.360> public 00:01:38.590 --> 00:01:38.600 align:start position:0% one in changai last month and uh public 00:01:38.600 --> 00:01:41.469 align:start position:0% one in changai last month and uh public goods<00:01:38.840> funding<00:01:39.320> experiments<00:01:39.920> so<00:01:40.320> applied<00:01:41.320> uh 00:01:41.469 --> 00:01:41.479 align:start position:0% goods funding experiments so applied uh 00:01:41.479 --> 00:01:44.190 align:start position:0% goods funding experiments so applied uh experiments<00:01:42.000> using<00:01:42.360> new<00:01:42.880> new 00:01:44.190 --> 00:01:44.200 align:start position:0% experiments using new new 00:01:44.200 --> 00:01:46.590 align:start position:0% experiments using new new mechanisms<00:01:45.200> so<00:01:45.399> in<00:01:45.560> case<00:01:45.719> you<00:01:45.960> wondering<00:01:46.439> what 00:01:46.590 --> 00:01:46.600 align:start position:0% mechanisms so in case you wondering what 00:01:46.600 --> 00:01:48.510 align:start position:0% mechanisms so in case you wondering what a<00:01:46.759> UNICEF<00:01:47.240> person<00:01:47.520> is<00:01:47.640> doing<00:01:47.920> here<00:01:48.119> so<00:01:48.280> we<00:01:48.399> have 00:01:48.510 --> 00:01:48.520 align:start position:0% a UNICEF person is doing here so we have 00:01:48.520 --> 00:01:51.310 align:start position:0% a UNICEF person is doing here so we have been<00:01:48.680> working<00:01:49.040> with<00:01:49.280> blockchain<00:01:49.840> since<00:01:50.320> 2015 00:01:51.310 --> 00:01:51.320 align:start position:0% been working with blockchain since 2015 00:01:51.320 --> 00:01:52.709 align:start position:0% been working with blockchain since 2015 uh<00:01:51.439> we<00:01:51.560> run<00:01:51.840> something<00:01:52.119> called<00:01:52.280> the<00:01:52.360> UNICEF 00:01:52.709 --> 00:01:52.719 align:start position:0% uh we run something called the UNICEF 00:01:52.719 --> 00:01:55.550 align:start position:0% uh we run something called the UNICEF Venture<00:01:53.040> fund<00:01:53.560> where<00:01:53.880> we<00:01:54.240> provide<00:01:55.119> uh<00:01:55.240> funding 00:01:55.550 --> 00:01:55.560 align:start position:0% Venture fund where we provide uh funding 00:01:55.560 --> 00:01:58.469 align:start position:0% Venture fund where we provide uh funding for<00:01:55.759> early<00:01:56.039> stage<00:01:56.360> startups<00:01:56.840> such<00:01:57.039> as<00:01:57.799> uh<00:01:57.920> stat 00:01:58.469 --> 00:01:58.479 align:start position:0% for early stage startups such as uh stat 00:01:58.479 --> 00:02:00.510 align:start position:0% for early stage startups such as uh stat that<00:01:58.600> man<00:01:58.960> is<00:01:59.039> working<00:01:59.280> for<00:01:59.960> uh<00:02:00.079> and<00:02:00.200> we<00:02:00.280> are 00:02:00.510 --> 00:02:00.520 align:start position:0% that man is working for uh and we are 00:02:00.520 --> 00:02:02.190 align:start position:0% that man is working for uh and we are also<00:02:00.759> interested<00:02:01.119> in<00:02:01.280> digital<00:02:01.680> public<00:02:01.960> goods 00:02:02.190 --> 00:02:02.200 align:start position:0% also interested in digital public goods 00:02:02.200 --> 00:02:03.590 align:start position:0% also interested in digital public goods we<00:02:02.280> are<00:02:02.399> part<00:02:02.560> of<00:02:02.640> the<00:02:02.759> digital<00:02:03.079> public<00:02:03.320> goods 00:02:03.590 --> 00:02:03.600 align:start position:0% we are part of the digital public goods 00:02:03.600 --> 00:02:05.670 align:start position:0% we are part of the digital public goods Alliance<00:02:04.000> and<00:02:04.200> that's<00:02:04.360> how<00:02:04.640> we<00:02:05.039> got<00:02:05.200> to<00:02:05.360> know 00:02:05.670 --> 00:02:05.680 align:start position:0% Alliance and that's how we got to know 00:02:05.680 --> 00:02:08.510 align:start position:0% Alliance and that's how we got to know David<00:02:06.119> So<00:02:06.479> hence<00:02:06.920> here<00:02:07.079> I<00:02:07.200> am<00:02:08.080> uh<00:02:08.280> first 00:02:08.510 --> 00:02:08.520 align:start position:0% David So hence here I am uh first 00:02:08.520 --> 00:02:10.109 align:start position:0% David So hence here I am uh first question<00:02:08.759> to<00:02:08.920> Mani<00:02:09.280> could<00:02:09.399> you<00:02:09.560> please<00:02:09.840> maybe 00:02:10.109 --> 00:02:10.119 align:start position:0% question to Mani could you please maybe 00:02:10.119 --> 00:02:12.910 align:start position:0% question to Mani could you please maybe talk<00:02:10.319> a<00:02:10.440> bit<00:02:10.759> of<00:02:11.120> the<00:02:11.360> product<00:02:12.319> uh<00:02:12.480> around<00:02:12.760> the 00:02:12.910 --> 00:02:12.920 align:start position:0% talk a bit of the product uh around the 00:02:12.920 --> 00:02:16.190 align:start position:0% talk a bit of the product uh around the vaccine<00:02:13.280> Supply<00:02:13.560> chains<00:02:14.080> please<00:02:15.080> uh<00:02:15.360> yeah<00:02:16.120> uh 00:02:16.190 --> 00:02:16.200 align:start position:0% vaccine Supply chains please uh yeah uh 00:02:16.200 --> 00:02:18.229 align:start position:0% vaccine Supply chains please uh yeah uh so<00:02:16.360> I<00:02:16.440> think<00:02:16.640> the<00:02:16.800> problem<00:02:17.560> um<00:02:17.879> the<00:02:18.160> the 00:02:18.229 --> 00:02:18.239 align:start position:0% so I think the problem um the the 00:02:18.239 --> 00:02:19.670 align:start position:0% so I think the problem um the the challenge<00:02:18.640> that<00:02:18.760> we<00:02:18.840> were<00:02:19.040> looking<00:02:19.280> at<00:02:19.519> was 00:02:19.670 --> 00:02:19.680 align:start position:0% challenge that we were looking at was 00:02:19.680 --> 00:02:22.350 align:start position:0% challenge that we were looking at was twofold<00:02:20.680> uh<00:02:20.800> so<00:02:21.000> the<00:02:21.160> first<00:02:21.440> initial<00:02:21.959> issue 00:02:22.350 --> 00:02:22.360 align:start position:0% twofold uh so the first initial issue 00:02:22.360 --> 00:02:24.750 align:start position:0% twofold uh so the first initial issue was<00:02:22.599> around<00:02:23.560> uh<00:02:23.680> how<00:02:23.920> the<00:02:24.080> supply<00:02:24.319> chains<00:02:24.560> are 00:02:24.750 --> 00:02:24.760 align:start position:0% was around uh how the supply chains are 00:02:24.760 --> 00:02:27.190 align:start position:0% was around uh how the supply chains are fragmented<00:02:25.760> and<00:02:26.360> specifically<00:02:26.920> in<00:02:27.040> the 00:02:27.190 --> 00:02:27.200 align:start position:0% fragmented and specifically in the 00:02:27.200 --> 00:02:29.229 align:start position:0% fragmented and specifically in the Healthcare<00:02:27.640> Systems<00:02:28.120> how<00:02:28.319> they<00:02:28.480> rely<00:02:28.800> on 00:02:29.229 --> 00:02:29.239 align:start position:0% Healthcare Systems how they rely on 00:02:29.239 --> 00:02:31.030 align:start position:0% Healthcare Systems how they rely on siloed<00:02:29.640> and<00:02:29.879> information<00:02:30.360> which<00:02:30.480> do<00:02:30.640> not<00:02:30.840> talk 00:02:31.030 --> 00:02:31.040 align:start position:0% siloed and information which do not talk 00:02:31.040 --> 00:02:33.190 align:start position:0% siloed and information which do not talk to<00:02:31.200> each<00:02:31.360> other<00:02:32.120> the<00:02:32.280> other<00:02:32.519> issue<00:02:32.800> was<00:02:32.959> also 00:02:33.190 --> 00:02:33.200 align:start position:0% to each other the other issue was also 00:02:33.200 --> 00:02:34.790 align:start position:0% to each other the other issue was also around<00:02:33.519> product<00:02:33.840> wastage<00:02:34.239> in<00:02:34.360> terms<00:02:34.599> of 00:02:34.790 --> 00:02:34.800 align:start position:0% around product wastage in terms of 00:02:34.800 --> 00:02:37.030 align:start position:0% around product wastage in terms of expiry<00:02:35.599> counter<00:02:36.000> feating<00:02:36.400> and<00:02:36.560> cold<00:02:36.800> chain 00:02:37.030 --> 00:02:37.040 align:start position:0% expiry counter feating and cold chain 00:02:37.040 --> 00:02:39.229 align:start position:0% expiry counter feating and cold chain failures<00:02:37.879> so<00:02:38.080> these<00:02:38.519> this<00:02:38.680> was<00:02:38.879> like<00:02:39.040> the 00:02:39.229 --> 00:02:39.239 align:start position:0% failures so these this was like the 00:02:39.239 --> 00:02:41.270 align:start position:0% failures so these this was like the primary<00:02:39.879> agenda<00:02:40.360> that<00:02:40.480> we<00:02:40.640> wanted<00:02:40.920> to<00:02:41.120> like 00:02:41.270 --> 00:02:41.280 align:start position:0% primary agenda that we wanted to like 00:02:41.280 --> 00:02:44.190 align:start position:0% primary agenda that we wanted to like you<00:02:41.400> know<00:02:42.200> uh<00:02:42.840> solve<00:02:43.200> firsthand<00:02:43.800> and<00:02:43.959> like<00:02:44.080> you 00:02:44.190 --> 00:02:44.200 align:start position:0% you know uh solve firsthand and like you 00:02:44.200 --> 00:02:46.670 align:start position:0% you know uh solve firsthand and like you know<00:02:44.400> have<00:02:44.720> a<00:02:44.879> unified<00:02:45.440> platform<00:02:46.200> so<00:02:46.400> that<00:02:46.519> is 00:02:46.670 --> 00:02:46.680 align:start position:0% know have a unified platform so that is 00:02:46.680 --> 00:02:48.990 align:start position:0% know have a unified platform so that is where<00:02:46.879> we've<00:02:47.120> built<00:02:47.640> a<00:02:47.920> a<00:02:48.080> solution<00:02:48.640> called 00:02:48.990 --> 00:02:49.000 align:start position:0% where we've built a a solution called 00:02:49.000 --> 00:02:51.470 align:start position:0% where we've built a a solution called vaccine<00:02:49.440> Ledger<00:02:50.440> uh<00:02:50.599> which<00:02:50.840> typically 00:02:51.470 --> 00:02:51.480 align:start position:0% vaccine Ledger uh which typically 00:02:51.480 --> 00:02:54.309 align:start position:0% vaccine Ledger uh which typically ensures<00:02:52.239> that<00:02:52.840> uh<00:02:53.040> every<00:02:53.319> physical<00:02:53.879> asset<00:02:54.200> in 00:02:54.309 --> 00:02:54.319 align:start position:0% ensures that uh every physical asset in 00:02:54.319 --> 00:02:56.750 align:start position:0% ensures that uh every physical asset in the<00:02:54.480> supply<00:02:54.840> chain<00:02:55.519> uh<00:02:55.640> we<00:02:55.800> create<00:02:56.200> a<00:02:56.360> digital 00:02:56.750 --> 00:02:56.760 align:start position:0% the supply chain uh we create a digital 00:02:56.760 --> 00:03:00.309 align:start position:0% the supply chain uh we create a digital twin<00:02:57.120> of<00:02:57.360> that<00:02:58.280> uh<00:02:58.519> and<00:02:58.680> so<00:02:58.920> from<00:02:59.560> what<00:03:00.120> how 00:03:00.309 --> 00:03:00.319 align:start position:0% twin of that uh and so from what how 00:03:00.319 --> 00:03:01.790 align:start position:0% twin of that uh and so from what how that<00:03:00.519> works<00:03:00.800> is<00:03:00.959> that<00:03:01.159> from<00:03:01.360> the<00:03:01.480> time<00:03:01.640> of 00:03:01.790 --> 00:03:01.800 align:start position:0% that works is that from the time of 00:03:01.800 --> 00:03:03.430 align:start position:0% that works is that from the time of procurement<00:03:02.480> or<00:03:02.640> from<00:03:02.840> the<00:03:03.040> point<00:03:03.280> of 00:03:03.430 --> 00:03:03.440 align:start position:0% procurement or from the point of 00:03:03.440 --> 00:03:05.309 align:start position:0% procurement or from the point of manufacturing<00:03:04.440> and<00:03:04.560> every<00:03:04.799> time<00:03:04.959> the<00:03:05.080> product 00:03:05.309 --> 00:03:05.319 align:start position:0% manufacturing and every time the product 00:03:05.319 --> 00:03:07.110 align:start position:0% manufacturing and every time the product changes<00:03:05.720> hands<00:03:06.040> we<00:03:06.159> basically<00:03:06.599> record<00:03:07.040> the 00:03:07.110 --> 00:03:07.120 align:start position:0% changes hands we basically record the 00:03:07.120 --> 00:03:08.869 align:start position:0% changes hands we basically record the Journey<00:03:07.440> of<00:03:07.640> products<00:03:08.120> as<00:03:08.239> in<00:03:08.400> how<00:03:08.560> it<00:03:08.680> is 00:03:08.869 --> 00:03:08.879 align:start position:0% Journey of products as in how it is 00:03:08.879 --> 00:03:12.190 align:start position:0% Journey of products as in how it is passing<00:03:09.200> on<00:03:09.840> so<00:03:10.319> we<00:03:11.040> uh<00:03:11.159> help<00:03:11.480> ensure<00:03:11.920> that<00:03:12.080> you 00:03:12.190 --> 00:03:12.200 align:start position:0% passing on so we uh help ensure that you 00:03:12.200 --> 00:03:14.030 align:start position:0% passing on so we uh help ensure that you know<00:03:12.400> all<00:03:12.560> these<00:03:12.840> stakeholders<00:03:13.840> are 00:03:14.030 --> 00:03:14.040 align:start position:0% know all these stakeholders are 00:03:14.040 --> 00:03:15.910 align:start position:0% know all these stakeholders are completely<00:03:14.560> aware<00:03:14.920> of<00:03:15.120> where<00:03:15.319> the<00:03:15.440> product<00:03:15.799> is 00:03:15.910 --> 00:03:15.920 align:start position:0% completely aware of where the product is 00:03:15.920 --> 00:03:18.670 align:start position:0% completely aware of where the product is in<00:03:16.120> supply<00:03:16.440> chain<00:03:16.840> right<00:03:17.000> now<00:03:17.959> uh<00:03:18.200> yeah<00:03:18.400> and 00:03:18.670 --> 00:03:18.680 align:start position:0% in supply chain right now uh yeah and 00:03:18.680 --> 00:03:21.149 align:start position:0% in supply chain right now uh yeah and and<00:03:18.879> we<00:03:19.080> did<00:03:19.480> we<00:03:19.640> did<00:03:20.040> also<00:03:20.400> have<00:03:20.640> like<00:03:20.799> issues 00:03:21.149 --> 00:03:21.159 align:start position:0% and we did we did also have like issues 00:03:21.159 --> 00:03:23.190 align:start position:0% and we did we did also have like issues looking<00:03:21.440> around<00:03:21.799> how<00:03:22.040> 30%<00:03:22.640> of<00:03:22.760> the<00:03:22.879> global 00:03:23.190 --> 00:03:23.200 align:start position:0% looking around how 30% of the global 00:03:23.200 --> 00:03:25.630 align:start position:0% looking around how 30% of the global vaccines<00:03:23.640> were<00:03:23.840> wasted<00:03:24.840> and<00:03:25.080> there<00:03:25.200> was<00:03:25.440> lack 00:03:25.630 --> 00:03:25.640 align:start position:0% vaccines were wasted and there was lack 00:03:25.640 --> 00:03:28.350 align:start position:0% vaccines were wasted and there was lack of<00:03:25.840> information<00:03:26.519> even<00:03:26.879> within<00:03:27.799> uh<00:03:27.920> you<00:03:28.040> know 00:03:28.350 --> 00:03:28.360 align:start position:0% of information even within uh you know 00:03:28.360 --> 00:03:30.309 align:start position:0% of information even within uh you know many<00:03:28.680> organizations<00:03:29.519> who<00:03:29.879> where<00:03:30.159> like 00:03:30.309 --> 00:03:30.319 align:start position:0% many organizations who where like 00:03:30.319 --> 00:03:33.030 align:start position:0% many organizations who where like sending<00:03:30.599> out<00:03:30.879> products<00:03:31.239> to<00:03:31.599> various<00:03:32.319> uh<00:03:32.920> uh 00:03:33.030 --> 00:03:33.040 align:start position:0% sending out products to various uh uh 00:03:33.040 --> 00:03:34.830 align:start position:0% sending out products to various uh uh lmic<00:03:33.640> countries<00:03:34.040> but<00:03:34.159> there<00:03:34.280> was<00:03:34.439> like<00:03:34.640> lack 00:03:34.830 --> 00:03:34.840 align:start position:0% lmic countries but there was like lack 00:03:34.840 --> 00:03:36.390 align:start position:0% lmic countries but there was like lack of<00:03:35.000> visibility<00:03:35.519> whether<00:03:35.720> it's<00:03:35.879> reaching<00:03:36.239> the 00:03:36.390 --> 00:03:36.400 align:start position:0% of visibility whether it's reaching the 00:03:36.400 --> 00:03:38.830 align:start position:0% of visibility whether it's reaching the final<00:03:36.799> beneficiaries<00:03:37.439> or<00:03:37.560> not<00:03:38.200> so<00:03:38.560> it<00:03:38.720> it 00:03:38.830 --> 00:03:38.840 align:start position:0% final beneficiaries or not so it it 00:03:38.840 --> 00:03:40.869 align:start position:0% final beneficiaries or not so it it becomes<00:03:39.200> very<00:03:39.560> important<00:03:40.120> and<00:03:40.319> critical<00:03:40.720> to 00:03:40.869 --> 00:03:40.879 align:start position:0% becomes very important and critical to 00:03:40.879 --> 00:03:42.509 align:start position:0% becomes very important and critical to ensure<00:03:41.239> that<00:03:41.360> the<00:03:41.480> life<00:03:41.680> saving<00:03:42.000> vaccines<00:03:42.400> and 00:03:42.509 --> 00:03:42.519 align:start position:0% ensure that the life saving vaccines and 00:03:42.519 --> 00:03:44.990 align:start position:0% ensure that the life saving vaccines and medicines<00:03:43.000> reach<00:03:43.280> to<00:03:43.480> those<00:03:44.040> uh<00:03:44.480> people 00:03:44.990 --> 00:03:45.000 align:start position:0% medicines reach to those uh people 00:03:45.000 --> 00:03:47.470 align:start position:0% medicines reach to those uh people especially<00:03:45.400> in<00:03:45.519> the<00:03:45.760> underd<00:03:46.120> deserved<00:03:46.519> areas 00:03:47.470 --> 00:03:47.480 align:start position:0% especially in the underd deserved areas 00:03:47.480 --> 00:03:49.270 align:start position:0% especially in the underd deserved areas and<00:03:47.840> that's<00:03:48.040> how<00:03:48.239> I<00:03:48.360> think<00:03:48.720> what<00:03:48.959> what<00:03:49.080> we're 00:03:49.270 --> 00:03:49.280 align:start position:0% and that's how I think what what we're 00:03:49.280 --> 00:03:52.509 align:start position:0% and that's how I think what what we're trying<00:03:49.519> to<00:03:49.680> do<00:03:50.080> is<00:03:50.640> uh<00:03:50.799> leverage<00:03:51.519> blockchain 00:03:52.509 --> 00:03:52.519 align:start position:0% trying to do is uh leverage blockchain 00:03:52.519 --> 00:03:54.910 align:start position:0% trying to do is uh leverage blockchain uh<00:03:52.799> and<00:03:53.120> provide<00:03:53.560> that<00:03:54.159> uh<00:03:54.319> you<00:03:54.439> know<00:03:54.799> the 00:03:54.910 --> 00:03:54.920 align:start position:0% uh and provide that uh you know the 00:03:54.920 --> 00:03:57.949 align:start position:0% uh and provide that uh you know the whole<00:03:55.319> data<00:03:56.319> uh<00:03:56.439> in<00:03:56.599> real<00:03:56.920> time<00:03:57.319> for<00:03:57.720> every 00:03:57.949 --> 00:03:57.959 align:start position:0% whole data uh in real time for every 00:03:57.959 --> 00:04:01.750 align:start position:0% whole data uh in real time for every stakeholder<00:03:58.480> to<00:03:58.640> make<00:03:58.959> informed<00:03:59.360> decisions 00:04:01.750 --> 00:04:01.760 align:start position:0% 00:04:01.760 --> 00:04:05.309 align:start position:0% that's<00:04:02.000> fantastic<00:04:03.239> so<00:04:04.239> um<00:04:04.519> blockchain<00:04:05.120> here 00:04:05.309 --> 00:04:05.319 align:start position:0% that's fantastic so um blockchain here 00:04:05.319 --> 00:04:07.750 align:start position:0% that's fantastic so um blockchain here is<00:04:05.480> of<00:04:05.640> course<00:04:05.840> used<00:04:06.079> to<00:04:06.319> track<00:04:06.799> every<00:04:07.159> vial<00:04:07.519> of 00:04:07.750 --> 00:04:07.760 align:start position:0% is of course used to track every vial of 00:04:07.760 --> 00:04:10.190 align:start position:0% is of course used to track every vial of the<00:04:07.920> vaccine<00:04:08.760> I<00:04:08.840> think<00:04:09.079> which<00:04:09.360> adds<00:04:09.640> a<00:04:09.840> next 00:04:10.190 --> 00:04:10.200 align:start position:0% the vaccine I think which adds a next 00:04:10.200 --> 00:04:12.830 align:start position:0% the vaccine I think which adds a next layer<00:04:10.599> of<00:04:11.280> traceability<00:04:12.280> uh<00:04:12.439> and<00:04:12.560> you<00:04:12.680> know 00:04:12.830 --> 00:04:12.840 align:start position:0% layer of traceability uh and you know 00:04:12.840 --> 00:04:15.910 align:start position:0% layer of traceability uh and you know visibility<00:04:13.519> which<00:04:14.079> uh<00:04:14.200> all<00:04:14.360> the<00:04:14.920> stakeholders 00:04:15.910 --> 00:04:15.920 align:start position:0% visibility which uh all the stakeholders 00:04:15.920 --> 00:04:19.069 align:start position:0% visibility which uh all the stakeholders uh<00:04:16.160> get<00:04:16.600> and<00:04:16.919> U<00:04:17.120> talking<00:04:17.400> of<00:04:17.560> stakeholders<00:04:18.560> uh 00:04:19.069 --> 00:04:19.079 align:start position:0% uh get and U talking of stakeholders uh 00:04:19.079 --> 00:04:22.189 align:start position:0% uh get and U talking of stakeholders uh where<00:04:19.359> have<00:04:19.519> you<00:04:19.959> piloted<00:04:20.519> this<00:04:21.000> solution<00:04:22.000> uh 00:04:22.189 --> 00:04:22.199 align:start position:0% where have you piloted this solution uh 00:04:22.199 --> 00:04:23.070 align:start position:0% where have you piloted this solution uh so 00:04:23.070 --> 00:04:23.080 align:start position:0% so 00:04:23.080 --> 00:04:26.270 align:start position:0% so far<00:04:24.080> uh<00:04:24.479> yeah<00:04:24.639> so<00:04:24.880> we<00:04:25.199> we've<00:04:25.400> had<00:04:25.720> a<00:04:25.840> couple<00:04:26.080> of 00:04:26.270 --> 00:04:26.280 align:start position:0% far uh yeah so we we've had a couple of 00:04:26.280 --> 00:04:29.029 align:start position:0% far uh yeah so we we've had a couple of deployments<00:04:27.000> so<00:04:27.600> we<00:04:27.759> had<00:04:27.919> it<00:04:28.120> both<00:04:28.360> on<00:04:28.600> the 00:04:29.029 --> 00:04:29.039 align:start position:0% deployments so we had it both on the 00:04:29.039 --> 00:04:31.790 align:start position:0% deployments so we had it both on the private<00:04:29.400> side<00:04:29.759> also<00:04:30.039> and<00:04:30.160> on<00:04:30.320> the<00:04:30.639> public<00:04:31.639> uh 00:04:31.790 --> 00:04:31.800 align:start position:0% private side also and on the public uh 00:04:31.800 --> 00:04:34.749 align:start position:0% private side also and on the public uh so<00:04:32.000> we<00:04:32.199> did<00:04:32.759> uh<00:04:32.880> a<00:04:33.000> couple<00:04:33.240> of<00:04:33.400> deployments<00:04:34.199> in 00:04:34.749 --> 00:04:34.759 align:start position:0% so we did uh a couple of deployments in 00:04:34.759 --> 00:04:37.830 align:start position:0% so we did uh a couple of deployments in uh<00:04:34.960> Costa<00:04:35.360> Rica<00:04:36.240> uh<00:04:36.400> we<00:04:36.759> had<00:04:37.039> partnership<00:04:37.560> with 00:04:37.830 --> 00:04:37.840 align:start position:0% uh Costa Rica uh we had partnership with 00:04:37.840 --> 00:04:40.629 align:start position:0% uh Costa Rica uh we had partnership with idb<00:04:38.440> inter<00:04:38.759> American<00:04:39.160> Development<00:04:39.680> Bank<00:04:40.520> uh 00:04:40.629 --> 00:04:40.639 align:start position:0% idb inter American Development Bank uh 00:04:40.639 --> 00:04:42.830 align:start position:0% idb inter American Development Bank uh who<00:04:40.800> actually<00:04:41.039> opened<00:04:41.360> doors<00:04:41.639> for<00:04:41.800> us<00:04:42.000> to<00:04:42.280> like 00:04:42.830 --> 00:04:42.840 align:start position:0% who actually opened doors for us to like 00:04:42.840 --> 00:04:44.469 align:start position:0% who actually opened doors for us to like uh<00:04:42.960> help<00:04:43.240> track<00:04:43.560> products<00:04:44.000> within<00:04:44.280> that 00:04:44.469 --> 00:04:44.479 align:start position:0% uh help track products within that 00:04:44.479 --> 00:04:47.230 align:start position:0% uh help track products within that market<00:04:45.360> so<00:04:45.759> the<00:04:45.880> major<00:04:46.199> issue<00:04:46.600> at<00:04:46.759> hand<00:04:47.039> was 00:04:47.230 --> 00:04:47.240 align:start position:0% market so the major issue at hand was 00:04:47.240 --> 00:04:48.870 align:start position:0% market so the major issue at hand was that<00:04:47.560> once<00:04:47.759> the<00:04:47.880> manufacturers<00:04:48.479> send<00:04:48.720> the 00:04:48.870 --> 00:04:48.880 align:start position:0% that once the manufacturers send the 00:04:48.880 --> 00:04:50.550 align:start position:0% that once the manufacturers send the product<00:04:49.199> they<00:04:49.320> only<00:04:49.520> have<00:04:49.720> visibility<00:04:50.199> till 00:04:50.550 --> 00:04:50.560 align:start position:0% product they only have visibility till 00:04:50.560 --> 00:04:53.029 align:start position:0% product they only have visibility till Panama<00:04:51.560> and<00:04:52.000> after<00:04:52.320> which<00:04:52.600> there's<00:04:52.840> like 00:04:53.029 --> 00:04:53.039 align:start position:0% Panama and after which there's like 00:04:53.039 --> 00:04:54.870 align:start position:0% Panama and after which there's like complete<00:04:53.400> lack<00:04:53.720> of<00:04:54.199> understanding<00:04:54.440> if<00:04:54.600> the 00:04:54.870 --> 00:04:54.880 align:start position:0% complete lack of understanding if the 00:04:54.880 --> 00:04:56.909 align:start position:0% complete lack of understanding if the how<00:04:55.000> is<00:04:55.080> the<00:04:55.240> product<00:04:55.520> moving<00:04:55.800> in<00:04:55.919> the<00:04:56.080> country 00:04:56.909 --> 00:04:56.919 align:start position:0% how is the product moving in the country 00:04:56.919 --> 00:04:59.670 align:start position:0% how is the product moving in the country so<00:04:57.520> we<00:04:57.800> we<00:04:57.919> did<00:04:58.160> make<00:04:58.639> uh<00:04:58.759> a<00:04:58.880> deployment<00:04:59.400> there 00:04:59.670 --> 00:04:59.680 align:start position:0% so we we did make uh a deployment there 00:04:59.680 --> 00:05:01.270 align:start position:0% so we we did make uh a deployment there and<00:04:59.800> even<00:05:00.000> during<00:05:00.320> covid<00:05:00.639> we<00:05:00.759> were<00:05:00.919> able<00:05:01.120> to 00:05:01.270 --> 00:05:01.280 align:start position:0% and even during covid we were able to 00:05:01.280 --> 00:05:03.469 align:start position:0% and even during covid we were able to like<00:05:01.440> track<00:05:01.720> a<00:05:01.840> million<00:05:02.160> doses<00:05:02.520> of<00:05:02.800> covid-19 00:05:03.469 --> 00:05:03.479 align:start position:0% like track a million doses of covid-19 00:05:03.479 --> 00:05:05.790 align:start position:0% like track a million doses of covid-19 vaccines<00:05:04.280> and<00:05:04.440> also<00:05:04.680> the<00:05:04.800> end<00:05:05.120> beneficiaries 00:05:05.790 --> 00:05:05.800 align:start position:0% vaccines and also the end beneficiaries 00:05:05.800 --> 00:05:09.390 align:start position:0% vaccines and also the end beneficiaries who<00:05:05.960> were<00:05:06.440> receiving<00:05:06.720> it<00:05:07.639> um<00:05:08.240> and<00:05:08.639> we<00:05:08.880> we<00:05:09.039> did 00:05:09.390 --> 00:05:09.400 align:start position:0% who were receiving it um and we we did 00:05:09.400 --> 00:05:12.350 align:start position:0% who were receiving it um and we we did have<00:05:10.120> a<00:05:10.639> another<00:05:11.039> deployment<00:05:11.720> another<00:05:12.039> major 00:05:12.350 --> 00:05:12.360 align:start position:0% have a another deployment another major 00:05:12.360 --> 00:05:16.150 align:start position:0% have a another deployment another major deployment<00:05:13.000> with<00:05:13.280> the<00:05:13.840> UNICEF<00:05:14.840> uh<00:05:15.240> so<00:05:15.880> the<00:05:16.000> way 00:05:16.150 --> 00:05:16.160 align:start position:0% deployment with the UNICEF uh so the way 00:05:16.160 --> 00:05:18.070 align:start position:0% deployment with the UNICEF uh so the way it<00:05:16.280> works<00:05:16.520> is<00:05:16.680> that<00:05:16.840> we<00:05:17.000> have<00:05:17.120> an<00:05:17.280> LTA<00:05:17.919> with 00:05:18.070 --> 00:05:18.080 align:start position:0% it works is that we have an LTA with 00:05:18.080 --> 00:05:20.990 align:start position:0% it works is that we have an LTA with UNICEF<00:05:18.680> so<00:05:19.160> that<00:05:19.759> basically<00:05:20.240> gives<00:05:20.440> us<00:05:20.680> that 00:05:20.990 --> 00:05:21.000 align:start position:0% UNICEF so that basically gives us that 00:05:21.000 --> 00:05:23.430 align:start position:0% UNICEF so that basically gives us that opportunity<00:05:21.639> to<00:05:21.880> like<00:05:22.560> uh<00:05:22.680> go<00:05:22.840> to<00:05:23.000> multiple 00:05:23.430 --> 00:05:23.440 align:start position:0% opportunity to like uh go to multiple 00:05:23.440 --> 00:05:26.550 align:start position:0% opportunity to like uh go to multiple countries<00:05:24.319> we<00:05:24.639> recently<00:05:25.160> just<00:05:25.360> deployed<00:05:25.880> in 00:05:26.550 --> 00:05:26.560 align:start position:0% countries we recently just deployed in 00:05:26.560 --> 00:05:29.909 align:start position:0% countries we recently just deployed in Bangladesh<00:05:27.560> uh<00:05:27.680> so<00:05:27.960> we<00:05:28.280> are<00:05:28.600> ensuring<00:05:29.280> that<00:05:29.440> we 00:05:29.909 --> 00:05:29.919 align:start position:0% Bangladesh uh so we are ensuring that we 00:05:29.919 --> 00:05:31.510 align:start position:0% Bangladesh uh so we are ensuring that we are<00:05:30.080> tracking<00:05:30.479> the<00:05:30.720> product<00:05:31.160> from<00:05:31.360> the 00:05:31.510 --> 00:05:31.520 align:start position:0% are tracking the product from the 00:05:31.520 --> 00:05:34.150 align:start position:0% are tracking the product from the central<00:05:31.919> procurement<00:05:32.440> level<00:05:32.880> at<00:05:33.039> the<00:05:33.160> country 00:05:34.150 --> 00:05:34.160 align:start position:0% central procurement level at the country 00:05:34.160 --> 00:05:35.950 align:start position:0% central procurement level at the country and<00:05:34.600> uh<00:05:34.720> there<00:05:34.800> are<00:05:34.960> like<00:05:35.199> multiple<00:05:35.680> various 00:05:35.950 --> 00:05:35.960 align:start position:0% and uh there are like multiple various 00:05:35.960 --> 00:05:37.870 align:start position:0% and uh there are like multiple various stakeholders<00:05:36.560> within<00:05:36.759> the<00:05:36.919> entire<00:05:37.280> ecosystem 00:05:37.870 --> 00:05:37.880 align:start position:0% stakeholders within the entire ecosystem 00:05:37.880 --> 00:05:39.990 align:start position:0% stakeholders within the entire ecosystem who<00:05:38.000> are<00:05:38.160> also<00:05:38.479> going<00:05:38.639> to<00:05:38.800> be<00:05:38.919> a<00:05:39.039> part<00:05:39.240> of<00:05:39.400> it 00:05:39.990 --> 00:05:40.000 align:start position:0% who are also going to be a part of it 00:05:40.000 --> 00:05:41.830 align:start position:0% who are also going to be a part of it the<00:05:40.120> major<00:05:40.440> challenge<00:05:40.840> I<00:05:40.960> think<00:05:41.120> we<00:05:41.280> did<00:05:41.600> have 00:05:41.830 --> 00:05:41.840 align:start position:0% the major challenge I think we did have 00:05:41.840 --> 00:05:43.990 align:start position:0% the major challenge I think we did have around<00:05:42.360> was<00:05:43.080> uh<00:05:43.199> you<00:05:43.319> know<00:05:43.639> there<00:05:43.759> were 00:05:43.990 --> 00:05:44.000 align:start position:0% around was uh you know there were 00:05:44.000 --> 00:05:46.309 align:start position:0% around was uh you know there were barriers<00:05:44.440> in<00:05:44.600> terms<00:05:44.919> of<00:05:45.360> uh<00:05:45.720> digital 00:05:46.309 --> 00:05:46.319 align:start position:0% barriers in terms of uh digital 00:05:46.319 --> 00:05:48.469 align:start position:0% barriers in terms of uh digital infrastructure<00:05:47.319> so<00:05:47.560> they<00:05:47.680> did<00:05:47.840> not<00:05:48.120> have<00:05:48.319> like 00:05:48.469 --> 00:05:48.479 align:start position:0% infrastructure so they did not have like 00:05:48.479 --> 00:05:50.990 align:start position:0% infrastructure so they did not have like enough<00:05:48.800> capabilities<00:05:49.520> that<00:05:49.680> could<00:05:50.000> support 00:05:50.990 --> 00:05:51.000 align:start position:0% enough capabilities that could support 00:05:51.000 --> 00:05:52.950 align:start position:0% enough capabilities that could support uh<00:05:51.120> and<00:05:51.240> even<00:05:51.479> in<00:05:51.639> terms<00:05:51.880> of<00:05:52.080> remote<00:05:52.400> locations 00:05:52.950 --> 00:05:52.960 align:start position:0% uh and even in terms of remote locations 00:05:52.960 --> 00:05:54.830 align:start position:0% uh and even in terms of remote locations right<00:05:53.080> so<00:05:53.199> there<00:05:53.319> were<00:05:53.479> like<00:05:53.880> very<00:05:54.199> very 00:05:54.830 --> 00:05:54.840 align:start position:0% right so there were like very very 00:05:54.840 --> 00:05:56.590 align:start position:0% right so there were like very very remote<00:05:55.199> locations<00:05:55.639> where<00:05:55.759> you<00:05:55.840> do<00:05:56.000> not<00:05:56.280> have 00:05:56.590 --> 00:05:56.600 align:start position:0% remote locations where you do not have 00:05:56.600 --> 00:05:58.230 align:start position:0% remote locations where you do not have like<00:05:56.800> bandwidth<00:05:57.360> capacity<00:05:57.880> internet 00:05:58.230 --> 00:05:58.240 align:start position:0% like bandwidth capacity internet 00:05:58.240 --> 00:06:01.150 align:start position:0% like bandwidth capacity internet bandwidth<00:05:58.720> capacity<00:05:59.240> so<00:05:59.880> we<00:06:00.080> did<00:06:00.440> employ<00:06:01.000> a 00:06:01.150 --> 00:06:01.160 align:start position:0% bandwidth capacity so we did employ a 00:06:01.160 --> 00:06:02.870 align:start position:0% bandwidth capacity so we did employ a good<00:06:01.400> good<00:06:01.600> workaround<00:06:02.120> plan<00:06:02.319> for<00:06:02.520> that<00:06:02.680> to 00:06:02.870 --> 00:06:02.880 align:start position:0% good good workaround plan for that to 00:06:02.880 --> 00:06:04.710 align:start position:0% good good workaround plan for that to have<00:06:03.199> an<00:06:03.360> offline<00:06:03.759> mode<00:06:04.160> which<00:06:04.360> basically 00:06:04.710 --> 00:06:04.720 align:start position:0% have an offline mode which basically 00:06:04.720 --> 00:06:06.950 align:start position:0% have an offline mode which basically helped<00:06:05.080> people<00:06:05.440> record<00:06:05.880> information<00:06:06.440> in<00:06:06.599> real 00:06:06.950 --> 00:06:06.960 align:start position:0% helped people record information in real 00:06:06.960 --> 00:06:08.430 align:start position:0% helped people record information in real time<00:06:07.400> so<00:06:07.639> once<00:06:07.840> they<00:06:07.960> have<00:06:08.120> the<00:06:08.199> data 00:06:08.430 --> 00:06:08.440 align:start position:0% time so once they have the data 00:06:08.440 --> 00:06:10.070 align:start position:0% time so once they have the data connectivity<00:06:09.080> back<00:06:09.319> they<00:06:09.440> can<00:06:09.599> like<00:06:09.759> you<00:06:09.880> know 00:06:10.070 --> 00:06:10.080 align:start position:0% connectivity back they can like you know 00:06:10.080 --> 00:06:12.189 align:start position:0% connectivity back they can like you know they<00:06:10.199> don't<00:06:10.400> really<00:06:10.599> have<00:06:10.720> to<00:06:10.880> enter<00:06:11.120> it<00:06:11.319> again 00:06:12.189 --> 00:06:12.199 align:start position:0% they don't really have to enter it again 00:06:12.199 --> 00:06:14.589 align:start position:0% they don't really have to enter it again but<00:06:12.360> there<00:06:12.479> were<00:06:12.680> again<00:06:13.160> issues<00:06:13.680> with<00:06:13.960> having 00:06:14.589 --> 00:06:14.599 align:start position:0% but there were again issues with having 00:06:14.599 --> 00:06:18.270 align:start position:0% but there were again issues with having uh<00:06:15.039> uh<00:06:15.240> localization<00:06:16.240> in<00:06:16.479> place<00:06:17.319> uh<00:06:17.400> so<00:06:17.599> we<00:06:17.759> did 00:06:18.270 --> 00:06:18.280 align:start position:0% uh uh localization in place uh so we did 00:06:18.280 --> 00:06:19.870 align:start position:0% uh uh localization in place uh so we did understand<00:06:18.440> that<00:06:18.560> it<00:06:18.720> was<00:06:18.919> going<00:06:19.120> to<00:06:19.319> come<00:06:19.479> up 00:06:19.870 --> 00:06:19.880 align:start position:0% understand that it was going to come up 00:06:19.880 --> 00:06:21.790 align:start position:0% understand that it was going to come up uh<00:06:20.039> eventually<00:06:20.680> like<00:06:20.880> as<00:06:21.000> in<00:06:21.199> how<00:06:21.360> we<00:06:21.520> like<00:06:21.680> you 00:06:21.790 --> 00:06:21.800 align:start position:0% uh eventually like as in how we like you 00:06:21.800 --> 00:06:24.710 align:start position:0% uh eventually like as in how we like you know<00:06:22.520> uh<00:06:22.759> naturally<00:06:23.319> grow<00:06:24.000> uh<00:06:24.080> to<00:06:24.240> multiple 00:06:24.710 --> 00:06:24.720 align:start position:0% know uh naturally grow uh to multiple 00:06:24.720 --> 00:06:27.670 align:start position:0% know uh naturally grow uh to multiple countries<00:06:25.400> we<00:06:25.639> would<00:06:26.599> uh<00:06:27.080> have<00:06:27.240> to<00:06:27.440> like<00:06:27.599> you 00:06:27.670 --> 00:06:27.680 align:start position:0% countries we would uh have to like you 00:06:27.680 --> 00:06:29.589 align:start position:0% countries we would uh have to like you know<00:06:27.960> have<00:06:28.400> uh<00:06:28.560> the<00:06:28.919> application<00:06:29.319> of 00:06:29.589 --> 00:06:29.599 align:start position:0% know have uh the application of 00:06:29.599 --> 00:06:32.390 align:start position:0% know have uh the application of available<00:06:29.880> in<00:06:30.039> multiple<00:06:30.759> languages<00:06:31.759> and<00:06:32.199> we 00:06:32.390 --> 00:06:32.400 align:start position:0% available in multiple languages and we 00:06:32.400 --> 00:06:34.189 align:start position:0% available in multiple languages and we how<00:06:32.599> we<00:06:32.720> have<00:06:32.880> also<00:06:33.120> made<00:06:33.520> the<00:06:33.720> whole<00:06:33.919> thing 00:06:34.189 --> 00:06:34.199 align:start position:0% how we have also made the whole thing 00:06:34.199 --> 00:06:36.629 align:start position:0% how we have also made the whole thing accessible<00:06:34.840> is<00:06:35.080> that<00:06:35.639> it<00:06:35.919> is<00:06:36.199> it's<00:06:36.479> a 00:06:36.629 --> 00:06:36.639 align:start position:0% accessible is that it is it's a 00:06:36.639 --> 00:06:38.710 align:start position:0% accessible is that it is it's a combination<00:06:37.080> of<00:06:37.240> both<00:06:37.560> web<00:06:37.800> and<00:06:38.000> mobile<00:06:38.360> app 00:06:38.710 --> 00:06:38.720 align:start position:0% combination of both web and mobile app 00:06:38.720 --> 00:06:41.550 align:start position:0% combination of both web and mobile app so<00:06:39.000> the<00:06:39.199> way<00:06:39.400> it<00:06:39.720> works<00:06:40.039> is<00:06:40.240> that<00:06:40.720> the<00:06:40.880> user<00:06:41.240> who 00:06:41.550 --> 00:06:41.560 align:start position:0% so the way it works is that the user who 00:06:41.560 --> 00:06:44.150 align:start position:0% so the way it works is that the user who actually<00:06:42.360> who<00:06:42.520> was<00:06:43.160> initially<00:06:43.599> recording<00:06:44.000> it 00:06:44.150 --> 00:06:44.160 align:start position:0% actually who was initially recording it 00:06:44.160 --> 00:06:46.950 align:start position:0% actually who was initially recording it manually<00:06:44.520> on<00:06:44.599> a<00:06:44.720> book<00:06:44.880> and<00:06:45.160> pen<00:06:45.319> and<00:06:45.560> paper<00:06:46.360> he 00:06:46.950 --> 00:06:46.960 align:start position:0% manually on a book and pen and paper he 00:06:46.960 --> 00:06:48.830 align:start position:0% manually on a book and pen and paper he uh<00:06:47.199> has<00:06:47.400> the<00:06:47.599> access<00:06:47.880> on<00:06:48.000> his<00:06:48.160> mobile<00:06:48.479> app<00:06:48.680> so 00:06:48.830 --> 00:06:48.840 align:start position:0% uh has the access on his mobile app so 00:06:48.840 --> 00:06:50.550 align:start position:0% uh has the access on his mobile app so all<00:06:48.960> he<00:06:49.199> just<00:06:49.400> has<00:06:49.520> to<00:06:49.680> do<00:06:49.800> is<00:06:50.000> download<00:06:50.400> the 00:06:50.550 --> 00:06:50.560 align:start position:0% all he just has to do is download the 00:06:50.560 --> 00:06:52.749 align:start position:0% all he just has to do is download the app<00:06:51.360> uh<00:06:51.479> you<00:06:51.599> know<00:06:52.080> uh<00:06:52.199> record<00:06:52.560> the 00:06:52.749 --> 00:06:52.759 align:start position:0% app uh you know uh record the 00:06:52.759 --> 00:06:54.550 align:start position:0% app uh you know uh record the transaction<00:06:53.400> so<00:06:53.680> there's<00:06:53.880> like<00:06:54.039> no<00:06:54.280> double 00:06:54.550 --> 00:06:54.560 align:start position:0% transaction so there's like no double 00:06:54.560 --> 00:06:56.350 align:start position:0% transaction so there's like no double work<00:06:54.880> that<00:06:55.000> he<00:06:55.120> would<00:06:55.360> necessarily<00:06:56.000> have<00:06:56.160> to 00:06:56.350 --> 00:06:56.360 align:start position:0% work that he would necessarily have to 00:06:56.360 --> 00:06:59.869 align:start position:0% work that he would necessarily have to do<00:06:57.360> uh<00:06:57.560> so<00:06:58.240> in<00:06:58.440> in<00:06:58.639> that<00:06:58.840> sense<00:06:59.160> I<00:06:59.280> think<00:06:59.759> what 00:06:59.869 --> 00:06:59.879 align:start position:0% do uh so in in that sense I think what 00:06:59.879 --> 00:07:01.749 align:start position:0% do uh so in in that sense I think what we're<00:07:00.080> also<00:07:00.280> trying<00:07:00.479> to<00:07:00.639> do<00:07:00.919> is<00:07:01.240> have<00:07:01.479> some 00:07:01.749 --> 00:07:01.759 align:start position:0% we're also trying to do is have some 00:07:01.759 --> 00:07:04.670 align:start position:0% we're also trying to do is have some concept<00:07:02.160> called<00:07:02.919> incentivization<00:07:03.919> for<00:07:04.520> uh 00:07:04.670 --> 00:07:04.680 align:start position:0% concept called incentivization for uh 00:07:04.680 --> 00:07:07.110 align:start position:0% concept called incentivization for uh making<00:07:04.960> it<00:07:05.120> easier<00:07:05.440> for<00:07:05.639> people<00:07:05.919> to<00:07:06.199> adopt<00:07:06.919> the 00:07:07.110 --> 00:07:07.120 align:start position:0% making it easier for people to adopt the 00:07:07.120 --> 00:07:09.670 align:start position:0% making it easier for people to adopt the application<00:07:08.039> so<00:07:08.319> that's<00:07:08.520> where<00:07:08.720> I<00:07:08.840> think<00:07:09.080> with 00:07:09.670 --> 00:07:09.680 align:start position:0% application so that's where I think with 00:07:09.680 --> 00:07:11.909 align:start position:0% application so that's where I think with uh<00:07:09.759> UNF<00:07:10.319> Bangladesh<00:07:10.919> what<00:07:11.080> we<00:07:11.199> have<00:07:11.400> done<00:07:11.720> is 00:07:11.909 --> 00:07:11.919 align:start position:0% uh UNF Bangladesh what we have done is 00:07:11.919 --> 00:07:15.270 align:start position:0% uh UNF Bangladesh what we have done is like<00:07:12.919> the<00:07:13.479> uh<00:07:13.759> you<00:07:13.879> know<00:07:14.120> the<00:07:14.680> demographics 00:07:15.270 --> 00:07:15.280 align:start position:0% like the uh you know the demographics 00:07:15.280 --> 00:07:19.029 align:start position:0% like the uh you know the demographics are<00:07:16.039> vast<00:07:16.560> there<00:07:16.759> so<00:07:16.879> we<00:07:17.080> looking<00:07:17.400> at<00:07:18.039> almost 00:07:19.029 --> 00:07:19.039 align:start position:0% are vast there so we looking at almost 00:07:19.039 --> 00:07:21.110 align:start position:0% are vast there so we looking at almost 100,000<00:07:19.639> million<00:07:20.000> doses<00:07:20.360> of<00:07:20.560> vaccination 00:07:21.110 --> 00:07:21.120 align:start position:0% 100,000 million doses of vaccination 00:07:21.120 --> 00:07:23.309 align:start position:0% 100,000 million doses of vaccination that<00:07:21.280> we're<00:07:21.440> going<00:07:21.599> to<00:07:21.759> record<00:07:22.360> every<00:07:22.639> year 00:07:23.309 --> 00:07:23.319 align:start position:0% that we're going to record every year 00:07:23.319 --> 00:07:25.350 align:start position:0% that we're going to record every year and<00:07:23.560> that's<00:07:23.720> like<00:07:23.840> a<00:07:23.960> huge<00:07:24.240> number<00:07:25.000> and<00:07:25.160> then 00:07:25.350 --> 00:07:25.360 align:start position:0% and that's like a huge number and then 00:07:25.360 --> 00:07:28.270 align:start position:0% and that's like a huge number and then we<00:07:25.599> have<00:07:25.879> like<00:07:26.120> good<00:07:26.440> 150,000<00:07:27.440> plus<00:07:27.680> users<00:07:28.080> and 00:07:28.270 --> 00:07:28.280 align:start position:0% we have like good 150,000 plus users and 00:07:28.280 --> 00:07:30.189 align:start position:0% we have like good 150,000 plus users and wallets<00:07:28.720> that<00:07:28.840> we<00:07:29.000> going<00:07:29.120> to<00:07:29.240> generate<00:07:29.599> rate 00:07:30.189 --> 00:07:30.199 align:start position:0% wallets that we going to generate rate 00:07:30.199 --> 00:07:32.230 align:start position:0% wallets that we going to generate rate just<00:07:30.479> with<00:07:30.759> uh<00:07:30.879> UNICEF<00:07:31.400> Bangladesh<00:07:31.919> the<00:07:32.039> plan 00:07:32.230 --> 00:07:32.240 align:start position:0% just with uh UNICEF Bangladesh the plan 00:07:32.240 --> 00:07:34.350 align:start position:0% just with uh UNICEF Bangladesh the plan is<00:07:32.440> also<00:07:32.639> to<00:07:32.840> like<00:07:33.000> scale<00:07:33.319> up<00:07:33.759> to<00:07:34.039> various 00:07:34.350 --> 00:07:34.360 align:start position:0% is also to like scale up to various 00:07:34.360 --> 00:07:36.029 align:start position:0% is also to like scale up to various other<00:07:34.599> Supply<00:07:34.879> chains<00:07:35.240> so<00:07:35.400> we've<00:07:35.639> had<00:07:35.840> like 00:07:36.029 --> 00:07:36.039 align:start position:0% other Supply chains so we've had like 00:07:36.039 --> 00:07:38.629 align:start position:0% other Supply chains so we've had like par<00:07:36.440> conversations<00:07:36.960> running<00:07:37.319> with<00:07:37.800> uh<00:07:38.199> animal 00:07:38.629 --> 00:07:38.639 align:start position:0% par conversations running with uh animal 00:07:38.639 --> 00:07:41.070 align:start position:0% par conversations running with uh animal vaccines<00:07:39.080> for<00:07:39.280> nutritional<00:07:39.840> vaccines<00:07:40.680> so<00:07:40.960> the 00:07:41.070 --> 00:07:41.080 align:start position:0% vaccines for nutritional vaccines so the 00:07:41.080 --> 00:07:42.950 align:start position:0% vaccines for nutritional vaccines so the way<00:07:41.240> it<00:07:41.360> works<00:07:41.639> is<00:07:41.800> that<00:07:42.000> the<00:07:42.120> whole<00:07:42.479> platform 00:07:42.950 --> 00:07:42.960 align:start position:0% way it works is that the whole platform 00:07:42.960 --> 00:07:45.469 align:start position:0% way it works is that the whole platform has<00:07:43.120> the<00:07:43.319> capability<00:07:43.879> to<00:07:44.039> not<00:07:44.280> just<00:07:44.560> expand 00:07:45.469 --> 00:07:45.479 align:start position:0% has the capability to not just expand 00:07:45.479 --> 00:07:47.670 align:start position:0% has the capability to not just expand within<00:07:45.800> the<00:07:46.280> human<00:07:46.599> vaccine<00:07:47.000> space<00:07:47.360> but<00:07:47.520> it 00:07:47.670 --> 00:07:47.680 align:start position:0% within the human vaccine space but it 00:07:47.680 --> 00:07:49.550 align:start position:0% within the human vaccine space but it has<00:07:47.879> like<00:07:48.000> a<00:07:48.120> similar<00:07:48.440> use<00:07:48.800> case<00:07:49.000> in<00:07:49.199> various 00:07:49.550 --> 00:07:49.560 align:start position:0% has like a similar use case in various 00:07:49.560 --> 00:07:52.469 align:start position:0% has like a similar use case in various other<00:07:50.280> dimensions<00:07:51.280> so<00:07:51.759> it<00:07:52.000> it<00:07:52.159> has<00:07:52.280> a 00:07:52.469 --> 00:07:52.479 align:start position:0% other dimensions so it it has a 00:07:52.479 --> 00:07:54.550 align:start position:0% other dimensions so it it has a potential<00:07:52.879> of<00:07:53.000> creating<00:07:53.360> a<00:07:53.599> good<00:07:54.039> uh<00:07:54.199> you<00:07:54.319> know 00:07:54.550 --> 00:07:54.560 align:start position:0% potential of creating a good uh you know 00:07:54.560 --> 00:07:57.070 align:start position:0% potential of creating a good uh you know 5<00:07:54.800> million<00:07:55.120> wallets<00:07:55.919> uh<00:07:56.240> in<00:07:56.360> the<00:07:56.520> next<00:07:56.759> coming 00:07:57.070 --> 00:07:57.080 align:start position:0% 5 million wallets uh in the next coming 00:07:57.080 --> 00:07:59.670 align:start position:0% 5 million wallets uh in the next coming up<00:07:57.319> year<00:07:57.599> or<00:07:57.800> two<00:07:58.520> uh<00:07:58.639> so<00:07:58.759> we<00:07:58.919> looking<00:07:59.159> at<00:07:59.319> like 00:07:59.670 --> 00:07:59.680 align:start position:0% up year or two uh so we looking at like 00:07:59.680 --> 00:08:02.710 align:start position:0% up year or two uh so we looking at like some<00:07:59.879> potential<00:08:00.759> uh<00:08:00.879> contracts<00:08:01.400> coming<00:08:01.720> up<00:08:02.400> um 00:08:02.710 --> 00:08:02.720 align:start position:0% some potential uh contracts coming up um 00:08:02.720 --> 00:08:03.990 align:start position:0% some potential uh contracts coming up um yeah<00:08:02.840> hopefully 00:08:03.990 --> 00:08:04.000 align:start position:0% yeah hopefully 00:08:04.000 --> 00:08:07.589 align:start position:0% yeah hopefully soon<00:08:05.000> um<00:08:05.199> thanks<00:08:05.440> a<00:08:05.560> lot<00:08:05.800> for<00:08:06.360> um<00:08:07.080> not<00:08:07.319> just 00:08:07.589 --> 00:08:07.599 align:start position:0% soon um thanks a lot for um not just 00:08:07.599 --> 00:08:09.189 align:start position:0% soon um thanks a lot for um not just highlighting<00:08:08.159> the<00:08:08.360> challenges<00:08:08.919> that<00:08:09.039> you 00:08:09.189 --> 00:08:09.199 align:start position:0% highlighting the challenges that you 00:08:09.199 --> 00:08:11.469 align:start position:0% highlighting the challenges that you guys<00:08:09.360> had<00:08:09.520> to<00:08:09.680> overcome<00:08:10.280> in<00:08:10.440> a<00:08:10.639> real<00:08:10.879> world<00:08:11.159> use 00:08:11.469 --> 00:08:11.479 align:start position:0% guys had to overcome in a real world use 00:08:11.479 --> 00:08:13.990 align:start position:0% guys had to overcome in a real world use case<00:08:11.800> but<00:08:11.960> also<00:08:12.199> the<00:08:12.319> kind<00:08:12.479> of<00:08:12.680> impact<00:08:13.560> um<00:08:13.879> that 00:08:13.990 --> 00:08:14.000 align:start position:0% case but also the kind of impact um that 00:08:14.000 --> 00:08:15.950 align:start position:0% case but also the kind of impact um that could<00:08:14.159> be<00:08:14.280> generated<00:08:14.800> so<00:08:15.039> she<00:08:15.199> was<00:08:15.360> talking<00:08:15.599> of 00:08:15.950 --> 00:08:15.960 align:start position:0% could be generated so she was talking of 00:08:15.960 --> 00:08:18.390 align:start position:0% could be generated so she was talking of millions<00:08:16.960> of<00:08:17.400> uh<00:08:17.520> wallets<00:08:18.000> and<00:08:18.120> you<00:08:18.240> know 00:08:18.390 --> 00:08:18.400 align:start position:0% millions of uh wallets and you know 00:08:18.400 --> 00:08:21.230 align:start position:0% millions of uh wallets and you know stuff<00:08:18.680> like<00:08:18.840> the<00:08:19.039> offline<00:08:19.520> mode<00:08:20.520> uh<00:08:20.759> it's<00:08:21.120> it 00:08:21.230 --> 00:08:21.240 align:start position:0% stuff like the offline mode uh it's it 00:08:21.240 --> 00:08:23.469 align:start position:0% stuff like the offline mode uh it's it gets<00:08:21.479> very<00:08:21.680> real<00:08:22.000> out<00:08:22.240> there<00:08:22.479> so<00:08:22.960> that<00:08:23.080> is<00:08:23.199> a 00:08:23.469 --> 00:08:23.479 align:start position:0% gets very real out there so that is a 00:08:23.479 --> 00:08:25.710 align:start position:0% gets very real out there so that is a lifesaver<00:08:24.080> actually<00:08:24.840> um<00:08:25.240> which<00:08:25.560> which 00:08:25.710 --> 00:08:25.720 align:start position:0% lifesaver actually um which which 00:08:25.720 --> 00:08:27.469 align:start position:0% lifesaver actually um which which enables<00:08:26.240> the<00:08:26.360> blockchain<00:08:26.759> to<00:08:26.919> always<00:08:27.159> be<00:08:27.319> in 00:08:27.469 --> 00:08:27.479 align:start position:0% enables the blockchain to always be in 00:08:27.479 --> 00:08:29.670 align:start position:0% enables the blockchain to always be in sync<00:08:28.440> uh<00:08:28.599> and<00:08:28.879> and<00:08:29.039> and<00:08:29.159> then<00:08:29.280> know<00:08:29.520> other 00:08:29.670 --> 00:08:29.680 align:start position:0% sync uh and and and then know other 00:08:29.680 --> 00:08:30.790 align:start position:0% sync uh and and and then know other things<00:08:29.879> that<00:08:29.960> you<00:08:30.159> that<00:08:30.240> you<00:08:30.319> mentioned<00:08:30.639> as 00:08:30.790 --> 00:08:30.800 align:start position:0% things that you that you mentioned as 00:08:30.800 --> 00:08:32.909 align:start position:0% things that you that you mentioned as well<00:08:31.000> that's<00:08:31.240> that's<00:08:31.440> actually<00:08:31.720> fantastic<00:08:32.680> so 00:08:32.909 --> 00:08:32.919 align:start position:0% well that's that's actually fantastic so 00:08:32.919 --> 00:08:36.389 align:start position:0% well that's that's actually fantastic so now<00:08:33.080> I'll<00:08:33.279> switch<00:08:33.680> to<00:08:34.159> uh<00:08:34.360> David<00:08:35.360> So<00:08:36.120> as<00:08:36.240> you 00:08:36.389 --> 00:08:36.399 align:start position:0% now I'll switch to uh David So as you 00:08:36.399 --> 00:08:39.870 align:start position:0% now I'll switch to uh David So as you could<00:08:36.959> see<00:08:37.240> David<00:08:37.640> like<00:08:38.399> these<00:08:38.680> guys<00:08:39.240> U<00:08:39.479> manage 00:08:39.870 --> 00:08:39.880 align:start position:0% could see David like these guys U manage 00:08:39.880 --> 00:08:42.029 align:start position:0% could see David like these guys U manage to<00:08:40.080> not<00:08:40.279> just<00:08:40.479> build<00:08:40.800> the<00:08:41.000> tech<00:08:41.320> but<00:08:41.519> also<00:08:41.839> make 00:08:42.029 --> 00:08:42.039 align:start position:0% to not just build the tech but also make 00:08:42.039 --> 00:08:44.310 align:start position:0% to not just build the tech but also make it<00:08:42.479> accessible<00:08:43.159> and<00:08:43.360> make<00:08:43.519> it<00:08:43.680> work<00:08:44.000> in<00:08:44.120> the 00:08:44.310 --> 00:08:44.320 align:start position:0% it accessible and make it work in the 00:08:44.320 --> 00:08:46.990 align:start position:0% it accessible and make it work in the real<00:08:44.560> world<00:08:44.959> and<00:08:45.519> just<00:08:45.680> in<00:08:45.800> Bangladesh<00:08:46.560> uh 00:08:46.990 --> 00:08:47.000 align:start position:0% real world and just in Bangladesh uh 00:08:47.000 --> 00:08:49.030 align:start position:0% real world and just in Bangladesh uh they're<00:08:47.440> uh<00:08:47.560> they'll<00:08:47.760> soon<00:08:48.000> start<00:08:48.320> tracking 00:08:49.030 --> 00:08:49.040 align:start position:0% they're uh they'll soon start tracking 00:08:49.040 --> 00:08:51.710 align:start position:0% they're uh they'll soon start tracking 100,000<00:08:50.040> um<00:08:50.519> vaccines<00:08:51.000> with<00:08:51.240> thousands<00:08:51.560> of 00:08:51.710 --> 00:08:51.720 align:start position:0% 100,000 um vaccines with thousands of 00:08:51.720 --> 00:08:56.070 align:start position:0% 100,000 um vaccines with thousands of wallets<00:08:52.160> so<00:08:53.040> um<00:08:53.640> for<00:08:54.399> um<00:08:54.839> projects<00:08:55.320> such<00:08:55.519> as 00:08:56.070 --> 00:08:56.080 align:start position:0% wallets so um for um projects such as 00:08:56.080 --> 00:08:59.790 align:start position:0% wallets so um for um projects such as this<00:08:56.640> uh<00:08:56.800> web<00:08:57.000> 3<00:08:57.279> projects<00:08:58.120> um<00:08:58.399> real<00:08:58.720> world<00:08:59.640> uh 00:08:59.790 --> 00:08:59.800 align:start position:0% this uh web 3 projects um real world uh 00:08:59.800 --> 00:09:03.230 align:start position:0% this uh web 3 projects um real world uh open<00:09:00.160> source<00:09:01.160> what<00:09:01.279> would<00:09:01.480> be<00:09:01.720> the<00:09:02.360> um<00:09:02.640> sources 00:09:03.230 --> 00:09:03.240 align:start position:0% open source what would be the um sources 00:09:03.240 --> 00:09:05.069 align:start position:0% open source what would be the um sources of<00:09:03.440> funding<00:09:04.000> that<00:09:04.160> they<00:09:04.279> can<00:09:04.480> tap<00:09:04.720> into<00:09:04.959> could 00:09:05.069 --> 00:09:05.079 align:start position:0% of funding that they can tap into could 00:09:05.079 --> 00:09:06.550 align:start position:0% of funding that they can tap into could you<00:09:05.240> please<00:09:05.720> uh<00:09:05.839> take<00:09:06.000> us<00:09:06.200> through<00:09:06.399> an 00:09:06.550 --> 00:09:06.560 align:start position:0% you please uh take us through an 00:09:06.560 --> 00:09:09.269 align:start position:0% you please uh take us through an overview<00:09:07.000> of<00:09:07.160> that<00:09:08.040> yeah<00:09:08.200> so<00:09:08.399> I<00:09:08.560> think<00:09:09.120> I've 00:09:09.269 --> 00:09:09.279 align:start position:0% overview of that yeah so I think I've 00:09:09.279 --> 00:09:11.310 align:start position:0% overview of that yeah so I think I've always<00:09:09.600> thought<00:09:10.000> that<00:09:10.320> this<00:09:10.760> is<00:09:10.880> a<00:09:11.079> very 00:09:11.310 --> 00:09:11.320 align:start position:0% always thought that this is a very 00:09:11.320 --> 00:09:13.350 align:start position:0% always thought that this is a very interesting<00:09:11.920> use<00:09:12.240> case<00:09:12.480> real<00:09:12.720> world<00:09:13.040> real 00:09:13.350 --> 00:09:13.360 align:start position:0% interesting use case real world real 00:09:13.360 --> 00:09:15.870 align:start position:0% interesting use case real world real time<00:09:13.800> supply<00:09:14.120> chain<00:09:14.399> tracking<00:09:14.920> I<00:09:15.040> remember<00:09:15.560> a 00:09:15.870 --> 00:09:15.880 align:start position:0% time supply chain tracking I remember a 00:09:15.880 --> 00:09:18.430 align:start position:0% time supply chain tracking I remember a project<00:09:16.440> from<00:09:17.360> about<00:09:17.640> six<00:09:17.800> or<00:09:17.959> seven<00:09:18.240> years 00:09:18.430 --> 00:09:18.440 align:start position:0% project from about six or seven years 00:09:18.440 --> 00:09:20.509 align:start position:0% project from about six or seven years ago<00:09:18.640> I<00:09:18.760> believe<00:09:18.959> it<00:09:19.079> was<00:09:19.279> called<00:09:19.519> wobby<00:09:20.360> that 00:09:20.509 --> 00:09:20.519 align:start position:0% ago I believe it was called wobby that 00:09:20.519 --> 00:09:22.630 align:start position:0% ago I believe it was called wobby that was<00:09:20.680> more<00:09:20.959> focused<00:09:21.360> on<00:09:21.640> food<00:09:22.040> and<00:09:22.160> there<00:09:22.320> was 00:09:22.630 --> 00:09:22.640 align:start position:0% was more focused on food and there was 00:09:22.640 --> 00:09:24.990 align:start position:0% was more focused on food and there was like<00:09:22.880> a<00:09:23.000> a<00:09:23.079> lot<00:09:23.200> of<00:09:23.600> kind<00:09:23.720> of<00:09:24.519> uh<00:09:24.720> fake 00:09:24.990 --> 00:09:25.000 align:start position:0% like a a lot of kind of uh fake 00:09:25.000 --> 00:09:27.590 align:start position:0% like a a lot of kind of uh fake ingredients<00:09:25.640> issues<00:09:26.120> especially<00:09:26.480> in<00:09:26.640> China 00:09:27.590 --> 00:09:27.600 align:start position:0% ingredients issues especially in China 00:09:27.600 --> 00:09:28.790 align:start position:0% ingredients issues especially in China um<00:09:27.760> I'm<00:09:27.839> not<00:09:27.959> sure<00:09:28.120> what<00:09:28.240> happened<00:09:28.480> to<00:09:28.600> it<00:09:28.720> but 00:09:28.790 --> 00:09:28.800 align:start position:0% um I'm not sure what happened to it but 00:09:28.800 --> 00:09:30.910 align:start position:0% um I'm not sure what happened to it but I<00:09:28.880> thought<00:09:28.959> it<00:09:29.040> was<00:09:29.120> a<00:09:29.360> Brant<00:09:29.640> use<00:09:29.920> case<00:09:30.279> and 00:09:30.910 --> 00:09:30.920 align:start position:0% I thought it was a Brant use case and 00:09:30.920 --> 00:09:32.910 align:start position:0% I thought it was a Brant use case and it's<00:09:31.200> like<00:09:31.399> it's<00:09:31.600> not<00:09:31.880> like<00:09:32.120> sexy<00:09:32.600> cuz<00:09:32.720> it's 00:09:32.910 --> 00:09:32.920 align:start position:0% it's like it's not like sexy cuz it's 00:09:32.920 --> 00:09:34.630 align:start position:0% it's like it's not like sexy cuz it's real<00:09:33.120> world<00:09:33.480> and<00:09:33.600> there's<00:09:33.880> not<00:09:34.079> that<00:09:34.200> much<00:09:34.399> to 00:09:34.630 --> 00:09:34.640 align:start position:0% real world and there's not that much to 00:09:34.640 --> 00:09:37.190 align:start position:0% real world and there's not that much to speculate<00:09:35.160> on<00:09:35.920> um<00:09:36.079> but<00:09:36.200> it's<00:09:36.480> actually<00:09:36.920> like 00:09:37.190 --> 00:09:37.200 align:start position:0% speculate on um but it's actually like 00:09:37.200 --> 00:09:39.710 align:start position:0% speculate on um but it's actually like really<00:09:37.680> really<00:09:38.240> useful<00:09:38.680> for<00:09:39.079> millions<00:09:39.480> of 00:09:39.710 --> 00:09:39.720 align:start position:0% really really useful for millions of 00:09:39.720 --> 00:09:43.630 align:start position:0% really really useful for millions of people<00:09:40.720> um<00:09:41.079> I<00:09:41.200> think<00:09:41.560> in<00:09:41.800> in<00:09:41.920> terms<00:09:42.160> of<00:09:42.640> funding 00:09:43.630 --> 00:09:43.640 align:start position:0% people um I think in in terms of funding 00:09:43.640 --> 00:09:46.750 align:start position:0% people um I think in in terms of funding uh<00:09:43.800> in<00:09:44.200> crypto<00:09:44.640> we<00:09:44.839> have<00:09:45.120> this<00:09:45.920> uh<00:09:46.440> kind<00:09:46.560> of 00:09:46.750 --> 00:09:46.760 align:start position:0% uh in crypto we have this uh kind of 00:09:46.760 --> 00:09:48.990 align:start position:0% uh in crypto we have this uh kind of phrase<00:09:47.120> of<00:09:47.360> public<00:09:47.680> goods<00:09:47.920> funding<00:09:48.360> but<00:09:48.519> often 00:09:48.990 --> 00:09:49.000 align:start position:0% phrase of public goods funding but often 00:09:49.000 --> 00:09:51.630 align:start position:0% phrase of public goods funding but often what<00:09:49.360> people<00:09:49.640> mean<00:09:50.480> are<00:09:50.720> funding<00:09:51.120> Network 00:09:51.630 --> 00:09:51.640 align:start position:0% what people mean are funding Network 00:09:51.640 --> 00:09:54.269 align:start position:0% what people mean are funding Network Goods<00:09:52.480> which<00:09:52.640> are<00:09:53.200> uh<00:09:53.440> kind<00:09:53.560> of<00:09:53.800> digital 00:09:54.269 --> 00:09:54.279 align:start position:0% Goods which are uh kind of digital 00:09:54.279 --> 00:09:56.110 align:start position:0% Goods which are uh kind of digital public<00:09:54.560> goods<00:09:54.839> open<00:09:55.160> source<00:09:55.560> that<00:09:55.839> is 00:09:56.110 --> 00:09:56.120 align:start position:0% public goods open source that is 00:09:56.120 --> 00:09:58.509 align:start position:0% public goods open source that is specifically<00:09:56.680> applicable<00:09:57.200> to<00:09:58.160> uh<00:09:58.360> the 00:09:58.509 --> 00:09:58.519 align:start position:0% specifically applicable to uh the 00:09:58.519 --> 00:10:00.870 align:start position:0% specifically applicable to uh the optimism<00:09:59.399> super<00:09:59.600> chain<00:09:59.839> ecosystem<00:10:00.519> or<00:10:00.720> the 00:10:00.870 --> 00:10:00.880 align:start position:0% optimism super chain ecosystem or the 00:10:00.880 --> 00:10:03.230 align:start position:0% optimism super chain ecosystem or the polygon<00:10:01.360> ecosystem<00:10:02.079> or<00:10:02.600> the<00:10:02.720> ethereum 00:10:03.230 --> 00:10:03.240 align:start position:0% polygon ecosystem or the ethereum 00:10:03.240 --> 00:10:06.509 align:start position:0% polygon ecosystem or the ethereum ecosystem<00:10:03.959> or<00:10:04.160> the<00:10:04.279> Stellar<00:10:05.040> ecosystem<00:10:06.040> um 00:10:06.509 --> 00:10:06.519 align:start position:0% ecosystem or the Stellar ecosystem um 00:10:06.519 --> 00:10:08.750 align:start position:0% ecosystem or the Stellar ecosystem um which<00:10:06.640> is<00:10:06.880> a<00:10:06.959> little<00:10:07.160> different<00:10:07.720> than<00:10:08.320> uh<00:10:08.480> when 00:10:08.750 --> 00:10:08.760 align:start position:0% which is a little different than uh when 00:10:08.760 --> 00:10:11.750 align:start position:0% which is a little different than uh when kind<00:10:08.880> of<00:10:09.600> government<00:10:10.160> public<00:10:10.519> sector<00:10:11.279> UNICEF 00:10:11.750 --> 00:10:11.760 align:start position:0% kind of government public sector UNICEF 00:10:11.760 --> 00:10:13.710 align:start position:0% kind of government public sector UNICEF folks<00:10:12.120> talk<00:10:12.360> about<00:10:12.920> public<00:10:13.200> goods<00:10:13.480> which<00:10:13.560> are 00:10:13.710 --> 00:10:13.720 align:start position:0% folks talk about public goods which are 00:10:13.720 --> 00:10:15.870 align:start position:0% folks talk about public goods which are kind<00:10:13.880> of<00:10:14.079> like<00:10:14.640> the<00:10:14.839> the<00:10:15.000> public<00:10:15.399> that<00:10:15.560> is<00:10:15.760> you 00:10:15.870 --> 00:10:15.880 align:start position:0% kind of like the the public that is you 00:10:15.880 --> 00:10:18.590 align:start position:0% kind of like the the public that is you know<00:10:16.120> the<00:10:16.240> human<00:10:16.560> species<00:10:17.160> or<00:10:18.000> um<00:10:18.120> the<00:10:18.320> public 00:10:18.590 --> 00:10:18.600 align:start position:0% know the human species or um the public 00:10:18.600 --> 00:10:21.829 align:start position:0% know the human species or um the public of<00:10:18.880> Bangladesh<00:10:19.560> so<00:10:20.480> um<00:10:20.920> in<00:10:21.120> that<00:10:21.320> light<00:10:21.640> there 00:10:21.829 --> 00:10:21.839 align:start position:0% of Bangladesh so um in that light there 00:10:21.839 --> 00:10:25.590 align:start position:0% of Bangladesh so um in that light there are<00:10:22.560> um<00:10:22.720> a<00:10:22.880> number<00:10:23.120> of<00:10:24.040> public<00:10:24.360> goods<00:10:24.600> funding 00:10:25.590 --> 00:10:25.600 align:start position:0% are um a number of public goods funding 00:10:25.600 --> 00:10:28.470 align:start position:0% are um a number of public goods funding uh<00:10:25.800> systems<00:10:26.279> being<00:10:26.560> developed<00:10:27.240> and<00:10:28.079> um<00:10:28.240> some 00:10:28.470 --> 00:10:28.480 align:start position:0% uh systems being developed and um some 00:10:28.480 --> 00:10:30.269 align:start position:0% uh systems being developed and um some really<00:10:28.640> interesting<00:10:29.000> work<00:10:29.519> being<00:10:29.760> done<00:10:30.079> in 00:10:30.269 --> 00:10:30.279 align:start position:0% really interesting work being done in 00:10:30.279 --> 00:10:32.470 align:start position:0% really interesting work being done in the<00:10:30.560> optimism<00:10:31.079> ecosystem<00:10:31.720> with<00:10:31.880> retroactive 00:10:32.470 --> 00:10:32.480 align:start position:0% the optimism ecosystem with retroactive 00:10:32.480 --> 00:10:35.629 align:start position:0% the optimism ecosystem with retroactive public<00:10:32.760> goods<00:10:33.160> funding<00:10:34.160> um<00:10:34.760> there's<00:10:35.000> a<00:10:35.480> kind 00:10:35.629 --> 00:10:35.639 align:start position:0% public goods funding um there's a kind 00:10:35.639 --> 00:10:38.629 align:start position:0% public goods funding um there's a kind of<00:10:36.600> old<00:10:36.920> protocol<00:10:37.720> Gollum<00:10:38.079> Foundation<00:10:38.519> which 00:10:38.629 --> 00:10:38.639 align:start position:0% of old protocol Gollum Foundation which 00:10:38.639 --> 00:10:41.110 align:start position:0% of old protocol Gollum Foundation which deployed<00:10:39.040> something<00:10:39.320> called<00:10:39.720> octant<00:10:40.720> um 00:10:41.110 --> 00:10:41.120 align:start position:0% deployed something called octant um 00:10:41.120 --> 00:10:43.590 align:start position:0% deployed something called octant um which<00:10:41.519> uh<00:10:41.600> uses<00:10:41.959> quadratic<00:10:42.440> funding<00:10:43.279> uh<00:10:43.440> like 00:10:43.590 --> 00:10:43.600 align:start position:0% which uh uses quadratic funding uh like 00:10:43.600 --> 00:10:46.269 align:start position:0% which uh uses quadratic funding uh like gitcoin<00:10:44.120> to<00:10:44.279> fund<00:10:44.959> a<00:10:45.079> number<00:10:45.399> of<00:10:45.600> again<00:10:45.920> mostly 00:10:46.269 --> 00:10:46.279 align:start position:0% gitcoin to fund a number of again mostly 00:10:46.279 --> 00:10:49.230 align:start position:0% gitcoin to fund a number of again mostly ethereum<00:10:47.279> uh<00:10:47.360> open<00:10:47.680> source<00:10:47.959> public<00:10:48.279> goods 00:10:49.230 --> 00:10:49.240 align:start position:0% ethereum uh open source public goods 00:10:49.240 --> 00:10:52.310 align:start position:0% ethereum uh open source public goods what<00:10:49.560> I<00:10:49.680> think<00:10:50.440> um<00:10:51.079> these<00:10:51.600> ecosystems<00:10:52.160> are 00:10:52.310 --> 00:10:52.320 align:start position:0% what I think um these ecosystems are 00:10:52.320 --> 00:10:54.470 align:start position:0% what I think um these ecosystems are looking<00:10:52.600> for<00:10:52.839> is<00:10:53.000> essentially<00:10:53.920> transaction 00:10:54.470 --> 00:10:54.480 align:start position:0% looking for is essentially transaction 00:10:54.480 --> 00:10:57.190 align:start position:0% looking for is essentially transaction volume<00:10:55.000> on<00:10:55.160> their<00:10:55.360> chain<00:10:55.800> on<00:10:55.920> their<00:10:56.200> Network 00:10:57.190 --> 00:10:57.200 align:start position:0% volume on their chain on their Network 00:10:57.200 --> 00:11:00.389 align:start position:0% volume on their chain on their Network um<00:10:57.519> and<00:10:57.720> so<00:10:58.560> deploying<00:10:59.440> millions<00:10:59.760> of<00:10:59.920> Wallets 00:11:00.389 --> 00:11:00.399 align:start position:0% um and so deploying millions of Wallets 00:11:00.399 --> 00:11:02.190 align:start position:0% um and so deploying millions of Wallets on<00:11:00.519> a<00:11:00.680> decentralized<00:11:01.440> public<00:11:01.760> blockchain 00:11:02.190 --> 00:11:02.200 align:start position:0% on a decentralized public blockchain 00:11:02.200 --> 00:11:05.350 align:start position:0% on a decentralized public blockchain network<00:11:03.040> um<00:11:03.399> like<00:11:04.320> a<00:11:04.440> layer<00:11:04.680> two<00:11:04.880> on<00:11:05.040> top<00:11:05.160> of 00:11:05.350 --> 00:11:05.360 align:start position:0% network um like a layer two on top of 00:11:05.360 --> 00:11:08.509 align:start position:0% network um like a layer two on top of ethereum<00:11:06.360> would<00:11:06.639> be<00:11:07.240> uh<00:11:07.560> I<00:11:07.639> think<00:11:07.800> critical<00:11:08.240> to 00:11:08.509 --> 00:11:08.519 align:start position:0% ethereum would be uh I think critical to 00:11:08.519 --> 00:11:10.750 align:start position:0% ethereum would be uh I think critical to to<00:11:08.680> going<00:11:08.959> after<00:11:09.839> uh<00:11:09.959> public<00:11:10.200> goods<00:11:10.440> funding 00:11:10.750 --> 00:11:10.760 align:start position:0% to going after uh public goods funding 00:11:10.760 --> 00:11:12.069 align:start position:0% to going after uh public goods funding from<00:11:10.959> one<00:11:11.079> of<00:11:11.279> these 00:11:12.069 --> 00:11:12.079 align:start position:0% from one of these 00:11:12.079 --> 00:11:15.030 align:start position:0% from one of these ecosystems<00:11:13.079> um<00:11:13.600> there's<00:11:13.959> always<00:11:14.760> uh<00:11:14.880> the 00:11:15.030 --> 00:11:15.040 align:start position:0% ecosystems um there's always uh the 00:11:15.040 --> 00:11:18.190 align:start position:0% ecosystems um there's always uh the option<00:11:15.760> of<00:11:16.200> launching<00:11:16.600> a<00:11:16.760> token<00:11:17.720> um<00:11:17.839> using 00:11:18.190 --> 00:11:18.200 align:start position:0% option of launching a token um using 00:11:18.200 --> 00:11:21.629 align:start position:0% option of launching a token um using that<00:11:18.360> token<00:11:19.040> as<00:11:19.519> uh<00:11:19.680> an<00:11:19.839> incentive<00:11:20.279> layer<00:11:20.680> for 00:11:21.629 --> 00:11:21.639 align:start position:0% that token as uh an incentive layer for 00:11:21.639 --> 00:11:24.069 align:start position:0% that token as uh an incentive layer for uh<00:11:21.800> real<00:11:22.120> world's<00:11:23.040> uh<00:11:23.279> validators<00:11:23.880> or 00:11:24.069 --> 00:11:24.079 align:start position:0% uh real world's uh validators or 00:11:24.079 --> 00:11:26.949 align:start position:0% uh real world's uh validators or Auditors<00:11:24.920> um<00:11:25.120> that<00:11:25.240> are<00:11:25.720> you<00:11:25.839> know<00:11:26.040> tracking 00:11:26.949 --> 00:11:26.959 align:start position:0% Auditors um that are you know tracking 00:11:26.959 --> 00:11:29.590 align:start position:0% Auditors um that are you know tracking um<00:11:27.800> the<00:11:27.959> vaccines<00:11:28.480> as<00:11:28.680> they<00:11:28.800> go<00:11:28.959> through<00:11:29.440> time 00:11:29.590 --> 00:11:29.600 align:start position:0% um the vaccines as they go through time 00:11:29.600 --> 00:11:32.710 align:start position:0% um the vaccines as they go through time and<00:11:29.839> space<00:11:30.279> using<00:11:30.880> basic<00:11:31.240> devices<00:11:31.880> that<00:11:32.600> um 00:11:32.710 --> 00:11:32.720 align:start position:0% and space using basic devices that um 00:11:32.720 --> 00:11:34.670 align:start position:0% and space using basic devices that um millions<00:11:33.079> of<00:11:33.240> people<00:11:33.600> have<00:11:34.000> around<00:11:34.279> the<00:11:34.399> world 00:11:34.670 --> 00:11:34.680 align:start position:0% millions of people have around the world 00:11:34.680 --> 00:11:38.030 align:start position:0% millions of people have around the world so<00:11:34.959> you<00:11:35.160> enable<00:11:35.959> kind<00:11:36.120> of<00:11:36.680> uh<00:11:37.519> uh<00:11:37.760> large 00:11:38.030 --> 00:11:38.040 align:start position:0% so you enable kind of uh uh large 00:11:38.040 --> 00:11:40.110 align:start position:0% so you enable kind of uh uh large amounts<00:11:38.320> of<00:11:38.480> people<00:11:38.760> that<00:11:38.839> are<00:11:39.000> not<00:11:39.240> technical 00:11:40.110 --> 00:11:40.120 align:start position:0% amounts of people that are not technical 00:11:40.120 --> 00:11:42.470 align:start position:0% amounts of people that are not technical um<00:11:40.200> to<00:11:40.399> directly<00:11:40.839> engage<00:11:41.399> in<00:11:41.839> validating 00:11:42.470 --> 00:11:42.480 align:start position:0% um to directly engage in validating 00:11:42.480 --> 00:11:45.790 align:start position:0% um to directly engage in validating transactions<00:11:43.079> or<00:11:43.839> um<00:11:44.040> kind<00:11:44.200> of<00:11:44.800> interactions 00:11:45.790 --> 00:11:45.800 align:start position:0% transactions or um kind of interactions 00:11:45.800 --> 00:11:47.750 align:start position:0% transactions or um kind of interactions um<00:11:45.959> so<00:11:46.160> these<00:11:46.279> are<00:11:46.560> some<00:11:46.880> ideas<00:11:47.399> and<00:11:47.519> then 00:11:47.750 --> 00:11:47.760 align:start position:0% um so these are some ideas and then 00:11:47.760 --> 00:11:50.870 align:start position:0% um so these are some ideas and then beyond<00:11:48.440> web<00:11:48.680> 3<00:11:49.040> I<00:11:49.120> think<00:11:50.079> um<00:11:50.279> this<00:11:50.399> is<00:11:50.519> a<00:11:50.639> real 00:11:50.870 --> 00:11:50.880 align:start position:0% beyond web 3 I think um this is a real 00:11:50.880 --> 00:11:53.389 align:start position:0% beyond web 3 I think um this is a real use<00:11:51.200> case<00:11:51.440> for<00:11:52.040> public<00:11:52.399> sector<00:11:52.800> for 00:11:53.389 --> 00:11:53.399 align:start position:0% use case for public sector for 00:11:53.399 --> 00:11:55.829 align:start position:0% use case for public sector for governments<00:11:53.920> for<00:11:54.320> large<00:11:54.920> uh<00:11:55.040> nonprofits<00:11:55.680> and 00:11:55.829 --> 00:11:55.839 align:start position:0% governments for large uh nonprofits and 00:11:55.839 --> 00:11:58.269 align:start position:0% governments for large uh nonprofits and philanthropic<00:11:56.720> philanthropic<00:11:57.600> bodies<00:11:58.040> like 00:11:58.269 --> 00:11:58.279 align:start position:0% philanthropic philanthropic bodies like 00:11:58.279 --> 00:11:59.870 align:start position:0% philanthropic philanthropic bodies like Gates<00:11:58.639> Foundation 00:11:59.870 --> 00:11:59.880 align:start position:0% Gates Foundation 00:11:59.880 --> 00:12:03.230 align:start position:0% Gates Foundation um<00:12:00.240> I<00:12:00.360> think<00:12:00.639> that<00:12:00.959> the<00:12:01.600> uh<00:12:02.440> yeah<00:12:02.800> this<00:12:02.920> use 00:12:03.230 --> 00:12:03.240 align:start position:0% um I think that the uh yeah this use 00:12:03.240 --> 00:12:06.230 align:start position:0% um I think that the uh yeah this use case<00:12:03.399> goes<00:12:03.600> Way<00:12:03.760> Beyond<00:12:04.120> web<00:12:04.320> 3<00:12:05.240> um<00:12:05.639> I<00:12:05.760> think 00:12:06.230 --> 00:12:06.240 align:start position:0% case goes Way Beyond web 3 um I think 00:12:06.240 --> 00:12:09.069 align:start position:0% case goes Way Beyond web 3 um I think that<00:12:06.560> web<00:12:06.800> 3<00:12:07.519> uh<00:12:08.079> and<00:12:08.200> blockchain<00:12:08.600> Foundations 00:12:09.069 --> 00:12:09.079 align:start position:0% that web 3 uh and blockchain Foundations 00:12:09.079 --> 00:12:10.790 align:start position:0% that web 3 uh and blockchain Foundations should<00:12:09.320> be<00:12:09.480> very<00:12:09.680> interested<00:12:10.040> in<00:12:10.160> these<00:12:10.480> use 00:12:10.790 --> 00:12:10.800 align:start position:0% should be very interested in these use 00:12:10.800 --> 00:12:14.829 align:start position:0% should be very interested in these use cases<00:12:11.760> um<00:12:12.040> unfortunately<00:12:13.040> it's<00:12:13.639> generally<00:12:14.639> um 00:12:14.829 --> 00:12:14.839 align:start position:0% cases um unfortunately it's generally um 00:12:14.839 --> 00:12:16.910 align:start position:0% cases um unfortunately it's generally um only<00:12:15.240> if<00:12:15.360> you're<00:12:15.639> if<00:12:15.720> you're<00:12:16.000> using<00:12:16.399> some 00:12:16.910 --> 00:12:16.920 align:start position:0% only if you're if you're using some 00:12:16.920 --> 00:12:19.829 align:start position:0% only if you're if you're using some specific<00:12:17.920> um<00:12:18.120> stack<00:12:18.480> or<00:12:18.720> technology<00:12:19.600> uh<00:12:19.720> like 00:12:19.829 --> 00:12:19.839 align:start position:0% specific um stack or technology uh like 00:12:19.839 --> 00:12:22.350 align:start position:0% specific um stack or technology uh like I<00:12:19.959> mentioned<00:12:20.360> of<00:12:20.560> of<00:12:20.680> a<00:12:20.839> specific<00:12:21.160> layer<00:12:21.440> to<00:12:22.240> um 00:12:22.350 --> 00:12:22.360 align:start position:0% I mentioned of of a specific layer to um 00:12:22.360 --> 00:12:24.110 align:start position:0% I mentioned of of a specific layer to um would<00:12:22.560> they<00:12:22.839> generally<00:12:23.320> become<00:12:23.720> interested 00:12:24.110 --> 00:12:24.120 align:start position:0% would they generally become interested 00:12:24.120 --> 00:12:25.590 align:start position:0% would they generally become interested ethereum<00:12:24.519> Foundation<00:12:24.839> is<00:12:24.959> an<00:12:25.120> exception<00:12:25.480> they 00:12:25.590 --> 00:12:25.600 align:start position:0% ethereum Foundation is an exception they 00:12:25.600 --> 00:12:27.750 align:start position:0% ethereum Foundation is an exception they fund<00:12:25.839> a<00:12:25.920> lot<00:12:26.040> of<00:12:26.199> interesting 00:12:27.750 --> 00:12:27.760 align:start position:0% fund a lot of interesting 00:12:27.760 --> 00:12:32.389 align:start position:0% fund a lot of interesting research<00:12:28.760> thanks<00:12:29.000> both<00:12:29.320> that<00:12:30.760> um<00:12:31.760> uh<00:12:31.959> what<00:12:32.160> got 00:12:32.389 --> 00:12:32.399 align:start position:0% research thanks both that um uh what got 00:12:32.399 --> 00:12:34.269 align:start position:0% research thanks both that um uh what got me<00:12:32.639> into<00:12:32.920> blockchains<00:12:33.560> for<00:12:33.720> the<00:12:33.839> very<00:12:34.040> first 00:12:34.269 --> 00:12:34.279 align:start position:0% me into blockchains for the very first 00:12:34.279 --> 00:12:36.350 align:start position:0% me into blockchains for the very first time<00:12:34.480> many<00:12:34.680> years<00:12:34.920> ago<00:12:35.600> was<00:12:35.880> actually<00:12:36.160> the 00:12:36.350 --> 00:12:36.360 align:start position:0% time many years ago was actually the 00:12:36.360 --> 00:12:39.629 align:start position:0% time many years ago was actually the real<00:12:36.720> life<00:12:37.320> potential<00:12:38.320> of<00:12:38.839> uh<00:12:39.199> of<00:12:39.399> this 00:12:39.629 --> 00:12:39.639 align:start position:0% real life potential of uh of this 00:12:39.639 --> 00:12:42.710 align:start position:0% real life potential of uh of this technology<00:12:40.560> uh<00:12:40.680> helping<00:12:41.240> society<00:12:42.240> as<00:12:42.399> in<00:12:42.560> a 00:12:42.710 --> 00:12:42.720 align:start position:0% technology uh helping society as in a 00:12:42.720 --> 00:12:44.430 align:start position:0% technology uh helping society as in a whole<00:12:43.160> and<00:12:43.279> then<00:12:43.480> now<00:12:43.639> we<00:12:43.760> are<00:12:43.959> beginning<00:12:44.320> to 00:12:44.430 --> 00:12:44.440 align:start position:0% whole and then now we are beginning to 00:12:44.440 --> 00:12:46.150 align:start position:0% whole and then now we are beginning to see<00:12:44.680> these<00:12:44.839> real<00:12:45.160> world<00:12:45.360> use<00:12:45.639> cases<00:12:45.920> and<00:12:46.040> you 00:12:46.150 --> 00:12:46.160 align:start position:0% see these real world use cases and you 00:12:46.160 --> 00:12:48.949 align:start position:0% see these real world use cases and you already<00:12:46.560> mentioned<00:12:47.560> um<00:12:48.079> about<00:12:48.399> let's<00:12:48.600> say<00:12:48.839> the 00:12:48.949 --> 00:12:48.959 align:start position:0% already mentioned um about let's say the 00:12:48.959 --> 00:12:50.590 align:start position:0% already mentioned um about let's say the amount<00:12:49.199> of<00:12:49.399> data<00:12:49.720> that<00:12:49.839> has<00:12:49.959> to<00:12:50.040> be<00:12:50.120> stored<00:12:50.440> on 00:12:50.590 --> 00:12:50.600 align:start position:0% amount of data that has to be stored on 00:12:50.600 --> 00:12:53.710 align:start position:0% amount of data that has to be stored on chain<00:12:50.920> for<00:12:51.680> the<00:12:51.839> sources<00:12:52.680> uh<00:12:52.839> of<00:12:53.279> uh<00:12:53.440> public 00:12:53.710 --> 00:12:53.720 align:start position:0% chain for the sources uh of uh public 00:12:53.720 --> 00:12:55.590 align:start position:0% chain for the sources uh of uh public goods<00:12:53.920> funding<00:12:54.240> from<00:12:54.360> the<00:12:54.480> web3<00:12:54.880> ecosystem<00:12:55.440> to 00:12:55.590 --> 00:12:55.600 align:start position:0% goods funding from the web3 ecosystem to 00:12:55.600 --> 00:12:59.710 align:start position:0% goods funding from the web3 ecosystem to be<00:12:55.839> interested<00:12:56.600> uh<00:12:56.720> in<00:12:56.920> them<00:12:57.800> uh<00:12:58.720> um 00:12:59.710 --> 00:12:59.720 align:start position:0% be interested uh in them uh um 00:12:59.720 --> 00:13:02.829 align:start position:0% be interested uh in them uh um what<00:13:00.279> what<00:13:00.480> else<00:13:01.120> should<00:13:01.440> these<00:13:01.720> projects<00:13:02.600> uh 00:13:02.829 --> 00:13:02.839 align:start position:0% what what else should these projects uh 00:13:02.839 --> 00:13:05.189 align:start position:0% what what else should these projects uh keep<00:13:03.040> in<00:13:03.240> mind<00:13:03.720> apart<00:13:04.000> from<00:13:04.519> just<00:13:04.720> using<00:13:05.079> the 00:13:05.189 --> 00:13:05.199 align:start position:0% keep in mind apart from just using the 00:13:05.199 --> 00:13:06.710 align:start position:0% keep in mind apart from just using the blockchain<00:13:05.680> of<00:13:05.800> course<00:13:06.199> uh<00:13:06.399> that<00:13:06.519> you<00:13:06.600> know 00:13:06.710 --> 00:13:06.720 align:start position:0% blockchain of course uh that you know 00:13:06.720 --> 00:13:08.550 align:start position:0% blockchain of course uh that you know goes<00:13:06.920> without<00:13:07.240> saying<00:13:07.839> how<00:13:08.040> else<00:13:08.279> can<00:13:08.440> they 00:13:08.550 --> 00:13:08.560 align:start position:0% goes without saying how else can they 00:13:08.560 --> 00:13:11.389 align:start position:0% goes without saying how else can they make<00:13:08.880> themselves<00:13:09.600> attractive<00:13:10.600> uh<00:13:10.800> to<00:13:11.199> yeah<00:13:11.320> I 00:13:11.389 --> 00:13:11.399 align:start position:0% make themselves attractive uh to yeah I 00:13:11.399 --> 00:13:14.030 align:start position:0% make themselves attractive uh to yeah I think<00:13:11.680> I<00:13:11.800> think<00:13:12.399> um<00:13:12.800> as<00:13:13.040> we<00:13:13.199> spoke<00:13:13.480> about<00:13:13.760> a<00:13:13.880> bit 00:13:14.030 --> 00:13:14.040 align:start position:0% think I think um as we spoke about a bit 00:13:14.040 --> 00:13:17.069 align:start position:0% think I think um as we spoke about a bit earlier<00:13:15.120> um<00:13:16.120> understanding<00:13:16.440> how<00:13:16.680> can<00:13:16.839> we 00:13:17.069 --> 00:13:17.079 align:start position:0% earlier um understanding how can we 00:13:17.079 --> 00:13:19.910 align:start position:0% earlier um understanding how can we engage<00:13:18.079> uh<00:13:18.480> people<00:13:18.880> in<00:13:18.959> the<00:13:19.120> real<00:13:19.320> world 00:13:19.910 --> 00:13:19.920 align:start position:0% engage uh people in the real world 00:13:19.920 --> 00:13:23.710 align:start position:0% engage uh people in the real world Beyond<00:13:20.880> uh<00:13:21.600> uh<00:13:22.000> developers<00:13:23.000> um<00:13:23.199> bringing<00:13:23.519> this 00:13:23.710 --> 00:13:23.720 align:start position:0% Beyond uh uh developers um bringing this 00:13:23.720 --> 00:13:27.110 align:start position:0% Beyond uh uh developers um bringing this technology<00:13:24.320> outside<00:13:24.800> of<00:13:25.040> the<00:13:25.199> kind<00:13:25.360> of<00:13:26.120> um 00:13:27.110 --> 00:13:27.120 align:start position:0% technology outside of the kind of um 00:13:27.120 --> 00:13:29.629 align:start position:0% technology outside of the kind of um internal<00:13:27.760> circles<00:13:28.279> that<00:13:28.440> it<00:13:28.639> I<00:13:28.720> feel<00:13:28.920> like<00:13:29.440> um 00:13:29.629 --> 00:13:29.639 align:start position:0% internal circles that it I feel like um 00:13:29.639 --> 00:13:31.670 align:start position:0% internal circles that it I feel like um Al<00:13:29.839> I<00:13:29.959> also<00:13:30.240> got<00:13:30.440> interested<00:13:30.839> in<00:13:31.160> blockchain 00:13:31.670 --> 00:13:31.680 align:start position:0% Al I also got interested in blockchain 00:13:31.680 --> 00:13:34.710 align:start position:0% Al I also got interested in blockchain about<00:13:32.079> 11<00:13:32.480> 12<00:13:32.800> years<00:13:33.000> ago<00:13:33.279> for<00:13:34.040> um<00:13:34.199> real<00:13:34.440> world 00:13:34.710 --> 00:13:34.720 align:start position:0% about 11 12 years ago for um real world 00:13:34.720 --> 00:13:37.710 align:start position:0% about 11 12 years ago for um real world use<00:13:35.040> cases<00:13:35.320> and<00:13:35.519> impact<00:13:36.000> and<00:13:36.800> um<00:13:37.240> always<00:13:37.560> have 00:13:37.710 --> 00:13:37.720 align:start position:0% use cases and impact and um always have 00:13:37.720 --> 00:13:39.509 align:start position:0% use cases and impact and um always have been<00:13:38.240> really<00:13:38.480> interested<00:13:38.800> in<00:13:39.000> projects<00:13:39.360> and 00:13:39.509 --> 00:13:39.519 align:start position:0% been really interested in projects and 00:13:39.519 --> 00:13:42.030 align:start position:0% been really interested in projects and that's<00:13:39.639> how<00:13:39.760> we<00:13:39.880> got<00:13:40.320> connected<00:13:41.320> uh<00:13:41.519> so<00:13:41.880> yeah 00:13:42.030 --> 00:13:42.040 align:start position:0% that's how we got connected uh so yeah 00:13:42.040 --> 00:13:44.509 align:start position:0% that's how we got connected uh so yeah looking<00:13:42.279> at<00:13:42.519> how<00:13:42.839> can<00:13:43.720> um<00:13:43.880> people<00:13:44.120> around<00:13:44.399> the 00:13:44.509 --> 00:13:44.519 align:start position:0% looking at how can um people around the 00:13:44.519 --> 00:13:46.670 align:start position:0% looking at how can um people around the world<00:13:45.199> uh<00:13:45.320> living<00:13:45.600> in<00:13:45.880> places<00:13:46.199> like<00:13:46.360> Costa 00:13:46.670 --> 00:13:46.680 align:start position:0% world uh living in places like Costa 00:13:46.680 --> 00:13:49.870 align:start position:0% world uh living in places like Costa Rica<00:13:47.320> Bangladesh<00:13:48.320> um<00:13:48.480> use<00:13:48.880> very<00:13:49.160> basic<00:13:49.519> and 00:13:49.870 --> 00:13:49.880 align:start position:0% Rica Bangladesh um use very basic and 00:13:49.880 --> 00:13:53.710 align:start position:0% Rica Bangladesh um use very basic and rudimentary<00:13:50.880> devices<00:13:51.519> to<00:13:52.040> confirm<00:13:53.040> uh<00:13:53.440> things 00:13:53.710 --> 00:13:53.720 align:start position:0% rudimentary devices to confirm uh things 00:13:53.720 --> 00:13:55.350 align:start position:0% rudimentary devices to confirm uh things that<00:13:53.839> are<00:13:54.000> happening<00:13:54.320> in<00:13:54.399> the<00:13:54.560> real<00:13:54.759> world<00:13:55.160> and 00:13:55.350 --> 00:13:55.360 align:start position:0% that are happening in the real world and 00:13:55.360 --> 00:13:58.350 align:start position:0% that are happening in the real world and reward<00:13:55.839> them<00:13:56.440> directly<00:13:57.440> um<00:13:57.720> on<00:13:57.839> a<00:13:58.040> public 00:13:58.350 --> 00:13:58.360 align:start position:0% reward them directly um on a public 00:13:58.360 --> 00:14:00.990 align:start position:0% reward them directly um on a public blockchain<00:13:59.320> uh<00:13:59.440> for<00:13:59.720> those 00:14:00.990 --> 00:14:01.000 align:start position:0% blockchain uh for those 00:14:01.000 --> 00:14:06.230 align:start position:0% blockchain uh for those actions<00:14:02.000> okay<00:14:03.279> uh<00:14:04.279> so<00:14:04.639> impact<00:14:05.600> can<00:14:05.880> of<00:14:06.040> course 00:14:06.230 --> 00:14:06.240 align:start position:0% actions okay uh so impact can of course 00:14:06.240 --> 00:14:08.829 align:start position:0% actions okay uh so impact can of course be<00:14:06.440> generated<00:14:07.079> by<00:14:07.199> web<00:14:07.399> 3<00:14:07.680> projects<00:14:08.440> they<00:14:08.600> may 00:14:08.829 --> 00:14:08.839 align:start position:0% be generated by web 3 projects they may 00:14:08.839 --> 00:14:11.670 align:start position:0% be generated by web 3 projects they may also<00:14:09.160> be<00:14:09.360> generated<00:14:09.959> by<00:14:10.160> web<00:14:10.399> 2<00:14:10.680> projects<00:14:11.519> um 00:14:11.670 --> 00:14:11.680 align:start position:0% also be generated by web 2 projects um 00:14:11.680 --> 00:14:13.670 align:start position:0% also be generated by web 2 projects um who<00:14:11.800> are<00:14:11.920> doing<00:14:12.199> fantastic<00:14:12.680> work<00:14:13.399> the<00:14:13.519> thing 00:14:13.670 --> 00:14:13.680 align:start position:0% who are doing fantastic work the thing 00:14:13.680 --> 00:14:15.710 align:start position:0% who are doing fantastic work the thing is<00:14:13.880> these<00:14:14.040> web<00:14:14.240> two<00:14:14.440> projects<00:14:14.720> are<00:14:14.880> typically 00:14:15.710 --> 00:14:15.720 align:start position:0% is these web two projects are typically 00:14:15.720 --> 00:14:19.269 align:start position:0% is these web two projects are typically not<00:14:15.959> aware<00:14:16.680> of<00:14:17.040> how<00:14:17.240> to<00:14:17.759> become<00:14:18.160> web<00:14:18.519> 3<00:14:18.920> how<00:14:19.040> to 00:14:19.269 --> 00:14:19.279 align:start position:0% not aware of how to become web 3 how to 00:14:19.279 --> 00:14:21.430 align:start position:0% not aware of how to become web 3 how to get<00:14:19.440> the<00:14:19.639> data<00:14:19.920> on<00:14:20.120> chain<00:14:20.399> and<00:14:20.560> all<00:14:20.720> that<00:14:21.240> so 00:14:21.430 --> 00:14:21.440 align:start position:0% get the data on chain and all that so 00:14:21.440 --> 00:14:23.629 align:start position:0% get the data on chain and all that so how<00:14:21.600> can<00:14:21.720> the<00:14:21.839> web3<00:14:22.279> ecosystem<00:14:23.199> the<00:14:23.320> funding 00:14:23.629 --> 00:14:23.639 align:start position:0% how can the web3 ecosystem the funding 00:14:23.639 --> 00:14:25.829 align:start position:0% how can the web3 ecosystem the funding ecosystem<00:14:24.360> be<00:14:24.560> more<00:14:24.800> inclusive<00:14:25.519> and<00:14:25.639> you<00:14:25.720> know 00:14:25.829 --> 00:14:25.839 align:start position:0% ecosystem be more inclusive and you know 00:14:25.839 --> 00:14:27.790 align:start position:0% ecosystem be more inclusive and you know including<00:14:26.320> them<00:14:26.560> like<00:14:27.079> do<00:14:27.240> they<00:14:27.440> have<00:14:27.600> to 00:14:27.790 --> 00:14:27.800 align:start position:0% including them like do they have to 00:14:27.800 --> 00:14:30.350 align:start position:0% including them like do they have to learn<00:14:28.199> some<00:14:28.399> protocol<00:14:28.759> do<00:14:28.839> they<00:14:29.199> have<00:14:29.320> to<00:14:29.920> like 00:14:30.350 --> 00:14:30.360 align:start position:0% learn some protocol do they have to like 00:14:30.360 --> 00:14:32.710 align:start position:0% learn some protocol do they have to like or<00:14:30.519> is<00:14:30.800> or<00:14:30.959> could<00:14:31.120> there<00:14:31.279> be<00:14:31.639> easier<00:14:32.040> Pathways 00:14:32.710 --> 00:14:32.720 align:start position:0% or is or could there be easier Pathways 00:14:32.720 --> 00:14:34.030 align:start position:0% or is or could there be easier Pathways for<00:14:33.000> for<00:14:33.160> these<00:14:33.360> guys<00:14:33.480> to<00:14:33.639> enter<00:14:33.920> the 00:14:34.030 --> 00:14:34.040 align:start position:0% for for these guys to enter the 00:14:34.040 --> 00:14:37.150 align:start position:0% for for these guys to enter the ecosystem<00:14:34.560> as<00:14:34.720> well<00:14:35.639> yeah<00:14:35.880> I<00:14:36.000> think<00:14:36.720> uh<00:14:36.959> this 00:14:37.150 --> 00:14:37.160 align:start position:0% ecosystem as well yeah I think uh this 00:14:37.160 --> 00:14:40.509 align:start position:0% ecosystem as well yeah I think uh this is<00:14:37.399> an<00:14:37.600> issue<00:14:38.040> with<00:14:38.199> web<00:14:38.440> 3<00:14:38.759> it's<00:14:39.079> it's<00:14:39.680> uh<00:14:39.959> more 00:14:40.509 --> 00:14:40.519 align:start position:0% is an issue with web 3 it's it's uh more 00:14:40.519 --> 00:14:44.269 align:start position:0% is an issue with web 3 it's it's uh more insular<00:14:41.320> than<00:14:41.639> it<00:14:41.839> could<00:14:42.160> be<00:14:43.160> um<00:14:43.639> and<00:14:43.920> a<00:14:44.000> lot<00:14:44.160> of 00:14:44.269 --> 00:14:44.279 align:start position:0% insular than it could be um and a lot of 00:14:44.279 --> 00:14:46.670 align:start position:0% insular than it could be um and a lot of use<00:14:44.600> cases<00:14:45.079> are<00:14:45.440> being<00:14:45.720> built<00:14:46.160> specifically 00:14:46.670 --> 00:14:46.680 align:start position:0% use cases are being built specifically 00:14:46.680 --> 00:14:50.069 align:start position:0% use cases are being built specifically for<00:14:46.959> the<00:14:47.079> web<00:14:47.320> 3<00:14:47.680> Community<00:14:48.680> um<00:14:48.920> I<00:14:49.000> think<00:14:49.279> these 00:14:50.069 --> 00:14:50.079 align:start position:0% for the web 3 Community um I think these 00:14:50.079 --> 00:14:51.629 align:start position:0% for the web 3 Community um I think these uh<00:14:50.240> types<00:14:50.440> of<00:14:50.680> exceptions<00:14:51.120> are<00:14:51.399> really 00:14:51.629 --> 00:14:51.639 align:start position:0% uh types of exceptions are really 00:14:51.639 --> 00:14:54.030 align:start position:0% uh types of exceptions are really interesting<00:14:52.160> and<00:14:52.920> um<00:14:53.279> the<00:14:53.560> the<00:14:53.639> broader 00:14:54.030 --> 00:14:54.040 align:start position:0% interesting and um the the broader 00:14:54.040 --> 00:14:56.629 align:start position:0% interesting and um the the broader crypto<00:14:54.399> ecosystem<00:14:55.040> would<00:14:55.320> would<00:14:55.480> do<00:14:55.720> well<00:14:56.240> to 00:14:56.629 --> 00:14:56.639 align:start position:0% crypto ecosystem would would do well to 00:14:56.639 --> 00:15:01.110 align:start position:0% crypto ecosystem would would do well to engage<00:14:57.639> um<00:14:58.040> more<00:14:58.560> I<00:14:58.680> have<00:14:59.079> seen<00:14:59.800> uh<00:15:00.440> some<00:15:01.000> kind 00:15:01.110 --> 00:15:01.120 align:start position:0% engage um more I have seen uh some kind 00:15:01.120 --> 00:15:03.509 align:start position:0% engage um more I have seen uh some kind of<00:15:01.360> retroactive<00:15:02.360> uh<00:15:02.519> airdrops<00:15:03.160> and<00:15:03.360> and 00:15:03.509 --> 00:15:03.519 align:start position:0% of retroactive uh airdrops and and 00:15:03.519 --> 00:15:06.550 align:start position:0% of retroactive uh airdrops and and funding<00:15:04.440> mechanisms<00:15:05.079> going<00:15:05.320> to<00:15:05.959> uh<00:15:06.079> GitHub 00:15:06.550 --> 00:15:06.560 align:start position:0% funding mechanisms going to uh GitHub 00:15:06.560 --> 00:15:08.990 align:start position:0% funding mechanisms going to uh GitHub profiles<00:15:07.480> of<00:15:07.639> web<00:15:07.839> 2<00:15:08.079> developers<00:15:08.680> that<00:15:08.839> may 00:15:08.990 --> 00:15:09.000 align:start position:0% profiles of web 2 developers that may 00:15:09.000 --> 00:15:11.870 align:start position:0% profiles of web 2 developers that may have<00:15:09.519> never<00:15:09.759> heard<00:15:10.040> of<00:15:11.040> uh<00:15:11.560> the<00:15:11.639> people 00:15:11.870 --> 00:15:11.880 align:start position:0% have never heard of uh the people 00:15:11.880 --> 00:15:14.269 align:start position:0% have never heard of uh the people sending<00:15:12.240> them<00:15:12.440> the<00:15:12.560> token<00:15:13.079> but<00:15:13.600> like<00:15:13.759> I<00:15:13.920> think 00:15:14.269 --> 00:15:14.279 align:start position:0% sending them the token but like I think 00:15:14.279 --> 00:15:16.910 align:start position:0% sending them the token but like I think uh<00:15:14.800> ZK<00:15:15.279> sync<00:15:15.639> might<00:15:15.759> have<00:15:15.920> done<00:15:16.120> this<00:15:16.519> a<00:15:16.600> few<00:15:16.839> a 00:15:16.910 --> 00:15:16.920 align:start position:0% uh ZK sync might have done this a few a 00:15:16.920 --> 00:15:20.430 align:start position:0% uh ZK sync might have done this a few a few<00:15:17.560> um<00:15:17.959> recent<00:15:18.959> uh<00:15:19.079> airdrops<00:15:19.639> have<00:15:19.800> gone<00:15:20.040> to 00:15:20.430 --> 00:15:20.440 align:start position:0% few um recent uh airdrops have gone to 00:15:20.440 --> 00:15:22.509 align:start position:0% few um recent uh airdrops have gone to web<00:15:20.680> 2<00:15:20.959> developers<00:15:21.880> that<00:15:22.000> are<00:15:22.160> building 00:15:22.509 --> 00:15:22.519 align:start position:0% web 2 developers that are building 00:15:22.519 --> 00:15:25.350 align:start position:0% web 2 developers that are building libraries<00:15:23.279> that<00:15:23.480> have<00:15:23.680> been<00:15:24.000> leveraged<00:15:25.000> um<00:15:25.199> by 00:15:25.350 --> 00:15:25.360 align:start position:0% libraries that have been leveraged um by 00:15:25.360 --> 00:15:27.350 align:start position:0% libraries that have been leveraged um by crypto<00:15:25.759> protocols<00:15:26.279> and<00:15:26.440> then<00:15:26.720> the<00:15:27.000> the<00:15:27.240> they 00:15:27.350 --> 00:15:27.360 align:start position:0% crypto protocols and then the the they 00:15:27.360 --> 00:15:30.910 align:start position:0% crypto protocols and then the the they send<00:15:27.560> it<00:15:27.759> like<00:15:27.880> directly<00:15:28.240> to<00:15:28.480> a<00:15:28.680> a<00:15:29.160> Hub<00:15:30.040> um 00:15:30.910 --> 00:15:30.920 align:start position:0% send it like directly to a a Hub um 00:15:30.920 --> 00:15:33.069 align:start position:0% send it like directly to a a Hub um address<00:15:31.319> and<00:15:31.560> account<00:15:32.000> and<00:15:32.279> and<00:15:32.440> that's<00:15:32.759> uh 00:15:33.069 --> 00:15:33.079 align:start position:0% address and account and and that's uh 00:15:33.079 --> 00:15:34.470 align:start position:0% address and account and and that's uh that's<00:15:33.240> one<00:15:33.440> way<00:15:33.600> that<00:15:33.720> I've<00:15:33.880> seen<00:15:34.199> the<00:15:34.360> the 00:15:34.470 --> 00:15:34.480 align:start position:0% that's one way that I've seen the the 00:15:34.480 --> 00:15:38.030 align:start position:0% that's one way that I've seen the the web3<00:15:35.319> community<00:15:35.759> engaging<00:15:36.680> um<00:15:37.279> Beyond<00:15:37.880> kind 00:15:38.030 --> 00:15:38.040 align:start position:0% web3 community engaging um Beyond kind 00:15:38.040 --> 00:15:41.509 align:start position:0% web3 community engaging um Beyond kind of<00:15:38.319> the<00:15:39.120> um<00:15:39.360> the<00:15:39.519> small<00:15:40.440> relatively<00:15:41.000> small<00:15:41.360> but 00:15:41.509 --> 00:15:41.519 align:start position:0% of the um the small relatively small but 00:15:41.519 --> 00:15:44.470 align:start position:0% of the um the small relatively small but but<00:15:41.639> growing<00:15:42.040> ecosystem<00:15:42.639> that<00:15:42.759> we<00:15:42.880> have<00:15:43.480> here 00:15:44.470 --> 00:15:44.480 align:start position:0% but growing ecosystem that we have here 00:15:44.480 --> 00:15:46.629 align:start position:0% but growing ecosystem that we have here that's<00:15:44.839> uh<00:15:45.040> very<00:15:45.240> very<00:15:45.440> encouraging<00:15:46.360> uh<00:15:46.480> to 00:15:46.629 --> 00:15:46.639 align:start position:0% that's uh very very encouraging uh to 00:15:46.639 --> 00:15:49.550 align:start position:0% that's uh very very encouraging uh to know<00:15:46.959> that<00:15:47.560> new<00:15:47.839> avenues<00:15:48.240> are<00:15:48.399> opening<00:15:48.720> up<00:15:49.440> uh 00:15:49.550 --> 00:15:49.560 align:start position:0% know that new avenues are opening up uh 00:15:49.560 --> 00:15:53.150 align:start position:0% know that new avenues are opening up uh for<00:15:50.240> broader<00:15:50.680> areas<00:15:51.000> of<00:15:51.199> impact<00:15:52.000> uh<00:15:52.120> to<00:15:53.000> be 00:15:53.150 --> 00:15:53.160 align:start position:0% for broader areas of impact uh to be 00:15:53.160 --> 00:15:56.309 align:start position:0% for broader areas of impact uh to be funded<00:15:53.560> by<00:15:53.680> the<00:15:54.120> by<00:15:54.240> the<00:15:54.600> web3<00:15:55.480> ecosystem<00:15:56.120> so 00:15:56.309 --> 00:15:56.319 align:start position:0% funded by the by the web3 ecosystem so 00:15:56.319 --> 00:15:58.629 align:start position:0% funded by the by the web3 ecosystem so that's<00:15:56.560> fantastic<00:15:57.519> um<00:15:57.720> that's<00:15:57.880> all<00:15:58.079> the<00:15:58.279> time 00:15:58.629 --> 00:15:58.639 align:start position:0% that's fantastic um that's all the time 00:15:58.639 --> 00:16:02.269 align:start position:0% that's fantastic um that's all the time that<00:15:59.079> we<00:15:59.600> have<00:16:00.079> uh<00:16:00.279> thank<00:16:00.440> you<00:16:00.560> so<00:16:00.800> much<00:16:01.680> uh<00:16:01.839> MB 00:16:02.269 --> 00:16:02.279 align:start position:0% that we have uh thank you so much uh MB 00:16:02.279 --> 00:16:04.550 align:start position:0% that we have uh thank you so much uh MB mani<00:16:02.759> and<00:16:03.199> uh<00:16:03.360> David<00:16:03.920> for<00:16:04.240> of<00:16:04.360> course 00:16:04.550 --> 00:16:04.560 align:start position:0% mani and uh David for of course 00:16:04.560 --> 00:16:06.269 align:start position:0% mani and uh David for of course highlighting<00:16:04.959> the<00:16:05.079> solution<00:16:05.600> and<00:16:05.759> of<00:16:05.920> course 00:16:06.269 --> 00:16:06.279 align:start position:0% highlighting the solution and of course 00:16:06.279 --> 00:16:07.829 align:start position:0% highlighting the solution and of course uh<00:16:06.399> talking<00:16:06.720> about<00:16:07.199> the<00:16:07.319> ways<00:16:07.519> in<00:16:07.639> which 00:16:07.829 --> 00:16:07.839 align:start position:0% uh talking about the ways in which 00:16:07.839 --> 00:16:09.670 align:start position:0% uh talking about the ways in which Solutions<00:16:08.240> such<00:16:08.440> as<00:16:08.600> stat<00:16:08.880> wig<00:16:09.240> and<00:16:09.560> the 00:16:09.670 --> 00:16:09.680 align:start position:0% Solutions such as stat wig and the 00:16:09.680 --> 00:16:11.269 align:start position:0% Solutions such as stat wig and the vaccine<00:16:09.959> Ledger<00:16:10.360> could<00:16:10.560> get<00:16:10.680> funded<00:16:11.160> thank 00:16:11.269 --> 00:16:11.279 align:start position:0% vaccine Ledger could get funded thank 00:16:11.279 --> 00:16:15.920 align:start position:0% vaccine Ledger could get funded thank you<00:16:11.399> so<00:16:11.920> much<00:16:12.920> thanks