WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:14.470 align:start position:0% [Music] 00:00:14.470 --> 00:00:14.480 align:start position:0% 00:00:14.480 --> 00:00:17.330 align:start position:0% I<00:00:15.480> hope<00:00:15.719> you<00:00:16.080> are<00:00:16.260> all<00:00:16.379> having<00:00:16.680> a<00:00:16.980> fantastic 00:00:17.330 --> 00:00:17.340 align:start position:0% I hope you are all having a fantastic 00:00:17.340 --> 00:00:20.330 align:start position:0% I hope you are all having a fantastic day<00:00:17.699> like<00:00:18.119> my<00:00:18.420> name<00:00:18.480> is<00:00:18.600> Anna<00:00:19.080> and<00:00:19.500> Evelyn<00:00:20.100> and 00:00:20.330 --> 00:00:20.340 align:start position:0% day like my name is Anna and Evelyn and 00:00:20.340 --> 00:00:22.130 align:start position:0% day like my name is Anna and Evelyn and I'm<00:00:20.580> very<00:00:20.760> excited<00:00:21.060> because<00:00:21.359> this<00:00:21.660> is<00:00:21.840> the 00:00:22.130 --> 00:00:22.140 align:start position:0% I'm very excited because this is the 00:00:22.140 --> 00:00:25.009 align:start position:0% I'm very excited because this is the first<00:00:22.380> day<00:00:22.920> of<00:00:23.340> talks<00:00:23.880> in<00:00:24.480> the<00:00:24.660> tropical 00:00:25.009 --> 00:00:25.019 align:start position:0% first day of talks in the tropical 00:00:25.019 --> 00:00:28.370 align:start position:0% first day of talks in the tropical Sunset<00:00:25.619> and<00:00:26.279> today<00:00:26.460> we<00:00:27.060> have<00:00:27.359> the<00:00:27.900> talk<00:00:28.080> of 00:00:28.370 --> 00:00:28.380 align:start position:0% Sunset and today we have the talk of 00:00:28.380 --> 00:00:31.669 align:start position:0% Sunset and today we have the talk of ethereum<00:00:28.859> business<00:00:29.099> redness<00:00:29.699> in<00:00:30.060> 2022<00:00:30.840> with 00:00:31.669 --> 00:00:31.679 align:start position:0% ethereum business redness in 2022 with 00:00:31.679 --> 00:00:34.190 align:start position:0% ethereum business redness in 2022 with Dan<00:00:31.920> sha<00:00:32.399> and<00:00:32.759> Dan<00:00:33.059> Burnett 00:00:34.190 --> 00:00:34.200 align:start position:0% Dan sha and Dan Burnett 00:00:34.200 --> 00:00:37.610 align:start position:0% Dan sha and Dan Burnett thank<00:00:34.739> you<00:00:34.920> so<00:00:35.100> much<00:00:35.239> thank<00:00:36.239> you 00:00:37.610 --> 00:00:37.620 align:start position:0% thank you so much thank you 00:00:37.620 --> 00:00:39.530 align:start position:0% thank you so much thank you all<00:00:38.100> the<00:00:38.280> dance 00:00:39.530 --> 00:00:39.540 align:start position:0% all the dance 00:00:39.540 --> 00:00:41.330 align:start position:0% all the dance ethereum<00:00:40.260> Enterprise<00:00:40.500> you<00:00:41.100> have<00:00:41.219> to<00:00:41.280> be 00:00:41.330 --> 00:00:41.340 align:start position:0% ethereum Enterprise you have to be 00:00:41.340 --> 00:00:45.170 align:start position:0% ethereum Enterprise you have to be called<00:00:41.460> Dan<00:00:42.260> uh<00:00:43.260> so<00:00:43.739> hi<00:00:44.100> I'm<00:00:44.280> Dan<00:00:44.399> Shaw<00:00:44.820> from 00:00:45.170 --> 00:00:45.180 align:start position:0% called Dan uh so hi I'm Dan Shaw from 00:00:45.180 --> 00:00:47.030 align:start position:0% called Dan uh so hi I'm Dan Shaw from the<00:00:45.239> ethereum<00:00:45.660> foundation 00:00:47.030 --> 00:00:47.040 align:start position:0% the ethereum foundation 00:00:47.040 --> 00:00:49.850 align:start position:0% the ethereum foundation um<00:00:47.219> you<00:00:47.520> know<00:00:47.640> I<00:00:47.760> I<00:00:48.000> work<00:00:48.300> with<00:00:48.539> the<00:00:49.200> uh 00:00:49.850 --> 00:00:49.860 align:start position:0% um you know I I work with the uh 00:00:49.860 --> 00:00:52.490 align:start position:0% um you know I I work with the uh Enterprise<00:00:50.100> uh<00:00:51.059> big<00:00:51.300> businesses<00:00:51.719> back<00:00:52.320> in 00:00:52.490 --> 00:00:52.500 align:start position:0% Enterprise uh big businesses back in 00:00:52.500 --> 00:00:56.930 align:start position:0% Enterprise uh big businesses back in 2017<00:00:53.059> uh<00:00:54.059> at<00:00:54.300> the<00:00:54.420> launch<00:00:54.719> of<00:00:55.500> uh<00:00:56.340> the<00:00:56.579> ethereum 00:00:56.930 --> 00:00:56.940 align:start position:0% 2017 uh at the launch of uh the ethereum 00:00:56.940 --> 00:00:58.910 align:start position:0% 2017 uh at the launch of uh the ethereum the<00:00:57.300> Enterprise<00:00:57.420> ethereum<00:00:58.020> Alliance<00:00:58.379> the<00:00:58.500> eea 00:00:58.910 --> 00:00:58.920 align:start position:0% the Enterprise ethereum Alliance the eea 00:00:58.920 --> 00:01:01.330 align:start position:0% the Enterprise ethereum Alliance the eea uh<00:00:59.820> you<00:00:59.940> know<00:01:00.059> vitalik<00:01:00.480> called<00:01:00.660> for 00:01:01.330 --> 00:01:01.340 align:start position:0% uh you know vitalik called for 00:01:01.340 --> 00:01:04.729 align:start position:0% uh you know vitalik called for collaboration<00:01:02.340> amongst<00:01:02.940> private<00:01:03.359> and<00:01:03.960> uh<00:01:04.559> you 00:01:04.729 --> 00:01:04.739 align:start position:0% collaboration amongst private and uh you 00:01:04.739 --> 00:01:06.289 align:start position:0% collaboration amongst private and uh you know<00:01:04.860> public 00:01:06.289 --> 00:01:06.299 align:start position:0% know public 00:01:06.299 --> 00:01:09.410 align:start position:0% know public um<00:01:06.840> uh<00:01:07.740> you<00:01:07.979> know<00:01:08.100> to<00:01:08.280> to<00:01:08.400> be<00:01:08.820> able<00:01:09.000> to<00:01:09.119> support 00:01:09.410 --> 00:01:09.420 align:start position:0% um uh you know to to be able to support 00:01:09.420 --> 00:01:12.649 align:start position:0% um uh you know to to be able to support Enterprise<00:01:10.020> needs<00:01:10.619> and 00:01:12.649 --> 00:01:12.659 align:start position:0% Enterprise needs and 00:01:12.659 --> 00:01:15.770 align:start position:0% Enterprise needs and um<00:01:12.780> you<00:01:13.080> know<00:01:13.140> I<00:01:13.380> I<00:01:13.560> joined<00:01:14.040> back<00:01:14.280> in 00:01:15.770 --> 00:01:15.780 align:start position:0% um you know I I joined back in 00:01:15.780 --> 00:01:20.030 align:start position:0% um you know I I joined back in um<00:01:15.900> in<00:01:16.740> 2020<00:01:17.479> to<00:01:18.479> come<00:01:18.840> in<00:01:19.020> and<00:01:19.380> support<00:01:19.619> those 00:01:20.030 --> 00:01:20.040 align:start position:0% um in 2020 to come in and support those 00:01:20.040 --> 00:01:22.310 align:start position:0% um in 2020 to come in and support those Enterprise<00:01:20.159> users<00:01:20.759> uh<00:01:21.600> you<00:01:21.720> know<00:01:21.840> when<00:01:21.960> I<00:01:22.140> came 00:01:22.310 --> 00:01:22.320 align:start position:0% Enterprise users uh you know when I came 00:01:22.320 --> 00:01:24.950 align:start position:0% Enterprise users uh you know when I came in<00:01:22.560> uh<00:01:23.520> there<00:01:23.700> were<00:01:24.060> some<00:01:24.180> you<00:01:24.360> know<00:01:24.540> sort<00:01:24.840> of 00:01:24.950 --> 00:01:24.960 align:start position:0% in uh there were some you know sort of 00:01:24.960 --> 00:01:27.649 align:start position:0% in uh there were some you know sort of big<00:01:25.140> blockers<00:01:25.619> for<00:01:26.220> uh<00:01:27.060> you<00:01:27.180> know<00:01:27.299> going<00:01:27.420> on<00:01:27.600> on 00:01:27.649 --> 00:01:27.659 align:start position:0% big blockers for uh you know going on on 00:01:27.659 --> 00:01:29.090 align:start position:0% big blockers for uh you know going on on mainnet 00:01:29.090 --> 00:01:29.100 align:start position:0% mainnet 00:01:29.100 --> 00:01:30.710 align:start position:0% mainnet um you<00:01:29.220> know<00:01:29.340> concerns<00:01:29.700> around<00:01:29.759> privacy<00:01:30.240> gas 00:01:30.710 --> 00:01:30.720 align:start position:0% um you know concerns around privacy gas 00:01:30.720 --> 00:01:33.770 align:start position:0% um you know concerns around privacy gas prices<00:01:31.340> and<00:01:32.340> you<00:01:32.640> know<00:01:32.759> regular<00:01:33.060> regulatory 00:01:33.770 --> 00:01:33.780 align:start position:0% prices and you know regular regulatory 00:01:33.780 --> 00:01:36.410 align:start position:0% prices and you know regular regulatory risks<00:01:34.200> of<00:01:34.380> holding<00:01:34.920> assets 00:01:36.410 --> 00:01:36.420 align:start position:0% risks of holding assets 00:01:36.420 --> 00:01:38.870 align:start position:0% risks of holding assets um<00:01:36.479> over<00:01:36.780> the<00:01:36.960> past<00:01:37.079> year<00:01:37.380> and<00:01:37.560> a<00:01:37.680> half<00:01:37.880> I've 00:01:38.870 --> 00:01:38.880 align:start position:0% um over the past year and a half I've 00:01:38.880 --> 00:01:41.569 align:start position:0% um over the past year and a half I've been<00:01:39.119> really<00:01:39.299> happy<00:01:39.540> to<00:01:39.840> see<00:01:40.140> a<00:01:40.860> massive<00:01:41.280> sea 00:01:41.569 --> 00:01:41.579 align:start position:0% been really happy to see a massive sea 00:01:41.579 --> 00:01:45.170 align:start position:0% been really happy to see a massive sea change<00:01:41.700> away<00:01:42.119> from<00:01:42.600> uh<00:01:43.439> only<00:01:43.799> uh<00:01:44.640> a<00:01:44.880> private 00:01:45.170 --> 00:01:45.180 align:start position:0% change away from uh only uh a private 00:01:45.180 --> 00:01:47.569 align:start position:0% change away from uh only uh a private chain<00:01:45.420> and<00:01:46.259> you<00:01:46.500> know<00:01:46.619> gradual<00:01:46.979> introduction 00:01:47.569 --> 00:01:47.579 align:start position:0% chain and you know gradual introduction 00:01:47.579 --> 00:01:50.810 align:start position:0% chain and you know gradual introduction of<00:01:48.119> uh<00:01:48.840> real<00:01:49.079> real<00:01:49.320> mainnet<00:01:49.860> adoption<00:01:50.220> but<00:01:50.700> I 00:01:50.810 --> 00:01:50.820 align:start position:0% of uh real real mainnet adoption but I 00:01:50.820 --> 00:01:52.249 align:start position:0% of uh real real mainnet adoption but I really<00:01:50.939> didn't<00:01:51.119> know<00:01:51.420> you<00:01:51.780> know<00:01:51.899> what<00:01:52.140> was 00:01:52.249 --> 00:01:52.259 align:start position:0% really didn't know you know what was 00:01:52.259 --> 00:01:55.130 align:start position:0% really didn't know you know what was going<00:01:52.439> on<00:01:52.700> uh<00:01:53.700> and<00:01:54.119> I'm<00:01:54.420> really<00:01:54.600> happy<00:01:54.840> to 00:01:55.130 --> 00:01:55.140 align:start position:0% going on uh and I'm really happy to 00:01:55.140 --> 00:01:57.889 align:start position:0% going on uh and I'm really happy to share<00:01:55.380> what<00:01:56.100> uh<00:01:56.460> Dan<00:01:57.000> Burnett<00:01:57.360> and<00:01:57.540> the<00:01:57.600> EA 00:01:57.889 --> 00:01:57.899 align:start position:0% share what uh Dan Burnett and the EA 00:01:57.899 --> 00:01:59.870 align:start position:0% share what uh Dan Burnett and the EA have<00:01:58.079> been<00:01:58.200> working<00:01:58.320> on<00:01:58.619> uh<00:01:59.399> you<00:01:59.520> know<00:01:59.640> to 00:01:59.870 --> 00:01:59.880 align:start position:0% have been working on uh you know to 00:01:59.880 --> 00:02:01.249 align:start position:0% have been working on uh you know to really<00:02:00.000> you<00:02:00.299> know<00:02:00.360> give<00:02:00.540> us<00:02:00.659> some<00:02:00.780> proof<00:02:01.020> give 00:02:01.249 --> 00:02:01.259 align:start position:0% really you know give us some proof give 00:02:01.259 --> 00:02:04.069 align:start position:0% really you know give us some proof give us<00:02:01.380> some<00:02:01.500> data<00:02:01.860> uh<00:02:02.579> and<00:02:03.000> uh<00:02:03.420> I've<00:02:03.659> been<00:02:03.960> really 00:02:04.069 --> 00:02:04.079 align:start position:0% us some data uh and uh I've been really 00:02:04.079 --> 00:02:07.130 align:start position:0% us some data uh and uh I've been really surprised<00:02:04.680> at<00:02:05.520> uh<00:02:05.939> at<00:02:06.180> the<00:02:06.299> majority<00:02:06.540> of<00:02:06.780> of 00:02:07.130 --> 00:02:07.140 align:start position:0% surprised at uh at the majority of of 00:02:07.140 --> 00:02:09.290 align:start position:0% surprised at uh at the majority of of what's<00:02:07.259> going<00:02:07.500> on<00:02:07.759> you<00:02:08.759> know<00:02:08.940> things<00:02:09.060> are 00:02:09.290 --> 00:02:09.300 align:start position:0% what's going on you know things are 00:02:09.300 --> 00:02:13.610 align:start position:0% what's going on you know things are farther<00:02:10.520> ahead<00:02:11.520> and<00:02:11.640> farther<00:02:12.120> on<00:02:13.080> mainnet 00:02:13.610 --> 00:02:13.620 align:start position:0% farther ahead and farther on mainnet 00:02:13.620 --> 00:02:16.670 align:start position:0% farther ahead and farther on mainnet than<00:02:13.920> you<00:02:14.520> might<00:02:14.700> think<00:02:14.819> so<00:02:15.360> Dan<00:02:15.540> Burnett 00:02:16.670 --> 00:02:16.680 align:start position:0% than you might think so Dan Burnett 00:02:16.680 --> 00:02:19.810 align:start position:0% than you might think so Dan Burnett thanks<00:02:17.040> so<00:02:17.220> much 00:02:19.810 --> 00:02:19.820 align:start position:0% 00:02:19.820 --> 00:02:26.690 align:start position:0% [Applause] 00:02:26.690 --> 00:02:26.700 align:start position:0% 00:02:26.700 --> 00:02:29.150 align:start position:0% hello<00:02:27.120> oh<00:02:27.480> there<00:02:27.720> we<00:02:27.840> go<00:02:27.959> all<00:02:28.260> right<00:02:28.440> okay 00:02:29.150 --> 00:02:29.160 align:start position:0% hello oh there we go all right okay 00:02:29.160 --> 00:02:30.229 align:start position:0% hello oh there we go all right okay thanks 00:02:30.229 --> 00:02:30.239 align:start position:0% thanks 00:02:30.239 --> 00:02:32.570 align:start position:0% thanks um<00:02:30.360> and<00:02:30.720> I<00:02:30.840> may<00:02:31.020> ask<00:02:31.140> you<00:02:31.260> to<00:02:31.440> put<00:02:31.560> the<00:02:31.860> notes 00:02:32.570 --> 00:02:32.580 align:start position:0% um and I may ask you to put the notes 00:02:32.580 --> 00:02:35.570 align:start position:0% um and I may ask you to put the notes font<00:02:32.879> size<00:02:33.060> back<00:02:33.420> to<00:02:33.599> what<00:02:33.840> we<00:02:34.080> had<00:02:34.319> agreed<00:02:34.739> to 00:02:35.570 --> 00:02:35.580 align:start position:0% font size back to what we had agreed to 00:02:35.580 --> 00:02:38.390 align:start position:0% font size back to what we had agreed to um<00:02:35.640> all<00:02:35.819> right<00:02:36.000> thanks<00:02:36.660> uh<00:02:37.319> yeah<00:02:37.620> all<00:02:38.160> right<00:02:38.280> so 00:02:38.390 --> 00:02:38.400 align:start position:0% um all right thanks uh yeah all right so 00:02:38.400 --> 00:02:39.710 align:start position:0% um all right thanks uh yeah all right so anyway<00:02:38.520> what<00:02:38.819> I'm<00:02:39.000> here<00:02:39.180> to<00:02:39.300> talk<00:02:39.420> to<00:02:39.599> you 00:02:39.710 --> 00:02:39.720 align:start position:0% anyway what I'm here to talk to you 00:02:39.720 --> 00:02:42.170 align:start position:0% anyway what I'm here to talk to you about<00:02:40.020> today<00:02:40.379> is<00:02:40.860> a<00:02:41.099> report<00:02:41.280> that<00:02:41.760> the<00:02:41.879> EA 00:02:42.170 --> 00:02:42.180 align:start position:0% about today is a report that the EA 00:02:42.180 --> 00:02:45.170 align:start position:0% about today is a report that the EA wrote<00:02:42.540> issued<00:02:43.319> earlier<00:02:43.739> this<00:02:43.980> year<00:02:44.180> our 00:02:45.170 --> 00:02:45.180 align:start position:0% wrote issued earlier this year our 00:02:45.180 --> 00:02:48.050 align:start position:0% wrote issued earlier this year our ethereum<00:02:45.599> business<00:02:45.900> Readiness<00:02:46.620> report 00:02:48.050 --> 00:02:48.060 align:start position:0% ethereum business Readiness report 00:02:48.060 --> 00:02:49.670 align:start position:0% ethereum business Readiness report so 00:02:49.670 --> 00:02:49.680 align:start position:0% so 00:02:49.680 --> 00:02:51.890 align:start position:0% so you<00:02:50.160> know<00:02:50.220> in<00:02:50.519> the<00:02:50.640> media<00:02:50.940> all<00:02:51.420> the<00:02:51.599> stories 00:02:51.890 --> 00:02:51.900 align:start position:0% you know in the media all the stories 00:02:51.900 --> 00:02:54.530 align:start position:0% you know in the media all the stories are<00:02:52.080> focused<00:02:52.500> on<00:02:52.800> uh<00:02:53.280> you<00:02:53.519> know<00:02:53.640> popular<00:02:54.060> media 00:02:54.530 --> 00:02:54.540 align:start position:0% are focused on uh you know popular media 00:02:54.540 --> 00:02:56.330 align:start position:0% are focused on uh you know popular media right<00:02:54.720> all<00:02:54.959> focused<00:02:55.319> on<00:02:55.440> crypto<00:02:55.860> speculation 00:02:56.330 --> 00:02:56.340 align:start position:0% right all focused on crypto speculation 00:02:56.340 --> 00:02:59.570 align:start position:0% right all focused on crypto speculation nft<00:02:56.760> speculation<00:02:57.480> uh<00:02:58.440> big<00:02:58.620> collapses<00:02:59.220> and 00:02:59.570 --> 00:02:59.580 align:start position:0% nft speculation uh big collapses and 00:02:59.580 --> 00:03:01.490 align:start position:0% nft speculation uh big collapses and things<00:02:59.760> like<00:03:00.000> that<00:03:00.120> but<00:03:00.780> as<00:03:00.959> the<00:03:01.140> ethereum 00:03:01.490 --> 00:03:01.500 align:start position:0% things like that but as the ethereum 00:03:01.500 --> 00:03:03.530 align:start position:0% things like that but as the ethereum ecosystem<00:03:01.920> matures<00:03:02.580> more<00:03:03.120> and<00:03:03.300> more 00:03:03.530 --> 00:03:03.540 align:start position:0% ecosystem matures more and more 00:03:03.540 --> 00:03:05.809 align:start position:0% ecosystem matures more and more businesses<00:03:04.140> are<00:03:04.739> actually<00:03:05.040> adopting<00:03:05.580> the 00:03:05.809 --> 00:03:05.819 align:start position:0% businesses are actually adopting the 00:03:05.819 --> 00:03:08.750 align:start position:0% businesses are actually adopting the technology<00:03:06.560> unfortunately<00:03:07.560> that<00:03:08.160> story<00:03:08.400> is 00:03:08.750 --> 00:03:08.760 align:start position:0% technology unfortunately that story is 00:03:08.760 --> 00:03:10.850 align:start position:0% technology unfortunately that story is not<00:03:09.000> as<00:03:09.120> visible<00:03:09.540> to<00:03:10.140> the<00:03:10.319> general<00:03:10.500> public 00:03:10.850 --> 00:03:10.860 align:start position:0% not as visible to the general public 00:03:10.860 --> 00:03:13.369 align:start position:0% not as visible to the general public okay<00:03:11.819> and 00:03:13.369 --> 00:03:13.379 align:start position:0% okay and 00:03:13.379 --> 00:03:14.990 align:start position:0% okay and um<00:03:13.440> it's 00:03:14.990 --> 00:03:15.000 align:start position:0% um it's 00:03:15.000 --> 00:03:17.930 align:start position:0% um it's as<00:03:15.659> as<00:03:15.840> an<00:03:16.080> organization<00:03:16.620> that<00:03:17.099> is<00:03:17.459> committed 00:03:17.930 --> 00:03:17.940 align:start position:0% as as an organization that is committed 00:03:17.940 --> 00:03:20.630 align:start position:0% as as an organization that is committed to<00:03:18.180> enabling<00:03:18.739> uh<00:03:19.739> other<00:03:19.920> organizations<00:03:20.400> to 00:03:20.630 --> 00:03:20.640 align:start position:0% to enabling uh other organizations to 00:03:20.640 --> 00:03:23.449 align:start position:0% to enabling uh other organizations to adopt<00:03:21.060> and<00:03:21.180> use<00:03:21.360> business<00:03:21.720> uh<00:03:22.200> ethereum<00:03:22.680> uh<00:03:23.220> in 00:03:23.449 --> 00:03:23.459 align:start position:0% adopt and use business uh ethereum uh in 00:03:23.459 --> 00:03:25.729 align:start position:0% adopt and use business uh ethereum uh in their<00:03:23.640> day-to-day<00:03:24.060> business<00:03:24.300> operations<00:03:24.840> uh 00:03:25.729 --> 00:03:25.739 align:start position:0% their day-to-day business operations uh 00:03:25.739 --> 00:03:27.050 align:start position:0% their day-to-day business operations uh we<00:03:25.920> thought<00:03:26.040> it<00:03:26.220> was<00:03:26.280> important<00:03:26.640> to<00:03:26.819> shed 00:03:27.050 --> 00:03:27.060 align:start position:0% we thought it was important to shed 00:03:27.060 --> 00:03:29.690 align:start position:0% we thought it was important to shed light<00:03:27.239> on<00:03:27.480> what's<00:03:27.780> actually<00:03:28.140> happening<00:03:28.860> in 00:03:29.690 --> 00:03:29.700 align:start position:0% light on what's actually happening in 00:03:29.700 --> 00:03:31.790 align:start position:0% light on what's actually happening in business<00:03:29.879> use<00:03:30.180> of<00:03:30.360> ethereum<00:03:30.840> today<00:03:31.080> so<00:03:31.379> behind 00:03:31.790 --> 00:03:31.800 align:start position:0% business use of ethereum today so behind 00:03:31.800 --> 00:03:35.149 align:start position:0% business use of ethereum today so behind the<00:03:31.980> defy<00:03:32.580> nft<00:03:33.120> and<00:03:33.599> so<00:03:33.780> on<00:03:33.900> headlines<00:03:34.379> now 00:03:35.149 --> 00:03:35.159 align:start position:0% the defy nft and so on headlines now 00:03:35.159 --> 00:03:36.949 align:start position:0% the defy nft and so on headlines now there<00:03:35.340> are<00:03:35.459> some<00:03:35.580> challenges<00:03:36.000> to<00:03:36.239> this<00:03:36.420> in 00:03:36.949 --> 00:03:36.959 align:start position:0% there are some challenges to this in 00:03:36.959 --> 00:03:39.649 align:start position:0% there are some challenges to this in particular<00:03:37.280> day-to-day<00:03:38.280> projects<00:03:38.940> are<00:03:39.420> all 00:03:39.649 --> 00:03:39.659 align:start position:0% particular day-to-day projects are all 00:03:39.659 --> 00:03:42.050 align:start position:0% particular day-to-day projects are all happening<00:03:39.959> behind<00:03:40.379> the<00:03:40.500> scenes<00:03:40.860> okay<00:03:41.459> many<00:03:41.879> of 00:03:42.050 --> 00:03:42.060 align:start position:0% happening behind the scenes okay many of 00:03:42.060 --> 00:03:44.270 align:start position:0% happening behind the scenes okay many of us<00:03:42.180> know<00:03:42.420> about<00:03:42.659> them<00:03:43.019> or<00:03:43.500> those<00:03:43.739> who<00:03:43.920> are<00:03:44.040> sort 00:03:44.270 --> 00:03:44.280 align:start position:0% us know about them or those who are sort 00:03:44.280 --> 00:03:46.490 align:start position:0% us know about them or those who are sort of<00:03:44.340> crypto<00:03:44.700> Savvy<00:03:45.180> but<00:03:45.599> those<00:03:45.840> outside<00:03:46.140> of 00:03:46.490 --> 00:03:46.500 align:start position:0% of crypto Savvy but those outside of 00:03:46.500 --> 00:03:48.350 align:start position:0% of crypto Savvy but those outside of this<00:03:46.680> room<00:03:46.860> outside<00:03:47.280> of<00:03:47.640> the<00:03:47.819> the<00:03:48.000> crypto 00:03:48.350 --> 00:03:48.360 align:start position:0% this room outside of the the crypto 00:03:48.360 --> 00:03:49.910 align:start position:0% this room outside of the the crypto bubble<00:03:48.720> were<00:03:48.780> definitely<00:03:49.140> not<00:03:49.379> aware<00:03:49.680> of<00:03:49.799> them 00:03:49.910 --> 00:03:49.920 align:start position:0% bubble were definitely not aware of them 00:03:49.920 --> 00:03:52.729 align:start position:0% bubble were definitely not aware of them so<00:03:50.760> our<00:03:51.120> our<00:03:51.299> goal<00:03:51.659> was<00:03:51.780> to 00:03:52.729 --> 00:03:52.739 align:start position:0% so our our goal was to 00:03:52.739 --> 00:03:54.949 align:start position:0% so our our goal was to find<00:03:53.400> them<00:03:53.700> and<00:03:54.000> quantify<00:03:54.480> them<00:03:54.659> and<00:03:54.840> that's 00:03:54.949 --> 00:03:54.959 align:start position:0% find them and quantify them and that's 00:03:54.959 --> 00:03:56.990 align:start position:0% find them and quantify them and that's that's<00:03:55.140> what<00:03:55.379> we<00:03:55.500> set<00:03:55.620> out<00:03:55.799> to<00:03:55.980> do 00:03:56.990 --> 00:03:57.000 align:start position:0% that's what we set out to do 00:03:57.000 --> 00:04:00.050 align:start position:0% that's what we set out to do so<00:03:57.480> we<00:03:57.659> did<00:03:57.840> a<00:03:58.080> a<00:03:58.379> mix<00:03:58.860> of<00:03:59.099> direct<00:03:59.400> interviews 00:04:00.050 --> 00:04:00.060 align:start position:0% so we did a a mix of direct interviews 00:04:00.060 --> 00:04:02.830 align:start position:0% so we did a a mix of direct interviews case<00:04:00.599> study<00:04:01.080> development 00:04:02.830 --> 00:04:02.840 align:start position:0% case study development 00:04:02.840 --> 00:04:06.830 align:start position:0% case study development surveys<00:04:04.220> and<00:04:05.220> also<00:04:05.459> the<00:04:05.700> other<00:04:05.879> uh<00:04:06.480> important 00:04:06.830 --> 00:04:06.840 align:start position:0% surveys and also the other uh important 00:04:06.840 --> 00:04:09.770 align:start position:0% surveys and also the other uh important part<00:04:07.080> with<00:04:07.379> this<00:04:07.680> particular<00:04:08.159> report<00:04:08.540> was<00:04:09.540> to 00:04:09.770 --> 00:04:09.780 align:start position:0% part with this particular report was to 00:04:09.780 --> 00:04:11.449 align:start position:0% part with this particular report was to be<00:04:09.959> able<00:04:10.080> to<00:04:10.200> educate<00:04:10.620> business<00:04:10.980> decision 00:04:11.449 --> 00:04:11.459 align:start position:0% be able to educate business decision 00:04:11.459 --> 00:04:13.990 align:start position:0% be able to educate business decision makers<00:04:11.879> about<00:04:12.180> how<00:04:12.540> to<00:04:12.720> think<00:04:12.900> about 00:04:13.990 --> 00:04:14.000 align:start position:0% makers about how to think about 00:04:14.000 --> 00:04:16.490 align:start position:0% makers about how to think about ethereum-based<00:04:15.000> deployments 00:04:16.490 --> 00:04:16.500 align:start position:0% ethereum-based deployments 00:04:16.500 --> 00:04:18.710 align:start position:0% ethereum-based deployments so<00:04:17.100> the<00:04:17.519> work<00:04:17.639> that<00:04:17.820> we<00:04:17.940> did<00:04:18.060> is<00:04:18.180> based<00:04:18.419> on<00:04:18.540> both 00:04:18.710 --> 00:04:18.720 align:start position:0% so the work that we did is based on both 00:04:18.720 --> 00:04:21.469 align:start position:0% so the work that we did is based on both quantitative<00:04:19.320> and<00:04:19.739> qualitative<00:04:20.160> research<00:04:20.699> we 00:04:21.469 --> 00:04:21.479 align:start position:0% quantitative and qualitative research we 00:04:21.479 --> 00:04:23.210 align:start position:0% quantitative and qualitative research we did<00:04:21.660> the<00:04:22.019> quantitative<00:04:22.440> research<00:04:22.860> where<00:04:23.040> I'll 00:04:23.210 --> 00:04:23.220 align:start position:0% did the quantitative research where I'll 00:04:23.220 --> 00:04:24.230 align:start position:0% did the quantitative research where I'll talk<00:04:23.340> about<00:04:23.460> that<00:04:23.639> a<00:04:23.759> little<00:04:23.820> bit<00:04:23.940> more<00:04:24.060> later 00:04:24.230 --> 00:04:24.240 align:start position:0% talk about that a little bit more later 00:04:24.240 --> 00:04:27.290 align:start position:0% talk about that a little bit more later but<00:04:24.540> the<00:04:25.020> point<00:04:25.199> is<00:04:25.380> that<00:04:25.740> we<00:04:26.460> focus<00:04:26.759> primarily 00:04:27.290 --> 00:04:27.300 align:start position:0% but the point is that we focus primarily 00:04:27.300 --> 00:04:29.930 align:start position:0% but the point is that we focus primarily on<00:04:27.540> the<00:04:27.660> qualitative<00:04:28.139> our<00:04:28.860> goal<00:04:29.160> was<00:04:29.220> to<00:04:29.460> was 00:04:29.930 --> 00:04:29.940 align:start position:0% on the qualitative our goal was to was 00:04:29.940 --> 00:04:32.450 align:start position:0% on the qualitative our goal was to was to<00:04:30.180> do<00:04:30.360> storytelling<00:04:31.080> based<00:04:31.620> on<00:04:31.740> case<00:04:31.979> studies 00:04:32.450 --> 00:04:32.460 align:start position:0% to do storytelling based on case studies 00:04:32.460 --> 00:04:33.710 align:start position:0% to do storytelling based on case studies and<00:04:32.699> interviews<00:04:33.180> and<00:04:33.360> when<00:04:33.419> I<00:04:33.600> say 00:04:33.710 --> 00:04:33.720 align:start position:0% and interviews and when I say 00:04:33.720 --> 00:04:35.810 align:start position:0% and interviews and when I say storytelling<00:04:34.440> I<00:04:34.919> mean<00:04:35.100> stories<00:04:35.460> that<00:04:35.639> make 00:04:35.810 --> 00:04:35.820 align:start position:0% storytelling I mean stories that make 00:04:35.820 --> 00:04:37.430 align:start position:0% storytelling I mean stories that make sense<00:04:36.060> to<00:04:36.240> businesses 00:04:37.430 --> 00:04:37.440 align:start position:0% sense to businesses 00:04:37.440 --> 00:04:39.170 align:start position:0% sense to businesses one<00:04:37.919> of<00:04:38.040> the<00:04:38.100> reasons<00:04:38.340> we<00:04:38.460> focus<00:04:38.699> so<00:04:38.880> much<00:04:39.060> on 00:04:39.170 --> 00:04:39.180 align:start position:0% one of the reasons we focus so much on 00:04:39.180 --> 00:04:42.290 align:start position:0% one of the reasons we focus so much on case<00:04:39.360> studies<00:04:40.220> is<00:04:41.220> you<00:04:41.699> know<00:04:41.820> everyone<00:04:42.000> in 00:04:42.290 --> 00:04:42.300 align:start position:0% case studies is you know everyone in 00:04:42.300 --> 00:04:43.790 align:start position:0% case studies is you know everyone in this<00:04:42.419> ecosystem<00:04:42.780> likes<00:04:43.259> to<00:04:43.320> ask<00:04:43.440> well<00:04:43.680> what 00:04:43.790 --> 00:04:43.800 align:start position:0% this ecosystem likes to ask well what 00:04:43.800 --> 00:04:44.990 align:start position:0% this ecosystem likes to ask well what are<00:04:43.919> the<00:04:44.040> use<00:04:44.100> cases<00:04:44.340> what<00:04:44.520> are<00:04:44.639> the<00:04:44.759> use<00:04:44.820> cases 00:04:44.990 --> 00:04:45.000 align:start position:0% are the use cases what are the use cases 00:04:45.000 --> 00:04:47.450 align:start position:0% are the use cases what are the use cases what<00:04:45.240> are<00:04:45.419> the<00:04:45.479> use<00:04:45.600> cases<00:04:45.960> use<00:04:46.740> cases<00:04:47.100> are<00:04:47.280> for 00:04:47.450 --> 00:04:47.460 align:start position:0% what are the use cases use cases are for 00:04:47.460 --> 00:04:49.610 align:start position:0% what are the use cases use cases are for sellers<00:04:47.820> case<00:04:48.479> studies<00:04:48.840> are<00:04:49.020> for<00:04:49.199> buyers 00:04:49.610 --> 00:04:49.620 align:start position:0% sellers case studies are for buyers 00:04:49.620 --> 00:04:51.710 align:start position:0% sellers case studies are for buyers buyers<00:04:50.580> don't<00:04:50.759> want<00:04:50.940> to<00:04:51.060> hear<00:04:51.120> what<00:04:51.419> you<00:04:51.540> could 00:04:51.710 --> 00:04:51.720 align:start position:0% buyers don't want to hear what you could 00:04:51.720 --> 00:04:52.490 align:start position:0% buyers don't want to hear what you could do 00:04:52.490 --> 00:04:52.500 align:start position:0% do 00:04:52.500 --> 00:04:54.890 align:start position:0% do buyers<00:04:52.919> want<00:04:53.160> to<00:04:53.280> hear<00:04:53.400> what<00:04:53.639> works<00:04:54.060> today<00:04:54.240> so 00:04:54.890 --> 00:04:54.900 align:start position:0% buyers want to hear what works today so 00:04:54.900 --> 00:04:57.170 align:start position:0% buyers want to hear what works today so that<00:04:55.080> was<00:04:55.259> one<00:04:55.500> of<00:04:55.620> the<00:04:55.740> the<00:04:56.100> important<00:04:56.820> goals 00:04:57.170 --> 00:04:57.180 align:start position:0% that was one of the the important goals 00:04:57.180 --> 00:05:00.350 align:start position:0% that was one of the the important goals that<00:04:57.300> drove<00:04:57.660> what<00:04:57.780> we<00:04:57.900> did 00:05:00.350 --> 00:05:00.360 align:start position:0% 00:05:00.360 --> 00:05:01.310 align:start position:0% um<00:05:00.479> so 00:05:01.310 --> 00:05:01.320 align:start position:0% um so 00:05:01.320 --> 00:05:03.350 align:start position:0% um so just<00:05:01.860> very<00:05:01.979> quickly<00:05:02.340> I'm<00:05:02.759> gonna<00:05:02.940> I'm<00:05:03.180> gonna 00:05:03.350 --> 00:05:03.360 align:start position:0% just very quickly I'm gonna I'm gonna 00:05:03.360 --> 00:05:05.330 align:start position:0% just very quickly I'm gonna I'm gonna walk<00:05:03.600> through<00:05:03.780> this<00:05:03.960> part<00:05:04.199> this<00:05:05.100> is<00:05:05.160> something 00:05:05.330 --> 00:05:05.340 align:start position:0% walk through this part this is something 00:05:05.340 --> 00:05:07.909 align:start position:0% walk through this part this is something that's<00:05:05.520> in<00:05:05.699> the<00:05:05.820> report<00:05:06.380> we<00:05:07.380> from<00:05:07.680> a<00:05:07.860> business 00:05:07.909 --> 00:05:07.919 align:start position:0% that's in the report we from a business 00:05:07.919 --> 00:05:10.490 align:start position:0% that's in the report we from a business perspective<00:05:08.580> we<00:05:09.479> describe<00:05:09.840> kind<00:05:10.020> of<00:05:10.139> the<00:05:10.320> the 00:05:10.490 --> 00:05:10.500 align:start position:0% perspective we describe kind of the the 00:05:10.500 --> 00:05:12.830 align:start position:0% perspective we describe kind of the the history<00:05:10.800> of<00:05:11.100> the<00:05:11.280> ethereum<00:05:11.699> platform<00:05:12.180> as 00:05:12.830 --> 00:05:12.840 align:start position:0% history of the ethereum platform as 00:05:12.840 --> 00:05:14.930 align:start position:0% history of the ethereum platform as having<00:05:13.139> three<00:05:13.380> main<00:05:13.620> phases<00:05:14.100> in<00:05:14.699> the<00:05:14.820> early 00:05:14.930 --> 00:05:14.940 align:start position:0% having three main phases in the early 00:05:14.940 --> 00:05:16.490 align:start position:0% having three main phases in the early days<00:05:15.240> of<00:05:15.600> of<00:05:15.840> course<00:05:15.960> there's<00:05:16.139> a<00:05:16.380> lot<00:05:16.440> of 00:05:16.490 --> 00:05:16.500 align:start position:0% days of of course there's a lot of 00:05:16.500 --> 00:05:18.650 align:start position:0% days of of course there's a lot of excitement<00:05:16.919> experimentation<00:05:17.820> with<00:05:18.240> you<00:05:18.600> know 00:05:18.650 --> 00:05:18.660 align:start position:0% excitement experimentation with you know 00:05:18.660 --> 00:05:20.990 align:start position:0% excitement experimentation with you know decentralize<00:05:19.440> all<00:05:19.620> the<00:05:19.800> things<00:05:20.040> and<00:05:20.880> there's 00:05:20.990 --> 00:05:21.000 align:start position:0% decentralize all the things and there's 00:05:21.000 --> 00:05:22.310 align:start position:0% decentralize all the things and there's a<00:05:21.180> lot<00:05:21.240> of<00:05:21.360> great<00:05:21.479> experimentation<00:05:22.080> that's 00:05:22.310 --> 00:05:22.320 align:start position:0% a lot of great experimentation that's 00:05:22.320 --> 00:05:24.770 align:start position:0% a lot of great experimentation that's still<00:05:22.560> happening<00:05:22.919> of<00:05:23.280> course 00:05:24.770 --> 00:05:24.780 align:start position:0% still happening of course 00:05:24.780 --> 00:05:27.290 align:start position:0% still happening of course um<00:05:24.840> but<00:05:25.440> there<00:05:26.220> was<00:05:26.340> a<00:05:26.460> realization<00:05:26.880> pretty 00:05:27.290 --> 00:05:27.300 align:start position:0% um but there was a realization pretty 00:05:27.300 --> 00:05:29.090 align:start position:0% um but there was a realization pretty early<00:05:27.539> on<00:05:27.840> that<00:05:28.440> there<00:05:28.860> were<00:05:28.979> some 00:05:29.090 --> 00:05:29.100 align:start position:0% early on that there were some 00:05:29.100 --> 00:05:31.189 align:start position:0% early on that there were some limitations<00:05:29.580> from<00:05:30.000> a<00:05:30.240> business<00:05:30.419> perspective 00:05:31.189 --> 00:05:31.199 align:start position:0% limitations from a business perspective 00:05:31.199 --> 00:05:33.529 align:start position:0% limitations from a business perspective in<00:05:31.680> using<00:05:32.039> the<00:05:32.100> public<00:05:32.220> mainnet<00:05:32.880> and<00:05:33.360> in 00:05:33.529 --> 00:05:33.539 align:start position:0% in using the public mainnet and in 00:05:33.539 --> 00:05:34.790 align:start position:0% in using the public mainnet and in particular<00:05:33.840> the<00:05:34.139> three<00:05:34.320> that<00:05:34.500> we<00:05:34.680> always 00:05:34.790 --> 00:05:34.800 align:start position:0% particular the three that we always 00:05:34.800 --> 00:05:37.070 align:start position:0% particular the three that we always talked<00:05:35.100> about<00:05:35.160> the<00:05:35.400> three<00:05:35.580> p's<00:05:36.060> were<00:05:36.600> privacy 00:05:37.070 --> 00:05:37.080 align:start position:0% talked about the three p's were privacy 00:05:37.080 --> 00:05:39.350 align:start position:0% talked about the three p's were privacy permissioning<00:05:37.800> and<00:05:38.100> performance<00:05:38.580> those<00:05:39.240> were 00:05:39.350 --> 00:05:39.360 align:start position:0% permissioning and performance those were 00:05:39.360 --> 00:05:41.810 align:start position:0% permissioning and performance those were things<00:05:39.660> that<00:05:40.020> the<00:05:40.199> the<00:05:40.440> broader<00:05:41.100> public 00:05:41.810 --> 00:05:41.820 align:start position:0% things that the the broader public 00:05:41.820 --> 00:05:44.150 align:start position:0% things that the the broader public Community<00:05:42.180> was<00:05:42.720> not<00:05:43.020> interested<00:05:43.560> in<00:05:43.800> focusing 00:05:44.150 --> 00:05:44.160 align:start position:0% Community was not interested in focusing 00:05:44.160 --> 00:05:46.490 align:start position:0% Community was not interested in focusing on<00:05:44.400> at<00:05:44.580> the<00:05:44.759> time<00:05:44.880> but<00:05:45.479> but<00:05:45.840> for<00:05:46.080> businesses 00:05:46.490 --> 00:05:46.500 align:start position:0% on at the time but but for businesses 00:05:46.500 --> 00:05:48.950 align:start position:0% on at the time but but for businesses are<00:05:46.740> just<00:05:47.039> absolutely<00:05:47.460> essential<00:05:47.940> okay<00:05:48.660> and 00:05:48.950 --> 00:05:48.960 align:start position:0% are just absolutely essential okay and 00:05:48.960 --> 00:05:51.050 align:start position:0% are just absolutely essential okay and that<00:05:49.080> actually<00:05:49.259> led<00:05:49.620> to<00:05:49.740> a<00:05:49.919> focus<00:05:50.160> on<00:05:50.520> private 00:05:51.050 --> 00:05:51.060 align:start position:0% that actually led to a focus on private 00:05:51.060 --> 00:05:53.870 align:start position:0% that actually led to a focus on private blockchains<00:05:51.660> private<00:05:52.500> Consortium<00:05:52.979> networks 00:05:53.870 --> 00:05:53.880 align:start position:0% blockchains private Consortium networks 00:05:53.880 --> 00:05:56.090 align:start position:0% blockchains private Consortium networks um<00:05:53.940> using<00:05:54.240> ethereum<00:05:54.720> or<00:05:55.020> or<00:05:55.259> other<00:05:55.620> other 00:05:56.090 --> 00:05:56.100 align:start position:0% um using ethereum or or other other 00:05:56.100 --> 00:05:59.090 align:start position:0% um using ethereum or or other other Technologies<00:05:56.759> now<00:05:57.479> as<00:05:57.780> we<00:05:57.900> all<00:05:58.080> know<00:05:58.259> there 00:05:59.090 --> 00:05:59.100 align:start position:0% Technologies now as we all know there 00:05:59.100 --> 00:06:01.670 align:start position:0% Technologies now as we all know there has<00:05:59.220> been<00:05:59.460> a<00:05:59.759> great<00:05:59.880> Revival<00:06:00.300> of<00:06:00.600> interest<00:06:00.720> in 00:06:01.670 --> 00:06:01.680 align:start position:0% has been a great Revival of interest in 00:06:01.680 --> 00:06:03.950 align:start position:0% has been a great Revival of interest in public<00:06:01.860> blockchain<00:06:02.940> and<00:06:03.479> this<00:06:03.660> is<00:06:03.780> actually 00:06:03.950 --> 00:06:03.960 align:start position:0% public blockchain and this is actually 00:06:03.960 --> 00:06:06.529 align:start position:0% public blockchain and this is actually from<00:06:04.259> a<00:06:04.620> business<00:06:04.740> perspective<00:06:05.400> also<00:06:05.940> that's 00:06:06.529 --> 00:06:06.539 align:start position:0% from a business perspective also that's 00:06:06.539 --> 00:06:08.150 align:start position:0% from a business perspective also that's driven<00:06:06.900> by<00:06:07.199> of<00:06:07.380> course<00:06:07.500> what<00:06:07.680> we've<00:06:07.860> seen<00:06:07.979> with 00:06:08.150 --> 00:06:08.160 align:start position:0% driven by of course what we've seen with 00:06:08.160 --> 00:06:10.610 align:start position:0% driven by of course what we've seen with consumer<00:06:08.580> defy<00:06:09.060> which<00:06:09.360> is<00:06:09.600> uh<00:06:10.199> demonstrated 00:06:10.610 --> 00:06:10.620 align:start position:0% consumer defy which is uh demonstrated 00:06:10.620 --> 00:06:12.290 align:start position:0% consumer defy which is uh demonstrated that<00:06:10.860> decentralized<00:06:11.520> business<00:06:11.639> models<00:06:12.120> can 00:06:12.290 --> 00:06:12.300 align:start position:0% that decentralized business models can 00:06:12.300 --> 00:06:13.490 align:start position:0% that decentralized business models can work 00:06:13.490 --> 00:06:13.500 align:start position:0% work 00:06:13.500 --> 00:06:15.469 align:start position:0% work um<00:06:13.560> also<00:06:13.800> nfts<00:06:14.340> but<00:06:14.520> also<00:06:14.699> some<00:06:14.880> technological 00:06:15.469 --> 00:06:15.479 align:start position:0% um also nfts but also some technological 00:06:15.479 --> 00:06:16.850 align:start position:0% um also nfts but also some technological improvements<00:06:16.020> and<00:06:16.199> I'll<00:06:16.320> I'll<00:06:16.500> talk<00:06:16.740> about 00:06:16.850 --> 00:06:16.860 align:start position:0% improvements and I'll I'll talk about 00:06:16.860 --> 00:06:19.490 align:start position:0% improvements and I'll I'll talk about that<00:06:17.100> a<00:06:17.280> little<00:06:17.340> bit<00:06:17.520> more<00:06:17.699> later<00:06:18.240> on 00:06:19.490 --> 00:06:19.500 align:start position:0% that a little bit more later on 00:06:19.500 --> 00:06:22.070 align:start position:0% that a little bit more later on so<00:06:20.460> um<00:06:20.460> before<00:06:20.880> I 00:06:22.070 --> 00:06:22.080 align:start position:0% so um before I 00:06:22.080 --> 00:06:23.510 align:start position:0% so um before I um<00:06:22.139> before<00:06:22.440> I<00:06:22.620> talk<00:06:22.800> about<00:06:22.919> what's<00:06:23.160> on<00:06:23.400> this 00:06:23.510 --> 00:06:23.520 align:start position:0% um before I talk about what's on this 00:06:23.520 --> 00:06:25.010 align:start position:0% um before I talk about what's on this slide<00:06:23.699> I<00:06:23.880> want<00:06:24.060> to<00:06:24.120> mention<00:06:24.300> that<00:06:24.539> from<00:06:24.840> this 00:06:25.010 --> 00:06:25.020 align:start position:0% slide I want to mention that from this 00:06:25.020 --> 00:06:27.590 align:start position:0% slide I want to mention that from this point<00:06:25.139> on<00:06:25.380> everything<00:06:26.280> that<00:06:26.639> I<00:06:26.880> describe<00:06:27.300> is 00:06:27.590 --> 00:06:27.600 align:start position:0% point on everything that I describe is 00:06:27.600 --> 00:06:29.749 align:start position:0% point on everything that I describe is being<00:06:27.840> viewed<00:06:28.259> through<00:06:28.500> a<00:06:28.800> business<00:06:29.039> lens 00:06:29.749 --> 00:06:29.759 align:start position:0% being viewed through a business lens 00:06:29.759 --> 00:06:33.350 align:start position:0% being viewed through a business lens okay<00:06:30.539> so<00:06:31.139> when<00:06:31.740> I<00:06:31.919> when<00:06:32.160> I<00:06:32.340> show<00:06:32.520> Circles<00:06:33.120> of 00:06:33.350 --> 00:06:33.360 align:start position:0% okay so when I when I show Circles of 00:06:33.360 --> 00:06:35.090 align:start position:0% okay so when I when I show Circles of certain<00:06:33.539> sizes<00:06:34.020> and<00:06:34.199> so<00:06:34.319> on<00:06:34.380> this<00:06:34.560> is<00:06:34.680> based<00:06:35.039> on 00:06:35.090 --> 00:06:35.100 align:start position:0% certain sizes and so on this is based on 00:06:35.100 --> 00:06:37.430 align:start position:0% certain sizes and so on this is based on our<00:06:35.400> particular<00:06:35.759> data<00:06:36.240> set 00:06:37.430 --> 00:06:37.440 align:start position:0% our particular data set 00:06:37.440 --> 00:06:39.770 align:start position:0% our particular data set what<00:06:37.979> we<00:06:38.100> did<00:06:38.280> is<00:06:38.460> we<00:06:38.639> we<00:06:38.880> collected<00:06:39.360> a<00:06:39.539> data 00:06:39.770 --> 00:06:39.780 align:start position:0% what we did is we we collected a data 00:06:39.780 --> 00:06:42.050 align:start position:0% what we did is we we collected a data set<00:06:39.900> that<00:06:40.139> was<00:06:40.259> restricted<00:06:40.740> to<00:06:41.039> down<00:06:41.759> to<00:06:41.940> about 00:06:42.050 --> 00:06:42.060 align:start position:0% set that was restricted to down to about 00:06:42.060 --> 00:06:45.590 align:start position:0% set that was restricted to down to about 118<00:06:42.979> business<00:06:43.979> oriented<00:06:44.580> ethereum<00:06:45.120> projects 00:06:45.590 --> 00:06:45.600 align:start position:0% 118 business oriented ethereum projects 00:06:45.600 --> 00:06:47.390 align:start position:0% 118 business oriented ethereum projects these<00:06:46.199> are<00:06:46.259> projects<00:06:46.680> these<00:06:46.979> are<00:06:47.039> companies 00:06:47.390 --> 00:06:47.400 align:start position:0% these are projects these are companies 00:06:47.400 --> 00:06:49.189 align:start position:0% these are projects these are companies or<00:06:47.580> projects<00:06:47.940> that<00:06:48.120> are<00:06:48.300> active<00:06:48.600> now<00:06:48.840> have 00:06:49.189 --> 00:06:49.199 align:start position:0% or projects that are active now have 00:06:49.199 --> 00:06:51.409 align:start position:0% or projects that are active now have live<00:06:49.500> teams<00:06:50.039> and<00:06:50.520> are<00:06:50.639> developing<00:06:51.060> solutions 00:06:51.409 --> 00:06:51.419 align:start position:0% live teams and are developing solutions 00:06:51.419 --> 00:06:53.689 align:start position:0% live teams and are developing solutions for<00:06:51.660> traditional<00:06:52.080> business<00:06:52.319> problems 00:06:53.689 --> 00:06:53.699 align:start position:0% for traditional business problems 00:06:53.699 --> 00:06:55.790 align:start position:0% for traditional business problems so<00:06:54.120> the<00:06:54.419> data<00:06:54.720> set<00:06:54.840> is<00:06:55.020> somewhat<00:06:55.380> small<00:06:55.560> and 00:06:55.790 --> 00:06:55.800 align:start position:0% so the data set is somewhat small and 00:06:55.800 --> 00:06:57.710 align:start position:0% so the data set is somewhat small and eclectic<00:06:56.280> and<00:06:56.460> keep<00:06:56.639> that<00:06:56.819> in<00:06:56.940> mind<00:06:57.120> when<00:06:57.539> I 00:06:57.710 --> 00:06:57.720 align:start position:0% eclectic and keep that in mind when I 00:06:57.720 --> 00:06:59.749 align:start position:0% eclectic and keep that in mind when I when<00:06:58.199> I<00:06:58.380> draw<00:06:58.500> some<00:06:58.800> conclusions<00:06:59.220> like<00:06:59.520> I<00:06:59.639> do 00:06:59.749 --> 00:06:59.759 align:start position:0% when I draw some conclusions like I do 00:06:59.759 --> 00:07:01.610 align:start position:0% when I draw some conclusions like I do on<00:06:59.940> this<00:07:00.120> particular<00:07:00.419> slide 00:07:01.610 --> 00:07:01.620 align:start position:0% on this particular slide 00:07:01.620 --> 00:07:04.189 align:start position:0% on this particular slide um yes<00:07:01.860> please<00:07:02.100> reduce<00:07:02.340> the<00:07:02.639> font<00:07:02.819> size<00:07:03.199> back 00:07:04.189 --> 00:07:04.199 align:start position:0% um yes please reduce the font size back 00:07:04.199 --> 00:07:07.909 align:start position:0% um yes please reduce the font size back down<00:07:04.860> one<00:07:05.100> or<00:07:05.280> two<00:07:05.400> thank<00:07:06.180> you<00:07:06.300> on<00:07:06.539> the<00:07:06.720> notes 00:07:07.909 --> 00:07:07.919 align:start position:0% down one or two thank you on the notes 00:07:07.919 --> 00:07:09.590 align:start position:0% down one or two thank you on the notes um 00:07:09.590 --> 00:07:09.600 align:start position:0% um 00:07:09.600 --> 00:07:12.710 align:start position:0% um okay 00:07:12.710 --> 00:07:12.720 align:start position:0% 00:07:12.720 --> 00:07:15.170 align:start position:0% stop<00:07:13.259> there 00:07:15.170 --> 00:07:15.180 align:start position:0% stop there 00:07:15.180 --> 00:07:18.110 align:start position:0% stop there thanks<00:07:16.199> um<00:07:16.199> so<00:07:16.860> uh<00:07:17.220> okay<00:07:17.400> so<00:07:17.639> on<00:07:17.759> the<00:07:17.880> left<00:07:17.940> side 00:07:18.110 --> 00:07:18.120 align:start position:0% thanks um so uh okay so on the left side 00:07:18.120 --> 00:07:19.189 align:start position:0% thanks um so uh okay so on the left side here<00:07:18.300> what<00:07:18.479> we<00:07:18.600> have<00:07:18.720> is<00:07:18.900> the<00:07:19.080> business 00:07:19.189 --> 00:07:19.199 align:start position:0% here what we have is the business 00:07:19.199 --> 00:07:21.830 align:start position:0% here what we have is the business projects<00:07:19.860> organized<00:07:20.460> by<00:07:20.639> industry 00:07:21.830 --> 00:07:21.840 align:start position:0% projects organized by industry 00:07:21.840 --> 00:07:23.990 align:start position:0% projects organized by industry and<00:07:22.259> the<00:07:22.380> Lion's<00:07:22.800> Share<00:07:22.919> of<00:07:23.160> course<00:07:23.280> has<00:07:23.819> been 00:07:23.990 --> 00:07:24.000 align:start position:0% and the Lion's Share of course has been 00:07:24.000 --> 00:07:25.790 align:start position:0% and the Lion's Share of course has been an<00:07:24.180> infrastructure<00:07:24.840> and<00:07:25.199> fintech 00:07:25.790 --> 00:07:25.800 align:start position:0% an infrastructure and fintech 00:07:25.800 --> 00:07:28.730 align:start position:0% an infrastructure and fintech unsurprisingly<00:07:26.720> we're<00:07:27.720> basically<00:07:28.139> still<00:07:28.440> in 00:07:28.730 --> 00:07:28.740 align:start position:0% unsurprisingly we're basically still in 00:07:28.740 --> 00:07:30.469 align:start position:0% unsurprisingly we're basically still in in<00:07:29.039> the<00:07:29.220> stage<00:07:29.460> of<00:07:29.639> building<00:07:29.880> the<00:07:30.180> platform 00:07:30.469 --> 00:07:30.479 align:start position:0% in the stage of building the platform 00:07:30.479 --> 00:07:32.629 align:start position:0% in the stage of building the platform and<00:07:30.780> selling<00:07:31.080> picks<00:07:31.380> and<00:07:31.500> shovels<00:07:31.919> okay<00:07:32.460> I 00:07:32.629 --> 00:07:32.639 align:start position:0% and selling picks and shovels okay I 00:07:32.639 --> 00:07:33.890 align:start position:0% and selling picks and shovels okay I mean<00:07:32.759> that<00:07:32.940> is<00:07:33.060> really<00:07:33.240> where<00:07:33.479> the<00:07:33.599> industry 00:07:33.890 --> 00:07:33.900 align:start position:0% mean that is really where the industry 00:07:33.900 --> 00:07:35.330 align:start position:0% mean that is really where the industry is<00:07:34.080> particularly<00:07:34.680> from<00:07:34.919> a<00:07:35.160> business 00:07:35.330 --> 00:07:35.340 align:start position:0% is particularly from a business 00:07:35.340 --> 00:07:36.830 align:start position:0% is particularly from a business perspective 00:07:36.830 --> 00:07:36.840 align:start position:0% perspective 00:07:36.840 --> 00:07:38.749 align:start position:0% perspective now<00:07:37.319> if<00:07:37.560> you<00:07:37.620> look<00:07:37.740> at<00:07:37.860> use<00:07:38.099> cases<00:07:38.400> on<00:07:38.639> the 00:07:38.749 --> 00:07:38.759 align:start position:0% now if you look at use cases on the 00:07:38.759 --> 00:07:40.670 align:start position:0% now if you look at use cases on the right<00:07:38.940> side<00:07:39.180> most<00:07:39.599> of<00:07:39.780> the<00:07:39.900> activity<00:07:40.199> is<00:07:40.440> in 00:07:40.670 --> 00:07:40.680 align:start position:0% right side most of the activity is in 00:07:40.680 --> 00:07:42.830 align:start position:0% right side most of the activity is in software<00:07:41.039> development<00:07:41.520> and<00:07:42.000> fintech<00:07:42.599> which 00:07:42.830 --> 00:07:42.840 align:start position:0% software development and fintech which 00:07:42.840 --> 00:07:44.809 align:start position:0% software development and fintech which of<00:07:42.960> course<00:07:43.080> aligns<00:07:43.560> with<00:07:43.740> what<00:07:44.340> I<00:07:44.520> just<00:07:44.639> said 00:07:44.809 --> 00:07:44.819 align:start position:0% of course aligns with what I just said 00:07:44.819 --> 00:07:47.150 align:start position:0% of course aligns with what I just said and<00:07:45.120> so<00:07:45.300> again<00:07:45.720> it's<00:07:46.139> still<00:07:46.380> early<00:07:46.740> stages 00:07:47.150 --> 00:07:47.160 align:start position:0% and so again it's still early stages 00:07:47.160 --> 00:07:50.170 align:start position:0% and so again it's still early stages there's<00:07:47.940> a<00:07:48.180> lot<00:07:48.300> of<00:07:48.479> Need<00:07:48.720> for<00:07:49.020> building<00:07:49.319> core 00:07:50.170 --> 00:07:50.180 align:start position:0% there's a lot of Need for building core 00:07:50.180 --> 00:07:54.589 align:start position:0% there's a lot of Need for building core materials<00:07:51.180> yet 00:07:54.589 --> 00:07:54.599 align:start position:0% 00:07:54.599 --> 00:07:55.370 align:start position:0% foreign 00:07:55.370 --> 00:07:55.380 align:start position:0% foreign 00:07:55.380 --> 00:07:57.290 align:start position:0% foreign so<00:07:55.919> I<00:07:56.160> just<00:07:56.280> wanted<00:07:56.400> to<00:07:56.580> throw<00:07:56.759> this<00:07:56.940> up<00:07:57.060> some 00:07:57.290 --> 00:07:57.300 align:start position:0% so I just wanted to throw this up some 00:07:57.300 --> 00:07:59.809 align:start position:0% so I just wanted to throw this up some people<00:07:57.419> like<00:07:57.599> looking<00:07:57.840> at<00:07:58.080> logos<00:07:58.580> this<00:07:59.580> is<00:07:59.699> a 00:07:59.809 --> 00:07:59.819 align:start position:0% people like looking at logos this is a 00:07:59.819 --> 00:08:01.550 align:start position:0% people like looking at logos this is a subset<00:08:00.180> of<00:08:00.479> the<00:08:00.660> companies<00:08:00.960> and<00:08:01.139> projects 00:08:01.550 --> 00:08:01.560 align:start position:0% subset of the companies and projects 00:08:01.560 --> 00:08:03.529 align:start position:0% subset of the companies and projects that<00:08:01.800> are<00:08:01.919> in<00:08:02.099> our<00:08:02.220> database<00:08:02.580> I'm<00:08:03.240> not<00:08:03.419> going 00:08:03.529 --> 00:08:03.539 align:start position:0% that are in our database I'm not going 00:08:03.539 --> 00:08:05.029 align:start position:0% that are in our database I'm not going to<00:08:03.660> talk<00:08:03.780> about<00:08:03.900> it<00:08:04.139> this<00:08:04.319> isn't<00:08:04.620> exhaustive 00:08:05.029 --> 00:08:05.039 align:start position:0% to talk about it this isn't exhaustive 00:08:05.039 --> 00:08:07.010 align:start position:0% to talk about it this isn't exhaustive but<00:08:05.220> just<00:08:05.400> to<00:08:05.520> give<00:08:05.580> you<00:08:05.699> an<00:08:05.880> idea<00:08:06.120> of<00:08:06.300> of<00:08:06.599> uh 00:08:07.010 --> 00:08:07.020 align:start position:0% but just to give you an idea of of uh 00:08:07.020 --> 00:08:08.870 align:start position:0% but just to give you an idea of of uh some<00:08:07.259> of<00:08:07.380> the<00:08:07.500> the<00:08:07.860> companies<00:08:08.280> and<00:08:08.460> projects 00:08:08.870 --> 00:08:08.880 align:start position:0% some of the the companies and projects 00:08:08.880 --> 00:08:12.469 align:start position:0% some of the the companies and projects that<00:08:09.120> showed<00:08:09.360> up<00:08:09.479> in<00:08:09.660> that<00:08:09.840> list<00:08:10.139> of<00:08:10.319> 118 00:08:12.469 --> 00:08:12.479 align:start position:0% that showed up in that list of 118 00:08:12.479 --> 00:08:15.050 align:start position:0% that showed up in that list of 118 now<00:08:13.080> one<00:08:13.919> of<00:08:14.039> the<00:08:14.099> things<00:08:14.220> we<00:08:14.400> wanted<00:08:14.639> to<00:08:14.880> do 00:08:15.050 --> 00:08:15.060 align:start position:0% now one of the things we wanted to do 00:08:15.060 --> 00:08:17.450 align:start position:0% now one of the things we wanted to do was<00:08:15.599> uh<00:08:16.199> well<00:08:16.380> look<00:08:16.560> if<00:08:16.860> we're<00:08:16.979> gonna<00:08:17.099> if<00:08:17.400> we're 00:08:17.450 --> 00:08:17.460 align:start position:0% was uh well look if we're gonna if we're 00:08:17.460 --> 00:08:19.249 align:start position:0% was uh well look if we're gonna if we're going<00:08:17.580> to<00:08:17.639> put<00:08:17.759> out<00:08:17.880> a<00:08:18.060> report<00:08:18.240> on<00:08:18.960> business 00:08:19.249 --> 00:08:19.259 align:start position:0% going to put out a report on business 00:08:19.259 --> 00:08:21.950 align:start position:0% going to put out a report on business Readiness<00:08:19.979> of<00:08:20.340> ethereum<00:08:20.879> we<00:08:21.539> have<00:08:21.660> to<00:08:21.780> Define 00:08:21.950 --> 00:08:21.960 align:start position:0% Readiness of ethereum we have to Define 00:08:21.960 --> 00:08:24.469 align:start position:0% Readiness of ethereum we have to Define what<00:08:22.379> business<00:08:22.560> Readiness<00:08:23.220> means<00:08:23.580> okay<00:08:24.240> so 00:08:24.469 --> 00:08:24.479 align:start position:0% what business Readiness means okay so 00:08:24.479 --> 00:08:25.850 align:start position:0% what business Readiness means okay so that<00:08:24.660> was<00:08:24.780> our<00:08:24.960> first<00:08:25.139> goal<00:08:25.440> was<00:08:25.560> to<00:08:25.740> figure 00:08:25.850 --> 00:08:25.860 align:start position:0% that was our first goal was to figure 00:08:25.860 --> 00:08:27.650 align:start position:0% that was our first goal was to figure that<00:08:26.099> out<00:08:26.280> and<00:08:26.639> through<00:08:26.819> the<00:08:27.000> interviews<00:08:27.479> that 00:08:27.650 --> 00:08:27.660 align:start position:0% that out and through the interviews that 00:08:27.660 --> 00:08:28.969 align:start position:0% that out and through the interviews that we<00:08:27.840> did 00:08:28.969 --> 00:08:28.979 align:start position:0% we did 00:08:28.979 --> 00:08:31.850 align:start position:0% we did we<00:08:29.580> came<00:08:29.819> up<00:08:29.940> with<00:08:30.300> a<00:08:30.840> way<00:08:31.199> to<00:08:31.379> define<00:08:31.500> it<00:08:31.740> that 00:08:31.850 --> 00:08:31.860 align:start position:0% we came up with a way to define it that 00:08:31.860 --> 00:08:34.610 align:start position:0% we came up with a way to define it that we<00:08:32.039> believe<00:08:32.159> is<00:08:32.399> is<00:08:32.700> useful<00:08:33.180> for<00:08:33.539> business<00:08:33.779> so 00:08:34.610 --> 00:08:34.620 align:start position:0% we believe is is useful for business so 00:08:34.620 --> 00:08:36.469 align:start position:0% we believe is is useful for business so our<00:08:34.800> goal<00:08:35.159> keep<00:08:35.399> in<00:08:35.580> mind<00:08:35.760> with<00:08:36.060> this<00:08:36.240> report 00:08:36.469 --> 00:08:36.479 align:start position:0% our goal keep in mind with this report 00:08:36.479 --> 00:08:39.170 align:start position:0% our goal keep in mind with this report is<00:08:37.080> to<00:08:37.919> always<00:08:38.099> to<00:08:38.339> do<00:08:38.520> two<00:08:38.700> things<00:08:38.940> and 00:08:39.170 --> 00:08:39.180 align:start position:0% is to always to do two things and 00:08:39.180 --> 00:08:41.990 align:start position:0% is to always to do two things and education<00:08:39.659> is<00:08:39.899> one<00:08:40.140> of<00:08:40.200> those<00:08:40.380> parts<00:08:40.640> so<00:08:41.640> we 00:08:41.990 --> 00:08:42.000 align:start position:0% education is one of those parts so we 00:08:42.000 --> 00:08:44.449 align:start position:0% education is one of those parts so we wanted<00:08:42.120> to<00:08:42.300> make<00:08:42.419> sure<00:08:42.539> to<00:08:42.779> educate<00:08:43.260> people 00:08:44.449 --> 00:08:44.459 align:start position:0% wanted to make sure to educate people 00:08:44.459 --> 00:08:46.430 align:start position:0% wanted to make sure to educate people and<00:08:44.880> we<00:08:45.060> also<00:08:45.300> wanted<00:08:45.420> to<00:08:45.600> give<00:08:45.720> businesses<00:08:46.260> a 00:08:46.430 --> 00:08:46.440 align:start position:0% and we also wanted to give businesses a 00:08:46.440 --> 00:08:48.889 align:start position:0% and we also wanted to give businesses a tool<00:08:46.740> as<00:08:47.040> they<00:08:47.220> evaluate<00:08:47.820> uh<00:08:48.420> ethereum 00:08:48.889 --> 00:08:48.899 align:start position:0% tool as they evaluate uh ethereum 00:08:48.899 --> 00:08:52.009 align:start position:0% tool as they evaluate uh ethereum technology<00:08:49.500> and<00:08:49.800> deployment<00:08:50.160> possibilities 00:08:52.009 --> 00:08:52.019 align:start position:0% technology and deployment possibilities 00:08:52.019 --> 00:08:53.470 align:start position:0% technology and deployment possibilities so<00:08:52.320> we<00:08:52.440> developed<00:08:52.800> what<00:08:52.980> we<00:08:53.100> call<00:08:53.279> our 00:08:53.470 --> 00:08:53.480 align:start position:0% so we developed what we call our 00:08:53.480 --> 00:08:56.990 align:start position:0% so we developed what we call our ethereum<00:08:54.480> business<00:08:54.720> Readiness<00:08:55.320> framework 00:08:56.990 --> 00:08:57.000 align:start position:0% ethereum business Readiness framework 00:08:57.000 --> 00:08:59.090 align:start position:0% ethereum business Readiness framework um<00:08:57.060> and<00:08:57.420> we<00:08:57.660> think<00:08:57.779> this<00:08:58.140> is<00:08:58.320> the<00:08:58.860> first 00:08:59.090 --> 00:08:59.100 align:start position:0% um and we think this is the first 00:08:59.100 --> 00:09:00.410 align:start position:0% um and we think this is the first attempt 00:09:00.410 --> 00:09:00.420 align:start position:0% attempt 00:09:00.420 --> 00:09:03.290 align:start position:0% attempt that<00:09:01.019> we're<00:09:01.140> aware<00:09:01.440> of<00:09:01.620> to<00:09:01.980> do<00:09:02.220> this<00:09:02.519> in<00:09:03.120> an<00:09:03.240> in 00:09:03.290 --> 00:09:03.300 align:start position:0% that we're aware of to do this in an in 00:09:03.300 --> 00:09:05.750 align:start position:0% that we're aware of to do this in an in a<00:09:03.660> neutral<00:09:03.959> way<00:09:04.200> okay<00:09:04.500> so<00:09:04.920> we're<00:09:05.220> not<00:09:05.399> selling 00:09:05.750 --> 00:09:05.760 align:start position:0% a neutral way okay so we're not selling 00:09:05.760 --> 00:09:07.070 align:start position:0% a neutral way okay so we're not selling anything<00:09:06.000> in<00:09:06.300> particular<00:09:06.600> other<00:09:06.839> than 00:09:07.070 --> 00:09:07.080 align:start position:0% anything in particular other than 00:09:07.080 --> 00:09:09.290 align:start position:0% anything in particular other than ethereum<00:09:07.680> of<00:09:08.040> course<00:09:08.160> right 00:09:09.290 --> 00:09:09.300 align:start position:0% ethereum of course right 00:09:09.300 --> 00:09:09.889 align:start position:0% ethereum of course right um 00:09:09.889 --> 00:09:09.899 align:start position:0% um 00:09:09.899 --> 00:09:11.750 align:start position:0% um so<00:09:10.380> what<00:09:10.500> we<00:09:10.680> ended<00:09:10.920> up<00:09:10.980> with<00:09:11.160> is<00:09:11.459> seven 00:09:11.750 --> 00:09:11.760 align:start position:0% so what we ended up with is seven 00:09:11.760 --> 00:09:13.430 align:start position:0% so what we ended up with is seven technical<00:09:12.180> criteria<00:09:12.720> which<00:09:12.899> you'll<00:09:13.140> see<00:09:13.260> in 00:09:13.430 --> 00:09:13.440 align:start position:0% technical criteria which you'll see in 00:09:13.440 --> 00:09:15.050 align:start position:0% technical criteria which you'll see in the<00:09:13.560> the<00:09:13.680> coming<00:09:13.920> slides 00:09:15.050 --> 00:09:15.060 align:start position:0% the the coming slides 00:09:15.060 --> 00:09:17.810 align:start position:0% the the coming slides and<00:09:15.480> three<00:09:15.660> non-technical<00:09:16.380> criteria<00:09:17.040> with 00:09:17.810 --> 00:09:17.820 align:start position:0% and three non-technical criteria with 00:09:17.820 --> 00:09:20.210 align:start position:0% and three non-technical criteria with some<00:09:18.000> detailed<00:09:18.420> definitions<00:09:19.140> again<00:09:19.860> who's 00:09:20.210 --> 00:09:20.220 align:start position:0% some detailed definitions again who's 00:09:20.220 --> 00:09:21.829 align:start position:0% some detailed definitions again who's whose<00:09:20.640> goal<00:09:20.880> is<00:09:20.940> to<00:09:21.120> educate<00:09:21.480> a<00:09:21.660> business 00:09:21.829 --> 00:09:21.839 align:start position:0% whose goal is to educate a business 00:09:21.839 --> 00:09:23.930 align:start position:0% whose goal is to educate a business audience<00:09:22.320> and<00:09:23.220> through<00:09:23.459> this<00:09:23.580> we<00:09:23.760> believe 00:09:23.930 --> 00:09:23.940 align:start position:0% audience and through this we believe 00:09:23.940 --> 00:09:25.250 align:start position:0% audience and through this we believe that<00:09:24.180> businesses<00:09:24.540> can<00:09:24.720> learn<00:09:24.899> a<00:09:25.019> lot<00:09:25.140> about 00:09:25.250 --> 00:09:25.260 align:start position:0% that businesses can learn a lot about 00:09:25.260 --> 00:09:27.050 align:start position:0% that businesses can learn a lot about what<00:09:25.500> is<00:09:25.620> important<00:09:26.040> and<00:09:26.519> what<00:09:26.760> to<00:09:26.880> think 00:09:27.050 --> 00:09:27.060 align:start position:0% what is important and what to think 00:09:27.060 --> 00:09:29.389 align:start position:0% what is important and what to think about<00:09:27.300> as<00:09:27.959> they<00:09:28.560> um<00:09:28.620> as<00:09:28.860> they're<00:09:28.980> considering 00:09:29.389 --> 00:09:29.399 align:start position:0% about as they um as they're considering 00:09:29.399 --> 00:09:30.889 align:start position:0% about as they um as they're considering deployments 00:09:30.889 --> 00:09:30.899 align:start position:0% deployments 00:09:30.899 --> 00:09:33.530 align:start position:0% deployments okay<00:09:31.500> so<00:09:32.040> down<00:09:32.640> the<00:09:32.820> left<00:09:32.940> side<00:09:33.120> here<00:09:33.360> and<00:09:33.420> I 00:09:33.530 --> 00:09:33.540 align:start position:0% okay so down the left side here and I 00:09:33.540 --> 00:09:34.850 align:start position:0% okay so down the left side here and I know<00:09:33.660> this<00:09:33.839> is<00:09:33.899> an<00:09:34.080> eye<00:09:34.200> chart<00:09:34.380> I<00:09:34.620> don't<00:09:34.740> expect 00:09:34.850 --> 00:09:34.860 align:start position:0% know this is an eye chart I don't expect 00:09:34.860 --> 00:09:36.230 align:start position:0% know this is an eye chart I don't expect you<00:09:35.100> to<00:09:35.279> read<00:09:35.399> it<00:09:35.519> I'm<00:09:35.760> just<00:09:35.940> going<00:09:36.060> to 00:09:36.230 --> 00:09:36.240 align:start position:0% you to read it I'm just going to 00:09:36.240 --> 00:09:38.389 align:start position:0% you to read it I'm just going to describe<00:09:36.720> some<00:09:36.899> of<00:09:37.019> what's<00:09:37.140> on<00:09:37.380> here<00:09:37.560> so<00:09:38.160> down 00:09:38.389 --> 00:09:38.399 align:start position:0% describe some of what's on here so down 00:09:38.399 --> 00:09:40.310 align:start position:0% describe some of what's on here so down the<00:09:38.580> left<00:09:38.700> side<00:09:38.940> are<00:09:39.360> our<00:09:39.660> seven<00:09:39.839> plus<00:09:40.080> three 00:09:40.310 --> 00:09:40.320 align:start position:0% the left side are our seven plus three 00:09:40.320 --> 00:09:43.009 align:start position:0% the left side are our seven plus three criteria<00:09:40.860> they<00:09:41.640> are<00:09:41.820> quickly<00:09:42.240> Network<00:09:42.600> cost 00:09:43.009 --> 00:09:43.019 align:start position:0% criteria they are quickly Network cost 00:09:43.019 --> 00:09:44.769 align:start position:0% criteria they are quickly Network cost network<00:09:43.500> decentralization<00:09:44.279> security 00:09:44.769 --> 00:09:44.779 align:start position:0% network decentralization security 00:09:44.779 --> 00:09:48.310 align:start position:0% network decentralization security scaling<00:09:45.779> privacy<00:09:46.380> sustainability<00:09:47.220> usability 00:09:48.310 --> 00:09:48.320 align:start position:0% scaling privacy sustainability usability 00:09:48.320 --> 00:09:51.110 align:start position:0% scaling privacy sustainability usability interoperability<00:09:49.320> and<00:09:50.220> then<00:09:50.339> regulation<00:09:50.940> and 00:09:51.110 --> 00:09:51.120 align:start position:0% interoperability and then regulation and 00:09:51.120 --> 00:09:53.810 align:start position:0% interoperability and then regulation and compliance<00:09:51.660> ecosystem<00:09:52.620> resources<00:09:53.339> and 00:09:53.810 --> 00:09:53.820 align:start position:0% compliance ecosystem resources and 00:09:53.820 --> 00:09:56.210 align:start position:0% compliance ecosystem resources and ecosystem<00:09:54.240> robustness 00:09:56.210 --> 00:09:56.220 align:start position:0% ecosystem robustness 00:09:56.220 --> 00:09:58.070 align:start position:0% ecosystem robustness and<00:09:56.820> from<00:09:57.120> our<00:09:57.240> perspective<00:09:57.600> and<00:09:57.839> all<00:09:57.959> the 00:09:58.070 --> 00:09:58.080 align:start position:0% and from our perspective and all the 00:09:58.080 --> 00:10:00.710 align:start position:0% and from our perspective and all the interviews<00:09:58.440> we<00:09:58.620> did<00:09:58.800> those<00:09:59.760> captured<00:10:00.420> the 00:10:00.710 --> 00:10:00.720 align:start position:0% interviews we did those captured the 00:10:00.720 --> 00:10:03.230 align:start position:0% interviews we did those captured the factors<00:10:01.080> that<00:10:01.380> businesses<00:10:01.920> cared<00:10:02.399> about 00:10:03.230 --> 00:10:03.240 align:start position:0% factors that businesses cared about 00:10:03.240 --> 00:10:04.970 align:start position:0% factors that businesses cared about it<00:10:03.839> was<00:10:04.019> particularly<00:10:04.320> important<00:10:04.620> to<00:10:04.680> us<00:10:04.860> to 00:10:04.970 --> 00:10:04.980 align:start position:0% it was particularly important to us to 00:10:04.980 --> 00:10:05.630 align:start position:0% it was particularly important to us to make<00:10:05.040> sure<00:10:05.100> that<00:10:05.279> we<00:10:05.339> included 00:10:05.630 --> 00:10:05.640 align:start position:0% make sure that we included 00:10:05.640 --> 00:10:08.030 align:start position:0% make sure that we included decentralization<00:10:06.420> because<00:10:07.140> a<00:10:07.860> lot<00:10:07.920> of 00:10:08.030 --> 00:10:08.040 align:start position:0% decentralization because a lot of 00:10:08.040 --> 00:10:10.070 align:start position:0% decentralization because a lot of businesses<00:10:08.459> today<00:10:08.760> just<00:10:09.360> still<00:10:09.660> don't<00:10:09.899> even 00:10:10.070 --> 00:10:10.080 align:start position:0% businesses today just still don't even 00:10:10.080 --> 00:10:11.870 align:start position:0% businesses today just still don't even understand<00:10:10.440> why<00:10:11.040> that<00:10:11.279> is<00:10:11.399> something<00:10:11.580> they 00:10:11.870 --> 00:10:11.880 align:start position:0% understand why that is something they 00:10:11.880 --> 00:10:14.570 align:start position:0% understand why that is something they should<00:10:12.000> care<00:10:12.180> about<00:10:12.360> okay<00:10:13.080> so<00:10:13.620> anyway<00:10:13.740> if<00:10:14.519> you 00:10:14.570 --> 00:10:14.580 align:start position:0% should care about okay so anyway if you 00:10:14.580 --> 00:10:16.190 align:start position:0% should care about okay so anyway if you look<00:10:14.700> at<00:10:14.880> all<00:10:15.060> these<00:10:15.300> criteria<00:10:15.720> on<00:10:15.959> the<00:10:16.080> left 00:10:16.190 --> 00:10:16.200 align:start position:0% look at all these criteria on the left 00:10:16.200 --> 00:10:17.990 align:start position:0% look at all these criteria on the left not<00:10:16.800> all<00:10:16.980> businesses<00:10:17.459> are<00:10:17.580> going<00:10:17.760> to<00:10:17.880> Care 00:10:17.990 --> 00:10:18.000 align:start position:0% not all businesses are going to Care 00:10:18.000 --> 00:10:20.930 align:start position:0% not all businesses are going to Care equally<00:10:18.480> about<00:10:18.899> those<00:10:19.200> criteria 00:10:20.930 --> 00:10:20.940 align:start position:0% equally about those criteria 00:10:20.940 --> 00:10:22.850 align:start position:0% equally about those criteria so<00:10:21.360> the<00:10:21.600> goal<00:10:21.899> of<00:10:22.019> this<00:10:22.260> particular<00:10:22.560> chart 00:10:22.850 --> 00:10:22.860 align:start position:0% so the goal of this particular chart 00:10:22.860 --> 00:10:26.090 align:start position:0% so the goal of this particular chart this<00:10:23.399> particular<00:10:23.760> uh<00:10:24.420> item<00:10:24.839> this<00:10:25.620> section<00:10:25.860> of 00:10:26.090 --> 00:10:26.100 align:start position:0% this particular uh item this section of 00:10:26.100 --> 00:10:27.590 align:start position:0% this particular uh item this section of the<00:10:26.220> report<00:10:26.339> was<00:10:26.880> to<00:10:27.060> answer<00:10:27.180> the<00:10:27.420> question 00:10:27.590 --> 00:10:27.600 align:start position:0% the report was to answer the question 00:10:27.600 --> 00:10:29.930 align:start position:0% the report was to answer the question which<00:10:28.440> of<00:10:28.620> these<00:10:28.860> criteria<00:10:29.399> are<00:10:29.640> actually 00:10:29.930 --> 00:10:29.940 align:start position:0% which of these criteria are actually 00:10:29.940 --> 00:10:31.550 align:start position:0% which of these criteria are actually important<00:10:30.480> to<00:10:30.720> me 00:10:31.550 --> 00:10:31.560 align:start position:0% important to me 00:10:31.560 --> 00:10:33.170 align:start position:0% important to me so<00:10:32.040> what<00:10:32.160> we<00:10:32.279> looked<00:10:32.519> at<00:10:32.519> was<00:10:32.700> four<00:10:32.940> different 00:10:33.170 --> 00:10:33.180 align:start position:0% so what we looked at was four different 00:10:33.180 --> 00:10:34.730 align:start position:0% so what we looked at was four different types<00:10:33.480> of<00:10:33.600> businesses<00:10:34.080> as<00:10:34.320> we<00:10:34.440> call<00:10:34.560> them 00:10:34.730 --> 00:10:34.740 align:start position:0% types of businesses as we call them 00:10:34.740 --> 00:10:36.829 align:start position:0% types of businesses as we call them large<00:10:35.220> corporates<00:10:35.700> small<00:10:36.420> and<00:10:36.600> medium 00:10:36.829 --> 00:10:36.839 align:start position:0% large corporates small and medium 00:10:36.839 --> 00:10:38.750 align:start position:0% large corporates small and medium Enterprises<00:10:37.440> startups<00:10:38.100> and<00:10:38.459> then<00:10:38.580> there's 00:10:38.750 --> 00:10:38.760 align:start position:0% Enterprises startups and then there's 00:10:38.760 --> 00:10:40.490 align:start position:0% Enterprises startups and then there's government<00:10:39.060> which<00:10:39.480> is<00:10:39.600> not<00:10:39.779> a<00:10:39.959> business<00:10:40.080> but 00:10:40.490 --> 00:10:40.500 align:start position:0% government which is not a business but 00:10:40.500 --> 00:10:41.690 align:start position:0% government which is not a business but they're<00:10:40.680> they're<00:10:40.920> a<00:10:41.160> category<00:10:41.459> worth 00:10:41.690 --> 00:10:41.700 align:start position:0% they're they're a category worth 00:10:41.700 --> 00:10:44.569 align:start position:0% they're they're a category worth considering<00:10:42.240> in<00:10:42.600> uh<00:10:43.080> in<00:10:43.320> this<00:10:43.440> discussion 00:10:44.569 --> 00:10:44.579 align:start position:0% considering in uh in this discussion 00:10:44.579 --> 00:10:47.389 align:start position:0% considering in uh in this discussion so<00:10:45.660> um<00:10:46.140> there<00:10:46.680> are<00:10:46.800> two<00:10:46.920> things<00:10:47.040> I<00:10:47.220> want<00:10:47.279> to 00:10:47.389 --> 00:10:47.399 align:start position:0% so um there are two things I want to 00:10:47.399 --> 00:10:49.250 align:start position:0% so um there are two things I want to highlight<00:10:47.640> so<00:10:48.000> on<00:10:48.240> the<00:10:48.360> sustainability<00:10:48.899> side 00:10:49.250 --> 00:10:49.260 align:start position:0% highlight so on the sustainability side 00:10:49.260 --> 00:10:51.170 align:start position:0% highlight so on the sustainability side and<00:10:49.800> again<00:10:50.040> I<00:10:50.279> know<00:10:50.399> you<00:10:50.579> can't<00:10:50.700> see<00:10:50.880> all<00:10:51.060> of 00:10:51.170 --> 00:10:51.180 align:start position:0% and again I know you can't see all of 00:10:51.180 --> 00:10:52.250 align:start position:0% and again I know you can't see all of these<00:10:51.300> but<00:10:51.420> I<00:10:51.540> just<00:10:51.660> want<00:10:51.720> to<00:10:51.839> talk<00:10:51.959> about<00:10:52.079> a 00:10:52.250 --> 00:10:52.260 align:start position:0% these but I just want to talk about a 00:10:52.260 --> 00:10:54.410 align:start position:0% these but I just want to talk about a couple<00:10:52.380> of<00:10:52.500> them<00:10:52.680> so<00:10:53.459> almost<00:10:53.700> all<00:10:54.000> businesses 00:10:54.410 --> 00:10:54.420 align:start position:0% couple of them so almost all businesses 00:10:54.420 --> 00:10:56.449 align:start position:0% couple of them so almost all businesses care<00:10:54.660> about<00:10:54.779> the<00:10:55.079> environment<00:10:55.459> but 00:10:56.449 --> 00:10:56.459 align:start position:0% care about the environment but 00:10:56.459 --> 00:10:58.130 align:start position:0% care about the environment but governments<00:10:57.240> and<00:10:57.480> highly<00:10:57.779> visible 00:10:58.130 --> 00:10:58.140 align:start position:0% governments and highly visible 00:10:58.140 --> 00:11:00.470 align:start position:0% governments and highly visible corporates<00:10:58.620> care<00:10:58.980> a<00:10:59.220> lot<00:10:59.399> because<00:11:00.000> they<00:11:00.300> can 00:11:00.470 --> 00:11:00.480 align:start position:0% corporates care a lot because they can 00:11:00.480 --> 00:11:02.750 align:start position:0% corporates care a lot because they can face<00:11:00.720> very<00:11:01.320> high<00:11:01.560> and<00:11:01.800> costly<00:11:02.220> reputational 00:11:02.750 --> 00:11:02.760 align:start position:0% face very high and costly reputational 00:11:02.760 --> 00:11:05.090 align:start position:0% face very high and costly reputational risk<00:11:03.240> okay<00:11:03.839> if<00:11:04.079> they<00:11:04.260> screw<00:11:04.980> up 00:11:05.090 --> 00:11:05.100 align:start position:0% risk okay if they screw up 00:11:05.100 --> 00:11:07.069 align:start position:0% risk okay if they screw up sustainability<00:11:05.760> nowadays 00:11:07.069 --> 00:11:07.079 align:start position:0% sustainability nowadays 00:11:07.079 --> 00:11:09.370 align:start position:0% sustainability nowadays on<00:11:07.980> the<00:11:08.100> security<00:11:08.220> side 00:11:09.370 --> 00:11:09.380 align:start position:0% on the security side 00:11:09.380 --> 00:11:11.750 align:start position:0% on the security side all<00:11:10.380> companies<00:11:10.740> of<00:11:10.980> course<00:11:11.100> want<00:11:11.399> the<00:11:11.579> best 00:11:11.750 --> 00:11:11.760 align:start position:0% all companies of course want the best 00:11:11.760 --> 00:11:12.670 align:start position:0% all companies of course want the best security 00:11:12.670 --> 00:11:12.680 align:start position:0% security 00:11:12.680 --> 00:11:16.009 align:start position:0% security but<00:11:13.680> corporates<00:11:14.399> and<00:11:14.640> governments<00:11:15.180> uh 00:11:16.009 --> 00:11:16.019 align:start position:0% but corporates and governments uh 00:11:16.019 --> 00:11:17.870 align:start position:0% but corporates and governments uh interestingly<00:11:16.560> they<00:11:17.399> have<00:11:17.519> a<00:11:17.700> lot<00:11:17.760> of 00:11:17.870 --> 00:11:17.880 align:start position:0% interestingly they have a lot of 00:11:17.880 --> 00:11:19.910 align:start position:0% interestingly they have a lot of resources<00:11:18.360> to<00:11:18.660> ensure<00:11:18.959> security<00:11:19.260> whether 00:11:19.910 --> 00:11:19.920 align:start position:0% resources to ensure security whether 00:11:19.920 --> 00:11:22.069 align:start position:0% resources to ensure security whether it's<00:11:20.040> Financial<00:11:20.279> Resources<00:11:20.940> legal<00:11:21.540> technical 00:11:22.069 --> 00:11:22.079 align:start position:0% it's Financial Resources legal technical 00:11:22.079 --> 00:11:24.889 align:start position:0% it's Financial Resources legal technical whatever<00:11:22.440> and<00:11:23.399> so<00:11:23.640> in<00:11:24.060> some<00:11:24.180> cases<00:11:24.480> and<00:11:24.720> I<00:11:24.839> know 00:11:24.889 --> 00:11:24.899 align:start position:0% whatever and so in some cases and I know 00:11:24.899 --> 00:11:27.170 align:start position:0% whatever and so in some cases and I know this<00:11:25.079> is<00:11:25.200> sacrilege<00:11:25.740> to<00:11:25.920> say<00:11:26.100> it<00:11:26.220> okay<00:11:26.459> but<00:11:27.060> in 00:11:27.170 --> 00:11:27.180 align:start position:0% this is sacrilege to say it okay but in 00:11:27.180 --> 00:11:28.790 align:start position:0% this is sacrilege to say it okay but in some<00:11:27.300> cases<00:11:27.540> they're<00:11:27.779> willing<00:11:28.140> to<00:11:28.260> centralize 00:11:28.790 --> 00:11:28.800 align:start position:0% some cases they're willing to centralize 00:11:28.800 --> 00:11:31.910 align:start position:0% some cases they're willing to centralize to<00:11:29.459> sacrifice<00:11:29.820> some<00:11:30.060> decentralization<00:11:30.920> in 00:11:31.910 --> 00:11:31.920 align:start position:0% to sacrifice some decentralization in 00:11:31.920 --> 00:11:35.150 align:start position:0% to sacrifice some decentralization in return<00:11:32.100> for<00:11:32.820> scaling<00:11:33.959> but<00:11:34.500> that's<00:11:34.740> not<00:11:34.980> true 00:11:35.150 --> 00:11:35.160 align:start position:0% return for scaling but that's not true 00:11:35.160 --> 00:11:37.250 align:start position:0% return for scaling but that's not true for<00:11:35.399> smaller<00:11:35.700> businesses<00:11:36.180> in<00:11:36.779> particular<00:11:37.019> one 00:11:37.250 --> 00:11:37.260 align:start position:0% for smaller businesses in particular one 00:11:37.260 --> 00:11:38.930 align:start position:0% for smaller businesses in particular one of<00:11:37.380> the<00:11:37.440> main<00:11:37.560> appeals<00:11:38.100> of<00:11:38.459> blockchain 00:11:38.930 --> 00:11:38.940 align:start position:0% of the main appeals of blockchain 00:11:38.940 --> 00:11:41.030 align:start position:0% of the main appeals of blockchain technology<00:11:39.600> is<00:11:40.140> precisely<00:11:40.620> the<00:11:40.800> security 00:11:41.030 --> 00:11:41.040 align:start position:0% technology is precisely the security 00:11:41.040 --> 00:11:43.490 align:start position:0% technology is precisely the security against<00:11:41.540> technical<00:11:42.540> failure<00:11:43.079> attack 00:11:43.490 --> 00:11:43.500 align:start position:0% against technical failure attack 00:11:43.500 --> 00:11:45.769 align:start position:0% against technical failure attack manipulation<00:11:44.399> and<00:11:45.120> so<00:11:45.240> on<00:11:45.360> that<00:11:45.540> Network 00:11:45.769 --> 00:11:45.779 align:start position:0% manipulation and so on that Network 00:11:45.779 --> 00:11:48.530 align:start position:0% manipulation and so on that Network decentralization<00:11:46.620> offers<00:11:47.459> so<00:11:48.120> they<00:11:48.240> may<00:11:48.420> be 00:11:48.530 --> 00:11:48.540 align:start position:0% decentralization offers so they may be 00:11:48.540 --> 00:11:50.210 align:start position:0% decentralization offers so they may be less<00:11:48.779> willing<00:11:49.140> to<00:11:49.320> compromise<00:11:49.740> in<00:11:49.980> that 00:11:50.210 --> 00:11:50.220 align:start position:0% less willing to compromise in that 00:11:50.220 --> 00:11:52.130 align:start position:0% less willing to compromise in that particular<00:11:50.519> respect<00:11:50.940> now<00:11:51.480> we<00:11:51.720> did<00:11:51.899> this 00:11:52.130 --> 00:11:52.140 align:start position:0% particular respect now we did this 00:11:52.140 --> 00:11:54.350 align:start position:0% particular respect now we did this because<00:11:52.440> we<00:11:52.740> wanted<00:11:52.860> to<00:11:53.100> show<00:11:53.279> this<00:11:53.519> before<00:11:53.940> we 00:11:54.350 --> 00:11:54.360 align:start position:0% because we wanted to show this before we 00:11:54.360 --> 00:11:56.630 align:start position:0% because we wanted to show this before we got<00:11:54.540> to<00:11:55.279> describing<00:11:56.279> different 00:11:56.630 --> 00:11:56.640 align:start position:0% got to describing different 00:11:56.640 --> 00:11:58.310 align:start position:0% got to describing different architectures<00:11:57.300> and<00:11:57.600> where<00:11:57.779> we<00:11:57.959> think<00:11:58.079> they 00:11:58.310 --> 00:11:58.320 align:start position:0% architectures and where we think they 00:11:58.320 --> 00:12:03.050 align:start position:0% architectures and where we think they fall 00:12:03.050 --> 00:12:03.060 align:start position:0% 00:12:03.060 --> 00:12:04.850 align:start position:0% okay 00:12:04.850 --> 00:12:04.860 align:start position:0% okay 00:12:04.860 --> 00:12:07.610 align:start position:0% okay um<00:12:04.920> so<00:12:05.100> what<00:12:05.220> we<00:12:05.399> did<00:12:05.519> then<00:12:05.760> was<00:12:06.240> we<00:12:06.959> we 00:12:07.610 --> 00:12:07.620 align:start position:0% um so what we did then was we we 00:12:07.620 --> 00:12:09.290 align:start position:0% um so what we did then was we we basically<00:12:08.040> evaluated<00:12:08.640> those<00:12:08.940> criteria 00:12:09.290 --> 00:12:09.300 align:start position:0% basically evaluated those criteria 00:12:09.300 --> 00:12:10.730 align:start position:0% basically evaluated those criteria against<00:12:09.540> four<00:12:10.019> different<00:12:10.320> deployment 00:12:10.730 --> 00:12:10.740 align:start position:0% against four different deployment 00:12:10.740 --> 00:12:12.530 align:start position:0% against four different deployment architectures<00:12:11.279> you'll<00:12:11.640> see<00:12:11.760> we<00:12:12.240> called<00:12:12.360> it 00:12:12.530 --> 00:12:12.540 align:start position:0% architectures you'll see we called it 00:12:12.540 --> 00:12:14.150 align:start position:0% architectures you'll see we called it Network<00:12:12.779> archetype<00:12:13.380> in<00:12:13.560> the<00:12:13.680> report<00:12:13.800> what 00:12:14.150 --> 00:12:14.160 align:start position:0% Network archetype in the report what 00:12:14.160 --> 00:12:15.769 align:start position:0% Network archetype in the report what we're<00:12:14.339> talking<00:12:14.459> about<00:12:14.640> is<00:12:14.940> basic<00:12:15.420> deployment 00:12:15.769 --> 00:12:15.779 align:start position:0% we're talking about is basic deployment 00:12:15.779 --> 00:12:17.930 align:start position:0% we're talking about is basic deployment architectures<00:12:16.380> the<00:12:17.100> four<00:12:17.279> categories<00:12:17.760> are 00:12:17.930 --> 00:12:17.940 align:start position:0% architectures the four categories are 00:12:17.940 --> 00:12:19.790 align:start position:0% architectures the four categories are five<00:12:18.360> columns<00:12:18.839> but<00:12:19.019> there<00:12:19.200> are<00:12:19.320> four<00:12:19.440> primary 00:12:19.790 --> 00:12:19.800 align:start position:0% five columns but there are four primary 00:12:19.800 --> 00:12:22.490 align:start position:0% five columns but there are four primary ones<00:12:20.100> is<00:12:20.220> the<00:12:20.459> public<00:12:20.880> mainnet<00:12:21.540> mainnet<00:12:22.320> plus 00:12:22.490 --> 00:12:22.500 align:start position:0% ones is the public mainnet mainnet plus 00:12:22.500 --> 00:12:24.410 align:start position:0% ones is the public mainnet mainnet plus and<00:12:22.620> L2<00:12:22.980> mainnet<00:12:23.459> plus<00:12:23.579> a<00:12:23.760> side<00:12:23.940> chain<00:12:24.180> and 00:12:24.410 --> 00:12:24.420 align:start position:0% and L2 mainnet plus a side chain and 00:12:24.420 --> 00:12:26.449 align:start position:0% and L2 mainnet plus a side chain and private<00:12:24.839> Network 00:12:26.449 --> 00:12:26.459 align:start position:0% private Network 00:12:26.459 --> 00:12:28.790 align:start position:0% private Network the<00:12:26.880> second<00:12:27.000> column<00:12:27.480> is<00:12:27.720> mainnet<00:12:28.560> post 00:12:28.790 --> 00:12:28.800 align:start position:0% the second column is mainnet post 00:12:28.800 --> 00:12:31.310 align:start position:0% the second column is mainnet post upgrades<00:12:29.519> because<00:12:30.300> we<00:12:30.540> put<00:12:30.720> this<00:12:30.839> report<00:12:31.019> out 00:12:31.310 --> 00:12:31.320 align:start position:0% upgrades because we put this report out 00:12:31.320 --> 00:12:33.590 align:start position:0% upgrades because we put this report out of<00:12:31.500> course<00:12:31.620> before<00:12:31.980> the<00:12:32.820> merge<00:12:33.120> and<00:12:33.300> there's<00:12:33.480> a 00:12:33.590 --> 00:12:33.600 align:start position:0% of course before the merge and there's a 00:12:33.600 --> 00:12:35.449 align:start position:0% of course before the merge and there's a lot<00:12:33.660> of<00:12:33.779> other<00:12:33.899> great<00:12:34.140> stuff<00:12:34.380> coming<00:12:34.620> and<00:12:35.339> we 00:12:35.449 --> 00:12:35.459 align:start position:0% lot of other great stuff coming and we 00:12:35.459 --> 00:12:36.829 align:start position:0% lot of other great stuff coming and we wanted<00:12:35.579> to<00:12:35.760> make<00:12:35.880> sure<00:12:36.060> that<00:12:36.240> people<00:12:36.420> didn't 00:12:36.829 --> 00:12:36.839 align:start position:0% wanted to make sure that people didn't 00:12:36.839 --> 00:12:42.050 align:start position:0% wanted to make sure that people didn't look<00:12:37.800> at<00:12:38.220> the<00:12:38.519> lighter<00:12:39.000> uh<00:12:39.839> the<00:12:40.680> lighter<00:12:41.100> boxes 00:12:42.050 --> 00:12:42.060 align:start position:0% look at the lighter uh the lighter boxes 00:12:42.060 --> 00:12:43.610 align:start position:0% look at the lighter uh the lighter boxes here<00:12:42.300> which<00:12:42.540> don't<00:12:42.720> look<00:12:42.899> so<00:12:43.079> good<00:12:43.260> for<00:12:43.440> the 00:12:43.610 --> 00:12:43.620 align:start position:0% here which don't look so good for the 00:12:43.620 --> 00:12:45.710 align:start position:0% here which don't look so good for the public<00:12:43.680> mainnet<00:12:44.339> and<00:12:44.459> say<00:12:44.639> oh<00:12:44.820> yeah<00:12:45.120> that's 00:12:45.710 --> 00:12:45.720 align:start position:0% public mainnet and say oh yeah that's 00:12:45.720 --> 00:12:47.569 align:start position:0% public mainnet and say oh yeah that's always<00:12:45.959> going<00:12:46.139> to<00:12:46.260> be<00:12:46.380> the<00:12:46.560> case<00:12:46.740> no<00:12:47.279> it's 00:12:47.569 --> 00:12:47.579 align:start position:0% always going to be the case no it's 00:12:47.579 --> 00:12:49.670 align:start position:0% always going to be the case no it's definitely<00:12:47.940> not<00:12:48.300> and<00:12:48.779> as<00:12:49.019> we<00:12:49.200> do<00:12:49.320> this<00:12:49.500> report 00:12:49.670 --> 00:12:49.680 align:start position:0% definitely not and as we do this report 00:12:49.680 --> 00:12:51.170 align:start position:0% definitely not and as we do this report each<00:12:50.100> year<00:12:50.279> we're<00:12:50.760> going<00:12:50.940> to<00:12:51.060> continue 00:12:51.170 --> 00:12:51.180 align:start position:0% each year we're going to continue 00:12:51.180 --> 00:12:53.389 align:start position:0% each year we're going to continue updating<00:12:51.779> it<00:12:52.079> in<00:12:52.500> terms<00:12:52.680> of<00:12:52.800> where<00:12:53.160> where 00:12:53.389 --> 00:12:53.399 align:start position:0% updating it in terms of where where 00:12:53.399 --> 00:12:55.569 align:start position:0% updating it in terms of where where we're<00:12:53.639> actually<00:12:53.820> at<00:12:54.120> so<00:12:54.720> a<00:12:54.779> few<00:12:54.899> examples<00:12:55.320> here 00:12:55.569 --> 00:12:55.579 align:start position:0% we're actually at so a few examples here 00:12:55.579 --> 00:12:58.490 align:start position:0% we're actually at so a few examples here from<00:12:56.579> a<00:12:56.700> network<00:12:56.880> cost<00:12:57.120> perspective 00:12:58.490 --> 00:12:58.500 align:start position:0% from a network cost perspective 00:12:58.500 --> 00:13:00.829 align:start position:0% from a network cost perspective the<00:12:59.220> cost<00:12:59.339> to<00:12:59.639> to<00:12:59.880> actually<00:13:00.180> operate<00:13:00.660> a 00:13:00.829 --> 00:13:00.839 align:start position:0% the cost to to actually operate a 00:13:00.839 --> 00:13:02.810 align:start position:0% the cost to to actually operate a private<00:13:01.079> Network<00:13:01.260> can<00:13:01.740> be<00:13:01.920> very<00:13:02.100> low<00:13:02.339> even 00:13:02.810 --> 00:13:02.820 align:start position:0% private Network can be very low even 00:13:02.820 --> 00:13:03.710 align:start position:0% private Network can be very low even when<00:13:03.060> you're<00:13:03.180> running<00:13:03.360> your<00:13:03.600> own 00:13:03.710 --> 00:13:03.720 align:start position:0% when you're running your own 00:13:03.720 --> 00:13:05.750 align:start position:0% when you're running your own infrastructure<00:13:04.260> the<00:13:04.680> the<00:13:04.980> actual<00:13:05.279> operations 00:13:05.750 --> 00:13:05.760 align:start position:0% infrastructure the the actual operations 00:13:05.760 --> 00:13:07.850 align:start position:0% infrastructure the the actual operations cost<00:13:06.120> can<00:13:06.420> be<00:13:06.540> quite<00:13:06.720> low 00:13:07.850 --> 00:13:07.860 align:start position:0% cost can be quite low 00:13:07.860 --> 00:13:09.650 align:start position:0% cost can be quite low um<00:13:07.920> and<00:13:08.220> we<00:13:08.459> know<00:13:08.579> the<00:13:08.820> main<00:13:08.940> net<00:13:09.180> is<00:13:09.300> expensive 00:13:09.650 --> 00:13:09.660 align:start position:0% um and we know the main net is expensive 00:13:09.660 --> 00:13:11.389 align:start position:0% um and we know the main net is expensive today<00:13:09.839> okay 00:13:11.389 --> 00:13:11.399 align:start position:0% today okay 00:13:11.399 --> 00:13:13.730 align:start position:0% today okay um<00:13:11.459> and<00:13:11.820> that's<00:13:11.940> being<00:13:12.120> worked<00:13:12.420> on<00:13:12.480> we<00:13:12.660> know 00:13:13.730 --> 00:13:13.740 align:start position:0% um and that's being worked on we know 00:13:13.740 --> 00:13:16.090 align:start position:0% um and that's being worked on we know um<00:13:13.860> in<00:13:14.339> terms<00:13:14.579> of<00:13:14.639> ease<00:13:15.000> of<00:13:15.120> use<00:13:15.240> by<00:13:15.480> businesses 00:13:16.090 --> 00:13:16.100 align:start position:0% um in terms of ease of use by businesses 00:13:16.100 --> 00:13:19.250 align:start position:0% um in terms of ease of use by businesses uh<00:13:17.100> layer<00:13:17.399> twos<00:13:17.700> or<00:13:17.880> side<00:13:18.060> chains<00:13:18.480> uh<00:13:19.079> actually 00:13:19.250 --> 00:13:19.260 align:start position:0% uh layer twos or side chains uh actually 00:13:19.260 --> 00:13:21.430 align:start position:0% uh layer twos or side chains uh actually have<00:13:19.620> the<00:13:19.800> most<00:13:19.920> support<00:13:20.300> interestingly 00:13:21.430 --> 00:13:21.440 align:start position:0% have the most support interestingly 00:13:21.440 --> 00:13:23.870 align:start position:0% have the most support interestingly because<00:13:22.440> the<00:13:22.980> ones<00:13:23.160> who<00:13:23.279> are<00:13:23.399> building<00:13:23.639> those 00:13:23.870 --> 00:13:23.880 align:start position:0% because the ones who are building those 00:13:23.880 --> 00:13:26.690 align:start position:0% because the ones who are building those layer<00:13:24.180> twos<00:13:24.480> or<00:13:24.600> side<00:13:24.779> chains<00:13:25.339> provide<00:13:26.339> a<00:13:26.579> lot 00:13:26.690 --> 00:13:26.700 align:start position:0% layer twos or side chains provide a lot 00:13:26.700 --> 00:13:28.550 align:start position:0% layer twos or side chains provide a lot of<00:13:26.820> information<00:13:27.120> and<00:13:27.600> a<00:13:27.720> lot<00:13:27.839> of<00:13:27.959> help<00:13:28.139> on<00:13:28.440> how 00:13:28.550 --> 00:13:28.560 align:start position:0% of information and a lot of help on how 00:13:28.560 --> 00:13:30.170 align:start position:0% of information and a lot of help on how to<00:13:28.680> make<00:13:28.800> use<00:13:28.980> of<00:13:29.160> them 00:13:30.170 --> 00:13:30.180 align:start position:0% to make use of them 00:13:30.180 --> 00:13:31.850 align:start position:0% to make use of them uh<00:13:30.660> if<00:13:30.839> you<00:13:30.959> do<00:13:31.079> a<00:13:31.200> private<00:13:31.440> chain<00:13:31.560> on<00:13:31.740> the 00:13:31.850 --> 00:13:31.860 align:start position:0% uh if you do a private chain on the 00:13:31.860 --> 00:13:34.550 align:start position:0% uh if you do a private chain on the other<00:13:31.920> hand<00:13:32.100> it's<00:13:32.519> all<00:13:32.700> on<00:13:32.880> you<00:13:33.060> right<00:13:33.779> so<00:13:34.139> it's 00:13:34.550 --> 00:13:34.560 align:start position:0% other hand it's all on you right so it's 00:13:34.560 --> 00:13:35.990 align:start position:0% other hand it's all on you right so it's not<00:13:34.740> easy<00:13:34.920> at<00:13:35.160> all<00:13:35.279> if<00:13:35.459> you<00:13:35.579> want<00:13:35.639> to<00:13:35.760> do<00:13:35.880> a 00:13:35.990 --> 00:13:36.000 align:start position:0% not easy at all if you want to do a 00:13:36.000 --> 00:13:37.790 align:start position:0% not easy at all if you want to do a private<00:13:36.240> chain<00:13:36.420> you<00:13:36.720> have<00:13:36.839> to<00:13:37.079> do<00:13:37.500> a<00:13:37.620> lot<00:13:37.740> of 00:13:37.790 --> 00:13:37.800 align:start position:0% private chain you have to do a lot of 00:13:37.800 --> 00:13:39.829 align:start position:0% private chain you have to do a lot of the<00:13:37.920> work<00:13:38.040> yourself<00:13:38.240> from<00:13:39.240> a<00:13:39.420> compliance 00:13:39.829 --> 00:13:39.839 align:start position:0% the work yourself from a compliance 00:13:39.839 --> 00:13:41.030 align:start position:0% the work yourself from a compliance perspective 00:13:41.030 --> 00:13:41.040 align:start position:0% perspective 00:13:41.040 --> 00:13:43.009 align:start position:0% perspective a<00:13:41.519> private<00:13:41.760> Network<00:13:41.940> it's<00:13:42.300> the<00:13:42.480> easiest<00:13:42.779> to 00:13:43.009 --> 00:13:43.019 align:start position:0% a private Network it's the easiest to 00:13:43.019 --> 00:13:46.310 align:start position:0% a private Network it's the easiest to implement<00:13:43.320> you<00:13:43.800> know<00:13:43.860> controls<00:13:44.339> such<00:13:44.519> as<00:13:44.639> kyc 00:13:46.310 --> 00:13:46.320 align:start position:0% implement you know controls such as kyc 00:13:46.320 --> 00:13:48.230 align:start position:0% implement you know controls such as kyc um<00:13:46.440> and<00:13:46.740> on<00:13:46.920> you<00:13:47.160> know<00:13:47.220> the<00:13:47.399> mainnet<00:13:47.820> is<00:13:48.060> of 00:13:48.230 --> 00:13:48.240 align:start position:0% um and on you know the mainnet is of 00:13:48.240 --> 00:13:49.670 align:start position:0% um and on you know the mainnet is of course<00:13:48.360> fully<00:13:48.720> decentralized<00:13:49.260> on<00:13:49.440> the<00:13:49.560> other 00:13:49.670 --> 00:13:49.680 align:start position:0% course fully decentralized on the other 00:13:49.680 --> 00:13:52.490 align:start position:0% course fully decentralized on the other on<00:13:50.040> the<00:13:50.160> other<00:13:50.279> end<00:13:50.899> so<00:13:51.899> most<00:13:52.200> of<00:13:52.380> this 00:13:52.490 --> 00:13:52.500 align:start position:0% on the other end so most of this 00:13:52.500 --> 00:13:54.290 align:start position:0% on the other end so most of this shouldn't<00:13:52.860> surprise<00:13:53.160> you<00:13:53.339> too<00:13:53.579> much<00:13:53.760> but 00:13:54.290 --> 00:13:54.300 align:start position:0% shouldn't surprise you too much but 00:13:54.300 --> 00:13:56.629 align:start position:0% shouldn't surprise you too much but again<00:13:54.839> this<00:13:55.139> is<00:13:55.320> written<00:13:55.680> for 00:13:56.629 --> 00:13:56.639 align:start position:0% again this is written for 00:13:56.639 --> 00:13:58.370 align:start position:0% again this is written for chances<00:13:57.360> are<00:13:57.540> it's<00:13:57.779> written<00:13:58.019> for<00:13:58.200> your 00:13:58.370 --> 00:13:58.380 align:start position:0% chances are it's written for your 00:13:58.380 --> 00:13:59.750 align:start position:0% chances are it's written for your customers<00:13:58.800> the<00:13:59.040> people<00:13:59.220> you're<00:13:59.399> trying<00:13:59.639> to 00:13:59.750 --> 00:13:59.760 align:start position:0% customers the people you're trying to 00:13:59.760 --> 00:14:01.730 align:start position:0% customers the people you're trying to sell<00:13:59.880> to<00:14:00.180> and<00:14:00.779> who<00:14:00.959> need<00:14:01.079> someone<00:14:01.320> to<00:14:01.560> explain 00:14:01.730 --> 00:14:01.740 align:start position:0% sell to and who need someone to explain 00:14:01.740 --> 00:14:03.050 align:start position:0% sell to and who need someone to explain this<00:14:02.040> to<00:14:02.220> them<00:14:02.339> in<00:14:02.519> a<00:14:02.579> way<00:14:02.700> that<00:14:02.820> they<00:14:03.000> can 00:14:03.050 --> 00:14:03.060 align:start position:0% this to them in a way that they can 00:14:03.060 --> 00:14:04.910 align:start position:0% this to them in a way that they can understand 00:14:04.910 --> 00:14:04.920 align:start position:0% understand 00:14:04.920 --> 00:14:07.910 align:start position:0% understand um that<00:14:05.339> did<00:14:05.579> not<00:14:05.760> do<00:14:06.000> okay<00:14:06.480> all<00:14:06.779> right<00:14:06.959> so<00:14:07.620> one 00:14:07.910 --> 00:14:07.920 align:start position:0% um that did not do okay all right so one 00:14:07.920 --> 00:14:09.110 align:start position:0% um that did not do okay all right so one of<00:14:08.040> the<00:14:08.100> things<00:14:08.160> we<00:14:08.339> did<00:14:08.519> was<00:14:08.700> we<00:14:08.820> wanted<00:14:08.940> to 00:14:09.110 --> 00:14:09.120 align:start position:0% of the things we did was we wanted to 00:14:09.120 --> 00:14:10.550 align:start position:0% of the things we did was we wanted to give<00:14:09.180> examples<00:14:09.540> of<00:14:09.720> how<00:14:09.899> you<00:14:10.019> might<00:14:10.139> use<00:14:10.320> this 00:14:10.550 --> 00:14:10.560 align:start position:0% give examples of how you might use this 00:14:10.560 --> 00:14:12.769 align:start position:0% give examples of how you might use this framework<00:14:10.920> for<00:14:11.579> a<00:14:11.700> specific<00:14:12.000> use<00:14:12.300> case<00:14:12.540> and 00:14:12.769 --> 00:14:12.779 align:start position:0% framework for a specific use case and 00:14:12.779 --> 00:14:14.210 align:start position:0% framework for a specific use case and again<00:14:12.959> I<00:14:13.139> know<00:14:13.260> it's<00:14:13.380> an<00:14:13.500> eye<00:14:13.620> chart<00:14:13.800> you<00:14:14.100> can't 00:14:14.210 --> 00:14:14.220 align:start position:0% again I know it's an eye chart you can't 00:14:14.220 --> 00:14:16.430 align:start position:0% again I know it's an eye chart you can't see<00:14:14.399> all<00:14:14.579> these<00:14:14.760> it's<00:14:14.940> all<00:14:15.120> in<00:14:15.300> the<00:14:15.480> report 00:14:16.430 --> 00:14:16.440 align:start position:0% see all these it's all in the report 00:14:16.440 --> 00:14:18.050 align:start position:0% see all these it's all in the report but 00:14:18.050 --> 00:14:18.060 align:start position:0% but 00:14:18.060 --> 00:14:20.269 align:start position:0% but um we<00:14:18.480> basically<00:14:18.839> analyze<00:14:19.500> these<00:14:19.800> criteria 00:14:20.269 --> 00:14:20.279 align:start position:0% um we basically analyze these criteria 00:14:20.279 --> 00:14:21.829 align:start position:0% um we basically analyze these criteria against 00:14:21.829 --> 00:14:21.839 align:start position:0% against 00:14:21.839 --> 00:14:23.810 align:start position:0% against um<00:14:21.899> the<00:14:22.620> deployment<00:14:22.920> architectures<00:14:23.519> that 00:14:23.810 --> 00:14:23.820 align:start position:0% um the deployment architectures that 00:14:23.820 --> 00:14:26.269 align:start position:0% um the deployment architectures that that<00:14:24.060> I<00:14:24.300> talked<00:14:24.540> about<00:14:24.600> so<00:14:25.260> for<00:14:25.500> each<00:14:25.740> of<00:14:26.040> these 00:14:26.269 --> 00:14:26.279 align:start position:0% that I talked about so for each of these 00:14:26.279 --> 00:14:28.310 align:start position:0% that I talked about so for each of these architectures<00:14:26.760> we<00:14:27.180> scored<00:14:27.540> the<00:14:27.660> criteria<00:14:28.139> is 00:14:28.310 --> 00:14:28.320 align:start position:0% architectures we scored the criteria is 00:14:28.320 --> 00:14:31.069 align:start position:0% architectures we scored the criteria is very<00:14:28.620> poor<00:14:29.040> poor<00:14:29.519> neutral<00:14:29.940> good<00:14:30.660> and<00:14:30.899> very 00:14:31.069 --> 00:14:31.079 align:start position:0% very poor poor neutral good and very 00:14:31.079 --> 00:14:33.769 align:start position:0% very poor poor neutral good and very good<00:14:31.260> where<00:14:31.620> good<00:14:31.980> is<00:14:32.160> out<00:14:32.399> here<00:14:32.639> and<00:14:33.360> poor<00:14:33.660> is 00:14:33.769 --> 00:14:33.779 align:start position:0% good where good is out here and poor is 00:14:33.779 --> 00:14:36.829 align:start position:0% good where good is out here and poor is in<00:14:33.899> the<00:14:34.079> center<00:14:34.200> on<00:14:34.740> these<00:14:34.920> radar<00:14:35.279> graphs 00:14:36.829 --> 00:14:36.839 align:start position:0% in the center on these radar graphs 00:14:36.839 --> 00:14:37.490 align:start position:0% in the center on these radar graphs um 00:14:37.490 --> 00:14:37.500 align:start position:0% um 00:14:37.500 --> 00:14:39.110 align:start position:0% um so<00:14:37.920> I'm<00:14:38.040> just<00:14:38.220> going<00:14:38.339> to<00:14:38.459> hit<00:14:38.639> a<00:14:38.880> couple<00:14:38.940> of 00:14:39.110 --> 00:14:39.120 align:start position:0% so I'm just going to hit a couple of 00:14:39.120 --> 00:14:41.810 align:start position:0% so I'm just going to hit a couple of headlights<00:14:39.920> so<00:14:40.920> the<00:14:41.100> upper<00:14:41.339> left<00:14:41.459> one<00:14:41.639> is 00:14:41.810 --> 00:14:41.820 align:start position:0% headlights so the upper left one is 00:14:41.820 --> 00:14:44.150 align:start position:0% headlights so the upper left one is asset<00:14:42.180> tokenization<00:14:42.779> and<00:14:43.320> then<00:14:43.500> payments 00:14:44.150 --> 00:14:44.160 align:start position:0% asset tokenization and then payments 00:14:44.160 --> 00:14:45.769 align:start position:0% asset tokenization and then payments Payment<00:14:44.459> Solutions<00:14:44.940> is<00:14:45.240> just<00:14:45.420> to<00:14:45.540> the<00:14:45.660> right 00:14:45.769 --> 00:14:45.779 align:start position:0% Payment Solutions is just to the right 00:14:45.779 --> 00:14:47.870 align:start position:0% Payment Solutions is just to the right of<00:14:45.959> that<00:14:46.079> so<00:14:46.800> for<00:14:46.920> asset<00:14:47.279> tokenization 00:14:47.870 --> 00:14:47.880 align:start position:0% of that so for asset tokenization 00:14:47.880 --> 00:14:50.389 align:start position:0% of that so for asset tokenization mainnet<00:14:48.720> score<00:14:48.899> is<00:14:49.139> very<00:14:49.320> high<00:14:49.560> on<00:14:49.920> usability 00:14:50.389 --> 00:14:50.399 align:start position:0% mainnet score is very high on usability 00:14:50.399 --> 00:14:53.870 align:start position:0% mainnet score is very high on usability and<00:14:50.760> interoperability<00:14:51.600> for<00:14:51.899> tokenization 00:14:53.870 --> 00:14:53.880 align:start position:0% and interoperability for tokenization 00:14:53.880 --> 00:14:55.910 align:start position:0% and interoperability for tokenization um<00:14:54.000> but<00:14:54.779> you<00:14:55.260> know<00:14:55.320> if<00:14:55.440> you<00:14:55.560> have<00:14:55.680> a<00:14:55.800> project 00:14:55.910 --> 00:14:55.920 align:start position:0% um but you know if you have a project 00:14:55.920 --> 00:14:57.170 align:start position:0% um but you know if you have a project for<00:14:56.220> which<00:14:56.399> high<00:14:56.579> performance<00:14:57.000> and 00:14:57.170 --> 00:14:57.180 align:start position:0% for which high performance and 00:14:57.180 --> 00:14:58.790 align:start position:0% for which high performance and Regulatory<00:14:57.660> Compliance<00:14:58.139> are<00:14:58.320> priorities 00:14:58.790 --> 00:14:58.800 align:start position:0% Regulatory Compliance are priorities 00:14:58.800 --> 00:15:01.550 align:start position:0% Regulatory Compliance are priorities you'll<00:14:59.639> want<00:14:59.760> to<00:14:59.880> be<00:14:59.940> working<00:15:00.120> with<00:15:00.360> an<00:15:00.540> L2<00:15:00.899> or 00:15:01.550 --> 00:15:01.560 align:start position:0% you'll want to be working with an L2 or 00:15:01.560 --> 00:15:03.889 align:start position:0% you'll want to be working with an L2 or Si<00:15:01.920> chain<00:15:02.100> or<00:15:02.880> or<00:15:03.060> you<00:15:03.240> could<00:15:03.420> consider 00:15:03.889 --> 00:15:03.899 align:start position:0% Si chain or or you could consider 00:15:03.899 --> 00:15:06.410 align:start position:0% Si chain or or you could consider building<00:15:04.620> a<00:15:04.860> private<00:15:05.100> Network 00:15:06.410 --> 00:15:06.420 align:start position:0% building a private Network 00:15:06.420 --> 00:15:08.750 align:start position:0% building a private Network on<00:15:07.380> the<00:15:07.560> payment<00:15:07.680> side 00:15:08.750 --> 00:15:08.760 align:start position:0% on the payment side 00:15:08.760 --> 00:15:10.730 align:start position:0% on the payment side for<00:15:09.240> payments<00:15:09.600> use<00:15:09.720> case<00:15:09.899> ethereum<00:15:10.440> is<00:15:10.620> a 00:15:10.730 --> 00:15:10.740 align:start position:0% for payments use case ethereum is a 00:15:10.740 --> 00:15:12.230 align:start position:0% for payments use case ethereum is a payments<00:15:11.100> Network<00:15:11.279> essentially<00:15:11.820> out<00:15:12.000> of<00:15:12.120> the 00:15:12.230 --> 00:15:12.240 align:start position:0% payments Network essentially out of the 00:15:12.240 --> 00:15:13.430 align:start position:0% payments Network essentially out of the box<00:15:12.360> I<00:15:12.660> mean 00:15:13.430 --> 00:15:13.440 align:start position:0% box I mean 00:15:13.440 --> 00:15:15.530 align:start position:0% box I mean you<00:15:13.980> know<00:15:14.040> Finding<00:15:14.639> information<00:15:14.820> about<00:15:15.240> how 00:15:15.530 --> 00:15:15.540 align:start position:0% you know Finding information about how 00:15:15.540 --> 00:15:17.030 align:start position:0% you know Finding information about how to<00:15:15.660> do<00:15:15.779> uh<00:15:16.139> how<00:15:16.320> to<00:15:16.440> do<00:15:16.560> payments<00:15:16.920> with 00:15:17.030 --> 00:15:17.040 align:start position:0% to do uh how to do payments with 00:15:17.040 --> 00:15:19.129 align:start position:0% to do uh how to do payments with ethereum<00:15:17.519> or<00:15:18.180> something<00:15:18.360> built<00:15:18.779> on<00:15:18.839> top<00:15:19.019> of 00:15:19.129 --> 00:15:19.139 align:start position:0% ethereum or something built on top of 00:15:19.139 --> 00:15:21.590 align:start position:0% ethereum or something built on top of ethereum<00:15:19.500> is<00:15:19.620> not<00:15:19.800> at<00:15:19.920> all<00:15:20.040> hard<00:15:20.339> but<00:15:21.180> again<00:15:21.360> if 00:15:21.590 --> 00:15:21.600 align:start position:0% ethereum is not at all hard but again if 00:15:21.600 --> 00:15:23.090 align:start position:0% ethereum is not at all hard but again if you<00:15:21.720> have<00:15:21.839> high<00:15:22.139> volume<00:15:22.380> you're<00:15:22.860> going<00:15:23.040> to 00:15:23.090 --> 00:15:23.100 align:start position:0% you have high volume you're going to 00:15:23.100 --> 00:15:24.650 align:start position:0% you have high volume you're going to want<00:15:23.220> to<00:15:23.339> work<00:15:23.459> with<00:15:23.639> a<00:15:23.760> layer<00:15:24.000> 2<00:15:24.180> or<00:15:24.420> side 00:15:24.650 --> 00:15:24.660 align:start position:0% want to work with a layer 2 or side 00:15:24.660 --> 00:15:27.110 align:start position:0% want to work with a layer 2 or side chain<00:15:24.899> uh<00:15:25.620> particularly<00:15:25.980> if<00:15:26.160> you<00:15:26.279> have<00:15:26.459> uh<00:15:26.820> if 00:15:27.110 --> 00:15:27.120 align:start position:0% chain uh particularly if you have uh if 00:15:27.120 --> 00:15:29.269 align:start position:0% chain uh particularly if you have uh if you're<00:15:27.360> if<00:15:28.079> you're<00:15:28.440> addressing<00:15:28.800> retail 00:15:29.269 --> 00:15:29.279 align:start position:0% you're if you're addressing retail 00:15:29.279 --> 00:15:31.730 align:start position:0% you're if you're addressing retail customers<00:15:30.000> now<00:15:30.720> interestingly<00:15:31.380> if<00:15:31.620> you 00:15:31.730 --> 00:15:31.740 align:start position:0% customers now interestingly if you 00:15:31.740 --> 00:15:33.110 align:start position:0% customers now interestingly if you actually<00:15:31.920> have<00:15:32.100> a<00:15:32.220> wholesale<00:15:32.519> business<00:15:32.760> you 00:15:33.110 --> 00:15:33.120 align:start position:0% actually have a wholesale business you 00:15:33.120 --> 00:15:34.370 align:start position:0% actually have a wholesale business you might<00:15:33.240> not<00:15:33.360> need<00:15:33.540> to<00:15:33.660> go<00:15:33.839> to<00:15:33.959> that<00:15:34.079> and<00:15:34.199> you 00:15:34.370 --> 00:15:34.380 align:start position:0% might not need to go to that and you 00:15:34.380 --> 00:15:36.829 align:start position:0% might not need to go to that and you could<00:15:34.500> actually<00:15:34.620> do<00:15:34.860> a<00:15:35.100> private<00:15:35.339> Network<00:15:35.839> more 00:15:36.829 --> 00:15:36.839 align:start position:0% could actually do a private Network more 00:15:36.839 --> 00:15:39.889 align:start position:0% could actually do a private Network more simply<00:15:37.199> today<00:15:37.560> more<00:15:38.399> simply<00:15:38.699> more<00:15:38.940> cheaply<00:15:39.300> if 00:15:39.889 --> 00:15:39.899 align:start position:0% simply today more simply more cheaply if 00:15:39.899 --> 00:15:43.430 align:start position:0% simply today more simply more cheaply if you<00:15:40.139> have<00:15:40.320> a<00:15:40.620> a<00:15:40.920> wholesale<00:15:41.279> business 00:15:43.430 --> 00:15:43.440 align:start position:0% you have a a wholesale business 00:15:43.440 --> 00:15:46.850 align:start position:0% you have a a wholesale business okay<00:15:44.880> um<00:15:44.880> I<00:15:45.120> said<00:15:45.240> that<00:15:45.420> we<00:15:45.540> did<00:15:45.660> interviews 00:15:46.850 --> 00:15:46.860 align:start position:0% okay um I said that we did interviews 00:15:46.860 --> 00:15:48.170 align:start position:0% okay um I said that we did interviews um<00:15:46.920> we<00:15:47.100> actually<00:15:47.220> have<00:15:47.399> way<00:15:47.639> more<00:15:47.820> than<00:15:48.000> six 00:15:48.170 --> 00:15:48.180 align:start position:0% um we actually have way more than six 00:15:48.180 --> 00:15:50.389 align:start position:0% um we actually have way more than six interviews<00:15:48.720> but<00:15:49.380> I<00:15:49.500> just<00:15:49.620> wanted<00:15:49.740> to<00:15:49.980> give<00:15:50.160> a 00:15:50.389 --> 00:15:50.399 align:start position:0% interviews but I just wanted to give a 00:15:50.399 --> 00:15:51.829 align:start position:0% interviews but I just wanted to give a few<00:15:50.579> examples<00:15:50.940> of<00:15:51.120> some<00:15:51.300> of<00:15:51.420> the<00:15:51.480> people<00:15:51.600> that 00:15:51.829 --> 00:15:51.839 align:start position:0% few examples of some of the people that 00:15:51.839 --> 00:15:52.970 align:start position:0% few examples of some of the people that we<00:15:51.959> spoke<00:15:52.199> with 00:15:52.970 --> 00:15:52.980 align:start position:0% we spoke with 00:15:52.980 --> 00:15:54.769 align:start position:0% we spoke with uh<00:15:53.579> we<00:15:53.820> spoke<00:15:54.000> with<00:15:54.120> people<00:15:54.300> who<00:15:54.600> actually 00:15:54.769 --> 00:15:54.779 align:start position:0% uh we spoke with people who actually 00:15:54.779 --> 00:15:56.750 align:start position:0% uh we spoke with people who actually were<00:15:55.260> building<00:15:55.500> these<00:15:55.860> projects<00:15:56.220> we<00:15:56.519> also 00:15:56.750 --> 00:15:56.760 align:start position:0% were building these projects we also 00:15:56.760 --> 00:15:58.910 align:start position:0% were building these projects we also spoke<00:15:56.940> with<00:15:57.120> some<00:15:57.360> well-known<00:15:57.720> people<00:15:57.959> in<00:15:58.800> the 00:15:58.910 --> 00:15:58.920 align:start position:0% spoke with some well-known people in the 00:15:58.920 --> 00:16:00.290 align:start position:0% spoke with some well-known people in the space<00:15:59.100> and<00:15:59.459> probably<00:15:59.699> some<00:16:00.000> of<00:16:00.120> the<00:16:00.180> people 00:16:00.290 --> 00:16:00.300 align:start position:0% space and probably some of the people 00:16:00.300 --> 00:16:01.850 align:start position:0% space and probably some of the people here<00:16:00.540> in<00:16:00.720> the<00:16:00.899> room<00:16:00.959> and<00:16:01.139> I<00:16:01.320> just<00:16:01.440> haven't<00:16:01.560> seen 00:16:01.850 --> 00:16:01.860 align:start position:0% here in the room and I just haven't seen 00:16:01.860 --> 00:16:03.230 align:start position:0% here in the room and I just haven't seen them<00:16:01.980> yet 00:16:03.230 --> 00:16:03.240 align:start position:0% them yet 00:16:03.240 --> 00:16:04.610 align:start position:0% them yet um but<00:16:03.600> I<00:16:03.720> just<00:16:03.779> want<00:16:03.899> to<00:16:04.019> give<00:16:04.139> you<00:16:04.199> an<00:16:04.380> idea 00:16:04.610 --> 00:16:04.620 align:start position:0% um but I just want to give you an idea 00:16:04.620 --> 00:16:06.430 align:start position:0% um but I just want to give you an idea of<00:16:04.740> this<00:16:04.860> within<00:16:05.339> the<00:16:05.459> report<00:16:05.579> we<00:16:06.060> actually 00:16:06.430 --> 00:16:06.440 align:start position:0% of this within the report we actually 00:16:06.440 --> 00:16:10.250 align:start position:0% of this within the report we actually include<00:16:07.440> quotes<00:16:08.180> uh<00:16:09.180> throughout<00:16:09.600> because<00:16:09.959> we 00:16:10.250 --> 00:16:10.260 align:start position:0% include quotes uh throughout because we 00:16:10.260 --> 00:16:11.509 align:start position:0% include quotes uh throughout because we found<00:16:10.380> that<00:16:10.620> the<00:16:10.740> quotes<00:16:10.860> from<00:16:11.160> these<00:16:11.399> people 00:16:11.509 --> 00:16:11.519 align:start position:0% found that the quotes from these people 00:16:11.519 --> 00:16:13.730 align:start position:0% found that the quotes from these people are<00:16:11.880> the<00:16:12.060> thing<00:16:12.180> that<00:16:12.420> are<00:16:12.600> are<00:16:12.899> the<00:16:13.139> they 00:16:13.730 --> 00:16:13.740 align:start position:0% are the thing that are are the they 00:16:13.740 --> 00:16:16.129 align:start position:0% are the thing that are are the they express<00:16:13.980> this<00:16:14.399> better<00:16:14.579> than<00:16:14.820> any<00:16:15.060> of<00:16:15.240> us<00:16:15.360> could 00:16:16.129 --> 00:16:16.139 align:start position:0% express this better than any of us could 00:16:16.139 --> 00:16:18.230 align:start position:0% express this better than any of us could because<00:16:16.680> they're<00:16:16.980> dealing<00:16:17.279> with<00:16:17.459> it<00:16:17.639> uh<00:16:18.060> every 00:16:18.230 --> 00:16:18.240 align:start position:0% because they're dealing with it uh every 00:16:18.240 --> 00:16:20.449 align:start position:0% because they're dealing with it uh every every<00:16:18.540> single<00:16:18.839> day<00:16:18.959> so<00:16:19.260> I've<00:16:19.440> got 00:16:20.449 --> 00:16:20.459 align:start position:0% every single day so I've got 00:16:20.459 --> 00:16:22.550 align:start position:0% every single day so I've got um I've<00:16:20.699> got<00:16:20.820> three<00:16:21.060> examples<00:16:21.420> here 00:16:22.550 --> 00:16:22.560 align:start position:0% um I've got three examples here 00:16:22.560 --> 00:16:24.949 align:start position:0% um I've got three examples here um<00:16:22.620> and<00:16:22.860> the<00:16:22.980> one<00:16:23.100> that<00:16:23.220> I'm<00:16:23.399> gonna<00:16:23.720> uh<00:16:24.720> I'm 00:16:24.949 --> 00:16:24.959 align:start position:0% um and the one that I'm gonna uh I'm 00:16:24.959 --> 00:16:26.449 align:start position:0% um and the one that I'm gonna uh I'm gonna<00:16:25.079> actually<00:16:25.260> call<00:16:25.500> out<00:16:25.740> is<00:16:25.920> is<00:16:26.100> in<00:16:26.339> the 00:16:26.449 --> 00:16:26.459 align:start position:0% gonna actually call out is is in the 00:16:26.459 --> 00:16:28.970 align:start position:0% gonna actually call out is is in the middle<00:16:26.579> uh<00:16:27.120> from<00:16:27.300> Benson<00:16:27.660> of<00:16:28.199> acre<00:16:28.500> Africa 00:16:28.970 --> 00:16:28.980 align:start position:0% middle uh from Benson of acre Africa 00:16:28.980 --> 00:16:31.250 align:start position:0% middle uh from Benson of acre Africa acre<00:16:29.399> Africa<00:16:29.820> provides<00:16:30.300> parametric 00:16:31.250 --> 00:16:31.260 align:start position:0% acre Africa provides parametric 00:16:31.260 --> 00:16:32.990 align:start position:0% acre Africa provides parametric insurance<00:16:31.500> for<00:16:31.860> small<00:16:32.040> holding<00:16:32.459> farmers<00:16:32.820> in 00:16:32.990 --> 00:16:33.000 align:start position:0% insurance for small holding farmers in 00:16:33.000 --> 00:16:34.069 align:start position:0% insurance for small holding farmers in Africa 00:16:34.069 --> 00:16:34.079 align:start position:0% Africa 00:16:34.079 --> 00:16:35.329 align:start position:0% Africa so<00:16:34.380> what<00:16:34.500> they<00:16:34.620> said<00:16:34.740> is<00:16:34.860> we<00:16:34.980> could<00:16:35.100> have<00:16:35.220> done 00:16:35.329 --> 00:16:35.339 align:start position:0% so what they said is we could have done 00:16:35.339 --> 00:16:37.009 align:start position:0% so what they said is we could have done this<00:16:35.459> on<00:16:35.639> our<00:16:35.760> own<00:16:35.880> with<00:16:36.060> a<00:16:36.180> database<00:16:36.540> but<00:16:36.839> we 00:16:37.009 --> 00:16:37.019 align:start position:0% this on our own with a database but we 00:16:37.019 --> 00:16:38.930 align:start position:0% this on our own with a database but we wanted<00:16:37.139> public<00:16:37.560> proof<00:16:38.040> that<00:16:38.220> those<00:16:38.459> triggers 00:16:38.930 --> 00:16:38.940 align:start position:0% wanted public proof that those triggers 00:16:38.940 --> 00:16:40.790 align:start position:0% wanted public proof that those triggers that<00:16:39.420> the<00:16:39.660> customers<00:16:39.959> signed<00:16:40.320> up<00:16:40.380> for<00:16:40.560> when 00:16:40.790 --> 00:16:40.800 align:start position:0% that the customers signed up for when 00:16:40.800 --> 00:16:43.370 align:start position:0% that the customers signed up for when buying<00:16:41.279> are<00:16:41.940> still<00:16:42.180> the<00:16:42.480> same<00:16:42.660> ones<00:16:42.959> used<00:16:43.139> when 00:16:43.370 --> 00:16:43.380 align:start position:0% buying are still the same ones used when 00:16:43.380 --> 00:16:45.350 align:start position:0% buying are still the same ones used when it<00:16:43.500> comes<00:16:43.740> time<00:16:43.860> to<00:16:44.100> pay<00:16:44.220> out<00:16:44.399> that<00:16:44.940> is<00:16:45.060> a<00:16:45.240> great 00:16:45.350 --> 00:16:45.360 align:start position:0% it comes time to pay out that is a great 00:16:45.360 --> 00:16:47.449 align:start position:0% it comes time to pay out that is a great example<00:16:45.779> of<00:16:46.199> the<00:16:46.380> transparency<00:16:46.860> that<00:16:47.220> you<00:16:47.339> get 00:16:47.449 --> 00:16:47.459 align:start position:0% example of the transparency that you get 00:16:47.459 --> 00:16:49.790 align:start position:0% example of the transparency that you get from<00:16:47.759> a<00:16:48.000> good<00:16:48.240> blockchain<00:16:48.600> solution<00:16:49.019> so 00:16:49.790 --> 00:16:49.800 align:start position:0% from a good blockchain solution so 00:16:49.800 --> 00:16:51.410 align:start position:0% from a good blockchain solution so anyway<00:16:49.920> this<00:16:50.279> is<00:16:50.339> there's<00:16:50.699> just<00:16:50.880> a<00:16:51.060> few<00:16:51.180> we 00:16:51.410 --> 00:16:51.420 align:start position:0% anyway this is there's just a few we 00:16:51.420 --> 00:16:53.210 align:start position:0% anyway this is there's just a few we have<00:16:51.540> a<00:16:51.660> lot<00:16:51.779> more 00:16:53.210 --> 00:16:53.220 align:start position:0% have a lot more 00:16:53.220 --> 00:16:54.769 align:start position:0% have a lot more um<00:16:53.279> but<00:16:53.459> these<00:16:53.699> interviews<00:16:54.060> really<00:16:54.240> helped<00:16:54.660> us 00:16:54.769 --> 00:16:54.779 align:start position:0% um but these interviews really helped us 00:16:54.779 --> 00:16:56.509 align:start position:0% um but these interviews really helped us with<00:16:55.440> the<00:16:55.620> insights<00:16:56.040> which<00:16:56.160> is<00:16:56.279> what<00:16:56.399> I'm 00:16:56.509 --> 00:16:56.519 align:start position:0% with the insights which is what I'm 00:16:56.519 --> 00:16:58.129 align:start position:0% with the insights which is what I'm going<00:16:56.639> to<00:16:56.699> get<00:16:56.820> to<00:16:56.880> shortly 00:16:58.129 --> 00:16:58.139 align:start position:0% going to get to shortly 00:16:58.139 --> 00:17:00.889 align:start position:0% going to get to shortly um<00:16:58.199> so<00:16:58.500> we<00:16:58.800> took<00:16:59.040> that<00:16:59.160> 118<00:16:59.699> projects<00:17:00.360> and 00:17:00.889 --> 00:17:00.899 align:start position:0% um so we took that 118 projects and 00:17:00.899 --> 00:17:03.110 align:start position:0% um so we took that 118 projects and whittled<00:17:01.259> it<00:17:01.380> down<00:17:01.560> to<00:17:01.800> 12<00:17:02.100> for<00:17:02.579> a<00:17:02.699> super<00:17:02.880> deep 00:17:03.110 --> 00:17:03.120 align:start position:0% whittled it down to 12 for a super deep 00:17:03.120 --> 00:17:05.150 align:start position:0% whittled it down to 12 for a super deep dive<00:17:03.540> okay<00:17:04.140> so<00:17:04.439> we<00:17:04.620> were<00:17:04.740> looking<00:17:04.860> at<00:17:04.980> doing 00:17:05.150 --> 00:17:05.160 align:start position:0% dive okay so we were looking at doing 00:17:05.160 --> 00:17:08.210 align:start position:0% dive okay so we were looking at doing case<00:17:05.459> studies<00:17:05.819> on<00:17:06.059> on<00:17:06.299> 12<00:17:06.540> of<00:17:06.780> them 00:17:08.210 --> 00:17:08.220 align:start position:0% case studies on on 12 of them 00:17:08.220 --> 00:17:10.189 align:start position:0% case studies on on 12 of them um<00:17:08.339> nine<00:17:08.760> of<00:17:08.880> the<00:17:09.059> projects<00:17:09.480> were<00:17:09.780> ready<00:17:09.959> for 00:17:10.189 --> 00:17:10.199 align:start position:0% um nine of the projects were ready for 00:17:10.199 --> 00:17:11.870 align:start position:0% um nine of the projects were ready for us<00:17:10.319> to<00:17:10.500> include<00:17:10.799> them<00:17:10.980> in<00:17:11.160> the<00:17:11.280> report<00:17:11.400> and 00:17:11.870 --> 00:17:11.880 align:start position:0% us to include them in the report and 00:17:11.880 --> 00:17:14.270 align:start position:0% us to include them in the report and three<00:17:12.000> said<00:17:12.360> we<00:17:13.199> want<00:17:13.319> to<00:17:13.439> be<00:17:13.559> there<00:17:13.799> but<00:17:14.040> not 00:17:14.270 --> 00:17:14.280 align:start position:0% three said we want to be there but not 00:17:14.280 --> 00:17:17.090 align:start position:0% three said we want to be there but not yet<00:17:14.520> talk<00:17:15.000> to<00:17:15.179> us<00:17:15.299> next<00:17:15.600> year<00:17:15.780> okay<00:17:16.620> so<00:17:16.919> we 00:17:17.090 --> 00:17:17.100 align:start position:0% yet talk to us next year okay so we 00:17:17.100 --> 00:17:18.350 align:start position:0% yet talk to us next year okay so we ended<00:17:17.280> up<00:17:17.400> with<00:17:17.520> nine<00:17:17.760> that<00:17:18.000> are<00:17:18.120> in<00:17:18.240> the 00:17:18.350 --> 00:17:18.360 align:start position:0% ended up with nine that are in the 00:17:18.360 --> 00:17:20.329 align:start position:0% ended up with nine that are in the report<00:17:18.540> I<00:17:19.500> don't<00:17:19.679> have<00:17:19.799> time<00:17:19.919> to<00:17:20.100> go<00:17:20.220> through 00:17:20.329 --> 00:17:20.339 align:start position:0% report I don't have time to go through 00:17:20.339 --> 00:17:22.429 align:start position:0% report I don't have time to go through them<00:17:20.459> I<00:17:20.699> wish<00:17:20.819> I<00:17:21.000> did<00:17:21.179> too<00:17:22.020> short<00:17:22.199> a 00:17:22.429 --> 00:17:22.439 align:start position:0% them I wish I did too short a 00:17:22.439 --> 00:17:24.770 align:start position:0% them I wish I did too short a presentation<00:17:22.799> today<00:17:23.040> but<00:17:24.000> please<00:17:24.179> do<00:17:24.419> read<00:17:24.600> it 00:17:24.770 --> 00:17:24.780 align:start position:0% presentation today but please do read it 00:17:24.780 --> 00:17:26.270 align:start position:0% presentation today but please do read it in<00:17:24.959> the<00:17:25.140> report<00:17:25.260> because<00:17:25.620> there's<00:17:25.919> a<00:17:26.040> lot<00:17:26.160> of 00:17:26.270 --> 00:17:26.280 align:start position:0% in the report because there's a lot of 00:17:26.280 --> 00:17:28.130 align:start position:0% in the report because there's a lot of great<00:17:26.400> insights<00:17:26.939> for<00:17:27.360> each<00:17:27.540> one<00:17:27.660> of<00:17:27.780> these<00:17:27.900> we 00:17:28.130 --> 00:17:28.140 align:start position:0% great insights for each one of these we 00:17:28.140 --> 00:17:30.350 align:start position:0% great insights for each one of these we did<00:17:28.319> a<00:17:28.500> detailed<00:17:28.860> case<00:17:29.040> study<00:17:29.460> and<00:17:29.940> also<00:17:30.179> put 00:17:30.350 --> 00:17:30.360 align:start position:0% did a detailed case study and also put 00:17:30.360 --> 00:17:32.330 align:start position:0% did a detailed case study and also put the<00:17:30.600> key<00:17:30.720> takeaways<00:17:31.320> for<00:17:31.799> a<00:17:32.100> business 00:17:32.330 --> 00:17:32.340 align:start position:0% the key takeaways for a business 00:17:32.340 --> 00:17:36.409 align:start position:0% the key takeaways for a business audience<00:17:33.000> again<00:17:33.780> okay 00:17:36.409 --> 00:17:36.419 align:start position:0% 00:17:36.419 --> 00:17:38.150 align:start position:0% um<00:17:36.539> so<00:17:36.780> after<00:17:37.020> all<00:17:37.260> of<00:17:37.380> that<00:17:37.500> we<00:17:37.860> tried<00:17:38.039> to 00:17:38.150 --> 00:17:38.160 align:start position:0% um so after all of that we tried to 00:17:38.160 --> 00:17:39.770 align:start position:0% um so after all of that we tried to distill<00:17:38.640> everything<00:17:39.120> that<00:17:39.360> we<00:17:39.480> had<00:17:39.600> heard 00:17:39.770 --> 00:17:39.780 align:start position:0% distill everything that we had heard 00:17:39.780 --> 00:17:41.630 align:start position:0% distill everything that we had heard into<00:17:40.020> some<00:17:40.380> some<00:17:40.620> insight<00:17:41.039> so<00:17:41.280> if<00:17:41.580> you're 00:17:41.630 --> 00:17:41.640 align:start position:0% into some some insight so if you're 00:17:41.640 --> 00:17:43.190 align:start position:0% into some some insight so if you're going<00:17:41.820> to<00:17:41.940> take<00:17:42.000> pictures<00:17:42.240> of<00:17:42.539> anything<00:17:42.720> it's 00:17:43.190 --> 00:17:43.200 align:start position:0% going to take pictures of anything it's 00:17:43.200 --> 00:17:45.890 align:start position:0% going to take pictures of anything it's probably<00:17:43.440> this<00:17:43.799> slide<00:17:44.039> and<00:17:44.220> the<00:17:44.400> next<00:17:44.460> one 00:17:45.890 --> 00:17:45.900 align:start position:0% probably this slide and the next one 00:17:45.900 --> 00:17:48.350 align:start position:0% probably this slide and the next one so<00:17:46.260> there<00:17:46.440> is<00:17:46.559> a<00:17:46.679> growing<00:17:46.919> appreciation<00:17:47.460> now 00:17:48.350 --> 00:17:48.360 align:start position:0% so there is a growing appreciation now 00:17:48.360 --> 00:17:51.529 align:start position:0% so there is a growing appreciation now um<00:17:48.480> publicly<00:17:49.080> right<00:17:49.500> of<00:17:49.740> of<00:17:50.000> an<00:17:51.000> ability<00:17:51.299> to 00:17:51.529 --> 00:17:51.539 align:start position:0% um publicly right of of an ability to 00:17:51.539 --> 00:17:54.590 align:start position:0% um publicly right of of an ability to use<00:17:51.720> the<00:17:52.020> public<00:17:52.140> blockchain<00:17:52.740> that<00:17:53.640> is<00:17:53.760> new 00:17:54.590 --> 00:17:54.600 align:start position:0% use the public blockchain that is new 00:17:54.600 --> 00:17:56.210 align:start position:0% use the public blockchain that is new that's<00:17:55.020> a<00:17:55.140> that's<00:17:55.380> a<00:17:55.559> really<00:17:55.679> good<00:17:55.860> thing<00:17:56.039> to 00:17:56.210 --> 00:17:56.220 align:start position:0% that's a that's a really good thing to 00:17:56.220 --> 00:17:58.669 align:start position:0% that's a that's a really good thing to hear<00:17:56.400> and<00:17:57.120> decentralized<00:17:57.900> business<00:17:58.080> models 00:17:58.669 --> 00:17:58.679 align:start position:0% hear and decentralized business models 00:17:58.679 --> 00:18:01.150 align:start position:0% hear and decentralized business models are<00:17:59.039> beginning<00:17:59.220> to<00:17:59.520> make<00:17:59.700> some<00:17:59.940> sense<00:18:00.240> because 00:18:01.150 --> 00:18:01.160 align:start position:0% are beginning to make some sense because 00:18:01.160 --> 00:18:04.070 align:start position:0% are beginning to make some sense because defy<00:18:02.160> right<00:18:02.640> so<00:18:03.240> people<00:18:03.419> realize<00:18:03.840> there's 00:18:04.070 --> 00:18:04.080 align:start position:0% defy right so people realize there's 00:18:04.080 --> 00:18:05.270 align:start position:0% defy right so people realize there's something<00:18:04.260> there<00:18:04.559> they<00:18:04.799> don't<00:18:04.919> know<00:18:05.039> how<00:18:05.100> to 00:18:05.270 --> 00:18:05.280 align:start position:0% something there they don't know how to 00:18:05.280 --> 00:18:07.010 align:start position:0% something there they don't know how to do<00:18:05.340> use<00:18:05.640> it<00:18:05.820> yet<00:18:05.940> they<00:18:06.120> don't<00:18:06.299> know<00:18:06.360> how<00:18:06.480> to<00:18:06.660> how 00:18:07.010 --> 00:18:07.020 align:start position:0% do use it yet they don't know how to how 00:18:07.020 --> 00:18:09.230 align:start position:0% do use it yet they don't know how to how to<00:18:07.200> make<00:18:07.320> it<00:18:07.500> work<00:18:07.679> yet<00:18:07.980> but<00:18:08.340> but<00:18:08.760> they<00:18:09.059> know 00:18:09.230 --> 00:18:09.240 align:start position:0% to make it work yet but but they know 00:18:09.240 --> 00:18:12.350 align:start position:0% to make it work yet but but they know there's<00:18:09.539> something<00:18:09.780> there<00:18:10.020> that's<00:18:10.200> important 00:18:12.350 --> 00:18:12.360 align:start position:0% there's something there that's important 00:18:12.360 --> 00:18:14.570 align:start position:0% there's something there that's important um<00:18:12.419> technological<00:18:13.080> advances<00:18:13.559> ZK<00:18:13.919> proofs<00:18:14.460> Etc 00:18:14.570 --> 00:18:14.580 align:start position:0% um technological advances ZK proofs Etc 00:18:14.580 --> 00:18:16.850 align:start position:0% um technological advances ZK proofs Etc are<00:18:14.880> addressing<00:18:15.240> the<00:18:15.419> privacy<00:18:15.720> concerns<00:18:16.260> and 00:18:16.850 --> 00:18:16.860 align:start position:0% are addressing the privacy concerns and 00:18:16.860 --> 00:18:19.250 align:start position:0% are addressing the privacy concerns and a<00:18:17.039> variety<00:18:17.280> of<00:18:17.460> the<00:18:17.580> the<00:18:17.820> upgrades 00:18:19.250 --> 00:18:19.260 align:start position:0% a variety of the the upgrades 00:18:19.260 --> 00:18:21.289 align:start position:0% a variety of the the upgrades coming<00:18:19.740> or<00:18:20.100> have<00:18:20.400> already<00:18:20.580> happened<00:18:20.820> in<00:18:21.059> in 00:18:21.289 --> 00:18:21.299 align:start position:0% coming or have already happened in in 00:18:21.299 --> 00:18:22.669 align:start position:0% coming or have already happened in in the<00:18:21.480> mainnet<00:18:21.900> are<00:18:22.080> going<00:18:22.200> to<00:18:22.260> be<00:18:22.320> addressing 00:18:22.669 --> 00:18:22.679 align:start position:0% the mainnet are going to be addressing 00:18:22.679 --> 00:18:24.890 align:start position:0% the mainnet are going to be addressing the<00:18:22.980> remaining<00:18:23.280> business<00:18:23.520> issues<00:18:23.940> over<00:18:24.120> time 00:18:24.890 --> 00:18:24.900 align:start position:0% the remaining business issues over time 00:18:24.900 --> 00:18:27.830 align:start position:0% the remaining business issues over time but<00:18:25.320> now<00:18:25.559> of<00:18:25.740> course<00:18:25.860> we<00:18:26.220> know<00:18:26.400> that 00:18:27.830 --> 00:18:27.840 align:start position:0% but now of course we know that 00:18:27.840 --> 00:18:30.350 align:start position:0% but now of course we know that you<00:18:28.320> need<00:18:28.440> to<00:18:28.559> use<00:18:28.740> multiple<00:18:29.340> uh<00:18:30.000> multiple 00:18:30.350 --> 00:18:30.360 align:start position:0% you need to use multiple uh multiple 00:18:30.360 --> 00:18:32.330 align:start position:0% you need to use multiple uh multiple layers<00:18:30.720> or<00:18:31.020> multiple<00:18:31.380> networks<00:18:31.799> in<00:18:31.980> order<00:18:32.160> to 00:18:32.330 --> 00:18:32.340 align:start position:0% layers or multiple networks in order to 00:18:32.340 --> 00:18:34.190 align:start position:0% layers or multiple networks in order to address<00:18:32.460> some<00:18:32.880> of<00:18:33.000> the<00:18:33.179> performance<00:18:33.660> and<00:18:34.020> and 00:18:34.190 --> 00:18:34.200 align:start position:0% address some of the performance and and 00:18:34.200 --> 00:18:36.409 align:start position:0% address some of the performance and and permissioning<00:18:35.340> I<00:18:35.940> want<00:18:36.059> to<00:18:36.179> talk<00:18:36.240> about 00:18:36.409 --> 00:18:36.419 align:start position:0% permissioning I want to talk about 00:18:36.419 --> 00:18:38.750 align:start position:0% permissioning I want to talk about private<00:18:36.780> and<00:18:36.900> public<00:18:37.340> blockchain<00:18:38.340> for<00:18:38.700> a 00:18:38.750 --> 00:18:38.760 align:start position:0% private and public blockchain for a 00:18:38.760 --> 00:18:41.510 align:start position:0% private and public blockchain for a moment<00:18:39.080> there<00:18:40.080> are<00:18:40.320> still<00:18:40.559> as<00:18:41.100> I<00:18:41.280> mentioned 00:18:41.510 --> 00:18:41.520 align:start position:0% moment there are still as I mentioned 00:18:41.520 --> 00:18:43.730 align:start position:0% moment there are still as I mentioned some<00:18:41.820> good<00:18:42.000> use<00:18:42.179> cases<00:18:42.539> for<00:18:42.900> uh<00:18:43.260> for<00:18:43.500> private 00:18:43.730 --> 00:18:43.740 align:start position:0% some good use cases for uh for private 00:18:43.740 --> 00:18:45.890 align:start position:0% some good use cases for uh for private blockchains<00:18:44.340> but<00:18:44.880> we're<00:18:45.059> beginning<00:18:45.299> to<00:18:45.660> see 00:18:45.890 --> 00:18:45.900 align:start position:0% blockchains but we're beginning to see 00:18:45.900 --> 00:18:48.470 align:start position:0% blockchains but we're beginning to see the<00:18:46.320> use<00:18:46.500> cases<00:18:46.919> merge<00:18:47.640> much<00:18:47.880> more<00:18:48.059> strongly 00:18:48.470 --> 00:18:48.480 align:start position:0% the use cases merge much more strongly 00:18:48.480 --> 00:18:50.270 align:start position:0% the use cases merge much more strongly than<00:18:48.720> we've<00:18:48.900> seen<00:18:49.140> before<00:18:49.320> we're<00:18:50.039> also 00:18:50.270 --> 00:18:50.280 align:start position:0% than we've seen before we're also 00:18:50.280 --> 00:18:52.130 align:start position:0% than we've seen before we're also beginning<00:18:50.400> to<00:18:50.760> see<00:18:50.880> some<00:18:51.120> hybrid<00:18:51.600> options 00:18:52.130 --> 00:18:52.140 align:start position:0% beginning to see some hybrid options 00:18:52.140 --> 00:18:53.750 align:start position:0% beginning to see some hybrid options where<00:18:52.440> people<00:18:52.559> are<00:18:52.740> using<00:18:53.039> private<00:18:53.400> for<00:18:53.580> some 00:18:53.750 --> 00:18:53.760 align:start position:0% where people are using private for some 00:18:53.760 --> 00:18:55.669 align:start position:0% where people are using private for some things<00:18:54.000> and<00:18:54.600> public<00:18:54.780> for<00:18:55.020> others<00:18:55.320> and<00:18:55.559> that's 00:18:55.669 --> 00:18:55.679 align:start position:0% things and public for others and that's 00:18:55.679 --> 00:18:57.890 align:start position:0% things and public for others and that's that's<00:18:55.980> that's<00:18:56.039> an<00:18:56.580> interesting<00:18:57.000> uh<00:18:57.480> an 00:18:57.890 --> 00:18:57.900 align:start position:0% that's that's an interesting uh an 00:18:57.900 --> 00:18:59.930 align:start position:0% that's that's an interesting uh an interesting<00:18:58.200> result<00:18:58.440> as<00:18:58.679> well<00:18:58.860> one<00:18:59.760> of<00:18:59.880> the 00:18:59.930 --> 00:18:59.940 align:start position:0% interesting result as well one of the 00:18:59.940 --> 00:19:01.789 align:start position:0% interesting result as well one of the things<00:19:00.120> we<00:19:00.240> heard<00:19:00.480> very<00:19:00.660> clearly 00:19:01.789 --> 00:19:01.799 align:start position:0% things we heard very clearly 00:19:01.799 --> 00:19:05.210 align:start position:0% things we heard very clearly was<00:19:02.520> that<00:19:02.820> l2s<00:19:03.539> and<00:19:03.600> side<00:19:03.780> chains<00:19:04.260> are<00:19:04.740> no<00:19:05.100> one 00:19:05.210 --> 00:19:05.220 align:start position:0% was that l2s and side chains are no one 00:19:05.220 --> 00:19:07.669 align:start position:0% was that l2s and side chains are no one expects<00:19:05.640> those<00:19:05.820> to<00:19:06.000> be<00:19:06.120> a<00:19:06.360> temporary<00:19:06.720> solution 00:19:07.669 --> 00:19:07.679 align:start position:0% expects those to be a temporary solution 00:19:07.679 --> 00:19:09.529 align:start position:0% expects those to be a temporary solution so<00:19:08.100> even<00:19:08.280> with<00:19:08.580> everything<00:19:08.880> that's<00:19:09.179> planned 00:19:09.529 --> 00:19:09.539 align:start position:0% so even with everything that's planned 00:19:09.539 --> 00:19:12.350 align:start position:0% so even with everything that's planned in<00:19:09.720> terms<00:19:09.960> of<00:19:10.020> upgrades<00:19:10.500> for<00:19:10.799> ethereum 00:19:12.350 --> 00:19:12.360 align:start position:0% in terms of upgrades for ethereum 00:19:12.360 --> 00:19:14.750 align:start position:0% in terms of upgrades for ethereum um<00:19:12.480> no<00:19:12.900> one<00:19:13.020> who<00:19:13.260> is<00:19:13.440> actually<00:19:13.760> building 00:19:14.750 --> 00:19:14.760 align:start position:0% um no one who is actually building 00:19:14.760 --> 00:19:17.690 align:start position:0% um no one who is actually building projects<00:19:15.360> today<00:19:15.799> believes<00:19:16.799> that<00:19:16.980> LTS<00:19:17.580> and 00:19:17.690 --> 00:19:17.700 align:start position:0% projects today believes that LTS and 00:19:17.700 --> 00:19:19.190 align:start position:0% projects today believes that LTS and side<00:19:17.820> chains<00:19:18.240> are<00:19:18.299> going<00:19:18.720> to<00:19:18.780> be<00:19:18.840> temporary 00:19:19.190 --> 00:19:19.200 align:start position:0% side chains are going to be temporary 00:19:19.200 --> 00:19:20.570 align:start position:0% side chains are going to be temporary they're<00:19:19.500> expecting<00:19:19.919> them<00:19:19.980> to<00:19:20.160> be<00:19:20.220> here<00:19:20.400> to 00:19:20.570 --> 00:19:20.580 align:start position:0% they're expecting them to be here to 00:19:20.580 --> 00:19:23.990 align:start position:0% they're expecting them to be here to stay<00:19:20.760> to<00:19:21.240> you<00:19:21.780> know<00:19:21.900> to<00:19:22.080> remain<00:19:22.380> okay 00:19:23.990 --> 00:19:24.000 align:start position:0% stay to you know to remain okay 00:19:24.000 --> 00:19:25.730 align:start position:0% stay to you know to remain okay um<00:19:24.120> when<00:19:24.360> we<00:19:24.480> first<00:19:24.660> when<00:19:25.080> we<00:19:25.200> did<00:19:25.380> the<00:19:25.559> the 00:19:25.730 --> 00:19:25.740 align:start position:0% um when we first when we did the the 00:19:25.740 --> 00:19:27.350 align:start position:0% um when we first when we did the the research<00:19:26.100> here<00:19:26.280> the<00:19:26.640> number<00:19:26.700> one<00:19:26.880> blocker 00:19:27.350 --> 00:19:27.360 align:start position:0% research here the number one blocker 00:19:27.360 --> 00:19:30.770 align:start position:0% research here the number one blocker that<00:19:27.539> was<00:19:27.660> listed<00:19:28.160> was<00:19:29.160> sustainability 00:19:30.770 --> 00:19:30.780 align:start position:0% that was listed was sustainability 00:19:30.780 --> 00:19:32.390 align:start position:0% that was listed was sustainability across<00:19:31.380> the<00:19:31.500> board 00:19:32.390 --> 00:19:32.400 align:start position:0% across the board 00:19:32.400 --> 00:19:34.730 align:start position:0% across the board this<00:19:33.360> of<00:19:33.720> course<00:19:33.900> now 00:19:34.730 --> 00:19:34.740 align:start position:0% this of course now 00:19:34.740 --> 00:19:36.529 align:start position:0% this of course now that's<00:19:35.340> not<00:19:35.520> the<00:19:35.640> big<00:19:35.760> blocker<00:19:36.120> that<00:19:36.240> it<00:19:36.419> was 00:19:36.529 --> 00:19:36.539 align:start position:0% that's not the big blocker that it was 00:19:36.539 --> 00:19:38.510 align:start position:0% that's not the big blocker that it was because<00:19:36.780> of<00:19:36.960> the<00:19:37.080> merge<00:19:37.380> so<00:19:37.980> the<00:19:38.160> second<00:19:38.340> one 00:19:38.510 --> 00:19:38.520 align:start position:0% because of the merge so the second one 00:19:38.520 --> 00:19:40.010 align:start position:0% because of the merge so the second one is<00:19:38.700> now<00:19:38.880> the<00:19:39.059> top<00:19:39.240> one<00:19:39.419> and<00:19:39.600> that<00:19:39.780> one<00:19:39.900> was 00:19:40.010 --> 00:19:40.020 align:start position:0% is now the top one and that one was 00:19:40.020 --> 00:19:41.630 align:start position:0% is now the top one and that one was regulation<00:19:40.559> and<00:19:40.799> that's<00:19:40.980> not<00:19:41.220> probably<00:19:41.460> not 00:19:41.630 --> 00:19:41.640 align:start position:0% regulation and that's not probably not 00:19:41.640 --> 00:19:43.730 align:start position:0% regulation and that's not probably not going<00:19:41.820> to<00:19:41.940> surprise<00:19:42.179> this<00:19:42.419> audience 00:19:43.730 --> 00:19:43.740 align:start position:0% going to surprise this audience 00:19:43.740 --> 00:19:45.890 align:start position:0% going to surprise this audience um<00:19:43.799> but<00:19:44.220> it's<00:19:44.940> interesting<00:19:45.360> because<00:19:45.539> it's 00:19:45.890 --> 00:19:45.900 align:start position:0% um but it's interesting because it's 00:19:45.900 --> 00:19:48.169 align:start position:0% um but it's interesting because it's actually<00:19:46.080> not<00:19:46.320> a<00:19:46.559> blocker<00:19:46.919> for<00:19:47.220> all<00:19:47.520> use<00:19:47.760> cases 00:19:48.169 --> 00:19:48.179 align:start position:0% actually not a blocker for all use cases 00:19:48.179 --> 00:19:51.409 align:start position:0% actually not a blocker for all use cases and<00:19:49.260> um<00:19:49.320> if<00:19:49.740> you<00:19:50.100> can<00:19:50.220> you<00:19:50.520> can<00:19:50.700> see<00:19:50.940> some<00:19:51.299> of 00:19:51.409 --> 00:19:51.419 align:start position:0% and um if you can you can see some of 00:19:51.419 --> 00:19:52.730 align:start position:0% and um if you can you can see some of the<00:19:51.480> use<00:19:51.600> cases<00:19:51.840> where<00:19:52.080> it's<00:19:52.260> not<00:19:52.440> in<00:19:52.620> the 00:19:52.730 --> 00:19:52.740 align:start position:0% the use cases where it's not in the 00:19:52.740 --> 00:19:54.350 align:start position:0% the use cases where it's not in the report<00:19:52.919> or<00:19:53.280> catch<00:19:53.640> me<00:19:53.700> later<00:19:53.880> and<00:19:54.120> I'm<00:19:54.240> happy 00:19:54.350 --> 00:19:54.360 align:start position:0% report or catch me later and I'm happy 00:19:54.360 --> 00:19:56.330 align:start position:0% report or catch me later and I'm happy to<00:19:54.539> talk<00:19:54.660> with<00:19:54.840> you<00:19:54.960> but<00:19:55.679> there<00:19:55.860> are<00:19:55.980> some<00:19:56.160> for 00:19:56.330 --> 00:19:56.340 align:start position:0% to talk with you but there are some for 00:19:56.340 --> 00:19:58.669 align:start position:0% to talk with you but there are some for which<00:19:56.460> it's<00:19:56.640> not<00:19:56.820> an<00:19:56.940> issue<00:19:57.179> yet<00:19:57.360> and<00:19:58.440> um<00:19:58.440> hey 00:19:58.669 --> 00:19:58.679 align:start position:0% which it's not an issue yet and um hey 00:19:58.679 --> 00:20:01.370 align:start position:0% which it's not an issue yet and um hey nfts<00:19:59.400> are<00:19:59.580> really<00:19:59.760> making<00:20:00.000> people<00:20:00.360> aware<00:20:01.020> of 00:20:01.370 --> 00:20:01.380 align:start position:0% nfts are really making people aware of 00:20:01.380 --> 00:20:03.230 align:start position:0% nfts are really making people aware of what<00:20:01.620> digital<00:20:01.919> assets<00:20:02.280> are<00:20:02.520> and<00:20:02.640> can<00:20:02.820> do<00:20:03.000> so 00:20:03.230 --> 00:20:03.240 align:start position:0% what digital assets are and can do so 00:20:03.240 --> 00:20:05.330 align:start position:0% what digital assets are and can do so that's<00:20:03.419> that's<00:20:03.720> pretty<00:20:04.020> neat 00:20:05.330 --> 00:20:05.340 align:start position:0% that's that's pretty neat 00:20:05.340 --> 00:20:07.130 align:start position:0% that's that's pretty neat um<00:20:05.400> and<00:20:05.640> then<00:20:05.700> the<00:20:05.940> final<00:20:06.120> comments<00:20:06.780> I<00:20:06.840> want<00:20:07.020> to 00:20:07.130 --> 00:20:07.140 align:start position:0% um and then the final comments I want to 00:20:07.140 --> 00:20:10.070 align:start position:0% um and then the final comments I want to make<00:20:07.200> are<00:20:07.500> that<00:20:07.799> look<00:20:08.340> we<00:20:08.760> believe<00:20:09.020> this<00:20:10.020> is 00:20:10.070 --> 00:20:10.080 align:start position:0% make are that look we believe this is 00:20:10.080 --> 00:20:12.169 align:start position:0% make are that look we believe this is going<00:20:10.200> to<00:20:10.380> sound<00:20:10.559> obvious<00:20:11.220> right<00:20:11.520> we<00:20:12.059> believe 00:20:12.169 --> 00:20:12.179 align:start position:0% going to sound obvious right we believe 00:20:12.179 --> 00:20:13.850 align:start position:0% going to sound obvious right we believe that<00:20:12.419> the<00:20:12.539> ethereum<00:20:12.840> ecosystem<00:20:13.200> is<00:20:13.500> ready<00:20:13.679> for 00:20:13.850 --> 00:20:13.860 align:start position:0% that the ethereum ecosystem is ready for 00:20:13.860 --> 00:20:15.230 align:start position:0% that the ethereum ecosystem is ready for business<00:20:14.100> of<00:20:14.580> course<00:20:14.760> we're<00:20:14.940> going<00:20:15.059> to<00:20:15.120> say 00:20:15.230 --> 00:20:15.240 align:start position:0% business of course we're going to say 00:20:15.240 --> 00:20:18.110 align:start position:0% business of course we're going to say that<00:20:15.360> no<00:20:15.660> actually<00:20:15.960> here's<00:20:16.799> the<00:20:16.860> caveat<00:20:17.340> the 00:20:18.110 --> 00:20:18.120 align:start position:0% that no actually here's the caveat the 00:20:18.120 --> 00:20:20.390 align:start position:0% that no actually here's the caveat the caveat<00:20:18.480> is<00:20:18.720> it<00:20:19.020> is<00:20:19.200> not<00:20:19.440> yet<00:20:19.679> out<00:20:19.980> of<00:20:20.100> the<00:20:20.220> box 00:20:20.390 --> 00:20:20.400 align:start position:0% caveat is it is not yet out of the box 00:20:20.400 --> 00:20:21.529 align:start position:0% caveat is it is not yet out of the box ready 00:20:21.529 --> 00:20:21.539 align:start position:0% ready 00:20:21.539 --> 00:20:25.310 align:start position:0% ready that's<00:20:22.080> the<00:20:22.380> key<00:20:22.620> result<00:20:22.980> that<00:20:23.340> we<00:20:23.460> got 00:20:25.310 --> 00:20:25.320 align:start position:0% that's the key result that we got 00:20:25.320 --> 00:20:28.130 align:start position:0% that's the key result that we got um<00:20:25.500> okay<00:20:25.919> don't<00:20:26.400> scroll<00:20:26.580> that<00:20:26.820> far<00:20:27.000> please 00:20:28.130 --> 00:20:28.140 align:start position:0% um okay don't scroll that far please 00:20:28.140 --> 00:20:29.510 align:start position:0% um okay don't scroll that far please um<00:20:28.200> all<00:20:28.500> right 00:20:29.510 --> 00:20:29.520 align:start position:0% um all right 00:20:29.520 --> 00:20:32.029 align:start position:0% um all right um<00:20:30.000> so<00:20:30.539> anyway<00:20:30.660> the<00:20:31.200> good<00:20:31.320> news<00:20:31.440> is<00:20:31.679> there<00:20:31.919> are 00:20:32.029 --> 00:20:32.039 align:start position:0% um so anyway the good news is there are 00:20:32.039 --> 00:20:33.350 align:start position:0% um so anyway the good news is there are a<00:20:32.100> lot<00:20:32.160> of<00:20:32.280> different<00:20:32.400> options<00:20:32.820> right<00:20:33.179> there 00:20:33.350 --> 00:20:33.360 align:start position:0% a lot of different options right there 00:20:33.360 --> 00:20:34.490 align:start position:0% a lot of different options right there are<00:20:33.480> a<00:20:33.539> number<00:20:33.600> of<00:20:33.720> different<00:20:33.900> architectures 00:20:34.490 --> 00:20:34.500 align:start position:0% are a number of different architectures 00:20:34.500 --> 00:20:36.890 align:start position:0% are a number of different architectures and<00:20:35.160> they're<00:20:35.340> not<00:20:35.580> bad<00:20:35.880> I<00:20:36.360> know<00:20:36.419> that<00:20:36.660> this 00:20:36.890 --> 00:20:36.900 align:start position:0% and they're not bad I know that this 00:20:36.900 --> 00:20:38.810 align:start position:0% and they're not bad I know that this community<00:20:37.080> is<00:20:37.440> trying<00:20:37.620> to<00:20:37.799> push<00:20:38.039> the<00:20:38.400> the 00:20:38.810 --> 00:20:38.820 align:start position:0% community is trying to push the the 00:20:38.820 --> 00:20:41.510 align:start position:0% community is trying to push the the edges<00:20:39.240> at<00:20:40.140> the<00:20:40.320> EA<00:20:40.559> we're<00:20:40.799> trying<00:20:40.980> to<00:20:41.160> move<00:20:41.280> the 00:20:41.510 --> 00:20:41.520 align:start position:0% edges at the EA we're trying to move the 00:20:41.520 --> 00:20:42.289 align:start position:0% edges at the EA we're trying to move the middle 00:20:42.289 --> 00:20:42.299 align:start position:0% middle 00:20:42.299 --> 00:20:44.750 align:start position:0% middle okay<00:20:42.900> and<00:20:43.260> so<00:20:43.500> it's<00:20:43.799> helpful<00:20:44.100> for<00:20:44.400> us<00:20:44.520> to<00:20:44.700> be 00:20:44.750 --> 00:20:44.760 align:start position:0% okay and so it's helpful for us to be 00:20:44.760 --> 00:20:46.010 align:start position:0% okay and so it's helpful for us to be able<00:20:44.880> to<00:20:45.000> explain<00:20:45.120> that<00:20:45.600> there<00:20:45.840> are 00:20:46.010 --> 00:20:46.020 align:start position:0% able to explain that there are 00:20:46.020 --> 00:20:48.409 align:start position:0% able to explain that there are alternatives<00:20:46.500> today<00:20:46.860> and 00:20:48.409 --> 00:20:48.419 align:start position:0% alternatives today and 00:20:48.419 --> 00:20:49.789 align:start position:0% alternatives today and um and<00:20:48.660> those<00:20:48.840> Alternatives<00:20:49.260> will<00:20:49.500> get<00:20:49.679> you 00:20:49.789 --> 00:20:49.799 align:start position:0% um and those Alternatives will get you 00:20:49.799 --> 00:20:52.010 align:start position:0% um and those Alternatives will get you moving<00:20:50.160> and<00:20:50.580> you<00:20:50.760> don't<00:20:50.880> want<00:20:51.000> to<00:20:51.179> wait 00:20:52.010 --> 00:20:52.020 align:start position:0% moving and you don't want to wait 00:20:52.020 --> 00:20:53.810 align:start position:0% moving and you don't want to wait there<00:20:52.500> are<00:20:52.740> good<00:20:52.919> reasons<00:20:53.280> to<00:20:53.520> explore 00:20:53.810 --> 00:20:53.820 align:start position:0% there are good reasons to explore 00:20:53.820 --> 00:20:56.450 align:start position:0% there are good reasons to explore decentralized<00:20:54.660> models<00:20:55.080> okay 00:20:56.450 --> 00:20:56.460 align:start position:0% decentralized models okay 00:20:56.460 --> 00:20:58.610 align:start position:0% decentralized models okay um<00:20:56.520> of<00:20:56.820> the<00:20:57.059> you<00:20:57.660> know<00:20:57.780> and<00:20:58.080> and<00:20:58.260> to<00:20:58.500> take 00:20:58.610 --> 00:20:58.620 align:start position:0% um of the you know and and to take 00:20:58.620 --> 00:21:00.289 align:start position:0% um of the you know and and to take advantage<00:20:58.980> of<00:20:59.220> the<00:20:59.340> processes<00:20:59.760> of<00:20:59.940> the<00:21:00.059> type 00:21:00.289 --> 00:21:00.299 align:start position:0% advantage of the processes of the type 00:21:00.299 --> 00:21:02.750 align:start position:0% advantage of the processes of the type ethereum<00:21:01.080> makes<00:21:01.260> possible 00:21:02.750 --> 00:21:02.760 align:start position:0% ethereum makes possible 00:21:02.760 --> 00:21:04.190 align:start position:0% ethereum makes possible um<00:21:02.880> one<00:21:03.059> of<00:21:03.179> the<00:21:03.299> quotes<00:21:03.419> that<00:21:03.720> we<00:21:03.840> heard<00:21:03.960> was 00:21:04.190 --> 00:21:04.200 align:start position:0% um one of the quotes that we heard was 00:21:04.200 --> 00:21:05.870 align:start position:0% um one of the quotes that we heard was since<00:21:04.380> what<00:21:04.620> previously<00:21:05.039> relied<00:21:05.460> on<00:21:05.580> faith 00:21:05.870 --> 00:21:05.880 align:start position:0% since what previously relied on faith 00:21:05.880 --> 00:21:07.730 align:start position:0% since what previously relied on faith between<00:21:06.000> two<00:21:06.299> or<00:21:06.419> more<00:21:06.600> parties<00:21:06.960> can<00:21:07.440> now<00:21:07.620> be 00:21:07.730 --> 00:21:07.740 align:start position:0% between two or more parties can now be 00:21:07.740 --> 00:21:09.289 align:start position:0% between two or more parties can now be proven<00:21:08.039> mathematically<00:21:08.580> on<00:21:08.820> a<00:21:08.940> blockchain 00:21:09.289 --> 00:21:09.299 align:start position:0% proven mathematically on a blockchain 00:21:09.299 --> 00:21:11.690 align:start position:0% proven mathematically on a blockchain any<00:21:10.080> situation<00:21:10.440> which<00:21:10.740> someone<00:21:10.919> has<00:21:11.160> to<00:21:11.280> say<00:21:11.460> I 00:21:11.690 --> 00:21:11.700 align:start position:0% any situation which someone has to say I 00:21:11.700 --> 00:21:14.029 align:start position:0% any situation which someone has to say I have<00:21:11.880> to<00:21:12.000> trust<00:21:12.299> you<00:21:12.539> is<00:21:13.080> an<00:21:13.320> opportunity<00:21:13.740> for 00:21:14.029 --> 00:21:14.039 align:start position:0% have to trust you is an opportunity for 00:21:14.039 --> 00:21:16.190 align:start position:0% have to trust you is an opportunity for a<00:21:14.160> blockchain<00:21:14.520> based<00:21:14.940> solution<00:21:15.179> today<00:21:15.900> we 00:21:16.190 --> 00:21:16.200 align:start position:0% a blockchain based solution today we 00:21:16.200 --> 00:21:17.510 align:start position:0% a blockchain based solution today we increasingly<00:21:16.620> see<00:21:16.799> this<00:21:16.980> being<00:21:17.160> put<00:21:17.400> into 00:21:17.510 --> 00:21:17.520 align:start position:0% increasingly see this being put into 00:21:17.520 --> 00:21:19.490 align:start position:0% increasingly see this being put into practice<00:21:17.820> going<00:21:18.660> forward<00:21:18.780> the<00:21:19.080> opportunities 00:21:19.490 --> 00:21:19.500 align:start position:0% practice going forward the opportunities 00:21:19.500 --> 00:21:20.990 align:start position:0% practice going forward the opportunities are<00:21:19.740> as<00:21:19.860> numerous<00:21:20.160> as<00:21:20.340> the<00:21:20.520> Myriad<00:21:20.820> business 00:21:20.990 --> 00:21:21.000 align:start position:0% are as numerous as the Myriad business 00:21:21.000 --> 00:21:22.669 align:start position:0% are as numerous as the Myriad business challenges<00:21:21.539> that<00:21:21.720> depend<00:21:22.020> on<00:21:22.200> this<00:21:22.380> kind<00:21:22.559> of 00:21:22.669 --> 00:21:22.679 align:start position:0% challenges that depend on this kind of 00:21:22.679 --> 00:21:23.930 align:start position:0% challenges that depend on this kind of trust 00:21:23.930 --> 00:21:23.940 align:start position:0% trust 00:21:23.940 --> 00:21:27.409 align:start position:0% trust okay<00:21:24.539> so<00:21:25.200> here's<00:21:25.620> my<00:21:25.740> eea<00:21:26.160> slide 00:21:27.409 --> 00:21:27.419 align:start position:0% okay so here's my eea slide 00:21:27.419 --> 00:21:29.570 align:start position:0% okay so here's my eea slide um on<00:21:27.900> the<00:21:27.960> left<00:21:28.080> is<00:21:28.380> free<00:21:28.620> materials<00:21:29.159> on<00:21:29.460> the 00:21:29.570 --> 00:21:29.580 align:start position:0% um on the left is free materials on the 00:21:29.580 --> 00:21:31.789 align:start position:0% um on the left is free materials on the right<00:21:29.700> is<00:21:30.059> what<00:21:30.360> members<00:21:30.659> get<00:21:30.900> I'm<00:21:31.500> not<00:21:31.679> going 00:21:31.789 --> 00:21:31.799 align:start position:0% right is what members get I'm not going 00:21:31.799 --> 00:21:33.049 align:start position:0% right is what members get I'm not going to<00:21:31.919> walk<00:21:32.039> through<00:21:32.220> all<00:21:32.340> of<00:21:32.460> it<00:21:32.580> but<00:21:32.700> I<00:21:32.820> want<00:21:32.940> to 00:21:33.049 --> 00:21:33.059 align:start position:0% to walk through all of it but I want to 00:21:33.059 --> 00:21:35.210 align:start position:0% to walk through all of it but I want to talk<00:21:33.120> about<00:21:33.240> on<00:21:33.539> the<00:21:33.720> left<00:21:33.840> side<00:21:34.159> we<00:21:35.159> have 00:21:35.210 --> 00:21:35.220 align:start position:0% talk about on the left side we have 00:21:35.220 --> 00:21:36.649 align:start position:0% talk about on the left side we have primers<00:21:35.700> that<00:21:35.880> we're<00:21:36.000> putting<00:21:36.299> out<00:21:36.419> there 00:21:36.649 --> 00:21:36.659 align:start position:0% primers that we're putting out there 00:21:36.659 --> 00:21:38.450 align:start position:0% primers that we're putting out there basically<00:21:37.140> if<00:21:37.620> you<00:21:37.740> remember<00:21:37.860> like<00:21:38.280> the 00:21:38.450 --> 00:21:38.460 align:start position:0% basically if you remember like the 00:21:38.460 --> 00:21:41.510 align:start position:0% basically if you remember like the college<00:21:38.640> you<00:21:39.299> know<00:21:39.419> plastic<00:21:40.320> two-sided<00:21:41.220> sheet 00:21:41.510 --> 00:21:41.520 align:start position:0% college you know plastic two-sided sheet 00:21:41.520 --> 00:21:43.370 align:start position:0% college you know plastic two-sided sheet cheat<00:21:41.700> sheets<00:21:42.120> were<00:21:42.360> for<00:21:42.600> algebra<00:21:43.020> or 00:21:43.370 --> 00:21:43.380 align:start position:0% cheat sheets were for algebra or 00:21:43.380 --> 00:21:45.590 align:start position:0% cheat sheets were for algebra or whatever<00:21:43.500> else<00:21:44.000> that's<00:21:45.000> what<00:21:45.179> we're<00:21:45.299> putting 00:21:45.590 --> 00:21:45.600 align:start position:0% whatever else that's what we're putting 00:21:45.600 --> 00:21:47.270 align:start position:0% whatever else that's what we're putting out<00:21:45.720> and<00:21:46.080> they're<00:21:46.260> targeted<00:21:46.799> at 00:21:47.270 --> 00:21:47.280 align:start position:0% out and they're targeted at 00:21:47.280 --> 00:21:50.210 align:start position:0% out and they're targeted at non-technical<00:21:48.240> business<00:21:48.539> people<00:21:49.220> c-suites 00:21:50.210 --> 00:21:50.220 align:start position:0% non-technical business people c-suites 00:21:50.220 --> 00:21:51.590 align:start position:0% non-technical business people c-suites in<00:21:50.400> general<00:21:50.520> we<00:21:51.000> want<00:21:51.120> to<00:21:51.240> make<00:21:51.360> sure<00:21:51.480> they 00:21:51.590 --> 00:21:51.600 align:start position:0% in general we want to make sure they 00:21:51.600 --> 00:21:53.029 align:start position:0% in general we want to make sure they understand<00:21:51.840> the<00:21:52.200> trade-offs<00:21:52.679> of<00:21:52.799> the<00:21:52.919> things 00:21:53.029 --> 00:21:53.039 align:start position:0% understand the trade-offs of the things 00:21:53.039 --> 00:21:54.590 align:start position:0% understand the trade-offs of the things that<00:21:53.159> we're<00:21:53.280> talking<00:21:53.460> about<00:21:53.640> they<00:21:54.299> are<00:21:54.419> free 00:21:54.590 --> 00:21:54.600 align:start position:0% that we're talking about they are free 00:21:54.600 --> 00:21:56.090 align:start position:0% that we're talking about they are free to<00:21:54.780> download<00:21:54.960> and<00:21:55.260> use<00:21:55.440> they're<00:21:55.679> under<00:21:55.860> our 00:21:56.090 --> 00:21:56.100 align:start position:0% to download and use they're under our 00:21:56.100 --> 00:21:57.649 align:start position:0% to download and use they're under our resources<00:21:56.580> tab 00:21:57.649 --> 00:21:57.659 align:start position:0% resources tab 00:21:57.659 --> 00:21:59.090 align:start position:0% resources tab we<00:21:58.140> also<00:21:58.380> have<00:21:58.440> a<00:21:58.620> large<00:21:58.740> number<00:21:58.919> of 00:21:59.090 --> 00:21:59.100 align:start position:0% we also have a large number of 00:21:59.100 --> 00:22:01.310 align:start position:0% we also have a large number of educational<00:21:59.400> webinars<00:22:00.120> blogs<00:22:00.659> we<00:22:01.200> hold 00:22:01.310 --> 00:22:01.320 align:start position:0% educational webinars blogs we hold 00:22:01.320 --> 00:22:03.230 align:start position:0% educational webinars blogs we hold events<00:22:01.799> and<00:22:01.980> so<00:22:02.100> on<00:22:02.280> one<00:22:02.700> of<00:22:02.820> the<00:22:02.940> things<00:22:03.000> that 00:22:03.230 --> 00:22:03.240 align:start position:0% events and so on one of the things that 00:22:03.240 --> 00:22:05.149 align:start position:0% events and so on one of the things that we<00:22:03.480> just<00:22:03.720> launched<00:22:04.320> this<00:22:04.500> week<00:22:04.679> it's<00:22:04.919> brand 00:22:05.149 --> 00:22:05.159 align:start position:0% we just launched this week it's brand 00:22:05.159 --> 00:22:07.610 align:start position:0% we just launched this week it's brand new<00:22:05.340> so<00:22:06.120> hit<00:22:06.299> it<00:22:06.539> hard<00:22:06.780> and<00:22:07.140> expect<00:22:07.320> some 00:22:07.610 --> 00:22:07.620 align:start position:0% new so hit it hard and expect some 00:22:07.620 --> 00:22:10.490 align:start position:0% new so hit it hard and expect some problems<00:22:08.039> but<00:22:08.280> we<00:22:08.460> do<00:22:08.640> want<00:22:08.820> you<00:22:09.000> to<00:22:09.120> try<00:22:09.299> it<00:22:09.500> on 00:22:10.490 --> 00:22:10.500 align:start position:0% problems but we do want you to try it on 00:22:10.500 --> 00:22:12.710 align:start position:0% problems but we do want you to try it on our<00:22:10.620> website<00:22:11.039> lower<00:22:11.700> right<00:22:11.940> corner<00:22:12.360> there's<00:22:12.539> a 00:22:12.710 --> 00:22:12.720 align:start position:0% our website lower right corner there's a 00:22:12.720 --> 00:22:15.649 align:start position:0% our website lower right corner there's a chat<00:22:12.960> a<00:22:13.919> chat<00:22:14.220> icon 00:22:15.649 --> 00:22:15.659 align:start position:0% chat a chat icon 00:22:15.659 --> 00:22:17.330 align:start position:0% chat a chat icon um look<00:22:16.080> at<00:22:16.260> some<00:22:16.440> of<00:22:16.500> the<00:22:16.620> options<00:22:16.919> that<00:22:17.159> come 00:22:17.330 --> 00:22:17.340 align:start position:0% um look at some of the options that come 00:22:17.340 --> 00:22:19.070 align:start position:0% um look at some of the options that come up<00:22:17.520> but<00:22:17.760> the<00:22:17.940> reason<00:22:18.059> we<00:22:18.240> did<00:22:18.419> that<00:22:18.600> is<00:22:18.780> that's 00:22:19.070 --> 00:22:19.080 align:start position:0% up but the reason we did that is that's 00:22:19.080 --> 00:22:21.169 align:start position:0% up but the reason we did that is that's intended<00:22:19.500> to<00:22:19.559> be<00:22:19.679> a<00:22:19.799> help<00:22:19.919> desk<00:22:20.220> it<00:22:20.820> has<00:22:20.940> a<00:22:21.120> help 00:22:21.169 --> 00:22:21.179 align:start position:0% intended to be a help desk it has a help 00:22:21.179 --> 00:22:23.210 align:start position:0% intended to be a help desk it has a help desk<00:22:21.419> for<00:22:21.720> business<00:22:21.900> people<00:22:22.260> one<00:22:23.039> of<00:22:23.159> the 00:22:23.210 --> 00:22:23.220 align:start position:0% desk for business people one of the 00:22:23.220 --> 00:22:24.649 align:start position:0% desk for business people one of the things<00:22:23.340> we<00:22:23.580> heard<00:22:23.760> most<00:22:24.179> often<00:22:24.480> from 00:22:24.649 --> 00:22:24.659 align:start position:0% things we heard most often from 00:22:24.659 --> 00:22:27.529 align:start position:0% things we heard most often from businesses<00:22:25.140> was<00:22:25.440> look<00:22:26.400> I<00:22:26.700> can<00:22:26.820> call<00:22:27.059> anybody 00:22:27.529 --> 00:22:27.539 align:start position:0% businesses was look I can call anybody 00:22:27.539 --> 00:22:29.270 align:start position:0% businesses was look I can call anybody that<00:22:27.840> I<00:22:28.020> do<00:22:28.140> business<00:22:28.380> with<00:22:28.679> but<00:22:28.860> how<00:22:29.100> do<00:22:29.220> I 00:22:29.270 --> 00:22:29.280 align:start position:0% that I do business with but how do I 00:22:29.280 --> 00:22:30.950 align:start position:0% that I do business with but how do I call<00:22:29.460> ethereum 00:22:30.950 --> 00:22:30.960 align:start position:0% call ethereum 00:22:30.960 --> 00:22:33.110 align:start position:0% call ethereum that<00:22:31.500> is<00:22:31.679> literally<00:22:31.919> what<00:22:32.159> they<00:22:32.340> said<00:22:32.460> how<00:22:33.000> do 00:22:33.110 --> 00:22:33.120 align:start position:0% that is literally what they said how do 00:22:33.120 --> 00:22:35.510 align:start position:0% that is literally what they said how do I<00:22:33.240> call<00:22:33.360> ethereum<00:22:33.900> so<00:22:34.620> our<00:22:34.860> goal<00:22:35.100> was<00:22:35.280> to 00:22:35.510 --> 00:22:35.520 align:start position:0% I call ethereum so our goal was to 00:22:35.520 --> 00:22:38.029 align:start position:0% I call ethereum so our goal was to create<00:22:35.760> a<00:22:36.240> front<00:22:36.419> end<00:22:36.600> that<00:22:37.140> makes<00:22:37.260> it<00:22:37.440> easy<00:22:37.620> to 00:22:38.029 --> 00:22:38.039 align:start position:0% create a front end that makes it easy to 00:22:38.039 --> 00:22:40.190 align:start position:0% create a front end that makes it easy to answer<00:22:38.220> some<00:22:38.580> of<00:22:38.700> those<00:22:38.880> initial<00:22:39.480> business 00:22:40.190 --> 00:22:40.200 align:start position:0% answer some of those initial business 00:22:40.200 --> 00:22:42.529 align:start position:0% answer some of those initial business questions<00:22:40.620> that<00:22:41.039> people<00:22:41.159> have<00:22:41.520> our<00:22:42.240> goal<00:22:42.480> is 00:22:42.529 --> 00:22:42.539 align:start position:0% questions that people have our goal is 00:22:42.539 --> 00:22:43.730 align:start position:0% questions that people have our goal is not<00:22:42.720> to<00:22:42.840> steer<00:22:43.080> them<00:22:43.200> to<00:22:43.380> a<00:22:43.500> particular 00:22:43.730 --> 00:22:43.740 align:start position:0% not to steer them to a particular 00:22:43.740 --> 00:22:46.190 align:start position:0% not to steer them to a particular provider<00:22:44.280> but<00:22:44.760> to<00:22:45.000> help<00:22:45.120> get<00:22:45.360> that<00:22:45.659> initial 00:22:46.190 --> 00:22:46.200 align:start position:0% provider but to help get that initial 00:22:46.200 --> 00:22:48.169 align:start position:0% provider but to help get that initial understanding<00:22:46.860> out<00:22:47.100> of<00:22:47.220> the<00:22:47.340> way<00:22:47.460> so<00:22:48.000> when 00:22:48.169 --> 00:22:48.179 align:start position:0% understanding out of the way so when 00:22:48.179 --> 00:22:50.390 align:start position:0% understanding out of the way so when they<00:22:48.360> come<00:22:48.480> to<00:22:48.720> talk<00:22:48.900> to<00:22:49.080> you<00:22:49.320> they<00:22:50.039> have<00:22:50.159> some 00:22:50.390 --> 00:22:50.400 align:start position:0% they come to talk to you they have some 00:22:50.400 --> 00:22:52.370 align:start position:0% they come to talk to you they have some idea<00:22:50.700> what<00:22:50.880> they're<00:22:51.059> talking<00:22:51.240> about 00:22:52.370 --> 00:22:52.380 align:start position:0% idea what they're talking about 00:22:52.380 --> 00:22:54.470 align:start position:0% idea what they're talking about all<00:22:52.740> right<00:22:52.980> and<00:22:53.520> the<00:22:53.640> last<00:22:53.760> thing<00:22:54.000> I<00:22:54.179> want<00:22:54.299> to 00:22:54.470 --> 00:22:54.480 align:start position:0% all right and the last thing I want to 00:22:54.480 --> 00:22:56.630 align:start position:0% all right and the last thing I want to put<00:22:54.720> up<00:22:54.840> here<00:22:55.020> is<00:22:55.380> uh<00:22:55.740> there's<00:22:56.100> lots<00:22:56.340> more<00:22:56.460> in 00:22:56.630 --> 00:22:56.640 align:start position:0% put up here is uh there's lots more in 00:22:56.640 --> 00:22:58.250 align:start position:0% put up here is uh there's lots more in the<00:22:56.760> report<00:22:56.940> you<00:22:57.299> can<00:22:57.419> download<00:22:57.600> it<00:22:57.840> for<00:22:58.080> free 00:22:58.250 --> 00:22:58.260 align:start position:0% the report you can download it for free 00:22:58.260 --> 00:23:00.890 align:start position:0% the report you can download it for free that<00:22:59.039> QR<00:22:59.340> code<00:22:59.520> will<00:22:59.760> take<00:22:59.940> you<00:23:00.059> to<00:23:00.240> that<00:23:00.480> URL 00:23:00.890 --> 00:23:00.900 align:start position:0% that QR code will take you to that URL 00:23:00.900 --> 00:23:02.570 align:start position:0% that QR code will take you to that URL which<00:23:01.200> takes<00:23:01.320> you<00:23:01.500> to<00:23:01.620> our<00:23:01.740> website<00:23:02.039> where<00:23:02.340> you 00:23:02.570 --> 00:23:02.580 align:start position:0% which takes you to our website where you 00:23:02.580 --> 00:23:06.710 align:start position:0% which takes you to our website where you can<00:23:03.020> you<00:23:04.020> can<00:23:04.200> download<00:23:04.380> the<00:23:04.740> report<00:23:04.919> so<00:23:05.720> with 00:23:06.710 --> 00:23:06.720 align:start position:0% can you can download the report so with 00:23:06.720 --> 00:23:08.510 align:start position:0% can you can download the report so with that<00:23:06.900> I'm<00:23:07.559> going<00:23:07.799> to 00:23:08.510 --> 00:23:08.520 align:start position:0% that I'm going to 00:23:08.520 --> 00:23:10.390 align:start position:0% that I'm going to see<00:23:08.940> if<00:23:09.120> Dan<00:23:09.299> has 00:23:10.390 --> 00:23:10.400 align:start position:0% see if Dan has 00:23:10.400 --> 00:23:12.710 align:start position:0% see if Dan has anything<00:23:11.400> he'd<00:23:11.700> like<00:23:11.880> to<00:23:11.940> finish<00:23:12.059> with<00:23:12.299> great 00:23:12.710 --> 00:23:12.720 align:start position:0% anything he'd like to finish with great 00:23:12.720 --> 00:23:14.210 align:start position:0% anything he'd like to finish with great thanks<00:23:13.200> Dan 00:23:14.210 --> 00:23:14.220 align:start position:0% thanks Dan 00:23:14.220 --> 00:23:14.950 align:start position:0% thanks Dan um 00:23:14.950 --> 00:23:14.960 align:start position:0% um 00:23:14.960 --> 00:23:19.810 align:start position:0% um so<00:23:15.960> you<00:23:16.740> know<00:23:16.860> uh<00:23:17.820> for<00:23:18.000> 2022<00:23:18.600> we<00:23:18.960> got<00:23:19.200> through 00:23:19.810 --> 00:23:19.820 align:start position:0% so you know uh for 2022 we got through 00:23:19.820 --> 00:23:23.750 align:start position:0% so you know uh for 2022 we got through uh<00:23:20.820> 100<00:23:21.059> projects<00:23:21.780> and<00:23:22.620> you<00:23:22.919> know<00:23:23.039> got<00:23:23.220> down<00:23:23.460> to 00:23:23.750 --> 00:23:23.760 align:start position:0% uh 100 projects and you know got down to 00:23:23.760 --> 00:23:26.450 align:start position:0% uh 100 projects and you know got down to you<00:23:24.179> know<00:23:24.299> just<00:23:24.480> just<00:23:24.720> to<00:23:25.020> uh<00:23:25.860> just<00:23:26.100> a<00:23:26.220> few<00:23:26.340> of 00:23:26.450 --> 00:23:26.460 align:start position:0% you know just just to uh just a few of 00:23:26.460 --> 00:23:27.590 align:start position:0% you know just just to uh just a few of them 00:23:27.590 --> 00:23:27.600 align:start position:0% them 00:23:27.600 --> 00:23:28.850 align:start position:0% them um<00:23:27.720> you<00:23:27.840> know<00:23:27.960> kind<00:23:28.080> of<00:23:28.200> the<00:23:28.260> call<00:23:28.440> to<00:23:28.559> action 00:23:28.850 --> 00:23:28.860 align:start position:0% um you know kind of the call to action 00:23:28.860 --> 00:23:31.669 align:start position:0% um you know kind of the call to action is<00:23:29.640> uh<00:23:30.600> you<00:23:30.840> know<00:23:30.900> if<00:23:31.080> you<00:23:31.200> have<00:23:31.380> a<00:23:31.559> project 00:23:31.669 --> 00:23:31.679 align:start position:0% is uh you know if you have a project 00:23:31.679 --> 00:23:33.409 align:start position:0% is uh you know if you have a project that<00:23:31.919> you're<00:23:32.039> working<00:23:32.280> on 00:23:33.409 --> 00:23:33.419 align:start position:0% that you're working on 00:23:33.419 --> 00:23:36.350 align:start position:0% that you're working on um<00:23:33.539> grab<00:23:33.900> a<00:23:34.020> Dan<00:23:34.200> any<00:23:34.500> Dan<00:23:34.799> will<00:23:35.039> do<00:23:35.360> uh 00:23:36.350 --> 00:23:36.360 align:start position:0% um grab a Dan any Dan will do uh 00:23:36.360 --> 00:23:38.510 align:start position:0% um grab a Dan any Dan will do uh probably<00:23:36.539> one<00:23:36.840> of<00:23:36.960> these<00:23:37.080> dance<00:23:37.260> uh<00:23:38.159> or 00:23:38.510 --> 00:23:38.520 align:start position:0% probably one of these dance uh or 00:23:38.520 --> 00:23:40.610 align:start position:0% probably one of these dance uh or anybody<00:23:39.000> at<00:23:39.419> the<00:23:39.720> uh<00:23:40.260> the<00:23:40.500> Enterprise 00:23:40.610 --> 00:23:40.620 align:start position:0% anybody at the uh the Enterprise 00:23:40.620 --> 00:23:43.850 align:start position:0% anybody at the uh the Enterprise ethereum<00:23:41.220> Alliance<00:23:41.520> the<00:23:41.700> EA<00:23:42.320> and<00:23:43.320> uh<00:23:43.740> yeah 00:23:43.850 --> 00:23:43.860 align:start position:0% ethereum Alliance the EA and uh yeah 00:23:43.860 --> 00:23:46.430 align:start position:0% ethereum Alliance the EA and uh yeah we'd<00:23:44.280> love<00:23:44.460> to<00:23:44.640> uh<00:23:45.360> you<00:23:45.539> know<00:23:45.659> hear<00:23:46.080> about<00:23:46.260> your 00:23:46.430 --> 00:23:46.440 align:start position:0% we'd love to uh you know hear about your 00:23:46.440 --> 00:23:48.590 align:start position:0% we'd love to uh you know hear about your project<00:23:46.620> and<00:23:47.340> uh<00:23:48.000> you<00:23:48.240> know<00:23:48.360> potentially 00:23:48.590 --> 00:23:48.600 align:start position:0% project and uh you know potentially 00:23:48.600 --> 00:23:51.770 align:start position:0% project and uh you know potentially included<00:23:49.020> in<00:23:49.559> uh<00:23:49.919> next<00:23:50.700> year's<00:23:51.000> report 00:23:51.770 --> 00:23:51.780 align:start position:0% included in uh next year's report 00:23:51.780 --> 00:23:54.169 align:start position:0% included in uh next year's report Yep<00:23:52.320> this<00:23:52.620> was<00:23:52.740> the<00:23:52.919> first<00:23:53.039> one 00:23:54.169 --> 00:23:54.179 align:start position:0% Yep this was the first one 00:23:54.179 --> 00:23:56.390 align:start position:0% Yep this was the first one keep<00:23:54.659> sending<00:23:55.020> them<00:23:55.140> in<00:23:55.320> so<00:23:55.500> we<00:23:55.679> can<00:23:55.860> we<00:23:56.100> can<00:23:56.280> do 00:23:56.390 --> 00:23:56.400 align:start position:0% keep sending them in so we can we can do 00:23:56.400 --> 00:24:01.010 align:start position:0% keep sending them in so we can we can do more<00:23:56.940> thanks<00:23:57.559> thank<00:23:58.559> you 00:24:01.010 --> 00:24:01.020 align:start position:0% 00:24:01.020 --> 00:24:04.730 align:start position:0% okay<00:24:01.500> thank<00:24:02.340> you<00:24:02.520> so<00:24:02.700> much<00:24:02.960> for<00:24:03.960> this<00:24:04.140> amazing 00:24:04.730 --> 00:24:04.740 align:start position:0% okay thank you so much for this amazing 00:24:04.740 --> 00:24:08.330 align:start position:0% okay thank you so much for this amazing overview<00:24:05.159> of<00:24:05.400> the<00:24:05.940> eea<00:24:06.600> it's<00:24:06.960> been<00:24:07.340> impacting 00:24:08.330 --> 00:24:08.340 align:start position:0% overview of the eea it's been impacting 00:24:08.340 --> 00:24:10.190 align:start position:0% overview of the eea it's been impacting the<00:24:08.700> Enterprise<00:24:08.940> adoption<00:24:09.659> thank<00:24:09.960> you<00:24:10.080> so 00:24:10.190 --> 00:24:10.200 align:start position:0% the Enterprise adoption thank you so 00:24:10.200 --> 00:24:14.210 align:start position:0% the Enterprise adoption thank you so much<00:24:10.700> and<00:24:11.700> so<00:24:12.240> uh<00:24:12.659> should<00:24:12.960> we<00:24:13.080> leave<00:24:13.260> now 00:24:14.210 --> 00:24:14.220 align:start position:0% much and so uh should we leave now 00:24:14.220 --> 00:24:16.430 align:start position:0% much and so uh should we leave now yeah<00:24:14.520> but<00:24:15.120> thank<00:24:15.360> you<00:24:15.480> but<00:24:15.720> there's<00:24:15.960> some<00:24:16.200> few 00:24:16.430 --> 00:24:16.440 align:start position:0% yeah but thank you but there's some few 00:24:16.440 --> 00:24:19.010 align:start position:0% yeah but thank you but there's some few minutes<00:24:16.640> okay<00:24:17.640> maybe<00:24:18.120> if<00:24:18.419> there's<00:24:18.659> questions 00:24:19.010 --> 00:24:19.020 align:start position:0% minutes okay maybe if there's questions 00:24:19.020 --> 00:24:22.190 align:start position:0% minutes okay maybe if there's questions uh<00:24:20.340> yeah<00:24:20.940> well<00:24:21.179> we<00:24:21.419> have<00:24:21.480> a<00:24:21.659> lot<00:24:21.900> of<00:24:21.960> questions 00:24:22.190 --> 00:24:22.200 align:start position:0% uh yeah well we have a lot of questions 00:24:22.200 --> 00:24:24.409 align:start position:0% uh yeah well we have a lot of questions so<00:24:22.440> we<00:24:22.620> can<00:24:22.740> start<00:24:22.919> there 00:24:24.409 --> 00:24:24.419 align:start position:0% so we can start there 00:24:24.419 --> 00:24:27.950 align:start position:0% so we can start there hi 00:24:27.950 --> 00:24:27.960 align:start position:0% 00:24:27.960 --> 00:24:30.649 align:start position:0% we<00:24:28.740> are<00:24:28.919> going<00:24:29.100> to<00:24:29.280> give<00:24:29.580> you<00:24:29.700> the<00:24:29.940> microphones 00:24:30.649 --> 00:24:30.659 align:start position:0% we are going to give you the microphones 00:24:30.659 --> 00:24:35.330 align:start position:0% we are going to give you the microphones yeah 00:24:35.330 --> 00:24:35.340 align:start position:0% 00:24:35.340 --> 00:24:42.590 align:start position:0% yeah for<00:24:36.000> the<00:24:36.179> people<00:24:36.419> that 00:24:42.590 --> 00:24:42.600 align:start position:0% 00:24:42.600 --> 00:24:45.289 align:start position:0% I<00:24:43.140> so<00:24:43.919> um<00:24:43.980> can<00:24:44.220> you<00:24:44.400> share<00:24:44.640> some<00:24:44.940> specific 00:24:45.289 --> 00:24:45.299 align:start position:0% I so um can you share some specific 00:24:45.299 --> 00:24:48.830 align:start position:0% I so um can you share some specific examples<00:24:45.960> of<00:24:46.580> specific<00:24:47.580> businesses<00:24:48.299> who<00:24:48.720> are 00:24:48.830 --> 00:24:48.840 align:start position:0% examples of specific businesses who are 00:24:48.840 --> 00:24:51.710 align:start position:0% examples of specific businesses who are implementing<00:24:49.500> ethereum<00:24:50.100> today<00:24:50.460> on<00:24:51.360> a<00:24:51.539> public 00:24:51.710 --> 00:24:51.720 align:start position:0% implementing ethereum today on a public 00:24:51.720 --> 00:24:54.529 align:start position:0% implementing ethereum today on a public or<00:24:52.020> private<00:24:52.559> uh<00:24:53.039> chain<00:24:53.340> because<00:24:53.760> you<00:24:54.299> give 00:24:54.529 --> 00:24:54.539 align:start position:0% or private uh chain because you give 00:24:54.539 --> 00:24:56.870 align:start position:0% or private uh chain because you give like<00:24:54.840> more<00:24:55.080> of<00:24:55.260> a<00:24:55.500> general<00:24:55.740> overview<00:24:56.340> but<00:24:56.640> I 00:24:56.870 --> 00:24:56.880 align:start position:0% like more of a general overview but I 00:24:56.880 --> 00:24:59.330 align:start position:0% like more of a general overview but I know<00:24:57.000> curious<00:24:57.600> of<00:24:57.840> specific<00:24:58.200> companies<00:24:59.100> that 00:24:59.330 --> 00:24:59.340 align:start position:0% know curious of specific companies that 00:24:59.340 --> 00:25:01.490 align:start position:0% know curious of specific companies that are<00:24:59.520> doing<00:24:59.640> that<00:24:59.880> right<00:25:00.179> I<00:25:00.840> understand<00:25:00.960> and 00:25:01.490 --> 00:25:01.500 align:start position:0% are doing that right I understand and 00:25:01.500 --> 00:25:03.770 align:start position:0% are doing that right I understand and they've<00:25:01.740> just<00:25:01.919> taken<00:25:02.220> away<00:25:02.400> my<00:25:02.940> my<00:25:03.240> list<00:25:03.539> with 00:25:03.770 --> 00:25:03.780 align:start position:0% they've just taken away my my list with 00:25:03.780 --> 00:25:05.390 align:start position:0% they've just taken away my my list with my<00:25:03.960> notes<00:25:04.200> where<00:25:04.320> I<00:25:04.440> left<00:25:04.620> all<00:25:04.860> the<00:25:04.980> companies 00:25:05.390 --> 00:25:05.400 align:start position:0% my notes where I left all the companies 00:25:05.400 --> 00:25:07.430 align:start position:0% my notes where I left all the companies so<00:25:05.580> I<00:25:05.700> could<00:25:05.820> answer<00:25:06.000> that<00:25:06.299> question<00:25:06.539> with<00:25:07.320> a 00:25:07.430 --> 00:25:07.440 align:start position:0% so I could answer that question with a 00:25:07.440 --> 00:25:09.289 align:start position:0% so I could answer that question with a whole<00:25:07.559> bunch<00:25:07.740> but<00:25:08.039> it's<00:25:08.159> okay 00:25:09.289 --> 00:25:09.299 align:start position:0% whole bunch but it's okay 00:25:09.299 --> 00:25:10.789 align:start position:0% whole bunch but it's okay um<00:25:09.360> so 00:25:10.789 --> 00:25:10.799 align:start position:0% um so 00:25:10.799 --> 00:25:12.529 align:start position:0% um so um one<00:25:11.280> of<00:25:11.460> the 00:25:12.529 --> 00:25:12.539 align:start position:0% um one of the 00:25:12.539 --> 00:25:14.990 align:start position:0% um one of the uh<00:25:13.200> one<00:25:13.440> of<00:25:13.500> the<00:25:13.620> companies<00:25:13.980> that 00:25:14.990 --> 00:25:15.000 align:start position:0% uh one of the companies that 00:25:15.000 --> 00:25:18.169 align:start position:0% uh one of the companies that um that<00:25:15.419> we<00:25:15.539> know<00:25:15.659> of<00:25:15.840> is<00:25:16.140> Alia<00:25:16.620> they<00:25:16.980> did<00:25:17.159> a<00:25:17.400> a 00:25:18.169 --> 00:25:18.179 align:start position:0% um that we know of is Alia they did a a 00:25:18.179 --> 00:25:20.690 align:start position:0% um that we know of is Alia they did a a public<00:25:18.419> uh<00:25:19.140> placement<00:25:19.559> I'm<00:25:20.039> sorry<00:25:20.220> private 00:25:20.690 --> 00:25:20.700 align:start position:0% public uh placement I'm sorry private 00:25:20.700 --> 00:25:22.310 align:start position:0% public uh placement I'm sorry private placement<00:25:21.000> using 00:25:22.310 --> 00:25:22.320 align:start position:0% placement using 00:25:22.320 --> 00:25:23.930 align:start position:0% placement using um<00:25:22.380> using<00:25:22.679> blockchain<00:25:23.100> and<00:25:23.400> that<00:25:23.520> was<00:25:23.640> that 00:25:23.930 --> 00:25:23.940 align:start position:0% um using blockchain and that was that 00:25:23.940 --> 00:25:25.909 align:start position:0% um using blockchain and that was that was<00:25:24.059> very<00:25:24.240> successful 00:25:25.909 --> 00:25:25.919 align:start position:0% was very successful 00:25:25.919 --> 00:25:30.130 align:start position:0% was very successful um Microsoft<00:25:26.520> uses<00:25:27.260> nfts<00:25:28.460> to<00:25:29.460> track 00:25:30.130 --> 00:25:30.140 align:start position:0% um Microsoft uses nfts to track 00:25:30.140 --> 00:25:33.890 align:start position:0% um Microsoft uses nfts to track components<00:25:31.140> in<00:25:31.559> their<00:25:31.799> Azure<00:25:32.580> server<00:25:33.419> Farms 00:25:33.890 --> 00:25:33.900 align:start position:0% components in their Azure server Farms 00:25:33.900 --> 00:25:36.409 align:start position:0% components in their Azure server Farms so<00:25:34.380> they<00:25:34.559> basically<00:25:34.799> do<00:25:35.039> supply<00:25:35.340> chain<00:25:35.700> uh 00:25:36.409 --> 00:25:36.419 align:start position:0% so they basically do supply chain uh 00:25:36.419 --> 00:25:38.870 align:start position:0% so they basically do supply chain uh tracking<00:25:36.840> using<00:25:37.500> an<00:25:37.620> nft<00:25:37.919> for<00:25:38.340> every<00:25:38.640> single 00:25:38.870 --> 00:25:38.880 align:start position:0% tracking using an nft for every single 00:25:38.880 --> 00:25:41.330 align:start position:0% tracking using an nft for every single component<00:25:39.360> not<00:25:40.080> because<00:25:40.320> and<00:25:40.740> and<00:25:40.919> by<00:25:41.159> the<00:25:41.279> way 00:25:41.330 --> 00:25:41.340 align:start position:0% component not because and and by the way 00:25:41.340 --> 00:25:43.010 align:start position:0% component not because and and by the way they're<00:25:41.520> doing<00:25:41.700> this<00:25:41.940> essentially<00:25:42.360> privately 00:25:43.010 --> 00:25:43.020 align:start position:0% they're doing this essentially privately 00:25:43.020 --> 00:25:44.810 align:start position:0% they're doing this essentially privately okay<00:25:43.740> they're<00:25:43.980> doing<00:25:44.159> it<00:25:44.279> on<00:25:44.460> a<00:25:44.580> private 00:25:44.810 --> 00:25:44.820 align:start position:0% okay they're doing it on a private 00:25:44.820 --> 00:25:46.310 align:start position:0% okay they're doing it on a private network<00:25:45.000> but<00:25:45.539> the<00:25:45.720> reason<00:25:45.840> they're<00:25:46.080> using 00:25:46.310 --> 00:25:46.320 align:start position:0% network but the reason they're using 00:25:46.320 --> 00:25:48.230 align:start position:0% network but the reason they're using nfts<00:25:46.919> is<00:25:47.100> because<00:25:47.220> they<00:25:47.520> found<00:25:47.700> them<00:25:47.940> very 00:25:48.230 --> 00:25:48.240 align:start position:0% nfts is because they found them very 00:25:48.240 --> 00:25:51.409 align:start position:0% nfts is because they found them very convenient<00:25:48.779> as<00:25:49.440> a<00:25:49.679> as<00:25:49.919> a<00:25:50.159> holder<00:25:50.520> for 00:25:51.409 --> 00:25:51.419 align:start position:0% convenient as a as a holder for 00:25:51.419 --> 00:25:53.330 align:start position:0% convenient as a as a holder for information<00:25:51.720> that<00:25:52.380> they<00:25:52.500> needed<00:25:52.799> to<00:25:52.980> carry 00:25:53.330 --> 00:25:53.340 align:start position:0% information that they needed to carry 00:25:53.340 --> 00:25:56.210 align:start position:0% information that they needed to carry along<00:25:53.580> the<00:25:53.940> the<00:25:54.299> process 00:25:56.210 --> 00:25:56.220 align:start position:0% along the the process 00:25:56.220 --> 00:25:58.010 align:start position:0% along the the process um I<00:25:56.820> mentioned<00:25:57.120> acre<00:25:57.419> Africa<00:25:57.840> that's 00:25:58.010 --> 00:25:58.020 align:start position:0% um I mentioned acre Africa that's 00:25:58.020 --> 00:25:59.690 align:start position:0% um I mentioned acre Africa that's another<00:25:58.200> one<00:25:58.380> of<00:25:58.500> my<00:25:58.620> favorites 00:25:59.690 --> 00:25:59.700 align:start position:0% another one of my favorites 00:25:59.700 --> 00:26:00.830 align:start position:0% another one of my favorites um 00:26:00.830 --> 00:26:00.840 align:start position:0% um 00:26:00.840 --> 00:26:03.529 align:start position:0% um oh<00:26:01.620> gosh<00:26:01.980> let's<00:26:02.159> see<00:26:02.400> so<00:26:02.700> one<00:26:03.000> of<00:26:03.120> my<00:26:03.179> favorites 00:26:03.529 --> 00:26:03.539 align:start position:0% oh gosh let's see so one of my favorites 00:26:03.539 --> 00:26:07.250 align:start position:0% oh gosh let's see so one of my favorites is<00:26:03.840> uh<00:26:04.700> the<00:26:05.700> again<00:26:06.240> it's<00:26:06.480> a<00:26:06.600> Microsoft 00:26:07.250 --> 00:26:07.260 align:start position:0% is uh the again it's a Microsoft 00:26:07.260 --> 00:26:10.310 align:start position:0% is uh the again it's a Microsoft Microsoft<00:26:07.860> UI<00:26:08.460> uh<00:26:09.299> you<00:26:09.360> know<00:26:09.480> they've<00:26:09.840> been<00:26:10.020> uh 00:26:10.310 --> 00:26:10.320 align:start position:0% Microsoft UI uh you know they've been uh 00:26:10.320 --> 00:26:11.870 align:start position:0% Microsoft UI uh you know they've been uh really<00:26:10.679> really<00:26:10.860> great<00:26:11.100> partners<00:26:11.520> and<00:26:11.700> and 00:26:11.870 --> 00:26:11.880 align:start position:0% really really great partners and and 00:26:11.880 --> 00:26:13.970 align:start position:0% really really great partners and and doing<00:26:12.240> a<00:26:12.360> lot<00:26:12.480> of<00:26:12.539> good<00:26:12.659> work 00:26:13.970 --> 00:26:13.980 align:start position:0% doing a lot of good work 00:26:13.980 --> 00:26:19.310 align:start position:0% doing a lot of good work um<00:26:14.360> they<00:26:15.360> have<00:26:16.320> taken<00:26:16.880> all<00:26:17.880> of 00:26:19.310 --> 00:26:19.320 align:start position:0% um they have taken all of 00:26:19.320 --> 00:26:23.570 align:start position:0% um they have taken all of um<00:26:19.440> the<00:26:20.100> Xbox<00:26:20.419> royalties<00:26:21.419> that<00:26:21.960> they<00:26:22.260> would 00:26:23.570 --> 00:26:23.580 align:start position:0% um the Xbox royalties that they would 00:26:23.580 --> 00:26:25.789 align:start position:0% um the Xbox royalties that they would um<00:26:23.640> you<00:26:24.059> know<00:26:24.179> potentially<00:26:24.600> give<00:26:24.840> to<00:26:25.080> EA<00:26:25.559> Games 00:26:25.789 --> 00:26:25.799 align:start position:0% um you know potentially give to EA Games 00:26:25.799 --> 00:26:28.549 align:start position:0% um you know potentially give to EA Games and<00:26:26.220> all<00:26:26.400> all<00:26:26.580> the<00:26:26.820> network<00:26:27.000> that<00:26:27.360> that<00:26:27.600> are<00:26:27.900> a 00:26:28.549 --> 00:26:28.559 align:start position:0% and all all the network that that are a 00:26:28.559 --> 00:26:31.789 align:start position:0% and all all the network that that are a part<00:26:28.799> of<00:26:29.279> uh<00:26:30.000> you<00:26:30.120> know<00:26:30.240> the<00:26:30.360> Xbox<00:26:30.480> network<00:26:30.960> and 00:26:31.789 --> 00:26:31.799 align:start position:0% part of uh you know the Xbox network and 00:26:31.799 --> 00:26:34.549 align:start position:0% part of uh you know the Xbox network and they've<00:26:32.100> tokenized<00:26:32.700> that<00:26:32.940> and<00:26:33.720> what<00:26:34.140> used<00:26:34.380> to 00:26:34.549 --> 00:26:34.559 align:start position:0% they've tokenized that and what used to 00:26:34.559 --> 00:26:37.190 align:start position:0% they've tokenized that and what used to be<00:26:34.880> uh<00:26:35.880> you<00:26:36.059> know<00:26:36.120> Financial<00:26:36.299> reconciliation 00:26:37.190 --> 00:26:37.200 align:start position:0% be uh you know Financial reconciliation 00:26:37.200 --> 00:26:40.070 align:start position:0% be uh you know Financial reconciliation that<00:26:37.799> you<00:26:37.980> know<00:26:38.039> took<00:26:38.520> months<00:26:39.000> uh<00:26:39.779> you<00:26:39.960> know 00:26:40.070 --> 00:26:40.080 align:start position:0% that you know took months uh you know 00:26:40.080 --> 00:26:42.710 align:start position:0% that you know took months uh you know now<00:26:40.200> as<00:26:40.440> as<00:26:40.799> a<00:26:41.279> uh<00:26:41.880> you<00:26:42.000> know<00:26:42.120> spark<00:26:42.419> contract 00:26:42.710 --> 00:26:42.720 align:start position:0% now as as a uh you know spark contract 00:26:42.720 --> 00:26:45.730 align:start position:0% now as as a uh you know spark contract driven<00:26:43.140> uh<00:26:43.799> instantaneous<00:26:44.400> project<00:26:44.700> process 00:26:45.730 --> 00:26:45.740 align:start position:0% driven uh instantaneous project process 00:26:45.740 --> 00:26:47.810 align:start position:0% driven uh instantaneous project process that<00:26:46.740> uh 00:26:47.810 --> 00:26:47.820 align:start position:0% that uh 00:26:47.820 --> 00:26:49.430 align:start position:0% that uh um<00:26:47.880> you<00:26:48.059> know<00:26:48.179> it<00:26:48.419> goes<00:26:48.900> through<00:26:48.960> the<00:26:49.140> entire 00:26:49.430 --> 00:26:49.440 align:start position:0% um you know it goes through the entire 00:26:49.440 --> 00:26:52.789 align:start position:0% um you know it goes through the entire supply<00:26:50.100> chain<00:26:50.400> large<00:26:50.940> and<00:26:51.240> small<00:26:51.500> uh<00:26:52.500> you<00:26:52.620> know 00:26:52.789 --> 00:26:52.799 align:start position:0% supply chain large and small uh you know 00:26:52.799 --> 00:26:54.769 align:start position:0% supply chain large and small uh you know Partners<00:26:53.100> down<00:26:53.340> the<00:26:53.520> line<00:26:53.700> uh<00:26:54.480> you<00:26:54.600> know 00:26:54.769 --> 00:26:54.779 align:start position:0% Partners down the line uh you know 00:26:54.779 --> 00:26:57.110 align:start position:0% Partners down the line uh you know automatically<00:26:55.260> get<00:26:55.500> get<00:26:55.799> there<00:26:56.220> uh<00:26:56.820> get<00:26:57.059> their 00:26:57.110 --> 00:26:57.120 align:start position:0% automatically get get there uh get their 00:26:57.120 --> 00:27:00.409 align:start position:0% automatically get get there uh get their fair<00:26:57.360> share<00:26:57.980> and<00:26:58.980> uh<00:26:59.400> just<00:26:59.580> a<00:26:59.820> fantastic 00:27:00.409 --> 00:27:00.419 align:start position:0% fair share and uh just a fantastic 00:27:00.419 --> 00:27:03.470 align:start position:0% fair share and uh just a fantastic example<00:27:00.900> and<00:27:01.500> use<00:27:01.799> case<00:27:01.980> for<00:27:02.220> for<00:27:02.580> uh<00:27:03.179> for 00:27:03.470 --> 00:27:03.480 align:start position:0% example and use case for for uh for 00:27:03.480 --> 00:27:05.510 align:start position:0% example and use case for for uh for blockchain<00:27:03.900> and<00:27:04.559> there's<00:27:04.679> a<00:27:04.860> lot<00:27:04.980> more<00:27:05.100> I 00:27:05.510 --> 00:27:05.520 align:start position:0% blockchain and there's a lot more I 00:27:05.520 --> 00:27:07.130 align:start position:0% blockchain and there's a lot more I really<00:27:05.880> do<00:27:06.059> mean<00:27:06.240> you<00:27:06.539> know<00:27:06.600> download<00:27:06.840> the 00:27:07.130 --> 00:27:07.140 align:start position:0% really do mean you know download the 00:27:07.140 --> 00:27:08.630 align:start position:0% really do mean you know download the report<00:27:07.320> you'll<00:27:07.679> you'll<00:27:07.980> get<00:27:08.100> a<00:27:08.220> lot<00:27:08.340> more<00:27:08.460> from 00:27:08.630 --> 00:27:08.640 align:start position:0% report you'll you'll get a lot more from 00:27:08.640 --> 00:27:11.149 align:start position:0% report you'll you'll get a lot more from that<00:27:08.820> thank<00:27:09.240> you 00:27:11.149 --> 00:27:11.159 align:start position:0% that thank you 00:27:11.159 --> 00:27:14.169 align:start position:0% that thank you okay 00:27:14.169 --> 00:27:14.179 align:start position:0% 00:27:14.179 --> 00:27:15.730 align:start position:0% sorry 00:27:15.730 --> 00:27:15.740 align:start position:0% sorry 00:27:15.740 --> 00:27:18.590 align:start position:0% sorry thanks<00:27:16.740> but<00:27:17.279> you<00:27:17.460> can<00:27:17.640> ask<00:27:17.760> for<00:27:18.059> sure<00:27:18.179> more 00:27:18.590 --> 00:27:18.600 align:start position:0% thanks but you can ask for sure more 00:27:18.600 --> 00:27:19.810 align:start position:0% thanks but you can ask for sure more things<00:27:18.840> here 00:27:19.810 --> 00:27:19.820 align:start position:0% things here 00:27:19.820 --> 00:27:21.750 align:start position:0% things here thank<00:27:20.820> you<00:27:20.880> thank<00:27:21.240> you<00:27:21.360> so<00:27:21.480> much 00:27:21.750 --> 00:27:21.760 align:start position:0% thank you thank you so much 00:27:21.760 --> 00:27:27.059 align:start position:0% thank you thank you so much [Applause]