WEBVTT Kind: captions Language: en 00:00:17.690 --> 00:00:20.390 align:start position:0% so<00:00:18.690> the<00:00:18.779> panel<00:00:19.109> topic<00:00:19.560> is<00:00:19.770> the<00:00:19.920> pathway<00:00:20.160> to 00:00:20.390 --> 00:00:20.400 align:start position:0% so the panel topic is the pathway to 00:00:20.400 --> 00:00:22.550 align:start position:0% so the panel topic is the pathway to etherium<00:00:20.939> adoption<00:00:21.449> and<00:00:21.630> it's<00:00:22.199> going<00:00:22.350> to<00:00:22.439> be 00:00:22.550 --> 00:00:22.560 align:start position:0% etherium adoption and it's going to be 00:00:22.560 --> 00:00:23.779 align:start position:0% etherium adoption and it's going to be kind<00:00:22.710> of<00:00:22.859> just<00:00:23.010> a<00:00:23.100> little<00:00:23.279> round<00:00:23.430> table 00:00:23.779 --> 00:00:23.789 align:start position:0% kind of just a little round table 00:00:23.789 --> 00:00:25.550 align:start position:0% kind of just a little round table discussion<00:00:24.240> about<00:00:24.510> how<00:00:24.990> these<00:00:25.140> gentlemen 00:00:25.550 --> 00:00:25.560 align:start position:0% discussion about how these gentlemen 00:00:25.560 --> 00:00:27.109 align:start position:0% discussion about how these gentlemen think<00:00:25.859> we<00:00:26.039> will<00:00:26.220> achieve<00:00:26.519> the<00:00:27.029> ultimate 00:00:27.109 --> 00:00:27.119 align:start position:0% think we will achieve the ultimate 00:00:27.119 --> 00:00:29.779 align:start position:0% think we will achieve the ultimate adoption<00:00:27.840> of<00:00:27.990> everything<00:00:28.590> we've<00:00:28.740> seen<00:00:29.010> really 00:00:29.779 --> 00:00:29.789 align:start position:0% adoption of everything we've seen really 00:00:29.789 --> 00:00:36.380 align:start position:0% adoption of everything we've seen really over<00:00:30.090> the<00:00:30.179> last<00:00:30.210> week<00:00:30.570> so<00:00:35.149> seems<00:00:36.149> to<00:00:36.239> be<00:00:36.300> going 00:00:36.380 --> 00:00:36.390 align:start position:0% over the last week so seems to be going 00:00:36.390 --> 00:00:39.619 align:start position:0% over the last week so seems to be going pretty<00:00:36.510> well<00:00:36.690> so<00:00:36.960> far<00:00:36.989> I<00:00:37.350> think<00:00:37.440> that<00:00:38.629> today 00:00:39.619 --> 00:00:39.629 align:start position:0% pretty well so far I think that today 00:00:39.629 --> 00:00:43.160 align:start position:0% pretty well so far I think that today how<00:00:39.809> do<00:00:39.870> we<00:00:40.050> achieve<00:00:40.800> adoption<00:00:41.670> theorem<00:00:42.480> well 00:00:43.160 --> 00:00:43.170 align:start position:0% how do we achieve adoption theorem well 00:00:43.170 --> 00:00:45.410 align:start position:0% how do we achieve adoption theorem well I<00:00:43.440> mean<00:00:43.950> it's<00:00:44.309> gonna<00:00:44.430> come<00:00:44.610> in<00:00:44.730> phases<00:00:45.120> right 00:00:45.410 --> 00:00:45.420 align:start position:0% I mean it's gonna come in phases right 00:00:45.420 --> 00:00:47.299 align:start position:0% I mean it's gonna come in phases right the<00:00:45.989> you<00:00:46.320> know<00:00:46.440> the<00:00:46.739> first<00:00:46.920> thing<00:00:47.070> that 00:00:47.299 --> 00:00:47.309 align:start position:0% the you know the first thing that 00:00:47.309 --> 00:00:49.190 align:start position:0% the you know the first thing that happens<00:00:47.700> is<00:00:47.820> you<00:00:47.940> get<00:00:48.120> small<00:00:48.600> numbers<00:00:48.960> very 00:00:49.190 --> 00:00:49.200 align:start position:0% happens is you get small numbers very 00:00:49.200 --> 00:00:50.930 align:start position:0% happens is you get small numbers very smart<00:00:49.500> people<00:00:49.649> then<00:00:50.460> you<00:00:50.610> get<00:00:50.730> big 00:00:50.930 --> 00:00:50.940 align:start position:0% smart people then you get big 00:00:50.940 --> 00:00:52.850 align:start position:0% smart people then you get big institutions<00:00:51.629> then<00:00:51.930> everybody's<00:00:52.410> using<00:00:52.649> it 00:00:52.850 --> 00:00:52.860 align:start position:0% institutions then everybody's using it 00:00:52.860 --> 00:00:54.260 align:start position:0% institutions then everybody's using it even<00:00:53.100> if<00:00:53.190> they<00:00:53.280> don't<00:00:53.370> know<00:00:53.550> it<00:00:53.699> like<00:00:53.940> you<00:00:54.180> know 00:00:54.260 --> 00:00:54.270 align:start position:0% even if they don't know it like you know 00:00:54.270 --> 00:00:57.020 align:start position:0% even if they don't know it like you know how<00:00:54.420> did<00:00:54.570> SQL<00:00:55.020> adoption<00:00:55.710> you<00:00:56.489> just<00:00:56.670> wound<00:00:56.879> up 00:00:57.020 --> 00:00:57.030 align:start position:0% how did SQL adoption you just wound up 00:00:57.030 --> 00:00:59.180 align:start position:0% how did SQL adoption you just wound up using<00:00:57.270> it<00:00:57.510> to<00:00:57.600> run<00:00:57.719> society<00:00:58.320> and<00:00:58.620> we're<00:00:59.100> all 00:00:59.180 --> 00:00:59.190 align:start position:0% using it to run society and we're all 00:00:59.190 --> 00:01:01.360 align:start position:0% using it to run society and we're all SQL<00:00:59.520> users<00:01:00.059> whether<00:01:00.239> we<00:01:00.420> notice<00:01:00.660> her<00:01:00.750> or<00:01:00.870> not 00:01:01.360 --> 00:01:01.370 align:start position:0% SQL users whether we notice her or not 00:01:01.370 --> 00:01:07.250 align:start position:0% SQL users whether we notice her or not ubiquitous<00:01:02.370> invisible<00:01:03.210> of<00:01:03.329> the<00:01:03.480> present<00:01:06.260> you 00:01:07.250 --> 00:01:07.260 align:start position:0% ubiquitous invisible of the present you 00:01:07.260 --> 00:01:10.730 align:start position:0% ubiquitous invisible of the present you believe<00:01:07.530> it<00:01:07.680> should<00:01:07.920> be<00:01:08.720> partly<00:01:09.740> corporate 00:01:10.730 --> 00:01:10.740 align:start position:0% believe it should be partly corporate 00:01:10.740 --> 00:01:17.539 align:start position:0% believe it should be partly corporate driven<00:01:11.360> totally<00:01:12.360> ground<00:01:13.700> bottom-up<00:01:16.549> anything 00:01:17.539 --> 00:01:17.549 align:start position:0% driven totally ground bottom-up anything 00:01:17.549 --> 00:01:19.609 align:start position:0% driven totally ground bottom-up anything but<00:01:17.759> month<00:01:17.970> achieve<00:01:18.360> scale<00:01:18.600> will<00:01:19.110> wind<00:01:19.320> up<00:01:19.439> as 00:01:19.609 --> 00:01:19.619 align:start position:0% but month achieve scale will wind up as 00:01:19.619 --> 00:01:21.289 align:start position:0% but month achieve scale will wind up as being<00:01:19.950> largely<00:01:20.400> indistinguishable<00:01:20.909> from 00:01:21.289 --> 00:01:21.299 align:start position:0% being largely indistinguishable from 00:01:21.299 --> 00:01:23.990 align:start position:0% being largely indistinguishable from corporation<00:01:22.130> now<00:01:23.130> if<00:01:23.250> you<00:01:23.340> think<00:01:23.490> about<00:01:23.549> linux 00:01:23.990 --> 00:01:24.000 align:start position:0% corporation now if you think about linux 00:01:24.000 --> 00:01:26.390 align:start position:0% corporation now if you think about linux foundation<00:01:24.630> to<00:01:25.409> all<00:01:25.500> intents<00:01:25.650> and<00:01:25.920> purposes 00:01:26.390 --> 00:01:26.400 align:start position:0% foundation to all intents and purposes 00:01:26.400 --> 00:01:28.130 align:start position:0% foundation to all intents and purposes it's<00:01:26.580> a<00:01:26.670> corporate<00:01:26.880> institution<00:01:27.689> even<00:01:27.869> the 00:01:28.130 --> 00:01:28.140 align:start position:0% it's a corporate institution even the 00:01:28.140 --> 00:01:30.620 align:start position:0% it's a corporate institution even the linux<00:01:28.439> is<00:01:28.560> very<00:01:28.770> decentralized<00:01:29.070> effort<00:01:29.880> the 00:01:30.620 --> 00:01:30.630 align:start position:0% linux is very decentralized effort the 00:01:30.630 --> 00:01:33.080 align:start position:0% linux is very decentralized effort the interfaces<00:01:31.470> to<00:01:31.500> society<00:01:32.070> like<00:01:32.159> the<00:01:32.280> api's<00:01:32.759> are 00:01:33.080 --> 00:01:33.090 align:start position:0% interfaces to society like the api's are 00:01:33.090 --> 00:01:35.450 align:start position:0% interfaces to society like the api's are all<00:01:33.180> corpora<00:01:33.630> so<00:01:34.470> until<00:01:34.680> we've<00:01:34.860> gotten<00:01:35.159> so 00:01:35.450 --> 00:01:35.460 align:start position:0% all corpora so until we've gotten so 00:01:35.460 --> 00:01:37.280 align:start position:0% all corpora so until we've gotten so much<00:01:35.579> decentralization<00:01:36.390> that<00:01:36.689> the<00:01:36.780> basic<00:01:37.140> API 00:01:37.280 --> 00:01:37.290 align:start position:0% much decentralization that the basic API 00:01:37.290 --> 00:01:39.920 align:start position:0% much decentralization that the basic API is<00:01:37.590> that<00:01:37.920> drive<00:01:38.159> society<00:01:38.729> also<00:01:38.970> decentralized 00:01:39.920 --> 00:01:39.930 align:start position:0% is that drive society also decentralized 00:01:39.930 --> 00:01:41.690 align:start position:0% is that drive society also decentralized I<00:01:40.200> think<00:01:40.920> you're<00:01:41.009> going<00:01:41.100> to<00:01:41.159> wind<00:01:41.340> up<00:01:41.490> with 00:01:41.690 --> 00:01:41.700 align:start position:0% I think you're going to wind up with 00:01:41.700 --> 00:01:43.700 align:start position:0% I think you're going to wind up with even<00:01:42.299> decentralized<00:01:43.079> networks<00:01:43.409> having 00:01:43.700 --> 00:01:43.710 align:start position:0% even decentralized networks having 00:01:43.710 --> 00:01:45.530 align:start position:0% even decentralized networks having corporate<00:01:44.070> looking<00:01:44.310> api's<00:01:44.700> that<00:01:44.939> they<00:01:45.119> kind 00:01:45.530 --> 00:01:45.540 align:start position:0% corporate looking api's that they kind 00:01:45.540 --> 00:01:49.609 align:start position:0% corporate looking api's that they kind of<00:01:45.570> terminus<00:01:46.020> points<00:01:48.170> what<00:01:49.170> all<00:01:49.380> you<00:01:49.500> guys 00:01:49.609 --> 00:01:49.619 align:start position:0% of terminus points what all you guys 00:01:49.619 --> 00:01:54.920 align:start position:0% of terminus points what all you guys think<00:01:49.920> about<00:01:50.360> the<00:01:51.360> branding<00:01:51.899> of<00:01:52.020> etherium<00:01:53.930> the 00:01:54.920 --> 00:01:54.930 align:start position:0% think about the branding of etherium the 00:01:54.930 --> 00:01:57.139 align:start position:0% think about the branding of etherium the initial<00:01:55.350> branding<00:01:55.829> which<00:01:56.100> I<00:01:56.310> think<00:01:56.579> was<00:01:56.759> more 00:01:57.139 --> 00:01:57.149 align:start position:0% initial branding which I think was more 00:01:57.149 --> 00:02:00.560 align:start position:0% initial branding which I think was more developer<00:01:57.630> focused<00:01:58.700> does<00:01:59.700> it<00:01:59.909> need<00:02:00.060> to<00:02:00.119> change 00:02:00.560 --> 00:02:00.570 align:start position:0% developer focused does it need to change 00:02:00.570 --> 00:02:03.590 align:start position:0% developer focused does it need to change does<00:02:00.960> it<00:02:01.110> need<00:02:01.229> to<00:02:01.340> adapt<00:02:02.340> to<00:02:02.670> being<00:02:02.700> more<00:02:03.210> end 00:02:03.590 --> 00:02:03.600 align:start position:0% does it need to adapt to being more end 00:02:03.600 --> 00:02:06.170 align:start position:0% does it need to adapt to being more end user<00:02:04.110> focused<00:02:04.680> do<00:02:05.549> we<00:02:05.670> need<00:02:05.820> to<00:02:05.880> brand 00:02:06.170 --> 00:02:06.180 align:start position:0% user focused do we need to brand 00:02:06.180 --> 00:02:08.589 align:start position:0% user focused do we need to brand etherium<00:02:06.630> at<00:02:06.750> all<00:02:06.869> or<00:02:07.079> should<00:02:07.590> it<00:02:07.649> just<00:02:07.710> fade 00:02:08.589 --> 00:02:08.599 align:start position:0% etherium at all or should it just fade 00:02:08.599 --> 00:02:10.219 align:start position:0% etherium at all or should it just fade become<00:02:09.599> the 00:02:10.219 --> 00:02:10.229 align:start position:0% become the 00:02:10.229 --> 00:02:16.850 align:start position:0% become the internet<00:02:10.800> like<00:02:10.950> infrastructure<00:02:15.709> this<00:02:16.709> is<00:02:16.769> the 00:02:16.850 --> 00:02:16.860 align:start position:0% internet like infrastructure this is the 00:02:16.860 --> 00:02:21.740 align:start position:0% internet like infrastructure this is the Internet<00:02:17.220> around<00:02:19.790> they<00:02:20.790> have<00:02:21.090> in<00:02:21.420> about 00:02:21.740 --> 00:02:21.750 align:start position:0% Internet around they have in about 00:02:21.750 --> 00:02:26.089 align:start position:0% Internet around they have in about nineteen<00:02:22.470> ninety-five<00:02:23.629> but<00:02:24.629> a<00:02:25.080> theorem<00:02:25.860> does 00:02:26.089 --> 00:02:26.099 align:start position:0% nineteen ninety-five but a theorem does 00:02:26.099 --> 00:02:29.150 align:start position:0% nineteen ninety-five but a theorem does have<00:02:26.310> a<00:02:26.340> brand<00:02:26.720> is<00:02:27.720> a<00:02:27.840> necessary<00:02:28.170> do<00:02:28.950> we<00:02:29.040> need 00:02:29.150 --> 00:02:29.160 align:start position:0% have a brand is a necessary do we need 00:02:29.160 --> 00:02:33.020 align:start position:0% have a brand is a necessary do we need to<00:02:29.220> be<00:02:29.430> selling<00:02:29.910> etherium<00:02:31.549> what<00:02:32.549> is<00:02:32.670> missing 00:02:33.020 --> 00:02:33.030 align:start position:0% to be selling etherium what is missing 00:02:33.030 --> 00:02:34.910 align:start position:0% to be selling etherium what is missing anything<00:02:33.360> is<00:02:33.629> missing<00:02:33.810> from<00:02:34.230> the<00:02:34.410> branding 00:02:34.910 --> 00:02:34.920 align:start position:0% anything is missing from the branding 00:02:34.920 --> 00:02:39.199 align:start position:0% anything is missing from the branding that<00:02:35.459> you're<00:02:35.640> thinking<00:02:35.790> about<00:02:37.549> but<00:02:38.549> it's<00:02:38.940> been 00:02:39.199 --> 00:02:39.209 align:start position:0% that you're thinking about but it's been 00:02:39.209 --> 00:02:42.020 align:start position:0% that you're thinking about but it's been a<00:02:39.239> topic<00:02:39.540> of<00:02:39.780> discussion<00:02:39.959> recently<00:02:40.940> there<00:02:41.940> are 00:02:42.020 --> 00:02:42.030 align:start position:0% a topic of discussion recently there are 00:02:42.030 --> 00:02:46.430 align:start position:0% a topic of discussion recently there are people<00:02:42.360> who<00:02:43.400> feel<00:02:44.400> like<00:02:44.700> we<00:02:45.569> really<00:02:45.750> need<00:02:46.110> to 00:02:46.430 --> 00:02:46.440 align:start position:0% people who feel like we really need to 00:02:46.440 --> 00:02:50.800 align:start position:0% people who feel like we really need to put<00:02:47.099> it<00:02:47.220> out<00:02:47.629> into<00:02:48.709> public<00:02:49.709> consciousness 00:02:50.800 --> 00:02:50.810 align:start position:0% put it out into public consciousness 00:02:50.810 --> 00:02:54.680 align:start position:0% put it out into public consciousness perhaps<00:02:51.810> a<00:02:52.319> world<00:02:52.769> computer<00:02:53.310> maybe<00:02:53.790> a<00:02:54.180> little 00:02:54.680 --> 00:02:54.690 align:start position:0% perhaps a world computer maybe a little 00:02:54.690 --> 00:02:57.589 align:start position:0% perhaps a world computer maybe a little globe<00:02:55.109> icon<00:02:55.349> was<00:02:55.980> too<00:02:56.430> little<00:02:56.700> etherium<00:02:57.420> eyes 00:02:57.589 --> 00:02:57.599 align:start position:0% globe icon was too little etherium eyes 00:02:57.599 --> 00:03:00.289 align:start position:0% globe icon was too little etherium eyes and<00:02:58.170> and<00:02:58.440> some<00:02:58.950> keyboards<00:02:59.459> hanging<00:02:59.849> off<00:03:00.000> it<00:03:00.269> a 00:03:00.289 --> 00:03:00.299 align:start position:0% and and some keyboards hanging off it a 00:03:00.299 --> 00:03:02.150 align:start position:0% and and some keyboards hanging off it a little<00:03:00.510> little<00:03:00.870> beard<00:03:01.290> of<00:03:01.470> keyboards<00:03:01.980> and 00:03:02.150 --> 00:03:02.160 align:start position:0% little little beard of keyboards and 00:03:02.160 --> 00:03:06.199 align:start position:0% little little beard of keyboards and mouses<00:03:02.720> myself<00:03:04.519> at<00:03:05.519> Christmas<00:03:05.640> it<00:03:06.000> gets<00:03:06.150> a 00:03:06.199 --> 00:03:06.209 align:start position:0% mouses myself at Christmas it gets a 00:03:06.209 --> 00:03:09.550 align:start position:0% mouses myself at Christmas it gets a little<00:03:06.329> kind<00:03:06.540> of<00:03:06.599> Santa<00:03:07.109> ha<00:03:07.410> and<00:03:07.709> yeah 00:03:09.550 --> 00:03:09.560 align:start position:0% little kind of Santa ha and yeah 00:03:09.560 --> 00:03:13.670 align:start position:0% little kind of Santa ha and yeah trusting<00:03:10.560> computer<00:03:11.340> no<00:03:12.120> I<00:03:12.359> mean<00:03:12.959> there's<00:03:13.470> good 00:03:13.670 --> 00:03:13.680 align:start position:0% trusting computer no I mean there's good 00:03:13.680 --> 00:03:16.129 align:start position:0% trusting computer no I mean there's good case<00:03:14.010> for<00:03:14.040> making<00:03:14.639> that<00:03:14.669> the<00:03:15.060> eclectic<00:03:15.959> at 00:03:16.129 --> 00:03:16.139 align:start position:0% case for making that the eclectic at 00:03:16.139 --> 00:03:18.470 align:start position:0% case for making that the eclectic at explainer<00:03:16.590> brown<00:03:16.980> right<00:03:17.760> but<00:03:17.970> every<00:03:18.000> time<00:03:18.329> you 00:03:18.470 --> 00:03:18.480 align:start position:0% explainer brown right but every time you 00:03:18.480 --> 00:03:19.940 align:start position:0% explainer brown right but every time you see<00:03:18.690> something<00:03:18.900> that<00:03:19.049> explains<00:03:19.410> your<00:03:19.560> theorem 00:03:19.940 --> 00:03:19.950 align:start position:0% see something that explains your theorem 00:03:19.950 --> 00:03:21.289 align:start position:0% see something that explains your theorem the<00:03:20.069> world<00:03:20.250> computer<00:03:20.669> comes<00:03:20.849> on<00:03:21.030> it<00:03:21.150> does<00:03:21.269> a 00:03:21.289 --> 00:03:21.299 align:start position:0% the world computer comes on it does a 00:03:21.299 --> 00:03:23.270 align:start position:0% the world computer comes on it does a little<00:03:21.510> bit<00:03:21.690> in<00:03:21.780> the<00:03:21.840> talking<00:03:22.230> something<00:03:23.160> like 00:03:23.270 --> 00:03:23.280 align:start position:0% little bit in the talking something like 00:03:23.280 --> 00:03:26.210 align:start position:0% little bit in the talking something like that<00:03:23.400> but<00:03:23.609> in<00:03:23.910> the<00:03:24.450> long<00:03:24.630> run<00:03:24.660> I<00:03:25.260> mean<00:03:26.040> think 00:03:26.210 --> 00:03:26.220 align:start position:0% that but in the long run I mean think 00:03:26.220 --> 00:03:29.330 align:start position:0% that but in the long run I mean think like<00:03:26.370> is<00:03:26.519> HTML<00:03:27.120> a<00:03:27.299> brand<00:03:27.829> it<00:03:28.829> used<00:03:29.069> to<00:03:29.160> be<00:03:29.310> a 00:03:29.330 --> 00:03:29.340 align:start position:0% like is HTML a brand it used to be a 00:03:29.340 --> 00:03:34.099 align:start position:0% like is HTML a brand it used to be a brown<00:03:29.549> to<00:03:29.700> the<00:03:29.790> 1990s<00:03:30.150> 00<00:03:30.810> HTML<00:03:31.049> /<00:03:32.690> right<00:03:33.690> but 00:03:34.099 --> 00:03:34.109 align:start position:0% brown to the 1990s 00 HTML / right but 00:03:34.109 --> 00:03:37.970 align:start position:0% brown to the 1990s 00 HTML / right but in<00:03:35.690> the<00:03:36.690> brand<00:03:36.989> is<00:03:37.139> going<00:03:37.319> to<00:03:37.380> come<00:03:37.650> from<00:03:37.680> the 00:03:37.970 --> 00:03:37.980 align:start position:0% in the brand is going to come from the 00:03:37.980 --> 00:03:42.110 align:start position:0% in the brand is going to come from the community<00:03:38.519> the<00:03:39.030> more<00:03:39.769> users<00:03:40.769> there<00:03:41.310> are<00:03:41.489> the 00:03:42.110 --> 00:03:42.120 align:start position:0% community the more users there are the 00:03:42.120 --> 00:03:44.539 align:start position:0% community the more users there are the more<00:03:42.299> developers<00:03:42.840> there<00:03:43.049> are<00:03:43.250> then<00:03:44.250> the 00:03:44.539 --> 00:03:44.549 align:start position:0% more developers there are then the 00:03:44.549 --> 00:03:46.309 align:start position:0% more developers there are then the bigger<00:03:44.730> the<00:03:44.910> community<00:03:45.329> is<00:03:45.480> and<00:03:45.720> that's<00:03:46.139> how 00:03:46.309 --> 00:03:46.319 align:start position:0% bigger the community is and that's how 00:03:46.319 --> 00:03:48.740 align:start position:0% bigger the community is and that's how the<00:03:46.380> brand<00:03:46.799> is<00:03:46.950> going<00:03:47.130> to<00:03:47.220> splash<00:03:47.579> on<00:03:48.000> the 00:03:48.740 --> 00:03:48.750 align:start position:0% the brand is going to splash on the 00:03:48.750 --> 00:03:52.789 align:start position:0% the brand is going to splash on the market<00:03:49.139> so<00:03:50.130> my<00:03:50.849> focus<00:03:51.090> is<00:03:51.389> to<00:03:51.540> find<00:03:51.780> out<00:03:51.930> do<00:03:52.530> we 00:03:52.789 --> 00:03:52.799 align:start position:0% market so my focus is to find out do we 00:03:52.799 --> 00:03:55.009 align:start position:0% market so my focus is to find out do we know<00:03:52.889> how<00:03:52.980> many<00:03:53.040> developers<00:03:53.700> are<00:03:53.910> there<00:03:54.090> that 00:03:55.009 --> 00:03:55.019 align:start position:0% know how many developers are there that 00:03:55.019 --> 00:03:57.440 align:start position:0% know how many developers are there that are<00:03:55.310> knowledgeable<00:03:56.310> on<00:03:56.519> athyrium 00:03:57.440 --> 00:03:57.450 align:start position:0% are knowledgeable on athyrium 00:03:57.450 --> 00:04:00.800 align:start position:0% are knowledgeable on athyrium technologies<00:03:58.319> one<00:03:59.250> way<00:03:59.400> or<00:03:59.519> the<00:03:59.549> other<00:03:59.669> are<00:04:00.660> we 00:04:00.800 --> 00:04:00.810 align:start position:0% technologies one way or the other are we 00:04:00.810 --> 00:04:02.960 align:start position:0% technologies one way or the other are we talking<00:04:01.200> a<00:04:01.290> few<00:04:01.410> thousand<00:04:01.950> now<00:04:02.129> you<00:04:02.190> would<00:04:02.370> not 00:04:02.960 --> 00:04:02.970 align:start position:0% talking a few thousand now you would not 00:04:02.970 --> 00:04:05.089 align:start position:0% talking a few thousand now you would not be<00:04:03.150> more<00:04:03.299> than<00:04:03.450> five<00:04:03.629> hundred<00:04:03.660> thousand<00:04:04.560> two 00:04:05.089 --> 00:04:05.099 align:start position:0% be more than five hundred thousand two 00:04:05.099 --> 00:04:07.759 align:start position:0% be more than five hundred thousand two thousand<00:04:05.489> but<00:04:06.209> that's<00:04:06.660> not<00:04:06.930> that's<00:04:07.230> a<00:04:07.470> small 00:04:07.759 --> 00:04:07.769 align:start position:0% thousand but that's not that's a small 00:04:07.769 --> 00:04:10.610 align:start position:0% thousand but that's not that's a small number<00:04:08.599> how<00:04:09.599> many<00:04:09.629> should<00:04:09.989> there<00:04:10.169> be<00:04:10.290> I<00:04:10.470> mean 00:04:10.610 --> 00:04:10.620 align:start position:0% number how many should there be I mean 00:04:10.620 --> 00:04:13.309 align:start position:0% number how many should there be I mean that<00:04:10.739> is<00:04:10.889> I<00:04:11.010> think<00:04:11.040> of<00:04:11.340> focus<00:04:11.730> if<00:04:12.480> we<00:04:12.930> have<00:04:13.079> more 00:04:13.309 --> 00:04:13.319 align:start position:0% that is I think of focus if we have more 00:04:13.319 --> 00:04:16.009 align:start position:0% that is I think of focus if we have more developers<00:04:14.000> both<00:04:15.000> in<00:04:15.329> corporate 00:04:16.009 --> 00:04:16.019 align:start position:0% developers both in corporate 00:04:16.019 --> 00:04:19.940 align:start position:0% developers both in corporate environments<00:04:16.709> in<00:04:17.250> startups<00:04:18.030> in<00:04:18.959> all<00:04:19.349> kinds<00:04:19.859> of 00:04:19.940 --> 00:04:19.950 align:start position:0% environments in startups in all kinds of 00:04:19.950 --> 00:04:21.160 align:start position:0% environments in startups in all kinds of different 00:04:21.160 --> 00:04:21.170 align:start position:0% different 00:04:21.170 --> 00:04:23.590 align:start position:0% different of<00:04:21.380> organizations<00:04:22.040> I<00:04:22.160> think<00:04:22.340> that's<00:04:23.060> what's 00:04:23.590 --> 00:04:23.600 align:start position:0% of organizations I think that's what's 00:04:23.600 --> 00:04:27.550 align:start position:0% of organizations I think that's what's going<00:04:23.750> to<00:04:23.960> drive<00:04:24.080> adoption<00:04:25.240> well<00:04:26.240> I<00:04:26.450> mean<00:04:27.140> at 00:04:27.550 --> 00:04:27.560 align:start position:0% going to drive adoption well I mean at 00:04:27.560 --> 00:04:29.200 align:start position:0% going to drive adoption well I mean at that<00:04:27.770> level<00:04:28.010> I<00:04:28.340> think<00:04:28.370> once<00:04:28.790> you<00:04:29.000> see 00:04:29.200 --> 00:04:29.210 align:start position:0% that level I think once you see 00:04:29.210 --> 00:04:30.790 align:start position:0% that level I think once you see large-scale<00:04:29.990> adoption<00:04:30.410> by<00:04:30.530> things<00:04:30.740> like 00:04:30.790 --> 00:04:30.800 align:start position:0% large-scale adoption by things like 00:04:30.800 --> 00:04:33.040 align:start position:0% large-scale adoption by things like banks<00:04:31.340> which<00:04:31.550> i<00:04:31.640> think<00:04:31.700> is<00:04:31.850> happening<00:04:32.050> frankly 00:04:33.040 --> 00:04:33.050 align:start position:0% banks which i think is happening frankly 00:04:33.050 --> 00:04:34.870 align:start position:0% banks which i think is happening frankly faster<00:04:33.470> than<00:04:33.590> any<00:04:33.710> of<00:04:33.800> you<00:04:33.860> Julie<00:04:34.100> oriented<00:04:34.670> to 00:04:34.870 --> 00:04:34.880 align:start position:0% faster than any of you Julie oriented to 00:04:34.880 --> 00:04:38.470 align:start position:0% faster than any of you Julie oriented to i<00:04:35.270> think<00:04:35.900> the<00:04:36.050> the<00:04:36.080> sudden<00:04:37.300> realization<00:04:38.300> from 00:04:38.470 --> 00:04:38.480 align:start position:0% i think the the sudden realization from 00:04:38.480 --> 00:04:39.910 align:start position:0% i think the the sudden realization from developers<00:04:38.960> that<00:04:38.990> if<00:04:39.290> you<00:04:39.470> want<00:04:39.650> to<00:04:39.710> make<00:04:39.830> an 00:04:39.910 --> 00:04:39.920 align:start position:0% developers that if you want to make an 00:04:39.920 --> 00:04:41.410 align:start position:0% developers that if you want to make an awful<00:04:40.190> lot<00:04:40.490> of<00:04:40.550> money<00:04:40.700> working<00:04:40.970> for<00:04:41.210> bounce 00:04:41.410 --> 00:04:41.420 align:start position:0% awful lot of money working for bounce 00:04:41.420 --> 00:04:48.760 align:start position:0% awful lot of money working for bounce you<00:04:41.570> need<00:04:41.690> to<00:04:41.750> get<00:04:41.840> good<00:04:41.990> at<00:04:42.050> bok<00:04:42.260> choy<00:04:47.770> you're 00:04:48.760 --> 00:04:48.770 align:start position:0% you need to get good at bok choy you're 00:04:48.770 --> 00:04:53.430 align:start position:0% you need to get good at bok choy you're an<00:04:48.860> onus<00:04:49.190> on<00:04:49.370> the<00:04:50.200> who<00:04:51.200> is<00:04:51.410> going<00:04:51.560> to<00:04:51.650> drive 00:04:53.430 --> 00:04:53.440 align:start position:0% an onus on the who is going to drive 00:04:53.440 --> 00:04:57.190 align:start position:0% an onus on the who is going to drive getting<00:04:54.440> more<00:04:54.620> developers<00:04:55.100> out<00:04:55.220> there<00:04:56.200> so 00:04:57.190 --> 00:04:57.200 align:start position:0% getting more developers out there so 00:04:57.200 --> 00:05:00.430 align:start position:0% getting more developers out there so early<00:04:57.440> on<00:04:58.190> we<00:04:58.400> had<00:04:58.640> an<00:04:59.090> exercise<00:04:59.630> that<00:04:59.660> you<00:04:59.960> led 00:05:00.430 --> 00:05:00.440 align:start position:0% early on we had an exercise that you led 00:05:00.440 --> 00:05:02.230 align:start position:0% early on we had an exercise that you led in<00:05:00.680> Toronto<00:05:01.250> where<00:05:01.550> we<00:05:01.730> were<00:05:01.850> trying<00:05:02.150> to 00:05:02.230 --> 00:05:02.240 align:start position:0% in Toronto where we were trying to 00:05:02.240 --> 00:05:05.080 align:start position:0% in Toronto where we were trying to figure<00:05:02.390> out<00:05:02.660> branding<00:05:03.230> for<00:05:03.470> a<00:05:03.530> theorem<00:05:03.940> and<00:05:04.940> I 00:05:05.080 --> 00:05:05.090 align:start position:0% figure out branding for a theorem and I 00:05:05.090 --> 00:05:07.150 align:start position:0% figure out branding for a theorem and I think<00:05:05.360> one<00:05:05.570> of<00:05:05.600> our<00:05:05.750> conclusions<00:05:06.380> was<00:05:06.590> that<00:05:06.950> we 00:05:07.150 --> 00:05:07.160 align:start position:0% think one of our conclusions was that we 00:05:07.160 --> 00:05:11.290 align:start position:0% think one of our conclusions was that we should<00:05:07.840> target<00:05:08.840> messages<00:05:09.470> to<00:05:09.620> developers<00:05:10.300> not 00:05:11.290 --> 00:05:11.300 align:start position:0% should target messages to developers not 00:05:11.300 --> 00:05:13.090 align:start position:0% should target messages to developers not really<00:05:11.570> the<00:05:11.720> end<00:05:11.810> users<00:05:12.260> but<00:05:12.560> let<00:05:12.860> those 00:05:13.090 --> 00:05:13.100 align:start position:0% really the end users but let those 00:05:13.100 --> 00:05:16.780 align:start position:0% really the end users but let those developers<00:05:13.960> build<00:05:14.960> their<00:05:15.310> business<00:05:16.310> models 00:05:16.780 --> 00:05:16.790 align:start position:0% developers build their business models 00:05:16.790 --> 00:05:18.760 align:start position:0% developers build their business models and<00:05:17.120> find<00:05:17.630> their<00:05:17.990> niches<00:05:18.320> and<00:05:18.500> their 00:05:18.760 --> 00:05:18.770 align:start position:0% and find their niches and their 00:05:18.770 --> 00:05:21.040 align:start position:0% and find their niches and their customers<00:05:19.310> and<00:05:19.760> let<00:05:20.030> them<00:05:20.270> market<00:05:20.690> to<00:05:20.810> the<00:05:20.930> end 00:05:21.040 --> 00:05:21.050 align:start position:0% customers and let them market to the end 00:05:21.050 --> 00:05:23.860 align:start position:0% customers and let them market to the end user<00:05:21.230> so<00:05:21.740> not<00:05:22.310> really<00:05:22.490> mark<00:05:22.850> not<00:05:23.600> really 00:05:23.860 --> 00:05:23.870 align:start position:0% user so not really mark not really 00:05:23.870 --> 00:05:27.340 align:start position:0% user so not really mark not really ethereal<00:05:24.770> but<00:05:25.100> you<00:05:25.940> know<00:05:26.140> netflix<00:05:27.140> on<00:05:27.320> a 00:05:27.340 --> 00:05:27.350 align:start position:0% ethereal but you know netflix on a 00:05:27.350 --> 00:05:30.250 align:start position:0% ethereal but you know netflix on a theorem<00:05:27.740> or<00:05:28.720> prediction<00:05:29.720> markets<00:05:30.110> on 00:05:30.250 --> 00:05:30.260 align:start position:0% theorem or prediction markets on 00:05:30.260 --> 00:05:32.920 align:start position:0% theorem or prediction markets on etherium<00:05:30.680> something<00:05:31.160> like<00:05:31.310> that<00:05:31.930> that's 00:05:32.920 --> 00:05:32.930 align:start position:0% etherium something like that that's 00:05:32.930 --> 00:05:37.180 align:start position:0% etherium something like that that's certainly<00:05:33.500> one<00:05:33.770> approach<00:05:34.640> we<00:05:35.150> could<00:05:36.130> try<00:05:37.130> to 00:05:37.180 --> 00:05:37.190 align:start position:0% certainly one approach we could try to 00:05:37.190 --> 00:05:39.280 align:start position:0% certainly one approach we could try to emphasize<00:05:37.400> that<00:05:37.820> it<00:05:38.360> is<00:05:38.540> built<00:05:38.990> on<00:05:39.170> the 00:05:39.280 --> 00:05:39.290 align:start position:0% emphasize that it is built on the 00:05:39.290 --> 00:05:42.850 align:start position:0% emphasize that it is built on the theorem<00:05:39.590> sort<00:05:39.860> of<00:05:39.920> an<00:05:40.040> theorem<00:05:40.760> inside<00:05:41.860> type 00:05:42.850 --> 00:05:42.860 align:start position:0% theorem sort of an theorem inside type 00:05:42.860 --> 00:05:48.970 align:start position:0% theorem sort of an theorem inside type branding<00:05:44.020> campaign<00:05:45.020> I<00:05:47.200> don't<00:05:48.200> know<00:05:48.290> I<00:05:48.500> don't 00:05:48.970 --> 00:05:48.980 align:start position:0% branding campaign I don't know I don't 00:05:48.980 --> 00:05:51.900 align:start position:0% branding campaign I don't know I don't know<00:05:49.130> if<00:05:49.280> I<00:05:49.610> guess<00:05:50.570> at<00:05:50.720> this<00:05:50.870> early<00:05:51.140> stage 00:05:51.900 --> 00:05:51.910 align:start position:0% know if I guess at this early stage 00:05:51.910 --> 00:05:57.040 align:start position:0% know if I guess at this early stage because<00:05:53.980> it's<00:05:54.980> really<00:05:55.430> very<00:05:56.000> early<00:05:56.450> in<00:05:56.660> this 00:05:57.040 --> 00:05:57.050 align:start position:0% because it's really very early in this 00:05:57.050 --> 00:05:59.950 align:start position:0% because it's really very early in this niche<00:05:57.940> we<00:05:58.940> kind<00:05:59.210> of<00:05:59.240> have<00:05:59.390> to<00:05:59.540> do<00:05:59.660> everything 00:05:59.950 --> 00:05:59.960 align:start position:0% niche we kind of have to do everything 00:05:59.960 --> 00:06:02.470 align:start position:0% niche we kind of have to do everything so<00:06:00.650> we<00:06:00.830> probably<00:06:01.130> should<00:06:01.550> be<00:06:01.760> branding<00:06:02.270> a 00:06:02.470 --> 00:06:02.480 align:start position:0% so we probably should be branding a 00:06:02.480 --> 00:06:05.430 align:start position:0% so we probably should be branding a theorem<00:06:02.840> itself<00:06:03.260> and<00:06:03.530> helping<00:06:04.300> developers 00:06:05.430 --> 00:06:05.440 align:start position:0% theorem itself and helping developers 00:06:05.440 --> 00:06:10.300 align:start position:0% theorem itself and helping developers brand<00:06:06.440> their<00:06:06.860> projects<00:06:07.550> as<00:06:07.730> well<00:06:08.620> so<00:06:09.620> when<00:06:10.070> we 00:06:10.300 --> 00:06:10.310 align:start position:0% brand their projects as well so when we 00:06:10.310 --> 00:06:12.880 align:start position:0% brand their projects as well so when we round<00:06:10.790> I<00:06:11.390> think<00:06:12.080> it's<00:06:12.320> important<00:06:12.830> to 00:06:12.880 --> 00:06:12.890 align:start position:0% round I think it's important to 00:06:12.890 --> 00:06:14.350 align:start position:0% round I think it's important to understand<00:06:13.430> whether<00:06:13.610> we're<00:06:13.850> branding 00:06:14.350 --> 00:06:14.360 align:start position:0% understand whether we're branding 00:06:14.360 --> 00:06:16.780 align:start position:0% understand whether we're branding against<00:06:15.170> what<00:06:15.530> we're<00:06:15.680> branding<00:06:16.070> against<00:06:16.550> so 00:06:16.780 --> 00:06:16.790 align:start position:0% against what we're branding against so 00:06:16.790 --> 00:06:18.400 align:start position:0% against what we're branding against so branding<00:06:17.270> allows<00:06:17.660> us<00:06:17.900> to<00:06:18.050> differentiate 00:06:18.400 --> 00:06:18.410 align:start position:0% branding allows us to differentiate 00:06:18.410 --> 00:06:21.990 align:start position:0% branding allows us to differentiate ourselves<00:06:19.210> so<00:06:20.210> are<00:06:20.780> we<00:06:20.900> branding<00:06:21.410> against 00:06:21.990 --> 00:06:22.000 align:start position:0% ourselves so are we branding against 00:06:22.000 --> 00:06:24.460 align:start position:0% ourselves so are we branding against like<00:06:23.000> other<00:06:23.360> things<00:06:23.810> in<00:06:24.050> this<00:06:24.170> space 00:06:24.460 --> 00:06:24.470 align:start position:0% like other things in this space 00:06:24.470 --> 00:06:26.830 align:start position:0% like other things in this space re-branding<00:06:25.220> ourselves<00:06:25.940> as<00:06:26.090> you<00:06:26.750> know 00:06:26.830 --> 00:06:26.840 align:start position:0% re-branding ourselves as you know 00:06:26.840 --> 00:06:28.420 align:start position:0% re-branding ourselves as you know against<00:06:27.080> sort<00:06:27.290> of<00:06:27.350> the<00:06:27.440> internet<00:06:27.920> which<00:06:28.310> I 00:06:28.420 --> 00:06:28.430 align:start position:0% against sort of the internet which I 00:06:28.430 --> 00:06:31.510 align:start position:0% against sort of the internet which I guess<00:06:28.610> vinay<00:06:28.970> you<00:06:29.030> once<00:06:29.300> said<00:06:30.070> coke<00:06:31.070> doesn't 00:06:31.510 --> 00:06:31.520 align:start position:0% guess vinay you once said coke doesn't 00:06:31.520 --> 00:06:33.280 align:start position:0% guess vinay you once said coke doesn't doesn't<00:06:31.790> actually<00:06:32.030> compete<00:06:32.630> against<00:06:32.930> Pepsi 00:06:33.280 --> 00:06:33.290 align:start position:0% doesn't actually compete against Pepsi 00:06:33.290 --> 00:06:38.140 align:start position:0% doesn't actually compete against Pepsi it<00:06:33.380> competes<00:06:33.650> against<00:06:33.860> water<00:06:36.340> and<00:06:37.340> our<00:06:37.460> water 00:06:38.140 --> 00:06:38.150 align:start position:0% it competes against water and our water 00:06:38.150 --> 00:06:40.900 align:start position:0% it competes against water and our water is<00:06:38.450> just<00:06:38.750> the<00:06:39.560> top<00:06:39.830> down<00:06:40.070> command<00:06:40.580> and<00:06:40.760> control 00:06:40.900 --> 00:06:40.910 align:start position:0% is just the top down command and control 00:06:40.910 --> 00:06:44.320 align:start position:0% is just the top down command and control the<00:06:41.270> world<00:06:41.560> probably<00:06:42.560> and<00:06:43.370> our<00:06:43.790> Pepsi<00:06:44.030> is 00:06:44.320 --> 00:06:44.330 align:start position:0% the world probably and our Pepsi is 00:06:44.330 --> 00:06:46.660 align:start position:0% the world probably and our Pepsi is Bitcoin<00:06:44.840> I<00:06:45.110> would<00:06:45.290> guess<00:06:45.470> so<00:06:46.040> therefore<00:06:46.580> at<00:06:46.640> a 00:06:46.660 --> 00:06:46.670 align:start position:0% Bitcoin I would guess so therefore at a 00:06:46.670 --> 00:06:49.420 align:start position:0% Bitcoin I would guess so therefore at a Bitcoin<00:06:47.120> conference<00:06:47.390> that<00:06:48.110> we<00:06:48.650> tailor<00:06:49.250> the 00:06:49.420 --> 00:06:49.430 align:start position:0% Bitcoin conference that we tailor the 00:06:49.430 --> 00:06:52.900 align:start position:0% Bitcoin conference that we tailor the message<00:06:49.580> and<00:06:50.560> for<00:06:51.560> the<00:06:51.650> rest<00:06:51.800> of<00:06:51.920> the<00:06:52.010> time<00:06:52.250> I 00:06:52.900 --> 00:06:52.910 align:start position:0% message and for the rest of the time I 00:06:52.910 --> 00:06:55.030 align:start position:0% message and for the rest of the time I think<00:06:53.570> your<00:06:53.750> inclination<00:06:54.050> has<00:06:54.650> always<00:06:54.890> been 00:06:55.030 --> 00:06:55.040 align:start position:0% think your inclination has always been 00:06:55.040 --> 00:06:57.420 align:start position:0% think your inclination has always been to<00:06:55.220> not<00:06:56.090> even<00:06:56.360> think<00:06:56.390> about<00:06:56.690> Bitcoin 00:06:57.420 --> 00:06:57.430 align:start position:0% to not even think about Bitcoin 00:06:57.430 --> 00:07:01.270 align:start position:0% to not even think about Bitcoin irrelevant<00:06:58.430> I<00:06:59.230> think<00:07:00.230> that's<00:07:00.380> becoming 00:07:01.270 --> 00:07:01.280 align:start position:0% irrelevant I think that's becoming 00:07:01.280 --> 00:07:04.840 align:start position:0% irrelevant I think that's becoming torrent<00:07:01.760> or<00:07:03.160> what<00:07:04.160> do<00:07:04.220> you<00:07:04.310> think<00:07:04.580> is<00:07:04.700> the 00:07:04.840 --> 00:07:04.850 align:start position:0% torrent or what do you think is the 00:07:04.850 --> 00:07:07.840 align:start position:0% torrent or what do you think is the analogy<00:07:05.390> is<00:07:05.420> it<00:07:05.750> is<00:07:05.990> it<00:07:06.200> like<00:07:06.230> a<00:07:06.350> Linux<00:07:06.800> is<00:07:07.670> it 00:07:07.840 --> 00:07:07.850 align:start position:0% analogy is it is it like a Linux is it 00:07:07.850 --> 00:07:10.180 align:start position:0% analogy is it is it like a Linux is it like<00:07:08.000> a<00:07:08.030> Java<00:07:08.390> is<00:07:08.570> it<00:07:08.870> like<00:07:09.080> another<00:07:09.680> bitcoin 00:07:10.180 --> 00:07:10.190 align:start position:0% like a Java is it like another bitcoin 00:07:10.190 --> 00:07:12.870 align:start position:0% like a Java is it like another bitcoin is<00:07:10.460> it<00:07:10.670> what's<00:07:11.270> there<00:07:11.420> now<00:07:11.600> analogy<00:07:12.320> that 00:07:12.870 --> 00:07:12.880 align:start position:0% is it what's there now analogy that 00:07:12.880 --> 00:07:20.860 align:start position:0% is it what's there now analogy that athyrium<00:07:13.880> can<00:07:14.330> grow<00:07:15.020> up<00:07:15.170> to<00:07:17.290> I<00:07:18.290> think<00:07:18.470> I<00:07:19.870> think 00:07:20.860 --> 00:07:20.870 align:start position:0% athyrium can grow up to I think I think 00:07:20.870 --> 00:07:25.720 align:start position:0% athyrium can grow up to I think I think it's<00:07:20.990> the<00:07:21.100> HTTPS<00:07:22.100> padlock<00:07:23.650> so<00:07:24.650> this<00:07:25.520> notion 00:07:25.720 --> 00:07:25.730 align:start position:0% it's the HTTPS padlock so this notion 00:07:25.730 --> 00:07:27.580 align:start position:0% it's the HTTPS padlock so this notion that<00:07:25.940> you've<00:07:26.090> got<00:07:26.240> the<00:07:26.330> HTTPS<00:07:27.080> power<00:07:27.350> block 00:07:27.580 --> 00:07:27.590 align:start position:0% that you've got the HTTPS power block 00:07:27.590 --> 00:07:29.140 align:start position:0% that you've got the HTTPS power block which<00:07:27.830> is<00:07:27.860> this<00:07:28.190> kind<00:07:28.400> of<00:07:28.430> ubiquitous<00:07:28.970> symbol 00:07:29.140 --> 00:07:29.150 align:start position:0% which is this kind of ubiquitous symbol 00:07:29.150 --> 00:07:32.020 align:start position:0% which is this kind of ubiquitous symbol it<00:07:29.360> means<00:07:29.390> security<00:07:30.080> the<00:07:31.070> notion<00:07:31.520> you<00:07:31.700> see<00:07:31.910> the 00:07:32.020 --> 00:07:32.030 align:start position:0% it means security the notion you see the 00:07:32.030 --> 00:07:33.610 align:start position:0% it means security the notion you see the ethereal<00:07:32.600> diamond<00:07:32.960> and<00:07:33.050> you<00:07:33.110> know<00:07:33.260> that<00:07:33.470> the 00:07:33.610 --> 00:07:33.620 align:start position:0% ethereal diamond and you know that the 00:07:33.620 --> 00:07:35.350 align:start position:0% ethereal diamond and you know that the system<00:07:34.010> will<00:07:34.190> be<00:07:34.370> secure<00:07:34.760> and<00:07:34.790> will<00:07:35.030> be<00:07:35.180> well 00:07:35.350 --> 00:07:35.360 align:start position:0% system will be secure and will be well 00:07:35.360 --> 00:07:38.590 align:start position:0% system will be secure and will be well behaved<00:07:35.540> and<00:07:36.700> seems<00:07:37.700> pretty<00:07:37.820> reasonable<00:07:38.210> to 00:07:38.590 --> 00:07:38.600 align:start position:0% behaved and seems pretty reasonable to 00:07:38.600 --> 00:07:39.700 align:start position:0% behaved and seems pretty reasonable to me<00:07:38.630> that<00:07:38.870> you<00:07:38.960> know<00:07:38.990> you<00:07:39.110> look<00:07:39.320> on<00:07:39.440> a<00:07:39.470> browser 00:07:39.700 --> 00:07:39.710 align:start position:0% me that you know you look on a browser 00:07:39.710 --> 00:07:41.200 align:start position:0% me that you know you look on a browser if<00:07:39.980> it<00:07:40.100> doesn't<00:07:40.400> have<00:07:40.490> the<00:07:40.520> diamond<00:07:40.940> it's<00:07:41.060> not 00:07:41.200 --> 00:07:41.210 align:start position:0% if it doesn't have the diamond it's not 00:07:41.210 --> 00:07:42.700 align:start position:0% if it doesn't have the diamond it's not a<00:07:41.240> dark<00:07:41.510> it's<00:07:41.720> not<00:07:41.810> securing<00:07:42.350> you<00:07:42.440> know<00:07:42.560> your 00:07:42.700 --> 00:07:42.710 align:start position:0% a dark it's not securing you know your 00:07:42.710 --> 00:07:44.860 align:start position:0% a dark it's not securing you know your money's<00:07:42.950> at<00:07:43.100> rescue<00:07:43.400> normally<00:07:43.670> know<00:07:43.790> why<00:07:43.970> so<00:07:44.840> I 00:07:44.860 --> 00:07:44.870 align:start position:0% money's at rescue normally know why so I 00:07:44.870 --> 00:07:47.400 align:start position:0% money's at rescue normally know why so I think<00:07:45.050> that<00:07:45.260> would<00:07:45.410> be<00:07:45.470> a<00:07:45.590> possible<00:07:46.070> long-term 00:07:47.400 --> 00:07:47.410 align:start position:0% think that would be a possible long-term 00:07:47.410 --> 00:07:50.470 align:start position:0% think that would be a possible long-term get<00:07:48.410> a<00:07:48.440> model<00:07:48.950> of<00:07:49.010> public<00:07:49.340> consciousness<00:07:49.760> you 00:07:50.470 --> 00:07:50.480 align:start position:0% get a model of public consciousness you 00:07:50.480 --> 00:07:52.870 align:start position:0% get a model of public consciousness you know<00:07:50.600> the<00:07:50.930> the<00:07:50.960> you<00:07:51.860> know<00:07:51.980> the<00:07:52.100> sigil<00:07:52.460> equals 00:07:52.870 --> 00:07:52.880 align:start position:0% know the the you know the sigil equals 00:07:52.880 --> 00:08:00.370 align:start position:0% know the the you know the sigil equals secure<00:07:58.120> icon<00:07:59.120> in<00:07:59.240> a<00:07:59.300> particular<00:07:59.480> place<00:07:59.750> we're 00:08:00.370 --> 00:08:00.380 align:start position:0% secure icon in a particular place we're 00:08:00.380 --> 00:08:02.170 align:start position:0% secure icon in a particular place we're kind<00:08:00.590> of<00:08:00.650> undermining<00:08:01.250> the<00:08:01.640> very<00:08:01.670> thing<00:08:02.150> that 00:08:02.170 --> 00:08:02.180 align:start position:0% kind of undermining the very thing that 00:08:02.180 --> 00:08:04.980 align:start position:0% kind of undermining the very thing that were<00:08:02.690> actually<00:08:03.080> providing<00:08:03.890> which<00:08:04.100> is<00:08:04.340> an 00:08:04.980 --> 00:08:04.990 align:start position:0% were actually providing which is an 00:08:04.990 --> 00:08:09.970 align:start position:0% were actually providing which is an actually<00:08:05.990> secure<00:08:07.750> platform<00:08:08.750> so<00:08:09.260> maybe<00:08:09.620> that 00:08:09.970 --> 00:08:09.980 align:start position:0% actually secure platform so maybe that 00:08:09.980 --> 00:08:12.150 align:start position:0% actually secure platform so maybe that having<00:08:10.730> you<00:08:11.030> know<00:08:11.270> the<00:08:11.360> mist<00:08:11.600> browser 00:08:12.150 --> 00:08:12.160 align:start position:0% having you know the mist browser 00:08:12.160 --> 00:08:17.340 align:start position:0% having you know the mist browser identify<00:08:14.200> assets<00:08:15.200> that<00:08:15.620> come<00:08:15.830> off<00:08:15.970> untrusted 00:08:17.340 --> 00:08:17.350 align:start position:0% identify assets that come off untrusted 00:08:17.350 --> 00:08:21.370 align:start position:0% identify assets that come off untrusted interested<00:08:18.350> origins<00:08:18.980> is<00:08:19.960> kind<00:08:20.960> of<00:08:21.080> delivers 00:08:21.370 --> 00:08:21.380 align:start position:0% interested origins is kind of delivers 00:08:21.380 --> 00:08:23.920 align:start position:0% interested origins is kind of delivers the<00:08:21.500> same<00:08:21.680> thing<00:08:21.920> but<00:08:22.300> but<00:08:23.300> but<00:08:23.480> allows<00:08:23.720> the 00:08:23.920 --> 00:08:23.930 align:start position:0% the same thing but but but allows the 00:08:23.930 --> 00:08:26.290 align:start position:0% the same thing but but but allows the user<00:08:24.200> the<00:08:24.470> default<00:08:24.860> should<00:08:25.190> be<00:08:25.370> decentralized 00:08:26.290 --> 00:08:26.300 align:start position:0% user the default should be decentralized 00:08:26.300 --> 00:08:31.630 align:start position:0% user the default should be decentralized and<00:08:26.740> a<00:08:27.740> secure<00:08:28.580> use<00:08:28.820> of<00:08:29.030> your<00:08:29.180> secrets<00:08:30.430> we<00:08:31.430> can 00:08:31.630 --> 00:08:31.640 align:start position:0% and a secure use of your secrets we can 00:08:31.640 --> 00:08:34.510 align:start position:0% and a secure use of your secrets we can can<00:08:32.479> probably<00:08:32.870> get<00:08:33.050> there<00:08:33.260> in<00:08:33.349> time<00:08:33.380> when<00:08:33.890> if 00:08:34.510 --> 00:08:34.520 align:start position:0% can probably get there in time when if 00:08:34.520 --> 00:08:36.700 align:start position:0% can probably get there in time when if Darien<00:08:35.030> becomes<00:08:35.540> ubiquitous<00:08:35.960> and<00:08:36.380> everybody 00:08:36.700 --> 00:08:36.710 align:start position:0% Darien becomes ubiquitous and everybody 00:08:36.710 --> 00:08:40.719 align:start position:0% Darien becomes ubiquitous and everybody just<00:08:36.820> expects<00:08:37.820> this<00:08:39.219> trust<00:08:40.219> minimize 00:08:40.719 --> 00:08:40.729 align:start position:0% just expects this trust minimize 00:08:40.729 --> 00:08:43.180 align:start position:0% just expects this trust minimize computing<00:08:41.479> platform<00:08:42.020> I<00:08:42.380> think<00:08:42.830> that<00:08:42.979> makes 00:08:43.180 --> 00:08:43.190 align:start position:0% computing platform I think that makes 00:08:43.190 --> 00:08:46.329 align:start position:0% computing platform I think that makes sense<00:08:43.430> but<00:08:44.320> for<00:08:45.320> now<00:08:45.500> I<00:08:45.530> think<00:08:45.770> we<00:08:46.040> need<00:08:46.280> to 00:08:46.329 --> 00:08:46.339 align:start position:0% sense but for now I think we need to 00:08:46.339 --> 00:08:50.470 align:start position:0% sense but for now I think we need to deliver<00:08:47.180> the<00:08:47.420> message<00:08:47.810> for<00:08:48.230> now<00:08:48.320> oh<00:08:49.240> it's<00:08:50.240> a 00:08:50.470 --> 00:08:50.480 align:start position:0% deliver the message for now oh it's a 00:08:50.480 --> 00:08:52.000 align:start position:0% deliver the message for now oh it's a world<00:08:50.690> of<00:08:50.839> human<00:08:51.140> beings<00:08:51.440> and<00:08:51.650> human<00:08:51.980> beings 00:08:52.000 --> 00:08:52.010 align:start position:0% world of human beings and human beings 00:08:52.010 --> 00:08:55.600 align:start position:0% world of human beings and human beings need<00:08:52.580> branding<00:08:53.480> in<00:08:53.630> order<00:08:53.870> to<00:08:54.370> unless<00:08:55.370> they're 00:08:55.600 --> 00:08:55.610 align:start position:0% need branding in order to unless they're 00:08:55.610 --> 00:08:57.670 align:start position:0% need branding in order to unless they're going<00:08:55.850> to<00:08:55.970> inspect<00:08:56.390> the<00:08:57.200> byte<00:08:57.380> codes 00:08:57.670 --> 00:08:57.680 align:start position:0% going to inspect the byte codes 00:08:57.680 --> 00:09:00.610 align:start position:0% going to inspect the byte codes themselves<00:08:58.480> which<00:08:59.480> not<00:08:59.780> too<00:08:59.990> many<00:09:00.170> of<00:09:00.290> us<00:09:00.410> will 00:09:00.610 --> 00:09:00.620 align:start position:0% themselves which not too many of us will 00:09:00.620 --> 00:09:04.300 align:start position:0% themselves which not too many of us will do<00:09:00.830> we<00:09:01.820> need<00:09:02.770> trusted<00:09:03.770> authorities 00:09:04.300 --> 00:09:04.310 align:start position:0% do we need trusted authorities 00:09:04.310 --> 00:09:07.600 align:start position:0% do we need trusted authorities unfortunately<00:09:05.180> to<00:09:05.510> teach<00:09:05.900> us<00:09:06.370> what's<00:09:07.370> right 00:09:07.600 --> 00:09:07.610 align:start position:0% unfortunately to teach us what's right 00:09:07.610 --> 00:09:12.940 align:start position:0% unfortunately to teach us what's right to<00:09:07.910> teach<00:09:08.360> us<00:09:08.540> what's<00:09:08.780> secure<00:09:09.380> and<00:09:11.170> even<00:09:12.170> even 00:09:12.940 --> 00:09:12.950 align:start position:0% to teach us what's secure and even even 00:09:12.950 --> 00:09:17.190 align:start position:0% to teach us what's secure and even even when<00:09:13.270> a<00:09:14.270> theorem<00:09:14.900> does<00:09:15.110> become<00:09:15.320> ubiquitous<00:09:16.030> i 00:09:17.190 --> 00:09:17.200 align:start position:0% when a theorem does become ubiquitous i 00:09:17.200 --> 00:09:20.829 align:start position:0% when a theorem does become ubiquitous i would<00:09:18.200> estimate<00:09:18.620> that<00:09:19.280> there<00:09:19.730> that<00:09:20.420> branding 00:09:20.829 --> 00:09:20.839 align:start position:0% would estimate that there that branding 00:09:20.839 --> 00:09:22.810 align:start position:0% would estimate that there that branding will<00:09:20.960> still<00:09:21.200> be<00:09:21.380> really<00:09:21.620> important<00:09:22.130> that 00:09:22.810 --> 00:09:22.820 align:start position:0% will still be really important that 00:09:22.820 --> 00:09:26.829 align:start position:0% will still be really important that they'll<00:09:23.690> be<00:09:23.839> this<00:09:24.050> is<00:09:24.560> one<00:09:25.630> service<00:09:26.630> that 00:09:26.829 --> 00:09:26.839 align:start position:0% they'll be this is one service that 00:09:26.839 --> 00:09:28.690 align:start position:0% they'll be this is one service that provides<00:09:27.040> financial<00:09:28.040> instruments<00:09:28.550> and 00:09:28.690 --> 00:09:28.700 align:start position:0% provides financial instruments and 00:09:28.700 --> 00:09:30.370 align:start position:0% provides financial instruments and another<00:09:28.940> service<00:09:29.330> that<00:09:29.360> provides<00:09:29.630> financial 00:09:30.370 --> 00:09:30.380 align:start position:0% another service that provides financial 00:09:30.380 --> 00:09:31.210 align:start position:0% another service that provides financial instruments<00:09:30.800> and<00:09:30.920> they'll<00:09:31.010> need<00:09:31.190> to 00:09:31.210 --> 00:09:31.220 align:start position:0% instruments and they'll need to 00:09:31.220 --> 00:09:33.480 align:start position:0% instruments and they'll need to differentiate<00:09:31.730> themselves<00:09:32.089> somehow<00:09:32.540> and 00:09:33.480 --> 00:09:33.490 align:start position:0% differentiate themselves somehow and 00:09:33.490 --> 00:09:35.890 align:start position:0% differentiate themselves somehow and apparently<00:09:34.490> that's<00:09:34.730> how<00:09:34.970> we<00:09:35.030> do<00:09:35.360> it<00:09:35.540> with 00:09:35.890 --> 00:09:35.900 align:start position:0% apparently that's how we do it with 00:09:35.900 --> 00:09:44.290 align:start position:0% apparently that's how we do it with branding<00:09:39.760> chief<00:09:40.760> saml<00:09:41.720> keyword<00:09:42.790> how<00:09:43.790> can<00:09:44.000> I<00:09:44.030> a 00:09:44.290 --> 00:09:44.300 align:start position:0% branding chief saml keyword how can I a 00:09:44.300 --> 00:09:47.800 align:start position:0% branding chief saml keyword how can I a theorem<00:09:44.570> achieve<00:09:44.930> Network<00:09:45.680> effects<00:09:46.540> so<00:09:47.540> that 00:09:47.800 --> 00:09:47.810 align:start position:0% theorem achieve Network effects so that 00:09:47.810 --> 00:09:53.079 align:start position:0% theorem achieve Network effects so that it<00:09:48.560> can<00:09:48.830> be<00:09:49.040> deployed<00:09:49.820> more<00:09:51.760> aggressively<00:09:52.760> and 00:09:53.079 --> 00:09:53.089 align:start position:0% it can be deployed more aggressively and 00:09:53.089 --> 00:09:57.430 align:start position:0% it can be deployed more aggressively and quicker<00:09:53.709> there's<00:09:54.709> a<00:09:54.770> theory<00:09:55.190> that<00:09:56.200> when<00:09:57.200> there 00:09:57.430 --> 00:09:57.440 align:start position:0% quicker there's a theory that when there 00:09:57.440 --> 00:09:58.930 align:start position:0% quicker there's a theory that when there when<00:09:57.770> that<00:09:57.800> when<00:09:58.130> the<00:09:58.190> network<00:09:58.459> effects 00:09:58.930 --> 00:09:58.940 align:start position:0% when that when the network effects 00:09:58.940 --> 00:10:01.600 align:start position:0% when that when the network effects something<00:09:59.450> starts<00:09:59.780> to<00:09:59.839> kick<00:10:00.110> in<00:10:00.290> then<00:10:01.190> growth 00:10:01.600 --> 00:10:01.610 align:start position:0% something starts to kick in then growth 00:10:01.610 --> 00:10:05.260 align:start position:0% something starts to kick in then growth happens<00:10:02.860> much<00:10:03.860> more<00:10:03.890> efficiently 00:10:05.260 --> 00:10:05.270 align:start position:0% happens much more efficiently 00:10:05.270 --> 00:10:07.480 align:start position:0% happens much more efficiently so<00:10:05.900> what<00:10:06.290> are<00:10:06.320> your<00:10:06.530> thoughts<00:10:06.710> on<00:10:06.950> network 00:10:07.480 --> 00:10:07.490 align:start position:0% so what are your thoughts on network 00:10:07.490 --> 00:10:11.740 align:start position:0% so what are your thoughts on network effects<00:10:07.850> and<00:10:08.000> etherium<00:10:10.630> infrastructure<00:10:11.630> and 00:10:11.740 --> 00:10:11.750 align:start position:0% effects and etherium infrastructure and 00:10:11.750 --> 00:10:16.690 align:start position:0% effects and etherium infrastructure and applications<00:10:12.100> so<00:10:13.120> with<00:10:14.120> people<00:10:14.480> using<00:10:15.580> so<00:10:16.580> the 00:10:16.690 --> 00:10:16.700 align:start position:0% applications so with people using so the 00:10:16.700 --> 00:10:19.210 align:start position:0% applications so with people using so the obviously<00:10:17.450> athyrium<00:10:17.930> itself<00:10:18.320> is<00:10:18.620> difficult 00:10:19.210 --> 00:10:19.220 align:start position:0% obviously athyrium itself is difficult 00:10:19.220 --> 00:10:22.720 align:start position:0% obviously athyrium itself is difficult to<00:10:20.080> achieve<00:10:21.080> network<00:10:21.770> and<00:10:21.950> effects<00:10:22.340> without 00:10:22.720 --> 00:10:22.730 align:start position:0% to achieve network and effects without 00:10:22.730 --> 00:10:24.820 align:start position:0% to achieve network and effects without yeah<00:10:23.480> there's<00:10:23.690> no<00:10:23.810> intrinsic<00:10:24.230> networking 00:10:24.820 --> 00:10:24.830 align:start position:0% yeah there's no intrinsic networking 00:10:24.830 --> 00:10:27.550 align:start position:0% yeah there's no intrinsic networking until<00:10:25.160> people<00:10:25.520> have<00:10:25.820> ways<00:10:26.690> of<00:10:26.870> interoperating 00:10:27.550 --> 00:10:27.560 align:start position:0% until people have ways of interoperating 00:10:27.560 --> 00:10:32.050 align:start position:0% until people have ways of interoperating and<00:10:27.950> so<00:10:28.730> that<00:10:28.760> infrastructure<00:10:29.950> is<00:10:30.950> we<00:10:31.820> will 00:10:32.050 --> 00:10:32.060 align:start position:0% and so that infrastructure is we will 00:10:32.060 --> 00:10:34.120 align:start position:0% and so that infrastructure is we will provide<00:10:32.480> the<00:10:32.540> ways<00:10:32.930> of<00:10:33.230> interoperating<00:10:33.920> so 00:10:34.120 --> 00:10:34.130 align:start position:0% provide the ways of interoperating so 00:10:34.130 --> 00:10:36.250 align:start position:0% provide the ways of interoperating so things<00:10:34.310> like<00:10:34.430> registries<00:10:35.000> identity<00:10:35.540> all<00:10:36.020> the 00:10:36.250 --> 00:10:36.260 align:start position:0% things like registries identity all the 00:10:36.260 --> 00:10:37.330 align:start position:0% things like registries identity all the things<00:10:36.410> that<00:10:36.620> we<00:10:36.680> chatted<00:10:36.980> about<00:10:37.070> in<00:10:37.280> the 00:10:37.330 --> 00:10:37.340 align:start position:0% things that we chatted about in the 00:10:37.340 --> 00:10:40.180 align:start position:0% things that we chatted about in the standardization<00:10:37.940> panel<00:10:38.680> this<00:10:39.680> needs<00:10:39.950> to<00:10:40.070> be 00:10:40.180 --> 00:10:40.190 align:start position:0% standardization panel this needs to be 00:10:40.190 --> 00:10:42.940 align:start position:0% standardization panel this needs to be built<00:10:40.910> and<00:10:41.210> built<00:10:41.360> and<00:10:41.570> built<00:10:41.690> and<00:10:41.930> then<00:10:42.710> built 00:10:42.940 --> 00:10:42.950 align:start position:0% built and built and built and then built 00:10:42.950 --> 00:10:45.400 align:start position:0% built and built and built and then built upon<00:10:43.190> again<00:10:43.430> and<00:10:43.670> it's<00:10:44.510> that<00:10:44.630> that<00:10:45.020> will<00:10:45.170> allow 00:10:45.400 --> 00:10:45.410 align:start position:0% upon again and it's that that will allow 00:10:45.410 --> 00:10:48.690 align:start position:0% upon again and it's that that will allow will<00:10:46.010> bring<00:10:46.430> the<00:10:46.730> rich<00:10:46.970> commons<00:10:47.510> of<00:10:47.780> you<00:10:48.200> know 00:10:48.690 --> 00:10:48.700 align:start position:0% will bring the rich commons of you know 00:10:48.700 --> 00:10:52.810 align:start position:0% will bring the rich commons of you know user<00:10:50.350> interaction<00:10:51.350> that<00:10:51.770> will<00:10:52.730> ultimately 00:10:52.810 --> 00:10:52.820 align:start position:0% user interaction that will ultimately 00:10:52.820 --> 00:10:54.850 align:start position:0% user interaction that will ultimately deliver<00:10:53.270> thee<00:10:53.600> you<00:10:54.560> know<00:10:54.680> these<00:10:54.830> these 00:10:54.850 --> 00:10:54.860 align:start position:0% deliver thee you know these these 00:10:54.860 --> 00:10:58.060 align:start position:0% deliver thee you know these these effects<00:10:55.580> yeah<00:10:56.480> i<00:10:56.630> agree<00:10:56.920> infrastructure<00:10:57.920> and 00:10:58.060 --> 00:10:58.070 align:start position:0% effects yeah i agree infrastructure and 00:10:58.070 --> 00:11:00.130 align:start position:0% effects yeah i agree infrastructure and applications<00:10:58.160> and<00:10:59.120> to<00:10:59.600> get<00:10:59.750> there<00:10:59.960> we<00:10:59.990> need 00:11:00.130 --> 00:11:00.140 align:start position:0% applications and to get there we need 00:11:00.140 --> 00:11:04.480 align:start position:0% applications and to get there we need money<00:11:00.530> money<00:11:00.980> and<00:11:01.070> more<00:11:01.520> money<00:11:01.960> so<00:11:03.490> bitcoin 00:11:04.480 --> 00:11:04.490 align:start position:0% money money and more money so bitcoin 00:11:04.490 --> 00:11:07.570 align:start position:0% money money and more money so bitcoin has<00:11:05.350> received<00:11:06.350> the<00:11:06.650> Bitcoin<00:11:07.070> space<00:11:07.250> has 00:11:07.570 --> 00:11:07.580 align:start position:0% has received the Bitcoin space has 00:11:07.580 --> 00:11:09.040 align:start position:0% has received the Bitcoin space has received<00:11:07.940> the<00:11:08.000> benefit<00:11:08.360> of<00:11:08.420> about<00:11:08.780> a<00:11:08.810> billion 00:11:09.040 --> 00:11:09.050 align:start position:0% received the benefit of about a billion 00:11:09.050 --> 00:11:12.940 align:start position:0% received the benefit of about a billion dollars<00:11:09.500> over<00:11:09.800> the<00:11:09.890> last<00:11:10.070> year<00:11:10.430> of<00:11:11.950> vc 00:11:12.940 --> 00:11:12.950 align:start position:0% dollars over the last year of vc 00:11:12.950 --> 00:11:16.930 align:start position:0% dollars over the last year of vc investment<00:11:13.640> and<00:11:15.100> from<00:11:16.100> what<00:11:16.250> I've<00:11:16.370> seen<00:11:16.400> I 00:11:16.930 --> 00:11:16.940 align:start position:0% investment and from what I've seen I 00:11:16.940 --> 00:11:19.420 align:start position:0% investment and from what I've seen I would<00:11:17.360> love<00:11:17.510> to<00:11:17.570> hear<00:11:17.810> your<00:11:18.200> comments<00:11:18.980> but 00:11:19.420 --> 00:11:19.430 align:start position:0% would love to hear your comments but 00:11:19.430 --> 00:11:21.880 align:start position:0% would love to hear your comments but from<00:11:19.640> what<00:11:19.730> I've<00:11:19.880> seen<00:11:19.910> a<00:11:20.570> lot<00:11:20.930> of<00:11:21.290> VCS<00:11:21.680> are 00:11:21.880 --> 00:11:21.890 align:start position:0% from what I've seen a lot of VCS are 00:11:21.890 --> 00:11:23.620 align:start position:0% from what I've seen a lot of VCS are really<00:11:22.460> paying<00:11:22.640> attention<00:11:22.790> certainly<00:11:23.480> a<00:11:23.510> lot 00:11:23.620 --> 00:11:23.630 align:start position:0% really paying attention certainly a lot 00:11:23.630 --> 00:11:26.860 align:start position:0% really paying attention certainly a lot of<00:11:23.750> banks<00:11:23.990> and<00:11:24.440> accounting<00:11:25.160> firms<00:11:25.490> and<00:11:25.940> other 00:11:26.860 --> 00:11:26.870 align:start position:0% of banks and accounting firms and other 00:11:26.870 --> 00:11:29.170 align:start position:0% of banks and accounting firms and other sorts<00:11:27.470> of<00:11:27.650> business<00:11:28.100> issues<00:11:28.460> are<00:11:28.670> paying<00:11:28.910> a 00:11:29.170 --> 00:11:29.180 align:start position:0% sorts of business issues are paying a 00:11:29.180 --> 00:11:32.410 align:start position:0% sorts of business issues are paying a lot<00:11:29.930> of<00:11:30.310> attention<00:11:31.310> to<00:11:31.550> what<00:11:31.940> they<00:11:32.060> can<00:11:32.240> do<00:11:32.390> on 00:11:32.410 --> 00:11:32.420 align:start position:0% lot of attention to what they can do on 00:11:32.420 --> 00:11:33.940 align:start position:0% lot of attention to what they can do on a<00:11:32.570> theorem<00:11:32.960> that<00:11:33.140> they<00:11:33.290> can't<00:11:33.530> do<00:11:33.650> on<00:11:33.800> any 00:11:33.940 --> 00:11:33.950 align:start position:0% a theorem that they can't do on any 00:11:33.950 --> 00:11:37.920 align:start position:0% a theorem that they can't do on any other<00:11:34.190> system<00:11:34.960> and<00:11:35.960> I<00:11:36.920> would<00:11:37.130> I<00:11:37.430> couldn't 00:11:37.920 --> 00:11:37.930 align:start position:0% other system and I would I couldn't 00:11:37.930 --> 00:11:41.110 align:start position:0% other system and I would I couldn't imagine<00:11:38.930> very<00:11:39.680> easily<00:11:39.920> seeing<00:11:40.460> a<00:11:40.610> billion<00:11:40.970> or 00:11:41.110 --> 00:11:41.120 align:start position:0% imagine very easily seeing a billion or 00:11:41.120 --> 00:11:44.020 align:start position:0% imagine very easily seeing a billion or two<00:11:41.150> billion<00:11:41.600> or<00:11:42.170> n<00:11:42.860> billion<00:11:43.340> dollars<00:11:43.640> coming 00:11:44.020 --> 00:11:44.030 align:start position:0% two billion or n billion dollars coming 00:11:44.030 --> 00:11:47.890 align:start position:0% two billion or n billion dollars coming into<00:11:44.450> the<00:11:44.690> ecosystem<00:11:45.670> over<00:11:46.670> the<00:11:46.790> next<00:11:46.940> year<00:11:47.870> or 00:11:47.890 --> 00:11:47.900 align:start position:0% into the ecosystem over the next year or 00:11:47.900 --> 00:11:50.820 align:start position:0% into the ecosystem over the next year or a<00:11:48.110> few<00:11:48.320> years<00:11:48.530> and<00:11:49.430> that<00:11:50.090> will<00:11:50.360> build 00:11:50.820 --> 00:11:50.830 align:start position:0% a few years and that will build 00:11:50.830 --> 00:11:55.390 align:start position:0% a few years and that will build applications<00:11:51.830> but<00:11:54.100> scalability<00:11:55.100> is<00:11:55.220> the 00:11:55.390 --> 00:11:55.400 align:start position:0% applications but scalability is the 00:11:55.400 --> 00:11:58.720 align:start position:0% applications but scalability is the major<00:11:55.550> issue<00:11:55.910> that<00:11:56.360> that<00:11:57.290> this<00:11:57.740> system<00:11:58.040> faces 00:11:58.720 --> 00:11:58.730 align:start position:0% major issue that that this system faces 00:11:58.730 --> 00:12:02.380 align:start position:0% major issue that that this system faces and<00:11:59.650> without<00:12:00.650> taking<00:12:01.130> some<00:12:01.430> of<00:12:01.580> that<00:12:01.730> VC<00:12:02.180> money 00:12:02.380 --> 00:12:02.390 align:start position:0% and without taking some of that VC money 00:12:02.390 --> 00:12:05.440 align:start position:0% and without taking some of that VC money and<00:12:03.310> driving<00:12:04.310> it<00:12:04.430> down<00:12:04.640> into<00:12:05.360> the 00:12:05.440 --> 00:12:05.450 align:start position:0% and driving it down into the 00:12:05.450 --> 00:12:08.140 align:start position:0% and driving it down into the infrastructure<00:12:05.720> into<00:12:06.470> the<00:12:06.590> plumbing<00:12:07.150> that 00:12:08.140 --> 00:12:08.150 align:start position:0% infrastructure into the plumbing that 00:12:08.150 --> 00:12:09.850 align:start position:0% infrastructure into the plumbing that basically<00:12:08.720> looks<00:12:08.990> like<00:12:09.140> every<00:12:09.440> company 00:12:09.850 --> 00:12:09.860 align:start position:0% basically looks like every company 00:12:09.860 --> 00:12:12.510 align:start position:0% basically looks like every company that's<00:12:10.040> getting<00:12:10.340> funded<00:12:10.730> should<00:12:11.000> probably 00:12:12.510 --> 00:12:12.520 align:start position:0% that's getting funded should probably 00:12:12.520 --> 00:12:17.369 align:start position:0% that's getting funded should probably consider<00:12:13.520> devoting<00:12:14.500> ten<00:12:15.500> twenty<00:12:16.190> percent 00:12:17.369 --> 00:12:17.379 align:start position:0% consider devoting ten twenty percent 00:12:17.379 --> 00:12:19.710 align:start position:0% consider devoting ten twenty percent you<00:12:17.470> helping<00:12:18.399> out<00:12:18.549> at<00:12:18.849> the<00:12:18.999> foundation<00:12:19.359> level 00:12:19.710 --> 00:12:19.720 align:start position:0% you helping out at the foundation level 00:12:19.720 --> 00:12:21.960 align:start position:0% you helping out at the foundation level building<00:12:20.229> the<00:12:20.319> protocol<00:12:20.910> building<00:12:21.910> a 00:12:21.960 --> 00:12:21.970 align:start position:0% building the protocol building a 00:12:21.970 --> 00:12:24.150 align:start position:0% building the protocol building a scalable<00:12:22.419> system<00:12:22.809> I<00:12:22.989> think<00:12:23.589> that's<00:12:23.769> an<00:12:23.919> easy 00:12:24.150 --> 00:12:24.160 align:start position:0% scalable system I think that's an easy 00:12:24.160 --> 00:12:28.589 align:start position:0% scalable system I think that's an easy sell<00:12:24.549> to<00:12:24.939> VCS<00:12:25.410> do<00:12:26.410> you<00:12:26.559> want<00:12:26.970> our<00:12:27.970> product<00:12:28.449> or 00:12:28.589 --> 00:12:28.599 align:start position:0% sell to VCS do you want our product or 00:12:28.599 --> 00:12:34.409 align:start position:0% sell to VCS do you want our product or service<00:12:29.019> to<00:12:30.599> be<00:12:31.599> accessible<00:12:31.989> to<00:12:32.519> a<00:12:33.519> fairly 00:12:34.409 --> 00:12:34.419 align:start position:0% service to be accessible to a fairly 00:12:34.419 --> 00:12:37.859 align:start position:0% service to be accessible to a fairly limited<00:12:35.069> swath<00:12:36.069> of<00:12:36.399> the<00:12:36.669> planet<00:12:37.029> or<00:12:37.509> do<00:12:37.809> you 00:12:37.859 --> 00:12:37.869 align:start position:0% limited swath of the planet or do you 00:12:37.869 --> 00:12:40.589 align:start position:0% limited swath of the planet or do you want<00:12:38.049> it<00:12:38.109> to<00:12:38.289> be<00:12:38.499> accessible<00:12:39.159> to<00:12:39.489> 7<00:12:40.239> billion 00:12:40.589 --> 00:12:40.599 align:start position:0% want it to be accessible to 7 billion 00:12:40.599 --> 00:12:42.719 align:start position:0% want it to be accessible to 7 billion people<00:12:40.629> ultimately<00:12:41.139> or<00:12:41.709> 12<00:12:42.159> billion<00:12:42.519> people 00:12:42.719 --> 00:12:42.729 align:start position:0% people ultimately or 12 billion people 00:12:42.729 --> 00:12:47.369 align:start position:0% people ultimately or 12 billion people ultimately<00:12:43.059> when<00:12:43.899> we<00:12:44.019> get<00:12:44.229> there<00:12:45.119> yeah<00:12:46.119> so<00:12:47.109> you 00:12:47.369 --> 00:12:47.379 align:start position:0% ultimately when we get there yeah so you 00:12:47.379 --> 00:12:49.259 align:start position:0% ultimately when we get there yeah so you mentioned<00:12:47.739> the<00:12:47.949> banks<00:12:48.399> and<00:12:48.639> and<00:12:48.909> this<00:12:49.089> is<00:12:49.239> a 00:12:49.259 --> 00:12:49.269 align:start position:0% mentioned the banks and and this is a 00:12:49.269 --> 00:12:51.269 align:start position:0% mentioned the banks and and this is a very<00:12:49.389> important<00:12:49.929> point<00:12:50.139> which<00:12:50.439> we<00:12:50.919> kind<00:12:51.189> of 00:12:51.269 --> 00:12:51.279 align:start position:0% very important point which we kind of 00:12:51.279 --> 00:12:53.489 align:start position:0% very important point which we kind of are<00:12:51.519> taking<00:12:51.879> for<00:12:52.059> granted<00:12:52.089> but<00:12:52.659> we're 00:12:53.489 --> 00:12:53.499 align:start position:0% are taking for granted but we're 00:12:53.499 --> 00:12:55.439 align:start position:0% are taking for granted but we're discussing<00:12:54.039> last<00:12:54.279> night<00:12:54.549> and<00:12:54.909> if<00:12:55.179> you<00:12:55.269> think 00:12:55.439 --> 00:12:55.449 align:start position:0% discussing last night and if you think 00:12:55.449 --> 00:12:57.569 align:start position:0% discussing last night and if you think about<00:12:55.509> it<00:12:55.689> the<00:12:56.470> banks<00:12:56.769> have<00:12:56.919> not<00:12:57.099> touched<00:12:57.249> the 00:12:57.569 --> 00:12:57.579 align:start position:0% about it the banks have not touched the 00:12:57.579 --> 00:13:01.309 align:start position:0% about it the banks have not touched the coin<00:12:57.849> but<00:12:58.809> they<00:12:59.589> are<00:12:59.709> embracing<00:13:00.099> etherium<00:13:00.789> and 00:13:01.309 --> 00:13:01.319 align:start position:0% coin but they are embracing etherium and 00:13:01.319 --> 00:13:04.139 align:start position:0% coin but they are embracing etherium and there<00:13:02.319> are<00:13:02.439> numerous<00:13:02.619> banks<00:13:03.159> that<00:13:03.279> are<00:13:03.339> either 00:13:04.139 --> 00:13:04.149 align:start position:0% there are numerous banks that are either 00:13:04.149 --> 00:13:08.309 align:start position:0% there are numerous banks that are either trying<00:13:04.569> it<00:13:05.169> or<00:13:05.609> doing<00:13:06.609> proof<00:13:06.939> of<00:13:07.089> concepts<00:13:08.079> and 00:13:08.309 --> 00:13:08.319 align:start position:0% trying it or doing proof of concepts and 00:13:08.319 --> 00:13:10.529 align:start position:0% trying it or doing proof of concepts and and<00:13:08.499> that's<00:13:09.429> a<00:13:09.579> big<00:13:09.699> achievement<00:13:09.909> that<00:13:10.419> is 00:13:10.529 --> 00:13:10.539 align:start position:0% and that's a big achievement that is 00:13:10.539 --> 00:13:13.699 align:start position:0% and that's a big achievement that is kind<00:13:10.809> of<00:13:10.869> a<00:13:10.959> bit<00:13:11.139> I<00:13:11.739> think<00:13:12.489> understated 00:13:13.699 --> 00:13:13.709 align:start position:0% kind of a bit I think understated 00:13:13.709 --> 00:13:16.439 align:start position:0% kind of a bit I think understated because<00:13:14.709> half<00:13:14.919> of<00:13:15.009> them<00:13:15.220> don't<00:13:15.369> want<00:13:15.549> anybody 00:13:16.439 --> 00:13:16.449 align:start position:0% because half of them don't want anybody 00:13:16.449 --> 00:13:18.599 align:start position:0% because half of them don't want anybody to<00:13:16.629> know<00:13:16.659> that<00:13:16.899> they<00:13:16.989> are<00:13:17.109> doing<00:13:17.259> it<00:13:17.499> but<00:13:18.249> some 00:13:18.599 --> 00:13:18.609 align:start position:0% to know that they are doing it but some 00:13:18.609 --> 00:13:20.129 align:start position:0% to know that they are doing it but some of<00:13:18.699> the<00:13:18.819> other<00:13:18.939> half<00:13:19.179> are<00:13:19.419> saying<00:13:19.720> that<00:13:19.989> they 00:13:20.129 --> 00:13:20.139 align:start position:0% of the other half are saying that they 00:13:20.139 --> 00:13:21.840 align:start position:0% of the other half are saying that they are<00:13:20.229> doing<00:13:20.409> stuff<00:13:20.829> on<00:13:20.979> a<00:13:21.039> theorem<00:13:21.459> and<00:13:21.549> I<00:13:21.609> think 00:13:21.840 --> 00:13:21.850 align:start position:0% are doing stuff on a theorem and I think 00:13:21.850 --> 00:13:24.590 align:start position:0% are doing stuff on a theorem and I think that<00:13:22.479> that's<00:13:22.509> a<00:13:22.839> big<00:13:22.989> achievement<00:13:23.079> and 00:13:24.590 --> 00:13:24.600 align:start position:0% that that's a big achievement and 00:13:24.600 --> 00:13:28.649 align:start position:0% that that's a big achievement and hopefully<00:13:25.600> it's<00:13:25.720> going<00:13:25.869> to<00:13:26.549> have<00:13:27.549> a<00:13:27.659> side 00:13:28.649 --> 00:13:28.659 align:start position:0% hopefully it's going to have a side 00:13:28.659 --> 00:13:31.319 align:start position:0% hopefully it's going to have a side effect<00:13:29.019> of<00:13:29.199> more<00:13:29.649> growth<00:13:29.889> and<00:13:30.189> more<00:13:31.089> and<00:13:31.299> more 00:13:31.319 --> 00:13:31.329 align:start position:0% effect of more growth and more and more 00:13:31.329 --> 00:13:35.039 align:start position:0% effect of more growth and more and more adoption<00:13:31.929> as<00:13:32.109> well<00:13:32.529> so<00:13:33.519> it's<00:13:34.329> up<00:13:34.749> to<00:13:34.779> us<00:13:34.989> to 00:13:35.039 --> 00:13:35.049 align:start position:0% adoption as well so it's up to us to 00:13:35.049 --> 00:13:37.889 align:start position:0% adoption as well so it's up to us to start<00:13:35.589> to<00:13:35.709> tell<00:13:35.859> those<00:13:36.069> stories<00:13:36.249> I<00:13:36.819> think<00:13:37.689> the 00:13:37.889 --> 00:13:37.899 align:start position:0% start to tell those stories I think the 00:13:37.899 --> 00:13:40.139 align:start position:0% start to tell those stories I think the market<00:13:38.229> wants<00:13:38.439> to<00:13:38.529> hear<00:13:38.679> stories<00:13:39.029> wants<00:13:40.029> to 00:13:40.139 --> 00:13:40.149 align:start position:0% market wants to hear stories wants to 00:13:40.149 --> 00:13:43.349 align:start position:0% market wants to hear stories wants to hear<00:13:40.649> different<00:13:41.649> use<00:13:41.799> cases<00:13:42.009> and<00:13:42.399> best 00:13:43.349 --> 00:13:43.359 align:start position:0% hear different use cases and best 00:13:43.359 --> 00:13:47.999 align:start position:0% hear different use cases and best practices<00:13:43.899> I<00:13:45.689> mean<00:13:46.689> I<00:13:46.720> think<00:13:46.779> of<00:13:47.019> this<00:13:47.139> a<00:13:47.379> lot 00:13:47.999 --> 00:13:48.009 align:start position:0% practices I mean I think of this a lot 00:13:48.009 --> 00:13:49.319 align:start position:0% practices I mean I think of this a lot of<00:13:48.100> this<00:13:48.220> is<00:13:48.399> because<00:13:48.639> the<00:13:48.699> theorem<00:13:49.059> is<00:13:49.209> seen 00:13:49.319 --> 00:13:49.329 align:start position:0% of this is because the theorem is seen 00:13:49.329 --> 00:13:52.169 align:start position:0% of this is because the theorem is seen as<00:13:49.449> being<00:13:49.600> kind<00:13:49.839> of<00:13:50.489> politically<00:13:51.489> safer<00:13:52.059> than 00:13:52.169 --> 00:13:52.179 align:start position:0% as being kind of politically safer than 00:13:52.179 --> 00:13:54.179 align:start position:0% as being kind of politically safer than Bitcoin<00:13:52.419> you<00:13:53.139> know<00:13:53.259> the<00:13:53.409> etherion<00:13:53.739> community 00:13:54.179 --> 00:13:54.189 align:start position:0% Bitcoin you know the etherion community 00:13:54.189 --> 00:13:55.769 align:start position:0% Bitcoin you know the etherion community has<00:13:54.309> a<00:13:54.339> pretty<00:13:54.639> kind<00:13:54.879> of<00:13:54.970> straight<00:13:55.419> down<00:13:55.600> the 00:13:55.769 --> 00:13:55.779 align:start position:0% has a pretty kind of straight down the 00:13:55.779 --> 00:13:57.769 align:start position:0% has a pretty kind of straight down the line<00:13:55.899> technology<00:13:56.319> computer<00:13:57.129> science 00:13:57.769 --> 00:13:57.779 align:start position:0% line technology computer science 00:13:57.779 --> 00:14:00.389 align:start position:0% line technology computer science decentralization<00:13:58.779> as<00:13:59.109> an<00:13:59.229> effect<00:13:59.649> but 00:14:00.389 --> 00:14:00.399 align:start position:0% decentralization as an effect but 00:14:00.399 --> 00:14:02.699 align:start position:0% decentralization as an effect but without<00:14:00.639> really<00:14:00.909> naming<00:14:01.329> our<00:14:01.419> enemies<00:14:01.869> and<00:14:02.559> I 00:14:02.699 --> 00:14:02.709 align:start position:0% without really naming our enemies and I 00:14:02.709 --> 00:14:03.899 align:start position:0% without really naming our enemies and I think<00:14:02.919> that<00:14:03.039> that's<00:14:03.069> been<00:14:03.489> very<00:14:03.699> helpful 00:14:03.899 --> 00:14:03.909 align:start position:0% think that that's been very helpful 00:14:03.909 --> 00:14:05.429 align:start position:0% think that that's been very helpful because<00:14:04.299> the<00:14:04.509> banks<00:14:04.749> have<00:14:04.839> been<00:14:04.899> desperate<00:14:05.409> to 00:14:05.429 --> 00:14:05.439 align:start position:0% because the banks have been desperate to 00:14:05.439 --> 00:14:06.899 align:start position:0% because the banks have been desperate to do<00:14:05.649> something<00:14:05.949> with<00:14:06.039> Bitcoin<00:14:06.399> but<00:14:06.579> didn't 00:14:06.899 --> 00:14:06.909 align:start position:0% do something with Bitcoin but didn't 00:14:06.909 --> 00:14:08.699 align:start position:0% do something with Bitcoin but didn't want<00:14:07.059> to<00:14:07.179> get<00:14:07.359> a<00:14:07.600> whole<00:14:08.019> bunch<00:14:08.049> of<00:14:08.289> political 00:14:08.699 --> 00:14:08.709 align:start position:0% want to get a whole bunch of political 00:14:08.709 --> 00:14:10.879 align:start position:0% want to get a whole bunch of political rhetoric<00:14:08.859> alongside<00:14:09.309> of<00:14:09.669> it<00:14:09.789> and<00:14:09.970> the<00:14:10.600> sort<00:14:10.779> of 00:14:10.879 --> 00:14:10.889 align:start position:0% rhetoric alongside of it and the sort of 00:14:10.889 --> 00:14:12.449 align:start position:0% rhetoric alongside of it and the sort of economics<00:14:11.889> narrative<00:14:12.399> about 00:14:12.449 --> 00:14:12.459 align:start position:0% economics narrative about 00:14:12.459 --> 00:14:14.369 align:start position:0% economics narrative about decentralization<00:14:12.970> is<00:14:13.689> efficient<00:14:14.169> with<00:14:14.289> the 00:14:14.369 --> 00:14:14.379 align:start position:0% decentralization is efficient with the 00:14:14.379 --> 00:14:15.899 align:start position:0% decentralization is efficient with the current<00:14:14.559> technology<00:14:15.129> base<00:14:15.339> therefore<00:14:15.789> it's 00:14:15.899 --> 00:14:15.909 align:start position:0% current technology base therefore it's 00:14:15.909 --> 00:14:18.449 align:start position:0% current technology base therefore it's inevitable<00:14:16.509> and<00:14:17.039> doesn't<00:14:18.039> force<00:14:18.279> the 00:14:18.449 --> 00:14:18.459 align:start position:0% inevitable and doesn't force the 00:14:18.459 --> 00:14:20.789 align:start position:0% inevitable and doesn't force the confrontation<00:14:19.089> it<00:14:19.209> just<00:14:19.389> accepts<00:14:19.899> that<00:14:20.049> the 00:14:20.789 --> 00:14:20.799 align:start position:0% confrontation it just accepts that the 00:14:20.799 --> 00:14:21.929 align:start position:0% confrontation it just accepts that the most<00:14:21.009> efficient<00:14:21.399> form<00:14:21.669> will<00:14:21.819> be<00:14:21.849> a 00:14:21.929 --> 00:14:21.939 align:start position:0% most efficient form will be a 00:14:21.939 --> 00:14:23.189 align:start position:0% most efficient form will be a decentralized<00:14:22.419> firms<00:14:22.809> there'll<00:14:23.079> be<00:14:23.109> a 00:14:23.189 --> 00:14:23.199 align:start position:0% decentralized firms there'll be a 00:14:23.199 --> 00:14:24.329 align:start position:0% decentralized firms there'll be a migration<00:14:23.559> over<00:14:23.889> into<00:14:24.129> the 00:14:24.329 --> 00:14:24.339 align:start position:0% migration over into the 00:14:24.339 --> 00:14:26.519 align:start position:0% migration over into the forms<00:14:24.730> and<00:14:25.389> I<00:14:25.449> think<00:14:25.629> that<00:14:25.749> that's<00:14:25.779> really<00:14:26.170> the 00:14:26.519 --> 00:14:26.529 align:start position:0% forms and I think that that's really the 00:14:26.529 --> 00:14:29.340 align:start position:0% forms and I think that that's really the adoption<00:14:26.980> curve<00:14:27.399> that<00:14:28.269> you<00:14:28.839> know<00:14:28.930> we<00:14:29.050> forget 00:14:29.340 --> 00:14:29.350 align:start position:0% adoption curve that you know we forget 00:14:29.350 --> 00:14:30.900 align:start position:0% adoption curve that you know we forget the<00:14:29.439> decentralization<00:14:30.189> is<00:14:30.490> something<00:14:30.790> which 00:14:30.900 --> 00:14:30.910 align:start position:0% the decentralization is something which 00:14:30.910 --> 00:14:33.420 align:start position:0% the decentralization is something which is<00:14:31.029> our<00:14:31.180> global<00:14:31.629> mega<00:14:32.259> trend<00:14:32.620> because<00:14:33.249> of 00:14:33.420 --> 00:14:33.430 align:start position:0% is our global mega trend because of 00:14:33.430 --> 00:14:35.780 align:start position:0% is our global mega trend because of things<00:14:33.579> like<00:14:33.670> cheaper<00:14:34.449> super<00:14:34.930> solar<00:14:35.259> panels 00:14:35.780 --> 00:14:35.790 align:start position:0% things like cheaper super solar panels 00:14:35.790 --> 00:14:38.670 align:start position:0% things like cheaper super solar panels aging<00:14:36.790> grade<00:14:37.180> there<00:14:38.079> are<00:14:38.139> lots<00:14:38.470> of<00:14:38.559> things 00:14:38.670 --> 00:14:38.680 align:start position:0% aging grade there are lots of things 00:14:38.680 --> 00:14:40.410 align:start position:0% aging grade there are lots of things that<00:14:38.860> are<00:14:38.949> pushing<00:14:39.279> us<00:14:39.430> towards<00:14:39.819> this<00:14:40.149> kind<00:14:40.389> of 00:14:40.410 --> 00:14:40.420 align:start position:0% that are pushing us towards this kind of 00:14:40.420 --> 00:14:41.759 align:start position:0% that are pushing us towards this kind of d<00:14:40.600> centroids<00:14:41.019> were<00:14:41.170> couldn't<00:14:41.620> just 00:14:41.759 --> 00:14:41.769 align:start position:0% d centroids were couldn't just 00:14:41.769 --> 00:14:43.860 align:start position:0% d centroids were couldn't just availability<00:14:42.370> and<00:14:42.490> networking<00:14:42.819> so<00:14:43.660> we're 00:14:43.860 --> 00:14:43.870 align:start position:0% availability and networking so we're 00:14:43.870 --> 00:14:46.170 align:start position:0% availability and networking so we're another<00:14:44.170> part<00:14:44.649> of<00:14:44.889> this<00:14:45.129> global<00:14:45.339> mega<00:14:45.759> trend 00:14:46.170 --> 00:14:46.180 align:start position:0% another part of this global mega trend 00:14:46.180 --> 00:14:48.150 align:start position:0% another part of this global mega trend which<00:14:46.930> means<00:14:47.170> that<00:14:47.259> for<00:14:47.379> example<00:14:47.470> the<00:14:47.829> banks 00:14:48.150 --> 00:14:48.160 align:start position:0% which means that for example the banks 00:14:48.160 --> 00:14:51.030 align:start position:0% which means that for example the banks are<00:14:48.279> looking<00:14:48.550> this<00:14:48.790> up<00:14:49.529> you<00:14:50.529> know<00:14:50.620> part<00:14:50.860> of<00:14:50.949> a 00:14:51.030 --> 00:14:51.040 align:start position:0% are looking this up you know part of a 00:14:51.040 --> 00:14:54.509 align:start position:0% are looking this up you know part of a whole<00:14:51.189> system<00:14:51.579> of<00:14:51.879> operations<00:14:53.249> so<00:14:54.249> it's<00:14:54.370> not 00:14:54.509 --> 00:14:54.519 align:start position:0% whole system of operations so it's not 00:14:54.519 --> 00:14:55.710 align:start position:0% whole system of operations so it's not that<00:14:54.579> we're<00:14:54.819> selling<00:14:54.999> a<00:14:55.149> single<00:14:55.449> technology 00:14:55.710 --> 00:14:55.720 align:start position:0% that we're selling a single technology 00:14:55.720 --> 00:14:57.869 align:start position:0% that we're selling a single technology it's<00:14:56.230> if<00:14:56.740> you're<00:14:56.889> looking<00:14:57.160> to<00:14:57.249> adapt<00:14:57.490> to<00:14:57.759> this 00:14:57.869 --> 00:14:57.879 align:start position:0% it's if you're looking to adapt to this 00:14:57.879 --> 00:14:59.939 align:start position:0% it's if you're looking to adapt to this inevitable<00:14:58.480> decentralization<00:14:59.199> of<00:14:59.410> society 00:14:59.939 --> 00:14:59.949 align:start position:0% inevitable decentralization of society 00:14:59.949 --> 00:15:02.249 align:start position:0% inevitable decentralization of society because<00:15:00.699> of<00:15:00.819> a<00:15:00.879> multi<00:15:01.389> dimensional<00:15:01.839> shift<00:15:02.139> in 00:15:02.249 --> 00:15:02.259 align:start position:0% because of a multi dimensional shift in 00:15:02.259 --> 00:15:04.829 align:start position:0% because of a multi dimensional shift in the<00:15:02.290> technology<00:15:02.860> base<00:15:03.209> then<00:15:04.209> this<00:15:04.629> is<00:15:04.809> a 00:15:04.829 --> 00:15:04.839 align:start position:0% the technology base then this is a 00:15:04.839 --> 00:15:06.119 align:start position:0% the technology base then this is a positive<00:15:05.170> thing<00:15:05.470> that<00:15:05.740> you<00:15:05.829> can<00:15:05.949> do<00:15:06.100> to 00:15:06.119 --> 00:15:06.129 align:start position:0% positive thing that you can do to 00:15:06.129 --> 00:15:09.230 align:start position:0% positive thing that you can do to survive<00:15:06.490> those<00:15:06.759> transitions<00:15:07.709> there's<00:15:08.709> a 00:15:09.230 --> 00:15:09.240 align:start position:0% survive those transitions there's a 00:15:09.240 --> 00:15:12.780 align:start position:0% survive those transitions there's a there's<00:15:10.240> a<00:15:10.329> slow<00:15:10.809> but<00:15:11.230> very<00:15:11.709> inevitable<00:15:12.430> curve 00:15:12.780 --> 00:15:12.790 align:start position:0% there's a slow but very inevitable curve 00:15:12.790 --> 00:15:14.970 align:start position:0% there's a slow but very inevitable curve here<00:15:13.240> the<00:15:13.449> things<00:15:13.660> are<00:15:13.749> going<00:15:13.990> down<00:15:14.230> and 00:15:14.970 --> 00:15:14.980 align:start position:0% here the things are going down and 00:15:14.980 --> 00:15:16.530 align:start position:0% here the things are going down and there's<00:15:15.129> no<00:15:15.249> way<00:15:15.370> back<00:15:15.550> up<00:15:15.759> that<00:15:15.939> curve<00:15:16.149> that's 00:15:16.530 --> 00:15:16.540 align:start position:0% there's no way back up that curve that's 00:15:16.540 --> 00:15:18.079 align:start position:0% there's no way back up that curve that's just<00:15:16.809> what<00:15:16.959> the<00:15:17.050> technology<00:15:17.199> looks<00:15:17.620> like<00:15:17.800> that 00:15:18.079 --> 00:15:18.089 align:start position:0% just what the technology looks like that 00:15:18.089 --> 00:15:20.460 align:start position:0% just what the technology looks like that this<00:15:19.089> definitely<00:15:19.300> has<00:15:19.720> the<00:15:19.779> feel<00:15:20.170> of 00:15:20.460 --> 00:15:20.470 align:start position:0% this definitely has the feel of 00:15:20.470 --> 00:15:23.939 align:start position:0% this definitely has the feel of inevitability<00:15:22.019> so<00:15:23.019> so<00:15:23.439> if<00:15:23.529> we<00:15:23.589> have<00:15:23.769> two 00:15:23.939 --> 00:15:23.949 align:start position:0% inevitability so so if we have two 00:15:23.949 --> 00:15:26.400 align:start position:0% inevitability so so if we have two thousand<00:15:24.430> developers<00:15:24.910> more<00:15:25.120> or<00:15:25.269> less<00:15:25.420> now<00:15:26.019> on 00:15:26.400 --> 00:15:26.410 align:start position:0% thousand developers more or less now on 00:15:26.410 --> 00:15:29.129 align:start position:0% thousand developers more or less now on athyrium<00:15:26.949> let's<00:15:27.730> say<00:15:27.970> next<00:15:28.269> year<00:15:28.929> or<00:15:29.079> whenever 00:15:29.129 --> 00:15:29.139 align:start position:0% athyrium let's say next year or whenever 00:15:29.139 --> 00:15:31.470 align:start position:0% athyrium let's say next year or whenever the<00:15:29.439> next<00:15:29.620> Def<00:15:29.860> Con<00:15:30.129> is<00:15:30.309> how<00:15:31.120> many<00:15:31.209> do<00:15:31.420> you 00:15:31.470 --> 00:15:31.480 align:start position:0% the next Def Con is how many do you 00:15:31.480 --> 00:15:34.290 align:start position:0% the next Def Con is how many do you think<00:15:31.569> we<00:15:31.839> should<00:15:31.870> there<00:15:32.649> be<00:15:33.089> developers<00:15:34.089> on 00:15:34.290 --> 00:15:34.300 align:start position:0% think we should there be developers on 00:15:34.300 --> 00:15:41.639 align:start position:0% think we should there be developers on net<00:15:34.509> doing<00:15:34.990> a<00:15:35.079> theorem<00:15:38.220> 5,000<00:15:39.220> 10,000<00:15:40.379> so<00:15:41.379> I 00:15:41.639 --> 00:15:41.649 align:start position:0% net doing a theorem 5,000 10,000 so I 00:15:41.649 --> 00:15:45.360 align:start position:0% net doing a theorem 5,000 10,000 so I can<00:15:42.639> imagine<00:15:43.379> next<00:15:44.379> Def<00:15:44.589> Con<00:15:44.889> whether<00:15:45.160> it's 00:15:45.360 --> 00:15:45.370 align:start position:0% can imagine next Def Con whether it's 00:15:45.370 --> 00:15:47.910 align:start position:0% can imagine next Def Con whether it's six<00:15:45.610> months<00:15:46.059> from<00:15:46.269> now<00:15:46.300> or<00:15:46.959> 12<00:15:47.410> months<00:15:47.740> from 00:15:47.910 --> 00:15:47.920 align:start position:0% six months from now or 12 months from 00:15:47.920 --> 00:15:50.369 align:start position:0% six months from now or 12 months from now<00:15:47.949> I<00:15:48.399> would<00:15:48.910> imagine<00:15:48.970> that<00:15:49.329> for<00:15:50.170> every 00:15:50.369 --> 00:15:50.379 align:start position:0% now I would imagine that for every 00:15:50.379 --> 00:15:53.730 align:start position:0% now I would imagine that for every developer<00:15:50.889> here<00:15:51.129> there's<00:15:51.429> a<00:15:51.819> be<00:15:52.480> ten<00:15:53.019> in<00:15:53.350> six 00:15:53.730 --> 00:15:53.740 align:start position:0% developer here there's a be ten in six 00:15:53.740 --> 00:15:55.650 align:start position:0% developer here there's a be ten in six months<00:15:53.920> and<00:15:54.429> I<00:15:54.879> don't<00:15:55.300> even<00:15:55.389> want<00:15:55.600> to 00:15:55.650 --> 00:15:55.660 align:start position:0% months and I don't even want to 00:15:55.660 --> 00:15:58.049 align:start position:0% months and I don't even want to speculate<00:15:56.019> what<00:15:56.290> it's<00:15:56.439> going<00:15:56.559> to<00:15:56.620> be<00:15:56.709> in<00:15:57.009> in<00:15:57.309> 12 00:15:58.049 --> 00:15:58.059 align:start position:0% speculate what it's going to be in in 12 00:15:58.059 --> 00:16:03.689 align:start position:0% speculate what it's going to be in in 12 months<00:15:58.300> I<00:15:59.019> think<00:16:00.779> we<00:16:01.779> joked<00:16:02.110> about<00:16:02.429> hiring<00:16:03.429> out 00:16:03.689 --> 00:16:03.699 align:start position:0% months I think we joked about hiring out 00:16:03.699 --> 00:16:08.999 align:start position:0% months I think we joked about hiring out Wembley<00:16:04.209> for<00:16:04.600> this<00:16:04.720> event<00:16:05.850> this<00:16:06.850> year<00:16:06.910> but<00:16:08.009> who 00:16:08.999 --> 00:16:09.009 align:start position:0% Wembley for this event this year but who 00:16:09.009 --> 00:16:13.319 align:start position:0% Wembley for this event this year but who knows<00:16:09.929> give<00:16:10.929> it<00:16:11.079> maybe<00:16:11.350> we'll<00:16:11.559> have<00:16:12.399> a<00:16:12.459> town<00:16:13.300> in 00:16:13.319 --> 00:16:13.329 align:start position:0% knows give it maybe we'll have a town in 00:16:13.329 --> 00:16:18.629 align:start position:0% knows give it maybe we'll have a town in Kazakhstan<00:16:14.290> or<00:16:14.470> something<00:16:14.889> I<00:16:17.399> mean<00:16:18.399> it's<00:16:18.519> not 00:16:18.629 --> 00:16:18.639 align:start position:0% Kazakhstan or something I mean it's not 00:16:18.639 --> 00:16:20.249 align:start position:0% Kazakhstan or something I mean it's not just<00:16:18.910> developer<00:16:19.420> bound<00:16:19.629> right<00:16:19.929> it's<00:16:20.110> also 00:16:20.249 --> 00:16:20.259 align:start position:0% just developer bound right it's also 00:16:20.259 --> 00:16:23.040 align:start position:0% just developer bound right it's also tool<00:16:20.620> bound<00:16:20.949> so<00:16:21.759> I<00:16:22.149> think<00:16:22.509> there<00:16:22.629> are<00:16:22.749> a<00:16:22.779> lot<00:16:23.019> of 00:16:23.040 --> 00:16:23.050 align:start position:0% tool bound so I think there are a lot of 00:16:23.050 --> 00:16:25.499 align:start position:0% tool bound so I think there are a lot of kind<00:16:23.410> of<00:16:23.499> big<00:16:24.220> web<00:16:24.519> shops<00:16:24.939> you<00:16:25.300> know<00:16:25.389> the<00:16:25.480> kind 00:16:25.499 --> 00:16:25.509 align:start position:0% kind of big web shops you know the kind 00:16:25.509 --> 00:16:27.960 align:start position:0% kind of big web shops you know the kind of<00:16:25.660> 20-30<00:16:26.170> person<00:16:26.529> Internet<00:16:26.920> companies<00:16:27.370> that 00:16:27.960 --> 00:16:27.970 align:start position:0% of 20-30 person Internet companies that 00:16:27.970 --> 00:16:29.579 align:start position:0% of 20-30 person Internet companies that could<00:16:28.149> very<00:16:28.179> easily<00:16:28.449> wind<00:16:28.899> up<00:16:29.050> with<00:16:29.259> one<00:16:29.470> or 00:16:29.579 --> 00:16:29.589 align:start position:0% could very easily wind up with one or 00:16:29.589 --> 00:16:31.560 align:start position:0% could very easily wind up with one or two<00:16:29.620> athyrium<00:16:30.160> guys<00:16:30.339> on<00:16:30.550> staff<00:16:30.819> and 00:16:31.560 --> 00:16:31.570 align:start position:0% two athyrium guys on staff and 00:16:31.570 --> 00:16:32.850 align:start position:0% two athyrium guys on staff and someone's<00:16:31.840> hair<00:16:31.990> tools<00:16:32.320> and<00:16:32.590> support 00:16:32.850 --> 00:16:32.860 align:start position:0% someone's hair tools and support 00:16:32.860 --> 00:16:34.980 align:start position:0% someone's hair tools and support services<00:16:33.150> that<00:16:34.150> would<00:16:34.270> then<00:16:34.450> be<00:16:34.630> in<00:16:34.870> a 00:16:34.980 --> 00:16:34.990 align:start position:0% services that would then be in a 00:16:34.990 --> 00:16:36.570 align:start position:0% services that would then be in a position<00:16:35.110> to<00:16:35.380> develop<00:16:35.860> and<00:16:36.010> deployed<00:16:36.280> apps 00:16:36.570 --> 00:16:36.580 align:start position:0% position to develop and deployed apps 00:16:36.580 --> 00:16:38.790 align:start position:0% position to develop and deployed apps without<00:16:37.300> necessarily<00:16:37.630> having<00:16:38.140> massive 00:16:38.790 --> 00:16:38.800 align:start position:0% without necessarily having massive 00:16:38.800 --> 00:16:40.890 align:start position:0% without necessarily having massive internal<00:16:39.100> expertise<00:16:39.760> so<00:16:40.480> I<00:16:40.510> think<00:16:40.600> you<00:16:40.780> could 00:16:40.890 --> 00:16:40.900 align:start position:0% internal expertise so I think you could 00:16:40.900 --> 00:16:42.540 align:start position:0% internal expertise so I think you could see<00:16:41.020> the<00:16:41.140> number<00:16:41.410> of<00:16:41.500> institutions<00:16:42.070> are 00:16:42.540 --> 00:16:42.550 align:start position:0% see the number of institutions are 00:16:42.550 --> 00:16:44.640 align:start position:0% see the number of institutions are functionally<00:16:43.180> able<00:16:43.450> to<00:16:43.660> commission<00:16:44.560> or 00:16:44.640 --> 00:16:44.650 align:start position:0% functionally able to commission or 00:16:44.650 --> 00:16:46.680 align:start position:0% functionally able to commission or deliver<00:16:44.980> an<00:16:45.160> app<00:16:45.340> could<00:16:45.940> be<00:16:46.090> a<00:16:46.120> hundred<00:16:46.300> times 00:16:46.680 --> 00:16:46.690 align:start position:0% deliver an app could be a hundred times 00:16:46.690 --> 00:16:49.050 align:start position:0% deliver an app could be a hundred times what<00:16:46.930> it<00:16:47.050> is<00:16:47.080> now<00:16:47.170> in<00:16:47.500> a<00:16:47.590> year<00:16:47.950> even<00:16:48.370> if<00:16:48.700> most<00:16:48.880> of 00:16:49.050 --> 00:16:49.060 align:start position:0% what it is now in a year even if most of 00:16:49.060 --> 00:16:50.520 align:start position:0% what it is now in a year even if most of the<00:16:49.150> understanding<00:16:49.720> is<00:16:49.810> relatively<00:16:50.230> shallow 00:16:50.520 --> 00:16:50.530 align:start position:0% the understanding is relatively shallow 00:16:50.530 --> 00:16:51.960 align:start position:0% the understanding is relatively shallow because<00:16:50.860> most<00:16:51.160> of<00:16:51.250> the<00:16:51.340> DAPs<00:16:51.520> will<00:16:51.700> be<00:16:51.790> called 00:16:51.960 --> 00:16:51.970 align:start position:0% because most of the DAPs will be called 00:16:51.970 --> 00:16:54.380 align:start position:0% because most of the DAPs will be called as<00:16:52.090> similar<00:16:52.480> as<00:16:52.540> websites<00:16:53.080> are<00:16:53.290> to<00:16:53.440> each<00:16:53.560> other 00:16:54.380 --> 00:16:54.390 align:start position:0% as similar as websites are to each other 00:16:54.390 --> 00:16:58.100 align:start position:0% as similar as websites are to each other yeah<00:16:55.390> i<00:16:55.420> think<00:16:56.250> the<00:16:57.250> developer<00:16:57.670> numbers<00:16:57.970> are 00:16:58.100 --> 00:16:58.110 align:start position:0% yeah i think the developer numbers are 00:16:58.110 --> 00:17:00.450 align:start position:0% yeah i think the developer numbers are kind<00:16:59.110> of<00:16:59.230> an<00:16:59.320> interesting<00:16:59.800> one<00:17:00.160> there's<00:17:00.310> a<00:17:00.340> lot 00:17:00.450 --> 00:17:00.460 align:start position:0% kind of an interesting one there's a lot 00:17:00.460 --> 00:17:02.130 align:start position:0% kind of an interesting one there's a lot of<00:17:00.490> gray<00:17:00.700> area<00:17:01.030> that<00:17:01.240> the<00:17:01.690> way<00:17:01.810> that<00:17:01.990> we've 00:17:02.130 --> 00:17:02.140 align:start position:0% of gray area that the way that we've 00:17:02.140 --> 00:17:04.470 align:start position:0% of gray area that the way that we've we've<00:17:02.470> made<00:17:02.710> the<00:17:02.860> api's<00:17:03.220> are<00:17:03.970> such<00:17:04.300> that 00:17:04.470 --> 00:17:04.480 align:start position:0% we've made the api's are such that 00:17:04.480 --> 00:17:09.150 align:start position:0% we've made the api's are such that there's<00:17:04.630> a<00:17:04.690> relatively<00:17:05.199> easy<00:17:06.959> on<00:17:07.959> ramp<00:17:08.500> from 00:17:09.150 --> 00:17:09.160 align:start position:0% there's a relatively easy on ramp from 00:17:09.160 --> 00:17:11.760 align:start position:0% there's a relatively easy on ramp from traditional<00:17:09.910> web<00:17:10.120> stuff<00:17:10.510> into<00:17:11.470> sort<00:17:11.680> of 00:17:11.760 --> 00:17:11.770 align:start position:0% traditional web stuff into sort of 00:17:11.770 --> 00:17:17.189 align:start position:0% traditional web stuff into sort of full-on<00:17:12.570> consensus<00:17:13.570> coding<00:17:13.959> so<00:17:15.810> at<00:17:16.810> the<00:17:16.990> one 00:17:17.189 --> 00:17:17.199 align:start position:0% full-on consensus coding so at the one 00:17:17.199 --> 00:17:19.500 align:start position:0% full-on consensus coding so at the one end<00:17:17.230> you<00:17:17.589> know<00:17:17.650> it's<00:17:17.940> much<00:17:18.940> of<00:17:19.120> it<00:17:19.209> is<00:17:19.329> about 00:17:19.500 --> 00:17:19.510 align:start position:0% end you know it's much of it is about 00:17:19.510 --> 00:17:23.850 align:start position:0% end you know it's much of it is about sort<00:17:19.930> of<00:17:19.990> classic<00:17:20.770> HTML<00:17:21.730> CSS<00:17:22.860> javascript 00:17:23.850 --> 00:17:23.860 align:start position:0% sort of classic HTML CSS javascript 00:17:23.860 --> 00:17:25.770 align:start position:0% sort of classic HTML CSS javascript stuff<00:17:24.040> at<00:17:24.699> the<00:17:24.820> other<00:17:24.940> end<00:17:25.089> is<00:17:25.240> maybe<00:17:25.449> you<00:17:25.660> know 00:17:25.770 --> 00:17:25.780 align:start position:0% stuff at the other end is maybe you know 00:17:25.780 --> 00:17:27.449 align:start position:0% stuff at the other end is maybe you know some<00:17:26.020> pretty<00:17:26.230> hardcore<00:17:26.560> game<00:17:26.949> theory<00:17:27.400> in 00:17:27.449 --> 00:17:27.459 align:start position:0% some pretty hardcore game theory in 00:17:27.459 --> 00:17:30.150 align:start position:0% some pretty hardcore game theory in solidity<00:17:27.850> and<00:17:28.530> in<00:17:29.530> between<00:17:29.680> there's<00:17:30.100> an 00:17:30.150 --> 00:17:30.160 align:start position:0% solidity and in between there's an 00:17:30.160 --> 00:17:35.160 align:start position:0% solidity and in between there's an entire<00:17:30.400> spectrum<00:17:30.940> of<00:17:31.150> f<00:17:31.950> of<00:17:32.950> ability<00:17:34.050> so<00:17:35.050> what 00:17:35.160 --> 00:17:35.170 align:start position:0% entire spectrum of f of ability so what 00:17:35.170 --> 00:17:36.450 align:start position:0% entire spectrum of f of ability so what you're<00:17:35.290> saying<00:17:35.440> that<00:17:35.500> summed<00:17:35.860> apps<00:17:36.040> are<00:17:36.250> kind 00:17:36.450 --> 00:17:36.460 align:start position:0% you're saying that summed apps are kind 00:17:36.460 --> 00:17:38.430 align:start position:0% you're saying that summed apps are kind of<00:17:36.490> invisible<00:17:36.790> they're<00:17:37.690> doing<00:17:37.930> their<00:17:38.080> job<00:17:38.290> in 00:17:38.430 --> 00:17:38.440 align:start position:0% of invisible they're doing their job in 00:17:38.440 --> 00:17:40.560 align:start position:0% of invisible they're doing their job in the<00:17:38.530> background<00:17:38.980> and<00:17:39.160> well<00:17:39.880> I<00:17:39.940> guess<00:17:40.210> that<00:17:40.240> the 00:17:40.560 --> 00:17:40.570 align:start position:0% the background and well I guess that the 00:17:40.570 --> 00:17:42.780 align:start position:0% the background and well I guess that the point<00:17:40.720> is<00:17:40.930> that<00:17:41.200> the<00:17:41.860> the<00:17:41.890> actual<00:17:42.220> number<00:17:42.550> of 00:17:42.780 --> 00:17:42.790 align:start position:0% point is that the the actual number of 00:17:42.790 --> 00:17:44.430 align:start position:0% point is that the the actual number of developers<00:17:43.270> are<00:17:43.510> very<00:17:43.870> difficult<00:17:44.320> to 00:17:44.430 --> 00:17:44.440 align:start position:0% developers are very difficult to 00:17:44.440 --> 00:17:47.910 align:start position:0% developers are very difficult to actually<00:17:45.660> guess<00:17:46.660> because<00:17:47.170> quite<00:17:47.440> a<00:17:47.500> lot<00:17:47.740> of 00:17:47.910 --> 00:17:47.920 align:start position:0% actually guess because quite a lot of 00:17:47.920 --> 00:17:49.650 align:start position:0% actually guess because quite a lot of the<00:17:48.070> there<00:17:48.340> could<00:17:48.460> be<00:17:48.490> like<00:17:48.940> already<00:17:49.390> there 00:17:49.650 --> 00:17:49.660 align:start position:0% the there could be like already there 00:17:49.660 --> 00:17:52.110 align:start position:0% the there could be like already there could<00:17:49.810> be<00:17:49.840> over<00:17:50.320> 10,000<00:17:51.040> that<00:17:51.160> know<00:17:51.370> that 00:17:52.110 --> 00:17:52.120 align:start position:0% could be over 10,000 that know that 00:17:52.120 --> 00:17:53.670 align:start position:0% could be over 10,000 that know that there<00:17:52.300> is<00:17:52.420> such<00:17:52.660> a<00:17:52.690> thing<00:17:52.810> as<00:17:52.990> like<00:17:53.260> this<00:17:53.470> web 00:17:53.670 --> 00:17:53.680 align:start position:0% there is such a thing as like this web 00:17:53.680 --> 00:17:56.130 align:start position:0% there is such a thing as like this web three<00:17:54.040> object<00:17:54.520> that<00:17:54.820> has<00:17:55.150> you<00:17:55.660> know<00:17:55.780> allows 00:17:56.130 --> 00:17:56.140 align:start position:0% three object that has you know allows 00:17:56.140 --> 00:17:57.990 align:start position:0% three object that has you know allows you<00:17:56.350> to<00:17:56.500> interact<00:17:57.220> with<00:17:57.430> some<00:17:57.610> magic 00:17:57.990 --> 00:17:58.000 align:start position:0% you to interact with some magic 00:17:58.000 --> 00:18:04.920 align:start position:0% you to interact with some magic invisible<00:17:58.240> server<00:17:58.720> I<00:18:03.780> think<00:18:04.780> that's 00:18:04.920 --> 00:18:04.930 align:start position:0% invisible server I think that's 00:18:04.930 --> 00:18:07.020 align:start position:0% invisible server I think that's reasonable<00:18:05.140> i<00:18:05.500> think<00:18:05.740> there<00:18:05.920> might<00:18:06.310> be<00:18:06.370> 10,000 00:18:07.020 --> 00:18:07.030 align:start position:0% reasonable i think there might be 10,000 00:18:07.030 --> 00:18:09.660 align:start position:0% reasonable i think there might be 10,000 people<00:18:07.300> who've<00:18:07.450> taken<00:18:07.630> a<00:18:08.290> glance<00:18:08.770> at<00:18:09.190> this 00:18:09.660 --> 00:18:09.670 align:start position:0% people who've taken a glance at this 00:18:09.670 --> 00:18:12.150 align:start position:0% people who've taken a glance at this technology<00:18:10.300> haven't<00:18:10.630> haven't<00:18:11.620> spent<00:18:11.920> more 00:18:12.150 --> 00:18:12.160 align:start position:0% technology haven't haven't spent more 00:18:12.160 --> 00:18:16.530 align:start position:0% technology haven't haven't spent more than<00:18:12.310> an<00:18:12.760> hour<00:18:13.240> or<00:18:13.570> two<00:18:13.840> but<00:18:14.740> you<00:18:15.400> know<00:18:15.520> i<00:18:15.760> do 00:18:16.530 --> 00:18:16.540 align:start position:0% than an hour or two but you know i do 00:18:16.540 --> 00:18:17.850 align:start position:0% than an hour or two but you know i do that<00:18:16.810> with<00:18:16.990> lots<00:18:17.170> of<00:18:17.290> different<00:18:17.590> technologies 00:18:17.850 --> 00:18:17.860 align:start position:0% that with lots of different technologies 00:18:17.860 --> 00:18:22.860 align:start position:0% that with lots of different technologies give<00:18:18.700> it<00:18:18.820> a<00:18:18.880> good<00:18:19.030> solid<00:18:19.300> 30<00:18:20.140> minutes<00:18:21.690> but<00:18:22.690> I 00:18:22.860 --> 00:18:22.870 align:start position:0% give it a good solid 30 minutes but I 00:18:22.870 --> 00:18:28.050 align:start position:0% give it a good solid 30 minutes but I think<00:18:23.640> at<00:18:24.640> in<00:18:25.620> two<00:18:26.620> years<00:18:26.920> from<00:18:27.190> now<00:18:27.430> four 00:18:28.050 --> 00:18:28.060 align:start position:0% think at in two years from now four 00:18:28.060 --> 00:18:30.900 align:start position:0% think at in two years from now four years<00:18:28.210> from<00:18:28.330> now<00:18:28.630> I<00:18:28.900> think<00:18:29.310> the<00:18:30.310> notion<00:18:30.700> of 00:18:30.900 --> 00:18:30.910 align:start position:0% years from now I think the notion of 00:18:30.910 --> 00:18:34.350 align:start position:0% years from now I think the notion of developer<00:18:31.540> might<00:18:31.960> even<00:18:32.140> change<00:18:32.820> this<00:18:33.820> kind<00:18:34.330> of 00:18:34.350 --> 00:18:34.360 align:start position:0% developer might even change this kind of 00:18:34.360 --> 00:18:36.180 align:start position:0% developer might even change this kind of infrastructure<00:18:34.660> is<00:18:35.410> going<00:18:35.590> to<00:18:35.650> enable<00:18:35.860> us<00:18:36.160> to 00:18:36.180 --> 00:18:36.190 align:start position:0% infrastructure is going to enable us to 00:18:36.190 --> 00:18:38.610 align:start position:0% infrastructure is going to enable us to build<00:18:36.610> two<00:18:37.090> puzzle<00:18:37.600> pieces<00:18:37.630> or<00:18:38.230> building 00:18:38.610 --> 00:18:38.620 align:start position:0% build two puzzle pieces or building 00:18:38.620 --> 00:18:39.810 align:start position:0% build two puzzle pieces or building blocks<00:18:38.890> out<00:18:39.250> of 00:18:39.810 --> 00:18:39.820 align:start position:0% blocks out of 00:18:39.820 --> 00:18:42.420 align:start position:0% blocks out of smart<00:18:40.690> contracts<00:18:41.200> or<00:18:41.440> smart<00:18:41.830> clauses<00:18:42.400> that 00:18:42.420 --> 00:18:42.430 align:start position:0% smart contracts or smart clauses that 00:18:42.430 --> 00:18:44.880 align:start position:0% smart contracts or smart clauses that you<00:18:42.760> can<00:18:42.940> compose<00:18:43.330> into<00:18:43.840> smart<00:18:44.110> contracts<00:18:44.770> and 00:18:44.880 --> 00:18:44.890 align:start position:0% you can compose into smart contracts and 00:18:44.890 --> 00:18:50.510 align:start position:0% you can compose into smart contracts and so<00:18:45.100> I<00:18:45.400> think<00:18:46.060> lawyers<00:18:47.550> business<00:18:48.550> dev<00:18:48.970> people 00:18:50.510 --> 00:18:50.520 align:start position:0% so I think lawyers business dev people 00:18:50.520 --> 00:18:59.430 align:start position:0% so I think lawyers business dev people could<00:18:51.520> end<00:18:51.700> up<00:18:52.800> being<00:18:53.800> quite<00:18:54.730> technical<00:18:57.720> so<00:18:58.720> in 00:18:59.430 --> 00:18:59.440 align:start position:0% could end up being quite technical so in 00:18:59.440 --> 00:19:00.810 align:start position:0% could end up being quite technical so in one<00:18:59.830> of<00:18:59.920> the<00:18:59.980> things<00:19:00.160> i<00:19:00.280> think<00:19:00.430> it's<00:19:00.670> worth 00:19:00.810 --> 00:19:00.820 align:start position:0% one of the things i think it's worth 00:19:00.820 --> 00:19:02.610 align:start position:0% one of the things i think it's worth discussing<00:19:01.300> is<00:19:01.540> you<00:19:02.020> know<00:19:02.110> really<00:19:02.500> there's 00:19:02.610 --> 00:19:02.620 align:start position:0% discussing is you know really there's 00:19:02.620 --> 00:19:05.010 align:start position:0% discussing is you know really there's going<00:19:02.770> to<00:19:02.830> be<00:19:02.860> blood<00:19:03.130> on<00:19:03.310> the<00:19:03.430> tiles<00:19:03.790> but<00:19:04.570> one 00:19:05.010 --> 00:19:05.020 align:start position:0% going to be blood on the tiles but one 00:19:05.020 --> 00:19:06.540 align:start position:0% going to be blood on the tiles but one of<00:19:05.050> the<00:19:05.140> things<00:19:05.230> i've<00:19:05.470> been<00:19:05.680> talking<00:19:06.040> about<00:19:06.310> is 00:19:06.540 --> 00:19:06.550 align:start position:0% of the things i've been talking about is 00:19:06.550 --> 00:19:08.270 align:start position:0% of the things i've been talking about is that<00:19:06.730> etherium<00:19:07.240> is<00:19:07.360> potentially<00:19:07.870> the<00:19:08.020> first 00:19:08.270 --> 00:19:08.280 align:start position:0% that etherium is potentially the first 00:19:08.280 --> 00:19:10.620 align:start position:0% that etherium is potentially the first really<00:19:09.280> effective<00:19:09.820> tool<00:19:10.060> kit<00:19:10.300> for<00:19:10.450> white 00:19:10.620 --> 00:19:10.630 align:start position:0% really effective tool kit for white 00:19:10.630 --> 00:19:13.440 align:start position:0% really effective tool kit for white collar<00:19:10.810> automation<00:19:11.760> that<00:19:12.760> you<00:19:12.850> can<00:19:13.030> see<00:19:13.150> lots 00:19:13.440 --> 00:19:13.450 align:start position:0% collar automation that you can see lots 00:19:13.450 --> 00:19:15.180 align:start position:0% collar automation that you can see lots and<00:19:13.660> lots<00:19:13.810> and<00:19:13.900> lots<00:19:13.990> of<00:19:14.230> people<00:19:14.500> whose<00:19:14.740> job<00:19:15.070> it 00:19:15.180 --> 00:19:15.190 align:start position:0% and lots and lots of people whose job it 00:19:15.190 --> 00:19:17.700 align:start position:0% and lots and lots of people whose job it is<00:19:15.280> to<00:19:15.340> do<00:19:15.640> the<00:19:16.270> perform<00:19:16.750> transactions<00:19:17.530> in 00:19:17.700 --> 00:19:17.710 align:start position:0% is to do the perform transactions in 00:19:17.710 --> 00:19:20.100 align:start position:0% is to do the perform transactions in relatively<00:19:18.220> high<00:19:18.430> trust<00:19:18.760> networks<00:19:19.240> like 00:19:20.100 --> 00:19:20.110 align:start position:0% relatively high trust networks like 00:19:20.110 --> 00:19:23.250 align:start position:0% relatively high trust networks like interbank<00:19:20.710> trading<00:19:21.310> type<00:19:21.520> stuff<00:19:22.050> that<00:19:23.050> you 00:19:23.250 --> 00:19:23.260 align:start position:0% interbank trading type stuff that you 00:19:23.260 --> 00:19:24.960 align:start position:0% interbank trading type stuff that you could<00:19:23.410> see<00:19:23.590> entire<00:19:23.890> departments<00:19:24.490> basically 00:19:24.960 --> 00:19:24.970 align:start position:0% could see entire departments basically 00:19:24.970 --> 00:19:27.150 align:start position:0% could see entire departments basically be<00:19:25.150> replaced<00:19:25.540> by<00:19:25.840> you<00:19:26.290> know<00:19:26.380> half<00:19:26.890> a<00:19:27.010> dozen 00:19:27.150 --> 00:19:27.160 align:start position:0% be replaced by you know half a dozen 00:19:27.160 --> 00:19:30.450 align:start position:0% be replaced by you know half a dozen tabs<00:19:27.460> and<00:19:28.320> the<00:19:29.320> notion<00:19:29.470> that<00:19:29.680> one<00:19:29.830> of<00:19:29.920> the<00:19:30.010> huge 00:19:30.450 --> 00:19:30.460 align:start position:0% tabs and the notion that one of the huge 00:19:30.460 --> 00:19:32.550 align:start position:0% tabs and the notion that one of the huge drivers<00:19:31.240> for<00:19:31.480> a<00:19:31.510> theory<00:19:31.750> of<00:19:31.840> development<00:19:31.990> is 00:19:32.550 --> 00:19:32.560 align:start position:0% drivers for a theory of development is 00:19:32.560 --> 00:19:35.220 align:start position:0% drivers for a theory of development is going<00:19:32.860> to<00:19:32.980> be<00:19:33.160> you<00:19:33.820> know<00:19:33.880> essentially<00:19:34.480> firing 00:19:35.220 --> 00:19:35.230 align:start position:0% going to be you know essentially firing 00:19:35.230 --> 00:19:36.840 align:start position:0% going to be you know essentially firing paper<00:19:35.500> pushers<00:19:35.980> and<00:19:36.010> replacing<00:19:36.670> them<00:19:36.700> with 00:19:36.840 --> 00:19:36.850 align:start position:0% paper pushers and replacing them with 00:19:36.850 --> 00:19:40.530 align:start position:0% paper pushers and replacing them with technology<00:19:38.790> it's<00:19:39.790> a<00:19:39.850> hell<00:19:40.090> of<00:19:40.120> a<00:19:40.330> thing<00:19:40.480> to 00:19:40.530 --> 00:19:40.540 align:start position:0% technology it's a hell of a thing to 00:19:40.540 --> 00:19:41.940 align:start position:0% technology it's a hell of a thing to think<00:19:40.810> of<00:19:40.900> yourself<00:19:41.200> as<00:19:41.320> being<00:19:41.440> the<00:19:41.590> bleeding 00:19:41.940 --> 00:19:41.950 align:start position:0% think of yourself as being the bleeding 00:19:41.950 --> 00:19:44.370 align:start position:0% think of yourself as being the bleeding edge<00:19:42.070> technological<00:19:42.940> unemployment<00:19:43.260> but<00:19:44.260> I<00:19:44.290> do 00:19:44.370 --> 00:19:44.380 align:start position:0% edge technological unemployment but I do 00:19:44.380 --> 00:19:45.900 align:start position:0% edge technological unemployment but I do think<00:19:44.680> that<00:19:44.800> that<00:19:45.010> could<00:19:45.040> be<00:19:45.310> a<00:19:45.340> huge<00:19:45.550> part<00:19:45.790> of 00:19:45.900 --> 00:19:45.910 align:start position:0% think that that could be a huge part of 00:19:45.910 --> 00:19:47.370 align:start position:0% think that that could be a huge part of what<00:19:46.060> drives<00:19:46.090> adoption<00:19:46.750> in<00:19:46.840> the<00:19:46.930> initial<00:19:47.080> few 00:19:47.370 --> 00:19:47.380 align:start position:0% what drives adoption in the initial few 00:19:47.380 --> 00:19:50.070 align:start position:0% what drives adoption in the initial few stages<00:19:47.650> is<00:19:48.070> large<00:19:48.700> organizations<00:19:49.540> are<00:19:49.780> under 00:19:50.070 --> 00:19:50.080 align:start position:0% stages is large organizations are under 00:19:50.080 --> 00:19:51.720 align:start position:0% stages is large organizations are under financial<00:19:50.380> pressure<00:19:50.650> because<00:19:51.250> the<00:19:51.370> markets 00:19:51.720 --> 00:19:51.730 align:start position:0% financial pressure because the markets 00:19:51.730 --> 00:19:54.390 align:start position:0% financial pressure because the markets are<00:19:51.850> so<00:19:52.000> kind<00:19:52.210> of<00:19:52.300> rough<00:19:52.510> and<00:19:52.950> you<00:19:53.950> know<00:19:54.010> taking 00:19:54.390 --> 00:19:54.400 align:start position:0% are so kind of rough and you know taking 00:19:54.400 --> 00:19:56.280 align:start position:0% are so kind of rough and you know taking ten<00:19:54.730> fifteen<00:19:55.150> twenty<00:19:55.180> percent<00:19:55.720> of<00:19:55.930> their<00:19:56.080> head 00:19:56.280 --> 00:19:56.290 align:start position:0% ten fifteen twenty percent of their head 00:19:56.290 --> 00:19:58.380 align:start position:0% ten fifteen twenty percent of their head counts<00:19:56.710> you<00:19:57.340> know<00:19:57.370> simply<00:19:58.000> because<00:19:58.240> they 00:19:58.380 --> 00:19:58.390 align:start position:0% counts you know simply because they 00:19:58.390 --> 00:19:59.640 align:start position:0% counts you know simply because they could<00:19:58.540> go<00:19:58.690> through<00:19:58.870> and<00:19:59.020> they<00:19:59.140> can<00:19:59.290> just<00:19:59.440> take 00:19:59.640 --> 00:19:59.650 align:start position:0% could go through and they can just take 00:19:59.650 --> 00:20:02.460 align:start position:0% could go through and they can just take problems<00:20:00.130> that<00:20:00.430> are<00:20:00.520> currently<00:20:00.960> mad<00:20:01.960> rollick 00:20:02.460 --> 00:20:02.470 align:start position:0% problems that are currently mad rollick 00:20:02.470 --> 00:20:05.840 align:start position:0% problems that are currently mad rollick and<00:20:02.680> turn<00:20:03.250> them<00:20:03.460> into<00:20:03.580> consensus<00:20:04.570> problems 00:20:05.840 --> 00:20:05.850 align:start position:0% and turn them into consensus problems 00:20:05.850 --> 00:20:08.550 align:start position:0% and turn them into consensus problems just<00:20:06.850> feel<00:20:07.060> kind<00:20:07.330> of<00:20:07.390> like<00:20:07.570> where<00:20:07.780> IBM<00:20:07.990> in<00:20:08.440> the 00:20:08.550 --> 00:20:08.560 align:start position:0% just feel kind of like where IBM in the 00:20:08.560 --> 00:20:14.570 align:start position:0% just feel kind of like where IBM in the fifties<00:20:11.280> to<00:20:12.280> be 00:20:14.570 --> 00:20:14.580 align:start position:0% 00:20:14.580 --> 00:20:18.240 align:start position:0% Jeff<00:20:16.050> how<00:20:17.050> about<00:20:17.200> the<00:20:17.320> role<00:20:17.500> of<00:20:17.530> a<00:20:17.710> mist<00:20:17.950> and 00:20:18.240 --> 00:20:18.250 align:start position:0% Jeff how about the role of a mist and 00:20:18.250 --> 00:20:21.690 align:start position:0% Jeff how about the role of a mist and the<00:20:18.520> which<00:20:19.180> is<00:20:19.360> the<00:20:19.510> special<00:20:19.870> browser<00:20:20.640> do<00:20:21.640> you 00:20:21.690 --> 00:20:21.700 align:start position:0% the which is the special browser do you 00:20:21.700 --> 00:20:23.520 align:start position:0% the which is the special browser do you think<00:20:21.910> it<00:20:22.000> has<00:20:22.030> also<00:20:22.360> a<00:20:22.510> role<00:20:22.780> in<00:20:22.990> increasing 00:20:23.520 --> 00:20:23.530 align:start position:0% think it has also a role in increasing 00:20:23.530 --> 00:20:25.620 align:start position:0% think it has also a role in increasing adoption<00:20:24.010> at<00:20:24.520> the<00:20:24.550> end<00:20:24.760> user<00:20:24.910> level<00:20:25.210> me<00:20:25.450> could 00:20:25.620 --> 00:20:25.630 align:start position:0% adoption at the end user level me could 00:20:25.630 --> 00:20:27.299 align:start position:0% adoption at the end user level me could it<00:20:25.660> be<00:20:25.870> like<00:20:26.470> I<00:20:26.530> have<00:20:26.650> this<00:20:26.800> vision<00:20:27.010> we're 00:20:27.299 --> 00:20:27.309 align:start position:0% it be like I have this vision we're 00:20:27.309 --> 00:20:31.680 align:start position:0% it be like I have this vision we're assuming<00:20:28.180> miss<00:20:28.510> gets<00:20:28.800> adopted<00:20:29.970> everywhere<00:20:30.970> it 00:20:31.680 --> 00:20:31.690 align:start position:0% assuming miss gets adopted everywhere it 00:20:31.690 --> 00:20:35.750 align:start position:0% assuming miss gets adopted everywhere it could<00:20:32.020> be<00:20:32.260> like<00:20:32.410> the<00:20:32.530> next<00:20:33.540> kind<00:20:34.540> of<00:20:34.630> sass 00:20:35.750 --> 00:20:35.760 align:start position:0% could be like the next kind of sass 00:20:35.760 --> 00:20:38.490 align:start position:0% could be like the next kind of sass equivalent<00:20:36.760> in<00:20:37.000> the<00:20:37.059> sense<00:20:37.150> that<00:20:37.450> in<00:20:38.260> big 00:20:38.490 --> 00:20:38.500 align:start position:0% equivalent in the sense that in big 00:20:38.500 --> 00:20:41.100 align:start position:0% equivalent in the sense that in big companies<00:20:38.620> when<00:20:39.570> if<00:20:40.570> something<00:20:40.960> is<00:20:41.080> not 00:20:41.100 --> 00:20:41.110 align:start position:0% companies when if something is not 00:20:41.110 --> 00:20:45.090 align:start position:0% companies when if something is not available<00:20:41.470> now<00:20:43.320> employs<00:20:44.320> we<00:20:44.559> can<00:20:44.770> go<00:20:44.890> on<00:20:45.010> the 00:20:45.090 --> 00:20:45.100 align:start position:0% available now employs we can go on the 00:20:45.100 --> 00:20:46.620 align:start position:0% available now employs we can go on the web<00:20:45.220> and<00:20:45.250> sign<00:20:45.670> up<00:20:45.790> to<00:20:45.910> anything<00:20:46.150> that's<00:20:46.420> not 00:20:46.620 --> 00:20:46.630 align:start position:0% web and sign up to anything that's not 00:20:46.630 --> 00:20:48.299 align:start position:0% web and sign up to anything that's not available<00:20:46.750> and<00:20:47.290> they'll<00:20:47.860> go<00:20:48.010> and<00:20:48.160> they'll 00:20:48.299 --> 00:20:48.309 align:start position:0% available and they'll go and they'll 00:20:48.309 --> 00:20:50.850 align:start position:0% available and they'll go and they'll bypass<00:20:48.730> IT<00:20:49.030> and<00:20:49.390> be<00:20:49.570> happy<00:20:49.720> with<00:20:49.990> it<00:20:50.110> so<00:20:50.290> could 00:20:50.850 --> 00:20:50.860 align:start position:0% bypass IT and be happy with it so could 00:20:50.860 --> 00:20:53.270 align:start position:0% bypass IT and be happy with it so could miss<00:20:51.070> provide<00:20:51.490> that<00:20:51.700> kind<00:20:51.880> of<00:20:52.030> promise<00:20:52.390> where 00:20:53.270 --> 00:20:53.280 align:start position:0% miss provide that kind of promise where 00:20:53.280 --> 00:20:56.250 align:start position:0% miss provide that kind of promise where anybody<00:20:54.280> can<00:20:54.490> sign<00:20:54.730> up<00:20:54.910> and<00:20:55.150> and<00:20:55.660> conduct 00:20:56.250 --> 00:20:56.260 align:start position:0% anybody can sign up and and conduct 00:20:56.260 --> 00:20:58.320 align:start position:0% anybody can sign up and and conduct trust<00:20:56.530> based<00:20:56.710> services<00:20:57.160> without<00:20:57.370> any<00:20:57.790> any<00:20:58.210> of 00:20:58.320 --> 00:20:58.330 align:start position:0% trust based services without any any of 00:20:58.330 --> 00:21:01.440 align:start position:0% trust based services without any any of anybody's<00:20:58.809> authorization<00:20:59.730> yeah<00:21:00.730> the<00:21:00.970> facial 00:21:01.440 --> 00:21:01.450 align:start position:0% anybody's authorization yeah the facial 00:21:01.450 --> 00:21:05.549 align:start position:0% anybody's authorization yeah the facial mist<00:21:01.750> is<00:21:02.020> gonna<00:21:02.290> be<00:21:02.500> a<00:21:03.370> critical<00:21:04.350> column<00:21:05.350> in 00:21:05.549 --> 00:21:05.559 align:start position:0% mist is gonna be a critical column in 00:21:05.559 --> 00:21:07.980 align:start position:0% mist is gonna be a critical column in the<00:21:05.830> push<00:21:06.070> for<00:21:06.309> adoption<00:21:06.940> of<00:21:07.030> etherium<00:21:07.720> and<00:21:07.900> of 00:21:07.980 --> 00:21:07.990 align:start position:0% the push for adoption of etherium and of 00:21:07.990 --> 00:21:11.760 align:start position:0% the push for adoption of etherium and of the<00:21:08.140> wider<00:21:08.580> api's<00:21:10.230> that<00:21:11.230> are<00:21:11.350> needed<00:21:11.500> to 00:21:11.760 --> 00:21:11.770 align:start position:0% the wider api's that are needed to 00:21:11.770 --> 00:21:14.970 align:start position:0% the wider api's that are needed to really<00:21:11.980> sort<00:21:12.250> of<00:21:12.720> maximize<00:21:13.720> the<00:21:14.559> value<00:21:14.679> of 00:21:14.970 --> 00:21:14.980 align:start position:0% really sort of maximize the value of 00:21:14.980 --> 00:21:17.970 align:start position:0% really sort of maximize the value of ethereum<00:21:15.600> and<00:21:16.600> it's<00:21:16.750> I<00:21:17.050> mean<00:21:17.170> you<00:21:17.230> know<00:21:17.350> it's 00:21:17.970 --> 00:21:17.980 align:start position:0% ethereum and it's I mean you know it's 00:21:17.980 --> 00:21:20.280 align:start position:0% ethereum and it's I mean you know it's not<00:21:18.130> just<00:21:18.190> missed<00:21:18.610> there's<00:21:18.940> also<00:21:19.290> various 00:21:20.280 --> 00:21:20.290 align:start position:0% not just missed there's also various 00:21:20.290 --> 00:21:23.400 align:start position:0% not just missed there's also various other<00:21:21.360> projects<00:21:22.360> out<00:21:22.480> there<00:21:22.510> that<00:21:22.900> are<00:21:23.080> trying 00:21:23.400 --> 00:21:23.410 align:start position:0% other projects out there that are trying 00:21:23.410 --> 00:21:26.910 align:start position:0% other projects out there that are trying to<00:21:23.559> bring<00:21:23.800> these<00:21:24.400> api<00:21:24.880> is<00:21:25.030> into<00:21:25.830> you<00:21:26.830> know 00:21:26.910 --> 00:21:26.920 align:start position:0% to bring these api is into you know 00:21:26.920 --> 00:21:30.360 align:start position:0% to bring these api is into you know user-focused<00:21:27.580> gateway<00:21:29.070> beyond<00:21:30.070> the<00:21:30.190> death 00:21:30.360 --> 00:21:30.370 align:start position:0% user-focused gateway beyond the death 00:21:30.370 --> 00:21:32.790 align:start position:0% user-focused gateway beyond the death grants<00:21:30.820> or<00:21:31.000> private<00:21:31.720> projects<00:21:32.170> yeah<00:21:32.410> i<00:21:32.440> mean<00:21:32.530> i 00:21:32.790 --> 00:21:32.800 align:start position:0% grants or private projects yeah i mean i 00:21:32.800 --> 00:21:37.320 align:start position:0% grants or private projects yeah i mean i think<00:21:32.860> the<00:21:33.190> concept<00:21:33.700> behind<00:21:33.790> it<00:21:34.120> is<00:21:34.300> self<00:21:36.330> like 00:21:37.320 --> 00:21:37.330 align:start position:0% think the concept behind it is self like 00:21:37.330 --> 00:21:39.000 align:start position:0% think the concept behind it is self like having<00:21:37.630> the<00:21:37.750> self<00:21:37.990> ownership<00:21:38.320> and<00:21:38.710> self 00:21:39.000 --> 00:21:39.010 align:start position:0% having the self ownership and self 00:21:39.010 --> 00:21:42.180 align:start position:0% having the self ownership and self authority<00:21:39.580> to<00:21:39.760> to<00:21:40.510> get<00:21:40.630> on<00:21:40.780> a<00:21:40.809> service<00:21:41.320> that 00:21:42.180 --> 00:21:42.190 align:start position:0% authority to to get on a service that 00:21:42.190 --> 00:21:44.400 align:start position:0% authority to to get on a service that has<00:21:42.940> a<00:21:43.000> strut<00:21:43.360> that<00:21:43.600> has<00:21:43.870> a<00:21:43.900> trust-based 00:21:44.400 --> 00:21:44.410 align:start position:0% has a strut that has a trust-based 00:21:44.410 --> 00:21:47.130 align:start position:0% has a strut that has a trust-based component<00:21:45.030> without<00:21:46.030> asking<00:21:46.480> anybody's 00:21:47.130 --> 00:21:47.140 align:start position:0% component without asking anybody's 00:21:47.140 --> 00:21:49.620 align:start position:0% component without asking anybody's authorization<00:21:47.830> without<00:21:48.300> asking<00:21:49.300> the<00:21:49.390> IT 00:21:49.620 --> 00:21:49.630 align:start position:0% authorization without asking the IT 00:21:49.630 --> 00:21:52.260 align:start position:0% authorization without asking the IT department<00:21:49.660> for<00:21:50.410> for<00:21:50.800> something<00:21:51.120> that's<00:21:52.120> the 00:21:52.260 --> 00:21:52.270 align:start position:0% department for for something that's the 00:21:52.270 --> 00:21:55.770 align:start position:0% department for for something that's the promise<00:21:52.480> i<00:21:52.690> think<00:21:53.250> if<00:21:54.250> you<00:21:54.520> read<00:21:54.910> if<00:21:55.300> you<00:21:55.600> read 00:21:55.770 --> 00:21:55.780 align:start position:0% promise i think if you read if you read 00:21:55.780 --> 00:21:57.840 align:start position:0% promise i think if you read if you read a<00:21:55.809> i<00:21:56.470> think<00:21:56.920> it<00:21:57.010> was<00:21:57.100> Eric<00:21:57.340> Raymond's<00:21:57.670> book 00:21:57.840 --> 00:21:57.850 align:start position:0% a i think it was Eric Raymond's book 00:21:57.850 --> 00:22:01.290 align:start position:0% a i think it was Eric Raymond's book again<00:21:58.150> what<00:21:58.990> how<00:21:59.110> little<00:21:59.590> Linux<00:21:59.890> become<00:22:00.190> so<00:22:00.400> so 00:22:01.290 --> 00:22:01.300 align:start position:0% again what how little Linux become so so 00:22:01.300 --> 00:22:06.870 align:start position:0% again what how little Linux become so so incredibly<00:22:01.960> popular<00:22:04.020> it<00:22:05.309> was<00:22:06.309> called<00:22:06.520> under 00:22:06.870 --> 00:22:06.880 align:start position:0% incredibly popular it was called under 00:22:06.880 --> 00:22:10.169 align:start position:0% incredibly popular it was called under the<00:22:07.000> radar<00:22:07.210> and<00:22:08.250> that<00:22:09.250> was<00:22:09.400> it<00:22:09.580> right<00:22:09.760> the 00:22:10.169 --> 00:22:10.179 align:start position:0% the radar and that was it right the 00:22:10.179 --> 00:22:14.460 align:start position:0% the radar and that was it right the Linux<00:22:10.690> was<00:22:10.870> too<00:22:11.080> easy<00:22:11.460> to<00:22:12.460> not<00:22:12.700> use<00:22:12.970> as<00:22:13.240> a<00:22:13.750> as<00:22:14.170> a 00:22:14.460 --> 00:22:14.470 align:start position:0% Linux was too easy to not use as a as a 00:22:14.470 --> 00:22:17.700 align:start position:0% Linux was too easy to not use as a as a sysadmin<00:22:14.980> in<00:22:15.490> a<00:22:15.700> big<00:22:16.540> corporation<00:22:16.780> if<00:22:17.410> you 00:22:17.700 --> 00:22:17.710 align:start position:0% sysadmin in a big corporation if you 00:22:17.710 --> 00:22:20.340 align:start position:0% sysadmin in a big corporation if you used<00:22:18.010> like<00:22:18.309> if<00:22:18.670> you<00:22:18.820> if<00:22:19.240> you<00:22:19.360> had<00:22:19.480> a<00:22:19.510> niggling 00:22:20.340 --> 00:22:20.350 align:start position:0% used like if you if you had a niggling 00:22:20.350 --> 00:22:21.930 align:start position:0% used like if you if you had a niggling problem<00:22:20.800> with<00:22:20.950> your<00:22:21.160> I<00:22:21.220> your<00:22:21.790> IT 00:22:21.930 --> 00:22:21.940 align:start position:0% problem with your I your IT 00:22:21.940 --> 00:22:23.640 align:start position:0% problem with your I your IT infrastructure<00:22:22.540> then<00:22:23.230> you<00:22:23.350> could<00:22:23.530> either 00:22:23.640 --> 00:22:23.650 align:start position:0% infrastructure then you could either 00:22:23.650 --> 00:22:26.790 align:start position:0% infrastructure then you could either fill<00:22:24.130> out<00:22:24.280> however<00:22:24.760> many<00:22:24.970> forms<00:22:25.480> pray<00:22:25.929> ET<00:22:26.260> home 00:22:26.790 --> 00:22:26.800 align:start position:0% fill out however many forms pray ET home 00:22:26.800 --> 00:22:29.370 align:start position:0% fill out however many forms pray ET home preity<00:22:27.220> old<00:22:27.550> garden<00:22:28.000> and<00:22:28.240> an<00:22:28.480> MPEG<00:22:29.140> your 00:22:29.370 --> 00:22:29.380 align:start position:0% preity old garden and an MPEG your 00:22:29.380 --> 00:22:31.890 align:start position:0% preity old garden and an MPEG your manager<00:22:29.860> to<00:22:30.130> to<00:22:30.700> sign<00:22:30.910> off<00:22:31.120> an<00:22:31.330> additional 00:22:31.890 --> 00:22:31.900 align:start position:0% manager to to sign off an additional 00:22:31.900 --> 00:22:35.250 align:start position:0% manager to to sign off an additional operating<00:22:32.200> system<00:22:32.820> license<00:22:33.820> and<00:22:34.720> whatever<00:22:35.020> I 00:22:35.250 --> 00:22:35.260 align:start position:0% operating system license and whatever I 00:22:35.260 --> 00:22:36.620 align:start position:0% operating system license and whatever I don't<00:22:35.410> know<00:22:35.590> hardware<00:22:36.070> that<00:22:36.160> would<00:22:36.310> require 00:22:36.620 --> 00:22:36.630 align:start position:0% don't know hardware that would require 00:22:36.630 --> 00:22:39.750 align:start position:0% don't know hardware that would require or<00:22:37.630> you<00:22:37.960> would<00:22:38.110> just<00:22:38.350> find<00:22:38.590> some<00:22:38.830> all<00:22:38.980> dead<00:22:39.340> box 00:22:39.750 --> 00:22:39.760 align:start position:0% or you would just find some all dead box 00:22:39.760 --> 00:22:42.240 align:start position:0% or you would just find some all dead box in<00:22:40.120> the<00:22:40.210> corner<00:22:40.360> and<00:22:40.690> install<00:22:41.110> slack<00:22:41.920> wire<00:22:42.130> on 00:22:42.240 --> 00:22:42.250 align:start position:0% in the corner and install slack wire on 00:22:42.250 --> 00:22:45.270 align:start position:0% in the corner and install slack wire on it<00:22:42.370> and<00:22:42.990> that's<00:22:43.990> why<00:22:44.290> linux<00:22:44.680> in<00:22:44.980> the 00:22:45.270 --> 00:22:45.280 align:start position:0% it and that's why linux in the 00:22:45.280 --> 00:22:47.730 align:start position:0% it and that's why linux in the enterprise<00:22:45.700> is<00:22:45.730> a<00:22:45.910> thing<00:22:46.240> is<00:22:46.660> because<00:22:46.960> the<00:22:47.500> IT 00:22:47.730 --> 00:22:47.740 align:start position:0% enterprise is a thing is because the IT 00:22:47.740 --> 00:22:51.270 align:start position:0% enterprise is a thing is because the IT guys<00:22:48.100> didn't<00:22:48.610> have<00:22:48.880> to<00:22:48.910> ask<00:22:49.240> permission<00:22:50.280> maybe 00:22:51.270 --> 00:22:51.280 align:start position:0% guys didn't have to ask permission maybe 00:22:51.280 --> 00:22:56.420 align:start position:0% guys didn't have to ask permission maybe we<00:22:51.490> should<00:22:51.520> give<00:22:51.850> away<00:22:52.060> etherium<00:22:52.540> for<00:22:52.750> free 00:22:56.420 --> 00:22:56.430 align:start position:0% 00:22:56.430 --> 00:22:58.590 align:start position:0% switching<00:22:57.430> gears<00:22:57.460> a<00:22:57.730> little<00:22:57.820> bit<00:22:58.030> and<00:22:58.300> really 00:22:58.590 --> 00:22:58.600 align:start position:0% switching gears a little bit and really 00:22:58.600 --> 00:23:01.980 align:start position:0% switching gears a little bit and really curious<00:22:58.990> about<00:22:59.140> your<00:22:59.500> thoughts<00:22:59.530> on<00:23:00.660> IOT<00:23:01.660> as<00:23:01.930> a 00:23:01.980 --> 00:23:01.990 align:start position:0% curious about your thoughts on IOT as a 00:23:01.990 --> 00:23:05.700 align:start position:0% curious about your thoughts on IOT as a use<00:23:02.710> case<00:23:02.920> as<00:23:03.160> a<00:23:03.190> driver<00:23:03.640> for<00:23:04.710> etherium 00:23:05.700 --> 00:23:05.710 align:start position:0% use case as a driver for etherium 00:23:05.710 --> 00:23:09.780 align:start position:0% use case as a driver for etherium adoption<00:23:06.220> I<00:23:07.380> been<00:23:08.380> surprised<00:23:09.010> to<00:23:09.280> hear<00:23:09.490> lots 00:23:09.780 --> 00:23:09.790 align:start position:0% adoption I been surprised to hear lots 00:23:09.790 --> 00:23:11.310 align:start position:0% adoption I been surprised to hear lots of<00:23:10.030> different<00:23:10.360> opinions<00:23:10.570> on<00:23:10.930> that<00:23:11.080> I<00:23:11.140> think 00:23:11.310 --> 00:23:11.320 align:start position:0% of different opinions on that I think 00:23:11.320 --> 00:23:16.110 align:start position:0% of different opinions on that I think it's<00:23:11.680> a<00:23:11.800> no-brainer<00:23:11.980> but<00:23:14.430> many<00:23:15.430> people<00:23:15.550> still 00:23:16.110 --> 00:23:16.120 align:start position:0% it's a no-brainer but many people still 00:23:16.120 --> 00:23:18.320 align:start position:0% it's a no-brainer but many people still think<00:23:16.300> that<00:23:16.630> that<00:23:17.530> more<00:23:18.010> traditional 00:23:18.320 --> 00:23:18.330 align:start position:0% think that that more traditional 00:23:18.330 --> 00:23:20.940 align:start position:0% think that that more traditional architectures<00:23:19.330> maybe<00:23:19.840> they<00:23:20.050> have<00:23:20.140> vested 00:23:20.940 --> 00:23:20.950 align:start position:0% architectures maybe they have vested 00:23:20.950 --> 00:23:22.800 align:start position:0% architectures maybe they have vested interests<00:23:21.610> but<00:23:21.760> more<00:23:22.270> traditional 00:23:22.800 --> 00:23:22.810 align:start position:0% interests but more traditional 00:23:22.810 --> 00:23:24.920 align:start position:0% interests but more traditional architectures<00:23:23.380> would<00:23:23.560> be<00:23:23.680> better<00:23:23.860> for<00:23:23.980> IOT 00:23:24.920 --> 00:23:24.930 align:start position:0% architectures would be better for IOT 00:23:24.930 --> 00:23:26.820 align:start position:0% architectures would be better for IOT what<00:23:25.930> do<00:23:25.990> you<00:23:26.020> think<00:23:26.080> some<00:23:26.380> of<00:23:26.410> the<00:23:26.590> benefits 00:23:26.820 --> 00:23:26.830 align:start position:0% what do you think some of the benefits 00:23:26.830 --> 00:23:30.060 align:start position:0% what do you think some of the benefits of<00:23:27.250> etherium<00:23:27.760> would<00:23:28.090> be<00:23:28.270> 4i<00:23:28.600> o<00:23:28.840> different<00:23:29.650> IOT 00:23:30.060 --> 00:23:30.070 align:start position:0% of etherium would be 4i o different IOT 00:23:30.070 --> 00:23:34.650 align:start position:0% of etherium would be 4i o different IOT use<00:23:30.490> cases<00:23:30.760> so<00:23:31.630> I<00:23:31.990> mean<00:23:33.300> in<00:23:34.300> a<00:23:34.450> nutshell 00:23:34.650 --> 00:23:34.660 align:start position:0% use cases so I mean in a nutshell 00:23:34.660 --> 00:23:39.450 align:start position:0% use cases so I mean in a nutshell they're<00:23:34.990> idiots<00:23:36.450> no-brainer<00:23:37.770> I<00:23:38.770> mean<00:23:39.160> you 00:23:39.450 --> 00:23:39.460 align:start position:0% they're idiots no-brainer I mean you 00:23:39.460 --> 00:23:41.790 align:start position:0% they're idiots no-brainer I mean you know<00:23:39.580> when<00:23:39.850> when<00:23:40.150> you<00:23:40.270> see<00:23:40.540> you<00:23:41.320> know<00:23:41.440> you<00:23:41.500> see 00:23:41.790 --> 00:23:41.800 align:start position:0% know when when you see you know you see 00:23:41.800 --> 00:23:45.210 align:start position:0% know when when you see you know you see I<00:23:42.070> don't<00:23:42.280> know<00:23:42.370> Kristoff<00:23:42.910> a<00:23:43.870> sort<00:23:44.260> of<00:23:44.320> you<00:23:45.190> know 00:23:45.210 --> 00:23:45.220 align:start position:0% I don't know Kristoff a sort of you know 00:23:45.220 --> 00:23:48.900 align:start position:0% I don't know Kristoff a sort of you know talking<00:23:45.550> vision<00:23:46.150> of<00:23:46.740> lots<00:23:47.740> and<00:23:48.160> resources<00:23:48.760> in 00:23:48.900 --> 00:23:48.910 align:start position:0% talking vision of lots and resources in 00:23:48.910 --> 00:23:50.190 align:start position:0% talking vision of lots and resources in general<00:23:49.330> being<00:23:49.480> controlled<00:23:49.990> in<00:23:50.140> a 00:23:50.190 --> 00:23:50.200 align:start position:0% general being controlled in a 00:23:50.200 --> 00:23:52.020 align:start position:0% general being controlled in a decentralized<00:23:50.500> fashion<00:23:51.220> and<00:23:51.370> then<00:23:51.760> you<00:23:51.850> see 00:23:52.020 --> 00:23:52.030 align:start position:0% decentralized fashion and then you see 00:23:52.030 --> 00:23:54.630 align:start position:0% decentralized fashion and then you see on<00:23:52.690> the<00:23:52.810> other<00:23:53.080> end<00:23:53.260> of<00:23:53.380> the<00:23:53.470> scale<00:23:53.560> IBM<00:23:54.250> saying 00:23:54.630 --> 00:23:54.640 align:start position:0% on the other end of the scale IBM saying 00:23:54.640 --> 00:23:57.330 align:start position:0% on the other end of the scale IBM saying exactly<00:23:55.060> the<00:23:55.300> same<00:23:55.420> thing<00:23:55.740> then<00:23:56.740> you<00:23:57.100> got<00:23:57.310> to 00:23:57.330 --> 00:23:57.340 align:start position:0% exactly the same thing then you got to 00:23:57.340 --> 00:23:58.440 align:start position:0% exactly the same thing then you got to start<00:23:57.640> thinking<00:23:57.700> actually<00:23:58.120> there's<00:23:58.420> probably 00:23:58.440 --> 00:23:58.450 align:start position:0% start thinking actually there's probably 00:23:58.450 --> 00:24:02.280 align:start position:0% start thinking actually there's probably something<00:23:59.080> in<00:23:59.350> it<00:24:00.150> you<00:24:01.150> know<00:24:01.180> it's<00:24:01.870> the<00:24:01.990> only 00:24:02.280 --> 00:24:02.290 align:start position:0% something in it you know it's the only 00:24:02.290 --> 00:24:04.590 align:start position:0% something in it you know it's the only way<00:24:02.380> to<00:24:02.440> scale<00:24:02.830> you<00:24:03.610> know<00:24:03.730> if<00:24:03.790> you<00:24:03.910> talk<00:24:04.120> to<00:24:04.240> IBM 00:24:04.590 --> 00:24:04.600 align:start position:0% way to scale you know if you talk to IBM 00:24:04.600 --> 00:24:06.030 align:start position:0% way to scale you know if you talk to IBM the<00:24:04.900> first<00:24:05.260> thing<00:24:05.380> they<00:24:05.440> say<00:24:05.560> is<00:24:05.590> well<00:24:05.830> you 00:24:06.030 --> 00:24:06.040 align:start position:0% the first thing they say is well you 00:24:06.040 --> 00:24:07.740 align:start position:0% the first thing they say is well you know<00:24:06.160> we<00:24:06.340> don't<00:24:06.520> we<00:24:06.850> don't<00:24:07.060> want<00:24:07.240> to<00:24:07.420> run<00:24:07.600> the 00:24:07.740 --> 00:24:07.750 align:start position:0% know we don't we don't want to run the 00:24:07.750 --> 00:24:09.420 align:start position:0% know we don't we don't want to run the server<00:24:07.960> infrastructure<00:24:08.560> there's<00:24:08.860> necessary 00:24:09.420 --> 00:24:09.430 align:start position:0% server infrastructure there's necessary 00:24:09.430 --> 00:24:12.450 align:start position:0% server infrastructure there's necessary to<00:24:10.030> drive<00:24:10.300> this<00:24:10.660> amount<00:24:11.050> of<00:24:11.260> stuff<00:24:12.130> we<00:24:12.310> don't 00:24:12.450 --> 00:24:12.460 align:start position:0% to drive this amount of stuff we don't 00:24:12.460 --> 00:24:14.550 align:start position:0% to drive this amount of stuff we don't want<00:24:12.700> to<00:24:12.820> have<00:24:13.030> the<00:24:13.150> legal<00:24:13.420> department<00:24:14.020> draw 00:24:14.550 --> 00:24:14.560 align:start position:0% want to have the legal department draw 00:24:14.560 --> 00:24:16.500 align:start position:0% want to have the legal department draw up<00:24:14.620> contracts<00:24:15.160> for<00:24:15.340> all<00:24:15.520> the<00:24:15.730> various<00:24:16.090> parties 00:24:16.500 --> 00:24:16.510 align:start position:0% up contracts for all the various parties 00:24:16.510 --> 00:24:18.120 align:start position:0% up contracts for all the various parties to<00:24:16.750> have<00:24:16.960> to<00:24:17.140> coordinate<00:24:17.290> with<00:24:17.680> each<00:24:17.830> other 00:24:18.120 --> 00:24:18.130 align:start position:0% to have to coordinate with each other 00:24:18.130 --> 00:24:19.980 align:start position:0% to have to coordinate with each other over<00:24:18.310> things<00:24:18.910> like<00:24:19.030> you<00:24:19.240> know<00:24:19.270> data<00:24:19.600> privacy 00:24:19.980 --> 00:24:19.990 align:start position:0% over things like you know data privacy 00:24:19.990 --> 00:24:22.260 align:start position:0% over things like you know data privacy we<00:24:20.470> just<00:24:21.100> don't<00:24:21.340> want<00:24:21.490> to<00:24:21.580> do<00:24:21.670> that<00:24:21.700> that's<00:24:22.060> not 00:24:22.260 --> 00:24:22.270 align:start position:0% we just don't want to do that that's not 00:24:22.270 --> 00:24:23.910 align:start position:0% we just don't want to do that that's not our<00:24:22.450> core<00:24:22.630> competency<00:24:23.170> it's<00:24:23.320> not<00:24:23.530> work<00:24:23.740> that 00:24:23.910 --> 00:24:23.920 align:start position:0% our core competency it's not work that 00:24:23.920 --> 00:24:25.890 align:start position:0% our core competency it's not work that anyone<00:24:24.220> enjoys<00:24:24.550> there<00:24:25.450> has<00:24:25.600> to<00:24:25.780> be<00:24:25.810> a 00:24:25.890 --> 00:24:25.900 align:start position:0% anyone enjoys there has to be a 00:24:25.900 --> 00:24:27.540 align:start position:0% anyone enjoys there has to be a technological<00:24:26.560> solution<00:24:26.680> and<00:24:27.100> they<00:24:27.160> found<00:24:27.400> it 00:24:27.540 --> 00:24:27.550 align:start position:0% technological solution and they found it 00:24:27.550 --> 00:24:32.700 align:start position:0% technological solution and they found it in<00:24:29.610> four<00:24:30.610> years<00:24:30.760> i<00:24:31.000> use<00:24:31.120> induced<00:24:31.870> job<00:24:32.110> by<00:24:32.290> IOT 00:24:32.700 --> 00:24:32.710 align:start position:0% in four years i use induced job by IOT 00:24:32.710 --> 00:24:35.070 align:start position:0% in four years i use induced job by IOT in<00:24:32.770> a<00:24:32.890> computer<00:24:33.310> security<00:24:33.760> complex<00:24:34.090> as<00:24:34.510> the 00:24:35.070 --> 00:24:35.080 align:start position:0% in a computer security complex as the 00:24:35.080 --> 00:24:36.780 align:start position:0% in a computer security complex as the totally<00:24:35.500> insecure<00:24:35.800> internet<00:24:36.370> of<00:24:36.460> totally 00:24:36.780 --> 00:24:36.790 align:start position:0% totally insecure internet of totally 00:24:36.790 --> 00:24:37.890 align:start position:0% totally insecure internet of totally unsecure<00:24:37.030> things 00:24:37.890 --> 00:24:37.900 align:start position:0% unsecure things 00:24:37.900 --> 00:24:39.990 align:start position:0% unsecure things and<00:24:37.990> the<00:24:38.920> notion<00:24:39.220> that<00:24:39.250> kind<00:24:39.670> of<00:24:39.760> smart 00:24:39.990 --> 00:24:40.000 align:start position:0% and the notion that kind of smart 00:24:40.000 --> 00:24:41.340 align:start position:0% and the notion that kind of smart contracts<00:24:40.540> provide<00:24:40.810> you<00:24:40.930> a<00:24:40.960> meaningful 00:24:41.340 --> 00:24:41.350 align:start position:0% contracts provide you a meaningful 00:24:41.350 --> 00:24:44.490 align:start position:0% contracts provide you a meaningful alternative<00:24:42.070> to<00:24:42.400> you<00:24:43.150> know<00:24:43.270> tens<00:24:43.870> of<00:24:44.080> millions 00:24:44.490 --> 00:24:44.500 align:start position:0% alternative to you know tens of millions 00:24:44.500 --> 00:24:46.650 align:start position:0% alternative to you know tens of millions or<00:24:44.770> billions<00:24:45.160> of<00:24:45.520> tiny<00:24:45.760> little<00:24:46.060> hackable 00:24:46.650 --> 00:24:46.660 align:start position:0% or billions of tiny little hackable 00:24:46.660 --> 00:24:48.990 align:start position:0% or billions of tiny little hackable boxes<00:24:47.200> that<00:24:48.070> could<00:24:48.250> give<00:24:48.430> hackers<00:24:48.640> the 00:24:48.990 --> 00:24:49.000 align:start position:0% boxes that could give hackers the 00:24:49.000 --> 00:24:51.300 align:start position:0% boxes that could give hackers the ability<00:24:49.360> to<00:24:49.480> turn<00:24:49.630> off<00:24:49.810> entire<00:24:50.080> cities<00:24:50.530> you 00:24:51.300 --> 00:24:51.310 align:start position:0% ability to turn off entire cities you 00:24:51.310 --> 00:24:53.010 align:start position:0% ability to turn off entire cities you know<00:24:51.400> it<00:24:51.550> seems<00:24:51.730> like<00:24:51.970> there's<00:24:52.180> just<00:24:52.450> no<00:24:52.780> way 00:24:53.010 --> 00:24:53.020 align:start position:0% know it seems like there's just no way 00:24:53.020 --> 00:24:54.720 align:start position:0% know it seems like there's just no way of<00:24:53.140> building<00:24:53.320> a<00:24:53.530> security<00:24:54.010> model<00:24:54.280> that<00:24:54.430> isn't 00:24:54.720 --> 00:24:54.730 align:start position:0% of building a security model that isn't 00:24:54.730 --> 00:24:58.760 align:start position:0% of building a security model that isn't smart<00:24:54.940> contracts<00:24:56.010> for<00:24:57.010> IOT<00:24:57.460> I<00:24:57.730> mean<00:24:57.880> I<00:24:57.940> just 00:24:58.760 --> 00:24:58.770 align:start position:0% smart contracts for IOT I mean I just 00:24:58.770 --> 00:25:01.050 align:start position:0% smart contracts for IOT I mean I just there<00:24:59.770> seems<00:25:00.040> to<00:25:00.100> be<00:25:00.220> no<00:25:00.340> other<00:25:00.490> path<00:25:00.670> forward 00:25:01.050 --> 00:25:01.060 align:start position:0% there seems to be no other path forward 00:25:01.060 --> 00:25:04.950 align:start position:0% there seems to be no other path forward and<00:25:01.770> so<00:25:02.770> a<00:25:02.800> bit<00:25:03.130> like<00:25:03.280> canna<00:25:03.670> Linux<00:25:04.480> gets<00:25:04.720> mass 00:25:04.950 --> 00:25:04.960 align:start position:0% and so a bit like canna Linux gets mass 00:25:04.960 --> 00:25:07.290 align:start position:0% and so a bit like canna Linux gets mass adoption<00:25:05.140> through<00:25:05.650> Android<00:25:06.190> devices<00:25:06.490> I<00:25:06.880> think 00:25:07.290 --> 00:25:07.300 align:start position:0% adoption through Android devices I think 00:25:07.300 --> 00:25:08.790 align:start position:0% adoption through Android devices I think that<00:25:07.450> might<00:25:07.630> be<00:25:07.660> the<00:25:07.780> parallel<00:25:08.230> to<00:25:08.380> a<00:25:08.440> theorem 00:25:08.790 --> 00:25:08.800 align:start position:0% that might be the parallel to a theorem 00:25:08.800 --> 00:25:13.380 align:start position:0% that might be the parallel to a theorem in<00:25:08.890> IOT<00:25:10.470> IOT<00:25:11.470> is<00:25:11.590> a<00:25:11.620> terrifying<00:25:12.010> future<00:25:12.460> in<00:25:13.240> a 00:25:13.380 --> 00:25:13.390 align:start position:0% in IOT IOT is a terrifying future in a 00:25:13.390 --> 00:25:16.640 align:start position:0% in IOT IOT is a terrifying future in a in<00:25:13.780> a<00:25:13.900> centralized<00:25:14.410> context<00:25:15.100> where<00:25:15.280> for<00:25:15.820> sure 00:25:16.640 --> 00:25:16.650 align:start position:0% in a centralized context where for sure 00:25:16.650 --> 00:25:18.900 align:start position:0% in a centralized context where for sure should<00:25:17.650> we<00:25:17.800> open<00:25:17.830> it<00:25:18.160> up<00:25:18.310> to<00:25:18.340> some<00:25:18.700> questions 00:25:18.900 --> 00:25:18.910 align:start position:0% should we open it up to some questions 00:25:18.910 --> 00:25:25.380 align:start position:0% should we open it up to some questions so<00:25:21.360> how<00:25:22.360> much<00:25:22.480> more<00:25:22.690> time<00:25:22.720> do<00:25:22.960> we<00:25:23.050> have<00:25:24.390> what's 00:25:25.380 --> 00:25:25.390 align:start position:0% so how much more time do we have what's 00:25:25.390 --> 00:25:27.270 align:start position:0% so how much more time do we have what's the<00:25:25.510> time<00:25:25.690> frame<00:25:25.720> I<00:25:26.110> think<00:25:26.770> there's<00:25:26.920> questions 00:25:27.270 --> 00:25:27.280 align:start position:0% the time frame I think there's questions 00:25:27.280 --> 00:25:35.910 align:start position:0% the time frame I think there's questions there 00:25:35.910 --> 00:25:35.920 align:start position:0% 00:25:35.920 --> 00:25:40.080 align:start position:0% hello<00:25:36.790> um<00:25:37.740> so<00:25:38.740> I'm<00:25:38.890> really<00:25:39.070> excited<00:25:39.160> about<00:25:39.760> the 00:25:40.080 --> 00:25:40.090 align:start position:0% hello um so I'm really excited about the 00:25:40.090 --> 00:25:43.890 align:start position:0% hello um so I'm really excited about the potential<00:25:40.420> for<00:25:40.780> erm<00:25:41.410> to<00:25:41.830> form<00:25:42.780> sort<00:25:43.780> of<00:25:43.840> the 00:25:43.890 --> 00:25:43.900 align:start position:0% potential for erm to form sort of the 00:25:43.900 --> 00:25:46.110 align:start position:0% potential for erm to form sort of the bedrock<00:25:44.260> of<00:25:44.290> a<00:25:44.500> new<00:25:44.680> socio-economic<00:25:45.120> paradigm 00:25:46.110 --> 00:25:46.120 align:start position:0% bedrock of a new socio-economic paradigm 00:25:46.120 --> 00:25:50.760 align:start position:0% bedrock of a new socio-economic paradigm um<00:25:47.280> however<00:25:48.280> I'm<00:25:48.580> also<00:25:48.640> a<00:25:48.880> non<00:25:49.300> developer<00:25:49.870> I<00:25:50.080> am 00:25:50.760 --> 00:25:50.770 align:start position:0% um however I'm also a non developer I am 00:25:50.770 --> 00:25:53.640 align:start position:0% um however I'm also a non developer I am NOT<00:25:51.340> a<00:25:51.370> dude<00:25:51.640> and<00:25:51.880> I<00:25:52.870> don't<00:25:53.140> work<00:25:53.260> for<00:25:53.320> a<00:25:53.530> bank 00:25:53.640 --> 00:25:53.650 align:start position:0% NOT a dude and I don't work for a bank 00:25:53.650 --> 00:25:57.450 align:start position:0% NOT a dude and I don't work for a bank so<00:25:54.520> I<00:25:55.020> kind<00:25:56.020> of<00:25:56.110> can't<00:25:56.920> help<00:25:57.160> but<00:25:57.250> get<00:25:57.340> the 00:25:57.450 --> 00:25:57.460 align:start position:0% so I kind of can't help but get the 00:25:57.460 --> 00:25:59.400 align:start position:0% so I kind of can't help but get the feeling<00:25:57.820> that<00:25:57.970> you're<00:25:58.180> baking<00:25:58.690> a<00:25:58.780> fatal<00:25:59.140> flaw 00:25:59.400 --> 00:25:59.410 align:start position:0% feeling that you're baking a fatal flaw 00:25:59.410 --> 00:26:02.490 align:start position:0% feeling that you're baking a fatal flaw into<00:26:00.010> your<00:26:00.160> system<00:26:00.580> at<00:26:00.820> its<00:26:01.090> inception<00:26:01.500> by 00:26:02.490 --> 00:26:02.500 align:start position:0% into your system at its inception by 00:26:02.500 --> 00:26:04.950 align:start position:0% into your system at its inception by focusing<00:26:03.160> so<00:26:03.790> much<00:26:03.820> on<00:26:04.060> such<00:26:04.630> a<00:26:04.660> narrow 00:26:04.950 --> 00:26:04.960 align:start position:0% focusing so much on such a narrow 00:26:04.960 --> 00:26:07.590 align:start position:0% focusing so much on such a narrow demographic<00:26:05.290> and<00:26:06.070> so<00:26:06.670> I'm<00:26:06.910> wondering<00:26:07.120> what 00:26:07.590 --> 00:26:07.600 align:start position:0% demographic and so I'm wondering what 00:26:07.600 --> 00:26:09.380 align:start position:0% demographic and so I'm wondering what sort<00:26:07.780> of<00:26:07.930> outreach<00:26:08.620> and<00:26:09.010> engagement 00:26:09.380 --> 00:26:09.390 align:start position:0% sort of outreach and engagement 00:26:09.390 --> 00:26:13.770 align:start position:0% sort of outreach and engagement activities<00:26:10.390> you<00:26:10.780> have<00:26:11.050> to<00:26:11.710> try<00:26:12.520> to<00:26:12.780> encourage 00:26:13.770 --> 00:26:13.780 align:start position:0% activities you have to try to encourage 00:26:13.780 --> 00:26:16.200 align:start position:0% activities you have to try to encourage demand<00:26:14.410> rather<00:26:14.680> than<00:26:14.950> focus<00:26:15.430> solely<00:26:15.700> on<00:26:15.820> the 00:26:16.200 --> 00:26:16.210 align:start position:0% demand rather than focus solely on the 00:26:16.210 --> 00:26:22.830 align:start position:0% demand rather than focus solely on the supply<00:26:16.540> of<00:26:16.570> this<00:26:16.900> new<00:26:17.110> system<00:26:21.690> that's<00:26:22.690> a<00:26:22.810> very 00:26:22.830 --> 00:26:22.840 align:start position:0% supply of this new system that's a very 00:26:22.840 --> 00:26:28.710 align:start position:0% supply of this new system that's a very good<00:26:23.050> question 00:26:28.710 --> 00:26:28.720 align:start position:0% 00:26:28.720 --> 00:26:31.149 align:start position:0% this<00:26:29.720> ties<00:26:29.929> back<00:26:29.960> to<00:26:30.200> your<00:26:30.649> question<00:26:30.860> about 00:26:31.149 --> 00:26:31.159 align:start position:0% this ties back to your question about 00:26:31.159 --> 00:26:35.169 align:start position:0% this ties back to your question about brand<00:26:31.990> so<00:26:32.990> I<00:26:33.019> think<00:26:33.169> ya<00:26:33.470> mean<00:26:33.649> it<00:26:33.769> is<00:26:34.070> a<00:26:34.179> potion 00:26:35.169 --> 00:26:35.179 align:start position:0% brand so I think ya mean it is a potion 00:26:35.179 --> 00:26:39.669 align:start position:0% brand so I think ya mean it is a potion of<00:26:35.509> Paul<00:26:36.279> and<00:26:37.809> I<00:26:38.809> can<00:26:39.019> I<00:26:39.169> don't<00:26:39.350> speak<00:26:39.590> on 00:26:39.669 --> 00:26:39.679 align:start position:0% of Paul and I can I don't speak on 00:26:39.679 --> 00:26:41.259 align:start position:0% of Paul and I can I don't speak on behalf<00:26:39.860> of<00:26:40.190> the<00:26:40.309> theorem<00:26:40.610> necessary<00:26:41.090> but<00:26:41.210> I 00:26:41.259 --> 00:26:41.269 align:start position:0% behalf of the theorem necessary but I 00:26:41.269 --> 00:26:42.759 align:start position:0% behalf of the theorem necessary but I think<00:26:41.509> yeah<00:26:41.600> we<00:26:41.720> can<00:26:41.869> do<00:26:41.960> mean<00:26:42.289> a<00:26:42.320> theorem<00:26:42.619> can 00:26:42.759 --> 00:26:42.769 align:start position:0% think yeah we can do mean a theorem can 00:26:42.769 --> 00:26:45.279 align:start position:0% think yeah we can do mean a theorem can do<00:26:42.919> more<00:26:43.509> perhaps<00:26:44.509> or<00:26:44.840> maybe<00:26:44.869> the<00:26:45.139> whole 00:26:45.279 --> 00:26:45.289 align:start position:0% do more perhaps or maybe the whole 00:26:45.289 --> 00:26:48.659 align:start position:0% do more perhaps or maybe the whole ecosystem<00:26:45.950> can<00:26:46.100> do<00:26:46.249> more<00:26:46.460> in<00:26:47.210> education 00:26:48.659 --> 00:26:48.669 align:start position:0% ecosystem can do more in education 00:26:48.669 --> 00:26:51.989 align:start position:0% ecosystem can do more in education anybody<00:26:49.669> who<00:26:49.820> is<00:26:49.970> on<00:26:50.119> it<00:26:50.240> athyrium<00:26:50.929> has<00:26:51.590> a 00:26:51.989 --> 00:26:51.999 align:start position:0% anybody who is on it athyrium has a 00:26:51.999 --> 00:26:55.600 align:start position:0% anybody who is on it athyrium has a responsibility<00:26:52.999> or<00:26:53.749> has<00:26:53.960> a<00:26:53.990> I<00:26:54.559> don't<00:26:55.429> want<00:26:55.549> to 00:26:55.600 --> 00:26:55.610 align:start position:0% responsibility or has a I don't want to 00:26:55.610 --> 00:26:58.060 align:start position:0% responsibility or has a I don't want to say<00:26:55.700> obligation<00:26:56.269> to<00:26:56.600> to<00:26:56.960> be<00:26:57.139> themselves<00:26:57.499> in 00:26:58.060 --> 00:26:58.070 align:start position:0% say obligation to to be themselves in 00:26:58.070 --> 00:27:01.090 align:start position:0% say obligation to to be themselves in evangelist<00:26:59.049> and<00:27:00.049> tell<00:27:00.320> others<00:27:00.619> about<00:27:00.649> it<00:27:01.070> I 00:27:01.090 --> 00:27:01.100 align:start position:0% evangelist and tell others about it I 00:27:01.100 --> 00:27:06.369 align:start position:0% evangelist and tell others about it I think<00:27:03.399> yeah<00:27:04.399> a<00:27:04.580> tough<00:27:05.539> question<00:27:05.749> but<00:27:06.139> a<00:27:06.200> good 00:27:06.369 --> 00:27:06.379 align:start position:0% think yeah a tough question but a good 00:27:06.379 --> 00:27:09.430 align:start position:0% think yeah a tough question but a good question<00:27:06.830> I<00:27:07.009> can<00:27:07.940> address<00:27:08.749> it<00:27:08.869> from<00:27:09.139> a<00:27:09.230> couple 00:27:09.430 --> 00:27:09.440 align:start position:0% question I can address it from a couple 00:27:09.440 --> 00:27:12.009 align:start position:0% question I can address it from a couple of<00:27:09.590> perspectives<00:27:10.279> from<00:27:11.119> the<00:27:11.389> Foundation's 00:27:12.009 --> 00:27:12.019 align:start position:0% of perspectives from the Foundation's 00:27:12.019 --> 00:27:16.210 align:start position:0% of perspectives from the Foundation's perspective<00:27:13.090> focus<00:27:14.090> on<00:27:14.330> making<00:27:15.289> a<00:27:15.590> multi<00:27:15.980> cig 00:27:16.210 --> 00:27:16.220 align:start position:0% perspective focus on making a multi cig 00:27:16.220 --> 00:27:18.549 align:start position:0% perspective focus on making a multi cig wallet<00:27:16.639> really<00:27:17.269> elegant<00:27:17.809> and<00:27:18.110> easy<00:27:18.200> to<00:27:18.529> use 00:27:18.549 --> 00:27:18.559 align:start position:0% wallet really elegant and easy to use 00:27:18.559 --> 00:27:22.180 align:start position:0% wallet really elegant and easy to use focus<00:27:19.159> on<00:27:19.549> making<00:27:20.480> a<00:27:20.720> beautiful<00:27:20.960> very<00:27:21.740> elegant 00:27:22.180 --> 00:27:22.190 align:start position:0% focus on making a beautiful very elegant 00:27:22.190 --> 00:27:27.609 align:start position:0% focus on making a beautiful very elegant missed<00:27:22.899> ether<00:27:23.899> browser<00:27:24.169> experience<00:27:24.850> I<00:27:26.619> think 00:27:27.609 --> 00:27:27.619 align:start position:0% missed ether browser experience I think 00:27:27.619 --> 00:27:30.970 align:start position:0% missed ether browser experience I think and<00:27:27.830> hope<00:27:27.889> that<00:27:28.369> that<00:27:28.549> will<00:27:29.110> make<00:27:30.110> it<00:27:30.259> easy<00:27:30.499> for 00:27:30.970 --> 00:27:30.980 align:start position:0% and hope that that will make it easy for 00:27:30.980 --> 00:27:33.460 align:start position:0% and hope that that will make it easy for non-technical<00:27:31.519> people<00:27:31.999> to<00:27:32.480> appreciate<00:27:32.960> some 00:27:33.460 --> 00:27:33.470 align:start position:0% non-technical people to appreciate some 00:27:33.470 --> 00:27:36.119 align:start position:0% non-technical people to appreciate some of<00:27:33.559> the<00:27:33.649> early<00:27:33.980> benefits<00:27:34.460> of<00:27:34.610> the<00:27:34.700> ecosystem 00:27:36.119 --> 00:27:36.129 align:start position:0% of the early benefits of the ecosystem 00:27:36.129 --> 00:27:39.820 align:start position:0% of the early benefits of the ecosystem at<00:27:37.129> consensus<00:27:37.879> were<00:27:38.210> putting<00:27:39.110> together<00:27:39.259> games 00:27:39.820 --> 00:27:39.830 align:start position:0% at consensus were putting together games 00:27:39.830 --> 00:27:41.590 align:start position:0% at consensus were putting together games we're<00:27:40.580> also<00:27:40.879> putting<00:27:41.119> together<00:27:41.360> an 00:27:41.590 --> 00:27:41.600 align:start position:0% we're also putting together an 00:27:41.600 --> 00:27:43.269 align:start position:0% we're also putting together an accounting<00:27:42.049> system<00:27:42.200> we<00:27:42.529> don't<00:27:42.740> expect<00:27:43.100> people 00:27:43.269 --> 00:27:43.279 align:start position:0% accounting system we don't expect people 00:27:43.279 --> 00:27:46.930 align:start position:0% accounting system we don't expect people to<00:27:43.509> who<00:27:44.509> are<00:27:44.720> very<00:27:45.499> interested<00:27:45.860> in<00:27:46.669> checking 00:27:46.930 --> 00:27:46.940 align:start position:0% to who are very interested in checking 00:27:46.940 --> 00:27:48.489 align:start position:0% to who are very interested in checking out<00:27:47.210> a<00:27:47.240> theorem<00:27:47.600> we<00:27:47.690> don't<00:27:47.869> expect<00:27:48.200> them<00:27:48.350> to 00:27:48.489 --> 00:27:48.499 align:start position:0% out a theorem we don't expect them to 00:27:48.499 --> 00:27:50.529 align:start position:0% out a theorem we don't expect them to fire<00:27:48.799> up<00:27:48.950> the<00:27:49.100> accounting<00:27:49.580> system<00:27:49.999> in<00:27:50.210> the<00:27:50.330> in 00:27:50.529 --> 00:27:50.539 align:start position:0% fire up the accounting system in the in 00:27:50.539 --> 00:27:53.820 align:start position:0% fire up the accounting system in the in the<00:27:50.570> first<00:27:50.899> day<00:27:51.309> so<00:27:52.309> we're<00:27:52.519> trying<00:27:52.669> to<00:27:52.879> build 00:27:53.820 --> 00:27:53.830 align:start position:0% the first day so we're trying to build 00:27:53.830 --> 00:27:58.919 align:start position:0% the first day so we're trying to build some<00:27:54.830> decentralized<00:27:55.789> applications<00:27:57.009> poker 00:27:58.919 --> 00:27:58.929 align:start position:0% some decentralized applications poker 00:27:58.929 --> 00:28:04.090 align:start position:0% some decentralized applications poker democracy<00:28:00.039> Dow<00:28:01.039> Wars<00:28:02.320> prediction<00:28:03.320> markets<00:28:03.799> or 00:28:04.090 --> 00:28:04.100 align:start position:0% democracy Dow Wars prediction markets or 00:28:04.100 --> 00:28:06.789 align:start position:0% democracy Dow Wars prediction markets or trying<00:28:04.369> to<00:28:04.460> put<00:28:05.179> together<00:28:05.299> a<00:28:06.080> very 00:28:06.789 --> 00:28:06.799 align:start position:0% trying to put together a very 00:28:06.799 --> 00:28:10.419 align:start position:0% trying to put together a very entertaining<00:28:07.389> skin<00:28:08.440> for<00:28:09.440> one<00:28:10.220> of<00:28:10.340> our 00:28:10.419 --> 00:28:10.429 align:start position:0% entertaining skin for one of our 00:28:10.429 --> 00:28:12.700 align:start position:0% entertaining skin for one of our prediction<00:28:10.879> market<00:28:11.179> offerings<00:28:11.570> so<00:28:11.899> we<00:28:12.470> are 00:28:12.700 --> 00:28:12.710 align:start position:0% prediction market offerings so we are 00:28:12.710 --> 00:28:18.700 align:start position:0% prediction market offerings so we are indeed<00:28:14.379> trying<00:28:15.379> to<00:28:15.940> create<00:28:16.940> applications<00:28:17.710> for 00:28:18.700 --> 00:28:18.710 align:start position:0% indeed trying to create applications for 00:28:18.710 --> 00:28:22.239 align:start position:0% indeed trying to create applications for normal<00:28:19.190> people<00:28:19.659> and<00:28:20.769> it's<00:28:21.769> just<00:28:22.070> going<00:28:22.220> to 00:28:22.239 --> 00:28:22.249 align:start position:0% normal people and it's just going to 00:28:22.249 --> 00:28:24.220 align:start position:0% normal people and it's just going to take<00:28:22.309> some<00:28:22.429> time<00:28:22.610> it<00:28:22.999> platforms<00:28:23.840> only<00:28:24.080> been 00:28:24.220 --> 00:28:24.230 align:start position:0% take some time it platforms only been 00:28:24.230 --> 00:28:25.690 align:start position:0% take some time it platforms only been out<00:28:24.320> for<00:28:24.379> a<00:28:24.619> short<00:28:24.649> while<00:28:24.980> and<00:28:25.309> people<00:28:25.580> are 00:28:25.690 --> 00:28:25.700 align:start position:0% out for a short while and people are 00:28:25.700 --> 00:28:29.440 align:start position:0% out for a short while and people are still<00:28:25.879> developing<00:28:26.119> I<00:28:27.850> think<00:28:28.850> I'd<00:28:29.029> say<00:28:29.240> that 00:28:29.440 --> 00:28:29.450 align:start position:0% still developing I think I'd say that 00:28:29.450 --> 00:28:34.060 align:start position:0% still developing I think I'd say that I'm<00:28:29.799> by<00:28:30.799> and<00:28:30.980> large<00:28:31.480> demand<00:28:32.480> has<00:28:33.019> always<00:28:33.830> been 00:28:34.060 --> 00:28:34.070 align:start position:0% I'm by and large demand has always been 00:28:34.070 --> 00:28:38.349 align:start position:0% I'm by and large demand has always been a<00:28:34.129> major<00:28:34.580> concern<00:28:35.119> for<00:28:36.220> us<00:28:37.220> as<00:28:37.580> architects<00:28:38.240> of 00:28:38.349 --> 00:28:38.359 align:start position:0% a major concern for us as architects of 00:28:38.359 --> 00:28:41.499 align:start position:0% a major concern for us as architects of the<00:28:38.480> system<00:28:39.220> but<00:28:40.220> perhaps<00:28:40.399> not<00:28:40.669> in<00:28:40.730> quite<00:28:41.330> the 00:28:41.499 --> 00:28:41.509 align:start position:0% the system but perhaps not in quite the 00:28:41.509 --> 00:28:42.310 align:start position:0% the system but perhaps not in quite the same<00:28:41.539> way<00:28:41.749> that 00:28:42.310 --> 00:28:42.320 align:start position:0% same way that 00:28:42.320 --> 00:28:46.240 align:start position:0% same way that that<00:28:42.919> everybody<00:28:43.549> thinks<00:28:44.179> of<00:28:44.450> it<00:28:44.950> we've<00:28:45.950> always 00:28:46.240 --> 00:28:46.250 align:start position:0% that everybody thinks of it we've always 00:28:46.250 --> 00:28:50.080 align:start position:0% that everybody thinks of it we've always considered<00:28:47.179> the<00:28:47.899> end<00:28:48.860> users<00:28:49.490> so<00:28:49.730> to<00:28:49.789> speak 00:28:50.080 --> 00:28:50.090 align:start position:0% considered the end users so to speak 00:28:50.090 --> 00:28:52.120 align:start position:0% considered the end users so to speak from<00:28:50.630> our<00:28:50.840> point<00:28:51.289> of<00:28:51.470> view<00:28:51.529> to<00:28:51.919> be<00:28:52.039> the 00:28:52.120 --> 00:28:52.130 align:start position:0% from our point of view to be the 00:28:52.130 --> 00:28:53.769 align:start position:0% from our point of view to be the developers<00:28:52.700> that<00:28:52.730> are<00:28:52.940> going<00:28:53.120> to<00:28:53.210> use<00:28:53.480> this<00:28:53.720> to 00:28:53.769 --> 00:28:53.779 align:start position:0% developers that are going to use this to 00:28:53.779 --> 00:28:56.200 align:start position:0% developers that are going to use this to make<00:28:54.139> the<00:28:54.289> final<00:28:54.740> sort<00:28:54.980> of<00:28:55.100> applications<00:28:56.029> and 00:28:56.200 --> 00:28:56.210 align:start position:0% make the final sort of applications and 00:28:56.210 --> 00:28:58.299 align:start position:0% make the final sort of applications and infrastructure<00:28:56.409> so<00:28:57.409> from<00:28:57.590> our<00:28:57.740> point<00:28:58.070> of<00:28:58.250> view 00:28:58.299 --> 00:28:58.309 align:start position:0% infrastructure so from our point of view 00:28:58.309 --> 00:29:00.129 align:start position:0% infrastructure so from our point of view the<00:28:58.669> the<00:28:58.880> man<00:28:59.090> that<00:28:59.330> were<00:28:59.480> trying<00:28:59.809> to<00:28:59.899> create 00:29:00.129 --> 00:29:00.139 align:start position:0% the the man that were trying to create 00:29:00.139 --> 00:29:04.450 align:start position:0% the the man that were trying to create is<00:29:01.029> having<00:29:02.029> having<00:29:02.960> developers<00:29:03.470> want<00:29:04.130> to<00:29:04.309> come 00:29:04.450 --> 00:29:04.460 align:start position:0% is having having developers want to come 00:29:04.460 --> 00:29:06.580 align:start position:0% is having having developers want to come to<00:29:04.549> the<00:29:04.639> platform<00:29:04.850> find<00:29:05.659> it<00:29:05.779> easy<00:29:05.960> to<00:29:06.200> get<00:29:06.440> to 00:29:06.580 --> 00:29:06.590 align:start position:0% to the platform find it easy to get to 00:29:06.590 --> 00:29:08.919 align:start position:0% to the platform find it easy to get to grips<00:29:06.710> with<00:29:07.000> find<00:29:08.000> easy<00:29:08.179> to<00:29:08.360> learn<00:29:08.570> and<00:29:08.630> find 00:29:08.919 --> 00:29:08.929 align:start position:0% grips with find easy to learn and find 00:29:08.929 --> 00:29:12.310 align:start position:0% grips with find easy to learn and find it<00:29:09.019> easy<00:29:09.169> to<00:29:09.259> develop<00:29:09.470> on<00:29:10.330> so<00:29:11.330> from<00:29:11.990> our<00:29:12.080> point 00:29:12.310 --> 00:29:12.320 align:start position:0% it easy to develop on so from our point 00:29:12.320 --> 00:29:14.289 align:start position:0% it easy to develop on so from our point of<00:29:12.440> view<00:29:12.500> it's<00:29:12.740> always<00:29:13.039> about<00:29:13.190> making<00:29:13.789> the<00:29:14.000> API 00:29:14.289 --> 00:29:14.299 align:start position:0% of view it's always about making the API 00:29:14.299 --> 00:29:17.980 align:start position:0% of view it's always about making the API is<00:29:14.419> as<00:29:14.809> transparent<00:29:15.679> as<00:29:15.679> possible<00:29:16.990> making 00:29:17.980 --> 00:29:17.990 align:start position:0% is as transparent as possible making 00:29:17.990 --> 00:29:20.830 align:start position:0% is as transparent as possible making things<00:29:18.409> as<00:29:18.620> making<00:29:19.549> the<00:29:19.669> tools<00:29:20.000> in<00:29:20.389> order<00:29:20.629> to 00:29:20.830 --> 00:29:20.840 align:start position:0% things as making the tools in order to 00:29:20.840 --> 00:29:22.779 align:start position:0% things as making the tools in order to make<00:29:21.019> developers<00:29:21.919> as<00:29:22.039> comfortable<00:29:22.549> as 00:29:22.779 --> 00:29:22.789 align:start position:0% make developers as comfortable as 00:29:22.789 --> 00:29:25.480 align:start position:0% make developers as comfortable as possible<00:29:23.080> to<00:29:24.080> arm<00:29:24.259> to<00:29:24.470> understand<00:29:25.100> what<00:29:25.309> it<00:29:25.399> is 00:29:25.480 --> 00:29:25.490 align:start position:0% possible to arm to understand what it is 00:29:25.490 --> 00:29:31.930 align:start position:0% possible to arm to understand what it is that<00:29:25.549> they're<00:29:25.820> doing<00:29:30.129> so<00:29:31.129> I<00:29:31.429> think<00:29:31.580> there's 00:29:31.930 --> 00:29:31.940 align:start position:0% that they're doing so I think there's 00:29:31.940 --> 00:29:33.580 align:start position:0% that they're doing so I think there's another<00:29:32.149> way<00:29:32.389> of<00:29:32.419> seeing<00:29:32.990> this<00:29:33.200> which<00:29:33.440> is 00:29:33.580 --> 00:29:33.590 align:start position:0% another way of seeing this which is 00:29:33.590 --> 00:29:35.860 align:start position:0% another way of seeing this which is basically<00:29:34.009> it<00:29:34.700> is<00:29:35.000> the<00:29:35.179> parallel<00:29:35.480> case 00:29:35.860 --> 00:29:35.870 align:start position:0% basically it is the parallel case 00:29:35.870 --> 00:29:38.379 align:start position:0% basically it is the parallel case Bitcoin<00:29:36.769> query<00:29:37.429> you<00:29:37.610> need<00:29:37.759> lots<00:29:38.090> of<00:29:38.210> mass 00:29:38.379 --> 00:29:38.389 align:start position:0% Bitcoin query you need lots of mass 00:29:38.389 --> 00:29:40.210 align:start position:0% Bitcoin query you need lots of mass adoption<00:29:38.570> lots<00:29:39.169> of<00:29:39.320> understanding<00:29:39.950> lots<00:29:40.100> of 00:29:40.210 --> 00:29:40.220 align:start position:0% adoption lots of understanding lots of 00:29:40.220 --> 00:29:42.730 align:start position:0% adoption lots of understanding lots of people<00:29:40.399> using<00:29:40.580> it<00:29:40.789> or<00:29:40.970> is<00:29:41.629> it<00:29:41.659> SQL<00:29:42.409> where 00:29:42.730 --> 00:29:42.740 align:start position:0% people using it or is it SQL where 00:29:42.740 --> 00:29:44.470 align:start position:0% people using it or is it SQL where everybody's<00:29:43.309> using<00:29:43.490> it<00:29:43.700> already<00:29:43.850> because<00:29:44.360> the 00:29:44.470 --> 00:29:44.480 align:start position:0% everybody's using it already because the 00:29:44.480 --> 00:29:46.360 align:start position:0% everybody's using it already because the infrastructure<00:29:44.990> runs<00:29:45.320> on<00:29:45.529> it<00:29:45.679> and<00:29:46.070> it's<00:29:46.190> just 00:29:46.360 --> 00:29:46.370 align:start position:0% infrastructure runs on it and it's just 00:29:46.370 --> 00:29:49.779 align:start position:0% infrastructure runs on it and it's just an<00:29:46.519> invisible<00:29:47.000> substrate<00:29:47.539> and<00:29:47.720> my<00:29:48.470> gas<00:29:48.889> is<00:29:49.460> the 00:29:49.779 --> 00:29:49.789 align:start position:0% an invisible substrate and my gas is the 00:29:49.789 --> 00:29:51.039 align:start position:0% an invisible substrate and my gas is the etherium<00:29:50.299> is<00:29:50.419> going<00:29:50.539> to<00:29:50.600> wind<00:29:50.750> up<00:29:50.870> being 00:29:51.039 --> 00:29:51.049 align:start position:0% etherium is going to wind up being 00:29:51.049 --> 00:29:52.570 align:start position:0% etherium is going to wind up being closer<00:29:51.320> to<00:29:51.529> the<00:29:51.620> SQL<00:29:52.009> end<00:29:52.190> of<00:29:52.340> the<00:29:52.399> spectrum 00:29:52.570 --> 00:29:52.580 align:start position:0% closer to the SQL end of the spectrum 00:29:52.580 --> 00:29:55.990 align:start position:0% closer to the SQL end of the spectrum and<00:29:53.830> although<00:29:54.830> if<00:29:55.009> we<00:29:55.159> will<00:29:55.340> bind<00:29:55.549> up<00:29:55.730> being<00:29:55.940> a 00:29:55.990 --> 00:29:56.000 align:start position:0% and although if we will bind up being a 00:29:56.000 --> 00:29:57.879 align:start position:0% and although if we will bind up being a major<00:29:56.179> brand<00:29:56.539> inside<00:29:56.899> a<00:29:56.929> computer<00:29:57.139> security 00:29:57.879 --> 00:29:57.889 align:start position:0% major brand inside a computer security 00:29:57.889 --> 00:30:00.279 align:start position:0% major brand inside a computer security where<00:29:58.519> you<00:29:58.789> know<00:29:58.879> athyrium<00:29:59.450> saw<00:29:59.809> inside 00:30:00.279 --> 00:30:00.289 align:start position:0% where you know athyrium saw inside 00:30:00.289 --> 00:30:03.039 align:start position:0% where you know athyrium saw inside equals<00:30:00.769> doesn't<00:30:01.279> get<00:30:01.429> hacked<00:30:01.750> that<00:30:02.750> it<00:30:02.870> could 00:30:03.039 --> 00:30:03.049 align:start position:0% equals doesn't get hacked that it could 00:30:03.049 --> 00:30:04.629 align:start position:0% equals doesn't get hacked that it could be<00:30:03.139> the<00:30:03.259> other<00:30:03.379> way<00:30:03.529> around<00:30:03.559> but<00:30:04.399> at<00:30:04.519> this 00:30:04.629 --> 00:30:04.639 align:start position:0% be the other way around but at this 00:30:04.639 --> 00:30:06.249 align:start position:0% be the other way around but at this point<00:30:04.909> I<00:30:05.240> think<00:30:05.509> that<00:30:05.659> the<00:30:05.720> people<00:30:05.840> that<00:30:06.139> have 00:30:06.249 --> 00:30:06.259 align:start position:0% point I think that the people that have 00:30:06.259 --> 00:30:09.490 align:start position:0% point I think that the people that have the<00:30:06.409> ability<00:30:06.440> to<00:30:07.720> meaningfully<00:30:08.720> deploy<00:30:09.080> adapt 00:30:09.490 --> 00:30:09.500 align:start position:0% the ability to meaningfully deploy adapt 00:30:09.500 --> 00:30:11.350 align:start position:0% the ability to meaningfully deploy adapt that<00:30:09.529> will<00:30:09.980> be<00:30:10.100> then<00:30:10.250> used<00:30:10.279> by<00:30:10.820> other<00:30:10.970> people 00:30:11.350 --> 00:30:11.360 align:start position:0% that will be then used by other people 00:30:11.360 --> 00:30:13.480 align:start position:0% that will be then used by other people are<00:30:11.649> relatively<00:30:12.649> small<00:30:13.009> right<00:30:13.309> it's 00:30:13.480 --> 00:30:13.490 align:start position:0% are relatively small right it's 00:30:13.490 --> 00:30:14.830 align:start position:0% are relatively small right it's institutions<00:30:14.149> for<00:30:14.330> which<00:30:14.480> people<00:30:14.809> are 00:30:14.830 --> 00:30:14.840 align:start position:0% institutions for which people are 00:30:14.840 --> 00:30:16.930 align:start position:0% institutions for which people are already<00:30:15.049> customers<00:30:15.799> which<00:30:16.279> is<00:30:16.399> why<00:30:16.519> the<00:30:16.580> banks 00:30:16.930 --> 00:30:16.940 align:start position:0% already customers which is why the banks 00:30:16.940 --> 00:30:18.759 align:start position:0% already customers which is why the banks are<00:30:17.059> so<00:30:17.210> exciting<00:30:17.659> they've<00:30:18.110> already<00:30:18.259> got<00:30:18.529> huge 00:30:18.759 --> 00:30:18.769 align:start position:0% are so exciting they've already got huge 00:30:18.769 --> 00:30:21.220 align:start position:0% are so exciting they've already got huge customer<00:30:19.039> bases<00:30:19.460> or<00:30:19.820> its<00:30:20.659> people<00:30:20.899> that<00:30:21.080> are 00:30:21.220 --> 00:30:21.230 align:start position:0% customer bases or its people that are 00:30:21.230 --> 00:30:22.629 align:start position:0% customer bases or its people that are creating<00:30:21.559> tools<00:30:21.710> for<00:30:21.919> other<00:30:22.009> people<00:30:22.340> to<00:30:22.429> use 00:30:22.629 --> 00:30:22.639 align:start position:0% creating tools for other people to use 00:30:22.639 --> 00:30:24.970 align:start position:0% creating tools for other people to use the<00:30:23.240> big<00:30:23.389> turning<00:30:23.809> point<00:30:23.840> is<00:30:24.230> if<00:30:24.379> we<00:30:24.500> get<00:30:24.679> a<00:30:24.710> big 00:30:24.970 --> 00:30:24.980 align:start position:0% the big turning point is if we get a big 00:30:24.980 --> 00:30:27.549 align:start position:0% the big turning point is if we get a big social<00:30:25.250> web<00:30:25.549> type<00:30:25.909> app<00:30:26.149> only<00:30:26.480> theorem<00:30:27.049> or<00:30:27.200> a 00:30:27.549 --> 00:30:27.559 align:start position:0% social web type app only theorem or a 00:30:27.559 --> 00:30:29.560 align:start position:0% social web type app only theorem or a big<00:30:27.799> game<00:30:28.070> right<00:30:28.279> if<00:30:28.490> you<00:30:28.610> see<00:30:28.789> you<00:30:28.970> know<00:30:29.059> world 00:30:29.560 --> 00:30:29.570 align:start position:0% big game right if you see you know world 00:30:29.570 --> 00:30:31.600 align:start position:0% big game right if you see you know world of<00:30:29.720> warcraft<00:30:29.960> manages<00:30:30.710> its<00:30:30.860> magic<00:30:31.190> swords<00:30:31.490> on 00:30:31.600 --> 00:30:31.610 align:start position:0% of warcraft manages its magic swords on 00:30:31.610 --> 00:30:33.220 align:start position:0% of warcraft manages its magic swords on etherium<00:30:32.059> or<00:30:32.240> you<00:30:32.330> get<00:30:32.570> a<00:30:32.600> decentralized 00:30:33.220 --> 00:30:33.230 align:start position:0% etherium or you get a decentralized 00:30:33.230 --> 00:30:35.649 align:start position:0% etherium or you get a decentralized reddit<00:30:33.649> where<00:30:33.980> people<00:30:34.279> come<00:30:34.519> actually<00:30:35.419> make<00:30:35.629> a 00:30:35.649 --> 00:30:35.659 align:start position:0% reddit where people come actually make a 00:30:35.659 --> 00:30:38.259 align:start position:0% reddit where people come actually make a living<00:30:36.110> as<00:30:36.289> content<00:30:37.279> finders<00:30:37.789> editors 00:30:38.259 --> 00:30:38.269 align:start position:0% living as content finders editors 00:30:38.269 --> 00:30:40.960 align:start position:0% living as content finders editors creators<00:30:38.929> you<00:30:39.860> know<00:30:39.950> something<00:30:40.490> like<00:30:40.519> that 00:30:40.960 --> 00:30:40.970 align:start position:0% creators you know something like that 00:30:40.970 --> 00:30:42.999 align:start position:0% creators you know something like that would<00:30:41.179> suddenly<00:30:41.509> change<00:30:41.779> it<00:30:42.230> imogen<00:30:42.830> heap's 00:30:42.999 --> 00:30:43.009 align:start position:0% would suddenly change it imogen heap's 00:30:43.009 --> 00:30:44.499 align:start position:0% would suddenly change it imogen heap's fair<00:30:43.279> trade<00:30:43.519> music<00:30:43.909> stuff<00:30:44.120> would<00:30:44.299> be<00:30:44.330> another 00:30:44.499 --> 00:30:44.509 align:start position:0% fair trade music stuff would be another 00:30:44.509 --> 00:30:46.539 align:start position:0% fair trade music stuff would be another possibility<00:30:44.990> if<00:30:45.320> you<00:30:45.440> saw<00:30:45.590> systemic 00:30:46.539 --> 00:30:46.549 align:start position:0% possibility if you saw systemic 00:30:46.549 --> 00:30:48.399 align:start position:0% possibility if you saw systemic transformation<00:30:47.299> around<00:30:47.509> fair<00:30:47.750> trade<00:30:47.990> music 00:30:48.399 --> 00:30:48.409 align:start position:0% transformation around fair trade music 00:30:48.409 --> 00:30:50.950 align:start position:0% transformation around fair trade music something<00:30:49.190> like<00:30:49.460> that<00:30:49.669> but<00:30:50.059> I<00:30:50.120> think<00:30:50.360> that<00:30:50.480> I 00:30:50.950 --> 00:30:50.960 align:start position:0% something like that but I think that I 00:30:50.960 --> 00:30:52.869 align:start position:0% something like that but I think that I mean<00:30:51.409> this<00:30:51.529> is<00:30:51.679> one<00:30:51.799> of<00:30:51.830> these<00:30:51.980> things<00:30:52.129> where<00:30:52.309> a 00:30:52.869 --> 00:30:52.879 align:start position:0% mean this is one of these things where a 00:30:52.879 --> 00:30:54.549 align:start position:0% mean this is one of these things where a lot<00:30:53.570> of<00:30:53.600> it<00:30:53.750> is<00:30:53.840> too<00:30:54.110> early 00:30:54.549 --> 00:30:54.559 align:start position:0% lot of it is too early 00:30:54.559 --> 00:30:57.430 align:start position:0% lot of it is too early tell<00:30:54.879> like<00:30:55.879> we're<00:30:56.509> gonna<00:30:56.600> wind<00:30:56.840> up<00:30:56.960> following 00:30:57.430 --> 00:30:57.440 align:start position:0% tell like we're gonna wind up following 00:30:57.440 --> 00:30:59.499 align:start position:0% tell like we're gonna wind up following one<00:30:57.980> of<00:30:58.009> those<00:30:58.249> trends<00:30:58.759> as<00:30:58.850> it<00:30:58.940> begins<00:30:59.149> to<00:30:59.330> go 00:30:59.499 --> 00:30:59.509 align:start position:0% one of those trends as it begins to go 00:30:59.509 --> 00:31:02.139 align:start position:0% one of those trends as it begins to go you<00:31:00.019> know<00:31:00.139> zoom<00:31:00.499> but<00:31:01.249> until<00:31:01.639> it<00:31:01.669> kind<00:31:01.970> of 00:31:02.139 --> 00:31:02.149 align:start position:0% you know zoom but until it kind of 00:31:02.149 --> 00:31:03.759 align:start position:0% you know zoom but until it kind of achieves<00:31:02.480> that<00:31:02.570> liftoff<00:31:03.049> we're<00:31:03.559> kind<00:31:03.710> of 00:31:03.759 --> 00:31:03.769 align:start position:0% achieves that liftoff we're kind of 00:31:03.769 --> 00:31:05.680 align:start position:0% achieves that liftoff we're kind of guessing<00:31:04.279> and<00:31:04.549> keeping<00:31:04.850> our<00:31:04.940> options<00:31:04.999> open<00:31:05.419> on 00:31:05.680 --> 00:31:05.690 align:start position:0% guessing and keeping our options open on 00:31:05.690 --> 00:31:07.600 align:start position:0% guessing and keeping our options open on that<00:31:05.870> and<00:31:06.110> rather<00:31:07.039> than<00:31:07.159> have<00:31:07.340> an<00:31:07.429> actual 00:31:07.600 --> 00:31:07.610 align:start position:0% that and rather than have an actual 00:31:07.610 --> 00:31:09.549 align:start position:0% that and rather than have an actual fixed<00:31:08.059> strategy<00:31:08.570> because<00:31:09.110> we<00:31:09.230> don't<00:31:09.379> really 00:31:09.549 --> 00:31:09.559 align:start position:0% fixed strategy because we don't really 00:31:09.559 --> 00:31:10.779 align:start position:0% fixed strategy because we don't really know<00:31:09.649> what<00:31:09.799> people<00:31:09.919> will<00:31:10.100> make<00:31:10.309> of<00:31:10.460> our<00:31:10.580> work 00:31:10.779 --> 00:31:10.789 align:start position:0% know what people will make of our work 00:31:10.789 --> 00:31:12.489 align:start position:0% know what people will make of our work you<00:31:11.480> know<00:31:11.570> that's<00:31:11.960> very<00:31:12.139> much<00:31:12.259> something 00:31:12.489 --> 00:31:12.499 align:start position:0% you know that's very much something 00:31:12.499 --> 00:31:13.810 align:start position:0% you know that's very much something where<00:31:12.710> we<00:31:12.799> have<00:31:12.889> to<00:31:13.009> follow<00:31:13.220> the<00:31:13.519> public 00:31:13.810 --> 00:31:13.820 align:start position:0% where we have to follow the public 00:31:13.820 --> 00:31:16.060 align:start position:0% where we have to follow the public rather<00:31:14.029> than<00:31:14.210> lead<00:31:14.629> them<00:31:14.870> or<00:31:15.139> maybe<00:31:15.799> I<00:31:15.889> have 00:31:16.060 --> 00:31:16.070 align:start position:0% rather than lead them or maybe I have 00:31:16.070 --> 00:31:18.820 align:start position:0% rather than lead them or maybe I have thought<00:31:16.249> wrong<00:31:16.490> I<00:31:16.990> mean<00:31:17.990> yeah<00:31:18.259> I<00:31:18.289> mean<00:31:18.350> in 00:31:18.820 --> 00:31:18.830 align:start position:0% thought wrong I mean yeah I mean in 00:31:18.830 --> 00:31:21.399 align:start position:0% thought wrong I mean yeah I mean in fairness<00:31:19.070> a<00:31:19.490> theorem<00:31:19.879> has<00:31:19.940> only<00:31:20.120> been<00:31:20.360> out<00:31:20.629> in 00:31:21.399 --> 00:31:21.409 align:start position:0% fairness a theorem has only been out in 00:31:21.409 --> 00:31:23.320 align:start position:0% fairness a theorem has only been out in the<00:31:21.529> wild<00:31:21.889> for<00:31:21.950> three<00:31:22.820> and<00:31:22.940> a<00:31:22.970> half<00:31:22.999> months 00:31:23.320 --> 00:31:23.330 align:start position:0% the wild for three and a half months 00:31:23.330 --> 00:31:27.669 align:start position:0% the wild for three and a half months barely<00:31:24.039> for<00:31:25.039> more<00:31:26.029> or<00:31:26.149> less<00:31:26.269> so<00:31:26.480> it's<00:31:27.409> it's 00:31:27.669 --> 00:31:27.679 align:start position:0% barely for more or less so it's it's 00:31:27.679 --> 00:31:31.509 align:start position:0% barely for more or less so it's it's still<00:31:27.919> very<00:31:28.129> very<00:31:28.249> new<00:31:28.610> and<00:31:28.850> and<00:31:29.090> as<00:31:30.220> yeah<00:31:31.220> as 00:31:31.509 --> 00:31:31.519 align:start position:0% still very very new and and as yeah as 00:31:31.519 --> 00:31:35.859 align:start position:0% still very very new and and as yeah as Jeff<00:31:32.299> azurite<00:31:33.139> kevin<00:31:33.440> was<00:31:33.559> saying<00:31:33.799> before<00:31:34.869> the 00:31:35.859 --> 00:31:35.869 align:start position:0% Jeff azurite kevin was saying before the 00:31:35.869 --> 00:31:37.210 align:start position:0% Jeff azurite kevin was saying before the focus<00:31:36.169> was<00:31:36.320> the<00:31:36.379> end<00:31:36.619> you<00:31:36.740> at<00:31:36.889> the<00:31:36.980> end<00:31:37.129> user 00:31:37.210 --> 00:31:37.220 align:start position:0% focus was the end you at the end user 00:31:37.220 --> 00:31:39.580 align:start position:0% focus was the end you at the end user was<00:31:37.429> a<00:31:37.460> developer<00:31:37.999> and<00:31:38.179> now<00:31:38.779> as<00:31:39.049> more<00:31:39.409> and<00:31:39.499> more 00:31:39.580 --> 00:31:39.590 align:start position:0% was a developer and now as more and more 00:31:39.590 --> 00:31:42.669 align:start position:0% was a developer and now as more and more apps<00:31:39.889> get<00:31:40.519> out<00:31:40.759> there<00:31:41.360> then<00:31:42.259> the<00:31:42.409> end<00:31:42.529> user 00:31:42.669 --> 00:31:42.679 align:start position:0% apps get out there then the end user 00:31:42.679 --> 00:31:44.440 align:start position:0% apps get out there then the end user will<00:31:42.950> also<00:31:43.249> be<00:31:43.340> the<00:31:43.460> end<00:31:43.610> user<00:31:43.759> like<00:31:44.119> the<00:31:44.240> user 00:31:44.440 --> 00:31:44.450 align:start position:0% will also be the end user like the user 00:31:44.450 --> 00:31:49.330 align:start position:0% will also be the end user like the user the<00:31:44.779> non<00:31:44.929> technical<00:31:45.110> user<00:31:47.950> great<00:31:48.950> another 00:31:49.330 --> 00:31:49.340 align:start position:0% the non technical user great another 00:31:49.340 --> 00:31:50.830 align:start position:0% the non technical user great another question<00:31:49.730> out<00:31:49.850> there<00:31:49.879> yeah<00:31:50.450> give<00:31:50.690> a<00:31:50.720> couple 00:31:50.830 --> 00:31:50.840 align:start position:0% question out there yeah give a couple 00:31:50.840 --> 00:31:59.710 align:start position:0% question out there yeah give a couple questions<00:31:55.720> and<00:31:57.279> say<00:31:58.279> perhaps<00:31:58.850> Gavin's<00:31:59.480> right 00:31:59.710 --> 00:31:59.720 align:start position:0% questions and say perhaps Gavin's right 00:31:59.720 --> 00:32:02.950 align:start position:0% questions and say perhaps Gavin's right and<00:31:59.929> maps<00:32:00.080> in<00:32:00.320> a<00:32:00.409> long-term<00:32:01.600> Bitcoin<00:32:02.600> will<00:32:02.779> be 00:32:02.950 --> 00:32:02.960 align:start position:0% and maps in a long-term Bitcoin will be 00:32:02.960 --> 00:32:04.749 align:start position:0% and maps in a long-term Bitcoin will be in<00:32:03.169> a<00:32:03.289> relevance<00:32:03.710> in<00:32:03.980> comparison<00:32:04.580> to<00:32:04.730> a 00:32:04.749 --> 00:32:04.759 align:start position:0% in a relevance in comparison to a 00:32:04.759 --> 00:32:07.720 align:start position:0% in a relevance in comparison to a theorem<00:32:05.119> and<00:32:05.269> but<00:32:06.259> surely<00:32:06.799> at<00:32:07.009> this<00:32:07.220> at<00:32:07.669> this 00:32:07.720 --> 00:32:07.730 align:start position:0% theorem and but surely at this at this 00:32:07.730 --> 00:32:09.909 align:start position:0% theorem and but surely at this at this point<00:32:08.090> in<00:32:08.419> bitcoins<00:32:09.049> evolution<00:32:09.649> and<00:32:09.799> a 00:32:09.909 --> 00:32:09.919 align:start position:0% point in bitcoins evolution and a 00:32:09.919 --> 00:32:12.279 align:start position:0% point in bitcoins evolution and a theorems<00:32:10.340> evolution<00:32:10.970> not<00:32:11.659> only<00:32:11.779> are<00:32:11.960> there<00:32:12.080> so 00:32:12.279 --> 00:32:12.289 align:start position:0% theorems evolution not only are there so 00:32:12.289 --> 00:32:13.899 align:start position:0% theorems evolution not only are there so many<00:32:12.320> lessons<00:32:12.919> to<00:32:13.070> learn<00:32:13.279> from<00:32:13.700> what's 00:32:13.899 --> 00:32:13.909 align:start position:0% many lessons to learn from what's 00:32:13.909 --> 00:32:16.509 align:start position:0% many lessons to learn from what's happening<00:32:14.059> in<00:32:14.330> the<00:32:14.419> Bitcoin<00:32:14.869> ecosystem<00:32:15.519> but 00:32:16.509 --> 00:32:16.519 align:start position:0% happening in the Bitcoin ecosystem but 00:32:16.519 --> 00:32:19.720 align:start position:0% happening in the Bitcoin ecosystem but also<00:32:16.730> there's<00:32:17.179> a<00:32:17.710> very<00:32:18.710> valuable<00:32:19.070> work<00:32:19.429> it's 00:32:19.720 --> 00:32:19.730 align:start position:0% also there's a very valuable work it's 00:32:19.730 --> 00:32:21.609 align:start position:0% also there's a very valuable work it's being<00:32:19.940> carried<00:32:20.269> out<00:32:20.509> funded<00:32:21.259> by<00:32:21.409> those 00:32:21.609 --> 00:32:21.619 align:start position:0% being carried out funded by those 00:32:21.619 --> 00:32:23.799 align:start position:0% being carried out funded by those billion<00:32:21.950> dollars<00:32:22.220> of<00:32:22.249> VC<00:32:22.700> money<00:32:22.850> and<00:32:23.179> so<00:32:23.779> I 00:32:23.799 --> 00:32:23.809 align:start position:0% billion dollars of VC money and so I 00:32:23.809 --> 00:32:28.419 align:start position:0% billion dollars of VC money and so I just<00:32:24.049> wonder<00:32:24.470> I<00:32:26.139> I<00:32:27.139> think<00:32:27.409> bitcoins<00:32:27.889> not 00:32:28.419 --> 00:32:28.429 align:start position:0% just wonder I I think bitcoins not 00:32:28.429 --> 00:32:29.950 align:start position:0% just wonder I I think bitcoins not talking<00:32:28.759> about<00:32:28.850> a<00:32:28.940> theorem<00:32:29.269> but<00:32:29.450> the<00:32:29.600> theorem 00:32:29.950 --> 00:32:29.960 align:start position:0% talking about a theorem but the theorem 00:32:29.960 --> 00:32:33.060 align:start position:0% talking about a theorem but the theorem is<00:32:30.049> also<00:32:30.350> made<00:32:30.559> the<00:32:30.710> conscious<00:32:31.190> choice<00:32:31.580> not<00:32:32.269> to 00:32:33.060 --> 00:32:33.070 align:start position:0% is also made the conscious choice not to 00:32:33.070 --> 00:32:34.960 align:start position:0% is also made the conscious choice not to talk<00:32:34.070> about<00:32:34.340> some<00:32:34.549> of<00:32:34.580> the<00:32:34.669> work<00:32:34.789> that's 00:32:34.960 --> 00:32:34.970 align:start position:0% talk about some of the work that's 00:32:34.970 --> 00:32:36.580 align:start position:0% talk about some of the work that's happening<00:32:35.090> Bitcoin<00:32:35.720> I<00:32:35.990> just<00:32:36.350> like<00:32:36.499> your 00:32:36.580 --> 00:32:36.590 align:start position:0% happening Bitcoin I just like your 00:32:36.590 --> 00:32:38.919 align:start position:0% happening Bitcoin I just like your thoughts<00:32:36.919> on<00:32:37.220> that<00:32:37.519> strategic<00:32:38.509> decision 00:32:38.919 --> 00:32:38.929 align:start position:0% thoughts on that strategic decision 00:32:38.929 --> 00:32:42.340 align:start position:0% thoughts on that strategic decision within<00:32:39.110> this<00:32:39.320> conference<00:32:40.029> yeah<00:32:41.029> I<00:32:41.059> mean<00:32:41.119> so<00:32:41.480> in 00:32:42.340 --> 00:32:42.350 align:start position:0% within this conference yeah I mean so in 00:32:42.350 --> 00:32:44.440 align:start position:0% within this conference yeah I mean so in terms<00:32:42.679> of<00:32:42.950> irrelevant<00:32:43.669> let's<00:32:43.970> be<00:32:44.149> clear<00:32:44.330> I 00:32:44.440 --> 00:32:44.450 align:start position:0% terms of irrelevant let's be clear I 00:32:44.450 --> 00:32:46.389 align:start position:0% terms of irrelevant let's be clear I didn't<00:32:44.899> mean<00:32:45.080> that<00:32:45.230> Bitcoin<00:32:45.679> was<00:32:45.889> irrelevant 00:32:46.389 --> 00:32:46.399 align:start position:0% didn't mean that Bitcoin was irrelevant 00:32:46.399 --> 00:32:49.359 align:start position:0% didn't mean that Bitcoin was irrelevant in<00:32:46.789> general<00:32:47.179> but<00:32:47.480> rather<00:32:47.690> simply<00:32:48.369> irrelevant 00:32:49.359 --> 00:32:49.369 align:start position:0% in general but rather simply irrelevant 00:32:49.369 --> 00:32:51.700 align:start position:0% in general but rather simply irrelevant from<00:32:49.850> the<00:32:49.940> point<00:32:50.119> of<00:32:50.330> view<00:32:50.389> of<00:32:50.659> what<00:32:51.320> is<00:32:51.499> the 00:32:51.700 --> 00:32:51.710 align:start position:0% from the point of view of what is the 00:32:51.710 --> 00:32:54.009 align:start position:0% from the point of view of what is the etherium<00:32:52.249> platform<00:32:52.730> art<00:32:52.970> you<00:32:53.149> know<00:32:53.269> were<00:32:53.720> not 00:32:54.009 --> 00:32:54.019 align:start position:0% etherium platform art you know were not 00:32:54.019 --> 00:32:56.200 align:start position:0% etherium platform art you know were not direct<00:32:54.710> competitors<00:32:55.309> etherium<00:32:55.789> is<00:32:55.909> very<00:32:56.090> much 00:32:56.200 --> 00:32:56.210 align:start position:0% direct competitors etherium is very much 00:32:56.210 --> 00:32:57.669 align:start position:0% direct competitors etherium is very much a<00:32:56.269> platform<00:32:56.809> for<00:32:56.929> doing<00:32:57.139> distributed 00:32:57.669 --> 00:32:57.679 align:start position:0% a platform for doing distributed 00:32:57.679 --> 00:32:59.470 align:start position:0% a platform for doing distributed applications<00:32:58.220> bitcoin<00:32:58.820> is<00:32:58.850> very<00:32:59.210> much<00:32:59.299> you 00:32:59.470 --> 00:32:59.480 align:start position:0% applications bitcoin is very much you 00:32:59.480 --> 00:33:01.210 align:start position:0% applications bitcoin is very much you know<00:32:59.509> its<00:32:59.720> own<00:32:59.840> its<00:33:00.200> own<00:33:00.320> thing<00:33:00.529> it's<00:33:00.710> in<00:33:00.980> terms 00:33:01.210 --> 00:33:01.220 align:start position:0% know its own its own thing it's in terms 00:33:01.220 --> 00:33:06.630 align:start position:0% know its own its own thing it's in terms of<00:33:01.279> a<00:33:01.369> currency 00:33:06.630 --> 00:33:06.640 align:start position:0% 00:33:06.640 --> 00:33:09.570 align:start position:0% sorry<00:33:07.640> for<00:33:07.820> getting<00:33:07.910> into<00:33:08.360> trouble<00:33:08.540> there<00:33:08.840> I 00:33:09.570 --> 00:33:09.580 align:start position:0% sorry for getting into trouble there I 00:33:09.580 --> 00:33:13.120 align:start position:0% sorry for getting into trouble there I agree<00:33:10.580> we<00:33:11.300> are<00:33:11.480> a<00:33:11.510> decentralized<00:33:12.410> application 00:33:13.120 --> 00:33:13.130 align:start position:0% agree we are a decentralized application 00:33:13.130 --> 00:33:16.720 align:start position:0% agree we are a decentralized application platform<00:33:13.700> are<00:33:14.030> our<00:33:14.450> token<00:33:15.230> is<00:33:15.500> a<00:33:15.530> crypto<00:33:16.250> fuel 00:33:16.720 --> 00:33:16.730 align:start position:0% platform are our token is a crypto fuel 00:33:16.730 --> 00:33:20.500 align:start position:0% platform are our token is a crypto fuel first<00:33:17.510> and<00:33:17.750> foremost<00:33:18.200> and<00:33:18.670> if<00:33:19.670> you<00:33:20.150> want<00:33:20.390> to 00:33:20.500 --> 00:33:20.510 align:start position:0% first and foremost and if you want to 00:33:20.510 --> 00:33:23.170 align:start position:0% first and foremost and if you want to pay<00:33:20.810> people<00:33:21.050> with<00:33:21.560> that<00:33:21.830> crypto<00:33:22.400> fuel<00:33:22.730> it 00:33:23.170 --> 00:33:23.180 align:start position:0% pay people with that crypto fuel it 00:33:23.180 --> 00:33:30.450 align:start position:0% pay people with that crypto fuel it works<00:33:23.390> pretty<00:33:23.600> well<00:33:23.750> for<00:33:24.140> that<00:33:25.100> purpose<00:33:25.490> also 00:33:30.450 --> 00:33:30.460 align:start position:0% 00:33:30.460 --> 00:33:36.400 align:start position:0% next<00:33:31.460> question<00:33:32.680> hi<00:33:34.120> with<00:33:35.120> the<00:33:35.150> abduction<00:33:35.810> of<00:33:35.840> a 00:33:36.400 --> 00:33:36.410 align:start position:0% next question hi with the abduction of a 00:33:36.410 --> 00:33:38.800 align:start position:0% next question hi with the abduction of a government<00:33:36.830> smart<00:33:37.490> contact<00:33:37.880> have<00:33:38.480> you<00:33:38.690> ever 00:33:38.800 --> 00:33:38.810 align:start position:0% government smart contact have you ever 00:33:38.810 --> 00:33:43.120 align:start position:0% government smart contact have you ever thought<00:33:39.110> about<00:33:39.640> the<00:33:40.640> social<00:33:41.800> changes<00:33:42.800> needed 00:33:43.120 --> 00:33:43.130 align:start position:0% thought about the social changes needed 00:33:43.130 --> 00:33:45.550 align:start position:0% thought about the social changes needed to<00:33:43.340> order<00:33:43.790> our<00:33:43.820> vision<00:33:44.450> of<00:33:44.630> work<00:33:44.900> because<00:33:45.290> for 00:33:45.550 --> 00:33:45.560 align:start position:0% to order our vision of work because for 00:33:45.560 --> 00:33:48.160 align:start position:0% to order our vision of work because for example<00:33:45.590> a<00:33:45.920> lot<00:33:46.160> of<00:33:46.340> white<00:33:46.940> collar<00:33:47.180> works<00:33:47.750> will 00:33:48.160 --> 00:33:48.170 align:start position:0% example a lot of white collar works will 00:33:48.170 --> 00:33:56.380 align:start position:0% example a lot of white collar works will simply<00:33:48.620> disappear<00:33:48.680> I<00:33:54.880> think<00:33:55.880> heard<00:33:56.090> you<00:33:56.180> say 00:33:56.380 --> 00:33:56.390 align:start position:0% simply disappear I think heard you say 00:33:56.390 --> 00:33:58.150 align:start position:0% simply disappear I think heard you say what<00:33:57.050> did<00:33:57.140> we<00:33:57.230> take<00:33:57.380> the<00:33:57.590> theorem<00:33:57.950> in<00:33:58.100> the 00:33:58.150 --> 00:33:58.160 align:start position:0% what did we take the theorem in the 00:33:58.160 --> 00:33:59.800 align:start position:0% what did we take the theorem in the future<00:33:58.490> of<00:33:58.610> work<00:33:58.820> because<00:33:59.120> the<00:33:59.390> white<00:33:59.540> collar 00:33:59.800 --> 00:33:59.810 align:start position:0% future of work because the white collar 00:33:59.810 --> 00:34:01.150 align:start position:0% future of work because the white collar work<00:34:00.020> would<00:34:00.230> disappear<00:34:00.710> was<00:34:00.950> that<00:34:01.070> the 00:34:01.150 --> 00:34:01.160 align:start position:0% work would disappear was that the 00:34:01.160 --> 00:34:03.730 align:start position:0% work would disappear was that the question<00:34:01.190> um<00:34:02.230> well<00:34:03.230> we<00:34:03.530> know<00:34:03.710> that 00:34:03.730 --> 00:34:03.740 align:start position:0% question um well we know that 00:34:03.740 --> 00:34:05.770 align:start position:0% question um well we know that technological<00:34:04.640> unemployment<00:34:04.790> is<00:34:05.480> going<00:34:05.690> to 00:34:05.770 --> 00:34:05.780 align:start position:0% technological unemployment is going to 00:34:05.780 --> 00:34:08.560 align:start position:0% technological unemployment is going to hit<00:34:05.930> really<00:34:06.200> hard<00:34:06.760> one<00:34:07.760> part<00:34:08.000> of<00:34:08.090> my<00:34:08.180> family 00:34:08.560 --> 00:34:08.570 align:start position:0% hit really hard one part of my family 00:34:08.570 --> 00:34:10.570 align:start position:0% hit really hard one part of my family are<00:34:08.720> Scottish<00:34:09.020> working<00:34:09.560> class<00:34:09.830> from<00:34:10.190> areas 00:34:10.570 --> 00:34:10.580 align:start position:0% are Scottish working class from areas 00:34:10.580 --> 00:34:12.700 align:start position:0% are Scottish working class from areas that<00:34:10.820> were<00:34:11.000> completely<00:34:11.840> destroyed<00:34:12.020> when 00:34:12.700 --> 00:34:12.710 align:start position:0% that were completely destroyed when 00:34:12.710 --> 00:34:14.910 align:start position:0% that were completely destroyed when shipbuilding<00:34:13.400> cease<00:34:13.640> to<00:34:13.820> be<00:34:13.910> an<00:34:13.970> industry<00:34:14.420> and 00:34:14.910 --> 00:34:14.920 align:start position:0% shipbuilding cease to be an industry and 00:34:14.920 --> 00:34:17.950 align:start position:0% shipbuilding cease to be an industry and you<00:34:15.920> know<00:34:16.010> I<00:34:16.040> would<00:34:16.280> quite<00:34:16.580> like<00:34:16.820> to<00:34:16.880> see<00:34:17.300> you 00:34:17.950 --> 00:34:17.960 align:start position:0% you know I would quite like to see you 00:34:17.960 --> 00:34:19.990 align:start position:0% you know I would quite like to see you know<00:34:18.080> that<00:34:18.560> kind<00:34:18.830> of<00:34:19.040> stuff<00:34:19.280> happened<00:34:19.820> to 00:34:19.990 --> 00:34:20.000 align:start position:0% know that kind of stuff happened to 00:34:20.000 --> 00:34:23.170 align:start position:0% know that kind of stuff happened to large<00:34:20.840> areas<00:34:21.380> where<00:34:22.010> educated<00:34:22.850> people<00:34:23.090> are 00:34:23.170 --> 00:34:23.180 align:start position:0% large areas where educated people are 00:34:23.180 --> 00:34:24.820 align:start position:0% large areas where educated people are stuck<00:34:23.390> in<00:34:23.420> completely<00:34:24.020> unproductive<00:34:24.380> rules 00:34:24.820 --> 00:34:24.830 align:start position:0% stuck in completely unproductive rules 00:34:24.830 --> 00:34:27.100 align:start position:0% stuck in completely unproductive rules crucian<00:34:25.790> transactional<00:34:26.420> paperwork<00:34:26.840> between 00:34:27.100 --> 00:34:27.110 align:start position:0% crucian transactional paperwork between 00:34:27.110 --> 00:34:30.430 align:start position:0% crucian transactional paperwork between organizations<00:34:27.890> you<00:34:28.670> know<00:34:28.790> I<00:34:29.000> mean<00:34:29.260> we've<00:34:30.260> got 00:34:30.430 --> 00:34:30.440 align:start position:0% organizations you know I mean we've got 00:34:30.440 --> 00:34:32.290 align:start position:0% organizations you know I mean we've got a<00:34:30.470> real<00:34:30.680> problem<00:34:30.860> that<00:34:31.190> we've<00:34:31.310> got<00:34:31.520> more<00:34:31.790> human 00:34:32.290 --> 00:34:32.300 align:start position:0% a real problem that we've got more human 00:34:32.300 --> 00:34:34.000 align:start position:0% a real problem that we've got more human capacity<00:34:32.900> and<00:34:33.020> more<00:34:33.140> intelligence<00:34:33.710> and<00:34:33.920> we 00:34:34.000 --> 00:34:34.010 align:start position:0% capacity and more intelligence and we 00:34:34.010 --> 00:34:36.910 align:start position:0% capacity and more intelligence and we have<00:34:34.280> jobs<00:34:35.060> for<00:34:35.450> that's<00:34:36.050> a<00:34:36.170> limitation<00:34:36.320> of<00:34:36.860> the 00:34:36.910 --> 00:34:36.920 align:start position:0% have jobs for that's a limitation of the 00:34:36.920 --> 00:34:38.470 align:start position:0% have jobs for that's a limitation of the institutions<00:34:37.640> of<00:34:37.790> limitation<00:34:38.360> of<00:34:38.420> the 00:34:38.470 --> 00:34:38.480 align:start position:0% institutions of limitation of the 00:34:38.480 --> 00:34:40.210 align:start position:0% institutions of limitation of the questions<00:34:38.990> you<00:34:39.650> know<00:34:39.710> if<00:34:39.830> we<00:34:39.950> could<00:34:40.100> figure 00:34:40.210 --> 00:34:40.220 align:start position:0% questions you know if we could figure 00:34:40.220 --> 00:34:41.860 align:start position:0% questions you know if we could figure out<00:34:40.400> how<00:34:40.580> to<00:34:40.640> organize<00:34:41.090> society<00:34:41.390> around 00:34:41.860 --> 00:34:41.870 align:start position:0% out how to organize society around 00:34:41.870 --> 00:34:44.260 align:start position:0% out how to organize society around something<00:34:42.500> like<00:34:42.680> I<00:34:42.950> don't<00:34:43.430> know<00:34:43.520> building<00:34:44.150> on 00:34:44.260 --> 00:34:44.270 align:start position:0% something like I don't know building on 00:34:44.270 --> 00:34:45.550 align:start position:0% something like I don't know building on morrow<00:34:44.480> space<00:34:44.720> and<00:34:44.930> then<00:34:45.020> maybe<00:34:45.170> taking<00:34:45.500> a 00:34:45.550 --> 00:34:45.560 align:start position:0% morrow space and then maybe taking a 00:34:45.560 --> 00:34:47.440 align:start position:0% morrow space and then maybe taking a crack<00:34:45.770> at<00:34:45.800> interstellar<00:34:46.310> travel<00:34:46.790> I<00:34:46.910> think 00:34:47.440 --> 00:34:47.450 align:start position:0% crack at interstellar travel I think 00:34:47.450 --> 00:34:49.210 align:start position:0% crack at interstellar travel I think we'd<00:34:47.600> find<00:34:47.780> a<00:34:47.930> place<00:34:48.140> for<00:34:48.170> every<00:34:48.710> intelligent 00:34:49.210 --> 00:34:49.220 align:start position:0% we'd find a place for every intelligent 00:34:49.220 --> 00:34:50.590 align:start position:0% we'd find a place for every intelligent person<00:34:49.520> on<00:34:49.580> earth<00:34:49.610> to<00:34:49.880> work<00:34:50.060> to<00:34:50.210> the<00:34:50.300> limit<00:34:50.540> of 00:34:50.590 --> 00:34:50.600 align:start position:0% person on earth to work to the limit of 00:34:50.600 --> 00:34:52.720 align:start position:0% person on earth to work to the limit of their<00:34:50.720> capability<00:34:51.380> so<00:34:52.100> if<00:34:52.190> we<00:34:52.250> have<00:34:52.490> to<00:34:52.640> go 00:34:52.720 --> 00:34:52.730 align:start position:0% their capability so if we have to go 00:34:52.730 --> 00:34:53.970 align:start position:0% their capability so if we have to go through<00:34:52.940> technological<00:34:53.300> unemployment 00:34:53.970 --> 00:34:53.980 align:start position:0% through technological unemployment 00:34:53.980 --> 00:34:56.050 align:start position:0% through technological unemployment followed<00:34:54.980> by<00:34:55.100> a<00:34:55.130> revolutionary 00:34:56.050 --> 00:34:56.060 align:start position:0% followed by a revolutionary 00:34:56.060 --> 00:34:57.820 align:start position:0% followed by a revolutionary renegotiation<00:34:57.020> of<00:34:57.080> the<00:34:57.170> goals<00:34:57.350> of<00:34:57.470> the<00:34:57.560> human 00:34:57.820 --> 00:34:57.830 align:start position:0% renegotiation of the goals of the human 00:34:57.830 --> 00:35:00.100 align:start position:0% renegotiation of the goals of the human race<00:34:58.040> I<00:34:58.390> think<00:34:59.390> that<00:34:59.510> would<00:34:59.570> be<00:34:59.690> a<00:34:59.720> good<00:34:59.900> thing 00:35:00.100 --> 00:35:00.110 align:start position:0% race I think that would be a good thing 00:35:00.110 --> 00:35:02.280 align:start position:0% race I think that would be a good thing if<00:35:00.290> we<00:35:00.680> just<00:35:00.950> get<00:35:01.160> the<00:35:01.280> detector<00:35:01.700> logical 00:35:02.280 --> 00:35:02.290 align:start position:0% if we just get the detector logical 00:35:02.290 --> 00:35:04.300 align:start position:0% if we just get the detector logical unemployment<00:35:03.290> without<00:35:03.830> the<00:35:04.010> renegotiation 00:35:04.300 --> 00:35:04.310 align:start position:0% unemployment without the renegotiation 00:35:04.310 --> 00:35:06.700 align:start position:0% unemployment without the renegotiation about<00:35:05.000> the<00:35:05.090> long-term<00:35:05.270> goals<00:35:05.720> this<00:35:06.350> would<00:35:06.560> not 00:35:06.700 --> 00:35:06.710 align:start position:0% about the long-term goals this would not 00:35:06.710 --> 00:35:12.010 align:start position:0% about the long-term goals this would not be<00:35:06.860> so<00:35:07.040> good<00:35:10.450> okay<00:35:11.450> I<00:35:11.480> think<00:35:11.600> we<00:35:11.720> got<00:35:11.840> time<00:35:11.960> for 00:35:12.010 --> 00:35:12.020 align:start position:0% be so good okay I think we got time for 00:35:12.020 --> 00:35:15.000 align:start position:0% be so good okay I think we got time for one<00:35:12.170> more<00:35:12.260> question 00:35:15.000 --> 00:35:15.010 align:start position:0% 00:35:15.010 --> 00:35:18.960 align:start position:0% hi<00:35:15.640> I<00:35:16.030> think<00:35:16.810> some<00:35:17.140> of<00:35:17.170> the<00:35:17.410> demand<00:35:17.830> for<00:35:18.310> a 00:35:18.960 --> 00:35:18.970 align:start position:0% hi I think some of the demand for a 00:35:18.970 --> 00:35:21.540 align:start position:0% hi I think some of the demand for a serum<00:35:19.720> based<00:35:19.930> applications<00:35:20.650> can<00:35:21.040> come<00:35:21.250> from 00:35:21.540 --> 00:35:21.550 align:start position:0% serum based applications can come from 00:35:21.550 --> 00:35:24.180 align:start position:0% serum based applications can come from identity<00:35:22.360> management<00:35:22.750> i<00:35:23.170> dint<00:35:23.680> digital 00:35:24.180 --> 00:35:24.190 align:start position:0% identity management i dint digital 00:35:24.190 --> 00:35:27.330 align:start position:0% identity management i dint digital identity<00:35:24.760> space<00:35:25.350> and<00:35:26.350> that<00:35:26.590> was<00:35:26.710> wondering 00:35:27.330 --> 00:35:27.340 align:start position:0% identity space and that was wondering 00:35:27.340 --> 00:35:31.100 align:start position:0% identity space and that was wondering what<00:35:28.270> do<00:35:28.360> you<00:35:28.420> think<00:35:28.750> how<00:35:29.650> a<00:35:29.680> serum<00:35:30.400> can<00:35:30.640> help 00:35:31.100 --> 00:35:31.110 align:start position:0% what do you think how a serum can help 00:35:31.110 --> 00:35:35.010 align:start position:0% what do you think how a serum can help to<00:35:32.110> make<00:35:32.140> identity<00:35:33.100> schemes<00:35:33.760> more<00:35:34.180> efficient 00:35:35.010 --> 00:35:35.020 align:start position:0% to make identity schemes more efficient 00:35:35.020 --> 00:35:39.930 align:start position:0% to make identity schemes more efficient effective<00:35:35.470> and<00:35:37.350> maybe<00:35:38.350> you<00:35:38.530> can<00:35:38.560> touch<00:35:38.950> on<00:35:39.220> the 00:35:39.930 --> 00:35:39.940 align:start position:0% effective and maybe you can touch on the 00:35:39.940 --> 00:35:43.920 align:start position:0% effective and maybe you can touch on the the<00:35:40.810> terms<00:35:41.740> of<00:35:42.120> privacy<00:35:43.120> and<00:35:43.150> that<00:35:43.780> was 00:35:43.920 --> 00:35:43.930 align:start position:0% the terms of privacy and that was 00:35:43.930 --> 00:35:45.900 align:start position:0% the terms of privacy and that was happening<00:35:44.380> was<00:35:44.530> transparencies<00:35:45.250> bryson<00:35:45.760> the 00:35:45.900 --> 00:35:45.910 align:start position:0% happening was transparencies bryson the 00:35:45.910 --> 00:35:50.730 align:start position:0% happening was transparencies bryson the networking<00:35:46.710> sure<00:35:47.710> so<00:35:48.090> we<00:35:49.090> are<00:35:49.720> talking<00:35:50.620> with 00:35:50.730 --> 00:35:50.740 align:start position:0% networking sure so we are talking with 00:35:50.740 --> 00:35:54.380 align:start position:0% networking sure so we are talking with lots<00:35:50.920> of<00:35:51.100> groups<00:35:51.280> and<00:35:51.820> working<00:35:52.800> on<00:35:53.800> building 00:35:54.380 --> 00:35:54.390 align:start position:0% lots of groups and working on building 00:35:54.390 --> 00:35:59.250 align:start position:0% lots of groups and working on building an<00:35:55.390> identity<00:35:56.350> persona<00:35:57.160> system<00:35:58.260> integrated 00:35:59.250 --> 00:35:59.260 align:start position:0% an identity persona system integrated 00:35:59.260 --> 00:36:01.860 align:start position:0% an identity persona system integrated with<00:35:59.530> a<00:35:59.560> reputation<00:36:00.130> system<00:36:00.790> so<00:36:01.420> essentially 00:36:01.860 --> 00:36:01.870 align:start position:0% with a reputation system so essentially 00:36:01.870 --> 00:36:06.330 align:start position:0% with a reputation system so essentially our<00:36:01.990> strategy<00:36:02.530> is<00:36:02.680> to<00:36:04.110> do<00:36:05.110> our<00:36:05.260> best<00:36:05.560> to<00:36:06.070> map 00:36:06.330 --> 00:36:06.340 align:start position:0% our strategy is to do our best to map 00:36:06.340 --> 00:36:09.650 align:start position:0% our strategy is to do our best to map what<00:36:06.610> we<00:36:06.760> see<00:36:07.260> in<00:36:08.260> terms<00:36:08.650> of<00:36:08.860> our 00:36:09.650 --> 00:36:09.660 align:start position:0% what we see in terms of our 00:36:09.660 --> 00:36:13.260 align:start position:0% what we see in terms of our interpersonal<00:36:10.660> interactions<00:36:11.530> into<00:36:12.270> that 00:36:13.260 --> 00:36:13.270 align:start position:0% interpersonal interactions into that 00:36:13.270 --> 00:36:17.160 align:start position:0% interpersonal interactions into that space<00:36:13.660> so<00:36:15.030> we<00:36:16.030> believe<00:36:16.240> that<00:36:16.390> we<00:36:16.720> represent 00:36:17.160 --> 00:36:17.170 align:start position:0% space so we believe that we represent 00:36:17.170 --> 00:36:19.950 align:start position:0% space so we believe that we represent ourselves<00:36:17.710> from<00:36:18.460> different<00:36:18.880> personas<00:36:19.660> and 00:36:19.950 --> 00:36:19.960 align:start position:0% ourselves from different personas and 00:36:19.960 --> 00:36:23.370 align:start position:0% ourselves from different personas and that<00:36:20.380> we<00:36:20.560> interact<00:36:20.980> from<00:36:21.870> different<00:36:22.870> personas 00:36:23.370 --> 00:36:23.380 align:start position:0% that we interact from different personas 00:36:23.380 --> 00:36:26.430 align:start position:0% that we interact from different personas whether<00:36:23.710> we're<00:36:24.360> buying<00:36:25.360> or<00:36:25.690> selling<00:36:25.900> or 00:36:26.430 --> 00:36:26.440 align:start position:0% whether we're buying or selling or 00:36:26.440 --> 00:36:29.070 align:start position:0% whether we're buying or selling or lending<00:36:26.950> borrowing<00:36:27.520> repaying<00:36:28.060> or<00:36:28.570> working 00:36:29.070 --> 00:36:29.080 align:start position:0% lending borrowing repaying or working 00:36:29.080 --> 00:36:30.840 align:start position:0% lending borrowing repaying or working together<00:36:29.200> on<00:36:29.440> a<00:36:29.620> project<00:36:29.830> or<00:36:30.400> playing<00:36:30.610> games 00:36:30.840 --> 00:36:30.850 align:start position:0% together on a project or playing games 00:36:30.850 --> 00:36:36.300 align:start position:0% together on a project or playing games together<00:36:31.500> and<00:36:32.500> so<00:36:33.450> they're<00:36:34.470> in<00:36:35.470> our<00:36:35.620> you<00:36:36.040> port 00:36:36.300 --> 00:36:36.310 align:start position:0% together and so they're in our you port 00:36:36.310 --> 00:36:38.220 align:start position:0% together and so they're in our you port wallet<00:36:36.700> there<00:36:36.940> is<00:36:37.090> an<00:36:37.690> anchor<00:36:38.020> a 00:36:38.220 --> 00:36:38.230 align:start position:0% wallet there is an anchor a 00:36:38.230 --> 00:36:40.710 align:start position:0% wallet there is an anchor a cryptographic<00:36:38.770> key<00:36:39.460> pair<00:36:39.820> that<00:36:40.120> serves<00:36:40.420> as<00:36:40.600> an 00:36:40.710 --> 00:36:40.720 align:start position:0% cryptographic key pair that serves as an 00:36:40.720 --> 00:36:43.740 align:start position:0% cryptographic key pair that serves as an anchor<00:36:40.900> for<00:36:41.580> multiple<00:36:42.580> personas<00:36:43.120> that<00:36:43.360> you 00:36:43.740 --> 00:36:43.750 align:start position:0% anchor for multiple personas that you 00:36:43.750 --> 00:36:45.420 align:start position:0% anchor for multiple personas that you can<00:36:43.930> create<00:36:44.080> for<00:36:44.380> yourself<00:36:44.680> you<00:36:44.890> can<00:36:45.040> have<00:36:45.160> one 00:36:45.420 --> 00:36:45.430 align:start position:0% can create for yourself you can have one 00:36:45.430 --> 00:36:48.390 align:start position:0% can create for yourself you can have one or<00:36:45.460> many<00:36:46.500> you<00:36:47.500> probably<00:36:47.800> want<00:36:48.040> to<00:36:48.100> have<00:36:48.190> one 00:36:48.390 --> 00:36:48.400 align:start position:0% or many you probably want to have one 00:36:48.400 --> 00:36:52.010 align:start position:0% or many you probably want to have one canonical<00:36:49.090> persona<00:36:49.650> to<00:36:50.650> which<00:36:50.830> you<00:36:51.040> attach 00:36:52.010 --> 00:36:52.020 align:start position:0% canonical persona to which you attach 00:36:52.020 --> 00:36:54.830 align:start position:0% canonical persona to which you attach identifiers<00:36:53.020> like<00:36:53.470> email<00:36:53.890> address 00:36:54.830 --> 00:36:54.840 align:start position:0% identifiers like email address 00:36:54.840 --> 00:36:59.090 align:start position:0% identifiers like email address attributes<00:36:55.840> like<00:36:55.960> a<00:36:56.670> state-issued 00:36:59.090 --> 00:36:59.100 align:start position:0% attributes like a state-issued 00:36:59.100 --> 00:37:05.430 align:start position:0% attributes like a state-issued identification<00:37:00.300> certificate<00:37:01.860> and<00:37:04.140> if<00:37:05.140> you 00:37:05.430 --> 00:37:05.440 align:start position:0% identification certificate and if you 00:37:05.440 --> 00:37:07.680 align:start position:0% identification certificate and if you can<00:37:05.650> set<00:37:06.040> up<00:37:06.160> other<00:37:06.400> personas<00:37:07.000> that<00:37:07.030> can<00:37:07.480> be 00:37:07.680 --> 00:37:07.690 align:start position:0% can set up other personas that can be 00:37:07.690 --> 00:37:10.730 align:start position:0% can set up other personas that can be unlinked<00:37:08.260> in<00:37:08.500> unlink<00:37:08.950> able<00:37:09.220> to<00:37:10.030> your 00:37:10.730 --> 00:37:10.740 align:start position:0% unlinked in unlink able to your 00:37:10.740 --> 00:37:13.950 align:start position:0% unlinked in unlink able to your canonical<00:37:11.740> persona<00:37:12.400> so<00:37:12.700> if<00:37:12.790> you<00:37:12.940> want<00:37:13.150> to<00:37:13.240> not 00:37:13.950 --> 00:37:13.960 align:start position:0% canonical persona so if you want to not 00:37:13.960 --> 00:37:16.680 align:start position:0% canonical persona so if you want to not have<00:37:13.990> your<00:37:14.410> gamer<00:37:14.740> persona<00:37:15.510> associated<00:37:16.510> with 00:37:16.680 --> 00:37:16.690 align:start position:0% have your gamer persona associated with 00:37:16.690 --> 00:37:19.350 align:start position:0% have your gamer persona associated with your<00:37:16.960> canonical<00:37:17.650> and<00:37:18.070> work<00:37:18.190> persona<00:37:18.610> then<00:37:18.940> you 00:37:19.350 --> 00:37:19.360 align:start position:0% your canonical and work persona then you 00:37:19.360 --> 00:37:20.320 align:start position:0% your canonical and work persona then you can<00:37:19.570> do<00:37:19.690> that 00:37:20.320 --> 00:37:20.330 align:start position:0% can do that 00:37:20.330 --> 00:37:24.280 align:start position:0% can do that and<00:37:21.010> in<00:37:22.010> order<00:37:22.190> to<00:37:22.310> make<00:37:23.060> these<00:37:23.420> things<00:37:23.450> sort 00:37:24.280 --> 00:37:24.290 align:start position:0% and in order to make these things sort 00:37:24.290 --> 00:37:28.240 align:start position:0% and in order to make these things sort of<00:37:24.410> fuzzy<00:37:24.770> and<00:37:25.310> and<00:37:26.380> richly<00:37:27.380> representative 00:37:28.240 --> 00:37:28.250 align:start position:0% of fuzzy and and richly representative 00:37:28.250 --> 00:37:31.000 align:start position:0% of fuzzy and and richly representative of<00:37:28.370> who<00:37:28.580> we<00:37:28.730> are<00:37:28.910> and<00:37:29.210> and<00:37:29.540> more<00:37:30.010> trustful 00:37:31.000 --> 00:37:31.010 align:start position:0% of who we are and and more trustful 00:37:31.010 --> 00:37:33.220 align:start position:0% of who we are and and more trustful because<00:37:31.520> people<00:37:31.850> can<00:37:32.030> look<00:37:32.360> at<00:37:32.540> them<00:37:32.690> and<00:37:32.990> say 00:37:33.220 --> 00:37:33.230 align:start position:0% because people can look at them and say 00:37:33.230 --> 00:37:35.440 align:start position:0% because people can look at them and say oh<00:37:33.530> that<00:37:33.950> person<00:37:34.460> has<00:37:34.580> so<00:37:34.790> many<00:37:34.910> different 00:37:35.440 --> 00:37:35.450 align:start position:0% oh that person has so many different 00:37:35.450 --> 00:37:37.300 align:start position:0% oh that person has so many different kinds<00:37:35.630> of<00:37:35.990> interactions<00:37:36.500> they<00:37:36.980> couldn't 00:37:37.300 --> 00:37:37.310 align:start position:0% kinds of interactions they couldn't 00:37:37.310 --> 00:37:41.050 align:start position:0% kinds of interactions they couldn't possibly<00:37:37.670> be<00:37:37.910> spoofed<00:37:39.370> persona<00:37:40.370> serves<00:37:40.790> as<00:37:41.030> a 00:37:41.050 --> 00:37:41.060 align:start position:0% possibly be spoofed persona serves as a 00:37:41.060 --> 00:37:44.110 align:start position:0% possibly be spoofed persona serves as a container<00:37:41.870> for<00:37:42.520> reputational<00:37:43.520> attributes 00:37:44.110 --> 00:37:44.120 align:start position:0% container for reputational attributes 00:37:44.120 --> 00:37:47.100 align:start position:0% container for reputational attributes and<00:37:44.620> reputational<00:37:45.620> attestations<00:37:46.280> so 00:37:47.100 --> 00:37:47.110 align:start position:0% and reputational attestations so 00:37:47.110 --> 00:37:49.210 align:start position:0% and reputational attestations so attributes<00:37:48.110> are<00:37:48.290> things<00:37:48.530> that<00:37:48.620> you<00:37:48.920> know 00:37:49.210 --> 00:37:49.220 align:start position:0% attributes are things that you know 00:37:49.220 --> 00:37:52.660 align:start position:0% attributes are things that you know about<00:37:49.430> yourself<00:37:50.290> control<00:37:51.460> things<00:37:52.460> like 00:37:52.660 --> 00:37:52.670 align:start position:0% about yourself control things like 00:37:52.670 --> 00:37:55.360 align:start position:0% about yourself control things like financial<00:37:52.940> records<00:37:53.600> health<00:37:53.840> records<00:37:54.370> again 00:37:55.360 --> 00:37:55.370 align:start position:0% financial records health records again 00:37:55.370 --> 00:37:59.580 align:start position:0% financial records health records again that<00:37:55.610> the<00:37:55.910> state<00:37:56.390> issued<00:37:56.840> ID<00:37:57.340> and<00:37:58.340> those<00:37:58.880> are 00:37:59.580 --> 00:37:59.590 align:start position:0% that the state issued ID and those are 00:37:59.590 --> 00:38:08.130 align:start position:0% that the state issued ID and those are cryptographically<00:38:01.060> encoded<00:38:02.470> and<00:38:04.870> granularly 00:38:08.130 --> 00:38:08.140 align:start position:0% 00:38:08.140 --> 00:38:10.360 align:start position:0% accessible<00:38:09.140> if<00:38:09.410> you<00:38:09.590> make<00:38:09.800> them<00:38:10.010> accessible 00:38:10.360 --> 00:38:10.370 align:start position:0% accessible if you make them accessible 00:38:10.370 --> 00:38:13.300 align:start position:0% accessible if you make them accessible to<00:38:11.060> whoever<00:38:11.450> you<00:38:11.630> need<00:38:11.840> to<00:38:12.590> see<00:38:12.770> those<00:38:12.950> so<00:38:13.190> if 00:38:13.300 --> 00:38:13.310 align:start position:0% to whoever you need to see those so if 00:38:13.310 --> 00:38:15.580 align:start position:0% to whoever you need to see those so if you<00:38:13.460> want<00:38:13.640> to<00:38:13.760> send<00:38:14.390> your<00:38:14.690> certain<00:38:15.290> medical 00:38:15.580 --> 00:38:15.590 align:start position:0% you want to send your certain medical 00:38:15.590 --> 00:38:19.360 align:start position:0% you want to send your certain medical records<00:38:16.010> to<00:38:16.280> your<00:38:16.460> eye<00:38:16.880> doctor<00:38:17.210> you<00:38:18.160> you<00:38:19.160> don't 00:38:19.360 --> 00:38:19.370 align:start position:0% records to your eye doctor you you don't 00:38:19.370 --> 00:38:21.190 align:start position:0% records to your eye doctor you you don't need<00:38:19.490> to<00:38:19.670> send<00:38:19.910> your<00:38:20.420> your<00:38:20.720> full<00:38:20.960> medical 00:38:21.190 --> 00:38:21.200 align:start position:0% need to send your your full medical 00:38:21.200 --> 00:38:23.610 align:start position:0% need to send your your full medical history<00:38:21.440> you<00:38:21.890> can<00:38:22.040> select<00:38:22.460> what's<00:38:22.850> necessary 00:38:23.610 --> 00:38:23.620 align:start position:0% history you can select what's necessary 00:38:23.620 --> 00:38:29.830 align:start position:0% history you can select what's necessary attestations<00:38:24.620> are<00:38:25.070> things<00:38:25.340> that<00:38:26.080> people<00:38:28.840> a 00:38:29.830 --> 00:38:29.840 align:start position:0% attestations are things that people a 00:38:29.840 --> 00:38:32.980 align:start position:0% attestations are things that people a test<00:38:30.470> about<00:38:30.740> you<00:38:31.160> but<00:38:32.060> your<00:38:32.210> conduct<00:38:32.690> in 00:38:32.980 --> 00:38:32.990 align:start position:0% test about you but your conduct in 00:38:32.990 --> 00:38:34.450 align:start position:0% test about you but your conduct in different<00:38:33.410> transactions<00:38:34.130> so<00:38:34.310> those 00:38:34.450 --> 00:38:34.460 align:start position:0% different transactions so those 00:38:34.460 --> 00:38:36.010 align:start position:0% different transactions so those transactions<00:38:35.210> can<00:38:35.390> be<00:38:35.450> on<00:38:35.690> blockchain 00:38:36.010 --> 00:38:36.020 align:start position:0% transactions can be on blockchain 00:38:36.020 --> 00:38:38.020 align:start position:0% transactions can be on blockchain transactions<00:38:36.980> in<00:38:37.160> the<00:38:37.250> different<00:38:37.580> kinds<00:38:37.880> of 00:38:38.020 --> 00:38:38.030 align:start position:0% transactions in the different kinds of 00:38:38.030 --> 00:38:40.470 align:start position:0% transactions in the different kinds of situations<00:38:38.240> that<00:38:38.720> I<00:38:38.840> described<00:38:39.290> or<00:38:39.530> even 00:38:40.470 --> 00:38:40.480 align:start position:0% situations that I described or even 00:38:40.480 --> 00:38:43.030 align:start position:0% situations that I described or even physical<00:38:41.480> transaction<00:38:42.140> so<00:38:42.380> there's<00:38:42.650> also<00:38:42.800> the 00:38:43.030 --> 00:38:43.040 align:start position:0% physical transaction so there's also the 00:38:43.040 --> 00:38:45.700 align:start position:0% physical transaction so there's also the notion<00:38:43.220> of<00:38:43.520> just<00:38:44.030> like<00:38:44.780> having<00:38:45.110> a<00:38:45.200> cell<00:38:45.410> phone 00:38:45.700 --> 00:38:45.710 align:start position:0% notion of just like having a cell phone 00:38:45.710 --> 00:38:48.400 align:start position:0% notion of just like having a cell phone broadcasting<00:38:46.130> your<00:38:46.760> presence<00:38:47.240> Vinay<00:38:47.930> has<00:38:48.140> his 00:38:48.400 --> 00:38:48.410 align:start position:0% broadcasting your presence Vinay has his 00:38:48.410 --> 00:38:52.780 align:start position:0% broadcasting your presence Vinay has his broadcasting<00:38:49.160> his<00:38:49.310> presence<00:38:49.820> and<00:38:51.010> its<00:38:52.010> opt-in 00:38:52.780 --> 00:38:52.790 align:start position:0% broadcasting his presence and its opt-in 00:38:52.790 --> 00:38:54.220 align:start position:0% broadcasting his presence and its opt-in we<00:38:53.000> turn<00:38:53.240> these<00:38:53.390> things<00:38:53.630> on<00:38:53.840> because<00:38:54.200> it's 00:38:54.220 --> 00:38:54.230 align:start position:0% we turn these things on because it's 00:38:54.230 --> 00:38:58.360 align:start position:0% we turn these things on because it's valuable<00:38:54.680> to<00:38:54.830> us<00:38:55.300> to<00:38:56.590> have<00:38:57.590> each<00:38:57.710> other<00:38:57.950> a<00:38:58.040> test 00:38:58.360 --> 00:38:58.370 align:start position:0% valuable to us to have each other a test 00:38:58.370 --> 00:39:00.400 align:start position:0% valuable to us to have each other a test to<00:38:58.490> the<00:38:58.550> fact<00:38:58.820> that<00:38:58.910> we<00:38:59.150> were<00:38:59.300> here<00:38:59.690> in<00:38:59.930> this 00:39:00.400 --> 00:39:00.410 align:start position:0% to the fact that we were here in this 00:39:00.410 --> 00:39:02.740 align:start position:0% to the fact that we were here in this time<00:39:00.740> and<00:39:00.950> space<00:39:01.220> and<00:39:01.670> so<00:39:01.850> you<00:39:01.910> can<00:39:02.150> create<00:39:02.720> a 00:39:02.740 --> 00:39:02.750 align:start position:0% time and space and so you can create a 00:39:02.750 --> 00:39:04.720 align:start position:0% time and space and so you can create a very<00:39:03.020> rich<00:39:03.290> personal<00:39:03.920> profile<00:39:04.460> that's 00:39:04.720 --> 00:39:04.730 align:start position:0% very rich personal profile that's 00:39:04.730 --> 00:39:09.040 align:start position:0% very rich personal profile that's granularly<00:39:05.360> private<00:39:07.360> yeah<00:39:08.360> I<00:39:08.420> think<00:39:08.510> that's<00:39:08.810> a 00:39:09.040 --> 00:39:09.050 align:start position:0% granularly private yeah I think that's a 00:39:09.050 --> 00:39:11.110 align:start position:0% granularly private yeah I think that's a that's<00:39:09.860> a<00:39:10.100> good<00:39:10.310> start<00:39:10.550> and<00:39:10.640> I<00:39:10.700> can<00:39:10.850> certainly 00:39:11.110 --> 00:39:11.120 align:start position:0% that's a good start and I can certainly 00:39:11.120 --> 00:39:12.790 align:start position:0% that's a good start and I can certainly be<00:39:11.240> done<00:39:11.390> on<00:39:11.480> the<00:39:11.540> technology<00:39:12.050> as<00:39:12.140> it<00:39:12.260> stands<00:39:12.500> I 00:39:12.790 --> 00:39:12.800 align:start position:0% be done on the technology as it stands I 00:39:12.800 --> 00:39:13.960 align:start position:0% be done on the technology as it stands I think<00:39:13.280> that<00:39:13.520> we're<00:39:13.640> going<00:39:13.730> to<00:39:13.790> need<00:39:13.940> some 00:39:13.960 --> 00:39:13.970 align:start position:0% think that we're going to need some 00:39:13.970 --> 00:39:17.500 align:start position:0% think that we're going to need some further<00:39:14.720> sort<00:39:15.230> of<00:39:15.320> developments<00:39:16.510> especially 00:39:17.500 --> 00:39:17.510 align:start position:0% further sort of developments especially 00:39:17.510 --> 00:39:20.710 align:start position:0% further sort of developments especially in<00:39:17.600> terms<00:39:17.750> of<00:39:18.080> zero<00:39:19.010> knowledge<00:39:19.160> proofs<00:39:19.720> to 00:39:20.710 --> 00:39:20.720 align:start position:0% in terms of zero knowledge proofs to 00:39:20.720 --> 00:39:23.080 align:start position:0% in terms of zero knowledge proofs to guarantee<00:39:21.170> that<00:39:21.370> for<00:39:22.370> example<00:39:22.460> if<00:39:22.880> I<00:39:23.000> have 00:39:23.080 --> 00:39:23.090 align:start position:0% guarantee that for example if I have 00:39:23.090 --> 00:39:24.580 align:start position:0% guarantee that for example if I have multiple<00:39:23.240> personas<00:39:23.750> it<00:39:24.080> may<00:39:24.230> be<00:39:24.290> that<00:39:24.410> I 00:39:24.580 --> 00:39:24.590 align:start position:0% multiple personas it may be that I 00:39:24.590 --> 00:39:26.980 align:start position:0% multiple personas it may be that I actually<00:39:24.770> want<00:39:25.160> one<00:39:26.120> persona<00:39:26.450> to<00:39:26.720> sort<00:39:26.900> of 00:39:26.980 --> 00:39:26.990 align:start position:0% actually want one persona to sort of 00:39:26.990 --> 00:39:28.660 align:start position:0% actually want one persona to sort of vouch<00:39:27.200> for<00:39:27.590> the<00:39:27.650> other<00:39:27.800> one<00:39:28.040> and<00:39:28.220> say<00:39:28.400> actually 00:39:28.660 --> 00:39:28.670 align:start position:0% vouch for the other one and say actually 00:39:28.670 --> 00:39:31.510 align:start position:0% vouch for the other one and say actually there<00:39:29.330> is<00:39:29.480> some<00:39:29.720> this<00:39:30.200> isn't<00:39:30.500> maybe<00:39:30.740> a<00:39:31.040> master 00:39:31.510 --> 00:39:31.520 align:start position:0% there is some this isn't maybe a master 00:39:31.520 --> 00:39:33.160 align:start position:0% there is some this isn't maybe a master persona<00:39:31.850> but<00:39:32.090> it's<00:39:32.240> like<00:39:32.360> a<00:39:32.390> slave<00:39:32.690> persona 00:39:33.160 --> 00:39:33.170 align:start position:0% persona but it's like a slave persona 00:39:33.170 --> 00:39:33.609 align:start position:0% persona but it's like a slave persona down 00:39:33.609 --> 00:39:33.619 align:start position:0% down 00:39:33.619 --> 00:39:36.549 align:start position:0% down indeed<00:39:33.859> to<00:39:34.869> increase<00:39:35.869> my<00:39:36.019> privacy<00:39:36.349> in 00:39:36.549 --> 00:39:36.559 align:start position:0% indeed to increase my privacy in 00:39:36.559 --> 00:39:38.440 align:start position:0% indeed to increase my privacy in particular<00:39:36.829> ways<00:39:37.160> but<00:39:37.670> I<00:39:37.700> still<00:39:37.940> want<00:39:38.240> to 00:39:38.440 --> 00:39:38.450 align:start position:0% particular ways but I still want to 00:39:38.450 --> 00:39:41.739 align:start position:0% particular ways but I still want to without<00:39:39.230> actually<00:39:40.329> transparently<00:39:41.329> linking 00:39:41.739 --> 00:39:41.749 align:start position:0% without actually transparently linking 00:39:41.749 --> 00:39:43.989 align:start position:0% without actually transparently linking them<00:39:41.900> allow<00:39:42.259> one<00:39:42.589> to<00:39:42.619> to<00:39:43.279> state<00:39:43.519> that<00:39:43.730> yeah 00:39:43.989 --> 00:39:43.999 align:start position:0% them allow one to to state that yeah 00:39:43.999 --> 00:39:45.579 align:start position:0% them allow one to to state that yeah this<00:39:44.180> is<00:39:44.299> a<00:39:44.329> real<00:39:44.420> person<00:39:44.869> there<00:39:45.259> is<00:39:45.349> some 00:39:45.579 --> 00:39:45.589 align:start position:0% this is a real person there is some 00:39:45.589 --> 00:39:47.079 align:start position:0% this is a real person there is some government<00:39:45.920> issued<00:39:46.160> ID<00:39:46.339> but<00:39:46.640> I<00:39:46.670> want<00:39:46.880> to<00:39:46.940> tell 00:39:47.079 --> 00:39:47.089 align:start position:0% government issued ID but I want to tell 00:39:47.089 --> 00:39:49.930 align:start position:0% government issued ID but I want to tell you<00:39:47.210> anything<00:39:47.509> else<00:39:47.720> about<00:39:47.930> it<00:39:48.109> and<00:39:48.880> for<00:39:49.880> that 00:39:49.930 --> 00:39:49.940 align:start position:0% you anything else about it and for that 00:39:49.940 --> 00:39:51.039 align:start position:0% you anything else about it and for that we're<00:39:50.119> going<00:39:50.240> to<00:39:50.299> need<00:39:50.390> a<00:39:50.450> little<00:39:50.779> bit<00:39:50.900> more 00:39:51.039 --> 00:39:51.049 align:start position:0% we're going to need a little bit more 00:39:51.049 --> 00:39:57.190 align:start position:0% we're going to need a little bit more attack<00:39:53.920> in<00:39:54.920> where<00:39:55.609> all<00:39:55.759> this<00:39:55.999> kinda<00:39:56.749> reaches<00:39:57.109> a 00:39:57.190 --> 00:39:57.200 align:start position:0% attack in where all this kinda reaches a 00:39:57.200 --> 00:40:01.059 align:start position:0% attack in where all this kinda reaches a terminal<00:39:57.769> point<00:39:58.039> is<00:39:58.369> DNA<00:39:59.329> DNA<00:39:59.900> sequencing<00:40:00.650> IRS 00:40:01.059 --> 00:40:01.069 align:start position:0% terminal point is DNA DNA sequencing IRS 00:40:01.069 --> 00:40:02.289 align:start position:0% terminal point is DNA DNA sequencing IRS scanning<00:40:01.460> and<00:40:01.579> all<00:40:01.640> the<00:40:01.730> rest<00:40:01.880> of<00:40:02.029> that<00:40:02.059> are 00:40:02.289 --> 00:40:02.299 align:start position:0% scanning and all the rest of that are 00:40:02.299 --> 00:40:05.589 align:start position:0% scanning and all the rest of that are falling<00:40:03.259> in<00:40:03.349> price<00:40:03.589> extremely<00:40:04.130> rapidly<00:40:04.599> it 00:40:05.589 --> 00:40:05.599 align:start position:0% falling in price extremely rapidly it 00:40:05.599 --> 00:40:07.749 align:start position:0% falling in price extremely rapidly it seems<00:40:05.960> like<00:40:06.049> most<00:40:06.440> future<00:40:07.039> generations<00:40:07.609> of 00:40:07.749 --> 00:40:07.759 align:start position:0% seems like most future generations of 00:40:07.759 --> 00:40:09.069 align:start position:0% seems like most future generations of computing<00:40:08.180> devices<00:40:08.450> well<00:40:08.779> at<00:40:08.960> least 00:40:09.069 --> 00:40:09.079 align:start position:0% computing devices well at least 00:40:09.079 --> 00:40:10.870 align:start position:0% computing devices well at least fingerprint<00:40:09.680> identification<00:40:10.130> possibly 00:40:10.870 --> 00:40:10.880 align:start position:0% fingerprint identification possibly 00:40:10.880 --> 00:40:14.259 align:start position:0% fingerprint identification possibly facial<00:40:11.269> eyeballs<00:40:11.779> and<00:40:12.369> so<00:40:13.369> at<00:40:14.029> some<00:40:14.210> point 00:40:14.259 --> 00:40:14.269 align:start position:0% facial eyeballs and so at some point 00:40:14.269 --> 00:40:16.839 align:start position:0% facial eyeballs and so at some point there's<00:40:14.720> going<00:40:14.869> to<00:40:14.930> be<00:40:14.960> a<00:40:15.049> settlement<00:40:15.529> or<00:40:15.849> an 00:40:16.839 --> 00:40:16.849 align:start position:0% there's going to be a settlement or an 00:40:16.849 --> 00:40:19.150 align:start position:0% there's going to be a settlement or an interconnection<00:40:17.569> of<00:40:17.839> biometrics<00:40:18.829> and<00:40:18.980> block 00:40:19.150 --> 00:40:19.160 align:start position:0% interconnection of biometrics and block 00:40:19.160 --> 00:40:21.690 align:start position:0% interconnection of biometrics and block chains<00:40:19.460> and<00:40:19.730> the<00:40:20.319> necessary<00:40:21.319> crypt 00:40:21.690 --> 00:40:21.700 align:start position:0% chains and the necessary crypt 00:40:21.700 --> 00:40:24.700 align:start position:0% chains and the necessary crypt cryptography<00:40:22.700> to<00:40:22.730> separate<00:40:23.420> those<00:40:23.599> two<00:40:23.710> to 00:40:24.700 --> 00:40:24.710 align:start position:0% cryptography to separate those two to 00:40:24.710 --> 00:40:26.170 align:start position:0% cryptography to separate those two to the<00:40:24.829> point<00:40:25.039> where<00:40:25.249> you've<00:40:25.400> got<00:40:25.549> some<00:40:25.849> hope<00:40:26.059> of 00:40:26.170 --> 00:40:26.180 align:start position:0% the point where you've got some hope of 00:40:26.180 --> 00:40:28.299 align:start position:0% the point where you've got some hope of privacy<00:40:26.690> in<00:40:26.779> the<00:40:26.869> future<00:40:27.200> and<00:40:27.470> control<00:40:28.220> of 00:40:28.299 --> 00:40:28.309 align:start position:0% privacy in the future and control of 00:40:28.309 --> 00:40:29.920 align:start position:0% privacy in the future and control of your<00:40:28.400> identity<00:40:28.970> it's<00:40:29.359> kind<00:40:29.509> of<00:40:29.630> this<00:40:29.749> ongoing 00:40:29.920 --> 00:40:29.930 align:start position:0% your identity it's kind of this ongoing 00:40:29.930 --> 00:40:32.559 align:start position:0% your identity it's kind of this ongoing technical<00:40:30.410> negotiation<00:40:31.369> so<00:40:31.819> the<00:40:32.359> zero 00:40:32.559 --> 00:40:32.569 align:start position:0% technical negotiation so the zero 00:40:32.569 --> 00:40:33.999 align:start position:0% technical negotiation so the zero knowledge<00:40:32.749> proofs<00:40:33.109> come<00:40:33.319> in<00:40:33.410> from<00:40:33.589> one<00:40:33.740> side 00:40:33.999 --> 00:40:34.009 align:start position:0% knowledge proofs come in from one side 00:40:34.009 --> 00:40:36.190 align:start position:0% knowledge proofs come in from one side and<00:40:34.279> we<00:40:34.369> have<00:40:34.490> to<00:40:34.609> develop<00:40:34.849> the<00:40:35.240> technology 00:40:36.190 --> 00:40:36.200 align:start position:0% and we have to develop the technology 00:40:36.200 --> 00:40:38.620 align:start position:0% and we have to develop the technology side<00:40:36.410> as<00:40:36.920> fast<00:40:37.640> as<00:40:37.849> the<00:40:37.970> biometrics<00:40:38.539> are 00:40:38.620 --> 00:40:38.630 align:start position:0% side as fast as the biometrics are 00:40:38.630 --> 00:40:41.200 align:start position:0% side as fast as the biometrics are adopted<00:40:39.220> because<00:40:40.220> otherwise<00:40:40.640> it's<00:40:41.029> almost 00:40:41.200 --> 00:40:41.210 align:start position:0% adopted because otherwise it's almost 00:40:41.210 --> 00:40:43.420 align:start position:0% adopted because otherwise it's almost inevitably<00:40:41.809> wind<00:40:42.079> up<00:40:42.259> with<00:40:42.559> carob<00:40:42.890> biometric 00:40:43.420 --> 00:40:43.430 align:start position:0% inevitably wind up with carob biometric 00:40:43.430 --> 00:40:45.819 align:start position:0% inevitably wind up with carob biometric panopticon<00:40:43.700> where<00:40:44.450> somebody's<00:40:45.319> bank<00:40:45.559> gets 00:40:45.819 --> 00:40:45.829 align:start position:0% panopticon where somebody's bank gets 00:40:45.829 --> 00:40:47.499 align:start position:0% panopticon where somebody's bank gets hacked<00:40:46.069> and<00:40:46.400> they<00:40:46.460> released<00:40:46.759> you<00:40:46.999> know<00:40:47.089> half<00:40:47.359> a 00:40:47.499 --> 00:40:47.509 align:start position:0% hacked and they released you know half a 00:40:47.509 --> 00:40:49.660 align:start position:0% hacked and they released you know half a million<00:40:47.839> DNA<00:40:48.259> records<00:40:48.859> like<00:40:49.430> there<00:40:49.579> are 00:40:49.660 --> 00:40:49.670 align:start position:0% million DNA records like there are 00:40:49.670 --> 00:40:52.299 align:start position:0% million DNA records like there are unthinkable<00:40:50.239> privacy<00:40:50.839> implications<00:40:50.989> as<00:40:51.680> that 00:40:52.299 --> 00:40:52.309 align:start position:0% unthinkable privacy implications as that 00:40:52.309 --> 00:40:54.160 align:start position:0% unthinkable privacy implications as that kind<00:40:52.430> of<00:40:52.549> stuff<00:40:52.730> those<00:40:52.970> onwards<00:40:53.390> so<00:40:53.989> again 00:40:54.160 --> 00:40:54.170 align:start position:0% kind of stuff those onwards so again 00:40:54.170 --> 00:40:56.410 align:start position:0% kind of stuff those onwards so again it's<00:40:54.349> a<00:40:54.410> bit<00:40:54.529> like<00:40:54.650> I<00:40:54.829> OT<00:40:55.009> there's<00:40:55.970> really<00:40:56.059> no 00:40:56.410 --> 00:40:56.420 align:start position:0% it's a bit like I OT there's really no 00:40:56.420 --> 00:40:59.259 align:start position:0% it's a bit like I OT there's really no other<00:40:56.450> way<00:40:56.690> of<00:40:56.809> doing<00:40:57.170> this<00:40:57.819> you<00:40:58.819> know<00:40:58.910> we<00:40:59.059> have 00:40:59.259 --> 00:40:59.269 align:start position:0% other way of doing this you know we have 00:40:59.269 --> 00:41:00.519 align:start position:0% other way of doing this you know we have to<00:40:59.299> accept<00:40:59.839> that<00:40:59.960> we're<00:41:00.109> going<00:41:00.200> to<00:41:00.289> have<00:41:00.410> to 00:41:00.519 --> 00:41:00.529 align:start position:0% to accept that we're going to have to 00:41:00.529 --> 00:41:02.650 align:start position:0% to accept that we're going to have to build<00:41:00.710> these<00:41:00.859> systems<00:41:01.309> but<00:41:01.999> we<00:41:02.119> have<00:41:02.150> to<00:41:02.420> do<00:41:02.539> it 00:41:02.650 --> 00:41:02.660 align:start position:0% build these systems but we have to do it 00:41:02.660 --> 00:41:04.470 align:start position:0% build these systems but we have to do it with<00:41:02.779> the<00:41:02.869> expectation<00:41:03.200> that<00:41:03.589> they're<00:41:03.890> robust 00:41:04.470 --> 00:41:04.480 align:start position:0% with the expectation that they're robust 00:41:04.480 --> 00:41:07.900 align:start position:0% with the expectation that they're robust 10<00:41:05.480> 20<00:41:05.960> 30<00:41:06.170> years<00:41:06.470> out<00:41:06.769> when<00:41:06.980> DNA<00:41:07.249> sequencing 00:41:07.900 --> 00:41:07.910 align:start position:0% 10 20 30 years out when DNA sequencing 00:41:07.910 --> 00:41:15.249 align:start position:0% 10 20 30 years out when DNA sequencing is<00:41:08.029> fifteen<00:41:08.390> cents<00:41:13.180> well<00:41:14.180> thank<00:41:14.630> you<00:41:14.720> guys<00:41:14.869> um 00:41:15.249 --> 00:41:15.259 align:start position:0% is fifteen cents well thank you guys um 00:41:15.259 --> 00:41:18.519 align:start position:0% is fifteen cents well thank you guys um come<00:41:15.980> around<00:41:16.190> with<00:41:16.369> us