WEBVTT Kind: captions Language: en 00:00:19.480 --> 00:00:21.760 align:start position:0% so<00:00:20.480> thank<00:00:20.720> you<00:00:20.780> all<00:00:20.810> for<00:00:21.080> coming<00:00:21.110> i<00:00:21.380> introduce 00:00:21.760 --> 00:00:21.770 align:start position:0% so thank you all for coming i introduce 00:00:21.770 --> 00:00:23.920 align:start position:0% so thank you all for coming i introduce myself<00:00:21.920> briefly<00:00:22.220> earlier<00:00:22.460> but<00:00:23.420> my<00:00:23.720> name<00:00:23.840> is 00:00:23.920 --> 00:00:23.930 align:start position:0% myself briefly earlier but my name is 00:00:23.930 --> 00:00:26.440 align:start position:0% myself briefly earlier but my name is matthew<00:00:24.200> spoke<00:00:24.490> i<00:00:25.490> actually<00:00:26.060> I<00:00:26.090> remember 00:00:26.440 --> 00:00:26.450 align:start position:0% matthew spoke i actually I remember 00:00:26.450 --> 00:00:28.269 align:start position:0% matthew spoke i actually I remember speaking<00:00:26.689> last<00:00:27.050> year<00:00:27.260> at<00:00:27.350> Def<00:00:27.500> Con<00:00:27.560> in<00:00:27.890> London 00:00:28.269 --> 00:00:28.279 align:start position:0% speaking last year at Def Con in London 00:00:28.279 --> 00:00:31.179 align:start position:0% speaking last year at Def Con in London and<00:00:28.460> I<00:00:29.360> left<00:00:29.810> that<00:00:29.990> week<00:00:30.200> in<00:00:30.410> London<00:00:30.590> feeling 00:00:31.179 --> 00:00:31.189 align:start position:0% and I left that week in London feeling 00:00:31.189 --> 00:00:34.210 align:start position:0% and I left that week in London feeling this<00:00:31.310> really<00:00:31.759> strange<00:00:32.240> hi<00:00:32.930> from<00:00:33.770> spending 00:00:34.210 --> 00:00:34.220 align:start position:0% this really strange hi from spending 00:00:34.220 --> 00:00:36.910 align:start position:0% this really strange hi from spending time<00:00:34.430> with<00:00:34.670> this<00:00:34.790> community<00:00:35.270> I<00:00:36.170> was<00:00:36.590> really 00:00:36.910 --> 00:00:36.920 align:start position:0% time with this community I was really 00:00:36.920 --> 00:00:38.350 align:start position:0% time with this community I was really like<00:00:37.100> in<00:00:37.130> awe<00:00:37.520> of<00:00:37.550> everything<00:00:38.030> that<00:00:38.270> was 00:00:38.350 --> 00:00:38.360 align:start position:0% like in awe of everything that was 00:00:38.360 --> 00:00:40.780 align:start position:0% like in awe of everything that was happening<00:00:38.450> in<00:00:38.750> this<00:00:38.840> space<00:00:39.110> and<00:00:39.410> I<00:00:39.829> was<00:00:40.040> pretty 00:00:40.780 --> 00:00:40.790 align:start position:0% happening in this space and I was pretty 00:00:40.790 --> 00:00:42.910 align:start position:0% happening in this space and I was pretty you<00:00:41.360> know<00:00:41.390> shook<00:00:41.870> when<00:00:42.050> I<00:00:42.110> left<00:00:42.440> to<00:00:42.650> say<00:00:42.800> the 00:00:42.910 --> 00:00:42.920 align:start position:0% you know shook when I left to say the 00:00:42.920 --> 00:00:45.460 align:start position:0% you know shook when I left to say the least<00:00:43.120> at<00:00:44.120> the<00:00:44.300> time<00:00:44.510> I<00:00:44.570> was<00:00:44.870> leading<00:00:45.140> a<00:00:45.290> black 00:00:45.460 --> 00:00:45.470 align:start position:0% least at the time I was leading a black 00:00:45.470 --> 00:00:46.690 align:start position:0% least at the time I was leading a black chain<00:00:45.649> technology<00:00:46.160> team<00:00:46.370> at<00:00:46.489> a<00:00:46.550> big 00:00:46.690 --> 00:00:46.700 align:start position:0% chain technology team at a big 00:00:46.700 --> 00:00:50.040 align:start position:0% chain technology team at a big consulting<00:00:47.000> firm<00:00:47.330> in<00:00:47.420> Toronto<00:00:47.870> now<00:00:48.560> I'm<00:00:48.710> not 00:00:50.040 --> 00:00:50.050 align:start position:0% consulting firm in Toronto now I'm not 00:00:50.050 --> 00:00:53.230 align:start position:0% consulting firm in Toronto now I'm not so<00:00:51.050> I'm<00:00:51.650> going<00:00:51.890> to<00:00:51.920> give<00:00:52.070> my<00:00:52.220> general<00:00:52.670> caveat 00:00:53.230 --> 00:00:53.240 align:start position:0% so I'm going to give my general caveat 00:00:53.240 --> 00:00:55.120 align:start position:0% so I'm going to give my general caveat right<00:00:53.450> now<00:00:53.630> for<00:00:54.470> those<00:00:54.590> of<00:00:54.650> you<00:00:54.890> in<00:00:55.010> the<00:00:55.100> room 00:00:55.120 --> 00:00:55.130 align:start position:0% right now for those of you in the room 00:00:55.130 --> 00:00:57.340 align:start position:0% right now for those of you in the room that<00:00:55.460> work<00:00:55.700> for<00:00:56.000> a<00:00:56.030> quote<00:00:56.300> unquote<00:00:56.450> corporate 00:00:57.340 --> 00:00:57.350 align:start position:0% that work for a quote unquote corporate 00:00:57.350 --> 00:00:59.440 align:start position:0% that work for a quote unquote corporate i<00:00:57.560> will<00:00:58.190> take<00:00:58.340> absolutely<00:00:58.910> no<00:00:59.030> responsibility 00:00:59.440 --> 00:00:59.450 align:start position:0% i will take absolutely no responsibility 00:00:59.450 --> 00:01:01.770 align:start position:0% i will take absolutely no responsibility if<00:00:59.990> you<00:01:00.080> leave<00:01:00.380> this<00:01:00.560> week<00:01:00.830> quit<00:01:01.250> your<00:01:01.340> job 00:01:01.770 --> 00:01:01.780 align:start position:0% if you leave this week quit your job 00:01:01.780 --> 00:01:04.149 align:start position:0% if you leave this week quit your job jump<00:01:02.780> into<00:01:02.930> the<00:01:03.050> blockchain<00:01:03.260> ecosystem 00:01:04.149 --> 00:01:04.159 align:start position:0% jump into the blockchain ecosystem 00:01:04.159 --> 00:01:06.310 align:start position:0% jump into the blockchain ecosystem there's<00:01:05.059> many<00:01:05.330> people<00:01:05.479> who<00:01:05.720> have<00:01:05.750> done<00:01:06.020> it<00:01:06.080> you 00:01:06.310 --> 00:01:06.320 align:start position:0% there's many people who have done it you 00:01:06.320 --> 00:01:11.590 align:start position:0% there's many people who have done it you wouldn't<00:01:06.500> be<00:01:06.590> the<00:01:06.619> first<00:01:09.909> so<00:01:10.909> briefly<00:01:11.479> i'm 00:01:11.590 --> 00:01:11.600 align:start position:0% wouldn't be the first so briefly i'm 00:01:11.600 --> 00:01:12.580 align:start position:0% wouldn't be the first so briefly i'm going<00:01:11.720> to<00:01:11.780> tell<00:01:11.930> you<00:01:11.990> a<00:01:12.049> little<00:01:12.200> bit<00:01:12.290> about<00:01:12.470> the 00:01:12.580 --> 00:01:12.590 align:start position:0% going to tell you a little bit about the 00:01:12.590 --> 00:01:16.030 align:start position:0% going to tell you a little bit about the work<00:01:12.740> that<00:01:12.890> we're<00:01:13.040> doing<00:01:13.070> at<00:01:13.310> new<00:01:13.430> co<00:01:13.810> and<00:01:15.040> then 00:01:16.030 --> 00:01:16.040 align:start position:0% work that we're doing at new co and then 00:01:16.040 --> 00:01:17.260 align:start position:0% work that we're doing at new co and then i'm<00:01:16.130> going<00:01:16.250> to<00:01:16.310> move<00:01:16.430> on<00:01:16.610> I<00:01:16.640> don't<00:01:17.060> want<00:01:17.180> I 00:01:17.260 --> 00:01:17.270 align:start position:0% i'm going to move on I don't want I 00:01:17.270 --> 00:01:18.370 align:start position:0% i'm going to move on I don't want I don't<00:01:17.299> want<00:01:17.420> to<00:01:17.600> kind<00:01:17.750> of<00:01:17.780> get<00:01:17.900> too<00:01:18.110> repetitive 00:01:18.370 --> 00:01:18.380 align:start position:0% don't want to kind of get too repetitive 00:01:18.380 --> 00:01:19.690 align:start position:0% don't want to kind of get too repetitive with<00:01:18.740> some<00:01:18.860> of<00:01:18.950> the<00:01:19.010> things<00:01:19.220> that<00:01:19.340> we<00:01:19.430> spoke 00:01:19.690 --> 00:01:19.700 align:start position:0% with some of the things that we spoke 00:01:19.700 --> 00:01:21.040 align:start position:0% with some of the things that we spoke about<00:01:19.820> on<00:01:19.940> the<00:01:20.090> panel<00:01:20.420> or<00:01:20.540> some<00:01:20.690> of<00:01:20.780> the<00:01:20.840> topics 00:01:21.040 --> 00:01:21.050 align:start position:0% about on the panel or some of the topics 00:01:21.050 --> 00:01:22.960 align:start position:0% about on the panel or some of the topics that<00:01:21.409> Victor<00:01:21.710> covered<00:01:22.040> because<00:01:22.550> I<00:01:22.670> mean<00:01:22.850> a<00:01:22.880> lot 00:01:22.960 --> 00:01:22.970 align:start position:0% that Victor covered because I mean a lot 00:01:22.970 --> 00:01:24.490 align:start position:0% that Victor covered because I mean a lot of<00:01:23.090> the<00:01:23.240> problems<00:01:23.600> that<00:01:23.630> are<00:01:23.780> being<00:01:23.960> solved<00:01:24.380> by 00:01:24.490 --> 00:01:24.500 align:start position:0% of the problems that are being solved by 00:01:24.500 --> 00:01:26.770 align:start position:0% of the problems that are being solved by various<00:01:24.830> party<00:01:25.360> companies<00:01:26.360> in<00:01:26.540> this<00:01:26.630> space 00:01:26.770 --> 00:01:26.780 align:start position:0% various party companies in this space 00:01:26.780 --> 00:01:28.210 align:start position:0% various party companies in this space are<00:01:27.110> pretty<00:01:27.260> similar<00:01:27.560> I<00:01:27.740> mean<00:01:27.950> we're<00:01:28.100> all 00:01:28.210 --> 00:01:28.220 align:start position:0% are pretty similar I mean we're all 00:01:28.220 --> 00:01:29.890 align:start position:0% are pretty similar I mean we're all looking<00:01:28.460> at<00:01:28.700> the<00:01:28.760> same<00:01:28.880> restrictions<00:01:29.750> and 00:01:29.890 --> 00:01:29.900 align:start position:0% looking at the same restrictions and 00:01:29.900 --> 00:01:32.290 align:start position:0% looking at the same restrictions and limitations<00:01:29.960> of<00:01:30.500> what<00:01:31.220> needs<00:01:31.370> to<00:01:31.640> happen<00:01:31.670> to 00:01:32.290 --> 00:01:32.300 align:start position:0% limitations of what needs to happen to 00:01:32.300 --> 00:01:34.360 align:start position:0% limitations of what needs to happen to athyrium<00:01:33.170> based<00:01:33.320> technologies<00:01:33.920> to<00:01:34.100> be<00:01:34.190> really 00:01:34.360 --> 00:01:34.370 align:start position:0% athyrium based technologies to be really 00:01:34.370 --> 00:01:37.930 align:start position:0% athyrium based technologies to be really applicable<00:01:34.640> in<00:01:35.090> the<00:01:35.390> enterprise<00:01:35.720> space<00:01:36.940> we 00:01:37.930 --> 00:01:37.940 align:start position:0% applicable in the enterprise space we 00:01:37.940 --> 00:01:40.420 align:start position:0% applicable in the enterprise space we heard<00:01:38.270> from<00:01:38.810> you<00:01:39.470> know<00:01:39.560> that's<00:01:39.800> this<00:01:40.010> panel 00:01:40.420 --> 00:01:40.430 align:start position:0% heard from you know that's this panel 00:01:40.430 --> 00:01:42.670 align:start position:0% heard from you know that's this panel specifically<00:01:41.030> how<00:01:41.210> the<00:01:41.810> path<00:01:42.050> towards<00:01:42.500> some 00:01:42.670 --> 00:01:42.680 align:start position:0% specifically how the path towards some 00:01:42.680 --> 00:01:44.110 align:start position:0% specifically how the path towards some of<00:01:42.770> these<00:01:42.830> solutions<00:01:43.159> in<00:01:43.490> the<00:01:43.580> path<00:01:43.760> towards 00:01:44.110 --> 00:01:44.120 align:start position:0% of these solutions in the path towards 00:01:44.120 --> 00:01:45.820 align:start position:0% of these solutions in the path towards some<00:01:44.299> meaningful<00:01:44.600> enterprise<00:01:45.049> adoption<00:01:45.350> and 00:01:45.820 --> 00:01:45.830 align:start position:0% some meaningful enterprise adoption and 00:01:45.830 --> 00:01:48.460 align:start position:0% some meaningful enterprise adoption and there's<00:01:46.549> really<00:01:46.970> some<00:01:47.450> some<00:01:47.930> tremendous 00:01:48.460 --> 00:01:48.470 align:start position:0% there's really some some tremendous 00:01:48.470 --> 00:01:49.600 align:start position:0% there's really some some tremendous companies<00:01:48.890> up<00:01:49.010> here<00:01:49.159> that<00:01:49.310> we're<00:01:49.430> speaking 00:01:49.600 --> 00:01:49.610 align:start position:0% companies up here that we're speaking 00:01:49.610 --> 00:01:52.180 align:start position:0% companies up here that we're speaking earlier<00:01:49.880> that<00:01:50.240> i<00:01:50.270> really<00:01:50.990> admire<00:01:51.140> and<00:01:51.470> i<00:01:51.560> think 00:01:52.180 --> 00:01:52.190 align:start position:0% earlier that i really admire and i think 00:01:52.190 --> 00:01:53.830 align:start position:0% earlier that i really admire and i think the<00:01:52.340> the<00:01:52.670> industry<00:01:53.030> is<00:01:53.120> in<00:01:53.240> good<00:01:53.360> hands<00:01:53.570> if<00:01:53.750> we 00:01:53.830 --> 00:01:53.840 align:start position:0% the the industry is in good hands if we 00:01:53.840 --> 00:01:54.880 align:start position:0% the the industry is in good hands if we can<00:01:53.990> just<00:01:54.140> look<00:01:54.229> at<00:01:54.350> the<00:01:54.470> group<00:01:54.590> of<00:01:54.740> companies 00:01:54.880 --> 00:01:54.890 align:start position:0% can just look at the group of companies 00:01:54.890 --> 00:01:57.310 align:start position:0% can just look at the group of companies or<00:01:55.220> solving<00:01:55.610> this<00:01:55.729> so<00:01:56.600> newco<00:01:56.960> a<00:01:56.990> little<00:01:57.229> bit 00:01:57.310 --> 00:01:57.320 align:start position:0% or solving this so newco a little bit 00:01:57.320 --> 00:01:59.100 align:start position:0% or solving this so newco a little bit about<00:01:57.500> us<00:01:57.680> we're<00:01:58.460> a<00:01:58.490> fully<00:01:58.790> modular 00:01:59.100 --> 00:01:59.110 align:start position:0% about us we're a fully modular 00:01:59.110 --> 00:02:01.289 align:start position:0% about us we're a fully modular customizable<00:02:00.110> black<00:02:00.260> chain<00:02:00.470> infrastructure 00:02:01.289 --> 00:02:01.299 align:start position:0% customizable black chain infrastructure 00:02:01.299 --> 00:02:05.020 align:start position:0% customizable black chain infrastructure framework<00:02:02.299> that<00:02:02.479> is<00:02:02.750> designed<00:02:03.020> to<00:02:03.560> enable<00:02:04.030> the 00:02:05.020 --> 00:02:05.030 align:start position:0% framework that is designed to enable the 00:02:05.030 --> 00:02:06.789 align:start position:0% framework that is designed to enable the creation<00:02:05.240> of<00:02:05.510> domain-specific<00:02:05.869> block<00:02:06.560> chain 00:02:06.789 --> 00:02:06.799 align:start position:0% creation of domain-specific block chain 00:02:06.799 --> 00:02:09.070 align:start position:0% creation of domain-specific block chain networks<00:02:07.159> that<00:02:07.790> can<00:02:07.909> be<00:02:08.030> optimized<00:02:08.539> to<00:02:08.750> solve 00:02:09.070 --> 00:02:09.080 align:start position:0% networks that can be optimized to solve 00:02:09.080 --> 00:02:11.080 align:start position:0% networks that can be optimized to solve specific<00:02:09.289> problems<00:02:09.709> specific<00:02:10.519> applications 00:02:11.080 --> 00:02:11.090 align:start position:0% specific problems specific applications 00:02:11.090 --> 00:02:14.559 align:start position:0% specific problems specific applications in<00:02:11.239> specific<00:02:11.689> industries<00:02:13.090> so<00:02:14.090> we've<00:02:14.239> we've 00:02:14.559 --> 00:02:14.569 align:start position:0% in specific industries so we've we've 00:02:14.569 --> 00:02:16.570 align:start position:0% in specific industries so we've we've essentially<00:02:14.900> piggyback<00:02:15.470> off<00:02:15.500> of<00:02:15.769> the<00:02:16.310> the 00:02:16.570 --> 00:02:16.580 align:start position:0% essentially piggyback off of the the 00:02:16.580 --> 00:02:19.089 align:start position:0% essentially piggyback off of the the vision<00:02:16.879> of<00:02:16.939> etherium<00:02:17.480> to<00:02:17.989> create<00:02:18.349> this<00:02:18.620> this 00:02:19.089 --> 00:02:19.099 align:start position:0% vision of etherium to create this this 00:02:19.099 --> 00:02:21.759 align:start position:0% vision of etherium to create this this this<00:02:19.489> framework<00:02:19.900> to<00:02:20.900> design<00:02:21.140> a<00:02:21.170> technology 00:02:21.759 --> 00:02:21.769 align:start position:0% this framework to design a technology 00:02:21.769 --> 00:02:22.990 align:start position:0% this framework to design a technology that<00:02:21.799> can<00:02:22.099> solve<00:02:22.370> some<00:02:22.580> of<00:02:22.610> the<00:02:22.730> pain<00:02:22.970> and 00:02:22.990 --> 00:02:23.000 align:start position:0% that can solve some of the pain and 00:02:23.000 --> 00:02:24.850 align:start position:0% that can solve some of the pain and unattractive<00:02:23.810> problems<00:02:24.260> that<00:02:24.410> we<00:02:24.500> see<00:02:24.530> in<00:02:24.709> the 00:02:24.850 --> 00:02:24.860 align:start position:0% unattractive problems that we see in the 00:02:24.860 --> 00:02:27.370 align:start position:0% unattractive problems that we see in the enterprise<00:02:25.190> world<00:02:25.480> by<00:02:26.480> bringing<00:02:26.900> to<00:02:27.050> it<00:02:27.200> kind 00:02:27.370 --> 00:02:27.380 align:start position:0% enterprise world by bringing to it kind 00:02:27.380 --> 00:02:27.940 align:start position:0% enterprise world by bringing to it kind of<00:02:27.410> a<00:02:27.500> new 00:02:27.940 --> 00:02:27.950 align:start position:0% of a new 00:02:27.950 --> 00:02:29.800 align:start position:0% of a new ends<00:02:28.099> of<00:02:28.220> how<00:02:28.640> do<00:02:28.700> distributed<00:02:29.360> systems 00:02:29.800 --> 00:02:29.810 align:start position:0% ends of how do distributed systems 00:02:29.810 --> 00:02:31.660 align:start position:0% ends of how do distributed systems change<00:02:30.590> kind<00:02:30.920> of<00:02:30.980> the<00:02:31.069> framework<00:02:31.459> and 00:02:31.660 --> 00:02:31.670 align:start position:0% change kind of the framework and 00:02:31.670 --> 00:02:34.600 align:start position:0% change kind of the framework and operations<00:02:32.480> of<00:02:32.599> a<00:02:32.660> large<00:02:32.810> enterprise<00:02:33.370> now<00:02:34.370> one 00:02:34.600 --> 00:02:34.610 align:start position:0% operations of a large enterprise now one 00:02:34.610 --> 00:02:35.680 align:start position:0% operations of a large enterprise now one of<00:02:34.640> the<00:02:34.760> things<00:02:34.819> that<00:02:34.970> I<00:02:35.060> like<00:02:35.330> to<00:02:35.480> kind<00:02:35.599> of 00:02:35.680 --> 00:02:35.690 align:start position:0% of the things that I like to kind of 00:02:35.690 --> 00:02:36.970 align:start position:0% of the things that I like to kind of reiterate<00:02:35.900> over<00:02:36.379> and<00:02:36.500> over<00:02:36.590> again<00:02:36.739> when<00:02:36.920> I 00:02:36.970 --> 00:02:36.980 align:start position:0% reiterate over and over again when I 00:02:36.980 --> 00:02:38.800 align:start position:0% reiterate over and over again when I started<00:02:37.400> in<00:02:37.489> the<00:02:37.580> blockchain<00:02:37.760> space<00:02:38.209> kind<00:02:38.750> of 00:02:38.800 --> 00:02:38.810 align:start position:0% started in the blockchain space kind of 00:02:38.810 --> 00:02:41.530 align:start position:0% started in the blockchain space kind of two<00:02:39.019> years<00:02:39.260> ago<00:02:40.150> enterprises<00:02:41.150> and<00:02:41.300> large 00:02:41.530 --> 00:02:41.540 align:start position:0% two years ago enterprises and large 00:02:41.540 --> 00:02:43.180 align:start position:0% two years ago enterprises and large companies<00:02:41.810> we're<00:02:42.200> kind<00:02:42.349> of<00:02:42.379> you<00:02:42.890> know<00:02:42.920> being 00:02:43.180 --> 00:02:43.190 align:start position:0% companies we're kind of you know being 00:02:43.190 --> 00:02:45.190 align:start position:0% companies we're kind of you know being framed<00:02:43.489> as<00:02:43.760> like<00:02:43.970> the<00:02:44.330> evil<00:02:44.540> that<00:02:44.840> needed<00:02:45.170> to 00:02:45.190 --> 00:02:45.200 align:start position:0% framed as like the evil that needed to 00:02:45.200 --> 00:02:46.990 align:start position:0% framed as like the evil that needed to be<00:02:45.290> removed<00:02:45.680> from<00:02:45.980> the<00:02:46.160> world<00:02:46.370> and<00:02:46.670> therefore 00:02:46.990 --> 00:02:47.000 align:start position:0% be removed from the world and therefore 00:02:47.000 --> 00:02:50.140 align:start position:0% be removed from the world and therefore we<00:02:47.150> created<00:02:47.510> Bitcoin<00:02:47.690> and<00:02:48.140> then<00:02:48.260> etherium<00:02:49.150> but 00:02:50.140 --> 00:02:50.150 align:start position:0% we created Bitcoin and then etherium but 00:02:50.150 --> 00:02:51.460 align:start position:0% we created Bitcoin and then etherium but I<00:02:50.180> think<00:02:50.450> it's<00:02:50.569> kind<00:02:50.690> of<00:02:50.780> important<00:02:51.230> for<00:02:51.349> us<00:02:51.440> to 00:02:51.460 --> 00:02:51.470 align:start position:0% I think it's kind of important for us to 00:02:51.470 --> 00:02:52.809 align:start position:0% I think it's kind of important for us to recognize<00:02:51.680> that<00:02:51.980> these<00:02:52.250> are<00:02:52.370> the<00:02:52.459> companies 00:02:52.809 --> 00:02:52.819 align:start position:0% recognize that these are the companies 00:02:52.819 --> 00:02:54.400 align:start position:0% recognize that these are the companies that<00:02:52.970> we<00:02:53.090> rely<00:02:53.360> on<00:02:53.540> on<00:02:53.630> a<00:02:53.660> day-to-day<00:02:53.840> basis 00:02:54.400 --> 00:02:54.410 align:start position:0% that we rely on on a day-to-day basis 00:02:54.410 --> 00:02:55.600 align:start position:0% that we rely on on a day-to-day basis these<00:02:54.590> are<00:02:54.709> the<00:02:54.769> companies<00:02:55.099> that<00:02:55.130> provide<00:02:55.459> us 00:02:55.600 --> 00:02:55.610 align:start position:0% these are the companies that provide us 00:02:55.610 --> 00:02:56.800 align:start position:0% these are the companies that provide us services<00:02:56.030> like<00:02:56.209> bank<00:02:56.390> accounts<00:02:56.780> and 00:02:56.800 --> 00:02:56.810 align:start position:0% services like bank accounts and 00:02:56.810 --> 00:02:58.509 align:start position:0% services like bank accounts and insurance<00:02:57.260> and<00:02:57.769> although<00:02:58.010> it's<00:02:58.160> sometimes 00:02:58.509 --> 00:02:58.519 align:start position:0% insurance and although it's sometimes 00:02:58.519 --> 00:03:00.250 align:start position:0% insurance and although it's sometimes frustrating<00:02:59.120> to<00:02:59.209> deal<00:02:59.330> with<00:02:59.510> them<00:02:59.660> there's<00:03:00.080> an 00:03:00.250 --> 00:03:00.260 align:start position:0% frustrating to deal with them there's an 00:03:00.260 --> 00:03:01.809 align:start position:0% frustrating to deal with them there's an enormous<00:03:00.680> opportunity<00:03:00.799> to<00:03:01.400> help<00:03:01.610> these 00:03:01.809 --> 00:03:01.819 align:start position:0% enormous opportunity to help these 00:03:01.819 --> 00:03:03.910 align:start position:0% enormous opportunity to help these companies<00:03:02.180> and<00:03:02.630> these<00:03:03.080> industries<00:03:03.560> solve 00:03:03.910 --> 00:03:03.920 align:start position:0% companies and these industries solve 00:03:03.920 --> 00:03:06.160 align:start position:0% companies and these industries solve their<00:03:04.280> kind<00:03:04.459> of<00:03:04.519> outdated<00:03:04.910> systems<00:03:05.510> so<00:03:05.989> that's 00:03:06.160 --> 00:03:06.170 align:start position:0% their kind of outdated systems so that's 00:03:06.170 --> 00:03:07.390 align:start position:0% their kind of outdated systems so that's kind<00:03:06.380> of<00:03:06.410> where<00:03:06.530> we're<00:03:06.620> putting<00:03:06.739> our<00:03:06.950> focus<00:03:07.280> is 00:03:07.390 --> 00:03:07.400 align:start position:0% kind of where we're putting our focus is 00:03:07.400 --> 00:03:09.699 align:start position:0% kind of where we're putting our focus is to<00:03:07.519> really<00:03:07.700> bring<00:03:08.079> these<00:03:09.079> critically 00:03:09.699 --> 00:03:09.709 align:start position:0% to really bring these critically 00:03:09.709 --> 00:03:11.470 align:start position:0% to really bring these critically important<00:03:10.190> services<00:03:10.610> that<00:03:10.819> we<00:03:10.910> all<00:03:11.030> rely<00:03:11.329> on 00:03:11.470 --> 00:03:11.480 align:start position:0% important services that we all rely on 00:03:11.480 --> 00:03:13.360 align:start position:0% important services that we all rely on day-to-day<00:03:11.690> into<00:03:12.620> the<00:03:12.709> modern<00:03:12.890> world<00:03:13.040> with 00:03:13.360 --> 00:03:13.370 align:start position:0% day-to-day into the modern world with 00:03:13.370 --> 00:03:16.270 align:start position:0% day-to-day into the modern world with new<00:03:13.459> technology<00:03:14.290> to<00:03:15.290> do<00:03:15.440> this<00:03:15.590> we're<00:03:15.829> looking 00:03:16.270 --> 00:03:16.280 align:start position:0% new technology to do this we're looking 00:03:16.280 --> 00:03:17.380 align:start position:0% new technology to do this we're looking we're<00:03:16.579> taking<00:03:16.849> a<00:03:16.910> slightly<00:03:17.120> different 00:03:17.380 --> 00:03:17.390 align:start position:0% we're taking a slightly different 00:03:17.390 --> 00:03:19.990 align:start position:0% we're taking a slightly different approach<00:03:17.569> I<00:03:17.989> mean<00:03:18.709> we<00:03:18.860> looked<00:03:19.160> at<00:03:19.310> etherium<00:03:19.849> as 00:03:19.990 --> 00:03:20.000 align:start position:0% approach I mean we looked at etherium as 00:03:20.000 --> 00:03:22.210 align:start position:0% approach I mean we looked at etherium as a<00:03:20.780> technology<00:03:21.410> that<00:03:21.440> really<00:03:21.799> is<00:03:21.890> a<00:03:21.920> public 00:03:22.210 --> 00:03:22.220 align:start position:0% a technology that really is a public 00:03:22.220 --> 00:03:24.069 align:start position:0% a technology that really is a public utility<00:03:22.340> that<00:03:22.819> that<00:03:23.060> everybody<00:03:23.510> can<00:03:23.720> use<00:03:23.870> for 00:03:24.069 --> 00:03:24.079 align:start position:0% utility that that everybody can use for 00:03:24.079 --> 00:03:26.350 align:start position:0% utility that that everybody can use for pretty<00:03:24.349> much<00:03:24.410> anything<00:03:24.950> and<00:03:25.370> we<00:03:26.000> applied<00:03:26.329> a 00:03:26.350 --> 00:03:26.360 align:start position:0% pretty much anything and we applied a 00:03:26.360 --> 00:03:28.539 align:start position:0% pretty much anything and we applied a lens<00:03:26.750> of<00:03:27.019> enterprise<00:03:27.799> technology<00:03:28.040> and 00:03:28.539 --> 00:03:28.549 align:start position:0% lens of enterprise technology and 00:03:28.549 --> 00:03:31.120 align:start position:0% lens of enterprise technology and enterprise<00:03:28.880> infrastructure<00:03:29.180> to<00:03:29.750> it<00:03:29.900> so<00:03:30.440> we<00:03:30.620> we 00:03:31.120 --> 00:03:31.130 align:start position:0% enterprise infrastructure to it so we we 00:03:31.130 --> 00:03:33.160 align:start position:0% enterprise infrastructure to it so we we kind<00:03:31.370> of<00:03:31.430> dissected<00:03:32.060> the<00:03:32.150> etherium<00:03:32.600> stack<00:03:32.900> and 00:03:33.160 --> 00:03:33.170 align:start position:0% kind of dissected the etherium stack and 00:03:33.170 --> 00:03:35.800 align:start position:0% kind of dissected the etherium stack and said<00:03:33.380> if<00:03:33.530> i<00:03:33.769> were<00:03:33.950> to<00:03:34.160> redesign<00:03:34.670> this<00:03:34.940> asking 00:03:35.800 --> 00:03:35.810 align:start position:0% said if i were to redesign this asking 00:03:35.810 --> 00:03:37.930 align:start position:0% said if i were to redesign this asking the<00:03:35.959> simple<00:03:36.380> question<00:03:36.829> of<00:03:37.040> how<00:03:37.489> would<00:03:37.790> this 00:03:37.930 --> 00:03:37.940 align:start position:0% the simple question of how would this 00:03:37.940 --> 00:03:39.610 align:start position:0% the simple question of how would this have<00:03:38.150> been<00:03:38.180> built<00:03:38.510> if<00:03:38.750> it<00:03:38.900> was<00:03:39.049> built<00:03:39.290> from<00:03:39.410> day 00:03:39.610 --> 00:03:39.620 align:start position:0% have been built if it was built from day 00:03:39.620 --> 00:03:42.099 align:start position:0% have been built if it was built from day one<00:03:39.799> as<00:03:39.920> an<00:03:40.040> enterprise<00:03:40.220> technology<00:03:40.670> and<00:03:41.269> so 00:03:42.099 --> 00:03:42.109 align:start position:0% one as an enterprise technology and so 00:03:42.109 --> 00:03:43.330 align:start position:0% one as an enterprise technology and so what<00:03:42.290> does<00:03:42.440> that<00:03:42.560> mean<00:03:42.769> that<00:03:42.950> the<00:03:43.010> consensus 00:03:43.330 --> 00:03:43.340 align:start position:0% what does that mean that the consensus 00:03:43.340 --> 00:03:45.009 align:start position:0% what does that mean that the consensus layer<00:03:43.730> what<00:03:43.970> does<00:03:44.120> that<00:03:44.239> mean<00:03:44.420> all<00:03:44.660> the<00:03:44.780> way<00:03:44.900> up 00:03:45.009 --> 00:03:45.019 align:start position:0% layer what does that mean all the way up 00:03:45.019 --> 00:03:46.720 align:start position:0% layer what does that mean all the way up the<00:03:45.139> stack<00:03:45.350> of<00:03:45.530> etherium<00:03:45.950> so<00:03:46.370> that<00:03:46.519> it<00:03:46.609> can 00:03:46.720 --> 00:03:46.730 align:start position:0% the stack of etherium so that it can 00:03:46.730 --> 00:03:48.370 align:start position:0% the stack of etherium so that it can really<00:03:47.000> start<00:03:47.239> to<00:03:47.420> be<00:03:47.569> meaningfully<00:03:48.079> applied 00:03:48.370 --> 00:03:48.380 align:start position:0% really start to be meaningfully applied 00:03:48.380 --> 00:03:50.530 align:start position:0% really start to be meaningfully applied in<00:03:48.560> an<00:03:48.650> enterprise<00:03:48.859> context<00:03:49.519> and<00:03:49.700> that<00:03:50.269> led<00:03:50.450> us 00:03:50.530 --> 00:03:50.540 align:start position:0% in an enterprise context and that led us 00:03:50.540 --> 00:03:53.199 align:start position:0% in an enterprise context and that led us to<00:03:50.569> some<00:03:50.900> really<00:03:51.230> challenging<00:03:51.670> but<00:03:52.670> important 00:03:53.199 --> 00:03:53.209 align:start position:0% to some really challenging but important 00:03:53.209 --> 00:03:54.640 align:start position:0% to some really challenging but important priorities<00:03:53.690> that<00:03:53.840> have<00:03:53.900> essentially<00:03:54.410> become 00:03:54.640 --> 00:03:54.650 align:start position:0% priorities that have essentially become 00:03:54.650 --> 00:03:56.949 align:start position:0% priorities that have essentially become the<00:03:54.769> roadmap<00:03:55.130> of<00:03:55.160> what<00:03:55.459> we're<00:03:55.579> building<00:03:55.959> so 00:03:56.949 --> 00:03:56.959 align:start position:0% the roadmap of what we're building so 00:03:56.959 --> 00:03:58.150 align:start position:0% the roadmap of what we're building so for<00:03:57.109> context<00:03:57.500> I<00:03:57.590> didn't<00:03:57.769> give<00:03:57.859> you<00:03:57.889> the<00:03:58.040> full 00:03:58.150 --> 00:03:58.160 align:start position:0% for context I didn't give you the full 00:03:58.160 --> 00:03:59.620 align:start position:0% for context I didn't give you the full background<00:03:58.400> I<00:03:58.609> mean<00:03:58.730> newco<00:03:59.030> is<00:03:59.150> a<00:03:59.180> relatively 00:03:59.620 --> 00:03:59.630 align:start position:0% background I mean newco is a relatively 00:03:59.630 --> 00:04:01.990 align:start position:0% background I mean newco is a relatively new<00:03:59.750> venture<00:04:00.200> as<00:04:00.319> I<00:04:00.470> mentioned<00:04:00.920> we<00:04:01.370> used<00:04:01.639> to<00:04:01.819> we 00:04:01.990 --> 00:04:02.000 align:start position:0% new venture as I mentioned we used to we 00:04:02.000 --> 00:04:04.449 align:start position:0% new venture as I mentioned we used to we kind<00:04:02.180> of<00:04:02.239> our<00:04:02.780> initial<00:04:03.230> core<00:04:03.530> team<00:04:03.799> started<00:04:04.310> as 00:04:04.449 --> 00:04:04.459 align:start position:0% kind of our initial core team started as 00:04:04.459 --> 00:04:06.640 align:start position:0% kind of our initial core team started as a<00:04:04.519> blockchain<00:04:05.329> technology<00:04:05.480> team<00:04:06.170> at<00:04:06.319> Deloitte 00:04:06.640 --> 00:04:06.650 align:start position:0% a blockchain technology team at Deloitte 00:04:06.650 --> 00:04:09.009 align:start position:0% a blockchain technology team at Deloitte we<00:04:06.950> we<00:04:07.730> left<00:04:08.030> and<00:04:08.239> we<00:04:08.389> started<00:04:08.660> this<00:04:08.750> company 00:04:09.009 --> 00:04:09.019 align:start position:0% we we left and we started this company 00:04:09.019 --> 00:04:10.300 align:start position:0% we we left and we started this company four<00:04:09.230> months<00:04:09.470> ago<00:04:09.560> were<00:04:09.769> based<00:04:09.950> in<00:04:10.130> Toronto 00:04:10.300 --> 00:04:10.310 align:start position:0% four months ago were based in Toronto 00:04:10.310 --> 00:04:12.940 align:start position:0% four months ago were based in Toronto Canada<00:04:10.690> so<00:04:11.690> some<00:04:12.230> of<00:04:12.260> the<00:04:12.380> priorities<00:04:12.590> that<00:04:12.889> we 00:04:12.940 --> 00:04:12.950 align:start position:0% Canada so some of the priorities that we 00:04:12.950 --> 00:04:15.309 align:start position:0% Canada so some of the priorities that we decided<00:04:13.400> to<00:04:13.489> tackle<00:04:14.049> you<00:04:15.049> know<00:04:15.139> very 00:04:15.309 --> 00:04:15.319 align:start position:0% decided to tackle you know very 00:04:15.319 --> 00:04:16.779 align:start position:0% decided to tackle you know very similarly<00:04:15.680> to<00:04:15.859> the<00:04:15.950> topics<00:04:16.370> we<00:04:16.459> were<00:04:16.579> speaking 00:04:16.779 --> 00:04:16.789 align:start position:0% similarly to the topics we were speaking 00:04:16.789 --> 00:04:18.190 align:start position:0% similarly to the topics we were speaking about<00:04:16.940> earlier<00:04:17.359> are<00:04:17.599> things<00:04:18.019> like 00:04:18.190 --> 00:04:18.200 align:start position:0% about earlier are things like 00:04:18.200 --> 00:04:21.159 align:start position:0% about earlier are things like scalability<00:04:18.919> so<00:04:19.849> on<00:04:20.000> scalability<00:04:20.419> we're 00:04:21.159 --> 00:04:21.169 align:start position:0% scalability so on scalability we're 00:04:21.169 --> 00:04:23.379 align:start position:0% scalability so on scalability we're focused<00:04:21.349> on<00:04:21.650> optimizing<00:04:21.769> the<00:04:22.700> availability 00:04:23.379 --> 00:04:23.389 align:start position:0% focused on optimizing the availability 00:04:23.389 --> 00:04:25.060 align:start position:0% focused on optimizing the availability of<00:04:23.419> different<00:04:23.780> consensus<00:04:24.289> mechanisms<00:04:24.889> into 00:04:25.060 --> 00:04:25.070 align:start position:0% of different consensus mechanisms into 00:04:25.070 --> 00:04:26.830 align:start position:0% of different consensus mechanisms into the<00:04:25.280> etherium<00:04:25.700> stack<00:04:25.970> so<00:04:26.180> how<00:04:26.300> do<00:04:26.360> you<00:04:26.479> AAPIs 00:04:26.830 --> 00:04:26.840 align:start position:0% the etherium stack so how do you AAPIs 00:04:26.840 --> 00:04:29.440 align:start position:0% the etherium stack so how do you AAPIs kate<00:04:27.139> the<00:04:27.770> consensus<00:04:28.460> mechanism<00:04:29.060> from<00:04:29.240> the 00:04:29.440 --> 00:04:29.450 align:start position:0% kate the consensus mechanism from the 00:04:29.450 --> 00:04:30.969 align:start position:0% kate the consensus mechanism from the actual<00:04:29.720> operation<00:04:30.289> of<00:04:30.380> the<00:04:30.440> block<00:04:30.590> chain<00:04:30.620> so 00:04:30.969 --> 00:04:30.979 align:start position:0% actual operation of the block chain so 00:04:30.979 --> 00:04:33.900 align:start position:0% actual operation of the block chain so that<00:04:31.130> you<00:04:31.220> can<00:04:31.370> bring<00:04:31.610> in<00:04:31.880> an<00:04:32.530> appropriate 00:04:33.900 --> 00:04:33.910 align:start position:0% that you can bring in an appropriate 00:04:33.910 --> 00:04:36.070 align:start position:0% that you can bring in an appropriate consensus<00:04:34.910> depending<00:04:35.330> on<00:04:35.450> the<00:04:35.539> scenario<00:04:35.750> that 00:04:36.070 --> 00:04:36.080 align:start position:0% consensus depending on the scenario that 00:04:36.080 --> 00:04:38.800 align:start position:0% consensus depending on the scenario that you're<00:04:36.380> trying<00:04:36.860> to<00:04:36.979> solve<00:04:37.250> for<00:04:37.550> so<00:04:38.150> you<00:04:38.720> know 00:04:38.800 --> 00:04:38.810 align:start position:0% you're trying to solve for so you know 00:04:38.810 --> 00:04:40.300 align:start position:0% you're trying to solve for so you know proof-of-work<00:04:39.260> operating<00:04:39.950> on<00:04:40.039> a<00:04:40.070> public 00:04:40.300 --> 00:04:40.310 align:start position:0% proof-of-work operating on a public 00:04:40.310 --> 00:04:41.310 align:start position:0% proof-of-work operating on a public chain<00:04:40.640> or 00:04:41.310 --> 00:04:41.320 align:start position:0% chain or 00:04:41.320 --> 00:04:42.720 align:start position:0% chain or of<00:04:41.410> stake<00:04:41.710> in<00:04:41.890> the<00:04:41.980> eventual<00:04:42.370> roadmap<00:04:42.700> of 00:04:42.720 --> 00:04:42.730 align:start position:0% of stake in the eventual roadmap of 00:04:42.730 --> 00:04:45.480 align:start position:0% of stake in the eventual roadmap of etherium<00:04:43.300> has<00:04:43.660> its<00:04:43.930> its<00:04:44.170> validity<00:04:44.920> and<00:04:45.250> a<00:04:45.340> lot 00:04:45.480 --> 00:04:45.490 align:start position:0% etherium has its its validity and a lot 00:04:45.490 --> 00:04:47.010 align:start position:0% etherium has its its validity and a lot of<00:04:45.520> value<00:04:45.970> in<00:04:46.000> terms<00:04:46.210> of<00:04:46.390> what<00:04:46.570> it's<00:04:46.690> trying<00:04:46.870> to 00:04:47.010 --> 00:04:47.020 align:start position:0% of value in terms of what it's trying to 00:04:47.020 --> 00:04:49.020 align:start position:0% of value in terms of what it's trying to accomplish<00:04:47.320> for<00:04:47.680> a<00:04:47.740> public<00:04:48.070> network<00:04:48.190> but<00:04:48.850> we 00:04:49.020 --> 00:04:49.030 align:start position:0% accomplish for a public network but we 00:04:49.030 --> 00:04:50.790 align:start position:0% accomplish for a public network but we think<00:04:49.270> that<00:04:49.300> in<00:04:49.510> different<00:04:49.840> contexts<00:04:50.440> with 00:04:50.790 --> 00:04:50.800 align:start position:0% think that in different contexts with 00:04:50.800 --> 00:04:51.780 align:start position:0% think that in different contexts with different<00:04:51.070> numbers<00:04:51.220> of<00:04:51.400> participants 00:04:51.780 --> 00:04:51.790 align:start position:0% different numbers of participants 00:04:51.790 --> 00:04:53.220 align:start position:0% different numbers of participants operating<00:04:52.630> different<00:04:52.900> types<00:04:53.080> of 00:04:53.220 --> 00:04:53.230 align:start position:0% operating different types of 00:04:53.230 --> 00:04:54.630 align:start position:0% operating different types of applications<00:04:53.830> there<00:04:54.220> may<00:04:54.340> be<00:04:54.370> other 00:04:54.630 --> 00:04:54.640 align:start position:0% applications there may be other 00:04:54.640 --> 00:04:56.130 align:start position:0% applications there may be other consensus<00:04:55.240> mechanisms<00:04:55.780> that<00:04:55.900> are<00:04:55.960> better 00:04:56.130 --> 00:04:56.140 align:start position:0% consensus mechanisms that are better 00:04:56.140 --> 00:04:57.840 align:start position:0% consensus mechanisms that are better suited<00:04:56.410> so<00:04:57.100> that's<00:04:57.280> one<00:04:57.520> thing<00:04:57.700> on 00:04:57.840 --> 00:04:57.850 align:start position:0% suited so that's one thing on 00:04:57.850 --> 00:05:01.080 align:start position:0% suited so that's one thing on scalability<00:04:59.100> we're<00:05:00.100> also<00:05:00.220> building<00:05:00.520> to 00:05:01.080 --> 00:05:01.090 align:start position:0% scalability we're also building to 00:05:01.090 --> 00:05:02.550 align:start position:0% scalability we're also building to ensure<00:05:01.330> that<00:05:01.480> the<00:05:01.630> technology<00:05:02.170> that<00:05:02.200> we 00:05:02.550 --> 00:05:02.560 align:start position:0% ensure that the technology that we 00:05:02.560 --> 00:05:04.620 align:start position:0% ensure that the technology that we develop<00:05:03.220> is<00:05:03.370> completely<00:05:03.850> agnostic<00:05:04.060> to<00:05:04.420> server 00:05:04.620 --> 00:05:04.630 align:start position:0% develop is completely agnostic to server 00:05:04.630 --> 00:05:06.150 align:start position:0% develop is completely agnostic to server infrastructure<00:05:05.200> whether<00:05:05.410> it<00:05:05.620> be<00:05:05.710> cloud<00:05:05.980> or 00:05:06.150 --> 00:05:06.160 align:start position:0% infrastructure whether it be cloud or 00:05:06.160 --> 00:05:07.800 align:start position:0% infrastructure whether it be cloud or on-premise<00:05:06.280> infrastructure<00:05:07.150> I<00:05:07.300> mean<00:05:07.660> quite 00:05:07.800 --> 00:05:07.810 align:start position:0% on-premise infrastructure I mean quite 00:05:07.810 --> 00:05:09.360 align:start position:0% on-premise infrastructure I mean quite similar<00:05:08.170> to<00:05:08.260> what<00:05:08.380> Victor<00:05:08.680> mentioned<00:05:08.860> so<00:05:09.190> that 00:05:09.360 --> 00:05:09.370 align:start position:0% similar to what Victor mentioned so that 00:05:09.370 --> 00:05:11.490 align:start position:0% similar to what Victor mentioned so that as<00:05:09.550> we<00:05:09.580> scale<00:05:10.420> this<00:05:10.720> and<00:05:10.960> as<00:05:11.020> we<00:05:11.140> go<00:05:11.320> into 00:05:11.490 --> 00:05:11.500 align:start position:0% as we scale this and as we go into 00:05:11.500 --> 00:05:13.190 align:start position:0% as we scale this and as we go into networks<00:05:12.010> of<00:05:12.190> companies<00:05:12.610> at<00:05:12.790> all<00:05:12.940> today 00:05:13.190 --> 00:05:13.200 align:start position:0% networks of companies at all today 00:05:13.200 --> 00:05:15.540 align:start position:0% networks of companies at all today operate<00:05:14.200> on<00:05:14.320> different<00:05:14.550> traditional 00:05:15.540 --> 00:05:15.550 align:start position:0% operate on different traditional 00:05:15.550 --> 00:05:17.010 align:start position:0% operate on different traditional infrastructure<00:05:15.700> some<00:05:16.390> of<00:05:16.510> which<00:05:16.630> are<00:05:16.750> moving 00:05:17.010 --> 00:05:17.020 align:start position:0% infrastructure some of which are moving 00:05:17.020 --> 00:05:18.360 align:start position:0% infrastructure some of which are moving into<00:05:17.200> the<00:05:17.290> cloud<00:05:17.530> and<00:05:17.830> they'll<00:05:18.220> have 00:05:18.360 --> 00:05:18.370 align:start position:0% into the cloud and they'll have 00:05:18.370 --> 00:05:20.370 align:start position:0% into the cloud and they'll have different<00:05:18.670> cloud<00:05:18.880> providers<00:05:19.450> how<00:05:19.990> do<00:05:20.050> we<00:05:20.170> make 00:05:20.370 --> 00:05:20.380 align:start position:0% different cloud providers how do we make 00:05:20.380 --> 00:05:22.290 align:start position:0% different cloud providers how do we make sure<00:05:20.560> that<00:05:20.740> the<00:05:21.040> the<00:05:21.550> connectivity<00:05:22.210> between 00:05:22.290 --> 00:05:22.300 align:start position:0% sure that the the connectivity between 00:05:22.300 --> 00:05:23.550 align:start position:0% sure that the the connectivity between these<00:05:22.630> different<00:05:22.660> infrastructures<00:05:23.290> is 00:05:23.550 --> 00:05:23.560 align:start position:0% these different infrastructures is 00:05:23.560 --> 00:05:25.260 align:start position:0% these different infrastructures is solved<00:05:23.920> using<00:05:24.040> a<00:05:24.220> blockchain<00:05:24.490> that<00:05:25.030> we<00:05:25.120> can 00:05:25.260 --> 00:05:25.270 align:start position:0% solved using a blockchain that we can 00:05:25.270 --> 00:05:26.940 align:start position:0% solved using a blockchain that we can solve<00:05:25.480> things<00:05:25.660> like<00:05:25.840> p2p<00:05:26.200> latency<00:05:26.650> when<00:05:26.830> we 00:05:26.940 --> 00:05:26.950 align:start position:0% solve things like p2p latency when we 00:05:26.950 --> 00:05:28.530 align:start position:0% solve things like p2p latency when we want<00:05:27.100> transactions<00:05:27.730> to<00:05:27.880> move<00:05:28.000> seamlessly 00:05:28.530 --> 00:05:28.540 align:start position:0% want transactions to move seamlessly 00:05:28.540 --> 00:05:31.320 align:start position:0% want transactions to move seamlessly around<00:05:29.110> the<00:05:29.200> world<00:05:29.370> so<00:05:30.370> that<00:05:30.730> kind<00:05:31.090> of<00:05:31.120> leads 00:05:31.320 --> 00:05:31.330 align:start position:0% around the world so that kind of leads 00:05:31.330 --> 00:05:33.000 align:start position:0% around the world so that kind of leads us<00:05:31.480> to<00:05:31.660> performance<00:05:32.200> which<00:05:32.350> is<00:05:32.470> obviously<00:05:32.860> an 00:05:33.000 --> 00:05:33.010 align:start position:0% us to performance which is obviously an 00:05:33.010 --> 00:05:35.190 align:start position:0% us to performance which is obviously an enormous<00:05:33.400> reason<00:05:33.760> why<00:05:33.880> large<00:05:34.570> companies<00:05:35.020> have 00:05:35.190 --> 00:05:35.200 align:start position:0% enormous reason why large companies have 00:05:35.200 --> 00:05:37.050 align:start position:0% enormous reason why large companies have run<00:05:35.320> into<00:05:35.460> restrictions<00:05:36.460> when<00:05:36.610> they<00:05:36.760> want<00:05:37.000> to 00:05:37.050 --> 00:05:37.060 align:start position:0% run into restrictions when they want to 00:05:37.060 --> 00:05:39.750 align:start position:0% run into restrictions when they want to use<00:05:37.240> athyrium<00:05:37.750> to<00:05:37.900> do<00:05:37.990> anything<00:05:38.760> within 00:05:39.750 --> 00:05:39.760 align:start position:0% use athyrium to do anything within 00:05:39.760 --> 00:05:41.190 align:start position:0% use athyrium to do anything within certain<00:05:40.030> context<00:05:40.570> if<00:05:40.660> you<00:05:40.750> think<00:05:40.960> of<00:05:41.050> like<00:05:41.170> a 00:05:41.190 --> 00:05:41.200 align:start position:0% certain context if you think of like a 00:05:41.200 --> 00:05:42.810 align:start position:0% certain context if you think of like a very<00:05:41.440> simple<00:05:41.830> example<00:05:41.950> high<00:05:42.370> frequency 00:05:42.810 --> 00:05:42.820 align:start position:0% very simple example high frequency 00:05:42.820 --> 00:05:44.640 align:start position:0% very simple example high frequency trading<00:05:43.090> in<00:05:43.270> a<00:05:43.330> financial<00:05:43.480> market<00:05:44.110> it's 00:05:44.640 --> 00:05:44.650 align:start position:0% trading in a financial market it's 00:05:44.650 --> 00:05:46.500 align:start position:0% trading in a financial market it's pretty<00:05:44.920> obvious<00:05:45.340> that<00:05:45.370> running<00:05:46.180> that<00:05:46.300> on<00:05:46.420> the 00:05:46.500 --> 00:05:46.510 align:start position:0% pretty obvious that running that on the 00:05:46.510 --> 00:05:47.820 align:start position:0% pretty obvious that running that on the public<00:05:46.750> athyrium<00:05:47.170> network<00:05:47.410> would<00:05:47.530> would 00:05:47.820 --> 00:05:47.830 align:start position:0% public athyrium network would would 00:05:47.830 --> 00:05:50.430 align:start position:0% public athyrium network would would cause<00:05:48.070> problems<00:05:48.480> just<00:05:49.480> because<00:05:49.750> of<00:05:49.780> the<00:05:49.900> sheer 00:05:50.430 --> 00:05:50.440 align:start position:0% cause problems just because of the sheer 00:05:50.440 --> 00:05:52.440 align:start position:0% cause problems just because of the sheer nature<00:05:50.770> and<00:05:51.250> size<00:05:51.580> of<00:05:51.820> transaction 00:05:52.440 --> 00:05:52.450 align:start position:0% nature and size of transaction 00:05:52.450 --> 00:05:54.120 align:start position:0% nature and size of transaction throughput<00:05:52.750> that<00:05:52.900> you<00:05:52.990> would<00:05:53.140> need<00:05:53.260> so<00:05:53.980> on 00:05:54.120 --> 00:05:54.130 align:start position:0% throughput that you would need so on 00:05:54.130 --> 00:05:55.710 align:start position:0% throughput that you would need so on performance<00:05:54.730> we've<00:05:54.910> got<00:05:55.120> kind<00:05:55.390> of<00:05:55.450> two 00:05:55.710 --> 00:05:55.720 align:start position:0% performance we've got kind of two 00:05:55.720 --> 00:05:57.810 align:start position:0% performance we've got kind of two parallel<00:05:56.620> focuses<00:05:57.130> that<00:05:57.280> we're<00:05:57.400> working<00:05:57.700> on 00:05:57.810 --> 00:05:57.820 align:start position:0% parallel focuses that we're working on 00:05:57.820 --> 00:05:59.550 align:start position:0% parallel focuses that we're working on right<00:05:58.000> now<00:05:58.030> starting<00:05:58.750> with<00:05:58.900> a<00:05:58.930> suite<00:05:59.290> of<00:05:59.320> high 00:05:59.550 --> 00:05:59.560 align:start position:0% right now starting with a suite of high 00:05:59.560 --> 00:06:02.700 align:start position:0% right now starting with a suite of high performance<00:06:00.090> throughput<00:06:01.090> api's<00:06:01.500> to<00:06:02.500> kind<00:06:02.680> of 00:06:02.700 --> 00:06:02.710 align:start position:0% performance throughput api's to kind of 00:06:02.710 --> 00:06:04.140 align:start position:0% performance throughput api's to kind of compliment<00:06:03.220> or<00:06:03.310> be<00:06:03.400> alternatives<00:06:03.940> to<00:06:04.120> the 00:06:04.140 --> 00:06:04.150 align:start position:0% compliment or be alternatives to the 00:06:04.150 --> 00:06:05.820 align:start position:0% compliment or be alternatives to the available<00:06:04.660> web<00:06:04.810> three<00:06:05.020> api<00:06:05.320> that<00:06:05.410> you<00:06:05.680> can 00:06:05.820 --> 00:06:05.830 align:start position:0% available web three api that you can 00:06:05.830 --> 00:06:07.590 align:start position:0% available web three api that you can find<00:06:06.070> or<00:06:06.310> that<00:06:06.700> you<00:06:06.790> can<00:06:06.910> use<00:06:07.060> for<00:06:07.240> the<00:06:07.330> public 00:06:07.590 --> 00:06:07.600 align:start position:0% find or that you can use for the public 00:06:07.600 --> 00:06:09.210 align:start position:0% find or that you can use for the public athyrium<00:06:07.960> network<00:06:08.230> so<00:06:08.650> that<00:06:08.680> we<00:06:08.890> can<00:06:09.070> get 00:06:09.210 --> 00:06:09.220 align:start position:0% athyrium network so that we can get 00:06:09.220 --> 00:06:11.370 align:start position:0% athyrium network so that we can get closer<00:06:09.580> to<00:06:10.030> that<00:06:10.240> enterprise<00:06:11.170> level 00:06:11.370 --> 00:06:11.380 align:start position:0% closer to that enterprise level 00:06:11.380 --> 00:06:12.930 align:start position:0% closer to that enterprise level transaction<00:06:12.010> throughput<00:06:12.310> that's<00:06:12.460> necessary 00:06:12.930 --> 00:06:12.940 align:start position:0% transaction throughput that's necessary 00:06:12.940 --> 00:06:15.210 align:start position:0% transaction throughput that's necessary for<00:06:13.120> a<00:06:13.150> lot<00:06:13.330> of<00:06:13.420> these<00:06:13.510> use<00:06:13.690> cases<00:06:14.040> we've<00:06:15.040> also 00:06:15.210 --> 00:06:15.220 align:start position:0% for a lot of these use cases we've also 00:06:15.220 --> 00:06:16.920 align:start position:0% for a lot of these use cases we've also designed<00:06:15.640> and<00:06:16.090> we're<00:06:16.210> soon<00:06:16.420> starting<00:06:16.840> the 00:06:16.920 --> 00:06:16.930 align:start position:0% designed and we're soon starting the 00:06:16.930 --> 00:06:19.110 align:start position:0% designed and we're soon starting the process<00:06:17.140> of<00:06:17.560> implementing<00:06:18.120> enterprise 00:06:19.110 --> 00:06:19.120 align:start position:0% process of implementing enterprise 00:06:19.120 --> 00:06:21.780 align:start position:0% process of implementing enterprise modifications<00:06:20.020> at<00:06:20.170> the<00:06:20.290> vm<00:06:20.650> level<00:06:21.070> so<00:06:21.520> that<00:06:21.550> we 00:06:21.780 --> 00:06:21.790 align:start position:0% modifications at the vm level so that we 00:06:21.790 --> 00:06:23.370 align:start position:0% modifications at the vm level so that we can<00:06:21.970> start<00:06:22.210> looking<00:06:22.420> at<00:06:22.810> parallel 00:06:23.370 --> 00:06:23.380 align:start position:0% can start looking at parallel 00:06:23.380 --> 00:06:25.020 align:start position:0% can start looking at parallel transaction<00:06:23.950> processing<00:06:24.400> for<00:06:24.790> smart 00:06:25.020 --> 00:06:25.030 align:start position:0% transaction processing for smart 00:06:25.030 --> 00:06:26.910 align:start position:0% transaction processing for smart contracts<00:06:25.480> when<00:06:26.050> it<00:06:26.170> makes<00:06:26.350> sense<00:06:26.560> when 00:06:26.910 --> 00:06:26.920 align:start position:0% contracts when it makes sense when 00:06:26.920 --> 00:06:28.590 align:start position:0% contracts when it makes sense when transaction<00:06:27.490> dependencies<00:06:28.030> are<00:06:28.180> at<00:06:28.270> a<00:06:28.300> state 00:06:28.590 --> 00:06:28.600 align:start position:0% transaction dependencies are at a state 00:06:28.600 --> 00:06:30.540 align:start position:0% transaction dependencies are at a state where<00:06:29.110> there<00:06:29.260> are<00:06:29.410> not<00:06:29.620> too<00:06:30.100> many<00:06:30.130> of<00:06:30.460> them 00:06:30.540 --> 00:06:30.550 align:start position:0% where there are not too many of them 00:06:30.550 --> 00:06:31.860 align:start position:0% where there are not too many of them depending<00:06:30.970> on<00:06:31.060> the<00:06:31.150> application<00:06:31.510> depending 00:06:31.860 --> 00:06:31.870 align:start position:0% depending on the application depending 00:06:31.870 --> 00:06:33.300 align:start position:0% depending on the application depending on<00:06:32.080> the<00:06:32.170> industry<00:06:32.380> so<00:06:32.710> that<00:06:32.830> we<00:06:32.950> can<00:06:33.100> really 00:06:33.300 --> 00:06:33.310 align:start position:0% on the industry so that we can really 00:06:33.310 --> 00:06:35.160 align:start position:0% on the industry so that we can really crank<00:06:33.640> through<00:06:34.000> the<00:06:34.510> performance<00:06:35.020> that's 00:06:35.160 --> 00:06:35.170 align:start position:0% crank through the performance that's 00:06:35.170 --> 00:06:37.920 align:start position:0% crank through the performance that's necessary<00:06:35.680> on<00:06:35.830> these<00:06:35.980> networks<00:06:36.540> now<00:06:37.540> overall 00:06:37.920 --> 00:06:37.930 align:start position:0% necessary on these networks now overall 00:06:37.930 --> 00:06:39.930 align:start position:0% necessary on these networks now overall when<00:06:38.320> we're<00:06:38.470> when<00:06:38.980> we<00:06:39.100> identify<00:06:39.640> kind<00:06:39.880> of 00:06:39.930 --> 00:06:39.940 align:start position:0% when we're when we identify kind of 00:06:39.940 --> 00:06:42.060 align:start position:0% when we're when we identify kind of priorities<00:06:40.450> for<00:06:40.660> our<00:06:40.810> for<00:06:41.470> our<00:06:41.500> development 00:06:42.060 --> 00:06:42.070 align:start position:0% priorities for our for our development 00:06:42.070 --> 00:06:44.160 align:start position:0% priorities for our for our development team<00:06:42.100> for<00:06:42.370> our<00:06:42.460> engineers<00:06:42.970> we<00:06:43.450> kind<00:06:43.900> of<00:06:43.960> go 00:06:44.160 --> 00:06:44.170 align:start position:0% team for our engineers we kind of go 00:06:44.170 --> 00:06:45.420 align:start position:0% team for our engineers we kind of go back<00:06:44.350> to<00:06:44.380> some<00:06:44.710> very<00:06:44.860> simple<00:06:45.070> design 00:06:45.420 --> 00:06:45.430 align:start position:0% back to some very simple design 00:06:45.430 --> 00:06:48.360 align:start position:0% back to some very simple design principles<00:06:46.050> and<00:06:47.050> you<00:06:47.860> know<00:06:47.950> when<00:06:48.100> you<00:06:48.190> when 00:06:48.360 --> 00:06:48.370 align:start position:0% principles and you know when you when 00:06:48.370 --> 00:06:50.190 align:start position:0% principles and you know when you when you<00:06:48.400> consider<00:06:48.730> the<00:06:48.940> enterprise<00:06:49.240> market<00:06:49.270> the 00:06:50.190 --> 00:06:50.200 align:start position:0% you consider the enterprise market the 00:06:50.200 --> 00:06:51.720 align:start position:0% you consider the enterprise market the biggest<00:06:50.380> thing<00:06:50.680> that<00:06:50.710> I<00:06:50.860> kind<00:06:51.070> of<00:06:51.100> look<00:06:51.340> at<00:06:51.490> is 00:06:51.720 --> 00:06:51.730 align:start position:0% biggest thing that I kind of look at is 00:06:51.730 --> 00:06:54.720 align:start position:0% biggest thing that I kind of look at is their<00:06:52.360> need<00:06:52.720> and<00:06:53.040> expectation<00:06:54.040> of<00:06:54.130> Technology 00:06:54.720 --> 00:06:54.730 align:start position:0% their need and expectation of Technology 00:06:54.730 --> 00:06:55.320 align:start position:0% their need and expectation of Technology maturity 00:06:55.320 --> 00:06:55.330 align:start position:0% maturity 00:06:55.330 --> 00:06:57.570 align:start position:0% maturity and<00:06:55.449> as<00:06:56.199> much<00:06:56.530> as<00:06:56.560> it's<00:06:56.860> incredible<00:06:57.340> to<00:06:57.400> watch 00:06:57.570 --> 00:06:57.580 align:start position:0% and as much as it's incredible to watch 00:06:57.580 --> 00:06:58.950 align:start position:0% and as much as it's incredible to watch what's<00:06:57.819> happening<00:06:57.909> in<00:06:58.210> this<00:06:58.330> space<00:06:58.539> we<00:06:58.780> all 00:06:58.950 --> 00:06:58.960 align:start position:0% what's happening in this space we all 00:06:58.960 --> 00:07:00.540 align:start position:0% what's happening in this space we all can<00:06:59.199> recognize<00:06:59.650> that<00:06:59.830> this<00:06:59.949> is<00:07:00.009> an<00:07:00.189> extremely 00:07:00.540 --> 00:07:00.550 align:start position:0% can recognize that this is an extremely 00:07:00.550 --> 00:07:02.939 align:start position:0% can recognize that this is an extremely nascent<00:07:01.060> space<00:07:01.330> and<00:07:01.960> nascent<00:07:02.229> technology 00:07:02.939 --> 00:07:02.949 align:start position:0% nascent space and nascent technology 00:07:02.949 --> 00:07:05.640 align:start position:0% nascent space and nascent technology scares<00:07:03.400> large<00:07:04.060> enterprises<00:07:04.539> because<00:07:05.409> there's 00:07:05.640 --> 00:07:05.650 align:start position:0% scares large enterprises because there's 00:07:05.650 --> 00:07:07.200 align:start position:0% scares large enterprises because there's unanswered<00:07:06.129> questions<00:07:06.639> and<00:07:06.849> unsolved 00:07:07.200 --> 00:07:07.210 align:start position:0% unanswered questions and unsolved 00:07:07.210 --> 00:07:09.360 align:start position:0% unanswered questions and unsolved problems<00:07:07.780> so<00:07:08.319> we're<00:07:08.500> trying<00:07:08.650> to<00:07:08.830> bring<00:07:08.979> a<00:07:09.099> lens 00:07:09.360 --> 00:07:09.370 align:start position:0% problems so we're trying to bring a lens 00:07:09.370 --> 00:07:13.469 align:start position:0% problems so we're trying to bring a lens of<00:07:10.469> enterprise<00:07:11.469> maturity<00:07:12.129> so<00:07:12.849> that<00:07:13.210> means 00:07:13.469 --> 00:07:13.479 align:start position:0% of enterprise maturity so that means 00:07:13.479 --> 00:07:15.600 align:start position:0% of enterprise maturity so that means that<00:07:13.659> when<00:07:14.139> possible<00:07:14.500> and<00:07:15.039> when<00:07:15.129> relevant 00:07:15.600 --> 00:07:15.610 align:start position:0% that when possible and when relevant 00:07:15.610 --> 00:07:17.429 align:start position:0% that when possible and when relevant bringing<00:07:16.389> in<00:07:16.509> existing<00:07:17.169> enterprise 00:07:17.429 --> 00:07:17.439 align:start position:0% bringing in existing enterprise 00:07:17.439 --> 00:07:19.649 align:start position:0% bringing in existing enterprise frameworks<00:07:18.159> existing<00:07:18.669> enterprise<00:07:18.879> languages 00:07:19.649 --> 00:07:19.659 align:start position:0% frameworks existing enterprise languages 00:07:19.659 --> 00:07:22.140 align:start position:0% frameworks existing enterprise languages and<00:07:19.840> existing<00:07:20.560> enterprise<00:07:20.710> tools<00:07:21.250> and<00:07:21.580> making 00:07:22.140 --> 00:07:22.150 align:start position:0% and existing enterprise tools and making 00:07:22.150 --> 00:07:23.610 align:start position:0% and existing enterprise tools and making them<00:07:22.330> a<00:07:22.389> meaningful<00:07:22.810> part<00:07:23.169> of<00:07:23.289> a<00:07:23.349> blockchain 00:07:23.610 --> 00:07:23.620 align:start position:0% them a meaningful part of a blockchain 00:07:23.620 --> 00:07:25.409 align:start position:0% them a meaningful part of a blockchain infrastructure<00:07:24.430> so<00:07:24.819> that<00:07:24.849> it's<00:07:25.120> a<00:07:25.210> more 00:07:25.409 --> 00:07:25.419 align:start position:0% infrastructure so that it's a more 00:07:25.419 --> 00:07:27.540 align:start position:0% infrastructure so that it's a more familiar<00:07:25.629> and<00:07:26.169> seamless<00:07:26.680> transition<00:07:27.250> when<00:07:27.430> we 00:07:27.540 --> 00:07:27.550 align:start position:0% familiar and seamless transition when we 00:07:27.550 --> 00:07:30.360 align:start position:0% familiar and seamless transition when we go<00:07:27.669> to<00:07:27.699> make<00:07:27.969> that<00:07:28.120> infrastructure<00:07:28.419> change<00:07:29.370> so 00:07:30.360 --> 00:07:30.370 align:start position:0% go to make that infrastructure change so 00:07:30.370 --> 00:07:32.249 align:start position:0% go to make that infrastructure change so our<00:07:30.580> goal<00:07:30.819> as<00:07:31.180> I<00:07:31.240> said<00:07:31.690> is<00:07:31.930> to<00:07:32.110> make 00:07:32.249 --> 00:07:32.259 align:start position:0% our goal as I said is to make 00:07:32.259 --> 00:07:34.409 align:start position:0% our goal as I said is to make blockchains<00:07:32.860> a<00:07:33.250> very<00:07:33.550> evident<00:07:34.030> and<00:07:34.270> obvious 00:07:34.409 --> 00:07:34.419 align:start position:0% blockchains a very evident and obvious 00:07:34.419 --> 00:07:36.089 align:start position:0% blockchains a very evident and obvious next<00:07:34.900> step<00:07:35.080> in<00:07:35.500> how<00:07:35.680> do<00:07:35.740> we<00:07:35.889> make 00:07:36.089 --> 00:07:36.099 align:start position:0% next step in how do we make 00:07:36.099 --> 00:07:38.189 align:start position:0% next step in how do we make infrastructures<00:07:36.849> of<00:07:36.969> the<00:07:37.330> past<00:07:37.569> get<00:07:37.840> replaced 00:07:38.189 --> 00:07:38.199 align:start position:0% infrastructures of the past get replaced 00:07:38.199 --> 00:07:40.260 align:start position:0% infrastructures of the past get replaced with<00:07:38.349> infrastructures<00:07:38.949> of<00:07:38.979> the<00:07:39.159> future<00:07:39.460> you 00:07:40.260 --> 00:07:40.270 align:start position:0% with infrastructures of the future you 00:07:40.270 --> 00:07:41.490 align:start position:0% with infrastructures of the future you know<00:07:40.360> digital<00:07:40.750> infrastructure<00:07:40.990> and<00:07:41.440> the 00:07:41.490 --> 00:07:41.500 align:start position:0% know digital infrastructure and the 00:07:41.500 --> 00:07:43.260 align:start position:0% know digital infrastructure and the replacing<00:07:42.099> the<00:07:42.370> replacement<00:07:42.849> of<00:07:42.879> legacy 00:07:43.260 --> 00:07:43.270 align:start position:0% replacing the replacement of legacy 00:07:43.270 --> 00:07:44.969 align:start position:0% replacing the replacement of legacy systems<00:07:43.690> and<00:07:43.870> large<00:07:44.020> companies<00:07:44.409> is<00:07:44.590> not<00:07:44.740> a<00:07:44.770> new 00:07:44.969 --> 00:07:44.979 align:start position:0% systems and large companies is not a new 00:07:44.979 --> 00:07:46.830 align:start position:0% systems and large companies is not a new topic<00:07:45.159> that<00:07:45.849> was<00:07:46.000> introduced<00:07:46.389> just<00:07:46.569> because 00:07:46.830 --> 00:07:46.840 align:start position:0% topic that was introduced just because 00:07:46.840 --> 00:07:48.749 align:start position:0% topic that was introduced just because blockchain<00:07:47.139> showed<00:07:47.529> up<00:07:47.650> on<00:07:47.770> the<00:07:47.800> scene<00:07:47.919> but 00:07:48.749 --> 00:07:48.759 align:start position:0% blockchain showed up on the scene but 00:07:48.759 --> 00:07:50.670 align:start position:0% blockchain showed up on the scene but black<00:07:48.969> chains<00:07:49.240> as<00:07:49.389> we<00:07:49.539> all<00:07:49.719> know<00:07:49.960> our<00:07:50.409> kind<00:07:50.620> of 00:07:50.670 --> 00:07:50.680 align:start position:0% black chains as we all know our kind of 00:07:50.680 --> 00:07:52.019 align:start position:0% black chains as we all know our kind of an<00:07:50.770> evident<00:07:51.099> tool<00:07:51.310> that<00:07:51.580> needs<00:07:51.759> to<00:07:51.940> be 00:07:52.019 --> 00:07:52.029 align:start position:0% an evident tool that needs to be 00:07:52.029 --> 00:07:53.909 align:start position:0% an evident tool that needs to be included<00:07:52.150> in<00:07:52.629> how<00:07:52.750> we<00:07:52.810> do<00:07:53.050> that<00:07:53.169> redesign<00:07:53.650> so 00:07:53.909 --> 00:07:53.919 align:start position:0% included in how we do that redesign so 00:07:53.919 --> 00:07:55.260 align:start position:0% included in how we do that redesign so you<00:07:54.460> know<00:07:54.550> the<00:07:54.669> more<00:07:54.819> we<00:07:54.969> can<00:07:55.000> make<00:07:55.240> that 00:07:55.260 --> 00:07:55.270 align:start position:0% you know the more we can make that 00:07:55.270 --> 00:07:57.179 align:start position:0% you know the more we can make that seamless<00:07:55.840> and<00:07:55.960> obvious<00:07:56.319> the<00:07:56.560> better<00:07:56.979> off 00:07:57.179 --> 00:07:57.189 align:start position:0% seamless and obvious the better off 00:07:57.189 --> 00:07:58.740 align:start position:0% seamless and obvious the better off it'll<00:07:57.490> be<00:07:57.580> in<00:07:57.699> terms<00:07:57.879> of<00:07:58.000> the<00:07:58.120> transition<00:07:58.599> for 00:07:58.740 --> 00:07:58.750 align:start position:0% it'll be in terms of the transition for 00:07:58.750 --> 00:08:01.920 align:start position:0% it'll be in terms of the transition for these<00:07:58.840> large<00:07:59.050> organizations<00:08:00.419> now<00:08:01.419> as<00:08:01.599> we<00:08:01.779> all 00:08:01.920 --> 00:08:01.930 align:start position:0% these large organizations now as we all 00:08:01.930 --> 00:08:04.439 align:start position:0% these large organizations now as we all know<00:08:02.219> and<00:08:03.219> we<00:08:03.400> constantly<00:08:03.879> hear<00:08:04.150> this<00:08:04.300> from 00:08:04.439 --> 00:08:04.449 align:start position:0% know and we constantly hear this from 00:08:04.449 --> 00:08:06.269 align:start position:0% know and we constantly hear this from innovators<00:08:04.870> in<00:08:04.990> this<00:08:05.110> space<00:08:05.349> there<00:08:06.009> is<00:08:06.159> an 00:08:06.269 --> 00:08:06.279 align:start position:0% innovators in this space there is an 00:08:06.279 --> 00:08:08.010 align:start position:0% innovators in this space there is an enormous<00:08:06.759> amount<00:08:07.029> of<00:08:07.090> opportunity<00:08:07.659> everybody 00:08:08.010 --> 00:08:08.020 align:start position:0% enormous amount of opportunity everybody 00:08:08.020 --> 00:08:09.200 align:start position:0% enormous amount of opportunity everybody who's<00:08:08.229> here<00:08:08.469> in<00:08:08.560> this<00:08:08.680> room<00:08:08.949> although 00:08:09.200 --> 00:08:09.210 align:start position:0% who's here in this room although 00:08:09.210 --> 00:08:11.909 align:start position:0% who's here in this room although athyrium<00:08:10.210> is<00:08:10.300> kind<00:08:10.509> of<00:08:10.599> at<00:08:10.779> that<00:08:11.139> state<00:08:11.620> of<00:08:11.770> no 00:08:11.909 --> 00:08:11.919 align:start position:0% athyrium is kind of at that state of no 00:08:11.919 --> 00:08:13.290 align:start position:0% athyrium is kind of at that state of no longer<00:08:12.099> being<00:08:12.250> an<00:08:12.550> infant<00:08:12.849> and<00:08:13.000> probably 00:08:13.290 --> 00:08:13.300 align:start position:0% longer being an infant and probably 00:08:13.300 --> 00:08:14.879 align:start position:0% longer being an infant and probably being<00:08:13.479> more<00:08:13.719> of<00:08:13.779> a<00:08:13.839> toddler<00:08:14.080> right<00:08:14.440> now<00:08:14.620> and 00:08:14.879 --> 00:08:14.889 align:start position:0% being more of a toddler right now and 00:08:14.889 --> 00:08:16.950 align:start position:0% being more of a toddler right now and there's<00:08:15.370> this<00:08:15.550> enormously<00:08:16.210> growing<00:08:16.690> group<00:08:16.870> of 00:08:16.950 --> 00:08:16.960 align:start position:0% there's this enormously growing group of 00:08:16.960 --> 00:08:18.689 align:start position:0% there's this enormously growing group of developers<00:08:17.229> that<00:08:17.500> are<00:08:17.680> kind<00:08:18.219> of<00:08:18.279> being 00:08:18.689 --> 00:08:18.699 align:start position:0% developers that are kind of being 00:08:18.699 --> 00:08:20.550 align:start position:0% developers that are kind of being aggregated<00:08:19.240> around<00:08:19.690> this<00:08:19.779> technology<00:08:20.349> we're 00:08:20.550 --> 00:08:20.560 align:start position:0% aggregated around this technology we're 00:08:20.560 --> 00:08:22.529 align:start position:0% aggregated around this technology we're still<00:08:20.770> the<00:08:20.889> pioneers<00:08:21.370> you<00:08:21.969> know<00:08:22.060> everybody<00:08:22.419> in 00:08:22.529 --> 00:08:22.539 align:start position:0% still the pioneers you know everybody in 00:08:22.539 --> 00:08:24.029 align:start position:0% still the pioneers you know everybody in this<00:08:22.659> room<00:08:22.750> that's<00:08:23.110> working<00:08:23.379> on<00:08:23.469> a<00:08:23.500> project<00:08:23.740> as 00:08:24.029 --> 00:08:24.039 align:start position:0% this room that's working on a project as 00:08:24.039 --> 00:08:26.219 align:start position:0% this room that's working on a project as a<00:08:24.069> pioneer<00:08:24.339> there's<00:08:24.819> a<00:08:24.879> ton<00:08:25.150> of<00:08:25.229> opportunity 00:08:26.219 --> 00:08:26.229 align:start position:0% a pioneer there's a ton of opportunity 00:08:26.229 --> 00:08:28.309 align:start position:0% a pioneer there's a ton of opportunity for<00:08:26.259> everybody<00:08:26.650> to<00:08:26.949> carve<00:08:27.219> out<00:08:27.400> interesting 00:08:28.309 --> 00:08:28.319 align:start position:0% for everybody to carve out interesting 00:08:28.319 --> 00:08:30.629 align:start position:0% for everybody to carve out interesting markets<00:08:29.319> and<00:08:29.500> interesting<00:08:29.949> use<00:08:30.099> cases<00:08:30.370> that 00:08:30.629 --> 00:08:30.639 align:start position:0% markets and interesting use cases that 00:08:30.639 --> 00:08:32.579 align:start position:0% markets and interesting use cases that maybe<00:08:30.789> nobody<00:08:31.120> else<00:08:31.300> has<00:08:31.449> thought<00:08:31.629> of<00:08:31.870> but<00:08:32.560> I 00:08:32.579 --> 00:08:32.589 align:start position:0% maybe nobody else has thought of but I 00:08:32.589 --> 00:08:34.199 align:start position:0% maybe nobody else has thought of but I suspect<00:08:33.070> I'm<00:08:33.190> not<00:08:33.339> the<00:08:33.430> only<00:08:33.579> one<00:08:33.699> who<00:08:33.969> really 00:08:34.199 --> 00:08:34.209 align:start position:0% suspect I'm not the only one who really 00:08:34.209 --> 00:08:36.329 align:start position:0% suspect I'm not the only one who really thinks<00:08:34.240> about<00:08:34.599> this<00:08:35.320> and<00:08:35.560> gets<00:08:35.709> excited<00:08:36.219> by 00:08:36.329 --> 00:08:36.339 align:start position:0% thinks about this and gets excited by 00:08:36.339 --> 00:08:37.889 align:start position:0% thinks about this and gets excited by this<00:08:36.399> but<00:08:36.729> also<00:08:36.820> gets<00:08:37.060> equally<00:08:37.390> terrified<00:08:37.719> by 00:08:37.889 --> 00:08:37.899 align:start position:0% this but also gets equally terrified by 00:08:37.899 --> 00:08:39.839 align:start position:0% this but also gets equally terrified by this<00:08:37.959> because<00:08:38.620> the<00:08:38.979> the<00:08:39.250> nature<00:08:39.610> of<00:08:39.640> those 00:08:39.839 --> 00:08:39.849 align:start position:0% this because the the nature of those 00:08:39.849 --> 00:08:42.000 align:start position:0% this because the the nature of those ambitions<00:08:40.360> is<00:08:40.539> not<00:08:40.719> you<00:08:41.380> know<00:08:41.409> what<00:08:41.709> a<00:08:41.740> typical 00:08:42.000 --> 00:08:42.010 align:start position:0% ambitions is not you know what a typical 00:08:42.010 --> 00:08:44.100 align:start position:0% ambitions is not you know what a typical kind<00:08:42.640> of<00:08:42.699> app<00:08:42.820> developer<00:08:43.449> might<00:08:43.630> be<00:08:43.750> looking 00:08:44.100 --> 00:08:44.110 align:start position:0% kind of app developer might be looking 00:08:44.110 --> 00:08:45.449 align:start position:0% kind of app developer might be looking at<00:08:44.260> when<00:08:44.440> they<00:08:44.470> want<00:08:44.709> to<00:08:44.829> accelerate<00:08:45.220> your 00:08:45.449 --> 00:08:45.459 align:start position:0% at when they want to accelerate your 00:08:45.459 --> 00:08:47.009 align:start position:0% at when they want to accelerate your food<00:08:45.670> delivery<00:08:46.089> we're<00:08:46.510> talking<00:08:46.899> about 00:08:47.009 --> 00:08:47.019 align:start position:0% food delivery we're talking about 00:08:47.019 --> 00:08:48.630 align:start position:0% food delivery we're talking about changing<00:08:47.620> how<00:08:47.740> people<00:08:47.769> interact<00:08:48.279> with<00:08:48.550> each 00:08:48.630 --> 00:08:48.640 align:start position:0% changing how people interact with each 00:08:48.640 --> 00:08:50.519 align:start position:0% changing how people interact with each other<00:08:48.790> how<00:08:49.209> organizations<00:08:49.990> transact<00:08:50.470> with 00:08:50.519 --> 00:08:50.529 align:start position:0% other how organizations transact with 00:08:50.529 --> 00:08:52.230 align:start position:0% other how organizations transact with each<00:08:50.680> other<00:08:50.860> on<00:08:50.980> a<00:08:51.040> global<00:08:51.220> basis<00:08:51.670> and<00:08:51.850> it's 00:08:52.230 --> 00:08:52.240 align:start position:0% each other on a global basis and it's 00:08:52.240 --> 00:08:54.630 align:start position:0% each other on a global basis and it's important<00:08:52.810> but<00:08:53.380> it's<00:08:53.440> also<00:08:53.740> critically 00:08:54.630 --> 00:08:54.640 align:start position:0% important but it's also critically 00:08:54.640 --> 00:08:56.490 align:start position:0% important but it's also critically important<00:08:55.000> that<00:08:55.120> we<00:08:55.209> get<00:08:55.360> it<00:08:55.510> right<00:08:55.720> so<00:08:56.380> that 00:08:56.490 --> 00:08:56.500 align:start position:0% important that we get it right so that 00:08:56.500 --> 00:08:58.259 align:start position:0% important that we get it right so that we<00:08:56.560> need<00:08:56.709> to<00:08:56.829> slow<00:08:57.100> down<00:08:57.279> and<00:08:57.519> kind<00:08:57.640> of<00:08:57.760> bring 00:08:58.259 --> 00:08:58.269 align:start position:0% we need to slow down and kind of bring 00:08:58.269 --> 00:09:00.019 align:start position:0% we need to slow down and kind of bring that<00:08:58.300> enterprise<00:08:58.779> maturity<00:08:59.320> to<00:08:59.350> this<00:08:59.560> market 00:09:00.019 --> 00:09:00.029 align:start position:0% that enterprise maturity to this market 00:09:00.029 --> 00:09:03.889 align:start position:0% that enterprise maturity to this market now<00:09:01.029> I<00:09:01.060> can<00:09:01.329> tell<00:09:01.360> you<00:09:01.720> how<00:09:02.290> easy<00:09:02.320> it<00:09:02.800> is<00:09:02.920> to 00:09:03.889 --> 00:09:03.899 align:start position:0% now I can tell you how easy it is to 00:09:03.899 --> 00:09:08.650 align:start position:0% now I can tell you how easy it is to easily<00:09:04.899> become<00:09:05.140> Desai<00:09:06.100> be<00:09:06.819> is<00:09:07.720> going<00:09:07.870> after 00:09:08.650 --> 00:09:08.660 align:start position:0% easily become Desai be is going after 00:09:08.660 --> 00:09:10.809 align:start position:0% easily become Desai be is going after when<00:09:08.899> we<00:09:09.019> look<00:09:09.199> at<00:09:09.290> like<00:09:09.500> you<00:09:09.800> know<00:09:10.310> in<00:09:10.670> our 00:09:10.809 --> 00:09:10.819 align:start position:0% when we look at like you know in our 00:09:10.819 --> 00:09:12.850 align:start position:0% when we look at like you know in our case<00:09:11.120> just<00:09:11.720> looking<00:09:11.990> at<00:09:12.110> the<00:09:12.230> nature<00:09:12.529> of<00:09:12.560> a 00:09:12.850 --> 00:09:12.860 align:start position:0% case just looking at the nature of a 00:09:12.860 --> 00:09:14.559 align:start position:0% case just looking at the nature of a small<00:09:13.190> team<00:09:13.430> trying<00:09:13.759> to<00:09:13.850> tackle<00:09:14.029> big<00:09:14.329> global 00:09:14.559 --> 00:09:14.569 align:start position:0% small team trying to tackle big global 00:09:14.569 --> 00:09:17.350 align:start position:0% small team trying to tackle big global problems<00:09:15.790> but<00:09:16.790> I'll<00:09:16.879> tell<00:09:17.029> you<00:09:17.089> what<00:09:17.269> it<00:09:17.329> is 00:09:17.350 --> 00:09:17.360 align:start position:0% problems but I'll tell you what it is 00:09:17.360 --> 00:09:18.999 align:start position:0% problems but I'll tell you what it is that<00:09:17.600> motivates<00:09:17.959> us<00:09:18.110> at<00:09:18.259> new<00:09:18.379> co<00:09:18.560> I<00:09:18.589> mean<00:09:18.860> we're 00:09:18.999 --> 00:09:19.009 align:start position:0% that motivates us at new co I mean we're 00:09:19.009 --> 00:09:21.939 align:start position:0% that motivates us at new co I mean we're a<00:09:19.040> small<00:09:19.399> local<00:09:19.699> startup<00:09:20.449> in<00:09:20.629> Toronto<00:09:21.379> you 00:09:21.939 --> 00:09:21.949 align:start position:0% a small local startup in Toronto you 00:09:21.949 --> 00:09:23.410 align:start position:0% a small local startup in Toronto you know<00:09:22.069> 10<00:09:22.279> people<00:09:22.310> operating<00:09:23.000> out<00:09:23.209> of<00:09:23.240> a 00:09:23.410 --> 00:09:23.420 align:start position:0% know 10 people operating out of a 00:09:23.420 --> 00:09:25.030 align:start position:0% know 10 people operating out of a start-up<00:09:24.050> office<00:09:24.410> going<00:09:24.620> after<00:09:24.949> these 00:09:25.030 --> 00:09:25.040 align:start position:0% start-up office going after these 00:09:25.040 --> 00:09:28.840 align:start position:0% start-up office going after these globally<00:09:26.350> impactful<00:09:27.350> ambitions<00:09:27.980> and<00:09:28.189> I<00:09:28.639> think 00:09:28.840 --> 00:09:28.850 align:start position:0% globally impactful ambitions and I think 00:09:28.850 --> 00:09:30.309 align:start position:0% globally impactful ambitions and I think the<00:09:28.970> simple<00:09:29.300> reason<00:09:29.449> that<00:09:29.600> we<00:09:29.779> can<00:09:29.930> do<00:09:30.050> that<00:09:30.199> is 00:09:30.309 --> 00:09:30.319 align:start position:0% the simple reason that we can do that is 00:09:30.319 --> 00:09:31.389 align:start position:0% the simple reason that we can do that is because<00:09:30.470> there's<00:09:30.800> a<00:09:30.860> vision<00:09:31.160> in<00:09:31.279> this 00:09:31.389 --> 00:09:31.399 align:start position:0% because there's a vision in this 00:09:31.399 --> 00:09:32.860 align:start position:0% because there's a vision in this community<00:09:31.759> that<00:09:31.939> kind<00:09:32.089> of<00:09:32.180> drives<00:09:32.449> us<00:09:32.689> a 00:09:32.860 --> 00:09:32.870 align:start position:0% community that kind of drives us a 00:09:32.870 --> 00:09:34.900 align:start position:0% community that kind of drives us a vision<00:09:33.319> of<00:09:33.500> global<00:09:33.860> changing<00:09:34.399> vision<00:09:34.639> of<00:09:34.759> of 00:09:34.900 --> 00:09:34.910 align:start position:0% vision of global changing vision of of 00:09:34.910 --> 00:09:37.269 align:start position:0% vision of global changing vision of of deep<00:09:35.540> impact<00:09:36.019> that<00:09:36.290> really<00:09:36.529> will<00:09:36.649> will<00:09:37.040> touch 00:09:37.269 --> 00:09:37.279 align:start position:0% deep impact that really will will touch 00:09:37.279 --> 00:09:39.460 align:start position:0% deep impact that really will will touch unreachable<00:09:38.199> previously<00:09:39.199> unreachable 00:09:39.460 --> 00:09:39.470 align:start position:0% unreachable previously unreachable 00:09:39.470 --> 00:09:41.590 align:start position:0% unreachable previously unreachable populations<00:09:40.250> on<00:09:40.399> earth<00:09:40.430> that<00:09:41.060> now<00:09:41.300> the<00:09:41.360> new 00:09:41.590 --> 00:09:41.600 align:start position:0% populations on earth that now the new 00:09:41.600 --> 00:09:44.319 align:start position:0% populations on earth that now the new technology<00:09:42.139> can<00:09:42.290> kind<00:09:42.439> of<00:09:42.470> unlock<00:09:42.970> so<00:09:43.970> in<00:09:44.120> some 00:09:44.319 --> 00:09:44.329 align:start position:0% technology can kind of unlock so in some 00:09:44.329 --> 00:09:46.090 align:start position:0% technology can kind of unlock so in some cases<00:09:44.360> I<00:09:44.810> mean<00:09:45.139> having<00:09:45.379> the<00:09:45.500> financial<00:09:45.949> reach 00:09:46.090 --> 00:09:46.100 align:start position:0% cases I mean having the financial reach 00:09:46.100 --> 00:09:47.470 align:start position:0% cases I mean having the financial reach of<00:09:46.250> these<00:09:46.370> large<00:09:46.579> companies<00:09:47.000> to<00:09:47.180> be<00:09:47.269> able<00:09:47.360> to 00:09:47.470 --> 00:09:47.480 align:start position:0% of these large companies to be able to 00:09:47.480 --> 00:09:49.179 align:start position:0% of these large companies to be able to just<00:09:47.600> dump<00:09:47.959> 50<00:09:48.379> engineers<00:09:48.800> on<00:09:48.980> to<00:09:49.100> a<00:09:49.129> new 00:09:49.179 --> 00:09:49.189 align:start position:0% just dump 50 engineers on to a new 00:09:49.189 --> 00:09:51.460 align:start position:0% just dump 50 engineers on to a new project<00:09:49.670> is<00:09:49.790> helpful<00:09:50.120> but<00:09:50.720> in<00:09:50.839> most<00:09:51.019> cases<00:09:51.139> i 00:09:51.460 --> 00:09:51.470 align:start position:0% project is helpful but in most cases i 00:09:51.470 --> 00:09:52.420 align:start position:0% project is helpful but in most cases i actually<00:09:51.740> think<00:09:51.829> that<00:09:51.920> the<00:09:52.069> meaningful 00:09:52.420 --> 00:09:52.430 align:start position:0% actually think that the meaningful 00:09:52.430 --> 00:09:53.559 align:start position:0% actually think that the meaningful change<00:09:52.639> is<00:09:52.759> going<00:09:52.910> to<00:09:52.970> happen<00:09:53.180> from<00:09:53.329> small 00:09:53.559 --> 00:09:53.569 align:start position:0% change is going to happen from small 00:09:53.569 --> 00:09:54.970 align:start position:0% change is going to happen from small teams<00:09:53.779> like<00:09:53.990> the<00:09:54.019> ones<00:09:54.259> represented<00:09:54.800> here 00:09:54.970 --> 00:09:54.980 align:start position:0% teams like the ones represented here 00:09:54.980 --> 00:09:56.980 align:start position:0% teams like the ones represented here from<00:09:55.459> small<00:09:55.670> companies<00:09:56.089> of<00:09:56.240> developers<00:09:56.720> kind 00:09:56.980 --> 00:09:56.990 align:start position:0% from small companies of developers kind 00:09:56.990 --> 00:09:59.350 align:start position:0% from small companies of developers kind of<00:09:57.050> operating<00:09:57.560> in<00:09:57.709> garages<00:09:58.459> or<00:09:58.879> kind<00:09:59.120> of<00:09:59.209> back 00:09:59.350 --> 00:09:59.360 align:start position:0% of operating in garages or kind of back 00:09:59.360 --> 00:10:01.150 align:start position:0% of operating in garages or kind of back office<00:09:59.660> is<00:09:59.930> saying<00:10:00.199> we<00:10:00.410> have<00:10:00.439> an<00:10:00.680> idea<00:10:00.949> we're 00:10:01.150 --> 00:10:01.160 align:start position:0% office is saying we have an idea we're 00:10:01.160 --> 00:10:02.769 align:start position:0% office is saying we have an idea we're going<00:10:01.189> to<00:10:01.339> change<00:10:01.550> something<00:10:02.029> and<00:10:02.209> i<00:10:02.600> think 00:10:02.769 --> 00:10:02.779 align:start position:0% going to change something and i think 00:10:02.779 --> 00:10:04.660 align:start position:0% going to change something and i think the<00:10:02.870> reason<00:10:03.050> is<00:10:03.290> pretty<00:10:03.529> clear<00:10:04.129> i<00:10:04.160> mean<00:10:04.399> i<00:10:04.459> came 00:10:04.660 --> 00:10:04.670 align:start position:0% the reason is pretty clear i mean i came 00:10:04.670 --> 00:10:08.069 align:start position:0% the reason is pretty clear i mean i came from<00:10:04.790> the<00:10:04.910> enterprise<00:10:05.089> world<00:10:05.949> where<00:10:06.949> you<00:10:07.759> know 00:10:08.069 --> 00:10:08.079 align:start position:0% from the enterprise world where you know 00:10:08.079 --> 00:10:10.119 align:start position:0% from the enterprise world where you know instability<00:10:09.079> and<00:10:09.350> uncertainty<00:10:09.500> scares 00:10:10.119 --> 00:10:10.129 align:start position:0% instability and uncertainty scares 00:10:10.129 --> 00:10:12.970 align:start position:0% instability and uncertainty scares people<00:10:11.000> tremendously<00:10:11.899> and<00:10:12.199> anybody<00:10:12.709> who's 00:10:12.970 --> 00:10:12.980 align:start position:0% people tremendously and anybody who's 00:10:12.980 --> 00:10:14.170 align:start position:0% people tremendously and anybody who's been<00:10:13.100> in<00:10:13.220> the<00:10:13.250> block<00:10:13.490> chain<00:10:13.519> space<00:10:13.910> long 00:10:14.170 --> 00:10:14.180 align:start position:0% been in the block chain space long 00:10:14.180 --> 00:10:15.490 align:start position:0% been in the block chain space long enough<00:10:14.420> knows<00:10:14.630> that<00:10:14.870> if<00:10:14.959> you're<00:10:15.110> scared<00:10:15.439> of 00:10:15.490 --> 00:10:15.500 align:start position:0% enough knows that if you're scared of 00:10:15.500 --> 00:10:18.160 align:start position:0% enough knows that if you're scared of instability<00:10:16.130> you<00:10:16.730> won't<00:10:16.910> last<00:10:17.120> i<00:10:17.540> mean<00:10:17.990> all 00:10:18.160 --> 00:10:18.170 align:start position:0% instability you won't last i mean all 00:10:18.170 --> 00:10:19.480 align:start position:0% instability you won't last i mean all you<00:10:18.290> have<00:10:18.380> to<00:10:18.500> do<00:10:18.589> is<00:10:18.709> look<00:10:18.829> at<00:10:18.949> bitcoin<00:10:19.310> over 00:10:19.480 --> 00:10:19.490 align:start position:0% you have to do is look at bitcoin over 00:10:19.490 --> 00:10:21.100 align:start position:0% you have to do is look at bitcoin over the<00:10:19.579> last<00:10:19.730> seven<00:10:20.060> years<00:10:20.209> or<00:10:20.449> even<00:10:20.480> you<00:10:21.079> know 00:10:21.100 --> 00:10:21.110 align:start position:0% the last seven years or even you know 00:10:21.110 --> 00:10:22.569 align:start position:0% the last seven years or even you know more<00:10:21.319> relevant<00:10:21.740> to<00:10:21.800> this<00:10:21.920> audience<00:10:22.220> look<00:10:22.459> at 00:10:22.569 --> 00:10:22.579 align:start position:0% more relevant to this audience look at 00:10:22.579 --> 00:10:24.610 align:start position:0% more relevant to this audience look at athyrium<00:10:23.060> over<00:10:23.180> the<00:10:23.269> last<00:10:23.389> four<00:10:23.660> months<00:10:23.839> or<00:10:24.170> a 00:10:24.610 --> 00:10:24.620 align:start position:0% athyrium over the last four months or a 00:10:24.620 --> 00:10:26.860 align:start position:0% athyrium over the last four months or a theorem<00:10:25.040> over<00:10:25.189> the<00:10:25.279> last<00:10:25.430> three<00:10:25.759> days<00:10:25.939> I<00:10:26.329> mean 00:10:26.860 --> 00:10:26.870 align:start position:0% theorem over the last three days I mean 00:10:26.870 --> 00:10:28.720 align:start position:0% theorem over the last three days I mean there's<00:10:27.199> always<00:10:27.620> reasons<00:10:27.889> to<00:10:28.279> get<00:10:28.399> nervous 00:10:28.720 --> 00:10:28.730 align:start position:0% there's always reasons to get nervous 00:10:28.730 --> 00:10:31.660 align:start position:0% there's always reasons to get nervous and<00:10:29.149> scared<00:10:29.480> and<00:10:29.779> that's<00:10:30.529> why<00:10:30.740> I'm<00:10:30.889> confident 00:10:31.660 --> 00:10:31.670 align:start position:0% and scared and that's why I'm confident 00:10:31.670 --> 00:10:32.949 align:start position:0% and scared and that's why I'm confident and<00:10:31.850> absolutely<00:10:32.240> certain<00:10:32.630> that<00:10:32.660> it's<00:10:32.870> going 00:10:32.949 --> 00:10:32.959 align:start position:0% and absolutely certain that it's going 00:10:32.959 --> 00:10:35.370 align:start position:0% and absolutely certain that it's going to<00:10:33.019> be<00:10:33.139> small<00:10:33.500> you<00:10:34.250> know<00:10:34.370> startups<00:10:35.029> and 00:10:35.370 --> 00:10:35.380 align:start position:0% to be small you know startups and 00:10:35.380 --> 00:10:38.590 align:start position:0% to be small you know startups and community<00:10:36.380> driven<00:10:37.089> campaigns<00:10:38.089> that<00:10:38.329> really 00:10:38.590 --> 00:10:38.600 align:start position:0% community driven campaigns that really 00:10:38.600 --> 00:10:40.150 align:start position:0% community driven campaigns that really make<00:10:38.750> change<00:10:39.050> rather<00:10:39.290> than<00:10:39.439> large<00:10:39.800> scale 00:10:40.150 --> 00:10:40.160 align:start position:0% make change rather than large scale 00:10:40.160 --> 00:10:43.139 align:start position:0% make change rather than large scale enterprises<00:10:40.550> I<00:10:41.420> mean<00:10:41.870> that<00:10:42.019> said<00:10:42.290> I<00:10:42.319> have<00:10:42.829> no 00:10:43.139 --> 00:10:43.149 align:start position:0% enterprises I mean that said I have no 00:10:43.149 --> 00:10:46.090 align:start position:0% enterprises I mean that said I have no no<00:10:44.149> hard<00:10:44.360> feelings<00:10:44.810> for<00:10:45.139> the<00:10:45.649> large<00:10:45.860> scale 00:10:46.090 --> 00:10:46.100 align:start position:0% no hard feelings for the large scale 00:10:46.100 --> 00:10:47.650 align:start position:0% no hard feelings for the large scale enterprises<00:10:46.220> I<00:10:46.670> came<00:10:46.850> from<00:10:47.000> Deloitte<00:10:47.329> I<00:10:47.420> spent 00:10:47.650 --> 00:10:47.660 align:start position:0% enterprises I came from Deloitte I spent 00:10:47.660 --> 00:10:48.759 align:start position:0% enterprises I came from Deloitte I spent five<00:10:47.810> years<00:10:47.839> there<00:10:48.230> and<00:10:48.350> I<00:10:48.380> think<00:10:48.529> there's<00:10:48.680> an 00:10:48.759 --> 00:10:48.769 align:start position:0% five years there and I think there's an 00:10:48.769 --> 00:10:50.110 align:start position:0% five years there and I think there's an enormously<00:10:49.250> important<00:10:49.730> role<00:10:49.850> for<00:10:49.880> those 00:10:50.110 --> 00:10:50.120 align:start position:0% enormously important role for those 00:10:50.120 --> 00:10:53.259 align:start position:0% enormously important role for those companies<00:10:50.410> as<00:10:51.410> as<00:10:51.860> Victor<00:10:52.339> mentioned<00:10:52.550> you 00:10:53.259 --> 00:10:53.269 align:start position:0% companies as as Victor mentioned you 00:10:53.269 --> 00:10:55.389 align:start position:0% companies as as Victor mentioned you know<00:10:53.300> integration<00:10:54.110> and<00:10:54.410> adoption<00:10:55.069> by<00:10:55.189> large 00:10:55.389 --> 00:10:55.399 align:start position:0% know integration and adoption by large 00:10:55.399 --> 00:10:57.309 align:start position:0% know integration and adoption by large enterprises<00:10:55.819> in<00:10:56.089> education<00:10:56.630> is<00:10:56.779> going<00:10:57.170> to<00:10:57.230> be 00:10:57.309 --> 00:10:57.319 align:start position:0% enterprises in education is going to be 00:10:57.319 --> 00:10:58.809 align:start position:0% enterprises in education is going to be a<00:10:57.350> problem<00:10:57.680> that<00:10:57.980> everybody<00:10:58.100> needs<00:10:58.519> to<00:10:58.730> kind 00:10:58.809 --> 00:10:58.819 align:start position:0% a problem that everybody needs to kind 00:10:58.819 --> 00:11:01.240 align:start position:0% a problem that everybody needs to kind of<00:10:58.939> tackle<00:10:59.180> together<00:10:59.769> but<00:11:00.769> the<00:11:00.889> future<00:11:01.160> of 00:11:01.240 --> 00:11:01.250 align:start position:0% of tackle together but the future of 00:11:01.250 --> 00:11:03.009 align:start position:0% of tackle together but the future of this<00:11:01.339> technology<00:11:01.670> really<00:11:02.059> is<00:11:02.300> be<00:11:02.509> going<00:11:02.809> to<00:11:02.899> be 00:11:03.009 --> 00:11:03.019 align:start position:0% this technology really is be going to be 00:11:03.019 --> 00:11:04.990 align:start position:0% this technology really is be going to be determined<00:11:03.139> by<00:11:03.500> groups<00:11:03.740> like<00:11:03.829> this<00:11:04.189> groups 00:11:04.990 --> 00:11:05.000 align:start position:0% determined by groups like this groups 00:11:05.000 --> 00:11:07.420 align:start position:0% determined by groups like this groups like<00:11:05.089> us<00:11:05.389> so<00:11:06.259> we<00:11:06.439> see<00:11:06.649> the<00:11:06.769> inefficiencies<00:11:06.980> of 00:11:07.420 --> 00:11:07.430 align:start position:0% like us so we see the inefficiencies of 00:11:07.430 --> 00:11:09.129 align:start position:0% like us so we see the inefficiencies of these<00:11:07.699> large<00:11:07.939> companies<00:11:08.360> as<00:11:08.540> an<00:11:08.629> opportunity 00:11:09.129 --> 00:11:09.139 align:start position:0% these large companies as an opportunity 00:11:09.139 --> 00:11:11.199 align:start position:0% these large companies as an opportunity for<00:11:09.230> a<00:11:09.410> new<00:11:09.439> business<00:11:09.740> model<00:11:09.920> and<00:11:10.430> we<00:11:10.850> envision 00:11:11.199 --> 00:11:11.209 align:start position:0% for a new business model and we envision 00:11:11.209 --> 00:11:13.059 align:start position:0% for a new business model and we envision a<00:11:11.300> future<00:11:11.329> where<00:11:11.959> unlike<00:11:12.290> some<00:11:12.920> of<00:11:13.009> the 00:11:13.059 --> 00:11:13.069 align:start position:0% a future where unlike some of the 00:11:13.069 --> 00:11:15.340 align:start position:0% a future where unlike some of the rhetoric<00:11:13.220> of<00:11:13.550> the<00:11:13.670> early<00:11:13.910> blockchain<00:11:14.180> days<00:11:14.540> we 00:11:15.340 --> 00:11:15.350 align:start position:0% rhetoric of the early blockchain days we 00:11:15.350 --> 00:11:17.379 align:start position:0% rhetoric of the early blockchain days we want<00:11:15.589> to<00:11:15.709> allow<00:11:16.069> people<00:11:16.100> to<00:11:16.610> get<00:11:16.730> the<00:11:16.850> services 00:11:17.379 --> 00:11:17.389 align:start position:0% want to allow people to get the services 00:11:17.389 --> 00:11:19.509 align:start position:0% want to allow people to get the services they<00:11:17.449> need<00:11:17.809> from<00:11:18.380> the<00:11:18.559> companies<00:11:18.949> they<00:11:19.160> trust 00:11:19.509 --> 00:11:19.519 align:start position:0% they need from the companies they trust 00:11:19.519 --> 00:11:21.549 align:start position:0% they need from the companies they trust rather<00:11:20.269> than<00:11:20.509> just<00:11:20.720> cutting<00:11:20.930> these<00:11:21.110> companies 00:11:21.549 --> 00:11:21.559 align:start position:0% rather than just cutting these companies 00:11:21.559 --> 00:11:22.450 align:start position:0% rather than just cutting these companies out<00:11:21.740> of<00:11:21.769> the<00:11:21.949> equation 00:11:22.450 --> 00:11:22.460 align:start position:0% out of the equation 00:11:22.460 --> 00:11:24.160 align:start position:0% out of the equation really<00:11:23.000> helping<00:11:23.480> them<00:11:23.630> redesign<00:11:24.020> their 00:11:24.160 --> 00:11:24.170 align:start position:0% really helping them redesign their 00:11:24.170 --> 00:11:26.890 align:start position:0% really helping them redesign their processes<00:11:24.710> to<00:11:24.830> make<00:11:24.860> it<00:11:25.100> better<00:11:25.480> now<00:11:26.480> to<00:11:26.540> do 00:11:26.890 --> 00:11:26.900 align:start position:0% processes to make it better now to do 00:11:26.900 --> 00:11:28.810 align:start position:0% processes to make it better now to do this<00:11:27.080> we're<00:11:27.770> aiming<00:11:27.920> to<00:11:28.100> become<00:11:28.310> a<00:11:28.460> provider 00:11:28.810 --> 00:11:28.820 align:start position:0% this we're aiming to become a provider 00:11:28.820 --> 00:11:31.750 align:start position:0% this we're aiming to become a provider of<00:11:28.940> infrastructure<00:11:29.540> simply<00:11:30.440> put<00:11:30.650> and<00:11:30.920> we<00:11:31.580> want 00:11:31.750 --> 00:11:31.760 align:start position:0% of infrastructure simply put and we want 00:11:31.760 --> 00:11:33.190 align:start position:0% of infrastructure simply put and we want that<00:11:31.820> infrastructure<00:11:32.210> to<00:11:32.570> be<00:11:32.630> leveraged<00:11:32.990> not 00:11:33.190 --> 00:11:33.200 align:start position:0% that infrastructure to be leveraged not 00:11:33.200 --> 00:11:34.810 align:start position:0% that infrastructure to be leveraged not only<00:11:33.470> by<00:11:33.590> these<00:11:33.770> big<00:11:33.950> organizations<00:11:34.610> but<00:11:34.760> also 00:11:34.810 --> 00:11:34.820 align:start position:0% only by these big organizations but also 00:11:34.820 --> 00:11:37.870 align:start position:0% only by these big organizations but also by<00:11:35.240> smaller<00:11:36.110> kind<00:11:36.770> of<00:11:36.920> application<00:11:37.130> driven 00:11:37.870 --> 00:11:37.880 align:start position:0% by smaller kind of application driven 00:11:37.880 --> 00:11:39.430 align:start position:0% by smaller kind of application driven teams<00:11:38.150> that<00:11:38.390> have<00:11:38.540> an<00:11:38.630> ambition<00:11:38.900> to<00:11:39.080> change 00:11:39.430 --> 00:11:39.440 align:start position:0% teams that have an ambition to change 00:11:39.440 --> 00:11:41.740 align:start position:0% teams that have an ambition to change something<00:11:39.860> in<00:11:39.980> the<00:11:40.070> in<00:11:40.280> the<00:11:40.310> industry<00:11:40.880> so<00:11:41.570> are 00:11:41.740 --> 00:11:41.750 align:start position:0% something in the in the industry so are 00:11:41.750 --> 00:11:43.690 align:start position:0% something in the in the industry so are our<00:11:42.170> expectation<00:11:42.950> is<00:11:43.070> that<00:11:43.100> if<00:11:43.310> you<00:11:43.430> have<00:11:43.580> an 00:11:43.690 --> 00:11:43.700 align:start position:0% our expectation is that if you have an 00:11:43.700 --> 00:11:45.610 align:start position:0% our expectation is that if you have an idea<00:11:44.030> that<00:11:44.270> is<00:11:44.420> really<00:11:44.750> enterprise<00:11:45.170> driven 00:11:45.610 --> 00:11:45.620 align:start position:0% idea that is really enterprise driven 00:11:45.620 --> 00:11:47.290 align:start position:0% idea that is really enterprise driven and<00:11:45.800> you<00:11:46.160> need<00:11:46.310> an<00:11:46.400> infrastructure<00:11:47.000> to<00:11:47.090> power 00:11:47.290 --> 00:11:47.300 align:start position:0% and you need an infrastructure to power 00:11:47.300 --> 00:11:49.300 align:start position:0% and you need an infrastructure to power that<00:11:47.570> idea<00:11:47.930> that<00:11:48.170> can<00:11:48.560> be<00:11:48.650> well-suited<00:11:49.100> for 00:11:49.300 --> 00:11:49.310 align:start position:0% that idea that can be well-suited for 00:11:49.310 --> 00:11:50.650 align:start position:0% that idea that can be well-suited for kind<00:11:49.670> of<00:11:49.730> the<00:11:49.850> requirements<00:11:50.540> and 00:11:50.650 --> 00:11:50.660 align:start position:0% kind of the requirements and 00:11:50.660 --> 00:11:52.360 align:start position:0% kind of the requirements and specifications<00:11:50.840> of<00:11:51.470> an<00:11:51.590> enterprise<00:11:51.800> market 00:11:52.360 --> 00:11:52.370 align:start position:0% specifications of an enterprise market 00:11:52.370 --> 00:11:54.610 align:start position:0% specifications of an enterprise market we'd<00:11:52.820> love<00:11:53.060> to<00:11:53.270> be<00:11:53.360> working<00:11:53.720> with<00:11:53.840> you<00:11:54.020> so<00:11:54.590> I 00:11:54.610 --> 00:11:54.620 align:start position:0% we'd love to be working with you so I 00:11:54.620 --> 00:11:56.170 align:start position:0% we'd love to be working with you so I mean<00:11:54.950> by<00:11:55.100> all<00:11:55.220> means<00:11:55.400> please<00:11:55.610> reach<00:11:55.820> out<00:11:55.970> to<00:11:56.030> us 00:11:56.170 --> 00:11:56.180 align:start position:0% mean by all means please reach out to us 00:11:56.180 --> 00:11:58.690 align:start position:0% mean by all means please reach out to us get<00:11:56.510> to<00:11:56.630> know<00:11:56.750> us<00:11:56.930> if<00:11:57.440> you<00:11:57.920> ever<00:11:58.070> decide<00:11:58.430> to<00:11:58.460> do 00:11:58.690 --> 00:11:58.700 align:start position:0% get to know us if you ever decide to do 00:11:58.700 --> 00:12:00.460 align:start position:0% get to know us if you ever decide to do the<00:11:58.820> etherium<00:11:59.300> pilgrimage<00:11:59.810> and<00:11:59.960> come<00:12:00.170> back<00:12:00.290> to 00:12:00.460 --> 00:12:00.470 align:start position:0% the etherium pilgrimage and come back to 00:12:00.470 --> 00:12:02.950 align:start position:0% the etherium pilgrimage and come back to Toronto<00:12:00.860> where<00:12:01.010> it<00:12:01.130> all<00:12:01.250> began<00:12:01.690> you<00:12:02.690> know<00:12:02.780> not 00:12:02.950 --> 00:12:02.960 align:start position:0% Toronto where it all began you know not 00:12:02.960 --> 00:12:04.900 align:start position:0% Toronto where it all began you know not so<00:12:03.140> many<00:12:03.290> years<00:12:03.380> ago<00:12:03.620> let<00:12:04.370> us<00:12:04.460> know<00:12:04.670> and<00:12:04.820> we'll 00:12:04.900 --> 00:12:04.910 align:start position:0% so many years ago let us know and we'll 00:12:04.910 --> 00:12:08.170 align:start position:0% so many years ago let us know and we'll host<00:12:05.300> you<00:12:05.510> while<00:12:05.660> you're<00:12:05.810> there<00:12:07.030> 2016<00:12:08.030> has 00:12:08.170 --> 00:12:08.180 align:start position:0% host you while you're there 2016 has 00:12:08.180 --> 00:12:09.340 align:start position:0% host you while you're there 2016 has been<00:12:08.330> a<00:12:08.360> really<00:12:08.540> interesting<00:12:08.840> year<00:12:09.140> and<00:12:09.290> I'll 00:12:09.340 --> 00:12:09.350 align:start position:0% been a really interesting year and I'll 00:12:09.350 --> 00:12:10.510 align:start position:0% been a really interesting year and I'll spend<00:12:09.560> maybe<00:12:09.710> a<00:12:09.830> minute<00:12:10.130> just<00:12:10.250> kind<00:12:10.490> of 00:12:10.510 --> 00:12:10.520 align:start position:0% spend maybe a minute just kind of 00:12:10.520 --> 00:12:11.740 align:start position:0% spend maybe a minute just kind of looking<00:12:10.790> back<00:12:10.970> at<00:12:11.120> what<00:12:11.210> happened<00:12:11.330> since<00:12:11.630> I 00:12:11.740 --> 00:12:11.750 align:start position:0% looking back at what happened since I 00:12:11.750 --> 00:12:13.720 align:start position:0% looking back at what happened since I spoke<00:12:11.810> at<00:12:12.170> Def<00:12:12.320> Con<00:12:12.350> last<00:12:12.560> year<00:12:13.100> I've<00:12:13.490> been 00:12:13.720 --> 00:12:13.730 align:start position:0% spoke at Def Con last year I've been 00:12:13.730 --> 00:12:15.040 align:start position:0% spoke at Def Con last year I've been referring<00:12:14.210> to<00:12:14.360> this<00:12:14.450> year<00:12:14.660> as<00:12:14.720> kind<00:12:14.930> of<00:12:14.990> the 00:12:15.040 --> 00:12:15.050 align:start position:0% referring to this year as kind of the 00:12:15.050 --> 00:12:16.750 align:start position:0% referring to this year as kind of the year<00:12:15.230> of<00:12:15.320> the<00:12:15.350> blockchain<00:12:15.680> proof<00:12:16.130> of<00:12:16.250> concept 00:12:16.750 --> 00:12:16.760 align:start position:0% year of the blockchain proof of concept 00:12:16.760 --> 00:12:18.550 align:start position:0% year of the blockchain proof of concept and<00:12:17.030> not<00:12:17.450> just<00:12:17.660> because<00:12:17.840> of<00:12:18.020> the<00:12:18.140> number<00:12:18.470> of 00:12:18.550 --> 00:12:18.560 align:start position:0% and not just because of the number of 00:12:18.560 --> 00:12:19.990 align:start position:0% and not just because of the number of prototypes<00:12:18.800> being<00:12:19.310> built<00:12:19.490> but<00:12:19.610> also<00:12:19.760> because 00:12:19.990 --> 00:12:20.000 align:start position:0% prototypes being built but also because 00:12:20.000 --> 00:12:21.850 align:start position:0% prototypes being built but also because the<00:12:20.240> mainstream<00:12:20.390> world<00:12:20.930> is<00:12:21.140> now<00:12:21.260> looking<00:12:21.650> at 00:12:21.850 --> 00:12:21.860 align:start position:0% the mainstream world is now looking at 00:12:21.860 --> 00:12:23.620 align:start position:0% the mainstream world is now looking at Bitcoin<00:12:22.640> and<00:12:22.760> athyrium<00:12:23.180> with<00:12:23.270> a<00:12:23.300> lot<00:12:23.480> more 00:12:23.620 --> 00:12:23.630 align:start position:0% Bitcoin and athyrium with a lot more 00:12:23.630 --> 00:12:24.880 align:start position:0% Bitcoin and athyrium with a lot more interest<00:12:23.960> and<00:12:24.200> saying<00:12:24.380> does<00:12:24.560> this<00:12:24.680> stuff 00:12:24.880 --> 00:12:24.890 align:start position:0% interest and saying does this stuff 00:12:24.890 --> 00:12:27.400 align:start position:0% interest and saying does this stuff actually<00:12:25.070> work<00:12:25.520> but<00:12:26.450> I<00:12:26.660> don't<00:12:27.110> think<00:12:27.290> we're 00:12:27.400 --> 00:12:27.410 align:start position:0% actually work but I don't think we're 00:12:27.410 --> 00:12:28.960 align:start position:0% actually work but I don't think we're the<00:12:27.530> only<00:12:27.620> ones<00:12:27.950> to<00:12:28.160> be<00:12:28.250> frustrated<00:12:28.790> by<00:12:28.910> the 00:12:28.960 --> 00:12:28.970 align:start position:0% the only ones to be frustrated by the 00:12:28.970 --> 00:12:31.990 align:start position:0% the only ones to be frustrated by the fact<00:12:29.060> that<00:12:29.360> pocs<00:12:29.960> can<00:12:30.410> seem<00:12:30.710> to<00:12:30.950> be<00:12:31.100> an<00:12:31.340> endless 00:12:31.990 --> 00:12:32.000 align:start position:0% fact that pocs can seem to be an endless 00:12:32.000 --> 00:12:34.210 align:start position:0% fact that pocs can seem to be an endless cycle<00:12:32.210> of<00:12:32.570> not<00:12:32.780> getting<00:12:33.020> anywhere<00:12:33.470> an<00:12:33.680> endless 00:12:34.210 --> 00:12:34.220 align:start position:0% cycle of not getting anywhere an endless 00:12:34.220 --> 00:12:35.590 align:start position:0% cycle of not getting anywhere an endless cycle<00:12:34.370> of<00:12:34.610> not<00:12:34.790> understanding<00:12:34.910> how<00:12:35.360> you<00:12:35.450> can 00:12:35.590 --> 00:12:35.600 align:start position:0% cycle of not understanding how you can 00:12:35.600 --> 00:12:37.780 align:start position:0% cycle of not understanding how you can actually<00:12:35.990> make<00:12:36.140> meaningful<00:12:36.440> change<00:12:36.830> so<00:12:37.670> as 00:12:37.780 --> 00:12:37.790 align:start position:0% actually make meaningful change so as 00:12:37.790 --> 00:12:39.640 align:start position:0% actually make meaningful change so as exciting<00:12:38.210> as<00:12:38.330> this<00:12:38.450> trend<00:12:38.750> is<00:12:38.900> we<00:12:39.440> need<00:12:39.560> to 00:12:39.640 --> 00:12:39.650 align:start position:0% exciting as this trend is we need to 00:12:39.650 --> 00:12:40.990 align:start position:0% exciting as this trend is we need to figure<00:12:39.800> out<00:12:39.980> how<00:12:40.070> to<00:12:40.160> get<00:12:40.280> beyond<00:12:40.610> this<00:12:40.790> type 00:12:40.990 --> 00:12:41.000 align:start position:0% figure out how to get beyond this type 00:12:41.000 --> 00:12:42.610 align:start position:0% figure out how to get beyond this type of<00:12:41.030> RND<00:12:41.450> work<00:12:41.750> and<00:12:41.930> into<00:12:42.110> real<00:12:42.260> production 00:12:42.610 --> 00:12:42.620 align:start position:0% of RND work and into real production 00:12:42.620 --> 00:12:44.770 align:start position:0% of RND work and into real production work<00:12:42.890> and<00:12:43.100> I'm<00:12:43.610> confident<00:12:44.270> that<00:12:44.360> that's<00:12:44.540> on 00:12:44.770 --> 00:12:44.780 align:start position:0% work and I'm confident that that's on 00:12:44.780 --> 00:12:46.630 align:start position:0% work and I'm confident that that's on the<00:12:44.990> verge<00:12:45.140> of<00:12:45.320> changing<00:12:45.560> and<00:12:45.980> we're<00:12:46.370> making 00:12:46.630 --> 00:12:46.640 align:start position:0% the verge of changing and we're making 00:12:46.640 --> 00:12:48.160 align:start position:0% the verge of changing and we're making sure<00:12:46.820> that<00:12:46.970> if<00:12:47.090> they're<00:12:47.240> that<00:12:47.480> new<00:12:47.690> co<00:12:47.840> is<00:12:47.990> kind 00:12:48.160 --> 00:12:48.170 align:start position:0% sure that if they're that new co is kind 00:12:48.170 --> 00:12:50.230 align:start position:0% sure that if they're that new co is kind of<00:12:48.230> ready<00:12:48.380> to<00:12:48.470> get<00:12:48.710> there<00:12:48.920> now<00:12:49.910> I'll<00:12:50.030> give<00:12:50.150> you 00:12:50.230 --> 00:12:50.240 align:start position:0% of ready to get there now I'll give you 00:12:50.240 --> 00:12:51.610 align:start position:0% of ready to get there now I'll give you kind<00:12:50.360> of<00:12:50.450> one<00:12:50.600> closing<00:12:51.020> thought<00:12:51.230> because<00:12:51.590> I 00:12:51.610 --> 00:12:51.620 align:start position:0% kind of one closing thought because I 00:12:51.620 --> 00:12:52.870 align:start position:0% kind of one closing thought because I know<00:12:51.740> it's<00:12:52.040> the<00:12:52.190> end<00:12:52.310> of<00:12:52.370> the<00:12:52.460> day<00:12:52.610> and<00:12:52.760> it's 00:12:52.870 --> 00:12:52.880 align:start position:0% know it's the end of the day and it's 00:12:52.880 --> 00:12:56.230 align:start position:0% know it's the end of the day and it's been<00:12:53.000> the<00:12:53.090> end<00:12:53.240> of<00:12:53.300> the<00:12:53.360> long<00:12:53.510> week<00:12:54.280> but<00:12:55.280> I<00:12:55.580> want 00:12:56.230 --> 00:12:56.240 align:start position:0% been the end of the long week but I want 00:12:56.240 --> 00:12:57.760 align:start position:0% been the end of the long week but I want to<00:12:56.300> kind<00:12:56.390> of<00:12:56.510> encourage<00:12:56.810> this<00:12:57.080> community<00:12:57.560> if<00:12:57.650> I 00:12:57.760 --> 00:12:57.770 align:start position:0% to kind of encourage this community if I 00:12:57.770 --> 00:12:59.560 align:start position:0% to kind of encourage this community if I if<00:12:58.040> I<00:12:58.160> can<00:12:58.340> do<00:12:58.460> that<00:12:58.490> from<00:12:58.760> my<00:12:58.940> perspective<00:12:59.240> I 00:12:59.560 --> 00:12:59.570 align:start position:0% if I can do that from my perspective I 00:12:59.570 --> 00:13:01.150 align:start position:0% if I can do that from my perspective I mean<00:12:59.600> last<00:12:59.930> year<00:13:00.080> I<00:13:00.200> talked<00:13:00.530> about<00:13:00.710> the 00:13:01.150 --> 00:13:01.160 align:start position:0% mean last year I talked about the 00:13:01.160 --> 00:13:03.100 align:start position:0% mean last year I talked about the floodgates<00:13:02.090> kind<00:13:02.330> of<00:13:02.390> opening<00:13:02.840> and<00:13:03.020> the 00:13:03.100 --> 00:13:03.110 align:start position:0% floodgates kind of opening and the 00:13:03.110 --> 00:13:04.600 align:start position:0% floodgates kind of opening and the mainstream<00:13:03.680> attention<00:13:03.800> kind<00:13:04.250> of<00:13:04.310> dumping 00:13:04.600 --> 00:13:04.610 align:start position:0% mainstream attention kind of dumping 00:13:04.610 --> 00:13:06.250 align:start position:0% mainstream attention kind of dumping into<00:13:04.790> this<00:13:04.940> space<00:13:05.180> because<00:13:05.450> it<00:13:05.600> was<00:13:05.720> 400 00:13:06.250 --> 00:13:06.260 align:start position:0% into this space because it was 400 00:13:06.260 --> 00:13:07.720 align:start position:0% into this space because it was 400 people<00:13:06.530> sitting<00:13:06.830> in<00:13:06.860> a<00:13:06.980> room<00:13:07.070> in<00:13:07.220> London<00:13:07.580> and 00:13:07.720 --> 00:13:07.730 align:start position:0% people sitting in a room in London and 00:13:07.730 --> 00:13:09.370 align:start position:0% people sitting in a room in London and not<00:13:08.240> many<00:13:08.420> people<00:13:08.720> outside<00:13:08.840> of<00:13:09.110> that<00:13:09.170> room<00:13:09.350> had 00:13:09.370 --> 00:13:09.380 align:start position:0% not many people outside of that room had 00:13:09.380 --> 00:13:11.140 align:start position:0% not many people outside of that room had heard<00:13:09.620> about<00:13:09.740> athyrium<00:13:10.250> before<00:13:10.610> I<00:13:10.790> mean<00:13:11.090> I 00:13:11.140 --> 00:13:11.150 align:start position:0% heard about athyrium before I mean I 00:13:11.150 --> 00:13:12.520 align:start position:0% heard about athyrium before I mean I exaggerate<00:13:11.810> but<00:13:11.840> the<00:13:11.990> mainstream<00:13:12.380> world 00:13:12.520 --> 00:13:12.530 align:start position:0% exaggerate but the mainstream world 00:13:12.530 --> 00:13:14.110 align:start position:0% exaggerate but the mainstream world hadn't<00:13:12.920> really<00:13:13.130> heard<00:13:13.250> about<00:13:13.490> athyrium<00:13:13.940> and 00:13:14.110 --> 00:13:14.120 align:start position:0% hadn't really heard about athyrium and 00:13:14.120 --> 00:13:15.610 align:start position:0% hadn't really heard about athyrium and for<00:13:14.630> those<00:13:14.750> of<00:13:14.930> you<00:13:15.020> who<00:13:15.140> have<00:13:15.230> been<00:13:15.380> involved 00:13:15.610 --> 00:13:15.620 align:start position:0% for those of you who have been involved 00:13:15.620 --> 00:13:16.930 align:start position:0% for those of you who have been involved in<00:13:15.770> this<00:13:15.890> space<00:13:16.070> long<00:13:16.340> enough<00:13:16.550> you<00:13:16.640> know<00:13:16.790> that 00:13:16.930 --> 00:13:16.940 align:start position:0% in this space long enough you know that 00:13:16.940 --> 00:13:18.670 align:start position:0% in this space long enough you know that that's<00:13:17.090> completely<00:13:17.480> changed<00:13:17.960> we've<00:13:18.440> seen 00:13:18.670 --> 00:13:18.680 align:start position:0% that's completely changed we've seen 00:13:18.680 --> 00:13:21.220 align:start position:0% that's completely changed we've seen companies<00:13:18.980> get<00:13:19.370> funded<00:13:19.880> and<00:13:20.120> founded<00:13:20.990> and 00:13:21.220 --> 00:13:21.230 align:start position:0% companies get funded and founded and 00:13:21.230 --> 00:13:22.900 align:start position:0% companies get funded and founded and projects<00:13:21.950> being<00:13:22.100> launched<00:13:22.490> over<00:13:22.610> the<00:13:22.760> last 00:13:22.900 --> 00:13:22.910 align:start position:0% projects being launched over the last 00:13:22.910 --> 00:13:24.400 align:start position:0% projects being launched over the last year<00:13:23.150> that<00:13:23.180> have<00:13:23.390> really<00:13:23.570> thrown<00:13:23.900> etherium 00:13:24.400 --> 00:13:24.410 align:start position:0% year that have really thrown etherium 00:13:24.410 --> 00:13:25.840 align:start position:0% year that have really thrown etherium into<00:13:24.560> the<00:13:24.620> spotlight<00:13:25.100> I<00:13:25.310> think<00:13:25.730> we've 00:13:25.840 --> 00:13:25.850 align:start position:0% into the spotlight I think we've 00:13:25.850 --> 00:13:27.340 align:start position:0% into the spotlight I think we've probably<00:13:26.120> seen<00:13:26.480> the<00:13:26.600> etherium<00:13:26.930> community 00:13:27.340 --> 00:13:27.350 align:start position:0% probably seen the etherium community 00:13:27.350 --> 00:13:29.410 align:start position:0% probably seen the etherium community grow<00:13:27.530> by<00:13:27.740> 10<00:13:27.980> x<00:13:28.130> over<00:13:28.340> the<00:13:28.400> last<00:13:28.610> year<00:13:28.880> it's 00:13:29.410 --> 00:13:29.420 align:start position:0% grow by 10 x over the last year it's 00:13:29.420 --> 00:13:31.390 align:start position:0% grow by 10 x over the last year it's easily<00:13:29.750> become<00:13:30.140> the<00:13:30.290> most<00:13:30.470> readily<00:13:31.010> available 00:13:31.390 --> 00:13:31.400 align:start position:0% easily become the most readily available 00:13:31.400 --> 00:13:33.460 align:start position:0% easily become the most readily available and<00:13:31.790> most<00:13:31.970> used<00:13:32.240> technology<00:13:32.570> in<00:13:32.900> R&D<00:13:33.170> labs 00:13:33.460 --> 00:13:33.470 align:start position:0% and most used technology in R&D labs 00:13:33.470 --> 00:13:35.560 align:start position:0% and most used technology in R&D labs around<00:13:33.650> the<00:13:33.860> world<00:13:33.920> it<00:13:34.310> hit<00:13:34.820> its<00:13:34.940> 1<00:13:35.150> billion 00:13:35.560 --> 00:13:35.570 align:start position:0% around the world it hit its 1 billion 00:13:35.570 --> 00:13:36.280 align:start position:0% around the world it hit its 1 billion dollar<00:13:35.750> miles 00:13:36.280 --> 00:13:36.290 align:start position:0% dollar miles 00:13:36.290 --> 00:13:37.960 align:start position:0% dollar miles this<00:13:36.589> year<00:13:36.829> which<00:13:36.980> is<00:13:37.009> tremendously<00:13:37.790> valuable 00:13:37.960 --> 00:13:37.970 align:start position:0% this year which is tremendously valuable 00:13:37.970 --> 00:13:43.210 align:start position:0% this year which is tremendously valuable for<00:13:38.420> this<00:13:38.540> community<00:13:39.639> and<00:13:41.110> and<00:13:42.110> not<00:13:43.040> to 00:13:43.210 --> 00:13:43.220 align:start position:0% for this community and and not to 00:13:43.220 --> 00:13:45.280 align:start position:0% for this community and and not to understate<00:13:43.670> vitalik<00:13:44.180> turn<00:13:44.360> 22<00:13:44.810> this<00:13:44.959> year<00:13:45.019> I 00:13:45.280 --> 00:13:45.290 align:start position:0% understate vitalik turn 22 this year I 00:13:45.290 --> 00:13:48.610 align:start position:0% understate vitalik turn 22 this year I mean<00:13:45.470> that's<00:13:45.589> a<00:13:45.740> big<00:13:45.949> milestone<00:13:46.339> here<00:13:47.620> so 00:13:48.610 --> 00:13:48.620 align:start position:0% mean that's a big milestone here so 00:13:48.620 --> 00:13:50.560 align:start position:0% mean that's a big milestone here so quite<00:13:48.889> the<00:13:49.070> year<00:13:49.190> for<00:13:49.250> theriyum<00:13:49.910> but<00:13:50.360> we<00:13:50.449> also 00:13:50.560 --> 00:13:50.570 align:start position:0% quite the year for theriyum but we also 00:13:50.570 --> 00:13:51.910 align:start position:0% quite the year for theriyum but we also learned<00:13:50.870> some<00:13:51.050> lessons<00:13:51.079> this<00:13:51.470> year<00:13:51.529> I<00:13:51.709> mean<00:13:51.860> I 00:13:51.910 --> 00:13:51.920 align:start position:0% learned some lessons this year I mean I 00:13:51.920 --> 00:13:53.470 align:start position:0% learned some lessons this year I mean I think<00:13:51.949> we<00:13:52.160> also<00:13:52.310> realize<00:13:53.149> that<00:13:53.180> there<00:13:53.449> are 00:13:53.470 --> 00:13:53.480 align:start position:0% think we also realize that there are 00:13:53.480 --> 00:13:54.660 align:start position:0% think we also realize that there are challenges<00:13:53.720> that<00:13:54.139> we<00:13:54.259> hadn't<00:13:54.500> necessarily 00:13:54.660 --> 00:13:54.670 align:start position:0% challenges that we hadn't necessarily 00:13:54.670 --> 00:13:56.680 align:start position:0% challenges that we hadn't necessarily anticipated<00:13:55.670> challenges<00:13:56.060> to<00:13:56.180> decentralized 00:13:56.680 --> 00:13:56.690 align:start position:0% anticipated challenges to decentralized 00:13:56.690 --> 00:13:58.629 align:start position:0% anticipated challenges to decentralized governance<00:13:56.750> and<00:13:57.290> the<00:13:57.680> difficult<00:13:58.130> task<00:13:58.310> of 00:13:58.629 --> 00:13:58.639 align:start position:0% governance and the difficult task of 00:13:58.639 --> 00:14:00.009 align:start position:0% governance and the difficult task of dealing<00:13:58.819> with<00:13:59.000> diverse<00:13:59.420> groups<00:13:59.750> that<00:13:59.930> have 00:14:00.009 --> 00:14:00.019 align:start position:0% dealing with diverse groups that have 00:14:00.019 --> 00:14:01.900 align:start position:0% dealing with diverse groups that have diverse<00:14:00.350> interests<00:14:00.769> and<00:14:01.009> how<00:14:01.370> do<00:14:01.430> we<00:14:01.519> properly 00:14:01.900 --> 00:14:01.910 align:start position:0% diverse interests and how do we properly 00:14:01.910 --> 00:14:03.340 align:start position:0% diverse interests and how do we properly solve<00:14:02.300> that<00:14:02.449> we<00:14:02.660> realize<00:14:03.019> that<00:14:03.199> there<00:14:03.319> are 00:14:03.340 --> 00:14:03.350 align:start position:0% solve that we realize that there are 00:14:03.350 --> 00:14:05.499 align:start position:0% solve that we realize that there are challenges<00:14:03.620> that<00:14:04.490> are<00:14:04.639> legal<00:14:05.029> and<00:14:05.149> regulatory 00:14:05.499 --> 00:14:05.509 align:start position:0% challenges that are legal and regulatory 00:14:05.509 --> 00:14:07.269 align:start position:0% challenges that are legal and regulatory that<00:14:05.870> apply<00:14:06.139> to<00:14:06.199> token<00:14:06.620> systems<00:14:07.040> and 00:14:07.269 --> 00:14:07.279 align:start position:0% that apply to token systems and 00:14:07.279 --> 00:14:09.670 align:start position:0% that apply to token systems and challenges<00:14:08.120> with<00:14:08.329> the<00:14:08.930> development<00:14:09.470> of<00:14:09.529> like 00:14:09.670 --> 00:14:09.680 align:start position:0% challenges with the development of like 00:14:09.680 --> 00:14:12.400 align:start position:0% challenges with the development of like secure<00:14:10.370> enterprise<00:14:11.000> software<00:14:11.269> or<00:14:11.750> a<00:14:11.990> thirion 00:14:12.400 --> 00:14:12.410 align:start position:0% secure enterprise software or a thirion 00:14:12.410 --> 00:14:14.110 align:start position:0% secure enterprise software or a thirion based<00:14:12.649> software<00:14:12.860> but<00:14:13.639> I<00:14:13.670> think<00:14:13.850> all<00:14:13.940> of<00:14:13.970> this 00:14:14.110 --> 00:14:14.120 align:start position:0% based software but I think all of this 00:14:14.120 --> 00:14:15.610 align:start position:0% based software but I think all of this points<00:14:14.480> to<00:14:14.540> kind<00:14:14.750> of<00:14:14.810> a<00:14:14.870> productive<00:14:15.290> year<00:14:15.440> for 00:14:15.610 --> 00:14:15.620 align:start position:0% points to kind of a productive year for 00:14:15.620 --> 00:14:18.129 align:start position:0% points to kind of a productive year for etherium<00:14:16.040> and<00:14:16.160> kind<00:14:16.339> of<00:14:16.399> a<00:14:16.519> very<00:14:17.180> positive 00:14:18.129 --> 00:14:18.139 align:start position:0% etherium and kind of a very positive 00:14:18.139 --> 00:14:19.749 align:start position:0% etherium and kind of a very positive looking<00:14:18.769> year<00:14:18.980> ahead<00:14:19.220> and<00:14:19.490> I'm<00:14:19.579> really 00:14:19.749 --> 00:14:19.759 align:start position:0% looking year ahead and I'm really 00:14:19.759 --> 00:14:21.150 align:start position:0% looking year ahead and I'm really looking<00:14:19.940> forward<00:14:20.120> to<00:14:20.360> being<00:14:20.569> here<00:14:20.720> next<00:14:20.930> year 00:14:21.150 --> 00:14:21.160 align:start position:0% looking forward to being here next year 00:14:21.160 --> 00:14:23.530 align:start position:0% looking forward to being here next year so<00:14:22.160> I'll<00:14:22.730> just<00:14:22.759> leave<00:14:23.000> you<00:14:23.060> with<00:14:23.240> that<00:14:23.360> and<00:14:23.509> I 00:14:23.530 --> 00:14:23.540 align:start position:0% so I'll just leave you with that and I 00:14:23.540 --> 00:14:24.939 align:start position:0% so I'll just leave you with that and I mean<00:14:23.690> before<00:14:23.839> I<00:14:24.019> wrap<00:14:24.290> up<00:14:24.470> because<00:14:24.709> I<00:14:24.740> am<00:14:24.920> the 00:14:24.939 --> 00:14:24.949 align:start position:0% mean before I wrap up because I am the 00:14:24.949 --> 00:14:26.949 align:start position:0% mean before I wrap up because I am the last<00:14:25.130> presentation<00:14:25.579> of<00:14:25.819> the<00:14:25.880> day<00:14:26.060> I<00:14:26.269> thought 00:14:26.949 --> 00:14:26.959 align:start position:0% last presentation of the day I thought 00:14:26.959 --> 00:14:29.740 align:start position:0% last presentation of the day I thought it'd<00:14:27.110> be<00:14:27.139> worthwhile<00:14:27.440> to<00:14:27.759> maybe<00:14:28.759> do<00:14:29.209> a<00:14:29.240> quick 00:14:29.740 --> 00:14:29.750 align:start position:0% it'd be worthwhile to maybe do a quick 00:14:29.750 --> 00:14:31.470 align:start position:0% it'd be worthwhile to maybe do a quick thank<00:14:29.959> you<00:14:30.079> and<00:14:30.290> round<00:14:30.410> of<00:14:30.529> applause<00:14:30.800> to<00:14:31.009> Ming 00:14:31.470 --> 00:14:31.480 align:start position:0% thank you and round of applause to Ming 00:14:31.480 --> 00:14:37.620 align:start position:0% thank you and round of applause to Ming Vitalik<00:14:32.480> George<00:14:33.110> the<00:14:33.410> etherium<00:14:33.860> foundation<00:14:34.519> I 00:14:37.620 --> 00:14:37.630 align:start position:0% 00:14:37.630 --> 00:14:39.550 align:start position:0% didn't<00:14:38.630> want<00:14:38.720> to<00:14:38.810> steal<00:14:38.990> your<00:14:39.139> thunder<00:14:39.410> Ming 00:14:39.550 --> 00:14:39.560 align:start position:0% didn't want to steal your thunder Ming 00:14:39.560 --> 00:14:40.600 align:start position:0% didn't want to steal your thunder Ming but<00:14:39.740> you<00:14:39.800> probably<00:14:40.040> wouldn<00:14:40.310> to<00:14:40.370> thank 00:14:40.600 --> 00:14:40.610 align:start position:0% but you probably wouldn to thank 00:14:40.610 --> 00:14:43.990 align:start position:0% but you probably wouldn to thank yourself<00:14:40.819> so<00:14:42.040> thanks<00:14:43.040> Matt<00:14:43.250> I<00:14:43.579> really 00:14:43.990 --> 00:14:44.000 align:start position:0% yourself so thanks Matt I really 00:14:44.000 --> 00:14:47.689 align:start position:0% yourself so thanks Matt I really appreciate<00:14:44.480> it 00:14:47.689 --> 00:14:47.699 align:start position:0% 00:14:47.699 --> 00:14:49.759 align:start position:0% you